Hi
As you know Samsung Galaxy S (i9000) has one internal flash memory ( 8 or 16 GB) but it is separated as two parts for acting like ROM and the other one is for internal memory...
Mine is 8 GB version. 2 GB is for ROM and the rest( 6GB) is for internal memory. Therefore,this artificial separating causes lagging... I know there are some solution about lagging. However the real problem is still remains.
I think the real solution is not separating internal flash memory . Internal memory should remain one part not two!...
Samsung's point of view can be profitable. But I think it is the cheapest solution!... Samsung's view!!! causes lagging problem!...
So my question : Is there any way to merge internal memory?
Thanx
No, the partitioning itself doesn't cause lag, it's a combination of the RFS filesystem and the MoviNAND controller that causes the lag. You clearly need to do some more reading in the development forum.
It needs to be partitioned in any case though because when the internal SD card is mounted over usb, it is dismounted from the android system. Any apps or data stored in /data would then be inaccessible, causing errors.
Sent from my GT-I9000 using XDA App
I know roughly about RFS and MoviNAND controller. What happens if there is a discrete ROM and 8 (16) GB internal flash memory. You think there wont be any difference (I/O performans etc.) ?
i would certainly like to try and use the full 16 GB as a single system partition instead of the current 2GB + 14GB model
then i can finally load up my full GPS maps into it without having to swap files in and out of the 2 partitions
In Windows world, even in Linux when a single HDD is partitioned in 2 or more chunks, it performs slower.
even though this is a flash disk (it supposed to be unaffected) I'm speculating something similar might be happening in the back end and it causes extra work to system to handle partition 1 vs partition 0
Related
What causes the SGS to lag and what does the "Lag Fix" actually do?
I think its due to samsung using a slow filesystem (rfs) to be fat32 compatible. Theres some devs working to make a full ext4 rom. Rfs does not allow multi access writing so its slow. Some lag fixes use a ext3/4 partition on external card to buffer writes an and use as swap space. Another method is make a ext2 partition file on your internal 8/16gig user space. I personaly prefer the ext4 external card fix as lag fixes can get damaged as multi writes can wear away nand ram so with that in mind a external card is cheaper to replace then a phone. Right now though im not using any lag fixes but jm6 with stockstrip rom which is hell fast so no lag fixes needed. Ive had bad experiences with all of the fixes with system freezing and doing odd things. Worst case I use auto task killer to help
Sent from my GT-I9000 using Tapatalk
ickyboo said:
I think its due to samsung using a slow filesystem (rfs) to be fat32 compatible. Theres some devs working to make a full ext4 rom. Rfs does not allow multi access writing so its slow. Some lag fixes use a ext3/4 partition on external card to buffer writes an and use as swap space. Another method is make a ext2 partition file on your internal 8/16gig user space. I personaly prefer the ext4 external card fix as lag fixes can get damaged as multi writes can wear away nand ram so with that in mind a external card is cheaper to replace then a phone. Right now though im not using any lag fixes but jm6 with stockstrip rom which is hell fast so no lag fixes needed. Ive had bad experiences with all of the fixes with system freezing and doing odd things. Worst case I use auto task killer to help
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Thank you. I think I understand now. I was getting lost in the other threads trying to understand what was going on.
So will Samsung fix this with 2.2 or will they continue with the same file system? Do other manufacturers use this format as well?
No problem. I'm not Samsung so I can't tell you if they are going to fix it or use the Epic 4g fix which is to use a ramdrive, but they should damned well fix it. And as far as I know nothing one else uses the rfs. Beats me why they even use it to begin with
Sent from my GT-I9000 using Tapatalk
How hard would it be to change the Lag Fix to use a small 128Mb virtual RAM drive, rather than the internal SD?
this will solve the corruption seen often in many of the devices people have reported problem with during install, use, and dead internal SD, also avoid unnecessary partition changes which are usually the cause of some SD getting damaged in the process, and voiding the warranty.
in a way the RAM drive will work more very much like a swapspace/pagefile to cache the most recently used files and writing them back only if changes have been made
if it a new App that loads up needs more buffer/cache than it's available it'll write back all the stuff on the cache back to the physical SD to free up space for the new App being loaded.
Also apps that are too big for the 128MB RAM drive will be loaded directly into memory bypassing the RAM drive, and it will safe files directly back to Internal SD, the only times this are expected to happen are with Games, HD movies and such
this will keep the phone fast and responsive, meanwhile reducing the usage of the internal SD
ideally the size of the virtual RAM drive should be configurable to like 64 Mb, 128 Mb, 256 MB, or more (after froyo)
BTW... the goal of this is to help people getting into the situation of getting the internal SD corrupted
AllGamer said:
How hard would it be to change the Lag Fix to use a small 128Mb virtual RAM drive, rather than the internal SD?
this will solve the corruption seen often in many of the devices people have reported problem with during install, use, and dead internal SD, also avoid unnecessary partition changes which are usually the cause of some SD getting damaged in the process, and voiding the warranty.
in a way the RAM drive will work more very much like a swapspace/pagefile to cache the most recently used files and writing them back only if changes have been made
if it a new App that loads up needs more buffer/cache than it's available it'll write back all the stuff on the cache back to the physical SD to free up space for the new App being loaded.
Also apps that are too big for the 128MB RAM drive will be loaded directly into memory bypassing the RAM drive, and it will safe files directly back to Internal SD, the only times this are expected to happen are with Games, HD movies and such
this will keep the phone fast and responsive, meanwhile reducing the usage of the internal SD
ideally the size of the virtual RAM drive should be configurable to like 64 Mb, 128 Mb, 256 MB, or more (after froyo)
Click to expand...
Click to collapse
We already only have like 300mb ram total, with less than 200 free. With a 128mb ram drive, I don't think we'd have enough ram to really run more than 1 app! Plus loading apps into and out of the ram drive would be pretty slow, I think? Managing how to load-unload apps from the ramdrive sounds very very difficult too. You'd modify the dalvik system I guess? Wow, I have no idea how!
yes currently we only have a bit over 300 MB to use, and with a RAM drive it'll be even less, but once we move to Froyo we might be able to get full access to our 512 MB of RAM.
From PC experience even when you have little RAM (512MB Win9x, Win2000) a small RAM drive can still improve system performance drastically even when after mounting the RAM drive you have less RAM available.
Most apps in android even though they reside in memory they don't consume RAM/CPU cycle unless it's actively running in the background or foreground
this can be seen clearly in the stock Task Manager
so even though the amount of RAM is reduced, end users should theoretically be able to run several apps in memory and no experience any delay as only the active 3~5 tasks are swapping in the RAM drive then going back to idle.
in the old times Win9x/2K didn't have that, all the stuff kept running in the back-burner even when the software & services were idle, yet it still worked better with a RAM drive installed than working off the slow 5400 rpm hard drive swap (very similar to the problem with have with the RFS from Samsung vs. Ext2,3,4 FS from Linux)
the current methods that you are the other guys are using for the Lag Fix could work if we can tweak them some how to hold the space elsewhere (External SD), or as you said if we can add 2GB of RAM into the phone
this will give advantage to speed/cache buffer, and prevent wear on the External SD, and even if the External SD does dies, it can be easily replaced without having to send the phone back to Samsung to replace the internal SD.
Hello AllGamer!
Actually data is written to disc because it needs to, that's what differentiate "Ram" and "disk"
The better solution would be to determine exactly where the problem is, and if RFS is the problem, to work towards fixing the bottleneck in the RFS drivers (if possible).
So, many of us want more storage space for apps. It seems that there are a couple of options:
1. Use BlackRose to increase the /data partition.
2. Use DT apps2sd to move the applications to the sd card
3. Use DT apps2sd to move the dalvik cache to the sd card
(or a combination of 2 and 3)
Can anyone provide a clear understanding of what the trade-offs are? Option 1 has some appeal, as it just leaves everything in internal memory and simply repartitions to match the a good setting for my current ROM (OxygeN1mod).
I have used DT apps2sd, but all I moved with the dalvik cache (option 3 above).. It seemed to work OK for a while, then everything seemed to fall apart (FC, etc.) Not sure if the problem was with the SD card, the fact that the dc was moved, or something unrelated.
So, in short, what are the performance considerations of moving either apps or the dalvik cache to the SD card?
The only performance consideration is the speed of your SD card and Nexus' SD controller (the slowest of them), compared to the speed of Nexus' system NAND (the original location of /data partition).
The space consideration is simple - no matter how you split Nexus' partitions, you end up with nothing. I don't have too many apps installed (only 103), and I have 700 MB taken on /data on my MT4G. So even if you squeeze 300MB out of Nexus using Blackrose, it's still nothing.
Jack_R1 said:
The only performance consideration is the speed of your SD card and Nexus' SD controller (the slowest of them), compared to the speed of Nexus' system NAND (the original location of /data partition).
Click to expand...
Click to collapse
In other words, using blackrose means you stay on the system NAND, whereas DT you have the SD controller bottleneck? Do we have any performance measurements on these?
Jack_R1 said:
The space consideration is simple - no matter how you split Nexus' partitions, you end up with nothing. I don't have too many apps installed (only 103), and I have 700 MB taken on /data on my MT4G. So even if you squeeze 300MB out of Nexus using Blackrose, it's still nothing.
Click to expand...
Click to collapse
I thought this was the N1 forum
Sure, getting another phone will give me more NAND. But for me, getting an additional 50-100 MB is what I'm after.
Theoretically, SD controller can be faster than NAND, since NAND is slow. On newer devices with eMMC you can see this very clearly.
The problem is that eMMC use 8 bit MMC protocol, while regular SD card uses 4 bit - this is dropping the performance expectations for N1 2-fold already. Also, SD controller in Nexus One might have a system throughput bottleneck, just like its WiFi path does.
I don't think there are any ready-made measurements, but you can easily make your own. Take a big file (50MB or so), move it from /data to /sd-ext, and move it back. It'll give you a good measurement of write speed. There might be performance measurement apps in the Market, I just didn't ever look. The easiest will be just reading from the same 50MB file, from both locations, and seeing which read takes less time.
I still hang around in N1 forum, since I had this phone for a while, and I made some stuff for it, including sorting and writing a big part of the Wiki. But I don't have the phone anymore.
I'm thoroughly confused, i'm getting low storage notifications, BUT I can't even see what it's related to...
From root explorer:
/datadata is 143MB used 278MB free
/data is 529MB used 962MB free
In the apps menu
Internal is 429MB used 1GB free
SD card 2.8GB used 2.9GB free
RAM 280MB used 129MB free
In about phone
ive got access to 409MB memory.
So at which point is anything there to be alarmed about storage/RAM wise!? I'm confused! I've read into datadata fix and few other options, but there seems to be enough free to go around to not cause any issues surely?
Cheers for any help
Hi - i got same thing with slimbean.. i dont think it caused an issue as i would only get on boot, i'm back on cm 10.1 for the moment though
leperousdust said:
I'm thoroughly confused, i'm getting low storage notifications, BUT I can't even see what it's related to...
From root explorer:
/datadata is 143MB used 278MB free
/data is 529MB used 962MB free
In the apps menu
Internal is 429MB used 1GB free
SD card 2.8GB used 2.9GB free
RAM 280MB used 129MB free
In about phone
ive got access to 409MB memory.
So at which point is anything there to be alarmed about storage/RAM wise!? I'm confused! I've read into datadata fix and few other options, but there seems to be enough free to go around to not cause any issues surely?
Cheers for any help
Click to expand...
Click to collapse
See HERE if this helps you
micks_address said:
Hi - i got same thing with slimbean.. i dont think it caused an issue as i would only get on boot, i'm back on cm 10.1 for the moment though
Click to expand...
Click to collapse
I wasnt sure if it was just a boot thing or not because i dont get constant notifications, but the phone does seem sluggish.... Then again i've just switched from my nexus 4 back to my i9000. My expectations might be a little skewed!
And I've used datafix in the past, I've not tried it yet, but i fail to see how it would help if i've got space?
It's something about the funny partitions the AOSP roms are using. They set a whole load of partitions and define which stuff should go to which partition, so it's a huge pain the *** to try and figure out which of them is full. Using the datafix "relaxes" the partitions, thus giving your phone more room to fit stuff in. This is not an accurate explanation of what's actually going on, but it's close enough.
Hello. I have a question regarding my phone that is constantly running out of storage space and have to use cleaner almost daily. I would like to be able to install more games and other apps but I can't do that due to low internal storage space. I bought a sd card (32 GB) in the hope of installing or moving apps to It. Unfortunately I can't do either. I moved all other files to it but it's not enough.My phone is not rooted and no free program I have tried successed (thought rooting could help). Do I have to buy a new phone to get possibility of using more amount of apps or is there another way? If I have to buy a new phone, recommend me something please. I would like to get a phone with a comparable CPU and GPU or maybe better, at least 4GB+ and 64GB of internal storage or more. It has to be a budget phone but upgrade should be viable.
Hello, I'd like to asked to if you guys also experience this:
Whenever I try to maxxed out the volume and play something whether its a video or music, the phone just reboots right after.
Idk what happened but before I noticed those kind of stuff to happen in my Redmi 9. I just previously fixed it from bootloop w/o recovery & w/o fastboot due to downgrading from MIUI 13.0.5 CN ROM to MIUI 11.0.4 GLOBAL ROM.
So I was wondering whether it was a software issue or hardware issue in this case the battery. Idk if someone had ever tried this but I've watched a similar problem got fixed in youtube w/ Redmi Note 9 instead
with soldering or reheating the fuse within the battery.
TYPICALHUMAN said:
Hello. I have a question regarding my phone that is constantly running out of storage space and have to use cleaner almost daily. I would like to be able to install more games and other apps but I can't do that due to low internal storage space. I bought a sd card (32 GB) in the hope of installing or moving apps to It. Unfortunately I can't do either. I moved all other files to it but it's not enough.My phone is not rooted and no free program I have tried successed (thought rooting could help). Do I have to buy a new phone to get possibility of using more amount of apps or is there another way? If I have to buy a new phone, recommend me something please. I would like to get a phone with a comparable CPU and GPU or maybe better, at least 4GB+ and 64GB of internal storage or more. It has to be a budget phone but upgrade should be viable.
Click to expand...
Click to collapse
Before, Android can still do that transfering apps + associated data to the sd card iirc it was Jellybean. Lol
But right now you can still do that but i think you need some root access correct me if im wrong. Though that is still not advisable cause accessing those apps would be much more slower or rather laggy than installing your apps within the internal storage.
One way to not run out internal storage is to transfer all "passive/static" files like photos/music/videos to your sdcard. The ones that are left for your internal storage should be the apps only that is if you want to install more apps in your device. Also you can set where the files should be saved everytime you take photo or video or download files, and set them to sdcard.