Database Info

[ROM][7.15.2011]NAMELESS v1 for Droid Charge - Test Build #3 - EXT4/Debloat/Tweaks - Verizon Droid Charge

NAMELESS v1
based on the EP1F Gingerbread Leak
{
"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"
}
--------------------
About:
This ROM is currently in testing for Charge. As such, some things may not work - but not for long! Please report issues in the thread. This ROM is the EP1F leak with my personal touches and changes, and some common sense tweaking to present a smoother, faster, EP1F experience.
--------------------
Thanks:
I've gotten some great help! Here they are (in no particular order):
gunnermike53 (tester, modder)
c0ns0le (tester)
Grillrd (tester)
I'm looking to get more help all the time, because with more help the faster the process goes Join me on FreeNode IRC chat at #samsung-charge
--------------------
What you really want to know:
Refer to Post #2 for an explanation of the below features.
Kernel Features:
EXT4 Support
Extra Storage Support (mmcblk0p2 remap for personal use /extstorage folder)
DBDATA/DATADATA Symlink
init.d Script Loading Support
Auto root install
Built-in BusyBox
Built-in fix_permissions script
Built-in bash shell
Built-in nano editor
FC Prevention & Detection (e.g. if you get acore FC's on boot, just reboot the device)
SD Card Read Speed Tweak
CPU/VM/Kernel Tweaks
CWM4 Recovery
Charge Mode ADB access
Rom Features:
Supercleaned
De-odexed
Zipaligned
De-TouchWiz'ed
Go Launcher EX
Touchwiz Calendar/Calculator
GAPPS - Gmail, Maps, Street, Vsearch, Talk2 (with video chat)
Appwidgetpicker
EXT4 auto-format on install (all partitions converted to EXT4)
sysrw, sysro scripts for remounting /system r/w or r/o
zipapps script for zipaligning apps on the fly
bstats script for removing old battery stats to refresh battery life
build.prop tweaks
Malware exploit patch
--------------------
FAQ:
Q: Ok, I'm cool with it, so what should I know about installing it?
A: Just flash from CWM3 recovery, no data wiping or other actions are needed, the entire installation is automated. NOTE: Your data will be wiped.
--
Q: Ok, what kind of caveats can I expect from this ROM?
A: The ROM is currently open for testing. I don't own a Droid Charge so I have no idea if anything works or not without testers. Being a test build, you may run into issues with things not working or nothing working at all. If that is the case just report it here.
--------------------
FILES:
Test Build #3
http://www.mediafire.com/?fz11ex27qo2ho97
--------------------
If you like my work, consider donating, or thanking me by clicking the thanks button

NAMELESS ROM DICTIONARY
Kernel Features​
EXT4 Support This is a filesystem, basically what organizes and makes sense of the data on your phone. This specific one, EXT4, is generally known for being reliable and fast, compared to the one that comes with the phone, RFS.
Click to expand...
Click to collapse
Extra Storage Support (mmcblk0p2 remap for personal use /extstorage folder) This is a custom feature of the kernel which takes the "preinstall" partition (used for over-the-air updates from Verizon) and turns it into an on-phone storage space where you can store files separate from your SD card.
Click to expand...
Click to collapse
DBDATA/DATADATA Symlink This is a custom feature of the kernel which creates a symlink (a connection between two different points of data, or a shortcut) from the DATADATA directory to the DBDATA directory. This is advantageous because you will be able to use scripts not originally written for TouchWiz based ROM's.
Click to expand...
Click to collapse
init.d Script Loading Support This is a built-in kernel feature which allows you to store script files in the /system/etc/init.d directory on your phone. This directory is special because it will run said scripts at boot time. Generally in this directory people put performance enhancing scripts to better their phone.
Click to expand...
Click to collapse
Auto root install This is a custom kernel feature which roots your phone upon every boot, practically forcing your phone to be rooted while using the kernel. Even if you accidentally delete root, you will be rooted again upon the next boot.
Click to expand...
Click to collapse
Built-in BusyBox BusyBox is a binary (a linux program) that is a conglomeration of multiple utilities packed into one. Basically it allows you to use lots of useful linux commands not originally available on the Android operating system. It allows you to be the master and commander of your phone.
Click to expand...
Click to collapse
Built-in fix_permissions script This is a special script which when run (using a program like terminal emulator, or adb shell) will try to fix the permissions on your phone. Sometimes permissions can be set wrong, and this can cause lots of problems. This script fixes that.
Click to expand...
Click to collapse
Built-in bash shell Bash is a linux program, or rather a linux "shell", which is an environment where you can control your linux system and execute linux commands. Bash is also known as the "Bourne-Again Shell" and is a more advanced successor to its older sibling shell environments like "SH".
Click to expand...
Click to collapse
Built-in nano editor NANO is a linux text editing program that can be used from a command prompt in a linux shell.
Click to expand...
Click to collapse
FC Prevention & Detection (e.g. if you get acore FC's on boot, just reboot the device) This is a custom feature of the kernel where upon every boot the kernel will run a special error fix/detection script that will try to find and fix a few critical TouchWiz elements before booting you into the operating system. This is advantageous because it eliminates not being able to wipe between ROM's, since doing so usually causes a lot of problems.
Click to expand...
Click to collapse
SD Card Read Speed Tweak This is a common kernel implementation which slightly speeds up the reading speed of data on the SD card. In other words, it makes stuff on your SD card work faster.
Click to expand...
Click to collapse
CPU/VM/Kernel Tweaks These are common kernel implementations which overall improve the performance of your phone.
Click to expand...
Click to collapse
CWM4 Recovery This is a famous "recovery" system created by a developer named Koushik Dutta. This has been around awhile and is now in its 4th evolution. The version included here is one of the latest available. The recovery system allows you to execute useful linux and Android specific elements so that you may modify, save, or otherwise control your phone outside of the normal operating system.
Click to expand...
Click to collapse
Charge Mode ADB access This is a custom feature of the kernel which allows you to access your phone via ADB shell while charging. Charge mode is when your phone is off, and plugged in, showing the battery icon.
Click to expand...
Click to collapse
ROM Features​
Supercleaned This means that all of the stuff that most people do not want, that comes on your phone when you buy or over-the-air update it, has been completely removed.
Click to expand...
Click to collapse
De-odexed Any Android application is usually delivered in the form of an APK file. An APK file is pretty much just a ZIP file. Sometimes the Android application needs extra code to do things, and this is found inside of the APK file and called "classes.dex". An APK file can be "ODEXED", this basically means taking the classes.dex file OUT of the APK file. This is advantageous because it allows the Android system to access the code directly instead of having to decompress and recompress (take apart, put back together) the APK file every time to access the code. However, it has one downside, it is difficult to make themes or mods while using this process. So, the APK file is "DEODEXED", which basically puts the code back in the APK file, creating one single file again.
Click to expand...
Click to collapse
Zipaligned Each APK file has a certain alignment to the little bits and bytes that flow through the phone, this is pretty much the same concept as having your car tires aligned for a straight drive. It allows the application to use less memory and perform better, like a tire alignment would allow you to use less gas and drive faster and straighter.
Click to expand...
Click to collapse
De-TouchWiz'ed The removal of close to all but the best TouchWiz applications.
Click to expand...
Click to collapse
Go Launcher EX A home launcher application included in the ROM, instead of the standard.
Click to expand...
Click to collapse
Touchwiz Calendar/Calculator Quite useful and good looking TouchWiz applications.
Click to expand...
Click to collapse
GAPPS - Gmail, Maps, Street, Vsearch, Talk2 (with video chat) The Google suite of applications.
Click to expand...
Click to collapse
Appwidgetpicker This little program condenses the widgets list when long-pressing on your home screen. It makes it so that you don't have 500 widgets to scroll through.
Click to expand...
Click to collapse
EXT4 auto-format on install (all partitions converted to EXT4) A custom ROM feature written by me which formats/converts your phone to the EXT4 filesystem automatically when installing the ROM.
Click to expand...
Click to collapse
sysrw, sysro scripts for remounting /system r/w or r/o Useful scripts which allow you to "remount" your system partition to a read/writable or read/non-writable state so that you may modify files in the system area.
Click to expand...
Click to collapse
zipapps script for zipaligning apps on the fly A special script which will attempt to give any applications in the standard locations the aforementioned tire alignment.
Click to expand...
Click to collapse
bstats script for removing old battery stats to refresh battery life A script which will delete old battery stats allowing you to renew the stats so as to attempt to get more battery life.
Click to expand...
Click to collapse
build.prop tweaks This file contains important properties of which the operating system cannot live without. I have tweaked this file to optimum performance standards so as to better your phone as much as possible.
Click to expand...
Click to collapse
Malware exploit patch Quite awhile ago a tricky person found a way to mess peoples phones up through the Android market, and this fixes that problem from ever occuring (It has long been fixed by Google anyway).
Click to expand...
Click to collapse

Wow a lag fix for the leak ill have to give it a shot later
Sent from my SCH-I510 using XDA Premium App

Awesome that you have EXT4 on GB! Hopefully one of the folks with a spare Charge will test this out.

great to see this rom here! I was using this on my Fascinate!
thank you.

glad to see a new ROM pops up. The OP mentioned flashing it w/ cwm3, while I'm already on cwm4, do I need to downgrade cwm before loading this?
Sent from Droid Charge

Do you need to be on the official leak first? I was on humble 2.1 and flashed this. The phone just boots straight into recover now.

Tested but after several attempts to install only boots up in recovery

IamIkari said:
Do you need to be on the official leak first? I was on humble 2.1 and flashed this. The phone just boots straight into recover now.
Click to expand...
Click to collapse
Thanks for the info IamIkari, I expected this and am working on a fix.

New Rom
As much as I like what the other devs have brought to the charge this is exciting. I cant wait to see a working and stable build.

I tried going back to the debloated official leak using ODIN. I'm still stuck at a recovery screen.
It is not your average recovery screen. It says "Android system recovery <3e>" and uses the home key to select instead of the power button.

im having same issue when i go back to debloated using odin

IamIkari said:
I tried going back to the debloated official leak using ODIN. I'm still stuck at a recovery screen.
It is not your average recovery screen. It says "Android system recovery <3e>" and uses the home key to select instead of the power button.
Click to expand...
Click to collapse
You will need a PIT file to go along with your ODIN flash.

I have included another kernel to test, it is in the OP under files. Flash after flashing ROM. Report issues.

IamIkari said:
I tried going back to the debloated official leak using ODIN. I'm still stuck at a recovery screen.
It is not your average recovery screen. It says "Android system recovery <3e>" and uses the home key to select instead of the power button.
Click to expand...
Click to collapse
i think you want to follow these instructions to get back to a working state
http://forum.xda-developers.com/showthread.php?t=1111486

navenedrob said:
You will need a PIT file to go along with your ODIN flash.
Click to expand...
Click to collapse
Where would I find a PIT file? I searched the forum and didn't see anything.
Nevermind, Thanks robby88!

I just installed test version 2 and I am getting nothing but clockworkMod recovery v4.0.0.8 when I boot up. Still a no go.

timgt said:
I just installed test version 2 and I am getting nothing but clockworkMod recovery v4.0.0.8 when I boot up. Still a no go.
Click to expand...
Click to collapse
Did you install the test kernel too?

navenedrob said:
Did you install the test kernel too?
Click to expand...
Click to collapse
No, i figured if it wasn't going to boot then there was no reason to. Is the kernel what you worked on to fix this? I will try again in a few mins. I started to odin back.

Looks like a great start.
I'll be watching this thread closely.

Related

{
"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"
}
PDroid allows blocking access for any installed application to the following data separately:
Device ID (IMEI/MEID/ESN)
Subscriber ID (IMSI)
SIM serial (ICCID)
Phone and mailbox number
Incoming call number
Outgoing call number
GPS location
Network location
List of accounts (including your google e-mail address)
Account auth tokens
Contacts
Call logs
Calendar
SMS
MMS
Browser bookmarks and history
System logs
SIM info (operator, country)
Network info (operator, country)
For device ID, phone and mailbox number, SIM serial, subscriber ID and device location it also allows supplying custom or random values.
Why you would want to use it:
Applicaitons do NOT crash when access to private data is blocked (unlike with Permissions Denied or CM)
Fine-grained tuning of access to private data
No background service needed
Very small memory footprint (~700KB)
No impact on battery life
No impact on performance (5ms overhead on access to private data; yes, that's 0.005s)
100% reliable unlike ROOT applications (LBE), which need to start their background service on boot (see android underground to learn why this is an issue)
No ROOT required for the app to run
No Android permissions required for the app to run
Open-source
Download:
Automatic PDroid Patcher for Windows (XP/Vista/7):
JDK 6 or newer is required (get it here http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u25-download-346242.html)
Install JDK 6 into the default directory (don't change anything when installing)
.NET Framework 2.0 or newer required (ships with Windows since XP SP2)
Currently only supports Gingerbread (Android 2.3)
Will only work with deodexed ROMs (take a look into your ROM's system/framework directory; if there are any *.odex files, your ROM is NOT deodexed)
You will need to re-create your settings backup after updating from version 1.27 (it is not compatible with the newer version)
Download PDroid Patcher v1.32 Beta 0.321 for Windows
Patch Installation Requirements:
ROOTED device
For HTC devices: S-OFF ([TOOL] One click ENG S-OFF for HTC Desire HD)
ClockworkMod Recovery 3.0.2.6 or newer
If you "integrated sys Dalvik into ROM" with Titanium Backup, you will have to undo it
Installation Instructions:
BACKUP YOUR ROM (HOWTO)
Make a PDroid Patch for your ROM with the PDroid Patcher and put the patch on your SD card
Boot your device into your custom (CWM) recovery (Desire HD: vol down + power)
If you flashed the patch before but PDroid said it still was not installed, then select "mount /system"
Select "install zip from sdcard"
Select "choose zip from sdcard"
Select the PDroid patch you have put on your SD card
After flashing is finished, reboot the device
Install the PDroid app from the Android Market
Rate the app at the Android market (let me know, if you have any issues beforehand)
Patch Changelog:
1.32: Fixed updating from version 1.27 and below
1.31: Fixed patching incompatibility with some ROMs (like Zeus v5)
1.30:
Fixed the alarm being put to snooze every time a call is received or made
Fixed FC for some applications (like Yandex Maps)
Fixed bootloops for AT&T and SonyEricsson devices (hopefully)
Many small tweaks
1.27: Fixed an issue, where the Touchwiz launcher (and probably others) would continuously crash
1.26: Fixed an issue, which would make Google Listen and probably other apps crash
1.25:
Fixed an issue, where PDroid would conflict with some ROOT applications making them freeze
Fixed random geocoordinates generation
Fixed other minor bugs
1.22: Fixed the patch version reporting bug (v1.21 reports that it's 1.2)
1.21: Fixed the bug where the device would sometimes boot loop right after the boot is finished
1.2: Added data access notification feature
1.1: Bugfixes
1.0: Initial release
Source:
Download: PDroid 2.3.4 source (v1.27) (yes it is based on 2.3.4 but also works with 2.3.3 and 2.3.5 flawlessly)
Get the 2.3.4 source from AOSP (branch: android-2.3.4_r1)
Extract the patches from the above archive to the 2.3.4 tree root
Run:
Code:
patch -p1 -i build.patch
patch -p1 -i frameworks.patch
patch -p1 -i libcore.patch
Building from source:
Make a clean build
Apply the patches (see above)
Run:
Code:
source build/envsetup.sh
make update-api
mmm frameworks/base
mmm frameworks/base/services/java
mmm libcore
make snod
FAQ:
I do not have Market access, where can I download the PDroid app?
Click to expand...
Click to collapse
Right here
What about controlling the internet access?
Click to expand...
Click to collapse
Controlling access to the network/internet requires either patching the kernel or using ROOT access within the PDroid app. I try avoiding the former due to portability and the latter due to user privacy/security reasons. I am looking into adding internet access control in a way, which would be the most acceptable/convenient for the user. However, this feature currently isn't on the top of my to-do list.
How do I make a patch manually myself?
Click to expand...
Click to collapse
For experienced developers the following basic steps for creating a PDroid patch should be enough to get you started:
Make a clean AOSP build (2.3.4, assuming that your ROM is based on 2.3.x)
Make another build with PDroid sources added
Decompile the framework.jar, services.jar and core.jar files inside the system/framework directory (of both above builds) using apktool
Diff the output so that you know, which parts were changed by PDroid
Decompile the above three files from your ROM, you want to patch
Add the missing code to your ROM files based on the above diff
Recompile your patched ROM files using apktool
Do you plan on adding Froyo/ICS support?
Click to expand...
Click to collapse
Yes. But I have not ported PDroid to Froyo or ICS yet. No ETAs yet. You'll need some patience there.
Will you provide a public source code repository for PDroid?
Click to expand...
Click to collapse
I might, when I get some more spare time
Can I backup the privacy settings with TitaniumBackup?
Click to expand...
Click to collapse
Yes, however you will need to backup your settings to internal memory (PDroid preferences) before making a backup with TitaniumBackup. After restoring with TitaniumBackup, you will need to restore the previously backed up settings. Alternatively you can backup privacy settings to the SD card.
Can I use LBE Privacy Guard together with PDroid?
Click to expand...
Click to collapse
Yes.
I have applied the correct patch but my device does not boot, how do I find out what the error is?
Click to expand...
Click to collapse
Restore your backup
Get the Android SDK
Install it (you don't need the eclipse part)
Enable USB-debugging on your device
Connect it to your PC
Start ddms, which is located in the android-sdk-[platform]\tools directory
Apply PDroid patch
Reboot the device
When your device appears in the ddms window, click on it to see the system log
Filter the log by "error"
Watch the system log for errors and post them here
I have flashed a patch but I am having very weird issues I didn't have before (like you cannot unlock the SIM card or there are weird graphics etc.)?
Click to expand...
Click to collapse
Have you flashed other mods to your ROM? If so, PDroid is most likely conflicting with them. You will need to create a patch for your customized ROM.
Also make sure that you are using a patch appropriate for your ROM (the CyanogenMod patches for stable 7.1 will mostly not work on nightlies unless the link says so).
How do I make a patch for my device after I have flashed some other mods?
Click to expand...
Click to collapse
If your other mods DO NOT replace any of the three files: framework.jar, services.jar or core.jar in /system/framework, you can just create a patch normally based on your original ROM file.
Otherwise you will need to extract those three files from your device (use a root file manager or adb pull), put them into your ROM zip (also in /system/framework) and then create a PDroid patch based on the ROM zip.

Reserved, just in case

Yes. This is awesome

Great !
But I have a Desire... Just for Desire HD?

I believe you need root to push those jar files... so you do need root. right?

So this will not run at all times, and thus not kill the batterytime?
Sent from my HTC Desire HD using XDA App

Seems interesting, I'll be happy to test out this app if it releases for SGS2.
Sent from my GT-I9100 using XDA App

Sybregunne said:
I believe you need root to push those jar files... so you do need root. right?
Click to expand...
Click to collapse
Correct, that's what the description says
no_johnr said:
So this will not run at all times, and thus not kill the batterytime?
Click to expand...
Click to collapse
That's right. It has virtually no impact on battery life / performance.
hallydamaster said:
Seems interesting, I'll be happy to test out this app if it releases for SGS2.
Click to expand...
Click to collapse
Which ROM do you use? Which one is the most popular for SGS2?

Hi,
in where should i set the 3 files?
platform-tools?

fe22st said:
Hi,
in where should i set the 3 files?
platform-tools?
Click to expand...
Click to collapse
Anywhere, you can run ADB from. And yes, you can place them in platform-tools (I assume, your adb files are located there).

svyat said:
Anywhere, you can run ADB from. And yes, you can place them in platform-tools (I assume, your adb files are located there).
Click to expand...
Click to collapse
i get a issue after these commands:
adb push DHD-framework-gr5.mod.jar /system/framework/framework.jar
adb push DHD-services-gr5.mod.jar /system/framework/services.jar
adb push DHD-core-gr5.mod.jar /system/framework/core.jar
its looke like:
adb push DHD-framework-gr5.mod.jar /system/framework/framework.jar
cannot stat 'DHD-framework-gr5.mod.jar': No such file or directory
what can i do to fix that problem?

fe22st said:
i get a issue after these commands:
adb push DHD-framework-gr5.mod.jar /system/framework/framework.jar
adb push DHD-services-gr5.mod.jar /system/framework/services.jar
adb push DHD-core-gr5.mod.jar /system/framework/core.jar
its looke like:
adb push DHD-framework-gr5.mod.jar /system/framework/framework.jar
cannot stat 'DHD-framework-gr5.mod.jar': No such file or directory
what can i do to fix that problem?
Click to expand...
Click to collapse
You should run the commands from the directory, where you have extracted those 3 files.

Hi, great stuff! Have been following this for some time hoping for the first version to be released. Which you did! Bummer you do need root access for changing some files, I had hoped it wasn't necessary...
Anyhow: great tool, now just to find a temporary solution to the rooting
Sent from my Desire HD using XDA App

I've uploaded an update script, which can be used to flash PDroid from the CWM recovery more conveniently. Have fun.

Is it possible to use this on gs2 with cyanogen?
On the fly of my Galaxy S2
RogueZet

Tried this on RunnyRCmix3d 4.0 and after flashing zip could not boot in rom. So it does not work on every rom based on 2.3.5 . Can you look into this?
Sent from my Desire HD using Tapatalk

vault1965 said:
Tried this on RunnyRCmix3d 4.0 and after flashing zip could not boot in rom. So it does not work on every rom based on 2.3.5 . Can you look into this?
Click to expand...
Click to collapse
You're right. It won't work with Sense 3.5 ROMs. I've added to the description that it currently only works with Sense 3.0. I might port it to Sense 3.5 soon.

That would be great. I am using LBE app now, but yours promises so much more.
Sent from my Desire HD using Tapatalk

Thanks for releasing code. Now the challenge is up for me to integrate it with MIUI ( no source available !!!!!)

cool app, but i feel it spend alot of CPU resource , maybe my phone is slow

-What do we have here?
-Supercharged script's
-SuperClean script's
-Deblur
-Deodex
-Oc Under terminal emulator (built in in V4 and above see second post)
-Build.Prop tweaks (a lot of 'em)
-Sdcard speed tweaks
-1 percent battery mod
-No carrier logo
-Quick Settings
-Webtop over hdmi
*********-How to Install...**********
------------------This only applies to v1-4, For V5 and above follow instructions listed next to downloads below---------------
-Boot into**BOOTSTRAP**(NO SAFESTRAP)
-Format System
-Install Stock Deodex rom
-Wipe Data/Factory Reset
-Wipe Cache
-Wipe Dalvik Cache
-Reboot phone
-Once stock rom has loaded install bootstrap and reboot into recovery(we need a clean, deodxed, rooted base)
-Wipe Data/Factory Reset
-Wipe Dalvik Cache
-Wipe Cache
-Install SuperCharged Rom
-*****DO NOT FORMAT/WIPE ANYTHING AFTER FLASHING****
-Now what???
-When prompted choose go launcher and set as default
*********Changelog*********
-V1.0
-Initial Release
-Known minior theming bugs.
-v2.0
-Fixed a few theme bugs(wipe data/factory reset)
-Fixed Contacts
-Edit's to updater script
-Added apps (including bloat freezer, I checked its cool)
-Move some apps to /data (so you can uninstall them)
-Added ics notification sounds
- Put back moto launcher (use home switcher)
-V3
-****HUGE Performance increase over V1 and V2****
-Fixed Super user issue's
-Fixed busy box issue
-Fixed webtop?
-Fixed permission issues with oc. Should no longer cause a reboot.
-V4
-Fixed webtop (I'm sure this time)
-OC'd to 1122 on boot
-Ad blocking in hosts file
-Wireless tether hack is now included (this damn thing..)
-Removed Motomizer (I could not seen any improvement over the included scripts)
-Removed Scripts app and BloatFreezer (both were causing push ad's)
-Removed Ciq Completely! (THANKS JIMBRIDGEMAN!)
-V5
-Based on 2.3.6 Update
-Added CapnPez's Toggles
-Better Init.d support (Now loaded from system/bin if install-recovery.sh fails)
-New boot animation
-More build.prop tweaks
-This is a fesh build of 2.3.6 from a system dump, it has been deodxed.
-----------V5_Update_1
------------------Fixed haptic feedback matches 2.3.6
------------------Fixed Supercharger "V6" scripts THANK YOU ZEPPELINROX
------------------Build prop edits to wifi, vm, and 3g Thanks Tyler Carter
---------------------------V5_Update_2
-------------------------------------------Added reboot option and ICS animation. Thank you JRW28 and COGEARY
-------------------------------------------Added ICS Ui, Notification's, and Ringtones.
-------------------------------------------Added Voicesearch from market to system/app
-------------------------------------------Fixed gps fix issues that show up after a few days with rom
{
"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"
}
<----Go launcher ics theme
*********Downloads*********
http://depositfiles.com/files/7sm8wjocq <----SuperCharged V 5 This is not a flashable zip, it is a cwm backup, you will need to extract the contents of the zip to the root of your sdcard. Instructions are included in the zip. READ THE "README" FILE INSIDE THE ZIP!---YOU WILL NEED TO WIPE DATA/FACTORY RESET NO MATTER WHAT ROM YOU ARE COMING FROM. Then go to back up and restore, select restore, select SuperCharged_V_5. Let it restore Reboot and you are on your way!
http://downloads.h22designs.com/SuperCharged_V_5_DO_NOT_FLASH.rar <----SCV5 Mirror thanks to Script
http://depositfiles.com/files/0z63kidwv <---- SCV5 Update 1, ALL YOU NEED TO DO IS FLASH FROM BOOTSTRAP, No wipe etc... SCV5 "ONLY"
http://depositfiles.com/files/k4opdtt3g <----SCV5 Update 2, ALL YOU NEED TO DO IS FLASH FROM BOOTSTRAP, YOU DO NOT NEED TO WIPE ANYTHING. This Includes SCV5 Update 1. Having force close issues? Use the full backup listed below.
http://depositfiles.com/files/en42gu9jp <----SCV5 Update 2 Full System Img. Place on root of sdcard, Use advanced restore and only restore /system Read the "README" File included in the zip. You will Not need to wipe. This is only for those of you facing force closes after updating to SCV5_Update_2.
http://www.multiupload.com/9UHYFAPETU <----Supercharged V 4 (If coming from
V3 Just wipe dalvik cache any other rom, full wipe see above)
http://depositfiles.com/files/a3my85m50 <---- Alt Link for Supercharged V 4
http://www.sendspace.com/file/o7kzac <---- Alt link for Supercharged V 4
http://www.multiupload.com/FIUXZ4FBFD <----Supercharged V 3 (Wipe data/factory reset, wipe dalvik cache)
http://www.multiupload.com/21J01SXJ6Z <----Supercharged V 2
http://db.tt/MtDaBE8O <----Supercharged Atrix Rom
http://www.multiupload.com/IZVCVPRNGJ <----Stock Deodexd Rom Direct Link
http://forum.xda-developers.com/showthread.php?t=1420980 <----Stock Deodexed Thread
Thanks for clicking Thanks!!
*********Thanks*********
Thanks: Jimbridgeman-No ciq and more advice then you can shake a stick at , Shady_lanen-Theme base, most of updater script and power toggles, Nitro-Battery Icons,fenny-webtop mod,hashcode,Jydaddy, zeppelinrox, tylercarter... If I forget ya PM me and i'll put it up.
A special thanks to all of you willing to test almost everything I throw at you, It helps so much thanks guys.
Xda Member Script is nice enough to host the rom's free of charged, Please click this link and click thank's! http://forum.xda-developers.com/member.php?u=441777
Hey guys sorry for taking so long to do well... anything :-(. Since I have let my A2 go to take advantage of an amazing opportunity presented to me by another smart phone manufacturer I weighed the options of just letting the supercharged rom die or hand it over to one of the other amazing devs here for the a2. And after literally 354 pm's requesting updates, fixes, or just to get back in the game it became clear I couldn't let it die! And lucky for you guys rdavisct is willing to take the rom on! I hope you all the best of luck and I know you are all in great hands with rdavist. I encourage you all to check out his work and to stay tuned as I know he will make great things happen for your devices! Thank you guys for all your support and hard work, You made a dev out of a tinker lol.

************A note on over clocking***********
For best results this is how ya need to do it. (only if you are using the old method exp typing 1200 into terminal emulator)
-Do not over clock until your phone is fully loaded (feels like setup lag is gone)
-Use motor_hot_plug governor
-Set min and Max to 1000
-Reboot the phone
-Wait till the phone is fully booted (again feels like lag is gone)
-Now open terminal emulater and type "su"
-Now type "1100"
-Run at 1100 for a few mins put some stress on it at 1100
-Now go to terminal emulator and type "su"
-Now type "1200"
****I'm seeing much better results if I "break it in" the over clock as opposed to just jumping in at 1200****
Thanks to Rick#2 for this overclock method.
Original OC thread http://forum.xda-developers.com/showthread.php?t=1341514
************READ ME************
If you are running V4 you will need to delete the file OC3 in system/ect/init.d in order to use this overclock method, the default method in V4 is different then this one but they are both included. Please read the post linked below to learn how to set your own clock speed.
If you want to OC to say 1200 you would open terminal emulator type su, then echo 1200000000 > /proc/opptimizer
Another option is say you know your phone is stable at 1250 you could go to /system/etc/init.d open the file oc3 and change the values to 1250000000 and you would be at 1250 on every boot. DO NOT SET THIS TO A LEVEL YOUR PHONE IS NOT STABLE AT YOU WILL BOOT LOOP.
http://rootzwiki.com/topic/14511-op...4-overclocking-kernel-modulesofficial-thread/

Why distribute a rom as a backup?
It's just so much easier to maintain a rom like this, by just using the /system image for the restore we keep things small, simple, and updates can come much faster. We are also eliminating the possibility of a bootloop during flash to a new rom and we don't need a prep rom that causes gps issues! This will also mean the future updates in theory should never require you to format /data. That means we should not have to lose all our setting's in future editions of the supercharged roms!
____
-Beta;
It means the rom is a "WIP" Work In Progress, With enough of the features working to be a daily driver. In this stage the rom is not to be considered as a finished product or 100% stable. Expect bugs, (Report bugs!)
_____________
********Included in SCV5 update*****
-Like the lighter haptic feedback 2.3.6 has stock?? Me too... Here's how to get it back in SCV5.
1: Click here ----> http://depositfiles.com/files/fg1c2ro4e
2: From cmd or terminal type:
3: adb push framework-res.apk /sdcard/
4: adb shell
5: su
6: mount -o rw,remount /dev/null /system
7: cp /sdcard/framework-res.apk /system/framework/
8: reboot
9: All Done!
__________________
***********MD5**********
SuperCharged V5_Update_2 618A7E1EC527439459717391BDACEB07 *SuperCharged_V_5_Update_2_Do_Not_Flash.rar
SuperCharged V5 AC513654F485042DE5A3E3686031C1B4 *SuperCharged_V_5_DO_NOT_FLASH.rar
SuperCharged V4
SuperCharged V3 35BAE13E25D61A1E3531EECE446F3C2B *SuperCharged_Atrix_V3.zip
SuperCharged V2 CA30B7CDE32C633C8E74EC0005D3C700 *SuperCharged_Atrix_V2.zip
SuperCharged V1 257B237EB0566E679591FB1D493A8A3E *SuperCharged_Atrix.zip

Sounds great! Where can we download it? Thanks

I heard dropbox will get upset if you share to much, have you thought about www.multiupload.com just an idea.
Sent from my MB865 using xda premium

Zoide_ said:
Sounds great! Where can we download it? Thanks
Click to expand...
Click to collapse
It's up now!
kleeman7 said:
I heard dropbox will get upset if you share to much, have you thought about www.multiupload.com just an idea.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Yeah, I will. It's just dropbox is so easy I mean come on in windows it's just a drag and drop to the internet!

lfaber06 said:
It's up now!
Yeah, I will. It's just dropbox is so easy I mean come on in windows it's just a drag and drop to the internet!
Click to expand...
Click to collapse
Agreed, lol. I love dropbox.
Sent from my MB865 using xda premium

I see the link to the new rom is up Could you please provide a link to the "stock deodexed rom"? Thanks

This is working well so far.
So far, Overclocking with opptimizer doesn't need to run for 24 hours to work properly; at 1275mhz I'm beating a galaxy nexus in antutu.
I kinda miss the stock blur homescreen

Do we have to use Go Launcher? Just wondering, Thanks again for another great looking ROM.

Love you lfaber! Great news to wake up to! Will flash tonight once I get home from work. I have the stock deodexed rom already on the phone and I will report back any issues, if I run into any. Thanks!

PeteSeiler2010 said:
Do we have to use Go Launcher? Just wondering, Thanks again for another great looking ROM.
Click to expand...
Click to collapse
You can install another launcher if you wish. I prefer ADW Launcher on my touchpad... It works well here too.
Also, I was able to restore the stock launcher
Drop BlurHome2.apk from the StockRootedOcWebDeodex zip back into /system/app directory, reboot, then install Moto Home Fix to switch to it.

I was wondering if i could use the themes from the StockDeodexRootTogglesOc-2 rom?
So I decided to go ahead and install the ROM and realized that the theme is already there.

Running this all morning so far, its nice and fast and stable, Thanks again!

PeteSeiler2010 said:
Running this all morning so far, its nice and fast and stable, Thanks again!
Click to expand...
Click to collapse
How is your battery life so far?

i installed everything and it looks great so far!
however when i try to open AnTuTu i get a force close.
any ideas?
nevermind.
i updated the app and all is well!

When I try to open my google account to stop it from syncing certain things i get a FC that states. "The application Accounts (processcom.motorola.setup) has stopped unexpectedly. Please try again"
I also am not able to find the email app. I use exchange and can add my account but not able to find the emails.

Coldheat1906 said:
How is your battery life so far?
Click to expand...
Click to collapse
My battery was holding its own pretty well, I would not be able to give an actual percentage now though, I plugged it in to transfer some files and forgot to unplug it...

duke8804 said:
When I try to open my google account to stop it from syncing certain things i get a FC that states. "The application Accounts (processcom.motorola.setup) has stopped unexpectedly. Please try again"
I also am not able to find the email app. I use exchange and can add my account but not able to find the emails.
Click to expand...
Click to collapse
Fixed in v2
moofree said:
You can install another launcher if you wish. I prefer ADW Launcher on my touchpad... It works well here too.
Also, I was able to restore the stock launcher
Drop BlurHome2.apk from the StockRootedOcWebDeodex zip back into /system/app directory, reboot, then install Moto Home Fix to switch to it.
Click to expand...
Click to collapse
BlurHome is back in v2 just use home switcher from the market.
duke8804 said:
I was wondering if i could use the themes from the StockDeodexRootTogglesOc-2 rom?
Yes but you would get the carrier logo back (AT&T logo in status bar) I have not updated them yet.
Click to expand...
Click to collapse

Is the link in the OP for V1 or for V2? This is the one I see:http://db.tt/MtDaBE8O. The filename is SuperCharged_Atrix.zip
Thanks for your great work!
EDIT: I see you added the link for V2 just now

{
"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"
}
an AROMA based Touch UI Recovery Installer
As seen on Valhalla Black Edition and Team Acid AOKP​
Please tell me if you're going to use this in your ROMs just so I know who is using it . Thank you.
This is for ROM chefs only, not for regular users. Regular users, you will see this in all your ROMs soon .
All the instructions below refer to the files in META-INF/com/google/android
You can change the splash image by replacing aroma/splash.png (make sure it's a PNG though)
As mentioned in the installation instructions, make sure your ROM's zip file matches that of Valhalla Black Final's for best results.
Full touch screen support
Allows for a typical install, using default settings
Allows the user to customize the ROM installation
Allows the chef to customize the user experience
Support for different themes/skins
Installs Busybox
Installs kernel if you desire
Installs modem if you desire
No need to check mounts, the installer properly mounts the partitions for you.
No need to format partitions, the installer can wipe them for you.
Download and extract the installer zip file
Edit aroma/installer.default.prop to set your ROM's information
Rename installer.default.prop to installer.prop
Edit aroma-config and updater-script to your liking
Extract your current ROM's zip
Delete your ROM's META-INF folder
Put the new SGS4G CWM Rom Installer's META-INF and tools folders in your ROM's root
Make sure your ROM's file structure matches that of AOKP Unofficial by TeamAcid, unless you know what you're doing
Create a new zip file
Flash away and test!
If you use this tool you have to link back to this thread and give me credit using the link. Example:
My ROM uses the SGS4G ROM Installer by FBis251
http://forum.xda-developers.com/showthread.php?t=1481228
installer.zip
Installer on GitHub
You can download installer.zip from the link above to get the latest version of the installer files to package into your own rom.
Octoboer 13, 2012
Remove touchscreen calibration fix /data extract bug
-- With aroma 2.55+ touchscreen calibration is no longer necessary
-- /data packages should get extracted properly after a /data restore
Updated to latest AROMA binary (2.56)
-- Much more stable binary in ICS recovery!
---- The newest binary hasn't crashed on me yet during testing unlike the older version (2.50) that was included in the last version of the SGS4G Installer.
Here is the AROMA changelog since the last version included in the SGS4G Installer
EDELWEIS - 2.56 - BUILD 121004-031
Fix capacitive button
Remove calibration tools
EDELWEIS - 2.55 - BUILD 121003-030
Completely new Input/Touchscreen Handler - Thanks to agrabren from TWRP
Remove all calibration need. calibtool(), calibrate() and calibrate_matrix() won't do anything now.
EDELWEIS - 2.51 - BUILD 120810-026
Supported Galaxy Nexus Touch Screen - And maybe other devices now supported
Click to expand...
Click to collapse
July 18, 2012
ICS public release
May 25, 2012
Fixed bug that wouldn't mount partitions
-- Added support for mounting /efs
Added /efs partition info to installer.default.prop
Fixed a bug that would cause redbend_ua to restart the phone while flashing
-- (Thanks to itzik2sh from xda-developers for the fix)
Updated efs-backup
Now only checks whether /efs is empty
-- Will be compatible with devices that don't use an nv_data.bin
May 23, 2012
Updated scripts for easier porting
-- aroma-config and updater-script now uses information from installer.prop
-- porting to new devices will now be a lot easier because of this
Updated efs-backup script
--Backups now only take up ~560kB of space, compared to 6.3mB before!
Added colors to the installation confirmation screen
May 2, 2012
Changed to using installer.prop file for controlling all the variables
-- Chefs no longer need to edit the main AROMA script
-- AROMA checks if the installer.prop file exists to prevent users who flash the zip from messing up their phones
Added an installation option confirmation screen to make sure users know what options were selected
April 15, 2012
Updated to aroma-2.00-120414-A7
Now checking for phone version using a kernel check. Should prevent Froyo users from installing a GB ROM
Fixed a bug that would always do a free space check even when the user didn't try to do a /data backup
Now doing a /data restore before the kernel flash. Some ROMs caused the phone to reboot once the kernel flashed which means the /data restore never happened.
March 11, 2012
Updated AROMA binary to 2.0a4
Changed busybox version back to busybox v1.19.0.git
Now using aroma's TrueType font support
-- Installer uses the rom's default font (DroidSans)
Updated ROM information screen
Reboot prompt moved to the end of the installation
Updated Agreement to add formatting
Added efs-backup script which makes a backup of the efs partition
-- Saved under /sdcard/aroma-backup
Now has UTF-8 and RTL support!
March 3, 2012
Forced installation of busybox
Updated busybox to bonsai's version v1.17.1 (2010-08-12 23:44:34 CDT)
Fixed a bug that wouldn't allow the data backup and restore scripts to run
Moved mke2fs.conf to tools directory
Updated the sdcard free space check for /data backup
-- Will now only warn users when they selected the backup option in customized installs
March 3, 2012
Cleaned up a lot of the aroma-config code for easier reading
Deleted duplicate busybox binary
Deleted changelog.txt since no one used it
Added .gitignore
Updated busybox binary to version 1.19.4
Added monospace font
Now using the latest aroma nightly Version 1.62 build 120303-030
Using the latest themes from the nightly
Added a check to disallow /data backup when there isn't enough free sdcard space
-- Added a warning for the user to know the backup isn't going to happen
Updated touchscreen calibration values
Now displays filesystem and ROM information on the same screen
-- Added sdcard filesystem information
Reboot no longer done in the updater-script
Changed symlinks in updater-script to use busybox for more functions
Feb 12, 2012
Added aroma theme support. Check aroma/themes/
Added three themes, sense, MIUI and ICS (default ICS)
Added MIUI icons
Added filesystem (disk free/total and percentage used) information viewbox
Added ext4 format from bonsai's installer script.
-- Now does a full ext4 format and tuning before the install
Now allows choice of splash animation instead of static splash screen
Removed a lot of whitespace from aroma-config
Removed options to do wipes since the format takes care of this
Added data backup option
Now using bonsai backup. Left compression enabled for minimal sd storage usage.
Backup may take up to 10 minutes to complete!
Removed color.prop (no longer needed due to themes)
Changed checking for SGH-T959V to allow you to continue in case there is no ROM installed.
Feb 5, 2012
Edited updater script to output all installer options to one prop file
Now using variables in aroma-config for easier writing of the final options.prop file
Cleaned up updater-script to only use one .prop file
Fixed a bug that would make the wipe /data dialog come up even when deselected in the customized install
The script will now ask the user if they want to reboot their phones in all instances before the install gets going.
Now using Roboto font
Added color.prop file to control theme colors
Updated the wording on the install type chooser
Click to expand...
Click to collapse

FB
I was just gonna thank you for this over on Black thread. Glad you got this out for folks. Slick very slick. Who needs ROM manager(mangler) when you're around. So thanks to you and everyone else who worked on it.

I just used this a few hours ago I installed the black final rom with touch screen features is cool!
Sent from my SGH-T959V using XDA Premium App

FB, I will be using it for the next edition of AOSP Style coming out soon. I have already built mos of the rom and its installer, but I needed verification.

airfluip1 said:
FB, I will be using it for the next edition of AOSP Style coming out soon. I have already built mos of the rom and its installer, but I needed verification.
Click to expand...
Click to collapse
Sounds good. Just follow the OP if you'd like. I'm sure you already looked through the scripts. You should theme the installer to make it look like your ROM .

airflip if u are using my rom as a base its already in there .... which u asked me to use so.....

FB, I just flashed Raver's final and everything flashed fine then when the installer was done it showed an error having to do with not finding a path for something. I was going to re do it and copy the error down but now the phone is stuck at the T-Mo screen and it won't go into recovery with the button combo. I'm going to Odin it in the morning and re-flash and see if it throws the error again and I'll let you know.

bswann said:
FB, I just flashed Raver's final and everything flashed fine then when the installer was done it showed an error having to do with not finding a path for something. I was going to re do it and copy the error down but now the phone is stuck at the T-Mo screen and it won't go into recovery with the button combo. I'm going to Odin it in the morning and re-flash and see if it throws the error again and I'll let you know.
Click to expand...
Click to collapse
Same error on my sgs4g I think it was a temp file error, didn't affect my rom booting though.
Sent from my Glacier using xda premium

bswann said:
FB, I just flashed Raver's final and everything flashed fine then when the installer was done it showed an error having to do with not finding a path for something. I was going to re do it and copy the error down but now the phone is stuck at the T-Mo screen and it won't go into recovery with the button combo. I'm going to Odin it in the morning and re-flash and see if it throws the error again and I'll let you know.
Click to expand...
Click to collapse
If it happens again, hit save log and send that to me. I'd really like to see it.

Gr8 job FB - thank you very much.
We'll probably also use it in our next version
10x

Thanks Guys!!!(Raver,FB)

FBis251 said:
If it happens again, hit save log and send that to me. I'd really like to see it.
Click to expand...
Click to collapse
FB, awesome work man. Lovin it. I had an error on my install but the ROM installed fine and booted fine. I made a log anyway so I could send it to you. Maybe it can be of some use.

alon2 said:
Gr8 job FB - thank you very much.
We'll probably also use it in our next version
10x
Click to expand...
Click to collapse
Awesome, don't forget to post here if you have any usage questions. I wound up taking out a lot of the comments for space, but I learned the syntax of the AROMA functions pretty well.
putsometrebleinit said:
FB, awesome work man. Lovin it. I had an error on my install but the ROM installed fine and booted fine. I made a log anyway so I could send it to you. Maybe it can be of some use.
Click to expand...
Click to collapse
Yes I'd love to see that.
airfluip1 said:
Thanks Guys!!!(Raver,FB)
Click to expand...
Click to collapse
No problem. I'm guessing it's working fine?

Cool very very neat. Never seen this on a phone before
Sent from my SGH-T959V using xda premium

FBis251 said:
Awesome, don't forget to post here if you have any usage questions. I wound up taking out a lot of the comments for space, but I learned the syntax of the AROMA functions pretty well.
Yes I'd love to see that.
No problem. I'm guessing it's working fine?
Click to expand...
Click to collapse
You are right. I am making this installer so customizable, from kernel to bootanimation.

airfluip1 said:
You are right. I am making this installer so customizable, from kernel to bootanimation.
Click to expand...
Click to collapse
I'm gonna release an update soon. You should look into it once I'm done since I simplified the updater-script portion of it.

What do you mean by "soon" because i may release 4.0 tomorrow. I just need to test my new features.

I'm doing final testing of the installer so in about an hour.

Feb 5, 2012
Edited updater script to output all installer options to one prop file
Now using variables in aroma-config for easier writing of the final options.prop file
Cleaned up updater-script to only use one .prop file
Fixed a bug that would make the wipe /data dialog come up even when deselected in the customized install
The script will now ask the user if they want to reboot their phones in all instances before the install gets going.
Now using Roboto font
Added color.prop file to control theme colors
Updated the wording on the install type chooser

Panicking right now because I can't seem to PM you FB.
I hope I don't come off as a stickler for details, but there's just a single typo in what is the 6th screenshot posted in the OP. It's for the option where you can choose to Wipe Data.
"...another ROM. Don't select if you want to keep your ap"
I'm assuming it was supposed to say "apps."
Just wanted to make note of it as I saw that Raver updated the contents in the aroma folder within the META-INF directory for his Valhalla Black rom. I was just thinking the typo might've been updated or something somehow.

IMPORTANT: If you updated your system to Android 4.1.2, *DO NOT* flash either _motley kernel, as they are built on 4.1.1 and contain the wrong interface to the power management chip. This will result in a bootloop at the least, and possibly much much worse
What we're doing, here, is turning your n7 into a multitasking muscle-machine, and giving it the I/O throughput to match. These instructions are for the stock ROM, but can be applied to any ROM with a little modification. Enjoy!
Do the OTA update to 4.1.1 (if you're stock and haven't, already), and then......
[KERNEL][GPL][Linaro][OC 1.6GHz][UV][GPU+][ZRAM][SIO+V(R)] 2012-08-10 motley 1.1.1
From that thread, you need:
a) the 1.1.1 kernel of your choice
b) the 1.0.5b kernel with ramdisk (if you're already running a custom ROM with init.d support, you don't need this, nor do you need to create /system/etc/init.d in a future step)
You'll also need:
a) root
b) cwm
c) busybox (absolute must, make sure your symlinks are proper)
d) some type of root-enabled text editor (I use root explorer)
e) a full featured cpu/sd management app (I use System Tuner)
BEYOND THIS POINT, THERE BE DRAGONS. I'm not responsible if you FUBAR your device, but if you follow my instructions to the letter, you won't
0.5) READ THIS ENTIRE POST BEFORE PROCEEDING
1) install cwm and root your tab (if you haven't already)
2) reboot into CWM, flash the 1.0.5b kernel with ramdisk (if you're on stock or a stock-based ROM without init.d support), then immediately flash the 1.1.1 kernel you chose (gpu overclocking is nice and all, but I haven't found a game that doesn't run perfectly with the stock GPU speed of 416MHz..Looks great on benchmarks, though)
3) reboot back into JB, fire up root explorer, remount /system rw, create a folder in /system/etc called init.d (permissions rwxr-xr-x), create a file in it called S90zRAMandSpeedTweaks (permissions rwxrwxrwx), and long-press to open it in a text editor
4) make it look like this:
Code:
#!/system/bin/sh
#remount /data for faster i/o
mount -o remount,noauto_da_alloc /data /data
#disable fsync (controversial, I've been doing it for years with no real issues)
echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled
#set zRAM size (recommended sizes are 64 and 128, as this compresses an actual block of RAM. Setting it higher will likely impede performance)
echo $((1024*1024*128)) > /sys/block/zram0/disksize
#use busybox to create and activate zram0, if busybox is not in /system/xbin, modify accordingly
/system/xbin/busybox mkswap /dev/block/zram0
/system/xbin/busybox swapon /dev/block/zram0
It's important to leave at least one trailing line in scripts. Just trust me, it's a linux thing.
*NOTE* The above script does NOT check to see if it was successful, but if you copied it directly and installed busybox to /system/xbin then it will work. Once you reboot in a few minutes, you can check by using the command "busybox free" from a terminal emulator or adb shell
5) Save the file, delete the .bak now in that folder, and close root explorer.
6) Open System Tuner, tap on the SD option, change cache to 1024 and scheduler to deadline
7) Tap the Voltage option and hit -25 4 times and save the settings as voltage_table_uv
8) Tap the CPU option and tap Boot Settings. For CPU and SD, set the method to init.d
9) Close System Tuner and reboot your device.
10 Profit/consume butter
It seems like a lot, but it really only takes about 15 minutes if you're a complete rooting n00b, and the end result is a buttery-smooth multitasking powerhouse (that blows iOS *away*). The 100mV undervolt also greatly extends battery life. I haven't had ANY issues at -100mV, but if you do, just increase it by hitting +25 on the voltage tab of System Tuner until you have something that works for you (in fact, you might want to start at -25mV and slowly grow it to -100mV, playing games and checking for instablity along the way)
It's also worth mentioning that if you're currently completely stock, you will need to unlock your bootloader to root and install CWM, and unlocking the bootloader wipes your device (no way around it, unfortunately. Hook your N7 up to your computer and backup the entire contents of /storage/sdcard0 to make restoring your data as painless as possible)
farmerbb's scripts - If you're having trouble getting your scripts to stick, or just don't want to be assed with installing System Tuner, use these! There are three different packages, for 64MB, 128MB, and 256MB zRam setups. Thanks, farmerbb!!
------- Revisions as of 9/1/12 -------
Fixed first line of script so it will actually run
Fixed zRam settings, as zRam is a block of actual RAM, not written to storage
Removed JRummy busybox installer as recommended. Use whichever you like, just make sure your symlinks are good

