Did you know you can enable the GPS functionality in the new-generation Pocket PC phone, the HTC Trinity (HTC P3600) with a simple, easy, free ROM upgrade? Did you know the latest ROM upgrade offers a significantly lowered boot-in time and slightly decreased (albeit still very bad) A2DP CPU usage, more wireless icons (E for Edge) and, last but not least, SDHC compatibility? If you didn’t but would certainly enjoy the advantages of the built-in GPS unit and the other goodies of the new ROM, make sure you do the following:
download the SSPL-TRIN.zip utility linked in from the first post of this thread (note that you’ll need to register yourself in the XDA-Dev forums to be able to access the file)
download the new ROM upgrade from here (Pacific users may also want to give a try to this Chinese source to see if it’s faster)
decompress both files. From the first, transfer SSPL-TRIN.exe to your PDA and execute it there, after disconnecting your Trinity from your desktop. You’ll see the standard rainbow-color bootup screen.
now, start the large RUU_Trinity_DOPODASIA_WWE_1.23.707.6_6275_1.35.00.11_108_Ship.exe file on the desktop, press the OK / Update / Yes buttons until it gets to flashing the new ROM.
It worked for everyone so far. Note that if there is “Serial” at the bottom third of the rainbow bootloader screen of the Trinity, the desktop PC won’t likely to recognize it. Then, just reset the PDA and, after booting in, just restart SSPL-TRIN.exe. You’ll need to see “USB” for the PDA to be recognized.
Warranty issues
Note that, by upgrading, you MAY lose your warranty, depending on where you've initially purchased your Trinity from. However, as you can flash back a ROM of your operator any time (assuming they DO come out with any publicly available ROM version), this isn’t really an issue most of the time.
Also note that, as SSPL-TRIN doesn’t remove the CID lock (unlike with the older and expensive IMEI-Check service), you won’t have problems with the service folks because of the lack of the CID lock. This is also a huge advantage over the IMEI-Check method.
Advantages
I’ve already listed the major advantages of the new version; most importantly, the enabled GPS functionality. Having GPS support in your phone is just unbeatable. Note that you must use the port COM9:. Also note that you may not want to run for example iGo to find the GPS port automatically because it’ll spend a LOT of time in doing so – just give it COM9: right at the beginning, and you’re all set.
As has already been pointed out, the boot-in time has been significantly reduced between the initial HTC ROM version (1.15.405.5 dated 10/23/2006) and the this one (1.23.707.6, 02/08/2007); according to my tests, it’s 39 seconds now, as opposed to the original 45 seconds. Getting better and better (albeit still can't beat the 36 seconds of the AKU3 HTC Wizard!)
I’ve also made some serious benchmarks with the new version to see whether the problematic areas (digitizer handling, A2DP CPU usage) have been fixed. Unfortunately, they aren’t – read on to see what the problem is!
Acute problems with the HTC Trinity
The excellent XDA-Developers community, lately, has been complaining about two special issues regarding the HTC Trinity, the, in my opinion, best HTC 2.8” Pocket PC right now. Having just received a Trinity myself, I’ve thoroughly scrutinized these problems.
Touchscreen CPU usage issues
(Also see this thread)
Unfortunately, it seems all 2.8” WM5 HTC QVGA Pocket PC phones are particularly sensitive to long-pressing the touchscreen. While none of the other Pocket PC models I’ve tested (HP iPAQ 2210, HP iPAQ hx4700 running WM5, Dell Axim x51v , Fujitsu-Siemens Pocket Loox 720 and the HTC Universal) exhibited any increased CPU usage while constantly keeping the stylus down on the touchscreen, both the 2.8” WM5 HTC Wizard and the HTC Trinity did. The, otherwise, almost-zero CPU usage of gwes.exe raised, on the (non-overclocked) former, to around 17% and about 36% on the latter. This is why, for example, action games like K-Rally or Skyforce (Unlimited) will become next to unplayable when, as is recommended, played with the stylus.
This issue is the same in even the latest (Dopod) Trinity ROM version and should be addressed by HTC as soon as possible. It’s hopefully a driver issue and, therefore, can be fixed in software.
(Note that, again, different HTC phone models exhibit different level of excess CPU usage because of the problem. The new, quick Trinity suffers a lot from the bug, the older, “slow” Wizard suffers a lot less, particularly when it’s overclocked (when overclocked to 240 MHz, games like K-Rally become really enjoyable with the stylus). This, however, doesn’t mean ALL “old” (TI CPU-based) HTC phones fare much better than ALL “new” (Samsung CPU-based) HTC phones – other new, Samsung-based models may behave fat better in this respect.
I really hope HTC really soon addresses this issue as it’s almost completely renders some? several? of their models almost useless for stylus-based action gaming and unnecessarily increases the power consumption.)
A2DP CPU usage issues
Unfortunately, there is another major Achilles’ heel with all Trinity ROM’s released so far: the A2DP CPU usage.
While the built-in A2DP doesn’t consume much CPU cycles in the other HTC phones I’ve tested (for example, on the HTC Wizard, even at the original 195 MHz, it hardly exceeds 30%), the Trinity is an exception. When playing music via A2DP, the CPU usage when used in the default (mono) mode is 52.5%, in stereo mode, 49.5%. (With the original ROM version, the figures were 54% and 51%, respectively – as can be seen, the new version has slightly improved upon the situation, but it’s still much worse than with most other devices.) This is another issue HTC should look into as soon as possible, because it makes the device almost useless as an A2DP player.
(A quick note: the A2DP defaults to mono in this device. If you’re familiar with the Registry and have already read my older A2DP-related articles, you will know HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\Bluetooth\ A2DP\Settings\ UseJointStereo also introduced in my article The A2DP support & sound quality & power consumption of the Microsoft and Widcomm BT stack compared; a lot of new A2DP info. With the Trinity, it’s set to 1 by default; you’ll want to change its value to 0.
If you feel unsafe about editing the Registry, you can also use the excellent, free HTweakC tool. I highly recommend it for all Trinity, Wizard and TyTN users.)
Widcomm BT stack compliance?
Unfortunately, as was the case with the original HTC Trinity ROM, neither the Dell Axim WM5 x50/x51 / HTC Wizard nor the HTC Universal Widcomm Bluetooth stacks work with the new ROM. This is very bad news: first, the Microsoft Bluetooth stack as of AKU3 has still bad sound quality with a lot of Bluetooth stereo headphones; second, the Widcomm BT stack would consume considerably less power on the Trinity (I’d say the third of that of the current MS BT stack.)
Verdict
I’m really sorry about HTC’s leaving so bad bugs in the firm- and/or software of this model – the Pocket PC I, otherwise, recommend the most of today’s Pocket PC’s. While upgrading to the new ROM version is HIGHLY recommended for most people, you still won’t be able to play fast-paced action games and should think twice before using the built-in A2DP sound transfer.
Recommended links
My older A2DP-related articles. I also recommend the two reports I’ve posted today about the news: here and here.
Thanks for your excellent work here!
I really appreciate what you do for the Trinity communitiy!
Thanks for a great summary.... nice to have it all in one post, one of my disadvantages with the Trinity is the bad performance with xvid in coreplayer, due to the ATI graphic chip...
MP3/Audio quality
I've read that some users have experienced highly degraded audio quality after upgrading to the latest test Dopod ROM. Has this final ROM corrected this issue?
psargent said:
...MP3 quality is GREATLY degraded after upgrading to the test rom. Used to be rich with plenty of bass when plugged into my car aux input when I was using HTC rom, now it sounds like I am listening through a tin can!!! Sounds like most of the lower frequencies are not being sent out of the audio output...
Click to expand...
Click to collapse
prsnow said:
I've read that some users have experienced highly degraded audio quality after upgrading to the latest test Dopod ROM. Has this final ROM corrected this issue?
Click to expand...
Click to collapse
I've only checked it through (the crappy) A2DP, not via a wired headset - I couldn't notice any sound degradaton, iot sounded equally bad than with other MS BT stack A2DP implemenations.
Are you sure about SDHC being now supported? From other reports it seems that the problem with disappearing files and folders on 4GB SDHC cards is still there.
Menneisyys said:
Did you know you can enable the GPS functionality in the new-generation Pocket PC phone, the HTC Trinity (HTC P3600) with a simple, easy, free ROM upgrade? Did you know the latest ROM upgrade offers a significantly lowered boot-in time and slightly decreased (albeit still very bad) A2DP CPU usage, more wireless icons (E for Edge) and, last but not least, SDHC compatibility? If you didn’t but would certainly enjoy the advantages of the built-in GPS unit and the other goodies of the new ROM, make sure you do the following:
download the SSPL-TRIN.zip utility linked in from the first post of this thread (note that you’ll need to register yourself in the XDA-Dev forums to be able to access the file)
download the new ROM upgrade from here (Pacific users may also want to give a try to this Chinese source to see if it’s faster)
decompress both files. From the first, transfer SSPL-TRIN.exe to your PDA and execute it there, after disconnecting your Trinity from your desktop. You’ll see the standard rainbow-color bootup screen.
now, start the large RUU_Trinity_DOPODASIA_WWE_1.23.707.6_6275_1.35.00.11_108_Ship.exe file on the desktop, press the OK / Update / Yes buttons until it gets to flashing the new ROM.
It worked for everyone so far. Note that if there is “Serial” at the bottom third of the rainbow bootloader screen of the Trinity, the desktop PC won’t likely to recognize it. Then, just reset the PDA and, after booting in, just restart SSPL-TRIN.exe. You’ll need to see “USB” for the PDA to be recognized.
Warranty issues
Note that, by upgrading, you MAY lose your warranty, depending on where you've initially purchased your Trinity from. However, as you can flash back a ROM of your operator any time (assuming they DO come out with any publicly available ROM version), this isn’t really an issue most of the time.
Also note that, as SSPL-TRIN doesn’t remove the CID lock (unlike with the older and expensive IMEI-Check service), you won’t have problems with the service folks because of the lack of the CID lock. This is also a huge advantage over the IMEI-Check method.
Advantages
I’ve already listed the major advantages of the new version; most importantly, the enabled GPS functionality. Having GPS support in your phone is just unbeatable. Note that you must use the port COM9:. Also note that you may not want to run for example iGo to find the GPS port automatically because it’ll spend a LOT of time in doing so – just give it COM9: right at the beginning, and you’re all set.
As has already been pointed out, the boot-in time has been significantly reduced between the initial HTC ROM version (1.15.405.5 dated 10/23/2006) and the this one (1.23.707.6, 02/08/2007); according to my tests, it’s 39 seconds now, as opposed to the original 45 seconds. Getting better and better (albeit still can't beat the 36 seconds of the AKU3 HTC Wizard!)
I’ve also made some serious benchmarks with the new version to see whether the problematic areas (digitizer handling, A2DP CPU usage) have been fixed. Unfortunately, they aren’t – read on to see what the problem is!
Acute problems with the HTC Trinity
The excellent XDA-Developers community, lately, has been complaining about two special issues regarding the HTC Trinity, the, in my opinion, best HTC 2.8” Pocket PC right now. Having just received a Trinity myself, I’ve thoroughly scrutinized these problems.
Touchscreen CPU usage issues
(Also see this thread)
Unfortunately, it seems all 2.8” WM5 HTC QVGA Pocket PC phones are particularly sensitive to long-pressing the touchscreen. While none of the other Pocket PC models I’ve tested (HP iPAQ 2210, HP iPAQ hx4700 running WM5, Dell Axim x51v , Fujitsu-Siemens Pocket Loox 720 and the HTC Universal) exhibited any increased CPU usage while constantly keeping the stylus down on the touchscreen, both the 2.8” WM5 HTC Wizard and the HTC Trinity did. The, otherwise, almost-zero CPU usage of gwes.exe raised, on the (non-overclocked) former, to around 17% and about 36% on the latter. This is why, for example, action games like K-Rally or Skyforce (Unlimited) will become next to unplayable when, as is recommended, played with the stylus.
This issue is the same in even the latest (Dopod) Trinity ROM version and should be addressed by HTC as soon as possible. It’s hopefully a driver issue and, therefore, can be fixed in software.
(Note that, again, different HTC phone models exhibit different level of excess CPU usage because of the problem. The new, quick Trinity suffers a lot from the bug, the older, “slow” Wizard suffers a lot less, particularly when it’s overclocked (when overclocked to 240 MHz, games like K-Rally become really enjoyable with the stylus). This, however, doesn’t mean ALL “old” (TI CPU-based) HTC phones fare much better than ALL “new” (Samsung CPU-based) HTC phones – other new, Samsung-based models may behave fat better in this respect.
I really hope HTC really soon addresses this issue as it’s almost completely renders some? several? of their models almost useless for stylus-based action gaming and unnecessarily increases the power consumption.)
A2DP CPU usage issues
Unfortunately, there is another major Achilles’ heel with all Trinity ROM’s released so far: the A2DP CPU usage.
While the built-in A2DP doesn’t consume much CPU cycles in the other HTC phones I’ve tested (for example, on the HTC Wizard, even at the original 195 MHz, it hardly exceeds 30%), the Trinity is an exception. When playing music via A2DP, the CPU usage when used in the default (mono) mode is 52.5%, in stereo mode, 49.5%. (With the original ROM version, the figures were 54% and 51%, respectively – as can be seen, the new version has slightly improved upon the situation, but it’s still much worse than with most other devices.) This is another issue HTC should look into as soon as possible, because it makes the device almost useless as an A2DP player.
(A quick note: the A2DP defaults to mono in this device. If you’re familiar with the Registry and have already read my older A2DP-related articles, you will know HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\Bluetooth\ A2DP\Settings\ UseJointStereo also introduced in my article The A2DP support & sound quality & power consumption of the Microsoft and Widcomm BT stack compared; a lot of new A2DP info. With the Trinity, it’s set to 1 by default; you’ll want to change its value to 0.
If you feel unsafe about editing the Registry, you can also use the excellent, free HTweakC tool. I highly recommend it for all Trinity, Wizard and TyTN users.)
Widcomm BT stack compliance?
Unfortunately, as was the case with the original HTC Trinity ROM, neither the Dell Axim WM5 x50/x51 / HTC Wizard nor the HTC Universal Widcomm Bluetooth stacks work with the new ROM. This is very bad news: first, the Microsoft Bluetooth stack as of AKU3 has still bad sound quality with a lot of Bluetooth stereo headphones; second, the Widcomm BT stack would consume considerably less power on the Trinity (I’d say the third of that of the current MS BT stack.)
Verdict
I’m really sorry about HTC’s leaving so bad bugs in the firm- and/or software of this model – the Pocket PC I, otherwise, recommend the most of today’s Pocket PC’s. While upgrading to the new ROM version is HIGHLY recommended for most people, you still won’t be able to play fast-paced action games and should think twice before using the built-in A2DP sound transfer.
Recommended links
My older A2DP-related articles. I also recommend the two reports I’ve posted today about the news: here and here.
Click to expand...
Click to collapse
I upgreaded as instructed and put the new rom. My problem is I see no GPS icon in the Systems folder or anywhere for that matter to set it to Com 9. Furthermore, when I installed Tomtom it said i have no gps on my Trinity Can you help advise where my GPS icon is
Another thing that is bugging the hell out of me is the network configuration. how can I get it rid of it completely so that everytime i soft reset, i don't get that annoying message?
Second, please advise, if I remove My Connect, does it make a difference to the device? I live in Canada and do not own a dopod but a HTC unbranded Trinity instead.
Third, What is the CAM program. What does it do?
Many thanks for any help you can offer and best regards,
Gilbert
Gilbert said:
I upgreaded as instructed and put the new rom. My problem is I see no GPS icon in the Systems folder or anywhere for that matter to set it to Com 9. Furthermore, when I installed Tomtom it said i have no gps on my Trinity Can you help advise where my GPS icon is
Click to expand...
Click to collapse
Hold - one thing at a time
1) Once you have upgraded the ROM you have to configure TomTom to use the internal GPS, so start TomTom, go to "Change Preferences", go to "Show GPS Status" , then "Configure" to choose your new GPS. Select "Other NMEA GPS Receiver", baud rate = 115200, "GPS on COM9".
2) You will not see any "GPS setting" anywhere unless you hack the Windows Registry. You need a registry editor to do that. Go in HKLM->ControlPanel->GPS Settings: get rid of any DWORD there and make sure to add a new DWORD with the following values: "Group"/0x02. Once done SoftReset and you will have your GPS icon into Settings->Connections.
3) BTW, if you do that registry hack you will be able to map the GPS to other COM ports as well.
Hope this will help!
Anubis
anonimo said:
Are you sure about SDHC being now supported? From other reports it seems that the problem with disappearing files and folders on 4GB SDHC cards is still there.
Click to expand...
Click to collapse
Yes; unfortunately my 4GB Transcend SDHC card still behaves in this way with the new rom.
Anubis1965 said:
Hold - one thing at a time
1) Once you have upgraded the ROM you have to configure TomTom to use the internal GPS, so start TomTom, go to "Change Preferences", go to "Show GPS Status" , then "Configure" to choose your new GPS. Select "Other NMEA GPS Receiver", baud rate = 115200, "GPS on COM9".
2) You will not see any "GPS setting" anywhere unless you hack the Windows Registry. You need a registry editor to do that. Go in HKLM->ControlPanel->GPS Settings: get rid of any DWORD there and make sure to add a new DWORD with the following values: "Group"/0x02. Once done SoftReset and you will have your GPS icon into Settings->Connections.
3) BTW, if you do that registry hack you will be able to map the GPS to other COM ports as well.
Hope this will help!
Anubis
Click to expand...
Click to collapse
I got:
GPS program port: COM9
GPS hardware port: COM6 (randomly chosen) with Baud rate 115200 (what does Baud rate mean?)
Access: automatically
In TomTom I use COM9, but when I switch the program with the hardware port, TomTom tells me that the GPS still has port COM9.. weird.
Anyways, is this correct? Thanks in advance!
BTW: this goes a looot quicker if you choose the other NMEA GPS Receiver than if you use "other external bluetooth" thanks!
BTW2: you can use "http://www2r.biglobe.ne.jp/~tascal/download/pocketpc/tre_e.htm to edit the register.
Thanks Menneisyys for the summary.
Regarding the cpu consumption I am not so sure everything is HTC related.
can you give me a device which is performing very well with this samsung cpu?
it is fast: 400 Mhz. ok, on paper. but in real life it needs a lot of cycles to do things...
40% if you press the screen.
85% for 320*240 simple divX with tcpmp (more than the OMAP 200 from Wizard)
55% to encode A2DP stream.
and it gets on and on, and does not improve with new ROMs.
I start to wonder why nobody is blaming samsung there. Is there proof somewhere of its effectiveness?
I have HTC-P3600 purchased in US. So far I have no problem using Cingular service and I like the phone.
But why I am posting. I want to update to the latest ROM with the GPS activated.
When I run SSPL-TRIN I get only "SERIAL" in third line.
I have tried three times and same result. I there a something else I need to change to get "USB" activated.
Thanks in advance Peter Simek
psimek said:
I have HTC-P3600 purchased in US. So far I have no problem using Cingular service and I like the phone.
But why I am posting. I want to update to the latest ROM with the GPS activated.
When I run SSPL-TRIN I get only "SERIAL" in third line.
I have tried three times and same result. I there a something else I need to change to get "USB" activated.
Thanks in advance Peter Simek
Click to expand...
Click to collapse
You have to have it connected to USB when you run SSPL-TRIN.exe.
mdacfan said:
@chenchon
my way:
1. extract RUU_Trinity_DOPODASIA_WWE_1.23.707.6_6275_1.35.00. 11_108_Ship.exe with WinRAR to XP PC (NewFolder)
2. connect phone to windows XP PC (activesync status green)
3. copy the SSPL-trin to the device ie. \temp (memory) - not storage card
4. run the SSPL-trin (Trinity Display must then show "USB" at the bottom) - wait until XP detects a new USB device
5. run from the extracted file on XP PC (NewFolder) the file "ROMUpdateUtility.exe"
6. Pass all Upgrade questions and wait about 10 Minutes to finish the upgrade from 0% to 100%
7. Softreset Trinity after the successfull upgrade
No SuperCID required if you use SSPL !!
good luck,
Gerhard
Click to expand...
Click to collapse
Worked well for me.
Tomtom 6.03 freeze
hi,
does anyone with tomtom 6.03 as any problem of freezing while u r navigating?
i think the problem was when i selected the gps in tomtom config... i selected "use own gps" (the built in gps) but now i choosed another cable gps nmea on com9 and with 115200. Tomorrow i'll feedback
another experiences with tomtom 6.03 are welcome.
best regards,
aprt
Lost Voice Dialing
Hi All,
I have done the ROM upgrade, but seem to have lost voice dialing. Is this something available only on the original HTC ROM? Can I download this seperately?
Thanks
Small Problem
I have updated both the test and final rom,I have noticed a strange problem. As I am using a third party keyboard because of the arabic language i can not switch the keyboard to any installed one rather than the preinstalled SIPs.
I tried two different arabic software plus Resco keyboard all the same. som times it works and many other times it does not.
Any Idea?
I started noticing problems too.
When I soft reset, Pocket Informant always start automatically and hangs the phone.
Before that, the Network guide started and hung, every reboot, so that I had to hard reset.
It works for about one hour, regardless of which programs I install.
GPS works though..
NOT Blaming Samsung
meroupow said:
Thanks Menneisyys for the summary.
Regarding the cpu consumption I am not so sure everything is HTC related.
can you give me a device which is performing very well with this samsung cpu?
it is fast: 400 Mhz. ok, on paper. but in real life it needs a lot of cycles to do things...
40% if you press the screen.
85% for 320*240 simple divX with tcpmp (more than the OMAP 200 from Wizard)
55% to encode A2DP stream.
and it gets on and on, and does not improve with new ROMs.
I start to wonder why nobody is blaming samsung there. Is there proof somewhere of its effectiveness?
Click to expand...
Click to collapse
In the case of TCPMP it is not anything todo with solely the Samsung chip itself but more todo with the Imageon Chip being not properly utilised in the ROMS and also TCPMP not being able to make use of the Imageon with the Samsung/ATI combo.
I did a small test once where I had one video that didn't cause screen flicker with the Imageon being used in TCPMP and I got a MASSIVE improvement - posted the benchmark results in another post I will look for them.
The A2DP Stream in my opinion is more todo with the Bluetooth Stack i.e if it were WIDCOMM then we woudn't have these problems.
As for the screen press I am hoping it is down to the Samsung Chip and ROM combination as a pose to just the chip being flawed.
And yes they should put more effort in tweaking these flaws and provide fixes for software and ROMS faster - but these are money making corporations that like to take shortcuts.
The joys of early adoption!
Hello,
Everyone seems to talk about 115200 baud but in Tomtom the highest you get is 57k+ for baud speed. I read once that it should remain on 9600 baud to work well. Where do you all see the 115200 baud? is it through the hack of the registry to enable the GPS icon? Hope someone can help me here.
Best regards,
Gilbert
Related
Hello everyone,
I would like to start this new thread with a different purpose than trying to explorer the latest and gratest of releases of ROMs, extensions, software and patches.
I have tested many of the releases posted here and I have yet to find one that offer a rock solid unit that can be depended on in all situations.
What I would like is to put together a package based on the best of all available that offer the highest reliability available for our device.
It's very annoying to have to reset the device, somtimes more than one time in one day because you loose GPRS connectivety or because you turn on the WiFi card at an unlucky moment and lock up the device.
It's very annoying that you press the answer button repeatedly but have trouble picking up the rining phone.
It's very annoying that you try to make a call, but the phone keeps hanging up without making the call until you reset the phone subsystem.
It's very annoying that you pick up the device to make a call only to find that for some reason the phone has been locked up for hours with the screen on and now you are out of power and far away from your charger.
It's very annoying that your screen gets garbled and you find that you are unable to get the display back to normal without resetting the device.
It's very annoying that bluetooth more or less have turned out to be a marketing item only, since we have yet to se an implementation on the device that works (and maybe we never will)
If you agree with me or/and have experienced some or probably all of the above and have some input you would like to share on what is the best release, or have software and patched that have made a difference to you, then please contribute and maybe we could one day have a reliable operating system and software pack on our PDA that we can actually trust to handle the important task of keeping us connected to the rest of the information based world 24/7.
I hope many people will participate in this thread and that we can get to a release of software that we can all feel happy about, since it seems that none of the providers have been able to accomplish this task.
Michael
Fully agreed with you. And here is my BA config:
- MDA III with 1 Gb SD (Trandcent 80x)
- ROM 1.40 & radio 1.12
- Big storage - No Extended ROM
- Excluded nearly all software from WWE 1.40 ExtROM. Install only patched
Most apps are installed to storage :lol:
- Pocket Informant 2005 (In main memory)
- Pocket breeze 5 (In main memory)
- Pocket Player 2.6
- Sound Explorer 2005
- Pocket Navigator 2.74
- Sprite backup 3.1.4
- Mobile Pocket reader 5.0
- Total Commander 2.0
- Adobe Acrobat Reader 2.0 for PPC
- Tools: Cab Installer, vxUtils, Tascal Reg. Editor TRE 0.9, calculator, stop time ...
Full backup with Sprite backup 3.1.4, excutable archive file so that I can restore to a fully loaded system righ after hard reset. The backup is also in storage.
With this config the phone is very stable. On average 1 soft reset/week, mostly due to phone problem (I work in a building with very week GSM signal).
here here!
while ive not bothered to update for exactly one year now, i truely couldn't be bothered with the rom backup, new rom, install settings, settings restore, all to find out that... oh others are still having a problem with phones hanging/not connecting, because you used bluetooth and didn't reset before using gprs. of course, silly me!
right now i'm looking for a stable basic setup, with Tomtom 5 (bt gps mouse) and gprs useage... and possibly, using them together!
it does seem experimenting is only way to do so...
What a good idea - however, after one year of updating ROMs I do not think that there is a stable system for this device after all ...
I cannot use my Qtek for business because
- I am not sure whether I will miss a call because my Qtek somehow decides not to ring
- I am never sure whether I can finish a call decently (or the devices shuts down on its own)
And I am tired of resetting the device before and after
- using WLAN
- using BT
Currently, I am on
ROM 1.42.01 GER
Radio 1.12.00
ExtROM 1.42.116 GER
which still has all the flaws mentioned above.
This is the 4th different ROM I have installed (WWE, GER). I mainly use it for storing contact info and meetings.
A
I still wan't to try.
I'm using a configuration of 1.40 and 1.12. This is OK, but the phone app is still quite unstable and the device itself will hang. Most trouble seems to be when you press a key at an unlucky split second when the unit is trying to do something else, this often leads to lockups.
Does anyone have any input regarding the version numbers to use? Especially is 1.42 or 1.31 better than 1.40? and is 1.12 better than 1.13 or vice versa?
What about patches and registry hacks, what do you consider being a vital patch or hack to improva stability dramatically ... ? If any.
I hope to get some input from you guys that install every single thing and have gained allot of input on what works and what doesn't?
Michael
This combination seems to be vert stable for Scandinavians
I have had very good results so far with this combination:
BA_DT_WWE_NorwayRetail_14000_149_11200_Ship.exe
Then install:
86794-9090_radio_upgrade_1.15.00.zip
This is so far the bes experience I have had while I had the device.
Michael
Update
After a while, I have observed that I'm still having the GPRS connect problem and I have therefore installed the:
IA_CallerID_1.20_WWE.CAB
I will update my experience in a while. So far I like this combination, except that GPRS cinnection problem. I haven't had many other problems. There has been a little "flutter" around Blue Tooth and TomTom, If you try to start TomTom with BT disabled, you sometimes seem to grid lock until you re-boot.
Extended ROMs
Is it my imagination? The higher the extended ROM version the less stabillity? It seems to me that way. The more stuff they add, the less overall stability you get. Does anyone have a different experience?
Michael
jamcow said:
here here!
while ive not bothered to update for exactly one year now, i truely couldn't be bothered with the rom backup, new rom, install settings, settings restore, all to find out that... oh others are still having a problem with phones hanging/not connecting, because you used bluetooth and didn't reset before using gprs. of course, silly me!
right now i'm looking for a stable basic setup, with Tomtom 5 (bt gps mouse) and gprs useage... and possibly, using them together!
it does seem experimenting is only way to do so...
Click to expand...
Click to collapse
i find that when upgrading to the new WM5 roms, that all my files, programs and settings, even contacts and messages are all still as i left them, i just put the device into bootloader and plonk into the cradle, then start upgrade 2 mins later its done, all new features and nothing that is usually backed up is changed.
The best stabillity so far
I'm still running with the configuration outlined in my previous posts. And it's pretty stable, the only problems I seem to be affected by are:
After 1 to 7 days the GPRS connection fails and I have to reset the device to get it working.
Rarely some applications and the phone gets in a bind somehow, probably by starting at the same time in an incompatible way and lock up the phone. I have to reboot the device to get out of that.
The phone part itself seems to be stable and I have no missing sound or low volume issues.
I had good bluetooth functionality, but since paring my device with my GPS I can't get the device to connect correctly to my headset. I will pair up and then when it tries to connect it fails. I'm unsure what that's about. I don't use the bluetooth headset much, so I haven't been bothered much by this, but I would ofcourse prefer if everything was working as you would expect it to!
I would upgrade my base ROM to 1.42, but my testing and experiences with that have been that it's more unstable than 1.40.
I'm even more convinced now that I'm right about the extended ROM thing, the higher the version of extended ROM to more problems (potential problems).
Any input on stability are very welcome, I would love to find a near perfect configuration where most things work 100% and all the time.
Michael
Updates are in BLUE
Okay, time for a long post... (and please remember this is all subjective, and personal experiences, your's may be different!)
Preamble:
I've had my BA for a couple of months now, prior to that it has always been PalmO OS devices which I loved, but I wanted a phone enabled device and the Treo was just too expensive to justify it... so ebay beckoned and £100 later I was a proud owner of an O2 XDA IIs...
I'm a fairly heavy user of my PDA's I use them for all my network admin, work documentation, mail on the move, a heavily laden calendar and everything else a busy professional with a family does... with loads, and loads, of travel!!
First thoughts:
I was, to be honest, dreading the move to M$, I have always been a promoter of opensource, Palm, and anything other than the big M, but I was pleasantly surprised... with relativley little pain I got into the WM2003SE way of things, and after a quick read of the Wiki, I cooked my own ROM and had an O2 device which worked really well... I could use my BT headset as stereo headphones or a headset, while connecting to my GPS, I had my Gmail, O2, Hotmail and other accounts set up, I could chat with Skype, GoogleTalk, MSN and ICQ, I had a WiFi sniffer, and all the other trappings as well as a GPRS connection for TomTom Traffic etc... and the media capability was cool, TCPMP worked really well, and with a 1Gig SD card I could take a couple of movies/TV episodes for the journey... in short, I no longer had to worry about taking a laptop on the road.
But that wasn't enough, I was reading about these WM5 ROMS and felt that, after being pleasantly surprised with WM2003SE, it was worth a shot... over the last few days I have tried several ROM's and they all have up/down sides... what follows is a (not so brief) summary of my experiences...
I load up my BA fairly heavily, and I had specific requirements... speed, callerid, space, preferrably A2DP, and again, speed!!
TuMa 1.4 (MS BT Stack):
Some see this as the 'Daddy' of the WM5 ports and I must admit, with one major bugbear, this is an impressive ROM... it includes a lot of stuff in the build which some might prefer was left out, but for the basic user it's helpful to have some of these...
(A Really COOL Boot Logo!!)
TotalCommander
PocketRAR
Extra Games
Cyberon Voice Dialler
GB-Soft Tweak
vBar
pShutXP
IP Utilities
Pocket FTP
SMS Name Notify
ClearVue PDF
BT Headset Today Plugin
BT Stereo Control
Device Lock Today Plugin
and other bits and bobs...
This may well be considered as a 'bloated' ROM (but remember they are all installed in ROM, so no space is taken up from your 'own' space), there is an Ext_ROM option, from SD Card, in this ROM so the memory works out like this... 60MB Storage (- whatever you set up as an Ext_ROM) and 91MB Program Memory... you also get a 32MB Temp_Drive ( I assume this is like a RAMDISK?)... available on a clean install is:
Storage: 57.62MB
Program: 72.53MB
TEMP_Drive: 31.85MB
Total: 162MB (Storage & TEMP_Disk available for app install = 89.47MB)
Out of the Box:
BT: Works very well... including A2DP, I had no problems, whatsoever with this BT Stack/Setup.
WiFi: Again no problems and no reset once I'd applied the Reg Hack.
Base OS: This is where, for me, it all falls apart... even with eveything else working like a dream, the 'Pictures & Videos' app in this build just does not work, at all! This means that the CallerID functionality is kaput... I can't live with this, I love the ability to 'see' who is calling, I have many, many numbers in the work category, and being able to put a face to a number beats having only a name any day... other than that this ROM works really well, and the additional install space means I can have all my apps installed without the 'critical' low storage warning... in addition to this another glitch I have come across is 'sticky' buttons... both the D-Pad and the hardware keyboard can result in stuck keys/repeated entries... BT Voice Dialling works with Cyberon, and even better with MS Voice Command (if you hack a little), and with the A2DP profile the MS option works through the BT headset rather than the PDA speaker,,,
Ivan V4 R3 (WidComm BT Stack):
Built as a 'clean' ROM, this one really comes with no bells or whistles, included are:
BT Headset Today Plugin
Cyberon Voice Dialler (I Think!)
and apart from the Base OS stuff, that's about it!
This is a relatively speedy ROM on first impressions, but it slows dramatically down when loaded with apps... you can setup an Ext_ROM with this one, or use the full 60MB as storage... there is no Ramdisk or Temp_Drive option so you get 60MB Storage (- whatever you set up as an Ext_ROM) and 123MB Program Memory... available on a clean install is...
Storage: 57.64MB
Program: 98.40MB
Total: 156.04MB (Storage available for app install = 57.64MB)
Out of the box:
BT: works okay, although there is no A2DP functionality,but I can connect to my headset and my GPS... (which is a big thumbs-up for me). I have experienced a few of the system restarting glitches, but not the BT not restarting/dropping out with this ROM so that's an upside.
WiFi: Connectivity is okay (typical BA signal strength) and once you apply the 'ResetOnResume' Reg hack then it works very well, I have had no dropouts or non-restarts with it at all.
Base OS: A big upside for this is the Pictures & Video, it works! This means I can use the CallerID function on the WM5 dialler, which I do, extensively!!
Logout V5.4.03 (WidComm BT Stack):
Read great reviews of this on the forum, so thought I'd give it a bash... included are (if you install the Ext_ROM):
Cyberon Voice Dial
ResInfo
Task Manager
Device Lock Today Plugin
TuMa Keyboard (I think, although it looks nicer!)
Just installed this one today... first impressions weren't very good as many of the apps which were meant to be there couldn't be found on startup... then I realised I hadn't cleaned my Registry Hive before the Flash!! The speed in this one is blinding! Compared to both of the others this one is as fast as 2003SE, again, it uses a Ramdisk so you have added space for installs, and it can also use an Ext_ROM, so you have your choice... so you get 60MB Storage (- whatever you use for Ext_ROM), 93MB Program Memory and a 32MB Ramdisk... available on a clean(ish) install (I installed the MMS/Album/Voice Dial and Resinfo Cabs) is...
Storage: 52.8MB
Program: 71.9MB
RAMDISK: 31.8MB
Total: 156.6MB (Storage available for app install = 84.6MB)
Out of the Box:
BT: What there is available works fine... but no A2DP... not experienced any restart issues yet, but it's ealry days
WiFi: Again, all seems fine
Base OS: As stated above this one is blindingly fast... so much so that I actually forget it's a ported WM5 ROM at times, the Pictures & Videos app works, so that's a biggy on the plus side for me, everything seems to be ticking along quite sweetly...
UPDATE 1: Logout ROM seems to lag for a while after installs of S/W... but it settles down again, had one occurrence of s-s-s-stuttering keyboard, but nothing major, and no 3s delay on phone ring, even without reg hack
Artz (WM5_ArtZ_upgrade_WWE_1.7.1.3400_SDCard)
Iloved this ROM at first sight, it had the Stereo Audio BT profile without any updating, it was clean, smooth and fast, but then I tried using it... I'm not sure what went wrong but it just didn't 'gel':
BT: As stated this looked good from the outside, and it did recognise both my GPS and my headset, and it would connect with both, but, andit's a huge but! It wouldn't get any services from my headset on reconnection, it wouldn't recognise my headset as stereo (even though it though it would recognise the profile?) and as vor a 'normal' BT headset, it just sent my i.Tech headset haywire, beeping, pinging and ringing constantly... I couldn't stop it!
WiFi: Again, issues with this... no matter what I did, this ROM would not reconnect to my AP after a reset or power down...
Base OS: At face value this ROM was excellent, it had all I needed to start setting up my BA, and the option for Ext_ROM from an SD card is great... but with the issues above, and the spped at which it 'slowed down' with apps added it was unworkable
Obviously I will update each of these as I continue to 'tinker'... and wait for Logout 5.4.5 or TuMa 1.5, if either of these fix the little issues I've mentioned (A2DP for Logout and P&V for TuMa) then I'll be in BA WM5 Nirvana!
In summary, heres a little overview (TuMa, Ivan, Logout):
Speed: 3, 2, 1 (And then some!)
Apps: 1, 3, 2
A2DP: Y, N, N
P&V: N, Y, Y
Voice Dial: Y*, Y, Y
Available Mem: 162/89, 156/57, 156/84
*TuMa's is the only ROM I tested with MS Voice command, so BT Mic+PDA speaker for the other two, complete headset for TuMa.
So there you have it... a 'brief' insight into a few days of WM5 experience, personally I'm going to stay with Logout's ROM, the speed is unsurpassed, it has ample space for installs, I get my CallerID due to P&V working, and if there's one thing about TuMa's ROM I could do without it's the 'free' installed apps... I don't use TtlCmd, I don't use Pocket FTP and I don't use Pocket RAR (Resco Explorer covers those 3 and then some), I use Tweaks2k2 to apply most of my hacks, so the GB-Soft Tweak is mostly redundant, and I use Wisbar instead of vBar... but it's a personal preference thing... in the end, it's up to you... (I now use Total Commander loads Thx TuMa)
I'll update this as I try other ROM's or find other benefits/problems/fixes...
*** See my other post in this thread dated 23/06/06 for other issues which I have come across with WM5...***
Logout 5.4.05
I had high hopes for this ROM, 5.4.03 was nearly there, and built on the best of TuMa and Ivan's ROM's...
Out of the Box
An incredibly fast ROM, by far the fastest in basic form compared to all the others available... there are many little tweaks in the software and add-ons included as standard which are useful, such as the SMS Alert Fix etc. It's up to you to make the Ext_ROM, but this is good for 'tweakers' as you can build it to your liking.
BT: Basically, a nightmare! I believe this uses the WidComm stack and as such I can't get the A2DP to work, yes it recognises my Headset, and yes it says there is a 'Wireless Stereo' capability, but when you try to enable that profile it says 'No Device Found'... in addition, and I'm not sure if this is due to the BT switching off fix, my device was switching on at least once every two minutes!!
WiFi: I didn't get round to test this for the reason above, and also the power up issue causing me major headaches.
Issues: I had too many issues with this ROM to detail them all, a short list would be:
No A2DP
Random Power Ons
Software Not Installing Correctly
Software Not Removing Correctly
Software Not Running (Tweaks2K2, WiFiFoFum and others)
BT Dropping Out (While Powered Up)
OS Locks Out (Random, No Common Factor)
And the speed once a few 'heavy' apps are installed deteriorates dramatically...
I have now resorted to TuMa 1.4... I know I have stated previously that I couldn't use it, but I have found a workaround to the Caller ID issue, and the BT works very well (including A2DP), with both 1.13 and 1.15 Radio ROM's, and I have not experienced one unwanted power up, and the BT has stayed on for ages regardless, in addition as long as I don't install WisBar the speed of this ROM beats all the others hands down once all my other apps are loaded. Also, I have had the BA on for 7 hours now, using bluetooth for 1 hour solid in the gym for music, making several calls, setting up my software etc and the battery is still at 75%... not bad at all in my books.
As I said earlier, bring on TuMa 1.5!
Now this is useful! Thanks for sharing and I give my thumbs up for updating the first post as you go on trying.
I'm very happy to read your review.
I'm surprised you did not mention the battery drain (false indications that your battery is dead, when in fact it is not) with TuMa 1.4
Great Work!!!!
G8 work. Good detailed description which i am sure a lot of people will appreciate. i
Logout Rom = Speaker phone icon does not disappear after call
WMP 10 crackling noise for first 30 -60 sec of song
@snapper - Can't say I noticed it, but then again, whenever I sit down for more than 30mins, my brick goes on to power anyhow...
Why does everybody forget about ArtZ's ROM? :/
http://forum.xda-developers.com/viewtopic.php?t=48215
Not forgotten, just not used,,,
If you read the last couple of para's I do state that I'll get round to Artz's and update the post...
Yup, missed that (was in hurry, checked only the explicitly enumerated ROMs :| )
The Artz of ROM's
Hmm, d/l'ing this one now... expect an update over the next day ot two... encountered a few 'glitches' with the Logout ROM tday, nothing too major, but enough to get my goat!
Is there any reason why, with certain ROM's, certain apps decide my BA is a VGA device? This has cased me no end of trouble today, and I can't for the life of me, work out the reason...
Anyway, expecting good things from the Artz ROM, just read the forum a few mins ago and notice it's a 'clean' ROM with the BT stack! Could be I get my wishlist... let's just see if P&V works...
Mad props for a very well written article.
I've gone down the wm5 road the last week as well. I tried tuma 1.3, tuma 1.4, ivan, and now i'm on logout. I was wondering how extensively you tested the wifi? I have had problems with it on all the roms.
The issue happens when wifi is ON and the device shuts off after 1 minute. Then the device powers back up when i press the power button and the wifi will continually try to reconnect to the AP that it was just on but will never make a connection. Clearing the settings on the connection doesn't work and it inhibits the ability of the device to detect any new networks.
I was wondering if you had any problems like this and if resetonresume fixes this?
Also i'm a little confused about the location of the storage memory and the programs memory in the file structure of wm5. Could someone explain this or send me in the right direction? (aka. search terms or thread link)
willpower102 said:
Mad props for a very well written article.
I've gone down the wm5 road the last week as well. I tried tuma 1.3, tuma 1.4, ivan, and now i'm on logout. I was wondering how extensively you tested the wifi? I have had problems with it on all the roms.
The issue happens when wifi is ON and the device shuts off after 1 minute. Then the device powers back up when i press the power button and the wifi will continually try to reconnect to the AP that it was just on but will never make a connection. Clearing the settings on the connection doesn't work and it inhibits the ability of the device to detect any new networks.
I was wondering if you had any problems like this and if resetonresume fixes this?
Also i'm a little confused about the location of the storage memory and the programs memory in the file structure of wm5. Could someone explain this or send me in the right direction? (aka. search terms or thread link)
Click to expand...
Click to collapse
I had this problem on my BA with 03se just a couple days ago so I don't think its related to just 05. I used the vx ip utility to release and renew the IP and I believe that fixed it.. I think it has something to do with the DHCP reservation
Great guide, very handy for begginers. Should be sticked :idea:
willpower102 said:
Mad props for a very well written article.
I've gone down the wm5 road the last week as well. I tried tuma 1.3, tuma 1.4, ivan, and now i'm on logout. I was wondering how extensively you tested the wifi? I have had problems with it on all the roms.
Click to expand...
Click to collapse
Using wifi on my BA for over a wk everyday @ work & home, no such problems faced with Ivans ROM, have not tested logout, but will do that this wkend.
Guess its a hardware issue! again, thats just a guess
Yaantra
Great info!
This is great info and was very useful to me. I am on WM2003 and have not yet upgraded. With 2003, my only issues are that MS voice command won't work via the BT headset, the 80211b wireless requires a reboot to turn on and off, and the phone requires a reboot perhaps once a week. Otherwise it works well and I want my 2005 to be equal or better. I thin TuMA 1.5 will be it.
Has anyone actually got a working MMS Client primarily for Logout's new ROM
WiFi Issues...
@ will...
Yes, I noticed on first flashing that, even though I had entered the settings for my AP, when the system resumed then it would not reconect, after using the resetonresume reg hack all was well...
I also noticed this on Artz's ROM which I will be adding to my first post over the next day or two, as well as a few other points/comparisons...
All I will say at the moment is that all has not been a bed of roses in my WM5 world and backward steps may be ahead... (unless Logout 5.4.0.5 or TuMa 1.5 are here soon... and they deliver on our expectations!!)
Tuma / Logout roms
sounds to me that you will be heading back to wm2003. main reason for saying this is how you use your pda. Your demands are high (as they should be) and you use your pda very heavily (wifi, bluetooth etc) hence functionality and speed are your highest priorities.
having said all this i think and hope tuma/logouts new roms will hit the spot (i have faith).
FYI just upgraded to 1.15 radio and the sound quality is good!!!!!!
Issues, concerns and resolutions...
Well, the first post will be updated later today, but just as a heads up, I experienced BT issues with all ROM's except the TuMa 1.4, and various other 'niggles'... issues which I couldn't live with unfortunately:
BT: I like the A2DP functionality, I use GPS heavily and need them to work every time, with the other 3 ROM's I've tried I experienced various problems such as BT not reconnecting to paired devices, BT connecting but causing mayhem with my headset (in Artz' update later), crackly sound, dropouts, no phone, no voice dial, ad infinitum...
WiFi: This worked fairly well in all the ROMs, I managed to get all 4 tested to reconnect after standby/soft reset/battery change etc.
Battery: The experiences I had with battery life weren't actually that bad, yes it was heavier than 2003SE, but that's to be expected... my main issue was that on a couple of the ROM's I experienced the 'no Radio ROM' syndrome after a battery change, not major, but a pain in the butt anyway!
Usage: These are all ROM's that are designed for 'newer' machines at their hearts, and as such, as soon as you load up some heavy apps the whole system starts to drag, I cannot afford to wait over 1 minute for my PDA to boot after soft reset, or 30 secs for an app to open... and I certainly don't like it to be 'hit or miss' if an app opens when I ask it to!
Summary: I really love the WM5 interface, the smoother way that notifications are dealt with, the 'soft-menu' buttons are a godsend, the built in GPS management, and any of the other 'tweaks' MS have included make it a PDA users dream, unfortunately, at the moment it's just that, a dream... the BA is not 'Designed for Windows Mobile 5' and until TuMa, Logout, or Artz [I believe Ivan has left for a new device ] manage to get it 'right' (and major kudos to them all for their perseverence in what must be a most frustrating endeavour) I, as an everyday, heavy, PDA user will remain with WM2003SE... I'm not happy about it, but needs must
Re: Issues, concerns and resolutions...
spkr4thdd said:
Usage: These are all ROM's that are designed for 'newer' machines at their hearts
Click to expand...
Click to collapse
Just FYI that is incorrect, Artz and Ivan's ROMS are based on an actual BA BEAT build of WM5 that was made by microsoft, that has been patched and edited with later versions of the components, whereas TuMa and Logout's Rom are based on a Wizard ROM.
spkr4thdd said:
the BA is not 'Designed for Windows Mobile 5'
Click to expand...
Click to collapse
Read up, Basically every WM2003SE device has a WM5 Version made for it, however the operators in thier infinate wisdom decided that they didnt want people having WM5 on thier 'old' phones and would rather that people brought new ones.
Re: Issues, concerns and resolutions...
Midget_1990 said:
Just FYI that is incorrect, Artz and Ivan's ROMS are based on an actual BA BEAT build of WM5 that was made by microsoft, that has been patched and edited with later versions of the components, whereas TuMa and Logout's Rom are based on a Wizard ROM.
Click to expand...
Click to collapse
I stand corrected... I was under the impression that all the ROM's were 'ported' from different devices, I believe that was the case originally wasn't it?
Midget_1990 said:
Read up, Basically every WM2003SE device has a WM5 Version made for it, however the operators in thier infinate wisdom decided that they didnt want people having WM5 on thier 'old' phones and would rather that people brought new ones.
Click to expand...
Click to collapse
Read my post!! WM5 wasn't released when the BA came out, so it was built around WM2003SE, the fact that a ROM became available, albeit not publicly, doesn't mean they redesigned the handset!
SYMPTOM:
Hi,
After I upgraded to Dutty's V4 and then later on to DCS's V1.5 (both are great ROMs by the way), I am having difficulties using iNavigator (iGuidance) on my Tilt.
Symptom:
When I start driving, the location on the map does not update as I go. It ONLY updates the second that it enters full screen or exits from full screen (i.e. I click on the screen when it's in full screen mode).
The COM port is set to COM4 and Baudrate is 57600. Is it because iNavigator is not fully compatible with this ROM or radio?
BR...
Click to expand...
Click to collapse
SOLUTION:
http://forum.xda-developers.com/showpost.php?p=2114969&postcount=25
http://forum.xda-developers.com/showpost.php?p=2120352&postcount=35
http://forum.xda-developers.com/showpost.php?p=2114969&postcount=40
Click to expand...
Click to collapse
I had this as well with Sleuth's v3 (WM6.1) rom as well, I went back to Sleuth's v1.2 (WM6) and all is good again with iGuidance.
vip_snoopy said:
Hi,
After I upgraded to Dutty's V4 and then later on to DCS's V1.5 (both are great ROMs by the way), I am having difficulties using iNavigator (iGuidance) on my Tilt.
Symptom:
When I start driving, the location on the map does not update as I go. It ONLY updates the second that it enters full screen or exits from full screen (i.e. I click on the screen when it's in full screen mode).
The COM port is set to COM4 and Baudrate is 57600. Is it because iNavigator is not fully compatible with this ROM or radio?
BR...
Click to expand...
Click to collapse
My Tilt with DCS's 1.5 cannot run iGuidance 4 totally.
vip_snoopy said:
Hi,
After I upgraded to Dutty's V4 and then later on to DCS's V1.5 (both are great ROMs by the way), I am having difficulties using iNavigator (iGuidance) on my Tilt.
Symptom:
When I start driving, the location on the map does not update as I go. It ONLY updates the second that it enters full screen or exits from full screen (i.e. I click on the screen when it's in full screen mode).
The COM port is set to COM4 and Baudrate is 57600. Is it because iNavigator is not fully compatible with this ROM or radio?
BR...
Click to expand...
Click to collapse
Try baud rate at 4800. See if that helps.
I think v4 is far inferior to v3. I have both and v4 is uninstalled. No map generation and compatibility problems.
J
I've found v4 to be OK on Hermes and Kaiser with WM6.0. I've played with baud and it doesn't matter, from 4800-38400 same refresh rate seen.
so, set it to 4800? will try tomorrow when I drive
vip_snoopy:
Don't bother. It won't help. It has something to do with the internal GPS on the Kaiser and WM 6.1 that iGuidance 4 doesn't like. I had the same issue as you (and others). As a test, I paired my bluetooth GPS to the phone and iG4 worked great.
However, other GPS based software (ie Live Search) works fine in WM 6.1.
I cooked my own ROM from Alex's 3.02 package...
shadee
slimshadee said:
vip_snoopy:
Don't bother. It won't help. It has something to do with the internal GPS on the Kaiser and WM 6.1 that iGuidance 4 doesn't like. I had the same issue as you (and others). As a test, I paired my bluetooth GPS to the phone and iG4 worked great.
However, other GPS based software (ie Live Search) works fine in WM 6.1.
I cooked my own ROM from Alex's 3.02 package...
shadee
Click to expand...
Click to collapse
so you said you cooked your own ROM from Alex's 3.02 package, is that WM6.1? could you provide some more details about it?
Yes. 3.02.405.0 ROM base (WM 6.1). It is Alex's v5 Kitchen.
I just got iG4, so I never tested it with any of the ROMS I cooked from WM 6.0. I did however, use iG3.01 sucessfully on all of those WM6.0 ROMs.
I was fortunate to have a bluetooth GPS from my old Hermes and Wizard PPC's, and used it to confirm the problem with iG4 / WM6.1 (3.02 ROM) was related to the internal GPS on the Tilt / Kaiser. iG4 works like a champ with the BT GPS, but craps out constantly when using the built-in GPS.
IMO, the built-in GPS is significantly inferior to a paired BT GPS.
And, BTW, iG4 is slower than iG3.01, probably because of the added POI's and the fact the entire map must be loaded on your storage card. I really miss the maploader program from version 3.
Get a BT GPS and enjoy iG4...it's still the best nav software in my book.
shadee
My two cents worth... I have Handymap (South African Version of Papago) and it also was very sluggish, used to update every 300m or so when going at 100kmph. I complained to the vendor, and since then they have released a cab install specifically for the Tytn II.
So it seems to me that the way the internal GPS chats to the software is different than the way an external BT GPS does.
Just to get this thread back on track and see if anyone can help us find a solution. I am also having the same issues that you describe with iGuidance 4. I am able to get a satellite lock quickly, but while driving, the map does not refresh or update unless you tap the screen. The interesting thing about this problem is that the same version iGuidance works incredibly when using a WM6 rom. This problem only occurs when using WM6.1. Additionally, using the 6.1 rom only seems to impact iGuidance and not TomTom.
I did some research on other devices and saw that some people had success using Franson GPSGate, but I am looking for a solution that doesn't require it as it was not required in wm6.
Please do not turn this thread into a debate over which gps application is better or which version of iGuidance is better. Any suggestions as to what may solve this issue would be appreciated.
I found two issued with iG4 and WM6.1
1 - the map gets a fix but doesn't update unless the screen is touched
2 - the TTS in iG4 uses "canned" speech for most commands, and TTS to just say the street names. With 6.1, the TTS engine seems disabled as well.
3 - Just an FYI, there is a reg setting to force iG4 to only use canned speech like the previous versions like iG3 which does speed up the prog. You can also force full TTS which slows the prog more, so the current hi-brid method is a performance balance.
If GPS Gate fixes this, I'd be OK with that for now till a better fix comes along. Anyone have solid information about this? I'm on Sleuth's v1.2 WM6 rom till then, which is a solid rom, snappier than the stock Kaiser which was very good.
My experience with tech support with iNav will be that they will deny the existance of WM6.1 and any issues, then fix it in the next release. That's what they've done year over year. But I still love the prog.
slimshadee said:
Yes. 3.02.405.0 ROM base (WM 6.1). It is Alex's v5 Kitchen.
I just got iG4, so I never tested it with any of the ROMS I cooked from WM 6.0. I did however, use iG3.01 sucessfully on all of those WM6.0 ROMs.
I was fortunate to have a bluetooth GPS from my old Hermes and Wizard PPC's, and used it to confirm the problem with iG4 / WM6.1 (3.02 ROM) was related to the internal GPS on the Tilt / Kaiser. iG4 works like a champ with the BT GPS, but craps out constantly when using the built-in GPS.
IMO, the built-in GPS is significantly inferior to a paired BT GPS.
And, BTW, iG4 is slower than iG3.01, probably because of the added POI's and the fact the entire map must be loaded on your storage card. I really miss the maploader program from version 3.
Get a BT GPS and enjoy iG4...it's still the best nav software in my book.
shadee
Click to expand...
Click to collapse
well, although I do have a BT GPS, I'm just lazy to carry another one around since I have an "Internal GPS" for the Tilt. So for the meantime I'll be using TomTom until someone figures how it works out. - Hopefully by then iGuidance 5 will be out
I have seen this as an issue as well...But i actually saw it in one of Dutty's WM6.0 ROMs. I then updated to Schaps 6.0 rom and the problem went away. I've since installed only one WM6.1 rom, the udK 7.0 R1 Vega - WWE | WM6.1 CE OS 5.2.19199 (Build 19199.1.0.0). I was going to try a different rom, but i'm not sure that it will solve my issue after reading this thread.
Rom Doesn't Matter
I've had this exact problem ever since the first cooked WM6.1 ROMs have been made available. I have tried every radio and almost every WM6.1 ROM and all have the exact same problem as mentioned in this thread.
But a Bluetooth GPS reciever does work so I'm just going to go with that for now since I only use GPS in my car anyway.
Also I registered my program with iNav and there are no updates to the software yet. opefully when there is it will fix the problem.
temporary work around
Ok, I've given up searching for now and believe that the only solution is to use GPSGate as discussed in this post
http://forum.xda-developers.com/showpost.php?p=1862272&postcount=4
GPSGate is not free, but there are alternatives to it out there that haven't been tested yet. I did download the trial of GPSGate and can verify that it does work. It's not too expensive either for just the ppc license.
To use the mortscript script that is discussed in this thread, you do also need to download AstroGPSLauncher which can be found here:
http://forum.xda-developers.com/showpost.php?p=1870976&postcount=1
It seems as if we are stuck with this until iGuidance can resolve it. The more users that contact them, the better chance we have of getting a fix. However since 6.1 isn't officially released yet, they will more than likely deny the issue.
Heres what iNav support had to say in response to my e-mail
I don't think any of these options will fix the 6.1 compatibility issue...what do you all think?
MY SUPPORT REQUEST...
Hello,
I have Windows Mobile 6.1 on my AT&T Tilt Pocket PC. iGuidance recognizes my internal GPS, but does not automatically refresh the screen. I have to zoom in/out or change something with the screen to get it to refresh. Do you know how I can fix this problem?
THEIR RESPONSE...
There are several possibilities:
1) GPS connection issue : the program is not connected to your GPS and thus unable to update your current position. If it's connected, the arrow/cursor in iGuidance map screen should be in yellow or green. And when you click on view > gpsinfo, you should see the screen w/ NMEA data being updated continuously. If the cursor continues to stay at grey color, this means iGuidance has not been connected to your GPS. If the cursor is red, then this means it has found your GPS but is in the process of locking and searching for satellite signals. The GPS connection indicator information can be found under Section IX step #6 of the iGuidance Installation Guide, and the step-by-step instruction on how to configure and connect iGuidance to your GPS is available under Section VIII step #4 of your iGuidance Installation Guide.
2) Normal program operation: whenever you've just entered an address and click on "nav", the program will automatically enable panning mode. You will need to click on the "X" button at the lower right hand corner to exit the panning mode to see the screen refresh. If you don't manually exit, it will self auto-exit after 40-45 seconds. So if you didn't know how to operate the program and didn't wait for 40-45 seconds, it's likely you will think that the screen is not updating.
3) Program installation: it is also possible that some files were corrupted during installation. You might want to following the uninstall/reinstall instruction in Section II of your iGuidance Installation Guide and reinstall the PPC version.
Tilt is the most popular pocket pc phone used by our customers, so there's no compatibility issue w/ the hardware nor the internal GPS. Most likely, scenario #2 or 3 is the problem.
Has anyone figured out how to get iGuidance 4.0 to work on Windows Mobile 6.1 without spending more money? I know about the GPS Gate trick, but would rather not spend another $20 when iGuidance worked flawlessly by itself on WM6.0.
afgoody said:
Has anyone figured out how to get iGuidance 4.0 to work on Windows Mobile 6.1 without spending more money? I know about the GPS Gate trick, but would rather not spend another $20 when iGuidance worked flawlessly by itself on WM6.0.
Click to expand...
Click to collapse
If you click on my link from two posts above, you'll see that they mention a free alternative called GPSProxy
My friend and I both have Tilts running the following:
HardSPL 3.56
Death V4.1
Radio 1.58.16.24
The only difference between the two phones, is that I used the cab widely available here for TomTom and he bought a full fledged copy on DVD.
When I go to use my phone for navigation everything is choppy like so many others, but he showed me a route demo and it's smooth as the Magician in the htcclassaction.org demonstration video. I can't figure out how it's so smooth though. He's not using the "D3D drivers", either, so I'm at a loss.
His TomTom is 6.01 with 6.01 USA and Canada
Any ideas as to why / how TomTom got around the choppyness of DirectDraw?
Nothing at all?
I think this could be very important for DirectDraw and 2D acceleration if someone could figure this out
What I found when running TomTom on my Tytn II is that if you disable all the POIs from showing on the map while you are navigating then the software runs very smoothly.
If you use any speed cam warnings etc these still show up on the map as you navigate but it has no impact on the speed etc.
Let me know how that works.
Paul.
What about differences in the speeds of the SD cards? What do you have and what does he have? There have been reports that the 4GB and higher capacity cards cause Tom Tom to run slow.
how is it laggy?
Err...could this be the old Windoze analogy???
Increase of version = extra stuff to do???
Like early version just drew maps,,,new version waits for you to talk to it, checks traffic draws more items and still wants to work on same memory and processor???
you disable all the POIs from showing on the map while you are navigating then the software runs very smoothly.
Click to expand...
Click to collapse
I'm sure glad to have seen this post. I've posted on 2-3 different forums, including teh TomTom support forum here; I've Called TomTom support...all to no avail.
This fixed my problem.
how is it laggy?
Click to expand...
Click to collapse
Go in and check a dozen or so POIs to display while driving, and I suspect you'll find out. Map was jerky; I could make a turn, and be a half block down the road before it know I had turned.
I have an 8GB Sandisk MicroSDHC card and he has a 4GB Sandisk MicroSD card. I'm going to try disabling POIs, but I don't think that's it.
NerdsMcGee said:
I have an 8GB Sandisk MicroSDHC card and he has a 4GB Sandisk MicroSD card. I'm going to try disabling POIs, but I don't think that's it.
Click to expand...
Click to collapse
Disabling POIs sped up TomTom IMMENSELY. Thanks for the info.
NerdsMcGee said:
Disabling POIs sped up TomTom IMMENSELY. Thanks for the info.
Click to expand...
Click to collapse
You're welcome.
I have a 4gb micro sd card and the speed has nothing to do with the size or speed of the card.
I wonder if the video of the 2 machines on the class action lawsuit website had the Tytn II displaying all the POIs.
I think they would be a bit embarrassed if that turns out to be the case
I think the problem is just TomToms laggy software rather than the PDA
Paul.
firstandlast said:
You're welcome.
I have a 4gb micro sd card and the speed has nothing to do with the size or speed of the card.
I wonder if the video of the 2 machines on the class action lawsuit website had the Tytn II displaying all the POIs.
I think they would be a bit embarrassed if that turns out to be the case
I think the problem is just TomToms laggy software rather than the PDA
Paul.
Click to expand...
Click to collapse
I wouldn't be surprised. TomTom has always been smooth and lag-free for me, even with the stock HTC shipped ROM.
I forget which versions I've used, but I think it was:
6.02?
6.030 (or 6.032? I can't remember)
7.450 (the latest TTN7)
Well, at least video is smooth. I had sound issues with 6.030/32 and TTN7 that did not occur with the first version I used.
As you can see by my current sig (although soon to change) I'm using the latest HTC WM 6.1 ROM and 1.65.17.56 Radio with the correct 3.28.0000 SPL and I get very laggy GPS performance full-stop. It's not necessarily jerky (although on occasion where lots of movement such as going around a roundabout occurs, it can be) but it is very laggy. By this I mean I can be sitting in the train stationary and from the train starting to move and Tomtom Navigator actually registering movement/speed, it can take up to 25 seconds - and this is with a reasonable signal reception averaging 3 or more bars the whole time. I put this down to the actual GPS perfomance of the Radio module driver. Tomtoms call centre in the UK advised me that TTN Version 6.032 (the HTC official version) isn't actually supported under WM 6.1, only the original WM 6.0 O/S so guess what's happening to my TyTN II later this week at the HTC repair centre.... I'll be so pleased not to have to put up with rubbish GPS performance anymore. Next time I'll only upgrade to WM 6.1 once I get the all clear that they've fixed their WM 6.1 ROM/Radio combination.
Oh and I have tried TT 6.10 when Tomtom were first attempting to work out why their software was playing up after the WM 6.1 upgrade (they provided me with a free 'crossgrade' for faultfinding purposes) and I fould in terms of smoothness, it was identical to 6.032. I went back to 6.032 because 6.10 didn't have fully working customised things like jog button volume control, volume change screen indication and native inbuilt 'internal' GPS setting. The start menu also misbehaved or the physical Windows button on the phone wouldn't work properly when TTN was running, something like that - altogether not as 'Kaiser friendly'.
NerdsMcGee said:
Disabling POIs sped up TomTom IMMENSELY. Thanks for the info.
Click to expand...
Click to collapse
Perhaps this works with Navigon, too. Gonna try that later
I am using TTN 6.032 on the latest WM 6.1 with a maximum of POIs enabled and it runs smoothly.
I've tried a version lower than 6.032, and based on my personal experience it didn't really make a difference. As long as you turn off the POI the TT will run like crazy, and plus the lower version is not as user friendly as the 6.032, or even better V.7, that's if V.7 will accept the maps from V.6, just my 2 cents.
Flying Kiwi said:
As you can see by my current sig (although soon to change) I'm using the latest HTC WM 6.1 ROM and 1.65.17.56 Radio with the correct 3.28.0000 SPL and I get very laggy GPS performance full-stop. It's not necessarily jerky (although on occasion where lots of movement such as going around a roundabout occurs, it can be) but it is very laggy. By this I mean I can be sitting in the train stationary and from the train starting to move and Tomtom Navigator actually registering movement/speed, it can take up to 25 seconds - and this is with a reasonable signal reception averaging 3 or more bars the whole time. I put this down to the actual GPS perfomance of the Radio module driver. Tomtoms call centre in the UK advised me that TTN Version 6.032 (the HTC official version) isn't actually supported under WM 6.1, only the original WM 6.0 O/S so guess what's happening to my TyTN II later this week at the HTC repair centre.... I'll be so pleased not to have to put up with rubbish GPS performance anymore. Next time I'll only upgrade to WM 6.1 once I get the all clear that they've fixed their WM 6.1 ROM/Radio combination.
Oh and I have tried TT 6.10 when Tomtom were first attempting to work out why their software was playing up after the WM 6.1 upgrade (they provided me with a free 'crossgrade' for faultfinding purposes) and I fould in terms of smoothness, it was identical to 6.032. I went back to 6.032 because 6.10 didn't have fully working customised things like jog button volume control, volume change screen indication and native inbuilt 'internal' GPS setting. The start menu also misbehaved or the physical Windows button on the phone wouldn't work properly when TTN was running, something like that - altogether not as 'Kaiser friendly'.
Click to expand...
Click to collapse
Google "static navigation". The oddball performance at low speeds (such as lag from a stop) is not TomTom's fault. It's a setting in the GPS receiver that (unfortunately) can't be disabled on the Kaiser.
I have an x1i running windows mobile 6.5 Energy rom (build 2308.1.5.30)
and it contains radio 1.14.25.55.
I bought it this way, but the problem is that the GPS sensor does not work. I have tried the usual programs to activate it, but no signal whatsoever in any of the programs (Chart CrossGPS test, GPS scanner, GPS reset, HTC GPSTool). Is the ROM or radio incompatible with the GPS hardware? Or is there a way to test if the hardware itself is not working.
I like the phone a lot (now), even though I am a Mac person. Flashing a new ROM would be a big deal with a Mac. Plus I have set up the phone very nicely now. Hoping for an easy way out. GPS is not a huge deal for me but it keeps nagging.
check control panel setting: let windows managed automatically enable
check registry: \HKLM\System\CurrentControlSet\GPS Intermediate Driver\
isenable : 1.
check if using gpsmod driver : com4 enable.
hope thats help.
In the external GPS control panel, I enable the Manage GPS automatically
Also the settings on the registry is as you recommended
I do not have gpsmod.
so far no luck
You can flash a new radio and will be able to keep your settings, contacts, messages, etc. If you have trouble flashing with a Mac, you can easily flash via SD.
Try out the different radios available here in XDA. I went from 1.14 to 1.16 a year ago, got a HUGE boost in reception and battery life, but had to flash to the unofficial 1.17 since GPS did not work in 1.16 for me.
Thanks, I will try this.
Tried the radio 1.17. Flashing is indeed straightforward via SD card. Unfortunately the GPS did not work. I then changed the whole system by flashing the 826x series rom, as recommended here recently in the Q and A section. Great ROM, even better than the one I used. Still no GPS, so I concluded that it is a hardware issue. Then used an external GPS and finally got it to work after changing some registry data, because the 'external gps' settings on the phone would not save a com port for the external device, as others had also experienced. Used the two links below and finally deduced a solution from that as written below the links. (I could not use the exact solution from the link, since the registry item referring to the external device was named differently) Freedom Keychain GPS 2000 is the external device I use, really cheap (19 euro) and lasts up to 10 hours and is really small (considering the battery use of X1 not a bad solution).
the links:
sorry as new user I am not allowed to post the links
the changes in the registry:
1. [HKLM\System\CurrentControlSet\GPS Intermediate Driver\Drivers]
"CurrentDriver"=" GPSOnePort
2. [HKLM\System\CurrentControlSet\GPS Intermediate Driver\Drivers\GPSOnePort]
"CommPort"="COMX:" where X = the hardware COM port (for me COM0)
"InterfaceType"="COMM"