Database Info

HELP: Phone locks up and dies at random

I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!

Sounds like a warranty replavement to me.
Caution swyping! Read at your own risk.

TheSopranos16 said:
I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!
Click to expand...
Click to collapse
What kernel are you running? And are you OC/UV?
If so, try a different kernel (like speedmod k13e) that doesn't have OC/UV option. Black screen is usually a UV setting problem.
If it's not the case, warranty?
EDIT: Have you flashed over different ROM with lagfix/ OC/UV enabled?

Right now I'm running lastest Cog 4 with the included kernel (which doesn't support UV). I was OC but once I had this issue I reset the clocks to stock but then it happened again. Before I installed Cog 4 I flashed stock and master cleared...

1. Did u restore any data using TiBu when u flashed the ROM? Did u happen to restore any system data?
2. Did u put on any kind of under volting?
Flash any ROM, say Firefly, and use it for a day or two without restoring any of ur apps, and see if the issue is coming up again.
If yes, try changing kernel, say to onix, and keep on for a day or two see if the issue is recurring.
Just to be sure, can u do this:
1. Revert to stock
2. Format internal SD (similar to master clear to clear out SD card; I never did a master clear so far, only this)
3. Copy the ROM u want to use to SD
4. Flash Firefly 3.0 (this formats all system partitions, so no need to master clear)
Firefly has hardcore's kernel by default, and this kernel does not apply lagfix by default. Same with onix kernel too, and this is the reason I am recommending this combination of ROM and kernels. I use onix cos I have some wifi issues on hardcore's kernel.
5. Do NOT restore of ur data or apps

I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...

TheSopranos16 said:
I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...
Click to expand...
Click to collapse
I would NOT recommend ANY system data, except for contacts storage. This is the only one system data I personally found not to cause any issues.
Its easier to connect BT and wifi again, than go through the pain restoring this data sometimes creates. I faced issues with my phone not being paired to my car when I tried to restore bluetooth settings. It shows my car, but doesn't pair. I had to restart phone, delete the connection, and then reconnect. I found it easier to add back, than restore and go through all this trouble.
This time, pls try to refrain from restoring any of ur data from TiBu and a day's run for the ROM and see how it goes. If it goes well, u can restore data. But, before u restore data, I would recommend taking a nandroid backup just in case restoring apps starts creating issues again. This could save some time by getting u back to current state with no apps, instead of flashing all over again.

Before doing any of those things, I would check out your IMEI number and compare it to the one in this link,
http://www.captivateforums.com/sams...random-shutdown-issues-on-att-captivate-1272/
I dont pay for any warranty through AT&T, but I brought my phone in to a device replacement center and they replaced mine with a brand new phone!
Its worth a shot if you ask me.

Question: System crashing and rebooting since today

Hi all.
Is there a known issue with the latest "standard application updates" that may cause the system crashing and rebooting?
I dont know if there is such a thing like "event log" in android to help tracing the error im getting since today.
First time was while I was playing Mortal Kombat X Mobile, game went unresponsive, screen black, charge led was flashing strangely and very short, almost unrecognizable. Now this could perfectly happen just on the homescreen.
Occurs once in a while, Id say almost every 1-2 hours.
Have the latest stock rom , patched, rooted and some minor debloating. Havent touched the system for weeks, everything was perfectly fine, this is the first day it is not.
So if anyone can give me a hint on how to find whats wrong , that would be great.

Guess I'm not the only one! I've been having the same exact problem since yesterday too!

onkelfeix said:
Hi all.
I dont know if there is such a thing like "event log" in android to help tracing the error im getting since today.
Click to expand...
Click to collapse
There is logcat. You're rooted, so it's fine. You can also pull logcat logs via adb. However these logs are cleared once the phone reboots.

I've been having heating issues,very fast battery drain and my camera went back to taking green pictures . It was beacause of updating magisk. I uninstalled it and reflashed the 14v and it is back to normal. I'd recommend seeing if that is the problem

pikeylfc said:
I've been having heating issues,very fast battery drain and my camera went back to taking green pictures . It was beacause of updating magisk. I uninstalled it and reflashed the 14v and it is back to normal. I'd recommend seeing if that is the problem
Click to expand...
Click to collapse
I still have 14.5 installed while it tells me 15.3 is the latest.
No overheating (at least nothing that could be felt on the outside) , camera works as it should.
Did a shutdown and restart, device didnt crash over night, now after its been used for 30minutes, it crashed while reading the news within chrome....
Maybe some kind of Spectre/Meltdown countermeasure patch which affects stability?
Really cant need that as I use my phone for 24/7 support

Just found out that I didn't have the latest build. Was on 47.1.A.5.51 probably.....
Now on 47.1.A.8.49 , still rooted , restored almost everything what has been installed before, so far it has been crash-free since 1-2 hours. If it doesn't crash within the next 24hours , i'll put the simcard back.

Screen not working?

It's sort of laggy, when I want to tap on an app to open it, for example, it takes a few taps or sometimes just doesn't work at all.
The problem doesn't seem to be only on one area of the screen though, the whole screen has the same problem.
Haven't installed any recent updates or anything, in case that could be a cause of the problem. I've tried restarting the phone a few times and also wiping the screen but it hasn't worked.
I've also tried using the optimise and clean up options in the Phone Manager, but they haven't improved anything...
The screen was working like normal just this morning, but then around late afternoon the problem started.
I haven't installed a custom ROM or any other major modifications like that, by the way. The phone is pretty much the same as it was since I bought it. EMUI v8.0 and Android Oreo.

