[GUIDE][COMPLETE] Android ROM Development From Source To End

[deve678]

build finished, But after flashing mobile, My Device Can Not Start Boot Normally And reboots

You mean bootloop?

 

[smart-t78]

kmsg: https://paste.ubuntu.ir/xwmn
dmesg: https://paste.ubuntu.ir/ttyx

please post a link to your device sources (device, vendor, kernel)

 

[MHK2012]

please post a link to your device sources (device, vendor, kernel)

vendor: http://github.com/TheMuppets/proprietary_vendor_samsung
device: http://github.com/tilaksidduram/android_device_samsung_n7100
kernel: http://github.com/LineageOS/android_kernel_samsung_smdk4412

 

[_d4Mn_]

Can Auto-Permissions Enabled be done?

Friends,

I'm in a making of an application that has to be running on a custom rom (this projects is running for 1,5 years now and I am nearly finished). Basically I am creating a tablet that is meant to be used for one thing only and that's it (purpose made machine). Have nearly finished my app and have built my ROM with most of the modifications I needed (cm14.1).
Few things I cannot figure out.

The goal is to avoid the "give permission" pop-up window to appear at the first run of the app.

1.: Is it achievable to have the required permissions already given to my application? Can I set this somewhere in the source files?
2.: Alternatively can I give all the required permissions to every app somehow?
3.: Is the above goal is achieveable at all?

This tablet will be used in schools by mentally low-skilled people and cannot rely on them reading and giving the permissions at the first run. I also dont want their teachers to do this at the first time after the tablets are delivered. I would like to have a ROM that I flash and will have everything ready to go.

Can anyone help?

 

[DiamondJohn]

Having a bootloop issue on an Oreo Rom for ks01ltexx.
kernel: https://github.com/kyasu/android_kernel_samsung_msm8974
device: https://github.com/kyasu/android_device_samsung_ks01ltexx
vendor: https://github.com/kyasu/android_vendor_samsung_ks01ltexx

The weird things are:
It will boot loop about 2-5 times and then boot up ok
If I replace the init.qcom.rc from another device (but a little similar), the bootloop disappears but things like WiFi don't work
I previously built this without problems

I have taken a last_kmsg at both success and failure, and compared the two.Basically the difference starts at the following
GOOD: https://www.hastebin.com/avabopojug.bash
BOOT-LOOP: https://www.hastebin.com/odajuqonit.bash
View attachment 4577859

They appear to diverge at "samsung_dsi_panel_event_handler : unknown event " on the good side, but that same event occurs many times on both sides above.

Any ideas? or even where to start next?

I have looked for the function, and its defined in 4 or 5 files within the kernel, which appear to be based on resolution. I am 1920x1080
View attachment 4577872

 

[Jay_B]

I am compiling Oreo-based ROMs for Oxygen (Xiaomi Mi Max 2). The Oreo sources are not out yet for it.

The issue we have been facing is the "in-call" vol. We are not able to increase or decrease the vol during a call be it from the phones hardware keys or from a headphones hardware keys. For the rest of the media, it works quite good.

I am attaching a call log along with links to the trees I am using, hoping someone out on XDA might be able to help us out.

Oxygen DT : https://github.com/jayant-b/device_xiaomi_oxygen

msm8953-common DT :
https://github.com/jayant-b/device_xiaomi_msm8953-common

Kernel :
https://github.com/jayant-b/andorid_kernel_xiaomi_oxygen

Vendor
https://github.com/jayant-b/proprietary_vendor_xiaomi_oxygen

Log:
https://hastebin.com/wetaxomibo.coffeescript

 

[Sapphiress]

Can anyone help me with this. I keep getting this error even though I've manually removed -Werror and replaced it with -Wno-error in all of the make files.

