I updated my stock Rogers Nexus 9020A via the manual update to 2.3.4 update went fine but now my search button randomly flashes and executes on it's own...is this a bug in stock 2.3.4? Also did a factory reset still problem exists.
Anyone else experience the same?
Im on Rogers as well. Had no problems at all...certainly not like this. Then i ended up switching to custom ROM's and what not just to add some enhancements. Try re-flashing? Did you create a backup first?
I had this problem prior to updating to 2.3.4. It has been 12 hours and I have not seen it occur. I am crossing my fingers on this one. Google claims they are investigating the issue. There were a lot of complaints on the Google Mobile forum. It seems random and occurs maybe once or twice a day, sometimes it skips a day.
So I was able to figure out the cause for the search button bug was the Baseband switching to KD1....I reverted back to 2.3.3 with baseband KD1 but problem still occured...once I switched the radio back to KB2 problem was gone....so any ideas on what I should do to get the Stock 2.3.4 update to function on my rogers device without the search button bug? I have not received any OTA notice on my phone yet. Anyone on Rogers receive the OTA?
So after trying to flash 2.3.4 many ways it is evident the baseband of KD1 is causing my Nexus S this search button bug. So now I am using 2.3.4 with the KB2 radio and it is rock solid. Anyone have an idea why only a select few nexus s 9020A phones are doing this after the 2.3.4 update?
Looks like a lot of people with the Canadian version Nexus S 9020A are experiencing the same problem once they upgrade OTA to 2.3.4 .....google is trying to narrow down the problem.
http://www.google.la/support/forum/p/Google+Mobile/thread?hl=en&tid=49e8ca84071d51a4&start=80
I cleared Dalvik cache, did not resolve the issue.
I know downgrading to kb2 would solve a lot of the issues, but then i still have issues with the search bug during navigation.
Let's see if we can figure this out.
Matridom said:
I cleared Dalvik cache, did not resolve the issue.
I know downgrading to kb2 would solve a lot of the issues, but then i still have issues with the search bug during navigation.
Let's see if we can figure this out.
Click to expand...
Click to collapse
Looks to be a confirmed bug in KD1 baseband:
http://mobilesyrup.com/2011/05/23/canadian-nexus-s-experiencing-voice-search-bug/
So your saying since you bought your nexus s with the stock 2.3.3 you have had this issue?....and is the issue worse once you update to 2.3.4 like I have?
Rob
richerob said:
Looks to be a confirmed bug in KD1 baseband:
http://mobilesyrup.com/2011/05/23/canadian-nexus-s-experiencing-voice-search-bug/
So your saying since you bought your nexus s with the stock 2.3.3 you have had this issue?....and is the issue worse once you update to 2.3.4 like I have?
Rob
Click to expand...
Click to collapse
Yup. I need to do more testing but with kb2 I would only get it in gps mode.
Sent from my Nexus S
Related
I made a youtube video of my problem here:
youtube.com/watch?v=LL_kubZ4ENc
Have anybody else had this issue with their touchscreen? I have tried to factory reset the phone. Go back to stock rom lock the bootloader, and unroot. But the problem still appear. Also tried to clean the screen and only charge it with the original charger. Nothing helps I have tried to send questions to samsung but no answers.
Have anyone here had similar issues and found a fix?
qaaqq said:
I made a youtube video of my problem here:
youtube.com/watch?v=LL_kubZ4ENc
Have anybody else had this issue with their touchscreen? I have tried to factory reset the phone. Go back to stock rom lock the bootloader, and unroot. But the problem still appear. Also tried to clean the screen and only charge it with the original charger. Nothing helps I have tried to send questions to samsung but no answers.
Have anyone here had similar issues and found a fix?
Click to expand...
Click to collapse
I have the same issue, only the position is different. Have you worked out a solution? Or still waiting for it? Anyone?
Im on Miui with matrix cfs 5.5 (9023)
huh, if anyone have this problem... I really tried almost everything that came to my mind or sparetime, but installing a 2.3.5 based rom solved the problem even with miui it works just fine
bucimaci said:
huh, if anyone have this problem... I really tried almost everything that came to my mind or sparetime, but installing a 2.3.5 based rom solved the problem even with miui it works just fine
Click to expand...
Click to collapse
I have this problem also, im on CM7 nightly. cant unlock the screen. Phones barely 3 days old
Had that same problem, and it's gone now. Don't know what did fix it, but I flashed new radio and Trinity kernel, and the problem is gone now...
I thought with the 2.3.5 the problem was solved, but its back now... dunno what it is, my phone is 2 weeks old.
I'm experiencing the same issue on a stock, not rooted or in any way modified Nexus S I9023 (SCLCD version) with Android 2.3.6
Also the settings button is right under the line (so the location is different from the video) and it is unresponsive as well.
Does anybody have any idea what to do about this???
Well, here goes.
I've been reading alot for quite a while, and learning everything I could around this place. Thanks to tall who contribute.
I'm running NScollab, 1.0.42, with matrix 8.0 kernel.
Currently on the XXKB3 baseband.
Following this thread http://forum.xda-developers.com/showthread.php?t=1116884
I tried flashing the new KF1 radio for the nexus S. No luck. Either is doesn't flash at all ( status 6 error ) or when it does ( the signed version can be flashed in CWM ) no signal whatsoever. I've tried everything, changing the band, ( *#*#4636#*#* ) rebooting 45 times, dalvik wipe, changing type of radio, all guides, searched google, this website ( for a whole week ).
Nothing came up.
I'm posting, because this is pretty much last resort. I actually tried the KF1 radio on Miui, devnull, oxygen, and NScollab.
Telus users out there, what is your baseband ? What radio gives you the best signal and performance ? I know koodo switched to KF1, but I can't get it to work on my NS.
Any help is appreciated !
still noone ?
Darn.
wrick01 said:
still noone ?
Darn.
Click to expand...
Click to collapse
I use KB3 for koodo(telus). I get signal... and it works.
I'm curious as to whether KF1 would be a better radio for us, or if it even works for Telus/Koodo. Anybody know?
MC
1
xcoley said:
I'm curious as to whether KF1 would be a better radio for us, or if it even works for Telus/Koodo. Anybody know?MC
Click to expand...
Click to collapse
I have a Telus Nexus S in BC and I just installed an OTA update to 2.3.6 / GRK39F / I9020AUCKF1 and the KF1 radio seems to be working fine. I've been able to call around and MMS without issues so far. (about 2 hrs) Not enough time spent with it to tell you if it gets better reception or not...
I acutally installed the OTA pacakage in order to go back to stock as I was getting sick of the Search Bug that has been plaguing my phone for ages and I was going to bring it back for warranty work, but it appears the flash of the radio to KF1 that was included in the package has resolved the Search Bug!
Sweet! So, I might stick with this for a bit to confirm it is gone and and if all is well, I guess there's no need to return the phone for service!
I have the same issue on koodo. Flashed ICS and I get reception with KF1 downtown but barely anything at home and it used to be great.
I'm running the UCKF1 radio on my telus NS, on cm9 + matrix 14.5. With my phone, it was impossible to flash the radio with CWM, it would flash, but could not get on the network. I had to use fastboot to flash the radio.
In my experience, XXKB3 and XXKD1 were definitely the fastest radios (no upload cap), but my connection was unstable, needing occasional reboots to reestablish connection if I ever lost reception. UCKF1 has been rock solid for me. (I'm in the Toronto area)
Also, for some reason I only started getting the search bug with ICS and XXKD1, but UCKF1 fixed that.
Sent from my Nexus S using XDA App
So I've been trying to upgrade my phones from a custom ROM to the official 4.0.4 releases on Nexus S 4G. So I flashed the IMM76D signed zip (flashable one) and got it working. A bit after this, I noticed that I wasn't getting SMS messages. I'm not going to bore you guys with a backstory, so I'm just going to say what I did.
I used "SMSC Updates" found on the Cyanogenmod Wiki to update my SMSC settings (tried all of the following numbers: 07918188561627F7, 07917140140000F0) after seeing it as a suggestion somewhere else about SMS issues. I re-flashed the radio (the new one that released with 4.0.4), and I still cannot get it to work.
I've tried several ROMs, too. Un-rooted, re-rooted, had problems with recovery (solved those, though), and re-rooted again. Also, attempting to use 4G settings crashes the phone.
Does anyone have any suggestions for what I should do? As far as I know, I'm able to send SMS, but not receive. Could this be a Sprint issue?
Thanks.
xation said:
So I've been trying to upgrade my phones from a custom ROM to the official 4.0.4 releases on Nexus S 4G. So I flashed the IMM76D signed zip (flashable one) and got it working. A bit after this, I noticed that I wasn't getting SMS messages. I'm not going to bore you guys with a backstory, so I'm just going to say what I did.
I used "SMSC Updates" found on the Cyanogenmod Wiki to update my SMSC settings (tried all of the following numbers: 07918188561627F7, 07917140140000F0) after seeing it as a suggestion somewhere else about SMS issues. I re-flashed the radio (the new one that released with 4.0.4), and I still cannot get it to work.
I've tried several ROMs, too. Un-rooted, re-rooted, had problems with recovery (solved those, though), and re-rooted again. Also, attempting to use 4G settings crashes the phone.
Does anyone have any suggestions for what I should do? As far as I know, I'm able to send SMS, but not receive. Could this be a Sprint issue?
Thanks.
Click to expand...
Click to collapse
When you say new radio, do you mean LC1? I have had that radio for a week and all is good. If I were you I'd take a screenshot of my current setup and post it on here. I would try to, if you haven't already updating Prl and Profile and call Sprint and get them to reprovision your phone.
Hope you get it fixed soon. Sorry I couldn't be of more help..
xation:
Have you resolved your SMS issue?
My wife's S4G is doing the same thing after OTA: can't send, only receive SMS. MMS, on the other hand, are fine.
I've also tried the mentioned CM SMSC update, did not work; tried (*#*#72786#*#*) re-provision, but no luck.
Running out of ideas...
Just a follow up:
I installed Go_SMS, un-installed Handcent, and SMS started working!
I used odin when the 4.0.4 official leak was posted here. I since uses the one click software restore back to 2.3.4. At first it gave an issue with the radio. On my phone while restoring it said "radio fail" but the phone seems to be working.
Now I manually updated the unrooted Sprint official 4.0. And my phone since the very first thing I said, has been randomly rebooting, I tried a different battery and it does the same thing. It's also real laggy. Any advice? Are there stock 2.3.4(7) files I can odin? I want it completely factory. Or suggest the problem? Thank you.
Bumping
Hi all -
I recently updated to the 4.4.3 VzW firmware and upgraded from Viper 1.8.0 to Viper 2.5.0. Since upgrading, I have been having troubles with my hotspot. After being on and other devices have been using it for a bit, my M8 begins to rapidly turn on/off the Data Connection. This doesn't stop and the only way to fix the problem is go into airplane mode and back out again. I figured that I may have had a bad flash, so i tried reflashing clean downloads of both the firmware and a full wipe and reinstall of ViperOne, but still seeing the exact same issue. I seem to be also experiencing a problem where my phone is reporting a 4G connection, but data is disconnected and i cannot get anything over the data channel. Voice works fine. Again, to fix it's a cycle through airplane mode.
I tried applying the changes recommended by for the 4G handoff fix, even though the problem described does not seem to be exactly the same as mine. It did not seem to help, and mae it even harder to get a reliable 4G connection.
http://forum.xda-developers.com/verizon-htc-one-m8/general/verizon-4g-handoff-fix-t2868778
Has anyone else seen anything like this and have any recommendations for a fix?
Just realized this would be better in the troubleshooting forum. Is there a way for me to move it there or does that require a moderator?
Check http://forum.xda-developers.com/verizon-htc-one-m8/help/loss-lte-data-using-ap-t2900047
I have had the same thing, going back to 1.55.605.2 FW does seem to be the fix, I think its something with 4.4.3 FW.
One of the so called improvements is Mobile hotspot connectivity, but maybe that's only with phones that don't use the patched default.xml,
the ones that really pay for the mobile hotspot.
kc6wke said:
I have had the same thing, going back to 1.55.605.2 FW does seem to be the fix, I think its something with 4.4.3 FW.
One of the so called improvements is Mobile hotspot connectivity, but maybe that's only with phones that don't use the patched default.xml,
the ones that really pay for the mobile hotspot.
Click to expand...
Click to collapse
Thanks for the reply - do you have a link for the old firmware, so i can flash and revert back to that?
Also - are you still running Viper 2.x or did you roll back to a prior ROM as well?
After some more searching, i found this link for stock 4.4.2 on VzW, but was wondering if anyone has the firmware only, so don't have to restore recovery, and rom afterwards.
http://forum.xda-developers.com/showthread.php?t=2727831
I certainly can and will do it, if necessary, just would prefer to have the firmware only, if someone has it available. Anyone?
Thanks in advance for the help!
Dave
deh2k7 said:
Thanks for the reply - do you have a link for the old firmware, so i can flash and revert back to that?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?w=files&flid=13966
Dl the one without boot img
Thanks, downloaded and reverted. Long boot times, but things working. Now to give the hotspot a few tests. I'll update with my results.
deh2k7 said:
Thanks, downloaded and reverted. Long boot times, but things working. Now to give the hotspot a few tests. I'll update with my results.
Click to expand...
Click to collapse
initial tests are very promising. hotspot seems to be stable and hasn't dumped the data connection yet. Looks like good old VzW managed to screw up the firmware update as usual. Would be nice if they didn't always to be different. Thank god for these forums and the hardworking devs here!
I spoke too soon. Still seeing the same issue after reverting the FW back to 1.55.605.2. Anyone seeing this? Any thoughts on if reverting back to Viper 1.8 would help?
deh2k7 said:
I spoke too soon. Still seeing the same issue after reverting the FW back to 1.55.605.2. Anyone seeing this? Any thoughts on if reverting back to Viper 1.8 would help?
Click to expand...
Click to collapse
I don't think it is the firmware that is the issue, I think it is the kernel. You should be good going back to Viper 1.8 as it uses an older kernel. I would think you would also be fine using the newer firmware and an older ROM version.
jsaxon2 said:
I don't think it is the firmware that is the issue, I think it is the kernel. You should be good going back to Viper 1.8 as it uses an older kernel. I would think you would also be fine using the newer firmware and an older ROM version.
Click to expand...
Click to collapse
I'm starting to believe this as well, that there's something flaky in the 2.x Viper ROMS for VzW and hotspots, and likely in the kernel. I've already reverted back to the old firmware, and I'm going to go back to a clean 1.7.x full install, then OTA to 1.8. Will update with the results.
deh2k7 said:
I'm starting to believe this as well, that there's something flaky in the 2.x Viper ROMS for VzW and hotspots, and likely in the kernel. I've already reverted back to the old firmware, and I'm going to go back to a clean 1.7.x full install, then OTA to 1.8. Will update with the results.
Click to expand...
Click to collapse
Any luck fixing this issue?