Discussion in 'Android Devices' started by Homeuser66, Oct 9, 2012.
Yeah, UVKL1 was the update from 2.3.5 to 2.3.6 back in December.
Ok...I reset my router too, I think I had to do that too, for some reason...don't know why, but it appears I am connected now...
EDIT: Update- I had to Reset my router (which I said already), but then I also had to go to MENU>>Wireless and Network.. then I had to Untick Wi-Fi calling as it said some sort of Error R906??? or something like that. then once I re-ticked the box to enable it, I got the Wi-Fi Blue Icon back on top and I was connected to my Wifi and able to make and receive calls.!!!
I don't know why, but it now works!! Thank you for your guidance and help! I will be testing this for a few days and see if I am back to normal, then I will be doing my Wife's phone too...as she hates the updates as well!!
Great! Glad you got it working. :thumbup:
So am I...I posted an EDIT/Update....to that previous post...lol
So, what version are you running?
I'm running stock ICS 4.0.4. I rooted it and removed most of the T-Mobile bloat crap. I've tried a lot of custom roms but I always come back to the rooted stock.
Ok...Good to know... I just tested it and my call disconnected before he could pick up....so I'm restarting phone and gonna see what happens...I may upgrade to the next ROM....I remember that happened before too...
UPDATE: I redid my ROM again with the same Version. 2.3.6 UVLDE/ Kernel- 22.214.171.124 and I must say, other than me not being able to call my freind in PA, (in WiFi Mode only) I can call everyone else. I also must add, that my phone is lightening fast again!!! I noticed while using ICS, my RAM was well into 550-650 MB of use. Now I am only in the mid 300 MB range. and yes, that was checking it right after the Factory Reset and install of ICS with no apps or data installed, and the same goes for this version I am currently using....
Dies it matter if you check, or don't check the developer option? I did it on mine, but not on my wifes, but it looks like it worked anyway.
Well, i thought it did. If it worked I guess that's the important thing.
Roger That! Thanks again for your help and your AWESOME walk through!
You're welcome. Glad you got your phone 'back'.
No trouble at all, your posts have helped me a lot, thanks again.
Just an update... accidentally solved my calling issue??
I flashed back to 4.0.3 but then botched the titanium backup app restore, so I decided to restore my nandroid backup and start over. After I restored, I decided to give it a day back in its stock 4.0.4 rooted state just to see if the calling issues were still there. Over the span of the day today i made or answered about 7 calls (some wifi, some cell tower) and not a single issue so far. So i'm keeping it like this for a while to see if problems come back.
Weird part 1:
I assumed the nandroid backup would restore the calling problem along with everything else since the problem was present when I made the backup. The only explanation I can think of as to what possibly could have helped is that I did a Darkside super wipe before I restored, and cache wipe after. I know that just a plain system restore did not help it previously.
Weird part 2:
I noticed that after I restored the nandroid backup, my phone info is as follows:
Android Version: 4.0.4
Baseband version: T989UVLE1
Build Number: IMM76D.UVLH1
Not sure how I ended up with the the UVLH1 build and the UVLE1 radio... I guess it must have been like that all along which means that my Kies update from 4.0.3 to 4.0.4 left me like that?
So that's where I'm currently at. Sorry to ramble, but maybe it might help someone with the same problem who comes across this thread.
If the dreaded calling problem comes back, my next try is to flash the UVLH1 radio I guess, since it looks like I didn't have it all along.
The reason it is like that is because you Odin'ed to 4.0.3 but your nandroid is 4.0.4. Flashing the UVLH1 radio should fix it. The only problem I know it would cause the way it is now is with Kies. If there is ever an update over Kies, it won't recognize your phone with the mismatched baseband and build.
What is this Nandroid you speak of?
I got my calling issues back again..and along with that, I also got the "Unknown" caller on the Caller ID. This was a problem we had when we were using the (December 12th 2011 version) 2.3.6 Version along with T989UVLDE and Kernal 126.96.36.199. With that said, I am now going to go forward a version or 2, for a May 9th 2012 date, weather it was a patch or what. I don't remember that around that time, things were working fairly well...
If you are rooted, you cam make a backup of your system in recovery. The backup is called a nandroid. ICS came out in June so I think the one in May would be UVLDE. It was the last GB update before ICS.
That's what I thought..(on both the above) Hopefully, if I recall, that was when we were working flawlessly....that is why I am choosing that now...I'm hoping the update is Cumulitive and I don't have to start from the first Firmware and reinstall them all up till the date I want...
Here is a list of Firmwares I got from SamMobile:
Country/Carrier Date Android PDA
USA (T-Mobile) 2012 August 4.0.4 T989UVLH1 T989TMBLH1
USA (T-Mobile) 2012 June T989UVLE1 T989TMBLE1
USA (T-Mobile) 2012 May T989UVLDE T989UVLDE
USA (T-Mobile) 2011 December 2.3.6 T989UVKL1 T989UVKL1
USA (T-Mobile) 2011 December 2.3.6 T989UVKL1 ## T989UVKL1
USA (T-Mobile) 2011 September T989UVKID T989UVKID
Ahhh... I see. That makes sense now. Thank you. I was assuming the nandroid restore would restore the radio also.
I am happy to report that neither my wife (who i Odined back to 4.0.3 a few days ago), nor I (who now ended up with 4.0.4 but with the radio from 4.0.3) has had any problems with any phone calls.
I think that means that the solution to the calling problem for me was to use the UVLE1 radio, at least it's working so far (fingers crossed).
Give it a shot, Homeuser66... try Android 4.0.4 but then flash the UVLE1 radio from 4.0.3... might also want to look into rooting and making a nandroid backup, it could save you. Rooting will also allow you to install TitaniumBackup which will give you some powerful tools.
I just got a new galaxy 2 from t-mobile with 4.0.4 on it and am having calling issues. I was thinking of rooting my phone and loading the 4.0.3 ROM but will I still have the wifi calling feature?
You should. I went back to Gingerbread
2.3.6, and I have it. That wifi calling feature came out in December 2011. As fast as, if you root it? I'm not sure.
I would just flash the radio from 4.0.3 (UVLE1) instead of the whole 4.0.3. 4.0.4 is pretty universally considered a much better version. The UVLE1 radio seemed to fix my issues, and that way you still get to have 4.0.4.
I believe you can flash the radio even if you decide not to root... although that's not the way I did it. I rooted mine so that I could have the peace of mind of having a Nandroid and Titanium backup.
How do I just flash the radio to 4.0.3 (UVLE1). Is there a guide to do this? I am new to this! This way I can keep 4.0.4.
Hi bfranc. To flash a radio, you would have to be rooted. Here is a guide for rooting if you decide you want to do that. There is a link in the All Things Root Guide for all the compatible radios. The UVLE1 radio is here.
Just an update for anyone troubleshooting the calling problem. A few days ago I had a thought that maybe something about the Kies update process to 4.0.4 was what caused my calling problems, so I did a wipe, reset, and flash to 4.0.4 and left the stock 4.0.4 UVLH1 radio installed. I have not had a single problem with any phone call, wifi calling or cell tower calls. So that puts a big hole in my previous theory that my problems were being caused by the UVLH1 radio. Also, It seems that my reception for data and phone may be slightly better than when I was on the UVLE1 radio.
So I guess that forces my new theory to be that it was the actual upgrade from 4.0.3 (which is what came installed on my phone) to 4.0.4 via Samsung Kies, that caused the calling problems I was having (cant hear ring, cant hear other party, they can't hear me, etc.). Perhaps a good wipe and reset and then flashing straight to 4.0.4 via Odin results in a more stable install? Who knows, but that's where my troubleshooting has led me. I hope this helps someone.
I was wrong... uvlh1 started giving me the call audio problems again so I went back to UVLE1 and my calls have all been perfectly fine.... 3 weeks and not a single problem.
So I guess it was the UVLH1 giving me problems.
It's a shame, because I felt like I was getting beter data performace with the UVLH1.
I'm suburban St. Louis area for the record.
I also have an update:
I lasted about 1 month from the moment I went backwards in Firmware, when I started having the issue again. I called TM and made my way to their Level 2 Tech Support. Here, I first pulled my SIM card and battery and I asked them to "PURGE" the BLR or the HLR from their system to my Phone. Since then, I have NOT had one single issue with the WiFi calling. I was told TM was the only one who had this function and found out that mostly all TM phones had this issue, not any or many of other carriers had this issue..I got this information from my local Rep at a local TM store and he said it was a known issue, so this is worth a try, you don't have anything to loose...
Hey Homeuser :hello:
Thanks for the update. Hopefully that might help someone in the future.