Related
Does anyone elses G1 not wake up when Menu is pressed? Sometimes I have to press it like 6 times before the phone wakes up, does anyone know why?
Mine does this as well. I just thought it was learning from it's owner (I take more than 5-6 pokes to wake me up too).
My only guess is that something is running in the background in order to slow it down and the number of presses has little to do with it.
momentarylapseofreason said:
Mine does this as well. I just thought it was learning from it's owner (I take more than 5-6 pokes to wake me up too).
My only guess is that something is running in the background in order to slow it down and the number of presses has little to do with it.
Click to expand...
Click to collapse
Yea, i was thinkin the same, i should try runnin a ton of apps and find out if [email protected] the problem
mine does the same things sometimes. gets annoying at times. usually i just open and close the keyboard
Mine recently started this, it must be something we downloaded, plus I have the following problems too, they all started at the same time:
1) When someone calls, the screen stay blank for a while so the phone rings but the screen is off so I dont see whos calling
2) The background keeps changing back to the original blue picture thing
3) The WiFi keeps turning off and drians the battery, nothing I do stops it from turning on. I have all sorts of software running, I even ask Locale to turn it off if its between 12.01am to 11pm and still WiFi keeps poping up.
4) Battery drains FAST lately.
I uninstalled a long list of software and problem is not solved.
Brooklynite!
brooklynite said:
Mine recently started this, it must be something we downloaded, plus I have the following problems too, they all started at the same time:
1) When someone calls, the screen stay blank for a while so the phone rings but the screen is off so I dont see whos calling
2) The background keeps changing back to the original blue picture thing
3) The WiFi keeps turning off and drians the battery, nothing I do stops it from turning on. I have all sorts of software running, I even ask Locale to turn it off if its between 12.01am to 11pm and still WiFi keeps poping up.
4) Battery drains FAST lately.
I uninstalled a long list of software and problem is not solved.
Brooklynite!
Click to expand...
Click to collapse
Shop Savvy?
I also started having the wake up problem and quicker then normal battery drain. I have an ADP1 phone which I updated to 1.1 a few days before noticing issue
I think that the theory of something sucking clock cycles is a good one. I noticed my CPU Usage (when nothing was running other then System Monitor) went from 0-40% to 20-70%.
I couldn't be bothered with the finer points of troubleshooting, so I took the thermo-nuclear approach and did a factory wipe.
Just before the mystery CPU cycle and wake up issue, I hadn't installed any new apps, BUT I did update a bunch of existing apps. After the factory wipe, I left off installing the following list:
Watts
StreamFurious
DroidFTP
Telnet
e-VoiceRecorder
VoiceRecorder
Constitution
Barcode Scanner
Astro
RingDroid
SlovoEd Classic English Dictionary
Things are fine now.
both of my g1's do this, and have done this out of the box, anyone turn off there screen with the keyboard out, and then close the screen and the screen comes back on with the lock screen up and then having to turn the screen back off? annoying
try the swapper app?
or turn phone off and back on, it might becuase you are usingahome or openhome or dxtop or sweeterhome, these app may slow down the interface a bit, try downloading droid sans tweak lite and fool around with that..
goodluck i also get this sometimes
brooklynite said:
Mine recently started this, it must be something we downloaded, plus I have the following problems too, they all started at the same time:
1) When someone calls, the screen stay blank for a while so the phone rings but the screen is off so I dont see whos calling
2) The background keeps changing back to the original blue picture thing
3) The WiFi keeps turning off and drians the battery, nothing I do stops it from turning on. I have all sorts of software running, I even ask Locale to turn it off if its between 12.01am to 11pm and still WiFi keeps poping up.
4) Battery drains FAST lately.
I uninstalled a long list of software and problem is not solved.
Brooklynite!
Click to expand...
Click to collapse
I'm having same issue as the OP and issued #1, 3 and 4 from the above post.
Hmm, im not experiencing any of the above posted issues, it may be a particular app that u have installed. I only have the wakeup issue sometimes, most likely when the phone is running slow from the browser or another memory draining app, but no app in particular.
Hmm, when mine fails to wake up, I never waited long enough for it to come back, just reseated the battery for a reboot.
Of the other problems, I have the "screen-black-for-a-few-before-caller-picture-shows-up" issue.
JayBachatero said:
I'm having same issue as the OP and issued #1, 3 and 4 from the above post.
Click to expand...
Click to collapse
what firmware do you have?
btw, dont count on Locale to turn off your stuff all the time, its not very accurate imo, at times its great, but thanks to the crappy g1 battery, they have a choice, constantly check time/location/.ect and drain the battery in a hour flat, or periodically check it and reduce battery drain, do you have any wifi programs that keep wifi on when phone sleeps (such as wifi lock and so on)? if so use the program on the market that writes up a log of its actions and see if its acting up
as for #1 (sorry im unorganized) my phone does that too, i believe its because i have 2 programs that run when the phone rings, let alone im sure locale is checking to see who is coming since thats a condition, which would make 3, and then i have a mp3 that plays when the phone rings, and i have a class 4 sd card (i know, i know), the way that programs work is that it has to go line by line of the code, if it is slowed down, or it has to execute other items before continuing that are slow to execute, than everything has a delay, but yeah from time to time i have this issue, phoneplus was a program that made me miss a few calls (1/4th of the time)
i think 3 and 4 are directly related, could be wrong
I was having the same problem right after I installed the app "Contact Owner"
No amount of reboots fixed the problem. Uninstalled and everything was back to normal.
@wootroot - I have stock RC30. Haven't rooted yet.
JayBachatero said:
@wootroot - I have stock RC30. Haven't rooted yet.
Click to expand...
Click to collapse
consider upgrading to the rc33 ota update yet? i had better battery life (and my battery didnt get as hot) when i used rc33
also, if youve had your phone since it first came out (rc19 i believe) and your battery used to get very hot, you might of damaged some of the cells (especially of the battery has expanded), if this is the case simply call tmobile and tell them that your noticing even after wiping the phone that your battery life is lasting shorter and shorted, even with out any programs installed from the market, i even went as far as to say that i made sure wifi was off, only 2g was on, gps was off, screen was dimmed, timeout set at 30 secs, and im still only getting a hour of life (none of which is true but it got through all the "well how about trying this and calling back if you still have a problem" bs, with the ota rc33 and the new battery, i noticed a pretty good difference
I have a modified version of this "doesnt always wake up". The phone is less than 24 hours old, it was a refurb they sent me for the last one that went dead. I used it with the rc33 it came with and found the problem, then figured it was hosed so i rooted and installed 3 of the versions of cupcake (The Dude, JF, and Haykuro) to see if they all had the issue- they do. Here is a video, hope you can see the attempted keypresses. There will be lines that appear, like the screen is broke..then, they will go away. Sometimes it takes 5 minutes to get the phone to turn on, however if I leave it on (never goes to sleep) it works flawlessly.
http://www.youtube.com/watch?v=ecQo2Ly2WUM
I get this all the time also...
Uninstalling dxTop doesn't change anything for me...it still acts the same...
I also get the problem that when someone calls me the screen stays blank for about 5 seconds and I can't tell who calling...
wake up issue
I am experiencing the same problem, with a brand new warranty replaced G1, what happens is when the phone goes to sleep it completely locks up, when I try to wake it up via menu, it does not wake. Plugging the phone in and trying ddms or adb does not work, ddms shows the phone as offline, also the device seems to get really hot when this happens, sometimes Call + Menu + Power resets it, and sometimes I have to pull the battery.
I think this may have to do with wifi turned on. Because when the screen goes off your phone switches wifi off and goes to 3G as default setting.
I think we should try leaving wifi on all the time and see if that solves the issue, im about to try that now.
It seems this is a known issue over at tmo forums
A couple questions:
When this happens to you guys is wifi enabled and connected when the phone is shut off?
What Rom, SPL, and Radio is installed?
I noticed this didnt happen to me until I enabled wifi, maybe I didnt wait long enough because its completely random, please send back your results
defcon
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
Anyone else having this problem,
Sometimes when I get to unlock screen and swipe across it doesnt react to it the first time and I have to do it again.
Yes. Many, many times. I resolved this by downloading an app that gets rid of the bar from me, so now I press home. Unfortunately this means I have no security on my phone. Yay!
Yea; I mean how much of a problem is it though? I guess it takes a second sometomes to initialize the scanner.
Rooted/ROM Captivate (For Sale)
Rooted Atrix
I am not talking about the finger printer reader, also at work I have about 1 second to check phone, so it just gets annoying when I spend that one second trying to get passed the lock screen
Oh! Yea that happens to me sometimes as well; I hate it.
It also "confuses" me when I slide it but there's nothing really being slid you know? Just the color.
Rooted/ROM Captivate (For Sale)
Rooted Atrix
Never had a problem with slide to unlock.
The finger scanner though, you have to remember at what angle and what direction you scanned in. Finding a comfortable swipe is better than trying to get a correct register. It's kind of like practicing golf swings.
I didn't have this issue till I did a factory reset, now the lock screen is soo slow.
Sent from my MB860 using XDA App
Was going to say same thing. I did my 1.5.7 update a little bit ago and really having seconds from when I hit the power button until my screen wakes up. I can actually hit the button and scan my finger before it comes on. Anyone else having this type of slowdown?
Sorry for bringing up a old thread but kinda based on what I am dealing with.
My Atrix keeps waking itself up after putting it to sleep and STAYING on...
It is killing the battery life. This has only happened since the update...
Solutions?
I had that once before on my old build. Not sure what did it but it did end up stopping after a little bit myself. I think it was an app that was doing it
Spinstorm said:
My Atrix keeps waking itself up after putting it to sleep and STAYING on...
It is killing the battery life. This has only happened since the update...
Solutions?
Click to expand...
Click to collapse
I would check to see if any apps are causing your phone to wake up; I remember this happening on my Captivate last year. I don't remember what the problem was but I knew it stopped after a week or so.
Something I have noticed with 1.5.7 the supposed fix to allow the phone to sleep while charging was a sinple change in the setting under development. I also have noticed when you place the phone on the charger if the lock screen is up and you are using the fingerprint scanner. you can never ( or should I say rarely) get it to stay asleep as it keeps reading the button press as a finger swipe. The only solution I have found is to make the the phone is on the home screen and press the button to make it sleep. then it stays asleep
I have had things like this happen to me, for a while I was using GingerBlur and I thought thats why the phone was glitching but when I went back to stock I had it glitch like this a few times on me also... I almost feel like my Atrix is running a beta...
I have not had any issues with the slider itself but i have observed this for a few days now. When i slide to unlock the screen, it goes directly to the contacts page and just freezes for a while. no other buttons work except hitting the home button and then ot works as usual. Any pointers? i recently rooted my phone and flashed it with the Alien rom [build #4 - 2.6.32.9]
ALSO, the screen would not turn on when i get on a call and cover the proximity sensor, Only way to come back is to reboot it.I dont know whats going on with my phone but lately the knock on has gotten worse and it's pissing me off. Past week, only way to turn on screen is with the power button and when it wakes up its only for a few seconds, then relocks itself. Knock on will work randomly when it feels like it but really its only worked like 10% of the time the past week. I've checked for any new apps, removed them even though they were official. I dont get it. I have xposed and g2 xposed. Uninstall them. problem still happening. I'm on Rooted Stock 11a.
anybody else experience this?
Amazingly, I googled the phone call screen off problem and found a workaround until it really dies I guess.
Make pressure at the top of the phone by the spaker,sensors area, squeeze it there and poof its working great again. So weird, somehow the inside gets apart from itself? definitely a hardware problem that seems pretty popular with this phone.
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..