Develop Bugs

When will the first update be out ?

Currently a Nexus-S 4G owner, thinking of getting the GS II, but keep reading so many issues with WiFi...Network/Radio...SMS text problems...I am scared to upgrade to the S II, until an update/patch is released to fix these issues I have read about.
Also my Nexus-S has pretty crap WiFi signal already, in my house with a great WiFi setup, it drops way too often, my EVO 4G was rock solid always connected.
Any news or opinions on this ?

Zorachus said:
Currently a Nexus-S 4G owner, thinking of getting the GS II, but keep reading so many issues with WiFi...Network/Radio...SMS text problems...I am scared to upgrade to the S II, until an update/patch is released to fix these issues I have read about.
Also my Nexus-S has pretty crap WiFi signal already, in my house with a great WiFi setup, it drops way too often, my EVO 4G was rock solid always connected.
Any news or opinions on this ?
Click to expand...
Click to collapse
Honestly, I haven't had ANY of these problems. Maybe I got one from a different batch because I was backordered.
My phone seemlessly goes from WiFi to 3G and back again without any intervention from me, in weak OR strong coverage areas. To my knowledge, all my texts have gone through.
I just rooted late last night (with the stock kernel), and so far I haven't had any issues, either.

No issues what so ever trust me. Ask stock phone. Always on wifi when at home. Wifi turns on and connects super quick. text calls come thru right away.
.: sent from my Samsung Galaxy S II Epic 4G Touch :.

I havent experienced any of those problems either.
Sent from my SPH-D710 using Tapatalk

Zorachus said:
Currently a Nexus-S 4G owner, thinking of getting the GS II, but keep reading so many issues with WiFi...Network/Radio...SMS text problems...I am scared to upgrade to the S II, until an update/patch is released to fix these issues I have read about.
Also my Nexus-S has pretty crap WiFi signal already, in my house with a great WiFi setup, it drops way too often, my EVO 4G was rock solid always connected.
Any news or opinions on this ?
Click to expand...
Click to collapse
All those issues are rooted phone issues not stock....
Sent from my SPH-D710 using xda premium

craigbailey1986 said:
All those issues are rooted phone issues not stock....
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
That's bs. Sorry.

nabbed said:
That's bs. Sorry.
Click to expand...
Click to collapse
I havent had a signal problem or anything listed in the other threads
If I got a phone that didnt do what I needed it to do I would exchange it untill I got one that worked.... (thank god best buy is honoring my 30 days rather than the 14) Update or not these "issues" are more in root users than stock....
Sent from my SPH-D710 using XDA App

The T-Mobile version is coming out with 2. 3. 5 which I saw the original gs2 got it and it boast performance alot I read I am wondering when we will get the 2. 3. 5 update
Sent from my SPH-D710 using XDA App

nate420 said:
I havent had a signal problem or anything listed in the other threads
If I got a phone that didnt do what I needed it to do I would exchange it untill I got one that worked.... (thank god best buy is honoring my 30 days rather than the 14) Update or not these "issues" are more in root users than stock....
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
That's bs
Sent from my SPH-D710 using xda premium

I guess any disagreement is bs to you guys....lol... sorry but no problems here on stock. But this thread will quickly turn into a troll thread so last post here
Sent from my SPH-D710 using xda premium

craigbailey1986 said:
I guess any disagreement is bs to you guys....lol... sorry but no problems here on stock. But this thread will quickly turn into a troll thread so last post here
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I agree 100% with your sentiment IRT the thread...but, I had 2 LOS in the 5 or 6 days I was rooted. I rooted and had another 2 over 2 or 3 days. Stock kernel reinstalled and I've been good so far, but, I think blaming the kernel is foolish. The problem occurred before I rooted and after I rooted.
Does the fact that I am now rooted with a stock kernel and haven't had the problem suggest to you that only rooted stock-kernels are without fault?

You guys know that you can have everything stock, including kernel/rom/recovery, except the rom would also be rooted by addition of su binary/apk/busybox?
I haven't had any los or any other severe issues before or after I rooted the phone.
It may be that since I live in a small university town, my towers aren't getting upgraded to rev b, but yours are. These issues may not have anything to do with the phone at all. Maybe it has something to do with the sprint maintenance timing.
Or maybe it's because some people bought their phones from third-party retailers, and the phones weren't properly activated.
Or maybe it's some commonly used app that people with problems have installed, and I and others don't have installed.

