Auto turn on wi-fi?

[adulak]

Wlecome

Is it possible to automaticaly turn on Wi-Fi on TX? If I set kMeteo to automaticaly get weather and disconnect, I must confirm that I want turn it on at the specified time. How to avoid it???

[Church Punk]

2playme :rolleyes:

[cyberdude]

I don't recall the specific name, but wasn't there a wifi auto on/off hack?

I found it. There is an app called WiFiOn and one called WifiAutoOff. The wifion app seems okay, but for reasons I don't remember I have the wifiautooff app in my incompatible folder on my card. I believe they are both available from www.freewarepalm.com.

[FerdFerd]

Is it possible to automaticaly turn on Wi-Fi on TX? If I set kMeteo to automaticaly get weather and disconnect, I must confirm that I want turn it on at the specified time. How to avoid it???I usually just leave WiFi on, but disconnected. kMeteo then will connect automatically without need of confirmation.{Edit: The update of kMeteo to 0.9 took care of the following problem. I have to say, though, that I have been having trouble with scheduled updates since version 0.8 was released a day or two ago. This version seems not to get notification after a reset, so if I update early in the morning, after my automatic backups that include a soft reset, the scheduler hasn't been working to wake kMeteo up. I didn't have that trouble in version 0.7. If I open version 0.8 manually after the reset, the scheduler then seems to work. (Yes, I have kMeteo in my unCache list. And the same difficulty has been cropping up even with unCache disabled completely.)}

There is a difference of opinion about the power drain caused by just leaving WiFi on but disconnected. I haven't noticed much effect on battery life, but there is a thread somewhere on one of the Palm forums that says doing this does cause a substantial power draw.

[_Em]

From what I've measured, is causes a measurable, but not very substantial power draw. I think the "turn off" feature was added as a safety, so you could ensure it wouldn't accidentally turn on in areas where you're not allowed to have radiating devices.

[tgeorges]

My TX used to connect to my home WAP every morning (to download weather), but now, I have to first specifically connect to a WAP before browsing, etc. In other words, my TX used to have this behavior:

1 - I'd bring up browser
2 - enter a URL and hit "go"
3 - Wifi would attempt and succeed connecting to my home WAP

Now, step 3 looks like it's starting, but it craps out and I have to manually connect.

It even says "Home Office: Initializing" (Home Office is my home SSID).

It then fails and says, "No network connection found. Select Wi-Fi or Bluetooth to set up your connection."

I then click OK, then I manually click on the Wifi small icon and connect manually.

Anyone have any idea why this behavior is happening and there's no auto-connect?

-Tom

[_Em]

My guess: you have more neighbours with WiFi hotspots now.

I found that my area is saturated with hotspots (more than 11), so now it's hit or miss as to whether I can establish a connection without specifying the AP I'm using explicitly.

[pruss]

From what I've measured, is causes a measurable, but not very substantial power draw. I think the "turn off" feature was added as a safety, so you could ensure it wouldn't accidentally turn on in areas where you're not allowed to have radiating devices.

Interesting. Dmitry said there was no power draw at all when he measured it. How big is the power draw you've measured?

I do have auto WiFi on/off utilities. They work just fine. But after Dmitry said there was no power draw, I removed them since I thought they weren't needed.

[_Em]

Indeed. The power draw I measured was very very minimal, and done very unscientifically (large margin for error). The battery charge dropped around 2% more in 8 hours than with it turned off (dropped from 100% to 95% instead of to 97% IIRC). This included a nightly NVBackup to SD in both instances. No files were added or modified in NVRAM during this time.

Now I recall that old conversation; I think I decided at that time that the difference must have been due to other factors, and like you, forgot about it.

[FerdFerd]

I tried but failed to find a post I read in the last week that claimed the drain on the battery was the same when you have WiFi on but not connected as when you are connected and using WiFi. There were voltage or current measurements quoted. Although numbers were attached to the measurements, which gave an air of authority to the claim, it didn't make sense to me in terms of my experiences. But I have no actual data.

If I resurrect that post, I'll be back. It must have been here or at Brighthand.

[Gregte]

I'vew measured the WiFi power draw as very substantial on two occasions and just verified it again. Here the the method I used this time:

I plugged my 4 AA cell battery pack into the TX's power port. This is what I use to power the TX for long periods of time. Anyway, I also put my ammeter in series with the 4 AA cells. I turned on the TX and the meter read that the TX was drawing 360 miliamps from the battery pack. If the TX's own internal battery were fully charge then that reading would have been less. But back to the point... it was drqwing 360 mA with WiFi turned OFF. Next I turned WiFi ON and the ammeter jumped up to 480 mA and stayed there. I then turned WiFi OFF and it dropped back down to 360 mA. This is very repeatable as I have done it a several times with the same results.

