I dont want to use app2sd as I feel it a bit unnecessary and I really don't need too much more space. I saw WES incorporated moving dalvik cache to the cache partition (cache part is 80 megs that will never get fully used on the slide). I asked in his thread twice but it seems it'll never be seen. Any way, I did some searching and found a script that does exactly what I want. This would also be useful for those like me that just want a few more mb's of internal storage and dont want to use apps2sd. I'm not a developer so I just want to put this here for our devs to mod or give the okay on if this will work on the slide.
I got the script attached from this thread. You can also read in more detail on what exactly it is I'm wanting to do here http://forum.samdroid.net/f9/relocate-dalvik-cache-free-up-space-1117/
I just want to know what has to be done if anything to get this working on the Slide. Thanks
I was able to get dalvik-cache to /cache by going into clockworkmod recovery and accessing from adb:
mv /data/dalvik-cache /cache/dc
ln -s /cache/dc /data/dalvik-cache
After the files are moved and the symlink is created, you should have no problems when rebooting.
However, I came across a problem when I flashed the radio, since it wiped the cache partition. If you are missing all your installed apps in android, it might be that the cache partition was wiped. You need to recreate the /cache/dc folder and reboot.
Thanks for the input. finally someone! ..thats good to know Im going to try it now, I didnt think it would be as simple as a move command.. any reason the radio wipes the cache partition? did dalvik recreate itself after the wipe in /data? and were ALL the apps gone or just the few that took up the memory?
turboyo said:
I didnt think it would be as simple as a move command..
Click to expand...
Click to collapse
Don't forget to make the symbolic link. That is the important command, not the move one.
turboyo said:
Thanks for the input. finally someone! ..thats good to know Im going to try it now, I didnt think it would be as simple as a move command.. any reason the radio wipes the cache partition?
Click to expand...
Click to collapse
I realize I wasn't completely clear. I don't know why the OTA radio update wiped my cache partition. Perhaps someone familiar with the update process (ChiefzReloaded) can explain this.
turboyo said:
did dalvik recreate itself after the wipe in /data?
Click to expand...
Click to collapse
If you wipe only the cache partition, you will need to recreate the dir /cache/dc but not the symlink. If you wipe only the data partition, you will need to recreate the symlink, but not the dir. If you want to clear the dalvik-cache, just delete all the files in /cache/dc (they should be recreated on next boot). If you are accustomed to 'rm -R /data/dalvik-cache' to clear the dalvik-cache, you'll have to re-setup the symlink (and possibly the /cache/dc dir as well).
turboyo said:
and were ALL the apps gone or just the few that took up the memory?
Click to expand...
Click to collapse
None of the apps are 'gone' per se, but since the /data/dalvik-cache dir is just a symlink to a non-existant dir (/cache/dc), the system can't create a dir that already exists (/data/dalvik-cache) and can't write anything to a dir that doesn't exist (/cache/dc), so it won't show any of the apps. It is an easy fix to just recreate the /cache/dc dir and reboot. None of your apps need to be reinstalled, since they are still in the /data/app dir.
reukiodo said:
None of the apps are 'gone' per se, but since the /data/dalvik-cache dir is just a symlink to a non-existant dir (/cache/dc), the system can't create a dir that already exists (/data/dalvik-cache) and can't write anything to a dir that doesn't exist (/cache/dc), so it won't show any of the apps. It is an easy fix to just recreate the /cache/dc dir and reboot. None of your apps need to be reinstalled, since they are still in the /data/app dir.
Click to expand...
Click to collapse
Awesome, that cleared it up. Will be doing this now.
alright bringing this back up, works great but .. Just in case how do we move dalvik back to data with out loosing apps or anything?
turboyo said:
alright bringing this back up, works great but .. Just in case how do we move dalvik back to data with out loosing apps or anything?
Click to expand...
Click to collapse
I'm guessing you can do these in recovery:
rm /data/dalvik-cache
mv /cache/dc /data/dalvik-cache
rm -rf /cache/dc
But I haven't tested it. In theory it should work. The first command removes the symlink, the second moves the existing cache to the original location of dalvik-cache, and the last removes the copy of dalvik-cache on the cache partition.
I have tried this process, but shouldn't I see an increase in internal memory if you go to sdcard / phone storage?
Please advise, I am not totally clear of tthe process.
Can someone help?
I am very interested on this
UnkzDomain said:
I'm guessing you can do these in recovery:
rm /data/dalvik-cache
mv /cache/dc /data/dalvik-cache
rm -rf /cache/dc
But I haven't tested it. In theory it should work. The first command removes the symlink, the second moves the existing cache to the original location of dalvik-cache, and the last removes the copy of dalvik-cache on the cache partition.
Click to expand...
Click to collapse
It's up to you, but I would suggest just letting Android regenerate the cache...
rm /data/dalvik-cache
rm -R /cache/dc
riverajuan said:
I have tried this process, but shouldn't I see an increase in internal memory if you go to sdcard / phone storage?
Please advise, I am not totally clear of the process.
Can someone help?
I am very interested on this
Click to expand...
Click to collapse
It depends on how many applications you have installed, but you should see at least some kind of increase if you move the dalvik-cache off of /data and onto the /cache partition.
reukiodo said:
I was able to get dalvik-cache to /cache by going into clockworkmod recovery and accessing from adb:
mv /data/dalvik-cache /cache/dc
ln -s /cache/dc /data/dalvik-cache
After the files are moved and the symlink is created, you should have no problems when rebooting.
However, I came across a problem when I flashed the radio, since it wiped the cache partition. If you are missing all your installed apps in android, it might be that the cache partition was wiped. You need to recreate the /cache/dc folder and reboot.
Click to expand...
Click to collapse
I've moved dalvik-cache to /cache with a symlink. However, everytime i booted, /cache was 770 and not 771.
To solve this, I just add a little script in /system/etc/init.d
#!/system/bin/sh
#
# Change 770 to 771 /cache to enable dalvik-cache
/system/bin/chmod 0771 /cache
echo "*** cache updated ***"
exit
Name it for ex. 02cache and chmod 755 it.
reboot and the /cache should be 771 now and dalvik-cache should work fine without patching anything (I have a stock rooted froyo rom)
sibere said:
I've moved dalvik-cache to /cache with a symlink. However, everytime i booted, /cache was 770 and not 771.
To solve this, I just add a little script in /system/etc/init.d
#!/system/bin/sh
#
# Change 770 to 771 /cache to enable dalvik-cache
/system/bin/chmod 0771 /cache
echo "*** cache updated ***"
exit
Name it for ex. 02cache and chmod 755 it.
reboot and the /cache should be 771 now and dalvik-cache should work fine without patching anything (I have a stock rooted froyo rom)
Click to expand...
Click to collapse
forgive the newbness but to make that a script file do you just make that script into a .txt file and add it to system/etc/init.d? what exactly are you naming the file?
turboyo said:
forgive the newbness but to make that a script file do you just make that script into a .txt file and add it to system/etc/init.d? what exactly are you naming the file?
Click to expand...
Click to collapse
the init.d is a script. open it up and add those lines to it. then just save (do not change the file name when you save it)
turboyo said:
forgive the newbness but to make that a script file do you just make that script into a .txt file and add it to system/etc/init.d? what exactly are you naming the file?
Click to expand...
Click to collapse
I did it with "vi", a linux text editor.
You can name it whatever you like. the 2 first numbers are for the order of execution if you have more than 1 script in /etc/init.d/
sibere said:
I've moved dalvik-cache to /cache with a symlink. However, everytime i booted, /cache was 770 and not 771.
To solve this, I just add a little script in /system/etc/init.d
#!/system/bin/sh
#
# Change 770 to 771 /cache to enable dalvik-cache
/system/bin/chmod 0771 /cache
echo "*** cache updated ***"
exit
Name it for ex. 02cache and chmod 755 it.
reboot and the /cache should be 771 now and dalvik-cache should work fine without patching anything (I have a stock rooted froyo rom)
Click to expand...
Click to collapse
I have a Motorola Droid running froyo 2.2 FRG83 rooted. I don't have a /system/etc/init.d file, what's the correct permissions for it? And shouldn't the 771 actually be on /cache/dc instead of /cache as all the 771 does vs the 770 is add the execute bit for others so basically it changes from rwxrwx--- to rwxrwx--x.
Also, I am curious what happened before you added the script to change the permissions, were you able to still use the terminal app to get into the shell after booting?
To get /system/etc, you must boot into recovery mode
And I DO confirm to set 771 to /cache because the system rests it to 770 on each boot. For children folders, you can set 777, this will be kept even after a reboot.
Beleive me, that's how it works
Sent from my HTC Desire using XDA App
sibere said:
To get /system/etc, you must boot into recovery mode
And I DO confirm to set 771 to /cache because the system rests it to 770 on each boot. For children folders, you can set 777, this will be kept even after a reboot.
Beleive me, that's how it works
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
There is no need to boot into recovery mode to get to /system/etc which is the same as /etc. All you need to do is use either root explorer app or get the terminal shell prompt and then get into the directory after you mount it as read+write. Besides, how do you get into the /system/etc directory with recovery mode?
I know /cache is set to 770 after boot but since /cache/dc is the directory that you're dealing with and the only difference between 770 and 771 is the 1 adds the execution by others to the permissions so it doesn't give others read+write anyways as that requires another 6 so why wouldn't just setting 771 on /cache/dc work. Before you did the 771 on /cache, are you still able to boot and use the phone and the apps?
Almighty1 said:
There is no need to boot into recovery mode to get to /system/etc which is the same as /etc. All you need to do is use either root explorer app or get the terminal shell prompt and then get into the directory after you mount it as read+write. Besides, how do you get into the /system/etc directory with recovery mode?
I know /cache is set to 770 after boot but since /cache/dc is the directory that you're dealing with and the only difference between 770 and 771 is the 1 adds the execution by others to the permissions so it doesn't give others read+write anyways as that requires another 6 so why wouldn't just setting 771 on /cache/dc work. Before you did the 771 on /cache, are you still able to boot and use the phone and the apps?
Click to expand...
Click to collapse
This would normally be the case, however the slide doesn't have S-off like other phones, so we can't mount with r/w like you would.
Ace42 said:
This would normally be the case, however the slide doesn't have S-off like other phones, so we can't mount with r/w like you would.
Click to expand...
Click to collapse
Interesting. I guess what I'm trying to figure out is what happens if /cache is at 770, will the phone just force close on everything making it a brick at that point?
To get to /system/esltc in recovery, connect your phone to your PC and use adb
If you leave 770 to /cache, dalvik VM will not get access to the directory and will rebuild dalvik-cache in /data.
But man, if you don't trust me, you can always try yourself and make your own experiments
Sent from my HTC Desire using XDA App
Related
I update from Cronos Droid Version 1.4 to 1.4.1
In 1.4 rom ，there was about 140M left in my telephone memory
after the update ， there is only 108M left in the telephone memory
then I did this：
adb shell
su
cp -a /data/app /system/sd/
rm -r /data/app
ln -s /system/sd/app /data/app
reboot
there is still 108M left
Then I find the apks exist under data/app also exist under system/sd/app
if i delete the apk under data/app,the same apk will also disappear
WHY
PS after full wipe and I flash the 1.4.1 ,reboot,flash the app2sd.zip ,the phone died,the 1.4.1 means this one :StableCronos_4.1_528_fix_sign.zip
108 sounds about right mate it sounds like before it was moving dalvik cache to sd card as well and now it is not
If you installed some apps from HTC Sync, the copy of the apks could still be on your phone. I can't use adb from work to tell you where it is exactly, but I think it's in /data/local (or something like that, it's in a "local" folder)
Isn't it possible the new rom takes 32mb memerie more than your older rom? I don't know the differences between the roms, but it might be it..
skedone said:
108 sounds about right mate it sounds like before it was moving dalvik cache to sd card as well and now it is not
Click to expand...
Click to collapse
So,how can i move dalvik cache to sd card
kouray said:
If you installed some apps from HTC Sync, the copy of the apks could still be on your phone. I can't use adb from work to tell you where it is exactly, but I think it's in /data/local (or something like that, it's in a "local" folder)
Click to expand...
Click to collapse
yes，you are right
but why the apps in the /data/app??
if you really want to move your Dalvik cache to your sd-card you could flash the latest Ra-Hero recovery image.
it has an option to move Dalvik + apps to your sd-card ( this won't enable apps2sd though )
Hello again everybody.
Here is a little tutorial to get rid of the crap thats shipped with the phone
and get it on a sweet diet of slimfast.
If you think to yourself "HEY! that shouldn't be removed!"
I most likely removed it because there is a Market alternative.
*Always be careful when modifying /system*
First we need to remount our phone and make /system/app - R/w
adb remount
then type:
adb shell
*In Shell ($)
su (IMPORTANT)
cd /system/app/
ls
Now you can start removing the bloat.
rm Launcher.* (ONLY IF YOU HAVE AN ALTERNATIVE LAUNCHER INSTALLED!)
rm Maps.*
rm SystemTutorial.*
rm LatinIME.* (MAKE SURE YOU HAVE ANOTHER KEYBOARD INSTALLED)
rm Email.*
rm Calculator.*
rm EmotionWeather.*
rm EmotionPhotoWidget.*
rm EmotionCalendar.*
rm EmotionPhotoAlbumWidget.*
rm EmotionBookmarksWidget.*
rm EmotionEvents.*
rm Twidroid.*
rm EmotionMemo.*
rm EmotionRSSReader.*
rm EmotionVideoWidget.*
rm EmotionClockWidget.*
rm HwIME.*
as always, reboot.
and, as with most things in the filesystem, this can also be done
with Root Explorer
If you messed something up, it probably wasn't meant to be
removed and most likely wasn't listed above. Start over from scratch...
unless you made back-up of course
If i missed anything, shoot me a message!
You honestly consider Calculator, Maps and Email "bloatware"?
raduque said:
You honestly consider Calculator, Maps and Email "bloatware"?
Click to expand...
Click to collapse
if they can be downloaded (and be more up to date from the market) then yeah.
You don't need to delete them to download the updated versions. My tablet prompted me to update them as soon as I connected to wifi and logged into my google account.
Updates take more space
When you update a Android app that is part of the rom it takes up 1.5 to 2x the storage than if you just simply download the newest version.
crispien said:
When you update a Android app that is part of the rom it takes up 1.5 to 2x the storage than if you just simply download the newest version.
Click to expand...
Click to collapse
That honestly means nothing to me. I don't load 500 apps on my devices.
raduque said:
That honestly means nothing to me. I don't load 500 apps on my devices.
Click to expand...
Click to collapse
look, when you delete /system files obviously it doesn't touch the /data... obviously... now your /system is on your INTERNAL partition so removing these files frees up space on your INTERNAL memory, and as for obviously downloading the updated apps from the market does update them YES AND INSTALLS THEM INTO /data, but it does not delete the OLD outdated version which still reside in /system which need to be updated and is taking up space, i hope this helps you understand whats going on... hopefully.
joenilan said:
look, when you delete /system files obviously it doesn't touch the /data... obviously... now your /system is on your INTERNAL partition so removing these files frees up space on your INTERNAL memory, and as for obviously downloading the updated apps from the market does update them YES AND INSTALLS THEM INTO /data, but it does not delete the OLD outdated version which still reside in /system which need to be updated and is taking up space, i hope this helps you understand whats going on... hopefully.
Click to expand...
Click to collapse
Yes, I understand this. But, they are two separate partitions. The S7 does not dynamically resize partitions. /system and /data are completely self-contained, and the size of either does not effect the other.
Space on /system, does not effect space on /data. I don't know how much plainer I can say this. All you're doing is freeing space on /system, but nothing goes there except pre-installed *system* files!
The bolded, underlined, italicized is the part that doesn't make any sense. It's taking up space in /system, which has no bearing on space in /data. Period, end of sentence, full stop. I'm not saying anything more on this matter, because I don't think you're going to get it.
raduque said:
Yes, I understand this. But, they are two separate partitions. The S7 does not dynamically resize partitions. /system and /data are completely self-contained, and the size of either does not effect the other.
Space on /system, does not effect space on /data. I don't know how much plainer I can say this. All you're doing is freeing space on /system, but nothing goes there except pre-installed *system* files!
The bolded, underlined, italicized is the part that doesn't make any sense. It's taking up space in /system, which has no bearing on space in /data. Period, end of sentence, full stop. I'm not saying anything more on this matter, because I don't think you're going to get it.
Click to expand...
Click to collapse
probably not, i can't get through the fog of cocky responses. instead of being a helpful person.
joenilan said:
probably not, i can't get through the fog of cocky responses. instead of being a helpful person.
Click to expand...
Click to collapse
Well, that's an interesting way of saying that you don't understand what I'm saying.
http://forum.xda-developers.com/showpost.php?p=11476068&postcount=9
Repeat after me:
"/system space is completely separate from /data space. One has no bearing on the other"
Once you have saved some room on /system/app, you can then move some of the apps that you have in /data/app to that directory. I have done this for swype, adw, facebook, google apps, documents to go for example, this is saving me an extra precious 40M.
dear joenilan..
pls help..i have remove the home launcher .replace with vtl.
i do factory reset and forgot restore with Titanium before
now face boot loop ..what should i do now.
dont have cwm in my ideos
thx big for advice
rgds
sasmitadani :
Flash a new room,
http://forum.xda-developers.com/showthread.php?t=1043349
http://phonedock.net/huawei-ideos-s7-froyo-2-2-2-update.html
http://www.androidtablets.net/forum...uawei-ideos-s7-official-firmware-2-2-2-a.html
I would also request that the OP's post be removed, or huge big letters of warnings or better described procedures be added, this can be very harmful and really makes no sense.
it does it everywhere else except for the system folder. i really want to get this version of pandora off, but it's not doing anything. it worked with my other android devices, not sure why it's happening with this
Do you have the latest version of Root Explorer?
yeah what version of root explorer???
Generally if you can mount R/W in other folders you should also be able to do so in the system folder. You may have already tried this but you may want to boot into recovery and wipe cache and try again. If you have ADB set-up you should also be able to mount the device in R/W by doing the following command: su [enter] mount -o remount,rw -t /dev/block/mtdblock5 /system [enter] if that goes out without a hitch you should be able to delete in the system folder. You can also put that command in to terminal (if you have it) and that also should put the system into R/W. To remount the device in R/O just replace rw with ro. Hope this helps.
2.9.3...wow i'm restarted...i updated and it works now
I have had this issue a couple of times and a simple reboot has fixed it.
Sent from my B.A.M.F. Thunderbolt
Of the 20+ Android phones I have had, and each being rooted and ROM'd, this is the first that I have seen.
On the TPC ROM, when my phone boots, my /system & /etc are mounted by default as Read/Write rather than Read Only. I have no such problem when I flash SAUROM.
I can set it to R/O, reboot, it becomes R/W again.
I asked the question in the ROM thread but got no help. It seems that others don't have this problem.
Why is this and how do I fix it?
Thanks.
Edit: The mount point is /dev/block/mmcblk0p24 for /system and /etc. There are some remount commands in a file located in init.d. Could that be the cause?
I'm no dev, but have you looked at the superuser logs to see what app might be changing r/rw modes? You say when you reboot it changes back. So that makes me think an app you have auto starting is mounting the system rw to make a change and failing to mount back to R.
Go in SuperUser.. clear the logs, set it to R, make note that it saved that change in the log using whatever program you use it to set with... Reboot, check Superuser logs to see what gained root and changed it back.
snovvman said:
Of the 20+ Android phones I have had, and each being rooted and ROM'd, this is the first that I have seen.
On the TPC ROM, when my phone boots, my /system partition is mounted by default as Read/Write rather than Read Only. I have no such problem when I flash SAUROM.
I can set it to R/O, reboot, it becomes R/W again.
I asked the question in the ROM thread but got no help. It seems that others don't have this problem.
Why is this and how do I fix it?
Thanks.
Click to expand...
Click to collapse
jb0nd38372 said:
I'm no dev, but have you looked at the superuser logs to see what app might be changing r/rw modes? You say when you reboot it changes back. So that makes me think an app you have auto starting is mounting the system rw to make a change and failing to mount back to R.
Go in SuperUser.. clear the logs, set it to R, make note that it saved that change in the log using whatever program you use it to set with... Reboot, check Superuser logs to see what gained root and changed it back.
Click to expand...
Click to collapse
Thanks for the suggestion. I removed all the apps that requested SU on boot, but the ROM still had /system as R/W. I don't think it's an app doing it.
Is there a way for me to add something into a boot script to set it as R/O?
Thanks.
I'm still trying to track down this problem.
I noticed that /etc also mounts as R/W by default. I see that both /system and /etc share the same mount point: /dev/block/mmcblk0p24.
I look in init.d and found one file which contained these lines:
#mount fs for faster IO speeds
mount -o remount,nodev,noatime,nodiratime /dev/block/mmcblk0p24 /system
mount -o remount,noauto_da_alloc,nodev,noatime,nodiratime /dev/block/mmcblk0p25 /data
mount -o remount,noauto_da_alloc /dev/block/mmcblk0p26 /cache
Would the first line cause this?
Is there something I can add to init.d to re-mount as R/O?
I'm still curious as to what is causing this. Thanks for any help.
Through trial and error, I found this command works to set /system and /etc to RO:
mount -o remount,ro /dev/block/mmcblk0p24 /system
I added it to init.d, and it works. Once the phone completes the boot, those directories are RO. It's just a patch.
But nevermind that--I am still very interested in the "why" and if there is some other script/boot command somewhere that is causing this.
I'd appreciate some guidance. Thanks.
Move dalvik-cache to /cache
import /disclaimer.md
Code:
I am not responsible for any damage done to your device/SD card/OTG cable/washing machine etc.
You are responsible for what you do.
If something brakes, it's on you!
This has only been tested on a CM13-based ROM. I have no idea how it will function on other ROMs because of the size of the dalvik-cache directory.
I have found that, on CM13-based ROMs, the dalvik-cache directory is small enough to fit in the /cache partition, giving us several MBs on /data
Current state: Beta
Reason: Not fully tested (on all ROMs)
Comment: Stable enough for daily use
Installation:
Busybox required!
Download the attached zip and flash it in recovery.
Or extract the script from the zip, put it in /system/etc/init.d/ , set the permissions to 755 (rwxr-xr-x) and ownership to 0, 2000 (root, shell).
Uninstallation:
Delete /system/etc/init.d/10dc-linker and /cache/dalvik-cache
To-Do:
Add a size checker
Make suggestions
Bugs:
Found one? Let me know!
Changelog:
v1.0:
First release
Reserved
Didn't work for me on CM13 Xperia SP.
kkumar326 said:
Didn't work for me on CM13 Xperia SP.
Click to expand...
Click to collapse
How much space do you have on /cache?
Also, what exactly is not working?
What is the state of SELinux?
Complete Data
This is what I did:
1) Extracted zip and pasted 10dc-linker in init.d
2) Rebooted phone with twrp recovery
3) Cleared dalvik-cache
4) Rebooted
Result: Nothing happened
Probable cause: Access problem to move/create folders as I couldn't change permissions for /cache , /data and /data/dalvik-cache folders manually using root explorer. It gets reverted back to original. My access was also restricted to root, there was no shell.
Probable fix: Adding script to gain permission to modify/ create in these folders. Plus adding access to both root and shell. I also read somewhere about superuser access to get permission but I couldn't understand.
My cache folder has about 600 MB space and it's completely empty. There is no issue with the space.
Please let me know about your step by step process and probable fixes. Maybe it works.
kkumar326 said:
This is what I did:
1) Extracted zip and pasted 10dc-linker in init.d
2) Rebooted phone with twrp recovery
3) Cleared dalvik-cache
4) Rebooted
Result: Nothing happened
Probable cause: Access problem to move/create folders as I couldn't change permissions for /cache , /data and /data/dalvik-cache folders manually using root explorer. It gets reverted back to original. My access was also restricted to root, there was no shell.
Probable fix: Adding script to gain permission to modify/ create in these folders. Plus adding access to both root and shell. I also read somewhere about superuser access to get permission but I couldn't understand.
My cache folder has about 600 MB space and it's completely empty. There is no issue with the space.
Please let me know about your step by step process and probable fixes. Maybe it works.
Click to expand...
Click to collapse
The script must have 755 or 777 permissions or it won't work.
Also, the zip is flashable. Just flash it in recovery and it will setup everything by itself.
When I flashed it, google-play-services fc like crazy until I restore a backup
Miasaya said:
When I flashed it, google-play-services fc like crazy until I restore a backup
Click to expand...
Click to collapse
What happens if you flash the zip and wipe dalvik-cache?
Does it still fc?
Didn't work with flash
Vagelis1608 said:
The script must have 755 or 777 permissions or it won't work.
Also, the zip is flashable. Just flash it in recovery and it will setup everything by itself.
Click to expand...
Click to collapse
I flashed zip too but nothing happened. No folder was created or moved.
Man use this utility http://forum.xda-developers.com/g2-mini/development/d620-partition-table-tool-t3107664
But choose "optimal" partition layout.
kkumar326 said:
I flashed zip too but nothing happened. No folder was created or moved.
Click to expand...
Click to collapse
Did you wipe dalvik-cache and /cache after flashing?
Lion_Smith said:
Man use this utility http://forum.xda-developers.com/g2-mini/development/d620-partition-table-tool-t3107664
But choose "optimal" partition layout.
Click to expand...
Click to collapse
Sure, go on dev threads and advertise other people's work. That's highly appreciated.
That's why we can't have nice things...
Found the Reason
Vagelis1608 said:
Did you wipe dalvik-cache and /cache after flashing?
Sure, go on dev threads and advertise other people's work. That's highly appreciated.
That's why we can't have nice things...
Click to expand...
Click to collapse
My dalvik-cache is shooting up to 400+ MB, that's why it's not working. I moved /data/dalvik-cache to /cache/dalvik-cache. Then, I used terminal command after su command to link them
Code:
ln -s /cache/dalvik-cache /data/dalvik-cache
It worked but my phone started showing errors with low memory notifications.
1) Is there a way to limit dalvik-cache size?
2) Another approach can be to increase /cache size with with some additional memory e.g. 100 MB, and then following this might work. There will still be a gain of 300+ MB of memory.
Please let me know what's possible.
kkumar326 said:
My dalvik-cache is shooting up to 400+ MB, that's why it's not working. I moved /data/dalvik-cache to /cache/dalvik-cache. Then, I used terminal command after su command to link them
It worked but my phone started showing errors with low memory notifications.
1) Is there a way to limit dalvik-cache size?
2) Another approach can be to increase /cache size with with some additional memory e.g. 100 MB, and then following this might work. There will still be a gain of 300+ MB of memory.
Please let me know what's possible.
Click to expand...
Click to collapse
You can't limit dalvik-cache size, sadly.
If there is enough space for dalvik-cache on /cache, then the script should work.
Also, could you give me the output of this command on a rooted shell?
Code:
ls -l /data/dalvik-cache
It's a small L.
Vagelis1608 said:
You can't limit dalvik-cache size, sadly.
If there is enough space for dalvik-cache on /cache, then the script should work.
Also, could you give me the output of this command on a rooted shell?
Code:
ls -l /data/dalvik-cache
It's a small L.
Click to expand...
Click to collapse
rwxrwxrwx 1 root root [date] [time] /data/dalvik-cache -> /cache/dalvik-cache
kkumar326 said:
rwxrwxrwx 1 root root [date] [time] /data/dalvik-cache -> /cache/dalvik-cache
Click to expand...
Click to collapse
My bad.
I forgot to mention with and without the script installed.
What's the output without the script installed?
Script not working
Vagelis1608 said:
My bad.
I forgot to mention with and without the script installed.
What's the output without the script installed?
Click to expand...
Click to collapse
Script is not doing anything at all as I told earlier. That's why I did it manually.
Lion_Smith said:
Man use this utility http://forum.xda-developers.com/g2-mini/development/d620-partition-table-tool-t3107664
But choose "optimal" partition layout.
Click to expand...
Click to collapse
This is intended to work on a LG G2 Mini, not any other phone.
kkumar326 said:
Script is not doing anything at all as I told earlier. That's why I did it manually.
Click to expand...
Click to collapse
I want the output without it linked.