Database Info

Treo 750 Bluetooth Password X2?

I have a Treo 750 and a Gtop G33 BT GPS. When I try to connect I can get to the password and if i put nothing in (Gtop says no password needed) and press next - it connects (light flashes slower) but Treo asks for Password again and this time it wont allow me to press next till I put a password in (next is grayed out.) I've tried 0000(Gtop says use 0000 if devise must have a password) and 1234 but as soon as I press next again GPS disconnects (light flashes fast again) and Treo says it is now connected.
I have been all over this sight for the past 2 days and have learned a lot, I even flashed my rom, OS-WM 6.1 WWE lite and radio1.54.07.00, but so far I still cant get this to work (bluetooth), perhaps I cant see the forest for the trees.
Any help would be greatly appreciated!
Jim

GPS CONNECz
Check to see if the treo proccessor speed 300Mhz is compatibalbe with the GPS RECR.
else i don't know I'm a novice

Me too- only with bluetooth headset
I had the same issue under WM5, but did found a way past it once and then of course it was irrelevant. That was months ago and now I can't figure out how I got past the problem. So I'd appreciate it if anyone could clue us in.
Thanks

I've managed to find a way past this
There appear to be multiple versions of WM6.1 around. I had the same problem until yesterday when I re-upgraded to a different version of WM6.1.
Not sure of the version (I'm in New Zealand, so using an Australian rom).
The version that doesn't work is easy to spot as there is no battery indicator and it uses the Microsoft Inbox for texting. The version that does work has the battery indicator and uses the Palm version of texting.
Once I'd got to this version, it no longer insisted on having a bluetooth password.
Cheers, Hope this helps.

MDA Compact IV Can't Turn Wi-Fi On

Hi guys, now something odd is going on with my MDA Compact IV (aka Touch Diamond). With the original T-Mobile ROM I could connect to Wi-Fi fine. When I upgraded to Dutty 2.6 ROM I could still connect fine but after a couple of weeks it stopped connecting for no reason I could see. When I mean it stopped connecting, basically, when I click the "Turn on Wi-Fi" option, the little spinny ball pops up to show you its trying to do something but then nothing - it stays unticked and there is NO error message. I have tried setting power mode to best performance and changing the wifi to connecting between "The Internet" and "Work" - the two options available (I think it used to work on the default Work settings) - but it still doesn't work. I just upgraded to Dutty 2.9 and it does exactly the same thing - no error message so I am not sure how I am supposed to diagnose the problem!
Anyone have any ideas? Any help would be much appreciated!

Hi,
I'm having the same issue with the same device.
I already reverted back to stock spl/rom/radio but the problem still remains in every rom i try.
The only solution is to get out the battery for at least 10 minutes and try again.
It should work until it stops again.

Thanks for the message, I just managed to fix it on mine about 5 minutes ago. In the end, I cleared my internal storage and hard reset it and it finally worked. That is after trying various ROMS/Radios. Lets see how long it lasts....

Hi,
I'm having the same issue now... It just started yesterday - And I have no clue - except, that I recently have used the device connecting my laptop using internet sharing...
Any clue someone? don't want to hard-reset...
Thanks!! J

Strange network problem

Some time ago I wrote a thread at the Diamond section about a problem with my HTC Diamond, regarding the unusual waking up of the phone in random periods of time. This happens on a freshly installed ROM from the HTC, official one. Nobody could help me, so I switched back to my Touch Cruise, again after freshly installed ROM (no third party software installed) and the problem started apearing again. I came to the conclusion that the problem is somehow related to my SIM card. I guess there is some bug either in WM or in my mobile operator's network, regarding something with 3G or HSDPA. My opinion is that on random intervals my phone recieves some kind of a signal from the network or loses some kind of a signal, which makes it to wake up. I reached this opinion because there is a certain place on the road between my home and office, where the phone ALWAYS wakes up. I guess there is a weak spot in the network.
My question is: How can I find and read the system log of Windows Mobile 6.1 ? I am asking this because I am almost certain that there will be some kind of information or error message on the times of the wake, which will help me determin the problem.

try to use your phone in Airplane Mode.. if it happened again then it doesnt belong to your network

I Found the problem !!!
Finally after months of agony, I have found the source of my problem. It was my SIM Card ! The damn thing was broken. I found that this is the problem, because I was already given up on my Diamond and wanted to sell it. So i put my SIM Card in my older Touch Cruise. And as you guess, the Touch started to act the same way as the Diamond. I went to my operator, exchanged my SIM card with a new one and now everything works as a charm. I don't know really what was the problem, but I guess it was some Voltage issue or maybe the card just wasn't getting the right signals. The important thing is that now I get to keep my Diamond and enjoy it without the problems I had.
Thanks for the replies !

Touch Pro2 won't turn on?

I was having a few issues with my Touch Pro2 freezing up and not turning on. The reset button did nothing. Then, I discovered my problem and I wrote about it:
http://www.medicalsmartphones.com/2009/09/touchpro2-wont-turn-on-use-right-power.html

You can see that the actual power button icon is also on the red "hang up" button.
Makes more sense for someone coming from a regular phone as most devices actually use the same button to turn on and off the phones.

I'm still not convinced of this... i've been seeing issues with the TP2 on sprint using WM 6.5. It enters one of the following states... and the only way to recover is carry out a reset (remove back cover and press the 'reset' button).
1) Device will not power on, but orange charge light is visible
2) Device will not active sync and becomes locked, and cannot be powered down
3) Device repeatedly shuts down and restarts when connected to a PC via active sync..
Its all with the sprint rom that came with the phone.

