Hello everybody,
Is it possible the change the default display orientation from landscape to portrait in celadon_ivi? The goal is to make the celadon_ivi to display the bootanimation pictures and the systemui/apps in portrait mode.
I have tried it in several ways, but without success:
1) I have set at build time in system props the ro.sf.hwrotation=90. It had no effect
2) I have set in BoardConfig.mk the SF_PRIMARY_DISPLAY_ORIENTATION := 90. It had no effect, too.
I was able to change the orientation to portrait mode only via "adb shell settings put system user_rotation 1" command, but this setting is ignored by the boot animation.
Best regards,
Gigi

Hi Valerio,
Sorry for the inconvenience, open JIRA "Bug FOUND On" issue is fixed, it was backend IT maintenance issue. You can report Bug/Feature with same link below.
Regards,
Yogesh.
From: Valerio.Pilo(a)tomtom.com <Valerio.Pilo(a)tomtom.com>
Sent: Thursday, April 16, 2020 2:12 PM
To: Marathe, Yogesh <yogesh.marathe(a)intel.com>; Palli, Tapani <tapani.palli(a)intel.com>; celadon(a)lists.01.org; Huang, Yuanjun <yuanjun.huang(a)intel.com>; Jiang, Fei <fei.jiang(a)intel.com>
Subject: Re: [01.org Celadon] Re: CIV installation script broken on Ubuntu 20.04, etc
Hello Yogesh, my answers are also below:
________________________________
From: Marathe, Yogesh <yogesh.marathe(a)intel.com<mailto:yogesh.marathe@intel.com>>
Sent: Wednesday, April 15, 2020 17:10
To: Palli, Tapani <tapani.palli(a)intel.com<mailto:tapani.palli@intel.com>>; Valerio Pilo <Valerio.Pilo(a)tomtom.com<mailto:Valerio.Pilo@tomtom.com>>; celadon(a)lists.01.org<mailto:celadon@lists.01.org> <celadon(a)lists.01.org<mailto:celadon@lists.01.org>>; Huang, Yuanjun <yuanjun.huang(a)intel.com<mailto:yuanjun.huang@intel.com>>; Jiang, Fei <fei.jiang(a)intel.com<mailto:fei.jiang@intel.com>>
Subject: RE: [01.org Celadon] Re: CIV installation script broken on Ubuntu 20.04, etc
> > Contrary to what the documentation says (as stated here
> > <https://01.org/projectceladon/documentation/getting-started/on-vm>
> > "Any later OS version should also work"), the installation scripts do
> > not work properly on Ubuntu 20.04.
>
> Right, IMO our documentation is a bit too optimistic here. Google talks
> about 14.04 in their AOSP build environment setup documentation:
>
> https://source.android.com/setup/build/initializing
We need to this a documentation bug, currently support only Ubuntu 18.04 and
move to later Ubuntu is under discussion. BTW, we also use guest kernel 4.19 with
supported version of Ubuntu. LTS move to 5.x for Celadon guest kernel is WIP as we
speak and this shall be available soon.
so expectation should be, Ubuntu Host kernel 5.3.x, Celadon Guest kernel 4.19
for CIV_01.20.01.12_A10
Can you please confirm your guest kernel version?
[VALERIO] The guest has the original kernel from CIV_01.20.01.12_A10, uname -a states:
"Linux localhost 4.19.107-PKT-190618T011631Z-04723-g053f6d279f12 #1 SMP PREEMPT Sun Mar 29 10:51:19 IST 2020 x86_64"
But I was talking about the host kernel, which is indeed 5.3 in Ubuntu 18.04.4 (the latest).
> >
> > I also have a few questions for you, if you don't mind:
> >
> > 1. Will you provide a Celadon IVI target for CIV ? Or if an Android
> > Auto target or mode is already available, how to enable it?
We intend to use caas as single target for multiple usecases. If the target worked
with 18.04 what exactly are you looking from separate IVI target? Is it just IVI UI,
or any other services specifically? If you can list it, we can file a feature request
on your behalf and start evaluating it.
You can also file it here, When you log it with Type as Feature.
https://01.org/projectceladon/community#report-a-bug-or-issue
[VALERIO] I am unable to create issues of any kind, even filling in every single available field I get a Jira error: "Bug FOUND On: Bug FOUND On is required." which prevents me from creating it. This happens from both the Create Issue button and from the dedicated issue creation page
> > 2. Is it, by chance, a planned feature to allow mirroring the screen
> > DPI info from the host into the Android guest?
Do you mean change in resolution/DPI on host to reflect in guest? Need to
check at our end, if not supported, we can take file this request as well.
+Yuanjun, Fei, for comments, if any.
[VALERIO] I mean that the resolution and DPI of the screen of the host doesn't seem to be applied to the guest when booting the guest. I did not try changing displays in the host, but I do not expect Android resolution changes.
The guest screen contents are much bigger than they are when running the same CAAS release zip as a guest vs. on bare metal.
It's a difference like ldpi vs hdpi:
as a guest -> https://01.org/projectceladon/sites/default/files/_images/caas-qemu-locks...
as bare metal -> https://imgur.com/pFBr8hb
> > 3. Wifi is broken for me (clean Ubuntu 18.04.4 install on a NUC7i5BNH,
> > Wifi working in the host, using latest release CIV_01.20.01.12_A10).
> > I attached the logcat. Is there anything I am missing or that is not
> > stated in the documentation?
This could still be kernel, pulling from release notes.
Component Results Comments
Wi-Fi OK Host wifi is switched to Android UI in QEMU
BT OK Bluetooth is working
This is tested and working with Ubuntu 18.04 + 4.19 guest kernel at our
end on NUC7i5DNHE. Suggesting you to confirm this combination.
Additionally, I see these commands to toggle WiFi
sudo -E ./start_android_qcow2.sh --wifi-passthrough
(To get WIFI control in Android UI)
and
sudo -E ./start_android_qcow2.sh
(To get WIFI control in HOST side)
Im not sure if you tried this already.
[VALERIO] I probably didn't use the --wifi-passthrough option! My bad.
I am currently trying caas on bare metal so at the moment I cannot confirm, but I will open a detailed bug if I can reproduce it with the option. Thanks!
> >
> > Thanks in advance,
> >
> > Cheers
> >
> > - Valerio
> >
> >
> > *> Valerio Pilo**/*PU IVI
> Amsterdam*/* valerio.pilo(a)tomtom.com*/*<mailto:valerio.pilo@tomtom.com*/*> +31
> > (0) 20 7575 218 Amsterdam ODE */*www.tomtom.com
> >
> > **
> >
> > --
> > Celadon mailing list -- celadon(a)lists.01.org<mailto:celadon@lists.01.org> To unsubscribe send an
> > email to celadon-leave(a)lists.01.org<mailto:celadon-leave@lists.01.org>
> >
> --
> Celadon mailing list -- celadon(a)lists.01.org<mailto:celadon@lists.01.org> To unsubscribe send an email to
> celadon-leave(a)lists.01.org<mailto:celadon-leave@lists.01.org>

On 4/14/20 8:37 PM, Valerio Pilo wrote:
> Hello Celadon developers,
>
> I have been following up on using CIV instead of bare metal, and it is
> already quite promising! Thank you very much for all your work 🙂
>
> Contrary to what the documentation says (as stated here
> <https://01.org/projectceladon/documentation/getting-started/on-vm> "Any
> later OS version should also work"), the installation scripts do not
> work properly on Ubuntu 20.04.
Right, IMO our documentation is a bit too optimistic here. Google talks
about 14.04 in their AOSP build environment setup documentation:
https://source.android.com/setup/build/initializing
> They rely on a differently named package ("libusb-1.0.0-dev" is named
> "libusb-1-0-0-dev" in Ubuntu 20.04, and "python-dev" is now
> "python2-dev") and there's some other issue with compilation of ovmf
> (compilation fails due to a missing file, I didn't investigate).
> Additionally, the scripts do not terminate on error, leading to the
> assumption that installation somehow succeeded. You could at least add
> "set -eux" at the beginning to block the script on errors.
>
> I am now using Ubuntu 18.04.4 (where it all worked perfectly) but it
> being the new LTS, I think this will be a problem!
>
> I also have a few questions for you, if you don't mind:
>
> 1. Will you provide a Celadon IVI target for CIV ? Or if an Android
> Auto target or mode is already available, how to enable it?
> 2. Is it, by chance, a planned feature to allow mirroring the screen
> DPI info from the host into the Android guest?
> 3. Wifi is broken for me (clean Ubuntu 18.04.4 install on a NUC7i5BNH,
> Wifi working in the host, using latest release CIV_01.20.01.12_A10).
> I attached the logcat. Is there anything I am missing or that is not
> stated in the documentation?
>
> Thanks in advance,
>
> Cheers
>
> - Valerio
>
>
> *> Valerio Pilo**/*PU IVI Amsterdam*/* valerio.pilo(a)tomtom.com*/* +31
> (0) 20 7575 218 Amsterdam ODE */*www.tomtom.com
>
> **
>
> --
> Celadon mailing list -- celadon(a)lists.01.org
> To unsubscribe send an email to celadon-leave(a)lists.01.org
>

Hello Celadon developers,
I have been following up on using CIV instead of bare metal, and it is already quite promising! Thank you very much for all your work 🙂
Contrary to what the documentation says (as stated here<https://01.org/projectceladon/documentation/getting-started/on-vm> "Any later OS version should also work"), the installation scripts do not work properly on Ubuntu 20.04.
They rely on a differently named package ("libusb-1.0.0-dev" is named "libusb-1-0-0-dev" in Ubuntu 20.04, and "python-dev" is now "python2-dev") and there's some other issue with compilation of ovmf (compilation fails due to a missing file, I didn't investigate).
Additionally, the scripts do not terminate on error, leading to the assumption that installation somehow succeeded. You could at least add "set -eux" at the beginning to block the script on errors.
I am now using Ubuntu 18.04.4 (where it all worked perfectly) but it being the new LTS, I think this will be a problem!
I also have a few questions for you, if you don't mind:
1. Will you provide a Celadon IVI target for CIV ? Or if an Android Auto target or mode is already available, how to enable it?
2. Is it, by chance, a planned feature to allow mirroring the screen DPI info from the host into the Android guest?
3. Wifi is broken for me (clean Ubuntu 18.04.4 install on a NUC7i5BNH, Wifi working in the host, using latest release CIV_01.20.01.12_A10). I attached the logcat. Is there anything I am missing or that is not stated in the documentation?
Thanks in advance,
Cheers
- Valerio
> Valerio Pilo / PU IVI Amsterdam / valerio.pilo(a)tomtom.com / +31 (0) 20 7575 218 Amsterdam ODE / www.tomtom.com

Hi,
I downloaded a pre-built binary from github for NUC7 CIV 01.20.01.12 A10
and booted the NUC with the same. The Android image came up, but the image
is missing a few .apk. The steps i used to boot are as follows:
1. $sudo ./start_flash_usb.sh caas-flashfiles-eng.build.zip
2. $sudo ./start_android_qcow2.sh
I re-booted into Native Android, please advise how to get the various .apk
so that i can run a few tests. Thank you in advance.
Regards
Sateesh