I've seen in some ROMs for other phones (like Cyanogen and Enomther's ROMs) that they implement a hack that moves the dalvik-cache into the /cache partition, thus freeing up a lot of space in /data (and virtually eliminating the need for a2sd). I'm wondering if anyone has thought of or knows how to do that? I think it'd be a great addition to any ROM.
adb shell
busybox cp -a /data/dalvik-cache /cache/delvik
reboot recovery
adb shell
mount cache
rm -rf /data/dalvik-cache
ln -s /cache/dalvik/dalvik-cache /data/dalvik-cache
should work
Dont know about after reboot though.
Me personally I just moved it all to the sd ext2.
Dalvik and system apps also.
smstutler said:
adb shell
busybox cp -a /data/dalvik-cache /cache/delvik
reboot recovery
adb shell
mount cache
rm -rf /data/dalvik-cache
ln -s /cache/dalvik/dalvik-cache /data/dalvik-cache
should work
Dont know about after reboot though.
Me personally I just moved it all to the sd ext2.
Dalvik and system apps also.
Click to expand...
Click to collapse
Cool! Now to make that survive a reboot, it would have to be written into the boot.img, or in a script that is called in the boot.img correct?
That I dont know. I was wondering how to utilize all the free space I have better. Just a heads up though dalvik on my system is 60megs.
smstutler said:
That I dont know. I was wondering how to utilize all the free space I have better. Just a heads up though dalvik on my system is 60megs.
Click to expand...
Click to collapse
Exactly why moving it to cache would be ideal, as far as my limited knowledge of this understands. That frees up about 60mb of space in /data.
smstutler said:
I was wondering how to utilize all the free space I have better.
Click to expand...
Click to collapse
Honestly, the best use for the internal memory would be to leave the dalvik cache on it. It consists of files that have already been preprocessed by the VM specifically with the intention of improving performance. Moving that from the internal memory to the slower sd card.... It ain't gonna help....
If your trying to tweak performance, you're much better off looking for other things you can move to create more space for the cache....
Isn't /cache just a separate partition in the internal memory?
mrinehart93 said:
Isn't /cache just a separate partition in the internal memory?
Click to expand...
Click to collapse
I assumed he had symlinked it over to the sd card. Generally the only benefit to be gained by moving files around is by putting things on the (slow) sd card to free up the (faster) internal memory.
If that's not what we're talking about, then the end result would be exactly nill...
subliminalurge said:
I assumed he had symlinked it over to the sd card. Generally the only benefit to be gained by moving files around is by putting things on the (slow) sd card to free up the (faster) internal memory.
If that's not what we're talking about, then the end result would be exactly nill...
Click to expand...
Click to collapse
Actually I have seen no performance hit as I can tell by running it internally or on sd card.
smstutler said:
Actually I have seen no performance hit as I can tell by running it internally or on sd card.
Click to expand...
Click to collapse
That's certainly possible. Are you using the stock sd card?
I still stand behind my assertion that the dalvik cache is the wrong thing to be moving if the goal is to improve performance. (Well, unless you somehow have an sd card that operates faster than the internal memory...)
And your statement that you see no performance hit one way or the other is kind of just another way of saying what I said... The result was nill.....
subliminalurge said:
That's certainly possible. Are you using the stock sd card?
I still stand behind my assertion that the dalvik cache is the wrong thing to be moving if the goal is to improve performance. (Well, unless you somehow have an sd card that operates faster than the internal memory...)
And your statement that you see no performance hit one way or the other is kind of just another way of saying what I said... The result was nill.....
Click to expand...
Click to collapse
Right I get your point. But now on to the better thing. Possibly moving some music files to internal since I have seen complaints of hiccups when playing tunes. I cant think of any other benefits as of yet. Was just curious as to if it could be done so I did it. I am using a class 4 card I have a 6 but it is a tad bad so it is of no use. Now as for moving the dalvik to the /cache, that seems like it would be the better idea, since i have yet to see my cache used much at all.
smstutler said:
Now as for moving the dalvik to the /cache, that seems like it would be the better idea, since i have yet to see my cache used much at all.
Click to expand...
Click to collapse
I haven't really monitored the usage, although it shouldn't change much.
I'm also new to Android, but I have a good number of years under my belt both adminning Linux machines and developing Java apps (amongst other things...).
I've done a bit of reading on how the Dalvik VM works, and I can confidently tell you that you want the Dalvik cache on whatever the fastest memory in your phone is. For the vast majority of people, that will be the internal memory. If you've spent a small fortune on a super-badass sd card that is faster (like that other thread where the guy bought a class 10), then moving it would be a simple matter of symlinking that directory onto the card.
As far as your concerns with stuttering music, even the dog slow sd card that comes stock with the hero is plenty fast for playing an mp3 file. If you're having trouble there, you need to take a look at what's hogging your cpu, not what's hogging your memory....
Nah wasn't meant for me with the music on SD. I rarely use it for that. But yes I do agree with you. The SD may not be best choice but there has to be a better way to utilize some of the system memory that just sits dormant.
/dev/block/mtdblock4 130.0M 1.1M 128.9M 1% /cache
see what I mean here. 1% used.
I've tested this on my Hero, my Nexus One and on a friend's Evo.
Code:
#!/system/bin/sh
echo "++++ DALVIK 2 CACHE STARTING ++++"
if [ ! -d /cache/dalvik-cache ]
then
mkdir /cache/dalvik-cache
chown 1000:1000 /cache/dalvik-cache
chmod 775 /cache/dalvik-cache
fi
if [ -L /data/dalvik-cache ]
then
rm -f /data/dalvik-cache
mkdir /data/dalvik-cache
chown 1000:1000 /data/dalvik-cache
chmod 775 /data/dalvik-cache
elif [ ! -d /data/dalvik-cache ]
then
mkdir /data/dalvik-cache
chown 1000:1000 /data/dalvik-cache
chmod 775 /data/dalvik-cache
elif [ -d /data/dalvik-cache ]
then
for filename in /data/dalvik-cache/*
do
if [ -L $filename ]
then
rm -f $filename
fi
done
mv /data/dalvik-cache/* /cache/dalvik-cache/
fi
mount -o bind /cache/dalvik-cache/ /data/dalvik-cache/
It's part of Darktremor A2SD 2.7 update 3r1.
Command: a2sd cachepart
Hacre said:
I've tested this on my Hero, my Nexus One and on a friend's Evo.
Code:
#!/system/bin/sh
echo "++++ DALVIK 2 CACHE STARTING ++++"
if [ ! -d /cache/dalvik-cache ]
then
mkdir /cache/dalvik-cache
chown 1000:1000 /cache/dalvik-cache
chmod 775 /cache/dalvik-cache
fi
if [ -L /data/dalvik-cache ]
then
rm -f /data/dalvik-cache
mkdir /data/dalvik-cache
chown 1000:1000 /data/dalvik-cache
chmod 775 /data/dalvik-cache
elif [ ! -d /data/dalvik-cache ]
then
mkdir /data/dalvik-cache
chown 1000:1000 /data/dalvik-cache
chmod 775 /data/dalvik-cache
elif [ -d /data/dalvik-cache ]
then
for filename in /data/dalvik-cache/*
do
if [ -L $filename ]
then
rm -f $filename
fi
done
mv /data/dalvik-cache/* /cache/dalvik-cache/
fi
mount -o bind /cache/dalvik-cache/ /data/dalvik-cache/
Click to expand...
Click to collapse
tkirton said:
It's part of Darktremor A2SD 2.7 update 3r1.
Command: a2sd cachepart
Click to expand...
Click to collapse
Was there a reason you quoted me?
Hacre said:
Was there a reason you quoted me?
Click to expand...
Click to collapse
I believe tkirton quoted you because instead of ruunning the script you could simply use the Command: a2sd cachepart
In his latest release.
nfinitefx45 said:
I believe tkirton quoted you because instead of ruunning the script you could simply use the Command: a2sd cachepart
In his latest release.
Click to expand...
Click to collapse
Oh I see. Well the script I posted should work on ROMs that don't have such a feature.
True. Point taken.
Hacre said:
Oh I see. Well the script I posted should work on ROMs that don't have such a feature.
Click to expand...
Click to collapse
Newbie question
Hacre said:
I've tested this on my Hero, my Nexus One and on a friend's Evo.
Code:
#!/system/bin/sh
echo "++++ DALVIK 2 CACHE STARTING ++++"
if [ ! -d /cache/dalvik-cache ]
then
mkdir /cache/dalvik-cache
chown 1000:1000 /cache/dalvik-cache
chmod 775 /cache/dalvik-cache
fi
if [ -L /data/dalvik-cache ]
then
rm -f /data/dalvik-cache
mkdir /data/dalvik-cache
chown 1000:1000 /data/dalvik-cache
chmod 775 /data/dalvik-cache
elif [ ! -d /data/dalvik-cache ]
then
mkdir /data/dalvik-cache
chown 1000:1000 /data/dalvik-cache
chmod 775 /data/dalvik-cache
elif [ -d /data/dalvik-cache ]
then
for filename in /data/dalvik-cache/*
do
if [ -L $filename ]
then
rm -f $filename
fi
done
mv /data/dalvik-cache/* /cache/dalvik-cache/
fi
mount -o bind /cache/dalvik-cache/ /data/dalvik-cache/
Click to expand...
Click to collapse
How can I run this script on my ROM? Please guide me to make this work.
Related
I originally was using apps2sd on my DC 2.09.01 hero. I have now decided not to use it. But when I go into applications it shows all the apps that I had installed as ex: "com.jrtstudio.automont" 0 kb. How can I remove these?
reboot into recovery and wipe your cache.
1 more question...
Once you use apps2sd is there a way to transfer those apps back to your device if you decide you no longer want those apps on your SD.
Kcarpenter said:
reboot into recovery and wipe your cache.
Click to expand...
Click to collapse
I rebooted into recovery and wiped my dalvik cache and they are still there...
Still trying to figure this all out...
Just go to dc config an disable a2sd and disable dalvik cache to sd (uncheck the buttons) then save. After that reboot it should move all ur apps and cache back to internal storage memory. That's it
-------------------------------------
Sent via the XDA Tapatalk App
roadster92 said:
Just go to dc config an disable a2sd and disable dalvik cache to sd (uncheck the buttons) then save. After that reboot it should move all ur apps and cache back to internal storage memory. That's it
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
I did that originally and it still shows the .com files...and my apps never got moved back to the phones memory.
Type the following in ADB shell:
/system/xbin/busybox rm /data/app
/system/xbin/busybox rm /data/app-private
/system/xbin/busybox mkdir /data/app
/system/xbin/busybox mkdir /data/app-private
/system/xbin/busybox chmod 755 /data/app
/system/xbin/busybox chmod 755 /data/app-private
/system/xbin/busybox cp /system/sd/app/* /data/app
/system/xbin/busybox cp /system/sd/app-private/* /data/app-private
Now your programs should be back on the SD card.
To move dalvik-cache, while in ADB Shell, type the following commands:
/system/xbin/busybox rm /data/dalvik-cache
/system/xbin/busybox mkdir /data/dalvik-cache
/system/xbin/busybox chmod 755 /data/dalvik-cache
/system/xbin/busybox cp -f /system/sd/dalvik-cache/* /data/dalvik-cache
Now, your phone is now using internal storage. Reboot the phone to make sure the changes stay (make sure the A2SD and Dalvik-Cache to SD is off in Dconfig).
If that doesn't work, download Darktremor A2SD 2.7 Update 3. Once that is flashed and you have your phone booted, type the following in an ADB shell:
a2sd remove
That will move everything back to internal storage and sets a flag (called .noa2sd) on your SD card to prevent the data from being moved again (until you reactivate it using a2sd install)
Hope that helps.
fifedogg said:
I did that originally and it still shows the .com files...and my apps never got moved back to the phones memory.
Click to expand...
Click to collapse
Just got my Droid yesterday. Already have Simple ROM 1.0 running... And I'm looking on here for apps2sd and can't find anything. Any answers? Before I did the flash, I was sitting at 120 megs of memory easily. Now... I'm sitting at around 77 megs.
Please help!!!
Sent from my Droid using XDA App
Haven't tried that rom, but if you go into settings>>applications, and go into each application, there should be an option to move to SD card. Don't move your launchers, or anything that has a widget, or you will have issues. Some apps will not allow you to move them anyways. It also doesn't move the entire application, usually about half to two thirds of the app gets moved.
If his suggestion doesn't work, Cyanogenmod has Apps2SD integrated and working. I thought you had to create an ext* partition, but apparently not anymore. It works fine as normal.
I'm using CyanogenMod right now... And I hate it. I keep getting FCs from .acore, whatever that is. I think it's a Firmware System File, and it's corrupted.
And that dude's answer is like the answer for a total noob that has no clue what they're doing. Sorry, but I'm not new to this. LOL!
Back on topic.... is there any way to get Apps2SD using the SDK's ADB Shell? I think I read somewhere that there's some way of basically tricking the Market and the phone into saving Apps2SD by using the ADB. If you've got commands, I can type them.
And also.... If I were to get Apps2SD working in SimpleRom, is there going to be a way that I can just pull the apps off my SD Partition without having to go all the way back through the excruciating process of RE-DOWNLOADING ALL MY APPS from the Market?
Until we figure this out, I'll be tinkering away on my own... LOL!
Regarding the force close with acore...have you tried clearing the dalvik-cache? I've had issues with the dalvik-cache getting hosed (or having an older copy).
Quickest way of clearing the dalvik-cache:
If dalvik is on internal storage: busybox rm -f /data/dalvik-cache/*
if dalvik is on cache partition: busybox rm -f /cache/dalvik-cache/*
In both cases, reboot the phone.
If the CyanogenMod is a nightly build, I noticed it puts the dalvik-cache on /cache partition. With my Darktremor Apps2SD, this messes up the program as it completely bypasses /data/dalvik-cache. Simple workaround would be to copy the files in /cache/dalvik-cache to /data/dalvik-cache, remove the /cache/dalvik-cache, then create a symlink of /cache/dalvik-cache pointing to /data/dalvik-cache.
Classic Apps2SD (or as some would call A2SD+) can be achieved by performing the following actions (after you launch ADB Shell):
1. Find out where your EXT partition for your SD card mounted to. There's at least two mount points: /system/sd or /sd-ext
2. Perform the following command:
- for mount point /system/sd: cd /system/sd
- for mount point /sd-ext: cd /sd-ext
3. Create two directories: app and app-private:
- busybox mkdir app
- busybox mkdir app-private
- chmod 777 app
- chmod 777 app-private
4. Copy the contents of both /data/app and /data/app-private to the SD card:
For mount point /system/sd:
- busybox cp -fp /data/app/* /system/sd/app
- busybox cp -fp /data/app-private/* /system/sd/app
For mount point /sd-ext:
- busybox cp -fp /data/app/* /sd-ext/app
- busybox cp -fp /data/app-private/* /sd-ext/app-private
5. Remove the /data/app directory and /data/app-private directory:
- busybox -rf /data/app
- busybox -rf /data/app-private
6. Create symlinks to the sd card:
For mount point /system/sd:
- busybox ln -s /system/sd/app /data/app
- busybox ln -s /system/sd/app-private /data/app-private
For mount point /sd-ext:
- busybox ln -s /sd-ext/app /data/app
- busybox ln -s /sd-ext/app-private /data/app-private
And that should do it. Just make sure that the rom mounts the /dev/block/mmcblk0p2 device:
Mount to /system/sd:
- busybox -t auto -o rw /dev/block/mmcblk0p2 /system/sd
Mount to /sd-ext
- busybox -t auto -o rw /dev/block/mmcblk0p2 /sd-ext
Hope this helps.
DyMiC said:
I'm using CyanogenMod right now... And I hate it. I keep getting FCs from .acore, whatever that is. I think it's a Firmware System File, and it's corrupted.
And that dude's answer is like the answer for a total noob that has no clue what they're doing. Sorry, but I'm not new to this. LOL!
Back on topic.... is there any way to get Apps2SD using the SDK's ADB Shell? I think I read somewhere that there's some way of basically tricking the Market and the phone into saving Apps2SD by using the ADB. If you've got commands, I can type them.
And also.... If I were to get Apps2SD working in SimpleRom, is there going to be a way that I can just pull the apps off my SD Partition without having to go all the way back through the excruciating process of RE-DOWNLOADING ALL MY APPS from the Market?
Until we figure this out, I'll be tinkering away on my own... LOL!
Click to expand...
Click to collapse
I used a simple shell command in terminal emulator which worked fine for me, I believe its
pm setInstallLocation 2 (1 instead to reset to internal storage.)
one line of code, simple fix. and as stated earlier, no launchers or widgets should be moved, so if you install one after entering this, move it back to phone through application settings, manage applications.
Hi Folks,
By request from a friend i've created a sh script to move all [email protected] dalvik cache files to /cache/dalvik-cache because some roms store [email protected] dalvik files in /data/dalvik-cache. So for those that need or wont to save some space in /system follow this steps:
1 - You need a rooted phone
2 - You need terminal emulator
3 - Download script from here
4 - Open terminal, navigate to where you downloaded the script and run sh dalvik.sh
5 - Reboot
!!Warning!!
Only run script in roms that store [email protected] dalvik files in /data/dalvik-cache otherwise you will experience some bugs in aplications.
Please post your feedback please
Thanks to HeD_pE for testing!
Cheers,
h4ck3dm1nd
Sorry I can't find the links
http://forum.xda-developers.com/showthread.php?p=32360919#post32360919
his other post...
[email protected]:/ # su
[email protected]:/ # cd /data/dalvik-cache
[email protected]:/data/dalvik-cache # mv [email protected]* /cache/dalvik-cache
failed on '[email protected]@[email protected]' - Cross-device link
255|[email protected]:/data/dalvik-cache #
I have [email protected] dalvik stuff in /data/dalvik cache and I've created folder /cache/dalvik-cache. Android: CM9.1 miroslav. Ideas?
prwnd said:
[email protected]:/ # su
[email protected]:/ # cd /data/dalvik-cache
[email protected]:/data/dalvik-cache # mv [email protected]* /cache/dalvik-cache
failed on '[email protected]@[email protected]' - Cross-device link
255|[email protected]:/data/dalvik-cache #
I have [email protected] dalvik stuff in /data/dalvik cache and I've created folder /cache/dalvik-cache. Android: CM9.1 miroslav. Ideas?
Click to expand...
Click to collapse
I'm having the same problem but with AIME.apk file. I'm using AOSP v1.2 by miroslav
prwnd said:
[email protected]:/ # su
[email protected]:/ # cd /data/dalvik-cache
[email protected]:/data/dalvik-cache # mv [email protected]* /cache/dalvik-cache
failed on '[email protected]@[email protected]' - Cross-device link
255|[email protected]:/data/dalvik-cache #
I have [email protected] dalvik stuff in /data/dalvik cache and I've created folder /cache/dalvik-cache. Android: CM9.1 miroslav. Ideas?
Click to expand...
Click to collapse
Hi,
Sorry but i do not check GT540 forum to often, I realised that if you create the /cache/dalvik-cache folder and run the script after it it will create the same folder again and in root explorer you can see the folders with the exact same name, So please backup your ROM, move all dalvik cache from /cache to its original folder, remove any symlinks and without creating the /cache/dalvik-cache folder run the script please.
In the attachment I share the scripts that Worked for me in order to move dalvik-cache to /cache (or to /dev).
Just put the one you want on /system/etc/init.d and set permissions to 777. Reboot to recovery, wipe cache and dalvik-cache and reboot to system again. Done =D
coto39 said:
In the attachment I share the scripts that Worked for me in order to move dalvik-cache to /cache (or to /dev).
Just put the one you want on /system/etc/init.d and set permissions to 777. Reboot to recovery, wipe cache and dalvik-cache and reboot to system again. Done =D
Click to expand...
Click to collapse
using your script, and it works. tq m8. using optimus 2x
The script is pretty easy to create.
# /system/bin/sh
rm /data/dalvik-cache/*
reboot
Use su binary.
Save it has a .sh file and then chmod 755 the file so you can run it via terminal.
And how do I know that?, I have experience with Linux OS.
I will upload it to my site tomorrow if I have time to also create index.php for it and update the other index.php file so it is easy to access the file to download.
EDIT: Oops, you are talking about moving, all well, this can be useful anyway.
EDIT2: Here is the link: caftp.3owl.com/Shell_Scripts/Dalvik_cache_cleaner/
andyabc said:
The script is pretty easy to create.
# /system/bin/sh
rm /data/dalvik-cache/*
reboot
Use su binary.
Save it has a .sh file and then chmod 755 the file so you can run it via terminal.
And how do I know that?, I have experience with Linux OS.
I will upload it to my site tomorrow if I have time to also create index.php for it and update the other index.php file so it is easy to access the file to download.
EDIT: Oops, you are talking about moving, all well, this can be useful anyway.
Click to expand...
Click to collapse
Oops, moderator delete this post, I accidentally ended up quoting my own post o.o
I fixed this script, but u must create before dalvik-cache folder in /cache (maybe add this to updater script) [no need anymore till V0.2 version]
Script v0.4 (can be used also as init.d script ) :
Code:
#!/system/bin/sh
#Dalvik Cache Saver by Alberto96
if [ -d /cache/dalvik-cache ];
then
cd /data/dalvik-cache
cp -a [email protected]* /cache/dalvik-cache
rm -r -f [email protected]*
find /data/dalvik-cache -type l -delete
busybox find /cache/dalvik-cache/* -type f -exec cp -f -s {} /data/dalvik-cache/ \;
else
mkdir /cache/dalvik-cache
cd /data/dalvik-cache
cp -a [email protected]* /cache/dalvik-cache
rm -r -f [email protected]*
find /data/dalvik-cache -type l -delete
busybox find /cache/dalvik-cache/* -type f -exec cp -f -s {} /data/dalvik-cache/ \;
fi
[ 0.3 version works but have a problem, im searching a fix. ]
Link for thread : http://forum.xda-developers.com/showthread.php?p=35843614
Ok , but how move ONLY SYSTEM DALVIK to cache/dalvik cache? Any ideas?
When we move ALL dalvik cache apps (some data and system) , than cache partition is fully! And we can't install any others apps !
This script moves only system dalvik cache so cache partition size is enough. Data dalvik cache will be saved in data partition with no cause of no space Tested in huawei u8160 with very little partitions
Inviato dal mio GT-I9000 con Tapatalk 2
Script working perfect , but first we must create dalvik-cache folder in cache partition (in CM9) and set permissions this folder:
[x][x][x]
[x][x][x]
[o][o][x]
Script move to etc/init.d and set perm:
[x][x][x]
[x][o][x]
[x][o][x]
reboot.
As I cannot use the internal sdcard with CM11, I've made a small script which mounts the internal sdcard as /data/dalik-cache to get more free space for apps & app-data.
WARNING: Only for users who are familiar with adb as you can probably brick your device!
Installation is a bit tricky, maybe someone makes an installer. All steps are done over adb
First format the internal sdcard with ext4: mke2fs -t ext4 /dev/block/mmcblk0p23
Copy script below to /data/local/userinit.sh (e.g. adb push userinit.sh /data/local/userinit.sh)
chmod 755 /data/local/userinit.sh
Reboot and let dalvik cache recreate. After this happend, reboot into recovery, wipe dalvik-cache and enjoy the 200MB more free space in data for apps.
Code:
#!/system/bin/sh
busybox mount -t ext4 -o noatime,nodiratime,nosuid,nodev /dev/block/mmcblk0p23 /data/dalvik-cache;
mountext=`busybox mount | egrep 'ext2|ext3|ext4'`;
if [ -n "$mountext" ];
then
busybox chown 1000:1000 /data/dalvik-cache;
busybox chmod 771 /data/dalvik-cache;
fi;
sync;
Awesome... I just needed it for assigning block on dalvik in my beta app. Works great!
Is anyone here familiar with Kali Nethunter? They released version 3.0 that now supports Marshmallow, however, Kali is installed on top of stock Marshmallow from what I understand. Can anyone elaborate on how this is possible seeing as Marshmallow on the shamu is packed tightly to the brim on the system partition? I freed up about 200 to 300 MB of space deleting system apps I don't need, but this Kali build is over 600MB! Probably uncompresses to be even bigger. Thanks for any insight ant of you can provide! Cheers!
H4X0R46 said:
Is anyone here familiar with Kali Nethunter? They released version 3.0 that now supports Marshmallow, however, Kali is installed on top of stock Marshmallow from what I understand. Can anyone elaborate on how this is possible seeing as Marshmallow on the shamu is packed tightly to the brim on the system partition? I freed up about 200 to 300 MB of space deleting system apps I don't need, but this Kali build is over 600MB! Probably uncompresses to be even bigger. Thanks for any insight ant of you can provide! Cheers!
Click to expand...
Click to collapse
When flashing it most likely removes enough to fit what it needs. It Could also over write stock files. I use Kali so am DL it now to have a look.
zelendel said:
When flashing it most likely removes enough to fit what it needs. It Could also over write stock files. I use Kali so am DL it now to have a look.
Click to expand...
Click to collapse
You were right, I went ahead and flashed it, and the aroma installer had a line that said "clearing up space in /system" and it did. Thanks!
Sent from my Nexus 6
H4X0R46 said:
You were right, I went ahead and flashed it, and the aroma installer had a line that said "clearing up space in /system" and it did. Thanks!
Sent from my Nexus 6
Click to expand...
Click to collapse
Yeah I have the zip and am gonna rip it apart and see just what it is doing.
zelendel said:
Yeah I have the zip and am gonna rip it apart and see just what it is doing.
Click to expand...
Click to collapse
Yea it makes me wonder what it's really removing. I had about 200 - 300 MB free on my system because I removed some Google bloatware, and after the Kali install, I had like, 500 ish MB free. It deletes something big from the system. Wonder what is actually removed.
Sent from my Nexus 6
H4X0R46 said:
Yea it makes me wonder what it's really removing. I had about 200 - 300 MB free on my system because I removed some Google bloatware, and after the Kali install, I had like, 500 ish MB free. It deletes something big from the system. Wonder what is actually removed.
Sent from my Nexus 6
Click to expand...
Click to collapse
Here is what their script removes.
# clean the system from extra/uneeded apps
#
SA=/system/app
# Apks were located in /system/app folder previously
rm -f $SA/PrintSpooler.*
rm -f $SA/QuickOffice.apk
rm -f $SA/CloudPrint2.apk
rm -f $SA/HPPrintPlugin.apk
rm -f $SA/KoreanIME.apk
rm -f $SA/PlusOne.apk
rm -f $SA/PlayGames.apk
rm -f $SA/Drive.apk
rm -f $SA/Maps.apk
rm -f $SA/Magazines.apk
rm -f $SA/GooglePinyinIME.apk
rm -f $SA/Books.apk
rm -f $SA/Magazines.apk
rm -f $SA/Currents.apk
rm -f $SA/GoogleEars.apk
rm -f $SA/Keep.apk
rm -f $SA/FaceLock.apk
# Apks are located in folders now...can we move to /data?
rm -rf $SA/HoloSpiralWallpaper
rm -rf $SA/BasicDreams
rm -rf $SA/Drive
rm -rf $SA/Maps
rm -rf $SA/FaceLock
rm -rf $SA/Books
rm -rf $SA/Newsstand
rm -rf $SA/Street
rm -rf $SA/CloudPrint2
rm -rf $SA/PlayGames
rm -rf $SA/YouTube
rm -rf $SA/PlusOne
rm -rf $SA/PrintSpooler
rm -rf $SA/GoogleHindiIME
rm -rf $SA/GooglePinyinIME
rm -rf $SA/KoreanIME
#rm -rf $SA/LatinImeGoogle
rm -rf $SA/Music2
rm -rf $SA/iWnnIME
rm -rf $SA/Photos
rm -rf $SA/LiveWallpapersPicker
rm -rf $SA/PhaseBeam
rm -rf /system/priv-app/Hangouts
rm -rf /system/priv-app/Wallet
zelendel said:
Here is what their script removes.
# clean the system from extra/uneeded apps
#
SA=/system/app
# Apks were located in /system/app folder previously
rm -f $SA/PrintSpooler.*
rm -f $SA/QuickOffice.apk
rm -f $SA/CloudPrint2.apk
rm -f $SA/HPPrintPlugin.apk
rm -f $SA/KoreanIME.apk
rm -f $SA/PlusOne.apk
rm -f $SA/PlayGames.apk
rm -f $SA/Drive.apk
rm -f $SA/Maps.apk
rm -f $SA/Magazines.apk
rm -f $SA/GooglePinyinIME.apk
rm -f $SA/Books.apk
rm -f $SA/Magazines.apk
rm -f $SA/Currents.apk
rm -f $SA/GoogleEars.apk
rm -f $SA/Keep.apk
rm -f $SA/FaceLock.apk
# Apks are located in folders now...can we move to /data?
rm -rf $SA/HoloSpiralWallpaper
rm -rf $SA/BasicDreams
rm -rf $SA/Drive
rm -rf $SA/Maps
rm -rf $SA/FaceLock
rm -rf $SA/Books
rm -rf $SA/Newsstand
rm -rf $SA/Street
rm -rf $SA/CloudPrint2
rm -rf $SA/PlayGames
rm -rf $SA/YouTube
rm -rf $SA/PlusOne
rm -rf $SA/PrintSpooler
rm -rf $SA/GoogleHindiIME
rm -rf $SA/GooglePinyinIME
rm -rf $SA/KoreanIME
#rm -rf $SA/LatinImeGoogle
rm -rf $SA/Music2
rm -rf $SA/iWnnIME
rm -rf $SA/Photos
rm -rf $SA/LiveWallpapersPicker
rm -rf $SA/PhaseBeam
rm -rf /system/priv-app/Hangouts
rm -rf /system/priv-app/Wallet
Click to expand...
Click to collapse
Alright! That's good to know! I was wondering how it removes so much from system, this answers my question perfectly!
H4X0R46 said:
Alright! That's good to know! I was wondering how it removes so much from system, this answers my question perfectly!
Click to expand...
Click to collapse
If you are ever wondering what it is doing, just unzip the file on the pc and use notepad++ to check out the scripts. Even if you dont understand everything somethings will start to make sense the more you look at it.
zelendel said:
If you are ever wondering what it is doing, just unzip the file on the pc and use notepad++ to check out the scripts. Even if you dont understand everything somethings will start to make sense the more you look at it.
Click to expand...
Click to collapse
I've done this more or less, where should I look? The update script? I've done this a couple of time to see which Android version a ROM was when the post I found it on was not specific enough.
Sent from my Nexus 6
H4X0R46 said:
I've done this more or less, where should I look? The update script? I've done this a couple of time to see which Android version a ROM was when the post I found it on was not specific enough.
Sent from my Nexus 6
Click to expand...
Click to collapse
What I did was look to see what the update script was running and then went and looked at those scripts. It's a bit of tracking but it works
zelendel said:
What I did was look to see what the update script was running and then went and looked at those scripts. It's a bit of tracking but it works
Click to expand...
Click to collapse
Thanks man! Appreciate it! Also, an unrelated side question. If you remove the SuperSU zip from a rom, will it still flash right and just skip SuperSU? Or does the script have to be also changed? Thanks! You may be able to answer this one, if not, that's cool!
Yeah it should. I would imagine to pull off alot of what its pc counter part does it will need root
zelendel said:
Yeah it should. I would imagine to pull off alot of what its pc counter part does it will need root
Click to expand...
Click to collapse
Mostly for multirom use, some roms include systemless root and as of right now, that doesn't flash correctly with multirom. So in theory, removing the super su folder from the rom and then installing normal system root should work?
Sent from my Nexus 6
H4X0R46 said:
Mostly for multirom use, some roms include systemless root and as of right now, that doesn't flash correctly with multirom. So in theory, removing the super su folder from the rom and then installing normal system root should work?
Sent from my Nexus 6
Click to expand...
Click to collapse
To be honest I have never messed with multirom. It has never really worked properly and most roms I run will not support it. So that I can't answer.
zelendel said:
To be honest I have never messed with multirom. It has never really worked properly and most roms I run will not support it. So that I can't answer.
Click to expand...
Click to collapse
Alright. Well cool thanks for all your help man! Appreciate it!
can i flash kali nethunter 3 on top of aosip slim gapps hcb13 ?
i installed their 3.0 the day they announced it but the terminal doesnt work with the error "1.) no title".
other people have the same issue and they cannot seem to reproduce the issue and fix it. had to dirty flash my system image.
even though they say its stable there are many issues hovering over this mod BUT its hell of a mod if it works, makes you proud to own an android; specially a Nexus!