I'm having trouble with Background App Refresh triggering, in addition to an URL scheme as suggested by another user can help alleviate the issue perhaps a slider widget in the Today section of Notification Center can also help quick management.

I know as the night goes on I like to make the screen warmer and warmer, so a Today widget would also help in that regard.

Thanks so much for open-sourcing this. My eyeballs and sleep cycle are grateful!

Added preparations for background refresh without depending on the iOS background refreshing using this solution.

This solution could also enable a transition animation equally to f.lux.

Also a small design change: App is now longer named "GammaTest" on SpringBoard but "Gamma Thingy"

Would it be possible to include automatic change of color based on user location? solar.c from redshift source (GPLv3) should help in implementation of this function.

Recently I saw some discussion here on this problem. Right now we use background refresh to check if the screen temperature must change, however this isn't very reliable, because it requires the screen to be enabled to change the colour. Now the latest problems with battery of the Facebook app set me thinking. What if we let the background fetch determine whether it's time to switch, and as soon it's time to switch we enable 'Audio background' playing. This allows the app to change the screen colour as soon as the device is unlocked, because it can continuously run in the background. We disable the 'Audio background' thereafter to keep the battery usage to a minimum. I might be wrong on this idea, because I've never played around with the 'Audio background' mode. What do you think?

It would be awesome if the app could support URL schemes, so we can automate dimming with Workflow/Launch Center Pro!

(Disclosure: I'm not an iOS dev, no idea how easy this would be but I think it would be a perfect addition! Also, this would be a nice place to say: my eyes thank you for the app, it's great! :) )

Hello,

I'm new to this so sorry if it is a stupid question, but when I open GammaTest.xcodeproj in Xcode 7.0.1, I get a yellow triangle with an exclamation point that said "Applications using launch screen files and targeting iOS 7.1 and earlier need to also include a launch image in an asset catalog." I have OSX 10.10.5 and am trying to install GammaThingy on an iOS 9.0.2 device. I also get another warning, an exclamation point in a stop sign, reading "No provisioning profiles found: No non-expired provisioning profiles were found." It then says "Failed to code sign" when I attempt to build on the device, prompting me to "Fix Issue". It goes through a loading screen and then says "An App ID with Identifier 'me.thomasfinch.GammaThingy' is not available. Please enter a different string." and does not complete the build. How can I resolve this issue? Thanks for your time and for building this.

I just discover with iOs 9.3 beta 5 that the Redshift option is not available on my first generation ipad mini!!!! Seems it will not be available on any older 32bit tablet/phone because of a performance issue!!! I never add performance issue with Flux or Gammathingy... Apple marketing...

ld: warning: directory not found for option '-F/Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk/System/Library/PrivateFrameworks' ld: framework not found IOMobileFramebuffer clang: error: linker command failed with exit code 1 (use -v to see invocation)

#33 introduced a basic widget. I've been looking into a full widget. Since this required quite a bit of more work, I made this a new PR.

UI and functions are simple but it's a good base to work from. I've been running this for a few days and it's quite stable.

Main Changes

App Groups

Extension and host app live in separate processes. They can only talk by using App Groups. Changing to app groups requires a bit of work:

• Enabling App Group Capability for both host and extension.
• Adding a group identifier, usually group.<main bundle ID>.

Problem: As with the main bundle ID, it seems we can’t share a group ID. Everyone has their own. The best I came up with:

• Adding a project setting APP_GROUP_IDENTIFIER for everybody to set their group ID.
• In code, getting the identifier from the Info.plist.

NSUserDefaults

• To share defaults, now use [[NSUserDefaults alloc] initWithSuiteName:<group ID>] instead of standardUserDefaults. I added a category so we can just call [NSUserDefaults groupDefaults].
• Call [defaults synchronize] when making changes.
• It seems NSUserDefaultsDidChangeNotification won't get delivered between widget and app.

GammaController

App and widget have their own GammaController class which write to their own gammatable.dat file. This leads to the problem where the widget initializes its file with already modified gamma data instead of the default screen values (or vice versa). It will then use this wrong data as the base level for adjustments.

I changed it to write the gammatable.dat into the shared app group space. Works for now but is not protected against concurrent writes. Although it's unlikely widget and app will write at the same time, this should be resolved. Maybe there is a better solution altogether that does not clutter GammaController with app group related stuff.

Problem

The group ID stuff increases the barrier to entry for users who just want to install the thing. You now have to: (see linked screenshots)

• Add custom bundle ID to the main app (as before)
• Add custom bundle ID to the extension
• Create a group ID, add it to both main app and extension
• Insert the group ID into the project setting

I'm open for contributions and happy to change stuff as needed.

See also #14, #33.

App is crashing when checking "Enabled".

Crash reports below.

Running iOS 9.2 on iPhone 6S.

This is very similar to crash in GammaThingy fork GoodNight reported here.

When enabled is set to 1 and you reboot and open Gamma Thingy again the enabled switch is active but the effect is not present.

Workaround: Turning enabled off and on again does help for now.

Possible solution: Adding logic at application launch that checks for the state of enabled.

Any chance that there'll be a URL added to enable/disable Darkroom Mode? I ask because I saw that there's now an orangeness URL to enable/disable the orange filter.

I'm sorry if this is a silly question, but I feel it's warranted despite the simplicity of the app: if I turn on the scheduled activation will it only work if I manually hit the enabled switch? It would appear so whenever I enable the schedule. It often doesn't yellow the screen until I manually enable the app, regardless of the time of day.

Thanks for your work on this :)! I was able to use it previously, but since your latest commit, I'm getting an "EXC_BAD_ACCESS" on this line and am unable to use the app: error = IOMobileFramebufferGetGammaTable(fb, data);

In GammaController.m. Can you look into this?

After installing on my iPhone and deleting the app the orange filter still remains.

Powering off and restarting the phone returns the screen to normal but as soon as I reinstalled the app and tuned on the filter again, it was like I had two filters on at the same time, one permanent and the other controlled by the app.

The result is that, using the app, I can increase the orange level up to extremely orange but I am not able to turn it off.

Is there a way to undo this and return the app and my phone to normal behaviour?

Even after disabling the tweak there is a light red tint that covers the whole screen ( which is different from the orange tint). (iPhone 6+ 9.0.2) Maybe a mixup with restoring the original gamma tables?