Project

General

Profile

Actions

Issue #1792

closed

WiFi connection established via RepWifi not correctly reported by the Android Framework to user-space apps

Added by Fil Bergamo almost 7 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Wi-Fi
Target version:
Start date:
04/12/2017
Due date:
09/01/2017
% Done:

100%

Estimated time:
Resolution:
fixed
Device:
Grant:
Type of work:

Description

It is a suggested best practice for Android apps to check for the connectivity status of the device before performing any network-related task.
To do so, the Android Framework exposes some methods that apps can use to retrieve the available network connections, and their status.

When a WiFi connection is established via RepWifi app, although perfectly working (ping, dns resolution, web browsing), the framework still presents the WiFi connection as disabled or disconnected to the user-space apps.
This misleads apps that rely on this mechanism, so that they prevent the user from doing network-related tasks.

E.g. F-Droid prevents the user from updating the repos while connected to WiFi via RepWifi app, because it detects the WiFi connection as inactive.

A possible solution is to modify the designated system service in the Android Framework that reports the connection status to client apps.
Some research has already been done in this field.
A promising approach seems to properly modify the class "com.android.ConnectivityService.java" to read the ip routing tables, and detect the route established by RepWifi, and if present, modify the status of the corresponding "NetworkInfo" instance returned to calling applications.


Files


Related issues

Related to Replicant - Issue #1867: Download app not working when on USB network or RepWifi connectionResolvedFil Bergamo01/20/201806/01/2018

Actions
Actions

Also available in: Atom PDF