Phone

Published on September 7th, 2016 | by Nicholas

2

Popular Display-Tweaking Application f.lux Is Due Android, Currently Available In Beta (Root Needed)

Popular Display-Tweaking Application f.lux Is Due Android, Currently Available In Beta (Root Needed)
Total Shares196

  • Applications
  • News

There are numerous apps on Android that advertise to change the colour temperature of the screen during the night to advertise better sleep, however the popular desktop application f.lux has so far not been included in this. This really is going to change, though. A beta form of f.lux for Android can be obtained for download at this time, however it does require root.

The concept behind apps like f.lux and Twilight would be that the blue light released from your screen transmits signals for your brain making it think the sun is intense. This could hinder what you can do to slPopular Display-Tweaking Application f.lux Arrives Android, Presently Obtainable In Beta (Root Needed)eep if you are using a telephone at night. So, these apps attempt to shift the screen to some warmer temperature to lessen that effect.

Apps like Twilight simply give a red filter on the top from the UI, which might work-it type of is dependent on whom you ask. f.lux needs root since it is really intercepting the pixels in the GPU and desaturating the blues. This ought to be more efficient, however, it is dependent whom you ask. To get involved with the beta, you will have to enroll in the f.lux forums and get to be included to the exam.

 


About the Author



2 Responses to Popular Display-Tweaking Application f.lux Is Due Android, Currently Available In Beta (Root Needed)

  1. Al says:

    The caustic manual (http://www.singlecellsoftware.com/docs/caustic/caustic_2_1_0_manual.pdf) says it “calculates the device’s audio output latency based on the size of the minimum output buffer allowed”. Actually, it seems to divide the “AudioTrack MinBufferSize” / “Sample Rate”.
    Nexus 7 /2012 / Android 4.2.2 and 4.3: 3072/44100 = 69.659… caustic says 70ms
    Galaxy Nexus / 4.2.2: 1728/44100 = 39.182… caustic says 40ms
    However, that’s not relevant. More important are the numbe1 given by the AudioManager properties:
    N7: 512 frames/44100Hz
    GN:144 frames/44100Hz
    Also see https://www.youtube.com/watch?feature=player_embedded&v=d3kfEeMZ65c at 29 minutes 28 seconds. With native code / OpenSL, you need at least 2 buffer, there might be another hardware buffer =>
    GN: 3.26ms * 3 = 9,78ms (Google claims they are below 10ms, so that might be right)
    N7/2012: 11.6ms * 3 = 34.8ms
    Since caustic shows the same 40ms as the GN, we might expect similar latency as with the Galaxy Nexus. But that’s a guess.
    @androidpolice: don’t trust numbe1 given by othe1 that you don’t unde1tand, measure you1elf. BTW: caustic seems to be slow. Use an app that supports the audio fast path, ideally use midi via usb (that’s faster than a on-screen manual if done right) and measure the difference between the start of the sound pressing a key on a midi keyboard and the start of the apps sound.

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to Top ↑
  • Get newest posts?

    Name
    Email *
  • Hot Posts

  • Recent Comments

  • Categories