Hey guys could anyone help me out, I received a refurbished phone from Verizon 5 days ago and it keeps rebooting. I managed to root my phone using "BAMF GingerREMIX v2.0 Beta #6", Radio: 1.39.00.0430. The most I can use my phone is for about 10 min. unless I leave plugged into a charger. Can anyone help me out???
Are you sure your battery is any good?
Yeah my battery is good, i got a brand new one and its still acting up..
Change the radio to the mr2 radio. Seems the most stable of the gb radios. That might help
Sent from my thunderbolt
This happened to me as well as soon as the screen went off. Rebooted. If I kept playing with it it was fine.
Had to go back to Froyo roms because of it. Happened with MR2 and 2.5 radios.
Sometimes when I mess with the kernel settings a lot this will happen. Try flashing a new kernel or even the same one and see what happens.
Mine has started doing the same thing after receiving refurbished from VZW. My old one never rebooted with same setups. Something quirky going on with it. I can flash back to stock and stops. Its not the rom or kernel i'm using because i have tried all combinations that used to work flawless on old device.
Related
So I've done a lot of searching and haven't really found anything definitive. I've found that with some roms I'll lose GPS signal after a certain amount of time (say 10-30 minutes) and have to turn GPS off and back on or reboot the phone. I saw something about flashing a different radio may make a difference. Kinda just wanted to see other peoples thoughts on the issue or if maybe there is something else I can do before I go flashing a different radio.
Currently running CELB 4.1 and baseband 2.42.01.04.27 and I have the issue.. I've had it with most of Tazz's roms as well. KaosFroyo is the only one Ive used that I've never seen the issue with, but I'm really diggin CELB right now and this is the ONLY issue I've got with it.
Have you tried GPS status in the market? I know it will help you lock in a signal, so it would make sense that it would also help keep your GPS locked in.
Bayhill Jacket said:
Have you tried GPS status in the market? I know it will help you lock in a signal, so it would make sense that it would also help keep your GPS locked in.
Click to expand...
Click to collapse
I have now.. I did the reset and download options in the program. Too bad this isn't something I can quickly test. I'll report back with the results. Thanks!
I have noticed this as well. Last time it happened to me it was 4:30 in the morning, and the "GPS lost" message came up about 180 seconds before I had to make two freeway changes in an area I'd never been before. (CELB 3.9 and same radio as your case). Fortunately for me I had reviewed the route, so I more or less knew what to do.
If I recall correctly, it has always happened after the Nav app had been running for a fair bit of time - at least 30 minutes or more.
However, I don't know if it is something about the root ROMs or not - I started using rooted ROMs back in March or so, so I really don't have a tremendous operating baseline on stock 2.1 ROMs to compare it to. Maybe it is a problem there, too!
If I recall correctly, the last time it happened, I just pulled up GPS Status and asked it reload the aGPS state (without exiting the Nav app), and the Nav app seemed to gracefully recover.
Annoying? Yeah. I don't know what can be done about it, though - like the "undead calls" problem, it happens so infrequently that it is hard to know whether or not a ROM change actually fixes the problem.
bftb0
I had the same problem with every 2.2 rom I used GPS with. I decided to go back to 2.1 because I have been needing GPS alot more often lately but I havent tested it out since I made the switch. I'll try it out today and report the results tonight.
This same thing seemed to happen on the 2.1, CyanogenMod 5 based ELB by Conap as well. If it is happening with all of the 2.2 ROMs, I wonder if it's just a CyanogenMod issue?
See http://forum.xda-developers.com/showthread.php?p=6812308#post6812308 (this was not the only person reporting it, if you search that thread.)
I really don't think it's ALL 2.2 CM roms though. I've gone on 7 hour car trips with Kaos Froyo without a single drop.. to and from. I've seen another theory somewhere around here about it being certain hardware revisions that act this way with certain software builds. At lease we've got a thread dedicated to this issue now.. maybe we can get something figured out.
Still don't know if the GPS status program helps.. I left navigation turned on for a bit sitting in my house and it stayed connected for the half an hour I left it, just don't think that's gonna be an accurate test with not moving around and all. If it doesn't work I will try a different radio.. I saw somewhere one guy had good luck with a specific older version radio. If that's what it comes down to I'll try.
I have been having issues with the GPS working on both of my phones while using 2.2 roms. I switched to 2.1 a few days ago and I used the GPS on my way to work this morning and didnt have any issues. I also had to flash Senseable a couple of months ago while on a road trip because I was tired of loosing the GPS signal every half hour. It may be a CM thing.
Im having the same issues as well. Haven't found a fix yet..
I've had this issue, after I flashed KaosFroyo(v36), and XTR(4 i think). I recently unrooted using Flashback21 v1 and flashed with the radio included. I have gone back to xtr 5 now and have had no lost gps in over a week. Don't have a clue as to why. hope it helps someone.
deadbot1 said:
I've had this issue, after I flashed KaosFroyo(v36), and XTR(4 i think). I recently unrooted using Flashback21 v1 and flashed with the radio included. I have gone back to xtr 5 now and have had no lost gps in over a week. Don't have a clue as to why. hope it helps someone.
Click to expand...
Click to collapse
give us another update. is the gps problem still fixed for you? Thanks!
I have flashed the radio directly with the verizon zip file that is around and I still get inconsistent results But it always drops a signal eventually in about a 1/2 hour
Jrocker23 said:
I have flashed the radio directly with the verizon zip file that is around and I still get inconsistent results But it always drops a signal eventually in about a 1/2 hour
Click to expand...
Click to collapse
I've seen it on several ROM's as well. From what i've messed with, it doesn't seem to be dependent on the autokiller memory preset, radio firmware, or amount of overclocking i'm doing. It doesn't seem to be dependent on how many programs are running either. I usually have nav and pandora running while i'm in the car, and sooner or later, the gps poops out.
I feel like it seems to happen less, now that i'm back to using the on-demand governor. but that could just be in my head.
I've had to go back to a 2.1 rom because of it. Its very annoying when the goa signal gets lost right before the exit ramp.
Sent from my Eris using XDA App
Im thinking of going back to a 2.1 rom as well...
I have also seen the same results on any 2.2 or higher rom. I have since returned to XTRRom 5.0 and have not had a single problem with GPS on any of my jogging runs. I definitely think it is a CM thing. At least on my phone.
Using kaosfroyo v39 and I flashed that sprint phone radio on my eris and haven't had any gps issues. In fact, just the opposite. Mine would lock up before the v39 and the radio flash
I flashed that radio as well and today not one issue at all. Will test more tomorrow
I'm using the 2.42.02.10.29 sprint radio and still seeing it drop out.
Sent from my GSBv1.1 using XDA App
haganme said:
I'm using the 2.42.02.10.29 sprint radio and still seeing it drop out.
Sent from my GSBv1.1 using XDA App
Click to expand...
Click to collapse
Today I even flashed back to the July 2010 version (2.42.01.04.27). the gps dropped out almost every 5 minutes while i was driving around. that's the worst i've seen. So i flashed back to the 2.42.02.10.29 sprint radio again. I haven't seen very good navigation performance on the v1.1 gingershedbread overall, actually. my position on the gps nav doesn't update very often, although it seemed like the voice instructions were still pretty well timed as usual.
Hi.
I am about to unroot and go back to otb stock. I am wondering if anyone knows for sure when the random reboots that I, and several others encounter, first started because I need to know whether to do the OTA after I go back to stock.
From my memory....... :
Wasn't there 2 OTA's?
And the random reboots started after installing the 2nd one?
So should I just install the first one.......orrrr......does it automatically only give one OTA direct to the 2nd one released?
Or should I not install any OTA's at all and patiently wait for Gingerbread........
Thanks!
We have MR1, MR2, and MR2.5 but I think only MR1 was an official OTA (dont quote me on it tho since I have been rooted since I got the phone and have never received an OTA). I think the reboot issue has been a problem for a lot of people for the entire time and isnt a new thing. IIRC MR1 caused quite a few reboot issues but not for everyone. I personally ran w/o any reboots until I got to 2.5 and even then I have only ever had 1. Its just what works best for you.
You will be waiting patiently for quite a while for official GB from what I have heard on the boards but you can always try out some of the GB ROMs that we have already.
Beastclaw said:
We have MR1, MR2, and MR2.5 but I think only MR1 was an official OTA (dont quote me on it tho since I have been rooted since I got the phone and have never received an OTA). I think the reboot issue has been a problem for a lot of people for the entire time and isnt a new thing. IIRC MR1 caused quite a few reboot issues but not for everyone. I personally ran w/o any reboots until I got to 2.5 and even then I have only ever had 1. Its just what works best for you.
You will be waiting patiently for quite a while for official GB from what I have heard on the boards but you can always try out some of the GB ROMs that we have already.
Click to expand...
Click to collapse
You are correct Beast there has only been one official OTA. My wife is not rooted but I am
Well I went back to stock because I was gonna try to go to Verizon today and swap it out.....
I find it funny this exactly what I was going to ask today myself. I'm also running bamf remix 1.8, have tried all the radios and even installed bamf 2.0 for GB with the Mr 2.0/2.5 radios. Still got reboots. Now I want to go back to stock and unroot so I can go back to the store and swap it
Just wonder if its worth it, maybe if they let me swap SD cards
I just un-rooted my phone about two days ago. After, I did the OTA update. I hadn't seen any problems until today. I live in a 4G area and work in a (up until Monday) 3G area. Since Monday they have been testing out a 4G tower. I have had 4G until this morning, I just figured that they were still testing it out and had switched it off. Well, about an hour ago I got my first Reboot. When the phone came back up I noticed that the 4G had just came back on. I'm pretty sure that's what triggered my reboot. So in short, as long as they keep the 4G going I don't have any issues.
Just curious is the update worth doing? And if i do it do i go ahead and install the GB bamf rom and radio? or just go back to my current 1.8 remix?
im curious what you guys have your phones overclocked at? I am rooted on the RC3 bamf 3.0 and the only time I have seen reboots is when i had my phone overclocked to high. now that im at 1.42 on the bamf cpu (I disabled my setCPU) and it has been solid.
Is this happening to anybody else? My phone reboots several times a day and I cant seem to pinpoint the cause of the problem. I have tried various kernels and versions of CM7 (running latest RC now). My phone is not overclocked and is not having any heat issues. Does anybody have any ideas on how to fix the problem?
I have not had a single reboot since I put 1.5.2 on my phone. I did not wipe coming from 1.4 but I didn't have any issues on that build either. Have you tried wiping data and cache yet and reinstalling?
Sent from my ADR6400L using XDA Premium App
You mentioned it isn't overclocked, but is it undervolted by your own modding at all? Other than that only thing I can think of are the reboots people were just experiencing in general (most likely due to the handoff between LTE and CDMA).
To answer the two previous comments. First, my phone is not undervolted. Second, I have erased everything and done a fresh install several times. Thirdly, I live in Richmond VA so I don't even have LTE enabled. I just enabled it yesterday and it seemed to decrease the number of reboots today. Yesterday I have about 4-6 while today I only had one. I think that all this began when I switched to the MR2 radio.
Is there a proper way to go from an earlier radio to the current or is it like flashing anything else?
Flashing the radio is pretty much just like anything else. Go into the bootloader and have the radio .zip on SD card named correctly and that's basically it.
You flash radios from hboot.
Pull battery, hold power and vol down
courtesy of my rooted bolt
Ya, that's how I've been flashing my radios. I just don't understand why the Mr2 and 2.5 radios would cause my phone to reboot.
Not too familiar with AOSP Roms, but have you tried the official OTA radio?
courtesy of my rooted bolt
I am a flashaholic. I flash any new rom on my fassy whenever a new one is released. I recently did TSM Res 2.0. I always flash by the book. I made many mistakes as a rookie and I try not to repeat oopsies. All was well and I found the rom to be stable and well put together. The next day I rebooted for an unrelated issue. After that, as the day progressed my data connection fizzled. By the next day I had lost it completely. I flashed back to stock and nothing. Then Superclean, CM7 and still nothing. Called Verizon and got a replacement. My last day with the phone, day 4, my ability to call also went. I called Verizon. I did an activation and had it authenticated. Rebooted phone and ta-da. All was well.
So WTF? Any ideas folks?
I kept the replacement anyways.
Sent from my SCH-I500 using XDA App
A little background, I've run Alien 4 for a few months with no issues whatsoever. About three weeks ago, CM7 (the stable atrix build Ba2TF), and shortly after I Flashed Neutrino 2.1GT (1.3), with the patch and assorted addons.
Within the last 1-2 weeks, my internal speaker began going in and out. I flashed 2.2 EE last week, and still had the speaker issues. In that last week, I've also been virtually unable to connect to a PC in any capacity. It's worked at random a couple of times, but that's it.
I reverted back to CM7 attempting to fix the issues, and no luck (this was before the charging issues).
Yesterday, I flashed Faux's Unified CM7 024_r2, thinking maybe it was just wigging out on me. No luck there, so I reverted back to a stable (with the exception of the speaker issue) restore.
Now, my phone will not charge, except when the demon inside it wants too. I've done a factory restore, manually formatted everything but the SD card via CWM, and restored back to the supposed stable CM7 restore. I've tried Neutrino 2.1 & 2.2, CM7, and am currently downloading the MFBSR stock restore.
If it helps, I'm using Rom Racer's current recovery.
Any thoughts here? I'm still pretty new to all this. Could the overclock to 1.3 (Neutrino 2.1GT) have done some damage? My phone was in an otterbox defender. Is there anyway to tell that you guys can think of?
Dumbass me procrastinated on getting my usual Square Trade insurance, and they've now stopped insuring phones past 60 days of purchase. I've had this one since June.
Sorry for the long windedness. If I missed anything, please let me know.
From a powered off state, when I plug the phone in to the PC, it turns on. I'd think this would mean it's seeing something via the data cable, right?
Anyone?