Hey guys,
so in the last couple of weeks my HTC Touch Pro has finally had its first real problem. It appears that it misreads the hardware keyboard open/close sensor. It basically flips back and forth constantly thinking the keyboard is open/closed. If I leave the keyboard open it stabilizes and is usable, but that is the only way. It is killing battery life and makes the thing a pain to use. The problem shows up in the Android OS I'm running as well as in the WinMo. so it's definitely a hardware issue (And I did a full hard reset and wipe etc as well).
Anybody aware of where the registry entry for the driver for that sensor is so I can kill the sensor? I did a registry search on a few keywords and didn't find anything obvious. If anyone can help that'd be great!
Thanks,
Steve
It's not the keyboard sensor but the gyro that is broken!
I'm not a pro at this, but there might be a way to disable the gyro driver...
it's not the g-sensor. i have ruled it out umerous ways as well as disabled it. it is without question an issue with the keyboard hardware/sensor.
I am looking for an option to disable the sensor all the time I own TP,without success. The sensor is readed by the slideout keyboard driver and I know only one man,who could help with this,but he luckily ignores my request. It is a programmer of Keyboard Config utility nicknamed Tarkim. Try to ask him and if you will have a solution,please let me know. Simply I hate the autorotation and I want to disable it.
Related
Hallo guys,
After playing around one week without any troubles I realized now that the g-sensor doesn´t work any more. The only thing I did today was to install schap’s advanced config and the remote tracker-software and after some time I recognized that my phone gets little bit warm. I wanted to deny a call by turning the phone around but nothing happens. I tried the g-senor application to calibrate, but also here the bubbles don´t move. Also the hard-reset doesn´t help anything.
Any ideas or suggestions for me, I hope I don´t have to return the phone to repair. And another question: Is the phone after a hard-reset really in the point of origin ??
thanks
juwenio
hi mate,
probably in the schaps advanced config, you have disabled the mute function, try to search through for that function in the schaps advanced config and see what it's on now
Also if advanced config doesnt remedy it do a hard reset, most likely a software thing rather than a broken accelerometer.
mrvanx said:
Also if advanced config doesnt remedy it do a hard reset, most likely a software thing rather than a broken accelerometer.
Click to expand...
Click to collapse
thanks guys for your help, but i have already restored all settings from advanced config, removed the program and netcf 3.5. and also did 2 hardresets..the problem is still alive
Thats bad luck man.
I'd put it back to the original settings and get it repaired that should be covered in the warranty...
Im guessing its most definatly a manufacurer defect since its pretty difficult to kill an accelerometer, the device would be dead elsewhere before the G sensor if it is something like a drop or an impact.
hallo friends,
wanted to tell you, that my problem has gone... some hours after my last post i tried the g-sensor once and once more and although i didn´t change anything with the phone suddenly g-sensor reacts again... it´s really curious but in the fact till now it doesn´t came back
so, thanks for your help and have a good day
juwenio
My Raphael is having the same trouble. I noticed the G-sensor not working when I tried to play Teeter. Calibration doesn't work And also other software using the G-sensor is not functioning. In Teeter the ball gets stuck in one corner and won't move. In calibration (under settings) the green indicators move and the text Calibrating" appears. After calibration the green indicator move to the uppermost and rightmost corner of the vertical resp. horizontal indicator. Running ROMeos 1.22 Dutch version with 1.02.25.19 radio.
Already tried a hard reset. Didn't do the trick. Any ideas?
I have had a similar problem wherein the G-Sensor was not working. I tried restoring the registry back to the state prior to the G-Sensor got busted but nothing seemed to work. I logged the problem with HTC Customer support. In addition to other regular things they asked me the S/N of my device. To check out the S/N of the device I had to remove the battery. It was out for a few minutes and when I put it back I thought of re-running the G-Sensor and surprisingly enough it has been working since then .
I don't know how long it would continue to work but i tried running the G-Sensor for 5-7 times and it worked. I hope it works with you as well.
Just to let you know, I even tried hard-rest twice in the past but it didn't work.
Thanx for the reply.
I'll try this and post the results here.
Not working
Tried everything.
had my hopes set on software. Seems to be a hardware problem
Going to restore ROM to original and hand it in for repair.
G-sensor fixed
Finally I returned the Touch pro with stock ROM for repair (just before warranty expired)
Pick up service at the office, and within one week the phone was send back, repaired.
Kudo's for HTC service.
Hi @ll i just bought a samsung bluetooth headset for my diamond and i already have a problem with it, it seems to be on my diamond self
whenever i use the headsets controls to forward track/ skip etc it wakes up the phone, and thus also the touchscreen, in my pocket
quite irritating
is there a way to fix this?, is this a known issue and can i return my headset based on this flaw ?
or must i wait for HTC to make a fix of some sort :S
same problem!
I have the exact same problem and know a friend of mine does as well.
If someone could fix this incredibely annoying issue... that would be GREAT
sooooooo, someone? pleeeaaaaassssssssssssssse!
http://forum.xda-developers.com/showthread.php?t=422871&highlight=sensorlock
it`s really a searchin` thing
sensor lock is fine and all, but this doesnt eliminate the problem that the display turns on and uses up the allready weak battery...
exactly.
And I don't want to be rotating my phone everytime I want to do something with it (tiny hands)... the thing will probably drop.
i "found"that igo navigator 8 has the same issue when minimised
i can deal with igo, because the safe mode setting disables touch screen
I've solved the problem. It's one key in the registry. But I'm not really sure which one, because I've changed a lot of them.
I think, it's this one:
[HKEY_LOCAL_MACHINE\ControlPanel\Phone\sleep] change to "1"
after this change, the phone will stay sleep as usual
So does anybody have a fix for this yet?
ps. the regkey doesn't exist in my phone.
Hi,
If I use the hardware keyboard (ie the one you slide out) in TomTom 7 it adds a weird character at the end of each letter, so for example if I write:
"New York"¨
It will appear on screen as:
"Nåeåwå Yåoåråkå"
Anyone have that problem and know how I can solve it?
I get it it tomtom 6 too, some peeps on here have had issues with it representing the same charater no matter what button is pressed in several different programs
yep, I get the same in TT7.
I get the same problem with TT7.... would be keen know if anyone has a fix.
yeah, I have that as well... very strange indeed...
Maybe someone comes with an answer...ya never know...
I use Tommy 7 btw...
+1 same here, pain in the ass so i just use the onscreen
I had this problem at one point but I don't now. I've been trying to think how i got rid of it.
I definatly installed the following patch http://www.tomtom.com/support/index.php?Language=1&FID=9852 other than that I played with the keyboard settings in tomtom and WM 6. Not much to go on, I hope it helps.
This seems to be a problem with the key assignment of the hardware keyboard, it behaves strange also in other applications. I solved it using the reg hack from this thread: http://forum.xda-developers.com/showthread.php?t=425646
Unfortunately, problems with auto-screen rotation appeared on my device.
i have the same problem, i found that KforTouchPro (http://forum.xda-developers.com/showthread.php?t=425646&page=4) can be use to fix the problem
Hello to all, am going to ask if anybody of you have a problem in TPs Touch Capacitive Pad? I used this app
Nav Debug Tool by HTC
http://forum.xda-developers.com/showthread.php?p=2511016
To check out this multi touch stuff in my TP (though I know before that it has a multi touch feature, I just want to check if it's working properly) but it seems that the pad has a problem. The problem was sometimes, it can register my touch and most of the time, not.. sometimes it can register the multi touch, and most of the time, not .. even the nav wheel has a problem which doesn't register the rotation most of the time. Is this a common problem in TPs or even Diamond??
I even use the signed os WM6.1 but still has a problem.. so I wonder if any of you guys having the same..
thanks!
It's been happening to me for about a year already as well. Seems like it's just defective. It resets thought after sleeping the phone and waking it. I'm not sure if it was because I used to use Sensor scroll or it's a little scratched up.
I hear the d-pad was a good conceptual idea but that is about it... I personally don't use the d-pad at all because of this, much less any of the buttons (to include the power button). On the other hand, from what I can tell about the d-pad "sensor" from using the NDT(Nav debug tool), it does seem pick up points but it seems to not like repetitive touches. It almost seems like the sensor overloads the processor to the point that it fails in terms of keeping up with the actual location that is being touched; if that makes any sense?
R^7Z said:
I hear the d-pad was a good conceptual idea but that is about it... I personally don't use the d-pad at all because of this, much less any of the buttons (to include the power button). On the other hand, from what I can tell about the d-pad "sensor" from using the NDT(Nav debug tool), it does seem pick up points but it seems to not like repetitive touches. It almost seems like the sensor overloads the processor to the point that it fails in terms of keeping up with the actual location that is being touched; if that makes any sense?
Click to expand...
Click to collapse
that made sense but why would HTC permit a buggy front pad???
You know, it seems many phone brands/cooperations come under fire due to lack of something or another; maybe proof of concept? Perhaps the debug tool is to blame? Or even the sensor degradation over time? One can only speculate so far before it becomes a volatile thought... Again, I point out the idea being good, conceptually. So, I don't know where that exactly puts us as being end users? Then again, I've never really had a decent experience with phones, much less with newer phones; my thoughts and expectations may be slightly on the negative/lesser side of things because of this.
I have the same issue. I used to use GScroll to flip pages in e-books, but finally it got so buggy I had to dump it (other GScroll features were almost impossible to use). I've used NavPad DBug. What I do find is that running the compact heaps command of SK Tools will temporarily fix things, at least most of the time. When I have NavPad DBug running, if it's logging compact heaps will clear out the traces. Somehow or other, it cleans things out when the nav pad gets confused or overloaded with inputs. But even compact heaps doesn't work all the time.
It would be sweet if the capacitative area really worked, but unfortunately it appears to get worn out about the time that you figure out all the things you can do with it. Lol.
Edit: I wonder if the device has problems distinguishing a single touch of your finger vs. several touches. That could really screw up the function of the device.
Hello,
i have issues with the Display Rotation.
The Accelerometer don´t work anymore at my phone. Last Week i was wondering that the Display won´t rotate at the Album. Then i checked the Display Settings. Auto Rotate was checked.
at the Service Menu *#*#7378423#*#* the Accelerometer don´t respond. But the Gyroscope work fine.
At this Time i have installed the Concept Software from Sony. Today i´m back home from Holiday i go back to offical Stock Software. But it won´t work also.
Smartrotate on or off are the same...
The last idea is to repair the Software with the PC Companion. Is there an option to calibrate the Accelerometer?
I have the same issues with my D6653 - auto rotation doesn't work (but very rarely it does come back). In service menu the Accelerometer doesn't respond, as well as Proximity switch is off and doesn't work on calls.
This is not a rom-specific problem as I've tried to revert back to stock firmware but alas no changes. It must be some miscommunication between hardware and software.
Any ideas what to do? Can it be related to kernel?
yesterday i've had the same problem i needed to wipe to have the accelerometer back to work
Hi all rather than opening a new thread I am upping this one
On my D6603 screen rotation is very erratic and often not working.
Any idea what I can investigate?
I wander if it could be app/service related of hardware deficiency.
Thanks!
Any luck with this?
I am currently using an EM95X Android Box with a Viewsonic touch screen. The touch screen has been working perfect with the box. My issue is with the rotation ability. Anytime I force the screen into portrait mode the system UI crashes. Unfortunately, I need the monitor view to be vertical. I cannot figure out how to stop it from crashing. I have tried several rotation apps with the same results.
I have went into the build prop to view the rotation texts and the only thing I have found is this:
"Persist.sys.app.rotation=middle_port"
I thought I might be able to find somewhere I can change the rotation, but I have not.
Any suggestions?