I've had minimal to no issues personally. And I've had none while using stock Kernel. Using i9000 kernel I had a few LOS, but infrequent.
I also owned the Nexus S...and this is BY FAR a better device from a connectivity comparison.
Remember that the complaints you see are misleading...in that people are more apt to post about an issue, versus those that don't. It's human nature.

rooting or not has NOTHING TO WITH THE ISSUES!!
- I have had a stock phone since the day it came out, and have "watchdog lite" installed, watchdog alerts me about 10-15 times a day that "suspend", "events/0", and "base system" in my phone are using over 50% CPU while the phone is sleeping... LOL, it JUST happened again while i was typing this...
- also had the LOS issues 2 times, has to restart the phone to get signal again
- once, i was in a call, and when i went to "end" the call, i could not click the end button... the other side wud NOT hang up because it was customer service, they r not allowed 2 hang up on a person... so i had 2 restart the phone to fix this
- sometimes i click the power button to wake the screen, n nothing happens for about 5 seconds... so i click the button again, and the screen turns on and back off right away... n den i have 2 click the button a 3rd time to wake the phone...
- sometimes app just close randomly, and if you try to open the app again, its begins from the VERY BEGINNING, so w.e. u were doing in the app is lost... this sucks for games, and if ur in the middle of something important
- when the phone is on charge, the keyboard sometimes acts weird, typing letters u never click... and also u have 2 touch the screen 2wice sometimes 2 make selections... only happens when on charge, u take it off charge, n its back 2 normal right away
cant think of anything else as of right now... but there are some issues in the phone that can most likely be fixed either via root, or thru a sprint update...

I had the nexus s 4g and due to the antenas that phone was practically unusable especially on wifi. The gs2 doesnt have any of those issues. This is the first phone since the evo 4g that has impressed me snd i have owned the evo 3d and photon as well.

craigbailey1986 said:
All those issues are rooted phone issues not stock....
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I seem to be having an issue with battery draw whenever wifi is on.
I'm not rooted, my phone is 100% unmodded. I haven't even installed a different launcher.

Im hoping for an update so my games dont continue to crap the bed 10 mins into them. Nothing like trying to lvl up in nova and never finishing an online match.
Sent from my SPH-D710 using xda premium

LOS can occur with or without the root. I've only experienced it once but it was in an area with good coverage and no one else with Sprint phones at my office encountered it when I did. It only happened once but I do NOT have a modified ET4G - it is stock. There is a detailed thread on this on android forums and it can occur with or without a root. Apparently it was listed on android forums or android police that this is a known issue. I don't use wifi but it seems to be a common issue for people using wifi from what has been reported.
That being said, I would highly recommend this phone to anyone looking to get a phone.

ipetloudog said:
Im hoping for an update so my games dont continue to crap the bed 10 mins into them. Nothing like trying to lvl up in nova and never finishing an online match.
Click to expand...
Click to collapse
Yeah... you would think that being unable to handle games for more than 10 minutes would have been something that the engineers would have caught during development...

I have had no issues either. I had one LOS after I flashed the rooted kernel. Went right back to stock kernel and no issues since. And none before the rooted kernel either.

Spint working with LOS customers

I called Sprint today to see what they will do for me since I have LOS. After being on the phone for 1/2 hour. They are shipping me a brand new ET4G. Just wanted to let everyone know so they can try it. I hope my new one will not have LOS.
Also for those how are rooted here is the link to the How to unroot thread if they are sending a new phone.
http://forum.xda-developers.com/showthread.php?t=1281287

Do all phones get LOS? or just certain phones?
I get it but once a day or twice. Never had more than 5 a day.

leyvatron said:
Do all phones get LOS? or just certain phones?
I get it but once a day or twice. Never had more than 5 a day.
Click to expand...
Click to collapse
I am on my 3rd phone including the 1 sprint is sending. My first one did not have LOS, but was overheating. From what I am seeing not all phones have LOS.
I have gotten days with no LOS then other days with 10+. It is not fun.

