Thanks, thats neat (although I didnt really using Android). I will add this to my Confluence skin. Just in case 
Yep, me neither.
But I like to have (some sort of) redundancy. And, just in case, broaden the “portfolio” of services, provided from the box. Android gaming, for example.
Can anyone confirm that these boxes power down their USB ports when switched off ?
Shoog
Mine does NOT.
I have a small usb fan connected and yes it power it down after shutdown, but no immediately It takes about 40 seconds after shutdown.
Is WoL still working for you guys? It broke for me a while back but I’m not sure exactly when as I don’t use it much.
yep i think you right!
Just test now and my PC dont wake up
Still on 20200206
1 Like
Thanks, thats useful to know.
Shoog
Today i measured the performance of CE with X96 Air. Does somebody experience the same ?
It takes 12 seconds after power on for the splash screen to appear and 70 seconds before the clock displays and a few more seconds before the skin starts.
Why is the boot process so slow ?
This is not normal. Perhaps your heatsink is not firmly attached and the cpu is being heavily throttled.
It works much faster when i boot Android. Maybe 10 seconds all together.
On a X96 Max Plus S905X3 I get about 10 seconds to CoreElec logo and a further 16 seconds to menu. That’s on a V30 card or on internal emmc. Have you got wait for network enabled in boot that would slow it down or a slow SD card.
I don’t have wait enabled. I checked dmesg and i see already a gap of 30 seconds here:
[ 23.441942@0] OpenVFD: Skipping vfd_gpio0 evaluation (0xFF)
[ 23.441943@0] OpenVFD: Skipping vfd_gpio1 evaluation (0xFF)
[ 23.441945@0] OpenVFD: Skipping vfd_gpio2 evaluation (0xFF)
[ 23.441946@0] OpenVFD: Skipping vfd_gpio3 evaluation (0xFF)
[ 23.442420@1] OpenVFD: Select FD628 controller
[ 23.442459@1] OpenVFD: SW SPI 3-wire interface intialized (LSB mode)
[ 50.798251@2] the demux clock on, ref cnt: 1
After OpenVFD nothing happens for 27 seconds.
Then again some losses:
[ 50.798260@2] the parser_top clock on, ref cnt: 1
[ 50.798264@2] the vdec clock on, ref cnt: 1
[ 50.798288@2] the clk_hevc_mux clock on, ref cnt: 1
[ 50.798293@2] the clk_hevcb_mux clock on, ref cnt: 1
[ 50.798398@2] hevc mux clock is 499999992 Hz
[ 50.798437@2] hevc back mux clock is 499999992 Hz
[ 50.798464@2] the clk_vdec_mux clock on, ref cnt: 1
[ 50.798498@2] vdec mux clock is 799999987 Hz
[ 50.798559@2] vdec_create instance ffffff80101c7000, total 1
[ 50.798580@2] vdec_disable_DMC input->target= 0x0
[ 50.798581@2] vdec_release instance ffffff80101c7000, total 1
[ 50.798599@2] the clk_vdec_mux clock off, ref cnt: 0
[ 50.798605@2] the vdec clock off, ref cnt: 0
[ 50.798608@2] the parser_top clock off, ref cnt: 0
[ 50.798611@2] the demux clock off, ref cnt: 0
[ 62.491343@1] fb: mem_free_work, free memory: addr:800000
[ 64.779750@2] aml_tdm_open
From the demux to fb: mem again 12 seconds gone.
Anybody knows why ?
So today i disabled openvfd and tried again but it didn’t help.
I think this takes much time:
[ 62.490484@0] fb: mem_free_work, free memory: addr:800000
Btw, with the update from today you can also change the cpu governor but setting it to “ondemand” didn’t help also.
Yes x96 more faster to x96 air…
I have just received my second x96Air after the first’s HDMI socket died.
Before I added active cooling, with PERFORMANCE governor set, I was observing CPU speeds dropping down to 1.7ghz, which is proof positive that these boxes uncooled will experience thermal throttling.
Adding an active fan and CPU speed sticks at 1.9ghz
I added the fan drive by directly soldering the fan to the USB pads on the underside of the X96Air board, and I will report back if it responds to USB power off when the box is powered down. I already obverse that the newer board is subtly different to the older board even though they are both 2g/16g.
A massive 27C temp drop with fan cooling.
Shoog
Which did you get … P2 or P3 … or maybe P4 now
Dont know how to check.
Shoog