Ah. Okay. CWM temporary. Intel x64, stock rom from asus, because still imposible to install other stock rom on asus device, their system is complicated.

Ah anyway it's working when I change my color driver, I use default compositor, when I change it to Qualcomm or Tegra it will work only for the dark room mode, but not for the flux filter anyway. Something strange happened 😓😓. So would you debug it?

I just tried to change the Color Driver from Compositor (slower, compatible) to Tegra and now it does not pending back and forth between the two sets of colors. It did however, depending on when I pressed, choose either the yellowish or intense blue color. So I had to press a couple of times before I could get it to stay at the yellowish color that f.flux for computers have (that also has a tone of red in it depending on what angle you look at the screen). Or at least my eyes seem to think so.

Another thing that happened was that when I rotated the screen f.lux seemed to stop working, the display went back to the original one, just as it were before installing f.lux. Maybe that's some kind of bug?

I'm running it on an Galaxy S6 and have the same issue.

I would like to try the beta. Galaxy S6 rooted. Let me know, Thanks!

@arthurhjorth well yes, my flux 22.0 on AOSP 4.4.4 Note 2 & Note 3 (2 devices) also has trouble using location although "GPS Test 1.3.2" finds me a 3D-fix after a couple of seconds. I assume developer relies on google location services framework to communicate?
That'd be a bad msg for aosp ...

I believe version 4.4.x and higher is supported, but my device is on 4.3 and indeed does not work.

@Manish-Mukherjee Be patient, but notify the devs with @f-lux-team .

Can confirm exactly the same bug with Sony Xperia Z3 Compact (model D5803, processor Qualcomm, Android 5.1.1)

Thanks for the hint. Using the superuser app I also checked the root status and found out, that the Fairphone 2 (unlike the Fairphone 1) is not rooted by default. Thats probably the problem ;)

@Tungsten_smooth The problem isn't the transition itself, but that it starts changing around sunset, which is at the beginning of my day. I work from 5pm to 5am, so I need it to start changing around 5am and go back to normal around noon.

@donutz With a name like "Fire" phone, that's just ironic!

@cstation Yeah, keep it on Tegra for sure then, the compositor will most likely eat your battery.

Hi. I am using Samsung Galaxy S4 LTE-A i9506 running on Android 5.0.1 and after I installed f.lux on my device, I open the app and it crashes and shows a black screen. I pressed the power button to lock my device and afterwards unlock my device back. I reopened f.lux and it is able to be opened but it is not working. The colour of my screen is still the same.

However, I tried to install f.lux on my brother's phone: Samsung Galaxy S4 LTE i9505 running on Android 5.0.1, it works perfectly. No bugs or blank screen after installing the app and its functions work. That is what I'm confused about.

Please fix this. Thanks.

I agree. I've been hoping for f.lux on Android for a long time as many others surely have as well.

Prior to this release I used Twilight which served me well for what it is. I've already retired it though.

The only thing I miss about it was the Tasker plugin support, specifically with regards to enabling and disabling it.

If dev wants my software and hardware info you my cpu is sd818 and lollipop 5.1 stock

I have continued to have the same issue of f.lux seemingly stop for a few seconds after any app is installed. Has happened four times now.

@salata I'm having the same issue with my 6P.