[BUG] - autotunnel not working, location perms seemingly not accessed in several days

[mdecourcy]

Describe the bug
WGTunnel not auto connecting after disconnecting from WiFi. It appears it hasn't accessed location data since 11/30

Smartphone (please complete the following information):

• Device: pixel 9
• Android Version: Android 15 graphene os build 2024112700
• App Version: 3.6.1
• Backend: [e.g. Kernel, Userspace]

To Reproduce
Steps to reproduce the behavior:

1. Have autotunnel on for untrusted wifis of mobile data
2. Disconnect from WiFi (either via settins or walking out of range of router)
3. You never connect to the vpn

Expected behavior
Autotunnel gets triggered after leaving/joining network

Screenshots (Only if necessary)

Additional context
Error logs (unsure if related)

2024-12-03T01:57:01.000000655Z 24108 26309 ERROR AmneziaWG/home-proxmox: message= UAPIOpen: mkdir /data/data/org.amnezia.awg: permission denied
2024-12-03T01:57:01.000000688Z 24108 26288 ERROR cutils-trace: message= Error opening trace file: No such file or directory (2)

Note it was previously working. Unsure if an app update or android update broke something.

[mdecourcy]

Appears rebooting the device fixed the auto tunneling on WiFi disconnect

[timi35]

Same here in a Samsung s23 Ultra.
It seems the reason is the last Samsung Update. A restart didn't help.

[timi35]

I tested it again. In the last nightly AutoTunnel doesn't work.
In Version fecc55f it works better, but the tunnel doesn't stop if there is no connection.

[zaneschepke]

Hey! The latest nightly coming out tonight should fix a lot of these issues. Please let me know if it helps. Thanks!

[timi35]

Hi Zane, this version has the same problems on my device. 1. It still connects to whitelisted WLANs. 2. It doesn´t disable VPN if there is no connection. It looks like keep alive, but I don’t use this feature. Btw: if I add a wlan to the whitelist, VPN disconnect immediately. But as soon as I reconnect to the whitelisted WLAN, VPN is active. Comment to 1.: I tested it again, the problem is reproducible: First connection to a whitelisted WLAN – VPN starts Second connection to a whitelisted WLAN – VPN doesn’t start -> correct Third connection to a whitelisted WLAN – VPN starts and so on… Best regards! Von: Zane Schepke ***@***.***> Gesendet: Sonntag, 8. Dezember 2024 02:30 An: zaneschepke/wgtunnel ***@***.***> Cc: timi35 ***@***.***>; Comment ***@***.***> Betreff: Re: [zaneschepke/wgtunnel] [BUG] - autotunnel not working, location perms seemingly not accessed in several days (Issue #472) Hey! The latest nightly coming out tonight should fix a lot of these issues. Please let me know if it helps. Thanks! — Reply to this email directly, view it on GitHub <#472 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEMHWTFEZW5OB2XCP2GQHQL2EOOJ5AVCNFSM6AAAAABS4WQKMGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRVGM3TCMJUGA> . You are receiving this because you commented. <https://github.com/notifications/beacon/AEMHWTHWQQVO4FXBW22VDQT2EOOJ5A5CNFSM6AAAAABS4WQKMGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUWQYNQI.gif> Message ID: ***@***.*** ***@***.***> >

[zaneschepke]

Thanks for this detail, I'm able to reproduce. Working on a fix now!

[zaneschepke]

I found the bug. This should be fixed in the next nightly.

[timi35]

Dear Zane, it looks great until now. I’ll test it still a while. Btw, now I can see the „missing“ Feature in Autotunneln 😊 and know why WGtunnel didn’t stop the tunnel 😉 Thanks a lot! Best regards, Tim Von: Zane Schepke ***@***.***> Gesendet: Sonntag, 8. Dezember 2024 21:08 An: zaneschepke/wgtunnel ***@***.***> Cc: timi35 ***@***.***>; Comment ***@***.***> Betreff: Re: [zaneschepke/wgtunnel] [BUG] - autotunnel not working, location perms seemingly not accessed in several days (Issue #472) I found the bug. This should be fixed in the next nightly. — Reply to this email directly, view it on GitHub <#472 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEMHWTG3JI42CZ6TOGDJXL32ESRIFAVCNFSM6AAAAABS4WQKMGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRWGM2TSMBQGQ> . You are receiving this because you commented. <https://github.com/notifications/beacon/AEMHWTAYQOOCFWGLTCOCIA32ESRIFA5CNFSM6AAAAABS4WQKMGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUWSUW5Y.gif> Message ID: ***@***.*** ***@***.***> >

[zaneschepke]

I think this one is now resolved by 3.6.3. Marking this as closed. We can reopen if the issue comes back up.