Originally Posted by UnknownzD

I will help you on that as well. btw, I have been told that some devices are using 2.6.X kernel for ICS in CM channel. Therefore it may not be necessary to use 3.X kernel for ICS.

What you speaking about? Better to make the new kernel 3.0 from scratch than to 2.6, which is also already made ​​ardatdat.

Why do you think so? I don't think it is better to start all the things from scratch, coz the the 3.X kernel src lacks the code for tegra 2 platform so much, that no one has sucessfully built a 3.X kernel src before. This is just because nvidia refuses to release the tegra 2 src code they shipped with their product.

Originally Posted by UnknownzD

Why do you think so? I don't think it is better to start all the things from scratch, coz the the 3.X kernel src lacks the code for tegra 2 platform so much, that no one has sucessfully built a 3.X kernel src before. This is just because nvidia refuses to release the tegra 2 src code they shipped with their product.

Thank you sir .

Ace-ing all tests.

Originally Posted by UnknownzD

I will help you on that as well. btw, I have been told that some devices are using 2.6.X kernel for ICS in CM IRC channel. Therefore it may not be necessary to use 3.X kernel for ICS.

How do we go about making a kernel ICS-compatible ?

Ace-ing all tests.

I have found a bug (or better say the config that not yet enabled is wrong) in your github repo for BoardConfig.mk

https://raw.github.com/EmoBoiix3/and...BoardConfig.mk

# BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00480000
# BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00780000
# BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x0cf80000
# BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x0d020000

The correct value should be
# Boot image size is 16384 x 512 bytes = 8388608
# You can double check it with fdisk -l /dev/block/mmcblk0p9
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00800000
# Recovery image size is 10240 x 512 bytes = 5242880
# You can double check it with fdisk -l /dev/block/mmcblk0p8
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00500000
# System image size is 1228800 x 512 bytes = 629145600
# You can double check it with fdisk -l /dev/block/mmcblk0p2
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x25800000
# User data image size is 4194304 x 512 bytes = 2147483648
# You can double check it with fdisk -l /dev/block/mmcblk0p6
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x80000000

I know that someone has said the mmcblk0p* size is in 2048 bytes / unit before, however it is wrong as most of the partitions on mmcblk0 are using 512 bytes / unit only. btw I am trying to dump the pit file out of the device ... wish me luck for that

In addition, this is the recovery.fstab that someone provided to me (and I have confirmed that it should be right)
# mount point fstype device [device2]

/efs ext4 /dev/block/mmcblk0p1
/system ext4 /dev/block/mmcblk0p2
/cache ext4 /dev/block/mmcblk0p3
/sdcard vfat /dev/block/mmcblk0p4
/misc emmc /dev/block/mmcblk0p5
/data ext4 /dev/block/mmcblk0p6
/recovery emmc /dev/block/mmcblk0p8
/boot emmc /dev/block/mmcblk0p9
/prebuilt ext4 /dev/block/mmcblk0p11
/sd-ext vfat /dev/block/mmcblk1p1

and what does it mean?

Originally Posted by UnknownzD

I have found a bug (or better say the config that not yet enabled is wrong) in your github repo for BoardConfig.mk

https://raw.github.com/EmoBoiix3/and...BoardConfig.mk

# BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00480000
# BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00780000
# BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x0cf80000
# BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x0d020000

The correct value should be
# Boot image size is 16384 x 512 bytes = 8388608
# You can double check it with fdisk -l /dev/block/mmcblk0p9
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00800000
# Recovery image size is 10240 x 512 bytes = 5242880
# You can double check it with fdisk -l /dev/block/mmcblk0p8
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00500000
# System image size is 1228800 x 512 bytes = 629145600
# You can double check it with fdisk -l /dev/block/mmcblk0p2
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x25800000
# User data image size is 4194304 x 512 bytes = 2147483648
# You can double check it with fdisk -l /dev/block/mmcblk0p6
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x80000000

I know that someone has said the mmcblk0p* size is in 2048 bytes / unit before, however it is wrong as most of the partitions on mmcblk0 are using 512 bytes / unit only. btw I am trying to dump the pit file out of the device ... wish me luck for that

In addition, this is the recovery.fstab that someone provided to me (and I have confirmed that it should be right)
# mount point fstype device [device2]

/efs ext4 /dev/block/mmcblk0p1
/system ext4 /dev/block/mmcblk0p2
/cache ext4 /dev/block/mmcblk0p3
/sdcard vfat /dev/block/mmcblk0p4
/misc emmc /dev/block/mmcblk0p5
/data ext4 /dev/block/mmcblk0p6
/recovery emmc /dev/block/mmcblk0p8
/boot emmc /dev/block/mmcblk0p9
/prebuilt ext4 /dev/block/mmcblk0p11
/sd-ext vfat /dev/block/mmcblk1p1

Thanks for pointing all of this out, but you should be working on another repo.
Look at the repository on : https://github.com/TeamGalaxyR/andro...amsung_galaxyr

Check out this sources instead, they are for the AOSP but atleast they are working.

Great to see one more developer joining!

Originally Posted by UnknownzD

I have found a bug (or better say the config that not yet enabled is wrong) in your github repo for BoardConfig.mk

https://raw.github.com/EmoBoiix3/and...BoardConfig.mk

# BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00480000
# BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00780000
# BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x0cf80000
# BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x0d020000

The correct value should be
# Boot image size is 16384 x 512 bytes = 8388608
# You can double check it with fdisk -l /dev/block/mmcblk0p9
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00800000
# Recovery image size is 10240 x 512 bytes = 5242880
# You can double check it with fdisk -l /dev/block/mmcblk0p8
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00500000
# System image size is 1228800 x 512 bytes = 629145600
# You can double check it with fdisk -l /dev/block/mmcblk0p2
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x25800000
# User data image size is 4194304 x 512 bytes = 2147483648
# You can double check it with fdisk -l /dev/block/mmcblk0p6
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x80000000

I know that someone has said the mmcblk0p* size is in 2048 bytes / unit before, however it is wrong as most of the partitions on mmcblk0 are using 512 bytes / unit only. btw I am trying to dump the pit file out of the device ... wish me luck for that

In addition, this is the recovery.fstab that someone provided to me (and I have confirmed that it should be right)
# mount point fstype device [device2]

/efs ext4 /dev/block/mmcblk0p1
/system ext4 /dev/block/mmcblk0p2
/cache ext4 /dev/block/mmcblk0p3
/sdcard vfat /dev/block/mmcblk0p4
/misc emmc /dev/block/mmcblk0p5
/data ext4 /dev/block/mmcblk0p6
/recovery emmc /dev/block/mmcblk0p8
/boot emmc /dev/block/mmcblk0p9
/prebuilt ext4 /dev/block/mmcblk0p11
/sd-ext vfat /dev/block/mmcblk1p1

I.....love.....you !
I'll make the appropriate changes !
Thanks a bunch !

This was sent from a Galaxy Ace. Problem?

Originally Posted by EmoBoiix3

I.....love.....you !
I'll make the appropriate changes !
Thanks a bunch !

This was sent from a Galaxy Ace. Problem?

Make sure you add TARGET_ARCH_VARIANT_FPU := vfpv3 to Boardconfig.mk too.
(According to the good info from UnknownzD in another thread, thanks again!)

This could really be the key for getting CM7 to work!!!

Excitement!


Sent from my GT-I9103 using xda premium