Awesome guide. Can't wait to try this out!

Thanks for the share..

Sounds good, will try this out tomorrow.

Dont suppose anyone has a copy if 1.0.5? Removed from Motleys OP
Nvm, went on web version and it was there
Sent from my Nexus 7 using xda app-developers app

Nice to see your thread here.
Sent from my GT-I9100 using xda premium

Copied this over from the other thread to show that it works:
clankfu said:
Here's my Androbench after applying the zRAM and fsync tweaks that Jay Aristide posted on page 6. I didn't really have a problem with lag but now my N7 is absolutely flying! Only minor annoyance is that my System Tuner settings won't stick after a reboot.
{
"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"
}
And here's my Androbench before I did the tweaks for comparison:
Click to expand...
Click to collapse

I'm out of thanks for the next few hours, so here's a ^5! Glad it's working well for you

Jay Aristide said:
*NOTE* The above script does NOT check to see if it was successful, but if you copied it directly and installed busybox to /system/xbin then it will work. Once you reboot in a few minutes, you can check by using the command "busybox free" from a terminal emulator or adb shell
/QUOTE]
What should it say here if it worked? Thanks for the guide
Click to expand...
Click to collapse

ChrisJ951 said:
What should it say here if it worked? Thanks for the guide
Click to expand...
Click to collapse
For the last line, you'll see numbers next to "Swap" instead of just zeroes.

