Database Users

Sliding Keyboard getting loose?

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

Touch screen sensitivity

How to change the sensitivity of the screen ?
I want it to be more sensitive to finger touches so i dont have to apply any pressure on the screen to register a "click."
Is there any way to change this ?

I heard somewhere that when you calibrate the screen, it not only calibrates where you touch the screen, but also how much pressure you apply? Is that true anyone?

Seems true to me, barely takes any pressure for me to use the touch screen.

I had the same problem wen I formatted my phone again, I had to calibrate the phone again and it worked perfectly.

bharat4ever said:
I heard somewhere that when you calibrate the screen, it not only calibrates where you touch the screen, but also how much pressure you apply? Is that true anyone?
Click to expand...
Click to collapse
That is AFAIK true.
To recalibrate, go to Start -> Settings -> choosing the system tab -> tap the screen icon.
There, you can recalibrate where you touch the screen and how much pressure you apply to the touches.

Thanks guys.
Just tried to re-calibrate the screen with little pressure by my clicks, and it works better now.

To recalibrate, go to Start -> Settings -> choosing the system tab -> tap the screen icon.
Click to expand...
Click to collapse
My X1a arrived from a previous owner without the stylus working, so I'm hopeful that calibrating the screen will remedy the problem like it has for so many (altho a handset problem is still a possibility).
However, before I do (which will be after work today), I was hoping to hear why, or how anyone could screw it up, so that I could either troubleshoot the current problem, or minimally not screw up the procedure myself.
This is my 1st smartphone so pardon the newbish query ...
TIA
and cheerios from the Avalon Peninsula

*sigh*
A quick (5 seconds?) search and:
http://forum.xda-developers.com/showthread.php?t=485037&highlight=screen+sensitivity

SquidgyB said:
*sigh*
A quick (5 seconds?) search and ...
Click to expand...
Click to collapse
Thanx Squidgy ... my search tumed up this thread only, altho your thread seems to be more about an alternate procedure, and does come up short on why or how anyone could screw up the primary procedure(?)
Edit: I also could have been more clear ... ie, finger touch seems to work well, while my stylus does not ... and that's a bit of a mystery to me(?)
cheerios

I Have found that if you calibrate with finger, then stylus doesnt work so good but if you calibrate gently with stylus, then finger and stylus works far better
try it

SquidgyB said:
*sigh*
A quick (5 seconds?) search and:
http://forum.xda-developers.com/showthread.php?t=485037&highlight=screen+sensitivity
Click to expand...
Click to collapse
This post is old.
almost 2 months before softtouch was released.

flub said:
I Have found that if you calibrate with finger, then stylus doesnt work so good but if you calibrate gently with stylus, then finger and stylus works far better ...
Click to expand...
Click to collapse
Thanx Flub!
My own approach to the procedure (called an alignment) took me around the screen several times. I don't know if it was trying to acquire some minimum threshold of satisfaction, but I might imagine it leading some users to pressing harder and harder. Your suggestion was an impetus for using soft touches only, and the result is a stylus touch that is now very sensitive.
cheerios

rotsu said:
This post is old.
almost 2 months before softtouch was released.
Click to expand...
Click to collapse
I don't understand what you mean "this post is old"...
The methods described in the post work, and I can't see any other newer versions of that softtouch, apart from the softtouch keyboard which is a completely different app.
As for why you would want to use the 2nd procedure (I don't know how you could bugger up a .cab installation), personally I prefer a quick clean reg edit to installing a cab. But each to their own.

Strange trackball/keypad issue

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.

touch screen not working

So my touch screen hasn't been responsive for the last few days. It's only partially responsive sometimes and not at all others. Has anyone else experienced this or know how to fix it? If not does anyone know if this would count as a manufacturer defect and I fould get it replaced?

For how long have you had it? It should go under warranty.

pak256 said:
So my touch screen hasn't been responsive for the last few days. It's only partially responsive sometimes and not at all others. Has anyone else experienced this or know how to fix it? If not does anyone know if this would count as a manufacturer defect and I fould get it replaced?
Click to expand...
Click to collapse
Is your phone overclocked? Or even rooted?
Sent from my HTC Vision using XDA App

I'm having a touchscreen issue too. However it only occurs when keyboard has been flipped out. The entire screen's touch capability does not work, including the touch buttons search, back, menu and home. If you close the screen over the keyboard even a little bit. The touchscreen works perfectly. Even if you then flip it all the way back out again it works, until you close and open it again.
Anyone experienced this? Or have an idea if this should just be replaced under warranty?

novakry said:
I'm having a touchscreen issue too. However it only occurs when keyboard has been flipped out. The entire screen's touch capability does not work, including the touch buttons search, back, menu and home. If you close the screen over the keyboard even a little bit. The touchscreen works perfectly. Even if you then flip it all the way back out again it works, until you close and open it again.
Anyone experienced this? Or have an idea if this should just be replaced under warranty?
Click to expand...
Click to collapse
Sounds like a classic case of bad ribbon cable.
If you are under warranty, replace it. If not, it could be something as simple as replacing the cable the connects the two halves of the phone together.

burtcom said:
Sounds like a classic case of bad ribbon cable.
If you are under warranty, replace it. If not, it could be something as simple as replacing the cable the connects the two halves of the phone together.
Click to expand...
Click to collapse
Yeah getting it collected tomorrow, is this a common issue with the DZ then?

novakry said:
Yeah getting it collected tomorrow, is this a common issue with the DZ then?
Click to expand...
Click to collapse
No, not at all..It might even just be the ribbon lossened from the connector or disconnected..Unless stuff hit the fan, ur phone should be soon back to u..

chris2busy said:
No, not at all..It might even just be the ribbon lossened from the connector or disconnected..Unless stuff hit the fan, ur phone should be soon back to u..
Click to expand...
Click to collapse
Been a week now, do you know roughly how long it takes for a HTC repair? Falling back to an old hero isn't great, but at least I have a phone

Dual Monitor (Touch/Non-touch) Fix.

Hi All,
I have a dual monitor setup with one touch and one non-touch. The problem that I had was in-order to make my touch screen work I had to make it the default. I did not want that as my other monitor (non-touch) was larger. I have been searching all the various forums for a solution. I found it on the Surface Geek web site. The instructions follow:
-----------------------------------------------------------------------------------------------------------
So, I know that you guys are going to think I am crazy, but I recently bought a new machine that has a touchscreen. I had already bought a touchscreen for my old machine and decided I wanted to go dual monitors with each a touchscreen. I found an interesting problem. It appears that Window 8 sees the touchscreen input differently than the monitor. Sorta makes sense, how is it supposed to know which touchscreen goes to which monitor. I looked on the web to see if I could find a solution and nothing could be found except others complaining about this as well. Well, I am happy to say that I figured out how to associate the touchscreen of each monitor to the correct one.
You have to go into your control panel. Click on Hardware and Sound. Click on Tablet PC Settings. Click on Setup under Configure your pen and touch displays. Then you have to touch the screen that is showing the text. Click OK or Next and then click the next one when the words come on this one. This allows the computer to know which screen is which screen. Otherwise it appears that it just thinks that both are one. Hope this helps.
--------------------------------------------------------------------------------------------------------------
Regards.