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] 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] WiFi calling on EaglesBlood - seems to be stuck...?

I just fresh flashed to EaglesBlood
WiFi calling seems to be stuck. It says "enabling" but it's stuck on this forever.
I did a reset (just in case) - didn't fix it
any thoughts?
Thanks!!!

Wifi calling is notoriously bad. It will work fine for some and barely ever work for others. My completely stock 2.3.3 had the same problem time and time again, as does my phone in its current setup. I believe the problem is external.
Sent from my LG-P999

e4e5nf3nc6 said:
Wifi calling is notoriously bad. It will work fine for some and barely ever work for others. My completely stock 2.3.3 had the same problem time and time again, as does my phone in its current setup. I believe the problem is external.
Sent from my LG-P999
Click to expand...
Click to collapse
Thank you. That's so odd, during the night (did you notice XDA was down for maintenance?) i switched to Weapon ROM and the WiFi issue persists. Yet my wife's phone, the Vibrant, stock rom of course, does the WiFi thing every time and right on the money. Damn it LG!

I think I remember reading that it was having trouble switching DNS servers when needed or something along those lines. I found plenty of feedback on these forums if you want to do a quick search and see if you can dig anything up.
(Yeah, I noticed the forums went down for a bit. I was in the middle of something at the time and really needed links!)

e4e5nf3nc6 said:
I think I remember reading that it was having trouble switching DNS servers when needed or something along those lines. I found plenty of feedback on these forums if you want to do a quick search and see if you can dig anything up.
(Yeah, I noticed the forums went down for a bit. I was in the middle of something at the time and really needed links!)
Click to expand...
Click to collapse
Thx!
Tsugi ROM solved this it's no working!
(yes I am on a ROM chase - I have some free time so I decided to not give up until I make this device owned!

[Q] Installing V21Y 2.3.4 Update and corrupting cell connection

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]

Has anyone encountered this voice mail bug?

Hey all,
Ugh, didn't mean to post yet!
I just updated from CM9 to 10.2 in the hopes it might fix this bug, but it didn't. I suspect then that it's not ANYTHING to do with a ROM per se but I'm perplexed as to what it is.
The behaviour is:
- I get a voice mail
- After listening to the voice mail, deleting it, and hanging up, the notification doesn't disappear
- Some time later, I get a repeat notification of the voice mail
- During this time, I can't receive any texts
- About a DAY later, the phone will realize that voice mail actually has been deleted
I've tried searching xda, and I've tried general googling, but I haven't pinned anything down. I've seen some references to what might be a similar bug, but not with these ROMs, and... honestly a couple of YEARS ago.

ccamfield said:
Hey all,
Ugh, didn't mean to post yet!
I just updated from CM9 to 10.2 in the hopes it might fix this bug, but it didn't. I suspect then that it's not ANYTHING to do with a ROM per se but I'm perplexed as to what it is.
The behaviour is:
- I get a voice mail
- After listening to the voice mail, deleting it, and hanging up, the notification doesn't disappear
- Some time later, I get a repeat notification of the voice mail
- During this time, I can't receive any texts
- About a DAY later, the phone will realize that voice mail actually has been deleted
I've tried searching xda, and I've tried general googling, but I haven't pinned anything down. I've seen some references to what might be a similar bug, but not with these ROMs, and... honestly a couple of YEARS ago.
Click to expand...
Click to collapse
I have not seen this on any of my T-Mobile phones....did you do a full wipe before flashing CM10.2..
Which 10.2 Rom did you flash..
You Might have to one-click back to
stock.
That should fix it..then work back up.
Sent from my SM-G900T using XDA Premium 4 mobile app

