Related
Hey guys. Phone's been good for a long time. Ran cm6 and CM7 nightlys for a long time.. Tonight is real first big issue
WTH.. I already tried Wiping, and nandroiding.
Now booting with old builds, and new build #33 when the screen goes to sleep after initial boot. I can't get it back on no matter what. Needs a battery pull first. Odd.. I'm hoping something isn't wrong with my nexus one. It's really acting up now.. Basically the phone turns on and runs, but the minute it falls asleep it's done for. I can wake it with my Power button, but only the soft capacitive key's light up. No screen. but I can turn the screen/key's off and on with no problems with the button. Just the screen never comes on. but I can watch those softkey's do it. So the power button is working, but it could be going out. but seems to work every time.
I've officially wiped tonight. I tried a nandroid to a past build, I'm thinking I might have a hardware issue.
Any idea's. Screen wont come on after falling asleep. At all, requires a battery pull. (saw this in CM forum) guy said fix permissions fixed it. any idea's?
This might be happening because of the WiFi/BT connectivity bug. If you watch the logcat (or maybe it was in kmesg), you'll probably see lots of errors regarding mmc0.
On the other hand, anything that would get the CPU stuck at 100% throughtput, might do the same, and it might be some other bug.
Try to turn off WiFi and BT and do the same, see if it helps any.
Neither are enabled.. Now it is doing this For sure, completely everytime. I can pull battery and boot phone. Seems to run ok, can open apps. go to market. whatever. but when I go into settings I get Activity FC and it freaks out. I just tried to power off my phone. It's been at the Shutting Down spinning circle part for over 15 minutes. Is it possible the build it 512mb went bad and thats why it can't resume from standby, and stuff?
I'm still testing things. but I've completely wiped and had no luck. and also nandroided to a good working version also. Basically if my phone goes to sleep at all. I can't turn it back on. I have to pull battery.
Same thing here..
Screen will not wakeup from sleep unless I do a battery pull... Any updates?
Its been 1 year since nobody posted, anybody came up with an explanation/solution?
This Issue just appeared in my phone after two years of use.
-When the screen goes to sleep it won't be possible to switch it on again. Either via the power button, time up or proximity sensor.
-The phone and the touchscreen work as always, haptic feedback reveals my unlock slider is still active and the phone can recieve calls and notifications.
-Plugging in the phone or using another button won't revive the screen either.
-The backlight of the screen turns on, but the screen remains black.
-Only removing the battery and waiting at least 10 seconds before putting it in again will let the screen to come back.
-Shouldn't be a software problem as i have wiped several times everything that could be wiped and instaled diffrent Roms, even tested ICS.
-In my case, removing the microSD doesn't change anything.
-Swapping batteries also doesn't help.
Anybody out there with the same problem?
Programmed obsolescense on HTC?
http://forum.xda-developers.com/showpost.php?p=22625457&postcount=11
My N1 developed this issue just a few days ago- I'm looking for a solution as well. I have all of the symptoms you've described, apart from the backlight turning on as I have an AMOLED display. It's interesting to know that the backlight turns on, as it and the video signal are controlled separately (and impossible to distinguish on an AMOLED display).
I've reverted mine back to an official shipping ROM, something really ancient, and it still occurs.
Mine is also right around the 2 year mark. There are a handful of other threads on various forums which describe the same issue with the only resolution being sent in for servicing. I don't know whether it was the screen or the motherboard that was replaced, which would be very helpful to root causing the issue.
I'm not sure whether it's an issue with initializing the screen itself as it is is functional and can turn on after a battery pull/sitting for a few hours. I would guess it's something to do with a capacitor or similar, since the way to get the screen to work is a battery pull +time or to wait a long time before turning the screen back on.
It's a shame, too, because everything else is working just fine in my N1 and I think it is the perfect combination of a phone.
anomalyconcept said:
My N1 developed this issue just a few days ago- I'm looking for a solution as well. I have all of the symptoms you've described, apart from the backlight turning on as I have an AMOLED display. It's interesting to know that the backlight turns on, as it and the video signal are controlled separately (and impossible to distinguish on an AMOLED display).
I've reverted mine back to an official shipping ROM, something really ancient, and it still occurs.
Mine is also right around the 2 year mark. There are a handful of other threads on various forums which describe the same issue with the only resolution being sent in for servicing. I don't know whether it was the screen or the motherboard that was replaced, which would be very helpful to root causing the issue.
I'm not sure whether it's an issue with initializing the screen itself as it is is functional and can turn on after a battery pull/sitting for a few hours. I would guess it's something to do with a capacitor or similar, since the way to get the screen to work is a battery pull +time or to wait a long time before turning the screen back on.
It's a shame, too, because everything else is working just fine in my N1 and I think it is the perfect combination of a phone.
Click to expand...
Click to collapse
Format your SD-Card. It's known to fix it.
Thanks for your suggestion, but unfortunately it does not fix my issue.
I've tried different SD cards, repartitioned & formatted the card (previously had a sd-ext partition), and even running it without an SD card- all either won't turn the screen on during boot (starting with the battery out) or will fail to wake the screen.
My logs don't show the mmc0 errors which would indicate an issue with the card; it seems to be pretty normal for the screen turning on and off, just that the screen doesn't actually initialize and display anything.
About a week before the screen wake issue developed, I had a problem with the camera and gallery thinking that the SD card was not present. I eventually wiped and reloaded an older ROM and the problem went away.
I replaced the AMOLED screen and it now properly works. Since the screen was able to turn on by itself after an hour or so, I suspect it might be a capacitor or something that's gone bad on the flex cable itself. I'm not sure how much effort I'll spend tracing it down, but I might at least give it a shot.
Change the Screen
Had same issue with a Nexus 5. I changed the screen and it worked great.
xguntherc said:
Hey guys. Phone's been good for a long time. Ran cm6 and CM7 nightlys for a long time.. Tonight is real first big issue
WTH.. I already tried Wiping, and nandroiding.
Now booting with old builds, and new build #33 when the screen goes to sleep after initial boot. I can't get it back on no matter what. Needs a battery pull first. Odd.. I'm hoping something isn't wrong with my nexus one. It's really acting up now.. Basically the phone turns on and runs, but the minute it falls asleep it's done for. I can wake it with my Power button, but only the soft capacitive key's light up. No screen. but I can turn the screen/key's off and on with no problems with the button. Just the screen never comes on. but I can watch those softkey's do it. So the power button is working, but it could be going out. but seems to work every time.
I've officially wiped tonight. I tried a nandroid to a past build, I'm thinking I might have a hardware issue.
Any idea's. Screen wont come on after falling asleep. At all, requires a battery pull. (saw this in CM forum) guy said fix permissions fixed it. any idea's?
Click to expand...
Click to collapse
Hey everyone. Ive been searchnig around and cant find any information on this. I was told that the tablet enters a deep sleep mode to save battery. Ive noticed that while im playing music and the tablet screen times out, after the song finishes it never moves on to the next song. Also when it wakes up the screen is unresponsive for a few seconds. I have tried a few roms and thiese issues seem to be on all of them. Anyone else having this? Any fixes?
i have a similar issue where if the screen is off for longer than about 5 minutes, the wifi disconnects. its not really a problem since it jumps back on pretty quickly, i'm more wondering if anybody else has this. and sometimes, if the screen is off longer than a day or so, it worn't wake up - i have to powercycle it...
simonsgray said:
i have a similar issue where if the screen is off for longer than about 5 minutes, the wifi disconnects. its not really a problem since it jumps back on pretty quickly, i'm more wondering if anybody else has this. and sometimes, if the screen is off longer than a day or so, it worn't wake up - i have to powercycle it...
Click to expand...
Click to collapse
Your wifi is disconnecting due to your wifi policy in settings.
As for the "deep sleep", I've seen this once or twice. Seems to be something endemic to the Tegra chipset itself, as it gets reported on all devices.
the screen not responding i can put up with if i have to. but i have never had these issues with 3.0.1 stock. im not downplaying any of the amazing roms out there. because i know this is an android related bug. i was told i should try another music player as some have a workaround for this issue. but google music on the tablet is the best music player imo. anyone know of a fix? can someone else also confirm that the music issue is present on their device?
Hi,
Same things here : when the screen is off, the player never goes to the next song.
Any fix ?
Siso
I've noticed this deep sleep thing a few times with HC3.1. Can't seem to wake it backup up once it's in it. Don't know about the song issue with it.
Normally when the screen goes off, i just hit the power button and it's ready for me to do my unlock pattern. But when it goes into this deep sleep, it refuses to wake up. I have to hold the power button down for about 10 seconds (no vibration noted). let go, then hold it down for about 8 seconds until I feel the "boot up" vibration.
It hasn't bothered me too much yet. It doesn't seem to do it very often. I guess I use it often enough to keep it from doing it.
simonsgray said:
i have a similar issue where if the screen is off for longer than about 5 minutes, the wifi disconnects. its not really a problem since it jumps back on pretty quickly, i'm more wondering if anybody else has this. and sometimes, if the screen is off longer than a day or so, it worn't wake up - i have to powercycle it...
Click to expand...
Click to collapse
Euclid's Brother said:
I've noticed this deep sleep thing a few times with HC3.1. Can't seem to wake it backup up once it's in it. Don't know about the song issue with it.
Normally when the screen goes off, i just hit the power button and it's ready for me to do my unlock pattern. But when it goes into this deep sleep, it refuses to wake up. I have to hold the power button down for about 10 seconds (no vibration noted). let go, then hold it down for about 8 seconds until I feel the "boot up" vibration.
It hasn't bothered me too much yet. It doesn't seem to do it very often. I guess I use it often enough to keep it from doing it.
Click to expand...
Click to collapse
Yeah, that's what i was trying to describe in the second half of my post. Much better said here, anyone else experiencing this annoying if non-frequent issue?
yes, i have a few times, on 3.01 and 3.1
both of my issues where solved in android 3.2... i am once again happy
Can you all possible update your posts with what build of 3.1 you're using?
I am in the US and was on .08 and my sleep issues from 3.0.1 were completely resolved so I'm trying to find out if it still exists on foreign builds of the ROM.
If you're on the U.S version - I know you don't want to hear this, but you might want to try a factory reset. There could be some settings 'stuck' in the system. A file that didn't get overwritten which was supposed to by the update, etc. Anything can happen. It's like going from 1 version of Linux/Windows to the next using an upgrade when you don't factory reset.
Alternatively, you could also wait for the .10 version being seeded right now to see if that helps. But as I mentioned, I didn't have the issue on my tablet so it's likely some folks are experiencing a software glitch.
Any solution to this? Any good players that would work as they should?
M-XXXX said:
Any solution to this? Any good players that would work as they should?
Click to expand...
Click to collapse
it appears the issue was with android 3.1 itself. try a 3.2 rom. all of the issues are gone
Hi,
Since late RC versions of Swiftdroid I have observed that sometimes when I put phone to sleep (HANG UP button) it immediately wakes up, as if button was pressed twice. It doesn't happen every time and it's actually hard to predict when it would. *Maybe* it has something to do with that sometimes the phone is slow to wake up and I have to press the PICK UP button again. Maybe.
As I mentioned, I started to notice this behaviour quite recently. I'm using Swiftdroid since v2 M4 but those symptoms took my attention about RC3 or RC2.
Anyone else observed something like that?
me some times but after awhile its ok maybe you should make a clean install of the rom??
Usually I clean caches and stuff. But incidentally I'm about to make full-wipe reinstall. I'm just waiting until RC5 comes out.
Your button probably is pressed twice, because it's busted. Apparently the GT540 has some issues that show after some time. That's the reason I sent my phone to be repaired under warranty. I could be wrong, of course, but keep that in mind.
I don't rule out this possibility. Though at this moment I'm not too convinced. If the button were the problem, I'd expect it to happen in more consistent way. Here, it just happens only once in a while.
Bug
This happens to me too. It's some problem with the power button. It happened to me always.
Hey guys,
I did some searching around the web regarding the issue with my N7 and couldn't find anything, so my apologizes if this has been asked before.
The issue I am having is, when my N7 has been sleeping for a while, (on or off charger) it will get "stuck". It won't wake up when I push the power button (or at least the screen won't illuminate). I can hard reset it by holding power+volup+voldown but that gets kinda irritating when I just want to quickly use it and put it away.
It doesn't appear to be causing a battery drain, it's almost like it's a sleep and just won't wake up. I am currently using CNA 3.6.6 with the latest franco kernel. I do not have a case at the moment (it's in the mail). I will be attempting a different ROM tonight to see if it retains the problem.
I have a Galaxy Nexus and sometimes it will fail to accept touch input, but the power/volume buttons have always still worked.
Any ideas?
EDIT: Can't find the delete button, but found a similar posting here: http://forum.xda-developers.com/showthread.php?p=32819135#post32819135
Try disabling auto-brightness and see if that stops the problem recurring.
Sent from my Nexus 7
Thanks
I saw that in the previous post, it appears to have worked. Any idea if there is as fix in the works?
Occasionally my phone will just go crazy, screen will get all jittery,touching on a menu doesn't work ,it mainly happens on noughat stock and custom ROMs.,random apps popping up.any experience anything like that?a simple reboot fixes the problem.
russ722 said:
Occasionally my phone will just go crazy, screen will get all jittery,touching on a menu doesn't work ,it mainly happens on noughat stock and custom ROMs.,random apps popping up.any experience anything like that?a simple reboot fixes the problem.
Click to expand...
Click to collapse
It's an inherent issue with some displays present on the Moto G4. It most often happens when you charge your phone. Too much current builds into the frame of the display and you get weird ghost and jitter touches.
No way around it unless you send it in, and even then it may be only a temporary fix.
I also face this issue. Unable to find solid solution for this. Finally i decied to go for custom rom like RR and Invicta. This still comes occasionally(when Heats too much during phone charging)
russ722 said:
Occasionally my phone will just go crazy, screen will get all jittery,touching on a menu doesn't work ,it mainly happens on noughat stock and custom ROMs.,random apps popping up.any experience anything like that?a simple reboot fixes the problem.
Click to expand...
Click to collapse
On my phone this happens while not charging. Seems to happen about one out of every 3 times the phone is unlocked using the fingerprint sensor. Locking the screen and unlocking via a pin seems to be a reliable way of getting past the issue. Though occasionally it happens on the pin entry screen before it the pin has been entered. Needless to say, it IS annoying.
Same problem which is fixed.
I had this problem with the factory firmware too, intermittent bouts of the phone going crazy with phantom touches on my Moto G4. I sent it to Motorola/Lenovo after the supplier gave me their phone number and they did find the problem and fix it. Now I can play graphic intensive games even during fast charge and the phone is awesome for once. : )
Please note they will fix it for free if in warranty and bootloader not yet modified.
Pressing power button to turn off the display and then pressing power button again to turn the display back on will provide temporary relief from jittery screen. I noticed that the jittery screen has twice subsided over time but came back twice immediately after OS upgrade so blaming the problem on charging, or hardware doesn't seem accurate.
Updated 5/20/2018
As a last ditch effort prior to buying a replacement phone I deleted all apps I installed, reset phone and reinstalled fresh copies of most if the apps I needed.
I don't recall every thing I did but my focus was to delete everything I could and then reset phone back to factory state. After reinstalling, my jittery problem went away and has not returned. Your millage may very, so no promises. Phil
. I have touch screen issue(ghost touch) but this time not screen burn issue.. Now there is in winter.. I have checked battery temperature with ex kernel manager. When i go outside in fog or cool weather and when battery temprature goes to less than 20 degree Celsius phone gonna mad..back key home button automatically pressed..Is there any solution? Without going service center And fix battery battery temperature to 25 degree.?
phone going crazy
Hi,
I am having the same exact problem. I have observed that Google Assistant is intruding because each time this happens, Google Assistant is trying to run. Reboot is a temporary fix but the problem persists. I have removed most of the third party apps just to see if anything changes but it did not work.
This is not something that was happening from the start. I have the phone for about 2 months put the problem only started a couple weeks ago. I would love to hear if there is a solution and what. Thanks
Sadly, but compared to the issues visible indoors, in outdoors this Lenovo gift turns complete crap:
youtu.be/dTcHclVEfCg
"Lenovo Moto Z2 Force touchscreen gets completely unusable when getting outdoors! The video is made at about 0 degrees Celsius. So it takes about 30 sec from getting MotoZ2 Frc to sleep with pwr btn (and wakeing up back) to see the touchscreen goes crazy. At -10C, it takes ~5 sec. At +15-20C, after several min it becomes unresponsive and have to use pwr button to recover.
Lenovo, what you have done to Motorola ?!!"
Can it be fixed somehow with changing the upper protective part? I have seen comments that the touchscreen can stop working completely, if peel off the cover part..