Open GoogleCodeExporter opened 8 years ago
There's a chance the update has
changed your access points, can you
check they're not using proxies?
Check the FAQ for more about proxy
stuff.
Original comment by hugovk@gmail.com
on 22 Jul 2009 at 4:57
My APs correct. Other apps are connecting without any problem. I also tried
using
fire.fm from my browser (laptop) at that time and it was playing okay. Do you
have
any debugging/logging capability built in? I will try once again and let you
know
the status.
Original comment by jjai...@gmail.com
on 22 Jul 2009 at 7:43
Looks like a problem with the AP in my office and mobbler. I get the "200 ok"
error
in office (WPA/WPA2 enterprise with PEAP network) where as it works fine at my
home
network(WEP). However, all other apps work fine with both the network. This is
where
I'm a little confused.
Original comment by jjai...@gmail.com
on 23 Jul 2009 at 6:15
Did your office AP work before the
firmware upgrade?
Original comment by hugovk@gmail.com
on 23 Jul 2009 at 4:22
Original comment by hugovk@gmail.com
on 24 Jul 2009 at 10:38
yes. I deleted the AP and recreated. Problem remains with mobbler. Other apps
are
working fine. I'll continue investigation for another two days. Meanwhile, is
there
a way to generate some logs?
Original comment by jjai...@gmail.com
on 24 Jul 2009 at 11:38
Not really, not in the release version. Perhaps we can sort out a debug
version,
that generates some logs, but it might not have logs for the bit we're
interested
in.
Eartle, what do you think?
Original comment by hugovk@gmail.com
on 24 Jul 2009 at 11:42
I too had this issue on my n96 after updating the firmware, with mobbler
1.09(265) and 0.9(265). But only on my wifi AP. Also mobbler would not update
to the latest version correctly. Both these issues were cured by removing and
reinstalling mobbler.
Original comment by andrew.c...@googlemail.com
on 25 Feb 2010 at 1:18
Original issue reported on code.google.com by
jjai...@gmail.com
on 22 Jul 2009 at 12:11