THREAD CLOSED - Micromax A110

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.3.1 (JB), which is designed to increase performance and reliability over stock Android for your device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
THIS THREAD IS FOR DEVELOPMENT AND COMPILING OF CYANOGENMOD 10.2(4.3.1) FOR A110
REQUEST TO ALL DEVS TO HELP ME OUT IN THIS PROJECT
AS I M UNABLE TO BUILD CYANOGENMOD 10.2 FOR A110
AND GETTING ERRORS IN BUILDING
PLEASE DO NOT SPAM THE THREAD
XDA:DevDB Information
[ROM][4.3.1][UNOFFICIAL] CyanogenMod 10.2 | A110 |ALPHA #1 , a ROM for the Micromax A110
Contributors
[email protected]
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.4.x
ROM Firmware Required: MTK6577
Based On: CYANOGENMOD
Version Information
Status: Testing
Created 2013-11-03
Last Updated 2014-01-09

@stelios97
Code:
[email protected]:/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2$ make -j4build/core/main.mk:45: ********************************************************************************
build/core/main.mk:46: * You are using version 4.0 of make.
build/core/main.mk:47: * Android is tested to build with versions 3.81 and 3.82.
build/core/main.mk:48: * see https://source.android.com/source/download.html
build/core/main.mk:49: ********************************************************************************
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.3.1
CM_VERSION=10.2-20131103-UNOFFICIAL-a110
TARGET_PRODUCT=cm_a110
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.8.0-29-generic-x86_64-with-Ubuntu-12.04-precise
HOST_BUILD_TYPE=release
BUILD_ID=JLS36I
OUT_DIR=/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out
============================================
Checking build tools versions...
ls: cannot access external/bash/etc/: No such file or directory
build/core/Makefile:44: warning: overriding recipe for target '/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/system/lib/hw/audio.primary.default.so'
build/core/base_rules.mk:520: warning: ignoring old recipe for target '/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/system/lib/hw/audio.primary.default.so'
build/core/Makefile:44: warning: overriding recipe for target '/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/system/lib/hw/audio_policy.default.so'
build/core/base_rules.mk:520: warning: ignoring old recipe for target '/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/system/lib/hw/audio_policy.default.so'
build/core/Makefile:44: warning: overriding recipe for target '/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/system/lib/hw/audio_policy.stub.so'
build/core/base_rules.mk:520: warning: ignoring old recipe for target '/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/system/lib/hw/audio_policy.stub.so'
build/core/Makefile:44: warning: overriding recipe for target '/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/system/lib/hw/camera.default.so'
build/core/base_rules.mk:520: warning: ignoring old recipe for target '/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/system/lib/hw/camera.default.so'
build/core/Makefile:44: warning: overriding recipe for target '/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/system/lib/hw/gralloc.default.so'
build/core/base_rules.mk:520: warning: ignoring old recipe for target '/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/system/lib/hw/gralloc.default.so'
build/core/Makefile:44: warning: overriding recipe for target '/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/system/lib/hw/keystore.default.so'
build/core/base_rules.mk:520: warning: ignoring old recipe for target '/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/system/lib/hw/keystore.default.so'
build/core/Makefile:44: warning: overriding recipe for target '/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/system/lib/hw/local_time.default.so'
build/core/base_rules.mk:520: warning: ignoring old recipe for target '/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/system/lib/hw/local_time.default.so'
build/core/Makefile:44: warning: overriding recipe for target '/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/system/lib/hw/power.default.so'
build/core/base_rules.mk:520: warning: ignoring old recipe for target '/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/system/lib/hw/power.default.so'
build/core/Makefile:44: warning: overriding recipe for target '/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/system/etc/permissions/android.software.live_wallpaper.xml'
build/core/base_rules.mk:520: warning: ignoring old recipe for target '/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/system/etc/permissions/android.software.live_wallpaper.xml'
PRODUCT_COPY_FILES device/micromax/a110/prebuilt/usr/keylayout/AVRCP.kl:system/usr/keylayout/AVRCP.kl ignored.
PRODUCT_COPY_FILES device/micromax/a110/prebuilt/usr/keylayout/Generic.kl:system/usr/keylayout/Generic.kl ignored.
PRODUCT_COPY_FILES device/micromax/a110/prebuilt/usr/keylayout/qwerty.kl:system/usr/keylayout/qwerty.kl ignored.
PRODUCT_COPY_FILES device/micromax/a110/prebuilt/usr/keylayout/Vendor_045e_Product_028e.kl:system/usr/keylayout/Vendor_045e_Product_028e.kl ignored.
PRODUCT_COPY_FILES device/micromax/a110/prebuilt/usr/keylayout/Vendor_046d_Product_c216.kl:system/usr/keylayout/Vendor_046d_Product_c216.kl ignored.
PRODUCT_COPY_FILES device/micromax/a110/prebuilt/usr/keylayout/Vendor_046d_Product_c294.kl:system/usr/keylayout/Vendor_046d_Product_c294.kl ignored.
PRODUCT_COPY_FILES device/micromax/a110/prebuilt/usr/keylayout/Vendor_046d_Product_c299.kl:system/usr/keylayout/Vendor_046d_Product_c299.kl ignored.
PRODUCT_COPY_FILES device/micromax/a110/prebuilt/usr/keylayout/Vendor_046d_Product_c532.kl:system/usr/keylayout/Vendor_046d_Product_c532.kl ignored.
PRODUCT_COPY_FILES device/micromax/a110/prebuilt/usr/keylayout/Vendor_054c_Product_0268.kl:system/usr/keylayout/Vendor_054c_Product_0268.kl ignored.
PRODUCT_COPY_FILES device/micromax/a110/prebuilt/usr/keylayout/Vendor_05ac_Product_0239.kl:system/usr/keylayout/Vendor_05ac_Product_0239.kl ignored.
PRODUCT_COPY_FILES device/micromax/a110/prebuilt/usr/keylayout/Vendor_22b8_Product_093d.kl:system/usr/keylayout/Vendor_22b8_Product_093d.kl ignored.
PRODUCT_COPY_FILES frameworks/native/data/etc/android.software.sip.voip.xml:system/etc/permissions/android.software.sip.voip.xml ignored.
No private recovery resources for TARGET_DEVICE a110
build/core/tasks/kernel.mk:56: ***************************************************************
build/core/tasks/kernel.mk:57: * Using prebuilt kernel binary instead of source *
build/core/tasks/kernel.mk:58: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED *
build/core/tasks/kernel.mk:59: * Please configure your device to download the kernel *
build/core/tasks/kernel.mk:60: * source repository to kernel/micromax/a110
build/core/tasks/kernel.mk:61: * See http://wiki.cyanogenmod.org/w/Doc:_integrated_kernel_building
build/core/tasks/kernel.mk:62: * for more information *
build/core/tasks/kernel.mk:63: ***************************************************************
Can't open kernel/micromax/a110/arch/arm/configs/: No such file or directory at -e line 1.
Can't open kernel/micromax/a110/arch/arm/configs/: No such file or directory at -e line 1.
Export includes file: build/libs/host/Android.mk -- /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/host/linux-x86/obj/STATIC_LIBRARIES/libhost_intermediates/export_includes
host Java: jsr305lib (/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/host/common/obj/JAVA_LIBRARIES/jsr305lib_intermediates/classes)
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/host/linux-x86/obj/include/libexpat/expat.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/host/linux-x86/obj/include/libexpat/expat_external.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/obj/include/libexpat/expat.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/obj/include/libexpat/expat_external.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/host/linux-x86/obj/include/libpng/png.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/host/linux-x86/obj/include/libpng/pngconf.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/host/linux-x86/obj/include/libpng/pngusr.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/obj/include/libpng/png.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/obj/include/libpng/pngconf.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/obj/include/libpng/pngusr.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/host/linux-x86/obj/include/selinux/selinux.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/host/linux-x86/obj/include/selinux/label.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/host/linux-x86/obj/include/selinux/context.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/host/linux-x86/obj/include/selinux/avc.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/host/linux-x86/obj/include/selinux/android.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/obj/include/selinux/selinux.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/obj/include/selinux/label.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/obj/include/selinux/context.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/obj/include/selinux/avc.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/obj/include/selinux/android.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/obj/include/libsonivox/eas.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/obj/include/libsonivox/eas_types.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/obj/include/libsonivox/eas_reverb.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/obj/include/libsonivox/jet.h
Header: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/obj/include/libsonivox/ARM_synth_constants_gnu.inc
Import includes file: /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/host/linux-x86/obj/STATIC_LIBRARIES/libhost_intermediates/import_includes
Export includes file: build/tools/acp/Android.mk -- /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/host/linux-x86/obj/EXECUTABLES/acp_intermediates/export_includes
Notice file: external/guava/NOTICE -- /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/host/linux-x86/obj/NOTICE_FILES/src//framework/guavalib.jar.txt
host Java: antlr-runtime (/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/host/common/obj/JAVA_LIBRARIES/antlr-runtime_intermediates/classes)
Notice file: external/antlr/NOTICE -- /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/host/linux-x86/obj/NOTICE_FILES/src//framework/antlr-runtime.jar.txt
Notice file: external/doclava/NOTICE -- /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/host/linux-x86/obj/NOTICE_FILES/src//framework/doclava.jar.txt
target Java: core (/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/common/obj/JAVA_LIBRARIES/core_intermediates/classes)
Yacc: aidl <= frameworks/base/tools/aidl/aidl_language_y.y
prebuilts/misc/linux-x86/bison/bison -d -o /media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/host/linux-x86/obj/EXECUTABLES/aidl_intermediates/aidl_language_y.cpp frameworks/base/tools/aidl/aidl_language_y.y
/bin/bash: prebuilts/misc/linux-x86/bison/bison: No such file or directory
build/core/binary.mk:366: recipe for target '/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/host/linux-x86/obj/EXECUTABLES/aidl_intermediates/aidl_language_y.cpp' failed
make: *** [/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/host/linux-x86/obj/EXECUTABLES/aidl_intermediates/aidl_language_y.cpp] Error 127
make: *** Waiting for unfinished jobs....
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

