Related
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.
Howdy,
I got a new Note 4 from Bell Mobility about a month ago...
I updated the software, rooted it and installed the Wanam modified Xposed framework.
I have lost the automatic rotation, except for the built in camera software. Nothing else will auto-rotate. Checked the gyroscope and checked a few 'leveler' applications - all tests pass. Oddly I noticed the camera software still auto-rotates, no idea why it is special.
I tried the Wanam Xposed module to 'Enable all rotation angles' it has made no difference. With screen rotation software, currently have "Rotation - Orientation Manager by Pranav Pandey" installed. Auto-Rotate On and Forced Auto-Rotate neither option will rotate the screen when I turn my phone. If I choose Forced Landscape, it will go into Landscape mode. The only way to return to Portrait though is to use one of the Force Portrait options though.
My other issue is with turning on Device Encryption... Using SuperSU Pro for su..
If I just go through the prompts without changing anything, it reboots but doesn't encrypt.
First I tried installing as a system app so I could use the Disable function in the Android Application Manager, as I did with my Note 2, SuperSU tells me "Not (currently) available in system-less root mode".
If I turn off "Enable Superuser" in SuperSU, encryption enables properly, but I am unable to turn the "Enable Superuser" again, it says it has to update, but the fails. Suggests a reboot and try again. Sadly, this did not help.
I had success with one of the exploit root methods, KingRoot. While this worked when my phone was encrypted, it wasn't stable and kept popping up stuff. I tried to replace it with SuperSU, there are a few guides written to do just that, but they all indicate that it is very hard to get rid of, regardless, none of the guides worked for me. I ended up resetting the phone and starting over...
I tried the CLI command to start the device encryption from a # prompt..
vdc cryptfs enablecrypto inplace password 1234567890abcdef
The phone rebooted a couple times, but took a very long time (hour plus) to come back to the Android Lock-Screen.. But still a non-encrypted device. If I intrupted the process because I thought it had crashed, it started up and immediately told me something when wrong with the encryption and I need to use Recovery to reset the device..
As for root methods, I was using the CF-Auto-Root at first, trying to look for solutions to both issues, I tried a few ways of getting SuperSU installed.. The last time I reset I tried the "SkipSoft Unified Android Toolkit" method. 'Grasping at straws' to get SuperSU installed into /system so can use the Applicaiton Manager to disable and enable it...
My mobile's specifics, if it matters..
Samsung Galaxy Note 4
Model number - SM-N910W8
Android Version 5.1.1
Baseband version - N910W8VLU1COK3
Build number - LMY47X.N910W8VLU1COK3
Currently have the Team Win Recovery Project v2.8.7.0 recovery software installed.
I am looking for suggestions for both issues, but really want to avoid resetting the phone if I can at all possible... Yes, I have Titanium Backup Pro installed, but have never actually gotten a restore to properly restore all my applications and data... I rely on it now just for the Uninstall and Freeze features.
For an update,
I also noticed that rotation works on the Lock Screen and in the camera applicaiton.
If I rotate my screen on the Lock Screen, the red handset picture and camera icons rotate.
If I rotate in the camera application, nothing changes position, but all the icons rotate as well.
I'm still completely stuck though, open to suggestions...
For rotation, it is likely caused because you removed the com.thingy.facebook system app. I tried removing it because I thought is was bloatware but read somewhere that messing around with it cause the auto rotate and pedometer to fail. I fixed it by reflashing the rom without data wipe then never removed it again. Page Manager is safe to remove though.
uchihakurtz said:
For rotation, it is likely caused because you removed the com.thingy.facebook system app. I tried removing it because I thought is was bloatware but read somewhere that messing around with it cause the auto rotate and pedometer to fail. I fixed it by reflashing the rom without data wipe then never removed it again. Page Manager is safe to remove though.
Click to expand...
Click to collapse
Thank you,
I had it frozen for a while, completely uninstalled it, trying to see if lack of space was why I couldnt' get SuperSu to become a System App..
I will try to put the facebook app back to see if that helps. Hoping I don't need to do a ROM reset, but if that is what it takes.
kevinds said:
Thank you,
I had it frozen for a while, completely uninstalled it, trying to see if lack of space was why I couldnt' get SuperSu to become a System App..
I will try to put the facebook app back to see if that helps. Hoping I don't need to do a ROM reset, but if that is what it takes.
Click to expand...
Click to collapse
Thank you http://forum.xda-developers.com/member.php?u=5047956
I tried installing FaceBook from the PlayStore, no change.. So I uninstalled it again.
Took a backup in Titanium Backup and in TWRP.
From the stock image, I extracted system.img.ext4 and used SkipSoft's application to make just this file Odin flashable..
Flashed it.. When I got back to Android, my phone hadn't reset (what I was going for ), rotation is working, SuperSU still giving root access
I went back into Titanium Backup, the freshly installed apps were listed on top, because there was no backup of them.
Froze each, one at a time and checked the rotation after each.. Froze all the apps with no backups, and rotation stayed working, which I thought was odd for what fixed it.
So.. The Facebook applications are all frozen, as they were before I erased them the first time, and rotation still works. Hurray..
Now for the device encryption, I will keep messing with it.. Trying FlashFire to mount System as RW and to write the newest version of SuperSU, hopefully it will install to System this time.
Thank you again.
kevinds said:
Thank you http://forum.xda-developers.com/member.php?u=5047956
I tried installing FaceBook from the PlayStore, no change.. So I uninstalled it again.
Took a backup in Titanium Backup and in TWRP.
From the stock image, I extracted system.img.ext4 and used SkipSoft's application to make just this file Odin flashable..
Flashed it.. When I got back to Android, my phone hadn't reset (what I was going for ), rotation is working, SuperSU still giving root access
I went back into Titanium Backup, the freshly installed apps were listed on top, because there was no backup of them.
Froze each, one at a time and checked the rotation after each.. Froze all the apps with no backups, and rotation stayed working, which I thought was odd for what fixed it.
So.. The Facebook applications are all frozen, as they were before I erased them the first time, and rotation still works. Hurray..
Now for the device encryption, I will keep messing with it.. Trying FlashFire to mount System as RW and to write the newest version of SuperSU, hopefully it will install to System this time.
Thank you again.
Click to expand...
Click to collapse
This is amazing, can you please post the odin flashable file? I am having this exact problem right now because I removed it in TB. Is it just the facebook file that are flashed? Thanks so much in advance, you're saving my life here
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 All,
So I'm facing this weird issue, where my app updates from the Google Play Store don't seem to stick.
I started having this problem when I was using LOS, and I thought maybe the ROM was the issue. But then, I switched to OOS, same thing.
An app will update and play store will show all apps updated. Then after a few hours the app will update again, and then once more. Usually the update sticks after the third update.
Also, even though I haven't kept a log, but it doesn't seem specific to some apps, it appears to be the case with all apps.
I use Magisk for Titanium Backup. But nothing else.
Also, I thought this was an issue with apps restored with Titanium Backup, but that isn't the case.
PS: I haven't tried without Magisk, as I wouldn't want to use the phone without that.
Any ideas?
fash_ahmed said:
Hi All,
So I'm facing this weird issue, where my app updates from the Google Play Store don't seem to stick.
I started having this problem when I was using LOS, and I thought maybe the ROM was the issue. But then, I switched to OOS, same thing.
An app will update and play store will show all apps updated. Then after a few hours the app will update again, and then once more. Usually the update sticks after the third update.
Also, even though I haven't kept a log, but it doesn't seem specific to some apps, it appears to be the case with all apps.
I use Magisk for Titanium Backup. But nothing else.
Also, I thought this was an issue with apps restored with Titanium Backup, but that isn't the case.
PS: I haven't tried without Magisk, as I wouldn't want to use the phone without that.
Any ideas?
Click to expand...
Click to collapse
Currently using Magisk on OOS and I do not have this issue, so root isn't the issue. I think it may have to do with the play store itself, as it doesn't seem to actually update the apps until the third time like you said. The only two solutions I can come up with are as followed:
1. Hold down on the play store app and clear the data on it and then disable the app (Make sure the option to go back to the factory version comes up after you press disable) and then re-enable the app again. Open it and see what happens afterwards. The idea is to get the play store to re-update itself and fix the issue.
2. Get on a computer and fastboot flash OOS again and see if it persists after you get your phone set up again.
Sadistic_Loser said:
Currently using Magisk on OOS and I do not have this issue, so root isn't the issue. I think it may have to do with the play store itself, as it doesn't seem to actually update the apps until the third time like you said. The only two solutions I can come up with are as followed:
1. Hold down on the play store app and clear the data on it and then disable the app (Make sure the option to go back to the factory version comes up after you press disable) and then re-enable the app again. Open it and see what happens afterwards. The idea is to get the play store to re-update itself and fix the issue.
2. Get on a computer and fastboot flash OOS again and see if it persists after you get your phone set up again.
Click to expand...
Click to collapse
Hi.. Tried these already... The problem persists.
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.