Has anyone figured out how to juice up the radio? Much like overclocking the CPU, but with the radio to improve up and down signal.
Willing to run any experimental programming on my phone if anyone has something to try out.
I'm not worried about bricking my phone, as that's already happened and I've brought it back to life again, so gimme all you've got!!!
Sent from my ADR6300 using XDA App
Haven't ever seen anything like that, no.
.......and FYI if you're still using it, it wasn't "bricked"
Other
You could always try the other released radios. The 11.xx has been scoring some pretty "oh my goodness, how fast can I uninstall this thing" ratings, but the 9.xx may do you some good. On all radios, YMMV; and be VERY VERY careful when flashing.
When it bricked it was stuck in an infinite boot loop, then after a few tries, wouldnt go further than hboot. I got lucky and found a way to restore an old rom I saved to my PC with the sdcard. I'm just glad I could still get it to run clockwork recovery.
Sent from my ADR6300 using XDA App
Bricked actually means that you can't power it on its 100% unresponsive.
Sent from my Incredible using XDA App
jdmba said:
You could always try the other released radios. The 11.xx has been scoring some pretty "oh my goodness, how fast can I uninstall this thing" ratings, but the 9.xx may do you some good. On all radios, YMMV; and be VERY VERY careful when flashing.
Click to expand...
Click to collapse
Interestingly, the 11.x radio increased my battery life about 20% (no major impact on my reception, if anything it seemed to have cost me a dB or two) compared to the 7.x radio. Tried the 9.x for a few days; cost me nearly half my battery life and caused the phone to run above 100F just for surfing the web.
It's DEFINITELY a YMMV situation.
6stringandy said:
When it bricked it was stuck in an infinite boot loop, then after a few tries, wouldnt go further than hboot. I got lucky and found a way to restore an old rom I saved to my PC with the sdcard. I'm just glad I could still get it to run clockwork recovery.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Your phone wasn't even remotely close to being bricked. That would be kind of like saying a dislocated shoulder is total paralysis.
A bricked phone is one that can't do anything at all and is completely unrecoverable. A basic rule of thumb is that if you can get to the bootloader, the phone is in no way bricked.
Gahh Its Lee said:
Bricked actually means that you can't power it on its 100% unresponsive.
Ah, ok. Had no clue. Thought that was when the programming crashes. Thnx.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Sent from my ADR6300 using XDA App
When did this go from radios to bricks? I get it, I didn't brick it. (2 point for numbnuts)
Where do I go to get other radio versions, and which ones don't play nicely with Dinc?
Sent from my ADR6300 using XDA App
Search for the radio thread in the dev section.
6stringandy said:
When did this go from radios to bricks? I get it, I didn't brick it. (2 point for numbnuts)
Where do I go to get other radio versions, and which ones don't play nicely with Dinc?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Sent from my Incredible using XDA App
6stringandy said:
When did this go from radios to bricks? I get it, I didn't brick it. (2 point for numbnuts)
Where do I go to get other radio versions, and which ones don't play nicely with Dinc?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Flashing radios is the number one way to brick your phone; basically, be careful and check MD5 sums.
Sent from my Droid Incredible running Myn's Warm Two Point Two RLS5.3.
Grr
I wish VZW would just release an official updated radio already.
As much as it ticked me off that some guy declared his own thread to be the new official thread, I think this has the links:
http://forum.xda-developers.com/showthread.php?t=886129
You can also get all Radios except the 11.xx radio here:
http://adrynalyne.us/files/di_radios/
Related
So lately I've been getting the 5 vibration code and I've been searching around here and on other forums and no one seems to know what causes it. Has anyone else that's been experiencing this noticed that it seems to go away after a battery pull and then letting the phone cool down? I'm rooted with unrevoked running cm7 rc2 with Chad's newest kernel right now and tried running cm7 with the included kernel and experienced the same issue.
My main concern is whether to ruu and whether thats going to fix it or if it's simply a hardware issue
Sent from my ADR6300 using XDA Premium App
I have it too. Can you boot your phone up like normal after a little while? Everyone else on this forum who gets this can't do jack with their phone. I can boot up fine afterwards, it's just extremely annoying.
It's a code for some kind of hardware failure and they all had to get a new phone. I've been told a RUU may fix everything, but that's a semi-long process for someone as ADD as me to go through. You could try it though. And if you do, shoot me a PM with the results.
Yeah that's exactly what mine does, It'll boot right away and I usually only run into the issue when I'm playing a game for more than five minutes or using my phone in a warm environment. It seems to hit 100° F and then stops itself from overheating.
I was really hoping to not have to Ruu, because its such a process and I don't want to lose the gingerbread keyboard. Maybe someone else will chime in with another idea.
Sent from my ADR6300 using XDA Premium App
So far you and I are the only 2 I know about in the internet who can still boot up like normal afterwards.
I wiped dalvik last night and I haven't had the issue today, you might give that a try. It can't hurt.
-CM7 ADR6300
Ill try that today. I initially thought it was the battery overheating but it did it with the stock 1300 and its doing it with the evo battery I'm using now. Ill finish setting up adb and try the ruu next week when I get time.
Sent from my ADR6300 using XDA Premium App
This just in, rebooted while playing star wars podracing on n64oid.
I think it is a heat issue, cuz my phone is always pretty warm when it happens.
-CM7 ADR6300
I've read about this in a lot of forums lately. But it seems like it only comes up with cm7. You guys sure its not rom related?
Sent from my ADR6300 using XDA App
Also had it on OMFGB, though not as frequently.
Also, today I've noticed my haptic feedback has been... varied in vibration intensity.
-CM7 ADR6300
thisisshep said:
Ill try that today. I initially thought it was the battery overheating but it did it with the stock 1300 and its doing it with the evo battery I'm using now. Ill finish setting up adb and try the ruu next week when I get time.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
I have an Ruu that you just place on the root of your SD and flash through hboot no adb needed if you want it pm me..... and ill give you the file and instructions
Sent from my Incredible using XDA App
Well I broke down tried the RUU and that went through fine but I cant seem to replicate the error with stock. I tried gaming for about 20 minutes and it didnt do it yet, normally it does it after like 5
Good to know.
Have you gone back to CM7 and seen if it helps out there?
-CM7 ADR6300
No I havent tried rerooting yet and reinstalling cm7 It keeps doing it only now it gets stuck in a boot loop instead of doing the five vibration thing then it boot loops about 3-5 times till it cools itself down then restarts normally like nothing ever happened
I already talked to verizon and the new ones in the mail so theres really no sense messing with it anymore now i just need to decide if i want to root the next phone or not
That's what's happening to mine now, too... I also couldn't root it? Unrevoked kept failing. Oh well. I'm selling it and migrating to a Thunderbolt.
Sent from my ADR6300 using XDA App
thisisshep said:
So lately I've been getting the 5 vibration code and I've been searching around here and on other forums and no one seems to know what causes it. Has anyone else that's been experiencing this noticed that it seems to go away after a battery pull and then letting the phone cool down? I'm rooted with unrevoked running cm7 rc2 with Chad's newest kernel right now and tried running cm7 with the included kernel and experienced the same issue.
My main concern is whether to ruu and whether thats going to fix it or if it's simply a hardware issue
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
What version of ClockWorkMod are you running? I read some problems with flashing CM7 caused by CWM 3.0.0.8 that was fixed by going to 3.0.0.7
dpwhitty11 said:
That's what's happening to mine now, too... I also couldn't root it? Unrevoked kept failing. Oh well. I'm selling it and migrating to a Thunderbolt.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Nice, I hope the person who buys it informed.....id be f ing pissed
Sent from my ADR6300 using XDA App
pete_kowalski83 said:
Nice, I hope the person who buys it informed.....id be f ing pissed
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Yeah, you've got that right !!!!
When it happened to me I couldn't do a damn thing except get into clockwork Mod, which didn't help because I couldn't access the sdcard. I called up verizon and got a new one. For the two of you that actually have a working phone after this is your phone S-ON or S-OFF?
thisisshep said:
It seems to hit 100° F and then stops itself from overheating.
Click to expand...
Click to collapse
100F is nothing for these processors. Think about it, your body is 98F and a processor is meant to handle a lot more heat than your body. I know the TI OMAP in the original droid had a failure point of 220F.
silverxbv2 said:
I've read about this in a lot of forums lately. But it seems like it only comes up with cm7. You guys sure its not rom related?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Nope, not rom related since it happened to me when I was using Incredibly Re-Engineered v2.3 and flashing a custom kernel when it happened.
Mine remained rooted ans s-off throughout the issue.
I unrooted and applied s-on and reverted to the November RUU and it fixed everything.
Rerooted and reapplied s-off a few hours ago and flashed Virtuous. No more CM7 for me. That's when I started having issues.
Mine does the same thing. Vibrates once, turns off, vibrates 5 times and the LED blinks green. I think mine is related to an overheating issue. Mine reboots almost always when im plugged into the car charger, talking on the phone over bluetooth on my way to work. About a 35-45 minute commute. Even when plugged in at home, and while messing with the settings as well. The only thing that is almost always the same is the screen brightness. Thats when it gets super warm and then turns off. I'll try it out with the screen brightness settings to lower then usual. But when I let it cool off, like I do in the car in front of the A/C vent for about 30 seconds,, with the battery out of the device, it comes right back on no problems.
Mine was rooted and s off. I believe I installed cm7 using clockwork 3.0.0.7 then upgraded to 8 and still had the issue. I know 100°f is nothing for a processor but it seemed to have issues as soon as it got around 110 then if you let it sit it works again so that's what led me to thinking it was a heat issue even though it doesn't make much sense
Sent from my ADR6300 using XDA Premium App
Yeah, you read right. I want to brick my Evo.
Any surefire ways to go about it?
I already flashed some GSM radios, but it's still booting like a champ. Rawr.
I'm curious as to why? You could try flashing a rom for a different phone.
We're comin from a pure power source.
metalfan78 said:
I'm curious as to why? You could try flashing a rom for a different phone.
We're comin from a pure power source.
Click to expand...
Click to collapse
I did, and it still boots into recovery.
Try running the ruu for another phone and see if it still boots. Try the inspire 4G ruu, or grab the inspires radio and flash it. Maybe even the Motorola droids radio and a rom.
~ d3rk
The catch with the radios is to update then interrupt the update process by pulling the battery. That should do the trick.
~ d3rk
dirkyd3rk said:
The catch with the radios is to update then interrupt the update process by pulling the battery. That should do the trick.
~ d3rk
Click to expand...
Click to collapse
At what point though?
And you can't flash that RUU. Or the inspire's radios..
Can you attach something for me to flash or direct me to it?
I still wanna know why? Lol
We're comin from a pure power source.
dirkyd3rk said:
The catch with the radios is to update then interrupt the update process by pulling the battery. That should do the trick.
~ d3rk
Click to expand...
Click to collapse
exactly correct!
flash the radio then reboot and when you see the lil android guy next to the box, pull that battery instant paperweight
Don't help this idiot try to get a new phone if has one that works
Sent from my Optimus V
Why on earth would you even do something like that??? Lol
Sent from my GT-I9000 using XDA Premium App
He's clearly aware of what he's doing. Why are you guys in here judging, its his phone right? Ok then stfu if you aren't trying to help.
~ d3rk
he wants an answer and asked the question, who are we to discuss what somebody should or shouldn't do with something they own
Keep flashing radio and pulling out battery while in the middle of it. Would have to so it up to 20 times
Sent from my PC36100 using XDA App
if the battery pull doesn't work, you can do what proskaterronnie did in my sig ;p
What bout putting a sbc kernel and keep it charging and use it a lot till if over heats I'm not sure if it will. Work buy just giving ideas
Sent from Gingersense
kidram said:
What bout putting a sbc kernel and keep it charging and use it a lot till if over heats I'm not sure if it will. Work buy just giving ideas
Sent from Gingersense
Click to expand...
Click to collapse
Radio interrupt is way easier and less time 0_o
~ d3rk
I had my phone plugged in for 5 days with a sbc kernel, didn't even get warm, no smoke, battery didn't care
Why not just lose it? And then you can sell it to me for $50 when you find it again.
I don't think I want that one though.
Sent from my PC36100 using XDA Premium App
dirkyd3rk said:
He's clearly aware of what he's doing. Why are you guys in here judging, its his phone right? Ok then stfu if you aren't trying to help.
~ d3rk
Click to expand...
Click to collapse
I'm not judging, I just have never seen anyone ask about deliberately bricking a phone and wanted to know what for
We're comin from a pure power source.
xHausx said:
Why not just lose it? And then you can sell it to me for $50 when you find it again.
I don't think I want that one though.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Because that costs 50 bucks.
The problem is, when I flash a radio, it just says how it's flashing, then it says to reboot. Then it goes to the evo w/ refresh symbol, then boots back up. I have pulled at every step along the way, and I still boot. Can someone link me up to some radios or RUUs with some instructions as to what to do with whatever it is?
And I would appreciate it if people who don't have anything constructive to say would not say anything. I paid a lot of money for this device, and IT IS MINE TO DO WHATEVER I WANT WITH.
I recently rooted my incredible 2 successfully and got CM7 on with no problem. I was trying to install a new splash screen, but accidentally installed my existing radio (1.09.01.0722) instead. Now I can't get any wireless signal or dial *228. I've tried different radios, but none of them work now. Any ideas?
thanks
You're able to still use the phone, but you don't get any data or anything?
Sent from my ADR6350 using xda premium
It's not bricked if you can turn in on.....
Did you remove the radio file after you flashed?
Had same issue on build 109 I placed a call and it fixed it. Yes placed a call with no 3g or 1x and no baseband showing in software. 3g then showed up and baseband updated.
Sent from my Incredible 2 HD using XDA App
kubes069 said:
It's not bricked if you can turn in on.....
Did you remove the radio file after you flashed?
Click to expand...
Click to collapse
Ya that's what I was thinking too. Didn't make sense to me about what he was saying.
Sent from my ADR6350 using xda premium
Try reflashing your original stock ROM and everything... Do the Ruu if nothing else works.. you'll lose root, but your phone will most likely work again... Then if you really want to, reroot.
Sent from my ADR6350 using xda premium
faehsemc said:
reflash...stock ROM, RUU if nothing else works.. etc. etc.
Click to expand...
Click to collapse
This is what I was about to say. seems like your only option and hope it fixes it.
I always thought that the flashing your Radio twice thing was just a rumor cause I can never find any answer as to why this would brick your device.
guess it doesn't care it just does!
Hope you can get an insurance replacement being rooted. Verizon wouldn't even cover my week old battery that was bad from the factory and wouldnt take a complete charge because the VZW dip behind the counter noticed the custom boot screen and started asking questions. guess I should have hidden my mods!
I really wish you guys would look up the definition of "brick" if you don't understand what a BRICK is. please refer:
Bricked
Bricked refers to ANY hardware that is unable to start up due to bad software; Usually because of a bad software flash, a modification done improperly, loss of necessary files, being overheated from overclocking or overuse if the item is a lemon, a short-circuiting, or a Trojan that deletes necessary files for a few examples.
The noob bricked his PSP because he took out the battery while running a firmware update.
andybones said:
I really wish you guys would look up the definition of "brick" if you don't understand what a BRICK is. please refer:
Bricked
Bricked refers to ANY hardware that is unable to start up due to bad software; Usually because of a bad software flash, a modification done improperly, loss of necessary files, being overheated from overclocking or overuse if the item is a lemon, a short-circuiting, or a Trojan that deletes necessary files for a few examples.
The noob bricked his PSP because he took out the battery while running a firmware update.
Click to expand...
Click to collapse
^ this
Sent from my Incredible 2 using Tapatalk
Thanks for all the help. I tried switching to a different rom and that worked. I'm afraid to go back to CM7, but MIUI works just fine, so I'm sticking with it.
morenone said:
Thanks for all the help. I tried switching to a different rom and that worked. I'm afraid to go back to CM7, but MIUI works just fine, so I'm sticking with it.
Click to expand...
Click to collapse
No reason to be afraid... Do a full wipe and everything.. will he just fine.. and my real advice.. stay away from radios...
Sent from my ADR6350 using xda premium
Don't know what happened, my phone has been going strong with a the SuperGalaxy rom 1.7 with no problems. I recently updated to 1.8 and it ran fine for the past two days with no problems. Then after leaving the phone on the charger at work yesterday, the phone kept resetting randomly. I unplugged it, hard reset, flashed a different rom, everything, and it still keep resetting randomly. Not sure what the problem is, any suggestions?
Edit: I'm a dumbass, realized my cpu was under clocked to 800mhz, running smooth at 1400mhz now.
okay, i'm not a dumbass (maybe). Phone keeps resetting on its own randomly still but less frequently after I overclocked.
How is your battery condition? Like how old is it? Do you have and tweaks (kobridge or phakker scripts)
Cpusleep app? And you said it happens on a few ROMs, I would say it maybe a battery or hardware issue. Also, do you check the MD5 sums before you flash the different ROMs?
Sent from my SPH-D710 using XDA
Battery condition is good, I actually have two oem batteries that I use daily and swap them when one dies.
I'm not running any tweaks currently, but when I flashed the roms recently its been through a nandroid backup of my previous working rom. But I'll try a clean install without a backup and see if that works. Thanks
Sent from my SPH-D710 using xda premium
Okay, just did a fresh clean install from recovery. The phone still resets, I've noticed if it's plugged in to a charger though instead of resetting it will just turn off and show me the battery charging screen.
Also, how do you check the MD5 sums? I always thought the phone recovery automatically checks this before it flashes a rom?
Sent from my SPH-D710 using xda premium
Subiegsr said:
Okay, just did a fresh clean install from recovery. The phone still resets, I've noticed if it's plugged in to a charger though instead of resetting it will just turn off and show me the battery charging screen.
Also, how do you check the MD5 sums? I always thought the phone recovery automatically checks this before it flashes a rom?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Are you using a stock battery charger? Is the charging cable damaged or loose? I had an issue with an after market charger making my phone freeze up before.
Not to my knowladge, but it never hurts to check it. I use md5sum app.
Sent from my SPH-D710 using XDA
Okay, I flashed a totally different ROM and it seemed to have solved the problem for now. Most likely it was a ROM issue, which is kind of weird since it was using the same rom before without any issues, even when I did a recovery of it. Oh well, maybe it was the right combination of apps and crap. But so far right now, everything is good. Thanks for the help g_ding84!
What were you using to under/overclock? Setcpu specifically has been known to cause the exact issue you were having, namely random reboots, however I would not be shocked to find other overclocking utilities that could cause the same problem. Regardless I'd be willing to bet that whatever you were were using to adjust the clock speeds was the source of the issue as opposed to the ROM.
Sent from my SPH-D710 using Tapatalk 2
Subiegsr said:
Okay, I flashed a totally different ROM and it seemed to have solved the problem for now. Most likely it was a ROM issue, which is kind of weird since it was using the same rom before without any issues, even when I did a recovery of it. Oh well, maybe it was the right combination of apps and crap. But so far right now, everything is good. Thanks for the help g_ding84!
Click to expand...
Click to collapse
No problem, just wanna find out the root cause of the reboots.
Sent from my SPH-D710 using XDA
---------- Post added at 11:29 PM ---------- Previous post was at 11:26 PM ----------
cp320703 said:
What were you using to under/overclock? Setcpu specifically has been known to cause the exact issue you were having, namely random reboots, however I would not be shocked to find other overclocking utilities that could cause the same problem. Regardless I'd be willing to bet that whatever you were were using to adjust the clock speeds was the source of the issue as opposed to the ROM.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
You may be right on the money with that. It could be causing script confliction. Between the ROM and the CPU app. But I do know that cpu app scripts will override the ROMs cpu scripts, but not all the time.
Sent from my SPH-D710 using XDA
Subiegsr said:
Don't know what happened, my phone has been going strong with a the SuperGalaxy rom 1.7 with no problems. I recently updated to 1.8 and it ran fine for the past two days with no problems. Then after leaving the phone on the charger at work yesterday, the phone kept resetting randomly. I unplugged it, hard reset, flashed a different rom, everything, and it still keep resetting randomly. Not sure what the problem is, any suggestions?
Edit: I'm a dumbass, realized my cpu was under clocked to 800mhz, running smooth at 1400mhz now.
Click to expand...
Click to collapse
This has been happening to me all day today even after Changing roms and removing every tweak related app. It even reboots inside the recovery menu wtf
Sent from my SPH-D710 using xda app-developers app
FuMMoD said:
This has been happening to me all day today even after Changing roms and removing every tweak related app. It even reboots inside the recovery menu wtf
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I would bring your battery in sprint. You may need a new one.
Sent from my SPH-D710 using XDA
g_ding84 said:
I would bring your battery in sprint. You may need a new one.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I have 3 OEM and 4 extended they all do the same thing.
Sent from my SPH-D710 using xda app-developers app
You might try this thread...
http://forum.xda-developers.com/showthread.php?t=1916817
tysonrj said:
You might try this thread...
http://forum.xda-developers.com/showthread.php?t=1916817
Click to expand...
Click to collapse
Thank you very much. I didnt know this was an issue with the phone.
FuMMoD said:
This has been happening to me all day today even after Changing roms and removing every tweak related app. It even reboots inside the recovery menu wtf
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Does it reboot in download mode? If not..I would odin to stock and go from there see if that fixes things.
Update: still resetting. :crying:
Today its been resetting probably about once every few minutes to ten minutes. It's stupid, like the battery will say 60% and when it reboots on its own, the battery will be at like 10%. No idea what the issue may be, but I might try to see if it will reboot in download mode as some of you suggest and maybe try to flash a stock rom. It seems that when it does go in reboot crackhead mode it will do it even in recovery.
The power button will not be as functional during the crackhead reboot mode as well. I'll press it and nothing will happen, but the screen will come on itself (not sure if this is a delay or just the screen coming on by itself lol).
I'm not too worried about exchanging it as of now, since I'm in the market for a new phone, but would like to fix this issue so I can sell the phone; if not I'll just do the trade in thing with Sprint (even though I won't get as much).
Subiegsr said:
Update: still resetting. :crying:
Today its been resetting probably about once every few minutes to ten minutes. It's stupid, like the battery will say 60% and when it reboots on its own, the battery will be at like 10%. No idea what the issue may be, but I might try to see if it will reboot in download mode as some of you suggest and maybe try to flash a stock rom. It seems that when it does go in reboot crackhead mode it will do it even in recovery.
The power button will not be as functional during the crackhead reboot mode as well. I'll press it and nothing will happen, but the screen will come on itself (not sure if this is a delay or just the screen coming on by itself lol).
I'm not too worried about exchanging it as of now, since I'm in the market for a new phone, but would like to fix this issue so I can sell the phone; if not I'll just do the trade in thing with Sprint (even though I won't get as much).
Click to expand...
Click to collapse
Trade in is roughly $80 bucks (i'm looking to do that with mine this weekend hopefully for the S3) Sorry your having issues.. Mine has done it once ina great while.. but nothing crazy. Good luck on new phone! (I'm a craigslist junky so i'll shop on there for temp replacements lol) Got my Touch for $50 which was an upgrade from my OG Epic.
milky1112 said:
Trade in is roughly $80 bucks (i'm looking to do that with mine this weekend hopefully for the S3) Sorry your having issues.. Mine has done it once ina great while.. but nothing crazy. Good luck on new phone! (I'm a craigslist junky so i'll shop on there for temp replacements lol) Got my Touch for $50 which was an upgrade from my OG Epic.
Click to expand...
Click to collapse
Thanks man. It started doing it today and I took out the SD card and it hasn't done it since. So maybe it was the SD card this whole time?
Hopefully it is.
Sent from my SPH-D710 using xda premium
I am running aerovan's cm 10-20121003 with 2.6.35.14 ae14 kernel and radio 1.09.01.0622 I've got between -83 and -95 dBm signal strength when I check. I ask you guys, who I consider experts compared to me, if there is any reason for me to flash a different radio. If the answer is yes then a suggested radio would be a welcome addition to your answer. Oh and thanks in advance.
Jasonp0 said:
I am running aerovan's cm 10-20121003 with 2.6.35.14 ae14 kernel and radio 1.09.01.0622 I've got between -83 and -95 dBm signal strength when I check. I ask you guys, who I consider experts compared to me, if there is any reason for me to flash a different radio. If the answer is yes then a suggested radio would be a welcome addition to your answer. Oh and thanks in advance.
Click to expand...
Click to collapse
It couldn't hurt but those are pretty good numbers you're getting, I wouldn't expect a lot better
Sent from my Incredible 2 using xda app-developers app
So the short answer is no.
Sent from my Incredible 2 using xda app-developers app
Derp
The short answer is try it and see
Sent from my Incredible 2 using xda app-developers app
jeremytn86 said:
The short answer is try it and see
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
Yeah, you can always flash back. It's easy. Rename it, put it on root of sd, reboot into bootloader and let it do its thing. Be sure to rename again and put it somewhere else or delete it once you are done. Otherwise anytime you boot into bootloader it will try to flash again, which some say is bad. If you don't know how to do it, check the stickies.
Sent from my Incredible 2 using xda app-developers app
I'm great at reading stickies. I was just wanting to know what the benefits of flashing a new radio really were. Like I said I'm pulling good service. I was just trying to figure out the benefit vs. potential risks of flashing a radio. It does seem like the risk is relatively low, but I really haven't seen the benefit side of it.
Jasonp0 said:
I'm great at reading stickies. I was just wanting to know what the benefits of flashing a new radio really were. Like I said I'm pulling good service. I was just trying to figure out the benefit vs. potential risks of flashing a radio. It does seem like the risk is relatively low, but I really haven't seen the benefit side of it.
Click to expand...
Click to collapse
The reason we say try and see is because benefit varies. Some don't notice any. I'm not sure I do. Others see better battery, signal, performance, ect. Nothing about this phone is consistent for everyone. One person swears a rom is flawless and another can't get it to boot. If you think your phone performs well enough I would not bother.
Sent from my Incredible 2 using xda app-developers app
I did end up updating the radio. I haven't seen any noticeable change. So for me it was pointless from a performance stand point, but from the experience stand point it was worth it. The slight moment of panic when the phone doesn't make it past the splash screen before all of the different advice from what I've read on the forums kick in and I go into recovery and wipe the delvak which I had forgotten and the cache and everything booted up great.
Sent from my Incredible 2 using xda app-developers app
Agreed. It's good to learn. Helps ease your mind about trying things.
Sent from my Incredible 2 using xda app-developers app