Update in #1.
I only compiled new version under parent kszaq's version as I have a bike camp in Croatia this week.
[8.0.2c] LibreELEC 8.0 builds for KI Plus / KII Pro / KI Pro
-
afl1 -
November 29, 2016 at 9:04 PM -
Thread is Unresolved
-
-
Update in #1.
I only compiled new version under parent kszaq's version as I have a bike camp in Croatia this week.Thanks for your and Kszaq's job.
Less buffering, smother channel switching.In video player mode rewind doesn't work.
Wake up does'no t work. I realize without Network time Sever kII pro doesn't know the time, without actual time impossible to wake up.Have a good bike camp!
-
K1 Plus Combo 8.0.1a -> 8.0.1c [DVB-S2]
I'm not sure that I had any buffering issues with 8.0.1a version, at least I cannot remember any, but with the "1c" it's present. I had been using "1a" since release for 1-3 hours a day.today
Code19:14:21.781 T:3631215520 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer 19:14:23.929 T:4121042400 NOTICE: Display resolution ADJUST : 1920x1080 @ 50.00 - Full Screen (16) (weight: 0.000) 19:18:14.621 T:3631215520 NOTICE: Previous line repeats 1 times. 19:18:14.621 T:3631215520 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer
Yesterday 7 times according to log. I remember few times.
logs -
Update in #1 with pvr.hts timeshift fix.
-
After reading this topic I ordered a KII plus PRO in China, I'am bored with dull enigma2 and wan't a mediaplayer/system allinone
Now awaiting delivery ( Can't wait) great job afl1 from what I read here
-
Does anyone else had any problems on dvb-c using latest updates?
How can get more detailed debug information from Tvheadend? And not just "dvb-c scan no data, failed"
-
Does anyone else had any problems on dvb-c using latest updates?How can get more detailed debug information from Tvheadend? And not just "dvb-c scan no data, failed"
In tvheadend debug window allow linuxdvb,mpegts and in log window push 'gear-box' to allow debug log.
-
Update in #1
-
It seems that r848 is trying to tune dvbs or i'm reading useless info?
need rebuild again
+ tuners/r848: DVB-C annex B support.Hi, same issue that happened with R848 is present now with new board (r912 tuner), I saw that there wasn't r912 folder in /sys/modules, is it possible to port the same solution that was made for r848 for r912? System appears to be trying to use r848 driver
logs:
Code
Display More[ 290.090015@1] R848: r848_init: [ 293.083501@1] AVL: avl6862_read_status: Level=32 [ 293.283482@1] AVL: avl6862_read_status: Level=32 [ 293.483475@1] AVL: avl6862_read_status: Level=32 [ 293.683107@1] AVL: avl6862_read_status: Level=32 [ 293.883442@1] AVL: avl6862_read_status: Level=32 [ 294.074872@2] AVL: avl6862_set_dvbmode: initing demod for delsys=1 [ 294.075018@2] i2c i2c-1: Load avl6862 firmware patch for DVB-C size=47928 [ 294.257298@1] AVL: avl6862_wait_demod_boot: status:1 ready_code:0x5aa57ff7 [ 294.283264@1] AVL: avl6862_wait_demod_boot: status:0 ready_code:0x5aa57ff7 [ 294.283603@1] i2c i2c-1: avl6862 patch ver 2.0 build 20559 [ 294.385136@0] R848: r848_set_params: delivery_system=2 frequency=375000000 symbol_rate=5360000 bandwidth_hz=6000000 [ 294.985213@1] R848: r848_set_params: R848_SetPllData for DVB-C Annex B [ 294.985307@1] R848: r848_set_params: R848_SetStandard=45 [ 294.985357@1] R848: r848_set_params: R848_SetFrequency=375000 KHz [ 294.985597@1] R848: R848_GetLockStatus: R848_GETLOCKSTATUS=0x57 [ 294.985642@1] R848: r848_set_params: Tuner Locked. [ 294.986004@1] AVL: avl6862_set_dvbc_b: Freq:375000000 Mhz,sym:5360000 [ 295.013690@1] AVL: avl6862_read_status: Level=32 [ 295.014395@1] AVL: avl6862_read_status: Level=32 [ 295.015501@1] AVL: avl6862_read_status: Level=32 [ 295.018363@1] AVL: avl6862_read_status: Level=32 [ 295.065325@1] AVL: avl6862_read_status: Level=32 [ 295.115384@1] AVL: avl6862_read_status: Level=32 [ 295.165794@1] AVL: avl6862_read_status: Level=32
-
Thanks for efforts, same issue with buffering here, from usb drive every one minute stop for buffering few seconds.
-
In tvheadend debug window allow linuxdvb,mpegts and in log window push 'gear-box' to allow debug log.
Code
Display MoreLoglevel debug: enabled 2017-04-09 13:53:08.716 mpegts: DVB-C Network - adding mux 219MHz in DVB-C Network to scan queue weight 6 flags 4000 2017-04-09 13:53:08.717 mpegts: 219MHz in DVB-C Network - add raw service 2017-04-09 13:53:08.717 mpegts: 219MHz in DVB-C Network - tuning on Availink avl6862 #0 : DVB-C #0 2017-04-09 13:53:08.717 linuxdvb: Availink avl6862 #0 : DVB-C #0 - starting 219MHz in DVB-C Network 2017-04-09 13:53:08.718 mpegts: 219MHz in DVB-C Network - started 2017-04-09 13:53:08.718 mpegts: 219MHz in DVB-C Network - open PID 1FFB (8187) [20/0xee401fd0] 2017-04-09 13:53:08.718 mpegts: 219MHz in DVB-C Network - open PID 012B (299) [16/0xee403400] 2017-04-09 13:53:08.718 mpegts: 219MHz in DVB-C Network - open PID 0039 (57) [16/0xee404880] 2017-04-09 13:53:08.718 mpegts: 219MHz in DVB-C Network - open PID 0BBA (3002) [16/0xee405d98] 2017-04-09 13:53:08.718 mpegts: 219MHz in DVB-C Network - open PID 0BBB (3003) [16/0xee4072d8] 2017-04-09 13:53:08.718 mpegts: 219MHz in DVB-C Network - open PID 0012 (18) [20/0xee408828] 2017-04-09 13:53:08.718 mpegts: 219MHz in DVB-C Network - open PID tables subscription [0042/0xee400bb8] 2017-04-09 13:53:08.718 subscription: 0005: "scan" subscribing to mux "219MHz", weight: 6, adapter: "Availink avl6862 #0 : DVB-C #0", network: "DVB-C Network", service: "Raw PID Subscription" 2017-04-09 13:53:08.781 linuxdvb: Availink avl6862 #0 : DVB-C #0 - status FAINT (SIGNAL) 2017-04-09 13:53:13.717 mpegts: 219MHz in DVB-C Network - scan no data, failed 2017-04-09 13:53:13.717 subscription: 0005: "scan" unsubscribing 2017-04-09 13:53:13.717 mpegts: 219MHz in DVB-C Network - close PID tables subscription [0042/0xee400bb8] 2017-04-09 13:53:13.717 mpegts: 219MHz in DVB-C Network - stopping mux 2017-04-09 13:53:13.718 linuxdvb: Availink avl6862 #0 : DVB-C #0 - stopping 219MHz in DVB-C Network 2017-04-09 13:53:13.718 mpegts: 219MHz in DVB-C Network - close PID 0012 (18) [20/0xee408828] 2017-04-09 13:53:13.718 mpegts: 219MHz in DVB-C Network - close PID 0039 (57) [16/0xee404880] 2017-04-09 13:53:13.718 mpegts: 219MHz in DVB-C Network - close PID 012B (299) [16/0xee403400] 2017-04-09 13:53:13.718 mpegts: 219MHz in DVB-C Network - close PID 0BBA (3002) [16/0xee405d98] 2017-04-09 13:53:13.718 mpegts: 219MHz in DVB-C Network - close PID 0BBB (3003) [16/0xee4072d8] 2017-04-09 13:53:13.718 mpegts: 219MHz in DVB-C Network - close PID 1FFB (8187) [20/0xee401fd0] 2017-04-09 13:53:13.718 mpegts: DVB-C Network - removing mux 219MHz in DVB-C Network from scan queue
That is what i get trying to scan on DVB-C Annex A, in Brazil.
PS.: Worked perfectly until version 8.0-8.0.0f-I, inclusive. All version after that dont work. -
That is what i get trying to scan on DVB-C Annex A, in Brazil.
PS.: Worked perfectly until version 8.0-8.0.0f-I, inclusive. All version after that dont work.With DVB-C annex B update by crazycat69 I updated dvb-c firmware. Try this special version with original dvb-c firmware.
LibreELEC-S905.arm-8.0-8.0.1e-IX.img.gz -
With DVB-C annex B update by crazycat69 I updated dvb-c firmware. Try this special version with original dvb-c firmware.
LibreELEC-S905.arm-8.0-8.0.1e-IX.img.gzThanks alot! i'll try it now post the results later on.
[hr]With DVB-C annex B update by crazycat69 I updated dvb-c firmware. Try this special version with original dvb-c firmware.
LibreELEC-S905.arm-8.0-8.0.1e-IX.img.gzSeems like it didnt work. But, thanks anyway.
Code
Display MoreLoglevel debug: enabled 2017-04-09 18:30:32.754 mpegts: DVB-C Network - adding mux 219MHz in DVB-C Network to scan queue weight 6 flags 4000 2017-04-09 18:30:32.755 mpegts: 219MHz in DVB-C Network - add raw service 2017-04-09 18:30:32.755 mpegts: 219MHz in DVB-C Network - tuning on Availink avl6862 #0 : DVB-C #0 2017-04-09 18:30:32.755 linuxdvb: Availink avl6862 #0 : DVB-C #0 - starting 219MHz in DVB-C Network 2017-04-09 18:30:32.755 mpegts: 219MHz in DVB-C Network - started 2017-04-09 18:30:32.755 mpegts: 219MHz in DVB-C Network - open PID 0012 (18) [20/0xee1029a8] 2017-04-09 18:30:32.756 mpegts: 219MHz in DVB-C Network - open PID 0BBA (3002) [16/0xee103e20] 2017-04-09 18:30:32.756 mpegts: 219MHz in DVB-C Network - open PID 0BBB (3003) [16/0xee1055b8] 2017-04-09 18:30:32.756 mpegts: 219MHz in DVB-C Network - open PID 0039 (57) [16/0xee1069e8] 2017-04-09 18:30:32.756 mpegts: 219MHz in DVB-C Network - open PID 012B (299) [16/0xee107e18] 2017-04-09 18:30:32.756 mpegts: 219MHz in DVB-C Network - open PID 1FFB (8187) [20/0xee10aa70] 2017-04-09 18:30:32.756 mpegts: 219MHz in DVB-C Network - open PID tables subscription [0042/0xee1017d0] 2017-04-09 18:30:32.756 subscription: 0005: "scan" subscribing to mux "219MHz", weight: 6, adapter: "Availink avl6862 #0 : DVB-C #0", network: "DVB-C Network", service: "Raw PID Subscription" 2017-04-09 18:30:32.821 linuxdvb: Availink avl6862 #0 : DVB-C #0 - status FAINT (SIGNAL) 2017-04-09 18:30:37.755 mpegts: 219MHz in DVB-C Network - scan no data, failed 2017-04-09 18:30:37.755 subscription: 0005: "scan" unsubscribing 2017-04-09 18:30:37.755 mpegts: 219MHz in DVB-C Network - close PID tables subscription [0042/0xee1017d0] 2017-04-09 18:30:37.755 mpegts: 219MHz in DVB-C Network - stopping mux 2017-04-09 18:30:37.755 linuxdvb: Availink avl6862 #0 : DVB-C #0 - stopping 219MHz in DVB-C Network 2017-04-09 18:30:37.756 mpegts: 219MHz in DVB-C Network - close PID 0012 (18) [20/0xee1029a8] 2017-04-09 18:30:37.756 mpegts: 219MHz in DVB-C Network - close PID 0039 (57) [16/0xee1069e8] 2017-04-09 18:30:37.756 mpegts: 219MHz in DVB-C Network - close PID 012B (299) [16/0xee107e18] 2017-04-09 18:30:37.756 mpegts: 219MHz in DVB-C Network - close PID 0BBA (3002) [16/0xee103e20] 2017-04-09 18:30:37.756 mpegts: 219MHz in DVB-C Network - close PID 0BBB (3003) [16/0xee1055b8] 2017-04-09 18:30:37.756 mpegts: 219MHz in DVB-C Network - close PID 1FFB (8187) [20/0xee10aa70] 2017-04-09 18:30:37.756 mpegts: DVB-C Network - removing mux 219MHz in DVB-C Network from scan queue
-
-
R912 is only new version of R848. Driver is same for both chips.What do you mean under weak signal? Is only signal strength gauge showing low value? In driver is erratically calculated signal strength (I am unable to fix it), only usable value is SNR. -
Hi, could you add the Realtekwifidriver from gxbb_p200_1G_100M_RealtekWiFi.dtb to your firmware?
I use 5ghz network because the 2.4ghz is full in our location. -
Hi, could you add the Realtekwifidriver from gxbb_p200_1G_100M_RealtekWiFi.dtb to your firmware?
I use 5ghz network because the 2.4ghz is full in our location.In KI Plus is Realtek RTL8189ETV. It only supports 2.4 GHz WiFi.
-
Kszaq totally repair fps changes with latest dev build:
LibreELEC-S905.arm-8.0-devel-20170409011740-r25791-g1fb98dc.tarAnd he say make a little break with developing.
Can you make this version to K1plus too?thank you :R
-