Related
Just got Complete Eclair v2.2.1 and downloaded a few apps from the market...
I have Apps2SD on...but why does my memory keep going down?
I have Advance Task Killer on and everytime I install new apps...my phone memory goes down....before it was at 39mb and now its at 24mb... I thought Apps2SD didnt use up phone memory?
Mytouch 32b
radio 2.22.23.02
hboot 1.33.0006
cpld 10
ROM: Complete Eclair v2.2.1
luminiz said:
Just got Complete Eclair v2.2.1 and downloaded a few apps from the market...
I have Apps2SD on...but why does my memory keep going down?
I have Advance Task Killer on and everytime I install new apps...my phone memory goes down....before it was at 39mb and now its at 24mb... I thought Apps2SD didnt use up phone memory?
Mytouch 32b
radio 2.22.23.02
hboot 1.33.0006
cpld 10
ROM: Complete Eclair v2.2.1
Click to expand...
Click to collapse
Do you have your sd card partitioned?
koreancanuck said:
Do you have your sd card partitioned?
Click to expand...
Click to collapse
Yes to the regular format of
LinuxSwap – 32MBs
Ext2 – 512Mbs
Fat32 – Remainder
luminiz said:
Yes to the regular format of
LinuxSwap – 32MBs
Ext2 – 512Mbs
Fat32 – Remainder
Click to expand...
Click to collapse
Use adb shell and enter 'mount'
This will make sure that you have an ext partition
Also using adb shell, enter 'df'
That should give us an idea of what is taking up all of your storage.
Keep in mind that the data for the apps are still being stored onto the device (under /data). Before you ask, it is not advisable to move /data to the ext partition. It's been done and determined not to be recommendable.
Binary100100 said:
Use adb shell and enter 'mount'
This will make sure that you have an ext partition
Also using adb shell, enter 'df'
That should give us an idea of what is taking up all of your storage.
Keep in mind that the data for the apps are still being stored onto the device (under /data). Before you ask, it is not advisable to move /data to the ext partition. It's been done and determined not to be recommendable.
Click to expand...
Click to collapse
After I typed in "df" in adb shell:
http://imagefrog.net/show.php/92144_AdbShellDF.JPG
Is there a problem?
Magic 32B S-ON G
HBOOT - 1.33.0006
Radio - 2.22.16.261
Rom - Complete Eclair v2.2.1
Recovery - Amon Ra's 1.6.2G
Btw...One question
In SpareParts in my Complete Eclair v2.2.1 what the Comcache/Swap Setting and Compcache Size do? There's no option checked...so is that the source of the problem? Just wondering
Compcache and swap don't have anything to do with application storage space. If you don't know what they are, don't enable them.
Edit:
Looking at your screenshot, Apps2sd is working correctly.
/dev/block/mtdblock5 is mounted to /data where your apps would go normally
/dev/block/nmcblkop2 is mounted to /sd-ext which is where space is being used.
If you notice, /data usage is at 2%, while /sd-ext is at 5%, so your apps look to be going there (21339 bytes used on /sd-ext)
Phone ram goes down because apps are using ram. Apps2sd doesn't have anything to do with how much ram a program uses.
1)Quit obsessing over free memory. Android will kill app processes when it needs ram. It's smarter than you.
2)Task Killers do more harm than good. There's a dozen articles scattered all over the web why, do a little research on it, then uninstall ATK and stop worrying.
raduque said:
Compcache and swap don't have anything to do with application storage space. If you don't know what they are, don't enable them.
Edit:
Looking at your screenshot, Apps2sd is working correctly.
/dev/block/mtdblock5 is mounted to /data where your apps would go normally
/dev/block/nmcblkop2 is mounted to /sd-ext which is where space is being used.
If you notice, /data usage is at 2%, while /sd-ext is at 5%, so your apps look to be going there (21339 bytes used on /sd-ext)
Phone ram goes down because apps are using ram. Apps2sd doesn't have anything to do with how much ram a program uses.
1)Quit obsessing over free memory. Android will kill app processes when it needs ram. It's smarter than you.
2)Task Killers do more harm than good. There's a dozen articles scattered all over the web why, do a little research on it, then uninstall ATK and stop worrying.
Click to expand...
Click to collapse
Wow. Very Informative Post! Thanks!
Sorry about me over-obsessing about phone memory...its just that I'm new to the Rooted-Android world and I'm used to seeing and expecting things differently when I had stock Android. I'm just trying to learn here like everybody else and everyone makes misjudgments on things sometimes. Any ways...Thanks for your post!
luminiz said:
After I typed in "df" in adb shell:
http://imagefrog.net/show.php/92144_AdbShellDF.JPG
Is there a problem?
Magic 32B S-ON G
HBOOT - 1.33.0006
Radio - 2.22.16.261
Rom - Complete Eclair v2.2.1
Recovery - Amon Ra's 1.6.2G
Click to expand...
Click to collapse
Yeah, you're nowhere near filling up the phone's memory. In fact you still have over 3mb of free space in /system to use by tossing in a bootanimation.zip file (for 2.1 roms only) or adding some custom ringtones (/system/media/audio/), whatever and you have only used about 20mb of your 500mb ext partition. If you do feel the need to clean it up, I would suggest using a cache clearing app to do so and nothing else.
Good luck.
Binary100100 said:
Yeah, you're nowhere near filling up the phone's memory. In fact you still have over 3mb of free space in /system to use by tossing in a bootanimation.zip file (for 2.1 roms only) or adding some custom ringtones (/system/media/audio/), whatever and you have only used about 20mb of your 500mb ext partition. If you do feel the need to clean it up, I would suggest using a cache clearing app to do so and nothing else.
Good luck.
Click to expand...
Click to collapse
Sorry for the newbie questions but...
How do you toss in the bootanimation.zip file?
What do you mean I still have over 3mb of free space in system? I thought system memory was only used up by the ROM's
What else can I put in the /system ?
So when I have Advance Task Killer telling me I have 16mb of memory...its ok?
Thanks for your responses...They're greatly appreciated!
luminiz said:
Sorry for the newbie questions but...
How do you toss in the bootanimation.zip file?
What do you mean I still have over 3mb of free space in system? I thought system memory was only used up by the ROM's
What else can I put in the /system ?
So when I have Advance Task Killer telling me I have 16mb of memory...its ok?
Thanks for your responses...They're greatly appreciated!
Click to expand...
Click to collapse
I wouldn't worry about any of that. The bootanimation.zip is the animation that you see after starting your phone. An example:
http://www.youtube.com/watch?v=lAFSEsEZnnE&feature=related
If you are running Firmware 2.2 (such as Cyanogen's 5.0.7 or 5.0.8) you can remove the existing bootanimation.zip file by:
adb remount
adb shell
rm /system/media/bootanimation.zip
and then adb push bootanimation.zip /system/media
Anyway... all of that is unrelated to your topic.
And your 16mb of memory is regarding RAM, not ROM.
luminiz said:
Wow. Very Informative Post! Thanks!
Sorry about me over-obsessing about phone memory...its just that I'm new to the Rooted-Android world and I'm used to seeing and expecting things differently when I had stock Android. I'm just trying to learn here like everybody else and everyone makes misjudgments on things sometimes. Any ways...Thanks for your post!
Click to expand...
Click to collapse
Nah, don't worry about it. I used to freak out about free memory all the time too, both on stock 1.6 and cyanogenmod 5.0.7, till I read some articles about how Android manages apps and processes and I realized it's not worth worrying about, because Android will kill what it has to when it needs ram for something.
What are the chances of being able to ditch all the concerns that go along with Ext2, Ext3, and Ext4 hacks to improve read-write on the Captivate by going with YAFFS or YAFFS2?
http://en.wikipedia.org/wiki/YAFFS
YAFFS is an optimized filesystem for use with NAND flash memory, would it provide the stability and speed we're looking for?
I know this idea has been discussed lightly before in the various "lag fix" threads, but I was wondering if users with knowledge could enlighten the rest of us on the YAFFS filesystem.
I may be way wrong here, but judging by a few commands I've seen regarding busybox install issues, is it possible the stock kernel supports this already?? In which case could we modify the current lag fixes to use it instead?
Since this is related and I already posted this in Nuka's thread:
http://forum.xda-developers.com/showthread.php?t=750663
Those wacky gents over in the I9000 section have managed to get YAFFS2 compatibility into the kernel. This is something we should probably look into once we've figured out the wake-lag issue (maybe sooner )
In other news, assuming we can get YAFFS2 plugged into our kernel, how feasible (albiet probably complicated) would it be to actually REPLACE RFS and then load the OS on top of YAFFS2? There's just something about cascading file systems written on top of each other that sounds like trouble to me.
Zilch25 said:
Since this is related and I already posted this in Nuka's thread:
http://forum.xda-developers.com/showthread.php?t=750663
Those wacky gents over in the I9000 section have managed to get YAFFS2 compatibility into the kernel. This is something we should probably look into once we've figured out the wake-lag issue (maybe sooner )
Click to expand...
Click to collapse
Nice find!
I agree, the wake-up-lag issue is bothersome. Looking forward to mimocan possibly helping us out with his solution that he offered the Samset people.
kennethpenn said:
What are the chances of being able to ditch all the concerns that go along with Ext2, Ext3, and Ext4 hacks to improve read-write on the Captivate by going with YAFFS or YAFFS2?
http://en.wikipedia.org/wiki/YAFFS
YAFFS is an optimized filesystem for use with NAND flash memory, would it provide the stability and speed we're looking for?
I know this idea has been discussed lightly before in the various "lag fix" threads, but I was wondering if users with knowledge could enlighten the rest of us on the YAFFS filesystem.
Click to expand...
Click to collapse
Using a FS designed for Flash media will help with some of the fixes but not all. For example the mimocan fix it should help, as it will reduce overhead and increase the longevity of the Flash. Also since the mimocan fix is on the external card, it is properly un-mounted at shut down so this helps stop corruption.
Conversly it won't really do anything for the ext2 fix because that is a virtual disk sitting on top of another FS, which is not un-mounted at shutdown.
Potentially a custom ROM could replace the FS on the internal flash, but Samsung must have did what they did for a reason. It is hard to tell if they did what they did because they were lazy / didn't know any better, or they knew something we don't.
Bjd223 said:
Potentially a custom ROM could replace the FS on the internal flash, but Samsung must have did what they did for a reason. It is hard to tell if they did what they did because they were lazy / didn't know any better, or they knew something we don't.
Click to expand...
Click to collapse
Samsung use rfs because for some misguided and twisted reason some manager there thinks it is good and proprietary so they have a leg up on the competition. They go on about how quick rfs mounts as a benefit (yaffs and other flash files systems are slow to mount).
RFS isn't exactly terrible in the right places - the /dbdata symlink hack works because RFS-on-NAND is faster than RFS-on-SD, even though raw reads on the internal SD are faster than on the OneNAND partitions. I suspect it simply interacts poorly with devices that already do their own remapping and wear-leveling, or perhaps that the performance hit is a result of using much larger blocks on /data. I wonder what would happen if one just formatted /data with smaller blocks than 16KiB?
kennethpenn said:
YAFFS is an optimized filesystem for use with NAND flash memory
Click to expand...
Click to collapse
That already explains it all. I do not think it can be used on SD. This is copy-paste from UBIFS, but I believe it is the same for YAFFS:
This is why UBIFS does not work on MMC cards and the like - they look like block devices to the outside world because they implement FTL (Flash Translation Layer) support in hardware, which simply speaking emulates a block device on top of the built-in raw flash.
Click to expand...
Click to collapse
For the ext2 hack with loop device (file formated as ext2) I have no idea if it is any better.
Why do I feel like i'm the only one without the wake up lag issue? .
tbae2 said:
Why do I feel like i'm the only one without the wake up lag issue? .
Click to expand...
Click to collapse
I bet u r on stock kernel
Sent from my SAMSUNG-SGH-I897 using XDA App
Doesn't the Captivate already use yaffs2? Try running "mount" in a terminal emulator or in adb shell.
junknuts said:
Doesn't the Captivate already use yaffs2? Try running "mount" in a terminal emulator or in adb shell.
Click to expand...
Click to collapse
no, it uses rfs for everything...
yaffs2 is not really any better than rfs, both file systems, however, are not intended for use on SD memory. In other words you would be exerting great effort to get yaffs2 as your file system for the NAND part of your phone, and get little to no improvement. As for the mimocam fixes and the like that use your SD card or Internal Memory (Internal SD Card essentially), ext2, 3, or 4 would still be better options than yaffs2 or rfs as they are intended for true NAND Flash memory not block based SD memory.
tbae2 said:
Why do I feel like i'm the only one without the wake up lag issue? .
Click to expand...
Click to collapse
Ok, silly question...what is "wake up lag"? Either thats too technical of a term, or too vague, I dont really get it.
derek4484 said:
Ok, silly question...what is "wake up lag"? Either thats too technical of a term, or too vague, I dont really get it.
Click to expand...
Click to collapse
When you don't use your phone for a while, the phone goes into a "sleep" mode where the screen is totally black and does not respond to any touch. To "wake up" the phone, you press the power button, after which you can see the phone locked screen, and the screen responds to touch again. On a normal Captivate with the precompiled kernel installed by Samsung, or on a Captivate where you have flashed the same precompiled kerenel via Odin, the delay between pressing the power button, and seeing the phone locked sceen is usually less than a second or so. On phones where a kernel compiled from the Samsung released source code (either with or without any modifications) is flashed on, there is a much longer delay between the power button press, and the phone waking up to show the phone locked screen. This is what we mean by wake up lag. We still don't know what causes the rebuilt kernels to lag on wake up.
*Moved question to General*
Flash memory: NAND vs SD?
Hello,
Mr Taco above made a distinction that I can't figure out. He suggests that YAFFS is for "NAND" memory and not "block based SD." Here is my confusion.
From what I have read, it appears as though typical flash multimedia drives, such as MMC and other SD cards, are all created from NAND chips (as opposed to the less-memory-dense NOR chips). So I do not understand the distinction between "NAND" and "SD."
Also, he mentions "block based" devices. But as far as I can tell, "block level" has to do with the *interface* to storage and not the nature of the storage itself. For example, one could map a bunch of random access memory and present it as a block device (say, so it could be treated as a disk with a filesystem). Similarly, mmap and other techniques use disk storage with a memory-like interface (as opposed to a block interface).
So here are some questions I have that might help me figure this out:
1. Presumably the Captivate has some true RAM, that is, non-NAND chips that give truly random access memory that is not persistent upon shutdown.
2. That RAM has a normal (non-MTD) interface (512MB?).
3. Besides this RAM, the Captivate has an internal NAND-based flash drive (2gb).
4. It also has another internal NAND-based flash drive (16GB).
5. It has an external slot for a micro sd card, a NAND-based flash device accepting up to 32GB.
If these are all true, I have questions.
A. Is mimocam's (sp?) solution to use actual RAM, synced to flash, to load certain partitions?
B. Or is his solution implemented on the internal 2GB flash?
C. Certainly, other solutions have used external and internal flash (the ext2 solution, for example).
D. So, isn't it still true that any solution that would rely on the 2GB, internal 16GB or external NAND-flash would profit from using YAFFS?
Thank you in advance,
-0
zeroaltitude said:
Mr Taco above made a distinction that I can't figure out. He suggests that YAFFS is for "NAND" memory and not "block based SD." Here is my confusion.
From what I have read, it appears as though typical flash multimedia drives, such as MMC and other SD cards, are all created from NAND chips (as opposed to the less-memory-dense NOR chips). So I do not understand the distinction between "NAND" and "SD."
Click to expand...
Click to collapse
I'll repeat once again, it is from UBIFS page, but afaik it is the same for yaffs and others:
One thing people have to understand when dealing with UBIFS is that UBIFS is very different to any traditional file system - it does not work on top of block devices (like hard drives, MMC/SD cards, USB flash drives, SSDs, etc). UBIFS was designed to work on top of raw flash, which has nothing to do with block devices. This is why UBIFS does not work on MMC cards and the like - they look like block devices to the outside world because they implement FTL (Flash Translation Layer) support in hardware, which simply speaking emulates a block device on top of the built-in raw flash.
Click to expand...
Click to collapse
"One thing people have to understand when dealing with UBIFS is that UBIFS is very different to any traditional file system - it does not work on top of block devices (like hard drives, MMC/SD cards, USB flash drives, SSDs, etc). UBIFS was designed to work on top of raw flash, which has nothing to do with block devices. This is why UBIFS does not work on MMC cards and the like - they look like block devices to the outside world because they implement FTL (Flash Translation Layer) support in hardware, which simply speaking emulates a block device on top of the built-in raw flash."
Although I do appreciate the attempt to answer my questions, this reply is very puzzling.
My question was why did Mr Taco make a *distinction* between SD and NAND as far as flash memory goes. The reply, quoted above, *lumps SD and NAND devices together*. Furthermore, the primary topic of the quotation is yet another filesystem, UBIFS, that is not even under discussion (at least, not in my post it wasn't).
So, I'm happy to read up on UBIFS, however, I don't see how that can possibly answer the specific questions I have. I hope someone with some familiarity with device drivers or filesystem internals will drop by this thread. Otherwise, it's back to the research .
-0
NAND flash is typically configured so that for each block of stored data, there is a sub-block for supplementary data. This is used for wear-levelling, etc. "Raw" NAND devices such as kernel mtd devices expose this as well as the data portion of each block, and filesystems like yaffs2 and ubifs incorporate wear-levelling into the filesystem design, and rely on having direct access to raw flash.
SD cards contain a controller that does its own wear-levelling, and expose only the data segment of each block. Yaffs2 and ubifs will simply not work on such a device, nor are they really appropriate choices for it. A block-oriented filesystem is needed here, and because we can't guarantee graceful shutdowns, it needs to have some sort of data integrity scheme. Ext3/4 are journalled, Samsung's RFS is FAT with copy-on-write added, and the other possibilities here are nilfs2 and btrfs - but there are no backports of reasonable recent btrfs versions for the kernel Samsung has provided to us.
Unhelpful said:
nilfs2 and btrfs - but there are no backports of reasonable recent btrfs versions for the kernel Samsung has provided to us.
Click to expand...
Click to collapse
Thanks. I'm a bit boring to explain the basic things ppl can google first.
About fs. Do we need metadata or block level journaling?
We can consider ReiserFS or JFS? btrfs sounds nice tho.
now i m confused.. wich lagfix is better? in quadrant all the fix do then the 2000...
Your choice. Do you want to repartition the sd card and fiddle in cmd, or just double click a file?
The problem with the first fix is that you cant replace the card any time you want. The problem with the second fix is that if you dont have 1gb free on the phone, it wont work
Second one looks like a much better deal.
If you don't have 500mb free on your internal SC card (correct me if I'm wrong, but I don't think it's 1gb), you can always move all your personal stuff in the external SD card.
Unless of course you have filled it up with apps only (with no app2sd with Eclair), but how you would have managed to fill almost 2gb of apps is beyond me. That'd be more than 2000 apps.
What I don't know though is the long term effects. I have no idea if the fixes that are made are bad for the internal SD card. I guess you have to trust Ryan.
Davith said:
Second one looks like a much better deal.
If you don't have 500mb free on your internal SC card (correct me if I'm wrong, but I don't think it's 1gb), you can always move all your personal stuff in the external SD card.
Unless of course you have filled it up with apps only (with no app2sd with Eclair), but how you would have managed to fill almost 2gb of apps is beyond me. That'd be more than 2000 apps.
What I don't know though is the long term effects. I have no idea if the fixes that are made are bad for the internal SD card. I guess you have to trust Ryan.
Click to expand...
Click to collapse
what do you mean about second choise lagfix 2.0??
2.0 caused my phone to be unstable so I re-flashed and went back to the first (1GB) fix.
Are you considering mimocam's fix (using the external card) or just between Ryan and Chanfire's fixes?
rock187 said:
what do you mean about second choise lagfix 2.0??
Click to expand...
Click to collapse
Yeah, I was talking about Ryan's Lagfix 2.3. (it's not 2.0 anymore).
I don't use either. I recommend the original fix that moves data to dbdata. I have over 70 apps installed and still plenty of space left. Using autokiller to keep free memory at 70 meg I have no lag. Currently on jm5.
Sent from my GT-I9000 using XDA App
I first did it by command line with the 1Gb partition. That ran well. I then updated to Ryans 2.2 which I have been using all day. It also runs really well. Lag pretty much gone.
If i apply the one-click-LagFix it makes an virtual ext2 partition to my internal sd-card. So if i choose sometime later to undo the fix how can i delete the ext2 partition in my internal sd-card? Will it be necessary to use gparted or similar?
Bajo76 said:
If i apply the one-click-LagFix it makes an virtual ext2 partition to my internal sd-card. So if i choose sometime later to undo the fix how can i delete the ext2 partition in my internal sd-card? Will it be necessary to use gparted or similar?
Click to expand...
Click to collapse
Just run the included unlagfixme.bat file. It's automated. But make sure you are running the unlagfixme for the correct version (2-2 or 2-3)
It works fine. I ran unlagfixme and flashed back to a stock ROM, tested with Quadrant and got the 900 something score again, so it does remove the lagfix.
I will note, however, that it's a very good idea to run the unlagfixme.bat before flashing to a different ROM.
kgk888 said:
Just run the included unlagfixme.bat file. It's automated. But make sure you are running the unlagfixme for the correct version (2-2 or 2-3)
It works fine. I ran unlagfixme and flashed back to a stock ROM, tested with Quadrant and got the 900 something score again, so it does remove the lagfix.
I will note, however, that it's a very good idea to run the unlagfixme.bat before flashing to a different ROM.
Click to expand...
Click to collapse
If you are flashing to any rom using odin3, there is no need to do the unlagfix at all, because the flashing would have overwritten any changes that you have made to the file system.
I often flashed my device alredy with repartition but it didnt touched my internal sd, cause my photos which are stored in the internal sd were still there after flashing. So will a firmware-flash through odin really delete the virtual ext2 partition?
Bajo76 said:
If i apply the one-click-LagFix it makes an virtual ext2 partition to my internal sd-card. So if i choose sometime later to undo the fix how can i delete the ext2 partition in my internal sd-card? Will it be necessary to use gparted or similar?
Click to expand...
Click to collapse
The LagFix does not partition your internal card. A 1gb file is created upon which the ext2 filesystem is made. Then this file is mounted as a loopback device. So the UnLagFix basically moves the data back to the native internal storage directories and deletes the ext2 file, so no need to use gparted
Hello,friends i need two solution from you people....
1.how to backup entire /system folder for using it in android kitchen working rom.
can i backup with root explorer or use some commands in terminal emulator..
i think terminal commands will bakup it in .tar and will not change anything in the files
so please give me the commands to backup system on sd card.
2.secondly what value to put while partioning sd card using rom manager....
thanks in advance.
rohitzz said:
Hello,friends i need two solution from you people....
1.how to backup entire /system folder for using it in android kitchen working rom.
can i backup with root explorer or use some commands in terminal emulator..
i think terminal commands will bakup it in .tar and will not change anything in the files
so please give me the commands to backup system on sd card.
2.secondly what value to put while partioning sd card using rom manager....
thanks in advance.
Click to expand...
Click to collapse
Don't know number 1,
I have a SD card partition of 1024 MB and 32 MB swap. I can install 500 apps . So I guess these values are more than enough
rohitzz said:
Hello,friends i need two solution from you people....
1.how to backup entire /system folder for using it in android kitchen working rom.
can i backup with root explorer or use some commands in terminal emulator..
i think terminal commands will bakup it in .tar and will not change anything in the files
so please give me the commands to backup system on sd card.
2.secondly what value to put while partioning sd card using rom manager....
thanks in advance.
Click to expand...
Click to collapse
1. nand backup via CWM or Amon_RA recovery
2. don't use ROM Manager (EVER for ANYTHING), either make the partition via recovery or via the built in tools
---------- Post added at 12:21 PM ---------- Previous post was at 12:19 PM ----------
QuantumFoam said:
Don't know number 1,
I have a SD card partition of 1024 MB and 32 MB swap. I can install 500 apps . So I guess these values are more than enough
Click to expand...
Click to collapse
Yeah, 1024 goes a long way but if you got a big SD card you might want to go for twice that and swap isn't just not needed, it's not even used unless you make a separate script to use it which ISN'T included in most roms.
Which kind of built in tools?
Sent from my Blade using xda premium
QuantumFoam said:
Don't know number 1,
I have a SD card partition of 1024 MB and 32 MB swap. I can install 500 apps . So I guess these values are more than enough
Click to expand...
Click to collapse
Why anyone don't know 1. Step!!!
Sent from my Blade using xda premium
rohitzz said:
Why anyone don't know 1. Step!!!
Sent from my Blade using xda premium
Click to expand...
Click to collapse
Jinxxed posted it above
Tar will only backup what is inside the system partition . For a more complete backup one needs backup of all partitions and boot loader with recovery. It possible only by a tool like CWM.
Also for a phone with 512 MB RAM one doesn't need swap. It mai actually degrade the performance.
My Idea ZTE Blade has only 256MB RAM, I am using CM7.2 . In manage applications total of free plus used is only 128MB. So I enabled swap using m2sd, it's 256MB, actual usage varies from 80MB to 130MB.
My phones performance is greatly improved.
Sent from my Idea Blade
rahulsa said:
Tar will only backup what is inside the system partition . For a more complete backup one needs backup of all partitions and boot loader with recovery. It possible only by a tool like CWM.
Also for a phone with 512 MB RAM one doesn't need swap. It mai actually degrade the performance.
My Idea ZTE Blade has only 256MB RAM, I am using CM7.2 . In manage applications total of free plus used is only 128MB. So I enabled swap using m2sd, it's 256MB, actual usage varies from 80MB to 130MB.
My phones performance is greatly improved.
Sent from my Idea Blade
Click to expand...
Click to collapse
1. CWM will use TAR to make the backups so it's the same thing, to make a clone of the partition you'll need to use cc.
2. It won't degrade the performance in any scenario, it MAY be unnecessary and unused though.
3. That's not swap, that's using an extended partition to store data, what you're looking at is internal storage and more specifically the internal partition /data
Jinxxed said:
1. CWM will use TAR to make the backups so it's the same thing, to make a clone of the partition you'll need to use cc.
2. It won't degrade the performance in any scenario, it MAY be unnecessary and unused though.
3. That's not swap, that's using an extended partition to store data, what you're looking at is internal storage and more specifically the internal partition /data
Click to expand...
Click to collapse
1. Ok, new learning for me.
2. Good to know this. I was bit worried initially with my 256MB swap size. As I saw 0 or 32 MB swap in many posts. But after 2 weeks I confirm that it was the best thing I did for my Blade. Yes it was even better than using sd card's ext4 partition for more space. Low RAM was a bit serious issue for me than low space.
3. I know swap and ext partition are different. I have 256MB swap and 2 GB ext-4 on my class 4 16GB.
Also understand that using m2sd one can mount /data on ext-4 (r mount) and /sdext on internal nand.
Sent from my Idea Blade
rahulsa said:
1. Ok, new learning for me.
2. Good to know this. I was bit worried initially with my 256MB swap size. As I saw 0 or 32 MB swap in many posts. But after 2 weeks I confirm that it was the best thing I did for my Blade. Yes it was even better than using sd card's ext4 partition for more space. Low RAM was a bit serious issue for me than low space.
3. I know swap and ext partition are different. I have 256MB swap and 2 GB ext-4 on my class 4 16GB.
Also understand that using m2sd one can mount /data on ext-4 (r mount) and /sdext on internal nand.
Sent from my Idea Blade
Click to expand...
Click to collapse
3. Just nitpicking but the way it works is to mount data to /sd-ext/data, /sd-ext is just the mount point for your ext partition (which may be ext2, ext3 or ext4 depending on how you configured it during partitioning and how you mount it). Depending on how you do this you can have data, app, dalvik-cache and app-private mounted to /sd-ext/[folder] (this is the common way of using it when you use my script and S2E).
Jinxxed said:
... Depending on how you do this you can have data, app, dalvik-cache and app-private mounted to /sd-ext/[folder] (this is the common way of using it when you use my script and S2E).
Click to expand...
Click to collapse
May I know your script name?
Using your script which of above should be moved last, I mean with swap already might take a portion of sd card i/o and hence i fear, may make overall speed very slow.
Or for enabling all of them should i upgrade to faster sd card?
Currently I am happy with swap and apps on sd card, rest all on int. nand.
Sent from my Idea Blade
rahulsa said:
May I know your script name?
Using your script which of above should be moved last, I mean with swap already might take a portion of sd card i/o and hence i fear, may make overall speed very slow.
Or for enabling all of them should i upgrade to faster sd card?
Currently I am happy with swap and apps on sd card, rest all on int. nand.
Sent from my Idea Blade
Click to expand...
Click to collapse
S2E-Swap-Jinxxed.zip is the name, you flash it via recovery. https://dl.dropbox.com/u/54672755/S2E-Swap-Jinxxed.zip
It's basically a set of init.d scripts for proper configuration of swap, mounting of sd-ext and the S2E application to move apps, data and cache (you can choose what you want to move and what you want to leave on your internal nand data partition) to sd-ext.
It works on all roms that don't have S2E support from the get go including all ICS variants and JB.
Jinxxed said:
S2E-Swap-Jinxxed.zip is the name, you flash it via recovery. https://dl.dropbox.com/u/54672755/S2E-Swap-Jinxxed.zip
It's basically a set of init.d scripts for proper configuration of swap, mounting of sd-ext and the S2E application to move apps, data and cache (you can choose what you want to move and what you want to leave on your internal nand data partition) to sd-ext.
It works on all roms that don't have S2E support from the get go including all ICS variants and JB.
Click to expand...
Click to collapse
To deactivate mounts2sd-4.6.2 script and use your script.
I did following after getting your answer as PM.
I deleted 10mounts2sd script from \system\etc\init.d\ .
While observing S2E-Swap-Jinxxed.zip, I realized that it contained s2e.apk in /system/app.
So I actually installed s2e from from market to get latest version.
Then to enable swap and other optimizations, I added following lines in begining of 20userinit script present in /etc/init.d .
mount -o remount,noatime,nodiratime,relatime,barrier=0,nobh /system
mount -o remount,noatime,nodiratime,relatime /data
swapon /dev/block/mmcblk0p3
So I got what I wanted and also learnt many things in the process.
Also experimented with /etc/sysctl.conf by adding vm.swappiness=50 (initially 70).
---------- Post added at 08:47 PM ---------- Previous post was at 08:26 PM ----------
Jinxxed said:
1. CWM will use TAR to make the backups so it's the same thing, to make a clone of the partition you'll need to use cc.
....
Click to expand...
Click to collapse
I backed up my Blade using the latest ClockworkMod 5.0.2.0 .
CWM backup up saying done, but with a message.
It said it did not backup up /sd-ext or external ext2/3/4 partition.
So I was worried to use app-to-ext scripts or programs.
Now I successfully used tar to backup sd-ext and restore it on a faster (class 4 to 6) sd card.
But I would like know if there is any new version of CWM for Blade 6.0.1.2 with or without touch, which backs up ext2/3/4 without any issues.
If yes, I would upgrade my CWM.
It saves time to use CWM, compared to tar.
Thanks in advance.
Hello everyone and thank you for having me on your wonderful forum. I have learned so much in such a short time by reading everything I could whether I was intending to use it or not.
I got my 16gb Nexus on Monday and immediately prepped it for ROMs, settling on CM10.1 RC2, Prior to that I had an Optimus V running CM7. On my Optimus, after flashing CM7 for the long haul I was able to move all excess /system space back into /data using terminal emulator and the fdisk command, but I followed a guide of some sort that is long lost now.
Everything is fantastic so far except one thing, there seems to be quite a lot of space reserved in the /system and /cache partitions, and I am not sure if I am able to re-partition this space back to /data or how exactly to do this.
right now /system is reading at 395.8 / 827.8 MB used, and /cache is at 68.4 / 551.7 MB. I would like to repartition 200 MB away from /system and 300-400 MB away from /cache, and put it back into /data. This will leave me some space to integrate or convert a few apps to system apps, and enough cache space to be safe (why does it need 550 MB to begin with?) and give back another half gig of storage that I paid so much to have.
I have three issues with this, one being that I can find almost no information on this topic directly mentioning the NExus 4, and any relatable information from other devices talking about device specific toolkits to do the job.
The only thread I found on XDA about this is below, and it only gave me a vague "this is not possible"
http://forum.xda-developers.com/showthread.php?t=2248400
The second issue is I do not recall the command switches/flags that go with the fdisk command, only that I had to use some things to set file permissions or remount the partition or some such (I know, i'm a noob, forgive me).
Lastly, I am rather confused by the multiple partitions of /data and /storage/emulated all showing a partition size of 13231.8 MB. Obviously they are all the same physical space, but I am afraid to mess with the partitions and break what I assume are a ton of symlinks that trick apps into believing there is an external SD card in play. Can any of you shed some light on this for me?
I3ig Al said:
Hello everyone and thank you for having me on your wonderful forum. I have learned so much in such a short time by reading everything I could whether I was intending to use it or not.
I got my 16gb Nexus on Monday and immediately prepped it for ROMs, settling on CM10.1 RC2, Prior to that I had an Optimus V running CM7. On my Optimus, after flashing CM7 for the long haul I was able to move all excess /system space back into /data using terminal emulator and the fdisk command, but I followed a guide of some sort that is long lost now.
Everything is fantastic so far except one thing, there seems to be quite a lot of space reserved in the /system and /cache partitions, and I am not sure if I am able to re-partition this space back to /data or how exactly to do this.
right now /system is reading at 395.8 / 827.8 MB used, and /cache is at 68.4 / 551.7 MB. I would like to repartition 200 MB away from /system and 300-400 MB away from /cache, and put it back into /data. This will leave me some space to integrate or convert a few apps to system apps, and enough cache space to be safe (why does it need 550 MB to begin with?) and give back another half gig of storage that I paid so much to have.
I have three issues with this, one being that I can find almost no information on this topic directly mentioning the NExus 4, and any relatable information from other devices talking about device specific toolkits to do the job.
The only thread I found on XDA about this is below, and it only gave me a vague "this is not possible"
http://forum.xda-developers.com/showthread.php?t=2248400
The second issue is I do not recall the command switches/flags that go with the fdisk command, only that I had to use some things to set file permissions or remount the partition or some such (I know, i'm a noob, forgive me).
Lastly, I am rather confused by the multiple partitions of /data and /storage/emulated all showing a partition size of 13231.8 MB. Obviously they are all the same physical space, but I am afraid to mess with the partitions and break what I assume are a ton of symlinks that trick apps into believing there is an external SD card in play. Can any of you shed some light on this for me?
Click to expand...
Click to collapse
nexus4 doesn´t have a fix size for partitions, you can use the whole memory for everything... no need to re-partition anything
75markus said:
nexus4 doesn´t have a fix size for partitions, you can use the whole memory for everything... no need to re-partition anything
Click to expand...
Click to collapse
I'm not sure if you are misunderstanding or not reading my whole post, or if I am not understanding you or the situation I am posting about, so please don't take offense to this reply.
It appears to me that the /system partition is reserving 827 MB space for the ROM, and CM10.1 is only using 400 MB of it
It also appears that 552 MB is reserved for the /cache partition, and only 70 MB is being currently used.
This is ~900 MB of storage space that is reserved and unused. I would like to know if it is possible to reallocate ~500-600 MB of this back into the /data partition for user space.
Please explain to me how this space is part of the whole memory that can be used for anything.
After posting I have thought some more about it and decided to NOT mess with the partition sizes, mainly because I do not know what effect it would have if I were to flash another ROM in the future, which is almost a given when Key Lime Pie is released. However I would still like to understand what I have asked about in case I do want to do this in the future, and also just for the sake of expanding my knowledge.
I like this. The only "issue" is that if more space were ever to be reallocated to /system or /cache, it'd require wiping /data obviously. Small price to pay. 500MB isn't too small a chunk for 8GB users.
75markus said:
nexus4 doesn´t have a fix size for partitions, you can use the whole memory for everything... no need to re-partition anything
Click to expand...
Click to collapse
Actually it does. System data cache and boot, plus like 30 other ones, same as any other phone with no micro SD card
Sent from my Nexus 7 @1.60 GHz on Stock 4.2.2
I3ig Al said:
I'm not sure if you are misunderstanding or not reading my whole post, or if I am not understanding you or the situation I am posting about, so please don't take offense to this reply.
It appears to me that the /system partition is reserving 827 MB space for the ROM, and CM10.1 is only using 400 MB of it
It also appears that 552 MB is reserved for the /cache partition, and only 70 MB is being currently used.
This is ~900 MB of storage space that is reserved and unused. I would like to know if it is possible to reallocate ~500-600 MB of this back into the /data partition for user space.
Please explain to me how this space is part of the whole memory that can be used for anything.
After posting I have thought some more about it and decided to NOT mess with the partition sizes, mainly because I do not know what effect it would have if I were to flash another ROM in the future, which is almost a given when Key Lime Pie is released. However I would still like to understand what I have asked about in case I do want to do this in the future, and also just for the sake of expanding my knowledge.
Click to expand...
Click to collapse
i think N4 uses FUSE (Filesystem in Userspace) file system
noobdeagle said:
isnt this what they were saying was the reason for no SD card and use of MTP ?; basically if i recall correctly the nexus devices do not truly assign partitions instead there is a storage 'pool' that anything can use dynamically.
so i guess there is no partitions its just all 1 volume.
source: http://www.androidcentral.com/why-nexus-devices-have-no-sd-card
Click to expand...
Click to collapse
That is for the sdcard.
The other partitions such as /system still have fixed amounts of space allocated
Sent from my Nexus 4 using xda app-developers app