need motorola kernalsources...can any 1 provide me...
I think this ay solve the error of compling

https://github.com/Bnaya/kernel_mtk6577 check here! I just want to help! I'm not spamming!
Sent from my A250 LegoIce™_Turbo using XDA Premium 4 mobile app

Jukel Rakesh said:
https://github.com/Bnaya/kernel_mtk6577 check here! I just want to help! I'm not spamming!
Sent from my A250 LegoIce™_Turbo using XDA Premium 4 mobile app
Click to expand...
Click to collapse
kk...thanks bro...and is it Motorola source..

http://sourceforge.net/projects/razrd.motorola/files/
Sent from my A250 LegoIce™_Turbo using XDA Premium 4 mobile app

@[email protected]... Bro it saying CM can be build on GNU Make 3.81
and you are using GNU Make 4.0.
so download GNU Make 3.81...... From here
ftp.gnu.org/gnu/make/

khan_frd2002 said:
@[email protected]... Bro it saying CM can be build on GNU Make 3.81
and you are using GNU Make 4.0.
so download GNU Make 3.81...... From here
ftp.gnu.org/gnu/make/
Click to expand...
Click to collapse
YUP BUDDY THE MAKE ERROR IS FIXED BUT THE MAIN ERROR IS WITH KERNAL IF U CAN FIX...
Code:
build/core/tasks/kernel.mk:56: ***************************************************************
build/core/tasks/kernel.mk:57: * Using prebuilt kernel binary instead of source *
build/core/tasks/kernel.mk:58: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED *
build/core/tasks/kernel.mk:59: * Please configure your device to download the kernel *
build/core/tasks/kernel.mk:60: * source repository to kernel/micromax/a110
build/core/tasks/kernel.mk:61: * See http://wiki.cyanogenmod.org/w/Doc:_integrated_kernel_building
build/core/tasks/kernel.mk:62: * for more information *
build/core/tasks/kernel.mk:63: ***************************************************************
Can't open kernel/micromax/a110/arch/arm/configs/: No such file or directory at -e line 1.
Can't open kernel/micromax/a110/arch/arm/configs/: No such file or directory at -e line 1.
make: *** No rule to make target `device/micromax/a110/kernel', needed by `/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/kernel'. Stop.

[email protected] said:
YUP BUDDY THE MAKE ERROR IS FIXED BUT THE MAIN ERROR IS WITH KERNAL IF U CAN FIX...
Code:
build/core/tasks/kernel.mk:56: ***************************************************************
build/core/tasks/kernel.mk:57: * Using prebuilt kernel binary instead of source *
build/core/tasks/kernel.mk:58: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED *
build/core/tasks/kernel.mk:59: * Please configure your device to download the kernel *
build/core/tasks/kernel.mk:60: * source repository to kernel/micromax/a110
build/core/tasks/kernel.mk:61: * See http://wiki.cyanogenmod.org/w/Doc:_integrated_kernel_building
build/core/tasks/kernel.mk:62: * for more information *
build/core/tasks/kernel.mk:63: ***************************************************************
Can't open kernel/micromax/a110/arch/arm/configs/: No such file or directory at -e line 1.
Can't open kernel/micromax/a110/arch/arm/configs/: No such file or directory at -e line 1.
make: *** No rule to make target `device/micromax/a110/kernel', needed by `/media/5e969efc-f4d6-4da4-98e2-2aaf3356518e/cm10.2/out/target/product/a110/kernel'. Stop.
Click to expand...
Click to collapse
Place the config file there I gave you.

andiroxu said:
Place the config file there I gave you.
Click to expand...
Click to collapse
where sholud i place...

[email protected] said:
where sholud i place...
Click to expand...
Click to collapse
I think bro you have to past the config here
kernel/micromax/a110/arch/arm/configs

khan_frd2002 said:
I think bro you have to past the config here
kernel/micromax/a110/arch/arm/configs
Click to expand...
Click to collapse
IN MY DIRECTORY THERE WAS NO kernel/micromax/a110/arch/arm/configs FOLDER....I MADE IT N THEN PASTED .CONFIG FILE THERE BUT NO LUCK... I THINK ONLY @andiroxu can answer this

@fia@z I've heard that 3.4.6+ kernel supports 4.3.x jb is it true? Then you could use @andiroxu s new kernel right?
Sent from my Micromax A110 using XDA Premium 4 mobile app

[email protected] said:
IN MY DIRECTORY THERE WAS NO kernel/micromax/a110/arch/arm/configs FOLDER....I MADE IT N THEN PASTED .CONFIG FILE THERE BUT NO LUCK... I THINK ONLY @andiroxu can answer this
Click to expand...
Click to collapse
Paste it in root directory only. If you have mediatek directory then you can post it in mediatek->config->mt6577->autoconfig->kconfig and rename it to platform and then make it.
If you again fail to do so then do the following:
make menuconfig
Now you will get graphical menu to choose configuration from. Set what configs you want. I will suggest to look my config file side-by-side by seting those configuartion because setting wrong config or config not supported on mediatek will cause bootloop.

