All Projects

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.

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.

Rendering on RTL devices is does not work properly due to alignment problems.

Attached: Screen grabs from the pre-release report on an Arabic device.

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?

Material design icons are supposed to be white according to comments found online and most apps.

(I can’t find an actual upstream reference) Found at http://www.androiddocs.com/design/style/iconography.html

Dark icons are displayed white in practice.

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

Reported by Terry Parrott

Reports that the app won’t auto load despite having the option enabled.

Reported on Oreo.

Presumably related to FS#370.

The app force-closes on device boot when load on boot is enabled.

Once the boot is complete it behaves normally.

Seen in Oreo.

Presumably related to FS#369.

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%

Meta-task depending on tasks scheduled for the 1.4 release.

Previous release:  FS#234  (1.3.1)

Should provide an easy way to generate a new configuration file based on the provided command-line arguments.

It just makes more sense

Useful for debugging, likely not useful for users since the command-line already overrides configurable arguments

When the resulting contact sheet is too thin, the meta-information header is cramped and fields overlap.

Fails on some files (gets stuck forever while capturing the first frame).

Happens often with Matroska. 1.0.7a introduced a workaround (-Wo) with ffmpeg’s argument order that worked with other file types.

Originally suggested by Dogn Redhammer

Originally requested by Dougn Redhammer

E.g. with ImageMagick’s -stroke and -strokewidth

Originally reported by Phil Grundig

Version of ffmpeg: ffmpeg (CVS-060515)

Originally reported by Phil Grundig

Version of mplayer: mplayer (1.0pre8cvs)

Originally reported by Tomasz Strózik

Example given:

$ find $DIR \(-name "*.avi" -o -name "*.wmv" -o -name "*.mpg" -o -name "*.mp4" \) -exec vcs -dt -ds -n 12 -c2 -H 200 --jpeg --quiet {} \;

Works on avi, mpg and mp4 but fails on wmv with
Failed to capture frame (at second xxx.000)

Processing the same file directly works:

$ vcs -dt -ds -n 12 -c2 -H 200 --jpeg --quiet File.wmv

No need for description

Originally reported by Dougn Redhammer

Timestamps could use some tweaking: e.g. centering on their background and rounded corners

Original report by Dougn Redhammer

vcs hangs with some RM files.

Tracing shows it gets stuck in mplayer_identify.

MPlayer can play the files fine from the terminal. Although it exits with «MPlayer interrupted by signal 11 in module: uninit_vcodec».

I can reproduce the abrupt termination, it happens when using Real’s native decoder (w64codecs, /usr/lib/codecs/drvc.so). Using FFMpeg’s decoder (MPlayer’s -vc ffrv30) MPlayer exits normally.

I can’t reproduce the hang either way.