[Q] ADT 8.0.0 doesn't like Java libraries? - Android Software Development

Just updated to ADT 8.0.0 for Gingerbread goodness, and now it won't compile a project that compiled perfectly well on the previous version with the following error:
Code:
[2010-12-06 20:55:23 - Dex Loader] Unable to execute dex: null
[2010-12-06 20:55:23 - DummyAndroidProject] Conversion to Dalvik format failed: Unable to execute dex: null
I've narrowed this down to the fact that my Android project references a pure Java Eclipse project I have in the same workspace, which is a platform-neutral library I wrote myself. I confirmed by creating a blank Java project with an empty class, and a blank Android project that referenced the Java project as a library. This triggered the above dex error.
Has anyone else encountered this? I'm sure I'm not the only one who references external projects in this way?

I got the exact same problem. Have you found a solution?

Nothing yet. Going to report it as a bug and see of this behaviour is intentional. I certainly hope not.
As a workaround, manually including the library as a .jar should work...

Ok, now got it logged as bug 13000 (!) right here.
My current workaround is to link the source of my Java project to my Android project (right click Android project, 'Build Path' > 'Link Source')

FYI, Google have just pushed out AT 8.0.1 that fixes this bug. Hooray!

Related

[Q] Eclipse - check API specific code ?

Does anyone know how I can get Eclipse to check my code & see if all the API calls will work on a specific revision ? I've just written some code that used -
Code:
.getTextContent()
on an XML node. Worked fine on my (2.2) phone, but others were getting "Force Close" errors. I eventually worked out they had Andy 2.1, and getTextContent() was introduced in 2.2. OK, I rewrote it to use
Code:
.getNodeValue()
as I want it to run on their phones.
Is there any way I can get Eclipse to check my code against the Min SDK Version, to ensure all of it will work ? Sorry if its an obvious question, but its really annoying me. Thanks.

Android studio wont work with an api

So, I am currently messing around with android programming, and i am using android studio and my ide of choice. I have made a few simple apps(calculator and whatnot) without issue. But now i am trying to make an app using the youtube data api. I can not even get started on it though because i cant get the api to work. Heres what i have done so far.
I have taken the api zip file and unzipped it. This produced an youtube folder. I than copied this folder to the libs folder in my project. This caused no issues in and of itself.
I than tried to add some imports based on the api and that caused an syntax error
To fix that error i added the following lines to the build.gradle in the dependencies section at the bottom
Code:
compile fileTree(dir: 'libs/youtube', include: '*.jar')
compile fileTree(dir: 'libs/youtube/libs', include: '*.jar')
This fixed the syntax errors and also allowed it to build successfully
The issue comes when I try to actually add something based on the api. When i add the following lines of code...
Code:
/** Global instance of the HTTP transport. */
private static final HttpTransport HTTP_TRANSPORT = new NetHttpTransport();
/** Global instance of the JSON factory. */
private static final JsonFactory JSON_FACTORY = new JacksonFactory();
/** Global instance of Youtube object to make all API requests. */
private static YouTube youtube;
there are no syntax errors, but when i attempt to build it I get a single error
Code:
Gradle: Execution failed for task ':ApiTest2:dexDebug'.
> Failed to run command:
/Applications/Android Studio.app/sdk/build-tools/android-4.2.2/dx --dex --output /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/build/libs/ApiTest2-debug.dex /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/build/classes/debug /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/build/dependency-cache/debug /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/google-api-client-servlet-1.16.0-rc.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/google-oauth-client-servlet-1.16.0-rc.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/google-api-client-protobuf-1.16.0-rc.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/google-http-client-jdo-1.16.0-rc.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/google-api-services-youtube-v3-rev70-1.16.0-rc-sources.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/transaction-api-1.1.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/google-http-client-appengine-1.16.0-rc.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/jackson-core-asl-1.9.11.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/protobuf-java-2.4.1.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/httpclient-4.0.1.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/google-oauth-client-java6-1.16.0-rc.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/gson-2.1.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/google-http-client-gson-1.16.0-rc.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/commons-logging-1.1.1.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/google-http-client-android-1.16.0-rc.jar /Applications/Android Studio.app/sdk/extras/android/m2repository/com/android/support/support-v4/13.0.0/support-v4-13.0.0.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/jackson-core-2.1.3.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/google-api-client-gson-1.16.0-rc.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/google-api-services-youtube-v3-rev70-1.16.0-rc.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/google-oauth-client-java7-1.16.0-rc.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/google-api-client-android-1.16.0-rc.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/jetty-util-6.1.26.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/google-http-client-jackson-1.16.0-rc.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/httpcore-4.0.1.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/jetty-6.1.26.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/google-oauth-client-jetty-1.16.0-rc.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/google-oauth-client-1.16.0-rc.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/jdo2-api-2.3-eb.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/google-oauth-client-appengine-1.16.0-rc.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/google-http-client-1.16.0-rc.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/google-api-client-1.16.0-rc.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/google-api-services-youtube-v3-rev70-1.16.0-rc-javadoc.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/jsr305-1.3.9.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/google-api-client-appengine-1.16.0-rc.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/google-api-client-java6-1.16.0-rc.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/xpp3-1.1.4c.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/google-http-client-jackson2-1.16.0-rc.jar /Users/Andrew/AndroidStudioProjects/ApiTest2Project/ApiTest2/libs/youtube/libs/google-api-client-jackson2-1.16.0-rc.jar
Error Code:
1
Output:
trouble processing "javax/transaction/HeuristicCommitException.class":
Ill-advised or mistaken usage of a core class (java.* or javax.*)
when not building a core library.
This is often due to inadvertently including a core library file
in your application's project, when using an IDE (such as
Eclipse). If you are sure you're not intentionally defining a
core class, then this is the most likely explanation of what's
going on.
However, you might actually be trying to define a class in a core
namespace, the source of which you may have taken, for example,
from a non-Android virtual machine project. This will most
assuredly not work. At a minimum, it jeopardizes the
compatibility of your app with future versions of the platform.
It is also often of questionable legality.
If you really intend to build a core library -- which is only
appropriate as part of creating a full virtual machine
distribution, as opposed to compiling an application -- then use
the "--core-library" option to suppress this error message.
If you go ahead and use "--core-library" but are in fact
building an application, then be forewarned that your application
will still fail to build or run, at some point. Please be
prepared for angry customers who find, for example, that your
application ceases to function once they upgrade their operating
system. You will be to blame for this problem.
If you are legitimately using some code that happens to be in a
core package, then the easiest safe alternative you have is to
repackage that code. That is, move the classes in question into
your own package namespace. This means that they will never be in
conflict with core system classes. JarJar is a tool that may help
you in this endeavor. If you find that you cannot do this, then
that is an indication that the path you are on will ultimately
lead to pain, suffering, grief, and lamentation.
1 error; aborting
And i am not sure why this is happening. I am sure I am doing something wrong, but I havent found anywhere online where i shows how to do this exactly and through all my tinkering i havent gotten it to woerk.
Any help
Anyone have any ideas? Over 100 views and no replies
Hi,
although I haven't face the same problem, I think I can analyze your problem.
It's because dependencies in your gradle.build
You can't declare 2 "compile"(s) statement like what you've done.
Code:
compile fileTree(dir: 'libs/youtube', include: '*.jar')
compile fileTree(dir: 'libs/youtube/libs', include: '*.jar')
That's wrong, though I don't know how to solve that given that I'm still learning about it.
I thought that these links can help you solve it:
- http://www.gradle.org/docs/current/userguide/artifact_dependencies_tutorial.html
- http://www.gradle.org/docs/current/userguide/dependency_management.html
JoshieGeek said:
Hi,
although I haven't face the same problem, I think I can analyze your problem.
It's because dependencies in your gradle.build
You can't declare 2 "compile"(s) statement like what you've done.
Code:
compile fileTree(dir: 'libs/youtube', include: '*.jar')
compile fileTree(dir: 'libs/youtube/libs', include: '*.jar')
That's wrong, though I don't know how to solve that given that I'm still learning about it.
I thought that these links can help you solve it:
- http://www.gradle.org/docs/current/userguide/artifact_dependencies_tutorial.html
- http://www.gradle.org/docs/current/userguide/dependency_management.html
Click to expand...
Click to collapse
curious if either one of you figured it out.
If you are trying to use youtube api add the following line to the gradle build.
Code:
compile 'com.google.apis:google-api-services-youtube:v3-rev107-1.18.0-rc'
You dont need to download and copy the youtube project into your project.

