[Kernel] Custom kernel for Samsung galaxy core 2
Does anyone know how to compile custom kernel for our device.
edit the tittle of thread to [ASK]. cz ur thread is about questions.
Dhruvit Pokharna said:
Does anyone know how to compile custom kernel for our device.
Click to expand...
Click to collapse
I do.
Then lets compile a kernel together
Dhruvit Pokharna said:
Then lets compile a kernel together
Click to expand...
Click to collapse
Just building one to see what will come up
ok
Is there amajor differences between the kernel of G355H to G355HN?
No
zyn06 said:
Is there amajor differences between the kernel of G355H to G355HN?
Click to expand...
Click to collapse
It should be no difference at all.
got problem. Kernel size is 4.9 mb which is odd. I might missed something in boardconfig.mk so help...
here:
Code:
TARGET_ARCH := arm
TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM := sc8830
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv7-a-neon
TARGET_CPU_VARIANT := cortex-a7
TARGET_CPU_SMP := true
ARCH_ARM_HAVE_TLS_REGISTER := true
TARGET_BOOTLOADER_BOARD_NAME := kanas3gnfcxx
# Kernel
TARGET_KERNEL_CONFIG := kanas3gnfc_hw04_defconfig
TARGET_KERNEL_SOURCE := kernel/samsung/core2
BOARD_KERNEL_CMDLINE := console=ttyS1,115200n8
BOARD_KERNEL_BASE := 0x00000000
BOARD_KERNEL_PAGESIZE := 2048
# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_FLASH_BLOCK_SIZE := 131072
i dont know much about kernel compiling but you should compare it with stock kernel
Dhruvit Pokharna said:
i dont know much about kernel compiling but you should compare it with stock kernel
Click to expand...
Click to collapse
I did. kernel (no boot.img) size pulled from official firmware is aprox 12 mb.
http://forum.xda-developers.com/showthread.php?t=1698582
Dhruvit Pokharna said:
http://forum.xda-developers.com/showthread.php?t=1698582
Click to expand...
Click to collapse
The. But I haven't used windows for a while
build it but size of boot.img is 5,5 mb? .
Y300-0100 said:
The. But I haven't used windows for a while
build it but size of boot.img is 5,5 mb? .
Click to expand...
Click to collapse
Could it be that samsung used different approach for building kernel?
No but Samsung had put something we dont know
Y300-0100 said:
The. But I haven't used windows for a while
build it but size of boot.img is 5,5 mb? .
Click to expand...
Click to collapse
But cygwin is just a copyright of Linux terminal you can use linux
and @Y300-0100 can you tell which guide you used to compile kernel
@Y300-0100 i have also made kernel but it is 4.8mb
Dhruvit Pokharna said:
and @Y300-0100 can you tell which guide you used to compile kernel
Click to expand...
Click to collapse
There are two ways. Build just kernel and build boot imag .
I used my modified device tree for recovery. And same process as for building recovery except command line is make bootimage.
Related
Here's a guide on how to build paranoidandroid from source for skyrocket.
Note this assumes you already have a build environment setup.
First is ics:
First make a working directory:
For example: mkdir ~/paranoid; cd ~/paranoid
Initialize the repo:
repo init -u git://github.com/ParanoidAndroid/android.git -b ics
Create a local_manifest.xml with these contents:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/samsung/hercules" name="CyanogenMod/android_device_samsung_hercules" remote="github" revision="ics" />
<project path="device/samsung/skyrocket" name="CyanogenMod/android_device_samsung_skyrocket" remote="github" revision="ics" />
<project path="device/samsung/msm8660-common" name="CyanogenMod/android_device_samsung_msm8660-common" remote="github" revision="ics" />
<project path="kernel/samsung/msm8660-common" name="CyanogenMod/android_kernel_samsung_msm8660-common" remote="github" revision="ics" />
<project path="vendor/samsung" name="TeamChopsticks/proprietary_vendor_samsung" remote="github" revision="ics" />
</manifest>
Then checkout the source:
repo sync
Before building:
go to device/samsung/skyrocket and open vendorsetup.sh:
change cm_skyrocket to pa_skyrocket save and exit
Now open cm.mk
and add:
Code:
# Inherit PA stuff
$(call inherit-product, vendor/pa/config/pa_common.mk)
under:
Code:
# Inherit some common CM stuff.
$(call inherit-product, vendor/cm/config/gsm.mk)
so that it looks like:
Code:
$(call inherit-product, device/samsung/skyrocket/full_skyrocket.mk)
# Inherit some common CM stuff.
$(call inherit-product, vendor/cm/config/gsm.mk)
# Inherit PA stuff
$(call inherit-product, vendor/pa/config/pa_common.mk)
# Enhanced NFC
$(call inherit-product, vendor/cm/config/nfc_enhanced.mk)
# Inherit some common CM stuff.
$(call inherit-product, vendor/cm/config/common_full_phone.mk)
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=SGH-I727 TARGET_DEVICE=SGH-I727 BUILD_FINGERPRINT="samsung/SGH-I727/SGH-I727:4.0.4/IMM76D/UCLF6:user/release-keys" PRIVATE_BUILD_DESC="SGH-I727-user 4.0.4 IMM76D UCLF6 release-keys"
TARGET_BOOTANIMATION_NAME := vertical-480x800
PRODUCT_NAME := pa_skyrocket
PRODUCT_DEVICE := skyrocket
now run lunch and select pa_skyrocket-eng
then make -j4 bacon
I'm pretty sure that's it. If I missed anything lt me know.
Here's my build, untested of course:pa_skyrocket-1.6a-16AUG2012-130315.zip
For paranoid jellybean: still building will post a guide once I have a build, so I know that it works.
Maybe an aokp guide if people want it.
any news on jb guide?
Skickat från min GT-N7000 via Tapatalk 2
Utacka said:
any news on jb guide?
Skickat från min GT-N7000 via Tapatalk 2
Click to expand...
Click to collapse
Go to project rookie. Should have all you need. Plus the community over there can certainly help you with any questions you have.
------------------------------------------------
Sent from my Skyrocket i727 running AOKP JB
For a one stop shop are Vincom's threads
Everything Root: http://forum.xda-developers.com/showthread.php?t=1773659
Returning to Stock: http://forum.xda-developers.com/showthread.php?t=1652398
Hello everyone!!!
This is a continuation of rapmv78's ICS Camera HAL for 2.6 kernel. Great thanks to nobodyAtall who helped get this working
THINGS YOU WILL NEED:
A working ICS ROM for your device
A lot of time
Now this can be adapted to any phone, but it is designed for the LG Optimus One (P500)
I will upload the panorama fix to my GitHub as soon as I finish porting the code for it
SOURCES:
https://github.com/androidarmv6/android_device_libcamera
Camera app changes coming soon!
Frameworks changes coming soon!
TO FIX VIDEO RECORDING AND PLAYBACK:
To fix video you will need the lib/libstagefright_soft_aacdec.so file from your ICS ROM. Setup a vendor pregenerated lib by adding that .so to your COMMONFOLDERNAME/proprietary/lib/libstagefright_soft_aacdec.so
TO INSTALL:
1. Follow the instructions in the READMEs in the repos
2. In your BoardConfigCommon.mk, delete the following lines IF THEY EXIST:
(Note: these are scattered all over the file, so look for them)
COMMON_GLOBAL_CFLAGS += -DICS_CAMERA_BLOB
TARGET_USE_OVERLAY := false
TARGET_HAVE_BYPASS := false
TARGET_USES_C2D_COMPOSITION := false
COMMON_GLOBAL_CFLAGS += -DREFRESH_RATE=60
3. Now add these lines to your BoardConfigCommon.mk
TARGET_DISABLE_ARM_PIE := true
TARGET_BOOTANIMATION_USE_RGB565 := true
TARGET_BOOTANIMATION_TEXTURE_CACHE := true
Note that the following 2 might not be needed based on your device, but most devices will need them
TARGET_NO_HW_VSYNC := true
COMMON_GLOBAL_CFLAGS += -DQCOM_NO_SECURE_PLAYBACK
4. Edit the files in the DEVICE/libcamera folder to suit your device
Again, thanks to nobodyAtall for getting this to work!!!
are you sure that this line need to be removed?
COMMON_GLOBAL_CFLAGS += -DREFRESH_RATE=60
Yes
Or else you get weird issues with the screen
How to do this "Setup a vendor pregenerated lib by adding that .so to your COMMONFOLDERNAME/proprietary/lib/libstagefright_soft_aacdec.so"??
I have an x10 and camera works but with small grey bar at the bottom in 8 Mpx but 6MPx works fine.. No video recording nd panaroma..
Rashed97 said:
Hello everyone!!!
This is a continuation of rapmv78's ICS Camera HAL for 2.6 kernel. Great thanks to nobodyAtall who helped get this working
THINGS YOU WILL NEED:
A working ICS ROM for your device
A lot of time
Now this can be adapted to any phone, but it is designed for the LG Optimus One (P500)
I will upload the panorama fix to my GitHub as soon as I finish porting the code for it
SOURCES:
https://github.com/Rashed97/android_device_libcamera
Camera app changes coming soon!
Frameworks changes coming soon!
TO FIX VIDEO RECORDING AND PLAYBACK:
To fix video you will need the lib/libstagefright_soft_aacdec.so file from your ICS ROM. Setup a vendor pregenerated lib by adding that .so to your COMMONFOLDERNAME/proprietary/lib/libstagefright_soft_aacdec.so
TO INSTALL:
1. Follow the instructions in the READMEs in the repos
2. In your BoardConfigCommon.mk, delete the following lines IF THEY EXIST:
(Note: these are scattered all over the file, so look for them)
COMMON_GLOBAL_CFLAGS += -DICS_CAMERA_BLOB
TARGET_USE_OVERLAY := false
TARGET_HAVE_BYPASS := false
TARGET_USES_C2D_COMPOSITION := false
COMMON_GLOBAL_CFLAGS += -DREFRESH_RATE=60
3. Now add these lines to your BoardConfigCommon.mk
TARGET_DISABLE_ARM_PIE := true
TARGET_BOOTANIMATION_USE_RGB565 := true
TARGET_BOOTANIMATION_TEXTURE_CACHE := true
Note that the following 2 might not be needed based on your device, but most devices will need them
TARGET_NO_HW_VSYNC := true
COMMON_GLOBAL_CFLAGS += -DQCOM_NO_SECURE_PLAYBACK
4. Edit the files in the DEVICE/libcamera folder to suit your device
Again, thanks to nobodyAtall for getting this to work!!!
Click to expand...
Click to collapse
Read me only shows this message "This directory contains code for the Jelly Bean Camera HAL"
BTW where do we replace the files ? Where does BoardConfigCommon.mk file exist ?
Put the file in the /vendor/MANUFACTURER/DEVICE/proprietary/lib/
Add this line to your vendor-DEVICE-blobs.mk: (Note: Make sure it's the second to last line, not the last line)
vendor/COMPANY/DEVICE/proprietary/lib/libstagefright_soft_aacdec.so:system/lib/libstagefright_soft_aacdec.so \
Also here is an example of a common repo where you need to make all these changes:
https://github.com/lgics/cm_device_lge_msm7x27-common
And the vendor for the video:
https://github.com/lgics/cm_vendor_lge
http://review.cyanogenmod.com/#/c/22147/
This should fix recording issues
I just added it to all of CM since its needed a lot
Rashed97 said:
http://review.cyanogenmod.com/#/c/22147/
This should fix recording issues
I just added it to all of CM since its needed a lot
Click to expand...
Click to collapse
I use Xperia Ray running CM10 by FXP with FXP kernel. Should it work on it ? I can't find any file with extension .mk
take credit to erikcas for vide LQ
For camera on LG p690/e510 it doesnt work..we cant take picts... pano works :s
How to open the readme??
I get just " This directory contains code for the Jelly Bean Camera HAL"
Use proprietary files from GB ?
Sent from my GT-S5830 using xda app-developers app
Any way to use prprietary file from froyo 2.2.2 the only official available for a Huawei S7 tablet with snapdragon and adreno 200 ?...
Or other hack to make camera working.
Thank you.
Hello bright minds . I'm always using the perfect CM7, and as you know there is no nightlies(a CM7 build) since July. I was thinking about compiling/building CM7 from source for our Nexus S . I was doing it for Samsung Galaxy S, but for NS there is no guide.
Any idea please?
Thank you very much .
aladin6 said:
Hello bright minds . I'm always using the perfect CM7, and as you know there is no nightlies(a CM7 build) since July. I was thinking about compiling/building CM7 from source for our Nexus S . I was doing it for Samsung Galaxy S, but for NS there is no guide.
Any idea please?
Thank you very much .
Click to expand...
Click to collapse
There's very little difference in building though
https://github.com/CyanogenMod/android_device_samsung_crespo
polobunny said:
There's very little difference in building though
https://github.com/CyanogenMod/android_device_samsung_crespo
Click to expand...
Click to collapse
Thank you, the problem is how having a flashable .zip file with the recent changes made in GB :/?
aladin6 said:
Thank you, the problem is how having a flashable .zip file with the recent changes made in GB :/?
Click to expand...
Click to collapse
I'm not sure I understand... That's what building a rom is. Taking sources, compiling them and making them in a flashable format.
polobunny said:
I'm not sure I understand... That's what building a rom is. Taking sources, compiling them and making them in a flashable format.
Click to expand...
Click to collapse
Please look for example of what i used to do with building CM7 ROMs for my SGS1:
http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Compile_CyanogenMod_(Linux)
Hopefully you understood me .
There haven't been changes to GB since it came out? What is stopping you from using CM7.2?
063_XOBX said:
There haven't been changes to GB since it came out? What is stopping you from using CM7.2?
Click to expand...
Click to collapse
No, there has been many changes in CM7 since the latest nightly of 22th of July. I'm want to build a CM7 with the latest merged changes. Why CM7? Because simply is the perfect one in terms of stability, features, battery...
Bad screen, better adb screenshot
Hi, fellows.
I want to compile a CM7 for my Huawei u8186 Y100 (msm7227a, Adreno200 GPU). During the compiling process everything goes OK, but after flashing I've got something strange on my screen (see attached pictures). If I make a screenshot with ADB, the screen is not good either, but it's better than in reality... Maybe I put wrong configs in my mk files???
Here is a part of my BoardConfig, concerning my processor and graphics...
Code:
# CPU (msm7227a)
TARGET_BOARD_PLATFORM := msm7k
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv7-a-neon
TARGET_ARCH_VARIANT_FPU := neon
TARGET_BOARD_PLATFORM_GPU := qcom-adreno200
ARCH_ARM_HAVE_TLS_REGISTER := true
TARGET_GLOBAL_CFLAGS += -mfpu=neon -mfloat-abi=softfp
TARGET_GLOBAL_CPPFLAGS += -mfpu=neon -mfloat-abi=softfp
# Graphics
BOARD_EGL_CFG := device/huawei/u8185/config/lib/egl/egl.cfg
USE_OPENGL_RENDERER := true
BOARD_USES_QCOM_HARDWARE := true
COMMON_GLOBAL_CFLAGS += -DQCOM_HARDWARE
BOARD_ADRENO_DECIDE_TEXTURE_TARGET := true
# Qcom stuff
TARGET_USES_OVERLAY := false
TARGET_HAVE_BYPASS := false
TARGET_USES_C2D_COMPOSITION := false
TARGET_QCOM_HDMI_OUT := false
TARGET_FORCE_CPU_UPLOAD := true
TARGET_GRALLOC_USES_ASHMEM := true
WoW!!!! maximik1980 that's awesome! but, did you finish the CM7?
in this forum there are many people interested in a Cyanogenmod.
Please let us know any progress!
huaweiu8185.mi-foro.net
maximik1980 said:
Hi, fellows.
I want to compile a CM7 for my Huawei u8186 Y100 (msm7227a, Adreno200 GPU). During the compiling process everything goes OK, but after flashing I've got something strange on my screen (see attached pictures). If I make a screenshot with ADB, the screen is not good either, but it's better than in reality... Maybe I put wrong configs in my mk files???
Here is a part of my BoardConfig, concerning my processor and graphics...
Code:
# CPU (msm7227a)
TARGET_BOARD_PLATFORM := msm7k
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv7-a-neon
TARGET_ARCH_VARIANT_FPU := neon
TARGET_BOARD_PLATFORM_GPU := qcom-adreno200
ARCH_ARM_HAVE_TLS_REGISTER := true
TARGET_GLOBAL_CFLAGS += -mfpu=neon -mfloat-abi=softfp
TARGET_GLOBAL_CPPFLAGS += -mfpu=neon -mfloat-abi=softfp
# Graphics
BOARD_EGL_CFG := device/huawei/u8185/config/lib/egl/egl.cfg
USE_OPENGL_RENDERER := true
BOARD_USES_QCOM_HARDWARE := true
COMMON_GLOBAL_CFLAGS += -DQCOM_HARDWARE
BOARD_ADRENO_DECIDE_TEXTURE_TARGET := true
# Qcom stuff
TARGET_USES_OVERLAY := false
TARGET_HAVE_BYPASS := false
TARGET_USES_C2D_COMPOSITION := false
TARGET_QCOM_HDMI_OUT := false
TARGET_FORCE_CPU_UPLOAD := true
TARGET_GRALLOC_USES_ASHMEM := true
Click to expand...
Click to collapse
great job brother, well if I'm not mistaken, all this problem is based on screen size, or resolution of it, what happened to me wanting to install the same "CronMod-INT2EXT + _signed" and "ClockWorkRec "to give much more internal memory, was exactly the same as having a 240 x 320, compared with OT918a alcatel 320 x 480 that worked perfectly without errors :/
CM7 on 8185/8186: screen problem....
Hi everyone.
I'm still trying to run a CM7 on my Huawei u8186 (u8185). But I've got the same problems as I'd mentionned above.
Here is my log, maybe someone could see where the problem with my screen is...
I've got a very good picture through ADB, I can't undestand why it isn't good on my device.
Fixed...
https://github.com/maximik1980/device_u8185
https://github.com/maximik1980/vendor_u8185
But one needs much time to fix almost everything!
cant help you
Built 4.2.1 pure aosp for pyramid yet three drivers will not build for me.
copybit.msm8660 \
gralloc.msm8660 \
hwcomposer.msm8660 \
Click to expand...
Click to collapse
Board set to: Code:
Code:
BOARD_USES_QCOM_HARDWARE := true
Its in my msm8660.mk
and my libhardware is in place
Display folder renamed to display-legacy
Any help on this issue would surely be appreciated!
USING CM Display as well!
hello i search how i can fix that but google isn't my friend this time , i have this error any idea how fix that ?
build/core/java.mk:33: *** frameworks/support/v4: Invalid LOCAL_SDK_VERSION '17' Choices are: current 4 5 6 7 8 9 10 11 12 13 14 15 16. Arrêt.
thank you !
Hi!
I'm having the same issue trying to build p.a.c. 19.9.0.
It seems the aosp repos upgraded the platform sdk to 4.2.2 and some build scripts of aokp, cm and pa have not yet been fully made aware of this. I hope a sync tomorrow will make everything right.
Thank same problem here bajee has just send me a pm for confirm that so I just build aokp right now 4.2.2 is merged in her source
Envoyé depuis mon Nexus 4 avec Tapatalk
Confirmed
As of today I am having this issue trying to build Pac 19.9.0 for htc one v
4.2.2 isn't merged yet...
Envoyé depuis mon Nexus 4 avec Tapatalk
Any clues in fixing this ? Is this really just a merge problem ? Some say after a reinstall of the SDK the problem was gone ....
Dont want to mess up my system when i just need to wait
I'm still hanging at this problem, and repo sync doesn't fix it.
Any ideas guys?
I think that we just have to wait, till pacman repos are fixed .....
I had the same problem with two other repos, and now they are fine.
Just give the Pacman team some time to look @ it
you can trickly do following:
in frameworks/support/v4/Android.mk at begins Line 92
# A helper sub-library that makes direct use of JellyBean MR1 APIs.
include $(CLEAR_VARS)
LOCAL_MODULE := android-support-v4-jellybean-mr1
LOCAL_SDK_VERSION := 17
LOCAL_SRC_FILES := $(call all-java-files-under, jellybean-mr1)
include $(BUILD_STATIC_JAVA_LIBRARY)
Click to expand...
Click to collapse
to
# A helper sub-library that makes direct use of JellyBean MR1 APIs.
include $(CLEAR_VARS)
LOCAL_MODULE := android-support-v4-jellybean-mr1
LOCAL_SDK_VERSION := current
LOCAL_SRC_FILES := $(call all-java-files-under, jellybean-mr1)
include $(BUILD_STATIC_JAVA_LIBRARY)
Click to expand...
Click to collapse
and packages/apps/Deskclock/Android.mk from
LOCAL_PATH:= $(call my-dir)
include $(CLEAR_VARS)
LOCAL_MODULE_TAGS := optional
LOCAL_STATIC_JAVA_LIBRARIES := android-support-v13
LOCAL_STATIC_JAVA_LIBRARIES += android-support-v4
LOCAL_SRC_FILES := $(call all-java-files-under, src)
LOCAL_PACKAGE_NAME := DeskClock
LOCAL_OVERRIDES_PACKAGES := AlarmClock
LOCAL_SDK_VERSION := 17
LOCAL_PROGUARD_FLAG_FILES := proguard.flags
include $(BUILD_PACKAGE)
# Use the following include to make our test apk.
include $(call all-makefiles-under,$(LOCAL_PATH))
Click to expand...
Click to collapse
to
LOCAL_PATH:= $(call my-dir)
include $(CLEAR_VARS)
LOCAL_MODULE_TAGS := optional
LOCAL_STATIC_JAVA_LIBRARIES := android-support-v13
LOCAL_STATIC_JAVA_LIBRARIES += android-support-v4
LOCAL_SRC_FILES := $(call all-java-files-under, src)
LOCAL_PACKAGE_NAME := DeskClock
LOCAL_OVERRIDES_PACKAGES := AlarmClock
LOCAL_SDK_VERSION := current
LOCAL_PROGUARD_FLAG_FILES := proguard.flags
include $(BUILD_PACKAGE)
# Use the following include to make our test apk.
include $(call all-makefiles-under,$(LOCAL_PATH))
Click to expand...
Click to collapse
this is not the best, but its building fine now