As a comparison, the screen backlight draws 0 mA when the backlight is OFF (obviously) but an additional 78 mA at full brightness.

I have also done the same with bluetooth and found that it draws a very insignificant amount of power. I leave bluetooth ON always just as a matter of convenience but I always turn WiFi OFF when not in use.

It seems that there are many who have gotten very different results than I have regarding the power consumption of WiFi. I wonder if there is a difference in TX's during their production run? My serial number is:PN70UBT5V4P8

[FerdFerd]

Yep, yours is the post I remembered, Gregte. It's here: Linky (http://forum.brighthand.com/showpost.php?p=1513487&postcount=12).

[pruss]

I'vew measured the WiFi power draw as very substantial on two occasions and just verified it again. Here the the method I used this time:

I plugged my 4 AA cell battery pack into the TX's power port. This is what I use to power the TX for long periods of time. Anyway, I also put my ammeter in series with the 4 AA cells. I turned on the TX and the meter read that the TX was drawing 360 miliamps from the battery pack. If the TX's own internal battery were fully charge then that reading would have been less. But back to the point... it was drqwing 360 mA with WiFi turned OFF. Next I turned WiFi ON and the ammeter jumped up to 480 mA and stayed there. I then turned WiFi OFF and it dropped back down to 360 mA. This is very repeatable as I have done it a several times with the same results.

I am curious how much more current draw there is when the WiFi is actually connected. Would you be able to check that?

[thierry2064]

I am curious how much more current draw there is when the WiFi is actually connected. Would you be able to check that?
Gregte already answered here (http://forum.brighthand.com/showpost.php?p=1494570&postcount=1)
Big surprise to me: I thought that Bluetooth on (always detectable) was using more power than Wifi on (which should do nothing, or ?). I used Blue Fang to switch bluetooth off as much as possible, now I am mainly looking for a Wi Fang...

[PinCushionQueen]

Gregte already answered here (http://forum.brighthand.com/showpost.php?p=1494570&postcount=1)
Big surprise to me: I thought that Bluetooth on (always detectable) was using more power than Wifi on (which should do nothing, or ?). I used Blue Fang to switch bluetooth off as much as possible, now I am mainly looking for a Wi Fang...

Ok... so which is it? I just found the old thread for Pruss' Auto WiFi Toggle where people were pretty insistant that there is no draw when WiFi is on but not connected, yet Gregte experiments seem plausible and provide quantitative data. Anyone else care to comment?

If Gregte is correct then we need a WiFi toggle! Alex, any chance of resurrecting Auto Wifi toggle and wifi off? The link in the old thread is dead...

[MD_Brite]

To me seems like after the automatic feature in the T|C all of the other PDA's that succeded the T|C really seems crappy. Using web pro with the power-save feature, from what I have seem the wi-fi turns on and shuts down automatically. Is this a feature they took out of the TX? It was one I had been considering just for the larger screen and memory.

[Greek]

In the TX, it turns on when an internet app is launched and off after "x" mins of inactivity which you can define.

Regards,

[PinCushionQueen]

In the TX, it turns on when an internet app is launched and off after "x" mins of inactivity which you can define.

Regards,

I always thought it "Connects" when an internet app is launched and "Disconnects" after x mins of inactivity. And that On/off is different that connect/disconnect. I've got 2 different controls in the WiFi panel.

[Greek]

You are right, didn´t express correctly. I have an On/Off, which is always turned On, but the wi-fi is activated when an internet apps asks for it and disconnects when it is inactive after X mins. :)

Regards,

[pruss]

I guess when I get back home, I'll resurrect WiFi on/off. I'll probably roll them into a single app.

[thierry2064]

I guess when I get back home, I'll resurrect WiFi on/off. I'll probably roll them into a single app.
I hope it won't require English localization, as Wifi on did ;)

[pruss]

I hope it won't require English localization, as Wifi on did ;)

I'll try. You may need to tell me the localized equivalents of various messages.

[pruss]

OK, here it is:
http://www.1src.com/freeware/index.php?cid=21

[dump71]

Pruss, thanks VERY much for AutoWifi---very handy :)

[Greek]

It is great as it will save battery. I have tried it, and it turns On a Wi-Fi Off machine instantly!! Faster than if I do it manually. That´s why I always had it on, and the OS asking bothered me...This does all automatically. Turns off after x minutes (I have it set when the machine turns Off). :cool:

I thank you Alex for all the wonderful, useful and stable stuff you are sharing with us. :)


Regards, :)

[PinCushionQueen]

Yeah!!! Ditto on what Greek said! I don't even notice that it's happening... I had to check a couple of times to make sure it was even activated - it was :D

I'm curious now to see if I actually notice a differenence in battery life. Anyways, as always - Thanx bunches for your work!!

