Hi guys,
I was not planning to buy a GalaxyS5, but i was lucky to get one as gift this weekend.
One of the issues i noticed on the past two days was the SHealth incompatibility with Xposed (described on this thread), somehow if you are using Xposed framework, Secure storage will fails to process and save data, which leads to Sensor service hangs
This module bypass the secure storage checks on SHealth and Private mode services, and will let you load the SHealth App with no hangs and activate Private mode on Rooted Samsung devices running Xposed framework.
I did just the basic tests for SHealth because i don't use this App anyway, it's not easy to play football with a device on my hands/pocket .
Download
Note:
You may need to clear SHealth and Health service data (you will loose your Pedometer data).
Clearing Personal pages service will break Private mode.
Troubleshooting:
If you can't get Private mode to work after switching to Xposed, you need to go back to a stock FW and backup your private files, after that you can install Xposed and enable my module then remove "/data/system/users/privatemode_edk_1000" as advised by @invano.
Changelog:
1.0.1:
- Add Private mode support.
- App renamed from XHealth to XSecureStorage
Thanks to:
Rovo89 for his awesome work on Xposed framework and Mods.
Tungstwenty for contribution on Xposed framework and his many Mods
Working good! I had the secure storage disabled but I enabled it now and tried your module. S Health works! Thank you!
Not working for me. Getting “Health service has stopped working” about every other second. Much more frequent than before…
Maybe I am doing something wrong.
It also seems to reset everything saved in the Health Service app, or? Maybe you should have mentioned that.
ulsa said:
Not working for me. Getting “Health service has stopped working” about every other second. Much more frequent than before…
Maybe I am doing something wrong.
It also seems to reset everything saved in the Health Service app, or? Maybe you should have mentioned that.
Click to expand...
Click to collapse
Can you post your xposed logs?
wanam said:
Can you post your xposed logs?
Click to expand...
Click to collapse
16 sep 2014 11:46:32 UTC
Loading Xposed v54 (for Zygote)...
Running ROM 'KOT49H.G900FXXU1ANG9' with fingerprint 'samsung/kltexx/klte:4.4.2/KOT49H/G900FXXU1ANG9:user/release-keys'
-----------------
16 sep 2014 11:50:23 UTC
Loading Xposed v54 (for Zygote)...
Running ROM 'KOT49H.G900FXXU1ANG9' with fingerprint 'samsung/kltexx/klte:4.4.2/KOT49H/G900FXXU1ANG9:user/release-keys'
Loading modules from /data/app/ma.wanam.xshealth-1.apk
Loading class ma.wanam.xshealth.Xposed
Loading modules from /data/app/com.oasisfeng.greenify-4.apk
Loading class com.oasisfeng.greenify.pro.FrameworkPatch
Loading class com.oasisfeng.greenify.pro.SettingsPatch
Loading modules from /data/app/com.bubblesoft.android.bubbleupnp-6.apk
Loading class com.bubblesoft.android.bubbleupnp.xmod.BubbleUPnPXMod
logging enabled: false
created audio cast fifo: /data/data/com.bubblesoft.android.bubbleupnp/audiocast
ulsa said:
16 sep 2014 11:46:32 UTC
Loading Xposed v54 (for Zygote)...
Running ROM 'KOT49H.G900FXXU1ANG9' with fingerprint 'samsung/kltexx/klte:4.4.2/KOT49H/G900FXXU1ANG9:user/release-keys'
-----------------
16 sep 2014 11:50:23 UTC
Loading Xposed v54 (for Zygote)...
Running ROM 'KOT49H.G900FXXU1ANG9' with fingerprint 'samsung/kltexx/klte:4.4.2/KOT49H/G900FXXU1ANG9:user/release-keys'
Loading modules from /data/app/ma.wanam.xshealth-1.apk
Loading class ma.wanam.xshealth.Xposed
Loading modules from /data/app/com.oasisfeng.greenify-4.apk
Loading class com.oasisfeng.greenify.pro.FrameworkPatch
Loading class com.oasisfeng.greenify.pro.SettingsPatch
Loading modules from /data/app/com.bubblesoft.android.bubbleupnp-6.apk
Loading class com.bubblesoft.android.bubbleupnp.xmod.BubbleUPnPXMod
logging enabled: false
created audio cast fifo: /data/data/com.bubblesoft.android.bubbleupnp/audiocast
Click to expand...
Click to collapse
No issues on the logs, which means it should be working fine, are you using the latest SHealth update? were you using any other mod to get it working before?
About the App data, i got a popup to restore my data through SHealth App and it was restored with no issues!
S health says it's the latest update.
I have not done any other mods.
I did not get a restore popup. The data was automatically restored when I uninstalled xsposed.
Skickat från min SM-G900F via Tapatalk
ulsa said:
S health says it's the latest update.
I have not done any other mods.
I did not get a restore popup. The data was automatically restored when I uninstalled xsposed.
Skickat från min SM-G900F via Tapatalk
Click to expand...
Click to collapse
Okay, if you have time to try the module again, PM me your logcat.
If don't get the same bellow errors, then it should be other thing:
Code:
I/SecureStorage( 7245): [INFO]: SPID(0x00000000)Processing data
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)transition_table [first_perm][second_perm] != 0
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)first_perm = 3
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)second_perm = 3
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)Block_perm = 2
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=0 415E4000 - 41650000 r-xp /system/lib/libdvm.so
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=1 41650000 - 41651000 r-xp /system/lib/libdvm.so
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=2 41651000 - 416A7000 r-xp /system/lib/libdvm.so
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=3 416A7000 - 416AB000 r--p /system/lib/libdvm.so
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=4 416AB000 - 416B1000 rw-p /system/lib/libdvm.so
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=5 416B1000 - 416B5000 rw-p
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)bad block
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)parse_proc_fs error
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)Error processing data
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)Android: read data error: -2
I/SecureStorage( 7245): [INFO]: SPID(0x00000000)Processing data
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)transition_table [first_perm][second_perm] != 0
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)first_perm = 3
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)second_perm = 3
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)Block_perm = 2
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=0 415E4000 - 41650000 r-xp /system/lib/libdvm.so
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=1 41650000 - 41651000 r-xp /system/lib/libdvm.so
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=2 41651000 - 416A7000 r-xp /system/lib/libdvm.so
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=3 416A7000 - 416AB000 r--p /system/lib/libdvm.so
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=4 416AB000 - 416B1000 rw-p /system/lib/libdvm.so
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=5 416B1000 - 416B5000 rw-p
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)bad block
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)parse_proc_fs error
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)Error processing data
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)Android: read data error: -2
I/SecureStorage( 7245): [INFO]: SPID(0x00000000)Processing data
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)transition_table [first_perm][second_perm] != 0
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)first_perm = 3
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)second_perm = 3
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)Block_perm = 2
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=0 415E4000 - 41650000 r-xp /system/lib/libdvm.so
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=1 41650000 - 41651000 r-xp /system/lib/libdvm.so
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=2 41651000 - 416A7000 r-xp /system/lib/libdvm.so
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=3 416A7000 - 416AB000 r--p /system/lib/libdvm.so
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=4 416AB000 - 416B1000 rw-p /system/lib/libdvm.so
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)i=5 416B1000 - 416B5000 rw-p
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)bad block
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)parse_proc_fs error
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)Error processing data
E/SecureStorage( 7245): [ERROR]:SPID(0x00000000)Android: read data error: -2
I/SQLiteSecureOpenHelper( 7245): getWritableDatabase(pwd)
I/SQLiteSecureOpenHelper( 7245): getDatabaseLocked(b,b,pwd)...
I/SQLiteSecureOpenHelper( 7245): Open platform.db in secure mode
E/SQLiteLog( 7245): (26) statement aborts at 0: [PRAGMA user_version;] file is encrypted or is not a database
E/DefaultSecureDatabaseErrorHandler( 7245): Corruption reported by sqlite on database: /data/user/0/com.sec.android.service.health/databases/platform.db
E/DefaultSecureDatabaseErrorHandler( 7245): backup the database file: /data/user/0/com.sec.android.service.health/databases/platform.db
D/SQLiteSecureOpenHelper( 7245): ...getDatabaseLocked(b,b,pwd)
E/JavaBinder( 7245): *** Uncaught remote exception! (Exceptions are not yet supported across processes.)
E/JavaBinder( 7245): java.lang.RuntimeException: android.database.sqlite.SQLiteDatabaseCorruptException: file is encrypted or is not a database (code 26)
E/JavaBinder( 7245): at com.sec.android.service.health.cp.database.DBManager.getWritableDatabase(DBManager.java:164)
E/JavaBinder( 7245): at com.sec.android.service.health.cp.database.DBManager.getWritableDatabase(DBManager.java:100)
E/JavaBinder( 7245): at com.sec.android.service.health.cp.HealthContentProvider.query(HealthContentProvider.java:534)
E/JavaBinder( 7245): at android.content.ContentProvider.query(ContentProvider.java:857)
E/JavaBinder( 7245): at android.content.ContentProvider$Transport.query(ContentProvider.java:200)
E/JavaBinder( 7245): at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:112)
E/JavaBinder( 7245): at android.os.Binder.execTransact(Binder.java:404)
E/JavaBinder( 7245): at dalvik.system.NativeStart.run(Native Method)
E/JavaBinder( 7245): Caused by: android.database.sqlite.SQLiteDatabaseCorruptException: file is encrypted or is not a database (code 26)
E/JavaBinder( 7245): at android.database.sqlite.SQLiteConnection.nativeExecuteForLong(Native Method)
E/JavaBinder( 7245): at android.database.sqlite.SQLiteConnection.executeForLong(SQLiteConnection.java:788)
E/JavaBinder( 7245): at android.database.sqlite.SQLiteSession.executeForLong(SQLiteSession.java:652)
E/JavaBinder( 7245): at android.database.sqlite.SQLiteStatement.simpleQueryForLong(SQLiteStatement.java:107)
E/JavaBinder( 7245): at android.database.DatabaseUtils.longForQuery(DatabaseUtils.java:825)
E/JavaBinder( 7245): at android.database.DatabaseUtils.longForQuery(DatabaseUtils.java:813)
E/JavaBinder( 7245): at android.database.sqlite.SQLiteDatabase.getVersion(SQLiteDatabase.java:996)
E/JavaBinder( 7245): at android.database.sqlite.SQLiteSecureOpenHelper.getDatabaseLocked(SQLiteSecureOpenHelper.java:366)
E/JavaBinder( 7245): at android.database.sqlite.SQLiteSecureOpenHelper.getWritableDatabase(SQLiteSecureOpenHelper.java:275)
E/JavaBinder( 7245): at com.sec.android.service.health.cp.database.DBManager.getWritableDatabase(DBManager.java:153)
E/JavaBinder( 7245): ... 7 more
Works perfect!!!
Using Neatrom v2.2 odexed
Set false back to true and works without a fc @ulsa try fc and wipe data of shealth make a backup first if you dont want to lose progress.
Reboot and try again might work for you.
Verstuurd vanaf mijn SM-G900F met Tapatalk
Sock12345 said:
Works perfect!!!
Using Neatrom v2.2 odexed
Set false back to true and works without a fc @ulsa try fc and wipe data of shealth make a backup first if you dont want to lose progress.
Reboot and try again might work for you.
Verstuurd vanaf mijn SM-G900F met Tapatalk
Click to expand...
Click to collapse
FC and wiping data worked perfectly. Thanks to you both!
ulsa said:
FC and wiping data worked perfectly. Thanks to you both!
Click to expand...
Click to collapse
Ur welcome man
Verstuurd vanaf mijn SM-G900F met Tapatalk
I am using Xposed and SHealth is working fine for me without a module. I once had a problem and I cleared the data of the app and the service and never had a problem anymore.
DirkStorck said:
I am using Xposed and SHealth is working fine for me without a module. I once had a problem and I cleared the data of the app and the service and never had a problem anymore.
Click to expand...
Click to collapse
Are you running the latest update of SHealth?
Yes I think so. Version 3.2.3 at least there is no new version in Samsung app store.
---------- Post added at 07:39 PM ---------- Previous post was at 07:38 PM ----------
DirkStorck said:
Yes I think so. Version 3.2.3 at least there is no new version in Samsung app store.
Click to expand...
Click to collapse
OK. I am running your wanam Xposed module. If that makes a difference ☺
DirkStorck said:
Yes I think so. Version 3.2.3 at least there is no new version in Samsung app store.
---------- Post added at 07:39 PM ---------- Previous post was at 07:38 PM ----------
OK. I am running your wanam Xposed module. If that makes a difference ☺
Click to expand...
Click to collapse
Yes my latest update include this fix.
DirkStorck said:
Yes I think so. Version 3.2.3 at least there is no new version in Samsung app store.
---------- Post added at 07:39 PM ---------- Previous post was at 07:38 PM ----------
OK. I am running your wanam Xposed module. If that makes a difference ☺
Click to expand...
Click to collapse
wanam said:
Yes my latest update include this fix.
Click to expand...
Click to collapse
I was running both modules and SHealth did not work. Uninstalled this module, and now SHealth is working. Having 2 modules doing the same thing must cancel out the thing...
wanam said:
Yes my latest update include this fix.
Click to expand...
Click to collapse
OK. Didn't know that ? thanks for letting me know ☺
clearing data on both shealth and health service resolved the FC's . Thanks heaps.
---------- Post added at 07:44 AM ---------- Previous post was at 07:27 AM ----------
I have noticed that the latest update to Wanam Xposed has a check box for disabled secure storage check for shealth. So can I uninstall this module and just check that box in the wanam xposed ?
trevagreene said:
clearing data on both shealth and health service resolved the FC's . Thanks heaps.
---------- Post added at 07:44 AM ---------- Previous post was at 07:27 AM ----------
I have noticed that the latest update to Wanam Xposed has a check box for disabled secure storage check for shealth. So can I uninstall this module and just check that box in the wanam xposed ?
Click to expand...
Click to collapse
Yes, you do NOT need this module if you are using Wanam xposed.
wanam said:
Hi guys,
I was not planning to buy a GalaxyS5, but i was lucky to get one as gift this weekend.
One of the issues i noticed on the past two days was the SHealth incompatibility with Xposed (described on this thread), somehow if you are using Xposed framework, Secure storage will fails to process and save data, which leads to Sensor service hangs
This module will let you bypass the secure storage checks on SHealth services, and load SHealth App with no hangs on Rooted devices running Xposed framework.
I did just the basic tests because i don't use this App anyway, it's not easy to play football with a device on my hands/pocket .
Download
Note: You may need to clear SHealth and Health service data.
Thanks to:
Rovo89 for his awesome work on Xposed framework and Mods.
Tungstwenty for contribution on Xposed framework and his many Mods
Click to expand...
Click to collapse
I have a question about your module. I am still learning about all the stuff on android. So I fixed my S Health with the Buildprop editor. Yet I am unable to get Secure Storage to work, but S HEALTH DOES. So will you app solution work? Do I have to change what I did in build.prop?
---------- Post added at 04:44 AM ---------- Previous post was at 04:36 AM ----------
wanam said:
Hi guys,
I was not planning to buy a GalaxyS5, but i was lucky to get one as gift this weekend.
One of the issues i noticed on the past two days was the SHealth incompatibility with Xposed (described on this thread), somehow if you are using Xposed framework, Secure storage will fails to process and save data, which leads to Sensor service hangs
This module will let you bypass the secure storage checks on SHealth services, and load SHealth App with no hangs on Rooted devices running Xposed framework.
I did just the basic tests because i don't use this App anyway, it's not easy to play football with a device on my hands/pocket .
Download
Note: You may need to clear SHealth and Health service data.
Thanks to:
Rovo89 for his awesome work on Xposed framework and Mods.
Tungstwenty for contribution on Xposed framework and his many Mods
Click to expand...
Click to collapse
Does this also fix Private Mode?
Related
The latest version of the Netflix android app (1.2.1) seems to work fine on any 2.3 vibrant roms out of the box, no mods needed!
The previous tutorial is now obsolete, all you need to do is install any 2.3 rom and Netflix should work directly from the market, or you can download it here: http://bit.ly/mA0ar0. Enjoy. Btw, from my personal experience, I have yet to find a 2.2 rom where Netflix actually works, but this shouldn't be a problem if you install a ginger-rom or wait for the official sammy 2.3 update (if it ever happens lmao).
Reserved for OP
And another update uninstalled flash all together and it still works fine.. also i don't think it was a data toggle that helped but more locking the device and really unlocking but i think that's just because I'm running miui! And thanks for the props!!! much appreciated...
Sent from my HTC Vision using XDA Premium App
n1gh7mar3 said:
And another update uninstalled flash all together and it still works fine.. also i don't think it was a data toggle that helped but more locking the device and really unlocking but i think that's just because I'm running miui! And thanks for the props!!! much appreciated...
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
By unlocking the device you mean, actually pressing the lock button on the side of the phone and unlocking it? I know, stupid questions, but I wasn't sure lol. And no problem on the credit or the tutorial, it was the least I could for the guy who discovered how to get netflix running on the Vib!
works!
I did what the tutorial said on my vibrant running simply honey 3.3 update 1. at first i got all the weird color lines on my phone then i toggled data and air plane mode off and on and it worked...i subscribed to netflix, only 7.99$ not too bad. super clear video, im loving it..
gramlights4 said:
I did what the tutorial said on my vibrant running simply honey 3.3 update 1. at first i got all the weird color lines on my phone then i toggled data and air plane mode off and on and it worked...i subscribed to netflix, only 7.99$ not too bad. super clear video, im loving it..
Click to expand...
Click to collapse
awesome good to know.
Build.prop: This isn't the galaxy s your looking for
Netflix: oh okay.
Edit: got it installed, and it isn't telling me wrong device. But when I log in it flashes white the exits out.. updating flash to see if that helps.
Tynen said:
Build.prop: This isn't the galaxy s your looking for
Netflix: oh okay.
Click to expand...
Click to collapse
very nice reference my friend, very nice indeed lmao.
It's not complaining about the device type but once I log in it dumps out of the program. Any ideas?
Tynen said:
It's not complaining about the device type but once I log in it dumps out of the program. Any ideas?
Click to expand...
Click to collapse
Getting the same thing, right when I hit login, it sits and spins for a bit, then dumps me out to home.
LOGCAT from when I hit login, til it dumped me to home
Code:
V/WindowManager( 3469): Dsptch > Window{487610f0 com.netflix.mediaclient/com.netflix.mediaclient.UIWebViewActivity paused=false}
V/InputDevice( 3469): ID[0]=0(0) Dn(0=>1)
V/WindowManager( 3469): Dsptch > Window{487610f0 com.netflix.mediaclient/com.netflix.mediaclient.UIWebViewActivity paused=false}
V/InputDevice( 3469): ID[0]=0(0) Up(1=>0)
D/navcache( 6988): cursorInputFieldAction : Focused node is not an inputfield
E/MAXKTK ( 6988): socket443
D/dalvikvm( 6988): GC_FOR_MALLOC freed 9402 objects / 610496 bytes in 44ms
E/MAXKTK ( 6988): socket443
W/PowerManagerService( 3469): Timer 0x3->0x3|0x3
E/NRDdevice2( 6988): DeviceLib::init Cannot load library /data/data/com.netflix.mediaclient/lib/libnetflix_devicex.so: Cannot load library: link_image[1995]: failed to link libnetflix_device1.so
E/NRDdevice2( 6988):
E/NRDdevice2( 6988): DeviceLib::init Cannot load library /system/lib/libnetflix_devicex.so: Cannot load library: find_library[1188]: 2719 'libnetflix_device1.so' failed to load previously
E/NRDdevice2( 6988): DeviceLib::init Cannot Cannot load symbol createBufferManager: Invalid library handle: find_library[1188]: 2719 'libnetflix_device1.so' failed to load previously
E/NRDdevice2( 6988): DeviceLib::init Cannot Cannot load symbol createPlaybackDevice: Invalid library handle: find_library[1188]: 2719 'libnetflix_device1.so' failed to load previously
D/Zygote ( 2719): Process 6988 terminated by signal (11)
I/ActivityManager( 3469): Process com.netflix.mediaclient (pid 6988) has died.
I/WindowManager( 3469): WIN DEATH: Window{487610f0 com.netflix.mediaclient/com.netflix.mediaclient.UIWebViewActivity paused=false}
I/UsageStats( 3469): Unexpected resume of com.ebproductions.android.launcher while already resumed in com.netflix.mediaclient
V/RenderScript_jni( 4193): surfaceCreated
V/RenderScript_jni( 4193): surfaceChanged
W/InputManagerService( 3469): Got RemoteException sending setActive(false) notification to pid 6988 uid 10207
W/Resources( 3469): Converting to boolean: TypedValue{t=0x3/d=0x1574 "res/anim/accelerate_decelerate_interpolator.xml" a=2 r=0x10a0004}
W/PowerManagerService( 3469): Timer 0x3->0x3|0x0
Tynen said:
It's not complaining about the device type but once I log in it dumps out of the program. Any ideas?
Click to expand...
Click to collapse
I get the same thing with the Bionix-v 1.3.2.
I sure that there will be some work around soon. I am so happy that this app was finally released.
d_bot said:
Getting the same thing, right when I hit login, it sits and spins for a bit, then dumps me out to home.
LOGCAT from when I hit login, til it dumped me to home
Code:
V/WindowManager( 3469): Dsptch > Window{487610f0 com.netflix.mediaclient/com.netflix.mediaclient.UIWebViewActivity paused=false}
V/InputDevice( 3469): ID[0]=0(0) Dn(0=>1)
V/WindowManager( 3469): Dsptch > Window{487610f0 com.netflix.mediaclient/com.netflix.mediaclient.UIWebViewActivity paused=false}
V/InputDevice( 3469): ID[0]=0(0) Up(1=>0)
D/navcache( 6988): cursorInputFieldAction : Focused node is not an inputfield
E/MAXKTK ( 6988): socket443
D/dalvikvm( 6988): GC_FOR_MALLOC freed 9402 objects / 610496 bytes in 44ms
E/MAXKTK ( 6988): socket443
W/PowerManagerService( 3469): Timer 0x3->0x3|0x3
E/NRDdevice2( 6988): DeviceLib::init Cannot load library /data/data/com.netflix.mediaclient/lib/libnetflix_devicex.so: Cannot load library: link_image[1995]: failed to link libnetflix_device1.so
E/NRDdevice2( 6988):
E/NRDdevice2( 6988): DeviceLib::init Cannot load library /system/lib/libnetflix_devicex.so: Cannot load library: find_library[1188]: 2719 'libnetflix_device1.so' failed to load previously
E/NRDdevice2( 6988): DeviceLib::init Cannot Cannot load symbol createBufferManager: Invalid library handle: find_library[1188]: 2719 'libnetflix_device1.so' failed to load previously
E/NRDdevice2( 6988): DeviceLib::init Cannot Cannot load symbol createPlaybackDevice: Invalid library handle: find_library[1188]: 2719 'libnetflix_device1.so' failed to load previously
D/Zygote ( 2719): Process 6988 terminated by signal (11)
I/ActivityManager( 3469): Process com.netflix.mediaclient (pid 6988) has died.
I/WindowManager( 3469): WIN DEATH: Window{487610f0 com.netflix.mediaclient/com.netflix.mediaclient.UIWebViewActivity paused=false}
I/UsageStats( 3469): Unexpected resume of com.ebproductions.android.launcher while already resumed in com.netflix.mediaclient
V/RenderScript_jni( 4193): surfaceCreated
V/RenderScript_jni( 4193): surfaceChanged
W/InputManagerService( 3469): Got RemoteException sending setActive(false) notification to pid 6988 uid 10207
W/Resources( 3469): Converting to boolean: TypedValue{t=0x3/d=0x1574 "res/anim/accelerate_decelerate_interpolator.xml" a=2 r=0x10a0004}
W/PowerManagerService( 3469): Timer 0x3->0x3|0x0
Click to expand...
Click to collapse
forgot to mention you need to flash a gingerbread rom for this to actually work, sorry my bad.
I'm flashing CyanogenMod now to see if it'll work there. I just finished editing the build.prop I'm rebooting after Dalvik cache wipe.. takes a while
Edit:
bobofosho123 said:
forgot to mention you need to flash a gingerbread rom for this to actually work, sorry my bad.
Click to expand...
Click to collapse
Figured as much.
I wonder what the Nexus One (running 2.2) has that Vibrant 2.2 doesn't.... hmmmmm
Didn't Google add a DRM framework into GB?? Makes sense that it wouldn't work without that framework.
Tynen said:
I'm flashing CyanogenMod now to see if it'll work there. I just finished editing the build.prop I'm rebooting after Dalvik cache wipe.. takes a while
Edit:
Figured as much.
I wonder what the Nexus One (running 2.2) has that Vibrant 2.2 doesn't.... hmmmmm
Click to expand...
Click to collapse
it's made by htc. the hardware and software on the nexus s 2.3 is the only similar one.
Yeah i definately think a 2.3 rom needs to be the base!
Sent from my HTC Vision using XDA Premium App
i flashed Simply Galaxy RC3.3 and all i did was install netflix and it worked!!!!
works gorgeously on miui 1.5.6b edited reboot cleared, rebooted play. no data toggling, locking etc.
Got it working on CM7.
Sent from my SGH-T959 using XDA Premium App
Hmmm so I either get GPS or Netflix...... I think I use my GPS much more than I will Netflix
Sent from my HTC Vision using XDA App
I amgetting a boot loop with bonixV 1.2.1, I let it sit for awhile then restore my nandroid backup.
Ahhh it booted up.
Hi all,
First-time poster and fairly new to rooting...
I have a Samsung Galaxy SII (GT-I9100, originally LBP firmware on Orange UK) which I successfully managed to flash with Odin/Heimdall to give:
CF-Root
CyanogenMod 9 RC1
Siyah 3.3.2
I then thought I'd give Boot2Gecko a try so I followed gokhanmoral's post and managed to get a page not found screen booting to the second rom.
So I checked out the B2G source code and performed a
make install-gaia
Click to expand...
Click to collapse
ensuring
adb devices
Click to expand...
Click to collapse
found my phone connected over usb - This gave me a lock screen which wouldn't respond to touch events.
After quite a bit of reading I then decided to attempt pusler new 6th July Build performing:
simg2img userdata.img data.img
heimdall detect
heimdall flash --hidden system.img
(cleared 2ndROM data and cache through CWM)
adb push data.img /sdcard/.secondrom/data.img
Click to expand...
Click to collapse
However, when I booted to the 2ndROM I gott a black screen - I tried looking through the
adb shell logcat
Click to expand...
Click to collapse
output and saw several errors similar to:
I/GeckoDump( 9894): Opened socket on 9999
E/GeckoConsole( 9894): [JavaScript Error: "NS_ERROR_UNEXPECTED: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getCharPref]" {file: "chrome://browser/content/shell.js" line: 80}]
I/Gecko ( 9894): Logging GL tracing output to /system/b2g/firefox.trace
I/Gecko ( 9894): Attempting load of /data/local/egltrace.so
F/libc ( 9894): Fatal signal 11 (SIGSEGV) at 0x00000068 (code=1)
I/Gecko ( 9894): Attempting load of libEGL.so
D/libEGL ( 9894): egl.cfg not found, using default config
D/libEGL ( 9894): loaded /system/lib/egl/libGLES_android.so
I/Gecko ( 9894): Failed to create EGL config!
F/libc ( 9894): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1)
I/DEBUG ( 9891): debuggerd committing suicide to free the zombie!
F/libc ( 9847): Fatal signal 13 (SIGPIPE) at 0x00002677 (code=0)
I/DEBUG ( 9978): debuggerd: Jul 6 2012 04:08:21
I/ ( 9979): ServiceManager: 0xf958
V/yamaha::media::CManager( 9979): constructor
Click to expand...
Click to collapse
Seems like a Gecko Chrome error but I can't be sure. As a last ditch effort I tried to follow gokhanmoral's method of extracting/mounting pusler's images, creating tar files and placing them into a CWM flashable zip but Siyah wouldn't recognise the 2ndROM after installing so now I'm all out of ideas.
Has anyone managed to successfully install the 6th July build as a 2ndROM? Any help/info would be appreciated.
Cheers
Hello!
I have some problem with my Samsung Galaxy S2. In normal system, when some application crash then can see message box to force shutdown application and additional report a problem to the author. Unfortunately I don't have it. When some application crash then first my phone freeze for about 1-2 minutes (but upper toolbar works) and later my phone restart, but it's not a full booting.
I connected my phone to the PC and run logcat so I got this logs. Parsebin: 8db3G1c5 . I thing this part of logs is interesting:
09-30 10:58:51.570 E/android.os.Debug( 1991): [email protected] > dumpstate -k -t -n -z -d -o /data/log/dumpstate_app_error
09-30 10:58:51.595 I/dumpstate(10861): Check if stand-alone
09-30 10:58:51.605 I/dumpstate(10861): begin
09-30 10:58:52.070 W/ActivityManager( 1991): Activity pause timeout for r
(...)
09-30 10:59:36.900 I/Process ( 1991): Sending signal. PID: 1991 SIG: 3
09-30 10:59:36.905 I/dalvikvm( 1991): threadid=3: reacting to signal 3
09-30 10:59:37.005 I/dalvikvm( 1991): Wrote stack traces to '/data/anr/traces.txt'
09-30 10:59:37.005 E/Watchdog( 1991): [email protected] 183
(...)
09-30 11:00:09.125 I/Watchdog_N( 1991): dumpKernelStacks
09-30 11:00:09.145 E/android.os.Debug( 1991): [email protected]umpstate > dumpstate -k -t -z -d -o /data/log/dumpstate_sys_watchdog
09-30 11:00:09.145 E/Watchdog( 1991): WATCHDOG caused by null
(...)
09-30 11:00:21.200 I/Process ( 1991): Sending signal. PID: 1991 SIG: 9
09-30 11:00:21.200 W/Watchdog( 1991): *** WATCHDOG KILLING SYSTEM PROCESS: null
09-30 11:00:21.330 I/binder_sample(10879): [,14,86755,app_process,100]
09-30 11:00:21.330 I/binder_sample(10847): [,2,89808,com.prodtestapp,100]
09-30 11:00:21.330 I/binder_sample( 2219): [com.android.internal.telephony.ITelephonyRegistry, 4,18131,com.android.phone,100]
09-30 11:00:21.330 I/Process (10847): Sending signal. PID: 10847 SIG: 9
09-30 11:00:21.330 E/AndroidRuntime(10847): Error reporting crash
09-30 11:00:21.330 E/AndroidRuntime(10847): android.os.DeadObjectException
09-30 11:00:21.330 E/AndroidRuntime(10847): at android.os.BinderProxy.transact(Native Method)
09-30 11:00:21.330 E/AndroidRuntime(10847): at android.app.ActivityManagerProxy.handleApplication Crash(ActivityManagerNative.java:2950)
09-30 11:00:21.330 E/AndroidRuntime(10847): at com.android.internal.os.RuntimeInit$UncaughtHandle r.uncaughtException(RuntimeInit.java:96)
09-30 11:00:21.330 E/AndroidRuntime(10847): at java.lang.ThreadGroup.uncaughtException(ThreadGrou p.java:693)
09-30 11:00:21.330 E/AndroidRuntime(10847): at java.lang.ThreadGroup.uncaughtException(ThreadGrou p.java:690)
09-30 11:00:21.330 E/AndroidRuntime(10847): at dalvik.system.NativeStart.main(Native Method)
09-30 11:00:21.335 W/Sensors ( 8861): sensorservice died [0x1523e0]
09-30 11:00:21.335 W/Sensors ( 2219): sensorservice died [0xb9640]
(...)
Click to expand...
Click to collapse
My phone has version I9100BVLPH (Orange 4.0.4), update only by KIES. I think that my phone has some garbage from previous version, because I had 2.3*, 4.0.3 and now 4.0.4, all update by KIES. I remember that someday it works.
How can I fix it? My phone is rooted.
Thank you for help.
Fryderyk
------
Sorry, please move my post to Q&A.
dedykjp said:
Hello!
I have some problem with my Samsung Galaxy S2. In normal system, when some application crash then can see message box to force shutdown application and additional report a problem to the author. Unfortunately I don't have it. When some application crash then first my phone freeze for about 1-2 minutes (but upper toolbar works) and later my phone restart, but it's not a full booting.
I connected my phone to the PC and run logcat so I got this logs. Parsebin: 8db3G1c5 . I thing this part of logs is interesting:
My phone has version I9100BVLPH (Orange 4.0.4), update only by KIES. I think that my phone has some garbage from previous version, because I had 2.3*, 4.0.3 and now 4.0.4, all update by KIES. I remember that someday it works.
How can I fix it? My phone is rooted.
Thank you for help.
Fryderyk
------
Sorry, please move my post to Q&A.
Click to expand...
Click to collapse
First post your ROM and kernel details; Goto Settings - About phone, and post everything you see
Jokesy said:
First post your ROM and kernel details; Goto Settings - About phone, and post everything you see
Click to expand...
Click to collapse
Model: GT-I9100
Android version: 4.0.4
Modem: I9100BVLPE
Kernel: 3.0.15-I9100BVLPH-CL969772 [email protected] #3 SMP PREEMPT Mon Jul 30 15:28:47 KST 2012
Version: IMM76D.BVLPH
dedykjp said:
Model: GT-I9100
Android version: 4.0.4
Modem: I9100BVLPE
Kernel: 3.0.15-I9100BVLPH-CL969772 [email protected] #3 SMP PREEMPT Mon Jul 30 15:28:47 KST 2012
Version: IMM76D.BVLPH
Click to expand...
Click to collapse
Flash a custom kernel first, then perform a factory data reset
Jokesy said:
Flash a custom kernel first, then perform a factory data reset
Click to expand...
Click to collapse
I don't wanna flash a custom kernel or perform a factory data reset. Maybe it's a better way to fix it. Maybe clear some files or directory in /data directory.
dedykjp said:
I don't wanna flash a custom kernel or perform a factory data reset. Maybe it's a better way to fix it. Maybe clear some files or directory in /data directory.
Click to expand...
Click to collapse
5 minutes ago I discovered a reason of my problem. The reason was rooted phone. After unroot my phone works well. It means that when application crash then I get ANR. Again after root my phone I also get this exception.
Why? Is this only my problem or it's global, but not discovered to now.
device is:
ST70208-1
Android Version: 4.1.1
Kernel Version: 3.0.8+
Build: ST70208-1_20130808_INT
aka Trekstor Surftab Ventos 7.0 HD
As Chrome crashes at start even after factory reset and all known measures did not help,
i installed root/su/bussybox/ssh-server and did a logcat.
...
/ActivityManager( 3603): Start proc com.android.chrome:sandboxed_process0 for service com.android.chrome/org.chromium.content.app.SandboxedProcessService0: pid=24769 uid=99001 gids={}
I/LibraryLoader(24750): loading: chromeview
E/Main (24750): Failed to load native library.
E/Main (24750): org.chromium.content.common.ProcessInitException
E/Main (24750): at org.chromium.content.app.LibraryLoader.loadNow(Unknown Source)
E/Main (24750): at com.google.android.apps.chrome.Main$InitializerContinuation.loadLibraryNow(Unknown Source)
E/Main (24750): at com.google.android.apps.chrome.Main$InitializerContinuation.access$400(Unknown Source)
E/Main (24750): at com.google.android.apps.chrome.Main$InitializerContinuation$2.run(Unknown Source)
E/Main (24750): at android.os.Handler.handleCallback(Handler.java:615)
E/Main (24750): at android.os.Handler.dispatchMessage(Handler.java:92)
E/Main (24750): at android.os.Looper.loop(Looper.java:137)
E/Main (24750): at android.os.HandlerThread.run(HandlerThread.java:60)
E/Main (24750): Caused by: java.lang.UnsatisfiedLinkError: Cannot load library: link_image[1891]: 2487 could not load needed library 'libjnigraphics.so' for 'libchromeview.so' (load_library[1093]: Library 'libjnigraphics.so' not found)
E/Main (24750): at java.lang.Runtime.loadLibrary(Runtime.java:370)
E/Main (24750): at java.lang.System.loadLibrary(System.java:535)
E/Main (24750): ... 8 more
E/Trace (24769): error opening trace file: No such file or directory (2)
D/OpenGLRenderer(24750): Enabling debug mode 0
I/SandboxedProcessService(24769): Creating new SandboxedProcessService pid=24769
I/LibraryLoader(24769): loading: chromeview
E/SandboxedProcessService(24769): Failed to load native library, exiting sandboxed process
E/SandboxedProcessService(24769): org.chromium.content.common.ProcessInitException
E/SandboxedProcessService(24769): at org.chromium.content.app.LibraryLoader.loadNow(Unknown Source)
E/SandboxedProcessService(24769): at org.chromium.content.app.SandboxedProcessService$2.run(Unknown Source)
E/SandboxedProcessService(24769): at java.lang.Thread.run(Thread.java:856)
E/SandboxedProcessService(24769): Caused by: java.lang.UnsatisfiedLinkError: Cannot load library: link_image[1891]: 2487 could not load needed library 'libjnigraphics.so' for 'libchromeview.so' (load_library[1093]: Library 'libjnigraphics.so' not found)
E/SandboxedProcessService(24769): at java.lang.Runtime.loadLibrary(Runtime.java:370)
E/SandboxedProcessService(24769): at java.lang.System.loadLibrary(System.java:535)
E/SandboxedProcessService(24769): ... 3 more
..
"ls -al" in /system/lib showed amongst others 4 suspicious shared native libraries:
-rw------- 1 0 0 59996 Mar 17 18:50 libjnigraphics.so
-rw------- 1 0 0 10017928 Mar 17 18:18 libmsrmsdk.so
-rw------- 1 0 0 8577120 Mar 17 18:50 libreader.so
-rw------- 1 0 0 135864 Mar 17 18:51 librss.so
all other libs here look like that:
-rw-r--r-- 1 0 0 31363328 Aug 1 2008 libchromeview.so
The 4 suspects have a date 03/17/2016 and no read permission for group/other but the rest all are 8/1/2008 and have the permissions.
I did "chmod 644" to them.
But i had to remount /system as readwrite.
Seams it is normaly readonly!
And i had to do "su"!
How/Who can change anything here in /system/lib?
Chrom still crashes but logcat shows it is not because it does not find the libjnigraphics.so.
Now it crashes with a dump.
I think it is because libchromeview.so loads the dependency libjnigraphics.so,
but that is an newer version than that it was linked against.
After i left the device in the morning on the day this **** happend, it was working ok.
In the evening (my wife had used it) there was tones of error msg at starting of many apps (Contacts, Playstore, ...).
So i did a factory reset, but the Chrome problem persists (Google+ and Maps where *****y too but worked after update).
I did not switch of auto update.
So i think some update messed it up, or my wife had switched it hard off during something important/longer lasting, as it was not responsive to her.
But how can a normal apk do something to /system?!
Any ideas why Chrome still uses these old native shared libraries?
Please can somebody who is having the same device, send me a "ls -al" of /system/lib.
Any ideas how to fix Chrome (PlayStore)?
Greetings
Michael
PS: This was the 3rd factory reset i had to make because some update managed to screwed it. But the two before worked, ok.
The stock "firmware" of this device looks as if it was the 5th test build a new greenhorn system builder.
And ADB does not work. The device announces itself only in recovery mode to USB (of course "USB debugging" is on).
Hi everyone,
like many other Pixel 6 and 6 Pro owners, I have experienced frequent random reboots with my Pixel 6 since getting it November 2021. They became less frequent with the monthly updates, but never went fully away and occur often when it's very inconvenient. But as reports about this seem to be quieting down, I'm now worrying that for me it's not a software problem after all. So I'm reaching out to see if anyone has a suggestion for me to try out before RMA'ing it.
The reboot frequency varies from sometimes multiple reboots per day to sometimes a whole week without a single reboot. They do occur seemingly random without any apparent causal connection to a specific app. It frequently happens at night while charging when not in use, which I only notice the next morning when I get prompted to enter my SIM PIN. I feel as if it happens more often, when I open up a app which was not running before (independent on which it is) or when I try to share a resource (e.g., an image) from one app to another. Although this might only be a skewed perception on my end, as it is a bit more annoying when trying to get something done in contrast to it happening when checking the time.
The phone mostly reboots quite fast and seems back to normal, but it is also common to reboot multiple times before being able to fully enter the pin. There have also been around 6 times since November, where it bootlooped for a couple of minutes and in the process either partially corrupting the file system or executing some type of silent system restore, which causes some apps (not all) to loose state. Most notably for me is that I have to log into Spotify again, whereas most other apps tend to keep their state. One time this week it actually managed to corrupt the Google Photos app, so that it did not start even when booted into safe mode, with adb logs showing a failure to load an asset:
Code:
java.io.IOException: Failed to load asset path /data/app/~~vPG9I1zFLLjLpeetfcyDEw==/com.google.android.apps.photos-toH31kBPyggrkw-bTY1jdw==/split_config.xxhdpi.a
However, this was easily resolved by reinstalling it (or rather uninstalling and reinstalling updates) via the play store. It's more an example on how far reaching the effects of the reboots are.
Far more common is it for some apps to refuse to open app, after such a reboot until I manually reboot the phone again. Google Chrome is the app I notice it the most with, but it occasionally happens, with other apps as well. The stacktrace seems to point to an issue with GMS:
Code:
Abort message: 'Check failed: found_virtual Didn't find oat method index for virtual method: <<invalid-method-idx-314717208>>'
For troubleshooting I so far attempted the following steps:
Factory reset: While it seemed to decrease the frequency at first it went back to the usual amount of reboots within a a few day. I did restore a backup, but I don't really have the time to not do this without knowing for certain, that it would fix the issue.
Safe mode: I have not yet been able to reproduce a crash while booted in safe mode, but it was also difficult to purposefully get a reboot while booted normally.
Uninstalled certain apps: I did remove certain apps, which are not that common or are targeted towards an older Android version. This did not result in any noticeable change. Testing every app individually (as suggested by the Pixel phone help) is obviously unfeasible.
Launcher: I recently also tried out a third-party launcher instead of the stock launcher, as the launcher also regularly crashed on me and I've read in a post that this this could help. Unfortunately, this had no impact on the issue.
In the first few months, I was patiently waiting for new system updates to increase stability, since this seemed also really common. While these updates did fix some issues, e.g., frequent camera related crashes, the reboots described where not addressed. While there are some posts about such issues, I haven't found any detailed reports of a issue similar to mine. I hence tried to use adb to look into it myself. It took me a while to purposefully crash the system, while having adb logcat running, but eventually I succeeded (first time I was really happy to see a crash ). As a disclaimer, my phone is neither rooted nor having an unlocked bootloader, but I enabled the developer settings solely for the purpose of debugging this issue. I have not installed or sideloaded any apps, so all software running on the device originated from the Google Play Store. I also tried to irregularly submit crash logs via the phone settings app, but this unfortunately often resulted in another crash.
Unfortunately, I did not find any obvious cause in for the crashes in the logs:
Spoiler: adb log of reboot
Code:
05-21 22:34:10.360 27825 27835 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfe2a3f72ff1577a2 in tid 27835 (ReferenceQueueD), pid 27825 (system_server)
05-21 22:34:11.145 3626 3626 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-21 22:34:11.146 3626 3626 F DEBUG : Build fingerprint: 'google/oriole/oriole:12/SP2A.220505.002/8353555:user/release-keys'
05-21 22:34:11.146 3626 3626 F DEBUG : Revision: 'MP1.0'
05-21 22:34:11.146 3626 3626 F DEBUG : ABI: 'arm64'
05-21 22:34:11.146 3626 3626 F DEBUG : Timestamp: 2022-05-21 22:34:10.510538789+0200
05-21 22:34:11.146 3626 3626 F DEBUG : Process uptime: 0s
05-21 22:34:11.146 3626 3626 F DEBUG : Cmdline: system_server
05-21 22:34:11.146 3626 3626 F DEBUG : pid: 27825, tid: 27835, name: ReferenceQueueD >>> system_server <<<
05-21 22:34:11.146 3626 3626 F DEBUG : uid: 1000
05-21 22:34:11.146 3626 3626 F DEBUG : tagged_addr_ctrl: 0000000000000001
05-21 22:34:11.146 3626 3626 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfe2a3f72ff1577a2
[...]
05-21 22:34:11.146 3626 3626 F DEBUG : backtrace:
05-21 22:34:11.146 3626 3626 F DEBUG : #00 pc 0000000000169138 /system/lib64/libandroid_runtime.so (Binder_destroy(void*)+32) (BuildId: 12e324c49b27b9ecc2ae009f81539f74)
05-21 22:34:11.146 3626 3626 F DEBUG : #01 pc 0000000000011978 /apex/com.android.art/javalib/arm64/boot-core-libart.oat (art_jni_trampoline+104) (BuildId: 4e753cd7907e1b76a7c177f849bba17384e0f9f6)
05-21 22:34:11.146 3626 3626 F DEBUG : #02 pc 0000000000032dd8 /apex/com.android.art/javalib/arm64/boot-core-libart.oat (libcore.util.NativeAllocationRegistry$CleanerThunk.run+72) (BuildId: 4e753cd7907e1b76a7c177f849bba17384e
0f9f6)
05-21 22:34:11.146 3626 3626 F DEBUG : #03 pc 0000000000308af8 /apex/com.android.art/javalib/arm64/boot.oat (sun.misc.Cleaner.clean+136) (BuildId: ad9ee401645a5135206a62ff86fc2ef5cdc29120)
05-21 22:34:11.146 3626 3626 F DEBUG : #04 pc 00000000000cbd1c /apex/com.android.art/javalib/arm64/boot.oat (java.lang.ref.ReferenceQueue.enqueueLocked+236) (BuildId: ad9ee401645a5135206a62ff86fc2ef5cdc29120)
05-21 22:34:11.146 3626 3626 F DEBUG : #05 pc 00000000000cbe1c /apex/com.android.art/javalib/arm64/boot.oat (java.lang.ref.ReferenceQueue.enqueuePending+172) (BuildId: ad9ee401645a5135206a62ff86fc2ef5cdc29120)
05-21 22:34:11.146 3626 3626 F DEBUG : #06 pc 00000000000472d4 /apex/com.android.art/javalib/arm64/boot-core-libart.oat (java.lang.Daemons$ReferenceQueueDaemon.runInternal+244) (BuildId: 4e753cd7907e1b76a7c177f849bba17384e0f9
f6)
05-21 22:34:11.146 3626 3626 F DEBUG : #07 pc 000000000001f32c /apex/com.android.art/javalib/arm64/boot-core-libart.oat (java.lang.Daemons$Daemon.run+332) (BuildId: 4e753cd7907e1b76a7c177f849bba17384e0f9f6)
05-21 22:34:11.146 3626 3626 F DEBUG : #08 pc 00000000001bf19c /apex/com.android.art/javalib/arm64/boot.oat (java.lang.Thread.run+76) (BuildId: ad9ee401645a5135206a62ff86fc2ef5cdc29120)
05-21 22:34:11.146 3626 3626 F DEBUG : #09 pc 00000000002ca764 /apex/com.android.art/lib64/libart.so (art_quick_invoke_stub+548) (BuildId: 34e3dd028e2e682b63a512d6a4f1b5eb)
05-21 22:34:11.146 3626 3626 F DEBUG : #10 pc 000000000030e980 /apex/com.android.art/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*)+156) (BuildId: 34e3dd028e2e682
b63a512d6a4f1b5eb)
05-21 22:34:11.146 3626 3626 F DEBUG : #11 pc 00000000003c1db4 /apex/com.android.art/lib64/libart.so (art::JValue art::InvokeVirtualOrInterfaceWithJValues<art::ArtMethod*>(art::ScopedObjectAccessAlreadyRunnable const&, _jobje
ct*, art::ArtMethod*, jvalue const*)+380) (BuildId: 34e3dd028e2e682b63a512d6a4f1b5eb)
05-21 22:34:11.146 3626 3626 F DEBUG : #12 pc 00000000004578ec /apex/com.android.art/lib64/libart.so (art::Thread::CreateCallback(void*)+992) (BuildId: 34e3dd028e2e682b63a512d6a4f1b5eb)
05-21 22:34:11.146 3626 3626 F DEBUG : #13 pc 00000000000b1590 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204) (BuildId: 53a228529316d67f22e241dd17ea9b9e)
05-21 22:34:11.146 3626 3626 F DEBUG : #14 pc 0000000000050fac /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 53a228529316d67f22e241dd17ea9b9e)
05-21 22:34:11.353 28015 28111 E AndroidRuntime: FATAL EXCEPTION: SysUiBg
05-21 22:34:11.353 28015 28111 E AndroidRuntime: Process: com.android.systemui, PID: 28015
05-21 22:34:11.353 28015 28111 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
05-21 22:34:11.456 30401 30438 E AndroidRuntime: FATAL EXCEPTION: highpool[1]
05-21 22:34:11.456 30401 30438 E AndroidRuntime: Process: com.google.android.gms.persistent, PID: 30401
05-21 22:34:11.456 30401 30438 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
05-21 22:34:11.465 30401 3636 E AndroidRuntime: FATAL EXCEPTION: [com.google.android.gms.chimera.container.intentoperation.PersistentIntentOperationChimeraService-Executor] idle
05-21 22:34:11.465 30401 3636 E AndroidRuntime: Process: com.google.android.gms.persistent, PID: 30401
05-21 22:34:11.465 30401 3636 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
05-21 22:34:11.475 21792 21857 E AndroidRuntime: FATAL EXCEPTION: XmppMessageRouter
05-21 22:34:11.475 21792 21857 E AndroidRuntime: Process: com.whatsapp, PID: 21792
05-21 22:34:11.475 21792 21857 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
05-21 22:34:11.483 28999 28999 E AndroidRuntime: FATAL EXCEPTION: main
05-21 22:34:11.483 28999 28999 E AndroidRuntime: Process: com.google.android.googlequicksearchbox:interactor, PID: 28999
05-21 22:34:11.483 28999 28999 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
This pattern seems to be consistent for every reboot, while the originating process seems to vary with mostly being Google Apps (YouTube/Google Photos) or built in services, such as search, phone, or wellbeing. The tombstones also don't reveal any more helpful information (at least to me).
I'm now at the point where I exhausted all options that I have and I'm not sure how to proceed. I have been hesitant on RMA'ing, because other people shared that this hasn't resolved the issue for them and it would be a larger inconvenience. My remaining theories are either that I have faulty hardware (e.g., bad memory), there is still a bigger os/firmware bug that causes these crashes, or if there really is an app that I installed that is causing this.
I was hoping that with this rather detailed post, someone may be able to point me in a direction on how to proceed and if my third theory is correct, how to investigate which app is the culprit. Thanks to everyone who takes the time to read this rather lengthy post, I really appreciate it!
ech0_de said:
I'm now at the point where I exhausted all options that I have and I'm not sure how to proceed. I have been hesitant on RMA'ing,
Click to expand...
Click to collapse
Random restarts shouldn't be tolerated with a Pixel running stock Android unmodified. Even modified the phone should be more stable than what you described. I've had a few problems, I root and sideload an app or two, but never had random restarts except for the time an OTA update borked the phone. Clean flashing the factory build fixed me up and it's been fine since. Maybe clean flashing the latest factory build (released today?) will fix yours too. If not Google owes you a stable replacement.
manjaroid said:
Random restarts shouldn't be tolerated with a Pixel running stock Android unmodified. Even modified the phone should be more stable than what you described. I've had a few problems, I root and sideload an app or two, but never had random restarts except for the time an OTA update borked the phone. Clean flashing the factory build fixed me up and it's been fine since. Maybe clean flashing the latest factory build (released today?) will fix yours too. If not Google owes you a stable replacement.
Click to expand...
Click to collapse
my pixel 6 is heavy modified and tweaked and i have 200 user apps installed
as far as i know i have never had a random reboot.
send that in for repair, or replacement.
Hi! I'm having this issue as well, since day one. Still haven't figured out a pattern, it happens while using the phone, while idle, hot and cold. I know the phone is gonna restart because it gets laggy for a couple seconds.
Funny thing is these reboots don't affect the up time. It may go for hundreds of hours even if I got many restarts.
Around a month ago the reboots stopped for around a week but then started happening again.
It is more frequent while using Twitter, Instagram and heavy games for a while. Already factory restored but still.
I contacted google but they told me this is not a known issue and I should send it for repair. The lack of patterns and frequency gave me the hope of this not being a hardware issue but I'm losing it after six months.
Hi! Hope this helps you: after running logcat and experiencing three reboots during it, seems that I finally found the APK that was generating the random reboots, a DirecTV app. Already uninstalled it and today is my third day in a row w/o reboots. I honestly hope this finally solves the issue, and encourage you to keep searching for the app causing the same on your pixel.
Thanks for the replies. After the latest update that manjaroid mentioned, I only had two reboots, but still fully random. I now gave up and RMA it, to see if they find an issue (or hopefully replace the faulty phone).
@nova90 how did you narrow it down to this app? Did the the exception stack traces in the logs originate from this app? Might be helpful for me or others, stumbling across this post in the future
Hi! I used my pixel for a couple of hours while connected to my laptop running logcat. Got two or three reboots and the errors pointed to that app (something like "com.directv... fatal exception..." "The system has died"). There where more than one error in every reboot, but only one repeating was the one related to DirecTV. Currently two weeks in a row with no reboots. It was actually my only issue with pixel, so I'm pretty happy with it.