Related
Hey all... first for the record, I'm a longtime lurker here but not many posts, but I'm also "answerman" over at PPCGeeks and HowardForums, probably close to 1000 posts at those sites so I am definitely not new to this world...
Looking to see if anyone else has had this issue: I went from the stock Alltel WM6 ROM to the 3.27 radio and the progression of DCD's ROMs from 2.0.0 to 2.1.0 to 2.2.1... and every one has the same issue for me: when I leave my 6800 plugged into the wall charger overnight, the next morning it is locked up solid and I have to soft reset to get it back.
I'm guessing this has less to do with DCD's ROM and more to do with the radio, but I am just looking for clarification. Anyone else seeing this?
I don't have much installed... the next step would be to hard reset and see if the problem arises with no programs installed, but I haven't gotten to that yet... all I have installed besides Odyssey Mobile are HTC X-Button 1.5, VistaHide battery meter, AIM (which I haven't even opened yet), Total Commander, Opera Mobile 8.65, and nandHP FreeCell. And I have it checking 4 email accounts via IMAP once an hour. It's fine during the day, the problem arises only when I leave it plugged in overnight.
Otherwise, DCD's ROMs have been fantastic... fast, reliable (other than the above issue) and GPS has worked flawlessly from day 1 for me... I use Odyssey Mobile (nav program that came with my Holux GPSlim 236) and I get a lock within about 60 seconds of starting up Odyssey, no need to "jumpstart" the GPS.
26 views and no responses... apparently I am in the minority...
I'd even like to hear "No, I have not had this problem" from someone... that would be useful...
answerman said:
26 views and no responses... apparently I am in the minority...
I'd even like to hear "No, I have not had this problem" from someone... that would be useful...
Click to expand...
Click to collapse
No, I haven't had that problem. I'm on Verizon though so it might make a difference.
I'm also on Verizon and leave my phone in a charging cradle all night with no problems.
i have the problem, but it seems only if i leave IM+ running overnight, if nothing is running it seems to last fine
Had that problem when I used S2U2.
ok, that would seem to rule out the radio then... that was the answer I was looking for...
I am going to leave it off the charger tonight and see if it happens that way...
[I have a AT&T tilt and more often than not, it is locked up solid in the mornings, whenever i leave it on charging overnight.
Well, the plot thickens... since it had a pretty good charge, I left it unplugged overnight and it was fine this morning after 8 hours of nonuse... so it's not a "lockup during idle" thing. Definitely seems to be related to being plugged in.
Next step is to try a different charger, I guess... weird, because this was never a problem until I reflashed the radio and DCD's ROM, and this is the original OEM charger I'm using so there shouldn't be anything wonky there.
I had this issue with DCD 2.0.0 and 2.1.0, but since 2.2.0 came out, the problem has gone away. I'm now running 2.2.4 and still no problems yet. It only seems to happen if the screen turns off. If you uncheck that setting in the power management, you could avoid the issue.
tavella said:
I had this issue with DCD 2.0.0 and 2.1.0, but since 2.2.0 came out, the problem has gone away. I'm now running 2.2.4 and still no problems yet. It only seems to happen if the screen turns off. If you uncheck that setting in the power management, you could avoid the issue.
Click to expand...
Click to collapse
Isn't the current version 2.2.3?
Edit: Just saw the 2.2.4 version for Sprint. My bad.
Yeah, well I tried that... kinda...
I have my power management settings set to never turn the screen off when it is on external power, and usually I manually put it in standby (screen off) when I charge it, but a couple nights ago I tried leaving the screen on all night and it still did the same thing... so...
tavella said:
I had this issue with DCD 2.0.0 and 2.1.0, but since 2.2.0 came out, the problem has gone away. I'm now running 2.2.4 and still no problems yet. It only seems to happen if the screen turns off. If you uncheck that setting in the power management, you could avoid the issue.
Click to expand...
Click to collapse
i have the issue even when the screen is one (i did have the backlight turning off, that would seem an odd thing to lock it up though)
Isn't the current version 2.2.3?
Click to expand...
Click to collapse
dcd posted a 2.2.4 test for sprint, its in the second post in his thread
i'm still running dcd 2.1.0 here on verizon. i only had the unit lock up overnight once... the first night after reflashing. i had left a wmirc session open and running -- the next morning the unit was locked up solid and needed a soft reset to fix.
since then, i haven't had it do anything wonky while charging overnight at all, but i usually close all apps when it's done for the night and set down to charge.
could still be a radio issue with data connections causing these crashes... not sure. given all the seemingly known issues with radio v3.27, i can't wait for an update to the radio already...
scootle74 said:
could still be a radio issue with data connections causing these crashes... not sure. given all the seemingly known issues with radio v3.27, i can't wait for an update to the radio already...
Click to expand...
Click to collapse
See, that was what I was wondering... the only thing that should be running when it's charging overnight (I'm pretty anal about closing apps when I am not using them) is Messaging to check my email accounts...there are 3 that get checked every 15 minutes via IMAP... I will try disabling the auto send/receive and see if that makes a difference.
I installed 2.2.4 and went to break, came back and my device was locked again. It's hooked to my pc via USB. Not sure if those details help or not. Running Vista Ultimate x64. This didn't appear to happen with 2.2.1 or 2.2.2. Could just be coincidental. Overall, great ROM!
i am having the same, my phone is password protected in the morning when left charging overnight. I am currently using DCD 2.5 but it was also happening using PPCkitchens newest build. After doing a little research it seems to mostly be happening to the Alltel 6800s.
mine usually locks up once or twice during the day, and only when it is in a timed-out/sleep state. I have to push the reset button/hole thing to bring it back, but I have never woken up to it being frozen, but that could be because of my power settings.
Set your screen/power to always stay on when plugged in on external power, but still to time out/off after 1minutes on battery power. You should set it to that, because I let mine charge all night and never wake up with it frozen.
also, when mine does freeze, during the day, the service light is still blinking green, like it still has a signal...i dont get it. you would think that would stop too when it froze. hmm.
it happens to me a few times...seems to happen after a new rom update...but mostly goes away after a few days..i noticed it alot after 3.2.0
i leave it charging and i thinks it just in standby until i push the power button...but its frozen and got to soft reset
i posted about it on this page http://forum.xda-developers.com/showthread.php?t=402920&page=38
My issue is not that the phone is frozen but is actually locked with a password and I have not set any passwords or lock on my phone. I have tried the epst unlock code, and my phone number but it still will not unlock unless I soft reset.
Morning, gentlemen.
I'd like to give you a break down of the 44~ hours I've had this phone as of right now and the troubles I've had with it. I'll preface this post with the fact that I work a corporate IT job and even as I may believe everything posted to be correct, please correct me if I state anything incorrectly. Thanks
I received the HTC Rezound around 3PM EST on Friday. Out of the box, I was unable to active the phone. I was coming from a 3G Droid X via an alternate line upgrade, and I had played with the Droid Bionic and had some issues activating there. I'll chalk up activating issues to needing to activate the 4G SIM card over the phone because of it being a corporate account. After 25 minutes on the phone with our Verizon representative, we were successful in activating the phone. Immediately afterwords, the phone rebooted. I believe that it did because of the PRI programming, but I'm also not terribly familiar with the back-end of the 4G activation.
At 3:30 PM EST it was at 35% out of the box after activation. I figured that I'd let it drain entirely to zero out the battery and charge it to 100% later on that night. After getting home and around 7:30 PM, the phone battery gave up and shut down. I plugged in the phone (HTC charger, HTC cable, surge protected outlet) and at 9:00 stood in front of the phone watching it go from off, to the HTC white boot screen, to the unlock screen where it would be completely frozen, and approx. 30 seconds later, would loop that process again and again until I pulled the battery. I go to pick up the phone and it's very hot. Not uncomfortable just yet, but hotter than any phone since the droid 1 had gotten in my hand. Pulled the battery, let it cool down, and booted to the HTC recovery (power + vol. Down) and wiped the phone. After booting, the battery was only at 14%. Strange since it had been on the charger, but I supposed bootlooping might hinder the ability to charge. After verifying that it was not bootlooping any further and using my old fascinate charger (same voltage, same microUSB connector), I went to bed.
Saturday morning 8AM, the phone was bootlooping again. Pulled the battery, let it boot up afterwords after and it was at 100% battery. Strange. Fast forward to 5PM: Phone has rebooted twice throughout the day maybe around noon and 2PM, but no looping. Battery was at 50%, and at 5:15 PM it begins to bootloop again. Pull battery, turn it back on, battery is at 9%. I plug it into the HTC charger using the HTC cable again to a grounded power strip. Plug it in at 5:30 PM and walk away.
At 7PM, I go to pick up the phone and it's bootlooping again and it is so hot it's literally uncomfortable to hold for more than literally a couple seconds. Immediately unplug it from the cable and pull the battery, also very uncomfortable to hold. I decide that the HTC charger is having many problems, and put it away so I don't use it by accident. I've uploaded a video on my Facebook (http://www.facebook.com/photo.php?v=1661452940302) so that you can see what the screen was doing after it heated up that much. I didn't have any other problems with the phone after one FINAL reboot for last night.
This morning, I placed it on the charger: Same deal of massive overheating and the screen doubling. EDIT: I've also noticed that for the most part, it overheats if it charges past 50%
Simply put: This is a beautiful phone, a wonderful speakerphone, great at texting. But seriously: I haven't seen anything else like ANY of this online anywhere yet. Anyone else seeing issues like these?
Thanks.
Dan Manners
Nope.
Try pulling the battery and putting it back. Do not power up. Connect to charger and let it full charge. Disconnect charger and boot it
If it is super hot during any of that take it back.
DanManners said:
Morning, gentlemen.
I'd like to give you a break down of the 44~ hours I've had this phone as of right now and the troubles I've had with it. I'll preface this post with the fact that I work a corporate IT job and even as I may believe everything posted to be correct, please correct me if I state anything incorrectly. Thanks
I received the HTC Rezound around 3PM EST on Friday. Out of the box, I was unable to active the phone. I was coming from a 3G Droid X via an alternate line upgrade, and I had played with the Droid Bionic and had some issues activating there. I'll chalk up activating issues to needing to activate the 4G SIM card over the phone because of it being a corporate account. After 25 minutes on the phone with our Verizon representative, we were successful in activating the phone. Immediately afterwords, the phone rebooted. I believe that it did because of the PRI programming, but I'm also not terribly familiar with the back-end of the 4G activation.
At 3:30 PM EST it was at 35% out of the box after activation. I figured that I'd let it drain entirely to zero out the battery and charge it to 100% later on that night. After getting home and around 7:30 PM, the phone battery gave up and shut down. I plugged in the phone (HTC charger, HTC cable, surge protected outlet) and at 9:00 stood in front of the phone watching it go from off, to the HTC white boot screen, to the unlock screen where it would be completely frozen, and approx. 30 seconds later, would loop that process again and again until I pulled the battery. I go to pick up the phone and it's very hot. Not uncomfortable just yet, but hotter than any phone since the droid 1 had gotten in my hand. Pulled the battery, let it cool down, and booted to the HTC recovery (power + vol. Down) and wiped the phone. After booting, the battery was only at 14%. Strange since it had been on the charger, but I supposed bootlooping might hinder the ability to charge. After verifying that it was not bootlooping any further and using my old fascinate charger (same voltage, same microUSB connector), I went to bed.
Saturday morning 8AM, the phone was bootlooping again. Pulled the battery, let it boot up afterwords after and it was at 100% battery. Strange. Fast forward to 5PM: Phone has rebooted twice throughout the day maybe around noon and 2PM, but no looping. Battery was at 50%, and at 5:15 PM it begins to bootloop again. Pull battery, turn it back on, battery is at 9%. I plug it into the HTC charger using the HTC cable again to a grounded power strip. Plug it in at 5:30 PM and walk away.
At 7PM, I go to pick up the phone and it's bootlooping again and it is so hot it's literally uncomfortable to hold for more than literally a couple seconds. Immediately unplug it from the cable and pull the battery, also very uncomfortable to hold. I decide that the HTC charger is having many problems, and put it away so I don't use it by accident. I've uploaded a video on my Facebook (http://www.facebook.com/photo.php?v=1661452940302) so that you can see what the screen was doing after it heated up that much. I didn't have any other problems with the phone after one FINAL reboot for last night.
This morning, I placed it on the charger: Same deal of massive overheating and the screen doubling. EDIT: I've also noticed that for the most part, it overheats if it charges past 50%
Simply put: This is a beautiful phone, a wonderful speakerphone, great at texting. But seriously: I haven't seen anything else like ANY of this online anywhere yet. Anyone else seeing issues like these?
Thanks.
Dan Manners
Click to expand...
Click to collapse
I watched that video. I have NEVER seen anything like that and I have seen some weird stuff on my phone trying some weird modifications. (I have gotten massive screen tear and other stuff but that is due to the things I have done).
I would suggest returning the phone and getting a new one. I imagine that one is a lemon. You could try restoring the phone via the RUU in the shipped rom thread in the developement section but I think you should just return that one.
Unless you have messed with it aside from what you have told us (I doubt it though) I would return that one.
Easy
Return it.
My first Incredible did this, and my current incredible is doing this. Something in your phone is causing a thermal overload, which triggers a reboot, which gets only so far in the reboot until the thermal protection loads, it notices it is hot, and triggers a reboot [repeat].
In my case, the hardware radio (on both Dincs) was damaged/defective/finally gave way. 10 seconds on the internet will do this to me.
Return it. Do not diagnose it. Do not follow other peoples recommendations for testing. Return it. You must get rid of a phone like this.
Of course, this is one of my huge fears because I am leaving my Dinc for this phone; and now I am seeing that lemons are in this batch as well.
jdmba said:
Return it.
My first Incredible did this, and my current incredible is doing this. Something in your phone is causing a thermal overload, which triggers a reboot, which gets only so far in the reboot until the thermal protection loads, it notices it is hot, and triggers a reboot [repeat].
In my case, the hardware radio (on both Dincs) was damaged/defective/finally gave way. 10 seconds on the internet will do this to me.
Return it. Do not diagnose it. Do not follow other peoples recommendations for testing. Return it. You must get rid of a phone like this.
Of course, this is one of my huge fears because I am leaving my Dinc for this phone; and now I am seeing that lemons are in this batch as well.
Click to expand...
Click to collapse
Definitely what I'm planning on doing. Debating on whether I want to hold of until tomorrow so I can show my boss though. I usually mess with my droid phones (Alternate roms, overclocking, undervolting, etc) and he always gets annoyed. For once, STRAIGHT OUT OF THE BOX it's acting like this. I suppose it's Karma
DanManners said:
Definitely what I'm planning on doing. Debating on whether I want to hold of until tomorrow so I can show my boss though. I usually mess with my droid phones (Alternate roms, overclocking, undervolting, etc) and he always gets annoyed. For once, STRAIGHT OUT OF THE BOX it's acting like this. I suppose it's Karma
Click to expand...
Click to collapse
Just show him that video haha. That convinced me immediately. If it is really getting that hot there is a real problem and I would be getting it out of my hands ASAP.
you either just got a faulty phone or a faulty battery. as the others are saying, return/exchange it.
I personally got a dead pixel and the touch screen is a tad off(I'll click on a link and it'll think I clicked on the link right above(or below).... not all the time though.
right now I'm just sitting in front of Verizon waiting for them to open.
Mine gets fairly warm, especially when working while being plugged.
My first phone had a problem with the bezel coming apart, but it also ran warmer then the second one I have, it was always warm in my pocket, the new one isn't.
If you guys use LTE OnOff you can turn off the antenna you don't need/use be it CDMA or LTE. It will run cooler and battery life will last longer.
AtLemacks said:
If you guys use LTE OnOff you can turn off the antenna you don't need/use be it CDMA or LTE. It will run cooler and battery life will last longer.
Click to expand...
Click to collapse
I always leave it off, LTE really is overrated. A wonderful nicety, but I don't NEED it.
...
With total and complete respect for the immediately preceding couple of posters, I CANNOT STRESS THIS ENOUGH ... do not use tricks to cool your phone down.
You do not want to wind up on the other side of the 14 days with a phone which otherwise overheats from general use. DO NOT FOLLOW ADVICE SUCH AS TURNING OFF LTE.
Sure, if you have a working phone, and you think that will help your battery, then go for it. If you have thermal issues do NOT use bandaids.
(This has been a public service announcement).
LOL. I'm watching this very closely.
If the device isn't currently overheating turning LTE off isn't going to hurt it, lmao. They wouldn't bake in a feature that is going to make your phone melt down. Now, if you have problems CURRENTLY then you should warranty replace it. But 14 days doesn't have anything to do with it, you can call and warranty your phone anytime in the first year, 2 if you have the extended warranty. So it is NOT bad advice to turn it off if it is of no use to you. Don't scare people into killing their batteries just because they don't currently have an issue.
To the OP: I am currently on my SECOND DEFECTIVE Brand new Rezound.
The first one gave up on having any sort of vibrate function whatsoever (yes, the battery was pulled, factory reset, blah blah). Haptic feedback, softkey vibration, and all vibrations in general were completely dead. I took it back and got a brand new one since it's only 6 DAYS old. It only started having this problem this morning.
Got the new one at about 11AM today, and it starting having the power cycling issue that you're having about an hour ago. The phone is literally 7 HOURS old and wont stay on for more than 30 seconds before it reboots itself. I am VERY disappointed. Now I have to find the time to go in yet AGAIN to Verizon. I was on the phone with the tech and tried battery pulling it and factory data resetting it to no avail. It wouldn't even Factory Data Reset from HBOOT!
Sigh.
voxigenboy said:
you either just got a faulty phone or a faulty battery. as the others are saying, return/exchange it.
I personally got a dead pixel and the touch screen is a tad off(I'll click on a link and it'll think I clicked on the link right above(or below).... not all the time though.
right now I'm just sitting in front of Verizon waiting for them to open.
Click to expand...
Click to collapse
Why don't you go in and calibrate the keyboard if it's off?
OP
I think you should have added a "None of the above" as a selection for your poll. would have a lot more than 2 people.
My first phone and my second phone are set up the same, both factory reset both with LTE on and the second one makes little to no heat when idle, the first was warm all the time.
zeroxg4 said:
To the OP: I am currently on my SECOND DEFECTIVE Brand new Rezound.
The first one gave up on having any sort of vibrate function whatsoever (yes, the battery was pulled, factory reset, blah blah). Haptic feedback, softkey vibration, and all vibrations in general were completely dead. I took it back and got a brand new one since it's only 6 DAYS old. It only started having this problem this morning.
Got the new one at about 11AM today, and it starting having the power cycling issue that you're having about an hour ago. The phone is literally 7 HOURS old and wont stay on for more than 30 seconds before it reboots itself. I am VERY disappointed. Now I have to find the time to go in yet AGAIN to Verizon. I was on the phone with the tech and tried battery pulling it and factory data resetting it to no avail. It wouldn't even Factory Data Reset from HBOOT!
Sigh.
Click to expand...
Click to collapse
I tried to go to Verizon today, but they refused to do anything since it's a corporate account and 48 hours old. I'm really up in the air about whether I'm going to stick with the Rezound or go back to the Droid X.
DanManners said:
I tried to go to Verizon today, but they refused to do anything since it's a corporate account and 48 hours old. I'm really up in the air about whether I'm going to stick with the Rezound or go back to the Droid X.
Click to expand...
Click to collapse
Wow, that's ridiculous. They had no issues whatsoever replacing mine (and the one I'm replacing tomorrow) because it's within the first 14 days of purchase. I guess it works differently for corporate accounts.
Honestly, though.. I can't imagine them saying anything other than "Sorry, we'll give you a new one". How can you be sold a product that is OBVIOUSLY defective (and certainly NOT cheap) and be told that there's nothing that can be done? It just doesn't make any sense to me.
I'm actually pretty upset that I keep having to go get replacements, even though they're new. I've been looking forward to getting this phone for a while and actually would like it to work correctly. It's just disappointing to see that 2/2 have been defective so far. Hopefully it ends there.
zeroxg4 said:
Wow, that's ridiculous. They had no issues whatsoever replacing mine (and the one I'm replacing tomorrow) because it's within the first 14 days of purchase. I guess it works differently for corporate accounts.
Honestly, though.. I can't imagine them saying anything other than "Sorry, we'll give you a new one". How can you be sold a product that is OBVIOUSLY defective (and certainly NOT cheap) and be told that there's nothing that can be done? It just doesn't make any sense to me.
I'm actually pretty upset that I keep having to go get replacements, even though they're new. I've been looking forward to getting this phone for a while and actually would like it to work correctly. It's just disappointing to see that 2/2 have been defective so far. Hopefully it ends there.
Click to expand...
Click to collapse
Corporate allocation and stock is different than the consumer market.
Alright, so this phone is becoming extremely frustrating.
The very first day i got the rezound I had it for literally five hours right from the store and I figured i would restart it to freshen things up after messing around with setting up my home screens.
Upon my phone turning back on, it booted up to the lockscreen... froze... turned itself on and then restarted itself and it LOOPS... it does NOT get past this point it bootloops the process
So I pulled the battery a few times, then did a factory reset in hboot and the problem fixed itself, so I gave it the benefit of the doubt and thought maybe it was just a fluke so i reset everything back up... now three days later... I restarted the phone... upon turning it back on... SAME THING... BOOTLOOPING for no reason
I have never tried to temp root my phone or do anything whatsoever. This is a 100% legit phone but its becoming extremely annoying. Im returning this thing to VZW tonight and exchanging it for another one but im torn between exchanging it for a different rezound or just straight up returning it and waiting for the nexus december 8th to come out.
There have been ALOT of reported problems with this phone from my bootlooping... dead pixels... horrible battery life... etc
Dont reboot it anymore. There is an app in the market called fast reboot.when you need to freshen the phone just push the icon and it wiill get all the free memory in about 10-15 seconds.
Sent from my Galaxy Tab 10.1
im supose to be locked into a phone for the next 2 years that i cant reboot because it bootloops?
I have seen several people with boot-looping issues.
I'm not one of them and I don't think it is rampant with this phone. As for dead pixels and horrible battery life - those issues are even fewer and far between.
I wouldn't say there have been ALOT; probably a normal percentage of definite defective units mixed with people being unfamiliar with "how things work" on a phone like this.
..... my $.02
yeah im returning it at VZW tonight for a new unit... if the second one has any issues at all that have been described on this forum so sorry i gave them two chances... returning and waiting for nexus
You also gotta realize your hearing about a ton of issues with the phone, because only people with issues are posting about it. The other 90% that dont have issues arent posting.
Anytime a new phone comes out about 10% of them are duds with the same problems you are describing. When the nexus comes out their forum will be full of threads about problems with that phone. Read thru the android forums and no matter what the phone, you will see complaints about the phone. i have been reading them for years.
Sent from my Galaxy Tab 10.1
I had the phone for about 7 hours three have been fighting loops. My temporary solution is to disable LTE and put my standard size battery in the device ? I don't know why, but I have a hunch that my specific device may be verry sensitive to heat issues.
I called Verizon and they show the boot cycling a known issue and that it was submitted to HTC.
The phone does not seem overly hot to Me so my hunch could be wrong
Sent from my ADR6425LVW using Tapatalk
Well my first Rez was a dud. It got as hot as 130F at one point! Returned it, now this second one will boot to a certain point then bootlop!! My evo never did this ****!!
Sent from my SCH-I510 using XDA App
Ok here's what I did. I shut down, removed the 4G sim and rebooted. It fully booted with no cell service of course. I went into the LTE switch and set it to CDMA auto. I shut down, re-inserted sim, booted up and it's working. Not sure if all that was necessary, but that's what I did...
Sent from my ADR6425LVW using Tapatalk
Ok phone getting better but loops still persist.I am giving up and getting a replacement in the am. BTW. THE tmo vibrant with stock headsets and voodoo sound 10 blows the beats gimmicks away.
Sent from my ADR6425LVW using Tapatalk
Bootloops = Heat
In my experience, Bootloops are a result of heat. The phone heats up (or the radio heats up), the phone reboots on the thermal warning, but the bootup time is not nearly long enough to cool down a phone that hot, so once the OS (or kernel) loads to the point where it starts checking for thermals, it sees a heat issue, and reboots.
I have this on my DInc which I was hoping to replace with a Rezound because of these bootloops, but of course I am going to have sit and see if this subsides (or what the Nexus people say) because ...
... you are right, you do NOT want a phone for 2 years which bootloops when you use it for 15 minutes. It is hell.
What is causing all the heat on your phone ??
Sent from my HTC
LTE 4G Rezound
deleted
I asked and called Verizon again. I found someone with a little more info.
it seems that an above average amount of devices where sent out with a corrupted OS.
The corrupt Rom is having issues with its signal acquisition and causing issues.
its heating up from consistently trying to cycle thru signal acquisition etc etc.
I kinda believe they have nailed the issue- as we booted up the device with no back cover on,and bam!- a perfect phone that functions without the reboots ( Obviously no signal),but it works.
I have a replacement coming Tuesday.
Hmmm i think mine has something like that. BUT i dont do it so much.
Had the same issue with mine last night. Removed Sim disabled all network services and replaced Sim and it worked when I enabled networks again. Mine has been set to cdma only also. I think it might be an issue when authenticating with Verizon that somehow crashes the phone.
chkn said:
I asked and called Verizon again. I found someone with a little more info.
it seems that an above average amount of devices where sent out with a corrupted OS.
The corrupt Rom is having issues with its signal acquisition and causing issues.
its heating up from consistently trying to cycle thru signal acquisition etc etc.
I kinda believe they have nailed the issue- as we booted up the device with no back cover on,and bam!- a perfect phone that functions without the reboots ( Obviously no signal),but it works.
I have a replacement coming Tuesday.
Click to expand...
Click to collapse
Let's hope that is the problem since I haven't had it and would hate to see it be a hardware problem. That is something that can be fixed with an update. I think phones are getting to thin for their own good. Cases problem don't help either.
For what it is worth, my phone is charging, streaming music, and I'm on the internet with auto brightness on. The temp is reading 100F. When I first got it, I was trying to kill the battery so I streamed Netflix over 4g and it got warm but never rebooted. Hope they figure this out for y'all.
Sent from my ADR6425LVW using Tapatalk
I got stuck bootlooping related to the fb chat widget. As soon as it would load, sense would restart and after 10-20 the phone started rebooting.
Non stop. I got it to boot with battery cover off (no reception).
Cover on, it would restart as soon as the lock screen was up.
Battery pull, no help.
So I did a battery pull, guessed volume down +power and choose factory reset.
No fb chat widget and no issues so far
Sent from my ADR6425LVW using XDA App
struggling radio = heat = reboot = still hot = reboot ...
Same as I currently have on my incredible.
They may be able to do something in software, but it is really hardware. the radio struggling to get a signal is not a software issue.
Sent from my ADR6300 using XDA App
My S-Off DNA is just under 6 months old and the battery, on all roms, lasts less that 6 hours on STANDBY. WiFi/data both on and off makes very little difference, and I tried freezing/uninstalling any apps that were not included in the ROM. So far, this problem has occurred on Hatka, NOS, Flyhalf's CM10.1, and Pio's PAC.
I use a wireless charger intermittently, which I have noticed heats up the phone sometimes. Perhaps that damaged the battery? This problem happened very suddenly. It does not correlate with any flashes, the purchase of the wireless charger, bootloader unlock, or change in location.
At this point I feel as if I should try for a replacement, unless anyone here has an idea for a software issue that's causing the problem (I have not run stock in several months, would going completely back to stock reset something?). Anything offered is appreciated.
noahsark3 said:
My S-Off DNA is just under 6 months old and the battery, on all roms, lasts less that 6 hours on STANDBY. WiFi/data both on and off makes very little difference, and I tried freezing/uninstalling any apps that were not included in the ROM. So far, this problem has occurred on Hatka, NOS, Flyhalf's CM10.1, and Pio's PAC.
I use a wireless charger intermittently, which I have noticed heats up the phone sometimes. Perhaps that damaged the battery? This problem happened very suddenly. It does not correlate with any flashes, the purchase of the wireless charger, bootloader unlock, or change in location.
At this point I feel as if I should try for a replacement, unless anyone here has an idea for a software issue that's causing the problem (I have not run stock in several months, would going completely back to stock reset something?). Anything offered is appreciated.
Click to expand...
Click to collapse
i would go completely back to stock and try charging only via the supplied charger - see if it makes a difference. If it doesn't, you may have a defective handset. Also, check to see what is working in the background and check your deep sleep times. HTH
has this been recent?? my dna battery life sucks too, but not that bad. I'm almost positive it's an issue with the last google play services update they did at i/o....
Sent from my HTC DNA
I have not noticed any crazy battery drain...but I have noticed that Google Now always tells me my Location Services are off, when in fact they are on!? Now that jayochs mentioned it, its probably due to the recent Google Play Services update.
Has anyone started or has had issues with the V10 becoming progressively non-responsive?
My wife and I both have the V10, mine being recently replaced due to what looked like memory corruption as icons started showing as grey blocks randomly even after a restore from my pc. Hers is starting to exhibit multiple of the same issues plus more even after a restore from pc:
Not powering on requiring battery pull
No longer accepting double tap to wake/sleep
Icons starting to become grey blocks
slowness to responses
Phone calls are not coming through at times
Verizon has replaced my phone but the fact that hers is starting to show the exact same issues has me wondering if there is a bigger issue to these phones. My new phone has started to show the issues of double tap not responding, there is not an app that is causing wakelock or draining battery. I don't have unusual apps loaded on either phones and have tried going a few days fully stock and it is still exhibiting the issues.
If there is, is there anyway to get Verizon to move us out of these phones if it continues as I'm not going to have a phone that is going to constantly have issues.
after they replace it 3 times you can generally negotiate a different model.
My family's two V10s are starting to show their age. Okay, my wife's crapped out last week so it is definitely aged. The phone got really hot, drained the battery, and kept rebooting. Then it got locked into an eternal bootloop. The only way I got it to boot was to put it in the freezer. I had connected a cable to it and was able to get most of the data off running the cable out of the freezer to a laptop. I still have some other stuff to recover. Hopefully the freezer trick works again.
But now my V10 is having radio issues. It switches between 4G, 3G, and 1x constantly. I'll be in a location that I know has a 4G signal and pull out my phone only to see 1x. The other day it wouldn't find the GPS signal if it was plugged in. Time to backup my data and see if Vz will replace it.
Sad thing is that I declined the insurance coverage. So once my 1 year warranty is up I'll have to buy a new phone. Easy come, easy go.
You can still add insurance to the lines it's never to late. When one customer service rep says no hang up and call again and it doesn't hurt to play stupid and nice. For some reason they do what you ask if they feel smarter then you and I.
Sent from my XPOSED V10
My v10 started running hotter than normal and my battery drain was more. I replaced the old battery with a new one and the problem seems to have gone away. In my case I think the battery was getting too hot and was making the phone run hot and unresponsive.
Kickin' it on my VS990