Android 8 evk_7ulp-user not supported ?

[zbigniewmazur]

On Android 8.1.0 for imx 7ulp there is no lunch target "evk_7ulp-user". There is only userdebug and eng. When I select myself by:

lunch evk_7ulp-user

and build it then userdata partition exists but is not accessible by package manager and application later during first boot.

I have to change build flag 'ro.secure=0' and 'ro.debuggable=1' in buid/core/main.mk in order to problem to disappear, but then device is not fully secure and not ready to release.

Does NXP supports 'evk_7ulp-user' builds ? or only 'eng' and 'userdebug' ?

[zbigniewmazur]

Thank you, You have few untrue statements in your reply. I'll correct it so readers won't get mislead.

1. O8.1.0_1.4.0_ANDROID_SOURCE_7ULP_GA is for imx 7ulp it is written in the release notes and it works on imx7 , please check release notes doc on NXP page for the above version.

2. "Installs modules tagged with user."

There is no 'user' tag for LOCAL_MODULE_TAGS it's only (test, debug, eng, optional)

3. ro.sercure = 1 in both userdebug and user
ro.adb.sercure = 0 is userdebug but in user ro.adb.secure = 1

3. NXP didn't add lunch combo evk_7ulp-user in imx7/vendorsetup.sh and in other SoC mk's for user option there is only:
evk_7ulp-eng, and evk_7ulp-userdebug. Hence it's unclear if 'lunch evk-7ulp-user' produces stable output.

The question I have really is this:
Does NXP test evk_7ulp-user builds?

[weidong_sun]

Hello Zbigniew Mazur,

>>You have few untrue statements in your reply. I'll correct it so readers won't get mislead.

Thank you for your kindly correction!  I didn't pay attention to the version.

>>Does NXP test evk_7ulp-user builds?

I confirmed it with android team: Yes, and android supports "evk_7ulp-user" build.

Hope above information can help you!

Have a nice day!

BR,

Weidong

[weidong_sun]

Hi Mazur ,

    Android 8.1 doesn't support I.MX7ULP, starting from android 9.0.0_2.2.0，i.mx7ulp is supported by android.

    As for user mode, described in android user's guide, see below, please!

The main differences among the three modes are as follows:
• eng (development configuration with additional debugging tools)
   • Installs modules tagged with: eng and/or debug.
   • Installs modules according to the product definition files, in addition to tagged modules.
   • ro.secure=0
   • ro.debuggable=1

   • ro.kernel.android.checkjni=1
   • adb is enabled by default.
• user (limited access, suitable for production)
   • Installs modules tagged with user.
   • Installs modules according to the product definition files, in addition to tagged modules.
   • ro.secure=1
   • ro.debuggable=0
   • adb is disabled by default.
• userdebug (like user but with root access and debuggability, preferred for debugging)
   • Installs modules tagged with debug.
   • ro.debuggable=1
   • adb is enabled by default.

So above 3 modes are all supported.

Have a nice day!

Weidong