Develop Bugs

PRL update with Skyraider 2.2 Sense?

Hey all. Apologies if this question has already been previously answered. Ever since installing the Skyraider 2.2 Sense ROM, my signal strength and 3G connectivity have been acting a little funky. Phone will flip flop between 1x and 3G in areas where it never used to, as well as loose signal in those same areas. I'm wondering if this has to do with an outdated or oddball PRL. I can only assume it's not a safe idea to perform an automated PRL update on a modded rom, but I don't know for sure. Anyone out there have any advice?
Thank you all in advance for your help!
Sent from my ADR6300 using XDA App

I updated mine when I updated my radio to 2.05. It works better now, and I've had no problems from VZW or anything

Alright, sweet, good to hear! Do you happen to know if the same applies to the 2.15 radio (the version I have)?
Thanks for the response!
Sent from my ADR6300 using XDA App

I updated PRL with out any issues and I am using 2.15 radio with Skyraider 2.2.

Yeah it's starting to look like I'm going to have to manually update my PRL, because I just tried doing a *228 and it came back as "Programming failed, call customer service".
Sent from my ADR6300 using XDA App

Nevermind actually. I tried it a second time and it completed successfuly. Now just need to determine if my overall signal has gotten better, lol.
Thank you all again fr your responses
Sent from my ADR6300 using XDA App

Dinc radio boost?

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/

5 vibration diagnostic code

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

Cm7 gps

I haven't used GPS in so long that I didn't realize it didn't work on the latest version of cm7 for me. How can I fix that?
Sent from my PC36100 using XDA App

GPS fix link is in my signature.

Seems like he got you, but I still don't know how it doesn't work for so many people.

teh roxxorz said:
Seems like he got you, but I still don't know how it doesn't work for so many people.
Click to expand...
Click to collapse
Just one of those things. Like how some Evos can handle higher overclocking or more unvolting than others.

So do I have to change my NV as well? Cause I would really like to take advantage of my gps so me and the lady don't get lost again haha it never happened.
Sent from my PC36100 using XDA App

mattykinsx said:
Just one of those things. Like how some Evos can handle higher overclocking or more unvolting than others.
Click to expand...
Click to collapse
Yea, that is true. I guess I got a 'premium' evo.

jacoballen22 said:
So do I have to change my NV as well? Cause I would really like to take advantage of my gps so me and the lady don't get lost again haha it never happened.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yeah do all it says to correct the issue and high Android system usage.

jacoballen22 said:
So do I have to change my NV as well? Cause I would really like to take advantage of my gps so me and the lady don't get lost again haha it never happened.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yes, its always best to keep your PRI & NV on the same version, in addition to the other directions.

all I did was flash the GPS fix (with cm7.1 and tiamat) and I'm again not getting GPS. I guess I'll need to go to that post and do all those steps? I'm just worried because there was a disclaimer that read "At this time, I can no longer recommend the below steps!!!, but I can still let you know that the GPS driver files below are pretty damned awesome." so i'm concerned.

thank you for this

3G Drops on Skyraider?

I've been running skyraider for a while now and I notice that my phone often goes to 2G and won't switch back unless I reboot. Am I the only one? What should I do?

no such problem with skyraider here, maybe you can try the new radio.

I'm on Inc2 HD for now. I don't really want to update the radio.

I've had that once since I started using this Rom. Was shortly after I first installed it. I went in and out of airplane mode and it cleared it right up. Haven't had it again since
Sent from my ADR6350 using XDA App

AgalychnisCallidryas said:
I've been running skyraider for a while now and I notice that my phone often goes to 2G and won't switch back unless I reboot. Am I the only one? What should I do?
Click to expand...
Click to collapse
Had this exact same issue. Update the radio to 722. It should work better than ever.
Sent from my Incredible 2 using xda premium