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
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
Hello,
I am trying since yesterday to make my GPS working, with no success. Everytime, I got the following message:
Cannot find port com. I do not know what the problem might be. I tried all Ports (from COM 0 to COM 12, and all Baud rates). Tried 3 differents GPS applications. Memory Map tells me for Port 0 GPS communication timeout...
In addition, I tried to play with the External GPS. I tried with Manage GPS automatically on and off. Still the same..
I begin to think my GPS unit is defective...
Any ideas would be appreciate.
Thanks very much in advance,
Philippe
did you change settings in the gps control panel?
the default settings can be left alone. COM4. Baud rate should be automatically handled and unless you enabled AGPS any baud rate will do, if you enabled AGPS then I think you have to use 2400 as your Baud.
I just noticed the GPS harddware port in setting, system External GPS is not saved when you click ente.
Exemple I choose COM4, and Baud rate: 4800. I click OK. When I reclick exernal GPS, Hardware, I have got ''none for GPS hardware port. I do not know if it might be one of the reason why the GPS does not work.
Note: I just flashed the new rom: 1.35.401.3 WWE. Might it be a bug in this ROM (just question?)
Philippe
I can cofirm TomTom working with COM4 and baud 57600. Signal pickup can be time hungry, tho. Sometimes I get a fix in 20 seconds, sometimes it takes as much as 10 minutes.
no problem using mapking...
Hello,
And thanks everybody for your help. I just updated to the new Elite 1 ROM, and now it works like a charm....Very good...
I do not know if there is many francophones on this forum, but there is a new french forum about the Diamond:
http://htc-touch-diamond.forumactif.info/index.htm
Not very busy yet, but....
Cheers,
Philippe
Same problem... The tomtom 6 don't detect my integrated gps... if i chose the wired and put ports like say before, it don't work too.. Any way for detect integrated gps?
Here are exactly my setting:
Setting system External GPS:
GPS program port: COM 4
GPS hardware port: None
Baud rate: 4800
Manage GPS automatically is checked.
So open your GPS program, choose COM Port 4, and baud rate: 4800.
Should work. If not, flashthe new Elite ROM. It could help too.
Philippe
I can't flash the rom, it will make the warranty expire... And the mobile isn't mine, it's destined to be selled, i work on a gsm shop...
got exactly opposite problem - when I leave these default settings in "External GPS" CPL, the Diamond will suck my batterry within several hours, as if the GPS was still ON. have found out that if I disable all settings in this CPL, it stops sucking power (but then I can't use the GPS, obviously) - any clues or solutions?
I HAD to enable Windows Mobile manages automatic in External GPS in 'settings'. Check if it is enabled.
Disabling it made GPS never work.
Strange?
Yes, unless I restored all settings to their original values (Virtual port - COM4, HW port - None, Managed access - checked), I was not able to use the GPS. But these were exactly the settings I was having the battery drain issue with... I miss the GPS LED indication vastly...
I am have this problerm too...
Solution : make hard reset.. no more!
And all will be ok ... about GPS.
i have same proplem
i have same proplem when i updat to the new rom 1.93
I have a similar Problem.
I Updates my ROM to the new branded one from O2-Germany and since then my GPS is not working anymore. in GPSMapware I get device.exe errors and TomTom7 keeps searching and searching and so on...
The old O2 ROM has no GPS problems and every software got a loc in about 10 - 20 seconds.
But the most intresting point is that my brother has a Diamond too and no GPS problems at all.
I think I will get a new one from O2 before flashing it and loose my warrenty
Telus CDMA Diamond
I've got problem too. First Diamond I had no problem with GPS, something happened with the phone I had to exchange, and new one (phone) GPS wouldn't pickup Sat. I'm on Telus CDMA. Maybe they removed physically on the second batch of Diamonds.
My GPS doesn't work too well either. I can usually get a fix eventually when outside with a clear view of the sky but in the car it is hopeless. I use TT7 and the GPS status screen shows that the Diamond can see maybe half a dozen satellites or so but with very low signal strength. The bars stay grey for ages and then eventually three or four will turn blue and all the time the battery is draining like crazy. I also have a Holux GPSlim 256 and with that I get a fix much faster and the signal strength is much higher. I can also use it in the car with no problem.
I have to say I'm pretty disappointed with the GPS performance of the Diamond and from the number of posts in this forum from people with similar problems I would suggest that there is a design flaw or very poor quality control. I had an XDA Orbit 2 for a while and that was far superior.
Me too
my diamond have the same problem too.
it was working with the old rom's and the early new
but later with new rom's it is locked, I don't know why or how to fix it.
then I back to the last good one but still locked.
it seem's working fine, because the software is detect the gps device and also detect it on port 4 and baud speed, but without signal any more.
I used Garmin, Destenator, iGo, fanaeen, and gps test.
and I try to use all avaliable solutions
I used all diamond rom's here and used all radio version's even the hardspl I changed it too with no succeed.
any advice would be help!
thanks in advanced
Hi,
I own two diamonds and I also found problems with the GPS in both of them. Probably mine is not the same you are describing. What I get is the following:
Running TT7, the GPS works but TT7 map in the screen remains in grey color. Rarely it shows color for some seconds and l"oses signal" again. It navigates, but no messages on proximity of POIs work. Also, when driving, if TT7 is forced to recalculate (every time I do not follow the instructions), it forgets about the required destination. In the GPS configuration option within TT7 it does not show satellites, the bars are empty and the coordinates shown are grey... but showing values!
Finally, I found the reason. I use Bluefire VPN, a piece of software to connect securely to my company. The GPS and Bluefire cannot live together.
I have tried everything: TomTom 6, changing COM port (many combinations)for the GPS, A-GPS on and off... No way.
It worked perfectly in P3600. I tried many ROMS and pieces of software without problems but in the Diamond I haven't been able.
Perhaps the reason is some resident code of Bluefire. Don't know. In any case, if this is a case similar to any of you, my advice is the following:
Hard reset, install TT7 and maps and test the GPS. If it works, start installing software until it crashes.
In my case, the GPS is always dead after the soft reset required after the installation of Bluefire, and it works again after another soft reset once Bluefire is uninstalled.
Hope it helps and hope somebody can also help me solve this issue.
SOLVED
Hi guys
Here is my solution.
First you have to flash 1.13.25.24 radio rom sometimes it can be solve the problem.If not you must open your phone with Htc service manual and find gps coaxial cable and check it.Sometimes it can be pulled out.Mine antenna was unconnected and gps couldnot find any satellites.Sorry for my bad english.
Since I bought my Diamond, last week, I haven't been able to get a single fix.
Even worse, although my GPS is detected as running by every GPS soft, there is only one sattelit bar active at a time.
(about 10 satelits are being sensed, but only one is actually sending datas to my device, every time...)
I've never expericenced such problems with my preivous triny. There were always at least 3 or more bars moving up and down at a time, and at the end I could get some fix.
- either it is a hardware problem and I got a crap GPS chipset...
- or it is a setting problem with my ROM.
By the way, in the External GPS settings screen, I have strange infos:
Port GPS: com4 which is normal, GPS Material Port: None!!
baud rate: 4800 (which I think is very low, but I heard everybody has got the same)
What's wrong with my device?
Seems to be lots of posts on this issue...a nice simple one is to flash a new radio.....if that doesn't work do a Hard Reset (to be sure!) and restore to minimum and see if it runs.....then move on from there....
I've been having a similar problem with my Raphael (it takes a million, billion years to get a lock and even then it's only 3 satellites).
I deleted the 2 GPSlog files in the Windows folder, did a soft reset, ran QuickGPS and then tried Google Maps again. I got a lock in about 10 seconds with 8 satellites.
Now, I've only been able to test it once and will have a go again tomorrow but it's easier than a radio flash or hard reset!
Harry
Thanks for the replies!
- I've been doing many hard resets these days, due to some problems with Asian Fonts. So, this is not the problem.
I may go for the radio flashing as u suggest.
By the way, I've noticed you're using the x.x.8 radio, are you satisfied with it? I read many are going back to x.x.5 cause they it has poor performances.
-The GPS log files sounds good. I've never tried this but I may give it a try.
I tried to reset the GPS logs from within the soft I was using, but it did not improve anything, looks like the GPS only receives the list of satelits, but no localisation datas at all...
riri22 said:
Thanks for the replies!
- I've been doing many hard resets these days, due to some problems with Asian Fonts. So, this is not the problem.
I may go for the radio flashing as u suggest.
By the way, I've noticed you're using the x.x.8 radio, are you satisfied with it? I read many are going back to x.x.5 cause they it has poor performances.
-The GPS log files sounds good. I've never tried this but I may give it a try.
I tried to reset the GPS logs from within the soft I was using, but it did not improve anything, looks like the GPS only receives the list of satelits, but no localisation datas at all...
Click to expand...
Click to collapse
....I'm about to revert back to the 07 radio (from 08) as it did not give me the same sat pickup as 07....you can also try the HTC GPS Tool and run a COLD start...I understand this wipes the data and restarts as advised previously...
http://forum.xda-developers.com/showthread.php?t=416334
...lot of other goodies here
The Doctor said:
I've been having a similar problem with my Raphael (it takes a million, billion years to get a lock and even then it's only 3 satellites).
I deleted the 2 GPSlog files in the Windows folder, did a soft reset, ran QuickGPS and then tried Google Maps again. I got a lock in about 10 seconds with 8 satellites.
Now, I've only been able to test it once and will have a go again tomorrow but it's easier than a radio flash or hard reset!
Harry
Click to expand...
Click to collapse
I have a similar problem from time to time.A lot of data received from 10-12 satellites but a fix only after a long long time. In comparison with the Garmin Gps I have the sensitivity of the Diamond GPS receiver is good, but the algoritm is not. Diamond radio is .05
I have the same problem if i delete the log file and update with quick GPS.
It seems that the algorithm in the radio sometimes is not able to converge easily to a fix.
My tomtom was working just Excellent on my diamond, than i did a hard reset and no gps, 1 bar for over 1 hour, so reflashed the same rom again 1.93.405 still same problem, so flashed 1.93.401 and bingo it works again. after a nother hard reset 1.93 401 rom gps wont work angin, this time the 1.93 405 rom fixed it. ( all WWE roms)
no idea why this happend.. when the diamond gps works its excellent (better than most tomtom units) but thants only when it works.
as the gps feature is very importent to me, i now have a back up bluetooth gps incase inbuilt gps fails.
and with out quick gps i find its aloms impossible to get a lock.
I only hope HTC fic this issue if not this will have been my first and last HTC product.
Any tips welcomed
Hi mates,
First of all thanks for the link and the goodies, in fact I had already found some datas since many Diamond users seem to have similiar problems with their device.
I agree this is obviously a mistake of HTC to have put a defectuous part in their phone.
1) My problem even went worse yesterday after I flashed the last HK WWE ROM: my GPS wasn't even sensed by the softs!
No NMEA datas blabla...
2)
many hard reset and reflash couldn't fix the problem. I was about to give up when i found info about that HTC GPS TOOL I had never heard about.
After using it for quite a while, at least my GPS was finally sensed and 'some' datas received, though it wasn't enough to get a proper satelit bar, not to mention a fix...
3)
So now I'm back to the same point: no fix or proper reception available, although I'm already quite happy that my GPS is detected again!
3)
I got back to the same stock radio, x.x.5 but no matter which one I use, I can't see when I'm going to have a a fix with that whimsical GPS!
SOLVED!!!
I finally found a solution to wake up my sleeping (beauty) GPS.
The most helpful infos were in that post below, but I did pick other datas here and there.
http://forum.xda-developers.com/showpost.php?p=2563369&postcount=6
The funniest thing is that this problem looks like a hardware one, but in fact it's all software related. A problem of configuration, due to the A-GPS function probably.
From what I understand, if you use A-GPS (I mean if you really have access to this special service through your phone operator) everything is fine.
If you don't, then you may get into big troubles like I and many others did...
1) make sure A-GPS function is desactivated (nothing to do with the Quick GPS function)
2)
... just follow the instructions provided by the Oijkn on the link above.
3)
delete as well the file(s) GPSlogs.txt in the windows directory
4)
soft reset
5)
enjoy a very efficient GPS
Hello ! (I am french)
I have a HTC Diamond P3700 and Tomtom Navigator 7.910 + western Europe 1GB map.
This map map is not recognized ? How repair ? Thanks
Question:
Is there any way to adjust GPS settings in TE or in some other settings GUI?
In all my time of Android use on the Kaiser, only once has the GPS ever worked which was with l1q1d's .25 kernel (with module update) and Incubus26jc's build.
Google maps/latitude/navigation/places all worked fine on this build but I currently have it set up with the current Sourceforge build and Scoot's/n2rjt's cache kernel. I DO NOT want to change anything EXCEPT the GPS settings.
From what I've gathered the settings should be 9600baud, N, 8, 1.
Thanx for any help in advance...
Wait... WHAT?
IIRC, you don't have to change anything. GPS works for a long time now...
I don't know if it's the phone, something in the kernel or a module error but I never got a lock on any program that uses GPS, not GPS test, facebook, maps/latitude/navigation, or foursquare.
Like I said, it only worked once way back when we were using the .25 kernel with the update. Since then I've not gotten one GPS lock... not one.
I'm using the new cache kernel and all of the current fixes, updates. My GPS always worked with every release. It's very slow when searching for GPS signal but it's working.
I have tried with iGo but not with Google Maps. But I think it could work with Google Maps.
I have changed the Radio ROM several times so it can't be the problem.
I personally think I might have a bad GPS reciever in this phone because I can't remember it ever working.
Ill try and scavenge another one of these Kaisers from work (they were popular amongst the office workers), HardSPL it and install the build I'm using on it, just to see if it works. Ill report back later...
Sent from my Android on HTC Kaiser using XDA App
Okay, got another Kaiser and tested GPS on it before wiping/unlocking/hardspl-ing it and it worked fine. Found 5 sattelites and locked on within seconds using GPS test under winmo.
Unlock/security unlock/hardspl/kernel install/install android and update/use backup from original phone (2.2.2 with RIL and cache update) and problem followed. GPS test only found 3 sattelites at most and never locked on for the 10-15 minutes I had it up.
IMHO, I have a software comm port issue. wether it needs a different speed or a different setting in android I can't tell. I looked over initrd and can't seem to find any port settings.
I can tell you that the GPS did work with Krazy Killa's kernel, but it was highly unstable compared to the newest one from Scoot/l1q1d/n2rjt.
Any ideas would be greatly appreciated...
I got a idea... flash winmo and test it
As stated in post #6, the Kaiser was stock when I tested the GPS, meaning winmo 6.0 was running before flashing anything to the phone. GPS tested fine under winmo, aquiring signal and lock in about 10 seconds using GPS Test for winmo (2008 version).
Im just looking for where the actual hard settings would be in either /system or in modules added. I have done some GPS work in the past (omnitech hacking and modding, changing OS, modding settings, etc.), so I have no fear of breaking something if it doesn't work anyway.
PoXFreak said:
As stated in post #6, the Kaiser was stock when I tested the GPS, meaning winmo 6.0 was running before flashing anything to the phone. GPS tested fine under winmo, aquiring signal and lock in about 10 seconds using GPS Test for winmo (2008 version).
Im just looking for where the actual hard settings would be in either /system or in modules added. I have done some GPS work in the past (omnitech hacking and modding, changing OS, modding settings, etc.), so I have no fear of breaking something if it doesn't work anyway.
Click to expand...
Click to collapse
Somewhere on the winmo settings, you'll find the GPS port, baud etc.
You can ask in ther kernel threads how this is set...
Thats what I was asking about...
Could the kernel (mtdblock0) be mounted under terminal emulator, be edited and still work, or is this a crapshoot?
I have all the settings for the "correct" GPS port number, Xbit, BPP, basically all of it.
I remeber reading somewhere that Android is looking for 38.4bps. This is not correct as the Kaiser uses 9.6bps, or 9600 bits data rate.
If this is incorrect, data from the satellite(s) will be misinterpeted and give incorrect readings. The satellites don't care what you recieve, it's how the data is handled after the phone gets it.
The way I learned all of this is by cracking a "nk.bin" file open for the Omnitech GPS back in 2008 and creating a custom bootloader that allowed use of one of 3 different GPS programs to run on one unit. Destinator, iGo and TomTom all ran well of this one GPS because I was able to get the GPS settings right.
PoXFreak said:
Thats what I was asking about...
Could the kernel (mtdblock0) be mounted under terminal emulator, be edited and still work, or is this a crapshoot?
Click to expand...
Click to collapse
IIRC, mtdblock0 is the WHOLE nand memory. So you cannot mount it, only mtdblock0p1, mtdblock0p2 etc etc. But yes, you can mount /system for writing with mount -o remount,rw /system
I have all the settings for the "correct" GPS port number, Xbit, BPP, basically all of it.
I remeber reading somewhere that Android is looking for 38.4bps. This is not correct as the Kaiser uses 9.6bps, or 9600 bits data rate.
If this is incorrect, data from the satellite(s) will be misinterpeted and give incorrect readings. The satellites don't care what you recieve, it's how the data is handled after the phone gets it.
Click to expand...
Click to collapse
Perhaps liquid or scooter or somebody else will see this and point you in the right directions.
The way I learned all of this is by cracking a "nk.bin" file open for the Omnitech GPS back in 2008 and creating a custom bootloader that allowed use of one of 3 different GPS programs to run on one unit. Destinator, iGo and TomTom all ran well of this one GPS because I was able to get the GPS settings right.
Click to expand...
Click to collapse
Posted a question to the main android forum and have 272 views so far.
Sorry, forgot "mtdblock0" was NAND, pt1/2/3/4 is the partitions. Will try mounting and see if I can find anything. I've checked /system/libs/*.* ("all" for non-DOS users) and can't find anything pertaining to the GPS. Maybe I'm not looking in the right place.
/system/lib/libgps.so ???? <-----
Apparently I need to acces the kernel directly in order to change any values within the base GPS driver. I extracted OS (kernel) with NBH tool and gave it a once over.
I'll dig in later as myPITA girlfriend wants to go putz around today...pfft.