This is a 4 month old, unlocked, bought directly from HTC, 10 that was working like a charm until two weeks ago when I would hit the power button to wake the screen and a notification sound would blare from the speakers. It does it every time now. It also does it when I wake with fingerprint scanner. I just upgraded tonight to Nougat and I still have the problem. I've checked all settings at least 15 times and there is nothing checked that shouldn't be, such as 'screen lock sounds' 'tap sounds' etc. Nothing. If I hit the power button in the theater, I'm sure I'll have 300 pairs of eyes glaring at me.
Running Android 7.0 / 2.38.617.6
Anyone encounter this situation or have any ideas? I've soft rebooted several times, no luck.
Thanks in advance.Nor
Related
Hi, i have just got a new xda orbit and noticed that when the backlight goes off after a set period (30 secs), it seems to be still lit but only very slighty, so at night you still see the today screen etc. But if i press the power button then the display goes off. Is this correct ?
The reason im asking as i have been using an xda mini s for over a year and when the backlight times out the display is not visible at all in the dark. You have to press the power button to see the screen again.
Hope this makes sense
Yes, that is fine. The dim backlight will go out in time too.
MaskedMarauder is 100% right. It will go out eventually.
Ok thanks guys for the quick reply, just obsevered it last night and noticed it was different.
Thanks again...
I've tried posting about this before, but it never gets answered - i've got a mda III, and that dims to brightness 1 (from within the registry), but will never go out - regardless of what rom i've tried.
I've also noticed that i can force set it to 0 in the registry, but thats the overall screen brightness. None of the other reg keys (putting bkl1:, etc in the various power keys) seem to work.
Any one got any ideas or utils to sort this? I'd try to code this as there are some code samples which allow you to force this, but i've not got VS
Like you i've tried all the registry edits i can think off to no avail. I too have a wizard and find this irritating - plus backllight stays on when media player on etc.. No difference with wm6 so i guess it maybe a hardware issue. I use a small app to turn off display when apps are running and i want the display off.
I use backlight time of 30 secs and power of 1 minute - so overall similar to my wizards backlight time of 1 minute.
why not..
why not just pres the I/O button on the side to turn off the backlight when u don't want it on? obviosuly a bit of a hassle, but if u get into the habit of doing it, no problems
Because that puts the device into standby and turns everything else off too (except the phone etc.) So if your listening to music your plunged into silence.
I had an XDA2i (Alpine) previous to my Orbit and I actually prefer the dimmed screen.
A brief press on the 1/0 power button WILL make the device go into standby.... BUT...
press and HOLD the power button for LONGER than 2-3 seconds and it toggles the backlight on and off, whilst STILL keeping the device on!
hope this helps
Joe
I have a Samsung Focus, upgraded weeks ago to the official Mango release via AT&T.
Ever since the upgrade, I've noticed a weird recurring problem, where it looks like my back button goes absolutely insane for 5-10 seconds. I could be typing a text, and the phone will start backing out of the messaging center and through my app history until it spontaneously stops a few seconds later. It's happened while I've been browsing in IE and a few other apps.
My hands are nowhere near the capacitive buttons when this happens, so I'm not activating them unknowingly. In fact, I can set my phone down during the period of crazy, and it'll still back through programs on its own. I'm convinced it's the phone registering phantom hardware presses, because each back function is accompanied by the slight vibration that's toggled when you normally tap one of the lower buttons. Except I'm not tapping anything.
Now, this has only happened 3-4 times since Mango was loaded, but it had never occurred prior to that, even when I was running the beta. Still, it's annoying when my phone has a mini-freakout, and I was curious whether anyone else had noticed a similar problem.
I haven't noticed that, but I have noticed that the back button seems to be more sensitive, and sometimes just briefly brushing my finger against it brings up the app switcher.
Hi,
I started to get a weird problem since last week. I've had this phone for about 3 months now and never had any problem like this.
It all started one morning when I wanted to stop phone alarm. The alarm was going off but the screen was black. I pressed the power button to wake up, but it was still black. After couple of times pressing the power button the screen came up. First it was not that often but the situation started to get worse. It came to that I can sometimes cannot turn it on for a long period of time. I need to keep pressing power button, volume buttons and eventually it will come up.
This is what I've found so far:
1) When the power button is pressed, although the screen doesn't start up, I can see the three buttons at the bottom lighting up. So it is not a problem of the power button.
2) When the power button is pressed, although the screen doesn't power up, the screen seems responsive. I can feel the vibrations when I tap (I have a startup password)
3) When the phone is connected to a power supply, screen always starts up without a problem.
4) Screen will start up more frequently when the batter power is high.
It seems as though there is a connection between batters power and the screen not starting up. But then again, once the screen comes up (after not starting up), then it works fine, until I turn the screen off.
Has anybody experienced anything like this before?
I did a factory reset thinking it might be some application I installed but it didnt help.
I had to send this phone once to repair the speaker and cost more than $80 just for courier. I don't want to spend another to get this fixed.
Thanks.
I have this problem or a problem very close to this. I have a HTC One X (international version). I'm running the latest version and updates and the problem has existed for at least the last two updates.
Android Version 4.1.1
HTC Sense version 4+
Software number 3.18.401.1
I have the screen lock pattern turned on.
Sometimes when I hit the power button, the phone does not turn on and so I press it again and only after a third press does the phone turn on. I then unlock the phone and use as normal. So, several times per day I have to press the power button three times before the phone turns on. But other times I press the power button once and it turns on straight away. I've just turned the pattern unlock off to see if this makes any difference. I'll start to record the exact details of when I experience this and see if we can work out a common cause.
Hopefully if enough people report this problem then they can send out an update to fix this problem.
exazonk said:
I have this problem or a problem very close to this. I have a HTC One X (international version). I'm running the latest version and updates and the problem has existed for at least the last two updates.
Android Version 4.1.1
HTC Sense version 4+
Software number 3.18.401.1
I have the screen lock pattern turned on.
Sometimes when I hit the power button, the phone does not turn on and so I press it again and only after a third press does the phone turn on. I then unlock the phone and use as normal. So, several times per day I have to press the power button three times before the phone turns on. But other times I press the power button once and it turns on straight away. I've just turned the pattern unlock off to see if this makes any difference. I'll start to record the exact details of when I experience this and see if we can work out a common cause.
Hopefully if enough people report this problem then they can send out an update to fix this problem.
Click to expand...
Click to collapse
I'm pretty sure this is a hardware issue. I bought mine from Expansys and sent it back to them for repair. It's been more than a month and they say they're still reparing it.
In my case it was impossible for me to start the screen up with power button no matter how much I pressed it. The only thing that worked for me was to press the back of the phone just below the camera. So it seems like a hardware issue. But on the other hand, at times when I can't get the screen turned on no matter what I do, I'd turn the phone off and start again and the thing would start up like nothing happened. So while I'm pretty sure it is a HW issue, I'm not sure how a power restart makes it work.
For me I don't think that this is a hardware problem as it only started happening once I did the big upgrade from 4.0 to 4.1 and then it follows a specific pattern. That is three power button presses will always turn it on. Less frequently I also get a problem where the power button turns on the three lights on the soft buttons but the screen remains black. I then hit the power button to turn it off, and again to turn it on and the phone is back to normal again.
Is yours an international version? I bought mine an international version and had it shipped to Australia.
solved?
Hi - did anyone ever solve this? This is happening to me with my HTC desire X after having had the screen repaired, so I think it is hardware related, but the shop doesn't know how to fix it! My screen also does not turn back on when I want to end a phone call and pull the phone away from my face anymore. These problems seem related as they started at the same time. I would be grateful for help!
Hi guys, I bought a new zenwatch and am experiencing a weird issue. Occasionally, when the watch is in ambient mode, it is not responsive to touch. I turned off wrist gestures to wake up the device, and need to tap it to wake up. Sometimes I tap it and nothing happens at all, it stays in ambient mode. Pressing the power button at the back will wake up the device and it will function normally. It is just slightly annoying to have to press the power button which is on the back a few times a day. Any input to why this might be happening is appreciated.
I have the same problem, but sadly no solution. I've had the watch since Jan and it only recently started doing it, last month or so
At least its good to know I'm not the only one, probably a software bug.
Mine does that occasionally. I find that rotating it back and forth a couple of times (even though Tilt to Wake is switched off) before touching the screen clears it.
Mine did that just a little while ago. I do still have tilt to wake turned on, though, and after waking once that way, it's back to responding to taps now.
Also, selecting a different watchface from the phone seems to clear it.
Pretty sure it has something do to with the latest update. Maybe they are using more aggressive power saving settings on the cpu governor, making it take longer to ramp up clock speed and be responsive.
Hi everyone,
Any help here is appreciated.. I have a moto 360 v2, had it for about 5 months and gave up on it a few months back because it was so laggy and glitchy.
Got it out again a week ago, thinking maybe new updates or whatnot would get it up to speed, and having the same results.
The watch was unresponsive 80% of the time, and spent most of its time flipping in between awake and dimmed, so I turned off AOD as suggested in other posts (although it should have been fixed as I am on the recent firmware?). I also turned off the "lift wrist" wakeup gesture. Now if I touch the screen or press the side button, it usually turns the screen on and then instantly back off. If I can get it to stay on I can open notifications about 50% of the time, the other 50% the screen is unresponsive. Lastly, if the side button opens the apps its a miracle, and I can scroll through the apps briefly before becoming unresponsive.
I've tried factory reset and the above two fixes.
I just tried recovery mode, but the screen doesnt work in recovery mode so I can't swipe between options..
I have emailed Motorola but haven't heard back yet.
I'd love for this device to work well, as it seems like a great device, but its basically unusable atm.
Any help/suggestions would be great!
Thanks