yashsingh1/xdaforums huggingface dataset:
[HD2 Android Q&A, Help & Troubleshooting and Genera] roloracer:
I've been flashing my hd2 since day one of release, went to sd builds about october last year, switched to MGLDR right after new years running CyanogenMod7 and never had any screen issues, maybe MGLDR is reacting different with some devices, who knows, maybe is a bad batch of hd2's that are having the same problem, I just think that if MGLDR had such a big bug as to messing up touchscreens there would be a much larger amount of users with the same issue. I'm not saying that the OP is wrong for saying MGLDR is responsible for his screen issue but if he keeps recreating the issue every time he uses MGLDR, then he has the right to come to that conclusion , I know I would be pretty upset and would want a solution to my problem if I was having screen issues like the OP :cool:
[HD2 Android Q&A, Help & Troubleshooting and Genera] FreakyFerret:
Thanks roloracer. I'm thinking it's a design difference with earlier TMOUS models. I got one of the models on opening day.
[HD2 Android Q&A, Help & Troubleshooting and Genera] apallohadas:
Honestly, it doesn't sound like you want any input that doesn't jive with your pre-conclusion.

Exactly what builds did you try? Give MDJ's cynogen build a try, the one dated Jan 22. Some people have reported problems, but none claiming that MAGLDR broke their touch screen.

Also, give 1.12 a try instead of 1.13.
[HD2 Android Q&A, Help & Troubleshooting and Genera] FreakyFerret:
I tried MAGLDR 1.11, 1.12, and 1.13.

I tried several builds of MDJ's as well as HyperDroid, Typhoon, Stock Gingerbread and about half a dozen others I don't recall.

I apologize if I come off ad unwilling to listen. Part of the reason I posted here was to see if anyone had a solution. I appreciate your suggestion to try other builds.

:( I'm just not hopeful I guess.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Danation:
Yeah... you're the same person who said "PEOPLE, MAGLDR WILL CORRUPT YOUR TOUCHSCREEN IF YOU USE IT" so don't tell me about negative comments.

I would be a LOT more sympathetic if you posted a thread about how something MAY be related to Magldr and that you're wondering if anybody else has had the issue. As it is, all I'm seeing is FUD. Don't make me the bad guy when it's you who is smearing somebody's hard work.

Also... you don't know me, so I think it's ridiculous that you claim I have no knowledge on these topics.

In summary, I suggest you stop being inflammatory and actually respectfully ask the developers of Magldr if they know of any possible causes that could be related to their release.
[HD2 Android Q&A, Help & Troubleshooting and Genera] AngelDeath:
Really? We need now two threads about this? One with 15 pages wasnt enough to beat the dead horse? No disrespect to anyone, but enough already. I have 2 HD2 TMoUS1024, 1 was manufactured before June 2010, the other after June 2010, My SIG has both roms that I installed, and since 1/1/11 I have had no issues with the screen.

Okay nevermind you got DFT, see its really a conspiracy:

Its Darkforces "cue scarey music" that are causing this, they implanted a drone that monitors to see if you have played the tetris game in the bootscreen, if you didnt it kills your touchscreen "cue scarey music again".

Seriously, Can we merge the posts and be on our way?
[HD2 Android Q&A, Help & Troubleshooting and Genera] datas0ft:
Again

I dont want claim or blame DFT team or any NAND rom developer. I just want find what is wrong and where. Is it bug on somewhere or is it hardware problem.

I have two HD2. One bought on UK (not T-mobile version) half year ago. Second on my country (WWE version) year ago. On second i itself changed digitizer and lcd (was bout oem version and was before complected). This second phone i use daily itself. UK version phone uses my son.

I have on both phones installed HSPL3 2.08HSPL. I had previosly on both phones MAGLDR 1.11/1.12 and now 1.13.

I have tested many many different roms over HD2 Android NAND Development forum. With every nand rom i get issues described before on this thread and on this thread.

But i dont have problems with stock win 6.5 rom. Dot want waste time to custom win 6.5.

Dont have problems with win 6.5 and android SD version.

Also i can say with my long time experience with thousands and hundred thousands ethernet users, that reporting about some bug do only 10% users. Others at best times only reading. Mostly go away. And they dont want run over forums (so complicated). They are so lazy and apathetic
[HD2 Android Q&A, Help & Troubleshooting and Genera] elgrego4:
If it helps with this debate, I'll post what htc find wong with my phone. Hopefully it will clear alot of questions up. I will be back on Android as soon as i get the phone back :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] apallohadas:
Your problem sounds like a bad proximity sensor, not MAGLDR killing your screen.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Cotulla:
Any of this issues are not related to MAGLDR, because current MAGLDR versions don't use touchscreen at all.

But you definitely forgot one thing: when you run Android via Haret, the touchscreen initialized by WM65 before.

It's actual general reason why touchscreen can have different behavior with Haret run and with MAGLDR run. Primary it means lack of touchscreen initialize in the linux kernel.

btw MAGLDR SD and NAND run are same: difference only in the storage media.
[HD2 Android Q&A, Help & Troubleshooting and Genera] bugsounet:
google translation:

-------------------

I have the same problem with touch screen.

HD2 no overclock (998 MHz)

I try with win6.5, the problem is the same (stock ROM)

I do not know if MAGLDR is in question or a problem of kernel.

I can't restart the phone with the red button: if I do that the touch-screen no longer works for example ...

my phone is Branded HD2 SFR (France)
[HD2 Android Q&A, Help & Troubleshooting and Genera] t0ny0:
Alright Im almost done testing, here are my findings so far:

Step 1 - touchscreen kinda stopped working - it goes on and off all the time, was running the configuration that you see in my signature.

Step 2 - Task 29, I reflashed my HD2 with SPL 2.08.000 and with Stock T-Mobile Windows Rom.

I was getting the first time I booted, I rebooted again and the freezes were gone.

Step 3 - I installed HSPL and MAGLDR 1.13, with 1.13 recovery, and I went with a different Android Rom. It was CM7 preview by charnsingh_online - the screen freezes came back with first boot, and did not go away after a few reboots.

Step 4 - I did the same thing I did on step 2. Screen freezes went away.

Step 5 - I installed HSPL again with MAGLDR 1.12. Installed recovery 1.12 and the CM7 Preview by charnsingh_online. Screen freezes on first boot, and no screen freezes after that. They are just gone.

This is the reason that I'm thinking that there is a bug with either MAGLDR 1.13 or CWM recovery (I doubt that the recovery can have anything to do with it).

Again I am not blaming anyone for anything, this is just something that I did and it worked for me. The fact is that MAGLDR 1.13 is giving me problems. Maybe there is something wrong with my phone, maybe there is something wrong with MAGLDR 1.13, or maybe there is just something wrong with the combination of my phone and running magldr 1.13 :D

What I also noticed is that when touchscreen is not loading, it seems like its more of a drivers problem than anything else. Since its not killing it permanently, it still works 1 out of 3 times. Its like the phone wakes up, but it forgets to wake the touchscreen. Since now it works with no issues whatsoever - I will simply keep my current 1.12 and will see if problem will come back again :)