The only thing I get is that my battery is garbage. I dont think it overheats, I do have the Android OS bug that drains my battery.
LOS is not common on my end. Glad I don't get LOS 10+ times, I would be mad.

I had my original one returned form Sprint after the 14 day warranty. I spoke to advanced support and talked circles around him on the problems Im having so they send a new one. Now this new on isnt so much loosing Wifi and 3G like the other one, but it is making me reset it a couple times a day. My original one couldnt keep a signal for more than 5 seconds. IDK if Im gonna return this one or not, I just want a phone that works!!!!

leyvatron said:
Do all phones get LOS? or just certain phones?
I get it but once a day or twice. Never had more than 5 a day.
Click to expand...
Click to collapse
I got my myself, wife and son this phone on October 1. By the next Monday I had returned my phone due to LOS and on that Tuesday my son returned his. My wife has yet to experience LOS.
My son and I both rooted our phones. I have read posts that people who NEVER have rooted their phone have had this issue.

I have not rooted the phone and am running completely stock everything. I have major LOS issues. It seems they start mainly when the handoff from wifi to 3g/4g when leaving home or work and no longer being on the wifi network. I dont have too many issues if I keep wifi off all the time and just rely on the cell network for data.

I am working with someone in Dan Hessy's office and she has advised me there is nothing sprint can do without me taking this into a service center first.

LOLOL! You guys are all delusional. LOS is completely kernel dependent. It is not a hardware issue. There are way too many variables that could influence reception. It's people like you that raise our TEP costs. Thanks!

akarol said:
LOLOL! You guys are all delusional. LOS is completely kernel dependent. It is not a hardware issue. There are way too many variables that could influence reception. It's people like you that raise our TEP costs. Thanks!
Click to expand...
Click to collapse
Then fix the stock KERNEL.
Well lets see here. I paid for a phone and I pay for service. So I expect to be able to use my invesment the way it was intended. Losing my signal 5-10 times a day and having to constently reebot. Not a lot of fun in my book. And maybe unlike some people I can not constently watch my phone to check for LOS. In other words I may have LOS for hours before I even notice it.
I am not one to complain unless it is a legit issue.

akarol said:
LOLOL! You guys are all delusional. LOS is completely kernel dependent. It is not a hardware issue. There are way too many variables that could influence reception. It's people like you that raise our TEP costs. Thanks!
Click to expand...
Click to collapse
Sorry but if a pay $500 is bc I need a phone that works, with no this type of problems and I don't care if is hardware or is the kernel, I just need something that works and sprint and samsung are responsible and they need to fix it and we are not supposed to pay for their mistakes.

dmora01 said:
Sorry but if a pay $500 is bc I need a phone that works, with no this type of problems and I don't care if is hardware or is the kernel, I just need something that works and sprint and samsung are responsible and they need to fix it and we are not supposed to pay for their mistakes.
Click to expand...
Click to collapse
I agree 100%. Thank you.

dmora01 said:
Sorry but if a pay $500 is bc I need a phone that works, with no this type of problems and I don't care if is hardware or is the kernel, I just need something that works and sprint and samsung are responsible and they need to fix it and we are not supposed to pay for their mistakes.
Click to expand...
Click to collapse
Uhh he means it is kernel dependent as in custom XDA kernel dependent.
This problem almost never affects the stock kernel.

manekineko said:
Uhh he means it is kernel dependent as in custom XDA kernel dependent.
This problem almost never affects the stock kernel.
Click to expand...
Click to collapse
Well considering my first phone was an overheated disaster (no root complete stock). The one I am on now had LOS prior to root. So I rooted to hope for a fix. Also read the LOS forums and a lot of un-rooted users getting LOS.

manekineko said:
Uhh he means it is kernel dependent as in custom XDA kernel dependent.
This problem almost never affects the stock kernel.
Click to expand...
Click to collapse
Not true, it affected mine, and I never rooted.

manekineko said:
Uhh he means it is kernel dependent as in custom XDA kernel dependent.
This problem almost never affects the stock kernel.
Click to expand...
Click to collapse
If that was true, I would be a happy customer. I am not rooted, completely stock, and I get LOS.

