Android 6.0 marshmallow on DragonBoard 410c

cy_huang · February 20, 2017, 9:23am

Hi, All

Since the DragonBoard 410c is officially supported by Qualcomm,
will Qualcomm release the Android 6.0 codebase for DragonBoard 410c???

I have some features want to test, but it needs Android 6 .0 codebase.

I have checked the below site, it seems the 6.0 codebase for 8x16 is on-going.
https://www.codeaurora.org/xwiki/bin/QAEP/release

If anyone knows the information, please don’t hesitate to answer me.

vjanicki · February 20, 2017, 9:23am

Hi,

According to Qualcomm, Android M source would potentially be available by March 2016.

Regards,

Vicky Janicki

arielyitus · February 20, 2017, 9:25am

Hello,

Anyone knows if Android M is coming for the Dragon?

Thanks

smadger · February 20, 2017, 9:25am

Check the blog

rameshandroid99gmail · February 20, 2017, 9:26am

Hi All,

Refer below link for marshmallow porting

https://github.com/Linaro/documentation/wiki/DragonBoard%E2%84%A2-410c-RPB-AOSP-Build-Source-16.03

Regards
Ramesh

alanlissl · February 20, 2017, 9:26am

Hi Ramesh,

I have followed this link to download and build AOSP for dragonboard 410c. It could be downloaded and built sucessfully but there is an error about display as follows.

01-01 00:00:19.295 2202 2292 E GRALLOC-GBM: buffer 0x7fa6abbac0 usage = 00000900
01-01 00:00:19.296 2328 2348 E GRALLOC-GBM: handle: name=0 pfd=13
01-01 00:00:19.409 2202 2290 D GRALLOC-GBM: create BO, size=1920x1080, fmt=2, usage=4
01-01 00:00:19.980 2202 2202 E hwc-drm-generic-importer: could not create drm fb -22
01-01 00:00:19.980 2202 2202 E hwcomposer-drm: Failed to init composition from layer -22

dmesg will output the following error
msm 1a00000.qcom,mdss_mdp: unsupported pixel format: XB24

It seems that I could not build system.img correctly. Do you know how to fix it?

rameshandroid99gmail · February 20, 2017, 9:26am

HI Alan Li,

I am also facing display issue’s .In my case zygote and media,surface finger services are getting killed and keep on restarting.
Boot got strucked, it’s only display android text on the screen.I am debugging, Once i am done i will let you know.

Thanks
Ramesh

abdi · February 20, 2017, 9:26am

Hi All,

I have the same issue. E hwcomposer-drm: Failed to init composition from layer -22

Did anyone resolved this issue?

Thanks,
Kinka

jake-weinstein · February 20, 2017, 9:27am

Please refer to the following guide: https://developer.qualcomm.com/download/db410c/linux-android-software-build-and-installation-guide.pdf

Sync the LA.BR.1.2.7-01010-8x16.0-4 manifest

Use the following BSP: https://developer.qualcomm.com/download/db410c/android_board_support_package_vla.br_.1.2.7-01010-8x16.0-4.zip

arun8276 · February 20, 2017, 9:27am

Hello,

  I have downloaded the source from code aurora and the board support packages from qualcomm. After compilation of images and flashing, com.android.phone process fails. Below is a portion of my logs from logcat:-

01-01 00:11:31.524 3776 3776 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke interface method ‘int com.android.internal.telephony.IExtTelephony.getPrimaryStackPhoneId()’ on a null object reference
01-01 00:11:31.524 3776 3776 E AndroidRuntime: at com.android.services.telephony.TelecomAccountRegistry.setupAccounts(TelecomAccountRegistry.java:487)
01-01 00:11:31.524 3776 3776 E AndroidRuntime: at com.android.services.telephony.TelecomAccountRegistry.access$500(TelecomAccountRegistry.java:59)
01-01 00:11:31.524 3776 3776 E AndroidRuntime: at com.android.services.telephony.TelecomAccountRegistry$1.onSubscriptionsChanged(TelecomAccountRegistry.java:286)
01-01 00:11:31.524 3776 3776 E AndroidRuntime: at android.telephony.SubscriptionManager$OnSubscriptionsChangedListener$1.handleMessage(SubscriptionManager.java:364)
01-01 00:11:31.524 3776 3776 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
01-01 00:11:31.524 3776 3776 E AndroidRuntime: at android.os.Looper.loop(Looper.java:148)
01-01 00:11:31.524 3776 3776 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5417)
01-01 00:11:31.524 3776 3776 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
01-01 00:11:31.524 3776 3776 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
01-01 00:11:31.524 3776 3776 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
01-01 00:11:31.527 299 512 D PRDrmPlugIn: PRDrmPlugin::onTerminate, uniqueId = 4182
01-01 00:11:31.527 813 2758 W ActivityManager: Process com.android.phone has crashed too many times: killing!
01-01 00:11:31.530 300 300 I ExtendedExtractor: QTIParser is prefered
01-01 00:11:31.531 300 300 I ExtendedExtractor: ExtendedExtractor::create 0xaae0ecc8
01-01 00:11:31.531 300 300 I ExtendedExtractor: ExtendedExtractor::updateExtractor: Use default QTI parser
01-01 00:11:31.532 300 774 E MM_OSAL : FileSource::FileSource
01-01 00:11:31.532 300 774 E MM_OSAL : FileSource::FileSource m_bEveryThingOK 1
01-01 00:11:31.532 300 774 E MM_OSAL : MM_File_Create failed .Efs Error No -1 , File Name /data/mmosal_logmask.cfg , Mode 0
01-01 00:11:31.532 300 774 E MM_OSAL : Open or read fail on /data/mmosal_logmask.cfg. Possible permission denied issue. Looking for /data/misc/media/mmosal_logmask.cfg
01-01 00:11:31.532 300 774 E MM_OSAL : MM_File_Create failed .Efs Error No -1 , File Name /data/misc/media/mmosal_logmask.cfg , Mode 0
01-01 00:11:31.533 3776 3776 I Process : Sending signal. PID: 3776 SIG: 9