andiroxu said:
Paste it in root directory only. If you have mediatek directory then you can post it in mediatek->config->mt6577->autoconfig->kconfig and rename it to platform and then make it.
If you again fail to do so then do the following:
make menuconfig
Now you will get graphical menu to choose configuration from. Set what configs you want. I will suggest to look my config file side-by-side by seting those configuartion because setting wrong config or config not supported on mediatek will cause bootloop.
Click to expand...
Click to collapse
:crying: BUDDY IN MY DIRECTORY THERE WAS NO mediatek->config->mt6577->autoconfig->kconfig SO I MADE IT AND PASTED YOUR CONG=FIG.TXT THERE N RENAMED IT TO PLATFORM BUT THE SAME ERROR
THEN TRIED YOUR SECOND METHOD....MOVED TO DIRECTORY N WROTE MAKE MENUCONFIG THEN THE PROCEESED STARED LIKE THE ABOVE AND AT THE END
Code:
make: *** No rule to make target `menuconfig'. Stop.
EDITEDBUDDY FINALLY RECTIFIED THIS ERROR...JUST PASTED THE BOOT.IMG IN DIRECTORY AND CHANGED THE PATH TO IT IN KERNAL.MK AND N GOING FURTHER...BUT NOW ALSO SOME ERRORS...BUT I WILL RECTIFY IT

Make errors are due to absence of Makefile. Check the path in the error and find whether the Makefile is there or not.
Sent from my GT-I9500 using xda app-developers app

andiroxu said:
Make errors are due to absence of Makefile. Check the path in the error and find whether the Makefile is there or not.
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
BUDDY THERE IS NO MAKE FILR IN ANY DIRECTORY...THERE IS ONLY ONE MAKE FILE IN MAIN DIRECTORY....AND IF THE ERROR COMES FOR EG IN{MAKE*** OUT/TARGER/ETC NOT FOUND
I GO TO THAT FOLDER AND MAKE A FILE THERE WITH THE FILE NAME SHOWN IN ERROR AND DO A MAKE AGAIN...
I THIS WAY I M TRYING AND AFTER EVERY STEP IT GOES FUTHER
BUT BY MISTAKE YESTERDAY I DID MAKECLEAN AND THE WHOLE FILES WHERE DELETED
NOW WORKING ON IT AGAIN

[email protected] said:
:crying: BUDDY IN MY DIRECTORY THERE WAS NO mediatek->config->mt6577->autoconfig->kconfig SO I MADE IT AND PASTED YOUR CONG=FIG.TXT THERE N RENAMED IT TO PLATFORM BUT THE SAME ERROR
THEN TRIED YOUR SECOND METHOD....MOVED TO DIRECTORY N WROTE MAKE MENUCONFIG THEN THE PROCEESED STARED LIKE THE ABOVE AND AT THE END
Code:
make: *** No rule to make target `menuconfig'. Stop.
EDITEDBUDDY FINALLY RECTIFIED THIS ERROR...JUST PASTED THE BOOT.IMG IN DIRECTORY AND CHANGED THE PATH TO IT IN KERNAL.MK AND N GOING FURTHER...BUT NOW ALSO SOME ERRORS...BUT I WILL RECTIFY IT
Click to expand...
Click to collapse
Don't use make clean until you want everything compiled to be clean.
Sent from my GT-I9500 using xda app-developers app

i really have no idea about compiling cm...as there you all shifted from cm10.1 to cm10.2...i came across cm11
repo init -u git:// github.com/CyanogenMod/android.git -b cm-11.0

premsagar_rs1 said:
i really have no idea about compiling cm...as there you all shifted from cm10.1 to cm10.2...i came across cm11
repo init -u git:// github.com/CyanogenMod/android.git -b cm-11.0
Click to expand...
Click to collapse
How funny u r :
Dear member our devs r working hardly for get CM 10.1 or CM 10.2
he will do his best work ever ..
N CM company say that when all high n device not get CM 10.2 so they r not build CM11 n u know that
Now there is no rom which is base on CM ..in our A110 fourm
So plz dont spamming in this thread bcz very impo thread for me n our A110 community..
Sry devs for posting here

Related

[DEV] Adding your ROM to ROM Manager

It's easy, it's free. And here's how you do it!
You will need to create two simple JavaScript files:
A file that describes your ROMs that you send to me.
A file that you host that lists your ROMs, so you can update your ROM Manager section.
First, your developer/ROM description file:
Code:
{
// This is what name you want your ROMs to show up under.
developer: "CyanogenMod",
// Your id. This should have no spaces or other funny characters.
// This would ideally be your Github id, so when you send me your manifest
// I can verify who you are. But it can be anything really.
id: "cyanogen",
// The display summary. Two lines max.
summary: "Mods and bacon for Dream, Sapphire, Droid, and Nexus One",
// The location of the developer's manifest.
manifest: "http://gh-pages.clockworkmod.com/ROMManagerManifest/cyanogenmod.js",
// The list of devices that this developer's ROMs support.
// If you don't support a device, just don't list it!
roms:
{
supersonic: true,
sholes: true,
passion: true
}
}
Send me that file! [email protected]
Link to developer sample: http://gh-pages.clockworkmod.com/ROMManagerManifest/samples/developer.js
And now, create your ROM list file:
Code:
{
// The version of the manifest, so ROM Manager knows how to load it
version: 1,
// The homepage for your ROM, if you have one.
homepage: "http://www.cyanogenmod.com/",
// The donate link for yuor ROM, if you have one.
donate: "https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=3283920",
// Your list of ROMs
roms:
[
{
// Display name of the rom
name: "CyanogenMod 5.0.5",
// Display summary of the rom
summary: "Stable",
// Device that this rom runs on
device: "sholes",
// This is the download URL of your ROM.
// These URLs should have unique filenames per version!
// Ie, don't use a zip with the same name
// as that of a previous version with a new version.
// Otherwise ROM Manager will continue using the
// old cached zip on the SD card.
// This must be a direct download,
// and not a Mediafire type link.
url: "http://www.droidaftermarket.com/koush/motorola/sholes/cyanogen_sholes-ota-eng.koush_5.0.5.zip"
},
// Antother, older ROM!
{
name: "CyanogenMod 5.0.4",
summary: "Stable",
device: "sholes",
url: "http://www.droidaftermarket.com/koush/motorola/sholes/cyanogen_sholes-ota-eng.koush_5.0.4.zip"
}
]
}
Link to manifest sample: http://gh-pages.clockworkmod.com/ROMManagerManifest/samples/simplemanifest.js
And you're done!
If you're a pro dev, you can even create a ROM customizer. But I won't get into that here
Follow this link for more information: http://www.koushikdutta.com/2010/03/rom-manager-and-third-party-roms.html
Could the stock ones be added?
Nice... added it to the sticky.
very nice, thx!
I hope more devs start doing this. It's such a handy tool for users.
will this be open source and be used on another server? So we don't have to send you the file to be listed.
puertoblack2003 said:
will this be open source and be used on another server? So we don't have to send you the file to be listed.
Click to expand...
Click to collapse
the manifest.js is hosted on our own server. i have mine hosted on my server and it seems to work great!
would love to see more DEV's use this tool [email protected]
I love blueeeeee
I agree...so handy
Sent from my PC36100 using XDA App

[SCRIPT][MULTILANG] Swordrune10's Android Kitchen