Thank you Cotulla for your input on our problem, you sir are the biggest android God that I can think of :D And would like to thank you for giving life to our otherwise useless Wincrap devices :D ::bow down::
[HD2 Android Q&A, Help & Troubleshooting and Genera] apallohadas:
Try it without CWM. If you haven't, then what would be the harm in trying?
[HD2 Android Q&A, Help & Troubleshooting and Genera] t0ny0:
Good point, will do later tonight, as I need my phone on till the end of the day. Hopefully that would do the trick :D
[HD2 Android Q&A, Help & Troubleshooting and Genera] jose makalolot:
Can we now change the title to:

MAGLDR doesn't cause Touch Screen issues Confirmed by Cotulla!
[HD2 Android Q&A, Help & Troubleshooting and Genera] t0ny0:
I agree that "Confirmed" needs to go. ASAP. Wasn't supposed to be there at a first time if you ask me :D
[HD2 Android Q&A, Help & Troubleshooting and Genera] datas0ft:
You didnt read where i say that on winmo (both 6.5 and 7) idont have these issues.

More and again. I just informed that finded these anomalies with android nand. Iwant fin way to away. And not only i.
[HD2 Android Q&A, Help & Troubleshooting and Genera] apallohadas:
According to *you* by the thread *you* linked to:

Nowhere there does it say you tested anything on Winmo 6, 6.5, or 7. Just that your screen turns off on calls.

Edit: I see you mentioned winmo in the thread here. What OS on your PC are you using and are you running the install "as Administrator"?
[HD2 Android Q&A, Help & Troubleshooting and Genera] datas0ft:
Sorry if i was unclear somrwhere.

Actually i use different os-es. Most of time xp. Yes on work 7 and home laptop 7 64 bit. Not need to worry about 64bit os problems. I do this type works every time on win xp compatbility mode.

