NAND MAGLDR causes Touch Screen and keyboard errors - HD2 Android Q&A, Help & Troubleshooting and Genera

I've tried a few NAND builds. They're cool. However on everyone of them, when I am using the keyboard, I notice the phone thinks I've touched a different key (usually on the other side of keyboard). For instance, I'll hit the O key, and the phone thinks I pressed V or D or such. Or I'll tap one letter, and the phone registers 2 to 5 different keys pressed.
Has anyone else seen this? Any solutions?
Reflashing HSPL fixed the issue.
Updated title to be more descriptive

Are you charging while this is happening?

Nope. I noticed that could happen back when I had just WinMo on phone. I noticed if I use the cover that came with phone, and make sure not to touch any conductive part of the phone, it works normally.

Personally, I think your screen has developed a fault and it's just co-incidence that you're trying NAND builds. I, too, thought that it was Android that was at fault, I sent my phone back to HTC and they replaced the screen.
See my thread here.

ignore this

del
10chars..

Bump. Anyone have any idea?
Confirming the problem, I took these steps.
Task 29 Phone and formatted SD card
Install MAGLDR
Install a nand ROM
Problem remained.
Task 29 and format again. MAGLDR again. Another ROM, problem remained.
Task 29 and format again. Flash stock WinMo ROM. Problem gone.
Task 29 and format again. Flash ChuckyDroid and HD2ONE sd ROM. Problem gone.
Seems to me a problem with the MAGLDR / nand builds. No one else has had this? Any solutions?

Reflashing HSPL fixed it.
Also seems the Swype beta was causing similar issues. :/

Tried MAGLDR 1.12 and problem persists. Reflashing HSPL didn't fix the issue earlier, though it helped.
Does anyone have any ideas?

This really sounds like a hardware problem to me man... Try returning for warranty.

StephanV said:
This really sounds like a hardware problem to me man... Try returning for warranty.
Click to expand...
Click to collapse
It's not hardware. Cause I can run Android SD builds and Windows and have no issues. Perfect operation of the touch screen in all the SD and Win builds. Perfect precisions too. Any build using the NAND and MAGLDR has the problem happen after a couple of minutes.
I can switch between the various types of builds and produce (or resolve) the problem consistantly. It seems odd to me the problem would only exist in MAGLDR use.

FreakyFerret said:
It's not hardware. Cause I can run Android SD builds and Windows and have no issues. Perfect operation of the touch screen in all the SD and Win builds. Perfect precisions too. Any build using the NAND and MAGLDR has the problem happen after a couple of minutes.
I can switch between the various types of builds and produce (or resolve) the problem consistantly. It seems odd to me the problem would only exist in MAGLDR use.
Click to expand...
Click to collapse
I'm sorry I had misread your post, I thought you had the same problem on WinMo but you just meant in Android with WinMo still in NAND.

Right. (Wish I could delete my previous posts and consolidate them properly.)
Also, it seems the screen is bit more ... charged when I'm using MAGLDR. Like there's a slight more "static charge" to it. I'm thinking it's some sort of driver issue or something. :/ It becomes really noticable once I install Swype (beta and nonbeta), so maybe Swype is changing a value or something that accentuates the problem.
Does anyone know how to contact the DFT team directly?

My touchscreen actually went out after flashing a NAND build. Heres the thread. If you could, chime in. Im trying to make this a known issue.
http://forum.xda-developers.com/showthread.php?t=922503

Did further research and testing. Follow up in a new thread since this one is all over the place.
http://forum.xda-developers.com/showthread.php?p=11107926

FreakyFerret said:
Did further research and testing. Follow up in a new thread since this one is all over the place.
http://forum.xda-developers.com/showthread.php?p=11107926
Click to expand...
Click to collapse
I do not know whether this will work or not. But try a NAND build with SENSE in it. Sense has a function of "Calibrate your Screen". Try and recalibrate your screen.
I know for sure the build "imilka's Vision Sense v3.0 (HD2Z)" has this feature. The link for this build is http://forum.xda-developers.com/showthread.php?t=898708
I hope that resolves your issue.