I myself use scripts (that i wrote of course) to build so i wanted to share them with you guys!
spent a few days rearranging, and on some completely redoing, my scripts to come up with this easy to use, dare i say pretty if your into ascii, kitchen.
Features
Setup, update, build, and fix
Update kitchen app through script
Build enviroment installation (64 bit only) currently supports Ubuntu 10.04 - 14.04, with general support for Fedora, Debian, Linux Mint, Arch Linux, and with semi-general support for Mac OS X
Able to build Android Open Kang Project, Android Open Source Project, Carbon, Cyanogenmod 10.2, Cyanogenmod 11, Evervolv, omnirom, PAC-man, and ParanoidAndroid
Designed to build for nexus devices, but supports other devices
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the recommended file directory is as follows:
Code:
android/swordkitchen
android/swordkitchen/.scripts
# Everything below is made by the kitchen
android/repos/[all the repositorys u sync]
android/builds/[the roms that are made]
Instructions:
Boot into a 64-bit Unix System: supports Ubuntu 10.04 - 13.10, with general support for Fedora, Debian, Linux Mint, Arch Linux
Download and install using the script linked below
Either click swordkitchen.sh which will open in terminal or open terminal, change directory to the installed folder, and type in ./swordkitchen.sh
Inside Kitchen now!
Go to setup kitchen and run 1 (installation of repo) and 2 (setup build enviroment)
Initialize the desired repo(s) and sync when it asks if you want to
Go back, and go to the build menu, select what u want to build and omg! ur building a rom!! =O
Optional:
Tweak the romeditor or gitpuller as u like it.. ur changes in these files reflect towards ur builds
You can just use repo to grab it if you want..
Code:
Stable Version:
repo init -u http://github.com/TeamKeyblade/kitchen_manifest.git -b stable
Developer Version ( the one i push to when working on kitchen ):
repo init -u http://github.com/TeamKeyblade/kitchen_manifest.git -b master
these can work in the ~/bin folder, if anyone puts it anywhere not in your home folder please let me know and ill see about making it work perfectly from there. Below should be in ur path on login if you decide to put it in ~/bin
Code:
$HOME/bin/kitchen:$HOME/bin/kitchen/build:$HOME/bin/kitchen/update:$HOME/bin/kitchen/menu:$HOME/bin/kitchen/config
Languages:
English (Completed)
Russian (Completed)
German (Completed)
Dutch (Completed)
Spanish (Incomplete)
Brazilian Portuguese (Incomplete)
This kitchen is totally open sourced!
Please use Kitchen to update, script below is for installation
Older tarballs of the kitchen can be found here
Kitchen Installer: SourceForge link for swordkitchen_installer.bash
Join me on freenode channel #Swordrune10Kitchen
Changelog:
4/27/14
retardedbabelfish: fixed language not saving issue
Add Ubuntu 14.04 also updated translation files
4/21/14
Had a few users having issues with selecting a language, and this bugfix should squash the issue
issue reported by @flyboy1100
Fix retardedbabelfish missing language file
2/5/14
Added Dutch Translations
2/4/14
German translations is now complete!
1/26/14
Added Russian, was translated, Marked as active
special thanks to App Translators thread and @gaich for making this happen
1/24/14
my translation project is finished! currently the translation framework is done, but the translation files are a bit lacking.. if any of u want to help please let me know! our languages which have been started is spanish, german, and brazilian portuguese
1/14/14
I am now starting a project for this kitchen to be translated to multiple languages, for right now i am adding spanish and french using google translate.. as soon as the framework is situated i will invite anyone to help me with native translations.. also if you want to see a language added please ask me to include it and help translate the language!
Update changes in repos: update omni vendorsetup naming scheme, Update pacman's manifest location, and Update ParanoidAndroid's source location and update them to kitkat as well
Update specific build commands per repo
Add freenode channel info to error messages
Add Copyright info under apache license 2
move base scripts to a folder named utility
EDIT: Decided to initially add also german, italian, japanese, and korean as well.. this came about because my wife just grabbed a copy of Pokemon Y and that was the language choices
1/2/14
hey guys, been busy working on this and other stuff to actually post.. i have been working on this kitchen, let me tell u a summary of whats been going on
now possible to run auto builder from menu
update manifest always if manifest already exists
Use signapk.jar built for aosp during instead of prebuilt
use repodefiner for repo variables
specify manifest xml file/change cm10.2 to stable branch
fixed double zip variable, causing the build for cm to be double in size
mirror how cm is made from hudson
If user is root, make files read and write for everyone
lots of bug fixing and updating as well
11/5/13
Added Cyanogenmod 11
Removed Cyanogenmod 9 & 10, also Rooted & Busyboxed AOSP
11/3/13
add aosp 4.4 as a seperate repo, will take place of 4.3 later
Add Nexus 5
Fix AOSP/RAOSP tweaks after building
Before building, mute error if cant find vendorsetup.sh in vendor folder
also will be adding new tarball asap!
10/17/13
Add Ubuntu 13.10 setup
new tarball will be out on sourceforge later today
10/14/13
Added omnirom/Removed Codename Android
scriptmakir: clean up gitpuller and make it up to date
10/13/13
Updated swordkitchen_installer to now have .bash at the end of the name to signify it runs in bash, also made it so it will run in bash regardless of anything.. even if you do "sh swordkitchen_installer.bash"
scriptmakir: remove duplicate device/sample for cm-10.2
10/11/13
I now have a sourceforge project for the kitchen and i also now have an installer script instead of just posting tarballs.. tarballs will still be available and will be made every so often on sourceforge, i will be posting the changelog here still so stick around!
Updated repo binary location for both reposync and macosxinit
10/10/13
Update aosp/raosp to 4.3.1 release 1
Added Ccache to building, not mandatory
Change back to cyanogenmod for tilapia
Finally stop the script if zip isnt present, this makes the end alot cleaner when it errors out
PACman and ParanoidAndroid now builds correctly
Fixed building, forgot i changed the jobs variable in headerfile
Full Changelog
Good work. Just wondering, what is the benefit of this script over for instance this compiler tool: http://www.omgubuntu.co.uk/2012/05/gui-cyanogenmod-compiler-tool-for-ubuntu/ ?
mbroeders said:
Good work. Just wondering, what is the benefit of this script over for instance this compiler tool: http://www.omgubuntu.co.uk/2012/05/gui-cyanogenmod-compiler-tool-for-ubuntu/ ?
Click to expand...
Click to collapse
honestly? that tool is probably a lot better.. I made this as a learning experience
EDIT: actually now that i think about it mine is kinda better on the fact that my updates itself (as in the actual "program"), u know exactly whats in it since its all scripts, and im gonna put into it ability to modify the rom before its built
Sent from my Galaxy Nexus using XDA
Changelog:
5/22/12
Added build other functionality, you can now build any cm or aosp device
Changelog:
5/22/12 8pm
Added gitpuller, a symbolic linked file that u can edit to add git pull's to modify the repos
Might come in handy
Sent from my Galaxy Nexus using Tapatalk 2
Changelog:
5/23/12
Added Rooted & Busyboxed AOSP
nice work will try
Changelog:
5/24/12
Added ability to build toroplus thru Rooted & Busyboxed AOSP
Fixed build menu looping, making it having to hit exit one to many times on the main menu
Changelog:
5/25/12
fix problem with using
Code:
sh "Swordrune10's Kitchen.sh"
code is a bit more simplified
Changelog:
5/26/12
added fix kitchen menu
new gitpuller, same stuff just not part of the updater anymore - if you had gitpuller before, please remove the old one
Changelog:
5/26/12 5pm
fixed an error at creating gitpuller, please trash gitpuller for it to fix (last time i will mess with gitpuller, honest!)
Changelog:
5/26/12 8pm
Added romeditor, allows u to edit rom manager esque details like developer id and modversion before build, romeditor is like gitpuller and is shown to u in the directory
Is this something that a newbie could use? I want to get into building a rom for myself, it this easy to use for that?
Sent from my Sprint Galaxy Nexus CDMA using XDA
pastert33 said:
Is this something that a newbie could use? I want to get into building a rom for myself, it this easy to use for that?
Sent from my Sprint Galaxy Nexus CDMA using XDA
Click to expand...
Click to collapse
yes, whole reason I made this is for new people.. right now its missing setting up the build environment, but that's next on my plate.. I'll probably finish that tomorrow
Sent from my Galaxy Nexus using XDA
How i can flash that ?
Sent from my Galaxy Nexus using xda premium
leos0000 said:
How i can flash that ?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
how do u mean?
Sent from my Galaxy Nexus using XDA
swordrune10 said:
how do u mean?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
This is kitchen for what.. cuz im little jnderstand sorry bro
Sent from my Galaxy Nexus using xda premium
Changelog:
5/27/12
Added build enviroments installation
Menus more consistent