Well, I did do a factory reset.
Is resetting to the stock ROM actually guaranteed to, well, basically format /system?
(Oh, and I flashed this ROM: http://forum.xda-developers.com/showthread.php?t=2451317 )
P.S. see here for someone's... probably unorthodox solution to the problem. Basically seems to be forcing # of voice mail notifications to 0. Which isnt really what I want, anyway.
http://forum.xda-developers.com/goo...w-to-sprint-fix-persistent-voicemail-t2562262

ccamfield said:
Well, I did do a factory reset.
Is resetting to the stock ROM actually guaranteed to, well, basically format /system?
(Oh, and I flashed this ROM: http://forum.xda-developers.com/showthread.php?t=2451317 )
P.S. see here for someone's... probably unorthodox solution to the problem. Basically seems to be forcing # of voice mail notifications to 0. Which isnt really what I want, anyway.
http://forum.xda-developers.com/goo...w-to-sprint-fix-persistent-voicemail-t2562262
Click to expand...
Click to collapse
That looks like a work-around not a solution. .
Yeah if you odin back to stock...
Its a guarantee it will format your system partition..
Try gremlin remover its always worked for me and odin is pretty simple..follow the OP its a one-click pre-made odin setup so dont change anything and your good.
http://forum.xda-developers.com/showthread.php?t=1500427
Once your back to stock...
And the problem is fixed.
I always went to Team Acids CM9.
Let the partitions convert..
Then on to CM10.2 or whatever..
Never had a problem this way..
Sent from my SM-G900T using XDA Premium 4 mobile app

hutson23 said:
That looks like a work-around not a solution. .
Yeah if you odin back to stock...
Its a guarantee it will format your system partition..
Try gremlin remover its always worked for me and odin is pretty simple..follow the OP its a one-click pre-made odin setup so dont change anything and your good.
http://forum.xda-developers.com/showthread.php?t=1500427
Once your back to stock...
And the problem is fixed.
I always went to Team Acids CM9.
Let the partitions convert..
Then on to CM10.2 or whatever..
Never had a problem this way..
Click to expand...
Click to collapse
Unfortunately, I have the 959W rather than the 959V so I can't use it.
And I remember upgrading from gingerbread to CM9 was a lot tougher than I expected (I think getting the drivers to work right) and I had to get a LOT of help from a member here on the forum. IIRC there were a lot more reboots required of the phone / my PC to get things to work.
All in all I probably shouldn't mess around with ROMs. Hardware problems make me angry and frustrated.

ccamfield said:
Unfortunately, I have the 959W rather than the 959V so I can't use it.
And I remember upgrading from gingerbread to CM9 was a lot tougher than I expected (I think getting the drivers to work right) and I had to get a LOT of help from a member here on the forum. IIRC there were a lot more reboots required of the phone / my PC to get things to work.
All in all I probably shouldn't mess around with ROMs. Hardware problems make me angry and frustrated.
Click to expand...
Click to collapse
O..didn't know you had the T959w..
Well I have seen something similar
On the Samsung GS4G Blaze..
They had a call fowarding bug that was carrying over on Roms..
It was something in CM11 that they
Figured was being written on the
Sim Card..and it was even carrying over to any Rom you flashed..
Once you got it... it didn't matter
what Rom you installed
full wipe or not it stuck..
They have Offical CM11 and the
CM team fixed it..but I remember it took a couple weeks..
Have you tried getting another
Sim Card..couldn't hurt..
Have you tried Force closing the
Phone Apk.and clearing data..
Also found this..
Here's what just worked for me on my Tmobile Galaxy S III
1) Pull the battery
2) Wait a few minutes with the battery out (I waited 5 minutes)
3) Pull the SIM card
4) Replace battery and power up phone. Wait until phone is fully booted
5) Power down phone
6) Replace SIM card and power up
Annoying VoiceMail icon is now gone.
BTW.. I hate the voice mail notification...
I wish people would
Never leave me a voice mail..LOL..
Sent from my SM-G900T using XDA Premium 4 mobile app

Oh huh, I missed your reply till now.
I think force closing the phone app and clearing caches works but ONLY temporarily and then the problem reoccurs (when the phone decides to check for more voice messages?)
Man if this was something being written on the sim card and not a ROM thing that'd be really annoying. But couldn't I "just" wipe the whole sim card? That's gotta be possible, right?
I'm trying the pull-battery-and-sim-card just to see what happens.
On the plus side I found some old posts of mine on the forum and realized that I only ever used this new computer for flashing stuff. So I just have to figure out which USB port worked last time... the usb drivers should still be installed and everything.

^ Just curious what modem are you using? Is it patched to work on MTD partitions layout? Is it the stock one from Wind the Canadian carrier?
Try using modem LB6 for 959w/v patched to work for mtd roms, hope this will fix the issue.

Rebel_X said:
^ Just curious what modem are you using? Is it patched to work on MTD partitions layout? Is it the stock one from Wind the Canadian carrier?
Try using modem LB6 for 959w/v patched to work for mtd roms, hope this will fix the issue.
Click to expand...
Click to collapse
I believe I am using the LB6 - certainly, I'm not using the stock. (The only confusion is that I've got zip files on my PC for the LB6 and a KG4 modem.)
Whatever modem I have on my phone was working fine prior to some upgrade of CM9 (IIRC).

God!!!
So I got Heimdall working again, flashed to stock, reformatted my SD card, re-updated to CM10... and I'm getting the same problem again!
So either it's the CM 10 ROM or something with my phone company! GRRRR...
Maybe the next step is to go back to stock and then just try CM 9. Or even CM 7 or something... put a modem on the stock ROM and see if THAT still ****s up.

Aaaaand stock + LB6 modem gets the voice mail notifications.
!%()*!%()*!#% phone company!