got it, thank you!
is it possible to update xpadneo driver to newest version, actually buildin is 0.6.0, newest is 0.9.1
master branch is 0.10.0 but it needs kernel 4.18 so not for us 
Your s905x doesn’t need to be updated to Android 8 or higher.
Android 7.1.2 is the version you need.
You can try this ROM (lots of positive feedback from the owners of various s905x boxes):
https://mega.nz/file/e0oj0CQK#6k-GdfJp0xIuYHa24HKJtUEF_WboMMqJETjyouqmspM
1 Like
Hoi!
Today I did a fresh install on my Venz V10 Pro, a generic gxl_p212_2g/S905X device.
Previous version was CoreElec 9.7.2
Using the remote.conf from the original installation everything used to work fine with 9.7.2. But with this release at least the down button does not work.
In the log from 9.7.2. it reads (up and down pressed)
2021-08-01 19:58:49.773 T:4087472112 DEBUG: Keyboard: scancode: 0x67, sym: 0x0111, unicode: 0x0000, modifier: 0x0
2021-08-01 19:58:49.774 T:4087472112 DEBUG: HandleKey: up (0xf080) pressed, action is Up
2021-08-01 19:58:50.563 T:4087472112 DEBUG: Keyboard: scancode: 0x6c, sym: 0x0112, unicode: 0x0000, modifier: 0x0
2021-08-01 19:58:50.563 T:4087472112 DEBUG: HandleKey: down (0xf081) pressed, action is Down
In the 19.2rc2 log it reads:
2021-08-01 19:13:52.077 T:5842 DEBUG <general>: Keyboard: scancode: 0x67, sym: 0x0111, unicode: 0x0000, modifier: 0x0
2021-08-01 19:13:52.077 T:5842 DEBUG <general>: HandleKey: up (0xf080) pressed, action is Up
2021-08-01 19:14:01.349 T:5856 DEBUG <general>: CLibInputPointer::ProcessMotion - event.type: 3, event.motion.x: 0, event.motion.y: 0
The CLibInputPointer is the only response to the down button.
The sections (yes, the up and down buttons appear twice) in remote.conf are:
0x05 103 #up
0x00 108 #down
0x25 103 #up
0x26 108 #down
Any recommendations??
Groeten,
Frank.
Hello,
I am facing a very strange problem,
I just bought a second Khadas Vim3 pro box. I transferred the MicroSD card from one to the other, and I have a problem with this new box that I don’t have on my first Khadas Vim 3 pro box (older). However, both have the same firmware. I have done the test several times, and the problem is systematic.
The problem is : Movies crash after 2min of playback.
The last time it happened around 6:20 pm : http://ix.io/3uOh
Need some informations. I am now on 9.2.7 version. Can i update to 19.2 Matrix . Is the chipset supported ?
Guess what, we need some informations too, like which chipsets?
1 Like
Sorry forgot , i own MINIX NEO U9 -H SOC Amlogic S912-H
Are you using same SD card on both devices?
1 Like
Yes i do and i do not want to loose that option
on sd side i have coreelec. On internal storage emmc Android
I see there are other questions, but let me share my research with you. It happened again, and here’s what I can read as it happened :
2021-08-02 19:35:31.185 T:4917 ERROR <general>: [ script.embuary.helper ] Image error: Could not get image for image://video@smb%3a%2f%2f192.168.1.50%2fSgt_8To%2fFILMS%2fGemini%20Man%20(2019)%20(HDR%2060ips).mkv/ (try 3) -> [Errno 2] No such file or directory: '/storage/.kodi/userdata/addon_data/script.embuary.helper/img/tmp/cc5e398c2fa91ba680f34a64ef0960f8.jpg'
2021-08-02 19:39:41.574 T:4811 INFO <general>: CVideoPlayer::CloseFile()
2021-08-02 19:39:41.575 T:4811 INFO <general>: VideoPlayer: waiting for threads to exit
2021-08-02 19:39:46.112 T:5145 INFO <general>: CVideoPlayerAudio::Process - stream stalled
2021-08-02 19:39:50.563 T:5142 INFO <general>: CVideoPlayer::OnExit()
2021-08-02 19:39:50.563 T:5142 INFO <general>: Closing stream player 1
2021-08-02 19:39:50.563 T:5142 INFO <general>: Waiting for audio thread to exit
2021-08-02 19:39:50.568 T:5145 INFO <general>: thread end: CVideoPlayerAudio::OnExit()
2021-08-02 19:39:50.569 T:5142 INFO <general>: Closing audio device
2021-08-02 19:39:50.574 T:5142 INFO <general>: Deleting audio codec
2021-08-02 19:39:50.574 T:5142 INFO <general>: Closing stream player 2
2021-08-02 19:39:50.574 T:5142 INFO <general>: waiting for video thread to exit
2021-08-02 19:39:50.574 T:4819 INFO <general>: CActiveAESink::OpenSink - initialize sink
2021-08-02 19:39:50.604 T:5144 INFO <general>: thread end: video_thread
2021-08-02 19:39:50.604 T:5142 INFO <general>: deleting video codec
2021-08-02 19:39:50.608 T:5142 INFO <general>: Closing stream player 3
2021-08-02 19:39:50.660 T:4819 INFO <general>: CAESinkALSA::Initialize - Attempting to open device "surround71:CARD=AMLAUGESOUND,DEV=0"
2021-08-02 19:39:50.667 T:4819 INFO <general>: CAESinkALSA::Initialize - Opened device "surround71:CARD=AMLAUGESOUND,DEV=0"
2021-08-02 19:39:50.670 T:4819 INFO <general>: CAESinkALSA::InitializeHW - Your hardware does not support AE_FMT_FLOAT, trying other formats
2021-08-02 19:39:50.670 T:4819 INFO <general>: CAESinkALSA::InitializeHW - Using data format AE_FMT_S24NE4
2021-08-02 19:39:59.862 T:5143 ERROR <general>: Read - Error( -1, 110, Connection timed out )
2021-08-02 19:39:59.862 T:5143 ERROR <general>: Process - <smb://192.168.1.50/Sgt_8To/FILMS/Gemini Man (2019) (HDR 60ips).mkv> source read failed with -1!
2021-08-02 19:40:59.921 T:4811 INFO <general>: VideoPlayer: finished waiting
2021-08-02 19:40:59.922 T:4811 INFO <general>: CVideoPlayer::CloseFile()
2021-08-02 19:40:59.922 T:4811 INFO <general>: VideoPlayer: waiting for threads to exit
2021-08-02 19:40:59.922 T:4811 INFO <general>: VideoPlayer: finished waiting
2021-08-02 19:40:59.956 T:4811 ERROR <general>: GetString: error reading /sys/class/amhdmitx/amhdmitx0/custom_mode
(…)
What does this mean ? Whole of informations in LOG
Yes, exactly the same. I directly transfer it to the new Vim3 pro to test.
You mean physically same SD card? Or you have two same cards and both devices are on.
Coreelec is on microSD, on internal is Android? can we install CoreELEC 19.2 (Kodi 19) to Minix U9-H ?
I only have one microSD card for two Vim3 Pro
-
I put the card in the first Vim3 Pro : everything works
-
I put this same card in the second Vim3 Pro : the videos crash after 2 min
S912 isn’t supported in Amlogic-ng and Matrix. You’ll have to stay in 9.2.7.
Topic closed as rc3 is available: