Database Users

T-Mobile USA and Older radios problem!

We all know that after updating to 4.2.2 via OTA and the new radio .48 the LTE is disabled.Some users have flashed older radios .27 and .33 and were successful enabling LTE again on our devices! However most of T-Mobile USA users(including myself) are NOT able to get older radios work on stock rooted 4.2.2! After flashing older radios you have usable data connection but no audio in call! I`m not able to hear anything when connected to a call! So far I have tried:
1.Flashing .27 radio and installing the RIL for 4.2.1= no audio in call
2. Flashing .33 radio and installing the RIL for 4.2.1= no audio in call
If anyone has been successful getting it work on T-Mobile USA, please share your steps and methods to achieve that!
Thanks

BigDig said:
We all know that after updating to 4.2.2 via OTA and the new radio .48 the LTE is disabled.Some users have flashed older radios .27 and .33 and were successful enabling LTE again on our devices! However most of T-Mobile USA users(including myself) are NOT able to get older radios work on stock rooted 4.2.2! After flashing older radios you have usable data connection but no audio in call! I`m not able to hear anything when connected to a call! So far I have tried:
1.Flashing .27 radio and installing the RIL for 4.2.1= no audio in call
2. Flashing .33 radio and installing the RIL for 4.2.1= no audio in call
If anyone has been successful getting it work on T-Mobile USA, please share your steps and methods to achieve that!
Thanks
Click to expand...
Click to collapse
I had the same issue. .33 screwed up my phone. I couldn't hear anything from the earpiece. Unfortunately I found the reason why and .48 fixed the problem. Anyways, which city do you live in that has LTE from T-Mobile? There are very very few LTE coverage in USA from t mobile. It would be pointless to enable lte if you do not live in a lte coverage area. I don't know why .33 won't work on 4.2.1. It should work.
Sent from my Nexus 4 using Tapatalk 2

scream4cheese said:
I had the same issue. .33 screwed up my phone. I couldn't hear anything from the earpiece. Unfortunately I found the reason why and .48 fixed the problem. Anyways, which city do you live in that has LTE from T-Mobile? There are very very few LTE coverage in USA from t mobile. It would be pointless to enable lte if you do not live in a lte coverage area. I don't know why .33 won't work on 4.2.1. It should work.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I live in Boston. I don`t know if LTE is live yet, but I just wanted to try and see. But older radios don`t work....Have you tried older radios+custom roms?

BigDig said:
I live in Boston. I don`t know if LTE is live yet, but I just wanted to try and see. But older radios don`t work....Have you tried older radios+custom roms?
Click to expand...
Click to collapse
I don't think it would matter if the phone was running on a custom rom with a old baseband. Basebands, bootloaders, kernels and roms are kinda like their own thing, y'know.

Same thing happened to me, had to go back to .48

scream4cheese said:
I don't think it would matter if the phone was running on a custom rom with a old baseband. Basebands, bootloaders, kernels and roms are kinda like their own thing, y'know.
Click to expand...
Click to collapse
That's not exactly right though... The kernel controls the radio(baseband)
Sent from my Nexus 4 using xda app-developers app

Yeah!!! What's the deal with that I can't get .33 to work on stock rooted 4.2.2 I'm also from the Boston area.
Sent from my Nexus 4 using xda premium

If you want a solid ROM that works with the old radio use CM10.1 Nightlies . It works great with both radios.

Daddy_617 said:
Yeah!!! What's the deal with that I can't get .33 to work on stock rooted 4.2.2 I'm also from the Boston area.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yeah, I guess we have to jump to custom roms whenever LTE is live in Boston....

bump! Maybe a Dev can give us some more info on that matter???

I've seen the LTE APN setup in the switch as fast.Tmobile.com . I'm thinking you need that for it to work once it's turned on

Flashed .33 too and had no sound. Had to flash back 48
On Tmobile USA too
Sent from my Nexus 4 using xda app-developers app

I flashed Dark Jelly n4 with the .33 radio and it works fine coming from the .48 on t-mobile. (I was on stock originally then got the update)
No problem here but i am using the franco kernel if it matters.

djdanska said:
I flashed Dark Jelly n4 with the .33 radio and it works fine coming from the .48 on t-mobile. (I was on stock originally then got the update)
No problem here but i am using the franco kernel if it matters.
Click to expand...
Click to collapse
Very useful info! Thanks

