Related
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.
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.
Has anyone experienced your U11+ freezing up.
It has happened to me about 3 times.
It generally happens over night while it's charging. I get up one of those mornings and the green light is on, remove the charging cable and I can't wake up the phone. I can't even turn off the phone by pressing and holding the power button to kill the device. The only way is to put it into download mode by simultaneously holding down the vol down key and power key, and then when the menu comes up to select the reboot option to get the phone back to normal.
Has anyone else experienced this or know what could be causing this to happen?
The problem is that I use my phone as my alarm clock, and when it freezes up, my alarm doesn't work.
Any suggestions anyone?
No problem like that until now.
However, noticed sometimes that the my alarm, which is setup for vibration only, only vibrates once and then continues silently alarming until I turn it off.
Happens randomly but still strange. I've to try with another clock app.
That's really odd.
I'm going to turn off the always - on feature and see if I get anymore freezes. I had another one this afternoon.
I'll report back after some time and let you know if there has been no more freezes.
I'm just updating to the latest update 1.23.709.3 and see also how it performs.
I'm a bit concerned about this random freezing that I have experienced since I got this device.
If it persists I may ask for a new one.
globalgpj said:
I'm just updating to the latest update 1.23.709.3 and see also how it performs.
I'm a bit concerned about this random freezing that I have experienced since I got this device.
If it persists I may ask for a new one.
Click to expand...
Click to collapse
I'm still on the October security patch so I'm expecting one for the December period soon I hope.
In regards to your freezes I've not encountered anything like that so far been working flawlessly so far if there is anything I can test let me know
I have the Taiwan version.
If you could try the always-on feature for a couple of days and nights and report back, that would be awesome. However, I selected the option, for always-on to only come on when I moved the phone. (good for night time use especially)
I had my phone in the pocket yesterday afternoon and it froze.
As I stated earlier, I can only restart the phone only by putting it into download mode and reboot from there.
globalgpj said:
I have the Taiwan version.
If you could try the always-on feature for a couple of days and nights and report back, that would be awesome. However, I selected the option, for always-on to only come on when I moved the phone. (good for night time use especially)
I had my phone in the pocket yesterday afternoon and it froze.
As I stated earlier, I can only restart the phone only by putting it into download mode and reboot from there.
Click to expand...
Click to collapse
I have been using the AOD since I got the phone yesterday. Not a single freeze
Galactus said:
I have been using the AOD since I got the phone yesterday. Not a single freeze
Click to expand...
Click to collapse
Thanks for letting me know.
I guess I can rule that feature out as a probable cause.
It must be some other app that's causing this issue. But it's a pain to go through the process of finding out which one.
globalgpj said:
Thanks for letting me know.
I guess I can rule that feature out as a probable cause.
It must be some other app that's causing this issue. But it's a pain to go through the process of finding out which one.
Click to expand...
Click to collapse
Yeah trial and error isn't fun. I'd probably factory reset though and see if it happens with barely any third party apps installed.
globalgpj said:
I have the Taiwan version.
If you could try the always-on feature for a couple of days and nights and report back, that would be awesome. However, I selected the option, for always-on to only come on when I moved the phone. (good for night time use especially)
I had my phone in the pocket yesterday afternoon and it froze.
As I stated earlier, I can only restart the phone only by putting it into download mode and reboot from there.
Click to expand...
Click to collapse
I have the HK model I think and I had the AOD when I first got it, set to motion and nothing has happened to my phone in regards to freezing fingers crossed. I have disabled it for the moment as I noticed a greater battery usage overall, I believe between 9-10% overnight and only 2% when I had it disabled.
Hopefully you find the problem otherwise see if you can get it replaced...
Since not using the always-on feature, I don't have any more freezes. Must be some conflict with the alarms and always-on. Can't see what else could be causing those freeze ups.
My phone surprisingly just froze up yesterday. But at least it's been a long while since not having the always-on feature enabled. With always-on enabled, it seems to have happened every day.
The issue I have most about this, is missing that important call when I haven't realised that the phone is frozen, because sometimes I don't pick up the phone for hours.
I had to do a complete fresh install from scratch and I have no more issues. I believe all my issues came from using HTC's transfer tool when going from u11 to u11+. Importing all the settings features using the Transfer Tool has caused issues. I'll never use this tool again.
All good now.
Hi all!
I've been searching for a solution for some time but couldn't find any.
Always On Display stopped working on my Pixel 6a. It's all turned on in the settings but it simply doesn't work. It works only in those cases:
1. When device is rebooted into an Airplane mode
2. When device is rebooted into the Safe Mode
3. When device is rebooted but not unlocked for the first time
There are also no notifications displayed so screen wake on notification doesn't work. Same story as above.
I thought there is some app blocking it but couldn't really figure out which, I tried to disable many of them but none helped.
I did a factory reset once but issue came back after few days.
I seriously have no idea what might it be. Hope someone here might have had similar problem and found a solution.
Thanks!
Czarls said:
Hi all!
I've been searching for a solution for some time but couldn't find any.
Always On Display stopped working on my Pixel 6a. It's all turned on in the settings but it simply doesn't work. It works only in those cases:
1. When device is rebooted into an Airplane mode
2. When device is rebooted into the Safe Mode
3. When device is rebooted but not unlocked for the first time
There are also no notifications displayed so screen wake on notification doesn't work. Same story as above.
I thought there is some app blocking it but couldn't really figure out which, I tried to disable many of them but none helped.
I did a factory reset once but issue came back after few days.
I seriously have no idea what might it be. Hope someone here might have had similar problem and found a solution.
Thanks!
Click to expand...
Click to collapse
Would you be down to try flashing a custom ROM?
I've read in another thread not long ago someone saying their Tap to Wake randomly stopped working. We narrowed it down to an issue with the proximity sensor (so the phone thought it was in a pocket/covered, therefore didn't let Tap to Wake work, he had to use the power button to turn the screen on). He then flashed a custom ROM (it was LOS, I think), and that solved the issue for him.
I've also had some issues with the stock ROM, flashing a non-factory one solved all of them
If you want to keep on using the factory ROM, you might wanna try using the Android Flash Tool instead of just factory resetting to make sure no corrupted settings can live on.
Lada333 said:
Would you be down to try flashing a custom ROM?
I've read in another thread not long ago someone saying their Tap to Wake randomly stopped working. We narrowed it down to an issue with the proximity sensor (so the phone thought it was in a pocket/covered, therefore didn't let Tap to Wake work, he had to use the power button to turn the screen on). He then flashed a custom ROM (it was LOS, I think), and that solved the issue for him.
I've also had some issues with the stock ROM, flashing a non-factory one solved all of them
If you want to keep on using the factory ROM, you might wanna try using the Android Flash Tool instead of just factory resetting to make sure no corrupted settings can live on.
Click to expand...
Click to collapse
I would say it does not have anything in common with the proximity sensor since it works fine with airplane mode turned on. I want to stay with the factory ROM. Maybe it's an issue that will be fixed any time soon?
Czarls said:
I would say it does not have anything in common with the proximity sensor since it works fine with airplane mode turned on. I want to stay with the factory ROM. Maybe it's an issue that will be fixed any time soon?
Click to expand...
Click to collapse
Why do you ask for advice if you just want to "wait for it to get fixed"?
If you've done a factory reset already, it's not a hassle re-flashing the factory ROM (since you already have your data backed up).
Fwiw, the guy with the proximity sensor issue also had it sometimes work and other times not, much like your issue
Lada333 said:
Why do you ask for advice if you just want to "wait for it to get fixed"?
If you've done a factory reset already, it's not a hassle re-flashing the factory ROM (since you already have your data backed up).
Fwiw, the guy with the proximity sensor issue also had it sometimes work and other times not, much like your issue
Click to expand...
Click to collapse
I'm trying to figure out if it's a software issue in a ROM or some applications impact..