Hi,
my screen is set to turn off in 30 seconds but is not happening. Stays on.
Noticed that some time ago but thought was one off but it isn't.
Any ideas???
If i turn the phone off and on, it works again but don't know for how long?
There's an option in the developer settings to keep screen on when charging. Is that ticked?
Sent from my Nexus 4 using Tapatalk 2
ackliph said:
There's an option in the developer settings to keep screen on when charging. Is that ticked?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Happens when not charging????
I have the same issue. Hopefully someone can help
Oh not just me.
Happens when not charging, it is random.
Had like 5 android phones and always end up asking for problems
Is there any android phone without problems?
Sent from my Nexus 4 using Tapatalk 2
5 android phones with problems, really...
I've had 4, not a single one. I think you're something to them.
calanizzle said:
5 android phones with problems, really...
I've had 4, not a single one. I think you're something to them.
Click to expand...
Click to collapse
Believe me there is always something
Own two devices atm :
nexus4 - this screen problem, rattle, camera became unresponsive more then once and there is something with the network signal (don't know yet what is it)
nexus 7 - the lag, that's not butter for sure.
Must be me.
I had this problem too. But for now it's back to the 30 seconds. No idea how it started and how it stopped. Pretty sure after I tried a reboot, that it still happened.
Related
Hello
Does anyone have any idea why the device takes 4 seconds to come on ??????
the artix rooted
Mine takes less than a second. There have been a few times when it took a little longer, but that's pretty rare.
I'm rooted, but I stuck with Blur.
gamliel said:
Hello
Does anyone have any idea why the device takes 4 seconds to come on ??????
the artix rooted
Click to expand...
Click to collapse
Are you underclocking? I have SetCPU set to lower mhz's when the screen is off, which I noticed did cause it to take longer to come on, once the profile was set.
underclockink ??? what is this ???
gamliel said:
underclockink ??? what is this ???
Click to expand...
Click to collapse
Its when you set it so the CPU can't go above a certain mhz to save power. Opposite of that is over clocking which makes the CPU go faster.
Sent from my MB860 using Tapatalk
Wow mine easily takes 15 to boot
Completely stock
If you installed live wallpapers from market don't use them, I had same problems with some, sometimes took some time to wake up. However the stock ones are fine.
Sent from my MB860 using XDA App
Techcruncher said:
Wow mine easily takes 15 to boot
Completely stock
Click to expand...
Click to collapse
I think what he means is when the phone is already on, to wake the screen.
You right.
I try all the think that the guys said .....
but it is not help to me.
it take sometime. More then 4 second.
why????????
The device is clean. Only Rooted no apps and no wallpaper
I've been having issues with this too. I definetly hope this gets resolved at some point. My captivate was on as soon as I hit the button.
I am having issues with my 32 GB tablet. Sometimes the screen stops responding to touch and I either have to leave an app or turn off the screen and back on again to get it back. Occasionally, when I lock the screen to get it unfrozen then it doesn't come back, and restarts.
Anyone else experience anything like this?
Same here. When the screen looses responsiveness I have to reboot.
Sent from my Nexus 10 using xda premium
Sounds like a software issue to me. A very large portion of people seem to be reporting this and I have had this happen to me as well in two instances. I'm sure it will get worked out sooner rather than later.
Same Here
Takes forever to power back on..
mine restarts quite fast... i would know since it keeps on crashing and restarting itself
ShadowVlican said:
mine restarts quite fast... i would know since it keeps on crashing and restarting itself
Click to expand...
Click to collapse
Same here. Happened twice today when my N10 was idle. Screen was frozen on lockscreen. I could turn the screen on and off but it would stay unresponsive.
Meh...
All these restarts, frozen screens, etc are starting to take a toll on my patience.
johno86 said:
Happened twice today when my phone was idle.
Click to expand...
Click to collapse
Did you really mean "phone"?
ContentsMayVary said:
Did you really mean "phone"?
Click to expand...
Click to collapse
Oh, I meant Nexus 10, hahahaha.
I get confused with my nexus devices... =\
My Nexus 4 does this thing where it dims the screen a few seconds before it goes to sleep.
I thought my Nexus 7 did the same thing, but lately it does not. Was I just imaging it?
Solutions Etcetera said:
My Nexus 4 does this thing where it dims the screen a few seconds before it goes to sleep.
I thought my Nexus 7 did the same thing, but lately it does not. Was I just imaging it?
Click to expand...
Click to collapse
n7 still does it, confirmed
maybe you're still high :silly:
Yes, you are high.
Anyone got an issue where after some time (can be one week plus), you pick up your tab and the touchscreen is completely unresponsive on the lockscreen, can't even press powermenu? Reboot fixes. I had it on JSS1J and persists into JSS1Q. Hard to isolate as it may not happen for say a week of uptime, seems to be no pattern or consistent trigger
Sent from my Nexus 7 using Tapatalk 4
I been getting the same thing. Charging over night the tablet wakes but touch is unresponsive. I'm on Clean rom and Elementalx kernel. Yesterday morning after 8 hours on battery and unused it woke and touch was fine. This morning after 6 hours on charger, over night, it woke and touch is fine. Need more testing.
Note: yesterday afternoon I update Elementalx kernal to 1.3
Yeah elemental or stock it happens
Sent from my Nexus 7 using Tapatalk 4
A week or more? I can't get my nexus 7 to last more than a few hours without rebooting itself.
Sent from my Nexus 4 using xda app-developers app
I see this from time to time on mine. What sucks the most is when the damn alarm is going off and I can't do anything but hold the power down to reboot. Wife loves this "feature" in the early AM.
I have an unlocked bootloader but I'm running stock kernel (3.4.0-g6537a16) and stock JSS15Q. I do see random reboots as well, seems to be related to the screen going to sleep by itself but I can't reliably reproduce it.
Happens to me as well. Annoying.
I had this on stock locked so its nothing to do with bootloader or custom kernel/ROM.
Curious if a CM based ROM will affect this i.e. not stock JSS1Q based.
Is everybody facing this touchscreen issue? I am planning to get the new nexus 7 2nd Gen from canada. Is it something you can discover in the first week itself because the person who is bringing it will get the tab a week before her return.
If you're lucky it'll show up in that time period.
Others have gone 10 days.
Have them put off buying until the last second....
Same thing happening to me. The screen becomes unresponsive. Happens in the morning when the alarm is going off and have to reboot. I just updated to ElementalX 1.4 and hoping it'll fix it. I'm hoping Google comes out with an update soon because my screen sensitivity sucks sometimes. It's not registering my taps.
It doesn't lol it's either hardware or something in 4.3base
Sent from my C6603 using Tapatalk 4
My one, after 10 days, dead, the touch screen has no response at all
sent back to repair for over 1 week, still no news on when can return..
really bad feeling with this Nexus 7 (2013),
only Nexus 4/7/10 has no problem and still working well till now.
I faced this as well. But it solves itself.
Sent from my Nexus 7 using Tapatalk 4
I experienced the same issue here. However, I am not able to reboot as I am still running on stock and don't have the debug option enabled. Pushing the power bottun for some time only brings up a menu where i may chosse to shut down. As the touchscreen is not working, I cannot do anything. Unfortunately, my battery is almost completely charged. Any ideas how to reboot?
Coincidence: The touchscren went unresponsive after the alarm clock went off. Maybe there is a connection?
Here's hoping JSS15R fixes this (fat chance hah)
wintermute000 said:
Here's hoping JSS15R fixes this (fat chance hah)
Click to expand...
Click to collapse
I'm hoping too.
Sent from my Jedi Powered Samsung Galaxy Note II
Got this problem several time, i dont know when will google solve this problem abt multitouch & reboot. Just flash new update without root, lets see how device work with no root
Sent from my HTC One using Tapatalk 2
qlistenerp said:
I experienced the same issue here. However, I am not able to reboot as I am still running on stock and don't have the debug option enabled. Pushing the power bottun for some time only brings up a menu where i may chosse to shut down. As the touchscreen is not working, I cannot do anything. Unfortunately, my battery is almost completely charged. Any ideas how to reboot?
Click to expand...
Click to collapse
Hold down the power button until it reboots.
I had this issue exactly once since I got mine, and it's been fine since. I suspect it's a hardware or driver issue.
Androidnow said:
Is everybody facing this touchscreen issue? I am planning to get the new nexus 7 2nd Gen from canada. Is it something you can discover in the first week itself because the person who is bringing it will get the tab a week before her return.
Click to expand...
Click to collapse
I was looking to upgrade my OG N7 tablet to the current, but it sounds like the 2013 version has some frustrating bugs huh?...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Using stock rooted and never had these issues.
Do you guys think there may be an app causing this?
Sent from my Nexus 7 using xda app-developers app
I've read of this happening with the N2 as well...
My N900A on AT&T absolutely will not keep time. I've tried every combination of time settings (sync to network checked and unchecked, sync to timezone synced and unchecked) and my phone ends up several minutes behind every time I lock it, go to do something else and come back to it. This morning my alarm to wake up was 40 minutes late because the phone was inexplicably 40 minutes behind. I set the time manually according to my PC which runs ntpd and it STILL ends up slow. If I have it set to sync to network time, I can force it to resync by entering airplane mode and then disabling it. If that's my only work-around, I'd have to do dozens of times a day and my alarm in the morning would still be late.
Does anyone else's $750 toy have issues with this simple task that my microwave mastered years ago? I wish I could just run a proper NTP service on it and force it to sync every 60 seconds either to my router or to the pool.
Well first of all that is extremely weird, and if I had that issue with my Note3 I would go insane.
For now mine doesn't have this problem and the time keeping is spot on.
Check out "ClockSync"
https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync
But... Anyways, I think it might be better if you could exchange it for a new device... Maybe you got a lemon?
Best of luck!
Sent from my SM-N9005 using Tapatalk 2
CekMTL said:
Well first of all that is extremely weird, and if I had that issue with my Note3 I would go insane.
For now mine doesn't have this problem and the time keeping is spot on.
Check out "ClockSync"
https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync
But... Anyways, I think it might be better if you could exchange it for a new device... Maybe you got a lemon?
Best of luck!
Sent from my SM-N9005 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the input--Clocksync looks useful but root's required for automatic sync it says, and I have the securely locked, highly incapable (for now) AT&T variant. It should still prove useful for diagnostics--wondering if this is extreme drift or if it's being reset somehow to some totally incorrect time while the phone is locked. The clock stays accurate as long as I watch it.
The only way I could see it being hardware-related is if it had a battery for maintaining time like a CMOS battery or one in a game console, and I'd be shocked if any smartphone had this. It's a serious problem but I can't imagine it being exclusive to my particular model. A bug most people haven't run in to perhaps, but something software-related nonetheless.
Edit: Someone with a Note 2 with the same problem. Then again, after staring at ClockSync for some time, the local offset isn't changing significantly which suggests drift isn't the problem at all. What is I don't know, but it appears to only happen when I'm not using the phone.
You welcome and sorry to hear that...
Yes, for automatic mode the app needs root privilege.
Sent from my SM-N9005 using Tapatalk 2
CekMTL said:
You welcome and sorry to hear that...
Yes, for automatic mode the app needs root privilege.
Sent from my SM-N9005 using Tapatalk 2
Click to expand...
Click to collapse
Just confirmed it's drift.
When active, the phone keeps time well.
I just allowed it to sleep for 10 minutes then checked ClockSync: it had drifted 29 seconds behind. Totally unacceptable but I'm just going to use an old-fashioned alarm clock under the expectation that eventually I'll be able to root it and have it sync automatically, and frequently.
I agree that you should return it. Even if a hardware problem seems inconceivable, it is an obvious, unacceptable problem. And very likely the next one you get, for whatever reason will probably not do that. Or by changing phones and setting it all up again you may stumble upon the solution.
Sent from my SAMSUNG-SGH-I317
Thanks. I'm starting to consider getting a replacement as crazy as losing seconds while in sleep mode being a hardware issue is. I'm still curious as to if anyone else is experiencing this. With the Note 2 it seemed to be exclusively an AT&T problem, and it apparently was never fixed.