Related
I have just spent an absolute age with HTC tech support, and the answer to the few that have been suffering with no data via wifi is................send your handset in for repair.
I honestly have completely lost the will to live, no matter what i say to try and convince them the issue is software related as i can use 2.2.1 absolutely fine, it seems to completely be over everyones head, i even spoke to a manager, who after listening to everything i said, who then spent 3 minutes in silence came back with "broken wifi module"
Arghh, they now want to book my handset in for repair, which i am reluctant to do as they quote a turn around of 20 days currently, i dont want to be without a handset that long.
all i want is gingerbread on my handset and be able to use WiFi, 3G works perfectly
Has anyone had any luck in solving this? its not a router issue, i have tried 4 different routers, its not a signal issue (i have a full signal, and its not dropping the signal), i have tried every 2.3.3 custom rom and stock rom out there and still no data Via WiFi, tried different radio's, and different kernels,
If i go back to using the Android revolution 2.3.2 beta, it works fine, so its defo since the 2.3.3 update.
any help from anyone would be so gratefully recieved i will buy you a pint!
Hi there,
Have you flashed the matching RIL's for your radios? A similar issue affected me but it was only with CM7 and ARHD. I flashed the radio in my signature (good WiFi performance for signal and battery life) and the corresponding RIL and all was working after a couple of reboots.
Hope this helps.
i have indeed pal, really really struggling with this.
A work colleague has just completed his OTA update at work, same issue,
at least i know its not just mine
im wondering if its something to do with the wifi driver in the ota,
Actually its not just the ota, tried the RUU just now, same issue
any Dev's got any clues?
Mate,
I´ve downgraded the ROM as per this thread (http://forum.xda-developers.com/showthread.php?t=905003), and now it is working perfectly. No need of gingerbread, I noticed that I do not need it anyway. Instead of that, my baby is alive and kicking againg.
Cheers.
hmoroni said:
Mate,
I´ve downgraded the ROM as per this thread (http://forum.xda-developers.com/showthread.php?t=905003), and now it is working perfectly. No need of gingerbread, I noticed that I do not need it anyway. Instead of that, my baby is alive and kicking againg.
Cheers.
Click to expand...
Click to collapse
im back on LeeDroid 2.2.1 custom rom and everything works like a charm, there isnt anything on gingerbread i need, but i want the option, i prefare the menu, but i can not be without WiFi. I have just sent HTC a humerous letter/email, i have spent hours on the phone with them today.
Sent LeeDroid a pm, see if he has any idea why this is, or if there is anyway to sort it
hopefully someone soon can come up with something, there are only a few of us with the problems, but even so HTC should release a patch or something to rectify it. A guy who has a T-Mobile branded device at work has updated fine, but myself and another colleague (both unlocked sim free devices from the carphonewarehouse) have the no data issue via wifi
i am losing the will to live
I searched and didnt find anything that seemed to be the same topic.
I updated to 4.0.4, MoDaCo custom lr11 (lMM30B) from the factory ota 4.0.2 because it sucked. Now everything seems to work great but the wifi distance seems to have dropped. In places where my iphone and this phone on .2 had 3 to 4 bars on wifi the .4 now struggles to hold 1 bar. In my room with the router about 8 feet away I get 1 or 2 bars and only get all 4 when its within 2 feet. Any free wifi spot that I have saved and used to use perfectly is pretty much gone now. I wouldn't make a big deal of it but the area I am usually in most of the day is extended for me so I don't have 3 or 4g access.
Anyone know of a fix.
ty in advance
What baseband are you using? Most if not all custom roms exclude the baseband so you will need to update that manually.
Sent from my Galaxy Nexus using Tapatalk
same problem here! my radio signal, too, sucks a lot more compared to when i was on stock.
all started happening after rooting and flashing to aokp.
salivaman said:
same problem here! my radio signal, too, sucks a lot more compared to when i was on stock.
all started happening after rooting and flashing to aokp.
Click to expand...
Click to collapse
You need to change your baseband to a later version. There are issues if you have the old one while running a rom based on 4.0.3 or above.
Sent from my Galaxy Nexus using Tapatalk
yeah i have flashed to the latest one but the problem still persists on my aokp.
strangely i decided to flash a new rom which the bugless beast and so far it's working good.
Sorry, Baseband is
l515.09 V.EK05 / L515.EK02
I see the rom update Ir12 out there so I think I will update to it. I see a change log for a previous patch that addressed the signal stregth. Will post back if any changes. Hopefully will fix it.
salivaman said:
yeah i have flashed to the latest one but the problem still persists on my aokp.
strangely i decided to flash a new rom which the bugless beast and so far it's working good.
Click to expand...
Click to collapse
next time try flashing a different Kernel if your having issues and have tried flashing a different baseband. Faux or trinity seem to be best for me using AOKP
Nothing worked...
Tried several things from roms to just the radios and I couldnt get anything to upgrade. Guess I'll wait until .5 or something.
Howdy Folks!
I recently got a SGH-I927 that is locked to AT&T.
I have read what I believe is all the relevant data about how to do the things I want, and I think I have it down, but I want to make sure I have everything exactly correct. I still have 6 days left with Virgin Mobile before I have to have all this done.
What I want to do...
Root
Back up my EFS
Update from 2.3.6 to 4.0.4
Carrier Unlock from AT&T so I can use a T-Mobile MVNO.
So my question is- is this the best order to do things in? I know I have to root before I can Unlock the phone or Backup my EFS, but I notice that there are two different methods for Rooting. I can root before I update to ICS or after. Does it make a difference? Which method is easier, which one is more reliable/safer? I also noticed that Unlocking the phone after updating to ICS requires an extra step, so that would be another factor.
Kies seems to be working, and when I plugged my phone in, it offered to update me from 2.3.6 (Baseband Ver I927UCKL1) to 4.04 (Baseband Ver I927UCLJ3), so it doesn't seem like updating will be a problem.
Are there any major issues with version two of the ICS update? I have read a lot of people that had issues with the first version of ICS that got released, and I know AT&T pulled it as an OTR update, but haven't heard a lot about version two. The people who have it are you satisfied with it? Did anyone prefer Gingerbread?
Thanks in advance for any help, and sorry if these questions have been answered already, I really did read through a LOT of information before posting here, and haven't seen these answered.
You don't need to root to unlock the phone. You just need to insert a code you buy from a seller on the internet.
I'm running the ULCHJ version of ICS and it works fine. I experienced the same GPS issue i had in GB, but the same fix worked it out and it I'm totally happy with it.
I can say, hope i won't regret, that there's nothing i should fix so far. Some minor issues were fixed as soon as i went through, I'm quite satisfied with this ROM now.
DarkBlaidd said:
Howdy Folks!
I recently got a SGH-I927 that is locked to AT&T.
I have read what I believe is all the relevant data about how to do the things I want, and I think I have it down, but I want to make sure I have everything exactly correct. I still have 6 days left with Virgin Mobile before I have to have all this done.
What I want to do...
Root
Back up my EFS
Update from 2.3.6 to 4.0.4
Carrier Unlock from AT&T so I can use a T-Mobile MVNO.
So my question is- is this the best order to do things in? I know I have to root before I can Unlock the phone or Backup my EFS, but I notice that there are two different methods for Rooting. I can root before I update to ICS or after. Does it make a difference? Which method is easier, which one is more reliable/safer? I also noticed that Unlocking the phone after updating to ICS requires an extra step, so that would be another factor.
Kies seems to be working, and when I plugged my phone in, it offered to update me from 2.3.6 (Baseband Ver I927UCKL1) to 4.04 (Baseband Ver I927UCLJ3), so it doesn't seem like updating will be a problem.
Are there any major issues with version two of the ICS update? I have read a lot of people that had issues with the first version of ICS that got released, and I know AT&T pulled it as an OTR update, but haven't heard a lot about version two. The people who have it are you satisfied with it? Did anyone prefer Gingerbread?
Thanks in advance for any help, and sorry if these questions have been answered already, I really did read through a LOT of information before posting here, and haven't seen these answered.
Click to expand...
Click to collapse
hi dark blaidd, welcome to glide!
if i were to do it over again i would backup my efs via adb on my computer before rooting or anything.
i used fastgsm to unlock my phone which is a codeless way to unlock and i suspect its how i lost my imei
certainly get a code and use dmans uclj3 deodexed rooted as the stable rom.. then you can use es explorer to modify sirgps.conf and gps.conf to get your gps working. before i switched to cm10.1 JB I was running it with no issues and instant GPS lock in all apps.
I will likely switch back as I have a new hands free stereo for my car that I would like to legally take advantage of
let us know if you run into issues you will need to do a few searches.
sbiricuda said:
You don't need to root to unlock the phone. You just need to insert a code you buy from a seller on the internet.
Click to expand...
Click to collapse
I'm a poor boy, so I am probably going to try and save a few bucks by using this method, which requires root.
I'm running the ULCHJ version of ICS and it works fine. I experienced the same GPS issue i had in GB, but the same fix worked it out and it I'm totally happy with it.
Click to expand...
Click to collapse
What was the GPS issue? Can you link to the fix please?
I can say, hope i won't regret, that there's nothing i should fix so far. Some minor issues were fixed as soon as i went through, I'm quite satisfied with this ROM now.
Click to expand...
Click to collapse
Cool, thanks for giving your opinion. How good is your battery life?
yohan4ws said:
hi dark blaidd, welcome to glide!
if i were to do it over again i would backup my efs via adb on my computer before rooting or anything.
Click to expand...
Click to collapse
Sounds like a good idea, I will do that.
i used fastgsm to unlock my phone which is a codeless way to unlock and i suspect its how i lost my imei
Click to expand...
Click to collapse
Noted, I will stay away from fastgsm. I think I am going to do this or GalaxSim Unlock.
certainly get a code and use dmans uclj3 deodexed rooted as the stable rom.. then you can use es explorer to modify sirgps.conf and gps.conf to get your gps working. before i switched to cm10.1 JB I was running it with no issues and instant GPS lock in all apps.
Click to expand...
Click to collapse
I can't believe I am about to say this, I have spent the last two years on custom ROMs, but I think I am fine with stock for now. The ROMs for the Glide look promising, but I MUST have Camera and Bluetooth, so I will probably wait until those issues get ironed out. There is also a chance that Samsung will update us to Jellybean, they just released an update for the Galaxy S2, so it's possible.
let us know if you run into issues you will need to do a few searches.
Click to expand...
Click to collapse
Thanks! I believe I have done enough research to do what I want, so hopefully I won't make any dumb mistakes.
DarkBlaidd said:
Update from 2.3.6 to 4.0.4
Click to expand...
Click to collapse
Don't bother with ICS, the official ROM has issues and we never did much dev at that level. Go to CM10.1 once you have the ICS bootloader.
Carrier Unlock from AT&T so I can use a T-Mobile MVNO.
Click to expand...
Click to collapse
About that... AT&T phones, even once unlocked, cannot use UMTS or HSPA+ on T-Mobile's network. It's a physical limitation of the radio. ONLY do this if you already KNOW you will be happy with EDGE.
DarkBlaidd said:
I can't believe I am about to say this, I have spent the last two years on custom ROMs, but I think I am fine with stock for now. The ROMs for the Glide look promising, but I MUST have Camera and Bluetooth, so I will probably wait until those issues get ironed out.
Click to expand...
Click to collapse
I'm in same boat here I guess. Just ordered a Glide, looking forward to having a physical keyboard again since my TP2 days. I was checking out the ROM options, found the link for "Stock UCLJ3 Rom" and it looks like that is the way go, other than maybe just staying stock... I need Bluetooth, Camera, GPS, and Tethering to work, so I guess I won't be messing around with anything fancy.
So don't do any OTA upgrade at all when I first get it out of the box? Just back it up, then root, and install UCLJ3 via CWM? Is this the best choice?
roothorick said:
Don't bother with ICS, the official ROM has issues and we never did much dev at that level. Go to CM10.1 once you have the ICS bootloader.
Click to expand...
Click to collapse
Doesn't CM10.1 still have issues, like with bluetooth, GPS, and camera?
idenlover said:
Doesn't CM10.1 still have issues, like with bluetooth, GPS, and camera?
Click to expand...
Click to collapse
There is not and never has been GPS problems that actually affect normal use. I don't know where people are getting that from. There's some anomalies in the data returned, but nothing that's actually used by the location API.
Bluetooth itself works, but there are some audio layer problems that interfere with headsets/earpieces and the like. (TBH our whole audio layer is a mess right now.) Stuff like OBEX and tethering should work fine.
Speaking of audio layer issues... there's still a longstanding bug where if userspace (i.e. an app; normal cell network phonecalls are fine) opens the microphone, audio output is corrupted. The biggest problem caused by this is the other person is basically unintelligible when calling in Skype. That and Bluetooth audio routing are really the only big problems we still have.
The camera was fixed months and months and months ago. I discovered the original fix even. There was a problem with audio in the video recorder that has now been solved recently.
roothorick said:
There is not and never has been GPS problems that actually affect normal use. I don't know where people are getting that from. There's some anomalies in the data returned, but nothing that's actually used by the location API.
Bluetooth itself works, but there are some audio layer problems that interfere with headsets/earpieces and the like. (TBH our whole audio layer is a mess right now.) Stuff like OBEX and tethering should work fine.
Speaking of audio layer issues... there's still a longstanding bug where if userspace (i.e. an app; normal cell network phonecalls are fine) opens the microphone, audio output is corrupted. The biggest problem caused by this is the other person is basically unintelligible when calling in Skype. That and Bluetooth audio routing are really the only big problems we still have.
The camera was fixed months and months and months ago. I discovered the original fix even. There was a problem with audio in the video recorder that has now been solved recently.
Click to expand...
Click to collapse
OK, so then just the random app microphone and bluetooth issues still remain... So you still say it's worth it? I'm leaning towards the debloated rooted stock as I'm just lazy and want everything to work.
idenlover said:
OK, so then just the random app microphone and bluetooth issues still remain... So you still say it's worth it? I'm leaning towards the debloated rooted stock as I'm just lazy and want everything to work.
Click to expand...
Click to collapse
Official ICS was something of a ****storm, as Samsung never did get it to work quite right. There was a myriad of weird keyboard issues, intermittent radio problems, and come to think of it, I think I know where the GPS thing came from... official ROMs have lethargic GPS if you're not on AT&T. I'd say 99% of power users with a Glide are on one build/variant or the other of CM10.1 because it's the most problem-free ROM that's not, ugh, Gingerbread.
The primary value of official ICS to us was the kernel sources and RIL blobs -- the last few critical bits and pieces we needed to make our own ROMs and properly connect them to all the phone hardware.
I'd say, once you have everything backed up:
Flash official ICS UCLJ3 (for the bootloader and baseband)
Flash CWM over the top of it
Use CWM to flash the current CM10.1 build and gapps. Call it good.
roothorick said:
Official ICS was something of a ****storm, as Samsung never did get it to work quite right. There was a myriad of weird keyboard issues, intermittent radio problems, and come to think of it, I think I know where the GPS thing came from... official ROMs have lethargic GPS if you're not on AT&T. I'd say 99% of power users with a Glide are on one build/variant or the other of CM10.1 because it's the most problem-free ROM that's not, ugh, Gingerbread.
The primary value of official ICS to us was the kernel sources and RIL blobs -- the last few critical bits and pieces we needed to make our own ROMs and properly connect them to all the phone hardware.
I'd say, once you have everything backed up:
Flash official ICS UCLJ3 (for the bootloader and baseband)
Flash CWM over the top of it
Use CWM to flash the current CM10.1 build and gapps. Call it good.
Click to expand...
Click to collapse
Ok great, thanks for the explanation/breakdown So if there is an OTA update that pops up right out of the box, do I do it or skip it? And I'll have to root before flashing the UCLJ3, right?
idenlover said:
Ok great, thanks for the explanation/breakdown So if there is an OTA update that pops up right out of the box, do I do it or skip it? And I'll have to root before flashing the UCLJ3, right?
Click to expand...
Click to collapse
Might as well, as if it happens to be UCLJ3, well, it just did Step 1 for you, and if not, well, it doesn't matter either way.
You don't really need root for any of this since our bootloader is unlocked OOB.
roothorick said:
Might as well, as if it happens to be UCLJ3, well, it just did Step 1 for you, and if not, well, it doesn't matter either way.
You don't really need root for any of this since our bootloader is unlocked OOB.
Click to expand...
Click to collapse
Awesome, thanks for the help!:good:
roothorick said:
About that... AT&T phones, even once unlocked, cannot use UMTS or HSPA+ on T-Mobile's network. It's a physical limitation of the radio. ONLY do this if you already KNOW you will be happy with EDGE.
Click to expand...
Click to collapse
Damn it, that really sucks. Thank you so much for letting me know that, you saved me some headaches.
Edit: I did some digging around to get a technical explanation of this issue and stumbled across some unexpectedly good news, I can use HSPA+ on T-MO, well halfway at least, I'm going to make a new post as a public service.
I posted about this briefly on the T-Mo forums, looks like I'm not the only one who is having some issues with Kitkat. Mainly, sometimes when you leave Wifi you will lose all radio signal until a reboot. Also, on Wifi Calling, usually after 20 minutes or so you can send text messages just fine but you won't receive them until you reboot.
Just want to warn anyone who is looking to update their bootloader like I did and now can't go back to the fully functional 4.3. I'm completely reliant on Wifi calling where I am so this is a bad situation.
I've also heard there are some battery drain issues in 4.4.2 with the Note 3.
no problem here if not i get better lte signal b4 i only get one 1 bar at my work now i get 3
mrej201 said:
no problem here if not i get better lte signal b4 i only get one 1 bar at my work now i get 3
Click to expand...
Click to collapse
Yeah, the signal is a little better in some areas, but I'm not sure if that's just the way the signal is displayed or if there was actually something done to improve the signal, I tend to think it's the first option.
These are mostly issues related to Wifi calling, just wanted to warn people who are reliant on it like me.
Bacardi222 said:
Yeah, the signal is a little better in some areas, but I'm not sure if that's just the way the signal is displayed or if there was actually something done to improve the signal, I tend to think it's the first option.
These are mostly issues related to Wifi calling, just wanted to warn people who are reliant on it like me.
Click to expand...
Click to collapse
Have you tried a fresh install
TWEAKED 2.0 ELEMENT V3.0 NOTE 3
Bacardi222 said:
Yeah, the signal is a little better in some areas, but I'm not sure if that's just the way the signal is displayed or if there was actually something done to improve the signal, I tend to think it's the first option.
These are mostly issues related to Wifi calling, just wanted to warn people who are reliant on it like me.
Click to expand...
Click to collapse
How did you take the update? If you're not concerned with knox flags I really suggest backup apps etc and use philz or twrp....wipe that thing till it bleeds haha...i like to follow wipes with a reboot back into revovery....(also tapping No to any requests to add root) then flash the stock deodexed or odexed if you must lol....I've not had a single hangup. ....then after loading rom set everything up and proceed to remove bloat from [system/app] AND [data/app] ....reboot....profit.
Let me add I've had my note for about 2 weeks with stock 4.3 no root nada...straight from t-mo and had about 12-15 random reboots....After update (1st took ota then said f*÷! it and rooted and slapped custom recov on him then wiped everything except external sd and flashed stock zip) Not 1 reboot ! since what...Wednesday .....wifi calling 100 %....best of luck
BACARDILIMON said:
Have you tried a fresh install
TWEAKED 2.0 ELEMENT V3.0 NOTE 3
Click to expand...
Click to collapse
louforgiveno said:
How did you take the update? If you're not concerned with knox flags I really suggest backup apps etc and use philz or twrp....wipe that thing till it bleeds haha...i like to follow wipes with a reboot back into revovery....(also tapping No to any requests to add root) then flash the stock deodexed or odexed if you must lol....I've not had a single hangup. ....then after loading rom set everything up and proceed to remove bloat from [system/app] AND [data/app] ....reboot....profit.
Let me add I've had my note for about 2 weeks with stock 4.3 no root nada...straight from t-mo and had about 12-15 random reboots....After update (1st took ota then said f*÷! it and rooted and slapped custom recov on him then wiped everything except external sd and flashed stock zip) Not 1 reboot ! since what...Wednesday .....wifi calling 100 %....best of luck
Click to expand...
Click to collapse
Yes, tried multiple fresh installs/re-downloads.
I Odin'd the 4.4.2 update, rooted, flashed philz recovery, then wiped and installed the de-odexed from that thread over in development. It isn't an issue with the roms, it's definitely the update itself, people over on the T-Mo forums are having the same issues. Hopefully it gets worked out.
Bacardi222 said:
I posted about this briefly on the T-Mo forums, looks like I'm not the only one who is having some issues with Kitkat. Mainly, sometimes when you leave Wifi you will lose all radio signal until a reboot. Also, on Wifi Calling, usually after 20 minutes or so you can send text messages just fine but you won't receive them until you reboot.
Just want to warn anyone who is looking to update their bootloader like I did and now can't go back to the fully functional 4.3. I'm completely reliant on Wifi calling where I am so this is a bad situation.
I've also heard there are some battery drain issues in 4.4.2 with the Note 3.
Click to expand...
Click to collapse
My wife and I have Note 3s, both still on 4.3, rooted only otherwise stock rom and we are having this problem. We've had our phones since launch and this problem only started happening a couple of weeks ago. I definitely do not think it's an OS update problem.
Russbad said:
My wife and I have Note 3s, both still on 4.3, rooted only otherwise stock rom and we are having this problem. We've had our phones since launch and this problem only started happening a couple of weeks ago. I definitely do not think it's an OS update problem.
Click to expand...
Click to collapse
Strange, I didn't notice any issue at all before the update. This is my second phone and both have been fine, so maybe something larger at hand here.
Russbad said:
My wife and I have Note 3s, both still on 4.3, rooted only otherwise stock rom and we are having this problem. We've had our phones since launch and this problem only started happening a couple of weeks ago. I definitely do not think it's an OS update problem.
Click to expand...
Click to collapse
It not an is update issue. This happened to a few. Don't know exactly what fix was.
TWEAKED 2.0 ELEMENT V3.0 NOTE 3
Try this
I had similar problem on 4.3.
Try what I did here and see if it fixes it?
I know it is a little different problem, but nothing wrong in trying different fixes
Good luck.
Hello all...
Has anyone else been having buffering issues at the beginning of Google Play Music streaming songs? The music will go for a second, stop, go for another couple of seconds, stop, and then play fully. This is on Normal quality and is in places where I can do a speedtest at over 10mbit/sec. Often it's 20mbit or more. It seems like this started happening when the new 3.x firmware was released. I never had buffering before.
I've tried everything from uninstalling/clearing data to clean flashing ROMs. Same thing, and it shouldn't be happening with the bandwidth I have available.
Thanks.
A
Ive noticed this as well. Have not noticed any difference in quality of music but i have noticed it start, buffer, play, buffer, play..
I also am in a strong cellular spot with LTE and often 15+mb down. So i am convinced its not a thru put issue. I have not noticed it on WiFi so ill keep a look out for that.
Alpione said:
Hello all...
Has anyone else been having buffering issues at the beginning of Google Play Music streaming songs? The music will go for a second, stop, go for another couple of seconds, stop, and then play fully. This is on Normal quality and is in places where I can do a speedtest at over 10mbit/sec. Often it's 20mbit or more. It seems like this started happening when the new 3.x firmware was released. I never had buffering before.
I've tried everything from uninstalling/clearing data to clean flashing ROMs. Same thing, and it shouldn't be happening with the bandwidth I have available.
Thanks.
A
Click to expand...
Click to collapse
I've had GPM problems as well. Sometimes what you describe, sometimes the song starts, plays a few seconds then stops completely. All on good data connections, sometimes happens on WiFi. I also have the latest FW but I flashed right after I got the phone so I have nothing to compare it to.
While we're on the subject of music, does anyone experience crackling when moving the 3.5mm jack during playback? Sometimes the crackling really bothers me when I'm walking.
No crackling that im aware of on my unit.
From past experience that crackling can be from dirty connectors or a bad connection. What your hearing is the arching or electrical components momentarily loosing then regaining contact with each other. OR if it is securely connected in its possible the connector is being stressed to much and possibly coming loose from the board.
The last alternative is your headphones were not made very well and the crackling is coming from damaged or poorly soldered connection inside the male plug.
To test this out try a different cable or different wired headphones with a different cable. IF the crackling stops its your cable and not your phone connector.
I have had these start/stop issues at the beginning of tracks using both my cellular network and Wi-Fi...very strange.
I'm also experiencing this issue. It's very distracting. ARHD 21.0 on latest firmware.
Good to hear that I'm not the only one. I did a support chat with Google Play's support techs and they couldn't figure it out. Frustrating.
I've had the issue on ARHD and Venom. I was using the default modem/radio in the new international firmware and tried changing it to the latest AT&T radio. I got significantly better speeds on the AT&T radio but the skipping problem was still there.
Weird.
A
Ok, so I finally solved this after trying a ton of things.
I've got the AT&T variant and, like many of us, had been using the international firmware and ROMs (ARHD, Venom, etc.) This Google Play buffering problem seemed to start when I upgraded to the latest 3.x firmwares. I decided to test out that theory by going back to AT&T-specific firmwares and used this thread: http://forum.xda-developers.com/att...-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
I first tried wiping everything and flashing the 3.28.1540.5 firmware and ROM, which is 4.4.4 not officially released by AT&T but apparently for the identical Dev edition. Didn't work. Buffering problem was still there.
I decided to go back to total stock and flashed the officially released AT&T 4.4.3 version - 2.22.1540.4. Eureka! Everything works great now, and LTE speeds have jumped from 10-20mbit down to 30-40. That's especially interesting because I had already tried swapping out the international modem/radio with AT&T's 1.16 version. That only got me to 20. Flashing the whole firmware and stock ROM got me to 40.
So this is a good lesson - even though the phone hardware is identical and we complain about the carriers taking forever for updates, there obviously is value in what they do to optimize these ROMs for their own network.
A
I decided to go back to total stock and flashed the officially released AT&T 4.4.3 version - 2.22.1540.4.This is still us developer build:silly:. If using the build in my thread it has been modified for ATT specifically. All firmwares in my thread are for the US Developer device, but are modified for ATT as thats my carrier.
Alpione said:
Ok, so I finally solved this after trying a ton of things.
I've got the AT&T variant and, like many of us, had been using the international firmware and ROMs (ARHD, Venom, etc.) This Google Play buffering problem seemed to start when I upgraded to the latest 3.x firmwares. I decided to test out that theory by going back to AT&T-specific firmwares and used this thread: http://forum.xda-developers.com/att...-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
I first tried wiping everything and flashing the 3.28.1540.5 firmware and ROM, which is 4.4.4 not officially released by AT&T but apparently for the identical Dev edition. Didn't work. Buffering problem was still there.
I decided to go back to total stock and flashed the officially released AT&T 4.4.3 version - 2.22.1540.4. Eureka! Everything works great now, and LTE speeds have jumped from 10-20mbit down to 30-40. That's especially interesting because I had already tried swapping out the international modem/radio with AT&T's 1.16 version. That only got me to 20. Flashing the whole firmware and stock ROM got me to 40.
So this is a good lesson - even though the phone hardware is identical and we complain about the carriers taking forever for updates, there obviously is value in what they do to optimize these ROMs for their own network.
A
Click to expand...
Click to collapse
Wonders_Never_Cease said:
I decided to go back to total stock and flashed the officially released AT&T 4.4.3 version - 2.22.1540.4.This is still us developer build:silly:. If using the build in my thread it has been modified for ATT specifically. All firmwares in my thread are for the US Developer device, but are modified for ATT as thats my carrier.
Click to expand...
Click to collapse
Ha! Too damned many versions.
Regardless, I'm good to go for now.
A