Hello,
I have been experiencing a bug where the phone acts as if there has been a long press of the search button (and the appropriate dialog comes up) when I have not touched the search button at all! (I am not pressing it by accident, it will do this while sitting on a table untouched). When it happens, the search button is not lit up (as if it were pressed), and none of the other buttons can be pressed, nor can anything on the screen, other than responding to the dialog. This can last two to four seconds (it's REALLY annoying). What's worse is that this can happen up to once a minute sometimes!
I've discovered that this happens only when I have 3g data turned on. When data is off, or when on wifi only, it does not occur.
Is anyone else having this problem, and (hopefully) has found a fix? I did do a search (both on Google and in here). I discovered a Google forum where people talk about experiencing the problem (a Google employee chimes in with questions) but no solution as of yet. I was hoping to find something about this in Xda, but as stated, couldn't find anything Though this person may be talking about the same problem:
http://forum.xda-developers.com/showthread.php?t=1069765
Here is the link for the Google forum:
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
Since it only happens when 3g data is turned on, could it be my radio image? Or something else? Any help or thoughts would be greatly appreciated! My current running specs below:
Nexus S
Android Version 2.3.3
Baseband version NO DGSXKD1
Kernel Version 2.6.35.7-g1 d030a7 [email protected] #1
Mod Version Cyanogenmod-7.0.3-NS
Build Number GRI40
Model number GT 19020A (originally bought from a Telus Store) currently running on Bell Mobility
Rooted, bootloader unlocked
I was about to post this exact thread! I am having the same issue with my NS i9020a running stock unrooted 2.3.4. I to have noticed a link between data connection type and the issue occuring. One theory i read said that static charge may be to blame?... but that didn't seem right to me....
Anyway... I would also love some more info on this subject of anyone has any input. I bought my phone off ebay less than a week ago, and if the issue is hardware i am going to have to file a claim with paypal...
Sent from my Nexus S using Tapatalk
This is exactly what I posted in a separate thread. However, I'm not sure about the 2G / 3G changing.
I'll experiment.
Which radio are you using - seems like this was at least temporarily related to my switch to KD1 ?
Sent from my Nexus S using XDA Premium App
I reflashed radio KB3 and problem , at least for now is not happening. It was almost making the phone unusable this am earlier before changing radio
??!
Sent from my Nexus S using XDA Premium App
How can I find what radio I am using? Also, How long have the two of you had your devices? Is this issue something that manifested after you changed something on your phone (thus indicating it is not hardware related) or has it always been there? Thx, and i hope we can get this sorted out.
Cheers
Settings > About. Then look for Baseband version
I've had about three or four weeks. Not sure unless this radio change theory is correct
Sent from my Nexus S using XDA Premium App
jcrompton said:
Settings > About. Then look for Baseband version
I've had about three or four weeks. Not sure unless this radio change theory is correct
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Baseband Version
NO DGSXXKD1
Kernel version
2.6.35.7-ge382d80
[email protected] #1
Build number
GRJ22
Please update as to whether the radio change is a permanent fix. Thx.
Cheers
Edit: I am assuming that this (NO DGSXXKD1) is the KD1 radio that you switched to and are theorizing may be the culprit...it is also something that all three of our devices have in common. I am eager to see if changing the radio permanently fixes your issue.
I'm on a Telus 9020a radio KB3 and i have the same problem.
Not sure at this point what the deal is! But changing from the upgraded radio KD1 back to KB3 has up to this point solved the issue. Maybe six or seven hours without the phantom search firing.
????
Sent from my Nexus S using XDA Premium App
Currently there is no stock 2.3.4 for the i9020a. The no xxxxkb1 is a result of forcing the update from the t version. Since the a version uses didn't frequencies, I'm not sure about it's reliability.The ota has yet to be released and this tells me that our phone has something different
I see this issue also however I get it more when using gps. I have my phone vent mounted and I am suspecting heat might be the issue
Sent from my Nexus S
Matridom said:
Currently there is no stock 2.3.4 for the i9020a. The no xxxxkb1 is a result of forcing the update from the t version. Since the a version uses didn't frequencies, I'm not sure about it's reliability.The ota has yet to be released and this tells me that our phone has something different
I see this issue also however I get it more when using gps. I have my phone vent mounted and I am suspecting heat might be the issue
Sent from my Nexus S
Click to expand...
Click to collapse
Interesting, I don't know what was done to my phone before it was in my possession but when I received it it was running stock 2.3.3 and on first boot after setup i received a popup notifying me that there was a system update available. I selected install and it did its thing and now I have 2.3.4. Is there a way to revert the device back to the software it is supposed to have on it?
Cheers
Sent from my SCH-I500 using Tapatalk
Hey guys, got the Sprint Nexus S 4g just this last Friday. Phantom search button presses and long presses started up soon after. Still going on now. Have not been able to narrow down culprit as far as 3G/4G/Wifi go. Running completely stock everything:
Android 2.3.4
Baseband D720SPRKD8
Kernel 2.6.35.7ge382d80 [email protected] #1
Build Number GRJ22
Just thought I'd add my stat to the growing list.
Sophos1 said:
Interesting, I don't know what was done to my phone before it was in my possession but when I received it it was running stock 2.3.3 and on first boot after setup i received a popup notifying me that there was a system update available. I selected install and it did its thing and now I have 2.3.4. Is there a way to revert the device back to the software it is supposed to have on it?
Cheers
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I'm on my phone so it's as little hard to link. In the general section there is a thread to a stock nandroid backup with the kb3 modem.
Sent from my Nexus S
I've now been about 9 or 10 hours after switching back to KB3 - no more issues yet! Pretty strange huh?
Sent from my Nexus S using XDA Premium App
Finally got my device rooted and switch to the KB3 radio.... it's has been a few hours and I have yet to experience the search button bug. I'm crossing my fingers that you found the solution! Thx.
Sent from my Nexus S using Tapatalk
Ok. So it's now been almost 24 hours. No repetitive firing of the search button on my Nexus S since flashing back to the KB3 radio.
Beware anyone experiencing this should not flash to the KD1 radio. I have a 9020a device. I assume it is Canadian since it had ATT 3G bands prior to any mention of ATT devices.
I think they are all a bit different when it comes to hardware which baffles more when I read on a Google forum post about a T-Mobile device that was stock Ann's doing this.
Sent from my Nexus S using XDA Premium App
Where to dowload KB3 radio image? (And advice)
Hey jrcompton,
Wow, that's great news! I tried a bunch of things, including going back to stock 2.3.3 via ROM manager (am now on 2.3.4, as I was prompted almost immediately for an OTA upgrade), and the bug still persists. It seemed after returning to stock that the issue didn't present itself until after installing certain apps (Dialer 1, Handcent, Extended Controls) but after removing them, am still seeing the bug. Was thinking that maybe it was these apps and uninstalling still let some trace and another factory reset might be necessary, but your results give me hope! As it is, on mobile data the bug can present itself several times in a minute! (Making the phone almost unusable).
All that being said, any chance you could share where I could download the KB3 radio? I did search and was only able to find a thread with mostly Tmobile users, and was thinking that the radio in that thread might not be the right one. I'm on Bell, so sounds like the radio that you're using would be right for me (since your phone uses AT&T bands).
Also, never flashed just a radio before, and am a little nervous. I know that there are a ton of threads with instructions, but I hope it's ok if I ask a couple questions. I'm assuming that I download the image, and put it in my ANDROID-SDK-TOOLS directory, then just (in command prompt from that same directory) type "fastboot flash radio *********.img (with the phone in bootloader, and connected via usb). And that I should NOT disconnect, power down, touch, or even look at phone during process, and make sure that PC doesn't power down, reboot, etc. If all of that is correct, do I need to wipe/factory reset or anything else beforehand or afterwards?
Thanks so much in advance, and so glad that you've at least had 24 hours bug free!
If this works for me as well, will post in the Google help forum thread as well.
I just downloaded the zip from here ( http://forum.xda-developers.com/showthread.php?t=975105
[RADIOS] 01/Mar XXKB3 (GRI54): Basedband (radio) only updates) and installed via CWM... worked like a charm
Cheers
Sent from my Nexus S using Tapatalk
If this worked for you guys then that's great, but do you have any suggestions for a NS4G user? I realize we don't have our own subforum but up until that happens, we have to have our questions fielded here. I'm still getting the search button going nuts on me issue. have tried data off/only wifi and still doing it. Wondering if I just got a defective unit...
Sophos1 said:
I just downloaded the zip from here ( http://forum.xda-developers.com/showthread.php?t=975105
[RADIOS] 01/Mar XXKB3 (GRI54): Basedband (radio) only updates) and installed via CWM... worked like a charm
Cheers
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Hey Sophos1 (or anyone else who might know),
My Nexus is now running the following:
Android Version: 2.3.4
Baseband Version: NO DGSXXKD1
Kernel Version: 2.6.35.7-ge382d80 [email protected] #1
Build number: GRJ22
Model number GT 19020A (originally bought from a Telus Store) currently running on Bell Mobility
Would the KB3 radio that you downloaded for your phone work for mine? Also, just for confirmation, will I be ok following the steps that I listed above? Lastly, what's the worst that can happen if I flash the incorrect radio? Would I still have the opportunity to flash the correct radio (or reflash stock including the correct radio) via fastboot?
Thanks so much guys!
I have had my Galaxy S 4G about 1 month now and I'm a newb to Android. I've not rooted or done anything other than load more apps from the Market to try and learn more about this phone. It is out of the box stock as of 9/2011
My Wifi shows that it is on and logged on to my router at home and when I run the SpeedTest.net app it shows that ping works (though slow) and then the download runs but then times out with a network error.
All I do is toggle off the wifi and then back on again and try it again and suddenly it works fine for some extended time.
I have an I-pod touch that always works along with a laptop that has no issues with the 802.11 g connection from the same chair that I'm sitting in with the phone.
It is an annoyance to keep having to check for "quality of service" issues with an internet connection. You never know when you will have to toggle the service back on again or if you are just looking at a server issue on the other end of the connection
Is this a known problem with either Froyo, Samsung Galaxy or T-Mobile?
My config:
[t959v] = [SGH-T959V]
Firmware version
2.2.1
Kernal Version
2.6.32.9
Build #
Froyo.vuvkd1
Thanks in advance.
ggregor said:
Is this a known problem with either Froyo, Samsung Galaxy or T-Mobile?
Click to expand...
Click to collapse
Not to my knowledge. I had my SGS4G back in February before the KD1 update and never had the problem. It wouldn't be a T-Mobile issue as, whatever the problem is, is between your phone and the router. So T-Mobile is out of that equation.
Maybe try a factory data reset? Just a thought to see if it helps. I can't think of a good reason it would but it's just an idea. Given that you're not rooted nor running any custom ROMs or firmware I don't want to even think about pointing you down that road.
Have you tried it with more than the 1 router in the house? If it's a problem with wifi in general it could be defective hardware. If it's only with the 1 router then there could be other variables at play (type of router, security on it, & the SGS4G not liking that, etc.)
I'm rambling...but stumped a bit.
Called t_mobile support and once I got to the second level support person she had me stop by a store and get an updated Sim card.
My original card was 7 years old. I really didn't think that would matter, but so far it seems to have done the trick.
Sent from my SGH-T959V using XDA App
ggregor said:
Called t_mobile support and once I got to the second level support person she had me stop by a store and get an updated Sim card.
My original card was 7 years old. I really didn't think that would matter, but so far it seems to have done the trick.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Awesome. Glad you got it working.
I can't send text or phone calls after CWM recovery flash.
I initially rooted my i535 sg3 using this method http://forum.xda-developers.com/showthread.php?t=1840030
I then flashed 4.2.2 Pacman. Used this for a few days and everything was ok but battery life was horrible so I flashed, I think CleanRom, then Liquid RC1. I'm not sure where in the process of flashing but I noticed that my reception was weak compared to stock and then I couldn't send outgoing text or calls all together. I've searched everywhere and I have seen similar issues/symptoms but non of the fixes have worked for me. Here's my current setup.
Model SCH-I535
Android Version 4.1.2
Baseband I535VRBMA2
Kernal 3.0.30-861013
Build JZO54K.I535VRBMA2
Status
Netowork = Unknown
Mobile Network Type = 1xRTT.6
Service State = In Service
Roaming = Roaming
Mobile Netowrk State = Disconnected
My Phone # = 000-000-8561 (last 4 aren't even correct)
IMEI looks correct
IP Address = Unavailable
Thanks for any help/advice.
Pozman1 said:
I can't send text or phone calls after CWM recovery flash.
I initially rooted my i535 sg3 using this method http://forum.xda-developers.com/showthread.php?t=1840030
I then flashed 4.2.2 Pacman. Used this for a few days and everything was ok but battery life was horrible so I flashed, I think CleanRom, then Liquid RC1. I'm not sure where in the process of flashing but I noticed that my reception was weak compared to stock and then I couldn't send outgoing text or calls all together. I've searched everywhere and I have seen similar issues/symptoms but non of the fixes have worked for me. Here's my current setup.
Model SCH-I535
Android Version 4.1.2
Baseband I535VRBMA2
Kernal 3.0.30-861013
Build JZO54K.I535VRBMA2
Status
Netowork = Unknown
Mobile Network Type = 1xRTT.6
Service State = In Service
Roaming = Roaming
Mobile Netowrk State = Disconnected
My Phone # = 000-000-8561 (last 4 aren't even correct)
IMEI looks correct
IP Address = Unavailable
Thanks for any help/advice.
Click to expand...
Click to collapse
Have you tried odining back to stock? Somewhere along the way from AOSP back to TW you might have lost/changed some sys data.
Feels like it lost the IMEI, even if it looks correct. Getting stuck on roaming and possibly the weird phone number may mean that's what went wrong.
Sent from my SCH-I535 using xda app-developers app
sworld said:
Feels like it lost the IMEI, even if it looks correct. Getting stuck on roaming and possibly the weird phone number may mean that's what went wrong.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I was able to Odin back to a stock unrooted 4.0.4 rom but it did not fix the issue. Is there a good way to restore IMEI?
Did you try to reprovision after you used Odin to get back to stock 4.04? A lot of people have had success after doing that, including myself. Be warned, it will completely wipe your phone.
HHF2 said:
Did you try to reprovision after you used Odin to get back to stock 4.04? A lot of people have had success after doing that, including myself. Be warned, it will completely wipe your phone.
Click to expand...
Click to collapse
I'm somewhat new to this and have no clue what "Reprovision" does. I found this comment on one post "reprovision your device with dialer code *2767*3855#". When I dialed this it said that when roaming that you have to use an area code and then hangs up? I really hope I don't have to dish out $600 to Verizon! I'm at a loss right not.
You need to enable the hidden menu before you can use the reprovision code. Dial *#22745927 and enable the hidden menu. Now the reprovision code should work. You shouldn't have to hit send at the end of the code. It should work as soon as you enter the last digit. This is assuming you are still on ICS.
Pozman1 said:
I'm somewhat new to this and have no clue what "Reprovision" does. I found this comment on one post "reprovision your device with dialer code *2767*3855#". When I dialed this it said that when roaming that you have to use an area code and then hangs up? I really hope I don't have to dish out $600 to Verizon! I'm at a loss right not.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2066731
I think I found a thread that has solved this for me.
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/show....php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
OMG THANK YOU GUYS!! This thread saved my sanity! I had flashed the latest MIUI 4.1.2 and wasn't a big fan so I flashed my backup and *POOF* no data! I had no clue how it happened (still don't fully understand it), tried every basic "go-to fix" in the book, and scoured the forums for two days without luck. The suggestions in Pozman1's last thread post to flash back to the VRALG1 4.0.4 ROM and the I535VRLHE radio did the trick! The only thing I had to do differently was use the *#7780# Factory Reset Code instead of the *2767*3855# Reprovisioning Code, for whatever reason that code just wouldn't work. Anyway, thanks again!
Thanks!
I spent all last night and most of this morning trying to figure out what was wrong with my phone. I was not connecting to the network and went through the forums searching for the solution to my problem. I odin'ed, flashed, prayed, hoped and then did it all over again all the way back to 4.04. until I landed here.
I was finally ready to give up, so I went to the Verizon site to see if my IMEI was listed and if it matched my phone. Both my phone and my wife's phone were different than the phones we actually have. I got on chat with verizon support and they fixed it right up. I got my 4g back. Now, I'm updating my way back up to the present.
I've been able to solve every problem I've had by lurking/searching these forums. I've been doing this for a couple years now. I really should have registered and started thanking people a long time ago. I have bought apk's off of google play and donated some beer money, but probably not enough. After I post this, I'll take some time and spread the thanks I owe.
I've registered and planted this response here so that if someone else is having the same problem, they might think to go check their account and make sure they've actually got the same phone their carrier thinks they do. Sometimes, it helps to start with the simple stuff.
Thanks to everyone!
So just today I updated my skyrocket to cm-10.1-20130526-NIGHTLY an it didn't say anything about updating radios or anything of the sort every thing seems to be running just fine but now i show no service almost anywhere I go but most of my txt will send but every few or so will come back saying cannot send at the moment. then if I retry/ move around it will send never had this problem before with existing NIGHTLY rom's. any insight or help would be greatly appreciated. My whole family has at&t has no signal problems.
phone info:
kernel version
3.0.72-cyangenmod-g5d26b2d [email protected] #1
baseband version
i727UCL13
Android version 4.2.2
Read the thread dude. Gawd.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 4 Beta
Hi guys,
So I just installed rooted 2.3.6 on my infuse 4G and then went straight ahead to installing the slimbean 3.0.0 Infuse version...
Everything went smoothly (can't believe how strikingly different the device feels with default-looking 4.1.2 version), except for the most important part- I can't seem to be able to do anything with the APN setting on the device, so no cellular connection at all on a cellphone.
I'd go into the APN settings menu (under mobile network settings), press the menu button, choose new APN and then all the relevant info from here http://forum.xda-developers.com/showpost.php?p=29219661&postcount=1785
But when I choose save and get out of the menu there's nothing left- no default options, no APN setting I just saved. Just a black screen that says APNs
Does anyone have any idea what might have happened? How would I be able to fix this?
Thanks!
Maybe no imei number. Your supposed to flash an ICS ROM then a Jb ROM. Look under phone status see if u have an imei number. Also try another rom
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Yup. IMEI issue. I solved it (kind of) by going back to stock and then flashing again into aeon rom.
Kind of boring to be on 2.3 again, but I never realized how functional and lean all this was back then
Still on the fence about going ICS or JB though, this will be my only phone for a while...
Sent from my SAMSUNG-SGH-I997 using xda app-developers app