[ROM/DEVELOPMENT/DISCUSSION] MIUI For i9500 [ALPHA/PATCHROM]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I started patching touchwiz rom with miui for more stable rom..And i will join miui contest with some chance
I will post all things here. It's still Alpha.
MIUI CONTEST CALENDAR
EDIT : TIME EXTENDED !!!
Port:Aug.1—Sep.15, 2013* Contestants port MIUI ROM in compliance with the rules
Submit:Sep.16—Oct.31, 2013* Contestants submit ROMs following the procedure
Distribute:Nov.1—Nov.30, 2013* Contestants distribute their ROMs for downloading, and wait for the final count
Final Count:Dec. 1—Dec.5, 2013* Contestants will be ranked by the amount of their ROMs’ active users
Winner Announced:Dec.6, 2013
MIUI PATCH ROM PROGRESS FOR I9500
MIUI PATCHROM TOP OF CYANOGENMOD BASE (4.3 / CM10.2)
-Framework-res.apk Patching - Done
-framework-miui-res.apk for i9500 - Done
-framework.jar Patching -WAIT
-framework2.jar Patching - WAIT
-services.jar Patching - Done
-android.policy.jar Patching - Done
Conflicts Fixed -- NO
BOOTING - NO !
---------------------------------
MIUI PATCHROM TOP OF TOUCHWIZ BASE
-Framework-res.apk Patching - Done
-framework-miui-res.apk for i9500 - Done
-framework.jar Patching - ALMOST IMPOSSIBLE
-framework2.jar Patching - Done.
-services.jar Patching - Done.
-android.policy.jar Patching - Done.
Conflicts Fixed -- HALF
BOOTING - NO !
---------------------------------
31.08.2013 11.07 : I'm updating miui repos.maybe that caused services.jar problem
31.08.2013 11:53 : Services.jar Problem Fixed
31.08.2013 12:11 : android.policy.jar patching problems : "[14400,4] All register args must fit in 4 bits"
31.08.2013 12:24 : looks like i fixed android.policy.jar re-compiled.
31.08.2013 12.35 : looks like patchrom f*ked all framework.jar .so it shows lot of multiple definitions more than 20
31.08.2013 12.40 : some fixes on framework.jar
31.08.2013 12.56 : IStatusBarService$stub.smali still has problems. i fixed some conflicts.
31.08.2013 13:39 : Some more fixes on statusbarservice.
31.08.2013 16:40 : Passing framework.jar and will test other all things.. except framework.jar for now
31.08.2013 17.07 : framework2.jar patched
31.08.2013 17:36 : MIUI Patchrom created without framework.jar..So i will try with samsung's framework.jar
31.08.2013 17:38 : Creating MIUI ZIP File with samsung's framework.jar .. MIUI Developer alpha 1
31.08.2013 17:58 : MIUI Developer Alpha 1 - Causes bootloop..
31.08.2013 18:03 : Going back to framework.jar patching
31.08.2013 18:51 : Re-patching framework.jar
31.08.2013 18:54 : Added ADB Service to build.prop
31.08.2013 18:56 : While Touchwiz based MIUI repatching, i'm checking cm based patch
31.08.2013 19:45 : Framework.jar problems still continuing.. trying fix
31.08.2013 20:29 : Understanding Framework structure. removing duplicate methods
31.08.2013 20.45 : sswitch_14 duplicate fixed.
31.08.2013 20.51 : IStatusBar$Stub sswitch_10 duplicate fixed.
31.08.2013 20.58 : catch_miui_0 not defined. conflict problem ignoring
31.08.2013 21.17 : method index is too large. separating frameworks
31.08.2013 21.58 : Calculating Method index.
31.08.2013 22.07 : WTF ! framework.jar ok but framework2.jar is bigger than framework.jar so method index is too large. again
31.08.2013 22.10 : Creating framework3.jar ...kernel needs bootclasspath change
31.08.2013 22:23 : Probably all problems fixed but maybe i placed wrong some frameworks i should test
31.08.2013 22:35 : System Folder is ready hope it works
31.08.2013 22:37 : Ramdisk ready with new bootclasspath added framework3.jar
31.08.2013 22:42 : ROM ZIP Creating..
31.08.2013 23:00 : ROM ZIP READY. Tested but bootlooping. enabling adb for bug smashing MIUI Developer Alpha 2
31.08.2013 23:23 : Wrong framework3 creation.... trying to fix
31.08.2013 23:36 : Re-created framework.jar , framework2.jar and framework3.jar
31.08.2013 23:38 : MIUI Developer Alpha 3 -- ZIP Creating. Lets test
31.08.2013 23:55 :
Code:
E/dalvikvm( 9170): Requested: Landroid/os/SystemClock;._setCurrentTimeMillis:(J)Z
E/JNIHelp ( 9170): RegisterNatives failed for 'android/os/SystemClock', aborting
F/libc ( 9170): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thr....
bootloop and this
01.09.2013 00.06 : I forgot to wipe data/cache remembering @Grarak 's suggestions about 1 month ago LOL
01.09.2013 00.19 : Searching for a fix.. where is that wrong code?!??
01.09.2013 00:26 :
Code:
###android/os/SystemClock.smali
.method public static native setCurrentTimeMillis(J)Z
.end method
its exists. what is problem ?!?
01.09.2013 01:43 : Changing base to 4.2mtk ... for testing.. hope this one works
01.09.2013 01:47 : Framework-res.apk completed on 42mtk
01.09.2013 01.48 : framework-miui-res.apk completed on 42mtk
01.09.2013 01:49 : services.jar problem fixes
01.09.2013 02:02 : services.jar problem fixed but i think i did something different.
01.09.2013 02:18 : android.policy.jar failed. i copied 4.1_2 PATCHED ONE.. mtk didnt patch correctly
01.09.2013 02:26 : framework.jar fixed... but i need sleep and time for 4.2mtk i'm happy because most important one looks patched gr8
01.09.2013 02:32 : framework.jar - method index is too large. lets separate tomorrow
01.09.2013 12:56 : Good morning lets start mtk port again
01.09.2013 13:48 : Mtk port finished zip created.
01.09.2013 18:25 : mtk base screwed up all things.
01.09.2013 18:26 : going back to jellybean patchrom
01.09.2013 22:25 : conflicts fixing on framework.jar
01.09.2013 22:34 : *** 48,53 ****___CREATED SSWITCH_17 BECAUSE OF CONFLICT DOGA OZKARACAABATLIOGLU _PATCH SEEMS OK
01.09.2013 22:38 : :cond_miui_1 NOT DEFINED FIXED DOGA OZKARACAABATLIOGLU _ PATCH_OK -CONFLICT FIXED -ResolverActivity$ResolveListAdapter.smali.rej
02.09.2013 01:38 : bootloop problem found .wrong framework patching because of me.. trying to fix bad framework jars
02.09.2013 01:51 : Completely bootclasspath and jar structure problem.. i couldnt re-pack dex to jar file correctly..
02.09.2013 01:52 : if i can patch these jars correctly, miui should be boot
02.09.2013 11:50 : Good Morning . and i'm deleting some samsung things in framework.jar i cannot separate framework ...
02.09.2013 14:57 : Framework.jar Patching COMPLETELY FAILED... MIUI PATCHROM THING SUCKZ.. !!! -- WHY MIUI WHY ?!?! PLEASE RELEASE SOURCE CODES..
02.09.2013 15.06 : STARTING FROM BEGINNING WITH CYANOGENMOD BASE
02.09.2013 17.03 : Main things patched
02.09.2013 23:00 : ALL PATCHROM THINGS CANCELLED BECAUSE OF WRONG PATCHING FOR I9500 - SO I WILL PORT WITHOUT PATCHROM. I WILL PORT FROM ANOTHER DEVICE
02.09.2013 23:02 :
02.09.2013 23:14 : Port Completed got that log
Code:
D/dalvikvm( 5396): Unable to stat classpath element '/system/framework/voip-comm
on.jar'
D/dalvikvm( 5396): Trying to load lib libjavacore.so 0x0
D/dalvikvm( 5396): Added shared lib libjavacore.so 0x0
E/dalvikvm( 5396): ERROR: couldn't find native method
E/dalvikvm( 5396): Requested: Lorg/apache/harmony/xnet/provider/jsse/NativeCrypt
o;.EVP_PKEY_new_RSA_SECPkcs11:()I
E/JNIHelp ( 5396): RegisterNatives failed for 'org/apache/harmony/xnet/provider/
jsse/NativeCrypto', aborting
Probably fixable i didnt get any framework.jar problems i will change ril things in framework.jar now.
03.09.2013 00:26 : i have to go school tomorrow.i need sleep i wont work today much on miui but after adding missing methods .probably miui will boot good night xda community :highfive:
03.09.2013 13:56 : Started again and found missing method in core.jar.
03.09.2013 19:12 : looks like i should change androidruntime .... so it will be more stable..i'm trying now
07.10.2013 08:32 : I'm back for compiling cm10.1.3(android 4.2.2) and miui released new patchrom for 4.2.2 and maybe we have some chance now. and porting time extended.
Good luck !
You have all our support and wishes !
Best Of Luck!
:fingers-crossed:
Hi Doga Buddy, :good::good::good:
If you wish, I can try to help you to find solution of issues.
For that I have to setup initial development env and setup tools and also have to get the development that you did so far.
Basically need to learn initial things from you to catch up with your development.
And hopefully I will contribute a little in your MIUI Porting...
Thanks
Amazing! I will install it! Won't mind voiding my warranty for MIUI
Sent from my GT-I9500 using xda premium
Keep up the good work
Sent from my GT-I9500 using xda app-developers app
maybe some MIUI porters can help u
@Alex93917 @incaner @bmarko82
Keep up man good work we support you works as 9500 owners
Sent from my GT-I9500 using XDA Premium 4 mobile app
http://en.miui.com/forum.php?mod=at...yNWQ0NWJ8MTM3Nzk2MjQ1N3wxMjE2MDI2ODh8NDE3OQ==
find some patchrom guide i dont know if this will help but i hope so
@doga.ozkaraca
can't wait for MIUI!!!
gdonanthony said:
http://en.miui.com/forum.php?mod=at...yNWQ0NWJ8MTM3Nzk2MjQ1N3wxMjE2MDI2ODh8NDE3OQ==
find some patchrom guide i dont know if this will help but i hope so
@doga.ozkaraca
Click to expand...
Click to collapse
i already have that thanks anyway :good: (i cant press anymore thanks button today )
hey doka, which base did you use? Jellybean or jellybean42-mtk?
Rahulrulez said:
hey doka, which base did you use? Jellybean or jellybean42-mtk?
Click to expand...
Click to collapse
I think 42-mtk
Jellybean is for 4.1
Sent from my GT-I9500 using xda app-developers app
Grarak said:
I think 42-mtk
Jellybean is for 4.1
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
Rahulrulez said:
hey doka, which base did you use? Jellybean or jellybean42-mtk?
Click to expand...
Click to collapse
i'm using jellybean .because 42mtk has different dependencies also using mediatek driver things which i dont understand. jellybean repo has great now.its patching good
EDIT : and @Rahulrulez its doga not doka
Good luck brooooo
Cant wait your Miui port for i9500...
thankssss
Doga please use 42-mtk
with jellybean branch you cannot get it to work.
If you need dualboot to keep your current rom, contact me I can give you patches
Grarak said:
Doga please use 42-mtk
with jellybean branch you cannot get it to work.
If you need dualboot to keep your current rom, contact me I can give you patches
Click to expand...
Click to collapse
dualboot for cm slim and carbon ??
do i need include dualboot feature in all rom file .. and i have an idea grarak maybe it can help you i dont know . i realized now you can create patch about 10 kb after installing that cm roms . user can run that 10 kb zip file and script can movesystem folder to data/somefolder and then it can format system folder for example that update script may save us from include update-script in whole rom. just a suggestion
and mtk one doesnt decompile all things correctly but i will try i will change some miui codes
doga.ozkaraca said:
dualboot for cm slim and carbon ??
do i need include dualboot feature in all rom file .. and i have an idea grarak maybe it can help you i dont know . i realized now you can create patch about 10 kb after installing that cm roms . user can run that 10 kb zip file and script can movesystem folder to data/somefolder and then it can format system folder for example that update script may save us from include update-script in whole rom. just a suggestion
and mtk one doesnt decompile all things correctly but i will try i will change some miui codes
Click to expand...
Click to collapse
No I was think about dualboot your current rom and your experimental miui rom, so you can keep your daily use rom without to make backups.
We have recovery experts on board they will modify there recoveries to make it dual compatible with romswitcher. Anyway thanks for the idea.
Grarak said:
No I was think about dualboot your current rom and your experimental miui rom, so you can keep your daily use rom without to make backups.
We have recovery experts on board they will modify there recoveries to make it dual compatible with romswitcher. Anyway thanks for the idea.
Click to expand...
Click to collapse
after booting miui it can be awesome but i must boot miui first and then i can use your dualboot for fixing bugs :good: :highfive:
also i started using mtk 42 as base. hope that one works
wooowww !! im excited reading this improvements...
how i wish i can develop too
Wait are you gonna release this rom on October 1st or once done then you release it?

