[mythtv-users] Major Issues with new Nvidia Shield 9.0 upgrade to Android 11

[glen]

On Mon, 2022-01-17 at 11:28 -0500, Peter Bennett wrote:
> 
> On 1/17/22 9:41 AM, glen wrote:
>  
> > 
> > On Mon, 2022-01-17 at 09:35 -0500, James Abernathy wrote:
> >  
> > > 
> > >  
> > > On Mon, Jan 17, 2022 at 9:27 AM Peter Bennett
> > > <pb.mythtv at gmail.com> wrote:
> > >  
> > > > 
> > > > On 1/16/22 3:24 PM, James Abernathy wrote:
> > > >  
> > > >  
> > > > > 
> > > > >  
> > > > > On Sun, Jan 16, 2022 at 3:07 PM glen <glenb at glenb.net> wrote:
> > > > >  
> > > > >  
> > > > > > i had terrible results on the 9.0 and very happy to be back
> > > > > > on 8.23, the myth apps, both, play really well. i'm sure
> > > > > > nvidia will get the interlaced content issue resolved so i
> > > > > > plan to keep an eye on the forums and try again when it
> > > > > > looks like the coast is clear. it was fairly simple to
> > > > > > reflash using their recovery image.
> > > > > > 
> > > > > >  
> > > > > >  
> > > > > > > 
> > > > > > > Just to add my experience with the 9.0 update, I have v30
> > > > > > > backend and a v30 frontend and after the update I have
> > > > > > > audio sync issues with both recorded and live tv (paused
> > > > > > > a few seconds).  It's like the video is occasionally
> > > > > > > choppy, and the audio fluctuates from almost synced to
> > > > > > > maybe a half second off.  I haven't tried playing with
> > > > > > > any video settings yet, I have a v31 apk to try as
> > > > > > > well.  
> > > > > > > 
> > > > > > > On first launch I get a "this app was built for a
> > > > > > > different version of android" message, if I build from
> > > > > > > source will it fix that?
> > > > > >  
> > > > > 
> > > > > For those who somehow got 9.0 installed and now regret it,
> > > > > like Glen says it's easy to put 8.23 back on the Shield. I
> > > > > summarized what I did with Glen's help in a posting on the
> > > > > MythTV forum
> > > > > (http://email.mg.glenb.net/c/eJxFjssKgzAQRb8m7ho0M3ktsigU_yOJExW0hhgt_ftKuyjcxeHAgTu4mPwgsZkddBC1QpQkycfUInlPFn0H1hoplbTaGJUUj36lhWE7LvQM_Em1mZwIgxgERjABolHkpdFWpyBaAwgqNIubas07gzsT_bW0lWPl67tO9eRbGS91zvSqW54jz1Nm0CcGD9RMqPoFbJvifsHt2Kns14V__wFdZD25).  So
> > > > > it's there when I have to do it again and forget where to
> > > > > start.
> > > > > 
> > > > >  
> > > > I did the upgrade. I checked leanfront and mythfrontend. I did
> > > > not see any problems with playback. I played parts of a few
> > > > recordings with mythfrontend and did some skip forward and
> > > > back. I watched for a half hour with leanfront.
> > > > I do not have any mpeg-2 recordings. They are all h264. Perhaps
> > > > mpeg2 is the issue.
> > > > Peter
> > > >  
> > > 
> > > Right, Peter, MPEG2 is the problem. Not so much with mythfrontend
> > > since it has its own version of ffmpeg for OpenGL to use, and
> > > that's what I use as my video profile. But Leanfront in v9 is not
> > > nearly as good a mythfrontend or as good as Leanfront was back on
> > > 8.23.  I did the rollback and things are good again.
> > > 
> > > Jim A
> > > 
> > > _______________________________________________
> > > mythtv-users mailing list
> > > mythtv-users at mythtv.org
> > > http://email.mg.glenb.net/c/eJxNjkEOwiAURE9TdhJaPhQWLNx4jy98WhKgpqCJt7caE01mM29mkgnORwwKWHJylH7WAIoUoY8CCJEs4CitNUppZWdjdNTcY6E8gFgy1Suv1NnqaAxW-hCQZtIetBhtUBomaywImgPLbu39NsjzMF0O5dR64-XZ1_7g274cqGDKBes3TDVub_hpnO6N9sZ292-PB7_9C5QRQE4
> > > http://email.mg.glenb.net/c/eJxFjTsOwjAQRE8Td1hx_IlduKChgjNEi71OLJwAyQbE7bFEgTTF6GmeJvqQIGrFspdCht4opVEjhNQqBECnQEjnrNZGu95akwwPMGNpVDsWXK58QWKThyiCdEYEm1KtrU0KuhhlEM7J3gRW_ET0aOSx6U4173zLfP7QRC9-X8dKLpBLXsbhnDcakPJzRyJkq_-tDvuG61Zf_9IX1bs8jQ
> > > MythTV Forums: http://email.mg.glenb.net/c/eJxFjMsKwyAQAL8m3ipRd9U9eOil_-FjTQp5FGMK_fsGeijMZRiYEnKNBUE8g1EmOwuAjBxzHYFjZIKoDJFHtEjOe1utzHHlZYBxWnhLcuMu5qC8q9YVg1qppCFBzaqA0w4pE3ESS5h7fx2DuQ_6cVH3dq5y_fS5v-XeJtHCT27nwe249v_2BZKDMyw
> > 
> > my experience different from Jim, the mythfrontend was worse. when
> > i changed profile from mediacodec to ffmpeg (standard decoder), it
> > would barely play at all and was not watchable. Jim is on the 2017
> > shield and my experience on the 2019 shield pro. that may be the
> > difference. reverting back everything great again. I will keep an
> > eye on the forum at nvidia also and let you know when they indicate
> > they have worked out the interlacing issue. 
> > 
> > 
> I think manufacturers are not very interested in MPEG-2. Google makes
> MPEG-2 optional in android, while h264 and others are required. My
> phone from 2016 would play MPEG-2 with leanfront without a problem.
> My 2021 phone (same brand) does not support MPEG-2. It seems MPEG-2
> is being phased out. No reasonable streaming service would use MPEG-
> 2.
> Peter
> 
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://email.mg.glenb.net/c/eJxNjkEOwiAURE9TdhJaPhQWLNx4jy98WhKgpqCJt7caE01mM29mkgnORwwKWHJylH7WAIoUoY8CCJEs4CitNUppZWdjdNTcY6E8gFgy1Suv1NnqaAxW-hCQZtIetBhtUBomaywImgPLbu39NsjzMF0O5dR64-XZ1_7g274cqGDKBes3TDVub_hpnO6N9sZ292-PB7_9C5QRQE4
> http://email.mg.glenb.net/c/eJxFjTsOwjAQRE8Td1hx_IlduKChgjNEi71OLJwAyQbE7bFEgTTF6GmeJvqQIGrFspdCht4opVEjhNQqBECnQEjnrNZGu95akwwPMGNpVDsWXK58QWKThyiCdEYEm1KtrU0KuhhlEM7J3gRW_ET0aOSx6U4173zLfP7QRC9-X8dKLpBLXsbhnDcakPJzRyJkq_-tDvuG61Zf_9IX1bs8jQ
> MythTV Forums: http://email.mg.glenb.net/c/eJxFjMsKwyAQAL8m3ipRd9U9eOil_-FjTQp5FGMK_fsGeijMZRiYEnKNBUE8g1EmOwuAjBxzHYFjZIKoDJFHtEjOe1utzHHlZYBxWnhLcuMu5qC8q9YVg1qppCFBzaqA0w4pE3ESS5h7fx2DuQ_6cVH3dq5y_fS5v-XeJtHCT27nwe249v_2BZKDMyw

agree as far as i know. all the more reason for people still using ota
antennas in mpeg2 not to upgrade the shield and other android boxes
probably. the new atsc 3.0 should be fine as that is target codec 265.
that still comes down to the default though. i may nevertheless pick
the silicondust 3.0 tuner as 3 stations have popped up in my area.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20220117/0a26957c/attachment.htm>