Database Info

Anyone else with problems like this?

Recently put ViperXL on and took updates now its ViperXL 3.2.5, put kernel 3.4.10-ElementalX v5.0 vanilla on, flashed radio 2.41.,S-OFF.. Now the screen at times becomes unresponsive like when deleting apps,touch the app , it opens but it wont move or delete.IF I reboot, the screen behaves like it should for an unknown period then problem starts to repeat itself untill rebooting again. Another issue I noticed lately before flashing Viper is in TWRP , especially when rebooting, tapping the reboot button it wont respond for a short period,I might have to tap several times to get reboot to happen. I am wondering if I put too much on the system or might it be something internal?

leesumm said:
Recently put ViperXL on and took updates now its ViperXL 3.2.5, put kernel 3.4.10-ElementalX v5.0 vanilla on, flashed radio 2.41.,S-OFF.. Now the screen at times becomes unresponsive like when deleting apps,touch the app , it opens but it wont move or delete.IF I reboot, the screen behaves like it should for an unknown period then problem starts to repeat itself untill rebooting again. Another issue I noticed lately before flashing Viper is in TWRP , especially when rebooting, tapping the reboot button it wont respond for a short period,I might have to tap several times to get reboot to happen. I am wondering if I put too much on the system or might it be something internal?
Click to expand...
Click to collapse
delay with twrp reboot is normal. issues with custom kernels are pretty common as you are pushing your phone beyond spec and making the phone do things it wasn't really designed to do. imo the screen freezing is due to s2w but i could be wrong. i think you can turn s2w off in elemental, try turning it off and see if you still get freezing.

could be.
DvineLord said:
delay with twrp reboot is normal. issues with custom kernels are pretty common as you are pushing your phone beyond spec and making the phone do things it wasn't really designed to do. imo the screen freezing is due to s2w but i could be wrong. i think you can turn s2w off in elemental, try turning it off and see if you still get freezing.
Click to expand...
Click to collapse
This could be the trick. I tried this morning and so far today there hasn't been a hangup on apps. I tried a couple and everything as usual. But this has been a intermittent thing not knowing when or how it would happen.

Yeah I have found some of the Venom tweaks really affecting responsiveness. For example if you could figure power long press to turn on the flashlight it takes NOTABLY longer to wake the phone. I can see s2w having the same effect

Here I thought I was the only one experiencing this issue. I did a full wipe and format and flashed a bone stock (default configuration) flash of ViperXL to see if that would solve the issue. Screen issue doesn't occur as often as before bit it still happens. I found that if I block the light sensor, the screen begins to behave normally. I don't have a logcat yet but can upload if necessary.
Sent from my HTC One X using xda app-developers app

same problem again.
leesumm said:
This could be the trick. I tried this morning and so far today there hasn't been a hangup on apps. I tried a couple and everything as usual. But this has been a intermittent thing not knowing when or how it would happen.
Click to expand...
Click to collapse
I thought wrong , again, tried this morning just moving an app from home screen to second screen. It will open but unable to move it or delete it from the screen. Rebooted and seems everything is normal again.

Are you using 4x5 Rosie?
Sent from my VENOMized HoxL

area51avenger said:
Are you using 4x5 Rosie?
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Not really sure, I can't find anything that 4x5 is enabled. S2W I disabled also, this is not a big problem just irritating some times. Things usually start working normal when I reboot system .

You could try increasing the voltage.

ken bentley said:
You could try increasing the voltage.
Click to expand...
Click to collapse
At this point I am not sure I am that smart to be messing with volotage and such on the inside of this thing.

just stopped using a custom kernel. i stopped using them cause of freezing issues.

Revelation Rom random reboots

Hi, I have a problem with random reboots on Revelation Rom. I already know some users have already reported some issues with it. Full reboots are totaly random, they happen when i dont use the phone (sleep), when i try to unlock it, or doing anything like typing a message, using web browser, etc. Ofcourse i did a full wipe befeore install, installed rom with default settings, i also didn't restore any apps, or something.
This is my last_kmsg from last reboot, i hope it will help SebastianFM to solve the problem (i believe there is one, other roms work like they should and i think i also do everythig like i should during install and after).
Can't post it in dev sectcion due to 10 posts restrictions.
Cheers.

Use 1188 mhz max cpu frequency, no cpu control software, I don't have reboots.
Sent from my HTC Sensation Z710e using Tapatalk 2

I have already tried to set 1188, 1296 and 1512 during install, all options gave me the same results, so i think it is not realted to CPU max freq.

I don't know if we have the same problem, I have my sensation turning off randomly for no reason what so ever. The weird thing is when it is plugged in, it doesn't turn it self off. I already brought a new battery so shouldn't be that. I also tried putting some paper in the battery section in case there was a lose connection. Played around with software, got nothing changing ROM, changing CPU freq, changing radio... nothing helps. I think mine problems are random reboots + shutdown, so it is not all ways the case it has rebooted. But when it does do the random reboot, it is often when I am trying to wake the device. I have no idea when it shuts down since when I try to wake it, it was shut down. Then I had to hold the power button to turn it on. Lastly, I think i get mostly shutdown.

Well, i don't know what is causing your problem. If you change between different roms/kernels/firmwares/radios/etc. and problem always exist, it can be hardware related.
Mine only appears on Revelation rom, and i always get the full reboot (no soft reboots or shutdowns).

