Database Info

Nexus S Freezing - How big a problem is this?

I'm on the verge of buying a Nexus S but I am now reading about many freezing issues where the phone loses all responsiveness after the backlight goes out on occasion - the only solution being to pull the battery and reboot, only to have it happen again.
This thread shows that some people are returning their phones to Samsung and are seeing a fault diagnosis of 'bad BGA' and a fix of 'PBA replaced'
Original Problem:
Technical Inquiry
Phone Freezing / Locked U
Freeze/Delay Between Menu
Problem found:
BAD BGA COMPONENT
WARRANTY, REPLACE PART
Solution:
Replaced PBA
Passed All Functional Testing
Just how wide a problem is this, is it something that will affect pretty much everyone at some point or are these cases failry isolated?
edit: I am buying from someone who has this phone on contract so I am wondering also if I will be able to get support from Samsung should I run into this problem. Are warranty issues dealt with by Samsung direct or are they passed through the carrier when originally obtained on contract?
Any thoughts?

never experienced any of these problems. you have a 30 day return policy (maybe less now)

zephiK said:
never experienced any of these problems. you have a 30 day return policy (maybe less now)
Click to expand...
Click to collapse
Unfortunately not, see my edit above.
Also, it seems users are running into this problem after owning the device for a while, taking them beyond their 28 day / 30 day return

i've had mine since it was first available and never had any problem like this.

I've also never seen this.

milkham said:
i've had mine since it was first available and never had any problem like this.
Click to expand...
Click to collapse
same. ive had it maybe like a 1.5 week after release date

It happens to me if i mess around with custom kernels and o/c speed but so far if i use netarchy's stable CFS, it'll be fine. No freezing and having to pull my batt.
It happens if i use hornity or some BFS kernels. Haven't tried Jame Bond yet to test it out.

i think the OP is confusing the SGS issues with SNS
the SNS doesn't have any of those problems listed.

AllGamer said:
i think the OP is confusing the SGS issues with SNS
the SNS doesn't have any of those problems listed.
Click to expand...
Click to collapse
the thread the OP linked is Nexus S

only time that has happened to me is when i overclock to 1.4 ghz and the phone can not handle it

Ok, it's encouraging that this isn't affecting everyone but still a bit worrying.
AllGamer said:
i think the OP is confusing the SGS issues with SNS
the SNS doesn't have any of those problems listed.
Click to expand...
Click to collapse
Wrong - as zephiK has pointed out, the link is to a whole load of people having issued with the Nexus S, NOT the Galaxy S.

I believe the most problems with smartphones are in software, not hardware. And software could/should be patched/updated.

and this is one of the reasons that preventing me from walking into cpw and buying it tomorrow.

I am Having this exact issue with my phone. it is unusable the phone freezes every 20 minutes. Hope Samsung finds a fix for this soon.

I just got my nexus s the other day but I haven't had any freezing either I hope those with the issue get it sorted out though

loading another ROM would help, or perhaps it might be a hardware issue, in which case, take it back for an exchange

AllGamer said:
loading another ROM would help, or perhaps it might be a hardware issue, in which case, take it back for an exchange
Click to expand...
Click to collapse
Happens in stock rom, and many other custom roms too. So I dun think its the rom problem

oh dear, this is exactly what I'm concerned about. Any pattern as to which are affected by this, ie just slcd or just samoled? Only a thought.
I shall soon receive my second nexus s and I really don't want to have this problem!

I'm using the i9023 if that info helps.

Yes thanks but it's not what I wanted to hear as the chances are that this is the one I will receive.
I've heard of people reporting successfully fixing this with a full reflash, others say it's a hardware issue.
Keep us posted.

cant hear me now

Im having a problem with the charge - im running Gummy 2.0 with EE4 Radio.
When im on calls i frequently get into a situation where people will stop being able to hear me. I can still hear them, but nothing i can do including re-dialing them will fix the outgoing voice from me to them. I have to reboot to make it work.
Has anyone experienced this and is it a known issue with a fix perhaps?
Thanks