Are you certain about this?
FreakyFerret said:
I've tried a few NAND builds. They're cool. However on everyone of them, when I am using the keyboard, I notice the phone thinks I've touched a different key (usually on the other side of keyboard). For instance, I'll hit the O key, and the phone thinks I pressed V or D or such. Or I'll tap one letter, and the phone registers 2 to 5 different keys pressed.
Has anyone else seen this? Any solutions?
Reflashing HSPL fixed the issue.
Updated title to be more descriptive
Click to expand...
Click to collapse
I have this same problem in my HD2...
In winmo and nand android, same problem.
You wrote: "Reflashing HSPL fixed the issue."
Are you certain about this?

Related

screen blacking out

Hi new to hd2 android. I have tried multiple roms and and droid builds ,but the problem I am having is after I format my sd card with the sd formatter that I was recommended I transfer the android build to it let it boot up. After that I reboot it and set everything up ,and 99% of the time I will set the phone down and when I go to pick it back up I hit the power/end button to turn on the screen and I get no screen I just get buttons lighting up. Is there anything that I am not doing or doing that is causing this. Please help. I am no stranger to electronics as I modify about everyone of them that I own ,but I can't crack this one. I've been working at it for over a week keep getting the same result. If anyone can help me I would greatly appreciate it. Thanks in advance
vdubbri said:
Hi new to hd2 android. I have tried multiple roms and and droid builds ,but the problem I am having is after I format my sd card with the sd formatter that I was recommended I transfer the android build to it let it boot up. After that I reboot it and set everything up ,and 99% of the time I will set the phone down and when I go to pick it back up I hit the power/end button to turn on the screen and I get no screen I just get buttons lighting up. Is there anything that I am not doing or doing that is causing this. Please help. I am no stranger to electronics as I modify about everyone of them that I own ,but I can't crack this one. I've been working at it for over a week keep getting the same result. If anyone can help me I would greatly appreciate it. Thanks in advance
Click to expand...
Click to collapse
It would help if you added your WinMo ROM/Radio and the Android build this is happening with?
Sorry I am running the elegancia gtx right now with the froyostone sense 3.1.7 and the 2.10.50 radio ,but it has done it with numorous builds
Me too
I have the same problem and i have tried several different builds and am running chuckyRom
I have tried the chucky rom and the ozdroid rom as well with almost every single android build that is half way decent. This sucks I would love this phone to be up and running good. Now I did have the combo of chucky rom with the same radio I have now with the hyperdroid 1.6 and it ran for a few days with no problems ,but the darn battery died quick. I haven't been able to get it to work properly since.
Hit the phone button it will wake up faster
Sent from my HTC HD2 using Tapatalk
The problem is its not turning the screen on at all. No matter what button I hit.
vdubbri said:
The problem is its not turning the screen on at all. No matter what button I hit.
Click to expand...
Click to collapse
U have advanced task killer installed?
Sent from my HTC HD2 using Tapatalk
I'm having the same issue, and yep, Advanced Task Killer is installed and running.
same here
i am having all those same problems and i have tried it with and without ATK
I do not have task killer installed not any version of any of the task killers. If a android build has it in it I go in and uninstall it.
Try changing your sd card. I saw some cards (such as team branded) exhibit that behaviour.
Same problem here tried changing the SD card and same thing happens.
Might have found a fix for this for now. All I did is turn auto rotatescreen in android display settings hope it works for you guys.
I have just started using the newest Energy rom with tmobile usa radio and I was getting the black screen of death. After a bunch of messing around I set it to the compact start menu and turned off sense in windows mobile home options and now the problem went away. YMMV
In the middle of reading all the posts here yestarday I glanced at motoman234's sig and I decided to try his setup and so far twelve hours later still no black screen of death. I don't know if it was my winmo rom that was causing it for me or the radio I was using ,but so far so good. The touch screen seems a little laggy which I wish wasn't there ,but again happy to have a setup that is stable.

Just an answer to my question.