[adulak]

OK, here it is(...)
Hello!
I ask for it in first post :-) Thank You.
The same for bluetooth? :D

[cyberdude]

I don't see how to set it to turn off in x amount of time. Also I'm getting a recurrent error from crash pro (3 times so far). A reset occurs and the error is:

Application: AutoWiFi 1.00
Date: 24 Apr 2007 8:44 am

rtnetlink.c, Line 13:KALMutexCreate

I have Alex's Wififix installed also.

[pruss]

When does the error occur? On connecting? On disconnecting? On launching an app?

[cyberdude]

When does the error occur? On connecting? On disconnecting? On launching an app?
I'll keep a more careful eye on it. Usually I just look at my TX to do something else and the crash screen is there. For instance I just turned the device on and saw the same error except the time index is 9:48am. I don't have wifi at work - so maybe it tried to connect? But I wasn't even using the device at all when the reset happened! :confused:

[FerdFerd]

I can report no problems with Auto WiFi so far. It works to do a scheduled automatic update for kMeteo in the early morning and also to get the correct time at the end of my nightly scheduled NVBackup cycle.

It also has worked correctly repeatedly to start WiFi to update currency conversion data for Currency, news content for Add It, and content for Avantgo. My TX did hang once when I tried to manually update weather data in kMeteo; WiFi never even began to open - I had to do a soft reset to recover, but the unit didn't crash.

[PinCushionQueen]

I don't see how to set it to turn off in x amount of time. Also I'm getting a recurrent error from crash pro (3 times so far). A reset occurs and the error is:

Application: AutoWiFi 1.00
Date: 24 Apr 2007 8:44 am

rtnetlink.c, Line 13:KALMutexCreate

I have Alex's Wififix installed also.

The "turn off in x amount of time" is found in your WiFi prefs under "timeout". This is the disconnect control for WiFi. Alex has made AutoWiFi turn off the antenna upon disconnect.

I still have not experienced any problems with AWF. I too have the WiFiFix installed.

[cyberdude]

The "turn off in x amount of time" is found in your WiFi prefs under "timeout". This is the disconnect control for WiFi. Alex has made AutoWiFi turn off the antenna upon disconnect.

I still have not experienced any problems with AWF. I too have the WiFiFix installed.
Thanks. Don't know what is going wrong here - first SB now this - I think I may have to hard reset and reinstall everything from scratch ... :(

[FerdFerd]

- first SB now this - I thought I remembered a post from you about ShowBattery, but I couldn't find it. I don't want to pull this thread off course, but if you could provide a pointer to your issue, I'd be interested. I'm not having trouble with it either.

BTW, I also have WiFiFix installed, if it matters.

I'm not really convinced yet that AutoWiFi is actually saving battery power as a practical matter, relative to just leaving WiFi on but disconneted. I suppose the data are the data, but I can't discern a difference in length of use before needing to recharge. And despite a report of data to the contrary, I know for sure that my battery drains substantially faster when I am connected to WiFi than when WiFi is on but disconnected. (I cannot use the power saving option - I can only intermittently connect to my router and I often get dropped if I do.)

[cyberdude]

I thought I remembered a post from you about ShowBattery, but I couldn't find it. I don't want to pull this thread off course, but if you could provide a pointer to your issue, I'd be interested. I'm not having trouble with it either.

BTW, I also have WiFiFix installed, if it matters.

I'm not really convinced yet that AutoWiFi is actually saving battery power as a practical matter, relative to just leaving WiFi on but disconneted. I suppose the data are the data, but I can't discern a difference in length of use before needing to recharge. And despite a report of data to the contrary, I know for sure that my battery drains substantially faster when I am connected to WiFi than when WiFi is on but disconnected. (I cannot use the power saving option - I can only intermittently connect to my router and I often get dropped if I do.)
For SB problem see http://www.1src.com/forums/showpost.php?p=983930&postcount=327
http://www.1src.com/forums/showpost.php?p=983610&postcount=281
http://www.1src.com/forums/showpost.php?p=983539&postcount=255

and a couple of more in that thread. enough offtopic. :o

[John Stanley]

AutoWiFi is Wonderful! I can even have my Palm locked with PictureLogin enabled and all my wireless morning updates work just fine!

