Related
If you are an Epic Touch user that is experiencing the LOS (Loss of Signal) issue please click on the link below and report in that thread with Sprint.
http://community.sprint.com/baw/message/339779
If you do end up posting on the Sprint site please do post in this thread as well...
Also it was just pointed out that there also is a Samsung support Twitter @ www.twitter.com/samsungsupport
(Please also contact there if you experience LOS)
If you would like to follow this up with a call to tech support, it will help. Try and get transferred to advanced tech support.
This needs to happen from as many people experiencing this as possible!
Don't be lazy!
Thx!
There is another thread 11 down from this one(and multiple other ones further in the forum). The search button works wonders if you use it :-D
Sent from my SPH-D710 using XDA App
Double post
Sent from my SPH-D710 using XDA App
graffixnyc said:
There is another thread 11 down from this one(and multiple other ones further in the forum). The search button works wonders if you use it :-D
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
I don't think those other threads were specifically aimed at getting people to do this
I have been told by a reliable source that sprint is aware there is an issue and their engineers are working diligently to find a fix.
Sent from my SPH-D710 using Tapatalk
graffixnyc said:
There is another thread 11 down from this one(and multiple other ones further in the forum). The search button works wonders if you use it :-D
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Anything is better than "is our phone compatible with random tech blog rumor" threads.
Sent from my SPH-D710 using Tapatalk
kingsway8605 said:
I have been told by a reliable source that sprint is aware there is an issue and their engineers are working diligently to find a fix.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I hope your reliable source wasn't a Sprint CSR.
Those of us coming from the Moment were constantly being told that by Sprint regarding the radio lock up issue. They never did fix it. It wasn't until the devs at SDX got 2.2 onto the phone that the issue went away.
I have also found that tweeting complaints to www.twitter.com/samsungsupport during business hours will get a quick response, which results in escalation of real issues.
adma84 said:
I have also found that tweeting complaints to www.twitter.com/samsungsupport during business hours will get a quick response, which results in escalation of real issues.
Click to expand...
Click to collapse
Nice find! Thx!
i just got off the phone with sprint and they told me that samsung pushed an update on friday to fix a delay in receiving text messages which has borked the internal antenna. that would explain why i only started having problems yesterday.... sprint will give you a ticket number and they will fix your phone for free at a store.
call up and get it fixed.
its only going to get worse!
dtr145r said:
i just got off the phone with sprint and they told me that samsung pushed an update on friday to fix a delay in receiving text messages which has borked the internal antenna. that would explain why i only started having problems yesterday.... sprint will give you a ticket number and they will fix your phone for free at a store.
call up and get it fixed.
its only going to get worse!
Click to expand...
Click to collapse
This is false. The issue has been going long since before Friday.
It will be fixed in the first update though.
... and here I was thinking about exchanging my 3D for a GS2... it seems the signal problems are widespread to all phones. :/
Droga said:
... and here I was thinking about exchanging my 3D for a GS2... it seems the signal problems are widespread to all phones. :/
Click to expand...
Click to collapse
Its not a showstopper and it doesnt happen on all devices. So if it happens when you get it use your 30 swap to get a new replacement. It hasnt happened on mine at all. Also there is going to be a fix... So, with all of that said I cannot think of a single thing that should cause anyone to decide not to get this and choose another phone. Thx
DeeXii said:
Its not a showstopper and it doesnt happen on all devices. So if it happens when you get it use your 30 swap to get a new replacement.
Click to expand...
Click to collapse
It is a 14-day swap unless you bought your device pre-launch.
This is a total show stopper, I have 2 of these and they both do it constantly. I cant even surf for more then 10 minutes without it happening to both units. I cant make calls, I cant receive calls, cant go online, cant use streaming music, cant use navigation. total waste at this point. I love the phone physically and its great when on WiFi but that's only 1/4 of the day. I am not taking a chance of getting stuck with a phone that I cant even make calls on. maybe I will try again once everything gets fixed but for now its not worth the trouble.
davedave1234 said:
This is a total show stopper, I have 2 of these and they both do it constantly. I cant even surf for more then 10 minutes without it happening to both units. I cant make calls, I cant receive calls, cant go online, cant use streaming music, cant use navigation. total waste at this point. I love the phone physically and its great when on WiFi but that's only 1/4 of the day. I am not taking a chance of getting stuck with a phone that I cant even make calls on. maybe I will try again once everything gets fixed but for now its not worth the trouble.
Click to expand...
Click to collapse
You have something seriously wrong with yours then. I've had mine since launch and it's done it twice. You should exchange yours.
I rooted my phone and got this for the first time the next day. Hasn't happened before that. Didn't even know what you guys were seeing until it happened. I just got a zero with a line across the middle of it in my top bar and my signal bar and data icon were gone.
Is that what people are getting also that have not rooted their phone? When I say not rooted, not the people who rooted then installed the stock kernal back on. People who never rooted in the first place. That is what I would like to know.
Mine did it once before rooting, once after.
And yes, it happened just like you described. I thought rooting and flashing Zedo v3 fixed it, but it didn't.
clamknuckle said:
Mine did it once before rooting, once after.
And yes, it happened just like you described. I thought rooting and flashing Zedo v3 fixed it, but it didn't.
Click to expand...
Click to collapse
Cool, I hope it is device problem and not just a rooting problem. This way we can get a fix for it from Samsung, hopefully.
I have it on good authority it will be fixed in the first software update from Sprint. No idea when that will be though. It's not a rooting problem.
First of all let me point at that I am currently still a OG EVO user. This will probably be my next phone on DEC. 1 once I am due for a upgrade with Sprint. I really love the design and specs for this phone but I have been turned off by all the LOS talk.
If a phone can't maintain a working signal it isn't much good no matter how nice the screen or specs are.
After doing some research on what I hope will be my next phone, I've come to the conclusion that this is a hardware problem. From what I can gather these phones have some kind of defect with the internal antenna which is causing this problem.
This probably isn't news to anyone on these forums but I just wanted to get some confirmation on this. I'm hoping that if this is in fact that problem the next batch of these phones released around the holiday season will have this problem fixed.
Assuming this hardware problem is not fixed; is there any rom/kernel combination that is known to be most effective in terms of this LOS issue?
Na don't think it's a hardware issue, if so I believe it wouldn't be so random. With the LOStKernel I haven't had any more issues but others have. That being said, if it were a hardware issue i would've had los as well already.
Sent from my SPH-D710 using xda premium
I agree If this is Hardware issues that say the Antenna get low signal and then won't pick it back up. Then That Pickup is what needs to be fixed (and that is software). We've all had low signal or switched to Roaming. This is where the issue is, at least to me. The Low Signal strength maybe a 2nd issue but that may need a Power adjustment.
I also agree with the LOSKernel. I was averaging 1-2 a day and haven't had one in 3 days (I installed 3 days ago).
acrown said:
Na don't think it's a hardware issue, if so I believe it wouldn't be so random. With the LOStKernel I haven't had any more issues but others have. That being said, if it were a hardware issue i would've had los as well already.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Interesting. I was assuming that this was a hardware issue but you guys seem to think otherwise. I could care less as long as there a way to get the damn phone to work. I really want this phone!!!
ditto on the LOStKernal.
i used to have LOS daily about 8 times. now i havent had it in a week and i flashed it in a week.
=D
SantinoInc said:
Interesting. I was assuming that this was a hardware issue but you guys seem to think otherwise. I could care less as long as there a way to get the damn phone to work. I really want this phone!!!
Click to expand...
Click to collapse
Yeah, it's not hardware. The way the bug pops up is extremely circumstantial...so much so that we still don't know the parameters of the circumstance that triggers the bug. Having a low signal seems to have something to do with it but it has also occurred with full signal...but software changes seem to have a gigantic impact on it. I haven't seen one in weeks. I dunno....
I wouldn't be too concerned. I have the phone and I'm not.
...and it is a pretty bad-ass phone. If you are already a Sprint subscriber you'll love it, especially coming from the Evo4G.
I have never had LOS.
Sent from my SPH-D710 using XDA App
I'm thinking this is definitely software related, I personally didn't have a LOS problem until I started flashing kernels.Even on the Loskernel I was experiencing several LOS a day, flashed back to stock rom/kernel and haven't had a problem. From what I have experienced, Los seems to correlate with the phone roaming off of the sprint network and unable to connect back.
Sent from my SPH-D710 using XDA App
Its software. I haven't had LOS since the day the phone came out.
Sent From My Evo Killer!!!
Its a modem issue the kernel can only help so much. Samsung will be releasing a new modem.bin when they give us the maintenance update.
No it's a sprint problem my phone is fully flashed to ntelos and I have been trying to get los since monday even trying different kernels and roms I just cant produce los
Sent from my Galaxy S2 using Tapatalk
I've seen a couple posts saying the LoS issue is related to roaming off/on the Sprint network...this may be true to a certain extent but I sit 5 feet from an Airave and I'll get LoS a few times a day when at home. Happens just as often if not more when I'm out and about.
On a more related note, OP: this phone is great and they will fix the phone somehow or make good on it. If for some reason they haven't solved the problem and you are over the 14-30 days (maybe even waaaayyyy past that...months!) then they will take the phone back. If you can't get them to give you a free Photon or basically whatever you want, then you are a pushover! Just have to start making a papertrail for your issue, that is all really.
Would that necessarily rule out that the air wave itself is not roaming or losing/regaining signal throughout the day affecting your phone?
Sent from my SPH-D710 using XDA App
vdub804 said:
No it's a sprint problem my phone is fully flashed to ntelos and I have been trying to get los since monday even trying different kernels and roms I just cant produce los
Sent from my Galaxy S2 using Tapatalk
Click to expand...
Click to collapse
Its not a Sprint issue.
Its a Samsung issue.
That's been confirmed by developers.
ClutchR1 said:
Would that necessarily rule out that the air wave itself is not roaming or losing/regaining signal throughout the day affecting your phone?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
I have an Airave in my house and do not have any connectivity issues at all to it. I am also using a phone that has not been rooted and have yet to get an LOS either.
My point is that if the air wave is losing connectivity at all, then your phone is as well forcing it to roam
Sent from my SPH-D710 using XDA App
I never got LOS until I started flashing(about 3 days )
I was getting once per day utill the Lost kernel came along, now I've only had 1 LOS in the 10 days or so since the kernel has been out. I definitely believe it's software or modem related.
Bad ass phone nonetheless...dont hesitate!
Love this phone. Got it launch day and have never experienced a single LOS. I've never tried to root it or install a custom kernel.
Stock rom and not rooted, never had LOS.
I only have had LOS when I installed a ROM a long time ago.. Have had no problems on stock rom, stock kernel, rooted
As many, many other users of the galaxy nexus have reported, I am having some miserable signal problems. Obviously, CDMA nexus here.
I wish the issue was only that the signal on my phone is bad, but unfortunately it extends beyond that: my entire signal is lost at times. Usually it's intermittent and will happen 4 or 5 times a day for only 30 seconds at most at a time, but sometime (Usually late at night), it will lose its signal for even an hour or two, and I'll watch the battery plummet from as high as 54% to 0 as it searches for a signal the whole time.
I realize this is nothing new for some, but I almost feel like the problem went away for the whole world except for me, due to the low volume of threads related to the issue at all on the boards here. At least, recent ones.
What are my options? I don't really like the idea of trading in my nexus for a refurbished phone. Is 4.03 supposed to solve this problem? I had also read that rooting and flashing radios doesn't make much of a difference. To those of you with the CDMA nexus, what have you done to alleviate this problem? Or are you waiting patiently for an update?
Thank you in advance.
If bought new then return as faulty. Easiest solution.
sent from my Nexus Prime using XDA app
Daramue said:
I realize this is nothing new for some, but I almost feel like the problem went away for the whole world except for me, due to the low volume of threads related to the issue at all on the boards here. At least, recent ones.
Click to expand...
Click to collapse
The problem didn't go away. Most people had to make the decision to either live with it or trade it in on a RAZR or Rezound.
Daramue said:
What are my options?
Click to expand...
Click to collapse
You could:
1. Trade it in for another GNex, on the "hopes" that yours is defective.
2. Trade it in for something else.
3. Live with it & wait it out on the hopes that someday Verizon will ship updated radios that will help. Current rumors say that could still be a couple of months away...
I am on the option 3 plan.
The leaked 4.0.3 radios have had limited & mixed results. For those who they do help, they don't seem to do a whole lot. There are a couple of people who had really good luck. Pretty much the same story for those of us who got Hardware version 10 phones - Haven't noticed any appreciable difference between it and the 9 I got on opening day.
Good luck!
strongergravity, thank you, that was extremely helpful; I was curious to how my fellow Nexus bretheren were dealing with the issue.
If a potential update can fix the radio, then I too will stick with number 3 as you have. Call me a masochist, but this thing is just too nice to part with.
Thank you very much for the detailed response.
Daramue said:
strongergravity, thank you, that was extremely helpful; I was curious to how my fellow Nexus bretheren were dealing with the issue.
If a potential update can fix the radio, then I too will stick with number 3 as you have. Call me a masochist, but this thing is just too nice to part with.
Thank you very much for the detailed response.
Click to expand...
Click to collapse
I just saw your thread right after I created the exact same one today! I was just wondering what you ended up doing. No one has answered definitively as to whether or not this is happening on all phones. If an exchange will fix it, I would gladly go tomorrow. I know most phones are having trouble with the 3g/4g handoff but that is not the same issue we are having. What do you think!?
Mike
Same problems I've experienced. I'm on my second gnex, same issues.
Also I pulled speed tests next to other Verizon 4g phones (razor,rezound,TB) they all had significantly higher speeds than mine . I did multiple tests around our site, they had at least twice the speed as mine.
The razr pulled three times my speed most the time. 30+mb/s vs 10
The thunderbolt was around twice as fast downloads but uploads were even.
And the rezound was double on both uploads and downloads
I used the speed test app and speakeasy online.
Sent from my Galaxy Nexus using Tapatalk
Another comparison I did was turning on airplane mode on and off on all phones simultaneously. And switching 3g only on/off. To see which phones would latch on to 4g first.
Again the gnex was the slowest.
I really wish we received an update to fix this I love this phone!
Sent from my Galaxy Nexus using Tapatalk
I posted this earlier on another thread hoping it will get more views here.
So, I'm having the same exact problems but i did a log cat to see what might be culprit.
I have narrowed it down to this:
02-08 11:21:51.912 E/IMSFW (415): IIL: Disconnected from '7467' socket
still have no idea what can cause it yet.
also if you switch to 3g it seems it doesn't happen so maybe its a sim problem on verizons lte network end?
11:22:40.029 E/IMSFW (415): ImsSMSInterface: Registration failed, go for retrying if isim nounce present
that's what i found so if anyone can clarify and maybe see if it is really on Verizons end as this is the 4th phone that has had this problem
I will be going to verizon tomorrow to "try" and get a new 4g sim card and see if that helps somewhat.
that1techguy said:
I posted this earlier on another thread hoping it will get more views here.
So, I'm having the same exact problems but i did a log cat to see what might be culprit.
I have narrowed it down to this:
02-08 11:21:51.912 E/IMSFW (415): IIL: Disconnected from '7467' socket
still have no idea what can cause it yet.
also if you switch to 3g it seems it doesn't happen so maybe its a sim problem on verizons lte network end?
11:22:40.029 E/IMSFW (415): ImsSMSInterface: Registration failed, go for retrying if isim nounce present
that's what i found so if anyone can clarify and maybe see if it is really on Verizons end as this is the 4th phone that has had this problem
I will be going to verizon tomorrow to "try" and get a new 4g sim card and see if that helps somewhat.
Click to expand...
Click to collapse
I just went to the store and swapped out my 4g sim card... I dropped two calls on the way home from the store so I'm not sure it helped at all. Hopefully it didn't make it worse though!
I also checked my speeds and service against some other phones in the store and the Droid Razr destroyed my nexus and some other stock nexus that were there usually 12mpbs vs my 8 and 1mbps upload vs their 3.
Well I got my issues fixed today I was on tech support for an hour and he suggested to go to a store and get the sim card replaced. And that solved all my issues
Another problem I had was when using the headset for calling the person on the other line would here themselves. This has also gone away, I am so relieved I love this phone and did not want to abandone it.
Well, I did a bit of a test.
I kept my phone on 3g the whole day: Signal did not drop even for a single MOMENT in the entire day. Sure, there are times where it was bad, but my connection never entirely dropped. This leads me to believe that the problem lies with transitioning between 3g and 4g, or perhaps is just entirely related to 4g.
With the LTE network, I will have anywhere between 3% - 50% time with "no signal." It's extremely annoying and I'll always watch as my battery tanks extremely fast.
Maybe it's worth replacing the SIM card or at least, pulling it and putting it back in. Posting this here for others that are troubleshooting this same problem. I'll report back.
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.
My brother has a GNex. He is not as tech savvy as I am, so I try to help him out when I can (update his rom, troubleshoot issues, etc.). It's a bit difficult because I live in Texas and he goes to school in North Carolina. Long story short, he is having problems with his phone. He is having issues where the phone will not have any signal at all (literally can't make calls or text or anything). It is not the area he is in because I visited him and had zero issues with my GNex. His phone also says it is December 31, 1999. I found a few threads from a quick Google search describing similar issues, although it seems to be a variety of phones having the issue (I can't post links here yet because I am a 'new' user. If you want to see the threads I posted, this same message is posted at droidHive under Help/Galaxy Nexus and at DroidJunk under General Gnex Discussion). This must be some Samsung issue. He had the problem while running stock 4.0.2. Verizon sent him a ‘certified like new’ replacement and that was okay for a few days, then he had the issue again. I put him on Tranquil Ice 4.0.4 and that fixed the issue for a few days, then it came back. This has all been within the last couple of months.
Basically, I am wondering if anyone has previously heard of this and/or know how to fix it? All of the threads I noted above seem to have died and have not resolved the issue.
Thanks in advance for any feedback.
(in case you are wondering, I have a GNex running Junk with no serious issues and I'm loving it)
Just to update, my brother did a battery pull and everything seems to be working properly for the time being.
I'm still interested to know if anyone has more information about the problem described in the OP.