I put it in one thread as it may be connected. My Mi 5 behaves strangely for some time. It occasionally freezes, but not totally. I can, for instance, enable/disable WiFi, but an application gets stuck. After a while phone restarts by itself, but then very often freezes on LineageOS initial animation. I need to restart it manually by pressing the power button.
To make it more interesting, almost each time that results in a reset of some style settings (like icon style) and an inability to use existing fingerprints. They are still visible in the fingerprint settings, but apps that used them can't see them anymore (just inform that "you probably changed or deleted your fingerprints, activate it again"). I also cannot unlock my screen with fingerprints (after entering password once). The only way is to delete old fingerprints and add new ones.
I generated logcat files after such reboots, but they usually don't cover the time before a restart, as if the logs were cleared.
I have LineageOS 18.1-20220508-NIGHTLY-gemini.
I attach logcat examples:
Logcat_1 - sudden, partial freeze and auto-restart, which got stuck (12.05.2022 about 19:48). Fingerprints not lost. Surprisingly there are some logs from February which jump straight to the time after restart.
Logcat_2 - sudden auto-restart (15.04.2022, about 11:07) with fingerprints lost. (LOS 17.1). Again logs from a month before the restart just disappeared.
Do you think that may be a hardware issue? Similar strange things happend on LineageOS 17.1 just before an upgrade (about a month ago). Sometimes nothing happens for a week and sometimes I have a problem day after day.
Given that Lineage OS was flashed to your device, and if this issue did not happen before Lineage OS was flashed, I would suggest it a software issue.
To solve this issue, if you can still enter recovery
- format data - "yes";
- clean-flash a new rom.
I would suggest you flash a rom from lineage official website: https://lineageos.org/ if it was no so or a stock rom or a rom from XDA forum.
Related
Has anyone else noticed problems with CM crashing on their Atrix HD? I have been running CM on mine since September and have noticed the same problems in both CM 10.2 (epinter) and CM 11 (official). I never noticed any problems with the stock software. I have identified at least two different types of crashes.
Type 1 typically happens overnight when plugged into a charger (though less so with more recent builds) or when the phone is idle in my pocket. There is no notice the phone has crashed though sometimes if it happens in my pocket the phone seems to warm up somewhat. When I pull out the phone and press the power button I get nothing at all. This requires holding down the power and volume buttons for an extended period to force the phone off and then restarting it.
Type 2 typically happens when on an active phone call, though it can happen other times when using the phone as well. This involves the phone crashing and immediately going into a reboot (red M on the display as soon as I pull the phone away from my head).
I also have a less serious issue where when I press the power button to turn on the screen it will occasionally display the lock screen but refuse to take any touch input. I can usually get things to work by pressing the power button a few more times to turn the screen off and on again.
Just yesterday I switched to the new unified builds and have not seen all of these happen yet but I have definitely seen a type 2 already. Just wondering if these problems are widespread as I don't see them discussed a lot and if there's anything I can do about them.
Nothing? Am I really the only one having these problems? For the record I have now seen both types of crashes on the unified build.
May be you can try to flash stock rom:silly:
Try flashing the latest Validus ROM. I have been using version 4.3, which is based on KOT49H and it's been very stable with no crashes.
Is there a crash log that I can capture and review after a crash?
BenFranske said:
Is there a crash log that I can capture and review after a crash?
Click to expand...
Click to collapse
/proc/last_kmsg - kernel log from before the last reboot
/data/dontpanic/apanic_console - last kernel crash log
If the kernel crashed and the crash caused the last reboot, the content of both will be the same.
Regarding the non-responsive touchscreen after pulling the phone out of your pocket - it is usually caused by static electricity build-up. Subsequent turning off/on of the screen usually invokes ESD recovery procedure in the touchscreen circuit and the touchscreen starts to respond again.
It's very common on wide variety of phones (including e.g. iPhone). Change your trousers or use a belt case .
kabaldan said:
/proc/last_kmsg - kernel log from before the last reboot
/data/dontpanic/apanic_console - last kernel crash log
If the kernel crashed and the crash caused the last reboot, the content of both will be the same.
Click to expand...
Click to collapse
Great, I'll check those out the next time I have a crash. I am thinking there will almost certainly be some useful information for the second type of crash where the phone actually reboots itself. I am less optimistic that there will be any information when it simply locks up and I'm forced to reboot it by holding power and volume down buttons.
kabaldan said:
Regarding the non-responsive touchscreen after pulling the phone out of your pocket - it is usually caused by static electricity build-up. Subsequent turning off/on of the screen usually invokes ESD recovery procedure in the touchscreen circuit and the touchscreen starts to respond again.
It's very common on wide variety of phones (including e.g. iPhone). Change your trousers or use a belt case .
Click to expand...
Click to collapse
Thanks for the helpful information there too. My sister has forbidden me from wearing belt cases for at least the last 10 years but it's at least nice to understand what the problem is!
Crash Logs
Sorry it took me a while to get back to this. I've attached a few crash logs that I captured last month. I have updated the OS several times since then but I'm still experiencing both of the types of crashes I originally mentioned. Any assistance in interpreting the logs is appreciated!
Any ideas about what might be causing these crashes and reboots?
Am I really the only person with these issues? How can that be?
I've been dealing with an issue on the latest cm11 builds. I can't seem to remedy it. After using the tablet for a few minutes, the device would lock up, and the notification and navigation bars would disappear, and I get forced to the lockscreen with out any widgets. Trying to unlock the device causes a lock up again, requiring a force reboot.
I've tried clean installing and changing roms. I also noticed that pulling the quick tiles causes the crash often. However its difficult to replicate, as it randomly occurs.
I'm going to try flashing an older build.
Is this a cm11 issue?
Sent from my TouchPad using Tapatalk
Have had similar problems but they seem corrected now. I am using the latest Pac-man Shumash rom and on another TP, the latest Jcsullins.
Make sure to wipe the cache and Dalvik cache before installing. Also, use the latest gapps. I assume you are using the TPtoolbox for installing?
Also, set lock screen to off.
Same problem
I have the exact same problem. After a period of work, it just seizes up forcing me to lock screen and then just turning off the screen. Again it's most usually caused with the pull down tiles. A thing I noticed is when it seizes up you have some time before it locks you out. At that time I pressed the home button on the touchpad and it took me to the main screen. At that point the pull down tiles and the bottom 3 buttons (back, home, tasks) are unresponsive. I've now reset the Davik cache and cache, will see if this fixes the problem.
Edit: After the reset same thing is occurring, but this time there is no lockout. Just the menus becoming unresponsive. If I press one of the menu buttons everything becomes unresponsive, after a while it return to normal (except the menu buttons). If I press them again ... well just repeat the above. After a couple of times the tablet shuts down.
***I used the toolbox with pa_app, Cyanogenmode11 (the one from Jcssnuell (or something)) and Clockworkmod - all after deletion of previous systems. Before that I had Cyan9 which had the same issue i believe.
After some guesswork I believe I may have found the cause. I've tried resetting the cache and Dalvik cache a couple of times, problem persists...
Last reset I skipped the Google account thing and set the language to English (United States). I don't know what helped, but it seems to not be crashing any more.
I will add my google account after a little more time to see if it crashes or not and then see if it crashes with the account. It would be super funny and NOT FUNNY AT ALL if it was actually the language settings that are causing it.
I am having these exact same problems as well. Freezing up pulling down quick tiles. Nav buttons becoming unresponsive Also, sometimes is will just spontaneously do what looks like a "quick reboot" where is goes to the CM spinning boot animation for a few seconds, and then back to the home screen, usually followed by unresponsive buttons, etc.
I've tried jscullins 0625 and 0409, Milaq latest nightly, Shumash pac-man. All have the same issues. Gapps is gapps-kk-20140105.
I used TPToolbox to do the partitions and initial install. I think I'm going to try a full wipe and start over.
1905
I did some more searching and found that Google hotword detection can cause problems like these. I set that to disabled and my problems seem to have stopped, so far
Same problem here... Only all of my apps will not load before it crashes. Using latest milaq cm11. Wipe caches and problem persists. I rarely use googles hotword, believe its shut off...
Ideas??
LE S3, unrooted, using nova launcher. Two sim cards: one is ATT, the other is China Unicon(roaming on ATT). Just had the phone about three weeks.
My S3 often reboot itself, during text message, or browsing, or playing youtube, or in some apps, or even it is screen off resting on my desk. I couldn't find a pattern.
I performed factory reset and install about 10 frequently used apps. It has just 1 reboot over last 24 hours. I was cast youtube to chromecast and the phone was screen off and resting.
Another annoying issue is the fingerprint randomly lost function, it refuses my fingerprint. If I tried to add a new fingerprint, it prompted let me clean my finger and fingerprint identifier. Usually a reboot will solve the issue. But sometime it lost fingerprint function after a reboot.
Does anyone have similar experience? what could be the cause of those two issues? Is there any debugging log that can be checked? Should I contact support to get a fix/replacement?
Any help is appreciated!
Thanks.
Replace You're Phone..
Start from the beginning. Back a few weeks ago, when 4.1.5 was leaked but not officially announced, I downloaded 4.1.5 and flashed it through TWRP. Then 4.1.6 was released officially right after I've done my upgrading. So I CLEAN FLASHED 4.1.6 again on my phone.
Now the weird part: after 2 days of normal use (no flashing, no new apps installed), I left my phone charging today while went asleep. After I woke up, my phone is at 15% of battery. Although connect to the DASH charger, the phone doesn't charge at all with its LED showing red.
More weird is I can't open the notification center. I can pull the 5 toggles down, but can't open the whole menu.
Plus, notifications don't show up (no toast notification, no icons while in the homepage either).
My access to developer options is also blocked (says "Developer options is not available to this user").
The home button, recent apps button DOESN'T work - no matter if u switch the buttons in settings, or toggle the on-screen soft buttons. Although the "return" button and the fingerprint sensor DOES work.
Root access is still there (using Magisk).
While using TitaniumBackup, the app warns "This device's Android ID has changed". And a few apps have logged themselves out (I guess because of the ID change).
I think I can solve the problem by simply factory reset it. But Questions is : what's going on with my phone?
Its a common, not so common issue. I had exactly that same issue twice on two different fones. My old xperia L and my oneplus one. In my particular case, this was triggered when my settings were automatically restored from my google account (apps auto download, wifi settings, display settings etc.) After a factory reset.
After this, android id "crashes" showing that it has been changed, and statusbar only allows one pull down, along with the others bugs you described.
You should not allow google account to restore your settings (or at least that worked out for me) and restore manually your data. (Especially your display settings).
Hope it helps, i thought i was the only one.
elmarian756 said:
Its a common, not so common issue. I had exactly that same issue twice on two different fones. My old xperia L and my oneplus one. In my particular case, this was triggered when my settings were automatically restored from my google account (apps auto download, wifi settings, display settings etc.) After a factory reset.
After this, android id "crashes" showing that it has been changed, and statusbar only allows one pull down, along with the others bugs you described.
You should not allow google account to restore your settings (or at least that worked out for me) and restore manually your data. (Especially your display settings).
Hope it helps, i thought i was the only one.
Click to expand...
Click to collapse
Wow! I can't image someone had the same issue. So i actually re-flashed 4.1.6 and it's working.
But the charging problem persists. I've tried multiple power sources from the room, the kitchen, etc. None seem to be working.
Strangely, I was able to charge the device once a few hours ago at evening. And then it stopped charging again after I got the system working.
Any idea?
Hi Everyone,
It has been going on for roughly a year now, while I'm using my phone it suddenly just freezes entirely. Touchscreen just becomes unresponsive, can't tap on anything, gestures don't work and notification bar can't be pulled down.
Physical buttons does not seem to be affected, even if my screen is totally frozen I can still adjust volume levels and I can lock the phone via the power button. After locking and unlocking my phone, everything goes back to normal, touch responsiveness comes back and starts working as it should till the next hiccup.
It happens frequently, there are times when the screen locks up 2 or 3 times in a 10 minute period window. Every time this happens, I need to lock and unlock my phone and it starts working again.
Also it doesn't seem like a specific application is doing it, it happens when I'm browsing websites via Google Chrome, it happens with Amazon App, Messenger, Google Play Store, even on the Google News feed.
It gets more and more annoying as time goes by and it still hasn't been fixed.
I have been in contact with Google Support in the beginning when it started, but all they suggested is that I should do a Factory Reset (which I did).
Has anyone else experienced this issue or is it just my device doing this?
PS.: My phone is fully stock, hasn't been messed around.
Any physical damage to the device? & Have you tried checking if the issue occurs in safe mode too? If it is caused by a 3rd party or background app it wont replicate in safe mode.
Scan with Malwarebytes.
Try clearing system cache.
Try safe mode and a hard reboot.
That qualifies for erratic behavior and may be the only sign of a virus or trojan you'll see... at first.
Either way you could be headed for a boot loop.
Regardless even if Malwarebytes finds nothing it's factory reset time. Nuke it; a trojan can do a lot of damage to you in a short amount of time.
After the reload change your Google password.
Before you load -anything- make sure the issue is gone!
If it persists it's either a firmware or more likely a hardware failure.