I sometimes have issues with my screen going black when I hit the power button coming from sleep mode. I keep having to reboot, and that sucks. I'm not sure what causes this and past experience tells me not to change anything unless I know what the problem is, and exactly how to fix it. What sucks even more than having to reboot often is having to reflash everything and spend an 2 hours setting it back up.
I added this line----> ro.HOME_APP_ADJ=1 to the build.prop, but I'm not sure this is even responsible for the problem. Is there something else I need to know about?
Is that going to fix the issue permanently or is there something else altogether that I have to tweak?
I have the Pacman ROM, and the Next 3D launcher. I also have the ROM Toolbox and Android Tuner. Are there settings in either one of those tools that will fix this black screen delay/freeze thing coming from sleep mode?
TheEvoNoob said:
I sometimes have issues with my screen going black when I hit the power button coming from sleep mode. I keep having to reboot, and that sucks. I'm not sure what causes this and past experience tells me not to change anything unless I know what the problem is, and exactly how to fix it. What sucks even more than having to reboot often is having to reflash everything and spend an 2 hours setting it back up.
I added this line----> ro.HOME_APP_ADJ=1 to the build.prop, but I'm not sure this is even responsible for the problem. Is there something else I need to know about?
Is that going to fix the issue permanently or is there something else altogether that I have to tweak?
I have the Pacman ROM, and the Next 3D launcher. I also have the ROM Toolbox and Android Tuner. Are there settings in either one of those tools that will fix this black screen delay/freeze thing coming from sleep mode?
Click to expand...
Click to collapse
Try upping your Clock speed to Min/384 and see if that kinda helps a bit.
Related
k i read about an app called spare parts on here so i figured hey i'll try it out. i did saw what extra setting were there and decided i wasn't gonna use it didn't even change any settings.
after opening the app and then pressing home something wierd happened i saw a white screen with HTC in green in the center for about 3-5 seconds my backround with a loading pop-up and nothing else for about another 3-5 seconds. this is happening every time i press the home button or exit out of an app. it's getting infuriating, i'm also getting wicked bad lagg in sense and lot's of hang up's and force closes. also wicked bad battery life. i don't know what to do to fix it.
i have the OTA and rooted last night with unrevoked method, this morning is when i tried the app around 10 or 11 not sure last couple days is a blur.
can anyone help, how can i restore what i had previously, do i have to do a full wipe.
nobody...... anyone plz, it is cripling my evo
thorpe24 said:
k i read about an app called spare parts on here so i figured hey i'll try it out. i did saw what extra setting were there and decided i wasn't gonna use it didn't even change any settings.
after opening the app and then pressing home something wierd happened i saw a white screen with HTC in green in the center for about 3-5 seconds my backround with a loading pop-up and nothing else for about another 3-5 seconds. this is happening every time i press the home button or exit out of an app. it's getting infuriating, i'm also getting wicked bad lagg in sense and lot's of hang up's and force closes. also wicked bad battery life. i don't know what to do to fix it.
i have the OTA and rooted last night with unrevoked method, this morning is when i tried the app around 10 or 11 not sure last couple days is a blur.
can anyone help, how can i restore what i had previously, do i have to do a full wipe.
Click to expand...
Click to collapse
get used to it if you intend to use sense, the screen you speak of is sort of like the htc sense/rosie intro. If you dont like it you can go vanilla and use another launcher, like adw froyo,launcherpro, or even the extra launcher thats included....
Sounds like you enabled aggressive handling of apps. Can you get in there to turn it off?
jmxp69 said:
Sounds like you enabled aggressive handling of apps. Can you get in there to turn it off?
Click to expand...
Click to collapse
Or just do a factory reset.
also, you are experiencing some isolated problems which leads me to beleive the issue is software related rather than hardware.I have experienced NOT ONE of the issues you speak of. Make sure you update prl. I can vouch for that one. My data was 90% broken till i did. Also try and wipe data, that would prolly fix everything as well.....FYI, i cannot gurantee the problem lies with your hardware OR software. Thats just my diagnosis. Good luck
Thats what it was the agressive handling of processes thanks alot guys feel like a fool.....
Sent from my PC36100 using Tapatalk
thorpe24 said:
Thats what it was the agressive handling of processes thanks alot guys feel like a fool.....
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Heh...I did that once on my hero. I know the feeling.
some versions of spare parts come with a launcher. the problem is that when you press the home button now, it's trying to goof with /system, which is forcing the reboot. even though you may be rooted, you don't have rw privileges in /system while messing with android.
you may be able to get away with accessing /system and erasing your goofy installed spare parts app. you'll have to do that through adb shell, and the custom recovery. do a search for 'remove apps', you should find it easily enough. i think the thread was moved from dev to general, or q and a.
anything that will call a write to /system (i.e. a rooted app that needs access to it to work right) has the potential to cause the phone to reboot. when i installed adfree, it had the same effect. trying to install hosts (which write to /system/etc) caused a reboot. i had to install hosts through recovery with a push after remount.
hope that helps
Hmm I installed autokiller and it appears to work doesn't mess with anything that is
I really dunno a way of testing that its actually working though if you where looking for a way to manage memory
I was using a task killer but read up on stuff and turned it off just keeping it in case I need it for something that wont close and the phone is running great and battery life keeps getting better and better.
Sent from my PC36100 using Tapatalk
autokiller
People you need to be careful with autokillers!
Make sure that you are not closing down sense items.
Put anything that says htc or sense on ignore.
If not you are shutting down parts of sense. Then sense has to reboot. Witch is why you see the white screen with the htc logo in the middle.
Sense wigdets and short cuts are mis shaped and crooked on rooted stock rom.
I suspect it has something to do with sense tring to go to landscape every once in awhile.
Any ideas how to fix?
Sent from my PC36100 using XDA App
It stays that way through a reboot?
Also, screenshot?
on the second reboot it went back to normal. weird that it happened and also weird that the second reboot seemed to fix the symptom.
well i am having this issue again and i googled this and i found my own thread at the top of the list.
i cant be the only fool with this issue, it has done to me 10 more times since i first posted this. so it doesn't happen often and a reboot normally clears this
i think this symptom is caused by sense trying to go to landscape mode and somehow getting stopped in the process
i would assume that i might be able to disable sense home screen and re enable it may take care of this.
the only way i can think of doing this might be to change home screen to something else and then set sense to be default home screen, might be faster than rebooting, i just tried this and it doesnt work.
awesome
potna said:
well i am having this issue again and i googled this and i found my own thread at the top of the list.
i cant be the only fool with this issue, it has done to me 10 more times since i first posted this. so it doesn't happen often and a reboot normally clears this
i think this symptom is caused by sense trying to go to landscape mode and somehow getting stopped in the process
i would assume that i might be able to disable sense home screen and re enable it may take care of this.
the only way i can think of doing this might be to change home screen to something else and then set sense to be default home screen, might be faster than rebooting, i just tried this and it doesnt work.
awesome
Click to expand...
Click to collapse
That's weird, I've never seen my Widgets or shortcuts do that before. And the Evo's stock version of sense doesn't rotate to landscape, so I'm not sure why it would attempt to. Could you use drocap2 or Shootme to get a screen shot of this? I would suggest doing a full wipe and then reflash a rom to fix it. That should take care of it
Sent from my PC36100 using XDA App
I was wondering if any has encountered this.
1) After a reboot and when I'm on my main screen, it would take a while for it to load the launcher. If I attempt to scroll with Nova, it would say its unresponsive, and if i wait, it would work.
I recall on stock ICS, after reboot, i'd unlock screen and pretty much immediately i can use the main screens.
2) Sometimes when I try to unlock the screen it would freeze up. The screen remains blank, but the capacitive buttons light up.
I can reboot to enter the phone.
I can wait it out and it would eventually load and say something is unresponsive, sometimes the launcher. And if i wait, it would work again.
Or I can increase min cpu to 486 instead of 384hz, and i dont see this problem. Can someone explain to me whats happeneing? Why would 384Hz create Sleep of death?
Any insights would be helpful. I would like to get rid of the sod or lock screen freezing thing without having to mess with my cpu settings.
And resolve the lag issue at during reboot. it would take like 10 plus seconds for it to be responsive. I'm not saying 10 seconds is long, but the point is that i never had this issue with stock TW.
I am rooted on paranoid android/CM10 latest build. with SuperchargerV6.
Thanks in advance guys.
bump
anyone?
mikoal said:
bump
anyone?
Click to expand...
Click to collapse
try dirty flashing the rom. that usually clears up issues in cm10-based roms. make a nandroid if you havent already. cheers
I was just wondering if this happens to anyone else. So sometimes I go to unlock and the screen doesn't let me do anything, it happens not just when unlocking but when I'm using the phone too, it's really annoying when I'm trying to text someone back or try to answer a call. It doesn't happen all the time so I could live with it....but I'm wondering if anyone has a fix or has the same problem.
Also I have my phone rooted and g3 tweaksbox, and I turned off the knock in code..I don't know if any of these have factors.
WendyB87 said:
I was just wondering if this happens to anyone else. So sometimes I go to unlock and the screen doesn't let me do anything, it happens not just when unlocking but when I'm using the phone too, it's really annoying when I'm trying to text someone back or try to answer a call. It doesn't happen all the time so I could live with it....but I'm wondering if anyone has a fix or has the same problem.
Also I have my phone rooted and g3 tweaksbox, and I turned off the knock in code..I don't know if any of these have factors.
Click to expand...
Click to collapse
Is it lag? Does it only happen for a few seconds before it starts again?
It's not lag..I don't think unless it's a really long lag ?... I turn my screen on and off and it would still be frozen. Maybe after a few mins of turning the screen off and on again it will work...
WendyB87 said:
It's not lag..I don't think unless it's a really long lag ?... I turn my screen on and off and it would still be frozen. Maybe after a few mind not turning the screen off and on again it will work...
Click to expand...
Click to collapse
Sounds faulty i think.I'd get the phone freezing for a few seconds before it responded, but that was lag.
Aww man that would suck if it was... That's the only problem I have!
WendyB87 said:
Aww man that would suck if it was... That's the only problem I have!
Click to expand...
Click to collapse
i had this problem..it would lock up..freeze and i had to wait for a min or so to come back to life..a hard reset fixed it
Oh okay! That is good to know...I guess I'll be trying that soon
I have the same issue as well.
It's not that the screen "stopped" working. It works, except there's no update on the screen. As if the entire phone is frozen, but it's still giving me haptic feedbacks. Except, actions aren't being reflected on the UI; things like, tapping home navbar button, doesn't take me to the launcher, tapping up/back doesn't take me to the previous screen. I can lock/unlock the phone, but I'd return to the whatever page of the app that corresponds to the back/up command I previously made.
I think, the easiest way I can summarize this is that the OS stopped doing visual updates, while there's actually stuff going on despite that "stuck" screen.
sometimes when i pick up my phone and press the power button to turn it on,i find the screen is black and i can t do anything but press power and vol + to reboot.
then the phone works fine again but of course this is quite annoying to happen and it happens maybe one or two times daily
it started happening when i upgraded to 5.1.1.
in 5.0 and 4.4 phone behaved fine.
how to find what causes screen to turn black when i try to turn it on?
does somebody faced this also?
any helpful idea?
broky said:
sometimes when i pick up my phone and press the power button to turn it on,i find the screen is black and i can t do anything but press power and vol + to reboot.
then the phone works fine again but of course this is quite annoying to happen and it happens maybe one or two times daily
it started happening when i upgraded to 5.1.1.
in 5.0 and 4.4 phone behaved fine.
how to find what causes screen to turn black when i try to turn it on?
does somebody faced this also?
any helpful idea?
Click to expand...
Click to collapse
Phone stock? Rooted? Recovery? Etc... I've never experienced it, but with modded phones, cache wipe fixes these types of things often
levone1 said:
Phone stock? Rooted? Recovery? Etc... I've never experienced it, but with modded phones, cache wipe fixes these types of things often
Click to expand...
Click to collapse
sorry,did not mention.
locked bootloader,stock 5.1.1 rom rooted and recovery,xposed installed.
i need a way to track what causes this situation,maybe an adb command?
broky said:
sorry,did not mention.
locked bootloader,stock 5.1.1 rom rooted and recovery,xposed installed.
i need a way to track what causes this situation,maybe an adb command?
Click to expand...
Click to collapse
I don't know much in that realm, but I read this one time - http://forum.xda-developers.com/showthread.php?p=34960691 - looks interesting if you know what you're doing. Anyway, all I really had to offer is attempting a cache wipe, which you probably tried. Besides that, if it happens consistently, you could experiment with disabling Xposed modules one at a time, for a day or so, and see if that reveals it. I have gotten black screen before from installing incompatible modules before, but it would just boot to the black screen. I haven't had it happen only occasionally like that. My guess would definitely be somewhere with Xposed. Maybe something clashing with built-in settings, ( I don't remember what it's called, but there's something that senses when yo pick up the phone, and it wakes up automatically - that kind of thing).
levone1 said:
I don't know much in that realm, but I read this one time - http://forum.xda-developers.com/showthread.php?p=34960691 - looks interesting if you know what you're doing. Anyway, all I really had to offer is attempting a cache wipe, which you probably tried. Besides that, if it happens consistently, you could experiment with disabling Xposed modules one at a time, for a day or so, and see if that reveals it. I have gotten black screen before from installing incompatible modules before, but it would just boot to the black screen. I haven't had it happen only occasionally like that. My guess would definitely be somewhere with Xposed. Maybe something clashing with built-in settings, ( I don't remember what it's called, but there's something that senses when yo pick up the phone, and it wakes up automatically - that kind of thing).
Click to expand...
Click to collapse
thanks mate i m working on it and i ll repopt back if i solve it and how or need more help
SOLVED:after a lot of testing found out that my problem was xposed framework v74-sdk22.
from the moment i installed xposeeed v75-sdk22 everything works as it should,not a single reboot and phone is rebooting faster also and no lag as i used to have before,fingers crossed it won t show up again:good: