Related
Hey,
Idk if its jus my phone but in every android build ive tried..there always this problem. tried searching but nothing :S
when i try to wake the phone....the hardware keys light up but the screen doesnt wake up for like a few seconds...sometimes even like 10secs :S:S:S other times its really quick.
Ive tried disabling auto brightness, even used setcpu to check if it was clocked too low and set the sleep profile at really high jus to check..but same problem :S the screen jus doesnt come on right away.
It works perfect in winmo but android has this problem
ive even tried changing the winmo rom...but nothin. same problem.
Right now im running: mdeejay FroYo sense 3.1.
Radio : 2.12.50.02
any help!!???
I have noticed this too, although mine only sits there for half a second to 2 secs, never had the patience to wait 10s, just start mashing the power button!
Any fix would be greatly appreciated!
I think your problem is more than likely due to a slow SD card I put the same build I use on a buddies phone and he had some cheap walgreens SD card. The only other thing to get around that is to use setCPU and raise the processor speed during sleep. Unless you are still running one of the earlier builds where this problem still was an issue.
Sent from my HD2 using XDA App
I just got my Dell Streak a week ago, I really like it so far, but I've had a pretty vexing problem come up today.
I had it in Silent mode, and when I woke up the screen and went to "Slide to Unlock", the whole bottom of the screen was unresponsive. I had to let the screen time out and try it again at least three times.
Has anyone else had this problem? I'm running the Stock 2.2 on Rogers, and using ADW Launcher Pro as my launcher. No other major UI Tweaks.
I can confirm that I do experience that problem sometimes. The S2U moves just a little bit, but but I can't slide it all the way over. I'm also using LP+ as my default launcher. I guess it would be a good test to run the Stage UI as a test to see if it's related to LP+ or not.
Sent from my Dell Streak using XDA App
I had this same problem, but I noticed that it only occurred if I had the screen facing my leg when it was in my pocket.
I think that what is happening is that when it's in your pocket it still detects screen presses by your leg, and then it gets confused, and won't detect any more screen presses for a long time.
To begin with it stopped me from answering calls and was really annoying, but now I just make sure I put it in my pocket with the screen facing out and it works fine.
Yall need to recalibrate ur screen that helped mine never to be unresponsive again! Search for the guide on here cant remember the button combo to get to it i think it was hold camera and power at the same time when turning on but dont hold me to that just search xda its on here
recalibrate the screen, and also its created by the friction/heat from rubbing off your leg (wahay), so either have the screen facing out, or buy a case for it
Since i recalibrated my screen i can have it any way i want in my pocket and it never hangs anymore
Download menu unlock from the market. It will unlock when you hit menu
Sent from my Dell Streak using XDA Premium App
kybernetikos said:
I had this same problem, but I noticed that it only occurred if I had the screen facing my leg when it was in my pocket.
I think that what is happening is that when it's in your pocket it still detects screen presses by your leg, and then it gets confused, and won't detect any more screen presses for a long time.
To begin with it stopped me from answering calls and was really annoying, but now I just make sure I put it in my pocket with the screen facing out and it works fine.
Click to expand...
Click to collapse
That's exactly what happened to me all day today! I had it in my jeans pocket with the screen facing my leg! I thought it may have something to do with ADW Launcher, or having it in silent mode all day. I'm recalibrating the screen now!
Mucho Thanks!
Hello I JUST realized my god damn hero's screen must be broken, or, the mobo is somewhat malfunctioning. I can't seem to be able to access the lower part of my screen.
Not only that, it often "decalibrates" and starts malfunctioning even worse :S I have to go back to the lock screen in order to get it back working for a few minutes.
I'm currently running CM7... Please advice thanks
Any chance it could be a bit of a ROM malfunction? Have you tried any others? That would be what I would try first. Hope it helps
Yes.. I have I tried the latest VillainROM, elelinux's rom and the one I'm currently running... any more suggestions? ...
Known issue with Hero's, Half of the screen dies after a year or so.
Mines half dead as well
I think the digitizer malfunctions.
Unfortunately, the only cure is a replacement of the digitizer or a replacement phone.
I found mine Hero having that behavior today.. screen not responding, jus a part of it, but when i turn the screen off and on again it goes to lock screen, and in lock screen works always, and after unlocking the screen it works for some instants.. :/
Can anyone tell me how much do you think it will cost to change the digitizer?
EDIT: After a cache wipe and dalvik cache wipe as well it's working perfectly
£30 I think. Do search for digitizer aand screen not responding in the Hero forums. There should be instructions and suppliers there.
Sent from my Blade using XDA App
I just bought a archos 101 g9 when it was on sale on woot last week and so far it is working pretty good, however I have an annoying problem with it.
If it has been sleeping for over a few minutes (regular sleep, not the deep sleep) and I wake it back up the touch screen goes crazy. The bottom left corner keeps detecting a touch event. It will cycle from multiple on/off touches a second to one on/off every few seconds. If I rotate the tablet to portrait, it will start scrolling the screen none stop to the left. So far the only fix is to do a reboot.
It does not happen every time, just occasionally when I wake it up from sleep.
Today i got a case for it, and whenever it is in the case, the touch screen goes crazy. Same touch events in that same area.
I am guessing something is wrong with the digitizer. Anyone else seen this problem before?
Have the same problem, and as I've read on xda and archosfans forums, this isn't an uncommon issue. We'll just have to wait for a firmware update, as rebooting seems to fix it, so it doesn't seem to be a hardware problem.
Sent from my ARCHOS 101G9 using Tapatalk 2
I have exactly the same problems.
@ARCHOS: PLEASE FIX THIS PROBLEM. THIS IS A SERIOUS BUG !
Sensitive Touch
I have similar problems with the touchscreen. If I'm holding it with one hand by a corner, it detects touch. The rest of the time it is a little jittery and releases or double taps in games. It's still not a deal breaker, though.
I hope we don't have to swap digitizers to fix it.
Hi !
Me too
...works fine after Touch Screen Calibrate , but the next reboot do the same !
surdu_petru said:
Hi !
Me too
...works fine after Touch Screen Calibrate , but the next reboot do the same !
Click to expand...
Click to collapse
I'll give that a try and see if that works. I just got a case and as soon as it is in the case it is even worse.
EDIT: I installed a calibration app on xda and it really made it worse!
What app are you using to calibrate it?
I have a similar issue sometimes.
For me the fix is simply to clean the screen.
The strange thing is, it happens even when the screen doesn't appear to be especially dirty but I put the tablet to sleep, give the screen a serious clean with a microfibre cloth and the touchscreen issues vanish.
Could be a different issue to what you guys are having but the symptoms are the same and it's an easy 'fix' to try.
Hope it helps.
Sent from my ARCHOS 80G9 using xda app-developers app
feffrey said:
I'll give that a try and see if that works. I just got a case and as soon as it is in the case it is even worse.
EDIT: I installed a calibration app on xda and it really made it worse!
What app are you using to calibrate it?
Click to expand...
Click to collapse
Use the inbuilt one, Settings > Repair & formatting > Touch screen calibration.
Sent from my GT-I9001 using Tapatalk 2
omegaRED7 said:
Use the inbuilt one, Settings > Repair & formatting > Touch screen calibration.
Sent from my GT-I9001 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, I had not noticed that area in the settings before. Recalibrating it in the cover has helped a lot.
I pretty much had this since day 1......
The current state is ; it doesn't work at all then all of a sudden It will pop back into life and then pretty much go "mental" as already described, I also found it reacts poorly to minor temperature variations, i.e going from outside to inside and general day to day travelling. Recalibrating used to "help" but now has no effect.
From watching the debug logs part of me thinks it's a bit of both, hardware and software ( just a hunch ) I noticed the driver fail to get a "ping" response from the hardware a couple of times.
I've pratically given up on it myself and plugged a keyboard and mouse in via a hub on the full size usb...... The hub has now stopped working for some reason , I'm now on a OTG Keyboard with a Virtual Mouse Driver using the numeric keypad and some adb input trickery ,
I've got another touch screen/digitizer to plug in, just not got round to putting it in yet and a little part of me is starting to enjoy finding more elaborate ways of interacting with the device... :laugh:
Does anyone know who the OEM of the digitizer Unit is? My previous investigation led me to china but information seems to be thin on the ground with this one
surdu_petru said:
Hi !
Me too
...works fine after Touch Screen Calibrate , but the next reboot do the same !
Click to expand...
Click to collapse
Same problem and even managed a RMA from ARCHOS. Thing is your OC edition fixed it for me.
Hey guys,
I've been having an issue with AOSP roms where my display will just stop updating, Previously on one of Neo's ROM, and currently on CounterShrike 2.1. The screen doesn't turn itself off; it stays on, but freezes and doesn't change. I have to hit the power button to turn the display off and on again and it will work normally again for awhile.
It actually still accepts input when the display freezes. If I press the home button while it's frozen, it will be back on the home screen when I hit the power button off and on. If I'm in a list and scroll with my finger while it's frozen, it will be further down in the list when I hit the power button off and on.
I thought this was related to the proximity sensor bug but when I follow shrike's guide in the FAQ for setting up Chad's proximity sensor calibration, it already is showing 'FAR' when I first load the app and I don't need to adjust the high threshold. I think the sensor is fine.
Anyone have any other tips I can try? Everything works fine under CleanROM DE but AOSP is so much faster I'd really like to try and nail the issue down.
Thanks!
EDIT: I've attached a logcat. Two times I recorded the timestamp when it frozen, around 00:45 and 01:11. But I don't really know what to be looking for in the log cat.
thank god I'm not alone with this! I get this crap with any aosp based rom. I sent logcats to a few and nobody can't figure it out yet. sometimes it freezes but the display bleeds and fades itself off simultaneously
This is just an accepted problem with any AOSP ROM.
If you read the OPs they all mention graphics issues.
If you have been following the JellyBean stuff, they can't get any graphics to work at all.
GrayTheWolf said:
This is just an accepted problem with any AOSP ROM.
If you read the OPs they all mention graphics issues.
If you have been following the JellyBean stuff, they can't get any graphics to work at all.
Click to expand...
Click to collapse
really? the OP's for rage and aokp mention nothing about freezing or graphics being glitchy
Maybe unrelated, but I have recently discovered that if my fingers are even the tiniest bit wet or sweaty, my touch screen completely freaks out and becomes impossible to use. The only way to fix it is to turn the screen off, and turn it back on.
a.mcdear said:
Maybe unrelated, but I have recently discovered that if my fingers are even the tiniest bit wet or sweaty, my touch screen completely freaks out and becomes impossible to use. The only way to fix it is to turn the screen off, and turn it back on.
Click to expand...
Click to collapse
That is probably not an AOSP issue.
GrayTheWolf said:
That is probably not an AOSP issue.
Click to expand...
Click to collapse
Yeah, I sorta agree.. but I never had noticed it until I started using CM9 ROMS.
Actually though, ever since the ICS leaks something has been a little off about the Rezound touch screen, even on Sense ROMs..
Sometimes when you swipe horizontally one direction quickly, it starts to go and then jerks back and actually scrolls the other way. Worked fine in GB for the 2 months I ever used it on this device....
a.mcdear said:
Maybe unrelated, but I have recently discovered that if my fingers are even the tiniest bit wet or sweaty, my touch screen completely freaks out and becomes impossible to use. The only way to fix it is to turn the screen off, and turn it back on.
Click to expand...
Click to collapse
This is true. I've stated this issue months back, sweat or a drop of liquid makes our screen act funny.
Sent from my ADR6425LVW using xda app-developers app
freezing occurs regardless, no moisture involved
What cpu governor and i/o scheduler are you using, do you know?
I've noticed freezes/slow response with either noop or deadline i/o scheduler. The powersave governor or turning cpu speed down too far can also cause freezing.
Occasional Graphical flickering in GUI elements does seem to be an issue with cm roms on multiple devices. I've had success turning on settings - developer - force gpu rendering to reduce flickering, YMMV.
Sent from my Rezound using Tapatalk 2
brenuga said:
What cpu governor and i/o scheduler are you using, do you know?
I've noticed freezes/slow response with either noop or deadline i/o scheduler. The powersave governor or turning cpu speed down too far can also cause freezing.
Occasional Graphical flickering in GUI elements does seem to be an issue with cm roms on multiple devices. I've had success turning on settings - developer - force gpu rendering to reduce flickering, YMMV.
Sent from my Rezound using Tapatalk 2
Click to expand...
Click to collapse
I forget exacts but it's with whatever is default when first flashed. the logcats at the time didn't mention anything about the CPU itself but graphics and HDMI errors with different invalid sound outputs as well
I experience this on multiple AOSP rom's! My phone was fine with sense based rom's but AOSP freezes. Sometimes it doesn't freeze at all, sometimes it's multiple intervals close together. This leads me to believe that it's something in the AOSP rom's themselves and not bad hardware, too many people have it with the same symptoms. Yet sense works fine.
Head scratcher (to put it very lightly).
least I'm not alone on this one. can't be hardware otherwise same issues on sense. anything that's not custom like the kernel or aosp works fine
I agree that I don't think it's necessarily the hardware itself. I think it could be some sort of threshold parameter HTC sets that differs just slightly from CM9 (threshold in what exactly I don't know), but that some of us have hardware that gets tripped up on it and others don't.
I initially thought it was an issue with the CPU (I've always been using the stock speed and governor after the initial flash) but it doesn't matter if I'm doing something really light or really intensive. It also doesn't seem to matter if I'm using stock apps vs. apps I've downloaded either.
I have 2 days off from work so I'm going to flash back to the latest CounterShrike and grab a log cat every single time it freezes up. At the end of the two days, I'll compare every single instance and try to find some correlating event.
Hopefully I'll find something!
God Damn this is really annoying!
Just had to get that of my chest. I'm reading threads and scrolling every few seconds and I just had a few lockups in a row. It's so frustrating because every other aspect of the Rom works perfectly! I don't understand. No amount of kernels I try fixes the issue. Volts don't affect it, cpu speed doesn't affect it. It's enough to make me want to go back to sense just to not have to deal with it. I don't want to
winston856 said:
God Damn this is really annoying!
Just had to get that of my chest. I'm reading threads and scrolling every few seconds and I just had a few lockups in a row. It's so frustrating because every other aspect of the Rom works perfectly! I don't understand. No amount of kernels I try fixes the issue. Volts don't affect it, cpu speed doesn't affect it. It's enough to make me want to go back to sense just to not have to deal with it. I don't want to
Click to expand...
Click to collapse
yeah sadly I went back to sense. dark tranquility gives me phenomenal battery until the mean time with functional video chat. it's not often but I would like to give up video calls for aosp. even with everything I want removed from sense it's still bloated memory wise.
good luck with getting logs. I sent to most devs here and they were stumped
Got a replacement phone coming in the morning, we'll see if I experience the same issue or not.
I tried all sorts of things, and it happens to me.
Went back to Sense with included dsb kernel.
Funky kernel has the issue on sense for me though.
Sent from my ADR6425LVW using Tapatalk 2
I didn't have much luck identifying something in the logs winston856 I'm considering getting a replacement as well. Let me know how you make out.