Database Users

G1 Doesnt Always Wake Up

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

Screen wont come on after Sleep

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

[Q] Last year I tossed the XV6800 into a drawer

I had been playing with it, trying to put an android system on it. When I was done, I flashed some other ROM onto it, not sure what...I recall getting frustrated with it when I tossed it into the drawer. Well, now I am wanting to set it up to simply run Slacker Radio and some other streaming media. I don't need it as a phone, just use it as a cheap media player.
So I dig it out, charge it, boot it mess with it for a minute and it reboots. Then I let it reboot and just looked at it. After a few minutes, it reboots....endless cycle. So I did a hard reset. It boots up to where I align the screen and then it goes to the today page, and immediately goes into some automatic customization thing....after which it reboots and reboots...
Okay, fine, I'll flash a new ROM (I found a light one here that has no carrier...perfect). At my current location all I have is a Windows 7 x64 laptop and I cannot get a driver anywhere that I've looked that will work. I can get the phone into bootloader mode, but that of course does me no good if the laptop won't recognize it. I've searched the forums as well as the web, and most of the Wiki for this phone is broke. I'm remembering perhaps why it ended up in a drawer.
Any ideas? Thanks.
Calis

I always flash using the micro sd card. Works great!

can you virtualize xp? then you should be able to see it in bootloader

Home button opens clock

Hi!
I just had a very weird bug. Suddenly when I pressed the home button the stock clock app (which I think is useless by the way) opened. When I pressed again the phone didn't switch to my home screen but stayed in the clock app.
When I tried to put the phone in standby and wake it up again my lock screen didn't show up, it was the stupid clock again.
I rebooted my phone and now everything is like it should be...
I'm running 2.3.4 (not rooted) with Launcher Pro.
Anyone else familiar with this problem?

I believe that you can set home button behavior in Launcher Pro. Not sure about the lock screen though.

I've had the same issue, always resolves itself though, especially after a reboot. Odd bug but doesn't occur enough to bother me.
But I agree the clock app seems largely useless, I have no wish to leave my phone screen on all night, and I can access alarm clock, gallery etc fine without.

I had this issue in January when I first got the phone, I guess on 2.3.1 or so. Anyways, the buttons did random things, and launching App A would result in App C launching instead, if you get what I mean. For example, I'd try to open Dolphin browser and Youtube would come up instead. I'm not sure why this occurred, and a simple restart fixed it. I wouldn't worry too much unless it keeps happening.
I only had it happen to me the one time.

I'm also experiencing this on my Nexus S, First the Car/Dock Mode appeared out of nowhere. It literally just launched itself while I was working at my desk! Now the home button pen up the clock App. Windows can't even detect the Nexus S now. No "you phone is plugged, mount it?" dialog box.
help!

romdroid said:
I'm also experiencing this on my Nexus S, First the Car/Dock Mode appeared out of nowhere. It literally just launched itself while I was working at my desk! Now the home button pen up the clock App. Windows can't even detect the Nexus S now. No "you phone is plugged, mount it?" dialog box.
help!
Click to expand...
Click to collapse
Okay so I think I may have found a solution. I set my Nexus S beside my iPad 2 last night before going bed. I think it may have been the caused of magnets. yup. magnets. So I tried contacting both together. The iPad 2 reacted and lit up its screen and voila the Nexus S home button now works as a HOME and not a CLOCK button! I know its a little weird, may just be a coincidence for all I know! But mine works fine now.
Try it and let us know if this works for you!

Let me resurrect a dead thread here with a new solution. I began building my roms from source on the NS4G and immediately this bug appeared in them. Funny thing is only on my phone none of the testers had this issue. I decided to overwrite desk clock with desk clock pro on the market for free, and it knocked out the bug, and I still have my alarms for work.

Random reboots

Has anyone else goten a ton of random reboots? It tends to happen when I am not using the dvice, and it's docked with the screen open and turned off. About every few hours, I see the EEE Pad restart. Even when I do not have it near me, I often come back to it only to find that AndChat/my other running programs have stopped running, which suggests the device reboot itself.

Hi,
I can't say that have seen lots of them, but last weekend as I was putting it down, as usual I switched off the screen by pressing the On/Off button... and it rebooted!?!??!?!
There is no way that I have held down the button for over 4 sec, and it should ask me whether to shut down first, and finally I have never seen an option on the TF for rebooting the device.
Any ideas guys?
rio

I have the same trouble I have noticed this today.
MP3 player on pause, tablet docked and open on my desk and after a while (like 5 or 10 min) I look at it and it's rebooting...
Quite strange.
Sounds like a power management trouble.
Would really love to know what's wrong with it.
Fandaor

If you have an sdcard plugged in the dock, you can try to remove it.
It worked for me.
more details -> http://forum.xda-developers.com/showthread.php?t=1120185

reppad said:
If you have an sdcard plugged in the dock, you can try to remove it.
It worked for me.
more details -> http://forum.xda-developers.com/showthread.php?t=1120185
Click to expand...
Click to collapse
What about that don't have dock & this happens?

Yes mine does it fairly often and I had never seen it happen undocked before until this weekend. I started undocking it at night due to the battery drain issue and both Sat and Sunday when I undocked it and sat the tablet aside, the tablet auto reboot. Previously I had seen this happen only when docked and sleeping and when the screen was open. Very annoying, wish they'd fix this.

I had it wake up a few times when it notified me I had mail..of those times...it rebooted on me.
Turning off background sync did the trick for me. It really is annoying..sometimes come from work and power level dropped dramatically...now when I go anywhere..airplane mode helps...pia but it gets the job done.