Since taht I upgraded to Froy, I have always the same bugs, when I try to capture video, the screen freezes, the phone starts beeping and restarts. Also the GPS does not work.
How I can fix this?
This has happened to me with any rom and even with the official update. These problems go away, just when I return to 2.1
Thanks for any help.
Which radio are you using?
Sent from my ADR6300 using XDA App
Related
I have Skyraider 2.5.2 with sense, 1.00.03.04.06 radio, s-off.
EVERY time I go to record a video and I click the optical joystick to start recording, the screen freezes and a few seconds later my phone reboots.
The first time I was just like, ok, lets try that again. But time after time it keeps crashing and rebooting.
Is there a fix for this, or is it a bug? I'd really like to record some video.
You need to update your radio. Either to the 2.05 or if you have s-off you can also go to 2.15.
I just updated from 1.00 to 2.15 yesterday. 720p works like a charm. Also running skyraider 2.52 sense.
Sent from my ADR6300 using XDA App
Alright thanks.
So. Uh. How do I update it? lol
Sent from my ADR6300 using XDA App
Well, since I'm new I cant post links. But if you go back to the General forum there is a post called "Guides: Root, nand unlock, radio update, Froyo 2.2 update, restore stock radio/rom" by dadicus that covers just about everything.
Section 3 covers radio updates.
I would read the guide a few times over just to make sure you do everything right to avoid bricking it. Because you do not want to accidentally update the radio twice. Otherwise It's a pretty simple process.
Yep, that fixed it, thanks a ton!
God this is the nicest forum I've ever been to.
I honestly cannot find the cause of this. I Have tried everything in my power to try to fix this problem but absolutely nothing seems to work. When using my phone regularly (only on froyo) my phone will get very very hot and then start a reboot loop where it keeps rebooting and rebooting and rebooting. I have the official 2.2 update. Currently not rooted but S-OFF. I wanted to see if the root was causing any problems but im still getting the reboots. I Love my Inc. and i love the AMOLED screen. I want to be able to fix this problem so i dont get stuck with a ****ty replacement. PLEEZ HELP MEEZ
first thing would be to tell everyone what ROM you're on and if you're running setCPU.
Sent from my ADR6300 using XDA App
mzmartipants said:
first thing would be to tell everyone what ROM you're on and if you're running setCPU.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
He said that he is using the stock ota update already
But if your using setcpu this is a great time to stop
Sent from my ADR6300 using XDA App
nope im running completely stock no rooting apps
I get them everyone in awhile when I recieve a text message in the background. Like if I'm in foursquare, or the internet browser for example. And recieve a text, it'll lock up and restart, sometimes it doesn't clear my uptime which is weird...
Sooooo no one can help?
Sent from my ADR6300 using XDA App
Pleez
Sent from my ADR6300 using XDA App
I get this problem all of the time and I will tell you it has nothing to do with root. In fact, I'm not sure it is even a software issue. I have done multiple factory resets to try to troubleshoot the problem.
There is a thread at AndroidForums about it that I am currently running, but I can't link to it evidently. Look in the Support section for the Incredible.
How did you update? You're running a 2.xx radio, right?
If your problems are surviving a full wipe + RUU, the most likely culprit is that your hardware is failing.
It's a full wipe stock 2.2 and yes I have the newest radio
I was having the same issue with my phone on Stock 2.1, Stock 2.2, custom ROMs, etc. No software updates/configurations would make the random reboots stop. Anything that taxed the CPU seemed to cause my reboots. The easiest way to reproduce was to just start GPS'ing somewhere. Within minutes, the phone would go into a reboot loop that would usually only stop after a battery pull.
I took the phone into VZW while it was doing a reboot loop, showed it to them, and they put in a replacement order for me. The replacement (yes, it's a refurb) has been rock solid over a few days of heavy use. I read that if you had an AMOLED screen, then you're replacement will also be AMOLED.
tl;dr; - random reboots on stock ROM with no mods is probably a hardware failure. Go with a refurb.
Decided to go to VZW and order a replacement. They told me it would be a new phone and not a refurb but I don't trust them. Anyways it comes Thursday. I shall report back my friends. I still find this problem to be so odd
I looked and wasnt able to find a answer having to do with a evo. When I play music from bluetooth to my radio in my car it disconnects. Its never at the same time, just random. If i shut down bluetooth and turn it back on it works for a short amount of time. Any one having this isue with their evo? Im running Fresh 3.3 and king kernal cfs11. Any help would be great.
Anyone having this problem, and its there a fix?
I do get this too but happens only occasionally. Running netarchy 4.1.9 with myns Rom rls 2.
sent from my iph...wait oops.
Yea? Today I was able to play almost the while song then a disconnect. Then a song and half. Last try I got mayb 15 sec into a song then bam! Silent. Idk if its a phone issue or rom, kernal. I just updated to fresh 3.4 and kept the stock kernal when I tested it today. I ended up flashing kings cfs #11 and the problem still occurred. I just dont know!
shdwboy said:
Yea? Today I was able to play almost the while song then a disconnect. Then a song and half. Last try I got mayb 15 sec into a song then bam! Silent. Idk if its a phone issue or rom, kernal. I just updated to fresh 3.4 and kept the stock kernal when I tested it today. I ended up flashing kings cfs #11 and the problem still occurred. I just dont know!
Click to expand...
Click to collapse
Having same problem on Myns RLS 1 and RLS2, using Kings Kernel #11. Cant seem to get bluetooth to stay connected for more than a couple minutes. Once it disconnects I need completely unpair and repair and same problem happens again.
I am having the same issue, i have tried several Sense roms including stock and the issue persists with all of them. And yes, i have tried wiping several times and still no dice. I have been contemplating flashing an AOSP rom to see if it happens with those too.
I know for a fact that its a problem with 2.2 as i flashed a 2.1 sense rom and bluetooh worked without issues.
I have been having the same issue with stock 2.2 on the EVO. It happens when I am listening to music via bluetooth and ford sync and a call comes in. Afterwards, It will disconnect and won't stay connected even after a factory restore. The only fix I have found is to reload the stock 2.2 via ruu. This will work until I get a call while listening to music. Repeatable.
I'm having this same problem too. I've read that the Cynogen BT stack works but I'm in a 4G area and don't want to switch from Fresh.
Is there any way to grab the BT stack from Cynogen and blow it into another ROM?
Nope. AOSP only.
Sent from my PC36100 using XDA App
Try turning off WiFi and see if it helps.
Sent from my PC36100 using XDA App
scoobdude said:
Try turning off WiFi and see if it helps.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
nope, never have WiFi turned on in the car anyway...
Sorry if there's a post on this already, but I've tried searching and I can't find any kind of answer.
I'm a total newbie when it comes to modding my phone, but I have the alpha 1 of CM7 flashed on my epic. I was already having a few problems with the proximity sensor when it was stock (my face would bring up the keypad and dial numbers while I was in the middle of a conversation.... I could see the screen lighting up mid-convo for some reason) but it seems almost worse now that I've flashed. My calls will disconnect even though I have service, and this happens almost daily. The screen also can't sense when I take my face away from the phone, so the screen is still black when I want to end a call... I usually have to slide the keyboard open and shut in order to end the call.
Is anyone else having this kind of problem? Or does anyone know if there is a way to... I dunno, recalibrate the proximity sensor or anything? Any help at all would be fantastic.
Sent from my Samsung-SPH-D700 using XDA App
I would reflash back to stock EC05 and see if the issue continues with the prox. Most of the time a reflash stock will fix the problem. I know you said you had the issue with stock but did you reflash stock to see if it went away. If you still have the issue w/EC05 you just might have a bad prox. If you have TEP just take it in to a sprint store its free, if not it will be $35, make sure it has EC05 software when taking it in or else they will laugh at you and tell you it is the cooked rom you are running which it very well could be.
Haha ok thanks, I'll try flashing back to stock and hope it fixes itself... And thanks for reminding me to go back to EC05 if I take it to a sprint store, I def would've forgotten to change it back lol.
Sent from my Samsung-SPH-D700 using XDA App
Cm7 is in alpha and I have the same problem.
Hopefully the beta will fix this
Syndicate rom works the best for ec05 that I've used.
Sent from my SPH-D700 using XDA App
was very excited to get the update but after updating.....
is anyone else having the issue of the screen shutting off when you open up the browser? I did a search on this forum and can't find anyone who has posted about this issue.
I'm running stock ek02. basically, everytime I open up the stock browser the screen goes completely black. push the power button, unlock, happens again.... this has never happened before the update.
currently using opera as an alternative.
anyone else having this issue???
Yes I had this happen this morning. I recieved the EK02 update last week 12/9 in the early AM and this is the first time I encountered this screen blanking bug. It's only happened once but required a reboot to fix the problem. I just tried launching the stock browser again and this bug did not happen this time. I will monitor and update this thread if it happens again.
Happened to me too, amongst other issues since the update. I took the phone in to Best Buy and I'm getting a refurbed one, which sucks and is another story.
so after it happened for the first few reboots immediately after updating, it hasn't happened again.
I feel like a lucky man.
I wonder what was the cause?
Doesn't seem like this has happened to many people so I'll make a special point to keep you two updated on any developments on my end.
Thanks guys.
try clearing your browser data
Sent from my SPH-D710 using xda premium
Not to hijack this thread, but how about the lock screen turning on very slow after hitting the power button on ek02?
neudof said:
try clearing your browser data
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Thanks for the suggestion; thats a good tip. I tried clearing out the cache and the data- no dice.
I think its a bug that is triggered by the screen brightness setting. if you set your screen brightness setting under system to the lowest setting, go into browser, turn on manual brightness, slide that all the way down, it seems to happen more.
I've moved on to playing with some custom roms though so someone will have to try that out and see?