Database Users

Eris problems I've been having

The reason i put this in the developers section is because I'm sure they've run into these issues.
I am currently running the new white widow "Phoenix". I am OC'ing at 710.
ISSUES:
Screen wont wake. I have to pull the battery and reboot.
If I tap the phone on a table on the top left corner of the device (lightly) it shuts off.
Sometimes I go to wake the screen and it reboots. Somehow having turned off.
I hit the home button and all I see is the status bar and a blank rest of screen.
I've tried froyo roms as well as a couple 2.1s and all of these have occurred on each rom. Help? Thanks in advance.
Sent from my Eris using XDA App

QUOTE:
If I tap the phone on a table on the top left corner of the device (lightly) it shuts off.
based upon that statement, personally, i think your phone (hardware) is jacked. i've used just about EVERY ROM in existence... never had any of the issues you described.
i've even dropped my phone on concrete, tables, etc... no shut-offs, etc.
probably not what you want to hear, but i'd probably flash a fairly stock ROM, see if still happens. if so, probably time to get a refurb/warranty replacement!

agentofchaos said:
The reason i put this in the developers section is because I'm sure they've run into these issues.
I am currently running the new white widow "Phoenix". I am OC'ing at 710.
ISSUES:
Screen wont wake. I have to pull the battery and reboot.
If I tap the phone on a table on the top left corner of the device (lightly) it shuts off.
Sometimes I go to wake the screen and it reboots. Somehow having turned off.
I hit the home button and all I see is the status bar and a blank rest of screen.
I've tried froyo roms as well as a couple 2.1s and all of these have occurred on each rom. Help? Thanks in advance.
Sent from my Eris using XDA App
Click to expand...
Click to collapse
WHY WOULDN'T YOU POST THIS IN ITS OWN THREAD? WW has its own thread ask the developer of the rom, this is getting out of hand. it is a specific issue with a specific rom please help keep the forum clean.
sorry for snapping i know your new but next time please, this should be kept to its own thread.
XDA-Developers.

Sjflowerhorn said:
WHY WOULDN'T YOU POST THIS IN ITS OWN THREAD? WW has its own thread ask the developer of the rom, this is getting out of hand. it is a specific issue with a specific rom please help keep the forum clean.
sorry for snapping i know your new but next time please, this should be kept to its own thread.
XDA-Developers.
Click to expand...
Click to collapse
Sorry dude (I think your a dude, anyway) but read the whole post from the top he said he tried it on many roms and it happen in all of them so its not rom specific

if this is happening on multiple roms, and with the issue you described with the phone acting up if it gets tapped, my advice would be to 1 try a stock rom and see if it still happens and 2 if it does call vzw or the insurance company and get another phone. because to me also it sounds as if its a hardware problem, not a software (rom) problem

what really sucks is that I just got a replacement because the trackball broke :/. I'm think it might be the extended battery I have shaking loose a little. That would do it I suppose. Thanks for the replies. And I apologize to the user who wants the forum clean. Not only did I try it on multiple roms but I knew I'd get more replies if I posted it here.
Sent from my Eris using XDA App

Also I've heard of others having the screen wake bug. Where it doesn't turn on the lockscreen at all. Is there something I could flash to fix it?
Sent from my Eris using XDA App

I just put in the original battery and and back. So far no random shutting off or shutting off when it taps something hard. Will update.
Sent from my Eris using XDA App

Sleep of death (SOD)

I have had a half a dozen totally stock mytouch 4gs that will run perfectly fine but about 4-6 times a day I will pull the phone out of my pocket and it will be totally unresponsive to the power and trackpad buttons. No led no button lights or anything. To get it back to normal I have to pull the battery and reboot. I just loaded virtuous fusion 1.0.6 and the problem persists.
I've tried factory resets, formatting the sd card, new sim card, turning off screen animations, clocking the cpu higher when the screen is off, and running with no apps and no google account set and none of that has helped. The only common thing between all the phones is my number and google account and it still happened after a factory reset without signing into google.
Has anyone else had this issue? Am I just extremely unlucky?
I just loaded loaded the 26.08.04.30 radio we'll see if that helps...

Have you run a logcat?
Sent from my HTC Glacier using XDA App

kimbernator said:
Have you run a logcat?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
No I'm kind of a noob at this stuff. I'm not familiar with logcat at all. Where should I start?

i've had this problem as well, usually only once a day tho, the led does still work and the buttons do light up as well button the screen just wont turn back on unless the battery is pulled
i posted this in another similar thread but still no answer, i want to know whats wrong! lol

