Database Develop

[Q] Constantly receiving com.google.process.location and Google Play has stopped

After every reboot I receive the following messages
Code:
com.google.process.location
Code:
Google Play services has stopped
I am running a Samsung Galaxy S5 Active (G870AuCU1ANE4) - rooted with stock ROM, this all just started a week or two ago, and it happens randomly during charging as well. I was reading this thread http://forum.xda-developers.com/galaxy-s3/help/how-to-fix-unfortunately-process-com-t2410896/page4 related to the S3, but no luck with those recommendations, and it was for a different error message and different phone, hence this thread. Any assistance would be appreciated.

DrSeussFreak said:
After every reboot I receive the following messages
Code:
com.google.process.location
Code:
Google Play services has stopped
I am running a Samsung Galaxy S5 Active (G870AuCU1ANE4) - rooted with stock ROM, this all just started a week or two ago, and it happens randomly during charging as well. I was reading this thread http://forum.xda-developers.com/galaxy-s3/help/how-to-fix-unfortunately-process-com-t2410896/page4 related to the S3, but no luck with those recommendations, and it was for a different error message and different phone, hence this thread. Any assistance would be appreciated.
Click to expand...
Click to collapse
did you freeze/delete any system apps? that can cause these type of issues
if you have a root browser installed go to /data/log there should be a set of error logs zipped into a tar.gz file copy that out to your sdcard extract it and search the contents for fatal errors or missing files that should tell you what the root cause is.

cstayton said:
did you freeze/delete any system apps? that can cause these type of issues
if you have a root browser installed go to /data/log there should be a set of error logs zipped into a tar.gz file copy that out to your sdcard extract it and search the contents for fatal errors or missing files that should tell you what the root cause is.
Click to expand...
Click to collapse
So I have froze multiple AT&T applications, but nothing recently, and I had reset app preferences (which unfroze everything) and the issue still existed.
What I found in "dumpstate_app_error.txt" was
Code:
10-22 18:33:33.636 30602 30619 D skia : GFXPNG PNG bitmap created width:11 height:12 bitmap id is 270
10-22 18:33:33.636 30602 30619 D skia : GFXPNG PNG bitmap created width:3 height:69 bitmap id is 271
10-22 18:33:33.636 30602 30619 D skia : GFXPNG PNG bitmap created width:64 height:64 bitmap id is 272
10-22 18:33:33.636 30602 30619 D skia : GFXPNG PNG bitmap created width:64 height:64 bitmap id is 273
10-22 18:33:33.636 30602 30619 D skia : GFXPNG PNG bitmap created width:64 height:64 bitmap id is 274
10-22 18:33:33.636 30602 30619 D skia : GFXPNG PNG bitmap created width:64 height:64 bitmap id is 275
10-22 18:33:33.636 30602 30619 D skia : GFXPNG PNG bitmap created width:64 height:64 bitmap id is 276
10-22 18:33:33.636 30602 30619 D skia : GFXPNG PNG bitmap created width:64 height:64 bitmap id is 277
10-22 18:33:33.636 30602 30619 D skia : GFXPNG PNG bitmap created width:64 height:64 bitmap id is 278
10-22 18:33:33.636 30602 30619 D skia : GFXPNG PNG bitmap created width:64 height:64 bitmap id is 279
10-22 18:33:33.636 30602 30619 D skia : GFXPNG PNG bitmap created width:64 height:64 bitmap id is 280
10-22 18:33:33.636 22940 22940 I dalvikvm: Could not find method android.os.PowerManager.isPowerSaveMode, referenced from method com.google.android.location.n.y.d
10-22 18:33:33.636 22940 22940 W dalvikvm: VFY: unable to resolve virtual method 1458: Landroid/os/PowerManager;.isPowerSaveMode ()Z
10-22 18:33:33.636 22940 22940 D dalvikvm: VFY: replacing opcode 0x6e at 0x000a
10-22 18:33:33.646 30602 30619 D skia : GFXPNG PNG bitmap created width:13 height:64 bitmap id is 281
10-22 18:33:33.646 30602 30619 D skia : GFXPNG PNG bitmap created width:12 height:12 bitmap id is 282
10-22 18:33:33.646 30602 30619 D skia : GFXPNG PNG bitmap created width:32 height:32 bitmap id is 283
10-22 18:33:33.656 893 1879 D EnterpriseDeviceManager: ContainerId: 0
10-22 18:33:33.666 30602 30619 D skia : GFXPNG PNG bitmap created width:16 height:16 bitmap id is 284
10-22 18:33:33.666 30602 30619 D skia : GFXPNG PNG bitmap created width:32 height:32 bitmap id is 285
10-22 18:33:33.676 30602 30620 D skia : GFXPNG PNG bitmap created width:96 height:96 bitmap id is 286
10-22 18:33:33.676 30602 30617 D skia : GFXPNG PNG bitmap created width:16 height:16 bitmap id is 287
10-22 18:33:33.676 893 1000 E LightSensor: RED : 0, GREEN : 0, BLUE : 0, CLEAR : 0, CALCULATED LUX : 0.000000, CCT : 1596.000000, REAL LUX : 0.000000 a_time = 238, gain = 64, ir=0, rp1=1, gp1=0, bp1=0, cp1=0, cpl=3202560
10-22 18:33:33.686 30602 30617 D skia : GFXPNG PNG bitmap created width:32 height:32 bitmap id is 288
10-22 18:33:33.686 30602 30621 D skia : GFXPNG PNG bitmap created width:16 height:16 bitmap id is 289
10-22 18:33:33.686 30602 30621 D skia : GFXPNG PNG bitmap created width:32 height:32 bitmap id is 290
10-22 18:33:33.696 22940 22940 D AndroidRuntime: Shutting down VM
10-22 18:33:33.696 22940 22940 W dalvikvm: threadid=1: thread exiting with uncaught exception (group=0x4178eda0)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: FATAL EXCEPTION: main
10-22 18:33:33.696 22940 22940 E AndroidRuntime: Process: com.google.process.location, PID: 22940
10-22 18:33:33.696 22940 22940 E AndroidRuntime: java.lang.RuntimeException: Unable to bind to service [email protected]388 with Intent { act=com.android.location.service.v3.NetworkLocationProvider pkg=com.google.android.gms }: java.lang.NullPointerException: null result when primitive expected
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at android.app.ActivityThread.handleBindService(ActivityThread.java:2842)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at android.app.ActivityThread.access$2000(ActivityThread.java:173)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1390)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at android.os.Looper.loop(Looper.java:136)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5579)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at java.lang.reflect.Method.invokeNative(Native Method)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at java.lang.reflect.Method.invoke(Method.java:515)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1268)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1084)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at dalvik.system.NativeStart.main(Native Method)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: Caused by: java.lang.NullPointerException: null result when primitive expected
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at com.google.android.location.network.NetworkLocationService.a(Native Method)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at com.google.android.location.network.NetworkLocationService.onBind(SourceFile:55)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at android.app.ActivityThread.handleBindService(ActivityThread.java:2829)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: ... 11 more