If this issue is regarding telephony services, is there a way to disable it or any suggestion regarding this issue ?

Thanks,
Arun

halfbit · February 20, 2017, 9:27am

+1 We’re also experiencing this problem. Wondering how to remove the phone component from Android… since we don’t need it. thanks.

arun8276 · February 20, 2017, 9:27am

Hello,

I have made the following changes to disable phone component and it works properly:-

in build/target/product/telephony.mk
PRODUCT_PACKAGES :=
#CarrierConfig
#Dialer
#CallLogBackup
#rild

          PRODUCT_COPY_FILES := \

in build/target/product/core.mk
comment Telecom and Teleservice

in device/qcom/msm8916_64/system.prop
change ro.telephony.default_network=0
telephony.lteOnCdmaDevice=0

in vendor/qcom/proprietary/common/config/device-vendor.mk
#PRODUCT_PACKAGES += $(QTI_TELEPHONY_FWK)
#PRODUCT_PACKAGES += $(TELEPHONY_APPS)
#PRODUCT_PACKAGES += $(QTI_TELEPHONY_FWK)
#PRODUCT_PACKAGES += $(QTI_TELEPHONY_RES)
#PRODUCT_PACKAGES_DEBUG += $(TELEPHONY_APPS_DBG)

Let me know in case of further issues.
Thanks

halfbit · February 20, 2017, 9:27am

Thanks Arun, this seems to have done the trick. I think I still see errors in logcat but I’m going to ignore it. But your instructions are great, I think I can figure out how to do it myself for other modules now. Thanks a lot!

dodoamuro · February 20, 2017, 9:27am

Hi All,

If I need phone component, how could I fixed this issue?
I am trying to porting RIL with Quectel EC20 modem, but phone always died, OS can’t recognize SIM and can’t use phone function.
Could anyone know how to fixed it?

Thanks so much.
Johnny

jake-weinstein · February 20, 2017, 9:27am

Thank you, Arun for posting a workaround. Instead of disabling RIL entirely, the error can be fixed with a commit from CyanogenMod, which causes the telephony service not to fail if Qualcomm’s proprietary extended telephony framework is not present: https://github.com/CyanogenMod/android_packages_services_Telephony/commit/9827225f3a4cb25060a72fe0abd27a69906c27bf

dodoamuro · February 20, 2017, 9:28am

Hi Jake,
Thanks for the fixed.
I tried to download pure Android M from google.
But it seems the code is different with CyanogenMod.
And I try to replace TeleService from google pure Android M, the phone still died and didn’t work.
If I just need 3G/LTE data connection but no need dial/message or other phone function.
Do I have any other method to do that?
Because it seems Qualcomm remove phone components from APQ8016 BSP, could I replace Android OS to pure Android which I download from google and build by myself?

Thanks.
Best regards,
Johnny

rehilderman · February 20, 2017, 9:28am

Hi Jake,
Maybe this post is old, but I just tried following the procedure above for Android 6.0.

Please refer to the following guide: https://developer.qualcomm.com/download/db410c/linux-android-software-build-and-installation-guide.pdf

Sync the LA.BR.1.2.7-01010-8×16.0-4 manifest

Use the following BSP: https://developer.qualcomm.com/download/db410c/android_board_support_package_vla.br_.1.2.7-01010-8×16.0-4.zip

Unfortunately I am stuck when running ./DB410c_build.sh. Get this error:

Applying patches …
applying patches on ./bootable/bootloader/lk …
./DB410c_build.sh: line 44: cd: /home/osboxes/dragonboard/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8X16.0_6.0.1_Marsh_Mallo_P2/./bootable/bootloader/lk: No such file or directory.

When I list the contents of this directory… it is empty and same with the parent: /home/osboxes/dragonboard/linux_android_board_support_package_vla.br.1.2.7-01010-8x16.0-4/APQ8016_410C_LA.BR.1.2.7-01010-8X16.0_6.0.1_Marsh_Mallo_P2

Any help would be appreciated.

Thanks, Randy

jake-weinstein · February 20, 2017, 9:28am

Hi Johnny,

The BSP is only meant for use with Qualcomm’s fork of Android at the CodeAurora forums and may have issues with AOSP. Please try with CAF and see if that resolves your issue.

jake-weinstein · February 20, 2017, 9:28am

Hi Randy,

Are you sure that the platform synced correctly? Can you see the rest of the build environment?

rehilderman · February 20, 2017, 9:28am

Hi,
The repo sync failed the first time due to out of memory. I increased the memory for the virtual box image, and then tried again. still out of memory, so I created a swap partition and then the repo sync was successful. Is it possible the original failure would have caused this?

Anyways, maybe I should just clear everything and start over.

Thanks, Randy