Related
Hey everyone, I looked around and didn't find anyone having my particular problem, but If I put this in the wrong place, or someone has already solved it, just let me know. Don't want to waste your time!
I got my DINC the day they came out in stores...the first one my local store sold in fact. It was working great, but I hated the bloatware and the fact that the Bluetooth stack was not up to date...couldn't connect with a new hands free speaker phone I just bought (Parrot mini-kit slim). I had occasional random reboots, but not too many. Once or twice a week maybe.
So when the unrevoked one-click came out I tried it. Worked great.
Then I started trying ROMs. With everything I've tried I get random reboots...a lot of them. Sometimes it reboots once and works fine for a couple hours. Other times, it will loop until I do a battery pull. When it loops it will sometimes make it all the way to the lock screen, sometimes it will only make it to the boot animation, and sometimes it won't get past the white HTC screen.
I've used a couple different nightly builds of CM6, with and without google apps. I've used Skyraider 1.8 and 1.9 with and without sense. I've tried "touch of photons". Same results and activity on all of them.
Last night I gave up and downgraded to unrooted 2.1 with sense...factory fresh. I reformatted my SD card with the phone, reformatted the phone storage, and I've done factory resets. It still isn't working right.
At this point, I'd be happy to get it back to pre-Unrevoked and just wait for the official OTA Froyo which is supposed to come out soon. Rooting and using a stable rom is fine with me too. I just need a phone that works consistently.
Any ideas? I'm pretty desperate.
sounds like you needed to return it and get a new one since it was doing random reboots from the day you bought it.
have you used any of the hydra kernels to try and OC it, the 1.15 OC would cause mine to reboot. a good stable rom that i tried was JagerRom, 1.7.4 is without sense, and chocolate is with sense. don't try the OTA one because that is for people who updated to the OTA leak and im going to assume you aren't one of thoes people. haha
http://incredibleroms.com/roms/jager/
hope this helps
Thanks Stroupified...
The weird thing is that the reboot issue wasn't that big of a deal before I rooted and started flashing roms. It happened, but not enough to be a problem.
Does the camera and camcorder work on Jager?
Does anyone know if there is something that could have gotten messed up with unrevoked or the roms I tried?
Is there another downgrade method I can use? I just installed the PB31IMG.zip you can find in a few places out there...is there a known reliable source for the downgrade zip?
If I can avoid fighting with Verizon on this I'd like to. I'm obviously outside my 30 days, and I don't want to wait a week or 2 or three or more for a new incredible (if I can convince them to get me one). I'm not even sure warranty or Asurion will do anything with this kind of a problem either...I fear I'm stuck with a $500 reboot roulette machine.
re
i have gone through 4 incredibles.
they all exhibited the same rebooting issues... completely stock with NO installed apps.
I have also tested the phones with 2 different batteries and with different sd cards and no sd cards installed.
I had done factory resets.
I get a ****ty cell connection where i live, -100 to -96 db.
Its looking more like a tower issue..
I also have had a reboot issue. I rooted the phone the day I got it and installed a senseless rom. It worked perfect the 1st day then started into a downward spiral of reboots till it went into a full boot loop. I did a nandroid back up of the original rom. No real issues since. Im still rooted and have only had one random reboot in about a week that I know of. I know the first issue was because of the rom but what causes the random reboots. Is it aloss of signal? Im a noob so Im just trying to get some insight.
Im on #2
I got my 2nd Incredible on Friday. Prior one would just get hotter and hotter (possibly due to signal issues) until it would enter a reboot loop. Hoping # 2 fares better.
johnsquared said:
Thanks Stroupified...
The weird thing is that the reboot issue wasn't that big of a deal before I rooted and started flashing roms. It happened, but not enough to be a problem.
Does the camera and camcorder work on Jager?
Click to expand...
Click to collapse
ya everything works in jager. but from what everyone else is saying it seems like it could be the signal (or lack there of) that's causing the reboots. have you tried the hybrid prl? it uses the verizon and altell towers instead of just the verizon ones. i haven't tried it because im in cali and there aren't any altell towers near me, but if your stuck with the phone you might as well give it a shot if you live in the supported areas. good luck man.
Link to PRL thread:
http://forum.xda-developers.com/showthread.php?t=723829
If you don't have problems with signal don't bother with the hybrid prl... it kills your data speeds because it switches you from Verizon data network to Sprints data in most areas. I know in the Carolinas phones randomly reboot a lot because thats Alltel country and phones don't work properly without the hybrid. But down south its mostly Verizon. Out west Texas/Ok is mostly Alltel.
But man honestly - I have the same issue on custom roms. My stock Sense rom does fine though. Sometimes I'll be on a custom rom typing a text and the keyboard just freezes and its over. lol nandroid time to me - I can't take the reboots but hate not having the features of newer software.
re
i have tried the hybrid prl and it did not help my rebooting issues.
i have also tried switching to the the cdma codec to -b the higher quality compression... with no luck in fixing the reboots.
I have also made sure there was not an issue with an app causing it, i have tested mine with a clean / factory reset with absolutely no apps installed.
I have had 100% good luck with the leaked ota update, the one upped the camera to 720p recording as well as a hand full of other fixes, and not once did my incredible reboot or crash.
I'm pretty confident that htc has fixed this issue for me, once they drop the 2.2 update that everybody seems to be speculating will be released in a handful of weeks.
Thanks for the input everyone, and I'm sorry others are having the same problem.
I went by my local Verizon store (actual Verizon store, not a 3rd part dealer) and told them my phone was rebooting repeatedly. They didn't even touch my phone...I was out of there in 5 minutes with a FedEx 2nd Day Air confirmation number for a new handset. And my wallet is intact also. I'm rarely impressed by Verizon's customer service, but this time...man... Between the new handset and the impending 2.2 update, I hope to be in good shape.
Me Too
johnsquared said:
Thanks for the input everyone, and I'm sorry others are having the same problem.
I went by my local Verizon store (actual Verizon store, not a 3rd part dealer) and told them my phone was rebooting repeatedly. They didn't even touch my phone...I was out of there in 5 minutes with a FedEx 2nd Day Air confirmation number for a new handset. And my wallet is intact also. I'm rarely impressed by Verizon's customer service, but this time...man... Between the new handset and the impending 2.2 update, I hope to be in good shape.
Click to expand...
Click to collapse
Same EXACT thing happened with me and telesales. No scripts, no hard reset, no task killer; NOTHING. Said "my phone gets hot and reboots" and they said (last Thurs), let's get you a replacement overnight so you can try the new one out of the weekend. No muss, no fuss. Got here 10:30AM the next day, and my evil super-heating 4-to-13-reboot-try prone phone is going back.
sprintrjm said:
i have gone through 4 incredibles.
they all exhibited the same rebooting issues... completely stock with NO installed apps.
I have also tested the phones with 2 different batteries and with different sd cards and no sd cards installed.
I had done factory resets.
I get a ****ty cell connection where i live, -100 to -96 db.
Its looking more like a tower issue..
Click to expand...
Click to collapse
I don't believe towers/signal would have any effect on shutting down or booting. Basically once you're on a current PRL, you really shouldn't even have to update it. Unless you're having that poor service deal where an Alltell/Vzw hybrid would benefit you.
rhinolow said:
So I went back to 4.0.1 and was getting a steady three bars on my phone
Went to 4.0.2 and am getting a steady 2 bars on 4g
Unlocked, and rooted on 4.0.2, and was getting really sporadic signal behavior, including signal loss
All these readings are from the same location in my home.
Then I went back to 4.0.1 and tested all three conditions and got the same results.
I'm no programmer so I can't say why unlocking/rooting would make a difference, but I believe it's making enough of a difference at this point that I'm going to stay stock and locked at 4.0.2 for now.
You guys that are having a lot of problems, are you unlocked or rooted?
Click to expand...
Click to collapse
Now that it's been a few days..... I want others to chime in on this report (no one answered this question in the original thread).
I was having a ton of issues, thought that VZW did something to make it slightly better (which I still believe they did), but stilll... I have issues, although not as bad as the second 12 hours of ownership.
I had made the call to tech support and was then going to return the phone.... when I got home I brought the device back to stock carrier 4.0.1 ROM floating around). Problems were almost completely gone!?! An hour later, the update came and I was worried about the upgrade screwing the radio that was acting better (not that it was perfect by any means!!). So..... after a little thought, I figured I could always go back to 4.0.1 and/or return it. I let the update do it's thing.
There seems to be zero difference between 4.0.1 and 4.0.2, when it comes to the radio.
I was still scared to do much..... I didn't install any apps while I watched the phone for a few hours. Then only Google's apps... the next day the rest of my apps (w/small exceptions, detailed below). Everything ran smoothly.... including the radio. Now it isn't nearly as good as the DX radio in my last phone, BUT..... at least I wasn't constantly with -120dbm and was able to use the phone, as a phone!
So.... I figured after another day that VZW must have fixed something.
Cool, right? Not sure..... I am stock, unlocked, and unrooted. I am afraid to root the phone..... I can't fathom how root could cause a radio issue, but am wondering how many others might have issue with and without root.
Now.... I am still seeing issues, but not nearly as bad. I'll root the phone tonight to see what happens, but would like others input.
Stock Verizon Nexus here and where I normally get full 4g I get maybe 2-3 3g bars. Most of the time I get zero signal where I at least get 3g.
http://www.anandtech.com/show/5254/investigating-the-galaxy-nexus-lte-signal-issue
droid2andyou said:
http://www.anandtech.com/show/5254/investigating-the-galaxy-nexus-lte-signal-issue
Click to expand...
Click to collapse
Great article. Sure as heck opened my eyes up. Thanks.
Root doesn't touch the radio. All it does it give you admin right over the phone.
-Galaxy Nexus
-Asus Transformer
player911 said:
Root doesn't touch the radio. All it does it give you admin right over the phone.
-Galaxy Nexus
-Asus Transformer
Click to expand...
Click to collapse
Exactly right it must have just been the cell towers by the ops area
I'm currently having issues now before and after root
droid2andyou said:
http://www.anandtech.com/show/5254/investigating-the-galaxy-nexus-lte-signal-issue
Click to expand...
Click to collapse
Just read that earlier today. Lots of great info inside.
The story continues
So, just to follow up. I did return my device for a new GNEX and have not had the same issues. I have been reluctant to root my new phone, but I still don't see any reason why the two would be related. I think I had a bad device. I think there are a substantial number of people that are getting DOA devices, but it doesn't appear to a majority. I'll report back if/when I decide to root and flash anything to my new device.
abendx said:
Now that it's been a few days..... I want others to chime in on this report (no one answered this question in the original thread).
I was having a ton of issues, thought that VZW did something to make it slightly better (which I still believe they did), but stilll... I have issues, although not as bad as the second 12 hours of ownership.
I had made the call to tech support and was then going to return the phone.... when I got home I brought the device back to stock carrier 4.0.1 ROM floating around). Problems were almost completely gone!?! An hour later, the update came and I was worried about the upgrade screwing the radio that was acting better (not that it was perfect by any means!!). So..... after a little thought, I figured I could always go back to 4.0.1 and/or return it. I let the update do it's thing.
There seems to be zero difference between 4.0.1 and 4.0.2, when it comes to the radio.
I was still scared to do much..... I didn't install any apps while I watched the phone for a few hours. Then only Google's apps... the next day the rest of my apps (w/small exceptions, detailed below). Everything ran smoothly.... including the radio. Now it isn't nearly as good as the DX radio in my last phone, BUT..... at least I wasn't constantly with -120dbm and was able to use the phone, as a phone!
So.... I figured after another day that VZW must have fixed something.
Cool, right? Not sure..... I am stock, unlocked, and unrooted. I am afraid to root the phone..... I can't fathom how root could cause a radio issue, but am wondering how many others might have issue with and without root.
Now.... I am still seeing issues, but not nearly as bad. I'll root the phone tonight to see what happens, but would like others input.
Click to expand...
Click to collapse
I have a Galaxy Nexus on Sprint. I got it a couple days before the 4.0.4 update, and for those couple days, it worked great. Calls were coming and going, no browser issues, even the GPS sync'd up in seconds (I heard about the issues so I put it through some testing).
Fast forward a couple days and I get 4.0.4. First thing I notice is my web browsing slowing to a crawl, then eventually, just stops. I would click anything or go anywhere, and the progress bar will barely move and just stay put. This did not happen connected to WiFi, only 3G. I reboot my phone, and all is well for another few hours. I don't always use my phone at all times, so I don't know what causes it. I've had to reboot my phone twice yesterday because of this issue.
The next issue was the GPS. I was going somewhere with my wife and figured GPS'ing an address wouldn't be a problem. Well, after about 3 minutes I figured it was like the browsing issue and rebooted the phone hoping it would work again. Nope. We loaded the address up in my wife's Samsung Replenish and were on our way. The whole time my phone was trying to get a GPS lock after a fresh reboot. I even threw my phone on the dashboard so it had a clear view of the sky. The GPS never did sync after the 15 minutes or so it took to get there.
Today, I just discovered ANOTHER issue! I was talking on the phone to my doctor's office, when I heard a few clicks, then it hung up. I thought it was my doctor's office that tried to transfer me and goofed up. I try to call back and after a few rings, I get call cannot be completed as dialed. Still, I thought it was their end. I call again and the recording comes up and plays for about 5 seconds, then cuts out again. So I finally call on a landline and all was well. After I was off the phone, another call came in to my phone and I answered it after the second ring, and it cut out immediately. My wife tried calling later after that, with the same results. After calling again, I was able to hear her after about 5 seconds (I waited longer than that last time).
I'm coming from an EVO 3D (EVO 4G before that) and it had it's quirks, but at least I could hold a conversation and use the web browser reliably. Being basically a vanilla Google Android handset, I had high hopes that all my worries and woes would go away. Now? After being pro-Android since my Samsung Moment, I'm starting to think if I should get a damn iPhone. As much as I dislike Apple and what it stands for, at least their phones "just work".
Anybody have anything I can or should try? Should I just toss this phone on the shelf until Google figures out what they're doing with this handset?
sounds like sprint in your area is having problems.
i doubt it would matter if you had a iphone or not.
My wife isn't having ANY problems with her old PoS Replenish. A lot of friends of mine have Sprint and nobody is having problems that I've heard. As soon as I reboot it when I have browser problems, it works great again, until later.
Flash a custom rom.
Or if you don't want to have a custom rom then flash the factory image.
Maybe something went a bit arse-ways with the ota.
that shouldn't be happening, its not normal, 4.0.4 made the gnex better than it already was!
I did a factory reset and the first call I made was dropped. Guess I'll put a custom rom on it... I shouldn't have to though
might something with the radio if everyone else around is not having problems with sprint. factory reset is not the same as reflashing the 4.0.4 images. try and reflash the stock 4.0.4 images.
I'm on my second device, sprint swapped mine out because my data was just crawling, and I came from T-Mobile and they don't have fast 3G and it felt like I just switched to Dial-Up. They updated the device in-store to 4.0.4 and it was fine yesterday and this morning Pandora kept stopping and buffering. When I got to work I rebooted and ran a speed test and I was getting 1400-1700kbps and sub 400ms ping, which IMHO good considering I don't get great reception in our datacenter. Now 4 hours later I'm down to 100-330kbps and ping of 1000ms plus... even after reboot...
Probably Sprint-version-specific problem or hardware problem of your phone.
I use a GSM Nexus on tmobile and I know people that have the Verizon version. Everyone noticed significant improvement after going to 4.0.4.
Hi all.
I just picked up my (second) Galaxy Nexus today and have been having some severe 4G issues with the Verizon Wireless LTE version. When I brought the phone home, my first action was to put Jelly Bean on the device. I used Muzzy's 4.1.1 JB ROM and everything loaded in fine. When I booted into the ROM and began setting everything up, I noticed that my 4G connection was fading in and out and wouldn't hold for more than two minutes at a time. After wiping everything and re-flashing the ROM, it was still giving me trouble.
I just re-locked my bootloader and axed my root access and reloaded the stock 4.0.4 build that I left the store with, and I'm still having 4G issues. Mike's ROM doesn't change any radio settings, so I'm confused as to why this is happening. Did I get a lemon from the store and should I try to get a replacement?
I picked up a new (free) g-nex from best buy to replace a phone on a secondary line. I'd been selling the wife on the amazingness of the g-nex (i love mine), but of course, it doesnt work right for her, and it has the pulsing 4g/no-g signal problem (if yours is like ours, check battery stats and you can see the 4g/signal drop on/off...like candy stripes with all the red).
I've read extensively, and some insist this is a bad firmware flash that Vzw knows about and a fix is in the works, others say hardware and there is no fix other than a new device. I'm taking it in since I'm still in the 14 day window (rather than risk it) - suggest you do the same?
What could possibly poison an Epic 4G's system speed across the stock ROM and 2 custom ROMs?
Like this...
I'm on my second Epic 4G, got a used one off eBay about a month ago when the screen on my first one died.
On my first one, I rooted it, upgraded to Clean GB, then eventually moved it to cm-10.1.3.1.
The used one came stock, but ran extremely slowly. No problem - I've seen that happen before with my old phone (I call it sloth mode) and knew that installing a new ROM would resolve it. Just to be conservative, I bumped it up along the same path I did before, Clean GB, then cm-10-1.3.1.
Here's the thing. After installing a new ROM, both phones would operate normally. But no matter which ROM ran on the old phone and the replacement, *eventually* it would slip back into sloth mode. I don't mean sluggish, I mean crawling, even during the bootup animation. Even the CWM recovery menu was sluggish.
When I ran Clean GB on the replacement phone, I didn't add more than 2 or 3 apps to it after installing. But it still fell back to sloth mode after about a week of use. After installing cm-10.1.3.1, it only lasted a 3-4 days before sloth mode returned.
Before changing ROMs, I routinely did a factory reset, cleared cache and Dalvik cache.
Of course a virus is a possibilty, but having security apps installed and running didn't seem to make any difference. Could this be a rootkit-class issue?
DeafScribe said:
What could possibly poison an Epic 4G's system speed across the stock ROM and 2 custom ROMs?
Like this...
I'm on my second Epic 4G, got a used one off eBay about a month ago when the screen on my first one died.
On my first one, I rooted it, upgraded to Clean GB, then eventually moved it to cm-10.1.3.1.
The used one came stock, but ran extremely slowly. No problem - I've seen that happen before with my old phone (I call it sloth mode) and knew that installing a new ROM would resolve it. Just to be conservative, I bumped it up along the same path I did before, Clean GB, then cm-10-1.3.1.
Here's the thing. After installing a new ROM, both phones would operate normally. But no matter which ROM ran on the old phone and the replacement, *eventually* it would slip back into sloth mode. I don't mean sluggish, I mean crawling, even during the bootup animation. Even the CWM recovery menu was sluggish.
When I ran Clean GB on the replacement phone, I didn't add more than 2 or 3 apps to it after installing. But it still fell back to sloth mode after about a week of use. After installing cm-10.1.3.1, it only lasted a 3-4 days before sloth mode returned.
Before changing ROMs, I routinely did a factory reset, cleared cache and Dalvik cache.
Of course a virus is a possibilty, but having security apps installed and running didn't seem to make any difference. Could this be a rootkit-class issue?
Click to expand...
Click to collapse
Could it be a failing processor? I had one that went into that mode and never came back...no matter what it would take 20 times longer to boot...boot animation was like beyond slow motion. Best thing to do at this point is to just odin stock and leave it that way for a week...no extra apps or restore and see how it does.
Worth a try...
KennyG123 said:
Could it be a failing processor? I had one that went into that mode and never came back...no matter what it would take 20 times longer to boot...boot animation was like beyond slow motion. Best thing to do at this point is to just odin stock and leave it that way for a week...no extra apps or restore and see how it does.
Click to expand...
Click to collapse
Yeah, it's worth a try. I've also wondered if I slipped up and installed a version of Clean GB or cm-10-1.3.1 that jumped betweeen MTD and BML file formats. I know it could cause problems, but I don't know if it could cause the specifc trouble I had.
Phone's been parked in a drawer for a month since I posted the question. Will odin back to stock and see how it works out.
DeafScribe said:
Yeah, it's worth a try. I've also wondered if I slipped up and installed a version of Clean GB or cm-10-1.3.1 that jumped betweeen MTD and BML file formats. I know it could cause problems, but I don't know if it could cause the specifc trouble I had.
Phone's been parked in a drawer for a month since I posted the question. Will odin back to stock and see how it works out.
Click to expand...
Click to collapse
I just hooked one of my old ones up to freedompop through the BYOD program. Nice to see the old girl getting use at least as an emergency phone.