I have seen this but not that bad, are you checking your phone constantly cause thats what happens to me. Lock, unlock, then the lcd doesn't light up but led, and buttons do, try loading the newest radio 26.09
Sent from my 3.0 sense Glacier

andrewdoessuck said:
I have seen this but not that bad, are you checking your phone constantly cause thats what happens to me. Lock, unlock, then the lcd doesn't light up but led, and buttons do, try loading the newest radio 26.09
Sent from my 3.0 sense Glacier
Click to expand...
Click to collapse
This happened to me once,just battery pulled & all is well.. I wanna knw what causes this too??
Mytouch 4g-white
Permrooted s-off
Root Method-gfree
CWR-3.0.2.4
Rom-Royalginger v2.1
Kernel-Ckisgen~smartass~v1.2

I feel like if it happened on 6 phones that often, it must be the user...

It also happened to me all the time, but ONLY on gorilla sense HD rom .....
Sent from my HTC Glacier using XDA App

lowandbehold said:
I feel like if it happened on 6 phones that often, it must be the user...
Click to expand...
Click to collapse
At one point I thought that too. I thought "theres no way they sent me SIX dud phones in a row." So I wiped my sd card and did a factory reset without signing into google or anything and loaded no apps and it still did it.
I noticed though that when I pull my sim card out and use it in my other mytouch 4g(which works perfectly fine with that sim) this phone will not show this issue without the sim in it. So I started thinking it might be the radio as I've tried a different sim card and that didn't work.
This is my first day with the new radio so I will report back with my results.

Well that didn't work. It just SODed on me twice in a half an hour.
Should I try flashing the other radios or CM7 or something? I'm wary of flashing too much as I have the dreaded M4G2E emmc serial.

i also have the latest radio but still get this problem every once in a while, i almost wanna say i started noticing this after i started flashing different radios tho, first the 26.08.04.30 radio then the newest 26.09.04.26 radio

smatthew45 said:
i also have the latest radio but still get this problem every once in a while, i almost wanna say i started noticing this after i started flashing different radios tho, first the 26.08.04.30 radio then the newest 26.09.04.26 radio
Click to expand...
Click to collapse
Maybe I'll try the oldest one then.

I noticed today that if my phone becomes unresponsive and I plug it in the charging light will come on and I can boot the phone without pulling the battery. It does a full boot too not a fastboot. For some reason though if I do this it will SOD on me way quicker than usual.

johnsmith970 said:
Well that didn't work. It just SODed on me twice in a half an hour.
Should I try flashing the other radios or CM7 or something? I'm wary of flashing too much as I have the dreaded M4G2E emmc serial.
Click to expand...
Click to collapse
I think that is the issue your EMMC. I had this problem with my phone, then one time it happened when I pulled the battery it bootlooped and CWR showed me that lovely error... be careful. Wish we would know if your other phones had the M4G2E as well. My current phone has the other chip and I have never once had the SOD like I did on my old chip.

[Q] Unique Nexus One power up issue

Hi Moderators,
Please feel to delete or move this thread, if you find it repetitive. Apologies for starting a new thread.
Hi All,
I have a unique issue with my Nexus one. Sometimes it fails to reboot and then does not start even pressing power button multiple times. Sometimes it starts but then screen does not come up after the display time expires. Whenever it is ON, power button works good, ALWAYS. When it goes into the weird state, I am not able to put it in recovery mode as well. Whenever, I am able to put it in recovery mode, power button ALWYAS works good. Also I have seen that sometimes, even after boot-up it is not able to detect the SD card even when battery is at around 30%.
I have tried all the methods I could find related to "Nexus One power issue" here on XDA as well as via Google search. Sometimes the "remove battery multiple times while plugged into AC" works but at times it also does not help either.
I visited the local HTC service station. The guy there showed me that the small strip of Litmus paper on battery and phone has turned reddish. For normal phone it should be white. This indicates that phone was in contact with something acidic in nature. I tried swapping batteries with my friends and colleagues, but no luck. I have replaced the power button strip of my phone which seems to be trouble some as per the discussions here.
I have tried CM7.x, RCADS, MM super hybrid, eVil's desire port and of course stock 2.3.x ROMs. All seem to have similar issue one or another time. I have also tried Amon_RA's 2.2.0 and 2.2.1. Somebody told me to try with CM6.1 which I will try now if I am able to boot it in recovery.
My warranty is long gone, BTW. Also I bought my phone from US and it is not possible for me to go there again in near future. This issue cropped up approximately 3/4 weeks back. I have default radio.
Having said that, does anybody know what could be the issue with my phone? Has anyone faced such an issue?

