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.
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.
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 :/
Good evening people.Today i got my Amazfit delivered to my home and i am REALLY excited!
i finally have my modular clock!
My idea is to create a github organization and gather all dev in one place.
Do you like to dev ?
Are you interested to make roms and other root stuff ?
Do you like designing watch faces ?
Lets gather em all!...If you are interested please tell me your email and i will add u as admin to the organization.
The organization that i just created:
https://github.com/amazfitDev
thanks for all!
Being an Recognized Developer i know how android stuff works. I am really interested on that clock and i would like to dev on that. Any other dev around ?
From the image on your GitHub, I assume you have a Pace. There's been a few development projects surrounding it already:
Modified version of Amazfit app with many features: https://github.com/edotassi/AmazMod
Custom Springboard pages: https://github.com/KieronQuinn/AmazfitSpringboardPluginExample
→ Music page: https://github.com/KieronQuinn/AmazfitSpringboardMusic
→ Calendar page: https://github.com/GreatApo/AmazfitPaceCalendarWidget
→ Rearrange pages: https://github.com/KieronQuinn/AmazfitSpringboardSettings
Phone > Watch > Phone communication in apps: https://github.com/KieronQuinn/AmazfitCommunication
→ Internet Companion: https://github.com/KieronQuinn/AmazfitInternetCompanion
→ Train Times: https://forum.xda-developers.com/smartwatch/amazfit/app-uk-train-times-live-train-t3779955/page1
Custom watchfaces: https://forum.xda-developers.com/sm...t-huamiwatchfaces-based-custom-t3760814/page1
Step notify app: https://github.com/KieronQuinn/AmazfitStepNotify
My GitHub username is obvious from the links but the email linked to that account is quinny898 (at) gmail (dot) com
Quinny899 said:
From the image on your GitHub, I assume you have a Pace. There's been a few development projects surrounding it already:
Modified version of Amazfit app with many features: https://github.com/edotassi/AmazMod
Custom Springboard pages: https://github.com/KieronQuinn/AmazfitSpringboardPluginExample
→ Music page: https://github.com/KieronQuinn/AmazfitSpringboardMusic
→ Calendar page: https://github.com/GreatApo/AmazfitPaceCalendarWidget
→ Rearrange pages: https://github.com/KieronQuinn/AmazfitSpringboardSettings
Phone > Watch > Phone communication in apps: https://github.com/KieronQuinn/AmazfitCommunication
→ Internet Companion: https://github.com/KieronQuinn/AmazfitInternetCompanion
→ Train Times: https://forum.xda-developers.com/smartwatch/amazfit/app-uk-train-times-live-train-t3779955/page1
Custom watchfaces: https://forum.xda-developers.com/sm...t-huamiwatchfaces-based-custom-t3760814/page1
Step notify app: https://github.com/KieronQuinn/AmazfitStepNotify
My GitHub username is obvious from the links but the email linked to that account is quinny898 (at) gmail (dot) com
Click to expand...
Click to collapse
amazfitmod. is it rom ? or mod ? for flashing rule ?
brmbjn said:
amazfitmod. is it rom ? or mod ? for flashing rule ?
Click to expand...
Click to collapse
It's a modded CN Amazfit app, with support for Strava and other features.
As Quinny mentioned, there are some devs around, including the the ones providing some multilingual ROMs. Most of us have a github account (this is my project).
Και στο Facebook μπορείς να μας βρεις
There are many reputable developers here in one place...
I apologize, maybe it's not a good question at this place, but:
what is the ADB command line that shows the QR code for on active Amazfit watch display?
gidano said:
There are many reputable developers here in one place...
I apologize, maybe it's not a good question at this place, but:
what is the ADB command line that shows the QR code for on active Amazfit watch display?
Click to expand...
Click to collapse
adb shell am start -n com.huami.watch.ble/com.huami.watch.qrcode.QrActivity
You need to be running as root first with "adb root"
https://gitlab.com/Neuer_User/PACEfied_AmazFit/wikis/Faq
Thank you very much! :highfive:
wow...
its true that there are many projects around...but why everything is separated ? we better get unified / under a same git org ?
i love all those actions...i am still playing with watchfaces though...still non-rooted.i want to investigate the hardware of the clock (MIPS device-chances for ROM build? etc)
wishing the best!
side said:
wow...
its true that there are many projects around...but why everything is separated ? we better get unified / under a same git org ?
i love all those actions...i am still playing with watchfaces though...still non-rooted.i want to investigate the hardware of the clock (MIPS device-chances for ROM build? etc)
wishing the best!
Click to expand...
Click to collapse
They're separated because this forum isn't segmented like device forums are, and nobody had set up an organisation until now.
I've been looking at the possibility of getting custom ROMs working, Huami won't release the kernel source so that limits us a lot, but using a generic MIPS build of 8.0 built for a IoT board (optimistic I know) I got it as far as graphics crashing because of an incompatible driver. There is a supposedly compatible open source driver for the GPU in the MESA project, but I don't have the knowledge to build it (or the space). Maybe you could help there?
Quinny899 said:
They're separated because this forum isn't segmented like device forums are, and nobody had set up an organisation until now.
I've been looking at the possibility of getting custom ROMs working, Huami won't release the kernel source so that limits us a lot, but using a generic MIPS build of 8.0 built for a IoT board (optimistic I know) I got it as far as graphics crashing because of an incompatible driver. There is a supposedly compatible open source driver for the GPU in the MESA project, but I don't have the knowledge to build it (or the space). Maybe you could help there?
Click to expand...
Click to collapse
the gallium3d stuff ? i think i can help there
side said:
the gallium3d stuff ? i think i can help there
Click to expand...
Click to collapse
Yes, in theory all I need is the driver itself and it may continue booting. I'd also like to get a device tree set up using the generic source as base, but no kernel source is annoying
Damn... you 2 speak your own language....
Right now I'm at home and not on a phone, here's a dump of everything I know and have got working on the Pace in terms of custom ROMs. I have a second device I use for testing, and it's currently got something I hacked together from this on it. I used that ROM's system image as base, and copied across the following files from Pacefied (that I can remember, it was a few weeks ago now):
/system/bin/logcatd
/system/lib/sdcard
I also used a compare program to copy across drivers and device specific files, and went about reading the logcat and copying missing things, getting it further and further into the boot. The graphics drivers (libEGL_VIVANTE) aren't compiled for Oreo, so they have namespace issues. After copying way too many files to /system/vendor/lib/egl (this alone is a massive red flag, they should not be there at all), it complains something being missing:
Code:
05-05 17:43:17.572 7503 7503 E vndksupport: Could not load /vendor/lib/egl/libEGL_VIVANTE.so from sphal namespace: dlopen failed: /system/vendor/lib/egl/libcutils.so: cannot locate "_memset16"....
05-05 17:43:17.572 7503 7503 E libEGL : load_driver(/vendor/lib/egl/libEGL_VIVANTE.so): unknown
05-05 17:43:17.573 7503 7503 F libEGL : couldn't find an OpenGL ES implementation
05-05 17:43:17.573 7503 7503 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 7503 (surfaceflinger), pid 7503 (surfaceflinger)
05-05 17:43:17.671 7560 7560 I crash_dump32: obtaining output fd from tombstoned, type: kDebuggerdTombstone
05-05 17:43:17.671 7560 7560 E libc : failed to connect to tombstoned: No such file or directory
05-05 17:43:17.671 7560 7560 I crash_dump32: performing dump of process 7503 (target tid = 7503)
05-05 17:43:17.672 7560 7560 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-05 17:43:17.672 7560 7560 F DEBUG : Build fingerprint: 'Android/aosp_ci20/ci20:8.1.0/OPM1.171019.011/mousew03081157:userdebug/test-keys'
05-05 17:43:17.672 7560 7560 F DEBUG : Revision: '00000001'
05-05 17:43:17.672 7560 7560 F DEBUG : ABI: 'mips'
05-05 17:43:17.672 7560 7560 F DEBUG : pid: 7503, tid: 7503, name: surfaceflinger >>> /system/bin/surfaceflinger <<<
05-05 17:43:17.672 7560 7560 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
05-05 17:43:17.679 7560 7560 F DEBUG : Abort message: 'couldn't find an OpenGL ES implementation'
05-05 17:43:17.679 7560 7560 F DEBUG : zr 00000000 at 00000001 v0 00000000 v1 bd35f1fe
05-05 17:43:17.679 7560 7560 F DEBUG : a0 00001d4f a1 00001d4f a2 00000006 a3 00000000
05-05 17:43:17.679 7560 7560 F DEBUG : t0 00000000 t1 00000001 t2 fffffffc t3 00000000
05-05 17:43:17.679 7560 7560 F DEBUG : t4 fffffffc t5 77eeb000 t6 00000000 t7 65704f20
05-05 17:43:17.680 7560 7560 F DEBUG : s0 7719c7e0 s1 00001d4f s2 00001d4f s3 7fa964c0
05-05 17:43:17.680 7560 7560 F DEBUG : s4 00000004 s5 00000001 s6 77825304 s7 77825048
05-05 17:43:17.680 7560 7560 F DEBUG : t8 00000000 t9 7709a380 k0 773a1e0b k1 00000000
05-05 17:43:17.680 7560 7560 F DEBUG : gp 7719c7e0 sp 7fa96488 s8 773a0000 ra 7709a6d0
05-05 17:43:17.680 7560 7560 F DEBUG : hi 00000000 lo 00000000 bva 77c77fe0 epc 7709a3c0
05-05 17:43:17.686 7560 7560 F DEBUG :
05-05 17:43:17.686 7560 7560 F DEBUG : backtrace:
05-05 17:43:17.686 7560 7560 F DEBUG : #00 pc 000193c0 /system/lib/libc.so (syscall+64)
05-05 17:43:17.686 7560 7560 F DEBUG : #01 pc 000196d0 /system/lib/libc.so (abort+164)
05-05 17:43:17.686 7560 7560 F DEBUG : #02 pc 00021e0b /system/lib/libEGL.so
So this driver isn't compatible, clearly. At this point I went and researched the GPU of the watch. It has a Vivante GC 1000, which has been used in a couple of Android devices before but they're ARM and ancient so are not helpful. However, the etnaviv project has created some support for it, I'm not sure how helpful it is though: https://github.com/etnaviv/etna_viv, it's also been merged into the mesa driver. Android x86 uses Mesa, so it's definitely compatible with Android, but we need a tree set up first as far as I know
That's where my experience ends. I've never built Android from source before, nor do I have the space for it at the moment. I'd be willing to assist in setting up a tree, though. The earlier linked CI20 code is here: https://github.com/MIPS/CI20_android
Also remembered this: I think this is the commit that's causing the driver to be incompatible: https://android.googlesource.com/platform/bionic/+/b0cf928, as _memset16 is in a different place than it's expected to be. Using a newer lib in the egl folder does not fix this.
@Quinny899
perfect findings mate. Everything seems really nice! and your try to make stuff working is really respected!....although i got some bad news .
device tree and kernel sources are mandatory...even if we build the device tree,there is no chance to get the kernel source code ...and there is no chance to build AOSP from source without the kernel source.
my opinion is to push huami release the kernel source. Since its Linux Kernel (there is no doubt about it ) its licensed as GPL. They have to release it. i can get some FOSS maniacs to push them
edit1:
This device tree ( https://github.com/MIPS/CI20_android/tree/dev-mips-oreo-mr1 ) could do the job but still...no kernel.although the device tree is not that hard to be built.i can do that.
For a flashable zip built by AOSP sources we need:
device tree + proprietary libs ( those u copied ) and a kernel .the rest could be unified or something
edit2:
Even if i got a flashable rom i cant test it on my self.i dont have 2nd watch and i wont risk it
edit3:
about the commit u said...its easy to be reverted.as i see its a standalone commit.doesnt depend on any other repo...really easy to be reverted but i dont think that reverting it fixes the driver problem. it may be fixed from runtime side but not kernel/module side
edit4:
about the log u posted.is it a last_kmsg ? or dmsg ? or simple log ?
whatever it is i can confirm its bionic's issue since libc blows up
The log is a snippet of a logcat, the kernel doesn't actually crash so the last message wouldn't be of use as far as I know
If you want to send any test stuff to me, I have a second device I can flash on (using dd - nice and dangerous) to see if it works
In terms of the lack of kernel, could we use the generic MIPS kernel from AOSP and just not flash the boot image maybe?
This is the response I got when I asked for the kernel source:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Quinny899 said:
The log is a snippet of a logcat, the kernel doesn't actually crash so the last message wouldn't be of use as far as I know
If you want to send any test stuff to me, I have a second device I can flash on (using dd - nice and dangerous) to see if it works
In terms of the lack of kernel, could we use the generic MIPS kernel from AOSP and just not flash the boot image maybe?
This is the response I got when I asked for the kernel source:
Click to expand...
Click to collapse
hmmm about the generic kernel .i dont know...those "generic" solutions usually doesnt work but we can try it .keep in mind that a source-built kernel product is different than the one the vendor is providing. kernel and rom are strictly tided....there is no chance to build THE SAME kernel as the vendor's one. a source-built one needs patches to be bootable.
about their response.really ? if its linux kernel(which i am sure it is) thats against the law and they will have serious problems O_O'
side said:
hmmm about the generic kernel .i dont know...those "generic" solutions usually doesnt work but we can try it .keep in mind that a source-built kernel product is different than the one the vendor is providing. kernel and rom are strictly tided....there is no chance to build THE SAME kernel as the vendor's one. a source-built one needs patches to be bootable.
about their response.really ? if its linux kernel(which i am sure it is) thats against the law and they will have serious problems O_O'
Click to expand...
Click to collapse
A lot of Chinese vendors ignore the GPL, Xiaomi themselves aren't great at releasing sources either
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.