Phone freezes no matter what I try. Stumped
I have a question that seems not to be able to get answered where ever I post it. so please forgive me for posting here if this is not the correct place. I have been trying android from the beginning and I've tried everyones builds. from winmo to droid and different radios to find the right combination. The problem i keep running into is that my phone freezes up no matter what i do. I tried the letama .2 & .3. This problem even occurs in winmo even with the sd out. I may get a full day out of it with no problems then the problem returns. Right know i'm running MDJ Froyo revolution v.1.3 and winmo ozrom 5.10 wwe and radio 2.10.50.26. Also, wipe the sd clean every time i switch builds or upgrade. Haven't figured out how to do logs yet. still searching and reading to try and teach myself how to be more useful around the forums. Thanks and I appreciate all the hard work the DEVS put in. That's why i follow the rules except this time.
cwsmall said:
That's why i follow the rules except this time.
Click to expand...
Click to collapse
Obey the rules!
Naa, just kidding. But if your phone's freezing even in WinMo there's something really messed up. Did you try to make a task 29 and flash your ROM again? That might be helpful.. If not, turn your phone back to original standards (ROM, HSPL, Radio must be as given by the factory) and go to your retailor to use your guarantee if you still have.
Obey the rules!
Naa, just kidding. But if your phone's freezing even in WinMo there's something really messed up. Did you try to make a task 29 and flash your ROM again? That might be helpful.. If not, turn your phone back to original standards (ROM, HSPL, Radio must be as given by the factory) and go to your retailor to use your guarantee if you still have.
I like you sense of humor. thank you for taking the time and commenting. there has been 30+ people that have viewed this and haven't even responded. But, some can ask like where is the download link and we all now where its at. always at the beginning of the thread,but they get all kind of replies. It just makes no sense to me when someone has a legit question they can't get much help. don't really understand that. Thought we were here to help each other.I don't believe that its an issue hardware issue. i believe its more software than anything. It comes and goes. My phone was going thru a period where it would reboot all by itself with no apparent reason. Then all of a sudden it stopped it and hasn't done that for 4 to 6 weeks.
really 97 views and no insight.
you tried the stock factory rom?? It might be hardware. You will be surprised a tiny drop of water inside your phone will slowly mess up your phone through a long period of time.
Are you on tmobile? I will try to look for a stock rom for you.
BTW, what do you mean by freezing? it hiccups or you have to do a battery pull.
cwsmall said:
really 97 views and no insight.
Click to expand...
Click to collapse
btw, your title is a curious one, that is why you have many views and received little to no response. If they can't help you they won't post anything. But I will try my best to see whats going on.
if your suffering from the freezes in winmo and android then you I think that you need to forget about android for the time being and concentrate on getting a stable WM set up........
If you havent already done so then try a hard reset and see if that helps.......
try booting and running your phone with and without your sd card........
with and without your sim card........
if it still happens after the hard reset then you will need to reflash your WM rom, if you plan on using the phone mostly for android then I would opt for a basic rom like the energy reference series or one of duttys roms.....
there are many reasons why your phone might freeze and you need to spend time trying all situations to figure out what makes it freeze..........
if it still happens after the reset/reflash then we can only assume that it is a serious problem which may well require a warranty replacement.....
if your suffering from the freezes in winmo and android then you I think that you need to forget about android for the time being and concentrate on getting a stable WM set up........
I have tried all that you have suggested. The curious thing to me is that it seems to come and go. It first started with the energy rom and it's also happened with dutty's as well. if you guys know how to pull logs that devs need is possible you could give me a run down on how and then maybe i can find out if it is hardware. My phone has never been near water. i'm very careful about that. I'm using ozrom now. This is the 3rd HD2 i've had. the last one lost all touch response. I just have a feeling its software, but i just have a gut feeling on that. Thanks everyone though for your input i greatly appreciate it and keep it coming.
BTW, what do you mean by freezing? it hiccups or you have to do a battery pull.
I have to pull the battery. Then i may have to leave it out for a minute or two maybe longer then replace battery before it will load windows. it will just show the splash screen.
was this happening even when you were running the stock rom?
Have you tried to reformat your SD Card? I have two, and when I used my original card received with my HD2, TMOUSA, it would freeze. Since I reformatted and use new and old card, no problems for over a month.
was this happening even when you were running the stock rom?
YES
Have you tried to reformat your SD Card? I have two, and when I used my original card received with my HD2, TMOUSA, it would freeze. Since I reformatted and use new and old card, no problems for over a month.
yes. I have two the 16 that came with it and an 8. it happens with both. I reformat every time i switch builds.
I see that your using radio 2.10 and that caused my HD2 to freeze a lot. change your radio to 2.12 or 2.14
I use the same Android build as you but with the elegancia gtx wm rom with radio 2.14 and after upgrading the radio the freezing (SOD) stopped.
I started using the radio 2.15.50 and have had no problems whatsoever. Also unchecking auto rotate and auto britghtness helps. Sometimes redownloading and installing your Android helps if you got a bad download the first time.
Update
now runnning enery extreme from 11/5 and mdj desire hd with his newest kernel smartass and the only time it freezes in during a call. usually anywhere from 5 - 15 minutes into the call. Anyone have any insight two a possible solution?
This is what I would do:
1. Task 29
2. Flash a slim WM ROM such as the one mentioned in my signature.
3. Flash a NEW RADIO...at least 2.12 or even higher.
3a. Install NOTHING. NOTHING AT ALL. Just answer and make calls. Period.
4. Test that build for two days. If I have freezups, then my phone is bad and I would flash the stock rom and radio and return it. If it does not freezup goto 5.
5. Completely reformat my SD card to Fat32 32kb (or 64kb if you think it affects stuttering in music).
6. Since you and I are both in the US, I recommend getting an Android that has a built in TMO MMS fix such as the new MDJ build (with link to MMS fix) or the fine MooMoo build or even Bluetopia.
7. Test the basic features in Android for two days minimum and see if I get freezeups (after disabling auto-rotate and wi-fi on the Android build as well as completely shutting off all radios in WM).
8. Be glad I got this far, and slowly reinstall my apps, testing each thoroughly for freezing.
This is what I would do:
1. Task 29
2. Flash a slim WM ROM such as the one mentioned in my signature.
3. Flash a NEW RADIO...at least 2.12 or even higher.
3a. Install NOTHING. NOTHING AT ALL. Just answer and make calls. Period.
4. Test that build for two days. If I have freezups, then my phone is bad and I would flash the stock rom and radio and return it. If it does not freezup goto 5.
5. Completely reformat my SD card to Fat32 32kb (or 64kb if you think it affects stuttering in music)
Thanks for taking the time to post this i appreciate it. I have tried it all. It appears to be getting better. I have been using MDJ's kernels since he posted them with his desire hd build. I have always felt that it was software related and not hardware. It appears to me to be caused maybe by the data drops from ppp. Not sure though till i teach myself how to do that. thanks again though.
Turned out to be a hardware issue. Got my new replacement and it works flawless. Can't believe the fun I was missing. At least it was a great learning experience.
Sent from my HTC HD2 Desire using XDA App

