So when do u think Google Will Fix the Nexus S i9020A - Nexus S Q&A, Help & Troubleshooting

Some ppl here don't Even know how To root. I myself know but those who updated OTA and aren't Techies are stuck... think Google should Seriously give us an ETA ... =\
Sent from my Nexus One using xda premium

The major problem of the i9020A is the capacitative search button firing on its own. They tried to fix it, but:
with GRK39C
wireless tether broke
search button bug still present
with GRK39F
wireless tether broke still (for me and others on AT&T). There are people on Bell/Rogers reporting it works again.
search button bug still present
The search button bug is present in low 3G areas and I can repeat the bug at will at a couple locations.
I'm fully aware of how to root/unlock flash ROMs, etc but I made a decision that this particular device would stay completely stock so I could have a frame of reference for my other phones.
Google didn't sell many Nexus phones and they are currently doing what they have done on several other projects in leave stuff broke while they attend to the next greatest thing (ICS & Honeycomb/tablets). As for a guess about when they fix this, perhaps Q1 2012 when the NS gets OTA Ice Cream Sandwich.

Telus 9020A user with rooted stock ota'ed to K39F and my tethering both USB and hotspot are fine. Never saw the search button bug myself.
Sent from my Nexus S using xda premium

slimdizzy said:
Telus 9020A user with rooted stock ota'ed to K39F and my tethering both USB and hotspot are fine. Never saw the search button bug myself.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
same here.

On Rogers had mine since it became available in April. Also never had the search problem and 39f working fine.

Related

So after living with official Froyo for a month...

