melanzane alla parmigiana here:
http://groups.google.com/group/juicedefender/web/JuiceDefender179.apk
(sorry for the ungoogly redirects - direct links apparently remain
valid for just about one minute)
- new location algorithm!
- fixed rare FC
- fixed Toggle mobile data widget bug
- debug logging now optional
First thing to do: 'help', 'enable debug logging'.
You're encouraged to stress-test Location - it's not strictly
necessary to 'clear known locations' but it's probably a good idea.
Location will soon enough learn about your Access Points. You'll see
various 'Updated location for network blahblah: lat, long (XXX/YYY m)'
entries in the log; the XXX and YYY are the 'inside' and 'outside'
distances. The 'inside' radius will grow as Location learns of
'places' where WiFi turns out to be working (keep in mind it uses the
very coarse cell location, so it might become rather large). The
'outside' radius will shrink on the opposite rule. In between, there's
the 'maybe' area - which optimally should eventually be reduced to a
thin 'ring' (currently it has a lower bound of 100m of thickness).
(Also, latitude and longitude will be progressively tweaked as well,
and they will *not* necessarily converge towards your AP; instead
it'll be the optimal center point for the various cell-based
locations)
If you see any of this happening (in order of decreasing importance):
- WiFi failing to get enabled when you're close enough to your AP
(forcing you to a manual enable)
- WiFi getting briefly enabled even if you're, say, 10 miles away from
your AP
- WiFi getting briefly enabled every time while at a certain not-so-
distant (but distant enough) place, even after *extensive training*
please do this:
- open JD, 'help', 'send feedback'
- change the subject line to something like "JD Location - didn't
enable wifi, FAIL!!!11!"
- briefly describe the situation either on this thread mentioning your
subject line, in the log email itself, or both for bonus points :)