Good afternoon, guys, I created a tutorial how to compile roms for Zenfone 5 (x86 chip).
NOTE:
I will use my AOSP device tree but also this tutorial can be used for CM building with another devide tree.
Lets begin.
STEP #1
I recommend you to use this device tree:
(for AOSP)
https://github.com/tank0412/aosp_device_asus_a500cg
https://github.com/tank0412/android_vendor_asus_a500cg
(for CM)
https://github.com/tank0412/android_device_asus_a500cg-1
https://github.com/tank0412/android_vendor_asus_a500cg
Put device folder here:
*AndroidSource-folder*/device/asus
full path:
*AndroidSource-folder*/device/asus/a500cg
Put vendor folder here:
*AndroidSource-folder*/vendor/asus
full path:
*AndroidSource-folder*/vendor/asus/a500cg
STEP #2
Go to *AndroidSource-folder*/hardware and delete intel folder.
Add there this folder:
https://github.com/tank0412/android_hardware_intel-1
Rename it to Intel.
STEP #3
open Terminal
cd *AndroidSource-folder*
. build/envsetup.sh
lunch cm_a500cg-userdebug
make -j6
ERROR 1:
If you get errors due to inline kernel building, you should disable it.
ERROR 2:
If you use device tree by quanganh2627 and you got errors due to device/intel/common folder or due to this:
linux/modules/PRIVATE/fm/broadcom/bt_protocol_driver/AndroidBt.mk
In this case you should open BoardConfig.mk file in the device folder and comment needed lines like here:
#include device/intel/common/gps/GpsBoardConfig.mk
Credits:
@dgadelha (becuase he published his intel/hardware folder)
XDA:DevDB Information
How to compile roms for Zenfone 5 (x86 chip), Tool/Utility for the Asus Zenfone 5
Contributors
tank0412
Version Information
Status: Testing
Created 2016-02-11
Last Updated 2016-07-08
to add the device tree, I need to do git clone https://github.com/quanganh2627/android_vendor_asus_a500cg.git in intel common folder?
TecnoTailsPlays said:
to add the device tree, I need to do git clone https://github.com/quanganh2627/android_vendor_asus_a500cg.git in intel common folder?
Click to expand...
Click to collapse
What? NO no and no.
Wait. I will add more info.
UPD^ More info is added.
tank0412 said:
What? NO no and no.
Wait. I will add more info.
UPD^ More info is added.
Click to expand...
Click to collapse
ok, so what I need to do to add the device tree in a500cg folder? git clone? what command?
---------- Post added at 12:03 ---------- Previous post was at 12:02 ----------
tank0412 said:
What? NO no and no.
Wait. I will add more info.
UPD^ More info is added.
Click to expand...
Click to collapse
and can you add more information about step 4?
TecnoTailsPlays said:
ok, so what I need to do to add the device tree in a500cg folder? git clone? what command?
---------- Post added at 12:03 ---------- Previous post was at 12:02 ----------
and can you add more information about step 4?
Click to expand...
Click to collapse
I think that it is enough. What is your problem?
tank0412 said:
I think that it is enough. What is your problem?
Click to expand...
Click to collapse
what is comment? and what command I tipe to add the device tree?
TecnoTailsPlays said:
what is comment? and what command I tipe to add the device tree?
Click to expand...
Click to collapse
Just unpack archive with device folder and put it in the path above.
To comment just add this symbol "#" to every string.(line)
I provided an example.
You will get something like this:
Code:
#ifeq ($(INTEL_VA),true)
#
#include $(call all-subdir-makefiles)
#
#endif
It was:
Code:
ifeq ($(INTEL_VA),true)
include $(call all-subdir-makefiles)
endif
tank0412 said:
Just unpack archive with device folder and put it in the path above.
To comment just add this symbol "#" to every string.(line)
I provided an example.
You will get something like this:
Code:
#ifeq ($(INTEL_VA),true)
#
#include $(call all-subdir-makefiles)
#
#endif
It was:
Code:
ifeq ($(INTEL_VA),true)
include $(call all-subdir-makefiles)
endif
Click to expand...
Click to collapse
to build I need to choose cm_a500cg-userdebug?
---------- Post added at 13:13 ---------- Previous post was at 13:08 ----------
tank0412 said:
Just unpack archive with device folder and put it in the path above.
To comment just add this symbol "#" to every string.(line)
I provided an example.
You will get something like this:
Code:
#ifeq ($(INTEL_VA),true)
#
#include $(call all-subdir-makefiles)
#
#endif
It was:
Code:
ifeq ($(INTEL_VA),true)
include $(call all-subdir-makefiles)
endif
Click to expand...
Click to collapse
I got this error when building https://drive.google.com/file/d/0B8e62vKMKobRWjBNUllkLXBSRDA/view?usp=sharing
TecnoTailsPlays said:
to build I need to choose cm_a500cg-userdebug?
---------- Post added at 13:13 ---------- Previous post was at 13:08 ----------
I got this error when building https://drive.google.com/file/d/0B8e62vKMKobRWjBNUllkLXBSRDA/view?usp=sharing
Click to expand...
Click to collapse
No.
One config is missing in your kernel sources:
https://github.com/quanganh2627/Kernel-fo-Zenfone-6-by-BORETS24/blob/master/arch/x86/configs/cm_a500cg_defconfig
tank0412 said:
No.
One config is missing in your kernel sources:
https://github.com/quanganh2627/Kernel-fo-Zenfone-6-by-BORETS24/blob/master/arch/x86/configs/cm_a500cg_defconfig
Click to expand...
Click to collapse
so what I do?
TecnoTailsPlays said:
to build I need to choose cm_a500cg-userdebug?
---------- Post added at 13:13 ---------- Previous post was at 13:08 ----------
I got this error when building https://drive.google.com/file/d/0B8e62vKMKobRWjBNUllkLXBSRDA/view?usp=sharing
Click to expand...
Click to collapse
TecnoTailsPlays said:
so what I do?
Click to expand...
Click to collapse
Disable inline kernel building.
Check OP.
tank0412 said:
Disable inline kernel building.
Check OP.
Click to expand...
Click to collapse
how I do that? it is not on the thread
TecnoTailsPlays said:
how I do that? it is not on the thread
Click to expand...
Click to collapse
Oops.
Try to use BoardConfig.mk from AOSP:
https://github.com/tank0412/aosp_device_asus_a500cg/blob/master/BoardConfig.mk
And delete linux folder with kernel sources. (if you have it)
tank0412 said:
Oops.
Try to use BoardConfig.mk from AOSP:
https://github.com/tank0412/aosp_device_asus_a500cg/blob/master/BoardConfig.mk
And delete linux folder with kernel sources. (if you have it)
Click to expand...
Click to collapse
I just need to change the code inside of boardconfig.mk to that one you gived me? and I don't know what linux folder to delete, I searched in search bar and I found more than 20 linux folders
TecnoTailsPlays said:
I just need to change the code inside of boardconfig.mk to that one you gived me? and I don't know what linux folder to delete, I searched in search bar and I found more than 20 linux folders
Click to expand...
Click to collapse
OMG, And i though that i am a noob....
Do you use device tree by Tran Huu Tin?
Note:
Linux folder is a fodler with kernel sources. You could add it manually.
tank0412 said:
OMG, And i though that i am a noob....
Do you use device tree by Tran Huu Tin?
Note:
Linux folder is a fodler with kernel sources. You could add it manually.
Click to expand...
Click to collapse
yes I used it, I am a noob, Its my first time compiling a rom from source
TecnoTailsPlays said:
yes I used it, I am a noob, Its my first time compiling a rom from source
Click to expand...
Click to collapse
STOP.
OMG. You wrote an incorrect command.....
Use this:
Code:
. build/envsetup.sh
lunch cm_a500cg-userdebug
make -j4
tank0412 said:
STOP.
OMG. You wrote an incorrect command.....
Use this:
Code:
. build/envsetup.sh
lunch cm_a500cg-userdebug
make -j4
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B8e62vKMKobRT3FzREt0R3lZalE/view?usp=sharing
TecnoTailsPlays said:
https://drive.google.com/file/d/0B8e62vKMKobRT3FzREt0R3lZalE/view?usp=sharing
Click to expand...
Click to collapse
Try to wipe your trash folder.
And i hope that you really used devcie tree by Tran Huu Tin.
Or you can try to delete healthd folder from devcie tree.
tank0412 said:
Try to wipe your trash folder.
And i hope that you really used devcie tree by Tran Huu Tin.
Or you can try to delete healthd folder from devcie tree.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B8e62vKMKobRQUI1N01OUEg5Qnc/view?usp=sharing
I did what you said
Related
I would like to start building this rom (with kernel), because I did not like how it was stopped by Maclaw, but I need people to help me because I have a netbook and the construction of the rom could be very slow.
Any volunteers?
UP
i can help, did u downloaded the source?
Messi10 said:
i can help, did u downloaded the source?
Click to expand...
Click to collapse
Yes now I just have to fill the rom
Fedefriffo said:
Yes now I just have to fill the rom
Click to expand...
Click to collapse
if u have ant error in building post it here and i will try to help
Can I use Squadzone source for the kernel? I know that support the swap partition ...
Ok I finished the repo sync following this guide: http://source.android.com/source/downloading.html , now how do I build for arm-v6? (noob question)
Fedefriffo said:
Can I use Squadzone source for the kernel? I know that support the swap partition ...
Ok I finished the repo sync following this guide: http://source.android.com/source/downloading.html , now how do I build for arm-v6? (noob question)
Click to expand...
Click to collapse
see this guide
Messi10 said:
see this guide
Click to expand...
Click to collapse
Thanks, it was what I wanted
Ok so now I have a problem with the guide, I followed everything but when he says: replace CM9 folder tree with this, do you mean?
Fedefriffo said:
Ok so now I have a problem with the guide, I followed everything but when he says: replace CM9 folder tree with this, do you mean?
Click to expand...
Click to collapse
do this in terminal
cd android/system
git clone git://github.com/Squadzone/GalaxyMini_cm9_config
Click to expand...
Click to collapse
Messi10 said:
do this in terminal
Click to expand...
Click to collapse
Already done, but when I put the command. build / envsetup.sh && brunch tass says it can not find the device
Fedefriffo said:
Already done, but when I put the command. build / envsetup.sh && brunch tass says it can not find the device
Click to expand...
Click to collapse
try repo sync again
Messi10 said:
try repo sync again
Click to expand...
Click to collapse
Ok now I try to build, likely tomorrow afternoon news
One question, can I use the 3.0 kernel source taken by galaxy nexus?
Fedefriffo said:
Ok now I try to build, likely tomorrow afternoon news
One question, can I use the 3.0 kernel source galaxy taken by nexus?
Click to expand...
Click to collapse
i don't think so
there is no "brunch" in aosp;
do:
Code:
. build/envsetup.sh && lunch full_tass-userdebug
Code:
make -j[B]x[/B]
o r
Code:
make -j[B]x[/B] otapackage
where x is jobs, I have 4 cores and 4 threads so I use make -j8
TheWhisp said:
there is no "brunch" in aosp;
do:
Code:
. build/envsetup.sh && lunch full_tass-userdebug
Code:
make -j[B]x[/B]
o r
Code:
make -j[B]x[/B] otapackage
where x is jobs, I have 4 cores and 4 threads so I use make -j8
Click to expand...
Click to collapse
I have this error: federico @ Balamb-DOTS: ~ / $ AOSP_GALAXY_MINI. build / && envsetup.sh lunch full_tass-userdebug
Including device / asus / grouper / vendorsetup.sh
Including device/generic/armv7-a-neon/vendorsetup.sh
Including device/generic/armv7-a/vendorsetup.sh
Including device / bike / wingray / vendorsetup.sh
Including device/samsung/crespo4g/vendorsetup.sh
Including device / samsung / kinky / vendorsetup.sh
Including device / samsung / maguro / vendorsetup.sh
Including device / samsung / bull / vendorsetup.sh
Including device / you / panda / vendorsetup.sh
Including sdk / bash_completion / adb.bash
build / core / product_config.mk: 205: *** No product matches for "full_tass". Arrest.
Product ** Do not have a spec for: 'full_tass'
** Do you have the right repo manifest?
federico @ Balamb-DOTS: ~ / $ AOSP_GALAXY_MINI
you need file full_tass.mk in device/samsung/tass. Check github/MaclawStudios
TheWhisp said:
you need file full_tass.mk in device/samsung/tass. Check github/MaclawStudios
Click to expand...
Click to collapse
I've found full_gio.mk not full_tass.mk
Fedefriffo said:
I've found full_gio.mk not full_tass.mk
Click to expand...
Click to collapse
Just take this (attachment)
Thanks now i build...
Hi
I am experiencing this problem while I went for final step (
Code:
mka bacon -j8
).
It did not create any zip in .../out/target/product/DeviceName/
Here is the log->
http://pastebin.com/CcNXpbSR
I believe the cause of problem could be->
Code:
make: *** No rule to make target `/home/jaskaran/android/UbuntuPort/out/target/common/obj/APPS/framework-res_intermediates/src/R.stamp', needed by `/home/jaskaran/android/UbuntuPort/out/target/common/obj/APPS/DeviceSettings_intermediates/src/R.stamp'. Stop.
(As told by a forum member).
I basically didn't see any errors in outputs except "fatal: Invalid git file format: ...repo/repo/.git/clone.bundle" but thats network problem. Right? And btw the sync went fine after that. Even when I ran repo sync again (without deleting repo folder), it successfully fetched everything from existing files. There was no error then.
I also did run make clean command before building it, but still.....
EDIT:
I came over this problem by editing the i9300.mk and removing "DeviceSettings \"->
Code:
# Product specific Packages
PRODUCT_PACKAGES += \
DeviceSettings \
libsecril-client \
libsecril-client-sap \
SamsungServiceMode \
tinyplay
(so is it ok? Or will I loose settings app?)
Anyhow, I came over this error and there is a new one now->
Code:
Export includes file: frameworks/av/services/camera/libcameraservice/Android.mk -- /home/jaskaran/android/UbuntuPort/out/target/product/i9300/obj/SHARED_LIBRARIES/libcameraservice_intermediates/export_includes
make: *** No rule to make target `/home/jaskaran/android/UbuntuPort/out/target/product/i9300/obj/SHARED_LIBRARIES/libTVOut_intermediates/export_includes', needed by `/home/jaskaran/android/UbuntuPort/out/target/product/i9300/obj/EXECUTABLES/mediaserver_intermediates/import_includes'. Stop.
make: *** Waiting for unfinished jobs....
Thanks.
Please help.
Can u guys help me porting it on my s3
Sent from my GT-I9300 using xda app-developers app
Do this. make -j 8 otapackage. I've built as I tell. I'll post it here my night's otapackage successfully built if you want.
It's for trusty tahr.
Sent from my GT-I9300 using Tapatalk
---------- Post added at 12:48 PM ---------- Previous post was at 12:34 PM ----------
astronfestmon said:
Do this. make -j 8 otapackage. I've built as I tell. I'll post it here my night's otapackage successfully built if you want.
It's for trusty tahr.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
link:
http://www.mediafire.com/download/b3274qlh47y1cw9/cm_i9300-ota-eng.pedro.zip
my build worked with raring.
trying to boot trusty.
i've forgot to make new changes doing it now.
---------- Post added at 04:27 PM ---------- Previous post was at 04:01 PM ----------
it gave me green light but no screen.
tomorrow check it out
How to port it and any bugs bro??
Sent from my GT-I9300 using xda app-developers app
make as the following i9300 wiki ubuntu guide.
then make -j8 otapackage inside your ubuntu touch folder
i'll explain more tomorrow
Do this.
Install phablet tools with sudo apt-get install -y phablet-tools
Then phablet-dev-bootstrap -c ubuntu/
To sync the repo source code.
cd ubuntu
source build/envsetup.sh
lunch cm_i9300-userdebug
mka -j3 otapackage
See you
Sent from my GT-I9300 using Tapatalk
Trying my new kernel with googymax v1.
Ubuntu trusty connected as googymax1 1st rom is giving me black screen but adb devices showing it as device.
Doing adb shell you can connect it into it.
help
Hello,
Can someone fix the phone /SMS problem or know how to do it ? Because I'll love have ubuntu touch on my gs3 but I can't devellop ubuntu by myself because I don't know how to do this .... Please ; thanks for considération and sorry forme m'y bad english .
Is it easy to use Ubuntu on S3?
Could not start the installation. Booted to recovery, wiped everything, trying to flash Build No5 in recovery and STATUS 7 error comes. The installation stops already at the beginning. Any suggestions ?
Thanks in advance.
buddy66 said:
Could not start the installation. Booted to recovery, wiped everything, trying to flash Build No5 in recovery and STATUS 7 error comes. The installation stops already at the beginning. Any suggestions ?
Thanks in advance.
Click to expand...
Click to collapse
Status 7 means your Clockworkmod Recovery is outdated. I suggest updating it using ROM manager from the Play store. The same problem will occur if you try to install Android Kitkat versions as long as you don't update CWM.
Is this build working. Thanks for the info.
astronfestmon said:
my build worked with raring.
trying to boot trusty.
i've forgot to make new changes doing it now.
---------- Post added at 04:27 PM ---------- Previous post was at 04:01 PM ----------
it gave me green light but no screen.
tomorrow check it out
Click to expand...
Click to collapse
You're build wouldn't boot .
So, the current builds are that CALLS/SMS don't work? And random freezes. That's all?
Trusty tahr s3 i9300 intl
supreethms said:
So, the current builds are that CALLS/SMS don't work? And random freezes. That's all?
Click to expand...
Click to collapse
Here it goes howto I've done the changes.
mkdir ~/ubuntu
cd ubuntu/
on terminal too:
repo init -u https://code-review.phablet.ubuntu.com/p/aosp/platform/manifest.git -b phablet-4.4.2_r1
repo sync -j8
after sync the repo files
Download the following files:
bootable recovery 4.4.2 r1 : https://android.googlesource.com/platform/bootable/recovery/+/android-4.4.2_r1
into folder bootable
copy my device samsung i9300 also smdk4412-common into device samsung folder
source build/envsetup.sh
lunch aosp_i9300-userdebug
make
PS: I'll upload my device i9300 changes right next and I'll my repo downoad link
I don't have a PC to build. Can you make a cwm zip to flash?
Sure I can.
Thank you :thumbup::thumbup:
astronfestmon said:
Here it goes howto I've done the changes.
mkdir ~/ubuntu
cd ubuntu/
on terminal too:
repo init -u https://code-review.phablet.ubuntu.com/p/aosp/platform/manifest.git -b phablet-4.4.2_r1
repo sync -j8
after sync the repo files
Download the following files:
bootable recovery 4.4.2 r1 : https://android.googlesource.com/platform/bootable/recovery/+/android-4.4.2_r1
into folder bootable
copy my device samsung i9300 also smdk4412-common into device samsung folder
source build/envsetup.sh
lunch aosp_i9300-userdebug
make
PS: I'll upload my device i9300 changes right next and I'll my repo downoad link
Click to expand...
Click to collapse
Hi, sir. Well. I am not an expert with this.
I am still learning.
But, till today all i have learnt on phones is to boot to recovery and flash ROMs.
I just want to frankly say this.
But, i appreciate your work very much. Have been following your posts on this thread from the beginning.
All i wanted to know was that if ONLY calls/sms and random reboots are the flaws with the current builds.
Thank you.
Hi. i have tried to compile cm11 kernel by using kernel source from http://github.com/cm-nokia-x2 and gcc toolchain 4.8 from here http://github.com/huyparody/gcc_linaro
i get config.gz from /proc/
and renamed it to ara_defconfig
and when i:
make ara_defconfig
make
after a few minute, it show me a error:
CC drivers/input/touchscreen/cyttsp4_device_access.o
drivers/input/touchscreen/cyttsp4_device_access.c: In function 'cyttsp4_grpdata_store_touch_params':
drivers/input/touchscreen/cyttsp4_device_access.c:1447:19: warning: 'rc3' may be used uninitialized in this function [-Wuninitialized]
error, forbidden warning: cyttsp4_device_access.c:1447
make[3]: *** [drivers/input/touchscreen/cyttsp4_device_access.o] Error 1
make[2]: *** [drivers/input/touchscreen] Error 2
make[1]: *** [drivers/input] Error 2
make: *** [drivers] Error 2
[email protected]:~/android/kernel/nokia/msm8610$
Click to expand...
Click to collapse
how to solve it!! thanks much
kaotd99 said:
how to solve it!! thanks much
Click to expand...
Click to collapse
Hello,
Use toolchain from CyanogenMod prebuilt repo, here is link: github.com/CyanogenMod/android_prebuilt/tree/cm-11.0/linux-x86/toolchain/arm-eabi-4.4.3
You also don't need to copy config from /proc, it is included in source at arch/arm/configs/msm8610-nokia-defconfig.
zombah said:
Hello,
Use toolchain from CyanogenMod prebuilt repo, here is link: github.com/CyanogenMod/android_prebuilt/tree/cm-11.0/linux-x86/toolchain/arm-eabi-4.4.3
You also don't need to copy config from /proc, it is included in source at arch/arm/configs/msm8610-nokia-defconfig.
Click to expand...
Click to collapse
thanks dev
oh god... i got new error:
i type:
export PATH=/home/kaotd/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin:$PATH
export ARCH=arm
export CROSS_COMPILE=arm-eabi-
and:
[email protected]:/home/kaotd/android/kernel/nokia/msm8610# make msm8610-nokia_defconfig
#
# configuration written to .config
#
[email protected]:/home/kaotd/android/kernel/nokia/msm8610# make
scripts/kconfig/conf --silentoldconfig Kconfig
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CC kernel/bounds.s
kernel/bounds.c:1: error: bad value (cortex-a7) for -mtune= switch
make[1]: *** [kernel/bounds.s] Error 1
make: *** [prepare0] Error 2
[email protected]:/home/kaotd/android/kernel/nokia/msm8610#
Click to expand...
Click to collapse
can you help me ? thanks.... because im a newbie and sorry about that
kaotd99 said:
can you help me ? thanks.... because im a newbie and sorry about that
Click to expand...
Click to collapse
Hello,
Ahh yep, i forgot switch to memcpy optimizations, here is correct link to newer toolchain android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7
zombah said:
Hello,
Ahh yep, i forgot switch to memcpy optimizations, here is correct link to newer toolchain android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7
Click to expand...
Click to collapse
thanks.. i will try and report to you later!! thanks again
@zombah hi again. i was compiled a kernel( zImage )
now i have "Kernel: arch/arm/boot/zImage is ready"
so how can i compare it with boot.img ?
Hello,
If you wont use inline kernel building inside CyanogenMod, you probably need to unpack boot.img content replace kernel and then pack boot.img again with replaced kernel. Remember that it is dangerous if your kernel is not bootable, you'll stuck to recovery only boot and if your recovery also lost only unbricking will help.
Use CyanogenMod mkbootimg.c/unpackbootimg.c for that, here is repo github.com/CyanogenMod/android_system_core/tree/cm-11.0/mkbootimg
Here is how to compile them separatly of whole system:
Code:
gcc -o mkbootimg mkbootimg.c ../libmincrypt/sha.c -I../include
gcc -o unpackbootimg unpackbootimg.c ../libmincrypt/sha.c -I../include
you'll need to download dependencies also.
zombah said:
Hello,
If you wont use inline kernel building inside CyanogenMod, you probably need to unpack boot.img content replace kernel and then pack boot.img again with replaced kernel. Remember that it is dangerous if your kernel is not bootable, you'll stuck to recovery only boot and if your recovery also lost only unbricking will help.
Use CyanogenMod mkbootimg.c/unpackbootimg.c for that, here is repo github.com/CyanogenMod/android_system_core/tree/cm-11.0/mkbootimg
Here is how to compile them separatly of whole system:
Code:
gcc -o mkbootimg mkbootimg.c ../libmincrypt/sha.c -I../include
gcc -o unpackbootimg unpackbootimg.c ../libmincrypt/sha.c -I../include
you'll need to download dependencies also.
Click to expand...
Click to collapse
thanks much
can you tell me which file contain OverClock number of nokia x2 ? and which kernelPatch i can apply with this kernel ?
Hello,
I don't know, i'm not interested in overclocking and never investigated this question.
And i don't recommend you to play with overclocking without deep embedded development skills, it is very easy to kill your device with wrong power modifiers.
i'm understand, thanks for your suggestion.
not about nokia x2ds but can i ask you a question?
-can i make a kernel source for a mtk device ? because i have a mtk china phone which not have kernel source from manufacturer !
kaotd99 said:
i'm understand, thanks for your suggestion.
not about nokia x2ds but can i ask you a question?
-can i make a kernel source for a mtk device ? because i have a mtk china phone which not have kernel source from manufacturer !
Click to expand...
Click to collapse
Hello,
Sure it is possible, why not. But you need at least serial/uart console on device, otherwise how you will debug kernel boot problems?
zombah said:
Hello,
Sure it is possible, why not. But you need at least serial/uart console on device, otherwise how you will debug kernel boot problems?
Click to expand...
Click to collapse
thanks... now i'm trying to port double-tap to wake feature from Nokia Stock Kernel. There is any suggestion ?? Thanks
i'm trying to add this: https://github.com/ryanaepple/android_kernel_motoe/commit/080003bc8e61349bf7c8da00fa6923f3c84d1927
and being stuck at editing synaptics_dsx_i2c.c and synaptics_dsx_i2c.h
can you tell me which files is Touchscreen driver of nokia x2 ?? i think it is synaptics_i2c_rmi4.c/.h
kaotd99 said:
can you tell me which files is Touchscreen driver of nokia x2 ?? i think it is synaptics_i2c_rmi4.c/.h
Click to expand...
Click to collapse
Hello,
Nokia X2 have Cypress TMA4XX touchscreen, driver location is drivers/input/touchscreen/cyttsp4*
Hi everyone,
I wanna build old version of Xposed, for Android SDK 16-19, then have tried to compile Xposed fw for hundreds time but still failed.
Environment: Ubuntu 15.10 x64 | tools: JDK 1.6, libc6 ....
AOSP: JZO54L / android-4.1.2_r2 /Jelly Bean ("make app_process" have been run successfully).
My steps:
- Download AOSP into /opt/android/aosp
- XposedBridge.jar: Download Xposed Installer here repo[dot]xposed[dot]info/module/de.robv.android.xposed.installer and detach jar from apk. Put it to /opt/out/java
- Download XposedTools source from github into /opt/xposed/ then make build.conf file:
[General]
outdir = /opt/out
[Build]
# Please keep the base version number and add your custom suffix
version = 58
# makeflags = -j4
[GPG]
sign = release
user = 852109AA!
# Root directories of the AOSP source tree per SDK version
[AospDir]
16 = /opt/android/aosp
# SDKs to be used for compiling BusyBox
# Needs github[dot]com/rovo89/android_external_busybox
[BusyBox]
Click to expand...
Click to collapse
- To integrate Xposed to AOSP, I tried following 2 ways in the instruction (local manifest and manual cloning)
+ local manifest: link [XposedTools]/local_manifests/xposed_sdk16.xml to [aosp]/.repo/local_manifests/ then run repo sync.
+ manual cloning: remove [aosp]/build; clone github[dot]com/rovo89/platform_build/ to replace; clone github[dot]com/rovo89/Xposed into [aosp]/framework/base/cmds/xposed
- Go back to [XposedTools] and run ./build -t x86:16
>>output: cd /opt/android/aosp && . build/envsetup.sh >/dev/null && lunch full_x86-user >/dev/null && make -j8 TARGET_CPU_SMP=true xposed
Click to expand...
Click to collapse
The result I received is a big "app_process_xposed" file (~ 270-350 KBs), it size is as many times as the origin app_process file (~20 KBs). I think there are somethings wrong. I open them by 7z and see some differences:
i.imgur.com/PU80vSV.png
Click to expand...
Click to collapse
I may did some mistakes in these steps. Could you please give me any advice?
Thank so much!
Help me Pls...
Did you actually try the app_process_xposed you got, or did you just assume it was wrong because it was bigger? If you did try it, what did it do?
josephcsible said:
Did you actually try the app_process_xposed you got, or did you just assume it was wrong because it was bigger? If you did try it, what did it do?
Click to expand...
Click to collapse
Thank for your reply. I tried rename app_process_xposed to app_process_sdk16 then push new file to assets folder of XposedInstaller project. When XposedInstaller.apk file installed, i had receive messages not compatible with my sdk 19...
hahalulu said:
When XposedInstaller.apk file installed, i had receive messages not compatible with my sdk 19...
Click to expand...
Click to collapse
What was the exact message that you got? Can you post a screenshot of it?
josephcsible said:
What was the exact message that you got? Can you post a screenshot of it?
Click to expand...
Click to collapse
My message i had received
Update: sdk16.zip file
I'm still stuck at this problem :crying:
hahalulu said:
I'm still stuck at this problem :crying:
Click to expand...
Click to collapse
build duoc chua ban. minh cung dang bi giong ban. khong biet giai quyet the nao
hellboy211 said:
build duoc chua ban. minh cung dang bi giong ban. khong biet giai quyet the nao
Click to expand...
Click to collapse
Please post in English, I have translated this one for you
Regards
Sawdoctor
Build is not acid. You are also welcome. Not the right time
Does its existence for devices like the Z3C make it more or less likely for us to see on suzuran? Would love to see a LineageOS 17 ROM for this device. Makes me wish I was a dev. Thanks to all those who continue to grind hours into porting and developing ROMs for the platform.
beflythis said:
Would love to see a LineageOS 17 ROM for this device.
Click to expand...
Click to collapse
Oh! I have successfully built a LineageOS 17.0 rom for z5c! :good:
But.... As my 16.0 try this rom is not booting...
Don't know why
Berni-0815 said:
Oh! I have successfully built a LineageOS 17.0 rom for z5c! :good:
But.... As my 16.0 try this rom is not booting...
Don't know why
Click to expand...
Click to collapse
Are you making any kernel changes? If not, that's probably why. You can't use the LineageOS 15.1 kernel on the PIE. Correct me if I'm wrong but Pie requires linux kernel 4.4x and greater while, Android 10 requires 4.9 and greater.
Apart from fixing compile-errors, no.
But I don't think that the kernel version is important. This project uses kernel 3.x too, if I'm not wrong...
Sure, there have to be changes, but I can't do so...
I've tried another kernel (this one) and I changed/added some files to avoid compile errors. But the result is the same:
The splash screen apears, then a blank screen....
The splash screen apears, then a blank screen....
The splash screen apears, then a blank screen....
The splash screen apears, then a blank screen....
...and so on until end of battery...
Have you tried looking at any sort of logs, kernel logs? (I'm not sure if there would be one in the first place) It would be better to try by increments (PIE first with https://github.com/joel16/android_kernel_sony_msm8994). I might give it a try this weekend just for the sake of it.
Joel16 said:
Have you tried looking at any sort of logs, kernel logs? (I'm not sure if there would be one in the first place)
Click to expand...
Click to collapse
Where should these logs be?
I have no access to the device at this early stage...
An when I reflash a working rom /system will be overwritten.
It would be better to try by increments (PIE first with https://github.com/joel16/android_kernel_sony_msm8994). I might give it a try this weekend just for the sake of it.
Click to expand...
Click to collapse
I've tried to build pie with this kernel. Nearly the same result.
Berni-0815 said:
Where should these logs be?
I have no access to the device at this early stage...
An when I reflash a working rom /system will be overwritten.
I've tried to build pie with this kernel. Nearly the same result.
Click to expand...
Click to collapse
Weird, I ran into some issues building pie yesterday, but didn't have any time to fix it. I'll try again tonight and see how it goes. If I still have issues, I'll have to wait till the weekend.
Joel16 said:
Weird, I ran into some issues building pie yesterday
Click to expand...
Click to collapse
I'm sorry; I should have tell you about that... :angel:
I changed a lot of things to compile it successfully. Here are my changes (I hope this list is complete):
.bashrc:
Code:
export CPU_SSE42=false
to avoid crashes in hiddenapi and profman
device/sony/kitakami-common/SonyOtgSwitch/Android.mk:
Code:
LOCAL_SDK_VERSION := current
kernel/sony/msm8994/include/uapi/linux/rmnet_data.h; insert lines 226 to 236 (line 226 changed [a comma at the end of line]):
Code:
RMNET_NETLINK_DEL_VND_TC_FLOW,
/*
* RMNET_NETLINK_NEW_VND_WITH_NAME - Creates a new virtual network
* device node with the specified
* device name
* Args: int32_t node number
* char[] vnd_name - Use as name
* Returns: status code
*/
RMNET_NETLINK_NEW_VND_WITH_NAME
bionic/libc/include/bits/fortify/fcntl.h; insert lines 33 to 36:
Code:
#ifndef __O_TMPFILE
#define __O_TMPFILE 020000000
#endif
#define O_TMPFILE (__O_TMPFILE | O_DIRECTORY)
hardware/qcom/audio-caf/msm8994/hal/audio_hw.c; line 2457:
Code:
ALOGE("%s: error [B]%ld[/B] - %s", __func__, ret, pcm_get_error(out->pcm));
hardware/qcom/audio-caf/msm8994/hal/audio_extn/audio_extn.c; lines 523 and 524:
Code:
void audio_extn_set_parameters(struct audio_device *adev [B]__unused[/B],
struct str_parms *parms [B]__unused[/B])
and line 67:
Code:
static struct audio_extn_module aextnmod [B]__unused[/B] = {
hardware/qcom/display-caf/msm8994/libqdutils/idle_invalidator.cpp; line 127:
Code:
ALOGD_IF(II_DEBUG, "IdleInvalidator::%s Idle Timeout fired len [B]%ld[/B]",
hardware/qcom/display-caf/msm8994/libhdmi/hdmi.cpp: line 196:
Code:
ALOGD("%s: Scan Info string: %s length = [B]%ld[/B]",
and line 320:
Code:
ALOGD_IF(DEBUG, "%s: EDID string: %s length = [B]%ld[/B]",
device/sony/kitakami-common/SonyOtgSwitch/Android.mk: line 5:
Code:
LOCAL_PRIVATE_PLATFORM_APIS := true
Changes in bold
Berni-0815 said:
I'm sorry; I should have tell you about that... :angel:
I changed a lot of things to compile it successfully. Here are my changes (I hope this list is complete):
.bashrc:
Code:
export CPU_SSE42=false
to avoid crashes in hiddenapi and profman
device/sony/kitakami-common/SonyOtgSwitch/Android.mk:
Code:
LOCAL_SDK_VERSION := current
kernel/sony/msm8994/include/uapi/linux/rmnet_data.h; insert lines 226 to 236 (line 226 changed [a comma at the end of line]):
Code:
RMNET_NETLINK_DEL_VND_TC_FLOW,
/*
* RMNET_NETLINK_NEW_VND_WITH_NAME - Creates a new virtual network
* device node with the specified
* device name
* Args: int32_t node number
* char[] vnd_name - Use as name
* Returns: status code
*/
RMNET_NETLINK_NEW_VND_WITH_NAME
bionic/libc/include/bits/fortify/fcntl.h; insert lines 33 to 36:
Code:
#ifndef __O_TMPFILE
#define __O_TMPFILE 020000000
#endif
#define O_TMPFILE (__O_TMPFILE | O_DIRECTORY)
hardware/qcom/audio-caf/msm8994/hal/audio_hw.c; line 2457:
Code:
ALOGE("%s: error [B]%ld[/B] - %s", __func__, ret, pcm_get_error(out->pcm));
hardware/qcom/audio-caf/msm8994/hal/audio_extn/audio_extn.c; lines 523 and 524:
Code:
void audio_extn_set_parameters(struct audio_device *adev [B]__unused[/B],
struct str_parms *parms [B]__unused[/B])
and line 67:
Code:
static struct audio_extn_module aextnmod [B]__unused[/B] = {
hardware/qcom/display-caf/msm8994/libqdutils/idle_invalidator.cpp; line 127:
Code:
ALOGD_IF(II_DEBUG, "IdleInvalidator::%s Idle Timeout fired len [B]%ld[/B]",
hardware/qcom/display-caf/msm8994/libhdmi/hdmi.cpp: line 196:
Code:
ALOGD("%s: Scan Info string: %s length = [B]%ld[/B]",
and line 320:
Code:
ALOGD_IF(DEBUG, "%s: EDID string: %s length = [B]%ld[/B]",
device/sony/kitakami-common/SonyOtgSwitch/Android.mk: line 5:
Code:
LOCAL_PRIVATE_PLATFORM_APIS := true
Changes in bold
Click to expand...
Click to collapse
Yup I made those changes except for
Code:
export CPU_SSE42=false
I did not get any issues building but the device does bootloop. I'm gonna see if we can try and pull any sort of logs to see what's causing the issue.
Joel16 said:
Yup I made those changes except for
Code:
export CPU_SSE42=false
I did not get any issues building
Click to expand...
Click to collapse
That seems to be a problem with my cpu. The mentioned line is a cpu instruction. While trying to build this rom on my pc I ran into errors.
but the device does bootloop. I'm gonna see if we can try and pull any sort of logs to see what's causing the issue.
Click to expand...
Click to collapse
Maybe it's possible to backup the system onto a sd-card with an actual twrp and analyse these files?
Berni-0815 said:
That seems to be a problem with my cpu. The mentioned line is a cpu instruction. While trying to build this rom on my pc I ran into errors.
Maybe it's possible to backup the system onto a sd-card with an actual twrp and analyse these files?
Click to expand...
Click to collapse
I'm not entirely sure how it works, but I have heard people talking about pulling logs form bootloops. I mean there has to be a way to debug a bootloop, I highly doubt people just blindly fix them. Perhaps we can access last kernel message or logcat, someway. I'm going to try this weekend and see what I can come up with.
You can do It!!!
Joel16 said:
I'm not entirely sure how it works, but I have heard people talking about pulling logs form bootloops. I mean there has to be a way to debug a bootloop, I highly doubt people just blindly fix them. Perhaps we can access last kernel message or logcat, someway. I'm going to try this weekend and see what I can come up with.
Click to expand...
Click to collapse
Berni-0815 said:
That seems to be a problem with my cpu. The mentioned line is a cpu instruction. While trying to build this rom on my pc I ran into errors.
Maybe it's possible to backup the system onto a sd-card with an actual twrp and analyse these files?
Click to expand...
Click to collapse
What is about adbd, see here:
https://forum.xda-developers.com/showpost.php?p=67386761&postcount=13
The z5c is based on Qualcomm Snapdragon 810 MSM8994, like:
SONY XPERIA Z5 PREMIUM | MOTOROLA DROID TURBO | MICROSOFT LUMIA 950 XL | NUBIA Z9 MAX
Is there any source of a pie build availible where we can get some hints how get a pie build to run?
Here are some kernel sources from the Nubia Z9 Max (nx510j):
https://github.com/nubia-development/android_kernel_nubia_msm8994
I_did_it_just_tmrrow said:
What is about adbd, see here:
https://forum.xda-developers.com/showpost.php?p=67386761&postcount=13
Click to expand...
Click to collapse
I'll have a look at this. :good:
Joel16 said:
Have you tried looking at any sort of logs, kernel logs? (I'm not sure if there would be one in the first place) It would be better to try by increments (PIE first with https://github.com/joel16/android_kernel_sony_msm8994). I might give it a try this weekend just for the sake of it.
Click to expand...
Click to collapse
For my self I try slowly become deeper into that topic: building a rom.
So I did a little bit of research in github and gitlab and I found some interesting repos from this user:
https://github.com/Cyborg2017?tab=repositories
I ask him if he could help us a little bit and the first result is this.
@Joel16 & @Berni-0815 Perhaps this is useful:
https://github.com/Cyborg2017/android_kernel_sony_msm8994/tree/sony_msm8994_p-upstream
I hope it help us to come closer to an LineageOS 17 for suzuran.
I_did_it_just_tmrrow said:
I ask him if he could help us a little bit and the first result is this.
Click to expand...
Click to collapse
Error 404
A little time later: I think, you're talking about this kernel?
---------- Post added at 16:22 ---------- Previous post was at 16:03 ----------
I_did_it_just_tmrrow said:
What is about adbd, see here:
https://forum.xda-developers.com/showpost.php?p=67386761&postcount=13
Click to expand...
Click to collapse
Tried the mentioned tip in the 2nd post of this that thread without any success. I'm so sorry.
How can I include adbd into my build? I'll give it a try...
Berni-0815 said:
Error 404
A little time later: I think, you're talking about this kernel?
---------- Post added at 16:22 ---------- Previous post was at 16:03 ----------
Tried the mentioned tip in the 2nd post of this that thread without any success. I'm so sorry.
How can I include adbd into my build? I'll give it a try...
Click to expand...
Click to collapse
Yep, just try his source. He told that it could be useful to test this kernel with building twrp first.
To the logging problem. I understand that right that you have nothing in:
Code:
/proc/last_kmsg
Nor in:
Code:
/sys/fs/pstore/console-ramoops
and you check this with the twrp terminal?
You should take a look at this:
https://android.stackexchange.com/questions/213336/how-can-i-enable-last-kmsg
I_did_it_just_tmrrow said:
Yep, just try his source.
Click to expand...
Click to collapse
I'm actually building a rom with that kernel. I'll see later if it's working.
To the logging problem. I understand that right that you have nothing in:
Code:
/proc/last_kmsg
Nor in:
Code:
/sys/fs/pstore/console-ramoops
and you check this with the twrp terminal?
Click to expand...
Click to collapse
Right
You should take a look at this:
https://android.stackexchange.com/questions/213336/how-can-i-enable-last-kmsg
Click to expand...
Click to collapse
Ah! Nice. I'll try it later. Thank you very much! :good:
Berni-0815 said:
I'm actually building a rom with that kernel. I'll see later if it's working.
Right
Ah! Nice. I'll try it later. Thank you very much! :good:
Click to expand...
Click to collapse
Let me know how it goes, I'm more than certain kernel is what's preventing us from getting Pie/Q to boot up.