DrSeussFreak said:
So I have froze multiple AT&T applications, but nothing recently, and I had reset app preferences (which unfroze everything) and the issue still existed.
What I found in "dumpstate_app_error.txt" was
Code:
10-22 18:33:33.636 30602 30619 D skia : GFXPNG PNG bitmap created width:11 height:12 bitmap id is 270
10-22 18:33:33.636 30602 30619 D skia : GFXPNG PNG bitmap created width:3 height:69 bitmap id is 271
10-22 18:33:33.636 30602 30619 D skia : GFXPNG PNG bitmap created width:64 height:64 bitmap id is 272
10-22 18:33:33.636 30602 30619 D skia : GFXPNG PNG bitmap created width:64 height:64 bitmap id is 273
10-22 18:33:33.636 30602 30619 D skia : GFXPNG PNG bitmap created width:64 height:64 bitmap id is 274
10-22 18:33:33.636 30602 30619 D skia : GFXPNG PNG bitmap created width:64 height:64 bitmap id is 275
10-22 18:33:33.636 30602 30619 D skia : GFXPNG PNG bitmap created width:64 height:64 bitmap id is 276
10-22 18:33:33.636 30602 30619 D skia : GFXPNG PNG bitmap created width:64 height:64 bitmap id is 277
10-22 18:33:33.636 30602 30619 D skia : GFXPNG PNG bitmap created width:64 height:64 bitmap id is 278
10-22 18:33:33.636 30602 30619 D skia : GFXPNG PNG bitmap created width:64 height:64 bitmap id is 279
10-22 18:33:33.636 30602 30619 D skia : GFXPNG PNG bitmap created width:64 height:64 bitmap id is 280
10-22 18:33:33.636 22940 22940 I dalvikvm: Could not find method android.os.PowerManager.isPowerSaveMode, referenced from method com.google.android.location.n.y.d
10-22 18:33:33.636 22940 22940 W dalvikvm: VFY: unable to resolve virtual method 1458: Landroid/os/PowerManager;.isPowerSaveMode ()Z
10-22 18:33:33.636 22940 22940 D dalvikvm: VFY: replacing opcode 0x6e at 0x000a
10-22 18:33:33.646 30602 30619 D skia : GFXPNG PNG bitmap created width:13 height:64 bitmap id is 281
10-22 18:33:33.646 30602 30619 D skia : GFXPNG PNG bitmap created width:12 height:12 bitmap id is 282
10-22 18:33:33.646 30602 30619 D skia : GFXPNG PNG bitmap created width:32 height:32 bitmap id is 283
10-22 18:33:33.656 893 1879 D EnterpriseDeviceManager: ContainerId: 0
10-22 18:33:33.666 30602 30619 D skia : GFXPNG PNG bitmap created width:16 height:16 bitmap id is 284
10-22 18:33:33.666 30602 30619 D skia : GFXPNG PNG bitmap created width:32 height:32 bitmap id is 285
10-22 18:33:33.676 30602 30620 D skia : GFXPNG PNG bitmap created width:96 height:96 bitmap id is 286
10-22 18:33:33.676 30602 30617 D skia : GFXPNG PNG bitmap created width:16 height:16 bitmap id is 287
10-22 18:33:33.676 893 1000 E LightSensor: RED : 0, GREEN : 0, BLUE : 0, CLEAR : 0, CALCULATED LUX : 0.000000, CCT : 1596.000000, REAL LUX : 0.000000 a_time = 238, gain = 64, ir=0, rp1=1, gp1=0, bp1=0, cp1=0, cpl=3202560
10-22 18:33:33.686 30602 30617 D skia : GFXPNG PNG bitmap created width:32 height:32 bitmap id is 288
10-22 18:33:33.686 30602 30621 D skia : GFXPNG PNG bitmap created width:16 height:16 bitmap id is 289
10-22 18:33:33.686 30602 30621 D skia : GFXPNG PNG bitmap created width:32 height:32 bitmap id is 290
10-22 18:33:33.696 22940 22940 D AndroidRuntime: Shutting down VM
10-22 18:33:33.696 22940 22940 W dalvikvm: threadid=1: thread exiting with uncaught exception (group=0x4178eda0)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: FATAL EXCEPTION: main
10-22 18:33:33.696 22940 22940 E AndroidRuntime: Process: com.google.process.location, PID: 22940
10-22 18:33:33.696 22940 22940 E AndroidRuntime: java.lang.RuntimeException: Unable to bind to service [email protected]388 with Intent { act=com.android.location.service.v3.NetworkLocationProvider pkg=com.google.android.gms }: java.lang.NullPointerException: null result when primitive expected
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at android.app.ActivityThread.handleBindService(ActivityThread.java:2842)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at android.app.ActivityThread.access$2000(ActivityThread.java:173)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1390)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at android.os.Looper.loop(Looper.java:136)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5579)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at java.lang.reflect.Method.invokeNative(Native Method)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at java.lang.reflect.Method.invoke(Method.java:515)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1268)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1084)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at dalvik.system.NativeStart.main(Native Method)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: Caused by: java.lang.NullPointerException: null result when primitive expected
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at com.google.android.location.network.NetworkLocationService.a(Native Method)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at com.google.android.location.network.NetworkLocationService.onBind(SourceFile:55)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: at android.app.ActivityThread.handleBindService(ActivityThread.java:2829)
10-22 18:33:33.696 22940 22940 E AndroidRuntime: ... 11 more
Click to expand...
Click to collapse
the two lines from your log below reference the issue at hand, one of two things is happening either the /data/data/<app folder> is missing
or the apps were frozen or deleted. both power saving and location services have more than one call from several system apks as well as user apks. if you have titanium backup and used that to freeze apps try restoring data for the apps that you froze see if that helps, otherwise my next sugestion would be to odin back to stock and start over.
10-22 18:33:33.636 22940 22940 I dalvikvm: Could not find method android.os.PowerManager.isPowerSaveMode, referenced from method com.google.android.location.n.y.d
10-22 18:33:33.696 22940 22940 E AndroidRuntime: java.lang.RuntimeException: Unable to bind to service [email protected]388 with Intent { act=com.android.location.service.v3.NetworkLocationProvider pkg=com.google.android.gms }: java.lang.NullPointerException: null result when primitive expected
Click to expand...
Click to collapse

cstayton said:
the two lines from your log below reference the issue at hand, one of two things is happening either the /data/data/<app folder> is missing
or the apps were frozen or deleted. both power saving and location services have more than one call from several system apks as well as user apks. if you have titanium backup and used that to freeze apps try restoring data for the apps that you froze see if that helps, otherwise my next sugestion would be to odin back to stock and start over.
Click to expand...
Click to collapse
so this issue occured when ALL apps were unfrozen, no apps have ever been deleted, and I am running stock.

So I figured it out, in Xposed, I had a module called "Disable Location Consent" enabled, and as soon as I disabled and rebooted this error went away, enabled rebooted and it came back, disabled and rebooted and it is gone, so I am just waiting for an update, will contact the developer to let them know.
//edit
http://forum.xda-developers.com/xposed/modules/mod-disable-google-location-consent-t2449926/page27 -- looks like I don't need too

DrSeussFreak said:
So I figured it out, in Xposed, I had a module called "Disable Location Consent" enabled, and as soon as I disabled and rebooted this error went away, enabled rebooted and it came back, disabled and rebooted and it is gone, so I am just waiting for an update, will contact the developer to let them know.
//edit
http://forum.xda-developers.com/xposed/modules/mod-disable-google-location-consent-t2449926/page27 -- looks like I don't need too
Click to expand...
Click to collapse
ahhh yes, good ol xPosed framework it can cause wierd issues

cstayton said:
ahhh yes, good ol xPosed framework it can cause wierd issues
Click to expand...
Click to collapse
indeed

cstayton said:
did you freeze/delete any system apps? that can cause these type of issues
if you have a root browser installed go to /data/log there should be a set of error logs zipped into a tar.gz file copy that out to your sdcard extract it and search the contents for fatal errors or missing files that should tell you what the root cause is.
Click to expand...
Click to collapse
I get this when I use the Xposed app to grant the location pop ups. Can't remember the exact name but it is supposed to stop the lil pop up from asking can it say where I am...
You using ANY xposed modules?

