NOTE: No longer being developed. You may want to try tytung's kernels instead.
Click to expand...
Click to collapse
Release 8.6
This is a Kernel I built for my own purposes, and now for others, based on the current EVO kernel (as of whenever I last merged it to my branch) and changes from various sources.
Click to expand...
Click to collapse
Features
Here's what's different to the main tree (See changelog for latest changes in case I forget to update this)
Packaged to be compatible with cedesmith's new style initrd for easy installation on builds using it
CIFS support via a module
mac address patch for wifi/bt by mdebeljuh. See http://forum.xda-developers.com/showthread.php?t=819819
Built without support for ext3 and yaffs
Optimized for speed rather than size
Removed some debug features the average user isn't capable of using anyway (dmesg/logcat still work)
G-sensor workaround by mdebeljuh & jdivic (http://forum.xda-developers.com/showthread.php?p=9208297#post9208297)
Smartass governor added as default
Sysfs interface for optional under/overvolting (see http://forum.xda-developers.com/showthread.php?t=821372) (800-1350mV)
Optional overclocking (via SetCPU or similar) to 1536MHz - USE AT YOUR OWN RISK - it may damage your phone
Optional older battery driver with my patch to support the official HTC extended battery (eb version)
Click to expand...
Click to collapse
Extended battery users extra WARNING!
r8.3+ version with "eb" supports extended batteries using the old driver. r7.7+ temperature reporting for extended batteries is reasonable but NOT accurate. Please see this post for more information.
As of r8.5.3 versions without eb in the name have EXPERIMENTAL (ie it has known bugs) support for extended batteries using a patch to the new driver. More information.
Click to expand...
Click to collapse
Use this at your own risk.
How to Install the kernel
Download the latest from here:
Release r8.6 - https://dl.dropbox.com/u/11373163/Kernels/update.kernel.hastarin.16.12.2010.zip
(Overclock and Undervolt enabled but defaults to normal speeds and voltages)
Release r8.6_eb - https://dl.dropbox.com/u/11373163/Kernels/update.kernel.hastarin.eb.16.12.2010.zip
(as above but with older battery driver with extended battery support)
Undervolt 925mV - https://dl.dropbox.com/u/11373163/Kernels/update.kernel.hastarin.undervolt925mV.15.12.2010.zip
(optional update to undervolt to 925mV, edit as needed)
NOTE: It would be nice to see a few more clicks of that Thanks button folks.
Click to expand...
Click to collapse
DONATIONS
In the past I've suggested donating to your favorite charity instead of me.
But I've decided due to the amount of time this is now taking to accept some donations. I encourage you to still consider a charity first, such as:
http://www.kennedysdisease.org/
So far I've had enough donations to buy an official HTC extended battery for testing purposes. Future donations will probably be spent on beer, coffee or junk food.
Please only donate if you can spare the money. NOTE: I've all but given up getting extended battery support working with the new driver!
I also can't make any guarantees on how long I can keep investing time in the kernel so please consider any donations to be for past work done, not what I might do in the future.
Finally please note I'm building a kernel here and working on the odd bit of code. The bulk of the work is done by others:
Cotulla
Markinus
Letama
Rajko
gauner1986
and no doubt more I've missed
Donations to some of them can be made here:
http://forum.xda-developers.com/showthread.php?t=794953
Click to expand...
Click to collapse
Anyone having issues with this kernel. PLEASE before you post them here, try the following:
Make sure you reboot twice after installing so files get updated (or manually update them then reboot if your build won't auto update)
Actually reading the README.txt provided!
Reading my FAQ
If that doesn't work try a stock EVO kernel
If you still have issues with the stock EVO kernel it's nothing I've done and we may have to wait for the devs to fix it.
If that still doesn't work, then don't use any task killers, and try a clean format of your SD card.
If that still doesn't work you're out of luck.
Click to expand...
Click to collapse
Further Information
I am running Autokiller (despite it's name this is not an automatic task killer) set to Optimum.
I do recommend System Panel Lite to be able to see what processes are using your CPU. I DO NOT recommend using any automatic task killer.
I do recommend using EBL with a 3 sec timeout
Further recommendations can be found in My FAQ
Click to expand...
Click to collapse
A note on the included lights file
memin1857 said:
I talked to gauner1986 (author of the new lights file) and the filename comes from the build.prop file.
It is the ro.board.platform=xxxxxx line in the build.prop file.
xxxxx is also your lights filename. (lights.xxxxx.so)
For example my desire hd build has msm7x30
others I have seen are htcleo, default, qsd8k, ace, bravo.
So you have to rename the lights.htcleo.so that is in hastarins root\system\lib\hw folder to match your builds filename if you want it to work.
Click to expand...
Click to collapse
Old versions
Old camera driver versions for builds that haven't been updated to support the new driver yet:
Release r8.5.3_oldcam - http://www.multiupload.com/KTF4ULINT3
(as per base but with old camera driver)
Release r8.5.3_eb_oldcam - http://www.multiupload.com/X6ZTQ9S2ER
(as above but with older battery driver with extended battery support)
Click to expand...
Click to collapse
Notes:
This should work with any build that can use the EVO kernel.
Data will not work on RMNET based builds.
For anyone else complaining about no data issues make sure you installed the kernel AND modules correctly, and if you're using an older build you may need to update your WiFi firmware and/or your radio.
If it's no data over 3G also check your APN settings.
Click to expand...
Click to collapse
Changelog
Code:
[I]Release r8.6 - 16/12/2010[/I]
- Patched Wifi driver to match main tree (fixes wakeup lag when wifi is on) - Thanks Markinus
- Updated init script to update calibration data (fixes mac address not working) - Thanks OSM
- Enabled extreme overclocking and included speeds from mdeejay's kernel. USE THESE AT YOUR OWN RISK I DO NOT recommend overclocking, you will see little benefit in daily use.
[I]Release r8.5.3 - 09/12/2010[/I]
- EXPERIMENTAL support for extended battery users (NOT for daily use yet)
See http://bit.ly/eDLk0g for more information
- REMOVED initrd.gz & haret.exe (by now all recent builds are updated anyway)
- REMOVED LeTama's new PPP wrapper and aussiebum's suggested ppp options
The latest builds incorporate these changes anyway, and you can get them from
the original thread - http://bit.ly/92IBH6
- Modified package to suit cedesmiths initrd.gz - http://bit.ly/foZ1j3
- Trimmed changelog to only include recent changes
- Yet another smd_tty patch test
[I]Release r8.5.1 - 26/11/2010[/I]
- Included LeTama's patch to fix music skipping when turning the screen on
- Included root folder structure with LeTama's new PPP wrapper and aussiebum's suggested ppp options
****** WARNING ************ WARNING ************ WARNING ************ WARNING ************ WARNING ******
Includes new camera driver you may need a new camera APK and libraries, etc
HTC Desire (Sense) Camera APK - http://www.multiupload.com/0YVTSSQO79 (Thanks mdeejay)
Libraries for Desire/Nexus builds - http://www.multiupload.com/1UDF24Y28R (Thanks michyprima)
****** WARNING ************ WARNING ************ WARNING ************ WARNING ************ WARNING ******
[I]Release r8.5 - 23/11/2010[/I]
- Reverted my toolchain due to a wierd bug causing increased power drain in r8.4 after calls
- Updated smd_tty - This is still experimental but the Beta had 900+ downloads with largely positive feedback
- Changed default governor to smartass
[I]Release r8.4 - 18/11/2010[/I]
- WARNING from 8.3 still applies, see below.
- Updated my toolchain to latest CodeSourcery one
- Commit messages follow for the rest. Thanks to huanyu for finding most of the patches so I could just git cherry-pick them, and to mdeejay for pointing me to huanyu's git tree.
b02a70d Tweak smartass for better performance
260b0ba Added some extra debug info for vdd_level being set on bootup, and fixed another warning in WiFi driver.
e9c3ac0 Optimized ARM RWSEM algorithm
fea4f78 increase IDLE_TIMEOUT within kgsl_yamato_idle (kgsl_yamato.c)
f248e15 msm: kgsl: Remove support for mmap from the kgsl driver.
031a7f7 [ARM] msm: qsd8k: audio
7304611 cpufreq: interactive: Changes to interactive governor
c8cec4c cpufreq: interactive: Fix potential division by zero
c69e698 msm_kgsl: Optimize TLB flushing
9e35440 msm_kgsl: Move kgsl_sharedmem_init to module load
[I]Release r8.3 - 17/11/2010[/I]
- Added smartass governor (use SetCPU if you want to try it)
- Added sysfs interface for undervolting (see http://forum.xda-developers.com/showthread.php?t=821372)
- Added g-sensor workaround by mdebeljuh & jdivic (http://forum.xda-developers.com/showthread.php?p=9208297#post9208297)
- Merged main tree - WARNING: Includes new camera driver with auto white balance bug (but auto focus/zoom works)
[I]Release r8.2 - 11/11/2010[/I]
- Minor update to enable App2SD again (yes Angry Birds should install without unmounting SD)
- Merged main tree as usual (nothing of immediate use in there though)
[I]Release r8.1 - 07/11/2010[/I]
- Merged main tree again (light sensor changes, lowered verbosity of battery driver, etc)
- Included latest liblights to go with the light sensor changes
- Removed NFS support
- Moved CIFS support to a module
- Built with support for tunneling (GRE), may help those with VPN issues
[I]Release r8 - 30/10/2010[/I]
- MAJOR CHANGES = now closer to main tree
- Removed gauner1986s video driver tweaks (they were causing issues merging the main tree)
- DOES NOT support extended batteries due to the new ace based driver (until I can figure out a fix, best bet for eb users is to catch myself and/or Markinus on IRC over the next week or so and we may be able to test further)
- DOES NOT support Overclocking/Undervolting/AXI My testing shows they provide minimal benefit in day to day use, and tend to cause unpredictable errors that will make troubleshooting remaining issues (like data issues) harder. I may release a kernel with these things when everything is running smoothly, but until then I won't even be running one on my phone.
- Perflocked = You can't even underclock with SetCPU. My reasoning is the same as above.
- Merged main tree (updated battery driver from Desire HD kernel, plus a tweak to help prevent oom errors)
- Updated wifi.mac patch by mdebeljuh (http://forum.xda-developers.com/showthread.php?p=8828147)
- Added PPP patch from http://docs.openmoko.org/trac/ticket/2212 (no this does not fix everything with PPP)
I hope to upload to Rapidshare Links
Here u go
http://www.multiupload.com/5QIHT86TAU
[Kernel][21.09.2010][Overclocking][Undervolting][AXI]EVO base + tweaks
Click to expand...
Click to collapse
so... you come from the future?
jrdaz said:
so... you come from the future?
Click to expand...
Click to collapse
Lol in some countries (eg. Australia) it's already tuesday... So it is possible
pixine786 said:
Here u go
http://www.multiupload.com/5QIHT86TAU
Click to expand...
Click to collapse
Thanks I'd seen that but hadn't taken the time to sign up and figure it out.
MAsterokki said:
Lol in some countries (eg. Australia) it's already tuesday... So it is possible
Click to expand...
Click to collapse
Exactly, it's 36 minutes in to Tuesday here.
damn for some time I was just thinking what is he talking about... why u giving so much importance to time stamp... Let XDA server do things for you...
Life is simple... U making things complicated
Can this kernel only be used with a hd2 desire hd rom or also with other current roms?
hastarin said:
Thanks I'd seen that but hadn't taken the time to sign up and figure it out.
Click to expand...
Click to collapse
Hope u are not angry on me... I didnt even asked ur permission... Sorry Bro
TheWizzard2203 said:
Can this kernel only be used with a hd2 desire hd rom or also with other current roms?
Click to expand...
Click to collapse
ONLY HD2 Desire HD Rom (Beta 2)
TheWizzard2203 said:
Can this kernel only be used with a hd2 desire hd rom or also with other current roms?
Click to expand...
Click to collapse
I have no idea sorry. I updated the original post to indicate this.
you test this build?
or
you post this builds for other people try without securety
hastarin said:
I debated releasing an actual built version of this, rather than just the diff, but here goes...
This is a Kernel I built for my own purposes based on the current EVO kernel (as of this commit) and the diffs guaner1986 and darkstone provided in his Desire HD - Beta 2 build.
It has some minor tweaks to the code provided to enable overclocking with AXI enabled. Undervolting support was already there, from gauner1986.diff, along with audio tweaks and others. darkstones shadow writes and writecombine graphic tweaks are also included.
Use at your own risk if you know how. I won't be answering questions on this and I won't be doing another build in a hurry, I'll leave that to the core folks that really know what they're doing.
What's included:
The kernel (as Image) and needed modules
Latest haret.exe
A new initrd.gz (for use with darkstones Desire HD Beta 2 Build) with a logo.rle as created by Letama (hope he doesn't mind)
Diff of the changes made
Before people ask, and so I don't have to answer, no it is not built for extended batteries (unless the base kernel is and I didn't know about it).
NOTE: I have not tested this with other builds. Try it at your own risk. I don't understand half the code in gauner1986's patch.
Download from Megaupload:
http://www.megaupload.com/?d=Y18CPVVX
or
http://www.multiupload.com/5QIHT86TAU - thanks pixine786
Click to expand...
Click to collapse
Is this thread exclusive for Android Elites out there?
Thanks for a very informative thread for the Noobs.
What do we do with this?
Threads shared should offer support to EVERYONE. otherwise its DISCRIMINATORY.
starting a thread just to show off your skills with Android and not offering guide and help just pisses me off really
jigners said:
Is this thread exclusive for Android Elites out there?
Thanks for a very informative thread for the Noobs.
What do we do with this?
Threads shared should offer support to EVERYONE. otherwise its DISCRIMINATORY.
starting a thread just to show off your skills with Android and not offering guide and help just pisses me off really
Click to expand...
Click to collapse
Where do you see discrimination ?
There are many post on how to update a Kernel.
The dev has compile the kernel for users that don't know how to compile.
I prefer to say thanks to the user to give us the new kernel ..
Iosu
jigners said:
Is this thread exclusive for Android Elites out there?
Thanks for a very informative thread for the Noobs.
What do we do with this?
Threads shared should offer support to EVERYONE. otherwise its DISCRIMINATORY.
starting a thread just to show off your skills with Android and not offering guide and help just pisses me off really
Click to expand...
Click to collapse
If the OP had used smaller words, would that have made you feel better?
jigners said:
Is this thread exclusive for Android Elites out there?
Thanks for a very informative thread for the Noobs.
What do we do with this?
Threads shared should offer support to EVERYONE. otherwise its DISCRIMINATORY.
starting a thread just to show off your skills with Android and not offering guide and help just pisses me off really
Click to expand...
Click to collapse
And posts like yours are why I said I won't answer questions. The information is out there. I had to find it for myself, so can you.
That said, I've linked "know how" in the original post to the wiki:
http://htc-linux.org/wiki/index.php?title=Leo/UpdateKernel#Installing_latest_Linux_kernel_image_.28zImage.29
Should I try this with mattc 1.7 or is there no chance to boot it with this kernel?
Thanks for your work will test.
if OP wanted to publish something that has worked well for him
he should be willing to support the thread not warn those who
have little knowledge to stay away as he wont be answering questions
see my point? that is not in the spirit of community really now is it?
It's working fine. I don't like the first image but better than a white screen. It's overclock to 1113*** . I'll go home later to test WiFi .
Sent from my Desire HD using XDA App
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
ⓐⓝⓓⓡⓞⓒⓛⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