Try a factory reset?

Galaxy s10e. Lags after update to android 10

Hello to all. unfortunately after the update to android 10 some lag appeared that remind me a lot of the s8 .... it's a nightmare that haunts me. I did not reset and I would like to avoid it, could someone tell me if it has been affected by this problem and if it is possible to remedy it without resetting? thank you

I would suggest first wiping the cache from stock recovery mode. See how it runs and if it picks up. You do also have to ensure apps are updated as needed.

Mine lagged too after the oneui 2 update. I've done a reset and at first it was smooth before I restored apps and settings. But after restoring it started to lag especially on home and recents screen. I found a solution to turn off adaptive power saving. Now it's super smooth
Edit: I found out that the lag comes from accessibility services. Mine was AutoSkip. After I turned it off home and recents becomes smooth again.

So, did u advice to avoid the update? I bought mine today and I was wondering if it was worth it...

CatenaccioFM said:
So, did u advice to avoid the update? I bought mine today and I was wondering if it was worth it...
Click to expand...
Click to collapse
If you just bought the device, I recommend to not install all your apps yet, but first update all way up to Android 10 (keep updating until there’s no new updates available), and then make a factory reset. After this you can install your things normally.
I've made this process and now my S10e runs like a butter!
EDIT: As mentioned by @kdanina, turn OFF adaptative power saving, but let adaptative battery ON. They seem to be similar but in practice the first one is flawed on our device.

Question AOD and screen wake on notifications stopped working

Hi all!
I've been searching for a solution for some time but couldn't find any.
Always On Display stopped working on my Pixel 6a. It's all turned on in the settings but it simply doesn't work. It works only in those cases:
1. When device is rebooted into an Airplane mode
2. When device is rebooted into the Safe Mode
3. When device is rebooted but not unlocked for the first time
There are also no notifications displayed so screen wake on notification doesn't work. Same story as above.
I thought there is some app blocking it but couldn't really figure out which, I tried to disable many of them but none helped.
I did a factory reset once but issue came back after few days.
I seriously have no idea what might it be. Hope someone here might have had similar problem and found a solution.
Thanks!

Czarls said:
Hi all!
I've been searching for a solution for some time but couldn't find any.
Always On Display stopped working on my Pixel 6a. It's all turned on in the settings but it simply doesn't work. It works only in those cases:
1. When device is rebooted into an Airplane mode
2. When device is rebooted into the Safe Mode
3. When device is rebooted but not unlocked for the first time
There are also no notifications displayed so screen wake on notification doesn't work. Same story as above.
I thought there is some app blocking it but couldn't really figure out which, I tried to disable many of them but none helped.
I did a factory reset once but issue came back after few days.
I seriously have no idea what might it be. Hope someone here might have had similar problem and found a solution.
Thanks!
Click to expand...
Click to collapse
Would you be down to try flashing a custom ROM?
I've read in another thread not long ago someone saying their Tap to Wake randomly stopped working. We narrowed it down to an issue with the proximity sensor (so the phone thought it was in a pocket/covered, therefore didn't let Tap to Wake work, he had to use the power button to turn the screen on). He then flashed a custom ROM (it was LOS, I think), and that solved the issue for him.
I've also had some issues with the stock ROM, flashing a non-factory one solved all of them
If you want to keep on using the factory ROM, you might wanna try using the Android Flash Tool instead of just factory resetting to make sure no corrupted settings can live on.

Lada333 said:
Would you be down to try flashing a custom ROM?
I've read in another thread not long ago someone saying their Tap to Wake randomly stopped working. We narrowed it down to an issue with the proximity sensor (so the phone thought it was in a pocket/covered, therefore didn't let Tap to Wake work, he had to use the power button to turn the screen on). He then flashed a custom ROM (it was LOS, I think), and that solved the issue for him.
I've also had some issues with the stock ROM, flashing a non-factory one solved all of them
If you want to keep on using the factory ROM, you might wanna try using the Android Flash Tool instead of just factory resetting to make sure no corrupted settings can live on.
Click to expand...
Click to collapse
I would say it does not have anything in common with the proximity sensor since it works fine with airplane mode turned on. I want to stay with the factory ROM. Maybe it's an issue that will be fixed any time soon?

Czarls said:
I would say it does not have anything in common with the proximity sensor since it works fine with airplane mode turned on. I want to stay with the factory ROM. Maybe it's an issue that will be fixed any time soon?
Click to expand...
Click to collapse
Why do you ask for advice if you just want to "wait for it to get fixed"?
If you've done a factory reset already, it's not a hassle re-flashing the factory ROM (since you already have your data backed up).
Fwiw, the guy with the proximity sensor issue also had it sometimes work and other times not, much like your issue

Lada333 said:
Why do you ask for advice if you just want to "wait for it to get fixed"?
If you've done a factory reset already, it's not a hassle re-flashing the factory ROM (since you already have your data backed up).
Fwiw, the guy with the proximity sensor issue also had it sometimes work and other times not, much like your issue
Click to expand...
Click to collapse
I'm trying to figure out if it's a software issue in a ROM or some applications impact..