[ 52% 14718/28091] target  C++: hwcomp...ay/msm8994/libhwcomposer/hwc_utils.cpp
FAILED: out/target/product/angler/obj/SHARED_LIBRARIES/hwcomposer.msm8994_intermediates/hwc_utils.o 
/bin/bash -c "PWD=/proc/self/cwd prebuilts/misc/linux-x86/ccache/ccache prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-g++ -I hardware/qcom/display/msm8994/libhwcomposer/../libgralloc -I hardware/qcom/display/msm8994/libhwcomposer/../liboverlay -I hardware/qcom/display/msm8994/libhwcomposer/../libcopybit -I hardware/qcom/display/msm8994/libhwcomposer/../libqdutils -I hardware/qcom/display/msm8994/libhwcomposer/../libhwcomposer -I hardware/qcom/display/msm8994/libhwcomposer/../libhdmi -I hardware/qcom/display/msm8994/libhwcomposer/../libqservice -I ./external/skia/include/core -I ./external/skia/include/images -I hardware/qcom/display/msm8994/libhwcomposer -I out/target/product/angler/obj/SHARED_LIBRARIES/hwcomposer.msm8994_intermediates -I out/target/product/angler/gen/SHARED_LIBRARIES/hwcomposer.msm8994_intermediates -I libnativehelper/include_jni \$(cat out/target/product/angler/obj/SHARED_LIBRARIES/hwcomposer.msm8994_intermediates/import_includes)  -I system/core/include -I system/media/audio/include -I hardware/libhardware/include -I hardware/libhardware_legacy/include -I hardware/ril/include -I libnativehelper/include -I frameworks/native/include -I frameworks/native/opengl/include -I frameworks/av/include -isystem out/target/product/angler/obj/include -isystem device/huawei/angler/kernel-headers -isystem hardware/qcom/msm8994/kernel-headers -isystem bionic/libc/include -isystem bionic/libc/kernel/uapi -isystem bionic/libc/kernel/uapi/asm-arm64 -isystem bionic/libc/kernel/android/scsi -isystem bionic/libc/kernel/android/uapi -c  -Werror=implicit-function-declaration -DANDROID -fmessage-length=0 -W -Wall -Wno-unused -Winit-self -Wpointer-arith -no-canonical-prefixes -fno-canonical-system-headers -DNDEBUG -UDEBUG -fno-exceptions -Wno-multichar -O2 -g -fno-strict-aliasing -fdebug-prefix-map=/proc/self/cwd= -fdiagnostics-color -ffunction-sections -fdata-sections -fno-short-enums -funwind-tables -fstack-protector-strong -Wa,--noexecstack -D_FORTIFY_SOURCE=2 -Wstrict-aliasing=2 -Werror=return-type -Werror=non-virtual-dtor -Werror=address -Werror=sequence-point -Werror=date-time -Werror=format-security -mcpu=cortex-a53  -Wsign-promo -fvisibility-inlines-hidden  -std=gnu++11   -fno-rtti -DDEBUG_CALC_FPS -Wno-missing-field-initializers -Wconversion -Wall -Werror -D__ARM_HAVE_NEON -DVENUS_COLOR_FORMAT -DMDSS_TARGET -D__STDC_FORMAT_MACROS -DANDROID_JELLYBEAN_MR1=1 -DLOG_TAG=\\\"qdhwcomposer\\\" -std=c++11 -fPIC -D_USING_LIBCXX -Wno-attributes -DANDROID_STRICT   -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast  -MD -MF out/target/product/angler/obj/SHARED_LIBRARIES/hwcomposer.msm8994_intermediates/hwc_utils.d -o out/target/product/angler/obj/SHARED_LIBRARIES/hwcomposer.msm8994_intermediates/hwc_utils.o hardware/qcom/display/msm8994/libhwcomposer/hwc_utils.cpp"
In file included from frameworks/av/media/libmedia/include/media/IMediaPlayer.h:27:0,
                 from frameworks/av/media/libmedia/include/media/IMediaPlayerService.h:29,
                 from frameworks/av/media/libmedia/include/media/IMediaDeathNotifier.h:21,
                 from hardware/qcom/display/msm8994/libhwcomposer/hwc_qclient.h:37,
                 from hardware/qcom/display/msm8994/libhwcomposer/hwc_utils.cpp:41:
frameworks/av/include/media/VolumeShaper.h: In copy constructor 'android::media::VolumeShaper::Configuration::Configuration(const android::media::VolumeShaper::Configuration&)':
frameworks/av/include/media/VolumeShaper.h:135:18: error: base class 'class android::Parcelable' should be explicitly initialized in the copy constructor [-Werror=extra]
         explicit Configuration(const Configuration &configuration)
                  ^
cc1plus: all warnings being treated as errors
ninja: build stopped: subcommand failed.
16:22:13 ninja failed with: exit status 1

#### failed to build some targets (04:36 (mm:ss)) ####

