Problem - 1)Use of Android CAS framework to add "Security" for IPTV boxes
2)if i use this framework, will it work with widevine library
3) can we also generate our keys for encryption and decryption?
4) Each CAS guy like verimatrix, NSTV may have used different ways of encryption in
DVB-headend to encrypt the Video content, so how is this framework help me in extracting those keys on Android box side? OR what CAS i need to use at headend to make this framework work for securing IPTV content that is transmitted using UDP protocol?
5) Does it work on any specific Android/google certified chipset OR any SOC is fine?
We first need confirmation if this CAS framework is for Android TV framework
OR can be used on AOSP boxes.
what is restriction and do we have sample code anywhere for us to try?
Related
I am a flutter developer, I want to make an application to exchange messages and files by using NFC technique
I used nfc_in_flutter plugin for reading and writing NFC tags but I don't know how to send and receive data and files between devices by using NFC in flutter.
Could any one help me, please?
Generally you don't try and send data between 2 devices using NFC, there is a standard for it, but most devices don't support it (it has never been supported on iOS and Android has dropped support for it as it was unreliable)
Use Bluetooth or Wifi Direct instead.
Update:
If you have to use NFC then the nfc_in_flutter plugin is no use, you are going to have to call native code for each platform yourself / write your own plugin.
And for 2 iOS devices, then forget it, just not possible because of what the OS supports.
When one device is an Android there is a complicated method that some people have had some success with but it still has it's issue.
The Android device does Host Card Emulation (HCE) and pretends to be a really Type 4 NFC tag, then other devices can read/write to it as if it were a real Tag which both iOS and Android Support. BUT on older Android devices then the deprecated Android Beam might get in the way and you would need to use enableReaderMode to do the read/write on Android.
You will need to put in a lot of error handle in the read/write App as NFC comms is very slow and very prone to loosing the connection, so it would have to handle loosing the connection and restarting where it last successful read from/written to.
All these problems make this extremely difficult to achieve a workable solution and was the main reason Google removed Android Beam for Android to Android sharing (which does use a NFC peer to peer protocol)
Capacitor allows us to code once then generate web, Android and iOS applications. Most people using Capacitor will generate native Android and iOS applications.
But strange enough, I can't find any documentation about how to create automated-tests for the two native applications. I can easily test the web application using protractor, jasmine or whatever. But when it comes to native apps, I can't hardly rely on native tooling (Android Studio and XCode) as there are other issues preventing me from testing it easily (ex: no possibility to set Accessibility ID through the views markup, etc).
Where are we at with Capacitor native apps automated-tests ?
I believe this is what you are looking for Ionic/capacitor Integrations for Testing
As far as the community/forums and official docs go there are only 3 ways you can test your apks
Native [Andriod Studio / Xcode] [Emulated versions]
Real Devices
3rd party Integration listed in the link above..
Even on google there very less info on this topic.. most of the blogs/ articles only say that Ionic/Capacitors can be tested just like a normal WEB App
I'm really keen to develop a web browser application for Android Wear devices. To make such application I need a WebView object, but the major problem is that Google has made the android.webkit API unavailable in that OS.
Since Android is open-source, is it technically possible to manually include the needed libraries, by coping them from the android source code on GitHub into my project? Are they going to work like as in a normal Android device, and is it legal?
Here is the link to the API I'd like to use.
Developing a browser based on WebView is not a good idea anyway. Although historically Android Browser was based on WebView, it had to use a lot of hidden APIs in order to work. All more or less functional browser apps based on WebView have to do the same, which makes them fragile. Also, the resulting browser app will not be as secure as a real multi-process web browser.
A better idea is to take Chromium and build it using Wear SDK. And there is already one built this way.
You don't have access to a complete source for Android Wear to build a complete image.
I am just wondering is it worth to do a cross platform mobile app development using UIWebView (iphone) and Webview(Android)? We need to port multiple web applications as mobile apps for iphone and Android. One of the strategy is to use the UIWebView to render content from server and this content from server is same for Android and iPhone.
Have a you developed using this concept? Is there any limitations you found in it? Such as issues with redirect of web-pages, cookies, java-script library performance etc
So far I see only two issues:
Non availability specific UI design features native to device such as may be rounded corner buttons not available etc
Infrastructure code for handling cookies, sending and receiving information back and forth from server to device.
any advice?
Thank you
Cross platform frameworks are talking similar approach and also adding wrapper libraries to abstract away platform specific functionlity. Check out PhoneGap, Appcelerator and others.
Checkout Pyxis, which is a cross platform mobile app development software.
Is it possible to send GET, POST, PUT and DELETE requests from iPhone || Android applications to a third party server?
I want to build a web service to reuse on all 3 platforms (3rd being the web app itself).
Yes, making HTTP requests on mobile devices running iOS or Android is no different from desktop Java or Cocoa. Both platforms offer API's that enable you to change the request method. Checkout NSURLConnection on iOS and the org.apache.http package on Android.
Well, it's all possible on both iOS and Android OS platforms, however while designing web service, you probably may consider a lightweight implementation as mobile platforms are not powerful enough if you for example intend to use SOAP extensively. My most often choice is REST+JSON.
this is an example of how to implement a webservice call in android:
http://lukencode.com/2010/04/27/calling-web-services-in-android-using-httpclient/