[Q] LTE issues after flashing - Thunderbolt General

Hello everyone! I was wondering if anyone has been experiencing low download/upload speeds? Just two days ago (prior to rooting my phone) I was getting awesome download and upload speeds, 10-17Mbps and 3-7Mbps respectively. Since I've rooted my phone, my speeds are way below that. I've flashed the latest radio, Any ideas or suggestions on what it could be?

When you flashed the latest radio, did you wipe cache and dalvik too?
Sent from my ThunderBolt using Tapatalk

Yes. I did a full wipe twice, wiped cache (again), wiped Dalvik, and then once my ROM is installed, I fix permissions. I don't know if that helps but I've always done that.

wseda22 said:
Hello everyone! I was wondering if anyone has been experiencing low download/upload speeds? Just two days ago (prior to rooting my phone) I was getting awesome download and upload speeds, 10-17Mbps and 3-7Mbps respectively. Since I've rooted my phone, my speeds are way below that. I've flashed the latest radio, Any ideas or suggestions on what it could be?
Click to expand...
Click to collapse
What is "way below that", you gave numbers for your original speeds

Sorry I didn't post my new numbers. Download: 1-5Mbps (sometimes 7Mbps), upload: 0.7-3Mbps. In addition, my father has the same phone, unrooted, and his speeds are where my speeds were orginally. He and I both have the same radios, so I'm not sure what it could be.

Related

[Q] New Cyanogen 7 update for Thunderbolt

Hey Guys,
So I just rooted my Thunderbolt the other day with Cyanogen 7 Mod version 7.0.0. Today a new update came out (version 7.0.1) and I was trying to figure out if I needed to wipe my data and cache in order to update to this version. Hopefully someone has the answer. I am new to android and am looking for advice. Thanks in advance!
Wipe data
Wipe cache
wipe dalvik cache in the advanced portion of CWR
then install the ROM
Do all three at least 3 times just to be sure.
Make sure your battery is fully charged.
Anytime you install a new ROM follow this. If a small modification like new market, pull down menu. just wipe cache
Hopes this helps
hackercity said:
Do all three at least 3 times just to be sure.
Hopes this helps
Click to expand...
Click to collapse
Lol, reminded me of the website is down vid....did you reboot? Yea man I rebooted three times, I always reboot three times like you told me!
-sent via 1.21 giggawatts of android.
wipe 3 times? excessive much? once is sufficient and additional wipes wont do anything more.
mbh87 said:
wipe 3 times? excessive much? once is sufficient and additional wipes wont do anything more.
Click to expand...
Click to collapse
+1 to wiping just once.
Also, OP, keep in mind CM7 for TB is pre-alpha and does have bugs. If you're looking for a daily driver, since you're new to Android, perhaps you would want to try a more stable ROM to get your feet wet, and once you get the hang of things, perhaps trying CM7 or a leaked ROM.
Good luck!
Wipe 3 times Anal retentive much? ...haha anyway
Wipes of caches sure but ....
Flashing CM7 7.0.1 over 7.0.0 there is no need for data wipe .
If an issue does arise you can wipe it after but why reinstall all your apps really?
This has been my daily driver
No 4G here yet & I use do not use wifi regularly.
are there still issues with CM7 not being able to use phone information (EPST) or ##778# to manage / edit modem settings?
i think i'm stuck on 3g...
there's an app called network that lets you pick which radio you want to use..I used it to switch from 3g/4g to 3g only...it has 4g only.
I always wipe 2-3 times ever since the OG Droid days. It takes you 30 more seconds, whats the big deal. If it somehow bricks because the wipe wasn't successful or you have to reflash a rom it will take you another 10-20 minutes.
Better be safe than sorry.
I've followed the steps outlined in the following thread but i can't get data to stick. It frequently drops even the 3G connectivity.
Also noticed that bluetooth isn't workinig.
http://forum.xda-developers.com/showpost.php?p=13881413&postcount=2616
Any tips on what I can try to get data to stick.

