[ROM version] WP7.8 Custom ROM v2.0
The [core language】 simplified Chinese, traditional Chinese, English [Date] December 6, 2012 [applicable models] HTC Radiant
[Driver version] 1.18.502.01
[Version] 7.10.8858.136
Production staff waiting for the sun [version Features]
[Special thanks]
ultrashot - fully unlocked components and 8858 core resources
Nokia - the ROM used in proprietary applications and drive
EGO - easy to use File Manager
And the other the ROM used the resources of
Please note that this version of the ROM is only suitable for brush HSPL Titan Ⅱ, the machine is a friend so I produced 7.8 ROM
Merchants have help brush newest RhodiumW Hard - SPL, I did not get HSPL the altar temporarily not release HSPL unlock tool.
There's no HSPL for you, Now!
Always simple, simple, stable and smooth
[WP 7.8 8858 v2.0 Edition]
• the complete transplant latest 8858 core, contains the latest V4 transplant • XIP, SYS, and SLDR components unlock components and finished support Simplified Chinese / Traditional Chinese / Russian / English • the official amendments Pictures magnetic stickers can not be normal scaling villain of the game can not be normal display BUG
• Fixed BUG third-party software to customize the background color with accent color normal
Push • • support of the altar offline push package as part of the Friends of the machine requires the default integration unlocked version of UC browser camera enhanced to modify HTC and Nokia, mixed mode [with Tango mode • • Change the font display * plug-in for Nokia】
• Bing Wallpaper server changed to China, updated more quickly
[WP 7.8 8838 v1.1 Edition]
1.18.502.01 version of the driver based on the official transplant 8835 core • ROM has been fully unlocked V2 version unlock components [and has been authorized by the author]
• Fixed official ROM in the country can not send MMS BUG
• enhancements replacement camera integrated the new version is more powerful plug • Nokia the search key definitions and Microsoft equipment center, finished switch • Support all ringtones list (Simplified / Traditional), English language switching • Integrated call management to support bilingual 0.95 version, and integrated into the gravity sensor setting • Delete Traditional Microsoft's own font with elegant black instead of IE 10 threaded download • the support xbmod, ultrashot and individuals own CAB package to support the 21 background • Integrated registry Push • Default regulation, screenshots and Ego original file Manager • Support for Nokia exclusive counter software and integrated • beautify the part of the start menu icon, all home magnetic background colors and themes synchronization • support Nokia exclusive share contacts and integration • Streamlining software support Nokia exclusive counter system comes with the unnecessary input method, streamline Arial used comes with software • integration • Registration has all the characteristics of this altar other ROM • increase the cache and power-saving optimization in not introduced one by one.
Download
http://pan.baidu.com/share/link?shareid=164336&uk=1560742738
The Original site
www.darkforcesteam.com.cn
There is no jailbreak for the TITAN 2. So we can not flash this ROM into our devices
when is the hspl be ready to load the custom ruu
I think the DFT will be released in the end of the world.
Why did you post this with no instructions or HSPL? Then, you make a post to taunt those who are patiently waiting. Grow up!
Sent from my SAMSUNG-SGH-I317 using xda premium
tekgurl said:
Why did you post this with no instructions or HSPL? Then, you make a post to taunt those who are patiently waiting. Grow up!
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
He said he flashed this on a RSPL machine: RSPL is Reloaded SPL but my understanding is it can only be loaded to RAM which when reset returns to OSPL. It's said if you rarely flash this will work. Over on the Radiant thread there's a guy who has a ROM in 4 parts over there, build 8112 the thread said but if he's "transplanted" 8858 guts into 8112; is that possible?
Do we have already a hspl to flash this room ???????
Hey guys please someone to replay where is our HSPL we desperately need it
The answer is NO. Now we dont have HSPL for this device.
How do we get the RSPL or temporary HSPL mentioned in the OP?
Sent from my GT-I8750 using XDA Windows Phone 7 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
ⓐⓝⓓⓡⓞⓒⓛⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ
GravityBox - all-in-one tweak box - Xposed module for devices running AOSP 4.4Version 2.8.4 [KitKat]
Version for JellyBean is available in this thread:
http://forum.xda-developers.com/showthread.php?p=48820866#post48820866
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
--- Statusbar icon colors
--- 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
--- 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
--- 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
... 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
- Samsung Touchwiz, HTC Sense, MIUI, LeWa, 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
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 fromhttp://dl.xposed.info/latest.apk (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
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.
Multilanguage support
Volunteers are welcome to translate GravityBox to other languages.
Simply download this file: https://github.com/GravityBox/Gravit...es/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://raw.github.com/GravityBox/GravityBox/kitkat/res/values/strings.xml
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!
Changelog
https://github.com/GravityBox/GravityBox/blob/kitkat/CHANGELOG.txt
Change log:
---Improved Screen Recording
--- now can be used without busybox installed
--- detects if device supports screen recording
- AppLauncher: fix missing apps after reboot on some devices
- Fixed Screen Off Effect not respecting system default
- Updated Chinese (Simplified) translations (thanks to liveasx)
- Updated Spanish translations (thanks to jvbferrer)
- Updated Japanese translations (thanks to WedyDQ10)
- Updated Italian translations (thanks to pesa1234)
Full Change log:
https://github.com/GravityBox/GravityBox/blob/kitkat/CHANGELOG.txt
Please do not post other's work as if it is your own!
Original thread here
You did not even alter the OP, just copied and pasted. Please review XDA forum rule 12
Thread closed
{
"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"
}
CHANGELOG
- Brand new design
- Second space
- Support for cloning most apps
- Long screenshots
- New scanner
- Shortcut menu
- Special effects for video editing
- New templates for Notes
- Redesigned Task Manager
- Redesigned Gallery
- Smart menu for editing text
- Wallpaper Carousel
- All-new Battery saver
- Recognition for fraudulent messages
MIUI 8 China Developer ROM 6.6.16 Full Changelog
There are over a thousand optimizations in MIUI 8, please allow me to introduce some new features for you!
- Brand new design
- Second space
- Support for cloning most apps
- Long screenshots
- New Calculator
- New scanner
- Shortcut menu
- Mi Lanting font
- Support for speech-to-text output in Recorder
- Special effects for video editing
- New templates for Notes
- Redesigned Task Manager
- Redesigned Gallery
- Smart menu for editing text
- Wallpaper Carousel
- All-new Battery saver
- Recognition for fraudulent messages
Lockscreen, Status Bar, Notification Bar
Optimization - Can't unlock Second space with Mi Band (06-14)
Fix - Couldn't see percentage progress of the system updates (06-14)
Market
New - New power saving algorithm for automatic updates (06-14)
Fix - Problems with "Install" button in Downloads (06-14)
Live
New - New design (06-15)
New - Customizable Beautify (06-15)
New - Support for Traditional Chinese and English (06-15)
Optimization - 16 new animations (06-15)
Optimization - Minor adjustments and improvements (06-15)
Mi Drop
Fix - Mi Drop could not find the receiver after GPS was closed (06-07)
MIUI 8 China Developer ROM 6.6.23 Full Changelog
Highlights
New - App lock: Unlock all apps at once (06-23)
Optimization - Loading speed for the first reboot after OTA (06-21)
System
Optimization - Loading speed increased twice for the first reboot after OTA (support for 6.0 devices) (06-21)
Lockscreen, Status Bar, Notification Bar
Optimization - Floating notification format for incoming calls (06-22)
Fix - Errors on Wi-Fi details page (06-22)
Security
New - App lock: Unlock all apps at once (06-22)
Other
Fix - FC issues with Sogou handwritten input (06-21)
MIUI 8 China Developer ROM 6.6.30 Full Changelog
Highlights
New - Preventing unwanted triggered app starts (06-28)
New - Deleting Second space while in First space (06-29)
Messaging
New - Editing rules for blocked messages (06-28)
Home screen
Optimization - Hid the switch icon when there are no current tasks (06-27)
Settings
New - Deleting Second space while in First space (06-28)
Permissions Manager
New - Preventing unwanted triggered app starts (06-28)
File Explorer
Fix - Couldn't see files saved from dual apps (06-28)
Quick Ball
New - Tap gesture for Quick ball (06-30)
MIUI 8 China Developer ROM 6.7.7 Full Changelog
Highlights
New - Saved and available Wi-Fi networks appear first in the list (07-05)
New - After a permission is restricted, a clickable notification is sent to the user which can restore permissions (07-05)
System
Fix - Interrupted Wi-Fi connection in some cases (07-07)
Lockscreen, Status Bar, Notification Bar
New - Animation for successful Wi-Fi connection (07-07)
Optimization - Separeter sound and vibration permissions for notifications (07-07)
Fix - An error whe tapping the white area of the Notification shade (07-07)
Fix - Issues with notification shade in landscape mode (07-07)
Fix - Couldn't enter Mi Home from lock screen with Second space on (07-07)
Home screen
Optimization - Fixed sound effect for deleting apps (07-07)
Fix - Wrong app was opened after long-pressing the app in Task manager (07-07)
Fix - The button for switching modes didn't work in Task Manager in some cases (07-07)
Camera
New - MIUI 8 camera (07-07) (Mi 5, Mi Max)
Settings
New - Saved and available Wi-Fi networks appear first in the list (07-05)
Market
Optimization - Start page loading speed (07-05)
Fix - Issues with sharing apps to Weibo (07-05)
MI Wallet
New - Card design by default (07-05)
MIUI 8 China Developer ROM 6.7.14 Full Changelog
Highlights
New - Deleted button in the screenshot mode (07-12)
System
Fix - Fingerprint issues (07-12)
Fix - Fingerprint scanner made the device freeze and reboot (07-12)
Lockscreen, Status Bar, Notification Bar
Optimization - Clickable arrow for Wi-Fi (07-12)
Optimization - A prompt about entering password and activating fingerprint after rebooting the device (07-13)
Fix - Customized carrier name isn't shown in Second space (07-12)
Home screen
Optimization - Landscape mode for Task manager (07-08)
Optimization - Task Manager stability (07-13)
Fix - Issues with wallpaper when switching to Second space (07-13)
Delete - Home screen Music widget (07-13)
Gallery
New - Delete directly from the screenshot preview page (07-12)
Optimization - Adjusted size for the button which creates new albums (07-12)
Optimization - "Show original" option appears only on cloud or optimized items (07-12)
Optimization - Double tap to zoom in, swipe up without entering sharing mode (07-12)
Optimization - When auto-rotate is off in Gallery, it won't influence the rest of the system (07-13)
Fix - Scrolling screenshot issues in Notes and Mail (07-12)
Fix - Couldn't go back to the original photo after making a screenshot or finishing editing/sharing it (07-12)
Fix - Couldn't pick up calls while making Scrolling screenshots (07-13)
Fix - Enter system app while editing a scrolling screenshot in the OOB flow (07-13)
Delete - Removed Edit option for GIF images (07-12)
Weather
Fix - Issues with curves in forecasts (07-13)
Mi Wallet
Optimization - Details for transport cards (07-14)
Optimization - Transport card balance displayed on the start page of Mi Wallet (07-14)
Optimization - Transport card algorithm (07-14)
MIUI 8 China Developer ROM 6.8.11 full changelog (LATEST)
Improved layout for text descriptions of Wallpaper Carousel.
Issues fixed with icons after re-flashing the device.
Three-fingered swipe for taking screenshots
New option for preview scrolling screenshot preview with a double tap.
While creating a Scrolling screenshot screen won’t go to sleep.
Issues fixed with note’s background and QQ WeChat
Major design improvements in the music app.
Optimization in adjustments in Sound & Vibration while starting
New features added in the Chinese calendar.
Improved Security. Better design, more cool features.
Optimization in finger payment, password prompt and credit and bank cards bill
Fix issues in fingerprint and password appeared simultaneously in some cases
Fix back button in Settings, music app and crashed page.
MIUI 8 China Developer ROM 6.8.11 design improvement update:
The main page of music app is recreated to provide smooth and faster performance. MIUI renovate the Music app with a new look with harmonizing colors.
MIUI 8 China Developer ROM 6.8.11 three finger swipe for taking screenshot update:
It is whole new features which enable users to take fingerprint with three finger swipe. Users can take screenshots in more convenient way with this features. Below image demonstrate the three finger swipe.
MIUI 8 China Developer ROM 6.8.11 improved security update:
In this latest MIUI ROM performance score will be shown at first page. This will saves time of users to get performance score.
MIUI 8 Global Developer ROM 6.7.5 Features and Changelog(LATEST)
New Features
Introducing new design
Introducing Second space
Dual app support for most apps
Long screenshots
New Calculator
Introducing Quick ball
New templates for Notes
Redesigned Gallery
Smart menu for editing text
Highlights
New - App lock: Unlock all apps at once (06-23)
New - Deleting Second space while in First space (06-29)
New - Saved and available Wi-Fi networks appear first in the list (07-05)
New - After a permission is restricted, a clickable notification is sent to the user which can restore permissions (07-05)
System
Optimization - Loading speed increased twice for the first reboot after OTA (support for 6.0 devices) (06-21)
Lockscreen, Status Bar, Notification Bar
New - Animation for successful Wi-Fi connection (07-07)
Optimization - Floating notification format for incoming calls (06-22)
Optimization - Separeter sound and vibration permissions for notifications (07-07)
Fix - Repetitions in Settings (06-22)
Fix - Errors on Wi-Fi details page (06-22)
Fix - An error whe tapping the white area of the Notification shade (07-07)
Fix - Couldn't enter Mi Home from lock screen with Second space on (07-07)Home screen
Optimization - Hid the switch icon when there are no current tasks (06-27)
Optimization - Fixed sound effect for deleting apps (07-07)
Fix - Wrong app was opened after long-pressing the app in Task manager (07-07)
Fix - The button for switching modes didn't work in Task Manager in some cases (07-07)
Settings
New - Deleting Second space while in First space (06-28)
New - Saved and available Wi-Fi networks appear first in the list (07-05)
File Explorer
Fix - Couldn't see files saved from dual apps (06-28)
Quick Ball
New - Tap gesture for Quick ball (06-30)
AND MUCH MORE!
Some screenshots are available for you under screenshot tab on this forum !
Wipe data highly recommended in case of issues..!
Due to the limitation of hardware platform, devices running MIUI 8 based on Android 4.4 (Redmi 1, Redmi 1S, Redmi 2, Redmi 2A, Redmi Note 3G, Redmi Note 4G) don't support 'Second space' and 'Cloned apps' for now.
FLASHING INSTRUCTIONS
download rom from given link, sound patch & GAPPS to internal memory
MMX A350 V3 PHILZ recovery is recommended to flash any MIUI Version in A350
format data, caches, dalvik caches....go to custom format option then wipe system manually
then choose MIUI 8 zip & flash...
DO NOT INSERT SIM NEITHER CONNECT TO WIFI In order to complete 1st boot setup...
install viper driver by opening app & giving supersu permission
head to xposed, Activate both Modules & install firmware followed by reboot
To Improve Loudness of thr device sound patch zip can be flashed via Recovery
Vooollllaaaa.....ready to enjoy MIUI 8( IMEI can be entered by Chamlephone app from Google play store unless u don't lose ur baseband)
Credits :
XIAOMI & MIUI -For Providing the ROM.
Dr.Rahul(ME) & My Lovely Brother Dr.Rohan-For Endless Efforts.
DON'T FLASH ANY KERNEL
Note :
-IMPORTANT: FLASH AT YOUR OWN RISK. We are not responsible for any bricked phones or damages caused due to the ROM. You lose
warranty when you root/flash ROMS on your phone.
-BATTERY: Keeping at 100% charged is recommended before flashing.
-BACKUP: Take BACKUP from recovery, useful in case you mess up. Or try Titanium to backup all data and apps.
-Please do not mirror without permission.
-Do not port without permission
-Please read the FAQ first as it might help you.
-Please don't send PM. Ask queries in the thread only.
-Please do not send request to add any app / themes.
-This ROM will be kept as as close to pure MIUI to give a rich experience.
-Please don't ask for when will you update the ROM.
-I won't guarantee anything about my ROM. If you like it keep it otherwise the most simple thing you can do is switch to some other ROM.
DOWNLOAD LINKS
Download MIUI 8 China (Dev) V.6.6.16 ROM For V3 :CLICK HERE
Download Sound Enhancement Patch : CLICK HERE
Download Philz Touch Recovery for V3 Micromax A350 : CLICK HERE
Download GAPPS for MIUI7/8 China Dev ROMS : CLICK HERE
Download OTA_v4.4.2_A350_6.6.16_6.6.20_MIUI8 : CLICK HERE
Download OTA_v4.4.2_A350_MIUI8_6.6.20_6.6.23 : CLICK HERE
Download OTA-v4.4.2-A350-MIUI8-6.6.23-6.6.30-fix : CLICK HERE
Download MIUI 8-Multilingual-V.6.7.7-A350-ROM with Global Theme Support : CLICK HERE
Download MIUI 8-OTA-V.6.7.7-V.6.7.14-A350-DR.RAHUL : CLICK HERE
Download MIUI 8-OTA-V.6.7.14-V.6.8.11-A350-DR.RAHUL : CLICK HERE
Download MIUI 8-Global-Dev-V6.7.5-A350-ROM(NEW) Dated: -11/07/2016 : CLICK HERE
MIUI 7 THREAD LINK FOR A350 : CLICK HERE
XDA:DevDB Information
MIUI 8 for Knight, ROM for the Micromax Canvas Knight
Contributors
rsbaviskar, rohanbaviskar530
Source Code: https://github.com/tpruvot/MT6592-KK-KERNEL
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: kitkat 4.4.2 v3 merge storage
Based On: MIUI, AOSP
Version Information
Status: Stable
Current Stable Version: 6.6.16,6.6.20,6.6.23
Stable Release Date: 2016-06-17
Created 2017-01-01
Last Updated 2017-01-01