cmdrfrog said:
Im having a problem with the charge - im running Gummy 2.0 with EE4 Radio.
When im on calls i frequently get into a situation where people will stop being able to hear me. I can still hear them, but nothing i can do including re-dialing them will fix the outgoing voice from me to them. I have to reboot to make it work.
Has anyone experienced this and is it a known issue with a fix perhaps?
Thanks
Click to expand...
Click to collapse
Try flashing the EE4 or EP1Q radios.

I've experienced this too, and there's another thread, http://forum.xda-developers.com/showthread.php?t=1210384 with more details.
VZW replaced my phone, and I'm still trying to determine if the issue is gone yet or not. It appears to be happening a lot less so far. I noticed that for the EP1Q leak, as well as now with GummyCharge 2.0 + 1.4Ghz OC

This was posted by a Verizon employee on the Verizon Community Forums.
I have some good news to share about the audio going out on these devices. I did a query in our trouble ticket system about the Charge losing audio and randomly muting the call. What I found was actually surprising to me. SOME Charges were affected by network element in their market, and how the Charge responds to a switch element. Because it was so widespread, we assumed it was only a software problem (Samsung is fixing this issue as well with a software update). Here's an abbreviated resolution from one of the tickets that had this problem resolved: "There was an issue with the Samsung Charge in markets that use the Tellabs 3700 PAEC and that was resolved on Friday 8/12 BY changes on the 3700 PAEC ECANS .. Customers should be fine since then .. In MD - the issue was fixed on the night of 8/19." So many customers have already seen improvements.
So, what this means is each person that is experiencing issues with audio going out randomly while in good coverage should call tech support directly at 866-892-7957 > 1 > Enter number > Choose the option for advanced devices and PDAs. This will get you connected with tech support. If you'd like to give them a ticket to reference, use NRB ticket 4574701 as a reference. It's possible that the network your Charge is connecting to did not receive the 3700 PAEC ECANS update. If your issue is not resolvable by the NRB, it will by fixed by the Samsung software update (of course I have no ETA on that other than soon).
Click to expand...
Click to collapse

Data blinks in and out on AOSP only since getting new SIM

5/19/2013 Update: The bug might be dead! Like for real this time. See this post, post number 14 in this thread with an explanation of what to do.
10/25/2012 Update: TRY THE LATEST BUILDS OF BRUCE'S CM10 STARTING WITH THE 10/25 VERSION!
Bruce has made a change that helps differentiate between the regular data stream and the MMS data stream in an attempt to see if that was what was causing the instability issue. This is only on Bruce's CM10 Kang as of 10/25. If you are only another CM ROM, flash Bruce's (even if just for a minute or two) and see if the data bug goes away. Please report back if it did!
If this does cure it, I'm sure Bruce will share the sollution to all other devs and your favorite other AOSP ROm will have the cure shortly.
Updated 10/24/2012
This is a detailed description of the 6 million or so things that various people have attempted to do in order to rectify the blinking data connection problem plaguing T Mobile USA users on AOSP ROMs for the Sensation. This issue is non existant in Sense based ROMs.
The problem has something to do with how the Sensation authenticates itself with the T Mobile Data Network. It's not based on the cell towers as voice calling is unaffected. The theory is that the AOSP framework lacks the proper authentication certificates for part of the data network and when the phone is routed to that part of the network, it gets kicked off teh network, then continually retries to connect.
This was and issue on the Sense Gingerbread Stock ROM in 2011 but T Mobile and HTC patched it. All Sense ROMs are free from this bug. But no one knows what exactly the patch was so AOSP ROM's have not been able to be cured yet.
Short version....
Problem started for me on Bruce's CM10 rom. But it's reported on all CM10 variants and most CM9 ROM's as well.
One day I noticed that data wasn't connecting well. It would blink on and off. Sometimes it would stay on, but if I turn it off then right back on, it might go back to blinking.
The problem exists on all AOSP roms (AOKP, CM9, all versions of CM10) even after full wipes and restores of known working nandroids.
Cell signal for voice calls works perfectly. No problems whatsoever. So the phone is connecting to T Mobile. It just won't get data.
Long version....
To fix this I've tried the following...and how each does or doesn't work.
Switch to 2G networks only and switch back. Problem remains, and still blinks E on the EDGE networks rather than being solid on them.
Updated the radio. Problem remains.
Updated the entire firmware package. Problem remains.
Superwipe and flashed Sense, verify data works well. Then regular wipe and flash a fresh install of CM10. Problem remains.
Flashed clean version of CM10 and fixed permissions. Problem remains.
Made calls from the phone. Some people have reported that this helps temporarily.
Sent myself a text message. Some people have reported that this helps temporaliy.
Turn on airplane mode for a minute then go back to normal. Some people have reported that this helps temporarily.
It's not related to Wifi at all because I've created the error on fresh installs of CM10 before ever turning Wifi on.
Formatted SD card. Problem remains (and just to be sure I got the error while the blank formatted SD was removed from the device)
Checked the APN's 100 times. They are correct.
Spent an hour on the phone with T Mobile. Their tech said everything looked good on their end. He cleared the SIM and reactivated it. Problem remained.
Other people have gotten new SIM cards and found that while they helped right away, the problem eventually came back.
The only things that have shown any help to multiple users are in bold above. There are various reports of 100 other 'fixes' that people swear fixed the problem for them. But all of them involved the phone disconnecting from the network and reconnecting. That appears to be the key to get data working again temporarily. Making calls and sending yourself text messages also forces authentication on the T Mobile network without breaking the original connection.
If you want more details or want to review the logs to see if you can figure it out, logcats of the problem are located in this post! Click here for logcatty goodness!

