Develop Bugs

Unexplained Random Reboots On Froyo

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

[Q] Laggin, Freezing, and Making me mad!

Ok, I'm finally reporting this Uber annoying problem.
My phone will just lock up for anywhere between 2 and 15 seconds. I thought this was maybe a bad backup from titanium, so I stopped using it. I cleared my SD card, I've tried multiple roms, I'm formatted everything including SYSTEM during each different ROM install.
It seems the issue happens after I use SMSBACKUP+ to restore my txt messages. *EDIT But I've had it happen without installing SMSBACKUP+ EDIT* Handcent has been force closing on me for weeks as well. I just removed Handcent, and installed ChompSMS. The problem is still happening.
It happens very randomly, and without any cause that I can tell. I'll hit the power button, and unlock the screen, and then the touchscreen is completely unresponsive for seconds at a time. The touch buttons (home,back,etc) are also unresponsive. Then all the sudden, the phone will try to catch up to every one of my touchs.
Also, whatever it is is killing my battery. Yesterday I installed MikFroyo, and the phone was good for over 12-15 hours. Then I charged it, and something in the past 2 hours caused the issue and completely drained my battery in those 2 hours.
I've had this problem with
FreshEVO (multiple versions)
SprintLovers
Burnt Droid (multiple versions)
Ava-Froyo
OMJ's EVO
BakedSnack
I've also tried ASOP mods like MIUI and Cyanongen Mod, and as far as I can remember, the problem didn't happen with them, but I really would like to have my 4g work.
I just want my phone back!!!!

Well I don't know what your problem is exactly, smsbackup seems to be a culprit. You can check spare parts for wake lock issues. Are you using an SBC kernel?
I reccomend CM7, and you can use CM7 w/ WiMax [based on build 24] <- can be found in the development section.

First backup your apps and data. Then flash calkulins format all, then flash your rom and start from there it should work
Sent from my PC36100 using XDA App

I've been using calkulins format all for the past 2 weeks (7 flashs)

teh roxxorz said:
Well I don't know what your problem is exactly, smsbackup seems to be a culprit. You can check spare parts for wake lock issues. Are you using an SBC kernel?
I reccomend CM7, and you can use CM7 w/ WiMax [based on build 24] <- can be found in the development section.
Click to expand...
Click to collapse
I've used every kernel I could get my hands on, thinking it was the problem. I've been using stock kernels for the past 2 months now with the same problems.
I just haven't heard anything else bad about SMSBACKUP+, but I have read some issues with locking up, freezing etc regarding SMS in general.

Actually I'm one of the devs for handcent SMS and delete handcent and then install from market. See what happeneds
Sent from my PC36100 using XDA App

davidc23 said:
Actually I'm one of the devs for handcent SMS and delete handcent and then install from market. See what happeneds
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Been there, done that about 50 times too. I'm just gonna go without HandCent for a few days and a new ROM install and see what happens.
Have you had any other complaints about this?

None, what's your hardware version
Sent from my PC36100 using XDA App

davidc23 said:
None, what's your hardware version
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Current
HW: 0003
MikFroYo 4.5
2.6.32-17-gee557fd [email protected] #15
3.70.651.1

Are u using setcpu
Sent from my PC36100 using XDA App

Do you use 4g a lot? Do you reboot the phone after turning 4g off? The reason I ask, is because there is a bug with 4g, on any ROM, rooted or not. After you turn the 4g radio off, it will continuously scan, and it errors out. Download the app "aLogcat" from the market. Turn 4g on. Turn on the logcat, so it starts reading. Shut your 4g off, and go back to the logcat app. Watch all the red Wimax errors pop up. Endlessly. This causes a wake lock on the phone, so it doesn't sleep. Up time and awake time will remain the same, after turning 4g off. The only way to stop the wake lock is to reboot the phone.
Also, I have never really had that cause lock ups or freezes, it just drains the battery three times as fast when those wimax errors are occuring. Just something to check, wish I had more to suggest/offer for ya.
Here is a link with some info and other links on the issue.
http://code.google.com/p/android/issues/detail?id=11008
Some people say that it doesn't drain your battery, but I found that to be inaccurate. It certainly does for me, and the phone never sleeps when it happens. So even if that isn't what your main issue is, it's good to know about anyways, if you didn't already.
EDIT: Also, what PRI version and Radio/baseband version do you currently have? The latest? 1.90 PRI and 2.15.00.11.19? If you are on the 1.90 PRI, try downgrading it to the 1.77. The 1.90 PRI is definitely known to cause issues that you speak of on some phones. Just anothing thing to double check. Here is an attatchment of the 1.77 PRI. It sounds like you don't have anything to lose by trying. Everyone's phone acts differently with different software and what not.

