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.
Related
Hi!
I recently bought a Freelander PD20, for which I read great reviews and praise regarding its GPS capabilities, especially with its low price.
When I first tried it, the GPS worked perfectly, but then after switching it off and on again, it never came back. The device isn't able to get my location and no GPS icon is ever shown.
Also, when connected to my computer and EClipse Logcat is constantly showing the following:
01-08 09:33:09.360: D/gps_tcc_libgps(1204): '!
01-08 09:33:09.360: D/gps_tcc_libgps(1204): '
01-08 09:33:09.370: D/gps_tcc_libgps(1204): '[email protected]@'
01-08 09:33:09.390: D/gps_tcc_libgps(1204): '@'
01-08 09:33:11.360: D/gps_tcc_libgps(1204): '`
01-08 09:33:11.360: D/gps_tcc_libgps(1204): '
01-08 09:33:11.380: D/gps_tcc_libgps(1204): 'a?+?B??+?(????.
01-08 09:33:11.380: D/gps_tcc_libgps(1204): '
01-08 09:33:11.390: D/gps_tcc_libgps(1204): '??(?k?j?k??)
01-08 09:33:11.390: D/gps_tcc_libgps(1204): '
01-08 09:33:11.400: D/gps_tcc_libgps(1204): ''
Click to expand...
Click to collapse
I haven't found any posts with a problem similar to this in this device, but maybe someone found the same issue with another one or knows what the solution might be. I'd appreciate any help, I am reluctant to think this is a hardware malfunction since the device is like a week old and GPS worked the first time.
Hello,
I am posting here regarding a bug affecting a few custom roms. Some applications (mainly games) relying on expansion files (OBB) cannot be run on some roms (whatever the device). Apparently the bug is affecting Kitkat roms only. It's been reported a few times on the forum but never been fixed. When the affected app is trying to mount the obb file an exception is raised:
https://play.google.com/store/apps/details?id=com.simulationcurriculum.skysafari4pro&hl=en
Code:
09-20 17:14:36.128: D/MountService(839): Couldn't call DefaultContainerService to fetch OBB info for /storage/emulated/0/Android/obb/com.simulationcurriculum.skysafari4pro/main.401.com.simulationcurriculum.skysafari4pro.obb
https://play.google.com/store/apps/details?id=org.imperiaonline.android.v6
Code:
09-20 17:13:36.948: D/MountService(839): Couldn't call DefaultContainerService to fetch OBB info for /storage/emulated/0/Android/obb/org.imperiaonline.android.v6/main.57.org.imperiaonline.android.v6.obb
Most of the applications are paid app so it's not easy for rom developers to test and also only a few (known) apps are affected.
Here's the message in the log for different apps having the issue.
Apparently, it's related to a "RemoteException" error.
Other apps are affected:
https://play.google.com/store/apps/details?id=com.camouflaj.republique
"Custom ROMs are not officially supported, and may cause the error “Unfortunately, Package Access Helper has stopped.”
I understand only a few users/apps are affected but it would be great if a fix could be found. I have tested myself a few roms on different devices. (Nexus 7, 4 and OPO). AOKP, Carbon, Slim, AICP are affected. However CM11 and AOSPA (Paranoid) don't have the issue. Stock roms on Nexus devices are fine too.
Most of the apps are paid games so it does not make testing easy if you don't own the game. However "imperiaonline" is free with IAP. (No need to pay anything to reproduce the issue). So it's a good app for reproducing the bug.
I tried to have a look myself, but I don't have the required knowledge to understand the source of the issue. Most apps requiring OBB files are working fine, only a few are affected.
Maybe people having the same issue could post the name of the app here. Make sure it's exactly the same issue. (Have a look in the log).
I hope this is a good place to post considering it is not rom or device specific. Hopefully it will help to track the issue and fix it.
Roms teams are doing a fantastic job but I understand it is not a critical bug and it might no be easy to fix.
Some interesting links:
http://forum.slimroms.net/topic/2026-package-access-helper-has-stopped/
http://bugs.aokp.co/issues/293
I too have experienced this issue today on liquid smooth(Z1), when trying to play republique. Although the game launched there was no sound and the above mentioned dialogue showed up.
Techpenguin5 said:
I too have experienced this issue today on liquid smooth(Z1), when trying to play republique. Although the game launched there was no sound and the above mentioned dialogue showed up.
Click to expand...
Click to collapse
Same occured for me with Republique on my nexus 7 2013 (flo) on Paranoid Android 4.6 beta 5
I have this problem with BBC Cbeebies storytime app on my Nexus 7 2013 running Exodus rom (4.4.4). Not encountered it with any other app I have including paid apps. The app ran fine with the stock 4.4.4 rom. Love to know if there's a fix as my daughter loves the app!
Hello, I am a game developer working on a game that is affected by this. It is causing many issues with custom ROMs for us and we are desperately trying to come to a solution. We have noted that this specific error and symptoms may not be related to just a custom ROM, though our best repro case is Paranoid Android on a Nexus device. We have reports of this issue and symptoms from those running the Franco kernel, and those using various Xposed Framework modules. We have several crash logs from the Package Access Helper (/system/priv-app/DefaultContainerService.apk) service and we are willing to cooperate with knowledgable ROM developers to solve this issue.
I will locate the crash logs we have and submit them as soon as I can.
Crash Logs as promised:
Code:
I/ActivityManager(521): Start proc com.android.defcontainer for service com.android.defcontainer/.DefaultContainerService: pid=5923 uid=10003 gids={50003, 1028, 1015, 1023, 2001, 1035}
A/libc(5923): invalid address or address of corrupt block 0x6ab8a8f4 passed to dlfree
A/libc(5923): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 5935 (Binder_2)
I/DEBUG(125): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG(125): Build fingerprint: 'google/nakasi/grouper:4.4.4/KTU84P/1227136:user/release-keys'
I/DEBUG(125): Revision: '0'
I/DEBUG(125): pid: 5923, tid: 5935, name: Binder_2 >>> com.android.defcontainer <<<
I/DEBUG(125): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad
I/DEBUG(125): Abort message: 'invalid address or address of corrupt block 0x6ab8a8f4 passed to dlfree'
I/DEBUG(125): r0 00000000 r1 4013d11e r2 deadbaad r3 40140c60
I/DEBUG(125): r4 6ab8a8f4 r5 4014b180 r6 4000c000 r7 6ab8a8fc
I/DEBUG(125): r8 0000002d r9 4014b384 sl 00000000 fp 6ab8a984
I/DEBUG(125): ip 00000001 sp 6ab8a8c8 lr 4010e783 pc 4010e784 cpsr 60070030
I/DEBUG(125): d0 2064657372666c64 d1 2073736572646461
I/DEBUG(125): d2 657264646120726f d3 6f6320666f207373
I/DEBUG(125): d4 756f6d61632e6d6f d5 7065722e6a616c66
I/DEBUG(125): d6 2f657571696c6275 d7 37322e6863746170
I/DEBUG(125): d8 0000000000000000 d9 0000000000000000
I/DEBUG(125): d10 0000000000000000 d11 0000000000000000
I/DEBUG(125): d12 0000000000000000 d13 0000000000000000
I/DEBUG(125): d14 0000000000000000 d15 0000000000000000
I/DEBUG(125): d16 4000000000000000 d17 3fc999999999999a
I/DEBUG(125): d18 4146605000000000 d19 0065004e005f0061
I/DEBUG(125): d20 3f8948b0fcd6e9e0 d21 3fe555b0aaeac752
I/DEBUG(125): d22 3fd24998d6307188 d23 3fcc7288e957b53b
I/DEBUG(125): d24 3fc74721cad6b0ed d25 3fc2f112df3e5244
I/DEBUG(125): d26 40026bb1bbb55516 d27 4000000000000000
I/DEBUG(125): d28 40008df2d49d41f1 d29 3fb0f4a31edab38b
I/DEBUG(125): d30 3ff0000000000000 d31 3f4de16b9c24a98f
I/DEBUG(125): scr 80000010
I/DEBUG(125): backtrace:
I/DEBUG(125): #00 pc 00011784 /system/lib/libc.so (dlfree+1191)
I/DEBUG(125): #01 pc 0000dcc3 /system/lib/libc.so (free+10)
I/DEBUG(125): #02 pc 00010aa1 /system/lib/libandroidfw.so (android::eek:bbFile::parseObbFile(int)+296)
I/DEBUG(125): #03 pc 00010cc3 /system/lib/libandroidfw.so (android::eek:bbFile::readFrom(char const*)+54)
I/DEBUG(125): #04 pc 0008703f /system/lib/libandroid_runtime.so
I/DEBUG(125): #05 pc 0001dbcc /system/lib/libdvm.so (dvmPlatformInvoke+112)
I/DEBUG(125): #06 pc 0004e123 /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+398)
I/DEBUG(125): #07 pc 00026fe0 /system/lib/libdvm.so
I/DEBUG(125): #08 pc 0002dfa0 /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
I/DEBUG(125): #09 pc 0002b638 /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
I/DEBUG(125): #10 pc 0006057d /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+336)
I/DEBUG(125): #11 pc 0004ce89 /system/lib/libdvm.so
I/DEBUG(125): #12 pc 0006d32b /system/lib/libandroid_runtime.so
I/DEBUG(125): #13 pc 00071aab /system/lib/libandroid_runtime.so
I/DEBUG(125): #14 pc 00019225 /system/lib/libbinder.so (android::BBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+60)
I/DEBUG(125): #15 pc 0001d799 /system/lib/libbinder.so (android::IPCThreadState::executeCommand(int)+508)
I/DEBUG(125): #16 pc 0001db17 /system/lib/libbinder.so (android::IPCThreadState::getAndExecuteCommand()+38)
I/DEBUG(125): #17 pc 0001db8d /system/lib/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+48)
I/DEBUG(125): #18 pc 000219f5 /system/lib/libbinder.so
I/DEBUG(125): #19 pc 0000ea5d /system/lib/libutils.so (android::Thread::_threadLoop(void*)+216)
I/DEBUG(125): #20 pc 0004d915 /system/lib/libandroid_runtime.so (android::AndroidRuntime::javaThreadShell(void*)+68)
I/DEBUG(125): #21 pc 0000e58f /system/lib/libutils.so
I/DEBUG(125): #22 pc 0000d228 /system/lib/libc.so (__thread_entry+72)
I/DEBUG(125): #23 pc 0000d3c0 /system/lib/libc.so (pthread_create+240)
I/DEBUG(125): stack:
I/DEBUG(125): 6ab8a888 fffffea0
I/DEBUG(125): 6ab8a88c 4000eae8
I/DEBUG(125): 6ab8a890 41b10c50 /dev/ashmem/dalvik-heap (deleted)
I/DEBUG(125): 6ab8a894 07520650
I/DEBUG(125): 6ab8a898 6ab8a8f4
I/DEBUG(125): 6ab8a89c 4014b180
I/DEBUG(125): 6ab8a8a0 4000c000
I/DEBUG(125): 6ab8a8a4 4010faf9 /system/lib/libc.so
I/DEBUG(125): 6ab8a8a8 4013d11e /system/lib/libc.so
I/DEBUG(125): 6ab8a8ac 6ab8a8bc
I/DEBUG(125): 6ab8a8b0 40140c60 /system/lib/libc.so
I/DEBUG(125): 6ab8a8b4 4010e783 /system/lib/libc.so (dlfree+1190)
I/DEBUG(125): 6ab8a8b8 4013d11e /system/lib/libc.so
I/DEBUG(125): 6ab8a8bc 6ab8a8f4
I/DEBUG(125): 6ab8a8c0 40140c60 /system/lib/libc.so
I/DEBUG(125): 6ab8a8c4 00000000
I/DEBUG(125): #00 6ab8a8c8 40147000 /system/lib/libc.so
I/DEBUG(125): 6ab8a8cc 2abbb038
I/DEBUG(125): 6ab8a8d0 00000000
I/DEBUG(125): 6ab8a8d4 00000030
I/DEBUG(125): 6ab8a8d8 4176e5c8
I/DEBUG(125): 6ab8a8dc 4010acc5 /system/lib/libc.so (free+12)
I/DEBUG(125): #01 6ab8a8e0 00000030
I/DEBUG(125): 6ab8a8e4 4018caa5 /system/lib/libandroidfw.so (android::eek:bbFile::parseObbFile(int)+300)
I/DEBUG(125): #02 6ab8a8e8 00000000
I/DEBUG(125): 6ab8a8ec 4010df23 /system/lib/libc.so (dlmalloc+4254)
I/DEBUG(125): 6ab8a8f0 00000010
I/DEBUG(125): 6ab8a8f4 00000004
I/DEBUG(125): 6ab8a8f8 4010ce85 /system/lib/libc.so (dlmalloc)
I/DEBUG(125): 6ab8a8fc 00000030
I/DEBUG(125): 6ab8a900 01059983
I/DEBUG(125): 6ab8a904 07520650
I/DEBUG(125): 6ab8a908 4176e5c8
I/DEBUG(125): 6ab8a90c 400fbd80
I/DEBUG(125): 6ab8a910 0000002d
I/DEBUG(125): 6ab8a914 1d300009
I/DEBUG(125): 6ab8a918 1d600005
I/DEBUG(125): 6ab8a91c 4176e5c8
I/DEBUG(125): 6ab8a920 4000eaf8
I/DEBUG(125): 6ab8a924 4018ccc7 /system/lib/libandroidfw.so (android::eek:bbFile::readFrom(char const*)+58)
I can tell you we are using unencrypted OBB files that are quite large in size, so large that we had issues with the JOBB tool similar to those mentioned in several Stack Overflow posts (<stackoverflow_url>/questions/15832039/jobb-crash-fat-full). Sorry, my account has too few posts for direct outside links, so you'll have to add the URL there.
nightchaser said:
Hello, I am a game developer working on a game that is affected by this. It is causing many issues with custom ROMs for us and we are desperately trying to come to a solution. We have noted that this specific error and symptoms may not be related to just a custom ROM, though our best repro case is Paranoid Android on a Nexus device. We have reports of this issue and symptoms from those running the Franco kernel, and those using various Xposed Framework modules. We have several crash logs from the Package Access Helper (/system/priv-app/DefaultContainerService.apk) service and we are willing to cooperate with knowledgable ROM developers to solve this issue.
I will locate the crash logs we have and submit them as soon as I can.
Click to expand...
Click to collapse
Thank you very much for this report. I am sure you are not the only game developer having the issue. I developed a few apps myself, some using obb but I never managed to reproduce the issue. This is a really annoying bug. I have been in touch with some roms developers with no luck. I really hope a fix can be found. I will try to point some rom developers to this thread, I suppose it could be a great place to discuss the issue and get some feedback. Thanks again.
I'd LOVE to find the fix to this, be it in the ROM or app. I use Sky Safari and I can only use it on my daughters tablet as my phone and tablet both on AOKP 4.4.4 won't run it; gets this error.
If anyone comes up with a workaround or something to test, I'll be happy to try it.
I have some bad news regarding this bug. I managed to reproduce it already on some LP roms. I know it is very early and most roms are in 'alpha' state. However on my OnePlus One device, I tried two different roms and two apps known for having the issue on Jellybean:
(Skysafari and Imperia Online v6).
// Roms tested:
- http://forum.xda-developers.com/oneplus-one/development/daily-stock-unofficial-cm12-builds-t2948099
- http://forum.xda-developers.com/oneplus-one/development/rom-cm11-temasek-build-t2870743
On the 'stock unofficial' CM12 everything is good. Both apps are working fine.
On 'Temasek' build (which is based on CM12 but with some 'extra' commits/features from different roms), the issue is there.
No issues with Skysafari on 'stock' Nexus 4 and N7 (2013).
Anyway, I started to look at the logs and the error is a bit different. (But the issue is similar apparently, the obb cannot be mounted). There are a few interesting things though:
// Skysafari
Code:
I/ActivityManager( 867): START u0 {cmp=com.simulationcurriculum.skysafari4pro/com.southernstars.skysafari.SkySafariActivity} from uid 10082 on display 0
I/System.out( 4954): onCreate: com.southernstars.skysafari.SkySafariActivity
I/System.out( 4954): OBB is Readable
I/System.out( 4954): OBB is Writable
D/STORAGE_MNT( 4954): MOUNT SUCCESSFULLY QUEUED
W/ContextImpl( 867): [B]Calling a method in the system process without a qualified user[/B]: android.app.ContextImpl.bindService:1757 com.android.server.MountService$ObbActionHandler.connectToService:2761 com.android.server.MountService$ObbActionHandler.handleMessage:2640 android.os.Handler.dispatchMessage:102 android.os.Looper.loop:135
...
I/SkySafari( 4954): Path to obb:
I/SkySafari( 4954): Path to assets: /storage/emulated/0/Android/data/com.simulationcurriculum.skysafari4pro/files/
I/SkySafari( 4954): Creating CSkyChart
I/SkySafari( 4954): Finished nativeInit.
E/Vold ( 257): Failed to find mounted volume for /storage/usbdisk/Android/data/com.simulationcurriculum.skysafari4pro/files/
W/Vold ( 257): Returning OperationFailed - no handler for errno 0
//Imperia Online V6
Code:
D/ObbExpansionManager( 5411): Checking if /storage/emulated/0/Android/obb/org.imperiaonline.android.v6/main.70.org.imperiaonline.android.v6.obb mounted after 300ms...
W/ObbExpansionManager( 5411): Mount not queued. Retry...
W/ContextImpl( 867): Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1757 com.android.server.MountService$ObbActionHandler.connectToService:2761 com.android.server.MountService$ObbActionHandler.handleMessage:2640 android.os.Handler.dispatchMessage:102 android.os.Looper.loop:135
D/ObbExpansionManager( 5411): Mount state: 20
D/ObbExpansionManager( 5411): Checking if /storage/emulated/0/Android/obb/org.imperiaonline.android.v6/main.70.org.imperiaonline.android.v6.obb mounted after 300ms...
I hope this will be useful and rom developers will finally be able to fix this issue. More tests need to be done on different roms/devices. However I thought it would be a good idea to mention early, before more and more features are added to custom roms.
[edit]
I tested the latest build of AICP rom and contrary to JB the issue is not present on LP !
I've had the problem but in an another manner
Well, what has happens to me is completely different but similar in the same time everytime I try and install ANY app or game it pops up with message saying ^ unfortunaltey, package access helper has stopped. This is my problem I hope u can find a fix to it and if not I hope it was usefull
Vasili00 said:
Well, what has happens to me is completely different but similar in the same time everytime I try and install ANY app or game it pops up with message saying ^ unfortunaltey, package access helper has stopped. This is my problem I hope u can find a fix to it and if not I hope it was usefull
Click to expand...
Click to collapse
Nope, your ROM is busted. Not the same issue.
Anyway.. Sky Safari fixed something on their end a few weeks ago, working on all ROMs for me now. I wonder what they changed.
khaytsus said:
Nope, your ROM is busted. Not the same issue.
Anyway.. Sky Safari fixed something on their end a few weeks ago, working on all ROMs for me now. I wonder what they changed.
Click to expand...
Click to collapse
Really ? Would you mind giving more details about which roms/devices you tried ? Thanks.
_Man0waR_ said:
Really ? Would you mind giving more details about which roms/devices you tried ? Thanks.
Click to expand...
Click to collapse
It apparently was busted on official L, which I think honestly is the ONLY reason they fixed it. So it works there, also works on AOKP 4.4.4. I don't have any other ROMs on active devices.
It's a market update, should have already seen that update if Sky Safari was one you were having issues with?
khaytsus said:
It apparently was busted on official L, which I think honestly is the ONLY reason they fixed it. So it works there, also works on AOKP 4.4.4. I don't have any other ROMs on active devices.
It's a market update, should have already seen that update if Sky Safari was one you were having issues with?
Click to expand...
Click to collapse
To be honest, I have not done much testing recently on KK and mainly checked the state of the bug on L roms. I am definitely using Skysafari, but it's not the main app I'm using for testing this bug. Personally I never had the issue on the official L on my Nexus 4 and 7 (2013). The last time I tried Skysafari was a few weeks ago, just after an update (I remember that the whole obb file had to be downloaded again). I was still having the issue on my OnePlus One using 'Temasek' L rom. I will probably try again soon. It would be nice to know what was the fix though.
Thanks a lot anyway.
[edit] I have just found this. See last post. (Maybe this is where you heard about the fix ?)
http://www.cloudynights.com/topic/486890-sky-safari-android-5-nexus-10-issue/
[edit2[ Indeed I have just tested the latest Skysafari on 'Temasek' L rom (OnePlus One) and it's fine now ! They definitely 'fixed' something in the app. I will try to contact the developers to know a bit more about the fix and what was wrong. It's probably something similar in the other games/apps with the same issue. It looks like the issue is with the apps and not the custom roms.
_Man0waR_ said:
To be honest, I have not done much testing recently on KK and mainly checked the state of the bug on L roms. I am definitely using Skysafari, but it's not the main app I'm using for testing this bug. Personally I never had the issue on the official L on my Nexus 4 and 7 (2013). The last time I tried Skysafari was a few weeks ago, just after an update (I remember that the whole obb file had to be downloaded again). I was still having the issue on my OnePlus One using 'Temasek' L rom. I will probably try again soon. It would be nice to know what was the fix though.
Thanks a lot anyway.
[edit] I have just found this. See last post. (Maybe this is where you heard about the fix ?)
http://www.cloudynights.com/topic/486890-sky-safari-android-5-nexus-10-issue/
[edit2[ Indeed I have just tested the latest Skysafari on 'Temasek' L rom (OnePlus One) and it's fine now ! They definitely 'fixed' something in the app. I will try to contact the developers to know a bit more about the fix and what was wrong. It's probably something similar in the other games/apps with the same issue. It looks like the issue is with the apps and not the custom roms.
Click to expand...
Click to collapse
Eh? I heard about the fix in the Sky Safari changelog. It's gone now, as there has been another update, but the changelog clearly said that they fixed problems with L and should fix issues with custom ROMs. It did for me on AOKP 4.4.4, and it works on L on my Nexus 7 2013.
Temasek's 16.8 in ks01lte also presenting this with Republique. The game support did not helped me to find a solution. I know it's a paid game but I also have my reasons to use custom rom (specially because I work with a lot of things that only a custom rom have).
Someone got this fixed and the changelog posted?
leleobhz said:
Temasek's 16.8 in ks01lte also presenting this with Republique. The game support did not helped me to find a solution. I know it's a paid game but I also have my reasons to use custom rom (specially because I work with a lot of things that only a custom rom have).
Someone got this fixed and the changelog posted?
Click to expand...
Click to collapse
They have to fix it on their end... Various games or apps have fixed this issue after enough users complained about it. It even affects some stock ROMs or devices, I think a few were listed in this thread. I think I had problems with one app on a stock Nexus 7 ROM at one point.
But what to tell them? It's hard to convince them they they can or should fix it.
nightchaser said:
Hello, I am a game developer working on a game that is affected by this. It is causing many issues with custom ROMs for us and we are desperately trying to come to a solution. We have noted that this specific error and symptoms may not be related to just a custom ROM, though our best repro case is Paranoid Android on a Nexus device. We have reports of this issue and symptoms from those running the Franco kernel, and those using various Xposed Framework modules. We have several crash logs from the Package Access Helper (/system/priv-app/DefaultContainerService.apk) service and we are willing to cooperate with knowledgable ROM developers to solve this issue.
I will locate the crash logs we have and submit them as soon as I can.
Click to expand...
Click to collapse
I just found out that if I use apkeditor to change the installation location to internal the recompiled apk will install, I tried it with a couple of apps I couldn't install on my galaxy s4 with lollipop and now I can
So far for me it was Exoplanet Explorer and Turbo Dismount, and on both I just had to change the default location to internal.
EDIT: Nintendo is not allowing their Miitomo app to run on Android phones with root, jailbroken iPhones, and some other conditions. The app will crash immediately or shortly after launch. To bypass this on Android phones install Xposed, then install RootCloak and ChrisJosten's Miitomo Bypass modules and reboot your device. Add Miitomo to RootCloak's list of cloaked apps, and be sure to 'Thanks!' ChrisJosten for his help.
Original text:
Tonight Nintendo has first released their Miitomo app exclusively to Japan, however the app apparently already has a full English translation.
Unfortunately it does not appear to run on rooted devices, as reported by a few users here. One user reported success with RootCloak, however others and myself have not had such success. I have a Galaxy S5 with CyanogenMod 13.0. The app starts with a black screen for a second before crashing back to the home screen. Tried clearing any cached data for the app. Any other ideas?
From what I gathered at Neogaf, it seems to be a CM problem, but I have no further idea
Not on CM and it's happening with me too.
On 5.1.1 with root, fix would be appreciated.
Looks to me to be a problem with cyanogen.
Here's an interesting line in the debug:
03-17 11:51:55.399 8036 8036 I art : Thread[1,tid=8036,Native,Thread*=0xb4d76500,peer=0x74f993b0,"main"] recursive attempt to load library "/data/app/com.nintendo.zaaa-2/lib/arm/libNuanceVocalizer.so"
03-17 11:51:55.618 8036 8036 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 8036 (m.nintendo.zaaa)
03-17 11:51:55.618 253 253 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
03-17 11:51:55.618 253 253 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
03-17 11:51:55.618 253 253 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
03-17 11:51:55.671 813 1584 D NetlinkSocketObserver: NeighborEvent{elapsedMs=68823126, 192.168.32.1, [544A009C3344], RTM_NEWNEIGH, NUD_STALE}
03-17 11:51:55.720 253 253 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-17 11:51:55.720 253 253 F DEBUG : Build fingerprint: 'oneplus/bacon/A0001:5.1.1/LMY48B/YOG4PAS1N0:user/release-keys'
03-17 11:51:55.720 253 253 F DEBUG : Revision: '0'
03-17 11:51:55.720 253 253 F DEBUG : ABI: 'arm'
03-17 11:51:55.720 253 253 F DEBUG : pid: 8036, tid: 8036, name: m.nintendo.zaaa >>> com.nintendo.zaaa <<<
03-17 11:51:55.720 253 253 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
03-17 11:51:55.739 253 253 F DEBUG : r0 00000000 r1 00001f64 r2 00000006 r3 00000000
03-17 11:51:55.739 253 253 F DEBUG : r4 b6fcdb88 r5 00000006 r6 b6fcdb38 r7 0000010c
03-17 11:51:55.739 253 253 F DEBUG : r8 12ca4180 r9 b4d76500 sl 12c62c30 fp 70f4d6b0
03-17 11:51:55.739 253 253 F DEBUG : ip 00000000 sp beb02ef8 lr b6d1a42d pc b6d1cb90 cpsr 200d0010
03-17 11:51:55.745 253 253 F DEBUG :
03-17 11:51:55.745 253 253 F DEBUG : backtrace:
03-17 11:51:55.745 253 253 F DEBUG : #00 pc 00049b90 /system/lib/libc.so (tgkill+12)
03-17 11:51:55.745 253 253 F DEBUG : #01 pc 00047429 /system/lib/libc.so (pthread_kill+36)
03-17 11:51:55.745 253 253 F DEBUG : #02 pc 0001bbc3 /system/lib/libc.so (raise+10)
03-17 11:51:55.745 253 253 F DEBUG : #03 pc 0001846d /system/lib/libc.so (__libc_android_abort+36)
03-17 11:51:55.745 253 253 F DEBUG : #04 pc 000164cc /system/lib/libc.so (abort+4)
03-17 11:51:55.745 253 253 F DEBUG : #05 pc 009bf848 /data/app/com.nintendo.zaaa-2/lib/arm/libcocos2dcpp.so (Java_jp_co_nintendo_NativeSystem_nativeAbort+8)
03-17 11:51:55.745 253 253 F DEBUG : #06 pc 011218fd /data/app/com.nintendo.zaaa-2/oat/arm/base.odex (offset 0x985000)
03-17 11:51:56.064 253 253 F DEBUG :
03-17 11:51:56.064 253 253 F DEBUG : Tombstone written to: /data/tombstones/tombstone_03
03-17 11:51:56.064 253 253 E DEBUG : AM write failed: Broken pipe
Click to expand...
Click to collapse
Android N develop a no-go too
On launch of miitomo if running the android N developer preview you get a gray screen and that's it
I'm having the same problem. Rooted Wileyfox Swift running Cyanogen OS 12.1.1.
It's not just root
Have the same problem. But I'm bone stock 5.0 Note 3.
Galaxy S4 Resurrection Rom
Rooted - Crash
Un-rooted - Crash
Root Cloak - Crash
Nexus 10 CM13
Rooted - Crash
Un-rooted - Crash
Root Cloak - Crash
Galaxy S2 Stock
Crash
Literally cant get any device to work.
Thanks for the responses. I mean I wouldn't be surprised if Nintendo wanted to prevent cheating, but if this is a more widespread issue it might get fixed legitimately.
I'm using my Alcatel OT Idol X with Slimkat 4.4.2 and I'm getting crashes on both rooted and cloaked Miitomo. I haven't tried my other devices yet, but I doubt they'll fare out well.
app was crashing on my rooted Nexus 5X running stock 6.0.1, with ElementalX Kernel. All I did to fix it was use RootCloak and add Miitomo to the list. Bang, straight into the game
Same thing happening here.
Running on Android 4.4.4 with stock ROM.
Sent from my Micromax A065
harsh2909 said:
Same thing happening here.
Running on Android 4.4.4 with stock ROM.
Sent from my Micromax A065
Click to expand...
Click to collapse
Also here on Android 4.4.2 Rooted LG G3.
Nexus 5x - Systemless Root - Purenexus - Franco Kernel
Crashes every time.
Works fine on my wife's stock Samsung 5.
More and more apps are refusing to run on rooted devices. This should not be surprising. Some are even looking for xposed and monitoring the forums here to see how people are getting around it so they can block it.
Can confirm... I have a Motorola Droid 4 running CM11 and it crashes.
I tried updating to CM13 nightly, still crashes.
I tried disabling root from within CM, still crashes.
I went back to stock (rooted), still crashes.
I used superSU to unroot stock, it loaded.
This is infuriating, at least with Pokémon Shuffle it would load and let you play and just stop you from doing tournaments due to being rooted. This fake app crash GS is annoying. Someone needs to fix this :/
drfsupercenter said:
Can confirm... I have a Motorola Droid 4 running CM11 and it crashes.
I tried updating to CM13 nightly, still crashes.
I tried disabling root from within CM, still crashes.
I went back to stock (rooted), still crashes.
I used superSU to unroot stock, it loaded.
This is infuriating, at least with Pokémon Shuffle it would load and let you play and just stop you from doing tournaments due to being rooted. This fake app crash GS is annoying. Someone needs to fix this :/
Click to expand...
Click to collapse
Well see that's the thing is that it is not broken. Root is a security risk and an issue for game developers even Google is making root harder to get on Many devices and sooner or later unless you have a nexus root may not even be an option.
That's just stupid, I use root for things like taking backups of my phone, not hacking stupid games to begin with.
I do find it funny how the first thing that comes to people's mind when you tell them you have a rooted/jailbroken phone is that you must be some kind of pirate. You don't even need root to install .apks, and most people don't know enough to actually hack games like that anyway. (Pro tip: the leaderboards are kept server-side, it's not as simple as just modifying your data files)
drfsupercenter said:
That's just stupid, I use root for things like taking backups of my phone, not hacking stupid games to begin with.
I do find it funny how the first thing that comes to people's mind when you tell them you have a rooted/jailbroken phone is that you must be some kind of pirate. You don't even need root to install .apks, and most people don't know enough to actually hack games like that anyway. (Pro tip: the leaderboards are kept server-side, it's not as simple as just modifying your data files)
Click to expand...
Click to collapse
Well see the thing is root makes those things possible. There are apps that use root to hack the games. I won't mention them here as they are banned. Also it's not the leader boards they are worried about. It's things like in app purcheses.
You have to understand there are very real risks with root. An app can get granted root and do all types of things including ransom based viruses.
It's just something you will have to get used to. The older android gets the harder root will be to get.
I'm sure there will always be ways. While 99% of users don't need root abilities, there are those of us who are power users who have an actual use for it.
Even the newest phones have root exploits (I hate that word exploit, sure it's exploiting a locked-down system arbitrarily set by the manufacturer, but we should be able to do it like a real machine and choose if we want to allow root access or not!).... looks like the S7 has one already.
Hello,
i have compiled from source a lineageos kernel, installed it on my device, but when i turn on my device, i see a black screen :/
i have perform a logcat through ADB and i see some errors but i'm not sure if i go in the righ direction...
i tried to understand the log (hard due to lack of experience in this domain) but i see warnings about "/system/vendor/lib/libIMGegl_SGX540_120.so" file (others vendor files).
i read in some tutorial that user who want to compile lineageos rom (kernel too ???) must extract "proprietary blobs" (drivers) for samsung devices.
but where i put these files in my kernel source folder???
maybe i go in the wrong direction!!!!????
my bootlog.txt: https://files.fm/u/cym5w24v"]https://files.fm/u/cym5w24v
please, give me some time to help me, i try and try and try, search and search and search... i progress some times but there, i'm facing to a rock :'(
I remain at your disposal if you want more details in my kernel compilation procedure!
[EDIT]
in my bootlog i can see this:
01-08 11:34:33.358 2692 2692 E ti_hwc : Framebuffer HAL not opened before HWC
01-08 11:34:33.358 2692 2692 E SurfaceFlinger: composer device failed to initialize (Bad address)
01-08 11:34:33.358 2692 2692 E SurfaceFlinger: ERROR: failed to open framebuffer (Not a typewriter), aborting
01-08 11:34:33.358 2692 2692 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 2692 (surfaceflinger)
i tried to google the "SurfaceFlinger" error but without success :/
GCam_v7.0.009-v4.4.apk
https://www.celsoazevedo.com/files/android/google-camera/f/changelog777
Until LG releases the Android 10 update, you can't run 7.2 or higher. Gcam 7.0 is currently the highest version that will run on Pie. See link above.
This version works pretty well, supports motion photos, and enhances images well. It supports the wide lens when you enable the tele button. (I know this is counter intuitive, but it works)
All in all, LG's own stock Camera app is better. The LG app takes higher resolution, offers extensive manual control, has more stable features, and is more reliable..
I would only recommend GCam for motion photos, smaller file sizes, and Night Mode.
did you try to install Android 10 beta (preview) and try Gcam 7.2?
I have tried the higher versions on Pie and it works...
Some people live different regions and these are using LG G8s ThinQ model, so GCam link is working on G8s ThinQ model?
Yes, it is working on LG G8s.
hudy01 said:
Yes, it is working on LG G8s.
Click to expand...
Click to collapse
Thank very much
edmondt said:
I have tried the higher versions on Pie and it works...
Click to expand...
Click to collapse
I tried many different versions but they keep crashing since 7.0 after taking photo (only panorama mode will save the photo). How did you managed it to work? Can you upload settings for the GCam? Thank you :good:
JohnyCJ48 said:
I tried many different versions but they keep crashing since 7.0 after taking photo (only panorama mode will save the photo). How did you managed it to work? Can you upload settings for the GCam? Thank you :good:
Click to expand...
Click to collapse
Have you tried uninstalling completely then install the new version?
edmondt said:
Have you tried uninstalling completely then install the new version?
Click to expand...
Click to collapse
Yes, complete uninstall, delete app data, different settings in the app even used settings for G8 or V50. I'm on G8s stock android pie without root. Version 7.0 works without problem.
Try GCam_7.2.010_Urnyx05-v2.2
Located at: https://www.celsoazevedo.com/files/android/google-camera/f/changelog982/
edmondt said:
Try GCam_7.2.010_Urnyx05-v2.2
Located at: https://www.celsoazevedo.com/files/android/google-camera/f/changelog982/
Click to expand...
Click to collapse
I've tried that one too. Here is my logcat with applied G8 settings downloaded from that site too with 24 error lines, it has less lines than the default settings (more than 80 lines) so I assume it's more functional. I'm curious why I'm propably the only one with this problem. Thank you for help.
--- 9. 2. 2020 21:58:41 ----
02-09 21:49:06.424 14146 14462 F native : warpfield.cc:94 Check failed: cliff > 0 Invalid distortion curve.
02-09 21:49:06.424 14146 14462 F native : terminating.
02-09 21:49:06.425 14146 14462 F libc : Fatal signal 6 (SIGABRT), code -6 (SI_TKILL) in tid 14462 (End Payload Fra), pid 14146 (eaurora.snapcam)
02-09 21:49:06.731 14484 14484 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
02-09 21:49:06.731 14484 14484 F DEBUG : Build fingerprint: 'lge/betalm_e/betalm:9/PKQ1.190302.001/193601632981c:user/release-keys'
02-09 21:49:06.731 14484 14484 F DEBUG : Revision: '12'
02-09 21:49:06.731 14484 14484 F DEBUG : ABI: 'arm64'
02-09 21:49:06.731 14484 14484 F DEBUG : pid: 14146, tid: 14462, name: End Payload Fra >>> org.codeaurora.snapcam <<<
02-09 21:49:06.732 14484 14484 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
02-09 21:49:06.732 14484 14484 F DEBUG : Abort message: 'warpfield.cc:94 Check failed: cliff > 0 Invalid distortion curve.
02-09 21:49:06.732 14484 14484 F DEBUG : '
02-09 21:49:06.732 14484 14484 F DEBUG : x0 0000000000000000 x1 000000000000387e x2 0000000000000006 x3 0000000000000008
02-09 21:49:06.732 14484 14484 F DEBUG : x4 63656843202a2a2a x5 63656843202a2a2a x6 63656843202a2a2a x7 72756c696166206b
02-09 21:49:06.732 14484 14484 F DEBUG : x8 0000000000000083 x9 fc147cc1f89c0fa0 x10 0000000000000000 x11 fffffffc7ffffbdf
02-09 21:49:06.732 14484 14484 F DEBUG : x12 0000000000000001 x13 0a2a2a2a203a6563 x14 0000000000000030 x15 aaaaaaaaaaaaaaab
02-09 21:49:06.732 14484 14484 F DEBUG : x16 0000007a85e0f2a8 x17 0000007a85d30d60 x18 00000079c3001078 x19 0000000000003742
02-09 21:49:06.732 14484 14484 F DEBUG : x20 000000000000387e x21 00000079d094b588 x22 0000000000000061 x23 0000000000000001
02-09 21:49:06.732 14484 14484 F DEBUG : x24 00000079d0947ef8 x25 00000079de73ce5c x26 00000079d046cca0 x27 0000000000000003
02-09 21:49:06.732 14484 14484 F DEBUG : x28 0000000000000003 x29 00000079d0947c00
02-09 21:49:06.732 14484 14484 F DEBUG : sp 00000079d0947bc0 lr 0000007a85d22394 pc 0000007a85d223bc
02-09 21:49:06.736 14484 14484 F DEBUG :
02-09 21:49:06.736 14484 14484 F DEBUG : backtrace:
02-09 21:49:06.736 14484 14484 F DEBUG : #00 pc 00000000000223bc /system/lib64/libc.so (abort+116)
02-09 21:49:06.736 14484 14484 F DEBUG : #01 pc 0000000000f3edf8 /data/data/org.codeaurora.snapcam/files/libpatched_jni.so (offset 0xc2f000)
---- 9. 2. 2020 21:58:41 ----
I'm on a Sprint LG G8, OTA updated to Android 10, cleaned and wiped after the update.
No guarantees it will work, but that's the last resort to make it work? Also, you can try other gcam builts; just because it says it's for a certain phone, in my experience it might work on your device... I installed another built of GCam for my Galaxy Tab S4 and it works great by trail and error.
Urnyx 7.2.010 v2.2 is working great for me. The only thing that isn't working is slow motion, but the stock camera has that anyway.
Urnyx latest version has fixed wide angle and telephoto buttons. https://f.celsoazevedo.com/file/cfiles/gcm1/GCam_7.2.010_Urnyx05-v2.3.apk
Now wide angle button correctly switches to the wide angle lens. The 7.2 GCam is now mostly perfect.
Just curious if anyone else notice that Gcam photos are to too yellow/warm with a greenish tint on the g8. Is there any way to adjust this setting or fix it?
jericho246 said:
Urnyx latest version has fixed wide angle and telephoto buttons. https://f.celsoazevedo.com/file/cfiles/gcm1/GCam_7.2.010_Urnyx05-v2.3.apk
Now wide angle button correctly switches to the wide angle lens. The 7.2 GCam is now mostly perfect.
Click to expand...
Click to collapse
So on my G8, T-Mobile, enabling the 2nd lens then trying to use it crashes the app. Every subsequent open it crashes. Have to clear data to open with no crashes.
pre4speed said:
So on my G8, T-Mobile, enabling the 2nd lens then trying to use it crashes the app. Every subsequent open it crashes. Have to clear data to open with no crashes.
Click to expand...
Click to collapse
There is no telephoto on US variants of G8, so the 2x will not work. You can disable telephoto in settings and that option will disappear. To use the second wide angle lens you would click on the 0.6 option.
synaethe said:
There is no telephoto on US variants of G8, so the 2x will not work. You can disable telephoto in settings and that option will disappear. To use the second wide angle lens you would click on the 0.6 option.
Click to expand...
Click to collapse
Copy. Thank you. I was hoping to find a feature in this app of being able to take still photos while recording video like Samsung has. Unfortunately, that feature isn't available in this app either, like the LG camera app. ?
Two issues I've found with Urnyx05: GCam_7.3.018_Urnyx05-v1.0.apk. Front camera sometimes takes a couple seconds to focus and if you take a bunch of pictures at once, the app will close. I've found that turning off motion feature stops it from crashing. Oh and of course slow mo doesn't work.
GCam_7.3.018_Urnyx05-v1.5.APK works almost perfectly on my LG G8 (LM-G820TM, Android version: 10, software version: G820TM20d)
Slow Motion remains problematic. But even Slow Motion is closer to working; no more black screen, it now records, but with a still image and audio. Confoundingly, the preview of the slow motion shots looks perfect.