This is my second Rezound (I got this as a replacement from Verizon). Everything has been working fine for the past 2 months, but recently the screen won't turn on at random times. The screen seems to get stuck in the off mode and I have to do a battery pull to get it on again. Everything else is working when this happens, like I can hear people calling and hear emails coming in, but I can't do much without the screen! I noticed that it happens often when I'm in phone calls... the proximity sensor won't work after the first time I hold it to my head, the screen just goes off and then stays off. Sometimes (rarely) the screen will turn on when I press the power button, but then turn off as soon as the screen is touched (which makes me want to break the phone).
I hope this makes sense. Any ideas from anyone or I am on to my third replacement phone? Will they even replace my phone again? I bought it back in December.
They will replace it again, and it does sound like a hardware issue.
Sounds like you need a replacement
-- Sent from my TouchPad using Communities
happened on my incredible on a few custom roms, and then it happened on my rezound stock not rooted too. it's an HTC issue, probably.
had the exact same problem on my rezound. busted proximity sensor. Verizon replaced it with no hassles.
Thanks for all the input so far people! I'll be getting in touch with Verizon.
I got my new replacement Rezound today and now have a new problem where the phone will not allow data connections. I finally got Verizon to let me switch to a different phone. This will be my first non HTC phone since 2004, starting with the i-mate JAM. I am so glad to be done with the Rezound finally.
damn sounds like u have bad luck with thus phone
Sent from my ADR6425LVW using xda premium
I was having this problem consistently too with both GB and ICS when I was using custom kernels. So far, only the 2 most recent 3.0 ICS leak kernels have stabilized the problem to the point where I haven't had a reboot or freeze in a couple weeks.
Related
Hey guys, hope you can help with an issue I'm having with my Eris. A while back I dropped it in a parking lot and the screen broke. I upgraded to a Droid, but I got the screen fixed so my wife could have the phone. Everything seems to be working great, except for one problem. When you make a call, the screen goes to sleep as soon as you press the call button. When this happens, none of the buttons wake the screen up or end the call. The phone will wake up for around a second if you cover the light sensor, then uncover it, letting you end the call and then the phone is back to normal. I tried using Shakeawake and Screebl, neither worked.
I tried several different ROMs to see if it was just a weird quirk, but that didn't help. Currently running Jcase's Plain Jane with a mild overclock (710). Is there a way I can prevent the screen from sleeping? Seems easier than trying to get it to wake up. Seems like I remember a ROM that didn't sleep during calls, Espresso maybe?
If anyone can help or point me in the right direction, I'd appreciate it. Gladtm see the Eris community still going strong, things had gotten a little ugly when I left. Sorry if my post ran a little long.
Sent from my Droid using XDA App
Case?
Do you have a protective case on the phone? I had the same problem with my Eris after putting a case on it. The case interfered with the sensor on the top left of the phone.
There are a couple of things to try that I can think of off of the top of my head. One, under Settings > Call Settings > there should be a box to check to keep the screen on longer during the call. The other is to try pushing the trackball in and at the same time volume down. Surely not the most convenient way, but more so than not being able to not hang up a call or whatever. I honestly had this issue and a couple of other small problems that I ended up getting a refurb. One other thing that you could try before that is doing a nandroid back up and installing a Froyo based rom. I feel that it might be a 2.1 issue for some phones. I'm not sure why, but computers/phones can be finicky sometimes. Hope this helps!
it has to be a hardware issue since it started after the phone was dropped and across several different roms. i would see vzw about getting a refurb replacement. unroot it, put it back to stock and get a new one.
I did the same thing, dropped my eris off of the moving truck, and cracked the screen, I had been looking for something to fix that issue for quite a while, recently I installed Tazz Froyo v.4 and enabled the Settings => Call Settings => Keep Screen Awake function, ever since I have enabled that it hasn't locked up on me yet *knock on wood* Good Luck
Thanks for the replies everybody. I'll try the track ball trick, then installing Froyo tonight and see if that helps. I hadn't even looked at Froyo ROMs since I came back to XDA; when I left there was only one and it really couldn't even be called functional at the time. Glad the Eris is getting Froyo goodness too.
I do agree its probably a hardware issue, especially since when my screen was broken everything still worked fine, just couldn't see the display very well and it was ugly as sin. But looking at when this happens, I think if I can keep the phone from ever telling the screen to sleep, it would probably solve the problem.
If all else fails I'll try to get a refurb. Thanks again, and if anyone thinks of anything else, post it up.
Sent from my Droid using XDA App
Forgot to mention, the really weird thing is it only does it every other call. Thought that was pretty strange.
Sent from my Droid using XDA App
So i just upgraded to Tazz V5 and it started freezing again, from my research the problem that's causing the screen to lock up is the proximity sensor, when you cracked your screen it messed that up, my hunch is that in Tazz V4 that the proximity sensor isn't supported, so as a byproduct it doesn't turn the screen off for us Just my observation, let me know what you guys think
I've had the Photon for a couple days now and have noticed that it will randomly shut off while in my pocket. Also will not power back on without a battery pull.
Other things are random restarts I've been getting quite often.
During some phone calls when you make the phone call, I hear dead air and no ringing, but the other party gets the phone call but also hears dead air. I've fixed with a restart but can get annoying quickly.
Yesterday the phone was almost red hot from being idle in my pocket, only noticed because of the heat increase.
Has anyone had any of these problems or do I have a dud?
The only problem I've experienced had been one random reset while using Dolphin HD. Perhaps a rogue update is killing your battery.
Sent from my MB855 using XDA Premium App
I've had a few of the same problems, my best guess at the moment is there's some bugs to be worked out. As for the random restarts....for me it was caused by an app, it was an HD wallpaper app that was poorly written. Still trying to find a cause for the dead air while calling.
Hmm, haven't had any of these happen. Though this is day 3 of me having it though
Sent from my MB855 using XDA Premium App
naps79 said:
I've had the Photon for a couple days now and have noticed that it will randomly shut off while in my pocket. Also will not power back on without a battery pull.
Other things are random restarts I've been getting quite often.
During some phone calls when you make the phone call, I hear dead air and no ringing, but the other party gets the phone call but also hears dead air. I've fixed with a restart but can get annoying quickly.
Yesterday the phone was almost red hot from being idle in my pocket, only noticed because of the heat increase.
Has anyone had any of these problems or do I have a dud?
Click to expand...
Click to collapse
Been having this problem with my EVO 4G for the past few days. Picked up the Photon last night- no issues (knock on wood).
fordhighlander said:
I've had a few of the same problems, my best guess at the moment is there's some bugs to be worked out. As for the random restarts....for me it was caused by an app, it was an HD wallpaper app that was poorly written. Still trying to find a cause for the dead air while calling.
Click to expand...
Click to collapse
Same issue here with the dead air.. its really annoying!
Sent from my MB855 using XDA Premium App
I'm glad that I'm not the only one having some problems. I'm sure it's a software tweak that probably that needs to be done.
Just an FYI, I had gotten the Photon prior to launch at a Motorola Event. Now when they gave us the phones they said we had to do an update. I did that and it does a factory reset. I'm hoping that if there is an update it won't force a factory reset.
naps79 said:
I've had the Photon for a couple days now and have noticed that it will randomly shut off while in my pocket. Also will not power back on without a battery pull.
Other things are random restarts I've been getting quite often.
During some phone calls when you make the phone call, I hear dead air and no ringing, but the other party gets the phone call but also hears dead air. I've fixed with a restart but can get annoying quickly.
Yesterday the phone was almost red hot from being idle in my pocket, only noticed because of the heat increase.
Has anyone had any of these problems or do I have a dud?
Click to expand...
Click to collapse
Other than the random restarts I've experienced the exact same thing. Phone was red hot, dead air where I can't hear the caller and they can't hear me and the lockups where I had to pull the battery. Have you taken it back or called Sprint? Mine is only a day old so I think I'm just going to return or exchange it. I'm not doing repaired after just a day.
jorjitoc said:
Other than the random restarts I've experienced the exact same thing. Phone was red hot, dead air where I can't hear the caller and they can't hear me and the lockups where I had to pull the battery. Have you taken it back or called Sprint? Mine is only a day old so I think I'm just going to return or exchange it. I'm not doing repaired after just a day.
Click to expand...
Click to collapse
I'm torn I might just take it back to Sprint. I guess I believe it's a software issue instead of hardware. Of course I have no way to verify that yet. Maybe I'll try to root as I have the HD Dock. Hopefully the Devs can figure something out.
Wow, phone sure react different. My son and I both had the 3d. He has never had a problem with his. Mine had lots of fc's, and 1 reboot. Now I have the Photon, and these problems are listed, and I haven't had any. Only had it for 1 day though. Knock on wood.
I posted this info in a different thread. Thought I would sharte here as well too.
http://forum.xda-developers.com/showpost.php?p=16561154&postcount=20
hi, just wondering does anyone found a solution to this ?
i just bough a brand new photon and its been behaving like that.
it doesn't wake when i presss the power button, o i have to do battery pull
and thats annoying.
1 day it can be working 100% normal
and the next day it can turn off by it self like 10 times.
so please any advice on what should i do ?
cause I'm overseas and i don't think returning the phone is an option for me .
thank you.
Yea me to started around the 1st for me.
Unlimited if you can get it.......
Stock, Rooted with Torpedo, and [CWM] Bootstrap Recovery. Rain Drop Mod with Five Pt. Touch. ADWLauncherEX with QQ's Lock Screen.
I fixed my wife's photon
just sharing...
me and my wife bought the motorola photon last year and had a 2-yr contract with sprint...
my phone was great but my wife's phone keeps rebooting...
so after 2 days i decided to root our phones and successfully rooted it...
but still her phone has random reboots..and it got worse after few months...
then i gave up... untill i tried M.O.F rom for locked bootloader (credits goes to mof9336)
http://forum.xda-developers.com/showthread.php?t=1648297
now my wife's photon has not rebooted for a week...
did anyone tried it? we are on a locked bootloader..
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
I bought a thunderbolt off of a friend for $50. When I got it, it wouldn't start up, but I got it running. I still had sporadic issues with the touch screen though. I thought it was a software problem since it would work like normal when I got past the lock screen.
One time I started the TB up while it was hooked up to my laptop and had no problems at all with the screen. I decided to try out the headphone jack and one of the earbuds had a weird buzzing sound. I unplugged the USB cord and the buzzing changed. When I touched the screen it would change again and all the sudden the screen stopped working.
I decided to go ahead and put the phone on my account and see if I could do a warranty replacement (I had already contacted to confirm this would be possible) but now it's working fine after a restart. 2 days and no trouble. My question is do you think it's a hardware issue (maybe a short in the digitizer?) or a software problem? The phone is in very nearly mint with no damage and sat in a drawer for 8 months. One earbud still buzzes on occasion, but only for a minute. I'm not sure what the problem is now.
Sent from my ADR6400L using Tapatalk 2
Well my phone is still working, but I've discovered something. When I installed the clarus widget app, it showed the battery health as "over voltage" any suggestions on how I can check the health of my battery? The stock romantic doesn't show that info and I want to confirm what the clarus widget is showing.
Sent from my ADR6400L using Tapatalk 2
Battery calibrator? It shows the actual voltage
Sent from my ADR6400L using Tapatalk 2
I'm on my second TB, and getting my 3rd in the mail Tuesday. I had touch screen issues with both. Never rooted either of them. If I get issues with the 3rd one, I'm going to tell them I need a different device already.
Issues I've been having are deadspots on the screen where I don't get any functionality out of those spots.
Hey guys, I've been having a weird issue for the past week now. On Mean Bean 3.09 every phone call I take or make ends up rebooting, usually within a minute of the call going through. Now, I also noticed that my proximity sensor now longer works and the screen remains ON during the calls no matter how close my face is to the sensor/screen (I am not a ghost).
I have tried completely wiping to factory multiple times, and flashing different roms, including basic rooted stock roms. All now have this same issue where my proximity sensor does nothing (screen stays on unless I hit power button during call) and it reboots the phone during all my phone calls. Anyone have any idea what's going on, and suggestions on how to fix? Thanks!
You may want to look at the firmware version you are running.
Just an idea, never had that issue before.
Captain has a very detailed list of them here
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
I guess at this point it cant hurt.
So, seems it was a hardware failure. Took it into sprint and they had to order a replacement phone, there goes 50 bucks =/
At least its fixed
Sent from my EVO using xda premium