Im using PA4.5 with franco kernel (i switched to this kernel because the standard kernel also had this problem
After a while i try to wake up the device with gestures (i always try with gestures first and then with the power button) it just dont turn on the display.
Adb and the home, back and option buttons are lighted up, the cpu is also pushed to different freqs, but the screen keeps empty. I need to force a restart and it boots normally.
I have turned on any gesture.
I couldnt find any to Opo related thread
Edit:
I have installed xposed app settings
Does it happen on other ROMs our only on PA?
Transmitted via Bacon
I didnt test, but isnt there anybody who has the same problem? I love this phone, and PA makes it more awesomer
Rather than waiting to see if someone has the same problem, you can do two things.
1) Search the PA thread to see if the same problem has been reported there.
2) Flash another ROM temporarily to see if the problem sill occurs. This will tell you if it's isolated to PA or not.
Transmitted via Bacon
So the phone does not turn on when your double tapping the screen or using power button?
It seems like you're having the sleep of death problem. Are you under volting by any chance?
Also, do you have capacitive buttons on? If so, do they light up when you double tap or press power?
Sent from my One using Tapatalk
timmaaa said:
Rather than waiting to see if someone has the same problem, you can do two things.
1) Search the PA thread to see if the same problem has been reported there.
2) Flash another ROM temporarily to see if the problem sill occurs. This will tell you if it's isolated to PA or not.
Transmitted via Bacon
Click to expand...
Click to collapse
I now flashed cm11 nighly for testing
zephiK said:
So the phone does not turn on when your double tapping the screen or using power button?
It seems like you're having the sleep of death problem. Are you under volting by any chance?
Also, do you have capacitive buttons on? If so, do they light up when you double tap or press power?
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I read something about sod, but i didnt understand what sod means ^^
No, no undervolting on a new phone with nearly unlimited speed
But the processor govenour is working i checked the current freq with adb and it seems its working. Only display does not turn on.
I also have sometimes no signal, but thats not related i think
_Beni_ said:
I now flashed cm11 nighly for testing
I read something about sod, but i didnt understand what sod means ^^
No, no undervolting on a new phone with nearly unlimited speed
But the processor govenour is working i checked the current freq with adb and it seems its working. Only display does not turn on.
I also have sometimes no signal, but thats not related i think
Click to expand...
Click to collapse
Sleep of death is pretty much what you said. If you have your capacitive buttons on, there are cases where those buttons light up and the screen does not turn on.
Sleep of death is when your phone is still on but when you turn the screen on it doesn't turn on. I personally didn't have the problem but use the stock kernel for a half a hour. See if it still occurs, it's not rom related it's kernel related.
Sent from my One using Tapatalk
Thanks for the name of my issuse, it seems to be caused by xposed.
So it should not appear now, i will write in this thread if its reappeard. No logcat related to the issue is logged
The SOD does not happen often.
Just sometimes
_Beni_ said:
Thanks for the name of my issuse, it seems to be caused by xposed.
So it should not appear now, i will write in this thread if its reappeard. No logcat related to the issue is logged
The SOD does not happen often.
Just sometimes
Click to expand...
Click to collapse
Hm good information. So it doesn't sod when you're not using xposed and works with Franco and cm?
Sent from my One using Tapatalk
zephiK said:
Hm good information. So it doesn't sod when you're not using xposed and works with Franco and cm?
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I dirty flashed CM, in the offical OPO forum smb wrote that uninstalling xposed fixs it.
zephiK said:
Sleep of death is pretty much what you said. If you have your capacitive buttons on, there are cases where those buttons light up and the screen does not turn on.
Sleep of death is when your phone is still on but when you turn the screen on it doesn't turn on. I personally didn't have the problem but use the stock kernel for a half a hour. See if it still occurs, it's not rom related it's kernel related.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Stock Kernel(Mahdi's Kernel) is not giving me SOD but Franco is...
skydayzer said:
Stock Kernel(Mahdi's Kernel) is not giving me SOD but Franco is...
Click to expand...
Click to collapse
Im now running with cm11 stock for test reason, reboot happend in my pocket, i dont know why.
Have you expirence with PA stock kernel?
_Beni_ said:
Im now running with cm11 stock for test reason, reboot happend in my pocket, i dont know why.
Have you expirence with PA stock kernel?
Click to expand...
Click to collapse
I've used Franco's Kernel upto now with Mahdi-Rom 2.7... And now am running it's kernel and it's working well
Ok i dont want anymore a noname rom, too much change when i switch the phone
EDIT:
nice my bluetooth headset is not working with cm11, lets go back to PA
zephiK said:
Sleep of death is pretty much what you said. If you have your capacitive buttons on, there are cases where those buttons light up and the screen does not turn on.
Sleep of death is when your phone is still on but when you turn the screen on it doesn't turn on. I personally didn't have the problem but use the stock kernel for a half a hour. See if it still occurs, it's not rom related it's kernel related.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I received my Oneplus one 2 weeks ago, and i have been keeping it stock with cm11s. However I am experiencing the same issue. As you suggested, my capacitive button turned on, but the screen stayed dark. May I ask where can I find that fix for this case? thanks.
gary93 said:
I received my Oneplus one 2 weeks ago, and i have been keeping it stock with cm11s. However I am experiencing the same issue. As you suggested, my capacitive button turned on, but the screen stayed dark. May I ask where can I find that fix for this case? thanks.
Click to expand...
Click to collapse
Did you update to XNPH33R to see if the problem still occur?
had the issue too, guess it wasnt resolved and i created a jira ticket, you may as well just vote for it now..
Google: jira bacon-736
sorry, but i'm not yet allowed to post outside links!
?
is it a kernel problem?
Related
As the title suggests, I have a Nexus S i9023 (no root, perfectly clean) and the major problem is that i've upgrade the phone to ICS manually and now there are some things that don't work (recovery, light sensor, etc.). I know that there are a lot of threads like this, i know that the problem of the recovery is a problem of brightness, but i wanna know which ROM i've to flash. I'm using the build IML74K.
Another problem is that sometimes the keyboard freezes. Is it caused by the wrong build?
Which rom did you flash?
Try lastest version of ics
I'm using ICS 4.0.3, build IML74K, flashed manually.
Sent from my Nexus S using XDA App
alfax21 said:
I'm using ICS 4.0.3, build IML74K, flashed manually.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I am using the same on my i9023 with no issues, only difference is I am rooted and have clockwork recovery. I suggest a re flash.
I'll try to re-flash the same ROM. If it won't work i'll root the phone and i'll flash CM9.
Anyway, how can i solve the problem of the keyboard? I don't think it's a problem of the build.
I've flashed the ROM for Nexus S i9023 two times but the problems still remain. Any suggestion?
alfax21 said:
I've flashed the ROM for Nexus S i9023 two times but the problems still remain. Any suggestion?
Click to expand...
Click to collapse
Only thing I can suggest is installing clockwork recovery, rooting etc and flashing another rom to see if the problem persists, if so then it probably a hardware issue.
Also where did you get the rom your flashing? There is a thread in the general section with the full rom package I used. Its on the first page at the mo.
Ok maybe there's no solution (i'm new in this forum so i can't post link as the one below):
code.google.com/p/android/issues/detail?id=23065&can=1&q=ics%20nexus%20s%20i9023%20recovery&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
So I think it will be fixed in the next release. I ask confirmation if someone knows something.
CONTACTMC said:
Also where did you get the rom your flashing? There is a thread in the general section with the full rom package I used. Its on the first page at the mo.
Click to expand...
Click to collapse
Yeah, i've seen it. This one, right?
forum.xda-developers.com/showthread.php?t=1445635
alfax21 said:
Yeah, i've seen it. This one, right?
forum.xda-developers.com/showthread.php?t=1445635
Click to expand...
Click to collapse
Yeah that's the one, flash the full rom package. You may just have a corrupt .zip.
Alredy done two times, but the problem remains. Mmmh i don't think it's a corruption problem, i mean, i've tried to put the update in the phone from two PC.
Sent from my Nexus S using XDA App
Recovery: Known problem. Backlight stays off. Nothing you can do without unlocking your bootloader or rooting. Angle + lamp will show you what is on the screen.
Light Sensor: It's still buggy. With the phone locked, cover your hand over the light sensor (left of the ear piece while facing the phone). Hand still covering, unlock the phone. After a few seconds, remove your hand and face it under a light source. What i've noticed is it'll get brighter initially but refuse to darken again. Of course, you need to have Automatic brightness adjustment (just in case it isn't set to auto).
Unsure about your keyboard problem though, but it does like to stay open for longer than i'd like after going back to the home screen.
Harbb said:
Unsure about your keyboard problem though, but it does like to stay open for longer than i'd like after going back to the home screen.
Click to expand...
Click to collapse
Yeah, it remains open also after going back to the home screen, and it doesn't work. The only way is to crash it by going to the setting of the keyboard in the notifications.
alfax21 said:
Yeah, it remains open also after going back to the home screen, and it doesn't work. The only way is to crash it by going to the setting of the keyboard in the notifications.
Click to expand...
Click to collapse
Mine doesn't remain open though,. It just stays for say half a second, then animates away. Would be much more perfected if it went away while animating the previous window away, not a second later. I've not experienced the keyboard causing those kind of problems.
Might be wise to try SwiftKey or some other kind of keyboard alternative? That is easily enough to sway me away from stock.
Harbb said:
That is easily enough to sway me away from stock.
Click to expand...
Click to collapse
I agree. I'll wait for an Experimental Mod of CM9, then i'll root the phone.
Ok i'll make the thread as solved. I want to thanks Harbb for his help, i quote his post for those who will read this thread.
Harbb said:
Recovery: Known problem. Backlight stays off. Nothing you can do without unlocking your bootloader or rooting. Angle + lamp will show you what is on the screen.
Light Sensor: It's still buggy. With the phone locked, cover your hand over the light sensor (left of the ear piece while facing the phone). Hand still covering, unlock the phone. After a few seconds, remove your hand and face it under a light source. What i've noticed is it'll get brighter initially but refuse to darken again. Of course, you need to have Automatic brightness adjustment (just in case it isn't set to auto).
Click to expand...
Click to collapse
If you have problems (like the recovery one and the light sensor) with ICS 4.0.3, build IML74K, on your Nexus S i9023 there's nothing you can do, probably Google will fix it on his next update 4.0.5.
I'll just add that many custom ROMs allow light sensor manipulation. I hear there are great, working settings, its just the stock calibration that sucks. I've not tried this myself, but should be available in cm9, cna, etc.
..
Election Day said:
This is how I have my i9023 set up. These settings work very well, so feel free to use them.
Click to expand...
Click to collapse
Are these settings of the stock ROM?
..
twice now when I press my power button my phone won't turn on. it seems to happen randomly, i pull it out of my pocket and I can't get it to turn on. I end up having to hold the button for like 30 seconds? and then it hard-restarts and everything is back to working fine.
I'm using Cataclysm with Franco.kernel
Qi still beeps when i set my phone on it.
think this is a rom/kernel issue or hardware?
cataclysm + franco gets such amazing battery life :victory:
glitchhawk said:
twice now when I press my power button my phone won't turn on. it seems to happen randomly, i pull it out of my pocket and I can't get it to turn on. I end up having to hold the button for like 30 seconds? and then it hard-restarts and everything is back to working fine.
I'm using Cataclysm with Franco.kernel
Qi still beeps when i set my phone on it.
think this is a rom/kernel issue or hardware?
cataclysm + franco gets such amazing battery life :victory:
Click to expand...
Click to collapse
Im blaming it on the rom
markdapimp said:
Im blaming it on the rom
Click to expand...
Click to collapse
alright thanks.
markdapimp said:
Im blaming it on the rom
Click to expand...
Click to collapse
I don't know about that!! B/C I'm using the same ROM from day 1 no problems like that. I suggest flash another kernel see what happens:good:
I also had this problem about 3 or 4 times. I was always using stock kitkat and it happened with both stock kernel and franco kernel.
i swapped it up completely and am running KANGAKAT with elementX. we'll see what happens! thanks for the answers everybody.
Had the same issue. Called goggle to get RMA. It just arrived today. The sad part is this one is going right back because everytime I try to install a widget, the launcher crashes (stock launcher and 3rd party). I barely have any apps installed at this point. Looking like a faulty device. My original works fine besides the random instance of the screen not coming back on. Thought I was the only one since I started a topic about this a few weeks ago and got no replies. I'm 100% stock and unrooted
Sent from my Nexus 5 using Tapatalk
sitinon327 said:
Had the same issue. Called goggle to get RMA. It just arrived today. The sad part is this one is going right back because everytime I try to install a widget, the launcher crashes (stock launcher and 3rd party). I barely have any apps installed at this point. Looking like a faulty device. My original works fine besides the random instance of the screen not coming back on. Thought I was the only one since I started a topic about this a few weeks ago and got no replies. I'm 100% stock and unrooted
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This problem started with me after I installed the Franko Kernel.
Spent the whole night reverting to stock.
Not sure what I uninstalled, but my widgets are now working again. Still no idea what causes the screen to randomly not turn back on. Hoping this one doesn't have the same issue
Sent from my Nexus 5 using Tapatalk
My touchscreen randomly it seems becomes unresponsive. Power button will turn the phone off and on, volume works. Just no touch. I restart the phone and it's fine. I am running touchcontrol perhaps thats it? I turned it off for now, I'm just playing the waiting game. Just wanted to see if anyone else had similar experiences with the N5.
matthewordie said:
My touchscreen randomly it seems becomes unresponsive. Power button will turn the phone off and on, volume works. Just no touch. I restart the phone and it's fine. I am running touchcontrol perhaps thats it? I turned it off for now, I'm just playing the waiting game. Just wanted to see if anyone else had similar experiences with the N5.
Click to expand...
Click to collapse
started happening to me a couple of days ago i just told lg and they are going to repair it
matthewordie said:
My touchscreen randomly it seems becomes unresponsive. Power button will turn the phone off and on, volume works. Just no touch. I restart the phone and it's fine. I am running touchcontrol perhaps thats it? I turned it off for now, I'm just playing the waiting game. Just wanted to see if anyone else had similar experiences with the N5.
Click to expand...
Click to collapse
Are you rooted?
crocski said:
Are you rooted?
Click to expand...
Click to collapse
Yeah I am.
matthewordie said:
Yeah I am.
Click to expand...
Click to collapse
I dont know anything about rooting, Im just curious really. Have you tried a factory reset?
are you using a custom kernel with s2w/dt2w enabled?
if so, that's your culprit. disable it
Sent from my Nexus 5
notbrodie said:
are you using a custom kernel with s2w/dt2w enabled?
if so, that's your culprit. disable it
Sent from my Nexus 5
Click to expand...
Click to collapse
I'm not sure what kernel I'm using. I know it's as close to stock as possible. I disabled TouchControl and it hasn't had any issues since. I will look into those options you mentioned though as well just in case.
Is there a fix for the Sleep-of-death for CROMI-X 5.4. I am running that v8, GPU enabled, fsync off & no data2sd or rom2sd. I searched through the ROM thread, but the discussion about the SOD issue kinda petered out with no apparent closure.
Thanks.
mallard56 said:
Is there a fix for the Sleep-of-death for CROMI-X 5.4. I am running that v8, GPU enabled, fsync off & no data2sd or rom2sd. I searched through the ROM thread, but the discussion about the SOD issue kinda petered out with no apparent closure.
Thanks.
Click to expand...
Click to collapse
If you don't mind trying other than _that's kernel, I have something for you to test out....
LetMeKnow said:
If you don't mind trying other than _that's kernel, I have something for you to test out....
Click to expand...
Click to collapse
What do you suggest. I need some stability as I use this for business.
As far as I can tell, there isn't a solid solution because it is really hard to replicate the issue. I can go for a few weeks without any SODs, then SOD happens for a few days and just disappears after that.
mallard56 said:
What do you suggest. I need some stability as I use this for business.
Click to expand...
Click to collapse
It is very stable on my setup but it may be different on other users depending on how you are setting up your device. If you want to look for a solution, you may want to spend some time and test it out... I am not even sure if it is going to solve your SOD issue but I set it to kill any hang apps on the background so your device can response to your input or wake it up.
I am still running my modded 10.6.1.14.4 stock ROM with the latest version of my kernel, and I have never had a SOD since I installed the ROM, that must have been about a year ago. If you get a SOD, try to get a logcat and kernel log (dmesg).
_that said:
I am still running my modded 10.6.1.14.4 stock ROM with the latest version of my kernel, and I have never had a SOD since I installed the ROM, that must have been about a year ago. If you get a SOD, try to get a logcat and kernel log (dmesg).
Click to expand...
Click to collapse
I've never had a SOD either. I know it happens to TF300 users but not seen much of it on the TF700.
Log files after SOD
Not sure if I got these right; took logcat and dmesg from adb. I hope someone smarter than me can find something usefull in them
This SOD seems to be simply that the screen won't turn on. I get notification pings when mail is received, I can connect with adb and run commands, etc. Its just that the damn screen won't turn on.
Anyway, I appreciate what you all have done to make this a useable tablet.
mallard56 said:
This SOD seems to be simply that the screen won't turn on. I get notification pings when mail is received, I can connect with adb and run commands, etc. Its just that the damn screen won't turn on.
Click to expand...
Click to collapse
That's at least a good thing to know.
I don't find any obvious reasons for your problem in your logs, but next time it happens you could try to undock it and see if it makes any difference.
_that said:
That's at least a good thing to know.
I don't find any obvious reasons for your problem in your logs, but next time it happens you could try to undock it and see if it makes any difference.
Click to expand...
Click to collapse
Yeah, tried that; dock, undock, combination of key presses, etc. The only thing that works is to press and hold power for several long seconds until it reboots.
mallard56 said:
Yeah, tried that; dock, undock, combination of key presses, etc. The only thing that works is to press and hold power for several long seconds until it reboots.
Click to expand...
Click to collapse
I suspect it will eventually turn on. The log indicstes it registers your button press. It is not asleep.
Hi!
For past two-three days I am experiencing this problem. Touch sensor just randomly stops working. Top side of the screen is very very difficult to control, sometimes even impossible. Sometimes it feels like sensor recognizes multiple touches at the same time which results random pages or menus opening and closing.
After short usage with screen up or after long downtime (like when I go to sleep) I'm not able to use sensor at all. I cannot shut down the alarm clock, I cannot answer the calls. I still can use the power button tho.
Now what is the most retarded is that nearly all that vanishes after phone reboot. The only thing that remains is that top side of the screen is still quite difficult to control. For example I cannot open that top slide-bar comfortably. I have to slowly move my finger over the screen in order to do so.
Phone specifications:
Custom ROM: Cyanogen 11-20140702-nightly
sdcard partition type: FAT32
bootloader version: 2.14
Security-OFF
CID: 11111
Custom recovery: TWRP 2.7.0.8
P.S.: tried to re-insall ROM did not help. Phone havent been damaged by any means recently.
Did u over or under clock..flash a mod to control kernel? That's what it sounds like
I'm assuming you're using the stock kernel? What you're describing is an ongoing issue with the CM kernel, flash a custom kernel (Torched or Bubba) and your problem should cease.
Sent from my Evita
Wow. I never knew there was an issue with stock kernel...what's causing that anyways?
Damn it..
I'm a newbie with all that kernel flashes. Any How-To for noobs? Guide or something? I have found Tourched Kernel for KK thread (I suppose it stands for Kit-Kat?), but it's quite puzzling for me with all that voltages.
P.S.: What caused such random issue all of the sudden? Have been using CM for quite a bit of time already. Got that issue just 2-3 days ago
Look under Tims sig
marknoll said:
Wow. I never knew there was an issue with stock kernel...what's causing that anyways?
Click to expand...
Click to collapse
I have no idea what's causing it, I do know that using a custom kernel always fixes it for me though.
SoulSurvivors said:
Damn it..
I'm a newbie with all that kernel flashes. Any How-To for noobs? Guide or something? I have found Tourched Kernel for KK thread (I suppose it stands for Kit-Kat?), but it's quite puzzling for me with all that voltages.
P.S.: What caused such random issue all of the sudden? Have been using CM for quite a bit of time already. Got that issue just 2-3 days ago
Click to expand...
Click to collapse
Flashing a kernel is similar to flashing a ROM, if you want instructions just check the How-To Guide For Beginners thread in my signature.
Sent from my Evita
timmaaa said:
I have no idea what's causing it, I do know that using a custom kernel always fixes it for me though.
Flashing a kernel is similar to flashing a ROM, if you want instructions just check the How-To Guide For Beginners thread in my signature.
Sent from my Evita
Click to expand...
Click to collapse
Meh, I have updated kernel to 3.4.86-Torched-KK.B4.3+
Problem is still here.
Still cant open top slide menu properly. It is just weird, it really seems like some sort of damage to very top side of the screen. But i didnt hit it or anything like that. Screen itself without any visible damage or even scratches, cuz im using screen protector. Gonna see if I can at least answer the calls properly without sensor goin full nuts.
update:
That's definitely a software issue. If i turn the phone around so screen would get rotated that "damaged" area works just fine. What the **** is going on? It started so randomly
You can try flashing a different ROM, or rolling back to the last build of CM that you remember being ok.
Sent from my Evita
SoulSurvivors said:
Meh, I have updated kernel to 3.4.86-Torched-KK.B4.3+
Problem is still here.
Still cant open top slide menu properly. It is just weird, it really seems like some sort of damage to very top side of the screen. But i didnt hit it or anything like that. Screen itself without any visible damage or even scratches, cuz im using screen protector. Gonna see if I can at least answer the calls properly without sensor goin full nuts.
update:
That's definitely a software issue. If i turn the phone around so screen would get rotated that "damaged" area works just fine. What the **** is going on? It started so randomly
Click to expand...
Click to collapse
Maybe reflashing the ROM and the kernel would be a good idea. I've had to do that too. Its annoying,but sometimes I had to do that. Good luck.
Nop..
I've done the factory reset. Installer fresh ROM, Gapps and kernel.
Same ****. I Guess That is indeed hardware damage to sensor.
/sadpanda
There's a way to diagnose it. Download an app called sensor on play store