dmora01 said:
Sorry but if a pay $500 is bc I need a phone that works, with no this type of problems and I don't care if is hardware or is the kernel, I just need something that works and sprint and samsung are responsible and they need to fix it and we are not supposed to pay for their mistakes.
Click to expand...
Click to collapse
I 100% agree
the LOS is pretty bad on mine, stock or other kernel, its less on stock though
the only saving grace is that I have quick boot on my home page, and this phone reboots the fastest ive ever seen, on any of my smart phones in the past
I just get concerned sometimes, since I have kids that I may miss messages or something
its still a killer phone though,

As much as I hate to say that replacing the phone isn't likely to fix the problem, I do encourage it so Sprint will push Samsung to fix this issue quicker. The more phone replacements, the more sprint spends money on replacing. Also, if it ends up costing more than simply fixing the problem in the first place, they'll be forced to fix it.

Amd4life said:
I 100% agree
the LOS is pretty bad on mine, stock or other kernel, its less on stock though
the only saving grace is that I have quick boot on my home page, and this phone reboots the fastest ive ever seen, on any of my smart phones in the past
I just get concerned sometimes, since I have kids that I may miss messages or something
its still a killer phone though,
Click to expand...
Click to collapse
Stock is not a phone that was rooted then loaded a stock kernel. Stock is an untouched device that has never been rooted in the first place. Based on my personal experience, true LOS with the zero and line do not happen on an out of the box untouched phone.
My untouched phone had no LOS for 4 days until it was rooted. Next 2 days had an LOS each day. Got a replacement phone last Friday. Kept it stock and haven't seen an LOS yet. That would be 6 days without an LOS.
I am convinced it is only happening on rooted or once rooted phones. If I get an LOS I won't be afraid to report it here but I am pretty confident I won't see it. I have used my phone in the exact locations and same instances so far and still no LOS.

I agree. I'm totally stock and I've had the LOS problem mind that it was 3 times now 3rd time being today as I was walking back into the APT and the call just dropped as I looked at my phone there was ZERO signal when I had full bars just seconds before that. So far it's not been as bad as others are having so I've not really looked into getting the phone replaced yet but it's something that I do keep my eyes on to see if/when I'm getting it and how often it might show up.
---------- Post added at 02:17 PM ---------- Previous post was at 02:14 PM ----------
[email protected] said:
Stock is not a phone that was rooted then loaded a stock kernel. Stock is an untouched device that has never been rooted in the first place. Based on my personal experience, true LOS with the zero and line do not happen on an out of the box untouched phone.
My untouched phone had no LOS for 4 days until it was rooted. Next 2 days had an LOS each day. Got a replacement phone last Friday. Kept it stock and haven't seen an LOS yet. That would be 6 days without an LOS.
I am convinced it is only happening on rooted or once rooted phones. If I get an LOS I won't be afraid to report it here but I am pretty confident I won't see it. I have used my phone in the exact locations and same instances so far and still no LOS.
Click to expand...
Click to collapse
I have a totally stock phone it's never been rooted since the day I got it almost 2 weeks ago and I have had LOS on it. I honestly do not think this is a rooted phone issue if that was the case I would never of had it at any point in time and I have. And like I said Stock never once rooted and have not thought about doing it yet.

Menu key menu pops up during low signal

I have an extremely annoying issue. I've seen some posts reporting this on various boards, but it seems most people throw a default answer out there that it's a hardware issue. I'll explain why I don't think that's the case.
The menu that comes up with you press the "menu" capacitive key has been popping up and down rapidly and repeatedly when I'm in a low signal area. This didn't start happening until after Samsung/Sprint fixed the LOS issue. I'm thinking it has something to do with the way they fixed it, which I don't have any technical or general knowledge of. Most of the time, the screen and keys will not be responsive unless I hit the power key to turn the screen off and turn it back on. It's even more annoying since it vibrates everytime the key is "pressed". I don't think this is simply a hardware issue as the only time this presents itself is the same times the LOS issue used to. I'm sure it's tied to that fix somehow.
Is anybody else having this issue? This may be a long shot, but I installed the LOS Checker zip, (I forgot which dev created it), and never uninstalled it, but I've upgraded many roms since then and don't think it would still be installed.
If any of you do have this issue, did you ever install that LOS Checker zip?
Rom= Blazer Rom EL29 v3.8
Kernel = rogue 1.4.1