[Q] Android 4.2 vs 4.2.2

I have a stock Nexus 4 and it says an Update is available.
So far, my phone has been working ok and I am afraid that the Update will cause issues.
Does anyone know what are the changes between 4.2 and 4.2.2?

krowc said:
I have a stock Nexus 4 and it says an Update is available.
So far, my phone has been working ok and I am afraid that the Update will cause issues.
Does anyone know what are the changes between 4.2 and 4.2.2?
Click to expand...
Click to collapse
An update doesn't cause issues, it fixes them... Especially an update from Google directly.
Also if you Google search "4.2.2 Changelog" you'll get what you're looking for.
Its not that hard. :good:

MrDarkKV said:
An update doesn't cause issues, it fixes them... Especially an update from Google directly.
Click to expand...
Click to collapse
LOL who told you that?

I am using stock non rooted 4.2.2 with no issues
Sent from my Nexus 4 using xda premium

krowc said:
I have a stock Nexus 4 and it says an Update is available.
So far, my phone has been working ok and I am afraid that the Update will cause issues.
Does anyone know what are the changes between 4.2 and 4.2.2?
Click to expand...
Click to collapse
I always flash the whole rom instead of OTA`s to avoid issues. You get them here https://developers.google.com/android/nexus/images#occam.

Radio update question

Let me start by saying I know I have asked a few questions lately and I really appreciate the help. I am brand new to the nexus and don't want to brick it. I don't got money to just get another if I break it so I am being very careful with what I flash.
That said, I am planning to update my radio and I have read a few threads with regards to the topic. I found most of what I needed to know. My problem is I read a lot of posts saying it "broke" sensors or WiFi when flashed with the 4.2.1 Roms. Now it also goes on to say that 4.2.2. works fine with the newest radio, but i also seen where some were using a older radio (.27 I think it was)
Question 1- Can I use the .27 radio with the newest roms or is there a reason I need to use the .48 radio? Reason being the newest radio disables lte connectivity. Maybe the .27 keeps it?
Question 2- do I need to flash the new bootloader with the radio?
Sorry to act like a noob but with my older g-1 flashing the wrong radio and SPL could brick the device. So once again I am just trying to make certain I am taking the right steps. Thanks in advance...
Sent from my Nexus 4 using xda premium

Question 1:
Some people lose audio on phone calls when running the older radios on 4.2.2, but CyanogenMod 10.1-based ROMs work fine with .33 or .27 basebands, at least in my personal experience.
Question 2:
Not sure if there is some interplay between the bootloader and whether the radios work on 4.2.2. Haven't heard of there being any issues in this regard.
Sent from my Nexus 4 using Tapatalk 2

Yeah I would figure the cm variants would be coded for all different radios . I just didn't know if anyone out there knew the exact differences in radios and bootloaders. I have read so many posts and still can't get a really clear explanation.
Sent from my Nexus 4 using xda premium

selfinflicted1 said:
Yeah I would figure the cm variants would be coded for all different radios . I just didn't know if anyone out there knew the exact differences in radios and bootloaders. I have read so many posts and still can't get a really clear explanation.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I flashed .33 radio on 4.2.2 in order to keep using LTE here in Mexico. Phone works fine, haven't had any issues with it so far.

pacoguevara said:
I flashed .33 radio on 4.2.2 in order to keep using LTE here in Mexico. Phone works fine, haven't had any issues with it so far.
Click to expand...
Click to collapse
So you're using CM 10.1 with Radio .33 without issues and maintaining LTE/4G connectivity?
If so is it the latest nightly?

I was under the impression that the 33 radio caused all kinds of problems with 4.2.2. Are you sure you aren't on 4.2.1? Its crazy because I seen a lot of posts saying that they never updated but everything worked right on 4.2.2. I really wish someone could shed light on this issue.
Sent from my Nexus 4 using xda premium

selfinflicted1 said:
I was under the impression that the 33 radio caused all kinds of problems with 4.2.2. Are you sure you aren't on 4.2.1? Its crazy because I seen a lot of posts saying that they never updated but everything worked right on 4.2.2. I really wish someone could shed light on this issue.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
+1
Sent from my Nexus 4 using Tapatalk 2

Apparently the issue with CM 10.1 and the older radio is you lose autofocus in the CM camera (for example, might be more issues). Now, being in the UK, I have no need for the old radio as we don't have proper 4G here yet so I'm all 100% up-to-date and it works fine. Once 4G comes about I'll get a 'proper' 4G phone

Rom 4.3

Rom 4.3 for mytouch 4g ?
Sent from my myTouch 4G using xda app-developers app

airport19832000 said:
Rom 4.3 for mytouch 4g ?
Sent from my myTouch 4G using xda app-developers app
Click to expand...
Click to collapse
Dude you already asked this I think...

There is no way any one of us can _ask_ for a 4.3 ROM for good old Glacier... Going for 2.2 to 4.2 was a huge feat. Going to 4.3 would be the most incredible feat ever. We should all appreciate the developers we have more, and thank them for their time, even if we will never have a 4.3 ROM.
Thanks guys!

I agree that all the devs deserve a huge thank you. I have a SGS4G and the devs there work very hard to get our phone to 4.0.4 to 4.1.2 to 4.2.2 to 4.3 even though Samsung said the phone can't handle it.
My buddy has a glacier and I have seen the great quality of Deva you guys have here and am sure they want 4.3 just as much as everyone here does. All I can suggest is patience and maybe a donation.
One thing we did to help "motivate" everyone is start a bounty threat. Everyone chip in and the pot goes to the dev that makes the first fully functional 4.3. Just a thought.
Sent from my SGH-T959V using xda premium

i cant wait for such rom to be out

Mods can close this since we now have 4.3 ROMs
Sent from my HTC Glacier using xda app-developers app

Speaking of that 4.3 ROM for the Glacier... my keyboard isn't working.
N_otori0us_ said:
Mods can close this since we now have 4.3 ROMs
Sent from my HTC Glacier using xda app-developers app
Click to expand...
Click to collapse
Great news that albinoman887 got 4.3 off the ground. Unfortunately, I have a problem, and since I'm the junior...est of members, I can't yet post in the development thread where I could ask him this directly, so I thought I'd give this thread a shot.
I did a factory reset on my MyTouch 4G, installed Albinoman's 4.3 (gapps-jb-20130726.zip) ROM and the new GApps (gapps-jb-20130726) zip linked to in his thread, rebooted, and everything appeared to be working until it was time to enter and sync to my GMail account, at which point I received an error message indicating that the AOSP Android keyboard had closed. Sure enough, every time I attempted to input anything, the message reappeared and I had no way of logging into my Google account. Touch screen input works, but without a keyboard, that's as far as I could go.
Thinking maybe I had a corrupted GApps zip, I did another full wipe, re-flashed the ROM, and this time tried the 07/13 GApps zip; unfortunately, when I rebooted, I got identical behavior. Since I needed to use my phone as a, you know, phone (they still do that!) tonight, I did yet another wipe, flashed the latest 4.2 ROM (also from Albinoman) and, to make sure it worked, the newest 07/26 GApps. No problems, seems to work perfectly.
I've checked albinoman's 4.3 thread, and, while there are a few bug reports, no one else seems to be having this keyboard problem. I never had (unusual) keyboard issues with 4.2 or any older ROMs, and it works fine now, so this doesn't appear to be a hardware issue.
Any suggestions? As a n00b, is there any way for me to message albinoman directly without coming off as a d-bag? Thanks in advance...

[Q] Only getting 1.5mb internet speeds on 12mb

Hi,
This is an odd one.
I get 12mb download speeds on my home wifi if i do a test from my laptop or girlfriends iphone. If I do the test on my Nexus i only get about 1.5mb.
If I reboot the router (Draytek) I get the full 12mb again for a few hours then it drops right back down to 1.5mb.
Now I know you are all thinking straight away its the router but I have recently changed this from a Linksy router to the draytek and had the same problem with that one, so it would appear it is my Nexus.
I am running PA with the latest Kernal for it.
Any ideas or help?

foxguard said:
Hi,
This is an odd one.
I get 12mb download speeds on my home wifi if i do a test from my laptop or girlfriends iphone. If I do the test on my Nexus i only get about 1.5mb.
If I reboot the router (Draytek) I get the full 12mb again for a few hours then it drops right back down to 1.5mb.
Now I know you are all thinking straight away its the router but I have recently changed this from a Linksy router to the draytek and had the same problem with that one, so it would appear it is my Nexus.
I am running PA with the latest Kernal for it.
Any ideas or help?
Click to expand...
Click to collapse
Try changing your Radio. Which Radio you are on? Latest is .98

sidnoit22 said:
Try changing your Radio. Which Radio you are on? Latest is .98
Click to expand...
Click to collapse
Thanks for the reply mate. Im new to this, how do I tell which Radio is installed and how do I update it if needs be?

foxguard said:
Thanks for the reply mate. Im new to this, how do I tell which Radio is installed and how do I update it if needs be?
Click to expand...
Click to collapse
In "About Phone" look for baseband (a.k.a. radio) version. But be careful, if you are using Jelly Bean ROM, your radio should be 0.84. If KitKat ROM, then the radio should be .97 or .98. Don't flash 97 or 98 on Jelly Bean ROM !!!

taodan said:
In "About Phone" look for baseband (a.k.a. radio) version. But be careful, if you are using Jelly Bean ROM, your radio should be 0.84. If KitKat ROM, then the radio should be .97 or .98. Don't flash 97 or 98 on Jelly Bean ROM !!!
Click to expand...
Click to collapse
Thanks for that,
im on PA which is still Jelly Bean isn't it?
But the radio is 0/84, is that what it should be?

foxguard said:
Thanks for that,
im on PA which is still Jelly Bean isn't it?
But the radio is 0/84, is that what it should be?
Click to expand...
Click to collapse
In "About Phone" look for "Android Version" if it's below 4.4 then you are on Jelly Bean (e.g., 4.3 or 4.2). I don't use PA ROM so I don't know which version currently for PA.

taodan said:
In "About Phone" look for "Android Version" if it's below 4.4 then you are on Jelly Bean (e.g., 4.3 or 4.2). I don't use PA ROM so I don't know which version currently for PA.
Click to expand...
Click to collapse
4.3 is the one im on. Cheers
So any ideas on how to fix it?

foxguard said:
4.3 is the one im on. Cheers
So any ideas on how to fix it?
Click to expand...
Click to collapse
Have you tried to wipe cache and dalvik cache in recovery? Also did you test your phone in different area because it depends on where you are compared to the cell signal tower.

taodan said:
Have you tried to wipe cache and dalvik cache in recovery? Also did you test your phone in different area because it depends on where you are compared to the cell signal tower.
Click to expand...
Click to collapse
Have now done this and will see what happens )
Not sure I understand the second part though as im talking about my home wifi and not my 3g coverage.

foxguard said:
Have now done this and will see what happens )
Not sure I understand the second part though as im talking about my home wifi and not my 3g coverage.
Click to expand...
Click to collapse
I found this information on Google's support forum:
I can hereby confirm that flashing back the radio from M9615A-CEFWMAZM-2.0.1700.84 (default for 4.3) to M9615A-CEFWMAZM-2.0.1700.48 (default for 4.2.2), whilst keeping the rest of 4.3, did NOT fix the wifi speed and connectivity problems on my phone.
I then proceeded to downgrade completely to 4.2.2 using the Google-supplied factory images, and I'm now getting 44 Mbit/s down and 5 Mbit/s up via 802.11n, where on 4.3 with either of the two radios, I couldn't even reliably finish the test (it would stop halfway, with the download speed estimated at 7 Mbit/s). Besides that, I've now been able to update tons of apps from Play, where with 4.3 this was not possible with either of the radios.
Just in case someone finds this, the version of Android on this Nexus 4 causing endless wifi problems is:
* Android 4.3
* baseband M9615A-CEFWMAZM-2.0.1700.84
* kernel 3.4.0-perf-gf43c3d9, 2013-06-17
* build number JWR66V
The version working well is:
* Android 4.2.2
* baseband M9615A-CEFWMAZM-2.0.1700.48
* kernel 3.4.0-perf-g7ce11cd, 2013-01-29
* build number JDQ39

You should use a different radio. I'd recommend the hybrid radios 33/84. Uses .33 radio for connections such as WiFi and data, whereas .84 radio is used for calls.
Sent from my Nexus 4 using xda app-developers app

foxguard said:
Hi,
This is an odd one.
I get 12mb download speeds on my home wifi if i do a test from my laptop or girlfriends iphone. If I do the test on my Nexus i only get about 1.5mb.
If I reboot the router (Draytek) I get the full 12mb again for a few hours then it drops right back down to 1.5mb.
Now I know you are all thinking straight away its the router but I have recently changed this from a Linksy router to the draytek and had the same problem with that one, so it would appear it is my Nexus.
I am running PA with the latest Kernal for it.
Any ideas or help?
Click to expand...
Click to collapse
i had the same issue, its not the radio , there is a zip file that you can flash which was ported from an LG phone, and you Wifi will be fine for sure.
Check this link out, i know you will hit thanks after this for sure , lol
http://forum.xda-developers.com/showthread.php?t=2300873

Ajaykumar21066 said:
i had the same issue, its not the radio , there is a zip file that you can flash which was ported from an LG phone, and you Wifi will be fine for sure.
Check this link out, i know you will hit thanks after this for sure , lol
http://forum.xda-developers.com/showthread.php?t=2300873
Click to expand...
Click to collapse
Ok, have done this..... will it work!

Ajaykumar21066 said:
i had the same issue, its not the radio , there is a zip file that you can flash which was ported from an LG phone, and you Wifi will be fine for sure.
Check this link out, i know you will hit thanks after this for sure , lol
http://forum.xda-developers.com/showthread.php?t=2300873
Click to expand...
Click to collapse
Nope didn't work.

CellPhish said:
You should use a different radio. I'd recommend the hybrid radios 33/84. Uses .33 radio for connections such as WiFi and data, whereas .84 radio is used for calls.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Where do I get these from and do I just flash I'm recovery please?

foxguard said:
Where do I get these from and do I just flash I'm recovery please?
Click to expand...
Click to collapse
I am going to give you the best info you're likely going to get as I suffer the same problem.
Don't reset you're rooter switch wifi on and off on the phone as it achieves the same results.
After a while of doing this it will improve the duration it locks on to fast wifi.
Also I think relocking the bootloader helps WHY I haven't a clue.
All I know is I have the same problem with the newest and fastest wifi available in my area and after trying everything flashable, settings in wifi and even patching my wifi from roms with my wifi working the results are.
1 go back to a stock 4.3 rom.
2 try what I suggested.
Sent from my Nexus 4 using XDA Premium 4 mobile app
---------- Post added at 01:21 AM ---------- Previous post was at 01:13 AM ----------
bladebuddy said:
I am going to give you the best info you're likely going to get as I suffer the same problem.
Don't reset you're rooter switch wifi on and off on the phone as it achieves the same results.
After a while of doing this it will improve the duration it locks on to fast wifi.
Also I think relocking the bootloader helps WHY I haven't a clue.
All I know is I have the same problem with the newest and fastest wifi available in my area and after trying everything flashable, settings in wifi and even patching my wifi from roms with my wifi working the results are.
1 go back to a stock 4.3 rom.
2 try what I suggested.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
To add to the above I don't know if its 4g capabilities being added to roms as I have tried everything but thats what I am looking at now even though I have flashed multiple radios.
Sent from my Nexus 4 using XDA Premium 4 mobile app

Just asking, but are you sure you didn't confuse MByte/s with Mbit/s? (Notice the lower and upper case B )
It would make sense as 12Mbit/s are 1.5MByte/s.

Ok guys, just so you know, Radio/Baseband has nothing to do with your WiFi connectivity or the transfers speeds you are getting on WiFi. All WiFi modules, drivers are present in the Kernel and NOT the modem/baseband. Hope this gives you clarity and prevent waste of your time fiddling with the modem to solve WiFi issues!!

prembox said:
Ok guys, just so you know, Radio/Baseband has nothing to do with your WiFi connectivity or the transfers speeds you are getting on WiFi. All WiFi modules, drivers are present in the Kernel and NOT the modem/baseband. Hope this gives you clarity and prevent waste of your time fiddling with the modem to solve WiFi issues!!
Click to expand...
Click to collapse
Flashed enough radio basebands and pulled enough files from the system to know where both live. I am talking about interference something causing the wifi to drop suddenly as if the network is strangled (but its not) there's a few phones that suffer the same problems as I have read all there posts.
It's something causing it to drop turning it on and off helps for a short time in my case about 3mins tops.
It could be anything I just find it a little strange that on a custom rom any soap ,cm and custom stocks this happens but not on a Google image. So something strange is happening who knows. Just wish I did.
Sent from my Nexus 4 using XDA Premium 4 mobile app

Is Nexus 4 getting wireless speed over 2.4mb/s?
This is the maximum that I can see at transferring of files to PC on same network.
I can't have it locked over 54mbps at settings of wireless.
Sent from my NookColor using Tapatalk 4