davidc23 said:
Are u using setcpu
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Nope... Complete stock roms, with little to no apps. I can only think to point at bad hardware, the base sms operation, smsbackup+, handcent, or titanium backup. All of which I'd had issues without one or the other installed.

k2buckley said:
Do you use 4g a lot? Do you reboot the phone after turning 4g off? The reason I ask, is because there is a bug with 4g, on any ROM, rooted or not. After you turn the 4g radio off, it will continuously scan, and it errors out. Download the app "aLogcat" from the market. Turn 4g on. Turn on the logcat, so it starts reading. Shut your 4g off, and go back to the logcat app. Watch all the red Wimax errors pop up. Endlessly. This causes a wake lock on the phone, so it doesn't sleep. Up time and awake time will remain the same, after turning 4g off. The only way to stop the wake lock is to reboot the phone.
Also, I have never really had that cause lock ups or freezes, it just drains the battery three times as fast when those wimax errors are occuring. Just something to check, wish I had more to suggest/offer for ya.
Here is a link with some info and other links on the issue.
http://code.google.com/p/android/issues/detail?id=11008
Some people say that it doesn't drain your battery, but I found that to be inaccurate. It certainly does for me, and the phone never sleeps when it happens. So even if that isn't what your main issue is, it's good to know about anyways, if you didn't already.
Click to expand...
Click to collapse
You know what... I think you're on to something. Because an hour before this started happening today, I turned 4G on to see if I had service where I was, (I did not), but I did not reboot the phone. I'm going to play around with that idea before installing any other apps on my freshly installed mikfroyo.

4g still scans
Sent from my PC36100 using XDA App

mintee said:
You know what... I think you're on to something. Because an hour before this started happening today, I turned 4G on to see if I had service where I was, (I did not), but I did not reboot the phone. I'm going to play around with that idea before installing any other apps on my freshly installed mikfroyo.
Click to expand...
Click to collapse
Check the Edit in my previous post as well

k2buckley said:
Check the Edit in my previous post as well
Click to expand...
Click to collapse
I've tried every different radio combination. Just recently (last week) I've downgraded to Radio 1.36.00.04.02 and PRI 1.34_003.
It's currently looping the Wimax errors... I'm thinking that might build up in an hour or two and cease the phone. We'll see.

mintee said:
I've tried every different radio combination. Just recently (last week) I've downgraded to Radio 1.36.00.04.02 and PRI 1.34_003.
It's currently looping the Wimax errors... I'm thinking that might build up in an hour or two and cease the phone. We'll see.
Click to expand...
Click to collapse
Dang!! That's an old radio / pri combo! I've never rolled back that far, so can't say much about it, but are you sure that's not contributing to the issue? Maybe it doesn't like the 3.70 build.
Sent from my PC36100 using XDA App

Bootloops caused by GPS

It's been about a month i'm having this problem. Sometimes when using apps that require gps, the phone reboots itself, and then it gets stuck in a bootloop. Pulling off the battery and restarting does not help. I only have to keep it off for some minutes, and then restarting. Seems like it needs to "cool down". The phone worked flawlessly for a year. Do you think it may be a hardware/overheating issue? I read about many users complaining about it
Sent from my HTC Desire using XDA App

Rooted and running a custom ROM?
Is it the same app that causes the issue?
Sounds like an overheat issue.
You could install an app that checks temperature. Anything higher than 45, could be an issue.

Yes, rooted and s-off with cm7. Different apps caused the issue: maps, facebook, browser. I ll try checking temperatures. Thanks for the advice
Sent from my HTC Desire using XDA App

if it vibrate after reboot then it is the pv1 version
whit has a lot of problems an they are cost from the cpu overheading
so that is a mainboard problem