Wireless connectivity on my TX is now working the way Palm should have had it from day one. (Yet one more Pruss creation that's a strong reason for me to never want to give up my TX...)

Thank you Alex!!!

[FerdFerd]

For SB problem seeOuch, now I remember. I assumed you had that tamed by now.
I think I may have to hard reset and reinstall everything from scratch ... :(I think you are right about that.

[_Em]

Doing some testing, I tried out Palmary Clock Wireless... and it hangs if the modem isn't on before it tries to connect.

In NetFront, if the modem disconnects by the device going to sleep, the session hangs and NF must be restarted. If disconnected manually, everything works fine.

[pruss]

Doing some testing, I tried out Palmary Clock Wireless... and it hangs if the modem isn't on before it tries to connect.

What happens without AutoWiFi if WiFi is off before it tries to connect?

In NetFront, if the modem disconnects by the device going to sleep, the session hangs and NF must be restarted. If disconnected manually, everything works fine.

I am afraid I don't support NetFront, since there is no legal version of it for the TX to my knowledge and so I can't test problems. But if you find this problem in another app, please let me know.

[palmuse]

I guess I will chime in here. I have not had any issues with AutoWifi either. I did have odd problems using the Palm "conserve power" option though. Once again, Alex, you have come through. Thanks!

[_Em]

What happens without AutoWiFi if WiFi is off before it tries to connect?

Same thing, of course ;) --I just thought I should let you know, as it'll probably crop up again.

I am afraid I don't support NetFront, since there is no legal version of it for the TX to my knowledge and so I can't test problems. But if you find this problem in another app, please let me know.

Any "modern" app shouldn't have this problem, so it probably won't crop up anywhere else. Put this in the same category as the other bug.

As far as actual operation/integration, you appear to have released perfectly stable, feature complete alpha code. Good job!

[juggernaut#2]

[palmary clock wireless problem]

@ _EM: did you tell pclock to automatically turn on/off wifi by itself (in "options", "network settings") or do you leave this AutoWiFi ?

[pruss]

Palmary clock will hang with AutoWiFi if it is set to turn on wifi automatically. Otherwise, it will work just fine.

[juggernaut#2]

pruss, ain´t it a good idea to compact all of your invaluable little tools (CenterMenu, AutoWiFi, FixWiFi, FixField, FixBoot and the like, [except ForceDelete, that´s rather an app than a panel]) into one pref panel? at least all of those that only have a "ON/OFF" button to them.

just considering, not asking :)

another question is if one could define another category within the prefs panel to put them in, it gets rather crowded there - is there any possibility?

EDIT: added FixBoot, which appeared out of nothing while i was writing this... you are incredible... :)

[PinCushionQueen]

Just to report after 2 days of AutoWiFi use and automatic scheduled WiFi updates of both the time (NVBackup) and the weather (4Cast) work well - no hitches. Thanks again!

[cyberdude]

I think I found the problem that was causing that reset and error. I had a older app called Wifi Auto off still installed. I deleted this and AutoWiFi hasn't given me any problems since. :) (crosses fingers) :rolleyes:

[pruss]

pruss, ain´t it a good idea to compact all of your invaluable little tools (CenterMenu, AutoWiFi, FixWiFi, FixField, FixBoot and the like, [except ForceDelete, that´s rather an app than a panel]) into one pref panel? at least all of those that only have a "ON/OFF" button to them.

just considering, not asking :)


Hmm. It might make a nice shareware utility: "TX/LD Fix".

Alex

[juggernaut#2]

upps, they´re gonna beat me up now :)

[phreakonaleash]

/me gets a clue by four... :)

It would be nice, though it is not something i'd be willing to pay for :) when the apps are right here free...

[shsmith]

A reset occurs and the error is:

Application: AutoWiFi 1.00
Date: 24 Apr 2007 8:44 am

rtnetlink.c, Line 13:KALMutexCreate
I get exactly the same reset at random times. Happened today twice and I wasn't using wifi at all. Once it happened when clicking the home icon from TimerLT and another time I was in launcher and I think the reset happened when it automatically powered off.

[shsmith]

Hmm. It might make a nice shareware utility: "TX/LD Fix".

AlexI would be happy to pay a small registration for your bundle of fixes and enhancements. You deserve some reward for all you are contributing to the palm community.

[pruss]

I get exactly the same reset at random times. Happened today twice and I wasn't using wifi at all. Once it happened when clicking the home icon from TimerLT and another time I was in launcher and I think the reset happened when it automatically powered off.

Yeah, I got it, too. I wonder if it was the auto-on or the auto-off component that caused this.

[FerdFerd]

I had a reset tonight when I tried to manually update kMeteo's data. At the point I would have expected the wifi dialog to show up, my TX crashed. I didn't think too much about it, and all was well after, but seeing the latest discussion, I thought the report might help. The crash was when I would have expected wifi to turn on, not off.

[pruss]

I had a reset tonight when I tried to manually update kMeteo's data. At the point I would have expected the wifi dialog to show up, my TX crashed. I didn't think too much about it, and all was well after, but seeing the latest discussion, I thought the report might help. The crash was when I would have expected wifi to turn on, not off.

You don't happen to have a crash message, do you? (If you want to get crash messages, you can install CrashPro, or my free Diagnoser.)