I understand if my phone sensor broken, but my son phone is untouched inside and acts same.
[HD2 Android Q&A, Help & Troubleshooting and Genera] theboxmodder:
I have noticed a few times where while typing, the phone would randomly press letters 2-3 times. I even tapped an input box, set the phone down and watched it do it a few times. Not enough to drive me crazy but still gets on my nerves from time to time. Though it wasn't present in my SD boot. Only my NAND installs.
[HD2 Android Q&A, Help & Troubleshooting and Genera] andytham:
to add to the stats. I am having MAGLDR 1.12 for NAND WP7 and SD on MDJ's froyo HD 4.6. Most of the time I am on Android and only occasionally try out WP7. My Touch Screen dead since yesterday on both WP7 and Andriod. I have also flash back the stock ROM and the touch screen still not functioning but the buttons and lcd are working fine. The phone is slightly over 1 year and after warranty. I just sent it back to the service center today. It happen not long after installing MAGLDR and WP7. It is 1. WP7 2. MAGLDR 3. Coincidence. Am sure it is going to cost me for the repair.

And 1 more thing to add, I just recently activated the GPS and downloaded a map. could it be 4. GPS?

And btw, touchscreen failure is not new : http://xdaforums.com/showthread.php?t=635426&highlight=digitizer
[HD2 Android Q&A, Help & Troubleshooting and Genera] PoisonWolf:
I have no ghost hand issues, nothing whatsoever. Screen is perfectly normal.

Running an Android nand build. I am not using any CWM. Running MAGDLR 1.11.
[HD2 Android Q&A, Help & Troubleshooting and Genera] wbonney4:
New vs. Ols Models

I am leaning towards the older models of the HD2 having the issue I got the the HD2 the first week it came out and I have the touchscreen issues. Insurance is sending me a new one. I am going to try it out and report back.
[HD2 Android Q&A, Help & Troubleshooting and Genera] djpeezy:
Touchscreen fail

I've been running Magldr ever since it's been out and never had a problem since yesterday when I was using the browser and the phone just started acting up, so i soft reset it. Touchscreen hasn't been the same since. First it seemed like a lockscreen problem and once I could get past the lockscreen it would work, so I flashed different roms to see if the problem went away. Was working up to this morning when I flashed MDJ's cyanogen mod7, drove to my class turned on the phone to check my calls and the touchscreen has been unresponsive since. I have a bunch of missed calls and messages completely inaccessible because of this. From what i've been reading this has happened to numerous persons with completely stock phones. I've had numerous HTC phones and this has never happened. Right now I just need my phone working again,:confused::confused::confused::confused::mad::mad::mad::eek::eek::eek:
[HD2 Android Q&A, Help & Troubleshooting and Genera] akapaul26:
Best post in this entire thread!

I would agree with just about everything!

WHY IS THERE EVEN STILL DISCUSSION ON THIS TOPIC DID EVERYONE MISS THIS POST?
[HD2 Android Q&A, Help & Troubleshooting and Genera] TheATHEiST:
NOT at all!

IF, THIS was a bug in MAGLDR then it would affect the majority not minority.

ie, im referring to MAGLDR and this type of bug ONLY, not "bugs" in general.

So leave your "utter bull****" statements elsewhere please.
[HD2 Android Q&A, Help & Troubleshooting and Genera] br@inmatr:
aMAGLDR boot menu screen

:)First off I wanna say biggups to Cotulla and the team for creating this awesome ROM! Kinda off topic, but it's in regards to the boot menu screen.

I want to wipe the data off the device in order to troubleshoot a bad app that is draining battery power at an alarming rate. It's on an HTC HD 2.

Any assistance you can provide for this annoying issue will be most appreciative.

One more thing, I want to donate to this ROM and/or the dev. Where should I go to do that?
[HD2 Android Q&A, Help & Troubleshooting and Genera] t0ny0:
Alright, my final update for this thread - MAGLDR has nothing to do with my touchscreen issue. I've been reading all week to find out what happened, and Ive seen posts of users having exactly the same issues that I had waaay before MAGLDR came out :) So I got to the conclusion that there is a big amount of defective devices out there, and I just send mine to HTC, cause luckily it was still in warranty.

So the problem is not with a bug in the system, as I previously was thinking, the problem is that HD2 has a sucky screen :D
[HD2 Android Q&A, Help & Troubleshooting and Genera] theboxmodder:
Indeed. My phone ended up having no issues at all. After repeated use and a few restarts the problem has gone away. This is the last NAND install I'm going to do. I love rafpigna's RAFDROID HD 3.0. So much so that I'm going to wait for 2.3 to get sense and wait for him to cook one up. And if he doesn't ill do it myself. But so far my touch issues seem to have been temporary. Almost like it was because things weren't loaded properly. Hope the best of luck for the rest of you.
[HD2 Android Q&A, Help & Troubleshooting and Genera] lude219:
to say that it's a hardware issue is a bit ill-conceived. just how many influx of people who are still running wm6.5 are having a dead touch screen at this time compare to those running on android? it may not be MAGLDR related but you can't deny that there's something within the linux kernel that is killing all these touch screens. anecdotal evidence of your phone still functioning doesn't rule out the fact that ever since android development began, a lot of people have had their screens replaced.
[HD2 Android Q&A, Help & Troubleshooting and Genera] jose makalolot:
Because a lot of hd2 users who used and want to use android on their phone doesn't know how to read and search.
[HD2 Android Q&A, Help & Troubleshooting and Genera] akapaul26:
DID YOU READ THIS??????

