yashsingh1/xdaforums huggingface dataset:
[G2 and Desire Z Q&A, Help & Troubleshooting] cjward23:
I'm loving nightly's. I love the excitement of getting to flash something everyday I do believe i may be suffering from [URL="http://xdaforums.com/showthread.php?t=652857]ORD[/URL] . And generally everything has seemed fast and stable. Not sure about battery life yet because I'm flashing on a daily basis.

Nightly's or CM6.1.1 everything cyanogen is awesome
[G2 and Desire Z Q&A, Help & Troubleshooting] tvdang7:
i REALLY like the gingerbread text selection tool. Nightly is decently stable so yea.
[G2 and Desire Z Q&A, Help & Troubleshooting] stshannon:
I stick with the Stables (or at least the RC's [release candidates]).

I rely on my phone too much to have FC's or to have Navigation force close, or random reboots etc.

CM 7 by this point, i give, is certainly stable. From the tweets and rumors, i would expect a RC to be released soon.

But, i typically will wait for a stable release, unless there's some new feature that i just cannot wait for (this was the case from CM5 to CM6 where the camera was VASTLY improved). But i think as the OP stated, there's nothing incredible that i cant wait for a stable release for.

However, this post is purely subjective, and you will get ALL kinds of opinions. Every persons needs, and wants are completely different, and therefore you will likely get a wide variety of responses.
[G2 and Desire Z Q&A, Help & Troubleshooting] HotShotAzn:
When I had my HD2 on WM6.5, I got used to flashing NRG's every few days...so I also got used to have scripts to back everything up.

With my Vibrant, TW's releases were not as frequent, and that was very much welcomed.

I'm finally enjoying a stable release (CM6.1.1) and am not sure I am ready to start flashing every day again.
[G2 and Desire Z Q&A, Help & Troubleshooting] stshannon:
On a side note, Titanium Backup makes backing everything (and restoring) a CINCH.
[G2 and Desire Z Q&A, Help & Troubleshooting] HotShotAzn:
Yeah, i love TB. It took me so freaking long to realize that I shouldn't just do a blanket restore on everything as the system files tend to get wonky. One thing I hated about Samsung (and the Vibrant) was that you had to Odin to stock before you flashed if you wanted a "clean" flash. Otherwise you get some hanging processes or stuff like that.

For everyone that is flashing the nightlies, are you guys restoring or doing any kind of wipe to stock before hand?
[G2 and Desire Z Q&A, Help & Troubleshooting] Rantanplan1980:
So you only restore the user apps and not the system apps?
[G2 and Desire Z Q&A, Help & Troubleshooting] HotShotAzn:
User: Restore apps and data

System: Restore data only - and I choose which system apps to restore
[G2 and Desire Z Q&A, Help & Troubleshooting] marquis.hagetaka:
nightlies, @ 1st, i stayed away from them now, i look forward to them
[G2 and Desire Z Q&A, Help & Troubleshooting] borisimo:
CM 6.1.1 here, thinking about trying out the nightlies, but I just hate having to re-do all my screen shortcut and widgets. Will probably wait till an RC.
[G2 and Desire Z Q&A, Help & Troubleshooting] Zacky32:
I'm using CM 6.1.1 and I'm loving it, will wait for a more stable CM 7.
[G2 and Desire Z Q&A, Help & Troubleshooting] BootloopedMillennials:
Started with CM6.1.1 but moved onto the CM7 Nightly's since Build 1. I keep up to date with every CM7 Nightly Build. What I have noticed based on benchmarking apps is that CM7 scores lower than CM6.1.1. This is with the updated Quadrant and SmartBench 2010 that is compatible with Gingerbread. The Quadrant score in my sig was with a early CM7 build and a non gingerbread optimized Quadrant. In day to day use I dont notice much speed difference though.
[G2 and Desire Z Q&A, Help & Troubleshooting] dustrho:
I ran with CM7 Nightlies for about a week, but I truly feel and believe that CM 6.1.1 Stable runs quicker and smoother than CM7. Because of that, I restored my nandroid backup of CM 6.1.1 Stable. Much happier with that.
[HD2 Android Q&A, Help & Troubleshooting and Genera] FreakyFerret:
Update: According to info from Cotulla, MAGLDR does not initialize the touch screen since it doesn't have touch input. WinMo or Android (linux kernel) initializes the touch screen. The failures I'm seeing in Android NAND builds must be due to bug in those builds. I've just downloaded 14 different NAND builds (clockwork and not) to test out again. I'll report results later.

See Cotulla's post on the matter here. Thanks for all the help on the matter to everyone.

Update 2: Here is the link to my post testing a handful of builds and what I found.

Note: Please take the insults elsewhere. I'm trying to actually get some help and offer it. I never said MAGLDR caused any damage to my device. It's a simple bug which once pointed out can be researched and fixed.

The work the DarkForcesTeam has done is amazing! We're talking thousands of hours of work collectively. Some commercially available products don't receive such dedication. I just want to try to help out as best as possible to make it an even better product.

When I use MAGLDR, my touch screen becomes over-sensative. It'll randomly select parts of the screen as having been touched when they're not, like a "ghost hand" was using the device..

It is not a bad digitizer. It is not a hardware defect. It is a problem with MAGLDR. I've confirmed this existing with versions 1.11 to 1.13. The problem only exists when using MAGLDR. If WinMo is used, problem goes away.

Here's what I did:

1) Task 29

2) WinMo 6.5

