Database Info

Terrible Search Button Bug

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!

[Q] Time to speak up

Getting tried of watching my phone reboot. If going back to stock would resolve the issue I would do it. I called big red today and the pinhead I spoke to acted like it was the first time anyone had called about the TB rebooting on it's own. I'm looking at going to a different phone. I really think at this point it is a software issue that they need to correct. Just like with most businesses things are not addressed until they become a problem. So my thought is we should set a date when every one calls in to report their rebooting phones. We do this every week until we get a resolution. Anyone with me?

Wait... You are rooted and getting reboots? Are you on gb? Did you root or install your rom properly? What kernel?
Stock I had no issues. Non-Gb I've had mostly no issues... Some kernels less reliable than others, of course. But to be honest it sounds more like a user issue than a tb issue
Sent from my ADR6400L using XDA App
Sent from my ADR6400L using XDA App

Are you near a Verizon store? Verizon is usually very easy to convince that you need your phone replaced. (Although I think they will only replace it with the same model. But I'm not sure.) My Thunderbolt never reboots on its own but I know it is a problem that many Thunderbolts are experiencing, so maybe yours (and many others) is/are defective. I'm 99% sure if you go into a Verizon store and tell them that it randomly reboots all the time, they'll replace it for you.

I reverted back to stock and haven't had a single reboot or loss of data on three days. Just sayin'.
Sent from my ADR6400L using XDA App

I have read posts where people who are not rooted are getting reboots after they took the update. Have never had an issue with my phone until I took the update. Am going back to stock for a week or so to see if that clears things up.

Funny how VZW is changing their stance on it, almost as if it never has happened. About a month ago I went into a store and they told me that Im not the only one experiencing problems and that there will be a fix within 2 months.
I called VZW tech support and they told me that no one else is having reboots.. . . . I dont get it.

Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)

Can you specify what you mean when you say "both"? I have been getting reboots too - approximately 1 per day - but is there a process to flash each radio independently?
Sent from my ADR6400L using XDA App

sethschmautz said:
Can you specify what you mean when you say "both"? I have been getting reboots too - approximately 1 per day - but is there a process to flash each radio independently?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
No, but each flash has two radios
Sent from my ThunderBolt using XDA Premium App

Silvus said:
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Click to expand...
Click to collapse
Any issues with tethering or gps using the old radios?
Sent from my ADR6400L using XDA App

Silvus said:
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Click to expand...
Click to collapse
I still had reboots with both at .6, currently trying cdma.7/LTE.6.
Sent from my ADR6400L using Tapatalk

It is a hardware issue,that's where the few pricked phone came from,my original bolt had the reboot loop on stock but no one seems to want to hear that,it is a series of phones having the trouble and they are or have replaced most of them,as far as most of the other reboot go that is self made misery by not following directions or not reading to find the fix, this bolt I have now has no reboot issues and it has a mat finish to it,the other one and a few I have seen that had issues had a smooth glossy finish.
Sent from my ADR6400L using XDA Premium App

satseaker said:
It is a hardware issue,that's where the few pricked phone came from,my original bolt had the reboot loop on stock but no one seems to want to hear that,it is a series of phones having the trouble and they are or have replaced most of them,as far as most of the other reboot go that is self made misery by not following directions or not reading to find the fix, this bolt I have now has no reboot issues and it has a mat finish to it,the other one and a few I have seen that had issues had a smooth glossy finish.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I would love to think its a hardware issue, but my phone was solid from day one. Then I took the update and get these random reboot.
Sent from my ADR6400L using XDA App

It is not a hardware issue. It is a problem with the update and how certain phones installed it. Verizon is in the process of making a new update and has been working on it with HTC for a little while now & expect to have it going out this month. For some reason the software does not talk to the towers properly with some models & the hardware does not get the proper info which causes the reboots. Exactly how to tell which phones are affected, I don't know. My friend is trying to find out for me.
I can say that I ran my phone with rooted stock & moved up to the rooted update when it was available which I am still on and I have not had any issues at all besides the low recorded video audio which the update seems to have fixed for me.
My phone is:
Rooted stock & radios w/update
Adrynelynes 4.47 Kernal

