Develop Bugs

[REQUEST] MBR/partitions layout for 16GB version Galaxy S

Hey
As some maybe know I'm working on a lag fix for our Galaxy S.
This lag fix uses ext4 as native filesystem directly on the internal SD to replace rfs.
Features and description here
I'm coding the migration procedure right now and just figured that I need the partition layout of 16GB models to support them
Here is how you can get this data (as root)
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/mbr.bin bs=512 count=1
This command will produce a little file describing how your Galaxy S partitions are arranged. You'll find this file as "mbr.bin" in the SD mounted on your computer.
It does not contain any personal information.
required too, the result of :
Code:
cat /sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/size
Thanks !
Sample partition layout dump of the 8GB version :
Code:
$ sfdisk -d mbr_samsung
# partition table of mbr_samsung
unit: sectors
mbr_samsung1 : start= 64, size= 12124096, Id= c
mbr_samsung2 : start= 12124160, size= 3932160, Id= c
mbr_samsung3 : start= 0, size= 0, Id= 0
mbr_samsung4 : start= 0, size= 0, Id= 0

cant open for read mmcblk0 .. Egh.. i hate terminal on android

andrewluecke said:
cant open for read mmcblk0 .. Egh.. i hate terminal on android
Click to expand...
Click to collapse
This should be no problem as root

Egh.. Someone else should do it then.. My phone isn't rooted atm

Hey supercurio
Just wondering if you have done any speed testing at all on native EXT4?
Does the phone lock up when writing large files?

Here's mine. Just FYI, not sure if it matters, but i'm on JP3 with the "one click" lag fix.
Also, I'd be happy to beta test your fix on my 16gb SGS. I've pretty much tried them all

I9000 16GB - MBR layout
Here's from a Galaxy S running JM5 + Samset1.9f

I gave this a try on my 16GB SGS
Double checked the syntax and its telling me:
dd: can't open "/dev/block/mmcblk0': permission denied.
Im rooted with su also

supercurio said:
This should be no problem as root
Click to expand...
Click to collapse
well i'm rooted and using terminal emulator and ADB through my PC gets the same result as he posted.
*EDIT - Here's mine sorry rebooted and it ran just fine. this is JM2 with the one click lag fix just for the info.
If it matters Bell vibrant i9000m 16gb model.
Goodluck

Thank you Spybreak and titovic !
Both your mbr are bit-identical, this is a good news
I guess I need another value to detect which hardware I deal with :
Code:
cat /sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/size
Thx again
For the record, here is the partition table of your devices :
Code:
$ sfdisk -d mbr-16Go
# partition table of mbr-16Go
unit: sectors
mbr-16Go1 : start= 64, size= 28180416, Id= c
mbr-16Go2 : start= 28180480, size= 3932160, Id= c
mbr-16Go3 : start= 0, size= 0, Id= 0
mbr-16Go4 : start= 0, size= 0, Id= 0
@RyanZA about tests, I played about 3 hours with my device formatted as native ext2.
I was quite surprised by the responsiveness even when installing apps. I did not thought that the difference would be so drastic
I'll do extensive tests to find the best settings.
My goal is to preserve a maximum of interactivity, by consequence it will lower the benchmark settings a bit.
Here is an example of Quadrant run on /data as ext2 (no settings customization)
Note : I used ext2 because my e2fsprogs produced by default ext4 and ext3 formats that the old 2.6.29 drivers were not able to read
PS :
Quadrant score will theoretically always be lower than those obtained with mount -o loop because the filesystem honors fsyncs(), and SQLite database used in Android use fsync big time (and there is a reason why!)

Bell i9000M, rooted, JH2.
New request:
31260672
Question: why journalized fs on a flash device though?

canadian_psyko said:
Bell i9000M, rooted, JH2.
New request:
31260672
Question: why journalized fs on a flash device though?
Click to expand...
Click to collapse
Because you can corrupt a filesystem on flash exactly the same way that on a hard drive :
Kernel driver crash / phone lockup
Abrupt power down (remove the battery)
Abrupt reboot, pressing a combination of keys.
The flash disk here is presented as block, so it looks like a hard drive to the filesystem.
PS : thansk for your 31260672

wow this looks promising. but why don't you consider using YAFFS2 which is also used in Nexus One? havent heard anyone complaining of our kind of lag in the N1

+1, seems a reasonable choice. For testing anyway.

Agreed with the above, most likely YAFFS2 should be used, especially since Google decided it's the way to go =)

