Warning: This ET is very experimental tweaks and I do not recommend for someone are looking for a stable kernel to use this ET and this is only for someone is already running the previous ET... However, new users are welcome to try out to see what the ET does for their tablets.. If you have a problem with the previous ET, please don't try it because I have no idea what is causing the issue...
You can find the stable Hund's kernel without the ET here and developed by Hundsbuah:
http://forum.xda-developers.com/showthread.php?t=2143093
You can find more about Cromi X here and developed by sbdags:
http://forum.xda-developers.com/showthread.php?t=2425383
Note: Most of these tweaks are found on this website and some are on others websites. They are not from me. I found them and tested them on my TF700t and they seem to work... You can test them out and let me know if they are working. If you have some tweaks that work on your device, please let me know so I can add them to the list...Thanks...
The Extreme Tweak is an All in One optimizing package for the internet, ROM, and Kernels. Currently, it is running with Cromi X and Hund's kernel but it may work on other ROMs and kernels as well. So please feel free to chime in and discuss what we can do to push our TF700t to the top notch...:good:
WELCOME all levels of knowledge for ideas and tweaks! :highfive:
Preparations:
1. Disable or Uncheck the "Enable smart backlight adjuster" in the Asus customized settings
2. Make sure that you don't have any other UV/OV tweaks in your init.d folder
For the current ET users:
1. Download this file: "Hund_v3.4.2_ET_V1.4.zip"
2. Backup your system and wipe dalvik and cache before installing the v1.4
3. That is it and if you have a problem installing it, please go to the Possible Fix below for a solution..
For new users:
1. Download this file: "Hund_v3.4.2_ET_V1.4.zip"
2. Backup your system
3. Format your data partition and wipe everything on your internal SD
4. Install Cromi X Rom and select the ET during the installing process
5. Restart your device when it is done
6. Boot back into the recovery and install the ET v1.4
7. If you have a problem, you can see the Possible Fix below for a solution
Possible Fix:
1. Format your data partition and wipe everything on your internal SD except your System
2. Reinstall the ET v1.4
3. It should work from this point. If it is still not working then you have to start the installation all over again.
4. If it is still not working, then you need to restore your back up and forget about the ET...
Please give me a feedback with your experience on the ET, thanks in advance...
Good luck and enjoy...
These tweaks should improve your Wifi speed and load the pages faster...
Hund v3.4.0:
Available TCP Congestion Control: reno and cubic
Hund v3.4.2:
Available TCP Congestion Control: westwood, reno, bic, cubic, highspeed, hybla, htcp, vegas veno, scalable, lp, yeah, and illinois
Change the TCP Congestion Control: /system/xbin/sysctl -w net.ipv4.tcp_congestion_control=cubic
You need to replace the red TCP name with your choice of the other TCP Control name...
1. westwood (Prefer and works best in my area)
2. cubic
3. reno
4. Have not test others yet...
5. (Worst)
Requirements:
You need a working "init.d" folder in order to use these tweaks.
Installation:
1. You need to install the "WiFi-Optimizing v1.0" in your custom recovery. It will create a file in your init.d folder for you. For some reason, you don't like these tweaks. You can use the "remove-WiFi-Optimizing" to remove those tweaks and back to the previous setting that you have.
2. The alternative method is to copy those tweaks below and paste them in one of the files in your init.d folder and save it with a reboot.
### WiFi Tuning and Optimizing
/system/xbin/sysctl -w net.ipv4.tcp_congestion_control=cubic
/system/xbin/sysctl -w net.ipv4.tcp_mem="4000000 4054304 4194304"
/system/xbin/sysctl -w net.ipv4.udp_mem="4000000 4054304 4194304"
/system/xbin/sysctl -w net.core.somaxconn=65536
/system/xbin/sysctl -w net.core.optmem_max=2097152
/system/xbin/sysctl -w net.core.rmem_max=4194304
/system/xbin/sysctl -w net.core.rmem_min=8192
/system/xbin/sysctl -w net.core.rmem_default=131072
/system/xbin/sysctl -w net.core.wmem_max=2097152
/system/xbin/sysctl -w net.core.wmem_min=4096
/system/xbin/sysctl -w net.core.wmem_default=65536
/system/xbin/sysctl -w net.ipv4.tcp_rmem_min=8192
/system/xbin/sysctl -w net.ipv4.tcp_rmem_default=131072
/system/xbin/sysctl -w net.ipv4.tcp_rmem="8192 131072 4194304"
/system/xbin/sysctl -w net.ipv4.tcp_wmem_min=4096
/system/xbin/sysctl -w net.ipv4.tcp_wmem_default=65536
/system/xbin/sysctl -w net.ipv4.tcp_wmem="4096 65536 2097152"
/system/xbin/sysctl -w net.ipv4.udp_rmem_min=8192
/system/xbin/sysctl -w net.ipv4.udp_rmem_default=131072
/system/xbin/sysctl -w net.ipv4.udp_rmem="8192 131072 4194304"
/system/xbin/sysctl -w net.ipv4.udp_wmem_min=4096
/system/xbin/sysctl -w net.ipv4.udp_wmem_default=65536
/system/xbin/sysctl -w net.ipv4.udp_wmem="4096 65536 2097152"
/system/xbin/sysctl -w net.ipv4.tcp_tw_reuse=1
/system/xbin/sysctl -w net.ipv4.tcp_tw_recycle=1
/system/xbin/sysctl -w net.ipv4.route.flush=1
/system/xbin/sysctl -w net.ipv6.route.flush=1
Notes: There are a few more tweaks that could help your wifi speed but you have to implement them in the build.prop. So I will introduce them when I work on the ROM part on post #3....
The kernel is one of the important part of your device because it controls how your device is running and behaving. So it is a good place for users to tweak and change the settings the ways that users want.. I will change my plan and apply these tweaks on _that kernel so I hope that there are more testers to test these tweaks.. This will bring _that on board so we can be all benefit from his knowledge... I am working on these at the moment and will post update soon..
Mounting options: This will be the last explanations because I need more time to dig up information to answer _that questions...
Governors: Update soon..
I/O Schedulers: Update soon..
Reserve for Rom tweaks and explanations
Warning: Please backup your system and personal stuff before installing this zip, just in case you need it. Also, please research or ask what are the advantages and disadvantages before using it...
TF700t users can install the zip below to Enable/Disable their journal on System, Caches, and Data partitions... The Enable Zip file will also add the mounting option for Journal_Data_Writeback which will helps the overall improvement on the slow I/O performance..
For _that's users, you can install the Enable zip file to convert the Journal_Data_Order to Journal_Data_Writeback. I believe that _that's kernel is using the default setting which is Data_Order...
Update:
Oop, I made a wrong statement that it does improve Read/Write.... I/O scheduler does improve r/w speed, not mounting option... Haha, I think that I am buzz a little when I wrote this...
Good luck everyone...:fingers-crossed:
How about if we install an earlier version with sdbag's kernel installer and the add your 1.3? Is that away to avoid wiping /data? Also, i see notes about performance and battery. How about the heat. I'd like to stay under 58c.
Thx
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
awilson77584 said:
How about if we install an earlier version with sdbag's kernel installer and the add your 1.3? Is that away to avoid wiping /data? Also, i see notes about performance and battery. How about the heat. I'd like to stay under 58c.
Thx
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
I always use this command "fsck.ext4 or e2fsck" in the ET which will checks your System partition, Cache partition, and Data partition for a potential or corrupted problems. Especially on your Data partition, those commands will take forever to fix and clean up errors on it...
Also most of the time, if I run those commands with a good backup from the TWRP, I am end up with the issue here and there or even a bootloop.. I think that they are trying to convert the ext4 to ext3 system when it is restored from the backup. I don't have a solid evidence to confirm it...
To answer your question, if your system is not from a backup, then you can follow this method to see if it works for you.
1. Backup your system if you need to restore it
2. Format your data partition and wipe everything on your internal SD. You need to save your personal data some where because you will loose them if you format your data partition..
3. Using the kernel installer to install the ET version on your device so you have the ET build.prop
4. Reboot your device for it to setup and boot back into the TWRP so you can install the ET v1.3
5. Reboot your device again for the new version to setup
6. If everything is working, then you can restore backup for the data only from the TWRP and you should have the same settings and all apps as before.
Otherwise, you have to do a clean installation with a format of your data partition.
Or you can remove these commands from my v1.3 zip file in the updater-script. You can find it here: "/META-INF/com/google/android/updater-script". Then dirty installation...
ui_print("--->Tuning & Optimizing System...");
run_program("/tmp/fsck.ext4", "-Dfyv", "/dev/block/mmcblk0p1");
ui_print("--->Tuning & Optimizing Cache...");
run_program("/tmp/fsck.ext4", "-Dfyv", "/dev/block/mmcblk0p2");
ui_print("--->Tuning & Optimizing Data...");
run_program("/tmp/fsck.ext4", "-Dfyv", "/dev/block/mmcblk0p8");
About the performance and battery:
It is very fast and smooth comparing to the non ET version. At least it is on my device. For the battery, it will consume more battery because all 4 cores are running in a higher frequency to _that's kernel. You can always lower the frequencies to where _that settings then you should expect about the same battery usage..
For the heat issue: it should be depended on the load and frequency settings. For the light load on the balance mode, it should not be that high. However, you can lower your frequencies as describing above then you should not see any heat higher than your previous settings. I hope that I answer most of your questions...
Good luck...:fingers-crossed:
LetMeKnow said:
//snip
Good luck...:fingers-crossed:
Click to expand...
Click to collapse
Thanks!
awilson77584 said:
Thanks!
Click to expand...
Click to collapse
Does it work for you? Please give me feedback if it works and your opinion....:fingers-crossed: I will try to explain all the tweaks in the ET so users have better understanding how things work and how to use them properly...
Thanks..
Thanks for the heads up LMK. Worked well but unfortunately had continued FCs using ondemand governor regardless of IO used though improved performance. Still good work mate. Cheers
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Essentrix said:
Thanks for the heads up LMK. Worked well but unfortunately had continued FCs using ondemand governor regardless of IO used though improved performance. Still good work mate. Cheers
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
Thanks for the feedback. You will not see the performance if you use the Ondemand governor because it is not optimized yet... The ET is only optimized with the Interactive governor for now. Can you please leave it as a default setting for testing? I will try optimize the Ondemand governor for the next release...
Maybe you can help me out with the Ondemand optimization for the next release...
Update: It is totally wrong answer and deleted...
LetMeKnow said:
I always use this command "fsck.ext4 or e2fsck" in the ET which will checks your System partition, Cache partition, and Data partition for a potential or corrupted problems. Especially on your Data partition, those commands will take forever to fix and clean up errors on it...
Also most of the time, if I run those commands with a good backup from the TWRP, I am end up with the issue here and there or even a bootloop.. I think that they are trying to convert the ext4 to ext3 system when it is restored from the backup. I don't have a solid evidence to confirm it...
To answer your question, if your system is not from a backup, then you can follow this method to see if it works for you.
1. Backup your system if you need to restore it
2. Format your data partition and wipe everything on your internal SD. You need to save your personal data some where because you will loose them if you format your data partition..
3. Using the kernel installer to install the ET version on your device so you have the ET build.prop
4. Reboot your device for it to setup and boot back into the TWRP so you can install the ET v1.3
5. Reboot your device again for the new version to setup
6. If everything is working, then you can restore backup for the data only from the TWRP and you should have the same settings and all apps as before.
Otherwise, you have to do a clean installation with a format of your data partition.
Or you can remove these commands from my v1.3 zip file in the updater-script. You can find it here: "/META-INF/com/google/android/updater-script". Then dirty installation...
ui_print("--->Tuning & Optimizing System...");
run_program("/tmp/fsck.ext4", "-Dfyv", "/dev/block/mmcblk0p1");
ui_print("--->Tuning & Optimizing Cache...");
run_program("/tmp/fsck.ext4", "-Dfyv", "/dev/block/mmcblk0p2");
ui_print("--->Tuning & Optimizing Data...");
run_program("/tmp/fsck.ext4", "-Dfyv", "/dev/block/mmcblk0p8");
About the performance and battery:
It is very fast and smooth comparing to the non ET version. At least it is on my device. For the battery, it will consume more battery because all 4 cores are running in a higher frequency to _that's kernel. You can always lower the frequencies to where _that settings then you should expect about the same battery usage..
For the heat issue: it should be depended on the load and frequency settings. For the light load on the balance mode, it should not be that high. However, you can lower your frequencies as describing above then you should not see any heat higher than your previous settings. I hope that I answer most of your questions...
Good luck...:fingers-crossed:
Click to expand...
Click to collapse
So, how long should a new install take usually?
bluewr said:
So, how long should a new install take usually?
Click to expand...
Click to collapse
For a clean installation, it should only take around two minutes or less... If it is more than 5 minutes, you can use the power button to force it off. You can check the message during the tuning to see what partition is causing issue...
LetMeKnow said:
For a clean installation, it should only take around two minutes or less... If it is more than 5 minutes, you can use the power button to force it off. You can check the message during the tuning to see what partition is causing issue...
Click to expand...
Click to collapse
Mine is at Tuning & Optimizing Data and the bar is at...98% for the last two hour.
TWRP 2.6.1.0
So I should try reinstalling it, or start all over again?
bluewr said:
Mine is at Tuning & Optimizing Data and the bar is at...98% for the last two hour.
TWRP 2.6.1.0
So I should try reinstalling it, or start all over again?
Click to expand...
Click to collapse
You can use the power button to force it off so it can boot to your system. When device is up and running, you may want to reboot it back to your recovery and try this.
1. Use a Format option under Wipe and Format you data partition.
2. When it is done formatting, you can go ahead and install ET v1.3 again. It should work nicely and cleanly this time...
Good luck and please report back, thanks..:fingers-crossed:
LetMeKnow said:
You can use the power button to force it off so it can boot to your system. When device is up and running, you may want to reboot it back to your recovery and try this.
1. Use a Format option under Wipe and Format you data partition.
2. When it is done formatting, you can go ahead and install ET v1.3 again. It should work nicely and cleanly this time...
Good luck and please report back, thanks..:fingers-crossed:
Click to expand...
Click to collapse
Doesn't work, still stuck at the final data part.
bluewr said:
Doesn't work, still stuck at the final data part.
Click to expand...
Click to collapse
Did it boot fine into the system when you tried to force it off with a power button? If it did boot fine, then your installation is successful except that something is not correct on your data partition and the ET should not touch the data partition. It is the reason why I use fsck to check all partitions to prevent any issue down the road. I need the answer from you so I can make better suggestions.. Thanks..
LetMeKnow said:
Did it boot fine into the system when you tried to force it off with a power button? If it did boot fine, then your installation is successful except that something is not correct on your data partition and the ET should not touch the data partition. It is the reason why I use fsck to check all partitions to prevent any issue down the road. I need the answer from you so I can make better suggestions.. Thanks..
Click to expand...
Click to collapse
No, it just shows the Asus start screen, then it reboots again and again.
I'll need to go into power+Vol down to get into TWRP to wipe and reinstall rom again.
I can boot into it with cromi-x without the ET tweak, but with it, it goes into boot loop.
bluewr said:
No, it just shows the Asus start screen, then it reboots again and again.
I'll need to go into power+Vol down to get into TWRP to wipe and reinstall rom again.
I can boot into it with cromi-x without the ET tweak, but with it, it goes into boot loop.
Click to expand...
Click to collapse
Hmm, Did format your data partiton and wipe everything on your internal SD except the external SD before installing the Cromi X? Can you tell me what version of Cromi that you are using? How did you proceed with the clean installation? Thanks..
LetMeKnow said:
Hmm, Did format your data partiton and wipe everything on your internal SD except the external SD before installing the Cromi X? Can you tell me what version of Cromi that you are using? How did you proceed with the clean installation? Thanks..
Click to expand...
Click to collapse
Cromi-X 5.2a
I reboot into recovery, use Wipe on everything except microSD(CromiX and EX tweak)
Then format it(Type yes)
Then go to install in TWRP and choose Cromi-X, and the Hunds OC option, and install and reboot it into Android.
Restart it once.
Then reboot into recovery and run EX tweak for new user.
I tried it 3 time, and it freezes, I can take a picture of it and upload it later tonight.
Currently going back to normal install and that v4 or v5 kernel, v6, makes me unable to see my 64gb microSD card in there
bluewr said:
Cromi-X 5.2a
I reboot into recovery, use Wipe on everything except microSD(CromiX and EX tweak)
Then format it(Type yes)
Click to expand...
Click to collapse
Try to format first before wipe everything
bluewr said:
Then go to install in TWRP and choose Cromi-X, and the Hunds OC option, and install and reboot it into Android.
Restart it once.
Click to expand...
Click to collapse
Make sure to choose Hunds and ET options
Then reboot into recovery and run EX tweak for new user.
Yes, it is correct.
I tried it 3 time, and it freezes, I can take a picture of it and upload it later tonight.
Related
ROOTING, TWEAKING, NEW GPU DRIVER, CPU AND/OR GPU OVERCLOCK
Using CyanogenMod kernel source from https://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.1-blackhawk for both P31xx and P51xx target, from codeworkx and heavily modified by me
CPU clock: 300MHz, 600MHz, 800MHz, 1.008GHz, 1.2GHz, 1.35GHz, 1.42GHz, 1.48GHz, and 1.52GHz, locked @ 1.008GHz on boot, thanks to cmenard
CPU voltage control, thanks to cmenard. You can use Android Tuner or System Tuner to set CPU voltage
GPU clock: 153.6MHz, 307.2MHz, 384MHz, and 512MHz, 384MHz as the default maximum clock, thanks cmenard
The ramdisk base on JB 4.1.2 ramdisk, thanks to Google and Samsung
Using newer PowerVR SGX 540 kernel modules and binaries blob build [email protected], thanks to omapzoom.org
row (thanks to gokhanmoral), sio, and vr scheduler support
Governor bug fix, replace Samsung's interactive governor with default OMAP4 3.0.31 interactive governor from omapzoom.org, pegasusq and lulzactive governor from gokhanmoral
ntfs read-only (not loaded by default), exFAT, NFS (not loaded by default) and CIFS/samba (loaded by default) filesystem support
LZO compressed kernel and initrd, bigger but faster
swap support
kernel config, insmod configs.ko and then you can access /proc/config.gz
external modem support, for PPP Widget
Some tweaks from gokhanmoral's siyahkernel for S3
Remove a lot of debug message from touchscreen driver, display, mmc, modem, etc
linaro arm-linux-gnueabihf- cross compiler
SuperSU v1.25 by Chainfire
No-frills CPU Control v1.26 by hrk
BusyBox v1.20.2-cm9 bionic (2012-07-14 01:52 +0200) in /sbin, will overwrite busybox in /system/bin or /system/xbin and save it as busybox.backup
nano and bash from CyanogenMod 9, sysrw and sysro from dsixda Android Kitchen
Early boot scripts support (/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
Post boot script support (/system/etc/init.post_boot.sh), use it to swap between external SD card and internal media
Custom boot animation support (/data/local/bootanimation.zip or /system/media/bootanimation.zip if exists, Samsung boot animation as a fallback). If a bootanimation.zip found, the boot sound will be turned off as well as the shutdown animation.
Modified mount options
adb mode in charge state, thanks to codeworkx
adb insecure
Advanced TCP congestion support, westwood as the default congestion (recommended by someone but I forgot)
No /system/etc/hosts patch, you can install one of ads blocker form Google Play (i.e. AdAway)
KNOWN BUGS/UNSUPPORTED FEATURES:
Youtube HD bug WiFi driver update fix this issue, thank to paraiso-san since this solution is achieved because his cooperation and "pressure" as well
Using this boot image, you will lose exFAT filesystem kernel support
In certain situations (MTP transfers, wireless transfers), CPU frequency sometimes exceeds maximum frequency setting Finally, I managed to fix it :victory:
INSTALL:
There are 2 choices of installation: without overclock (*core* filename) and overclock version (*addon-oc* filename). All *addon* require the *core* package, otherwise your device will be soft brick because the graphics subsystem will fail to start. Confused? Do not download any package! Flash this using the latest CWM recovery at your own risk.
For GPU overclock, change:
Code:
echo 0 > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
to:
Code:
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
in /system/etc/init.d/00boot or run above command on "Terminal Emulator" or "adb shell" as root every boot
To set your external SD card as internal SD card, over "adb shell" or Terminal Emulator:
Code:
su
setprop persist.customboot.sdcard external
and then reboot your device.
To restore SD card default mount point:
Code:
su
setprop persist.customboot.sdcard internal
and then reboot your device.
BIG FAT WARNING: If you set your external SD card as internal media, always turn off your device first before ejecting your card!
To set your preload partition as swap partition, over "adb shell" or Terminal Emulator:
Code:
su
setprop persist.customboot.swap true
and then reboot your device.
To disable preload partition as swap partition:
Code:
su
setprop persist.customboot.swap false
and then reboot your device.
This kernel has driver and filesystem modules are not enabled by default, edit /system/etc/init.d/01modules to enable NFS filesystem and NTFS filesystem (read-only) or to change TCP congestion
DOWNLOAD:
kkboot-0.6.0-core-p51xx.zip (10.5 MB)
kkboot-0.6.0-addon-oc-p51xx.zip (5.3 MB)
kkboot-0.6.0-addon-exfat-p51xx.zip (5.7 MB)
kkboot-0.6.0-addon-oc-exfat-p51xx.zip (5.7 MB)
CREDITS:
Linux, Google, Samsung, Texas Instruments/omapzoom.org, CyanogenMod developers, Chainfire, dsixda, cmenard, gokhanmoral, hrk, imoseyon, coolbho3k, Faux123
Placeholder!
Reserved
thanks a lot my bro
i test and I hope this time it work
brolee93 said:
thanks a lot my bro
i test and I hope this time it work
Click to expand...
Click to collapse
Alors ?
for me NOTHING of your kernels work :/
hum one kernel kkboot-0.4.2-core-jb-p51xx.zip (8.8 MB) boot but after 5sec in home my tablet FREEZ :/
but thanks for your big work i wait for your new version lol
You must flash core first, then one of the of kernels I believe. Also, clear cache and dalvik before flash.
Backing up my **** now then flashing to stock. I'll provide log cats.
Sent from my GT-P5110 using xda premium
brolee93 said:
for me NOTHING of your kernels work :/
hum one kernel kkboot-0.4.2-core-jb-p51xx.zip (8.8 MB) boot but after 5sec in home my tablet FREEZ :/
but thanks for your big work i wait for your new version lol
Click to expand...
Click to collapse
Including the *stock* version?
dynospectrum said:
You must flash core first, then one of the of kernels I believe. Also, clear cache and dalvik before flash.
Backing up my **** now then flashing to stock. I'll provide log cats.
Sent from my GT-P5110 using xda premium
Click to expand...
Click to collapse
Waiting for your report...
langsung ane tes gan :fingers-crossed: :ngacir:
Cleared Cache & Dalvik-Cache
flashed kkboot-0.4.2-core-jb-p51xx.zip
flashed kkboot-0.4.2-option-gpu_oc-jb-p51xx.zip (4.7 MB)
Freezes right after unlock screen. Can't get adb to connect in order to save dmesg. Can't flash stock kernel since CWM won't read external sd. Gonna reflash 4.1.1. stock/root it , make internal backup w/CWM and copy .zips to internal. Hopefully I can reflash stock kernel and dump logs.
You mention in OP all packages require core. I'm assuming you mean that core must be flashed before OC kernels, correct? If not, then what do you mean and in what order should they be flashed?
*update* lol completely ****ed up my sdcard :\
dynospectrum said:
Cleared Cache & Dalvik-Cache
flashed kkboot-0.4.2-core-jb-p51xx.zip
flashed kkboot-0.4.2-option-gpu_oc-jb-p51xx.zip (4.7 MB)
Freezes right after unlock screen. Can't get adb to connect in order to save dmesg. Can't flash stock kernel since CWM won't read external sd. Gonna reflash 4.1.1. stock/root it , make internal backup w/CWM and copy .zips to internal. Hopefully I can reflash stock kernel and dump logs.
You mention in OP all packages require core. I'm assuming you mean that core must be flashed before OC kernels, correct? If not, then what do you mean and in what order should they be flashed?
*update* lol completely ****ed up my sdcard :\
Click to expand...
Click to collapse
- Flash the *core* version first - this version have no overclock code at all, reboot
- If fail to enter the home screen, wait a minutes and then force reboot your device (press and hold the power button)
- If still fail to enter the home screen, plug your device to power charger and then force reboot your device. Wait the battery animations appear and then unplug your device from power charger. Wait a minutes and then boot to recovery
- Flash the *stock* version - this version use stock Samsung P5100 kernel, reboot
- It's really strange if the *stock* version fail to enter the home screen, wait a minutes and force reboot your device
- Still fail???
Actually, if the battery animations in charging mode shown, my kernel works on your device. You can always connect to your device over USB since the adb mode enabled by default on boot including in charging mode.
I will try when I get home. Flashing core, then the CPU/GPU OC zip was booting, but as soon as I would open anything app or settings the tablet would hang then shutdown and boot loop.
Sent from my SGH-T769 using xda premium
ketut.kumajaya said:
- Flash the *core* version first - this version have no overclock code at all, reboot
- If fail to enter the home screen, wait a minutes and then force reboot your device (press and hold the power button)
- If still fail to enter the home screen, plug your device to power charger and then force reboot your device. Wait the battery animations appear and then unplug your device from power charger. Wait a minutes and then boot to recovery
- Flash the *stock* version - this version use stock Samsung P5100 kernel, reboot
- It's really strange if the *stock* version fail to enter the home screen, wait a minutes and force reboot your device
- Still fail???
Actually, if the battery animations in charging mode shown, my kernel works on your device. You can always connect to your device over USB since the adb mode enabled by default on boot including in charging mode.
Click to expand...
Click to collapse
ok i test it is very very strange :/
ùy phone boot with Core version but after 10 secondes my phone freez .same after few reboot.
with stock kernel of you my tab stuck on logo GALAXY tab :/
- Edit i flash core version with wipe optimisation app
dynospectrum said:
I will try when I get home. Flashing core, then the CPU/GPU OC zip was booting, but as soon as I would open anything app or settings the tablet would hang then shutdown and boot loop.
Sent from my SGH-T769 using xda premium
Click to expand...
Click to collapse
I had exactly the same problem..
Sent from my GT-P5100 using XDA Premium HD app
ketut.kumajaya said:
- Flash the *core* version first - this version have no overclock code at all, reboot
- If fail to enter the home screen, wait a minutes and then force reboot your device (press and hold the power button)
- If still fail to enter the home screen, plug your device to power charger and then force reboot your device. Wait the battery animations appear and then unplug your device from power charger. Wait a minutes and then boot to recovery
- Flash the *stock* version - this version use stock Samsung P5100 kernel, reboot
- It's really strange if the *stock* version fail to enter the home screen, wait a minutes and force reboot your device
- Still fail???
Actually, if the battery animations in charging mode shown, my kernel works on your device. You can always connect to your device over USB since the adb mode enabled by default on boot including in charging mode.
Click to expand...
Click to collapse
GT-P5113 | Stock Rooted | CWM 6.0.1.0
Cleared Cache & Dalvik.
Flashed kkboot-0.4.2-core-jb-p51xx.zip
Tablet booted to lock screen. Waited 30sec, then unlocked. Desktop swipes fine. I can open the app drawer and flip through the pages. *Wifi icon was missing*
Sliding notification bar open works, but clicking on anything that would open a new process results in a frozen tab. After restart it will bootloop.
Cleared Cache & Dalvik
Flashed kkboot-0.4.2-stock-jb-p51xx.zip
Tablet does not get past the initial Samsung Galaxy Tab 2 bootloader screen.
Bootloops
I PM'ed you my logcats. I Don't know if I was able to log what the problem is since it's the first time i've ever submitted logs. Not to mention they're enormous I hope they help! :highfive:
dynospectrum said:
GT-P5113 | Stock Rooted | CWM 6.0.1.0
Cleared Cache & Dalvik.
Flashed kkboot-0.4.2-core-jb-p51xx.zip
Tablet booted to lock screen. Waited 30sec, then unlocked. Desktop swipes fine. I can open the app drawer and flip through the pages. *Wifi icon was missing*
Sliding notification bar open works, but clicking on anything that would open a new process results in a frozen tab. After restart it will bootloop.
Cleared Cache & Dalvik
Flashed kkboot-0.4.2-stock-jb-p51xx.zip
Tablet does not get past the initial Samsung Galaxy Tab 2 bootloader screen.
Bootloops
I PM'ed you my logcats. I Don't know if I was able to log what the problem is since it's the first time i've ever submitted logs. Not to mention they're enormous I hope they help! :highfive:
Click to expand...
Click to collapse
Please re-download kkboot-0.4.2-stock-jb-p51xx.zip (10.9 MB).
Your latest kernel working silky smooth sir :thumbup: No problems at all so far. I wiil post log if I run into any. ^_^ Can't wait for OC!
Sent from my GT-P5113 using xda premium
@dynospectrum Your are so kind to test my work. Wait for the next test
dynospectrum said:
Your latest kernel working silky smooth sir :thumbup: No problems at all so far. I wiil post log if I run into any. ^_^ Can't wait for OC!
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Please re-download kkboot-0.4.2-core-jb-p51xx.zip (9.3 MB). This is using Sourcery G++ Lite 2010q1-202 cross compiler.
"Those, who fail to read history are bound to repeat its mistakes"
People here have and did and will fail to read the things here and many did and many probably will have to lose their devices. You don't have to lose a device to get knowledge inbetween your ears.You don't have to be stupid. You surely can learn from your mistakes. But There's a better way. You can learn from others mistakes. This thread is a compilation of such mistakes ,that I personally have done and many others ,who did and their solutions aka The easy ways.
So, officially I congratulate you for finding this thread and reading Upto here. So, even if you don't read the whole thread, these are the main stuff you must know is
1. Rooting is a dangerous process -done by developers only. If you did root your device, you assume full responsibility for your device. So, if you can't think like one of the developers at least partly, I suggest you don't root your device ,coz when you mess up, the one who deviced the procedure or Rom will not help you. And everything you find here is in "AS IS " tag.
2.If you have rooted, next thing you must do is backup-
Go to recovery,
go to backup and restore
click backup.
I find it strange that this is not included in the root procedure. This surely would've helped a lot of Picos out there.
3.NEVER DO A RUU
-It unanimously holds the number ONE title for the major causes of bricking of Picos.
Trust me -Surely you can save your device, without the ruu. And with ruu, you're bound to fail without proper knowledge and research.
The only time you are suggested by experts to do a ruu is when you have already done a ruu "and" bricked it.
4. Overclocking here may cause burnt nand. -know what Rom you're using-it may have built in-overclock .
However, overclocking doesn't necessarily produce burnt-nand for all devices.
5.Finally, Not all answers you receive in the question and answer thread are good. Some answers will kill your device. So please judge the credibility of the answerer before you follow the answers. Generally, you could track back their previous answers and their working. Thanks meter is a good source of credibility -but not always -Not all who have big thanks record are helpful neither are they knowledgeable-There are spammers, who trick people into giving thanks.Do your home work before you trust a stranger. Recognized developer title is a good source of credibility.
The above five should save you a lot of trouble.
Ever in trouble? Drop by and read.
Do your googling,if you don't understand anything here.Have a great time !
Re: [faq][newbies only][mini edition]
��To start, this thread is only for newBies,who have rooted thier Rom and have a custom recovery. If you haven't, click here
Alright, this thread aims to answer all the frequently asked questions by newBies. The section this thread aims to answer will consist mostly of custom Roms especially cyanogen.
To start, we'll start with basics
Our phone consists of the following five partitions
1.Boot/kernel
2.Recovery
3. System/Rom
3.1What's not working
3.2 Latest links
4. /cache- error /last log
5.Data
5.1Scripts
6.Common issues after flashing Rom, scripts/GAPPS/PLAY STORE /
Ram
7. USB and CPU ,screen and power button-2/7/13
8. About developers and members
9. ��Burnt nand*recovrecovery 25/6/13 *��
10. STILL CAN'T FIND THE ANSWER ��
10.1LOGCAT
10.2ADB
11.MINI TIPS AND TRICKS
11.1CM9/10 themes
11.2.FONT CHANGING AND language तदधा ಥಮು support adding
11.3.DID YOU KNOW?
12. Recommended apps
13. BATTERY LIFE AND PERFORMANCE
14 .http://forum.xda-developers.com/showthread.php?p=38098604
BUILD. PROP TWEAKS
We'll discuss the faq in each.
All links are here
Index:
http://forum.xda-developers.com/showthread.php?t=1754876
This is the best link you'll ever have
Thanks hrkh83
Guides
http://forum.xda-developers.com/showthread.php?p=36057579
Guides for everything
Thanks hpsgill
Make yourself useful by akshat
Seen it before,
Just read this now
http://forum.xda-developers.com/showthread.php?p=37805872
Stock Roms instead of bricking ruu
tk immortal yash
http://forum.xda-developers.com/showthread.php?p=39101954
Re: [faq][newbies only][mini edition]
/BOOT(4 MB Max )
1.what does this partition contain?
It contains your kernel
2.what is kernel?
It's a in betweener between ROM (/system ) and your hardware.
Basically, a software, which connects the main software (your Rom gui) and the hardware
3 .what is the stock kernel version?
2.6
4. Is there a update available?
Yes. You can update it to 3
3.4 is currently being worked on
5.what are advantages of kernel 3 ?
Nothing much that you can feel
Basically related to stability, security, and future Android Os updates can easily be done for a310e
5.where are the links to kernel 3 ?
Look down
6.what's not working in kernel 3 ?
1.Ext4+kernel 3+mount2SD/s2e/link2SD doesn't work.
2. CPU states file reading ~fixed in overclocked kernel ~fixes yet to be fully implemented across RomS [overclock may cause burnt nand/recovery ]
With cm9
1.Firewall
2.USB tethering
3. Wi-Fi hotspots
4.Vpn
Anything related to iptables
With cm10
Known issues
Ext4 cannot be mounted?
Temple run 2 and subway surfers reboots*fixed in overclocked kernel *burnt nand *
7. What's not working in kernel 2 ?
garuda v5
Data usage option in settings in jelly bean.
8.what's not working in kernel 2.6 sakindias cranium kernel?
Build #2
Lag
Build #3
No support for Android native a2SD
Build #4
Same as build #3,but advertised as faster
9. I wanna make my own kernel?
Special thanks to bhargz16
http://forum.xda-developers.com/showthread.php?t=2114594
10.Is there a overclocked kernel?
Yes
http://forum.xda-developers.com/showthread.php?p=38098604
11. How to Flash kernel? Do I need to clean install?
No need to clean install
Copy zip to root of /SD card
Go to recovery
Install zip from SDcard
Choose the correct zip
Install
Reboot
Go back to main ^|^
Re: [faq][newbies only][mini edition]
/Recovery(5 MB Max )
First thing to do after root is to make a nandroid backup.
Go to backup and restore and select backup
1.what is this partition?
It contains your recovery
2.what is recovery?
It's a specialized partition for Android, which is used when something goes wrong.
We use it to change (flash) Roms, change kernels and mostly everything in xda. Make nandroid before you mess up
3. What are the recoveries available for a310e ?
1 .yannou90 (cwm5) recovery
2.Twrp 2 .3 by cute prince
3. twrp 2.2 by oblikas
4.cwm6 by sakindia
5.*OFFICIAL *The latest TWRP by bhargz16( http://forum.xda-developers.com/showthread.php?t=2123503 )
6.cwm6 by nihar.g
Links .check index link in top post
4. Are all of them stable?
The 1 and 5 are pretty stable.
What's not working:
cwm6 by sak let me down big time .
http://forum.xda-developers.com/showthread.php?p=38734554
Except 1,all other recoveries will not show charging animation, when you are charging your phone after switching it off ~instead of charging animation ~you'll be going to recovery
twrp official - some problems with ext4 partition has been reported and also reported to have been fixed. -I never had the problem before and after and I recommend this one 2.5 present here in xda.
twrp cute prince has issues restoring backups (problem with symlink )
5.what's the difference between them?
cwm5 - complete backups of all partitions
twrp - support compressed backups /file manager and other great things
cwm6 - your SD ext partitions will not be fully backed up during subsequent backups,but only the changed files greatly reducing the size of subsequent backups
6. Can you explain more about cwm ?
http://forum.xda-developers.com/showthread.php?p=38100620
7. Recommended apps.?
Recovery file manager aroma 1.8
8. How to flash a recovery?
Two methods described in detail in link above by bhargz16 ~ fast boot
Flash from phone:
Required:
Flash_image binary
You can flash any recovery
From terminal using
Code:
su
flash_image recovery /sdcard/recovery.img
You need recovery.img (renamed like that ) present in /sdcard itself
9. Error while restoring .Androidsecure /sdext ?
http://forum.xda-developers.com/showthread.php?p=39874898
10. Cannot go to recovery /burnt recovery /unable to flash recovery?
Use
Code:
fastboot boot recovery /sdcard/twrp5.img
or
Code:
fastboot boot recovery.img
or
Code:
fastboot boot /sdcard/twrp5.img
You need twrp5.img or recovery.img present in /SDcard and renamed like that itself.
After booting into recovery, you can do everything you please. ~flash erase format and install new Rom and boot the device
After booting up the device, flash erase mtd1 through terminal emulator.and then flash a suitable small recovery. And then pledge here that you'll never overclock ever again.
Go back to main ^|^
Re: [faq][newbies only][mini edition]
/SYSTEM (235 MB Max )
1.what is it?
Here's where your Rom resides
Any cyanogen /ever/miui roms all go here
2. What are system apps
Any app in /system /app is system app and they have special permissions
2.1 how to make a app system app?
Uninstall the app with titanium backup and copy it's apk to system/app(normal delete apk will not delete. Dex and lib files ) ~reboot ~
Some apkS need it's library file also in /system /Lib (copy from /data /Lib to /system /lib )
3.what is binary?
These are executable ~very important files in /system /bin. (or /xbin in recovery)
Your root su is here
4. What are the roms available?
Many roms are available in xda
Main line ones are
CYANOGEN 7
CYANOGEN 9
CYANOGEN 10
Cyanogen 10.1
Miui
5.What is cyanogen 7 ?
It's a cyanogen version of gingerbread
9 is ics
10 is jelly 4.1
10.1 is jelly 4.2
5.1 what's the development going on?
cm7 *camera was unable to be fixed *development stopped
cm 10*active development now *
cm 10.1 *thread closed *
6. How to install a new Rom? Cyanogen for example?
Download the latest build. Zip and put in the root of /sdcard.
Go to recovery
Factory reset data
Wipe cache
Wipe dalvik
Wipe SD ext
Choose install zip from /sdcard and choose the build. Zip
Wait
Reboot
Go back to main ^|^
The nothing really bugs list
Welcome to THE "NOTHING REALLY" BUGS™
This is the official nothing really bugs Pico web post at xda. Its name implies that the bugs present are really nothing to some people. But to the rest, it may bother a lot. So, this post.
Here you'll find most of the nothing really bugs. All statements having "Nothing really " in bugs list directs here. This is to inform new flashers of what they'll get and what they won't. To make the facts clear,so that you won't have to flash every Rom to find out all the nothing really™ bugs. After all, this is a newbie friendly thread.
Please note that though every effort has been taken to ensure an exhaustive list of all the bugs .Some may not have been stated here .If you do find a bug, which isn't stated here, please feel free to mention it here and I'll add it after being personally confirmation by me or two to three renowned senior member witnesses. Further more, some bugs here may have been fixed. You can take a look at the last edited day of this post to make sure this post is up to date. And you can mention it here,if any of the information found here is wrong.
1.What doesn't work in cm10 4.1 Jelly beans ?:
1video (video recording with some third party apps~Skype video messaging, zoom camera ,camera magix and a lot more)(S. ucam works fully)
2Bluetooth headphones can't be used during call(try using sound about )✘
2.1 Bluetooth stereo headphones ✘
3vsync
4.stock camera force close often and unstable (S. Camera 360/ucam)
5.Wi-Fi unable to turn on ~from settings /notification bar. (s:Flash kernel 2.6)
6.burnt nand
7. Wi-Fi direct (native )causes reboot. (S. 3Rd party app ~fast file transfer)
8.some VOIP~{ex:gtalk(even after normal gapps),and many more}
9.Most streaming video{not flash, but those, which open in mx} doesn't work. Most TV apps don't work (not flash using tv apps)
10. mobile data may fluctuate for some(timedo app to turn on and off airplane mode for every hour)
11. calls robotic call for some
http://forum.xda-developers.com/showthread.php?p=32997468
12. Unofficial adobe flash is flickering too too much. (Only Firefox actually works with flash..which flickers unbearably ~the rest don't even work )
13. Headphones volume control during in call✘
14.USB tethering (native)✘
15. Wi-Fi hotspots work only as open source ✘
16.Bluetooth A2dp streaming ✘
17.Firewall rules don't stick, when put in init.d. Somehow the Rom process overtakes the firewall rules during boot and during some process. My intuition directs the blame at bandwidth controller| throttle service~|Data usage settings|which wasn't implemented properly, but using dirty hacks
18. USB mtp and ptp not working at all. USB mass storage not working for certain devices ~double mounting. (s.flash kernel 2.6 with USb mass storage fix here. )
19. Multi mount SD app doesn't work [s.flash kernel 2.6]
OTHERS
1. Battery drain
2.Phone heating
3.WiFi toggle
Total :22[Because, I used this Rom for a long time,so the large number]
✘- Unconfirmed by me .The rest are personally tested and confirmed "not working " and again confirmed to be a problem of Rom itself.
2.What doesn't work in cm9 ?
forum.xda-developers.com/showthread.php?p=35756952#post35756952
2VIDEO PLAYBACK doesn't work as well as stock
3 Wi-Fi toggle in latest RomS
4 Bluetooth stereo headphones ✘
Experienced by some:
A. Encryption doesn't work (crypt)✘
B.robot call http://forum.xda-developers.com/showthread.php?p=32997468
C.mobile data flickering
Note: video playback is much better in cm10.
Language rendering is also much better in cm10.
3.what doesn't work in Original HTC STOCK ROM?
A. if you ever click "reset to default" in the Camcorder settings..,all future video recordings will overwrite already taken videos and all previous videos will be lost(use ucam)
B. sending a more than 150MB file on Bluetooth file manager app through Bluetooth will reboot your device.
(use stock transfer)
3.1 what's not working in a rooted stock Rom?
(make a nandroid backup first to protect you)
Optimize storage in storage settings
Factory reset will put you in bootstruck.
4.What doesn't work in cm10.1 ?
Camera and lot more minor/major
Too long list
Will update when usable
5.what doesn't work in cm7 ?
Camera
6.what's not working in kernel 3 ?
1.Ext4+kernel 3+mount2SD/s2e/link2SD doesn't work.
2. CPU states file reading ~fixed in overclocked kernel ~fixes yet to be fully implemented across RomS [overclock may cause burnt nand/recovery ]
3.Wi-Fi toggle from notification bar /from settings
4. USB mtp and ptp not working at all. USB mass storage not working for certain devices ~double mounting.
5. Multi mount SD app not working.
With cm9
1.Firewall
2.USB tethering ✘
3. Wi-Fi hotspots ✘
4.Vpn ✘
Anything related to iptables
With cm10
Known issues
Some partitions [?Ext4] cannot be mounted
*burnt nand *
With latest cute prince kernel [power management fix ]:
Mounting of SDcard on some devices
Multimount SD app
7. What's not working in kernel 2 ?
garuda v5
Data usage option in settings in jelly bean.
8.what's not working in kernel 2.6 sakindias cranium kernel?
Build #2
Lag
Build #3
No support for Android native a2SD
Build #4
Same as build #3,but advertised as faster
9. Sense4 Roms
1.Burnt nand ~most common ✘
2.Random reboots ✘
3. WiFi direct. ✘
4.Bluetooth headphones ✘
Go back to main ^|^
✘- Unconfirmed by me .The rest are personally tested and confirmed "not working " and again confirmed to be a problem of Rom itself.
S - probable third party solutions
Solutions for burnt nand -Please go to burnt nand section.
[COLOR="RED"]Welcome to [b]▶LâTêS†↭ⓛⓘⓝⓚⓢ™◀[/B][/COLOR]
Welcome to ▶LâTêS†↭ⓛⓘⓝⓚⓢ™◀
Not sure whether it'll be updated,but galaxyfreak released a app on latest Roms ~ http://forum.xda-developers.com/showthread.php?p=38913186
Why this post ?
Because index has only thread links and sakindia123 never updates op
If he does, then this post will not be updated anymore. Other than that, here are some kernel links as well. Other than the main line ones, the others are not updated. Sense4 links are already present in op and here as well http://forum.xda-developers.com/showthread.php?p=40111838 . Any link that's not present in op will only be updated.
1.what's the latest build on cyanogen 9?
Build 13
http://forum.xda-developers.com/showthread.php?p=36626369
#14*beware of burnt nand *
http://forum.xda-developers.com/showthread.php?p=38770875
2.what's the latest build on cyanogen 10 ?
Build 3.2.2.use with kernel 2.6
http://forum.xda-developers.com/showthread.php?p=38183817
Liverpool fan latest 3.2
http://forum.xda-developers.com/showthread.php?p=38447868
Beta 5~beware of burnt nand ~
Video fix by bhargz*liverpl 4 beta5*
http://forum.xda-developers.com/showthread.php?p=39124906
http://forum.xda-developers.com/showthread.php?p=39090779
Beta6~beware of burnt nand ~
http://forum.xda-developers.com/showthread.php?p=39166124
+
http://forum.xda-developers.com/showthread.php?p=39804373
(Flash this to prevent overclock)
Lock screen fix for both beta 5 and 6 .
http://forum.xda-developers.com/showthread.php?p=39043840
2.1 Aokp build link
http://forum.xda-developers.com/showthread.php?t=2208242
3.what is the latest build on cyanogen 10.1 ?
Alpha 3
http://forum.xda-developers.com/showthread.php?p=38094629
Alpha 4
http://forum.xda-developers.com/showthread.php?p=38325531
4.what's the latest build on kernel?
Old Kernel 3
http://forum.xda-developers.com/showthread.php?p=36572115
Kernel 3 v2 only for sense
http://forum.xda-developers.com/showthread.php?p=38466559
http://forum.xda-developers.com/showthread.php?p=39730163
Kernel 3 v2 for cm10
http://forum.xda-developers.com/showthread.php?p=39737920
http://forum.xda-developers.com/showthread.php?p=39804373
5. Is there a overclocked kernel?
http://forum.xda-developers.com/showthread.php?p=38098604
kernel 2.6=garudav5kernel
6. Kernel 2.6 for JB ?
http://forum.xda-developers.com/showthread.php?p=37649737
http://forum.xda-developers.com/showthread.php?p=36303556
7. Kernel 2.6 for ics?
http://forum.xda-developers.com/showthread.php?p=35797210
http://forum.xda-developers.com/showthread.php?p=36526379
http://forum.xda-developers.com/showthread.php?p=37550173
8. Side effects and solution of using kernel 2.6 on a kernel 3 based Rom:
http://forum.xda-developers.com/showthread.php?p=39452607
Basically, USB storage may not work.
To, make it work, Flash the fix attached with this post(don't remove battery @ any stage:sly-tested on my twrp 2.4.4 with cm10beta5.May not work with ics.
Alternatively, you can use multi mount SD app /root tool box lite app.
Attached zip md5: 8216eaf4a357b9cddc5cfd29b8d05a50
Attached zip sha-1: 408a075479745fe1713f8c55a968801f7f6160dd
Some more links :
http://forum.xda-developers.com/showthread.php?p=40964578
Super wipe zip
http://forum.xda-developers.com/showthread.php?p=38338418
Nand recovery procedure:
http://forum.xda-developers.com/showthread.php?p=38098622
tk to akshatshenoy.
Flashing an older ruu:
Not recommended @ any stage
http://forum.xda-developers.com/showthread.php?p=38694608
Even if it works,you might have problems data, battery drain etc.. if you Flash a wrong radio
KERNEL RAMDISK exchange on Android itself:wip
AUTORAMDISK™ EXCHANGE PROJECT alpha™
http://forum.xda-developers.com/showthread.php?p=40035607
How to install kernel? Clean?
http://forum.xda-developers.com/showthread.php?p=38098513
QUESTION NUMBER 11 ABOVE
Go back to main ^|^
Re: [faq][newbies only][mini edition]
/DATA (150 MB )
1.WHat's this?
It is the internal memory
2.Why is it important?
Because this is the place where all the apps go
No /data = no more apps
3.what's our available internal memory?
150 MB
User available 90 MB
4. Any way to increase internal memory?
By scripts
5 .Recommended apps to diagnose application not installed
Diskusage app
Log cat
6. What does a app contain?
App when installed splits into apk dex,and data(lib+data) files
Go back to main ^|^
Re: [faq][newbies only][mini edition]
SCRIPTS
Before we start, a app when installed takes space as three parts.
They are apk,dex and data (lib+app data)
All scripts work by symlinking
1. What are the scripts available for our explorer?
Partial scripts
A.Link2SD app
Moves apk,dex,lib~doesn't move app data
B.Root data2SD app
Need ext partitions
Moves application data2 ext
Full scripts--Need init.d support able to move fully /partially as per requirements
Links available in index
1.Mount2SD
Download from play store or from here check index
Famous for it's stability and frequent updates
Issues +
2. Int2ext
As per script, moves partially /fully .
Has a large user base
issues ++
3.s2e
Moves fully.
Issues +++
NO official version for jelly beans.
4.a2sd darktremor
Issues ++++
However works pretty well with stock Rom and jaggy Rom
Discontinued
5.ungaze script
Issues +++++
I don't recommend it.
Why not?
Because
http://forum.xda-developers.com/showthread.php?p=33750812
http://forum.xda-developers.com/showthread.php?p=31915607
1.1 mount2SD doesn't work? Script not executed fully @ boot?
Flash kernel 2.6 from above and you should be good to go.
2. How do I increase internal memory (literally ) from 150 MB to 2GB(for example SD ext )?
Use mount2SD reverse mount
Use int2ext
Side effects:
As per Android rules, 10% of internal memory will be unavailable
So, 200 MB out of 2GB SD ext will be unavailable
Mount2SD also has normal moving methods ,which will make Android think you'll have 150MB but you can fill up 2GB inside of 150 MB (Here 10% would mean 15 MB)
3. I installed d2ext/similar ,I'm not able to install more apps ,even though I have more SD ext space?.
A. First make sure you don't hit 10% data limit described above
B. Use diskusage app to determine,which partitions are full
For example- some scripts don't move dalvik and so dalvik will fully accumulate in /data creating no space.
C. Fix permissions from recovery, wipe cache and dalvik and reboot.
4. My Rom doesn't have init.d support /I'm using stock Rom?
Check index
You can add init.d support by
Flashing custom kernel (cranium)
Flashing scripts to make init.d support (or pimp my Rom app[not tested])
5. Where to add scripts before flashing Rom?
Add it in /system/etc/init.d (permissions are rwx rwx rwx ,if you're adding this in recovery after flashing )
For mount2SD add configurations folder in /data/m2sd.
6. How to migrate from link2SD to mount2SD?
http://forum.xda-developers.com/showthread.php?p=38840247
7. Is there a full script so that I can use both my internal memory and SD ext?
A bit complicated, but this what I use...
Configure mount2SD
To move both apk and dalvik
Don't move data.
Then open titanium backup to move app data
@First move one app data to create data2SD directory.. then you can batch move whatever apps you think fit.
But please make sure you have at least 10 to 30 MB in /data and in/SD ext (SD ext not necessarily ) before a nandroid backup. Otherwise restoreS will not work.
Go back to main ^|^
Re: [faq][newbies only][mini edition]
Common issues with scripts:
0. Device stuck @ HTC logo with 4 error icons on all four corners
Since you flashed an ruu and failed user data fail etc.
Unlock bootloader if possible
Flash twrp recovery again
Code:
fastboot flash recovery.img
Then go to recovery with this command
Code:
fastboot boot recovery
Now that you're in recovery wipe everything, format everything .
If flashing failed /you can't enter recovery, do this keeping twrp recovery.img in /SDcard
Code:
fastboot boot /sdcard/recovery.img
Do cute prince recovery procedure shown in burnt nand section
Flash erase mtd3 as well
Now Flash your Rom and boot
If it doesn't boot, repeat the whole procedure above and now
Do ruu.
If all the above failed,
http://forum.xda-developers.com/showthread.php?p=39181288
Read the above thread fully. That's the last resort.
Moral : Don't ever Flash an RUU (if you haven't already )
You can Flash stock Rom ~safer
1. Device struck in HTC logo
Wait for 15 minutes
Try pulling out battery and reboot
Update busybox and try installing scripts again
Convert your partition to ext3
Change your kernel to 2.6
2. Mount2SD ~apps update after every boot?
Turn cache off in app
Turn safe mode off
Clear cache and dalvik ~fix permissions ~reboot
Common issues after flashing:
1. I get status 7 error?
Open archive with Bluetooth file manager and check archive integrity
Try different compression method(thanks hpsgill)
Delete system apps
2. I get status 0 error?
Update binary used is different
Exchanged update binary from a working zip to this one
Other errors can be cured by changing recovery .
http://forum.xda-developers.com/showthread.php?p=38469360
Common issues after flashing Rom:
1. Always do a clean install
To wipe everything except /sdcard.
Even in /sdcard delete Android /data after backup
2. No I won't listen. I want to do you a dirty install. Show me how?
Your choice
http://forum.xda-developers.com/showthread.php?p=35903694
3. I get force closes of all apps?
Dalvik problem.
Clear cache and dalvik cache and reboot
4.I get force close of a specific app?
If it's a paid app, then you need to change your Android id to your original Id with Android id changer /titanium backup
Not a paid app?
Clear cache and data of that app and reboot
Fix permissions
5.reboot after reboot?
Thanks bhargz16
Kernel problem. Change kernel
GAPPS:
1. This gapp always force closes?
A. If it's a gapp found on play, just uninstall that gapp from system using titanium backup and then reboot and install from play store.
B.if not found on play, then try flashing a different gapps version from goo.im .
Make sure you have enough space on /system and on /cache before flashing and then flash. If not delete unused apps like stock keyboard ,etc
2. RPS5~AEC0/927/any other error while downloading apps from play?
A. Clear data cache of play store app
Reboot
B. Clear data of google services framework
Reboot
C. Remove your google account and re add it. Reboot.- this worked for me.
3. All my apps are missing from installed apps in play?
Wait for some time,if you've flashed a new Rom
Clear data and cache of play store
Reboot
Download app eric market fix *use @ your own risk *
Repeat the solution of questions 2.
Go back to main ^|^
Part 2 on next page :thumbup:
Re: [faq][newbies only][mini edition]
CPU:
1.Can you overclock?
IMO,
All overclocking burns nand.
It's just a matter of sooner /later.
Read this post before attempting anything
http://forum.xda-developers.com/showthread.php?p=38445346
Burnt nand recovery procedures here ~~the third post below this post
http://forum.xda-developers.com/showthread.php?p=38098622
The links below are old. All latest Roms come with overclocked burning kernels.
cm10:
http://forum.xda-developers.com/showthread.php?p=38189883
cm10.1:
http://forum.xda-developers.com/showthread.php?p=38336080
gpu oc
http://forum.xda-developers.com/showthread.php?p=38331698
cpu oc
2. Governors ~what are they?
As the name says they govern when the cpu should go to higher speed and when they should sleep
Performance governor always keep your phone at Max
Powersave keeps your cpu always at low
USB :
1. Flashed kernel 3 and USB doesn't work.?
Flash kernel 2 back.
2. I want to know how to fix USB +kernel 3?
Don't know
3. Can I have usb otg ?
No, not yet.
SCREEN AND POWER BUTTON and soft keys:
1.SCREEN turns on after turning off ?
A. Some apps are trying to make screen on. After screen turns on, go to settings immediately and open running applications, you may be able to find the culprit. It's probably the app, which is restarting. Some apps like lock any app screen etc. Logs could be helpful.
B. Some users reported it could be a hardware problem -look below for power button issues.
C. Some users reported it could be a script problem (rare )
2. My home screen button and /or search buttons doesn't work?
A. Did you do a dirty install of new Rom
Clear cache and dalvik and fix permissions and reboot
B. Copy com.Android.providers.settings /databases from your previous nandroid backups(use yaffs file manager /nandroid manager)and paste it in it's respective location now (paste it using file manager in recovery )
C. If that doesn't work, clean install again
Tech savvy? ~search for device provisioned 1 in cyanogen forums
http://forum.xda-developers.com/showthread.php?p=38633404
3. Power button doesn't work properly ?
A. If it's not a software problem(try the above solution first),then you broke it.
If you broke it, avoid using the power button anymore-use attached scripts indeed.
There are apps in market to simulate power keys.
Or
http://forum.xda-developers.com/showthread.php?p=38633404
Go back to main ^|^
Re: [faq][newbies only][mini edition]
Miscellaneous topics:
Subject to change without prior notification
Developers:
1. Who are the developers that make these roms?
1. Cute_prince
2.sakîndia123
3.derefas
4.lirokoa
5.liverpool fan
6.bhargz16
7.nihar.g
8.ngolralph
And many others. The above are the developers of the roms that I used and present in no order.
2. Why doesn't sakindia123 update the OP ?
Disclaimer: Since it is one of the most faq by newbie,I'm forced to discuss here. I personally do not know sakîndia. If you still want more info, contact senior member hpsgill
You see.. He does nothing without reason. If he doesn't, then the last build present in op will be more /less equal to the latest build. There are other reasons ,which if I had to speak of them all, time wouldn't let me and I would have to deal with flaming members and mods and deleted posts and locked threads . Furthermore that question is well out of the scope of this thread. You are instructed not to ask this question any where.
YOU HAVE BEEN WARNED.
3. How can I contact these developers?
You can by studying Android development and codes, bccms,404s,tr2s and then talking to them. You'll have better luck talking with non recognized developers than the rds.
And try discussion threads .
4. Why doesn't a developer answer my question? (I'm being polite here)
Because the developer doesn't know the answer
w.r.f to http://forum.xda-developers.com/showthread.php?p=38095857
Or your question has already been answered. Try searching for your question at the least 10 pages back.
or your question is too silly to answer
Or your question is not seen ,because they don't have time .
5. Why do they do this ?
For passion of development, addicted, and for learning purposes.
So, that means they don't work for you. They don't help you. They do what they want.
6. I feel a emptiness around forum members. Was there a developer who worked here, yet left without goodbye?
Well not sure about goodbye, but yes his name is jaggyjags.
sakIndia123 came only late and his first work his cranium kernel, which he abandoned like it was nothing.. buried it along with jags. Cruel things did happen before you were here.
Go back to main ^|^
Members:
1. Why won't members answer my question?
Again, thanks to bhargz16
http://forum.xda-developers.com/showthread.php?p=38095857
Or question has already been answered over and over again. Try searching for your question and read at the least 10 pages back.
Or they don't want to help you
Or may be you aren't polite
Or they want thanks
2. Why do they want thanks?
You see.. you should hit thanks for them in order for them to reply
3. Why hit thanks?
Because they are thankaholics .
This addiction
Some call it want,
For some it's need
Some call it greed
And some call it hunger
And some childish foolishness
Never hit thanks, unless you mean it. Never sell yourself short. Mean it, then hit it.
http://forum.xda-developers.com/showthread.php?p=32867800
My first thread closed by mods
:crying:
Having said that, please do be grateful for what you receive. Hitting thanks is like giving a eternal reputation mark on them rather than just saying it. Saying just makes a temporary mark. Get it. 
4.what is spam?
Spam is going out of topic . It never should be done in dev threads unless thread is dead.
Some do the work of mods pretending to be mods.
5.who are mods?
They are moderators who have power to ban anyone at will (in short )
And they are losing patience
http://forum.xda-developers.com/showthread.php?p=37950595
6.Can I spam here?
Feel free to speak what you want..
7. If I feel something wrong is going on /flaming /threatening, who should I report to?
You can use the report system~that (!) mark over every post. Click it and your issue will be resolved within a hour(probably ).
Go back to main ^|^
[color="red"] [b]
0110…380“30…4010¨¨1WELCOME TO NAND/recovery BURNT ZONE 0110…380“30…4010¨¨1
0„30†2Moved by touch0160†640„30†3Inc.
0110…380“30…4010¨¨1DON'T FLASH AN RUU AT ANY STAGE 0110…380“30…4010¨¨1
0. What's burnt nand?
It's condition caused by overclocking(oc)[CPU oc ,to be specific. For gpu oc,go to the last part of this post question 10 ] resulting in bad blocks all over your system, data, cache and recovery.
Important: Use diskusage app to determine size. Don't go by phone's inbuilt settings
A case of burned /system partition in cm10 beta6 running overnight:
Uploaded with ImageShack.us
A late case of burnt nand of /data :
Uploaded with ImageShack.us
1 &2:Not applicable anymore. Peace!
3. No one has burnt thier nand*it's just some people think that thier nand is burnt * is this true?
Well, I'm sure, going through the forums and q &a ,I know that people have indeed burnt thier nands and some just by using the overclocked kernel without even overclocking.
Sources:
http://forum.xda-developers.com/showthread.php?t=1847002&page=400
http://forum.xda-developers.com/showthread.php?t=2243719
http://forum.xda-developers.com/showthread.php?p=39985385
http://forum.xda-developers.com/showthread.php?p=39799173
http://forum.xda-developers.com/showthread.php?p=39439861
http://forum.xda-developers.com/showthread.php?p=39428922
http://forum.xda-developers.com/showthread.php?p=39402187
http://forum.xda-developers.com/showthread.php?p=38941663
http://forum.xda-developers.com/showthread.php?p=39216556
http://forum.xda-developers.com/showthread.php?p=38945489
http://forum.xda-developers.com/showthread.php?p=39197918
http://forum.xda-developers.com/showthread.php?p=39169697
http://forum.xda-developers.com/showthread.php?p=38657723
http://forum.xda-developers.com/showthread.php?p=40616272
http://forum.xda-developers.com/showthread.php?p=39331139
But below is a strong correlation with bad block proof between overclocking and burnt recovery. Yes it burns recovery too.
http://forum.xda-developers.com/showthread.php?p=39196574
THE ABOVE LINKED POSTS ARE MOSTLY SOLVED BY ME OR SENIOR MEMBER S, BUT SOME HAVE LOST THEIR DEVICES. IF YOU CAN'T FIND THE ANSWER HERE, I SUGGEST YOU READ ALL THE LINKED POSTS-VARIOUS DIFFERENT METHODS HAVE BEEN EMPLOYED.,WHICH ARE TOO LONG TO EXPLAIN HERE. READ AND READ-YOU'LL FIND.
4. What are the symptoms of burnt nand?
Early symptoms:
You'll notice a strong drop in your free space in /data
Late symptoms:
/data free space is Nil /below 50%of what you saw before
Error in /cache /recovery/log.
Error in /cache/recovery/last log.Not readable.
No apps can be installed
Rom lags like hell
No Rom can be flashed /boots
Previous nandroids ,which are successfully restored before fails to restore now.
Really abrupt and fast restores with twrp
RUU cannot be done ~user data(mtd5) fail. System fail (mtd3)
5. How can I diagnose burnt nand early?
If you suspect burnt nand ,
1.Watch out for free space in /data and watch out for sharp reduction.
2.Download this app Disk Usage and watch out for increase in system data in /data
http://forum.xda-developers.com/showthread.php?p=39464989
3.Make a dmesg and look for these errors
http://forum.xda-developers.com/showthread.php?p=36834988
4.Definitive method is this :
shahrooz_ra said:
hello
is there any linux terminal command for check badblock on nand memory?
Click to expand...
Click to collapse
1.DOWNLOAD THE TERMINAL.ZIP ATTACHED BELOW
2.EXTRACT TERMINAL.ZIP INTO /SDCARD/lol [create a folder named lol[small letters ]in SDcard, if there already isn't one ]
3.Open terminal emulator on your phone
4.type or copy and paste this code and press enter
Code:
su
cp /sdcard/lol/runme.sh /r.sh
chmod 0755 /r.sh
/r.sh
5.if it doesn't work first time, paste twice.
6.If pasting twice doesn't work, type each code one by one -you'll surely get it. Come on-its just 4 lines -type it lazy!
And Now you'll see the number of bad blocks you've got.
You can also Flash the zip below[for which you have to go to recovery ]or execute the attached script badblocks.sh as root.
6. What are the parts affected by burning?
Proved to affect
/Data
/system
/cache
/recovery
Rest is unknown
7. Ok I managed to burn my nand What are the recovery procedures available?
I SIMPLIFIED THINGS HERE BY MAKING A FLASHABLE FLASH_ERASE. ZIP[Code named FLASH_ERASEmadeflashablebyBANNED.zip ] it works with twrp2.5 to flash_erase needed partitions. However not tested fully. Problem? Post here.
Other long procedures:
Cute prince recovery procedure:
http://forum.xda-developers.com/showthread.php?p=36868966
I think Cute prince missed this .Just add this at the end
Code:
./flash_erase -N /dev/mtd/mtd3 0 0
7.1 I GET FLASH ERASE NOT FOUND?
Flash the flash_erasemadeflashablebyBANNED.zip
Derefas recovery procedure:
derefas was the one who actually gave the idea of recovering nand
http://forum.xda-developers.com/showthread.php?p=36867557
Sachin Thomas recovery procedure
Developed lately *can be done on phone itself */if it didn't involve recovery /*
http://forum.xda-developers.com/showthread.php?p=38941897
Recovery recoveriNG procedure (bhargz16)
http://forum.xda-developers.com/showthread.php?p=39198068
8. I can't find my answer here?
Go to official burnt nand discussion thread
http://forum.xda-developers.com/showthread.php?t=2183130
Or you can ask your questions here.
9.can I Flash any other kernel to prevent overclocking?
You can Flash garuda2.6
Link in latest links post page 1.
http://forum.xda-developers.com/showthread.php?p=38098567
Side effects:
http://forum.xda-developers.com/showthread.php?p=39452607
10. Some more links:
Unknown recovery procedure
http://forum.xda-developers.com/showthread.php?p=36836090
MTD status report:
http://forum.xda-developers.com/showthread.php?p=36837173
11. Cannot go to recovery /burnt recovery /unable to flash recovery?
Not sure of the exact command,but will work.
Use
Code:
fastboot boot recovery /sdcard/twrp5.img
or
Code:
fastboot boot recovery.img
or
Code:
fastboot boot /sdcard/twrp5.img
You need twrp5.img or recovery.img present in /SDcard and renamed like that itself.
After booting into recovery, you can do everything you please. ~flash erase format and install new Rom and boot the device [do ruu here, if you haven't been able to enter hboot before]
After booting up the device, flash erase mtd1 through terminal emulator.and then flash a suitable small recovery. And then pledge here that you'll never overclock ever again.
12. GPU OC ?
gpu oc has been reverted along with CPU oc by sak for burnt nand. But may be added later. but not present in cm released on or two months before 9 may13.
12.1 is it safe?
I don't know. CPU oc did provide burnt nand and bad blocks. Gpu oc may also do some things, which may not be seen as of now. I've seen one case complaining that, after using Cyanogen and going back to stock - games started lagging, which did not lag, when he was in stock before. The reliability is doubtful. But not much people go back to stock either -so not much can be said.
12.2 do you recommend it?
"If any provider of any oc removes the "AS IS" tag and take responsibility,if something happens, then I'll probably may use that oc,otherwise count me out".
12.3 How to remove gpu oc ?
Its present in kernel. Flash another kernel. Or modify source and compile yourself.
Present at arch/arm/mach-msm/msm7x27a.c- kernel source.
Try here
Normal [bus, Gpu] is [0,133330000],[160000000,192000000],[200000000,245760000] I think.
13. Was there anyone unable to recover and lost thier device for ever?
AFAIK,
"The lost thier device for ever list RIP "
Ghostking
Hawk378
And May be many more
Legend *:
Attachment list:
***********************************************************VERY IMPORTANT : UNDER CLOCK BELOW 300MHZ ,IF YOU ARE USING ZIPS WHILE SYSTEM IS RUNNING.AFTER THE TESTS, YOU MAY OVER CLOCK AS YOU WISH. ********************************************************************************************
Provided "AS IS"
1- script to detect badblocks by banned.
2-flashable zip to detect badblocks by btfb0
3-Terminal method to detect bad blocks by banned .
4-flashable zip to detect bad blocks by banned.
5- Recovery procedure to delete bad blocks- Made flashable by BANNED.
All zips posted here has readme.txt files inside it-which are self explanatory to that particular zip.
*USE AT YOUR OWN RISK*
Re: [faq][newbies only][mini edition]
I have a question not answered here?
Post your question in the q&a section after making sure that your question hasn't already been asked.
Please use search button on the top right to make sure that your question hasn't already been asked. And it'll help you to find more answers.
Follow detailed instructions here
http://forum.xda-developers.com/showthread.php?p=33608527
And post with logcat increases your chances of resolving the problem
ADB
What is logcat and ADB?
Special thanks to akshat.shenoy
http://forum.xda-developers.com/showthread.php?p=37805872
He'll explain things better
Basics of ADB:
http://forum.xda-developers.com/showthread.php?p=9936674
Partition and wipe SD ext with ADB:
http://forum.xda-developers.com/showthread.php?p=38706881
Re: [faq][newbies only][mini edition]
reserved
Re: [faq][newbies only][mini edition]
MINI Tips and tricks:▶?
1.How can I apply cm9/10 themes?
http://forum.xda-developers.com/showthread.php?p=35530897
Download the zip from here, read instructions there and flash it in recovery
Now you can use any HDPI themes on your Pico
Thanks ngoloralph
2. How do I change fonts?
Download Rom toolbox lite and go to font installer;
A. If you're on stock, the rest is automatic
B.if you're on cyanogen 9/10/11,if you change the droid sans /others as recommended by app, you'll end up in boot loop (possibly because of symlinking of robot sans & droid sans )
In such a case go to preferences and click to overwrite only roboto regular font and everything will be fine.
Take a look
Uploaded with ImageShack.us
3. How do I add a new language support to my device?
Note: no new language gui can be added by this method. This only adds support. Instead of seeing boxes, you may see your language. If you want full language support, you can go to this abandoned thread.?? http://forum.xda-developers.com/showthread.php?p=40890599 ??
Language support can simply be added by adding a Android supported language font file in /system /fonts and give it permissions rw r. r.(font files can be found all over xda )
Step 2. Open system /etc /fallbackfonts.xml...
There should be a lot of font file names there.. just delete a font name that you don't want and add your font file name (the name of the file which you put in /system /fonts)
In there.
Practice makes perfect.
This method however doesn't work /only partly works for complex languages /script like Hindi Arabic etc.
DID YOU KNOW?
1. Long pressing reboot button (in the menu after pressing power key) will get you into safe mode
2. Long pressing power keys and volume keys + and- for more than 30 seconds will reboot your device (tk to hrkh83)
3. Repeatedly pressing certain options(like Android version) in the about menu in settings(on cyanogen ) will take you into different settings (tk liverpoolfan)
Go back to main ^|^
Battery drain
BATTERY DRAIN
Of course, we're gonna talk about drain.
Before we start, I want to disprove some prevalent concepts
1. Battery calibration
It is supposed to increase Battery capacity and increase Battery life and it makes your phone to show the correct Battery on the notification bar.
FALSE
It doesn't do any of those. Calibration is just deleting Batterystats.bin file. That file holds info about how many seconds each apps were running for.typically it's blameometer. It shows the information you see in the battery chart in your settings. Nothing more.
Source: article
2. Cycling your battery life from 0 to 100 and 100 to 0 will typically increase Battery life. Further more you should make sure it comes to zero by turning on the phone,every time it got switched off on it's own.
FALSE AGAIN
Nothing could destroy your Li-On Battery than extreme low voltage. You can be sure that this will destroy your battery life more than anything. During storage it's recommended to keep the battery in cool place with 40%Battery.
So, don't use any battery draining app from market.
Ok, since we took out the false foundation, it's time to put some true working tips to save your battery during usage and it's overall life
1. It's recommended to charge as often as possible ~every time you get a socket. Though not to keep @100 all the time. Overcharging theoretically may damage your battery, but your phone comes with various safety mechanisms to prevent charging after that.
2. Limit the number of apps. Definitely would produce good Battery.
3. Limit the number of apps, that run in background all the time.
Typical example would be facebook.
PERFORMANCE:
4.Disable autostarts for all apps, that you don't use much~using autostart manager.
Disabling autostarts for the clock app will make you get up late. Use common sense.
This alone should drastically improve your performance
5.Use lightweight launchers ~Nova.
Go (any go products) is not advisable
6.Post ICS, Disable media scanner receiver.
You can use elixir app to disable media scanner receiver. This will scan your SDcard over and over again resulting in Battery drain,which is significant, if you use a bigger SD. Use media scanner root to enable and disable.
As far as the usual ones,
7. Disable autobrightness
8. Keep screen @ minimum brightness
9. Disable autorotation
10. Disable location services.
GAPPS:
11. Disable GSF (google services framework ) receivers ~the ones with gtalk on it.
12. Disable auto sync
You can use timedo /timer Android to turn on sync twice /thrice daily.
13. Reduce number of accounts. Better to keep single than three accounts.
14. Good internet connection. Amount of energy taken to re connect is supposed to be far more than amount needed to keep a connection.
15. Undervolt/with underclock
RECOMMENDED APPS:
1.BETTER BATTERY STATS ~free for xda.
2. Onepower guard
I haven't found satisfying results with this app, but still try it out
3.greenIFY
I haven't used this @ all.
4. Any app, that is used to reduce /increase heartbeat sent to google servers.
Well, that's all I've learnt as of now.
Re: [faq][newbies only][mini edition]
Recommended apps section (only free)
Top apps
0. Superuser by koush (Clockworkmod)
1. Titanium backup
2. Efficient backup
3. Floating logcat ~logcat extreme
4. Catlog
5. Aroma file manager (recovery use only)
6 .Es file explorer
6.1 es file explorer v2
7. Yaffs file manager
8. App extractor
8.1 nandroid manager
9. Loaderdroid
10. Xda app
11. Elixir (much useful to disable app components than it's actual use)
12. Android pro widgets(similar to HTC friendstream)
13. Nova launcher
14. Timedo
15. Live logcat lite
16. Rom toolbox lite
17. Screen stand by root(turn off screen without making phone to sleep)
18. Disk Usage
Launcher:
1. Nova
2. Apex
Downloaders:
Loaderdroid
Multimedia players:
Video
mx
bs
qq
Audio
Ttpod
Equalizers
NOOZOXIDE REWIRE PRO
Walkman sound enhancements
Awesome beats
Cyanogen Dsp(better than stock )
Equalizer from market.
Cam/corDer /video recorder:
Camera:
Camera 360
ucam
spycam
Video recorder
ucam
Zoom camera
Camera magix
Browsers:
Fast and server based
Uc browser mini
Opera mini
Opera mobile
uc browser
Puffin browser
Full fledged browsers
Firefox
Dolphin
Google chrome beta
Chrome
KEYBOARDS ?
Touchpal keyboard
mĺ has internet permisn wid emoji
Office apps:
Kingsoft office(better than paid apps)
Zip extractors:
Zarchiver(ant-one)
Screen off(w/wake lock):
Screen stand-by
File managers:
ES explorer
Fx file explorer
Call recorders:
No known call recorders are working.
Stocks:
Personal finance
Superuser:
Superuser by koush ~open source&free
Super su ~made pro free after the release of prior~closed source ~
⇧Go back to main ♠
THE END.
© All rights reserved 2013?
Autoramdisk exchange alpha
MINI ADVANCED SECTION:
KERNEL RAMDISK exchange on Android itself:wip
AUTORAMDISK™ EXCHANGE PROJECT alpha™
『Moved by touch™』Inc.
In association with
Google Nose beta™
Presents
AUTORAMDISK™ EXCHANGE PROJECT alpha™
Current version: 0.0.0.0.071 Alpha
Created with Es explorer 1.6
Created on HTC explorer Pico a310e
Update:
I have got it to work and complete
http://forum.xda-developers.com/showthread.php?p=40035607
Old post: too lazy to delete
Present condition:
Hi. I cannot get it to work on HTC Pico yet .It may work on other phones. If someone can, please feel free to complete it provided you give proper credits And you do not make money out of this.
What's this?
It's a procedure (wip) to Flash any kernel without the need to change ramdisk.
As new kernel gets released, you don't need to change ramdisk to suit your Rom.
Automated procedure:
Open any kernel.zip with any zip extractor on your phone
Copy the script below and paste it in updater-script present in meta~inf/com/google/Android
(delete any other things written there. )
Code:
package_extract_dir("bin","/tmp");
set_perm(0, 0, 0755, "/tmp/busybox");
set_perm(0, 0, 0755, "/tmp/unpack-bootimg");
set_perm(0, 0, 0755, "/tmp/mkbootimg");
set_perm(0, 0, 0755, "/tmp/dump_image");
run_program("/sbin/dump_image","boot","/tmp/oldboot.img");
run_program("/tmp/unpack-bootimg", "-i","/tmp/oldboot.img","-o","/tmp");
package_extract_file("boot.img", "/tmp/boot.img");
run_program("/tmp/busybox", "mkdir","/tmp/boot");
run_program("/tmp/unpack-bootimg", "-i","/tmp/boot.img","-o","/tmp/boot");
run_program("/tmp/busybox", "rm","-r","/tmp/kernel");
run_program("/tmp/busybox", "mv","/tmp/boot/kernel","/tmp/kernel");
run_program("/tmp/mkbootimg", "--ramdisk","/tmp/ramdisk.cpio.gz","--kernel","/tmp/kernel","-o","/tmp/newboot.img");
write_raw_image("/tmp/newboot.img", "boot");
delete_recursive("/tmp/newboot.img", "/tmp/boot", "/tmp/oldboot.img", "/tmp/kernel", "/tmp/ramdisk.cpio.gz","/tmp/boot.img", "/tmp/busybox", "/tmp/unpack-bootimg", "/tmp/mkbootimg");
mount("yaffs2", "MTD", "system", "/system");
package_extract_dir("system", "/system");
Download zip files from the source link below
Extract it and copy the bin folder from there to your kernel folder directly.
There should be 3 folders in your kernel folder ~bin folder, meta inf folder, system folder and boot.img
Now compress it and Flash
Note that this is only applicable to change ramdisk. If the boot. Img needs more work than that, it won't work. Essentially, it won't work on sense4 compiled kernels and vice versa
Manual terminal emulator method:
Alright guys, one last tutorial from me making my last mark here .This tutorial is not tested fully and probably never will be due to lack of time. And it will work for sure ~but May have syntax errors.
Credits:
1.trevd for arm executable binaries.
2.Xda university.
Requirements:
1.Any Android 2.3+ rooted
2.Android terminal emulator
3.arm executable unpack-bootimg binary and mkbootimg binaries (find it below )
History:
I wanted to change ramdisk for kernels for a long time on phone itself ~probably for a year or more . But anyone who tried to unpack using normal unzip apps would've noticed that other data.img and even system.img in clockworkmod could be unpacked easily, but not the boot.img and recovery.img. When I searched to unpack, it was easy with computers using the unpackbootimg binary for Linux. Problem was it wasn't cross compatible with our phones . So, I was searching for quite a while,until I found trev on xda university and he had made arm executable binaries for unpacking, repacking. Actually the main reason these binaries were created was for far greater and more advanced purposes i.e. to use apply patch functions in update binary and update script to Flash ramdisk on phone without flashing the kernel itself or vice versa (AFAIK)[ The apply patch functions are used in normal ota updates for any Android phone ]. Anyway I took those binaries to unpack kernels on our phone to change ramdisk. I write this for those, who want to change ramdisk on thier phone, but had no experience in PC whatsoever. And also by doing this, I share the unpack boot image binaries by trevd for Android phone ,so that any advanced member May use it for kernel updater scripts~think about it ~one zip for all cm9/10/10.1. Ofcourse the rest is up to you. Thanks for reading
Procedure:
1.Download the zip given in source below
2.Unpack it
3.Find these two binaries in /system/bin
Unpack-bootimg and mkbootimg
4.Copy them to /system/bin and give them full execute permissions in es explorer and read/write permission for user.
5.For easy remembrance,say, b1.img is your original boot image for your Rom(and Android,say cm10 ) and b2.img is the new kernel released for cm10.1
6.You want to change the ramdisk ofb2 cm10.1 to cm10 ,so that you can Flash the new kernelb2 for your cm10
7.Create new folder in SDcard named boot and put both b1.img and b2.img there
8.Open terminal.
9.type the following code one by one
Code:
su
cd /sdcard/boot
mkdir /sdcard/boot/b1
mkdir /sdcard/boot/b2
unpack-bootimg -i /sdcard/boot/b1.img -o /sdcard/boot/b1
unpack-bootimg -i /sdcard/boot/b2.img -o /sdcard/boot/b2
rm /sdcard/boot/b2/ramdisk.cpio.gz
mv /sdcard/boot/b1/ramdisk.cpio.gz /sdcard/boot/b2/ramdisk.cpio.gz
mkbootimg --kernel /sdcard/boot/b2/kernel.img --ramdisk /sdcard/boot/b2/ramdisk.cpio.gz --base 12C00000 -o /sdcard/b2new.img
rm -r /sdcard/boot
Note: the last rm command will delete all your old kernels ~don't execute it, if you don't want to have it deleted.
10.Now you have new kernel boot image with your ramdisk in /sdcard/b2new.img
11.Put it back in the zip with it's modules and
12. Flash
13.Hoping it'll work.
14.That's the end.
Source and binaries here:
http://forum.xda-developers.com/showthread.php?p=36931024
For dream and Sapphire models, you can use the binaries created by koush ~ which is found in his github ~any kernel project.
I'll probably be leaving soon
Kind of feel like working for xda. I guess sak and others would probably feel like it later. It's been great while it lasted. So this is probably my last project. If I did have some extra hardware during this period, things May have been different. It's good, while it lasted.
"The fantasy of a dream is that, it's still a dream, when it becomes reality, then it's no more a dream and the fantasy is lost. "
「Good bye xda」
So long:angel:
Re: [faq][newbies only][mini edition]
one more
The Infamous BUILD.PROP Tweaks :
http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/
from
http://www.droidforums.net/forum/droid-4-roms/234899-examining-build-prop-tweaks.html
Guess that'll end this hoax for good.
One thing that was useful for me was this
http://www.modaco.com/topic/347274-guide-making-cm-utilise-both-cache-and-data-for-dalvik-cache/
[ROM]●●[TF700T][miniCROMi-X 2.0.1][JB 4.2.1 | OC | OV | DEODEX 10.6.1.27.5][FEB 14]●●
miniCROMi-X ROM - Lite version of CROMi-X with ROM2SD support
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Changelog
miniCROMi-X v2.0.1 - Released 14/02/2014
o Fixed installer script not waiting for /system to become available before attempting to mount
o Updated Super User to version 1.93
o Updated Google Core Services to latest version
miniCROMi-X v2.0 - Released 30/01/2014
o Updated Framework-res to version that doesn't need cromi-control installed.
o Recompiled framework-res.apk with TF701T default wallpaper. Goodbye Asus Tree
o Reverted services.jar and framework.jar to pre cromi-control versions
o Removed cromi-control
o Modded SystemUI.apk and Transformer.apk to remove sd card and dock notifications
o Updated LMK's Extreme Tweaks to version 1.6
o Updated LMK's init.cardhu.rc for ROM2SD compatibilty for better kernel integration
o Modified MiniC Launcher to 3 screens, new default wallpaper, 9x6 icons on 4.2 and removed screen indicators
o Updated Superuser and binary to latest version 1.91
o Moved Flash Player to /data/app
o Updated Google Play services and keyboard to latest versions
o Fixed Google Keyboard not defaulting on clean install when Asus keyboard is not installed
o Updated Hosts file
o Zip Aligned all system apks
o Changed Bootanimation to TF701T Stock
Click to expand...
Click to collapse
Old Versions:
Code:
[B]miniCROMi-X v1.3 - Released 01/12/2013[/B]
o Updated LetMeKnow's tweaks to v1.3
o Updated SuperUser and Binary to version 1.80
o Updated Google Play Services to latest version
o Updated Google Keyboard to latest version
o Updated Normal install so it doesn't install ROM2SD compatibility anymore
[B]miniCROMi-X v1.2a - Released 15/11/2013[/B]
o Fixed missing popup search bar when holding on text in v1.2a
o Applied LetMeKnow's power saving build.prop edit to assist fixing WiFi slowing down
o Fixed the missing Settings Status which was cauing force closes
o Removed facelock app, lib and face detection models from ROM
o Removed blocklayoutdriver.ko as not used
o Removed libereader.so as no Asus Reader app included
o Fixed keyboard permissions
o Updated SuperUser and SU binary to version 1.69
Created Patch for Asus Keyboard which fixes dock layout for non-US models
B]miniCROMi-X v1.1 - Released 10/11/2013[/B]
o Name changed to miniCROMi-X or miniC for short ;)
o Calendar sync adapter added to allow Google Calendar to sync properly
o Updated Google Play Services to version 4.0.31
o Updated Google Keyboard to version 2.0.18933.905102a
o Removed GoogleBackupTransport.apk, GoogleFeedback.apk
o Added Keyboard.apk back in for Dock compatibility
[B]CROMini-X v1.0 - Released 04/11/2013[/B]
o Name changed to CROMini-X
o Aroma-less - normal installer - no options - 2 versions - normal and rom2sd
o Massively debloated ROM. Half the size of CROMi-X. Most Google and Asus Apps removed - should have 500MB free RAM on boot
o ROM2SD compatible. You need 2 Ext4 partitions on your MicroSD for it to work. Thanks to _that
o CROMi-X Extreme tweaks and CROMI-CONTROL app installed by default
o Applied LMK's ET 1.1, hotplug interface set to 0,0,0. Quadrant on perf should be around 7000 and stable
o Updated Hunds app to version 2.4
o Added newer implementation of BusyBox that has better compatibility from trickster mod site
o Removed email widget and task manager widget
o Removed all wallpapers from Launcher apart form TF701T default - now only 5mb :)
o Resized Google Boot Animation
o You can install most add on apps from the store and use titanium backup to move to /system if you wish :) Or just install CROMi-X ;)
Credits to _that & Hundsbuah for the kernel and LetMeKnow for the kernel tweaks and elesbb for CROMi-Control
Remember you must have a fast microSD card formatted with a fat32, ext4 for /data and ext4 for /system in GPARTED for Rom2sd.
1. You need a fast microsd card - preferably at least a 16GB Class 10 - UHS-1 card like a sandisk or Samsung with a read speed of over 20MB/s
2. You need to use Linux or how I did it a GParted ISO on a Bootable USB Stick on a PC
3. In GParted set up your micro sd with 3 partitions all primary (no logical) in this order FAT32, EXT4, EXT4
They will be used as SDCARD, /data, /system in that order so I recommend the following sizes for a 16GB sdcard; 4GB for SDCard, 11GB for /data and 1GB for system or thereabouts.
If you used a 32GB or 64GB card then increase the SDCard and /data partitions as you see fit (I went with 16GB, 47GB and 1GB on my 64GB card)
4. The ROM now flashes the correct preinit script files to your normal system setup so as long as you have a _that or hunds based kernel it will detect your ROM2SD automatically
5. Install the ROM2SD version and let it finish. Let it reboot.
6. You should be presented with a clean install setup wizard when it boots if it has worked. If it hasn't worked you will be back at your previous CROMi-X/miniC installation launcher.
7. Job done - set up your ROM2SD however you like - it can't interfere with your normal setup
8. You will notice 2 folders on root - datai and sdcardi - these allow you to see your internal /datai and sdcardi partitions if you wish to copy files over
9. As long as the SDCard is inserted you will boot to ROM2SD, remove it (not whilst in android unless you want to crash) and on that boot you will switch back to your normal miniC or CROMi-X if you installed that to SD.
DOWNLOADS
miniC Normal Download
miniCROMi-X DEODEX v2.0.1_Signed.zip - 230 MB - Mirror 1
miniCROMi-X DEODEX v2.0.1_Signed.zip - 230 MB - Mirror 2
md5: 2362a85541f1ac6adc448397b26e1bf2
miniC Rom2SD Download
miniCROMi-X DEODEX v2.0.1_ROM2SD_Signed.zip - 230 MB - Mirror 1
miniCROMi-X DEODEX v2.0.1_ROM2SD_Signed.zip - 230 MB - Mirror 2
md5: 957a38f97109a2243756b473db3f924e
For those of you missing the dock layouts for your language please flash this patch. It will install the necessary files so you can set the dock language in the Asus Keyboard which dictates what the dock should use
Download Asus Keyboard Patch
md5: bee82d0e73ac0d5b2185417fa416e0a9
Use this patch if you want to remove the google keyboard.
Download Google Keyboard Removal Patch
md5: efcc6216af60feb7cba8dfab72daeac8
If you want to backup and restore to your ROM2SD setup flash the following file first in TWRP as it shifts TWRP to see the microsd as internal. Flash it again to return back to internal. All credits to _that for that
ROM2SD1.zip - 144 KB - Mirror 1
md5: 7b699136d59ea3d5538570ccaf422acf
XDA:DevDB Information
miniCROMi-X, a ROM for the Asus Transformer TF700
Contributors
sbdags, LetMeKnow, hundsbuah elesbb, pjc21, _that, flumpster
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.1.x
ROM Firmware Required: Bootloader 10.6.1.x version compatible
Based On: Asus Source
Version Information
Status: Stable
Current Stable Version: 2.0.1
Stable Release Date: 2014-01-30
Previous Version: 2.0
Previous Release Date: 2013-01-30
Created 2013-11-10
Last Updated 2014-02-14
miniC Addons
miniCROMi-X Add Ons
Kernel & Tweaks Installer - DOWNLOAD
Kernel & Tweaks Installer v5.2 - Updated Jan 06, 2014
For those who want to switch Kernels quickly, enable data2sd, rom2sd, cache2sd, change DPI, change res, disable / enable fsync and other tweaks
Note for Data2SD and Rom2SD you must have the correct ext partitions on your external sd card. See instructions here
Kernels:
TF700T : ASUS 10.6.1.27.5 Stock Kernel by sbdags
TF700T : _that 10.6.1.14.8 Modded Stock Kernel v4 Data2SD Compatible, Row Scheduler, UV, CIFS, ISO9660 and Fsync Control. By _that
TF700T : _that 10.6.1.14.10 Over Clocked Modded Stock Kernel v7 Rom2SD, Data2SD Compatible, Row Scheduler, UV, CIFS, ISO9660 and Fsync Control. By _that
You will have 3 options for Kernel CPU Speeds, all with GPU at 650MHz:
1518 - Power Save 1GHz, Balanced 1.5GHz, Performance 1.8GHz
1315 - Power Save 1GHz, Balanced 1.3GHz, Performance 1.5GHz
1318 - Power Save 1GHz, Balanced 1.3GHz, Performance 1.8GHz
TF700T : Hunds 10.6.1.14.10 Modded Kernel v3.4.4 BETA - Rom2SD, Data2SD Compatible, Overclocked, UV, Multi Scheduler, Fsync Control, Tweak App by Hundsbuah
TF700T : Max 10.6.1.14.8 Linaro Kernel Reloaded v4 RC3 BETA - Overclocked with dynamic Fsync Control by maxrdlf95
TF300T/G/TF201/ME301 : ASUS 10.6.1.27.5 Stock Kernel By sbdags
TF300T/G/TF201/ME301 : _that 10.6.1.14.8 Modded Stock Kernel v4 Rom2SD, Data2SD Compatible, Row Scheduler, UV, CIFS, ISO9660 and Fsync Control. By _that
TF300T/G/TF201/ME301 : _that 10.6.1.14.10 Over Clocked Modded Stock Kernel v7 Rom2SD, Data2SD Compatible, Row Scheduler, UV, CIFS, ISO9660 and Fsync Control. By _that
TF300T : Hunds 10.6.1.8.4 Modded Kernel v11 - Data2SD Compatible, Overclocked, UV, Multi Scheduler, Fsync Control, Tweak App by Hundsbuah
TF201 : Hunds 10.6.1.8.4 Modded Kernel v3.3.2 - Data2SD Compatible, Overclocked, UV, Multi Scheduler, Fsync Control, Tweak App by Hundsbuah
TF300T/G/TF201/ME301 : Max 10.6.1.14.8 Linaro Kernel Reloaded v4 RC2 BETA - Overclocked with dynamic Fsync Control by maxrdlf95
TF201 : Max 10.6.1.14.8 Linaro Kernel Reloaded v4 RC3 BETA - Overclocked with dynamic Fsync Control by maxrdlf95
Tweaks:
Data2sd enabling / disabling (only works with _that's and hunds kernels)
DPI Change
Resolution Change (TF700 Only : 1920 x 1200 or 1280 x 800)
Fsync Disabled / Enabled
GPU rendering or CPU software rendering
CPU Over-Volt by 50mV
CPU Under-Volt by 50mV
GPU Under-Volt (hunds only)
Cache2SD (Experimental)
DOWNLOAD Kernel Installer v5.2 Mirror 1
DOWNLOAD Kernel Installer v5.2 Mirror 2
MD5: ae34db3e891f5b96c82a5f124ddf6dc8
==================================================================================================
Various Kernel Benchmarks
Right benchmarks with various kernel options:
All were taken on CROMi-X 5.1 Odex with default options at 240dpi unless otherwise stated (fsync off / on). I've used quadrant as most people understand the results - I know it's not the best and I did 3 tests each time and took the 3rd result.
Stock - fsync on - 5672
_that v4 - fsync off - 5981
_that v4 - fsync on + data2sd - 5745
_thatv5 - fsync on - 6267
_that v5 - fsync off - 6414
_that v5 - fsync on + data2sd - 6143
Hunds + ET - fsync on - 6684
Hunds + ET - fsync off - 7245
Hunds + ET - fsync on + data2sd - 6725
Hunds - fsync off - 6805
Hunds - fsync on +data2sd - 6597
So data2sd doesn't really offer that much if you keep fsync on. It does feel faster when loading large games and files. The issue is it is a bit more unstable and easier to corrupt the data partition if you have fsync off. Same risk with normal data I suppose but less likely to corrupt due to less sponteneous reboots.
Is data2sd worth it? Only if you want to use your tablet whilst downloading large files or play store updates or you are prone to corruption with fsync off. Otherwise you can achieve at least the same speed with fsync off although with a risk to corrupt your data partition eventually.
Uh,uh! First one! :cyclops:
Let's set an example: Transaction ID #7FL985280X445515J
Thanks Darren!
berndblb said:
Uh,uh! First one! :cyclops:
Let's set an example: Transaction ID #7FL985280X445515J
Thanks Darren!
Click to expand...
Click to collapse
Bernd! Many thanks for the first donation of miniCROMi-X.
sbdags said:
Bernd! Many thanks for the first donation of miniCROMi-X.
Click to expand...
Click to collapse
You're more than welcome!
But could I trouble you for more detailed instructions for thick headed noobs like me on the ROM2SD installation?
I'm good until point 5), but then....
How's the hell do you install mini-X to the microSD?
I understand that once installed on a microSD with the correct partitions the kernel (??) will auto-detect it and boot into the rom installed on the card.
But how do you install? Boot into TWRP with miniCROMi-X on the fat32 partition of the card and just install from there?
I have to admit, it's late and I'm lazy. Just got finished with a clean install of 5.1.2 (which btw is super smooooth so far) and would hate to flash over that if I'm wrong.
berndblb said:
You're more than welcome!
But could I trouble you for more detailed instructions for thick headed noobs like me on the ROM2SD installation?
I'm good until point 5), but then....
How's the hell do you install mini-X to the microSD?
I understand that once installed on a microSD with the correct partitions the kernel (??) will auto-detect it and boot into the rom installed on the card.
But how do you install? Boot into TWRP with miniCROMi-X on the fat32 partition of the card and just install from there?
I have to admit, it's late and I'm lazy. Just got finished with a clean install of 5.1.2 (which btw is super smooooth so far) and would hate to flash over that if I'm wrong.
Click to expand...
Click to collapse
I'm going to get a full guide written mate on how to get the parted iso create a bootable usb and then use it Give me a few days
Also we have an alternative method for ROM2SD from _that that may make it even easier to install
I just tried to install, minicromi -and after twrp installed it, it didn't go into setup... just said reboot. At that point it would simply stick in a boot loop. Tried to reinstall boot loader and will retry. Really want to put all on my new SD card to speed this baby up
Sent from my VS980 4G using Tapatalk
success!
Update: I can avoid the reboots if I pop out my SD card. So. Just installed mini, now will go back to twrp and pop in SD card (partitioned), and try to install rom2sd
Sent from my VS980 4G using Tap a talk
Keep in mind im a beginner!
Few words of advise:
1) I ended up using new cromi 5.1.2
2) you must install twice!!! first without the sd card (i had mine in and it caused problems)- and choose option to set up rom2sd
3) start device- then reboot again into twrp bootloader- and reinstall rom but choose rom2sd now---(now insert sd card!)
first time it crashed after rom2sd- but second time (switched to hunds) and boom...its a miracle...device is awesome!!!
side note- i DID use the micro explorer windows partition tool many said "doesnt work well"- had windows 8 device- worked like a charm.
worth the late night figuring this out.
sdbags- how can i donate! you are the man
Jeffruby said:
Few words of advise:
1) I ended up using new cromi 5.1.2
2) you must install twice!!! first without the sd card (i had mine in and it caused problems)- and choose option to set up rom2sd
3) start device- then reboot again into twrp bootloader- and reinstall rom but choose rom2sd now---(now insert sd card!)
first time it crashed after rom2sd- but second time (switched to hunds) and boom...its a miracle...device is awesome!!!
side note- i DID use the micro explorer windows partition tool many said "doesnt work well"- had windows 8 device- worked like a charm.
worth the late night figuring this out.
Click to expand...
Click to collapse
I've been having a somewhat similar problem. I now tried your version, but I still end up with it upgrading the 87 apps, then it forever stalls at Android is upgrading... with the subtext Starting apps. I've installed it like 10 times, this last 2 times using your method (_that's OC then Hunds), no difference no matter what I try :crying:
It works fine without the card and the Rom2SD compatible option install. During second round Installed 5.1.2 both from internal memory with popping in the card midway, as you wrote and also from the card itself, left in, obviously.
When you make the partitions on the microSD card, do you give it a label or flag. I do neither. I'm at my wit's end... and wife's starting to get pissed off that I'm spending all day on this - again!
Adso3000 said:
I've been having a somewhat similar problem. I now tried your version, but I still end up with it upgrading the 87 apps, then it forever stalls at Android is upgrading... with the subtext Starting apps. I've installed it like 10 times, this last 2 times using your method (_that's OC then Hunds), no difference no matter what I try :crying:
It works fine without the card and the Rom2SD compatible option install. During second round Installed 5.1.2 both from internal memory with popping in the card midway, as you wrote and also from the card itself, left in, obviously.
When you make the partitions on the microSD card, do you give it a label or flag. I do neither. I'm at my wit's end... and wife's starting to get pissed off that I'm spending all day on this - again!
Click to expand...
Click to collapse
I don't understand what problems you guys are having, I have installed this 20 times plus and it works fine every time.
I gave my partitions labels - not sure if it matters.
So you have fat32, ext4 and ext4
You install the rom and you have two choices:
1. You install it without the ROM2SD compatibility and without ROM2SD as you only care about internal. (If you install it with ROM2SD compatibility it is going to try and boot from the SD card but you currently have nothing installed so it will never work - this will force you to have to boot with the card out)
2. You install the ROM2SD (this automatically forces compatibility to internal as well - maybe this is the confusion?). As long as the card is in it will boot to ROM2Sd but only as long as you have CROM-X or miniCROMi-X on internal.....
The only time you need to choose ROM2SD compatibility is when you already have a working rom on sd and you are upgrading internal.
Does that make sense?
So what you meant was:
1) Install it first the good old fashioned way choosing normal mode and let it boot and finish setup.
2) Then do the exact same thing again, only this time with the install Rom2SD option instead of the “normal” option.
Is that correct?
4. You must have already installed CROMi-X with ROM2SD compatibility selected from the installer and have it working - dirty or clean will work.
5. Install the ROM2SD version and let it finish. Let it reboot.
That part 4 sounds like my point 1 but with the compatibility option instead which you say don't work, hence the confusion.
I install two different boot animations so I can see where it's booting from. My point 1 is done and all good. Then I did point 2 and just like before it starts just fine, but then ends up stuck at the “Android is upgrading... Starting app.” screen and it never finishes. Last night I just did that too and this morning it was dead and out of battery (started with a full charge).
I'm dying to know what labels you gave your 3 partitions respectively. Since you didn't mention flags, I'm guessing you didn't flag one as boot for instance. This would be a really quick to change and see it that is where the dog lies burried.
Thanks for your quick reply btw. Mine a bit late as I just had to try out your suggestions.
Adso3000 said:
So what you meant was:
1) Install it first the good old fashioned way choosing normal mode and let it boot and finish setup.
2) Then do the exact same thing again, only this time with the install Rom2SD option instead of the “normal” option.
Is that correct?
4. You must have already installed CROMi-X with ROM2SD compatibility selected from the installer and have it working - dirty or clean will work.
5. Install the ROM2SD version and let it finish. Let it reboot.
That part 4 sounds like my point 1 but with the compatibility option instead which you say don't work, hence the confusion.
I install two different boot animations so I can see where it's booting from. My point 1 is done and all good. Then I did point 2 and just like before it starts just fine, but then ends up stuck at the “Android is upgrading... Starting app.” screen and it never finishes. Last night I just did that too and this morning it was dead and out of battery (started with a full charge).
I'm dying to know what labels you gave your 3 partitions respectively. Since you didn't mention flags, I'm guessing you didn't flag one as boot for instance. This would be a really quick to change and see it that is where the dog lies burried.
Thanks for your quick reply btw. Mine a bit late as I just had to try out your suggestions.
Click to expand...
Click to collapse
Yes 1 and 2 are how I normally flash it. In fact I just did it again tonight and it worked fine.
4 and 5 (what happened to 3? ) will also work.
I'll think about the installer next time to make it a bit more obvious.
You don't need to flag anything - only primary partitions. Don't need to set boot flag.
I labelled mine like this:
FAT32 : STORAGE
EXT4 : SD-EXT
EXT4 : SYSTEM
But you could label them whatever you want.....
Stuck @ "Apps upgrading..." SOLVED!
sbdags said:
Yes 1 and 2 are how I normally flash it. In fact I just did it again tonight and it worked fine.
4 and 5 (what happened to 3? ) will also work.
I'll think about the installer next time to make it a bit more obvious.
You don't need to flag anything - only primary partitions. Don't need to set boot flag.
I labelled mine like this:
FAT32 : STORAGE
EXT4 : SD-EXT
EXT4 : SYSTEM
But you could label them whatever you want.....
Click to expand...
Click to collapse
Not too sure about that just label them whatever part though.
Originally (yesterday) I had it named it Partion 1, Partition 2 and Partition 3. Then today I removed the labels entirely and it still acted funny. Just now I popped in the card, ran GParted and noticed the 3rd partition was given the label SYSTEM during the previous non-functional installation, but the first 2 still had no label. My problem was the apps loading. I noticed the installation seemed longer and don't remember it saying: Optimizing SD-EXT or something to that effect, "installing Dropbox, installling Titanium" etc at the end of all that quickly passing text when I ran the Rom2SD install previously, but I'm so tired right now it might be something I'm just imagining.
All I can say now is that just the fact that I named them exactly like you named yours it now works brilliantly :highfive: and that "apps starting" part took a only a few seconds. It seems the installation, in my case at least, can't figure out that it needs to install the apps to 2nd partition without the label SD-EXT or more likely given the timing of failure, it just fails to load them from said partition.
To anyone reading this, just name your partitions like sbdags does, just to be on the safe side and you're likely naming them anyway, or if not, then it is 1 minute well spent.
I've wiped, installed, booted, setup, etc. on the wrong side of 20 times since yesterday morning and I'm almost in disbelief that it's actually working all of a sudden :victory: and so late that it's now bedtime and I'll have to wait till tomorrow to take the damn thing flyin'
Thanks dude
It's all the good people at xda like yourself that I think of and mention to friends and family as a shining example of hope for the future for the human race when experiencing or hearing about all the ****ty sides of human behaviour from crime to corrupt politicians, terrorists, bigots and just general lack of helpfulness and a willing spirit. It brings me a sense of hope :angel: I've grown quite cynical over the years, but xda is one of the things that keep me from becoming like the old dude in the animated movie Up. :silly:
When Asus (or Samsung etc.) lets you fall, it's comforting to know there's almost always someone here at xda to catch you before you hit the ground.
Good luck and good night fellow Gadgeteers!
I finished just in time to cuddle a bit with the missus before she falls asleep to try to make up for all the time I've been knee-deep in **** with my head stuck between the screen and the keyboard during any free-time in the last two days. :silly:
Adso3000 said:
Not too sure about that just label them whatever part though.
Originally (yesterday) I had it named it Partion 1, Partition 2 and Partition 3. Then today I removed the labels entirely and it still acted funny. Just now I popped in the card, ran GParted and noticed the 3rd partition was given the label SYSTEM during the previous non-functional installation, but the first 2 still had no label. My problem was the apps loading. I noticed the installation seemed longer and don't remember it saying: Optimizing SD-EXT or something to that effect, "installing Dropbox, installling Titanium" etc at the end of all that quickly passing text when I ran the Rom2SD install previously, but I'm so tired right now it might be something I'm just imagining.
All I can say now is that just the fact that I named them exactly like you named yours it now works brilliantly :highfive: and that "apps starting" part took a only a few seconds. It seems the installation, in my case at least, can't figure out that it needs to install the apps to 2nd partition without the label SD-EXT or more likely given the timing of failure, it just fails to load them from said partition.
To anyone reading this, just name your partitions like sbdags does, just to be on the safe side and you're likely naming them anyway, or if not, then it is 1 minute well spent.
I've wiped, installed, booted, setup, etc. on the wrong side of 20 times since yesterday morning and I'm almost in disbelief that it's actually working all of a sudden :victory: and so late that it's now bedtime and I'll have to wait till tomorrow to take the damn thing flyin'
Thanks dude
It's all the good people at xda like yourself that I think of and mention to friends and family as a shining example of hope for the future for the human race when experiencing or hearing about all the ****ty sides of human behaviour from crime to corrupt politicians, terrorists, bigots and just general lack of helpfulness and a willing spirit. It brings me a sense of hope :angel: I've grown quite cynical over the years, but xda is one of the things that keep me from becoming like the old dude in the animated movie Up. :silly:
When Asus (or Samsung etc.) lets you fall, it's comforting to know there's almost always someone here at xda to catch you before you hit the ground.
Good luck and good night fellow Gadgeteers!
I finished just in time to cuddle a bit with the missus before she falls asleep to try to make up for all the time I've been knee-deep in **** with my head stuck between the screen and the keyboard during any free-time in the last two days. :silly:
Click to expand...
Click to collapse
Wow thanks for the kind words! :good: Hmmm.... not sure why labelling them works - I just called them whatever popped into my head......
sbdags said:
not sure why labelling them works - I just called them whatever popped into my head......
Click to expand...
Click to collapse
I didn't label my partitions at all and it worked...
For those of you missing the dock layouts for your language please flash this patch. It will install the necessary files so you can set the dock language in the Asus Keyboard which dictates what the dock should use
Download Asus Keyboard Patch
md5: bee82d0e73ac0d5b2185417fa416e0a9
Use this patch if you want to remove the google keyboard.
Download Google Keyboard Removal Patch
md5: f9a5ad7acbd47b737db2c54e849ee6b8
Seems to be working fine and smooth. Not sure if Browser2Ram is already implemented as standard?
How much screentime is people getting? Seems like the battery drain is bigger, but I have to give more charge cycles before I jump to conclusions.
Great work!
Ali I Hagen said:
Seems to be working fine and smooth. Not sure if Browser2Ram is already implemented as standard?
How much screentime is people getting? Seems like the battery drain is bigger, but I have to give more charge cycles before I jump to conclusions.
Great work!
Click to expand...
Click to collapse
Yes b2r is implemented by default as are hunds kernel with extreme tweaks. This is why your battery life isn't great. This ROM is designed for the speed demons. It comes over clocked and over volted.
Search not working
Hi
I installed the rom yesterday and it's running great thanks! I am having one issue which I would like to be able to fix. When I select text by a long press on the screen the options show up to copy or search web but when I select search web it says Search Via - No apps can perform this action. Is there a app I can add that is missing to fix this?
Thanks
R.
rnormore said:
Hi
I installed the rom yesterday and it's running great thanks! I am having one issue which I would like to be able to fix. When I select text by a long press on the screen the options show up to copy or search web but when I select search web it says Search Via - No apps can perform this action. Is there a app I can add that is missing to fix this?
Thanks
R.
Click to expand...
Click to collapse
I'll have a look.
******************* INFO&CREDITS *******************
I know i've been away from this forum for a lot of time (mostly my Nexus 5 fault ) but when i've seen that F2FS it's now possible on this device i decided to create an easier way to create&use this filesystem,so average users can try it and decide.The best part of XDA is that everyone can contribute in the best way he/she can.
Anyway all credit goes to: samsung (for the f2fs) , Alex Page <[email protected]>, @_that @Dees_Troy (TeamWin ), @dasunsrule32 (cyanogenmod), @Hundsbuah and to everyone who contributed to make this device better.Thank You all!
******************* About F2FS *******************
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk (Hangul: 김재극) at Samsung for the Linux operating system kernel.
The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Samsung chose a log-structured file system approach, which it adapted to newer forms of storage. F2FS also remedies some known issues of the older log structured file systems, such as the snowball effect of wandering trees and high cleaning overhead. Because a NAND-based storage device shows different characteristics according to its internal geometry or flash memory management scheme (such as the Flash Translation Layer or FTL), Samsung also added various parameters not only for configuring on-disk layout, but also for selecting allocation and cleaning algorithms. (source Wikipedia )
******************* WARNING *******************
* Please be aware that F2FS is still experimental and DATA LOSS or other issue may occur.
* You agree to use this MOD on you own risk and i don't take any responsability if you encounter any issue or if your personal data is lost
******************* Requirements *******************
Your tf700t device must be Unlocked
An external MicroSD card or a PC (for backup/restore )
A brain
******************* Preinstalling steps *******************
Backup of your personal data to an external card or PC (photo,music,ringtones,etc)
Create a backup from recovery and store it in a safe place (external sdcard or PC)
Download twrp_f2fs from the Download Section (second post )
Download a kernel from the Download Section (second post) - _that and Hundsbuah are for stock based roms only ; CM11 is for Cyanogenmod based.
Download your favorite rom
******************* Install Steps *******************
1) Install twrp_f2fs recovery using one of the methods bellow
Fastboot method
Code:
fastboot -i 0x0B05 flash recovery twrp_f2fs.blob
fastboot -i 0x0B05 reboot
Terminal/ADB
Save twrp_f2fs.blob to the root of your /sdcard directly (internal memory only).
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
Code:
su
dd if=/sdcard/twrp_f2fs.blob of=/dev/block/mmcblk0p4
and reboot your device
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
2) Reboot to recovery (if the recovery was installed you will see the 4 linux penguins after pressing the RCK button)
3) Enter the WIPE menu and select Format DATA ( warning all your personal data will be lost )
4) Wait until the format is complete then reboot to recovery again (if previous step was succefull your DATA partition is now F2FS )
5) Wipe Cache (Wipe Menu --> Advanced --> select only Cache partition and go)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
6) ROM installation ( you can choose several methods to get your system back and running)
a) if you already have a System installed you can skip to step 7)
b) install your favorite ROM from external sdcard and Reboot to Recovery
c) restore your previous backup from an external sdcard (select only SYSTEM and DATA partitions) and Reboot to Recovery
7) Install one of the F2FS kernels (based on the ROM you have) and REBOOT SYSTEM
Remember that everytime you install a new ROM you have to Reboot to Recovery and install an F2FS kernel.
That's it,the system should boot with an F2FS data partition,start playing with it. :good: :laugh:
******************* Rom2SD_F2FS *******************
NOTE:
In order to use Rom2SD you need to have a running and rooted stock-based ROM with busybox and a kernel with preinit support (_that and hundbuah kernels are one of them
Also make sure there are no residual folders&files from an old Data2SD/Rom2SD setup ( basically delete the /boot folder in /system if there is one)
Partitioning your MicroSD -- > You can find a good tutorial (thx @sbdags) here
**** Install steps ****
Download all the files from Rom2SD section in the Download page ( post #2) and save them on MicroSD
Download a Kernel from the Download page ( choose the correct one depending on your favorite ROM base) and save it to MicroSD
Boot your device in Recovery
Install Rom2SD_F2fs.zip
Install Rom2SD1.zip
Go to Mount option and make sure Data partition is unchecked ,if not,uncheck it and press Home icon to go back to the Main menu (don't press back)
Go to Wipe and press Format Data (this will format your external data partition to F2FS) - if is failing check the Mount option again
Install your favorite ROM (don't reboot)
Install an F2FS Kernel (don't reboot)
Install Rom2SD2.zip
Reboot and enjoy Rom2SD_F2FS
**** Tips ****
If you have a Backup for the Rom installed on external then you can restore your data and avoid the waste of time needed to configure everything again
Boot to Recovery
Install Rom2SD1.zip
Go to Restore and select the desired backup and check only Data
Swipe to restore and then reboot to system
******************* Back2EXT4 Script *******************
Description: This script will help you format the Data partition to EXT4 without the need to change the recovery.
Instructions:
**** Internal Data ***
Download Format Data to EXT4.zip from the download section and save it to MicroSD
Reboot to Recovery
Install Format Data to EXT4.zip --> Warning,your personal data will be lost
Now your data (mmcblk0p8) partition it's EXT4 but you can still use twrp_f2fs
**** External Data (Rom2SD/Data2SD setup) ***
Download Format Data to EXT4.zip from the download section and save it to MicroSD
Download Rom2SD1.zip from the download section and save it to MicroSD
Reboot to Recovery
Install Rom2SD1.zip
Install Format Data to EXT4.zip --> Warning,your personal data will be lost
Now your data (mmcblk1p2) partition it's EXT4 but you can still use twrp_f2fs
*********************************************************************************************************************************************************************************************************************
Note: As you can see there are several ways to get your system up and running after your Data partition was formated with F2FS.Also based on my tests you can use an "old" EXT4 backup to restore on F2FS and should work viceversa too.
I will also update this thread with info on how to go back to EXT4 without changing the recovery,and also i will try to modify the Data2SD/Rom2SD scripts and make them F2FS compatible.
And btw,please kick that THANKs button
Downloads
********************************************************* Downloads *********************************************************
++++++++ Kernels ++++++++
That_F2FS.zip --> MD5 Sum: 1165247d099f5dbd5f5a4d4a848ff186
Kernel_F2FS_Hund_v3.4.5 --> MD5 Sum: 888e71f5fade857ed7a062dc08b36d77
CM11_Kernel_F2FS.zip --> MD5 Sum: e9772d2b8a63a009d0499c43fb93a6db
Build by @sbdags F2FS kernels
++++++++ Recovery ++++++++
twrp_f2fs.blob --> MD5 Sum: 4391cdfac9bf9660f52b8b0081543ea0
++++++++ Rom2SD_F2FS++++++++
Rom2SD_F2fs.zip -- > MD5 Sum: f5629e4fc9c40cbb7590152001de8179
Rom2SD1.zip -- > MD5 Sum: f6a6b0e5f0260078782a86c2e60c664e
Rom2SD2.zip -- > MD5 Sum: e82008368cb8ee663a70e63c6cb10040
++++++++ Back2EXT4 Script ++++++++
Format Data to EXT4.zip -- > MD5 Sum: 7ddbbbbe5d7e3c546c46ab8c185b4a70
********************************************************* Sources *********************************************************
Recovery - build from the official sources available in Omnirom 4.4 tree (android_bootable_recovery)with @that kernel (kernel source ).
Hundsbuah kernel - original kernel from here + modified ramdisk
_that kernel - original kernel from here + modified ramdisk
CM11 kernel - Source + Patch
Pretoriano80 said:
Reboot to recovery (if the recovery was installed you will see the 4 linux penguins after pressing the RCK button)
Click to expand...
Click to collapse
Even if you hadn't told me before, I could guess which kernel your recovery is using.
Thanks for making this package available to all users!
A warning to all potential users of f2fs: There is still no program to repair a corrupted filesystem - fsck.f2fs can only detect corruption but not fix it. Don't store anything important on f2fs.
Do you run into any issue with this f2fs so far?
LetMeKnow said:
Do you run into any issue with this f2fs so far?
Click to expand...
Click to collapse
Nope, no issue so far. At some point i was afraid that internal storage will die on me with all the formatting, installing and erasing i've did during F2FS tests, but still no issues.
Sent from my Nexus 5
Thank you for the new recovery with f2fs support.
I'm running latest crombikk with your own cm kernel and the system is running smoothly. Androbench shows that the random write speed gets doubled.
However, my system is not completely stable. Sometimes it freezes without rebooting, specially trying to copy very large files. And sometimes the internal storage gets unmounted. I suppose it's kernel related.
Are you planning to give the option to format also /system and /cache on f2fs? Or you think it's not worth it?
deadlocked007 said:
So does this zips the full internal storage or just the data part with apps and stuff?
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Internal storage will be completely wiped,so /data/media too.
ariadnejro said:
Thank you for the new recovery with f2fs support.
I'm running latest crombikk with your own cm kernel and the system is running smoothly. Androbench shows that the random write speed gets doubled.
However, my system is not completely stable. Sometimes it freezes without rebooting, specially trying to copy very large files. And sometimes the internal storage gets unmounted. I suppose it's kernel related.
Are you planning to give the option to format also /system and /cache on f2fs? Or you think it's not worth it?
Click to expand...
Click to collapse
Didn't experienced issues so far but i 'm using CromiX here.
F2FS it's useful mostly for random write (or writing operations in general) ,there's no point using it for /system or /cache imo.
Sent from my Nexus 5 using Tapatalk
I assume twrp_f2fs is compatible with the current .10 bootloader and all the current roms: CROMi-X 5.4, CROMBi-KK and CM 11?
Sent from my K00C using Tapatalk
berndblb said:
I assume twrp_f2fs is compatible with the current .10 bootloader and all the current roms: CROMi-X 5.4, CROMBi-KK and CM 11?
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
twrp_f2fs it's based on official TWRP 2.7.0 and it should work fine with latest bootloader and all ROMs.
Basically i tested all those roms mentioned in your post and are working fine.
Sent from my Nexus 5
Seems to work well! I'm on the 3-19 build of CM11. Had really major IO issues with the device, nothing would make it even remotely usable, even on the performance CPU profile in both the cpu govenor and the asus cpu changer. It was always slow and laggy, it would not handle multiple things well, you basically had to single task. However, flashing this, doing my usual modifications, and it's making this baby fly again. I can open multiple apps and actually navigate without too much lag. Not sure if it's a placebo effect, but so far, it seems great, I'm able to install multiple things at once. I'll see how long this lasts (Wiping the SD can have some beneficial effects too) and I'll try to give an update later, it usually slows down after a few weeks. But this could be "settling" still, it's a fresh flash, even so, I'm happy it's usable again!
Hey is there any method available yet for this to work with rom2sd? Just imagining F2FS, rom2d, cromix 5.4 and hunds ET
yew123 said:
Hey is there any method available yet for this to work with rom2sd? Just imagining F2FS, rom2d, cromix 5.4 and hunds ET
Click to expand...
Click to collapse
In theory it should work like any ROM2SD installation:
* install rom2sd1 to switch the device nodes to the external card
* format data to f2fs
* install your ROM and a kernel with f2fs-enabled fstab in the ramdisk, don't reboot
* install rom2sd2 to move the ramdisk files to the external /system and modify mount points
Disclaimer: Not tested, there may be issues with the CROMI-X installer trying to be too clever, ...
_that said:
In theory it should work like any ROM2SD installation:
* install rom2sd1 to switch the device nodes to the external card
* format data to f2fs
* install your ROM and a kernel with f2fs-enabled fstab in the ramdisk, don't reboot
* install rom2sd2 to move the ramdisk files to the external /system and modify mount points
Disclaimer: Not tested, there may be issues with the CROMI-X installer trying to be too clever, ...
Click to expand...
Click to collapse
Well as long as you only do the data partition it should be OK. I'll look into f2fs support this week.
_that said:
In theory it should work like any ROM2SD installation:
* install rom2sd1 to switch the device nodes to the external card
* format data to f2fs
* install your ROM and a kernel with f2fs-enabled fstab in the ramdisk, don't reboot
* install rom2sd2 to move the ramdisk files to the external /system and modify mount points
Disclaimer: Not tested, there may be issues with the CROMI-X installer trying to be too clever, ...
Click to expand...
Click to collapse
Thanks @_that, when i've got some free time i'll give it a go
CM10 kernel?
Have a request for you, guys. Can someone make f2fs kernel for CM10?
Because I really don't want update my TF700 to 4.4, and stock-based roms isn't my choice...
I made 2 kernels for CM11 for data2sd setup with f2fs (sorry I know not CM10). But here they are if anyone wants to test them.
_thatv9 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 8c340aca96c50ed734b0c903b80d8312
Hunds 3.4.5 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 92cbf93223c07410758feb9921694353
sbdags said:
I made 2 kernels for CM11 for data2sd setup with f2fs (sorry I know not CM10). But here they are if anyone wants to test them.
_thatv9 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 8c340aca96c50ed734b0c903b80d8312
Hunds 3.4.5 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 92cbf93223c07410758feb9921694353
Click to expand...
Click to collapse
These Kernels will work on all CM based roms not just cromi-kk?
Sent from my SPH-L710 using Tapatalk
Frostbiter said:
These Kernels will work on all CM based roms not just cromi-kk?
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
Should do.
delete please
sbdags said:
Should do.
Click to expand...
Click to collapse
I end up with encryption unsucessful error on boot using the _that/sbdags kernel then reboots and twrp runs an open recovery script, reformatting cache with the mk_ext4 (IIRC), then same error on boot.
The CM kernel runs smoothly for me, but cannot get the touchscreen to respond from a deep sleep. The screen will turn on / off with power button press, but unable to get past the reboot screen or slide to wake screen because there isn't a response with touch. Fully charged the screen reads 'connect your charger' and will not connect to adb so I could not get a log for you.
We dug up the famous CROMi-X by @sbdags, dusted it off, pruned and tweaked it here and there and then slapped some paint on it.
Credits for the original ROM go to @sbdags, @_that, @Hundsbuah, @lj50036, @hardslog and everybody else who contributed and is credited in the original ROM thread: http://forum.xda-developers.com/showthread.php?t=2425383
@LetMeKnow has been (off and on) tweaking kernel and other settings in CROMi-X for the last 2 years, tirelessly looking for the sweet spot. The result is impressive IMHO
My contributions are mainly: Talking LMK into this project, some technical grunt work and putting this OP together.
This Is For You If:
You actually liked the Asus UI and miss it (nav buttons on the left anyone?)
You're tired of chasing the latest and greatest and want a ROM specifically designed for our hardware. Even it is JB 4.2
You are nostalgic for the "good ol' days"
Pre-Requisites:
The latest 10.6.1.14.10 bootloader. Grab it here if you don't have it: http://forum.xda-developers.com/showpost.php?p=55238386&postcount=3
The latest TWRP 2.8.x - We highly recommend lj50036/area51 Kang TWRP: http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
A working knowledge of flashing in fastboot or recovery. If you don't have it start reading here: http://forum.xda-developers.com/showthread.php?t=2688891
What's The Difference To The Original CROMi-X?
This rom is only for the TF700. Device specific files for the TF300, TF201 etc have been removed from the rom zip.
LetMeKnow added various kernel and settings tweaks (see post # 2)
fat32 and exFAT on the microSD is supported
No support for data2sd/rom2sd at this time (data2sd may come later, rom2sd.... I doubt it)
A major difference: CROMi-X Resurrected supports the f2fs file system. Here's some background on the benefits of f2fs: https://en.m.wikipedia.org/wiki/F2FS
But trust me on this: It makes a difference in performance.
CROMi-X Resurrected comes with only one kernel (based on Hundsbuah's), but in 3 variations:
Kernel 1 supports ONLY data & cache on ext4
Kernel 2 supports ONLY data f2fs / cache ext4
Kernel 3 supports ONLY data & cache f2fs
On this rom you will have to keep track of which file system you have on which partition and run the corresponding kernel. If you flash it and the rom does not boot, the most likely reason is that you flashed the wrong kernel for the file systems you chose.
How do you check which partition is on what file system? Glad you asked....
In Terminal Emulator or adb shell or the terminal in TWRP run:
Code:
mount
About half-way down in the output you'll find the details on /system, /cache and /data
On this ROM:
/system is always ext4. Since it is read-only in normal operation f2fs makes no sense
/data can be ext4 or f2fs, we highly recommend you run it on f2fs
/cache can be ext4 or f2fs. Your choice - opinions differ on this matter.Some say /cache on f2fs is pointless because the partition hardly (if ever) gets any write operations.
LetMeKnow's opinion: It does improve performance somewhat and if it doesn't - who cares....
It certainly does not hurt to have /cache on f2fs.
Installation Instructions:
For the initial installation a full format of /data in TWRP is highly recommended. If you want to chance it with just a wipe - go ahead, but don't blame us if the resulting ROM lacks the wow-factor or does not boot at all.
Note: Formatting /data in TWRP 2.8.x takes upwards of 60 minutes and formats /data to ext4. Do not interrupt it!
Then:
Load the ROM zip on a microSD, enter TWRP, flash it and follow the prompts in the Aroma installer.
Yeah, it's that complicated :cyclops:
There is no need to change file systems on /data or /cache prior to the ROM flash. We build this into Aroma.
You will have 4 options during installation:
1) both /data and /cache get formatted to ext4 (which is what they "normally" are)
2) only /data formatted to f2fs, /cache formatted ext4
3) both /data and /cache get formatted to f2fs
4) no partition gets formatted (for dirty flashing and keeping the existing file system configuration)
On the following page in Aroma you will choose the appropriate kernel for the file system combo you selected.
PLEASE make sure that you select the correct kernel! I made it clear as can be in Aroma. It's up to you to actually read and pay attention!!!
More Installation Options In Aroma
Select any Asus apps you would like to have, but select only those Gapps you absolutely need to have right after first boot. Instead, install Google apps from the Play Store later.
The reason for this: If you choose them in Aroma they get installed to /system, but you want them on /data to take maximum advantage of the improved performance on f2fs.
Browser - Browser2RAM
The rom comes packed with the stock browser and LMK's own version of Browser2RAM (B2R) which is optimized for the stock browser and the stock browser only!
If you want to run any other browser select the B2R option in Aroma. That will install sbdags version of B2R which works with a dozen different browsers (including the stock browser but not optimized for it).
If you plan to use only the stock browser do not select that option.
Post-Installation Tweaks:
Turn off automatic updates in the Play Store settings
Set Animation and Transitions to 0.5 or lower in Developer options
In Settings > Wi-Fi, Advanced Wi-Fi, set "Keep Wi-Fi on during sleep" to "only when plugged in" and uncheck "Wi-Fi optimization"
Stock browser advanced settings: Uncheck "Fast Scroller" and "Dim the screen while website loads"
Asus customized settings: Disable "Smart Backlight adjuster"
Hints And Tips
A reminder: The ROM boots by default with the JB 4.1 Asus UI (nav buttons to the left, Asus quick settings panel in the lower right). If you want the JB 4.2 UI (nav buttons in the middle, quick settings panel from top right, notifications top left) go to Settings > Launcher > select it and reboot
Dirty Flashing/Changing Kernels
If you want to reflash the ROM with the same file system/kernel combo and only change app selection or tweaks: Select "Do not format partitions" and "Do not flash a kernel" in Aroma.
If you want to change only the file system on /cache without also formatting /data (which would wipe your apps, settings and personal files):
Enter TWRP > Wipe > Advanced > check "Cache" > Repair or Change File System > Change File Systems > choose the file system you want and swipe the button.
Go back to TWRP Home, choose Install and flash the ROM. In Aroma choose "Do not format partitions" and then select the appropriate kernel for your new file system combo
More in-depths options for speed freaks in post # 2
Enjoy and let us know if you find any bugs
Read the release notes for the latest version in post # 3!!!
Change log:
CROMi-X [Resurrected] Changelog:</#></b>
<b><#selectbg_g>1/31/2016 - v5.4 CROMi-X & Extreme Tweaks - v3.0_RC2</#></b>
o Improve Wifi speed
o Set higher priority for Wifi to prevent starve and compete with other active processes
o Pressure the kernel more to reclaim the unused RAM
o Add a short delay for partitions to mount properly
o Change system settings for stability (Hopefully fix some rebooted issue for some users)
o Overall system improvements for performance
<b><#selectbg_g>11/12/2015 - v5.4 CROMi-X & Extreme Tweaks - v3.0</#></b>
o Device specific files for other Transformers removed. This ROM is only for the TF700
o Removed all other kernels except for Hund's ET v3.0
o Removed all other tweaks which conflict with ET v3.0
o Kernel supports ext4 or f2fs on data and cache
o Choice between data/cache on ext4, data f2fs/cache ext4 and data/cache f2fs
o Added option to choose file systems in Aroma
o Data2SD and ROM2SD support removed. May come back later but no promises
o Stock browser has it's own optimized Browser2RAM script. Will be overwritten if B2R for other browsers is selected in Aroma
o Updated build.prop to the latest Tweaks
o Updated Apex Launcher to latest version
o Updated Flash Player to the latest which supports Android OS
o Updated AdAway to latest version
<b><#selectbg_g>20/02/2014 - v5.4 CROMi-X</#></b>
o Removed CROMi-Control app. After discussions with elesbb he will redevelop as an xposed module
o Reverted Framework (framework.jar, services.jar, systemui.apk, transformer.apk) to pre-cromi-control versions
o Modded systemui.apk and transformer.apk to allow sd card and dock notifications to be removed as an option in installer
o Rebuilt Stock Launcher Lite version - 3 Screens ONLY, New Beach Wallpaper, 4.2 Gui gets 9x6 workspace and draw icons, removed google bar and page indicator
o Fixed framework-res.apk wallpaper inconsistencies. Tree definitely gone now and beach wallpaper formatted correctly
o Added installer option to switch balanced and performance profiles. If you choose balanced you actually get performance. Device boots to performance
o Changed entropy settings to stop kernel rebuilding entropy_avail - result should be less lag
o Updated _that's OC kernel to version 8
o Updated Hunds' kernel to version 3.4.5
o Updated LetMeKnow's ET to Hunds' 3.4.5 kernel
o Updated Google Core Services and libs to latest version
o Updated Titanium Backup to version 6.1.5.3
o Updated Google Maps to version 7.6.1
o Updated Google Music to version 5.4.1409N
o Updated Google Now to version 3.2.17
o Updated Superuser and binary to latest version 1.93
o Updated ES File Explorer to version 3.1.0.2
o Updated Asus Web Storage to version 2.1.3.7556
o Updated Google Mail to version 4.7.2
o Fixed issue of ET installation locked into 213 DPI
o Fixed search options missing - Reinstated QuickSearch from Asus
o Minor build.prop fix to remove duplicate entry
o Fixed build.prop for TF300T US users as it was showing the wrong version
Download from here: https://www.androidfilehost.com/?fid=745425885120760454
XDA:DevDB Information
CROMi-X 5.4 Resurrected, ROM for the Asus Transformer TF700
Contributors
berndblb, LetMeKnow, sbdags, _that, lj50036, Hund, hardslog
ROM OS Version: 4.2.x Jelly Bean
ROM Firmware Required: 10.6.1.14.10
Version Information
Status: Testing
Created 2015-12-18
Last Updated 2015-12-18
This is a short list of LetMeKnow's ET Tweaks:
My tweaks default setting:
Code:
PowerSaving mode : GPU @ 520MHz and CPU @ 1.2GHz (cpu1.sh)
Balance mode : GPU @ 650MHz and CPU @ 1.4GHz (cpu2.sh)
Performance mode : GPU @ 700MHz and CPU @ 1.8GHz (cpu3.sh)
Go here and change them yourselves with a reboot: "/system/ect/cpu1.sh" and change these settings in the "cpu1.sh". Repeat for others two modes. Look for these two lines:
GPU settings and changing:
GPU mV:
Code:
mV: 800 875 920 985 1042 1088 1135 1185 1290 1350 1410 (mV)
Freq: 200 267 304 361 408 446 484 520 600 650 700 (MHz)
Code:
logi "echo [COLOR="Red"]1350[/COLOR] > core_cap_level"
echo [COLOR="Red"]1350[/COLOR] > /sys/kernel/tegra_cap/core_cap_level
Change "1350" to "1185" for 520MHz or "1290" for 600MHz.
CPU settings and changing: The unit is in (KHz)
CPU mV:
Code:
mV: 200 300 420 485 510 540 575 620 650 690 740 795 860 895 930 975 1025 1075 1125 1180 1240 1300 1380 (mV)
Freq: 51 102 204 370 475 620 760 910 1000 1100 1200 1300 1400 1450 1500 1550 1600 1650 1700 1750 1800 1850 1900 (MHz)
Code:
logi "echo [COLOR="Red"]1800000[/COLOR] > pwr_cap_limit_1"
echo [COLOR="Red"]1800000[/COLOR] > /sys/module/cpu_tegra/parameters/pwr_cap_limit_1
logi "echo [COLOR="Red"]1800000[/COLOR] > pwr_cap_limit_2"
echo [COLOR="Red"]1800000[/COLOR] > /sys/module/cpu_tegra/parameters/pwr_cap_limit_2
logi "echo [COLOR="Red"]1800000[/COLOR] > pwr_cap_limit_3"
echo [COLOR="Red"]1800000[/COLOR] > /sys/module/cpu_tegra/parameters/pwr_cap_limit_3
logi "echo [COLOR="Red"]1800000[/COLOR] > pwr_cap_limit_4"
echo [COLOR="Red"]1800000[/COLOR] > /sys/module/cpu_tegra/parameters/pwr_cap_limit_4
You need to update the Red frequencies to a desired frequencies that you prefer and save it with a reboot.
Change the DPI:
DPI available for the Cromi-X: 136, 148, 160, 180, 200, 213, 224, 240
1. Go here: /system/build.prop and open the build.prop file in the edited mode with the rooted file explorer.
2. Look for this line "ro.sf.lcd_density=xxx" and change it to "ro.sf.lcd_density=new-DPI". You need to pick a desired DPI that you prefer.
3. Save your build.prop and reboot. Your DPI should be updated after the reboot.
That is all I have right now and have fun...
Notes on latest ROM version:
CROMi-X-ET-v.3.0-RC2:
If RC 2 is the first time you install this rom, just follow the instructions in the OP.
RC2 is basically RC1 + the latest performance patch by LMK
If you are already on RC 1 you can just flash the correct performance patch for your file system configuration, wipe cache and Dalvik and you're done. The patch is available in the Downloads section (one zip contains both patches) or from post # 77.
You can also dirty flash RC 2 - just remember to choose to not format any partitions in Aroma, and then select the correct kernel for your file system configuration.
If you had sudden reboot issues on RC 1:
1. In Settings go to Apps, swipe to All
2. Select the apps/games which caused the random reboot issue and ONLY click on the "Clear cache"
3. Do this for all apps/games which caused the reboot
4. When you are done, you need to reboot the device to complete the process. Please note that your device is going to be a little slow at first but it will improve the performance after a few minutes of usage
Congratulations on your first ROM release! :good:
berndblb said:
For sale
Click to expand...
Click to collapse
Sell it to @LetMeKnow so he can have some thanks too!
Nice.
An oldie but a goodie hehe
Please excuse my noobish question. When formating the internal or ext sd card should I put any user file or data on another device (pc) for safe keping until after formating and flashing the rom? When moving the user files and data back to the f2s formated cards do I need to do anything special.
sziggins said:
Sell it to @LetMeKnow so he can have some thanks too!
Click to expand...
Click to collapse
Thanks for your thought.... However, I am totally broke so I don't have money to buy it...
Any way, I did not do much in this release except for sharing my settings with others users.... The ROM is developed by @sbdags and the kernel is developed by @Hundsbuah. The repacked ROM is done by @berndblb. My tweaks are focused on the I/O optimization for R/W. I just found a balance for those read/write setting. The f2fs is a big help in this area. I think that is it, hahaha.....
Thanks,
LMK
---------- Post added at 10:24 AM ---------- Previous post was at 10:18 AM ----------
lartomar2002 said:
Please excuse my noobish question. When formating the internal or ext sd card should I put any user file or data on another device (pc) for safe keping until after formating and flashing the rom? When moving the user files and data back to the f2s formated cards do I need to do anything special.
Click to expand...
Click to collapse
Do you mean your /media partition? Your media should be either in Fat32 or exfat format.... I would recommend the exfat for your /media filesystem because it seems like it has a better performance in the write speed. These are the settings when you format your /media: exfat filesystem and "Allocation unit size" should be 128 kilobytes or 256 kilobytes. Please report back if you see improvement when you copy files to your media on your external uSD.....
Edit: For your internal SD or /media, you must move all your files to your PC because when you install the ROM, it will format your /data partition including your /media. When you are done with your installation, you can move it back to your internal /media but I would recommend you keep all your personal files on your external uSD....
Cheers,
LMK
For some reasons, it is duplicated so I delete the contents of this post....
Well done and welcome guys! I might just have to try this!
sbdags said:
Well done and welcome guys! I might just have to try this!
Click to expand...
Click to collapse
We are more than happy to hear a feedback from you. We hope that we did not screw it up so bad from your original Cromi-X v5.4, haha.....
LetMeKnow said:
Do you mean your /media partition? Your media should be either in Fat32 or exfat format....
Click to expand...
Click to collapse
You have a /media partition?
_that said:
You have a /media partition?
Click to expand...
Click to collapse
Haha, good catch.....:good: I meant /media Folder.....
LetMeKnow said:
Haha, good catch.....:good: I meant /media Folder.....
Click to expand...
Click to collapse
The point is, since /data/media is in the same filesystem as /data, it can't be formatted separately.
sziggins said:
Sell it to @LetMeKnow so he can have some thanks too!
Click to expand...
Click to collapse
I can't. He owns it already. I'm just holding that space for his next good ideas...
His posts are not hard to find. Hit the thanks button to your hearts content... All goes into the same pot...
Really nice to see you guys putting all the effort in giving new life to this dinosaur!!
Never got friends with KK and L on the TF700.
It's actualy quite flying again and quite snappy. High Five...!
Verstuurd vanaf mijn ASUS Transformer Pad TF700T met Tapatalk
Oh c'mon ! Maybe she's a granny, but dinosaur? A little harsh... ?
Good job guys! Installation was as painless as I've ever seen. Having Aroma do the FS changes was a stroke of genius, who do I thank for that? ROM boots FAST. Does seem like forever to shut down though. More next week after I find out how the new TF owner likes it!
Hi everyone ! I can't download the rom via Xda-Developers, the download is very slow and after a few minutes the download stops (Network error).
Can you Upload it on AndroidFileHost (or mega...) ? Thank you in advance and sorry for my bad english
This ROM is running wonderfully on my tf700t with a couple exceptions. I'm using plex and if I use the HDMI out with fullscreen video it will sometimes freeze the tablet when paused for too long. With plex fullscreen video & not using hdmi out it will sometimes artifact the display, freeze, & reboot.