bout the error between tablet and external penal(celadon android O)
by MR. Children
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>傳送
8 months
Re: [01.org Celadon] MediaSDK OMX license
by Xu, Guangxin
HI Cyan,
Sorry for late, legal things always tedious.
We have upload our license file at https://github.com/projectceladon/mediasdk_release/blob/master/PV%20Intel...
Please have a look, and give us some feedback.
thanks
> -----Original Message-----
> From: Kasatkina, Olga A
> Sent: Monday, November 26, 2018 11:26 PM
> To: Cyan Dro <cyandroi(a)gmail.com>; Xu, Guangxin <guangxin.xu(a)intel.com>
> Cc: celadon(a)lists.01.org; Sidorov, Sergey <sergey.sidorov(a)intel.com>
> Subject: RE: [01.org Celadon] MediaSDK OMX license
>
> Hi Cyan,
> Related to license, we plan to update the license file by the EOW WW48.
> Activity to open source OpenMAX plug-ins is still planned for end of this year.
>
> ---
> Thanks & Regards,
> Olga Kasatkina
>
> -----Original Message-----
> From: Cyan Dro [mailto:cyandroi@gmail.com]
> Sent: Monday, November 26, 2018 6:02 PM
> To: Xu, Guangxin <guangxin.xu(a)intel.com>
> Cc: celadon(a)lists.01.org; Kasatkina, Olga A <olga.a.kasatkina(a)intel.com>;
> Sidorov, Sergey <sergey.sidorov(a)intel.com>
> Subject: Re: [01.org Celadon] MediaSDK OMX license
>
> Hi,
>
> thanks for keeping me updated! Any news on the license?
>
> Since it is just little more than a month until end of this year, I would also
> appreciate if you could share if the activity to cleanup/open-source is still
> planned for end of this year or if it is going to be delayed.
>
> Thanks,
> Cyan
>
> On Mon, Nov 12, 2018 at 6:46 AM Xu, Guangxin <guangxin.xu(a)intel.com>
> wrote:
> >
> > Sorry, we still working on the license thing.
> > We need update the old license, let us wait one week more.
> >
> > thanks
> >
> > > -----Original Message-----
> > > From: Xu, Guangxin
> > > Sent: Monday, October 29, 2018 1:32 PM
> > > To: Cyan Dro <cyandroi(a)gmail.com>
> > > Subject: FW: [01.org Celadon] MediaSDK OMX license
> > >
> > > Still waiting feedback from internal. Need more time. Hope we can
> > > give you some update at end of this week.
> > > Thanks.
> > >
> > > > -----Original Message-----
> > > > From: Celadon [mailto:celadon-bounces@lists.01.org] On Behalf Of
> > > > Cyan Dro
> > > > Sent: Sunday, October 21, 2018 4:16 AM
> > > > To: celadon(a)lists.01.org
> > > > Subject: [01.org Celadon] MediaSDK OMX license
> > > >
> > > > Hi,
> > > >
> > > > while going through the Project Celadon repositories I noticed
> > > > that https://github.com/projectceladon/mediasdk_release contains
> > > > proprietary binaries without any license. It seems like MediaSDK
> > > > itself is open-source, but the OMX implementation is still
> > > > proprietary. Without any license that at very least allows
> > > > redistribution, I'm unable to build on Project Celadon for my project.
> > > > Could you clarify the licensing situation for these binaries?
> > > >
> > > > By the way, it's a pity that these are only released as binaries,
> > > > given that Project Celadon is an effort to build an *open-source*
> > > > software reference stack for the Intel architecture. I'm guessing
> > > > there are licensing issues that make it difficult to open-source
> > > > these components? Are there still plans to open-source it eventually?
> > > > Ideally, I'd like to build on a fully open-source stack for my
> > > > project (excluding firmware).
> > > >
> > > > Thanks in advance,
> > > > Cyan
> > > > --
> > > > Celadon mailing list
> > > > Celadon(a)lists.01.org
> > > > https://lists.01.org/mailman/listinfo/celadon
10 months
[CELADON] Android PMR0 Official APL_NUC and KBL_COMMERCIAL_NUC 2018_WW51 Release
by Balan, Swaroop
[cid:image001.png@01CFE4A4.BAC02DC0]
Android PMR0 CELADON 2018_WW51 release
[cid:image008.png@01CF54D4.99DD97B0]
December 28th, 2018 - Celadon team announces [APL-NUC(Model: NUC6CAYH)] & [COMMERCIAL-KBL_NUC (Model:NUC7i5DNH)] [Kernel Flinger] [2018WW51] [PPR2.181005.003.A1 eng.build.20181227.102437] based Android P Dessert release.
* Release binary : https://github.com/projectceladon/celadon-binary/blob/master/ww201851/cel...
* Manifest : https://github.com/projectceladon/manifest/blob/master/stable-build/ww201...
* Release Notes for KBL_NUC : https://github.com/projectceladon/celadon-documentation/blob/master/sourc...
* Release Notes for APL_NUC : https://github.com/projectceladon/celadon-documentation/blob/master/sourc...
* For more details please visit wiki : https://github.com/projectceladon/manifest/wiki
* Documentation : https://01.org/projectceladon/documentation
ww201851_KBLNUC<https://github.com/projectceladon/celadon-documentation/blob/master/sourc...>
Build ID
cel_apl-userdebug 9 PPR2.181005.003.A1 eng.build.20181227.102437 test-keys
Software Version
Android version 9
Mesa
18.2.6
Kernel Version
4.19
Download Link
https://github.com/projectceladon/celadon-binary/tree/master/ww201851
Integrated Features<https://github.com/projectceladon/celadon-documentation/blob/master/sourc...>
* Graphics Memory Allocator (Gralloc) 1.0
* HDMI display support
* HWC 2.0 support for Display
* Adb & Fastboot supported over USB 2.0 and USB 3.0
* Adb over WIFI and Ethernet is supported
* USB digital audio playback support
* Since no default sound card is present we should connect USB headsset for any BT or media related activities for KBL COMMERCIAL NUC hardware
* Wi-Fi 802.11 a/b/g/n/ac and Bluetooth 4.2
* Wired Ethernet support
* Android Kernelflinger boot support
* Thermal Daemon is enabled for CELADON
* 4K support is enabled on CELADON
* Video Codec support on celadon
Decoder
o AVC High profile @ Level 5.1 (4k@30fps<mailto:4k@30fps>)
o HEVC Main and Main 10 profile @ Level 5 (4k@30fps<mailto:4k@30fps>)(Main 10 with BT2020 and ST2084 information is not supported)
o VP9 profile 0 @ Level 5 (4k@30fps<mailto:4k@30fps>)
o Vp8 8 bits 1080p@60fps<mailto:1080p@60fps>
Encoder
o AVC High profile @ level 4.1 (1080P@30fps<mailto:1080P@30fps>)
o HEVC Main profile @ Level 4 (1080P@30fps<mailto:1080P@30fps>)
* Art-extension is enabled in CELADON
* f2fs filesystem support enabled
* S3 Suspend/Resume is supported
* Audio decoders supported: MP3/AAC-LC/HEAAC/HEAAC-v2/FLAC/VORBIS/OPUS/AMRNB/AMRWB
* Audio Encoders: AAC-LC, AAC ELD, HEAAC, AMR-NB, AMR-WB, WAV
* SDHCI host controller is enabled
* Security reference solution - TPM based h/w binding reference implementation
* Flashing binaries via PFT - Platform Flash Tool
Important Notes and Remarks<https://github.com/projectceladon/celadon-documentation/blob/master/sourc...>
|C|<https://github.com/projectceladon/celadon-documentation/blob/master/sourc...> build has been validated on |NUC|<https://github.com/projectceladon/celadon-documentation/blob/master/sourc...> Kit NUC7i5DNH<https://ark.intel.com/products/122488/Intel-NUC-Kit-NUC7i5DNHE> in the following function domains:
Component
Results
Comments
Wi-Fi
OK
WiFi Direct, WiFi streaming
Wi-Fi Hotspot
OK
BT
OK
File Transfer Protocol
Audio over USB
OK
MP3/AAC/MIDI/FLAC/WAV Audio playback
Adb connect over WIFI
OK
Adb connect over Ethernet
OK
Display /Touch and Gesture
OK
Storage/SD Card
OK
Security
OK
Boot/Kernel
OK
USB devices over OTG
OK
Ethernet
OK
Fastboot
OK
Web browsing
OK
Video playback
OK
H264/H265/MPEG4/VP8/VP9 Video Playback
Known Issues<https://github.com/projectceladon/celadon-documentation/blob/master/sourc...>
* UI Flicker observed in few Screens for example - Under AOSP settings .
* Bluetooth file transfer fails in the first attempt after DUT reboot and it works fine once BT is reset
* Lets Drive screen seen, on click of applications under "New User"
* While executing DEPQ CTS , at a certain point there is adb disconnect observed where the DUT freezes , however once the adb is reconnected the test continues but the DUT is frozen
________________________________
Status<https://github.com/projectceladon/celadon-documentation/blob/master/sourc...>
* This WW51 Release has achieved 99.97% CTS pass rate and we are trending to achieve 100% CTS pass rate that we will be announcing shortly .. STAY TUNED.
________________________________
ww201851_APLNUC<https://github.com/projectceladon/celadon-documentation/blob/master/sourc...>
Build ID
cel_apl-userdebug 9 PPR2.181005.003.A1 eng.build.20181227.102437 test-keys
Software Version
Android version 9
Mesa
18.2.6
Kernel Version
4.19
Download Link
https://github.com/projectceladon/celadon-binary/tree/master/ww201851
Integrated Features<https://github.com/projectceladon/celadon-documentation/blob/master/sourc...>
* Graphics Memory Allocator (Gralloc) 1.0
* HDMI display support
* HWC 2.0 support for Display
* Adb over WIFI and Ethernet is supported
* USB digital audio playback support
* DMIC support
* Realtek ALC283 HD Audio via a stereo microphone/headphone 3.5 mm jack on the front panel is supported
* Wi-Fi 802.11 a/b/g/n/ac and Bluetooth 4.2
* Wired Ethernet support
* Android Kernelflinger boot support
* Thermal Daemon is enabled for CELADON
* 4K support is enabled on CELADON
* Video Codec support on celadon
Decoder
o AVC High profile @ Level 5.1 (4k@30fps<mailto:4k@30fps>)
o HEVC Main and Main 10 profile @ Level 5 (4k@30fps<mailto:4k@30fps>) (Main 10 with BT2020 and ST2084 information is not supported)
o VP9 profile 0 @ Level 5 (4k@30fps<mailto:4k@30fps>)
o Vp8 8 bits 1080p@60fps<mailto:1080p@60fps>
Encoder
o AVC High profile @ level 4.1 (1080P@30fps<mailto:1080P@30fps>)
o HEVC Main profile @ Level 4 (1080P@30fps<mailto:1080P@30fps>)
* Art-extension is enabled in CELADON
* f2fs filesystem support enabled
* S3 Suspend/Resume is supported
* Audio decoders supported: MP3/AAC-LC/HEAAC/HEAAC-v2/FLAC/VORBIS/OPUS/AMRNB/AMRWB
* Audio Encoders: AAC-LC, AAC ELD, HEAAC, AMR-NB, AMR-WB, WAV
* SDHCI host controller is enabled
* Security reference solution - TPM based h/w binding reference implementation
* Flashing binaries via PFT - Platform Flash Tool
Important Notes and Remarks<https://github.com/projectceladon/celadon-documentation/blob/master/sourc...>
|C|<https://github.com/projectceladon/celadon-documentation/blob/master/sourc...> build has been validated on |NUC|<https://github.com/projectceladon/celadon-documentation/blob/master/sourc...> Kit NUC6CAYH<https://www.intel.com/content/www/us/en/products/boards-kits/nuc/kits/nuc...> in the following function domains:
Component
Results
Comments
Wi-Fi
OK
WiFi Direct, WiFi streaming
Wi-Fi Hotspot
OK
BT
OK
File Transfer Protocol
Audio over 3.5mm jack
OK
MP3/AAC/MIDI/FLAC/WAV Audio playback
Adb connect over WIFI
OK
Adb connect over Ethernet
OK
Display /Touch and Gesture
OK
Storage/SD Card
OK
Security
OK
Boot/Kernel
OK
USB devices over OTG
OK
Ethernet
OK
Web browsing
OK
Video playback
OK
H264/H265/MPEG4/VP8/VP9 Video Playback
Known Issues<https://github.com/projectceladon/celadon-documentation/blob/master/sourc...>
* DUT freezes while using 4k monitor as display
* Lets Drive screen seen on click of applications under "New User"
* Need to press power button twice to wake-up from S3"
________________________________
Status<https://github.com/projectceladon/celadon-documentation/blob/master/sourc...>
* APL_NUC validation is done until WW48 , the manifest is taken based on WW51
* BIOS public drop for APL_NUC is coming very soon , once it is available FASTBOOT and adb over USB will be supported.. STAY TUNED.
To subscribe/unsubscribe:
- subscribe/unsubscribe celadon mailing list using : https://eclists.intel.com/sympa/review/1a-weekly_release , also visit link : https://lists.01.org/mailman/listinfo/celadon
10 months, 1 week
About install apk in Celadon
by Tan, Ming
Dear all:
I use the source code to build an image of Celadon, and use userdebug build and celadon lunch target.
I install it to a device and it can boot to UI.
But when I try to install an apk in it, the installation failed.
Has someone successfully install 3rd party apk in a device which installed the Celadon?
Thank you.
Tan Ming.
Software Engineer, SSG/OTC.
Mobile: +86 13651977713.
10 months, 2 weeks
Up Squared Target Name
by Soham Sinha
Hello,
I understand that Android-IA is now merged with Project Celadon. I am
wondering what the name of the target is for previous Android-IA platforms.
I want to build Project Celdaon for an Up Squared machine. Thanks!
Regards,
Soham Sinha
PhD Student, Department of Computer Science
Boston University
10 months, 3 weeks
Re: [01.org Celadon] Celadon Digest, Vol 8, Issue 17
by Gnanasekaran, Sundar
Hello Sohan Sinha,
You can edit BoardConfig.mk CMDLINE parameter to change serial console :
device/intel/project-celadon/<target-product>/BoardConfig.mk
Thanks,
G Sundar
-----Original Message-----
From: Celadon [mailto:celadon-bounces@lists.01.org] On Behalf Of celadon-request(a)lists.01.org
Sent: Monday, December 24, 2018 6:20 AM
To: celadon(a)lists.01.org
Subject: Celadon Digest, Vol 8, Issue 17
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. Re: Up Squared Target Name (Soham Sinha)
2. Re: Up Squared Target Name (Tan, Ming)
----------------------------------------------------------------------
Message: 1
Date: Sun, 23 Dec 2018 19:39:21 -0500
From: Soham Sinha <soham1(a)bu.edu>
To: "Tan, Ming" <ming.tan(a)intel.com>
Cc: "celadon(a)lists.01.org" <celadon(a)lists.01.org>, "Li, Zhuangzhi"
<zhuangzhi.li(a)intel.com>
Subject: Re: [01.org Celadon] Up Squared Target Name
Message-ID:
<CABGbKsVHmgcgAfi4WO3sen6eKsjzBwvz24wFXgE7nRb8TdK-KQ(a)mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hello Tan,
Thanks for helping!
Where do you change the console ttyS1?
For GRUB, I changed in the bootloader menuentry in linux line.
For KernelFlinger, where am I supposed to do it?
Also, is it possible to add a lunch target for the UP2 boards for Celadon?
It could be helpful.
Another question: is there any way to build Celadon for 32-bit, instead of the default 64 bit one?
Lastly, a note from my side, I can run android-x86 8.1-rc1 32-bit ISO from the android-x86 project and live-boot android on the UP Squared. It shows up the GUI. This works with their "No Hardware Acceleration" menu entry.
Regards,
Soham Sinha
CS PhD Student
Boston University
On Sun, Dec 23, 2018, 7:27 PM Tan, Ming <ming.tan(a)intel.com wrote:
> Sinha:
>
> We enabled the Celadon in UP2 board in May, and it can boot to UI.
>
> The following need to be take care:
>
> 1. If the ttyS0 does not work, then refer to
> https://up-board.org/wp-content/uploads/datasheets/UP-Square-Datasheet
> V0.5.pdf, use the Pin 8,9,10 in the 40Pin GP-Bus, and try to use
> ttyS1.
>
> 2. Disable the trusty.
>
> Modify the device/intel/project-celadon/celadon/mixins.spec,
> set the trusty: false, and in boot-arch:, set tos_partition=false.
>
>
>
> You can also disable the trusty and try it in SKL NUC.
>
>
>
> BR/Tan Ming.
>
>
>
> *From:* Soham Sinha [mailto:soham1@bu.edu]
> *Sent:* Monday, December 24, 2018 6:38 AM
> *To:* Tan, Ming <ming.tan(a)intel.com>
> *Cc:* celadon(a)lists.01.org
> *Subject:* Re: [01.org Celadon] Up Squared Target Name
>
>
>
> Hello,
>
> I am working with UP2 or UP Squared boards: Intel Pentium version
> <https://up-board.org/upsquared/specifications/>.
>
>
>
> I applied the patch. Unfortunately, I could not get any output from
> the serial console. I can get serial console output in other cases but
> not with Project Celadon images. So the serial pins are working fine.
>
>
>
> I tried both the GRUB and kernelflinger processes. For GRUB, I changed
> to
> console=ttyS0,115200n8 which seems to be the required one for Up
> Squared board. I didn't connect any keyboard or display. Still, I
> could not see any output on my client serial output.
>
>
>
> For the KernelFligner as well, nothing comes to the console.
>
>
>
> Additionally, I tried the GRUB booting process on an Intel Skull
> Canyon <https://www.intel.com/content/www/us/en/products/docs/boards-kits/nuc/nuc...>.
> Same issue happened: when I select any of the boot options, the screen
> freezes, and the keyboard stops working. I have not tried the
> KernelFlinger direct booting on Skull Canyon because it seems to be
> directly working on the hard disk without any warning, which I don't want, as of now.
>
>
>
> Any clue or suggestions on how to fix this?
>
>
> Regards,
>
> Soham Sinha
>
> PhD Student, Department of Computer Science
>
> Boston University
>
>
>
>
>
> On Sun, Dec 23, 2018 at 9:06 AM Tan, Ming <ming.tan(a)intel.com> wrote:
>
> Sinha:
>
> Which type of UP board are you using? There are several type of UP
> board in https://up-board.org/.
>
> Can you mail me the serial log of kernelflinger to me?
>
> And you can try the patch of
> https://github.com/projectceladon/hardware-intel-kernelflinger/pull/5
> to output more detail kernel log. And the default serial port used by
> kernel is ttyS0, you need to check the UP board use which serial port.
>
>
>
> You can ignore the ?Failed to get SDIO protocol? warning and need
> not copy userdata.img.
>
>
>
> BR/Tan Ming.
>
>
>
> *From:* Soham Sinha [mailto:soham1@bu.edu]
> *Sent:* Sunday, December 23, 2018 9:54 PM
> *To:* Tan, Ming <ming.tan(a)intel.com>
> *Cc:* celadon(a)lists.01.org
> *Subject:* Re: [01.org Celadon] Up Squared Target Name
>
>
>
> I have built for the Celadon target but none of the booting processes
> works for Up Squared. I'm trying out the 8.1 branch.
>
>
>
> For the GRUB process, I copied over celadon.img, but once I select
> project Celadon from the boot menu, nothing shows up, keyboard stops working.
>
>
>
> For the KernelFlinger via EFI shell process, there seems to be some
> issue with eMMC storage. When the flashing is going on in EFI shell, I
> get error message as " Failed to get SDIO protocol". But the flashing
> continues and finally gets stuck on "flashing lock". When I remove the "flashing lock"
> fastboot command from installer.cmd file, flashing is completed. But
> then the booting hangs up in the "Intel" logo screen and never goes to
> the Android logo screen. Another issue was that I had to additionally
> copy userdata.img to the USB disk, which was not included in the
> KernelFlinger zip files.
>
>
>
> Regards,
> Soham Sinha
> CS PhD Student
> Boston University
>
>
>
> On Sun, Dec 23, 2018, 8:39 AM Tan, Ming <ming.tan(a)intel.com wrote:
>
> Sinha:
>
> Currently Celadon has two lunch target: celadon and cel_apl.
>
> Celadon is used for Android table device. Cel_apl is used for
> Android automotive device.
>
> You can select one as your device usage.
>
>
>
> BR/Tan Ming.
>
>
>
> *From:* Celadon [mailto:celadon-bounces@lists.01.org] *On Behalf Of
> *Soham Sinha
> *Sent:* Sunday, December 23, 2018 5:28 AM
> *To:* celadon(a)lists.01.org
> *Subject:* [01.org Celadon] Up Squared Target Name
>
>
>
> Hello,
>
>
>
> I understand that Android-IA is now merged with Project Celadon. I am
> wondering what the name of the target is for previous Android-IA platforms.
> I want to build Project Celdaon for an Up Squared machine. Thanks!
>
>
> Regards,
>
> Soham Sinha
>
> PhD Student, Department of Computer Science
>
> Boston University
>
>
10 months, 3 weeks
Encoded Frame is not proper , Using Hardware Encoder through Media Codec
by Sathish
Hi,
As part of a video app , I am using Hardware Encoder/Decoder through Media
Codec.
The camera is generating YUYV422 Raw frame , I am converting it to YUV420
using Media SDK VPP Processing.
and submitting the YUV420 frame to the Media Codec Encoder.
The Encoder is configured as H264, 1080p , COLOR_FormatYUV420Flexible,
1500Kbps, gop 0, Baseline , AVCLevel31, and fps 30.
I am submitting the encoded frame to Decoder , But this is not being
rendered on the surface.
I tried playing the encoded frame using ffplay , but the quality is very
poor but no errors. The YUYV422 and YUV420 frames looks good when played
through ffplay.
It seems the NALReference IDC value is 01 instead of 11 indicating of a B
frame.
I see the below codes in the generated H264 file , 00 00 00 01 25 being
repeated most of the time.
00 00 00 01 27
00 00 00 01 28
00 00 00 01 25
could you please let me know if there are any configuration change's that I
am missing in Encoder ? Is there any configuration to avoid generating B
frames ?
Appreciate any inputs on this .
Thanks,
Sathish
11 months