VRBLK1 Full Wipe vs No Wipe in Odin

Since the New TouchWiz JellyBean leak dropped, we quickly found out that the Rootdebug method no longer works for rooting...Not a big deal as developers rolled back to our grass roots and used the original Odin method to achieve root. My only issue is with the suggestion to flash a modified No Wipe image of the stock K1 leak...Im not sure if I agree with this. I have dirty flashed with Odin in the past and things appeared to work fine on ICS, but stepping up to JellyBean seems to be different!
Point is since the leak has dropped many folks complain of media server causing battery drain, I was one of them. So I decided to odin back to stock using the rooted FULL WIPE VRBLK1 version by Mr. Robinson...and I have had substantially less battery drain!!! Battery life is currently at 15hrs with 65% left...2 hrs screen on.
I would suggest to anybody that flashed a no wipe image in odin and is having issues with media server draining the battery, and/or any other issues appear, try flashing the FULL WIPE version! As others have said, I believe the problem is a corrupted file on the internal sd causing the issue. Also a few other small issues I was having appears to be fixed, such as touch screen being unresponsive at times...also gps seems to lock faster. Anybody else noticing the same??
This is interesting. I did the no wipe to the newest leak and I felt it was horrible. Battery for me was not as good and the phone was always hotter. So I went back to J1 leak. If I get time I might try the full wipe version of the newest leak. Try the theory out.
As an addition, my CPU was always acting crazy. Random low frequency locks (would not ramp up). Sometimes it would stay high, probably the cause of the warm phone. And weird battery drain from the system I just could not explain.
Thanks for this and as I said I'll try fresh after the weekend. Holiday weekend is my family time.
Sent from my SCH-I535 using Tapatalk 2
I know this is somewhat off topic so I apologize for derailing....are you guys having any issues with NFC on AOSP ROMs after flashing the leak via Odin?
Sent from my SCH-I535 using Tapatalk 2
Marcismo55 said:
I know this is somewhat off topic so I apologize for derailing....are you guys having any issues with NFC on AOSP ROMs after flashing the leak via Odin?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I've only flashed an AOSP once. That was the last time. Too choppy, and i like my TW features. So, to answer your question, I don't know.
Sent from my SCH-I535 using Tapatalk 2
I did full wipe and everything is great except gps.
I did a no wipe version moving from J1 to K1, what I saw was the RAM footprint increase by 50%...
I did the full and footprint went back to what I recognized on J1...Barry seems as good or better than J1 too
Sent from my SCH-I535 using xda app-developers app
I did Robinson's no error via Odin and don't have any apparent issues. what should I be looking for?
lexluthor said:
I did Robinson's no error via Odin and don't have any apparent issues. what should I be looking for?
Click to expand...
Click to collapse
Did you use the full wipe or no wipe version in odin? Thats the point of this thread...no wipe seems to be causing a foul odor with media drain and random issues for folks. The full wipe leaves you so fresh and so clean!!
Sorry for sounding like a noob, but what exactly is media drain? Battery use by "media server?"
Sent from my Galaxy S III using Tapatalk 2
US Marine said:
Sorry for sounding like a noob, but what exactly is media drain? Battery use by "media server?"
Sent from my Galaxy S III using Tapatalk 2
Click to expand...
Click to collapse
yes
Hmm...I did the no-wipe flash, and I haven't had any issues whatsoever.
Sent from my Galaxy S III using Tapatalk 2
US Marine said:
Hmm...I did the no-wipe flash, and I haven't had any issues whatsoever.
Sent from my Galaxy S III using Tapatalk 2
Click to expand...
Click to collapse
Thats good! Im not saying everybody is going to have issues with the no wipe version...most likely its going to be folks that have flashed a bunch of roms and accumulated alot of folders/files on the internal SD. The point is if you are one of the unfortunate folks thats having issues, try the FULL WIPE version.
droidstyle said:
Thats good! Im not saying everybody is going to have issues with the no wipe version...most likely its going to be folks that have flashed a bunch of roms and accumulated alot of folders/files on the internal SD. The point is if you are one of the unfortunate folks thats having issues, try the FULL WIPE version.
Click to expand...
Click to collapse
Yeah, I flashed from bone stock the day I got the phone.
Sent from my Galaxy S III using Tapatalk 2
My phone seems a little laggy which I did not experience on the first leak. I don't not have the typical problems people have with flashing the no wipe version... That's what I flashed. Thinking of trying a factory reset but this thread makes me wonder if flashing the wipe version might be better? What's the difference though? Both wipe and no wipe are from the same file, right?
Sent from my SCH-I535 using xda premium
Question, I did the no wipe version on odin from the stock samsung s3, and now my RAM usage is almost always close to 1 gb. Before on ICS it was like 600 or 700 mb. Is this normal for jelly bean?
Ryno77 said:
My phone seems a little laggy which I did not experience on the first leak. I don't not have the typical problems people have with flashing the no wipe version... That's what I flashed. Thinking of trying a factory reset but this thread makes me wonder if flashing the wipe version might be better? What's the difference though? Both wipe and no wipe are from the same file, right?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Full Wipe will repartition the Internal SD and wipe rom data...this will get rid of any corrupted files that reside on the internal. Its the same principal as reformatting and installing windows. Dirty Flashing writes your data over the top of data and nothing else in the internal sd is touched...not saying dirty flashing is bad, I do it alot, but when wierd issues arise, 90% of the time a Full Wipe with Odin fixes things.
VigilanteM2 said:
Question, I did the no wipe version on odin from the stock samsung s3, and now my RAM usage is almost always close to 1 gb. Before on ICS it was like 600 or 700 mb. Is this normal for jelly bean?
Click to expand...
Click to collapse
I believe touchwiz jellybean uses more ram.
Is the full wipe version included everything like the original Verizon release version? (radio, rom, kernel, bootloader etc...)Thanks.
buhohitr said:
Is the full wipe version included everything like the original Verizon release version? (radio, rom, kernel, bootloader etc...)Thanks.
Click to expand...
Click to collapse
Yep
I have just realized that the hotspot is broken. Every time I try to turn it on, it force closes Settings. Anyone else having this problem?
EDIT: So I downloaded a hotspot toggle widget, and it works fine. I only have a problem if I try to enable hotspot via Settings. Interesting.
Sent from my Galaxy S III using Tapatalk 2