I am telling you what HTC said they admit that a certain series is defective hence the snappy replacement. Just cause one Rom works and another doesn't isn't always the Roms fault,ever had a CPU that would run one OS and not another or RAM that worked fine on xp but not win 7 once the defective hard hits its limit it will fail. I have seen hardware work fine overclocked and the exact same hardware crash with half the settings,or a motherboard run suse fine but put Windows on it and it dies a week later. I didn't say they all were defective just one series of them and when they did the update a lot of the phones started to fail and some didn't,so does that tell you hardware or software,if one can run fine and the other fails its either a bad flash or bad hardware. Take your pick
Sent from my ADR6400L using XDA Premium App

I didn't do the update over the air on my other bolt, I downloaded it from HTC and it killed the phone,but the same download is on this phone and it works just fine,not one reboot, and its still stock and not rooted. The other one was dated Dec
10 and this one is dated Feb 11, I would just about guess they tweaked the update to weed out the bad phones faster,makes sense to me.
Sent from my ADR6400L using XDA Premium App

satseaker said:
I am telling you what HTC said they admit that a certain series is defective hence the snappy replacement. Just cause one Rom works and another doesn't isn't always the Roms fault,ever had a CPU that would run one OS and not another or RAM that worked fine on xp but not win 7 once the defective hard hits its limit it will fail. I have seen hardware work fine overclocked and the exact same hardware crash with half the settings,or a motherboard run suse fine but put Windows on it and it dies a week later. I didn't say they all were defective just one series of them and when they did the update a lot of the phones started to fail and some didn't,so does that tell you hardware or software,if one can run fine and the other fails its either a bad flash or bad hardware. Take your pick
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I wasn't aware of HTC stating there was some defective hardware. Never saw any references to it. If thats the case then glad they acknowledged it.

It's definitely not a hardware issue. Its a radio/ signal issue. Verizon does know about it, and is working on getting a new update out there. I know this, for a fact.
Sent from my ADR6400L using XDA App

jett2314 said:
I have read posts where people who are not rooted are getting reboots after they took the update. Have never had an issue with my phone until I took the update. Am going back to stock for a week or so to see if that clears things up.
Click to expand...
Click to collapse
My TBolt is not rooted and before the update I had no problems at all but after the update the random reboots started. Battery life is acceptable but could be allot better.
Called Verizon yesterday and they acknowledge the problem and actually said HTC is aware of the problem and are working on it but have no expected date as to when it will be fixed. I believe it is definitely is a software issue and will be fixed when the official Gingerbread is released. Just my 2 cents.

No signal or data

I'm not skyraider Zeus preview and have no no issues till last night. Now all of a sudden since last night I have not been able to get 1x, 3g anything and signal drops. Have multiple lines on verizon and the rest of the phones are fine. Really don't want to change roms but will if I have to.

Have you tried to just reload the rom on top of what you have now?
Have you tried to restore a backup?
Sent from my ADR6400L using XDA Premium App

ibsk8 said:
Have you tried to just reload the rom on top of what you have now?
Have you tried to restore a backup?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Okay I just restored a backup of liquid gingersense and same problem... Starting to get a bit scared.

Alright flashed the brand new GB radio from "someplace." Still have same problem. Sometimes I have full bars but no 3g and can't get calls tried to test and calls don't go through so my phone is kinda pointless... I'm really panicking I need this thing...

When you installed the new radio did you also install the LTE radio?

Stumpsalot said:
When you installed the new radio did you also install the LTE radio?
Click to expand...
Click to collapse
Honestly no clue how would I be able to tell? I've installed nearly every radio and never has two separate radio files.

cstrife999 said:
Honestly no clue how would I be able to tell? I've installed nearly every radio and never has two separate radio files.
Click to expand...
Click to collapse
There are not two separate radios to install. If you downloaded MR3, it will work if you're on a GB Rom. If you're on a froyo Rom then you need a froyo radio.
Also check to make sure your battery door is completely attached. Your antennas are in the door and it must be attached.
Sent from Synergized Thunderbolt via the XDA Premium App

cstrife999 said:
I'm not skyraider Zeus preview and have no no issues till last night. Now all of a sudden since last night I have not been able to get 1x, 3g anything and signal drops. Have multiple lines on verizon and the rest of the phones are fine. Really don't want to change roms but will if I have to.
Click to expand...
Click to collapse
Were you running a leaked radio when you had this problem first off?

mAlfunkti0n said:
Were you running a leaked radio when you had this problem first off?
Click to expand...
Click to collapse
I was running the OTA MR2 radio since release never had any problems then last night out of nowhere it just happened. Have been scrambling ever since.

