Related
what are some tweaks everyone is using on their stock F/W's?
I have removed:
sony sync, setup and guides, some of the stock apps that i don't use
added:
bravia engine (might remove due to suspicious battery consumptions)
misc tweaks:
build.prop
changed vm heapsize to 48m
added windowsevent line
added scripts to change read_ahead to 3072 (works best with my sccard)
disabled a lot of start up apps
hitting around 1372 in quadrant and 36-37 in linpack
what are some other tweaks that can be added that others are using?
Fps uncap by z. Im also want to removed bravia, could you show me how to do it pls?
Sent from my X10i using XDA App
teddymild said:
Fps uncap by z. Im also want to removed bravia, could you show me how to do it pls?
Sent from my X10i using XDA App
Click to expand...
Click to collapse
i just restored system from a previous backup
Im hoping an easier
Way. Tks anyway.
Sent from my X10i using XDA App
- prevent lag after boot if you have lots of pictures and don't use the 3D gallery at all but QuickPic or another alternative: install Rescan Media Root from Market.
Another way would be to simply rename the gallery but then adding images to contacts doesn't work.
- free root explorer: Estrong File Explorer, the root mode didn't work in 2.1, but it does now!
- AppWidgetPicker still works in GB (display submenus for widget selection instead of a long list)
- turning off the button leds still works in GB:
#! /system/bin/busybox sh
DIR=$(cd /sys && find | grep brightness | cut -c 3- | cut -d : -f 1 | head -n 1)
LED=/sys/$DIR
LEDB=$LED:sled/brightness
echo 0 > $LEDB
exit
zorglub08 said:
- prevent lag after boot if you have lots of pictures and don't use the 3D gallery at all but QuickPic or another alternative: install "Rescan Media Root" from Market.
Another way would be to simply rename the gallery but then adding images to contacts doesn't work.
- free root explorer: Estrong File Explorer, the root mode didn't work in 2.1, but it does now!
- WidgetPicker still works in GB (display submenus for widget selection instead of a long list)
- turning off the button leds still works in GB:
#! /system/bin/busybox sh
DIR=$(cd /sys && find | grep brightness | cut -c 3- | cut -d : -f 1 | head -n 1)
LED=/sys/$DIR
LEDB=$LED:sled/brightness
echo 0 > $LEDB
exit
Click to expand...
Click to collapse
Can you share WidgetPicker with me? I can't seem to find it in the market.
@OP - i was just about to start a thread like this!!
For those of us that would like to keep the stock rom and apply tweaks ourselves we need people that know the tweaks to share them! Should we use autokiller/sysctl for example?
How about spare parts with compcache/[email protected]?
i look forward to hearing what is possible!
@op, i set VM to 64, but not sure if there is a noticeable difference!
Sorry, it's AppWidgetPicker, I added the link now.
svtfmook said:
what are some tweaks everyone is using on their stock F/W's?
I have removed:
sony sync, setup and guides, some of the stock apps that i don't use
added:
bravia engine (might remove due to suspicious battery consumptions)
misc tweaks:
build.prop
changed vm heapsize to 48m
added windowsevent line
added scripts to change read_ahead to 3072 (works best with my sccard)
disabled a lot of start up apps
hitting around 1372 in quadrant and 36-37 in linpack
what are some other tweaks that can be added that others are using?
Click to expand...
Click to collapse
Hi, what do u mean "windowsevent line" ?
as quoted here in step 13. < this is from a tweaks guide for 2.1
For the thread, if you are experiencing problems downloading from your browser:
d/l astro file manager from the market, go into preferences (more/preferences) and tick the "enable browser downloads" box. this is not my find, I read it earlier somewhere here on xda
I direct rooted my fw and flashed Bravia engine, so far so good.
Is there any way to flash FPS uncap for stock ROM without the need of a new ROM?
Edit : Already done.
some hacks on mine
build.prop
HTML:
ro.telephony.call_ring.delay=1000
ro.mot.eri.losalert.delay=1000
ro.min_pointer_dur=100
mot.proximity.delay=750
dalvik.vm.startheapsize=64m
dalvik.vm.heapsize=64m
windowsmgr.max_events_per_sec=260
ro.FOREGROUND_APP_MEM=5120
ro.VISIBLE_APP_MEM=6144
ro.SECONDARY_SERVER_MEM=8192
ro.BACKUP_APP_MEM=8192
ro.HOME_APP_MEM=8192
ro.HIDDEN_APP_MEM=21000
ro.CONTENT_PROVIDER_MEM=23000
ro.EMPTY_APP_MEM=25000
create a new file without extension on \system\etc\init.d\ folder and name it to S96sdcardspeedfix
HTML:
#!/system/bin/sh
if [ -e /sys/devices/virtual/bdi/179:0/read_ahead_kb ]
then
/system/xbin/echo "2048" > /sys/devices/virtual/bdi/179:0/read_ahead_kb;
fi;
if [ -e /sys/devices/virtual/bdi/179:8/read_ahead_kb ]
then
/system/xbin/echo "2048" > /sys/devices/virtual/bdi/179:8/read_ahead_kb;
fi;
if [ -e /sys/devices/virtual/bdi/default/read_ahead_kb ]
then
/system/xbin/echo "2048" > /sys/devices/virtual/bdi/default/read_ahead_kb;
fi;
create a new file without extension on \system\etc\init.d\ folder and name it to 99SuperCharger - use busybox 1.18.2 and script manager for this
HTML:
due limit of characters to post, download the file attached and delete .txt
check this to find out more about SuperCharger
enjoy some of the "hidden" hacks out there
there´s so much more....search
as an addition to rendiero's post, results will vary depending on your sdcard. try other settings like 1024m, 2048m, 3072m, 4096m
svtfmook said:
as an addition to rendiero's post, results will vary depending on your sdcard. try other settings like 1024m, 2048m, 3072m, 4096m
Click to expand...
Click to collapse
yap, you´re right i forgot to mention that thanks
Stating the obvious but remove apps that aren't needed!
SEMCSettings
Livewallpapers
etc etc.
here's a list of stock apps that i haev found to be ok when removed (results may vary, you may have something installed/using may depend on some of these)
device-monitor.apk - error reporting
OMAClientProvisioning.apk - part of sony sync
OmaDatasyncService.apk - part of sony sync
OmaV1AgentDownloadServices.apk - part of sony sync
PcCompanion.apk - pc companion installer
POBoxSknPink.apk - skin for japanese keyboard
POBoxSknWood.apk - skin for japanese keyboard
SecureClockJava.apk - not sure what it's for, but i have had no problem after removing it
SemcCrashMonitor.apk - more error reporting
Sync.apk - part of sony sync
SyncWizard.apk - part of sony sync
usersupport.apk - teaches you how to use your phone
SEMCsetupwizard.apk - initial setup, once you've done it, you don't need this anymore
LiveWallpapersPicker.apk - live wallpapers
MediaWidget.apk - media widget
MusicWidget.apk - music widget
Japaneseime.apk - japanese keyboard
koreanime - korean keyboard
removing the above will have no effect on timescape/facebook integration (that i have found, everything has been working fine for me)
@rendiero: for the 2 tweaks 99SuperCharger and S96sdcardspeedfix,can you write a step by step please?
Because i am little confuse with busybox and script manager.
On the tuto in the links for supercharger i write some value like 6,16, ...
For X10 the value are same or?
I have add same line on my build.prop now my phone stuck on Sony Ericsson logo.
I need to restore my backup
Are you on any moded Rom? Cause as I understood this thread is for stock one. That may cause some instability issues?
sent from tapatalk on my Domm's mod rom
@Renderio, thanks for those, i will stop and try these later! the build prop is easy enough but will test the other 2 as well
thanks dude - you rule! please (all) let us know if any 'other tweaks/performance apps' can be applied - OR if they clash with any already stated (tweak conflicts where 2 process are doing the same thing, for e.g setcpu & other cpu app both doing the same tasks - you get my meaning i hope!!)
Thanks
The last 2 may conflict with wolf's Rom.
To use those you need to know witch files you must delete/change on it.
sent from tapatalk on my Domm's mod rom
An all in one collection for Galaxy S II where you can get all the information, tutorials, guides, mods, apps, tweaks, tips, tricks, DIY and many more.
Tutorials & Guides
How to build a perfect ROM
Know the Basics
Without knowing what you are getting yourself into will only make things worse even before you start off. To build a good Rom is different and to atleast build a fully functional Rom is different. So make sure you are fully aware of the technical fundamentals of building a Rom to enough extent so that you are able to fix the bugs and know what and where can things go wrong and how to solve them.
Performance, Memory, Stability and Battery
These are the four defining points which decide the pros and cons of the Rom that you develop. The Rom should be Fast, Have enough storage and program memory, should be stable and have a good battery backup. Trying to get a good balance of all these is very important. So make sure you keep all these things in mind while developing your Rom.
Be Patient and Polite
Building a good/perfect or bug free Rom wont come immediately. It’ll take many releases, experiments, testing and knowledge till you reach a nearly perfect Rom. So be patient as it sometimes takes weeks or sometimes months. Dealing with the public is not an easy job. You’ll find all sort of people of various characters. The can be nice as well as rude, but do remember that their critics are the only way you can improve. All they want from you is a good Rom, just keep this in mind and ignore the negatives.
Make it User Friendly
There are many ways in which you can make your Rom user friendly. Integrating useful apps. Prepping Eye candy themes, Important shortcuts etc.
Stay Motivated
This is the only driving force behind every Rom developer to continue doing their work with ease and success. Stay motivated and alert so that you can deliver the best with every release. Its hard sometimes but its it important.
Give Time to your Work
Most of the developers are either students or work some where and building Roms is some what like a hobby for us. Its correct that we are not supposed to spend all the time on building Roms but if we want to have a good working Rom we should manage considerable amount of time for few alternate days to work on this project.
Make it Different
You Rom characteristics should be some what different from what is already been provided by other developers. If its nothing different and Catchy then it’ll be hard to get users trying your Rom consistently. I still remember the days when i used to try alot of different Roms but still couldn’t find one that was nearly perfecting my needs. I tried alot of Roms that time.
Join Hands with another Developer
This is what i like the most. Join hands and team up with other developers and thus improve the efficiency and effectiveness of your Rom. The mind of two can bring together wonders. You can even team up with Developers of other devices and build a Rom for device that you personally do not own but you you widen your work area.
Don’t be ignorant
Make sure you are attentive and up to date with all what is discussed about your Rom, all bugs, all tests, reports, etc. so that you do not miss out on any bug possibly to be fixed for next release. If you ignore or avoid fixing the important bugs, the users will think that you are not really capable of solving them or not really interested in this Rom.
Get Testers
Testers are users who like to test the Rom and report you the bugs before you go public with the release. They are very helpful if you like to avoid the criticism after the release of the Rom as before itself you’ll be able to get rid of maximum number of Bugs and issues present in the Rom. That is where testers come in handy. Jus give a notice and many would love to try and test your Beta releases.
Keep Detailed Changelogs
Changelogs keep track of your developments over the time. They come in handy when ever you need to check for prolonged bugs. For example you may not notice it but if someone reports that he has been having an issue since your 3rd Rom release, then you can check out what all changes you made on that release and cross check whether one of those changes cause that bug.
Be Active on the Rom Page
This is the most important part of being interactive with the users cause there is alot that they want to be done in your Rom. Talk to them, answer their questions and discuss the pros and cons of the Roms with them. You can learn alot from them. Being active to the discussion will make them feel that you are eager to further develop and make this Rom improve further.
Add only Useful apps and Regularly Update them
Make sure the application you add to your Rom are useful by the people. Adding two Music Players in the Rom is not a good choice. Choose one that is best and use that only. But make sure you add one possibly best Application for all needs of the users. Keep track of all the applications that you have included in your Rom and make sure the latest versions are included. It keep the user feel updated with your Rom. Many times there are applications which are important to add but have some bug. Later these bugs are fixed in their next releases, so even you should add those updated fixed Applications. Use only Genuine Licenses and No Warez Applications. Warez is like a virus to the development of your Rom. Copyright issues and illegal use of cracked applications make pose a ban on you Roms by the Blogs and threads where you list them. Either you use development licenses to use the in your Roms or use an equally good free Application.
Good looking User Interface and Graphics
This is the major aspect that defines your Rom and makes it distinct from others. Work on that graphics that can be changed in your Rom, try different themes and skin enhancements in different aspects of os like dialer, lockscreen, fonts etc.
Keep Polls and ask Questions
Polls and asking questions from users is a very important way by which you can interact with users and get their feedback. Polls can be asking them about their preferences. Which applications they like or dislike, asking frequents questions on that changes you will be making in the Rom cause at the end of the day it is them who will be using them.
Learn from Competition
I don’t call the fellow developers a competition and usually many share their work and are supportive like i am to each other’s work. But you can learn from what is included in their Rom and if its catchy and important then you can add it to your Rom aswel. There might be many new and useful applications and features that other developers might be using and you are not even aware of that. It can be very helpful in evolving your Rom completely.
Listen and Learn from Users
Listening what a user has to say about their experiences on using your Rom is very important. They might have something very important to share from their experiences which you can incorporate in your Rom. It really helps in fixing bugs and improving your Rom further.
In the end you are the Decision Maker
Its you who has to take the decisions in the end. There will be many people wanting you to do this or that and add this or remove that but in the end you have to keep an unbiased judgment on all the requests, ideas and suggestions and bring forward the changes that you feel the masses are going to appreciate. And for that you will need to take care of all the above mentioned points in mind.
Give Credits
Not to forget that 70%-80% of your work is inspired from that of other developers. And it wonk charge you anything to be humbly give credit or some appreciation to the help you have got from other developers in terms of guides, tips, tricks, applications, UI Enhancements, etc. It just shows your character as a person as well.
What are Stock Roms and Custom Roms?
What is a Rom?
ROM – Read Only Memory is that memory which stores the system files of your Device. Those files which make up the basic Operating System, be is Windows Mobile Phone OS, Android, Symbian, Windows OS, etc. Every electronic device has a Read only Memory which stores the basic programming of the functions that the Electronic equipment is to perform. ROM in terms of our Android Devices the basic set of programming applications and files of functions which your device performs Out of the Box. Without a Rom no electronic device exists.
What are Stock ROMs?
Those ROMs which come pre installed are called Stock ROMs. Stock ROMs are the ones that come Box packed with your Device preinstalled. These are official Software that are provided by the Manufacturer or the OEM.
Is it possible to Edit/Customize/Alter Stock ROMs?
Yes it is. For a lot of Operating Systems be it Windows Mobile Phone OS, Android, Symbian, etc, it is possible to Customize these stock ROMs and install them to our devices.
What are Custom ROMs?
They are Custom ROMs are based on Stock ROMs but customized by the user in terms of additions in applications, improvements, removal of unnecessary application, etc. A customized ROM may be an minor improvement to Stock Rom or can even be a complete makeover of Stock Rom even changing the drivers of the Rom with that of other compatible devices providing better performance.
Why do we need Custom Rom?
Customization is making things personal. That is one main reason why we customize a Stock Rom. A stock Rom no matter what will have a lot of unnecessary applications, files, images, settings that are pre set by the Manufactures but are not at all important to us and uses a lot of space for no reason. No matter what there has to be one or the other Bug in a Stock Rom. To get rid of these issues we customize a stock ROM by either adding useful applications, settings, removed crap, fixing bugs and on getting a Top Notch easy to use and completely customized Device.
What about the warranty?
This is decision that you need to make personally. Yes, Custom ROMs will take away your precious warranty. But that to only if your device stops working while you are using Custom Rom on your device and you have to take it to the company. If you want you can revert back to Stock ROMs and then take your device to the Service Center and they won’t even know about it. But you need to consider reverting back to Original Stock Rom.
su
Also referred to as substitute user - a command for changing the account in the current terminal (usually black screen with blinking cursor). Default account is root account. So if you insert into terminal 'su' and hit enter, you will become root user.
root
Root alias superuser or poweruser is special user account for system administration. Similar to windows having its administrator account, unix-like systems have a root account. With this, you can do anything and if you run a command to delete the whole system, unix will just do it! No asking, no confirming. So, watch your steps!
rooting
Rooting is just enabling power of root for applications and other purposes.
Superuser app
After rooting is done, you will see a new app called superuser in app drawer. This app can delegate applications to use su (root) feature. When an app asks this from first use, a popup window will appear asking if the application should be allowed to use root permission.
sh, bash
is a command-line interpreter or shell that provides a traditional user interface for the Unix operating system and for Unix-like systems. So simply, it is some interface, which can execute command(s), which you have entered. Many shells exist, but in scope of android you can (as far as I know) use only sh (standard - Bourne-shell) or bash (compiled in BusyBox or separately on XDA). Both are basically same, but bash has much more features and it is more comfortable.
user/root shell
How do I know if I'm root or normal user? It's simple. Root's shell is ended with # (usually it's shell looks like "bash-3.2# _") and user's ends with $ (usually bash-3.2$ _). In terminal emulator you also can have only [path]($|#) (for root for example "/etc # _")
BusyBox
also called "The Swiss Army Knife of Embedded Linux" is a tool which brings into Android basic tools known from unix system, but is much more smaller than standard tools is. But this "packing" has limited functions in comparison to standard tools in unix-system (missing special modes of tool, color output and so on). Many application use this. For example busybox grep (filtering of text) is needed for application called Market enabler.
BusyBox commands
list of commands is really wide, so it's not possible explain all, so I pickup only top few. (hint: if you want what some command do, just search on google for "man <command_name>" for example man mv or enter command here
cd - change directory - same like in windows. You can switch directory. example: cd /sdcard
ls - list of files in actual directory (have few switches like for example: ls -l /sdcard/*.png (detailed listing)
cat - print file into standard output (like more in windows) Example: cat /sdcard/data.txt
vi - editing of file. But on limited phone keyboard (no keyboard) it is little harder Read more about vi
cp - copy of one or more file. Example: cp /sdcard/bike.jpg /sdcard/media/bike-wallpaper.jpg
mv - moving/rename files, Example: mv /sdcard/bike.jpg /sdcard/media/renamed-moved-bike.jpg
rm - delete file (rm -R for recursive, or for delete whole folder), Example: rm -R /sdcard/wallpaper-bad/*
find - search for files, Example find / -name "best-chopper-ever.avi"
mkdir - make directory - creates directory, Example: mkdir mynewdir
chmod - changes access of files
less - similar like cat, but you can scroll in it and it doesn't produce any output. Example: less /sdcard/funnytext.txt
For BusyBox's tool help, just enter BusyBox <command_name> -h.
ADB (shell)
ADB - Android Debug Bridge is a versatile tool that lets you manage the state of an emulator instance or Android-powered device. It is a client-server program that includes three components:
* A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
* A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
* A daemon, which runs as a background process on each emulator or device instance.
Generally, it can be compared with standard cmd prompt in windows (you can write commands which will be executed locally, for example in Terminal Emulator) or it can be just like SSH in unix-like system (you connect to terminal through adb client (in Android SDK) and commands will be run remotely.
Android SDK
Android software development kit is a complex set of tools for developing apps on Android. It includes a fully usable emulator of Android OS on your PC, where you can do everything. You can install/delete apps, browse web page in embedded web browser, play games or make your own application in Eclipse (widely used IDE for development). Of course, with emulator you can use also GPS or camera.
Android SDK tools
* Fully emulated Android device
* Android Development Tools Plugin (Eclipse IDE)
* Android Virtual Devices (AVDs)
* Hierarchy Viewer
* layoutopt
* Draw 9-patch
* Dalvik Debug Monitor Service (ddms)
* Android Debug Bridge (adb)
* Android Asset Packaging Tool (aapt)
* Android Interface Description Language (aidl)
* sqlite3
* Traceview
* mksdcard
* dx
* UI/Application Exerciser Monkey
* monkeyrunner
* Android
* zipalign
Tools for work with Android adb shell
You have two ways to connect into ADB service - locally and remotely.
Locally - for local access you will need some application which can connect to local adb shell.
Terminal Emulator (free) - probably most commonly used app from market, which works and looks like standard unix shell.
ConnectBot (free) - same as Terminal Emulator, but it can be also used for connecting via SSH or telnet
Remotely- For remote connection you need phone configuration adjustment:
Home desktop -> [menu button] -> Settings -> Applications -> Development -> USB debugging [ON].
Also you need connect your phone via USB (or finds on market some widget/app, witch enable using ADB also via wi-fi)
adb tool from Android SDK
After downloading Android SDK, extract the archive anywhere (in example I extracted it in c:/AndroidSDK). Then follow instructions on developer.android.com for installation of SDK Platform-tools (contains adb). After installation click on start menu and in Run... (in Windows7 in search bar) enter 'cmd' and press Ok or [enter]. Then write in cmd line:
Quote:
cd c:\AndroidSDK\android-sdk-windows\tools [enter]
now you can enter following command to connect to phone's adb shell if you don't have more connected device (virtual or real-one)
Quote:
adb shell
If you have more then one, you need explicitly say which one should be used for connection. So list connected devices with
Quote:
adb devices
which shows you serial number of connected devices. Than use
Quote:
adb -s <serial-number> shell
3. Custom recovery
* What is custom recovery
* Tools which custom recovery provide - NAND backup/restore, formatting of SDcard, partitioning (ext1,ext2, ext3), wiping, flashing of Custom ROM, ...
* Is it safe to install? - potential problems, backup/restore of original recovery
* How this whole thing works - installation description (not how-to install, just explanation of what is done during installation)
What is custom recovery
Recovery is an image (binary data) stored in internal memory. This image contains something like a "program" or "tool", which can boot-up independently from the Android system. This tool is part of phone system, and in PC terminology recovery can by compared to BIOS with some added features. This recovery state can be reached on all phones, but if you don't have a custom recovery, it will do a so-called HW reset and automatically restart itself into standard boot mode.
Tools which custom recovery provides
* USB-MS Toggle :mounts sdcard as mass storage
It just mounts your phone as USB-mass storage (USB disk) so you can access it through your PC
* Backup/Restore:
Absolutely GREAT feature. With NAND you can copy an image of your actual system (phone's memory). It means that you can backup the whole system with all configuration, customization, wallpapers, system's tweaks... just everything. This image will be written to your SD card which you are then free to copy around and back up on your computer
* Flash Zip From Sdcard
This tool is designed for installation of custom ROMs or tweaks. If you are instructed to install via custom recovery, then you should use this menu. Never unzip the file because it contains meta-information about itself with some validate-checks so if you edit it, or unpack and pack back, it won't work. And remember to place the file in the root (main folder) of your sdcard.
* Wipe Menu:
Wipe data/factory reset: wipes data & cache
- wipes user data (contacts, apps, configuration, ...) and cache (caches of applications)
Wipe cache
- wipes cache only
Wipe Dalvik cache : Wipes Dalvik cache in all possible locations if moved by apps2sd
- wipes Dalvik cache
Wipe SD:ext : Wipes Apps2sd ext partition
- if you used Partition SDcard option, you can wipe it here
Wipe Battery Stats (remember to fully charge your phone before doing this)
- If you think, that your battery life is too short, you can try delete battery stats. Than let phone fully charge. (more)
Wipe rotate settings
- wipe sensor settings (acceleration, ...)
Wipe .android secure : Wipes froyo native .android_secure on sdcard
- wipe information about moved apps
* Partition Sdcard:
Partition SD: Partitions sdcard for apps2sd (this formats card so all data will be lost)
- will create ext2 partition (you will be asked for size of ext2 and cache)
Repair Sd:ext
SD:ext2 to ext3 : converts apps2sd ext2 partition to ext3 (requires kernel support for ext3)
SD:ext3 to ext4 : same as above but ext3 to ext4 (requires kernel support for ext4)
ext2 - file system for the Linux kernel (no journal, fast but not recovery of I/O error)
ext3 - file system for the Linux kernel (journal, slower than ext2 because of journal, but provides recovery on I/O error)
ext4 - file system for the Linux kernel (journal, enhanced version of ext3)
* Mounts:
Gui automatically mounts folders
png-optimized -
png files takes less memory, are loads faster
JIT -
just-in-time compilation also known as dynamic translation, is a method to improve the runtime performance of computer programs, but it takes some time to convert into it on start.
HW:acceleration -
using of HW acceleration for rendering GUI. Increases battery consumption.
VM.Heap Size -
maximum memory an application can consume
stagefright -
In Android 2.2 new media framework that supports local file playback and HTTP progressive streaming
Deodex
Advantages or disadvantages
- Odexed ROMs are slightly faster, deodexed ROMs are slightly slower
+ You can make custom themes for your ROM
+ Performance los is negligible.
Requirements:
Download XUltimate
Busybox installed
Root
1. Connect phone to computer
2. Start xUltimate, we will now get the required files from our phone to deodex and zipalign it which we will describe in the 3rd step.
3. On the main menu of xUltimate, choose option 5 (Pull and deodex all). Everything will be done for you here. Don't worry. You will see all your finished files in the folders 'done_app' and 'done_frame' which are located in the installation directory of xUltimate.
4. move folders 'done_app' and 'done_frame' folders to your sdcard, you can find these folders in the directory of xUltimate as described in the previous step.
5. Make sure the sdcard is not mounted to pc anymore
6. Open Windows Command Prompt and type the following commands.
adb shell
su
stop
mount -o remount,rw /dev/block/stl12 /system
rm /system/app/*.odex
rm /system/framework/*.odex
busybox cp /sdcard/done_app/* /system/app/
busybox cp /sdcard/done_frame/* /system/framework/
chmod 644 /system/app/*
chmod 644 /system/framework/*
mount -o remount,ro /dev/block/stl12 /system
sync
reboot recovery
7. Now data and cache reset in the recovery menu...
8. reboot
If one of the commands, for example 'cp' is not found, try putting busybox in front of the command:
eg: busybox cp /sdcard/done_frame/* /system/framework/
--------------------------------------------------------------------------------------------------
[How To] Setup ADB for Windows/ Mac
For Windows
Want to set up ADB or Android Debugging Bridge on your PC, here is a quick guide for you. This tutorial does not need large download or full Android SDK installation. You will just have to download a small compressed file, which is all that you require.
STEP 1: First download this file called ADBUNZIPTOCDRIVE.zip, just click on the link, download will start automatically.
STEP 2: Now download PdaNet for driver installation. It comes with drivers from all major manufacturers, so this is all you need. Install PDAnet after downloading.
STEP 3: Now extract the zip file that we downloaded in the first step to C drive and name the extracted folder ADB.
STEP 4: Now we will go to the desktop and right click to make a new shortcut.
STEP 5: Point the shortcut to ADB folder that we created in step 3, and name the shortcut ADB or whatever you want.
STEP 6: Now right click on that shortcut and go to properties and change START IN field to c:\adb.
STEP 7: Click Apply or OK and you are done. Click on ADB shortcut on the desktop and you are good to go.
Here is list of ADB commands that might be useful for you in the future.
adb devices – list all connected devices
adb push <local> <remote> – copy file/dir to device
adb pull <remote> [<local>] – copy file/dir from device
adb sync [ <directory> ] – copy host->device only if changed
adb shell – run remote shell interactively
adb shell <command> – run remote shell command
adb emu <command> – run emulator console command
adb logcat [ <filter-spec> ] – View device log
adb forward <local> <remote> – forward socket connections forward specs are one of: tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp – list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> – push this package file to the device and install it
adb uninstall [-k] <package> – remove this app package from the device (‘-k’ means keep the data and cache directories)
adb bugreport – return all information from the device
that should be included in a bug report.
adb help – show this help message
adb version – show version num
adb wait-for-device – block until device is online
adb start-server – ensure that there is a server running
adb kill-server – kill the server if it is running
adb get-state – prints: offline | bootloader | device
adb get-serialno – prints: <serial-number>
adb status-window – continuously print device status for a specified device
adb remount – remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] – reboots the device, optionally into the bootloader or recovery program
adb reboot-bootloader – reboots the device into the bootloader
adb root – restarts the adbd daemon with root permissions
adb usb – restarts the adbd daemon listening on USB
adb tcpip <port> – restarts the adbd daemon listening on TCP on the specified port
:: build.prop tweaks ::
Experimental / Not Tested
##Date format
ro.com.android.dateformat=MM-dd-yyyy
ro.com.google.locationfeatures=1
ro.setupwizard.mode=DISABLED
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
# Default network type.
ro.telephony.default_network=8
##8 => CDMA/EVDO/LTE auto mode preferred. (I don't know what should be the value for our Galaxy 3)
#proximit sensor disable touch distance
mot.proximity.distance=60
Working
##Makes phone boot rapidly fast
persist.sys.shutdown.mode=hibernate
##Force launcher into memory
ro.HOME_APP_ADJ=1
## Raise JPG quality to 100%
ro.media.enc.jpeg.quality=100
##VM Heapsize; 178MB RAM = 32 is better
dalvik.vm.heapsize=48m
##Render UI with GPU
debug.sf.hw=1
##Decrease dialing out delay
ro.telephony.call_ring.delay=0
##Helps scrolling responsiveness
windowsmgr.max_events_per_sec=150
##Save battery
wifi.supplicant_scan_interval=180
pm.sleep_mode=1
ro.ril.disable.power.collapse=0
##Disable debugging notify icon on statusbar
persist.adb.notify=0
##Increase overall touch responsiveness
debug.performance.tuning=1
video.accelerate.hw=1
##Raise photo and video recording quality (2.3 ROM only)
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
# Photo and video recording quality tweak (2.2 Rom only)
ro.media.dec.jpeg.memcap=10000000
ro.media.enc.hprof.vid.bps=1000000
##Signal (3G) tweaks
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=10
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=6
ro.ril.def.agps.feature=1
ro.ril.enable.sdr=1
ro.ril.enable.gea3=1
ro.ril.enable.fd.plmn.prefix=23402,23410,23411
ro.ril.enable.a52=1
ro.ril.enable.a53=1
ro.ril.enable.dtm=1
##Net speed tweaks
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
##Disable blackscreen issue after a call
ro.lge.proximity.delay=25
mot.proximity.delay=25
##Fix some application issues
ro.kernel.android.checkjni=0
##Phone will not wake up from hitting the volume rocker
ro.config.hwfeature_wakeupkey=0
##Force button lights on when screen is on
ro.mot.buttonlight.timeout=0
##Disable boot animation for faster boot
debug.sf.nobootanimation=1
# Enable Stagefright helps stream Video and Music Faster
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
# Enable display Dithering
persist.sys.use_dithering=1
# Enable purgeable assets
persist.sys.purgeable_assets=1
# For SD storage insert notification sound
persist.service.mount.playsnd=0
##Miscellaneous flags
ro.config.hw_menu_unlockscreen=false
persist.sys.use_dithering=0
persist.sys.purgeable_assets=1
dalvik.vm.dexopt-flags=m=y
ro.mot.eri.losalert.delay=1000
Click to expand...
Click to collapse
init.d scripts
(needs ROM with init.d access and busybox, open empty file, insert header #!/system/bin/sh and put these there, save in /system/etc/init.d and name it something like 77tweaks)
Code:
##internet speed tweaks
echo "0" > /proc/sys/net/ipv4/tcp_timestamps;
echo "1" > /proc/sys/net/ipv4/tcp_tw_reuse;
echo "1" > /proc/sys/net/ipv4/tcp_sack;
echo "1" > /proc/sys/net/ipv4/tcp_tw_recycle;
echo "1" > /proc/sys/net/ipv4/tcp_window_scaling;
echo "5" > /proc/sys/net/ipv4/tcp_keepalive_probes;
echo "30" > /proc/sys/net/ipv4/tcp_keepalive_intvl;
echo "30" > /proc/sys/net/ipv4/tcp_fin_timeout;
echo "404480" > /proc/sys/net/core/wmem_max;
echo "404480" > /proc/sys/net/core/rmem_max;
echo "256960" > /proc/sys/net/core/rmem_default;
echo "256960" > /proc/sys/net/core/wmem_default;
echo "4096,16384,404480" > /proc/sys/net/ipv4/tcp_wmem;
echo "4096,87380,404480" > /proc/sys/net/ipv4/tcp_rmem;
##vm management tweaks
echo "4096" > /proc/sys/vm/min_free_kbytes
echo "0" > /proc/sys/vm/oom_kill_allocating_task;
echo "0" > /proc/sys/vm/panic_on_oom;
echo "0" > /proc/sys/vm/laptop_mode;
echo "0" > /proc/sys/vm/swappiness
echo "50" > /proc/sys/vm/vfs_cache_pressure
echo "90" > /proc/sys/vm/dirty_ratio
echo "70" > /proc/sys/vm/dirty_background_ratio
##misc kernel tweaks
echo "8" > /proc/sys/vm/page-cluster;
echo "64000" > /proc/sys/kernel/msgmni;
echo "64000" > /proc/sys/kernel/msgmax;
echo "10" > /proc/sys/fs/lease-break-time;
echo "500,512000,64,2048" > /proc/sys/kernel/sem;
##battery tweaks
echo "500" > /proc/sys/vm/dirty_expire_centisecs
echo "1000" > /proc/sys/vm/dirty_writeback_centisecs
##EXT4 tweaks (greatly increase I/O)
(needs /system, /cache, /data partitions formatted to EXT4)
tune2fs -o journal_data_writeback /block/path/to/system
tune2fs -O ^has_journal /block/path/to/system
tune2fs -o journal_data_writeback /block/path/to/cache
tune2fs -O ^has_journal /block/path/to/cache
tune2fs -o journal_data_writeback /block/path/to/data
tune2fs -O ^has_journal /block/path/to/data
##perfect mount options
busybox mount -o remount,noatime,noauto_da_alloc,nosuid,nodev,nodiratime,barrier=0,nobh /system
busybox mount -o remount,noatime,noauto_da_alloc,nosuid,nodev,nodiratime,barrier=0,nobh /data
busybox mount -o remount,noatime,noauto_da_alloc,nosuid,nodev,nodiratime,barrier=0,nobh /cache
##Flags blocks as non-rotational and increases cache size
LOOP=`ls -d /sys/block/loop*`;
RAM=`ls -d /sys/block/ram*`;
MMC=`ls -d /sys/block/mmc*`;
for j in $LOOP $RAM
do
echo "0" > $j/queue/rotational;
echo "2048" > $j/queue/read_ahead_kb;
done
##microSD card speed tweak
echo "2048" > /sys/devices/virtual/bdi/179:0/read_ahead_kb;
##Defrags database files
for i in \
`find /data -iname "*.db"`
do \
sqlite3 $i 'VACUUM;';
done
##Remove logger
rm /dev/log/main
##Ondemand governor tweaks
SAMPLING_RATE=$(busybox expr `cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_transition_latency` \* 750 / 1000)
echo 95 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo $SAMPLING_RATE > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate
##Auto change governor and I/O Scheduler
a) I/O Scheduler (Best: MTD devices - VR; EMMC devices - SIO) - needs kernel with these
echo "vr" > /sys/block/mmcblk0/queue/scheduler
or
echo "sio" > /sys/block/mmcblk0/queue/scheduler
b) Governor (Best: Minmax > SavagedZen > Smoothass > Smartass > Interactive) - needs kernel with these
echo "governor-name-here" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
##Block Ads with Hosts regularly updated in Sekhy ROM
Patch your hosts file for blocking Ads
(please think before doing this; many developers are supported through this way)
You can use AdFree application for this or changing manually your hosts file.
Here are some databases:
http://www.mvps.org/winhelp2002/hosts.txt
http://pgl.yoyo.org/adservers/serverlist.php?showintro=0;hostformat=hosts
##Use Google's dns servers
Create an empty file, name it resolv.conf and put there these 2 lines:
nameserver 8.8.8.8
nameserver 8.8.4.4
Save to /system/etc/.
Update Superuser and su binary to latest version
http://goo-inside.me/superuser/
I think many of you were familiar with QTADB. It is easy to manage your phone with it. But geeks who are interested doing the stuff in different ways try some of these:
Go to command command prompt where your ADB installed. (assuming you are familiar installing adb before doing these)
To install ADB download these and extract to any of the desired drive. Say D:\ or E:\ etc.
code to delete unwanted apps:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
rm /system/app/nameofapk.apk
Click to expand...
Click to collapse
code to add apps and stuff:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
exit
exit
adb push nameofapk.apk /system/app/
Click to expand...
Click to collapse
Tips & Tricks
Taking Screenshots
Taking screenshots on Android devices is a pain, but on the Galaxy S2, you can simply hold down the home button and then briefly press the power key to take a screenshot. You can then see your screenshots in the Gallery.
Adjusting Brightness with Notification Bar
The notification bar can serve as a brightness scroll on the Galaxy S 2, if you are not using the automatic brightness option. Just hit the notification bar, hold for a second and swipe left to decrese and right to increase the brightness.
Browser Text Wrapping
Out of the box the Galaxy S2 doesn’t automatically reflow the text in the webpage if you zoom in. But if you just goto settings and check the ‘auto-fit pages’ option, all is well again.
Changing User Agent
The SGS2 browser lets you change the user-agent without needing an extra app, just type ‘about:useragent’ in browser's location bar and you can choose between the iPhone, Nexus One, Desktop, Galaxy S or even enter a custom string.
Test Mode
Dialing *#0*# in the dialer enters the LCD test mode, useful if you are looking for for dead pixels, debugging sensors and other hardware parts of your SGS2.
Search Key
Although SGS2 like the SGS doesn’t have a dedicated search key that all other Android devices have, but if you long press menu, it launch the search screen, anywhere you'd need it.
Video Screen Lock
Pressing the power button while video player is playing locks the screen, now you can hold the device any way you like, no more accidental presses will happen. To unlock, just press the power button again.
Customizing App Launcher Bar
If you would like to change applications shortcuts in bottom application launcher bar, press the Applications button, then Menu -> Edit. You can then rearrange those shortcuts or replace them with other applications or remove them completely. There's limita of maximum 3 shortcuts and the Home button will always be there.
Changing USB to File Transfer Mode
When you connect USB cable, SGS2 mounts it's file system read-only and transfering files between PC and handset is possible with Kies only. To change this behavior to normal read-write USB file transfer mode, go to Settings -> Applications -> Development and enable USB debugging.
User interface
Scrolling:
- Use two fingers to scroll until fingers are released.
- Use three fingers to scroll fast until top/bottom.
Phone wake up: Via home or power.
Hold menu: Quick access Android search.
Dobule click home: Quick access voice commands.
Screenshot: Press home and power simultaneously. Screenshots are saved in /sdcard/ScreenCapture/
Home screen
Multiple home screens: Touch the dots to switch directly to a screen or hold and drag left/right to scroll very fast.
Changing shortcuts at the bottom: Click „Applications“ (bottom right), then menu, click „Edit“: Now change the three (left) icons via drag & drop. Afterwards click menu and choose „Save..“.
Quick brightness change: Hold the notification bar (on the top) and drag left/right to modify brightness (if not set to auto).
Pinch home screen to view all home screens and add/delete them.
Pinch application screen to view all application screens and reoder them.
Set background image for lock screen: When changing your desktop background image, there are two buttons, choose the right one (smaller area) and save. Now you‘ll be asked to use this image for the lockscreen too.
Android Apps
E-Mail: Pinch in the overview list to fold/unfold by date.
E-Mail: Click longer on a date (either the sent date or a date in the email text): Create a new calendar event for this date.
Contacts: Drag left over a contact to send SMS, drag right to call
Keypad: Use the letters on number keys to type a name, the triangle on the right shows how many matching contacts are found, clicking on it reveals them.
Camera: Change shortcut buttons by clicking menu, “Edit”, then modify shortcut buttons via drag&drop.
Camera: Pinch to zoom in/out.
Browser: Pinch to view all tabs/windows.
Browser: Go to “about:debug” via address bar. Now you have additional options when pressing the menu (at the bottom)
Browser: Go to “about:useragent” via address bar. Now you can modify the user agent string.
Video player: Drag left/right to Fast forward/Rewind
Video player: Power locks/unlocks the screen
Calendar: Pinch in month view to get an overview, swipe left/right to change the year.
Easter egg from Google: Go to preferences, about phone, click some times on “Android Version” (try multiple times)
[DIY] Do it yourself guides:
Reset Galaxy S II
Warning: All your data including contacts, messages will be lost!
Hard Reset:
Press and Hold Volume Up + Home button.
Keep pressing these two and press Power button for 2-3 seconds.
Release only power button. But keep pressing Volume UP + Home buttons.
Now, with Volume down, select wipe data/facotory reset (3rd)
Press Power
Useful Codes:
*#0*# LCD Screen test
*#06# Show IMEI Number
*#2222# HW Version
*#1234# Phone info
*#34971539# Camera Firmware
*#9900# Sysdump (Logfiles etc.)
*#0228# Battery diagnostics
*#7284# Phone utility
*#7353# Function testing
*#9090# Service Mode
*#*#197328640#*#* Service Mode Menu
*2767*3855# Factory Reset
Complete Codes Collections for SGS II and should work with other Samsung droids many of them.
Warning: Please use with caution
1 #*#8377466# S/W Version & H/W Version.
2 #*0227# GPRS Switch.
3 #*0277# GPRS Switch.
4 #*2027# GPRS Switch.
5 #*2077# GPRS Switch.
6 #*2252# Current CAL.
7 #*2255# Call Failed.
8 #*2256# Calibration info? (For CMD set DEBUGAUTONOMY in cihard.opt)
9 #*22671# AMR REC START.
10 #*22672# Stop AMR REC. (File name: /a/multimedia/ sounds/voice list/ENGMODE.amr)
11 #*22673# Pause REC.
12 #*22674# Resume REC.
13 #*22675# AMR Playback.
14 #*22676# AMR Stop Play.
15 #*22677# Pause Play.
16 #*22678# Resume Play.
17 #*22679# AMR Get Time.
18 #*2286# Databattery.
19 #*2337# Permanent Registration Beep.
20 #*2351# Blinks 1347E201 in RED.
21 #*2474# Charging Duration.
22 #*2527# GPRS switching set to (Class 4, 8, 9, 10)
23 #*2558# Time ON.
24 #*2562# Restarts Phone.
25 #*2565# No Blocking? General Defense.
26 #*2677# Same as 4700.
27 #*2679# Copycat feature Activa/ Deactivate.
28 #*2775# Switch to 2 inner speaker.
29 #*2787# CRTP ON/OFF.
30 #*2834# Audio Path. (Handsfree)
31 #*2836# AVDDSS Management Activate/ Deactivate.
32 #*2886# AutoAnswer ON/OFF.
33 #*3270# DCS Support Activate/ Deactivate.
34 #*3273# EGPRS multislot. (Class 4, 8, 9, 10)
35 #*3282# Data Activate/Deactivate.
36 #*3353# General Defense, Code Erased.
37 #*3370# Same as 4700.
38 #*3476# EGSM Activate/Deactivate .
39 #*3676# FORMAT FLASH VOLUME!!!
40 #*3725# B4 last off.
41 #*3728# Time 2 Decod.
42 #*3737# L1 AFC.
43 #*3757# DSL UART speed set to. (LOW, HIGH)
44 #*3837# Phone Hangs on White screen.
45 #*3838# Blinks 3D030300 in RED.
46 #*3838# Blinks 3D030300 in RED.
47 #*3849# Restarts Phone.
48 #*3851# Restarts Phone.
49 #*3876# Restarts Phone.
50 #*3877# Dump of SPY trace.
51 #*3888# BLUETOOTH Test mode.
52 #*3940# External looptest 9600 bps.
53 #*3941# External looptest 115200 bps
54 #*4263# Handsfree mode Activate/ Deactivate.
55 #*4472# Hysteresis of serving cell: 3 dB
56 #*4700# Please use function 2637.
57 #*4760# GSM Activate/Deactivate.
58 #*4773# Incremental Redundancy.
59 #*4864# White Screen.
60 #*5133# L1 HO Data.
61 #*5171# L1P1.
62 #*5172# L1P2.
63 #*5173# L1P3.
64 #*5176# L1 Sleep.
65 #*5187# L1C2 G trace Activate/ Deactivate.
66 #*5376# DELETE ALL SMS!!!!.
67 #*5737425# JAVA Mode.
68 #*6833# New uplink establishment Activate/Deactivate .
69 #*6837# Official Software Version: (0003000016000702)
70 #*7200# Tone Generator Mute.
71 #*7222# Operation Typ: (Class C GSM)
72 #*7224# !!! ERROR !!!
73 #*7252# Operation Typ: (Class B GPRS)
74 #*7271# CMD: (Not Available)
75 #*7274# CMD: (Not Available)
76 #*7284# L1 HO Data.
77 #*7287# GPRS Attached.
78 #*7288# GPRS Detached/Attached .
79 #*7326# Accessory.
80 #*7337# Restarts Phone. (Resets Wap Settings)
81 #*7352# BVMC Reg value (LOW_SWTOFF, NOMINAL_SWTOFF)
82 #*7372# Resetting the time to DPB variables.
83 #*7462# SIM Phase.
84 #*7524# KCGPRS: (FF FF FF FF FF FF FF FF 07)
85 #*7562# LOCI GPRS: (FF FF FF FF FF FF FF FF FF FF FF FE FF 01)
86 #*7666# White Screen.
87 #*7683# Sleep variable.
88 #*7693# Sleep Deactivate/Activate .
89 #*7722# RLC bitmap compression Activate/Deactivate .
90 #*77261# PCM Rec Req.
91 #*77262# Stop PCM Rec.
92 #*77263# PCM Playback.
93 #*77264# PCM Stop Play.
94 #*7728# RSAV.
95 #*7732# Packet flow context bit Activate/Deactivate .
96 #*7752# 8 PSK uplink capability bit.
97 #*7785# Reset wakeup & RTK timer cariables/variables.
98 #*7828# Task screen.
99 #*7878# FirstStartup. (0 NO, 1 YES)
100 #*7983# Voltage/Freq.
101 #*7986# Voltage.
102 #*8370# Tfs4.0 Test 0.
103 #*8371# Tfs4.0 Test 1.
104 #*8372# Tfs4.0 Test 2.
105 #*8373# Tfs4.0 Test 3.
106 #*8374# Tfs4.0 Test 4.
107 #*8375# Tfs4.0 Test 5.
108 #*8376# Tfs4.0 Test 6.
109 #*8377# Tfs4.0 Test 7.
110 #*8378# Tfs4.0 Test 8.
111 #*8379# Tfs4.0 Test 9.
112 #*8465# Time in L1.
113 #*8466# Old Time.
114 #*8724# Switches USBACM to Generator mode.
115 #*8725# Switches USBACM to Loop-back mode.
116 #*8726# Switches USBACM to Normal.
117 #*8727# Switches USBACM to Slink mode.
118 #*9270# Force WBS.
119 #7263867# RAM Dump. (On or Off)
120 *#*#4636#*#* Access Phone/Battery/Usage Stat/WiFi Info
121 *#0*# Access Sensor/LCD Screen Test/ Vibration/ Camera/ Speaker etc test
122 *#0011# ServiceMode/Debug /Basic
123 *#06# IMEI Number.
124 *#1234# Firmware Version.
125 *#2222# H/W Version.
126 *#2255# Call List.
127 *#232337# Bluetooth MAC Adress.
128 *#4777*8665# GPSR Tool.
129 *#5282837# Java Version.
130 *#8999*327# EEP Menu.
131 *#8999*364# Watchdog ON/OFF.
132 *#8999*377# Error Menu.
133 *#8999*427# WATCHDOG signal route setup.
134 *#8999*523# LCD Brightness.
135 *#8999*667# Debug Mode.
136 *#8999*8376263# All Versions Together.
137 *#8999*8378# Test Menu.
138 *#92782# PhoneModel. (Wap)
139 *2767*226372# E2P Camera Reset. (deletes photos)
140 *2767*2878# E2P Custom Reset.
141 *2767*3855# E2P Full Reset.
142 *2767*688# Reset Mobile TV.
143 *2767*927# E2P Wap Reset.
Useful Links
-Debrand & Rebrand back to O2 for Samsung Galaxy S2
-Permanently Fix SGS2 Echo and Digital Noise Reduction/Cancellation Problems
-Back up your data before moving to a new rom
-Recover your IMEI in 9 steps.
-Battery Saving Tips Collection
Mods:
-add customizable 14 statusbar toggle buttons for samsung ROM
-Long press volume buttons to skip songs.
-Manually Deodex and Odex back
-Learn to make your own 'eye-candy' mods [Easy Steps]
Tools:
-EFS Pro v1.2.6 - Advanced '/efs' Backup and Restore!
Patches:
-Add native android SIP stack for Wifi AND 3G calls
-Extended Power Menu with no header (reboot / download / recovery)
Speechless lol. Well done though.
looks like an iphone but powered by android baby!!!!
This should be a sticky thread
androidkid311 said:
Speechless lol. Well done though.
looks like an iphone but powered by android baby!!!!
Click to expand...
Click to collapse
Thanks for feedback. Can you explain what iphone thing you have mentioned?
anshmiester78900 said:
This should be a sticky thread
Click to expand...
Click to collapse
Thanks feedback like these will encourage me to do more.
Bloody hell. Made good reading while I was having a dump.: D I say sticky time. I mean sticky thread
Sent from my ICS blood mode S2
sekhargreen said:
Thanks for feedback. Can you explain what iphone thing you have mentioned?
Click to expand...
Click to collapse
Think that is his signature.
Nice posts! But you STILL didn't explain how to make the godamn ROM. All I saw was how ROM makers should be bla bla. I didn't see anywhere how to make the godamn .zip file.
That is awesome. Please continue.
Such efforts must be awarded.
Nice one mate!
This was really a good read
nice ****load of tweaks, but they are useless if you dont define and explain what each of them do.
good work though, keep it up!
even the real bible don't have this much reservations in this forum ...
and waiting for it...
Awesome thread mate... defo sticky material!
Fantastic post
This should be a sticky thread. Helped me with a lot of those... Thank you
Thank you for for this great and nice job/sharing, it's good to know even more about the stuffs that what we are dealing with..!
Best regards!
Fail to understand what is the point of this thread. Lots of preaching and shallow stuff. Sorry.
<< New in version 6: Smoother touch with kinetics, basic theme support, KitKat ready, MTK devices support >>
End Of Support
Project Status: No Longer Updated
As I mentioned before, I have a lot of new important projects in my real life. I am very happy to abandon this project for real life alternatives.
CWM is a dead project for now, until some dev resurrects it. I was about to do, until these new projects came.
Current version will probably work a while for many devices. Some devices with new ROM installers could have issues. Just use TWRP and avoid the new CM Simple Recovery
If the current version works for you, there is no reason you don't use it though. No need to ***** in all threads because it doesn't work for you. Just move on to other alternatives.
Click to expand...
Click to collapse
* * * * * * * * * * * * * * * * * * * * * * * * *
PhilZ Touch 6 Recovery
CWM Advanced Edition 6.x
* * * * * * * * * * * * * * * * * * * * * * * * *
Support clockworkmod developement
>> Developers Info + Device Request <<>> Special Features Guide <<>> How to Install <<>> Change Log <<>> FAQ <<
Download Home
https://mega.co.nz/#F!oZ1QDDbC!Ko20UNhowwIlXLVFjJsyKw
Older versions:
http://d-h.st/users/philz_touch
Specific Devices Threads
All general requests for these devices must go into their threads
Keep this thread for dev support and porting to new devices
Amazon
- Kindle Fire HD 8.9 (jem)
- Kindle Fire HD 7 (tate)
Android
- One (sprout) by @varun.chitre15
Asus
- Asus Transformer Pad TF300T (tf300t)
- Asus Transformer Prime TF700T (tf700t)
HTC
- HTC Evo 3D (shooteru) by @johnnyslt
- HTC Desire X (protou)
- HTC DROID Incredible 4G LTE (fireball)
- HTC Explorer (pico)
- HTC One GSM (m7ul --> m7)
- HTC One T-Mobile (m7tmo --> m7)
- HTC One AT&T (m7att --> m7)
- HTC One Sprint (m7spr)
- HTC One Verizon (m7vzw)
- HTC One M8 (m8): unified for International, Verizon and Sprint
- HTC One Mini (m4)
- HTC Droid DNA (dlx)
- HTC Desire 601 (zara)
- HTC Desire 601 dual sim (zaradug) by @andreya108
- HTC Desire S (saga) by @Ruling
- HTC Desire HD (ace) by @Ruling
- HTC One S (ville)
- HTC One V (primou)
- HTC One X (endeavoru)
- HTC One X+ (enrc2b)
- HTC One XL (evita)
- HTC Evo 4G LTE (jewel)
- HTC Rezound (vigor)
- HTC Desire 816 (a5) by @v_superuser
Google
- LGE Nexus 4 (mako)
- LGE Nexus 5 (hammerhead)
- ASUS Nexus 7 (tilapia + grouper)
- ASUS Nexus 7 2013 (flo)
- ASUS Nexus 7 2013 LTE (deb)
- Samsung Nexus 10 (manta)
- Samsung Galaxy Nexus - GSM (maguro)
- Samsung Galaxy Nexus - Verizon (toro)
- Samsung Galaxy Nexus - Sprint (toroplus)
- Samsung Galaxy Nexus S (crespo)
- Samsung Galaxy Nexus S 4G (crespo4g)
LGE
- LG Optimus One P500 (p500)
- LG Optimus L5 (e610)
- LG Optimus G International (e975)
- LG Optimus G ATT (e970)
- LG Optimus G Sprint (ls970)
- LG Optimus G Canada (e973)
- LG Optimus G Pro GSM (e980)
- LG Spectrum 4G (vs920)
- LG G2 AT&T (d800), TMO (d801), Int (d802), d803, d805, d806, Verizon (vs980), Sprint (ls980)
- LG Nitro HD AT&T (p930)
- LG G Pad 8.3 (v500)
- LG Optimus 4X HD P880 (p880)
- LG Optimus L7 P700 (p700) by @ali.filth
Motorola
- Motorola Droid RAZR M (xt907)
- Motorola Droid RAZR HD International (xt925) and US (xt926)
- Motorola Unified msm_8960 (xt925/xt926)
- Motorola Atrix HD (mb886)
- Motorola Moto X variants: TMO (xt1053), US Cellular (xt1055), Sprint (xt1056), GSM (xt1058), VZW (xt1060)
- Motorola Moto G unified (falcon) for: Verizon (xt1028), BoostMobile (xt1031), GSM (xt1032), Dual Sim (xt1033), Retail US (xt1034)
Oppo
- Find 5 (find5)
- Find 7, Find7a (find7)
- N1 (n1)
Samsung
- Galaxy S2 i9100/P
- Galaxy S2 Epic 4G Touch - SPH-D710 (d710)
- Galaxy S2 i9100G
- Galaxy R/Z (i9103)
- Galaxy S i9000 (galaxysmtd)
- i9001 - Galaxy S Plus (ariesve)
- Galaxy S Captivate (captivatemtd) by @brandonabandon
- Galaxy Grand Duos (i9082)
- Galaxy Exhibit - SGH-T599N (codinamtr)
- Galaxy W i8150 (ancora)
- Galaxy Grand Quatro I8552 (delos3geur) by @ali.filth
- Galaxy S 2 Skyrocket SGH-I727 (skyrocket)
- Galaxy S Blaze 4G - SGH T769 (t769)
- Galaxy S2 HD LTE - SGH-I757M (celoxhd)
- Exhilarate - SGH-I577 (exhilarate)
- N7000
- Galaxy S3 i9300 - i9305
- Galaxy S3 Unified d2 variants (d2lte): d2att d2cri d2mtr d2spr d2tmo d2usc d2vzw
- Galaxy S3 T-Mobile / SGH-T999 (d2tmo)
- Galaxy S3 AT&T (d2att)
- Galaxy S3 Sprint (d2spr)
- Galaxy S3 Verizon (d2vzw)
- Galaxy S3 Mini GT-I8190 (golden) by @Android-Andi
- Galaxy S Relay 4G - SGH-T699 (apexqtmo)
- Galaxy Express AT&T (expressatt)
- Galaxy S4 Exynos - i9500
- Galaxy S4 Unified Qualcomm variants (jflte): jfltecan jflteatt jfltecri jfltecsp jfltespr jfltetmo jflteusc jfltevzw jgedlte jfltexx jfltezm
- Galaxy S4 - i9505 (jfltexx --> jfltejflte)
- Galaxy S4 - T-Mobile (jfltetmo --> jflte)
- Galaxy S4 - Verizon (jfltevzw --> jflte)
- Galaxy S4 - AT&T (jflteatt --> jflte)
- Galaxy S4 - Sprint (jfltespr --> jflte)
- Galaxy S4 Mini i9190 (serrano3gxx), i9192 (serranodsub) and i9195 (serranoltexx)
- Galaxy S5 International (kltexx --> klte)
- Galaxy S5 Exynos SM-G900H (k3gxx)
- Galaxy Mega i9205 (meliusltexx)
- Galaxy Mega i9200 (melius3gxx)
- Galaxy Premier i9260 (superior)
- Galaxy Note 2 (N7100 - N7102 - N7105 (t0lte)
- Galaxy Note 2 LTE Sprint SPH-L900 (l900)
- Galaxy Note 2 LTE Verizon SCH-I605 (i605)
- Galaxy Note 2 AT&T (t0lteatt)
- Galaxy Note 2 - TMO (t0ltetmo)
- Galaxy Note 3 LTE International - N9005 (hltexx)
- Galaxy Note 3 T-Mobile (hltetmo)
- Galaxy Note 3 Sprint (hltespr)
- Galaxy Note 3 Verizon (hltevzw)
- Galaxy Note 3 Canada (hltecan)
- Galaxy Note 4 International (trltexx), credits @Chenglu
- Galaxy Note 10.1 - N80xx
- Galaxy Note 10.1 - 2014 Wifi (lt03wifi), 3G (lt03wifiue)
- Galaxy Note 8.0 (N51xxx)
- Galaxy Tab 2 7.0 (p31xx)
- Galaxy Tab 2 10.1 (p51xx)
- Galaxy Tab 3 7.0: SM-T210 WiFi (lt02wifi) - SM-T111 3G (lt023g)
- Galaxy Tab 3 8.0 (lt01wifi, lt013g, lt01lte)
- Galaxy Core - GT-I8262 (arubaslim) - by @ali.filth
- Galaxy Mini (tass)
- Galaxy Gio (gio)
- Galaxy Fit (beni)
- Galaxy Ace (cooper)
- Galaxy 5 (galaxy5)
- Galaxy 551 (callisto)
- Galaxy Tab Pro 8.4 WiFi SM-T320 (mondrianwifi)
Sony
- Xperia Z (yuga)
- Xperia Z1 (honami)
- Xperia Z2 (sirius) - by @DooMLoRD
- Xperia Z Ultra (togari)
- Xperia SP (huashan)
- Xperia T (mint)
- Xperia ZL (odin) - by @shoey63
- Xperia L (taoshan) by @varun.chitre15
- Xperia M (nicki) by @icoolguy1995
ZTE - maintained by @cooldudezach
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
- Warp Sequent - N861 (warp2)
- Warp 4G (warplte)
- Awe (nex)
- Overture (becky)
- Imperial (apollo)
- Source (hera)
- Iconic Phablet (stormer)
- Radiant (metis)
Huawei
- Acsend P1 U9200 (viva)
MicroMax
- A56/A57
- A110Q (unofficial repack by @sukarang9)
- A110 @bindassdost
- A177 Canvas Juice
- A310 Canvas Nitro by @thedevilashish
Cubot
- Cubot One (unofficial repack by @Maximus1a)
OnePlus
- One (bacon) by @acer73 and @katinatez
Xiaomi
- RedMi 1s (armani) by @juliusssss
- RedMi Note 4G (dior) by @juliusssss
- Redmi Note 3G by @EndLess
- Redmi 2/2A/Prime by @Rohan Taneja
Xolo
- Opus 3 by @thedevilashish
- A500S by @EndLess
PhilZ Touch Features: Read POST 2 for instructions to use special functions like aroma and ors support
touch interface:- toggle between 4 touch modes: FULL TOUCH, DOUBLE TAP to validate, SEMI TOUCH (scroll but no touch validation) and NO TOUCH to only use hardware keys
- written from scratch full touch code
- basic scroll kinetics for faster scrolling on demand
- safe full touch : no wrongly validations while scrolling
- when you set full touch mode, it defaults to optimized settings for menu height, scroll sensitivity and touch accuracy (you still can alter them manually later)
- adjust scroll sensitivity in a huge palette
- adjust menu height in a huge palette
- adjust touch accuracy
- 30 color settings for each of the 8 GUI parts + 5 alpha transparency settings
- user custom background png can be selected in addition to 30 solid colors option
- show / hide background icon
- show / hide bottom virtual buttons
- show/hide + set color and transparency for menu line separators to match solid color themes, like Black...
- set number of bottom log rows to show
- pause on logs mode: no more miss logs during zip installs
- auto dim screen after user configurable delay
- auto turn off screen after user configurable delay
- adjust brightness and turn off screen with a gesture action
- show/hide clock and remaining battery %, even during nandroid operations
- clock and battery stats now effectively refresh every 5 seconds and during nandroid operations
- toggle vibrator on/off on touch
- toggle key repeat for volume up/down scrolling when maintained pressed
- key repeat also enabled for virtual buttons
- set time zone + 30mn offset + DST: correct time can now be set for nandroid backup path and clock
- capture recovery screen shots with a gesture action (only some devices)
- basic theme support
- one file to save all settings
- backup and restore settings file
- backup and restore only GUI settings
- reset to default settings option
- prompt to restore your settings from a backup when they are wiped by a new ROM install
- option to auto restore your settings from a backup without a prompt
- all toggles are applied live, without restart of recovery (except reset of stock CWM background image)
- toggle menu options are automatically right aligned and menu text left aligned based on device display size
- configurable gesture actions: double tap, slide right/left, long press/lift, long press/move, can be associated with any of: show log, change brightness, blank screen, capture screen shot, launch Aroma File ManagerNote: after scroll, there is a minimal small delay (0.5 sec) to validate on next touch. This is by design and not a bug. It is there to limit erroneous validation while scrolling
true JB 4.2 migration: toggle between /data/media and /data/media/0
Secure recovery lock with passkey
browse phone with root access using full GUI in Aroma File Manager
terminal access from recovery with root access through Aroma File Manager
Multi Zip Install menu: check multiple zip files to install in a row
Custom Install Zip Mode: set a default folder to start with + browse backward up to the root
exFAT, NTFS and Ext4 support in recovery for external storage through kernel modules for many devices for faster write speed
TWRP backup and restore support, include full md5 sum support (single and multivolume, compressed and non compressed formats)
Advanced statistics during backup operations shown in color: total backup size, backup size progress, backup time, compression ratio...
support .android_secure backup/restore from external storage
optional reboot after custom backups/restores
sd-ext support (ext4)
nandroid backups support /preload in backup and restore jobs (custom and stock modes)
nandroid backups support /misc in backup and restore jobs (custom mode)
devs: 5 extra optional partitions supported in nandroid operations by editing recovery.fstab
set special nandroid settings: time zone, toggle md5 check for lightning fast backup and restore, toggle /preload backup and restore, enable nandroid compression using pigz (multi-cpu gzip compression) and choose ors backup target volume
recreate md5 sum check for your cwm backups for compatibility with stock CWM if you need to revert
cancel nandroid operation with back button
create custom_rom.zip from current ROM or from a pre-existing nandroid backup (based on boot, /system and optionally /preload)
nandroid backup path auto-renamed with current ROM id from build.prop (ro.modversion, then ro.romversion, then ro.build.display.id)
custom backup and restore job list: backup and restore freely any partition combo (include modem and efs)
backup/restore EFS in both tar + img formats, now with time tags for both tar and .img
support flash modem.bin image files in addition to custom modem.img files, now support for multiple *.bin versions under dedicated folder
during custom restore, you can see the contents of the folder you want to restore from
delete custom or TWRP backups from recovery menu
full wipe before flashing new ROM: wipe user data + format /system and /preload. SD card content is not affected
full support for openrecovery script specifications include all backup and restore options
run openrecovery scripts in 2 modes: on start goomanager boot scripts + one touch menu to either directly open a default path or freely browse for scripts
define ors backup target volume from within Nandroid Settings menu
ors backup/restore in stock clockworkmod or TWRP modes
advanced power options menu
detailed build info in About menu
Click to expand...
Click to collapse
Video Teaser:
new update soon...
Main menu and PhilZ Settings
{
"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"
}
GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...
27 color settings + 5 alpha transparency levels for every GUI element
Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original cwm image
User configurable touch gestures (feel free to request for new actions)
Setup your time-zone + 30mn offset, super wipe option to install a new ROM
Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can also be restored by original CWM Advanced Restore Menu
TWRP Backup and Restore Support + md5 + single/multivolume format
Support multi-cpu compression, md5 check toggle and custom .android_secure path
Choose ors backup volume target
Flash multiple zip files in a raw
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)
Full Wipe to Install a new ROM (sdcard is preserved)
Free Browse Mode to install zip files: select a default folder to start with and browse up to the root
Enjoy, and do not hesitate to post feedbacks and comments
Credits
To ALL people who help in porting device sources and give feedback for debugging
A special thank also to the below, and ALL who I do not mention but did contribute a lot with their efforts
Koush for having created and maintaining cwm
Cyanogenmod for making all this possible
Tallustus from Team Skyfire for his great support over IRC: MAJOR CREDITS
Dees_Troy from TWRP team for pigz source and many great ideas in their recovery + source for backups compatibility
Chenglu for his unpacking tools and porting i9505: Huge credit
kbc-developers for the base semi-touch code and much more
[email protected] for his great job / support
sk8erwitskil for his recovery source, a great place to start learning
shoe63 for his help from the start across many devices
DooMLoRD for his work and help with Sony
[NUT] for his ports to Sony
wanam for compiling sensors-free kernels for N71xx/i317M, i9500 and i9505 to fix boot delay for custom kernels, exfat support and much more
dougiebee for his work on fixing time on many Qualcom devices
ausdim for all the support in developing kernels for i9505
dr.ketan for his precious help in porting to the N7000 & N7100 (I don't own one) and all the support in threads
Chainfire for his support (stock recovery flash) and all his work for the Android community
XDA:DevDB Information
PhilZ Touch - Advanced Clockworkmod, Tool/Utility for the Android General
Contributors
Phil3759
Source Code: https://github.com/PhilZ-cwm6/philz_touch_cwm6
Version Information
Status: No Longer Updated
Created 2014-03-29
Last Updated 2016-01-05
Developers info: ** New: you can now build full version from my git sources **
You can also try to get support on IRC on freenode: #PhilZ-Touch (thanks @Bhargav97)
You can fetch source from this link (cm-11.0 branch):
https://github.com/PhilZ-cwm6/philz_touch_cwm6
I no longer maintain the older branches
Before you start, make sure you can build stock cwm from cm-11.0 source
Once you can build stock CWM, just replace your bootable/recovery folder with this one and lunch for your device
Device tree changes examples:
They are minimal and detailed below
You can see a few examples from here:
device tree: https://github.com/PhilZ-cwm6/philz_touch_cwm6_device_vendor/tree/cm-11.0
vold exfat/ntfs/f2fs kernel support: https://github.com/PhilZ-cwm6/android_system_vold/tree/cm-11.0
selinux extensions for extra partitions: https://github.com/PhilZ-cwm6/android_external_sepolicy/tree/cm-11.0
To avoid modifying BoardConfig.mk and device.mk for all devices I support, I modified the build makefile:
https://github.com/PhilZ-cwm6/android_build/tree/cm-11.0
Those are the only optional changes to get all features of this recovery mod.
To use f2fs/exfat/ntfs kernel support, you should learn how to modify the kernel too. Else, skip the vold changes and flags (see below details)
Optional PhilZ Touch extra flags:
The below info are optional. You should still be able to build without editing anything in device tree
bootable/recovery/boardconfig/BoardConfig.mk
It is a quick mode to add device specific tags without altering device tree. That way I can spot needed changes easier.
Code:
# Info on some tags:
- KERNEL_EXFAT_MODULE_NAME: This will force minivold to use much faster kernel modules instead of slow fuse
it will only work if you have modified vold sources (contact me for info)
you'll also have to copy modules to ramdisk and load them in init.rc or a loader script
you need either an exfat enabled prebuilt kernel or to compile exfat modules along kernel
you also need to patch minivold: [url]https://github.com/PhilZ-cwm6/android_system_vold[/url]
- KERNEL_NTFS_MODULE_NAME:
Same as above, but for ntfs.
- TARGET_USERIMAGES_USE_F2FS := true
will enable f2fs support and ext4 <-> f2fs conversion and backup migration
obviously you need to add f2fs support into the kernel
read about the extra.fstab use to use specific and distinct f2fs and ext4 mount options
else, it will drop to bare minimal ext4 or f2fs mount options if not defined in recovery.fstab
- BOARD_USE_MTK_LAYOUT := true
will enable backup/restore of boot, recovery and uboot partitions on MTK devices
- BOARD_MTK_BOOT_LABEL := "/bootimg"
This flag is optional, it is used only if BOARD_USE_MTK_LAYOUT is defined
If not defined while previous flag is enabled, default boot label is assumed "/bootimg"
Else, it is assigned the defined value
In fstab.device used by recovery (recovery.fstab), boot mount point must be the same as what we
define in label
It is also mandatory that it is defined to real device label (cat /proc/dumchar_info)
Partition size is grabbed during backup/restore from /proc/dumchar_info
uboot label is defined as "/uboot". It is automatically backed-up/restored with boot and recovery
recovery label is always assumed to be "/recovery"
- BOARD_HAS_LOW_RESOLUTION:
(optional) for all devices below 1024x768 resolution.
it forces default touch sensitivity to a lower value. It can be altered in GUI Settings
- BOOTLOADER_CMD_ARG:
This will override ro.bootloader.mode. Mostly used for Samsung devices to access download mode
- TARGET_COMMON_NAME
The device name that will be displayed on recovery start and in About dialogue
- BRIGHTNESS_SYS_FILE:
Needed to be able to alter screen brightness
- ro.cwm.backup_partitions:
this can be set on boot or during compile into default.prop. exp in device.mk:
PRODUCT_PROPERTY_OVERRIDES += \
ro.cwm.backup_partitions=/modemst1,/modemst2,/devlog
it will add support to backup/restore those partitions in nandroid custom jobs provided they are also defined in recovery.fstab
device/brand/phone_name/device.mk
Code:
PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/rootdir/etc/extra.fstab:recovery/root/etc/extra.fstab
extra.fstab documentation:
* Needed until fs_mgr_read_fstab() starts to parse blk_device2 entries
* extra.fstab sample:
Code:
# add here entries already existing in main device fstab, but for which you want a blk_device2, fs_type2 or fs_options2
# mount point must be the same, mmcblk device must be your device true path
# you can set the f2fs mount options for partitions you want to be able to toggle between f2fs/ext4
# it will enable faster transfer speed for devices supporting usb mount storage
# makes it possible to partition vold managed storage (sdcard/usb disks) and format it to ext2/ext3
# used also to stat for size of mtd/yaffs2 partitions
# blk_device2 # mount_point fs_type2 fs_options2 flags (not used in extra.fstab code)
/dev/block/mmcblk0p28 /storage/sdcard0 auto defaults defaults
/dev/block/mmcblk1p1 /storage/sdcard1 auto defaults defaults
/dev/block/sda1 /storage/usbdisk0 auto defaults defaults
/dev/block/mmcblk0p30 /data f2fs [options] [flags]
If it doesn't build or errors, post log/error here and I will help if I can
Adding Full PhilZ Touch version support for your device
Compile for your device by replacing bootable/recovery contents with files from my git
Set the needed options in bootable/recovery/boardconfig/BoardConfig.mk
It is very important to set the correct options so that libtouch_gui can be initialized properly
Optional: you can add your signature here, but do not remove other About ui_prints please, keep credits
https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0/advanced_functions.c#L3328
post a link to your thread or attach your recovery.img here and I will upload them to goo.im and main OP for official support
If you have errors, bugs or need a specific feature for your custom kernel, just let me know by PM
If errors are related to libtouch_gui, try to disable the PHILZ_TOUCH_RECOVERY flag here by adding a #
https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0/Android.mk#L6
Then, post here your error log when compiling
Click to expand...
Click to collapse
Missing sources in my github:
none, it is all open source now
- all gui options, include touch code
- Create Update.zip from current ROM or from pre-existing backups
- However, they are all enabled through the new libtouch_gui library. Just set your flags and compile it
Will libtouch_gui sources published?
They are open source now
Not for now. Why?
Answer: in this post
Can I include and use your libtouch_gui in my recovery mod ?
You are welcome, but:
- do not reverse code
- do not binary edit it
- add credits in your code
- do not remove credits headers from sources and give proper credit in your thread site
- post a link to this thread on your site/thread
- push fixes to my github if you find bugs that you fix or if you add new features
PhilZ Touch Quick Guide
It is based on Koush clockworkmod 6.x to which I added many features and a full reliable touch interface
It brings a true touch and scroll interface, fully customizable GUI, theme support, advanced nandroid options and much more
How to select your .android_secure path
In Custom Backup and Restore operations, you can select the target/source for android.secure or disable it
In stock backup/restore operations, include those started with ROM Manager, you can also force a target/source for .android_secure
basically, recovery will check first external storage for a .android_secure folder. If it doesn't find it, it will look in internal storage
If you want for example .android_secure to be in internal sd, just delete .android_secure folder from external sd and ensure there is a .android_secure folder in internal sd
for external sd, just ensure there is a .android_secure folder in it. It will be chosen what ever is the internal sd state
Custom Backup and Restore menu
This is one of the most powerful features of this recovery.
It is made completely open source code, built from sratch. Just keep credits headers and give proper credit if you use them
You can select which partitions you want to backup or restore
You can choose your .android_secure source and target or even disable it
You can set it to reboot directly after job is done
backups will go under the folder clockworkmod/backup (please move all contents of custom_backup folder used in previous versions to the default backup folder in cwm)
TWRP backups go under stock TWRP/BACKUPS/device_id folder and will be automatically recognized by TWRP
Custom Restore Menu allows you to restore from any of the stock clockworkmod backups, the custom backups or the TWRP backups
efs is backed up under clockworkmod/backup/.efs_backup
- efs must be selected alone for backup in cwm mode
- it will create 2 copies: a tar and raw img backup using cat/dd command
- to restore efs, under Custom Restore menu, select efs only and toggle between tar and .img
- restore .img format is advised, but tar will work under most circumstances
modem.bin files can be named any_thing.bin and must go under clockworkmod/backup/.modem_bin
- with that, you can flash modem.bin files that come with official firmware (may need unlocked devices for some models)
if you disable md5, your backups will no more be recognized by stock cwm builds. Look at next step to regenerate md5 for stock cwm compatibility. Otherwise, all stock and custom backups are backward compatible with stock cwm (except special partitions like preload, recovery, modem and efs which stock cwm doesn't support)
you can now recreate md5 sum for any backup you want. Use with caution!
Open Recovery Script Support (ORS): revised and adapted from original sk8erwitskil source
On start, recovery looks automatically for "/cache/recovery/openrecoveryscript" installed by goomanager or any tasker. If it finds it, it is run and phone will reboot
You can also add custom ors scripts you edit your self:
When pressing the ors menu, it will look at default locations for your custom scripts:
"clockworkmod/ors" first in extra storage, then in internal sd. Put your custom scripts there with file extension .ors
That way you can access your jobs (flash, wipe, backup, restore...) instantly
If no scripts are found in default folder, you get option to browse both storage volumes for a custom location
To learn how to write ors scripts to automate your backup/restore/wipe/flash tasks, read here, it is very easy: http://wiki.rootzwiki.com/OpenRecoveryScript
Give Goomanager a try
All backup and restore options are supported include special partitions 1, 2 and 3 and even extra 4 and 5 partitions (could add modem, efs and preload linked to them later)
/preload will be included with /system if you enabled the /preload option in Misc Nandroid Settings
you have an extra here: you can set the target volume for ors backups under Misc Nandroid Settings menu
ors backups can be set to either TWRP or CWM format
Aroma File Manager Support *Adapted from amarullz and sk8erwitskil
You get here the possibility to browse your phone with root access in a friendly GUI file browser, while being in recovery
You even now get a terminal emulator to run in recovery
Download Aroma File Manager from its Home Page
Get the last version and rename the file aromafm.zip
Put the aromafm.zip in "clockworkmod/aromafm/aromafm.zip" in any of the storage volumes
In recovery, tap the Aroma File Manager menu or double tap any part of the screen outside menus
It will launch the file manager automatically
Double tap gesture linked to Aroma File Manager can be altered in the GUI Settings menu
Touch GUI Preferences:
This is another unique feature of this recovery and is built from scratch
You can toggle through 4 touch modes:
Full Touch: menus are validated by touching them. I added extra checks to make it robust to validation by error while scrolling.
Double Tap: menus are highlighted on first touch. To validate action, you need to double tap the same menu
Semi Touch: the classic semi-touch interface I enhanced. Menus are selected/highlighted on first touch. You can scroll by swiping up/down, but no validation on touch.
Disable Touch: touch code completely disabled. You have all gui options left, but only hardware keys
When Full Touch mode is selected, it will automatically set recommended menu height, touch accuracy and scroll sensitivity. You can alter them later if you want
Scroll sensitivity controls scrolling on swipe up/down. Lower values are the most sensitive. Adjust this based on selected menu height
Touch accuracy: increase it if your touch gestures are not well accounted for
Config files are saved in /data/philz-touch/philz-touch_x.ini file.
You can do a backup of your settings file, it will go under /sdcard/clockworkmod/philz-touch.ini.bak
You can choose to be prompted to restore your settings whenever they are wiped while you have a backup. You can also set recovery to auto-restore them when needed. This check is done when you reboot to main system from within recovery
There are many gesture actions that you can setup at your wish (some default actions are setup by default)
Long press/move is the bad equivalent to a long press gesture action: just that after 0.6 sec of touch, slightly move your finger or change the pressure surface without actually lifting it
Your screen should auto-dim automatically after one minute and turn off after 3 mn. You can change those time settings. Just touch the screen to reset brightness and turn it on (some devices need to press hardware button)
All GUI parts can be customized: menu hight, text colors, menu colors, selection colors, background color and icon, menu seprators, battery and clock, header text...
To setup a custom background image: put a png image with your device resolution in a folder clockworkmod/custom_res
You can take screen shots from recovery display by the slide left gesture (change it at your wish). Pics captures will go under clockworkmod/screen_shots folder. External storage will be always used first. If no external storage is found, internal storage is used. You can take up to 999 pics before it resets to 1
Setup Free Browse Mode and Multi-zip Installer:
Free Browse Mode:
You can setup a default folder from where the Install Zip menu will start
From within your set default folder, you can now browse backward up to the root file system to install a zip file
Multi-zip Installer menu:
Lets you select multiple zip files to flash at the same time
The zip files must go into a subfolder under: "clockworkmod/multi_flash"
At least one subfolder with your zip files must be created. You can create as many subfolders as you want
exp: clockworkmod/multi_flash/NEAT_ROM_files
Pause on Logs:
Pause on Logs: when enabled, after flashing a zip file or doing a nandroid job, you will be prompted for a key to return to menu display. That way, logs are kept in full screen. Obviously, no pause will be performed on boot scripts and multi-zip operations
How to Install
This will depend on your device. Please look first for help in your device specific thread.
Provided instructions here ARE NOT VALID for all phone
Recovery (.zip) packages instructions
They come in the form of .zip files that can be flashed in cwm recovery
Download philz_touch_xxx.zip file
Put the previously downloaded philz_touch_xxx.zip file on your sd card
Boot into recovery (volume up+home+power)
Select "Install zip" and browser to your downloaded zip file.
Now select the philz_touch_xxx.zip fileyou copied in previous step
You will have PhilZ Touch Recovery flashed
Odin packages instructions: Samsung Only
They come in the form of .tar.md5 file
boot into download mode
start odin3 and configure it as in picture below
connect phone in download mode to PC via USB
press start to flash the tar.md5 package
normally, phone should auto-reboot into recovery.
If it reboots into main system and your recovery remains stock, repeat above steps and untick "autoreboot" in odin. Once flash is done, keep pressing the 3 buttons combo to for a reboot into recovery.You should see the new CWM
when in recovery, if you choose option "reboot system now" and you get "yes - disable flash recovery", select that option to avoid stock recovery overwriting cwm
to remove yellow triangle, use TriangleAway
Root your phone and reset Yellow Triangle
coming....
Full Change History
Change log is now here:
https://github.com/PhilZ-cwm6/philz_touch_cwm6/commits/cm-11.0
Older history in next post
6.48.4 (06.07.2014)
- merge multi stage install packages support from AOSP
- CWM 6.0.5.0
6.48.1 (30.06.2014)
- add option to directly parse time_daemon data files
- refresh current time in menu header after time daemon fixes
- fix first passkey prompt screen did not show proper background under some circumstances
- libtouch_gui 1.30
6.47.7 (25.06.2014)
- preserve background icon user settings after sideload, install zip and wipe actions
- use real fstype instead of auto in /etc/fstab when converting between ext4 <-> f2fs using extra.fstab
- libtouch_gui 1.29
- LG G2 variants: enable performance mode in recovery (device tree)
- HTC One Mini (m4): enable f2fs and exfat kernel support
- Galaxy S5 LTE (klte): enable backup/restore of /efs, /modemst1 and /modemst2 partitions
6.47.6 (24.06.2014)
- recovery lock: support use of virtual / capacitive keys as pass key
- libtouch_gui 1.28
6.47.4 (23.06.2014)
- fix adb was disabled when no recovery lock passkey was setup
- Galaxy S3 D2 variants: enable f2fs support
6.47.3 (20.06.2014)
- add recovery lock with passkey on start
- better extra partitions support in custom nandroid operations
- fix segfault during shell nandroid backup/restore commands
- enable progress display during "adb shell nandroid backup/restore" commands
- enhance and fix bugs of progress display during install/nandroid... operations
- nandroid restore: fix progress bar animation when md5 verify is enabled
- nandroid md5: fix progress bar was not reset for each file
- nandroid md5: fix .android_secure md5 sum was never generated or checked
this could cause md5 check to fail under some circumstances
- limit logging to console in adb shell nandroid and mount commands
- fix detection of real fstype (pointer to in the scope char array bug)
- merge: "Only chmod backup/blobs directory if it exists"
- merge: "Enable cmdline nandroid backup of vold volumes"
- disable useless sd-ext warnings and errors
- merge loki updates
- f2fs <-> ext4 conversion: support fs_options2 through extra.fstab before dropping to bare minimal options
- clean up code
- libtouch_gui 1.26
6.43.8 (02.06.2014)
- fix recursive path creation bug for /data/media/0
- f2fs: do not try f2fs recovery.fstab mount options on an ext4 partition
- f2fs: do not redefine default recovery ext4 mount options when migrating from an f2fs recovery.fstab
- f2fs: error message when converting unsupported file systems
- fix Galaxy Mega variant background resolution
6.43.5 (01.06.2014)
- default to /data/media/0 unless we define BOARD_HAS_NO_MULTIUSER_SUPPORT
- use lstat to check if file exists
6.43.4 (01.06.2014)
- fix text print colour could persist after md5 check
6.43.3 (31.05.2014)
- fix f2fs conversion of /data on /data/media devices
- allow ext4 <-> f2fs backup data migration in nandroid
- cleanup code
6.43.0 (30.05.2014)
- nandroid backup: fix 'media' exception:
In CWM, a bug present from the begining was preventing any path/file named media from backup on /data/media devices
This fix will only exclude /data/media path and not other media files/folders
6.42.9 (30.05.2014)
- default again to libtar for backup/restore
6.42.7 (30.05.2014)
default to busybox tar:
- use busybox tar by default as it now supports selinux context backup/restore
- unify libtar and busybox tar options (-p for selinux context)
- remove now deprecated external selinux container code
6.42.5 (30.05.2014)
- f2fs: recreate /etc/fstab after ext4/f2fs conversion for proper use of system mount command
- comment useless dead code
6.42.4 (30.05.2014)
- f2fs: fix nandroid restore to f2fs partitions
- f2fs: support format extra storage to f2fs (vold patch needed)
- f2fs: support switching between f2fs/ext4 (needs f2fs in kernel modules), thanks @KumaJaya
- f2fs: reload volume table after f2fs/ext4 conversion (no reboot needed after conversion)
- f2fs: do not format whole /data when not expected on /data/media devices
- f2fs: allow /data f2fs/ext4 conversion for non data_media devices
6.41.8 (26.05.2014)
Preserve recovery settings after a wipe
- on settings change, create a second copy of recovery settings on primary storage (/sdcard)
- on recovery exit, always copy recovery settings to sdcard if no copy is present
- after a wipe, on recovery exit, try to restore settings from the copy on primary storage
- fix save/restore settings menu labels
- libtouch_gui 1.22
6.41.6 (12.05.2014)
- update exfat to dorimanx 1.2.9 latest sources
- fix compile error when enabling BOARD_RECOVERY_USE_BBTAR
- repo sync latest sources
- Galaxy Tab Pro 8.4 WiFi SM-T320 (mondrianwifi)
- HTC M7 variants: use new cm kernel with exfat sources
- HTC M8 variants: use new unified recovery
6.41.5 (11.05.2014)
- libtouch_gui 1.21: auto detect BRIGHTNESS_SYS_FILE path if it is not set during compile
* search for the file in most common locations
* if found, save it to recovery settings ini file to be called on next recovery starts
* else, disable adjust brightness function to avoid error logs on recovery start
- fix various compiler warnings and errors
- enhance pre-compile setup
- dedupe: merge clean up code from @xiaolu
- merge: fix restorecon_from_file potential crash from @xiaolu (only for BOARD_RECOVERY_USE_BBTAR)
- fix 240x320 images
- merge "cwm: Honor recovery variant "
- merge "cwm: Remove hardcoded paths"
- merge "Keep 'show log' on screen until user dismisses it"
- create /data/media directory after internal storage is wiped
prevents denial to read/write from internal storage under some circumstances
- open source touch_gui library
- update licence files
6.40.1 (03.05.2014)
- proper libtar implementation: support backup/restore of selinux context inside archive
- dedupe: support backup/restore of selinux context by @Chenglu
- libtouch_gui 1.20: support custom key files (BOARD_CUSTOM_RECOVERY_KEYMAPPING)
Older Change History v6.x
6.29.9 (27.04.2014)
- merge "Recovery: swap XY on swipe controls"
- shell pipe: set exit code to error if any pipe element fails
* this was causing backup state to be reported good while tar command failed
6.29.7 (27.04.2014)
- minitar: add options help and change log
- minitar: build as a static library to spare 150 kb (only 16kb size increase)
6.29.2 (26.04.2014)
- fix potential bug when verifying root and recovery state on exit
- merge "Fix verify_root_and_recovery menu selections":
- hide the Go Back button from confirm menu
- merge "Prohibit mounting/formatting swap partitions in recovery"
- add minitar binary to /sbin instead of busybox tar
- minitar: enable more options, enable long options, fix selinux backup/restore, enhance GNU tar compatibility
- revert RECOVERY_NEED_SELINUX_FIX patch
- enable seamless backup/restore selinux context using minitar binary
- TWRP mode: support backup/restore of selinux context
- libtouch_gui 1.19
6.27.6 (21.04.2014)
- add libtouch_gui for armv6 devices, thanks @yuweng and androidarmv6 team
- loki: sync to upstream
- Galaxy S5 SM-G900H (k3gxx): update kernel to XXU1ANCI
- Amazon Kindle Fire HD 7 (tate): fix background and virtual keys
- Amazon Kindle Fire HD (jem & tate): fix display battery level
- LG G2: repack on older cm 6.25.4 kernel to fix graphic issues
- New: HTC One M8 Verizon (m8vzw)
- New: LG Optimus One P500 (p500) - arm v6 based
6.27.2 (18.04.2014)
- libtouch_gui 1.18
- confirm cancel nandroid jobs (prompt to press 'Back' twice or resume after 5 secs)
- vibrate after backup/restore operations
6.27.0 (17.04.2014)
- MTK support: fix backup & restore of boot/recovery/uboot partitions
- MTK devices: improve error handling of partitions size
- do not consider su symlink in /system/bin as a broken root
- New: Amazon Kindle Fire HD 7 (tate)
- New: Amazon Kindle Fire HD 8.9 (jem)
- New: Galaxy S5 SM-G900H Exynos variant (k3gxx)
6.26.6 (14.04.2014)
- m7 unified for m7ul, m7att and m7tmo
- CWM 6.0.4.8
- merge support for native dual boot devices
- sync sources
6.26.4 (12.04.2014)
- update libloki to latest sources
- broken root: help victims of bad custom ROMs
This adds extra code to detect if two su instances are installed in /system/bin and /system/xbin
It will kill both and properly apply SuperSU
- fixing root on exit was never done what ever was user choice
6.26.1 (06.04.2014)
- New: Note 10.1 2014 3G - SM-P601 (lt0wifiue)
- New: LG Optimus L7 P700 (p700) by @ali.filth
- New: Galaxy Grand Quatro (i8552) by @ali.filth
- New: HTC One mini (m4)
- fb2png: better error logging
6.25.7 (05.04.2014)
- New: HTC One M8 (m8)
- New: HTC One M8 sprint (m8spr)
- New: Note 10.1 2014 Wifi - SM-P600 (lt0wifi)
- derp cm_moto_msm8960
6.25.4 (31.03.2014)
- sort files using case insensitive order (adapted from @titanic-fanatic)
- use new ro.loki_disabled for unified variants not needing loki
This way, we only need to set the ENABLE_LOKI flag to have a loki enabled recovery
No more need to set an extra ro.loki_enabled property
Only modification needed now is for jflte variants not using loki
Only jflteatt and jfltevzw do
We have to set ro.loki_disabled to 1 for all other variants in libinit_jflte
- New device: Galaxy X Cover 2 - skomer
- New device: Galaxy S3 Mini - golden
- New device: Sony Xperia ZR (dogo)
- New device: Sony Xperia Tablet Z (pollux)
- New device: Sony Xperia Z1 Compact (amami)
- New device: Sony Xperia S (nozomi)
- New device: moto_msm8960 unified device (by @hachamacha)
- New device: Galaxy S Advance (janice)
- New device: Galaxy Ace 2 (codina)
- New device: Samsung Galaxy Tab 3 7.0 SM-T211 (lt023g)
6.25.0 (29.03.2014)
- jflte: enable back loki for jflteatt and jfltevzw
- remove old no more needed md5 check code
6.24.8 (28.03.2014)
- libtouch_gui 1.16:
- fix when quickly doing two gesture actions one after the other, highlighted m$
we only allow gesture actions when the previous one is terminated
- set these default gesture actions:
* swipe left = screen off
* swipe right = increase brightness
* press 1 sec and lift = show log
* press 2 sec and small move = screen shot
- merge "Only init legacy property environment once"
6.24.6 (28.03.2014)
- revert using ntfs module and drop to fuse for complete write support
- use new md5digest code to generate/verify nandroid backups
- bring progress bar during nandroid md5 generation and check
- exclude log and md5 file when regenerating md5 files
- twrp mode: use new md5digest function with status bar during md5 check/create
- twrp mode: fix double md5 verification bug
- fix delete backup menu failed to reopen base backup folder + wired log message
- libtouch_gui 1.15: fix the "umount: can't umount /data: Invalid argument" log message on start when time daemon was loaded
- libtouch_gui 1.15: show "time daemon loading" message on recovery start when we're waiting for the daemon to load
- libtouch_gui 1.15: support time_daemon /data/system/time path used on some ROMs
- add Xperia ZL (odin) flags (@shoey63)
- jflte: remove /firmware and /firmware-mdm from fstab
- repack builder: fix version display during install broken after fixing cm recovery builder script
6.23.7 (25.03.2014)
- cherry-pick @mdmower patches to legacy props init: better error checking to avoid segfaulting
- really hammer lazy developers
6.23.5 (25.03.2014)
- merge: "recovery: Compatibility with upstream minui change"
- merge: "use correct USB PID for adb and new PID for adb+ums"
- merge: "Fixes makerecoveries.sh"
- merge: "nandroid: Convert selinux_android_restorecon calls to new API" from @KumaJaya
- fix fb2png flag to be enabled by default
- cherry-pick: "Revert "Add a copy of the updater binary to the recovery resources""
- cherry-pick: "Make legacy prop environment available to recovery"
- cherry-pick: "Use legacy property environment if old update-binary"
- fix potential unsafe thread code
- libtouch_gui 1.10: disable gesture actions during md5 checks as they are not thread safe
6.22.5 (22.03.2014)
- fb2pn v2.0.0 by McKael & Phil3759
* autodetect image offset to properly align frame buffer data
* fix memory leak
* fix all compiler warnings
* auto detect active frame buffer to capture
* option to force buffer to capture by user
- fix compiling of Advanced Edition
6.22.1 (18.03.2014)
- fix fb2png code for new Qualcom boards (not merged, work in progress)
- fix key repeat for hardware keys
- fix MTK board support
- fix compiling error of Advanced Edition
- fix md5 check crash when installing zip files
6.21.2 (14.03.2014)
- add progress bar while reading zip file to compute md5 check
- add color printing during md5sum checks
- (derp) fix color code printing on md5 check disappears after 5 sec (ui_wait_key() screen refresh)
- md5sum check potential bug fixes and optimizations
- libtouch_gui 1.05
6.20.6 (12.03.2014)
- add md5 sum calculation and toggle verification during install of zip files
- hammerhead: fix efs backup (derp)
- loki: use new loki_tool multi bin sources
- add missing vkeys for 240 width
- many bug fixes and code cleanups
- libtouch_gui 1.04
6.19.6 (05.03.2014)
- loki: fix auto loki was broken and clean up sources
- hammerhead: add efs backup/restore
- m7 variants: fix charger in off mode
- jewel: fix no fstab!
6.19.3 (02.03.2014)
- fix compiling for QCOM devices when using a prebuilt kernel with TARGET_PREBUILT_KERNEL
- galaxysmtd: remove ntfs-3g drivers to fit partition size
6.19.2 (01.03.2014)
- merge "nandroid: Allow tar backups of yaffs2 partitions"
- merge "update-binary: Add collect_backup_data function"
- merge "recovery: add overlay interface for recovery mode"
- merge "recovery: Add support for split display "
- merge "recovery: Fix compilation for non MSM target "
- merge "Fix overlay inclusion on MSM"
- merge "Loki: Add LG G Flex KDDI MODEL"
- merge Aroma patches:
* User selectable colorspace added to settings.
* Unmount /system at exit if mounted.
* Some more logging added.
- add 480x854 res backgrounds
- add 240x320 res backgrounds
- hlte: use new unified device builds but only for devices with new 4.4 bootloader
- hlte: fix cdrom in mount usb storage, thanks to @Chenglu
- jewel: use cm kernel with new layout partitions to fix charger
- hammerhead: revert to using cm kernel instead of stock
- falcon_gpe: use unified falcon device with init started script to swap fstab f2fs for ext4
- New: d2dcm (d2lte)
- lt02wifi: support fb2png screen shots
- loki fix for zip installers broken after unified devices releases
6.18.7 (25.02.2014)
- enable full touch gui build through re-distributable libtouch_gui (v1.01)
- merge "Fix mass storage in recovery"
- merge remote cm-11.0 changes
- loki: add support for unified devices
- fix loki user setting could be overridden on edify install_zip commands
- Galaxy S4 Qualcom variants: use new unified device "jflte" for all variants
- loki: show the enabled/disabled state in menu
- more comprehensive menu text display for /data/media/0 toggle
- fix potential memory leak in /data/media/0 toggle
- Galaxy S3 Qualcomm variants: use unified dlte recovery image
- New: Galaxy S2 Epic 4G Touch - SPH-D710 (d710)
- New: Samsung Galaxy Tab 3 7.0 SM-T210 WiFi (lt02wifi), credits to gr8nole and ketut.kumajaya
- New: ZTE Warp Sequent - N861 (warp2), credits to jetx2x
- New: ZTE Awe (nex), credits to cooldudezach
- New: HTC Rezound (vigor)
- merge: "P31XX: use landscape background"
- fix virtual keys on devices with 1024 pixel width resolution
- huge cleanup and potential bug fixes
- fix all compiler warnings
6.15.3 (13.02.2014)
- update superSU to 1.93
- sync sources
- fix recovery reboot command (adb and shell) by adding the init sys.powerctl property control
- merge "Fix mkfs.f2fs calling in roots"
- merge "Fix mass storage in recovery"
- fix display current path when navigating backward in folders
- Nandroid Simple Logging: toggle logging of file names during nandroid to keep screen progress while speed up nandroid operations for some devices
- increase NICE_INTERVAL to 300 msec (faster backup/restore on some devices)
- hide unused settings in Nandroid Settings menu (if we disable all progress on screen, hide non valid options)
- re-order nandroid settings menu
- add a toggle for fall back to pre-built update-binary to permit use of older update-binary in zip packages (doesn't persist on reboot).
this will fix the assert errors due to outdate update-binary. It could still be affected by assert error on device name getprop. However, that one is easier to fix by end users by editing updater-script. This is a workaround. The best is to hammer your ROM cooker to update his scripts and binaries
- setting for signature check toggle on zip updates will be now saved on reboot
- Aroma File Manager: mount vold managed volumes on launch from recovery
- Free Browse Mode: make it possible to install from any custom path even ramdisk
- Free browse mode: fix exceptions when setting up custom path
- Free browse mode: mount known volumes during setup
- Free browse mode: better handling of /data/media devices
- Free Browse Mode: mount vold managed volumes when navigating in
- HTC One variants (m7): fix charger
- HTC Evo 4G LTE (jewel): fix charger
- HTC Evo 4G LTE (jewel): update to new Sense 5 partition layout (/data/media)
- HTC Evo 4G LTE (jewel): use exfat modules for much faster backup speed to exfat cards
- New: Moto G variants (falcon): xt1028 xt1031 xt1032 xt1033 xt1034
- New: Moto G Google Play Edition (falcon_gpe)
- New: Galaxy Note 8.0 LTE (n5120) support
- New: HP Touch (tenderloin), no touch
- fix potential logging issues
- fix compiler warnings
- clean up code and misc fixes
6.13.1 (06.02.2014)
- HTC One variants (m7xx): fix charger bug
- Nexus 5 (hammerhead): use stock kernel to fix graphic issues
- LG G2 variants (d80x, vs980, ls980): add faster exfat backups using exfat modules from samsung (credits @dorimanx)
- LG G2: add d805 and d806 support
- Galaxy S4 variants (jflte): derp fix kernel random hang on boot
- SGH-I757M (celoxhd): use exfat static drivers
6.12.8 (30.01.2014)
- time and date menu text formatting and order
- version display edit
- add ntfs write support to devices using kernel modules instead of fuse
- loki: merge "Support LG Optimus F7 ZV5_02"
- zip installer: update loki binaries for LOKI devices
- zip installer: use new update-binary sources
- add NTFS kernel module support for more Samsung devices
6.12.2 (28.01.2014)
- manually set time and date in recovery
- support Qualcom time daemon to sync time with main system (credits to dougiebee)
- support RTC offset hack for Qualcom devices without a proper time daemon in system ROM (credits to dougiebee)
- option to drop to system set time and date commands (credits to dougiebee)
- set default nandroid compression level back to low
- roll out exfat-nofuse sources from dorimanx into various kernels from Samsung and other brands
- code fix and cleanup
- New: Oppo N1
6.10.6 (23.01.2014)
- update SuperSU to 1.91
- merge android_system_core changes to adb to fix push to extra storage paths
- do not use performance mode during install zip: fixes hang on unmount /system in updater-script when usb cable is connected
- i9505 ans US variants: update kernel to fix random hang on boot
- update to CWM 6.0.4.7
- merge "Fix up bu restore"
- ROM Manager: workaround to backup/restore to/from external storage
6.10.2 (20.01.2014)
- enhance touch init (fix touch on some Sony devices)
- really fix reading device max brightness value
- loki: merge "Support Open EU LG Optimus F6 and US Cellular Optimus F7"
- New: HTC One X+ (enrc2b)
6.10.0 (18.01.2014)
- read the device max brightness setting to fix brightness toggle on some Sony devices
- merge: "Populate mount menu with new mount/format matrix" - final version
- merge: "Use cat for adb backup."
6.09.8 (16.01.2014)
- merge: "Populate mount menu with new mount/format matrix"
- New: Moto X variants: US Cellular (xt1055), Sprint (xt1056)
- New: Galaxy Tab 2 P3110 (p3110)
6.09.6 (15.01.2014)
- do not error on missing sd-ext when wiping dalvik cache
- merge: "su: Update for latest su daemon compatibility"
- merge "Clean up c formatting - 1"
- merge "Remove "Go Back" option from verify root and recovery options"
- merge "Fix potential chmod failures"
- merge: "Add a copy of the updater binary to the recovery resources"
- merge: "install: Support downgrade scenarios"
- merge: "install: Fix possible overflow condition in the updater "scanner""
- merge: "minui: do not use flexible array initialization"
- merge: "correctly mount tmpfs as /tmp in recovery"
- New: Sony Xperia SP (huashan)
- New: Sony Xperia T (mint)
- New: Samsung i9192 (serranodsub)
- New: Motorola Moto X variants: VZW (xt1060), GSM (xt1058), TMO (xt1053)
- New: Samsung Galaxy Note 10.1 LTE (n8020)
6.09.2 (12.01.2013)
- TWRP: merge "support use TW_USE_MODEL_HARDWARE_ID_FOR_DEVICE_ID"
- toggle prompt on low free space during backup
- SuperSU update to v1.89
- loki: merge "Support LG Vu 3."
- code cleanup
- New: US Cellular CH-R530U (d2usc) support
6.08.9 (04.01.2013)
- gesture action defaults changed
- long press and lift gesture action is now triggered after finger pressed for more than 1 sec
- do not include fb2png on non supported devices
- stop always rebuilding aroma intermediates
- Update: Samsung Exhilarate SGH-I577 (exhilarate)
- New: Galaxy Express AT&T (expressatt)
- New: Asus Transformer Pad TF300T (tf300t)
- New: Asus Transformer Prime TF700T (tf700t)
- New: HTC Evo 4G LTE (jewel)
- New: LG Optimus 4X HD P880 (p880)
- New: Galaxy Tab 3 8.0 SM-T310 - Wifi (lt01wifi)
- New: Galaxy Tab 3 8.0 SM-T311 - 3G (lt013g)
- New: Galaxy Tab 3 8.0 SM-T315 - LTE (lt01lte)
- New: Galaxy Note 3 Verizon (hltevzw)
- New: Galaxy Note 3 Canada (hltecan)
- New: Sony Xperia Z1 (honami)
- New: Sony Xperia ZU (togari)
6.08.7 (03.01.2014)
- fix Free Browse Mode folder cannot be changed in menus once first setup
- add back custom format fstype using vold (now patched in cm-11.0 thanks @cyanogen)
- disable journalling when formatting non voldmanaged extra storage in ext4 fstype
- merge "recovery: Add support for performance control"
- update CWM to v6.0.4.6
- loki: sync sources (support LG G2 D80010o)
- default backup compression level is now 5 (medium)
- v500: fix background width to 1200 pixels
- e970: fix OTA assert line breaking zip installer
- New: HTC Desire 601 (zara)
- New: HTC Droid DNA (dlx)
- New: Samsung Galaxy Grand Duos GT-I9082 (i9082)
6.07.8 (28.12.2013)
- fix exiting "pause on logs" mode with virtual keys caused erroneous validation
- fix exiting screen off mode with hardware key could cause erroneous validations
- fix some devices could not exit "pause on logs" mode with screen touch
- bring immediate touch responsiveness after exiting screen off mode and "pause on logs" mode
- fix erroneous first menu validation when exiting screen off mode on some devices
- fix long press and move action could be triggered while swiping outside menus and returning to first touched area
- increase threshold for long press and move action for easier triggering
- small touch scroll optimizations
- improve touch responsiveness on low res devices
- code clean-up and optimization
- fix log text could overwrite clock/battery icons on some low res devices
- after successful zip install with sideload, hide the install background icon
- after installing zip with sideload, do not trigger "pause on logs" mode
- loki: sync latest sources (support LG G2 VS98012b)
- New: HTC One Verizon (m7vzw)
- New: Galaxy Note 3 International, Sprint and TMO (now built with cm-11.0 device tree and kernel)
- New: Galaxy S Relay 4G - SGH-T699 (apexqtmo)
- New: LG G Pad 8.3 (v500)
- New: Samsung Galaxy Premier I9260 (superior)
- New: Samsung Galaxy Mega 6.3 I9200 - SGH-i527 (meliusltexx)
- New: Samsung Galaxy Mega 5.8 i9150 (melius3gxx)
- New: Galaxy S i9000 support (galaxysmtd) : still needs cat /proc/mtd to add in extra.fstab
- New: Galaxy S3 verizon - SGH-I535 (d2vzw)
6.05.6 (21.12.2013)
- better fit text logs on non HD devices: stop slightly overwrite of bottom virtual keys separation bar and clock/battery area
- fix logs overwriting bottom virtual keys and progress bar in sideload mode
- add 5 extra partitions support in nandroid: can be added in fstab and will be auto detected
- custom backup and restore menu: move reboot item to top of partitions list
- custom backup and restore menu: auto hide all unused items
- advanced menu: hide /data/media toggle for non datamedia devices
- sync loki sources: add new LG devices
- SuperSU update to 1.86
- busybox: merge @Chenglu changes to support selinux (no tar --selinux yet)
- huge code clean ups and fixes
- New: LG G Pad 8.3 (v500)
- New: Samsung Galaxy Premier I9260 (superior)
- New: Samsung Galaxy Mega 6.3 I9200 - SGH-i527 (meliusltexx)
- New: Samsung Galaxy Mega 5.8 I9150 (melius3gxx)
- New: Galaxy S i9000 support (galaxysmtd) : still needs cat /proc/mtd to add in extra.fstab
- New: Galaxy S3 verizon - SGH-I535 (d2vzw)
- Note 3: fix device name to hlte
- Note 3: ramdisk changes to better handle enforced selinux and usb mount storage
- Note 3 (hlte): add modem support in backup/restore
- Note 3 (hlte): repack on @Chenglu ramdisk to fix time
- Note 3 (hlte): fix boardconfig for correct ums lun path (mount usb storage)
- i9100/n7000: add extra.fstab support
- i9100/n7000: use built in kernel exfat modules for faster writes to exfat cards
6.04.0 (14.12.2013)
- fix twrp backup/restore default mode
- save loki support user setting (default is now disabled)
6.03.8 (13.12.2013)
- Galaxy Note 3 - n9005 (lt03ltexx)
- add custom backup and restore options to main nandroid menu for each storage volume
- ditch stock cwm limited advanced restore function
- add toggle to switch between TWRP/CWM as default backup mode
- ors: backup mode is now the default backup mode set for all recovery session
- ors: smart restore mode to override main backup mode depending on path we restore from (TWRP vs CWM auto detection)
- backup/restore validation menu moved to top in custom modes
- sanitize rom name for backup: exclude "&" symbol and fix compiler warnings (size_t)
- when deleting backups, do not exit the menu each time
- fix new line in process_volumes()
- merge: "Don't return immediately from reboot commands."
- merge: "Enable incremental builder to find files that moved"
- merge: "Support recoveries without CONFIG_EXT4_FS_XATTR"
6.03.5 (11.12.2013)
- Nexus 5 (hammerhead) support
- rebase on KitKat Android 4.4.x cm-11 branch
- restore NICE_INTERVAL to 100 for faster refresh of progress bar during nandroid restore
- Samsung phones: use built in kernel exfat/ntfs modules + fix selinux permissions to support exfat/ntfs read/write
- fix format to any user fstype without direct call to vold functions as it was no longer supported in cm-11.0
- proper ext2/ext4 support on extra storage volumes
- fix looping into readlink for boot/recovery partitions
- Samsung: add selinux permissions for preload partition
- if minivold fails to mount a voldmanaged volume, still drop to system mount (support ext2/ext3 mount)
6.02.1 (08.12.2013)
- loki: fix new line in ui_prints
- Nexus 7 (2013) deb and flo: fix background image size to better fit screen
- Galaxy Note 8.0 GSM (n5100): fix touch at kernel level for recovery and aroma, credits to @nickdollahz
- Galaxy Note 8.0 Wifi (n5110) support
- Galaxy Note 2: stop flashing sensors on boot (credits @AndreiLux), use built in kernel exfat modules (big thanks @wanam)
6.01.7 (07.12.2013)
- loki: update to v2.1 latest sources
- loki: use libloki_recovery for easier maintenance + clean-up the code
- loki: update to latest sources
- loki: fix all compiler warnings
- loki: remove licence in header file as requested by author
- fix get size of boot and recovery partitions from device block name link on some devices (yet another round, for good this time)
- LG G2 (d801): fix assert in zip installer
- Samsung Galaxy S2 Skyrocket i727 (skyrocket) support
- Samsung Galaxy W - GT-I8150 (ancora) support
- Samsung Galaxy S Plus i9001 (ariesve) support
6.01.2 (03.12.2013)
- fix error log when changing backup format for non datamedia devices
- fix celoxhd vibrator thanks @titanic_fanatic
- support LG G2 Int (d802), LG G2 AT&T (d800), LG G2 TMO (d801), LG G2 Verizon (vs980), LG G2 Sprint (ls980)
- support LG Nitro HD AT&T (p930)
6.01.0 (01.12.2013)
- fix settings file and themes could not be saved/restored on non data media devices
- fix various issues with non data media devices (new vold names)
- settings path (/data) is unmounted only on recovery start and not on every settings refresh
- move all recovery setting files/paths to a common header file
- fix Atrix HD mbm886 compiling
- fix success/failure display when copying files
- crespo (Nexus S): revert to cm-10.2 kernel sources
6.00.8 (30.11.2013)
- merge selinux backup/restore changes from @xiaolu
- by default, enable selinux context backup/restore
6.00.7 (30.11.2013)
- fix unpredictable first touch on some devices
- support MTK devices backup and restore of boot, recovery and uboot
6.00.5 (29.11.2013)
- fix potential memory overflow on elapsed timers
- use clock_gettime(CLOCK_MONOTONIC) for more reliable elapsed timers
- fix virtual keys won't repeat for some devices since recent cm device tree updates
- update SuperSU to v1.80
- resync sources for fixing selinux permissions on lost and found folder
- Galaxy S3 US variants (d2spr, d2tmo, d2att): fix vold dropping to fuse instead of exfat kernel module
- i9500: use adam 3.5 kernel + built in exfat + ntfs, credits @wanam
- Galaxy S Relay 4G - SGH-T699 (apexqtmo)
- Galaxy Note 8.0 (n5100)
- Galaxy S2 HD LTE - SGH-I757M (celoxhd) credits @titanic_fanatic
- Nexus 7 (2013) LTE (deb)
- LG Optimus G Pro GSM (e980)
- LG Spectrum 4G - vs920
- Motorola Atrix HD
- Galaxy S4 int + US: do not show unsafe volumes in mounts and storage
6.00.0 (24.11.2013)
- fix settings file could be left opened in rare circumstances
- make nandroid menu easier to edit + fix potential memory overflow bug
- properly fix root apply for 4.3+ systems, credits @Chainfire
- add superSU 1.75, credits to @Chainfire
- rewrite touch code from scratch to optimize events handling
- add touch scrolling kinetics
- fix touch key registration on start
- fix: double tap a menu in full mode could validate first menu
- fix cancel nandroid backup with virtual keys needs to keep cancel button pressed
- when changing gui settings, be able to return to default values
- keep bottom logs row height limited what ever menu size we choose
- get rid of now useless friendly log view mode
- always respect user set minimum log rows to display in bottom of menus
- when setting no touch gui mode, hide virtual keys and set default bottom log lines
- when setting touch modes, show virtual keys by default
- fix gui settings menu order
- theme support through pre-set configuration files
- settings file renamed to force a user migration on update
- add dedicated menu for custom/free browse mode (no more alter existing install zip menus)
- fix couldn't install from last install path when free browse mode was enabled
- move check for root on restart and auto restore settings to open source code
- remove "Custom Backup and Restore" menu from PhilZ Settings menu
- stop double stringify TARGET_COMMON_NAME (device name was shown with surrounding quotes in About menu)
- optimize memory use when browsing for files to install/backup/restore
Older Change History v5.x
5.18.9 (04.11.2013)
- add option to disable all nags on exit (root, flash recovery)
- add menu to root system and verify recovery
- code clean-up
5.18.7 (03.11.2013)
- optimize Install zip menu + order entries
- merge "minui: Allow devices to blank/unblank using LCD backlight" into cm-10.2
- merge "recovery: Add a proper CleanSpec.mk * Clean all the stuff that conflicts with AOSP recovery."
- merge "Add guard makefile for allowing simple recovery build"
- merge "Quickly install from last install path"
- merge "Enable optional swipe based touch controls"
5.18.5 (18.10.2013)
- unmount /data on user request for /data/media devices
- fix bug when reading partition link target
- do not ever log to screen mount/unmount events for sdcards (this will preserve ui_print for USB OTG volumes)
- write recovery version on exiting recovery instead of start: spare an extra partition mount/unmount on start
- Asus Nexus 7 2013 (flo) support
- HTC One AT&T support
- HTC One m7ul, m7spr, m7att, m7tmo: support exfat kernel module instead of fuse
- Galaxy S3 i9300/i9305: add exfat kernel module support in minivold
5.18.2 (15.10.2013)
- merge @Chenglu latest changes for selinux context backup/restore (4.3 ROMs)
- user can enable/disable nandroid backup/restore of selinux context: speed up things for non JB 4.3 users
- fix bug where restore compressed archive from external storage caused vold crash because of busy volume:
- misc bug fixes
- S4 mini (i9195/i9190): use exfat/ntfs ko modules with custom kernel from samsung sources (thanks to @wanam)
- Xperia Z (yuga): use stock Sony + exfat ko module instead of fuse
- Galaxy S4 ATT and VZW: support auto loki on flash
5.17.9 (13.10.2013)
- fix min brightness value in auto dim mode from 25 to 10
- merge temporary @Chenglu fix to backup/restore selinux context for 4.3 ROMs
5.17.8 (13.10.2013)
- merge "Make "one confirm" the default action. Create .many_confirm to restore all the extra no options"
- stop useless mount of /data in write_recovery_version() as it will be mounted later
- i9195: use custom kernel compiled from samsung source update1
- i9195: enable use exfat/ntfs ko modules + migrate to cm-10.2
5.17.7 (12.10.2013)
- merge su changes: "Add required libraries to list." into cm-10.2
- set lowest brightness value from 25 to 10
- i9505: use new custom kernel from google sources to fix ext4 corruption, exfat and ntfs kernel modules (huge thanks to @wanam)
5.17.6 (09.10.2013)
- Merge "Recovery: Loki patching support" into cm-10.2
- Merge "Support f2fs format"
- Fix f2fs formatting through edify scripting (roots.c entry)
- Merge "Don't print any messages regarding sd-ext to the UI"
- merge touch changes into cm-10.2
- add extra.fstab file support to provide blk_device2, fs_type2 and fs_options2
- use blk_device2 to partition sdcard and to format in ext2/ext3 for voldmanaged volumes
- fix Aroma file manager cannot see external storage due to minivold/fuse
- fix ors scripting for new cm-10.2 fstab format
- ors backup target: ensure user doesn't enter a non valid volume mount point in recovery settings file
- fix Get_Size_Via_statfs() handling of /data/media storage with new vold
- improve get_ors_backup_volume() call
- serious cm-10.2 bug: do not show partition sdcard menu for voldmanaged devices unless they have a valid blk_device2
- allow custom format of voldmanaged volumes if fs_type == auto even if they cannot be partitioned (!can_partition)
- format_device() could fail to wipe /sdcard on /data/media devices
- format_volume() could fail to wipe /sdcard on /data/media devices (edify scripting)
- ensure_path_unmounted() could not unmount /sdcard path on /data/media devices
- Find_Partition_Size() can now get /data size partition from a /data/media path (/sdcard)
- misc bug fixes for cm-10.2 and vold
- remove included device_config.h and put all additional BoardConfig.mk in one file (easier port for devs)
- ignore Rainbow commit
- improve write_recovery_version() to also unmount /sdcard on non /data/media devices
- favour kernel module over fuse to mount exfat volumes
- add get_device_mmcblk() function to read real device /dev/block path from blk_device link
- fix dd raw backup and restore to better detect real device block (efs / modem backup and restore)
- nandroid backup and restore speed fix
* spare some pthread_mutex_lock(&gUpdateMutex) on ui_delete_line() call
* do not hammer with fputs to write nandroid log
* increase NICE_INTERVAL from 100 to 350 msec to lower screen refresh rate during nandroid jobs
- do not define S4 i9505 with BOARD_HAS_SLOW_STORAGE to re-enable displaying all backup stats by default
- allow sideload to be used in conjunction with other commands.
- merge: Array max is incorrectly calculated, can lead to missed events for ids > MAX_DEVICES (thanks @jeboo)
- sync sources to update su
- merge "loki: Update to 2.0, Add support for LG G2 (and device trees in general)"
- update cwm to 6.0.4.4 + sync sources
- i9505: move to wanam 1.6 kernel : small size, adb root, touch, force load of exfat
- i9505: support ntfs through ko modules
5.15.9 (26.09.2013)
- get rid of = and space in ors script (merge from twrp) + merge to cm-10.1
- touch: drop unwanted devices to handle touch events for some devices (Xperia Z...) + merge to cm-10.1
- touch: improve scroll and make it more friendly
- touch: fix slide right/left actions triggered after a scroll ending outside menu
- touch: improve long press and lift + long press and move actions and lower delay to 0.6 sec
- touch: in double tap and highlight only modes, fix unwanted scroll down while selecting a menu after a scroll
- touch: misc bug fixes + cleaner code
- HTC One X (endeavoru): repack with 4.18 stock ramdisk to fix write/read speed
- HTC One S (ville): add compatibility with new /data/media hboot
- SGH-T599N (codinamtr): rebase repack on Unjestified Dev tree to fix adb/mount usb storage
- Xperia Z: fix touch handling
- Motorola Droid RAZR M (xt907)
- Motorola Droid RAZR HD GSM (xt925) and US (xt926)
- Galaxy S Blaze 4G - SGH T769 (t769)
- Galaxy Exhilarate - SGH-I577 (i577)
- Galaxy S4 mini i9190 (serrano3gxx)
- Galaxy S4 mini i9195 (serranoltexx)
- Micromax A57 (a57)
- LG Optimus G ATT (e970)
- LG Optimus G Canada (e973)
- LG Optimus G Sprint (ls970)
- LG Optimus G Intl (e975)
5.15.0 (21.09.2013)
- fix bug where android_secure could not be restored
- add png files for 320px width devices and fix pico device tree for screen resolution + merge to cm-10.1
- selectively force tar wrapper on yaffs2 file systems (better handling of make update.zip from ROM and ors backup in cwm format)
- fix touch support for some Samsung phones
- merge latest aroma 1.91 changes to fix theme loading bug
- fix user choice format sdcard options
- i9505: powered by stock 4.3 Samsung kernel compiled and fixed by @ausdim: huge thanks to him
- i9505: fix adb root, sideload, exfat loading, time setting, touch and brightness
- i9500: fix flashing of cm-10.2 and AOKP 4.3 ROMs
- Galaxy S4 US variants: fix flashing of cm-10.2 and AOKP 4.3 ROMs
- i9100/n7000: add again the bootloop workaround (init swap from older version)
- fix /data/media toggle display was not correctly refreshed
- remove compute_archive_stats() file number calculation and replace with archive size for faster restores
- increase nandroid size check interval from 3 to 5 sec for slow storage devices (i9505)
- merge exclude google music cached files from nandroid backup
- merge new tar.gz wrapper into cm-10.1
- add pigz fast compression (-1) option + merge to cm-10.1
- add backup and restore of /data/media to external storage
- fix left free space warning when backup in compressed tar.gz mode
- fix partition sdcard menu not showing on devices without a second storage (cm-10.1 only)
- misc menus cleanup
- when key repeat is disabled: fix reboot when turning on screen after it was auto-blanked
- when key repeat is disabled: fix dim screen will not occur and only blank screen event was triggered
- fix dim/blank screen issues after reboot timer was reached and USB cable was connected
- fix various bugs with key handling through ui_wait_key()
- after screen is turned on, next touch event will now be considered (better touch response)
- more stable blank screen gesture actions (mainly on long press and move gesture)
- merge remove install update.zip from cm-10.2 to cm-10.1
- support new phones:
* Sony Xperia Z (yuga)
* Samsung S3 Sprint SPH-L710 (d2spr) - d2tmo repack
* Galaxy Exhibit Variants - SGH-T599N (codinamtr) - credits to @Unjustified Dev
* Galaxy Grand Duos (i9082) - credits @chotu222
* Galaxy S Plus - i9001 (ariesve) - thanks to @alireza7991
* HTC One V (primou) - credits to @doga.ozkaraca
* Huawei Acsend P1 U9200 (viva) - credits to @kiprap
5.11.2 (19.08.2013)
- ramdisk fixes for most devices to fix adb and sideload
- n7100/n7105/i317M: update to adam 2.7 kernel sensor free
- i9500: migrate to wanam sensors-free kernel v1.8 (fix boot into recovery delays, add back ntfs support)
- i9500: do not mount /data in postrecoveryboot.sh
- i9505: migrate to audism special repacked kernel (13.1) to fix poweroff bugs + update exfat kernel modules
- i9505 variants: revise ramdisk for stock based kernel edition
- i9100/n7000: update superuser to latest version
- i9100/n7000: stop patching kernel for emmc brick bug and replacing init for bootloop fix on unattended reboot
- n7000: do not include stock recovery and redbend_ua binaries to fit zImage size
- properly unmount /data after loading recovery settings on start
- properly unmount /data on recovery start for datamedia devices as per last cm changes
- mount /data before write_recovery_version() checks
- move advanced and twrp nandroid code to separate included file for easier code maintenance with cm sources
5.11.0 (17.08.2013)
- update to cwm 6.0.3.7
* Fix issue where android device manager, etc, dont actually wipe data.
--wipe_data issues via /cache/recovery/command will now completely format data.
- i9505: update to audism kernel v13 (smaller size to fit new ntfs/exfat format options) + new exfat modules
- jfltexx (i9505 cyanogenmod version) is now built properly using new TARGET_RECOVERY_INITRC in BoardConfig
- release i9505 cyanogenmod kernel based version
- n7100: update to adam kernel v2.7 for smaller size to fit ntfs/exfat format options
- endeavoru (HTC One X): do not use NTFS modules to fit recovery size
- i9500: remove fb2png and ntfs support because of small recovery size
- pico: remove exfat and ntfs support because of small recovery size
- clean up code when calling format_device() for sd-ext
- fix repacking script for toro, toroplus, grouper, protou
5.10.8 (14.08.2013)
- update to cwm 6.0.3.6
- merge cm sources: shrink cid
- fix text file formatting for dosfstools/Android.mk (PC to UNIX)
- sync sources
5.10.7 (10.08.2013)
- add option to toggle whole progress during backups for slow phones (hide size stats, progress bar and do not log backed up files)
- reorganize power options in a single menu
- update Aroma File Manager to latest sources
- port mkdosfs from TWRP + update to latest 3.0.16
- add mkextfatfs and mk_ntfs into recovery
- add support to choose format type for vfat storage: default, vfat, exfat, ntfs, ext2, ext3, ext4
- add preload partition on /etc/fstab generation: Now supports 'mount /preload' command in edify and recovery shell (by Ryuinferno)
- fix mount exfat/ntfs volumes under recovery for fs_type == auto
- fix partition sdcard auto for fstype
- merge cm-10.2 changes
* cwm: Add liblog dependency
* Add a recovery version variable, the releasetools want this now
* Use fstab v1 as a default
* Fixes for Superuser
* su installation and detection updates for 4.3
* su 4.3 detection fix
* update to v6.0.3.5
* add su daemon runner
* unset immutable bit on install-recovery.sh
* Don't treat link-time warnings as errors when linking with libbusybox
* Fix roots.c to use fs_mgr
* move key loading to verifier code. Add an option to verifier_test to load keys from a file, the way the recovery does.
* recovery: save logs from the last few invocations of recovery. Extends the last_log mechanism to save logs from the last six invocations of recovery
* recovery: ignore voldmanaged volumes
* update wipe data option confirmation
* merge "Revert "Use fstab v1 as a default."" into cm-10.2
- misc code cleanup
5.10.0 (25.07.2013)
- reorganize Backup and Restore menu:
* remove stock CWM Advanced Restore function
* move choose backup format to Misc Nandroid Settings menu
- add Misc Nandroid Settings option to disable nandroid size progress
- nandroid size progress is now disabled by default for specific phones (i9505)
- merge cm-10.1 changes:
* remove useless Fix Permissions menu
5.09.8 (24.07.2013)
- new time set function using TZ environement variable (should fix issues for some i9505 users)
- remove warning about selinux file_contexts (log only)
- Update CWM to v6.0.3.4
* merge more headless fixes from cm-10.1
- i9505 ramdisk: fix init.rc adb and sideload
- increase refresh backup size stats delay from 0.5 to 3 seconds (a proper fix will follow for i9505 users)
- fix some /data/media files could be included in TWRP backup mode
- It's summer time: open source many parts of PhilZ Touch
* settings file config
* all misc nandroid settings menu setup
* get rom name function to stamp backup folder name
* free browse mode and custom install zip folder
5.09.2 (21.07.2013)
- fix compiler warning in nandroid.c / nandroid_callback()
- remove non used virtual_keys images from ramdisk
- resync sources
- merge cm-10.1 changes:
* SELinux: don't suppress the "no file_contexts" message on the UI
* add --headless mode
5.09.1 (20.07.2013)
- add NTFS support for external storage
5.09.0 (19.07.2013)
- exfat-fuse: use existing external/exfat and external/fuse branches
- exfat-fuse: remove old implementation for prebuilt binary
5.08.9 (18.07.2013)
- compile mount.exfat-fuse static binary along recovery source to support exfat on cm-10.1 kernels
- fix Aroma File Manager compiling for non NEON devices
- clean up code (partition sdcard menu)
- fix broken touch after screen wake-up for some phones (i9500)
- resync sources
5.08.5 (11.07.2013)
- Compile Aroma File Manager (by amarullz) zip installer under recovery:
* either compile whole recovery, zip will be created at first pass
* or only compile aroma zip installer in two pass:
1- mmm bootable/recovery/aromafm
2- mmm bootable/recovery/aromafm/tools
* output: [target_out]/aromafm_out/aromafm_[DeviceID].zip
- detect aroma compatibility with non NEON devices during compiling
- use less conflicting flags: TARGET_NAME --> TARGET_COMMON_NAME
5.08.0 (07.07.2013)
- improve nandroid progress bar update
- fix recovery was not prompting when backup estimated size is larger than free space
- add ors backup support for twrp format requested by BillGoss
- ors backup: when no backup name is given, generate it using same way as nandroid operations (time stamp + rom name tag)
- support separated compiling for Loki patched devices (S4 AT&T and Verizon)
- i9505: revert some changes to fix time bug for some users
- Galaxy S4 US variants: repack around Audism stock JB 4.3 kernel v3 + Samsung exfat modules + revert use of mkefs for partition corruption issue
- fix missing break in set backup compression value menu (misc_nandroid_menu())
- misc clean up code
- sync latest sources
5.07.6 (05.07.2013)
- update version 6.0.3.3
- add exfat-fuse 1.0.1.362 / 2.9.2 optional support by enabling USE_EXFAT_FUSE_BIN CFLAG in BoardConfig (exfat support on cyanogenmod repacks)
- i9505: use Audism kernel v3 (Stock Samsung sources) to fix partition corruption without additional code and for better exfat support
5.07.1 (01.07.2013)
- i9100G support
5.07.0 (30.06.2013)
- fix "unknown volume for path /res/images/koush.png" on boot (do not search for a volume on ramdisk path)
5.06.8 (19.06.2013)
- fix bug introduced in v5.06.5: folder entries duplicated in some choose file menus (custom and twrp restore modes, regenerate md5 selection menu)
- by default, if /data/media/0 exists, it will be used as internal storage. You can still alter it in Advanced menu to force /data/media
5.06.7 (17.06.2013)
- Galaxy R/Z (i9103) support, thanks to Adam77Root
5.06.6 (13.06.2013)
- fix multi-zip flash "select/unselect all" persisting (static int select_all --> int select_all)
- add sdparted option to partition in ext4 fstype
- enable partition sdcard when non vfat fstype2 option is used in recovery.fstab
- merge cm-10.1 changes (6.0.3.2 Update 8):
* Merge "recovery: Fix adb backup" into cm-10.1
* Merge "Remove (un)mount option for datamedia partitions" into cm-10.1
* recovery.c: Fix the potential segmentation fault: Extral newline can trigger recovery segmentation fault
- Nexus 10 (manta): revert font changes since they were now merged in cm-10.1 device tree
- i9505 international: migrate to jfltexx device tree and repack with newer exfat modules
- Galaxy S4: support US variants
- misc code cleaning
5.06.4 (06.06.2013)
- fix touch repeat on capacitive virtual buttons for some devices
- Pico: ramdisk changes to enable backup size detection for mtd partitions (boot, recovery, misc)
5.06.3 (05.06.2013)
- HTC One Sprint and TMO variants support
- Galaxy S3 - T-Mobile (d2tmo): ramdisk changes to fix exfat (load modules using recovery-loader script)
5.06.2 (04.06.2013)
- Galaxy S3 - T-Mobile (d2tmo) - SGH-T999 support
5.06.1 (02.06.2013)
- HTC One: move to new m7ul device tree
5.06.0 (01.06.2013)
- support dual modem devices nandroid operations (dual sim, i9505)
- merge cm-10.1 changes: support version 2 (2048-bit e=65537) keys in recovery
- Nexus S/4G (crespo/4g): add mmcblk names to recovery.fstab to fix /data mount
- HTC Desire X (protou): support both protou-ics and protu-jb fstab
5.05.9 (31.05.2013)
- do not write backup size progress to log file
- show total time after restore job
- write backup path to log
5.05.7 (30.05.2013)
- use bigger 23x41 roboto font for HD devices (i9500, i9505, Nexus 10)
- do not uselessly statfs partition to refresh backup size progress if we're under NICE_INTERVAL (100ms)
- show backup compression 0% when backup is tar format and compression is disabled
- fix get time events during nandroid jobs and touch events
- universal scroll sensitivity and row height settings (fix hypersensitivity for HD devices)
- fix backup size progress for datamedia devices (special thanks to pickandwhammy for the time he spent in debugging this and providing logs)
- merge Get_Folder_Size() changes from twrp 2.5
- misc logging improvements
- small bug fixes
5.05.0 (26.05.2013)
- fix potential memory overflow during computing of size stats in backup
- fix /efs backup not possible for devices without /preload, unless preload menu was selected once
- fix custom nandroid and twrp backups for yaffs2 devices (do not force tar format on these)
- misc fixes for supporting more devices mainly during nandroid jobs:
* allow use of device2 for raw backup and restore operations (using dd/cat)
* better nandroid support when device names in fstab do not match actual mtd name (revert statfs for volume->device)
- revert cm-10.1 changes: write correctly fstab info in log (do not print to stderr)
- merge old custom_backup folder to cwm backup folder
- old .efs_backup and .modem_bin folders also should be moved to clockworkmod/backup
- .aromafm folder is now aromafm (no more hidden folder for this)
- add regenerate md5 sum option for nandroid backups (use with caution)
- revert inverting fstype and fstype2 (see github commit for more info on this)
- fix nandroid backup fails before generating md5 for /external_sd devices when card is not inserted/mountable (.android_secure check)
- fix falling back to system mount command will fail when calling ensure_path_mounted(filename)
- HTC Desire X (protou) support added
- HTC Droid Incredible 4G LTE (fireball):
* add support
* allow sd-ext and mount external sd in ext4
* allow backup/restore of /radio
- Galaxy S4 - i9505:
* support emmc partitions size detection during nandroid jobs
* fix exfat mount for some sdcards (thanks to chenglu)
- Nexus S/4G (crespo/crespo4g):
* allow raw + yaffs2 backups for /efs and /radio
* allow size detection for MTD partitions during nandroid backup
* fix device name to Samsung Nexus S
* repack with stock GB kernel to fix USB mount in recovery
- Nexus 10: enable efs backup and restore
- Galaxy Nexus (maguro/toro/toroplus): enable efs backup and restore
5.03.8 (20.05.2013)
- support HTC Droid Incredible 4G LTE - fireball
5.03.7 (19.05.2013)
- merge cm-10.1 changes: add getprop
- HTC One (m7) support
- i9505 fix graphics, date and cache/wipe issues (Big thanks to Chenglu for that)
- Samsung Nexus S (crespo) and Nexus S 4G (crespo4g) support
5.03.2 (16.05.2013)
- fix scroll down on touch issue when in double tap and highlight only modes
- support Galaxy Nexus GSM (maguro), Verizon (toro) and Sprint (toroplus), i9500 and i9505 Canada/Bell (jfltecan) and T-mobile (jfltetmo)
- merge cm-10.1 changes: add getprop
5.03.0 (12.05.2013)
- fix backup size progress in twrp mode
- improve code for backup stats during nandroid jobs
- display full backup stats (total size, compression ratio, elapsed time) at end of backups
- merge last cm-10.1 updates:
* fix nandroid cmd command did not load volume table
* support nandroid dump/undump commands
* nandroid backup command line still segfaults
* silent log when mounting /data/media
Touch:
- add 3 new color palettes (30 colors total): dimmer gray, yellow and gold
- add toggle for header custom color
- add toggle for battery and clock custom color
- line at bottom of menus will now have same color as menus separator lines
- set new defaults to header and menu text colors
- show backup/restore stats in color during nandroid jobs
- fix touch issue when exiting friendly log or blanked screen, and pressing on virtual buttons
5.02.3 (10.05.2013)
- fix root break for devices with shared recovery partition caused by Whil Wheaton update
- advanced backup size monitoring during nandroid operations
- prompt to cancel backup on low free space (% and absolute)
- live display size stats during backup: total data written, free space left
- support backup and restore of /misc partition for both CWM and TWRP operations
- prevent potential segfault when calling is_data_media_volume_path()
- merge cm-10.1 changes:
* remove adb sideload /tmp/update.zip after flashing to avoid second flash under some circumstances
- fix android_secure could not be backed up under some circumstances (ensure mount of sdcard)
- completely rewritten android_secure support: much simpler code
Touch:
- optimize cancel nandroid job action
- allow cancel yaffs2 nandroid operations
- allow dim screen timeout during yaffs2 nandroid operations
- fix set brightness and auto-dim screen timer for Nexus 7 and Nexus 10
- fix battery stats display for Nexus 10
- restore default actions of real device keys we fake for touch events
- correctly map device virtual keys to default recovery actions
- fix virtual buttons highlight color to match their line separator color (blue)
5.00.8 (05.05.2013)
- support Nexus 7 and Nexus 10
- clean code for non PhilZ Touch buils
- Merge cm-10.1 changes to cwm 6.0.3.2:
* recovery: fix sideload cancel" into cm-10.1
* make_ext4fs support
* auto prompt to root device when booting to main system
5.00.5 (04.05.2013)
- use device specific background images during compile process
5.00.4 (04.05.2013)
- touch code completely rewritten to support more devices (no more calibration needed)
- true touch scroll effect and much improved touch response
- secure touch: robust to wrong selections while scrolling + confirmation before any bad thing
- add option to completely disable touch
- options to restore Koush or PhilZ Touch background images
- restoring default backgrounds (Koush, PhilZ Touch) will apply live (a reboot was previously needed)
- fix touch on HTC Pico, HTC One S and HTC One XL
- restore support for device keys KEY_MENU and Home key (KEY_HOME, KEY_HOMEPAGE)
- add /preload support in twrp backup and restore modes
- mount /system and /data on Aroma File Explorer launch
- fix battery stats error in some circumstances
- i9100/n7000: update CWM Superuser to v1.0.1.8 (through zip installer)
- code cleaning, various fixes and optimizations
- force reset of recovery settings to v5: new settings file name
- backup file name is unchanged so that old settings can still be restored
Older Change History v1 to v4
4.96.6 (28.04.2013)
- support HTC One S (ville)
4.96.5 (27.04.2013)
- change event input handling code to support auto-interpolation
- auto support for devices built-in virtual keys
- enable key repeat for recovery virtual buttons (up/down): now they auto-repeat while pressed
- fix HTC One X nandroid backup was very slow (ramdisk changes)
- fix touch for new N71xx, T889, I317/M repacks based on wanam Adam 2.3 kernel to fix boot delay for non stock kernels
- misc bug fixes and code optimization
4.94.6 (21.04.2013)
- fix compile error for non touch version
- N71xx, T889, I317/M: repack on wanam Adam 2.3 kernel to fix boot delay for non stock kernels
- Fix touch support for HTC One X (endeavoru) and HTC One XL (evita)
- More fixes for HTC Explorer (pico) - work in progress
4.93.9 (18.04.2013)
- Initial support for HTC devices
* HTC One X (endeavoru) support
* HTC One XL (evita) support
* HTC Explorer (pico) support (big thanks to Nihar.G for this port)
4.93.6 (17.04.2013)
- fix reboot to bootloader for phones without download mode
- define default values for CWM Advanced Edition builds to non officially supported devices by PhilZ Touch
- no need to confirm sideload as it can be cancelled
- move philz settings file from /system to /data
- fix compile error for non PhilZ Touch version
- revert temporary assert fix for i9100/n7000 (ramdisk changes):
* do not mount /system in init.rc
* add needed entries in default.prop
- n7000: no more replace init binary to fix /data corruption bootloop issue (ramdisk changes)
4.93.2 (14.04.2013)
- share source for multi-zip installer
- add sideload and print commands support to ors as per TWRP specs
- always ensure sync before rebooting
- disable adb secure
- Update to CWM 6.0.3.1
* allow cancel sideload
* allow sideload install from /cache/recovery
* courier_extended_15x24
4.92.8 (05.04.2013)
>>True support for /data/media/0 for Android 4.2.2<<
First to introduce true JB 4.2 migration: live toggle between /data/media and /data/media/0
This implementation keeps compatibility with stock cwm while giving user option to force /data/media/0
When migrating from or to JB 4.2, you still need to move folders to/from /data/media/0. No one will do it for you
- fix early mount of /data for datamedia devices caused by write_recovery_version()
this could cause errors on some install scripts
- hide some external menus for devices without external storage
- fix Setup Free Browse Mode bug for devices without external storage
- fix Free Browse Mode could not browse up to the root for /data/media devices
- fix Misc Nandroid Settings menu regression for devices without external storage
- fix .nandroid_secure selection in custom backup and restore for devices without external storage
- no more mount internal/external storage when checking for ors script at startup
- do not report custom recovery logs to ROM Manager
- export error log on failure during boot installed packages
- make sure we have all the log posted by users
- misc bug fixes
4.92.3 (03.04.2013)
- properly set time for all recovery session: this will now apply to the time stamp of any file modified (logs, backups...)
- add Daylight Saving Time support
4.91.9 (03.04.2013)
- merge and fix fb2png source: now built as static binary and compatible with RGBX devices (Nexus 4...)
special thanks for this to McKael and a huge thumbs up to talustus for his great support
- silent failure when formatting non existing /sd-ext volume
- use statfs instead of stat in nandroid operations
- misc fixes
- i9100/n7000 zip installer: option to skip flashing superuser using philz_installer.cfg
- i9100/n7000: disable init binary substitution from older LSJ (aka /data corruption bootloop fix)
- i9100/n7000: update clockworkmod superuser to 1.0.1.7 (security fix)
4.91.5 (29.03.2013)
- Support Nexus 4 (mako)
- fix nandroid backup and restore for devices without /modem, /radio, /preload and /efs
- fix recovery functions for devices without external sdcard storage
4.91.2 (26.03.2013)
- fix touch code to support P31xx and N8xxx
- merge cm-10.1 changes:
- nandroid backup: save recovery log to backup folder
- minadbd: remove unnecessary header files.
- add external_sd and efs to /etc/fstab generated by recovery
- revert chmod in write_string_to_file()
4.90.8 (22.03.2013)
- multi zip flash menu will now show the validation menu on top of files list
- added option to select/unselect all zip files in the multi zip flash menu
- touch code fixes: more responsive touch gui on menus. Less skips on bottom virtual buttons
- merge cm-10.1 changes
- update to cwm 6.0.3.0
- fix About dialog was not displaying what it should for non PhilZ Touch builds
- non PhilZ Touch builds are now: CWM Advanced Edition
- fix bug: if Key Repeat was disabled, blank screen will hang up when screen back on
- add beta support for P3100, P5100 and N8000
- i9100/n7000: migrate from Chainfire SuperSU to opensource superuser from clockworkmod
4.89.4 (14.03.2013)
- New Custom Install Zip mode: set a default folder to start with + browse backward up to the root
4.88.5
- toggle menus are now formatted to device screen width (right align menu option)
- add 30mn timezone offset
- merge CM 10.1 commit: Fix segfault with dead symlinks in char** gather_files()
- add extra check for carriage return for get_rom_name function: ensures windobe noobs do not get stuck
4.88.2
- fix: ors backup could overwrite an existing folder and end up with mixed old/new backup images
4.88.1
- migrate from cm10 to new cm10.1 source
- fix fs_type2 is fs_type to maintain ext4 external storage compatibility with fs_type2 entry
- fix redefined MACRO for ITEM_APPLY_SDCARD
- merge cmw 6.0.2.9 changes (vchange only: ignored cwm commit: block google music cache from nandroid operations)
- fix: data partition was always restored in Advanced Restore menu
- in custom jobs: possibility to disable .android_secure from restore/backup as per TWRP/ors specs
- option to auto-restore recovery settings without a prompt screen on reboot
- ors support: fill ORS official specifications and more:
- optimize on boot check for openrecoveryscript command file
- add ors support for backup options: selected partitions, compression and md5 toggle
- fix: as per ors specifications, ors will now restore standard partitions when no options are set in script
- ors restore now supports TWRP and PhilZ Touch custom backup path
- ors-mount.sh: better support for path convfrom main system to recovery mount points
- ors backup target volume can be set by user in nandroid settings
- misc ors log fixes for special partitions ignored in cwm
4.87.6
- fix: show progress during TWRP backup and restore
- auto dim screen on timeout supported during backup and restore operations
- fix header menu could overlap battery stats if they are at 100%
- fix: restore custom rom zip failed because of left debug code
- fix: build custom rom zip from existing ROM would fail to restore if backup format was compressed
- huge performance optimize when building custom rom .zip from existing ROM (only backup needed partitions)
- fix useless edify incompatible code in custom rom .zip (alpha 06 files)
4.87
Backup and Restore:
- menu Custom Backup and Restore can now be accessed in main Backup and Restore menu
- support restore backups from /sdcard/0 (Android 4.2) in custom jobs and TWRP mode
- add support to sd-ext ext4 partition on external storage
- menu to delete custom and TWRP backup images
- auto-reboot option for custom backup and restore jobs
- set .android_secure path in custom jobs
- smart auto detect android_secure for stock CWM backup and restore operations
- fix preload was selectable in TWRP jobs (even if would not actually be processed)
- progress bar is no more overwritten by text
- time and battery stats are shown and refreshed during nandroid operations
- on successful or cancelled nandroid jobs, user background icon is restored
- on cancelled nandroid jobs, progress bar is correctly reset and user background icon is restored
GUI
- User configurable gesture actions
- gestures: double tap, long press/move, long press/lift, slide left, slide right
- always vibrate on long press/move action validation
- actions: show log, change brightness, blank screen, capture screen shot, launch Aroma File Manager
- default black theme without background icon
- toggle clock and battery on top
- header title will be auto-shortened to not overwrite battery and clock on lower res devices
- battery and clock will truly refresh indications every 15 sec
- user configurable dim screen timer
- user configurable turn-off screen timer
- manually adjust brightness (stock kernel doesn't support lower than 65, but recovery binary will accept 25 on custom kernels)
- when double tap mode is selected, you now really need to double tap the same menu to validate it
- menu Set Time Zone moved to GUI settings
- fix Moscow UTC time
Misc
- add support to sd-ext ext4 partition on external storage
- Move Clean before instal new ROM menu to Wipe Data/Factory Reset menu
- fix /system was left again mounted after start up and showing log
4.64
- fix: when disabled, virtual keys would still show for a fraction of a second on start
4.63
- preview support for slide right and double tap gesture actions
- friendly log mode now is final: logs are no more wiped when switching view for all operations (install zip, boot scripts, backup/restore...)
- fix: virtual keys will no more trigger an action at end of your scrolling if touched by case
- fix: virtual keys could remain highlighted under some circumstances
- fix screen capture index was back to 11 when it reached 100 (now it will be 999 photos and reverts to 001)
- fix: toggle background icon prompted for a key since 4.53
- fix: when toggle icon, screen logs are no more wiped
- fix: when change menu size, screen logs no more wiped
- deep revise of touch source to optimize and clean code (scrolling behavior is still same, this will be the next on my todo list)
- misc code cleaning
4.53
- fix user background image was not restored on restart
- TWRP backup and restore support, include full md5 sum support (single and multivolume, compressed and non compressed formats)
- support multiple efs backups in tar format (user request)
- now it is possible to restore from many modem.bin files under clockworkmod/custom_backup/.modem_bin folder to flash them (just name them *.bin)
- fix potential md5 error caused when restoring/flashing some modem.bin files
- fix recovery partition was restored when ever you restore something in stock Advanced Restore Menu
- custom restore option to browse from /sdcard/0 if it exists (this is a temporary workaround for Android 4.2)
- add ext4 support for mounting external storage (i9300 thread request)
- improved the friendly log view gui to include install zip, nandroid, boot scripts...
- enhance logging and user messages mainly in backup/restore operations
- remove useless support for browsable custom aromafm.zip folders (must be in default folder)
- many bugfixes + compiler warnings fix in code
- Clean Phone for a New ROM moved to Custom Backup and Restore
4.35
- Vulnerability fix: setting a fake/corrupted png file as background resulted in a bootloop into recovery
- Vulnerability fix: cancel nandroid operations could result in data corruption if user attempted to directly delete backup from menu or forced a reboot
- Friendly Log View: toggle during install of zip files (manual, multi, on boot) and forced when Show Log from advanced menu
- Pause on show log: Forced in Show Log from advanced menu. Always disabled for multi zip flash and on boot, toggle for manual zip installs
- Install zip menu order changed so that install from internal/external are nearby
- Move reset / save recovery settings to main PhilZ Settings menu
4.31
- add slide left to capture a screen shot from any active menu
- optimized code for cancel nandroid operations
4.24
- Back button now will cancel nandroid backup/restore operations (tar+dedupe) and custom_rom.zip operations
- merge CWM 6.0.2.8 changes (credits to Koush)
4.22
- multi-zip flashing from custom set locations
- after installing a new ROM that wipes recovery settings, on next reboot, you are prompted to restore them from a backup if you have done one
- New menus separator lines that you can show/hide, set colors and transparency. Useful for solid color themes, like Black
- fix default menu highlight transparency was set to a wrong default value
- code optimizing for file checks
- mix code optimizing
4.01
- show / hide bottom virtual buttons
- set number of bottom log rows to show
- misc compiler warning fixes
4.00-b39
- custom background image (png in 350x735 pixels)
- toggle background in preset 27 colors
- toggle background icon
4.00-b35
- fix /preload was always restored during nandroid operations
4.00-b34
- fix preload was again processed on each nandroid backup
- fix nandroid backup name was exiting on first checked missing key and using default noname
- fix output log for backup rom name was wrongly reporting error to open build.prop
4.00-b33
- code cleaning
4.00-b32
- life in color edition
- fix: resetting settings to default now is applied without the need to restart recovery
- small code optimize
- fix logging for file parser and load/save settings
4.00-b30
- nandroid backup/restore with gz compression using pigz (multi cpu threading): toggle between low (3), medium (6), high (9) or disabled
- fix when preload toggle was enabled, preload was processed in custom backup even if it is not selected
- complete rewrite of gui settings toggles: new menus display
- new toggle for touch accuracy
- more menu height settings (useful for high res devices)
- more scroll sensitivity settings
- all settings are now saved to a single .ini file you can edit (detailed values will follow)
- possibility to reset all values to defaults, to export and to import them to/from sdcard
- Nandroid Advanced Restore menu now shows that /preload will be processed with /system
- Misc Nandroid Settings now can also be accessed from Nandroid Menu
- code cleaning and fix compiler warnings
- add show really progressing bar during nandroid restore operations
- fix pigz as static library
- i9100/n7000 ramdisk: fix getprop hack script (thanks to a3955269)
4.00-b22 Recovery (CWM 6.0.2.7 based)
- unmount /system on recovery start to fix some install zip issues
- fix no time zone file message on start when no user time zone was selected
- i9100: fix error 7 was back (better fix later)
4.00-b21 Recovery (CWM 6.0.2.7 based)
- Completely new Custom Backup and Restore menu
- Custom back and restore job list: backup and restore freely any partition combo from old nandroid folder or new custom_backup one
- Restore modem as custom modem.img file or modem.bin (found in Samsung tar roms)
- Backup EFS in tar (overwrite old backup) + img formats (time stamped)
- Restore EFS from either tar or img files
- All backup and restore tasks are now built completely on native nandroid functions: no more calling of many shell scripts
- One shell script only left to handle raw backup and restore of ext4 partitions (not supported by cwm, I actually use it only for efs.img and restore of modem.bin files)
- New Nandroid Settings Menu: improved UI with settings immediately reflecting on menus
- New TimeZone menu: friendly UI (idea from TWRP) and simpler code to fix issue where it could sometimes fail to write config file
- pigz library: big credits to TWRP team (will be used for new lightning fast compressed backups)
- fix ors mount script for phones without external sd
- remove useless run of ors mount when not started from boot
- fix some partitions could be formatted despite no backup file to restore when md5 check was disabled
- small bug fixes and code cleaning
3.99 Recovery (CWM 6.0.2.7 based)
- Fix flash modem function failing when searching *.img files instead of *.bin files
- Merge sk8erwitskil changes: fix special backup and restore functions for devices without external sd
- Second pass at fixing write error of toggle time zone appearing on some conditions
- Make custom_rom.zip from current ROM or from pre-existing nandroid backup
- Ensure tar format during create custom_rom.zip operations
- Add sync() at end of special backup and restore functions (in case of... + fix lag on exit menu)
- Merge cwm 6.0.2.7 changes
- nandroid: Fix nonexistent backup format type bug.
- do not attempt to back up .android_secure if it is on /data/media
- Add Home button to select for i9300/n7100
- Edit i9300/n7100 ums lun file path
- Add rom name to nandroid backup path: fetched from
- ro.modversion=
- ro.romversion=
- ro.build.display.id=
- noname if above are empty
- Fix the getprop issue in i9100/n7000 JB leak, aka error 7 (early mount /system in recovery.rc)
- Code cleanup
3.81 Recovery (CWM 6.0.2.3 based)
- merge last cwm 6.0.2.3 updates from jellybean cm10 branch
- remove wipe battery stats
- better implementation for setting default backup format
- fix crash in recovery that occurs during backup (popen.c)
- dedupe: fix buffer overflow
- i9300: fix vibrator not working
- n7100: fix exfat support
- n7100: fix aroma file manager failure
- n7100/i9300: fix ramdisk/kernel used: now based on stock kernel/recovery: fixes potential exfat and aroma issues
- enable mount external sd over usb in recovery for /data/media devices
- complete re-write of Special Backup and Restore menu and functions: more efficient code to easily add new backup/restore jobs
- complete rewrite of toggle gui menu code: 4Kb size gain on recovery binary + more efficient code performance wise
- new Misc Nandroid Settings: toggle md5 checksum, toggle /preload processing, set time zone
- no fail of nandroid job on /preload error (auto skip on error)
- set time zone for nandroid backup path moved to new Nandroid Misc Menu
- add credits to special backup and restore sh scripts
- fix mount /system error log on recovery start
- key repeat toggle now applied live, no more need to restart recovery to take effect
3.75 : PhilZ Touch 3.63 Recovery (CWM 6.0.1.9 based)
- Complete rewrite of toggle gui menu code: 4Kb size gain on recovery binary + more efficient code performance wise
- New toggle to set time zone: correct time can now be set for nandroid backup path and recovery log
- Merge cm10 jb changes: set default backup format to tar
- Fix mount /system error log on recovery start
- Key repeat toggle now applied live, no more need to restart recovery to take effect
3.72 / 3.73 : PhilZ Touch 3.40 Recovery (CWM 6.0.1.9 based)
- 3.72 ---- > 3.73: code cleaning for universal exFat compatibility
- Support exFAT for external sdcards in recovery: no +4Gb size file limit like fat32, better optimized for 64Gb cards
3.70 / 3.71 : PhilZ Touch 3.39 Recovery (CWM 6.0.1.9 based)
- 3.70 --> 3.71: added format /preload on special wipe before install new rom
- Merge Koush last changes: (+ add credit inside code source)
- dedupe: fix buffer overflow, the length of key was incorrect, 4.2's libc detects the overflow and crashes
- fix bug where you cannot partition internal sd
- add wipe all before install ROM: wipe all user data + wipe system
- second pass at fixing partition sdcards menu by PhilZ, now it should work as supposed
3.65 : PhilZ Touch 3.35 Recovery (CWM 6.0.1.9 based)
- Completed ors implementation: added script started on boot, with same function as custom ors (simpler code than previous versions)
- fixed ors-mount.sh support for phones without /emmc
- goomanager support fixed for phones without /emmc
- misc permissions fixes for recovery scripts
3.62
- permissions fixed: now special backup and restore functions work again
3.61 / 3.62 - 22 nov 2012
- Update to cwm 6.0.1.9 + PhilZ Touch 3.34
- Add nandroid /preload backup & restore support
- Add option to flash modem image from recovery
- Fix Aroma File Manager path for devices without /emmc mount point
- Fix: mount sdcards before launch aroma as some times we did not have access to other sdcard under aroma
- Fix kerne/efs backup & restore for phones without /emmc
- Optimized backup/restore status log for kernel/efs/modem: now showing true success/failure based on exit code/stderr from CAT
- One ORS code is enough for custom and at boot scripts
- Fixed ORS backup job log
- Merge cm10 branch updates:
- Add support for doing a true ext4 format of /data on /data/media devices.
- Shorter confirmation menu if compiled as Philz Touch
3.5 - 18 nov 2012
- Update to new Touch PhilZ 3.25 cwm 6.0.1.8 based recovery
- Option to flash kernels (zImage you rename to *.img file) directly from recovery
- Backup kernels now supports multiple time stamped backups
- ORS/EFS/Kernel backup/restore scripts support universal mount points/path through recovery.fstab: multi-device compatibility
- Major update to code for multi-device support (compile from source code for any phone)
- Now, philz-cwm6 recovery is open source (see post 1)
3.43
- Support exFAT for external sdcards in recovery: no +4Gb size file limit like fat32, better optimized for 64Gb cards
- ADB now starts with root access
3.39
- added format /preload on special wipe before install new rom
3.38
- second pass at fixing partition sdcards menu
3.37
- add wipe all before install ROM: wipe all user data + wipe system
3.36
- Merge Koush last changes: (+ add credit inside code source)
- Dedupe: fix buffer overflow, the length of key was incorrect, 4.2's libc detects the overflow and crashes
- Fix bug where you cannot partition internal sd
3.35
- completed ors implementation: now script started on boot, with same function as custom ors (simpler code than previous versions)
- fixed ors-mount.sh support for phones without /emmc
- misc *.sh permission fixes on compilation
3.34
Merge cm10 branch updates:
- Add support for doing a true ext4 format of /data on /data/media devices.
- Shorter confirmation menu if compiled as Philz Touch
3.33
- Add nandroid /preload backup & restore support
3.32
- Fix: mount sdcards before launch aroma as some times we did not have access to other sdcard under aroma
3.31
- edited recovery.fstab for some devices (i9100 / n7000) to include /modem
- Clean ORS code + Add modem flash menu
- for i9100 / n7000, edit recovery.fstab and add this line
- /modem emmc /dev/block/mmcblk0p8
- Updated Readme.md file with Special backup and restore menu instructions
- Rename EFS/Kernel backup menu to Special Backup Menu
3.30
- One ORS code is enough for custom and at boot scripts
- Fixed ORS backup job log
3.29
- Fix kerne/efs backup & restore for phones without /emmc
- optimized backup/restore status log for kernel/efs: now showing true success/failure based on exit code/stderr from CAT
3.28
- First alpha / private release for i9300
- Fix Aroma File Manager path for devices without /emmc mount point
3.1 - 09 nov 2012
- Update to new Touch PhilZ 3.0 cwm 6.0.1.5 based recovery
- Completely revised new touch code: fixed old skips and jumps while scrolling
- Much more smooth behaviour after scrolling
- Even less risks of wrong validation of menus on touch while scrolling (can we say 0 risks?)
- GUI settings are now saved to /system/philz-cwm6 folder instead of /data/philz-cwm6: this is to fix some mount issues on early start and to maintain settings after a factory reset
- Added toggle key repeat for vol up/down keys (only feature needing recovery restart to take effect)
- Huge code cleaning and misc bug fixes
- Added install from sideload code based on last cwm6 update
- Moved sideload menu to install zip menu
- Added confirmation before "Fix Permissions" and "Install from sideload"
3.0 - 02 nov 2012 (i9100 only)
- Introducing PhilZ Touch 2.0 recovery (clockworkmod v6.0.1.5 based)
- touch interface: toggle 3 touch modes: FULL TOUCH, DOUBLE TAP to validate and SEMI TOUCH (scroll but no touch validation)
- very stable and safe scrolling in full touch mode: makes it hard to wrongly validate a menu while scrolling
- when you set full touch mode, it defaults to optimized settings for menu height and touch sensitivity (you still can alter them manually later)
- adjust scrolling touch sensitivity in 6 settings
- adjust menu height in 6 settings
- toggle vibrator on/off when using bottom virtual buttons
- toggle aggressive mode to try stealing bottom space for logs (may or may not work as expected depending on screen resolution and menu height)
- backup/restore EFS and Kernel
- browse phone with root access using full GUI in Aroma File Manager: checks first in default locations to give you direct access to your scripts, else you are prompted to browse for scripts in sdcards
- support openrecovery script in 3 modes using a smart one touch menu: looks first at goomanager scripts, then in default custom scripts location and finally prompts you to browse for scripts in sdcards
- show log menu modified to have its own screen: useful for the S2 because of its low resolution. Now, you can read teh screen logs even when having big menus
- reorganized menus layout
- miscellaneous fixes in initramfs for the kernel
2.7 - 07 oct 2012
- now using CWM6 based custom touch recovery 6.0.1.4 (internal build 1.15) * Siyah source code *
- DUAL USB MOUNT in recovery is now supported * Special thanks to [email protected] *
- semi-touch interface with right slide to select disabled for safety: use slide up/down and left for back
- include bottom virtual buttons for easier navigation
- revised GUI with bigger fonts and larger menus for better readability
- transparency effects in recovery menus
- fixed backup format selection menu in original Koush cwm6 (was echoing previous menu)
- added power off and reboot to download mode options in recovery menus
- battery % level displayed in recovery
- fixed some menus spelling and aspect in original recovery
2.5 - 22 sept 2012
- Introduced brand new original feature: MULTI-bootanimation scrolling on each boot. See post 2 for details on how to use this new feature
- No more true insecure kernel (ro.secure back to 1), ADB root in recovery is through cwm adbd like other custom kernels
- CWM updated to last 6.0.1.4 non touch: touch vcoming later
- CWM6 is now built from source, to avoid issues with dynamically linked binaries ** Big thanks to - Tallustus from Team Skyfire
2.0 - 14 sept 2012 (i9100 only)
- Now built automatically through scripting, no manual editing
- Added fake getprop to show custom kernel prop *credits to Siyah*
- Fixed missing /res/images fota png in ICS 4.0.4 (no bad consequence in any case)
- Minor cosmetic changes in scripts, mainly properties
- Added custom boot animation support:
- /data/local/bootanimation.zip
- /system/media/bootanimation.zip
- /data/local/bootanimation.bin
1.0 - 09 Sept 2012 : Initial release (i9100)
- Clockworkmod v6.0.1.2 recovery - Permanent
- Pure stock based kernel: only initramfs changes
- Flash through Odin or in Stock Recovery (no yellow triangle)
- Ready for root
- ADB root in recovery: just wait about a minute to activate
- Init.d and customboot.sh support
FAQ
1- what happens if I wipe/format/factory reset my data/media device?
format /data: only data is wiped, exclude /data/media:
Code:
cd /data ; for f in $(ls -a | grep -v ^media$); do rm -rf $f; done
format /sdcard : only /data/media or /data/media/0 (depending on setting you choose in Advanced menu) is wiped
Code:
rm -rf /sdcard/*
rm -rf /sdcard/.*
format /data and /data/media: will issue a true format on /data volume, obviously killing /data/media
Factory reset: will also preserve /data/media (rm -rf)
Clean to Install a New ROM: will do a factory reset (format /data, /cache, /datadata and sd-ext) + format /system +/- /preload. Your system will not boot until you install a new ROM
2- I backed up my data and I cannot find it when I boot into phone
Stock CWM and CM Updater app are using a non conventional linking for internal storage: internal storage is linked as /sdcard/0
PhilZ touch supports true /sdcard paths by linking it to either /data/media or /data/media/0
/sdcard/0 has no meaning in PhilZ Touch unless you set it to /data/media
By default, if a folder /data/media/0 exists, PhilZ Touch will default /sdcard to it, else it will use /data/media.
The advantage is for all stock +4.2 users: they can directly access their backups from /sdcard, while in main system and see them on PC in MTP mode.
You can override that setting in Advanced Menu and force it to /data/media or revert to /data/media/0
I recommend moving all your old cwm path to /data/media/0/clockworkmod and set sdcard to /data/media/0 unless you are switching between stock CWM and this mod or you need CM Updater app
To sum it up: for stock +4.2 rom users, keep default (/data/media/0). For CM users, if you frequently use CM Updater to flash in recovery, force /data/media
3- I come from stock CWM/TWRP and PhilZ Touch cannot see my backups
Read Answer 2
4- Aroma file manager doesn't start when I double tap screen
Read the guide to install aroma file manager.
Path changed in v5!
Read the /data/media/0 faq 2
5- CMUpdater cannot flash downlaoded files
If you get a /sdcard/0 error, it means you have /sdcard set as /data/media/0 in recovery
The reason is that CM app doesn't support /data/media/0 and is faking recovery with a /sdcard/0 implementation
You still can alter the setting and force it to /data/media in Advanced menu. This will give full compatibility with cwm, CM roms and CM Updater
6- How to flash a boot.img or recovery.img file?
- Put your boot.img or/and recovery.img files under a subfolder in clockworkmod/backup on sdcards
exp: /sdcard/clockworkmod/backup/cm-10.1-nightly_20130713/boot.img
- Navigate to Backup and Restore / Custom Backup and Restore / Custom Restore Job
- Unselect all partitions except boot and/or recovery
- Select >> Start Custom Backup Job <<
- Browse to your backup location until your cm-10.1-nightly_20130713, and select any file inside it
- You are done
7- My backups take a long time to complete
First, make sure you set compression to fast or low. Low compression setting gives around 30% compression with quiet no impact on speed. Rising compression value makes backups extremely slow with very little gain on space.
Stock CWM uses exfat fuse but without any buffering of writes. The end of it is a non usable thing for any backup because of an incredibly slow write speed.
TWRP uses exfat fuse binary to do the backups + caches tar writes to improve speed. This could cause data corruption on some devices.
PhilZ Touch uses patched kernel with native exfat support (static mode) for Samsung devices and soon other brands. This is supposed to be the faster and safest way.
However, it seems to struggle on some devices because of the logging mode used by CWM
Solutions:
- hide progress bar in Nandroid Settings menu: this will dramatically improve speed for many devices
- do not use exfat
- change exfat card to another brand. Ask in forum what people are using with good speed
- some users reported a real slow down when card/device is hot. Let your phone rest from intensive read/writes before starting a backup
- switch to another recovery like twrp if you cannot live with it. PhilZ Touch is compatible with TWRP and can backup/restore twrp format
8- You think you found a bug?
- Make sure your issue is recovery related
- All external sdcard issues: first format in PC with primary partition, tons of people are formatting as logical and come cry
- Reproduce your issue and while in recovery:
- Go to Advanced / Report Error
- Copy the /sdcard/clockworkmod/philz_recovery.log file and attach it here
- Give detailed info about your issues
- Without these, there is little chance I can help you, so, do not get mad if I do not answer
9- Loki things
Locked bootloader? How to lokify before flashing:
In Advanced Menu / Toggle Loki Support : enable auto loki
Flash the zip file and you are done
PhilZ Touch recoveries that come in a zip file format AND released after v6.01.2 have a script in the zip to lokify the recovery image during flash even if you are coming from older recoveries or TWRP (thanks @Wootever)
The included recovery.img in the zip is not lokified, it will be lokified during flash
If you are using a new CWM or PhilZ Touch with auto-loki enabled, please disable it before flashing my zip files to avoid any issue with double lokifying, if ever possible!
Unlocked bootloader users can still extract the recovery.img file and restore it from inside recovery:
put recovery.img in /sdcard/clockworkmod/backup/philz_update/recovery.img
In Custom Backup and Restore menu, unselect all except recovery
validate to browse to the update recovery.img
done
10- Assert error 7 on device name when installing roms and updates
Start of v6.02.2, recoveries are based on cm-11.0 (KitKat) device tree.
In all zip installers, you have a file called update-binary. It is the executable that will process and interpret all commands in updater-script, which will do all actions.
Older update-binary files cannot access system assert props on kitkat based kernels.
Fixes:
- edit your updater-script in zip file and remove all assert lines checking for device name. Use notepad++ or a linux editor
- manually change your update-binary in the zip with a new one you take from a cm-11.0 release
- revert to an older recovery before 6.02.2
- ask your rom releaser to update his update-binary
Note: start of 6.09.6, this error is fixed. However, you can end up with error in FAQ 11
11- various status 7 errors: format() expects 5 args, got 4 - set_permissions errors...
First read FAQ 10
Start of 6.09.6, recovery will analyze the update-binary that comes with your zip package. If it detects an outdated version, it will be automatically replaced during flash.
This will fix all assert getprop errors discussed in FAQ 10 (often used to check if the zip is meant to be flashed on your device)
However, doing so, can expose you to a bunch of new errors if the update-binary is +2 years old. In that case, the updater-script code used could not match the new update-binary:
The error "format() expects 5 args, got 4" is caused by not using the below new format command in updater-script:
format(fs_type, partition_type, location, fs_size, mount_point)
Click to expand...
Click to collapse
exp:
Code:
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
The error due to failure on set_perm is caused by using 2 years old update-binary
New ones will abort installation when setting permission fails on any file, while it was previously allowed to continue
Fixes:
- start of 6.15.4, PhilZ Touch added an option to force using the update-binary that comes in your zip. It will make it work except for the assert for device name error. However, that error is very easy to fix by any one (see FAQ 10). The option doesn't stick on reboot, you have to manually set it when you flash such files. It is done on purpose to keep you warned about potential risks using such bad scripts often coming from a copy paste procedure
- hammer your ROM maker to keep up to his time, and look closer at his scripting and update-binary engine used
12- Time fix for Qualcom Chips and other devices
On many Qualcom devices, setting the time is disabled on different levels, depending on the device
New PhilZ Touch versions added a workaround to this limitation. The fixes do not modify in anyway the RTC flags in kernel, as it is not recommended by Qualcom
- Qualcom Time Daemon:
This is the recommended option. It will load the time daemon from /system and will keep your recovery time in sync with ROM.
However, many CM/AOKP/Custom Roms do not have a proper implementation of the daemon. Ask your ROM dev to properly implement Qualcom proprietary binaries and RTC permissions.
- Use RTC Time Offset:
This is the second workaround, recommended for ROMs without proper time daemon. You have to enable the option. After that, it will ask you to setup the actual time/date manually. Do it AND Validate your choice to apply the actual time. Enabling the offset mode without manually setting correct time AND validating your option has no effect!
- Try Force Persist on Reboot:
This is your last choice, if all other options failed. Disable previous 2 options and enable this one. You will need to setup time/date manually AND validate your choice. Else, it won't have any effect.
- Normal/manual mode: Non Qualcom based devices, can just use the default mode to set time/date manually
13- My ROM maker advises another recovery
If an installer script cannot run on PhilZ Touch, it won't run on CWM. PhilZ Touch is just a CWM mod in that regard. Installer is not modified
Rule of thumb: If a ROM cooker says "YOU MUST USE A GIVEN RECOVERY", be sure there are bugs in his work
A properly formatted updater-script, shell child scripts or aroma scripts should be able to run on any recovery as it should call real blk device paths and not "pre-defined" mount points
Mount points WILL vary from recovery to another and maybe from a version to another. Relying on them is a bad idea
Also, many do miss proper edify scripting rules:
- /sdcard is a symlink, not a folder since years now (/data/media)
- you cannot extract without mounting first
- you must create your paths. Installer won't be verifying you did so
- you cannot mount vold paths (sdcard, usb storage...) by calling the mount point in a shell script. Look at your fstab under recovery to understand why
If a rom maker has issues to understand this, he can ask for help here or in an edify scripting thread
14- F2FS <-> EXT4 format migration
Under "mounts and storage" menu, if "toggle f2fs <-> ext4 migration" is enabled, whenever we try to format an ext4 or f2fs partition, we get a prompt to convert between f2fs/ext4
To convert /data on /data/media devices, we must as always select the "/data and /data/media" menu
Nandroid implementation to migrate your data/ROM from ext4 to f2fs:
- backup your existing data
- in "mounts and storage", format the partitions you want to convert to f2fs
- restore your data
- on restore, if both backup image and target partition has different fstype and fstype is either ext4 or f2fs, we favour target devise fsytpe (data migration)
This is awesome work buddy. Never seen this before..Great work my friend. You need clapping.
BTW, can I load it in MY galaxy R..?? Using CWM V 6.0.0.1.??
Re: [22.03.2013]Clockworkmod Advanced Edition / PhilZ Touch 4.90.8
Look at the dev info thread to port/compile it for any device supported by cyanogenmod
Sent from my GT-I9100 using Tapatalk 2
Updated post 1 with currently supported devices by me
This list can grow up as people would like to
Is it possible to add support other devices?
Congrats on the official thread Phill ! Your place belongs here. :angel:
Phill has been supporting the G Note community for almost a year now and he has special expertise with Samsung devices, more so with issues like brick bug, root, stability, battery, ever - growing features in the recovery menus, dealing with bootloops, even kernel issues etc.
Im sure his work will be well appreciated over a wider area on xda soon.
Of course he will support more devices as he gets more time and requests.
Keep it up Phil, you have been the best developer for Samsung community.
Phil love your work and your support man..
Lastest build great on LSD firmware on SGS2..PS Using the original build with SuperSU
You're the best Phil keep it up:good:
One question though why the new version included only two bases?
galaxynotes said:
You're the best Phil keep it up:good:
One question though why the new version included only two bases?
Click to expand...
Click to collapse
what is 2 bases?
Phil3759 said:
what is 2 bases?
Click to expand...
Click to collapse
Your latest version were for these two only :
DDLSC-ODD
XXLSZ-OXA
I'm not requesting anything just wondering why
Sorry, this the dev thread
As noted in post 1, support for specific devices goes into their respective thread
Skinny MIUI is all about preserving the good; Working premium drivers for Camera, CPU control, Notification LEDs, Bluetooth, FM Radio etc. while resolving what is bad in the stock offering.
All deletions assume the user has absolutely no interest in being part of the Xiaomi ecosphere. Leave now if that is not you.
This guide applies to MIUI stable versions 7.1.1 thru to 7.2.5 only. Developer, Beta or Eng versions are not good candidates.
STAGE 1:
Boot.img mods: (this is not creating a custom kernel!!!)
The stock boot.img is unpacked, init.d support added and many entries that are not relevant to our hardware removed.
Disabling lines trying to load non-existent services from init.rc, init.mt6795.rc and ueventd.rc etc. stops a bit of churning on each and every boot and frees up a bit of RAM.
There are intentionally no other tweaks contained within the boot.img. All tweaks are done in init.d scripts accessible outside the boot.img.
Note: This boot image made from 7.1.4 will work back to ver 7.1.1 and forward to 7.2.50 / 6.3.31 and is superior to the stock boot images contained in those ROMs.
At this point you can flash the modified boot.img to your phone if you already have a stock MIUI 7.1.1 to 7.2.50 installation that you are going to keep.
If you are going to do a clean install, replace the boot.img in your ROM zip file with this modified one. (backup the original first)
The boot.img is found here: (Now links to folder with all versions available)
https://drive.google.com/folderview?id=0BwdRTuyj12_yRk9Kcm1pZkxuZzg&usp=sharing
STAGE 2:
Full install:
I recommend you install my TWRP 3.02-2 version from here:
https://drive.google.com/open?id=0BwdRTuyj12_yWWp0SUpGV1pzT1k
Before installing your chosen ROM:
Check that the updater script found: \META-INF\com\google\android\updater-script is not going to install Preloader, Uboot (lk), Recovery or logo partitions. If so, edit the updater-script to prevent this happening. This is to reduce the risk of a soft-brick or being locked out of your phone.
Do a factory reset in TWRP (wipe Data, Dalvik, Cache) before installing any ROM.
Install your chosen ROM. Trying to slim down the ROM before install is an arduous affair which tends to end in bootloops so we leave the original ROM alone in this respect..
Do the install without connecting to mobile or WiFi networks and just skip at screens prompting for network connectivity and creating accounts.
Reboot into TWRP once finished with the initial Setup to avoid Recovery from being deleted on first boot.
Install an updated SuperSU zip package from TWRP recovery - V2.46 to 2.71 work equally well.
Do not install a root package other than SuperSU - most online ones are malware!
Update the outdated and incomplete Busybox installation. I have created a TWRP flashable zip to upgrade to the latest version 1.25.0. This is the second edition which has better binaries and no longer creates symlinks to busybox commands.
https://drive.google.com/open?id=0BwdRTuyj12_yd0s1QmNLRzdveFk
Now install a root capable filemanager (Root Explorer or Total Commander recommended). Open it and gain root permissions. Open /etc/perfservscntbl.txt in a text editor and edit as follows:
Code:
CMD_SET_CPU_FREQ, SCN_APP_TOUCH, 403000
CMD_SET_CPU_CORE, SCN_APP_TOUCH, 1
This will lower the number of cores used and the frequency at which it runs when a screen touch is detected (referred to as Touch Boost) Changes are activated on reboot.
Now create a file named 01_tweaks in the /etc/init.d folder. Change the permission of the file to 0755
Tips on creating scripts:
The EOL(end-of-line) characters must be in Unix format - not Windows. Make sure you are using a text editor that saves in Unix format.
Note also that many script files need a blank line at the end to work correctly. Get in the habit of always doing this whether needed or not.
Any line starting with a # character and anything after a # character on a line is not processed and is referred to as "commented out"
Script files must start with the header #!/system/bin/sh as the first line.
Init.d scripts are processed in alpha-numeric filename order hence the common usage of 01_xxx, 02_xxx format for names.
Copy these lines into the 01_tweaks file: Note: Different values for 2.2GHz cpu and freq limited operation.
Code:
#!/system/bin/sh
### Tweak Interactive CPU Governor
echo 806000 > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
echo 85 > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
echo "90 403000:80 806000:85 1326000:90 1625000:95 1950000:99" > /sys/devices/system/cpu/cpufreq/interactive/target_loads
echo 32000 > /sys/devices/system/cpu/cpufreq/interactive/timer_rate
echo 10000 > /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
echo 15000 > /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay
echo 20000 > /sys/devices/system/cpu/cpufreq/interactive/timer_slack
### Tweak IO Scheduler
echo deadline > /sys/block/mmcblk0/queue/scheduler ### choose between cfq, bfq or deadline
### Enable this line if using cfq or bfq scheduler only
# echo 0 > /sys/block/mmcblk0/queue/iosched/slice_idle
echo 256 > /sys/block/mmcblk0/queue/read_ahead_kb
### Enable zram swap
# echo 1073741824 > /sys/block/zram0/disksize ### 536870912 = 512MB 1073741824 = 1GB
# /system/bin/tiny_mkswap /dev/block/zram0
# /system/bin/tiny_swapon /dev/block/zram0
### Tweak Entropy to avoid regular depletion of available pool
echo 512 > /proc/sys/kernel/random/read_wakeup_threshold
echo 1024 > /proc/sys/kernel/random/write_wakeup_threshold
#Tweak for wifi router connection issues
#echo 1 > /proc/sys/net/ipv6/conf/wlan0/disable_ipv6
### FSTRIM: Enable once after installation is finalized and then monthly ##### needs an updated busybox installation to work
# busybox fstrim /data
# busybox fstrim /cache
# busybox fstrim /system
Options: Add / replace lines to do the following:
1. freq limit a 2GHz cpu to 1781MHz (recommended setting)
echo "90 403000:80 806000:85 1326000:90 1625000:95 1781000:99" > /sys/devices/system/cpu/cpufreq/interactive/target_loads
echo 1781000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1781000 > /proc/cpufreq/cpufreq_limited_max_freq_by_user
2. Full speed 2.2GHz cpu
echo "90 403000:80 806000:85 1326000:90 1664000:95 2158000:99" > /sys/devices/system/cpu/cpufreq/interactive/target_loads
3. freq limit a 2.2GHz cpu to 1885MHz (recommended setting)
echo "90 403000:80 806000:85 1326000:90 1664000:95 1885000:99" > /sys/devices/system/cpu/cpufreq/interactive/target_loads
echo 1885000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1885000 > /proc/cpufreq/cpufreq_limited_max_freq_by_user
4. Add a limit to the maximum number of cpu cores allowed to come online (for possible battery saving maybe...)
#Limit max cpu cores available (range 2 - 8)
echo 4 > /proc/hps/num_limit_low_batt
echo 4 > /proc/hps/num_limit_power_serv
echo 4 > /proc/hps/num_limit_thermal
echo 4 > /proc/hps/num_limit_ultra_power_saving
Edit /system/build.prop. Change the line: ro.sf.lcd_density from the default 480 to a value between 400 (everything smaller, more on screen) to 520 (everything larger, less on screen) to suit your taste and eyesight. You can test this out first by issuing the wm density command in a terminal app. e.g wm density 440 will immediately change the density to 440dpi, wm density reset will put it back to whatever the build.prop setting is. Adjust the text size in Settings in conjunction with this to get the best result.
At this point you have a functional set of tweaks that are all tested and proven to provide a battery and performance improvement. There are a lot of detrimental or placebo tweaks out there so be a little bit discerning in what else you add to these tweaks - sometimes less is more. Now is not the time to load up those tweaks!
Do a TWRP backup of System, Data, Boot and NVram partition now to save your efforts up to this point.
STAGE 3:
Now its time to get Skinny: You will need an app that can uninstall and freeze system apps. I use SD Maids App Control feature for this purpose.
Warning: If you intend to use app lock, you will unfortunately need to keep some fingerprint service files. See the post below and a few before it to understand the problem. Thanks to @DarthJabba9 for his work.
I believe that app lock also disables MIUI Optimization if enabled.
http://forum.xda-developers.com/showpost.php?p=67242356&postcount=583
First phase is to get rid of the obvious bloat apps and Xiaomi in-house apps....these in the list below are safe to remove.
Tick off what you have removed and reboot each 10 or so deletions and backup, don't try to delete everything in one hit as you will end up stuck at boot.
WARNING: This removes some functionality that may be useful to some users. You either want the function or you don't - it is your finger pressing the buttons!
Some people may choose to keep the MIUI Home Launcher interface. In this case, keep MIUI Wallpaper as well.
Must keep these - Do not delete:
Updater - disable autostarts, do not freeze
Theme Manager - disable autostarts
Security (com.miui.securitycenter) - leave as-is
FwkPlugin
Network Assistant app
MiuiSDK - disable autostarts
AuthManager
Webview (update via Playstore once install finished)
Xiaomi service framework - disable autostarts, freeze app
Definitely O.K to delete list:
Wallpaper Apps:
Android Live Wallpapers
Black Hole
Bubbles
com.android.wallpaper.holospiral
Live Wallpaper Picker
Music Visualization Wallpapers
Phase Beam
Photo Screensavers
*Miui MiWallpaper * keep if also keeping MIUI Home Launcher.
Xiaomi/MTK Apps:
Analytics
Assistant
Back up Home screen layout (cloud backup)
Backup - delete if you don't use it (use TWRP instead)
Battery Warning - deleting this does not affect battery charging or display
Battery Saver - deleting this improves battery life
Blocklist (AntiSpam) - delete if you don't use it
com.miui.mipub
File Explorer - delete (you should already have a root capable file browser)
Find device - use the generic Google version if you really must, not the Xiaomi one supplied.
FingerprintService
FPCSensorTestTool
FTPreCheck
FWUpgrade
gallery (com.mfashiongallery.emag daily wallpapers)
Games
Home screen
JeejenMIUIContainer
com.securitycore.miui_t (Tencent virus scanner plugin to Security Center)
KLO Bug report
LocationEM2
Metok
MI Account
Mi Cloud
Mi Credit
Mi Drop
Mi Home
MI Service Security Framework
Mi VIP
Mi Voice
Mi Wallet
Miravision
MTKAndroidSuiteDaemon
MtkFloatMenu
MTKLogger
Music
MusicFx
Notes - if you don't use it, delete it.
PowerKeeper (Battery Saver) - deleting this improves battery life
Report Bug
Security service plugin (not securitycenter app)
SystemAd
System Launcher (Miui Home) replace with an alternative Launcher, allow autostart in Security first then delete. ADW Launcher recommended for lightweight and simple functionality (set to 4x6 looks good).
Traffic Control
Uniplay
UpgradeSys
VCalendar
Video
Voice Unlock
VoiceAssist
Weather
Weather provider
Whetstone delete app and delete folder /etc/WhetstonePermission ****Whetstone is linked with several other apps to make it hard to get rid of. It may cause some temporary FC issues - these will pass.
Xiaomi Assistant
Yellow Pages
com.jeejen.knowledge
com.jeejen.store
com.ximalaya.ting.android
com.xiaomi pass
com.xiaomi.o2o
com.xiaomi.jr
Cheetah Mobile CleanMaster SDK + Cleaner - delete
NetworkLocation (com.baidu.map.location) delete app, delete folder: /system/vendor/operator and delete corpses
Android/Google Apps:
Browser - suggest replace with Polarity Browser - minimal permissions required, Ad Blocking, lightweight and fast
Documents
Google Keyboard - replace with something lighter - Hackers Keyboard v1.38.2 recommended
Google Pinyin input
Google Feedback
Google partnersetup
HTML Viewer
Email
Mail
Pico TTS
Print Spooler
com.android.browser.provider
PacProcessor
Note: If you have apps reappear as if by magic, they are being reconstructed from cached information. SD Maid has an excellent "Corpse Finder" function that will delete the orphaned files and prevent this happening. Clear corpses after each reboot.
Second phase is to toggle off the autostarts (receivers) on the apps that do not need to start by default. This is not the same as freezing an app. Some apps will still start by themselves - do not worry too much about this.
Atci_service
Backup
Blocklist
com.mediatek.batterywarning
Download Manager
Google Contacts Sync
Google One Time Init
MIUI SDK (don't freeze)
MTK NLP Service
Notes
One Time Init
Sim Toolkit
Themes (Theme Manager)
Updater
Xiaomi service framework (should also be frozen)
Third phase is to clean up left behind folders and files
/data/miui/app/customized/ remove any app folders that you have uninstalled
/data/miui/app/noncustomized/ remove any app folders that you have uninstalled
delete folder /data/miui/mms
delete folder /data/miui/gallery
delete contents of /data/miui/cust
delete folder /etc/jeejen
delete etc/voicecommand and etc/voiceextension folders if you have removed voice related apps
delete /system/tts folder if you have removed Pico TTS
delete folder /system/etc/radv
/etc/fake_cdrom_install.iso - delete file
/etc/IAmCdRom.iso - delete file
/system/addon.d delete folder
/system/app/jjcontainer/ - delete folder
/system/app/jjhome/ - delete folder
/system/app/jjknowledge/ - delete folder
/system/app/jjstore/ - delete folder
Libs you can remove:
/vendor/lib
libfingerprint_tac.so
libfpcalgorithm.so
/vendor/lib64
libcom_fingerprints_productiontestmanager.so
libcom_fingerprints_sensor.so
libfingerprint_tac.so
/system/lib
libcaFingerPrintShared.so
libcom_fingerprints_service.so
libfamily_jni.so
libjeejenAisound.so
libjeejenmsc.so
libMiraVision_jni.so (if deleted MiraVision App)
libpatcher_game_jni
libvoicerecognition.so (if voice recognition apps deleted)
libvoicerecognition_jni.so (if voice recognition apps deleted)
libweibosdkcore.so
libwhetstone_jni.so (if deleted Whetstone App)
libwhetstone_sdk.so (if deleted Whetstone App)
libxiaomimediaplayer.so (if xiaomi media player deleted)
libxiaomimediaplayerwrapper.so (if xiaomi media player deleted)
/system/lib64
libairtunes_jni.so
libairtunes.so
libBankCardRecognizer.so
libcaFingerPrintShared.so
libcom_fingerprints_service.so
libduokantext.so
libjni_latinimegoogle.so (if deleted Google keyboard)
libjni_pacprocessor.so (if deleted PacProcessor)
libMiraVision_jni.so (if deleted MiraVision App)
libpatcher_game_jni.so
libttspico.so
libweibosdkcore.so
libwhetstone_jni.so (if deleted Whetstone App)
libwhetstone_sdk.so (if deleted Whetstone App)
libxmpass_sdk_patcher.so
xmpass_libweibosdkcore.so
Establish network connectivity.
If Gapps is required but not installed, download open_gapps-arm64-5.0-pico version. You can install individual extra Google apps at any stage later on.
Go through all MIUI Settings and turn off everything you do not need running.
Install your favorite media player, web browser etc. to replace the deleted original apps.
Can replace Calendar and Messenger with Google Calendar and Google Messenger to remove some more Xiaomi dependencies. Contacts & Dialer are much harder to replace - True Phone is the only viable option.
To further limit Xiaomi unsolicited communications, rename (or delete) /system/xbin/tunman to tunmanbak. (This is a tunneling protocol driver that Xiaomi uses without your knowledge or permission).
The startup is disabled in the boot.img but it can still be started after boot unless renamed.
To skinny the Themes footprint:
Go to /system/media/theme/
Delete elder-default folder if no use.
Delete entire contents of miui_mod_icons folder
Delete items in /system/media/theme/default/ that are not going to be used.
Delete items in /system/media/lockscreen/ and /system/media/wallpaper/ that are not going to be used.
Now install your favorite app for monitoring CPU parameters and make sure that on idle, there is only one cpu core running and it sits predominantly on 403MHz. It will jump a little bit but that is normal with the inevitable background activities. Increase the timer_rate if you want more stability at idle rather than cranking up the load figures too far. Up to 50000 or down to 30000 is O.K (remember we are talking microseconds here so 50000 = 50mS)
Congratulations! You now you have a "Super Skinny" MIUI installation. Do a backup now!!!!
Now you will feel the AOSP shining through - and still you have working everything!
This post will list useful tools and items that need further investigation.
Apps for finding and disabling things:
Wakelock Detector-Root - monitor and records wakelock activity
GSAM - monitors what apps / services are consuming battery
Disable Service - disable services started on an app by app basis
SD Maid, Titanium Backup - Freeze / remove apps, toggle autostarts (receivers)
Modify your quick start grid size:
https://drive.google.com/file/d/0BwdRTuyj12_yYlphU3A0UWprcXc/view?usp=sharing
Modify MIUI Homescreen grid:
https://mega.nz/#F!yJdkxbBa!WSIqrhwUQwD7qjzxOuo1Yw
Issues:
Find a way to completely disable XMPush service with and without Xiaomi services framework installed.
Xiaomi Services Framework causes Sim connectivity issues if deleted - do not delete. There will always be one XMPush instance running.
Find out what is causing Audio On wakelock reported by GSAM
Quote: Originally Posted by DarthJabba9
With regard to the "Audio On" wakelock (aka AudioMix Wakelock) reported bt GSAM, I found this somewhere in this forum: "The nexus 6 had the same wakelock and most of us got rid of it by unchecking "use NuPlayer" in developer options". I have now unchecked that option, and will see over the next day or so whether it resolves the problem. This appears to be the fix
What triggers no sim / no service errors
Removing Xiaomi Services Framework is the culprit
Why do some files / folders not show up in root filemanagers?
MIUI locks the files / folders to prevent them being used or shown.
Why does zram not work anymore?
Rename tiny_mkswap, tiny_swapon, tiny_swapoff to teeny_mkswap, teeny_swapon, teeny_swapoff
Make sure owner is root shell and permissions are 0755 for all 3 files.
edit the init.d script to reflect the change in filenames. Now it will work again!
Example full Skinny ROM based on MR7.2.30 ID:
This is how my phone is set up, it has 100% functionality, zero FCs and zero battery drain on idle. The init.d settings are exactly as provided. Compare the directory listings to your own to see what is deleted.
The other major variation to this is for people who want to keep MIUI Launcher (and MIUI Wallpaper), everything else should remain the same. This cost you a bit more RAM usage and slightly more cpu activity (less battery) but is still impressive compared to stock.
/system/app
ApplicationsProvider
AtciService
AutoDialer
BSPTelephonyDevTool
Bluetooth
CaptivePortalLogin
CertInstaller
DeskClock
DownloadProviderUi
DrmProvider
EngineerMode
EngineerModeSim
FM
GoogleCalendarSyncAdapter
GoogleContactsSyncAdapter
KeyChain
MTKThermalManager
MiuiCompass
NetworkAssistant2
NlpService
Omacp
PackageInstaller
Provision
SuperSU
SystemHelper
ThemeManager
Updater
UserDictionaryProvider
WebViewGoogle
XiaomiServiceFramework
YGPS
cit
mcRegistry
miui
miuisystem
/system/priv-app
AuthManager
BackupRestoreConfirmation
BarcodeScanner
CDS_INFO
CalendarProvider
ContactsProvider
DefaultContainerService
DownloadProvider
ExternalStorageProvider
FusedLocation
GoogleBackupTransport
GoogleLoginService
GoogleOneTimeInitializer
GoogleServicesFramework
InCallUI
InputDevices
ManagedProvisioning
MediaProvider
MiuiCamera
MiuiGallery
MiuiKeyguard
MiuiSystemUI
MmsService
OneTimeInitializer
Phonesky
PrebuiltGmsCore
ProxyHandler
SecurityCenter
Settings
SettingsProvider
SharedStorageBackup
Shell
Stk1
TeleService
Telecom
TelephonyProvider
VpnDialogs
WallpaperCropper
com.ghisler.android.TotalCommander ### Total Commander installed as system app
com.hb.dialer.free ### True Phone replacement for Xiaomi Contacts & Dialer
org.adw.launcher ### ADW Launcher installed as system app
Other base apps in /data/app:
com.google.android.apps.messaging ### replacement Google Messenger
com.google.android.calendar ### replacement Google Calendar
com.duokan.phone.remotecontroller ### stock IR remote controller app
pcr.browser.polarity ### Polarity Browser
com.grarak.kerneladiutor ### Kernel Adiutor * disable autostarts*
org.pocketworkstation.pckeyboard ### Hackerskeyboard-v1.38.2 replaces Google keyboard
jackpal.androidterm ### Android Terminal
Thanks a bunch for the info. This is exactly what I'm looking for (my slimming down attempts always resulted in bootloops, so I've been playing it pretty safe so far).
Is this something you repeat every time an update is being pushed to your RN2?
@elaurens By doing this you are forgoing the use of OTA Updates which will unravel everything you have achieved.
I had to go through quite a few bootloops before creating the "safe lists" - I suffer so you can all benefit.
If you are starting with 7.1.4 everything is perfect and needs no more updating
Keep your eye out for additions to these lists as I discover or remember them
I have tried this:
http://forum.xda-developers.com/red...d-enable-clearmotion-miui-based-roms-t3278552
to enable ClearMotion and can vouch for it being safe - as in no malware and no breaking things. It adds the following to Build.prop and puts some hacked drivers in /system/lib.
persist.sys.display.clearMotion=1
persist.clearMotion.fblevel.nrm=255
persist.clearMotion.fblevel.bdr=255
ro.mtk_clearmotion_support=1
ro.mtk_slow_motion_support=1
ro.mtk_16x_slowmotion_support=1
Is this a worthwhile thing to do? There are no negatives in doing so as far as I can see but I don't really have anything that can give this a proper workout.
Can anyone see a difference in video playback? (Must have hardware acceleration selected) I won't recommend this if there is no perceivable gain.
most of the stuff works fine, everything checks out, It's not really anything new, but i find it well written, and it's not just a "placebo build.prop tweaks edit" which is a +. its a smart thing to have it all in a single thread.
however there're some issues with init.d script. even if you get init working, sometimes it just simply wont apply any of the tweaks. interestingly enough, i forced it to create a new text file on every boot, and that works. not really sure whats causing this prob.
anyways, by some magic I eventually made it apply the script, not really sure if it was cause of the rom change, or just pure luck lol
@sikica133 and anyone else having init.d problems:
init.d problems are usually one of the following:
1. incorrect folder permissions.
2. incorrect file permissions
3. No line feed at the end of the file (blank line)
4. incomplete or missing Busybox install
5. missing header in the text
6. Loosing SU privileges
Check init.d folder has 0755 permissions
Check file has at least 0644 permissions
Check and/or insert a line feed at the end of the file
Install busybox on rails, run the cleanup and busybox install, uninstall busybox on rails after this (this gives you an up-to-date and more complete busybox installation)
First line of file must be exactly #!/system/bin/sh
Reinstall a fresh version of SuperSu through TWRP
I sometimes get caught out myself by editing a file on the PC and transferring it back without fixing permissions afterwards:silly:
I have the ultimate build.prop tweak that I will share with you all now, stand back, it is very powerful
persist.sys.use_qualcomm_performance_features_instead=1
nah, i was testing it with a updater-script doing 0755 on all scripts. busybox should be fine cause other scripts did their job. dunno, could be some funny issue on my end. works now, i was just wtf, everything works, this doesnt. no idea what was going one tbh, but it works
could be incompatibility with bbox and the script itself? im running it without feedline atm, and it applies it all. same script i used before when it didnt do anything.
MIUI 7.1.4 and I assume all other versions has a very old and incomplete version of busybox installed (I think it was v1.20?).
It does not have fstrim command (plus a few others) included which is why I recommend updating.
I tried init.d and 01_tweaks script (whith correct permissions).
The system is more time in 806 Mhz., deep sleep not works properly.
I use Stable 7.1.1 .
Deleting script, deep sleep works fine.
Need I install or update busybox for resolve my issue?
@Xabadou This script is the starting point. If you do not "skinny down" MIUI, there are so many things running in the background that you will find it difficult to sit on idle frequency.
How far into skinnying down have you gone?
Also, if you have a 2.2GHz cpu, the 2nd line below frequencies in bold must be modified to valid frequency for that cpu.
If you are not going to skinny down to a great extent, then it helps to bump some of the load settings up a touch.
These are the original lines:
echo 80 > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
echo 90 403000:70 806000:81 1183000:84 1326000:87 1469000:90 1625000:93 1781000:96 1950000:99 > /sys/devices/system/cpu/cpufreq/interactive/target_loads
# for 2.2GHz cpu: echo 90 403000:70 806000:81 1183000:84 1326000:87 1482000:90 1664000:93 1885000:96 2158000:99 > /sys/devices/system/cpu/cpufreq/interactive/target_loads
Modify to:
echo 85 > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
echo 95 403000:75 806000:81 1183000:84 1326000:87 1469000:90 1625000:93 1781000:96 1950000:99 > /sys/devices/system/cpu/cpufreq/interactive/target_loads
This is enough to get it to sit on 403MHz idle in most cases. If you go higher, you will start compromising smoothness. There are no problems at all with entering deep sleep.
If you are still having problems, you have an app running that is badly behaved - identify it and deal with it.
Refer back post #10, I mention why you should upgrade busybox.
I am running my phone beyond Super Skinny and loving it. Super stable and battery friendly while still being a performance beast. You should notice even at the point of trimming down to Skinny, this phone really starts to liven up.
jajk said:
I am running my phone beyond Super Skinny and loving it. Super stable and battery friendly while still being a performance beast. You should notice even at the point of trimming down to Skinny, this phone really starts to liven up.
Click to expand...
Click to collapse
Do you have a list of the apks (and directories) that you deleted in order to get the skinny ROM? Such a list would be useful for writing a script to automate the task.
P.S.: you might have noticed that I am a script fanatic - I generally find that it is less error-prone to automate such tasks with a script - and you only need to get the script right once.
I use stable 7.1.1 by xiaomi.eu whith your modded kernel and a lot of apps frozen (App Quarantine).
Modified kernel works very good.
Just now I have updated busybox.
I have 2.0 ghz version.
I will try again the script.
Clear Motion mod works fine in MIUI roms but you must use MX Player for play videos.
---------- Post added at 01:20 PM ---------- Previous post was at 01:11 PM ----------
persist.sys.use_qualcomm_performance_features_inst ead=1
Works qualcomm tweaks whith mediatek processors?
@DarthJabba9 The lists ares already mentioned - 1 to get to skinny, 1 to get to super skinny but if you do this in a script on a live system you will likely end up in a bootloop because there are too many odex and cache entries orphaned for Android to handle in one hit. If you intend to apply a script to the ROM files before installation, that is a different story. It takes a bit of effort to figure out how and where MIUI is loading a lot of its components from but is doable.
Why I have not offered a complete ready to go package? It is too easy for users to do it themselves and add their preferences along the way. For those that have actually followed through with the process, I can guarantee that they will instantly loose interest in any other custom ROM.
@Xabadou Thanks for the clarification on ClearMotion. I run VLC set to hardware acceleration and can't see the split screen test mode. Video looks fine regardless, so really hard to tell if anything has changed.
Do the apps that you quarantine stay not running? I had problems with quite a few apps running regardless of being frozen or not so had to uninstall.
You, along with everyone else are not running a modified kernel - the kernel remains intact since we do not decompile and recompile or compile it from source.
The "persist.sys.use_qualcomm_performance_features_instead=1" tweak is a sarcastic dig at the many tweak offerings that do absolutely nothing:silly:
You asked the question showing you were not ready to accept this at face value:good:
If there is no evidence of a tweak doing something positive, don't blindly use it!!!
This is a customized boot image that provides init.d support and has unnecessary entries removed. No tweaks are embedded.
It is built on 7.1.4 and can be used on stock 7.1.1 to 7.1.4.
https://drive.google.com/file/d/0BwdRTuyj12_yR3phb0Zxd05UQjQ/view?usp=sharing
credits to @DarthJabba9 for the alternate init.d support method adopted in this image. It circumvents using busybox run-parts method that appears to have some bugs.
jajk said:
@DarthJabba9 The lists ares already mentioned - 1 to get to skinny, 1 to get to super skinny but if you do this in a script on a live system you will likely end up in a bootloop because there are too many odex and cache entries orphaned for Android to handle in one hit. If you intend to apply a script to the ROM files before installation, that is a different story. It takes a bit of effort to figure out how and where MIUI is loading a lot of its components from but is doable.
Why I have not offered a complete ready to go package? It is too easy for users to do it themselves and add their preferences along the way.
Click to expand...
Click to collapse
Fair enough ...
jajk said:
I will share my custom Super Skinny MIUI boot.img based on MIUI7.1.4 since it is now stable ... It is unpacked and repacked using AndroidMasterChef (downloaded from Needrom). I do not have problems unpacking and repacking again. If you try to unpack and have problems, use the same tool.
Click to expand...
Click to collapse
Thanks for the image. It cannot be unpacked with standard linux tools, but it unpacks ok with AndroidMasterChef.
I recently rooted and installed a custom rom (xXx No Limits following guide in their thread) on my Galaxy S5 (Europe, G900F).
Everything went well other than a little confusion during these steps:
9. Boot the phone into custom recovery (TWRP 3.0.0.0)
10. Hit ?Wipe? and then ?Advanced Wipe?
11. Go to Install Section, select Rom zip, flash the rom and reboot.
12. Wipe Dalvik / Art Cache, System, Data and Cache.
Click to expand...
Click to collapse
What i did was first i wiped everything except my SD using advance wipe, then installed the rom, and then wiped Dalvic and Cache.
Since everything worked fine i didn't think more of it but after running into a new problem i think i may have done something wrong here, or else the problem is something entirely different.
After setting up the phone with the newly installed custom ROM i was happy while installing all the apps i use daily - And then it struck me i forgot to make a separate vCard backup for my contacts, and i previously didn't use any cloud service or have the linked to my google account.
I figured i could restore my TWRP backup i made following the guide, then make a vCard backup of my contacts and save it to my pc - then reinstall the custom ROM and use the vCard backup. But i insisted there had to be a way to extract my contacts some other way and back them up and i went googling for awhile.
Found a few solutions:
Find some files from the TWRP backup and change the file extension to zip/tar.gz and extract a file from there and convert to using a website - Sounds easy but for some reason my 7zip refuses to recognize the files as archives.
Another solution would be to extract the files from the backup directly from the phone using apps like Titanum Backup (Pro, wich i bought for this reason) or AppExtractor. But neither of those app will recognize my backup? I have read several threads about people having the same problems and tried following some of the answers which included going to Menu -> Preferences -> Backup settings: Backup folder location and scan for backups, but it wont find any. Reading some more i notice something is different with my folders. People in other threads got instructed to look for /storage/emulated/0/TWRP/BACKUPS and i also have that folder, but my backup isnt there. My backup lies in /storage/E409-3EDC/TWRP/BACKUPS
AppExtractor cant find my backup either but wont allow me to search for it.
Further more i read about another app called Nandriod Manager and installed it. This app WILL find the backup but has no way of extracting what i specifically need.
Am i right in assuming this is cause by some mistake i made in the steps mentioned first in this thread?
If anyone is interrested this is the xXx.options.prop settings i used for installation:
Code:
# xXx.options.prop
#
# RomBase by xda member xXx
#
# Configuration file to allow customize the installation
#
# I agree to use any part of my work to create more advanced custom ROM,
# but it would be great if you add me to the credits
#
prop.version=14
use.prop.in.zip=0
#-----------------------------------------------------------------------
# Enable root access and install the SuperSU app (thanks to @Chainfire)
# Please Note: Do NOT install Root if you want to stay with Knox 0x0!!
# Allowed values:
# 0 - do not enable root access
# 1 - enable root access with SuperSU by chainfire
# 2 - Experiental - SuperSU + suhide by @chainfire to get Safety Net & Pokemon Go working
root.supersu=1
# Deodex ROM during install (change this value only if you really need it!)
# Allowed values: 0 - Odex; 1 - Deodex;
deodexed.rom=1
# Kernel
# Allowed values: 0 - Stock Kernel; 1 - PhoeniX Kernel; 2 - CrazySuperKernel; 3 - Boeffla-Kernel
kernel=0
# sdcard Fix Permissions script
# fix ownership and permissions of files and directories on the sdcard to what they would be
# if Android OS had put them there itself, since some apps can't access pushed files that have root.root as owner/group
# Sometimes Apps FC when trying to access/write files on sdcard even with correct r/w permissions.
# This might fix this issues
# Please Note: Depending on how much files you have stored on your sdcard it can take
# up to several minutes to scan and fix it!!
# Don't become nervous when Rom flashing process will stuck here for a while,
# it will continue - Promised !!
# Allowed values:
# 0 - disabled
# 1 - enabled (default)
sdcard.fix=1
# Keyboard
# Please Note: Key vibration doesn't work on the S6 Keyboard!!
# Allowed values:
# 0 - Stock Keyboard
# 1 - S6 Keyboard - no key vibration, better choose newer C5 keyboard
# 2 - Sony Xperia Keyboard - very clean and plenty of optional settings
# 3 - C5 Keyboard - newest Samsung keyboard
keyboard.mod=3
# SystemUI mods
# Allowed values:
# 0 - Pure Stock SystemUI
# 1 - White theme, 3minit battery, rounded notifications and recents, Sdcard notifications fix
# 2 - Good Lock - no further mods or fixes. Fingerprint is not supported. Don't try it!
# 3 - White theme, rounded notifications and recents, Sdcard notifications fix
systemui.mod=2
# xXx Tweaks
# - A collection of system tweaks which optimizes overall speeds and RAM management
# - deodex the rom
# - 5-Way Reboot menu
# - Privat Mode fixed
# - Changed default Window Animation Scales to 0.5 for faster animations
# - Updated hosts file for Adblock
# - Qualcomm Adreno 330 Beta Drivers for better GPU Performance with Stability Fix by @DAS82 based the on @airidosas252 framework
# - Screen Overlay Fix
# - SystemUpdateService Disabler
# Allowed values:
# 0 - xXx Tweaks disabled
# 1 - xXx Tweaks enabled (default)
# 2 - xXx Tweaks + Qualcomm Adreno 330 Beta Drivers
xXx.tweaks=1
# Camera Mod
# Please Note: If you choose the modded Camera xXx Tweaks will be installed as well!
# Allowed values:
# 0 - stock camera (default)
# 1 - camera mod thanks to @amk1
camera.mod=1
# Screen Overlay Fix
# This will bypass the Android Screen Overlay Security and don't bother you anymore to disable previous activated
# Please Note: This will make you device vulnerable to Tapjacking!
# Allowed values:
# 0 - stock settings (default) (max Tapjacking security)
# 1 - modified Android Screen Overlay Security (for your convenience)
screen.overlay.fix=1
# Xposed Framework
# Allowed values:
# 0 - Xposed NOT installed
# 1 - Xposed + Original Rovo Xposed Installer (default)
# 2 - Xposed + Material Design Xposed Installer
xposed=2
# Sound Mods
# Allowed values:
# 0 - NO Sound Mod
# 1 - OLD - V4A Combo - Viper4Android + Sony Beats + eXtremeBeats Aural Maximizer by @guitardedhero and @Ben Feutrill
# 2 - OLD - V4A Combo + Dolby ATMOS
# 3 - NEW - Viper4Arise/eXtremeBeats Combo by @A.R.I.S.E. Sound Systems and @Ben Feutrill (default)
sound.mod=3
# Take care of security-related system files if there are any (SuperSU PIN, Avast Anti-Thelf in root mode).
# Allowed values: 1 - make a backup and then restore at the end of installation, 0 - skip backup
security.files=1
# Force overwrite your current recovery by stock recovery matched to the ROM version
# (by default it is overwritten only if KNOX 0x0 status has been detected).
# Allowed values: 1 - force overwrite current recovery, 0 - check KNOX status and overwrite if 0x0
stock.recovery=0
# CSC Selection. Allowed values:
# KCSC - Keep current CSC, recommended in most cases (automatic selection or copy your current CSC contents).
# You can force the use of natively supported CSC by typing (use UPPERCASE!):
# ALB, ALE, ARO, ATL, ATO, AUT, BGL, BMC, BTU, BVO, CHO, CMF, COO, CYO, DBT, DTM, EON, ETL, EUR, H3G, ILO, ITV, KSA, LUX, MEO,
# MET, MOB, MOT, MSR, MWD, NEE, NZC, OMD, OMN, ORX, PCI, PCW, PEO, PHE, PHN, PRO, ROM, SEB, SEE, SER, SIO, SWC, TDR, TEB,
# TEM, TEN, TMZ, TNZ, TOP, TPA, TPH, TSI, TSR, TTT, TUR, TWO, UPO, VD2, VDH, VDS, VIA, VIM, VNO, XEF, XEH, XEO, XME, XTC, ZTO
CSC=KCSC
Since it has built in sdcard fix that should not be the problem.
I hope i'm not confusing anyone more than i do myself because i must admit i cannot wrap my head around it. Might have something to do with this being the first time i mess around with rooting/custom rom on my phone.
Any help is greatly appreciated!