Here is the real kicker....
Everyone once in a while...it connects. And once it's connected it'll stay connected until I turn the connection off or reboot the phone. Then it'll go back to blinking in and out when I try to turn it back on.

Just another note, the data is finicky on my old LG G2x also on TMobile with AOSP based ROMs, talk works, but cell data won't come back after going into airplane mode and out, until a reboot. It works fine on official TMobile ROMs. I suspect there may be some proprietary cell data negotiation between handset and Tmobile towers that AOSP code doesn't have.

Whyzor said:
Just another note, the data is finicky on my old LG G2x also on TMobile with AOSP based ROMs, talk works, but cell data won't come back after going into airplane mode and out, until a reboot. It works fine on official TMobile ROMs. I suspect there may be some proprietary cell data negotiation between handset and Tmobile towers that AOSP code doesn't have.
Click to expand...
Click to collapse
Okay here's an update on this for anyone who finds this thread through a search or Google or something....I'll try to describe this using the simplest terms possible so those of us who aren't cell tower engineers can understand it. (And I assume that's most of us, including me!)
The latest running theory is that the issue occurs due to the way the phone is handed off from 1 tower to another.
As you move your phone is handed off from one tower to the next. You get unregistered with tower 1 and reregistered with tower 2. That's normal.
However if you are within range of 2 towers you can't be on both. You have to be registered with 1, and that's supposed to be the stronger one. But AOSP ROMs lack a T Mobile certificate that authenticates which tower is supposed to have priority. So when the data is blinking you are getting bounced between 2 towers because the phone is trying to register with both.
The latest version of Bruce's CM10 ROM (Dated 10/10/12 and with TMOUS DATA in the rom name on the download page) supposedly includes patches that fix how this authentication works. And I only say 'supposedly' because the patches have only been up for about 12 hours so the jury is still out on how well it works. Personally I've been on it all day today and haven't had the data issue yet. But it can be days in between seeing it. So it'll take a while to know for sure that it's fixed.
If this turns out not to be the exact cause of the problem, it's something similar and a final sollution should be found soon.
Update: This have never been substantiated, and several users with the bug have reported knowing for a fact that they experience the problem when in range of only 1 tower.

Hi,
I have noticed with JB ROMS that you get 7 or 8 APN's,most of which do not apply to me.
Have you tried (making a note of your one first) and deleting all the APN's
Reboot,and just install yours.

malybru said:
Hi,
I have noticed with JB ROMS that you get 7 or 8 APN's,most of which do not apply to me.
Have you tried (making a note of your one first) and deleting all the APN's
Reboot,and just install yours.
Click to expand...
Click to collapse
That's one of the 1000 things that's been tried, to no effect. If he APN is set to the correct one the extra APN's are ignored.
Nothing that you do within the phone can cure the problem. At most, forcing the phone to re-register with the tower is the only thing that can help, and that will be temporary if it works at all.
The best bet now is to hope that Bruce fixed it with his latest additions to CM10 now that we understand what the actual problem is (or at least that we think we do)