DrSeussFreak said:
So I figured it out, in Xposed, I had a module called "Disable Location Consent" enabled, and as soon as I disabled and rebooted this error went away, enabled rebooted and it came back, disabled and rebooted and it is gone, so I am just waiting for an update, will contact the developer to let them know.
//edit
http://forum.xda-developers.com/xposed/modules/mod-disable-google-location-consent-t2449926/page27 -- looks like I don't need too
Click to expand...
Click to collapse
Oh my god... This was driving me NUTS all day :S I can't believe that Xposed module "Disable Location Consent" was causing this problem... THANKS!!!!

xddd00 said:
Oh my god... This was driving me NUTS all day :S I can't believe that Xposed module "Disable Location Consent" was causing this problem... THANKS!!!!
Click to expand...
Click to collapse
Happy this helped somebody else

[ROM][6.0.1_r68][Official] Exodus Android 6 for Onyx

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ABOUT:
Team Exodus brings you EXODUS Rom, coded by professional level developers with additional support from the community, focusing on improved versions of common features and improvements found in the open-source community while bringing new, original improvements and coding with the highest standards.
INSTALLATION:
Take necessary backups
Be rooted w/ a custom recovery
Download EXODUS Rom & Gapps for your device and move them to your phone
Reboot to Recovery
Wipe (full wipe if coming from another Rom)**
Flash the Rom
Flash the Gapps**
Reboot to System
Setup and Reboot System
These directions are not necessary after the first install if you use the Exodus Updater, included in the ROM. It can notify you of updates, download, and install them for you automatically.
**This is automated if coming from a previous Exodus build (Dirty Flashing).
We recommend using our stock (preinstalled) kernel for best results and usage of all features!
SOURCES:
Exodus official build:
http://exodus-developers.net/exodus-6.0/onyx/
GApps:
Any 6.0.x GApps of your choice, we recommend opengapps.org
----- Advanced Developers/Users Section----
Rom source:
https://github.com/TeamExodus
Kernel source:
kernel_oneplus_onyx
Gerrit code review system:
http://review.exodus-developers.net
COMMUNITY
For additional support, info, and updates please join us in the official Google+ community:
https://plus.google.com/communities/106801227383087889476
Crowdin project:
Help us with translating to support your native language!
CREDITS:
Thank you to all the members, contributors, and maintainers on the Exodus Android team.
Please see our source for an unabridged list of contributions, authorship, and cherry-picks.
SUPPORT/DONATION:
If you would like to thank us for our work or help in support server costs you can do so here:
Primedirective (Team Leader / Project Owner / Server hosting)
MartinRo (Project Owner / Server hosting)
Raja. M (Senior Developer / Project Owner)
Alex (Kernel Developer / Project Owner)
Jorge (Developer / Overall Project )
Adrian (Developer / Overall Project )
&
TEAMExodus Team
XDA:DevDB Information
Exodus Android for Onyx, ROM for the OnePlus X
Contributors
Raja.M, TheCrazyLex, Martin_Ro, primedirective, Raja.M
Source Code: http://github.com/TeamExodus
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod, AOSP, CAF Mixed
Version Information
Status: Nightly
Created 2016-03-11
Last Updated 2016-09-24

Reserved

It gives error 07 installing ROM with twrp 3.0. Where I can find opx latest firmware?

Great, best room ever

Wow awesome! Thx for sharing
Am loving Exodus. Used it on many devices. Good feature set combined with great performance and of course layers:thumbup:
Flashed without issues. So far so good
Sent from my One X

mousse04 said:
Great, best room ever
Click to expand...
Click to collapse
Cris7ianO said:
Wow awesome! Thx for sharing
Am loving Exodus. Used it on many devices. Good feature set combined with great performance and of course layers:thumbup:
Flashed without issues. So far so good
Sent from my One X
Click to expand...
Click to collapse
Great to here enjoy exodus android experience !
Sent from my ONE A2003 using XDA Free mobile app

Can you add Screenshots to OP? And what about a bug list?

It's good to see Exodus on onyx. Thanks! Smooth rom so far, most stable layer rom in my opinion and I like it. haha. Only small issues with the model number being unknown and the user profile picture can't be changed.

Thanks for the ROM, very good work. Daily rom for me for sure.
Some questions, remarks however:
I enabled system ui tuner but can't find the menu ...
Would you plan to add network speed in status bar?
Updater doesn't seem to recognize this onyx version.
Keyboard gesture doesn't seem to work ...

Excellent ROM!! I really liked it, installed it as a daily driver.
One bug though... even though I did a clean flash, Uber app for some reason force closes on me... I'll do a logcat when I arrive home.
Sent from my unknown using Tapatalk

Installed it just now and it's running like a charm so no bugs encountered yet.

@Raja.M In the exopdus updater app, onyx is not included in the list. Thus giving message 'unsupported device found'.

This is the logcat of the Uber app crash, anyone can help me understand this error please? Thanks!
(I've tried cleaning cache, data, uninstalling and re-installing... the app opens, but after I log-in the app crashes before the map to order an uber appears).
03-11 23:10:52.964 30224 30224 E AndroidRuntime: FATAL EXCEPTION: main
03-11 23:10:52.964 30224 30224 E AndroidRuntime: Process: com.ubercab, PID: 30224
03-11 23:10:52.964 30224 30224 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.res.Configuration android.content.res.Resources.getConfiguration()' on a null object reference
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.util.ResolutionOverride.<init>(ResolutionOverride.java:56)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.view.SurfaceView.init(SurfaceView.java:207)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.view.SurfaceView.<init>(SurfaceView.java:187)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at maps.dz.aq.<init>(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at maps.dz.ao.<init>(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at maps.dg.u.<init>(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at maps.dg.u.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at maps.ei.ag.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at maps.ei.bu.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at maps.ei.r.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at com.google.android.gms.maps.internal.j$a.onTransactcom.google.android.gms.alldynamite:66)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.os.Binder.transact(Binder.java:387)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at bcq.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at bbs.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at adb$2.b(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at adb$1.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at bbt.f(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at bbt.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at adb.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at adb.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at com.google.android.gms.maps.MapView.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at cry.a(SourceFile:115)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at com.ubercab.android.map.MapView.a(SourceFile:153)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at com.ubercab.client.feature.receipt.EnhancedReceiptDialogFragment.onViewCreated(SourceFile:415)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1086)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1248)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.support.v4.app.BackStackRecord.run(SourceFile:738)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.execPendingActions(SourceFile:1613)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl$1.run(SourceFile:517)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:739)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:95)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.os.Looper.loop(Looper.java:148)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5445)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)

hey dev...
f*****g awsome rom.i have tried so many on my onyx till date.never have i found a rom which is this bug free at first go.
The only error i found is
"Invalid Number".
Fix that and i guess the rom will look perfect.Thanks a lot!!

Finally !! The wait is over. My favourite ROM has arrived. Thank you Raja for bringing exodus to onyx.?

Testing the rom for some hours now and looks very promising for the initial release. Only missing function to swap buttons before daily driver in my opinion.

laav said:
Testing the rom for some hours now and looks very promising for the initial release. Only missing function to swap buttons before daily driver in my opinion.
Click to expand...
Click to collapse
Do you speak about HW button?

mousse04 said:
Do you speak about HW button?
Click to expand...
Click to collapse
Yes, or do I miss something?

Could you link me to a list of features, guys?
I have searched in google and G+ and haven't found it...
Thanks!!