supercurio said:
Thank you Spybreak and titovic !
Both your mbr are bit-identical, this is a good news
I guess I need another value to detect which hardware I deal with :
Code:
cat /sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/size
Thx again
Click to expand...
Click to collapse
Here's mine from a 16gb i9000 (singapore version) with JM5 and pit512. Won't the pit file used to flash your ROM affect this, or at least the original data you requested...?
Code:
# cat /sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/size
32112640
Also, attached is my mbr.bin from the 16gb phone mentioned above.
I like the idea of yaffs also, but would require custom kernels.
I'm glad to see someone working on this, I think it's ultimately the best solution. I was thinking of trying to mess around with it myself, but decided it was a bit beyond my skill levels...basically backup the partition, format in yaffs, then restore the data, right?

stock kernel doesnt not support yaffs2

raspdeep said:
stock kernel doesnt not support yaffs2
Click to expand...
Click to collapse
Yes, you're correct, I was just coming back to edit that out of my post. I forgot I was still running a custom kernel the last time I ran cat /proc/filesystems and that kernel supported yaffs. I'm back on stock JM5 kernel now and see no yaffs support.
original post amended.

ok, you are probably running my kernel.. that kernel is kinda outdated cos the OC div table is not done properly so flash back to stock or my latest oc kernel with wake lag fixed

raspdeep said:
stock kernel doesnt not support yaffs2
Click to expand...
Click to collapse
Yes, but why not make an ultimate fix using your updated kernel? =)

[Q] Searching Kernel for SWAP on my SENSE-ROM

Hello,
After i have runed well supercharger , i want to swap mi sdcard. But many kernels does not support this. And i get error via adb (applet not found) , i have a sense based rom (rcmix) wich has already by 100-150mb ram free , but i want to have swap , wich kernel works for that?

unity and rcmix3d kernel both support swap...
your problem must be something else. How did you create your swap partition? (means you first have to format your sdcard and create a swap partition)
maybe redownload the script
EDIT: and use the thanks button if people try to help you... (i saw you posted your problem in different threads)

I have partitioned the SD , i add i tryed with two different SD cards. And not working , the error seems is because the kernel does not support it

xdadevolpers said:
I have partitioned the SD , i add i tryed with two different SD cards. And not working , the error seems is because the kernel does not support it
Click to expand...
Click to collapse
hm... never had problems with unity kernel (swap related), which version of unity do you use?
unity kernel v10 supports swap for sure

Ok solved , there was busybox version problem

[tutorial][enable linux swap][alquez unoffical cm7.2]

First: Have Alquez's CM7.2 installed
Second: Flash his new kernel that supports linux swap partitions
Third: Read my tutorial on creating a Ext partition and a third Linux swap partition
Fourth: Read this post by me on how to enable swap persistantly and adjust swappiness.

Does it make any sense to use a swap partition?
I think, no. Why not? Read about in the official cm wiki: http://wiki.cyanogenmod.com/wiki/Swap_and_Compcache
Android has a very good built-in memory management. Apps not used any more will be closed and memory released. Swap does change that behavior, because RAM now (virtually) is much bigger. There's no sense anymore in cleaning parts of the RAM.
Androids mem management is much more efficient.
The only reason to use swap would be 1st generation phones (G1, Dream, Magic). Wildfire S would have no advantage of swap! Rather the opposite.
Using swap should require at least class 6 SD for not slowing down the device. Plus, the additional write accesses will wear down your sd much quicker.
Everyone has to decide if he wants this. I decided, not to do.

theq86 said:
does it make any sense to use a swap partition?
Click to expand...
Click to collapse
I'm just telling you how. You'll have to decide that for yourself.
Personally I'm just playing around with it...cause I can.

d33ps1x said:
I'm just telling you how. You'll have to decide that for yourself.
Personally I'm just playing around with it...cause I can.
Click to expand...
Click to collapse
Well, I read a little bout that topic and consider it more harming than useful. (read my edited post above)

Consider setting /proc/sys/vm/swappiness to 10 or even lower for android ?

what on earth is swap anyway?

swap is taking apart of your sd card or internal memory as ram memory like pageing file in windows

[Q] [Script Development] Expand Ram with external SD card.

