Not seeing Android Logo with imx6dl custom with android_p9.0.0_2.2.0

[chpub70]

Hi NXP,

I am using a android_p9.0.0_2.2.0 pre-built image, but I rebuilt the kernel + device tree, uboot for our custom board. The custom board is currently using kernel 4.9.11 Debian9. The code is porting from kernel 4.9.11. The custom board has 2 display 1368x768 and 800x480. 

When bootup, I can see 1 penguin and debug message dump to the display. The debug message is the same as the one in COM 1 port. 

I attach ps command, dmesg  and uboot log for your reference.

Regards,

Pun

[chpub70]

Hi NXP,

I am using an imx6dl 512MB memory custom board.

I have rebuilt the system. Attach is the dmesg and logcat log. 

I did not see all previous error, however I saw surfaceflinger error message. 

I did not see surfaceflinger error with the built image without adding my code and configuration.

Best Regards,

Pun 

[Zhiming_Liu]

Hi chee,

zygote' action=onrestart (<Service 'surfaceflinger' onrestart>:1) took 149ms and succeeded
[ 65.058596] init: Service 'zygote' (pid 523) received signal 9
[ 65.065712] init: Command 'write /sys/power/state on' action=onrestart (<Service 'zygote' onrestart>:2) took 0ms and failed: Unable to write to file '/sys/power/state': Unable to write file contents: Invalid argument

In your dmesg android try to write to file '/sys/power/state' but always failed ,so you can't see android MainActivity.I think zygote need power state to create the main android activty,however you remove the pmic from tthe dts.So you can boot normal in debain but not in android.

Best Regards,

Zhiming

[chpub70]

Hi Zhiming,

I have replacing the PMIC with a dummy regulator as you see in the dts. Is this ok ?

I did

cat /sys/power/state
freeze standby mem

could you help me how to resolve "Unable to write to file '/sys/power/state': Unable to write file contents: Invalid argument" ? For example to add this into kernel ?

Best Regards,

Pun

[chpub70]

Hi Zhiming,

During the build, I have GPU error, is this ok ?

[151/1003] including external/drm_gralloc/Android.mk ...
external/drm_gralloc/Android.mk:43: warning: invalid GPU drivers: vivante
[205/1003] including external/mesa3d/Android.mk ...
external/mesa3d/Android.mk:53: warning: invalid GPU drivers: vivante

[chpub70]

Hi Zhiming,

My custom board does not have these key, I am checking with H/W engineer what these pad is used or not. Do you think these button will cause some issue ?

gpio-keys {
compatible = "gpio-keys";
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_gpio_keys>;

power {
label = "Power Button";
gpios = <&gpio3 29 GPIO_ACTIVE_LOW>;
wakeup-source;
linux,code = <KEY_POWER>;
};

volume-up {
label = "Volume Up";
gpios = <&gpio1 4 GPIO_ACTIVE_LOW>;
linux,code = <KEY_VOLUMEUP>;
};

volume-down {
label = "Volume Down";
gpios = <&gpio1 5 GPIO_ACTIVE_LOW>;
linux,code = <KEY_VOLUMEDOWN>;
};
};

[Zhiming_Liu]

Hi,

The "Unable to write to file '/sys/power/state': Unable to write file contents: Invalid argument" happened in android offical framework layer. It is used in android system/core/rootdir/init.rc. 

# Allow system processes to read / write power state.
chown system system /sys/power/state
chown system system /sys/power/wakeup_count
chmod 0660 /sys/power/state

When android system init, android uses init.cpp to phrase init.rc. And zygote use system/core/rootdir/init.zygote32/64.rc "onrestart write /sys/power/state on" to start service. You can try to remove these command .If it can not solve the problem ,i am sorry that you may ask google how to change the google source code.

[Zhiming_Liu]

Dear  Chee Huey Pun

There are lots of messages like Abort message: 'Error creating cache dir /data/dalvik-cache/arm : No such file or directory' in uboot log.You changed uboot and kernel config, this may lead to some libs missing in rootfs . You can try to rebuild the whole  Android source code including rootfs.

Best regards,

Zhiming

[chpub70]

Hi,

How to do clean build ?

Do it like the steps below:

cd android_build

source build/envsetup.sh

make clean

lunch sabresd_6dq-userdebug
make -j4 2>&1 | tee build-log.txt