3) Ran an Android ROM from SD (Copes AOSP SD HD2 GB232/CM7 A2SD at

http://xdaforums.com/showthread.php?t=898831

Everything is fine. Screen is incredibly precise.

4) Task 29

5) MAGLDR 1.13

6) Change SD build to boot from MAGLDR instead of HARET

7) Boot up, everything comes up fine.

8) Screen goes crazy.

Since I didn't change the build I was booting, and only changed MAGLDR, there should have not been any touch screen issues.

9) Task 29

10) WinMo 6.5 reinstalled

11) Change SD build back to boot from HARET

12) Boot the Android SD build

13) Screen is very precise once again.

Does anyone know if the DarkForcesTeam (DFT) has commented on this issue before? Are they working on it? Are they even aware of it?

Has anyone else had any issue like this?

I'm using one of the first HD2s to come out for T-Mobile in the US.
[HD2 Android Q&A, Help & Troubleshooting and Genera] JhonKa:
My touch screen stopped working during windows phone 7 and i cant figure out a reason why. Im running magldr 1.12
[HD2 Android Q&A, Help & Troubleshooting and Genera] roloracer:
It might be a mgldr booting SD build issue, I've been using cyanogenmod 7 android 2.3 nand for a month without a single issue..
[HD2 Android Q&A, Help & Troubleshooting and Genera] dung8604:
Same here
[HD2 Android Q&A, Help & Troubleshooting and Genera] FreakyFerret:
When I use a pure NAND build, the problem is there too.

Anytime I use MAGLDR, it happens.

I don't like Sense, but I'll give the one you recommended a try later tonight.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Sukuya:
havent had the issue either.. BUT!!! cause its winter here whenever i come from outside and i use my phone i get random presses on the screen cause its wet, when i wipe it off it just behaves..
[HD2 Android Q&A, Help & Troubleshooting and Genera] t0ny0:
Alright... my phone just died :(

Had the setup that you can see on my signature, and touchscreen just stopped responding randomly. First it was once or twice a day, now its like every other time that the screen is sleeping and I try to wake it up.

I did Task29, flashed official WinMo radio, and now the problem still exists. Every other time that the phone goes to sleep - i press any button, the screen lights up, but like the touchscreen function just wont work.

I know for sure that I am not the first, second or even tenth person that has this problem after running NAND-android. Maybe this should be put on the android development thread, so people wont break their phones.

I have no idea why is this happening, but I know that its time for a new phone. Hopefully T-Mobile will give me a new phone, which I can sell and get a native android phone. I hate windows, the reason that I got this phone was the screen size, which no other android phone had on t-mobile back when I got it.

So, one more time

PEOPLE, MAGLDR WILL CORRUPT YOUR TOUCHSCREEN IF YOU USE IT

With that said - I would like to thank everyone that made android on HD2 possible, and specially cotulla, his team, mdj and hastarin, I had a blast using it :) You guys ROCK!!

Edit: After flashing winmo - I kept getting problems for the first 1hr.

Now it seems that freezing is gone on Win Mo.

Will update later.
[HD2 Android Q&A, Help & Troubleshooting and Genera] psykick5:
I had my touchscreen do that and just stop working BEFORE magldr even came out. A person I know who never hacked or did anything to his phone had this problem. It's a hardware defect and it's just coincidence that it broke while you had magldr on your phone.
[HD2 Android Q&A, Help & Troubleshooting and Genera] jose makalolot:
not again...