laav said:
Yes, or do I miss something?
Click to expand...
Click to collapse
Go into setting, hardware, define action or something like this.
Then, you can re define hardware button action

Restore incoming call swipe directions

On stock ROM, noticed after the OTA update before last that the direction to swipe the icon to answer an incoming call changed from left (reject)/right (answer) to up(reject)/down(answer). I really dislike this change, and would like to know if anyone has a way to change it back.
Thanks in advance

Have you got unlocked bootloader?

knw257 said:
On stock ROM, noticed after the OTA update before last that the direction to swipe the icon to answer an incoming call changed from left (reject)/right (answer) to up(reject)/down(answer). I really dislike this change, and would like to know if anyone has a way to change it back.
Thanks in advance
Click to expand...
Click to collapse
I really love to change slide up to answer and slide down to reject incoming call

przemcio510 said:
Have you got unlocked bootloader?
Click to expand...
Click to collapse
Yes, and installed Magisk for root

knw257 said:
Yes, and installed Magisk for root
Click to expand...
Click to collapse
You may try to install previous version of OOS dialer (you'd have to extract the ROM zip) or switch to an old version of Google Dialer (e.g. 4.2)

przemcio510 said:
You may try to install previous version of OOS dialer (you'd have to extract the ROM zip) or switch to an old version of Google Dialer (e.g. 4.2)
Click to expand...
Click to collapse
I tried this, and managed to extract the dialer.apk from the 4.1.7 OOS image, but upon trying to install, I get a message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

knw257 said:
I tried this, and managed to extract the dialer.apk from the 4.1.7 OOS image, but upon trying to install, I get a message:
Click to expand...
Click to collapse
You have to copy the apk to /system/priv-app/OPDialer (I thnk that this is correct path, but please check) and reboot. You can't install it like a normal app

przemcio510 said:
You have to copy the apk to /system/priv-app/OPDialer (I thnk that this is correct path, but please check) and reboot. You can't install it like a normal app
Click to expand...
Click to collapse
I attempted this, but found after reboot that trying to open the dialer resulted in the app immediately crashing. I'm guessing I also need the .odex files that go along with the APK from the image.
Also, the path is /system/priv-app/dialer, just for reference.
One question: does dialer.apk rely on other apps, such as OPInCallUI, TelephonyProvider, Telcom, TeleService, etc?

knw257 said:
I attempted this, but found after reboot that trying to open the dialer resulted in the app immediately crashing. I'm guessing I also need the .odex files that go along with the APK from the image.
Click to expand...
Click to collapse
Did you clear data and set 755 for folder and 644 for file permissions?
Odex files aren't needed.
It wolud be easier to debug, if you could grab the logcat from crash.
knw257 said:
Also, the path is /system/priv-app/dialer, just for reference.
Click to expand...
Click to collapse
Ok, thanks.
knw257 said:
One question: does dialer.apk rely on other apps, such as OPInCallUI, TelephonyProvider, Telcom, TeleService, etc?
Click to expand...
Click to collapse
OPInCallUI is not needed. The rest should stay.

przemcio510 said:
OPInCallUI is not needed. The rest should stay.
Click to expand...
Click to collapse
Just to clarify, I wanted to make sure those items are not also requirements to pull from the previous OOS ROM image. I.E. do I need the older versions of those as well in addition to the dialer.apk that I pulled out?
przemcio510 said:
It wolud be easier to debug, if you could grab the logcat from crash.
Click to expand...
Click to collapse
I'll see about getting that data tonight.

There are flashable zips for Google Dialer too, if I'm not wrong. Try getting that and flash it.

knw257 said:
Just to clarify, I wanted to make sure those items are not also requirements to pull from the previous OOS ROM image. I.E. do I need the older versions of those as well in addition to the dialer.apk that I pulled out.
Click to expand...
Click to collapse
I think no, but if it won't work, you may try to pull these too.

I hope you find the fix.
May be you can create a ZIP to flash it.
Thanks

przemcio510 said:
It wolud be easier to debug, if you could grab the logcat from crash.
Click to expand...
Click to collapse
I pulled a logcat from the phone just after trying open the dialer app, and found this:
Code:
10-24 22:30:51.937 4091 4091 D AndroidRuntime: Shutting down VM
10-24 22:30:51.938 4091 4091 E AndroidRuntime: FATAL EXCEPTION: main
10-24 22:30:51.938 4091 4091 E AndroidRuntime: Process: com.android.dialer, PID: 4091
10-24 22:30:51.938 4091 4091 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.dialer/com.oneplus.contacts.activities.OPDialtactsActivity}: java.lang.RuntimeException: Unknown animation name: selector
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2733)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2819)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.app.ActivityThread.-wrap12(ActivityThread.java)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1532)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6321)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: Caused by: java.lang.RuntimeException: Unknown animation name: selector
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.view.animation.AnimationUtils.createAnimationFromXml(AnimationUtils.java:160)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.view.animation.AnimationUtils.createAnimationFromXml(AnimationUtils.java:127)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.view.animation.AnimationUtils.loadAnimation(AnimationUtils.java:108)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at com.oneplus.contacts.activities.OPDialtactsActivity.createViewsAndFragments(OPDialtactsActivity.java:541)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at com.oneplus.contacts.activities.OPDialtactsActivity.onCreate(OPDialtactsActivity.java:423)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:6760)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1134)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2686)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: ... 9 more
10-24 22:30:51.938 4091 4091 D AppTracker: App Event: crash
I'm guessing this means I also need to replace the Contacts app with the old version, but I'm not certain. If you have any input, I'd certainly appreciate it.

[MOD] Camera supporting 60FPS 120FPS

