Related
Hello
Android version: 2.3.3
Running stock ROM with XWKF3 with default Samsung launcher. (let me know if further info is required)
From few days GS2 has been starting to force close the system applications out of blue. Not had this issue since 3 months. Basically I would get a force close of Google services initially (pic attached) which would throw that pop up in a contionus loop. When I later check out others apps the following applications also gave me the force close error:
1. Internet (doesn't even let me see the force close error. The box appears for less than a milliseconds and closes off)
2. Email
3. Gmail
4. Messaging
5. Social Hub
6. Gtalk
7. Tasks
8. YouTube
9. Wireless will not connect and it tries to scan and later switches off automatically.
10. TW launcher (not all the time, the home screen will restart itself on a contionus loop - effect similar to when we clear through RAM from task manager.
As u can see the above apps are mostly the system apps. Specifically android apps rather than touchwiz.
Here is what I have tried:
1. Try exiting all apps and clearing the RAM through task manager. But still the above mentioned applications force close.
2. so the only way was for me to switch off and the on the device. However this does not look like a permanent solution since the problem appears again like two or three times a day.
I would also like to point out that may be the issue issue is only when the wireless and is turned on. I can't be sure here completely.
Also after I restart the device oddly everytime the device temp shows as 39° C and then cools down.
I have not rooted my device at all and also have not installed any application which does a system wide changes (oh except Samsung app update and Samsung mobile security from the Samsung app store)
Just not able to know wot is causing the problem
So could anyone please help me out to as to solve this issue? Is some kind of virus/malware being attacked? Is the device suffering from faulty hardware?
Gald to provide any further info if required.
Thanx.
Have you tried fixing permissions a lot of time that solves FC's, if not id recommend doing a full wipe.
jonny68 said:
Have you tried fixing permissions a lot of time that solves FC's, if not id recommend doing a full wipe.
Click to expand...
Click to collapse
Thanx for the reply. What does fixing permission actually mean? also would I have a risk of killing my device when doing a full wipe? would I void my warranty? is it same as doing an hard reset on Nokia phones?
sorry for so many questions, this my first android device and got to get used to troubleshooting stuff :-/
Thanx!
Harsha Raj said:
Thanx for the reply. What does fixing permission actually mean? also would I have a risk of killing my device when doing a full wipe? would I void my warranty? is it same as doing an hard reset on Nokia phones?
sorry for so many questions, this my first android device and got to get used to troubleshooting stuff :-/
Thanx!
Click to expand...
Click to collapse
Fixing permissions fixes problems often associated with Force Close errors.
boot into recovery > advanced > fix permissions > reboot system now.
if fixing permissions doesn't work you should do a full wipe and you should be ok then.
I would definitely root your device if i were you most people do you can so much more, you can always "unroot" if you do need to send it for repairs and are worried about warranty.
jonny68 said:
Fixing permissions fixes problems often associated with Force Close errors.
boot into recovery > advanced > fix permissions > reboot system now.
if fixing permissions doesn't work you should do a full wipe and you should be ok then.
I would definitely root your device if i were you most people do you can so much more, you can always "unroot" if you do need to send it for repairs and are worried about warranty.
Click to expand...
Click to collapse
Hello
I tried to use the fix permission options. I went to recovery mode by switching off the device and holding down the volume up key + home key + power button and releases them once the Samsung logo appeared. I got the following screen. Link:
(there was an error attaching the pic
However I cannot see the "advanced" option though :-/ help?
And now after reading your post I'm actually thinking of rooting my device. Once I have time for it. Thanx for the advice on that.
Well it looks like issue is solved. I dint get option of "fix permissions" but by accident choose the fourth option "wipe cache partition" out of curiosity. And from that day on dint have any force close issues.
Just wanted to add that i too experienced this. Fixed it with a factory reset as i didn't think of wiping cache. I was not rooted, running KI1 2.3.4.
Force Close fix??
I have the same problem, I've tried everything again the same
Yesterday I got official M ota on my Moto G 2 Lte (Xt 1078 - Brazil)!
Just updated and everything was ok, no reset was needed.
Some tips:
- Can't activate System Ui Tuner:
In the developer options I turned off animations. Just restored the default option (1x) in all 3 animations, restarted
the device and voila, I could activate the System Ui Tuner (holding the cog icon). After that, disable the animations
again did no mess.
- Igo stopped working:
Just uninstalled and reinstalled the app (without delete the files), and it's working again.
- Greenify stopped showing black screen while hibernating apps (screen flickering):
Needed to give it permission to overlap other apps (in Settings > Applications > Advanced (cog wheel))
- Smart unlocker stopped working:
Works on the "Universal version"
A factory reset is always a good thing when you do a major version update, and reading "Just uninstalled and reinstalled the app (without delete the files???), and it's working again" lead me to think a factory reset should fix all your problems. Sad thing you can't backup your appdata or you will end in the same situation, not sure but mostly possible.
dr.nic said:
A factory reset is always a good thing when you do a major version update, and reading "Just uninstalled and reinstalled the app (without delete the files???), and it's working again" lead me to think a factory reset should fix all your problems. Sad thing you can't backup your appdata or you will end in the same situation, not sure but mostly possible.
Click to expand...
Click to collapse
But the only problem I had was the app Smart Unlock that isn't working in 6.0, I found the solution.... everything else is fine.
Factory reset is a last resort, because if I do it my bank app will require an activation in the bank, and I don't want to go there...
Ota file on the thread http://forum.xda-developers.com/moto-g-lte/general/mm-ota-xt1078-captured-brazilian-thea-t3313559
rafaelrgi said:
But the only problem I had was the app Smart Unlock that isn't working in 6.0, I found the solution.... everything else is fine.
Factory reset is a last resort, because if I do it my bank app will require an activation in the bank, and I don't want to go there...
Click to expand...
Click to collapse
For banking app, Take app+data backup using
Titanium (if rooted)
Helium (even without root)
nazir221 said:
For banking app, Take app+data backup using
Titanium (if rooted)
Helium (even without root)
Click to expand...
Click to collapse
Thanks for the advice, but my device isn't rooted and the Helium backup doesn't works for my bank (it has a #@$ seed for code generation, just Titanium can backup it, but I didn't rooted it).
I won't worry about it, because didn't reset it and it's working flawlessly....
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
Hi. I have a Xiaomi MiA1, Lineage 16.0 (I try to update it two or three times per week). It is rooted. I use openGapps.
I have a problem since yesterday: suddenly, my phone got a lot of lag that makes impossible the use. KLWP got closed (it stopped being the default background), Nova Launcher was lagging and restarting several times. Openning any app was impossible, including the settings and system, it freezes and closes, returning to the launcher home screen... I tried to stop, clean data and delete klwp, nova, but i got the same result. The minutes passed and it got worse. Finally, the phone freezed, the clock wasn't working, so the only solution was doing a manual soft reset.
So, yesterday I did a dirty flash, because I didn't have a recent backup. I used SDMaid database feature in the morning so I tought maybe it was bad executed and was the origin of the issue. I tried to rescue some information (to backup some app data) with oandbackups. I cleaned caché and did a Factory reset. It seem to work. and do a clean installation. at first, it seem like it worked. I installed the apps I had by my Google account, and went to sleep. Today, it was ready, I turned it off and charged it, and in the morning: again the crash. So I did a clean installation. Again, it seemed to work. It installed all my apps and... crash again. I fear it could be some launcher issue? any prob with lineage? Any app? How can I know whats happening?
Sorry for my bad english. Any help would be apreciated.
vainille said:
Hi. I have a Xiaomi MiA1, Lineage 16.0 (I try to update it two or three times per week). It is rooted. I use openGapps.
I have a problem since yesterday: suddenly, my phone got a lot of lag that makes impossible the use. KLWP got closed (it stopped being the default background), Nova Launcher was lagging and restarting several times. Openning any app was impossible, including the settings and system, it freezes and closes, returning to the launcher home screen... I tried to stop, clean data and delete klwp, nova, but i got the same result. The minutes passed and it got worse. Finally, the phone freezed, the clock wasn't working, so the only solution was doing a manual soft reset.
So, yesterday I did a dirty flash, because I didn't have a recent backup. I used SDMaid database feature in the morning so I tought maybe it was bad executed and was the origin of the issue. I tried to rescue some information (to backup some app data) with oandbackups. I cleaned caché and did a Factory reset. It seem to work. and do a clean installation. at first, it seem like it worked. I installed the apps I had by my Google account, and went to sleep. Today, it was ready, I turned it off and charged it, and in the morning: again the crash. So I did a clean installation. Again, it seemed to work. It installed all my apps and... crash again. I fear it could be some launcher issue? any prob with lineage? Any app? How can I know whats happening?
Sorry for my bad english. Any help would be apreciated.
Click to expand...
Click to collapse
Keeping in mind the kind of apps you mentioned, I'd go with an app+data backup of those apps you installed and uninstall them completely, check if problem is still there.
I suspect you're facing a compatibility or configuration issue, since both apps are related to home screen.
If problem is solved, first read if those apps are actually compatible with ROM and OS version, then you could try to install just one app, without data, and check if things go well (give it a day), same with the rest until you can confirm OS is working well with apps just installed, no changes made in them yet... In other words, were trying to confirm that problem comes from apps and/or their configurations, so you could somehow report those issues to apps developers. You can use Catalog or other apps to record System logs until app crashes.
On the other hand, if problem is still there, even before you started to reinstall apps, then Dirty flashing isn't a good choice in that case, since it preserves System configurations, no mention your device is rooted, were user changes are present... you are opened to different problems, worse if you use an old Magisk version, or installed modules there, or apps that force your OS to do things it doesn't do in it's original state.
So, as you were so dare to go with a dirty flash, you could better go with a clean flash instead.
Erase any system lock protection (fingerprint, pattern, etc), do a ROM Backup from TWRP, flash latest firmware and make a clean install of the latest version of the ROM of your choice, keeping in mind their own flashing procedure.
As with above reply, if a completely clean install doesnt work, consider going back to a previous lineage release. If it still doesnt work, consider a full EDL stock rom reflash using MiFlash -- then flash your custom rom.
KaaMyA said:
Keeping in mind the kind of apps you mentioned, I'd go with an app+data backup of those apps you installed and uninstall them completely, check if problem is still there.
I suspect you're facing a compatibility or configuration issue, since both apps are related to home screen.
If problem is solved, first read if those apps are actually compatible with ROM and OS version, then you could try to install just one app, without data, and check if things go well (give it a day), same with the rest until you can confirm OS is working well with apps just installed, no changes made in them yet... In other words, were trying to confirm that problem comes from apps and/or their configurations, so you could somehow report those issues to apps developers. You can use Catalog or other apps to record System logs until app crashes.
On the other hand, if problem is still there, even before you started to reinstall apps, then Dirty flashing isn't a good choice in that case, since it preserves System configurations, no mention your device is rooted, were user changes are present... you are opened to different problems, worse if you use an old Magisk version, or installed modules there, or apps that force your OS to do things it doesn't do in it's original state.
So, as you were so dare to go with a dirty flash, you could better go with a clean flash instead.
Erase any system lock protection (fingerprint, pattern, etc), do a ROM Backup from TWRP, flash latest firmware and make a clean install of the latest version of the ROM of your choice, keeping in mind their own flashing procedure.
Click to expand...
Click to collapse
I made a clean flash in the morning, with the same results, so there's when I thought it could be an app the main problem. It worked with Nova a few hours.
I just followed your instructions, I installed the last firmware (the jan one) and the last rom of lineage. I didn't installed the apps in my google backup so I can install them and check how is the behaviour. I will install CatLog so I can check the logs too! I really hope installing the firmware was enough. Thank you very much!
ayunatsume said:
As with above reply, if a completely clean install doesnt work, consider going back to a previous lineage release. If it still doesnt work, consider a full EDL stock rom reflash using MiFlash -- then flash your custom rom.
Click to expand...
Click to collapse
I was planning to reflash the custom ROM but I couln't find the latest one that's compatible with MiFlash. I really hope the clean install is enought... thank you
I was planning to reflash the custom ROM but I couln't find the latest one that's compatible with MiFlash. I really hope the clean install is enought... thank you[/QUOTE]What our partner said was flashing stock (original) ROM.
In any case, if you went with a clean flash, try to leave your system free of user installed apps for a few and check how it goes.
Hello!
I tried to update my phone (SM-G975U) via Odin from Android 9 to Android 12, got the firmware from SamFw.com. Everything went fine until the phone rebooted, after unlocking the phone gets stuck on 'phone is starting'. I CAN access the Set Up Menu, Uninstall apps, move some settings here and there, connect to Wifi/Bluetooth, receive calls, install apps using ADB. Also, theres a notification all the time that reads 'Phone restarted Unlock your phone to get app notifications', I'm assuming that the phone thinks it is not unlocked and that's why it doesn't fully boot up.
Some things that I've already tried:
Intalling another Launcher (Pixel Launcher)
Reinstalling the firmware (ver G975USQU6IVC7) / Trying with different CSC with no results
Wiping Cache in Recovery Mode
Deleting/Adding Fingerprints
Changing from Lock Pattern to NIP to Password
I don't really want to do the full wipe, I would like to keep my data or be able to export the photos (Device not Recognized by Smart Switch also)
Is there anything else I can do?, has anyone been through the same issue?
Is your phone rooted?
Vatt`ghern said:
Is your phone rooted?
Click to expand...
Click to collapse
No, it's not rooted
Hi !
@DannOsnaya have you found a solution to the phone problem other than restoring to factory settings?
I have the same problem at the moment, almost identical to what you experienced.
If anyone has some advice on how to fix this problem, please share your advice.
My phone is not rooted.
Racer512 said:
Hi !
@DannOsnaya have you found a solution to the phone problem other than restoring to factory settings?
I have the same problem at the moment, almost identical to what you experienced.
If anyone has some advice on how to fix this problem, please share your advice.
My phone is not rooted.
Click to expand...
Click to collapse
Sadly, I have not
My phone is still like that, I tried updating to the newest security patch but didn't work either, haven't lost hope in avoiding factory reset tho
Hi. Did u find any solution to it. Am facing the same issue. Although I tried to factory reset but doesn't work.
DannOsnaya said:
Sadly, I have not
My phone is still like that, I tried updating to the newest security patch but didn't work either, haven't lost hope in avoiding factory reset tho
Click to expand...
Click to collapse
Any way to factory reset. I tried every possible way following YouTube but nothing works. It's just stuck. I've a backup of my data so not worried.
No, I still have the same issue.
Have you tried to install a launcher?
DannOsnaya said:
No, I still have the same issue.
Have you tried to install a launcher?
Click to expand...
Click to collapse
Nothing works. Now decided to show it to anyone. I guess the mobile shops have an option to erase everything. I don't understand how did it happen because it's usually with my toddler, he might have done something.
DannOsnaya said:
Hello!
I tried to update my phone (SM-G975U) via Odin from Android 9 to Android 12, got the firmware from SamFw.com. Everything went fine until the phone rebooted, after unlocking the phone gets stuck on 'phone is starting'. I CAN access the Set Up Menu, Uninstall apps, move some settings here and there, connect to Wifi/Bluetooth, receive calls, install apps using ADB. Also, theres a notification all the time that reads 'Phone restarted Unlock your phone to get app notifications', I'm assuming that the phone thinks it is not unlocked and that's why it doesn't fully boot up.
Some things that I've already tried:
Intalling another Launcher (Pixel Launcher)
Reinstalling the firmware (ver G975USQU6IVC7) / Trying with different CSC with no results
Wiping Cache in Recovery Mode
Deleting/Adding Fingerprints
Changing from Lock Pattern to NIP to Password
I don't really want to do the full wipe, I would like to keep my data or be able to export the photos (Device not Recognized by Smart Switch also)
Is there anything else I can do?, has anyone been through the same issue?
Click to expand...
Click to collapse
I followed a video and wiped out. Finally successful. I wasn't worried about data as Google has a backup.
I followed this method and finally it's factory reset.