Background....
I used swapper2 and bricked my device.
Still I can't stop myself.
We all SGW I8150 users have low ram just 351MB.
Creating a startup script that adress swap partition on EXTERNAL SD card ( Preferred Class10) can be usefull for us to inrease our devices speed and responsiveness.
mkswap /dev/block/mmcblk1p2
The script can also include I/O tweaks for external SD card...
Inspired from: ( Don'nt flash this. It is not compatible. Also it targets main sd card.)
http://forum.cyanogenmod.com/topic/208-swap-enabledisable/page__st__10
http://www.igottadroid.com/ModMarket/Listings/Yank5551630095.html
V2:
Also another idea to swap SD0 to SD1 and the idea above.

Solved.
http://www.igottadroid.com/ModMarket/Listings/Yank5551630095.html

the best choice for now..try use turbo boost..it's not increase your ram,but it will free more ram..and your phone become smooth and responsive
Sent from my GT-I8150 using Tapatalk 4

i want to ask as i didn't understand
you provide us a script for expanding Ram or asking about a script to increase ram?

Android L for Galaxy W? In Custom way?

Oh,,, hell yeah, i want it badly. :victory:

+1

No. No sources are released, and you'll have to find someone to port it when the sources are released in the fall.

SGWUser said:
No. No sources are released, and you'll have to find someone to port it when the sources are released in the fall.
Click to expand...
Click to collapse
Maybe sir arco will save us again when the sources are released You never know..

a port may come soon but we have to wait until it is final so they release cm 12

eri000 said:
a port may come soon but we have to wait until it is final so they release cm 12
Click to expand...
Click to collapse
That isn't necessarily true, for example CM 10.1 released by arco still in beta4 version

dqsnunes said:
That isn't necessarily true, for example CM 10.1 released by arco still in beta4 version
Click to expand...
Click to collapse
the CM team announced that there will be NO CM version until the google releases the final image of android L on AOSP.This doesn't mean we will have a final stable version of cm immediately BUT we will only see a cm12 build when final android L gets merged into aosp.
^That is for other phones that get CM OFFICIAL.For ancora we have to wait a little bit more for unofficial cm, which is based on official cm.So no official--- no unofficial (arco if he has time to mess with it,or others)

BTW, Android L is currently being ported to the Nexus 4 and Nexus 7 2012 right now. Both are almost functional.

I think even if we were to have Android L here, i don't think it will be responsive. Google said, Animation transitions run at 60fps, Im not sure if overall perfomance can run at the same fps because i bet our processor is not powerful enuff or smth. CMIIW.

Android L Port For Nexus 4
Newest Android L Port For Nexus 4 Is Now Fully Operational And Ready For Download
INFO

I strongly doubt that our device could get an Android L update.
The default runtime of android l is ART runtime.Our device does'nt hold that much of system memory for apps.
The only chance is to make a switchable runtime like in Kitkat (Dalvik/Art) or creating a new partition .
Anyway these are all guess and lets see what magic our Great devs can bring to our small beloved device.:good::fingers-crossed:

theloneseeker said:
I strongly doubt that our device could get an Android L update.
The default runtime of android l is ART runtime.Our device does'nt hold that much of system memory for apps.
The only chance is to make a switchable runtime like in Kitkat (Dalvik/Art) or creating a new partition .
Anyway these are all guess and lets see what magic our Great devs can bring to our small beloved device.:good::fingers-crossed:
Click to expand...
Click to collapse
A swap partition for art can't help?

theloneseeker said:
I strongly doubt that our device could get an Android L update.
The default runtime of android l is ART runtime.Our device does'nt hold that much of system memory for apps.
The only chance is to make a switchable runtime like in Kitkat (Dalvik/Art) or creating a new partition .
Anyway these are all guess and lets see what magic our Great devs can bring to our small beloved device.:good::fingers-crossed:
Click to expand...
Click to collapse
Problem is not a system partition because system partition size(550mb) should be enough because at the moment with latest cm11+gapps i have a 150 mb free space on my system partition so i think our phone can/will handle next android release but we cant know at the moment so im not sure
But main problem is small cache partition
İt is just 60 mb
For that reason we are using some dirty workarounds(in my opinion) like this https://github.com/arco/android_device_samsung_ancora/commit/3455d7837c951e297335295a36cd2202a9f629f3 with that workaround apps is using /data partition instead of /cache partition for dalvik-caching operations
Why im saying this is dirty workaround? Because i think each operation should use its own partition
Repartition is a real fix for that kind of problems but this way is a very dangerous and have brick risk
İm planning to make some experiments like this:
-With fdisk im planning to split out my internat sdcard(1.7 GB ,mmcblk0p28) to 2 new partitions(first partition will be mmcblk0p28 and have 1.3 GB size and second partition will be mmcblk0p29 and have 400 MB size)
Then we will use mmcblk0p29 as cache partition
-For that firstly we need to format the partition as ext4(because internal sd is vfat but cache partition must be ext4 fs type formatted)
-After converting from vfat to ext4 of new mmcblk0p29 partition, we will change cache partition from mmcblk0p16 to 29 through fstab.qcom
-and last thing we need to do is removing/disabling previous workaround so we will change the following build.prop line dalvik.vm.dexopt-data-only=1 to dalvik.vm.dexopt-data-only=0
This is the cleanest way i think because we arent touching to main partitions(system,data and cache)
We just need to split it internal sd(1.7 GB)
Regards

sir mordred said:
Problem is not a system partition because system partition size(550mb) should be enough because at the moment with latest cm11+gapps i have a 150 mb free space on my system partition so i think our phone can/will handle next android release but we cant know at the moment so im not sure
But main problem is small cache partition
İt is just 60 mb
For that reason we are using some dirty workarounds(in my opinion) like this https://github.com/arco/android_device_samsung_ancora/commit/3455d7837c951e297335295a36cd2202a9f629f3 with that workaround apps is using /data partition instead of /cache partition for dalvik-caching operations
Why im saying this is dirty workaround? Because i think each operation should use its own partition
Repartition is a real fix for that kind of problems but this way is a very dangerous and have brick risk
İm planning to make some experiments like this:
-With fdisk im planning to split out my internat sdcard(1.7 GB ,mmcblk0p28) to 2 new partitions(first partition will be mmcblk0p28 and have 1.3 GB size and second partition will be mmcblk0p29 and have 400 MB size)
Then we will use mmcblk0p29 as cache partition
-For that firstly we need to format the partition as ext4(because internal sd is vfat but cache partition must be ext4 fs type formatted)
-After converting from vfat to ext4 of new mmcblk0p29 partition, we will change cache partition from mmcblk0p16 to 29 through fstab.qcom
-and last thing we need to do is removing/disabling previous workaround so we will change the following build.prop line dalvik.vm.dexopt-data-only=1 to dalvik.vm.dexopt-data-only=0
This is the cleanest way i think because we arent touching to main partitions(system,data and cache)
We just need to split it internal sd(1.7 GB)
Regards
Click to expand...
Click to collapse
Nice thinking and good luck :good:

sir mordred said:
Problem is not a system partition because system partition size(550mb) should be enough because at the moment with latest cm11+gapps i have a 150 mb free space on my system partition so i think our phone can/will handle next android release but we cant know at the moment so im not sure
But main problem is small cache partition
İt is just 60 mb
For that reason we are using some dirty workarounds(in my opinion) like this https://github.com/arco/android_device_samsung_ancora/commit/3455d7837c951e297335295a36cd2202a9f629f3 with that workaround apps is using /data partition instead of /cache partition for dalvik-caching operations
Why im saying this is dirty workaround? Because i think each operation should use its own partition
Repartition is a real fix for that kind of problems but this way is a very dangerous and have brick risk
İm planning to make some experiments like this:
-With fdisk im planning to split out my internat sdcard(1.7 GB ,mmcblk0p28) to 2 new partitions(first partition will be mmcblk0p28 and have 1.3 GB size and second partition will be mmcblk0p29 and have 400 MB size)
Then we will use mmcblk0p29 as cache partition
-For that firstly we need to format the partition as ext4(because internal sd is vfat but cache partition must be ext4 fs type formatted)
-After converting from vfat to ext4 of new mmcblk0p29 partition, we will change cache partition from mmcblk0p16 to 29 through fstab.qcom
-and last thing we need to do is removing/disabling previous workaround so we will change the following build.prop line dalvik.vm.dexopt-data-only=1 to dalvik.vm.dexopt-data-only=0
This is the cleanest way i think because we arent touching to main partitions(system,data and cache)
We just need to split it internal sd(1.7 GB)
Regards
Click to expand...
Click to collapse
Umm very interesting if you want some testers,i'm here.

If you have cm11 theme chooser:
http://forum.xda-developers.com/android/themes/theme-l-ready-t2802979
https://play.google.com/store/apps/details?id=nexbit.icons.moonshine
Settings>Performance>Force high-end graphics>check
AND YOU HAVE L IN YOUR WONDER(I LOVE MY WONDER)

what is android L? can someone tell me about it please?

smartiescoke said:
what is android L? can someone tell me about it please?
Click to expand...
Click to collapse
The upcoming Android version. About it...there are many things to say. You could search YouTube for "Google I/O 2014". There are a lot of new things about it. If you've got time to spend and curiosity, it might be very interesting to watch. This way, you will also answer your own question (and more).

arsradu said:
The upcoming Android version. About it...there are many things to say. You could search YouTube for "Google I/O 2014". There are a lot of new things about it. If you've got time to spend and curiosity, it might be very interesting to watch. This way, you will also answer your own question (and more).
Click to expand...
Click to collapse
whoa! really? awesome! i always been waiting google to update different kind of android version. ui and etc, hope it will come to our wonder soon! XD

oh man i love android L ui and statusbar. Hoping our Great Developer can bring this to our Wonder.
#sorry for my bad english.