Hello fellows,
I have a problem with my TomTom 7, Whenevr I start TomTom it always start "MUTE", I know it's just a couple of clicks to un-mute it but this little problem is bugging me since I have installed it.
Any help would be appreciated.
Regards
Sid
I had this problem too, I fixed it by adjusting the TomTom volume while it was muted, then I unmuted it and exited the application. I think I played around with the Diamond volume buttons at the same time. I restarted and it was all good. Sorry I can't be more specific, I just wanted to let you know that it can be fixed....
Just out of interest, do you have a bluetooth car kit that you are using as well? Because I suspected mine might have had something to do with it.
I have this problem too!
Anyone said, that TomTom start with Mute, when a Data Connection (Bluetooth etc.) ist on!?
Actually it's also happening to me again, just tried it out. Couldn't seem to 'fix' it again, tried so many different ROMS maybe one ROM had the problem, maybe another didn't. Will have to look into it some more!
I've had the same issue with TT6 on both my Hermes device and now the Diamond. I reckon the last used settings are not getting saved somehow.
Related
Hi dudes,
My problem seems similar to Obstler's issue in this thread: http://forum.xda-developers.com/viewtopic.php?t=35378&highlight=sound+problem
The problem: I can no longer hear any sound no matter what I do:
- clicking progs used to generate sounds. But no more...
- playing sound files just gives me silence
- a phone call generates a vibration as usual, but no more sound
- and when I pick up, I cannot hear the caller's voice
I tried:
- switching on/off bluetooth and speakerhone
- fiddling around with sound settings
- ending all active programs
Nothing seems to help.
My QTEK 9100 is one month old, has EXTrom 1.6.7.101 and is pretty much default (except for one lousy mahjongg game, but this one isn't the cause as it's been on for 2 weeks now.)
What I haven't tried yet; a soft reset. (I lack the doc here at the office but I think I need to do an ActiveSync at home first before resetting as I might lose some data right?)
Anyone had this? Anyone know what to do?
I'm quite new to PDA so I admit I wouldn't even know how to upgrade the bloody thing.
Had the same problem..
Try using your headphone plug, and plug it in several times(not to rough)
Sometimes the connection stays stuck in headphone....
It worked for me!!
p50kombi said:
Had the same problem..
Try using your headphone plug, and plug it in several times(not to rough)
Sometimes the connection stays stuck in headphone....
It worked for me!!
Click to expand...
Click to collapse
Strange... I never used that headphone. up to now.
Will try at home tonight. Thanks!
Found it! Switched on bluetooth.
Clicked the "connect" button on my Jabra headset. Et voila! :lol:
I have had the update 5.21 installed on my MDA Compact II for a couple of months. It works fine and is great. But lately something seems to make my ringtone go off. If i have tomtom open it does not work and if i close tomtom it does not work still. I try uninstalling everything and nothing works. I end up having to hard reset my whole device to get it working.
Anybody got any advice, not to sure if this is caused by the tomtom application.
Please! Help!
Tomtom controls the volume of other programs on the phone. It used lo be an option in the old Tomtom but no longer. If you turn down the volume on Tom-tom, it turns the master volume of the phone down. Check that you are not Muting the sound on Tomom. Also check you have a proper voice installed on TomTom.
The volume on my phone and TomTom are fine. It all works 100% for a few weeks and then all of a sudden only the tone which you hear when somebody is phoning you does not work. So if i have it on vibrate/ring then it only vibrates. This happens when i'm in TomTom and when i'm just using my phone as normal.
Now if i hard reset the phone to clear all programs it goes back to normal and works 100%. This is why i can only assume it is the TomTom 5.21 update and i have previously seen a few posts on here with people having the same issue. But i'm just not able to find it.
First of all, have you installed the A2DP patch? This patch usually causes a problem.
Try it with your headphones and see if you can hear it ring while using TT. There was a post not so long ago and a guy discovered that somthing got stuck in the headphone jack.
Not to sure what the A2DP patch is so i can only assume i have not installed it.
I will try the headphone socket, but not really wanting to walk around with headphones on all day and while i'm in the car. But thanks for the advice.
I've searched a bit, and can't find a solution to the problem I'm experiencing. When I got the phone last week, it discovered and paired with my bluetooth earpiece without issue. Now it won't even detect the bluetooth device?
I did install: Closeall, omapclock, smartskey, and lokiwiz unlocker. Sometime during or after, bluetooth stopped working correctly. Are there any known conflicts between the above applications and bluetooth? fyi- I did try my earpiece with another phone, and it works fine.
I should mention that I inadvertently deleted a file called "ssdaemon" (or something close to it) from the startup menu, during the smartskey install. I performed a hard reset and the file returned. Bluetooth still does not work after the hard reset and several soft resets. I've also tried playing with the blutooth settings to no avail. How do I resolve this issue?
Between this issue and that damn speakerphone being stuck on while using a regular earbud style earpiece this buggy ass phone is pissing me off! The freaking speakerphone stays on, and I can't get it off unless I perform a reset. :evil:
This is really annoying because I'm hearing impaired and rely on either a special blutooth device or a hearing aid adaptor (I can't use a cell phone in the normal fashion, all I hear is static). These two problems currently render the device useless to me.
I think that loading a different rom or waiting for cingular's update will help, but I'm not sure. Any help on either of these issues is much appreciated. Thank You!
Nick
No ideas or advice?
I think it's TomTom doing it.. I tested today, putting the phone on vibrate via the # key, then starting & exiting tomtom, then enabling sound using the # key.
I checked the sound by clicking on the speaker icon.. and lo & behold the phone's ringer volume was set at zero (whilst the earpiece volume is as i want it) - and I know it wasn't before my test. And to add to that, other events such as SMSs are perfectly audible. It's just the ringer itself.
Any idea if it's tomtom or something else? what can i do to stop this, as it's happening a fair bit & i miss calls...
Cheers
Rob
This happened to me as well on my Polaris. I don't know if TomTom is the reason but I will test this theory. I thought it was because I used the HTC profile tab to put the unit on vibrate, but come to think of it...the day this happened, I used TomTom. I'll have to get back to you....
luckycris0 said:
This happened to me as well on my Polaris. I don't know if TomTom is the reason but I will test this theory. I thought it was because I used the HTC profile tab to put the unit on vibrate, but come to think of it...the day this happened, I used TomTom. I'll have to get back to you....
Click to expand...
Click to collapse
thanks mate
tbh, is there software better than tom tom out there too? It is good, very good, but if anything I'd like a bit more screen detail! Have memory map for ordnance survey maps for walking, but a more detailed in-car nav would be nice.
I upgraded my XV6800 to 6.1 using the official upgrade. It's giving me trouble answering calls. When a call comes in I see the notification but when I try to press the Green phone button or the left soft button labeled 'Answer' it doesn't do it! It's like the keys are slow or something. When I use the soft button is DOES flash the soft button label like it recognized the button press. But it does not answer the call! I've had this happen at least a dozen times now so I know it's not just me fumbling with the keys. 9 times of of 10 I can't answer a call!
I've tried hard resetting the device and the symptom persists. I've tried using it without the microSD card loaded. Still the same trouble.
Has anyone else seen this? Or can you recommend a solution?
so your saying it doesn't show "connected"?
I had something similar to what your describing but it would show as "connected" on my phone. I couldn't hear anything when I'd answer. I realized after several attempts it was that the phone was paired to my cars bluetooth... I was trying to dial my phone as I was walking away from my car but I was still within 30 ft of the car... so all speaker and microphone was still being redirected to the cars system. lol. Same can happen with a bluetooth headset where the conversation (speaker/mic) is redirected to the headset that may be in your pocket or on the kitchen counter. But it would at least show as "connected" on the phone.
I feel stupid/foolish for shareing that experience but figured just maybe its what your experiencing.
Thanks,
Ben
*edit: by the way... when I had the 6.1 vzw upgrade I had no problem placeing and receiving calls, with the exception of the "user error" I described above. You could always try rolling back to 6.0 and upgrade again. Did you install any other new software after the upgrade to 6.1?
I have been experiencing something similar. PPC 6800 (not Verizon) with 6.0. When phone is locked and call comes in, can’t answer with the button or with BT. 6800 keeps ringing long after caller goes to voice mail. The only way to escape is soft reset. I’m running the original ROM & Radio that came with the 6800.
ygohome said:
so your saying it doesn't show "connected"?
I had something similar to what your describing but it would show as "connected" on my phone. I couldn't hear anything when I'd answer. I realized after several attempts it was that the phone was paired to my cars bluetooth... I was trying to dial my phone as I was walking away from my car but I was still within 30 ft of the car... so all speaker and microphone was still being redirected to the cars system. lol. Same can happen with a bluetooth headset where the conversation (speaker/mic) is redirected to the headset that may be in your pocket or on the kitchen counter. But it would at least show as "connected" on the phone.
Click to expand...
Click to collapse
Nope, never shows connected. It's like the UI has gotten hung somewhere and isn't passing control over to the phone app.
No bluetooth pairings have ever been done to this phone, not before the upgrade and certainly none since. BT isn't even enabled.
Tim may be on to something regarding the lock situation. I've found the lock method a lot less friendly than before 6.1. Can't quite pin it down but it just doesn't seem to unlock properly. Again, it seems to be related to something making the phone 'slow'. On-screen keypresses in the Lock app don't seem to register with the same speed as before 6.1. I can tap a couple of them and not see anything on the screen, then they all run through (showing the screen buttons getting pressed).
My Xv6800 Verizon Does The Same Thing. I Push The Green Hard Button To Answer And It Takes Like 5 Seconds To Answer. It Seems To Happen More When I Have Programs Like Internet Explorer Up, But There Is Still Plenty Of Memory So I Cant See Why It Would Be So Slow. Its Just Frustrating Because Sometimes It Takes So Long The Call Goes To Voicemail And Nobody (fiancee Included) Believes Me! Any Help From Anyone?
fyi... i use an auto close program so when I close an application it really closes. I don't have the slow response or ability to not answer within 5 secs, etc. maybe it is a low memory issue you are experiencing. I don't lock my phone so that may be it too. Sorry I'm not much help here.
ygohome said:
fyi... i use an auto close program so when I close an application it really closes. I don't have the slow response or ability to not answer within 5 secs, etc. maybe it is a low memory issue you are experiencing. I don't lock my phone so that may be it too. Sorry I'm not much help here.
Click to expand...
Click to collapse
No, it's definitely not a low memory issue. It's doing this fresh after a reboot having had no other apps even started.