Hi, there,
First of all, I am working on omr1 branch, and I have compiled both images
for Grub based and Kernel Flinger.
My first question is to confirm correctness of the output image as I cannot
boot up.
1. grub based, celadon.img, around 919MB
2. Kernrl Flinger, celadon-flashfiles-user.zip, about 593MB
I tried to use Rufus with celadon.img and try to boot it up firstly by
VirtualBox, is that a possible try?
Also, can someone help me to identify the image size is correct or not as I
saw the Kernel Flinger is about 14GB in the mailing list, this worries me
if my image is correct or not.
Sincerely,
minhong
--
Sincerely,
minhong

Hi,
I have refer to the tutorial to add Intel Movidius NCS (Neural Compute Stick) and it works well.
Due to NCS will be discontinued, and next generation is Intel NCS2(Neural Compute Stick 2).
But NCSDK does not support NCS2, only OpenVINO can do.
Will Celadon support NCS2 + OpenVINO integration for AI application? Or any reference guide for this?
Regards,
Menghui Wu
===================================================================================================================================
This email and any attachments to it contain confidential information and are intended solely for the use of the individual to whom it is addressed.If you are not the intended recipient or receive it accidentally, please immediately notify the sender by e-mail and delete the message and any attachments from your computer system, and destroy all hard copies. If any, please be advised that any unauthorized disclosure, copying, distribution or any action taken or omitted in reliance on this, is illegal and prohibited. Furthermore, any views or opinions expressed are solely those of the author and do not represent those of ASUSTeK. Thank you for your cooperation.
===================================================================================================================================

I have a tablet with a touch penal and hdmi external output.
When I only use the touch panel, everything is fine
But
But when I plug in the external hdmi panel, the hdmi panel can't be displayed,
and the touch function will be wrong (do not match the touch panel)
I think the error is in android.hardware.graphics.composer
This error did not occur in android x86 oreo (Not imported android.hardware.graphics.composer)
My touch panel information
Resolution: 800x1280
Interface type: mipi
Touch type: capacitor
從 Windows 10 的郵件<https://go.microsoft.com/fwlink/?LinkId=550986>傳送

Hello everybody,
I’m currently facing an issue again I thought was fixed a while back.
My NUC running celadon is stuck in the boot screen (android logo) when it’s connected to an 4K display. However, when I re-flash the image the first boot does not have this issue, but after a reboot it’s broken.
Interestingly enough I can start apps from command line and everything works as expected, it seems like the “overlay” with the boot logo is not correctly destoyed.
When I connect a keyboard I can “Alt-Tab” out of the boot screen.
I’ll attach my logs.
Best regards and thanks in advance,
Dominik Louven

Hello;
I'm building Celadon for development purposes. I'd like to 'unlock' the
device and so far I've been removing 'flashing lock' from installer.cmd
script to achieve this. However, now I noticed this does not work
anymore. If I remove 'flashing lock' line, the device won't boot at all.
Is this a bug somewhere or is there another way to unlock?
Thanks;
// Tapani