Update: Fixed, I missed common.mk and It was still setting -Werror.

 

[Ololoev9999]

Hello guys!
I am building Pie rom and want to include some system accents to it.
I dont have sources of them but i have apks wich should be located in /vendor/overlay/*name*/*name*.apk
How can i include them to rom?

 

[DiamondJohn]

I have been looking at an init.*.rc file for my device (specifically init.qcom.rc on https://github.com/kyasu/android_device_samsung_ks01ltexx/blob/lineage-15.1/rootdir/etc/init.qcom.rc). One thing I have noticed is that it references many paths/files which do not exist.

The one which is confusing me the most, I have found on 3 other devices. the following is the excerpt for example (around line 110):

# DRK permission
    mkdir /efs/prov 0770 radio system
    chown radio system /efs/prov/libdevkm.lock
    chmod 0660 /efs/prov/libdevkm.lock

So, reading this to me it translates to (in English):

1. make the directory /efs/prov
2. change the owner of the file /efs/prov/libdevkm.lock
3. change the permission on the file /efs/prov/libdevkm.lock

However, logically to me :cyclops:, simply by creating the directory, it is assuming that the file "libdevkm.lock" magically appears in the newly created directory :silly: I have checked on a booted device, and this file does not exist. I could maybe understand if a service or another boot process creates the file, but assuming the file to exist a few micro seconds after creating the path seems a bit of a reach, And the booted device appears to agree with me; ie the file is not even there a boot completed. As I said, these same lines are in three other devices I checked.

Am I missing something?

 

[TimSchumi]

Friends,

I'm in a making of an application that has to be running on a custom rom (this projects is running for 1,5 years now and I am nearly finished). Basically I am creating a tablet that is meant to be used for one thing only and that's it (purpose made machine). Have nearly finished my app and have built my ROM with most of the modifications I needed (cm14.1).
Few things I cannot figure out.

The goal is to avoid the "give permission" pop-up window to appear at the first run of the app.

1.: Is it achievable to have the required permissions already given to my application? Can I set this somewhere in the source files?
2.: Alternatively can I give all the required permissions to every app somehow?
3.: Is the above goal is achieveable at all?

This tablet will be used in schools by mentally low-skilled people and cannot rely on them reading and giving the permissions at the first run. I also dont want their teachers to do this at the first time after the tablets are delivered. I would like to have a ROM that I flash and will have everything ready to go.

Can anyone help?

You might want to try and target an API level (with your app) that doesn't support runtime permissions. That way, Android should fall back to the old permissions-on-installation way of handling those things. Alternatively, try making it a system app (at build time) and sign it with the platform keys.

 

[RickySplashHD]

Hi,
Where can I obtain proprietary files for my Wiko View? I'm trying to compile a 9.0 AOSP-based ROM, but I can't find anything online.

Aaand sorry for the dumb question

 

[eccko]

Hi,
Where can I obtain proprietary files for my Wiko View? I'm trying to compile a 9.0 AOSP-based ROM, but I can't find anything online.

Aaand sorry for the dumb question

On github.

 

[RickySplashHD]

On github.

On GitHub there isn't nothing for my device. But there are 2 repos for another device, that for what I saw it's similar (or identical too) to mine. Tinno bought Wiko last year, so maybe they can be useful. Here are the links.

Device compared: https://www.devicespecifications.com/en/comparison/5e37d2e7f
Android device for similar device: https://github.com/TINNO-8937/android_device_micromax_hs2
Proprietary vendor for similar device:
https://github.com/TINNO-8937/proprietary_vendor_tinno

So can I use them for my device?

 

[eccko]

On GitHub there isn't nothing for my device. But there are 2 repos for another device, that for what I saw it's similar (or identical too) to mine. Tinno bought Wiko last year, so maybe they can be useful. Here are the links.

Device compared: https://www.devicespecifications.com/en/comparison/5e37d2e7f
Android device for similar device: https://github.com/TINNO-8937/android_device_micromax_hs2
Proprietary vendor for similar device:
https://github.com/TINNO-8937/proprietary_vendor_tinno

So can I use them for my device?

You can TRY. But always you can find any rom for this device Micromax Canvas Infinity and port them.

 

[RickySplashHD]

You can TRY. But always you can find any rom for this device Micromax Canvas Infinity and port them.

For the port: isn't port only possible between same version rom? ex. 7.1 to 7.1. What I am trying to achieve is to upgrade my device to 9.0. (From what I know)
For the compile: Now I only miss the kernel. Any advice? Do I need that for my device or the latest one?

 

[eccko]

For the port: isn't port only possible between same version rom? ex. 7.1 to 7.1. What I am trying to achieve is to upgrade my device to 9.0. (From what I know)
For the compile: Now I only miss the kernel. Any advice? Do I need that for my device or the latest one?

Fitrst question, Porting is only rom 6.0 to 6.0 not from 6.0 to 9.0.
Second question, I didin't find any kernel repositories. As you can see on XDA there is 0 roms for Micromax Canvas Infinity - https://xdaforums.com/t/micromax-canvas-infinity


Also you cannot use this propert vendor (https://github.com/TINNO-8937/proprietary_vendor_tinno), there is msm8937 and you have msm8917. Addidtional there is only branch cm-14.1 - android 7.1.2.
https://www.devicespecifications.com/en/comparison/5e37d2e7f

You have to find device with same Processor - msm8917 snapdragon 425 and for better SAME RESOLUTION and same GB of RAM. Then this maybe something we can do.

 

[RickySplashHD]

Fitrst question, Porting is only rom 6.0 to 6.0 not from 6.0 to 9.0.
Second question, I didin't find any kernel repositories. As you can see on XDA there is 0 roms for Micromax Canvas Infinity - https://xdaforums.com/t/micromax-canvas-infinity


Also you cannot use this propert vendor (https://github.com/TINNO-8937/proprietary_vendor_tinno), there is msm8937 and you have msm8917. Addidtional there is only branch cm-14.1 - android 7.1.2.
https://www.devicespecifications.com/en/comparison/5e37d2e7f

You have to find device with same Processor - msm8917 snapdragon 425 and for better SAME RESOLUTION and same GB of RAM. Then this maybe something we can do.

So the device tree is correct or I need to change that too? Oh man, this is more complicated that I thought! (and I like it )
Anyway, for vendor and kernel is there a way to "get them from my current rom"? Any other way is accepted too.

 

[eccko]

So the device tree is correct or I need to change that too? Oh man, this is more complicated that I thought! (and I like it )
Anyway, for vendor and kernel is there a way to "get them from my current rom"? Any other way is accepted too.

To make it easier, you just need to find a device that is similar or nearly identical to yours. There is no need to complicate matters, just find a simple exit.
I find a HUGE list of smartphones who using Snapdragon 425 (msm8917) I pretty sure, you there find a similar device to your - https://www.kimovil.com/en/list-smartphones-by-processor/qualcomm-snapdragon-425-msm8917

If you've already found a device, I'd be happy to help you with the ROM porting for your Wiko View.

 

[RickySplashHD]

To make it easier, you just need to find a device that is similar or nearly identical to yours. There is no need to complicate matters, just find a simple exit.
I find a HUGE list of smartphones who using Snapdragon 425 (msm8917) I pretty sure, you there find a similar device to your - https://www.kimovil.com/en/list-smartphones-by-processor/qualcomm-snapdragon-425-msm8917

If you've already found a device, I'd be happy to help you with the ROM porting for your Wiko View.

Oh yeah, thank you dude! Where can we talk?
I think the Xiaomi Redmi 5A can be a nice one to start with. It has got same Soc, but different RAM, and screen resolution. The reason I choosed this one is because someone already developed a 9.0 Rom (https://xdaforums.com/xiaomi-redmi-5a/development/rom-carbonbeta-cr-7-0-t3830374). I don't know if this can be useful.
The most similar to mine is the Huawei Y6 2018, with same Soc, RAM and screen resolution.
What should we use for porting? Thanks again for helping me.

 

[deve678]

Oh yeah, thank you dude! Where can we talk?
I think the Xiaomi Redmi 5A can be a nice one to start with. It has got same Soc, but different RAM, and screen resolution. The reason I choosed this one is because someone already developed a 9.0 Rom (https://xdaforums.com/xiaomi-redmi-5a/development/rom-carbonbeta-cr-7-0-t3830374). I don't know if this can be useful.
The most similar to mine is the Huawei Y6 2018, with same Soc, RAM and screen resolution.
What should we use for porting? Thanks again for helping me.

You can use Honor Y6 for porting as it is more similar to yours as you don't want to do complicated.