How has your experience been with it?
Mine has been fine, my wife's not so much...
My wife's Captivate: WAS very very laggy but 2.2 fixed it. She had zero problems with her GPS but the 2.2 update threw it off about a block : /
My Captivate: Just as smooth as before, and GPS is perfect as was before.
How are you guys enjoying Froyo?
Not quite sure what you mean. I didn't know there was an official one for the captivate sent out? Searched for it and couldn't find it on google. You sure ATT pushed out official 2.2 a month ago?
There is no official froyo yet for the captivate
Sent from my SuperDuper!Captivate | PHOENIX RISING 4.1 | Firebird 2 v0.4 | Member of Team Phoenix
There is through Rogers.
gunstar3035 said:
There is through Rogers.
Click to expand...
Click to collapse
Correct... Rogers has released their update.
Us down here in the U.S. are still speculating when/if ATT will ever update our devices
Sent from my SAMSUNG-SGH-I897 using XDA App
I have lots of shutdown issues right now, gonna flash to a custom rom to see if it makes a diff.
Eschatologist said:
I have lots of shutdown issues right now, gonna flash to a custom rom to see if it makes a diff.
Click to expand...
Click to collapse
Flashing a new rom will not fix the problem...your only option is to contact att and get a replacement phone
Sent from my SAMSUNG-SGH-I897 using XDA App
Smallsmx3 said:
Flashing a new rom will not fix the problem...your only option is to contact att and get a replacement phone
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
+1 I had to do this and I'm glad I did, 30 days with zero random shutdowns.
Sent from my SAMSUNG-SGH-I897
DeMarzo said:
Correct... Rogers has released their update.
Us down here in the U.S. are still speculating when/if ATT will ever update our devices
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Sorry I should have specified Canada : /
It is complete bull$hit that ATT has not given you guys 2.2 I think I would go custom ROM and be done with it.
Just get a new (not refurbished) Captivate instead!
Eschatologist said:
I have lots of shutdown issues right now, gonna flash to a custom rom to see if it makes a diff.
Click to expand...
Click to collapse
Get another phone. Do not settle on a defective phone. I spoke with someone in the "Office of the President" (a higher level of AT&T customer service) and after checking into the issue, they overnighted me a NEW Captivate (my phone was purchased in August, so I am well out of the 30-days). Their statement was that the defective phones are not supposed to be in the new lots or refurb lots, as it is against their procedures to knowingly sell defective phones. I would suggest taking your complaints there. The number is 1-800-331-0500. Be firm and upset, but be respectful. They will work with you.
Overall its not bad, but I do have a few issues I am still contending with.
When I first did the update I lost navigation all together. I restarted the phone (using a access number Samsung provided me) and solved that issue.
I lost a lot of files that were on my SD card. I haven't been able to figure out why that should be. It's like the update made a point of deleting everything except my media... Oh well
However I am still fighting issues with the both the home and car docks. (Which by the way Samsung Canada doesn't recognize up here and said I am on my own)
The usb audio out worked once and then disappeared on me altogether... Restarting apps and phone isn't helping...
And using the home dock, the phones main screens get stuck in landscape mode (only after doing it all night, if it's only running for a couple hours it's fine) and I have to shut off the phone to get it back to normal. Using Samsung home dock app it was every night. Alarms Plus as well. I am currently using an app called no dock and its down to 25% of the time I don't get stuck in landscape mode. Livable... The car dock I have not gotten stuck in landscape yet, but then I don't think it will ever be in the dock long enough to get stuck...
Which brings me to a point of frustration. Why isn't landscape mode functional outside the dock mode? I love the ability, just not getting stuck there until I reboot... The phone CAN and WILL do it on certain conditions, so why not all the time?
I haven't tried the mass storage mode or tethering yet so I don't know if they are working or I have more issues to deal with.

[Q] Google connection sync/talk on NS never stays on consistently, lately.

Device: NEXUS S
Carrier: TMOBILE
Country / Language: USA
OS / Browser / build number (if applicable): 2.3.4
As of about two weeks now, my Google services connection sync and even Gtalk never stay on consistently. Data icon goes from green to gray, after wakeup. hen when it is green, I only then start to receive me push notifications. I never had this problem before and was very happy with the Nexus S. Now, however, I'm not so sure about that anymore, and it's a consensus out there that there is no solution, and that Google is "looking" into the problem. I don't think it's necessarily a hardware issue as everything was fine out of the box when I first got my phone, so its likely a Google server problem? Though it sounds like the problems are isolated to Nexus devices and myTouch 4G phones.
I would call Samsung to try to get a replacement device, but from what I hear, it doesn't solve the problem either, and Samsung's CS really sucks too.
Any advice would be greatly appreciated.
I am going through the same trouble, too. I think its more of Google server related. One thing tthat I am sure is, it started very recently. About 3 weeks ago.
Sent from my Nexus S using XDA Premium App
I have the same issue. It started a few weeks back. Got the 2.3.4 ota...same issue. Came from 2.3.2.
It's been happening to me for a while as well. Even back in 2.3.3 when I was on CM7 and OEM. I seriously think it's a problem on Google's side and they really need to address it because it keeps logging me off of Gtalk which is annoying.
Funny thing is. I notice that it happens alot less when I'm using 2g only....
Wonder if there is something to that..
Sent from my Nexus S using XDA App
I am also on two google threads about this, and there is still no agreement on a solution..
http://www.google.com/support/forum...e2&hl=en&fid=7c7a962fd3ae87e20004a26b2f3f005b
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=56f54d35a6a0da29&hl=en&start=80
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=5113952419b47e54&hl=en
I am having the same problem since around mid April. This is so frustrating, please guys flood the google help forums, this the only way google will see the seriousness of the problem.
Sent from my Nexus S using XDA Premium App
Flood indeed. Google is clueless on a solution to this problem, especially if they don't even acknowledge it..
Sent from my Nexus S using XDA App
clin0420 said:
Funny thing is. I notice that it happens alot less when I'm using 2g only....
Wonder if there is something to that..
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yeah I stay green if I'm on 3g, so maybe it's a wifi issue. I would've sworn it was a 2.3.4 issue though.
highly doubtful that this is a wifi issue, with the number of people of various threads stating that they dont even use wifi....worse yet it occurs regardless of wifi or 3g/2g
i posted a video on youtube showing the problem
http://youtu.be/axpyhgdvuMs
i have the same issue, both of my nexus 1 and tmo G2

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!

Official Gingerbread Update Soon???

So I've been looking for a way to try that GB sweetness on my Tbolt. The leak a few weeks ago was very tempting, but due to bricking issue and the fact that the leak is just a test build made me hesitant.
After googling GB update for TB, a few links came up that suggest that the TB and Evo should get official update to 2.3 in June.
Here is my question: I just saw an announcement for Evo update to 2.3 on June 6. When is it our turn??? I know it's a bit antsy but they can't just throw a wet cat in front of me and not expect me to beat that sh#$ up.
But seriously, anyone got news?
here's a poll for ya speculations
Even if sombody has a date its always wrong. So let's get over the guessing game. The bamf gb rom is flawless you just need a little experience when it comes to wiping data and radio updates. But I have had no problems once the ROM is up and running.
And battery life is better in this ROM then froyo from my personal experiences.
Going to have to add another vote for BAMF GB. Loving me some "ROM of Death" ;}
The latest CM7 Alpha build from Slayher is almost problem free for me (no big issues, all data etc. working great) and I've had lots of problems with previous builds. It's worth a shot.
I'm guessing there will be some more leaked builds, but the final version and OTA won't happen until September... 4 to 5 months after the first leak seems to be the standard procedure with VZW and Android updates...
I got an email from HTC yesterday and was told that Gingerbread will be out this summer.
I Emailed HTC to complain about the constant rebooting issue and battery life after the OTA.....bla bla ect ect & asked when the Tbolt will get Gingerbread and this is what I received back.
Dear XXXXX XXXXX,
I understand your device is randomly rebooting after the latest OTA. I will advise how to back up your contacts and perform a factory data reset. If the device continues to reboot we are currently advising customers to swap the device out with Verizon, but I will provide another option as well.
I do not currently have any information that indicates the cause of the rebooting issue or whether it is possible for it to be resolved in a software update. I can advise you that the Thunderbolt will be receiving Gingerbread this Summer.
To back up your contacts launch the People application and press menu=>import/export=>export to SD card=>Phone. If you are not sure that your contacts are in Google you can repeat this step and select the Google category.
The Thunderbolt is usually configured to mass-reinstall your Market applications after a factory data reset if you log in with the same Gmail account. If you wish to avoid this for troubleshooting purposes you can open the Market and press Menu>My Apps and uninstall your applications. Alternatively, after the factory data reset, you can wait to enter your Gmail account until you have had a chance to test the phone functionality.
A factory reset will clear all of the settings and data from your phone's internal memory and restore your device to its default state. Media on your storage card, which includes your pictures and videos, however, will not be affected. To perform this reset, from the home screen, press menu=>settings=>SD & Phone Storage=>Factory Data Reset.
If device behavior continues we are asking customers to swap their devices out at a Verizon store. However, you can also use your warranty with HTC by calling our warranty provider PCD at 1-800-229-1235 (8:30 AM - 5 PM EDT M-F).
To send a reply to this message or let me know I have successfully answered your question log in to our ContactUs site using your email address and your ticket number XXXXXXXXXX.
Sincerely,
Douglas
HTC
Braggo said:
The latest CM7 Alpha build from Slayher is almost problem free for me (no big issues, all data etc. working great) and I've had lots of problems with previous builds. It's worth a shot.
Click to expand...
Click to collapse
I would but there is no 4G LTE on CM7, and I'm not willing to give it up since I live in an area with the service, but to anyone that isn't in the 4G area, CM7 is a great choice.
We already knew it was coming in summer the problem is when in summer? Summer can go all the way to the end of August basically so its really cloudy as to a somewhat exact date.
ctinsley said:
I would but there is no 4G LTE on CM7, and I'm not willing to give it up since I live in an area with the service, but to anyone that isn't in the 4G area, CM7 is a great choice.
Click to expand...
Click to collapse
From what I understand, the 3G/4G/WiFi handoff is fixed in the version released early this morning/late last night.
We went threw the same thing with the incredible-froyo update. When we get updates, is anyone else like, wow that took a year?? Sure we get a couple new features and performance bumps and new extra awesome crapware, but this time I don't think I'll be marking off days on the calendar.
Sent from my ADR6400L using Tapatalk
miketoasty said:
We already knew it was coming in summer the problem is when in summer? Summer can go all the way to the end of August basically so its really cloudy as to a somewhat exact date.
Click to expand...
Click to collapse
Exactly. So if you're itching for some Gingerbread, you might as well flash one of the roms based on the GB leak. Otherwise you could be waiting much longer than expected
Sent from my ADR6400L using XDA App
ctinsley said:
I would but there is no 4G LTE on CM7, and I'm not willing to give it up since I live in an area with the service, but to anyone that isn't in the 4G area, CM7 is a great choice.
Click to expand...
Click to collapse
From work to my house to my girlfriends house, I have 4g everywhere. That was the sole reason I dumped CM7. After last nights update, I figured I would give it a try, and am glad I did! 4G Has been fixed and this is now the ROM to use! Everything is working great and have had 0 issues after using it for the last 12 hours or so.
@Miketoasty Do you have a link to your particular ROM and radio?
Sent from my ADR6400L using XDA App
rester555 said:
@Miketoasty Do you have a link to your particular ROM and radio?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Just the latest cm7 and dream kernel. Both on the first page of the dev section.
Sent from my ThunderBolt using XDA App
I hope it comes soon. I'm strongly considering going back to das bamf 2.0 but don't want to brick my phone
Sent from my ADR6400L using XDA App
I didn't know that the DAS BAMF 2.0 was causing some of the bricks. I guess that makes sense being that it is on the leaked version of GB
miketoasty said:
We already knew it was coming in summer the problem is when in summer? Summer can go all the way to the end of August basically so its really cloudy as to a somewhat exact date.
Click to expand...
Click to collapse
unless HTC/VZW observes Indian summer....
Sent from my ADR6400L using XDA Premium App
I'm running das bamf 2.0 and its GB 2.3.3 with sense 3.0. Runs flawless, quick, and battery is better than anything I've used before.
Sent from my DasBAMF 2.0 Thunderbolt using XDA App
MsSassypants said:
unless HTC/VZW observes Indian summer....
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Please don't jinx it I could so see a developer like Motorola or Samsung pulling something like that.
"Oh yea by summer we actually meant Indian summer so yea just buy a new phone if you want gingerbread now."