My HD2 screen gets inversed color after a while.

IF somebody know the inverse option on photoshop when black comes as white and same for all colors it happens to my hd2 after a while when I unlock is cuz I press harder on it or is a soft problem?
I've seen a few people reporting this, luckily haven't experienced it myself. Nobody seems to have figured the cause as yet, but a reboot solves the issue (until the next time of course).
I had inverted colours recently. Was weird... I was on the phone when it dialed another number (possibly i did it with my cheek cos i'd been switching back and forth from keypad and loudspeaker settings). When i hung up my phone went strange with the 'inverted' look.
I'd love to know why because it's the only stability issue I have now.
Regards
sp33dy_gtx said:
IF somebody know the inverse option on photoshop when black comes as white and same for all colors it happens to my hd2 after a while when I unlock is cuz I press harder on it or is a soft problem?
Click to expand...
Click to collapse
This happened to me as well. I had to give it a restart. It happened after I waked the phone from screen off. It would be nice to find a fix for this.
Edit: we are not alone: http://forum.xda-developers.com/showthread.php?p=10851646
+1
Hope it is just a soft prob and not a sign of hardware fail.
TheATHEiST said:
+1
Hope it is just a soft prob and not a sign of hardware fail.
Click to expand...
Click to collapse
Haven't tried it myself, but they say taking a screenshot creates a normal looking one.
So I'm afraid it is a sign of hardware fail. The bad thing is my phone is barely 2-3 months old.
edi: could you all please post the kernel you have. From what I've read, it seems an MDJ kernel problem. I used MDJ 0.2oc
I had this a few times before Xmas on one of Darkstones SD builds, only did it 4 or 5 times though. Taking a screenshot didn't work, just got a normal screen.
Since using NAND builds I've not come across this problem once, so I'm guessing the problem is Software/Kernel related rather than Hardware, which should come as a relief.
Sent from my HTC HD2 using XDA App
Did anyone find a fix for this?
I am using prj Clean Desire v0.3.2 (NAND) [Kernel: prj v0.4] and am getting the same issue, unlock the phone and everything is inverted but taking a screenshot with drocap2 comes out perfectly normal. It is happening every few days now.
I am going to try a different ROM and see if it still occurs.
Never had inverted colors in WinMo, with first Android SD releases I've had that problem quite often. But since flashed NAND Android 45 days ago haven't seen any inverted colors yet.
Sent from my HTC HD2 using Tapatalk
Had this problem today for the first time while in a call. A reboot put it back to normal...
Any known reason?
hyperdroid 2.1.0
I get this error occasionly on hyperdroid 2.1.0 but it happened to me again today.... its also happened on miui. No one found a solution or cause?
I have had this on various occasions and there i various topics on it but with no resolution of any answer as to possible cause.

[Q] Problem with WP7 Roms or problem with the phone?

I have some odd problems with my HD2 after installing two different WP7 roms (HD2O & XBMod) and am wondering if this is an issue with WP7 running on the HD2 that is universal, or is there possibly a problem with my particular hardware.
The main issue is that if the HD2 is moved (turned, twisted, etc.), it will revert back to the home screen and flicker and sometimes the voice activation app starts asking me to speak a command. It doesn't matter what I am doing at that moment. It is happening in both roms.
Are others having the same issue?
I apologize if this is a known problem, but I could not find any info. Any suggestions?
TomInMB said:
I have some odd problems with my HD2 after installing two different WP7 roms (HD2O & XBMod) and am wondering if this is an issue with WP7 running on the HD2 that is universal, or is there possibly a problem with my particular hardware.
The main issue is that if the HD2 is moved (turned, twisted, etc.), it will revert back to the home screen and flicker and sometimes the voice activation app starts asking me to speak a command. It doesn't matter what I am doing at that moment. It is happening in both roms.
Are others having the same issue?
I apologize if this is a known problem, but I could not find any info. Any suggestions?
Click to expand...
Click to collapse
sounds like its hardware related mate, you could try reverting back to a WM6.5 ROM see wehat happens there, id SD flash a stock original ROM which will revert your whole phone, SPL included, back to an original state
then if that works ok start again, HSPL>Radio>magldr>WP7 ROM,if none of that works then its definitely hardware
to be honest the flickering sounds more like a hardware issue...

[Q] SD & System Partitioning question

Hello everyone,
I'm trying to install a new ROM on my girlfriend's HD2. I use a SGS4G, and everything is much simpler there. I have Cyanogenmod installed on her phone currently, but I did that a while ago and I completely forgot how I did everything for it.
I'm trying to do the following:
- Repartition a new 16GB memory card so it works with the phone
- Install a stable/smooth ROM for her to use (this one looks good -- is it?)
The problem with the SD card partitioning is that I'm not exactly sure how to boot into CWM (assuming that's where you partition the SD card at). I can get into the aMAGLDR v1.13 screen, but I have no idea how to progress into the CWM screen.
The second problem is that I'm not sure how to format the system to 200mb and the cache to 5mb.
If someone could at least point me in the right direction. I wouldn't mind trial-and-error with my phone, but I'd really like to avoid bricking hers. Thanks!
get the 'nand tookit'
start phone into magldr, and choose 'usb flasher'
connect usb, run the toolkit, magldr repartition, select 200, and hit repartition. This will partition teh nand AND install Cwm
then, restart, in magldr choose 'ad recovery', this starts cwm, , in cwm - advanced - partition sd car (or words to that effect, i'm not restarting my phone to check) - it WILL wipe your card, so back up anything you wanna save.
So much for the SGS4G being easier lol. Thanks for the information!
adobrakic said:
So much for the SGS4G being easier lol. Thanks for the information!
Click to expand...
Click to collapse
Lol, no native Android phone is as easy to flash as the HD2 is HSPL, MAGLDR, CWM, Partition SD, ROM with no chance whatsoever of bricking it providing you have an EU HD2
Yeah, now that I see how the HD2 is done, I wish the SGS4G did the same.
I came back here for another question, however. My girlfriend said that her phone randomly becomes unresponsive. When she hits a button, the backlight for the buttons comes on, but the screen doesn't turn on. She's forced to pull the battery to reboot and have it working again. It happened once yesterday, and just now as well.
The rom I flashed to her phone is this one. I tried searching that thread, but was unable to find anything. Is that a hardware issue, or software? If it's a software thing, what's a different rom I can flash that won't have the same issue?
Thanks guys.
I offer you my understanding of the issue and what I've read about it. It's not definitive, but hopefully it helps.
The issue is often referred to as the black SOD (screen of death), so you can search this to try to find more. It appears to affect some HD2 roms, as well as various other android devices. As for the cause (hardware or software) I've seen people claim it was certain apps, roms, kernels, even the SD card (some said changing to a 2 or 4 GB card stopped the problem).
I currently have an issue with this, but mine started after I had a cracked screen replaced. When my screen goes black during a call it will occasionally exhibit the same symptoms you described, and I believe my issue is due to the screen install and the proximity sensor. To bring the screen back I hold the screen towards a bright light (or flick a lighter near the proximity sensor) and it's worked every time for me. Not a fix, but if it works for you it beats pulling the battery.
Lastly, my personal advice would be to consider a Gingerbread rom for her phone instead of ICS if there are any other problems. The ICS roms are still undergoing heavy development , where GB roms are usually highly tested and polished.
adobrakic said:
Yeah, now that I see how the HD2 is done, I wish the SGS4G did the same.
I came back here for another question, however. My girlfriend said that her phone randomly becomes unresponsive. When she hits a button, the backlight for the buttons comes on, but the screen doesn't turn on. She's forced to pull the battery to reboot and have it working again. It happened once yesterday, and just now as well.
The rom I flashed to her phone is this one. I tried searching that thread, but was unable to find anything. Is that a hardware issue, or software? If it's a software thing, what's a different rom I can flash that won't have the same issue?
Thanks guys.
Click to expand...
Click to collapse
Hmm, as stated above it could be the SOD, but that's extremely unlikely. This problem never existed on NAND builds and was solved a long time ago on SD builds. I would suggest trying a Gingerbread build (probably CM7 or MIUI, Sense is RAM consuming) and using that instead. No matter what the dev says ICS is NOT stable or fast on the HD2, it's all just advertising. You will not beat the speed of MIUI and CM7 and these are the most stable as well. Assuming your girlfriend isn't a power user MIUI is better as it has a better UI with more eye candy, although you probably will want to replace the stock launcher with GO Launcher because it's simply better than the stock one.
Would you mind linking me to a stable gingerbread CM rom? The one I flashed for her before the ICS one she has now also had the problem of the screen turning off and staying off. I don't mean to seem lazy, but I don't think she'd let me have her phone for long enough to test out all the roms. Thanks again, guys. I appreciate it.
Typhoon, look for it in the nand section.
ALL the ICS roms are still works in progress, no matter how much the author types 'for daily use', they aren't daily useable for everyone.
Gotcha. Thank you!
This ROM is smooth as heaven, have a try!
Hi m8! try this one: http://forum.xda-developers.com/showthread.php?t=769026
it has everything and bat performance is great!!
Cheers!!

Categories

Resources