Quantcast
Jump to content

Launch the native Tizen application using Tizen Studio?


Recommended Posts

Is there a way to take the application files from the TV and run it on Samsung's Tizen blu-ray player?

I have a problem with the application from the Samsung Store. Its publisher left version 5 available for my Samsung UBD-M9500 player. This version does not work anymore, but on Samsung TVs it is version 6. The system is the same, so if i had access to the files of this application maybe it could be launched via developer mode on the blu-ray player.

Does anyone know how it can be done?

Link to post
Share on other sites


Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Similar Topics

    • By 4cr4n1x
      When user selects input, keyboard opens and shifts app almost all the way up. Only 10% of app is visible with keyboard on.
    • By Manlyman1992
      There is lots of iptv players but i am really tired of looking to find the one that works with the extension .json.
    • By STF News
      The Remote Device Manager provides a mechanism to deploy a project remotely from Tizen Studio to a Tizen-enabled device, such as Galaxy Watch. Tizen-enabled devices can be connected or disconnected through the Remote Device Manager if they are on the same network. Once the connection is made, a device log is shown in the Log View. You can also use the interface of the Remote Device Manager for executing SDB shell commands.
      Prerequisites: Tizen Studio 2.0 or higher
      Launch a project with Remote Device Manager
      Step 1: Disable Bluetooth
      If the watch has not been upgraded and the Tizen version is below 5.0, Bluetooth should be disabled during this process. In upgraded watches, you don’t need to disable Bluetooth.
      Path: Settings > Connections > Bluetooth

      Figure 1: Disabling Bluetooth
      Step 2: Enable debugging mode
      Make sure debugging mode is enabled. You can enable debugging mode from the Settings menu, as shown below.
      Path: Settings > About Watch > Debugging is turned on

      Figure 2: Enabling debugging mode
      Step 3: Set the Wi-Fi to Always on
      This step is optional, but to avoid any unnecessary issues, it is better to set the Wi-Fi to Always on. Leaving the setting on Auto can sometimes create issues.
      Path: Settings > Connections > Wi-Fi > Always on

      Figure 3: Setting the Wi-Fi to Always on
      Caution: Setting the Wi-Fi to Always on can drain the battery drastically. After debugging, it should be set back to Auto again for better battery life. Step 4: Connect to the network
      Connect the watch to the same network as your PC.
      Choose either of the following ways to connect the devices to the same network:
      • By creating a mobile hotspot
      • By using Wi-Fi under the same router
      Step 5: Restart the watch
      After the previous steps have been completed, restart the device. If you do not, the connection setup shows an error.

      Figure 4: Rebooting the watch
      Step 6: Establish the connection from the Remote Device Manager
      In Tizen Studio, go to Launch Remote Device Manager.

      Figure 5: Launching the Remote Device Manager
      Scan for new devices. The window shows a list of available devices and their IP addresses. You can also add a device manually from the Remote Device Manager window.

      Figure 6: Searching for available devices for connection
      To connect to the device, click on the Connect toggle next to the watch IP address and port information. The watch receives an RSA authentication request through a pop-up during this connection setup and it is mandatory to accept the RSA authentication to complete the process.

      Figure 7: Connecting to the watch from the Remote Device Manager
      You are now all set to deploy your app from Tizen Studio to the wearable device.
      Step 7: Permit to install user applications
      As a security feature, the device or emulator you have connected to does not contain the necessary certificates for installing user applications, and you must install them before being able to run your application on it. To do so, select “Permit to install applications” from the context menu of the device in the Device Manager.
      If the “The permit to install application is not required for this device” appears, this step is unnecessary.

      Figure 8: Setting the permit to install applications in the Device Manager
      Step 8: Launch your project
      Now, deploy your project on your connected watch, as shown in the image below.
      Path: Right-Click on the project > Run As > 1 Tizen Native Application

      Figure 9: Deploying the project from Tizen Studio to a connected watch
      Some helpful tips for connecting your device with the Remote Device Manager
      Check the IP address of your watch from Connections > Wi-Fi -> Wi-Fi Networks > tap on the SSID (your Wi-Fi name) > IP address.
      If your device is already shown in the Remote Device Manager's history, delete it and try to connect again.
      Launch the Device Manager to see the Log View.

      Figure 10: The Log View from Device Manager
      Make sure the watch is not connected with any other devices, including a phone. Otherwise, the connection fails and you receive the following error message:

      Figure 11: Error message during multiple connections
      If you cannot find the watch after scanning for devices from the Remote Device Manager, make sure your device is on the same network. To check this, go to the command prompt on your PC and ping the IP address of the watch in the following manner:
      ping < Watch_IP >
      If the ping command fails to connect to the IP address of your watch, it is not on the same network, and the SDB / Remote Device Manager does not work. To fix this, you need to change the network settings of your router or PC. The issue can also be caused by firewall settings, although this is rare.
      Conclusion
      The main purpose of this article is to help new developers to deploy Tizen projects to a real device using the Tizen Remote Device Manager. Hopefully, this tutorial is helpful for beginners and gives them a good experience with Tizen Studio.
      If you have any other problems or queries regarding launching projects with the Remote Device Manager, feel free to reach out through the Samsung Developers Forum.
      View the full blog at its source
    • By STF News
      Localization is the process of adapting an application to a specific country or region. To do this, an application should translate an application’s resources, such as text and images, into multiple languages and formats. Then, the application shows localized resources based on the settings of the device.
      This post explains how to localize text in Tizen .NET application. I strongly recommend you to read Xamarin.Forms String and Image Localization before you get started. You can obtain the sample application used in this post here.
      Create resource files
      The .NET framework provides a way for localizing an application using Resx resource files. Each file contains a list of items that consist of a name/value pair and an application can retrieve a specific resource by name. By using this mechanism, you can store and retrieve localized texts.
      Create a default resource file.
      Using Add New Item dialog, add a default resource file. The file name of the default resource doesn’t contain any language information. In the sample application, the default resource file AppResources.resx is added to the Resources folder.

      Set the Access Modifier to Public, which results in a file with the .designer.cs extension being added to the project. Then, add items which contain the following information:
      Name : The key used to retrieve the text Value : The localized text Comment : Additional information (optional)
      Add additional resource files.
      Create additional resource files for each language you want to support. The file name of each resource should include the language information, such as AppResources.ko-KR.resx. In these resource files, set the Access Modifier to No code gen.

      The file name of resource can include just the language code, without a country code, such as AppResource.es.resx. If the language of the device is es-ES, the application looks for resource files in this order:
      AppResources.es-ES.resx AppResources.es.resx AppResources.resx (default) Specify the default language
      Specify a default language using NeutralResourcesLanguage to inform the resource manager of the app’s default language. This improves lookup performance for the first resource that is loaded. In the sample application, en (English) is set by NeutralResourcesLanguage in Main.cs. For more information about NeutralResourcesLanguage, see NeutralResourcesLanguage Attribute Class.
      using System.Resources; [assembly: NeutralResourcesLanguage("en")] Localize texts
      The language setting of a device can be changed when your application is running. To adapt your application to the new language, text needs to be translated on the fly. XAML markup extensions is a good solution to meet this requirement and this is where we will start with my own LocalizingExtension class.
      [ContentProperty("Name")] public class LocalizingExtension : IMarkupExtension<BindingBase> { private static readonly IValueConverter _converter = new LocalizedResourceConverter(); public string Name { get; set; } public BindingBase ProvideValue(IServiceProvider serviceProvider) { return new Binding(nameof(LocalizationService.UICulture), BindingMode.OneWay, converter: _converter, converterParameter: Name, source: LocalizationService.Instance); } object IMarkupExtension.ProvideValue(IServiceProvider serviceProvider) { return (this as IMarkupExtension<BindingBase>).ProvideValue(serviceProvider); } } This extension enables a text to be localized when an application is started and the language setting is changed. This extension has a single property Name of type string that you set to the name of the text to be localized. This Name property is the content property, so Name= is not required when using it in XAML.
      I also made a LocalizationService class which provides information about the current language and notifies clients that the language setting has changed. You can see the code here.
      In addition, the LocalizationService class provides a method to get localized text. This function uses ResourceManager defined in AppResources.Designer.cs.
      /// <summary> /// Get the value of localized resource. /// </summary> /// <param name="resourceName">Resource name</param> /// <returns> /// The value of localized resource. /// If resourceName is not defined as a name in any resource file, then resourceName is returned as the value of the resource. /// </returns> public string GetResource(string resourceName) { return AppResources.ResourceManager.GetString(resourceName, UICulture) ?? resourceName; } By using this method, the LocalizedResourceConverter class converts text to the localized text.
      public class LocalizedResourceConverter : IValueConverter { public object Convert(object value, Type targetType, object parameter, CultureInfo culture) { return LocalizationService.Instance.GetResource(parameter as string); } public object ConvertBack(object value, Type targetType, object parameter, CultureInfo culture) { throw new NotImplementedException(); } } Accessing the value of text by LocalizingExtension enables localized text to be displayed even if the language setting of device has been changed.
      <ContentPage x:Class="LocalizationSample.Views.CenterLayoutPage" xmlns="http://xamarin.com/schemas/2014/forms" xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml" xmlns:ext="clr-namespace:LocalizationSample.Extensions" xmlns:viewModels="clr-namespace:LocalizationSample.ViewModels"> <ContentPage.BindingContext> <viewModels:CenterLayoutViewModel/> </ContentPage.BindingContext> <ContentPage.Content> <StackLayout Margin="0, 40, 0, 30" VerticalOptions="CenterAndExpand"> <Label Text="{ext:Localizing CountryName}" HorizontalOptions="CenterAndExpand"/> </StackLayout> </ContentPage.Content> </ContentPage> Sample application demo
      You can see that the text (CountryName) in the application is changed to the localized text when the language setting is changed.

      View the full blog at its source
    • By STF News
      Localization is the process of adapting an application to a specific country or region. To do this, an application should translate an application’s resources, such as text and images, into multiple languages and formats. Then, the application shows localized resources based on the settings of the device.
      This post explains how to localize text in Tizen .NET application. I strongly recommend you to read Xamarin.Forms String and Image Localization before you get started. You can obtain the sample application used in this post here.
      Create resource files
      The .NET framework provides a way for localizing an application using Resx resource files. Each file contains a list of items that consist of a name/value pair and an application can retrieve a specific resource by name. By using this mechanism, you can store and retrieve localized texts.
      Create a default resource file.
      Using Add New Item dialog, add a default resource file. The file name of the default resource doesn’t contain any language information. In the sample application, the default resource file AppResources.resx is added to the Resources folder.

      Set the Access Modifier to Public, which results in a file with the .designer.cs extension being added to the project. Then, add items which contain the following information:
      Name : The key used to retrieve the text Value : The localized text Comment : Additional information (optional)
      Add additional resource files.
      Create additional resource files for each language you want to support. The file name of each resource should include the language information, such as AppResources.ko-KR.resx. In these resource files, set the Access Modifier to No code gen.

      The file name of resource can include just the language code, without a country code, such as AppResource.es.resx. If the language of the device is es-ES, the application looks for resource files in this order:
      AppResources.es-ES.resx AppResources.es.resx AppResources.resx (default) Specify the default language
      Specify a default language using NeutralResourcesLanguage to inform the resource manager of the app’s default language. This improves lookup performance for the first resource that is loaded. In the sample application, en (English) is set by NeutralResourcesLanguage in Main.cs. For more information about NeutralResourcesLanguage, see NeutralResourcesLanguage Attribute Class.
      using System.Resources; [assembly: NeutralResourcesLanguage("en")] Localize texts
      The language setting of a device can be changed when your application is running. To adapt your application to the new language, text needs to be translated on the fly. XAML markup extensions is a good solution to meet this requirement and this is where we will start with my own LocalizingExtension class.
      [ContentProperty("Name")] public class LocalizingExtension : IMarkupExtension<BindingBase> { private static readonly IValueConverter _converter = new LocalizedResourceConverter(); public string Name { get; set; } public BindingBase ProvideValue(IServiceProvider serviceProvider) { return new Binding(nameof(LocalizationService.UICulture), BindingMode.OneWay, converter: _converter, converterParameter: Name, source: LocalizationService.Instance); } object IMarkupExtension.ProvideValue(IServiceProvider serviceProvider) { return (this as IMarkupExtension<BindingBase>).ProvideValue(serviceProvider); } } This extension enables a text to be localized when an application is started and the language setting is changed. This extension has a single property Name of type string that you set to the name of the text to be localized. This Name property is the content property, so Name= is not required when using it in XAML.
      I also made a LocalizationService class which provides information about the current language and notifies clients that the language setting has changed. You can see the code here.
      In addition, the LocalizationService class provides a method to get localized text. This function uses ResourceManager defined in AppResources.Designer.cs.
      /// <summary> /// Get the value of localized resource. /// </summary> /// <param name="resourceName">Resource name</param> /// <returns> /// The value of localized resource. /// If resourceName is not defined as a name in any resource file, then resourceName is returned as the value of the resource. /// </returns> public string GetResource(string resourceName) { return AppResources.ResourceManager.GetString(resourceName, UICulture) ?? resourceName; } By using this method, the LocalizedResourceConverter class converts text to the localized text.
      public class LocalizedResourceConverter : IValueConverter { public object Convert(object value, Type targetType, object parameter, CultureInfo culture) { return LocalizationService.Instance.GetResource(parameter as string); } public object ConvertBack(object value, Type targetType, object parameter, CultureInfo culture) { throw new NotImplementedException(); } } Accessing the value of text by LocalizingExtension enables localized text to be displayed even if the language setting of device has been changed.
      <ContentPage x:Class="LocalizationSample.Views.CenterLayoutPage" xmlns="http://xamarin.com/schemas/2014/forms" xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml" xmlns:ext="clr-namespace:LocalizationSample.Extensions" xmlns:viewModels="clr-namespace:LocalizationSample.ViewModels"> <ContentPage.BindingContext> <viewModels:CenterLayoutViewModel/> </ContentPage.BindingContext> <ContentPage.Content> <StackLayout Margin="0, 40, 0, 30" VerticalOptions="CenterAndExpand"> <Label Text="{ext:Localizing CountryName}" HorizontalOptions="CenterAndExpand"/> </StackLayout> </ContentPage.Content> </ContentPage> Sample application demo
      You can see that the text (CountryName) in the application is changed to the localized text when the language setting is changed.

      View the full blog at its source


×
×
  • Create New...