Update....
T Mobile data is still broken. It has not been fixed yet. The latest theory may just be one more in a long line of theories that turned out to be wrong.
There are days when I really hate this phone.

Thanks for the update. I've been monitoring that thread occasionally, but it has way too much traffic for me to keep up. I was close to switching to it, but I need good battery life and reliable cell service over any smoothness benefits of JB, which is why I'm sticking with HyperNonSense ICS for now.

been experiencing this issue for a couple months myself. currently stuck in a no data bout as we speak. i'm wondering if it has anything to do with the amount of data we've used. i noticed this last bout started right around the time i passed 5gb. should also be noted i'm on the unlimited 4g plan and tether like crazy. i guess i'll know if the problem persists until my next billing cycle. for now i'm stuck with a sense nandroid and crack flashing aosp daily to see if it's fixed.

cpittman said:
been experiencing this issue for a couple months myself. currently stuck in a no data bout as we speak. i'm wondering if it has anything to do with the amount of data we've used. i noticed this last bout started right around the time i passed 5gb. should also be noted i'm on the unlimited 4g plan and tether like crazy. i guess i'll know if the problem persists until my next billing cycle. for now i'm stuck with a sense nandroid and crack flashing aosp daily to see if it's fixed.
Click to expand...
Click to collapse
I have tried the SIM swap fix. And that has apparently worked. I've been using in good for about the last 6ish hours without any problems. :good:
So i'd give that a shot if your willing.

I've been using CM10 KANG since it was available for HTC sensation. Never had the data blink issue. Recently, my phone started to have this issue. Data would simply not connect with CM10 or CM10.1 with any radio/firmware combination. I also noticed that when I travel to work, i get data say after 10 miles away from my home and it continues to work after coming back home. However, after restarting the phone, i hit the blink problem again. Wondering if its because of some cell tower maintenance/upgrade near my area.

So I was on bruce's ROM until a week ago and this never happened while on his ROM. Just upgraded to albinoman's ROM and this started happening. I have to send myself a MMS picture to get it back again. Hope this helps

Fix
Ive had this problem on and the only thing that seems to help is flashing a new ROM but then a few weeks later it returns... I realized that this only happens when I try to send an MMS message or attempt to receive them. I don't know how to stop receiving an MMS but just delete the picture message you're trying to send and your data should stop blinking on and off. Can't guarantee it'll work for you but it worked for me! GL!!

It appears as though this stupid annoying silly obnoxious bug has finally been squished, sprayed with 3 cans of Raid, and its' mangled corpse then burned to a crisp...I hope.
3 weeks ago W1ldFl0wer brought this fix to Albinoman's attention...
In the build.prop under phone>system was the following line....
ro.telephony.ril.v3=datacallapn,signalstrength
This line appeared like this on all AOSP roms for the sensation.
The fix was to add skipbrokendatacall to the line so it looked like this....
ro.telephony.ril.v3=datacallapn,signalstrength,skipbrokendatacall
Save the file, reboot, and data should spine right up and work fine. So far the peopl ewho have run into the data bug have implimented this change and BOOM, data fixed.
So if you use any AOSP ROM 4.0, 4.1, or 4.2 other than Albino's CM10.1 Kang just add skipbrokendatacall to that line and see if it fixes it. Only do this if you on in the US on T Mobile's network. If you are in parts of Europre making this change will screw up your data.
If you are using Albinoman's CM10.1 Kang ROM, he has already included this line in the build.prop for you. You just have to activate it. About 30 lines into the build.prop is the new line that reads...
#ro.telephony.ril.v3=datacallapn,signalstrength,skipbrokendatacall
Just delete the # in front of that line. (The # makes the ROM skip the line when loading everything, but lets it stay in the file so you can read it. Deleting the # means that the phone will read that line when it reboots.) Then go up to the line that says the same thing without skipbrokendatacall and delete that line entirely. Save the file and reboot. If you don't delete the original line without skipbrokendatacall, your phone will go haywire, data might not work at all, and you might inadvertantly trigger Z Day. So if you're not ready to fight in the zombie apocolypse, only leave one of those lines in the build.prop.
Hope this cures it for everyone! Again, don't make this change if you live outside the USA or are not on T Mobile's network! Doing so on other networks in other parts of the world could make things worse for your phone!
Here is the link to the post where W1ldFl0wer informed Albinoman of this fix.
http://forum.xda-developers.com/showpost.php?p=40755845&postcount=9003
I don't think W1ldFl0wer invented the fix, but he certainly is the one who made it public to Sensation users so go to that post and thank him/her bcause I might finally be able to stop obsessing over this stupid bug because of this user!!! :good:

