Hi all
I've done something stupid to my phone.
Been fiddling with auto-brightness settings, and now the screen won't switch on.
Got CyanogenMod 7.1 stable for the HTC Desire HD, had it loaded for close to a month(been enjoying it).
I've rebooted, pulled battery, SD card, SIM, everything. On boot the display shows the HTC logo, and the CyanogenMod BootScreen, immediately after that, I see the screen off animation, where it would normally go to homescreen. I know the phone is still on, the notification light is flashing, and via USB I can get screenshots of my lockscreen(widgetlocker).
When I click the power button a few times, intervals of ~3 seconds, the screen flashes just quick enough to see my lockscreen, but it really is a split second flash.
I've got Juice Defender Beta, I think the latest, used it for a couple weeks. Today I wanted to test the auto brightness settings it "supports"(beta feature). I noticed no changes, so I skipped over to the custom display settings for cyanogenmod, under Settings/Cyanogen .../display/Auto Brightness.
I fiddled there, as I've so done before, couldn't find the right balance , so I left my phone for a bit, it clicked the screen off, now screen is 'stuck' off.
I understand that this may be Juice Defender's doing, but since I was fiddling with cyanogen settings too, I'm posting here and to JD support, just in case. There might be a conflict.
Anyone know how I would debug this through ADB? I would really like to disable auto-brightness, that would probably eliminate Cyanogen from causing this (as the settings I changed related to Auto-Bright).
I tried this, no luck.
Otherwise, how to reset Juice Defender settings via ADB, or through a USB screenview... thing?
I've got a NANDroid backup, but its a little dusty, I've done a lot of customisation and such since, I'd prefer to avoid using it.
This is, of course, urgent. I can't use my phone at all, so any help is greatly appreciated.
EDIT: Solved it. Booted into safe mode, disabled what I changed, sorted. Still no idea what caused it, but ja, I fixed it. Android has a safe mode? Good to know...
Related
Hi guys!
I noticed over quite a time, that while I leave my phone charging over the night, any random notofication will cause the screen to stay on until I wake up and manually turn it off.
On my galaxy s2 I have VillainRom 2.1.0 (Android 2.3.4) with ninpho's 2.0.4 kernel.
However I did notice the problem before with VR 1.4 and CF-Root kernel (didn't use anything else yet), so I figure it might not be related to this.
This is rather annoying, as I don't want any burn in effects on my screen, but there's a much worse part about it:
It's noch 100% limited to the time of being charged. If I remove the charger at 100%, play around a little with the phone and then go to sleep, some random notification (whatsapp/sms etc.) will still cause the phone to wake up and not go back to sleep mode.
What happens is, I wake up with a phone at 50% battery (at it's best!), or I don't even wake up because my phone is dead and therefore my alarm clock stays quiet..
I read about some people having this problem with their SGS1 and it might help to go to Settings -> Applications -> Development -> uncheck Stay awake.
SGS2 does not have this "stay awake" option (or I'm seriously stupid)..
Anyone an idea what I might want to try?
Best greetings, Alex
At that screen I have "Standby" and you need to have it unchecked. Also, what's your screen-off delay? You don't have any apps like screebl keeping you screen on, I assume?
prodygee said:
At that screen I have "Standby" and you need to have it unchecked. Also, what's your screen-off delay? You don't have any apps like screebl keeping you screen on, I assume?
Click to expand...
Click to collapse
I do not have this option. my screens stays on all the time.
You're problem sounds similar to mine.
http://forum.xda-developers.com/showthread.php?t=1224117
I have tested with a stock rom of which I made no input and had the same issue.
Hope we can solve our problems. Cheers
cjackway said:
You're problem sounds similar to mine.
http://forum.xda-developers.com/showthread.php?t=1224117
I have tested with a stock rom of which I made no input and had the same issue.
Hope we can solve our problems. Cheers
Click to expand...
Click to collapse
mine just started doing it. i have been running custom rom for awhile now.
apps recently installed:
words free
launcher pro 806
extended controls
impossible level game
I have uninstalled:
words free
impossible level game
my issue is still happening.
when unplugged screen turns off.
I can get a text, it will light up then turn back off.
when plugged in (charging)
display will not turn off unless i press the lock button.
if i get a text the screen turns back on and stays on unless i press the lock button again.
I have recently re-flashed, complete wipe of phone and factory reset wipe.
I still have the screen on when charging and no option to disable.
I need an option to disable the "stay awake"
As my fault occurs with the phone completely reset on a stock rom it must be hardware so I am going to return it and see what happens from there.
I have flashed CM7 and there is an option to turn stay awake off.
This option is removed in DarkyRom.
Finally figured out how to turn it on or off!!!!
install the app extended controls and add stake awake as a toggle.
Turn it off!!!
then remove app
FINALLY!
Hello guys, I just noticed strange bug/behaviour. If my battery is around 10%, touch screen is not respondig as it should (also touch buttons). I have to tap like 10 times on some tile to open it and then tap another 10 times on back button or home button to jump of from app. As soon as I connected the charger, phone is behave normal, like new
Does somebody else notice the same behaviour or its just me?
P.S. Tried to reboot phone twice. Battery saver was off.
p1ceus said:
Hello guys, I just noticed strange bug/behaviour. If my battery is around 10%, touch screen is not respondig as it should (also touch buttons). I have to tap like 10 times on some tile to open it and then tap another 10 times on back button or home button to jump of from app. As soon as I connected the charger, phone is behave normal, like new
Does somebody else notice the same behaviour or its just me?
P.S. Tried to reboot phone twice. Battery saver was off.
Click to expand...
Click to collapse
Can you check under settings -> applications -> Background tasks?
It more looks like plenty of apps are trying to sync up or use the resources. I might be wrong, but this did happen to me even at about 55% battery. But not as bad as 10 taps. I just felt the app launching was a lil slower than normal when I had ample background tasks.
Didn't know about "Background tasks", thanks
Currently I have only "HTC Hub" there. I will go and check this setting next time when I occur this problem.
But anyway, shouldn't reboot kill all background apps?
p1ceus said:
Didn't know about "Background tasks", thanks
Currently I have only "HTC Hub" there. I will go and check this setting next time when I occur this problem.
But anyway, shouldn't reboot kill all background apps?
Click to expand...
Click to collapse
Reboot surely will kill all background apps. But these background apps are different to other OS. They are those that will 'start on boot'. So after reboot just in few seconds, they will get to their business as usual.
I love this 'background' task feature! No other OS does it so efficiently as Windows.
The good thing is if you check that place often, you will know what apps are 'going to run'. It doesn't mean they are running all the time. It tends to indicate the capability of them to run.
So as you said you just have HTC Hub, which is same on mine. However, when you to go 'advanced' option on that same page, you will see a list of greyed out apps that are going to run in background and you can't kill them. Reason being these apps need to be told about not running in background by entering them individually.
See if that greyed out list has some huge apps. I downloaded this gMaps thing from market and although I just looked for maps once (a day ago) since then, it's been running. It's because it kept on looking for my GPS co-ordinates. Now that dint freeze my phone (1.5 Ghz, I know!) but it drained battery quicker. Changing attributes within the app, removed it from greyed list and happy days!
In a nutshell, very intelligent task management. You can choose what can run and can't run while your screen is off! + you get benefit of battery saver option if you use that so you can choose who can connect to 3g network and who can't while you are not looking at your screen!
PS: whole point of that long post was : Most likely it's not a background task that's hogging your processor, but it's worth looking under advanced and you might know what app was it.
Hey, that was a long post Thanks for clarifying. I just checked Advanced tab and there are only HTC hub and some Media something (I have it in Czech so don't know the exact name in english)
Anyway I will keep my eye on that menu and in case of any issue I will check it and we will see
OK guys, here is the update. It's still happening :/ Everytime battery drops under 10% phone cannot be almost used. I have to tap everything 10 times to get it done. Checking background task was not helpfull, only HTC Hub is running (even if I kill it its the same).
So...I don't know...maybe its a bug (some power-saving feature thats is not configured properly?). I was used to behaviour when my mobile works even with no battery left like fully charged. No change in behaviour...
p1ceus said:
OK guys, here is the update. It's still happening :/ Everytime battery drops under 10% phone cannot be almost used. I have to tap everything 10 times to get it done. Checking background task was not helpfull, only HTC Hub is running (even if I kill it its the same).
So...I don't know...maybe its a bug (some power-saving feature thats is not configured properly?). I was used to behaviour when my mobile works even with no battery left like fully charged. No change in behaviour...
Click to expand...
Click to collapse
As a last resort - try a hard reset. I've got many issues fixed that way.
However, can I ask how closer to the release did you get this phone? Here in the UK there seems to be two separate batches dispatched. One which was at the release - which is buggy batch. I got my new phone sorted from someone I knew at the store and so far not a single problem from the earlier handset is seen. Battery is drastically better too (it was better on earlier one already, but this is very pleasing!)
Try hard reset, if that doesn't solve it, I would recommend to swap it if you can.
Hello everyone,
I am facing the exact same issue on my HTC Titan - when battery is low (battery saver turns on), touchscreen becomes unresponsive. This is very annoying since it usually happens when i get an incoming call and i cannot answer it.
Did anybody try hard-resetting the phone in order to solve this issue?
Thanks for the answers!
Regards
Hello there... I have the same problems too. I don't try to do hard rest for my titan. It is very annoying for me. Also some time my touchscreen becomes unresponsive even the battery charging is more than 50%...
Yeah, I get this issue too, it makes the phone unusable until you get to a charger. I find that it comes in stages, it sometimes is really bad then works for a few seconds, then stops again.
I have checked all my background tasks and nothing is really running.
I have this issue too. I got this phone only yesterday, and when my battery reached 10%, touchscreen became unresponsible.
Guys I think I've mentioned this in the FAQs thread, but ..
Everyone with this issue - please tick the box under battery saver, where it says 'automatically start.... '
If you phone goes below 25% without battery saver ON, it will lag/freeze - the screen response.
However with battery saver on, you will be able to use it till you go below 5% or even 3% when it gives you the 'critical battery' warning.
This is HTC screwing with us!
mine has the completely opposite problem!! when the phone is charging, the screen becomes very unusable, in ex. i press the phone tile, the screen registers my tap, but it understands that i pressed the tile below or next to the one i really pressed. or i happen to scroll down or up, the phone hesitates for a second and then scrolls but it is very jumpy and jittery, unlike normal use. some times it doesn't even register my taps 2 or maybe 3 times in a row!!
the only workaround i've found is not to use the phone when charging
is this happening because of a faulty charger, maybe the phone is experiencing a short circuiting situation??
(i forgot to mention that i have the phone only for a week!!)
thanks
drupad2drupad said:
Guys I think I've mentioned this in the FAQs thread, but ..
Everyone with this issue - please tick the box under battery saver, where it says 'automatically start.... '
If you phone goes below 25% without battery saver ON, it will lag/freeze - the screen response.
However with battery saver on, you will be able to use it till you go below 5% or even 3% when it gives you the 'critical battery' warning.
This is HTC screwing with us!
Click to expand...
Click to collapse
I have battery saver enabled and even with the heart icon in the info bar at the top, the screen is still unresponsive.
Same here! i thought it was just my device that was dead or something, even since it's only 2 months old!
I did a hard reset and it solved the problem, it must have been something messing it up.
Nope...I have tried Hard Rests...ROM Changes etc...but its still the same problem..
Does anyone here think its a hardware problem ? or something else?
Any geek suggestion would be helpful
Send it back to htc, let them repair it?
Sent from my HTC using Board Express
Hi, I also have a problem with non-responsive screens but only in specific areas and doesn't have to be 10% percent or lower.
Ex: It happens only when the keyboard is up and the buttons on the bottom are very difficult to press!
I'll provide pictures soon
------------
Phone: HTC Titan X310e
Custom rom: Dynamics 2.0b full unlock 7.10.8862 (ultrashot)
p1ceus said:
Hello guys, I just noticed strange bug/behaviour. If my battery is around 10%, touch screen is not respondig as it should (also touch buttons). I have to tap like 10 times on some tile to open it and then tap another 10 times on back button or home button to jump of from app. As soon as I connected the charger, phone is behave normal, like new
Does somebody else notice the same behaviour or its just me?
P.S. Tried to reboot phone twice. Battery saver was off.
Click to expand...
Click to collapse
That happened to me today. Then I did a hard reset and now my phone won't go past the carrier logo (the one after the HTC logo, and before the windows Phone logo)
Hi everyone !
I'm new here (and not a native english speaker, so apologies in advance for any grammar mistakes)
Before making this thread, I looked for info here, but I'm not sure for what to search.
I'll try to explain my problem here.
I bought a Galaxy SIII from my provider 3 weeks ago and everything looked fine, till last week.
Some times to time, with no apparent reason or cause, while my phone is on sleep mode, on my desk, or in my pocket, playing music, I have the following problem: when I push the on/off button to wake up my phone, my screen is turning on, taking me to the lock screen.
But, my screen brightness is very low, like set to the minimum.
And when I draw my unlocking pattern, screen goes black.
Bottom buttons are lit and my phone seems to be OK, I can feel haptic feedbacks.
But the screen is black.
If I push the on/off button again, screen stays black and bottom buttons are not lit anymore, as a usual Sleep Mode.
If I push on/off again (depending on how much I wait between 2 on/off):
- My phone awakes from Sleep and takes me again to the unlock screen, brightness still very low. And after the unlocking pattern traced, black screen again
- If I didn't wait enought after putting it into sleep mode, in this case, I don't have to redraw the unlocking pattern. I'm back to my home screen...
for 1/4 of a second, stilll with brightness at the minimum. And screen goes black.
And after a serie on onoffonoff, boom, my screen is back to full and normal brightness and everything is OK.
At the beginning, my phone did that once in a while. I thought at the time ti was after pushing the on/off button while using a CPU/RAM hungry app, my phone struggling to recover....
But now, it's totally random.
Depending on .... I don't know what, I have to do the onoffonoff thing 2, 5, 10, 50 times in a row so my phone can recover from is half comatose.
Yesterday, I could not use my phone for half an hour ...
and if someone calls me, I hear the ringtone, but screen stays black.
I can answer the call (but not knowing who's calling) by sliding on the part of the screen where the slider normally is.
Funny thing is about removing the battery. It doesn't solve my problem.
When I do so, my phone boots, I see the "Samsung Galaxy SIII" boot screen, on low brightness (whih is not normal ...)
After that, I normally have another boot screen with my provider's logo and tone. But screen goes black again (but I still here the tone)
Then I realized it started to happen when my phone proposed me a Samsung update.
I tried to reset my phone to factory settings but it didn't work, the update was still here.
For a while I thought my problem was solved, because my phone behaved normally for 3 or 4 hours, without problem.
But it came back.
I found on the internet several "almost-same-problems" without proposed solutions.
Like checking if the proximity sensor was blocked by a protective transparent plastic sheet, or a case.
I tried to to remove mine.
Didn't work.
Some people said it was linked to their phone trying to acquire a wifi network.
My wifi on or off, withiin or without the range of a wifi router didn't work ...
I tried to note things down about what I did, when, how, app launched before the problem appears.
I checked battery info (temp, voltage, etc).
No pattern emerged.
So.
Hs anyone of you enountered the same problem ?
Do you have ideas, solutions I can use ?
Or maybe a voodoo prayer ?
I could sent it back to my provider which will bounce it back to Samsung. But it will take ages (3 to 4 weeks ...) :'(
Thanks in advance !
do a factory reset, go completely stock
if that doesn't help, send it in
Glebun said:
do a factory reset, go completely stock
if that doesn't help, send it in
Click to expand...
Click to collapse
That's what I did.
I tried by going into the Parameters menu, and reseting.
I tried by booting my phone with Vol+ / Home / Power buttons to access a console mode and do a wipe data/reset.
The problem is that my phone got an update like one week ago from a 4.?.? to 4.1.2.
And even with a reset, my phone reboot with the 4.1.2 version, which seems to cause this problem.
Or maybe not, but I can't be sure.
As I said, after a factory reset I did yesterday, everything went well for 3 or 4 hours and the problem reappeared.
send it to the service
Hi. Today I rooted my phone using Odin 3.7 and Siyah-s2-v6.0b5 kernel, everything went fine, installed few applications like Smart Launcher, customized everything and messed around with a phone but after few hours noticed that my menu and back button lights stay always on. I tried everything, turning energy saver on and off, changing button light duration (off to on etc) and nothing helped. Lights kept staying no matter what. They only turn off with the screen (I changed the setting to 15 seconds). Why is that?
Yes, I did factory reset too actually. All my applications are now gone (I hate doing backups, but whatever) and I thought it will sort this issue out but it didn't help. Is there something that could be done without flashing ROM or kernel again? I'm paranoid of bricking my phone.
I googled and seems like I'm the only one with this problem. Android version 4.1.2. First time noticed this problem today after rooting.
P.S. I tried also some moderators solution here: sys/class/misc/notification/led_timeout change value to -1 but no effect, value doesn't change, reverts back.
EDIT: sorry I don't find the option to delete the thread. The problem was solved using STweaks application (got the idea from some member here to edit option in BLN folder) and I set timeout to 1 sec and everything is fine now. Thank you stranger very much.
For a week or two now,* I have been having some funny things happen with my Redmi Note 4 (Qualcomm, Global) phone.
Before that it had gotten water in it and basically shut down entirely, but they fixed it and got it up and running. When I picked it up they showed me watermarks on the screen, saying that the screen had frozen only once but that it may just be lagging.
Since then I have had a few symptoms of an issues, perhaps hardware issues, but potentially something that I can fix without paying more for parts.
Here are the things that happen:
- Music stops suddenly (screen on or off) and the music app has to be reopened (DoubleTwist, Miuiu's Music app, etc); Somes while in Doubletwist, if I click to visit home screen (square button) than the music stops. (this is the first issue that I noticed).
- 1-2 seconds of white screen before already-open apps appear after selected; Sometimes problems with apps loading or screen goes black when loading
- When closing apps or returning to home screen, it looks like the desktop(?) background comes up and then a second after is is re-populated with icons as if system is refreshing the home screen
- Once any of these issues begins, it usually worsens and the cell phone gets slower, behaving more and more strangely until not even useful to me; Reboot clears it right up for an hour or two or whenever this wierd stuff starts to happen again
-It seems like if I make a point of using the phone modestly, slowly, I can avoid these issues from starting up
- Sometimes reboot rometimes hangs on initial black loading screen
- Sometimes if I hit the power button to turn off the display, I can not turn it back on with that button (neither does the battery-dead orange light flash), so I have to reboot.
-When I turn the phone screen off while it has been working fine, I come back later, turn on the screen to find that it is now on the boot logo screen and it stays until I hard-reset the phone.
So, these are potential issues I have guessed at:
* Screen damaged? So far, other than watermarking at the top and some backlight bleed, sensistivity is perfect on the phone, and symptoms involving screen always seem to be triggered more by apps or pressing buttons.
* Apps or Android corrupted/internal memory damaged? I backed up via Settings and did a Hard/Factory Reset, then restored from backup. I still have the problems.
* RAM partially damaged? I test RAM with two apps and none of them showed issues. Namely my available RAM and used RAM reported always add up to the 4GB my phone has.
*Other Hardware Components failing? I used 3 apps to check all of the hardware devices and sensors that I could think of. Vibration is the only thing that does not work, and honestly, I don't care much about vibration.
Today I have suspected that settings may being at fault, and/or battery savers turning off my audio. Battery savers often identify my music apps as using "excessive amounts of power," perhaps because the speakers at involved, but it does make me think... I removed any battery-related and security apps, then turned off all battery saver options in settings earlier today. In 2 hours of music listening after that, I have not had any shutdowns, but I am not convinced I have solved the problems. In the weeks after this, the issue is back and the audio issue is always followed by the phone operating very sluggishly.
I have done a factory reset and restore, and the issue persists. Do you think there's any point in trying to do a clean reflashing of MIUI? Could it be a software issue or definitely hardware?
What advice can you give me?
Thank you for reading.
You can try booting in safe mode and then check if the problems still persist. Other than that, I suggest you to get advice from senior members of the forum.
Lazy_Pickachu said:
You can try booting in safe mode and then check if the problems still persist. Other than that, I suggest you to get advice from senior members of the forum.
Click to expand...
Click to collapse
Miui 9 does not have safe mode to boot in.