Related
Yesterday my touchscreen no longer responded to input. Hard buttons worked. Took it to T-Mobile and will have a replacement within 7 days. Anyone else have their touchscreen die on them?
Is the HD2 black? Yeah, everyone it seems has suffered from this...especially if you run Android alot.
Mine died today. Unfortunately I have bought it second hand and don't have a receipt.
Any hints for fixing it would be nice.
Mine did it too. Got the replacement and it did it on that one too the next day. I just kept flashing random roms and after 2 or 3, it unfroze. Lesson i learned? If in android, your screen freezes, DON'T reset or take out the battery. Wait til the screen turns off and it apparently is safe to reset. (I quickly do a reboot command in android)
ashasaur said:
Is the HD2 black? Yeah, everyone it seems has suffered from this...especially if you run Android alot.
Click to expand...
Click to collapse
If you mean the screen, no. It boots up and everything fine, hard buttons work fine.
djdanska said:
Mine did it too. Got the replacement and it did it on that one too the next day. I just kept flashing random roms and after 2 or 3, it unfroze. Lesson i learned? If in android, your screen freezes, DON'T reset or take out the battery. Wait til the screen turns off and it apparently is safe to reset. (I quickly do a reboot command in android)
Click to expand...
Click to collapse
Wow, interesting, if true, that Android could affect our touchscreen like this. I'd test out flashing new ROMs but I already reverted back to stock ROM and SPL when I took it to T-Mobile. Think I'll just use the loaner in the mean time and await my shiny new HD2 =D
happened to me.
and these threads:
http://forum.xda-developers.com/showthread.php?t=757117
http://forum.xda-developers.com/showthread.php?t=758846
http://forum.xda-developers.com/showthread.php?t=775333
http://forum.xda-developers.com/showthread.php?t=814584
http://forum.xda-developers.com/showthread.php?t=822777
happened to me again today. I had to flash 7 different roms but eventually it did unfreeze. I picked a new kernel from a thread in android, the one where it prevents screen freezes and it so far has worked. For some reason, for me, it does it when it gets near moisture. Doesn't have to be on the phone, but if its raining out, misty out, foggy out and even humid out, and it constantly freezes up. Nice dry sunny day and i know i am good all day. If its acting up, gps will kill it for sure.
Special Delivery =)
Well I just received my replacement today! =D Talk about a quick delivery, it got here before they even sent me the tracking number lol. Can't say its a "New" device. Telling from the hex screws it looks like it has been torn down. For a refurbished phone it looks new =)
Time to put Android back on =P
jsmccabe78 said:
happened to me.
and these threads:
http://forum.xda-developers.com/showthread.php?t=757117
http://forum.xda-developers.com/showthread.php?t=758846
http://forum.xda-developers.com/showthread.php?t=775333
http://forum.xda-developers.com/showthread.php?t=814584
http://forum.xda-developers.com/showthread.php?t=822777
Click to expand...
Click to collapse
WOW, didn't realize it was this big of an issue. I'm sure there are others.
djdanska said:
happened to me again today. I had to flash 7 different roms but eventually it did unfreeze. I picked a new kernel from a thread in android, the one where it prevents screen freezes and it so far has worked. For some reason, for me, it does it when it gets near moisture. Doesn't have to be on the phone, but if its raining out, misty out, foggy out and even humid out, and it constantly freezes up. Nice dry sunny day and i know i am good all day. If its acting up, gps will kill it for sure.
Click to expand...
Click to collapse
Interesting theory.
It started acting up this morning again so i changed the kernel to this one
http://forum.xda-developers.com/showthread.php?t=787588
because its supposed to have the touch screen freeze/g sensor issue patch built in. And it has not yet. (And the backlight to my keys work a LOT better vs. the bangsters one.)
Touchscreen death blows
I was so happy with my HTC HD2 leo ever since I put the Energy sense 2.5 rom on it with radio 2_10_50_08_2 until today. Have the same problem with non-responsive touchscreen but hard keys work fine. I didn't even get to put Android on it yet : (
Not sure if I should try random roms or switch back to the original rom; newbie here and need quickest and easiest solution. Input greatly appreciated.
Try going back to the stock 2.13 ROM and see if it helps. It more than likely won't, but it's always worth a try!
ashasaur said:
Try going back to the stock 2.13 ROM and see if it helps. It more than likely won't, but it's always worth a try!
Click to expand...
Click to collapse
That's exactly what I tried at first to no avail.
bigbodymissmari said:
I was so happy with my HTC HD2 leo ever since I put the Energy sense 2.5 rom on it with radio 2_10_50_08_2 until today. Have the same problem with non-responsive touchscreen but hard keys work fine. I didn't even get to put Android on it yet : (
Not sure if I should try random roms or switch back to the original rom; newbie here and need quickest and easiest solution. Input greatly appreciated.
Click to expand...
Click to collapse
Someone stated that multiple flashes fixed his, so maybe going on a flashing spree may do it. Best of luck and if you still have manufactures warranty I'd say use that.
Sent from my [HD]|[2] using XDA App
It happened to me and I just got my new one about 15 minutes ago. Sad that Android does this, but it seems the MCCM builds caused mine to go out, since I replicated it three times. Oh well. I'll go through 10 if I have to, as I love my HD2
ashasaur said:
Is the HD2 black? Yeah, everyone it seems has suffered from this...especially if you run Android alot.
Click to expand...
Click to collapse
You have a stock rom for one, try the one darkstone suggests for it and flash your radio to a newer one, it fixed my problem with it, and I use it daily now...
psykick5 said:
It happened to me and I just got my new one about 15 minutes ago. Sad that Android does this, but it seems the MCCM builds caused mine to go out, since I replicated it three times. Oh well. I'll go through 10 if I have to, as I love my HD2
Click to expand...
Click to collapse
I don't think it's build dependant since it happened to me using CMYLXGO's Topia series build.
Sent from my HTC HD2 using XDA App
Hey I got a HTC Hd2 and my touch screen is not working I bought it from a guy and have no warranty so do you know a solution to fixing it and I'm not sure if it had android put on it so if you could help I really would appreciate it.
Spidey EVO
spideytw2007 said:
Hey I got a HTC Hd2 and my touch screen is not working I bought it from a guy and have no warranty so do you know a solution to fixing it and I'm not sure if it had android put on it so if you could help I really would appreciate it.
Spidey EVO
Click to expand...
Click to collapse
Does the phone boot properly and hard keys still functioning? If it's the same issue I and others had then your best bet is to flash roms untill it works again.
Sent from my HTC HD2 using XDA App
This recently happened to my GF's phone, She said she was just playing a game one day, it froze so she popped the battery out and rebooted. Now every time she uses the End/Power ( red ) hard button to shutoff or wake up the device, the screen stays locked and won't respond.
I have tried soft reset, hard reset, different lock screens and what not. The only solution I found, besides sending it in, is to let the screen shut off by itself, and then wake it up with the Call/Send ( green ) hard button.
You can also try using the End/Power hard button to lock it, but then as long as you wake it with the Call/Send hard button it should be fine.
It has worked every time now. Try it and see if it helps! It's a little annoying but it saves money and insurance!
Going to repost this in all those previous listed threads to see if it helps anyone else.
Good Luck!
Happened to me the other day too. Mine was stock rom and t- mobile replaced it immediately. The new one came to my house within 16 hours and it runs silky smooth like mine never could have. I noticed it has a newer rom version than my original one.
rom 3.14.531.1
radio 2.15.50.11u
I found a work around, I have only tried this in android. Press the power button to turn the screen on, Then when it comes on it will not be responsive.
However if you turn the screen off then back on and try and unlock it it will respond and also i have noticed if the phone wakes it self up it will be responsive again.
First of all, I know that I have read about this problem in other threads but I cannot find it; I think it was associated with custom ROMs but I'm not entirely sure.
I have two problems with my sound right now:
popping
Every time the tables boots up the speakers pop. No a big deal and it might be just because they get activated and the current causes the pop. But every time a sound is made? That is annoying!
humming/screeching/buzzing
Now this is the scariest problem. The sound that comes from "within" the tablet, i.e. behind the screen and not the actual speakers. It does not always appear but seems to be linked to apps trying to use sound. It almost sounds like a hard drive spinning irregularly or a distant old dial-up modem (weird analogy, I know). I don't know what's causing it but in my opinion it's not a good sign.
Again, if anyone here remembers where it has been discussed already I will take the blow as long as I can find out if the problem(s) have been solved somewhere.
Thanks y'all!
1. Everyone's device does that. It's just the way the device wakes the speakers before playing a sound as you say. Would hope Asus could do something about that in the future.
2. It sounds like you are hearing the screen's backlight frequency. Not everyone will hear this (as we lose the ability to hear certain frequencies as we get older), but again it happens with everyones device, and is normal with any screen using a backlight.
Do you have a custom rom on it?
Oyeve said:
Do you have a custom rom on it?
Click to expand...
Click to collapse
Yes, I do. I use the PRIME! 1.4 ROM and the blades-clemsyn overclock kernel. It has been an issue since the 3.1 upgrade I think. Never had it stock though so I cannot comment on issues with the stock ROM, unfortunately.
stuntdouble said:
2. It sounds like you are hearing the screen's backlight frequency. Not everyone will hear this (as we lose the ability to hear certain frequencies as we get older), but again it happens with everyones device, and is normal with any screen using a backlight.
Click to expand...
Click to collapse
What makes this theory a bit wobbly is that the sound isn't always there. It seems to be application-specific. I would expect a backlight frequency (like a fluorescence bulb?) to be audible whenever the backlight is on and not during one application running but not the other.
Process of elimination.
Roll back to stock and see if the problem occurs. If so, sounds like you’re going to have to return it for an exchange.
smellmyfingers said:
Process of elimination.
Roll back to stock and see if the problem occurs. If so, sounds like you’re going to have to return it for an exchange.
Click to expand...
Click to collapse
The scientific way, I like your idea
Do you also know if there has been a use for the SBK to enable root for the stock ROM?
funnycreature said:
What makes this theory a bit wobbly is that the sound isn't always there. It seems to be application-specific. I would expect a backlight frequency (like a fluorescence bulb?) to be audible whenever the backlight is on and not during one application running but not the other.
Click to expand...
Click to collapse
Each app will tell your device to process the images onscreen in different ways, whether thats the refresh rate, resolution or just pixel density, so you would still get different frequencies from different apps all the time. Anyway I'm not saying that's 100% the reason, it's just a possibilty based on what you were describing.
stuntdouble said:
Each app will tell your device to process the images onscreen in different ways, whether thats the refresh rate, resolution or just pixel density, so you would still get different frequencies from different apps all the time. Anyway I'm not saying that's 100% the reason, it's just a possibilty based on what you were describing.
Click to expand...
Click to collapse
Very good points! Never thought of it this way... Do you also think it's worth going back to stock and try to figure it all out or just take it "as is"?
If it is what I thought it was, it won't make a difference which rom you use, and it's a normal feature of the tablet. You must live in a very quiet place to hear it all the time or have very sensitive ears. If it's not that, then trying another rom as mentioned above may help you narrow down the list of causes. If it's annoying you too much then possibly it IS a fault with the tablet and in which case you'd need to get a replacement. If it was me I'd probably roll back to the stock rom just to see.
stuntdouble said:
If it is what I thought it was, it won't make a difference which rom you use, and it's a normal feature of the tablet. You must live in a very quiet place to hear it all the time or have very sensitive ears. If it's not that, then trying another rom as mentioned above may help you narrow down the list of causes. If it's annoying you too much then possibly it IS a fault with the tablet and in which case you'd need to get a replacement. If it was me I'd probably roll back to the stock rom just to see.
Click to expand...
Click to collapse
After 20 years of listening to metal I highly doubt that my ears are that sensitive but you never know I might try the stock ROM as soon as it has been rooted but for now I don't think it's worth it. I was more worried about something inside the device being tortured
funnycreature said:
Yes, I do. I use the PRIME! 1.4 ROM and the blades-clemsyn overclock kernel. It has been an issue since the 3.1 upgrade I think. Never had it stock though so I cannot comment on issues with the stock ROM, unfortunately.
Click to expand...
Click to collapse
I hear the buzzing sound too and I am also unning Prime 1.4 ROM and Clemsyn-Blades KERNEL. I hear it on the Left side of the tablet and sounds like its coming from the speaker but more towards the screen edge. Never heard it on Stock though.
dja2k
I'll have to wait for another reboot to test this, but I hear what I call high pitched 'tweeting' from the speaker I just have to touch the volume up/down button on the tablet and it seems to instantly stop.
I'll test here in a bit. Using Primordial 3.1 and the OC Kernel at 1.4 right now.
Update: 'twas my imagination on the touching of the volume button. It squeals a bit thru all the ASCII art and status boot screens, but settles down when the lock screen appears. Not a nuisance, but audible.
Sent from my Transformer TF101 using XDA Premium App
I updated the Clemsyn-Blades v6 KERNEL to v7ELITE and I don't hear the buzzing sound anymore. Maybe it was that version of the custom KERNEL. I will check it out, maybe it is just random.
dja2k
funnycreature said:
Yes, I do. I use the PRIME! 1.4 ROM and the blades-clemsyn overclock kernel. It has been an issue since the 3.1 upgrade I think. Never had it stock though so I cannot comment on issues with the stock ROM, unfortunately.
What makes this theory a bit wobbly is that the sound isn't always there. It seems to be application-specific. I would expect a backlight frequency (like a fluorescence bulb?) to be audible whenever the backlight is on and not during one application running but not the other.
Click to expand...
Click to collapse
It's the custom kernel you're using, mine was doing the same thing with some weird high pictched sounds too. I reflashed the stock ASUS kernel and it hasent done it since. Just to make sure, I reflashed the custom kernel you're using and the speakers make the humming noise again.
cdpriest said:
It's the custom kernel you're using, mine was doing the same thing with some weird high pictched sounds too. I reflashed the stock ASUS kernel and it hasent done it since. Just to make sure, I reflashed the custom kernel you're using and the speakers make the humming noise again.
Click to expand...
Click to collapse
I haven't noticed the humming since v7 of Clemsyn/Blades' kernel. But the popping is as bad as ever. I wish there was a fix for that too!
funnycreature said:
First of all, I know that I have read about this problem in other threads but I cannot find it; I think it was associated with custom ROMs but I'm not entirely sure.
I have two problems with my sound right now:
popping
Every time the tables boots up the speakers pop. No a big deal and it might be just because they get activated and the current causes the pop. But every time a sound is made? That is annoying!
humming/screeching/buzzing
Now this is the scariest problem. The sound that comes from "within" the tablet, i.e. behind the screen and not the actual speakers. It does not always appear but seems to be linked to apps trying to use sound. It almost sounds like a hard drive spinning irregularly or a distant old dial-up modem (weird analogy, I know). I don't know what's causing it but in my opinion it's not a good sign.
Again, if anyone here remembers where it has been discussed already I will take the blow as long as I can find out if the problem(s) have been solved somewhere.
Thanks y'all!
Click to expand...
Click to collapse
Sound like you got a Bee in there eathing rice crispies
I have been using Android since cupcake and it's going to end with my Nexus One. Reasons:
These are problems I've had with various roms, most stock roms, some MIUI:
- The Camera, no matter which ROMS I get when I try and take a picture it reboots the phone after freezing. I cannot use my 5MP camera at all because of this.
- After leaving the phone charging for awhile then going back to it when I push one spot on the screen it thinks I've pushed a completely different spot. I require a full reboot to fix this.
- My keyboard, stock keyboard, sometimes turns all white. You then cannot see what you're typing and there's just this big white bar.
- To fix the above I got Better Keyboard. It force closes often, and sometimes when I try to type with it what I'm typing doesn't get inserted into the selected input box.
- I got five hours of STANDBY (not using phone at all) battery life on Gingerbread. I had to downgrade back to froyo to get normal battery life back.
- After ten seconds or so if you don't use your screen it's supposed to DIM. Regardless of whether or not I'm using my phone it still dims after ten seconds.
So as far as Android goes come October when my three year Bell contract expires I'll be selecting an iPhone. I am done with Android problems of all kinds. That's not to say there's not a lot of things I like about Android but I can't just keep on going with it whilst experiencing these annoying problems, when I've never experienced any problems of any sort on my jailbroken iPad.
Did you ever try using your warranty? Really sounds like you had a dodgy handset.
Sounds like your phone is a lemon. I experience none of that....don't think anything you mentioned is a problem of android itself, you just got unlucky with your phone
Sent from my Nexus One using XDA App
Sounds like some bad flashing you been doing to your phone
Sent from my Nexus One using XDA App
lemons
.
You must be holding it wrong, those are some crazy problems you are experiencing ... I've never had any of those.
Macmee said:
- The Camera, no matter which ROMS I get when I try and take a picture it reboots the phone after freezing. I cannot use my 5MP camera at all because of this.
Click to expand...
Click to collapse
Not related to Android in the slightest. You're having a HARDWARE problem.
- After leaving the phone charging for awhile then going back to it when I push one spot on the screen it thinks I've pushed a completely different spot. I require a full reboot to fix this.
Click to expand...
Click to collapse
Not related to Android in the slightest. You're having a HARDWARE problem.
My keyboard, stock keyboard, sometimes turns all white. You then cannot see what you're typing and there's just this big white bar.
Click to expand...
Click to collapse
In all of my time with Android, on multiple devices, I have NEVER once seen this issue. Something is wrong with the custom rom you're running... which btw, YOU flashed on your phone.
To fix the above I got Better Keyboard. It force closes often, and sometimes when I try to type with it what I'm typing doesn't get inserted into the selected input box.
Click to expand...
Click to collapse
So some janky app YOU installed is causing a problem? Uninstall it and find something better.
I got five hours of STANDBY (not using phone at all) battery life on Gingerbread. I had to downgrade back to froyo to get normal battery life back.
Click to expand...
Click to collapse
Did you try and diagnose this at all? Were you having a wake lock issue? Was some app freezing?
I go all day on Gingerbread, especially if I don't even use it...
After ten seconds or so if you don't use your screen it's supposed to DIM. Regardless of whether or not I'm using my phone it still dims after ten seconds.
Click to expand...
Click to collapse
Again, this sounds like either something wrong with your rom or a hardware issue. I have never seen this issue.
Yeah, you're an idiot. Sorry, but you're blaming problems that either you have created or hardware problems on Android, the operating system.
But go ahead and leave Android. It sounds like you're not really technology capable of much more than an iPhone (and really, this is probably going to be pushing your technological limits it seems), so that is probably what you should stick to.
I won't be as harsh as the others
The only problem you mentioned that is N1 related is the screen, rest are probably rom related. If your flahsing all those roms you already know they are not guaranteed to work on all phones.
If you want to try another phone, try the new Sensation or equivalent. Android is still much better than Apple. IMHO. That said, my son and his wife have been Apple users for 20 years or as long as I can remember. They have used nothing else. So, I think the iphone is a good phone, just not for everyone. As android is not for everyone. I once thought Blackberry was unbeatable, I was wrong bigtime. When I first started using them, they may have been. But, not any more.
You are probably like me and get an itch to try something different. I am currently running RCADSmix Sense rom with a number of issues. But, I like it so much, I will put up with the issues. Probably means my next phone will be the Sensation or it's future quadcore brother.
Enjoy whatever you get, I still remember when a six transistor am radio was an upgrade. These are great tech times--
Ken
If you really can't realize that the problems you are experiencing are hardware related...it's probably better you get an iphone. Bye and don't let the door hit you on the way out
So as far as Android goes come October when my three year Bell contract expires I'll be selecting an iPhone. I am done with Android problems of all kinds. That's not to say there's not a lot of things I like about Android but I can't just keep on going with it whilst experiencing these annoying problems, when I've never experienced any problems of any sort on my jailbroken iPad.
Click to expand...
Click to collapse
Im just guessing here but your in Canada with bell? bell doesn't offer the nexus one. how are you on a contract? Ill also agree with everyone else your problems are not android related. Sounds like a hardware issue. Good luck with the iPhone my brother loves his. I like the design but that's it.
Just flashed cyanogen latest version. New problems:
1. Sometimes when turning on the phone the lock screen doesn't show up, just my background displays and nothing else. Reboot required by pulling battery out in order to fix.
2. Display menus don't show up sometimes.
3. Already experienced this one, but the keyboard is yet again going completely white.
Anyone want to point me towards an actual working rom without any problems or does such a thing exist
wsrider said:
Im just guessing here but your in Canada with bell? bell doesn't offer the nexus one. how are you on a contract? Ill also agree with everyone else your problems are not android related. Sounds like a hardware issue. Good luck with the iPhone my brother loves his. I like the design but that's it.
Click to expand...
Click to collapse
I bought it outright two years into my contract when I had a vogue.
Babydoll25 said:
If you really can't realize that the problems you are experiencing are hardware related...it's probably better you get an iphone. Bye and don't let the door hit you on the way out
Click to expand...
Click to collapse
Because not all of these problems are with the hardware and you, or myself are incapable of diagnosing them without more extensive investigation to the handset.
Roms work fine. Your phone doesn't
Most people have no or little problems with these roms
Most if not all issues are improper flashing or incomplete wipes--like not wiping system and data and caches multiple times
Check md5s
Or, not properly partitioning sdcard
If still issues then the phone has too many bad blocks for the rom and kernal
Ken
After reading your first post again, I think it is your phone and not common issues. I have never had a bad camera unless specifically noted on the OP page of an alpha type rom.
I can tell you how I do my sdcard and prepare for a new rom if you like. If my procedure doesn't work you will never have any better luck flashing with that particular phone.
Sorry
Ken
I'm with Telus on my N1 and i've never ever seen any of the problems you mentioned. I've also flashed alot of different roms/kernels/apps/etc and nothing like you had mentioned.
I did however have an issue that resembles your camera issue. Mine was the GPS causing my phone to reboot every time i used it. I didn't really notice it much until i started using it for GPS nav and such. Tried flashing different roms, going back to stock and issue still came up. Called HTC and sent my phone back under warranty. They told me they replaced the board and i have not seen the problem ever since.
I strongly recommend giving HTC a call and see if you can send your phone in for repairs.
That's what iPhone is for. To protect incompetents like yourself from themselves.
You should be nowhere near a rooted phone.
I have the exact same camera issue. The reason is a date of my beloved Nexus and my washing mashine. So it might be a hardware problem for you as well. Sometimes with some roms the camera seems to work 1 out of 10 times.
Bluetooth, fm radio died as well but everthing else is just fine. Some roms seem to check/use camera, radio or bluetooth during a reboot. Then the rom won't start at all or it makes random problems.
This phone is a beast. 20 minutes in the washing mashine at 60°C couldn't really destroy it. Even between screen and digitizer there was water and I had to disamble the phone three times and dry the parts for one week in a rice bowl to get it to work again.
xManMythLegend said:
That's what iPhone is for. To protect incompetents like yourself from themselves.
You should be nowhere near a rooted phone.
Click to expand...
Click to collapse
+1
sent from SGS Captivate 2.3.4 with CM7 or MIUI using Escapist or TKglitch
- The Camera, no matter which ROMS I get when I try and take a picture it reboots the phone after freezing. I cannot use my 5MP camera at all because of this.
- After leaving the phone charging for awhile then going back to it when I push one spot on the screen it thinks I've pushed a completely different spot. I require a full reboot to fix this.
- My keyboard, stock keyboard, sometimes turns all white. You then cannot see what you're typing and there's just this big white bar.
Click to expand...
Click to collapse
Got this also, annoying but I'm quite sure it goes along with flashes. Pretty sure it will be normal on stock rom.
Actually mate I think you should upgrade your radio...
I used to have this issue with the camera before, get the latest radio and ur camera issue will be solved.
and the battery as well i guess
as for the keyboard and all the other problems just go to rom manager and flash cm 7.1 rc1 from there, make sure you wipe cache, and dalvik cache
it should solve ur issues
Android is a more technical platform, it is by default that the user likes going technical before getting an android
I just tried out 3 different ROMS. Cherryblur, Ninja, and Red Pill. All three of them cause my touchscreen to be unresponsive at times. When I try to interact with my phone a lot, sometimes I have to wait a couple seconds before I can actually press on what I want to press on. Does anybody have issues like that? I went back to 1.83 and everything is dandy. Is there a fix for this? Haven't seen anything like this yet on the forums.
kshiuan said:
I just tried out 3 different ROMS. Cherryblur, Ninja, and Red Pill. All three of them cause my touchscreen to be unresponsive at times. When I try to interact with my phone a lot, sometimes I have to wait a couple seconds before I can actually press on what I want to press on. Does anybody have issues like that? I went back to 1.83 and everything is dandy. Is there a fix for this? Haven't seen anything like this yet on the forums.
Click to expand...
Click to collapse
This is an issue with the SBF... which one did you use?
Im using the official GB and im having the same problem, especially on phone calls....the screen locks itself up
mpalatsi said:
This is an issue with the SBF... which one did you use?
Click to expand...
Click to collapse
I didn't use any of the SBF's. I have not used any SBF's period to flash besides a long time ago when I was playing around with Froyo.
bandityo said:
Im using the official GB and im having the same problem, especially on phone calls....the screen locks itself up
Click to expand...
Click to collapse
I don't think that's what my issue is. Anyone know what I need to do to fix it? It's quite annoying.
For background:
I was on 1.8.3 and decided to jump to a GB ROM today. Went with Cherryblur at first. Noticed the lag, so I tried Red Pill and then settled on Ninja. However, Ninja is still giving me these touchscreen lag issues. When CWM'ing new ROMS I ALWAYS wiped data/cache/Dalvik. Then I would install the ROMs on CWM and apply jug's battery fix. Was there anything else I needed to do? I figured I shouldn't be SBFing anyways.
Sent using my Ninja Atrix 4G.
As some of us know, after knowing your Desire HD for quite a long time, flashing a ROM such as CM7 has incurred problems such as camera flash shutdowns.
The explanation for this is simple! :laugh: It is NOT (by about 99.999%) a hardware fault. It is due to the phone withdrawing too much power at boot due to some voltage settings and kernels...
Solution 1
Change your kernel and adjust voltage settings...
Solution 2 (The better one)
Replace your Desire HD battery, it may seem drastic for some cheapskates (like me), but is effective. ONLY do this is Solution 1 didn't work. Also, it may give you better battery life.
Solution 3 EXTREME MEASURES
Revert to a stock ROM... NOT a flashed one, I mean a full fledged RUU (Rom Update Utility).
For RUU's check out the Development forum.
FINAL SOLUTION (MOST EXTREMELY FREAKING WEIRD MEASURES)
Lock bootloader, undo s-off and contact HTC.
In my personal experience the battery solution was the best and worked like a charm.
Have a good day.
And click thanks.
Come on... 103 views and no thanks..? Come on people!!!
can you explain more about solution 1 !
Dr. Globbyglob said:
Come on... 103 views and no thanks..? Come on people!!!
Click to expand...
Click to collapse
Not sure if serious... :/
PHOENIX-9 said:
can you explain more about solution 1 !
Click to expand...
Click to collapse
Go to the development section, go to the index and look at the kernel category. Pick one that seems good to you and use it. The dev might also write about what voltages are good for the kernel, and to change them I recommend SetCPU
I hope I helped the poor poor people with this issue.
:good::good::good::good::good::good:
For me this issue comes and goes, so I guess it's a kernel/system settings related.
right now on Sabsa Prime v11 @1.5Ghz and no issues with flash.
-SmOgER said:
For me this issue comes and goes, so I guess it's a kernel/system settings related.
right now on Sabsa Prime v11 @1.5Ghz and no issues with flash.
Click to expand...
Click to collapse
That's nice, this tutorial was just for those people who are going absolutely KAY-RAY-ZEE at their DHD's. (like me)
I had the same issue, on a stock phone. The DHD would first shut down when doing a photo with flash, then when simply doing a photo, then sometimes without any apparent reasons, even with screen off. In the last times it would works only when without the sim card, every time i booted with SIM in the phone shutted down at the moment it was gaining signal.
I bought a new battery and, by now at least, it solved everything.
D-7 said:
I had the same issue, on a stock phone. The DHD would first shut down when doing a photo with flash, then when simply doing a photo, then sometimes without any apparent reasons, even with screen off. In the last times it would works only when without the sim card, every time i booted with SIM in the phone shutted down at the moment it was gaining signal.
I bought a new battery and, by now at least, it solved everything.
Click to expand...
Click to collapse
Yay just like me! Nice that it worked, it happened to me as well. Plus do click thanks though.
YAY!