if MAGLDR makes those weird things to your phone then DON'T USE IT!!!

I have been using MAGLDR since it came out. EVen flashing a lot of builds everyday to test but never had any issues with the touchscreen.
[HD2 Android Q&A, Help & Troubleshooting and Genera] hd2k10:
Same, I've flashed well over 25 times and my Touchscreen hasn't had any problems.

MAGLDR is safe, end of story.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Danation:
Confirmed? Really? Because you think it happened to you?

This is anecdotal, and it is definitely not concrete in any way. This is pure FUD, nothing more. You should consider thinking before you post ridiculous claims that something has been "confirmed."

This has happened to ONE person on ONE phone, and pretty much everybody else is telling you that you are wrong. Does that sound confirmed to you?

It annoys me that you would smear somebody else's fantastic work because your phone had a freak accident. Go blame the government or something, just stop blaming magldr. Thanks.
[HD2 Android Q&A, Help & Troubleshooting and Genera] LiFE1688:
Buy a WinMO 6.5 phone stick to WinMO6.5 if you want it to work as intended by manufacturer.

If you want to tinker, then be prepared to tinker it to its death.

If you can't afford a new phone, don't mess with it.

If you can't be without a phone for even 1 day, don't mess with it.

If you want to blame, then blame yourself. You are just messed up.
[HD2 Android Q&A, Help & Troubleshooting and Genera] FreakyFerret:
Danation and hd2k10, I'm not smearing anyone. My phone is fine. There is a bug in MAGLDR. One I'm sure the DarkForces Team can fix if someone can provide some good feedback. Read what I posted again. I'm asking to help DFT solve this software bug. Not saying it's bad.

And I did confirm the problem only exists when using MAGLDR. It runs fine on most of the phones, but there are others aside from myself who have had problems with it. We would love to see MAGLDR working perfectly and I personally encourage anyone who it works for to continue using it. I wish I could use it and want to do everything I can to make that a reality.

psykick5, did you try flashing a WinMo ROM or Android SD build to see if your screen returns to normal?
[HD2 Android Q&A, Help & Troubleshooting and Genera] t0ny0:
Maybe you should read around and see that its not ONE person on ONE phone? :p

Also, I have flashed many many times, on HD2 and other devices, the fact of the matter is that it happened. Its not just the OP, its not just me, there are plenty of posts in here, saying that exactly the same thing happened to them /just search and you will see/.

Also, I would hate if someone is talking bad about someone elses fantastic work, and this is why I thanked everyone that helped getting android on our HD2s. There is no disrespect, I was just trying to warn other people that this has happened, and not once or twice. The fact that it didnt happen to you - means nothing :) It wasn't happening to me either, and I even wrote an angry comment to one of the people that was complaining a while back, and ha, guess what happened today :D

I agree, that probably "confirmed" is not the write word in here, but what we are trying to do, is just warn other users, AND DEVELOPERS so they can look into it, what if the problem is with MAGLDR? Hopefully its not, but thats a big coincidence. What if by some way its overheating a chip or something? You never know, since you are not a developer, I'm don't think that you can be 100% sure about something that is not open source, and you can't see how its made or what it does to the device.

So cool down, and if you can't help - there is absolutely no need to post negative comments.

Thank you,

Tony.

Edit: This is not for you only, its for all the other negative comments that are before yours. And after yours :D Y'all need to chill out, we are here asking for help. I have donated to a good amount of developers in here, and I am not trying to disrespect any of them, as I said in my previous post. I appreciate their work, but as far as I'm concerned, and the few other guys before me - there is a bug in MAGLDR, and it would be nice if Cotullas team can take a look at it.
[HD2 Android Q&A, Help & Troubleshooting and Genera] HectiQ:
Must be a T-Mobile problem. I don't have it. Sorry for you tho, wish I could help.
[HD2 Android Q&A, Help & Troubleshooting and Genera] datas0ft:
I have EU HD2 and noticed same problems. Not all time and can say that i think its not MAGLDR problem. More NAND roms side. You ask why.

Tested many roms, not one. No, i dont go say these are bad. just tryed find wich works best for me.