About:
This is a modification of the LineageOS camera wrapper, Snapdragon Camera app, libstagefright, and media profiles to allow recording video at 60FPS and 120FPS with stereo audio at 256kbps, also allows recording files over 4GB (the selected storage filesystem must support files larger than 4GB), and the ability to change AV bitrates/codecs on the fly. Album preference has been added in 1.3.
Q Users: Backup before install!
/system/lib/libstagefright.so
/system/product/priv-app/Snap/Snap.apk
/system/product/priv-app/Snap/oat/arm/Snap.odex
/system/product/priv-app/Snap/oat/arm/Snap.vdex
/system/vendor/etc/media_profiles_V1_0.xml
/system/vendor/lib/hw/camera.msm8974.so
P/O Users: Backup before install!
/system/lib/libstagefright.so
/system/priv-app/Snap/Snap.apk
/system/priv-app/Snap/oat/arm/Snap.odex
/system/priv-app/Snap/oat/arm/Snap.vdex
/system/vendor/etc/media_profiles_V1_0.xml (or /system/etc/media_profiles.xml)
/system/vendor/lib/hw/camera.msm8974.so
N Users: Backup before install!
/system/etc/media_profiles.xml
/system/lib/libstagefright.so
/system/lib/hw/camera.msm8974.so
/system/priv-app/Snap/Snap.apk
Download ZIP:
If you experience bugs or crashes please attach the adb log file, also include your mod version, OS, and device model in the post!
Q v1.3, TWRP 3.3.1: https://drive.google.com/file/d/1T3d6tIj_aM_zcfS7Q-RNNrT2IkvMwwvf/view?usp=sharing
P v1.3, TWRP 3.3.1: https://drive.google.com/file/d/1MPOfu7UXV-1RfWbW4EBJfSwmbVSnPXkC/view?usp=sharing
----------------
Q v1.2: https://drive.google.com/file/d/1wL5QeTFPaBGhbT3l3x4J52Q6f-fF9w8-/view?usp=sharing
P v1.2: https://drive.google.com/file/d/1Pjzu_Y5L0H8qqszYzwHJptD3uESvFKkB/view?usp=sharing
----------------
O v0.6: https://drive.google.com/open?id=1fM-SMDZT2iYxaX3AoYWCRegu918PqRFp
N v0.6: https://drive.google.com/open?id=1t2HalWYSObez0Xar0MOfk7opcLaSf0AD
----------------
Old versions: https://drive.google.com/drive/folders/1oFLPaoDmfDJlD8FAoRVhAk2haETI_dH6
v1.3 Changelog:
snap: Album preference: This will store media into subdirectories: Default, Date, Custom, Hidden.
snap: Media is now stored using the MediaStore API for Android 10 / LOS 17.1 builds.
Past Changelogs:
v1.2 Changelog:
snap: Merge upstream
snap: PiP and Multi-Window Removed (Bugs)
stagefright: Merge upstream
v1.1 Changelog:
snap: Added Picture-in-Picture support
snap: Fixed Multi-Window handling
profiles: Updated to proper location (again)
v0.9 Changelog:
snap: Merge upstream
stagefright: Merge upstream
profiles: Set all audio channels to stereo
v0.8-2 Changelog:
profiles: Updated path from upstream change, moved from /system/etc/media_profiles.xml to /system/vendor/etc/media_profiles_V1_0.xml
v0.8 Changelog:
snap: Upstream change now saves files in /Android/data/org.lineageos.snap/files instead of /DCIM/Camera
v0.7 Changelog:
snap: Fix compilation for Pie
v0.6 Changelog:
snap: Added new advanced video preferences: Video bitrate, Audio bitrate
To access these preferences, tap the "Bright screen" preference until it enables advanced camera preferences
Auto: Run the original code.
Profile: Use bitrate found in media profile, no scaling.
Manual: Set custom bitrate with slider dialog, based on the minimum and maximum bitrate caps, saving the preference for each codec.
Max: Set maximum bitrate from the encoder cap.
snap: Disabled 4GB file size limit
snap: Separate video denoise and photo denoise preferences
stagefright: Disabled 4GB file size limit
profiles: Cleanup
v0.5-3 Changelog:
wrapper: Fix quick settings flash
wrapper: Fix flash "On" photo mode
v0.5 Changelog:
wrapper: Fix hang during selfie shot
profiles: Increase audio bitrates in media_profiles.xml
v0.4 Changelog:
snap: Added "Denoise" setting to Video menu
wrapper: Restart flash during preview changes
wrapper: Removed focus modes from previous versions
wrapper: Code optimizations
profiles: Cleanup
v0.3 Changelog:
snap: Handle resource error
wrapper: Fix flash mode "On" in photo mode
v0.2 Changelog:
snap: Enabled advanced settings by default
wrapper: If torch is set, turn back on once recording in 60FPS
Known Bugs:
Camera name becomes assigned to a different resource ID on Android 9 and below. Android 10 does not have this issue.
On certain devices, front camera does not load or fails to save pictures.
1.2 Q is not parsing Snaps external storage, the files exist but they will not appear in the Gallery. In 1.3 this is fixed.
Android 9 still has the sdcard deletion bug.. if you do your own builds you can fix it with the commits below:
https://github.com/tomm1e/android_vendor_lineage/commit/6ad07dee60e26bdf88d9ac07face4d7a0fbe5610
https://github.com/tomm1e/android_p...mmit/7cad0838a254f6422343d17d5a578d2e09382359
https://github.com/LineageOS/android_frameworks_base/commit/c3f4b30d8e15228a12ca6bd1f4037d5c69dda6ea
Notes:
To access the Advanced camera preferences in Snap, tap the "Bright screen" preference until it enables.
Bitrates can be changed in media_profiles.xml. To reload them, clear the camera out of recent apps.
O+ users should force rebuild of dalvik cache after installing or upgrading: adb shell cmd package compile -m speed -f org.lineageos.snap
P and below should clear Data after upgrading so the Camera name does not get reassigned.
Source Code:
All of my changes can be found at Github:
https://github.com/tomm1e/android_device_samsung_klte-common
https://github.com/tomm1e/android_packages_apps_Snap
https://github.com/tomm1e/android_frameworks_av
Thanks to everyone at LOS and XDA! :good:
-Tom

Why to buy a new phone when we have a huge ,great support for our old S5 ,with Dev's like you ?
S5 Resurrected!

This is great! Im gonna test it

Does it works with Klte?

razor17 said:
Does it works with Klte?
Click to expand...
Click to collapse
Duh.. Read the op.
Sent from my SM-G900V using XDA Labs