Started happening to me recently as well. Im running Calks still on GB with ICS theme. I haven't paid attention to my signal when it happens but you are right, turning off the screen does stop it momentarily. I agree this may not be a hardware issue as well. I've just been bearing it because I plan on changing phones soon anyway.
Edit: It just started happening after this post. Signal was at 1 bar...
Epic-ly tapped from my Galaxy S II

Zoidpilot said:
Started happening to me recently as well. Im running Calks still on GB with ICS theme. I haven't paid attention to my signal when it happens but you are right, turning off the screen does stop it momentarily. I agree this may not be a hardware issue as well. I've just been bearing it because I plan on changing phones soon anyway.
Edit: It just started happening after this post. Signal was at 1 bar...
Epic-ly tapped from my Galaxy S II
Click to expand...
Click to collapse
Did you happen to install this? http://forum.xda-developers.com/showthread.php?t=1326569

Happens to me too. Menu button hitting itself at random times.
Sent from my SPH-D710 using xda premium

I have this same issue. I never realized it correlated with low signal. The issue cropped up 3 times today and each occurrence was with low signal. Good eye sir.
Do any of you undervolt or use a kernel that runs less than standard voltages?
My device is undervolted quite a bit and was wondering if it may be part of issue as i don't remember having this problem prior to that.
I am removing my undervolts and will report back if i still have this issue.
Sent from my SPH-D710 using Tapatalk

I'm on stock rooted. Always happens on different occasions. I just turn the screen on and off and usually it'll fix the problem
Sent from my SPH-D710 using xda premium

I was gonna post the same thing I just realized this morning that it always coincides with low signal
Sent from my SPH-D710 using xda premium

I think its a hardware issue. Im running the same setup on my replacement phone and haven't had the issue since.

I experienced this ever since I got the phone back in september but I didn't wise up until the 14 day period ended. there are two threads in the Q&A section concerning this, one that i started and another that i contributed to.
I would be trying to text and the menu button would pop up and i would accidently hit something on the menu that came up bc the button spazzes out randomly and consecutively and sometimes for a solid 5 seconds, but like the rest of you im sure, it wasnt confined to any single app so it was impossible to find one thing to blame. it would have to be something system-related or hardware-related (btw i did flash the LOS checker some time ago)
I believed the low signal theory for a while, as well as having a corrupted flash. but I experienced the spasms with full bars of service AND after a complete Odin restore to stock everything without restoring any of my past data whatsoever. thus I deferred to the "default" that it is hardware-related.
that was months ago.
I got so fed up with it, i decided to do anything to make it stop. So, I recently opened up my device and took everything apart and found that the water indicator just above the capacitive buttons had been activated. keep in mind I DID NOT EVER have any encounter with water. in fact, the other water indicators were perfectly undisturbed. this pissed me off because that means there might have been an accident or something while they were being manufactured that would have damaged the button - idk just another theory.
This is my main piece of evidence supporting my claim that it is hardware-related:
I ended up breaking the screen trying to separate the glass from the digitizer (stupid, I know bc theyre fused together) so I ended up buying a new screen/digitizer. put it in myself. i haven't had it since. I'm running the EXACT same set up as before I replaced my screen and its been about a week and no instances. I would be experiencing the sporadic menu button randomly, several times a day but it has completely disappeared.
i suggest to you all: bring it in to Sprint if you bought it from them or invest in a new screen off ebay if you bought it from a 3rd party seller (Amazon, wirefly, letstalk), i got my new screen for $65 shipped and it was in pristine condition. now im living a happily-ever-after ending
i'll keep a close eye on this thread to help you all with your endeavors/theories though
if any of you plan on opening up ur device, i suggest you do some homework so as not to destory your phone - its still an amazing device. or you can just ask in this thread and i can give tips to everyone
good luck!!

Thanks for all the updates.. I've noticed I'll sometimes get this error, but my phone will be showing full bars where I KNOW I have a poor signal.. for instance, my elevator at work..
Is there any sort of logging app I could run and go into an area I know this will happen to find out what's going on?

