Related
All,
I realized after posting in the general app announcement thread that you/we Droid X users might want to be aware of this app written specifically for the Droid X (but might be useful to other phones too).
So, here's the link to the general app announcement thread and a brief summary of what this app is all about:
[App] BattMonX (Droid X Battery State Monitor via LED Status)
BattMonX is a utility for the Motorola Droid X to turn on the LED indicator light while the phone' screen is off to indicate its battery state: charged, discharging, or charged/full.
The Droid X does not currently indicate the battery charging state via the LED indicator light as other phones do.
This app is free in the Market. Search for "BattMonX".
This app is intended bridge that gap until such functionality is restored by VZW/Motorola.
QR code, screenshots, more details are in the link provided above.
Thanks and enjoy!
I missed this feature coming from my Blackberry thank you!
Sent from my DROIDX using XDA App
Ubermicro13 said:
I missed this feature coming from my Blackberry thank you!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
You are most welcome! Its been a fun project to work on. I hope to get the set-on-boot / run-on-boot thing figured-out soon. Stay tuned.
Coming from the HTC Droid Eris, I was used to this feature too.
There were lots of us on launch day that were posting as to whether anyone had a lit LED while the phone was being charged. I actually saw my LED light up (not through a text notification or anything) very briefly during the first OTA update we got, but never since then.
Anyway, glad to have finally learned enough Android programming to have made this feature available to folks. By the way, I've been keeping my discharging state LED color set to blue--looks cool .
Cheers!
nice idea but if you run a custom rom it usually adds this already without the need for another app. im running tranq and it has it
luke1333 said:
nice idea but if you run a custom rom it usually adds this already without the need for another app. im running tranq and it has it
Click to expand...
Click to collapse
Thanks for the feedback. I didn't know this (I'm still running stock 2.2 (although rooted)).
The app development request came from someone running ApeX, so it must not be in that particular ROM yet.
I'm a little curious as to why VZW/Motorola didn't include this support natively...
Anyway, cheers!
scary alien said:
Thanks for the feedback. I didn't know this (I'm still running stock 2.2 (although rooted)).
The app development request came from someone running ApeX, so it must not be in that particular ROM yet.
I'm a little curious as to why VZW/Motorola didn't include this support natively...
Anyway, cheers!
Click to expand...
Click to collapse
yeah no problem its a great app if you run stock 2.2 i agree 100%!!
I'm on Fission 2.2.2 and they don't light up either. Until now that is.
Sent from my DROIDX using XDA App
DRTMI said:
I'm on Fission 2.2.2 and they don't light up either. Until now that is.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Nice!
Thank you and cheers!
v1.3 just uploaded: now supports set-on-boot option
Just a quick thread bump to let everyone know that I've updated the app to version 1.3 that now includes a set-on-boot / run-on-boot option.
Select this option via the menu (menu -> More -> Set on Boot -> select True or False).
Enjoy!
By the way, thanks for all of the great feedback and support from everyone--its made creating this app for everyone worthwhile. I very much appreciate it! Cheers!
version 1.4 of BattMonX just published
Version 1.4 of BattMonX has been uploaded to the Market.
Changes to this version include:
* Support of five new LED color codes (dark orange, orange, dark violet, dark green, deep sky blue)
* Support for low-battery condition indicator:
selectable low-battery percentage threshold (10%, 20%, 30%, 40%)
action to take when threshold is reached (none, LED on, LED blink)
LED color selection for low-battery condition (will take precedence over other battery states)
Hope you find this app and these changes useful. Thanks for all of the great feedback!
Cheers!
v1.6 just uploaded: now works w/SMS text notifications
All,
Just a quick thread-bump to let everyone know about the latest release of the app: version 1.6 now works with SMS text notifications!
So now, you should be able to run the app all of the time and still get notified when a text message comes in.
The timeliness of the seeing the SMS notification is still dependent on the polling interval you are using, but app steps aside when the SMS notification comes in and then resumes when its been acknowledged (by reading the text) or cleared (by the notification pull-down's Clear button).
Please note that the app doesn't actually control the color or blinking status of the SMS text notification, my app just allows it to come in and been seen--so I cannot change its color or behavior.
I also added the option / ability to make the LEDs blink (or stay on like before) for the charging / discharging / charged state like the functionality I added for the low-battery condition in v1.4.
Enjoy the app and its recent changes--I hope you find the app useful.
Also, I do very much appreciate everyone's feedback and support! Thank you!
v1.7 just uploaded to Market (very useful fixes and improvements)
version 1.7 changes include:
- added strategy to auto-recover from Android auto-killing the app's service; should make the app much more stable and without unwanted shutdowns
- replaced multiple menu settings w/standard Settings/Preferences menu item
- dynamically determine battery status directory (I did this to see if the app would work on more phones (with mixed success); should allow for users that don't see that the app was written for the Droid X to at least see if it will work on their phone (does not appear to work on a stock HTC Evo 4G, HTC Droid Eris))
- re-instituted screen lock to portrait mode to prevent orientation change from causing FCs
- fixed integer parsing issue causing some reported crashes (probably just experienced by non-Droid X phones)
- added option for 3 minute polling-interval
- added larger range for low-battery percentage threshold
- fixed issue where LED would not blink when charging
Anyway, if you have any issues, comments, questions, etc., please contact me at [email protected].
Cheers and have a great New Year!
v1.8 just published to the Market
All,
I've just published version 1.8 to the Market and updated the main thread (http://forum.xda-developers.com/showthread.php?t=859651) with information and screenshots... Lots of new features and improvements. Change log for 1.8 includes:
- supported new experimental features:
* ability to keep LED on while the screen is on (root only)
* support white LED color when used with the "LED is Always ON" experimental (root-only) feature/setting
- updated w/better strategy for dynamically locating battery state and LED notification files to TRY to support non-Motorola Droid phones
- added 'Suspend' feature to turn off LED and pause battery status monitoring until resumed (un-checked)
- added strategy to make app more timely/responsive to SMS text notifications and preference/setting changes
- fixed set-on-boot and charging-color preference mis-match and other minor preference/settings issues (this was causing a few folks issues...if you still have an issue, try an un-install and fresh re-install--this will clear-out the saved preferences)
- supported amber LED color in addition to the original red/green/blue LED colors (for phones that support an amber LED color)
Anyway, this version should be much more stable and responsive than the prior versions (although v1.7 was pretty solid, ).
Enjoy, and please visit https://sites.google.com/site/scaryalienware/battmonx for full details and screen shots. Shoot me an email at [email protected] for any issues, comments, questions, etc.
Cheers!
v2.2 uploaded to the Market
Uploaded version 2.2 of the app to the Market last night. Here's the highlights:
- added more strategies for making the app more responsive when screen off & unplugged (I implemented a partial wakelock for one minute after the screen is turned off and unplugged from power source)
- added 'Set LED Colors by Percent Charged' feature (i.e., you can assign a different color to each 10% range of battery percent-charged)
- added 'Rainbow Mode' (under Fun Stuff) to cycle through the various LED colors
- added 'Keep CPU On' feature to allow you keep the CPU awake/on when the screen is turned off (this is only true when monitoring is active);
*** Warning *** use of this option will consume more battery!
- added preset-color buttons to LED color tester (easier to test main colors)
Hope you enjoy this new version.
Cheers!
Notes re. other versions not previously listed:
- v1.9 was just a very minor update to not display percent signs in menu items that was causing FCs in some Milestone phones running non-stock ROMs
- v2.0 was the original release of what is now v2.2; I had to rescind v2.0 to fix a loop (and the FCs) caused when using the color none/off under certain circumstances
- v2.1 was a re-publish of v1.9 until I could fix the FC issue in v2.0
Thanks again!
v2.3 just uploaded to the Market
New version just published.
Here's the change log:
Version 2.3 - 14-Mar-2011:
- support option to display status bar notification icon with battery percent charged
- support option to turn off use of LED battery state indication
- more accurate app behavior for Moto Droid-class phones via 1% charge delta vs. original 10% delta
- support blink action for monitor-by-percent charged mode (screen off only)
- additional logic to try to support other phones like Sony Ericsson Xperia x10 family
- lots of app cleanup; re-organized preferences / settings menus
Check it out and let me know what you think!
Cheers!
version 2.4 just published to the Market
New version just released. I hope you find these changes useful.
Cheers!
RECENT CHANGES (version 2.4 - 26-Mar-2011):
- app should now work on all Android devices by using system intents (now the default setting) vs. reading battery status files (still supported)
- supported low-battery condition sound or vibrate alert
- supported high battery temperature monitoring similar to low-battery monitoring (especially useful for those who overclock or tether)
- notification changes: make app launch when pull-down notification selected; option to allow notification to be cleared; add battery temperature & voltage to notification shade details
- make low-battery & high-temp monitoring independent from the two main monitoring modes
- show change log at first/fresh install
- revised menus to reference 'status' instead of 'LED' to indicate support of both status bar icon and LED
- fixed issue w/LED color none/off not showing status bar notification
- supported logging of trace messages to SD card file for debugging if needed
- added donate button
- lots of minor fixes and improvements
BattMonX v2.6 just published to the Market...quite a few changes this time around.
Here's the change log:
Version 2.6 - 1-May-2011:
- thanks to all who have donated or purchased the donate version (very much appreciated!)
- re-post LED notification when clear notifications button is pressed
- support special (green only) status bar icons with large number format percent charged values
- add support for time-based suspend schedules
- support status bar icons with lightning bolt charging indicator
- support option to toggle display of percent charged value in status bar icon
- support special large low-battery mode for batteries that don't calibrate well
- fixed issue w/noticing plugged vs. un-plugged re. display of lightning bolt in status bar icon
- revise / update application icon (sorry, had to remove the bat logo)
- make pop-up dialogs cancelable via back button
Looks like I forgot the v2.5 change log last time:
Version 2.5 - 29-Mar-2011:
- fix issue to handle 1% charge_counter file not always being present
- cleanup Current Settings screen (consolidated percent-charged settings info)
- added new debugging feature (ability to toggle app's logging of system messages)
BattMonX v2.9 published to the Market
All,
Version 2.9 of BattMonX has been uploaded to the Market. This version includes code to auto-recognize the 1% charge_counter file used on many Motorola phones. It also addresses the product-name changes that CyanogenMod ROMs impose that kept prior versions of this app from recognizing a Moto Droid family phone and auto-identifying their battery status and LED notification files.
Donate version of this app will be uploaded shortly.
Cheers and thanks for everyone's support and kind feedback.
RECENT CHANGES
Version 2.9 - 09-Jul-2011:
- improve auto-identification of charge_counter file (especially for Moto Droid X's running CM7;
this should also help other phones that support the charge_counter file)
- several minor updates and fixes
Version 2.8 - 13-Jun-2011:
- minor fixes to better support Moto Droid phones recent GingerBread 2.3 update:
* auto-recogize GB's different LED directory (w/o needing to manually locate files)
* fix LED-always-on reboot issue for Moto Droid's running GingerBread
* if you have problems or experience unusual issues coming from v2.7, please try an un-install and re-install
Version 2.7 - 22-May-2011:
- revised and improved service start/suspend/shutdown and notification clear handling
- cleanup current settings display and other logged values (especially debugging info)
- lots of minor cleanup and improvements
- turned off debug msg logging by default for fresh installs (option to enable is still present)
I'm not going to use this because I use my LED for other things, but its a great app. I tested it and it works great on my DX.
Tivo7 said:
I'm not going to use this because I use my LED for other things, but its a great app. I tested it and it works great on my DX.
Click to expand...
Click to collapse
Thank you very much for the kind words!
You can still use the mode where it will just display a status bar icon with the current battery percentage (just turn off the LED notifications in the menu settings).
Cheers!
Description
Get speed information and speeding alerts for your Google Navigation!
Trial features:
- Display overlay with speed information on your screen
- Display last two digits of your speed in notification area
- Choose between km/h and mph
- Starts automatically when connected to car dock
Pro features:
- Speeding alerts
- Smart alert volume adjusting to background noise
- Configurable speed overlay behaviour (hide, show only if Navigation is running)
- Trial notice removal
- And you will support independent developer and encourage me to add new awesome features!
This is a beta version supported via xda-developers forums, but e-mail communication is also available, especially for Pro users customer support.
Download
gMapsSpeed (Google Play)
gMapsSpeed Pro (Google Play)
Changelog
Code:
0.5:
- Since new version of Google Maps does not allow me to detect if navigation is running, the feature was replaced with "Only show speed overlay if Maps are running"
0.4:
- Due to new Google Play policies, PayPal payment option had to be removed
- Holo theme implemented
0.3:
- Fixed performance issues
- Option to hide notification icon
0.2:
- Market license support
Johny_G said:
Description
- Speeding alerts
Click to expand...
Click to collapse
What data are those based on? There's no speed data available in Google Maps so you do need some source to determine the allowed speed, what is that source?
Currently, it is the simple user-defined threshold system that is also used by some HUD-style applications, but I'm trying to implement something smarter for later releases .
hm, too bad, makes it pretty much useless
We will see what I'll figure out - having database of speeds is impossible with my budget, but I have some ideas how to make it better. But I personally use the threshold system, and it is actually not bad and it saved me from some unmeant speeding situations. And do not forget, that car's speedometer shows about 5% lower speeds compared to reality, so you know by sound when you reached the actual speed.
where i live there's no general speed limit but limits are different all the time (30,50,60,70,80,90,100,110,120,130) so manual tresholds just won't do it :-(
Oh, I see :-(
Just a small update today. The speed alerts will be improved later.
Changelog
0.2:
- Market license support
Like the app, just what I need. After minor update the app freezes however.
In what situation?
No exception. The first version worked flawlessly. This version gets stuck as soon as you open it.
Is there a way to revert to the first version? That one worked.
HTC Incredible S. Standard OS Android 2.3.5
Oh, I see it. Will resolve it ASAP.
Got a solution! I will implement one little feature and publish the update later today. Thanks for reporting!
Hey OP...
Quick question...I purchased the app in the market and on my phone i opened the beta app and registered it, now my question is why does the app in my app drawer still say beta? Did I not register correctly? Please help
The app is still in beta stage, but your purchase authorized you to use the Pro features. As it makes it to final version, you will get all the new features with no extra charge .
The update is here!
Changelog
0.3:
- Fixed performance issues
- Option to hide notification icon
App works again, performance issue fixed. Thank you for the swift response.
Found this app on the market and I have a question about the pro version. The main feature I like about pro is only showing the overlay when navigation is running. The only major problem is that it keeps the GPS active even if navigation isn't being used.
Are there any future plans for implementing a feature that will auto start this app when the navigation app is opened, along with closing it when navigation ends? This will prevent from having to manually open and close an additional app each time.
Sent from my SPH-D710 using xda premium
This is not easy to handle since Android does not tell you when app has been started. Only way I can think of is some service, but it might cause serious battery drain. But I can turn off the GPS if not visible. It might help.
I'd imagine, if it's possible it would only be for root users. I'm not a dev, just brainstorming really. The overlay looks great and it's 2nd to none right now.
Sent from my E4GT using xda premium
Hello, I want to introduce the Hold Screen ON app.
Bring a little bit of SGSIII opportunities to your phone
This application act as service and use front camera of your phone for human face detection. When the face is detected, the application will prevent the locking of phone's screen. Just keep the screen on while you are looking on it.
Key features:
This application uses your phone's camera only during the face scanning. By default, it is 3 frame every 5 seconds. Between these intervals, you can run any other application which can lock up and use the camera.
If your front camera have low resolution or small viewing angle, you can use eyes detection instead of face detection. Or all toghether.
The app can detect the phone rotation and respectively rotate image.
This is a Lite version. Therefore, application service's activity will be stopped after 10 minutes of continuous operation. Just restart the service, when it happens.
Requirements:
Android 2.3+ device with frontal camera
Download link:
play.google.com/store/apps/details?id=com.kkeyser.android.eyebuddy.demo
And the last:
I myself am the owner of the Note and often use my application. I think many will be interested in it. Of course, I am pleased to hear all your suggestions and comments
I used a similar app called ISeeYou and to be honest it didnt work so well for me,
Does this one work perfectly ? Dont want to be buying apps that dont do the job
Just try it and decide I post link to the free version. Unlike the ISeeYou, I use opencv library with face and eyes detections cascades. The benefits is a eyes detections (in addition to face detection). Disadvantages is apk size - now about 4 MB.
Update:
Version 1.27 is released.
New features and fixes:
Application binding: now you can describe app behaviour on all or one apps running.
Minor and major bug fixed
Hi trying the app now. It does not work in low light condition on the Note.
Any suggestions
Sent from my GT-N7000 using xda app-developers app
how is the battery usage with it?
Sorry, but in low light conditions any face detections app is lost. I try to improve detection algorhytms, but it can take some time.
About battery drain - mostly depends on scan interval. When screen goes off, the worker thread stops - run only when screen on (depends on app binding rules).
v1.32 is released
Version 1.32 is released.
New features:
Native (Android) face detection method implemented
Image histogram normalization was inplemented
New version
New release: 1.35
* Notification management
* Remove lag in the main app menu
* Legend on tap on preview image
This is when we say smart innovation bravo bravo bravo, perfect idea and perfect developing keep up mate...Thanks
New release
New release: 1.45
Applications binding feature
Light sensor support
Proximity sensor support
thanks for the application mate.
btw could u please tell me if we can configure fps?
regards
New release: 2.2
New version: 2.2
What's new:
Total UI redesign
Touch detector
Many bugs fixed = stability improved
P.S. I hope, new bugs is _not_ appears )
About
CF.lumen adapts the colors on your Android device based on the position of the sun, or your custom configuration.
When using the default settings, your display will get a warmer tint (lower color temperature) when the sun is down, vastly reducing strain on the eyes. This will take some getting used to, though! The colors also match closer to common artificial light sources, than the daytime light you get from the sun. Blue light makes your brain want to stay awake, and a lower color temperatures reduces the amount of blue displayed; using this in the evening also reduces your brain's effort to keep you awake at night, and can be beneficial to your sleeping pattern.
During sleeping hours by default a red filter is used. Red strains your eyes the least, and retains your night vision.
Light sensor
The light sensor can be used to automagically adjust the color: switch to the sleep filter in full dark, or to the day filter (usually none) under bright lights.
Because light sensor quality varies wildly between devices, a calibration option is provided. Most devices seem to work fine with sliders set all the way to the left, others need them to be set all the way to the right. Experiment as needed, but be warned that some devices simply cannot distinguish between evening indoor lighting and full darkness, and this feature may thus not work well for you.
Color filters
Several filters are provided. Those named after a color (red, green, blue, amber, salmon) do not limit the display to those colors, but convert the displayed image to grayscale first, then display that image in levels of the selected color, instead of levels of all channels (white). This preserves details that would otherwise be lost.
Grayscale, invert colors, temperature adjustment and custom R/G/B adjustment filters are also provided.
Colorblindness
The master color filter setting also has an option for colorblindness enhancement, with settings for protanopia/anomaly, deuteranopia/anomaly and tritanopia/anomaly. These options redistribute colors across the spectrum, in theory enhancing clarity and color detail.
No claims are made to the effectiveness of these filters, but positive reports have been received from testers. Also note that these filters were thought up by Google engineers - CF.lumen just includes them.
Pro version
Upgrading to CF.lumen Pro will support my developments, remove all nags, unlock the option to start at device boot (make sure you test your configuration first), and unlocks notification options. It also enabled Tasker integration.
In Pro mode, the notification adds convenient buttons to quickly disable the current filter or switch to sleep mode, and you can switch the notification to when enabled mode, which shows the notification only when a color filter is active.
In non-Pro mode, the notification only asks you to upgrade to Pro. It may seem that notification is just there to annoy you, but it actually prevents Android from randomly killing the background service taking care of all the work. Getting rid of it without getting the service killed can be done by going to Settings -> Apps -> CF.lumen and unticking Show notifications.
As in the past CF.lumen was part of Chainfire3D, if you have the Pro package of the latter installed, Pro mode will also be enabled.
Drivers
CF.lumen currently supports three driver backends to adjust the display: the original CF.lumen driver, the KCAL kernel driver, and the rootless (non-root) overlay. See the driver section below for further details.
Performance
When no color filter is active, there should not be any noticeable performance impact. When a filter is active, impact depends on device and what you are doing. On some devices we have tested there was no performance impact at all, on others it was slightly noticeable.
Performance characteristics change based on the driver you are using. See the driver section below for further details.
History
Nightmode - now called 'sleep mode' in CF.lumen - was actually the kick-off of Chainfire3D's development, and the later arrival of the original CF.lumen additionally containing the functionality to change color temperature based on the sun's position. Completely different (and no longer possible) techniques were used to get similar results. There were fewer options, and the filters limited display to the selected channels instead of the currently used much higher quality method of displaying luminance levels on the selected channel.
Future
Keep in mind that Android's rendering system changes over time. This app was possible in the old days of Android, and then wasn't possible for a long time. Only with KitKat did it become possible to make this work again. As such, you should be aware that this app may simply stop working on future Android versions without the possibility of a fix.
Scary permissions
By far most permissions are used only for Google Maps to set your location, and Google Play to provide for In-App Purchases. I cannot make any claims as to what information the Google components do or do not send to Google servers, but no information is sent to me or anyone else (than Google).
Download
Get CF.lumen at Google Play
It needs Android 5.0 Lollipop or newer!
Screenshots
Walkthrough video
GIF
Drivers
CF.lumen currently supports several driver backends to adjust the display: the original CF.lumen driver, the KCAL kernel driver, the PCC/RGB kernel driver, and the rootless (non-root) overlay. Driver selection will only be presented to you if multiple drivers are actually supported on your device.
Drivers: performance background
Software compositing is when your device takes the different surfaces on screen (the app's display, the status bar, the navigation bar, a popup window, these are all surfaces), draws them into a single buffer, then lets the hardware display this buffer. Virtually all modern devices can also do hardware compositing, where these different surfaces are presented to display hardware themselves, skipping one drawing step. It should be noted however, that hardware compositing only supports three surfaces (usually), so only the most basic scenes can be rendered this way. If more than the number of supported surfaces are displayed, the system falls back to software compositing automatically. Performance is slightly lower when this happens, but it happens all the time, and I doubt you've ever noticed it without looking for it.
One specific note about this is that "secure" content (DRM protected video rendering, for example) can only be hardware composited, as the software is not allowed to gain access to the surface. So if you are experiencing video disappearing, it's because the system has switched to software compositing. This can be due to CF.lumen's driver, a color overlay, or even just a system popup pushing the number of surfaces beyond the number of supported surfaces by the hardware compositor.
Drivers: CF.lumen
The CF.lumen driver requires software compositing, as it changes the colors displayed during the software compositing step. Of course, it lets the system go back to hardware compositing if it's not actively changing colors. This can slightly impact performance.
This driver changes colors on the surface content level, and can perform all sorts of calculus before deciding what to display. This usually gives it the highest possible image quality output. For example, in the color channel modes (red - night mode, green, blue, amber, salmon), the image is first converted to a luminance-based grayscale image, and then output in the selected color channels. This dramatically improves clarity and detail over only displaying the selected channels. Taking red mode as an example, this means that green and blue image content still shows up in a shade of red, whereas normally all colors devoid of a red component would show up as full black. Because of the surface-based manipulation, the invert filter may sometimes show unexpected results.
This driver affects both full-screen screenshots as well as app screenshots. Aside from normal screenshot/cast purposes, these are also used by the system for animations and in the recent task lists, and thus it may sometimes appear like a filter is applied twice during rotation or while browsing the tasks list.
Since v3.65 this driver comes in three different modes:
Drivers: CF.lumen: Compatibility mode
This driver mode should work on virtually all devices out there, however, on many firmwares it comes with an extra large performance penalty. Rendering quality is generally excellent, but various internal actions of Android itself (such as screen on, pattern unlock, app install, etc), as well as any app that triggers Android's accessibility options, may temporarily interfere with the rendering. This can cause a flash of the original colors being shown, instead of our manipulated colors.
Drivers: CF.lumen: Performance mode
This driver mode overrides Android's rendering system in a different way. While it doesn't work on all devices and firmwares, if it does work, it is often significantly faster than the compatibility mode. It also doesn't suffer from short flashes of the original colors being shown. This mode causes visible artifacts on some devices, though it isn't common.
Drivers: CF.lumen: Anti-flicker mode
This driver mode is a hybrid of compatibility and performance modes. It uses the same subsystem as performance mode, and thus it doesn't work on all devices and firmwares. This mode keeps the rendering from compatibility mode, but attempts to prevent the short flashes of the original colors being shown.
Drivers: KCAL
The KCAL driver is quickly becoming a popular kernel mod for Qualcomm devices. It allows color adjustments in the display hardware itself. There is no performance difference with this driver, but of course your kernel must support it. This is the fastest driver.
This driver changes colors on the display level, and is limited in the operations it can perform. It is fast, but the image quality can be less. In color temperature modes (probably your most used mode) there is no difference with the CF.lumen driver. In the color channel modes however, there is no luminance conversion. If you select for example the red mode, you will only see the red component of colors. Pure blue, pure green, or any color which is a mix of blue and green but not red, will appear black.
A gamma correction option is available for this driver. Some devices automatically gamma correct the values CF.lumen gives the kernel, the app needs to know about this, so it can take this into account in its calculations.
This driver affects neither full-screen screenshots nor app screenshots. It does not support the colorblind filter.
Drivers: PCC/RGB
This driver is very closely related to the KCAL driver, as they use the same hardware, so please read that section. Some kernels provide support for one but not the other. If both are supported, KCAL generally gives you a few more options than PCC/RGB, but there is no performance difference between the two.
This driver does not support the grayscale, invert or colorblind filters.
Drivers: rootless
The rootless fallback driver (for non-root users) uses a color overlay. This is an additional surface, causes at least one additional expensive full-screen rendering step, and is likely to throw your system into software compositing mode most of the time. This is the slowest (and ugliest) driver.
Image quality wise, it is no competition for the other drivers, but not everyone has root. Like the other screen color tint apps on the market (there are quite a few, and while CF.lumen is older than all of those, it is certainly not the best known or most popular one), a color overlay is used. Where the other drivers properly manipulate the displayed colors, this driver is more like putting a half-transparent colored sheet over a picture. While it somewhat does the job, it lowers contrast significantly.
On Android 6.0, various Android functions refuse to work when an overlay is present. This includes apps asking for permission, installing apps, etc. The app attempts to detect these situations and automatically turn off the filter. If you spot a situation where the filter is not automatically temporarily disabled, please let me know.
This driver affects only full-screen screenshots (but not full-screen animations), not app screenshots. It does not support the grayscale, invert, or colorblind filters.
Non-GApps firmwares
This app uses Maps for manual location setting, and Play for purchasing Pro. An increasing number of users do not have GApps, for privacy, security, and other concerns. If the app is installed on such a firmware, your location will be determined using the normal location API (without manual override, so your phone has to be able to determine your location). As I do not want to deprive anyone from the potential health benefits of sleeping better, the app operates in Pro mode if you do not have the Play store installed (PayPal'ing me beer money is always an option).
The APK is attached to this post for those not using Google Play (only).
Under no circumstances are you allowed to (re-)distribute this APK
(v2.00: 32, v2.05: 180, v2.10: 164, v2.16: 288, v2.25: 118, v2.40: 555, v2.50: 546, v2.60: 39, v2.61: 132, v2.66: 27, v2.71: 563, v2.74: 388, v2.75: 1042, v3.00: 4320; v3.65: 1376)
Changelogs
2020.12.22 - v3.74
- (c) 2020
- Remove references to G+
- Android 11 support
- Android 10+: Show warning about notification options not working
- Android 10+: Disable rootless mode
- Android 10+: Disable advanced/injection/anti-flicker/performance driver (needs further investigation to make work)
- Add foreground service permission
- Built for API 29
- Fix notification spam issue
- Fix maps crashing
2018.12.20 - v3.72-TEST
- Pie: Fix soft-bar transparency
- Pie: Fix boot-up launch
- Pie: Fix maps not working
- Pie: Fix greylist violations
- Oreo/Pie: Fix notifications
- Fix Magisk detection / root warning
- Fix system settings modification permission handling
- Fix location permission handling
- Fix performance driver injection on some 7.0 devices
- Fix several deadlocks
- Add option to detect which driver mode is the fastest
- Support for new KCAL paths
- Replaced root sockets with Binder-based IPC
- Removed colorblind options (available in Developer Options on all recent devices)
- Greyscale/Saturation filter: allow up to 2.0x factor (oversaturate)
2018.11.28 - v3.71-TEST
- (c) 2018
- Basic Pie fixes (far from complete!)
- Updated libsuperuser and librootjava
- CF.lumen performance driver: fixed injector for newer Android versions
2017.02.09 - v3.70
- (c) 2017
- Upgrade grayscale filter from a toggle to a saturation slider
- CF.lumen driver: fix 'performance mode' on Nougat (bypass new linker protections)
- CF.lumen driver: fix darken filter math issue (still doesn't work on invert, though)
2016.03.30 - v3.66
- CF.lumen driver: smoother filter switching
- CF.lumen driver in Performance mode: fix disable hardware overlays option sticking when CF.lumen is disabled
- Tasker: fix black screen on filter selection
- Tasker: fix brightness change on filter selection
2016.03.01 - v3.65
- Reworked raw remote control receiver
- Fix logcat spammed with notification errors regarding a missing icon
- Fix issue with "Bright light" setting
- Fix flicker on location update
- Reduce frequency of notification updates
- Add color checker to rgb/custom and temperature filter selection dialogs
- Underlined numbers next to sliders can now be tapped to input a text value
- CF.lumen driver: fix not closing properly when switching to KCAL
- CF.lumen driver: better monitor accessibility settings
- CF.lumen driver: added anti-flicker and performance modes
- KCAL driver: add gamma correction feature
- KCAL/CF.lumen drivers: Tune color temperature algorithm
- PCC RGB driver added
- Add "Darken filter" setting to "Brightness" option (sub-zero)
- Made "Brightness" setting on filter selection an icon
- Moved "Auto-update location" option to the Map activity
2016.02.18 - v3.62
- Fix driver not initializing on various devices
2016.02.17 - v3.61
- Slight performance improvement in root driver
- Change timeout handling code in root service
- Fix background ANR
2016.02.16 - v3.60 - RELEASE NOTES
- Play release of v3.53
2016.02.16 - v3.53 BETA
- Add notice to reboot first after installation if old driver found
- Fix some options in the settings screen not being disabled when they should be
- Adjust light sensor calibration texts and min/max values
- Add option to auto update location (enabled by default, passive listener, no power use)
- Add welcome message
2016.02.13 - v3.52 BETA
- Fix issue with system-based SuperSU
- Fix old driver not always being reset when switching drivers
- Fix KCAL driver not always resetting when setting to disabled (screen power cycle also works)
- Fix rootless overlay being applied twice on service restart
- Periodically and on certain actions, reset color matrix
2016.02.08 - v3.51 BETA
- Fix grayscale channel rendering
- Allow master mode without location
- Improve Marshmallow doze/standby handling
- Fix filters sometimes not showing on initial setup in Rootless mode
- Added warning if drawing over other apps is disabled in M+Rootless mode
- Added capability to detect permission dialogs and hide overlay in M+Rootless mode
2016.02.08 - v3.49 BETA
- Should work again on MIPS
- 4.4 support dropped, now 5.0+
- Fix FC on SuperSU prompt
- Completely new CF.lumen driver code
- Improved driver switching
- (C) 2016
2015.10.28 - v3.16
- Detect Enforcing SELinux without supolicy availability and warn user
2015.10.27 - v3.15
- Fixed a case of the new root driver not being injected (and thus nothing happening)
2015.10.26 - v3.11 BETA - RELEASE NOTES
- Fixed freezing issue
- Fixed Note5 (and others?) support
2015.10.19 - v3.10 BETA - RELEASE NOTES
- New root driver method
- Adjusted slider layouts
- Dropped MIPS support
2015.02.24 - v3.00 - RELEASE NOTES
- (C) 2015
- Added KCAL driver (see XDA thread for details)
- Added Rootless driver (see XDA thread for details)
- Added freeload option
- Backuptool script updated (requires un-/reinstall of driver to become active)
2014.12.22 - v2.75
- Change notification flags
- Fix driver detection issue which could lead to bootloops on devices with symlinked busybox
- Work-around one case of bootloops, detect that case, and warn about it
2014.12.02 - v2.74
- Fix remote control issue
2014.11.19 - v2.72
- Fix issue with in-app billing
2014.11.14 - v2.71
- Hide notification from (secure) lockscreens on L
- Check free space before installing driver
2014.11.06 - v2.70
- Tasker integration (Pro only)
2014.11.05 - v2.66 - RELEASE NOTES
- Android 5.0 fixes
- 64-bit fixes
- Performance improvement
2014.10.22 - 2.61
- Fix UI bug where settings wouldn't open sometimes
2014.10.22 - 2.60 - RELEASE NOTES
- Fixed a name issue with the recovery installer
- Automatically restart service when app is updated
- Expanded theme options, including material (basic)
- SELinux policy patches for LPX13D
- Experimental support for arm64, x86-64, mips64
2014.07.02 - 2.51
- Fix: ignore light sensor triggered sleep if forced awake during sleep hours
2014.07.01 - 2.50
- Installer fixes for latest AOSP
- Installer fixes for Android "L" Preview
- Added wake button to notification during sleep mode, which goes to sundown mode and is the default tap response - in contrast to disable, which disables all filters and is the default tap response while not sleeping
- Fixed issue where starting CF.lumen would not start the driver/service when not using Pro, and nothing would happen regarding screen colors, no matter which buttons you push
2014.04.16 - 2.40 - RELEASE NOTES
- Added brightness control to filters (actionbar option)
- Added option to wake from sleep mode when an alarm goes off
- Added option to install via custom recovery
- Added backuptool support (survive custom ROM nightlies) - un/re-install driver to activate if coming from an older version
- Fixed setting sleep filter to disabled using day filter at night instead of sundown filter
- Fixed filters occasionally sticking while modifying settings
2014.04.14 - 2.25 - RELEASE NOTES
- Various UI tweaks
- Added gradual filter fading, configurable for sunrise, sunset, sleep and sensor events
- Added notification icon options (keep notification but hide icon)
- Added light sensor based wake from sleep option
- Added driver update needed notification
- Added option to switch between light, dark, and device themes
- Added quick toggle menu items to main activity
- Improved (Pro) notification behavior - en/disable now default tap option when active
- Fixed kelvin and R/G/B choices not being saved between filter selections
- Fixed "Upgrade to Pro" from notification sometimes not working
- Fixed text wrapping on light calibration dialog
2014.04.11 - 2.15
- Fixed driver installation problem when using Superuser instead of SuperSU
2014.04.11 - 2.10
- Fixed crash on driver (un)install
2014.04.10 - v2.05
- Fixed a number of force closes
2014.04.10 - v2.00
- Initial public release
Is there any practical difference between this and Lux?
Sent from my Nexus 5 using XDA Premium 4 mobile app
rlaw said:
Is there any practical difference between this and Lux?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
See walkthrough video on YouTube, and you will get the answer.
Sent from my Nexus 4 using Tapatalk
Is it possible that you could add Tasker compatibility? If not, are there public intents available to control cf.lumen through Tasker intents? Thanks for updating this great app.
EDIT: The latest update(s) fixed my problems. Thanks CF! Will buy if I like the app after a few days of use.
BUG:
I would love to include a logcat, but I simply don't have the time today or tomorrow. If needed, I'll post one this weekend.
When the app runs for the first time: grant su access, then I see the "please install cf.lumen driver". I click install, device reboots after a few secs, after reboot I wait for some time before opening the app again. When I open it, it asks me the same thing: install the driver. Wasn't the driver installed, or doesn't it detect the driver?
PHONE: Nexus 4, ROM: Paranoid Android 4.2 BETA 4 (that's Android 4.4.2 if you don't know), KERNEL: franco.Kernel #204.
On my first try I had Nexus Display Control (also by Franco) installed. My guess was the apps aren't compatible. After uninstalling both apps, reboot, installed cf.lumen again, install driver, reboot: same problem. So for now no cf.lumen for me. Just eye strain.
I hope this helps you find the bug or incompatibility I have!
4.0+
Excellent, and we need it for Android 4.0+
No love for 4.1 - 4.3 makes me a sad panda
kodirovshchik said:
Excellent, and we need it for Android 4.0+
Click to expand...
Click to collapse
+1. Although I favour the cool-factor and performance of custom ROMs, it's always nice to be able to get a similar experience on stock ROM (which is ICS for me), considering that there are no stable custom ROMs on my device at the moment. I'm actually in the midst of custom ROM development for my device, though I work on CM10.2. (There are others who work on KitKat). It would be much appreciated if the @Chainfire could add support for lower Android versions.
rlaw said:
Is there any practical difference between this and Lux?
Click to expand...
Click to collapse
Seems to me (haven't actually tried), Lux (like several other solutions) uses an overlay for things like colortemperature and nightmode, which usually gives a lot worse image quality.
It's auto-brightness features on the other hand should work fine, and is something not really available from CF.lumen. Maybe one day one app will also be able to control the other.
jackattack said:
Is it possible that you could add Tasker compatibility? If not, are there public intents available to control cf.lumen through Tasker intents? Thanks for updating this great app.
Click to expand...
Click to collapse
This is not available right now, but I've added it to my to-do list.
erikieperikie said:
BUG:
I would love to include a logcat, but I simply don't have the time today or tomorrow. If needed, I'll post one this weekend.
When the app runs for the first time: grant su access, then I see the "please install cf.lumen driver". I click install, device reboots after a few secs, after reboot I wait for some time before opening the app again. When I open it, it asks me the same thing: install the driver. Wasn't the driver installed, or doesn't it detect the driver?
PHONE: Nexus 4, ROM: Paranoid Android 4.2 BETA 4 (that's Android 4.4.2 if you don't know), KERNEL: franco.Kernel #204.
On my first try I had Nexus Display Control (also by Franco) installed. My guess was the apps aren't compatible. After uninstalling both apps, reboot, installed cf.lumen again, install driver, reboot: same problem. So for now no cf.lumen for me. Just eye strain.
I hope this helps you find the bug or incompatibility I have!
Click to expand...
Click to collapse
A logcat will not help for this (its not a crash) - we'll need to investigate some other way. Can you confirm /system/lib/libcflumen.so is present?
SirBindy said:
No love for 4.1 - 4.3 makes me a sad panda
Click to expand...
Click to collapse
Codename13 said:
+1. Although I favour the cool-factor and performance of custom ROMs, it's always nice to be able to get a similar experience on stock ROM (which is ICS for me), considering that there are no stable custom ROMs on my device at the moment. I'm actually in the midst of custom ROM development for my device, though I work on CM10.2. (There are others who work on KitKat). It would be much appreciated if the @Chainfire could add support for lower Android versions.
Click to expand...
Click to collapse
If I could easily do this, I would, but I can't, so I won't.
Chainfire said:
A logcat will not help for this (its not a crash) - we'll need to investigate some other way. Can you confirm /system/lib/libcflumen.so is present?
Click to expand...
Click to collapse
Same issue here on N4 running CM11 M5 4.4.2. I do not have the system/lib/libcflumen.so file. I tried pressing install and reboot a couple of times to no avail.
Edit: just got an update from the play store. Ironically this update that says it fixes force closes now causes the app to force close when pressing ok to install the driver. Using ART by the way.
It does not seem to work at all in Cm11. It crashed once but even when it does not it don't change anything. It does flicker a small black square though.
The app crashes when I tap okay for the driver installation. I am using a Nexus 4 on 4.4.2 SlimKat build 3 with Matr1x 13.5 kernel and ART. I've added a Logcat for you, not sure if I did it right, let me know if it doesn't contain all the information you need. I think ART might be breaking it.
Max Dark level - 100
Min Bright level - 250
Could you change Min Bright level to 101? Its logical, and I really need it on my nexus 7 2013.
Or, even better, could you make dynamic Max Dark/Min Bright level?
Max Dark - ( N ),
Min Bright - ( N + 1 )
I also get fc after driver install on cm11 with my vs980. No work:/
Sent from my LG-VS980 using Tapatalk
I stand by XXCoder and tacosdelicioso on the CM11 issue. App crashes when asking for reboot, soon after permissions are given. I am running ART, FYI.
Enviado de meu XT925 usando Tapatalk
Dante897 said:
The app crashes when I tap okay for the driver installation. I am using a Nexus 4 on 4.4.2 SlimKat build 3 with Matr1x 13.5 kernel and ART. I've added a Logcat for you, not sure if I did it right, let me know if it doesn't contain all the information you need. I think ART might be breaking it.
Click to expand...
Click to collapse
Happens the same to me. Using latest temasek v64, devil's kernel and dalvik.
FCs on me as soon as I press OK to restart to install the driver. Happens every single time. Restarted manually and opeed it up again and same thing
Night light is an open-source app which uses KCAL to adjust blue light intensity of the display colors, so that viewing the screen at dark becomes pleasant for the eyes, and help you fall asleep faster (this is what science have proven so...).
Features
Easy to use user interface. Settings are easier to find.
Uses KCAL to adjust screen RGB colors, hence its efficient and changes are seen everywhere on screen.
Supports older KCAL implementations as well as newer KCAL implementation for v4.4 kernels.
Simple color controls for normal users through color temperature control.
Manual KCAL controls for advanced users.
Automation routines lets you define routines where you specify Night Light settings which you wish to apply, and they will be automatically applied for you in specified times.
Intensity fading in/out is supported as part of automation routines.
Supports sunset/sunrise timings.
Set on boot delay.
Original KCAL settings of user is backed up and applied when night light is turned off. And it can be configured as well.
Support for user profiles, which are collections of settings that user can apply with one click.
And to fulfill your all kinds of automation needs, app is supported as a Tasker plugin. You can use it with Profiles.
Option to automatically disable Night Light in lock screen, and turn it back on after the device is unlocked.
Quick Setting tile for easy toggling on/off night light anywhere.
Launcher icon shortcut for toggling Night Light on/off and toggling intensities.
Dark and Light theme.
Advantages
No overlays.
Background service is only used for lock screen option. The entire automation (including the fading) is done using neat AlarmManager tricks (which not only is battery friendly, but memory friendly as well).
Requirements
Kernel supporting KCAL.
Root access.
Download
Source - https://github.com/corphish/NightLight
Wow. Thanks for this awesome app. This is my best daily night light app.
Thanks
sounds good
let me have a try brother......
corphish said:
Night light is an open-source app which uses KCAL to adjust blue light intensity of the display colors, so that viewing the screen at dark becomes pleasant for the eyes, and help you fall asleep faster (this is what science have proven so...).
Features
Easy one touch toggles, with a single slider to tweak blue light intensity.
Quick Setting tile for easy toggling on/off night light anywhere.
Automatic switching on/off night light at user specifed timings. (Limitation - Start time must be lesser in value than ending time, that is if you choose starting time at 2300 hrs and ending time at 0600 hrs (next day) it won't work for now).
Requirements
Kernel supporting KCAL.
Root access.
Download
Source - https://github.com/corphish/NightLight
Click to expand...
Click to collapse
The automatic switch doesn't seem to be reliable. Could you add intents so it can be toggled with Tasker? I already have a profile that triggers at sunset so that would be perfect.
Sent from my Nexus 5X using XDA Labs
Great app, thanks. Have been using CF.lumen until now, but that seems unsupported (and is closed source).
Please keep improving it. Would also like to donate a beer.
Can you explain whats this KCAL thing ??? ??
thanks for this app apreciate it i got ADD and Slightly Autism and i already have an issue sleeping my brain get supercharged and i can't get to sleep but this app helps [email protected]
Loving the app so far, however, I notice it won't trigger at the time I have set unless I manually open the app. I've removed it from Android's battery optimization so I don't think that can be it. Any ideas?
rickysidhu_ said:
Loving the app so far, however, I notice it won't trigger at the time I have set unless I manually open the app. I've removed it from Android's battery optimization so I don't think that can be it. Any ideas?
Click to expand...
Click to collapse
Same here. I forgot to report it. I use Tasker to launch it at sunset & sunrise along with switching between dark / light app themes.
Sent from my Nexus 6P using XDA Labs
yochananmarqos said:
Same here. I forgot to report it. I use Tasker to launch it at sunset & sunrise along with switching between dark / light apo themes.
Click to expand...
Click to collapse
I ended up doing this as well! Now the other thing I'm hoping gets implemented is a smooth transition to the orange hue.
zaibansari20 said:
Can you explain whats this KCAL thing ??? [emoji848][emoji848]
Click to expand...
Click to collapse
Kcal is a kernel tweak that lets you customize colors at lower (kernel) level, so there won't be any filter or layer on screen, but in most stock kernels it isn't available, so you have to find a custom kernel for your phone/rom that has it.
Thanks for the app, but I've used tasker with the command "echo 180 75 35> /sys/devices/platform/kcal_ctrl.0/kcal" for a long time (echo 256 256 256 > /sys/devices/platform/kcal_ctrl.0/kcal to get the color back.)
Obviously you can change the values to whatever you want.
But the app will be much more easy for many people
Envoyé de mon ONEPLUS A5000 en utilisant Tapatalk
J0kker said:
Kcal is a kernel tweak that lets you customize colors at lower (kernel) level, so there won't be any filter or layer on screen, but in most stock kernels it isn't available, so you have to find a custom kernel for your phone/rom that has it.
Click to expand...
Click to collapse
I'm using LineageOS with a custom kernel which allows mein to change RGB values from any kernel modification app...
Sent from my LG G2 using XDA Labs
zaibansari20 said:
I'm using LineageOS with a custom kernel which allows mein to change RGB values from any kernel modification app...
Click to expand...
Click to collapse
So it should work for you, you can try with a kernel manager like kernel adiutor but the app should work.
J0kker said:
Kcal is a kernel tweak that lets you customize colors at lower (kernel) level, so there won't be any filter or layer on screen, but in most stock kernels it isn't available, so you have to find a custom kernel for your phone/rom that has it.
Thanks for the app, but I've used tasker with the command "echo 180 75 35> /sys/devices/platform/kcal_ctrl.0/kcal" for a long time (echo 256 256 256 > /sys/devices/platform/kcal_ctrl.0/kcal to get the color back.)
Obviously you can change the values to whatever you want.
But the app will be much more easy for many people
Envoyé de mon ONEPLUS A5000 en utilisant Tapatalk
Click to expand...
Click to collapse
I tried the Tasker method and it works great. I had no idea that command existed and could be used in Tasker. Thank you for sharing! :good: :highfive:
rickysidhu_ said:
Loving the app so far, however, I notice it won't trigger at the time I have set unless I manually open the app. I've removed it from Android's battery optimization so I don't think that can be it. Any ideas?
Click to expand...
Click to collapse
Does it fail to trigger if a reboot had happened sometime before the time it should have triggered?
For example, if it was to trigger at 5pm, but a device reboot happened in, say, 3pm, then does it fail to trigger at 5pm?
Anyway, set on boot is broken (again), will need to fix it, but normal timers should work fine.
corphish said:
Does it fail to trigger if a reboot had happened sometime before the time it should have triggered?
For example, if it was to trigger at 5pm, but a device reboot happened in, say, 3pm, then does it fail to trigger at 5pm?
Anyway, set on boot is broken (again), will need to fix it, but normal timers should work fine.
Click to expand...
Click to collapse
Ahh, that might be it. I think it stops working after a reboot, so I'd be going back into the app to get it going again.
Very minor issue though, great app - thank you for your hard work!!:highfive:
corphish said:
Does it fail to trigger if a reboot had happened sometime before the time it should have triggered?
For example, if it was to trigger at 5pm, but a device reboot happened in, say, 3pm, then does it fail to trigger at 5pm?
Anyway, set on boot is broken (again), will need to fix it, but normal timers should work fine.
Click to expand...
Click to collapse
Launcher shortcut (toggle on/off) switch is also seems somewhat broken, it toggle on but fails to toggle off.
@jineshpatel30 @rickysidhu_
Here is an experimental version (in the attachment of this reply), with launcher shortcut toggle and set on boot fixed.
The reason why it is experimental :
- Now written in kotlin
- Uses some of the new stuff announced in I/O 18, like ktx and the new material design style
- Uses different font called 'Acme'. (Feel free to suggest fonts)
- I decided to ditch cards because normal layouts look better in this new style.
Source - https://github.com/corphish/NightLight/tree/p
corphish said:
@[email protected]_
Here is an experimental version (in the attachment of this reply), with launcher shortcut toggle and set on boot fixed.
The reason why it is experimental :
- Now written in kotlin
- Uses some of the new stuff announced in I/O 18, like ktx and the new material design style
- Uses different font called 'Acme'. (Feel free to suggest fonts)
- I decided to ditch cards because normal layouts look better in this new style.
Source - https://github.com/corphish/NightLight/tree/p
Click to expand...
Click to collapse
It kicked in automagically at sunset tonight which reminded me to come back and comment. That was unreliable previously.
What does the save button do at the bottom? I assume it saves something, but there's no toast message to acknowledge it's been pressed.
I don't like the font, myself. Since you're going for new and fancy code and styling, why not use ProductSans? I like the new font used in the Wear OS app, I think that's it.
Could you add the numerical values for the sliders for more accurate fine tuning? I like the way the new XDA Navigation Gestures app does it. It's in the latest beta posted in the thread and should be pushed to the Play Store soon.
Since CF.lumen is EOL now, this app is going to be a great alternative especially when it eventually breaks.
Thank you!
Sent from my Nexus 6P using XDA Labs