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...
Let us track the OPEN issues on Android HD2, we will only discuss problems dealing with android alone, issues arised due to radio, WinMo rom and a specific android rom should be ignored.
AFAIK we still have 3 main Problems
1. GSensor/ Touchscreen Freeze.
Related Files in Android : \system\bin\akmd,\data\misc\AK8973Prms.txt and \system\lib\hw\sensors.xxxxx.so
(xxxxx = htcleo or default or qsd8k or ace or bravo based on the build)
This issue is not noticeable unless you a play game which uses Gsensor (Eg Abduction, NFS Shift ...)
This thread has lot more details about this issue and it could be a possible solution for you (it does not work for me though)
http://forum.xda-developers.com/showthread.php?t=803242
Possible Workaround :
1. Disable Auto-Rotate screen in Settings -> Display
2. Run the following commands in Terminal
mv \system\bin\akmd \system\bin\akmd2
killall akmd
To Restore
mv \system\bin\akmd2 \system\bin\akmd
Basically you are renaming the file 'akmd' which is responsible for the sensor to work
2. Data Disconnects
Related Files : \system\lib\libhtc_ril_wrapper.so
This thread has lot more details about this issue and it could be a possible solution for you (it does not work for me though)
http://forum.xda-developers.com/showthread.php?t=794309
Possible Workaround :
1. Switch Mobile Network OFF and then ON (Add a widget [Widget -> Settings -> Mobile Network])
2. Switch Airplane Mode OFF and then ON (Add a widget [Widget -> Settings -> Airplane Mode])
[EDIT]:
Guys looks like we got a fix.. this wrapper seems to work flawlessly as of now... you can try it here...
http://forum.xda-developers.com/showthread.php?t=824413
Just download 0.3 file and replace the file at /system/lib using root explorer
3. Occasional Black SOD and Accuracy in Auto Brightness
Newest kernals seems to have this issue, where the display stays black while the keypad lights glow.
Related Files : \system\lib\hw\lights.xxxxx.so
(xxxxx = htcleo or default or qsd8k or ace or bravo based on the build)
Possible Workaround :
1. Show the Sensor of your phone to some bright light source and your display will be back
2. Disable Automatic brightness in Settings -> Display-> Brightness
I will update this thread with Solutions as and when the developers fix it.
Whatever i have written is limited to my knowledge, it could be wrong, if so please correct me, Most of the vetarans know these issues and the work arounds, i have just put everything together for the new comers and to remind the developers of the existing bugs
Mods feel free to move the thread to General if need be.
Hi depakjan, This is great, thanks for tracking these issues.
can people confirm this "occasional bsod"?
i haven't seen it since light-sensor is calibrated.
i think the bsod is fixed with 2.12 radio and above..
Actually BSOD was introduced in the new lights file... it does not occur frequently... also if you have not upgraded you wont have it obviously...
depakjan said:
Actually BSOD was introduced in the new lights file... it does not occur frequently... also if you have not upgraded you wont have it obviously...
Click to expand...
Click to collapse
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2
hastarin said:
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2
Click to expand...
Click to collapse
I second that explanation ... and the auto backlight levels in CM builds may actually work better than Desire builds if tweaked properly... atleast for me the reaction time of the sensor is much faster ... accuracy still a problem
Accuracy is still a problem, so is Black SOD .. i have been getting this in Mdeejay's Revolution, HD .. latest ones...
it so happens when you have been talking over your phone for a long time(which blocks the sensor from light).. and then when you are finished with the call it wont wake up... maybe it did not sense light ... but after you show the sensors over a bright light source.. it comes back..
i have seen couple of posts and users mentioning about this...
lets see if everyone agrees that there is no Black SOD, i will modify the post for accuracy..
Support of HTC extended battery
I have tried a few android builds, but none of them seemed to support OEM HTC 2300mAH extended battery - after android booted up in the dual boot process, the HD2 powered-off by itself. I read some posts that acknowledged the problem, but I have not come across any android build that resolved this issue... Did I miss them? Thanks.
Can we also add tracking of Idle / Screen Off Battery Drain? Target is 5-8ma, some builds run at 100ma.
Is anyone's market busted?
Most apps won't install, but some do just fine. This started last night. I tested on 4 roms now and all exhibit identical behavior. This was NEVER an issue before.
(the stupid mount/unmount trick does nothing)
However, once they've d/led I can install them manually. Except for google voice. It refuses to install LOL. Google must have screwed something big here.
badmonopoly said:
Is anyone's market busted?
Most apps won't install, but some do just fine. This started last night. I tested on 4 roms now and all exhibit identical behavior. This was NEVER an issue before.
(the stupid mount/unmount trick does nothing)
However, once they've d/led I can install them manually. Except for google voice. It refuses to install LOL. Google must have screwed something big here.
Click to expand...
Click to collapse
There has been an issue internationally with access to the market for a while now. People were able to browse the market as normal but upon trying to install anything nothing would happen. This has been mentioned on several threads over this forum already and the problem is an intermittent one (obviously based on what server you connect to when trying to download anything).
Led Notification is not functioning, especially on Sense build.
backlight drivers are not working , it don't dim light when left without use (it closes the screen ) , as well as light sensor , doesn't dimm light only brightens the screen
jcc266 said:
I have tried a few android builds, but none of them seemed to support OEM HTC 2300mAH extended battery - after android booted up in the dual boot process, the HD2 powered-off by itself. I read some posts that acknowledged the problem, but I have not come across any android build that resolved this issue... Did I miss them? Thanks.
Click to expand...
Click to collapse
Try replacing the kernel from one of the Sense builds with my Alternative kernel.
Sent from my HTC HD2
hastarin said:
Try replacing the kernel from one of the Sense builds with my Alternative kernel.
Sent from my HTC HD2
Click to expand...
Click to collapse
. . . can I just 'tip my hat' to you hastarin . . . you 'd' man
And I'm hopeful that all the devs and chefs will have these problems solved before too long.
Viv la HD2 Android!
Reno_79 said:
There has been an issue internationally with access to the market for a while now. People were able to browse the market as normal but upon trying to install anything nothing would happen. This has been mentioned on several threads over this forum already and the problem is an intermittent one (obviously based on what server you connect to when trying to download anything).
Click to expand...
Click to collapse
What doesn't make any sense is that the app successfully downloads, but either stalls when it needs to d/l or tries to install and tell me it was unsuccessful.
hastarin said:
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2
Click to expand...
Click to collapse
I've found the backlight problem occurs (generally) if I unlock/lock the phone fairly quickly in a short space of time (and yes, I've only seen this on Hyperdroid 1.6 & 1.7, both CM6 builds). It's not consistently reproduce-able though, I can go several days without it happening, then have it happen a couple of times in a single day.
The touch screen is still active though, and swiping the unlock brings the screen back to normal brightness levels.
Tyrion84 said:
Led Notification is not functioning, especially on Sense build.
Click to expand...
Click to collapse
Works for me..could be your build ....try some other build...
hoss_n2 said:
backlight drivers are not working , it don't dim light when left without use (it closes the screen ) , as well as light sensor , doesn't dimm light only brightens the screen
Click to expand...
Click to collapse
this is already covered in the third point as accuracy
Works for me..could be your build ....try some other build...
Click to expand...
Click to collapse
Hi!
I wonder what "works for me" means. What exactly are your leds doing? On all builds i tried so far the left green led flashed about one time a minute green and nothing happened when the phone was charging. Are there some hidden settings or a special program for hd2 leds?
Cheers,
Otto
Like the title says, my touchscreen start behaving erratically, registering random touches, when I use any other ROM except Froyo CEE. It happens when the phone is charging as well as when it's on battery (on battery less often). On froyo it happen's only when charging (so i can live with it).
My question, does any one have some advice as to what i can try, because i like CM7, but i'm unnable to use it like that.
My deduction is that somehow the froyo kernel+gingerbread framework are triggering these events. I can't use gingerbread kernel as i have SOC camera module, and i kinda need camera functionality.
Thanks.
hi my phone is just working 7.2 CM nand rom. ICS 4.0.4 - Htc Sense 3.5 - Cm scream rom - Miui Rom shift of the screen is in them. Usually red, vivid color screen is moving.Screen shift off color doesn't cause. Please help me.
Sorry for my english google translate
please help?
you should return to windows mobile first...
looks like a screen replacement that is not supported by our kernels
schlund said:
looks like a screen replacement that is not supported by our kernels
Click to expand...
Click to collapse
I had broken my screen repair.But it works cm7.2. ICS-HTC Sense-CM scream doesn't work. Why? What should I do?
please help me
what about old ROMs
mustafa3m said:
please help me
Click to expand...
Click to collapse
did try to switch back to SD card version of android or WM6.5??
do you have this problem yet?
tm.bax said:
do you have this problem yet?
Click to expand...
Click to collapse
yes, the problem continues
Hello there,
I recently changed from Schlund's Photonic SD Boot to CM 7.2 NAND Version, where I started having this strange issue. SD Boot worked just fine once I managed to get over the critical first 10 minutes after booting without freezing. Now the screen shifts occasionally, especially when I'm opening white windows or menus like the shutdown menu or the one where you enter a wlan security key. It stops in every position, just like mustafas picture shows. If I turn it around, the line dividing the screen just stays where it is, both frames will turn. I tried changing every single option related to the screen, flashing different versions, without gapps, without update, even [ROM] Phonerty MIUI v4 (ICS). The bug is a bit slower in this one, but still there. In all cases everything is the way it ought to be after tapping the standy button and waking it up again. But in most cases it will wont stay that way. I can't even flash it back to WM (and I don't really want to since I know how useful this little thing can be with Android on it), every RUU i tried to use told me I was using the wrong one. Any ideas? Anything new about this one?