Related
I just picked up another 8525 after returning the first one to checkout the Blackjack. I wanted to make sure I at least tried it before my 30 day return policy kicked in. I noticed on my second 8525 the keyboard does not lock into PDA mode as secure as my first one. It seems that the top part of the phone locks better then the bottom. So when I hold it has a phone I tend to slide the keyboard open a little. Has anyone had these issues? It just seems to easy on the second one to unlock/open the keyboard.
brmcguire said:
I just picked up another 8525 after returning the first one to checkout the Blackjack. I wanted to make sure I at least tried it before my 30 day return policy kicked in. I noticed on my second 8525 the keyboard does not lock into PDA mode as secure as my first one. It seems that the top part of the phone locks better then the bottom. So when I hold it has a phone I tend to slide the keyboard open a little. Has anyone had these issues? It just seems to easy on the second one to unlock/open the keyboard.
Click to expand...
Click to collapse
I'm afraid this is a fairly common problem. The metal runners/sliders have small indents at each end (cannot see these unless device is dismantled) that create the click into place when the sliding blocks attached to the base part slide over them.
These indents are often too shallow to create a nice firm click and in extreme cases the actual runner has sprung apart where small micro welds have broken.
There are fixes for this but only for those that don't care about their warranty and want to dis-assemble the device. I have done this fix and it now requires a very firm two thumbed push to open. However I do not recommend you do this when there is the possibility of exchange/return or repair.
Mike
If you decide to do it on your own I can vouch for Mike's method. He emailed me the process and I posted it on the WIKI.
barrydavisjr said:
If you decide to do it on your own I can vouch for Mike's method. He emailed me the process and I posted it on the WIKI.
Click to expand...
Click to collapse
Sounds like its possbile then. Where in the Wiki can I find the how-to? I looked and could not find it. Thanks again for the information.
It is under the hardware overview at the bottom. andMike i added some props to you for the method!
Mike, you must of really nailed this process. I guess I have to try it now.
barrydavisjr said:
It is under the hardware overview at the bottom. andMike i added some props to you for the method!
Click to expand...
Click to collapse
Cheers barrydavisjr.
Did it all work out well for you, I hope so.
Thanks
Mike
mikechannon said:
Cheers barrydavisjr.
Did it all work out well for you, I hope so.
Thanks
Mike
Click to expand...
Click to collapse
Yes Worked perfectly!!!
I have not done it yet, but plan to soon. To clarify what your fix does is that it tightens the sliding keyboard rails? or provide a better click when its closed?
Just read your site. I think that answered my question. Thanks, I will try and post my success (...or failure).
Great fix. One of the little but annoying things about the device fixed.
sliding keyboard then freezes
hello, I got my device ! I'm very happy but when I slide the keyboard, and here the left 'click' then it freezes.
It is very strange, is there anything I can do ?
Thanks in advance for any suggestion
dam said:
hello, I got my device ! I'm very happy but when I slide the keyboard, and here the left 'click' then it freezes.
It is very strange, is there anything I can do ?
Thanks in advance for any suggestion
Click to expand...
Click to collapse
I don't think the "clicking" mechanism is what's making your device freeze. I believe its the display going from portrait to landscape mode what's probably making it freeze up. Have you hard reset to make sure there is no 3rd party today plugins that are having issues with switching to landscape mode?
sliding keyboard, frozen device
dear brmcguire, thank you for your answer. I think I have to be more precise.
When I slide the keyboard and stop before the "click", it is ok, it moves to the landscape mode without problem. Then, when I push untill it locks, on the right lock it is ok but when pushed untill the left lock, then it freeezes. To be precise, "freeze" means that the menu bar opens, and the tactil screen does not answer anymore to the pen, (I can still use the buttons).
That is why I believe it is a hardware malfunction, but I'm still a newby
Does anybody had a similar problem ?
Any help appreciated
dam said:
dear brmcguire, thank you for your answer. I think I have to be more precise.
When I slide the keyboard and stop before the "click", it is ok, it moves to the landscape mode without problem. Then, when I push untill it locks, on the right lock it is ok but when pushed untill the left lock, then it freeezes. To be precise, "freeze" means that the menu bar opens, and the tactil screen does not answer anymore to the pen, (I can still use the buttons).
That is why I believe it is a hardware malfunction, but I'm still a newby
Does anybody had a similar problem ?
Any help appreciated
Click to expand...
Click to collapse
Ok, I see. It does sound like a hardware issue. I would try exchanging it for a new one.
dam said:
dear brmcguire, thank you for your answer. I think I have to be more precise.
When I slide the keyboard and stop before the "click", it is ok, it moves to the landscape mode without problem. Then, ...,,,,,,,,,,,,
Click to expand...
Click to collapse
I think we're all agreed it has to be hardware. There is no software that operates when the "left" edge clicks into place. There are two circuits that operate softwarewise when the keyboard opens
1. There is a small magnet operated switch that changes portrait to landscape and that's working fine,
2. The light sensor above the "p" key top right which operates the keyboard backlight.
I don't think either of these is responsible.
At a guess either the Multi connector Mylar Cable for the screen/digitizer connection is getting trapped/pulled/stretched and partially breaking its connection or the click into place is creating an internal squeeze against possibly the "windows" button hardkey next to the Green Phone Key.
I think like brmcguire that I'd get it back to shop while still in warranty perhaps after doing all the usual things like a hard reset - just in case we're all wrong and it is software.
Or you just never quite open it far enough to click into place. I do this a lot, partly because I've got a really firm click into place on both right and left sides that if I'm just quickly using keyboard I find I can get every key without the final clicks.
Mike
thanks
I tried hardware reset but no change. Anyway, thank you so much for your anwers. Not that it works better, but to feel support is quiet healing.
cheers !
mikechannon said:
I think you're right, maybe we need a Hermes counselling and psychological support group. All charges forwarded to HTC of course!
Mike
Click to expand...
Click to collapse
ok, I gave back my device, I will see what happen. Thanks !
RE. loose keyboard
CAN someone give me the direct link to the wiki page bc i couldnt find it i dont know why, if you know how to do it you can also send me the directions but PLZ someone send me a link thanks again
Did this fix after fighting with a very loose slider from the beginning. This and Mob6 software and I love my TyTn again.
Thanks for the instructions and thanks for the wiki.
derf
My HTC Hermes fell on the floor. Fortunately, it remained largely undamaged except for two little things: The on-button and the camera-button do not respond anymore when I press them. However, the buttons do not seem to be completely destroyed: They just seem somehow disadjusted. I notice that from the sound and the movement when I try to press them. I might be able to get them back to work if I could just open the device or at least use clamps to pull the button and readjust it.
Has anybody ever had similar problems, or could give me any hint as to how to fix it without breaking the device.
Of course there is no warranty, otherwise I wouldnt be so foolish as to try to open it up or use clamps.
Thanx in advance for any hints.
Cheers
Michael
are u 100% there is no warranty? even if you bought it from ebay try contacting htc directly.. dont tell them u dropped the phone obviously.
michaelbarrero said:
My HTC Hermes fell on the floor. Fortunately, it remained largely undamaged except for two little things: The on-button and the camera-button do not respond anymore when I press them. However, the buttons do not seem to be completely destroyed: They just seem somehow disadjusted. I notice that from the sound and the movement when I try to press them. I might be able to get them back to work if I could just open the device or at least use clamps to pull the button and readjust it.
Has anybody ever had similar problems, or could give me any hint as to how to fix it without breaking the device.
Of course there is no warranty, otherwise I wouldnt be so foolish as to try to open it up or use clamps.
Thanx in advance for any hints.
Cheers
Michael
Click to expand...
Click to collapse
The Hermes is actually quite durable. Chances are the button switches just need tweaked back into position.
Have a look here under Hermes Practical Fixes.
http://michael-channon.spaces.live.com
One really obvious/not so obvious thing to check is that the battery is still in position. One report I saw was where a guy dropped his Hermes, thought it was totally dead but it was just that the battery was just out of position.
Mike
Hi there!
I bought a damaged G1 from ebay to hack on.
There is some strange behaviour, that seems to be related to the trackball.
Everytime i scroll some pages for a while, the trackball is going really mad.
It toggles between applications, e.g. starts phone app or contacts and enters weird numbers.
If i leave it completely untouched the system behaves normal.
Just to give it a try, i disassembled the device and removed the trackball mechanic. Result: Everything behaves normal.
Due to these problems, i started a little research on the trackball parts.
So here's what i found (see attachment).
I will do some further investgation and check out if i'm able to fix this issue.
My suspicion is, that one of the magnetic sensors got damaged and toggles between high and low all the time, even without the trackball beeing moved.
Did anyone realized such a behaviour on a G1?
Any comments are welcome!!
Regards,
scholbert
Note that the trackball on HTC DREAM is identical to the trackball used in RIM cripplephones, so you can find a replacement easily... you can probably get a broken RIMjunk for $5 with good trackball hardware, or you can try at something like blackberrytrackball.com.
Hey lbcoder,
i knew that the touchball is identical to those used in the blackberries.
Thanks anyway to add this info and for pointing me at the web link!
Got a spare part with broken flat cable from another G1 device.
I'll have to do some further testing and then start the soldering job
BTW the trackball itself is not the damaged part. It's one of the magnetic sensor parts, i suppose.
Would be interesting if anyone else ever was affected by some irritating trackball issues?
Regards,
scholbert
It *is* magnetic though, so theoretically it *could* be an issue with the mechanical components rather than with the sensor itself... i.e. something stuck in the wrong place getting picked up by the sensor as continuous. Unless you've tried swapping them out already.
If you haven't already, I would at least try that. No need to go all the way to soldering just to find that it was something else
...
If you haven't already, I would at least try that. No need to go all the way to soldering just to find that it was something else
Click to expand...
Click to collapse
Sure, just did some test with the other mainboard (connector for touchscreen is damaged on this part).
The trackball behaves normal with this combination.
So the sub-PCB must be O.K.
I'll try searching for something weird on the original mainboard.
Damn, this would be much harder to fix i suppose
I'll keep you informed!
Anyway, maybe the datasheet would be of any use for the curious geeks
Best regards,
scholbert
experts welcome
Hi again,
after some more testing and examination of the hardware stuff, i'm in doubt that this problem is hardware related.
So i started to think of some software related issues.
I know that bootcode and Android filesystem should be aware of bad blocks in NAND memory.
But anyway here's the history of the device (so far i know it):
- It came to me with stock bootloader and firmware 1.5
- A stock update was made to firmware 1.6
- I did a downgrade to RC7 using a goldcard
- Rooted the device using telnet
- Installed cm-recovery-1.4
- Followed the steps from cyanogen's wiki to move to v4.2.12.2
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
- Also did a radio update to 2.22.19.26i
- Installed Hard-SPL as well
Everthing went fine, also no problems during registering to a google account.
I am able to boot into HSPL and the cm recobery is also intact.
It's very strange that the trackball weirdness did not change during all these up/downgrades.
I also got some issues with the power button.
Sometimes the device can not be set to sleep and immediately comes back into active state
Apart from that the device behaves quite normal...
What the hell is wrong with this device?
Could there still be some corrupt areas in NAND caused by bad blocks even after reflashing the system?
Any advice would be welcome!
Regards,
scholbert
scholbert said:
Would be interesting if anyone else ever was affected by some irritating trackball issues?
Click to expand...
Click to collapse
Yes, my trackball likes to 'triple-click', which causes issues sometimes, especially when submitting web forms. I even have to use Ra_mon recovery over cyan because he has option to use talk button where my trackball multi-clicking would bypass the 'click home to continue any other key to abort' by auto-clicking to abort.
Hi jalsing,
thanks for your reply
Yes, my trackball likes to 'triple-click', which causes issues sometimes, especially when submitting web forms. I even have to use Ra_mon recovery over cyan because he has option to use talk button where my trackball multi-clicking would bypass the 'click home to continue any other key to abort' by auto-clicking to abort.
Click to expand...
Click to collapse
Sounds like hardware related damage, because this occurs in recovery mode as well. Maybe the pushbutton underneath the trackball causes this issue, while pressed.
Could be some corrosion or similar causing this...
Is there anyone who made some experience with file corruption or bad blocks?
Regards,
scholbert
scholbert said:
I also got some issues with the power button.
Sometimes the device can not be set to sleep and immediately comes back into active state
Click to expand...
Click to collapse
I have noticed some weirdness in the power button, but I am thoroughly convinced that, at least in my case, it must be hardware related.... if I just shove down on the power button with the pad of my finger, it goes off and then right back to the lock screen. If I press the power button on the 9-clock point with a finger nail, it behaves as expected.
Although I must admit that this appeared coincidentally with a radio firmware upgrade.
Hey there,
I have been having an odd issue too although one that has not been mentioned. About a week ago when i scrolled "left" or while landscape "down" the trackball got jammed every 3 rotations. When you continue scrolling it repairs itself temporarily and then returns. This issue is still present but is not quite so bad.
I'm guessing that this would also be a hardware issue. Its not at a stage where its overbearingly annoying yet, just wondering if anyone else has similar issues.
Hi vonapets,
have you tried to check your hardware with HTC Dream diagnostic programm on sdcard? You'll have to create a "goldcard" and with the file DREADIAG.nbh.
Insert the card and enter bootloader mode, the test software will load automatically. Please search the forum, if you don't know what i'm talking about.
Anyway i did these tests on my device sometime ago and all hardware test were successful.
That's why it's all so strange
Especially i run the button test several times, and the test software did pass with no errors.
Regards,
scholbert
???
It's me again
Seems that i'm nearly the only one who suffers from this specific trackball issue.
Anyway i won't give up so early and i really hope to find the reason of this erroneous inputs.
After checking some of the system libs and the framework files concerning file integrity, i started some rudimental debugging with adb.
Working with the tool getevent i found out that input event2 (trackball) is detected correctly and disappears if the trackball remains untouched.
When the random inputs are going to start, input event3 (virtual keyboard) occurs though i did not touch anything (especially not the virtual keyboard)
If i am at home screen the inputs hit google search entry field and most of the time the number "3" is printed.
Input event3 stays active until i fiddle around with the trackball or press some hardware buttons. This sometimes stops the weirdness
I also did check the interrupt counting with cat /proc/interrupts.
Everything looks quite normal....
I am really wondering what is causing this.
Maybe it is a side effect from some damaged hardware part (maybe MSM7201 itself) or it is some software bug that has never been observed before.
Maybe it is the result of some bad timings...
Really got no clue right now!
EDIT: Just for completeness. Also did perform RAM test and other hardware diagnostic with DREADIAG. No errors here!
Regards,
scholbert
jalsing said:
Yes, my trackball likes to 'triple-click', which causes issues sometimes, especially when submitting web forms. I even have to use Ra_mon recovery over cyan because he has option to use talk button where my trackball multi-clicking would bypass the 'click home to continue any other key to abort' by auto-clicking to abort.
Click to expand...
Click to collapse
+1
i have trouble using recovery too. I have to press it very lightly to get it to select only once otherwise it clicks several times ><
Not a huge issue for me really, i don't use it that often, but it is pretty irritating.
But, no. I've never had it enter any numbers or anything, that is strange.
However, i do have a strange problem where when the phone receives a slight knock, like if it's in my pocket and it bangs against something, or i drop it a couple of inches onto my desk or something, a random app will launch. I have no idea why this happens and it's not anything coming in contact with the screen because it happens even when it's locked. It's usually the market which opens too for some strange reason. Oh, it also reboots sometimes too
Yeah, i think i need a new phone
scholbert said:
It's me again
Seems that i'm nearly the only one who suffers from this specific trackball issue.
Anyway i won't give up so early and i really hope to find the reason of this erroneous inputs.
After checking some of the system libs and the framework files concerning file integrity, i started some rudimental debugging with adb.
Working with the tool getevent i found out that input event2 (trackball) is detected correctly and disappears if the trackball remains untouched.
When the random inputs are going to start, input event3 (virtual keyboard) occurs though i did not touch anything (especially not the virtual keyboard)
If i am at home screen the inputs hit google search entry field and most of the time the number "3" is printed.
Input event3 stays active until i fiddle around with the trackball or press some hardware buttons. This sometimes stops the weirdness
I also did check the interrupt counting with cat /proc/interrupts.
Everything looks quite normal....
I am really wondering what is causing this.
Maybe it is a side effect from some damaged hardware part (maybe MSM7201 itself) or it is some software bug that has never been observed before.
Maybe it is the result of some bad timings...
Really got no clue right now!
EDIT: Just for completeness. Also did perform RAM test and other hardware diagnostic with DREADIAG. No errors here!
Regards,
scholbert
Click to expand...
Click to collapse
Virtual keyboard? Or touchscreen? Is the virtual keyboard actually listed as a separate input from the touchscreen? If it is, then how could it even be triggered when the vk isn't even opened? Or is the vk open when this weirdness happens? Could it simply be the digitizer that's borked?
Here's a REAL SIMPLE IDEA: clean the digitizer with rubbing alcohol. Can't hurt, and now that you bring touch events into the picture, there is a little bit of a dejavu feeling starting to come over me -- not from personal experience mind you, but I do recall someone mentioning something about a greasy digitizer causing some weird problems.... that went away when it was properly cleaned.
And if nothing else, if it happens to be a digitizer problem and the digitizer is totally borked, try disconnecting it. You should still be able to navigate by trackball and hack on it without a functioning touchscreen.
I know it sounds confusing, but it's true...
Thanks for the replies!
Is the virtual keyboard actually listed as a separate input from the touchscreen?
Click to expand...
Click to collapse
Yepp!
If it is, then how could it even be triggered when the vk isn't even opened?
Or is the vk open when this weirdness happens?
Click to expand...
Click to collapse
Yepp!
BTW, you may type characters on the vk simultanously, while there are numerous 3's fired from somewhere inside the system.
The ascii changes if i also scroll the trackpad....
If you are able to close vk it opens up again randomly
Could it simply be the digitizer that's borked?
Click to expand...
Click to collapse
Nope!
Already did test with disconnecting the digitizer, same behaviour.
Very wicked and confusing
I really think there must be something destroyed inside the MCU.
Short circuit or ESD damage on a GPIO bank of the chip.
I will do further debugging.....
scholbert
...not givin' up
Hey there,
i don't know if this is still of interest for someone, but anyway here's updated information about this confusing behaviour:
- booting into recovery console (different kernel, only initrd running from RAM)
- scrolling up with the trackball causes ASCII char "u" in this console
- after scrolling the hardware keyboard is blocked
Using SHR kernel:
- used sd boot image from leviathan and flashed it to the boot partition
- sdcard is used as rootfs
- system boots up after login i enter the console
- scrolling up with the trackball causes strange ASCII string "u542i3" in this console
- after scrolling the hardware keyboard is not blocked
Pretty sure that some parts of hardware are causing this "ghost" input.
I decided to put the mainboard into pure alcohol for some hours.
Though the humidity stickers on my mainboard never turned to red, i just want to make sure that there's no dirt causing this strange effect.
Anyway it's my last hope....
P.S.: Anyone ever programmed a simple commandline tool to observe the state of the systems GPIO?
Would be very helpful to find the needle in the stack
EDIT: In the meantime i found out a lot, about the internal components of the HTC dream.
If there's some interest, i may open up a new thread post some information about it.
Cheers,
scholbert
O.K. no ideas anymore.
Quoting myself:
scholbert said:
...
I decided to put the mainboard into pure alcohol for some hours.
...
Anyway it's my last hope....
Click to expand...
Click to collapse
Last hope has gone!
Some hardware part has also gone, i suppose.
Battery life was always very worse using this mainboard, which is another indicator, that something hardware related had gone mad.
P.S.: Anyone ever programmed a simple commandline tool to observe the state of the systems GPIO?
Click to expand...
Click to collapse
Anyone??
Whatever, i think i'll use that mainboard for some awesome experiments
Bye bye,
scholbert
Hey, new to this forum, and just stumbled across your post searching for a resolve to my problem, which seems to be very similar to yours.
Phone seems to work fine except:
When rolling trackball up (even slightest movement) I get virtual keyboard appearing on screen and u542i3.....(continuous 3's) types into the searchbar.
Also MENU button is inop, although one on keyboard is ok.
When locked, sometimes the screen and key backlights constantly go on and off.
Seems to flatten the battery pretty quick.
I stripped the phone checked everything clean and dry etc, tried turning the trackball upside down on the offchance, but no change. I have done nothing software related as I'm not too clued up on that side of things. It has the std 1.6 operating system as far as I know.
I have no clue where to go from here with it though, think my best bet might just be to get another one that needs a screen or something and use mine for parts?
Good to see I'm not alone with this issue though so there's a chance someone may figure it out.
....at least i'm not alone
Hi ram5ay,
thanks a lot for your reply!
ram5ay said:
...
When rolling trackball up (even slightest movement) I get virtual keyboard appearing on screen and u542i3.....(continuous 3's) types into the searchbar.
Also MENU button is inop, although one on keyboard is ok.
When locked, sometimes the screen and key backlights constantly go on and off.
Click to expand...
Click to collapse
That's exactly the behaviour of my device.
Seems to flatten the battery pretty quick.
Click to expand...
Click to collapse
True, i also observed this issue.
Seems that parts of the hardware are damaged or not set up correctly due to some other error.
As a result some of the GPIO's may act as an output and are shortened to Vio or GND. This could be a reason why the battery got drained so fast
Anyway, as i already wrote down, got no clue how to fix this.....
Best regards,
scholbert
scholbert said:
got no clue how to fix this.....
Click to expand...
Click to collapse
Cool man, no worries. Maybe futile, but I'll prob pull mine apart again and have another look, if I have any success I'll keep you posted.
Hi, I have problems with mi hd2, the buttons of my hd2 are unresponsive and my screen has become unresponsive as well, what happen is that one day I was using my phone and everything stopped working a take a closer look to the device and a found a little orange film with a black dot on the middle by the side of my device, I know that the little film is part of the buttons but I really dont know what the name of that piece is and i want to buy a spare to repair my phone because I love my device, can someone help me please, i want to fix it, thanks for your help
julioavalon2015 said:
Hi, I have problems with mi hd2, the buttons of my hd2 are unresponsive and my screen has become unresponsive as well, what happen is that one day I was using my phone and everything stopped working a take a closer look to the device and a found a little orange film with a black dot on the middle by the side of my device, I know that the little film is part of the buttons but I really dont know what the name of that piece is and i want to buy a spare to repair my phone because I love my device, can someone help me please, i want to fix it, thanks for your help
Click to expand...
Click to collapse
Unfortunately your problem seems to be much more complicated than replacing the little orange piece you found: that piece is the mobile part of one of a hardware button (volume up/down, reset, back, home, start, make/end call) and IMHO is not directly related to the problems you've described, could be just a coincidence (it should make that specific hardware button stop working and that one only!).
However you should try a hard reset and see what happens!
Good luck!
bib*oops said:
Unfortunately your problem seems to be much more complicated than replacing the little orange piece you found: that piece is the mobile part of one of a hardware button (volume up/down, reset, back, home, start, make/end call) and IMHO is not directly related to the problems you've described, could be just a coincidence (it should make that specific hardware button stop working and that one only!).
However you should try a hard reset and see what happens!
Good luck!
Click to expand...
Click to collapse
Thank you very much for your quick answer, but I already tried the hard reset and no good, nothing is responding, I do live in Costa Rica, and I really dont know how to solve the problem, I did though as well that was a software issue but nothing fixed the problem, also check all the hardware but no good(i'm studing enginering on systems).
I was did perform task 29 and install everything again but no good, and also check the digitizer but is ok.
i just want to know what the name of that part of my device is called so i can buy and try, in any case i need to replace that even if that is not the problem, also once it did worked, i place the littli orange film again on the phone where it was supposed to be, but after a while it did move and stop working again, I place it again on the right spot, but never got back to work, that is all the info that I have by now, thank you for your time
New Info: by changing from software i have noticed that on android it seems that is always like pressing a spot on the screen, because is like highlighted, and some buttons work, like the home button, so if I press it, it will highlight other option
My last HD2 had the hard end key press in order to get the touchscreen to work problem. I recently bought a new HD2, and don't want to run into this problem
michealmyers said:
My last HD2 had the hard end key press in order to get the touchscreen to work problem. I recently bought a new HD2, and don't want to run into this problem
Click to expand...
Click to collapse
If you want to avoid the problem and make phone last a lot longer use tablet tweaks so you have a set of touchscreen buttons/softkeys you can use and lock the screen with an app or widget that does that. Also only use the home or call button to power on your screen again. Also keep flashing roms to a minimum as it will make you use your power and back button more frequently.
But of course this means switching to android. Otherwise the best thing you can do is avoid using the phone.
Sent from my HD2 using xda vip edition
hengsheng120 said:
If you want to avoid the problem and make phone last a lot longer use tablet tweaks so you have a set of touchscreen buttons/softkeys you can use and lock the screen with an app or widget that does that. Also only use the home or call button to power on your screen again. Also keep flashing roms to a minimum as it will make you use your power and back button more frequently.
But of course this means switching to android. Otherwise the best thing you can do is avoid using the phone.
Sent from my HD2 using xda vip edition
Click to expand...
Click to collapse
indeed, its been the HD2s Achilles heel since day one, there are things you can do to minimize the issue such as already pointed out, using android and soft buttons, but I find that if I keep squashing the bottom right hand corner of the phone (Around the button) to keep all the different layers stuck together its unlikely the cable will fall out/get damaged which seems to be the biggest HD2 problem.
Forgot to mention you can also try to remap in wp7 button like this
call - power off
Home - back
Start - home
Back - any
The back button is more used than power button during normal use and may press in the same area as the end key.
So the rom doesn't necessary cause the touchscreen problem? Basicially, it's wear and tear on the device? If I were you using the stock rom, I would still more than likely run into this problem since the I would be using the end call key just as frequenttly hanging up phone calls?
michealmyers said:
So the rom doesn't necessary cause the touchscreen problem? Basicially, it's wear and tear on the device? If I were you using the stock rom, I would still more than likely run into this problem since the I would be using the end call key just as frequenttly hanging up phone calls?
Click to expand...
Click to collapse
Not directly of course, but depending on what type of rom you are using, how much you like using your phone, apps that have soft buttons, you may use certain keys more or less. For example you can only use one the end button turn on screen in wp7 which would force you to press on the digitizer cable at higher rate.
Also some rom's don't have end key end call enabled
But yes, it's the supposedly the wear and tear on the flex cable under the end and back key that causes touchscreen problems.
Sent from my htcLeo using xda vip edition
michealmyers said:
So the rom doesn't necessary cause the touchscreen problem? Basicially, it's wear and tear on the device? If I were you using the stock rom, I would still more than likely run into this problem since the I would be using the end call key just as frequenttly hanging up phone calls?
Click to expand...
Click to collapse
Personally, my orginal HD2 bought new at product intro lasted me 3 years. I never had any problems with the buttons. The digitizer failed and I think that was because I gave the phone to a friend to use for a few months when her phone died. She didn't use a case and probably carried the bare phone with putting pressure on the screen all the time.
I've have multiple HD2's and never had button issues. It's a matter of how you treat your hardware. Use a phone case where your keys are not exposed to being pressed accidently for long periods of time. Gently press the buttons...they don't need to be pressed hard for them to work.
As for the buttons to affect the touchscreen...the only way I can think is if the phone is crushed for periods of time over and over. I would think that would eventually have an affect on the digitizer.
hjhjhj said:
Personally, my orginal HD2 bought new at product intro lasted me 3 years. I never had any problems with the buttons. The digitizer failed and I think that was because I gave the phone to a friend to use for a few months when her phone died. She didn't use a case and probably carried the bare phone with putting pressure on the screen all the time.
I've have multiple HD2's and never had button issues. It's a matter of how you treat your hardware. Use a phone case where your keys are not exposed to being pressed accidently for long periods of time. Gently press the buttons...they don't need to be pressed hard for them to work.
As for the buttons to affect the touchscreen...the only way I can think is if the phone is crushed for periods of time over and over. I would think that would eventually have an affect on the digitizer.
Click to expand...
Click to collapse
I agree...my previous hd2 lasted about 4 years. It's an awesome phone! I have a HTC Sensation now, but personally, I think the HD2 is the phone of all phones! Wm7 looks amazing on the device! I purchased a screen and digitizer replacement from Amazon just in case in the future, and hopefully I can enjoy this phone a little while longer
there's two separate issues at work with the HD2, both kind of related due to proximity.
The first is the buttons, believe it or not, the HD2 wasn't designed to use the buttons much, don't believe me? go back to WM and see how much you use it compared to android and WP.
They use it significantly more than WM, and like all things mechanical, there is a usage limit to them.
The second issue is the digitiser, or more specifically the cable and PCB to it, this isn't damaged by pushing the buttons per-say, its more to do with flexing the cable. The root cause for this is the various layers in the LCD, digitiser and PCB, some of which are held together with glue that separates and allows the layers to move about a bit. this can also give the impression that the buttons are becoming dodgy and harder to get to work, which in turn makes the user press harder all of which flexes the cable back an forth underneath.
It probably has a lot to do with the climate you live in if your effected by the glue, hence why some folk don't have issues
but to answer your question if a ROM can damage your digitiser? no, not directly, but as pointed out, if you have separation and you use a ROM that means you push the buttons more, then you will speed up the process of the cable / PCB getting nackard.
edit, as I said tho, I try and keep all the layers together by squashing it through out the day, you dont even need to take it out of your pocket, just find the power button and squash with your thumb and forefinger above it, if I don't do it for a while you can feel the difference when you push the power button and even see that its not right