Thank you very much for gathering and presenting all that information. One question though. Does any of this impacts battery life?

sotoskawasaki said:
Thank you very much for gathering and presenting all that information. One question though. Does any of this impacts battery life?
Click to expand...
Click to collapse
The undervolting increases your battery life.

so just to make sure before attempting this mod:
im on stock 4.1.1 rooted with cwm
i need :???????
motley_nexus7_with_stock_ramdisk_v1.0.5_build_39.zip
and witch one of those??
motley_anykernel_nexus7_1.1.1_NoGPUOC_build_220.zip (GPU stock 416GHz)
motley_anykernel_nexus7_1.1.1_GPU484_build_219.zip (GPU OC 484MHz)
motley_anykernel_nexus7_1.1.1_GPU520_build_218.zip (GPU OC 520MHz)
thanx

guinnes.s said:
so just to make sure before attempting this mod:
im on stock 4.1.1 rooted with cwm
i need :???????
motley_nexus7_with_stock_ramdisk_v1.0.5_build_39.zip
and witch one of those??
motley_anykernel_nexus7_1.1.1_NoGPUOC_build_220.zip (GPU stock 416GHz)
motley_anykernel_nexus7_1.1.1_GPU484_build_219.zip (GPU OC 484MHz)
motley_anykernel_nexus7_1.1.1_GPU520_build_218.zip (GPU OC 520MHz)
thanx
Click to expand...
Click to collapse
Yes to the first one and take your pick with the second ones the only difference is the GPU overclock, stock works just fine so try that first
Sent from my CM9 TouchPad using Tapatalk 2