Nexus s search bug

I get repetitive search presses automatically every so often...anyone know why this is happening? I searched on Google and it says that it is a bug on some nexus s Canadian version..but there are no fixes at the moment..anyone also having this problem?
Sent from my Nexus S using Tapatalk
It's in all versions. There is another new thread on here that suggests flashing a new radio fixes the issue. Haven't tried it yet but will.
donnieace said:
It's in all versions. There is another new thread on here that suggests flashing a new radio fixes the issue. Haven't tried it yet but will.
Click to expand...
Click to collapse
Thanks going to check out some radios and report back
Sent from my Nexus S using Tapatalk
it only affects the i9020a (AT&T version) and the false search activations are related to signal strength, the lower the signal, the more often the search will fire.
Officially, according to Samsung, 2.3.6 fixes the issue.
Playing with different radios can have an impact, the best will be the most recent (the one included in 2.3.6). The software fix mitigate the problem by suppressing search activations that it thinks are false positives.
For a true fix is sending it to Samsung for a screen replacement. I got my phone back and have had no false search activations since. I told them that I was on 2.3.6 and that I was still having search activations, they authorized a repair. replaced the screen and that's that.
On the official 4.0.4 OTA for the i9020A and the bug is STILL present.
I popped my SIM in and did some browsing on 3G in my house (terrible signal) and after about a minute, the search button began firing.
crachel said:
On the official 4.0.4 OTA for the i9020A and the bug is STILL present.
I popped my SIM in and did some browsing on 3G in my house (terrible signal) and after about a minute, the search button began firing.
Click to expand...
Click to collapse
Are you using the new radio for 4.04 too?
Sent from my Nexus S using Tapatalk
Imppy said:
Are you using the new radio for 4.04 too?
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Yep.. this occurred on a completely stock, OTA 4.0.4 with the new radio.
I had this problem a few months ago. I resolved it by flashing the following radio:
http://forum.xda-developers.com/attachment.php?attachmentid=766907&stc=1&d=1320037083
This is latest radio for I9020A Radio UCKF1 (New Version) from this thread:
http://forum.xda-developers.com/showthread.php?t=1116884
If you plan to change you radio, make sure you backup your EFS folder.
Are you on nexus s 4g? The new radio kj1 for nexus 3g seems to have fixed the issue!
Sent from my Nexus S using Tapatalk
I haven't seen it with UCKE1 or UCKJ1
i don't have the search bug, but have the automatic back firing bug? anyone have this too?

Categories

Resources