[UTILITY][APP][WINDOWS] AndroidFileUtils | Grab the Logs you need!

This is my first Windows App written in Visual C#
Pre-req's: You will need .NET 4.5 installed to work
ADB not needed, comes packaged with AndroidLib.dll <- Embedded in application (thanks to regaw_leinad)
Does not work with Windows XP or lower
This app is for Windows that will quickly grab a:
-Logcat log : Verbose(default), Debug, Info, Warning, Error, Fatal, Silent
-dmesg log
-last_kmsg log
To use this App effectively, you will need to grab the log AFTER the problem has occured!
Also will copy to your clipboard so you can just paste it to your favorite site or file!
Nothing fancy or elegant about this but it gets the job done! Help out our devs by getting them the Logs they need!
Credit also goes to @regaw_leinad for the AndroidLib.dll
Feedback is needed as this is my first Windows application!
Also, if anybody can come up with a better name for this app, I will gladly change it!
Credit goes to [insert xda-member handle here] for renaming this app to "[insert new name of application]"
Downloads can be found here: http://forum.xda-developers.com/devdb/project/?id=1544#downloads
================================================
Code:
v1306
+Kills all threads if any are running upon exit, small other optimizations.
v1305:
+Fixed two small bugs that caused crashes.
v1300:
+Another overhaul in code, thanks again to regaw_leinad for the help (he did 100% of this update)
+AndroidLib.dll is no longer needed ^
+ADB is now properly killed when closing the application ^
v1200:
+Cleaned up code, ui, added a logcat filtering option { Verbose, Debug, Info, Warning, Error, Fatal, Silent }
v1100:
+Added save log feature, changed up the UI a tiny bit
v1004:
+Major overhaul to code, now speedier! (thanks to regaw_leinad for the help)
v1003:
+Updated App again: Now should support ANY device :)
v1002:
+Cleaned up code, more aesthetics !
v1001:
+New Release, Cleaned up some things and added some device info !
v1000:
+Initial Release
XDA:DevDB Information
[Windows] AndroidFileUtils | Grab the Logs you need!, a Tool/Utility for the Android General
Contributors
.torrented, http://forum.xda-developers.com/member.php?u=3766545, regaw_leinad
Version Information
Status: Stable
Current Stable Version: AFU - v1305
Created 2013-11-12
Last Updated 2013-11-12

Omni for MSM8974