Skyrocket on Tmobile, echo's during calls

Hello,
We flashed our Skyrocket with the "CvD-Nibbles-v1.6" ROM (4.1.2 I believe) along with the "Blaze_4G_LB7_ICS_Radio_MOD" a couple days ago. So far everything is working fantastic, data speeds are good... with the exception of call quality.
Anyone who calls the phone hears themselves echo back about 1 second later. The echo issue fades in and out but it's hard to tell if it's tied to a good or poor call connection.
Anyone have any thoughts or suggestions? Maybe a different radio? The process we used was:
Unlocked phone previously using the touch codes and an older modem.
Flashed the new ROM.
Flashed the modem.
Thanks!
Havevyoubtriwd reflashing just the radio since you noticed issue wipe dalvik cache
crashpsycho said:
Havevyoubtriwd reflashing just the radio since you noticed issue wipe dalvik cache
Click to expand...
Click to collapse
I haven't but I can give that a try.
BS wiping dalvik , it has nothing to do with echo .... it's your network OP
Here flash your problems away:
http://d-h.st/zrg

[Q] Problems flashing an already rooted 4.4.3 over 4.4.2

I flashed the ROM and baseband per instructions in this thread: http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
I had 4.4.2 and he said it had to be stock, and it was with the exception of potentially having some system files modified due to other apps, like Android Tuner. I wiped Dalvik cache and regular cache, installed both files as mentioned through TWRP, and yet upon starting I get a notice to update to 4.4.3 despite already being on 4.4.3, and it can't connect to T-Mobile which is my service provider. Am I doing something wrong here? I figured by "stock" ROM he meant the original and not CyanogenMod or anything like it. Was that supposed to mean stock Android with zero modifications to the system files?
I didn't want to do a factory reset and have to redo all my data and applications, but if I must then I will.
There is a rough thunderstorm going on so maybe that knocked out T-Mobile service, but I find it rather coincidental.
]UPDATE] Turns out that the storm coincidentally disabled the towers at around the exact time I updated my phone. The phone was flashed fine. T-Mobile is the problem. Thanks for the help!
It doesn't matter what ROM you're coming from but if it's not stock you need to wipe. But whatever mods you have on stock is irrelevant.
If you're having issues connecting,, wiping cache is often the cause. Check. Our imei etc is correct. Maybe fastboot flash a stock cache image or Nandroid restore
Sent from my Nexus 5 using Tapatalk
rootSU said:
It doesn't matter what ROM you're coming from but if it's not stock you need to wipe. But whatever mods you have on stock is irrelevant.
If you're having issues connecting,, wiping cache is often the cause. Check. Our imei etc is correct. Maybe fastboot flash a stock cache image or Nandroid restore
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It was the original stock that shipped with the phone, with potentially some files modified from an application. Strangely when searching for networks to connect to, Sprint and AT&T show up as normal but not T-Mobile, although their APN's show up as if I am connected but can't get access to their service.
The IMEI within the phone appears to match the worn off label. Either way, I cleared the Dalvik and regular cache again so I'll see what happens when the phone finishes booting.
Surely it's booted by now?
Sent from my Nexus 5 using Tapatalk
rootSU said:
Surely it's booted by now?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It finished updating the apps and didn't get a connection, however when I traveled outside of my home zone to work, after I reach the spot outside of the city at which there is no LTE support and it drops to EDGE the connection picked up and remained. After I returned from work and got back in the city near my home where it switches back to LTE the connection dropped again and remained that way even after wiping the caches again.
Does this still sound like a software problem or maybe it's on T-Mobile's end?
Fixed
Turns out that the storm coincidentally disabled the towers at around the exact time I updated my phone. The phone was flashed fine. T-Mobile is the problem. Thanks for the help!

