Psosmith82 Posted January 21, 2021 Share Posted January 21, 2021 6 hours ago, Cyknight said: Nice - probably will revoke it and that's why the driver wasn't just encrypted and republished right away. What could people do with it with an exposed key? Will the driver stop working for people that installed it before it was pulled? When re-released, will it require a driver update or will a new driver have to be inserted from scratch? ] I am just a user, not a programmer Quote Link to comment Share on other sites More sharing options...
tmj4 Posted January 22, 2021 Share Posted January 22, 2021 Well, FWIW, I've pinged Nvidia Shield support and asked them when they expect to have the driver available again. Have yet to hear back. Quote Link to comment Share on other sites More sharing options...
Cyknight Posted January 22, 2021 Share Posted January 22, 2021 3 hours ago, Psosmith82 said: What could people do with it with an exposed key? Will the driver stop working for people that installed it before it was pulled? When re-released, will it require a driver update or will a new driver have to be inserted from scratch? ] I am just a user, not a programmer Hack, and yes, the 'current' driver would stop working if the key gets changed Quote Link to comment Share on other sites More sharing options...
Cyknight Posted January 22, 2021 Share Posted January 22, 2021 33 minutes ago, tmj4 said: Well, FWIW, I've pinged Nvidia Shield support and asked them when they expect to have the driver available again. Have yet to hear back. I doubt they'd even know, as this would be the engineers dealing with it. Quote Link to comment Share on other sites More sharing options...
Cyknight Posted January 22, 2021 Share Posted January 22, 2021 9 hours ago, DanITman said: It will probably be a while. Not necessarily. The DRIVER would be the least of the concern , merely put a new key in. With the key exposed, it's likely they'll (want to) bring out a firmware update pretty quick too. So it could be a matter of a week or so. That is of course assuming that was the issue - not saying it isn't true, just mean to say I've only seen that piece of info on here, from you. Quote Link to comment Share on other sites More sharing options...
zaphod Posted January 22, 2021 Share Posted January 22, 2021 An earlier post says that Nvidia forget to encrypt the driver. Does that mean you can see all of the Lua source code in the driver? Quote Link to comment Share on other sites More sharing options...
Cyknight Posted January 22, 2021 Share Posted January 22, 2021 1 minute ago, zaphod said: An earlier post says that Nvidia forget to encrypt the driver. Does that mean you can see all of the Lua source code in the driver? Not by default, but possibly yes. That said, that doesn't mean you can reverse engineer a new driver - or that it would give you any more valuable info other than the key. One assumes the commands sent etc in and of themselves are basic code - it's how the Shield handles it that matters, and once the key gets changed, non of it matters anyway. Quote Link to comment Share on other sites More sharing options...
zaphod Posted January 22, 2021 Share Posted January 22, 2021 It is still interesting to see the code. I really wish all of these types of devices would have a simple, open API like the Roku API where you can do something like http://192.168.1.101:8060/query/apps in a web browser and get a list of inputs and installed channels. Quote Link to comment Share on other sites More sharing options...
Cyknight Posted January 22, 2021 Share Posted January 22, 2021 1 hour ago, zaphod said: I really wish all of these types of devices would have a simple, open API Hey, I'm not saying no to that, but then again, it would be great if everything was free as well and we all had everything we wanted, no strings attached of course Quote Link to comment Share on other sites More sharing options...
RyanE Posted January 22, 2021 Share Posted January 22, 2021 12 hours ago, zaphod said: I really wish all of these types of devices would have a simple, open API like the Roku API where you can do something like http://192.168.1.101:8060/query/apps in a web browser and get a list of inputs and installed channels. In an ideal world, that'd be great, and I completely agree for partners that can do that. Some manufacturers (like Dish) have a non-public API because the API can expose customer data (subscribed channels, recorded items, watching status data, etc.), so it's a privacy / liability issue. RyanE Quote Link to comment Share on other sites More sharing options...
DanITman Posted January 24, 2021 Share Posted January 24, 2021 On 1/21/2021 at 9:26 PM, Cyknight said: Not necessarily. The DRIVER would be the least of the concern , merely put a new key in. With the key exposed, it's likely they'll (want to) bring out a firmware update pretty quick too. So it could be a matter of a week or so. That is of course assuming that was the issue - not saying it isn't true, just mean to say I've only seen that piece of info on here, from you. Yes, it’s true. I reported it to @RyanE Unless nvidia had other keys already on the shield, it will require a an update to make a new key work. It will also require an update to revoke the existing key. Quote Link to comment Share on other sites More sharing options...
DanITman Posted January 24, 2021 Share Posted January 24, 2021 On 1/21/2021 at 5:51 PM, Psosmith82 said: What could people do with it with an exposed key? Will the driver stop working for people that installed it before it was pulled? When re-released, will it require a driver update or will a new driver have to be inserted from scratch? ] I am just a user, not a programmer They could write an integration without nvidia’s approval. The api is not public and it was also exposed without the driver being encrypted. Quote Link to comment Share on other sites More sharing options...
tmj4 Posted January 27, 2021 Share Posted January 27, 2021 Just a quick update: This is where Nvidia has stated they will inform us when the driver is released again: https://www.nvidia.com/en-us/geforce/forums/shield-tv/9/428887/shield-span-classhighlightcontrol4span-driver-temp/ Quote Link to comment Share on other sites More sharing options...
TikiTat Posted February 16, 2021 Share Posted February 16, 2021 Updated driver available as of 2/10/2021. The Control4 driver for SHIELD TV is now available. To make sure your SHIELD is compatible with the new driver, make sure you have downloaded the latest “SHIELD TV Remote Services” app from the Google Play Store on your SHIELD. If you have set up Control4 for SHIELD TV previously, you will need to update your SHIELD TV Control4 driver. c44me and Matt Lowe 1 1 Quote Link to comment Share on other sites More sharing options...
enzeder Posted February 16, 2021 Author Share Posted February 16, 2021 Do we have e a long press option on the new driver? Quote Link to comment Share on other sites More sharing options...
tmj4 Posted February 18, 2021 Share Posted February 18, 2021 Anybody having any issues with this driver and potentially causing issues with inputs/AVRs? Since getting this new driver installed and configured with the mini-apps, anytime I switch between the mini apps, my Denon AVR powers off and back on. Quote Link to comment Share on other sites More sharing options...
eggzlot Posted February 18, 2021 Share Posted February 18, 2021 1 minute ago, tmj4 said: Anybody having any issues with this driver and potentially causing issues with inputs/AVRs? Since getting this new driver installed and configured with the mini-apps, anytime I switch between the mini apps, my Denon AVR powers off and back on. CEC disabled on the AVR and the Shield? Maybe the update somehow put the CEC back on the shield? Quote Link to comment Share on other sites More sharing options...
tmj4 Posted February 18, 2021 Share Posted February 18, 2021 Just now, eggzlot said: CEC disabled on the AVR and the Shield? Maybe the update somehow put the CEC back on the shield? Yeah--CEC is disabled in the entire chain. I know something is coming from somewhere w/in C4, however, as in looking at the Lua log for the AVR, it's showing that it's getting a serial command from somewhere to power off and then power back on. Quote Link to comment Share on other sites More sharing options...
adam333 Posted February 20, 2021 Share Posted February 20, 2021 weird,,, cant control anything on the shield. I installed the nvidia remote services...disabled all the CEC stuff on the shileld and cant control it. works fine from the shield remote...nothing from c4 remote. brand new shield, updated firmware new c4 driver was installed. Quote Link to comment Share on other sites More sharing options...
Neo1738 Posted February 20, 2021 Share Posted February 20, 2021 14 minutes ago, adam333 said: weird,,, cant control anything on the shield. I installed the nvidia remote services...disabled all the CEC stuff on the shileld and cant control it. works fine from the shield remote...nothing from c4 remote. brand new shield, updated firmware new c4 driver was installed. Might need to input shield IP into driver for it? Quote Link to comment Share on other sites More sharing options...
msgreenf Posted February 20, 2021 Share Posted February 20, 2021 31 minutes ago, Neo1738 said: Might need to input shield IP into driver for it? Nope. It's sddp Quote Link to comment Share on other sites More sharing options...
pdapice Posted February 20, 2021 Share Posted February 20, 2021 ok, i have the new driver installed and connected via SDDP works pretty well, however even after deleting my mini-apps and downloading the updated ones, i cannot seem to get them working. i have them connected but the audio path still says NO for all of the mini apps. i have checked and rechecked but can't seem to figure out what step i have missed. anyone else with this problem? or a solution? Quote Link to comment Share on other sites More sharing options...
tmj4 Posted February 20, 2021 Share Posted February 20, 2021 6 minutes ago, pdapice said: I have them connected but the audio path still says NO for all of the mini apps I noticed the same thing the other day as well and figured this was the reason my AVR was freaking out (mentioned above and in another thread). The driver works well for switching between the apps, control of the device, turning on and off devices, but every mini-app switch triggers my AVR to turn off and on instantly. Quote Link to comment Share on other sites More sharing options...
didiasku Posted February 25, 2021 Share Posted February 25, 2021 On 2/20/2021 at 12:51 PM, pdapice said: ok, i have the new driver installed and connected via SDDP works pretty well, however even after deleting my mini-apps and downloading the updated ones, i cannot seem to get them working. i have them connected but the audio path still says NO for all of the mini apps. i have checked and rechecked but can't seem to figure out what step i have missed. anyone else with this problem? or a solution? Try this...cause i had some issues with the v103 driver and the only way to clear them up was this. Go to your network tab on composer, right click and disconnect the shield Go on the shield, go to settings and your apps, show system apps. Find the "Shield TV Rremote" app. Stop it, clear data and uninstall updates. Re-install "Shield TV remote" app/Update it Reboot Shield Once booted, go to connections on network tab in composer and drag the SDDP back onto your 'disconnected' shield device reboot the shield one more time I have 2 shields that stopped working with the v103 driver and this was the only way to clear it up Quote Link to comment Share on other sites More sharing options...
ps0ps Posted February 26, 2021 Share Posted February 26, 2021 If only they mapped the guide button as well like every other driver. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.