Yes, my device is a pvt1, and yes, it does vibrate again before rebooting when it's stuck in a bootloop. I'll send it to RMA asap. I hope it won't take much time!
Sent from my HTC Desire using XDA App

Just be sure you flash it back to stock so it kills the root,
Back-up all contacts and such, delete the fotos after copying.

i have the same kinda issues but they are caused when i use wifi or play a game while the phone is on charging..its getting quite annoying now as now i dont use it while its charging. feels like a crappy phone now. (

[Q] Running Adownloader (Torrent) with Juggernaut 4.1 ROM

Hi guys. I wanted to post this question under this thread
http://forum.xda-developers.com/showthread.php?t=1322642
but I don't have enough posts and am not allowed to post there yet.
I love the Juggernaut ROM and its worked great for me thus far. (Thanks for all your hard work Team Kang)
However, I've come across my first problem with it.
Actually I don't know if its my phone or the Rom but when I try using Adownloader for torrents, my phone shuts down to black screen.
I then have to play with it for a while (plug it into power source, unplug, battery pull, etc) to be able to power it up again
My thoughts were initially that maybe my phone couldnt handle the wifi speed 2.5 mbps download and that it overheats which causes the shutdown but I downloaded an app that checks temperature and my batter temp never goes up past 36 degrees celcius (96.8 Fahrenheit) and has even shut down at low temps like 26 degrees celcius (78.8 Fahrenheit).
So I've found out that overheat isnt the issue.
I've searched all over the net and this is the only other instance I can find. Coincidently the guy is also using Juggernaut 4.1 on T989
http://www.reddit.com/comments/ojfw3/can_we_really_not_torrent_directly_to_our_phone/?sort=old
Is my problem due to the Bullet kernel being overclocked to 1.8?
Please help as it would be GREAT to download movies to my phone @ 2.5 mbps

I had this problem once and gave up on torrenting. My immediate advice would be to flash a another kernel as bullets is relatively unstable compared to others
Sent from my SGH-T989 using Tapatalk

iLeopard said:
I had this problem once and gave up on torrenting. My immediate advice would be to flash a another kernel as bullets is relatively unstable compared to others
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Thanks for the tip
I just flashed the darkside kernel.
Hopefully this does the trick.
I will report back when I go home and check
edit.
One big improvement I've noticed so far is that my what's app receives messages when I haven't opened what's app.
Previously, if I rebooted my phone or close what's app, I wont receive any messages until I opened up the app but now I get all messages without opening up the app.

badbeatjackpot said:
Thanks for the tip
I just flashed the darkside kernel.
Hopefully this does the trick.
I will report back when I go home and check
edit.
One big improvement I've noticed so far is that my what's app receives messages when I haven't opened what's app.
Previously, if I rebooted my phone or close what's app, I wont receive any messages until I opened up the app but now I get all messages without opening up the app.
Click to expand...
Click to collapse
Fresh Wipe and Flash juggs 5.0 or another ROM. You don't necessarily need to WIPE to update to 5.0, but I would to fix your first world problems.

I am using Jugg's 5.0, and have this problem also. I have been having it ever since I flashed juggs 4.1. I am running stock kernel, so it isn't the kernel either. I am trying to run a log cat to see if a DEV can maybe see what the true issue is.
Once I get a logcat of it crashing, I will send to whitehawkx and see if he can help.

idtheftvictim said:
I am using Jugg's 5.0, and have this problem also. I have been having it ever since I flashed juggs 4.1. I am running stock kernel, so it isn't the kernel either. I am trying to run a log cat to see if a DEV can maybe see what the true issue is.
Once I get a logcat of it crashing, I will send to whitehawkx and see if he can help.
Click to expand...
Click to collapse
Had the same issue until I switched to the darkside kernel! I use ttorrent without having issues now! Try that!
Sent from my SGH-T989 using xda premium

darkside79 said:
Had the same issue until I switched to the darkside kernel! I use ttorrent without having issues now! Try that!
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Yeah I was going to report back as well!
I used the darkside kernel and my phone is working perfectly!
Thanks you Darkside!!!
Torrented a movie yesterday at 2.5 mbps (5 min) and was able to use all share to stream to my tv on wifi
Holy technology

Also, my battery life is insane!!!
I've had my phone off the charger for 6 hours and am still at 70% at moderate use.!!!
Thats with twittering, whats app, very little surfing
Can't believe I can actually use my phone and still get 18+ hours off one charge.
Thank you Darkside!!!

[FIX] [GSM] BT Temp Fix for CM9 and CM9 based ROM users

Only for CM9 and CM9 based ROM users :cyclops:​Did your phone just switch off and wouldn't turn on completely when turning on the bluetooth one day? :crying:
Do you really need your data/messages/settings/alarms/call log back? :crying:
Do you really need to access the internet or call someone urgently? :crying:​:fingers-crossed:!! HERE'S THE FIX !! :fingers-crossed:​OK, So, it's actually not a fix but a way you could get back your precious messages (if there were any), settings, alarms, call logs, etc.. everything!!
It has happened to me the third time while using AOKP Milestone 6 for the HTC One V..
So one day you just turned on bluetooth and your phone got switched off and got mad . It started getting switched off within 10 seconds as soon as it started. You have important messages, etc. whose backup you don't have. You're going mad, you just don't know what you should do within those 10 secs.. DO THIS -
First, of all, I'm not any big man to even give out a fix or something.. But what I did really helped me to get back my data..
I was using CM9 UnOfficial for the One V and there came a bad day on which my phone entered a bootloop and I was ruined with all my customizations..
I loved CM9 so I tried AOKP Milestone 6 then...
Again there came to be a day when my phone started switching off as soon as it started within 10 seconds..
I had my Airplane Mode ON 'cause I was in my class and when I turned on bluetooth, my phone went mad.
In those 10 secs for which the phone was on, it was laggy, just preparing to shut down.
I saw that bluetooth was turned off when I pull the notfication bar down. Tried to turn it on, asuming it would solve the problem, but all in vain.
Then it was really important for me to call home due to some reason.
When I tried to turn off the Airplane Mode, the phone immediately got switched off again.
Then I did this :
1. Opened the dialer app.
2. Typed *#*#4636#*#*
3. The 'Testing' menu appeared.
4. Tapped on the 'Phone Information' option. (10 secs were about to get over)
5. Scrolled down and pressed 'Turn on radio' button.
6. BOOM! The phone didn't switch off again! -The Airplane Mode was still on, BUT I was connected to my EDGE Network and could also access the internet!
Then I could call / use the mobile for a while till I reached home.. I made a backup of several things on my phone using JS Backup.. Didn't dare to mess with the airplane or bluetooth buttons them.. Then changed the ROM when I reached home.

Oops..
Ohh .. Sorry moderators..! I think I started this thread in the wrong section.. Someone please move it to the 'One V Q&A, Help & Troubleshooting' section.

I'm not a CM9 user but congrats that you've found out a workaround for it. Something smels fishy in your problem cause no one reported this kind of behavior before and I am 100% sure that maxwen's work on both bluetooth and cm9 was flawless.

1ceb0x said:
I am 100% sure that maxwen's work on both bluetooth and cm9 was flawless.
Click to expand...
Click to collapse
Umm.. what do you mean by that? Is the Bluetooth problem fixed....? I'm on CM10 now just because of the BT Prob in CM9..
Sent from my One V using xda app-developers app

i mean that the problem is at your end1

Yea I never had a problem check kernel....
Sent from my One V using xda premium

cybervibin said:
Yea I never had a problem check kernel...
Click to expand...
Click to collapse
It really happened to me three times using 201212251747 HELLBOY Kernel.. Is the problem fixed now? It won't happen if you use Bluetooth occasionally.. I use it everyday and it always happened within 6-7 days. Them I had to again reflash the same or change the ROM..
Sent from my One V using xda app-developers app

Paresh Kalinani said:
It really happened to me three times using 201212251747 HELLBOY Kernel.. Is the problem fixed now? It won't happen if you use Bluetooth occasionally.. I use it everyday and it always happened within 6-7 days. Them I had to again reflash the same or change the ROM..
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
I'll check if ur using the proper kernel once I reach home...yea I use it in the car for music and sending images and stuff
Sent from my One V using xda premium

cybervibin said:
I'll check if ur using the proper kernel once I reach home...
Click to expand...
Click to collapse
Thanks I'll not even waste a single second in turning to CM9!
Sent from my One V