Code is Too old

[JeongHyeok97]

As in the title, your code is too old. . Not only is it outdated, but it's also not stable.
There is no support for providers with channel data at all.
Basically, if you insert channels in tvprovider in the way of companionlibrary, only providers with really few channels can use this method.
As a test, if you use another large xmltv instead of richinput, you will get numerous errors, or the scan time will be in the order of hours. Android seems to have given up on the field of tv development. At the same time, it is not compatible with Live Tv App.
Why are these issues left unresolved in the latest branch?

[swinder0161]

What is your Android Version on TV?
I have moved the code to latest media3 and I donot see functionality issues as such running on android-pie TV.
I have removed the xml parsing part though and do xml parsing on my own since I am using Kodi compatible xml and m3u.
checkout swinder0161/androidtv-sample-inputs branch media3

[JeongHyeok97]

-----Original Message----- From: ***@***.***> To: ***@***.***>; Cc: ***@***.***>; ***@***.***>; Sent: 2023-10-03 (화) 15:40:32 (GMT+09:00) Subject: Re: [googlesamples/androidtv-sample-inputs] Code is Too old (Issue #63) What is your Android Version on TV? I have moved the code to latest media3 and I donot see functionality issues as such running on android-pie TV. I have removed the xml parsing part though and do xml parsing on my own since I am using Kodi compatible xml and m3u. checkout swinder0161/androidtv-sample-inputs branch media3 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread. First of all, I am grateful that you have provided me with an answer to my opinion until the second quarter or at this point. At the same time, I would like to apologize for my ignorant question. I've also been working on a project with 9.0 set-top box like you. Looking back, my complaint was that the Api I receive has a different structure from Google's standard (as used in CompanionLibrary in our company, program and advertising are not separated, but simply send out LiveStream, and in this context, most of the playback information is included in the Channel), and the speed issue of the xml Parsing part. However, this was due to my lack of understanding of the TV industry, and the TestCase I complained about found that the amount of data I had was unusually high compared to the normal provider, causing speed issues on the TvProvider side of Android, not my Rich-based application. Also, my complaint about RichPlayer being low on ExoPlayer version, mostly resolved.Message ID: ***@***.***>

[AlbertEinsteinGlitchPoint]

What about sdk 31 .. to run on androidx ?