Related
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
Code:
*** Disclaimer
I am not responsible for any side effects (if any) or damages (if any) caused by this application.
This is not a 100% systemless app. If you are having problems, please just uninstall it then reboot.
Introduction
Created in the midst of a broken heart, HEBF Optimizer is an application that aims to increase the performance of your device, also by focusing on battery performance, we didn't forget it.
The application also features a useful and smart toolbox that you can use whenever you want.
"HEBF" stands for "empty heart, full battery"
Click to expand...
Click to collapse
Images
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features
VIP Battery Saver:
VIP Battery Saver puts your device into a deep battery saving mode by setting the CPU governor along with several other parameters of your choice such as force-stopping apps ("hibernating"), forcing the device into idle state (doze) and disabling checked features (WiFi, bluetooth, etc). VIP can be used with Tasker to be triggered in certain events or scheduled within the app itself. It is a very useful option if want to keep your device alive as longer as possible.
Game Booster:
In contrast to VIP Battery Saver, this Game Booster ramps up the CPU to obtain better instant performance. It can also trigger the DnD mode and force-stop apps as well to avoid interruptions while gaming.
This is also a root toolbox:
HEBF provides a nice interface for power users to tweak their device. There are some advanced stuff like the Window Manager, ART Compiler Filter and well known stuff like a CPU and RAM Manager, Fstrim and a Cleaner section. There are also several general battery, performance internet twaks you can apply, all within a single app.
Click to expand...
Click to collapse
Installation instructions
Make sure you meet the requeriments:
Android 4.1+
Root access (although the app has a rootless version, it will be dropped out soon)
Download and install the .apk file or get the app in Google Play. See below get the downlod links.
Click to expand...
Click to collapse
Changelogs
Code:
Current version: 2.4.6, 2020-07-18
[new] Added Kernel Panic switch
[new] Added option to activate VIP Battery Saver when the screen goes off
[changed] CPU Manager is now deprecated and will be later removed, please use SPKM instead
[changed] Removed DPI Changer, please use the Window Manager instead
[changed] Removed VIP Profiles
[changed] Overall improvements to VIP Battery Saver behavior
[changed] Updated Games database
Click to expand...
Click to collapse
Downloads
Note: Android File Host build may take longer to be updated. Please use XDA Labs instead.
Download
Google Play | XDA Labs | AFH
Click to expand...
Click to collapse
Thanks to/Credits
Code:
* @Lennoard
* Android VIP
* Beta Testers and translators
XDA:DevDB Information
HEBF Optimizer, App for the Android General
Contributors
IvsomEmidio, Lennoard
Source Code: https://github.com/Lennoard/HEBF
Version Information
Status: Stable
Current Stable Version: 2.4.6
Stable Release Date: 2020-07-18
Current Beta Version: 2.3.5
Beta Release Date: 2019-11-16
Created 2016-06-18
Last Updated 2020-07-18
Downloads
Play Store (Stable Version)
2.2.0 available on beta
HEBF Google+ Community
Facebook Page
HEBF Blog
Reserved
Changelogs:
1.0.1b
Second beta release
Now HEBF notifies you when the thumbnails size is over 300Mb!
Fixed Force Close when switching to Landscape mode
Tweaks revisions
Added Force connection type indicator
Color changes
Text revisions
Added more cleaner options
Collapsing AppBar Layout on About screen. The new FloatingActionButton takes you to the build folder at AFH
HEBF now verifies whether the necessary files exists and shows a warning if does not
Updated credits
Updated licenses dialog
v1.0.2b
Third beta release
Attempt to fix Force Close bug at the first time (By asking for READ first)
Fixed and improved busybox detection (We hope so) Thanks to @Omario-242
Updated translations
We started to work on lighter performance tweaks
Source code clean up (Partial)
Application log (/system/etc/HEBF/app.log) (@Marília de Oliveira) BR
v1.0.3
v1.0.3 Released
HOT: Fixed FC due storage permissions on Android 6.0+ FOREVER
Now I don't need to kill myself
Changelog:
4rd beta release
Fixed Force Close bug at the first time (No luck before)
Version changes
Library updates
Updated translations
Fixed notification icon size
Added clean thumbnails at boot
v1.0.4 Pre-Stable
*Hot:* Added German translations by @VenityZ
*Hot:* Added profiles menu
Improved application's performance
Updated Tweaks (Thanks again to the myth @Paget96 for his mythness)
Small color changes
Improved dialogs look
Fixed notification icons
Removed cleaner scripts at boot
Removed strange shadow above the toolbar
Improved ART Fix Switch system
v1.0.5
Updated Tweaks
Added Kernel Panic
Added Settings screen
Fixed battery calibration dialog
Separated faster boot into 2 options
Removed tweaks Cards if they don't match with the Android version
Improved tweaks explanations (more coming real soon)
v1.1.2 (Especial Version)
Updated tweaks
Improved descriptions
Added widgets, check them out!
3 options for the Floating Action Button at the Main screen, check them out!
Added Force English language on settings
Better management of new versions: if a new version is installed, a notification will ask you to copy the files again
Added Power saver for multicore CPUs
Decreased margins size on landscape mode
DPI Changer and Hostname changer now show the current value as a hint
Added manufacturer's bloatware remover (Limited)
Force copy option now shows a progress dialog
New options for Google Play Services drain fix (Experimental)
WhatsApp files cleaner now shows the current size of the folders
Reduced necessary thumbnails size for a notification to show
Added Low Memmory Killer - minfree manager
Added Reduce in-call delay
Added Better rendering quality
Added use GPU for rendering
Added TCP tweaks
Added Google DNS
Added Better 3G connection
Added NET tweaks
Added Improve browsing
Added Better streaming
Improved block buttons layout
Improved CardView's ripple effect
Bug fixes
v1.1.4
Fixed problems with root access
Fixed problems with profiles and infinite progress dialogs
Fixed problems with the introduction of the application, which suddenly ends sooner than expected making an error appear asking to copy the files again.
General improvements for 4.4-
Other bug fixes.
v1.3b
Updated German translations by Christof Schäfer
Added Russian translations by XDA Member @Hanabishi Recca
Added tablet layouts
Added Telegram and Screenshots Cleaner
Added Low RAM Device flag
Adblocker updated
Improved application performance
UI and design changes
Improved navigation
Better support
General improvements for everyone on 6.0+
Bug fixes
v1.5.1- Hanabi
Fixed issues for 4.4-
Added a Build.prop Editor [Advanced options]
Added a Run as Root option [Advanced Options]
FStrim updated
Prevent service to be killed on boot so it can be finished correctly
Fixed back button not working for some screens
v1.5.2- HNOH
- Non-launcher shortcuts for apps [Android 7.1]
- DNS Changer added [Advanced Options]
- Entorpy Manager added [Advanced Options]
- Adaptive LMK control added
- Added Fsync control
- Design and layout changes
- Added a splash screen
- Enhanced logging [Settings]
- Small changes of information
v1.5.3
- Presets added to Build.prop editor
- Low Memory Killer updated (improved logic + apply at startup)
- Game Mode Removed
- Game Booster added
v1.5.4 (PLAYSTORE BETA)
Battery information
Notification improvements
Spanish translation reviewed by Alekss Ro
Initial Hindi translation by XDA Member @sohamsen
Added Turkish translation by Umut TURUNÇ
Hint for current DNS [Manual DNS @advanced Options]
Layout changes
v1.5.4-March Rain
Added presets for build.prop editor
Updated Low Memory Killer (RAM management profiles + improved logic + apply on boot)
Battery information
Spanish translation reviewed by Alekss Ro
Initial Hindi translation by XDA Member @sohamsen
Added Turkish translation by Umut TURUNÇ
The return of the SELinux switch
Notification improvements
Hint for current DNS [Manual DNS @advanced Options]
Layout changes
Removed Game mode
Game Booster added
Logging improved
Code improvements
2.0.0 FÊNIX
[!] Preferences were reset, some settings may have been lost
New Intro screen
Added a dashboard screen
Added a device info screen
Added a CPU Manager screen (basics for now)
Changed colors: The blood color of my broken heart is red, not pink
Decreased margins size
You can now stop HEBF services individually
You can now schedule fstrim and select which partitions to trim
Improved Game Booster and its widget
Improved ART Compiler Filter option
Improved VIP Battery Saver
added a widget and a Quick Settings Toggle
Improved Backup / Restore: you can now share, import or export a backup as a configuration file. It also supports directly opening confuguration.zip files
Moved uncategorized options to the "Tools" screen
Removed Wi-Fi sleeper
Added Wi-Fi Settings (user lvl 3)
Added Instant Doze option (6.0+)
Info about the DNS server (External link)
Better logging system
Google Play Services Drain Fix is back with a different approach
Widgets updated
Updated Settings screen
Liquid Smooth UI updated
Lots of bug fixes including:
/data/data junk size not being shown
Crash due permission denied errors
Root shell
Fsync path
Whatsapp cleaning failure
ANR while reapplying changes
Text not being shown in some small screens
VIP Battery saver improviments and new UI
Game Booster UI
Tweaks UPDATED
And much more (See GitHUB)
2.2.0 MATE
[!] Preferences were reset, some settings may have been lost
HEBF Account and its features; login using it or your Google Account
AppOps (if supported)
Auto start Manager
Create, save, restore and share backups using the Google Cloud
Quickly disable data, WiFi, location, bluetooth and sync to save battery
CPU Manager improved (added support for big.LITTLE - still a bit buggy )
CPU Tunables edit mode now adapts for numerical input
Doze idling mode selection
Whitelist / blacklist apps for Doze
Unforce idle button
Cleaner improved
Cloudflare DNS
Updated ART Compiler filters for Android 8.0+
Adaptive icon for Android 8.0+
Build.prop Editor improved (search props, better non-prop detection, fixed permission denied issues)
You can now create a script from scratch in the Scripts Runner
Scripts Runner will warn about scripts containing "sleep" and "exit" commands
Sysctl\'s navigation improved
You can now schedule mediaserver kill
You can now open .hebf files to restore a backup
Layouts for landscape mode and tablets
Boost widget
New white theme
HEBF Emulated Command Line
Root processes will be opened less often
Initial support for non-rooted devices
Themes improved
Fixed some problems with the settings screen
Other bug fixes
ROOTLESS Now Avaliable
Auto Optimizer job
and much, much more.
Tweaks summary
Fstrim
Discards "trims" unused blocks on a mounted filesystem, reducing the lag by running
Code:
fstrim -v /cache
fstrim -v /system
fstrim -v /data
using the fstrim binary (duh ).It is recommended that you fstrim at least once in a week.
Zipalign
Optimizes the android package files (and its uncompressed data) alignment. It is not "necessary" on 5.0+ apks
Let us quote developer.android.com :
Zipalign is an archive alignment tool the provides important optimization to Android application (.apk) files. The purpose is to ensure that all uncompressed data starts with a particular alignment relative to the start of the file. Specifically, it causes all uncompressed data whitin the .apk, such as images or raw files, to be aligned on 4-byte boundaries.
[...]
The benefit is a reduction in the amount of RAM consumed when running the application.
Click to expand...
Click to collapse
AdBlocker
[COLOR="#A400"]Not avaliable in the Play Store version, and may not be here for too long.[/COLOR]
Modifies the hosts file (/system/etc/hosts) to block all the advertisements, including in-app ads.
Faster boot
Sets the shutdown mode to hibernate and enables the Quick Power On feature, speeding up the boot time.
Disable bootanimation
Reduces the boot time by disabling the bootanimation (It may seem that your device will not turn on correctly, but it is normal).
Improve battery
Avaliable for 5.0- and 5.0+ (yes), Optimizes the Wi-Fi scan interval, enables the power saving mode, disables the error reports without performance impacts to improve your battery life.
Google Play Services drain fix
Not avaliable in the Play Store version.
Fixes the battery drain caused by some of the Google Play Services background services.
WARNING: IT WILL DISABLE THE SERVICES, ENABLE THIS OPTION ONLY IF YOU ARE OK WITH IT AND IF YOU ARE EXPERIENCING DRAIN.
Avaliable services:
Location
Check-in
System update
User report
Reenabling the services may take some time, please be patient
Wi-Fi Sleeper
Increases your battery life by controlling, preventing and scheduling the Wi-Fi to switch itself on/off.
The value set for WiFi idle wait is 15 seconds
Power saver for multicore CPUs
This CPU balance attempts to run the workload in the system on minimum number of CPU packages and tries to keep rest of them idle for longer duration, helping other packages to be in idle state and save power.
First, it checks whether your device has the power suspend mode and then set the value according to your selection to ys/kernel/power_suspend/power_suspend_mode
Let's quote android.com
The power states of the system on a chip (SoC) are: on, idle, and suspend. “On” is when the SoC is running. “Idle” is a medium power mode where the SoC is powered but doesn't perform any tasks. “Suspend” is a low-power mode where the SoC is not powered. The power consumption of the device in this mode is usually 100 times less than in the “On” mode.
Click to expand...
Click to collapse
And kernel.org:
The kernel supports up to four system sleep states generically, although three
of them depend on the platform support code to implement the low-level details
for each state.
The states are represented by strings that can be read or written to the
/sys/power/state file. Those strings may be "mem", "standby", "freeze" and
"disk", where the last one always represents hibernation (Suspend-To-Disk) and
the meaning of the remaining ones depends on the relative_sleep_states command
line argument.
Click to expand...
Click to collapse
Note that in Android is a bit different but the thought is the same
Disable manufacturer bloatware
Not avaliable in the Play Store version. Currently only available for Sony
Freezes some useless packages and applications, you choose which.
Performance tweak
Enables the performance tunning mode, decreases the colors number to 16bpp (16 bits per pixel) and optimizes the "fling" velocity (smooth scroll) for a general improvement with minimal impact on battery.
The 16bpp mode is most noticiable in darker areas.
Best Multitasking
Tunes the Low memory killer parameters for a better multitasking profile, based on the amount of RAM available.
Gaming mode
Optimizes the FPS limit, enables purge of assets and frees more RAM for performance improvements in games.
Reduce in-call delay
Reduces the delay to receive or end a call
Better scrolling
Might drain
Improves the scrolling responsiveness and speed.
Liquid smooth UI
Can drain
Optimizes the touch pressure scale for improved user interface elements.
Improve rendering quality
May drain
Optimizes the screen composition properties and enables overlay UI mode for a better graphics quality.
Use GPU Acceleration
Will drain
Enables the hardware accelerated UI, forces GPU screen composing and disables the vsync for a much better performance at the cost of battery.
TCP tweaks
Improves various TCP values for the IPv4 protocol such as timeout and sockets reuse.
Use Google DNS
An public alternative to your current DNS provider. Google DNS (8.8.8.8 and 8.8.4.4) will improve the security and speed up the browsing.
Guess what, it is free.
Improve 3G speed and signal
Improves a set of RIL and HSDPA properties, prefix and GPRS classes to improve the quality of the connection.
Improve browsing speed
Tweaks for the buffer size of the connection types, from LTE to GPRS. Results in a better browsing experience.
Better video streaming
Tweaks for the stagefright (the Android media library, not the bug). Results in smoother video streams.
Force connection type indicator
Attempts to force the connection indicator to show (The 4G/LTE, H+, H, 3G, E or in some unfortunately cases, G icon on statusbar). Requires a AOSP or AOSP based Custom ROM.
ART Fix
Only forAndroid 5.0+
Sets the dex2oat as interpret only, making the applications load faster.
The dex2oat is the new runtime since Lollipop, it compiles the dex file directly so your processor can execute the code natively. This process to take the dex and prepare for a direct process is called OAT.
According to Google, interpret only would skip all compilation and relies on the interpreter to run code. This should cause:
Apps will load faster as dex2oat won't touch the code again, so, no more waste of storage too.
There will be less time to that screen "Optimizing app X of X"
Battery calibration
Calibrates your battery by erasing the batterystatus.bin file generated by the Android OS containing battery statistics (which sometimes gets corrupted). YOU MUST ONLY CALIBRATE WITH BATTERY LEVEL AT 100%.
Kernel Panic
Kernel panic is an action performed when the system detects a fatal software / hardware error from which it can't recover. Similar to the blue screen of death, of which I was victim. (Dayumm :/ )
Disabling it may slightly reduce lags and avoid random reboots.
Disable logging
If you don't want to see the Android striving to record everything that is happening in all applications, enable this option.
Some say that this can save battery...
SELinux Changer
Tries to changes the Security Enhancements status (SELinux) by running
Code:
setenforce [ ]
On Android 4.4 and later, the default value is enforcing, unless changed by a custom kernel.
DPI Changer
Changes the LCD density. Smaller values are equal to larger screen space
Default DPI for some screen resolutions:
Code:
240x320(ldpi) - 120
320x480(mdpi) - 160
480x854(hdpi) - 240
540x960(hdpi as well) - 240
720x1280(xhdpi) - 320
1080x1920(xxhdpi) - 480
Warning: Please disregard the above information if you are running this application on a Tablet.
Hostname Changer
Another extra feature to change the hostname (the device's name when connected to a Wi-Fi or Ethernet network).
The default name is someting like android-0d02d3352rd2
See:
The best App for tweaking! ❤
God job, my team! ?
Nice APP! It helped me so much
Sent from my Moto G 2014 using XDA-Developers mobile app
DeluxeMark said:
Nice APP! It helped me so much
Sent from my Moto G 2014 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank you, please keep an eye on it and report anything you judge necessary!
Would be possible to add a section for RAM manager? It was perfect
Sent from my Moto G 2014 using XDA-Developers mobile app
DeluxeMark said:
Would be possible to add a section for RAM manager? It was perfect
Sent from my Moto G 2014 using XDA-Developers mobile app
Click to expand...
Click to collapse
We're looking into it with the "profiles" concept but please, formalize the feature request here
Crashed on first start up on my Sony Xperia Z3 with Android N Preview 3
Did a restart of the app and it seems to work just fine.
Somehow it doesn't detect the busybox installation as it constantly gives
out the error message (I have sterricsons busyboy installed and updated).
Enabled a few tweaks here and there,
Will probably give feed back if I notice any improvements.
Omario-242 said:
Crashed on first start up on my Sony Xperia Z3 with Android N Preview 3
Did a restart of the app and it seems to work just fine.
Somehow it doesn't detect the busybox installation as it constantly gives
out the error message (I have sterricsons busyboy installed and updated).
Enabled a few tweaks here and there,
Will probably give feed back if I notice any improvements.
Click to expand...
Click to collapse
This crash is due storage permission being reseted for some reason, just in case it still remains crashing, check it on Settings.
We'll put it on FAQ soon.
About the busybox... That's a problem. Is it installed at /system/xbin?
And finally, Android N support is currently not guaranteed so surely there is work to be done
Thank you for your feedback, we appreciate your help
Lennoard said:
The crash is probably due the storage permission for some reason being reseted. Just in case it still remains crashing, check it on Settings
About the busybox... That's a problem. Is it installed at /system/xbin?
And finally, Android N support isn't guaranteed so surely there is work to be done
Thank you for your feedback, we appreciate your help
Click to expand...
Click to collapse
Doesn't chrash anymore, even after a reboot.
About busybox, it is installed to su/xbin (default on N?) tried to change it int the installer to system/xbin but it doesn't work.
Will it affect the app as it can only access system/xbin?
Than N isn't fully supported yet is clear to me
I like to experiment with beta apps!
EDIT: I now simply copied the busybox file from su/xbin to system/xbin and it seems to work,
at least there's no error pop up anymore
Omario-242 said:
Doesn't chrash anymore, even after a reboot.
About busybox, it is installed to su/xbin (default on N?) tried to change it int the installer to system/xbin but it doesn't work.
Will it affect the app as it can only access system/xbin?
Than N isn't fully supported yet is clear to me
I like to experiment with beta apps!
EDIT: I now simply copied the busybox file from su/xbin to system/xbin and it seems to work,
at least there's no error pop up anymore
Click to expand...
Click to collapse
Niiiiiiiiiice Hacky solution it's cool because it will work lol
You can also check by typing
Code:
busybox echo "Testing"
on the terminal, check where the terminal is grabbing the binary to work (generally /system/xbin & bin so that's why that question)
Peace bro
EDIT: you *might* have to chmod and chown the /system/xbin/busybox
Code:
mount -o rw,remount /system
chmod 755 /system/xbin/busybox
chown 0:2000 /system/xbin/busybox
mount -o ro,remount /system
Lennoard said:
Niiiiiiiiiice Hacky solution it's cool because it will work lol
You can also check by typing
Code:
busybox echo "Testing"
on the terminal, check where the terminal is grabbing the binary to work (generally /system/xbin & bin so that's why that question)
Peace bro
EDIT: you *might* have to chmod and chown the /system/xbin/busybox
Code:
mount -o rw,remount /system
chmod 755 /system/xbin/busybox
chown 0:2000 /system/xbin/busybox
mount -o ro,remount /system
Click to expand...
Click to collapse
It already has the right permissions and owner set up.
But the terminal command dosn't seem to work.
Not a single reaction after typing the commands
Testing... Nice work ??
Sent from my D5803 using XDA Free mobile app
---------- Post added at 11:26 AM ---------- Previous post was at 11:18 AM ----------
Gave FC to open the application later after the application worked correctly.. How can I find out the directory of the application Log?
Sent from my D5803 using XDA Free mobile app
Omario-242 said:
It already has the right permissions and owner set up.
But the terminal command dosn't seem to work.
Not a single reaction after typing the commands
Click to expand...
Click to collapse
It should print what is inside the double quote
Lennoard said:
It should print what is inside the double quote
Click to expand...
Click to collapse
Either I'm stupid or my device, now it works
But that does'nt tell me which of the busybox installations is used (system/xbin or su/xbin), does it?
Marília de Oliveira said:
How can I find out the directory of the application Log?
Click to expand...
Click to collapse
The full log of the app isn't stored, according to Google, it can lead to performance issues. (Not sure about that G)
But, you can grab the logcat using the "CatLog" app from the post #4, then you just add a "hebf" filter and start the app again
Peace
EDIT: We will add the log storage in the next build, it's beta anyway
---------- Post added at 04:43 PM ---------- Previous post was at 04:26 PM ----------
Omario-242 said:
But that does'nt tell me which of the busybox installations is used (system/xbin or su/xbin), does it?
Click to expand...
Click to collapse
Well, I've made a test.
Moved the busybox to su/xbin (This folder doesn't exist here :v)
And the terminal is returning this on the attached image
So, if you typed busybox echo "Test" and it returned "Test" correctly, the system is using the path that actually works whatever it is.
So if the shell can do it , I think there's no problem with su/xbin.
I'm gonna just add a exception on the busybox check Fragment on the app and there we go
New Beta Uploaded : 1.0.2b
See changelog for more details!
1.0.1b and 1.0.2b are with FC bug on Android 6.0+ at the first launch we are working on it plase wait for v1.0.3b
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Google Camera Mods
Hi everyone. Finally i'm happy to say that i've successfully fixed/ported/changed 3 different version of Gcam that are fully working for our device! This versions are based on @miniuser123 , @Arnova8G2 and @oganyan-arthur .
First of all i'm not a developer i'm just a student of electronic engeneering that enjoys taking pics and that enjoys much more Google's Camera than Samsung's one!
I struggled a lot to make those apk working (that is == to waste time instead of studying for my courses ) beacuse i've never been into this field so don't expect anything more from me.
How to Install
Steps:
- Uninstall your current version of Gcam
- From smart manager clean up the memory (YES, sometimes it's needed beacuse after i tried a lots of different verisons of Gcams i messed up something more then the app cache itself)
- Install the app
- After the first setup close (or better force close) the app to apply all the settings
- Done!
V8.3b Base
Stability: Medium
v0 Features:
- User friendly version with remade settings menu and some stability improvements
https://drive.google.com/open?id=1KxDUQsYJkfttKlvLDU4HAC5ciHKBPGkl | Mirror
Stability: Good
v1 Features:
- Some extra setting (RAW funcitons, Lens Blur Nexus 6 HDR config)
- Completely changed settings menu with new icons
-Change descriptions and added some to have a better understanding of the menu settings (No-ZSL means that value wouldn't apply if you are on ZSL mode)
-Set to best configuration for our device (If you need to take photo with moving objects change Auto-exposure mode) to something faster
-Removed some dependencies from google for less ram consumption
-Some stability improvements
https://drive.google.com/open?id=1qBSYDJeWCmDAvcgLByy6B3t-rfVB1dSm | Mirror
Stability: Good
v2 Features:
- Merged all the v8.2b extra featuers so i removed it (Hope no more people will ask what is the best verison :angel: )
-Removed some slow shutter option that where unstable but there are new ISO options now
-Now Lens blur and portrait are usable both (not need to deactivate one or another)
-Added toggles for snapdragon users that had pink portrait problems and to fix white level
Clean install is a MUST. After the first boot of the app make sure you force close and re-open it
https://drive.google.com/open?id=13Uyifaqd4XvltCYj-H-TFVOfk5usEdp2 | Mirror
Stability: Good
v2.6 Features:
- Removed the time max exp stuff
-Added Slow shutter x2, x4 (x8 wasn't stable at all) and also the ISO are still there
-removed some unstabled option (lens blur 12mp option still cant sermove the 60 fps in video option so it wont work)
-fixed the higher exposure
-as always i set best settings to deafult based on what people report me
-disable hexagon like @cstark27 suggested the interface could be more smooth
Clean install is a MUST. After the first boot of the app make sure you force close and re-open it
https://drive.google.com/open?id=16wzZIEx3_zJ7wPxgJgksEo-iRz-AQoB8 | Mirror
Stability: Good
v2.8 Features:
-fixed slow shutter (let me know)
-added x8 again seems a bit more stable now. But still sometimes you get into blackscreen
Clean install is a MUST. After the first boot of the app make sure you force close and re-open it
https://drive.google.com/open?id=1FDdektLylUNz6azqUghTLas3M-FbmG_9 | Mirror
Stability: Good
v2.9.2 Features:
-Added 12.6 MP Lens Blur
-Changed some noise reduction code that could increase the definition of the photos
-Changed allocated mem to test if it's a little bit faster the processing
-Added italian language (and soon probably spanish and french)
-Rearranged a bit the menu the have to most used stuff on the very first settings menu
https://drive.google.com/open?id=1Qu_90fKH5_EiDM8v6nzCl2ATfEMPtFpa | Mirror
Stability: Good
3.1 Features:
- Added "wavegenerator" lib that allow higer ISO values
-Changed allocated mem again so that the app should not allocate unneeded RAM
-Added languages ES,FR, PT-Brasil,RU (thanks to @jujusito @Sergey @corentin @samoel and all who helped for translation)
-Rearranged a bit the menu the have to most used stuff on the very first settings menu
-Added bitrate settings for video(still 60 fps don't work) you can go up to 100 Mbps
-Other minor changes
I aimed to do a no config apk for exynos s8. That means that now you don't have to restart or forceclose the app after the clean install to set the settings. Everything should be ok now the only issue i found is that sometimes, after the first install only, beacuse i forced the camera selector to choose Pixel 2017 HDR, the app may crash but just after the first install and in no other situation.
https://drive.google.com/open?id=17lqzEVmhVdZllSQG56GBJBpnjV62Jw5Y | Mirror
Stability: Good
3.1.2 Features:
-enabled by default "temporal binning". Can improve processing time
-fixed the exposure of HDR+ enhaced mode on front camera for s7 users
-changed the Very High HDR config. Now will take a fixed burst of 20/24 (Pixel 2017/Nexus 6) processing time is longer but we can try to compare the result with (8/10 burst). As always you MUST restart the app to apply those settings!!
https://drive.google.com/open?id=1qGNVtTXgc1dGE-eoA9tmQAwvhTgysgVW | Mirror
Stability: Good
3.2 Features:
- Now you can select the path where to save the photos (doesn't work on sd card but probably can work with some xposed mod. I've tried to make it work with a magisk module and it works but the preview in gallery is broken).
- Removed all the snapdragon toggles. The app will know when apply that settings (if i forgot some devices just PM me with your device CODENAME and i'll add it or tell me what are the config. you use for your device)
- Removed custom denoise param and other settings
-Now the app will restart every time you go back from settings to the viewfinder. This means that you don't need anymore to restart the app to apply settings
-Now there are three gestures in the viewfinder:
1. double tap on the black area it will pop the exposure menu directly
2. long-press on gallery and it will open samsung gallery instead of google photos
3. long press on the switch camera and after the restart the viewfinder brightness will be set to maximum
- some minor changes and dark theme now as default theme
https://drive.google.com/open?id=1mblLEviff-PXvAhM5NcDSSFkwFjancb0 | Mirror
Stability: Good
3.2.7 Features:
-Fixed black level front,back camera for Samsung Galaxy A devices
-Enabled ois by default (for me works anyway) for s7 users
-Added saturation options in Advanced hdr+ settings
https://drive.google.com/open?id=168iA9cSe-UKCOIu2e2JxA_djdgPZOd7w | Mirror
Stability: Good
V8.3b Base Update
3.2.9 Features:
-Fixed black level back camera for Samsung Galaxy A8/A8+
-Fixed OIS
https://drive.google.com/open?id=1NDLxsUejxYimRyBpaDlzMA3FyKA6nbLq | Mirror
Pixe2Mod Base
Stability: Good
v6 Features:
- Fixed and working potrait mode (I may have broken it for SD variant)
https://drive.google.com/open?id=1z0cGbvZ2GoaSpPxAzPkHoxcycSfhyhEG | Mirror
Stability: Good
v 7 Features:
- Fixed black screen for some exynos devices
- Removed slowmo
- Flash is still not working for some reason. I need more time to look into this.
https://drive.google.com/open?id=1Zss2E-2r98HYzRzuaG61dzXEyXV-ip_g | Mirror
AR Stickers for Oreo
Steps:
- Install AR Core first https://play.google.com/store/apps/details?id=com.google.ar.core&hl=it
- If you can't download from playstore download from here https://www.apkmirror.com/apk/google-inc/arcore/arcore-1-1-180312068-release/
- Then AR Stickers https://drive.google.com/open?id=1kP98vuJR9bPdecBOzVeWPLNsgQb5YwjF
- Force close Gcam and re-open it!
- Done!
FAQ - Frequently Asked Questions
Q: Why the app is not installing?
A: Make sure you uninstall first the previous version
Q: Why i'm getting "parsing error" or errors when i try to install the apk?
A: Download the apk with the browser and NOT with the Drive app or use mirror links.
Q: Why i have still pink potrait mode?
A: Follow the Install instructions.
Q: Why slow-motion/ 60fps (or whatever you want)
A: Because i don't see the point of doing videos with Google Camera Ports beacuse Samsung camera it's doing a good job on that.
This doesn't mean i wont fix them either.
Q: On the device XYZ the app is not working.
A: I only support S8/S8+. I know on other Exynos devices it works (N8,S7,S6) so maybe i can take a look for them. If you ask for everything else i will just ignore your report.
Telegram Group
https://t.me/joinchat/CaDORE32mqEN45EflrK7rA
Donations
If you are cool and you want support me for this work you can donate with the "Donate" button or https://paypal.me/IDAN1109.
A little bit of boring theory
Introduction
Everyone in this thread is asking for what are the best options? The short answer is default. The long answer is it depends. To get the best results out of this mod you need to understand what all the options are and how they work. It is more similar to a professional camera where you have all the strange options to play with and you don't know what they do. You start changing all the values and then when you take a picture you are like "wut is this i took a picture of this beautiful panorama and it looks like a Picasso painting". To avoid that situation keep reading this post so you can understand what i'm talking about.
The basics
First of all before taking any picture you need to clean the lenses you are going to use. This seems to be trivial for someone but this are the results if you don't do it.
Clean vs. Dirty
The settings
Here you can find the explaination of what the settings do and how they work. I will add more in the future. If you don't know what shutter speed is or ISO google is your friend.
-Config. HDR+ camera
Nexus 6 HDR+ Auto: more dynamic range and quality (less noise). You can set all the Auto-Exposure modes but as downside you have the shutter lag so you should be careful to find the right time to shoot a photo with moving objects.
-Pixel 2017 ZSL HDR+: (ZSL = zero shutter lag HDR+)
Less dynamic range, and more noise in low light because slow shutter mode is NOT available. However it is much better in good/medium light if you make photos of moving objects, because it processes images already taken in the background. In low light, or high contrast scenes please use Enhanced HDR+
-HDR+ parameters:
It is recommend using one of the Pixel 2017 options, because they should be more stable regarding memory leak.
"High", "Very high" and even "Default" leak memory if pixel 2017 config is used.
Description for "HDR+ parameters": for example 8/10 burst means that HDR+ operates with 8 shot bursts. Portrait mode (ZSL) operates with 10 shot bursts at most. In my personal opinion Low or Very Low HDR+ are very similiar or equal to High or Pixel values but people prefer higher values for reasons uknown.
-HDR+ Auto-Exposure mode No-ZSL:
Everything that is No-ZSL means that will not work if "Pixel 2017 ZSL HDR+" is set for the back camera!
If you want to use custom Auto-Exposure and HDR+ for front camera you have to disable "Portrait ZSL mode".
"Slow shutter" will decrease shutter speed as much as possible in bad light. The result: much lower ISO and noise. Of course fast moving objects will probably get blurry more easily.
Slow shutter x8 is not stable for front camera but you can use x4 or x2. The max exposure time is 1/3 for the slow shutter x4.Sometimes you can get in trouble with x4 if you take a picture then you look at the gallery (black screen). But you wont have any problems if you take multiple pictures and then switch to x2 and look ad the gallery.
Selecting "Stock camera2 api" will get rid of rainbow effect, but dynamic range is poor, because camera can't underexpose fast enough if auto shutter control is on.
-Antibanding modes
Anti-banding allows the camera to avoid problems caused by artificial light sources that are not constant (flicker for want of a better description) these are typically florescent tubes but also multiplexed bulbs and PWM controlled LED’s (and your TV screen for similar, if not quite the same reasons) These sources cycle (flicker) fast enough to go unnoticed to the human eye, appearing continuous, they key word here being human. The camera’s eye (its sensor) can still see this flicker.
Only select 50hz or 60hz (dependig on where you live) in case of banding problems, because it can cause suboptimal shutter speed otherwise! Works up to 1/149 sec shutter speed.
-Denoise strength for HDR+ and portrait
Self explanatory. It will increase the denoise strenght for higer values.
For front cam you need to select about 2-300% to really see the difference. Back cam is much more sensitive to this setting.
-Underexposure multiplier (HDR+ dynamic range control)
Reduce below 100% to decrease rainbow effect. Should also overexpose if set to 0 with a good light source. Higher values means lower exposure.
-Samsung specific metering modes
Touch to expose is enabled by default. So won't have the touch to focus option. With "Centered" mode it will focus what it is in the center and then you can adjust the exposure by touching the area! This is a good option beacuse if you want to get the best results from HDR+ you'll need to adjust the exposure only and not the focused object at the same time.
-Samsung Live HDR mode:
Adds some dynamic range to modes where HDR+ is not available like zero shutter Portrait mode. No Rainbow effect in HDR+ mode if this is selected, but noise is encreased if isn't used in place where you don't have a good light source!
-Custom White Balance:
You can lower greens, or whatever colour you want (This would affect HDR+ ONLY). Adjust it accordingly to your taste!
Below some good photo shared on telegram group some of them can have some post-production
https://ibb.co/bGBhW7
https://ibb.co/gQurPS
https://ibb.co/gczrPS
https://ibb.co/nneQjS
What is the difference of the version 8.3 beta published by miniuser123 with the one published here?
Pixel ZSL mode now works on s8 now in this model.
If u can eliminate the processing time in s8 oreo, it would be great. Earlier in nougart it took much much less time to process afterwards. But since oreo it takes abt 10 second to process the photo after clicking.
Also if u can get slow shutter x4 and x8 working properly in low light.
Anyway thanks for your time.
Which are you recommended for HDR and portrait?
How can i enable RAW on the mod8.3b Variant ? Thanks for your hard work!
Can u add mirror selfie also.
cogelindo said:
What is the difference of the version 8.3 beta published by miniuser123 with the one published here?
Click to expand...
Click to collapse
It's written if you look at the description in features. I remade the menu and set the standard working config for s8 so no config are needed. Also i remove some debugging code
gtrs36 said:
Which are you recommended for HDR and portrait?
Click to expand...
Click to collapse
Idk try yourself i like the pixel 2 HDR+ but HDR+ of 6p looks sharper. i would say 8.2 or 8.3b but also pixel2mod is much more stable
lucccas942 said:
How can i enable RAW on the mod8.3b Variant ? Thanks for your hard work!
Click to expand...
Click to collapse
Maybe i can add it i need to look for it
@IDan1109 Thanks man.
raj.ayush78 said:
Pixel ZSL mode now works on s8 now in this model.
If u can eliminate the processing time in s8 oreo, it would be great. Earlier in nougart it took much much less time to process afterwards. But since oreo it takes abt 10 second to process the photo after clicking.
Also if u can get slow shutter x4 and x8 working properly in low light.
Anyway thanks for your time.
Click to expand...
Click to collapse
I think slow shutter x2 forces shutter speed to 1/4 so it makes it slower when shooting it also makes the camera driver default sometimes crashes because it is not auto sensor, especially if backlight conditions are very difficult to force into a speed of 1/4 so sometimes do not want to take pictures .. btw if you want slow shutter x4 and x8 work in lowlight try to increase underexposer to 200. coz underexposer value gives the signal a dark light condition, the higher the darker the camera is to run the slow speed for the shutter to brighten the photo.
If any one dont mind then i can ask something?
What is ZSL?
Din-Ace said:
If any one dont mind then i can ask something?
What is ZSL?
Click to expand...
Click to collapse
Zero Shutter Lag
Basically it takes photos very quickly.
S4turno said:
Zero Shutter Lag
Basically it takes photos very quickly.
Click to expand...
Click to collapse
Thanks bro
What is time max and time 1/2 max comparing with slow shutter?
Other word what settings are adequate to slow shutter (2x, 4x, 8x) in @miniuser123 version?
It's v8.2 about.
Din-Ace said:
If any one dont mind then i can ask something?
What is ZSL?
Click to expand...
Click to collapse
Zero Shutter Lag
In this mode the camera app takes photos continuously, even before pressing the shutter, so when you press the shutter, it just processes and saves the pictures that were already taken.
great, will try when upgrade to O from Nou on FE ^^ thanks in advance!
I have the gcam v7...what the diference between v7 and pixel2mod??
IDan1109 said:
[
Pixe2Mod Base
Stability: Good
Features:
- Fixed and working potrait mode (I may have broken it for SD variant)
https://drive.google.com/open?id=1z0cGbvZ2GoaSpPxAzPkHoxcycSfhyhEG
Click to expand...
Click to collapse
Can you please stop worrying about snapdragon? They have so many apks working for them.
Currently using Arnova8G2's Pixel3Mod v1 with great stability and image quality on a G950U. The only issue is the app crashes when switching to 4K video for either rear or front camera and no ZSL feature. Everything else works including Slow Motion and AR stickers.
Asmodean27 said:
Currently using Arnova8G2's Pixel3Mod v1 with great stability and image quality on a G950U. The only issue is the app crashes when switching to 4K video for either rear or front camera and no ZSL feature. Everything else works including Slow Motion and AR stickers.
Click to expand...
Click to collapse
This is exynos thread. Go to your chip thread.
Alright some of you have seen my contributions in the magisk thread by aer0zer0 but i seem to update it a lot and seem to spam the thread up, so i decided to make a seperate thread where i can post updates and edits.
//:
Q:Reason for using this over arnovas and cstarks gcams?
A:These settings are made especially for essentials IMX 258 and use more vibrant colors as seen in samples, plus the noise settings are manually tweaked by me and keep getting better as i tinker with them more, as well as the gcams provided by arnova and cstark use custom set blacklevel fix which is not an good idea, tolyan's uses dynamic black level which adjusts the tint values by ISO settings as said when checking the Fix Black level option.
://
Grab my compiled version with preset here- 5.3 https://mega.nz/#!qk4ggYqC!Pb3gY6DW0KNYd6huvbEvIARIGhdRrJckLZYBPnZ8q9I
6.1 Preset build based on MGC_6.1.021_V1d-Advances_test2.apkhttps://drive.google.com/file/d/1QV88P65dzBAy7wJTlozei24owB8mzA5U/view?usp=sharing
Old method below
we are using tolyans builds
https://www.celsoazevedo.com/files/android/google-camera/dev-tolyan009/
1: Advanced Settings
//: Final JPG quality hdr+ = 100%
//: Resampling method = Raisr
//: Fix Black Level = on
//: Enable Motion = on
//: Max BlackLevel offset = 25 or 50
2: Noise Reduction -> tuning back cam
Rev 0.23 - October 9th
//: Tuning master switch = ON
• Apply custom sensor noise model = ON
• Custom sensor noise offset a = 3000
• Custom sensor noise offset b = 22500 (default)
• Custom sensor noise scale a = 2117875
• Custom sensor noise scale b = 113625
//: Apply custom denoise params = ON
• Custom luma denoise at high ISO values = 1.5
• Custom luma denoise at average ISO values = 2
• Custom luma denoise at low ISO values = 0.4
• Custom chroma denoise at high ISO values = 40
• Custom chroma denoise at average ISO values = 10
• Custom chroma denoise at low ISO values = 2.55
• Custom denoise revert factor at high ISO values = 0
• Custom denoise revert factor at average ISO values = 0.05
• Custom denoise revert factor at low ISO values = 0.05
3: Back to Advanced Settings -> Saturation
//: Highlight Saturation: 1.2
//: Shadow Saturation: 2.0
Samples: https://imgur.com/a/O9hYlBh
Noise settings differences: https://i.imgur.com/ICn5fmi.jpg
We need more people like you. Thanks!
I appreciate you, thanks .
praise be to the @TheIronLefty
aer0zer0 said:
praise be to the @TheIronLefty
Click to expand...
Click to collapse
not til i make the apk recompiler work
Slow Motion does not appear to be working with this. Crashes app.
Sent from my PH-1 using Tapatalk
Spey said:
Slow Motion does not appear to be working with this. Crashes app.
Click to expand...
Click to collapse
Still need the magisk mod, but you can turn it off.
We should use HDR+ enhanced right?
aer0zer0 said:
Still need the magisk mod, but you can turn it off.
Click to expand...
Click to collapse
Thx 4 reply.
Will keep using SloMo on GoogleCamera-Pixel2Mod-Arnova8G2-V8.1.apk for time being. Was hoping to find 240fps (120fps only on this Arnova).
Sent from my PH-1 using Tapatalk
HaloTechnology said:
We should use HDR+ enhanced right?
Click to expand...
Click to collapse
Both work just fine.
Huh, this might make me finally install Magisk.
Just for your information, you might have missed that, another developer going by the name of ArtZ did something similar, just for a regular apk (https://www.celsoazevedo.com/files/android/google-camera/dev-artz/). He developed for the LG G6 which shares the IMX 258 with the PH-1 and very much focused on color reproduction. I've been using his latest apk since its release and always returned to it when testing other ones in between since the color reproduction is much better in HDR+ enhanced compared to other apks, his settings might be of interest to you as well in your development.
Edit: after testing tolyans build with your settings I'm definitely impressed by the speed and noise settings, but color reproduction is still significantly better with the black level settings introduced by ArtZ. The color shift can best be seen when taking a low light picture with HDR+ and HDR+ enhanced, the latter will often have a green tint. ArtZ talked a bit about his settings in this post: https://forum.xda-developers.com/showpost.php?p=75432324&postcount=1568. Integrating a PH-1 specific color fix into a Gcam apk could very well be worth the work.
Skirr said:
Huh, this might make me finally install Magisk.
Just for your information, you might have missed that, another developer going by the name of ArtZ did something similar, just for a regular apk (https://www.celsoazevedo.com/files/android/google-camera/dev-artz/). He developed for the LG G6 which shares the IMX 258 with the PH-1 and very much focused on color reproduction. I've been using his latest apk since its release and always returned to it when testing other ones in between since the color reproduction is much better in HDR+ enhanced compared to other apks, his settings might be of interest to you as well in your development.
Edit: after testing tolyans build with your settings I'm definitely impressed by the speed and noise settings, but color reproduction is still significantly better with the black level settings introduced by ArtZ. The color shift can best be seen when taking a low light picture with HDR+ and HDR+ enhanced, the latter will often have a green tint. ArtZ talked a bit about his settings in this post: https://forum.xda-developers.com/showpost.php?p=75432324&postcount=1568. Integrating a PH-1 specific color fix into a Gcam apk could very well be worth the work.
Click to expand...
Click to collapse
My settings are based of Artz's, in my testing i never got green or magenta tint on my settings, however i did have those issues when u used to use ArtZ's last builds
Skirr said:
Huh, this might make me finally install Magisk.
Just for your information, you might have missed that, another developer going by the name of ArtZ did something similar, just for a regular apk (https://www.celsoazevedo.com/files/android/google-camera/dev-artz/). He developed for the LG G6 which shares the IMX 258 with the PH-1 and very much focused on color reproduction. I've been using his latest apk since its release and always returned to it when testing other ones in between since the color reproduction is much better in HDR+ enhanced compared to other apks, his settings might be of interest to you as well in your development.
Edit: after testing tolyans build with your settings I'm definitely impressed by the speed and noise settings, but color reproduction is still significantly better with the black level settings introduced by ArtZ. The color shift can best be seen when taking a low light picture with HDR+ and HDR+ enhanced, the latter will often have a green tint. ArtZ talked a bit about his settings in this post: https://forum.xda-developers.com/showpost.php?p=75432324&postcount=1568. Integrating a PH-1 specific color fix into a Gcam apk could very well be worth the work.
Click to expand...
Click to collapse
If you don't care about slomo or hevc, you don't need magisk
TheIronLefty said:
My settings are based of Artz's, in my testing i never got green or magenta tint on my settings, however i did have those issues when u used to use ArtZ's last builds
Click to expand...
Click to collapse
The settings you describe though do only cover chroma and luminance noise handling, right? There are no IMX 258 specific black level offsett settings (aside from activating "Fix Black Level") applied like the ones ArtZ describes:
Release (default is 64.0 for all)
0x427F70A4 # 63.86f
0x427FB852 # 63.93f
0x427FB852 # 63.93f
0x428047AE # 64.14f
(Decimals are very important. There's visible differences using for instance 63.85 instead of 63.86!!!)
I haven't found that option in tolyans build, but I remember some apks would let you change these 4 values in 0.1 intervals. I tried the upper values in a few of those builds a while ago but they never gave the same result compared to the ArtZ apk, probably because ArtZ directly integrated them in the build including the second digit.
I'll try to whip up a quick comparison album this evening between the Essential cam, ArtZ v3.0 Taimen and the tolyan build with your settings to illustrate what I mean with respect to the green tint.
In the meantime, here is an older album I created this February with a few different ports, including the ArtZ v3.1 (which, oddly enough, is older than the v3.0). You can cleary see how most ports handle HDR+ (which i dubbed ZSL in the image descriptions back then) similarily but differentiate heavily when using HDR+ enhanced (HDR+ in the image description): https://photos.app.goo.gl/iGKAjwAD6PbUrgia2
aer0zer0 said:
If you don't care about slomo or hevc, you don't need magisk
Click to expand...
Click to collapse
You're right of course, I initially misread and thought the settings described by TheIronLefty were part of a specific magisk gcam module, not "just" settings for tolyans build.
Skirr said:
The settings you describe though do only cover chroma and luminance noise handling, right? There are no IMX 258 specific black level offsett settings (aside from activating "Fix Black Level") applied like the ones ArtZ describes:
Release (default is 64.0 for all)
0x427F70A4 # 63.86f
0x427FB852 # 63.93f
0x427FB852 # 63.93f
0x428047AE # 64.14f
(Decimals are very important. There's visible differences using for instance 63.85 instead of 63.86!!!)
I haven't found that option in tolyans build, but I remember some apks would let you change these 4 values in 0.1 intervals. I tried the upper values in a few of those builds a while ago but they never gave the same result compared to the ArtZ apk, probably because ArtZ directly integrated them in the build including the second digit.
I'll try to whip up a quick comparison album this evening between the Essential cam, ArtZ v3.0 Taimen and the tolyan build with your settings to illustrate what I mean with respect to the green tint.
In the meantime, here is an older album I created this February with a few different ports, including the ArtZ v3.1 (which, oddly enough, is older than the v3.0). You can cleary see how most ports handle HDR+ (which i dubbed ZSL in the image descriptions back then) similarily but differentiate heavily when using HDR+ enhanced (HDR+ in the image description).
Click to expand...
Click to collapse
I tried using those settings on arthurs build, i even discussed about it in magisk thread, but i never got the same results too. Besides i cant really do anything about integrating it, since i dont know how to work with java.
@TheIronLefty, looks like colour noise reduction is a bit overdone in your sample. Very apparent on the depth of field scale on the old lens.
When I try to install tolyans build, it says "update existing application" and I am unable to install it... Any fixes?
Sent from my PH-1 using XDA Labs
NummerEinsNerd said:
When I try to install tolyans build, it says "update existing application" and I am unable to install it... Any fixes?
Click to expand...
Click to collapse
Uninstall any other custom GCAM application and try again.
Genghis1227 said:
Uninstall any other custom GCAM application and try again.
Click to expand...
Click to collapse
I have already done that, still won't work :/
Sent from my PH-1 using XDA Labs
aer0zer0 said:
Still need the magisk mod, but you can turn it off.
Click to expand...
Click to collapse
which magisk mod do I need to activate slow mo on pie?
Poco X3 Pro is a device capable of delivering amazing photos with the help of Google-Camera Mod which has gained a lot of popularity in the past recent years. The aim of this thread is to provide the vayu community with the latest news and updates about our Google-Camera Mod.
The latest available G-Cam Mod is 8.4 version which is now in beta stage and pretty usable for daily use. All features are working very well with the exception of face retouching. A lot of work has been put into this version and many significant advancements have been made towards solving various bugs and improving the stability and output quality of this Google-Camera Mod.
Bugs:
• Face Retouching Not Working
• No Ultra Wide & Macro Lens Support Yet ( Should Be Added In Future Builds )
Download Links & Steps To Be Followed :
1.You Can Download Google-Camera 8.4.300 Beta Made By Arnova8G2 From HERE.
2.You'll Need To Import Gca File Into Gcam Now.
• How To Load:
Settings > Advanced > XML Config > Select Config > Browse & Select The GCA File
• Download The Gca File From HERE.
3.Now You'll Need A Config (XML) File To Apply The Necessary Changes To Enhance The Experience And Output Of The Gcam Optimised Specially For The Device.
• How To Load :
Step 1 - Move This File To The Following Location Internal > GCam > Configs8 (Create An Folder If Its Not There)
Step 2 - Then Double Click The Empty Space Next To The Shutter Button And Select The XML
• Download The Config (XML) File From HERE
NOTES:
Android 11 & above users must grant full file permissions to Google-Camera in order to be able to load xml configs
( Long-press on G-Cam icon > Info > See More > Permissions > Files and Media > Allow management of all files )
To prevent slow-motion/video focus hunting issues, tap to focus on the viewfinder and lock AF/AE by tapping the lock icon on top of the EV slider or DISABLE stabilization.
[ PRO Back Camera Tip ]
When shooting in low-light scenarios like after sunset or before sunrise, tap to focus on the viewfinder for a better exposure. Focusing manually will raise just the right amount of exposure for a perfectly balanced ratio between highlights and shadows
When shooting a subject with strong light coming from behind, tap to focus on the subject and slightly raise exposure using the exposure slider. This will ensure the subject will be well exposed
[ PRO Front Camera Tip ]
When shooting a selfie with strong light coming from behind or when shooting in low-light, your face may be underexposed. To counteract this issue, tap to focus on your face and slightly raise exposure using the exposure slider. This will ensure your face will be well exposed
For smoother selfies with less facial details on HDR+ Enhanced, Take Selfies In Night Sight Mode. (Hack For Beauty Mode LOL).
IMPORTANT: A clean install is always recommended prior to using Google-Camera in order to avoid possible functionality issues with the app! First uninstall all G-Cam apps currently found on your system » install G-Cam » open it and grant permissions » close G-Cam » clear G-Cam data and cache » open G-Cam and apply the settings/config » reboot device
Enjoy Google-Camera 8.4 on your vayu !
Cant even start apo. Fc. The same have for newest lmc.
Bsg 8.4.400 starting normally. On paranoid android 12
lsander said:
Cant even start apo. Fc. The same have for newest lmc.
Bsg 8.4.400 starting normally. On paranoid android 12
Click to expand...
Click to collapse
Could Be A ROM issue i have tried on several ROMs Works Perfectly Fine Everywhere.
THREAD LOCKED
As per the Forum Rules:
5. Create a thread topic or post a message only once, this includes external links & streaming media.
-snip-
-snip-
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
-snip-
Click to expand...
Click to collapse
Please search the forum for existing/similar threads before posting a new thread. For continuing discussion, kindly use the existing thread: https://forum.xda-developers.com/t/gcam-for-x3-pro.4256287/
Regards,
shadowstep
Forum Moderator