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
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.
Just bought a second hand GS3 from ebay, the screen had a small crack but otherwise was meant to be OK. I put Foxhound ROM on (I'm just used to having to upgrade the rom) and am finding that the sound will work fine after a restart, but then, after it has gone to sleep all sound will stop working.
I've tried clean wipes/formats etc. and also checked all relevant settings I could find (including turn off all sound in accessibility, what an odd option).
I've tried two ROMs and three kernels.
I've tried searching google and xda for hours but haven't found anything that wasn't related to the headphone port; this affects both speaker and headphone, although when the headphone is in and the sound has died I can hear some strange static noises when it's meant to play sound, could be interference or a clue.
I've dismantled the phone and inspected for damage, nothing obvious. While dismantled I tried applying pressure to the speaker flex cable and various other IC's to no effect.
It really seems like a software glitch since it only happens when the device goes to sleep;
You can turn the screen off and unlock within 3 seconds and it will be OK.
If you wait 5 seconds with the screen off - boom, no sound.
Any ideas? Is there some deep idle sleep setting that kicks in after 3 seconds I can disable or some way to log audio errors or... something?
Thanks
defroster said:
Just bought a second hand GS3 from ebay, the screen had a small crack but otherwise was meant to be OK. I put Foxhound ROM on (I'm just used to having to upgrade the rom) and am finding tht the sound will work fine after a restart, but then, perhaps after it has gone to sleep once or twice (never more than a few minutes unless I'm plying a game, in which case it stays on just fine) the sound, all sound, will stop working.
I've tried clean wipes/formats etc. and also checked all relevant settings I could find (including turn off all sound in accessibility, what an odd option).
Any ideas?
Click to expand...
Click to collapse
May Be The Phone Was Damaged, Try Stock ROM
i'm downloading a different ROM now but it takes hours (rural australian phone lines...)
same result with a different ROM =/ I've fixed many phones, computers etc before but not sure what to investigate here, guess i'll dismantle it and see.
A second rom and kernel same result.
Seems to lose sound as soon as it goes to sleep (screen off), really seems like a software problem but can't find any other reports on this phone similar.
Help!
Anyone?
Looks like a software problem but can't say where you can look.. If kernel is not the cause..
Maybe hardware after all..
sent from here, there, somewhere!!
The only way I can imagine it being hardware is if it's heating an audio ic during boot to make a connection and then when sleeping it cools and the connection is lost. It's a long shot but if it's software why is it not happening to anyone else? No weird software installed or anything.
defroster said:
The only way I can imagine it being hardware is if it's heating an audio ic during boot to make a connection and then when sleeping it cools and the connection is lost. It's a long shot but if it's software why is it not happening to anyone else? No weird software installed or anything.
Click to expand...
Click to collapse
Does the sound still work through headphones (after the sound stops working)?
Sent from my GT-I9300 using Tapatalk 2
no, it doesn't seem to be headphone jack related.
the only thing I changed (aside from the rom) that I can think of that MAY have done something is some network setting for my carrier (vodafone .au) - there was an option in foxhound rom or something, but I can't for the life of me remember what it was called, I googled it at the time to see what it was but have since lost the browser history, it was some feature of the phone network that stops sending requests to the network when the phone is sleeping or some such... I'm really grasping at straws there though.
can't seem to find a stock rom for Australia either?
updated OP with more info, sorry for the bump, i'll let this die if no-one's got any ideas.
defroster said:
no, it doesn't seem to be headphone jack related.
the only thing I changed (aside from the rom) that I can think of that MAY have done something is some network setting for my carrier (vodafone .au) - there was an option in foxhound rom or something, but I can't for the life of me remember what it was called, I googled it at the time to see what it was but have since lost the browser history, it was some feature of the phone network that stops sending requests to the network when the phone is sleeping or some such... I'm really grasping at straws there though.
Click to expand...
Click to collapse
I think you are talking about fast dormancy toggle.. But I do not think it will cause any problems.. Also as you have already done factory resets an app should not be a problem..
I can only think of hardware faults..
sent from here, there, somewhere!!
yes i just finally remembered it and tried disabling, you're right, no difference.
I'm having trouble figuring out how hardware could be the culprit though, since it's triggered by the screen off for more than 3 seconds, there's something in software causing it.. but you're right, why does it persist over a wipe then? argh!
Downloaded stock rom, problem remains
My issue has been happening for awhile but its gotten a lot worse lately.
My screen, when on, will randomly start "touching" places. When this happens, it appears as if a phantom finger is pressing various things and it is causing a lot of issues. Also when this happens, the 4 buttons on the bottom stop responding. i have to use the power switch to turn the screen off and then back on again.
any thoughts on how I might be able to fix this?
eldoon said:
My issue has been happening for awhile but its gotten a lot worse lately.
My screen, when on, will randomly start "touching" places. When this happens, it appears as if a phantom finger is pressing various things and it is causing a lot of issues. Also when this happens, the 4 buttons on the bottom stop responding. i have to use the power switch to turn the screen off and then back on again.
any thoughts on how I might be able to fix this?
Click to expand...
Click to collapse
Are you rooted/flashed a rom? If you are you should definitely wipe everything a few times and flash a new rom. If you aren't I would perform a factory reset.
adamsaur said:
Are you rooted/flashed a rom? If you are you should definitely wipe everything a few times and flash a new rom. If you aren't I would perform a factory reset.
Click to expand...
Click to collapse
It has happened across multiple roms. I will try again though.
If nothing else works, try SGS Screen Booster. My Rez has been having the same problem recently, and it's seemed to help quite a bit.
The right below the status bar, there seems to be a gap with what is and what isn't working properly, so I set everything to the max and lowered the response time to be as quick as possible.
Sent from my ADR6425LVW using xda app-developers app
Happens to me also. Do you have a screen protector maybe? That is what I always thought my problem was.
Certain chargers or USB cords with grounding issues can cause these problems. Does it only happen when it's plugged in?
I had one were it would cause the same issue when plugged into the laptop, but only while the laptop was plugged into the wall.
zourn said:
Certain chargers or USB cords with grounding issues can cause these problems. Does it only happen when it's plugged in?
I had one were it would cause the same issue when plugged into the laptop, but only while the laptop was plugged into the wall.
Click to expand...
Click to collapse
+1 for this answer. had it happen when i bought a cheap cable from HK. Went with OEM, and now i dont have this problem
I have seen this charger issue as well
Sent from my ADR6425LVW using Tapatalk 2
The title of this thread would have me more excited if "rezound" was a young hot female.
sorry for the absence.
it happens I'd the phone is plugged in or not.
no screen protector or case on the phone either.
I have done a full wipe multiple times now and different roms as well.
Sent from my ADR6425LVW using xda premium
Eh, mine does this as well. It's been happening more often in the colder weather I get into. So I just turn off the screen and let it sit in my pocket for a minute so the screen can warm up, and then it works. I swear, these Asurion replacements suck.
I'm having the same issues with my Rezound. I also have a lot of issues with the soft keys not working now ( Far more often than the random screen touch issue ). They won't respond at all or they will start randomly start clicking. I also notice that when they stop responding usually I can put the phone to sleep, then wake it back up right away and they will start working about 10-15 seconds later. Even when they are working I often have to hit them multiple times before it takes. This happened with the stock rom. It started happening shortly after I received the most recent OTA update, however I assume that is simply a coincidence and nothing to do with the update. I flashed the phone recently with CM10 hoping it was an issue with the ROM itself but the problem persists. This is a shame too because other than the screen issue it seems that CM10 would have given the phone a new life as it looks and runs so smooth on the hardware. I highly doubt I will ever buy an HTC again, we have had two of them and they both start having hardware issues much faster than they should for what they cost.
Im using the unofficial cm10.1 build with no mods. i went through and wiped everything twice. cache, system, boot, battery settings, rotation settings. i flashed the latest at the time (build from 4/3/13) and now my phone is working properly again. no more hanging up on people caue it preses by itself, no more emergency dialing.
hope that helps anyone who might have the same issue.
Sent from my Transformer Prime TF201 using xda premium
Okay first of all, I've scoured not only XDA but even Google for an answer to this problem to no avail. So if anyone has/knows of any thread that has the answer, please kindly reply or notify me so we can have this thread removed.
Here goes,
I'm experiencing a very unique (afaik) problem with my Galaxy S3. This started a few months back, when the phone started getting random reboots/ freezes and terrible battery life on ANY ROM/Kernel. I've tried CM, SlimBean/Kat, and even Stock and nothing worked. Finally I figured maybe the battery was shot. So a few days ago I went and got a new battery, and that's when it got weird.
I used the latest SlimKat after replacing the battery and after powering on the device, EVERYTHING seems perfect. It's really fast and responsive, battery drain while screen is on is extremely acceptable, things worked like new again. UNTIL I switched off the display, after 5 mins, I pulled out the phone and it was switched off. At first I thought maybe the initial charge wore down so I charged the phone to full, then powered it on. Again, everything went smoothly BUT, after switching off the display for more than 1 minute, the phone shuts off automatically.
I switched to the latest stock 4.3 ROM and restored everything to factory settings and it seems to have helped at first. As usual, everything is fast and battery doesn't drain so much BUT, after putting the phone to sleep, it takes 5-10 seconds for the screen to wake after pressing the power button, and even if it wakes up, it becomes EXTREMELY laggy and often freezes requiring a reboot. As usual, after a fresh reboot, everything becomes awesome again until I have to turn the display off for more than a minute.
I've tried everything, even installing an app that prevents deep sleep but the problem persists. It improved a little after flashing stock rom and reverting everything back so I'm really hoping this isn't a hardware issue. Is there maybe something else I can try, settings/software-wise? The phone is almost 2 years old and is already out of warranty.
I'm hoping it's not the sleep of death thing because the phone isn't exactly bricked. I can still use it for as long as it doesnt have to go into deep sleep (I turn it off before putting in my pocket and turn it on again when I need to browse/use the camera which is all it's good for in its current state.)
Also, the symptoms don't really fit the usual "Sleep of Death/Brickbug" Symptoms I've read about.
Hey, I remember having a similar problem. I formatted both my internal sd and external sd. Haven't had any problems ever since. Hope this helps.
Sent from my SM-N9005 using XDA Free mobile app
Already tried that. I did full wipes/formats on all my installs. I even tried not having an external SD inserted for the Odin installs. I tried not installing any app on the phone and it still gets messed up after going to sleep. As fresh installed AOSP or Pure Stock ROM. Odin flashes no problem so I'm really hoping nothing hardware-wise is messed up. I had to re-flash PIT after getting a new battery though, could I have messed something up there that would lead to this?
There is an app for that deep sleep syndrome, it's on playstore its calles brick check or something like that, if you cant find just google it.
And I dont think that could be software problem, BUT depends on what apps you used, flashes you made.
Hope it hepls
Well, i don't think its deith break, but i had the same essue with unofficial 4.3 and then at official 4.3 it worked well,
it may be a break in the motherboard or something.. as u tried every rome avilable it couldn't be softwear thing..
the app for emmc firmware is called 'eMMC check', you can find it on playstore
edit: does your phone heat up? or battery? did your display ever turned blue when waking up from sleep?
it could be also a short with your display/motherboard or other connectors or battery connector... and the protection kicks in
if you're good with tools and phone is not under warranty, you could disassemble it and reassemble/reseat the connectors
or, could be the power button shorting, if you decide to open it, examine the power button
@Eibram did you ever undervolt or overclock when using custom kernels or roms? Because it could be hardware damage.
Also, do as they tell you above, check if you have the insane f01 emmc chip. I know it's a common missconception going around that since 4.1.2 the SDS got fixed, but it didn't really get fixed since it's a firmware problem in the emmc patched through software which just makes it highly unlikely to happen (but not impossible).
I did some minor undervolting way back before JB came out but not since over half a year ago. I did the eMMc check and yes, I do have the inane chip.
Just an update, I re-flashed a PIT file and a rescue firmware and it seems to have helped a bit. It was running fine for over 12 hours aside from a random reboot just now.
I'm observing the phone right now to see wether the reboot was just coincidental. I really wish this is just a software thing.
Okay one more update, 2 days in and I've only experienced the one random reboot. It's still sometimes slow when waking up, but something around 2-5 secs sore not 5-15 seconds slow. I'm thinking that must be due to touchwiz bloat.