@ lude219

I think your theory of "ever since android development began, a lot of people have had their screens replaced". Probabally true but only because people go crazy and download every possible rom and screen is on during all this constantly and at high power....Hmm seems likely that would happen to me. I think these screens are going out because people are just plain using the **** out of the phone and their screen. Has nothing to do with these builds. Put it this way someone who has a LCD or plasma tv same model same software and uses it daily for normal use compared to someone who uses the tv all day watching hi-def movies and such never gives it a break....which one do you think will go out faster? Fact is screens may go out, I once got a tv, screen went out after two weeks.....got the same replacement model been going strong for 5 years now. To say that a software is breaking these phones is stupid especially sense this theory has been shot down by the man himself.
[HD2 Android Q&A, Help & Troubleshooting and Genera] rkalas:
I have always had issues with touch screen - too sensitive in WM and very inaccurate and sometimes crazy in Android. Now I decided to let it repair. I did task29 and flashed latest WM6.5. Now the keyboard in WM is working pretty good, only once the keyboard behaved crazy. So I'm affraid, that HTC service would tell me that everything works as it should, as I will not be able to show the opposite.
[HTC Aria General] arnienz:
Hey, I upgraded to FR008 last night and its great, except I think I've got the 2.2 sms bug which sends messages to random contacts.

I had 3 people text me last nigth saying "wtf" or something similar. I'm not sure if it was sending previously failed messages, or something else.

Anyway, is there a 2.2.3 update available for the Aria? I still want HTC Sense, is this possible?
[HTC Aria General] tpbklake:
With HTC Sense being a proprietary UI build on top of Android 2.2, it is up to HTC to incorporate Android point releases into their code and then release it. Since the current HTC Sense ROM for the Gratia/Aria is Android 2.2 and not even 2.2.1, it seems like HTC does not care whether the Gratia/Aria stay current with Android point releases.
[HTC Aria General] arnienz:
So the answer is no? Cool.

Someone make a Htc Sense mod for the cm7 ROM ;)
[HTC Aria General] zervic:
Not gonna happen ;) hence the word "propietary".
[HTC Aria General] Darius_bd:
Uhm... no.

But you can try to skin it to look like sense if that's how you want it...
[General Questions and Answers] njay222:
I currently have a htc desire on three. I tried rooting it today using the revoke method, revoke says done. However htc desire is still not rooted. Going to the hboot section and recovery mode gives me the following messages.

ClockworkMod Recovery v2.5.0.7

E: Can't Find MISC:

E: Cant mount cache : recovery/command

E: Can't FInd MISC:

E: Can't mount Cache:recovery/log

E: Can't find MISC:

I have used revoke program about 40-50 times. Sometimes it wont root saying firmware too new. Sometimes it went through and said done. Ran the programme on both windows and linux as i heard windows could have driver problems even though i installed the drivers properly. DId have force 2 sd before however undid this early today before rooting. I have also reset phone multiple times to see if that helped.
[General Questions and Answers] DroidFreek:
Root via sd card
[General Questions and Answers] gklute:
hi i have exactly the same problem :confused:

i rooted my girlfriends wildfire no problem

my desire wont work... can any 1 help???
[General Questions and Answers] Curious!:
there was an app to root it check desire forum.
[Droid X General] babygetoboy:
Hi, I am running the z4root on my Droid X and it is frozen on the screen and saying Running exploit in order to obtain root access....

What should I do, please help me
[Droid X General] dwray:
Try rebooting your phone and then run z4 again. Also make sure you have usb debugging turned on.
[Droid X General] Jmoney47:
Pull your battery, reboot, check to make sure USB debugging is enabled, and try again
[Droid X General] casron:
I have a t-mobile G2 2.3.4

I have done this, do I need to download SuperUser? I don't know anything about this except ...........I want change like all of you guys!

I'm female and not knowledgeable about this subject.

I do thank you all for your Expertise!:o
[Droid X General] infazzdar:
What is your phone's system version?

Z4root won't run on a Droid X with a later system version than 2.3.340.