[FerdFerd]

No messages, but I'll install Diagnoser and continue the watch. My response on getting the crash was to delete FixBoot (actually move it to a holding folder on the SD card) since that was the last thing I installed.

Don't have Crash Pro, although I've occasionally thought I was adventurous enough in trying things that I should buy it. My real trouble is that I will have no idea what the messages mean.

[Pgr]

Hi,

does this FixBoot program help find which application is crashing the PDA during a Global Find?

Thanks.

[Pgr]

I'm using AutoWiFi for three days now and it works great. I believe (just a belief, no scientific measurements :-) it has had a significant positive impact in battery life. I eagerly await that AutoBlueTooth!

Another significant positive side effect is that it solves another problem I had. I use AutoLock on my TX with that feature of unlocking through a combination code pressing the 5-Way keys. I used to have this nagging problem where I would turn on my Palm, see the code entry screen, but have to wait about a second before the 5-Way keys were active. This led to lots of erroneous entries of the code.

After I started using AutoWifi, this delay is gone (with BlueTooth also off). I had no idea it was related to Wifi.

Double thanks to Alex!

[juggernaut#2]

A reset occurs and the error is:

rtnetlink.c, Line 13:KALMutexCreate I can confirm this error happening to me as well. Kind of funny that there doesn´t seem to be a pattern to it - today morning I had a reset of this sort while the TX was unused and sitting in its cradle.

@Pgr: If you want to have the same for BT, why not use Bttoggle (http://www.whizoo.com/apps/bttogglepro.php) ?

[pruss]

I uploaded 1.11 which may or may not help with the errors.

[pruss]

I wonder if the power usage measurements may be flawed. Here's why. It is conceivable that the OS allocates power differently depending on whether the device is being externally powered or powered from the internal battery. If so, then measurements of current drain while powering the device externally would be flawed.

[cyberdude]

Hi,

does this FixBoot program help find which application is crashing the PDA during a Global Find?

Thanks.
use findtester, the author's website is www.flashplug.de

[Pgr]

I think AutoWifi breaks Versamail's Autosync feature, I suppose Versamail is not able to turn on WiFi. I don't get any error, it simply does not autosync hourly as it is configured to, and it used to work just fine before installing AutoWiFi.

If Alex Pruss is able to solve this, great! But even if not, I think I'll go on using AutoWifi because the battery gains are very observable to me.

use findtester, the author's website is www.flashplug.de
I tried it but it crashes my T|X every time. This particular TX does not have any problem with global find at this time, everything is fine and still Findtester crashes. But enough on this, I don't want to hijack this thread, and I was able to solve my problem (on a friend's PDA) with Crash Pro. Thanks anyway!

[ebonair]

Once again, an incredibly useful piece of software. I always hated to try to check my email and be presented with "Turn on Wifi?" :)

Thank you Mr. Pruss!

-joe-

[pruss]

Any crashes with the new version?

[pruss]

I think AutoWifi breaks Versamail's Autosync feature, I suppose Versamail is not able to turn on WiFi. I don't get any error, it simply does not autosync hourly as it is configured to, and it used to work just fine before installing AutoWiFi.

Does autosync work with WiFi off? I am guessing that Versamail may check whether WiFi is off, and if it's off, not run.

[juggernaut#2]

Any crashes with the new version?
Not since i´ve installed it. But being that just one day, I wouldn´t submit a "bug free" report :)

[FerdFerd]

Any crashes with the new version?OK here so far.

[cyberdude]

Any crashes with the new version?
Okay here as well. :)

[Greek]

I didn´t have crashes with the previous version, but the TX got frozen ofently until I disabled it. This new version has not frozen the machine so far. :D

Regards,

[FerdFerd]

I didn´t have crashes with the previous version, but the TX got frozen ofently until I disabled it. This new version has not frozen the machine so far.This is an interesting report to me. I've had several complete freezes when opening kMeteo v0.9 recently. It locks the device up with the only way to recover being a soft reset via the pin. It happens when I open the application, before any access to WiFi is requested. These freezes do not happen all the time, so it's hard to pin down their cause.

I thought this was kMeteo issue. I now wonder if it's related to AutoWifi. If it is, I still have that problem with the latest version, 1.11.

[shsmith]

Any crashes with the new version?Not a single reset since the new version. This one is a keeper.

[FerdFerd]

No more freezes with kMeteo so far, since my report two posts up. And no resets either.

[PinCushionQueen]

This is an interesting report to me. I've had several complete freezes when opening kMeteo v0.9 recently. It locks the device up with the only way to recover being a soft reset via the pin. It happens when I open the application, before any access to WiFi is requested. These freezes do not happen all the time, so it's hard to pin down their cause.