[s2vep][BLN][AOSP] Test Kernel [Leds fix]

This is pure kernel used by Aosp ROMS, plus BLN, plus a leds fix.
Won't work on stock roms.
No need for ROM with patch for leds anymore.
Works on me. Touch lights to turn on only when they are touched.
This may help to official roms like pacman that don't use the patch for leds.
This is unofficial cause the way I read the buttons timeout is really weird, and I don't know if it will work on other androids than 4.4.
If anyone know a safe way to read from kernel the button timeout, say so to use this for building roms!
BLN is enabled by default and it works thanks to cooldevelopement's changes for moshkernel.
https://github.com/dimimeim/BLN-and...mmit/c4da6fb101776c9f9d55ad0fd97b8a01da01c39c
v2:
fix the ability to turn off leds from settings.
beastaki23 said:
This is the our s2vep kernel used by Aosp ROMS, plus BLN, plus a test for leds fix.
Won't work on stock roms.
No need for ROM with patch for leds anymore.
Works on me. Touch lights to turn on only when they are touched.
This may help to official roms like pacman that don't use the patch for leds.
This is for test, cause the way I read the buttons timeout is really weird, and I don't know if it will work on other androids than 4.4.
If anyone know a safe way to read from kernel the button timeout, say so to use this for building roms!
BLN is enabled by default and it works thanks to cooldevelopement's changes for moshkernel.
https://github.com/dimimeim/BLN-and...mmit/c4da6fb101776c9f9d55ad0fd97b8a01da01c39c
Click to expand...
Click to collapse
Good work man
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app
Will it work on gt -i9105 ?
kkaranjkar said:
Will it work on gt -i9105 ?
Click to expand...
Click to collapse
Don't think so, but if it's stable enough I can built for i9105 too.
Sent from my GT-I9105P using XDA Premium 4 mobile app
Ok... Thanx in advance [emoji4]
I think you should better add a sysfs interface for the timeout and write the timeout to the sysfs file from the rom, probably liblights.
The kernel should be the base to run any system and not depend on a system.
CoolDevelopment said:
I think you should better add a sysfs interface for the timeout and write the timeout to the sysfs file from the rom, probably liblights.
The kernel should be the base to run any system and not depend on a system.
Click to expand...
Click to collapse
Or create a symlink to the timeout sysfs file
CoolDevelopment said:
I think you should better add a sysfs interface for the timeout and write the timeout to the sysfs file from the rom, probably liblights.
The kernel should be the base to run any system and not depend on a system.
Click to expand...
Click to collapse
I think that this also needs a patch to send the timeout to liblights.
From default it calls only setbrightness(255) leading to jni:
Code:
public void setBrightness(int brightness) {
setBrightness(brightness, BRIGHTNESS_MODE_USER);
}
and
public void setBrightness(int brightness, int brightnessMode) {
synchronized (this) {
int color = brightness & 0x000000ff;
color = 0xff000000 | (color << 16) | (color << 8) | color;
setLightLocked(color, LIGHT_FLASH_NONE, 0, 0, brightnessMode);
}
}
without sending timeout.
If we could read it from liblights somehow.
beastaki23 said:
I think that this also needs a patch to send the timeout to liblights.
From default it calls only setbrightness(255) leading to jni:
Code:
public void setBrightness(int brightness) {
setBrightness(brightness, BRIGHTNESS_MODE_USER);
}
and
public void setBrightness(int brightness, int brightnessMode) {
synchronized (this) {
int color = brightness & 0x000000ff;
color = 0xff000000 | (color << 16) | (color << 8) | color;
setLightLocked(color, LIGHT_FLASH_NONE, 0, 0, brightnessMode);
}
}
without sending timeout.
If we could read it from liblights somehow.
Click to expand...
Click to collapse
Hmm i have several ideas.
I think the timeout is something rom-dependet. It just sets brightness to 0 after the timeout.
What we can do now without modifying the rom source is to remove button light from the rom and just turn on the button light for a tineout when the buttons are pressed from the kernel. But i think we wouldn't have a ui to apply the settings anymore
Any other ideas?
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app
CoolDevelopment said:
Hmm i have several ideas.
I think the timeout is something rom-dependet. It just sets brightness to 0 after the timeout.
What we can do now without modifying the rom source is to remove button light from the rom and just turn on the button light for a tineout when the buttons are pressed from the kernel. But i think we wouldn't have a ui to apply the settings anymore
Any other ideas?
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think you mean a fixed timeout. I was thinking what if we add this java function
import android.app.Activity;
import android.net.Uri;
import android.os.Bundle;
import android.os.Handler;
import android.view.Menu;
import android.view.MenuItem;
import android.os.UserHandle;
import android.provider.Settings;
import android.content.ContentResolver;
import android.content.Context;
import android.database.ContentObserver;
public class lights_timeout {
Context mContext;
@overide
public static void main(String[] args) {
mContext = this;
int BT = 5000;
BT = Settings.System.getInt(mContext.getContentResolver(), Settings.System.BUTTON_BACKLIGHT_TIMEOUT, 5000);
// WRITE BT TO /SYS/CLASS/.../TIMEOUT
}
}
from device tree, and call it using jni from lights.c .
http://www.codeproject.com/Articles/22881/How-to-Call-Java-Functions-from-C-Using-JNI
This, I don't know if it's working yet. Do you know which lights.c we are using?
beastaki23 said:
I think you mean a fixed timeout. I was thinking what if we add this java function
import android.app.Activity;
import android.net.Uri;
import android.os.Bundle;
import android.os.Handler;
import android.view.Menu;
import android.view.MenuItem;
import android.os.UserHandle;
import android.provider.Settings;
import android.content.ContentResolver;
import android.content.Context;
import android.database.ContentObserver;
public class lights_timeout {
Context mContext;
@overide
public static void main(String[] args) {
mContext = this;
int BT = 5000;
BT = Settings.System.getInt(mContext.getContentResolver(), Settings.System.BUTTON_BACKLIGHT_TIMEOUT, 5000);
// WRITE BT TO /SYS/CLASS/.../TIMEOUT
}
}
from device tree, and call it using jni from lights.c .
http://www.codeproject.com/Articles/22881/How-to-Call-Java-Functions-from-C-Using-JNI
This, I don't know if it's working yet. Do you know which lights.c we are using?
Click to expand...
Click to collapse
This is a good idea.
We are using the proprietary light.cpari.so from stock rom.
Here is an editied lights.c for our device, but with bln support: https://github.com/CoolDevelopment/liblights_s2vep
place this into a folder called liblights in device tree and add lights.capri to PRDUCT_PACKAGES in device_s2vep.mk
CoolDevelopment said:
This is a good idea.
We are using the proprietary light.cpari.so from stock rom.
Here is an editied lights.c for our device, but with bln support: https://github.com/CoolDevelopment/liblights_s2vep
place this into a folder called liblights in device tree and add lights.capri to PRDUCT_PACKAGES in device_s2vep.mk
Click to expand...
Click to collapse
Cannot find this file lights.c file in sources. The other lights.c under hardware directory are different and I don't know which of them s2ve/p use.
This is our hardware sources:
CyanogenMod/android_hardware_samsung
Any idea?
beastaki23 said:
Cannot find this file lights.c file in sources. The other lights.c under hardware directory are different and I don't know which of them s2ve/p use.
This is our hardware sources:
CyanogenMod/android_hardware_samsung
Any idea?
Click to expand...
Click to collapse
You need to add it because our phone does not build the liblights module from source yet, so there is no light.c.
Create a folder named liblights in device/samsung/s2vep and copy everything except the binary folder from here into the folder.
Now add this to device_s2vep.mk:
Code:
PRODUCT_PACKAGES := \
lights.capri
and remove lights.capri.so from vendor files
What's this? Notification light???
OrdinaryNoob

