Related
I am looking for users with problems using the MS Voice Command on the T-Mobile Wing/Herald and their fixes or commments.
I have been using WM devices and MS Voice Command for many years. I have had a variety of devices all using voice command; but none have been worse at recognition and speed as my Wing has. How does everyone else with a wing feel about MS Voice Commands performance.
Problems I experience:
Slow response to initialization (1-2 seconds usually)
Slow finding a contact and confirming (2-4 seconds)
Most times with some background noise just gives up and makes that aweful beep.
Always asks to Please try again
Will not understand through bluetooth headset at all.
Commonly mistakes simple names for others i.e. (John Patrick)
Now the voice command can work pretty accuratly in a queit room other than the responsiveness, but I have had it installed on numerous devices and know how it should opperate and the tolerance to noise. I have overclocked my CPU to 273 and doesnt seem to help. I have tried increasing the page pool to 4mb which I have 23mbs for memory and still no luck. Ive even tried the combination of the two but doesnt seem to help. No other progams have been installed for test purposes to see if there is any conflicts and I have about 73 contacts, and sync very little content.
My previous device was a Wizard which respectively is very simular. It did work good with voice command 1.6 both on WM5 & WM6. I have had it installed on a Audiovox PPC4400 (WM2003), Treo 700wx, Blue Angel (WM5), and a Hermes (WM6); all the later devices worked best with no noticable delay or comprehension issues. The Herald will work with the same bluetooth equipment almost flawlessly, the wing will initiate the command but always fail to understand or will pull up something else.
I would like to know if I'm and isolated instance or if everyone has this problem.
Thanks
Jcostanza4
Works fine for me! However, I do speak in a Robotic tone.
Naw, I cant get that thing to do what I tell it.
YES!!!! MS Voice Command on the Wing is almost unusable for me. On my Wizard it was amazing -- fast and accurate. On the Wing frustrating, maddening and worthless.
I have experimented with standard versus overclocking, mic gain settings... everything I can think of. It seems to be a little bit better if I have Bluetooth turned off -- but just a little bit.
I have been reading these forums since the Wing was released and have been surprised that others have not commented on the problems with MS Voice Command on the Wing.
I sure wish there was an answer. Does anyone know what the problem is?
I agree with you, I dont know why more people haven't brought it up.
This is one of the biggest downfalls of the Wing for me. I love everything else even speed when overclocked and the page pool make it quite fast. But I just disable voice command completly because it is so unrelaible. I think it would more likely be along the lines of a hardware compatibility issue that the software would have to overcome or a fix in the OS; but I really dont know.
I wonder if the Herald guys get this problem or if its just an issue with the Wing OS.
Time will tell.
Jcostanza4-
It seems like it's just the crappy microphone on the bottom. It picks up EVERY noise around you and that confuses the voice command. I've noticed that if I use the wired headset that came with my wing it's almost always accurate.
Take a voice note in a semi-noisy environment and you'll see what I'm talking about. It definitely is not a noise canceling microphone.
Well... I can confirm that the audio quality of a voice note is clearly superior on my Wizard than on the Wing... considering that other people do not seem to be up-in-arms about MS Voice Command, I am coming to the conclusion that the microphone on the Wing is at fault.
Has anyone had problems reported with phone calls
Ive asked people if I sound faint or hard to hear and they say it sounds fine/normal. Also bluetooth mics also seem to have the same problems with comprehension when other Window Mobile devices with the same hardware work like they should. Ive tested the Hermes with WM6 on the same bluetooth car kit with MS VoiceCommand over bluetooth and no problems; I know certain bluetooth with VC works and some dont, the Wing seems to operate just like the hermes as far as initiation. This would bypass the poor mic theory on the Wing right?
jcostanza4 said:
Ive asked people if I sound faint or hard to hear and they say it sounds fine/normal. Also bluetooth mics also seem to have the same problems with comprehension when other Window Mobile devices with the same hardware work like they should. Ive tested the Hermes with WM6 on the same bluetooth car kit with MS VoiceCommand over bluetooth and no problems; I know certain bluetooth with VC works and some dont, the Wing seems to operate just like the hermes as far as initiation. This would bypass the poor mic theory on the Wing right?
Click to expand...
Click to collapse
I haven't used a bluetooth headset before on my wing but my wired headset works flawlessly almost every time. It could be that the bluetooth connection wasn't as strong or something (biased towards the wing not working when testing?). I still believe it's the microphone but I could be wrong
I havent really had too much problem with it, I'm using the PDAVIET rom and had to reinstall voice command once i had the rom, and it seems to work fine. Have you tweaked the mic gain?
Tweaking th mic gain.
dcmtnbkr said:
I havent really had too much problem with it, I'm using the PDAVIET rom and had to reinstall voice command once i had the rom, and it seems to work fine. Have you tweaked the mic gain?
Click to expand...
Click to collapse
Is your device a wing or a herald?
Im still using the stock T-Mobile Rom on the wing and Ive enable and disable the mic gain; shows no improvement that I can tell. Now the Wing comes pre installed with Voice Command and does not have a remove from the Uninstall Program options. I did once try to install 1.6 over it to see if i could get back the remove option and when I clicked reset to finish after installing it hard reset on me.
On your PDAVIET rom, does the vioce command launch instantly, respond quickly, and understand you to some degree or is there some trouble in any of these areas?
Thanks for the info
jcostanza4
me, too - very disappointing indeed
Yes, I just got the Wing a couple of days ago after giving my wonderful Imate Jam one too many love taps (the touchscreen has stopped accepting any input)...and I'm experiencing exactly the symptoms you listed with VoiceCommand. It actually does seem to do a little better through the BT headset, so the "poor mike" theory might be on the right track. But without the BT, it can't understand a damn thing--even in perfectly quiet environments--and takes forever.
I've been using the Jam with VC for over two years, and it is fast and damn-near flawless. Indeed, I've been a huge VC zealot; 'never been able to understand why WM-device reviewers don't even mention it but instead say things like "it's too hard to dial calls one-handed when driving." And for years already, while the best that other devices could offer was "voice tags" that users had to manually create, VC has, as you know, seamlessly worked with all my ~500 Outlook contacts. As far as I'm concerned, VC is the killer app that provides a huge part of the value of WM devices. If you ask me for the phone number of any of my friends, family or business clients, I couldn't tell you, 'cuz I haven't dialed them in years.
Now comes the Wing to set progress back five years or so. I have 12 days to make a decision about returning it.
mtn_lion said:
Yes, I just got the Wing a couple of days ago after giving my wonderful Imate Jam one too many love taps (the touchscreen has stopped accepting any input)...and I'm experiencing exactly the symptoms you listed with VoiceCommand. It actually does seem to do a little better through the BT headset, so the "poor mike" theory might be on the right track. But without the BT, it can't understand a damn thing--even in perfectly quiet environments--and takes forever.
I've been using the Jam with VC for over two years, and it is fast and damn-near flawless. Indeed, I've been a huge VC zealot; 'never been able to understand why WM-device reviewers don't even mention it but instead say things like "it's too hard to dial calls one-handed when driving." And for years already, while the best that other devices could offer was "voice tags" that users had to manually create, VC has, as you know, seamlessly worked with all my ~500 Outlook contacts. As far as I'm concerned, VC is the killer app that provides a huge part of the value of WM devices. If you ask me for the phone number of any of my friends, family or business clients, I couldn't tell you, 'cuz I haven't dialed them in years.
Now comes the Wing to set progress back five years or so. I have 12 days to make a decision about returning it.
Click to expand...
Click to collapse
I made all of my contacts store with first name, last name format and the recognition appeared to get a lot better. You shouldn't have to do that but it seemed to help so you could try it. I am temporarily trying the wing overclocked to 273mhz with a boost up to 286mhz and in a quiet environment I haven't had a problem with the voice recognition finding my contacts. I still have trouble with the "play" command and it's VERY difficult for it to understand my "yes" for some reason but contact recognition is good and speedy.
The yes response or correct doesnt pick up well for me either
I did notice this too, but I always forget that thats one of my biggest problems with dailing by name or number. Let's say its a bad mic, even with a headset wired/wireless does it seem to lag in speedy ness or accuracy?
I did mess with page pool on the Wing, I ran 4mb for about 2 months then moved to a 6mb and the device is overall faster than the 4mb or 12mb. The 6mb page pool defenitly responds quick when it can understand you; but 70% of the time it can understand and gives that very long pause before saying "please repeat". It does seam like voice command when enabled eats about 5mb or ram. I have 22.5mb on a soft reset and after using voice comand once it drops to 13mb and then goes to 17mb after about 3 minutes of no use.
I have not read anything from the Hermes users to show that they are having these issues. Could it be an OS problem that translates the mic to the program?
Jcostanza-
kraftey--Thanks for the suggestion, which makes sense, I guess...but I'm not willing to organized my contacts by first name, period. Call me a neo-traditionalist.
As I've posted in the overclocking thread, I can't get my Wing above 228 without the screen flickering.... Ideas?
jcostanza4--Thanks, too. Honestly, in a *perfectly* quiet environment, recognition is not bad, and using either BT headset or not, time from command to response is 5-7 seconds. That doesn't sound like much, but in actual use at work it's an eternity--and made much worse by all of the "Please Repeat"s, additional delays and/or failures.
I've got the pagepool set to 6MB, and I've mucked about with performance-related registry tweaks, but the 5-7 seconds and poor recognition in real-world environments is the best I've been able to get out of VC so far.
Im overclocking the Wing with Battery Status Ver. 1.04.203
I have the device set on dynamic mode so its 201Mhz on minimal load and 273Mhz on Max Load. Battery can last quite a while like this and I havent had screen issues. I hope this helps. I had issues with some other overclocking apps, and eventually tried this one and it worked. No complaints and Ive been using it for about 4 months.
Yes. The darn thing is frustrating. This was supposed to be top of the line. I paid around $250 for the PDA and I paid $100 for a top of the line bluetooth, and the voice mail keeps trying to call my Brother Jeff, regardless of what I say. I paid $140 for a Jawbone, and got the same poor performance. Just how much do I have to pay to get something that works.
Yes, jc, that helps. I had already moved to BS, but now I'll update it with the 1.04 beta. For starters, what OmapClock was calling "228", BS calls "247." With the "released" version of BS, I still get the screen flicker above "247." We'll see if it's any different after I install the beta. Thx.
I solved my Voice Command Problems!
I originally posted all the issues I was having with Voice Command 1.6 on my T-mobile Wing. I now have a working Voice Command to my standards, it works as it has on all my other devices; a little slow at times but not more than a second lag. Recognition is accurate and mic also seems to work better.
Here is the steps I used. (this was completely accidental, as I was trying to get TouchFlo working on the Wing)
I reflashed the T-Mobile Wing RUU found in the Herald wiki section or this thread http://forum.xda-developers.com/showthread.php?t=321717
Then Flashed the Original T-Mobile Rom with Touch Flow found here http://forum.xda-developers.com/showthread.php?t=329456
Then I Ran the Automatic 6mb page pool found here http://forum.xda-developers.com/showthread.php?t=324955
Then I installed Battery Status and overclocked my Wing to 273mhz.
I dont know if the RUU that was released was an update to the original rom, but my mic seems to work great now and recognize with about a 90% accuracy rate.
Please try this at your own risk, This may work for me and may not work for you. By all means I am no programer nor can I assist in a sticky situation.
I suggest reading each of the other threads I have listed before attempting. I will not be responsible if you brick your device. There is alot of information in each thread that is not posted on the first Topic like using ASerg Policies or how the page pool works or common problems.
Thanks-
Jcostanza4
Start > Settings > System > Microphone AGC
I don't use voice dial because I had all the same probs as the original poster. May want to give this a try before all of the steps mentioned in the post before me
for me it is working fine most of the time but not as good as it did with my wizard it is not slow and recognizes commands most of the time, I am using the pdaviet rom build 12 I changed the page pool to 4mb and clocked to 260 with bs , my problem though is that I can't get voice command to work by pressing the bluetooth headset button wich works fine on the wizard.
I bought a Kaiser a few months ago, and I've been pretty disappointed to be honest.
I sold my old Mio A701 (WM5) which never gave me any problems... big mistake.
I have a few issues with the Kaiser, two of them are very frustrating.
1. During a call, the microphone volume drops completely so the caller cannot hear me... although I can hear them perfectly. Done numerous microphone tests with voice recorders etc and it only does it during a call. It's not a signal problem either, as I get a full signal in the office. HTC tell me they've come across this issue before, but they can't remember how to fix it. This is a £330 device, touted to be one of the best on the market... if this isn't resolved soon, the whole thing will end up on the front carpark in pieces.
2. Pairing with Parrot 3100 (running 4.16d) is completely unusable. I have complained to HTC & Parrot several times but I'm simply told to wait as they're doing everything they can to resolve the issue. Parrot are quick to tell you "we have a great relationship with HTC so it shouldn't be much longer" but it's been months!!! I'm not sure if it's a problem with the phone or the headset, but it's still not good enough.
Ghost calls (Parrot says "Call....." and takes control of the stereo (it's a Saab 9-3SS with ISO) but the phone isn't dialing anyone. I can only regain control of the stereo by stopping and removing the key... leaving the Parrot to ask "do you want to transfer the call to handset?" WHAT CALL?
Incoming/Outgoing calls sometimes aren't diverted through the Parrot.
3. WM6 seems considerably slower than WM5 for many common tasks. Is there any way to downgrade to WM5?
I've upgraded the firmware several times (now using Schaps) and it seems to be a bit quicker than before but it still suffers from the frustrating mic problem.
Any help would be much appreciated.
For me, the Kaiser is worth the money - I've been like a dog with 2 dicks since getting mine and apart from a few simple problems setting up TomTom I'm more than satisfied.
I was the same with my Wizards (Qtek and HTC) and Hermes (Vodafone). Maybe I'm more tolerant about problems, or more lucky not to get the rogue phones with hardware problems (software stuff can always be resolved) - but my experience of the HTC phones is that they're worth the £300+ upgrade every year.
That said, I haven't had my Kaiser too long yet so I may change my opinion.
I spent months and months researching my new purchase & I can tell you with 100% confidence that YES, IMO the Kaiser is worth the cost.
I chose to go with the HTC TyTN II over the Tilt because I just didn't want to deal with all the stuff AT&T did.
I knew about the driver issues, blue tooth issues etc etc etc and I am still convinced this is the best device for my needs.
It will only get better with time, and thanks to the tech geniuses that lead us in our quest here at XDA, I know many more great things are coming (and this is one of the reasons I donate to the community and support the driver Bounty ).
Nothing in this world is perfect & with that being said I have found that almost every issue has a good workaround. Sometimes that might mean using different hardware or software than we are accustomed to.
IMHO, even with the issues we face this is the best device out there and has so many possibilities for customization.
I love mine and have enjoyed learning about it and what I can do to improve the quality and efficiency of my life, even though i do get impatient
what have you done about your crippled GPS? flash a few radios and then bare with the horrible fix times, or have you actually found a way to fix this? I wanna know how many people on this forum put up with crippled GPS.
I personally chose the option of putting up with the crippled GPS, ive tried to fix it but haven't found anything. Assisted GPS freezes so i have to leave it turned off. Today when i actually needed it and realized it took more than 5 minutes to get a fix, that really annoyed me..
not sure how i rank with those 2 options but i just keep my quickgps updated and then run GPStest get a fix before then start igo8 and fix time havent been too bad...been using the radio in my sig
edit: i have agps turned off via advancedconfig
bapssystupr3m3 said:
not sure how i rank with those 2 options but i just keep my quickgps updated and then run GPStest get a fix before then start igo8 and fix time havent been too bad...been using the radio in my sig
edit: i have agps turned off via advancedconfig
Click to expand...
Click to collapse
hm...but even then that would be considered "crippled" gps. you still need to jump through hoops just to get it to work right. and you have to have the right radio...i remember when there was no wm6.1, no matter what i would flash to, i never had to switch radios, my gps just connected instantly. no jumping through hoops.
i would say your option is that you "put up with your crippled GPS" but that is just my opinion.
One of the lucky guys i guess... No problems with GPS after the 6.1 update. I use a stock ROM and Radio (in my sig) and i use Destinator 7 for GPS. Takes me about 2 mins to get a fix and GPS runs smoothly. QuickGPS get updated when i connect via USB...
dont use GPS on my TYTN II, i have a standard Kaiser for that
Well
My GPS is going fine from the start till now. I've flashed many roms and many many radios. My GPS was working everytime with various things. I get a fix in 1-2 minutes. 3 is really max awaiting time. I'm using A-GPS without any problems.
ROM&Radio as in my signature.
Cheers,
Chris
Hey guys, 1-2 or 3 minutes is not considered as quick gps fix Have in mind that gps fix was about 15-20 seconds in WM6 roms
zalaros said:
Hey guys, 1-2 or 3 minutes is not considered as quick gps fix Have in mind that gps fix was about 15-20 seconds in WM6 roms
Click to expand...
Click to collapse
I must try it today once again after soft reset, and i will post my results as i get back to home. But its quite good for me.
I get a fix in about 90 seconds using TomTom or iNav. But if I use GPS Test, then the fix time drops to like 30 seconds.
I'm currently running Death v4.1 and the 1.58.25.27 Niki radio.
alright, ive made the test.
42 seconds in GPSTest, 59 in my AutoMap5 and 62 in GarminMobileXt. posting from Kaiser outdoors.
Cheers,
Chris
Rom: Hyperdragon IIIs
Radio: 1.65.20.29
QuickGPS regularly updates
AGPS turned on
GPSTest fixes in about 30 seconds
Tomtom 7 fixes in about 45 seconds; instant if GPSTest was started first
so... no, I don't feel my gps is crippled at all.
If 'attempted to fix it' includes emailing HTC (and only getting the automated response saying they received the message) and phoning HTC twice about it, I guess I fit into the second group. I've not strayed from HTC supplied firmware at any stage and don't want to. It's their responsibility to fix it, not mine and if they can't they should get Qualcom to update the chipset drivers/radio for them to fix it.
I wasn't happy with my sync time in 6.1 with the radio that I had (i.64.xx.xx) and i just flashed 1.58.25.17 on my phone and it synced in 1:30-2 mins fro ma cold start outside (needed a reason to walk away from the cube). good enough for me.
Mass/AT&T/Death 4.1
2-3 minutes doesnt seem like a good time to me...especially when there was once a time it could get a fix within 5-25 seconds.
I have heard good things about the stock roms, and i ALMOST upgraded to it, but then i remember they aren't as fast as some of our cooked roms here on the forum, and the fact that stock roms are loaded with a bunch of crap and have less memory.
I'm gonna knock on wood before and after I type this:
*knock on wood*
Since using Tomtom v7 extracted from Diamond, my Tilt has not disappointed me with initial GPS fix.
*knock on wood*
the problems people are experiencing and the seeming lack of issues for other people with the same ROMS must have something to do with the Kaiser variants people are using. I can think of no other reason why I can have the same ROM, radio and SPL as someone else and yet cannot get a fix, while they can. I have an Orange branded TyTn 2 from the UK. I am currently using the Dutty Diamond V1, hard spl 3.29 and the 1.65 radio that comes with the diamond ROM. I believe my Kaiser model number is KAI130. Does anyone else have the same model and ROM etc as me and is able to get a fix?
Ive tried 5 different ROMs and umpteen radio, disabling and enabling A-gps - even installing different quick GPS cabs. No luck.
I never had any problems like this on my N95, and everyone criticise its GPS!
hi,
i use now last updated htc rom in french (wm6.1) with tomtom 6.0 and quickgps V1.0 from htc.
Effectively, it takes now more time (1..3 minutes) than before (few seconds, under wm6.0) to get a fix, but it works has before.
Seem that the fix takes now much more time...
May be you are right, wm6.1 has somthing to do wuth t is problem.
Best regards,
Laurent
McGuider GPS
This program picks up signal in under 15 secs
leoni1980 said:
the problems people are experiencing and the seeming lack of issues for other people with the same ROMS must have something to do with the Kaiser variants people are using. I can think of no other reason why I can have the same ROM, radio and SPL as someone else and yet cannot get a fix, while they can. I have an Orange branded TyTn 2 from the UK. I am currently using the Dutty Diamond V1, hard spl 3.29 and the 1.65 radio that comes with the diamond ROM. I believe my Kaiser model number is KAI130. Does anyone else have the same model and ROM etc as me and is able to get a fix?
Ive tried 5 different ROMs and umpteen radio, disabling and enabling A-gps - even installing different quick GPS cabs. No luck.
I never had any problems like this on my N95, and everyone criticise its GPS!
Click to expand...
Click to collapse
I have an AT&T Tilt, I live in the US.
I'm using Radio 1.64.06.04
Im using Dutty's WM6.1 4/29 Rom
I have the Qualcomm 7200 chip (not 7201)
My Kaiser's Model Number is KAIS160.
Now that i think about it, i cant confirm this kaiser ever had a good GPS fix, being that this is my 2nd kaiser, my first one broke, and this one is the free replacement. hm...
The poll results are really surprising me, at least half the people's GPS is fine for them. I would upgrade to anything newer than dutty's 4/29 but most diamond builds dont support direct draw, i cant play quake, quake 2, or duke nukem. most other games or apps that use direct draw don't work either. i still have to try hyperdragon 6/24 build and L26_Kaiser Diamond 6/25. Does anyone know if GPS AND direct draw are working on these roms?
Indeed I miss the fast fixes from 6.0 ROMs. Within 20 seconds I would already have a fix from a cold start. Now it takes up to 3 minutes, its reaaally annoying. In fact, I also found it strange that half of the people here were not complaining about their GPS's. More than once I needed those fast fixes and had to wait for 2 minutes or so, and had to stop at dangerous eek:) places waiting for it. I tried different solutions but none of them seemed to work. And I really don't feel like going back to 6.0 ROMs so..
i have the original rom (1.35.401 ) and radio (0.93.25) and igo 8 installed and i have a big gps lag (5 sec). Is it a problem of igo 8 or rom/radio? If i flash a newer versions it will help? Slould be a cooked one or original is enough?
This GPS lag problem has not yet been resolved by anyone. Let's hope some rom cooker are able to resolve this lag problem. There are apparantly many people sufferring from this
Hi guys,
You probably used ACT and enabled A-GPS.
You should disabled it.
MonteCristoffOn said:
Hi guys,
You probably used ACT and enabled A-GPS.
You should disabled it.
Click to expand...
Click to collapse
Nope, thats not the issue.
A-GPS is disabled.
In my opinion the issue is generated by the interval between 2 consecutive positioning readings. It seems that somehow, the application doesn't receive data's from GPS fast enough and because of that, between 2 consecutive readings, you allready made 20-30 meters - enough to miss a crossroad . For example, because i also have a builtin car GPS, it seems that the IGO is allways ~20-50 meters (depending of speed) behind the builtin car gps
There are 3 options which can generate this issue:
1. IGO himself
2. Windows driver
3. GPS HW
For 1st option - i will try with a bluetooth GPS. Unfortunatelly i don't have one. Maybe somebody can try and let me know if the lag is the same?
Also if somebody can try tomtom (there are no available maps where i live) and let us know if still has that lag
For 2nd options - There is an option in registry called POLL interval which is by default 1000. I will try to set it to 300 to see if there is any difference. If is not maybe the dll has something hardcoded about polling interval
For 3rd option maybe with another Radio version the problem can be solved
Please let me know if somebody allready tried some of the options or have another ideeas
Hi there, I have GPS in my Parrot hands-free and it has the same lag as the bulit in GPS.
Seems strange that the Parrot has 2 times stronger signal (and about 2 sattelistes more) than Diamond And it even has not SIRF III chip!
So it is not 1)
Using TTN 7.45 and no lag
tehac said:
Hi there, I have GPS in my Parrot hands-free and it has the same lag as the bulit in GPS.
Seems strange that the Parrot has 2 times stronger signal (and about 2 sattelistes more) than Diamond And it even has not SIRF III chip!
So it is not 1)
Click to expand...
Click to collapse
it's not 3) then - if you have the same lag can be related to IGO himself. So it remains 1) and 2)
possible solution?!?
I have / had the same Problem.
It could be possible, that several programs try to use the GPS-chip at the same time. In that case, it could be that windows switches the availability between these apps. At my Diamond this strange behaviour starts after taking some fotos. So infer from it, that the option of "GPS-Photo" could be the villain.
I switched it off with "advanced config" before one hour. And till now everything is ok. I hope it will last a while.
but on mine the GPS photo is allready disabled and it was never enabled
AGPS
Yes, i think i was wrong. Today in the morning i had the same problem, again. So i tried something else.
Disable the "Assisted GPS" seems to work. Since then i had no more problems today. Lets hold the thumbs!
i've tried another ROM and RADIO - the same issue
I can only say that you shouldn't expect no lags in GPS software. I was using a lot of standalone GPS devices like TomTom Go/One etc. and even they lag a bit even though they use SirfStar III chipset. You just have to get used to it. Of course, new ROMs may decrease the problem a bit, but don't expect it to disappear completely.
I used mine with an external gps receiver (Sirf III), via bluetooth, and no noticable lag was detetcted during more than 800km (from Bavaria to Paris)...
So, there is something wrong...
I just don't know what....
My next test, will be a clean install of the rom, and drive imediatly after. I wonder if any of the tweaks we apply have any direct or indirect interference with GPS ...
HastaSSSS
I am just saying what I can observe with other devices. I've got Go920 and my friend Go520 and we can both see a noticeable lag, the same with older tomtoms we got in our company. Of course it's much less noticeable than the one in TyTN II or Diamond, when I can clearly see that I've already passed the junction 200m ago and I'm still approaching it in my GPS soft.
I called HTC support Australia and informed them off its fault with GPS lag and its accuracy, I informed them that over 50% of users are having this issue on the XDA forum, they told me that no fault has been logged and there isn't an issue, It may be time to call up the tech support and make some noise to get this issue resolved. its a pain in the arse and it shouldn't be happening.
Maybe we should have a poll to get some hard stats on just how many people are experiencing this problem and add momentum to finding solution.
i just made a 1800 km trip and now i can say that in the city the lag of the GPS make it unusable
Maybe we can try to install igo2006 to see if there is any difference
I haven't had any lag problems at all, the only problem is the time it takes to initially get the satellite data.
Lag time iGO 8
I also experienced the lag time issue. However, it is really lag time as iGO8 seems consistently 20 m behind. Try to stop sufficiently long in an intersection and monitor what happens - my GPS wil slowly count down from about 25 m to about 20 m. In other words its consistently 20 m behind - the lag time is only equvivalent to some 5 m. One thing which seems to improve things is to alter the seting "re-establish lock-to-position" (translation from the Danish menu) and put it at 5 sec. Surely I have not experienced any such issue with my Blaupunkt and Mio A701 systems. And yes it makes it absolutely hopeless in bigger cities if you don't know the road.
I have been using TomTom7 on my diamond for almost a year. First several months it was working fine, just some lags or freezes on roundabouts, which was not a big issue.
Then it started doing this strange behaviour at some occasions: I start TomTom, it finds satellites fairly quickly, I start driving, all fine. Then after some distance it loses coordinates (you can see the blue arrow, but everything behind it is grey and it is not following the route). Sometimes it fixes itself for a short time, then does it again. Sometimes this is all, whatever you do (reroute, restart tomtom, restart phone) it won't come back. Some days none of this happens.
Nothing in configuration had changed, I've been using the same radio and rom for almost a year.
I was really annoyed by this, could not simply rely on tomtom. Now I updated the ROM, and yesterday this happened again
If this was discussed before, please point me in the right direction, most of the threads I found by search were about lags or configuration.
It might be the Quick GPS Programs, I recall having a simular problem where the GPS would work for about 5 minutes then turn off, only turning the phone off then on then running up tomtom again would get another fix, only for it to run for a further 5 mins or so.
I think I disabled the quick GPS in the registry using PHM registry editor or something simular.
It might be worth considering updating the ROM. I'm running BsB's which seems much better than the stock offerings.
I've also had this problem with the latest rom from HTC (regular rom) with the radio 1.09.XX
I've updated to radio 1.15 and the problem is gone.
Thanks for you replies.
I've now updated the radio to one of the latest (1.09.25.23), the ROM was already recent (2.07 Gen.Y). Will test it during the week.
The solution based around disabling of Quick GPS - wouldn' it make the start up time longer ?
gonx_me said:
I've updated to radio 1.15 ..
Click to expand...
Click to collapse
I have tried to install this radio, but got "Invalid Device Id" message, 1.09 installed with no problems. The phone is security unlocked, could not understand what was the issue and just moved on .. :-/
Could be error in timezone
Hi all,
I had a similar problem and it appears to be the timezone, by reasons unknown my Diamond was set to a timezone of Stockholm, now that looks ok, but it is not a normal timezone.
I changed it to Stockholm, Berlin, ... the standard timezone and once again I got a fix fast and easy.
The thing that you get a gray screen is that you our somewere in the middle of the earth according to the GPS, you notice this if you could see the coordinates and altitude.
I have iGo in my Diamond, but the problem was the same when using Google maps so it wasn't a problem with the program.
I have also changed my iGo to have a manually selected time zone, because I'm not sure if it might be iGo that made the change for me.
But now all my GPS works splendid, and I have a fix within 15 seconds.
i do have similar problems.. but it only happens when i'm in the dense core of downtown toronto where all the tall buildings are..
I think it's because the tall buildings are blocking the signal somewhat that is why your GPS kept on running out or coordinates and relocating itself again
bigbro168 said:
I think it's because the tall buildings are blocking the signal somewhat that is why your GPS kept on running out or coordinates and relocating itself again
Click to expand...
Click to collapse
I am in rural Scotland actually, the only high buildings here are castles which are miles away .. so this must be something different.
Neither it seems to be dependent on the sky nor battery level ...
p.s. testing new radio, so far so good ..
Just some feedback from testing: the original problem seems to be solved, but now I've got something much worse - sometimes TomTom freezes several second after the launch, and nothing can be done apart from restarting to bring it back. Don't know if this is a radio's or ROM's issue as I have changed both. Reinstalling TomTom from .cab did not help.
Anyone had similar experience ?
Just some feedback from testing: the original problem seems to be solved, but now I've got something much worse - sometimes TomTom freezes several second after the launch, and nothing can be done apart from restarting to bring it back. Don't know if this is a radio's or ROM's issue as I have changed both. Reinstalling TomTom from .cab did not help.
Anyone had similar experience ?
Hard reset maybe will help
Yes it may, but 3 days before holiday I do not want to be installing everything from scratch. I could try another ROM too if not this.
Tried - atifix, starting with bluetootsh on, wanted to reconfigure GPS setting in TomTom, but can't get there yet ... must be either BT or GPS connectivity
Yes it may, but 3 days before holiday I do not want to be installing everything from scratch. I could try another ROM too if not this.
Tried - atifix, starting with bluetootsh on, wanted to reconfigure GPS setting in TomTom, but can't get there yet ... must be either BT or GPS connectivity
Updated radio to the latest 1.15.25.14 with 1.15.25.35 rilphone, made no difference at all ..
I think I found it - G-Profile service was the cause of the problem. Once I stopped it, TomTom has got 100% starting rate. It's a pity, was a nice small app to have.