IsThisOneTaken said:
Thanks for all the updates.. I've noticed I'll sometimes get this error, but my phone will be showing full bars where I KNOW I have a poor signal.. for instance, my elevator at work..
Is there any sort of logging app I could run and go into an area I know this will happen to find out what's going on?
Click to expand...
Click to collapse
sometimes the signal bars are inaccurate (like you described). your true signal is found in settings>about phone>status>signal strength. 0-1 bars is really about -90 to -100 dBm
devs use logcats to analyze issues with the internals
http://forum.samdroid.net/f38/tutorial-how-get-logcat-example-check-battery-drain-2543/

I just checked a few other boards and it seems a number of people have confirmed it correlates wih low signal. There are a few people that keep popping up on multiple threads stating it's a hardware issue, only because a new screen fixed it. I would be fine with that logic if there weren't so many people stating it correlates with low signal. Also, it seems most people haven't really experienced this issue until after the LOS fix. Now, at the same times I used to have LOS issues, I now have this. I'm guessing it has something to do with internals and whatever they did to update it may be separate from modems or roms, since people have gone back to stock and still experienced this issue.
I haven't done a search, but is there an information source that states exactly what Samsung did to address the LOS issue?

I'm going to ODIN back to the original shipped EG30 package and test it out.. I never did OTA updates.. always through ODIN, etc. I'm going to see if I update through OTAs if anything is different. I'll report back.

I had experienced it since around the 1st week of october. i didnt have los fixed until i flashed chris41g's experimental kernels, not sure when all that was though. i was convinced it was related to signal too, but i would still happen on the highway/in public with 3 bars of 4g and ~50-60 dBm
would be interesting if you figure it out though

Yea I ODIN'd back to EG30 and now OTA'd to EL29.. no issues yet but we'll see tomorrow when I'm in elevators. After doing all this, I realized I probably need to do a full EEPROM reset and then go through this... don't really feel like doing that tonight though.

Im pretty sure this is in fact a samsung phone issue in general. I came over to sprint and the e4gt from verizon and the fascinate. I loved that phone, but it had this exact same issue. I have not in fact had it happen to me so far with the e4gt yet. I have a sneaking suspiscion that this issue goes hand in hand with undervolting, but thats just my own personaly theory.
Sent from my SPH-D710 using Tapatalk

Happens to me on the rare occasion as well. Might be an issue with the phone?

I called this one during the LOS era. It definitely occurs in low signal areas. I could never get LOS so I went into known dead spots and sure enough those random pop ups happened
Sent from my Nexus S 4G using xda premium

*Luke* said:
Im pretty sure this is in fact a samsung phone issue in general. I came over to sprint and the e4gt from verizon and the fascinate. I loved that phone, but it had this exact same issue. I have not in fact had it happen to me so far with the e4gt yet. I have a sneaking suspiscion that this issue goes hand in hand with undervolting, but thats just my own personaly theory.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I noticed there were a few other threads on Samsung devices with issues.... hmmm. Did you ever try limiting your underclocking to a higher clock speed? This may be a noob question but for the EG4T, is anything less than 800mhz considered underclocking?

JohnCorleone said:
I called this one during the LOS era. It definitely occurs in low signal areas. I could never get LOS so I went into known dead spots and sure enough those random pop ups happened
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I believe I remember seeing your post haha... I'll see what I can do if I mess around with clock speed.

Signal consistently going from full to none.

I'll try to be succinct here. I got a replacement Nexus from Asurion when my screen cracked earlier this month. Incidentally, this was also around the time I started flashing Jelly Bean ROMs rather consistently. I have been experiencing (what I would actually refer to as) a crippling issue where my phone's signal will just completely drop. As in, no calls, no texts, no anything. Mobile network connection is gone. And while it does do it in my apartment, which has shoddy reception in the first place, it's doing it just as much when I'm in the middle of Best Buy, or a bar, or anywhere with FULL 4G. It will simply go from 4 bars to no service and then back to 4G (once the radio presumably cycles).
Do you guys think this is a hardware issue or a Jelly Bean issue? I've run two different ROMs overall (Jelly Belly and PARANOIDANDROID), so I've hit both the CM10 and non-CM10 ends of the spectrum and they're both doing it, so that leads me to believe that it's not a specific ROM issue, but either an overall Jelly Bean issue or a hardware malfunction. Any advice would be greatly appreciated. Thanks in advance.