Tested on klte + dotOS 2.3, does not work:
06-26 22:14:06.422 470 3336 I ActivityManager: Start proc 17888rg.lineageos.snap/u0a26 for activity org.lineageos.snap/com.android.camera.CameraActivity
06-26 22:14:06.406 1430 1566 W OpenGLRenderer: Incorrectly called buildLayer on View: ShortcutAndWidgetContainer, destroying layer...
06-26 22:14:06.473 470 8663 I OpenGLRenderer: Initialized EGL, version 1.4
06-26 22:14:06.473 470 8663 D OpenGLRenderer: Swap behavior 1
06-26 22:14:06.487 470 8663 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
06-26 22:14:06.530 470 707 W AppOps : Finishing op nesting under-run: uid 1000 pkg android code 24 time=0 duration=0 nesting=0
06-26 22:14:06.563 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile field:QUALITY_VGA
06-26 22:14:06.563 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile QUALITY_VGA
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile field:QUALITY_4KDCI
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile QUALITY_4KDCI
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile field:QUALITY_TIME_LAPSE_VGA
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile QUALITY_TIME_LAPSE_VGA
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile field:QUALITY_TIME_LAPSE_4KDCI
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile QUALITY_TIME_LAPSE_4KDCI
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile field:QUALITY_HIGH_SPEED_CIF
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile QUALITY_HIGH_SPEED_CIF
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile field:QUALITY_HIGH_SPEED_VGA
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile QUALITY_HIGH_SPEED_VGA
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile field:QUALITY_HIGH_SPEED_4KDCI
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile QUALITY_HIGH_SPEED_4KDCI
06-26 22:14:06.566 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile field:QUALITY_QHD
06-26 22:14:06.566 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile QUALITY_QHD
06-26 22:14:06.566 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile field:QUALITY_2k
06-26 22:14:06.566 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile QUALITY_2k
06-26 22:14:06.569 377 822 W QCamera2Factory: getCameraInfo: E, camera_id = 0
06-26 22:14:06.569 377 822 W QCamera2HWI: __dbg: info->orientation : 90 rc = 0
06-26 22:14:06.569 377 822 W QCamera2Factory: getCameraInfo: X
06-26 22:14:06.570 377 5565 W QCamera2Factory: getCameraInfo: E, camera_id = 1
06-26 22:14:06.570 377 5565 W QCamera2HWI: __dbg: info->orientation : 90 rc = 0
06-26 22:14:06.570 377 5565 W QCamera2HWI: __dbg: info->orientation : 270 rc = 0
06-26 22:14:06.570 377 5565 W QCamera2Factory: getCameraInfo: X
06-26 22:14:06.571 17888 17888 I CameraManagerGlobal: Connecting to camera service
06-26 22:14:06.574 377 822 W QCamera2Factory: getCameraInfo: E, camera_id = 0
06-26 22:14:06.574 377 822 W QCamera2HWI: __dbg: info->orientation : 90 rc = 0
06-26 22:14:06.574 377 822 W QCamera2Factory: getCameraInfo: X
06-26 22:14:06.594 17888 17888 D SnapCam_SettingsManager: cameraIdList size =2
06-26 22:14:06.601 377 377 W QCamera2Factory: getCameraInfo: E, camera_id = 1
06-26 22:14:06.601 377 377 W QCamera2HWI: __dbg: info->orientation : 90 rc = 0
06-26 22:14:06.601 377 377 W QCamera2HWI: __dbg: info->orientation : 270 rc = 0
06-26 22:14:06.601 377 377 W QCamera2Factory: getCameraInfo: X
06-26 22:14:06.608 17888 17888 D SnapCam_SettingsManager: cameraIdList size =2
06-26 22:14:06.613 17888 17888 W ResourceType: No known package when getting value for resource number 0x3f080009
06-26 22:14:06.614 17888 17888 D AndroidRuntime: Shutting down VM
06-26 22:14:06.614 17888 17888 E AndroidRuntime: FATAL EXCEPTION: main
06-26 22:14:06.614 17888 17888 E AndroidRuntime: Process: org.lineageos.snap, PID: 17888
06-26 22:14:06.614 17888 17888 E AndroidRuntime: java.lang.RuntimeException: Unable to create application com.android.camera.app.CameraApp: android.content.res.Resources$NotFoundException: Resource ID #0x3f080009
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5774)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at android.app.ActivityThread.-wrap1(Unknown Source:0)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1673)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at android.os.Looper.loop(Looper.java:164)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6525)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:440)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: Caused by: android.content.res.Resources$NotFoundException: Resource ID #0x3f080009
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at android.content.res.ResourcesImpl.getValue(ResourcesImpl.java:215)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at android.content.res.Resources.getInteger(Resources.java:1083)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at com.android.camera.util.CameraUtil.initialize(CameraUtil.java:247)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at com.android.camera.app.CameraApp.onCreate(CameraApp.java:47)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1119)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5771)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: ... 8 more
06-26 22:14:06.616 470 2724 W ActivityManager: Force finishing activity org.lineageos.snap/com.android.camera.CameraActivity
06-26 22:14:06.622 470 486 I ActivityManager: Showing crash dialog for package org.lineageos.snap u0
06-26 22:14:06.656 470 8663 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
06-26 22:14:06.661 470 8663 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8974.so from current namespace instead of sphal namespace.
06-26 22:14:07.119 470 485 W ActivityManager: Activity pause timeout for ActivityRecord{3c30b0 u0 org.lineageos.snap/com.android.camera.CameraActivity t5012 f}
06-26 22:14:07.155 1519 8622 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
06-26 22:14:07.170 1519 8622 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8974.so from current namespace instead of sphal namespace.
06-26 22:14:07.173 1430 1566 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
06-26 22:14:07.186 1430 1566 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8974.so from current namespace instead of sphal namespace.
06-26 22:14:07.203 1430 1566 W OpenGLRenderer: Incorrectly called buildLayer on View: ShortcutAndWidgetContainer, destroying layer...
06-26 22:14:07.203 1430 1566 W OpenGLRenderer: Incorrectly called buildLayer on View: ShortcutAndWidgetContainer, destroying layer...
06-26 22:14:07.210 1519 1519 W StaticLayout: maxLineHeight should not be -1. maxLines:2 lineCount:2
06-26 22:14:07.237 470 2724 W ActivityManager: Force finishing activity org.lineageos.snap/com.android.camera.CameraActivity
06-26 22:14:07.227 1519 1519 I chatty : uid=10040 com.google.android.googlequicksearchbox:search identical 6 lines
Inviato dal mio SM-G900F utilizzando Tapatalk

cinghio71 said:
Tested on klte + dotOS 2.3, does not work
No known package when getting value for resource number 0x3f080009
Click to expand...
Click to collapse
Ok, that error comes from a request to LineageOS 15.1 resources, I removed that request and recompiled it, try this version:
https://drive.google.com/file/d/1VVColk1q8D7_bM48QXo7hjDrB12pDolr/view?usp=sharing
Let me know if it works

socialentry said:
Ok, that error comes from a request to LineageOS 15.1 resources, I removed that request and recompiled it, try this version:
https://drive.google.com/file/d/1VVColk1q8D7_bM48QXo7hjDrB12pDolr/view?usp=sharing
Let me know if it works
Click to expand...
Click to collapse
G900F AEX v5.6 works like a charm ,test video record 720p/120fps slow motion ,perfect .
The Camera name changed to "enable" ,can you change to default name "Camera".
Thanks ! :good:
Edit :screenshot is set to 1080p ,just to show the active slow motion FPS .

Bosket said:
G900F AEX v5.6 works like a charm ,test video record 720p/120fps slow motion ,perfect .
The Camera name changed to "enable" ,can you change to default name "Camera".
Thanks ! :good:
Edit :screenshot is set to 1080p ,just to show the active slow motion FPS .
Click to expand...
Click to collapse
Awesome, does the High Speed work as well?
I'll look into that app name problem

Tested on lineage 15.1 klte build (SM-G900P model)
Everything works well, one bug i noticed was it doesn't work without flash, its not concerning but I'd like to point it out as a bug.
But I'd like to personally thank you so much for working on this mod as 60fps recording was one of the reasons I switched back and forth from AOSP to stock as I use this feature alot, I'm happy to know awesome devs like you are finally working on this, I wish you all the best with this project and I will keep testing and report back accordingly

rulex231 said:
Tested on lineage 15.1 klte build (SM-G900P model)
Everything works well, one bug i noticed was it doesn't work without flash, its not concerning but I'd like to point it out as a bug.
But I'd like to personally thank you so much for working on this mod as 60fps recording was one of the reasons I switched back and forth from AOSP to stock as I use this feature alot, I'm happy to know awesome devs like you are finally working on this, I wish you all the best with this project and I will keep testing and report back accordingly
Click to expand...
Click to collapse
Thank you!
With flash or without? I noticed it turned the torch off once recording starts, for now I made it so torch turns back on if it was set. New links in the OP. More changes are needed to properly switch into 60FPS after selecting it from the menu, that way the torch won't turn off.

socialentry said:
Awesome, does the High Speed work as well?
I'll look into that app name problem
Click to expand...
Click to collapse
Yes ,high speed work as well.
Camera name is not a problem ,just a suggestion.

socialentry said:
Ok, that error comes from a request to LineageOS 15.1 resources, I removed that request and recompiled it, try this version:
https://drive.google.com/file/d/1VVColk1q8D7_bM48QXo7hjDrB12pDolr/view?usp=sharing
Let me know if it works
Click to expand...
Click to collapse
Tested, works perfectly. Thanks.
Inviato dal mio SM-G900F utilizzando Tapatalk

Thanks, big biproject.
Does the front camera work?
I have not worked in my klte.

Using a KTLE S5. The front camera doesn't work instead the camera app crashes. Highspeed and Slow-mo both seemed to working great. Would love to see the front camera get fixed. Thanks

Delete

tomm1e said:
Thank you!
With flash or without? I noticed it turned the torch off once recording starts, for now I made it so torch turns back on if it was set. New links in the OP. More changes are needed to properly switch into 60FPS after selecting it from the menu, that way the torch won't turn off.
Click to expand...
Click to collapse
Installed it this morning, works great now thank you, even the front camera works regardless as well.

So, whats the difference between the LOS and Others?? What am asking is, which one should i install in example, Resurrection Remix?? Sorry if its a dumb question, i just thought since RR is based on LOS......
Also, what are the exact bugs?

