Related
First off, there are other threads on this topic but none of them seem to have an answer, and if you find an answer please post a link instead of telling me to search more.
Sometimes the phone randomly becomes unresponsive, its not with any certain app or anything, it just randomly happens. Usually pressing the sleep button and turning it off and on fixes it. It started in Android Revolution a while ago, stopped, and then came back a month later, I wiped everything and installed MIUI hoping this would solve my problem, well it didn't.
current setup
CWM 3.0.2.6
MIUI 1.7.8v1
FULL WIPE
CATTLEPROD KERNEL NOT OVERCLOCKED
DEFAULT THEME
Like you stated there are other threads on this. Please use them instead of opening a new one. There are many things that can lead to lag. I would look for others on the same rom as you and compare.
Thread closed
I would post this in the Developer forum, in reply to a poster who has the same problem, but I just registered and therefore do not meet the requirements to post there.
I'm wondering if anyone else has observed this behavior. In short, I installed TriForceROM 3.0 (after performing a "Wipe User Data" operation in TWRP 2.6.0.0) and all was well for about 12 hours. During the ROM installation, I chose the "Standard" option, as I believe it's called. (I didn't elect to customize anything.)
After 12-18 hours of having the ROM installed, I noticed that my phone was simply powered-off. I hit the power button and nothing. Then I held-down the power button, which is how I normally power-on the device, and then realized that the device was, in fact, powered-off when I came back to it after a few hours of being in the other room.
After powering-on the device, the same thing happened a few hours later, and the issue seems to be occurring more and more frequently as time passes.
I have not changed any of the ROMs settings, and I haven't installed any type of third-party "tweaking" app.
Another individual has the same problem:
http://forum.xda-developers.com/showpost.php?p=43942167&postcount=1466
Could this be due to kernel, power, or CPU settings? I noticed that when I opened KTweaker for the first time, the application warned me:
"Your KThermal values do not match current, Apply values?"
and
"Your vibration Strength does not match current, Apply Vibration Strength value?" (this one seems unrelated)
The CPU temperature seems to hover around 45 degrees Celsius. (Is this a normal range?)
Another observation is that when I long-press the Home button (to bring-up the app-switcher), I see a little Android icon with the title "MIPErrorActivi...". If I click on it, I'm simply dumped to the Home Screen. I don't know if this is at all related.
Thoughts or suggestions, anyone?
My phone is model SPH-L720.
Thanks in advance!
I went into KTweaker and clicked "Load Defaults" and rebooted, and everything seems to be stable. No reboots in 18 hours or so.
Also, the ROM author has mentioned this issue, as well as an interim fix (related to the KT kernel), and says that he will release v 3.1 within a few days, which should fix the issue entirely.
Good stuff!
UPDATE:
Well, the phone rebooted itself, eventually, so setting KTweaker settings to defaults was not the solution.
However, I downloaded the kernel update that the ROM author suggested ( http://forum.xda-developers.com/showthread.php?t=2288309 ) and that does seem to have fixed the problem. No reboots in over two days. Yay!
An interesting aside is that with the new kernel and accompanying KTweaker app, the warnings that I was receiving with the old kernel when launching KTweaker disappeared. All is well!
DrRichardQuack said:
I went into KTweaker and clicked "Load Defaults" and rebooted, and everything seems to be stable. No reboots in 18 hours or so.
Also, the ROM author has mentioned this issue, as well as an interim fix (related to the KT kernel), and says that he will release v 3.1 within a few days, which should fix the issue entirely.
Good stuff!
UPDATE:
Well, the phone rebooted itself, eventually, so setting KTweaker settings to defaults was not the solution.
However, I downloaded the kernel update that the ROM author suggested ( http://forum.xda-developers.com/showthread.php?t=2288309 ) and that does seem to have fixed the problem. No reboots in over two days. Yay!
An interesting aside is that with the new kernel and accompanying KTweaker app, the warnings that I was receiving with the old kernel when launching KTweaker disappeared. All is well!
Click to expand...
Click to collapse
Thanks for noting this. I actually started my account for the same reason, but haven't had enough useful input to get the posts to leave feedback in the dev forums. I sure don't want to spam useless posts :angel:
Lsd-Pulsar said:
Thanks for noting this. I actually started my account for the same reason, but haven't had enough useful input to get the posts to leave feedback in the dev forums. I sure don't want to spam useless posts :angel:
Click to expand...
Click to collapse
Haha. Well, glad I could be of help and that we both garner a couple of "useful posts" out of it.
I'm pretty sure that the reboots continued for me (although, less frequently with the kernel patch in place), but upgrading to TriForceROM 3.1 seems to have fixed the issue altogether. It's worth noting that I chose a different kernel this time (I forget what it's called; the name is four letters, all capitals). No reboots in the first 24 hours.
I doubt it makes a difference, but I also upgraded to the MF9 firmware from Samsung. Happy to answer any questions in that regard, too.
DrRichardQuack said:
Haha. Well, glad I could be of help and that we both garner a couple of "useful posts" out of it.
I'm pretty sure that the reboots continued for me (although, less frequently with the kernel patch in place), but upgrading to TriForceROM 3.1 seems to have fixed the issue altogether. It's worth noting that I chose a different kernel this time (I forget what it's called; the name is four letters, all capitals). No reboots in the first 24 hours.
I doubt it makes a difference, but I also upgraded to the MF9 firmware from Samsung. Happy to answer any questions in that regard, too.
Click to expand...
Click to collapse
I would wager that you moved over to AGAT's. Several users reported lag with that kernel, so I stuck with KT.
After more reboots and a lot of tweaking, I've got my issue nailed down. Raising the voltages on the low end cpu frequencies (where a phone would normally be with screen off) has corrected the stability issues. I also had to up the voltages at the high side. That helped Antutu to run for a while, but now that's crashing back to desktop for me. When it does run, I usually hit around 25,000 with the Triforce 3.0 + Ktoons kernel with overclock enabled. I have not overclocked the GPU (yet). Running KTmod, but not crossbreeder.
I may back this all up tonight and reflash with Triforce 3.1. I've been fighting battery issues: Google Location Services and Android Widgets Pro seem to be behaving badly.
I feel like I'm very close to a fast, stable rom install with good battery life. Once I get there, I'll wait a couple months until the existing ROM's and kernels are polished a little more. And now I'm one post closer to being productive in the Dev forum.
That's the one; AGAT's kernel. I haven't noticed any sluggishness with the ROM's (and or kernel's) default settings. So, I'm happy!
No random power-downs or any other abnormal behavior since upgrading to 3.1 and switching to AGAT's three days ago.
I don't know if it was upgrading from 3.0 to 3.1 or switching kernels that fixed the random power-downs; I'm just glad I have a very fast and stable ROM at this point.
My battery life has been good. Moderate usage throughout an 8-10-hour work-day leaves me with about 70% battery when I get home.
My hat's off to the developer. I think I'll kick him a few bucks.
Hi,
I am using the FatToad custom rom. Whenever I turn on my phone via power button the screen stays black. It doesn't look like the backlight is on. However, the menu button and back button light up. I tried using the volume rockers and home button to power on the screen but it's the same.
The screen does turn on after a couple tries. I have to press power button on (lights turn on), turn off, then back on. The number of tries varies. If I turn it off and back on immediately- then it comes back right away. Whenever I am done with a call, the screen stays off and I have to press the power button to get the screen back. I tried setting the phone to turn the screen on when plugging in charger cable but screen doesn't turn on right away. The auto-brightness seems to be working properly.
I didn't have this issue running the stock relay 4g rom. I have also tried the CarbonMod rom and OmniToad roms to see if it helped but would rather not have to go back to stock unless I need to.
I can live it with it but if anyone has a resolution it would be super awesome. Hopefully it's something simple that I messed up and not the phone itself!
Thanks,
-Alan
thebguard said:
Hi,
I am using the FatToad custom rom. Whenever I turn on my phone via power button the screen stays black. It doesn't look like the backlight is on. However, the menu button and back button light up. I tried using the volume rockers and home button to power on the screen but it's the same.
The screen does turn on after a couple tries. I have to press power button on (lights turn on), turn off, then back on. The number of tries varies. If I turn it off and back on immediately- then it comes back right away. Whenever I am done with a call, the screen stays off and I have to press the power button to get the screen back. I tried setting the phone to turn the screen on when plugging in charger cable but screen doesn't turn on right away. The auto-brightness seems to be working properly.
I didn't have this issue running the stock relay 4g rom. I have also tried the CarbonMod rom and OmniToad roms to see if it helped but would rather not have to go back to stock unless I need to.
I can live it with it but if anyone has a resolution it would be super awesome. Hopefully it's something simple that I messed up and not the phone itself!
Thanks,
-Alan
Click to expand...
Click to collapse
are you having this issue on all above mentioned roms....i have seen this issue before on other devices and is a deep sleep issue...i know the only rom you may be able to fix this on is my CarbonRom and done so by changing min frequency up a notch...if that doesnt work go down a notch....all other roms besides carbon have this feature force locked as far as i know so you cant do it on those roms
REV3NT3CH said:
are you having this issue on all above mentioned roms....i have seen this issue before on other devices and is a deep sleep issue...i know the only rom you may be able to fix this on is my CarbonRom and done so by changing min frequency up a notch...if that doesnt work go down a notch....all other roms besides carbon have this feature force locked as far as i know so you cant do it on those roms
Click to expand...
Click to collapse
I see. I will retry CarbonRom and up the min cpu and see if this issue goes away. Appreciate your feedback sir!
REV3NT3CH said:
are you having this issue on all above mentioned roms....i have seen this issue before on other devices and is a deep sleep issue...i know the only rom you may be able to fix this on is my CarbonRom and done so by changing min frequency up a notch...if that doesnt work go down a notch....all other roms besides carbon have this feature force locked as far as i know so you cant do it on those roms
Click to expand...
Click to collapse
I've got "FatToad" (nice rom, bad name) and the Trickster Mod app provides plenty of tuning options. Since the trouble manifests itself when the screen is off, I would look at mpdecision before I went raising the min frequency. Then again, I don't have many issues with getting my device to wake...
Anyhow, the app has options to tweak.
orange808 said:
I've got "FatToad" (nice rom, bad name) and the Trickster Mod app provides plenty of tuning options. Since the trouble manifests itself when the screen is off, I would look at mpdecision before I went raising the min frequency. Then again, I don't have many issues with getting my device to wake...
Anyhow, the app has options to tweak.
Click to expand...
Click to collapse
my Carbon rom is built differently than fattoad, cm, or omni...doesnt have lbcoders mpdecision touchboost amongst many other differences in its kernel
---------- Post added at 11:23 PM ---------- Previous post was at 11:16 PM ----------
thebguard said:
I see. I will retry CarbonRom and up the min cpu and see if this issue goes away. Appreciate your feedback sir!
Click to expand...
Click to collapse
if its at 192mhz go to 384mhz....if at 384mhz try 192mhz...if either dont work bump it up to the next highest mhz
I don't think changing the min cpu helped. Went up from 384 to 486. Then tried 594.
thebguard said:
I don't think changing the min cpu helped. Went up from 384 to 486. Then tried 594.
Click to expand...
Click to collapse
did you go to the lowest...also whats your method of flashing.....dirty flash? clean wipe?
REV3NT3CH said:
did you go to the lowest...also whats your method of flashing.....dirty flash? clean wipe?
Click to expand...
Click to collapse
The lowest option I had was 384mhz.
Flashing via CWM recovery: wiping data/system/cache/dalvik. Then CarbonRom and gapps. So clean wipe I think is what you are referring.
Sent you a zip to try via pm. Just let me know if it works.
Sent from my LG-VS980 using Tapatalk 4
Does this issue manifest itself when you have the phone plugged in? Can you get a logcat of the issue? Throwing things at the wall and seeing what sticks may not be the best resolution here. There are ways of finding out the underlying cause.
mpdecision is not the cause here (That only affects the secondary core) nor is min frequency (You can override it in the HypnoToad images too, just set another governor (like say 'conservative). In FatToad it may look like it resets because Cyanogenmod doesn't display the second core in the performance settings, but changing it is sufficient for testing. The official CM 11 builds do not have the touch boost (which only affects things after the phone is awake, and merely sets the secondary core's frequency up to 1184 Mhz when you are touching the screen, but the affect on the percieved performance of the phone due to this is immense)
Deep sleep is likely closer to the main cause because that affects both cores, and if the system isn't receiving the proper signals to wake back up, this can happen. Throughout development on apexqtmo, we've run into similar problems, and it's always helped by getting proper documentation from those who are experiencing the issues.
TL;DR: Trying random things likely won't solve this issue. Getting all the information you can will help.
Thanks again for all the help. I don't usually ask for any but I could not find much on my issue (or maybe I wasn't searching correctly).
I think I did the logcat correctly. See attached.
The thing that popped was:
D/SurfaceControl( 791): Excessive delay in unblankDisplay() while turning screen on: 269ms
Click to expand...
Click to collapse
When I would hit the power button and screen would not turn on, this would be there. I'm not really good with understanding this stuff. Hopefully this leads us in right direction though!
Edit: sorry forgot to answer your first question Magamo. This issue happens no matter if it's plugged in or not.
Edit 2: I watched the logcat from adb for awhile and I guess the above happens no matter what. I don't see any differences between if the screen turns on or not.
It looks like you have a hardware rev we're not supporting in our current kernel (which is why it works on stock). PM me if you want to mail your phone to me for analysis
This happened to a new device i purchased. After lbcoder and nard trailed through my logs, I was prescribed to resell the device. Your symptoms sounds identical to what I was experiencing. JB stock kernal works. But custom roms which since delved into the new edited kernel doesnt work on such devices. Since re-sold the device. Be interested to know if yours gets fixed where mine didn't. Good luck
Hi guys. I have a strange issue, that might be related to what's described in this thread.
Almost always when I open or close the keyboard, the screen goes blank for few seconds. One thing (that I think) helps is to press power button several times until the lockscreen comes up.
I am currently running LiquidSmooth 4.4.3, tried it with 4.4.4 and also some old backup 4.4.2 and the phones does it always. The critical position when it goes blank is just a millimiter when opening the keyboard from closed position.
Does any of you have the same experience? Can you please help me to determine either it's a ROM issue (deep sleep etc) or hardware issue?
I tried it also with the logos, boot animations and the screen goes blank too. So I fear it's hardware related - maybe a flex cable contact, but it would not come back so easily after few seconds. Another clue is that the keyboard lights and back+home stay on, but the screen goes blank.
I wish it's something that can be fixed by flashing or setting something as I waited few weeks to deliver my relay to Europe... Thanks for any help in advance!
sorgo said:
Hi guys. I have a strange issue, that might be related to what's described in this thread.
Almost always when I open or close the keyboard, the screen goes blank for few seconds. One thing (that I think) helps is to press power button several times until the lockscreen comes up.
I am currently running LiquidSmooth 4.4.3, tried it with 4.4.4 and also some old backup 4.4.2 and the phones does it always. The critical position when it goes blank is just a millimiter when opening the keyboard from closed position.
Does any of you have the same experience? Can you please help me to determine either it's a ROM issue (deep sleep etc) or hardware issue?
I tried it also with the logos, boot animations and the screen goes blank too. So I fear it's hardware related - maybe a flex cable contact, but it would not come back so easily after few seconds. Another clue is that the keyboard lights and back+home stay on, but the screen goes blank.
I wish it's something that can be fixed by flashing or setting something as I waited few weeks to deliver my relay to Europe... Thanks for any help in advance!
Click to expand...
Click to collapse
if its doing it an more than one rom it may be hardware...especially if its doing it at startup logo and bootani...does it do it on cm11 as well as omni?
REV3NT3CH said:
if its doing it an more than one rom it may be hardware...especially if its doing it at startup logo and bootani...does it do it on cm11 as well as omni?
Click to expand...
Click to collapse
Thanks for the reply. Yes the bootanimation and initial logo is telling enough about the cause of it. I must admit it's a hw problem. I tried to open/close the keyboard quicky instead of moving it slowly, but it occurs too. I'll try completely different rom with different kernel as the last chance
to hope for a sw issue.
I tried Omnirom with same result, but now I did a clean flash of the latest liquid and my impression is that this happens a lot fewer times than before. Maybe I just got the right velocity and force needed to open it gently I also installed just a few critical apps. Before I messed with Ultimate screen rotate etc.
But it now happens more when closing the keyboard. However, I'll rather buy new one, just ot have a backup of this great phone just in case.
http://www.cellulardr.com/samsung-t699-slide-flex/
Is this "the part" I need?
Do you have any experiences with this shop? It seems to me too much $40+shipping for that cable. Probably I'll just order another one from ebay, preferably new one and leave the current one for spare parts in the future.
Fixed today! You can see the state of the flex cable on the last picture in this post:
http://forum.xda-developers.com/showpost.php?p=56642402&postcount=35
New to posting here but I have been lurking for quite some time. I'll keep it brief here.
Suddenly, since flashing a 5.1.1 ROM, my N5 has been experiencing a sleep of death issue. Namely, once the screen turns off, it does not respond to anything. Pressing the power button does not wake the phone, and neither does plugging it in. After some time (~1 minute), the phone will reboot itself.
I know that this is not an uncommon issue, but the reason I have been forced to query the forums is because I have been unable to solve it by flashing ANY other rom. I've tried 5.1.1, 5.01, 5.0, and 4.3.3. I've searched and searched these forums and others to no avail. I've done countless restores to stock firmwares and 3rd party roms alike, removed apps and added them again, but nothing has solved my issue. I'm beginning to wonder if it is a hardware problem- that would be truly tragic.
I've pulled a kmsg but cannot attach it here as I have never posted, so I pulled a line that I believe is of interest, and would really appreciate it if you guys would look over it and tell me what you think.
Thanks!
KMSG
Code:
msm_vfe40_process_error_status: violation
[ 1066.509891] msm_vfe40_process_violation_status: camif violation
[ 1066.710201]
Hello World,
I recently purchased a SGN 12.2 Pro - Model Number SM-P900.
I flashed CyanogenMod onto it, and now its Android Version is 5.1.1
The CyanogenMod version is 12.1-20151104-Unofficial-v1aWIFI
The kernel version is 3.4.104-gd233b3f
Now for the most part the system runs smooth and w/o problems, but 7 or 8 times out of 10 when it goes asleep (screen is off and no program is actively running in the foreground, but the system was not shut down), I can not wake the tablet back up again.
Matter of fact, I end up having to perform a hard reboot on the tablet (pressing the power button until I force a reset) to get it to respond again.
I ran a logcat session in the background to catch any error, but the recorded log did not any error when this happened. It just suddenly stopped recording.
For me it seems like the system is going into some sort of hibernation mode, from which it only awakes after a hard reset.
But I don't see any such setting as "hibernation" in my system panel, and I certainly didn't install any such program on my tablet.
Now I am getting afraid that I might end up corrupting the filesystem or some important database by forcing these hard resets all the time.
That is why I need to find out what's going on here - anyone got some constructive ideas about it?
To rule out any potential hardware issues, you might want to try seeing if the problem occurs on stock as well.
ShadowLea said:
To rule out any potential hardware issues, you might want to try seeing if the problem occurs on stock as well.
Click to expand...
Click to collapse
Nice idea, but I need the functionallity of CM, and I also rely on my tablet for work - so I can't play "flashaholic" here.
But I have upgraded my CM Firmware three times in a row by now, and if this is CM related, then all those firmware packages would have to cause the same problem - with me being the only one who suffers from it (because I didn't read anyone else having this problem in the CM comment threads).
Really? Cwm for functionality? Even Snote doesn't work in cwm thus for a note device cwm is waste of space although for devices without spen i recommend cwm as well and do you want your problem to be fixed or not if yes then flash stock firmware to check if it's software or hardware related.
Osama chohan said:
Really? Cwm for functionality? Even Snote doesn't work in cwm thus for a note device cwm is waste of space although for devices without spen i recommend cwm as well and do you want your problem to be fixed or not if yes then flash stock firmware to check if it's software or hardware related.
Click to expand...
Click to collapse
Those are pretty brazen and broadband condemnations of a custom ROM that has won many distinctions and is even considered by industry groups as a replacement for STOCK ROMs.
And since SNOTE is part of Samsung's most crappy Software Suite, I truly would not regard *that app* as a benchmark of quality.
Now do you have any links to confirm your loudmouthed dismissal of CM, or does that fall into the same category as urban myths such as "openSUSE isn't real Linux" and "Virus Scanners are useless"?
And by the way: CM = Cyanogen Mod (Custom Firmware); CWM = Clockwork Mod (Custom Recovery).
Not the same by a longshot - and I use TW for recovery anyway.
PS: I found a solution by now in installing an app which prevents the tablet from going into deep sleep mode (-> CPU_WAKE_LOCK). As it seems at times the tablet would come back online after some seconds, *if* I let go of the power button in time. But since I have the tablet hooked up to a power source most of the time anyway, I don't need deep sleep mode, and I was never good at counting seconds when pressing the power button.
That app resolved the "sleep of death" issue for me.
PS#2: As a systems admin I generally refuse advise of the kind of "just reinstall (flash) from scratch and see if it fixes the problem", for that is *not* debugging, its just being too lazy to perform root cause analysis.
Masinissa said:
Those are pretty brazen and broadband condemnations of a custom ROM that has won many distinctions and is even considered by industry groups as a replacement for STOCK ROMs.
And since SNOTE is part of Samsung's most crappy Software Suite, I truly would not regard *that app* as a benchmark of quality.
Now do you have any links to confirm your loudmouthed dismissal of CM, or does that fall into the same category as urban myths such as "openSUSE isn't real Linux" and "Virus Scanners are useless"?
And by the way: CM = Cyanogen Mod (Custom Firmware); CWM = Clockwork Mod (Custom Recovery).
Not the same by a longshot - and I use TW for recovery anyway.
PS: I found a solution by now in installing an app which prevents the tablet from going into deep sleep mode (-> CPU_WAKE_LOCK). As it seems at times the tablet would come back online after some seconds, *if* I let go of the power button in time. But since I have the tablet hooked up to a power source most of the time anyway, I don't need deep sleep mode, and I was never good at counting seconds when pressing the power button.
That app resolved the "sleep of death" issue for me.
PS#2: As a systems admin I generally refuse advise of the kind of "just reinstall (flash) from scratch and see if it fixes the problem", for that is *not* debugging, its just being too lazy to perform root cause analysis.
Click to expand...
Click to collapse
You may be right but generally in samsung firmwares there are problems with the firmware itself...anyway...if you do find the root cause let me know although when I installed the cyanogen mod 12 this didn't happen I think it was a problem of wake lock in some early builds of rom. Have you experienced this after updating to latest builds?
Osama chohan said:
You may be right but generally in samsung firmwares there are problems with the firmware itself...anyway...if you do find the root cause let me know although when I installed the cyanogen mod 12 this didn't happen I think it was a problem of wake lock in some early builds of rom. Have you experienced this after updating to latest builds?
Click to expand...
Click to collapse
Hi Osama,
the problem startetd after I had installed some software tools for power management and activated CM's own CPU governor.
That is why I suspected this not be a case of a software loop caused by a program or Firmware bug, but a problem with the system waking back up from deep sleep mode.
Now I could have just uninstalled everything and disengaged the CPU governor altogether, but as I wrote earlier on, I don't think highly of such "let's reset it all to zero and see if at fixes things" approaches.
Also, I liked the battery savings options, I just needed a way to prevent the CPU from going all the way down into deep sleep mode.
I found that solution in the form of a small APK on the market place, which does exactly that - and only that.
It prevents the CPU from being turned off (CPU_WAKE_LOCK), whilst still allowing for the screen, bluetooth, WiFi and so on to be turned off, to save battery power.
That fixed my problem almost completely, and now it happens only when the app (I use RedEye) for some reason isn't auto-activated at boot.
Masinissa said:
Hi Osama,
the problem startetd after I had installed some software tools for power management and activated CM's own CPU governor.
That is why I suspected this not be a case of a software loop caused by a program or Firmware bug, but a problem with the system waking back up from deep sleep mode.
Now I could have just uninstalled everything and disengaged the CPU governor altogether, but as I wrote earlier on, I don't think highly of such "let's reset it all to zero and see if at fixes things" approaches.
Also, I liked the battery savings options, I just needed a way to prevent the CPU from going all the way down into deep sleep mode.
I found that solution in the form of a small APK on the market place, which does exactly that - and only that.
It prevents the CPU from being turned off (CPU_WAKE_LOCK), whilst still allowing for the screen, bluetooth, WiFi and so on to be turned off, to save battery power.
That fixed my problem almost completely, and now it happens only when the app (I use RedEye) for some reason isn't auto-activated at boot.
Click to expand...
Click to collapse
I'm glad that you fixed the problem and sorry that i couldn't be of any help.