So it's been a month since I got my HTC Touch pro and all the problems I have with it, I've had with the HTC TYTN II. To list them:
- Volume is too low during conversations, it has to be fairly quiet around to be able to hear the other person (even with the volume turned way up)
- There's a 2-3 ring delay on incoming calls.. which means people hang up before you get a chance to answer.
- Sometimes trying to call a number, the phone will just display the Calling Number screen and you hear no sound at all in the speaker.. then after 10 seconds it will end with 3 beeps.. Like it couldn't get a signal or something, even though there's plenty of signal on the signal gauge. You try again 2-3 times before it works.. REALLY annoying (Never had a phone that did that, other than the TYTN II!)
- Answers calls in pocket. You go for the phone, but the touch screen is on and you answer or hang up (in my case apparently almost always hangs up) while the phone is still in your pocket. Also VERY annoying.
- Alarm or snooze malfunctions. This happens rarely for me, but since I use it everyday as my alarm for waking up, I notice! It's not because I sleep past the alarm. I've been lying awake listening for it to ring... the vibrator works, but no sound is played. This means that I can't trust my phone to wake me up if I'm going to catch a plane or other important stuff. It's very rare, but it happens.. it also did on my TYTN II, except that didn't even vibrate! My guess is windows is busy doing something else .. then doesn't play the sound properly.
- Then there's the slowdowns.. not really a fault, but like windows 95 it can become very slow or unresponsive for a short period for unknown reasons. A phone has to work when you need it... not delay you for 30 secs while it thinks things over. I've had to reset my phone a couple of times this month. (No I didn't run 10 apps at the same time while trying to use TF3D to look at pictures)
- It takes 4 seconds to lock the phone (So that it doesn't also MAKE calls in your pocket) .. is there a way to tweak this? Like only pressing the off-hook button for 1-2 seconds instead?
These problems are the reasons that I'm considering selling my phone to some other unfortunate person. They are BASIC functions that just have to work! I love the HTC touch pro for it's PDA functionality and my Tom Tom maps etc. but I'm really starting to hate it for these basic functionalities that work very poorly!
I know other people have experience the same problems.. couldn't we make a sticky with problems and possible solutions for it? I also really hate that fact that I have to hack my phone in able to make it function properly!
ssndk said:
So it's been a month since I got my HTC Touch pro and all the problems I have with it, I've had with the HTC TYTN II. To list them:
- Volume is too low during conversations, it has to be fairly quiet around to be able to hear the other person (even with the volume turned way up)
Click to expand...
Click to collapse
Tweaks enough around
- There's a 2-3 ring delay on incoming calls.. which means people hang up before you get a chance to answer.
Click to expand...
Click to collapse
I don't have that problem?
- Sometimes trying to call a number, the phone will just display the Calling Number screen and you hear no sound at all in the speaker.. then after 10 seconds it will end with 3 beeps.. Like it couldn't get a signal or something, even though there's plenty of signal on the signal gauge. You try again 2-3 times before it works.. REALLY annoying (Never had a phone that did that, other than the TYTN II!)
Click to expand...
Click to collapse
never had that either
- Answers calls in pocket. You go for the phone, but the touch screen is on and you answer or hang up (in my case apparently almost always hangs up) while the phone is still in your pocket. Also VERY annoying.
Click to expand...
Click to collapse
try this solution
- Alarm or snooze malfunctions. This happens rarely for me, but since I use it everyday as my alarm for waking up, I notice! It's not because I sleep past the alarm. I've been lying awake listening for it to ring... the vibrator works, but no sound is played. This means that I can't trust my phone to wake me up if I'm going to catch a plane or other important stuff. It's very rare, but it happens.. it also did on my TYTN II, except that didn't even vibrate! My guess is windows is busy doing something else .. then doesn't play the sound properly.
Click to expand...
Click to collapse
Did you try a different alarm already?
- Then there's the slowdowns.. not really a fault, but like windows 95 it can become very slow or unresponsive for a short period for unknown reasons. A phone has to work when you need it... not delay you for 30 secs while it thinks things over. I've had to reset my phone a couple of times this month. (No I didn't run 10 apps at the same time while trying to use TF3D to look at pictures)
Click to expand...
Click to collapse
Don't have that problem
- It takes 4 seconds to lock the phone (So that it doesn't also MAKE calls in your pocket) .. is there a way to tweak this? Like only pressing the off-hook button for 1-2 seconds instead?
Click to expand...
Click to collapse
Now you mention it, yes, that is annoying... Would love to see a tweak for that as well!!
These problems are the reasons that I'm considering selling my phone to some other unfortunate person. They are BASIC functions that just has to work! I love the HTC touch pro for it's PDA functionality and my Tom Tom maps etc. but I'm really starting to hate it for these basic functionalities that work very poorly!
I know other people have experience the same problems.. couldn't we make a sticky with problems and possible solutions for it? I also really hate that fact that I have to hack my phone in able to make it function properly!
Click to expand...
Click to collapse
Have you considerd a custom Rom yet? I am currently running the DCS Rom, and don't have the problems you mention above. It made my TP much more responsive!
A lot of these problems though, are mentioned throughout this forum, and can be solved. Either by ROM updating, or tweaks... What Rom are you running?
I understand completely. I feel differently though. My TP is the best phone ever. The issues I have were seen on my previous devices (HTC devices for the US). The faster processor, increased storage, and TF3D make me happy. Don't get me wrong, I have cussed at this phone, missed inportant business calls, and missed a flight thanks to the alarm. I soft reset 1 - 5 times a day to proactively minimize these issues. But overall, the TP is a huge improvement over my Wing. So long as my new devices are improvements to the one before, I am happy. I can't live with a standard cell phone, and love my Raphael.
joeltje said:
I don't have that problem?
Click to expand...
Click to collapse
Try calling your phone from a land line phone.. how long does it take before your cell actually start ringing?
joeltje said:
Did you try a different alarm already?
Click to expand...
Click to collapse
Yes, but it happens so rarely I can't say if its the sound. Besides, it's the rooster sound that came with phone. No matter what it should never happen. It happened on my TYTN II too.. So I guess it's probably a windows thing.
joeltje said:
Have you considerd a custom Rom yet? I am currently running the DCS Rom, and don't have the problems you mention above. It made my TP much more responsive!
Click to expand...
Click to collapse
Hmm.. I might try that.. but I often see people start having entirely different problems with their phone then (lock ups and strange behaviour). If there is a stable ROM that fixes these issues and doesn't break down hard once every week. I'm all for it!
I'm running the standard ROM that came with the phone. Ver.: 1.90.403.6 DAN (Danish) ROM date 08/23/08, Radio: 1.02.25.19, Protocol: 52.33.25.17U
If I call my cellnr. from the home phone, it starts ringning as quickly as all my other mobile phones... So no, I really don't have that problem, thoughj I did just see another topic from somebody with exactly you problem: http://forum.xda-developers.com/showthread.php?t=432415
You might want to follow that.
On the alarm, I have 2 kids, so I don't use an electrical alarm Sorry...
The different ROM may be something you can test at least. It fixed a lot of annoyances for me anyway. Look in the Wiki for different Custom Roms, there are a couple out there, and for me, DCS worked best. You can always go back to original, should you not like the ROM. I'm running DCS now for three days, no resets, and it is still fast....
ssndk said:
- Sometimes trying to call a number, the phone will just display the Calling Number screen and you hear no sound at all in the speaker.. then after 10 seconds it will end with 3 beeps.. Like it couldn't get a signal or something, even though there's plenty of signal on the signal gauge. You try again 2-3 times before it works.. REALLY annoying (Never had a phone that did that, other than the TYTN II!)
Click to expand...
Click to collapse
The issue above really annoying. Normally that will cause my TP to go mute and can't hear each other. Have to soft reset. This issue is discuss in another thread here. Since I'm overseas for at the moment, can't go complain to my vendor.
ssndk said:
- It takes 4 seconds to lock the phone (So that it doesn't also MAKE calls in your pocket) .. is there a way to tweak this? Like only pressing the off-hook button for 1-2 seconds instead?
Click to expand...
Click to collapse
Using the registry hack for the touch diamond I'm now using the "lock on backlight turned off" fix.. it works, and my phone locks when I press the screen off button. Way less annoying than waiting 4 seconds for it to lock.
HKEY_CURRENT_USER\ControlPanel\BackLight\AutoDevic eLockEnable from 0 to 1 and everytime your backlight goes off the device is locked
Nice, 1 Question though; What happens if you make a call? The display goes of as well then, will the keyboard then lock as well? Cause that's not handy, to say the least
joeltje said:
Nice, 1 Question though; What happens if you make a call? The display goes of as well then, will the keyboard then lock as well? Cause that's not handy, to say the least
Click to expand...
Click to collapse
The touch screen locks, but the keyboard (Off-hook etc.) button doesn't..
So if I'm listning to my voicemail, and need to press "3" for deletion, I can't? Or will it disable after I extract my stylo?
joeltje said:
So if I'm listning to my voicemail, and need to press "3" for deletion, I can't? Or will it disable after I extract my stylo?
Click to expand...
Click to collapse
you can extract the stylus but the you have to juggle around with it OR you can press the standby button on top to unlock it. It's a pain I know but the problem is that it is a touch screen so pressing a button to unlock is less worse than without it.
So functionality actually remains as it is now... That's good, I'll give it a try!
joeltje said:
So if I'm listning to my voicemail, and need to press "3" for deletion, I can't? Or will it disable after I extract my stylo?
Click to expand...
Click to collapse
It unlocks when the stylus is extracted..
ssndk said:
So it's been a month since I got my HTC Touch pro and all the problems I have with it, I've had with the HTC TYTN II. To list them:
- There's a 2-3 ring delay on incoming calls.. which means people hang up before you get a chance to answer.
I know other people have experience the same problems.. couldn't we make a sticky with problems and possible solutions for it? I also really hate that fact that I have to hack my phone in able to make it function properly!
Click to expand...
Click to collapse
Sounds like you are using a ringtone from your microSD card. This will cause a delay. Your ringtones need to be copies to your device and activated by holding the stylus over your selection & hit set as ringtone.
Hope this helps,
Rgs,
J
ssndk said:
The touch screen locks, but the keyboard (Off-hook etc.) button doesn't..
Click to expand...
Click to collapse
Try SensorLock. It's a great little utility that unfortunately has stopped working for me. Must be something I poked somewhere. lol
As for the alarm, mine works fine... but I do notice the ringing a couple of times on the sending end before the phone starts to ring. I'd sort of passed that off to a network thing, not a phone thing.
The 3 second ringtone delay is a WM issue. Look at the postings for VAlert in the general hacking section. The only known fix is http://www.tweaks2k2.com/portal/staticpages/index.php?page=20050224182009983
but no one seems to have figured out their registry setting change...
Quote:
- Alarm or snooze malfunctions. This happens rarely for me, but since I use it everyday as my alarm for waking up, I notice! It's not because I sleep past the alarm. I've been lying awake listening for it to ring... the vibrator works, but no sound is played. This means that I can't trust my phone to wake me up if I'm going to catch a plane or other important stuff. It's very rare, but it happens.. it also did on my TYTN II, except that didn't even vibrate! My guess is windows is busy doing something else .. then doesn't play the sound properly.
TRY G-Alarm. It works well for me.
Klaxon (sp?) alarm looked cool and would have also been practical, but it would crash - totally unreliable.
[email protected] said:
Sounds like you are using a ringtone from your microSD card. This will cause a delay. Your ringtones need to be copies to your device and activated by holding the stylus over your selection & hit set as ringtone.
Hope this helps,
Rgs,
J
Click to expand...
Click to collapse
No, in my TPro the delay is exactly the same (oviously using the same mp3 file in memory card or in the device)..i've reduced delay sound installing Diamond tweaks and setting "without delay" in ring tone..then i've erased diamong tweaks because use too much battery now i have only 1 ring with light (and identified call incoming on the screen) and without sound, and BEFORE the second ring my device correctly sound
bugsykoosh said:
The 3 second ringtone delay is a WM issue. Look at the postings for VAlert in the general hacking section. The only known fix is http://www.tweaks2k2.com/portal/staticpages/index.php?page=20050224182009983
but no one seems to have figured out their registry setting change...
Click to expand...
Click to collapse
If your referring to this one,
108-Allow users to disable the 3 seconds delay between rings in devices with Windows Mobile Phone Edition
Click to expand...
Click to collapse
see the following thread at PPCGeeks.
If your talking about the fact that the NAV wheel starts flashing 5 seconds before the audio starts playing, then it's not the same scenario.
ssndk said:
Using the registry hack for the touch diamond I'm now using the "lock on backlight turned off" fix.. it works, and my phone locks when I press the screen off button. Way less annoying than waiting 4 seconds for it to lock.
HKEY_CURRENT_USER\ControlPanel\BackLight\AutoDevic eLockEnable from 0 to 1 and everytime your backlight goes off the device is locked
Click to expand...
Click to collapse
I have a HTC TouchPro and had the same issue of not wanting to press the long press end key for 5 seconds to lock the phone. I tried the code you gave and unfortunately the phone still does not lock when I push short press the power button to turn off the back light and put th phone in sleep mode. I really want this to work since when I am driving, I think when I go through good and bad coverage areas, the phone will automaticallly wake up about 3 times each way, so if it is not locked, I can accidentally call people while driving.
Since a couple of weeks, my OPO switch itself to vibrate-mode, and I have no clue where it's coming from.
Tasker, Locale and such apps have been deleted.
Profiles are deactivated.
But still... Even when I manually switch on sound notification and ringtone, it goes back to vibrate mode after a while.
I've reviewed every settings that could be involved with that, but I still don't find a solution.
Is this a known bug ?
Is there a setting I missed ?
I couldn't say, but any help is welcome (I'm currently looking for a job, I need to hear my phone and not missing any call...)
Thx by advance !
Don't know which rom you are using, but at least try to reflash your rom it will be fixed i guess
Chinaroad said:
Don't know which rom you are using, but at least try to reflash your rom it will be fixed i guess
Click to expand...
Click to collapse
I kept the original rom (Cyanogen) and it's updated...
I want to re-roll this phone for multiple reasons but I still keep faith in the fact that I don't need to reflash anything in order to have a phone actually ringing
PascalDk said:
I kept the original rom (Cyanogen) and it's updated...
I want to re-roll this phone for multiple reasons but I still keep faith in the fact that I don't need to reflash anything in order to have a phone actually ringing
Click to expand...
Click to collapse
You sure you haven't set up CM profiles in settings? Does this happen at specific TIMES (eg. 2PM every afternoon) or at specific INTERVALS (eg. 2 hours after you manually enabled ringer)?
The Dork Knight Rises said:
You sure you haven't set up CM profiles in settings? Does this happen at specific TIMES (eg. 2PM every afternoon) or at specific INTERVALS (eg. 2 hours after you manually enabled ringer)?
Click to expand...
Click to collapse
As I said in the original post, Profiles are deactivated + Tasker and such apps are deleted.
I still don't get if it happens at specific time (ie: every day at 2 pm), or after a specific delay (ie : 2 hours after I switch the ringtone back).
It seems to be the second option, but I lack a good monitor app that could brings me some intel about what's happening on my phone and what triggers events
PascalDk said:
As I said in the original post, Profiles are deactivated + Tasker and such apps are deleted.
I still don't get if it happens at specific time (ie: every day at 2 pm), or after a specific delay (ie : 2 hours after I switch the ringtone back).
It seems to be the second option, but I lack a good monitor app that could brings me some intel about what's happening on my phone and what triggers events
Click to expand...
Click to collapse
if you discover that it happens at specific time, just plug in the phone in PC and get a logcat
effry said:
if you discover that it happens at specific time, just plug in the phone in PC and get a logcat
Click to expand...
Click to collapse
Thx.. I'm going to digg about logcat then (I see what it is but I never use that).
Is there any way to look into a logcat (or other log-stuff) by searching events (or text) instead of time-stamp ?
Is there any app or software that helps digging this full load of data ?
I hate myself right now... I'm using MyPhoneExplorer and there is a setting to switch your phone ringtone while connected to a known-wifi.
And yes, I have activated this settings myself
In a word, when you don't find a solution on XDA or any forum, the bug is probably you...
#lessonlearned
Anyone else having problems with the watch loosing connection to the phone? And only solution is to power cycle the watch.
I had it happen once over the last week I had watch (got it on 8/26). It connected then unconnected repeatedly. After I power cycled phone and watch it never happened again. I'm connected to watch via bluetooth. Did you have issue once or repeatedly? Since I cycled powered it has been rock solid. I let my watch get to 1% on last charge and I never lost connection.
Drops a least once a day. Toggling Watch BT off then on restores it. Don't need to pwer cycle. Got an update today, maybe that'll fix it.
only happens for me when i'm too far away from phone... BUT is there no way to disable this annoying vibration on disconnect?
setting in developer settings isn't functional.
if anyone finds out how to disable this PLEASE let me know
RieGo said:
only happens for me when i'm too far away from phone... BUT is there no way to disable this annoying vibration on disconnect?
setting in developer settings isn't functional.
if anyone finds out how to disable this PLEASE let me know
Click to expand...
Click to collapse
Settings - Connections - All the way down. I don't know what it's called in english. Alarm at dissconnect maybe?
caesium2 said:
Settings - Connections - All the way down. I don't know what it's called in english. Alarm at dissconnect maybe?
Click to expand...
Click to collapse
MADE MY WEEK!
thanks
Hey all. I've been trying to use the new Quick Launch gesture (in advanced settings within the Wear app on my phone). I'd really like to use the gesture to quickly activate the flashlight when needed. Unfortunately the triggering Quick Launch with the "knock knock" gesture is hit or miss (mostly miss). Are any of you able to use this successfully and reliably? And, if so, do you have any suggestions or tips on how to consistently execute it? Thanks.
It says that you have to do it within 5 seconds of waking up the screen, maybe it's because of that? I can get it to work almost everytime
dumbdeniz said:
It says that you have to do it within 5 seconds of waking up the screen, maybe it's because of that? I can get it to work almost everytime
Click to expand...
Click to collapse
I swear I had been keeping that in mind every time and it just wasn't working consistently for me. Just turned it back on and tried again and now it seems to be working every time without fail. Thanks
It will only work right after you're screen turns on (within 5 seconds). It's useful if you need to launch something quick hands free. Best to use directly after your screen turns on from a lift to wake gesture.
It works from time to time for me. I have noticed it does not want to work especially when the battery is below 40%. I need to restart the watch and it starts working again. I also tried turning it off and then on again to see if this helps, but it did not.
I need some advice on troubleshooting this one.
Brand new P7P, turned on Tap to Wake and "Always show time and info" on the lockscreen. It only ever works after a reboot *before* I log in the first time. Once I log in,that's it,screen is black when I lock it and it won't tap to wake.
I've removed the screen protector in case it was messing with the proximity sensor. I ran the phone in safemode and both *do* work in safemode,so I suspect it's an app on startup causing this.
What I need help with is how can I whittle down the culprit without removing all the apps one by one? Is there an app that will allow me to stop apps starting up at boot time and add them one by one?
dunetails said:
I need some advice on troubleshooting this one.
Brand new P7P, turned on Tap to Wake and "Always show time and info" on the lockscreen. It only ever works after a reboot *before* I log in the first time. Once I log in,that's it,screen is black when I lock it and it won't tap to wake.
I've removed the screen protector in case it was messing with the proximity sensor. I ran the phone in safemode and both *do* work in safemode,so I suspect it's an app on startup causing this.
What I need help with is how can I whittle down the culprit without removing all the apps one by one? Is there an app that will allow me to stop apps starting up at boot time and add them one by one?
Click to expand...
Click to collapse
@zetsumeikuro wait,I don't get what's so funny?
Mine works on every part of my lock screen.
Any chance you're using lift to wake? Besides that, I have everything else on the same as you.
Edit: Just reread your post. Do you have a lot of apps? You could force stop every single one of them and test to see what happens to be sure that it's an app.
Curiousn00b said:
Mine works on every part of my lock screen.
Any chance you're using lift to wake? Besides that, I have everything else on the same as you.
Edit: Just reread your post. Do you have a lot of apps? You could force stop every single one of them and test to see what happens to be sure that it's an app.
Click to expand...
Click to collapse
Yeah I have quite a few,but I think I'd rather try this first than start uninstalling and reinstalling the lot.
Not fixed,but getting somewhere. This is related to Bluetooth in some way.
If I turn off Bluetooth and reboot the phone,AOD works. I unlock the phone,it still works.
If I turn on Bluetooth AOD immediately breaks again until I turn off Bluetooth AND reboot.
I thought it might be my fitness band so disconnected and uninstalled the app, but the problem persisted. I have no other devices permanently using Bluetooth, so I'm starting to think this is a Bluetooth bug rather than a specific app now
dunetails said:
Not fixed,but getting somewhere. This is related to Bluetooth in some way.
If I turn off Bluetooth and reboot the phone,AOD works. I unlock the phone,it still works.
If I turn on Bluetooth AOD immediately breaks again until I turn off Bluetooth AND reboot.
I thought it might be my fitness band so disconnected and uninstalled the app, but the problem persisted. I have no other devices permanently using Bluetooth, so I'm starting to think this is a Bluetooth bug rather than a specific app now
Click to expand...
Click to collapse
If the fitness band allows you to take pictures remotely, it is possible that it recognizes it as a keyboard and that this interferes due to some bugs
PaulBW said:
If the fitness band allows you to take pictures remotely, it is possible that it recognizes it as a keyboard and that this interferes due to some bugs
Click to expand...
Click to collapse
Good point. This is why I tried to uninstall the app and disconnect the fitness band entirely,just to rule it out. Unfortunately,even once uninstalled,after a reboot with BT off AOD worked,but the moment I turned BT on AOD broke.
I can't think of any other apps using the BT at the moment but having a think. Will post more info if/when I get it.
Finally figured it out thanks to the hint by LaNy_6. This *is* down to Android Auto, but it’s not immediately obvious how or why.
To fix I went to Settings > Apps
Select See All Apps
From the top right overflow menu select Show System
Scroll Down to Android System
Select Notifications
Ensure Car Mode is selected
When I did this, I saw LaNy_6’s screenshot for the Android System notification that says “Driving App is running – tap to exit driving app” in my notification shade.
After doing this, AOD/tap to wake/lift to wake all suddenly work as expected.
Please note that upon rebooting the Driving App notification shows again and you have to tap it to go away. Again,no idea why.
I have no idea why, but I’m guessing every reboot the phone was put in to driving mode. I have never connected it to a car, there’s no reason for this to happen, but because I didn’t see the notification it never got exited from it seems. There’s no other indicators that it’s in driving mode, the phone works as normal other than the AOD problem.