Ano01 said:
So, whats the difference between the LOS and Others?? What am asking is, which one should i install in example, Resurrection Remix?? Sorry if its a dumb question, i just thought since RR is based on LOS......
Also, what are the exact bugs?
Click to expand...
Click to collapse
I'm not sure if RR uses lineageos resource names, if LOS doesn't work the Others one should work. Only difference in those LOS versions is that Snap requests a resource from LOS configuration during startup, specifically which hardware keys are present for the camera, like home/back/menu, those will crash if you are not on lineageos. Others just keep a default hardware key set so no crash should happen in any android. Future versions will just handle the error, it will go back to one release if it still works across all android builds.
Bugs? Nothing major, currently the flash/torch has to restart when switching into 60fps. Maybe there should be a preference to keep the camera displaying 60fps while recording or not, to save battery. Trying to rewrite the wrapper to do this currently. Some say their front camera isn't working but I think that is only for certain variants, I need their logs to see what's going on.

On my S5 G9008W (kltechnduo), with LOS 15.1, this just makes snap crash.

[T710/T715] LineageOS 15.1 (Experimental stuff)

These are my experimental builds. They are not pretend to be stable and have a lot of issues. Flash it if you know how to restore your tablet from brick. This stuff is not for daily usage. Just for testing and helping me to find bugs.
Feel free to write your feedback about builds.
I will upload roms for t710 and t715 only. Don't ask about t81x roms here please.
if you don't know how to flash recovery or flash rom, this topic is not for you.
compatible twrp:
T710: https://drive.google.com/open?id=1F-RA6OEXpWSJx2LgxsRKum2KoROGrIhd
T715: https://drive.google.com/open?id=1Icux5fPJqxDveYAjvMWASnfUpfWzO4xj
rom:
t710 only: https://drive.google.com/open?id=1-abtJDh5CbnC2ijCoAL8AdVHzP47hfCe
I'm trying to make compatibility with phh gsi builds., but for now I have error with composer. To run his builds is dirty hack: replace /system/lib/libsurcafeflinger*.so two libs from my working build.
sources:
http://github.com/bonuzzz

one more build for today
https://drive.google.com/open?id=1cIV5WN-VZUngamcNCQCNZfHS_BDIMO_W
this universal build for both models (t710 and t715)
modem stuff doesn't work here. I haven't included in config yet, but all sensors should work.

bonuzzz said:
one more build for today
https://drive.google.com/open?id=1cIV5WN-VZUngamcNCQCNZfHS_BDIMO_W
this universal build for both models (t710 and t715)
modem stuff doesn't work here. I haven't included in config yet, but all sensors should work.
Click to expand...
Click to collapse
Hello, thanks for those builds! I've been trying your lineage 15.1 ROM and I think everything is working there already. So I'll start testing these ones now... Is there something in particular you want me to logcat?
Sent from my Aquaris M5 using Tapatalk

So like these build are treble enabled? @ripee and @bonuzzz

mtnez.david said:
Hello, thanks for those builds! I've been trying your lineage 15.1 ROM and I think everything is working there already. So I'll start testing these ones now... Is there something in particular you want me to logcat?
Sent from my Aquaris M5 using Tapatalk
Click to expand...
Click to collapse
if you want something to test, there is new build https://drive.google.com/open?id=1Mu-XjXbskSXzft11onGL3mrY_I1llVKX

bonuzzz said:
if you want something to test, there is new build https://drive.google.com/open?id=1Mu-XjXbskSXzft11onGL3mrY_I1llVKX
Click to expand...
Click to collapse
Downloading again then
Sent from my Aquaris M5 using Tapatalk

mtnez.david said:
Downloading again then
Sent from my Aquaris M5 using Tapatalk
Click to expand...
Click to collapse
Hi, I am getting an error while trying to flash this rom... what does the script /tmp/install/bin/custom_t710.sh test?

mtnez.david said:
Hi, I am getting an error while trying to flash this rom... what does the script /tmp/install/bin/custom_t710.sh test?
Click to expand...
Click to collapse
no. it replaces some parameters in build.prop
will check later

bonuzzz said:
no. it replaces some parameters in build.prop
will check later
Click to expand...
Click to collapse
ok, so you are writing into the /system/build.prop my device atributes (model, device name, stuff ...). I guess you do that there in order to have same build for both t710 and t715, am i right?
---------- Post added at 01:10 PM ---------- Previous post was at 12:51 PM ----------
bonuzzz said:
no. it replaces some parameters in build.prop
will check later
Click to expand...
Click to collapse
So in this line:
sed -i 's/.*ro.build.fingerprint.*/ro.build.fingerprint=samsung/gts28wifixx/gts28wifi:7.0/NRD90M/T710XXU2DRB1:user/release-keys/' /system/build.prop
I suppose you're trying to replace the "ro.build.fingerprint=samsung/lineage ... " with "ro.build.fingerprint=samsung/gts28wifixx/gts28wifi:7.0/NRD90M/T710XXU2DRB1:user/release-keys" but I think sed can not understand that ... don't you have to scape the "/" stuff on your string there?
---------- Post added at 01:21 PM ---------- Previous post was at 01:10 PM ----------
in any case the '/' in the substituting expression crashes, I just tested it
Sent from my Aquaris M5 using Tapatalk
---------- Post added at 01:41 PM ---------- Previous post was at 01:21 PM ----------
mtnez.david said:
ok, so you are writing into the /system/build.prop my device atributes (model, device name, stuff ...). I guess you do that there in order to have same build for both t710 and t715, am i right?
---------- Post added at 01:10 PM ---------- Previous post was at 12:51 PM ----------
So in this line:
sed -i 's/.*ro.build.fingerprint.*/ro.build.fingerprint=samsung/gts28wifixx/gts28wifi:7.0/NRD90M/T710XXU2DRB1:user/release-keys/' /system/build.prop
I suppose you're trying to replace the "ro.build.fingerprint=samsung/lineage ... " with "ro.build.fingerprint=samsung/gts28wifixx/gts28wifi:7.0/NRD90M/T710XXU2DRB1:user/release-keys" but I think sed can not understand that ... don't you have to scape the "/" stuff on your string there?
---------- Post added at 01:21 PM ---------- Previous post was at 01:10 PM ----------
in any case the '/' in the substituting expression crashes, I just tested it
Sent from my Aquaris M5 using Tapatalk
Click to expand...
Click to collapse
So this works:
sed -i 's/.*ro.build.fingerprint.*/ro.build.fingerprint=samsung\/gts28wifixx\/gts28wifi:7.0\/NRD90M\/T710XXU2DRB1:user\/release-keys/' /system/build.prop
sed -i 's/.*ro.vendor.build.fingerprint.*/ro.build.fingerprint=samsung\/gts28wifixx\/gts28wifi:7.0\/NRD90M\/T710XXU2DRB1:user\/release-keys/' /system/vendor/build.prop