If you're on 4.5.602 or 4.5.605 you must use Pete's Motorola Root Tools.
[Droid X General] casron:
It's a HTC T-Mobile G2 2.3.4
[Droid X General] NType3:
Z4Root no longer works. The same applies to Visionary.

You'll need to download "Motorola One-Click Root" and run that. If you can't find it, let me know.
[Galaxy S I9000 Q&A, Help & Troubleshooting] androidman9000:
My kernel is 2.6.32.9

curio@carton#1877

link:http://xdaforums.com/showthread.php?t=806195

Can I overclock my phone with this kernel up to 1.2Gz?
[Galaxy S I9000 Q&A, Help & Troubleshooting] azzledazzle:
you need to download voltage control and setCPU from the market.
[Galaxy S I9000 Q&A, Help & Troubleshooting] androidman9000:
no need to change kernel?
[Nook Color General] MДЯCЦSДИT:
Burn a SD and don't boot yet.

Erase uImage from the boot partition

Put the uimage from inside the eclair overclcock zip into boot

Success
[G2 and Desire Z Themes and Apps] andjohn:
Permissions setting lower down might fix this: "DOESN'T WORK ON ATRIX OR JS7 ROM. If your phone bootloops, just go into Clockwork and replace the font file again with the regular clockopia or reflash on top with the same Rom."

Hey All,

I found an ingenious solution to a problem I have been having. I don't like replacement lockscreens as they are usually slow or odd SO I found a solution. I have a live wallpaper clock and I don't like having the regular clock text on it so...replace it with a 'blank.ttf'

You can't just make a blank file, it must be formatted, so simple google search shows up this!

Change the extension to ttf, also you might want to do this:

Enjoy
[G2 and Desire Z Themes and Apps] noodles2224:
If using this, its just blank right? Battery, signal, etc doesn't scoot down to the right??
[G2 and Desire Z Themes and Apps] andjohn:
Ya, they are in the same space as if the clock is still there. The metrics of the font is similar to Clockopia
[G2 and Desire Z Themes and Apps] psynapse:
did not work on js7 rom. phone currently stuck in bizarre bootloader loop where the android OS restarts itself upon trying to display lockscreen text.
[G2 and Desire Z Themes and Apps] andjohn:
Hmmm, odd. Well, there we have it. Doesn't work on all roms...
[G2 and Desire Z Themes and Apps] gerbick:
Yep. Avoid doing this on a Motorola Atrix too. Reflashing right now due to getting stuck in the bootloader repeat.
[G2 and Desire Z Themes and Apps] andjohn:
Odd, sorry dude. I'll make a note of this on the OP.
[G2 and Desire Z Themes and Apps] Thegrimreaper3:
This is a great start and works on my thunderbolt, but how do I get rid of the rest of the info on the lock screen? Like the day of the week, the PM, and the charging status. Any ideas?
[G2 and Desire Z Themes and Apps] andjohn:
No ideas, those elements use the regular DroidSans.ttf font. You could look at the lockscreen zip but I'm not sure where to start.
[G2 and Desire Z Themes and Apps] amazinglarry311:
You should chmod 644 /system/fonts/Clockopia.ttf after you push it or it can bootloop almost every device without setting proper access permissions for the font.
[G2 and Desire Z Themes and Apps] adimcx:
Thanks! This is exactly what I was looking for! :good:

I'm using CyanogenMod 7 and this is the only way I have found, to remove just the clock from the lockscreen. ;)
[G2 and Desire Z Themes and Apps] Thegrimreaper3:
Ahh, the old days of the Thunderbolt. Looking back it depresses me, but I'm back on HTC now with the M8. Feels way better.
[Click General] deadevil13:
Hi

Okay i am pretty much a complete noob at all of this.. so give us a fair chance.

Ive just attempted to install nFinityGB v0.6 on my HTC Tattoo - and failed, quite miserably.

I've followed the following tutorials:

Goldcard - http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/

Rooting - http://theunlockr.com/2010/03/16/how-to-root-the-htc-tattoo/

Loading a rom - http://theunlockr.com/2010/03/30/how-to-load-a-custom-rom-on-the-htc-tattoo/

I downloaded, and moved the zip file across onto the SD card.

Turned off, Booted Recovery - made a back-up, wiped, reset and then installed flash.

Reboot > stuck on Tattoo screen.

Have tried re-install - no joy.

On the ROM's page it talks about a ClockworkMod - which i have no clue on, because the tutorial given; makes no sense to me; a noob. :confused:

(http://xdaforums.com/showthread.php?t=892401)

Someone please help, im backing using my old Sony Ericsson C305... :(