With win 6.5 and win 7 roms i dont seen this problem but with android nand roms yes. Tested custom win 6.5 + android sd too. With that siutation dont had these problems.

Why i try here too is that i think its clued with another problem too, described on this hd2 forum on diffrent places. One is this thread.

Also i have read on some NAND roms thread that rom cooker are increased screen sensitivy or smth. Cant find right now it but if i remember it then i go back and post link.
[HD2 Android Q&A, Help & Troubleshooting and Genera] TheATHEiST:
Not all this sh1t again.

IF there was a "bug" in magldr for TS then it would affect the MAJORITY not the MINORITY.

Also the title of this thread is retarded, you havent "confirmed" a bloody thing other then your ability to presume something and then jump to a wrong conclusion.

EVEN if there is a bug would be a very small one and not one that DFT should waste their time on atm.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Screemi:
your understanding of a bug is that it shows up on the majority of a system? that's utter bull****! sorry.
[HD2 Android Q&A, Help & Troubleshooting and Genera] jose makalolot:
I have a tmous HD2 and don't experience that crap at all!
[HD2 Android Q&A, Help & Troubleshooting and Genera] FreakyFerret:
10chars...
[HD2 Android Q&A, Help & Troubleshooting and Genera] mattfmartin:
Yea nothing wrong with mine.
[HD2 Android Q&A, Help & Troubleshooting and Genera] cavemaneca:
I just finished ordering my replacement warranty touchscreen. Pretty much, my screen stopped responding a few days ago, re flashing the ROM helped temporarily. After it stopped working completely, even re flashing back to stock did not help. The only thing that seems to help is leaving the phone off for an extended period of time, but the problem will return.

Anyway, as part of the discussion, I've seen people report this exact same issue almost weekly throughout the entirety of the android development for this device.

More likely than not, this is a manufacturing error, where the touchscreen for all versions of the HD2 is likely to fail due to whatever faulty design, since it effects devices using different touch screens too.

Like my own phone, it's likely that these devices have failed purely due to coincidence after they updated to the newest version of their ROM, installed MAGLDR for the first time, updated MAGLDR, or whatever it is this time.

(Also, the conspiracy theorist in me thinks it's part of planned obsolescence, and that the few of us lucky enough to have it break BEFORE the warranty has expired only escape the same fate that a majority of these devices will experience down the road....)
[HD2 Android Q&A, Help & Troubleshooting and Genera] hungtd:
Did you read terms before using MAGLDR ?
[HD2 Android Q&A, Help & Troubleshooting and Genera] crow6:
Somewhere around I read TouchScreen _can_ be damaged because people are overclocking HD2's (and overheating electronics). Maybe You just flashed some "factory" overclocked ROM (now it's standard that Android's can be clocked up to 1,5Ghz)?

BTW 1 or 2 breaks and 100s (1000s?) working HD2's. If devs will check every single fault reported be every single user, they will get no time for developing new features...
[HD2 Android Q&A, Help & Troubleshooting and Genera] FreakyFerret:
Just installed Typhoon 1.7 and it seems better. Screen still has touch issues, but if I turn off screen (using red hard button) and turn it back on, screen responds properly for a couple of minutes.
[HD2 Android Q&A, Help & Troubleshooting and Genera] crow6:
Maybe it's really overheating (when screen is on)?
[HD2 Android Q&A, Help & Troubleshooting and Genera] t0ny0:
I agree, this is why we have this thread, to see if there are other people that are having the same issues :) If we end up being a good amount of people - some of the devs might look into it.

I never had an overclocked kernel working on my HD2. I have killed my G1 with overclocking it, so I never overclocked my HD2. And I always made sure that the kernel that I put on is not OCed.

I only tested once with overclocking, and other than getting better quadrant results - it really doesnt make a big difference. That was for like 5mins, and it was at ~1200.

Also for the other posts - I have been running windoze 6.5 stock for about 24hrs now, and other than the first 1hr when screen was freezing - I havent had any issues. Its working perfectly fine now. I changed SPL to the 2.8.0000(i think) - which is the stock one, its not the HSPL.

I will re-flash Android again today, and will keep you guys updated on how are things going.