CanesDrew said:
There are not two separate radios to install. If you downloaded MR3, it will work if you're on a GB Rom. If you're on a froyo Rom then you need a froyo radio.
Also check to make sure your battery door is completely attached. Your antennas are in the door and it must be attached.
Sent from Synergized Thunderbolt via the XDA Premium App
Click to expand...
Click to collapse
Went back to MR2 radio now since I know it's not a radio issue. Battery door is completely sealed. Checked to see if the metal was bent in any way and it's not.
EDIT: Every time I reboot it gains bars back for a bit but no 3g. I've tried calling during this period to no avail. Then it looses bars with just an x over them. The one thing I am thinking is there any possibility that the sim just died...

Did you check your mobile network settings? Are you on LTE only mode possibly?

As goofy as it sounds, when I first rooted my TB awhile back I completely lost signal then was able to pick up 1x and that was it. I did a factory reset on the device (as instructed by VZW), and it actually worked. Nothing else had been done to the device besides a root, no one else could figure out what exactly went wrong, but the wipe restored it back to "factory" root and it worked perfectly.

g00s3y said:
Did you check your mobile network settings? Are you on LTE only mode possibly?
Click to expand...
Click to collapse
No LTE/CDMA. I have done like 30 factory resets lol. Called Verizon to make sure there was no outage. I'm getting a new device (Not refurbished shockingly) over-nighted. The big bummer is having to reroot and such, but hey the guy was nice about it and everthing so no complaints. I can live without it for one day. Thanks for all your help guys!

[Q] Nexus S changes to speaker phone on recieving call

So I just got a Nexus S 4g on Monday and my dad and I already rooted the phone and have been trying different roms. He actually rooted it and swapped out the stock rom before I even knew I was getting it.
So with both of the roms I have tried, whenever i recieve an incoming call the speakerphone automatically activates and I have to manually turn it off.
We already tried reflashing the rom and we have also tried replacing a lib***.so file (forget which one) and neither fixed the problem. I cant find any sort of setting for this.
Anyone else having this problem? Is there a fix available that someone can guide me? Very new to Android so I'm still learning the tricks of flashing etc.

Just curious...did you test the phone before it was rooted.
Sent from my PC36100 using XDA Premium App

I received the phone on monday evening and my dad had the phone all day and routed it etc.
I never handled the phone with the stock rom. Its not too big a deal since I don't use it for much calling but a fix would be greatly appreciated.
Sent from my Nexus S 4G using XDA App

webhead1994 said:
I received the phone on monday evening and my dad had the phone all day and routed it etc.
I never handled the phone with the stock rom. Its not too big a deal since I don't use it for much calling but a fix would be greatly appreciated.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Well it seems like you don't know if this problem has always existed or if it is a result of flashing a custom rom. Best bet would be go back to completely stock and see if you still have the problem.
Sent from my PC36100 using XDA Premium App

Just flashed the new miui rom and it fixed the problem. Now I just have to redo my launcher lol.
Sent from my Nexus S 4G using XDA App

I'm having the same problem running a stock version of Android.

I started to have the same problem few days ago and my phone is all original stock, ,,

my wife just started experiencing this today. completely stock nexus s. we may try uninstalling the last few apps that had updates and see if we can trace it to one of those.
edit: are any of u using go sms (specifically version 3.66)? other users are complaining that recent update is causing this issue. im sending my wife a backed up version i have of 3.65 to see if its resolved
edit 2: rolling back to 3.65 did not resolve the issue, but rolling back to 3.64 did. good thing i have appmonster pro.....

I just started to have this problem today too. I did try to activate GoogleVoice yesterday but the calling issue did not begin until today. Running MATR1X v.6 and CM7 nightly #83. Didn't have this problem during stock.

Go sms's latest update is the culprit. The August 29 th update is responsible. Just uninstall that and put some other sms app.
Should solve it, It fixed my phone.

it happened to me twice yesterday, I answer the phone the screen went black and the sound routed to the speaker..can't go back to turn it off during the call as the screen has nothing. (stock rooted)...will uninstall GoSMSPro and see how it goes

If anyone needs/wants the 3.64 version of GO SMS, dm me you're email addy. (i'm assuming this would be ok on XDA since the app is FREE in the market?)

They (GoSMS) just released an update 3.66 to fix the problem

vennstrom said:
They (GoSMS) just released an update 3.66 to fix the problem
Click to expand...
Click to collapse
Its still exists on 3.66. My wife was using this version and it had the problem. We had to roll back to 3.64 before it went away.

u were right, Go SMS was the issue, they released an update today and solved the problem!
cheers everyone!

