Open GoogleCodeExporter opened 9 years ago
Uninstalling Droidwall restored GPS working....hopefully that can be fixed as I
would like to use Droidwall.
Original comment by cmh...@gmail.com
on 6 Aug 2012 at 7:27
On my Samsung Galaxy S2 (tested with cyanogenmod 10.0 and 10.1-nightly, i.e.
android 4.2.2) I'm experiencing the same issue:
Although "GPS Status" shows satellite signals being received, it never gets a
fix - even with 9 or 11 satellite signals coming in.
Deleting / refetching the AGPS data doesn't help.
When I deactivate Droidwall iptables and reboot, it works.
I'm no expert. I know that for a quick gps fix a good time reference is needed,
otherwise a GPS device has to refer to the GPS signals in order to get the
exact time, which can take several minutes (though, even trying for half an
hour, it never got a fix...).
Android uses NTP (network time protocol) which usually uses UDP Port 123.
Having a look at the DROIDWALL logs via adb shell, Droidwall obviously
disallows those packets:
root@android:/ # dmesg | grep DROIDWALL | grep DPT=123
<4>[167079.918576] c0 [DROIDWALL] IN= OUT=wlan0 SRC=192.168.178.2
DST=192.53.103.104 LEN=76 TOS=0x10 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=58465
DPT=123 LEN=56 UID=0 GID=0
<4>[167085.926538] c0 [DROIDWALL] IN= OUT=wlan0 SRC=192.168.178.2
DST=192.53.103.104 LEN=76 TOS=0x10 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=51021
DPT=123 LEN=56 UID=0 GID=0
How about adding a separate rule to Droidwall that allows UDP Packets from and
to port 123?
Original comment by frank.ra...@gmail.com
on 28 May 2013 at 8:35
Original issue reported on code.google.com by
cmh...@gmail.com
on 3 Aug 2012 at 6:14