mtnez.david said:
ok, so you are writing into the /system/build.prop my device atributes (model, device name, stuff ...). I guess you do that there in order to have same build for both t710 and t715, am i right?
Yes. You're right.
---------- Post added at 01:10 PM ---------- Previous post was at 12:51 PM ----------
So in this line:
sed -i 's/.*ro.build.fingerprint.*/ro.build.fingerprint=samsung/gts28wifixx/gts28wifi:7.0/NRD90M/T710XXU2DRB1:user/release-keys/' /system/build.prop
I suppose you're trying to replace the "ro.build.fingerprint=samsung/lineage ... " with "ro.build.fingerprint=samsung/gts28wifixx/gts28wifi:7.0/NRD90M/T710XXU2DRB1:user/release-keys" but I think sed can not understand that ... don't you have to scape the "/" stuff on your string there?
---------- Post added at 01:21 PM ---------- Previous post was at 01:10 PM ----------
in any case the '/' in the substituting expression crashes, I just tested it
Sent from my Aquaris M5 using Tapatalk
---------- Post added at 01:41 PM ---------- Previous post was at 01:21 PM ----------
So this works:
sed -i 's/.*ro.build.fingerprint.*/ro.build.fingerprint=samsung\/gts28wifixx\/gts28wifi:7.0\/NRD90M\/T710XXU2DRB1:user\/release-keys/' /system/build.prop
sed -i 's/.*ro.vendor.build.fingerprint.*/ro.build.fingerprint=samsung\/gts28wifixx\/gts28wifi:7.0\/NRD90M\/T710XXU2DRB1:user\/release-keys/' /system/vendor/build.prop
Click to expand...
Click to collapse
I haven't checked this script on t710 yet. Working mostly on t715 tablet. Thanks for fix.

bonuzzz said:
I haven't checked this script on t710 yet. Working mostly on t715 tablet. Thanks for fix.
Click to expand...
Click to collapse
You're welcome, that's what this thread is about ... :good:

new build with fixed install script for t710 and some more things. one issue with lock screen (mobicore/keystore stuff) left. at least what I know
https://drive.google.com/open?id=1Uk3YISTssJ9h2-C8-K-XwlpGP3tpyMnk

Ok, im installing it real quick
bonuzzz said:
new build with fixed install script for t710 and some more things. one issue with lock screen (mobicore/keystore stuff) left. at least what I know
https://drive.google.com/open?id=1Uk3YISTssJ9h2-C8-K-XwlpGP3tpyMnk
Click to expand...
Click to collapse
Enviado desde mi Aquaris M5 mediante Tapatalk
---------- Post added at 10:46 PM ---------- Previous post was at 10:02 PM ----------
fingerprint settings is crashing:
Code:
08-04 00:50:45.441 7591 7591 E AndroidRuntime: FATAL EXCEPTION: main
08-04 00:50:45.441 7591 7591 E AndroidRuntime: Process: com.android.settings, PID: 7591
08-04 00:50:45.441 7591 7591 E AndroidRuntime: java.lang.RuntimeException: Failure delivering result ResultInfo{who=android:fragment:0, request=100, result=-1, data=null} to activity {com.android.settings/com.android.settings.password.ChooseLockGeneric}: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String android.content.Intent.getStringExtra(java.lang.String)' on a null object reference
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at android.app.ActivityThread.deliverResults(ActivityThread.java:4268)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at android.app.ActivityThread.handleSendResult(ActivityThread.java:4312)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at android.app.ActivityThread.-wrap19(Unknown Source:0)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1644)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at android.os.Looper.loop(Looper.java:164)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6494)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:440)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String android.content.Intent.getStringExtra(java.lang.String)' on a null object reference
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at com.android.settings.password.ChooseLockGeneric$ChooseLockGenericFragment.onActivityResult(ChooseLockGeneric.java:344)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at android.app.Activity.dispatchActivityResult(Activity.java:7303)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at android.app.ActivityThread.deliverResults(ActivityThread.java:4264)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: ... 9 more
08-04 00:50:45.448 3604 4687 W ActivityManager: Force finishing activity com.android.settings/.password.ChooseLockGeneric
08-04 00:50:45.458 3604 4687 W ActivityManager: Force finishing activity com.android.settings/.fingerprint.FingerprintEnrollIntroduction
08-04 00:50:45.466 3604 3620 I ActivityManager: Showing crash dialog for package com.android.settings u0
---------- Post added at 10:59 PM ---------- Previous post was at 10:46 PM ----------
screen lock as well:
Code:
08-04 00:57:44.415 4955 4955 D SubSettings: Launching fragment com.android.settings.password.ChooseLockGeneric$ChooseLockGenericFragment
08-04 00:57:44.423 3594 3786 I ActivityManager: START u0 {cmp=com.android.settings/.password.ConfirmLockPattern$InternalActivity (has extras)} from uid 1000
08-04 00:57:44.457 4955 5043 W TileUtils: Found com.android.settings.backup.BackupSettingsActivity for intent Intent { act=com.android.settings.action.SETTINGS pkg=com.android.settings } missing metadata com.android.settings.category
08-04 00:57:44.460 4955 5043 W TileUtils: Found org.lineageos.lineageparts.trust.TrustPreferences for intent Intent { act=org.lineageos.lineageparts.action.SETTINGS pkg=org.lineageos.lineageparts } missing metadata
08-04 00:57:44.474 4955 4979 D mali_winsys: EGLint new_window_surface(egl_winsys_display*, void*, EGLSurface, EGLConfig, egl_winsys_surface**, egl_color_buffer_format*, EGLBoolean) returns 0x3000, [1536x2048]-format:1
08-04 00:57:44.474 4955 4955 E RecyclerView: No adapter attached; skipping layout
08-04 00:57:44.476 4955 5044 D Settings: No enabled state changed, skipping updateCategory call
08-04 00:57:44.643 4955 4955 D AndroidRuntime: Shutting down VM
--------- beginning of crash
08-04 00:57:44.643 4955 4955 E AndroidRuntime: FATAL EXCEPTION: main
08-04 00:57:44.643 4955 4955 E AndroidRuntime: Process: com.android.settings, PID: 4955
08-04 00:57:44.643 4955 4955 E AndroidRuntime: java.lang.RuntimeException: Failure delivering result ResultInfo{who=android:fragment:0, request=100, result=-1, data=null} to activity {com.android.settings/com.android.settings.SubSettings}: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String android.content.Intent.getStringExtra(java.lang.String)' on a null object reference
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at android.app.ActivityThread.deliverResults(ActivityThread.java:4268)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at android.app.ActivityThread.handleSendResult(ActivityThread.java:4312)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at android.app.ActivityThread.-wrap19(Unknown Source:0)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1644)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at android.os.Looper.loop(Looper.java:164)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6494)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:440)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String android.content.Intent.getStringExtra(java.lang.String)' on a null object reference
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at com.android.settings.password.ChooseLockGeneric$ChooseLockGenericFragment.onActivityResult(ChooseLockGeneric.java:344)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at android.app.Activity.dispatchActivityResult(Activity.java:7303)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at android.app.ActivityThread.deliverResults(ActivityThread.java:4264)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: ... 9 more
08-04 00:57:44.647 3594 3786 W ActivityManager: Force finishing activity com.android.settings/.SubSettings
08-04 00:57:44.651 3594 3786 W ActivityManager: Force finishing activity com.android.settings/.Settings$SecuritySettingsActivity
08-04 00:57:44.661 3594 3610 I ActivityManager: Showing crash dialog for package com.android.settings u0

@mtnez.david I said about it in previous message

I confirm it then. I'll see if I find something else
Enviado desde mi Aquaris M5 mediante Tapatalk

today's build
https://drive.google.com/open?id=1yJQ8Pu1VnZddFr7YMeX9n7NQ_M5DkBE6

I haven't got any crash today in today's build, I've been installing apps, not games, all seem to work properly. I could install nexflix from play store but I got the apk and it works fine.
Is there something specific that is supposed not to work?
Sent from my Aquaris M5 using Tapatalk

@mtnez.david no. everything should work

Is it supposed to be treble enabled?
Sent from my SM-T710 using Tapatalk

@mtnez.david no, only build in first post was treble enabled. I have broken camera and I don't want to upload new builds until I fix it. But I'm not even sure I will fix it.