Glad I saw this thread... my G2 started doing this after not changing the ROM in months, at least now I know what caused it. I got my Nexus S yesterday and haven't answered any calls without the headset yet, lol, so I thought it was just my G2.

[Q] Should I be messing with my radio?

Originally used the Ace Hack Kit about 2 months ago. I think it was version 11 or somewhere close.
Rooted just fine and have played with a few different ROMs now. Found one I like until a fully working sense 3.5 comes out.
I have been reading more and more but still unsure about the Radio.
Since the root I have only flashed ROM's not a radio.
I am currently @ 12.28b.60.14eU_26.03.02.26_M
I don't seem to be having any cell issues, but read that you should use the Radio that is linked with the ROM your using.
Can someone shed a little more light on this for me?
If im not having cell issues should I mess with it?
Or maybe because I have not ever flashed a new one, I may not know what im missing.

Zen-Dragon said:
Originally used the Ace Hack Kit about 2 months ago. I think it was version 11 or somewhere close.
Rooted just fine and have played with a few different ROMs now. Found one I like until a fully working sense 3.5 comes out.
I have been reading more and more but still unsure about the Radio.
Since the root I have only flashed ROM's not a radio.
I am currently @ 12.28b.60.14eU_26.03.02.26_M
I don't seem to be having any cell issues, but read that you should use the Radio that is linked with the ROM your using.
Can someone shed a little more light on this for me?
If im not having cell issues should I mess with it?
Or maybe because I have not ever flashed a new one, I may not know what im missing.
Click to expand...
Click to collapse
You will get different opions here...but my thinking is your probably scared since you have never done it. And you should be lol. Flashing a radio is pretty common but still dangerous, but so is rooting, flashing roms, and other things if you haven't read and researched completely. Been there dude. I believe that if the radio you currently have works why change? If your lucky enough to have good coverage, GPS, etc then don't change.
Sent from my Inspire 4G using xda premium

I have to agree, general belief seems to be, 'if it aint broke, don't fix it'
Sent from my Inspire4G using xda premium

I was wondering the same thing. I'm new to the rooting and not quite ready to flash radios but have been reading into it. I'm using radio 12.28b.60.140eP 26.03.02.26M. But whenever I'm talking on the phone, everyone on the other end of the line says it echoes. Would that be a sign indicating I should go with the recommended radio for my ROM?
Sent from my Inspire4G using XDA App

Jaquez09 said:
I was wondering the same thing. I'm new to the rooting and not quite ready to flash radios but have been reading into it. I'm using radio 12.28b.60.140eP 26.03.02.26M. But whenever I'm talking on the phone, everyone on the other end of the line says it echoes. Would that be a sign indicating I should go with the recommended radio for my ROM?
Sent from my Inspire4G using XDA App
Click to expand...
Click to collapse
most echos are from using the speaker phone
Sent from my Inspire4G using xda premium

That's what I originally thought too. But i tried it with and without the speaker and the echoes were still heard. I admit I do have the volume set to max cuz I have trouble hearing over the phone, so with the audio enhancements from my rom would it be possible that I'm gonna just have to deal with it?
Sent from my Inspire4G using XDA App

i have tried a few different radions.....and to be completely honest, i havent noticed the slightest bit of difference......well, MAYBE slower data speeds on one of them (a little bit), but i couldnt be sure the radio was to blame. im on the most recent OTA update radio. it works, im not bothering to change again.

oFUNGUSo said:
i have tried a few different radions.....and to be completely honest, i havent noticed the slightest bit of difference......well, MAYBE slower data speeds on one of them (a little bit), but i couldnt be sure the radio was to blame. im on the most recent OTA update radio. it works, im not bothering to change again.
Click to expand...
Click to collapse
+1
I've never noticed a difference in any of them. Just use the latest AT&T radio firmware and you'll be fine.

How do you know what the latest one is and where do you get the latest OTA radio?
I checked my wife's inspire which I have not rooted yet (she is happy on stock) and her Baseband is different than what I have. Hers is 12.56.60.25U_26.10.04.03_M
Would that be the latest?
Sent from my Inspire 4G using XDA App

Zen-Dragon said:
How do you know what the latest one is and where do you get the latest OTA radio?
I checked my wife's inspire which I have not rooted yet (she is happy on stock) and her Baseband is different than what I have. Hers is 12.56.60.25U_26.10.04.03_M
Would that be the latest?
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
That's the latest for g bread.
Sent from my Inspire 4G using Tapatalk