chota_shivaji said:
Hi Moderators,
Please feel to delete or move this thread, if you find it repetitive. Apologies for starting a new thread.
Hi All,
I have a unique issue with my Nexus one. Sometimes it fails to reboot and then does not start even pressing power button multiple times. Sometimes it starts but then screen does not come up after the display time expires. Whenever it is ON, power button works good, ALWAYS. When it goes into the weird state, I am not able to put it in recovery mode as well. Whenever, I am able to put it in recovery mode, power button ALWYAS works good. Also I have seen that sometimes, even after boot-up it is not able to detect the SD card even when battery is at around 30%.
I have tried all the methods I could find related to "Nexus One power issue" here on XDA as well as via Google search. Sometimes the "remove battery multiple times while plugged into AC" works but at times it also does not help either.
I visited the local HTC service station. The guy there showed me that the small strip of Litmus paper on battery and phone has turned reddish. For normal phone it should be white. This indicates that phone was in contact with something acidic in nature. I tried swapping batteries with my friends and colleagues, but no luck. I have replaced the power button strip of my phone which seems to be trouble some as per the discussions here.
I have tried CM7.x, RCADS, MM super hybrid, eVil's desire port and of course stock 2.3.x ROMs. All seem to have similar issue one or another time. I have also tried Amon_RA's 2.2.0 and 2.2.1. Somebody told me to try with CM6.1 which I will try now if I am able to boot it in recovery.
My warranty is long gone, BTW. Also I bought my phone from US and it is not possible for me to go there again in near future. This issue cropped up approximately 3/4 weeks back. I have default radio.
Having said that, does anybody know what could be the issue with my phone? Has anyone faced such an issue?
Click to expand...
Click to collapse
Hi Moderators,
Apologies for posting this thread in this sub-forum. I forgot that question threads should be in Q&A section. Having said that, if its not too much to ask, can you please move this thread to Nexus One's Q&A sub-forum?

Just update d firmware wit any of the ones which r available here...m pretty sure this ll solve yor issue as I think its related to software not hardware...
Sent from my GT-S5830 using XDA Premium App

Firmware update lol seriously ...try updating your radio to the 5.08 or 5.12 then flashing a stock rom and go from there
shreyasvb said:
Just update d firmware wit any of the ones which r available here...m pretty sure this ll solve yor issue as I think its related to software not hardware..
Sent from my GT-S5830 using XDA Premium App
Click to expand...
Click to collapse
Sent from my Nexus One using XDA App

b1337 said:
Firmware update lol seriously ...try updating your radio to the 5.08 or 5.12 then flashing a stock rom and go from there
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Thanks a lot for your suggestions. I somehow manage to put my Nexus one in recovery mode by pressing power + volume down buttons multiple times. Then flashed the radio 5.08 on it. I already have CM 7.x ROM.
With this combination, my phone is working good so far. The power down issue would have reoccured by now. So it looks like my issue is resolved. I will use it for 24 more hours and come back if I am able to hit the power down issue again.
Once again thanks for the suggestions. As usual, XDA rocks. Had been experiencing this since good old Windows Mobile + HTC Touch days :-D.

chota_shivaji said:
Thanks a lot for your suggestions. I somehow manage to put my Nexus one in recovery mode by pressing power + volume down buttons multiple times. Then flashed the radio 5.08 on it. I already have CM 7.x ROM.
With this combination, my phone is working good so far. The power down issue would have reoccured by now. So it looks like my issue is resolved. I will use it for 24 more hours and come back if I am able to hit the power down issue again.
Once again thanks for the suggestions. As usual, XDA rocks. Had been experiencing this since good old Windows Mobile + HTC Touch days :-D.
Click to expand...
Click to collapse
I tested my Nexus one for past approx ~36 hours. In this time, I was hit by the issue mentioned in this thread twice.
Out of those 2, 1 was probably caused due to a soft reboot as I was able to get some output from cat /proc/last_kmsg but could not save it for sharing. The other one did not had last_kmsg entry so I am not sure what caused the phone to go haywire. The battery charge was ~30% when I booted it next time.
Now, I am on CM 7.x stable + 5.08 radio + Amon_Ra' 2.0.0 recovery and I explicitly have wiped the cache and Dalvik-cache via recovery. Since then, phone seems to be working OK. I will keep this thread updated if I am again able to get into the "Not able to power-on with power button" issue.

[Q] CM7: Wireless off on boot - how to fix?

I searched and found nothing like this.
When I boot my Nook Color, running Cyanogenmod 7, any recent nightly, wireless is off, even though it was on before booting.
I open Notifications, tap the wireless, it turns on and works fine. I've checked, airplane mode is not on.
Updating to newer nightlies doesn't work. I'm pretty sure this used to work. My glacier doesn't have this behavior.
Any thoughts on how to fix this so the wireless state is retained over boots?