enigmaisdead said:
I'll try to be succinct here. I got a replacement Nexus from Asurion when my screen cracked earlier this month. Incidentally, this was also around the time I started flashing Jelly Bean ROMs rather consistently. I have been experiencing (what I would actually refer to as) a crippling issue where my phone's signal will just completely drop. As in, no calls, no texts, no anything. Mobile network connection is gone. And while it does do it in my apartment, which has shoddy reception in the first place, it's doing it just as much when I'm in the middle of Best Buy, or a bar, or anywhere with FULL 4G. It will simply go from 4 bars to no service and then back to 4G (once the radio presumably cycles).
Do you guys think this is a hardware issue or a Jelly Bean issue? I've run two different ROMs overall (Jelly Belly and PARANOIDANDROID), so I've hit both the CM10 and non-CM10 ends of the spectrum and they're both doing it, so that leads me to believe that it's not a specific ROM issue, but either an overall Jelly Bean issue or a hardware malfunction. Any advice would be greatly appreciated. Thanks in advance.
Click to expand...
Click to collapse
I have the same issue with my phone. I have actually gotten 3 new phones only to have them all do the same thing. I flashed to Jelly Bean hoping it would fix the issue but no luck.

Sounds like a hardware issue. I have flashed many roms, ICS and JB and all are good for reception. Once we got new radios 5 months ago it fixed my 3g to 4g handoffs when I would lose data for minutes if not an hour. All good now.

It's common issue for Google nexus. I am also having same problem. You may ask a replacement or switch network mode to "CDMA only" instead of "LTE/CDMA".
Sent from my Galaxy Nexus using Tapatalk 2

It happens to my Galaxy Nexus too. >_<

Happens to me too. From HSPA (which should bei constant high-quality in my area) down to 2G, and if I am in areas with bad coverage, it looses signal completely.
Finally, after several ROMs, and basebands haven't fixed it, I'm going to send it in, as soon as possible now.
Sent from my Galaxy Nexus using xda app-developers app

This is a hardware issue. I515.10 is the one I have and it does this as well, the I515.9 however does not seem to be affected. The .10 was made in china and the .9 in korea... or maybe the other way around, hell who cares... Bottom line is, its a huge issue that samsung should have addressed long ago.
For more info check out the samsung forums. I'm waiting on a replacement to come Monday.
Sent from my VS910 4G using xda app-developers app

Same thing
This is happening on mine too. I installed the stock rom on my Verizon GNex and the signal has deteriorated significantly, almost like 4.0.2
I'm hoping a fix, or the new binaries fix this issues and put it back to it's 4.0.4 state.

I am still plagued by this. Anybody know of any fixes in the works? I have exchanged my phone 4 times to no avail.

Crandolph2001 said:
I am still plagued by this. Anybody know of any fixes in the works? I have exchanged my phone 4 times to no avail.
Click to expand...
Click to collapse
It's an issue with a certain batch of phones. All the ones I had that had issues were either manufactured in January or February (says 12.01 or 12.02 under the battery). I was finally able to get a new replacement at a Verizon store thanks to knowing the manager and it was just manufactured in July (12.07) and has worked like a charm (except a single stuck pixel in the upper right-hand corner, but I don't see it unless I'm looking for it, so I'll deal).

enigmaisdead said:
It's an issue with a certain batch of phones. All the ones I had that had issues were either manufactured in January or February (says 12.01 or 12.02 under the battery). I was finally able to get a new replacement at a Verizon store thanks to knowing the manager and it was just manufactured in July (12.07) and has worked like a charm (except a single stuck pixel in the upper right-hand corner, but I don't see it unless I'm looking for it, so I'll deal).
Click to expand...
Click to collapse
My current phone says it was manufactured 7/11/12 in China. I thought it was going to behave at first but the problem showed it's ugly head several days later.

Crandolph2001 said:
My current phone says it was manufactured 7/11/12 in China. I thought it was going to behave at first but the problem showed it's ugly head several days later.
Click to expand...
Click to collapse
That's strange. In my experience, it should either be screwed up totally or not at all. It shouldn't gradually onset. You sure it's not a ROM and/or radio issue this time that's just exhibiting similar symptoms?

