Is it possible to let my app start when Apple TV starts? - tvos

I'm wondering if apple allows configuring apple tv for kiosk/digital signage mode, means - let my app always start on system start.
I do not yet have the hardware to try, so I'm asking in advance does it makes sense to try?

Related

questions about oculus quest 2 development or capabilities :

I have 3 questions about oculus quest 2 development or capabilities :
1- first of all is it possible to create an app in oculus quest in order to have shortcuts in the helmet to run specific applications directly after launching the helmet (without going into the main menu, search for the app, ...) ? The purpose of theses quick links is also to switch from App A to App B easily (without to much or complex interactions)
2- Is it possible to avoid the position setup when the quest helmet launches (confirm floor level, or define play area) ? I dont know why but when I restart the helmet, even if the position has not changed beetween my previous experience, I need to redefine floor level and stationary boundary every time.
3- Is it possible to run the cast functionnality automaticaly when we start the helmet ?
Thanks for your help.
Joris
1 - You can launch other apps using deep linking.
https://developer.oculus.com/documentation/unity/ps-deep-linking/
2 - You are seeing guardian setup because it doesn't recognize the area as being the same. This may be due to lighting changes or things getting moved around.
3 - This is not possible to my knowledge. Possibly limited for privacy reasons.

Do tvOS transmissions stay active since there is no drain on battery?

Two part question:
First, does the Apple TV run app activities in the background while it is asleep? I would assume this would be the case since the Apple TV isn't relying on battery.
Second, if this is not the case, how would I override this keep an app running and writing to my database?
I am building an app that connects to Bluetooth LE, then writes to a database after connecting. I would like the Apple TV to be the "hub" for my device. So as long as the Apple TV can stay awake, unlike iOS, I should be fine. I could be looking at this the wrong way. Please feel free to correct me.
tvOS runs the same application state mechanism that iOS does. Meaning it has the same old:
not running > suspended > background > inactive > active
This also means that it will do basic background processing based on very specific background tasks you specify, just like iOS. Though, tvOS does not have a background data-refresh function, which I'd imagine you'd want to use for the scenario you described.
Check out this Apple doc for more modes. https://developer.apple.com/library/content/documentation/General/Reference/InfoPlistKeyReference/Articles/iPhoneOSKeys.html#//apple_ref/doc/uid/TP40009252-SW22
To specifically, answer the question: There may be a way to do some background data work, but it would be very limited; And you can prevent sleep programmatically by doing:
[UIApplication sharedApplication].idleTimerDisabled = YES;
This apple doc will give you all you need to accomplish this.
https://developer.apple.com/documentation/uikit/uiapplication

Windows Phone control tv over wifi

I'd like to create a Windows Phone 8.1 app to connect to a TV and have basic controls (change channels, turn on/off).
I know It's hard to have an universal remote for every TV, but I'm just testing so It could work to a specific model/maker.
My first guess is to connect to a smart tv over wifi connection, but I can't find any site to describe how to do this or how do I start researching. I only got links to apps already made, but not on how to build it.
Anyone knows how this connection works?
Thanks!
i dont think this is really related to Windows phone specific. but here is what you can do:
find out what kind of API the TV has. it's probably some Rest or SOAP based webservice you can call. if there are existing apps (maybe for other platforms) you can use Fiddler to check the network traffic from these apps to the TV if you set your pc as "man in the middle" with fiddler.
as soon as you have what you need look into HttpClient examples on how to send these requests toward your TV.
fiddler :http://www.telerik.com/fiddler
HttpClient: https://msdn.microsoft.com/library/windows/apps/dn298639

Is there any way to extract frames from video stream and process it real time in windows phone

I want to extract frames from live video stream using windows phone 8. I'm grabbing my video stream from a device via bluetooth connection. Also I want to do some image processing with the extracted frames. But this process should run on background and should notify user along with defined situations. I searched though the internet with my requirements, but didn't find any solution that could be use to handle that kind of scenario.
So please let me know, is it possible to implement that kind of application using windows phone 8 SDK? If so, please kind enough to provide some details and directives that I should concern. Otherwise please let me know what are the major issues with my scenario.
Thank you very much.

Prevent stealing HTML5 video in the browser?

I'm looking for a way to securely deliver video to mobile devices. There are two options:
HLS in tag. This works very nicely for iOS and supports adaptive bitrate, perfect for mobile. However, is seems to only work well on iOS. There seems to be only fragmented support for it on Android. I've read that Android has officially supported it since 3.0, but on all the android devices I've tested (>3.0), HLS hasn't played back on the browser.
Progressive download in tag. This will work on iOS and Android devices fine, but the concern is that since it's just a progressive download of the video, that the user find a way to just grab that video once the browser has finished downloading it. This may be more difficult on iOS, but I'm sure it's not that hard to figure out where the browser stored the video download in a tmp folder somewhere.
Either method I'd say can be protected from deeplinking by using an expiring token approach, where the token is generated serverside with a secret key that only the content server knows about. The video request would only be valid for 5 or 10 minutes, would would kill of deeplinking.
Is anyone aware of any way around these issues? Even if I was able to prevent deeplinking, the user could still get the video itself and re-distribute. Perhaps it's just not possible?
Thanks
Rule #1 of the internet:
If you don't want someone stealing it, don't put it online.
Welcome to the circumvention arms race. Brought to you by DownloadHelper.
There's nothing you can do to stop someone who really wants to pirate your video. There are various measures, like those you mention, that make it more difficult, but someone who really wants to copy it could find a way to capture it from memory, or even just point a camera at the screen and record the playback of the video.
It's the same way you protect your car. You install a steering lock, an alarm and an engine immobiliser, and then someone comes alongs and pulls the car onto a flat-bed truck and drives away with it.
Bottom line - you can't stop a determined thief, but you can make theft more difficult so that you're not the most attractive target.
As I was reading the above I could easily get pass all these techniques pretty quickly.
For a project I can't describe too much because of nda, we created our own protocol based on a well known encryption method can't mention that either , military grade) , encoded packets on the server to the protocol, and decoded on the device.
unfortunately this isn't perfect either because a lot of mobile apps can be re-versed engineered and once you get the key game over, very easy on android, of course you could periodically recycle the key, in which case even if they decompiled the android app and got the key it wouldn't work very long.
This is a lot of work and can't be implemented with html5 or hLS or event rtsp.
It also requires a custom server application that takes the video stream re-transmits it with the custom protocol.
On the other hand the protocol was transport agnostic, which meant we could use a variety of transports, tcp, IAP and bluetooth. Also would work on all mobile / desktop platforms.
The other little requirement, is couldn't use a browser, have to be a custom app.