I've done multiple searches over the last week and found this to be a common problem with not specifically the LTE but others (4g) and desire as well. It appears that most assume it is something to do with not upgrading firmware or not flashing properly but I can assure you that mine didn't start acting up until I flashed new radio, I then went to the old, tried different roms etc...it appears that there is NOTHING specific that can be applied to this problem as THE cause. That being said, if anyone, on this specific phone is having the same problems, I think it would be helpful if we started a post of our setups to see if maybe we can find the culprit as this is annoying the hell out of me...any takers?
My current setup :
S-off Lazy Panda
Hboot 1.12.1111
Radio: 1.12.11.09
Kernel: 3.0.8-01680-gb6402b4 [email protected]#1
Build: 2.13.651.1 CL99866 release-keys
Rom: Meanrom 4.2
PRI: 2.45_003
PRL: 25006
I see a lot of frustration through numerous threads but no solid answers, for some it was on stock rom first day out of the box, for me it was a month later after several flashes...hopefully we can address this by comparing setups specific to the LTE, I'm willing to give it a try. Or if someone has found the answer...please feel free to share, thanks
Did it start about the time you maybe put a case on the phone?
cmdauria said:
Did it start about the time you maybe put a case on the phone?
Click to expand...
Click to collapse
saw that answer too...have had the case since the day I bought the phone...there is something wrong...hardware, software, not sure...but it has nothing to do with the case, have seen those answers too, thanks for the input...looking for setups that are working and those that aren't...case has been known to hold the power button etc... i'm looking for answers with hardware or software, but please everyone check the obvious
What other roms have you tried running? Mean Rom has a lot of mods and such, u tried something a little closer to stock? Do u dirty flash or do full wipes?
Have pretty much the same stats as u, S-off, newest radios/etc., I'm on stock w/goodies though. No consistently irritating reboots for me.
This happens to me sometimes. The only thing that is common when it locks up or reboots is when I am at the exact same place.
I work about a half mile outside of downtown Raleigh and it seems there is a Sprint dead spot there. Not to mention the roaming warnings.
Just about every call drops, easily 90% the time and rarely get more than 1x data connection. Unfortunately the WiFi there is broken right now too.
I'm thinking the phone is trying too hard to connect and then just starts re booting. Yesterday in my pocket it felt like it was making toast and was completely locked up. Took me ten minutes to get it to re boot.
Last week I got 6 lockup and re boots in two hours.
Sprint in a down town area fails pretty hard here.
Sent from my EVO using xda app-developers app
jhawk1302 said:
I've done multiple searches over the last week and found this to be a common problem with not specifically the LTE but others (4g) and desire as well. It appears that most assume it is something to do with not upgrading firmware or not flashing properly but I can assure you that mine didn't start acting up until I flashed new radio, I then went to the old, tried different roms etc...it appears that there is NOTHING specific that can be applied to this problem as THE cause. That being said, if anyone, on this specific phone is having the same problems, I think it would be helpful if we started a post of our setups to see if maybe we can find the culprit as this is annoying the hell out of me...any takers?
My current setup :
S-off Lazy Panda
Radio: 1.12.11.09
Kernel: 3.0.8-01680-gb6402b4 [email protected]#1
Build: 2.13.651.1 CL99866 release-keys
Rom: Meanrom 4.2
PRI: 2.45_003
PRL: 25006
I see a lot of frustration through numerous threads but no solid answers, for some it was on stock rom first day out of the box, for me it was a month later after several flashes...hopefully we can address this by comparing setups specific to the LTE, I'm willing to give it a try. Or if someone has found the answer...please feel free to share, thanks
Click to expand...
Click to collapse
I upgrade using the OTA in MR never had any reboot problems
jhawk1302 said:
I've done multiple searches over the last week and found this to be a common problem with not specifically the LTE but others (4g) and desire as well. It appears that most assume it is something to do with not upgrading firmware or not flashing properly but I can assure you that mine didn't start acting up until I flashed new radio, I then went to the old, tried different roms etc...it appears that there is NOTHING specific that can be applied to this problem as THE cause. That being said, if anyone, on this specific phone is having the same problems, I think it would be helpful if we started a post of our setups to see if maybe we can find the culprit as this is annoying the hell out of me...any takers?
My current setup :
S-off Lazy Panda
Radio: 1.12.11.09
Kernel: 3.0.8-01680-gb6402b4 [email protected]#1
Build: 2.13.651.1 CL99866 release-keys
Rom: Meanrom 4.2
PRI: 2.45_003
PRL: 25006
I see a lot of frustration through numerous threads but no solid answers, for some it was on stock rom first day out of the box, for me it was a month later after several flashes...hopefully we can address this by comparing setups specific to the LTE, I'm willing to give it a try. Or if someone has found the answer...please feel free to share, thanks
Click to expand...
Click to collapse
This happens at least once a day for me. The phone isn't in a case. It'll just be sitting there with the screen off and all of the sudden the HTC boot screen shows up. I got the phone on day 1 but it just started happening about 3 weeks ago. I thought it was an app that was updated so I removed the ones that were updated last but it still happens. I'm running stock, non-rooted with the following:
Software: 2.13.651.1 710RD
Radio: 1.12.11.0809
Hboot: 1.19.0000
Kernel: 3.0.8-01680-gb6402b4 [email protected] #1
PRI: 2.45_003
PRL: 25006
You find it in the bootloader
Sent from my EVO using xda premium
Found it, thanks.
Anthonicia said:
What other roms have you tried running? Mean Rom has a lot of mods and such, u tried something a little closer to stock? Do u dirty flash or do full wipes?
Have pretty much the same stats as u, S-off, newest radios/etc., I'm on stock w/goodies though. No consistently irritating reboots for me.
Click to expand...
Click to collapse
Thanks but was on his rom too, have tried several, doesn't appear to be a rom issue, something to do with the last update, rolled that back too and still having the same problem so put it back to newest firmware etc...
Just checked my Hboot as well forgot to add that
1.12.1111
Related
So I have gotten a 3d 2 weeks ago as a replacement through asurion for my broken evo 4g and like most people on xda it is only natural to root it and slap on a rom the second you get your hands on it. I checked the hboot and to my hearts content it was 1.4, and easy as cake to root since I was coming from evo 4g. The dilemma is that I have tried several roms and everyone I have loaded would give me random reboots and eventually it would just keep rebooting as soon it loads to the home screen. Realizing maybe if I just loaded it back to stock it would help. The random reboots have cut down but I still get it and it's really frustrating. I have checked the battery and it is not loose, and at this point I don't know what to do. I realize that if I go to the sprint store I have to be able to show them the problem. I am also worried that they will update my hboot to 1.5 and claim that I didn't update system software and just send me on my way. Anyone experiencing the same symptoms as mine? Should I just bring it in to sprint to see if I can get a new one?
Thank you
Sent from my PG86100 using Tapatalk
They will update it I suggest you use a format all zip and flash a haus stock rooted ROM or run a ruu hour that works the got me that way updated my phone cause it was over heating
Sent from my PG86100 using Tapatalk
Without more information it would be hard to diagnose it without playing around with the device. It also sounds like it could be the kernel, or overclock settings causing instability because of the voltage either being too low, too high, or heat related. Do you have a custom kernel? If you are, is the device also being overclocked?
The first thing I would do is stop overclocking if you do have a custom kernel. If that doesn't fix it, change the kernel. Remember, some ROMs install their own kernel and you may not even be aware of that. While our devices run the same hardware design there are two possible differences between our device compared to another's. That would be flaws and differences caused by the manufacturing process, and different revision numbers. So while one device runs kernel A @ frequency B very well, another device may have problems and run kernel X @ Y frequency better.
So that could be the issue, and using those diagnostic steps you could easily determine that is the issue, or not.
Yeah I loaded the RUU on it and turned S-off back on. Just sucks because when it doesn't random reboot or bootloop it works great.
Sad Panda said:
Without more information it would be hard to diagnose it without playing around with the device. It also sounds like it could be the kernel, or overclock settings causing instability because of the voltage either being too low, too high, or heat related. Do you have a custom kernel? If you are, is the device also being overclocked?
The first thing I would do is stop overclocking if you do have a custom kernel. If that doesn't fix it, change the kernel. Remember, some ROMs install their own kernel and you may not even be aware of that. While our devices run the same hardware design there are two possible differences between our device compared to another's. That would be flaws and differences caused by the manufacturing process, and different revision numbers. So while one device runs kernel A @ frequency B very well, another device may have problems and run kernel X @ Y frequency better.
So that could be the issue, and using those diagnostic steps you could easily determine that is the issue, or not.
Click to expand...
Click to collapse
I am currently running everything stock, reverted back with RUU and turned back S-on, and it still does it, although less frequently. Before I reverted back to stock, I did use android revolutionary 1.1.1 and on boot up it would run unstable. I then applied his stock clock zip, and it seemed to allleviate the problem at first but would again random reboot. After decided to try InfectedRom which worked great but after a day it would just reboot and eventually just bootloop. Unlucky with both decided to try MIUI and ran great for a few days and kept it on the stock kernel, but again the issues have returned. I have properly wiped the phone each time before applying any ROMs and followed the directions with everyone of them. Before trying another new ROMs I would also battery pull each time it bootlooped to see if it was just a fluke, but it would always come back. I am interested in to see what revision it is, how would I check that?
Thanks again for all the advice!
Is your battery loose?
I thought I had this problem at first too but I just popped a business card behind the battery and Viola no random reboots
Sent from my PG86100 using xda premium
bakarus said:
I am currently running everything stock, reverted back with RUU and turned back S-on, and it still does it, although less frequently. Before I reverted back to stock, I did use android revolutionary 1.1.1 and on boot up it would run unstable. I then applied his stock clock zip, and it seemed to allleviate the problem at first but would again random reboot. After decided to try InfectedRom which worked great but after a day it would just reboot and eventually just bootloop. Unlucky with both decided to try MIUI and ran great for a few days and kept it on the stock kernel, but again the issues have returned. I have properly wiped the phone each time before applying any ROMs and followed the directions with everyone of them. Before trying another new ROMs I would also battery pull each time it bootlooped to see if it was just a fluke, but it would always come back. I am interested in to see what revision it is, how would I check that?
Thanks again for all the advice!
Click to expand...
Click to collapse
Not a problem at all, that is what the community is all about. Free exchange of information, open source advancement of the platform and technology. Everyone gives a little, and takes a little.
I know there is a dialer code that works to give you that information without the need to install any application, or the need for root access, but after lots of research I was unable to find which one would give that info. However, there is a very useful app that you might want to have anyway. It is called "elixir 2", available on the market for free. Once installed, information > click"processor" > more information > processor: (mine says: ....rev. 2 (v71))
Let us know what yours says [for curiosity sake] please
Quick note, if you replaced the phone through asurion and try to replace it doesn't sprint, don't they refer you back to asurion?
Sent from my PG86100 using xda premium
I would take it to see and request them not to update it they wont ask why not don't worry...
Sent from my PG86100 using XDA App
kpsingh said:
I would take it to see and request them not to update it they wont ask why not don't worry...
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I requested then not to and they still did the update
Sent from my PG86100 using Tapatalk
So just an update, I finally decided to bring it in store today with it rooted and s-off. I was just so sick and tired of it randomly rebooting I just walked into the Sprint store. Technician brought it in, updated the hboot 1.5 =*(. I checked bootloader, and of course I see the locked in capital letters, but I am still s-off. Does that mean I can still load TWRP and root it? Or do I have to follow the HTC method to root it? Thanks for all the help guys!
If it still says s-off, i believe you are good! but that sounds odd, because otherwise we should all be able to update are hboot after rooting? If anyone knows about this...but anyway...
It was not the hboot upgrade but the firmware upgrade that you needed. You did not have to take it to sprint to do that, they have the firmware update without hboot flooting around the dev threads. 2.3.4 and above roms require the new firmware or you'll get the problems you had. No that you have the firmware a lot of the more cutting edge roms still get reboots with most advanced kernels, you have to watch your rom kernel combo, or stick with the stock kernel.
As for flashing, if you really are s-off still, then you can flash anything you want just like on the ol 4g Let us know. Lucky bastard, have fun
[edit] Found this a few threads down:
"I did what you did, had 1.40 and flashed the wrong update, got 1.50 LOCKED with S-off. You can still flash ROMs and Kernels with no issues. I just had to reload TWRP recovery. Then I flashed the 1.40 Bootloader and all was well.
You can grab 1.40 and flash from here: http://forum.xda-developers.com/show...eng+bootloader
***To others reading this...do not flash this, unless you are S-OFF with 1.50 hboot***
You do not need to UNLOCK using the htcdev method. Just flash the 1.40 hboot and you will be fine."
So reinstall twrp, flash 1.40, and have 1.40 s-off and flash the good way
Yep just flashed old hboot 1.3 and merrily rooted, so far so good running cleanrom 2.9 and taking sad panda's advice trying to figure out if it's app related. I am suspecting that it is groove ip running in the background. So far just installed cleanrom and added tapatalk and SwiftKey
Sent from my PG86100 using Tapatalk
Hey guys,
I've been working all night to try and fix an issue I had with Cyanogen Mod. I couldn't get the GPS to work with the radio I had. So I tried flashing MR3 and I still had no GPS but had 3G / 4G / WiFi connectivity. Going back to MR2 restored GPS but I couldn't maintain data and only had 1X / WiFi.
I've messed with countless radio updates and ROMs trying to get this running again. Going to post my phone's stats:
ROM Current: BAMF Forever 1.0.5
Android Version: 2.3.4
HTC Sense Version: 3.0
Software Number: 2.11.605.0
Kernel: 2.6.35.10-ge8d3693 [email protected]
Baseband version: 1.39.00.0627r, 0.01.69.0625r
I need you guys to link me to a ROM, the more light weight the better, that has 3G / 4G, GPS, and WiFi (with tethering). That's all I require =)
If I need a specific radio, a link to that would be great. Thanks a lot.
It's not the ROM...
VZW's LTE is spotty in and out in some areas. I noticed mine first thing this morning...
There are other threads on other forums about it.
http://www.engadget.com/2011/12/21/psa-verizon-users-reporting-data-outages-across-the-us/
I laugh at how they state that 3G is working fine, while LTE isnt.
I can hardly even get 1x again.
Word is if you make a phone call you can get 3g back afterwards. Worked on the wife's bolt. Worth a shot at least
Sent from my DROID X2 using XDA App
I have 3G just fine here. I don't get 4G service at this location so I force it to "CDMA Auto (PRL)" anyway.
dajogejr said:
It's not the ROM...
VZW's LTE is spotty in and out in some areas. I noticed mine first thing this morning...
There are other threads on other forums about it.
Click to expand...
Click to collapse
I think you're right unfortunately. I wait 3 months to try and fix my GPS and the one night I try it, Verizon's entire data network is taking a crap.
I just assumed that the 1X was a radio issue. I now have 4G connectivity but it's definitely slower than it should be. About 1.4Mbps. My buddy right next to me clocked 10.4Mbps on his brand new Nexus...
I'd still love to get a recommendation on a ROM and Radio version to run. I hate this BAMF ROM.
Different ROMs and different radios will have minimal impact on 4g speeds, if that's your reason for wanting something different.
Sent from my ADR6400L using XDA App
LTE came back up in SE Michigan about 2 hours or so ago.
Upon reading the OP's next post, I tested my speed via the SpeakEasy Website's speed test, as I always do.
I don't know whether to **** or go blind, but inside my office just now I hit 22MB down and 4.5 up with 2 bars (out of 4)...I've never gotten more than 12 inside the office down...
Could be that no one is on it...could be a fluke, etc.
BAMF makes quality ROMs. I would bet it's not the ROM or the radio.
I've been using the latest radio leak found here in the developer thread.
I'm sure you already know this...but it's flashed in Bootloader, not recovery.
I'm almost 100% certain it's not the ROM...unless you got a bad download or something.
That being said...you are a few releases behind on their ROM. They are up to 1.10 Final now.
Good thing is there are a ton out there, it's what's best for you...not necessarily what we think.
dajogejr said:
I've been using the latest radio leak found here in the developer thread.
Click to expand...
Click to collapse
Thanks I'll try to locate this.
dajogejr said:
I'm almost 100% certain it's not the ROM...unless you got a bad download or something.
Click to expand...
Click to collapse
I agree. I always assumed it was the radio version I was running. I want a new ROM because I hate Sense and the stock look / feel.
dajogejr said:
That being said...you are a few releases behind on their ROM. They are up to 1.10 Final now.
Click to expand...
Click to collapse
Interesting. I'll check it out.
dajogejr said:
Good thing is there are a ton out there, it's what's best for you...not necessarily what we think.
Click to expand...
Click to collapse
You're right. My problem is there's too many and I'm tired of looking haha. I just wanted to flash a known good ROM and radio and get this over with. Tired of tampering with my phone.
New update:
I just flashed MIUI from:
http://forum.xda-developers.com/showthread.php?t=1172235
and the MR3 radio from:
http://www.thunderboltforums.com/fo...151-rs-approved-guide-thunderbolt-radios.html
It's clear from the screenshot provided on the MIUI thread that the dev is using the MR3 radio which is why I chose to flash that.
But now my GPS doesn't work? Holy crap this is getting so annoying. Either my GPS works or my 4G works, I can't have both -_-
I'm trying to get my post count up without spamming the boards so I can post in the development section ;x
EDIT: Just found this link:
http://forum.xda-developers.com/showpost.php?p=20312888&postcount=1141
Anyone know if it's true?
Are you sure your data/gps is not a phone issue?
Believe it or not I know a few people that replaced their battery door and data/gps was fixed. Antennas are on the door...
In regards to your question about that link, it may work but remember some solutions work for some and not for others. Only real way to know is to try it...
Jrocker23 said:
Are you sure your data/gps is not a phone issue?
Believe it or not I know a few people that replaced their battery door and data/gps was fixed. Antennas are on the door...
In regards to your question about that link, it may work but remember some solutions work for some and not for others. Only real way to know is to try it...
Click to expand...
Click to collapse
Holy crap this might be the problem. I just installed a longer life battery that has a new back cover for the phone. I'm going to go back to stock and see what happens.
Thanks for this recommendation!
.... will not be anything that is resolved here. It is a problem with the firmware for ICS.
I was talking to somebody at sprint today while I was there and showing them my device and asking if there will be any issues caused by having a virgin mobile ROM on the device. The lady explained to me that they are exactly the same, get the same reception, same update packages, and work on the same network, etc., etc.... All of this was known to me to some extent, but wanted to hear it from somebody at the company... and told me that the only problem they are having is with ICS in general is that there have been data/radio issues with the Galaxy Nexus line as well ever since it released on their network a few weeks ago.
Furthermore, she explained that this was a known bug/issue and that she knew for a fact that an update would be coming with a fix and that it was being worked on right now.
The reason I wanted to share this was because I have seen a lot of misinformation floating around about 1.) having a virgin mobile ROM on your device and 2.) virgin mobile ROM causing data issues - which is not the cause of the issue as I mentioned just now.
Just want you all to be aware of this in case you were thinking having this software and firmware on your device would cause any issues with your billing, your contract, etc. Simply put - it will not. Virgin mobile is owned by sprint, they run on the same towers, same network, and info of accounts is stored in the same place. You could literally walk into a sprint store to pay your bill for your virgin mobile account.
All is well. All is safe. An update will come to fix the data issues, keep your eyes peeled for it folks. We are not given source code for radios, etc., so unfortunately that needs to be fixed on the carrier/manufacturer end - and as I said, it will be fixed and they are working on it. Sit tight.
Hope this cleared up any misconception floating around.
So, you don't really know how to fix it then? Forgive me for being a little confused, but your title is slightly misleading.
Oh man, you have no idea how much I was freaking out about the billing. Thanks man. (Y)
xHausx said:
So, you're don't really know how to fix it then? Forgive me for being a little confused, but you say there is a problem with the firmware and then say that there is nothing wrong with it?
Click to expand...
Click to collapse
yeah, i can see the confusion there....
re-worded, i would say it appeared to me that people thought there were data issues because of being on a virgin mobile ROM. The point I am trying to express is that the problem is the firmware, not because the ROM is for the virgin mobile 3D - if this same firmware was released for "official sprint RUU" where your banner said "sprint" they would still be having the same issues. Ex.: the lady at sprint said the galaxy nexus was having the same issue.
If that makes sense.
If not, not sure how else I can explain it.
It seemed people were crediting the problem to the fact that there device is attached to virgin mobile - this is not the case.
EDIT*** lol, nice ninja edit haus - you gotta be quicker than that roffle
xHausx said:
So, you don't really know how to fix it then? Forgive me for being a little confused, but your title is slightly misleading.
Click to expand...
Click to collapse
I thought it was the ROM side that is giving the PRL/Data roaming and all the other network problems. Not the firmware. I say this because people have posted that they flashed the firmware, flashed the VM ICS ROM. Then went back to a GB ROM (MeanROM, MIUI, etc) and they had everything working, even though they were on the leaked firmware. But if you flashed that firmware, chad and another dev found a fix, they are going to release it sometime soon.
thread: http://forum.xda-developers.com/showthread.php?t=1638225&page=30
Punk9 said:
I thought it was the ROM side that is giving the PRL/Data roaming and all the other network problems. Not the firmware. I say this because people have posted that they flashed the firmware, flashed the VM ICS ROM. Then went back to a GB ROM (MeanROM, MIUI, etc) and they had everything working, even though they were on the leaked firmware. But if you flashed that firmware, chad and another dev found a fix, they are going to release it sometime soon.
thread: http://forum.xda-developers.com/showthread.php?t=1638225&page=30
Click to expand...
Click to collapse
after half a day of having flashing back they determined the problem to be gone??
......
the issues being caused by the firmware are not constant, and apparently are rather random from what I have read. a perfect example is my own device... no issues with new firmware until today (day 3) of having it, even tho many people reported issues after just a couple of hours.
I'll talk with chad and see what he is cooking up... I havent talked to him a whole lot this weekend.
sent from ICEvo
I've been saying that the roaming problem (if it truly exists outside of people's self affirming observations) only exists on this ROM due to ICS and the lack of roaming options on the rom itself. The radios do nothing to mess up roaming. This is all due to it being a TEST rom that we flashed. It's absurd to think that there is a perfectly functional rom sitting around with no bugs if the only leak we can get is a Virgin Mobile version. We have a beta rom and beta radios, and we should realize that's what we signed up for when we flashed it in the first place.
retnuh730 said:
I've been saying that the roaming problem (if it truly exists outside of people's self affirming observations) only exists on this ROM due to ICS and the lack of roaming options on the rom itself. The radios do nothing to mess up roaming. This is all due to it being a TEST rom that we flashed. It's absurd to think that there is a perfectly functional rom sitting around with no bugs if the only leak we can get is a Virgin Mobile version. We have a beta rom and beta radios, and we should realize that's what we signed up for when we flashed it in the first place.
Click to expand...
Click to collapse
this is true... but again, what is your explanation of the galaxy nexus having the same issue, and the fact that a sprint rep was entirely aware of the issue and that is was being worked on and would come in an update?
and surprise, but any new technology is "beta" ..... whether it is an official release or not. it is the price you pay for cutting edge technology.
sent from ICEvo
So in essence this means that the firmware in the new radio update, which is necessary/part of ics to run on phones is the heart of the data, sms, etc. issues people are having?
There are some differences between how the ROM interacts with the both radios but so far it looks like everything can still be made to work.
If you're having issues with roaming try opening up the build.prop and change 'persist.radio.voice.dom.roam=0' to 'persist.radio.voice.dom.roam=1', and then use setprop to reset it. I haven't been able to test it yet but I'm fairly certain that will bring back roaming.
raptoro07 said:
So in essence this means that the firmware in the new radio update, which is necessary/part of ics to run on phones is the heart of the data, sms, etc. issues people are having?
Click to expand...
Click to collapse
from what the lady explained to me, yes it is... intermittent data loss is a bug within the new firmware for ICS
my point here is that it has nothing to do with your ROM being intended for a virgin mobile 3D. it is because of a bug within the firmware for the radios.
as i said, sprint rep explained this to me, and seemed very confident in the way she explained it - confirming it as a known issue, and also knowing that it would be fixed soon because it was being worked on and said it would be serviced as a firmware update.
sent from ICEvo
You think a sprint tech in the store is an authority !!
For one thing, many may not care, you lose VPN capabilities. Which I need and want and has nothing to do with ICS. Flashed back to GingerBread an it's still gone.
You may also lose the ability to properly update the PRI when new ones come out with official ICS.
It is not just a banner issue.
I'm not in a roaming area to confirm roaming issues but I believe folks when they say they can no longer roam on th 3G. I never touched my default roaming settings and it always worked fine. You may be right that roaming is only ICS issue. But it smells like it's way more than that by folks reports. And quite believable given the phone half believes it's on Virgin Mobile.
It is the PRI which manages routing that is not correct. And different folks will get different issues depending on their location.
I don't think chad and friends would be working so hard to fix it if it was such minor issue and I trust them more than some sprint sales person.
Like was stated above. There are two kinds of people. Those with issues and those with no issues, YET !!
And please FIX the broken subject.
This all reeks of a panic due to us not understanding the new tech in the build we have. These issues may be a side effect of the ICS ROM or could just be issues with the way ICS interacts with the radios. The only information we have is hearsay, and people tend to overestimate effects of things when they don't know what they're looking for.
We get what we deserve for flashing beta radios and a beta rom, tbh. We accepted any possible problems by flashing these and we have nobody to blame but ourselves for not researching first.
"issues" is a vague word. whats to say a person's issue is due to ICS, the radios, or anything else in particular?
The new radios made me gain 20 pounds. There's no information showing that the radios did or didn't cause this. Yet here we are proverbially attributing all these issues to one thing or the other, when in reality WE DO NOT KNOW what is causing these problems.
retnuh730 said:
This all reeks of a panic due to us not understanding the new tech in the build we have. These issues may be a side effect of the ICS ROM or could just be issues with the way ICS interacts with the radios. The only information we have is hearsay, and people tend to overestimate effects of things when they don't know what they're looking for.
We get what we deserve for flashing beta radios and a beta rom, tbh. We accepted any possible problems by flashing these and we have nobody to blame but ourselves for not researching first.
Click to expand...
Click to collapse
People here are not stupid. Most do backups before they try something.
I restored a backup and lost capabilities I had.
I reflashed every every sprint RUU, Reflash Hboot 1.40, restored back up and things are not the same.
If you flashed that freeza patch your phone has it's feet in both Sprint and Virgin Mobile and it's not good.
Yes, we know we screwed up. And some of us would like it fixed before we get more surprises of what does not work correctly.
xHausx said:
There are some differences between how the ROM interacts with the both radios but so far it looks like everything can still be made to work.
If you're having issues with roaming try opening up the build.prop and change 'persist.radio.voice.dom.roam=0' to 'persist.radio.voice.dom.roam=1', and then use setprop to reset it. I haven't been able to test it yet but I'm fairly certain that will bring back roaming.
Click to expand...
Click to collapse
What is the "setprop" an ADB command? Do you have to use it. I edited the build.prop how you said reset the phone and nothing changed. I am roaming and cannot connect to data. My phone's data works fine when in a coverage area, but obviously not when roaming. I never did any kind of firmware update. Hope that helps.
retnuh730 said:
I've been saying that the roaming problem (if it truly exists outside of people's self affirming observations) only exists on this ROM due to ICS and the lack of roaming options on the rom itself. The radios do nothing to mess up roaming. This is all due to it being a TEST rom that we flashed. It's absurd to think that there is a perfectly functional rom sitting around with no bugs if the only leak we can get is a Virgin Mobile version. We have a beta rom and beta radios, and we should realize that's what we signed up for when we flashed it in the first place.
Click to expand...
Click to collapse
This leak isn't a beta, its release keys...
sent from my nocturnaled ics 3vo
powduh09 said:
This leak isn't a beta, its release keys...
sent from my nocturnaled ics 3vo
Click to expand...
Click to collapse
+1 this is a direct pull of the ruu for the upcoming vm evo 3d
Sent from my PG86100 using Tapatalk 2
to anyone that hasn't seen it already, if you flashed this firmware, chad is working on a fix over that this thread
http://forum.xda-developers.com/showthread.php?t=1638225&page=41
xHausx said:
There are some differences between how the ROM interacts with the both radios but so far it looks like everything can still be made to work.
If you're having issues with roaming try opening up the build.prop and change 'persist.radio.voice.dom.roam=0' to 'persist.radio.voice.dom.roam=1', and then use setprop to reset it. I haven't been able to test it yet but I'm fairly certain that will bring back roaming.
Click to expand...
Click to collapse
successfully implemented this. Hope this solves the no roaming issue. Thanks
Visionikz03 said:
successfully implemented this. Hope this solves the no roaming issue. Thanks
Click to expand...
Click to collapse
How were you able to do this? I'm trying to research a little on setprop.....but still not fully understanding it
Sent from my PG86100 using xda premium
So I feel really dumb because I am S-off and rooted using Tranquility ICS Rom HBOOT 1.12.PRI 2.45_003 PRL 25006 Baseband 1.12.11.0809 but my cell signal just drops when I am making calls. Could I have damaged the radios somehow while getting to root and S-off? Things haven't been the same since I tried to use CM10. I put CM10 on just after I rooted and flashed I put CM10 on it and that is when I started to notice my radios would just drop. Almost as if they were rebooted. Then I takes me a long time to get a good connection back. Could flashing the wrong firmware for your radios damage them? Not sure if I did that or not but I may have.
I was happy with stock but I wanted to tether every once in a while and that is why I did it. I am horrible and a very bad phone guy.(said with a little chuckle even though it is true)
If you can, please lend me some advice.
Thank you in advance. I really should stop playing with my phones as I am not savy enough to not break them. However I love to tinker but I think I will stick with full sized computers as I know how to fix them.
Andrew
Is this the wrong place to put this?
mayford5 said:
So I feel really dumb because I am S-off and rooted using Tranquility ICS Rom HBOOT 1.12.PRI 2.45_003 PRL 25006 Baseband 1.12.11.0809 but my cell signal just drops when I am making calls. Could I have damaged the radios somehow while getting to root and S-off? Things haven't been the same since I tried to use CM10. I put CM10 on just after I rooted and flashed I put CM10 on it and that is when I started to notice my radios would just drop. Almost as if they were rebooted. Then I takes me a long time to get a good connection back. Could flashing the wrong firmware for your radios damage them? Not sure if I did that or not but I may have.
I was happy with stock but I wanted to tether every once in a while and that is why I did it. I am horrible and a very bad phone guy.(said with a little chuckle even though it is true)
If you can, please lend me some advice.
Thank you in advance. I really should stop playing with my phones as I am not savy enough to not break them. However I love to tinker but I think I will stick with full sized computers as I know how to fix them.
Andrew
Click to expand...
Click to collapse
i believe if you flash the wrong firmware your device just wounldnt boot. you are on the latest radio.
might have a defective radio chip in your phone, but i dont know how to check that
You said you're running an AOSP Rom, right? Check this out : http://forum.xda-developers.com/showpost.php?p=32126633&postcount=106
thefoss said:
You said you're running an AOSP Rom, right? Check this out : http://forum.xda-developers.com/showpost.php?p=32126633&postcount=106
Click to expand...
Click to collapse
I think I am going completely back to stock and see if that has any issues. Maybe my radios aren't right so if I return to stock I will take it back to sprint and try to get it exchanged. thanks all
mayford5 said:
I think I am going completely back to stock and see if that has any issues. Maybe my radios aren't right so if I return to stock I will take it back to sprint and try to get it exchanged. thanks all
Click to expand...
Click to collapse
Okay so friday night I went with the stock rotted rom and Kaboom. My radios returned to normal. Not only that but after going with the custom roms I was having major battery issues(only 13 hours worth with limited use). I cleared the battery stats and charged it Friday into Saturday. I didn't need to recharge until tonight. 1day 8hrs 43mins with a good amount of use. I even used the wifi for about 2 hours at home installing all my apps that didn't get a proper titanium backup for some reason. Everything is back to normal. That is very strange because a lot of guys using those roms say they get similar if not better battery life. Could be me. Thanks guys for the info.
Andrew
Glad it worked for you. I've played with the AOSP roms, but I'm holding out til someone ports a Jelly Bean Sense Rom over. Til then, try Viper 2.3
I've tried every popular ROM out there it seems, and each one has this odd bluetooth stutter that I can't seem to figure out.
I loved the MeanROMs of the past, and thats my 'goto' ICS ROM, but meanbean, viper, and damn near every other one I've tried has had it.
I'm currently flashed to the latest radios and firmware, and s-off, but I can't seem to find one that works! I know its not the firmware because I can nandroid restore my ICS rom and get no stutter.
Does anyone have any ideas? My gut seems to tell me that it is an aggressive power saving setting somewhere in one of these ROMs thats built in, but I can't seem to find it.
Here are my specs:
Sprint HTC LTE 4G
TWRP 2.3.1.0
hboot 1.12.1111
radio 1.12.11.0809
Current ROM: Sinister LTE V5awe
Any ideas? Or ROM suggestions? The bluetooth is a dealbreaker because that is my primary method of streaming audio to my car and home stereo.
Thanks!
godzirrarawr said:
I've tried every popular ROM out there it seems, and each one has this odd bluetooth stutter that I can't seem to figure out.
I loved the MeanROMs of the past, and thats my 'goto' ICS ROM, but meanbean, viper, and damn near every other one I've tried has had it.
I'm currently flashed to the latest radios and firmware, and s-off, but I can't seem to find one that works! I know its not the firmware because I can nandroid restore my ICS rom and get no stutter.
Does anyone have any ideas? My gut seems to tell me that it is an aggressive power saving setting somewhere in one of these ROMs thats built in, but I can't seem to find it.
Here are my specs:
Sprint HTC LTE 4G
TWRP 2.3.1.0
hboot 1.12.1111
radio 1.12.11.0809
Current ROM: Sinister LTE V5awe
Any ideas? Or ROM suggestions? The bluetooth is a dealbreaker because that is my primary method of streaming audio to my car and home stereo.
Thanks!
Click to expand...
Click to collapse
You do not have the most current radio--see my signature.
ElMadre said:
You do not have the most current radio--see my signature.
Click to expand...
Click to collapse
Thanks! I'll try flashing that update, and do some testing with my current ROM.
Did the latest radio help?
godzirrarawr said:
Thanks! I'll try flashing that update, and do some testing with my current ROM.
Click to expand...
Click to collapse
I'm seeing the same behavior. In fact you see people complaining about this all over. A lot of people want to blame the bluetooth device. Which I'm sure in some cases is true. But I like you can flash the current stock rom and it disappears. The difference being I am on a E4GT. I am with you in that it seems it's something to do with power saving. So the CPU speed is cranked down and suddenly when the stream requires a little more processing power you get a gap as the CPU plays catch up or something along those lines. It's definitely across multiple roms across multiple devices.