Lubosz said:
Hi, I have a problem with random reboots on Revelation Rom. I already know some users have already reported some issues with it. Full reboots are totaly random, they happen when i dont use the phone (sleep), when i try to unlock it, or doing anything like typing a message, using web browser, etc. Ofcourse i did a full wipe befeore install, installed rom with default settings, i also didn't restore any apps, or something.
This is my last_kmsg from last reboot, i hope it will help SebastianFM to solve the problem (i believe there is one, other roms work like they should and i think i also do everythig like i should during install and after).
Can't post it in dev sectcion due to 10 posts restrictions.
Cheers.
Click to expand...
Click to collapse
These reboots are caused by kernel 3.4.10, not ROM, so we may continue this discussion on my kernel related thread. Reboots occurs only on few devices. I received many kernel logs, but I didn't find the reason, errors are different for each user.

The 12th day on the Revelation ROM and not a single reboot.
Also writing here due to the 10 post's rule eek
Will go back to the Revelation thread after this post because I really like the SebastiamFM's work and I have none of there mantioned problems (maybe one or two).
I was havign problems on the begining thoe... i couldnt startt the phone. It rebooted when I had to insert the PIN code or before the Sense even managed to load. Then I formated everything (including the SD card) to eliminate any "remains" of previous ROM's and i set the GPU on 300 and the MAX freq to 1520 and from than till now not a single lag.

Lubosz said:
Hi, I have a problem with random reboots on Revelation Rom. I already know some users have already reported some issues with it. Full reboots are totaly random, they happen when i dont use the phone (sleep), when i try to unlock it, or doing anything like typing a message, using web browser, etc. Ofcourse i did a full wipe befeore install, installed rom with default settings, i also didn't restore any apps, or something.
This is my last_kmsg from last reboot, i hope it will help SebastianFM to solve the problem (i believe there is one, other roms work like they should and i think i also do everythig like i should during install and after).
Can't post it in dev sectcion due to 10 posts restrictions.
Cheers.
Click to expand...
Click to collapse
Try using performance governer instead of ondemand.
Happy to help.

You could try reseating the battery or securing it a bit tighter, some users have reported reboots because of the battery being somewhat 'loose'.

[Q] Black screen

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

No idea what this problem is? anybody able to offer advice?

I currently have an N5 which is running PA (4.5 beta2) and Franco (R59) and i seem to come across this issue no matter what version (or combination of versions) i end up using.
The issue - After installing the rom and kernel it will work fine for a week or so and then after that period it will have this issue whereby I press the power button and nothing will happen to the screen, it just stays black but i know the phone is still on because the LED will flash. From this point onwards i usually just reset the phone and then it will work fine for the first maybe 20 mins and then it ends up doing the same thing again.
I know it isnt a problem with the power button itself cause it works totally fine after the phone resets (and im still able to reset the phone using the power button), sometimes the screen will actually power up when i press the button and it shows me my home screen but then fade to a black screen and it just does that over and over again (during that period you cant actually do anything, tried touching screen, volume up+down etc and there is just no response) unless you reset the phone.
any help would be appreciated

It could be one of a few things. Generally it will be an app or a kernel setting. I would recommend ruling out kernel first by flashing ROM without the kernel.
Sent from my Nexus 5 using Tapatalk

Yeah that definitely seems like a kernel issue. Try just flashing the rim by itself as mentioned above. Also what apps do you have install that deal with display stuff, ex. Lock screen notifications, led light etc.?

nym27jrey said:
...Try just flashing the rim...
Click to expand...
Click to collapse
Not sure you want to do that

hi guys, im pretty sure i have found the source of the problem now. I normally have the 'Twilight' app (nothing to do with teenage vampires + werewolves) in the background which softens the colours and dims the screen to a level which is more pleasant for the eyes at night. After uninstalling this it seems as though the problem has gone.
I think the app itself projects an overlay on top of the launcher to dim the screen but sometimes when the app is running and the screen is dimmed it seems to block out (unable to tick) some of the pop-up boxes which some programs throw up. Too bad, i really liked the app too, might just have to email the developer and let him know.
Now on to my next problem, anybody know of another app which does similar? lol

ticketseriously said:
Now on to my next problem, anybody know of another app which does similar? lol
Click to expand...
Click to collapse
Chainfire's C.F. Lumen

OK I was wrong. After uninstalling all the apps which have an effect on my display as well as reinstalling the ROM without the Franco kernel its still having the same issue.
I left a music app running this time and then left the phone till it put itself into sleep/lock mode. The app continued to run and I could change the volume with the side buttons but when i Pressed to get the screen on it just stays black now but it seems as though everything is still running in the background. Anybody had this type of issue with PA before? Thanks

One last question on the kernel, do you have any tweak apps running?
Sent from my Nexus 5 using Tapatalk

ticketseriously said:
OK I was wrong. After uninstalling all the apps which have an effect on my display as well as reinstalling the ROM without the Franco kernel its still having the same issue.
I left a music app running this time and then left the phone till it put itself into sleep/lock mode. The app continued to run and I could change the volume with the side buttons but when i Pressed to get the screen on it just stays black now but it seems as though everything is still running in the background. Anybody had this type of issue with PA before? Thanks
Click to expand...
Click to collapse
its sod, sleep of death. its not really known what causes it on the n5, but it happens. raising your voltages might help you, as it helps a few, but not all. if it happens that often, id see about an rma after flaahing the factory img to test.

Running beta software, custom kernel... Seems you're in for more that what you've bargained for.
Just do as simms22 says and flash latest factory image.

Sleep of Death befalls my SGN 12.2

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.