Keep Bluetooth GPS ON when Apache is Off

[sklathill]

Or at least keep the Apache's bluetooth on between off/on cycles!

Right now really frustrated with this Apache. It's great except for two things...

If I have an application on that uses my bluetooth GPS (say iGuidance or MS Live), it works just fine... until I turn the power off. What would be really great is if the connection was maintained while the stuff is off. It doesn't do that, and I guess I can live with that.

The big problem is that when I turn the Apache back on, the Apache's bluetooth itself is now off. So now I have to go to the comm manager and turn it back on again.

I've tried doing it both through bluetooth and virtual coms ports as well as through GPSGate and its own stuff like its internal NMEA logging (which I really would like to use... ideally with my phone off while I take pictures over the course of a day) and its own virtual com port routing...

Any ideas? Maybe there's a thread that I missed while I was searching for solutions? Anything is appreciated!

[Unknown Zone]

you might want to d/l those "freeware" phone profilers....and set the phone the way you like it.

Example: A profile like "GPS" and set your settings..ie.. bluetooth always "ON"

[sklathill]

Nope... the profile software doesn't do a thing. Profile or not, as soon as I turn off the Apache, I see that my bluetooth GPS device has lost it's connection. Once I turn the Apach back on, I see the bluetooth is off. The profile, even if it's set to bluetooth on, doesn't do anything to help.

What I don't get is why this happens. I mean, I could be talking with someone on the phone with my bluetooth headset. Switching the phone on and off doesn't crash the bluetooth stack. Why should the GPS react differently? Maybe it's because of how Windows Mobile itself deals with virtual COM ports?

[Unknown Zone]

I have PA Lite....and I did a profile....with "Flight Mode"..and labeled it "GPS"...and set the:
Radio---Off
IR------Off
Bluetooth..On

Switch profile...to "GPS"....phone went to "FlightMode" and the Bluetooth..stayed.."on", was still able to use MSVC 1.6 on my Bt800

Switch profile ..back to "Car"...phone comes out of "FlightMode" bluetooth still..."on"

Dont know if your GPS will still have a connection...since you stated that once the Apache goes to "FlightMode" you lose BT, possible cause of the virtual com.

When you mean ...."Apache OFF"...you are meaning "FlightMode...aka Phone/Radio (off)" right, since you cannot really turn off the 67...the only way is taking out the battery.

[sklathill]

When I mean Apache off, I mean hitting the power button on top, turning off the screen and button input.

[sklathill]

In order to make it clear exactly what's going on, I went ahead and tried making a youtube video that shows the behavior I'm experiencing.

http://youtube.com/watch?v=jR1xe6JEFUk

Note that this is the way it works regardless of GPS receiver, GPS-enabled application, or using straight Windows Mobile GPS to virtual COM Port or the GPSGate utility.

[Lazybones]

When you press the power button the unit goes two sleep and three things happen.
- bluetooth will go into a standby mode
- all applications go into standby
- the SD card is powered off.

If you want to save power find an app that will let you turn the screen off and map it to another button. SPB pocket plus will let you do this for example. THere is no stopping all of what the power button does.

[sklathill]

Is that really true? I mean, how does my bluetooth headset stay on when I turn off my phone while I'm talking to someone? Or just now, I decided to load a large web page: as soon as I press enter to go the URL, I turn the apache off... but then I turn it back on after a minute and see the whole page is there.

This also doesn't explain why the bluetooth itself is just OFF after I turn the unit back on. It didn't simply just go into standby mode...

[Unknown Zone]

At this point, I am just trying to dig as much info that I can think of, am I getting paid for all the research...btw I am turning in my 2 weeks....lol.

I looked at your video, did the same thing with the button....and I my bluetooth was active...either way...never lost BT and the light still was blinking, maybe it is different with GPS units.

Just Checking again:
Do a test, just with a BT Headset only, do you still get the same results...the blue light stops blinking, can you still use the BT Headset with the 67 in "standby"

I am thinking, it might be a software related with the GPS, since you put the 67 in "standby mode" the connection to the GPS is shut down to save battery, since the software is no longer talking to the GPS, who need GPS when the Unit is on Standby, that is where the "PowerState" below, might come in handy.

Are you running the orignal rom? Dont know if that has anything to do with it, but I am rumming Kirvin C&S, which has hacks up the ying/yang.

Of Course, Change At Your Own Risk!!

Also check the power state under HKLM\System\CurrentControlSet\Control\Power\State, as in "BlacklightOFF, Resuming, ScreenOFF, Suspend, Unattended"
which are all set to "btl1=4", you might want to change the value.

Mine is set to "btl1=1", on the Suspend State

From PDAPhoneHome.com,
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\Power\State\Suspend]
"btl1:"=dword:00000002

Powerstate definitions from microsoft.

D00:
State in which the device is on and running. It is receiving full power from the system and is delivering full functionality to the user.

D1:
tate in which the device is fully functional at a lower power or performance state than D0. D1 is applicable when the device is being used, but where peak performance is unnecessary and power is at a premium.

D2:
State in which the device is partially powered with automatic wakeup on request. A device in state D2 is effectively standing by.

D3:
State in which the device is partially powered with device-initiated wakeup if available. A device in state D3 is sleeping but capable of raising the System Power State on its own. It consumes only enough power to be able to do so; which must be less than or equal to the amount of power used in state D2. State in which the device has no power. A device in state D4 should not be consuming any significant power. Some peripheral busses require static terminations that intrinsically use non-zero power when a device is physically connected to the bus; a device on such a bus can still support D4.

D4:
State in which the device has no power. A device in state D4 should not be consuming any significant power. Some peripheral busses require static terminations that intrinsically use non-zero power when a device is physically connected to the bus; a device on such a bus can still support D4.

--------------------------------------------------------------------------------

[sklathill]

I recently put on a pretty minimal WM6 courtesy of the official helmi kitchen. however, this gps bluetooth problem's hit me all throughout last year with WM5 as well. Same thing with both my i.trek m5+ and pharos igps-500 units.

Tried doing some of the registry stuff and found some of the relevant threads on pdaphonehome. Putting the btl1=1 into the various power states didn't help. Did both suspend and unattended, didn't work. Put it in a couple more places, and that didn't help either.

I've been seeing in some places about:

[HKEY_LOCAL_MACHINE\Comm\Bluetooth device\Parms]
"DisablePowerManagement"=dword:00000001

But HKEY_LOCAL_MACHINE\Comm\Bluetooth device doesn't seem to exist in my registry... hrm...