Samsung Smart TV - upload application on tv for testing - samsung-smart-tv

I wrote simple app for Samsung Smart TV and now I want to upload it to TV for testing purposes. According to this article http://www.samsungdforum.com/Guide/art00013/index.html everything seems to be very easy but in my IDE I can't find "Samsung Smart TV" menu. I've also heve not found button responsible for packaging app. Any help? I've downloaded the newest IDE from samsung web site.

It seems SDK 5.0 beta removing that magic menu, that's bad decision because that's the best shortcut to do everything for TV Apps Development.
To package the application you can do this:
Right Click on Your Project
Click "Export"
Expand the "Samsung Smart TV Apps"
Click "Package file" and Finish
The usual packaging window will show.
To setup the packaging/SDK configuration is:
Open "Window" menu bar --> "Preferences"
Expand the "Samsung Smart TV" menu and usual configuration window available there

I haven't found how to package app using eclipse but I used this solution https://stackoverflow.com/a/13840964/2069368 and it works. All I've done was to zip application, put it in apache www dir and create widgetlist.xml.

Related

Plugin nativescript-mapbox is not included in preview app on device

Plugin nativescript-mapbox is not included in preview app on device
tns plugin add nativescript-mapbox
anyone experiencing this?
It means exactly what it says. The Nativescript Preview app only has a limited number of libraries installed, making it usable only for basic, simple apps.
The Preview app comes with a predefined set of NativeScript plugins. If your app > utilizes a plugin that is not present in the Preview app, you will see a warning > message and your app might not work as expected.
tns preview documentation
The best solution while developing your app is to use emulators.
As a side note, from my experience, I've found that the iOS Preview app has more plugins and generally works better.

What browser opens a PWA when it is launched from home screen app icon

I am examining PWA and Web Components technologies recently. As far as I have learned now Web Components is a new suit of tech,
Custom Elements, Shadow DOM, HTML Templates and HTML imports. Together with those Web Components enabling techs Web App Manifest, Service Workers, and certain performance improvement techniques used to make what is called as Progressive Web Applications.
What I wonder is when one "Adds to Home Screen" an application in a certain web browser what is the browser that opens it when it is launched from its home screen icon? Is it the browser it has been added to home screen from, or it is the default browser of the system no matter which browser it has been added to home screen from, or it is just a generic web view available on the host operating system at the moment like the one used in native web applications?
Lastly, is it possible for a developer coding her/his app to choose one?
Currently, for me, these combinations open a new "Standalone" window
I believe Android/Chrome is the only one that installs a WebApk
All the others are just shortcuts to open your website in that browser without the normal browser navigation items
I know of no options for the developer for how the shortcut opens your PWA
Android 8.10 - Chrome 67
Android 8.10 - Chrome (beta) 68
Android 8.10 - Edge 42
Android 8.10 - Opera 43
iOS 11.4 (simulator) - Safari
As test I created app shortcut of site https://pwa.rocks from browser:
Brave
Firefox
Chrome
and found that there were 3 different shortcut created for each of the browser. Launching each shortcut resulted in opening the respective browser that created it.
I believe there is no way of changing the default browser to launch the app by coding something in the app. I could not find a way of doing that, if someone knows how to do it, I will be interested to know about it
Here is similar question: What browser will PWA (Progressive Web App) use after adding to home screen?

Struggling to unleash the power of Chrome kiosk apps