enigmaisdead said:
That's strange. In my experience, it should either be screwed up totally or not at all. It shouldn't gradually onset. You sure it's not a ROM and/or radio issue this time that's just exhibiting similar symptoms?
Click to expand...
Click to collapse
When it started acting up I hadn't rooted / romed yet. I am now rooted and have flashed to 4 different roms and every single one of them still had the issue. I may have had the issue on the first couple days and not noticed it for whatever reason...

"Ghost Touch" Issues

Idk if some of you have heard about the "ghost touch" thing where sometimes when you turn on the screen it'd be like someone was pushing on some of your capacitive buttons and you wouldn't be able to touch or do anything on the screen. Turning off the screen for a couple seconds and turning it on again helps alleviate the problem for me.
How common of a problem is this? It seems that this never used to happen until ICS came around. Is it due to software or hardware like a bad digitizer? Is this something that I should be worried about hardware wise because I'm planning on hanging onto this phone for at least another 6 months and warranty's going to be up soon in a week or two. I'm using The Goodness ROM and agat's kernel if that matters at all. Any input is appreciated. Thanks.

Rf interference with the touchscreen controller in low signal areas.
It happens on some other Samsung phones as well.
Sent from my Galaxy Nexus using xda app-developers app

Thank you times. I have been wondering what that was.
sent from my BAD A$$ Epic touch

It used to happen to me all the time, but it hasn't happened in a few months.

It happened a lot on my first etch, but hasn't happened once on my replacement.
Sent from my SPH-D710 using Tapatalk 2

Hello. Thank you for all the replies. So overall, is this something that I should be worried about concerning the longevity of my phone? It happens quite often now like maybe 5 times a day when it used to be only once in a long while.

Yup times is right. This happened a lot to me when ICS leaks first came out way back in Feb ?
Sent from my SPH-D710 using Tapatalk 2

Happened to me alot but been much better since using cm10 mabe once ever 3 days instead of 25 times a day
Sent from my SPH-D710 using xda premium

http://forum.xda-developers.com/showthread.php?t=1551580
After trying to figure out what nearby was causing the RF intererence so I could eliminate it, I found this thread which explains that the interference originates in the phones 3G radio, not the environment. I just recently started having this problem, and from reading that thread, I think I didn't notice it before only because I was using a kernel with a fix integrated. So if you are having this problem and don't want to do surgery on your phone, maybe try to find a kernel with the software patch.

SupraLance said:
http://forum.xda-developers.com/showthread.php?t=1551580
After trying to figure out what nearby was causing the RF intererence so I could eliminate it, I found this thread which explains that the interference originates in the phones 3G radio, not the environment. I just recently started having this problem, and from reading that thread, I think I didn't notice it before only because I was using a kernel with a fix integrated. So if you are having this problem and don't want to do surgery on your phone, maybe try to find a kernel with the software patch.
Click to expand...
Click to collapse
Kernels fixed this? Waaah? Where have I been?
Sent from my SPH-D710 using xda premium

This has been happening like crazy lately, ever since Hurricane Sandy and also since running the FK09 JB leak. The Sprint signal in my area went from bad to garbage since the hurricane, not sure if the JB leak is also adding to it or not.
It is so annoying I am tempted to actually buy a different phone even though I love the E4GT.

Raistlin1 said:
This has been happening like crazy lately, ever since Hurricane Sandy and also since running the FK09 JB leak. The Sprint signal in my area went from bad to garbage since the hurricane, not sure if the JB leak is also adding to it or not.
It is so annoying I am tempted to actually buy a different phone even though I love the E4GT.
Click to expand...
Click to collapse
Agreed Sprint screwed NJ hard as AT&T and Verizon restored services within a week...
On a side note, AT&T's LTE was up and running within 48 hours...Dunno about Verizon cause most of my friends have iPhone's with them. But I was roaming on Verizon full bars the whole time. But guess what happened when I tried to make a call? "Welcome to Verizon, please have a phone card or credit card at handy to make a call". I have roaming under my plan and I would like to use it...especially not crapping out in emergencies.
Sent from my SPH-D710 using xda premium