Darkseed said:
I'm still not convinced of this... i've been seeing issues with the TP2 on sprint using WM 6.5. It enters one of the following states... and the only way to recover is carry out a reset (remove back cover and press the 'reset' button).
1) Device will not power on, but orange charge light is visible
2) Device will not active sync and becomes locked, and cannot be powered down
3) Device repeatedly shuts down and restarts when connected to a PC via active sync..
Its all with the sprint rom that came with the phone.
Click to expand...
Click to collapse
Yep, same issue with the "Official VZW 6.5" update for my Verizon TP2...
Updated, when was it out, Thursday? Finally got all my sync issues fixed (Vista/Myphone/6.5 were not playing nicely) and starting reloading my Rhapsody stuff... Working good... Lovin' the 'Sense UI' update (minus the lag - but workable) and then... DUN DUN DUHHHHH!
Sunday morning I woke up to a completely frozen phone. Charge light was stuck on, frozen at the TP2 startup screen.
First try, power button - no response...
Second try, reset button - reboots to stick at the TP2 startup screen again...
Third try, battery pull - back to the startup screen again...
Finally booted to boot mode where 6.1 went right back on that puppy - works like a dream again!
Something weird in 6.5 land!

zcarman said:
Yep, same issue with the "Official VZW 6.5" update for my Verizon TP2... Something weird in 6.5 land!
Click to expand...
Click to collapse
+1. My phone NEVER did this with 6.1.
Flashed to 6.5 thursday. Started re-installing cabs sort of fast and loose. Had the phone go into the sleep-of-the-dead five or six times over the next 24 hours. Power was on (pressing end/power button gave me the green arrow telling me to wake the phone using the top button. Pressing anything else wouldn't work and only a battery removal or soft reset would do the trick.
Hard reset Friday and started doing .cabs with a little more care (Sense off/install/reset/Sense back on). and I've gone three days without it happening again. Coincidence? Don't know. But I'll be watching these threads (here & XDA) carefully and keeping my fingers crossed.

zcarman said:
Yep, same issue with the "Official VZW 6.5" update for my Verizon TP2... .
Finally booted to boot mode where 6.1 went right back on that puppy - works like a dream again!
Something weird in 6.5 land!
Click to expand...
Click to collapse
Where did you get 6.1? Verizon is sending me a new phone, I hope it comes with 6.1. I got my phone on Friday and Flashed offical VZW 6.5 to it, as a matter of fact I think they would have suggested that I upgrade today if it wasn't already at 6.5. They had me check version and said yep that's the latest version, that's the one we need on your phone.
Of course they don't admit there is a problem.
One time when it was "sleeping" and couldn't wake it up I tried calling it.... it vibrated, the lights came on, but no way to answer it just wouldn't "wake up"
Totally unacceptable.

immjg said:
Where did you get 6.1? Verizon is sending me a new phone, I hope it comes with 6.1. I got my phone on Friday and Flashed offical VZW 6.5 to it, as a matter of fact I think they would have suggested that I upgrade today if it wasn't already at 6.5. They had me check version and said yep that's the latest version, that's the one we need on your phone.
Of course they don't admit there is a problem.
One time when it was "sleeping" and couldn't wake it up I tried calling it.... it vibrated, the lights came on, but no way to answer it just wouldn't "wake up"
Totally unacceptable.
Click to expand...
Click to collapse
All the stock ROMs can be found here http://forum.ppcgeeks.com/showthread.php?t=91940
If you like wm6.5 other than the issues you have had, i suggest trying a custom 6.5 ROM such as MightRom( http://forum.ppcgeeks.com/showthread.php?t=79579)
However before flashing make sure your phone is unlocked. This can be done here: http://forum.xda-developers.com/showthread.php?t=578660
If you live in verizon's 1x network and keep getting an error every five seconds or so, the fix can be found here: http://forum.ppcgeeks.com/showpost.php?p=1472842&postcount=107
Custom ROMs are faster and in many cases much more stable than verizons 6.5 update. I am currently using MightRom with no problems. No freezing or anything.

Opened a thread on this issue over at PPC Geeks:
http://forum.ppcgeeks.com/showthread.php?t=106799
Pretty clear this issue is NOT related to carrier, not isolated to any one ROM (yes, even Mighty ROM has experienced this, too), nor is it solely seen with WM 6.5.
I have my opinions and theries... but who knows. No definative solution is apparent as of yet.

Still happening with my VZW TP2 WM 6.5. Never happened with 6.1. My current theory is that it has something to do with Active Sync. I never start it, but it is often found running on my phone and I cannot find where to shut it off. This was not the case w/ 6.1. I don't know enough about the phone internals to say any more than this, or to test the theory.... Still looking and listening for answers, will post here if found.
Why would ActiveSync need to run when the phone is not hooked up to a PC??

Looks like an old thread, but I have a touch pro 2 w/ sprint. Activesync is always running. I have to kill it with the task manager. Haven't nailed down what's triggering it to fire but it takes up valued resources. I'm finding pother apps running when I thought I exited gracefully, like email, messaging. I'm thinking it's a setting somewhere??. I figured out for my case why Active sync kicks off on it's own.
QuickGPS significantly speeds up the time for determining your GPS
position. QuickGPS downloads ephemeris data from Web servers, instead of from satellites, using your
device’s Internet connection via Wi-Fi, ActiveSync or GPRS/3G. Now any location related service like the weather update is lijghting up ASync and I have to kill it with the task manager util. To prevent it from happing I'd have to turn off data services.. so fark it. I increased the weather update time and kill the app if I use it.

QuickGPS significantly speeds up the time for determining your GPS
position. QuickGPS downloads ephemeris data from Web servers, instead of from satellites, using your
device’s Internet connection via Wi-Fi, ActiveSync or GPRS/3G.
I think when the phone uses an app that requires location, like weather active sync is getting woken up. In my case I get weather updates every 2 hours. Presto - evertime I kill activesync then update weather acltivesysnc starts up again. So, what I'm saying is for my case if I don't have wifi or evo or a strong signal, and I update weather activesync lights up. That supports what the manual says about QuickGPS.

Activesync is used several things including exchange email. If you set up push email with exchange server then even if you turn off activesync with the task manager it will automatically turn back on.

Vox turns off automatically

Hi,
my vox turns off (completely off, not only display) automatically since yesterday.
Description:
I can switch on my phone, enter SimPIN an can normally use it. As long as i use the vox it stays on.
If i put on the keylock and let the vox untouched for a few minutes, it switches completely off.
The only change i did yesterday was playing around with Navigon Mobile Navigator, FakeCursor and Bluetooth.
I already deinstalled the applications i added yesterday, but same problem.
I also tried a second battery, same problem.
Has anybody an idea or is there like a log on vox, where i can see what causes the shutdown ?
OS: WM 6.5 from Fr. Hottelmann, worked fine for month until yesterday ...
Thanks in advance
Alex

Mh, sounds strange. It usually is a battery problem. Maybe try a hard reset or reflash (maybe also try a different ROM, although I doubt that it is my ROM since this didn't happen to anybody else...yet).
BTW: I have two batteries that don't work correctly, I just ordered a new one.

Hi Fhm, thanks for your reply. A hardreset worked. It seems that Navigon Mobile Navigator 7 combined with the usage of BT Gps causes this problem. Thanks, great forum Alex