I lost my Jam today and I am thinking of replacing it with a typhoon (qtek8020 right?) because I found it second handed cheap. Has anyone of you regreted buying this phone? Will I miss many of the features of a pocket pc? Is the only difference the touch screen? Have you guys upgraded to wm2005? Stable? Fully functional? I'm sorry for asking so many question but i really would appreciate any help.
Thanks
i have a JAM and an SP3.
i think the major difference are the input methods.
keyboard Vs keypad.
if you use it for minimal email etc etc, you won't miss the stylus.
if you do a lot of typing, the JAM is more suited to you.
You could always get an IR or BT keyboard for it.
i don't know where to post this thing properly so please forgive me.......is it possible to use wp7 on other Wm phones like pro2 diamond2 etc...
I suspect not. The main reason the HD2 works is that the architecture of the phone is close enough to work. Plus it has a capacitive rather than resistive screen which is a major point.
Hello,
I open this thread because I've got a bad issue with the nand rom just flashed on my HD2 MDJ's CyanogenMod7 (v2.6) A2SD+
In fact, sometimes, the screen seems to be "fool", it is shacking left to right, randomly even I don't touch the cell phone
I hardly suspect the accelerometer... I have deactivated the auto screen rotation and the haptic feedback but I have the same problem.
Before flashing this nand rom I was on Pyrana V11 nand rom winmo and I never experimented this sort of bug.
Is someone else have the same problem ? A solution to fix this issue ?
Thanks for your answers.
Best regards
I'm running the same NAND rom on my HD2 and I haven't had that problem.
Hello and thank you for your fast answer
This is very strange. Never have this problem on windows mobile before. I remember that I have tested another CyanogenMod but on sdcard this time and I was having the same issues with the screen who is doing stuff "alone" !
I have a screen protector but I'm not sure that is the guilty. That's a pity because the MDJ's CyanogenMod7 is very fast and stable, just this problem poisoning me
Will continue to search for a solution (maybe the screen is too sensitive and it can be set...).
Thanks again for your answer, wish you a good day. Best regards
Hello again !
Seems that my problem is solved.
I realized that I use an extra battery (2400mAh) with the HTC HD2 and that kind of battery is bigher than the original one and needs an extra battery cover (plastic one).
By looking the original cover in metal, I saw two points on it. These two points seems to do contact with two mini balls behind the cell phone (to avoid electrostatic discharges ???). So, the cover of the extra battery doesn't do the contact on the two balls.
So, I simply exchanged the two batteries and take back the original one with her original metal cover and now : NO PROBLEM AT ALL !!!
Right now the screen stopped to do things without any touch with fingers and it is totally well reacting
I hope this thread could help some people who are in the same case.
Thanks for reading, best regards.
It appears that there is a general issue with the G-Sensor after a screen replacement has been done. There are tons of users in the Android Q&A forum with the issue. The sensor works fine in winmo but not in ANY android rom after the screen has been replaced. I'm guessing its a hardware driver issue?
Please could someone tell us what info/data we can give to the ROM chefs and kernel gods so that they can take a look and fix this.
boflynn said:
It appears that there is a general issue with the G-Sensor after a screen replacement has been done. There are tons of users in the Android Q&A forum with the issue. The sensor works fine in winmo but not in ANY android rom after the screen has been replaced. I'm guessing its a hardware driver issue?
Please could someone tell us what info/data we can give to the ROM chefs and kernel gods so that they can take a look and fix this.
Click to expand...
Click to collapse
Dont know if this helps...but I had my Hd2 screen replaced few months back...and dont have this problem... screen is much better than before though with beter colour saturation....check with HTC as this might be an error on their part..
Sent from my HTC HD2 using XDA App
G-Sensor Not Working after Screen Replacement
boflynn said:
It appears that there is a general issue with the G-Sensor after a screen replacement has been done. There are tons of users in the Android Q&A forum with the issue. The sensor works fine in winmo but not in ANY android rom after the screen has been replaced. I'm guessing its a hardware driver issue?
Please could someone tell us what info/data we can give to the ROM chefs and kernel gods so that they can take a look and fix this.
Click to expand...
Click to collapse
I have this same problem with one of my HD2's that had the screen replaced.. Everything works perfectly except the "G-Sensor"...
I posted the problem in this thread http://forum.xda-developers.com/showthread.php?t=902129 a while ago, and been watching ever since... Havent seen any solutions, but more reports of the same problem been added to it daily... I'm also assuming that they changed the G-Sensor hardware along with the screen... Beacause it works perfectly in WinMo, and it dont in none of the Android Builds I've tried (CMYLXGOs all versions, Imilka's all versions, RAFDROID, CyanogenMod, etc)...
Everything works good on my Primary HD2, no problems at all... I'm hoping some Chef/Kernel developer might just take some time to check this out...
Have you guys went into Settings>Display>and ticked the check box for Auto-rotate screen?
T-Macgnolia said:
Have you guys went into Settings>Display>and ticked the check box for Auto-rotate screen?
Click to expand...
Click to collapse
That option is checked by default.. Even if You uncheck and check it, it still dont work... If You go into G-Sensor Calibration, the bubbles dont move at all... All those solution was posted in the thread, in the link above...
I'm really assuming is some hardware/driver problem... It worked fine with android, but after they replace the screen, it stopped working...
cmcmyers said:
That option is checked by default.. Even if You uncheck and check it, it still dont work... If You go into G-Sensor Calibration, the bubbles dont move at all... All those solution was posted in the thread, in the link above...
I'm really assuming is some hardware/driver problem... It worked fine with android, but after they replace the screen, it stopped working...
Click to expand...
Click to collapse
Sorry I did not click on the link and rad the other thread. If you go to calibriate your G-Sensor and it does not move then it sounds like either your internal G-Sensor hardware is faulty or not properly connected. I would make the tech you had work on your HD2 work on it again or take it to another repair shop.
T-Macgnolia said:
Sorry I did not click on the link and rad the other thread. If you go to calibriate your G-Sensor and it does not move then it sounds like either your internal G-Sensor hardware is faulty or not properly connected. I would make the tech you had work on your HD2 work on it again or take it to another repair shop.
Click to expand...
Click to collapse
It's a good point You have there... But I would be assuming that was the problem if the G-Sensor wasnt working in Windows Mobile... Everything works perfectly in WinMo, including the calibration... Thats another reason we have come to believe its a hardware upgrade or something similar...
I have the same problem. I bought an HD2 from someone in the Marketplace, and I can see from the pry marks on the bezel and the broken adhesive that the screen had been replaced at one point. I also believe there must have been some hardware revision that is still compatible with WinMo, as the same driver works unilaterally, but not with Android. Definitely tried most of the recent ROMs and different combinations of kernels, and cLK/MAGLDR, but it never works.
Charnsingh alludes to the G-Sensor code in the kernel in his [DEV] thread here: http://forum.xda-developers.com/showthread.php?t=1049170 (don't post unless you're a dev though), and says that it's pretty minimalistic. So maybe there's a solution out there, but the developers haven't gotten to the bottom of it. I'm watching that thread intently to see if there's anything cooking or if there's something I can help with.
I think there are quite a few users who are suffering from this.
If the devs need anything they have plenty of people to ask for debug info, etc.
I just wish someone had the time to have a look at this
have got the same issue, new screen, sensors stopped working, all the sensors that is, light, proximity, g-sensor, compass. and everything works in winmo (except the compass, don't know why) the interesting thing is, the proximity sensor does work, it just doesn't turn off the screen, but it does turn off the touch screen, and the g-sensor actually seems to work, i can calibrate, and the relevant files are updated (in /data/misc the bma150_usr and the akmd files are created and/or updated) and if i move during calibration, it is aborted. it seems as if there is something broken in software because the chip data is still being read and used somehow, just not piped to the right places...
Every sensor work fine here with except the g sensor
I guess its a kernel issue and not hardware relates
it work perfectly on wm6.5,but not work on any andriod rom.
i have the same issue
so no one is helping us???
i have the same issue too...
Same here works fine in windows but android will not work.
Also have screen replacement
SOLVED
my issue is solved now after motherboard replacement.
a few notes:
- as i eventually discovered, there was in fact a problem with the compass (aka the magnetic field sensor) which didn't work in any os. with this issue i had a good reason to send the phone back to the repair shop and they replaced the motherboard under warranty.
- i don't know what solved the issue, it's either [A] the working compass (which is somehow needed for auto-rotation to work - in android) or the new motherboard (which does not have compatibility issues with the new screen - in android).
so, please check wheather your compass is working or not.
if not, reflash to stock and send it back for a warranty repair.
I replaced the digitizer in my phone myself and the G-sensor works for me in Android.
LOOOOOOOOOOOOOOOOOOTS of threads and posts since 6 months and still nothing. About those sensors problems / screen replacements and still nothing... It's so sad, the HD2 is dying slowly. Lolz, let's keep the faith!!
+1 same problem...
Any solution???
Thx.
Same.
perfect on Windows.
not working, gyroscope, compass, screen rotation on any android.
no problem with proximity and light sensors.
I had tried screen rotations witout main flex (that holdss, vibration, camera, volume, wifi, buzzer)
And the sad point is I had replaced LCD-Digitizer together these are taken from a dead hd2. So my replaced LCD is 100% orijinal. I did not seperate chasis-button flex also.
Hi,
I own HTC HD2 and recently it stoped working and i had to send it to be repaired. They have changed the board because the CPU has malfunctioned. Since then accelrometer is not working in any rom. It only works in Windows. I could not find any answers except that the new board installed could be unsupported in android builds.
Any help is appreciated.
Help
duh2010 said:
Hi,
I own HTC HD2 and recently it stoped working and i had to send it to be repaired. They have changed the board because the CPU has malfunctioned. Since then accelrometer is not working in any rom. It only works in Windows. I could not find any answers except that the new board installed could be unsupported in android builds.
Any help is appreciated.
Click to expand...
Click to collapse
I also found out that several more users in Serbia have this issue. Anbody else? Plese help?
This is a Driver issues, maybe the new board has some different Component, but is not only the g-Sensor, the Magnetic Field and Orientation aren't Working, this kind of problem take to long time to be fixed, now that the developers are Focused on ICS. I'm thinking to sell my HD2 and Buy Another one.
ataria2 said:
This is a Driver issues, maybe the new board has some different Component, but is not only the g-Sensor, the Magnetic Field and Orientation aren't Working, this kind of problem take to long time to be fixed, now that the developers are Focused on ICS. I'm thinking to sell my HD2 and Buy Another one.
Click to expand...
Click to collapse
Maybe it will work in ICS if only we had the patience to wait.
It is wery strange to use a phone that does not have any rotation whatsoever. You have to try and take a picture or to watch a klip that is stuck in portrait mode and want turn. I cant belive that no one has solved this yet. PLEASE HELP!