Related
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!
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.
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
Hi,
My Nexus S is having a strange issue that when turn the phone on it picks up that I'm on Orange UK but from then on it says emergecy calls only or no service but shows signal in the status bar. If I try and call someone I get no mobile network messages but I can get a data connection and use the Internet although very slowy. Strangest thing is that if I put no sim card in the status bar still shows signal.
I've tried different radios and tried both Offical stock 2.3.4 and CM7 7.1.0 but same results, I've also tried turning 3g off but I'm now out of ideas so can anyone give me some tips please?
Thanks
Can you give specifics? Phone model, Baseband version (found in Settings >> About phone). Not all radios are the same and you can end up bricking the phone flashing wrong radio version.
Sent from my Nexus S using xda premium
[email protected] said:
Can you give specifics? Phone model, Baseband version (found in Settings >> About phone). Not all radios are the same and you can end up bricking the phone flashing wrong radio version.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
You cant brick your phone flashing the wrong radio....youll just have to have the correct radio as a back up. I flashed every radio for the nexus s and its not bricked.
Anyway, the standard radio the i9020a comes with is the UCKF1 or KB3 as I have heard. http://forum.xda-developers.com/showthread.php?t=1116884 is where you will find the radios. Just flash the correct one. How you will know whats the correct one is it will be stated after the phone model. for example I9020AUCKF1 the A after I9020 is for the carrier ATT and after the thats the radio it came with. just reflash the correct radio through CWM and you should be ok. If not PM and I will help you further
heinst said:
You cant brick your phone flashing the wrong radio....youll just have to have the correct radio as a back up. I flashed every radio for the nexus s and its not bricked.
Click to expand...
Click to collapse
Flashing I9023 radio on I9020 will brick the phone as it may not even boot into recovery, fastboot may not work too. Just a word of caution.
Sent from my Nexus S using xda premium
Sorry I should have said I have i9023 and have tried kf1 kd1 and jk8 radios all with the same results so far.
Sent from my GT-I9100 using XDA App
immolo said:
Sorry I should have said I have i9023 and have tried kf1 kd1 and jk8 radios all with the same results so far.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
What the next step would be is to try a new sim card. Go to your carrier and ask for a new one. If same results then its the phone and I'll assist you more.
Don't forget the thanks button.
Sent from my Nexus S using xda premium
Managed to borrow someones sim card at work today and it was the same result so it does seem to be a hardware problem now.
Sent from my GT-I9100 using XDA App
Yes. That would seem to me like the problem. I'm sure you restored your phone and completely wiped the SD? Also did you try pulling out the battery while the phone was on wait 30 seconds try turning the phone with out the battery then put the battery back in and turn it on? I'm sure you have done that you seem like a decently tech savvy fellow.
I've called Samsung before and I hate to say it but their repair policy is horrendous. You'll need another phone cause you'll be without yours for 2-4 weeks. They want to send "you your original phone back." Even their battery exchange is the same. You send your bad battery to them. They receive it process it then send you a new one. Motorola and apple have their repair department to be easy and quick which is what the consumer wants. More so apple cause you can go right to the local store and get a new one in 10 minutes. Motorola takes 2 days. Better than Samsung still.
Thats it for my rant! Just wanted to give you a heads up of what you will hear. Hope it all works out.
Sent from my Nexus S using xda premium
heinst said:
You cant brick your phone flashing the wrong radio....youll just have to have the correct radio as a back up. I flashed every radio for the nexus s and its not bricked.
Click to expand...
Click to collapse
yea, try flashing a CDMA radio on a GSM phone and see how that works out for you!
edit: actually, this sounds exactly like the ns4g i bought the other day. try making an emergency call and see what happens. really, that's how i fixed mine.
thedudejdog said:
yea, try flashing a CDMA radio on a GSM phone and see how that works out for you!
edit: actually, this sounds exactly like the ns4g i bought the other day. try making an emergency call and see what happens. really, that's how i fixed mine.
Click to expand...
Click to collapse
Well I dont think some one is that dumb to flash a CDMA for a GSM......if you are, you should stick to the iphone
Well it looks like I'm taking a trip to a service centre today let's hope it doesn't cost me too much to repair.
Sent from my GT-I9100 using XDA App
I've the same problem.
from morning my phone doesn't want find my sim card. Yesterday it was working fine.
I've try to reflash my radio but nothing.. now i'll try with odine, restoring... something older
d128b said:
I've the same problem.
from morning my phone doesn't want find my sim card. Yesterday it was working fine.
I've try to reflash my radio but nothing.. now i'll try with odine, restoring... something older
Click to expand...
Click to collapse
I tried that last flashing the xxka3 rom with no luck but let me know if you get any better luck then me.
Sent from my GT-I9100 using XDA App
Did you have any luck with Odin? I'm currently waiting for Samsung to diagnosis my problem so it would be nice to know at least one of us fixed this with software.
Sent from my GT-I9100 using XDA App
immolo said:
Hi,
My Nexus S is having a strange issue that when turn the phone on it picks up that I'm on Orange UK but from then on it says emergecy calls only or no service but shows signal in the status bar. If I try and call someone I get no mobile network messages but I can get a data connection and use the Internet although very slowy. Strangest thing is that if I put no sim card in the status bar still shows signal.
I've tried different radios and tried both Offical stock 2.3.4 and CM7 7.1.0 but same results, I've also tried turning 3g off but I'm now out of ideas so can anyone give me some tips please?
Thanks
Click to expand...
Click to collapse
I've had a similar issue in the past. Restoring my EFS made it work again.
But before that issue, I also had another problem where no amount of radio flashing and EFS fiddling would fix it. Sent it to Samsung and it came back with a form with a hand written note saying "BGA failure".
So I imagine this problem is more common than it might seem. *shrugs*
Restoring the EFS would have been one of my first moves but I was given the phone in this state with no backups made.
Just crossing my fingers that Samsung doesn't charge me a king's ransom to repair it.
Sent from my GT-I9100 using XDA App
I flashed back to the lg provided Gingerbread this week and then upgraded to 2.3.4 using their tool. Could not get over the bloatware so ended up upgrading to ICS. I now have Eagles Blood up and running, everything is great, but I can only make Wifi calls. Every time I make or receive a call over Cell towers it's a loud clicking noise that both parties can hear.
I've tried multiple ROM's and re-installs(Hellfire/Eagleblood) with CM and AOSP versions and nothing resolves this, so I finally called Tmobile thinking maybe a cell tower reset would work.
I made it to level 2 tech support and this is a "known issue" with "incomplete" 2.3.4 patches. They basically read me a service bulletin explaining my exact issue, but the warranty is broken and they simply direct me back to the LG upgrade tool.
Has anyone else been able to recover cell tower calls on any ROM or did my G2x just become a tablet when not using GrooveIP?
TIA
As far as I know from lurking on the G2x forums, only stock Gingerbread and a rooted version of stock Gingerbread are available. I don't think any third-party ROMS have call audio working. The reason is that the official update changed the baseband.
Jlloyd97 said:
I flashed back to the lg provided Gingerbread this week and then upgraded to 2.3.4 using their tool. Could not get over the bloatware so ended up upgrading to ICS. I now have Eagles Blood up and running, everything is great, but I can only make Wifi calls. Every time I make or receive a call over Cell towers it's a loud clicking noise that both parties can hear.
I've tried multiple ROM's and re-installs(Hellfire/Eagleblood) with CM and AOSP versions and nothing resolves this, so I finally called Tmobile thinking maybe a cell tower reset would work.
I made it to level 2 tech support and this is a "known issue" with "incomplete" 2.3.4 patches. They basically read me a service bulletin explaining my exact issue, but the warranty is broken and they simply direct me back to the LG upgrade tool.
Has anyone else been able to recover cell tower calls on any ROM or did my G2x just become a tablet when not using GrooveIP?
TIA
Click to expand...
Click to collapse
By updating the ROM with LG's update tool to 2.3.4, u also updated the baseband, and if u read around the forums here for the G2x, you can easily find that none of the custom ROMs work with the new baseband because of compatibility issues, you can only use ROMs that are based off of the official 2.3.4 update but there arent any yet.
Although im quite surprised tech support said it was a known issue, i wonder how many other people have called having this problem because they dont read around.
Anyways, hope this helps clear things up
Sent from my LG-P999 using XDA
thanks for the quick responses. I read the ROM install instructions multiple times, but did not read about the underlying baseband since I was running Weapon G2x gingerbread with no problems and thought the 3 wipes recommended prior to the install would take me back down to a clean phone.
Appears I have a tablet till the updates are released.
Also, Tmobile tier 2 support had a KB item on this issue, but it was caused by earlier versions of the software update failing prior to completion and causing the SIM card/network errors.
Jlloyd97 said:
I flashed back to the lg provided Gingerbread this week and then upgraded to 2.3.4 using their tool. Could not get over the bloatware so ended up upgrading to ICS. I now have Eagles Blood up and running, everything is great, but I can only make Wifi calls. Every time I make or receive a call over Cell towers it's a loud clicking noise that both parties can hear.
I've tried multiple ROM's and re-installs(Hellfire/Eagleblood) with CM and AOSP versions and nothing resolves this, so I finally called Tmobile thinking maybe a cell tower reset would work.
I made it to level 2 tech support and this is a "known issue" with "incomplete" 2.3.4 patches. They basically read me a service bulletin explaining my exact issue, but the warranty is broken and they simply direct me back to the LG upgrade tool.
Has anyone else been able to recover cell tower calls on any ROM or did my G2x just become a tablet when not using GrooveIP?
TIA
Click to expand...
Click to collapse
All EB ROM's based on ICS are not compatible with the latest March bandbase.
You can downgrade to v21e July 2011 baseband if you want to use other ROMs.
Sent from my LG-P999 using xda premium
kesara said:
You can downgrade to v21e July 2011 baseband if you want to use other ROMs.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I don't want to seem lazy, but man, I've been looking all around for the "downgrade" baseband thread, where is it?
[email protected]
mustangtim49 said:
I don't want to seem lazy, but man, I've been looking all around for the "downgrade" baseband thread, where is it?
[email protected]
Click to expand...
Click to collapse
There isn't one. You use the same kdz method that ppl are using to update to v21y. just switch the 21y.kdz with 21e.kdz when using the method.
cricketAC said:
There isn't one. You use the same kdz method that ppl are using to update to v21y. just switch the 21y.kdz with 21e.kdz when using the method.
Click to expand...
Click to collapse
Yes
Sent from my LG-P999 using xda premium
Jlloyd97 said:
thanks for the quick responses. I read the ROM install instructions multiple times, but did not read about the underlying baseband since I was running Weapon G2x gingerbread with no problems and thought the 3 wipes recommended prior to the install would take me back down to a clean phone.
Appears I have a tablet till the updates are released.
Also, Tmobile tier 2 support had a KB item on this issue, but it was caused by earlier versions of the software update failing prior to completion and causing the SIM card/network errors.
Click to expand...
Click to collapse
Just look for the rooted version of the new update in the dev section by Kwes. Your phone will be fine then.
Sent from my LG-P999 using xda premium
Yup having the same issue with my friends phone. Someone mentioned downgrading the baseband, the only way I know how to do that is by using the tool that helps you unbrick the phone. please correct me if im wrong or have any idea what ive just said
What exactly is the benefit of the new march 2012 baseband (other than breaking custom ROM compatibility at this point)? Looking for apples-to-apples comparisons of a custom ROM running with old baseband and new baseband (other than broken cell voice calls).
A similar ordeal happened for Virgin Mobile's Optimus V line, where a new baseband came out, everyone jumped on it, but it caused occasional random reboots and no apparent benefits, and couldn't be downgraded. Eventually devs had to apply fresh LG released kernel source code & recompile kernel for new baseband to be stable.
Whyzor said:
What exactly is the benefit of the new march 2012 baseband (other than breaking custom ROM compatibility at this point)? Looking for apples-to-apples comparisons of a custom ROM running with old baseband and new baseband (other than broken cell voice calls).
A similar ordeal happened for Virgin Mobile's Optimus V line, where a new baseband came out, everyone jumped on it, but it caused occasional random reboots and no apparent benefits, and couldn't be downgraded. Eventually devs had to apply fresh LG released kernel source code & recompile kernel for new baseband to be stable.
Click to expand...
Click to collapse
As much as I miss ics, the new baseband pretty much fixes everything. Battery lasts forever, GPS lock right now and I've seen accuracy to 3ft. No random rebooting. Fast, smooth, dripping butter everywhere. Other than that, no real reason to flash it.
[email protected]