Try this one:
http://channels-kodi.s3.amazonaws.com/2019.10.05.1837/pvr.channelsdvr-linux-armhf.zip
It doesnāt install, and all the pop up says is that it failed. The logs are almost as helpful as the pop up:
2019-10-05 15:01:13.321 T:4064066960 DEBUG: ------ Window Deinit (FileBrowser.xml) ------
2019-10-05 15:01:13.327 T:4064066960 DEBUG: CAddonInstaller: installing from zip '/storage/Gdrive/Downloads/Kodi Addons/pvr.channelsdvr-linux-armhf.zip'
2019-10-05 15:01:13.926 T:4064066960 DEBUG: ------ Window Init (DialogNotification.xml) ------
Is the failures of being able to create timers being worked on ?
Creating timers is not supported yet. This is a pre-alpha build and features are being added one at a time. There's only so many hours in a day and I am juggling DVR/Android/iOS/TVE all at the same time.
2 Likes
Thanks for the info ... understood.
Just curious, what is the scope of creating this add on? is it comparable to porting to a completely new platform?
Re: timers, it would help to know what you were trying to do that produced an error? Which features are most important? Timer support has many different parts:
- got record on current show while watching TV
- record single episode manually from guide
- create series pass for all or new episodes
- pause/resume existing pass
- delete existing manual recording schedule
- edit timer rule to change margin
Getting a sense of which of these are priorities will help me allocate development time.
These ... but no hurry already have passes for new shows.
Another one to try on Linux: 2019.10.06.0547
1 Like
Didnāt work 
Worked! 
Automatically detecting channels isnāt working for some reason, but adding in the IP for my server works. One main issue is no icons for a lot of channels.
Update: Icons are showing up now.
Cool! What skin is that?
What did the log show when auto discovery fails?
It's the Aura skin. I'll have to play around with it later, I can't find it in the kodi.log or kodi.old.log anymore since I rebooted a few times while moving things around.
Hereās what itās in the log after I install.
2019-10-07 20:17:47.113 T:2801791856 NOTICE: AddOnLog: Channels DVR Client: Discovery failed: listen udp4 224.0.0.0:5353: bind: address already in use
2019-10-07 20:17:47.114 T:2801791856 NOTICE: PVR Manager: Starting
2019-10-07 20:17:47.129 T:2528220016 ERROR: GetChannels: Add-on 'Channels DVR:connected' returned an error: server error
2019-10-07 20:17:47.129 T:2528220016 ERROR: GetChannels: PVR client 'Channels DVR:connected' returned an error: server error
2019-10-07 20:17:48.658 T:2528220016 ERROR: GetChannelGroupMembers: Add-on 'Channels DVR:connected' returned an error: server error
2019-10-07 20:17:48.658 T:2528220016 ERROR: GetChannelGroupMembers: PVR client 'Channels DVR:connected' returned an error: server error
2019-10-07 20:17:48.669 T:2528220016 ERROR: GetChannelGroupMembers: Add-on 'Channels DVR:connected' returned an error: server error
2019-10-07 20:17:48.669 T:2528220016 ERROR: GetChannelGroupMembers: PVR client 'Channels DVR:connected' returned an error: server error
2019-10-07 20:17:48.684 T:2528220016 ERROR: GetChannelGroupMembers: Add-on 'Channels DVR:connected' returned an error: server error
2019-10-07 20:17:48.684 T:2528220016 ERROR: GetChannelGroupMembers: PVR client 'Channels DVR:connected' returned an error: server error
2019-10-07 20:17:48.685 T:2528220016 ERROR: GetChannelGroupMembers: Add-on 'Channels DVR:connected' returned an error: server error
2019-10-07 20:17:48.685 T:2528220016 ERROR: GetChannelGroupMembers: PVR client 'Channels DVR:connected' returned an error: server error
2019-10-07 20:17:48.685 T:2528220016 ERROR: GetChannelGroupMembers: Add-on 'Channels DVR:connected' returned an error: server error
2019-10-07 20:17:48.686 T:2528220016 ERROR: GetChannelGroupMembers: PVR client 'Channels DVR:connected' returned an error: server error
2019-10-07 20:17:48.821 T:2528220016 ERROR: GetChannelGroupMembers: Add-on 'Channels DVR:connected' returned an error: server error
2019-10-07 20:17:48.821 T:2528220016 ERROR: GetChannelGroupMembers: PVR client 'Channels DVR:connected' returned an error: server error
2019-10-07 20:17:48.822 T:2528220016 ERROR: GetChannelGroupMembers: Add-on 'Channels DVR:connected' returned an error: server error
2019-10-07 20:17:48.822 T:2528220016 ERROR: GetChannelGroupMembers: PVR client 'Channels DVR:connected' returned an error: server error
2019-10-07 20:17:48.845 T:2528220016 ERROR: GetTimers: Add-on 'Channels DVR:connected' returned an error: server error
2019-10-07 20:17:48.845 T:2528220016 ERROR: GetTimers: PVR client 'Channels DVR:connected' returned an error: server error
2019-10-07 20:17:48.845 T:2528220016 ERROR: GetRecordings: Add-on 'Channels DVR:connected' returned an error: server error
2019-10-07 20:17:48.845 T:2528220016 ERROR: GetRecordings: PVR client 'Channels DVR:connected' returned an error: server error
1 Like
Thanks. Seems like a conflict with some zeroconf service on the system. Can you run this and paste results:
sudo lsof -nP :5353
netstat -antup | egrep -i 5353
udp 0 0 0.0.0.0:5353 0.0.0.0:* 3827/avahi-daemon:
udp 0 0 :::5353 :::* 3827/avahi-daemon:
lsof -nP :5353 (I cut out everything except the PID for avahi-daemon since the busybox lsof on CoreELEC just shows all open files without taking any options)
3827 /usr/sbin/avahi-daemon /dev/null
3827 /usr/sbin/avahi-daemon socket:[18510]
3827 /usr/sbin/avahi-daemon socket:[18510]
3827 /usr/sbin/avahi-daemon socket:[18512]
3827 /usr/sbin/avahi-daemon pipe:[18514]
3827 /usr/sbin/avahi-daemon pipe:[18514]
3827 /usr/sbin/avahi-daemon pipe:[18515]
3827 /usr/sbin/avahi-daemon pipe:[18515]
3827 /usr/sbin/avahi-daemon socket:[18516]
3827 /usr/sbin/avahi-daemon socket:[18518]
3827 /usr/sbin/avahi-daemon anon_inode:inotify
3827 /usr/sbin/avahi-daemon socket:[4901]
3827 /usr/sbin/avahi-daemon socket:[4902]
3827 /usr/sbin/avahi-daemon socket:[4903]
Thanks. I am able to reproduce the same problem on my LePotato ARM board.
Can you grab the output of /proc/cpuinfo on your ODroid and also verify this new build works:
https://channels-kodi.s3.amazonaws.com/2019.10.08.1923/pvr.channelsdvr-linux-armhf.zip
The update didnāt work for the auto-detect, but still works for everything else that I quickly played with. It did work initially but I was guessing it was cached, and when I rebooted it didnāt work.
cat /proc/cpuinfo
processor : 0
BogoMIPS : 48.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 1
BogoMIPS : 48.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 2
BogoMIPS : 48.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd09
CPU revision : 2
processor : 3
BogoMIPS : 48.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd09
CPU revision : 2
processor : 4
BogoMIPS : 48.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd09
CPU revision : 2
processor : 5
BogoMIPS : 48.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd09
CPU revision : 2
CPU info : 290a4000011810000002383448564d50
Serial : 1f516caf-3afd-41cd-9e00-001e064230f9
Hardware : Hardkernel ODROID-N2
Revision : 0400
1 Like
Great, thanks for testing.
The discovery issue is due to broken avahi-daemon configuration. I've submitted a fix here: https://github.com/CoreELEC/CoreELEC/pull/221
Will see if there is any workaround we can use in the mean time.
2 Likes
Anybody found a skin that has a nice epg display? All I've tried have had poor to mediocre guide displays (only shows a few channels at a time and text too large so that show names are cut off). This is on the sheild.
Thanks,
Bobby