Hi
I know, was discussed so many times...but because of just this, I'm confused as hell. Whenever my batterycharge is quite low, my phone starts to hang pretty frequently...the touchinputs at least. I noticed, that this happens, when I walked a bit with my phone. So my guess would be, that the g-sensor is overloaded and that freezes the touchscreen. I know, there are Kernels that deactivate the g-sensor, but it's a handy tool for screenorientation. So, is there a fixed kernel which leaves the g-sensor activated but removes the touchscreen-freeze bugs?
Hope someone can help me.
Greetings
NessD
wow ... i didnt know the battery charge has play in this ... i guess ill keep it better beefed up ... thanks for da tip
Its still a mystery to me. Because a lot of people seems not having this issue anymore.... Not me, with the last radio, trying wm roms and several builds. Like you, it is very hard to walk typing a sms. Ok I will not be hit by a car but its still frustrating hehe
Yeah, I just noticed that I get those problems when 2 cases are given: Low Battery Charge (full battery is no problem) AND when the HD2 moves around alot. I get touchscreen freezes then. Either one for it's own is no problem, but both keep producing the freezes.
I haven't had ANY touchscreen freezes using hastarin R8. It's actually probably the best one ive used. No touch screen freezes and the auto brightness works on CM6.
No kernels have fixed this yet, some builds claim "no g-sensor freezes" but they do. (or at least they do for me, i'm not doing something wrong am i?)
mmduluth said:
I haven't had ANY touchscreen freezes using hastarin R8. It's actually probably the best one ive used. No touch screen freezes and the auto brightness works on CM6.
Click to expand...
Click to collapse
Hastarin r8 does not work for me...using Hyperdroid v1.7, can't get data to work...
Experimental kernel released that (should) fix this.
http://forum.xda-developers.com/showpost.php?p=9194473&postcount=140
I can confirm it finally works. Today is a great day for the community
Related
Ok I'm using newest energy cht rom radio 2.12.50 and shubcraft froyo android build with 384 zimage....
Heres the problem that I have had all week my phone works fine when I am stationary minimal screen freezes great speed but when I get up and walk with my phone and try to use it the screen freezes almost every time then the entire phone freezes. I have also noticed this on elevator and when I step out of my car.. this is weird and I know it can't be just me as its been going on for a week now.
So to sum it up stationary best phone ever...walking phone dead and I wanna slam it on the ground.
Sent from my HTC HD2 using XDA App
try the desire v5's zimage, no freeze at all
Im having same issues,with all the version i have tried, including V5 aparently this screen freezing is a known issue and makes the use of Android in our HD2 very very frustrating.
ive upgraded my SD to a class 6 and still suffering from it
Im wondering if there is a program that causes it or its just the OS...
in any case We have to be patient ,im sure pretty soon the amazing developers will come with a solution.
might be a screen rotation issue
Just came back from street, again same issue.
I thought it may be the network connection that was affecting the phone, so i switched to Airplane mode and turn off automatic updates,still this didnt help...
so im beginning to think this is related to yes,either the screen rotation (maybe as we walk it does affect the sensor )or gps..
miko3d said:
Just came back from street, again same issue.
I thought it may be the network connection that was affecting the phone, so i switched to Airplane mode and turn off automatic updates,still this didnt help...
so im beginning to think this is related to yes,either the screen rotation (maybe as we walk it does affect the sensor )or gps..
Click to expand...
Click to collapse
I've just learned to deal. Its better than SoD's or being in Winmo and having to pull the battery out.
I actually noticed it today as I went from a dark room to a very well lit room so Im with u guys it seems its either rotation issue or light sensor issue andvi have no doubt in my mind the devs will have it fixed in no time just didn't see it mentioned anywhere else so figured it was worth a mention. Thanks all I'm so glad I'm not alone on this one.
Sent from my HTC HD2 using XDA App
when in windows mobile make sure to disable all battery and back light settings and in android change blacklight settings and sleep setting to stay on
I am having the same issue - using ChuckyDroidROM + shubCRAFT CM6RC2, basically when I start moving or even moving the phone the touch screen becomes very unresponsive and sometimes even the hardware buttons don't function properly. At first I thought it was just my device until I saw this post...
Think its a bug with manusfreedoms 384mb ram enabled Zimage dident get this problem using past images.
sure it will be sorted next image release.
I thought i was alone in this case too !
We are not a lot with that screen touch lag, so maybe we did something wrong. Here is what i found so far :
-Changing build don't rix the problem
-tried another radio, another rom...nothing.
I tested 27/07 03/08 cotulla zimage, now manufeeedom 382mo zimage-nopc, the problem is still here.
changed from a class 2 to a class 4 and seems to be worse. (!)
You are right, it seems to be worse when i am moving from one room to another so maybe it is gsensor related.
Right now it is hard for me to type that text,
Don't know what to do... buy a class 10 sdcard ?
I just got my HD2 today and got android set up. I'm noticing the same thing as everyone else with the unresponsive touchscreen. It happens every time I tilt the phone to try to change the screen rotation. Usually hitting the hardware button allows it to respond once again, but it happens quite often.
hey hey hey first and formost i see u guys all hav the same issuse what i dont see is ur device info along with the rom, radio, android verison, and the location ur android is stored ... i have the lates verison of droid v5 also energy with cookie full and my radio is 2.8 i believe android is on the sd card and running smooth ... now that the intro is out of the way hav u guys read what was needed , reason askin i found the thread where the question and answer is... and yes u guys are the only ones... now please do a search go up to the first thread of android on hd2, and good day to u all
Wingtytn, can you be more precise in your answer ? I am a quite long user in Xda, always try to help when i know and i never ask a question wich have been answered somewhere. I don't think i have the noob profile you seems to write. If you think about formatting sdcard, of course i did. I have a 2.08 radio, latest shubcraft build with manufreedom 382mo zimage. My rom was changed to a light android dedicated one, the latest chuckydroid rom. Just don't know what else to do and waste a lot of time trying to fix that from myself.
Sent from my HTC HD2 using XDA App
The TS issue is kernel related, that's why using an older kernel say the no speedy one should fix it. This is also the reason why this issue is being seen over multiple builds.
Sent from my HTC HD2 using XDA App
shu8i said:
The TS issue is kernel related, that's why using an older kernel say the no speedy one should fix it. This is also the reason why this issue is being seen over multiple builds.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Thanks a lot shu8i, i will try an older zimage than the 27/07's cotulla.
Edit : Mmh exact same problem with the 23/07 zimage Cotulla_zImage_CABDET_NOSPEEDDY. That is weird.
I will order a clas 10 sdcard and see what happen...
Try the game ”Runners”. It uses both the camera and the g-sensor and freezes mad anytime, anywhere. Huge affirmation to the idea it's a bug of the g-sensor's or otherwize the screen's drivers.
DuperMan
Me too with screen freezes, i had tried all builds and same result. I think this is a problem with SD access because i noticed more freezes as more apps opened in backgroud.
Try to calibrate the g sensor
Found something ...
try disabling auto-rotation feature (settings -> display)
It works perfectly for me now.
Can you confirm that works for you too?
Did you dind a way to calibrate g-sensor on froyo?
Why the auto-rotation feature hangs so much for us?
Sent from my HTC HD2 using XDA App
Does the kernal act different on different Hd2's???
Whenever i use N1 kernal i have this Touch screen freeze and Gsensor problem, it's like this, it works perfectly fine, all of a sudden touchscreen freezes for say 10 secs and at that time Gsensor stops working and again goes back to normal...
With EVO Kernal.. i still got this issue but at a level which is not usually notable, which becomes an issue only while playing games, but still issue persists for sure.
My question here is, many in this forum say they have 100% Gsensor working, how is that possible i have tried many Wm Roms and radio rom combination, i just couldn't get rid of the above problems, in that case how come some of them alone have 100% working android builds?
So does the kernal work best in one HD2 and bad in another.. is it even a valid conclusion?? or the ones who say 100% working are just bluffing or they did not test it properly??
i just wanted to confirm that the Gsensor and touchscreen bug is universal and not in specific phones,.. help me sort out this issue ...
Also it would be helpfull if any of the kernal developers confirm whether it's a known issue or it's only my device .. most of the cooks mention Gsensor and touchscreen as WORKING...
I'm still getting touch screen freezes with any of the Cyanogen Mod Froyo builds, Bangsters/HyperDroid, assumed to be associated with the g-sensor.
I re-formatted my SD-Card and re-installed and I'm still getting freezes.
This is the 1 thing that is stopping both from becoming a perfect build, as everything else is amazing.
Any suggestions? Does it have something to do with AXI/NOAXI/EVO kernels? Under-overvolting? Is it the kernel?
Ive had problems with screen freezes with almost every rom, but i got barely any on this one. http://forum.xda-developers.com/showthread.php?t=790374
It also is a very good looking rom.
scbrother said:
Ive had problems with screen freezes with almost every rom, but i got barely any on this one. http://forum.xda-developers.com/showthread.php?t=790374
It also is a very good looking rom.
Click to expand...
Click to collapse
Yeah, I've experienced similar results, though I dislike SENSE based builds and prefer a Cyanogen Mod. I know Sense builds are more stable in the sense that they don't have as many touch-screen freezes, but would like to find a solution for the other builds.
:-/
FriedSushi87 said:
I'm still getting touch screen freezes with any of the Cyanogen Mod Froyo builds, Bangsters/HyperDroid, assumed to be associated with the g-sensor.
I re-formatted my SD-Card and re-installed and I'm still getting freezes.
This is the 1 thing that is stopping both from becoming a perfect build, as everything else is amazing.
Any suggestions? Does it have something to do with AXI/NOAXI/EVO kernels? Under-overvolting? Is it the kernel?
Click to expand...
Click to collapse
I didnt get any touch freezes with this setup: http://leoandroid.com/viewtopic.php?f=212&t=168
Are the devs trying to fix this problem/Are they aware of it? I'm asking because I have not heard anything about this issue since months and the release notes list g-sensor as "working" (freezes are definitely related to or caused by g-sensor). The freezing problem still exists. I can even reproduce it perfectly when g-sensor is activated. Compass is shaky too.
I've tried a LOT of builds since September, mostly Mdeejays (love them ) the last few weeks. Could reproduce it with any build. Also tried many radio ROMs, many WinMo ROMs -> no change.
It's the kernel. Try one of the builds that use a current kernel (such as Hastarin's, rather than the old desire-based kernal on most of the stock builds). They still get the occasional, very short, freeze, but it is almost un-noticable. I'm using Darkstone's stock build (from here) with hastarin's 7.8 and it's fine with screen rotation left on.
The freezes are caused by saturating the i2c bus on the device. G-sensor is one of the things on that bus, but not the only one. The current kernels have increased the speed of the bus to help keep it clear, but it is now set to its maximum speed. I'm not sure if there where other fixes done as well.
I was using different versions of hastarins kernels. I don't get the freezes (only sometimes) when I hold the device in a normal way. But I get them EVERY time when the camera is facing down (for example when I look on the ground in streetview in Google maps with activated compass function, or when I play teeter). It's the same position you have to lay down the device for calibrating the g-sensor. The air bubbles will freeze almost every time in this position. All other orientations work very well.
I've made some videos where you can see the problem (sorry for the quality):
http://www.youtube.com/watch?v=-RlCuITimvM
http://www.youtube.com/watch?v=A8PWNIhwTqM
There is workaround which works: http://forum.xda-developers.com/showthread.php?t=803242... new hastarin and mdeejay kernels include this patch... and no, freezes aren't caused by saturating i2c bus but by occasionally not releasing i2c bus by g-sensor chip after reading its state...
Hey,
I've got the HD2 running extremely smoothly with the NexusHD2-Gingerbread v2.2 build.
Since moving to android and trying out WP7 I have been experiencing an issue where after a whole day of running perfectly I will turn the screen on to find everything is washed in white - it's like the screen turns greyscale but in white so everything is still visible and works but in white.
i don't seem to be able to find this problem anywhere else but it has happened with all the android nand roms and the WP7 rom - a soft reset fixes the issue. I'm currently using radio Radio_Leo_2.15.50.14 and have switched around but haven't found one that fixes the problem...
Any thoughts on what could be causing the problem??
Thanks, Luke.
I have the same problem sometimes. Will be glad if someone can explain!
Ive also experienced this, disappears after reboot or sometimes if i turn the screen on-off a couple of times, kinda weird.
Glad to see others are having this problem - seems to be so rare but I cannot find a solution. Would be interested to see if it still occurs now with standard wm6.5.
Anyone else experiencing this or have some idea of a fix?
i too have this problem.many times screen just go off like greyscale.can anyone help?
One more with the same problem...
Never had it with my currentrom (Hyperdroid) until I've read this thread.
Bump for wisdom.
Are you morons really that stupid
Get the screen out of the sun and away from hot surfaces you dumb bastards and it wont happen, it isn't a nand but a screen issue.
With stupidity like that you will be admins of XDA in no time
ALL_XDA_MODS_R_C*NTS said:
Get the screen out of the sun and away from hot surfaces you dumb bastards and it wont happen, it isn't a nand but a screen issue.
With stupidity like that you will be admins of XDA in no time
Click to expand...
Click to collapse
Erm what the f*ck? No need for that. Any actually, it's not a screen issue, it's an issue in earlier ROM's (well from what I've experienced). Like flash Cotulla's Desire ROM and it happens a lot. I presume you don't really like XDA due to your username? Banned maybe? Why would you even bother making a new account and just trollin'? That's sad, lol.
I only had it when the first batch of ROM's came out. Never withing the past month and a half.
It's like the screen goes negative.
But yeah, there isn't a clear fix for it AFAIK, you should back-up everything on your ROM and try an up-to-date ROM and see if it's still happening. I doubt it.
having the same problem as well
usually happens after i wake up, so during its idle time which is kinda strange
i also noticed it started happening after i installed cracked widget locker, any of you using that?
It happenes to my phone quite regulary but only running android roms, i think around september 2010 it happened the first time. I suspeced my phone, but even after getting a new hd2 it happens sometimes. It usually just happens randomly, not after specific actions. Sometimes it stays only for some minutes and sometimes it can be only fixed with a reboot.
I'd really like to know when this bug will be fixed.
I was having exacly the same issues with my old build. But since im using CoreDroid this problem has dissappeard.
+1 I've only experience this twice, and not since December, but I found it weird both times. I think both times were during a phone-call. A reset worked.
ALL_XDA_MODS_R_C*NTS said:
Get the screen out of the sun and away from hot surfaces you dumb bastards and it wont happen, it isn't a nand but a screen issue.
With stupidity like that you will be admins of XDA in no time
Click to expand...
Click to collapse
Wow...another keyboard hero....you are so brave typing that, we are all in awe of how awesome and manly and strong and tough you are!!
ANYWAY......STFU...it's not a screen problem.
I too have this problem, and it is my 2nd HD2 and happens VERY rarely, but does happen and has happend on both of them.
OH, and Mr Tough Guy....I live in the UK...VERY rarely get warm weather over here, so it AINT the sun.
You, Sir = FAIL.
Matt
Same here happens once or twice a month no big deal though
Sent from my HD2
I'm currently running imilka's RAM Desire HD v2.0 since a month or so, the pale screen appears sometimes up to 2-3 times on one day and then not for several days. A reboot allways fixes it, sometimes it fixes itself after some minutes.
But i really find it annoying.
This happened to me in most desire/desire hd sense builds.
Now, I use the official hd2 MIUI and gingerbread seems to solve the issue.
Hi,
many people still claim there isn't such a problem but there IS:
After ending a call the screen stays off and can't be turned on again. Hardwarekeys don' t do anything.
Only option: Hold the phone in bright light or take battery out -.-
I tried the most popular roms here (NAND&SD)
In WinMo everything works fine.
So here i want to show that not only i but many others suffer by this issue.
Hopefully some real CHEFS/Devs realize this.
Making tons of senseless customisations and graphics tweaks isn't enough to be a real Dev...
Here are some of the threads concerning this issue so far:
http://forum.xda-developers.com/showthread.php?t=1061481
http://forum.xda-developers.com/showthread.php?t=965123&highlight=call+screen
http://forum.xda-developers.com/showthread.php?t=1097531&highlight=call+screen
http://forum.xda-developers.com/showthread.php?t=1097531&highlight=call+screen
http://forum.xda-developers.com/showthread.php?t=735906
http://forum.xda-developers.com/showthread.php?t=946012
http://forum.xda-developers.com/archive/index.php/t-946012.html
srmemnoch2 said:
gsm.proximity.enable=false
you can include this in your build.prop file, locate in /system and reboot.
this never turn off screnn during calls..
but i think only run in froyo
im desperate i want update to gingerbread but this code do not run on ginger.
ragards
Click to expand...
Click to collapse
this really helps! But now the screen stys on all the time, must be careful not to end the call by touching the screen XD... But it's better than having a blocked phone.
But still the issue itself isn't solved ...
You could try http://www.xda-developers.com/android/proximity-sensor-re-calibrator-for-desire-hd/ this?
yes tried this already before, thanks, but didn't work.
I know this problem sounds weird to those who don't have this issue but it's real (i'm not crazy XD) The hardware is also working correctly as on WinMo everythiong's fine
I'm been having this problem since my first rom. I actually thought it was just my phone. It drives me crazy, as I found that plugging it in gets the screen to return. Very annoying!
Sent from my HD2 using XDA App