Related
Device: NEXUS S
Carrier: TMOBILE
Country / Language: USA
OS / Browser / build number (if applicable): 2.3.4
As of about two weeks now, my Google services connection sync and even Gtalk never stay on consistently. Data icon goes from green to gray, after wakeup. hen when it is green, I only then start to receive me push notifications. I never had this problem before and was very happy with the Nexus S. Now, however, I'm not so sure about that anymore, and it's a consensus out there that there is no solution, and that Google is "looking" into the problem. I don't think it's necessarily a hardware issue as everything was fine out of the box when I first got my phone, so its likely a Google server problem? Though it sounds like the problems are isolated to Nexus devices and myTouch 4G phones.
I would call Samsung to try to get a replacement device, but from what I hear, it doesn't solve the problem either, and Samsung's CS really sucks too.
Any advice would be greatly appreciated.
I am going through the same trouble, too. I think its more of Google server related. One thing tthat I am sure is, it started very recently. About 3 weeks ago.
Sent from my Nexus S using XDA Premium App
I have the same issue. It started a few weeks back. Got the 2.3.4 ota...same issue. Came from 2.3.2.
It's been happening to me for a while as well. Even back in 2.3.3 when I was on CM7 and OEM. I seriously think it's a problem on Google's side and they really need to address it because it keeps logging me off of Gtalk which is annoying.
Funny thing is. I notice that it happens alot less when I'm using 2g only....
Wonder if there is something to that..
Sent from my Nexus S using XDA App
I am also on two google threads about this, and there is still no agreement on a solution..
http://www.google.com/support/forum...e2&hl=en&fid=7c7a962fd3ae87e20004a26b2f3f005b
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=56f54d35a6a0da29&hl=en&start=80
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=5113952419b47e54&hl=en
I am having the same problem since around mid April. This is so frustrating, please guys flood the google help forums, this the only way google will see the seriousness of the problem.
Sent from my Nexus S using XDA Premium App
Flood indeed. Google is clueless on a solution to this problem, especially if they don't even acknowledge it..
Sent from my Nexus S using XDA App
clin0420 said:
Funny thing is. I notice that it happens alot less when I'm using 2g only....
Wonder if there is something to that..
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yeah I stay green if I'm on 3g, so maybe it's a wifi issue. I would've sworn it was a 2.3.4 issue though.
highly doubtful that this is a wifi issue, with the number of people of various threads stating that they dont even use wifi....worse yet it occurs regardless of wifi or 3g/2g
i posted a video on youtube showing the problem
http://youtu.be/axpyhgdvuMs
i have the same issue, both of my nexus 1 and tmo G2
Getting tried of watching my phone reboot. If going back to stock would resolve the issue I would do it. I called big red today and the pinhead I spoke to acted like it was the first time anyone had called about the TB rebooting on it's own. I'm looking at going to a different phone. I really think at this point it is a software issue that they need to correct. Just like with most businesses things are not addressed until they become a problem. So my thought is we should set a date when every one calls in to report their rebooting phones. We do this every week until we get a resolution. Anyone with me?
Wait... You are rooted and getting reboots? Are you on gb? Did you root or install your rom properly? What kernel?
Stock I had no issues. Non-Gb I've had mostly no issues... Some kernels less reliable than others, of course. But to be honest it sounds more like a user issue than a tb issue
Sent from my ADR6400L using XDA App
Sent from my ADR6400L using XDA App
Are you near a Verizon store? Verizon is usually very easy to convince that you need your phone replaced. (Although I think they will only replace it with the same model. But I'm not sure.) My Thunderbolt never reboots on its own but I know it is a problem that many Thunderbolts are experiencing, so maybe yours (and many others) is/are defective. I'm 99% sure if you go into a Verizon store and tell them that it randomly reboots all the time, they'll replace it for you.
I reverted back to stock and haven't had a single reboot or loss of data on three days. Just sayin'.
Sent from my ADR6400L using XDA App
I have read posts where people who are not rooted are getting reboots after they took the update. Have never had an issue with my phone until I took the update. Am going back to stock for a week or so to see if that clears things up.
Funny how VZW is changing their stance on it, almost as if it never has happened. About a month ago I went into a store and they told me that Im not the only one experiencing problems and that there will be a fix within 2 months.
I called VZW tech support and they told me that no one else is having reboots.. . . . I dont get it.
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Can you specify what you mean when you say "both"? I have been getting reboots too - approximately 1 per day - but is there a process to flash each radio independently?
Sent from my ADR6400L using XDA App
sethschmautz said:
Can you specify what you mean when you say "both"? I have been getting reboots too - approximately 1 per day - but is there a process to flash each radio independently?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
No, but each flash has two radios
Sent from my ThunderBolt using XDA Premium App
Silvus said:
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Click to expand...
Click to collapse
Any issues with tethering or gps using the old radios?
Sent from my ADR6400L using XDA App
Silvus said:
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Click to expand...
Click to collapse
I still had reboots with both at .6, currently trying cdma.7/LTE.6.
Sent from my ADR6400L using Tapatalk
It is a hardware issue,that's where the few pricked phone came from,my original bolt had the reboot loop on stock but no one seems to want to hear that,it is a series of phones having the trouble and they are or have replaced most of them,as far as most of the other reboot go that is self made misery by not following directions or not reading to find the fix, this bolt I have now has no reboot issues and it has a mat finish to it,the other one and a few I have seen that had issues had a smooth glossy finish.
Sent from my ADR6400L using XDA Premium App
satseaker said:
It is a hardware issue,that's where the few pricked phone came from,my original bolt had the reboot loop on stock but no one seems to want to hear that,it is a series of phones having the trouble and they are or have replaced most of them,as far as most of the other reboot go that is self made misery by not following directions or not reading to find the fix, this bolt I have now has no reboot issues and it has a mat finish to it,the other one and a few I have seen that had issues had a smooth glossy finish.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I would love to think its a hardware issue, but my phone was solid from day one. Then I took the update and get these random reboot.
Sent from my ADR6400L using XDA App
It is not a hardware issue. It is a problem with the update and how certain phones installed it. Verizon is in the process of making a new update and has been working on it with HTC for a little while now & expect to have it going out this month. For some reason the software does not talk to the towers properly with some models & the hardware does not get the proper info which causes the reboots. Exactly how to tell which phones are affected, I don't know. My friend is trying to find out for me.
I can say that I ran my phone with rooted stock & moved up to the rooted update when it was available which I am still on and I have not had any issues at all besides the low recorded video audio which the update seems to have fixed for me.
My phone is:
Rooted stock & radios w/update
Adrynelynes 4.47 Kernal
I am telling you what HTC said they admit that a certain series is defective hence the snappy replacement. Just cause one Rom works and another doesn't isn't always the Roms fault,ever had a CPU that would run one OS and not another or RAM that worked fine on xp but not win 7 once the defective hard hits its limit it will fail. I have seen hardware work fine overclocked and the exact same hardware crash with half the settings,or a motherboard run suse fine but put Windows on it and it dies a week later. I didn't say they all were defective just one series of them and when they did the update a lot of the phones started to fail and some didn't,so does that tell you hardware or software,if one can run fine and the other fails its either a bad flash or bad hardware. Take your pick
Sent from my ADR6400L using XDA Premium App
I didn't do the update over the air on my other bolt, I downloaded it from HTC and it killed the phone,but the same download is on this phone and it works just fine,not one reboot, and its still stock and not rooted. The other one was dated Dec
10 and this one is dated Feb 11, I would just about guess they tweaked the update to weed out the bad phones faster,makes sense to me.
Sent from my ADR6400L using XDA Premium App
satseaker said:
I am telling you what HTC said they admit that a certain series is defective hence the snappy replacement. Just cause one Rom works and another doesn't isn't always the Roms fault,ever had a CPU that would run one OS and not another or RAM that worked fine on xp but not win 7 once the defective hard hits its limit it will fail. I have seen hardware work fine overclocked and the exact same hardware crash with half the settings,or a motherboard run suse fine but put Windows on it and it dies a week later. I didn't say they all were defective just one series of them and when they did the update a lot of the phones started to fail and some didn't,so does that tell you hardware or software,if one can run fine and the other fails its either a bad flash or bad hardware. Take your pick
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I wasn't aware of HTC stating there was some defective hardware. Never saw any references to it. If thats the case then glad they acknowledged it.
It's definitely not a hardware issue. Its a radio/ signal issue. Verizon does know about it, and is working on getting a new update out there. I know this, for a fact.
Sent from my ADR6400L using XDA App
jett2314 said:
I have read posts where people who are not rooted are getting reboots after they took the update. Have never had an issue with my phone until I took the update. Am going back to stock for a week or so to see if that clears things up.
Click to expand...
Click to collapse
My TBolt is not rooted and before the update I had no problems at all but after the update the random reboots started. Battery life is acceptable but could be allot better.
Called Verizon yesterday and they acknowledge the problem and actually said HTC is aware of the problem and are working on it but have no expected date as to when it will be fixed. I believe it is definitely is a software issue and will be fixed when the official Gingerbread is released. Just my 2 cents.
Hey everyone I just bought a g2x and it seemed to be OK until everytime I charge it wont wake up and its hot as hell!! I have to battery pull. Last night I had it charging and in the morn the phone would not wake and was baking like it was in the oven. I rooted but still seem to have the problem with all rom's. After scouring the forums I've seen some people return there's and get an up to date model which fixes the problem. Other threads say its the battery at fault. Since I bought it straight up I can't call T-Mobile for exchange so what can I do? Are there any ways I can stop this from happening? Thanks guys for looking at my post.
Sent from my LG-P999 using Tapatalk
If it is getting that hot there is a serious problem with the battery or the phone. Contact TMO and get a replacement. If you bought from a third party source get them to replace your defective device. Are you using the official battery? After market batteries often have bad temp sensors and can cause dangerous issues such as this. If the battery gets too hot it can actually explode.
I bough it new from a third party at a high price. They said they will not take it back. Anything that is wrong with the phone its not their fault nor problem. Can't contact T-Mobile since i didn't get it through them and I'm on a different carrier because i had the phone sim unlocked.
Update though the only Roman which been running perfect no freezes or reboot is eagle blood froyo. Stable and fast rom but I'm dying for gingerbread. All Ginger roms give me problems. BTW I'm using battery that came with phone not third party.
Sent from my LG-P999 using Tapatalk
Do u have full coverage insurance? If u do, use the phone for a few days then call T-Mobile. Insurance stays on the line and covers 99% of phones.
Sent from my LG-P999 using xda premium
rbryant1983 said:
Do u have full coverage insurance? If u do, use the phone for a few days then call T-Mobile. Insurance stays on the line and covers 99% of phones.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I don't have tmobile contract. I use simple mobile 4g service which is 60 dollars a month. They won't honor me. I was thinking of calling LG support but I don't think that will go anywhere.
Sent from my LG-P999 using Tapatalk
Try a new battery. If that doesn't solve the problem contact LG USA support. Don't mention you are not a TMO customer or that you bought it second hand (warranty is to the original purchaser only - technically second hand devices have no warranty). If you don't have proof of purchase they might honor the warranty based on 18 months from the date of manufacture. Play as stupid as you can and see if they let you send it in for repair or replacement. They don't do advance exchanges so you will be without the phone for about a month.
No luck with LG support. The only thing I have left is trying a new battery. Right now I'm fine on Eagles Blood froyo rom but any other rom i get overheating and reboots/freezes. Idk why is that.
Sent from my LG-P999 using Tapatalk
I remember when I had the same issue you have... "charge over night, wake up and phone was very hot and the buttons light up but nothing was on screen"... I tried all the rom there is for g2x, best for me is cm7 nightly builds. No issue what so ever after flashing it. Cm7 Nightly 179
I just found a gingerbread Tom that was posted not too long ago that fixes all the screen of death issues and reboots. Jboxer ported it from another LG L95G (tracfone) that has the same hardware as the g2x. I've been running it and it is flawless. The only bad side is its stock. But ill take performance over everything else. Its gingerbread 2.3.4.
Im nit android saavy but im thinking LG messed up somewhere in the software. A bug that should have been noticed by them.
Sent from my LG-P999 using Tapatalk
Hello guys, i was looking at my system folder and i think i have so much files in there, do you all have them?
See what i mean on the attachment.
Post screenshot of yours of you have less.
And do you have any issues with your phone?
I'm asking this, because i have ghost touches issue, and at the start i thought it was hardware issue(grounding issue) as it was shown on the forums here by another user, so i went and opened my phone and applied the fix. but it still the same, today i opened the phone again to make sure i did it all right, and tried to insulate more parts. but the ghost touches remains.. so i really started to think it is a software issue.
looks like all these files conflicts one with another and makes this problem. just a theory thou, not sure. that's why i need your help.
Sent from my A0001 using XDA Free mobile app
Ghost touches is a hardware issue. This has been confirmed by Customer care. I got my phone replaced for a brand new one a month back. Best possible solution for you is to RMA your phone before your warranty runs out.
Sent from my OnePlus One.
akash4357 said:
Ghost touches is a hardware issue. This has been confirmed by Customer care. I got my phone replaced for a brand new one a month back. Best possible solution for you is to RMA your phone before your warranty runs out.
Sent from my OnePlus One.
Click to expand...
Click to collapse
RMA isnt possible for me since i got my phone from ebay. And i already opened it. And made a fix for any doubted grounding issue.
Sent from my A0001 using XDA Free mobile app
Had anyone noticed that OEM Unlock is now available for Verizon Note 5 customers???
Sorry buddy. Not that simple. That option has been there from day one. It just allows a Verizon specialist to now enter a code to unlock your phone (which they would never do anyway). Just pushing it will not unlock the bootloader. Our devs would have been smart enough to figure that one out.
Sent from my SM-N920V using Tapatalk
That is interesting because when I select it, it doesn't ask for a code. And I can confirm previously that this option was greyed out and not accessible. Now it is. I'm fighting phone issues (On my second Note 5 which is being warranted and a third one being shipped to me. 3rd phone now in three months. So its quite frustrating without titanium backup). First one was S Pen broke inside phone and the second one, my phone has seizures (constant charge/discharge cycle, red X on battery icon, Gear VR keeps popping up, when the original charge cord is plugged into it or placed onto a wireless charging pad. After a few reboots and cache clearing it will behave for a while until its charged again. This last time, it factory reset itself.
Sent from my SM-N920V using XDA Free mobile app
niftyguy239 said:
That is interesting because when I select it, it doesn't ask for a code. And I can confirm previously that this option was greyed out and not accessible. Now it is. I'm fighting phone issues (On my second Note 5 which is being warranted and a third one being shipped to me. 3rd phone now in three months. So its quite frustrating without titanium backup). First one was S Pen broke inside phone and the second one, my phone has seizures (constant charge/discharge cycle, red X on battery icon, Gear VR keeps popping up, when the original charge cord is plugged into it or placed onto a wireless charging pad. After a few reboots and cache clearing it will behave for a while until its charged again. This last time, it factory reset itself.
Sent from my SM-N920V using XDA Free mobile app
Click to expand...
Click to collapse
I had all those problems myself (except the spen) along with some Bluetooth issues I'm still having. 3rd phone here as well. And then when I say this phone is a dud people get mad at me and start crying. Oh well.
It doesn't ask you for a code it just unlocks the capability of said code to do anything upon being entered. Of course you are more than welcome to try it out and see if you can achieve root. Just don't say I didn't warn ya. [emoji6]
Sent from my SM-N920V using Tapatalk
So, the seizure one you've had?!? Verizon said that was unheard of
Sent from my SM-N920V using XDA Free mobile app
Nope. I had it and the lady said she has seen it before so exchanged it no questions asked. My new one has a Bluetooth problem. Music keeps cutting in and out if phone is in pocket or any pressure is placed against the area of the phone where the camera is located. I'm guessing that's where the radio is. They sent me a new one again but that had the same problem plus location issues so I said **** it and sent it back. They all have some issue or another.
Sent from my SM-N920V using Tapatalk
---------- Post added at 06:22 PM ---------- Previous post was at 06:20 PM ----------
The seizure is due to a defect in the charging port. On few devices it randomly detects a cable inserted which is not really there and screws everything up.
Sent from my SM-N920V using Tapatalk
Thank you! I kept on wondering WTF was wrong with this thing. The USB port is now dead. Won't recognize anything.
Sent from my SM-N920V using XDA Free mobile app