I thought this was kMeteo issue. I now wonder if it's related to AutoWifi. If it is, I still have that problem with the latest version, 1.11.

I only mention this because you guys are talking about recent freezes... I too have had a recent increase in Freezing TX that requires a pin reset. Once when turning off while WiFi still connected & OffFlush flushing and 3 times while in Plucker - I have no idea why AutoWiFi would affect Plucker. It's perhaps just a strange coincidence. I will disable AWF and see how Plucker behaves. All freezes were while using v1.11.

Blazer used to crash more frequently with the previous version but seems to be fixed in v1.11

[pruss]

AutoWiFi should not affect Plucker unless an earlier instance of it caused some instability. I don't have any problems on my TX right now. I have disabled ShowBattery, though. (I had it on for several days, but found the TX less than perfectly stable.)

[thierry2064]

I disactivated autowifi because Operamini is less stable with it. I suspect that the freezes come from a long known bug from Operamini, which you must sometimes restart when the connection was off because inactive for too long (I got used to it). With autowifi, it freezes instead of giving the message "Operamini could not connect", so you have to reset.

[juggernaut#2]

No resets or freezes since new version. The only thing I noticed is that flushing takes a bit longer now. Anyway, great little app, a keeper just as shsmith said :)

[Pgr]

Does autosync work with WiFi off? I am guessing that Versamail may check whether WiFi is off, and if it's off, not run.
I tried turning off your AutoWiFi, then turning off Wifi, and verified that Versamail does not AutoSync. I suppose you guessed right. It turns on my Palm, but does not turn on Wifi, and the Palm just goes off after 3 minutes again (that's my configuration).

I don't suppose there's any way around this?

[jstrubberg]

I went so far as to remove AutoWiFi and still can't get Versamail to turn on wifi and fetch my mail.


May be more going on here than AutoWiFi....

[Pgr]

I went so far as to remove AutoWiFi and still can't get Versamail to turn on wifi and fetch my mail.


May be more going on here than AutoWiFi....
Versamail never turns on, it merely connects Wifi to autosync. My Autosync still works as long as I put my Palm back to the original conditions: AutoWifi Off, Wifi On. But I lose battery life that way.

[Greek]

I only get my emails manually, but I tried to do it automatically and it failed with AutoWiFi activated. Machine turned on at the specified time, after some secs, I got a beep, and the alert manager started blinking, saying that VersaMail couldn´t get the mail and to do it manually.

Then I tried with AutoWiFi Off, WiFi On manually (machine turned off, it woke up and VersaMail checked the emails and worked as expected.

Regards,

Regards,

[PinCushionQueen]

My apologies Alex, it appears I was in error with my freezing report and Plucker. Plucker wasn't actually freezing it was just taking a loooonnngg time to find the image in the doc that I selected for full size view (It's a very large doc -119MB). So AutoWiFi is back on and working.

As for ShowBattery - well now I'm really used to having it there and not sure I want to give it up (actually not sure I need to give it up). Sorry you're still having problems because of it... Are your problems still limited to TCPMP?

[_Em]

Strange thing... I haven't had any problems vis TCPMP and Henk's version of ShowBattery on my T|X. However, I'd suggest turning off as many extended hacks in TCPMP as possible, as it isn't really a program where you're going to use most of them anyway. I keep FontSmoother turned off in TCPMP, for example.

[pruss]

My apologies Alex, it appears I was in error with my freezing report and Plucker. Plucker wasn't actually freezing it was just taking a loooonnngg time to find the image in the doc that I selected for full size view (It's a very large doc -119MB). So AutoWiFi is back on and working.

As for ShowBattery - well now I'm really used to having it there and not sure I want to give it up (actually not sure I need to give it up). Sorry you're still having problems because of it... Are your problems still limited to TCPMP?

The problem has been two or three unexplained crashes in other apps. One of these was in Plucker, one in Versamail, and maybe one elsewhere, over a period of about five days. On my standard TX config, I never get unexplained crashes. Of course the explanation could lie elsewhere.

[FerdFerd]

Do you suppose the chances of an unexplained crash are increased at the moment ShowBattery updates? I don't recall if you've said how often it does that, but it's apparent that it's only periodically.

If the crashes happen only if an incompatible action occurs when ShowBattery is updating, that would explain how it only crashes once in a while. And it would be hard to discern a pattern.

And if I'm not off track completely, would it then be possible to make ShowBattery test for conflicting actions elsewhere in the OS before doing an update? Or maybe just test for an inactive period before updating?

[pruss]

Do you suppose the chances of an unexplained crash are increased at the moment ShowBattery updates?

I would guess that the crashes may correlate with ShowBattery changing the displayed icon. But I try to make that happen in as safe a context as I can. *Perhaps* locking StatusBarResource would help, but I don't know.