Hello I am trying to port the beloved OmniRom to my device which is a KLTE (Samsung Galaxy S5) I have successfully built the ROM from source using kernel and device configs from CM and of course some fixes and cherry picking. The issue I have now is that the ROM will not boot.
I stays at my carrier logo (Samsung) so it does not even let me cat-log. I tried to install the ROM and then restored a backup of Cyanogenmods system directory. It boots to android but all apps forceclose. I did this to see if it was an issue with the boot image and since it can boot to a different system partition I don't believe its a boot.img issue or kernel issue for that matter. Or is it?
Any help getting this to boot would be appreciated. I can provide build logs and my device repo if needed.
gigoo25 said:
Hello I am trying to port the beloved OmniRom to my device which is a KLTE (Samsung Galaxy S5) I have successfully built the ROM from source using kernel and device configs from CM and of course some fixes and cherry picking. The issue I have now is that the ROM will not boot.
I stays at my carrier logo (Samsung) so it does not even let me cat-log. I tried to install the ROM and then restored a backup of Cyanogenmods system directory. It boots to android but all apps forceclose. I did this to see if it was an issue with the boot image and since it can boot to a different system partition I don't believe its a boot.img issue or kernel issue for that matter. Or is it?
Any help getting this to boot would be appreciated. I can provide build logs and my device repo if needed.
Click to expand...
Click to collapse
MSM8974 is our first CAF chipset we're working on supporting.
I'd suggest looking at the Oppo find7/msm8974-common repos as nearly all initial CAF 8974 work is being done on the Find7.
you need android-5.1-caf branches for frameworks/av and frameworks/native for a CAF device until I finish the merge effort
Entropy512 said:
MSM8974 is our first CAF chipset we're working on supporting.
I'd suggest looking at the Oppo find7/msm8974-common repos as nearly all initial CAF 8974 work is being done on the Find7.
you need android-5.1-caf branches for frameworks/av and frameworks/native for a CAF device until I finish the merge effort
Click to expand...
Click to collapse
Thank you! That explains a lot. Maybe you can help me again? I keep coming across building with legacy opposed to CAF and to change it in the configs... What configs are they talking about?
Sent from my SM-G900T using XDA Free mobile app
gigoo25 said:
Thank you! That explains a lot. Maybe you can help me again? I keep coming across building with legacy opposed to CAF and to change it in the configs... What configs are they talking about?
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
You mean AOSP HALs? It's pretty rare for a CAF device to work with vanilla AOSP HALs.
It's the various QCOM_blah_VARIANT flags - 8974s are caf-bfam
Entropy512 said:
You mean AOSP HALs? It's pretty rare for a CAF device to work with vanilla AOSP HALs.
It's the various QCOM_blah_VARIANT flags - 8974s are caf-bfam
Click to expand...
Click to collapse
Updated my repo to 5.1 source but still getting errors. Here is the device configs that I am using. I am getting the same errors throughout.
First error was
Code:
frameworks/base/core/jni/android_view_Surface.cpp:206:14: error: 'class android::Surface' has no member named 'setDirtyRect'
surface->setDirtyRect(&rect);
Which I solved by cherry-picking THIS
Next I get an error that msmcal-hwdep.h is not found not sure how to fix this yet...
I recreated my devices config from scratch and uploaded it to git... Maybe you can take a look when you have some free time? It would mean alot! https://github.com/Gigoo25/android_device_samsung_klte
gigoo25 said:
Updated my repo to 5.1 source but still getting errors. Here is the device configs that I am using. I am getting the same errors throughout.
First error was
Code:
frameworks/base/core/jni/android_view_Surface.cpp:206:14: error: 'class android::Surface' has no member named 'setDirtyRect'
surface->setDirtyRect(&rect);
Which I solved by cherry-picking THIS
Next I get an error that msmcal-hwdep.h is not found not sure how to fix this yet...
I recreated my devices config from scratch and uploaded it to git... Maybe you can take a look when you have some free time? It would mean alot! https://github.com/Gigoo25/android_device_samsung_klte
Click to expand...
Click to collapse
msmcal_hwdep - look at the stiff in your kernel source under include/ - all of that header-y stuff in some of the Kconfigs
You shouldn't be cherrypicking that, I'm not sure why Max even put that up. Until I finish the CAF av/native merge, anyone declaring QCOM_HARDWARE should be using the android-5.1-caf branches of av and native
Entropy512 said:
msmcal_hwdep - look at the stiff in your kernel source under include/ - all of that header-y stuff in some of the Kconfigs
You shouldn't be cherrypicking that, I'm not sure why Max even put that up. Until I finish the CAF av/native merge, anyone declaring QCOM_HARDWARE should be using the android-5.1-caf branches of av and native
Click to expand...
Click to collapse
Awesome! alright will look into that
Sent from my SM-G900T using XDA Free mobile app
Entropy512 said:
msmcal_hwdep - look at the stiff in your kernel source under include/ - all of that header-y stuff in some of the Kconfigs
You shouldn't be cherrypicking that, I'm not sure why Max even put that up. Until I finish the CAF av/native merge, anyone declaring QCOM_HARDWARE should be using the android-5.1-caf branches of av and native
Click to expand...
Click to collapse
Having issues compiling the camera I get the error
Code:
device/samsung/klte/camera/CameraWrapper.cpp: In function 'char* camera_fixup_setparams(int, const char*)':
device/samsung/klte/camera/CameraWrapper.cpp:161:20: error: 'KEY_DIS' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_DIS, android::CameraParameters::DIS_DISABLE);
^
device/samsung/klte/camera/CameraWrapper.cpp:161:56: error: 'DIS_DISABLE' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_DIS, android::CameraParameters::DIS_DISABLE);
^
device/samsung/klte/camera/CameraWrapper.cpp:162:20: error: 'KEY_ZSL' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_ZSL, android::CameraParameters::ZSL_OFF);
^
device/samsung/klte/camera/CameraWrapper.cpp:162:56: error: 'ZSL_OFF' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_ZSL, android::CameraParameters::ZSL_OFF);
^
device/samsung/klte/camera/CameraWrapper.cpp:164:20: error: 'KEY_ZSL' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_ZSL, android::CameraParameters::ZSL_ON);
^
device/samsung/klte/camera/CameraWrapper.cpp:164:56: error: 'ZSL_ON' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_ZSL, android::CameraParameters::ZSL_ON);
^
make: *** [/home/rob/android/omni51/out/target/product/klte/obj/SHARED_LIBRARIES/camera.msm8974_intermediates/CameraWrapper.o] Error 1
make: *** Waiting for unfinished jobs...
Is this a framework issue?
gigoo25 said:
Having issues compiling the camera I get the error
Code:
device/samsung/klte/camera/CameraWrapper.cpp: In function 'char* camera_fixup_setparams(int, const char*)':
device/samsung/klte/camera/CameraWrapper.cpp:161:20: error: 'KEY_DIS' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_DIS, android::CameraParameters::DIS_DISABLE);
^
device/samsung/klte/camera/CameraWrapper.cpp:161:56: error: 'DIS_DISABLE' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_DIS, android::CameraParameters::DIS_DISABLE);
^
device/samsung/klte/camera/CameraWrapper.cpp:162:20: error: 'KEY_ZSL' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_ZSL, android::CameraParameters::ZSL_OFF);
^
device/samsung/klte/camera/CameraWrapper.cpp:162:56: error: 'ZSL_OFF' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_ZSL, android::CameraParameters::ZSL_OFF);
^
device/samsung/klte/camera/CameraWrapper.cpp:164:20: error: 'KEY_ZSL' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_ZSL, android::CameraParameters::ZSL_ON);
^
device/samsung/klte/camera/CameraWrapper.cpp:164:56: error: 'ZSL_ON' is not a member of 'android::CameraParameters'
params.set(android::CameraParameters::KEY_ZSL, android::CameraParameters::ZSL_ON);
^
make: *** [/home/rob/android/omni51/out/target/product/klte/obj/SHARED_LIBRARIES/camera.msm8974_intermediates/CameraWrapper.o] Error 1
make: *** Waiting for unfinished jobs...
Is this a framework issue?
Click to expand...
Click to collapse
Looks like maybe some missing Samsung patches
Entropy512 said:
Looks like maybe some missing Samsung patches
Click to expand...
Click to collapse
I appreciate all the help you have been giving me in trying to port Omni to the KLTE! I could not have done it without you!
I ended up having a booting and working build when I removed the camera and RIL
RIL gives me an error of
Code:
frameworks/opt/telephony/../../../device/samsung/klte/ril/telephony/java/com/android/internal/telephony/KlteRIL.java:282: error: no suitable constructor found for SignalStrength(int,int,int,int,int,int,int,int,int,int,int,int,int,boolean)
return new SignalStrength(gsmSignalStrength, gsmBitErrorRate, cdmaDbm, cdmaEcio, evdoDbm,
^
constructor SignalStrength.SignalStrength(Parcel) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength(SignalStrength) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength(int,int,int,int,int,int,int,boolean) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength(int,int,int,int,int,int,int,int,int,int,int,int,boolean) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength(boolean) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength() is not applicable
(actual and formal argument lists differ in length)
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
It should be a frameworks/opt/telephony issue correct? Except it doesn't display the full file path?
gigoo25 said:
I appreciate all the help you have been giving me in trying to port Omni to the KLTE! I could not have done it without you!
I ended up having a booting and working build when I removed the camera and RIL
RIL gives me an error of
Code:
frameworks/opt/telephony/../../../device/samsung/klte/ril/telephony/java/com/android/internal/telephony/KlteRIL.java:282: error: no suitable constructor found for SignalStrength(int,int,int,int,int,int,int,int,int,int,int,int,int,boolean)
return new SignalStrength(gsmSignalStrength, gsmBitErrorRate, cdmaDbm, cdmaEcio, evdoDbm,
^
constructor SignalStrength.SignalStrength(Parcel) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength(SignalStrength) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength(int,int,int,int,int,int,int,boolean) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength(int,int,int,int,int,int,int,int,int,int,int,int,boolean) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength(boolean) is not applicable
(actual and formal argument lists differ in length)
constructor SignalStrength.SignalStrength() is not applicable
(actual and formal argument lists differ in length)
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
It should be a frameworks/opt/telephony issue correct? Except it doesn't display the full file path?
Click to expand...
Click to collapse
It looks like the KLTE actually specifies its own RIL subclass (interesting trick, I've never seen that before) and that subclass is depending on something in frameworks/opt/tel that Omni doesn't have.
Either find the missing patch in f/opt/tel or figure out how to adapt KlteRIL.java
Entropy512 said:
It looks like the KLTE actually specifies its own RIL subclass (interesting trick, I've never seen that before) and that subclass is depending on something in frameworks/opt/tel that Omni doesn't have.
Either find the missing patch in f/opt/tel or figure out how to adapt KlteRIL.java
Click to expand...
Click to collapse
I seem to have gotten everything working fine besides the camera. The app and libraries compile fine but when the rom boots I cannot see it in the app drawer. When I try to launch it through the lockscreen it just force closes. Not sure what could be causing the problem? All the permissions seem to be checking out, and messing with the BoardConfiv and Device make files has not seemed to help. Any suggestions on how to fix this? Could it be a framework issue?
gigoo25 said:
I seem to have gotten everything working fine besides the camera. The app and libraries compile fine but when the rom boots I cannot see it in the app drawer. When I try to launch it through the lockscreen it just force closes. Not sure what could be causing the problem? All the permissions seem to be checking out, and messing with the BoardConfiv and Device make files has not seemed to help. Any suggestions on how to fix this? Could it be a framework issue?
Click to expand...
Click to collapse
Look through the logcat for camera errors, especially any errors about missing libraries.
Not appearing in app drawer indicates that Android doesn't think there is a camera present. There are 2349734297320 different things that could cause this - missing camera HAL dependency, kernel/HAL mismatch, many other things.
Entropy512 said:
Look through the logcat for camera errors, especially any errors about missing libraries.
Not appearing in app drawer indicates that Android doesn't think there is a camera present. There are 2349734297320 different things that could cause this - missing camera HAL dependency, kernel/HAL mismatch, many other things.
Click to expand...
Click to collapse
Here is what I found in the logcat
Code:
--------- beginning of crash
[ 06-01 20:08:07.366 3437: 3437 E/AndroidRuntime ]
FATAL EXCEPTION: main
Process: com.android.camera2, PID: 3437
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.camera2/com.android.camera.CameraActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'void com.android.camera.util.PhotoSphereHelper$PanoramaViewHelper.onStart()' on a null object reference
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2325)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2387)
at android.app.ActivityThread.access$800(ActivityThread.java:151)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1303)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5254)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void com.android.camera.util.PhotoSphereHelper$PanoramaViewHelper.onStart()' on a null object reference
at com.android.camera.CameraActivity.onStartTasks(CameraActivity.java:1885)
at com.android.camera.util.QuickActivity.onStart(QuickActivity.java:111)
at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1236)
at android.app.Activity.performStart(Activity.java:6006)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2288)
... 10 more
gigoo25 said:
Here is what I found in the logcat
Code:
--------- beginning of crash
[ 06-01 20:08:07.366 3437: 3437 E/AndroidRuntime ]
FATAL EXCEPTION: main
Process: com.android.camera2, PID: 3437
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.camera2/com.android.camera.CameraActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'void com.android.camera.util.PhotoSphereHelper$PanoramaViewHelper.onStart()' on a null object reference
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2325)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2387)
at android.app.ActivityThread.access$800(ActivityThread.java:151)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1303)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5254)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void com.android.camera.util.PhotoSphereHelper$PanoramaViewHelper.onStart()' on a null object reference
at com.android.camera.CameraActivity.onStartTasks(CameraActivity.java:1885)
at com.android.camera.util.QuickActivity.onStart(QuickActivity.java:111)
at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1236)
at android.app.Activity.performStart(Activity.java:6006)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2288)
... 10 more
Click to expand...
Click to collapse
Pretty much - if you can't figure out what is wrong from reading a logcat, most likely, you can't figure out what parts of the logcat are relevant and which are not.
That excerpt basically tells me nothing.
I assume that was from trying to forcefully start the camera with no camera actually present as far as Android was concerned. That's a symptom, not the root cause of the problem. Based on what you've described, the root cause of the problem will likely be visible even if no attempt is made to use the camera.
Entropy512 said:
Pretty much - if you can't figure out what is wrong from reading a logcat, most likely, you can't figure out what parts of the logcat are relevant and which are not.
That excerpt basically tells me nothing.
I assume that was from trying to forcefully start the camera with no camera actually present as far as Android was concerned. That's a symptom, not the root cause of the problem. Based on what you've described, the root cause of the problem will likely be visible even if no attempt is made to use the camera.
Click to expand...
Click to collapse
I've been messing around with the device configurations and logcats. I I think I have found the culprit for my camera not working. It shows that it loads the module but then fails to open it? Is this a CameraWrapper issue? Still trying to fix the camera so I can use this as a daily build but I have limited experience as a developer.
EDIT: Also the camera shows up on first boot but then disappears and says that the application is not installed. I'm trying to logcat it but not sure how to do that on the first boot without allowing my PC
EDIT2: From the looks of it searching the web it seems to be an issue with frameworks/av/camera/CameraParameters.cpp & frameworks/av/camera/include/CameraParameters.h
Code:
I/CameraService( 381): CameraService started (pid=381)
I/CameraService( 381): Loaded "MSM8974 Camera Wrapper" camera module
I/CameraWrapper( 381): camera_get_number_of_cameras
I/CameraWrapper( 381): check_vendor_module
I/PackageManager( 741): /system/priv-app/MmsService changed; collecting certs
I/PackageManager( 741): /system/priv-app/OmniSwitch changed; collecting certs
E/HAL ( 381): load: module=/system/lib/hw/camera.vendor.msm8974.so
E/HAL ( 381): dlopen failed: cannot locate symbol "_ZN7android16CameraParameters25KEY_DYNAMIC_RANGE_CONTROLE" referenced by "camera.vendor.msm8974.so"...
E/CameraWrapper( 381): failed to open vendor camera module
gigoo25 said:
I've been messing around with the device configurations and logcats. I I think I have found the culprit for my camera not working. It shows that it loads the module but then fails to open it? Is this a CameraWrapper issue? Still trying to fix the camera so I can use this as a daily build but I have limited experience as a developer.
EDIT: Also the camera shows up on first boot but then disappears and says that the application is not installed. I'm trying to logcat it but not sure how to do that on the first boot without allowing my PC
EDIT2: From the looks of it searching the web it seems to be an issue with frameworks/av/camera/CameraParameters.cpp & frameworks/av/camera/include/CameraParameters.h
Code:
I/CameraService( 381): CameraService started (pid=381)
I/CameraService( 381): Loaded "MSM8974 Camera Wrapper" camera module
I/CameraWrapper( 381): camera_get_number_of_cameras
I/CameraWrapper( 381): check_vendor_module
I/PackageManager( 741): /system/priv-app/MmsService changed; collecting certs
I/PackageManager( 741): /system/priv-app/OmniSwitch changed; collecting certs
E/HAL ( 381): load: module=/system/lib/hw/camera.vendor.msm8974.so
E/HAL ( 381): dlopen failed: cannot locate symbol "_ZN7android16CameraParameters25KEY_DYNAMIC_RANGE_CONTROLE" referenced by "camera.vendor.msm8974.so"...
E/CameraWrapper( 381): failed to open vendor camera module
Click to expand...
Click to collapse
Looks like a patch for CameraParameters needed by your device is missing since no one has tried to bring that device up before, or hasn't tried bringing it up with 5.x
Since it's a Qualcomm-based device and likely using CAF repos, you'll probably have to patch frameworks/av-caf and not frameworks/av - see https://lists.omnirom.org/pipermail/maintainers/2015-June/000101.html for details (we need to add this info to the wiki...)
Entropy512 said:
Looks like a patch for CameraParameters needed by your device is missing since no one has tried to bring that device up before, or hasn't tried bringing it up with 5.x
Since it's a Qualcomm-based device and likely using CAF repos, you'll probably have to patch frameworks/av-caf and not frameworks/av - see https://lists.omnirom.org/pipermail/maintainers/2015-June/000101.html for details (we need to add this info to the wiki...)
Click to expand...
Click to collapse
So I would have to split av into two folders then applying I believe THIS patch to av-caf in order to compile it properly?
Also does native-caf branch still have to be merged before compiling?
gigoo25 said:
So I would have to split av into two folders then applying I believe THIS patch to av-caf in order to compile it properly?
Also does native-caf branch still have to be merged before compiling?
Click to expand...
Click to collapse
Well, the splitting of av is already done. Native is already merged with ifdefs (it didn't require nearly as much ifdefing as av, so we have a "unified" CAF+AOSP native). The only thing that is needed for device maintainers is adding av-caf to omni.dependencies - see the maintainers list post I linked to, or look at the Oppo find7 history.
So once you're pulling in av-caf via omni.dependencies, you should be able to apply that patch to av-caf and then submit it to Gerrit for review.
You might want to start idling in IRC, #omni is where most device maintainers are (in fact, all maintainers for supported devices idle their routinely, it's now a requirement for maintainers to routinely idle in IRC so they can see what's going on/people can ping them with questions.)
Entropy512 said:
Well, the splitting of av is already done. Native is already merged with ifdefs (it didn't require nearly as much ifdefing as av, so we have a "unified" CAF+AOSP native). The only thing that is needed for device maintainers is adding av-caf to omni.dependencies - see the maintainers list post I linked to, or look at the Oppo find7 history.
So once you're pulling in av-caf via omni.dependencies, you should be able to apply that patch to av-caf and then submit it to Gerrit for review.
You might want to start idling in IRC, #omni is where most device maintainers are (in fact, all maintainers for supported devices idle their routinely, it's now a requirement for maintainers to routinely idle in IRC so they can see what's going on/people can ping them with questions.)
Click to expand...
Click to collapse
Turns out I might of fixed the problem. Instead of messing with frameworks/av I can just override it with a file inside include/camera? Looking back at the Cyanogenmod repo for my device THIS is present while in my source it is not.
Compiling now. Will post results after.

VRTV Free for Cardboard 3.0 open beta

Hi XDA! I'm the developer of VRTV, a video player for Cardboard. I'm running an open beta of my latest release, and I was hoping I could get some feedback here. Hope this doesn't count as me spamming. The app is free, with a banner ad, but there is a paid version available.
Anyway, here's a small description of the news in 3.0 beta:
Big news:
Uses libVLC backend, with support for replacing the decoding library.
Regular 2D video player UI.
Configurable bluetooth controls.
Smaller news:
Support for 220/270 degree panoramas.
Audio track selection.
Guess video config from filename.
Setting for phones/headset in reverse landscape configuration.
Like MX Player, I've disabled support for DTS/AC3, but you can build and load your own libvlcjni.so from the libvlc source code if you are not under the jurisdiction of software patents. To get the correct version I recommend using the same source as I used to build the version that's distributed with the app. Link below.
The other big new thing in 3.0 is that I've implemented a simple "normal" video player UI, so ideally you would get by with VRTV for all your videos and can set it as the default video player. Something that's been bugging me with VRTV for a while (and with most other players I believe). Uncheck "VR Player" to use the regular player.
I use the beta functionality in the Play Store, so to join, click the appropriate link below to join the beta with your Google account, then find VRTV in the Play Store to update to the beta.
https://play.google.com/apps/testing/se.chai.vrtv.free
https://play.google.com/apps/testing/se.chai.vrtv (requires buying/owning the paid version)
Follow the link below to get the source code for libvlc used in VRTV. Let me know if you would be willing to help me test loading a self-built library!
https://github.com/svenhenrik/vlc_vrtv_1.7.x
Any feedback is valuable, and if you have the ability to provide logs for crashers I will love you forever! Especially Nougat seems to be a bit troublesome, and I don't have a device to test with myself.
Hi Sven,
I bought the pro app in the Play store and I am willing to build my own libvlcjni.so. From all the players I have tried so far your app had the best results for non-VR 3D-movies by far.
I will install an Ubuntu on an usb stick tonight and have a couple of questions since I am not familiar with developing in Linux.
- Will it compile correctly under 64-it linux?
- What settings do I have to change to enable AC3/DTS?
- Do I need the Android SDK or just the libraries mentioned at https://wiki.videolan.org/AndroidCompile/?
So I will just do a
sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install zlib1g:i386 libstdc++6:i386 libc6:i386
sudo apt-get install automake ant autopoint cmake build-essential libtool \ patch pkg-config protobuf-compiler ragel subversion unzip git
git clone https://github.com/svenhenrik/vlc_vrtv_1.7.x
./compile.sh --release -l -a armeabi-v7a
Copy the new libvlcjni.so to data/app/se.chai.vrtv-1/lib
?
Thank you for your help.
OK, I ran into a couple of issues (some URLs where additional packages were being fetched were dead, you need to use NDK 10e because newer versions are missing the required release.txt, you need to install Oracle Java and set the JAVA_HOME variable).
ColinMacLaren said:
OK, I ran into a couple of issues (some URLs where additional packages were being fetched were dead, you need to use NDK 10e because newer versions are missing the required release.txt, you need to install Oracle Java and set the JAVA_HOME variable).
Click to expand...
Click to collapse
Hi, so sorry for not checking in here sooner to help. Did you manage to get it all to compile? Let me know if you have more questions, I'll check a little more often
I'll update the patch later today with the new contrib links. I really should upgrade VLC since they released a new version recently, I used the one that was released when I started adding support.
I'll add the part about needing NDK r10e to the instructions, thanks!
ColinMacLaren said:
- What settings do I have to change to enable AC3/DTS?
Click to expand...
Click to collapse
Missed this part. You basically want to revert my changes relating to the a52 library. These are the modifications I've made:
- Make sure to use the last tested SHA of VLC instead of the latest checkout, to get some stability in what VRTV is using.
- Disable GPL, and fix building without GPL libraries (all changes relating to -lmad and -lpostproc
- Disable a52, in both the vlc build script and in the ffmpeg config.
The latter two are mixed and spread over two commits unfortunately so you can't just revert them.
https://github.com/svenhenrik/vlc_vrtv_1.7.x/commit/39bfc574661484f3d6e6f4371c1582aec57dbe35
Here you need to remove the --disable-a52 lines and add back the linker flag -la52 that was removed.
https://github.com/svenhenrik/vlc_vrtv_1.7.x/commit/961142382010ef3bb74028163cd66e11244d139a
Remove the --disable-decoder lines the patch added to vlc/contrib/src/ffmpeg/rules.mak
I think I might have had to add --enable-a52 to the compile script to get it to pick up the changes when rebuilding, try that if it doesn't download the a52 contrib lib or doesn't link.
By the way, the latest beta supports reading zip:ed libvlcjni.so files (make sure it's the only file in the archive).
Also gave this a shot. The developer still hasn't updated the source with new links to libraries, but I managed to get it to build and load after some tinkering.
If anyone else wants AC3/DTS support but can't build it themselves, PM me, new account so I can't post links.
Where do I put the zipped library and what are the naming restrictions?
ColinMacLaren said:
Where do I put the zipped library and what are the naming restrictions?
Click to expand...
Click to collapse
Haven't tried zip, but if you pick "load library" in the menu in VRTV you get a file browser so just put the file anywhere on the phone.
Instructions
A paid customer and also joined the Beta testing team.. Want to say thank you for this great Video player. Took me a while to land on it after trying so many VR players.
Two questions.
Are there better instructions anywhere?
1.) How / where to find Codec's for this? Trying to play .MKV files (no audio)
UPDATE: used VLC codec, thanks..
2.) Is there a way to have the filename syntax , pre-configure settings on video type, VR DOME etc.., so it starts without having the non-3D menu first ? Does this make sense?
​Using;
Note 5 -Samsung Gear VR​, streaming videos from Local NAS
sounds cool. will give it a try
Cool. Will give it a try
[WIP] Docker Build Steps
This isn't working but I thought I'd post anyone, I will edit when I figure out what I'm missing.
If you already have a build environment setup these steps may or may not be helpful, but here's what I did to build the library file with docker:
Code:
# Grab a docker image that's has the NDK and SDK install for you
docker pull dbndev/android-ndk-r12b-build-samples
# Grab the source for building VRTV's VLC Lib, and checkout the version before any changes were made
git clone https://github.com/svenhenrik/vlc_vrtv_1.7.x
cd vlc_vrtv_1.7.x
git checkout 58181046e79112450a3362df7195cc35dd332096
# EDIT compile.sh, otherwise gradle don't download, the url changed, and redirect isn't caught. Note change xxxx to http, I can't post links with my account
# ORG: GRADLE_URL=xxxx://services.gradle.org/distributions/gradle-${GRADLE_VERSION}-all.zip
# NEW: GRADLE_URL=xxxx://downloads.gradle.org/distributions/gradle-${GRADLE_VERSION}-all.zip
docker run -it --rm -v $(pwd):/build_vlc -w /build_vlc dbndev/android-ndk-r12b-build-samples bash
# Install needed tools and setup the environment for building
apt-get update
apt-get install zlib1g:i386 libstdc++6:i386 libc6:i386
apt-get install automake ant autopoint cmake build-essential libtool patch pkg-config protobuf-compiler ragel subversion unzip git
export ANDROID_SDK=/opt/android-sdk-linux
export ANDROID_NDK=/opt/android-ndk-r12b
echo "r10 (64-bit)" > $ANDROID_NDK/RELEASE.TXT
./compile.sh --release -l -a armeabi-v7a
exit
There should now be a libvlcjni.so around xKB in the root of the vlc_vrtv_1.7.x directory, copy to android and enjoy audio!
Here's the error I'm having now, it looks like I'm trying to build a 32bit library on a 64bit OS, and looks like I need to set some other envs to get past this.
Code:
configure: error: in `/build_vlc/vlc/contrib/contrib-android-arm-linux-androideabi/fribidi':
configure: error: C compiler cannot create executables
See `config.log' for more details
../../contrib/src/fribidi/rules.mak:26: recipe for target '.fribidi' failed
make: *** [.fribidi] Error 77
contribs: make failed
Getting the same thing on mac when trying the following. Hope someone know's how to fix this issue.
Code:
------ NATIVE MAC ------
Download Android studio
Configure / SDK Manager / SDK Tools / NDK
Open the vlc_vrtv_1.7.x folder (maybe not needed who knows...)
echo "r10 (64-bit)" > $HOME/Library/Android/sdk/ndk-bundle/RELEASE.TXT
brew install automake ant cmake libtool patchutils pkg-config protobuf ragel subversion
ANDROID_SDK=$HOME/Library/Android/sdk ANDROID_NDK=$HOME/Library/Android/sdk/ndk-bundle ./compile.sh --release -l -a armeabi-v7a
Hi.
Also using the paid version and I really like the app, it's the best yet!
Two things I'd like to see and it would be even better:
1. support for web streams. Youtube, vimeo, etc.
2. automatic switch off for locked view when browsing your videos in app. It's impossible to click on the X when the image follows your head.
- Mik
Version 3.2 beta / vc61
Not sure what happened since last update, but the back button does not exit from VRTV back to anymore. The only way to exit player is through VR mode and clicking on the small X on top left side.
Also, Gear VR controls don't seem to work anymore.
Also there is a serious drift now.
Future function; a way to save settings or backup settings. I lost my config of my gamepad controls and can't get them back.
---------- Post added at 11:50 AM ---------- Previous post was at 11:37 AM ----------
ColinMacLaren said:
Hi Sven,
I bought the pro app in the Play store and I am willing to build my own libvlcjni.so. From all the players I have tried so far your app had the best results for non-VR 3D-movies by far.
I will install an Ubuntu on an usb stick tonight and have a couple of questions since I am not familiar with developing in Linux.
- Will it compile correctly under 64-it linux?
Click to expand...
Click to collapse
An actual 64bit Android support would be cool, not sure if it would be needed if Hardware support works... just an idea that was triggered from above.
Hi. I am just a noob in this, but please help me. I love VRTV player, but I can't
in VR mode in cinema choose another video to play. Have to pull off my phone, go to another movie tapping it, then pull phone back and watch. very uncomfortable.
Wilsonb said:
A paid customer and also joined the Beta testing team.. Want to say thank you for this great Video player. Took me a while to land on it after trying so many VR players.
Two questions.
Are there better instructions anywhere?
1.) How / where to find Codec's for this? Trying to play .MKV files (no audio)
UPDATE: used VLC codec, thanks..
2.) Is there a way to have the filename syntax , pre-configure settings on video type, VR DOME etc.., so it starts without having the non-3D menu first ? Does this make sense?
​Using;
Note 5 -Samsung Gear VR​, streaming videos from Local NAS
Click to expand...
Click to collapse
Hi, can you explain how did you install VLC coded? Thanks.
--- deleted by user ---
Reason. This has been answered in the very first post of this thread.
I have a nexus 5X and I can't find a good setup to have a quality like in another app.
Trying to play with shader and opengl 3.0 or Vertex hq, but I can't reproduce a good image quality.
What do you suggest ?
Envoyé de mon Nexus 5X en utilisant Tapatalk
Could you revert back the exit behavior as it was 4-5 revisions ago? If it was launched using a File Manager, then backing out brought it back the the app that launched it, instead of now it exits to the launcher.
Hope this make sense. I was able to select movies while closing one eye using my file manager.
This would be important at least until SMB authentication is working.
Thanks
Wilsonb said:
Could you revert back the exit behavior as it was 4-5 revisions ago? If it was launched using a File Manager, then backing out brought it back the the app that launched it, instead of now it exits to the launcher.
Hope this make sense. I was able to select movies while closing one eye using my file manager.
This would be important at least until SMB authentication is working.
Thanks
Click to expand...
Click to collapse
What is your rendering settings plz ?
Envoyé de mon ONEPLUS A5000 en utilisant Tapatalk

Categories

Resources