It has been 4 years since the below question was asked:
Is it possible to install an android app on Tizen OS device?
I have a samsung watch running Tizen 4.0 and I need to install google fit onto it. This is so that google fit (running on my phone already) can have access to the steps and heart rate sensor data from my watch.
This is because google fit is compatible with many apps and partners whereas samsung health is barely compatible with anything.
Does anyone know how to side load google fit onto a Tizen OS device (or even just enable google fit on the phone to access the wearable sensors)
I do not need to view the google fit app on my watch, although this would be a bonus.
Please keep answers very simple as I have no experience in developing for mobile devices.
Thank you very much in advance,
Anya
Unfortunately, I think it will not be supported: Using APK for Android on Tizen platform...
It is not simple issue - more than just using an java application...
Definitely, since Google fit needs Google Play Service library (A collection of Google-specific features) https://developers.google.com/android/guides/overview,
Tizen Platform also needs to run Google Fit. It is more complicated than running a java application.
Related
I'm working in a company building Android-based IVI system for Tier1/OEM/aftermarket. Before the release of Android Automotive OS, we ported Android for Phone on IVI hardware and do customizations to bring in vehicle-related features like rear view camera, HVAC control, BT music, navigation, steering wheel control, etc. At that time, our products didn't need to be certified by Google and we could choose whether to test CTS or not. But with Android Automotive OS, I'm not sure if the CTS test should be carried out and the report must be sent to Google for certification, or even integrate GMS?
In the latest Android CDD document: https://source.android.com/compatibility/android-cdd.pdf. I can see that there are some hardware and software requirements for Automotive devices. But I can't find any further information about what exactly should be conformed before shipping a vehicle with Android Automotive OS based IVI in different countries.
Looking forward to any tips & info. Thanks a lot!
BR
It is still the same way you did for your last project.
I would say it up to you.
There is nothing diferences until now for what we called Android Automotive OS..
There is no "Android Automotive OS" actually .. it is simply Android PLUS some added service , Vehicle HAL, CarService
So nothing special... Android still violate many Automotive requirement regrading safety and Performance. That why many OEM like GM have to customize alot of things on top Android
Basically if your IVI contain Android Auto certification then you need to do CTS and other stuff to make Google say YES if not... then Who care...
In the Samsung Galaxy S6 there is a S Health app that measures heart rate, SpO2, stress and other values. It looks like I can purchase additional apps for this. Is this S Health exclusive to Samsung? When I search online Google Fit API shows up. I'm starting from scratch on my knowledge of this subject.
Background:
I want to make an app that accesses the API's above but I'm not sure if it's an Android API, Samsung API open to developers or a closed Samsung API. How does it all fit together?
S Health is now available on a variety of Android devices and is no longer exclusive to Samsung devices.
To make an app that interacts with S Health, you will need an Android development environment and the Samsung Health SDK. This can be found at: http://developer.samsung.com/health
The SDK download also includes a programming guide that can get you started. There are also sample apps that interact with S Health here: http://developer.samsung.com/sample-app/list.do
I am wondering if it is possible to run an tizen wearable app in background. I need to run an app in background. I am using several sensors and I need to save these data continuously.
another thing Can we get the sensor in Samsung Gear S2 data such as Heart Rate directly from an android app directly without any widget on the Gear S2.
I appreciate any help or suggestion.
Thanks,
I'm also new on this and I'm starting with Samsung Gear S2.
When I read your post, I thought I read somewhere that Gear S2 would only run web app, yet, I opened the Tizen IDE, used a sample native app, and installed it an ran on Gear S2, so, I would say that you probably can do it. I would just explore the native sample apps for start, you'll have to develop in c/c++ and as you might know, you'll need to instal the Tizen IDE and the Samsung Extension SDK (http://developer.samsung.com/technical-doc/view.do?v=T000000248)
hope it helps.
It wasn't possible in the first Tizen version that supported wearable (2.2) but became possible later (2.3) when native and hybrid apps were added to the wearable profile.
Not sure how running Android apps on Tizen is really implemented, but I'd expect the chances of Anrdoid apps getting access to device information (sensor and other) is fairly unlikely, as those come through Tizen-specific APIs with also Tizen-specific privilege requirements - the mapping would be complex, but who knows, someone may have managed it. You don't need a widget for that though, the same device information API (and more) is available through native apps.
Yes it is possible to create wearable background app but only with Tizen 2.3 & above and only in Native app versions not in Web apps.
If you want to build app in web version then u can write your service in native and UI in web app and make the app as hybrid app.
Follow the guide in link below to pack a hybrid app:
Tizen Hybrid App Packaging guide
I want to develop an app on android that uses screen mirroring with Samsung TV. I'm looking to use my android app screen as a remote(say a game controller) & TV screen to run the actual game. My initial approach was learning google cast but it needs a chromecast dongle which I don't want to use for this project. I want to use Samsung Smart TV's Screen Mirroring feature to do so. After some googling, I figured out that samsung uses Allshare Framework API for screen mirroring/cast but I'm not completely sure on this. I'm currently struggling to find a proper documentation for screen mirroring. If someone can point to the correct documentation link then that'd be awesome. Also, please correct me if I'm wrong with the assumption that this can be achieved using Allshare API only.
It seems Samsung have came out with this new SDK - Samsung Multiscreen SDK( or maybe I've found it now :)). This link should cover most of the questions I've asked above. Also, if you are Unity user, Samsung has their own version of Unity which comes intalled with Samsung Multiscreen Game SDK. But you need to send a partnership request to samsung in order to use this version of Unity. Apart from these two, you can also use Connect SDK which is independent of any technology, i.e. it covers almost every other technology used for Cast. For exmple, if you have a Samsung Smart TV at your home & a Roku connection. With Samsung SDK you can only discover Smart TV but not Roku stick. Whereas, with Connect SDK you can discover Samsung Tv as well as Roku & any other Cast device which is available in your network.
This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
Android Emulator vs Real Device
Is it better to test your app on an emulator or on an actual Android device? As in to test your app while you are still developing it.
In addition, does testing on the emulator gives you more computing power than actual devices?
It is always better to test on a real device, as the emulator lacks certain inputs like sensors etc. (especially the older version of it). You will also have problem testing services like In app billing and LVM as the emulator doesn't come with Google Play, and the accounts that can be configured on it are limited.
The best solution is to have a few devices to test on, and use the emulator for testing different screen sizes and how they react to your layouts. There was a Google I/O talk this year that gave you a breakdown of what devices you needed to test on to make sure you have maximum compatibility. I don't remember which one though, sorry.
Concerning the development period,you should test the application on emulator first so that you can test it on multiple targets having different versions eg:2.2, 2.3, 4.0 to find out the loopholes and the resolution issues.
After completion of development you can test it on your actual device for hands on experience.
I would say it certainly depends on your needs. Since you are developing an application that will be consumed not by yourself actually, it will be consumed by your targeted audience and what will they have? They will definitely have real devices to use your application.
There are some features that are not available or really hard to configure on the emulator, like for example you are developing an app that uses a bluetooth feature.
The emulator is certainly designed for developers to test their apps in a virtual environment with limited functionality.
It really depends on the kind of app you are creating. If you are creating a game that requires the accelerometer then a real device would be beneficial. Yet if you are creating an app with a simple layout and you want to test for different screen dimensions and so on, the emulator is pretty good with this.
Yet you should always have a real device, since the emulator is very limiting.
Android simulator provides a platform very similar to the actual phone, so if your application is running in the simulator, it goes to 94% given the same result in the actual phone, except that sometimes there are modules that must be compulsorily test on a phone like the GMap, Push, screen size..