[FerdFerd]

*Perhaps* locking StatusBarResource would help, but I don't know.It isn't presented in Resco Locker as something that could be locked. I'd try and report if I could do it.

[FerdFerd]

Does AutoWifi make any changes that would remain after it is deleted completely?

[pruss]

Does AutoWifi make any changes that would remain after it is deleted completely?

No, it doesn't.

[FerdFerd]

I thought that would be the answer, but I'm fishing for all options. I've had some crashes after tracking via WiFi with Tracker Dog that seemed to be related to whether I connected to WiFi before I initiated the tracking. If I let WiFi connect after being called by Tracker Dog, it was always crashing at the end. If I connected first and then tracked, all ended well. But this was true whether Auto WiFi was on, off, or absent. I tried turning ShowBattery off, but that didn't matter either. I didn't get to the point of deleting ShowBattery altogether. No Crash Pro error report accompanied the crashes.

To make matters more perplexing, the crashes seem to have stopped for no obvious reason.

[_Em]

Ferdferd: maybe some preferences related to your WiFi are corrupted. Try using a util like Cleanup to back up and delete your WiFi prefs, and see if the problem goes away.

Er, I should finish reading before I start writing :D
Anyway, you might find your Prefs DBs are corrupted anyway. I've found that many stability issues are really to do with this.

[FerdFerd]

Ferdferd: maybe some preferences related to your WiFi are corrupted. Try using a util like Cleanup to back up and delete your WiFi prefs, and see if the problem goes away.Interesting thought. I inspected my saved and unsaved preferences with FileZ and couldn't see anything that seemed like it might be the WiFi preferences. Also, these crashes only happened with Tracker Dog, not with several other applications that also call for WiFi to connect.

Just to be sure I understand, wouldn't it be true that if WiFi preferences were corrupted that I'd get these crashes for any application that caused WiFi to open and connect?

I won't be able to do more testing until this evening.

[_Em]

Hmm... so, probably not WiFi. I think WiFi keeps its info in its own DB actually, and doesn't use the PrefsDBs.

It *could* be that the file that lists local hotspots is corrupted, but it sounds more like it's an issue with trackerdog/low DB/etc.

[FerdFerd]

Well, I still get a crash sometimes after "Tracking" with Tracker Dog, if I haven't connected first to WiFi. Diagnoser caught the last one, but said the cause is Unknown. But it doesn't happen always. I've been trying to monitor cache size to see if there is a pattern. With about 30% free, it worked OK.

Other WiFi-using applications continue to work fine with AutoWiFi.

