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
Related
I've been using Android Revolution 9.2 and this morning installed 10.0. Everything was working fine for a while, then all of a sudden the GAPPS process started force-closing and I lost all access to the Play Store. I would click on the play store icon and it would just bounce me back to the launcher (in this case, Nova Launcher 2.0). I decided I need to reflash Android Rev HD 10.0 (I have CWM Recovery 6.0.1 installed). The AROMA installer would start, but it would always lock up at some point before the installation began, usually at the prompt to backup the efs partition, sometimes earlier, sometimes later. I haven't been able to get a clean flash started. I even tried to go back to 9.2, but the same thing is happening.
I did a factory reset hoping it would fix the problem, but the GAPPS process continues to crash and I can't access google to restore my apps. So I'm really up **** creek here. Am I looking at a bad RAM problem all of a sudden? (god, I hope not!).
Any help/advice would be welcome.
mudge
My fiancee has a fire phone, and she's had it for a few years. For the most of it, she's been using CM11 as her custom ROM. A few weeks ago, she mysteriously got it, and it wouldn't go away except when she disabled contact storage, but then she couldn't make phone calls. She then removed the dialer and it caused even more problems. I had to fully wipe her phone and re-flash back to Fire OS to get her dialer back. I then put CM11 back in, and everything was fine for awhile. Four days later, when Facebook updated, it did it again. We deleted Facebook, deleted the cache from contact storage, all that crap shown on Youtube, and still nothing. She opens up Chrome, it would pop up "process.acore has stopped", same with PlayStore. I wiped her phone again, then flashed her phone over to SlimKat, wiped dalvik cache, system, data, etc. It worked fine for a few days, then she opened up Cortana, and it's doing it again.
What apps have you disabled or uninstalled and/or installed since last wipe? Did you set it as a new phone after tou reinstalled cm11 or slimkat?
Try safeboot by clicking power button, then click reboot. Hold both volume up and down button while it fully reboots. You will see safeboot logo on screen. See if you get same error in safeboot. If not, then a change you are doing after fresh install is messing up your phone. Do a fresh install, then restore/install/uninstall one app at a time to see which app is responsible.
Every time I factory reset the phone, it's fine for awhile until some random app causes it again. The cause is different every time. At first, Facebook was the cause, then adding another Gmail account, then Reddit. We'll try your advice then get back to you.
If it is fine for a while, it is probably being triggered by some system app such as Google play services updating itself. I would suggest disable auto updates in play store and disable Amazon store if you haven't already. When phone prompts you that app updates are available, update one app at a time, (if have titanium backup and rooted, can backup the app before you update it). Once you find the culprit, open it in play store and disable auto update by un-checking the option by clicking three dots on top right. I had to do that for google play services because it was causing similar issues. Your issue may be related to contacts as well as calendar (clear calendar data but do not disable default calendar app from amazon)or one of the related background processes that is automatically updated but the updated version becomes incompatible with kit Kat causing all apps that depend on it to force close.
Check if your Google play services is newer than 10.0.84 version at the time acore error starts happening. If it is newer version then go to apk mirror website and download 10.0.84 version, uninstall the newer one and install this older one. Please do update if anything you did fixed the problem. Thanks.
Sent from my SD4930UR using XDA-Developers Legacy app
Have just 3 days with my new P2a42 and I love It but I didn't like the launcher (I don't like any other launcher anyway). So I installed "Total Launcher" which, for me, is the best launcher available. Unfortunately, after enabling dual app, the new created app does not appear inside Total Launcher apps but only in Lenovo's launcher apps. Is there a way to fix this? Thank you.
Nobody? well, be careful cause I tried with 2 different apps, "parallel space" and "2face" and suddenly my phone got into a reboot loop. I don't know which one of these was the guilty one because none was working very well so I tried with the other. But the only way I managed to stop my phone from rebooting every 10 seconds or so, was to factory reset it from recovery. BTW my phone is not rooted and has stock nougat ROM.
While updating/installing apps from the google playstore, the phone will crash and bootloop, and requires a full reinstall to get it working normally. I've attached 2 logcat files for both roms which give the same problem - Mokee5.1, CM13 on a clean installation with pico gapps and manually selecting several apps to install. One other custom rom also gave the same problem so I didn't bother trying any other custom roms. Reverting back to stock MIUIv8 gave no issues.
CM13 used to be mostly problem free until a few months ago I think when the update/install issue started happening. The playstore auto update is normally kept disabled on my phone so I'm unaware about when the problem really started happening.
Edit-
It doesn't seem to be happening anymore from a short test after flashing my CM13 backup but I've moved on to LO14.1
It may have something to do with some other complaints that people are having. It looks like some issue with Cynogenmod since Sept/Oct 2017 which needs some patching.
https://forum.xda-developers.com/general/help/bootloop-updating-apps-telegram-t3700773
Update to/ Installation of newest version breaks system
https://github.com/signalapp/Signal-Android/issues/7171
Several apps causes a phone reboot or boot loop
https://gitlab.com/fdroid/fdroiddata/issues/979
Can confirm the issue with CM13 on my Galaxy S3. Unfortunately, I do not know a solution. Just stick to older app versions.
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?