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
ⓐⓝⓓⓡⓞⓒⓛⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ
[size=+2]TweakedN3 3.95 UVUDNF9 4.4.2 SM-N900T Samsung Galaxy Note 3[/size][size=+2]... for AT&T![/size]
{
"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"
}
Hey everyone - me again, resident no-one-in-particular. Much like my previous forays into "projects"... I'm finally getting to where I feel good about posting this little mess - and it only took 4 months! Clearly I am still lacking a bit in the speed department, but hopefully folks enjoy what I've managed to muster together so far. This was originally based on the stock UVUDNF1 T-Mobile TouchWiz 4.4.2 and is now based on the stock UVUDNF9 4.4.2 base - the most recent official update at the time of writing this post... In other words - this is a stock modified T-Mobile rom! As I already mentioned this took quite a while to put together as a number of my tinkerings had to be more or less reworked from scratch (stemming from tinkerings on other devices and changes between 4.3 and 4.4.2 - and even between 4.4.2 builds), but on the upside I'm pretty happy with how things have turned out.
It should be noted that I still consider this a work in progress, so even though there are a number of things that I still want to include - at the time of writing this post I feel enough is done to warrant it actually being posted. That way others (assuming others give it a shot) can let me know if things don't work or if any oddities come up. Also feel free to comment on how this might improve, if I've gone about anything in a not-so-smart way, or if there is anything you would like to see (or wish wasn't there) - I can't promise I'll do anything about it, but such requests keep me motivated and learning, and thats been the driving force behind my tinkering since it began really
[size=+2]I AM IN NO WAY RESPONSIBLE FOR ANYTHING THAT HAPPENS (GOOD OR BAD) AS A RESULT OF FLASHING OR ATTEMPTING TO FLASH WHAT IS POSTED HERE![/size]
In an attempt to keep things clear and concise, see below for links to posts containing various bits of should-be-read info on what this is all about.
[size=+1]PLEASE NOTE:[/size] Make sure to THANK @RErick because without him the deep sleep issues that result from a disconnect between the ATT 4.4.2 kernel and the NF9/NF4/NF1 /system base would still be with us - BUT THAT IS NO LONGER THE CASE! As of Tweaked 3.9 all fixes are now included in the main install - and thanks again to RErick for the hard work on solving the deep sleep woes!
Wally's World
General installation instructions
Advanced/Custom installation/modification instructions
FAQ and notes
Downloads
Links to compatible themes
Thanks and resources
Click to expand...
Click to collapse
[size=+2]SCREENSHOTS[/size]
While the theme is pretty much stock, I figured I would throw in a few screenshots that show a few minor things. If you want to see the screenshots (and they aren't already showing) just click the "CLICK TO SHOW CONTENT" (or "SPOILER") button!
Click to expand...
Click to collapse
[size=+2]---CHANGELOG---[/size]
Code:
[u]Version 3.95 - 10/30/14[/u]
Again with some minor miscellaneous fixes
- Fixed an issue with init.d on stock kernel
- Allowed SELinux status to show in About Phone for ATT folks
-- Force update SuperSU to v2.16 for ATT permissive scripts to work
- Prevented new unlock effect sounds from bleeding over into AOSP unlock style
General
- Renamed particle and lens unlock effects to popping colors and light
- Scrapped the N3 twist on particle (or popping colors) and fully ported the S5 version
-- No longer need to force kill SystemUI when switching to/from particle
- Screen record option in power menu thanks in large part to @0xD34D
- Revert the patent block on SamsungIME autocorrect - for funsies
TSM Parts additions
=== General ===
- Added option to disable FLAG_SECURE
-- prevents disabling screenshot in some apps
- Added option to have plug-in notification use sound instead of always vibrate
=== Power menu ===
- Added option to show/hide screen record toggle
-- Also included screen record options for video size, bitrate, and sound
=== Statusbar ===
- Separated toggle color options
-- Now can color indicator and icon separately
- Added option to set custom target for TSM toggle longpress
- Added DOW MTH DD option for Day Month format
- Fixed an issue w/ other languages and the Day Month format mod
[u]Version 3.9 - 10/06/14[/u]
A few more miscellaneous fixes
- Fixed FC issues for ATT folks on SecMms and SecContacts
- Fixed issue w/ S5 Mms and SecTelephonyProvider
- Fixed FC when adjusting volume and chromecast-ing
- Corrected typos and reworked a number of things in updater-scripts
- Cleaned up things related to statusbar clock
- Fixed 30min screen timeout resetting to 10min on reboot
- Notification sound now plays when connecting charger
General
- Unlocked particle and lens unlock effects thanks to bri315317
-- SysUI is killed when switching to/from particle
-- Includes lock/unlock sounds for both newly unlocked effects
- Edited GPS toggle to cycle through all location options
TSM Parts additions
=== HardKey ===
- Added "Do nothing" options for hardkeys
- Added/altered a few icons seen in picker
=== Statusbar ===
- Cleaned up some code related to clocks
- Added option to hide clock but still show date
- Completely hide clock now in clock position settings
- Added several date/day formats to choose from
[u]Version 3.8 - 9/20/14[/u]
A few miscellaneous fixes
- Custom double-press home now works independent of s-voice settings
- Can now set Screen off as a custom target for hardkeys
- Power menu option as custom target for hardkeys no longer needs an initial activiation via power button
- AirView settings in S5 UI now points to the N3 location (so you can turn it on/off now)
- Added Font settings to S5 SecSettings UI
- Added a Tweaked version of The Box thanks to erikalin - check it out!
General
- Updated to TMo UVUDNF9 4.4.2 base
- Updated S5 SecMms (was using initial release - now NG4)
- Edited TSMParts so white/black background shows behind colored text to improve legibility
TSM Parts additions
=== General ===
- Can now disable capacitive keys from lighting up on screen touch
-- NOTE: It will still occur on lockscreen screen touches...
- Added Heads Up notification on/off
- Added custom timeout for Heads Up notification
=== Statusbar ===
- Option to enable/disable volume slider in pulldown
[u]Version 3.5 - 8/28/14[/u]
Miscellaneous Fixes
- Fixed the Call Forwarding FC in call settings
- Fixed some miscellaneous ATT-related bugs in SecPhone
- Fixed the ebay search issue
- Cleaned up some multiwindow stuff in order to make Trigger happy
- Removed camera and a few others from multiwindow stuff
- Added in some stuff to the toggle resets (both in SecSettings and TSMParts) that can help if the torch toggle gets "stuck" (I've seen this happen when there are FC issues involving SystemUI or Keyguard)
- Redid one aspect of a wifi calling check that wasn't working in SecContacts, so hopefully ATT folks will no longer have (or at the very least a decreased number of) force closes involving SecContacts
- Fixed the secure camera widget mod
- Just for funsies I also worked in the fix for the SystemServer crash based on the xposed mod put together by @thomashoffmann (info thread found here - make sure to thank him for the fix!)
General
- Updated to TMo UVUDNF4 4.4.2 base
- Removed the S5 MMS quick reply 160-character limit
TSM Parts additions
=== General ===
- Added custom Animation Scale options
-- anything in range of 0.00 to 10.00
-- did this for window animation, transition animation, and animation duration
-- also removed them in developer settings and added a link to tsm parts
- Added disable doublepress home option to hardkey settings area
- Added power menu as an option for hardkey custom app selection
=== Statusbar ===
- Can now pick custom app that opens with dateview click
-- Triggered when clicking on time/date with pulldown active
=== Touchwiz app settings ===
- Can now pick custom app that opens with upswipe on N3 TW Launcher
[u]Version 3.0 - 7/14/14[/u]
General
- Based on TMo 4.4.2 UVUDNF1
- 4 way reboot
- Added screenshot as an option for powermenu
- Removed annoying popups when using powermenu data/airplane mode toggles
- Syscope has been eviscerated - system official status
- CarrierIQ removed/edited/neutered as well
- custom boot animation support
-- just inject bootanimation.zip in /system/media
-- if not included, will play stock qmg instead
- Replaced TMo-flavored bootanimation/shutdown qmgs with international variants
- Appended PowerOn/Off.oggs w/ .bak to "remove" those sounds
- Increased max number of lockscreen widgets allowed from 5 to 8
- Disabled the annoying how-to-clear-defaults popup when selecting "always" for default app
- Unrestricted widget selection for lockscreen widgets
- The funny haha from 4.3 has been worked back in :)
- Made some minor edits related to tethering - of varying worth it seems, so be warned
- Edits throughout that allow for the removal of wifi calling things for non-TMobile phones
--- NOTE: This just means things have been prepped for such a scenario - wifi calling is still included!
--- For those not using TMo service, you need to opt for the appropriate carrier to ATT-ify things!
- Edits made to neuter/remove the rom-side dvfs hijinx - thanks #bizcoon for the help :)
-- Left wakeup booster intact to avoid wakelag
- Disabled signature checks
- Removed some Knox apks
- Forced all apps in multiwindow/penwindow
-- If an app doesn't agree w/ it, you can add the package name to /system/etc/mwin_exclusions.txt
-- App-Specific Mods (Listed Alphabetically) --
MultiWindowTrayService edits
- Force the allowing of quad view
PopupBrowser.apk
- Oldie but goodie from N2 - up-and-running and what not :)
PageBuddyNotiSvc2 edits
- Allowed apk to listen to settings so you can shut off notifications
- Headphones connected, spen detached, etc.
SamsungCamera edits
- Removed low battery restrictions
- Prevent music pausing when focus/shutter sound plays or when taking video
- Can now take video while in call - because why not right?
SamsungIME edits
- Enabled native longpress delay controls (200, 300, 500ms or custom)
SecEmail edits
- No longer force-closes if you remove MagazinesHome/Lounge (MyMagazines)
SecLauncer edits
- Enabled theme chooser capability
- Included theme chooser, including 6 extra theme apks
SecSettings edits
- Disabled some popups (adb, nonmarket, wifi on when turning on hotspot)
- Disconnected from tether provision apk
- Disabled font apk checking
- Enabled menu list/grid option on stock ui
- Added spen, removed fingerprint and rearranged some things on "s5" ui
- Enabled font clarity option
- Enabled spellcheck on/off in language settings
-- May require install of keyboard like google keyboard
- Enabled call/message block
- Refined some of the animation step options in developer settings (.25 and .75 added) - thanks bajasur!
- Connected notification panel settings w/ tsm toggle settings
-- Won't let you add more than max set by custom toggle number setting in tsm
-- Won't let you remove if you have only 3 active
SecMms edits
- Slight bump to attached mms image quality
- Slight increase to allowable size
- Increase to allowable recipients, messages, sms-to-mms thresholds
- Enabled emoji to be sent as sms
- Enabled folder view option, save to sdcard, reply all option
SecContacts edits
- Increase to allowable recipients to match SecMms
- Added image for VoLTE icon when using Call Icon display mod
SystemUI edits
- Enable auto-brightness adjust in pulldown
- Added 3 toggles (TSM, wificalling, flashlight)
-- Borrowed a little from the TMo S5 "official" wifi calling toggle
- Unlocked a number of hidden toggles
- Added an S5 version of smart network toggle icon
- Eliminated popups/warnings on data/airplane/wifi hotspot toggles
- Toggles will "re-size" when fewer than the custom portrait/landscape number of set to show
- Made some image/xml edits with the help of foreverloco and wally3614
-- Allows custom notification background to be seen better, and can allow for transparency
-- Lessened the amount of dim that occurs to the background when pulling down notification panel
- Edits to SecSettingsProvider to have all toggles show after data wipe
TSM Parts
- Underwent some MAJOR restructuring -
- Added ability to set it as a shortcut
- Open pen app window
=== Device info ===
- Device information
- Battery history
- Battery information
- Usage statistics
- Wifi information
=== General ===
- Link to developer options
- Option to disable wakeup booster (only allowed dvfs element, hopefully anyway)
- NFC mod type
-- Stock, lockscreen, screen off
- Option to choose custom air command text color
- Custom popupbrowser popout app
-- Requires popupbrowser from 4.3 tweaked...
- Screen off animations (NOT "on" - by design)
-- Stock (200ms fade), CRT (400ms), Fade (600ms)
- Disable wake on un/plug
- Disable low power screen dimming
- Disable low/full battery notification
- Hide pagebuddy notifications
- Enable volume panel expanded as default
- Enable/disable headphone ear protections
- Power menu options are now working
- Hardkey options -- NEW --
-- Volume cursor control type
--- Up/down moves cursor in text field left/right
--- Up/down moves cursor in text field right/left
--- Up/down does not move cursor in text field (stock)
-- Enable volume music controls
--- Option to set volume up/down longpress action
--- Can choose from skip, previous, or pause
-- Alter actions of doublepress home; longpress menu, back, home
--- Can pick any shortcut or visible-to-app-drawer app for any of them
--- Can also choose "screen off" option
-- Longpress app kill options
--- Can set to menu, back or none
=== Lockscreen ===
- Link to SecSettings lockscreen options
- Option to use custom lockscreen timeout
-- Can choose between 3-30 seconds
-- Note that SmartStay will override these settings
- Option to alter sview background (altered option is just flat black)
-- This also forces the apply-to-all to be NO in SecSettings when checked
- Option to force cover to be considered SView cover
- Option to disable lockscreens (separate from secsettings option)
- Option for Note3 or AOSP style lockscreen
- Option to disable aosp haptic feedback
- Option to allow quick pin/pass unlock
-- NOTE: This will cause a perceived slow down in responsiveness as every letter typed beyond three gets checked
- Allow camera widget on secure lockscreens
- Option to use custom carrier text (and choose text)
- Option to choose custom carrier text color
- Option to disable powermenu on lockscreen
- Option to disable home button wake
- Enable lockscreen torch
-- NOTE: Does NOT work on SView screen - this is by design
- Option to enable volume wake (requires kernel support or device to be plugged in after few seconds of screen off)
- Option to enable finger ink when swipe + ripple are on
- Option to enable custom ink colors
- Option to set custom ink color
=== Statusbar ===
- Option to toggle between S5 and N3 UI for SystemUI
- Enable statusbar brightness control
- Enable doubletap statusbar sleep
- Disable in-app icon dimming
- Option to use custom color for status bar
-- NOTE: Statusbar will still behave as it did on stock in regards to transparency
- Option to locate toggles at top/bottom or hidden from notification area (thanks to cbucz24 for starting the bottom toggle work!)
- Link to stock toggle options
- Toggle reset is functional
- Set max number of scrollable toggles
- Option to limit number of toggles shown on panel to same max scrollable number
- Set portrait/landscape toggle number
- Turn on/off and set custom toggle/toggle text color
- Option to hide toggle text completely
-- This also shrinks the toggle size - thanks @timurg for pointing me in the right direction :)
- Show/hide brightness bar
- Clock options
-- AM/PM type
-- No clock
-- Left/right/center
-- Custom clock color
-- Day of week large/small
- Accurate data icon type
- Enable persistant data icon
- Show dBm, label, and color options
- Option to hide signal icon
- MIUI battery bar options
-- standard miui feel
-- mirror
- Enable charging animation of battery bar
- Can also set color of battery text/bar via battery text/bar options
- Removed hide battery checkbox
- Show battery % text option
- Now icon type has 4 options
-- 4.4 stock
-- 4.4 w/ percent in icon
-- 4.3 image based (charging not animated, charging icons do not have anim in name)
-- none
- Option to alter color of 4.4 battery and text/bolt
- Option to use static image, animation, or custom color for notification area background (thanks to @jimmydene84 for starting the work on this one!)
- Option to use stock or animatation sequence for notification area close handle (thanks to @wally3614 for images!)
- Date/Clock color
- Show clear in header (AOSP style)
- Hide no notifications text box
- Hide Notifications text box
- Use custom carrier text
- Use ATTcarrier (statusbar) location
- Set custom carrier text
- Set carrier text color
- Statusbar hide nfc icon option
- Statusbar hide smart screen icon option
- Statusbar hide blocking icon option
- Statusbar hide ime picker icon option
- Statusbar hide alarm icon option
- Statusbar hide bluetooth icon option
- Statusbar hide vibration/silent icons option
- Statusbar hide wificall icon option
- Statusbar hide no sim icon option
=== Touchwiz app settings ===
- Switch between stock and "S5" ui
-- restarts Secsettings in new ui
- Email exchange bypass
-- MUST set this to what you want PRIOR to setting up the account!
- Steady ringer
- Skip call ended screen
- Show record button
-- NOTE: call recording now works out-of-the-box - seems TMo fixed that!
-- That being said - thanks go to freeza for pointing me to where the edits need to go if not already there!
- Show call in contacts
- Enable scrollable wallpaper
- Enable infinite scroll
- Enable hide apps/disable apps in app drawer
- Alter home upswipe target to Google Now
- Enable smiley button
- Network time stamp
- Disable sms/mms logs
- Enable convo send/recieve text color
- Enable thread list send/receive text color
Let me know if there are any suggestions/issues/etc. - also, feel free to stop by the IRC channel Alexia Whitehurst was so kind to make for all of this on freenode - #tweaked. If you don't have an IRC client you can always use their webchat interface here. Happy flashing!
XDA:DevDB Information
TweakedN3 v3.x, ROM for the AT&T Samsung Galaxy Note 3
Contributors
dwitherell
ROM OS Version: 4.4.x KitKat
Based On: Stock UVUDNF9 T-Mobile
Version Information
Status: Stable
Current Stable Version: 3.95
Stable Release Date: 2014-10-30
Created 2014-07-16
Last Updated 2014-10-30
BELOW ARE RESOURCES FOR MY THEMES @foreverloco THEMES l. All in one post baby!
KRYON THEME
FOR THE GALAXY NOTE 3 on ATT & TMO RUNNING TWEAKED NF1 KITKAT ROM O N L Y
KRYON THEME is a new theme that digs a little deeper into your Touchwiz ROM's DNA. Its not just image work, but expanding into the smallest things and exploring/exposing new ideas that will make Touchwiz become almost a new UI feel. With KRYON THEMEs, I wanted to merge that edgy taste with a bit of class, to the Touchwiz experience while driving that happy feel and sleek look through out. As an avid AOSP lover, I simply love the Note 3 and all its glory, just not the hideous look of stock TW. KRYON THEME hopes to make you smile
These versions are IN BETA RELEASE and consists of the Main Structures-Framework, SecSettings, SecContacts, SecPhone, SystemUi, S5-Mms, Calculator, Job Manager, MultiWindowTray, MusicPlayerWT, Camera and Clock of course there is more to come. Just getting started...
Screenies:
MATERIAL-L
FLAT MURDER
RED-FLAT MURDER
DOWNLOAD LINK HERE:
http://forum.xda-developers.com/showthread.php?p=53607818#post53607818
For FOREVERLOCO's BADAYUSS AOSP Multi Color Themes for Tweaked
Download Link Here:
http://forum.xda-developers.com/showthread.php?t=2676315
[size=+2]TWRP/Safestrap Installation instructions[/size]:
While this rom does offer some customizable options at install - THE CUSTOMIZATION PROCESS IS NOT QUITE THE SAME AS OTHER ROMS!!
What does this mean? Well, if you want to tailor your installation using some of the available options, you'll have to read up on how to do so.
Wut?!? I have to read then!?! NOO!!!!
LOL - well like I said you really don't HAVE to read about this, it's only if you want to customize things outside of the default setup. If you don't want to customize anything, then simply flash the main TweakedN3 zip and be on your way. NOTE:Info on default and custom install options can be found in the installation instructions zip!
So you want to customize the install? Sounds good - and read on.
This was an idea that I started using over on the Note2 (though I've changed what I consider "default" a bit), and given the lack of aroma capabilities while using safestrap it at least offers an approach that lets users customize things a bit. Another advantage (for those that like customizing a bit at install anyway) is that after an initial step - future re-flashes of the rom will always utilize the same selections (assuming you don't delete some files in a particular directory of course). This should be a boon to those that enjoy flashing this and that, as the process of reinstalling this will now be tailored to what you want. [size=+1]NOTE:[/size] Unless you use the default approach you will most likely need to edit/redo this process for each update to make sure all new/edited options are up-to-date! This isn't excessively relevant yet, but it will be soon enough I imagine.
A complete explanation of the customizable-install approach can be found in this post, but for the sake of brevity and simplicity I am going to focus on the approach most fitting to the general (or new-to-flashing) user.
Before getting into that though, remember that the usual rules still apply:
- While very much stable in my experience you should be cautious whenever you flash. Make sure to wipe data/factory reset to avoid issues.
- I highly recommend wiping data before getting started with any of this. This is just a recommendation - not a requirement - though if you have issues that is almost always one of the first recommended fixes.
- I also recommend you already be on the 4.4.2 update, as this is a 4.4.2 rom and I imagine requires (or if nothing else works best with) a 4.4.2 kernel
- Tweaked needs to be flashed in a custom recovery - and thanks to the hardwork of @Hashcode this can be done via his Safestrap that can be found here. Make sure to THANK HIM for this, as none of this would be possible without his work!
[size=+1]THE SUPER SIMPLE SAFE APPROACH[/size]
Well the super simplest of all approaches would be to just flash the main install zip. For those that tried any of the 4.4.2 alpha/beta zips discussed here the result will be very similar to what was experienced with those. For those that would like to tailor the install a bit, you'll need to check out this post for instructions. Basically there is a directory you need to place on your internal or external sd card, and inside that directory are files that can be edited to reflect the particulars you would like to be installed.
Below is what I would consider the general fits-whatever-install-approach-you-chose installation instructions:
[size=+1]THE GENERAL APPROACH[/size]
- Backup your current setup/data
- Decide which install route (default/custom) is best for you
- Download the main installer and put it on your internal/external sdcard
- If you decided on the custom install route
--- Download relevant zip for said approach
--- Extract directory inside zip and place it on internal/external sdcard as instructed
--- Edit install.prop and anything else required to reflect your install choices
- Boot into safestrap recovery thanks to Hashcode
- Recommended to wipe data/factory reset
- Select and install the main Tweaked rom .zip you put on your sdcard
Click to expand...
Click to collapse
[size=+2]How to custom install Tweaked[/size]
So you've decided to customize the install a bit eh? Good to hear.
[size=+2]NOTE:[/size] For this approach please be aware that the process will likely need to be redone with new versions to make sure you have access to all available options!
I will try to keep changes to these files minimal, but changes are inevitable, so make sure to stay up-to-date with the version you are flashing, as otherise you will likely get the default install!
[size=+2]ALSO -[/size] with this custom install approach you can place the TweakedInstall directory on either the internal or external sdcard. That being said, in general if you have a TweakedInstall directory on BOTH your external AND internal sdcard, the files in the external sdcard directory will be chosen over those in the internal sdcard directory. Furthermore - it is VERY important that you DO NOT RENAME ANY OF THE FILES OR THE DIRECTORY! If you do you will likely get a default install when flashing the main installer (not the worst thing of course).
[size=+2]----- CUSTOM -----[/size]
This approach requires changes you will have to do, and therefore needs a little reading and preparing ahead of time. In order to help things along, I've put together a zip file (see downloads post here) with instructions and needed files - make sure to read the... well, the README! The contents of that readme file are below:
--- From the READMEFIRST-INSTRUCTIONS.txt in the ATTInstallInfo.zip file ---
####################################
# HOW TO CUSTOM INSTALL ON ATT: #
####################################
### NOTE: THE INSTALL.PROP EDITING DESCRIBED HERE ###
### NEEDS TO BE COMPLETED PRIOR TO FLASHING THE ROM! ###
1) Decide if you will be editing text files on the computer or the phone
- regardless of where you do this, the result must go in a specific directory on your internal/external sdcard (see below)
- if you use a computer to edit, make sure it uses the Unix-style end-of-line character (you can use Notepad++ on a PC)
- Not all text editors work as you need them to if doing this on the phone - I have only tried it using the built-in text editor in Root Explorer
######## THIS IS VERY IMPORTANT AND A SOURCE FOR SIMPLE MISTAKES - YOU HAVE BEEN WARNED! ########
2) Extract the TweakedInstall folder (either on PC or extract it to the ROOT of your sdcard - internal OR external)
- Inside are five files - the main one of interest for installing is install.prop
3) Open install.prop using a text editor and read the instructions
- it is on this file you select options
- this is similar in idea to how aroma works
- ALL you are doing with this is changing the numbers that come after the = signs
- DON'T CHANGE ANYTHING ELSE! ONLY NUMBERS!
- Follow the instructions for what each number means for each choice
4) Complete any other OPTIONAL file edits per how you want to install
OPTIONS INCLUDE (these are for the more advanced users around - THEY ARE NOT NEEDED AND CAN BE IGNORED):
- If you opted to further debloat beyond available options and have set dangertweak to = 1
- edit the applist file with the apk name that you want removed
- ONE APK PER LINE
- see baseapplist.txt for a list of apk names that are included on /system as "default"
- If you opted to keep some pre-existing system files and have set savelist to = 1
- edit the savelist file with the full path to the file you want saved
- so for example if you wanted to save a script file called 02ForExample that was in the init.d folder, you would enter
/system/etc/init.d/02ForExample
into the savelist file
- ONE PATH PER LINE
5) Make sure the directory along with your newly-edited files are moved to your sdcard if not already
### IMPORTANT: THIS DIRECTORY HAS TO BE AT THE ROOT OF YOUR SDCARD (INTERNAL OR EXTERNAL)!! ###
### IMPORTANT: THE NAME OF THIS DIRECTORY MUST NOT CHANGE!! ###
### IMPORTANT: YOU ARE DOING THIS AT YOUR OWN RISK!! ###
6) Boot into recovery and flash the Tweaked rom zip
TAKE HOME:
The edited install.prop file (and optional ones related to it) being kept in the TweakedInstall directory on your sdcard will make it so you won't need to do any choosing the next time you want to flash the main installer. You can always come back to or reflash Tweaked exactly how you have set it up with no extra effort!
#########################################
# HOW TO USE MODIFICATINATOR ON ATT: #
#########################################
### NOTE: THE MODIFY.PROP EDITING DESCRIBED HERE IS ###
### TO BE DONE WHEN WANTING TO MAKE CHANGES AFTER ###
### THE ROM HAS BEEN INSTALLED! THE EDITS NEEDS TO BE ###
### COMPLETED PRIOR TO FLASHING THE MODIFICATINATOR! ###
Ok, let's say you've installed the rom and made a few custom selections, or regret not making some in hindsight. You can - without reflashing the entire rom - just go through and install/uninstall the particular thing you want to change using the modificatinator zip. BUT - it also requires you to do edits SIMILAR (but NOT IDENTICAL) to those you made to the install.prop, however in this case you will be using the modify.prop file. If you followed the above instructions for preparing a custom install, the modify.prop will be in the same directory as your install.prop.
1) Decide if you will be editing the modify.prop on the computer or the phone
- regardless of where you do this, the result must go in the same specific directory on your internal/external sdcard that the other files mentioned above are in
- if you use a computer to edit, make sure it uses the Unix-style end-of-line character (you can use Notepad++ on a PC)
- Not all text editors work as you need them to if doing this on the phone - I have only tried it using the built-in text editor in Root Explorer
2) Open modify.prop using a text editor and read the instructions
- it is on this file you select options
- this is similar in idea to how aroma works
- ALL you are doing with this is changing the numbers that come after the = signs
- DON'T CHANGE ANYTHING ELSE! ONLY NUMBERS!
- Follow the instructions for what each number means for each choice. PAY ATTENTION TO WHAT THE NUMBERS MEAN!
4) Move the edited modify.prop to the proper directory (same one the install.prop is in) if not already
### IMPORTANT: THIS DIRECTORY HAS TO BE AT THE ROOT OF YOUR SDCARD (INTERNAL OR EXTERNAL)!! ###
### IMPORTANT: THE NAME OF THIS DIRECTORY MUST NOT CHANGE!! ###
### IMPORTANT: YOU ARE DOING THIS AT YOUR OWN RISK!! ###
6) Boot into recovery and flash the modificatinator zip
TAKE HOME:
The edited modify.prop being kept in the TweakedInstall directory on your sdcard will need to be edited every time you want to use the modificatinator zip.
### WHEN EDITING TO MAKE A SELECTION MAKE SURE THAT ANY OPTIONS YOU HAD PREVIOUSLY SELECTED HAVE BEEN EDITED BACK TO "NO CHANGE" VALUES AS WELL!!! ###
--- End READMEFIRST-INSTRUCTIONS.txt -
The hope is that these instructions are as simple but as thorough as possible for those wanting to embark on the custom approach.
[size=+2]FAQ[/size]
Q: What the hell is TSMParts (new option in Settings menu)?
A: An interface for a huge slew of mods and tweaks, the base of which was originally put together by the original members of TSM and has since been inspired by impressive works of numerous others - the TSM Parts interface acts as a control for all of the customizable fun available. There are a large number of options there - so make sure to check them all out!
Q: TSMParts is asking for superuser access?!?
A: Yep - there are some options that will need it, so make sure you grant it!
Q: I'm having overlap issues with statusbar icons and center clock - what should I do?
A: Yeah - things may overlap, so you will have to either change settings to avoid the issue or just deal with it.
Q: I set a statusbar icon to hide, but it's still there. What gives?
A: The statusbar icon tweaks may require a little effort on your part for changes to take effect. All changes can be elicited with a reboot/hotboot, BUT for most there are other ways:
-- Bluetooth/vibrate-silent/alarm icons/ime/nfc/wificalling -- just change their state (on/off or vibrate/sound, etc)
-- No sim -- if the notification is already active you will need to reboot/hotboot to hide it
-- smart "eye" icon -- changes will happen once the eye triggers
Q: How is battery life on this rom?
A: This is a stock modified rom. As such, battery life will be equivalent to stock were you to be running a similar array of apps and kernel - it really should be no different than stock otherwise (which imo is not half bad really). The kernel and misbehaving 3rd party apps have more to do with battery life than a modified stock rom - at least in my opinion (and experience, though it's limited).
Q: So tethering is a common topic... can it be done with this?
A: To be honest I am unsure as to how tethering will behave using AT&T as the carrier... there was an annoying upsell message that TMo folks would get that I tried to set up to avoid, but in theory tethering SHOULD work on this. I will update this once it has been confirmed by a few folks
Q: Why isn't the accurate data icon mod working!!?!
A: The only time that mod shows an effect is when you are on the T-Mobile or ATT network - I don't believe other networks will see a change in data icon behavior.
Q: What is this LMT thing? How do you use it?
A: You need to check out noname81's thread here for info on that!
Q: Why can't I toggle off/on the security settings for exchange-based emails using the stock email client?
A: Mostly because I haven't been able to figure out how to do it. As long as you set it up to how you want PRIOR to setting up the account, AND you don't change the setting later - you should be fine.
Q: Why is it that when I swap the settings UI type the settings icon itself seems to move in the app drawer?
A: The toggling of the two UI types make the SecSettings package "appear" different to the system, so it's location in the app drawer may change after toggling depending on the launcher and settings used. This is normal and of no concern.
Q: I have an N9005 - can I flash this?
A: Thankfully the N9005 can pretty much flash any N900T rom, but there can be issues with things like wifi/bluetooth/nfc. Thanks to some due diligence searching of @galaningenieros and his pointing to the good work of @cdmvirt here, you can fix it right up by flashing the files found in this post!
Q: I'm getting a force close when I try toggling N3/S5 in TSMParts > Statusbar options... WHY YOU MAKE ME BREAK MY PHONE?!?!!
A: This has been an odd one, but it appears as if the blame resides within a few xposed modules. In particular, the iOS battery module and wanam have both been implicated. I will try to come up with a way around it, but if you uninstall these modules your toggling experiences should improve.
Q: I flashed this in safestrap and either used an old install.prop or none at all - why did I get an AT&T install?!?
A: I did this on purpose - I made it so when flashing it assumes that if you are using the default install.prop and in safestrap that you want an ATT-ified install (assumes you have an N900A and ATT as a service provider). If this is NOT the case - you can override this by updating or setting up a current install.prop
Q: Why don't you mention blah blah blah in your FAQ? It would have helped me a lot!
A: My bad - PM me anything you think should be added to this that would be helpful for the general user base!
[size=+2]Miscellaneous Notes[/size]:
- [size=+1]REMEMBER -[/size] Regardless of what install approach you use you can always use the Modificatinator to un/re/do virtually [size=+1]ANY[/size] of the options available to you in the main install! No need to reflash the whole rom!
Even if you don't use it right away, make sure to GRAB THE MODIFICATINATOR HERE NOW so you have it if you want it later!!
- Updates that come after the initial release MAY also have a flash-update-only option - whether or not it does just depends on the specifics of the update. [size=+1]NOTE:[/size] Depending on what is updated, an update-only flashable may break things if you are themed! I will try to avoid this as much as possible, but all it takes is a minor edit to a framework-res.apk string (for example) to necessitate an overwriting of a file typically quite important for themers (resources.arsc) - just be mindful of this please
- This is still pretty much an unthemed rom - so if any would like to change this PLEASE let me know (a themer I am not!). This is reflective of the thinking behind the whole setup as being nothing more than stock with some extra options. On that note - for those that like flashing various mods and what not, be wary - unless it specifies that it was made to work with Tweaked it likely will not.
- If you are unable to grab a logcat of a force close/issue, there is a directory on your phone that may contain files I can use in a similar way.
/data/log/ is the directory, and the files that offer tidbits and clues as to what the issue was start with the name "dumpstate_". If you send those to me along with an explanation of what went wrong, I will be much quicker to figuring out (and hopefully resolving) the issue!
Click to expand...
Click to collapse
[size=+2]---MAIN DOWNLOAD LINKS---[/size]
Note 3 UVUDNF9 Tweaked v3.95 -- Mirror
NOTE: THIS IS THE FILE THAT INSTALLS THE ROM
md5: 1FB05B0D42AC12CC77BC88F81A8B7913
Tweaked v3.9/3.95 Custom Install Information -- Mirror
NOTE: This is NOT a flashable zip! Open it up and read through it!
[size=+1]---OTHER DOWNLOADS---[/size]
Tweaked ATT Modificatinator UVUDNF9 v3.9/3.95 -- Mirror
NOTE: This is an aroma-inspired installer that lets you un/re/install most of the mods from the main installer
NOTE2: YOU MUST EDIT MODIFY.PROP TO USE THIS!!! SEE INSTRUCTIONS HERE FOR MORE INFO!!
md5: BD344DFE9F81BA4E00177F57B1E4ADAA
Tweaked MiniUpdate 3.9-to-3.95 -- Mirror
NOTE: THERE WILL BE ISSUES IF FLASHED WHEN NOT ALREADY ON 3.9!!
NOTE2: This one has a strong chance of NOT breaking themes! Yay!
md5: 4543A646B574FC9C5A9C9C3EB3D12263
[size=+1]---DOWNLOADABLE FIXES---[/size]
-- SecMms (N3) 3.9+ Fixes --
ATT Stock White N3 SecMms Fix
md5: 19B29430E8D99868E19882A8366819DD
ATT Stock Inverted N3 SecMms Fix
md5: 9D843240393E04BE4F51083B6042BBD9
-- SecContacts (N3) 3.9+ Fixes --
ATT Stock White N3 SecContacts Fix
md5: 57142AF3D851AD301509706849FB7165
ATT Stock Inverted N3 SecContacts Fix
md5: D0C96DCD8BAEB29AB66202480CD0F97C
---old download links---
Note 3 UVUDNF9 Tweaked v3.9 -- Mirror
NOTE: THIS IS THE FILE THAT INSTALLS THE ROM
md5: 9EE03F5A6794BA5658A48621954E6433
-- General fix for N900A users --
ATT-ify zip - Flash to make phone ATT friendly!
md5: 0DF254A405856835F66FAB487E34B40E
Note 3 UVUDNF9 Tweaked v3.8 -- Mirror
NOTE: THIS IS THE FILE THAT INSTALLS THE ROM
md5: E76C041A751BEC3BFFC1D3A4571C4BE9
Tweaked v3.8 Custom Installer Information -- Mirror
NOTE: This is NOT a flashable zip! Open it up and read through it!
Tweaked ATT Modificatinator UVUDNF9 v3.8 -- Mirror
NOTE: This is an aroma-inspired installer that lets you un/re/install most of the mods from the main installer
NOTE2: YOU MUST EDIT MODIFY.PROP TO USE THIS!!! SEE INSTRUCTIONS HERE FOR MORE INFO!!
md5: 42610B64150AC5125277D3FB74719D34
Note 3 UVUDNF4 Tweaked v3.5 -- Mirror
NOTE: THIS IS THE FILE THAT INSTALLS THE ROM
md5: DB29DF70820370B014DAFEB39F08C61D
Tweaked v3.5 Custom Installer Information -- Mirror
NOTE: This is NOT a flashable zip! Open it up and read through it!
Tweaked ATT Modificatinator UVUDNF4 v3.5 -- Mirror
NOTE: This is an aroma-inspired installer that lets you un/re/install most of the mods from the main installer
NOTE2: YOU MUST EDIT MODIFY.PROP TO USE THIS!!! SEE INSTRUCTIONS HERE FOR MORE INFO!!
md5: 32E070A023E189AF8F78DABB80C1F8DD
Note 3 UVUDNF1 Tweaked v3.0 -- Mirror
NOTE: THIS IS THE FILE THAT INSTALLS THE ROM
md5: B48A541B5B5CD590B9A1A5E6BE5E735C
Tweaked v3.0 Custom Installer Information -- Mirror
NOTE: This is NOT a flashable zip! Open it up and read through it!
Tweaked ATT Modificatinator UVUDNF1 v3.0 -- Mirror
NOTE: This is an aroma-inspired installer that lets you un/re/install most of the mods from the main installer
NOTE2: YOU MUST EDIT MODIFY.PROP TO USE THIS!!! SEE INSTRUCTIONS HERE FOR MORE INFO!!
md5: BAFC2C88E113054E8196A62CE9BCD1C6
[size=+2]---LIKE THEMES?---[/size]
Good! As time goes on hopefully there will be an increasing number of themes made SPECIFIC FOR TWEAKED! This will be good, as while there are a number of themes out there that would likely at least partly work ones made specifically for Tweaked will completely work! Below is a list of such themes for ease of reference!
I will update this list as new ones come out, so make sure to check back from time to time! Also - MAKE SURE TO THANK THEM! There aren't many who have done this, so make sure they know the work is appreciated!
[size=+1]Themes that have been made for Tweaked[/size]
Even though they are listed here, MAKE SURE THEY ARE COMPATABILE/UPDATED FOR THE VERSION OF TWEAKED YOU ARE USING!
- AOSP by foreverloco
- KRYON themes (there are more than one!) by wally3614
- REDRUM, RareAir, and Stock Blacked Out by SICKMADE
- Black and White by cbucz24
- Illuminati by cerj
[size=+2]THANKS GO TO:[/size]
sbrissen - smali tips and what not
nitsuj17 - tips, advice, useful info, and tireless stifling
imnuts - far too many reasons to list
jt1134 - far too many reasons yet again
ChainsDD and Chainfire - reasons upon reasons
iBotPeaches and JesusFreke - none of this would be possible without the work they are doing!
Hashcode - Safestrap, making flashing possible on N900A!
Alexia Whitehurst - support, theme/mod work, and a host of other things too numerous to name
wanam/lidroid - amazing guides
amarullz - awesome install utility
0xD34D - awesome screen record app
dirtybudha - for lending me some server space for screenshots and mirrors
wally3614 - awesome icons, boot animation, AT&T testing, and amazing theme work!
cbucz24 - help with .9s and getting the bottom toggle mod started, general idea creating and testing, image work
jimmydene84 - getting the animated handle/pulldown backgrounds started, general idea creating and testing
jdidtht - ridiculous amounts of support, testing, and encouragement
wcoast - testing and finding all kinds of interesting things
micmars - words cannot describe... well generally they can, but they are hard pressed when targeting this one
nijel8 - a number of awesome mods (settings package names, mms text coloring, awesome call ended screen mod info, secemail mods, tsmparts improvements, etc.) - great help!
itsmikeramsay - helping get the AT&T side of things up and running, kernel stuff
JaeKar99 - for past awesome wallpaper/banner/boot animation work
Warrior1975 - for kicking things off to even get this phone in the first place
AkaTheMacDaddy - tester extraordinaire and endless encouragement
KalEl7 - tester extraordinaire and endless encouragement
boobah204 - testing and idea stimulating
xperiacle - for great mods involving multiwindow, source for secthemechooser and theme apks
mikeyxda - help w/ non-murky ripplier lockscreen
sbreen94 - general s5-relavent discussions, and info on a few mods
bajasur - for help in working out a few trickier mods
foreverloco - for making an awesome AOSP theme and inverted apks specific for my muddled mess of a rom, and some new gps icons!
prdog1 and mikeybones - critical pieces to the long-press-kill mod
prdog1 again - general support/info/help
deeznutz1977 - testing and idea making
hangoutohfreeza - you know who you are
businesscoon - nuf said
icedventimocha - for help with toggle images
ReelFiles - uber-thorough testing of little-used nuances
Owlensteed - testing and mediafire goodness
beanstown106 - pointing me towards the aosp lockscreen info
RErick - help in talking through some ATT issues, reboot recovery and safestrap, and the vibration based deep sleep fixes!
chopperthedog - for hooking me up with file hosting stuffs
gunnermike - also providing hosting for files
Endless2232 - layout (and general) xml guidance
MidnightNinja - image repairs and what not
loserskater - improved volume skip info
[email protected] - help w/ SysScope from back in the Note2 days
noname81 - all the good LMT launcher work - check out his thread for more info!
didact79 - awesome guides that have pointed me in the right direction numerous times
JoshBeach - helping me debug things without even knowing it
Gunthermic - unintentional idea generating
lacoursiere18 - idea generating, help with the fullscreen caller mod
Dr.Ketan - all the great fullscreen caller mod work
bri315317 - all the help with unlocking the particle and lens unlock effects
dragonstalker - pointers, tips, general helpfulness
erikmm - pointers, tips, general helpfulness
merwin - pointers, tips, general helpfulness
All of TeamSbrissenMod and those responsible for TSMParts
Anyone else I likely forgot
Click to expand...
Click to collapse
[size=+2]ALL OF THESE PEOPLE DESERVE YOUR THANKS! MAKE SURE THEY KNOW THAT![/size]
Beyond the contributions of the above individuals, there were a number of guides found on xda or via google that were used along the way. Some representative samples include:
Heads Up Notification information
CRT/Fade animation guide
This and this were looked at for upsell avoidance attempts
Finger ink effect
Aroma installer info
Call recording guide
This and this held clues for the Nfc screen off/lockscreen mod
SecMms.apk modding info
Better volume skip info
This guide helped me figure out my twist on the lockscreen torch
Signature verification removal
Quick enter mod guide for pin/pass lockscreens by loserskater
FemBlack and XBlast for clues on volume key cursor movement
zst123 and XuiMod for clues and smali bits regarding muiu battery bar mod
C3C076 and GravityBox for clues regarding statusbar brightness control mod
This and this - sources and info on SecThemeChooser and theme apks
A bunch of others that have become buried in my browser history...
Another KK ROM. Awesome!
Alright - things should be all set now
This wasn't all that popular before, and I know it looks a bit convoluted - but I hope those who have tried it in the past will feel some level of familiarity with it!
I hope all goes well, and apologies for any issues that may arise
Thanks bro!!! Hoping this works out for me!!! Keep beastin bro
Sent from my SM-N900A using XDA Free mobile app
nvm , worked thanks for the rom
RoyalYeo said:
nvm , worked thanks for the rom
Click to expand...
Click to collapse
so can you just flash the rom without the custom install or is that a requirement for the att version?
gharris040604 said:
so can you just flash the rom without the custom install or is that a requirement for the att version?
Click to expand...
Click to collapse
i flashed it without the custom install , but im not sure since my note is unlocked and im on tmobile.
Yes been waiting for this rom to drop
gharris040604 said:
so can you just flash the rom without the custom install or is that a requirement for the att version?
Click to expand...
Click to collapse
No need to use the custom install if you don't want to customize the install beyond the default - you can just flash it.
Is there a better way to portray that in the OP(s)? That is definitely the feeling I wanted to convey, and not surprisingly it seems I fell a bit short of the mark
dwitherell said:
No need to use the custom install if you don't want to customize the install beyond the default - you can just flash it.
Is there a better way to portray that in the OP(s)? That is definitely the feeling I wanted to convey, and not surprisingly it seems I fell a bit short of the mark
Click to expand...
Click to collapse
Was been a bit cautious that's all, at first it sounded mandatory (myable BC I've been working all night) I installed it with material L theme and boy is it smooth, I might have to return my G3 now. Thank you!
Awesome thank you! Can't wait to download and flash this beast! Wallys themes are sick.
@dwitherell,
Thanks so much for giving us another ROM option for our ATT Note 3. Install went without issue. I had an issue with data, but added an apn from here and now have data. Had an issue with wifi passwords being remembered after a reboot, but applied fix from @Walter.White ...."Change the following line in build.prop:- ro.securestorage.support=true to false" and wifi passwords seems to be sticking after reboot.
I'll let you know if I see anything else. Once again...thanks very much.
sapps said:
@dwitherell,
Thanks so much for giving us another ROM option for our ATT Note 3. Install went without issue. I had an issue with data, but added an apn from here and now have data. Had an issue with wifi passwords being remembered after a reboot, but applied fix from @Walter.White ...."Change the following line in build.prop:- ro.securestorage.support=true to false" and wifi passwords seems to be sticking after reboot.
I'll let you know if I see anything else. Once again...thanks very much.
Click to expand...
Click to collapse
Nice
I'm curious - are you seeing the wifi calling toggle? It almost seems like you didn't get the ATT stuff in the install process - and that should have included ATT apns and an ATT build.prop with that securestorage edit. Let me know
{
"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!
{
"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
63Accent colors
12Icon shapes
22Fonts
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!
OP has been updated!
New "exclusive features" added:
"Disco Dingo the QS" (just a funny name for the option to apply random colors on QS toggles)
Lock Screen Camera Shortcut (enable/disable)
Status bar reduce height (and option to correct left padding on devices with the notch on the left)
Status bar quick QS pulldown (Never, Right pulldown, Left pulldown, Always)
Hope you may enjoy these new features.
Remember, these features needs both "Addon features V10" and "SystemUI V5" modules to be flashed.
Cheers!
OP has been updated!
New "exclusive features" added:
Status bar reduce height options (Default, Small, Medium)
Lock Screen Fluid Custom Clock
Hope you may enjoy these new features.
Remember, these features needs both "Addon features V11" and "SystemUI V6" modules to be flashed.
Cheers!
OP has been updated!
New "exclusive features" added:
Bring back status bar footer drag handle (and it's options | Default; Accent based; Hidden)
Added option to completely remove the nav bar (it gets removed on any navigation mode but stock gestures will continue to work)
Center clock position fix option (it's needed for devices with a left notch using default status bar height)
Added Switch styles
Hope you may enjoy these new features.
Remember, these features needs both "Addon features V12" and "SystemUI V7" modules to be flashed.
Notes:
The "center clock position fix" is somewhat related to the status bar height and "fix left side padding" options. You may encounter a few weird behaviors if you try to enable/disable/change those 3 features several times on Rom Control. I ran into a weird situation when testing all possible combo options....at the end I choose default status bar height and left clock. To my surprise, the clock ended up behind the notch...WTF!? So, if that, by any chance, happens to you, just try to set on/off all to default values, close ROM Control, open it again and choose your desired combo.
The "completely remove navigation bar" option has a warning dialog. I've added a "warning" so that people read it and understand what that option does. Since the text is somewhat long, I've added a timer that only enables the overlay, that removes the nav bar, after 10 secs (so that people have time to read the warning). And so, if you see the warning and just decide to immediately touch OK, you'll notice that the nav bar will only disappear after 10 secs... Having this said, the first a**hole that comes here stating something like "hey man I touch the remove nav bar option and it doesn't disappear...wtf!?...plzzz, halp. I've tried to enable disable several times...it dasn't wark!!!"... will be rewarded with a very nice "F**K *ff!" answer.
Cheers!
Hello!
SystemUI MOD V7 is compatible with April update, I'm using it already and it's working ok.
Tested it on sunfish (Pixel 4a) but I think it's the same for all models.
Thought you'd like to know.
Cheers!
Same here installed April from OTA file. App does crash though changing some settings and UI reboot but the settings get applied anyway.
Wallpapers won't download or apply Pixel 3 April 2021
@Typhus_
Lovatastic said:
Wallpapers won't download or apply Pixel 3 April 2021
@Typhus_
Click to expand...
Click to collapse
Clear Google Play App Data and Cache. Reboot device. Go to play store and check for Pixel apps updates. Update them. Done.
Typhus_ said:
Clear Google Play App Data and Cache. Reboot device. Go to play store and check for Pixel apps updates. Update them. Done.
Click to expand...
Click to collapse
Still not working. Device personalisation shows as pixel 5 when I have the 3 could this be the issue?
Lovatastic said:
Still not working. Device personalisation shows as pixel 5 when I have the 3 could this be the issue?
Click to expand...
Click to collapse
No.
Check if Pixel Live Wallpapers app is updated. It should be.
Typhus_ said:
No.
Check if Pixel Live Wallpapers app is updated. It should be.
Click to expand...
Click to collapse
Thanks version 1.3 showed as up to date in PS but APKMirror has 1.5 that got it working again. Thank you!
Also I'm using fluid navigation and hiding navigation bar so I can customise swipe gestures. I was wondering since you can adjust the width sensitivity of the back gestures would it also be possibly to adjust the height so it doesn't interfere with pull out menus?
I have 3 separate magisk modules for safetynet and google pay, do they all need them all disabled?
Gpay SQLite fix, magisk hide props fix, and kdrag0n universal safety net fix (it looks like this one for sure needs to be disabled as it's already implemented in this mod)
I want to try this mod out a lot it looks fabulous but I'm wary to mess up my working google pay! Anyone have any intel?
NinetoFive said:
I have 3 separate magisk modules for safetynet and google pay, do they all need them all disabled?
Gpay SQLite fix, magisk hide props fix, and kdrag0n universal safety net fix (it looks like this one for sure needs to be disabled as it's already implemented in this mod)
I want to try this mod out a lot it looks fabulous but I'm wary to mess up my working google pay! Anyone have any intel?
Click to expand...
Click to collapse
My guess is that you should try to disable the current modules you currently have installed. Then, install this one and check if you need the other ones. If you do, try to enable one at a time just to make sure they're compatible.
SafetyNet fix is not needed at all since it's already implemented on this MOD. That one you can completely uninstall it.
Cheers!
To confirm for anyone else wondering:
As Typhus stated, the SafetyNet fixes I had were all redundant. I disabled them all and then tried just this mod and it worked fine. Originally I thought it messed up SafetyNet but it turns out the API for the checker built into Magisk wasn't working itself so it had nothing to do with the mod. It's working great on the pixel 3, thanks!
Will it work on Pixel2xl?? I tried it some of the features work and some doesn't? I flashed build.props from pixel5 but no luck...is there anyway I can enjoy all these features on pixel 2 xl?
Daniyal48 said:
Will it work on Pixel2xl?? I tried it some of the features work and some doesn't? I flashed build.props from pixel5 but no luck...is there anyway I can enjoy all these features on pixel 2 xl?
Click to expand...
Click to collapse
Hello!
The "universal mod", that is, the Addon Features V8 module, should work on every AOSP, or close to it, ROM on any Pixel device.
Unfortunately, the Addon Features V12 adds more features that will only work if a separate module, the SystemUI V7, is also installed. But, that module is a modded SystemUI that must be compatible with the phone model you're running. Google stopped updating Pixel 2 XL, so your SystemUI is simply not compatible with it.
BUT on the OP I've shared a link to GitHub where I explain how anyone can try and port this MOD to their own SystemUI. Everything you need is there, you could try and port it yourself.
Cheers!
Typhus_ said:
Hello!
The "universal mod", that is, the Addon Features V8 module, should work on every AOSP, or close to it, ROM on any Pixel device.
Unfortunately, the Addon Features V12 adds more features that will only work if a separate module, the SystemUI V7, is also installed. But, that module is a modded SystemUI that must be compatible with the phone model you're running. Google stopped updating Pixel 2 XL, so your SystemUI is simply not compatible with it.
BUT on the OP I've shared a link to GitHub where I explain how anyone can try and port this MOD to their own SystemUI. Everything you need is there, you could try and port it yourself.
Cheers!
Click to expand...
Click to collapse
Thank you I will give it a try
Hey i have a problem. If i install Android_11_SystemUI_for_Addon_Features_V7.zip my phone boots but the screen just turns on and off. Just the Android_11_Addon_Features_For_Pixel_V12.zip works fine. Does anyone know why this happens? One idea i have is, that i cant find the Device Personalization Services in the playstore so i just disabled it.
Im using a pixel 3 with the latest april update.
Can anyone help me?
Yeah same issue here with pixel 2xl. i think it is the system UI . We have to port it for our own device. He has mentioned the method in the thread
SadaUkyo said:
Hey i have a problem. If i install Android_11_SystemUI_for_Addon_Features_V7.zip my phone boots but the screen just turns on and off. Just the Android_11_Addon_Features_For_Pixel_V12.zip works fine. Does anyone know why this happens? One idea i have is, that i cant find the Device Personalization Services in the playstore so i just disabled it.
Im using a pixel 3 with the latest april update.
Can anyone help me?
Click to expand...
Click to collapse
Yeah same issue here with pixel 2xl. i think it is the system UI . We have to port it for our own device. He has mentioned the method in the thread
{
"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"
}
What is this?
These are two Magisk modules that adds the following cool features to any Pixel 3, 4, 5 and 6 device running Android 12:
Enable/Disable Google Sans font system wide
Adds Icon Styles and Icon Shapes overlays from Android 11
Fonts options
Enable/Disable Combined signal icons
Pixel 6 Wallpapers
Adds 2 button mode navigation (it was removed on Android 11 but I think some users like that navigation mode, so I add it)
Adaptive sound options
Navigation bar options (reduce keyboard bottom space size, completely remove NavBar)
SystemUI Tuner options
Enable Game Overlay for all Pixels by default (although, if something goes wrong while playing games, you can disable this feature)
Enable/disable dual tone battery meter (it only works on icon portrait mode)
Enable/disable showing the number of unread messages on status bar notifications
Reduce Status bar height (and option to correct left padding on devices with the notch on the left)
Option to enable/disable more themed icons on launcher (some apps don't have a themed icon so it won't work for all apps)
Enable/Disable left shortcut on Lock screen
Enable/Disable camera shortcut on Lock screen
------------------//------------------------
Enable/Disable Wifi + Cell QS Tiles instead of single Internet QS Tile *
Battery Styles *
Clock Customization *
Network Traffic Indicators (on Pixel 5, Pixel 6 and Pixel 6 Pro devices they only work on QS Header) *
QS Battery percentage independent options (show estimate time remaining or just percentage) *
Dual tone Light/Dark themes for QuickSettings Panel and Power Menu *
Album art on lock screen options *
Music visualizer options (requires Visualizer fix module) *
QS Quick pulldown with one finger (options are off, drag from the top left and drag from the top right) *
Rom Control app (to setup all these options)
* -> These features are only available if "SystemUI module" is installed.
Downloads:
Addon_Features_for_Pixel_Visualizer_Fix.zip -> Install this module first (if you haven't installed it before). Afterwards, reboot your device and wait for about 1 minute before doing anything else. Really, I'm not joking, install, reboot and just wait. You see, this "Visualizer fix" module is only needed in order to add a missing permission to SystemUI. It only has to be installed once (obviously, if in the future you clean flash the ROM, you'll have to flash it again or you'll be missing that required permission). And, since it's only needed once, this module is deleted from the system after doing what it has to do. So, it's normal that you won't see it as installed after installing everything.
Android_12_Addon_Features_for_Pixel_V8.zip -> "Harmless" module that works on any Pixel device running on STOCK ROM, The features marked with an * above options, on Rom Control app, won't do anything if the SystemUI module, shared next, isn't installed.
Android_12_Pixel_3_SystemUI_for_Addon_Features_V7.zip -> This is "THE" module! This module adds all xml and smali changes into SystemUI and framework-res. 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 and framework-res for modded ones, you could run into problems if some other module tries to do the same or it's simply incompatible with it.
Android_12_Fixes_for_Pixel_3.zip -> This module is an extra and it's only for Pixel 3 devices. It enables the rounded corners on windows, as well as, AOD screen lights on/off animations.
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 Pixel. 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).
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 and/or framework-res between builds. When that happens, I have to recreate the module again to adapt those changes. Rest assured that I'll always test the module with new builds and update as necessary.
The SystemUI module is different on Pixel 6 devices! For those I had to make a new module, since Pixel 6 SystemUI is different from all other Pixels.
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
After grabbing the log, please open the txt file and search for "FATAL". Afterwards post here the lines where the "Fatal error occurred".
I've made these modules for my personal use and just decided to share with all XDA community. Having this in mind, there's no need for donations (although I won't refuse them if you want to buy me a beer). As for requests or whatever, I can only add more stuff when, and if, I have time for it. I'm a really busy man in real life so I can't promise anything nor ETAs.
Requirements:
Unlocked bootloader
Magisk Root | Magisk Manager
Suggestion:
Uninstall all other modules you may have installed before installing SystemUI module zip. 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, I recommend you to flash latest stock build through fastboot using flash_all.bat. In order to retain your data, remove the "-w" flag from the update command on flash-all script.
How to install?
Flash the "SytemUI" Magisk Module
Reboot device
If it booted ok, flash "Addon Features" Magisk Module
Reboot device
Have fun!
Faced a black screen after flashing the "SystemUI MOD"? Then try this:
(This usually happens when an error about "TensorFlow lib" is shown on the logcat, if it's any other error, don't do this. Share the log instead so I may take a look)
Enable 2 button, or 3 button, navigation mode on System Settings
Install "SytemUI" Magisk Module
Reboot device
Have fun!
If you're still having issues or if you want to fix that "TensorFlow lib stupid bug", which is responsible for not being able to use stock gestures navigation, then you'll have to do this:
Uninstall all previous Magisk modules you had installed
Completely uninstall Magisk (using the option on Magisk Manager app)
Reboot device
Flash latest stock ROM build through fastboot using flash_all.bat (remember to remove the -w flag inside the bat file if you want to keep your data)
Root the device again using latest Magisk Canary (stable version works for the time being but latest Magisk Canary is more compatible with Android 12)
Flash these two modules, and only these just to make sure no other module is causing conflicts
Reboot device
Hopefully it will work, so enjoy!
Video:
Check all Rom Control (with exclusive features) options HERE.
Note that this video was recorded when I've made this for Android 11. Some features may not be present (yet) for Android 12. The video is here only for those, who have never tried this on Android 11, may understand what to expect.
How's these "exclusive features" even possible?
All features that you see on Pixel Devices "SystemUI module" were reverse engineered from Proton AOSP and Evolution X ROM source code. The source code is available on the links 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 PAOSP and 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_Android12
Want to port the "exclusive features" to your Pixel device running on other ROM? Here's how:
https://github.com/ElTifo/CustomSettingsForDevs/tree/Pixel4a_Android12/app/src/mods
Credits:
Proton AOSP ROM team, specially @kdrag0n for all his work on Dual tone light/dark themes and other Proton AOSP helpfull commits.
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
@Freak07 for Adaptive Audio
@trzpro for More themed icons on launcher mod
Cheers and enjoy!
You little beauty! Thankyou, downloading now
Woohoo! Thanks a lot. My status bar is FINALLY back to normal after A12 messed it up!
Hello!
Both modules have been updated to Version 5 and the links are now available on the OP.
What changed?
Added Android 11 Icon Styles and Icon Shapes overlays
Added ProtonAOSP Fonts overlays
Option to enable/disable Wifi and Data separate Tiles, instead of Internet Tile
Reduced screenshot overlay PIP time after taking a screenshot
Added more themed icons
Updated Rom Control app
Hope you may enjoy this.
Heads up:
The icons and fonts overlays gets disabled after a reboot or a SystemUI restart. Don't know why. So, after a reboot you'll have to change those options again.
The icon shapes, sometimes, require us to disable theme icons and enable it again after choosing our desired shape. Don't know why as well...
Yeah, this kind'a sucks... but, if I find a solution, I'll fix it on next version.
Cheers!
Hello!
Both modules have been updated to Version 6 and the links are now available on the OP.
What changed?
Added Album art on lock screen options
Added Music visualizer options (requires Addon_Features_for_Pixel_Visualizer_Fix.zip)
Force Google Sans system-wide is now optional
Enable/disable combined signal icons on status bar
Added center clock fix to the right (for Pixel 3a models)
Updated Rom Control app
Heads up:
I still wasn't able to understand what causes the fonts, icons and icon shapes overlays get reset upon reboot or SystemUI restart
Install Addon_Features_for_Pixel_Visualizer_Fix.zip first. Afterwards, reboot and wait for about 1 minute before doing anything else. Really, I'm not joking, install, reboot and just wait. Afterwards you may install the other 2 modules and reboot
The visualizer fix is deleted from the system after doing what it has to do. So it's normal that you won't see it as installed after finishing all this. That fix is only there to add a missing permission to SystemUI. It only has to be installed once (obviously if on the future you clean flash the ROM, you'll have to do it again)
Anyway, hope you may enjoy this.
Cheers!
Hay, I installed these modules, it reminded me about Pixel Experience Plus, but now I dont know how to disable 'force Google Sans fonts system wide' and font like this (absolutely I dont like this", so you can show me how to turn it off?
Twin.Twiggs said:
View attachment 5470343
Hay, I installed these modules, it reminded me about Pixel Experience Plus, but now I dont know how to disable 'force Google Sans fonts system wide' and font like this (absolutely I dont like this", so you can show me how to turn it off?
Click to expand...
Click to collapse
I've included an option for that on Addon features latest version. It's on "Themes" section.
Quite obvious, if you ask me, but...ok...
Looks like there's a conflict between this and the Font Manager module. System freezes repeatedly and have to reboot if both are activated.
Tried again with v6, thinking it might be the global font option that was causing it, but even with that option off still getting freezing.
Any ideas how to make them both work together? Just want my iOS emojis and right-side clock at the same time. Lol.
jimjitsuesq said:
Looks like there's a conflict between this and the Font Manager module. System freezes repeatedly and have to reboot if both are activated.
Tried again with v6, thinking it might be the global font option that was causing it, but even with that option off still getting freezing.
Any ideas how to make them both work together? Just want my iOS emojis and right-side clock at the same time. Lol.
Click to expand...
Click to collapse
If you're not enabling Google Sans system wide, then I really don't know what could cause any conflict regarding fonts. Maybe that other module needs some update, don't know.
Try to grab a logcat when the freeze happens.
And, by the way, the freeze doesn't happen if you just use that other module?
Typhus_ said:
If you're not enabling Google Sans system wide, then I really don't know what could cause any conflict regarding fonts. Maybe that other module needs some update, don't know.
Try to grab a logcat when the freeze happens.
And, by the way, the freeze doesn't happen if you just use that other module?
Click to expand...
Click to collapse
I'll try to get a logcat. No, the freeze only happens when both are enabled, not when either is enabled separately.
Hello!
Both modules have been updated to Version 7 and the links are now available on the OP.
What changed?
Fix fonts, icons and icon shapes overlays get reset upon reboot or SystemUI restart
Light theme QS Header is now optional
Added 2 more battery styles (Big circle and Big dotted circle)
Added option to enable/disable dual tone battery meter (it only works on icon portrait mode)
Added option to enable/disable showing the number of unread messages on status bar notifications
Added option for QS Quick pulldown with one finger (options are off, drag from the top left and drag from the top right)
Enable Game Overlay for all Pixels by default (although, if something goes wrong while playing games, you can disable this feature)
Added 8 new fonts overlays
Fix lag on camera if navbar his completely hidden
Added option to enable/disable left shortcut on Lock screen
Added option to enable/disable camera shortcut on Lock screen
Force Google Sans system-wide is still optional but it's enabled by default (I like it that way, so yeah...bummer. You'll still be able to disable it, so no problem whatsoever)
Removed battery percentage option on system settings (since we can now change it on ROM Control app, it didn't make much sense to leave it there. Besides, it wasn't doing anything...)
Updated Rom Control app
Hope you may enjoy this.
Cheers!
Hello!
Addon features module has been updated to Version 8 and the link is now available on the OP.
What changed?
Added a fix to get rid of the TensorFlow lib stupid bug once and for all
Hope you may enjoy this.
Cheers!
Sorry for disturbing but I found the thread in Pixel 6 Forum which provides much newer versions of this and I installed it. However my Pixel 3 **booted twice** which means it doesn’t support the full version of the latest module according to the thread and I noticed that the github page says “from 3a to 6” but I don’t know if Pixel 3 is included. The question is I have no idea whether it was because Pixel 3 is not supported by the latest version that my installation fell back to lite version, or some other factors led to that. I wonder if Pixel 3 is supported, and if not, what the last version that supports Pixel 3 is as V8 mentioned in this post doesn’t work property on my device (The centralized time is not at the exact center of the status bar but a little shifted to the left).
Masellum said:
Sorry for disturbing but I found the thread in Pixel 6 Forum which provides much newer versions of this and I installed it. However my Pixel 3 **booted twice** which means it doesn’t support the full version of the latest module according to the thread and I noticed that the github page says “from 3a to 6” but I don’t know if Pixel 3 is included. The question is I have no idea whether it was because Pixel 3 is not supported by the latest version that my installation fell back to lite version, or some other factors led to that. I wonder if Pixel 3 is supported, and if not, what the last version that supports Pixel 3 is as V8 mentioned in this post doesn’t work property on my device (The centralized time is not at the exact center of the status bar but a little shifted to the left).
Click to expand...
Click to collapse
Same here!
V20 on github only gives the Lite version working on the Pixel 3
Any chance to get the exclusive features supported for the newest version?
Thanks
Carmine8 said:
Same here!
V20 on github only gives the Lite version working on the Pixel 3
Any chance to get the exclusive features supported for the newest version?
Thanks
Click to expand...
Click to collapse
Hello.
Please read this post. The answer to your question is there.
Cheers!
From this day on, Addon Features Module will no longer receive any updates. It's the EOL for it.
BUT....
I'm pretty sure you all noticed that @siavash79 has been working with me for some time now and we've teamed up to come up with a module that will try to, not only have everything Addon Features had, but MORE.
HOW!?
By creating a new project, called "AOSP Mods".
That project will be a mix between a Magisk module and Xposed module (using Lsposed zygisk version).
For now, the 2 projects are still separated (Addon Features and AOSP Mods) but the final objective is to merge them into a single module.
So, you may still use Addon Features V21 LITE version module zip but, in order to have some of the "exclusive features", that were present on FULL version, working, you'll need to flash AOSP Mods as well.
So, let's all just move on to the new AOSP Mods thread and start to have fun together, shall we?
See you guys "on the other side".
Cheers!