(I'm probably about to stop wondering about this and just remember to connect before tracking with Tracker Dog.)

[juggernaut#2]

I tried to reproduce your problem but I failed. On my device (TX, TD latest version, AutoWiFi installed and active) it makes no difference if WiFi is on or off; TrackerDog always connects and disconnects nicely without any crashes.

I know this is not of much help to you, but then again, Trackerdog does not offer to update on a scheduled basis. Do you use 2playme/crony for that or do you always "sync" using WiFi ? If the former, it might be those, if the latter, there might be another app that messes up WiFi just before TD runs.

[_Em]

Here's a Q: Are you guys using WiFiFix?

[cyberdude]

Here's a Q: Are you guys using WiFiFix?
yes, I am.

[FerdFerd]

Here's a Q: Are you guys using WiFiFix?Yes, I am. PErhaps I should see what happens with it off.

[FerdFerd]

I know this is not of much help to you, but then again, Trackerdog does not offer to update on a scheduled basis. Do you use 2playme/crony for that No, I don't. I haven't tried to schedule updates automatically, at least not so far.or do you always "sync" using WiFi ?Yes, under the App DB menu I select Tracking... This connects Wifi and proceeds directly to check the online database against my installed applications list. The updating proceeds normally, but just after the last application appears on the list, my TX crashes. I have never tried to track via hotsync, and I don't plan to do so.If the former, it might be those, if the latter, there might be another app that messes up WiFi just before TD runs.Wish I knew what the conflict is, mainly because I worry a little that this is exposing something wrong that is more important to me than Tracker Dog function.

[juggernaut#2]

Wish I knew what the conflict is, mainly because I worry a little that this is exposing something wrong that is more important to me than Tracker Dog function.
I´d suppose so, because as I said it works nicely here, and I´m using FixWiFi, also. I guess I basically do have much the same configuration as you guys do :)

I am mainly tracking through hotsync, though. It is not so much a time-critical update (many of the info is wrong anyway), and this way I just have an update once a day, which is enough for me. Did you try re-building the TD database ?

[FerdFerd]

Did you try re-building the TD database ?Yes, several times.

[juggernaut#2]

I´m sorry, I have no clue.

All I can tell which might be related to your problem is that I sometimes don´t have the default network connection set to WiFi because I used BT (which seems to set the default connection to whatever BT connection was active), but this doesn´t seem to be your problem since you´re saying crashes occur after syncing.

TD isn´t registered for any notifications, and AutoWiFi/FixWifI aren´t, either. So it might just be a problem of TD writing to its database ... so all I can think of is: Which of dmitry´s apps (i.e., FrameTX?) are you using? Sorry to say but I could track almost all "unbelievable" problems to one of those - FrameTX, PowerVolume, SuperSecurity in particular.

[FerdFerd]

I have another idea what might be going on with my Tracker Dog crashes, and it doesn't have anything to do with AutoWiFi directly. I thought about putting this in a separate thread, but decided to keep it here, even though I've turned this into a thread with two rather different topics in the end.

I now suspect the crashes after updating are related to whether the DIA is up or down when I begin tracking. If it is up, tracking completes normally without incident. If the DIA is down when tracking begins, all is normal until the end. At the end, the DIA, which rises up when tracking begins and WiFi connects, begins to retract again and that is the point at which my TX crashes.

In short: DIA up at the beginning = no crash at the end. DIA down at the beginning = crashes often on completion as the DIA begins to retract. I'd be curious if anyone else sees the same.

[juggernaut#2]

I always have the DIA down for TrackerDog using DisplayManager.

[FerdFerd]

I just installed DisplayManager and set it to have the DIA retracted in Tracker Dog. Tracking still caused a crash and reset. So having DisplayManager control the DIA doesn't solve this for me.

[cyberdude]

I always have the DIA down for TrackerDog using DisplayManager.
I have it set the same way as Juggernaut#2 and am not encountering a problem unless I ask it to scan the whole card as I mentioned in the other thread.

[juggernaut#2]

Just a thought: DIA = ShowBattery ? So it might not be a TD problem, but a DIA problem?

[FerdFerd]

I don't quite understand. I do use ShowBattery, but I've also tried turning it off, and I still get crashes following WiFi tracking if the DIA is retracted when the unit connects automatically to WiFi. I have not tried removing ShowBattery completely, though. cyberdude uses ShowBattery (or did), and he doesn't have this trouble, so I'm doubtful that ShowBattery is the cause.

The crashes remind me very much of what happened in early versions of Accessorizer, before Alex Pruss forced the DIA to be permanently displayed for all Accessorizer-created DAs.

[juggernaut#2]

I am just fishing in the dark (expr?)... you´re right with CD. Another thought would be if you have TD set to automatically disconnect on completion (I don´t). Maybe this could interfere with AutoWiFi ... but as I said, I have no clue, I am just thinking out loud.

[cyberdude]

I don't quite understand. I do use ShowBattery, but I've also tried turning it off, and I still get crashes following WiFi tracking if the DIA is retracted when the unit connects automatically to WiFi. I have not tried removing ShowBattery completely, though. cyberdude uses ShowBattery (or did), and he doesn't have this trouble, so I'm doubtful that ShowBattery is the cause.

The crashes remind me very much of what happened in early versions of Accessorizer, before Alex Pruss forced the DIA to be permanently displayed for all Accessorizer-created DAs.
I use SB 1.00 because I can't get newer versions to work after a reset. Maybe it is MetaView's SB that is causing the problem?

[FerdFerd]

I use SB 1.00 because I can't get newer versions to work after a reset. Maybe it is MetaView's SB that is causing the problem?Ah, I hadn't thought of that. I'll give it a whirl tonight when I get access to WiFi at home.

I'd regret losing MetaView's enhancements, but at least I'd understand what's going on.

[_Em]

Remember that the WiFi icon also gets updated on the DIA... are you using a skinning app? It could be your skin that isn't working well with TD. Try disabling your skinner in TD and see if that helps.

[FerdFerd]

No skinner other than myKbd for the DIA. Should I try disabling that, do you think? (I probably will anyway.) I use a slightly modified version of Velo's Grayhide for the DIA.

[FerdFerd]

Nothing helped. ShowBattery 1.02 on or off. Default DIA skin loaded back by myKbd. All permutations I tried, which must be close to all of them resulted in crashes after tracking if the DIA was down to begin with and automatic WiFi connection followed.

If I connect first with WiFi, the DIA does rise during connection, but it then goes down after connection completes. If I then track, no crash. If I expect WiFi to connect automatically, whether just having the usual WiFi on or through AutoWiFi, the DIA stays up during Tracker Dog tracking, and my TX crashes when it begins to retract automatically after tracking is complete. So it really is the automatic retraction of the DIA following tracking that crashes my TX.

I haven't tried uninstalling myKbd completely, because I'd quickly give up Tracker Dog if it came to a choice between it and my myKbd skins and the ATOMIK keyboard.