element-hq / element-hq/element-android

Unable to send messages when captive_portal is blocked

Open
#1,798 4 comments 5 reactions 0 assignees View on GitHub
Dominant language
Kotlin
Stars
3.7k
Forks
917
PR merge metrics
No merged PRs in 30d

Description

Hi Matrix-Team,
I really like your work and especially your messenger Element!

Myself I am using Android 9 without Google services due to I am also using AFWall+ to block Google services. First I was confused about why Element is not sending my messages, because in Riot everything was working fine.

I was blocking captive_portal_login which is connecting to a website from Google to check my internet connectivity.
Due to it reported that I have no internet access, even if I had internet access.
![IMG_20200723_120522](https://user-images.githubusercontent.com/27868982/88298734-1170a100-ccf1-11ea-8fe0-01eead51eb2b.jpg)

Now I just turned off captive portal detection with this command `adb shell settings put global captive_portal_mode 0` and Android is telling that I have internet access.
![IMG_20200723_120552](https://user-images.githubusercontent.com/27868982/88298749-16cdeb80-ccf1-11ea-88f3-f500a5e72505.jpg)

When captive portal detection response with "no internet access" even if I have internet access, I am not able to send messages in Element. In Riot this was working fine.

So captive portal detection is necessary for Element now?
In a worst case scenario no one (except technically experienced people) would be able to send messages in Element if the captive_portal website from Google is down, even if the matrix home server is online. I would recommend to check internet access with the matrix home server which is in use.

Best regards!

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.