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
1 year
Mediaplayer skips roughly first second if video has audio track
by Dominik Louven
Hi all,
I am experiencing a really weird problem, I am trying to play a video file with the android MediaPlayer instance.
When I play some specific videos the Mediaplayer skips about 1 second of video footage, other videos with audio track work fine though.
If I remove the audio track with ffmpeg the video plays fine.
I have attached both the logcat output as well as the ffmpeg info output.
I can see some Audio related logs , the most confusing one is
createTrack_l(): mismatch between requested flags (00000008) and output flags (00000000)
Does anyone has any idea what I am doing wrong here ?
MediaPlayer mMediaPlayer = new MediaPlayer();
mMediaPlayer.setOnCompletionListener(this);
mMediaPlayer.setOnErrorListener(this);
mMediaPlayer.setOnSeekCompleteListener(this);
if (mFile != null && mFile.exists()) {
try {
// Try the Default Method of Creating the MediaPlayer
Uri mVideoUri = Uri.fromFile(getFile());
mMediaPlayer.setDataSource(getContext(), mVideoUri);
mMediaPlayer.prepare();
} catch (Exception e) {
Logger.error(e.getMessage());
}
Best regards,
Dominik Louven
1 year, 3 months
Unresponsive USB port on NUC7i7BNH - Celadon
by Sathish
Hi,
I installed celadon-eng build on NUC7i7BNH. I am using this for a video
conferencing application.
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=9
TARGET_PRODUCT=celadon
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_ARCH=x86_64
TARGET_ARCH_VARIANT=x86_64
The front USB is non responsive for either Mouse, Keyboard, Camera or to
Jabra Speaker.
I am seeing this on the latest build , this was fine with omr1 version.
I am seeing the same issue on cel_apl build as well.
[ro.vendor.build.fingerprint]:
[cel_apl/cel_apl/cel_apl:9/PPR2.181005.003.A1/sathish06162135:eng/test-keys]
I am wondering , whether any of you have seen this issue during your
installs. Do i need to use celadon certified NUC hardware ?
Appreciate your inputs.
Thanks,
Sathish
1 year, 3 months
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
1 year, 4 months
Enable/Disable UAC3
by Ming-Hong Wu
Hi,
I checked with the tutorial,
https://01.org/projectceladon/documentation/tutorials/enabling-uac3
I've questions as below after reading that,
1. Is UAC3 enabled by default (said master codes)?
2. If I would like to make it disabled, what is the suggested way?
2.1 from something like menuconfig to NOT build the features from Kernel?
2.2 after booting into Celadon, any entry to disable this feature?
--
Sincerely,
minhong
1 year, 4 months
Re: [01.org Celadon] "not accessible for the namespace" error while loading an "so" file
by Zhang, Yanmin
Can you try user-debug?
From: Tan, Ming
Sent: Monday, July 29, 2019 10:26 AM
To: Zhang, Yanmin <yanmin.zhang(a)intel.com>; Gaurav Gupta <gaurav(a)trainingdata.io>; Sathish <satish.chevuru(a)gmail.com>
Cc: Chen, Tianmi <tianmi.chen(a)intel.com>; Cao, Jenny Q <jenny.q.cao(a)intel.com>; Lin, Johnson <johnson.lin(a)intel.com>
Subject: RE: [01.org Celadon] "not accessible for the namespace" error while loading an "so" file
Are you using KBL NUC 7i7BNH?
It does not support USB device mode, then does not support fastboot.
BR/Tan Ming.
From: Zhang, Yanmin
Sent: Monday, July 29, 2019 8:22 AM
To: Gaurav Gupta <gaurav(a)trainingdata.io<mailto:gaurav@trainingdata.io>>; Sathish <satish.chevuru(a)gmail.com<mailto:satish.chevuru@gmail.com>>
Cc: Chen, Tianmi <tianmi.chen(a)intel.com<mailto:tianmi.chen@intel.com>>; Cao, Jenny Q <jenny.q.cao(a)intel.com<mailto:jenny.q.cao@intel.com>>; Lin, Johnson <johnson.lin(a)intel.com<mailto:johnson.lin@intel.com>>; Tan, Ming <ming.tan(a)intel.com<mailto:ming.tan@intel.com>>
Subject: RE: [01.org Celadon] "not accessible for the namespace" error while loading an "so" file
I use user-debug at lunch before compiling.
+Ming.
From: Gaurav Gupta [mailto:gaurav@trainingdata.io]
Sent: Sunday, July 28, 2019 12:02 AM
To: Sathish <satish.chevuru(a)gmail.com<mailto:satish.chevuru@gmail.com>>
Cc: Zhang, Yanmin <yanmin.zhang(a)intel.com<mailto:yanmin.zhang@intel.com>>; Chen, Tianmi <tianmi.chen(a)intel.com<mailto:tianmi.chen@intel.com>>; Cao, Jenny Q <jenny.q.cao(a)intel.com<mailto:jenny.q.cao@intel.com>>; Lin, Johnson <johnson.lin(a)intel.com<mailto:johnson.lin@intel.com>>
Subject: Re: [01.org Celadon] "not accessible for the namespace" error while loading an "so" file
Hi Yanmin,
My experience with disable-verity on NUC6i5SYK was similar.
After disable-verity showed success status, there was an error "Fastboot mode failed: Unsupported"
On Sat, Jul 27, 2019 at 8:22 AM Sathish <satish.chevuru(a)gmail.com<mailto:satish.chevuru@gmail.com>> wrote:
I have tried power off and on again and it still says "Fastboot mode failed".
I have recorded a video of my steps I executed and attached the drive link.
I started with clean install and proceeded with the steps.
1) Installed the Celadon Image using startup.nsh and booted into the android home
2) Plugged in the USB and executed unlock commands
3) It went into recovery mode and I selected factory data reset.
4) After booting up , I connected to the device and executed disable-verity and reboot.
5) It gave me the "Fastboot mode failed: Unsupported"
6) I restarted the device ( power off and on ) and again it tried booting and got to "Fastboot mode failed: Unsupported"
I am using the celadon eng build.
[https://ssl.gstatic.com/docs/doclist/images/icon_10_generic_list.png] NUC-Unlock-DisableVerity-Sequence.mp4<https://drive.google.com/file/d/1WVkSUtTSh4pPd4-HsfSCEdFpemBz4IGA/view?us...>
Thanks,
Sathish
On Thu, Jul 25, 2019 at 6:01 AM Zhang, Yanmin <yanmin.zhang(a)intel.com<mailto:yanmin.zhang@intel.com>> wrote:
Can you try to power off and on the NUC? I also use NUC7i7BNH.
From: Sathish [mailto:satish.chevuru@gmail.com<mailto:satish.chevuru@gmail.com>]
Sent: Thursday, July 25, 2019 2:50 AM
To: Zhang, Yanmin <yanmin.zhang(a)intel.com<mailto:yanmin.zhang@intel.com>>
Cc: Chen, Tianmi <tianmi.chen(a)intel.com<mailto:tianmi.chen@intel.com>>; Cao, Jenny Q <jenny.q.cao(a)intel.com<mailto:jenny.q.cao@intel.com>>; Lin, Johnson <johnson.lin(a)intel.com<mailto:johnson.lin@intel.com>>; Gaurav Gupta <gaurav(a)trainingdata.io<mailto:gaurav@trainingdata.io>>
Subject: Re: [01.org<http://01.org> Celadon] "not accessible for the namespace" error while loading an "so" file
Yanmin,
Unlocked worked, disable verity worked , but the adb reboot after it failed.
sathish@ubuntuIA:~/TelyCode_IA/logs/stability/july22$ adb disable-verity
Successfully disabled verity
Now reboot your device for settings to take effect
sathish@ubuntuIA:~/TelyCode_IA/logs/stability/july22$ adb reboot
I see the below error now and the boot stopped.
Fastboot mode failed: Unsupported.
I am using NUC7i7BNH , Is this because of the NUC type.
Thanks,
Sathish
On Wed, Jul 24, 2019 at 11:01 AM Zhang, Yanmin <yanmin.zhang(a)intel.com<mailto:yanmin.zhang@intel.com>> wrote:
Plug the install usb key, enter UEFI shell, and run:
Installer.efi flashing unlock
Installer.efi continue
Then, it would be unlocked.
From: Sathish [mailto:satish.chevuru@gmail.com<mailto:satish.chevuru@gmail.com>]
Sent: Wednesday, July 24, 2019 1:28 PM
To: Zhang, Yanmin <yanmin.zhang(a)intel.com<mailto:yanmin.zhang@intel.com>>
Cc: celadon(a)lists.01.org<mailto:celadon@lists.01.org>; Chen, Tianmi <tianmi.chen(a)intel.com<mailto:tianmi.chen@intel.com>>; Cao, Jenny Q <jenny.q.cao(a)intel.com<mailto:jenny.q.cao@intel.com>>; Lin, Johnson <johnson.lin(a)intel.com<mailto:johnson.lin@intel.com>>
Subject: Re: [01.org<http://01.org> Celadon] "not accessible for the namespace" error while loading an "so" file
It says device unlocked.
sathish@ubuntuIA:~/TelyCode_IA/logs/stability/july22$ adb disable-verity
Device is locked. Please unlock the device first
The device is already enabled for developer options and OEM is also unlocked.
Thanks,
Sathish
On Wed, Jul 24, 2019 at 9:24 AM Zhang, Yanmin <yanmin.zhang(a)intel.com<mailto:yanmin.zhang@intel.com>> wrote:
adb disable-verity
adb reboot
It might boot to recovery mode, then you need choose reset factory
adb remount
Then, push the file and change anything.
From: Sathish [mailto:satish.chevuru@gmail.com<mailto:satish.chevuru@gmail.com>]
Sent: Wednesday, July 24, 2019 11:50 AM
To: Zhang, Yanmin <yanmin.zhang(a)intel.com<mailto:yanmin.zhang@intel.com>>
Cc: celadon(a)lists.01.org<mailto:celadon@lists.01.org>; Chen, Tianmi <tianmi.chen(a)intel.com<mailto:tianmi.chen@intel.com>>; Cao, Jenny Q <jenny.q.cao(a)intel.com<mailto:jenny.q.cao@intel.com>>; Lin, Johnson <johnson.lin(a)intel.com<mailto:johnson.lin@intel.com>>
Subject: Re: [01.org<http://01.org> Celadon] "not accessible for the namespace" error while loading an "so" file
Yanmin,
I tried this and it says "/vendor/etc" as a read only file system and failed to copy the file.
sathish@ubuntuIA:~/TelyCode_IA/logs/stability/july22$ adb push public.libraries.txt /vendor/etc
adb: error: failed to copy 'public.libraries.txt' to '/vendor/etc/public.libraries.txt': remote couldn't create file: Read-only file system
public.libraries.txt: 0 files pushed. 0.0 MB/s (51 bytes in 0.004s)
celadon:/vendor/etc # touch test.txt
touch: 'test.txt': Read-only file system
1|celadon:/vendor/etc #
I earlier bundled all the dependant libraries in the application lib, based on the suggestion from android help link you mentioned above.
Thanks,
Sathish
On Tue, Jul 23, 2019 at 12:49 PM Zhang, Yanmin <yanmin.zhang(a)intel.com<mailto:yanmin.zhang@intel.com>> wrote:
Sathish,
Since Android N, apk need call official API. All access to private libraries will be blocked.
https://developer.android.com/about/versions/nougat/android-7.0-changes
You can work around it by:
1) Add the shared object file names into a config file:
ymzhang@ymzhang:~/android/data/logs/KBL$ cat public.libraries.txt
i965_drv_video.so
libva.so
libdrm.so
libgmm_umd.so
ymzhang@ymzhang:~/android/data/logs/KBL$ adb push public.libraries.txt /vendor/etc/
2) After booting, run: adb shell setenforce 0
You app can start to a red window on my KBL.
Yanmin
From: Celadon [mailto:celadon-bounces@lists.01.org<mailto:celadon-bounces@lists.01.org>] On Behalf Of Zhang, Yanmin
Sent: Wednesday, July 17, 2019 8:44 AM
To: Sathish <satish.chevuru(a)gmail.com<mailto:satish.chevuru@gmail.com>>; celadon(a)lists.01.org<mailto:celadon@lists.01.org>
Cc: Chen, Tianmi <tianmi.chen(a)intel.com<mailto:tianmi.chen@intel.com>>; Xiao, Jin <jin.xiao(a)intel.com<mailto:jin.xiao@intel.com>>
Subject: Re: [01.org<http://01.org> Celadon] "not accessible for the namespace" error while loading an "so" file
+Jin, Tianmi.
I remember you raised the similar issue 2 months ago. It seems not resolved.
From: Celadon [mailto:celadon-bounces@lists.01.org] On Behalf Of Sathish
Sent: Wednesday, July 17, 2019 1:50 AM
To: celadon(a)lists.01.org<mailto:celadon@lists.01.org>
Subject: [01.org<http://01.org> Celadon] "not accessible for the namespace" error while loading an "so" file
Hi,
I am getting the below error while deploying an application no NUC7i7BNH with celadon PMR.
The library is available in the given path, but unable to load the library and reporting not accessible for the namespace error.
E libva : dlopen of /vendor/lib64//i965_drv_video.so failed: dlopen failed: library "/vendor/lib64//i965_drv_video.so" needed or dlopened by "/data/app/com.tely.device.application.ng-AHAaUmOTFd5Uvd1ECUGs6A==/lib/x86_64/libva.so" is not accessible for the namespace "classloader-namespace"
E libva : dlopen of /system/lib64/i965_drv_video.so failed: dlopen failed: library "/system/lib64/i965_drv_video.so" needed or dlopened by "/data/app/com.tely.device.application.ng-AHAaUmOTFd5Uvd1ECUGs6A==/lib/x86_64/libva.so" is not accessible for the namespace "classloader-namespace"
Appreciate your inputs on this.
Thanks,
Sathish
--
Gaurav,
Co-founder, TrainingData.io
+1-917-386-3396
228 Webster Street,
Palo Alto,
CA, 94301
1 year, 4 months
Supported NUC devices
by Dominik Louven
Hi,
Does Celadon run on any NUCs available or only on the two devices listed on the website ?
Best regards,
Dominik Louven
1 year, 4 months
"not accessible for the namespace" error while loading an "so" file
by Sathish
Hi,
I am getting the below error while deploying an application no NUC7i7BNH
with celadon PMR.
The library is available in the given path, but unable to load the library
and reporting not accessible for the namespace error.
E libva : dlopen of /vendor/lib64//i965_drv_video.so failed: dlopen
failed: library "/vendor/lib64//i965_drv_video.so" needed or dlopened by
"/data/app/com.tely.device.application.ng-AHAaUmOTFd5Uvd1ECUGs6A==/lib/x86_64/libva.so"
is not accessible for the namespace "classloader-namespace"
E libva : dlopen of /system/lib64/i965_drv_video.so failed: dlopen
failed: library "/system/lib64/i965_drv_video.so" needed or dlopened by
"/data/app/com.tely.device.application.ng-AHAaUmOTFd5Uvd1ECUGs6A==/lib/x86_64/libva.so"
is not accessible for the namespace "classloader-namespace"
Appreciate your inputs on this.
Thanks,
Sathish
1 year, 4 months
Re: [01.org Celadon] Question about installing with kernelflinger executable
by Haichen Ren
Thanks for the feedback Yogesh.
Yes, it works well off my NUC7i5.
And we would also like to test it off NUC8i5. What is the timeline to have NUC8i5 support celadon?
Thanks!
> On Jun 27, 2019, at 11:16 PM, Marathe, Yogesh <yogesh.marathe(a)intel.com> wrote:
>
> Hi Haichen,
>
> I would let boot experts comment but Celadon support for this WHL is work in progress and it may come soon. In core, currently we support KBL (NUC7i5).
>
> Regards,
> Yogesh.
> <>
> <>From: Celadon [mailto:celadon-bounces@lists.01.org <mailto:celadon-bounces@lists.01.org>] On Behalf Of Haichen Ren
> Sent: Friday, June 28, 2019 10:50 AM
> To: celadon(a)lists.01.org <mailto:celadon@lists.01.org>
> Subject: [01.org <http://01.org/> Celadon] Question about installing with kernelflinger executable
>
> Hi there,
>
> I built from source (android pie) for installing with kernelflinger executable. I was able to install on an Intel NUC7i5 system and tested well.
> But today I was trying to install on another Intel NUC8i5 system with the same kernelflinger executable, and failed on flashing the system at the step of running "installer --batch installer.cmd".
>
> The error is "Failed to reinstall block io interface on System disk: access Denied".
> This NUC8i5 system has a Ubuntu 16.04 installed before.
> Can you please advice? Thanks!
>
> <image002.png>
>
> Regards.
1 year, 5 months
