Hi,
since I don't have over 10 posts here I can't post in the development thread so i have to make a new thread.
I'm using carbon rom. With sultan kernel the phone reboots sometimes when i want to turn the screen on. I noticed that the reboots appear when I open a picture in gallery and turn screen off and then try to turn it on again it reboots. Also it reboots when I pull the notification drawer down while phone is locked and turn the screen off. Most times it will go off and when i try to turn screen on again it reboots, sometimes it reboots when i try to turn screen off.
With r35 the problem with notification drawer was solved, but with r36 it's there again.
Hope it's understandable what I want to say.
Edit: okay I upgraded to latest carbon rom, now both things dont happen, but when i get facebook messages or whatsapp messages the notification drawer doesnt work.
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
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.
Nexus 5 is unlocked/rooted. Did a full factory reset when I installed L.
Will randomly go to phone and it is off/unresponsive off screen (need to hold power button to reboot it)
Have occasionally seen the notification icon flashing with the screen off but also unresponsive otherwise (asked for friend to call, but would not ring)
Have also seen it randomly reboot.
Seems to be happening at least every hour or so...quite maddening now.
Would love any help! thx.
Same Problem..Motherboard Issue
Hey..i was facing the same issues after update..Showed it to Service Center...Service center guy told that Update has screwed my Motherboard..If your are in warranty just take back it to service center guy..
I'm on stock LRX21O, flashed from img, unrooted, third attempt, and the thing is still crashing and freezing all over the place. I'm starting to think LRX21O is a dud, plain and simple.
FINALLy found a fix. Switched over to Franco Kernel -- having NO problems anymore!
Now on Franco Kernel + Cataclysm + greenify -- getting full day batter life with no reboots anymore!
edit: here's the kernel http://forum.xda-developers.com/google-nexus-5/orig-development/kernel-franco-kernel-r53-t2508284
Hello and pretty much as the title says for some reason I cannot dismiss my alarm. If I dismiss it it turns itself back on a few seconds and sometimes minutes later. I first noticed this on Blisspop but I have since clean wiped (including locally stored files) and put CM12 back on but oddly the problem is still occurring.
Has anybody else had this problem?
PS I did have a good google around but cannot seem to find something that related to my problem :\
loonitic said:
Hello and pretty much as the title says for some reason I cannot dismiss my alarm. If I dismiss it it turns itself back on a few seconds and sometimes minutes later. I first noticed this on Blisspop but I have since clean wiped (including locally stored files) and put CM12 back on but oddly the problem is still occurring.
Has anybody else had this problem?
PS I did have a good google around but cannot seem to find something that related to my problem :\
Click to expand...
Click to collapse
I'm on Blisspop unofficial that include CAF kernel... And i don't facing that kind of problem...
Are you sure that you are dismiss it, instead of just snooze it?
Hello, definitely dismissing it. I decided to wipe every bit of info\data etc on the phone so that nothing is left, installed CM12 again, without GAPPS so that it cant pull any settings that might be stored on my google account and guess what? Even on a pretty much blank rom I am still getting the same issue :\. Now starting to think it could be hardware but it seems very unlikely.
I have been facing same problem. It comes back after I dismiss an upcoming alarm after turn off the screen and turn it back on, it comes back. Any suggestions?
Same issue on CM12.1 ROM I'm using. I dismiss the upcoming alarm, but most of the time it activates back.