I can't seem to get the Ext A2SD to work. I've got the partition but nothing installs there. Am I missing something? I remember on my G1 it was all pretty much automatic.
Sent from my CM7 EVO using XDA App.
i'm pretty sure that the most recent builds of CM do A2SD in the same fashion that Froyo implemented it.
Meaning that the apps run off your SD off the main partition, making the EXT 2/3/4 unnecessary.
The main difference between CM's version and the stock version of A2SD right now is that CM has implemented a way to get all apps unlocked to be able to go to your SD card, and not just the ones that have been enabled by the market publisher.
in general, there is no reason to keep the EXT partition on your card anymore if you are running CM. You can just reformat it and get that precious disk space back.
Hmm. Well that sucks. I always liked the Ext A2SD because it loaded much faster. With the Froyo method it takes a few once booted because the sd is mounted.
Sent from my CM7 EVO using XDA App.
IIRC CM7 supports Darktremor ext a2sd/cache2sd script. This is a necessity for me, so I hope that's correct.
The problem could be related to a bug
http://forum.cyanogenmod.com/topic/14813-darktremor-apps2sd-issue/
Have you tried the firerat a2sd+ script?
Data2sd support for performance enhancement would be nice also.
Ok, I am somewhat confused. I am coming from a sense-based rom that had a2sd enabled. I have a ton of apps so this is necessary. Was running my Dalvik from the \cache\ partition and apps from ext3.
Is this still possible in CM7?
I tried running a2sd check in CM& and it said "a2sd not located" (or something to that effect).
I've had a a2sd issue with recent aosp roms, my find is that if yours is not working and you have a2sd installed then it's the kernel, I had to try multiple kernels to get mine working, I found Sbc bcnice v7 works perfect, shows up properly partitioned and apps are utilizing it, all the new zendroids and savagezen dont support a2sd, neither does snap 7.6
my95z34 said:
I can't seem to get the Ext A2SD to work. I've got the partition but nothing installs there. Am I missing something? I remember on my G1 it was all pretty much automatic.
Sent from my CM7 EVO using XDA App.
Click to expand...
Click to collapse
use Link2SD it is the best a2sd replacement, it supports fat32 and ext as your 2nd partition.
my95z34 said:
I can't seem to get the Ext A2SD to work. I've got the partition but nothing installs there. Am I missing something? I remember on my G1 it was all pretty much automatic.
Sent from my CM7 EVO using XDA App.
Click to expand...
Click to collapse
Hey dude,
I had the same problem (or need depending on your view) - I tried to apply "cm7_legacy_a2sd_r3-signed.zip" which failed for some reason I couldn't be bothered to work out.
Which lead me to look inside and see how it was going to apply itself. Which then took me on a happy journey of discovery that resulted in the following How-To: pastebin.com/TgqtMuYX
Check it out and let me know how it goes. If you have any issues along the way either pm me or reply here if it's helpful to the wider audience. I'll feedback any relevant details if necessary.
Cheers.
AC
PS. The phone I applied this on was my Hero (GSM) before they pulled CyanogenMod-7.0.0-Hero - seems to behave quite well when you increase the heap to 32MB, but it's still work in progress for testing.
# Android.Control 2011/04
How to manually apply a2sd on CM7 from recovery - Carried out on a Hero, but other phones should be the same.
(details taken from cm7_legacy_a2sd_r3-signed.zip)
Boot into your recovery image. I used ClockworkMod as it allowed me to mount /system very easilly
If adb it is NOT in your search path you will need to specify the /full/path/to/adb
DO NOT complain to me if the adb commands below fail if adb is not in your path
All adb commands issued from a regular user account on Linux - (Windoze will be the same, I'm sure you can work it out)
Let us begin...
1. Mount the /system partition
Recovery: Select: [mounts and storage] > [- mount /system]
[ALTERNATIVE]
Code:
$ adb shell mount /system
Just to check all went well
Code:
$ adb shell df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 98400 0 98400 0% /dev
/dev/block/mtdblock4 133120 122304 10816 92% /cache
/dev/block/mtdblock3 174080 118224 55856 68% /system
2. Find your sd-ext partition - usually /dev/block/mmcblk0p2
Recovery: Select [mounts and storage] > [- mount /sd-ext]
[ALTERNATIVE]
Code:
$ adb shell mount /sd-ext
Just to check all went well and to see what the /sd-ext device details are
Code:
$ adb shell df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 98400 0 98400 0% /dev
/dev/block/mtdblock4 133120 122304 10816 92% /cache
/dev/block/mtdblock3 174080 118224 55856 68% /system
/dev/block/mmcblk0p2 505636 10532 468999 2% /sd-ext
Recovery: Select [mounts and storage] > [- umount /sd-ext]
[ALTERNATIVE]
Code:
$ adb shell umount /sd-ext
3. Manually aplly firstboot.sh actions - from cm7_legacy_a2sd_r3-signed.zip
Using "/dev/block/mmcblk0p2" from the df output above exceute the following (replace with apropriate value for your phone!)
Code:
$ adb shell
~ # /system/bin/e2fsck -fy /dev/block/mmcblk0p2
~ # /system/bin/tune2fs -O has_journal /dev/block/mmcblk0p2
~ # /system/bin/e2fsck -fy /dev/block/mmcblk0p2
~ # /system/bin/tune2fs -c 0 -i 0 /dev/block/mmcblk0p2
~ # /system/bin/tune2fs -l /dev/block/mmcblk0p2
4. Then mount the sd-ext partition using existing script
Need additional entry in PATH to allow /system/etc/init.d/05mountsd to work
Code:
~ # PATH=$PATH:/system/bin
~ # /system/etc/init.d/05mountsd
You should see something very similar to below
Code:
e2fsck 1.41.10 (10-Feb-2009)
/dev/block/mmcblk0p2: clean, 11/130560 files, 27008/522112 blocks
5. Create app and app-private in sd-ext
If app and app-private [or dalvik-cache] exist on sd-exe BUT are NOT a directory then they must be removed!
Code:
~ # rm /sd-ext/app
~ # rm /sd-ext/app-private
[OPTIONAL]
Code:
~ # rm /sd-ext/dalvik-cache
Now we can create the directories proper
Code:
~ # install -m 771 -o 1000 -g 1000 -d /sd-ext/app
~ # install -m 771 -o 1000 -g 1000 -d /sd-ext/app-private
[OPTIONAL]
Code:
~ # install -m 771 -o 1000 -g 1000 -d /sd-ext/dalvik-cache
If you didn't see any errors you can assume everything is ok, but just to make sure...
Code:
~ # ls -l /sd-ext/
drwxrwx--x 2 system system 1024 Apr 16 13:49 app
drwxrwx--x 2 system system 1024 Apr 16 13:49 app-private
drwxrwx--x 2 system system 1024 Apr 16 13:49 dalvik-cache
drwx------ 2 root root 1024 Apr 16 01:42 lost+found
6. Create the userinit.d and functions script directories on /sd-ext
Code:
~ # install -m 755 -o 0 -g 0 -d /sd-ext/userinit.d
~ # install -m 755 -o 0 -g 0 -d /sd-ext/userinit.d/functions
Now we need to quit adb back to the host to push some files onto the phone
Code:
~ # exit
7. Push the userinit.d files into /sd-exe/userinit.d
(extract the contents of "cm7_legacy_a2sd_r3-signed.zip" to a temporary directory, then cd into sd-ext for the following adb commands)
Code:
$ adb push ./userinit.d/functions/a2sd /sd-ext/userinit.d/functions/a2sd
$ adb push ./userinit.d/10cache2sdext-binds /sd-ext/userinit.d/10cache2sdext-binds
$ adb push ./userinit.d/11data2sdext-binds /sd-ext/userinit.d/11data2sdext-binds
$ adb push ./userinit.d/12app2sdext-binds /sd-ext/userinit.d/12app2sdext-binds
$ adb shell
~ # chmod 750 /sd-ext/userinit.d/functions/a2sd
~ # chmod 750 /sd-ext/userinit.d/10cache2sdext-binds
~ # chmod 750 /sd-ext/userinit.d/11data2sdext-binds
~ # chmod 750 /sd-ext/userinit.d/12app2sdext-binds
~ # chown root:shell /sd-ext/userinit.d/functions/a2sd
~ # chown root:shell /sd-ext/userinit.d/10cache2sdext-binds
~ # chown root:shell /sd-ext/userinit.d/11data2sdext-binds
~ # chown root:shell /sd-ext/userinit.d/12app2sdext-binds
~ # exit
[ADVISORY]
If app, app-private or dalvik-cache was NOT working you would see a line similar to these lines below in the logcat output
Code:
I/busybox ( 113): sd-ext /sd-ext/app bindings not enabled
I/busybox ( 113): sd-ext /sd-ext/app-private bindings not enabled
I/busybox ( 113): sd-ext /sd-ext/dalvik-cache bindings not enabled
Reboot the phone, then quickly run adb logcat to watch the initial progress to confirm success
If you do NOT see any lines like those above in the logcat output then everything went OK
Code:
$ adb logcat
- waiting for device -
--------- beginning of /dev/log/main
I/cm ( 67): Welcome to Android 2.3.3 / CyanogenMod-7.0.0-Hero
I/cm ( 68): _
I/cm ( 69): __ __ _ ___ _ _ __ ___ __ _ _ _ _ __ __))
I/cm ( 70): ((_ \(/'((_( ((\( ((_)((_( (('((\( ((`1( ((_)((_(
I/cm ( 71): )) _))
I/cm ( 72):
I/mountsd ( 87): Checking filesystems..
I//system/xbin/run-parts( 62): e2fsck 1.41.10 (10-Feb-2009)
I//system/xbin/run-parts( 62): /dev/block/mmcblk0p2: recovering journal
I//system/xbin/run-parts( 62): /dev/block/mmcblk0p2: clean, 555/500856 files, 428759/1000173 blocks
I/logwrapper( 93): busybox terminated by exit(0)
I/logwrapper( 97): busybox terminated by exit(0)
I/logwrapper( 99): busybox terminated by exit(0)
I/mountsd ( 101): /sd-ext successfully mounted
I/busybox ( 113): sd-ext /sd-ext/data bindings not enabled
I/busybox ( 113): sd-ext /sd-ext/system bindings not enabled
I/logwrapper( 113): busybox terminated by exit(0)
I/logwrapper( 62): /system/xbin/run-parts terminated by exit(0)
...
Please be patient while any existing files in /data/app, /data/app-private and /data/dalvik-cache are copied to /sd-ext/app, /sd-ext/app-private and /sd-ext/dalvik-cache respectively
If you have manually populated the app directory prior to enabling a2sd, then this will further delay your first boot while the dalvik-cache is updated for each unseen .apk file
[NOTE]
$ = regular user shell prompt (on your PC, depending which user you use for you adb environment)
# = root user shell prompt (on your phone)
Related
Here you will find a list of some shell commands you can use on your android phone, either with a terminal emulator or over adb shell from your PC. I would recommend using connectbot as your terminal emulator.
The commands listed are in no way limited to what is described below, I am just scraping the surface here. For more information on these commands type ' --help' after your command, e.g. 'mount --help' or use google, most of these commands are exactly the same as what you would find on any Linux system, so you will find EXTENSIVE information on the web if you want to know more.
These commands work on my HTC Desire running Cyanogenmod 6 (Android 2.2), most, if not all of them should work on other devices and/or roms.
If you have any suggestions post them below or pm me and I will edit this post to include them.
Notes
Most of these commands require root privileges, type su first.
Everything after a # is a not and not a part of the command.
busybox
What it does
Provides a selection of commands not built into android by default.
Example(s)
busybox cp a b
Notes
busybox is included in most custom roms and has aliases set up so you do not need to type busybox before the commands eg, 'cp' is the same as 'busybox cp' in most custom roms.
cat
What it does
Prints the contents of a (text)file onscreen.
Example(s)
cat file
cd
What it does
Changes the current directory. You may find it easier to change to the directory you will be working in before issuing other commands so you dont need to include the full path in your commands.
Example(s)
cd .. # Go up 1 directory level, eg go from '/sdcard/download/ to '/sdcard'.
cd /sd-ext # Change to '/sd-ext'.
chmod
What it does
Makes a file executable
Example(s)
chmod 755 /data/bin/yourbin
cp
What it does
Copies files/directories
Example(s)
cp filea fileb
cp -rf directorya directoryb # Copy entire directory recursively and forces copy.
df
What it does
Displays information on all mounted filesystems (free space).
Example(s)
df -hm # Show disk usage in human readable format in Megabytes.
du
What it does
Diplays the size of files/directories.
Example(s)
du -md 1 # Prints the size of all directories in Megebytes.
du -sh file # Prints the size of file in human readable format.
du -sh directory # Prints the size of directory in human readable format.
export
What it does
Sets environment variables.
Example(s)
export PATH=$PATH;/sd-ext/bin;
free
What it does
Display the amount of free and used system memory
losetup
What it does
Associates loop disk images with loop devices.
Example(s)
losetup /sdcard/disk.img /dev/block/loop7
Notes
Android 2.2's implementation of apps2sd uses one loop device for each app saved to SD. There are 8 loop devives by default (loop0-loop7) so if you have 8 or more apps saved to SD you will not be able to use this command. There is no issue when using 'oldschool a2sd'
ls
What it does
List Directory contents.
Example(s)
ls -a # List directory contents including hidden contents.
mount
What it does
Mounts a filesystem.
Example(s)
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 # Remounts /system as writable.
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 # Remounts /system as read only.
mount -t ext2 /dev/block/loop6 /sdcard/disk # Mount loop6 on /sdcard/disk.
mount /sd-ext /sdcard/sd-ext # Mount /sd-ext on /sdcard/sd-ext.
Notes
On other devices it may be possible to mount disk images without going through losetup and using the option -loop in mount instead.
If you are having trouble with mount try using busybox mount instead, the busybox version seems more capable than the one shipped with Android.
mv
What it does
Move/rename files/directories
Example(s)
mv download/file stuff/file
mv picture4.jpg mydog.jpg
ping
What it does
Pings a server to check for conectivity.
Example(s)
ping -c 5 http://www.google.com # Ping google 5 times
Notes
if you do not include the -c option ping will work indefinatly.
pwd
What it does
Prints the current directory.
rm
What it does
Remove file/directory.
Example(s)
rm file
rm -rf directory # Delete a directory and its contents.
rmdir
What it does
Removes a directory
Example(s)
rmdir emptydir
Notes
If a directory has contents us 'rm -rf' instad.
su
What it does
Gives you root privelages.
touch
What it does
Makes an empty file
Example(s)
touch file.txt
wget
What it does
Download things from http or ftp.
Example(s)
wget http://www.google.com
Excellent, thank you.
Just what the doctor ordered for n00bs like me
there're some troubles while data2sd, and it doesn't work.....
please help me！
my G7's infomation:
S-OFF, AlphaRev N1Table HBOOT, SdCard:6.8G+1.2G FATA32
Process：
E:\android-sdk\tools>adb shell
/ # mount /system
mount /system
/ # mount /data
mount /data
/ # mount /sdcard
mount /sdcard
/ # exit
exit
E:\android-sdk\tools>adb push c:\01data /system/etc/init.d
32 KB/s (394 bytes in 0.011s)
E:\android-sdk\tools>adb push c:\busybox-armv6l /system/xbin/busybox
1771 KB/s (1062992 bytes in 0.585s)
E:\android-sdk\tools>adb shell
/ # chmod 755 /system/etc/init.d/01data
chmod 755 /system/etc/init.d/01data
/ # chmod 777 /system/xbin/busybox
chmod 777 /system/xbin/busybox
/ # cd /
cd /
/ # mount /dev/block/mmcblk0p2 /sd-ext
mount /dev/block/mmcblk0p2 /sd-ext
/ # dd if=/dev/zero of=/sd-ext/ext2 bs=1048576
dd if=/dev/zero of=/sd-ext/ext2 bs=1048576
dd: writing '/sd-ext/ext2': No space left on device
1199+0 records in
1197+1 records out
/ # /system/xbin/busybox mke2fs -F -L userdata /sd-ext/ext2
/system/xbin/busybox mke2fs -F -L userdata /sd-ext/ext2
Filesystem label=userdata
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
76800 inodes, 306639 blocks
15331 blocks (5%) reserved for the super user
First data block=0
Maximum filesystem blocks=4194304
10 block groups
32768 blocks per group, 32768 fragments per group
7680 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
/ # mkdir /sd
mkdir /sd
/ # /system/xbin/busybox mount -o loop /sd-ext/ext2 /sd
/system/xbin/busybox mount -o loop /sd-ext/ext2 /sd
/ # cd /data
cd /data
/data # cp -a * /sd
cp -a * /sd
/data # cd /
cd /
/ # /system/xbin/busybox umount /sd
/system/xbin/busybox umount /sd
/ # exit
exit
E:\android-sdk\tools>adb reboot
error: closed
BTW,when i reboot the phone,i found the second partition on sdcard is 100% full,why?where is the mistake?
help！help！help！help！help！
This is a question and belongs in q&a, not development.
Sent from my Evil Lair using Doomsday Device
It actually belongs in the Data2SD thread, which in turn IS in ROM Development
Why you don't use Androhero tutorial that I reported on post number five??
It's very simple fast and secure.
Don't fails with it
sent from the future
thx，i'll try
Btw I suggest to use the default mtd structure.
sent from the future
E:\android-sdk\tools>adb reboot
error: closed
this problem may cause by usb drives or recovery?
the drives are all installed ok...
mattiadj said:
Why you don't use Androhero tutorial that I reported on post number five??
It's very simple fast and secure.
Don't fails with it
sent from the future
Click to expand...
Click to collapse
i have a question,in your tutorial, don't need this file busybox?
Busibox may be included in ROM.
Try to install recovery driver from root thread.
sent from the future
hi
here in this fantastic site i saw there are some tips to extend some roms inernal memory up to 2gigs!!!!!
but my rom is InsertCoinDATAplusplusv03 or i can even change it to LeeDrOiD_V2.4_A2Sd
is there any way to extend this roms to that capasity or not.
or not i like a 720p roms with this abality.
what is your suggestion
it is soooooo necessary
i'seen you answer all the questions so would you please answer mine too??
royalrose said:
hi
here in this fantastic site i saw there are some tips to extend some roms inernal memory up to 2gigs!!!!!
but my rom is InsertCoinDATAplusplusv03 or i can even change it to LeeDrOiD_V2.4_A2Sd
is there any way to extend this roms to that capasity or not.
or not i like a 720p roms with this abality.
what is your suggestion
it is soooooo necessary
i'seen you answer all the questions so would you please answer mine too??
Click to expand...
Click to collapse
The only way that i am aware of increasing internel memory is to install a rom which is compatable with a D2EXT script which makes the phone use an ext partition of your memory card as internal memory.
To find out if a particular rom is capable of this you will have to reed about them in the development section and, if you are still unsure, ask the question.
Hope this helps.
royalrose said:
but my rom is InsertCoinDATAplusplusv03 or i can even change it to LeeDrOiD_V2.4_A2Sd
is there any way to extend this roms to that capasity or not.
Click to expand...
Click to collapse
For LeeDroid 2.4 you might look here. Beware that there may be some issues ... It's sort of experimental !
bobsie41 said:
The only way that i am aware of increasing internel memory is to install a rom which is compatable with a D2EXT script which makes the phone use an ext partition of your memory card as internal memory.
To find out if a particular rom is capable of this you will have to reed about them in the development section and, if you are still unsure, ask the question.
Hope this helps.
Click to expand...
Click to collapse
thanx bro but as i'm new in this site i can't post any question there
i expereinced many kind of roms(include d2xt) but i had the same problem
Some Guy told me he physically removed the 512 memory chip (ram) from his Samsung galaxy s and replaced it with a gig one. Some soldering required I suppose.
mercianary said:
Some Guy told me he physically removed the 512 memory chip (ram) from his Samsung galaxy s and replaced it with a gig one. Some soldering required I suppose.
Click to expand...
Click to collapse
thanks but I think there should be an easier way too.
no answer?????
royalrose said:
no answer?????
Click to expand...
Click to collapse
You already got your answer, no? use a data2ext rom..
I personally use insertcoin 2.0.1 data2ext, and cant recommend it enough.
very fast, very stable, more than most hd roms ..
http://forum.xda-developers.com/showthread.php?t=861690
snakeeyes21 said:
You already got your answer, no? use a data2ext rom..
I personally use insertcoin 2.0.1 data2ext, and cant recommend it enough.
very fast, very stable, more than most hd roms ..
http://forum.xda-developers.com/showthread.php?t=861690
Click to expand...
Click to collapse
i had that rom too.it's so nice and fast but after instaling 15 apps or game my internal memory became full again.
is it usual??
Do you have an EXT partition on your sdcard?
cgmorris89 said:
Do you have an EXT partition on your sdcard?
Click to expand...
Click to collapse
yes bro
both ext 3 & 4
but still i have low memory
stumped
are your partitions in the correct order?
cgmorris89 said:
stumped
are your partitions in the correct order?
Click to expand...
Click to collapse
I think it's
usualy it's in this form
first fat32(6.5g)
2nd ext2(500mb)
3rd ext4(500mb)
4th swap(500mb)
You can also have a look at DATA2SD (see my sig) and adapt it manually to your favorite ROM
Try this:
Download a terminal app from the market.
Open it, allow SU permissions.
Type "a2sd cachesd"
The phone should now reboot.
And, if need be, try my guide here.
http://androidforums.com/desire-tip...ed-device-noobs-guide-updated-09-02-11-a.html
sibere said:
You can also have a look at DATA2SD (see my sig) and adapt it manually to your favorite ROM
Click to expand...
Click to collapse
i read your useful guide but some where i had a problem.
E:\New folder\android-sdk\platform-tools>adb shell
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
E:\New folder\android-sdk\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found
E:\New folder\android-sdk\platform-tools>adb shell
~ # mount /system
mount /system
~ # mount /data
mount /data
~ # mount /sdcard
mount /sdcard
~ # exit
exit
E:\New folder\android-sdk\platform-tools>adb push c:\01data /system/etc/init.d
28 KB/s (367 bytes in 0.012s)
E:\New folder\android-sdk\platform-tools>adb shell
~ # chmod 755 /system/etc/init.d/01data
chmod 755 /system/etc/init.d/01data
~ # cd /
cd /
~ # mount /dev/block/mmcblk0p2 /sd-ext
mount /dev/block/mmcblk0p2 /sd-ext
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or director
y
~ # dd if=/dev/zero of=/sd-ext/ext2 bs=1048576
dd if=/dev/zero of=/sd-ext/ext2 bs=1048576
dd: can't open '/sd-ext/ext2': No such file or directory
~ # /system/xbin/busybox mke2fs -F -L userdata /sd-ext/ext2
/system/xbin/busybox mke2fs -F -L userdata /sd-ext/ext2
mke2fs: can't open '/sd-ext/ext2': No such file or directory
i spend 8 hours to do it but.....
royalrose said:
i read your useful guide but some where i had a problem.
E:\New folder\android-sdk\platform-tools>adb shell
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
E:\New folder\android-sdk\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found
E:\New folder\android-sdk\platform-tools>adb shell
~ # mount /system
mount /system
~ # mount /data
mount /data
~ # mount /sdcard
mount /sdcard
~ # exit
exit
E:\New folder\android-sdk\platform-tools>adb push c:\01data /system/etc/init.d
28 KB/s (367 bytes in 0.012s)
E:\New folder\android-sdk\platform-tools>adb shell
~ # chmod 755 /system/etc/init.d/01data
chmod 755 /system/etc/init.d/01data
~ # cd /
cd /
~ # mount /dev/block/mmcblk0p2 /sd-ext
mount /dev/block/mmcblk0p2 /sd-ext
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or director
y
Click to expand...
Click to collapse
Here is the problem, your recovery doesn't have sd-ext directory. You must create it with a mkdir /sd-ext command
~ # dd if=/dev/zero of=/sd-ext/ext2 bs=1048576
dd if=/dev/zero of=/sd-ext/ext2 bs=1048576
dd: can't open '/sd-ext/ext2': No such file or directory
~ # /system/xbin/busybox mke2fs -F -L userdata /sd-ext/ext2
/system/xbin/busybox mke2fs -F -L userdata /sd-ext/ext2
mke2fs: can't open '/sd-ext/ext2': No such file or directory
i spend 8 hours to do it but.....
Click to expand...
Click to collapse
How this is the old way with an ext2 file mounted via a loop device. Now it's an ext4 partition of max 2GB. Default is without journal but informations are provided to use journal for safety specially on AOSP ROMs.
Droidzone has created also some ready 2 flash ZIP files for both AOSP and SENSE ROMS. Check-out the OP page again.
thanks for tips
16) My GoogleMaps (or other application that uses OpenGL) is freezing/irresponsive. What can I do?
Open terminal or adb shell and type these commands:
Code:
$ su
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
# echo sysctl -w vm.min_free_kbytes=4096 >> /system/etc/install-recovery.sh
# chmod 744 /system/etc/install.sh
# mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
Hi all i have some question about this!
So this is a countermeasure like a mod? I type it in then everything goes well?
Or i have to type it after every restart?
and if i write this it kills the app or it will run before the freezing?
is this working with opengl games?.
Thanks!
Ernő
when i tried typing this line
# chmod 744 /system/etc/install.sh
no such file exists
maybe this?
# chmod 744 /system/etc/install-recovery.sh
PS: Has this anything to do with recovery 2ndinit or something?
not exactly sure what this does, I think it makes sure at least 4096kb of RAM is free.
but try
$ su
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
# echo vm.min_free_kbytes = 4096 >> /system/etc/sysctl.conf
# mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
# sysctl -p
it worked for me and has kept the setting after restarts
Just download sysctl in market and set it at 4096 it higher. If you have setvsel, it had option to increase min kb to 4096
Sent from my MB525 using XDA App
My Defy 2.2 also freezes when trying Maps (the only one that works is 5.0.0) - so I've tried sysctl with 8192 at min. kb. free.
No success, still freezing with 5.6.0/5.7.0 .
Uninstall updates in maps then update a fresh one.
Sent from my MB525 using XDA App
Hi all,
since i could not use the UMS mode on my sgs3 and all of the tested Applications do not work i made 2 scrips for gscrip.
First check if all mount points are correct for you, if not correct them. Run mount, check mount point of sdcard (/dev/fuse /storage/sdcard1)
But i think on all sgs3 with cm10.1 it should be the same.
edit:
I get a transfer rate of ~8.5MB/s writing and ~ 18MB/s reading so for copying mp3 to the mobile i will still plug the card to the pc.
!!! AND DON'T FORGET TO UNMOUNT/EJECT YOUR SDCARD BEFORE ums_off !!!
And don't forget you are working as root so you can screw up a lot
[email protected]:/ # mount
...
/dev/block/vold/179:49 /mnt/fuse/sdcard1 ext4 rw,dirsync,nosuid,nodev,noexec,noatime,barrier=1 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
...
Click to expand...
Click to collapse
ums_on
Code:
setprop persist.sys.usb.config mass_storage,adb
umount /storage/sdcard1
echo /dev/block/vold/179:49 > /sys/devices/platform/s3c-usbgadget/gadget/lun0/file
ums_off
Code:
echo "" > /sys/devices/platform/s3c-usbgadget/gadget/lun0/file
setprop persist.sys.usb.config mtp,adb
vold
Hints:
If you are using Linux and your sdcard is ext4 like mine and can't write as a user to the root of the sdcard just add a group to "/etc/group" for me it was (the id you see when you type mount)
Code:
mobile_sd:x:1023:dark-wulf
Check and Disable journal on ext4 sdcard with a card-reader
Code:
root # tune2fs -l /dev/sdXY | grep has_journal
root # tune2fs -O ^has_journal /dev/sdXY
And remove reserved blocks for root
Code:
root # tune2fs -m 0 /dev/sdXY
Thanks to http://forum.xda-developers.com/showpost.php?p=27282116 for bringing me the idea
Greetings
dark-wulf