[ROM] [CUSTOM Unofficial] [MM 6.0.1] AICP [FLO]

[CUSTOM UNOFFICIAL]​
AICP MARSHMALLOW 6.0.x BUILD FOR NEXUS7 (2013 Wi-Fi) FLO​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/CENTER][/LEFT]
Flash the ROM at your own risk.
I accept NO responsibility for what you do (or can't do) with your own device. I am not responsible for bootloops, fruitloops or frickazees.
I DO accept responsibility for: Thermonuclear detonation & Zombie Apocalypse.
I started compiling this ROM as Unofficial because I have been using AICP exclusively for 2 years (on M7 & now Bacon) and figure if no one objects I can share some of the work. This is my HOBBY.
With that I say THANK YOU AICP (LorD ClockaN, n3ocort3x & semdoc along with their entire dev team) for bringing such terrific work to our devices.
I make no claim to doing any more than compiling and making minor changes to what I want from the build. I own these devices and enjoy the modifications, I hope you will also. PEACE.
Basic Changes from "Official" AICP Rom:
OTA is NOT enabled on my build
(dirty flashing an "Official" over my build & vice versa does work, most changes I made are cosmetic with some cherri-picks)
I don't recommend "backwards" flashing dirty - so check the build dates
First boot can take up to 10 minutes so be patient
Custom Boot Animation
Unofficial AICP Logos
Custom App for Unofficial Wallpapers [fixed scale when setting papers 4/03]
Amaze FM (new)
Viper4Android [Thank you ViPER520] (User will be prompted to install busybox [may need SuperSU] to load all drivers)
AdAway (new)
Gello Browser compiled from source 4/15/16 (new)
ROM & Kernel Compiled with 5.2.1 GCC Linaro
DOWNLOAD LINK
https://www.androidfilehost.com/?w=files&flid=45367 - - Build compiled 4/30 with cherri-picks listed in Changelog below
Please do not use issues with these builds to ask for help on the official thread. If you get an error, random reboot, etc. attach a logcat to any requests for help if possible. - Thank you
Recommended Gapps:
http://opengapps.org/
TWRP 3.0 Unofficial OR 2.3.0 (other versions have issues flashing radio images, etc. for CM ROMs)
- Nandroid / Backup your device!
- Standard factory reset wipe (recommended unless dirty flashing over THIS build)
- Flash Rom
- Flash Gapps
- Reboot
Custom AICP Boot Animation
View attachment 3662608
Current Changelog:
View attachment Changelog.txt
Full Sync w/ upstream & full update, optimization & sorted AICP Wallpaper App
Gello Changelog (WIP):
Gello: don't move navigation bar when selecting url text …
Gello: remove holo-like share dialog …
Gello: kang in two methods which changed their location and access …
Gello: Share bitmap via stream vs bitmap …
Gello: definitive ad block list …
Gello: web_refiner: Fix EasyList URLs …
gello_build: Makefile moved to vendor/cm …
gello_build: update .gclient file to match caf req …
gello-build: override aosp browser …
gello-build: remove --push …
gello-build: support prebuilt …
My GitHub
https://github.com/IkeGilbert
Bugs:
gerrit.aicp-rom.com - An overview of what is not merged yet (fixes, proposed changes, etc.)
If you get an odd crop setting a wallpaper from the new app, just reboot and it should center the image
High battery drain on all CM builds for Bacon due to GPS issues. If you experience this, turn off GPS while not in use & it should temp fix until full resolution to the issue is made.
Default alarm clock f/c when screen is off
Tips:
Root Access
- Turn on developer setting by tapping build version info
- In developer options, select root access (no need to flash supersu or anything else)
I recommend http://forum.xda-developers.com/apps/greenify for the best battery life!
Be sure to hit the THANKS button (unless thermonuclear war ensues)
--------------------- Checkout these links to the real developers of AICP below -------------------------
AICP Google+
http://gerrit.aicp-rom.com/
http://dwnld.aicp-rom.com/ - Official downloads
.
Thanks mate, will give this a run out later...
Cheers.
Flashed it today as secondary ROM. Thus far working without problems...
===edit===
After testing the ROM for a while I tried installing gapps and was faced with the "Unfortunately, Setup Wizard has stopped" problem that others have also seen. None of the different gapps (opengapps, purenexusgapps, CMgapps-600) that I tested solved the problem. Searching through XDA I saw that some people found a workaround by changing the permissions of the Setup Wizard, e.g. as described here. Some more trial and error revealed that setting the permission for reading the phone state seems to be sufficient for solving the problem.
This can easily be done using adb with the following command:
Code:
adb shell pm grant com.google.android.setupwizard android.permission.READ_PHONE_STATE
Notes:
I used the Marshmallow Base Gapps package for 6.0.0: gapps-600-base-20151201-1-signed.zip but think this should work with other gapps as well.
You could also use a terminal emulator on the device (become root first!) with the following command line pm grant com.google.android.setupwizard android.permission.READ_PHONE_STATE
===edit===
@Floyd_Flivercod Thanks for your work! :good:
Applying the following patch on updater-script would make the AICP-Logo look a little nicer IMHO
Code:
--- /tmp/updater-script.orig 2015-12-05 17:56:41.505163687 +0100
+++ /tmp/updater-script 2015-12-05 18:05:05.751277458 +0100
@@ -8,7 +8,7 @@
run_program("/tmp/install/bin/backuptool.sh", "backup");
unmount("/system");
ui_print("*********************************************");
-ui_print("* ___ __ ___ ___ *");
+ui_print("* ___ ___ ___ ___ *");
ui_print("* /\ \ /\ \ /\ \ /\ \ *");
ui_print("* /::\ \ _\:\ \ /::\ \ /::\ \ *");
ui_print("* /::\:\__\ /\/::\__\ /:/\:\__\ /::\:\__\ *");
tungdil said:
Flashed it today as secondary ROM. Thus far working without problems...
===edit===
After testing the ROM for a while I tried installing gapps and was faced with the "Unfortunately, Setup Wizard has stopped" problem that others have also seen. None of the different gapps (opengapps, purenexusgapps, CMgapps-600) that I tested solved the problem. Searching through XDA I saw that some people found a workaround by changing the permissions of the Setup Wizard, e.g. as described here. Some more trial and error revealed that setting the permission for reading the phone state seems to be sufficient for solving the problem.
This can easily be done using adb with the following command:
Code:
adb shell pm grant com.google.android.setupwizard android.permission.READ_PHONE_STATE
Notes:
I used the Marshmallow Base Gapps package for 6.0.0: gapps-600-base-20151201-1-signed.zip but think this should work with other gapps as well.
You could also use a terminal emulator on the device (become root first!) with the following command line pm grant com.google.android.setupwizard android.permission.READ_PHONE_STATE
===edit===
@Floyd_Flivercod Thanks for your work! :good:
Applying the following patch on updater-script would make the AICP-Logo look a little nicer IMHO
Code:
--- /tmp/updater-script.orig 2015-12-05 17:56:41.505163687 +0100
+++ /tmp/updater-script 2015-12-05 18:05:05.751277458 +0100
@@ -8,7 +8,7 @@
run_program("/tmp/install/bin/backuptool.sh", "backup");
unmount("/system");
ui_print("*********************************************");
-ui_print("* ___ __ ___ ___ *");
+ui_print("* ___ ___ ___ ___ *");
ui_print("* /\ \ /\ \ /\ \ /\ \ *");
ui_print("* /::\ \ _\:\ \ /::\ \ /::\ \ *");
ui_print("* /::\:\__\ /\/::\__\ /:/\:\__\ /::\:\__\ *");
Click to expand...
Click to collapse
If I can tear the device out of my sons hands now when he stops playing minecraft I'll try to give this a shot. Thank you!
PS - I think you'll only see the error if gapps are installed after the first boot.
@Floyd_Flivercod if not too much of a hassle then can you please develop for deb too?
htb2050 said:
@Floyd_Flivercod if not too much of a hassle then can you please develop for deb too?
Click to expand...
Click to collapse
Uploaded a build for DEB (see link in OP)
Floyd_Flivercod said:
Uploaded a build for DEB (see link in OP)
Click to expand...
Click to collapse
Thanks. Downloading now. Will report back after flashing.
Floyd_Flivercod said:
Uploaded a build for DEB (see link in OP)
Click to expand...
Click to collapse
I have been running it for 2 days now. Runs quite well. Everything works just as expected. Thanks for building it.
New build link for FLO added 12/12
Uploaded build 12/18 - https://www.androidfilehost.com/?fid=24269982087021052 & Custom Boot Animation [TWRP Flashable] - https://www.androidfilehost.com/?fid=24269982087020041
Let's try it instead of Pure Nexus.
Thanks
---------- Post added at 23:28 ---------- Previous post was at 22:30 ----------
No Luck with the 12/18 version. Bootloop on the Optimizing Apps.
Clean Flash whith Slim GApps Mini.
guillaumeserton said:
Let's try it instead of Pure Nexus.
Thanks
---------- Post added at 23:28 ---------- Previous post was at 22:30 ----------
No Luck with the 12/18 version. Bootloop on the Optimizing Apps.
Clean Flash whith Slim GApps Mini.
Click to expand...
Click to collapse
I'm baking another one tonight and will upload in the morning. Hopefully the bootloops are cured.
I didn't flashed the Pico version but the mini version instead, so i got bootloop.
With the Pico version, it's ok.
Gapps are touchy with every MM build I've tried so far, and that's not just device specific. I've had best success across the board with Opengapps & SlimRoms Gapps.
BTW - New build uploaded this AM https://www.androidfilehost.com/?fid=24269982087022177 - I dirty flashed on my sons device and it's working fine also.
Shout out to @semdoc for the work here. I think Official nightlies may be coming soon?
New build for DEB - https://www.androidfilehost.com/?fid=24337548750880774
Weekend build compiled & uploaded 2/28 --> https://www.androidfilehost.com/?fid=24421527759890653
Tweaks to the new boot animation & new logos are transparent. They should match your own theme or custom color schemes
Cherry Picks that apply to this build: http://review.cyanogenmod.org/#/c/132378/ - Terminal
Sync'd with upstream & latest official merges applied
View attachment Changelog.txt
New build compiled 4/30 >>> https://www.androidfilehost.com/?w=files&flid=45370
4/30 Build > Full Sync w/ upstream & optimized + sorted Unofficial AICP Wallpaper App
Amaze FM (new)
Viper4Android [Thank you ViPER520] (User will be prompted to install busybox [may need SuperSU] to load all drivers)
AdAway (new)
Gello Browser compiled from source 4/15/16 (new)
ROM & Kernel Compiled with 5.2.1 GCC Linaro
Gello Changelog (WIP):
Gello: don't move navigation bar when selecting url text …
Gello: remove holo-like share dialog …
Gello: kang in two methods which changed their location and access …
Gello: Share bitmap via stream vs bitmap …
Gello: definitive ad block list …
Gello: web_refiner: Fix EasyList URLs …
gello_build: Makefile moved to vendor/cm …
gello_build: update .gclient file to match caf req …
gello-build: override aosp browser …
gello-build: remove --push …
gello-build: support prebuilt …
If Gello Browser does not respond after flashing the ROM, re-install the APK file directly here > https://www.androidfilehost.com/?w=files&flid=54259
Hi there,
I need to root my Nexus 7(2013) 6.0.1 build MOB30J. Can some one please link me. So far I've found und root methods only for the earlier version or different for a build.
Thank you .
tenjohn23 said:
Hi there,
I need to root my Nexus 7(2013) 6.0.1 build MOB30J. Can some one please link me. So far I've found und root methods only for the earlier version or different for a build.
Thank you .
Click to expand...
Click to collapse
Besides nothing at all, what does this have to do with unofficial AICP?
read.

Categories

Resources