Open GoogleCodeExporter opened 8 years ago
I have not noticed the above complaint, but I have noticed that when I open
Trook, it closes the Wifi immediately which is annoying as well. If the Wifi
happens to be on, it makes sense to leave it on in case the user plans to grab
a feed of something like that right away. I've "fixed" this adding
"acquireAndWaitForWifi();" to the "onCreate()" method of the Trook class. I
don't think this is necessarily the best way to do it (I'm just not familiar
enough with this system yet), but it works for me and my irritation level is
down quite a bit since I made the change.
Original comment by craftycoder
on 12 Jul 2010 at 2:42
I second both of jmcode's observations. Whether or not the network lock
acquisition reference error is related to the fact that Wi-Fi does not get
disabled, this I don't know, but for me it consistently does stay on once I
have accessed the network using Trook. This is with a Nook Wi-Fi.
A (somewhat tedious) workaround is to manually stop Trook when done accessing
the network, after which Wi-Fi will turn itself off.
Original comment by mgoetze2...@gmail.com
on 15 Jul 2010 at 11:18
Original issue reported on code.google.com by
jmc...@gmail.com
on 4 Jul 2010 at 4:13