PDA

View Full Version : Ameo GPS Problem on T-Mobile WM6 ROM!!


georgiosp
27th January 2008, 03:49 PM
Hi all , just got an Ameo (U.K T-Mobile version) and upgraded to Windows Mobile 6 Professional CE OS 5.2.1620 (Build 18125.0.4.2) official rom.
Everything works fine except GPS signal that really sucks!! :( :( I have red all topics carefully and i have set all parameters right such as COM 5 and baud 9600 but with Destinator 7 it does not fix satellite signal! It gets one satellite on cold start after 3-5 minutes and maybe some 2nd or 3rd but really UNSTABLE...so it loses fix and again from start.. Navigation is almost impossible!

Any suggestions please?Does someone else have the same problem maybe?..Or my device is faulty?Is it possible that Destinator 7 does not work fine with the built in GPS?I have tried external bluetooth gps on other port and baud and it goes fine!!6 satellites minimum 8-9 maximum and fast fix even on cold start.Is it possible that my ROM version is problematic?

ROM Version: 2.35.110.4
ROM Date : 10/09/07
Radio Version: 1.50.00.00
Protocol version: 32.83.7020.20H

davemee
28th January 2008, 12:01 PM
I can never get a fix when it's in the faux-leather case, if that's any help... usually get a fix within 30s out of the case.

cyberjak
28th January 2008, 12:48 PM
I can never get a fix when it's in the faux-leather case, if that's any help... usually get a fix within 30s out of the case.

agreed, i get better results though in faux leather case, but my primary case is a n aluminum case hahaha so i know my own problem. temp resolve was an external recvr
hahaha

Digital.Diablo
29th January 2008, 01:56 PM
Have you tried the reg change to enable GPS in Camera mode (to allow location metadata to be stored within the picture)? I find if the GPS is ever slow to start up, using this first of all to get a location seems to kick things into life. Also make sure your QuickGPS file is upto date.

For some reason mine is now getting a lock much quicker than ever it has been before. I normally start TT just before I set off and previously it was taking approximatly a mile of driving before getting a lock. Now, it only takes about 1/2 a mile - have the US done something to the signal, or has my Ameo now developed supercow powers?

I'm running the cooked rom v3, radio 1.5 and its in the leather wallet.

Confucious
29th January 2008, 03:50 PM
Crumbs - half a mile? I usually start CoPilot when i get in the car and by the time I've started moving i have a fix - I take it out f the case to put in my Brodit mount but even in the house in the case it doesn't take that long to get a fix!

Digital.Diablo
29th January 2008, 10:14 PM
It is TomTom :D !!!

NeilM
1st February 2008, 05:31 PM
giorgosp: Yes, I can conform the problem and it's driving me mad!

Flashed to the T-Mo ROM this week, as PK3 was giving problems connecting to WMDC (tried a hard reset initially, and no better :( )

The T-Mo ROM is good, and allows WMDC to connect well, but since flashing, I've been unable to obtain a valid GPS lock. Tried with GPSInfo and iGO2006. I get a couple of small bars, and nothing more. Today, I drove for 45minutes, and no lock at all. My Orbit2 sitting on the car seat with CPL got a lock in 20 seconds from cold.

Previously, I could get a lock within 2 minutes if stationary, and about 10 minutes if moving (I live in a region with lots of windy country lanes, so rarely see the same bit of sy for more than a few seconds!), so this does seem to be an issue with the T-Mo radio.

NeilM
1st February 2008, 06:28 PM
..and further to the above, I've just downgraded the Radio to V1.47 (which means hard reset), and taken both the Orbit 2 and the Ameo outside- Orbit2 got a full fix in 30 seconds, and Ameo 30 seconds later (so 1min TTFF from cold, which is the best I've yet seen!)

Don't know if going back to radio 1.50 will keep the improvement, but I'm tempted to keep it as it is :)

ice_coffee
1st February 2008, 11:53 PM
im running 1.50 in a pawell rom and it's all good !! I think T-mo have messed things up !

georgiosp
2nd February 2008, 02:26 PM
So NeilM do you suggest me to downgrade radio version to 1.47?how many satellites is reaching to fix? ..to get a valid signal i think at least 4 and stable,right?

To all of you using other than the official t-mobile 2.35 rom with radio 1.50: how many sat signals do you achieve to fix using athena with the leather case under normal condition? does the radio version impact on gps signal so much?

NeilM
2nd February 2008, 04:06 PM
I tried reverting to radio V1.50 and same problem, so at least in my Ameo there is a problem with the new T-Mo ROM, Radio 1.50 and the GPS receiver.

Went back to 1.47, and this morning got a cold TTFF in 1 minute.

You need 3 satelites for a 2D fix- locates at ground level, and 4 for a 3D fix, which includes altitude.

From a cold boot, the 1st sat signal takes a while, but it then provides almanac info for any other in its vicinity. As the reciver gets more almanac info it builds a picture of the sky, then the ephemeral data is downloaded.

Once almanac info is obtained, you will see the short bars in GPS apps; once ephemeris is obtained the bars turn dark, or change colour and when you have 3 of those, navigation can commence.

I can't advise you to change the radio version, especially as it needs a hard reset, but can only repeat that it worked for me, here in East Anglia, using the Ameo on Orange.

georgiosp
2nd February 2008, 05:27 PM
Neilm,when reverted to radio 1.50 have you used the t-mobile rom or have you used only the radio cab provided by forum?even if my question seems silly i was thinking that maybe a file of those included in t-mobiles 2.35 rom radio 1.50 is problematic??so have you flashed only the radio version back to 1.50 or the entire rom (including t-mob radio 1.50)?
So you suggest change to 1.47?i understand that hard reset is unpleasant setup from beginning but having a dead gps after paying so much for this device is worse.. Could some expert please find this issue..?
..guys i live in rome and i tried everything..it gets 1 sat fix after 3 minutes and upon gets a second one it looses both of them..my ameo is like without gps.. only when i use an external bt i-blue i can use it.. but i bought this mobile for not carrying 200 things with me.. :-(

NeilM
3rd February 2008, 11:55 AM
I used the Radio only link, not the whoe T-Mo ROM, so it seems, for me at least, that it is the radio version, rather than where it comes from.

If you don't mind doing a hard rest, I'd say try it :) I can't say it will work, because it seems there are a number of factors which I don't understand. Some users have GPS working OK with this ROM and radio 1.50.

My personal experience is that radio 1.47 works much better for me, both for GPS and WiFi, and the phone reception is no worse. Battery use seems about the same.

Are you in Rome city centre? If so, have you tried going to a more open space to get a 1st fix? High density buildings can give a poor view of the sky, and give some 'multipath' interference, which can prevent a proper fix.

edenc
12th February 2008, 12:47 PM
Firstly, sorry to hijack this thread, but I couldn't find anything else appropriate.

Relevant to this thread: I have no problems with my current hard/firm/software combo and GPS connect time. It is about 2-3 mins without a current quickconnect file, but fine with both TomTom 6 and VisualGPSce.

Does anyone know what the antenna hardware is like for the GPS radio in Athena? Is it inbuilt to the semiconductor hardware or is there something else? If there is a physical antenna it could be broken? Try attaching an external bluetooth/USB receiver or external antenna. If one works it can only be the antenna or the GPS hardware at fault, right?

My problem
GPS quick connect will no longer connect through 802.11 wifi, bluetooth activesync or USB activesync. The only thing to have changed is that I briefly enabled and then disabled GPRS wifi. Although the settings for GPRS/WAP have been disabled and in network settings the option for 'programs that use the internet automatically' is set to 'my work network', GPSquickconnect still seems to be using my GPRS service provider (which cannot be deleted).

I know a hard reset will resolve this but it would be nice to know if anyone else has come across this and found a reg tweak to remove the service providers in the drop down connections list.

Thanks is advance.