I recently bought an unlocked Amazon Fire phone ($125; it came loaded with Fire OS 4.6.4). The phone seems solid and well-built. The only change I made to the stock phone so far was to load Google Play, using the instructions on the spinyourfire website.
I have noticed that the screen timeout does not work anymore. Whether I set the interval to 15 secs or any other setting, the phone does not go to sleep until a good 4-5 minutes have elapsed. I Googled this problem but did not find anything. Has anybody run into this, or am I overlooking something obvious? Thanks much!
Do you have a screen protector? I had to remove mine because it was messing with the proximity sensor.
I do have a screen protector. Did you experience similar problems with your phone (screen timeout not working), and did they go away after you took the screen protector off? I'd never though of that...
philharvey said:
I do have a screen protector. Did you experience similar problems with your phone (screen timeout not working), and did they go away after you took the screen protector off? I'd never though of that...
Click to expand...
Click to collapse
I had a tempered glass screen protector. I didn't notice that specific issue. The 2 major issues I immediately encountered was (1) the screen would remain off during a call and (2) the home button wouldn't wake the phone up. Maybe either of those issues are also happening to you?
I did not experience the 2 problems you described (screen off during a call, and home button not waking the phone up). My screen timeout problem is really intermittent: it seemed to work fine yesterday as the phone went to sleep after 15 secs of inactivity, as I wanted it to. Today, the phone remained stubbornly on for 10 mins and refuses to go to sleep.
I wonder if sideloading Google Play has something to do with it. I'll try uninstalling the Google Play stuff and see if it affects my timeout problem. I will update the thread.
I may have stumbled on the cause, as well as the solution, of my problem: apps running in the background may have prevented the phone from going to sleep.
I used the "Quick Switch" feature on the phone to display all running apps, then killed most of them by dragging them towards the top of the screen. Now my phone is going to sleep within 15-30 secs of inactivity, like I wanted it to. I hope this thread helps someone else struggling with the problem.
philharvey said:
I may have stumbled on the cause, as well as the solution, of my problem: apps running in the background may have prevented the phone from going to sleep.
I used the "Quick Switch" feature on the phone to display all running apps, then killed most of them by dragging them towards the top of the screen. Now my phone is going to sleep within 15-30 secs of inactivity, like I wanted it to. I hope this thread helps someone else struggling with the problem.
Click to expand...
Click to collapse
That's good news. Glad you didn't have to rip off your screen protector. Now all you need to do is figure out which app in particular is keeping your phone awake.
Related
I received a calendar event notification on my lock screen yesterday. It kept my screen on for 3 hours and drained the battery down into the teens. My Note was in a case and when I pulled it out it was very hot. Anybody else have this happen? I am new to touch wiz. All my phones have been Nexus devices. I haven't applied the OTA updates yet so maybe those will fix it. I may play around around bit to see if I can recreate the problem before I update. Until then I have turned off lock screen notifications.
Pretty sure the home button wasn't being held down. I will look into that too.
Brewbud said:
I received a calendar event notification on my lock screen yesterday. It kept my screen on for 3 hours and drained the battery down into the teens. My Note was in a case and when I pulled it out it was very hot. Anybody else have this happen? I am new to touch wiz. All my phones have been Nexus devices. I haven't applied the OTA updates yet so maybe those will fix it. I may play around around bit to see if I can recreate the problem before I update. Until then I have turned off lock screen notifications.
Pretty sure the home button wasn't being held down. I will look into that too.
Click to expand...
Click to collapse
Also looking to see if there is a solution for this. I am also having the same issue. I've had it happen three times already and it completely drained my tablet. Couple times I caught it before it turned off and the tablet was hot, like yours. I'm stock. Received last 2 ota updates. Mine sits in a pouch ( if that makes a difference with sensors or anything. ) I set the screen time out to be 30 secs. Still doesn't work. Something broken with the notification.
Hello,
The screen of my moto 360 goes randomly off and vibrates at that moment, just like when you dim the screen with your hand., but now I'm using it. It's very frustrating because I can't even open an app normally or the screen goed of and I need to start over again. Does anyone know how to fix this?
Having same issues with mine.
Really strange and really annoying. Its like when u cover it with palm. It vibrates and screen goes off but ur in the middle of trying to do something. Anyone else having this problem?
Glad I'm not the only one having this issue, just got my Moto 360 today. I'll be in the Settings or other parts of the watch and it will just randomly turn off. It is really frustrating to deal with.
I have the same issue. I have pretty hairy arms so I wonder if the hairs are somehow triggering the capacitive touch screen.
you guys try to do a reset on the watch yet?? not just a reboot..
Any updates on this? I'm having the same issue
Any updates? I have the same issue I think it happend after udate to 5.0.2 but I'm not sure.
I'm also having the same problem. I picked up a new Moto 360 during the BBY sale rush of the last couple of days. At first it was buggy but the screen seemed to stay on while working with it. Then it had a system update, and since then most bug issues (like the faces not updating with the companion app changes) went away, however from that point the screen constantly shuts off, usually with a little buzz, while I'm interacting with the watch.
For instance, regarding the sensor used to turn off the watch if you palm it. I thought maybe that was it, so I was looking for a way to turn that off. I went into settings, and spend about 10 times of the screen shutting off before I could get to "accessibility settings" just to see if that might be there.
This problem occurs whether I'm wearing the watch or not (trying to eliminate arm hair or similar), and has occurred after a factory reset and re-pair with my phone (Note 4). Ambient sensor settings don't help, because all that does is make the screen go dark instead of off, but it still reverts back to the clock no matter what I was doing.
Any ideas? Any way to turn off a sensor perhaps, maybe in a custom ROM? Since this seems to be associated with an update near as I can tell, I wonder if a fix is coming from Moto or if it's too rare of an issue to be on their radar.
As an update, I replaced the watch with a new one, and this new watch is perfect. It started on outdated software which I left on for a bit to make sure it didn't show the problem, then I updated. Still no issues. I think there is a chance the problem is software regardless, but either way it must be a small portion of watches and isn't necessarily tied to any particular outside software influence (phone model or android version, or installed apps as NONE of those things changed). My advice to people reading this thread is to exchange the watch or get an RMA if possible.
Same Issue
Hi All,
I have the same issue. Sent it back for repair so let's see...
Same issue here as well
I've been reading through the previous threads and I'm still confused if the issue is hardware or software related. I have the AUO panel and have broken swipes, and times where I can't scroll properly. This has been going on a couple months now and it's getting on my last nerve since it's frequently happening when I need my phone to work properly. All this time I assumed it was software but a couple threads mentioned it was hardware. Trouble is, some people with the JDI screen also have issues so I don't understand. My question is, has anyone ruled out software by flashing an AOSP rom? I'd rather not send this to Sony if at all possible since they don't cross ship and I'd be without a phone.
I have rarely an issue with the touch screen, when swipe up or down, it doesn't swipe it acts like I've just touched (clicked) once the display. I think it is a software issue, because in my case, if I turn off the display wait for 2-3 seconds and turn it on, it works with no problems.
Can you point me please to other threads that have this issue in discuss?
Thank you!
Have you removed the asf from the screen and placed an actual screen protector on it? I found that this really helped with the weird screen issues.
I have a screen protector over the ASF. But that has nothing to do with my issue, because, like I said, when I turn the display off, wait 3 seconds, and on again everything is working normally.
vibecatalin said:
I have a screen protector over the ASF. But that has nothing to do with my issue, because, like I said, when I turn the display off, wait 3 seconds, and on again everything is working normally.
Click to expand...
Click to collapse
Yeah, I reboot usually and the issue temporarily goes away. Then it will come back a day or two later. I'm afraid to remove the ASF because I've read some issues with goes touches even with a screen protector. I just want the issue to be fixed... I was thinking of flashing a AOSP rom but wanted to see if anyone with that ROM had any trouble or not. Maybe the L update in January will fix things.
Here are the resources I've read on this issue:
http://talk.sonymobile.com/t5/Xperia-Z1-Compact/Touchscreen-loosing-touch-issue/td-p/580111
http://johnhaller.com/blog/2014-03-06--sony-xperia-z1-z1s-touch-screen-issue
http://forum.xda-developers.com/showthread.php?t=2770293
I have rarely that issue, like I said I just turn off the screen, and after 2-3 seconds turn it on and it's gone. I'm sure this is a software related issue.
If it helps at all, I never had the issue in the two weeks I tried an aosp rom. However the camera and battery life were a bit lacking so I'm back on a stock rom.
I haven't have the issue too in the past weeks, I've wiping cache and dalvik cache pretty often , because I've installed some system apps. Anyway I will really want to know the cause of this
L.E. I'm still on stock firmware.
L.E. 2 : The Glove mode function, in the Settings-Display menu has an application or something? Has a file redirected to it? Is there in the phone's system a file than can be edited or deleted or something for the glove mode function? Maybe we will find answers there.
I'm not sure that I've made myself understood with the question.
I've been recently getting some instances where I would lock the phone and the fingerprint sensor won't respond to my finger.
This really started when I changed my lock to pattern swiping. Anyone have the same issue? I rebooted and changed it back to pin lock and it seems to be working all the time again, but I don't know what caused it in the first place.
Thoughts?
How many fingerprints do you have saved? I have 3. 2 of my left index finger and one of my right. 95% of the time I use my left. Set up several and see if that helps. Move your finger all over the sensor when setting it up so it gets a broad picture of your fingerprint
jbdan said:
How many fingerprints do you have saved? I have 3. 2 of my left index finger and one of my right. 95% of the time I use my left. Set up several and see if that helps. Move your finger all over the sensor when setting it up so it gets a broad picture of your fingerprint
Click to expand...
Click to collapse
It's not that it doesn't recognize my fingerprints, but it doesn't recognize fingerprints in general. So when I put my finger on it, it doesn't do the double buzz, it's just non responsive.
this happened to me yesterday several times. And i received phone yesterday... . I have two prints. Left and right index fingers. It didnt fail, just was as my finger wasnt in the reader
MDB08L
experienced the same thing this morning. phone was plugged charging and finger print would not detect, had to manually hit the power button then it worked. i find there are a lot of issues when the phone is charging though, screen sometimes becomes very unresponsive while charging. i think there was a similar thread about that as well.
Just started having this today as well. Sometimes doesn't acknowledge fingertip at all; works if i press lock button to wake the screen. Kind of a bummer, otherwise very satisfied overall. Hope it's just something that can be ironed out with a software update.
---------- Post added at 11:58 PM ---------- Previous post was at 11:52 PM ----------
Nothing out of the ordinary installed. Twitter, Instagram, Dropbox, etc. Nothing to interfere with lock screen. I do use pattern unlock.
EDIT: Will try PIN unlock instead of pattern for a while to see if it acts any differently.
ajmalott said:
Just started having this today as well. Sometimes doesn't acknowledge fingertip at all; works if i press lock button to wake the screen. Kind of a bummer, otherwise very satisfied overall. Hope it's just something that can be ironed out with a software update.
---------- Post added at 11:58 PM ---------- Previous post was at 11:52 PM ----------
Nothing out of the ordinary installed. Twitter, Instagram, Dropbox, etc. Nothing to interfere with lock screen. I do use pattern unlock.
EDIT: Will try PIN unlock instead of pattern for a while to see if it acts any differently.
Click to expand...
Click to collapse
Any luck? I did a system wipe after unlocking, and flashed new factory images but still happening.
No luck. Still happening either way. I'd say maybe 10% of the time, fingerprint unlock works correctly. The other 90% I have to wake the screen with the lock button first. Sometimes after trying fingerprint multiple times, when I press the lock button and the screen wakes there is a little message at the bottom that says "Fingerprint hardware unavailable" in red where the little fingerprint icon usually is. But then it immediately changes to the fingerprint icon and it works fine.
ajmalott said:
No luck. Still happening either way. I'd say maybe 10% of the time, fingerprint unlock works correctly. The other 90% I have to wake the screen with the lock button first. Sometimes after trying fingerprint multiple times, when I press the lock button and the screen wakes there is a little message at the bottom that says "Fingerprint hardware unavailable" in red where the little fingerprint icon usually is. But then it immediately changes to the fingerprint icon and it works fine.
Click to expand...
Click to collapse
I was able to find a bit more about this issue. When it happened again, I pressed the power button and quickly checked the fingerprint icon at the bottom of the lockscreen and it turned red and said "fingerprint hardware not available" for a split second before turning white again. I searched that error message and got this thread https://www.reddit.com/r/nexus5x/comments/3pm3lv/fingerprint_hardware_not_available/
I'll try wiping the cache and see if that helps at all. If not, I'm going to RMA.
jadesocket said:
I'll try wiping the cache and see if that helps at all. If not, I'm going to RMA.
Click to expand...
Click to collapse
I'm not much of a tinkerer, but I'll give this a shot. If it clears it up then okay, but if it happens again I'll probably RMA too. Not willing to put up with such inconsistencies on a brand new phone with such a highly touted feature.
Unrelated, this is actually already my second Nexus 5X. The first one I received would not take a charge, and I didn't have another USB Type-C cable to test, so they sent me an entirely new package. If wiping cache doesn't do it, I'm really not sure if I should bother with a third Nexus 5X. Kind of disheartening. I really enjoy the device otherwise.
So far so good for me, Let me know how it goes for you!
jadesocket said:
So far so good for me, Let me know how it goes for you!
Click to expand...
Click to collapse
Still happening today.
ajmalott said:
Still happening today.
Click to expand...
Click to collapse
That's a bummer. It actually happened again today for me too.
jadesocket said:
That's a bummer. It actually happened again today for me too.
Click to expand...
Click to collapse
I chatted with a Google support rep today, describing the issue and sending links to other message boards that are discussing this topic. He had me restart the phone in safe mode and sent a follow-up email, asking me to check back in after a few hours or a day or whenever, and let him know if the issue happens again. This was about seven or eight hours ago, and I haven't had the fingerprint sensor fail once when pulling the phone out of my pocket. It seems possible that a third-party app is interfering with the sensor's ability to function when the device is locked and the screen is off. I haven't installed very many apps, and they're all mainstream ones that everybody uses. My next step may be to factory reset the phone and stick to stock install for a day or two, then maybe add apps like Twitter, Instagram, etc., back one at a time per day and see if the issue returns. If it is a software issue, I don't think an RMA is necessary.
EDIT: Well it just did it, never mind all that
ajmalott said:
I chatted with a Google support rep today, describing the issue and sending links to other message boards that are discussing this topic. He had me restart the phone in safe mode and sent a follow-up email, asking me to check back in after a few hours or a day or whenever, and let him know if the issue happens again. This was about seven or eight hours ago, and I haven't had the fingerprint sensor fail once when pulling the phone out of my pocket. It seems possible that a third-party app is interfering with the sensor's ability to function when the device is locked and the screen is off. I haven't installed very many apps, and they're all mainstream ones that everybody uses. My next step may be to factory reset the phone and stick to stock install for a day or two, then maybe add apps like Twitter, Instagram, etc., back one at a time per day and see if the issue returns. If it is a software issue, I don't think an RMA is necessary.
EDIT: Well it just did it, never mind all that
Click to expand...
Click to collapse
I had hope Looks like RMA imminent for me. I put that glass screen protector on so well...
ajmalott said:
EDIT: Well it just did it, never mind all that
Click to expand...
Click to collapse
Lots of apps updated in the past week. The problem hasn't resurfaced for a whole 48 hours now. Hoping I can put this behind me
jadesocket said:
That's a bummer. It actually happened again today for me too.
Click to expand...
Click to collapse
I've spent the past week emailing back and forth with Google tech support, sending in bug reports, even sending a video of the problem happening (and showing the fingerprint sensor working immediately after pressing the lock button). They've determined that the fingerprint sensor hardware itself is fine, and the problem is that instead of waking the screen it's telling the phone to go into Doze. I'm still sending them bug reports, and they're trying to replicate the problem on their own Nexus 5X to determine what (possibly an app?) is causing the problem. I'll report back in with any more information, in case anyone else has the problem and ends up here.
It happened to me too, stock phone, no third apps installed. I will keep an eye on this.
off-topic: the discoloration of the back of the phone it's very bad!
ajmalott said:
I've spent the past week emailing back and forth with Google tech support, sending in bug reports, even sending a video of the problem happening (and showing the fingerprint sensor working immediately after pressing the lock button). They've determined that the fingerprint sensor hardware itself is fine, and the problem is that instead of waking the screen it's telling the phone to go into Doze. I'm still sending them bug reports, and they're trying to replicate the problem on their own Nexus 5X to determine what (possibly an app?) is causing the problem. I'll report back in with any more information, in case anyone else has the problem and ends up here.
Click to expand...
Click to collapse
I believe it's not the hardware as well. I've noticed that it's mainly when I get notifications from something that the sensor stops working.
jadesocket said:
I believe it's not the hardware as well. I've noticed that it's mainly when I get notifications from something that the sensor stops working.
Click to expand...
Click to collapse
Did a factory reset, and the problem came back almost immediately. Google tech support wanted me to reinstall OS entirely, but I don't have the right cable (type C to type A) to hook up to computer, so they just gave RMA. Got the new one on Friday, so far so good. But then, with the last phone, the issue didn't appear until after a week or two. Fingers pressed. Tech support really seemed to take my case as a rarity, and they were unable to recreate it with their own device. Here's hoping it's just limited to a few devices.
P.S. Off topic, but Google support wouldn't give me anything for the Black Friday deal. I asked multiple times in multiple ways. Oh well.
I've gotten this problem since 20 days ago where my Google Maps get frozen in the middle of my trip. And I had reboot the device multiple times (4-5 times, sometimes skipping the LineageOS booting animation).
After fiddling over 2 weeks, I finally switched to LineageOS 17.0 now (previously using 15.1). The problem still persists.
The problem is : the screen froze, I seem able to tap something on screen but the display doesn't change anything despite my interaction with screen. This especially pronounced when I stop my screen interaction (i.e. not scrolling) on these apps
- Google chrome (say, reading any articles on web)
- Quora (especially when I about to scroll down on author bio)
- Google Sheets
- Maps
but this unresponsiveness doesn't appear at all when I:
- Play any kind of games
- watching YouTube (with the app)
In general, it seems anything that uses webview can cause the screen freezes if I leave it couple seconds. At first I thought changing from android webview to chrome webview implementation changes this. It doesn't.
The "cure" I found is simply turning the display off for 40 seconds ~ 75 seconds, and turning it back on, where I can interact with lock screen fine again. Any time lower than 40 seconds will simply show the frozen display again the time I turn the screen on.
Is it possible it's a hardware problem? (faulty RAM/storage) after using this for 2.5 years) Since full system wipe and re-install doesn't entirely solve the problem. The first time I encountered this is when I navigate with my Google Maps and the screen simply froze out during drive, and I had to restart the device multiple times, worrying that my device is broken. The next time I drive, I leave it only on Ambient Display and it didn't freeze at all.
So... any idea how to troubleshoot this?
It seems the problem is more severe than just Android.
Because even in TWRP, I noticed the display need to wait ~1 minute from the last time I turn off the display (push the power button) to reactivating it.
If I try to turn it on, the display will give black color, but I still can actually interact with the system.
ArcOnFire said:
I've gotten this problem since 20 days ago where my Google Maps get frozen in the middle of my trip. And I had reboot the device multiple times (4-5 times, sometimes skipping the LineageOS booting animation).
After fiddling over 2 weeks, I finally switched to LineageOS 17.0 now (previously using 15.1). The problem still persists.
The problem is : the screen froze, I seem able to tap something on screen but the display doesn't change anything despite my interaction with screen. This especially pronounced when I stop my screen interaction (i.e. not scrolling) on these apps
- Google chrome (say, reading any articles on web)
- Quora (especially when I about to scroll down on author bio)
- Google Sheets
- Maps
but this unresponsiveness doesn't appear at all when I:
- Play any kind of games
- watching YouTube (with the app)
In general, it seems anything that uses webview can cause the screen freezes if I leave it couple seconds. At first I thought changing from android webview to chrome webview implementation changes this. It doesn't.
The "cure" I found is simply turning the display off for 40 seconds ~ 75 seconds, and turning it back on, where I can interact with lock screen fine again. Any time lower than 40 seconds will simply show the frozen display again the time I turn the screen on.
Is it possible it's a hardware problem? (faulty RAM/storage) after using this for 2.5 years) Since full system wipe and re-install doesn't entirely solve the problem. The first time I encountered this is when I navigate with my Google Maps and the screen simply froze out during drive, and I had to restart the device multiple times, worrying that my device is broken. The next time I drive, I leave it only on Ambient Display and it didn't freeze at all.
So... any idea how to troubleshoot this?
Click to expand...
Click to collapse
Can you enable "Show Tap" option in developer settings and see if theres any ghost touch happening, sometimes ghost touch can "freeze" the screen while you want to interact with it
Shimizux said:
Can you enable "Show Tap" option in developer settings and see if theres any ghost touch happening, sometimes ghost touch can "freeze" the screen while you want to interact with it
Click to expand...
Click to collapse
Thanks for responding.
I already enable "Show taps" on developer options. But the problem is that the screen freeze happened when there was no touch at all (i.e. I just looking at the screen, reading)
There's new observation I made today that : usually the screen doesn't want to immediately awaken when I just turn the screen off.
Today I tried to remove fingerprint from lock screen, the screen now is able to respond quickly again upon pressing power on button. It's still as responsive to power on when I add pattern to the device lock mechanism.
I'm not too sure whether this is OS level problem or even closer to hardware problem because this kind of unresponsiveness is also apparent even when I boot to TWRP.
ArcOnFire said:
Thanks for responding.
I already enable "Show taps" on developer options. But the problem is that the screen freeze happened when there was no touch at all (i.e. I just looking at the screen, reading)
There's new observation I made today that : usually the screen doesn't want to immediately awaken when I just turn the screen off.
Today I tried to remove fingerprint from lock screen, the screen now is able to respond quickly again upon pressing power on button. It's still as responsive to power on when I add pattern to the device lock mechanism.
I'm not too sure whether this is OS level problem or even closer to hardware problem because this kind of unresponsiveness is also apparent even when I boot to TWRP.
Click to expand...
Click to collapse
That is one big weird problem, i've never encounter something like that since i ever using a smartphones.
It does really sound like, it just a software problem. But if it also happen in TWRP, it doesn't look like it.
I also have installed LOS17 by Arian before too, and i dont have that problem.
Sorry man i have no idea nor expert about it
It could be your battery is dying?, if your battery cant give enough power to the screen already, screen gonna act like crazy i.e ghost touch etc.
I have a broken battery been using it for 2Year + because of the battery my screen has a problem too. I replaced it last december 2019 and everything went normal again.
Shimizux said:
That is one big weird problem, i've never encounter something like that since i ever using a smartphones.
It does really sound like, it just a software problem. But if it also happen in TWRP, it doesn't look like it.
I also have installed LOS17 by Arian before too, and i dont have that problem.
Sorry man i have no idea nor expert about it
It could be your battery is dying?, if your battery cant give enough power to the screen already, screen gonna act like crazy i.e ghost touch etc.
I have a broken battery been using it for 2Year + because of the battery my screen has a problem too. I replaced it last december 2019 and everything went normal again.
Click to expand...
Click to collapse
I don't think it's a battery problem. I see that I can play game for 1hr+ fine. A game that require exact timing of 2 touches on top of that. So that ghost touch really doesn't appear.
But yeah, it's really 2 contrasting sign
- In one hand, it seems an OS problem because I can simulate an environment where the screen definitely won't be frozen for hours, while on specific other environment, the screen freeze can happen very quickly between release and re-occurence.
- On the other hand, the problem seem doesn't stop on OS level because it can be found in TWRP.
If I read an answer on Quora that shows GIF image on the section I read, the screen freeze 100% won't happen. I tried the same thing on imgur too, the screen freeze won't happen.
So it seems that as long as the screen is showing dynamic content, it won't freeze (that's why game and YouTube doesn't show this kind of problem, but reading a web full of text/static images can)
A bit of update : I have left my phone in off state for 4-5 days. And I have been using it again, albeit, less extensively since my main phone has changed to K20 Pro.
Long story short : I haven't encountered screen freeze again. But this is just after 2 days playing with less intensity.
I wonder what really went wrong.