Google Testing Return of Separate Wi-Fi and Data Toggles in Android 16

“Do small interface tweaks change everything?” This is the question that has been hovering over the structure of the Quick Settings user interface in the Android operating system ever since Google decided to merge the switch for the mobile and the Wi-Fi data connections into the single ‘Internet’ tile in the version 12 update. The move in 2021 through the ‘Material You’ design was intended to improve the connectivity control and further prevent the misuse of mobile data.

Image Credit to shutterstock.com | Licence details

Prior to the introduction of Android 12, the Quick Settings shade had dedicated tiles for mobile data and Wi-Fi. This allowed the user to toggle off one network radio technology without disturbing the other, which helped those individuals that frequently travel, developers wanting to test networks, or individuals wanting to save battery life when the signals are weak. This Internet Panel ‘replaced the previous design with an expansion UI: a tap on the tile opened a bottom sheet containing switches for Internet, mobile data, nearby networks, and sharing. As pointed out by Google, users tended to toggle off the WiFi connection to switch to mobile data, then forget to turn WiFi back on, thus ‘resulting in excessive mobile data use.’ They thought that organizing these options ‘under one panel provides “a more intuitive and straightforward way… while reducing user error and unintended consequences.'”

In terms of Android’s technical audience, the reasoning made sense, but it felt like a loss of data fidelity. Complaints poured in on forums and social media sites about the increased complexity. Third-party developers set about creating software such as Better Internet Tiles, designed to bring back the original toggles via private APIs. This software had to run at administrator-level access via ADB or root access, since Android does not allow direct control over the radios via its public APIs. By Android version 13, all these had been excised by tighter security settings, except for custom UI layers such as One UI on Samsung phones or Xperia UI on Sonys.

However, hidden in the code of Android 16 QPR2, there’s evidence of a rethink by Google. Commits in the Android Open Source Project by Michael Bestas, lead Android developer for LineageOS, introduce two new Quick Settings tiles: “Mobile Data” and a new Wi-Fi tile featuring their pause and scan feature. The mobile data tile has toggle functionality through a confirmation dialog. The Wi-Fi tile, which remains code-named “Internet” for a transition phase, displays the current non-Wi-Fi provider in case Wi-Fi isn’t the default option. Features for a complete transition to the Wi-Fi-only tile are also mentioned in internal Android code.

Technically, this is hidden behind the feature flag com.android.systemui.qs_split_internet_tile, titled “Splits the Internet tile into Wifi (with internet info) + Mobile Data.” However, this flag is currently turned off in the current Android 16 QPR3 Beta 1 and Canary images. Additionally, this approach using feature flags allows Google to include silent code paths in their final Android production image so that they can be turned on in the future. This is convenient for developers wanting to experiment with new design layouts in the UI before implementing it on the public OS.

Functionally speaking, this not only involves a cosmetic touch-up of the toggles but reworks how connectivity manager functionality on Android needs to handle independent radio states without necessarily relying on the unified logic residing on the Internet Panel every time. This relates to how the whole system is listening for changes in connectivity and how it makes APIs available to applications. More granular hooks would definitely feature in the presentation once toggles are back, particularly in developers creating automation applications related to connectivity matters like geofencing or battery levels. This would definitely correspond with how connectivity functionality on Google will continue to evolve and would include items like Wi-Fi restriction on a granular basis on multi-user devices.

The UI/UX considerations are just as relevant here. Quick Settings is a high-use interface, and even slight slowdowns would multiply daily. A likely pattern of user engagement as measured by Google’s own metrics would demonstrate how frequently the Internet Panel is opened, how long the user lingers within it, and the rate at which they abandon a procedure midway through. Split buttons would likely decrease the time spent interacting as well as improve perceived speed in the process as well. This would further decrease the performance divide between Android and iOS, whose Control Center has always offered straightforward Wi-Fi and cellular buttons. Then of course, there is the overall ecosystem play, where the majority of IoT and Wear-related products function optimally on a stable Wi-Fi environment; the quicker, independent buttons simply make the entire experience easier without impacting mobile data connectivity in the process.

Enterprise support would allow IT administrators to implement policies-more directly accessible as a result of direct controls-similarly aimed at blocking Wi-Fi connectivity in “secure areas.” Their return would likely improve overall Android adoption in professional settings where speed of device administration is a significant priority. As to whether or not this sees the light of day on Pixels or only continues as an OEM component, only time will tell. Some manufacturers never did implement the panel, so this is a standardization of the Android environment that Google is clearly working on. However, as far as the subset of the Android community which voiced concerns at the loss of the aforementioned buttons is concerned, the fact that the feature is an option is the strongest indication of the community’s influence yet.”

spot_img

More from this stream

Recomended

Discover more from Modern Engineering Marvels

Subscribe now to keep reading and get access to the full archive.

Continue reading