7:14 p.m.
Hi Everyone
I downloaded celadon codebase with manifest 2019ww13.xml.
Using celadon-eng as my target and make kernelflinger build (*1).
Then flashed to my device UPCore Plus (*2).
Below table is the boot result of my UP Core Plus and compare board
----------------------------------------------------------------------------------------------
Image Version | Kernel Ver | Android Ver | UP Core Plus |
RTC-1010
----------------------------------------------------------------------------------------------
Celadon 2018ww32 | 4.14.59 | Android 8.1 | Boot to home | Boot
to home
Celadon 2018ww52 | 4.19.x | Android 9 | stuck on android logo | Boot
to home
Celadon 2019ww13 | 4.19.19 | Android 9 | stuck on android logo | Boot
to home
----------------------------------------------------------------------------------------------
I have check the log, found something.
1. /data/media partition seems not mount on UP Core Plus
-- UP Core Plus ------------------------------
console: # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 3.3G 1.3G 2.0G 39% /
tmpfs 895M 456K 895M 1% /dev
tmpfs 895M 0 895M 0% /mnt
/dev/block/dm-1 1.7G 726M 0.9G 42% /vendor
/dev/block/mmcblk0p12 3.7M 32K 3.7M 1% /vendor/oem_config
/dev/block/mmcblk0p13 5.6M 32K 5.6M 1% /vendor/factory
/dev/block/mmcblk0p19 18G 80M 18G 1% /data
-- RTC-1010 ------------------------------
console:/ # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 3.3G 1.3G 2.0G 39% /
tmpfs 1.8G 448K 1.8G 1% /dev
tmpfs 1.8G 0 1.8G 0% /mnt
/dev/block/dm-1 1.7G 726M 0.9G 42% /vendor
/dev/block/mmcblk0p12 3.7M 32K 3.7M 1% /vendor/oem_config
/dev/block/mmcblk0p13 5.6M 32K 5.6M 1% /vendor/factory
/dev/block/mmcblk0p19 46G 141M 46G 1% /data
/data/media 46G 141M 46G 1%
/mnt/runtime/default/emulated
2. lots of log about
write xxx to /dev/cpuset/camera-daemon/tasks: No such file or directory
write xxx to /dev/cpuset/foreground/tasks: No such file or directory
3. zygote does not start successfully, always killed with unknown reason.
4. Below log frequenlty shows and never stop on both UP Core Plus and
RTC-1010 logs.
init: cannot setexeccon('u:r:hdcpd:s0') for hdcpd: Invalid argumen
Should this happened ?
I can't find any sepolicy te or file_contexts related to "hdcpd"
Attached logs: (dmesg, df, logcat of "EXT|fsck|vold" )
https://pastebin.com/8mjtnLx4 -- 2019ww13_up_core_plus_stuck_on_android_logo
https://pastebin.com/yeDTDkr9 -- 2019ww13_rtc1010_boot_to_home
If need more information, please let me know.
-------------------------
**1: build cmd
$ . build/env.sh
$ lunch celadon-eng
$ make -j32 flashfiles
**2: flash steps
1. extract celadon-flashfiles-eng.hpo14.zip to usb flash drive
2. boot to EFI shell
3. run startup.nsh to flash
**3 Device Hardward information
UP Core Plus
- Apollo Lake
- Atom x5-E3930 / Sandisk 32G eMMC (SDINBDA4-32G) / 2G RAM
- BIOS Ver of UPCore Plus: UPCPSM10
- link:
https://up-shop.org/945-thickbox_default/up-core-plus.jpg
RTC-1010
- Apollo Lake
- Pentium N4200 / Sandisk 64G eMMC (SDINBDA4-64G) / 4G RAM
- link:
https://www.aaeon.com/en/p/10-inches-rugged-tablet-computers-rtc-1010
--
Sincerely
hpo14
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&...
不含病毒。www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&...
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
