First of all, sorry if this thread is out of place, but I'm not sure where else to turn.
My HD2 worked terrifically with FroyoStone 3.2, Hastarin 7.6 up until last Wednesday (5 days) ago. Then I started to experience, and have not been able to fix, serious TS lag issues.
Symptoms: I hit the unlock button, swipe to unlock, and the touchscreen will be responsive if I KEEP using it...if I pause for up to 3 seconds, the screen is no longer responsive. I have to relock the phone, unlock, and then swipe again to get it to work.
The touchscreen works perfectly fine in Windows Mobile 6.5. (Energy 2361X)
Attempts to fix: I've formatted the SD Card inbetween trying all of the following items-
1) Switch to MDJ ROM with MDJ kernel
2) Switch to Bluetopia ROM (0.5, 0.6 & 0.6.1) with Hastarin 8.0 OR 8.1
3) Switch back to FroyoStone 3.2 with kernel that comes with it
4) Update Radio ROM
5) Update to new Energy WinMo ROM -- after running Task 29 first.
Today, I purchased a new SD Card, loaded it with a clean install of Android, still have issues.
Also tried:
1) Turning off all LED notifications
2) Disabling Auto brightness in WinMo and Android
3) Disabled Screen Auto-Rotate
Honestly, I'm all out of ideas, and I hope someone in the community has a way to help out. I find it so odd that the touchscreen works great right after a "wake-up" as long as I keep it constantly stimulated...then fails to respond if I let it sit for more than three seconds. Is this a polling issue?
All ideas are appreciated. Thank you
This probably belongs in the Q&A forum, not development.
Moved.
For future Googlers and the sort who are researching this issue, the thread has been placed here:
http://forum.xda-developers.com/showthread.php?t=833068
Thanks.
Hello... First of all I'm not a noob... I have this weird issue: When I turn on my screen, it sometimes doesn't respond from first touch ( but the second always works )... Not matter how much I wait after lighting the screen it doesn't respond from first touch (occasionally) :S... For some reason this only happens on gingerbread, froyo runs like a charm and windows mobile and WP7... I have tried litterally everything: I have tried like every gingerbread build, task 29, tried several radios, reHSPLed my device No matter what I still have this issue :S ... It can't be a hardware issue coz froyo, WP7 and wm run gr8 and its not wake up lag... I have done my searches before posting but found nothing... Its a weird issue, not a big deal but very annoying coz I don't wanna be stuck on froyo forever ... P.S: I even tried the gpc 2.3.4 build but having same issue... I'd appreciate any reply Anyboddy experiencing same issue?
so after yukis zune updatable mango mod came out i flashed it ( thanks yuki &xb) but was having terrible heating issues ( with heavy wifi use or even charging long periods) and was wondering a. has anyone else had this issue b.has it been resolved in their new release
ive since went to hyperdroid (a GREAT simplistic android rom) but i miss the ease and flow of WP7. BUT as i dont wanna fry my baby i need input.
oh, and i hadnt had the heating problem with ANY other WP7 MOD so ive deduced its not a simple uncorrectable driver issue. again thanks for any input guys ... and girls.
come on guys :'( (edit)161 views and not even one smart answer. im just trying to save my nand from the horrendously hard process of going from Android back to WP.
please a simple yes or no is all im looking for
Hello! I would like to draw your attention to very annoying bug for all users, who uses Stereo Bluetooth Headsets (A2DP BT Headphones) with Mango and later versions of WP7.
The bug appears if your headset is connected & you are using zune to listen music via A2DP. You need to start track, listen sometime and then pause (never mind which way you use to pause - hardware buttons on headset or tap the pause button in zune or lock screen.
If you wait some time (minute or two) and then resume playback, the phone will freeze and after 5-6 secs reboots. This bug does not appear if you don't use A2DP/Bluetooth headset for listening. So it is Zune or bluetooth stack/radio combination bug, but it is very-very annoying.
Today I flashed about 20 different ROMs and discovered, when the bug appeared.
I flashed oldest ROMs since NODO. This bug appeared after first Mango ROM out. In NODO and PRE-MANGO (Green Mango) ROMs everything works properly. (Tried DFTs NODO & Green Mango ROMs (7392 and 7592 builds).
The radio version for 7392 and 7592, which works properly (without this bug) is: 5.51.09.29_22.32.50.10U (A.102.0.D4)
I hope this info will help ROM developers and DFT Team to fix this distressing bug.
Thank you very much!!!
Added some summary stats about Windows Phone builds:
BUG EXISTS:
7740 [Ultrafruit Based, almost all ROMs at the moment], 8107
A2DP WORKS PROPERLY (BUG DOESN'T APPEAR):
8779 [POST-TANGO by ansar] - BUG FIXED
7720/7740 [which based on Green Mango drivers, NOT Ultrafruit, I found only HD2O_WP7_1.25_LEO71_7740 from HD2Owner]
7592 [Green Mango from DFT]
7390 [NoDo]
It will be interesting to test this bug on first Mango ROMs, which were based on NON-Ultrafruit contents (builds 7720 for example, HD2O`s earlier ROM or any else).
This is ROM is not based on Ultrafruit and there is some probability that A2DP works OK there. I am downloading and flashing it right now and I`ll post the testing results here later.
UPD: my estimates about the problem is connected to Ultrafruit base have been confirmed! I've found a mango rom without this bug (I flashed HD2O_WP7_1.25_LEO71_7740 ROM, that is last version of HD2O Mango ROM NOT BASED ON ULTRAFRUIT)
Very nice of you to bring to the attention of the devs to this critical bug. A lot of us use bluetooth devices and this bug renders the device useless.
How about Ansar's rom? Have you tried it? The first versions i tried were ok bluetooth-wise and it is 8107 i reckon. It suffers from various other problems though and v6 i tried had reboot problems due to Cottula's touch drivers propably. Ansar states he has implemented most drivers from htc titan.
Good luck to all of us that want a fully working phone
[/COLOR]UPD: my estimates about the problem is connected to Ultrafruit base have been confirmed! I've found a mango rom without this bug (I flashed HD2O_WP7_1.25_LEO71_7740 ROM, that is last version of HD2O Mango ROM NOT BASED ON ULTRAFRUIT)[/QUOTE]
Was 1.26 based on ultrafruit??????
Yuki-xbmod rom works without an issue also, with all updates up to 8107 and SP1 drivers too. I test it for 2 weeks and you can use Bluetooth as you will and it will never freeze or reboot.But it has no fullunlock so is quite limited for testing purposes
It's a pity xbmod has abandon this beautiful rom, lots of work wasted. I don't think HD2O's project is similar to any ways.... so sad
indeed, yuki xbox rom has worked fine, this all started when ultrafruit came about and people started using it as a base.
whats slightly more frustrating is that when ever this gets brought up in the approperate threads for each rom it gets ignored.
I was just about to do a new thread similar to this so thank you for doing this.
fair enough if the developers do not use BT for this and thus dont have the problem but perhaps a prudent course of action would be to communicate with us to see if we can narrow down what is going wrong... say the word an ill bend over backwards to help!
alyn99 said:
Was 1.26 based on ultrafruit??????
Click to expand...
Click to collapse
My mistake, 1.26 is also not based on ultrafruit, but the next version and later versions are already based on Ultrafruit. Today Cotulla answered in his twitter, that the next ultrafruit ROM will be based on Schubert drivers and this bug seems to be fixed.
dark.angel said:
My mistake, 1.26 is also not based on ultrafruit, but the next version and later versions are already based on Ultrafruit. Today Cotulla answered in his twitter, that the next ultrafruit ROM will be based on Schubert drivers and this bug seems to be fixed.
Click to expand...
Click to collapse
Thanks for clarifying. I guess we'll have to wait for a working rom and use the old ones until then. This Bt and low incall issue has frustrated me so much that I bought an HTC Titan today and will just be using the WP7 as a backup until things get sorted.
alyn99 said:
Thanks for clarifying. I guess we'll have to wait for a working rom and use the old ones until then. This Bt and low incall issue has frustrated me so much that I bought an HTC Titan today and will just be using the WP7 as a backup until things get sorted.
Click to expand...
Click to collapse
I really appreciate, that you've tested the almost every ROM for the BT-Bug and reported this. I'm with you and for me this funktion ist also necessary. I'd say a little more patience and the new WP7 ROMs will be good.
The Titan is also a nice device...but please don't backslide ;-)
alyn99 said:
Thanks for clarifying. I guess we'll have to wait for a working rom and use the old ones until then. T
Click to expand...
Click to collapse
TitusO said:
I really appreciate, that you've tested the almost every ROM for the BT-Bug and reported this. I'm with you and for me this funktion ist also necessary. I'd say a little more patience and the new WP7 ROMs will be good.
Click to expand...
Click to collapse
Yes, I think this bug will be fixed soon. The most important thing is that we know where it appears and the developers (firstly Cotulla) confirmed that they are working on it now
Let's hope and say thanks to developers! I think the WP7 rom will be fully usable and perfect in the nearest time.
TitusO said:
I really appreciate, that you've tested the almost every ROM for the BT-Bug and reported this. I'm with you and for me this funktion ist also necessary. I'd say a little more patience and the new WP7 ROMs will be good.
The Titan is also a nice device...but please don't backslide ;-)
Click to expand...
Click to collapse
Actually, the Titan is a bit of a problem for me now as I realized on Tmobile US it won't do 3G, otherwise I like the phone. So I am bouncing back and forth between HD20's V1.26 on the HD2 and the Titan. In so many ways I like the HD2 better - ability to run 32gb memory, etc. Just curious as this is first time I tried V1.26 - so far it is AMAZING rom - bluetooth rock solid, sound perfect, incall volume perfect - what is wrong with the V1.26 rom and why did all the devs feel the need to "upgrade" the newer roms and thereby disable bluetooth functionality and incall volume?? I just don't get it. Newer is not always better.
HD20s V1.26 gives me 8107 Mango and I can't see any feature difference between it and all the newer roms, what am I missing?????
Edit: Only bummer so far on V1.26 is that I can't do a backup - certs missing error message.
At least the bug has been fixed in Post-Mango builds, don't know about earlier ROM's (I was using Android ICS) but I confirm, that ansar`s Post-Mango ROM works with Bluetooth A2DP perfectly!
Hi,
I recently installed the pdaimatejam HTC HD2 WP 7.5 ROM 7.9 (Tango build 8773) (thread link here: http://forum.xda-developers.com/showthread.php?t=1356833 ) and it's working pretty much flawlessly except for the fact that when I start a call and raise the phone up to my ear, the display is supposed to shut off, to prevent accidental pressing of the on-screen buttons, it stays on.
Has anyone else experience this problem or has a solution for it?
Thanks in advance.
Screen doesnt work after booting on new Pdmatejam ROM on HTC HD2
Hi,
I installed new Pdmatrejam ROM (link: http://forum.xda-developers.com/showthread.php?t=1356833) and after two working hours screen lagged and nothing helps. I restart my phone but nothjing changed screen still doesnt work. Please help!!
P.S. sorry for my bad english.
i have ROM installed 8 days and dont have any problems (dont count testing days before release in that case almost 2 weeks working without problems)...
lags can be related to problem with slow SDcard (sdcard is phone memory)
did you test SDcard with WP Bench?