Our company designs museum and visitor center exhibitory, and my main job is designing touch screen kiosk applications. Enamored by Vidya's introduction to Kiosk Apps using Chrome boxes, I quickly had my boss procure one for testing. I have since gained a firm grasp of Chrome App structure going though Google's tutorials (manifest files, MVC, etc) and have found the performance of our little HP Chromebox plus HTML5 development to be pretty impressive. I'm developing on my Macbook using Chrome Canary to run and test the apps.
I'm adding in this background information so you can better understand my goals. We of coarse need these apps to launch full screen upon power up. No login or user installation is desired. I prepare the boxes in my office, install them at the exhibit, the end. We certainly don't want our multimedia apps to be sitting up on the Chrome Web Store for others to download and install.
So, I've gotten to the point where I want to install a simple kiosk app on our HP Chromebox. Unfortunately Vidya did not go into detail on this part. The page from her article only touches upon adding kiosk_enabled" : true to the manifest file.
So here's what I've tried so far: I've moved my app folder onto an SD card and moved it from there onto our HP Chromebox into the "Downloads" folder (apparently the only folder). I sign into Chrome Browser on the box with my company account (do I have to do this?) and load up chrome:extensions. I click "load unpacked extension..." and select my app folder. The app installs and I am able to manually launch it by clicking "Launch". Next, I click the "Manage kiosk applications..." button and enter the app ID into the field. This is where I get stuck. Clicking "Add" produces an "Invalid Application" error.
Looking around the web I have found lots of confusing information:
I must "Wipe" the Chromebox in order to use a Ctrl+Alt+K key command to truly enable kiosk mode. (Google's instructions on how to do this stops with Samsung and Asus 'boxes, I have an HP, not to mention the "Manage Kiosk Applications" button is already visible to me).
I must upload my App to the Webstore as either public or unlisted, and then download and install it onto my Chromebox. Really? I don't want to sell my app or make it available to anyone. It is only meant to run in our exhibit. Our apps could be gigs of data with HD videos!
I must make my Chromebox "Managed" or "Enterprise" or "Enroll" it for Work and Education Administration. In most cases, we'll be installing one or two of the 'boxes to allow users to navigate though static HTML pages. I don't have a need to manage a fleet remotely (at least not yet). So, the aforementioned complications seem unnecessary, and expensive if I understand things correctly.
Can someone point me to the definitive process for achieving my goal of an auto starting, full screen kiosk application on my Chromebox?
I'm not an expert on this but kiosk apps are defined by "kiosk_enabled": true in manifest.json. What's important to know, though, is that from what I've seen they can work in three different modes:
If they are installed as an unpacked extension (for example, in development) they will be available as apps in your logged in environment and run but full screen mode. They're essentially "normal" apps except that they are full screen.
If they are installed using the "Manage kiosk applications..." button then they are available without logging in. On the log in screen at the bottom you'll be able to see the app and click to start it without logging in. However they won't start automatically. AFAIK you also can't load an unpacked extension in this way.
If you enable "kiosk mode" for Chrome OS then you can make kiosk apps auto start. At least on the Asus CB you do have to do the CTRL-ALT-K keystroke BEFORE you log in for the first time. This is for an unmanaged device. Now, when you load the app using "Manage kiosk applications..." in chrome://extensions and hover your mouse over it in the dialog you should seen a "enable auto-start" or similar button. You need to select this. Now, when you restart the system the app should automatically start. If you want to cancel this just as the app is loading you can press CTRL-ALT-S. A message indicates this on the screen, too.
Hope that helps,
Simon
Can't help you with anything related to kiosk, but you can generate a CRX file from the Extensions page on your development system, get that onto the Chromebox, put the Extensions page of the Chromebox into developer mode, and then drag the CRX to the Extensions page and drop it. You should see a dialog asking you if you want to install it. This is a completely different form of install than loading an unpacked extension and may get around whatever limitations you're seeing.
UPDATE: (1) Extensions page on Chromebox doesn't have to be in Developer Mode, (2) CRX to be dragged must be in the Downloads directory, not on Google Drive. Didn't test external device (SD card or USB drive).
In order to add your app from Manage Kiosk Applications, you will need to publish your app to the Chrome Web Store. If you don't want your app to be public you can publish it as Unlisted, which means that anyone with the link can install it. Unfortunately, if the app is published as Private you will not be able to add it as a kiosk app. [source]
Beyond that, the only thing you need to do to create a kiosk app is to include "kiosk_enabled": true in your manifest.json file.

GoogleTv Emulator Basic Text Entry

I recently set up my googleTV emulator on Ubuntu 12 Desktop edition. Added Android SDK and the ADT plugin for Eclipse. When I start the emulator, I see the google Icon and some buttons as expected with 4 other icons on the TV screen.
When I do select the TV option,I am propmted to enter the ZIPCode for LiveTV. Thats when I realised that I cant enter text using my keyboard!
My direction keys are working with the simulator for navigation but I just cant enter the ZIP code / Search Text .
Has anyone experienced the same issue ?
Please file an issue at http://code.google.com/p/googletv-issues/ and I will have someone look into it. AFAIK this was working correctly - can you provide some more detail on your system setup? SDK versions, any recent library updates etc.

Android 2.2: Where is the option for speech input in the emulator?

My Nexus One has it:
Settings includes a "Voice
recognizer settings" in the list of
"Voice input & output settings".
Google Search has a microphone
button next to it, so when I touch
it, a dialog prompts me to say what
I want to search.
On the emulator (API level 8, Android 2.2) however, any of the above is nowhere to be found.
Isn't voice search part of Android 2.2? If so, why is it found on my Nexus One (Froyo) but not on the emulator?
What do I need to do to make at least the "Voice input & output settings" available?
Update 1: I followed the instructions for creating the recognizer-enabled AVD as suggested below, but I still receive the "Recognizer no present" message:
What else do I need to do?
Is it possible that despite installing Google APIs by Google Inc., Android API 8, revision 2 and creating a special AVD with it, I still need to install the Voice Search app from the Android Market?
Update 2: I followed Michael's correction to install Google's Voice Search app. This solved the "Recognizer no present" problem but now I am presented with a new problem:
The app's suggestion "Speak again" is bogus: Speaking again presents the same error message over and over again.
In your emulator image, can you install Google Voice Search as in Converting speech to text. The app is in the marketplace at https://market.android.com/details?id=com.google.android.voicesearch&feature=search_result. I think this is the only way to add the Recognizer Intent. Recognizer is not part of the base Android, it is considered an additional component that ships with Google Voice Search and is included in some phones.
I thought that including the Google APIs in your emulator target image would work, but it appears that I was mistaken. I thought you needed to build the target to include "Google APIs" since this capability is not core android, but an additional Google feature.