This is getting annoying how can it be fixed, can it be fixed?
Sent from my SCH-I500 using XDA App
I notice it, too, with Super Clean v4 and the matching kernel. When in a call, the screen turns off within 2 seconds, no matter how I get it to come back on (pull awya from ear or press power button). Makes it near impossible to use automaed call systems.
It sucks why do we have the screen sensors if they dont work during calls its not supposed to time out unless something triggers it
Sent from my SCH-I500 using XDA App
I do not have such problems. My screen stays on unless I get close to the sensor. Once I move away the screen comes back. What are you running? Kernel / rom
Stock dl09
Sent from my SCH-I500 using XDA App
When I get out of work I'll check my wife's stock dl09 to see if the issue is present cuz my rooted voodoo dj05 is sensor dependent
Yeah I'm having the same problem, I am using Super Clean DJ05. I have to unlock the screen every time I take it off from my ear, no matter how long it's been.
I only had that problem on my stock rom after I disabled a needed service.
I think it was one of the voicemail services. Can't remember which one off hand.
Sent from my SCH-I500 using XDA App
I had that probably till I cleaned my screen
Sent from my SCH-I500 using XDA App
My wife doesn't have that problem but my sister does. Both stock dl09. Odd I can't figure out why.
Had the same issue with the kernel in the RubikS 1.7 OP. Switched to the 1/23 JT V5 and it went away.
Related
Hi,
I just bought a N1, it works great so far, the only problem it has is when I wake it up by using the power button. Sometimes it doesn't work but most of the time it works.
I thought it was the power button but I installed cyanogenmod, I set up the trackball to wake up the device and it also happens that way.
Are anybody having the same problem?
Same problem. I think is a problem with Cyanogenmod, when having stock firmware never happened tu me.
Sent from my Nexus One using XDA App
There's a six second lag between going to sleep and waking up. Maybe this is what you're seeing?
...although I have heard other complaints about this with CM.
Sent from my Nexus One using XDA App
perrera said:
Same problem. I think is a problem with Cyanogenmod, when having stock firmware never happened tu me.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I used the stock firmware only two days and I didn't noticed it, but I am not sure and I don't want to flash it back, I like Cyanogenmod. Maybe I will try 2.3 if it comes out soon.
danger-rat said:
There's a six second lag between going to sleep and waking up. Maybe this is what you're seeing?
...although I have heard other complaints about this with CM.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I thought it was Widget Locker. With Widget Lockers it fails often I think because the six second lag.
I've noticed that whenever I press the power button to wake my phone up, there usually is a delay from the time I press it til the lock screen comes up. The delay is about 2-3 seconds. Anyone else seeing this delay or is it just me? Im running a stock clean unrooted vibrant.
Sent from my SGH-T959 using XDA App
this also happens to me but it's not that often. Try lagfix?
Oh is this something that can be fixed with the lag fix? Can anyone with lagfix testify to this?
Sent from my SGH-T959 using XDA App
This isn't fixed with a lagfix; and it is quite normal with this phone. Custom ROMs, in my experience, do a good job with it though.
I'm not really sure, because when i have my delays i think it's only a lag.
Lagfix wont help.
I have lagfix and this happenstoo.
1 reason is... when you click power your phone fades in or out so that causes it to delay a second then it just does it again for a second to get everything started and ready.
No real way to fix. Its usually on every vibrant but the ones with super fast ROMS wont have it.
Sent from my SGH-T959 using XDA App
My phone often takes up to 10 seconds to turn off the screen which is super annoying.
Sent from my SCH-I500 using XDA App
10 seconds?! I STRONGLY reccomend you do a full master reset.
Sent from my SGH-T959 using XDA App
I was wondering if anyone else has ever experienced this issue. I am currently running the latest cyan 7 nightly but i do recall it happening 2 other times on cyan 7 RC4 and RC1. I am not at all saying it only happens on cyan, i am just showing when and how it happened. All 3 times it happened my battery was below 10% and i restarted my phone to have the issue occur. It seems as if every button on the screen would choose the exact mirrored opposite of itself on the screen. If i would press the phone icon on adw the default on the other side wich happens to be internet browser would launch. If i pulled down on the notification bar the app drawer would open and so on and so on. the only thing that was regular was when i would press an option in the main menu such as wifi or location, basically anything that didnt have an option next to it that it could switch to. after a few minutes i restarted the phone again to have the issue go away as fast as it started. It was not only in adw for those wondering it was anything that had an option next to it, such as pressing favorites in the browser and it would launch whatever is opp of it, settings i think im not positive at the moment. Oh well i just figured i would share some of my story with all of u in case it somehow starts a topic or even some how helps somebody out in any way. thanks, veritas
Sent from my HTC Vision using XDA Premium App
something told me i was going to be the only one with this crazy issue lol.
Sent from my HTC Vision using XDA Premium App
i know what you mean. I had that happen too. It didn't happen anymore after I flashed to another ROM. I'm on CM7 RC4
veritasaequita said:
something told me i was going to be the only one with this crazy issue lol.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
I work for a cell phone repair company and we recently had a G2 come in with heavy water damage. after doing the water damage treatment the phone powered on, everything working fine.
I powered it off to put my SIM into it to test the call functionality and when it powered back up the entire touchscreen was backwards, even the softkeys at the bottom.
we replaced the digitizer and that fixed the issue, so maybe T-Mobile or HTC will warranty it if its a bad digi
I flashed a co-workers vibrant today, and after messing up and having to use eugunes froyo followed by the true 959 flash, I got 2.1 rooted. Once I was there I flashed the Deodexed KA5 rom here; http://forum.xda-developers.com/showthread.php?t=913477&highlight=busybox+2.2. After that I flashed the voodoo lagfix 5.5
She didn't get much chance to use it at work, but text me just now to say that she can't hear anyone on her phone, but can if she uses speaker phone, and that the volume buttons are reversed (up puts the volume down).
Any idea what could be causing that? The only thing i can think of is the voodoo lagfix possibly being for the I9000, but if that's the case is there even a lagfix for the vibrant on froyo?
Thanks for the help.
EDIT: apparently the phone doesnt make any noise when it turns on either.
Sounds like a bad flash! Just odin back and reflash.
Sent from my SGH-T959 using XDA Premium App
Sent from my SGH-T959 using XDA Premium App
This has been happening since I remember getting the device. About 3/5 times when I bring my device out of standby and I go to enter my pattern the touch is off. I have "show touches" enabled in developer options to verify this.
When I put my finger on the top left dot of the 3X3 pattern, which is around the middle-left of the screen, it is detecting that I'm touching the device all the way in the top left corner. If I drag my finger around the screen, the touch is offset. If I remove my finger from the screen and place it back on the screen, then it is properly detected.
I didn't run on stock for very long, maybe an hour or two, before I rooted and flashed AOKP. Right now I'm on WhiteHawkx's unnoficial AOKP nightly and Franco's Kernel (r122).
My plan is to flash back to stock and see if it still happens then. But currently I have a really busy week ahead and don't have time so looking for insight.
Anyone else experience something like this?
No one? So I guess I should call Google for a warranty exchange?
Sent from my Nexus 4 using xda premium
fone_fanatic said:
No one? So I guess I should call Google for a warranty exchange?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I would do that if I were you.
Sent from my Nexus 4 using xda app-developers app
Try recalibrating the touch screen, I think there's an option in settings.
Sent from my HTC One X using xda app-developers app
It's franco's kernel, I have it too.
.coomb. said:
It's franco's kernel, I have it too.
Click to expand...
Click to collapse
I posted in that thread a while ago about this issue and no one confirmed. Thanks for your reply. I'm going to go back to stock this weekend and run it for a couple days to verify.
Sent from my Nexus 4 using xda premium
fone_fanatic said:
I posted in that thread a while ago about this issue and no one confirmed. Thanks for your reply. I'm going to go back to stock this weekend and run it for a couple days to verify.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Let me know your results. If it persists, I might have to send mine back.
I'm on stock ROM. I have this issue too, when I power on and drag to unlock, I get a delayed mismatched response. I have to power off then back on again.
It started this recently, so might be app related.
Sent from my Nexus 4 using xda app-developers app
Vyker said:
I'm on stock ROM. I have this issue too, when I power on and drag to unlock, I get a delayed mismatched response. I have to power off then back on again.
It started this recently, so might be app related.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
What kernel are you running?
Vyker said:
I'm on stock ROM. I have this issue too, when I power on and drag to unlock, I get a delayed mismatched response. I have to power off then back on again.
It started this recently, so might be app related.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Turn on " show touches" in developer options to help verify if you the save thing happening.
I don't have to reboot mine but I have to lift finger of screen and put back on to get it to properly detect where the touch should be.
Sent from my Nexus 4 using xda premium
So just as a follow up I reverted to stock for 5 days and didn't see this issue. Flashed back to AOKP and Franco kernel and now it's happening randomly when I go to hang up a call. I tap on the red hang up bar and it detects the touch in the top left corner.
I called Google play support but since I didn't buy my device from them they directed me to lg.
I'm starting to think it's my screen protector.
Sent from my Nexus 4 using xda premium
lol, I had insensitivity issues on the bottom of the screen way back, I use a displayed pin pad on lockscreen so I just tap a certain spot to unlock, I sometimes wonder why the digitizer register incorrectly.
flashing a different kernel helped, I'm using motleys.
Have had this problem since launch, im on stock rooted, maybe its a certain app?
If anyone wants to compare their apps with me to find a similar problem, shoot me a pm