modem issue

Hey guys, im having a weird issue... phone has worked fine for the past few weeks, all of a sudden I lost connectivity to data. Could make calls and text just fine. I was on NK4 modem / rom stock. I updated the modem to the NKD modem, and regained data connectivity but lost phone calls and sms. I did a full restore to NE5 (full tarball) and regained everything! Phone updated itself to NK4 and i lost data again.
Any idea on how to fix this issue? Or what could be causing it? Thanks in advance guys
Update: Im still on NK4, still have no data. HOWEVER, Data does work if I am roaming.
beffjall said:
Update: Im still on NK4, still have no data. HOWEVER, Data does work if I am roaming.
Click to expand...
Click to collapse
I have the exact same issue... no data except when roaming...
I contacted Sprint, was bumped up to level 2 support and they couldn't troubleshoot it, at all. They had me do all of the usual (reboot, battery pull, factory reset, blah, blah, blah).
I've flashed back to stock in Odin after wiping with still no luck.
This is getting very aggravating. Any help would be appreciated.
Your issue probably lies in this post here https://community.sprint.com/baw/mo...sprint.com/baw/api/core/v2/discussions/183846 as numerous others are experiencing this aswell and Sprint is saying that it will be fixed when Lollipop is launched on the 26th of January
Try odining NE5 modem. Other is going back to NE5 and install a custom recovery and the phone won't be able to take the OTA to NK4.
Sent from my SM-G900P

Categories

Resources