Related
I have been searching for a clear guide to enabling compcache on 3.9.2, but there is so much info about swap and compcache in this forum i feel like im running around like a chicken with its head cut off.
so far i have pushed 3 different userinit.sh files into my /system/sd with no change.
#free shows 0 swap , #cat /proc/ramzswap says doesnt exist , #cat /proc/swaps comes up blank.
So i searched more and ended up making a 32mb linuxswap partition on my sd and cant figure out how to get that moving either.
Im bogged down with information and have no idea where to start.
Someone point me in the right direction please. Im a swap/compcache noob...
i would like to run them both together, but as i said i need a noob setup guide
Your /system/sd is a mounted ext filesystem, correct?
Push the userinit.sh from here:
http://forum.xda-developers.com/showthread.php?t=542304
Then run it as root and report back any results:
# /system/sd/userinit.sh
i pushed userinit.sh to /system/sd/ with adb
then put in console
su
# /system/sd/userinit.sh and got /system/sd/userinit.sh: permission denied
should i be doing this in the recovery console?
and what did u mean by: is my system/sd/ a mounted ext filesystem?
i did adb remount to mount /system/ as r/w if thats what you meant.
let me apologize once again. i have almost no knowledge of linux commands. a step by step would really save some time. the only thing i hate more than not understanding something, is wasting others time while i do it.
ShatBag1105 said:
and what did u mean by: is my system/sd/ a mounted ext filesystem?
Click to expand...
Click to collapse
sounds like you did not set up a second partition (or a 3rd for that matter) on your sdcard.
there are many different ways to do this (I prefer gparted in linux), but here's one guide that uses parted in cyanogen's 1.4 recovery image:
http://forum.xda-developers.com/showthread.php?t=534714
hit me up if you hit a snag
gl
im pretty sure you are right. My mmcblk0p2 exists (of course) but when I check # /dev/block/mmcblk0p3 it says not found. And if I # ls /dev/block/mmcbl0p3 it says no such file or directory.
Im guessing i botched something in paragon partition 9. if i remember correctly i put the 32mb linuxswap partition between my fat32 and ext3.
Do u think i should create a new linuxswap partition after my ext3 with paragon9, or is there a workaround for my mistake? does the phone even recognize my poorly placed partition as anything?
thanks so much for your help. after a few hours of reading all these threads Ive come to realize you are the resident expert in swap compcache scripts. as for myself.... not so much
ext should be 2nd partition.
...and linux swap 3rd if you're using it (but it's not needed for compcache -- only as a backing swap).
I'd kill them both and readd with some variant of parted -- i've read that some are having trouble w/ paragon partitioning
Very well then. Ill reformat today and report back.
First of all! Paragon Partition Manager is a FARCE!
Gparted Live CD was awesome. Paragon had my sdcard looking pretty bad. I had 32mb of unallocated space between my FAT32 and EXT3. Even though paragon was telling me it was formatted to linuxswap.
I moved my ext3 over and created a 32mb linuxswap at the end of the sdcard with no loss of data. wow
But sadly, i pushed the userinit.sh #free shows 0 swap and #cat /proc/swaps shows nothing.
Im going to try this >> http://forum.xda-developers.com/showthread.php?t=542899 <<<WORKED!!
What ive learned:
Use Gparted to create a linuxswap partition AFTER your EXT3. Paragon is pure ****.
Get the user.conf and userinit.sh file from the link in above post.
Put them in the root of your sd card
I DID THIS WITH TERMINAL
su
mount -o remount,rw /dev/block/mtdblock3 /system
cp /sdcard/userinit.sh /system/sd
cp /sdcard/user.conf /system/sd
chmod 755 /system/sd/user.conf
chmod 755 /system/sd/userinit.sh
type #sh /system/sd/userinit.sh into console to activate the script.
type #sh /system/sd/userinit.sh -s to get a pretty well detailed report of the goings on.
OOOh being a linux noob is much headache.
Alpapa Thanks for giving me your time and pointing me in the right directions. Thanks man.
ShatBag1105 said:
Use Gparted to create a linuxswap partition AFTER your EXT3. Paragon is pure ****.
push the user.conf file (from link in above post) to /system/sd along with your userinit.sh.
type #sh /system/sd/userinit.sh into console to activate the script.
type #sh /system/sd/userinit.sh -s to get a pretty well detailed report of the goings on.
OOOh being a linux noob is much headache.
Alpapa Thanks for giving me your time and pointing me in the right directions. Thanks man.
Click to expand...
Click to collapse
I'm a newb as well... so did you chmod either of those files after moving them to ext2/3?
Yes. You have to chmod both of them.
And this works on 3.9.4.
V 0.1 files work best.
http://forum.xda-developers.com/showthread.php?t=542899
And these files come with everything disabled, so you have to edit both of them and enable what u want before putting them on your sd.
0=disabled
1=enabled
just wondering if im doing something wrong? got NV installed with all 3 partitions and I had 77mb of internal mem. when I install new apps it takes away mem, am I doing something wrong, did I not config something right? I have read that apps2sd are automatic and to do nothing or it will break the system. dont mind the 77mb but would like to have my apps on my sd. any help would be great.
Do you have ext3? Drizzy expressly says you need it. So I assume if you only have ext2 there might be probs with your a2sd.
If that's not it. Did you follow all of these steps before flashing?...
This is how I installed without any problems:
: rename to update.zip
: place in the root of sd card
: shut off device
: boot into recovery
: wipe
: go to console and hit enter
(enter)
# mount -o rw /dev/block/mmcblk0p2 /system/sd
# cd /system/sd
# rm -rf /system/sd/*
# reboot recovery
: now wipe again
: repair ext system
: flash
Enjoy!!
"DO NOT RUN ANY OTHER APPS TO SD IT WILL BREAK YOUR SYSTEM"
JUST EXT3 & LINUX-SWAP 32MB
kree said:
just wondering if im doing something wrong? got NV installed with all 3 partitions and I had 77mb of internal mem. when I install new apps it takes away mem, am I doing something wrong, did I not config something right? I have read that apps2sd are automatic and to do nothing or it will break the system. dont mind the 77mb but would like to have my apps on my sd. any help would be great.
Click to expand...
Click to collapse
your apps are going to the sd..your dalvik-cache is not
yup. checked thru the the console that in fact I do have an ext3 partition. I went thru an infinate loop with out it, also followed all the steps as best as an old newb could, I mean Im not new to flashing roms coming from the herald and wing, but concidering ow these android roms are becoming like full linux distro installs its getting a little hard to keep up, but still willing to try. gonna look up the dav thing to see where that leads me. definately an adventure! thanks!
Any mytouch users who are currently using Bart or Switchrom, can you please pm and tell me how you did it please! Thanks alot
I got it to work.!
I repartitioned.
with adb shell.....
well i tried but its not mounting for me when i do mount/dev....
Code:
adb shell
mount /system/sd
whatever commands are from the guide to use the utility.
i get that error
Code:
mount: mounting /dev/block/mmclbk0p2 on /system/sd failed: no such file or directory
That command is used to mount your ext partition. Either you don't have one or it's corrupted in some way...
when i rotoed my mytouch, Cyan's rom automatically did a partition for me. should i partition it again?
before i partition can i back up my apps on the ext in anyway, i have to many i dont want to lose them.
you can look for a back up app in the market, and how did the rom partition your sdcard?
Cyan's rom doesnt partition automatically...it sets up apps2sd automatically if you have an ext partition
i have no idea how, but i have 214 mb internal storage
could be because you have a mytouch which has twice the rom as a g1.
if you want to see if you have an ext3 partition do this in the terminal
ls /system/sd
I had tried many ways including A2SD and stuffs. But the best way I found is mounting /dev/block/mmcblk0p2 -> /data. I had also modified some scripts and now my htc salsa is having huge internal memory over my sdcard. The methods are in my blog.
New URL: http://wiki.bluebert.info/index.php?title=HTC_Salsa_C510e_Rooting
Some of the details and images are from here and files too. The only difference is I am using the recovery method to alter some scripts and forever it will auto mount the second partition of my sdcard to /data and I will never ever worry about the internal memory issue for my htc salsa
Please update the link
hi,
Can you please update the link as i am not able to browse it.Thanks in advance
wiki.bluebert.info/index.php/HTC_Salsa_C510e_Rooting
If unable to view please let me know. Thanks.
Its nice Blog
Hi,
Thanks for updating the link.I read your blog and have few queries:-
What happens when you connect your device to PC. Memory card is unmounted.So your phone thinks that internal memory is unmounted?
Did you got my point?
Can you tell me what are these partitions?
/dev
/mnt/asec
/mnt/obb
These three partitions take 209mb individually.
What about the battery.How is your phone's battery backup?
chinu1984 said:
Hi,
Thanks for updating the link.I read your blog and have few queries:-
What happens when you connect your device to PC. Memory card is unmounted.So your phone thinks that internal memory is unmounted?
Did you got my point?
Can you tell me what are these partitions?
/dev
/mnt/asec
/mnt/obb
These three partitions take 209mb individually.
What about the battery.How is your phone's battery backup?
Click to expand...
Click to collapse
1. The memory card only will be unmounting the FAT32 partition but not the EXT3/EXT2 partition. It just thinks that is another disk Currently the latest file system I am using is ext3 instead of ext2.
2. /dev: is the folder that contains all the devices files and pointers.
/mnt/asec: is the mount point for the apps that had moved to SDCard. url: groups.google.com/group/android-porting/browse_thread/thread/38b1768ed6a5e1a8
/mnt/obb: StorageManager is the interface to the systems storage service. The storage manager handles storage-related items such as Opaque Binary Blobs (OBBs).
OBBs contain a filesystem that maybe be encrypted on disk and mounted on-demand from an application. OBBs are a good way of providing large amounts of binary assets without packaging them into APKs as they may be multiple gigabytes in size. However, due to their size, they're most likely stored in a shared storage pool accessible from all programs. The system does not guarantee the security of the OBB file itself: if any program modifies the OBB, there is no guarantee that a read from that OBB will produce the expected output.
What do you mean about the phone battery backup?
Basically, what I am doing is actually making sure that even I unplug my /data my phone still be able to start back and also I can have any size for my internal memory. Currently, I had migrated to a 16GB class 10 sdcard and it performs like a charm.
I had noticed on my 8GB class 4 SDCard a bit lagging. So try to get a high speed sdcard and it really helps on this case. So once you had done this mod and you still maintains the original HTC firmware yet you get a very large internal disk.
But remember, whatever you do on the phone, please backup the images using the ClockworkMod. It will save your life. Happy modding
Summarize of the increasing internal memory process...
1. Make sure S-OFF
2. Flash the recovery partition with the clockworkmod
3. Boot into clockworkmod recovery and backup the original /data /system and all the partitions using the clockworkmod recovery.
4. Install the root.zip using the clockworkmod for rooting it
5. If fails we still able to revert back to original firmware.
6. If everything good, you should be root now. Once you get the root, install busybox and superuser. This is needed for the partition process.
7. Reboot back to recovery and make another backup.
8. Make the new ext2 partitions using the busybox or you can do this on any linux terminals on your desktop pc.
9. Upload the modified htcfs and copy everything from /data -> new ext2 partition.
10. The htcfs will auto mount the /data before everything starts and there you go with your newly created partitions size. This is how you get the huge internal memory size on your sdcard.
2nd day of my usage of the /data on sdcard.
I had bought a 16GB class 10 SDCard and partitioned into 4GB for /data as ext3 and the rest for /sdcard as fat32. Currently, I am consuming only 342MB/3.6GB. Which I am quite happy with it.
Below are the things I had found out:
1. Sometimes when there are some heavy process on going it will be a bit slow. Especially when turning on the screen after the screen when to power saving mode. Not all the time but when it is heavily transferring something inside the /data which is the sdcard. This is why we need a high speed sdcard.
2. I am using ext3 instead of ext2. ext3 partition seems a bit stable than ext2. I am not sure yet but will keep on trying.
I will keep on posting and hopefully people out there can do the same on the phone for enjoying the huge internal data storage for the apps. Now I no longer need to remove my apps away from my phone anymore
this sounds like a fantastic idea
i have a questioned
i rooted my gf's phone,installed links2sd,created a ext2 partition and removed a whole bunch of bloat
would me using your method now cause problems or instability on her phone?
i'd love to try this out tonight if possible
vickyboicancan said:
this sounds like a fantastic idea
i have a questioned
i rooted my gf's phone,installed links2sd,created a ext2 partition and removed a whole bunch of bloat
would me using your method now cause problems or instability on her phone?
i'd love to try this out tonight if possible
Click to expand...
Click to collapse
It may unstable unless you are pretty clear what you are migrating and redo the softlink.
The best to try with a clean and possible a few important apps installed like the file expert, root checker, superuser and busybox then you copy the whole /data to the ext2 partition of the sdcard and mount it with my method.
Again, remember to back up everything before trying it.
http://www.facebook.com/pages/HTC-Android/265046560194954
This is my FB HTC page.
Found some minor bug but is repairable. As long as you do not eject the sdcard after power off the HTC (where I had already enabled the fastboot) then everything should be fine. But just in case, like my case I had switched off the phone then I eject my sdcard for copying some files and reinsert it back then power on the phone and all my apps become unstable and not usable. This is because I had enabled the fastboot and some files are reside in the memory.
What you can do is:
1. Do not panic. Let it starts. Everything still in the ext3 partition.
2. use the adb command and run as below:
# sudo adb shell
# /system/bin/fix_permissions
If you have encounter some cut command not found that is not a main issue. Is fixable. You just need to remount the /system folder as rw and softlink the busybox as cut. Something like below:
# su
# mount -o rw,remount dev/block/mtdblock3 /system
# cd /system/xbin/
# ln -s busybox cut
Once done, re-run the /system/bin/fix_permissions again.
3. Wait for the process the fix all the file permission issues.
4. Then reboot the phone again:
# adb reboot
What is the fix_permissions about? Below link is the details on it:
http://wiki.cyanogenmod.com/wiki/Fix_permissions
mount Internal to internal??
Hi,
In spite of mounting and external drive with ext-3 partition onto /data. cant me mount an internal drive may be /dev/obb onto /data?
What will be the advantages and disadvantages?
chinu1984 said:
Hi,
In spite of mounting and external drive with ext-3 partition onto /data. cant me mount an internal drive may be /dev/obb onto /data?
What will be the advantages and disadvantages?
Click to expand...
Click to collapse
Defeating the purpose. The reason why we need to mount to the sdcard is to get extra disk space. I am using this method to trick the system thinks that it have a very huge space and eventually all from the external sdcard partition.
The /dev/obb... is just a tmpfs. Try to do a mount command to get the output then you will get a clearer picture on this. For my case, is /mnt/obb and just a tmpfs which is useless.
tmpfs is a temporary file system where it will be gone after power off.
Hi,
Where can i get this XTC Clip to S-OFF??
chinu1984 said:
Hi,
Where can i get this XTC Clip to S-OFF??
Click to expand...
Click to collapse
Read my Facebook page on the last second post.
Below images are the screenshots from my HTC Salsa.
{
"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"
}
The above image is after the /data remounted to my sdcard. Originally was 150MB and now is 4GB.
After I had installed many apps I am still having lots of space.
I had simplified the process:
What I am intend to do is to extend the /data (internal memory) to sdcard.
1. Install Busybox.
2. Install Sudo Checker and all the sudo tools.
3. Once this done, we will need to partition the sdcard. Please be making sure all the data are backup. I am not going to be responsible on that
4. Use the hardware method by pressing the volume down and power button to enter the recovery mode or using the adb command "adb reboot recovery".
5. Use the recovery tool and backup the existing working image to the sdcard before proceeding next step. It will be useful to have the recovery image in hand. You will never know when you going to make the mistakes.
6. Once done, lets proceed with the adb command on the linux / windows terminal.
7. Before we start lets prepare some simple shell scripting. What we are trying to do here is to create a file and replaces the existing htcfs on the /system/bin/htcfs. I am not sure what is the use of mounting this htcfs on /data/htcfs and is empty. But I will put back this to my script in future. What I had done was move the original htcfs to htcfs.original and put my version of htcfs which it will auto starts every power off or reboot. Below are the codes:
Filename: htcfs
#!/system/bin/sh
/system/xbin/busybox mount -t ext2 /dev/block/vold/179:2 /data
/system/bin/htcfs.original $1 $2 $3 $4 $5 $6
8. Now lets rename the original htcfs in the phone before we copy our version into the phone. At the same time we do partitioning on the SDcard.
# adb shell
# mount -a
# cd /system/bin/
# busybox cp htcfs htcfs.original
# exit
# adb push htcfs /system/bin/
# adb shell
# cd /system/bin
# chmod 755 htcfs
# chown root.shell htcfs
# fdisk /dev/block/mmcblk0
# mkfs.ext2 -m 0 /dev/block/mmcblk0p2
# mount /dev/block/mmcblk0p2 /sd-ext
# cd /data
# busybox cp -a . /sd-ext
# sync
# cd /
# umount /sd-ext /sdcard /data /system
# exit
# adb reboot
The above steps are creating an EXT2 partition on the SDCard. My version I created a 1.5G as my /data space.
So, basically the htcfs is mounting the /data from my sdcard on every reboot before all the applications start up. There is a step to copy all existing /data to the sd-ext and that is the trick to make the phone thinks that is using the internal memory and we have no longer facing insufficient disk space on cheaper android phones or on some branded HTC phones with little amount of internal disk.
Remember, the above steps are only for rooted phones. My phone until now still working great and with 4GB internal memory (mounted from SDCard as ext3).
I am working on a Linux Terminal for the above steps.
I have problem to get XTC Clip.
Is it possible we can S-Off without using XTC Clip?
luxoriouz said:
I have problem to get XTC Clip.
Is it possible we can S-Off without using XTC Clip?
Click to expand...
Click to collapse
Not at the moment.
Link2SD GUIDE
ROOTED DEVICES ONLY
Link2SD is a good solution to save the contents of your internal memory, I know we have a lot but its a good idea in the case of saving more space on your internal memory.
Back up your external sd contents before proceeding!
STEP 1
Install these:
https://play.google.com/store/apps/details?id=stericson.busybox
https://play.google.com/store/apps/details?id=com.sylkat.AParted
https://play.google.com/store/apps/details?id=com.broodplank.initdtoggler
https://play.google.com/store/apps/details?id=jackpal.androidterm
STEP 2
If you've already installed busybox, skip this step.
Install busybox using the busybox installer into /system/xbin
STEP 3
After install, unmount your external sd card from System/Storage/Unmount SD Card
THEN, unmount your external sdcard and sdext2 partition if you have one, from terminal emulator.
Thsi varies from ROM to ROM, I'm on CM11, so I run these commands
Code:
mount -o remount,ro /storage/sdcard1
umount /storage/sdcard1
mount -o remount,ro /data/sdext2
umount /data/sdext2
If you're stock, do this...
Code:
mount -o remount,ro /storage/external_SD
umount /storage/external_SD
mount -o remount,ro /data/sdext2
umount /data/sdext2
Again, rom specific. If you don't have an sdext2 partition, no need for the BOTTOM TWO commands.
STEP 4
Open AParted and resize your external sd card's partition, then make yourself an ext4 formatted sdext partition. Mine is 8 GB in size, since I have a 16 GB card. The journal write takes a long time...usually about a minute and a half. Don't cancel it or you'll end up with a corrupt sd card.
STEP 5
Remount your sd card by your system menu, this is the easy way.
STEP 6
Toogle init.d in Init.d Toggler. Only for stock ROMs without init.d support. Skip this if you've already done init.d or have a ROM that has it baked/enabled.
STEP 7
Install Link2SD and the pro key. The pro key costs money, so if you're poor than I'm sorry. I'm really poor, it's only a few bucks. XD
https://play.google.com/store/apps/details?id=com.buak.Link2SD
https://play.google.com/store/apps/details?id=com.buak.link2sdplus
Run Link2SD after both are installed. If done correctly you'll get a prompt asking you to create your mount scripts, so select ext4 format and confirm, then CANCEL reboot. Go to Link2SD settings and enable Relink Lib files and Relink .dex files at boot. I also make my cache auto-clear every 6 hours or so. Auto link is a really bad idea. Since some system apps break when you link them. Clear the app and dalvik cache. Some of your apps may crash. Recreate your mount scripts again, then REBOOT.
STEP 8
Go into Link2SD and link all your user apps, you can use the filter at the top and serlect "User" to see which ones you installed. DO NOT link anything that modifies your system, since those apps are known to break. For example, voltage control or ROM Manager / ROM Toolbox break when you link them. Since you have the pro version you can link the internal data too!
DO NOT link any system apps. This is a likely known cause for a brick.
DO NOT link CM themes.
DO NOT link launchers.
STEP 9
You have successfully installed Link2SD and have it working! I suggest installing SD booster or making yourself an init.d script to boost your read ahead speed at boot. This helps A LOT with app execution on older sd cards.
I hope this guide helped! Remember, if you fark up you did it to yourself! I'm not responsible.
The L90 D415 is awesome!!!
~LoopyD
Donate to the PayPalz ([email protected])
Partitions with cwm can work too?
I don't use cwm, but TWRP, so wouldn't know.