Develop Bugs

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.

[Q] Galaxy Nexus Dropping Data?

So normally I run my phone on Wifi because it saves battery when i'm on my university campus all day. So last night I headed off campus and so I turned off WiFi, and it didn't want to connect to data. Just sat there (with full service) but no data connectivity. So I rebooted the phone. still no connection, turned on airplane mode and then back off, now it worked but only for about 3 minutes I had 4G with blue sync and everything, then it dropped off. I went out into a rural area and I kept having full signal but no 3G. So I thought it was the rom. I was running AOKP b25 (Team Kang) so I just updated to Milestone 4. Everything was going well in initial setup of the phone, I had 4G signal, then halfway through setup the 4G dropped off. So I turned on Wifi and got everything setup. Turned off Wifi and it hooked to 4G almost immediately. Then about 3 minutes later, it dropped again. So at this point i'm really hoping it's not my phone and it's Verizon. I've never had a single issue before (i've had the phone since December) with data not connecting like this. It just started last night, which made me think it was Verizon and maybe it had to do with the Solar Flares or something? Has anyone had a similar issue and have any idea of what I might try?

Hi
I was just about to post the same thing. I'm experiencing the same, Data and service keeps dropping, I just got the phone Wednesday and since then It's been doing it. It's very frustrating, and I'm also on Verizon.
Someone else experiencing the same? Could Verizon be the responsible here and not the phone?

And if it helps, i'm located in Norman, OK

JGeZau said:
Hi
I was just about to post the same thing. I'm experiencing the same, Data and service keeps dropping, I just got the phone Wednesday and since then It's been doing it. It's very frustrating, and I'm also on Verizon.
Someone else experiencing the same? Could Verizon be the responsible here and not the phone?
Click to expand...
Click to collapse
It's the phone, there's numerous threads about it (the Verizon version.) There's an expected software fix supposedly coming out this month sometime to fix it, that's all we know.

If it's the phone and an update will fix it, then why is it still doing it with a custom ROM? Do the custom ROMs not have the fix in place? I was under the impression that most of the things Verizon releases OTA to fix issues dont' happen in custom ROMS.

zacelliott said:
And if it helps, i'm located in Norman, OK
Click to expand...
Click to collapse
Hey, we are 4hr away from each other. I'm in Rogers AR
spencer88 said:
It's the phone, there's numerous threads about it (the Verizon version.) There's an expected software fix supposedly coming out this month sometime to fix it, that's all we know.
Click to expand...
Click to collapse
Thank you I'll start digging up in some other threads

zacelliott said:
If it's the phone and an update will fix it, then why is it still doing it with a custom ROM? Do the custom ROMs not have the fix in place? I was under the impression that most of the things Verizon releases OTA to fix issues dont' happen in custom ROMS.
Click to expand...
Click to collapse
Samsung is going to hopefully release a radio update that fixes it, which isn't found in custom rom's because it hasn't been released outside of samsung yet.

It's kinda weird though that this JUST happened last night suddenly, the signal has been flawless since I bought it so that's why I thought it was Verizon because I guess I figured if it was the phone it would have been doing it all along and not stop working all of a sudden.

It's the phone and a software update won't fix it. I've tried every radio out there, none solved the issue. I got the phone swapped over a week ago, it is still stock, and the issue hasn't returned. Theres an ongoing thread over at rootz about this.
I can't post the link but it's there. many members are reporting that replacing the device solves the issue.

this was verizon. it happened to me, went away by itself.
that being said, ive had the best handoffs using the 4.0.4 and 4.0.3 radios. try one of those, or a hybrid package.

I went to the Verizon store and they gave me a new SIM Card. Now it works!

willstilson said:
It's the phone and a software update won't fix it. I've tried every radio out there, none solved the issue. I got the phone swapped over a week ago, it is still stock, and the issue hasn't returned. Theres an ongoing thread over at rootz about this.
I can't post the link but it's there. many members are reporting that replacing the device solves the issue.
Click to expand...
Click to collapse
First of all you don't know what you're talking about. It may be a hardware issue it may be a software issue. There is no way to tell at this point. You are trying leaked radios, good job that proves nothing. If Samsung is aware of the issue and working on a new radio you haven't tried it yet. Sit back and relax until the update comes out. Then we can go from there.

SirVilhelm said:
First of all you don't know what you're talking about. It may be a hardware issue it may be a software issue. There is no way to tell at this point. You are trying leaked radios, good job that proves nothing. If Samsung is aware of the issue and working on a new radio you haven't tried it yet. Sit back and relax until the update comes out. Then we can go from there.
Click to expand...
Click to collapse
Wow dude, no need to get insulting. I was merely sharing my experience with a frustrated OP. If you want to blindly believe that there can't be anything wrong with certain devices, until the manufacturer comes out and says it, then more power to you. You are the consumer that ever manufacturer loves. Myself and many others over at Rootzwiki have found success by having our devices replaced. When I tell you that it is night and day difference, it is not a lie.
I agree with you about the leaked radios. If they don't work then it proves nothing. They are leaked and probably not finished. The reason I mentioned them in the first place is because many people tend to suggest trying them to solve signal issues. I was explaining that I have tried them and it did not work. What worked was swapping the defective phone.

[Q] GNex reception and date issue

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.

My Samsung Galaxy Nexus Nightmare

Hey guys ever since getting this phone ive been having to keep getting replacements for it and it still havent fixed the various problems that ive had with this phone.
1. microphone will cut out during calls and sound will stop working.
This problem has been resolved from getting a replacement through verizon's warranty program.
After receiving my replacement however, i am now getting the signal drop issue where the only way for the phone to work is putting it in CDMA mode. Ive researched online and found that various other people have been experiencing the same problem with their galaxy nexus. So i go to the store to order another replacement.
After receiving my 3rd replacement, still no luck. This phone is still experiencing the same problem has the last where the signal would randomly keep dropping. So i go back into the store and decide to switch out the sim card for the phone and order another replacement.
The 4th replacement comes in and to still no surprise the signal keeps dropping off. I found that both korean made phones and chinese made phones are experiencing the same problem. Ive changed my SIM card, rooted and unrooted, tried various roms, updated to the unofficial 4.1 jelly bean update and still nothing fixes this damn radio problem.
Im so fed up with this phone but if anyone has any suggestions it would be greatly appreciated as i have no idea how to get a working galaxy nexus and have never experienced a working one still. I would KILL to get a phone that actually keeps a 4g signal ><

This should not be in development.

Oi...
I don't quite understand the purpose of these threads...
For reference, this is the development forum despite the Verizon designation. Releases only here.
Sent from my Galaxy Nexus using Tapatalk 2

dmeadows013 said:
This should not be in development.
Click to expand...
Click to collapse
oops sorry will move my post to general.

Can't find download links for your rom.
oh wait...

There is nothing you can do except to keep getting replacements. No software will fix your issue at this time.
I just received a replacement yesterday as my phone's radios, voice and data would disconnect and only a reboot would fix it. Today I made it through the day without it happening once on my replacement. Still not convinced it is the device though until I go a few days without it happening.
If it happens with this one, I would say it is more of software radio issue and not the physical device and Samsung needs to do something about it.
So, I will see how it goes over the next few days. If this one continues to work, then it could possibly be the device. I My first GNEX though would not keep 4G for more then a minute and jump off, then on, then 3G, then 4G. To me that was the device. My next one would just lose it after a few hours, otherwise it was fine....
Let's hope the 3rd one is a charm.

Try updating the radio and is it possible you live in a area where signal is poor. I haven't had an issue at all with my nexus
Sent from my Galaxy Nexus using xda premium

tbis said:
Try updating the radio and is it possible you live in a area where signal is poor. I haven't had an issue at all with my nexus
Sent from my Galaxy Nexus using xda premium[/QUOT
currenly using the latest from official 4.0.4
tried the many hybrid radios too out there and its still doing this. you must have gotten lucky then, ive been experiencing this ever since i got the phone
Click to expand...
Click to collapse

"like new" replacement improperly tested
Jooining the club.... I had a relatively well functioning gnex until about 2 weeks ago, it did reboot once in a while, but oh well. Then it totally died suddenly. Tried to revive it to save data, but to no avail. So here you come Verizon "like new" replacement..... :fingers-crossed:
Oh no....well sure enough, started to have problems with dropped connectivity data + voice immediately after init.
Previous phone never did it. And it is doing this over a huge urban city.... I was careful in transferring my SIM as well.
there a slew of threads around forums discussing this issue and related (among others see through https://code.google.com/p/android/issues/detail?id=24345"]https://code.google.com/p/android/issues/detail?id=24345
Is is time for class action against Verizon for improper testing procedures and wrongly sending faulty devices as new (which they can pass along to Samsung since ultimately, it is probably Samsung who is playing dumb) ?

deejaycin said:
Hey guys ever since getting this phone ive been having to keep getting replacements for it and it still havent fixed the various problems that ive had with this phone.
1. microphone will cut out during calls and sound will stop working.
This problem has been resolved from getting a replacement through verizon's warranty program.
After receiving my replacement however, i am now getting the signal drop issue where the only way for the phone to work is putting it in CDMA mode. Ive researched online and found that various other people have been experiencing the same problem with their galaxy nexus. So i go to the store to order another replacement.
After receiving my 3rd replacement, still no luck. This phone is still experiencing the same problem has the last where the signal would randomly keep dropping. So i go back into the store and decide to switch out the sim card for the phone and order another replacement.
The 4th replacement comes in and to still no surprise the signal keeps dropping off. I found that both korean made phones and chinese made phones are experiencing the same problem. Ive changed my SIM card, rooted and unrooted, tried various roms, updated to the unofficial 4.1 jelly bean update and still nothing fixes this damn radio problem.
Im so fed up with this phone but if anyone has any suggestions it would be greatly appreciated as i have no idea how to get a working galaxy nexus and have never experienced a working one still. I would KILL to get a phone that actually keeps a 4g signal ><
Click to expand...
Click to collapse
This is the VZW development thread. You'll find better responses /answers to your questions in the proper forum.
XDA Mods please move to proper thread.

Thread moved. Please do not post general threads or questions in the development section. Thank you.
---Jay--- From the GNex

USB and ROMs

Do any of the non stock ROMs handle USB any better than stock?
I thought the issues that plagued this phone early on had been resolved and all of a sudden they are all back. And looking through the forum here, I'm not the only one. Given this phone is a generation old I'd imagine it's not going to get much love from Google. So maybe modding is the answer.
Thanks!