Gambled trying Channels on Nvidia Shield. So far aside from no DRM support its stable.
Problem is I installed DVR on my Windows server and restarted app numerous times on my Shield and it is not being detected.
You can switch to the beta Channels app which offers DVR browsing and playback features. Scheduling and other DVR features will come later this year.
appreciate the quick reply but concerns are stability…will this app be as stable…already spent money for features that were supposed to be with current app I purchased and was not disclosed had to sign up after paying for beta software.
I will give it a try…but if stability issues arise I want to know how we can rectify this.
The beta is considered stable and the DVR features in the beta will be shipped to the store version next week.
On https://getchannels.com/androidtv/ DVR support is listed as “coming soon”. The screenshots and description of the Channels app on the Play store make no mention of DVR support. Obviously we aren’t doing a good job of communicating this if you were still confused- how can we make it more clear?
Description makes no mention but with DVR app advertised below but implies it has the capability for that function. And did not see mention of inability to play to Android device with DVR server for Windows during download or install. Dont take me the wrong way…dont want to come across wrong…app seems more stable for me than HDHomeruns own app…just wish it was more clear is all before I spent the money.
Thanks, we can certainly make things more clear on the DVR page. I will make a note to do that this week.
If you’re not satisfied with your purchase, you can get a quick refund from the Play Store.
Appreciate the offer but would rather see it through first. I reinstalled beta on Shield. I now see DVR section…but is empty…and no way I can see to schedule recordings. I am assuming it is not detecting the DVR server. Just sent logs from app.
My first thought is I only see Bonjour as way to announce on network.
At the moment the beta only offers playback of recordings (including commercial skip). To schedule recordings or setup passes you would need to use the DVR’s web UI.
Ok If the app passes the 24 hour continuous play test I dont mind having spent 25 dollars. The DVR option is not worth it to me currently as implemented. Couple suggestions…make mention on Google Play, Amazon, and your website that the Android TV version does not support all the current features as the iOS version and list the differences.
Also I noticed on Windows DVR it could not detect my router…Netgear X10 R9000 for upnp port forwarding.
Also one question…I noticed it mentioned I believe adjust flow control change for network adaptor on install of DVR. Was it wanting disable or enable flow control for best streaming? I let it set it the way it wanted…but just for my own future reference. Thanks and lets hope you get your app ready for prime time. Am looking forward to it.
1 Like
One last suggestion…allow direct stream instead of transcode for remote streaming from DVR remotely…some of us are spoiled with fios gigabit 
If you hit any bugs, let us know and we will fix them.
Okay good to know. Some routers have finicky upnp or natpmp implementations.
Disable Ethernet flow control. It is an antequated protocol and not necessary since TCP does its own flow control.
Unfortunately browsers cannot play mpeg2, so transcoding to h264 is required. The iOS app lets you stream directly even remotely as it can decode and play mpeg2.
As a GoogleFibre user in the same boat, I have found that despite my 1gig uplink, my remote client doesn’t get the same generous down speed, and that I’m often watching in 720/4Mb for hotels and other places.
On mobile, although I’m not billed, I do it to save my firm some money since they pay my bill.
Just submitted logs couple minutes ago. Was tuned to channel 689 and around 3PM my wife said screen was frozen. Could have been operator error though. Let me know if you see anything when you get time. Thanks
Just froze again on channel 500…logs submitted
Logs show constant buffering. Seems like an unstable network connection on the SHIELD. Is it on wifi?
Everything hard wired Cat6. Each room has separate switch. Room shield is in is using an R7000 as an access point/switch. Main hub is an R9000 connected using LAG to 2 S8000 switches also LAG,d together.
To start if I just bypass the r7000 and plug shield straight to rest of network would it show immediately if corrected in logs?
Is there a way I can view the logs? I dont want to waste your time troubleshooting my network piece by piece if thats where the problem lies.
http://IP_OF_SHIELD:57000/log
I pasted a snippet of log below…audio glitch triggering hiccup resulting in buffer run out.
I will forward the total logs to you from app in a few minutes. FFMpeg issue?
I find this is an issue across different apps, but yours is more tolerant…using larger buffer perhaps?
03-05 18:13:03.027 13685 13695 I art : Background sticky concurrent mark sweep GC freed 35625(1443KB) AllocSpace objects, 0(0B) LOS objects, 13% free, 103MB/119MB, paused 514us total 186.048ms
03-05 18:24:21.050 13685 13695 I art : Background sticky concurrent mark sweep GC freed 32941(1335KB) AllocSpace objects, 0(0B) LOS objects, 13% free, 103MB/119MB, paused 8.515ms total 20.636ms
03-05 18:29:12.988 13685 8413 V Streamer: overflowed 0 (pos: 3581517002, time: 2252s)
03-05 18:29:13.495 13685 13724 E mpv : [ffmpeg/audio] ac3: expacc 125 is out-of-range
03-05 18:29:13.496 13685 13724 E mpv : [ffmpeg/audio] ac3: error decoding the audio block
03-05 18:29:13.496 13685 13724 E mpv : [ffmpeg/audio] ac3: frame sync error
03-05 18:29:13.496 13685 13724 E mpv : [ad] Error decoding audio.
03-05 18:29:13.510 13685 13724 W mpv : [ad] Invalid audio PTS: 2252.000000 -> 0.032000
03-05 18:29:13.510 13685 13724 W mpv : [cplayer]
03-05 18:29:13.510 13685 13724 W mpv : [cplayer] Audio/Video desynchronisation detected! Possible reasons include too slow
03-05 18:29:13.510 13685 13724 W mpv : [cplayer] hardware, temporary CPU spikes, broken drivers, and broken files. Audio
03-05 18:29:13.511 13685 13724 W mpv : [cplayer] position will not match to the video (see A-V status field).
03-05 18:29:13.511 13685 13724 W mpv : [cplayer]
03-05 18:29:13.576 13685 8424 E libOpenSLES: frameworks/wilhelm/src/android/AudioPlayer_to_android.cpp:1152: pthread_mutex_lock_timeout_np returned 110
03-05 18:29:13.597 13685 8424 E libOpenSLES: frameworks/wilhelm/src/android/AudioPlayer_to_android.cpp:1152: pthread_mutex_lock_timeout_np returned 110
03-05 18:29:13.627 13685 8424 E libOpenSLES: frameworks/wilhelm/src/android/AudioPlayer_to_android.cpp:1152: pthread_mutex_lock_timeout_np returned 110
03-05 18:29:13.632 13685 13724 V mpv : event: unpause
03-05 18:29:13.632 13685 13724 V mpv : [cplayer] Enter buffering (buffer went from 100% -> 0%) [-1.000000s].