Related
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...
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
Hi,
I'm using a Tmous HD2, Energy for WM, shubcraft 1.5 for Android.
G-sensor worked fine in both OS, until one day I got stuck with the rain without the raincoat and my HD2 was wet a little bit. I dried it for one night. Everything still works ok but the G-sensor in Android.
I checked it again in WM. There's no problem with G-sensor (I can play games with it or rotate the pictures in gallery tab), but when I turned back to Android the problem still there so I assumed that it should be software's trouble. I booted again into WM, tried to do the callibration, turned on and off the G-sensor. Android's g-sensor kept not working. Home screen (Launcher Pro), browser, games, etc. can't use it either.
After that I downloaded another ROM of Android (JDMS 1.5), erased the old one, hard reset WM's ROM, installed JDMS 1.5: it didn't work as well.
What I haven't tried yet is trying another WM's ROM or re-installing Hard SPL.
So what do I need to do now?!
Can any one help me?
already reinstalled HSPL 3, nothing happened.
Vladikox said:
already reinstalled HSPL 3, nothing happened.
Click to expand...
Click to collapse
Did you try having Android build a new data.img just to test default settings?
jmmmmm said:
Did you try having Android build a new data.img just to test default settings?
Click to expand...
Click to collapse
I have deleted all of Android's files in SD card, then copy the original one --> problem not solved.
I am having the exact same problem. The G-sensor works in WinMo but not Android. I've tried re-formatting the SD card and doing a fresh Android install.
Were you ever able to find a solution or does anyone else have any other ideas of things to try?
My problem has been solved few weeks ago.
At that time I was going to lose hope and came to a decision of giving up trying and willing to say good bye to Android's g-sensor. I turned off the auto-rotate in Android for (about) a week. One early morning waked up, turned it on again and a wonderful thing happened: it was in land-scape mode.
In next few days the sensor was not working so well (but at least it worked). Now it run smoothly and I don't get trouble with it anymore.
Wish you can fix it successfully!
I've got the same problem since i'm running android, tried various winmo versions and HSPL versions without succes. Been trying many different android versions, but all won't work. The strange thing about it is that even the app sensordebug shows no variables. The HD2 had a screenreplacement in the past, but to my knowledge this should have nothing to do with this problem.
In winmo it's working great though.
pvdw50 said:
I've got the same problem since i'm running android, tried various winmo versions and HSPL versions without succes. Been trying many different android versions, but all won't work. The strange thing about it is that even the app sensordebug shows no variables. The HD2 had a screenreplacement in the past, but to my knowledge this should have nothing to do with this problem.
In winmo it's working great though.
Click to expand...
Click to collapse
Yeah, I don't get any variables in sensordebug either.
Actually, I did just replace the glass on my HD2, but I can't think of a good reason why that would make the G sensor not work just in Android. If I had broken a physical part of the phone I would think it wouldn't work in winmo as well, but everything works fine there.
As far as I know, the only physical part that would be used differently in Android would be the SD card, so this has me stumped.
I have also been having a ton of "black screen of death" freezes in Android since replacing the screen. Have you found a build that is at least stable?
I've also got this issue after installing a new kernel and no matter what combination I use now it won't work again. I've tried all of my previous working combinations and none of them have fixed this, I've tried turning off auto-rotate and on again but again nothing happens. This is pretty useless if it's stopping on multiple people for no reason.
Anyone know the script in g-script lite to enable and disable the g-sensor to see if this works as I've used this in the past on one of darkstone's builds but don't have the script anymore?
Thanks
RenaissanceMan said:
Yeah, I don't get any variables in sensordebug either.
Actually, I did just replace the glass on my HD2, but I can't think of a good reason why that would make the G sensor not work just in Android. If I had broken a physical part of the phone I would think it wouldn't work in winmo as well, but everything works fine there.
As far as I know, the only physical part that would be used differently in Android would be the SD card, so this has me stumped.
I have also been having a ton of "black screen of death" freezes in Android since replacing the screen. Have you found a build that is at least stable?
Click to expand...
Click to collapse
I'm using Sergio's core droid V0.8 desire wich is very stable and the camera is working, but I tried many others and I never had any BSOD's.
Can anyone tell us where the G-sensor hardware is located in the HD2? there should be a logical explanation to this problem.
Found something interesting just now, I've tried everything to get my current build working with the G-Sensor again including a fresh data.img and fresh install altogether with no success but decided to install a different build that I had on my PC and the G-Sensor works perfectly. I don't get why it wouldn't work with my current build but will with one thats months old with the same kernel as I'm using now. I've gone back to the newer build and the G-Sensor still doesn't work so I'm just going to use a different build as something's clearly wrong with this one.
AvRS said:
Found something interesting just now, I've tried everything to get my current build working with the G-Sensor again including a fresh data.img and fresh install altogether with no success but decided to install a different build that I had on my PC and the G-Sensor works perfectly. I don't get why it wouldn't work with my current build but will with one thats months old with the same kernel as I'm using now. I've gone back to the newer build and the G-Sensor still doesn't work so I'm just going to use a different build as something's clearly wrong with this one.
Click to expand...
Click to collapse
Huh, what build does it work in for you? I'm using NexusHD2-FRG83D V1.7 and it's not working for me in that or in V1.6 that I was using before.
Also, the black screen of death issue I was having wasn't related, as it was fixed with a radio change.
RenaissanceMan said:
Huh, what build does it work in for you? I'm using NexusHD2-FRG83D V1.7 and it's not working for me in that or in V1.6 that I was using before.
Also, the black screen of death issue I was having wasn't related, as it was fixed with a radio change.
Click to expand...
Click to collapse
It wasn't working in MDJ HD 3.7 build but is in MCCM Froyostone 3.4 and also the version I had from months ago Darkstone Froyostone 3.1.
Funnily enough after a day of using the MCCM build I've just gone back into the MDJ one and it's working again. I did find that my sensors.qsdk8k.so file was named incorrectly in system/lib/hw so check this as well as may have had something to do with it. It was called sensors.qsdk8kso before and had the . missing before the so. Use root explorer to change then reset.
Hope this helps.
AvRS said:
It wasn't working in MDJ HD 3.7 build but is in MCCM Froyostone 3.4 and also the version I had from months ago Darkstone Froyostone 3.1.
Funnily enough after a day of using the MCCM build I've just gone back into the MDJ one and it's working again. I did find that my sensors.qsdk8k.so file was named incorrectly in system/lib/hw so check this as well as may have had something to do with it. It was called sensors.qsdk8kso before and had the . missing before the so. Use root explorer to change then reset.
Hope this helps.
Click to expand...
Click to collapse
I don't have a "sensors.qsdk8k.so" file in that directory, only a "sensors.mahimahi.so". I have other qsd8k files, like "lights.qsd8k.so", so I would think I should have a sensors one as well.
Where does that file come from/where can I get it?
thanks for the help!
Up .......
RenaissanceMan said:
I don't have a "sensors.qsdk8k.so" file in that directory, only a "sensors.mahimahi.so". I have other qsd8k files, like "lights.qsd8k.so", so I would think I should have a sensors one as well.
Where does that file come from/where can I get it?
thanks for the help!
Click to expand...
Click to collapse
I've never seen any files called that on my device so what I'd try is first make a backup of that file then rename it to sensors.qsd8k.so and then restart. All of my files in that folder are all .qsd8k. With some builds/kernels they name things differently and say to rename according to your device for example when you get lights.htcleo.so which you need to rename to lights.qsd8k.so to make it work. If this doesn't work definitely try a different build to see if it's working in that and if it is try going back to your one you're on now and maybe it'll wake it up again.
Hi, I have same problem with sensors on my HTC HD2.
A downloaded Sensor Test app from Marketplace and it give me this values:
Accelerometer (BMA150)
Accel X Waiting... M/S
Accel Y Waiting... M/S
Accel Z Waiting... M/S
Magnetic Field (AK8973)
Mag X Waiting... Deg
Mag Y Waiting... Deg
Mag Z Waiting... Deg
Orientation (AK8973)
Az Waiting... Deg
Pitch Waiting... Deg
Roll Waiting... Deg
Proximity (CM3602)
Near/Far Waiting... Prox
Light (CM3602)
Light Waiting... Lux
Battery
Charge 94 %
Temp 35 Deg
Voltage 4.1 V
It looks like a problem with some communication bus or something like that. Can someone try Sensor Test app and check values.
All of these sensors are not working and I dont know how to fix them
Last edited by pawlish; Today at 02:57 PM..
I'm in the same boat as yall. Sensor works in WM 6.5 and even Windows Phone 7, but still no Android. I have also noticed that the proximity sensor isn't working as well. Do yall think the 2 might be related?
Hi everyone,
I have been trying to find a way to fix the data dropping on my htc hd2 while running android, it is so frustrating because it happens all the time. I have tried different roms and no luck!
is there a right combo of radio/roms that works well together? if you have a close to perfect combo please let me know what it is.....thanks!
nena1103 said:
Hi everyone,
I have been trying to find a way to fix the data dropping on my htc hd2 while running android, it is so frustrating because it happens all the time. I have tried different roms and no luck!
is there a right combo of radio/roms that works well together? if you have a close to perfect combo please let me know what it is.....thanks!
Click to expand...
Click to collapse
1) Use a radio version that gives you best reception.
2) Use a build that has letama version 0.7 ril wrapper (or greater)
3) Use a build that uses one of the newer kernels (8.2+ for hastarin's kernels, for example - see my sig)
4) Read http://forum.xda-developers.com/showthread.php?p=9270810#post9270810 and use the options.smd and ip-up zip files attached to the post.
5) Optional - add the word "passive" into the beginning of the options.smd file.
aussiebum said:
1) Use a radio version that gives you best reception.
2) Use a build that has letama version 0.7 ril wrapper (or greater)
3) Use a build that uses one of the newer kernels (8.2+ for hastarin's kernels, for example - see my sig)
4) Read http://forum.xda-developers.com/showthread.php?p=9270810#post9270810 and use the options.smd and ip-up zip files attached to the post.
5) Optional - add the word "passive" into the beginning of the options.smd file.
Click to expand...
Click to collapse
8.2+ does indeed fix data drops? are you sure?
Data drops aren't truely fixed for everyone yet, but theres good progress. Check out hastarin new kernal and the "[Dev] Call for test" thread which usually hovers on the first or second page of this forum.
Data drops has not been fixed! Period!
secano said:
Data drops has not been fixed! Period!
Click to expand...
Click to collapse
However they have been reduced to a level of a minor inconvenience.
I'm using NexusHD2 build with 2.15.50.14 radio and vbnrom ROM and data drops is so rare! maybe you should try the combination. note: i didn't update the kernel or add a fix. it worked out of the box.
dusty_nz said:
However they have been reduced to a level of a minor inconvenience.
Click to expand...
Click to collapse
Not for me, unfortunately. I'm actually back on Hastarin's 7.x kernel because it is the most stable for me. I hadn't thought about changing my radio, though. I think I'll switch from 2.15 to 2.14.
I have been experiencing these issues also. The only thing I found to fix it is to stick with RMNET builds/kernels.
Had loads of issues lately with various builds which were by fluke PPP. So now using the NexusHD 1.7 build and followed the instructions to switch it to rmnet and data is perfect.
Can I ask what country you are in and what network you're on? I am UK t-mobile. My colleague has far less data drop outs on UK vodafone.
Thoughts welcome. Report back.
Yans.
Sent from my Nexus One using XDA App
data stable for almost a week now on PPP
I have not had any single drop for almost 1 week now.
I'm using the following:
HSPL 2.08
Radio 2.12.50.02_2
Winmo rom VBN Droid Reloaded2 oct 2010
Android version Mdeejay_FroYo_Revolution_v._1.5 and changed Kernel to MDJ S7 test, has green tinge pics with flash, but can be solved by setting WB to fluores.
Latest ril wrapper from letama 0.7 from 18-11-2010
Changed my phone settings to GSM auto (PRL) and DNS check set to allowed in hidden menu you can enter the menu by dialing *#*#4636#*#* then go to phone settings
Battery drain in standby is 4-5 ma. Was a lot higher with Led me know, but uninstalled it yesterday. You can make the leds work perfectly by booting Android on your charger
A fully charged battery gives me appr 20 hours life in a mix of heavy and medium use.
Hope this helps any of you, it's really working very well for me.
Cheers
Hi all I have tried several new roms.. And I c seen to have all the features working in mdj revo sense. The only thing I suffer from is data drops..very annoying..but the nexus one frg8 data works fine when I switch it from ppp to rmnet..but the rim is not very fluid..i have force closing in dialer and bluetooth does not work properly...are there any other new roms that use rmnet..i could only find the nexus one.
Sent from my Nexus One using XDA App
Bump for that.
I have the same problems with data connection. Only rmnet works for me.
Any help?
hc97mg2000 said:
Hi all I have tried several new roms.. And I c seen to have all the features working in mdj revo sense. The only thing I suffer from is data drops..very annoying..but the nexus one frg8 data works fine when I switch it from ppp to rmnet..but the rim is not very fluid..i have force closing in dialer and bluetooth does not work properly...are there any other new roms that use rmnet..i could only find the nexus one.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I have been using one of michyprima's nightly builds that can be found here -> http://forum.xda-developers.com/showthread.php?t=824601. As found through my lengthy testing of this build, everything works. Camera does work, but it seems that all of my photos have a greenish tint to them. Other than that it is as close to perfect as you are going to find these days.
One word, do not change the kernel out to anything else unless you want to lose functionality and start having data drops again. The kernel that is shipped with this build is great. Just not overclock-able. Getting 3 mAh drain in standby with airplane mode on, 5-7 mAh drain with airplane mode off, WiFi on and good radio signal. Turning bluetooth on brings it up around 37 mAh.
The one I am using is "DOWNLOAD v4 (11182010 nightly, 31bc15c1)" and it is exceptional. It is PPP data connection but does not suffer from the data drops that the newer PPP builds seem to be suffering from. I have been running this one build for about 3 weeks now and have no intention of changing to anything else in the foreseeable future. I do not know anything about the two newer nightly builds that are listed in the thread, but I do know that this one in particular does work, and very well at that!
For some odd reason, the nightly builds have stopped and I have not seen anything out of michyprima for a few days, but hopefully he will be back around and they will start back up again soon.
Have fun with it ..... HTR
Data (almost) never drops on builds with the new ril wrapper... try any of MDJ builds with ppp.. either Froyo Sense (may have to update kernal) latest of Desire HD latest..