Good Morning,
I've had the Moto G5 since January and successfully rooted it with Magisk 11.6 / no verity opt encrypt 5.1 / twrp cedric 3.1.1-0 (stock ROM). It was working perfectly until last week when the camera suddenly stopped working, followed all the "camera problems" guides such as clear cache etc. and it disn't resolve the issue. Did a factory reset, re-locked the bootloader and re-flashed with stock firmware - this time with the November security patched version retgb NPP25.137-93. The camera started working again, so I'm assuming it isn't a hardware issue. Re-rooted and re-installed my apps and again the camera has been working fine then suddenly it stopped again. It does seem to have coincided with updating apps on the play store, pretty sure it took and camera app update ok and my gut feeling it that one of the Google app updates is causing the problem.
Installed apps include BBC iplayer, BT wifi, Gallery, Gallery vault, tomtom go, MX player, Nova Launcher, Power toggles, Root browser, Stellio, Superbeam, weather and clock widget.
Any ideas?
Thanks
Flashed with this (November variant).
https://forum.xda-developers.com/g5/development/rom-debloated-optimized-t3722396
So far so good, yet to re-root it though.
Related
On LineageOS 13, the latest official build of LineageOS for the Nexus 10, when I iinstall the Nova Google Companion for Nova Launcher, Google Play Services, Nova Launcher, and a number of other apps crash. When returning to the home screen, it freezes, then sends the app into a boot loop where after the LineageOS logo appears in it's entirety, my device tries to start LineageOS, but then crashes again and so the boot loop process continues. I have already reported this issue to the Nova Launcher Beta Google+ community and mentioned that Nova Google Companion ran fine on the stock 5.1.1 ROM. I've already tried reflashing LineageOS and GApps. Suggestions as to what I should do without flashing a different ROM?
Update: So as it turns out, ANY UI modifications (Launchers, TeslaUnread, Nova Google Companion/Action Launcher Google Plugin) will send the device into a bootloop. I suspect that the issue is with themes provider or GApps, since Google Play, Play Services, and Themes Provider are the first to crash.
I have a similar issue but I am unsure what program causes it.
The tablet was newly installed and installing my list of apps, one being Nova.
EDIT, information provided by op:
The August 5th nightly accepts Nova Launcher, but not TeslaUnread, Nova Google Companion, or Action Launcher
Hello, I have similar issue with my Nexus 10 on lineageos 13. I've reset from factory, reinstall all my apps except Nova and it works fine.
When I decide to reinstall Nova, my nexus immediatly boot in loop...
It arrive sudunly probably after an uptade of Nova...
Olivier.
Similar issue on Galaxy S3 running Cyanogenmod 13 (20161220 Snapshot).
Installing Nova Launcher causes the device to freeze and go into bootloop where it reboots after "optimising apps".
I've also tried installing Google Now launcher but " Home" option doesn't show up and there is no way to switch from Trebuchet to it.
Similar issue on S2 Plus CM13 after an update
Tested 2 weeks without Nova and nothing happened
Decided to give a shot again then bootloop happened again, luckily I had backup this time
I'm facing the same problem right now with my Redmi 4A. How did you solve it? Doing a factory reset?
I am currently facing a similar issue, but the culprit here for me is the facebook app, as soon as I install it from play store, it sends my samsung gt-i9082 (running cm13) into an instant bootloop, I tried deleting the facebook app's data from the twrp recovery's file manager.
but even then it kept on rebooting.
I had tested this even after a complete format of my device, including internal storage and external storage. even removing external storage, still as soon as the app was installed it went bootloop.
It's strange for me, cause it's the same rom and the same device, that was running the same app version before i format it to clean everything.
I would have doubt a data clash between my older files, but that was ruled out after a complete format. I have no clue why this is happening.
Edit: The only difference between my previous and the new installation is that I used deltagapps before and I am using opengapps now.
I will try with deltagapps again to see if it is sorted.
Edit 2: Well it did stopped the bootloop with the facebook app, but then again it started giving me the same issue with all the other random app I try to install(All those apps that previously were working on the same rom, same device).
Now the only suspect remains is the emmc of the device, maybe that is failing or got bad sector. strange that I haven't seen any issue on the device forum about this. Bad Luck, It reaches it's end.
The fix for this issue is available here (13):
https://forum.xda-developers.com/showpost.php?p=74636021&postcount=216
CM 12
https://forum.xda-developers.com/showpost.php?p=74842530&postcount=464
Flashed OTA to Oreo tonight, was 7.1.2 August Update, Unlocked, Google Phone on Verizon Network
Flashed this kernel:
https://forum.xda-developers.com/pixel-xl/development/kernel-stock-kernel-safetynet-patch-t3588154
Rooted with Su, and Hidden with Suhide
After every restart, i get 2 app crashes of Gboard and Google App Services, the keyboard and everything seems to function normally after the crashes.
Attempted to clear data/caches on both apps, no change.
Has anyone experienced this or have any suggestions? Would prefer not to wipe completely.
Thank you
It might be a simple OTA issue, it probably bring some unneeded props from previous build (I adjusted nav bar in beta 3 so I can use pip but even after final release I still have it).
You can always flash factory ota image without wiping the phone. You need to edit a .bat file ofc, which is just removing a "-w" part.
But don't take my advice if you are not going to take a back up. It might get ugly also ?
Thank you for your thoughts. I spent too many hours trying to get it to work properly. I think I have it now. Hopefully this helps someone:
I found greenify was having issues and possibly locking apps/files after the update.
Uninstalled Greenify, and Pandora (which Greenify was complaining about)
Uninstalled Gboard
Removed device admin for Play Services
Uninstalled all updates for Play Services
Cleared all app preferences
Rebooted
Installed Play Services
Installed Gboard
Rebooted
Installed Greenify
Installed Pandora
Errors gone at this point. Will report back if something else comes up.
I am having major issues with android auto since Oreo
Essentially, what is happening is that the Android Auto app itself will work with two and only two apps. They are Google Maps and Google Play Music.
My problem is, none, and I truly do mean no other 3rd party apps will work with Android Auto.
I should also restate that this is a problem with the Android Auto app itself, so let's pretend no head unit or car is involved. This can be replicated on just the phone.
Here's the behavior:
-Open android auto
-Open any 3rd party app (Let's say IheartRadio)
Either one of two things happen next:
-Instantly get a screen that says "IHeartRadio Doesn't Seem to Be Working"
OR
-IHeartRadio starts like it should, and is able to play music for about 15 seconds, and then I get "Doesn't seem to be working" screen
-This happens for every 3rd party app, not just IHeart, but Plex, TuneIn, Radio Scanner, EVERYTHING except Google Play Music and Google Maps.
I should also state that Android Auto and 3rd party apps worked without a hitch, absolutely flawlessly in Nougat.
And, I've asked around the OP5t forums here and nobody is having the same problem.
-------
What I've tried so far (And hasn't worked)
-Re installing Android Auto
-Re installing every 3rd party app and re-trying
-Installing a custom ROM (Oreo) (Same exact behavior right after factory reset flashing new rom )
-Tried installing 3rd party apps from a non google play source
-Flashing OOS 8.0 Stable, as well as OB4 thru factory wipes
What I haven't tried:
-Re-locking the bootloader and flashing back to OOS nougat (Would this even help?)
I'm totally at wits end here, folks. I bought the OP5t to accompany my new car as my old phone couldn't handle android auto, this is one of the most imporatnt features to me.
Does anyone have any suggestions? Would flashing back to nougat and locking the bootloader like the phone was brand new help me? I've never seen such a problem that persists through clean flashes.
Thank you kindly everyone,
Hey!
I had this exact same problem.
I managed to solve this.
I am on OOS Open Beta 4.
Install latest:
Android Auto:
https://www.apkmirror.com/apk/google-inc/android-auto/
Android System Webview:
https://www.apkmirror.com/apk/google-inc/android-system-webview/
Google Maps:
https://www.apkmirror.com/apk/google-inc/maps/maps-9-74-0-release/
Google App:
https://www.apkmirror.com/apk/google-inc/google-search/google-search-7-23-24-release/
Google Play Services:
https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-12-2-21-release/
After installing all the apps, reboot your phone.
Android auto should work smooth again!
Just FYI, the bootloader status (locked/unlocked) has nothing to do with this.
Nick502 said:
Hey!
Android auto should work smooth again!
Click to expand...
Click to collapse
Hey there, first and foremost, thank you so much for taking time to respond! I tried your suggestion, but I'm still not having any luck
I'm going to keep messing around with it, but thank you again for the reply.
captainstarbucs said:
Hey there, first and foremost, thank you so much for taking time to respond! I tried your suggestion, but I'm still not having any luck
I'm going to keep messing around with it, but thank you again for the reply.
Click to expand...
Click to collapse
Ohh that is really weird. Make sure you install all the Google Beta apps, and also the latest Android Auto version.
Are you using the Red Dash cable?
Nick502 said:
Ohh that is really weird. Make sure you install all the Google Beta apps, and also the latest Android Auto version.
Are you using the Red Dash cable?
Click to expand...
Click to collapse
Yes, I'm using the dash cable that came with the phone, but this problem is isolated within the android auto app. I don't need to connect it to the car to get the issues I'm having. Just launching the app on the phone itself and starting up a 3rd party app will trigger the "seems to not be working" screen.
If I connect it to the car, the same behavior happens. No issue with the connection to the car since I'm still able to use Maps and Play.
I'm considering flashing back to nougat to see if it works and OTA'ing til I get stable 8.0 and dirty flashing OB4 today.
UPDATE!!!
I got it working, and how I fixed it was a total PITA, but it works and I'm on OOS OB4.
Here's what I did:
1. Download the first available nougat OOS and flash it. Factory wipe from stock recovery. Once booted, install android auto and 3rd party apps. Test if it works, if so...
2. Sign in google account and update to 5.0.4 via OOS updater
3. Once rebooted into 5.0.4, take OB4 and stick it onto root, and reboot to recovery again
4. I dirty flashed OB4 over 5.0.4 and it seems to work fine!
I haven't tested this in my car yet, I will be on a long drive tomorrow and update results.
Waze on android auto
Waze is working parallel to google Maps without any problems. When you open navigate both programs are shown.
Damn I just noticed it. My maps work but I tried to open Google play music and got the same error.
That was the one thing that consistently worked for me. Which rom are you on?
Does anyone have this problem? Updated today to the new camera version and discovered the new playground option does not work, when launched it just sits there and does nothing. Quitting the app causes all subsequent launches of the camera app to display no images on screen through the lens just a big block of grey. Only a hardboot will restore the camera functions. I did an uninstall of all updates to go back to the November system version and the Arc Core function reacts the same way. Anybody have any similar experience?
Running the November security updates with stock kernel and only Magisk 17.3 applied.
I installed the new camera today - Playground works just fine. No issues at all. I am running a custom kernel - not sure if that matters - (Franken Kernel 5.1) and all is good.... sorry you are having issues - have you tried to clear cache/Data on camera APK to see if that helps?
Good Luck...
Tried all of that, even went so far as to do a complete factory reset and wipe to see if it would work on a completely stock system but still no go. Maybe I have a bad AR chip or something.
Reapply your animation serrings
If Google playground has stopped working, active your animation settings on your phone. This fixed it for me!!
:fingers-crossed:
I accepted the latest OTA update for lineage. After the reboot my camera app shows a black screen for the main camera and crashes after a few seconds.
What I've tried:
Messing with the camera app, permissions etc.
Trying other camera apps, same problem.
Rebooting.
Since I wanted to see what grapheneOS was like I tried installing that.
Same problem....?
Okay so then I thought they might be sharing the same camera driver. So I installed...
The latest Google factory image.
Then I tried reverting to Android 11 (everything was 12 before)
Main camera is still dead. Selfie camera works.