Related
Mods please close this thread, thank you . For everyone interested, I've opened another thread which once again involves the framework to be replaced, check it out here: http://forum.xda-developers.com/showthread.php?t=689830
Hi all,
I was not able to finish this before CM5.0.7 got released, but have since completed it. What this does is basically change the colour dialogs from a list of colours to a proper colour wheel, with a textbox for hex values, as well as a transparency slider.
Special Thanks:
ruqqq aka arctu . I basically took the colour picker from his MMS mod. I know it's based off Google's, but his code provided me a base and an example to work off.
http://www.anddev.org/announce_color_picker_dialog-t10771.html for the slider animations and text.
Screenshot:
Instructions:
You can either slide the wheel, then adjust the transparency, or use the textbox directly. The textbox accepts the following input:
#AARRGGBB
#RRGGBB
AARRGGBB
RRGGBB
Meaning, you can input your colours with or without the # in front, and with or without the alpha channels.
Changelog:
250510 #3
- Added option to reset all UI tweaks to defaults. As usual, reboot to see changes.
250510 #2:
- Ok this is unexpected . No real change, just added a dependency to clock colour, so if "show clock" is unticked, "clock colour" will be disabled.
250510:
- Changed list of colours to a proper colour picker
Explanation of Each Option:
http://wiki.cyanogenmod.com/index.php/User:Wysie
Download:
APK: http://dl.dropbox.com/u/263378/androidstuff/SpareParts.apk
Update.zip: http://dl.dropbox.com/u/263378/androidstuff/2505103_SpareParts_Color_Picker.zip
Install Instructions for APK:
Simply push to /system/app/
Code:
adb remount
adb pull /system/app/SpareParts.apk ./SpareParts.bak
adb push SpareParts.apk /system/app/
Install Instructions for Update.zip
Flash through recovery.
Source:
http://github.com/Wysie/development_apps_spareparts
You can be sure, I'm gonna push it - thank you Wysie !!
works perfectly. Damn, theming is so bloody easy now!!
Thanks for sharing have you test it on froyo version ??
Adds the "My" to MyTouch, thank you
Maybe cyano can push this in, as he will release a new 507 probably tonight (cause of gallery bug)
imfloflo said:
Thanks for sharing have you test it on froyo version ??
Click to expand...
Click to collapse
It won't work unfortunately. This SpareParts requires the framework mods I made (which are merged into CM5.0.7) for it to work .
I can't express enough how sweet this is.. I no longer have to worry about borking my services.jar when changing colors.
Made a very very small update .
Added option to reset all to defaults.
will this slip into CM's .1 release?
bewA: I believe so .
Link to explain what each option means: http://wiki.cyanogenmod.com/index.php/User:Wysie
Thanx Wysie, it was just a little request and you made a BIG thing out of it!!!!
You did a hell of a job on this Wysie! Good work!
jrummy16 said:
You did a hell of a job on this Wysie! Good work!
Click to expand...
Click to collapse
Ditto and thank you very much! Also to those others that were involved!!!!
To what framework file are these color settings saved to? I'm trying to do a custom theme for CM7 but can't figure out where these are saved to!
MicroMod777: They're saved to the system prefs, along with compcache (enabled/disabled) and so on. Get in touch with @jeagoss on Twitter, he's making a script that helps themers with exactly what you are trying to do .
To everyone else, it's been merged into 5.0.7.1 .
I gotta say, this is great for people who maintain their own theme for personal use. I was very pleasantly surprised when I flashed the .1 release and my custom colors were still there!!
daveid: This thread is useless again since it's been merged!
Wyse can U give me the string for translate in Italian so I can give to you and have sparepart all in Italian language?
This is the only part of cyanogen in English
Thanks
[Q&A][INFO] BlackBox™ [ROM][ML2][4.3][16 Jan] BlackBox™ 2.1 | [Samsung/AOSP Hybrid]
[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE][SIZE=+2]Specific to[/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"
}
This is a project to blur the lines between Samsung firmwares and AOSP. I have kept the best Samsung features (Camera, FM Radio), mixed it with AOSP features, and maintained stability
Click link here>> ●BlackBox ™ by DSA <<Click link here
Please feel free to share issues, questions and offer help
It is always best to thank a development thread OP, in lieu of simply posting "Thank you".
_______________________________________________
Please keep discussion focused, on the topic described in the OP
_______________________________________________-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
THE OLD OP
Hello again !!!
-=-=-=-
This new opened thread is fully dedicated to all questions and answers of ALL BlackBox`s all versions users.
I`ll try to do my best to maintain the required support for everyone in view of having all benefits from this amazing ROM series .
-=-=-=-=-
BlackBox
FAQ
Remove droid logo from aosp lockscreen circle: not possible, part of the rom
Add battery icon style: rom control or search forums but first backup system UI before flash, no support
Audio engine compatible: yes but make sure megabass wasn't selected during flash
Some of selected options during flash not applied: reflash without wipe
Full wipe or not?: advise always fullwipe to avoid issues
Charging issues after flash: reflash kernel if fullwipe previously made.
Jkay compatible: No !!!
Non inverted gapps: No !!! Black only !!!
Non signed gapps error from market, wipe cache and dalvik, reboot
Touchwizz launcher or samsung apps?: No this is an AOSP Rom (or search forum for flashable zip but no support, or extract from stock rom)
v 1.4
PHP:
BlackBox 1.4
Base Firmware: I9300XXEMH1 (4.1.2)
Region: Europe
Country: Netherlands
Carrier: Unbranded
Samsung Build Date: 1 August 2013
Modem: Removed
CSC: Removed
Change List: 1338371
Changes:
Rom is 434mb
Updated AOSP keyboard to latest version from CM10.2
Removed shutdown animation
Updated Xposed Framework - 2.2 - Can now browse modules through app
Updated App Settings (Per App DPI) - 1.5
Swapped Trebuchet for Nova Launcher
Fixed mms messages
Added AOSP themed pop up browser
Updated Play Music - v5.2.1204L.814012 (Blacked)
Updated Youtube - 5.0.21 - No HD mods, just blacked
Updated SuperSU - 1.55 (Issues updating to latest version)
Swapped CM File Manager for ES File Explorer (Blacked)
Removed Active Notifications from Rom Control
Removed call recording mods from Rom Control (Due to new AOSP phone.apk)
AOSP'ized a lot of Rom Control icons
Added AOSP phone.apk;
Full AOSP contacts/Dialer/In Call Screen
Fixed call logs
Fixed adding events to contacts
New Feature:
New 4.2.2 style statusbar/notifications
2 Different swipeable screens - one for notifications, one for toggles & built in volume panel
Screen switcher toggle included in statusbar, can also swipe left/right when pulling drag bar handle down
NOTE: Brightness slider is now non-removeable - Rom control options removed - background can still be made transparent using Notification background colour mod
Aroma:
Updated Aroma Installer - 2.70RC2 - Removed languages
Stock Kernel/Dont Flash - Updated Performance Control
Updated Boeffla Kernel - 3.1 Stable
Updated Philz Recovery - 5.15.0
READ THIS:
This will wipe your messages and contacts database regardless of whether you wipe or not - This is to make sure everything works ok with the new phone.apk
Thanks:
akash akya
GoldieKing
Kryten2k35
Team Blackout
ricky310711
NOTE:
THIS ROM DOESN'T CONTAIN ANY MODEMS, AFTER FLASHING THIS ROM YOU SHOULD EITHER FLASH THE MG4 MODEM OR RESTORE A PREVIOUS EFS FOLDER BACKUP.
ROOTSU HAS A THREAD TO HELP YOU IF YOU HAVE SIGNAL/IMEI/EFS FOLDER ISSUES HERE
v 1.3.1
NOTE:
THIS ROM DOESN'T CONTAIN ANY MODEMS, AFTER FLASHING THIS ROM YOU SHOULD EITHER FLASH THE MG4 MODEM OR RESTORE A PREVIOUS EFS FOLDER BACKUP.
ROOTSU HAS A THREAD TO HELP YOU IF YOU HAVE SIGNAL/IMEI/EFS FOLDER ISSUES HERE
list of modems HERE
Known Issues
v1.3
currently none ...
v 1.2
When using pin Lockscreen, the Lockscreen clock is obscured unless you hide the StatusBar (Being investigated)
In latest version, pattern Lockscreen option isn't working (Fixed in next version)
Latest version: New calender isnt syncing (Fixed in next version)
Latest version: I forgot to update call recording, currently not working (Fixed in next version)
-=-=-=-=-
●BlackBox ™ >>> development thread
-=-=-=-=-
darksideagent.com/downloads/
Thank you !!!
-=-=-
i`ll edit the OP as soon as i`ll get more time !
the second post will contain a list with known issues or/and possible fixes.
just feel free to contribute !!!
Enjoy !
With this ROM you will get
HTML:
AOSP/Samsung hybrid Rom
AOSP Apps & features
Full customized installation with Aroma
Fully customizable 23 statusbar toggles and JKay style additional customizable 2nd row
Fully customizable statusbar clock
4.2 apps from the Nexus 4
Blacked theme
Rom Control (Customized CodecROM Settings)
OTA for Rom updates
More free ram
Hacked/Themed Multiwindow for all apps
Removed bloat
Multi language
Optional GNex icons
Optional fully customizable Call Recording
Optional No SMS in logs
Optional Bass Boost
A choice of 11 custom bootanimations
Modems, Kernels, Music Players, Recoveries, Keyboards, Galleries, Cameras, and many framework mods
Multiple 'under the hood' system tweaks to improve;
Battery
Speed
Performance
3g Signal
Wifi
Media tweaks
Better internet speeds
Better streaming quality
as well as many other mods n tweaks
The Rom is now at a stage where its nearly a Release Candidate
Video Reviews of CodecROM by
& Devicecustomizer
(Hidden to reduce post size):
[/CENTER]
[/FONT]
Videos Of How To Flash By Xanthrax/srivas95 & Devicecustomizer(Hidden to reduce post size):
This is a CWM flashable ROM, not to be used through Odin
Backup apps etc via Titanium Backup
Move my .zip file to your SD Card (Internal Storage)
Reboot into CWM
YOU MUST PERFORM ‘wipe Data/Factory Reset’
Choose Install .zip from SD Card / Choose .zip from SD Card / XXEMA2CodecROM105BlackEdition.zip
Select yes from the options
Choose your options in AROMA Installer, wait until install finishes and reboot
If you refuse to read the thread and you ask a question that has been covered, i will ignore your post
If you find a bug, i want more than 'Hlap, mai fone broked'
You are flashing this at your own risk - I will not be held responsible for anything that goes wrong
ETA requests will be ignored
Requests for new mods will be read, not necessarily actioned
Rom Control only works in English, other languages will fc (Translations are being looked at)
If you are experiencing lag in the gallery, wait for the phone to finish loading/caching all the images
To repeat, i will not add in any Touchwiz features that aren't already in the ROM
Do not ask for ETA's or early changelogs...its rude
There will never be a non inverted option for this ROM
-=-=-=-
BlackBox 2.1
Model: GT-I9300
Country: Switzerland
Version: Android 4.3
Changelist: 2303192
Build date: Fri, 13 Dec 2013 13:04:46 +0000
Product Code: AUT
PDA: I9300XXUGML2
CSC: Removed
MODEM: Removed
Changes:
Rom is 481mb
XXUGML2 Base
Updated & improved flashing procedure code
Made efforts to improve overall speed & smoothness some more
Improved some code
Fixed Pie Control
Added sysro/sysrw
Updated Google Services framework
Updated GoogleTTS
Fixed quick search fc
Fixed choppy/laggy video recording playback
Updated Keyboard
Updated Gmail
Updated Calendar
Small graphical fixes
Fixed reject call with text
Fixed statusbar notifications fc
Updated About Phone section (Rom details)
NOTE: Ongoing items in statusbar has a weird background icon – being investigated
DO NOT POST ABOUT THIS
-=-=-=-
BlackBox 2.0.1
Changes:
Rom is 459mb
Ported my S4 BlackBox G.E SystemUI (Full AOSP with toggle control)
Enabled native App Ops (Settings-Security)
Fixed adding event in contacts
Fixed call logs
Themed more AOSP/KitKat
Added any colour/transparency statusbar
Changed keyboard for stock CM (Swiping not working but doesnt fc)
Updated Boeffla Kernel (Aroma) – 5.1 beta9
Updated Philz recovery (Aroma) – 6.07.9
Thanks:
Kryten2k35 (Call logs)
Crussader (Theme)
Kevdliu (Toggle control)
BlackBox 2.0
Initial Release
FAQ
Why dont i have any power menu toggles? - Disabled by default, toggle in Rom Control
Why cant i wake the phone with the home button? - Disabled by default, toggle in Rom Control
Known Issues
Call logs don't keep unknown numbers
Duplicate search results in contacts
Swiping on keyboard causes fc
Probably more, but people don't tell me anything useful or provide logs
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
OLD STUFFS
This is CodecRom Q&A Thread
All questions are welcome but below are the Codec Rules:
*)First check if your question has not been answered in the below FAQ
*)Second use the "Search Thread" feature in order to check if your question has not been answered yet, use basic key words it is working pretty well.
If after this you don't find an answer, please post your question and you'll sure get an answer from CodecTeam members.
At the contrary, and this is an important part of the rule, if you post an already answered question, don't expect any answer of any kind, from CodecRomTeam.
We'll try to update the faq with your new questions as frequently as we can.
Enjoy"
THE MOST FREQUENT QUESTIONS please read below before posting
-=-=-
CodecRom
A small video about how to copy files into system/app
AccuWeather files, extracted from stock rom
Add battery icon style: rom control or search forums but first backup system UI before flash, no support
Audio engine compatible: yes but make sure megabass wasn't selected during flash
Charging issues after flash: reflash kernel if fullwipe previously made.
Centered clock with date: go to settings, date and hour
Full wipe or not?: advise always fullwipe to avoid issues
Jkay compatible: No !!!
Launchers > Apex, Nova , Holo are fully customisable > Nexus 4 , Trebuchet are partially customisable
Non inverted gapps: No !!! Black only !!!
No weather on JB lockscreen - link to the 3 system
Non signed gapps error from market, wipe cache and dalvik, reboot
Remove droid logo from aosp lockscreen circle: not possible, part of the rom
Remove lock icon from status bar: not possible unless you will mod tw_status_bar.xml in res/layout
Some of selected options during flash not applied: reflash without wipe
Touchwizz launcher or samsung apps?: No this is an AOSP Rom (or search forum for flashable zip but no support, or extract from stock rom)
Talk video not working: link to non inverted apk
Yahoo news in this post
White line in the status bar: new battery bar - in rom control
ROM Control:
As people seem incapable of figuring this out i will explain;
STweaks will only be accessible if you install Siyah/Perseus Kernel
Boeffla Tweaks will only be accessible if you install Boeffla Kernel
Performance Control will only be accessible if you install Yank555/Stock/SpeedMod/GalaXsih Kernel
All of these options will always be visible in Rom Control, no matter which option you choose
ANY OPTION THAT YOU DIDN'T CHOOSE WILL FC
-=-=-
KodecRom AOKP
what is PIE ? and how to ...
-=-=-
thanks to jejecule who helped me out to collect them
Reserved
First!
Anyways just now saw DSA website.. that news about milestone ROM is not there
Sent from my Galaxy S III running CodecROM™ 9.1
anuragvivek93 said:
First!
Anyways just now saw DSA website.. that news about milestone ROM is not there
Sent from my Galaxy S III running CodecROM™ 9.1
Click to expand...
Click to collapse
Hi mate ! Welcome here ! AOKP is still I progress and there is a lot of work to do . And you know well that DSA want it near perfection !
I'm eager to get it as well . :thumbup:
Sent from my GT-I9300 using Tapatalk 2
What do you think to having a section in the first post that details the known bug's and workarounds. Not that theres many.
Would maybe keep repetitive questions to a minimum
_neutron_ said:
What do you think to having a section in the first post that details the known bug's and workarounds. Not that theres many.
Would maybe keep repetitive questions to a minimum
Click to expand...
Click to collapse
Yep ! That's why I left the second post in reserve.
I'll make a selection of known bugs and fixes .
Sent from my GT-I9300 using Tapatalk 2
Anurag mate ! What about the flash player now ?
Sent from my GT-I9300 using Tapatalk 2
So far all the app devs confirmed their rich notifications do work on 4.1.2 so it's definitely a ROM bug. Can't expand with one finger... or 2. Only gmail rich notifications are working.
Development thread seems to be without developer so xanthrax drăguță mea, could you pass this to DSA? :beer:
Sent from my GT-I9300 using Tapatalk 2
OK mate , will see what can be done . I'm sure that DSA will see your post himself
And I am just dragut , not draguta ... he's calling me darling , in my language ... believing that I'm a girl ...
But I'm still not 100% sure that I understood your problem.
I noticed that the default application doesn't stick but for tapatalk only . I installed three different SMS apps and they stick as I want , the browser as well , popup is default and you can tell us about the others apps.
Thanx for posting
Sent from my GT-I9300 using Tapatalk 2
xanthrax said:
OK mate , will see what can be done . I'm sure that DSA will see your post himself
And I am just dragut , not draguta ... he's calling me darling , in my language ... believing that I'm a girl ...
But I'm still not 100% sure that I understood your problem.
I noticed that the default application doesn't stick but for tapatalk only . I installed three different SMS apps and they stick as I want , the browser as well , popup is default and you can tell us about the others apps.
Thanx for posting
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Sorry frate, my bad
I don't care about Tapatalk not sticking, not a deal breaker but rich notifications are a big problem.
If you have running foreground apps or apps with persistent icon you will notice that they appear in your drop down menu. With 4.1.1 they implemented "expansion" of those notifications, if the app supports it. In 4.1.1 it was done with a 2 finger swipe gesture, swiping the notification downwards was expanding it. Gmail app is an example.
With 4.1.2 they changed that behavior to single finger gesture, both for expansion and collapsing. This doesn't work on Codec 9.1 Also it's not working with 2 fingers. So basically I can't expand my notifications. This kind of a deal breaker since I use Lux with its rich notifications to adjust the screen brightness, dropping below normal 0 level. I checked stocks by expanding notification, so on and so forth.
I will take a screen shot from my tab, which runs 4.1.1 so you will have a clear idea.
Sent from my GT-P7510 using Tapatalk 2
I am using ●CodecROM™ 9.1 S.E● BETA | Black Edition
I am using Siyah kernel.
On a previous rom there was an option to change the dpi settings - I like it on 241.
There was no option in this rom.
So I pulled the build.prop file for /system and changed the SECOND of the 2 density settings to 241, I pushed the file back and rebooted. My phone just couldn't get bast the boot animation. I could only go to recovery, so I did, wiped and flashed again.
I then tried to change the dpi using the toolkit (from XDA), it said it was successful and asked to reboot - I did. Same problem again, can't get passed the bootanimation. Went to recovery, wiped and flashed.
Any idea how I can change the dpi?
subzer0wbb said:
I am using ●CodecROM™ 9.1 S.E● BETA | Black Edition
I am using Siyah kernel.
On a previous rom there was an option to change the dpi settings - I like it on 241.
There was no option in this rom.
So I pulled the build.prop file for /system and changed the SECOND of the 2 density settings to 241, I pushed the file back and rebooted. My phone just couldn't get bast the boot animation. I could only go to recovery, so I did, wiped and flashed again.
I then tried to change the dpi using the toolkit (from XDA), it said it was successful and asked to reboot - I did. Same problem again, can't get passed the bootanimation. Went to recovery, wiped and flashed.
Any idea how I can change the dpi?
Click to expand...
Click to collapse
Did you have a look to the permissions of the built.prop?rw-r--r--
I did it with the Codec 8.6...i just opened the built prop with text editor,changed the density,safed the changes and reboot.
Thats how i did it.Maybe this is a way to to it for you too
subzer0wbb said:
On a previous rom there was an option to change the dpi settings - I like it on 241.
Any idea how I can change the dpi?
Click to expand...
Click to collapse
hi mate !
down below there are some pics showing you that DPI has been changed and how to .
i was using solid explorer to navigate to build.prop and toolbox for editing it.
first make a backup of your original build.prop somwhere .
open solid explorer and navigate to it root/system/build.prop . you must grant full acces to both apps when superSU requires.
open bulid.prop file and from the apps`s list offered to do it , choose build properties which is integrated on rom toolbox app , you don`t need to open rom toolbox (some others might work as well , haven`t tried it though)
then scroll down until you find ro.sf.lcd_density (in my pic has been already changed)
choose your desired default value for it , save and reboot .
that`s it ! the pics will help you
reverting to original 320 DPI , same way , same without problems
-=-=-
pushing another build.prop file onto your system , different than you currently use is not a good ideea
siyah 1.8 here , lulz/deadline/dual core
unfortunately , for my dear "brother" i couldn`t find an answer yet.
i`ve got you 100% percent now ( you should say REACH not RICH )
i was trying to use LUX app , but somehow my play store get nuts and doesn`t want to work ... gapps has stopped , investigating ...
might due to elk4 issue ... 4.1.2 still beta ...
My long press volume to skip song mod has gone since i flashed aosp lockscreen. Anyone got the flashable android policy?
I read that the one from the other thread is not compatible with 4.1.2 so what im looking for here is the one working with 4.1.2. Thanks
gothicdemons said:
My long press volume to skip song mod has gone since i flashed aosp lockscreen. Anyone got the flashable android policy?
I read that the one from the other thread is not compatible with 4.1.2 so what im looking for here is the one working with 4.1.2. Thanks
Click to expand...
Click to collapse
i`m not sure if it works but what about to push the original file into root/system/framework fix permission -rw-r-r- recte 644 , reboot
make a back up first of the one you`ve got
Butterfly11 said:
Did you have a look to the permissions of the built.prop?rw-r--r--
I did it with the Codec 8.6...i just opened the built prop with text editor,changed the density,safed the changes and reboot.
Thats how i did it.Maybe this is a way to to it for you too
Click to expand...
Click to collapse
Thanks for the reply, I used xanthrax's method though. More instructions lol.
xanthrax said:
hi mate !
down below there are some pics showing you that DPI has been changed and how to .
i was using solid explorer to navigate to build.prop and toolbox for editing it.
first make a backup of your orogonal build.prop somwhere .
open solid explorer and navigate to it root/system/build.prop . you must grant full acces to both apps when superSU requires.
open bluid.prop file and from the apps`s list offered to do it , choose build properties which is integrated on rom toolbox app , you don`t need to open rom toolbox (some others might work as well , haven`t tried it though)
then scroll down until you find ro.sf.lcd_density (in my pic has been already changed)
choose your desired default value for it , save and reboot .
that`s it ! the pics will help you
reverting to original 320 DPI , same way , same without problems
-=-=-
pushing another build.prop file onto your system , different than you currently use is not a good ideea
siyah 1.8 here , lulz/deadline/dual core
Click to expand...
Click to collapse
Cheers mate, sorted now.
subzer0wbb said:
Thanks for the reply, I used xanthrax's method though. More instructions lol.
Cheers mate, sorted now.
Click to expand...
Click to collapse
good ! ... i wrote "orogonal " instead original ...
o good rating for the thread might help as well
xanthrax said:
unfortunately , for my dear "brother" i couldn`t find an answer yet.
i`ve got you 100% percent now ( you should say REACH not RICH )
i was trying to use LUX app , but somehow my play store get nuts and doesn`t want to work ... gapps has stopped , investigating ...
might due to elk4 issue ... 4.1.2 still beta ...
Click to expand...
Click to collapse
Actually I'm writing it pretty correct, its called rich notifications.
I'm talking about this part of the code from Android; platform_framework_base/blob/master/core/java/android/app/Notification.java
In this code if you take a look at line 1395 & 1647 Android Code you will see that I'm not mistaken. Its often referred as "multimedia rich notification" as it handles some functions of apps like Lux does, or my IMKB stock app does. Also Android 4.1.2 change log shows that they changed it to 1 finger gesture from 2. AOSP Change Log - Line 256 - 257
Please take it to DSA and see if he has any clue. If he says he didn't mess around with the code than its probably a Samsung version bug for which I will file a report. But before doing that I would like to have DSA's opinion. Don't wanna report a bug which only happens to me (?)
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
ⓐⓝⓓⓡⓞⓒⓛⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ
[APP][ENGINE][2.3.6+][Xposed] Resflux - A powerful and very easy to use per-application theming module.
Resflux
--------------------------------------------------------------------------------------------------
Do you want to THEME your phone easily, without learning how to do it?
Then you are in the right place!!!
Resflux is very straight-forward. It's very easy to use. You don't need to learn anything just to get started. All you need is your common sense. Once you launch the application, you will see very big buttons with one-word description of what that button will do.
And I forgot to tell you that Resflux supports Gingerbread 2.3.6 and up! yeah you heard it right!
Just use the ported version of xposed installer for gingerbread users...
What else can I do with Resflux?
Tons! All you need is the idea!
- Theming an app or all of your apps.
- Replacing icon and name of your apps.
- Translating app from one language to another
- Overriding default settings inside frameworl-res.apk, settingsprovider.apk and systemui.apk
- and many more posibilities!
Laboratory
The laboratory is where most things will happen. It is where you start theming resources of a specific package. You can theme as many as packages if you want.
After you have selected the target package, Resflux will redirect you to the Experiment area where you can see five buttons namely "Drawable", "String", "Color", "Boolean" and "Integer" though you can only see their icons.
When you click a tab, the list will be populated with the corresponding resources and their current values are even shown so you can tell if it is what you are looking for and trying to replace.
Drawable Tab
{
"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"
}
In the Drawable tab, previews of every drawables are shown and by clicking the selected drawable, you can replace it with a new one.
This is replacement drawable chooser dialog
String Tab
In the String tab, you can take a look at the list of all string resources in an apk. The current value is shown in each string resource and you can replace the value with a new one if you want by clicking it.
Color Tab
In the color tab, all the color resources are listed and the preview of each color is also shown. You can replace it with a new color using the HoloColorPicker dialog.
Boolean Tab
In the boolean tab, you can see all the boolean resources of an apk. Boolean is type where its value is only true or false. You can also change it anytime just like the other resources.
Integer Tab
The integer tab is new in Resflux, since the old Resxploit only supported Drawable, String, Color and Boolean.
Export
If you plan to distribute your work or do a back-up or share it to your friend, then you can export it anytime. You can select which packages you want to export and which are not to be included.
From there, you can also completely, remove all modifications made to a specific package by long-pressing the target package.
Import
If you have exported a mod or got it somewhere and you want to upload it into your Resflux, then all you need to do is to put the zip file inside /sdcard/Resflux. By putting it inside /sdcard/Resflux, Resflux will quickly find it, but you can still leave it in other directories as Resflux will also search the other directories inside your sdcard.
Download Link:
http://repo.xposed.info/module/com.iwisdomsky.resflux
Please leave FEEDBACKS or SUGGESTIONS
And don't forget to hit Thanks if you find it useful!
Change logs:
Code:
1.6.1
- Replaced AAPT with ResourceFileParser library
(This will fix resflux compatibility issue with Kitkat and Lollipop. Marshmallow is yet to be tested. This change also causes resflux mapping of resources to becoming 2-10x faster than before)
[B]REMOVE:[/B]
[COLOR="Red"]1.7
- support for kitkat and above.
- faster mapping of resources (the mapping of resources will be done in the cloud)
- requires internet connection.
- 3x lesser apk file size.[/COLOR]
1.6
- Disabled xposed installed check on app start.
1.5
- UI updates.
1.4
- fix for colors not working issues.
- fix for double "#" on color resource's values.
- minor ui updates.
1.3
- The scroll position will remain and will not jump to the top when resetting/restoring a resource's value.
- Resflux Compiler link
1.2
- Fixed the resource name bug where an exclammation mark will appear before the modified resource's name.
- Forced the screen orientation of the Experiment area to stay in Portrait mode to avoid crashes when accidentally changed your phone's orientation.
- Added a possible fix for crashes on Import area.
- Increased the minimum width of dialogs to occupy some extra space on phones with bigger screen.
- Added labels to the tab buttons in the Experiment area.
- Updated the modified resource high-lighting feature for better visibility.
- Fast scroll enabled. Useful when you are trying to find a specific resource in the list quickly.
- Hold press a modified resource to restore its original value back.
- Clear cache action. If an installed app has received an update, it is a good practice clear the package's cache in Resflux so all changes to the resources to the updated app will become visible to Resflux.
- Added ability to supply a specific hex value to the color picker dialog as requested by many.
- Drawable picker dialog has been completely removed and replaced with an image chooser intent which will open the Gallery by default.
- When on drawable tab, you can change the drawable image preview's size by pressing the MENU key of your phone. Take note, this will not actually reflect to the final result but only to the previews.
- Other few minor UI changes.
1.1
- resource caching system for faster consecutive access.
- high-lighting of the modified resources to distinguish changes.
- added large heap attribute to the application element inside the android manifest file.
- empty package mods cleaner for the packages directory of Resflux.
1.0
- Initial release
Disclaimer
Though Resflux can modify any application, it is not guaranteed that it is can successfully modify all applications.
XDA:DevDB Information
Resflux, Xposed for all devices (see above for details)
Contributors
WisdomSky
Xposed Package Name: com.iwisdomsky.resflux
Version Information
Status: Stable
Current Stable Version: 1.5
Current Beta Version: 1.0
Beta Release Date: 2014-06-22
Created 2014-06-22
Last Updated 2014-08-03
How to use:
STEP 1: First, open Resflux then click Laboratory.
STEP 2: Next you need to choose the application you want to modify from the list and then click it.
STEP 3: Once you have clicked an application, Resflux will start mapping it's resources, you need to wait until it is finished before you can start.
STEP 4: If the mapping of resources has finished, you can now start changing any resource from the list. They are actually categorized as Drawable(Images), String(Texts), Color, Boolean(Switch) and Integer(Number)
STEP 5: Once you're done, you need to reboot your phone in order for the changes to take effect.
Sample Scripts
Disables Low Battery Warning notification
http://upfile.mobi/575226
System Font color changer (you need to extract the zip first then choose the zip of your fave color)
http://upfile.mobi/575213
NOTE: To install the scripts, you need to put all of them inside /sdcard/Resflux folder in your sdcard and then open Resflux and select Import and choose the file.
Reboot your phone afterwards to apply changes.
Resflux is proven working on these devices:
Motorola Moto G running Stock KitKat 4.4.2
S4 i9505 LTE running C-RoM 7.1 KitKat 4.4.4
Samsung Galaxy Y S3560 running Hyperion 8 GM Final Gingerbread 2.3.6
Cherry Mobile Flare S running Stock JellyBean 4.1.2
Cloudfone Thrill 430x running Stock JellyBean 4.1.2
Samsung Note Pro 12.2 tablet
HTC M8 running GPE KitKat 4.4.3
Samsung Note 2 running Touchwiz KitKat 4.4.2
Samsung S4 Mini
Xolo A500 running IceCreamSandwich 4.0.4
If Resflux is working on your device, please post your phone brand and model. thanks!
Special Thanks
I would like to thank everyone especially @rayjr13 for keeping the Resflux thread alive and answering all questions of other resflux users. Thank you very much! :good::good::good:
I would also like to thank all who donated! Please send me your names.
Source Code
Link.
Paypal Donations
If you have a very nice heart and want to make my wish come true, please don't hesistate to send your donations to my paypal account: [email protected]
Scripting
(For themers and programmers)
Apart from the Laboratory where users are provided with user-friendly interface, there is an another way to make modifications and that is by using the scripting feature of Resflux.
Soon, I will be focusing on adding more features to it. One is providing support for layouts. Not the whole layout, but to the components inside defined with an id.
When you export packages mod in Resflux, you will be given a zip file. And when you look inside it, you will actually find atleast a Resflux.ini file. And when you look inside the Resflux.ini file, you will see how Resflux turn everything into series of keys, sections, comments and how they are arranged.
The structure of the Resflux.ini complies with of an INI file as defined here:
http://en.m.wikipedia.org/wiki/INI_file
From the INI File wiki page, you can learn about which one is a key, section or comment.
From it, you may start studying how to write your own.
If you are a programmer, you may find it very easy to understand on how it works. And you can see that you are like dealing with objects. For now, we only have drawable, string, color, boolean, integer, layout, resflux and ini.
Rules
Resflux have rules in when it comes to syntax, grouping and arrangement.
RULE 1: The Resflux.ini can contain only keys, sections, comments and blank lines(with space or not) and should follow their corresponding syntax and must occupy a line therefore two keys in a single line is not honored.
For comments:
Code:
# [any text here]
; [any text here]
For sections:
Code:
[package.name.here]
For keys:
Code:
object.property_name = value
object.property_name : value
For blank lines:
A an empty line or composed of whitespaces.
If an invalid syntax is found, resflux will return error status 0
RULE 2: All resflux.* must be grouped together and must be placed before sections and any other keys except comments.
When this rule is violated, Resflux will return Error Status 1 during an attempt of importing it.
Rule 3: ]: All ini.* must be grouped together and must be placed after resflux.* and before sections and any other keys except comments.
When violated, it returns error status 2.
Rule 4: Before starting defining a key, you must have atleast defined a section. A section is composed of a opening square bracket "[", followed by the package name of the target app, and then a closing square bracket "]".
For example:
Code:
[com.my.app]
Rule 5: Each key must follow their respective value's format.
For drawable:
it could be a PNG image relative path like:
Code:
drawable.ic_launcher = icon.png
# or it could be also a color hex code:
drawable.ic_launcher = #ffff0000
For color:
color can have a single possible format for its value.
Code:
color.bg_color = #ff0000
For boolean:
boolean can only have two choices, the value could be either true or false.
Code:
boolean.enable_nothing = true
boolean.enable_nothing = false
For string:
string can have any value.
Code:
string.app_name = anything you want!!!
# enclosing value with quotes is also fine and work with all types of keys
string.app_name = "!want you anything"
OMG! the first themeing engine for gingerbread! many thanks sir! much appreciated it! :good:
i'm gonna try it soon & report back.
Two quick questions:
Will you upload this to the Xposed repo?
Do you plan on making the source available?
Thanks
GermainZ said:
Two quick questions:
Will you upload this to the Xposed repo?
Do you plan on making the source available?
Thanks
Click to expand...
Click to collapse
Thnx for the reminder sir...
I've uploaded it to the Xposed Repo.
I'm also planning to make it open sourced, but I still need to fix some things up. XD
Excelent work.
Enviado desde mi LG-D802 mediante Tapatalk
Has anyone been able to use this with Hangouts at all? It seems to never get past the "Mapping Resources" screen...
EDIT: Maybe I'm just not waiting long enough. Is it normal for it to take more than 10 minutes to map resources for some apps?
GermainZ said:
Two quick questions:
Will you upload this to the Xposed repo?
Do you plan on making the source available?
Thanks
Click to expand...
Click to collapse
mattdm said:
Has anyone been able to use this with Hangouts at all? It seems to never get past the "Mapping Resources" screen...
EDIT: Maybe I'm just not waiting long enough. Is it normal for it to take more than 10 minutes to map resources for some apps?
Click to expand...
Click to collapse
It really depends... if the /res dir contents of the apk file is really big for example (more than 1k resources) then it should take some considerable time... and it will also depend on ur phone's processing power...
I tested the framework-res.apk with a quad-core phone(not mine) and it took more than 30secs...
and when I tried it with my Samsung Galaxy Y, it took almost a lifetime...
WisdomSky said:
It really depends... if the /res dir contents of the apk file is really big for example (more than 1k resources) then it should take some considerable time... and it will also depend on ur phone's processing power...
I tested the framework-res.apk with a quad-core phone(not mine) and it took more than 30secs...
and when I tried it with my Samsung Galaxy Y, it took almost a lifetime...
Click to expand...
Click to collapse
Yeah, I let it go even longer, and it finally finished. I'm on an S4 Mini, which only has a dual-core Snapdragon 400.
Now my other problem is that when I look in the drawables of Dialer or Camera, there doesn't seem to be any launcher icon in the list. (I'm running an AOSP-based rom, FYI)
mattdm said:
Yeah, I let it go even longer, and it finally finished. I'm on an S4 Mini, which only has a dual-core Snapdragon 400.
Now my other problem is that when I look in the drawables of Dialer or Camera, there doesn't seem to be any launcher icon in the list. (I'm running an AOSP-based rom, FYI)
Click to expand...
Click to collapse
I believe the Camera is part of Gallery.apk and the Dialer is on Phone.apk
WisdomSky said:
I believe the Camera is part of Gallery.apk and the Dialer is on Phone.apk
Click to expand...
Click to collapse
Ohhhh, right. Now I feel dumb. This is an awesome module, I'm gonna have fun with it!
I'd like to offer a UI suggestion if I may though. Some of the lists are very long, and they scroll very slow on my phone. How about enabling a draggable scroll bar on the lists, so we can jump down to the bottom quickly?
mattdm said:
Ohhhh, right. Now I feel dumb. This is an awesome module, I'm gonna have fun with it!
I'd like to offer a UI suggestion if I may though. Some of the lists are very long, and they scroll very slow on my phone. How about enabling a draggable scroll bar on the lists, so we can jump down to the bottom quickly?
Click to expand...
Click to collapse
someone actually granted your wish already...
http://forum.xda-developers.com/xposed/modules/mod-force-fast-scroll-force-listviews-t2785006
WisdomSky said:
someone actually granted your wish already...
http://forum.xda-developers.com/xposed/modules/mod-force-fast-scroll-force-listviews-t2785006
Click to expand...
Click to collapse
Oh, nice! Thanks for pointing that out.
New problem...I changed the Hangouts launcher icon, but it's not actually changing after I restart. Any idea why this might be?
mattdm said:
Oh, nice! Thanks for pointing that out.
New problem...I changed the Hangouts launcher icon, but it's not actually changing after I restart. Any idea why this might be?
Click to expand...
Click to collapse
have you check the resflux in the xposed installer?
are you using samsung's default launcher?
coz I think it caches the packages' icon that's why u can't see the changes...
WisdomSky said:
have you check the resflux in the xposed installer?
are you using samsung's default launcher?
coz I think it caches the packages' icon that's why u can't see the changes...
Click to expand...
Click to collapse
Yes, I have it checked in the Xposed Installer. No, I'm using the Google Now Launcher (running SlimKat). The xSuite module also has trouble changing the Hangouts icon...there must be something different about it than other apps.
Great
Enviado desde mi unknown mediante Tapatalk
mattdm said:
Yes, I have it checked in the Xposed Installer. No, I'm using the Google Now Launcher (running SlimKat). The xSuite module also has trouble changing the Hangouts icon...there must be something different about it than other apps.
Click to expand...
Click to collapse
does resflux works fine with the other apps?
WisdomSky said:
does resflux works fine with the other apps?
Click to expand...
Click to collapse
Actually, I'm not sure. It's taking me quite a long time to test...I haven't been able to find a launcher icon to try to change in Phone, Dialer, Camera, Gallery, or Chrome. And each time I try a new app, it takes 5 - 10 minutes to map the resources. I'll find a small app to try and let you know...
EDIT: Ok, I just tried changing the icon of Buildprop Editor, and it worked perfectly.
Nokia Camera 91.9.1130.40 with Pro Mode and Animojis ENABLED for Nokia 8
Hi guys!
Now I want to share my small modification of Nokia camera. You know that if download not modified version from apkmirror it won't have pro mod and also there will be some not working features. But this mod solve the problem. It's based on source code by @linuxct , so it's not all my work. There are some features of my mod:
- New camera style (just swipe to go to other mod)
- Working slow-mo
- New Dual Sight
- Masks and artificial light
- New AR section in the top menu
-Disabled not working square and live bokeh mod
- Changed package name ("com.nokia.camera_4pda")
- Changed icon (blue->green)
But there're some bugs:
- Not working panorama. It's not working in all versions which I tried to modify
- Not working beauty (no changes if you turn on it)
- Photo distortion when shooting with masks and artificial light (the photo itself is normal, we just need to wait until Google photos it will load, it is also inverted)
- Missing Google lens item
- Sometimes unstable switching to front camera (at lag helps restart the app)
And not good things:
- I don't know how to enable dual camera switching, if someone knows, please help...
Download
https://yadi.sk/d/-l2Ja9METtt0Dg
Contributors
linuxct
mkolpak
Source Code: https://linuxct.space
ROM OS Version: 8.x Oreo
Version Information
Status: Stable
Current Stable Version: 91.9.1130.40 (2.2)
Stable Release Date: 2019-03-21
Created 2019-03-22
Last Updated 2019-03-22
P.s. If you don't have Nokia 8, write me back, working it or not on your phone. I will make a list of supported phones;
If you are a developer - no problem if you will modify my version.
Some screenshots (sorry for Russian)
get me error with front camera
negrroo said:
get me error with front camera
Click to expand...
Click to collapse
Switching front camera or taking photos?.. Yes, sometimes it can freeze on switching, but not always
For me taking photos is working...
taking photos with the front cam.. every time i try this error occurred
mkolpak said:
There are some features of my mod:
- New camera style (just swipe to go to other mod)
- Working slow-mo
- New Dual Sight
- Masks and artificial light
- New AR section in the top menu
-Disabled not working square and live bokeh mod
- Changed package name ("com.nokia.camera_4pda")
- Changed icon (blue->green)
Click to expand...
Click to collapse
Hey, could you please share the code/modifications you made along your mod?
If you need help on how to do it:
After decompiling the apk for the first time, you can set up a new local git repository and add all the current files to it, commit them, then proceed to mod them and commit them. You can then extract your changes into a single nice file with
Code:
git diff HEAD~[FONT="Arial Black"]number of commits[/FONT]..HEAD > my-patch.diff
or with
Code:
git format-patch -[FONT="Arial Black"]number of commits[/FONT] --stdout > my-patch-.patch
Thank you!
linuxct said:
Hey, could you please share the code/modifications you made along your mod?
If you need help on how to do it:
After decompiling the apk for the first time, you can set up a new local git repository and add all the current files to it, commit them, then proceed to mod them and commit them. You can then extract your changes into a single nice file with
Code:
git diff HEAD~[FONT="Arial Black"]number of commits[/FONT]..HEAD > my-patch.diff
or with
Code:
git format-patch -[FONT="Arial Black"]number of commits[/FONT] --stdout > my-patch-.patch
Thank you!
Click to expand...
Click to collapse
Hi!
I will make it, I dont remember all what I changed, but I will post code in these days. :fingers-crossed:
Or u can take my classes39.dex file and see it now.
I took stock apk from apkmirror, replaced some files with new one from your mod (I remember that with stock res folder animoji were not working, but with your files it started working), added my 39.dex file.
Wait 1-2 days, I will do it :angel:
linuxct said:
Hey, could you please share the code/modifications you made along your mod?
Click to expand...
Click to collapse
Sorry that I did not answer for so long, I was on vacation in Armenia, now I'm back.
My edits in the camera were too unpredictable, I can not remember what changed, namely where to turn off the "square". I can only write my actions in productmodelutil, also I remember that to make slow motion work, you need to take the original folder "res" and paste it into your apk.
Forgive me.
P.s. Some photos from Armenia
https://yadi.sk/d/arn2p89fz92IcA