guinnes.s said:
so just to make sure before attempting this mod:
im on stock 4.1.1 rooted with cwm
i need :???????
motley_nexus7_with_stock_ramdisk_v1.0.5_build_39.zip
and witch one of those??
motley_anykernel_nexus7_1.1.1_NoGPUOC_build_220.zip (GPU stock 416GHz)
motley_anykernel_nexus7_1.1.1_GPU484_build_219.zip (GPU OC 484MHz)
motley_anykernel_nexus7_1.1.1_GPU520_build_218.zip (GPU OC 520MHz)
thanx
Click to expand...
Click to collapse
The middle one works best IMO, but they will all do what you seek
Sent from my Nexus 7 using xda app-developers app

BIGSimon said:
Yes to the first one and take your pick with the second ones the only difference is the GPU overclock, stock works just fine so try that first
Sent from my CM9 TouchPad using Tapatalk 2
Click to expand...
Click to collapse
done, it seems is not working i still have no numbers next to "Swap" instead of just zeroes

guinnes.s said:
done, it seems is not working i still have no numbers next to "Swap" instead of just zeroes
Click to expand...
Click to collapse
Did you run the busybox installer you downloaded from the play store and have it install busybox to /system/xbin?
From terminal emulator, type
busybox which busybox
If it says anything other than /system/xbin/busybox you'll need to modify the script accordingly
Sometime in the next couple days, I'm going to make a cwm-flashable zip that does everything.. I just need to read up on how

