My G2 may be defective or is it this buggy?
I've actually had the phone reboot on me twice. It looked like a kernel panic like i'm used to on my nexus one with cyanogenmod nightly builds. not only that but i don't see any internet speed improvements in my area over the nexus one despite my area being HSPA+ deployed. I get about the same 800kbps-1.5mbps on both phones. Others in HSPA areas report >3Mbit.
I will also have some considerable lag issues and just plain hangups with switching applications that i never experienced on my nexus. Also I only get about 1.2ish gb of internal storage while othere report >2gb.
On the upside my hinge seems fairly solid and battery life is good. but those glaring issues have me wanting to return (get $ back) and go back to my nexus.
Did I get a lemon? Are others experiencing this as well?
Uhm... this forum is full of these complaints, how could you miss them all?
Here
And here
And here
And here
And here
Experiencing the same issues. Phone just turns itself off. Poor to no reception in areas where my Vibrant and Nexus One get2-3 bars of 3g. Like the phone but it does have issues which some people are reluctant to see. Weird things happen when I deploy the keyboard. Return button does not work at times etc.
From one entire day with the phone I thought reception was weak as well. BUT I asked my wife if her TMO BBerry 9700 had dead spots in the same areas and sure enough she said yes.
I'll be double checking that tonight.... I'll be much happier if it's the network and not the phone.
A lot of users seem to be having these so don't worry you aren't alone.
I get absolutely NO reception in my room (basement lol), coincidently I also use my phone as an alarm and couldn't figure out why it always stuck itself in a boot loop more at night than during the day (which it did...up to five times).
ANYWAY, personally I cut on airplane mode at night and have no problems with the phone crashing and boot looping (G2 splash screen). Ive also installed Rom Manager and run "fix permissions" which has basically stopped the random fc's and crashes during the day. I cant remember if the fix permissions is root dependent as ive always had root when running it but it worked very well for me. Before permission fix my phone was fast but seemed to jerk and twitch going through screens, now it doesn't.
I haven't experienced the freaky ghost track pad issue and the non responding touch screen which caused me to have to lock and unlock the screen.
These might help until either someone can achieve permaroot or tee-mobe sends an ota.
I've had the same reception issues. Tech support told me to do a factory reset, but I don't see how that would help since I just got my second phone two days ago (first one bricked after a kernel panic). It has had these problems out of the box.
Sent from my T-Mobile G2 using XDA App
Related
Please, somebody tell me there's hope. 2 really annoying & disappointing things are happening. My bluetooth keeps randomly disconnecting, and to make matters worse the status bar icon still shows it is connected, but it's not. Second, I am dropping calls almost daily, and I'm mostly in places where 2 seconds before the drop I had 4 bars!!! I went to a store today & got a replacement SIM (50.01 vs. 39.01 markings) hoping that might solve it, not happening. And the signal strength almost never shows less than -105 dBm, sometimes -97. I NEVER had a dropped call or any bluetotth issues with either my old trusty G1 or the MT3G I just came from. I'm really trying to love the phone, it has so many positives. But the fact that it's a "phone" and it's basic function is skewered is pissing me off big time. Please, someone tell me I ain't the only one experiencing these issues, and, that either the OTA FroYo or Cyan's first ROM is gonna fix 'em? Better yet, any known fixes now? Are these issues in any way related to the data issues, possibly? When I called Tech Support last night they said to try a hard reset, but I really don't want to do so, unless I can flash one of the stock/de-TW'ed "stock" ROM's written about in the Dev. threads. Anyone have any concrete suggestions or explanations? Thanks...
Hey all.
Been having problems with a Nexus One that crashes at seemingly random times.
I have been unable to pin it on anything, and am asking your help.
It appears to be independent of the Rom installed, whether there is an SD card present, or whether its connected to a USB cable or phone charger.
Any help would be greatly appreciated.
Phone Info:
Nexus One (AT&T model)
Radio: 4.06.00.12_7
Current Rom: Enomther's TheOfficial Nexus1 - v2.12.2
Provider: Rogers (BC, Canada)
Logcat output attached as screen capture image.
This has been reported by a few users. I sent mine in for repair and got it back not repaired - they couldn't replicate the problem.
My case has been escalated which means a HTC guy called and asked me a few questions and then told me to wait for an email (a few days ago).
I believe my problem started when I seriously overheated it ... driving with navigation on, 3g downloading maps and traffic data, car charger plugged in all on a very hot day on a very hot dashboard. This was the first reboot and they got more and more often after that. Now I can't run anything for more than 5 minutes if 3G or wireless is on (in 'Airplane' mode I can run for quite a while without a reboot).
mine was doing the same thing.
getting progressively worse until the phone was basically unusable earlier this week.
I was running CM6 at first when it started happening.
installed the newest nightly and it worked better for a bit then got even worse.
uninstalled the stand alone version of gmail from the market and it worked for a couple hours and then kept rebooting on me.
finally i did a factory data/cache wipe and installed a rooted stock rom and things have been working PERFECT for over half a week.
I had the same issue. first reboot happen when i had nav running plunged in then after a few months utube , browser etc would restart my phone. it didn't matter which rom i used or stock. I sent it in and they fixed it. i had issues with htc but it got fixed.
Yup, same here, strange thing is it isn't a complete reboot. Hard to explain but what happens is i'll touch the phone and then it will immediatly go to the CM6 boot logo, then immediatly to the lock screen, (which I have disabled) then to my normal desktop. Total time elapsed maybe 5/6 seconds, wierd.
A normal reboot usually takes about say a minute or so. just started happening 3/4 days ago, and happens maybe twice a day at most, some days not at all. Probably wait until Cyanogen includes 2.2.1 into 6.0.0 stable then reflash.
Ive been having the same problem for about a week now, but I'm still using stock, not rooted. Its weird, because its a really fast reboot. It goes to the Booting X, for about 6 seconds, then it boot up just fine. I cant understand it.
this really sucks
I am keeping my ATT nexus one around for gingerbread but these random reboots are really killing me....I use the phone for five minutes and it just reboots by itself....The phone runs really well for those five minutes...Ive done five factory resets but it is still just doing these phantom reboots.... Anybody find out anything more about this...or know a fix....the phone is not rooted and it is clean stock froyo...so please help or keep talking about it so htc will address this issue lol which i doubt since this phone is starting to become ancient....(cant wait till nexus S) =P
With regards to the original problem posted, I believe I've managed to diagnose it correctly.
The problem lies with faulty heat distribution. The phone would crash and reboot more often in times of great stress:
charging the phone (heats up the battery)
running many applications at once (heavy system load)
navigation (heavy dataand gps traffic, image processing)
This coupled with the fact that changing the OS did nothing to remedy the problem solidified the notion that the problem was hardware based.
Given this, I contacted HTC Nexus One support and had the phone repaired.
Note: HTC will honor the warranty and fix hardware issues for an unlocked Nexus One. With software issues, you're on your own (for obvious reasons).
This is exactly what my phone is off to warranty for. I experienced this with every rom tried. I wipe my phone completely and put stock froyo on only to see the exact same behaviour...so at least I'm not crazy
The tech told me it was a hardware problem so that is a bit of a mind ease.
It seems Nexus One and Desire are really similar: HTC Desire rebooting on its own.
P.S. It's a problem with faulty motherboard, if you're within warranty, it should be replaced.
I also have been pleasantly experiencing this issue with the nexus one, so i sent it for repair at HTC and they have said it is an issue with the motherboard and it has been replaced, it is now in the post so I will update this post when I receive it to whether the problem is resolved. Hope so was driving me crazy!
The log did not capture the error. In most cases its a software issue, not hardware. (has happened to me too, not recently though)
Well an update as promised.
I received my N1 back after UPS had finished not dispatching it due to "Adverse weather conditions" and the issue is GONE!!! I know a week isn't really a long time to trial the device but this was happening several times a day.
HTC replaced the motherboard.
My advice to anyone having this problem, is to send it to HTC for repair (dont be worried about it being rooted/custom ROM etc mine was and because its a known hardware issue they really aren't bothered about it.)
It took two trips to HTC for them to finally address the issue. They did fix something (they didn't say what) and the problem is gone.
I believe it was the motherboard because Swype Beta decided that it was a new phone and not the one I registered (so it would not install).
Earlier, my G2 shut off on me about 5 times. -_-
First, I had it sitting in the car ,tried to take a pic but the stupid voice recognition menu kept coming up so I gave up and set it down in the console. When I got home, the phone felt warm and was.. off.
Then, I turned it on.. stuffed it in my pocket. A moment later, I pulled it out and YET AGAIN when I pushed the button I was greeted by a quick vibe and the HTC screen -_-
Then a few minutes later I ran a speed test (checking HSPA+ out in Vegas).. put it down on the table.. come back.. PHONE IS *(@#% DEAD AGAIN.
I HATE YOU! *glares at phone*
It's killing me because it either happens several times in a row, or doesn't happen for days! I've tried replacing the sim card, replacing the SD card.. moving the battery... no dice.
Maybe it's my SIM card? Would that cause it? My last phone did that -_- And I'm silly to have not yet changed the SIM lol
Good thing I have a spare sitting in my bag.
What battery are you using? Aftermarket? Is so, did you remove the sticker around the battery? If you did then make sure you place a piece of tape on the battery to avoid making contact with the metal sd card holder. The metal on metal causes it to shut down.
Sent from my HTC Vision using XDA App
Interesting. I've also been having random shutdowns (not reboots, which I've seen mentioned elsewhere, due to a hardware fault) --
HTC Desire Z, using default battery, but I'll try isolating it anyway with a slip of paper or something.
OP you on a custom rom with overclock? maybe your clocking your phone too high or low?
Also if the phone for whatever reason gets too hot or cold it will turn itself off.
Please see this forum: Phone powers down and won't turn back on w/o pulling the battery
I strongly believe that this may be an issue with the GPS and/or Google Maps. Once I have the GPS off, this has not occurred. Can anyone else try this?
I have the Bell Desire Z NAM with stock HTC Sense 2.2 ROM.
It seems to be quite prevalent, see the bottom of this review: T-Mobile G2 is speedy sequel to original Android
I think you may be onto something with that GPS note, but my phone doesnt' need the battery pulled to restart.
Also, it's running the stock firmware, stock battery (just exchanged battery and got a new SIM card yesterday, and it shut off again today.. so those aren't the problem)... so any issues I'm having are 100% stock related...
This time it shut off after using Maps so....
i read somewhere (trying to find the source) that some G2's were experiencing random restarts / shutdowns due to low signal strength. Not sure how valid this is but you might want to look into this as well.
fablife said:
i read somewhere (trying to find the source) that some G2's were experiencing random restarts / shutdowns due to low signal strength. Not sure how valid this is but you might want to look into this as well.
Click to expand...
Click to collapse
This was true before we received the first OTA update. Since then though the problem has been fixed.
I think it was definitely the GPS, that said I just got done with a really long phone call about this and have a replacement on the way.. but that was way too much effort AND I have to pay shipping (it's not much, but seriously.) I'm not happy that T-Mobile was THAT big a pain in the butt about getting the phone replaced with a new one in the 30 day return period.
Going by the pointers one of my close friends on sprint (that used to be on AT&T) gave me, I'd say this could've been worse with another provider.. but it shouldn't have been. The reception isn't the best so the customer service should make up for that, and it sorta does.. but it sorta doesn't.
Oh well.
I have been experiencing almost the same thing for the past week or so. I have tried a few things such as lowering clock speeds, changing roms, and not using maps or GPS. Nothing has stopped the shutdowns. I cant seem to find a pattern in the things the phone is doing when it shuts off because it rarely does it when i have the screen on, also it never does it if music is playing or if i am watching a video. I will say that it seems to happen alot when i am in spots i know are dead spots for phone signal. I flash roms a fair amount so it is hard to say this has started after flashing a rom, but I will say it never did this before I flashed my first sensui 3.0 rom.
I am thinking its one of two things, something with the radio and/or its firmware or something with the sdcard because at least one senseui 3.0 rom said something about sdcard formatting.
I hope all this helps the smart people come up with idea on what wrong with our phones.
djrajir said:
I have been experiencing almost the same thing for the past week or so. I have tried a few things such as lowering clock speeds, changing roms, and not using maps or GPS. Nothing has stopped the shutdowns. I cant seem to find a pattern in the things the phone is doing when it shuts off because it rarely does it when i have the screen on, also it never does it if music is playing or if i am watching a video. I will say that it seems to happen alot when i am in spots i know are dead spots for phone signal. I flash roms a fair amount so it is hard to say this has started after flashing a rom, but I will say it never did this before I flashed my first sensui 3.0 rom.
I am thinking its one of two things, something with the radio and/or its firmware or something with the sdcard because at least one senseui 3.0 rom said something about sdcard formatting.
I hope all this helps the smart people come up with idea on what wrong with our phones.
Click to expand...
Click to collapse
My Desire Z had the same problem and I returned it to HTC Service for repair. They said they change some cables? and a new battery. It has been nearly 3 days and I haven't experienced a single shutdown but there was one time it restarted by itself.
Yeah my only problem with that is, I am close to my upgrade date. How much did it cost. I may still do it so I can give this phone to my kid brother.
Sent from my Htcclay's SuperCM7 G2 using Tapatalk
Just to update, I found that I can make it do it some times when playing with opening the hinge.
Sent from my Htcclay's SuperCM7 G2 using Tapatalk
Possible cause/fix found
I posted this in another thread here regarding the same problem but it appears it may have been overlooked so I'll post the info again in hopes of helping you and others having this problem.
A possible cause/fix has been found as posted on the T-mobile forums:
http://forums.t-mobile.com/t5/T-Mobile-G2/G2-Turning-off-by-itself/td-p/513575/page/4
There is a conductive metal strip along the back of the battery that looks like it may be shorting out. Check out the link for detailed fix with pics. I take no credit for this, just posting it since I'm experiencing this problem too.
Talked to tmobile CS today and was trying to get a replacement because my phone would randomly reboot and shut off. All he told me was go and pick up a new sim card. If that didn't help then they would be willing to give me a warranty replacement.
Sent from my T-Mobile G2 using XDA App
carquote said:
I posted this in another thread here regarding the same problem but it appears it may have been overlooked so I'll post the info again in hopes of helping you and others having this problem.
A possible cause/fix has been found as posted on the T-mobile forums:
http://forums.t-mobile.com/t5/T-Mobi.../513575/page/4
There is a conductive metal strip along the back of the battery that looks like it may be shorting out. Check out the link for detailed fix with pics. I take no credit for this, just posting it since I'm experiencing this problem too.
Click to expand...
Click to collapse
Clicking your link all I got was an empty T-Mobile page with the message "Page not found" and some some java script error message when closing the window.
Is this possible fix something else than lining the back of the battery with a strip of paper?
whpsnp said:
Clicking your link all I got was an empty T-Mobile page with the message "Page not found" and some some java script error message when closing the window.
Click to expand...
Click to collapse
Sorry about that, I fixed the link and it should be working now.
Cool, thanks!
Sent from my HTC Vision using XDA App
I'm pretty sure mine is not caused by the metal strip since my battery's all proofed. I didn't have anything wrong with it until about half a month ago, and it always happened after using GPS and left it on. If I turn it off after navigation or any other app that requires GPS the phone won't go into SOD.
I switched back to CM7 RC2 around that time and starting to get the GPS no fix problem, and it could't be fixed by the dd=/dev/.... script. So I switched into Nightly 88 or something that at least I was able to get a fix but the not-so-random freezing started.
This morning I flashed the new 7.1.0 RC1 and the phone would just turn itself off (it used to just freeze and become hot), and I got really tired of it... My old G1 was much more reliable than this.
I tried the dd=/dev script again, so far after 5 min the phone is still on with GPS on....
@carcuote
Thank you! I haven't had this issue for months now. But the solution is so easy to do that I will try our anyways.
I had this issue the first month our so when I got the new phone, but went away permanently after the second month. Maybe the contacts in the battery got a little rusted? Don't know but the solution is simple enough to try...
Sent from my T-Mobile G2
When I was talking with someone on the phone, the service will randomly lost and take several seconds to be available to call again. It is not very often and it is fully random.
My phone is T-MOBILE G2, with CM 6.2 with radio 26.03.02.26_M. I know many others who have the same problem too, no matter what rom or what radio they use, eight it is sense or CM, either it is the newest radio or my radio, there is still the problem.
How can I resolve this? Or it is a hardware problem?
Please kindly advise.
same
I have this problem too...i have a sneaky suspicion that its due to our undervolted kernels...
same problem
help
please help.
try settings/wireless/mobile networks/network mode/GSM only
That did wonders for my signal.
will try, thx bro.
I have the same issue as well using cm6.1.1
Sent from my HTC Vision using XDA App
This hardware has a very sensitive radio. That is the reason.
dhkr123 said:
This hardware has a very sensitive radio. That is the reason.
Click to expand...
Click to collapse
I've noticed that no matter what kernel I use the radio is very strange. I've never been sure if it was my wireless network at home or my cellular provider. I believe it's the phone itself though after extensive testing.
I also have this problem. It has happened with the stock ROM, CM6.1.1, and Enom's 2.14.2.
I'm also having issues with the touchscreen becoming entirely unresponsive, and either the touchpad sending random signals or the touchscreen registering random hits... when I'm operating the phone at times (most noticeable when texting), the cursor will begin jumping around the screen and selecting buttons randomly. Very annoying.
grivad said:
I also have this problem. It has happened with the stock ROM, CM6.1.1, and Enom's 2.14.2.
I'm also having issues with the touchscreen becoming entirely unresponsive, and either the touchpad sending random signals or the touchscreen registering random hits... when I'm operating the phone at times (most noticeable when texting), the cursor will begin jumping around the screen and selecting buttons randomly. Very annoying.
Click to expand...
Click to collapse
That might be due to your trackpad picking up stray lights that make it think your touching it. As far as everything else...it's T-Mobile...AGAIN. My cousin has a completely stock LG Optimus Prime (LOL...jk Optimus T) and she says the same exact thing keeps happening. Also my mom says she's had the same problem, and I'm sure mom doesn't know how to get an undervolted kernel on her phone...much less even root it...lol
i have that random touch register on the screen happen to me when charging with a poorly regulated chinese made power supply sending interference to the phone (measured on oscilloscope).
guys, can we focus on the signal problem?
I'm experiencing the exact same problem. I often make phone call with others for a long time. Every phone call breaks down. It often happens about every 30 mins. I'v tried every thing I can do to. I also started a new thread about this in Q&A section. But, I dont get any reply. I SHIP S-OFF my G2 and remove the Network lock with HTC Smartcard. Is that a problem?
http://forum.xda-developers.com/showthread.php?t=997689
This problem is so annoying, and I'm so disappointed.
Please, say something.
Try to update radio I had very same problem for long time, then i flashed 26.06.02.27_M radio and now my phone works 100% fine! No single dropped call in last ~4 weeks.
So today while in class at college, my phone was acting very funky. I noticed that touch screen response was going crazy (Even the capacitive buttons were freaking out). Pushing on the screen would type randomly, bring the notification bar down, etc. Pushing on the capacitive buttons would usually do nothing, vibrate, or do the exact opposite it is suppose to do. I can usually alleviate the issue by turning the screen off and turning it back on, but it will only be responsive for a very short time.
So, I was thinking there was something wrong with my install of the CM 6.1.1 ROM, so I flashed the Liberated Aria FR008 ROM and... it does the same. So then I load the CM 7 (18 nightly) and it seems fine with it happening every now and then, but I don't want to use CM7 (Albeit great, it's sluggish and isn't up to what I want to use as my daily driver).
I've treated my Aria with care ever since I got it after my transfer from Alltel. I'm usually able to fix my own problems, but this one has me stumped. Any ideas as to why it's freaking out?
CM7 is now up to nightly 39 and there was a big improvement in speed/performance from 34 and later.
I have 34 loaded right now (Just found it in my Dropbox folder); however, the touch screen is still very sensitive.
I've been having very similar problems with my Aria recently; unresponsive, misreads where my finger is, Swype goes nuts, but a quick lock/unlock will correct it for a little while. I thought it was just that my cracked screen was finally giving up. Now I'm downloading CM7 build 39 to see if it's something else.
EDIT: The CM7 build didn't help my problem. I'm upgrading to an Inpsire 4G tomorrow, but I might try a few more things first or while I'm rooting it.
So I found my backup of the stock ROM and flashed it back on there. Still getting the same issue.
I upgraded the stock ROM to the "latest" AT&T version and I'm taking it into AT&T tomorrow.
perhaps its an isolated defect on your phone. hopefully your hardware is still under warranty, but alas we already flashed. maybe you can get a technician to look at it.
Took it into the store and the guy said it's "shot". I'll be able to replace it under warranty.
I should be fine. I'm still confused about how the touch screen became unresponsive, and like I said... I'm usually able to figure this stuff out (Going to college for computer engineering).