For most up-to-date information on optimized libraries, please carefully read @osm0sis's post: http://forum.xda-developers.com/showpost.php?p=53963337&postcount=1287
You should also read @Lethargy's post in the Nexus 5 thread: http://forum.xda-developers.com/showpost.php?p=56038135&postcount=2918.
The outdated flashable ZIPs from this post have been deleted. Head over to post linked above for the latest libraries.
Have you ever wondered why your Nexus 4 performs worse than other flagship devices with the same quad-core CPU in benchmarks? Not any more! I present you with a very simple patch that will boost your performance to what other APQ8064-based devices offer.
Before using, please read the following Q&A.
Q: Will this void my warranty?
A: Yes. Flash at your own risk.
Q: Can I use it?
A: Yes, if you're on any 4.4/4.4.x ROM.
Q: How does this work?
A: This patch consists of two files that include optimized bionic and Dalvik libraries for any KitKat ROM.
Q: What is bionic?
A: It is a vital system library that provides i.a. basic math and memory access functions to every other library and application in Android.
Q: What is Dalvik?
A: In short, Dalvik is a virtual machine in which every not-native-code app runs. You can read more about it in a Wikipedia article.
Q: How do I benefit from this patch?
A: In two ways: bionic patch provides faster memory access and optimized some of the math operations, dalvik provides optimized Dalvik Virtual Machine library that allows faster code execution.
Q: Do I need this patch?
A: It depends on what ROM you are using:
if you're on stock ROM, you'll benefit from flashing both bionic and dalvik patches,
if you're using a custom ROM, you most probably don't need bionic patch, as these are already included in most custom ROMs. You'd benefit only from flashing dalvik patch (if it's not already included by your ROM maintainer, of course),
don't use the bionic patch on CyanogenMod, PSX and probably others, because they already have more optimized versions!
Q: Why aren't these patches included in stock ROM?
A: As for bionic - I don't know. Maybe that's because Google didn't want to include vendor-specific optimizations in AOSP or maybe simply because Qualcomm never posted them in Android Code Review to be merged. As for dalvik - because they are closed-source. Here'a a good explanation by @xboxfanj:
xboxfanj said:
Part of the point of Nexus devices is that AOSP can produce nearly identical images minus GApps. Google would not use a proprietary dalvik as that is one of the core libraries. Using a proprietary dalvik would undermine AOSP. Although, an open libqc-dalvik or even just giving us that binary would be nice. Google could have a device specific extension similar to the adreno extensions onto renderscript and egl for dalvik. Proprietary dalvik won't happen, but an adreno extension could be cool.
Click to expand...
Click to collapse
Q: Where do these patches come from?
A: These have been authored by Qualcomm. Bionic patch comes from Code Aurora Forum, Dalvik library has been extracted from Moto X 4.4. ROM. Another good read by @xboxfanj:
xboxfanj said:
CAF has all Qualcomm's bionic patches and slight dalvik tweaks, however, the dalvik patches that are used here in the Moto X and any QCOM (non-Nexus) device, are mostly closed source. If you look at the change here: https://www.codeaurora.org/cgit/qui...0&id=337a595d746d34ade52e3aba2c739455dfd3cf57
You will see that most of that change is supporting other libraries (libqc-opt and libqc-dalvik), which is where their optimizations are. Unfortunately, both of those are closed source. libqc-opt is included in QCOM ROM zips as a shared library, so we can use that, however, libqc-dalvik is a static library, so we can't pull that from anywhere, as it is included in the libraries themselves and not put in system. This means that our only option to get all of Qualcomm's dalvik optimizations is to use their binaries rather than building from source, since building from source would mean missing any optimizations brought by libqc-dalvik, libqc-sqlite, and libqc-skia (the last two haven't been included in any patch, but are QCOM static libraries).
TLDR: QCOM's dalvik optimizations are closed source, so we are forced to use their binaries.
Click to expand...
Click to collapse
Remember to thank @xboxfanj for his very useful posts!
Q: What is the reason for including installd file?
A: The installd binary is from stock Nexus 4 ROM and is included for compatibility with CyanogenMod and CM-based ROMs. This is because CyanogenMod changed installd to work with their dexopt-on-cache (see here: https://github.com/CyanogenMod/android_frameworks_native/commits/cm-11.0/cmds/installd) and it you don't flash stock installd you'd get hundreds of FCs and unusable ROM.
Q: How do I use this patch?
A: Simple flash it over your current ROM in recovery. Remember to wipe Dalvik Cache after flashing. Full wipe is not needed.
Q: How do I revert?
A: Simply flash over your current ROM and wipe Dalvik Cache afterwards. Full wipe is not needed.
Q: Can I flash it over an ODEXed ROM?
A: Yes, but it is strongly recommended to use a deodexed ROM if you want to use Dalvik patch.
Q: How will this affect my battery life?
A: It will be at least the same, if not better. Better performance = less CPU time spent on calculations = better battery life.
Q: I don't see any performance gains in some app, why is that?
A: The dalvik patch doesn't affect apps that use native libraries, i.e. you won't see much performance gain in Chrome etc.
Q: I'm on X kernel, can I use it?
A: Yes, use it with any kernel you like.
Q: Can I use it on other devices?
A: Yes, you can use this patch on every Krait device that uses AOSP-based ROM (examples: Nexus 5, Nexus 7 2013). Don't flash it on stock ROM on non-Nexus devices, as they already include these optimizations (that includes Galaxy S4 and HTC One Google Play editions!).
Q: What if I use it on stock ROM and OTA arrives? Can I install the OTA straight away?
A: You can't. You have to revert to stock libraries first. Keep in mind that every modification to stock ROM can mean problems when installing an OTA. You should revert to fully stock ROM to properly apply an OTA. For your courtesy, there's a revert ZIP attached for KRT15S and KOT49E ROMs. Remember that the safest way it to flash system.img from a factory image before applying an OTA once you made modifications to your /system partition!
Q: Can I use these patches on 4.4.1/4.4.2 stock ROM (KOT49E/KOT49H)?
A: Yes, you can.
Q: Can I use ART with this patch installed?
A: Yes, but you won't see any performance gains. In fact, with this patch Dalvik is faster than ART. I suppose ART will supersede Dalvik in performance in the future, but not yet.
Q: Where can I see some benchmark results before I flash?
A: Head over to Nexus 4 Benchmarks thread.
Q: Do I need to be rooted to flash this?
A: No. The only thing you need is custom recovery (CWM, TWRP etc.).
Q: Do I have to flash these patches every time I install an update/new ROM?
A: Yes.
Don't replace these files on a running system (i.e. via a file explorer or adb)! If you do this, your phone will stop working and you'd have to reflash your ROM to make it work again. And you'll probably loose some data by doing so. Always use recovery to replace these libraries.
If you're running CM11 released after 1 March 2014 or any other ROM that includes fixes to DVM, please flash 4.4_qc-optimized_dalvik-cm11.zip. This is the only file you need, don't flash anything else from this thread!
Nice job on the new thread!
Pure Speed X? ~ ViPER4Android ? [n⁴]
Yep, good to have a dedicated thread.
I did notice a slight change, with there being no more dexopt file, just checking that this is correct?
In the benchmarks thread, I saw a comment that it probably won't work on CyanogenMod ROMs. Is that true?
Sent from my SCH-I535 using Tapatalk
i got bootloop !
with 4.4 stock.
-----------------------------------------------
I tested the patches on my custom ROM and it seemed to me that I didn't need to replace dexopt binary anymore yet from your bootloops it looks like we have to replace it anyhow. Thank for noticing! I've uploaded an updated dalvik patch, please try it now.
Click to expand...
Click to collapse
now it's working , my apps is upgrading now
it's boring (289 apps .... :| )
Another bootloop in Stock 4.4.
And if like me, you didn't make a whole system backup, I've attached the original files.
i have no bootloop flashed both files, after install, i did wipe cache and dalvik cache. But previously i already did patch motoX_4.4_qcoptimized.zip from kszaq posted at Nexus 4 Benchmark thread. I have Stock ROM + Kernel.
i see you change the dalvik file( "4.4_qc-optimized_dalvik.zip") !
i'm testing your new file .
meangreenie said:
Yep, good to have a dedicated thread.
I did notice a slight change, with there being no more dexopt file, just checking that this is correct?
Click to expand...
Click to collapse
max4wdc said:
i got bootloop !
with 4.4 stock.
Click to expand...
Click to collapse
I tested the patches on my custom ROM and it seemed to me that I didn't need to replace dexopt binary anymore yet from your bootloops it looks like we have to replace it anyhow. Thank for noticing! I've uploaded an updated dalvik patch, please try it now.
LudicrousPeed said:
In the benchmarks thread, I saw a comment that it probably won't work on CyanogenMod ROMs. Is that true?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
It works for me on CyanogenMod. I figured out that the reason for it not having worked before was that CyanogenMod uses a modified installd binary (they patched it for Dexroot on Cache). As this is the only change they made I included stock installd binary (from stock Nexus 4 ROM) to make dalvik patch work with CM and any ROM that uses their base.
kszaq said:
I tested the patches on my custom ROM and it seemed to me that I didn't need to replace dexopt binary anymore yet from your bootloops it looks like we have to replace it anyhow. Thank for noticing! I've uploaded an updated dalvik patch, please try it now.
It works for me on CyanogenMod. I figured out that the reason for it not having worked before was that CyanogenMod uses a modified installd binary (they patched it for Dexroot on Cache). As this is the only change they made I included stock installd binary (from stock Nexus 4 ROM) to make dalvik patch work with CM and any ROM that uses their base.
Click to expand...
Click to collapse
now work on 4.4 stock .:good:
Working for me on Stock 4.4 with Franco's 194 nightly kernel
Just wanted to say thank you! For this.
Doubled benchmark performance, which I don't care about but makes a lot of apps faster.
Very interesting stuff, I never knew the other devices had Qualcomm optimized bionic and dalvik libraries.
Working perfectly fine on stock KRT16S on Nexus 7 (2013)
Thanks again!
PS. I was interested in why initially you said this would only work on deodexd ROMs? Almost all production shipped firmware's are odex, are they not? Or is the MotoX a deodexd ROM/firmware?
Just curious.
Sent from my Nexus 7 using Tapatalk 4
Not sure if you have already have, but may want to git pull Linaro bionic
http://android.git.linaro.org/gitwe...it;a=shortlog;h=refs/heads/linaro_android_4.4
It merges cleanly, so no big deal.
Thanks made Dalvic quicker. Added 10 to antutu but phone was not set up for testing. Seems snappier which begs the question why is this not in official builds? Insane
Sent from my Nokia 3210
Deleted
howard bamber said:
Thanks made Dalvic quicker. Added 10 to antutu but phone was not set up for testing. Seems snappier which begs the question why is this not in official builds? Insane
Sent from my Nokia 3210
Click to expand...
Click to collapse
Qualcomm won't open source their libqc-dalvik optimizations and Google won't use a proprietary dalvik as dalvik is such a core part of Android. The goal of the AOSP is to keep as much open source as they can, sometimes at the cost of proprietary optimization.
Using the old zip from the benchmark thread, my atuntu jumped to 20000. With the 2 new zips I'm back to 17000. Tried the old zip again and back up to 20000. Any ideas why?
Sent from my Nexus 4 using xda app-developers app
I've tried both patches above on my Nexus 4 with Brainmaster's KRT16S ROM and Semaphore 1.8.0 kernel, after applied both patch I'm wiped the dalvik cache too, but my N4 cannot boot into OS, it just bootlooped to CWM recovery again and again.
Working well on stock. If you have issues and you're odexed, wipe cache and dalvik.
motherninja said:
I've tried both patches above on my Nexus 4 with Brainmaster's KRT16S ROM and Semaphore 1.8.0 kernel, after applied both patch I'm wiped the dalvik cache too, but my N4 cannot boot into OS, it just bootlooped to CWM recovery again and again.
Click to expand...
Click to collapse
Have you re-downloaded the dalvik patch after I re-uploaded it yesterday? The first version missed dexopt binary and it caused bootloops.
purpse said:
Using the old zip from the benchmark thread, my atuntu jumped to 20000. With the 2 new zips I'm back to 17000. Tried the old zip again and back up to 20000. Any ideas why?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
What is your Dalvik score in AnTuTu? If it's about 1800, then the patch it working as it should and the lower score may be due the thermal throttling.
Related
THIS ROM IS A WORK IN PROGRESS. JUST ENLISTING TESTERS AT THE MOMENT.
I wanted to get a solid CWM flashable base ROM together. We shouldn't be entirely dependent on the Ouya updates and Ouya stock recovery.
As the name implies, the goal of this ROM is to provide a solid base that others may build/cook on top of. This ROM isn't supposed to have all the bells and whistles of a Cyanogenmod.
I simply used the stock Ouya ROM from the latest OTA (264) and changed a few things.
Changes:
-added superuser
-added busbox
-added terminal emulator
-changed install_recovery.sh to prevent stock recovery overwrite on boot
-removed recovery-from-boot.p
-changed ro.update_url in build.prop to attempt to disable OTA updates
Bugs so far:
-OTA updates have not been all the way disabled
-superuser and busybox need to be re-implemented properly into the updater-script
Instructions:
-You need CWM Recovery installed to flash this
-Do a backup in CWM before flashing (seriously, you'll have something to go back to if things go awry)
-Wipe cache
-Wipe dalvik cache
-Data wipe is optional (this is alpha, doing the wipe causes an annoying update loop)
Again, this ROM is in testing. It should be considered alpha state. Don't flash it if you are afraid to break something. I'm looking to make it better/more stable through testing.
http://invisiblek.org/ouya/ChickenStock264.zip
(Thanks to invisiblek for the hosting)
Awesome dude
mybook4 said:
THIS ROM IS A WORK IN PROGRESS. JUST ENLISTING TESTERS AT THE MOMENT.
I wanted to get a solid CWM flashable base ROM together. We shouldn't be entirely dependent on the Ouya updates and Ouya stock recovery.
As the name implies, the goal of this ROM is to provide a solid base that others may build/cook on top of. This ROM isn't supposed to have all the bells and whistles of a Cyanogenmod.
I simply used the stock Ouya ROM from the latest OTA (264) and changed a few things.
Changes:
-added superuser
-added busbox
-added terminal emulator
-changed install_recovery.sh to prevent stock recovery overwrite on boot
-removed recovery-from-boot.p
-changed ro.update_url in build.prop to attempt to disable OTA updates
Bugs so far:
-OTA updates have not been all the way disabled
-superuser and busybox need to be re-implemented properly into the updater-script
Instructions:
-You need CWM Recovery installed to flash this
-Do a backup in CWM before flashing
-Wipe cache
-Wipe dalvik cache
-DON'T wipe data (I'm not sure what we'll lose yet by wiping data and all we have are OTA updates to work from)
Again, this ROM is in testing. It should be considered alpha state. Don't flash it if you are afraid to break something. I'm looking to make it better/more stable through testing.
https://dl.dropboxusercontent.com/u/56104625/ChickenStock264.zip
Click to expand...
Click to collapse
Good job dude i give try and report
And the time has come! Thank you sir
So I just did an install wiping data, cache, and dalvik. There are definitely bugs to be worked out. The Ouya launcher constantly tries to get an update (verified in data usage in settings). Reboots take me to CWM recovery (where I choose not to run the update). When I boot back into Android the same thing happens. Anyone have an idea about how to disable updates but keep the Ouya launcher? I tried editing the build.prop (see OP), but that didn't seem to work.
They are using a modified version of CMupdater from cyanogenmod source, but I haven't figured out how to disable it yet...
I might need to decompile the Ouyalauncher apk and see if I can find something to disable the updates.
Sent from my SCH-I535 using xda premium
Actually went outside this weekend
Hey reporting had thee most disturbing pleasure of watching After Earth this weekend god help you if you get so unlucky to watch that
But on to better things I installed the rom all was well then started to get random reboots and freeze ups lucky had done a back up but other then that slim quick
Updating to properly install busybox and Superuser.apk.
I'm having some trouble hunting down how to disable the Ouya automatic updates. I deodexed and decompiled the OuyaLauncher.apk and found some references to auto updates, however, I'm unsure what to mess with to prevent updates from occurring.
-Can we prevent the AutoUpdateActivity or AutoUpdateService from being run by the launcher (or replace their behavior with something trivial that does nothing)?
-If we snooped on the ouya's ethernet connection (with tcpdump or wireshark), I wonder if we could see the dns query for the update site. If so, we might be able to simply block by modifying /system/etc/hosts. This wouldn't work if the domain of the updates was the same as the domain of the Ouya store. While an update was downloading, I used netstat to see current connections. I saw two established connections. Did a reverse DNS lookup on the IP addresses and found out they correspond to amazonaws.com. Added "127.0.0.1 amazonaws.com" to the /system/etc/hosts file. The update still started downloading the next time I rebooted. I tried manually going to amazonaws.com in the browser and couldn't connect (as expected). Oh well, it was worth a try.
-Any app developers / smali wizards out there who want to help?
I've included the decompiled OUYALauncher for reference.
Xeore said:
The only question is: What is on that ROM new? It just has the Root-Tools which you know from phone flashing. I don't see any reason for that work.
Click to expand...
Click to collapse
The idea is it's supposed to be a base for other roms to use. Others only have to concentrate on their additional apps and tweaks, not annoying things like preventing updates from annoying the user.
I don't think the OUYA store will work on anything other than a ROM based on stock, so a custom ROM with tweaks and the OUYA store will need to figure this out. I'm personally hoping we get CM 10.1 running, but I also see the value of stock based Roms for the OUYA focused apps from the store.
Sent from my SCH-I535 using xda premium
mybook4 said:
The idea is it's supposed to be a base for other roms to use. Others only have to concentrate on their additional apps and tweaks, not annoying things like preventing updates from annoying the user.
I don't think the OUYA store will work on anything other than a ROM based on stock, so a custom ROM with tweaks and the OUYA store will need to figure this out. I'm personally hoping we get CM 10.1 running, but I also see the value of stock based Roms for the OUYA focused apps from the store.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
And I've had phenomenally bad experiences trying to get apps NOT ported to the Ouya working. Real Racer 3 looks gorgeous... But you can't navigate the menus without a touch screen, for example. There's no controller support. If I could figure out which controller button corresponded to a mouse click...
Xeore said:
Since android 4.0.4 , gamez apps should have gamepad support. GTA 3 runs really smooth at OUYA.. I am the only one who got a heavy input lag from controller?
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
I can't get GTA 3 to download the additional files as of yet, myself.
Edited myself for being Off Topic
dibblebill said:
I can't get GTA 3 to download the additional files as of yet, myself.
Click to expand...
Click to collapse
what version of gta 3 did you install? i tried the latest version 1.4 and got the can't download error when i open it. So i tried version 1.3 and it downloaded fine. Runs great on the ouya!
toyosup88 said:
what version of gta 3 did you install? i tried the latest version 1.4 and got the can't download error when i open it. So i tried version 1.3 and it downloaded fine. Runs great on the ouya!
Click to expand...
Click to collapse
I'll try to track down a copy of 1.3 if I cannot convince 1.4 to function.
Sent from my Nexus 10 using XDA Premium HD app
From bongostl's Carbon builds:
Rules of the thread :
1. Be nice!
2. Be helpful!
3. No egos!
4. Someone asks a question that has already been asked a dozen times and you want to tell the n00b to go search? See rules 1+2(+3)!
Enjoy!
To be clear: I deserve ZERO credit in this. ALL I am doing is sharing my nightly builds that I make on my own.
I will make them occasionally for those crack-flashers out there who would like a nightly build on days when the official Carbon build fails for some reason.
ALL credit goes to the fantastic Carbon team and the work that they do.
I recommend Banks Gapps STANDARD.
I use TWRP. I recommend you do the same
(Actually, I use TWRP-MultiRom. It's awesome. Check it out.)
If you're interested in what has changed, I recommend looking at these
http://review.carbon-rom.com/#/q/sta...+branch:kk,n,z
http://review.cyanogenmod.org/#/q/st...ch:cm-11.0,n,z
If you want to build on your own:
Do this: http://wiki.cyanogenmod.org/w/Build_for_mako
and replace this line: repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0 with this line:
repo init -u git://github.com/CarbonDev/android -b kk
(ps--I take no responsibility if you brick your phone, yada yada yada)
Click to expand...
Click to collapse
Hey all, I just wanted to share my personal nightly build(s) of Carbon with the Halfbreed color from the KRT16S kernel found here. I take no responsibility for the builds and all credit goes to the individual builders of Carbon as well as the kernel used.
Bugs: Theme manager crashes, you tell me
Download
MD5: f87147ae96e986b05fca4810f9cf7c8e
So this build have all latest merged thing on official carbon?
Sent from my Nexus 4 using Tapatalk
xxxMADxxx said:
So this build have all latest merged thing on official carbon?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Yes, the rom's only modification as of now is the halfbreed color calibration, everything else comes directly from the upstream official carbon git.
andersensam said:
If you're interested in what has changed, I recommend looking at these
http://review.carbon-rom.com/#/q/sta...+branch:kk,n,z
http://review.cyanogenmod.org/#/q/st...ch:cm-11.0,n,z
Click to expand...
Click to collapse
Those links don't work, they got truncated. In the original thread they do work.
http://review.carbon-rom.com/#/q/status:open+branch:kk,n,z
http://review.cyanogenmod.org/#/q/status:open+branch:cm-11.0,n,z
ROM is not booting, phone stays at Google logo. Do I have to use the old (4.3) radio with this rom?
hunfatal said:
ROM is not booting, phone stays at Google logo. Do I have to use the old (4.3) radio with this rom?
Click to expand...
Click to collapse
I reflashed the ROM yesterday and found that the installer does not seem to wipe the system partition correctly (or at all, need to look more into this). Try wiping the system, data, and cache manually in CWM or other recovery before flashing. I am currently using the radio from 4.3 but I'm not sure if it has any effect on booting. If the system still doesn't boot, please post your logcat here.
andersensam said:
I reflashed the ROM yesterday and found that the installer does not seem to wipe the system partition correctly (or at all, need to look more into this). Try wiping the system, data, and cache manually in CWM or other recovery before flashing. I am currently using the radio from 4.3 but I'm not sure if it has any effect on booting. If the system still doesn't boot, please post your logcat here.
Click to expand...
Click to collapse
As far as I remember I've tried with full wipe, but will try again tonight later.
andersensam said:
I reflashed the ROM yesterday and found that the installer does not seem to wipe the system partition correctly (or at all, need to look more into this). Try wiping the system, data, and cache manually in CWM or other recovery before flashing. I am currently using the radio from 4.3 but I'm not sure if it has any effect on booting. If the system still doesn't boot, please post your logcat here.
Click to expand...
Click to collapse
I tried using the new radio from 4.4 and it caused a hang on the Google logo, once I changed the radio to the 33-84 hybrid it booted past the Google logo. In case that helps anyone.
tigertechmi said:
I tried using the new radio from 4.4 and it caused a hang on the Google logo, once I changed the radio to the 33-84 hybrid it booted past the Google logo. In case that helps anyone.
Click to expand...
Click to collapse
I have the new radio, then that's definitely the issue, thanks for the info.
Could you tell me how many customization available in the rom? Does the nav bar and the quick settings working? Or in it's current state it's more like a clean AOSP with very little modifications?
hunfatal said:
I have the new radio, then that's definitely the issue, thanks for the info.
Could you tell me how many customization available in the rom? Does the nav bar and the quick settings working? Or in it's current state it's more like a clean AOSP with very little modifications?
Click to expand...
Click to collapse
It's more like AOSP as of now, obviously as the people upstream add more customizations they'll be present in the uploads here. I did double check my modem and it's the .33/84 hybrid. I ran a full wipe and flashed again just to be sure and it seems to be working fine.
Earlier, I have been compiling several ROMs for the galaxy tab (P7510/p4wifi) based on KitKat 4.4. I now decided to move over to OMNI ROM as base: http://omnirom.org/
The nice thing of OMNI in my personal opinion is smoothness: it is relatively low in features, but at the same time it is not that resource hungry as some other ROMs. The end result is a smooth ROM.
Changelog of 15-Feb-2014
-Omni codebase of 14-Jan
Several small fixes, nothing spectecular
It features the Infamous kernel (same kernel as for JB4.3, without SELinux). The zram code has been optimized (based on google advice for low-RAM devices) and is enabled by default.
To see the additions on top of Omni, check github (additional patches are always shown on top):
Frameworks
Settings
OmniGears
First installation:
-Boot into recovery
-Factory reset
-Wipe system partition
-Install ROM
-Boot tablet (there sometimes are bootloops if gapps is flashed directly on top of the ROM without first booting the ROM)
-Reboot recovery
-Install SuperSU: http://download.chainfire.eu/371/SuperSU/UPDATE-SuperSU-v1.85.zip
-Install gapps (you should use a package specifically for KK4.4 and with the old-fashioned updater-script! - don't worry if you install an outdated gapps packages with the correct updater-script, as long as it is for KK4.4 the apps in the gapps package will be automatically updated -> only small gapps packages fit, e.g. banks core of pa 0-day gapps mini)
-Boot it up
-> some people report issues (e.g. bootloop or crashing gapps) if they flash ROM, gapps & supersu in a row after fully wiping the tablet. In that case, wipe again, flash ROM, boot the tab, reboot to recovery, and then flash the rest.
-> if coming from stock ROM, a factory reset may wipe you entire /data partition, so you loose you sdcard contents as well (I think this only happens with CWM, but I'm not sure)
-> in CWM "wipe system partition" can be found under mounts, and is called "format /system"
->If you get the message 'This package is for "p4" devices this is a "GT-P7500"' (or something likewise) update to a recent CWM or TWRP
Update installation (OMNI -> OMNI):
-Boot into recovery
-Install ROM
-Install SuperSU (in the SuperUser app you can create a script that will automatically backup/restore SuperSU on ROM updates so you don't have to reflash SuperSU).
-Boot it up
You can download any gapps packages for kitkat that you like, but one that many have used successfullyis PA 0 day gapps:
http://forum.xda-developers.com/showthread.php?t=2397942
Downloads:
P4WIFI:
http://rootaxbox.no-ip.org/kasper_h/roms/p4wifi/omni44/
P4:
http://rootaxbox.no-ip.org/kasper_h/roms/p4/omni44/
Credits:
OMNI team for the code
AAccount for his help along the way to get KK4.4 to compile for our aging device!
pershoot for the basis for the device trees & kernel base
Code:
Basis of OMNI code: https://github.com/omnirom/
Common p4 device tree: https://github.com/kasperhettinga/android_device_samsung_p4-common
Device tree p4wifi: https://github.com/kasperhettinga/android_device_samsung_p4wifi
Vendor blobs p4wifi: https://github.com/kasperhettinga/android_vendor_samsung_p4wifi
Device tree p4wifi: https://github.com/kasperhettinga/android_device_samsung_p4
Vendor blobs p4wifi: https://github.com/kasperhettinga/android_vendor_samsung_p4
What does NOT work?
-There are graphical glitches. Although they mainly have been solved there seem to be some remaining issues with hwcomposer that may crash the tab.
-Bluetooth audio does not work (other Bluetooth functions do work).
-HDMI output (may be fixed according to some posts, didn't test myself yet)
-HD movies (in e.g. youtube) may stutter
Smoothness advice:
Go to performance settings:
-Overclock CPU to 1400MHz (Do this at your own risk!)
-Set IO scheduler to CFQ
-Keep governor on Interactive
Go to developer settings:
-Set the three animation scale options to 0.5x
-Activate "Force GPU rendering"
-Active "Disble HW-overlays"
-Set background process limit to 4 processes
(if performance/developer options are not yet shown, go to settings>about and press build number 7 times)
-> Thanks to all forum members contributing to this list
-> Do it at your own risk!
-> Don't complain about limited battery life (ROW+interactive+1000MHz leads to better battery life for sure)
Some other tips:
-For improvement of sound quality, you can use Viper4Android
-For more volume only, SpeakerBoost is earier to use
-For netflix, head over here: http://forum.xda-developers.com/showpost.php?p=49208063&postcount=445
-To be able to use Flash player, use a browser that doesn't use the kitkat browser engine (e.g. firefox can be used). Download flash player from adobe website (thanks to AAccount for finding out!).
- If you can't see your internal SD on PC: Go to Settings -> Storage -> 3 dot menu -> tick MTP.
-To use the multi-window feature, go to the recent apps screen, press&hold an app, and select put aside.
Great......downloading now
Sent from my GT-N7000 using Tapatalk
p4
is there any p4 version in progress br zezam?
Nice work :good:
you will get version and for the P7500 ?
kasper_h said:
Reserved
Click to expand...
Click to collapse
i'm new to Galaxy tab 10.1..LOL,,, can this ROM be installed directly from Stock ROM with TWRP,,,Please help ASAP
zezam67 said:
is there any p4 version in progress br zezam?
Click to expand...
Click to collapse
paiktaras said:
Nice work :good:
you will get version and for the P7500 ?
Click to expand...
Click to collapse
Kasper already said that he won't be building for the p4.
Looks like my P7500 is gonna be a P7510 soon..
BTW, we still need to flash supersu zip?
Sent from my GT-P7500 using Tapatalk HD
Xenodrome_ said:
i'm new to Galaxy tab 10.1..LOL,,, can this ROM be installed directly from Stock ROM with TWRP,,,Please help ASAP
Click to expand...
Click to collapse
Just wipe everything and flash the ROM.
eushaun99 said:
Kasper already said that he won't be building for the p4.
Looks like my P7500 is gonna be a P7510 soon..
BTW, we still need to flash supersu zip?
Sent from my GT-P7500 using Tapatalk HD
Click to expand...
Click to collapse
You need to separately flash SuperSU. SuperSU can create a script for backing it up, so that on future ROM flashes you don't have to repeat this.
oooppppsss the ROM can not be installed in a P4
Hi,
I have tried to install the ROM in a P4 and I receive an error saying "this device is a P4 and the ROM can not be installed"
esfjrg1 said:
Hi,
I have tried to install the ROM in a P4 and I receive an error saying "this device is a P4 and the ROM can not be installed"
Click to expand...
Click to collapse
Doh, its a p4wifi ROM. If you don't use 3g, flash a p4wofi recovery first, reboot, and flash again.
Sent from my GT-P7500 using Tapatalk HD
esfjrg1 said:
Hi,
I have tried to install the ROM in a P4 and I receive an error saying "this device is a P4 and the ROM can not be installed"
Click to expand...
Click to collapse
Flash P4wifi recovery, Then flash this ZIP again
Bad to see that it is really not for the GT-P7500 . So i will not update.... i really need my 3G
Why it is so difficult to get 3G working Did 4.4 change so much?
Traace said:
Flash P4wifi recovery, Then flash this ZIP again
Bad to see that it is really not for the GT-P7500 . So i will not update.... i really need my 3G
Why it is so difficult to get 3G working Did 4.4 change so much?
Click to expand...
Click to collapse
The problem is that in 4.4 the radio stuff has been redone. I also had problem with another device I develop for (SGS) to get the radio to work. And to develop a ROM for a device I don't own make it even more complicated. In the past weeks I sometimes flashed 10-15 testbuilds on a single day to try and fix something simple (like USB OTG). If someone else would test something for me, the progress would be way too slow.
But all my code is open source: someone with a p7500 can just grab all the code, adapt it to p7500 and compile it. And start the whole process of fixing bugs
I get a unfortunately, setup wizard has stopped error and can not pass it.. Anything to work around it?
Sent from my SPH-L720 using xda app-developers app
@kasper_h As you might awared, YouTube is broken. It ran the same problem at that time with my GT-N7000 with OMNI 4.4, they managed to fix it. Maybe you can check with herna on that thread.
So far so good running ART
Sent from my GT-N7000 using Tapatalk
I also get the com.google.process.location has stopped error but I can pass that one..
Sent from my SPH-L720 using xda app-developers app
kasper_h said:
First installation:
-Install gapps (you can download any gapps package you like, as long as it is specifically for JB4.3!)
Click to expand...
Click to collapse
Is there a difference between 4.3/4.4 gapps?
Sent from my myTouch 4G using Tapatalk
Chris4809 said:
I get a unfortunately, setup wizard has stopped error and can not pass it.. Anything to work around it?
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Which gapps package? I flashed ROM & gapps myself today as well, just to test it once more. And it works flawlessly.
rogconnect said:
@kasper_h As you might awared, YouTube is broken. It ran the same problem at that time with my GT-N7000 with OMNI 4.4, they managed to fix it. Maybe you can check with herna on that thread.
So far so good running ART
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Youtube is a problem with some hardware blobs I believe. I had the same on AOKP. I have spend a lot of time, but could never solve it. I decided to ignore it
Chris4809 said:
I also get the com.google.process.location has stopped error but I can pass that one..
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
jaibar said:
Is there a difference between 4.3/4.4 gapps?
Sent from my myTouch 4G using Tapatalk
Click to expand...
Click to collapse
Yes, you should only use kitkat (4.4) gapps!
kasper_h said:
Which gapps package? I flashed ROM & gapps myself today as well, just to test it once more. And it works flawlessly.
Youtube is a problem with some hardware blobs I believe. I had the same on AOKP. I have spend a lot of time, but could never solve it. I decided to ignore it
Yes, you should only use kitkat (4.4) gapps!
Click to expand...
Click to collapse
If it is 4.4 gapps you might want update the OP.. It is telling us that we should use 3.4
Sent from my SPH-L720 using xda app-developers app
After enabled ART on first boot then rebooted. And then rebooted to recovery to install Banks 12-14_GApps_Core_4.4.2_signed.zip.. then I can signed in Google...so far no FC on Google apps.
Sent from my GT-P7510 using Tapatalk
I'm getting the "setup wizard has stopped" error also.
Coming from pac_P4wifi_4.3-Infamous_20131114
Followed install instructions.
Used gapps-jb-20130813-signed
Cannot find gapps for 4.4. The 20130813 (4.3) package seems to be the most current.
Full Advance 4.4.2
Samsung Galaxy S (Vibrant)
Full Advance is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. Full Advance does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on unofficial builds is the leading
* cause of male impotence.
*/
Steps to install
Coming from 4.4 or less ROMS
Download Full Advance-XXXXXXXX.zip to your phone
Boot into Recovery
Wipe all your data (System/Data/Dalvik Cache)
Flash Full Advance-XXXXXXXX.zip from your phone
(Optional)Flash Gapps.zip from your phone
Reboot
Features:
Highly optimised ROM
Stable
Smallest ever 135mb rom
New Battery tweaks
New speedup tweaks
complete AOSP
Downloads:
Rom
Gapps
Version Information
Status: Stable
Current Stable Version: Full Advance 4.4.2-2
Stable Release Date: 2015-12-19
Credits:
All credits will goes to Althafvly who allow me to do port his rom.
Original Thread
Here
Note
Dont go for any new open gapps getting errors
If u want more fluid and ram try Neat kernel
Sreenshots
Awesome ROM!! I was gonna skip KK after losing IMEI/APN/BASEBAND in various KK ROM's, but this one's been rock solid. Very stable. LP's notifications UI is great, but the eventual lag kinda spoils it. So, it's nice to have a solid KK ROM to use as a DD fallback. Not being forced to use MTP is a nice bonus. UMS is so much faster & more convenient, imo.
Could you provide a flashable Kernel only .zip (for the kernel used in your rom)?
I've been testing kernels and wanted to cleanly revert back to your default kernel whenever necessary. NeatKernel v1.11 (20140724) yields an impressive 417 MB RAM, but it obviously breaks 720p video playback. Surprisingly, I can still record video (just can't play it back). lyahmanKernel 20150722 (with Bigmem on) simply crashes when taking video. I used Semaphore KK v3.4.3 (20140315) zip contents and replaced the boot.img with yours, but I wasn't exactly sure if the META-INF (updater-script) was cleanly compatible for this ROM. After going back & forth between various kernels, it seems to be ok. Just wanted an "official" kernel zip to use just in case.
Is Stagefright patched in this ROM? IIRC, Coldwindofnowhere's OmniROM 5.1.1 (20151202) is the only recent ROM I've seen that indicates the Android Security Patch Level in settings.
Also, can Halo be completely removed or disabled? The novelty wears off after a while. I have it turned off but keep accidentally hitting the toggle in the notifications pulldown. Just wanted to remove that toggle somehow. Didn't notice anything in settings Halo section. Or, can it be frozen in TB? I'm assuming it's bundled with other system settings.
ninbang said:
Awesome ROM!! I was gonna skip KK after losing IMEI/APN/BASEBAND in various KK ROM's, but this one's been rock solid. Very stable. LP's notifications UI is great, but the eventual lag kinda spoils it. So, it's nice to have a solid KK ROM to use as a DD fallback. Not being forced to use MTP is a nice bonus. UMS is so much faster & more convenient, imo.
Could you provide a flashable Kernel only .zip (for the kernel used in your rom)?
I've been testing kernels and wanted to cleanly revert back to your default kernel whenever necessary. NeatKernel v1.11 (20140724) yields an impressive 417 MB RAM, but it obviously breaks 720p video playback. Surprisingly, I can still record video (just can't play it back). lyahmanKernel 20150722 (with Bigmem on) simply crashes when taking video. I used Semaphore KK v3.4.3 (20140315) zip contents and replaced the boot.img with yours, but I wasn't exactly sure if the META-INF (updater-script) was cleanly compatible for this ROM. After going back & forth between various kernels, it seems to be ok. Just wanted an "official" kernel zip to use just in case.
Is Stagefright patched in this ROM? IIRC, Coldwindofnowhere's OmniROM 5.1.1 (20151202) is the only recent ROM I've seen that indicates the Android Security Patch Level in settings.
Also, can Halo be completely removed or disabled? The novelty wears off after a while. I have it turned off but keep accidentally hitting the toggle in the notifications pulldown. Just wanted to remove that toggle somehow. Didn't notice anything in settings Halo section. Or, can it be frozen in TB? I'm assuming it's bundled with other system settings.
Click to expand...
Click to collapse
if u need kernel means extract zip and boot.img is the kernel u want
Hey. Replace the stock libs. You can play 720p videos
---------- Post added at 12:32 PM ---------- Previous post was at 12:32 PM ----------
The libs are modified for the best. It almost work in all
ninbang said:
Awesome ROM!! I was gonna skip KK after losing IMEI/APN/BASEBAND in various KK ROM's, but this one's been rock solid. Very stable. LP's notifications UI is great, but the eventual lag kinda spoils it. So, it's nice to have a solid KK ROM to use as a DD fallback. Not being forced to use MTP is a nice bonus. UMS is so much faster & more convenient, imo.
Could you provide a flashable Kernel only .zip (for the kernel used in your rom)?
I've been testing kernels and wanted to cleanly revert back to your default kernel whenever necessary. NeatKernel v1.11 (20140724) yields an impressive 417 MB RAM, but it obviously breaks 720p video playback. Surprisingly, I can still record video (just can't play it back). lyahmanKernel 20150722 (with Bigmem on) simply crashes when taking video. I used Semaphore KK v3.4.3 (20140315) zip contents and replaced the boot.img with yours, but I wasn't exactly sure if the META-INF (updater-script) was cleanly compatible for this ROM. After going back & forth between various kernels, it seems to be ok. Just wanted an "official" kernel zip to use just in case.
Is Stagefright patched in this ROM? IIRC, Coldwindofnowhere's OmniROM 5.1.1 (20151202) is the only recent ROM I've seen that indicates the Android Security Patch Level in settings.
Also, can Halo be completely removed or disabled? The novelty wears off after a while. I have it turned off but keep accidentally hitting the toggle in the notifications pulldown. Just wanted to remove that toggle somehow. Didn't notice anything in settings Halo section. Or, can it be frozen in TB? I'm assuming it's bundled with other system settings.
Click to expand...
Click to collapse
If you want Stagefright patched 4.4.2 rom i guess @althafvly will need to cherry-pick some commits from cm12.1 (see on cm gerrit ... i think it's possible to do so, even if i'm pretty sure you will get some conflicts) .
Audiracecar90 said:
if u need kernel means extract zip and boot.img is the kernel u want
Click to expand...
Click to collapse
Which META-INF - updater-script file should I use? I just used Semaphore KK v3.4.3's updater-script, and it seemed to be ok. Just wanted to see what you recommended.
althafvly said:
Hey. Replace the stock libs. You can play 720p videos
The libs are modified for the best. It almost work in all
Click to expand...
Click to collapse
Any particular libs to target for replacement? What libs would I replace them with? Or, can you point me to the discussion thread to read about this?
Coldwindofnowhere said:
If you want Stagefright patched 4.4.2 rom i guess @althafvly will need to cherry-pick some commits from cm12.1 (see on cm gerrit ... i think it's possible to do so, even if i'm pretty sure you will get some conflicts) .
Click to expand...
Click to collapse
I was hoping Stagefright would get patched in currently released builds. I like how your omni-5.1.1-20151202 build included the 2015-11-01 Android Security Patch. I just kept losing IMEI/APN/BB after flashing SuperSU-4.26.zip. That was a freaky fast rom (@ 1200 OC), but I just couldn't get past the IMEI issue.
720p video libs .not flashable zip
https://www.androidfilehost.com/?fid=24341993505161661
Audiracecar90 said:
Status: Stable
Current Stable Version: Full Advance 4.4.2-2
Stable Release Date: 2015-12-19
Click to expand...
Click to collapse
@Audiracecar90 - The kernel file in the zip is named boot.img.img. Since the updater-script references boot.img, maybe this was a typo? Was wondering why when I flashed this rom, the kernel would not change. Anyways, just an observation. Thanks again for this great KK rom.
ninbang said:
@Audiracecar90 - The kernel file in the zip is named boot.img.img. Since the updater-script references boot.img, maybe this was a typo? Was wondering why when I flashed this rom, the kernel would not change. Anyways, just an observation. Thanks again for this great KK rom.
Click to expand...
Click to collapse
Ya boot.img is kernel mate but i cant understand what you are saying!
Audiracecar90 said:
Ya boot.img is kernel mate but i cant understand what you are saying!
Click to expand...
Click to collapse
If you open up the rom .zip, the actual name of the kernel file = "boot.img.img"
Is that extra ".img" supposed to be in the name?
ninbang said:
If you open up the rom .zip, the actual name of the kernel file = "boot.img.img"
Is that extra ".img" supposed to be in the name?
Click to expand...
Click to collapse
Yes normally its name is boot.img
Audiracecar90 said:
Yes normally its name is boot.img
Click to expand...
Click to collapse
I think that @ninbang wanted to point out that there is a typo in the boot.img filename so it wont flash. See the screenshot.
Coldwindofnowhere said:
I think that @ninbang wanted to point out that there is a typo in the boot.img filename so it wont flash. See the screenshot.
Click to expand...
Click to collapse
Oh ya thanks bro
ninbang said:
If you open up the rom .zip, the actual name of the kernel file = "boot.img.img"
Is that extra ".img" supposed to be in the name?
Click to expand...
Click to collapse
As Coldwindofnowhere said if u want full advance kernel alone take boot.img.img and rename as boot.img
By popular requests, I present you Andromeda Series of custom roms by TURBO. Flash at you own risk. This rom is for the people that wanted just the strimmed line H811 20i MM core rom...... No fancy stuff here.
This project started by de-bloating the stock rom, later on it moved to optimizing the system and later tweaking it to the max......
The base rom will include the play store and some core stock apps, but that's it.....
Tweaks and customizations goes on you. So, feel free to customize it to your liking.
It features:
- All cpu core frequencies have been optimized to my specs, not the manufacturer.....
- Gpu frequency over clocked to 450mhz
- Sound subsystem it's been optimized to my specs, not the manufacturer...
- Super de-bloated.
- Rooted
- Network optimizations.
- H811 20i MM based
- De-bloated
- System cleaner script
- Blue tooth and Camera optimized for best quality
- Clean root file system
Instructions:
- Just flash rom from recovery. Remember to wipe all but external sd card prior flashing any rom.
Stock Kernel:
http://downloads.codefi.re/autoprime/LG/LG_G4/H811/H81120i/LG-H81120i-Flashable.COMPLETE.zip
SUPERXE Custom Kernel:
source: LINK
Base:
http://downloads.codefi.re/autoprime/LG/LG_G4/H811/H81120i/LG-H81120i-Flashable.COMPLETE.zip
Thanks to:
- autoprime, LINK
- #TEAMCODEFIRE
- ViPER520, for his excellent dsp Viper4Android. ViPER’s Audio Website
- cile381 for providing our new custom kernel. LINK
- metaspook, for providing ViPER4Android MK-Mod, http://forum.xda-developers.com/android/software-hacking/mod-viper4android-mk-mod-t3300821
- Linus Torvalds (https://en.wikipedia.org/wiki/Linus_Torvalds)
Special Note:
- To devs: If you find any of your work inside my rom, please pm me. I would gladly add you to the OP.
Screeshots:
Installed apps:
Optimized CPU freqs:
Temps:
Enjoy,
TURBO
Download Links:
ROM:: LINK
Thank you for bringing back your development. Good job.
Hey so we need to install gapps on stock ROM? Haven't came across that before that why I'm asking
bbell101584 said:
Hey so we need to install gapps on stock ROM? Haven't came across that before that why I'm asking
Click to expand...
Click to collapse
Negative. Just clean install , proceed with rom installation and reboot. No gapps needed. You will be able to install apps from Playstore. I had a typo, but I corrected it already.
TURBO
ElfinJNoty said:
Thank you for bringing back your development. Good job.
Click to expand...
Click to collapse
My pleasure. I am trying...... Lol.....
TURBO
Dude, I was going to ask you in the other tread about stock development, but you read my mind, awesome I just came back from work, I will flash this. BTW the cm build you did yesterday it runs very smooth all day no problem listening music at work. You are the best bro... Turbo the master is back!!!!!!!!!!!!!!!!!!!!!!
Androidblood said:
Dude, I was going to ask you in the other tread about stock development, but you read my mind, awesome I just came back from work, I will flash this. BTW the cm build you did yesterday it runs very smooth all day no problem listening music at work. You are the best bro... Turbo the master is back!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Glad my rom was part of your day!!!. Thank you and enjoy my next generation of roms......
TURBO
He's back!!
Sent from my LG-H811 using Tapatalk
HNIC702 said:
He's back!!
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Yes, sir. In cold blood...... Glad to hear from you....
TURBO
Yes! I'm so glad this is back, you were making so much progress before! Are you still trying to find unneeded services and things to remove?
Icanthelplt90 said:
Yes! I'm so glad this is back, you were making so much progress before! Are you still trying to find unneeded services and things to remove?
Click to expand...
Click to collapse
Lol.... Thank you!!. I am always searching for things to remove..... the quest ends with me.......
TURBO
TURBO2012 said:
Yes, sir. In cold blood...... Glad to hear from you....
TURBO
Click to expand...
Click to collapse
Just flashed this before bed and i am now setting up my replacement device. You're the man!
Sent from my LG-H811 using Tapatalk
HNIC702 said:
Just flashed this before bed and i am now setting up my replacement device. You're the man!
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Thank you, chief.... Glad to hear that.... Have a great rest of the day....
TURBO
Gents, H811 20i-03-30 release is ready.
Now, this particular release has a very simple script that wipes data and cache partitions....
This means that you will lose all previous configurations. So if you don’t want to set up your phone from scratch then please do not flash this rom...
On the other side. This helps avoid a innumerate of issues.......
Advantages:
- Stability
- Speed, after cache and dalvik settle phone feels very responsive.....
- Lag free. Remember first time you turned on your phone?
- Battery life accuracy. Since this script also wipes battery stats, you and the system will get correct battery and system readings...
- Improved scrolling experience.
New on this release:
- D/C cleaner
- Speed tweaks (net, scrolling, power saving, cache opts )
- Direct gpu rendering........ Adreno hardware rendering optimization..
It's up!!
TURBO
Love these readings (see below). Since I am just playing music, the lower frequencies are used the most. Like it should be. No crazy cpu utilization with not so complex tasks.... phone feel so cold.....
TURBO
TURBO2012 said:
Gents, H811 20i-03-30 release is ready.
Now, this particular release has a very simple script that wipes data and cache partitions....
This means that you will lose all previous configurations. So if you don’t want to set up your phone from scratch then please do not flash this rom...
On the other side. This helps avoid a innumerate of issues.......
Advantages:
- Stability
- Speed, after cache and dalvik settle phone feels very responsive.....
- Lag free. Remember first time you turned on your phone?
- Battery life accuracy. Since this script also wipes battery stats, you and the system will get correct battery and system readings...
- Improved scrolling experience.
New on this release:
- D/C cleaner
- Speed tweaks (net, scrolling, power saving, cache opts )
- Direct gpu rendering........ Adreno hardware rendering optimization..
It's up!!
TURBO
Click to expand...
Click to collapse
So do we still need to wipe internal sd and system or the script handles that
bbell101584 said:
So do we still need to wipe internal sd and system or the script handles that
Click to expand...
Click to collapse
That is correct. Is that I did not want to touch the sd card.. Next release script will clean /boot partition also......
TURBO
Does this delete internal storage as well?
TacoTuco said:
Does this delete internal storage as well?
Click to expand...
Click to collapse
Negative.
TURBO
Turbo .. Happy for your return and thank you for your time and commitment to this ROM!