Jay Aristide said:
Did you run the busybox installer you downloaded from the play store and have it install busybox to /system/xbin?
From terminal emulator, type
busybox which busybox
If it says anything other than /system/xbin/busybox you'll need to modify the script accordingly
Sometime in the next couple days, I'm going to make a cwm-flashable zip that does everything.. I just need to read up on how
Click to expand...
Click to collapse
Yes is installed in the right place and typing the busybox command it gives that directory. I jus copy and paste ur code when creating the file? ?is that OK, I have the 16gb model.

guinnes.s said:
done, it seems is not working i still have no numbers next to "Swap" instead of just zeroes
Click to expand...
Click to collapse
Mind didn't work until I ran the script via Script Manager. Download the app, find that zRAM script file you created in the init.d folder, select it, choose script, press the SU & boot icon up top and press Run. You'll see it run in command and say zRAM successful. Press Back and then save it.
For some reason, System Tuner doesn't seem to want to play nice with this script - at least for me.

guinnes.s said:
Yes is installed in the right place and typing the busybox command it gives that directory. I jus copy and paste ur code when creating the file? ?is that OK, I have the 16gb model.
Click to expand...
Click to collapse
If you're doing it in notepad, that's the problem. Notepad++ works if you choose Unix encoding

CM10.1 "WEEKLIES"!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This ROM aims at bringing to the G2X community what it deserves : a fully working jellybean (this is NOT the hackfest) build based on CM10.1 (android 4.2.1). I wanted this powerful device to get the very best, and now it will get the most recent android system, updated whenever I will have some time to. Never again, we will wait for LG to update this device.
As most of you know, the radio doesn't work, which means no calls/SMS on CM10/10.1. That is why I adapted a dual boot system (based on bihariel's work) for this device.​
WHY DUAL BOOT?
With dual booting, you can choose between two ROMS and change from one to another in less than 20 seconds!
You can change to CM10.1 to...
- Feel what it means to have a buttery smooth device
- Play games
- Make free WIFI calls (US and Canada) with GrooveIP lite
- Use the most recent android OS.
When you're on the go, change to a CM7/CM9/CM10 (hackfest) ROM...
- FAST!
- Without altering the CM10.1 files
- To make phone calls and receive SMS
DISCLAIMER
I AM NOT RESPONSIBLE of any damages to your device related to the use of this ROM or the dualboot toolkit. You do this at your own risk. Even though this has been tested and works well, using NVFLASH may brick your device if done incorrectly.
INSTALLATION INSTRUCTIONS
This ROM comes in two flavours: The dualboot toolkit or the Original flashable ROM
Dualboot ROM Instructions
WARNING! NVFLASH will format EVERYTHING, including internalSD. Make sure you backup your important files on your externalSD card
PART 1 - Resizing system partition
1) Unzip the dualboot toolkit and unzip NVFLASH_Resizer-G2X.zip.
2) Power off your phone and remove the battery. Keep vol. up and vol. down held and plug the phone via USB to a WINDOWS computer.
3) Windows should add an "APX driver". Go to control panel -> Device manager and right click on it -> Update driver -> search in system. Then, browse to the drivers folder inside the NVFLASH package and choose nvidiausb.inf. Approve any error messages (Windows 8 users read my FAQ). Install the Nvidia Fastboot driver.
4) Unplug your phone and hold down vol.up and vol.down. Replug it again and double click on flash.bat inside the NVFLASH folder. KEEP BOTH BUTTONS HELD DOWN DURING THE WHOLE PROCESS!.
5) When NVFLASH is done, unplug the phone and put back the battery. Reboot into recovery with power + vol. down. Plug it back and go to mounts and storage -> mount USB storage. If your PC asks to format the internal SD card, select yes.​
PART 2 - Installing ROMS
1) Download the desired "call/SMS" ROM and extract boot.img from it's flashable zip. Rename it to boot1.img. Extract Step3_bootimg.zip from the dualboot toolkit and copy-paste boot1.img into system/boot, replacing the file that is already there. Repack Step3_bootimg.zip.
2) Copy-paste your desired ROM into the 0dualboot folder and send it to your device SDcard with everything it contains (your device should already be in the "mount USB storage" menu).
3) From the recovery, flash Step1_enabler.zip. When the screen goes black, hold power + vol. down to get back into recovery.
4) Flash your desired ROM, then Step2_ROM1.zip. Reboot to the OS.
5) You should have a Systemchanger app. Open it, click on "Switching" and give root permissions. When the screen goes black (again...), hold power + vol. down to get into recovery.
6) Flash ROM2.zip and Step3_Bootimg.zip and reboot in the OS
And there you go! To switch from one OS to another, just open the systemchanger app and click on "switching"!
Credits to bihariel for the original method. See the original thread here.​
Original flashable zip ROM instructions
1) Boot into recovery with power + vol. down
2) Wipe data/cache, then mounts and storage -> format system
3) Flash this ROM
4) Advanced -> Wipe dalvik cache and fix permissions
5) Reboot and enjoy!​
Special trick : In settings, go to About phone and click 6 times on Build number. This will pop up the developer and performances options. In performances options, CPU settings, change the governor from INTERACTIVE to SMARTASSV2.
Download links
ROM with DUALBOOT Toolkit ***BETA***
DOWNLOAD HERE!
Original flashable ZIP (For single boot)
DOWNLOAD HERE!
Credits and thanks
See my original thread here for the full list!
Thanks to bihariel for the original method for the Optimus 2X which I adapted for the P999. Great job!
Special thanks to Core Memory for helping me start this project​

