May 2019 - Celadon - Ml01.01.Org

Re: [01.org Celadon] Unable to boot into launcher on stable branch using 4K monitor + custom build

by Fan, Yugang

For “Can I just disable them in device/intel/project-celadon/cel_apl/device.mk ?”, GFX team can’t answer this as it related to whole system integration I think. For APL NUC 4K support, we didn’t find 4K EPIC. And APL NUC hardware EDS shows HDIM only support max resolution 4K 3840x2160 30fps, and we also known that 4K also met some flicker issues due to display buffer side limitation when enabling some GFX feature, e.g. RBC. APL IVI may can boot to 4K 3840x2160 60fps, but we don’t know if there are some other potential issue. For different result of APL IVI and APL tablet of 4K 3840x2160 60fps, I got info that we haven’t verified APL tablet for long time, there should has some diffs, but not sure if we need continue investigate it as no 4k EPIC found. Above are all I know, so possible way is: we start to verify 4K 3840x2160 30fps(but not sure it is make sense to use 30 fps for 4k, or force using 1080P 60 fps for big resolution) for APL if we need support 4K, and figure out if we need limit the max resolution to 4K 3840x2160 30fps in somewhere, e.g. some config files/vbt. Best regards, Yugang From: Dominik Louven [mailto:dlouven@videro.com] Sent: Thursday, May 9, 2019 11:58 AM To: Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> Cc: celadon(a)lists.01.org<mailto:celadon@lists.01.org> Subject: Re: [01.org Celadon] Unable to boot into launcher on stable branch using 4K monitor + custom build Hello everyone, Any news on this ? Best regards, Dominik Louven On 6. May 2019, at 12:12, Dominik Louven <dlouven(a)videro.com<mailto:dlouven@videro.com>> wrote: Hi Swaroop, Thank you in advance. To be a little more specific. I would like to exclude all car components from the cel_apl build. Can I just disable them in device/intel/project-celadon/cel_apl/device.mk ? Please let me know if you find a way to exclude the car components from the compilation , because my NUC is not embedded in a car =) Best regards, Dominik Louven On 6. May 2019, at 12:09, Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> wrote: Hello Dominik Please give me some time , I will check and let you know after taking a clean tablet build from GitHub Regards Swaroop From: Dominik Louven [mailto:dlouven@videro.com] Sent: Monday, May 6, 2019 3:26 PM To: Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> Cc: celadon(a)lists.01.org<mailto:celadon@lists.01.org> Subject: Re: [01.org<http://01.org> Celadon] Unable to boot into launcher on stable branch using 4K monitor + custom build Hello Swaroop, It works fine now, I can boot into OS with celadon_apl-userdebug. Is it possible to disable the car launcher and car applications in the build ? Best regards, Dominik Louven On 3. May 2019, at 12:24, Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> wrote: Hello Dominik Celadon is for tablet and cel-apl is for APL NUC IVI Regards Swaroop From: Dominik Louven [mailto:dlouven@videro.com] Sent: Friday, May 3, 2019 3:08 PM To: Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> Cc: celadon(a)lists.01.org<mailto:celadon@lists.01.org> Subject: Re: [01.org<http://01.org/> Celadon] Unable to boot into launcher on stable branch using 4K monitor + custom build Hello Swaroop, I used : lunch celadon-userdebug Maybe that’s the issue here. I will try again with your steps. What’s the different between the celadon and the cel-apl build ? Best regards, Dominik Louven On 3. May 2019, at 11:35, Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> wrote: Hello Dominic I used a local build based on WW13 BIOS VERSION --> AYAPLCEL.86A.0059.2018.1226.1422 We used below steps to compile • source build/envsetup.sh • lunch cel-apl-userdebug • make SPARSE_IMG=true flashfiles -j4 Regards Swaroop From: Dominik Louven [mailto:dlouven@videro.com] Sent: Friday, May 3, 2019 3:02 PM To: Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> Cc: celadon(a)lists.01.org<mailto:celadon@lists.01.org> Subject: Re: [01.org<http://01.org/> Celadon] Unable to boot into launcher on stable branch using 4K monitor + custom build Hello Swaroop, That is weird. Did you use the same manifest ww201913 ? What BIOS version is your NUC running on and do I have set specific settings in the BIOS ? Did you compile the OS with different steps ? Best regards, Dominik Louven On 3. May 2019, at 11:29, Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> wrote: Hello Dominik, When I connect my NUC6CAYH (APL) to an 4K Display (View Sonic) There was no issue for us in booting to home screen Regards Swaroop From: Dominik Louven [mailto:dlouven@videro.com] Sent: Friday, May 3, 2019 2:42 PM To: Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> Cc: celadon(a)lists.01.org<mailto:celadon@lists.01.org> Subject: Re: [01.org<http://01.org/> Celadon] Unable to boot into launcher on stable branch using 4K monitor + custom build Hello Swaroop, Thanks a lot. If you need any more information please let me know. Best regards, Dominik Louven On 3. May 2019, at 11:08, Balan, Swaroop <swaroop.balan(a)intel.com<mailto:swaroop.balan@intel.com>> wrote: Hello Dominik We are checking at our end , Will update shortly Regards Swaroop From: Celadon [mailto:celadon-bounces@lists.01.org] On Behalf Of Dominik Louven Sent: Friday, May 3, 2019 1:49 PM To: celadon(a)lists.01.org<mailto:celadon@lists.01.org> Subject: [01.org<http://01.org/> Celadon] Unable to boot into launcher on stable branch using 4K monitor + custom build Hello everybody, I have checked out the latest stable branch ww201913.xml . When I connect my NUC6CAYH (APL) to an 4K Display (resolution 3840x2160) I am unable to boot into the launcher. The NUC hangs in android boot screen. What can I do ? Please find logs below : logcat https://pastebin.com/d8eGtPha dumpsys https://pastebin.com/UjrxC5PW bugreport https://drive.google.com/open?id=1oy9uQqqMpG_95Vsm4sUpH6pRjqnscPhN I am running the latest BIOS on my NUC and the os was compiled using : source build/envsetup.sh lunch celadon-userdebug make SPARSE_IMG=true flashfiles -j4 Best regards, Dominik Louven -- Celadon mailing list Celadon(a)lists.01.org<mailto:Celadon@lists.01.org> https://lists.01.org/mailman/listinfo/celadon

3 months

8
9
0 / 0

thermald spamming

by Tapani Pälli

Hi; On my KBL NUC device, thermald is continuously restarting itself causing a lot of 'spam output' to the logcat. This is annoying as it is hard to read the proper log output and it also affects many benchmark results because of additional CPU overhead. Is there easy way to just disable thermald? Or maybe implement some threshold that if it restarts 10 times then it would give up? Thanks; // Tapani

7 months

4
4
0 / 0

Re: [01.org Celadon] How to generate OTA update

by Regnier, Philippe

Hi Dominik, Can you please check and confirm the command line you are using? Instead of: make dist it should be something like that: make SPARSE_IMG=true dist -j8 I suspect that you might have forgotten the parameter SPARSE_IMG=true in your command line, which might explains why you get error in __init__ function of sparse_img.py. Regards. Philippe REGNIER -----Original Message----- From: Celadon [mailto:celadon-bounces@lists.01.org] On Behalf Of celadon-request(a)lists.01.org Sent: Tuesday, May 28, 2019 3:00 AM To: celadon(a)lists.01.org Subject: Celadon Digest, Vol 13, Issue 22 Send Celadon mailing list submissions to celadon(a)lists.01.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.01.org/mailman/listinfo/celadon or, via email, send a message with subject or body 'help' to celadon-request(a)lists.01.org You can reach the person managing the list at celadon-owner(a)lists.01.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Celadon digest..." Today's Topics: 1. How to generate OTA update (Dominik Louven) ---------------------------------------------------------------------- Message: 1 Date: Mon, 27 May 2019 08:54:16 +0200 From: Dominik Louven <dlouven(a)videro.com> To: celadon(a)lists.01.org Subject: [01.org Celadon] How to generate OTA update Message-ID: <16FD8A70-9284-48AC-A320-9D2196FB52EC(a)videro.com> Content-Type: text/plain; charset="utf-8" Hi all, How do I create an OTA update ? ?make dist? produces the following error: system.img already exists, no need to overwrite... vendor.img already exists, no need to overwrite... vbmeta.img already exists, no need to overwrite... Traceback (most recent call last): File "build/make/tools/releasetools/add_img_to_target_files", line 824, in <module> main(sys.argv[1:]) File "build/make/tools/releasetools/add_img_to_target_files", line 818, in main AddImagesToTargetFiles(args[0]) File "build/make/tools/releasetools/add_img_to_target_files", line 773, in AddImagesToTargetFiles AddCareMapTxtForAbOta(output_zip, ab_partitions, partitions) File "build/make/tools/releasetools/add_img_to_target_files", line 563, in AddCareMapTxtForAbOta care_map_list += GetCareMap(partition, image_path) File "build/make/tools/releasetools/add_img_to_target_files", line 111, in GetCareMap simg = sparse_img.SparseImage(imgname) File "/home/ubuntu/Android/celadon/build/make/tools/releasetools/sparse_img.py", line 52, in __init__ raise ValueError("Magic should be 0xED26FF3A but is 0x%08X" % (magic,)) ValueError: Magic should be 0xED26FF3A but is 0x00000000 ninja: build stopped: subcommand failed. 01:36:13 ninja failed with: exit status 1 #### failed to build some targets (14:12 (mm:ss)) #### Best regards, Dominik Louven

8 months, 1 week

2
9
0 / 0

UPCore Plus boot stuck on android logo with 2019ww13 stable build

by hpo14

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&utm_camp...> 不含病毒。www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_camp...> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

8 months, 3 weeks

2
3
0 / 0

Celadon/Android on other x86 platforms

by Krishna Kaza

Hi, We are investigating how Android works/behaves on various x86 chips for our work loads. The celadon project website only lists 2 reference platforms. Are these the only ones the Android build would work or is it possible that they will also work on other platforms like the Compute Card that has a Core-M3?. http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpN... thanks, krishna

8 months, 3 weeks

3
4
0 / 0

GFX stack releaseis ready on celadon https://github.com/projectceladon -- ww22

by Cao, Jenny Q

FYI, The GFX stack release (ww22) is ready on celadon github/projectceladon/ Patch List Mesa Rebase to Mesa 18.3.5 to 18.3.6 Hwc(13 patches): HWC: 13 patches 4c1177670d69f65bcd287f355851d154c52a9be2 Check if hwc is drm master by default in initialization 130d65a01afbbe95227b1c6c840bfa89755dbff6 The buffer interlace info should change to frame by frame 9bc722fd0d7ecd8a990f17234c0059bb181ddf43 Fix a misstike when LogicalDisplaymanager do present 8802564ba2366ebddc8b0e7dbf43f51ce92d38d8 Build libhwcservice as static library d008bd2e394673b49e70d908bae3e53b6c2f9886 Fix the wrong method name in compiling error 7f2dcd2c1bbbe1f45490fa7617005a78c0559703 Ensure LogicalDisplay called LogicalDisplayManager::Present() 377abb00e330e6c98fd4856c8855ffc37d1e7ea9 Allow drm commit by default adf0c36a8d43c0162f10f6d70c9c0bcacf88f6f8 Added the Panorama dynamic turn on/off feature. e9ecf2d61ee8c463ce75d72dc98f8b9b40e53341 Update GPUDevice thread for DRM-master setting/dropping cc914c3e16e82fefb7c459e68a119d1aff666075 Fix a null pointer bug after hwctrace enabled. 76e33c9ce88aee255e60828089022f8b3a3d3f6b fix build error f0a8cf3bb16fccd836e8d971c1013fc2d6472ff2 Add nullpoint checking for GetBuffer invoking. 0b4757767f147cf84011083e38a0d36cf567a323 Fix create/destroy VDS issue Thanks Jenny

9 months

1
0
0 / 0

How to generate OTA update

by Dominik Louven

Hi all, How do I create an OTA update ? “make dist” produces the following error: system.img already exists, no need to overwrite... vendor.img already exists, no need to overwrite... vbmeta.img already exists, no need to overwrite... Traceback (most recent call last): File "build/make/tools/releasetools/add_img_to_target_files", line 824, in <module> main(sys.argv[1:]) File "build/make/tools/releasetools/add_img_to_target_files", line 818, in main AddImagesToTargetFiles(args[0]) File "build/make/tools/releasetools/add_img_to_target_files", line 773, in AddImagesToTargetFiles AddCareMapTxtForAbOta(output_zip, ab_partitions, partitions) File "build/make/tools/releasetools/add_img_to_target_files", line 563, in AddCareMapTxtForAbOta care_map_list += GetCareMap(partition, image_path) File "build/make/tools/releasetools/add_img_to_target_files", line 111, in GetCareMap simg = sparse_img.SparseImage(imgname) File "/home/ubuntu/Android/celadon/build/make/tools/releasetools/sparse_img.py", line 52, in __init__ raise ValueError("Magic should be 0xED26FF3A but is 0x%08X" % (magic,)) ValueError: Magic should be 0xED26FF3A but is 0x00000000 ninja: build stopped: subcommand failed. 01:36:13 ninja failed with: exit status 1 #### failed to build some targets (14:12 (mm:ss)) #### Best regards, Dominik Louven

9 months, 1 week

1
0
0 / 0

Re: [01.org Celadon] UnsatisfiedLinkError: dlopen failed: cannot locate symbol "MFXClose" - Celadon PMR ww201913.xml Branch

by Chen, Tianmi

Hi Sathish, The dlopen issue may be caused by the mismatch between msdk omx plugin and msdk os libraries. It is recommended to use mediasdk opensource from celadon code tree. Can we know where you get the msdk source code? Is it from https://github.com/projectceladon/MediaSDK or https://github.com/Intel-Media-SDK/MediaSDK ? There are some difference between them. If the second one is being used, there might be the mismatch issue. Thanks, Regards, Tianmi -----Original Message----- From: Celadon [mailto:celadon-bounces@lists.01.org] On Behalf Of celadon-request(a)lists.01.org Sent: Saturday, April 27, 2019 3:00 AM To: celadon(a)lists.01.org Subject: Celadon Digest, Vol 12, Issue 7 Send Celadon mailing list submissions to celadon(a)lists.01.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.01.org/mailman/listinfo/celadon or, via email, send a message with subject or body 'help' to celadon-request(a)lists.01.org You can reach the person managing the list at celadon-owner(a)lists.01.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Celadon digest..." Today's Topics: 1. UnsatisfiedLinkError: dlopen failed: cannot locate symbol "MFXClose" - Celadon PMR ww201913.xml Branch (Sathish) ---------------------------------------------------------------------- Message: 1 Date: Fri, 26 Apr 2019 23:28:58 +0530 From: Sathish <satish.chevuru(a)gmail.com> To: celadon(a)lists.01.org Subject: [01.org Celadon] UnsatisfiedLinkError: dlopen failed: cannot locate symbol "MFXClose" - Celadon PMR ww201913.xml Branch Message-ID: <CACzLWDL70AXKtt2fH+FBSj+mqXFTDtbPOg-nScQO1cbzL-N_sQ(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi, I am trying to use Intel Media SDK for video processing and I could not move further because of the below error. The same was working with the celadon OMR1 older release. There the app was able to load the libraries from the /system/lib64 and /vendor/lib64. But on PMR1 stable branch, I am seeing the below error. I bundling the dependant libraries inside app lib directory , but same behaviour. Manifest branch: refs/tags/android-9.0.0_r18 Manifest merge branch: refs/heads/master Manifest groups: all,-notdefault ---------------------------- The command line program that uses the same Media SDK code is working fine, But when I use the code in a Application , I am not getting this error. I moved all the libs from /system/lib64 and /vendor/lib64 to app library path , but still seeing this error. Any suggestions/inputs is appreciated. 04-26 17:47:20.821 29559 29559 E AndroidRuntime: FATAL EXCEPTION: main 04-26 17:47:20.821 29559 29559 E AndroidRuntime: Process: com.tely.device.application.ng, PID: 29559 04-26 17:47:20.821 29559 29559 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "MFXClose" referenced by "/data/app/com.tely.device.application.ng-E5zwZhHUurFlC_HEw_EmVA==/lib/x86_64/libmfx_omx_components_hw.so"... 04-26 17:47:20.821 29559 29559 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:1016) 04-26 17:47:20.821 29559 29559 E AndroidRuntime: at java.lang.System.loadLibrary(System.java:1669) 04-26 17:47:20.821 29559 29559 E AndroidRuntime: at com.tely.media.core.JniLoader.loadJniLibraries(JniLoader.java:31) 04-26 17:47:20.821 29559 29559 E AndroidRuntime: at com.tely.media.video.NewTelyCameraPreview.<clinit>(NewTelyCameraPreview.java:517) 04-26 17:47:20.821 29559 29559 E AndroidRuntime: at java.lang.Class.classForName(Native Method) 04-26 17:47:20.821 29559 29559 E AndroidRuntime: at java.lang.Class.forName(Class.java:453) 04-26 17:47:20.821 29559 29559 E AndroidRuntime: at java.lang.Class.forName(Class.java:378) 04-26 17:47:20.821 29559 29559 E AndroidRuntime: at com.tely.device.application.ng.mediahal.TelyXLCameraPreview.Init(TelyXLCameraPreview.java:44) 04-26 17:47:20.821 29559 29559 E AndroidRuntime: at com.tely.device.application.ng.mediahal.TelyXLCameraPreview.<init>(TelyXLCameraPreview.java:77) 04-26 17:47:20.821 29559 29559 E AndroidRuntime: at com.tely.device.application.ng.mediahal.TelyCameraManager.getCamera(TelyCameraManager.java:43) 04-26 17:47:20.821 29559 29559 E AndroidRuntime: at com.tely.device.application.ng.setup.frag.HomeFrag.createCameraXL(HomeFrag.java:1992) 04-26 17:47:20.821 29559 29559 E AndroidRuntime: at com.tely.device.application.ng.setup.frag.HomeFrag$3.run(HomeFrag.java:1627) 04-26 17:47:20.821 29559 29559 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:873) 04-26 17:47:20.821 29559 29559 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99) Thanks, Sathish

9 months, 1 week

3
6
0 / 0

Use USB serial port to get log

by Tan, Ming

Dear all: In general, we use serial port log to debug some boot issue. But if the device has not native serial port, such as APL NUC, then we have to use the USB serial port convertor. However, you can get log only after the kernel load the USB serial port convertor driver. If the kernel crash before load the driver, then you have to check log in screen. In the cel_apl lunch target, default use ttyUSB0, and the other lunch targets are use ttyS0. Now support FTDI or PL2303 chip based USB serial port convertor. You can enable others as you needed. Some USB serial convertor: 1. FTDI: https://item.jd.com/10415462066.html 2. PL2303: https://item.jd.com/1309051.html BR/Tan Ming. Software Engineer, IAGS/SSP/Android Mobile: +86 13651977713.

9 months, 2 weeks

3
2
0 / 0

Unable to boot into launcher on stable branch using 4K monitor + custom build

by Dominik Louven

Hello everybody, I have checked out the latest stable branch ww201913.xml . When I connect my NUC6CAYH (APL) to an 4K Display (resolution 3840x2160) I am unable to boot into the launcher. The NUC hangs in android boot screen. What can I do ? Please find logs below : logcat https://pastebin.com/d8eGtPha <https://pastebin.com/d8eGtPha> dumpsys https://pastebin.com/UjrxC5PW <https://pastebin.com/UjrxC5PW> bugreport https://drive.google.com/open?id=1oy9uQqqMpG_95Vsm4sUpH6pRjqnscPhN <https://drive.google.com/open?id=1oy9uQqqMpG_95Vsm4sUpH6pRjqnscPhN> I am running the latest BIOS on my NUC and the os was compiled using : source build/envsetup.sh lunch celadon-userdebug make SPARSE_IMG=true flashfiles -j4 Best regards, Dominik Louven

9 months, 3 weeks

3
12
0 / 0

2020

2019

2018

Celadon May 2019