I have the same thing but I actually prefer it this way since I use it so much for reading.

I think those lately night builds have screwed up a few things such wireless OFF on boot. Another itchy part (for me) is the Terminal Emulator somehow got blue background and when "exit" command, it doesn't exit but I must force it off under Managing Applications.

votinh said:
I think those lately night builds have screwed up a few things such wireless OFF on boot.
Click to expand...
Click to collapse
Ah, thanks. I suppose I can't file a bug since it is a nightly, I'll mention it on the appropriate thread and hope.
Another itchy part (for me) is the Terminal Emulator somehow got blue background and when "exit" command, it doesn't exit but I must force it off under Managing Applications.
Click to expand...
Click to collapse
Press the menu key, then "Reset term".

Yeap, that's another less painful way to close T.E.

Try downloading android assistant from the market and checking to see if you have airplane mode on through the app.
Sent from my LG Optimus V using Tapatalk

koopakid08 said:
Try downloading android assistant from the market and checking to see if you have airplane mode on through the app.
Click to expand...
Click to collapse
I had it, and got rid of it because it wasn't doing anything for me. I'm pretty sure I had checked this before *and* I have flashed several times, but I just got it and...the airplane is blue. I've got a thread on a dev thread, I'll ask about it getting fixed, clearly shouldn't be happening.

excarnate said:
I had it, and got rid of it because it wasn't doing anything for me. I'm pretty sure I had checked this before *and* I have flashed several times, but I just got it and...the airplane is blue. I've got a thread on a dev thread, I'll ask about it getting fixed, clearly shouldn't be happening.
Click to expand...
Click to collapse
It should not be blue. Tap on it and it should turn gray. Problem solved.
Sent from my LG Optimus V using Tapatalk

Is there an actual answer for this issuer? Is this designed by the CM7 team?

thereddog said:
Is there an actual answer for this issuer? Is this designed by the CM7 team?
Click to expand...
Click to collapse
It's an Android problem. Something to do with missing radios. Happens on the touchpad too.
---------------------------------
Sent from my LG Optimus V using Tapatalk
If this post helped you don't forget to say thanks!

Definitely not a nightly problem, it's that way in the official release too.
Sent from my NookColor using xda premium

Some smart CyanogenMod users fixed this problem. Perhaps their methods would work for you as well as they worked for me.
I guess we just have to avoid accidentally enabling airplane mode.

I actually prefer wifi off on boot as I don't need it most of the time and it just drains the battery.

Revolution HD 6.x Bootloop

Since upgrading to Android Revolution HD 6.0 and now 6.1, pretty frequently (3 or 4 times a day) my phone will automatically reboot and then get stuck in a bootloop process. Taking the battery out gets it all up and running again but its pretty annoying and drains the battery when I don't know its doing it in my pocket
Any help would be appreciated!
Thanks

Actually, I have the same, but since 6.1.1. And I noticed it's not exactly a bootloop. It looks like a hot restart but then the ROM won't show.
Sent from my HTC Desire HD using xda premium

Mine kept on waking in my pocket, trying to access the locations app. Flashed virtuous unity instead and find it superior in almost every way. Personal opinion only mind, but I did think arhd was very nice though

i also facing the same problem.. have u all tried to voice out in ARHD thread?

I couldn't at the time because of the ten posts required rule, by the time I'd got enough I was on a new ROM and had forgot to be honest. Plus I reckon my problem was caused by me trying to restore app data through titanium rather than a fault in the ROM itself but then again I could bee wrong... But I did try to find solutions to the problem in the forums and didn't find anything similar to my problem to no avail, not even anyone with something similar so I just moved on figuring that it was probably for the best. Worked out better for me in the end cause I got more practice flashing roms, learned not to try to batch restore apps just in case and learned the benefit of backing up your nice shiny new working ROM

Happened to me once while I was on 5.2.6. It's to do with the date and time setting. Try untick "automatic" and set the time and date manually. Once you manage to shut down your phone you can retick the the automatic option

maybe your phone cant Handel the overclock? try flashing the script to return the CPU to default settings in the same thread you got the ROM from.

mutsc0 said:
Happened to me once while I was on 5.2.6. It's to do with the date and time setting. Try untick "automatic" and set the time and date manually. Once you manage to shut down your phone you can retick the the automatic option
Click to expand...
Click to collapse
Actually, that helped to solve my problem!
Sent from my HTC Desire HD using xda premium

Thanks. I'll give it a go. Sorry for not replying to all your help before. For some reason I didn't receive the emails saying replies had been posted on my question