CHANGELOG
***
V.2
Mazout360's kernel V.0122
Based on CM10.1 (Android 4.2.2)
Comes with Google Apps (20130301)
Patched Service.jar
LG Bootanimation
Stable and no hot reboots
GrooveIP for free US/Canada calls
Radio disabled (battery saving)
V.1 (original release)
Mazout360's kernel V.0104
Tweaked and fast!
Comes with Google Apps (20121212)
Patched Service.jar
LG Bootanimation
Fixed Facebook sync (untested yet)
Fixed SDcard detection by apps
Mass storage working
ADB working
Stable and no hot reboots

FAQ
I am using Windows 8 and I cannot install NVFLASH drivers!
In windows 8, you will need to go on Select Settings (right bar)/More PC Settings (at bottom). Then go General/Advanced Startup/Restart Now/Troubleshoot/Advanced Options/Windows Startup Settings/Restart. Disable driver signature enforcement (should be options 7 I think). If you don't get to the advanced startup menu, keep pressing F8 when rebooting.
I am getting Status 7 errors while flashing this ROM!
This is possible, and to fix this simply flash another CM10.1 ROM before (adampk's build 7) and dirty flash this ROM again. If it doesn't work, go to mounts and storage and manually mount /system.
I found a bug, can I submit a logcat ?
Yes, but make sure you are taking a logcat while the bug happens. Please post them in a userthread or send them to me via PM. Thanks!
I have a suggestion for your ROM...
...and I'm always open to them! Whether it's for integrating new apps, themes, tweaks, I'm always open for good ideas! PM me or post in the user thread.
I am experiencing FC and some base apps are missing!!
This is not normal. I've been running this build for two days in a row and didn't have a single issue. You should consider reinstalling using the Original flashable ZIP package. Simply boot to CM10.1, power off the phone, then get into recovery using power + vol. down and follow the instructions (if you are using the Dualboot Toolkit).
USERTHREAD HERE : http://forum.xda-developers.com/showthread.php?t=2127810 (Thanks to Yuvin for maintaining it!)

Re: [ROM][CM10.1] Mazout's CM10.1 weeklies with DUALBOOT Toolkit![V.beta1]
Appreciate this friend. You are quite generous.
Sent from my LG-P999 using xda app-developers app

Thanks a lot, I'll try it as soon as possible

Re: [ROM][CM10.1] Mazout's CM10.1 weeklies with DUALBOOT Toolkit![V.beta1]
This looks great. You are one of the best developers out there
Sent from my LG-P999 using xda app-developers app

Re: [ROM][CM10.1] Mazout's CM10.1 weeklies with DUALBOOT Toolkit![V.beta1]
Whoa. I think I'm going to try it out. Maybe a stable Gingerbread ROM like hellfire for calls to back up the CM10 goodness. Would switching ROMs often, like 3 or 4 times an hour, have much impact on battery?
Sent from my LG-P999 using xda app-developers app

plarmann said:
This looks great. You are one of the best developers out there
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Thanks! This was not my main project as this is only a port of cm10.1 (with some fixes and many tweaks to make it interesting of course ) because I had some issues with the other one but I'll try to make this one as useful as possible even without radio. I actually compiled this and realized that it was very efficient and functional.
Ravinxx said:
Whoa. I think I'm going to try it out. Maybe a stable Gingerbread ROM like hellfire for calls to back up the CM10 goodness. Would switching ROMs often, like 3 or 4 times an hour, have much impact on battery?
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Switching ROMS shouldn't have a very big impact on battery usage. Changing the CPU governor to SMARTASSV2 and keeping airplane mode on (in CM10.1) might help somewhat, but I already silenced the radio so it shouldn't use too much battery anyway.
If everything goes as planned, I should release another kernel build by tomorrow to add some interesting features and the upcoming "weekly" updates for this ROM will be available as "patches" for those who already have the dual boot set up to make it as simple as possible. Of course, new users will also have the full CWM flashable zip version.

I installed Original flashable ZIP (For single boot). It's the one that I am looking for a while.
• Jelly Bean 4.2.1
• 1080p Camera
• Fast / Classic / Common&Known / Simple / Stable
• Good&Concerned Developer

I don't know what's going on but after I unziped this dual boot file with 7zip and I went into the "0dualboot" folder then the "NVFlash_Resizer-G2x" and in there I find the "Drivers" folder like you said. However, in the drivers folder is the "amd64" and "i386" but both of those folders are empty. Nothing is inside them at all. Am I missing something? This is on Win7 so should find it just fine. Can anyone help me with this?
Edit: I just downloaded the file "DBToolkit_cm10.1_p999" for the 3rd time with the same problem. Also the file you specified, "flash.bat" isn't showing up either in the NVFlash folder.

Thank you so much. I hope people like you keep the G2X development alive.
Thanks again.

draky said:
I don't know what's going on but after I unziped this dual boot file with 7zip and I went into the "0dualboot" folder then the "NVFlash_Resizer-G2x" and in there I find the "Drivers" folder like you said. However, in the drivers folder is the "amd64" and "i386" but both of those folders are empty. Nothing is inside them at all. Am I missing something? This is on Win7 so should find it just fine. Can anyone help me with this?
Edit: I just downloaded the file "DBToolkit_cm10.1_p999" for the 3rd time with the same problem. Also the file you specified, "flash.bat" isn't showing up either in the NVFlash folder.
Click to expand...
Click to collapse
Oh woah my bad...I honestly don't understand why it's missing files in the NVFLASH package..Well it's being reuploaded at the moment so it should be ready in about 5-10 minutes.
Sorry for this.
I will download it myself and verify it to make sure everything is okay now...If something is wrong just reply back
EDIT: Okay it's back up and I verified everything so you should be good.

Re: [ROM][CM10.1] Mazout's CM10.1 weeklies with DUALBOOT Toolkit![V.beta1]
So do we have to use nvflash to flash these roms

faratl said:
So do we have to use nvflash to flash these roms
Click to expand...
Click to collapse
Use the single boot (Original flashable zip) if you do not want to use nvflash. For dual boot, you don't have the choice. If you backup everything with titanium backup on your externalSD or computer you shouldn't lose anything though.

Mazout360 said:
Oh woah my bad...I honestly don't understand why it's missing files in the NVFLASH package..Well it's being reuploaded at the moment so it should be ready in about 5-10 minutes.
Sorry for this.
I will download it myself and verify it to make sure everything is okay now...If something is wrong just reply back
EDIT: Okay it's back up and I verified everything so you should be good.
Click to expand...
Click to collapse
Just downloaded it and it has stuff in there. Thank you!

hey man thanks for your work, where you found time to tinker with our little dual boot problem, while working on the kernel and everything else, i wont ever know. dang dude. will be trying this out after i replace my wifes screen tonight. i would say the G2X community owes you one...or more. thanks again!

Ok, so I was installing this dual boot and ran across a problem, I, now, cannot mount the system or cache after the first step... So I cannot get a ROM on my phone to work at this time. Any ideas?

draky said:
Ok, so I was installing this dual boot and ran across a problem, I, now, cannot mount the system or cache after the first step... So I cannot get a ROM on my phone to work at this time. Any ideas?
Click to expand...
Click to collapse
Restart the NVFLASH process. Make sure you keep vol. up and vol. down held during the whole process. Plug the phone directly in a USB port from your motherboard (not in a splitter or a front port, for example). Also make sure you followed the instructions correctly and that the bootloader and recovery files are completely sent when running NVFLASH.
Oh also, verify that you have the correct drivers installed (Nvidia USB-boot driver or something like that) and extract everything for the NVFLASH archive.
Just to make sure the archive is okay now, can I have a confirmation of someone who tried it and it worked ?

Mazout360 said:
Restart the NVFLASH process. Make sure you keep vol. up and vol. down held during the whole process. Plug the phone directly in a USB port from your motherboard (not in a splitter or a front port, for example). Also make sure you followed the instructions correctly and that the bootloader and recovery files are completely sent when running NVFLASH.
Oh also, verify that you have the correct drivers installed (Nvidia USB-boot driver or something like that) and extract everything for the NVFLASH archive.
Just to make sure the archive is okay now, can I have a confirmation of someone who tried it and it worked ?
Click to expand...
Click to collapse
Thank you, I never thought to redo the NVFLASH.
Now, the NVFLASH opened a windows for a second or less when I told it to run. Is that normal?
And the APX drivers are installed correctly because I have been going from twrp to cwm and back without a problem.
I will try it again when I get home because my brother in law doesn't have a working pc. Will let you know and let me know about the NVFLASH please. Thank you
---------- Post added at 01:22 PM ---------- Previous post was at 01:01 PM ----------
Forgot to mention, the Window that opens on NVFLASH closes in less than a second so I cannot read it.

Awesome work Mazout! I'll try out this method after my exams are over, Also, do you want a new Userthread for this Dualboot system or will you use the older one?