Seems without adding anything to my A7, in the past day it is literally non stop FC'ing on the above process. I hit Force Close and it keeps coming back (not immediately, more like randomly without 10-25 seconds). Only thing I've did extra n the tablet lately is play Angry Birds. Should I try to clear it's DB even though I haven't loaded it today? Also would like to state that I have rebooted and even shut down the tablet, and it still does it.
what have you done to it? stock firmware update? DexterMod? Stock fresh out of the box?
netstat_EVO said:
what have you done to it? stock firmware update? DexterMod? Stock fresh out of the box?
Click to expand...
Click to collapse
Guess in my first version of this thread, before I edited it, I had that information (morning brain fart).
DexterMod v1.3 + BT Fix
Worked fine yesterday morning then it started FCing out of the blue. I've begun (even though none of the apps were installed immediately prior to the FCs) uninstalling widgets that I installed. Next is to start on programs (I did however uninstall Button Savior as I know it loads on startup so I was thinking that was causing it even though it had been on the device for a couple days running flawlessly).
Got tired of messing with it. Did a Cache Partition Wipe and Device Wipe and it's back to normal DexterMod v1.3. This seems to have resolved the issue so it must have been something with one of the databases on the applications that I had installed. Will see once I reload all my apps.
Hi,
The problem that I have is that everytime I turn on my S4 "Messages" crashes and afterwards "com.android.phone" keeps crashing.
It started when I was on Google Chrome Beta where I got a few crash notifications (I think it was 2, don't remember). I didn't think much about it then, but when I went to the Play Store to install Chrome, where it said it was already installed. Recently I have removed a lot of the bloatware including Chrome on the S4 and nothing happened by it and I have restarted my phone a few times after that. But in the Play Store when I clicked on the uninstall button it got stuck on uninstalling (most likely because it wasn't installed in the first place) and when I restarted my phone thinking it might solve the problem. The whole problem with "Messages" crashing and afterwards "com.android.phone" crashing again and again, started.
Now I have to keep Flight mode turned on or I can't even use my mobile.
I have tried following solutions:
- Wiped Cache & Dalvik Cache
- Factory Reset
- Reinstalled all the bloatware
- Reinserted SIM card
- Removed sdcard
My phone is a Samsung Galaxy S4 I9505 (XXUAMDM) - Root - Stock rom
I hope someone can help me figure out how to fix this.
I found out what the problem was. I didn't reinstall all the bloatware. I only got the first 20 installed instead of them all. So now it works again.
So I tried out the CM11 nightlies, and of course to see how it works I tried the WhisperPush out since it is included in noobdev's builds. Now after attempting setup Messaging crashes immediately upon tapping to open. If i switch Hangouts to be in charge of SMS, same thing, crashes if i try to create a text. I tried 2 other SMS apps from the play store, same problem. Reflashing rom has same issues, coming from another rom to it, also same. Any idea what could be causing it, I can run other 4.4 roms without this issues, so definitely something with CM/WhisperPush.
Same Issue here
wafflenator said:
So I tried out the CM11 nightlies, and of course to see how it works I tried the WhisperPush out since it is included in noobdev's builds. Now after attempting setup Messaging crashes immediately upon tapping to open. If i switch Hangouts to be in charge of SMS, same thing, crashes if i try to create a text. I tried 2 other SMS apps from the play store, same problem. Reflashing rom has same issues, coming from another rom to it, also same. Any idea what could be causing it, I can run other 4.4 roms without this issues, so definitely something with CM/WhisperPush.
Click to expand...
Click to collapse
I got the same problem.
Trebuchet crashed constantly, too. Also, saving Trebuchet's options did not work (migrating from CM 10.2 to 11 M3)
Edit: The "Unfortunately, WhiserPush has stopped" message comes right after receiving the verification code and generating the keys.
Edit2: In Trebuchet Settings, I cannot access "Drawer" or "Dock".
Running:
cm-11-20140210-SNAPSHOT-M3-jfltexx.zip
on SGS 9505 without gapps.
Did you wipe data before flashing CM11? Since this is a major Android version change, it could very well be that there's issues from the 4.3 vs 4.4 data.
For Trebuchet Settings not giving access to drawer or dock, it might have been placeholder or there's a bug accessing those.
I recently switched from AOSPA after not being particularly impressed and went back to oxygen. However, after attempting to send a message I was unable to send one and noticed that I also am unable to receive. Phone calls and cellular data seems to work perfectly. I have flashed the proper firmware and reflashed the OS several times, but for no avail. I've also tried to clear cache l, but still no luck. I haven't been able to test the SIM card on another phone yet, but as the problem started as I switched OS I doubt that the problem lies there.
Some weird things I've noticed:
- Both Facebook and Google Messenger refuse to even attempt at sending a message, whereas textra pretends nothing is wrong
- In gsam battery monitor the phone line is greyed out
- Right after boot a message saying there is no service appears, but disappears fairly quickly.
Thanks in advance!
And this is after clean flash? Also without trying to restore any data using Titanium backup or other?
Clean flash, but I did use titanium backup. Guess that could be the cause. Seems like I'll have to do another clean flash anyway.
Hi,
A few days ago I experienced a boot loop on my Nexus 10 with Lineage OS 13, build 20170909.
I broke it down to a recent update of Nova Launcher - going back to an older version and preventing Google Play automatic updates fixed it for me.
There are a number of reports of the same symptom pointing to Nova Google Companion, TeslaUnread, IFTTT, and Action Launcher.
I don't think this is an issue in those apps, but rather caused in the OS - an App should not be able to bring down the OS to a reboot (and even worse, due to the automatic restart of the launcher, causing a reboot loop).
any ideas of a fix in the OS? something else to prevent this from happening again?
Regards
sthones
I confirm the same. Constant bootloop with Nova Launcher
I am also experiencing this on an older version of CM13. Clearing cache does not work. Any quick fix possible via recovery?
stephendt0 said:
I am also experiencing this on an older version of CM13. Clearing cache does not work. Any quick fix possible via recovery?
Click to expand...
Click to collapse
I had the same problem with a Galaxy S3 running OctOS (CM13 based Android 6.0.1). The Nova Launcher update caused my phone to crash and reboot as soon as it was unlocked.
I was able to disable Nova in recovery (TWRP) using the built-in TWRP file manager. navigate to /data/app/com.teslacoilsw.launcher/ and delete base.apk. This will keep Nova from loading on startup but will not delete your data. My phone worked fine after that, albeit without Nova.
Thanks a lot, removing base.apk stopped the reboot loop.
My device has just started a bootloop too, but I don't even have Nova installed on it (though I do on my phone), just the stock launcher in CM / LineageOS.
I reset it to factory defaults and then it boots, but when it restores my old apps it starts looping again, so one of them is the cause. I didn't learn anything from the log via adb.
Any ideas?
I discovered it was one of my apps causing this. I removed it and it boots ok. https://play.google.com/store/apps/details?id=au.com.realestate.app&hl=en
hmoffatt said:
I discovered it was one of my apps causing this. I removed it and it boots ok.
Click to expand...
Click to collapse
Thanks for the hint, it was a real estate app from germany (immoscout24) which caused the problem at my device. Deleted the base.apk and everything works fine again.
Happening to me now, ffs im on the latest nightly and thats not fixed it.
TheRealSmurf said:
Thanks for the hint, it was a real estate app from germany (immoscout24) which caused the problem at my device. Deleted the base.apk and everything works fine again.
Click to expand...
Click to collapse
Same here.
daseddy said:
Same here.
Click to expand...
Click to collapse
Mine just started boot looping yesterday, but I hadn't installed any new apps in a while, and I have automatic app updating turned off (I also don't have any real estate apps installed, German or otherwise). Any hints on how to track down the culprit? Is there a boot log to look at?
Thanks!
Folks, there is a defect open in the official lineage bug tracking system. please add your comments there - maybe this needs some more support to get looked at:
https://jira.lineageos.org/browse/BUGBASH-1075
Same here. Started happening after it updated my apps yesterday. Removed nova launcher and all other Teslacoil software, problem remains. Can only start the tablet in Safe mode.
Seeing this on my device as well, except I am not able to remove the base.apk file because the app I installed somehow corrupted my bootloader such that I cannot get into recovery mode.
The culprit app? LinkedIn. Automatic app updates were turned off, and just before the bootloop started, the last thing I did was install that app. It finished, it rebooted, and hasn't stopped rebooting since.
When I put it into bootloader mode, it stops the continual rebooting and displays the "open panel" robot and "Downloading... do not turn off target". From there, all I can do is press power to start, then it goes back into rebooting. There is no way to get into recovery mode from there.
Also, attempting to keystroke into recovery mode just restarted the lineos infinite reboot.
Can't get into recovery, can't get the bootloader out of "Downloading" mode, and lineos continually reboots... Any wise sage souls have any ideas on this one? It looks like my device is bricked
It got me too - I don't have Nova Launcher installed. A few weeks ago the device started bootlooping with a build I had installed since september. I updated to one of the latest builds and had the same issue again. At the moment i got it working most of the time, but when i start certain apps it just reboots.
Seems to be independent to build version and can occur with different apps (at least thats what I've read here...).
Is this a Lineage Os 13 only thing or can I throw the device away now?
Greetings
I started having this issue this week as well. Oddly enough, I was still on CM12.1. In the middle of watching Plex and it rebooted, and has been boot-looping since. I did a factory wipe and while installing apps, it started looping again. I then installed the latest nightly of LOS13.1 and again, once it got part-way installing apps, it started boot-looping again. So this is not just a LineageOS thing, it seems to be an app update (I do have auto-update turned on).
I´m having the same problem without ever have the Nove Launcher installed. The bootloop started on my device several weeks ago. I tried to fix it by wipe partly or total and reinstall the latest nightly of los13 (20171126) and opengapps micro 27.11.2017 (and everything else).
As soon as I reinstall my apps, los goes back to bootloop. Sometimes, when I manually install only few apps, the system seems stable, until die next updates come by the play store.
So now I went back to stock rom until I´m getting aware of the problem beeing solved.
workaround, maybe
I wouldn'n call it a bootloop but rather a startloop
Anyhow, in my case I was able to break the loop by entering android's safe mode by simultaneously pressing vol up and down keys during startup. In safe mode, I was able to delete offending apps. After reboot, system is running again. Apps identified so far to make lineageos unhappy: open camera, yalp store, YouTube(!).., oruxmaps.
Removing offending apps works
Thank you!
I did the same with your advice... removed some apps and it works. I went back to September ROM, then update to Nov ASB ROM and it works fine.
ShevT is on it, here https://jira.lineageos.org/browse/BUGBASH-1052
and here: https://review.lineageos.org/#/c/197386/
Hope it gets fixed and merged soon... as this has been a pain the neck for a while, possibly related to a similar problem earlier this year.
loveandmarriage said:
I wouldn'n call it a bootloop but rather a startloop
Anyhow, in my case I was able to break the loop by entering android's safe mode by simultaneously pressing vol up and down keys during startup. In safe mode, I was able to delete offending apps. After reboot, system is running again. Apps identified so far to make lineageos unhappy: open camera, yalp store, YouTube(!).., oruxmaps.
Click to expand...
Click to collapse
I'm running CM13 and I have the same problem. I am not tech savvy with installing ROMs but managed to get to TWRP and did a reset to factory. Got part way thru optimising apps and the problem came back. I could only turn the tablet off via TWRP!
I don't mind going back to stock rom but not sure how to do it..best I look on here and start to educate myself..I'm 73yo so might not get finished before my time is up