Verizon Update 12/22/2016

Got a notification this morning. Anyone upgraded?

@anewday, you got screenshot of the update notification? Is it ending with PL#, then it must be December security patch. What's the build no.?

Mmb29k.g920vvru4cpk2

Yes, it's been running smoothly since last night.

txtl said:
Yes, it's been running smoothly since last night.
Click to expand...
Click to collapse
Whats different?

I think it's the November security patch.

AsaSpades said:
Whats different?
Click to expand...
Click to collapse
Just Nov security patches ,and samsung music is removed. Feel a little bit smoother.

Anyone seeing battery issues after this latest update? I already used package diablerie pro to remove bloat and I am still seeing terrible battery life.

JCTechie said:
Anyone seeing battery issues after this latest update? I already used package diablerie pro to remove bloat and I am still seeing terrible battery life.
Click to expand...
Click to collapse
Usually takes a few days to settle down after an upgrade. Give it a little time and see how it goes.

Touch and performance issues with Verizon update G925VVRU4CPK2 Galaxy S6E 12/16/16
sometimes, as in for short periods throughout the day the phone detects touches as a jump from one letter to the next; consequently, not inputting the first character but the second. This impairs my typing, so I have to type significantly slower for it to understand I'm typing different letters. this also affects any touch movement and the phone's performance as it lags as well as misses certain touches. This only happened after this update on 12/16/16. Not only does did it affect my phone but my brother installed the update as well and his phone (same model) is experiencing the same issues. I had nova launcher as well which i uninstalled and I have deleted the cache multiple times, started the phone in safe mode and was not able to use the phone codes since Verizon blocked access to updating the touchscreen's firmware. It is not a constant issue but it happens at least a couple times as day which is extremely annoying when trying to type or move around.
If anyone has encountered a similar problem or has a possible solution I would greatly appreciate any help
My device is Unrooted

Does service mode still work? Go to dialer and input *#0011#

anewday said:
Does service mode still work? Go to dialer and input *#0011#
Click to expand...
Click to collapse
Could someone try and let me know. I wouldn't upgrade if service mode doesn't work. Much appreciated.

Cricket bands, thoughts on beta, how to delete posts

Sorry to try to get in three topics here, but sometimes I post stuff with no reply.
I've heard of some T Mobile reception issues, but no one really complains of cricket issues. I don't have another Cricket phone in my pocket to compare it to while traveling, but I do have an a Verizon phone... And in my state cricket/ att would always have just as good coverage as Verizon. Just don't understand why this phone seems to go to the H (edge right?) When it should be on LTE. And then there are those times when the signal just goes away entirely.
Beta Build 8.1.0 solved a lot of the freeze ups on the phone, but it also came with some network issues it seemed. I went back to 7.1.1 and then the freezes started again.
Somewhere on these forums I read that if you were going to go back to nougat you needed to use the Sprint variant build (if you bought from.Sprint) rather than the " other" build. Not thinking I had to chose that, I went back and flashed that build, and something strange happened in the restore that hadn't happened before- all 168 apps where restored, but the homescreen remained blank. Call me superstitious, but without moving all the icons to the homescreen AND not adjusting to the largest display and next to the largest font .... This phone hasnt crash yet.
So then I try the beta again (since now it was sent to my phone rather than all the sideloading I had done before)....and I'm nearly 24 hours again without a crash.
If your phone makes you money like mine does on the weekend- it can't crash, the GPS has to work, oh and then there's that reception thing.
Are we getting closer to having it work consistently?
Oh and one more thing, after while I think some of my posts have no value, I'll admit that. I can't seem to delete my own posts on here. Is that possible?
Sent from my PH-1 using Tapatalk