Yes, I have. I am not keeping anyone responsible, and I am so grateful that we finally have that. All I am saying is that I think that there is a bug, and I realize that until more people get that issue - nobody will look into it. Thats completely fine with me, I am just warning other people that this might happen to them :) I am looking for support and help, and am not going around blaming anyone for my own decisions to flash or not to flash.
[HD2 Android Q&A, Help & Troubleshooting and Genera] elgrego4:
I was using gauners hd nand rom and all was fine. Then i tried with desire z rom and everything went nuts, the screen wehnt jittery, random selections by itself not to mention the weather constantly popping up. So today I flashed DL.DesireZ.v3.4.final and im still having the same problems. I wish there was a simple answer for it but i dont now if it is maglar?
[HD2 Android Q&A, Help & Troubleshooting and Genera] crow6:
In theory is difficult to destroy read-only device like TouchScreen - it's just pooling device - not writing...

Good test will be flashing Windows Mobile 7 and check if it will be working...
[HD2 Android Q&A, Help & Troubleshooting and Genera] elgrego4:
I've flashed another rom and still having these problems
[HD2 Android Q&A, Help & Troubleshooting and Genera] jigners:
i think the problem arises on step 6 from the OP

MAGLDR is made not primarily made to boot android via sdcard:p

never even thought magldr could do that, :o

magldr was to boot android into nand

please stop this hearsay!! once and for all

I have an EU HD2 with HSPL3 2.08HSPL

been shifting win 6.5, android via sd, used MAGLDR 1.11 (first released) to load

android via nand, MAGLDR 1.12, MAGLDR1.13, now using windows 7, at times

shifting back to android nand to test the development of NAND builds Desire Z and

Desire HD. Never, again Never, encountered this problem. full stop;)
[HD2 Android Q&A, Help & Troubleshooting and Genera] FreakyFerret:
MAGLDR 1.13 is designed to load an Android build from SD card if the build is designed to be loaded by MAGLDR. The build I tried is designed as such. It has files for booting using WinMo and HARET and another set of files for booting from MAGLDR. When using HARET, screen is fine. When using MAGLDR, screen has the usual wonkiness. As an example, the device acts as though someone has pressed a part of the screen when no one is touching it.

Using any OS the problem is always present when booting with MAGLDR and never present when not.

My discussion on this issue is not hearsay. My findings can be reproduced reliably and without fail on my device. I'm not saying MAGLDR caused any damage to my device. In actually it did not do anything since I can fix the problem by changing boot option. Additionally there are a number of other individuals experiencing the same problem. There is a bug in MAGLDR. It's a minor one only affecting a small group of people and is more annoyance than horrible disaster. The fact such a problem exists with such a small influence is reason to praise the DarkForcesTeam and not put them down as many people think we are. I really don't understand the hatred we are getting on this issue. Reporting bugs is how things get fixed and become better.
[HD2 Android Q&A, Help & Troubleshooting and Genera] elgrego4:
I think its a phone fault, Ive flashed back to a standard winmo rom and its still doing the same problems as i said earlier. I'll be calling HTC tommorow
[HD2 Android Q&A, Help & Troubleshooting and Genera] FreakyFerret:
If you have the same problems in WinMo (or Android on SD using HARET), then it's not the same issue I have. The screen problems go away so long as I don't have MAGLDR on my phone. If your problem is persisting, it is most likely a hardware issue. Try to see if your carrier will replace it for you under warranty.
[HD2 Android Q&A, Help & Troubleshooting and Genera] dharvey4651:
Me either. I've flashed maybe 20 different ROMs since I've switched to Android and probably close to 1500-2000 times when running Windows Mobile. Now I'm running Android with CWM and I can tell you I've never had a single problem whether it be with my touch screen or my hardware keys, etc..

To all who are experiencing this issue - Try every NAND DAF and CWM build, NOT an SD build converted to work with MAGLDR. If you experience the same exact problem with every single build and every single version of CWM and every single version of MAGLDR then maybe, just maybe.. You have discovered a bug.

I'm EXTREMELY tempted to say hardware-defect here... And I highly encourage users experiencing touch screen issues to restore their devices to factory stock and see if you can get your carrier to replace it via warranty or insurance.
[HD2 Android Q&A, Help & Troubleshooting and Genera] FreakyFerret:
Dharvey, thank you for your constructive comments. They are appreciated esp in this thread. I do experience this in every instance of using MAGLDR. I've been trying it for a month now with several different builds: winnow and android SD and android band. The only common factor when experiencing the problem is MAGLDR. I used a build that could switch between it and haret to rule out issue with the build itself.