All Projects

To mimic the original way of working

Once the user has chosen to use only a set of icons, allow them to choose which of the two.

No need for description

Theming support as initially intended ( FS#237 ) is not possible.

With the switch to vector graphics adding alternative icons becomes fairly “cheap” app-size-wise and many users have requested alternative ones. This task tracks these suggestions.

Recap of related suggestions:

• Pamy Srt 10/01/2016 on Google Play
  Needs to indicate using LTE icon not just 4g icon good app if you add this I will make it a 5
  
  
• Jon Manilenio 29/04/2016 on Google Play
  Nice I wish there were more designs though.
  
  
• Miles Vino 23/04/2017 on Google Play
  Appreciate this handy app! Please consider a simpler icon, without the square, so it blends with Google’s material design. Thanks!
  
  
• MJ Cortez 02/06/2017 on Google Play
  4G should be displayed as LTE instead of [4]
  
  
• Prince Priyam Borah 08/08/2017 on Google Play
  Plz add the stylish 4G logo. Your app only shows 4. Else, everything is ok.
  
  

This is a continuation of  FS#354 .

Temporarily using pre-rendered PNGs in 1.5.1, should try to re-design icons to render properly on Android 5.0 and up.

Take advantage of Nougat style notifications to display more information to the user.

See https://material.io/guidelines/patterns/notifications.html

Possible design elements:

1. “App icon”: Network type? AFAICT setting it to the actual app will replace the status bar icon.
2. Header text: Provider
3. Timestamp: Time of the last update
4. Large icon: Network type, bigger?

Since the introduction of Material, icons should be white. The black icons only display as such in a subset on devices.

Submitted by Tom

Display alarm or change color to indicate roaming

Submitted by Tom:  FS#222  Display provider name in status bar

Not feasible in the actual status bar, but can be done in the notification.

Gradle allows to define fields on the generated class BuildConfig. This should be enough to discard the current per-build-type classes.

Example: https://stackoverflow.com/questions/24518940/custom-fields-for-a-build-type-in-gradle

In the past BuildConfig.DEBUG wasn’t reliable (when combining Eclipse and ADT), but on Android Studio with Gradle it can be used safely and hence there’s no need to duplicate the functionality.

As of 2019-07 usage below KitKat is anecdotal:

2.3.x: 0.04%
4.0.x: 0.07%
4.1: 0.86%
4.2: 1.35%
4.3: 0.82%

2.3 to 4.3: 3.14%

4.4: 6.28%
5.0: 4.33%