Related
GravityBox - all-in-one tweak box - Xposed module for devices running AOSP 4.4
Version 3.6.2 [KitKat]
Version for JellyBean is available in this thread: http://forum.xda-developers.com/showthread.php?t=2316070
READ THIS POST CAREFULLY BEFORE PROCEEDING ANY FURTHER
Hey!
After countless hours of coding and searching for proper entry points to inject code to incorporate fixes and mods, here it is:
GravityBox - a complex Xposed module targeted for devices running Android 4.4, which turns vanilla ROM into
feature-packed "non-flashing" custom ROM.
Originally, this module was designed for MTK6589 devices which lack custom ROMs built from source due to MediaTek closed-source policy.
Later on, it was adjusted to support other (non-MTK) devices running vanilla or close-to-vanilla AOSP ROMs.
Introduction
The app utilizes amazing Xposed framework coded by recognized
developer rovo89 which, briefly, provides interface for injecting code into any app, including system services allowing modifications of applications and system services at run-time. One of the biggest advantages of GravityBox is that it is not bound to any specific device. Actually, it should run on any device having vanilla Android 4.4 (ROM close enough to AOSP).
This project wouldn't be possible without rovo's Xposed framework, so huge kudos to him.
Feature highlight
--- CyanogenMod Pie controls
--- Expanded Desktop
--- Statusbar QuickSettings tile management with tile reordering
--- Lockscreen targets
--- Statusbar icon coloring
--- Statusbar Brightness Control
--- Additional QuickSettings tiles:
------- Sync on/off, WiFi AP on/off, GravityBox shortcut, Torch, Network mode (2G/3G/2G+3G switch), Sleep, QuickRecord,
QuickApp, GPS on/off, Ringer mode, Volume tile, Camera tile, ...
--- Quick pulldown - switches to QuickSettings when status bar is pulled down near edges
--- Auto-switch to QuickSettings when there are no notifications
--- Center clock in statusbar
--- Battery indicator style
--- Navigation bar tweaks including cursor control keys
--- Navigation bar ring targets
--- Low battery warning policy
--- Disable LED flashing when battery low
--- Disable LED while charging
--- Advanced power-off menu (reboot, recovery)
--- Volume key cursor control
--- Skip tracks by volume key long-press while screen off (thanks to rovo89)
--- More volume levels for music stream
--- Option to control safe headset media volume
--- Button for clearing all recent tasks at once
--- CRT screen off animation
--- Minimal brightness setting
--- Autobrihtness levels adjustment
--- Lockscreen tweaks - show widgets maximized, lockscreen background style (color fill, custom image)
--- Lockscreen rotation
--- Hardware key actions - menu long-press/double-tap, back long-press, home long-press
--- Dithered Holo background
--- Option to use solid black Holo background
--- Expandable volume panel
--- Option to unlink ringtone and notifications volumes
--- Notification drawer style (background color, image for portait/landscape, transparency)
--- Button backlight modes (default, disabled, always on while screen is on)
--- Dialer (Phone) tweaks
--- Launcher tweaks
--- Screen recording
--- GravityBox Actions - interface for 3rd party apps
--- Smart Radio
--- Notification control (per-app notification LED/sounds/vibrations)
--- Ascending ring tone
... more to come
Compatibility
Some words about GB's main concept. One thing I didn't like about xposed modules was that it was always necessary to reboot a device after making a change to some option. Since GB's main concept was to turn MTK devices running stock ROM into something that's close enough to a feature-packed custom ROM, I had to take a decision - for it to be as much comfortable as possible and to really behave like a custom ROM, I had to design it to support most of the preference changes to be done on the fly without needing to reboot a device. While this sounds nice, it also brings couple of "drawbacks". For changes to be made on the fly, it is necessary to make some preparations when device starts. This means, even if you don't use the particular feature, the necessary preparation/modification is already there and is waiting for the user to come and change that option.
This means it is not possible to "completely deactivate" particular feature if it causes trouble on your device or if you installed GB because you want to use only one particular feature you can't find elsewhere.
This results in issues on ROMs/devices that have parts that are diverting from default Android implementation too much, or are running heavily modified custom ROMs.
If you experience weird issues after installing GB, even if you didn't activate a particular feature, it is not because of GB is broken, it is because it is not compatible with your ROM. It is very similar as if you installed ROM built from source for Nexus to some Xperia device - it won't work.
Next thing, GB is a complex module and is not suitable for 1 purpose scenario. This means, if you are running custom ROM built from source (CM, PAC, ...), and you are missing a certain feature, your best option is to go ask creators of those ROMs to implement those additional features. Supplementing missing features on well-known custom ROMs built from source by installing xposed modules (especially complex ones) is definitely not a good way to go and can cause more trouble than good.
And finally, the last. GB being a complex module, it shouldn't be combined with other complex modules often racing for the same goal. They can conflict/fight on the same playground and there's no way you can deterministically say which one's going to win.
They can even lose both.
So in summary:
- this module is designed to run on vanilla or close-to-vanilla Android 4.4 (AOSP)
- supports "Google devices" like Nexus, HTC One Google play edition, and others running vanilla Android 4.4
- supports Motorola Moto G Dual SIM running stock KitKat
- supports ThL 5000 running stock KitKat and potentially other MediaTek devices running pure MediaTek ROMs
- Samsung Touchwiz, HTC Sense, MIUI, LeWa, Xperia, Lenovo, etc. are NOT supported. It is not guaranteed this module will work on these at all so try at your own risk. This module is simply too complex to support all kind of ROM brands that were vastly modified by vendors.
- DO NOT USE WITH CUSTOM ROMS LIKE CM,AOSPA,ROOTBOX,AOKP,SLIM, OMNI AND THEIR OTHER CLONES... IT MAKES NO SENSE AND CAN CAUSE CONFLICTS AND UNEXPECTED BEHAVIOUR
- I will not implement any exceptions that will adapt this module to a specific custom ROM. Please, do understand, it is unmanageable.
- I will not provide any support for devices violating these compatibility rules
trjlive said:
As is detailed in the OP, GravityBox is designed to be used with stock, vanilla AOSP ROMs, not OEM and custom ROMs. In other words, Google Play Edition and Nexus devices. All OEM ROMs (TouchWiz, Sense, Xperia, Moto, etc.), and custom ROMs (CyanogenMod, ParanoidAndroid, etc.) differ significantly in their code base from pure AOSP. And as most of these ROMs are closed source, and the developer does not have access to all the devices, it means that GravityBox is not designed for, or tested on, these devices and ROMs.
Even though the Moto devices look like stock Android, they are as much custom under-the-hood as TouchWiz or Sense. It's just that Motorola decided to implement a skin that resembles stock Android, rather than a custom skin like Samsung has done. But the changes to the core code mean that many of GravityBox's features will not work, and actually do cause some well-known bugs. The same goes for ParanoidAndroid, there are just too many changes to the core code for GB to be reliable.
If you choose to use GravityBox on a ROM it was never intended to be used with, then you do so at your own risk, and without any support. You should always have a good nandroid backup and be familiar with ADB and Fastboot. At any time, a ROM update or GravityBox update may cause any/all GravityBox features to break, and worst case, send your device into a bootloop. This is just an unfortunate reality of using a mod on a device it wasn't intended to be used on. Any user who wishes to improve or fix bugs on their unsupported ROM is more than welcome to download the source code for GravityBox (links to Git in the OP) and work on debugging and fixing the bugs on their own.
Click to expand...
Click to collapse
Prerequisites
To use this module, the following conditions must be met
- You have a device running Android 4.4 that's based on AOSP (vanilla or close-to-vanilla Android)
- ROM must be rooted (XposedInstaller requires root to be able to install framework into system)
- You have working custom recovery allowing you to make a backup before installing Xposed framework
GravityBox KitKat version has been developed and tested on Nexus 5
Installation
1) Backup your current ROM in custom recovery. I am serious. Don't skip this step.
2) Get the Xposed installer from Download section from Xposed official thread (the latest version is typically available at this link: http://dl.xposed.info/latest.apk)
3) Install and run Xposed installer and follow the instructions to activate Xposed framework
4) Reboot. If device doesn't boot that means that the Xposed framework is not compatible with ROM you are currently
running. You don't need to continue with the next steps. You will have to restore your ROM from backup.
5) Download, GravityBox APK from the second post, rename it to GravityBox.apk and install it.
Alternatively, you can download the latest GravityBox directly from Xposed Installer (search for GravityBox [KK] module).
6) Make sure GravityBox app is installed into internal memory. If it was installed into phone storage or external storage,
move it into the internal memory first (applies only to devices having additional or external storage)
7) Run Xposed installer, go to Modules menu and activate GravityBox by checking the checkbox
8) Reboot
9) Launch GravityBox from app drawer or from Xposed installer and set options as desired
Videos
- Xposed framework install plus gravity box module overview (thanks to Rootjunky.com & Marshall Williams)
- Gravity Box - What is it and How to install it (thanks to @D3VI0US)
Documentation
Thanks to @cadarn07, there's a comprehensive and searchable User Guide listing
all of the GravityBox features. It's an EverNote document located at https://www.evernote.com/pub/cadarn07/gravitybox
Reporting bugs
If you experience problems with certain feature, provide the full-detailed info that can help me
to reproduce the bug and attach debug.log file you'll find in:
/data/data/de.robv.android.xposed.installer/log
In case you experience SystemUI crashes or other apps Force Closing, or device soft reboots, attach logcat from time
crash occurs. (use adb logcat *:E or your favorite logcat app from Play Store).
Please, don't attach big logs. Only the portion where error is clearly seen.
Disable all other xposed modules before reproducing bug to make sure it is really GravityBox related
Remember, this app was developed and tested on one particular device so it is not guaranteed that
it will work flawlessly on yours.
Click here tor ead additional, more detailed info on Reporting bugs provided by @trjlive
Multilanguage support
Volunteers are welcome to translate GravityBox to other languages.
Simply download this file: https://github.com/GravityBox/GravityBox/raw/kitkat/res/values/strings.xml
Use Notepad++ to edit strings and then send me edited file so I can include translations into next release.
Source code
GravityBox is opensource. Sources are available in my gihub: https://github.com/GravityBox/GravityBox/tree/kitkat
If you're a dev and have some ideas for additional features, feel free to fork it, work on it
and send the pull requests.
Copyright notice
https://github.com/GravityBox/GravityBox/blob/kitkat/NOTICE
Support development
Coding, maintaining and supporting this project costs me a lot of my precious time. If you find this project useful, you are welcome to support its development via donation. This form of support is meant to compensate for my time dedicated to the community + eventually, help me to afford newer device to keep up with AOSP evolution thus providing continuous support as Android evolves. Thanks!
Info about premium features and PayPal transaction ID verification system
1) Those who supported development via PayPal donation can use their PayPal transaction ID to unlock premium features.
As of v2.9.5, there's one premium feature: Backup/restore of GB settings.
2) If you contributed to the project by providing translations, code fragments, or by any other way
you can apply for a free transaction ID by contacting me via PM.
3) Be aware that there's a system that can identify potential transaction ID
abuse. E.g. when one ID is being used by more users. Such IDs will get blocked automatically.
This can also happen when you previously exposed your ID in public forum and other users took
advantage of it. If this is the case, contact me via PM so I can issue new, special ID.
In case you own more devices, you can use one transaction ID on up to 10 of them.
4) If you are using your own custom builds of GB for personal use, you will get hash mismatch
upon verifying your ID as verification system accepts requests only from official releases of GB.
If you want to be able to verify IDs with your custom build, contact me via PM so I can setup
a special hash for your build.
If you are using a custom build that you provide for broader group of users (e.g. in a custom ROM),
it is necessary to ask for new hash everytime your new custom version is released for public use.
These rules are based on mutual trust so please, do not violate them.
Credits
- @bgcngm for his code contributions to the project
- @MohammadAG for Xperia specific contributions to the project
- @rovo89 for his ultimate Xposed framework and "Volume keys to skip track" mod
- @peptonib for starting me up with this project
- @Tungstwenty for Fake ID vulnerability patch
- THL W8 owners for providing support and feedback
- CyanogenMod project
- ParanoidAndroid project
- SlimBean, RootBox, AOKP, OmniROM projects
- Sergey Margaritov for ColorPickerPreference
- All those who provided translations for different languages (Mr.Premise, peptonib, kidmar, ch-vox, romashko, Indiant, lelemm, oicirbaf, unavix, LuHash, WedyDQ10, mp3comanche, awaaas, liveasx, samsonbear, Eric850130, xtrem007, benjoe1, asmb111, ...)
- and finally, all those who keep the project alive by supporting me via donations (you know who you are)
Changelog
https://github.com/GravityBox/GravityBox/blob/kitkat/CHANGELOG.txt
XDA:DevDB Information
GravityBox [KK] Xposed Framework Module, Xposed for the Android General
Contributors
C3C076
Source Code: https://github.com/GravityBox/GravityBox/tree/kitkat
Xposed Package Name: com.ceco.kitkat.gravitybox
Version Information
Status: Stable
Current Stable Version: 3.6.2
Stable Release Date: 2017-04-23
Created 2013-12-03
Last Updated 2017-04-23
Changelogs
Changelog 3.6.2 - 23/04/2017
- Download Progress Bar: implemented extensions from SBDP module
--- added support for multiple concurrent progress bar notifications
--- keeps track of all available progress bar notifications and switches between them
--- added support for clearable notifications containing progress bar
--- added logic for auto-hiding progress of idle notifications
--- added option for sound notification
--- added option for playing sound only when screen is off
- QuietHours: implemented Wear mode
--- available only when Android Wear app is installed
--- mutes notification sounds and device-wide vibrations while preserving vibrations on a paired watch
--- can be toggled from QuietHours tile or via dedicated GravityBox Action
- Made screenshot faster by introducing dynamic context-aware delay
- Adjusted for compatibility with the latest GravityBox Unlocker v1.4.3
--- improved reliability of license validation
--- !!! won't work with older versions of the Unlocker !!!
- Updated Chinese (Simplified) translations (thanks to liveasx)
- Updated Hungarian translations (thanks to benjoe1)
Full Changelog: https://github.com/GravityBox/GravityBox/blob/kitkat/CHANGELOG.txt
Alternative downloads: directly via Xposed Installer or at: http://repo.xposed.info/module/com.ceco.kitkat.gravitybox
Reporting bugs by @trjlive
Here's the comprehensive info on reporting bugs prepared by @trjlive (many thanks!).
Please, read it carefully.
trjlive said:
I've noticed an increase in bug reports being filed over the last few days. While a few of these bug reports have been quite helpful, the vast majority of them lack significant and necessary information, which makes them less useful and causes additional confusion about what the bug really is. So I thought I would write a guide on how to provide a proper bug report for GravityBox, to help the new users to this thread, as well as provide a reference for the experienced users.
The aim of a bug report is to describe what went wrong in enough detail that the developer can reproduce it on his device. Describe everything in detail, be direct and clear. State what you saw, and also state what you expected to see. List all the steps to reproduce the problem. After you type out the steps, follow them yourself to ensure you haven’t left anything out. Don’t make any assumptions that the developer will know what you mean, if you haven’t written it out, then it didn’t happen. If the developer can’t reproduce the problem, or at least identify what is causing it, then you’re probably not going to get a fix.
Be ready to provide extra information if the developer needs it. If he didn’t need it, he wouldn’t be asking for it. He isn’t being deliberately difficult. Providing version numbers of your device, ROM, Xposed, and GravityBox are the minimum. Don’t just say “the latest version”, actually provide the number. Sometimes an update is released since the last time you checked, so you may not actually be on the latest version. Providing the actual version numbers is the only way the developer can be sure of your device’s environment.
Many users think that by providing any type of bug report, even a very basic one, such as: "It doesn't work" is better than doing nothing. Give the developer some credit for basic intelligence: if GravityBox really didn’t work at all, he would probably have noticed. Since he hasn’t noticed, it must be working for him. Therefore, either you are doing something differently from him, or your device is different from his. He needs information; providing this information is the purpose of a bug report. More information is always better than less. Be precise, developers like precision.
If a bug has already been reported, there is little reason to report it again, unless the developer specifically asks for more people to report it. When you post a "+1" message after someone else's bug report, all this does is add confusion to the thread and contributes nothing to the goal of fixing the bug. If you have no new information to provide, then don't post a bug report. If you can provide additional information that you think might help, then do post and link to the original bug report, and include your additional details, including all relevant details about your device if it’s different from what has already been reported.
Due to financial and technological constraints, developers can’t possibly own every device and ROM combination, which means there are a lot of users who have devices and ROMs that the developer has not used. This is important information. Every bug report should always include the make and model of the device, the name and version number of the ROM. An example such as, “Nexus 5 stock Android 4.4.4 build KTU84P.” Provide the device details upfront, the developer should never have ask for them, this is a basic detail that is always required. A bug may be specific to a particular device, or it may occur on different devices, but these details can make all the difference, and providing will usually result in you getting a fix sooner.
A bug report should always contain a log of the error. There are a number of things going on in the background on your device that you don’t see but are relevant to the operation of GravityBox. A minor UI glitch might be nearly impossible to track down without a log, but by being able to read line by line in a log and seeing what happened, makes it a lot easier to find and fix the bug. Without a log, many bug fixes are like trying to find a needle in a corn field. Provide a verbose log, of only the time period where you reproduce the bug. These logs will likely contain hundreds if not thousands of lines, so please limit it as much as possible to the shortest time needed to reproduce the bug. Attach the log file to your bug report as a file attachment (.txt or .zip file), or paste it on a site like pastebin.com, and then include a link to it in your bug report. But please don't just copy and paste the entire logcat into your post in this thread, it causes posts to be unnecessarily long and difficult to read.
In summary, every single bug report should contain, at the minimum, the following information:
What happened: Describe the bug, what you saw, any error messages, force closes, UI glitches, etc.
What was expected: Describe what you expected to see.
Steps to reproduce the bug: Be thorough and detailed, don’t make any assumptions in the steps. List everything you do, from tapping an icon, changing a setting, turning down the volume, etc. This is the part where you can’t give too much information, more is always better.
Device environment: List your device’s make, model, ROM name and version, OS build if available, and the carrier name is sometimes helpful (if there are multiple different configurations of the same device).
Log file: Provide a logcat file of the steps where you reproduce the bug. Set the log type to verbose, and limit the duration to as short of a time as needed to capture the bug.
If you can’t provide all of this information, then please explain why. If you’re trying to get a logcat, but it errors out before running, explain that. It’s better to explain what is preventing you from providing a crucial piece of information, than to just omit it. A bug report that contains all of this information, or as much of it as possible, will go a long way to helping the developer recreate the bug on his end, determine what is causing it, and provide a fix for it, all in a timely fashion.
And always remember to be gracious and appreciative of the developer for donating his time and effort to helping you. Developers on XDA do not get paid for their work, they do it all because they want to, on their own time and at their own expense. They owe nothing to anyone on this site. Even if you have donated to their project, they still owe you nothing more than anyone else. You donated because you wanted to contribute to the development of the project, not to buy any extra level of support.
Let’s help the developers help us, the users, by providing the necessary information they need, in the bug reports we post.
Click to expand...
Click to collapse
Thanks! (First! ) but I get a parsing error for the package...
Gesendet von meinem Nexus 4 mit Tapatalk
Maxr1998 said:
Thanks! (First! ) but I get a parsing error for the package...
Gesendet von meinem Nexus 4 mit Tapatalk
Click to expand...
Click to collapse
You can't install this on Android lower than 4.4
Thanks. Installed fine. Looking forward to trying it out
Sent from my Nexus 4 using Tapatalk
C3C076 said:
You can't install this on Android lower than 4.4
Click to expand...
Click to collapse
But I have a Nexus 4 with KRT16S...
EDIT: Worked fine now...reupload solved the issue...
Gesendet von meinem Nexus 4 mit Tapatalk
So, do you have any ideas how to get the MotoX files to decompile? Which one did you have trouble with? I can't get the framework-res.apk to install.
Great Work, AWESOME !
All i need now is KK for my phone
Thank you for great work. It's working!
Is it possible to add battery bar - line on top? If possible with animation charge. Thank you.
Sent from my GT-I9100G using Tapatalk
Great work installed on my S4.
GravityBox is working well on my n4, thanks for your good work
Gesendet von meinem Nexus 4 mit Tapatalk 2
Maxr1998 said:
But I have a Nexus 4 with KRT16S...
EDIT: Worked fine now...reupload solved the issue...
Gesendet von meinem Nexus 4 mit Tapatalk
Click to expand...
Click to collapse
No problem. I thought you have 4.3 according to your signature info.
C3C076 said:
No problem. I thought you have 4.3 according to your signature info.
Click to expand...
Click to collapse
Umm...I haven't updated it by now...
But I have to say, GravityBox with xThemes makes my phone look wonderful
Gesendet von meinem Nexus 4 mit Tapatalk
Working just fine on my Dev Moto X.
Thanks for your efforts.
To alter auto brightness what are values to start with? I'd like the screen to auto dim more when using the phone in the dark.
Beamed from my Moto X
Thank you so much for all your hard work!
Thanks a lot!!
Sent from my HTC One using Tapatalk
On HTC One GPE based rom, latest update causes phone to reboot immediately if the power button is pressed and held even momentarily. Advanced reboot is unchecked, since the rom has it included (insertcoin, modified stock pretty much)
FSRBIKER said:
Working just fine on my Dev Moto X.
Thanks for your efforts.
To alter auto brightness what are values to start with? I'd like the screen to auto dim more when using the phone in the dark.
Beamed from my Moto X
Click to expand...
Click to collapse
You have to reboot after enabling brightness tweaks. After reboot default stock levels will be filled in which you can the adjust as necessary.
gfp17 said:
On HTC One GPE based rom, latest update causes phone to reboot immediately if the power button is pressed. Advanced reboot is unchecked, since the rom has it included (insertcoin, modified stock pretty much)
Click to expand...
Click to collapse
Custom Roms are not supported but I would be interested in seeing logcat of a crash, anyway.
C3C0, My old Friend, works as expected ,as always. Thank you.
Nexus 4 AOSPA 4.0
ⓐⓝⓓⓡⓞⓒⓛⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ
This overlay APK it's "born" because of the necessity to overcome missing overlays (thanks Huawei, love ya xoxo) under /vendor/overlay .
What it does exactly?
Nothing more than adding AOSP overlay matching our device capabilities and also, inherits Warsaw power profile.
Do I need it?
Yes.
It will fix Battery stats problems and add compatible features for your WAS over GSI.
This will conisderably enhance your experience on every GSI ROM giving better functionality overall.
Why you did that?
Because I'm sick of inheriting stuff that belongs to /vendor, in system.
Project Treble it's all about separating vendor implementation from system.
So why we should keep adding OEM stuff in that if it doesn't belong no more in /system?
I have XYZ device with ZYX firmware can I use it?
As long as you're on a WAS-*** device (with a non-EMUI firmware), you're good to go.
Otherwise DO NOT USE IT FOR THE LOVE OF MANKIND.
I don't have WAS, but I want it on my Huawei device !
Well, that's fine, join the Telegram group @GSI_HI6250, so that you could help me with stock files grabbing to make an overlay for your device.
Installation Instructions
Download the overlay
With root, push the overlay to /vendor/overlay. Create the folder if it doesn't exist.
Run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/dil3mm4-overlay-WAS.apk
UPDATE
-P compatibility
-Improved brightness levels
DOWNLOAD
Any update for Duk-al20（honor v9）？
Sent from my Honor V9 using XDA Labs
This overlay APK it's "born" because of the necessity to overcome missing overlays (thanks Huawei, love ya xoxo) under /vendor/overlay .
What it does exactly?
Nothing more than adding AOSP overlay matching our device capabilities and also, inherits Victoria power profile and it's compatible with P!
Do I need it?
Yes.
It will fix Battery stats problems and add compatible features for your VTR over GSI.
This will conisderably enhance your experience on every GSI ROM giving better functionality overall.
Why you did that?
Because I'm sick of inheriting stuff that belongs to /vendor, in system.
Project Treble it's all about separating vendor implementation from system.
So why we should keep adding OEM stuff in that if it doesn't belong no more in /system?
I have XYZ device with ZYX firmware can I use it?
As long as you're on a VTR-*** device (with a non-EMUI firmware), you're good to go.
Otherwise DO NOT USE IT FOR THE LOVE OF MANKIND.
I don't have VTR, but I want it on my Huawei device !
Well, that's fine, join the Telegram group @GSI_HI6250, so that you could help me with stock files grabbing to make an overlay for your device.
Installation Instructions
Download the overlay [/URL]
With root, push the overlay to /vendor/overlay. Create the folder if it doesn't exist.
Run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/dil3mm4-overlay-VTR.apk
Thank you very much!
It seems like there is already a huawei vtr overlay included in phh's aosp pie. Can you tell if there are any benefits in applying this on top?
Of
Sent from my LDN-LX2 using XDA Labs
nabihaharyono said:
Of
Click to expand...
Click to collapse
same
Introduction:
This modification / custom kernel configuration for Pixel and Pixel XL is optimized and made with the focus on bringing several, carefully tuned behind-the-scenes enhancements & adjustments that improves overall critically needed performance, system responsivness and battery life to the highest possible level. The seed to this project can by the way be found here, for anyone that is interested of its origins.
Note: This script is not recommended to be modified or customized by the user.
The latest release can be found here.
Disclaimer:
This is presented as "what if". If this modification screws up or breaks anything for you, I am not the one to be held responsible. It's a free will to try out this kind of changes/modifications/addons/tweaks, just don't blame the inventors for eventual bad results and/or screw-ups.
Features:
Reduced battery consumption
Device specific enhancements for best possible balance between battery life & performance
Enabled, and fully configured, Boeffla generic kernel wakelock blocker
[
Disabled a lot of useless stuff at kernel level (Improves battery life as well as performance)
CPUSet improvements & optimizations
Schedtune tweaks (Improves responsivness)
Power efficiency enhancements
Wide IO block tuning (Reduces the possibility of hiccups, lags and overhead)
Possibly other miscellaneous things I've forgotten to write down here, both big and small.
Requirements/what you need for getting this script fully working:
An unlocked bootloader
Your own specific choice of kernel
Latest Magisk
Busybox for Android NDK Magisk Module by @osm0sis
Patience
Installation/How-To use & abuse:
1) Download the attached ZIP
2) Extract the script
3) Move the script to the following location;
/data/adb/service.d and give the script the following permissions (0755)
4) Reboot your phone, let Android boot to the launcher and let Magisk boot service do its crucial magic (takes a few seconds before the scripts is fully up and running around behind the scenes)
5) Enjoy!
Note: If you still are unsure how to do for making my kernel configuration / modification work & be up and running behind the scenes, then please read @Phalanx7621 phenomenal guide here or check out @Phalanx7621 in-depth video here. The installation method is the same for both the first generation as well as the second generation of Pixels!
Credits:
@nathanchance for his contributions with his Flash Kernel
@franciscofranco for all the information on which kernel wakelocks that is safe to block
@Phalanx7621 for his phenomenal how-to guide
@Lord Boeffla for his awesome generic kernel wakelock blocker
@pkgnex for inspiring me walking into this partially unknown territory from the beginning
@flar2 for his excellent EXKM application and ElementalX Kernel
@osm0sis for his Magisk Busybox module
Everyone that I've forgotten to mention here
Telegram:
If you want to try out betas / previews of my script before they are officially released, or just hangout and chat a little, then join the official Telegram group here
To-Do list:
Optimize and properly tune things even further for best possible balance between battery life, system responsivness and performance
Contributors:
@xFirefly93
Created: 2018-10-08
Last updated: 2019-01-04
Been following your thread over in the Pixel 2 XL forum, nice to have you here
Edit: sorry for stealing the first post btw hehe
EDIT: My changelog dedicated post have exceeded 30000 characters, so I have decided that the changelog will only be included in the respective update posts from now on!
So you all know how the situation is.
shagbag913 said:
Been following your thread over in the Pixel 2 XL forum, nice to have you here
Click to expand...
Click to collapse
I'll do whatever I can on the first generation Pixels for giving you guys & girls the same awesome experience.
And thanks btw.
:highfive:
Update!
v1.1 (Minor release)
- Made a few more (hopefully) battery conserving adjustments to the Sched governor.
Enjoy!
There is no .core folder inside /sbin, do we have to create it ? Edit: reboot solved. Couldn't see it.
Got it installed and I'm thinking it's working. Does the script turn off Core Control ? Just noticed it's off in Ex Kernel Manager , is this by design ?
Core control screenshot
Phalanx7621 said:
There is no .core folder inside /sbin, do we have to create it ? Edit: reboot solved. Couldn't see it.
Got it installed and I'm thinking it's working. Does the script turn off Core Control ? Just noticed it's off in Ex Kernel Manager , is this by design ?
Click to expand...
Click to collapse
Hm, I have not touched the specific tunable that is controlling Core Control.. Maybe it is disabled because of my Sched CPU governor tweak.
Phalanx7621 said:
Core control screenshot
Click to expand...
Click to collapse
xFirefly93 said:
Hm, I have not touched the specific tunable that is controlling Core Control.. Maybe it is disabled because of my Sched CPU governor tweak.
Click to expand...
Click to collapse
I can confirm that the same happens to me.
Thanks for the work!
Phalanx7621 said:
Core control screenshot
Click to expand...
Click to collapse
Old Man Dave said:
I can confirm that the same happens to me.
Thanks for the work!
Click to expand...
Click to collapse
I'll take a look into it later today.
EDIT: Oh snap, I forgot that I have disabled the Core Control tunable in my script. My bad, sorry.
Do you guys want to have it enabled or disabled btw?
xFirefly93 said:
I'll take a look into it later today.
EDIT: Oh snap, I forgot that I have disabled the Core Control tunable in my script. My bad, sorry.
Do you guys want to have it enabled or disabled btw?
Click to expand...
Click to collapse
I mean I'm only concerned with battery life. If you get better battery life with it off, I'm down with that for sure.
Phalanx7621 said:
I mean I'm only concerned with battery life. If you get better battery life with it off, I'm down with that for sure.
Click to expand...
Click to collapse
I will compare how my Marlin / Pixel XL performs with it disabled respectively enabled and see which "solution" that is giving best battery life with less performance tradeoffs, and then I will include the best overall compromise in v1.2 of my kernel configuration / script.
For anyone else interested in this, this is how I went about it:
1) Downloaded Flash Kernel from his thread over here https://forum.xda-developers.com/pixel-xl/development/marlin-flash-kernel-1-00-t3788300
2) Downloaded the latest version of this mod
3) Downloaded the Magisk module required, which you can find by searching Magisk for "busybox" and choosing the "Busybox for android NDK" version
4) Flash that Magisk module, reboot into recovery, flash the Flash kernel (no need to reflash magisk, it's automatic), reboot back into system.
5) Check to make sure Magisk is functioning properly, for me I had to reboot due to an error in the application but that may have been on my end.
6) So now you have Flash kernel and the Magisk module required to be able to properly run this script. Extract the script from the .zip file you downloaded to a folder.
7) Ok so these next steps if you aren't familiar with this stuff could be tricky, but it's actually simple it just sounds tricky. I use Mixplorer for this, I highly suggest using it, it's free and it's on XDA Labs here. https://labs.xda-developers.com/store/app/com.mixplorer But any file explorer w/ root access will do. Inside the folder you extracted the script into there are two versions, choose the Public Release version and copy that file. Navigate to root ( / ) and go to /data/media/0 and paste the file there. The reason for this is you have to change the permissions to allow it to be an executable script and this folder allows that. (there are other ways to do this, FYI but this works just fine for me) You want the permissions to be 755, so it would look like this: (see attachment) To change permissions in Mixplorer, just long press the file and hit the little i (for information) in the upper right. Then click on the permissions you want to change.
8) Now all you have to do is copy that file you just changed the permissions to and paste it into: /sbin/.core/img/.core/service.d | | Now you won't be able to SEE .core unless you have hidden files on, in Magisk it's in the upper right hand corner 3 dot menu. Click Show Hidden. After you paste the file there, reboot and congratulations, you have achieved greatness.
Phalanx7621 said:
.. FYI..
Click to expand...
Click to collapse
Thanks a lot for the in-depth guide! I added your guide to the OP both in this thread and over at my Pixel 2 (XL) thread!
:highfive:
xFirefly93 said:
Thanks a lot for the in-depth guide! I added your guide to the OP both in this thread and over at my Pixel 2 (XL) thread!
:highfive:
Click to expand...
Click to collapse
Oh ok cool, just wanted anybody else to be able to use this awesome mod too, it works wonderfully!
I miss this path on my pixel: /sbin/.core/img/.core/service.d
i'm on last LOS 16.0
moyses said:
I miss this path on my pixel: /sbin/.core/img/.core/service.d
i'm on last LOS 16.0
Click to expand...
Click to collapse
It's there.... I'm on the same rom. You need to start at root and not device storage, as well as show hidden folders
moyses said:
I miss this path on my pixel: /sbin/.core/img/.core/service.d
i'm on last LOS 16.0
Click to expand...
Click to collapse
Use X-plore file manager adn give Root permissions and in settings Show hidden files or folders something.
Update!
v1.2 (Minor release)
- Optimized Sched governor for best balance between performance & battery life
- Reverted pm_freeze_timeout to stock settings
- Raised dirty_ratio to 30
- Some minor script based clean-ups here and there
Enjoy!
xFirefly93 said:
Update!
v1.2 (Minor release)
- Optimized Sched governor for best balance between performance & battery life
- Reverted pm_freeze_timeout to stock settings
- Raised dirty_ratio to 30
- Some minor script based clean-ups here and there
Enjoy!
Click to expand...
Click to collapse
Hi, which release from Public and Maintenance we have to use. Thank you for your hard work.
{
"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"
}
So what is this? This is a Magisk module that adds the following features to any Pixel 3, 4 or 5 device running on Android 11:
Forces Google Sans font system wide
63 Accent colors
12 Icon shapes
22 Fonts
Wallpapers Breel 2019; 2020 & 2020a
9 different Dark Styles
Adds 2 button mode navigation (it was removed on Android 11 but I think some users like that navigation mode, so I add it)
Background Blur options
Blur Intensity options
Adaptive sound options
Navigation bar options (hide pill, reduce keyboard bottom space size, hide assist handles)
SystemUI Tuner options
Rounded corner options
QS Rows x Columns options
QS Footer Drag Handle options (Default, Accent based, Hidden)
Option to show more icon notifications on staus bar
Forces Basic Attestation thus making ctsProfile true by just enabling Magisk Hide
Rom Control app (to setup all options available that you cannot using just Styles & Wallpapers)
Everything can be controlled using Styles & Wallpapers and also Rom Control app.
This MOD will probably work on any AOSP, or close to it, ROMs.
Get it here: Android_11_Addon_Features_for_Pixel_V8.zip
Just a note, this module already includes a SafetyNet fix, so if you're using another module for SafetyNet, please remove it since I don't know if that couldn't cause issues.
For all users already running Android 12 please go to THIS THREAD.
Addon Features EXCLUSIVE for Pixel Devices running on STOCK Android 11 ROM:
These exclusive and specific for Pixel Devices running on STOCK Android 11 ROM Magisk modules that you'll see next adds all of the features stated above but with extra goodies!
"Exclusive features" included:
Battery Bar
Battery Styles
Clock Customization
Corrected lock screen icons not changing after applying different theme
"Disco Dingo" the QS (just a funny name for the option to apply random colors on QS toggles)
Hide QS Labels
Lock screen album art customization
Lock screen camera shortcut (enable/disable)
Lock screen custom clock faces
Network Traffic Indicators (unfortunately, on redfin, it only works on QS Header and not on status bar)
QS Battery percentage independent options
QS Header opacity level control
QS Headers styles
QS Panel opacity level control
QS Tiles styles
QS Data usage info
QS Rows x Columns options (both on portrait and landscape modes)
Reduce Status bar height (and correct left padding on devices with the notch on the left)
Removed side assist handles from lock screen
Status bar Quick Pulldown (Never, Right pulldown, Left pulldown, Always)
Switch styles
Touch QS Labels to add or remove on QS customize panel (just didn't bothered to translate "Tap or Drag Tiles..." strings, so you'll continue to see "Drag Tiles..." but the feature is there, try it.)
Exclusive features downloads:
Android_11_Addon_Features_For_Pixel_V13.zip -> "Harmless" module that works on any Pixel device running on STOCK ROM, much like the "universal mod" shared above, but with a Rom Control app version that has more options. The "exclusive features" options won't do anything if the SystemUI module, shared next, isn't installed. If your going to try these exclusive features module, install this one and not the one shared above. The SaftetyNet is also included on this module, so once again, don't try to use any other SafetyNet module since it could break things.
Android_11_SystemUI_for_Addon_Features_V10.zip -> This is "THE" module! This module adds all xml and smali changes into SystemUI. Without this module the "exclusive features" won't work. Also, this module could be responsible for breaking boot if it fails to work at your end. I've ran several tests on my device (a Pixel 4a) and didn't face any issues but, since this module replaces stock SystemUI for a modded SystemUI, you could run into problems if some other module tries to do the same or it's simply incompatible with it. This module was updated to match latest Android 11 October 2021 build.
Android_11_SystemUI_for_Addon_Features_V9.zip -> Use this version ONLY if you're still running any Android 11 build between June and September 2021!
Notes regarding the "exclusive version" for Pixel devices:
DO NOT, I'll repeat, DO NOT flash "SystemUI module" zip on any other ROM besides stock. It won't work! If you want those extra features on your current ROM you will have to port them yourself. I explain how to later on this post.
Make sure that you're able to run adb shell as root before rebooting your device.
If something goes wrong after flashing "SystemUI module", like if your device doesn't boot or something stupid, connect your phone to your PC during boot and run this:
Code:
adb shell
Code:
su
Code:
rm -rf /data/adb/modules/Modded_SystemUI && reboot
If you forgot to enable the ability to run adb shell as root, and if your device is on a "non-boot" state, the only way you can fix that is to remove all Magisk modules you have installed. That can be achieved by running the following commands during boot:
Code:
adb shell
Code:
magisk --remove-modules
If none of the above methods work to get your device booting, then you have to boot into safe mode. By doing so, Magisk will disable all modules for you (it doesn't uninstall them, just disables them). To force a boot into safe mode all you need to do is to keep pressing volume down button during boot animation. After the system boots into safe mode you can reboot your device to boot up normally (since all modules will be disabled). If you get stuck during boot animation again, just force another reboot (I've had to do that during my tests).
The "SystemUI module" requires that your device is already updated to March build!
When a new OTA update comes please don't flash the "SystemUI module" until I say it's ok to do so. I mean, me or any other member who may have tested it. Why? Because Google may change things on stock SystemUI between builds. When that happens, I have to recreate the module again to adapt those changes. For instance, March build was not compatible with the module that was built on top of February build SystemUI. Rest assured that I'll always test the module with new builds and update as necessary.
In case your device gets caught in a bootloop, please provide me a logcat so I may try and look if anything can be done about it. To do so, during boot connect your device to your PC and grab a logcat with this adb command:
Code:
adb logcat > log.txt
Requirements:
Unlocked bootloader
Magisk Root | Magisk Manager
Suggestion:
Uninstall all other modules you may have installed IF you're going for the "exclusive features". They could be incompatible with the "SystemUI module" thus making the device get caught in a bootloop. You may install them afterwards, one by one, just to make sure everything is ok.
If you're up to it, instead of disabling/removing modules, just flash latest stock build through fastboot. If you want to retain your data, remove the "-w" flag from the update command on flash-all script.
How to install? (If you're running a Pixel 5, just install the module...you don't need all these next steps)
Uninstall Device Personalization Services updates
Clear Google Play Store app data and cache
Flash the Magisk Module(s)
Reboot device
Open Google Play Store and update Device Personalization services (or any other Pixel exclusive app you see it needs to update).
Profit!
Video:
Check all Rom Control (with exclusive features) options HERE.
How's these "exclusive features" even possible?
All (well, not all but almost...) features that you see on Pixel Devices "SystemUI module" were reverse engineered from Evolution X ROM source code. The source code is available on the link bellow shown on the credits. This means that I've been practicing some hard core "old school" Android smali edition in order to get this working. So, yes, I have some credits about this but, if it weren't for the original developers and it's public source code, none of this would be possible. Thank them for this!
Smali, and xml, edition wasn't enough to get this working. After decompiling, changing/adapt the code and recompiling everything again, I had to find a way to make it bootable without messing with the original apk signature. And here is where VR Theme logic came in handy. So thanks for the original dev who brought us this feature.
As for ROM Control app....this was/is a project created by daxgirl and wubydax back in 2015! So yeah, I'm not bringing anything new here, I just followed their instructions in order to get the features working after editing smali/xml with the source code taken from Evolution X. The original app source code is also available on the link shared on the credits.
I've just combined all of the above into a Magisk Module and shared here so that we can get the best of both worlds....a stock ROM with custom features included.
Rom Control with "exclusive features" source code:
https://github.com/ElTifo/CustomSettingsForDevs/tree/Pixel4a
Want to port the "exclusive features" to your Pixel device running on other ROM? Here's how:
https://github.com/ElTifo/CustomSettingsForDevs/tree/Pixel4a/app/src/mods
Credits:
EvolutionX ROM team, specially @joeyhuab
@daxgirl and @Wuby986 for ROM Control project and source code.
@Tulsadiver for showing me how to adapt VR Theme logic originally used on 3Minit Battery Mod by @gharrington.
@Ticklefish for Tickle My Android
@topjohnwu for Magisk
@kdrag0n for Safetynet-fix.
@Freak07 for Adaptive Audio
Cheers and enjoy!
Typhus_ said:
This is a simple Magisk module that:
- Forces Google Sans font system wide
- Adds more accent colors and icon shapes
- Adds 9 dark styles (use cmd overlay to enable/disable them or any other method you may know to change overlay states)
- Enables Background Blur
- Enables Adaptive sound
The MOD is compatible with any Pixel 4 device running Android 11.
Made it for my personal use, decided to share for anyone who's interested on these features.
Adaptive sound takes time to appear on Settings. Just wait a few minutes.
Enjoy!
Cheers!
Click to expand...
Click to collapse
Hey thanks for this. I really appreciate the different fonts and icon shapes.
Really appreciate your work man, just a quick question; what can I modify to skip the font stuff from the module? Because I use another module for a custom font and it gets overridden by this one, tnx.
Daenjel said:
Really appreciate your work man, just a quick question; what can I modify to skip the font stuff from the module? Because I use another module for a custom font and it gets overridden by this one, tnx.
Click to expand...
Click to collapse
Open the zip and remove the /system/fonts folder. Reflash that modified zip. Done.
Thank you for your great work!
However I didn't see adaptive sound showing on the setting, even though a few hours later.
bigJbig said:
Thank you for your great work!
However I didn't see adaptive sound showing on the setting, even though a few hours later.
Click to expand...
Click to collapse
Sometimes the service doesn't run at boot. Please reboot the phone and wait like 2~3 minutes.
OP has been updated.
Safetynet fix added to the module.
Typhus_ said:
OP has been updated.
Safetynet fix added to the module.
Click to expand...
Click to collapse
Thank you again for these customization options. I've had it flashed for several days and rebooted many times and cannot locate the adaptive sound option. Would it just be under sound and vibration? Everything else is great.
floydster1708 said:
Thank you again for these customization options. I've had it flashed for several days and rebooted many times and cannot locate the adaptive sound option. Would it just be under sound and vibration? Everything else is great.
Click to expand...
Click to collapse
It should be on sound and vibration, yes. On my Pixel 4a it's here....so I can't quite understand why it isn't on yours....
floydster1708 said:
Thank you again for these customization options. I've had it flashed for several days and rebooted many times and cannot locate the adaptive sound option. Would it just be under sound and vibration? Everything else is great.
Click to expand...
Click to collapse
Same thing happen to my pixel 4.
bigJbig said:
Same thing happen to my pixel 4.
Click to expand...
Click to collapse
Please, try to uninstall the Device Personalization Services app update. Then, having the module installed, reboot and wait for, like, 2 minutes tops. Check if the option appears or not.
Typhus_ said:
This is a simple Magisk module that:
- Forces Google Sans font system wide
- Adds more accent colors and icon shapes
- Adds 9 dark styles (use cmd overlay to enable/disable them or any other method you may know to change overlay states)
- Enables Background Blur
- Enables Adaptive sound (make sure to uninstall Device Personalization Services updates before flashing the module)
- Forces Basic Attestation thus making ctsProfile true by just enabling Magisk Hide.
The MOD is compatible with any Pixel 4 device running Android 11.
Made it for my personal use, decided to share for anyone who's interested on these features.
Adaptive sound takes time to appear on Settings. Just wait a few minutes.
Enjoy!
Credits:
EvolutionX ROM team, specially @joeyhuab
@kdrag0n for Safetynet-fix.
@Freak07 for Adaptive Audio
Cheers!
Click to expand...
Click to collapse
This is terrific. Thank you
How to edit so just enables blur?
Thanks!
badaas said:
How to edit so just enables blur?
Thanks!
Click to expand...
Click to collapse
Delete everything inside /system folder on the zip. Flash the modified zip. Done.
Typhus_ said:
This is a simple Magisk module that:
- Forces Google Sans font system wide
- Adds more accent colors and icon shapes
- Adds 9 dark styles (use cmd overlay to enable/disable them or any other method you may know to change overlay states)
- Enables Background Blur
- Enables Adaptive sound (make sure to uninstall Device Personalization Services updates before flashing the module)
- Forces Basic Attestation thus making ctsProfile true by just enabling Magisk Hide.
The MOD is compatible with any Pixel 4 device running Android 11.
Made it for my personal use, decided to share for anyone who's interested on these features.
Adaptive sound takes time to appear on Settings. Just wait a few minutes.
Enjoy!
Credits:
EvolutionX ROM team, specially @joeyhuab
@kdrag0n for Safetynet-fix.
@Freak07 for Adaptive Audio
Cheers!
Click to expand...
Click to collapse
I have this font that I really like that's not included. Is it possible for me to just add it to system in your module and flash the modified zip or is there more to it than that. Not that I'm complaining in any way. I like all the fonts. Just curious
floydster1708 said:
I have this font that I really like that's not included. Is it possible for me to just add it to system in your module and flash the modified zip or is there more to it than that. Not that I'm complaining in any way. I like all the fonts. Just curious
Click to expand...
Click to collapse
The font itself won't do anything. You would have to edit fonts_customization.xml and create an overlay for it.
Another solution would be to rename the font files to roboto*whatever* and replace it inside the zip /system/fonts. But, by doing so you would lose Google Sans applied system wide. If that's your objective, then you can do it.
Cheers!
Hi, would something break with regards to the safetynet if I've already flashed this (to resolve safetynet on Android 11) and then I try to flash your file?
Typhus_ said:
The font itself won't do anything. You would have to edit fonts_customization.xml and create an overlay for it.
Another solution would be to rename the font files to roboto*whatever* and replace it inside the zip /system/fonts. But, by doing so you would lose Google Sans applied system wide. If that's your objective, then you can do it.
Cheers!
Click to expand...
Click to collapse
Ok. Cool thanks
Xaeons said:
Hi, would something break with regards to the safetynet if I've already flashed this (to resolve safetynet on Android 11) and then I try to flash your file?
Click to expand...
Click to collapse
No problem at all. But, it's useless to have 2 modules doing the same thing, so, you could just use one of them,
nvm got it figured out, thanks!