Filter
-
Content Type
-
Category
Mobile/Wearable
Visual Display
Digital Appliance
Platform
Recommendations
Filter
SDP DevOps
websearch sign in learn code lab foldables and large screens one ui beta develop mobile/wearable galaxy gamedev galaxy themes galaxy watch health samsung blockchain samsung dex samsung iap samsung internet samsung wallet see all mobile products samsung pay partner samsung pay galaxy ar emoji galaxy accessory galaxy edge galaxy z galaxy performance galaxy fm radio galaxy s pen remote galaxy sensor extension penup samsung automation samsung neural samsung teegris samsung ese sdk galaxy watch for tizen watch face studio one ui watch for tizen galaxy watch studio converter samsung iap for galaxy watch (tizen) visual display smart tv smart hospitality display smart signage digital appliance family hub platform bixby knox smartthings tizen.net design design system one ui one ui watch smart tv distribute galaxy store tv seller office instant plays support forums dev support remote test lab samsung android usb driver galaxy emulator skin connect news and updates events samsung developer conference blog sign in recommendations blog code lab foldable and large screen optimization health samsung wallet sdc24 samsung developer samsung developer quick link android usb driver code lab galaxy emulator skin foldables and large screens remote test lab dev support family site bixby knox smartthings tizen samsung research samsung open source samsung dev spain galaxy store seller portal legal terms samsung developer terms samsung wallet partner terms samsung pay partner terms privacy samsung developer privacy policy samsung wallet partner privacy policy samsung pay partner privacy policy open source license cookie samsung developer cookie policy samsung wallet partner cookie policy samsung pay partner cookie policy social communications facebook instagram twitter youtube rss linkedin system status site map system status site map facebook instagram twitter youtube rss linkedin copyright (c) 2021 samsung all right reserved.
Learn Developers Podcast
docseason 3, episode 5 previous episode | episode index | next episode this is a transcript of one episode of the samsung developers podcast, hosted by and produced by tony morelan a listing of all podcast transcripts can be found here host tony morelan senior developer evangelist, samsung developers instagram - twitter - linkedin guest maria ly, skimble galaxy watch, galaxy store, entrepreneurship maria ly, founder of skimble, the company behind the mobile fitness app workout trainer not only do we chat about how skimble began as a small startup but also their collaboration with samsung health and the made for samsung team listen download this episode topics covered skimble rock health workout trainer publishing on galaxy store marketing discoverability monetization generating revenue in-app purchase iap galaxy badges best of galaxy store awards diversity and inclusion helpful links skimble website - skimble com rock health - rockhealth com publishing on galaxy store - developer samsung com/galaxy-store marketing - developer samsung com/galaxy-store/marketing-resources best of galaxy store awards - developer samsung com/galaxy-store/best-of-galaxy-store maria ly linkedin - linkedin com/in/marialy maria ly interview - developer samsung com/sdp/blog skimble facebook - facebook com/skimbleinc skimble twitter - twitter com/skimble skimble pinterest - pinterest com/skimbleinc skimble instagram - instagram com/skimbleinc skimble youtube - youtube com galaxy badges - developer samsung com/galaxy-store/gsb-promotion samsung iap - developer samsung com/iap samsung developer program website - developer samsung com samsung developer program newsletter - developer samsung com/newsletter samsung developer program blog - developer samsung com/blog samsung developer program news - developer samsung com/news samsung developer program facebook - facebook com/samsungdev samsung developer program instagram - instagram com/samsung_dev samsung developer program twitter - twitter com/samsung_dev samsung developer program youtube - youtube com/samsungdevelopers samsung developer program linkedin - linkedin com/company/samsungdevelopers transcript note transcripts are provided by an automated service and reviewed by the samsung developers web team inaccuracies from the transcription process do occur, so please refer to the audio if you are in doubt about the transcript tony morelan 00 01 hey, i'm tony morelan and this is the samsung developers podcast, where we chat with innovators using samsung technologies, award winning app developers and designers, as well as insiders working on the latest samsung tools welcome to season three, episode five on today's show, i'm joined by maria lai, founder of scramble the company behind the mobile fitness app workout trainer not only do we chat about getting their start through the accelerator program, rock health, but also integrating with samsung health to become a launch partner and collaborating with the made for samsung team enjoy hey, maria, welcome to the podcast hi, tony maria ly 00 42 good morning thanks for having me tony morelan 00 44 yeah, so let me first ask who is maria ly? maria ly 00 49 oh, gosh, let's see, i am a health advisor, investor, an entrepreneur i am asian canadian turned american i live in salt lake city and san francisco part time and i love to travel around the world whenever i can to rock climb and explore and discover new cultures tony morelan 01 14 wow, this is pretty exciting so i understand that you got involved in tech at a young age tell me tell me about that start maria ly 01 21 so i got started i would say mostly when i started high school, and i had access to some of the tech focused groups for youth in canada and so i went through and did some of the courses out there started taking my first programming classes my parents got me my first computer actually when i was in elementary school, and that maybe sparked my interest even earlier but then eventually, i went to study computer engineering at the university of waterloo in canada and then i took a bunch of different coop internships in the tech field around the world tony morelan 01 58 so you said that you did some internships during those times? what were some of those industries that you were involved with? maria ly 02 04 yeah, so there was a good friday? i think, for me, i explored different tech verticals i think i started in a cad software company, and then moved on to aerospace and automotive i even dabbled in h fac, and semiconductors so kind of sampled, which i think you know, while you're young, you might as well and figure out what you're most passionate about tony morelan 02 28 sure, sure now, obviously, you're very passionate when it comes to having an active lifestyle was that the motivation for you to then think, how could i create some sort of active technology company? maria ly 02 40 oh, absolutely i was involved in athletics, i suppose from an early age, i dabbled in figure skating and gymnastics and eventually i got a chance to represent canada at the world cheerleading championships wow and you know, nowadays, i mentioned, i love to rock climb so i do that quite frequently and yes, all of those experiences in living an active lifestyle definitely inspired me to blend my background in technology and health together to form symbol tony morelan 03 12 now how long does symbol been around? i've been maria ly 03 14 working on symbol tinkering on fitness applications for about a decade now we started developing fitness focused applications during the advent of the smartphone and the smartwatches and you know, those connected devices, really were a critical part in sort of adoption, a mass adoption for fox because it's not that easy to have a personal trainer day but you know, having an app you can pull up on your phone is super convenient and if anything affordable and personal yeah, tony morelan 03 49 no, i think your timing was great, because that really was the beginning of the big fitness push when it came to wearables so let's talk about the beginning of skimble first, i need to ask the word scramble i'd love that as the name of the company is that a play off of the word skill in nimble? that's how i see it maria ly 04 06 at first i wanted to get nimble com but truly gone are the days when you get perfect, you know, words, but i thought about scramble because scribble was the name of a nimble cat in a ts eliot poem scribbled also in broadway, the broadway musical cats, so symbol was actually becoming available it was on backorder so i got it on backorder it was expired and, you know, sky plus nimble was sort of my blended word sure, but yes, skill as well sure lots of great skim musker words tony morelan 04 42 yeah so i understand that you guys were part of an accelerated program called rock health tell me about that maria ly 04 52 we were we got into rock health during our earlier days, and they provided us with a grant access to group office space in san francisco, as well as a mentorship program that was about four or five months long and during that time, we were able to kind of focus on different aspects of digital health and connect with potential partners and that sort of thing so i think it's a really amazing ecosystem that has really blossomed in the industry tony morelan 05 24 yeah, i'm sure that was a big help for you guys to get things started so you had mentioned that that program was based in san francisco, is that where your headquarters is? now? maria ly 05 32 to some extent, yes but i would say, we are quite remote and all around before we were located in the ferry building, i don't know if you've been there before, but it's pretty iconic yeah, we were upstairs there but then we started thinking about, you know, the lifestyle that our team wanted to pursue, being able to have access to the outdoors and all that good stuff so we decided to try to make our team as remote as possible and so we still kept our studio multimedia space in san francisco in the mission but then we gave up the very building, and we did a lot of video chats, and you know, team meets wherever we were and so this was actually pre pandemic, believe it or not and so when that hit, we were all pretty much set up tony morelan 06 24 oh, that was nice really, really good timing for such an unfortunate pandemic event maria ly 06 28 yeah, right the silver lining? exactly tony morelan 06 32 so how many people work first gimbal maria ly 06 35 so we have a pretty distributed team of mostly contractors, we work with quite a handful of internal personal trainers and we have over like 1000 trainers on our platform, who develop the training programming for our team and we've got different folks across the globe, focusing on various roles in the company, such as we have our marketing manager in australia, that sort of thing so sure, i would say we're a lean team but we have a great network tony morelan 07 05 so let's talk about your flagship app, workout trainer, tell the people out there, what exactly is workout trainer, maria ly 07 11 workout trainer offers 1000s of follow along multimedia workouts, led by expert coaches and we also offer a personal training network if you want to find a one-on-one online coach tony morelan 07 24 nice, ya know, i have used the app before i love it unlike just like clicking play and watching a video there's a lot more, you know, personal data that you get, i love the fact that you see the in progress, calorie burn, that sort of a fun motivating, you know, piece of data that comes to me as i'm working out maria ly 07 45 absolutely it's funny, you mentioned the heart rate feedback and, and that sort of thing some of our most active users are using the application with their connected heart rate devices, mostly the smartwatches that are available on the market today and it's remarkable to see like the progress people are making by just doing their workouts and coming back to maybe their go to workouts and they can see, you know, their heart rate or the reps chain you can log all that information in the application and you get performance stats as you make progress tony morelan 08 18 that's wonderful now, and now it's not just for folks like myself that are wanting to get a great, you know, fitness routine going but you also are bringing on you'd mentioned contractors so if you are a trainer that would like to bring your workouts to a larger audience this is where you guys are inviting trainers could come join the platform, correct? maria ly 08 39 yes so when you launch the app, there's actually a little tab called trainers, you tap there, you can follow any of our trainers for free and if you find, you know, one trainer who particularly inspires you, or has a background and skill set in a specialty that you're looking for, you can recruit that trainer to help you one on one and they can send messages to you workouts and even a full complete training plan so that's been really nice to connect these folks together tony morelan 09 10 that's great so let's talk about the relationship with samsung and in skin we'll talk about how did that first start? maria ly 09 18 sure so a little while ago, samsung reached out to us interested specifically in our health integrations and it was the samsung health team that contacted us and we became one of their launch partners in their ecosystem with various health app developers and they came to our office in the ferry building and we met several times then we actually went to korea to meet some of the health team there you know, samsung has a big headquarters in mountain view, as well as korea and seoul so we were able to kind of meet the key folks there and since then, we bit remote and working with the folks at the made for samsung team and also within the health team tony morelan 10 07 now, last year, you guys won the 2021, best of galaxy store award for best wellness app what did it mean to win that award? maria ly 10 16 yes, that award was really, really wonderful to receive because, you know, during the time, the last few years, as you guys know, it hasn't been easy and when folks aren't able to go into their gyms, and meet their favorite trainers, or even their workout buddies at the gym, i was really personally very thankful to be able to offer folks and do our part to give them the workouts they wanted in a in a safe place when life was a bit more unpredictable so it really was meaningful to receive that award and we're very grateful for kind of the journey that we have had with samsung, as an integral partner tony morelan 10 55 yeah, i think the timing of that award and where we were at in the pandemic really just showed the value of workout trainer, and really what the, you know, what the people out there wanted to see in us so tell me, are there any unique aspects or optimizations to the galaxy store version of workout trainer? oh, yes maria ly 11 12 so we have a special made for samsung version of workout trainer so if you go on to the galaxy app store, you can just download workout trainer for samsung and this version of the application is tailored for all the latest samsung smart devices you've got a unique offering here so you can get access to some exclusive content such as workouts as well as oftentimes we do some promotion so you can actually unlock our pro plus membership, if you sign up with your samsung account and then further just to add, because we have such a good relationship with the samsung health team, all that data that you're doing, you can share between applications, you can have that sort of a large overview of your health profile within the samsung health application as well tony morelan 12 08 oh, that's wonderful so let's talk a bit about the development of the app what is the workflow? what is the process for you guys, when you created workout trainer? maria ly 12 17 i guess for starters, we use kind of agile development practices and a lot of brainstorming, we currently use android studio and we host all of our contents in the cloud and on top of that, obviously, we use the latest tools with within the samsung sdk id kind of environment tony morelan 12 40 sure, sure so when you first created the app, how long did it take? you know, is this an app that took, you know, a long time to create? or was this something that came pretty quickly and easily to you, maria ly 12 50 i would say that the first very early version of our app took about six months but as you guys know, app development is never as straightforward as you would like and you're always evolving your app and making it better and better and so throughout the years, we've added more features tightened up our flow improved our ui ux experience so you know, it all depends on what your app is aiming to do and offer, and try to use, you know, the best tools possible and rev on it and keep in mind that people like good user experience so even if it's a utility app, you have to think about your customers and get their feedback early on yeah, you tony morelan 13 33 know, the one thing that i will say about when i used to work at trainer was the ui was wonderful i mean, it's because you're in the middle of a workout and so you want something that is simple and easy to use with just a nice, clean interface and that's one of the things that stood out for me with workout trainer maria ly 13 47 well, thanks it's always a work in progress tony morelan 13 50 so let's talk about discoverability because i know that is one of the hardest parts i mean, it's one thing to go and create an app and build it and publish it but the hardest thing is to get people to actually see it and use it so what have you guys done related to discoverability? maria ly 14 05 for us, we have different channels to get discovered a lot of it has to do with be partners with certain discovery channels, but also with our community so for instance, you know, people can do workouts and invite their friends and challenge them to workouts so sort of creating that, like word of mouth has been very helpful for us get discovered through a grassroot approach and then also, you know, sometimes we have different partners where we can sell our app into verticals like within health care, or corporations, or specific areas, or times of the year for instance, samsung and symbols workout trainer can do sort of a collab or a promotion period tony morelan 14 55 yeah, yeah and i'm sure you guys are using the galaxy store badge is that correct to help promote it and weren't people directly to the app on galaxy store? yes, we are for sure wonderful and i'll make sure to include a direct link to that in the in the show notes for, not just that for, but for many of the other areas that we're talking about i loved what you said, as far as you know, inviting a friend and building that community because i know when it comes to workouts, a lot of times people don't have the motivation to do it themselves and they need to be held accountable so you know, if you find a friend that says, hey, if you work out all workout, and when you guys can work out together, you know, in sort of motivate each other to work out, that's what really gets you into a good routine as far as fitness so how many people would you say are using workout trainer, maria ly 15 43 we've seen over 30 million users come our way and, you know, on a day-to-day basis, we're seeing 10s of 1000s of workouts being completed and these are, you know, long form workouts so people are not just going into our app, and you know, jumping away, they're actually finding good content, relevant content for them to do and play for a long period of time, be it, you know, five to 20, to even, you know, 45 minutes long tony morelan 16 08 that's wonderful that is great and that is one of those key things when it comes to you for app developers, they want to create an experience where someone is not just coming in, you know, and like playing a game for a few minutes, and then they're gone retention is such a key component to creating a successful app how do you guys generate revenue, maria ly 16 29 we're going to trainer is a free application, and we offer in app purchase subscription that would be the pro plus membership option so that's offered at 699 a month and it's a reoccurring subscription and we also offer our one-on-one online training platform and the trainer sets the price and on average, it's between 50 to $200 a month, and we take a platform fee tony morelan 16 52 i love that that that you offer that that opportunity for people who want to really, you know, find that personal one on one trainer but yet your app also is available at an affordable price just for the general community i think that is that is great, because it makes it easy for people to give it a try and see if they like it and then decide maybe they want to, you know, get more involved with the app maria ly 17 13 oh, for sure and sometimes our trainers offer one on one training with free trials so we offer a free trial period as well tony morelan 17 19 oh, that's great that is that it's that's wonderful yeah so what advice would you give developers looking to bring their app to galaxy store? maria ly 17 29 oh, i would definitely encourage folks to get on the samsung platform because, as you guys know, around the world, like there are so many people that are using samsung devices, be it the smartphones, tablets, or the smartwatches and so being on the platform will just bring more visibility to your application and it's an opportunity to grow your user base naturally tony morelan 17 52 tell me what is in the future first gimble maria ly 17 55 so we've focused on creating great content and we're going to continue doing that working on providing a platform where people can access more multimedia content from trainer created content workouts created and led by your famous youtube fitness celebrities, and so forth so for us with workout trainer, we want to create and serve the best content for you so that personalized experience where you can have instant access to follow along content for your fitness journey tony morelan 18 28 that's, that's wonderful you know, this this past year, there's been a really big push for diversity and inclusion tell me what is kimble doing related to that? maria ly 18 38 i think from the start with scramble and growing our early team, i always wanted to have a group of great folks not just like industry, people, but trainers and everybody that has been involved to reflect the people who are actually using the application and so, you know, i was not specifically seeking out extreme diversity, but by just me wanting to talk to all kinds of folks from around the world trainers who had, you know, a focus on high intensity training versus pilates, yoga studio style backgrounds and we have so many different trainers demonstrating our exercises, our exercise database library, i believe has grown to be the largest out there with trainers who are very diverse, you know, they look like me and you and all the other folks who use the application so i hope that the application offers content that feels diverse in the type of content it provides, and also the friendly faces who are demonstrating the exercises tony morelan 19 47 that's great so recently, we did a blog feature on you for international women's day you know, being a woman leading a tech company tell me what advice would you give young women looking to start a career are in tech, maria ly 20 01 you know, more than ever before, women are breaking barriers so, you know, having their voices heard within tech within athletics within all sorts of fields, you know, having them be out there doing the work that they love living their best life and if that means, you know, being a leader in technology, or you know, a developer, an engineering manager, there are so many roles within tech that you could pursue and if you have an early appetite for some of the math and science classes, you know, a technology career could be for you so just pursue it and explore it, and you could be your own boss, even, there are so many opportunities now more than ever, i would say, where you can have the mentorship and support and encouragement from not just, you know, the leaders, the your male counterparts, the females in the space, who maybe have been there for a few years, even for me, you know, i do like advising and investing in women led companies in something that inspires me because i want to see the young females take charge and create amazing products for our future generation and, you know, my children even i'm excited for the future and what it can bring for all folks tony morelan 21 18 yeah, no, that's, that's wonderful in that blog, i'm going to link to it it was a great interview; you actually went into great detail on some of these areas that would really help inspire women and young women to really get started into this tech industry so maria, it was excellent to chat with you and learn much more about you know, workout trainer and all the great things that you guys are doing it's gimble let me ask you, what is it that you do for fun when you are not working? maria ly 21 45 well, i have two kids, they can be quite busy on my off hours, we are doing a lot of different activities for instance, over the weekend, i took my son to his first gymnastics class, and then we went skiing because we're in salt lake and it's the end of the season, he went out his first black even so just seeing the young guys, they're leading the charge there and i'm just trying to keep up in addition, when there's a little downtime, i do like to have some focus over for home cooked meal and a board game or two so i actually like playing strategy board games so that's one of my little-known passions as well tony morelan 22 25 that's wonderful that's wonderful i love a good time with friends, food and fun game activity well, hey, maria, it was great to have you on the podcast, i really enjoy you taking the time to chat maria ly 22 35 likewise, tony closing 22 37 looking to start creating for samsung download the latest tools to code your next app, or get software for designing apps without coding at all sell your apps to the world on the samsung galaxy store check out developer samsung com today and start your journey with samsung tony morelan 22 53 the samsung developers podcast is hosted by tony morelan and produced by jeanne hsu
events mobile, health, game, ai, iot
blogthe 2022 samsung developer conference in san francisco showcased some of samsung’s latest innovations in technology. this year spotlighted samsung’s brilliant minds innovating a calm technology ecosystem that gives consumers more seamless experiences in their daily lives. every year we kick off sdc with a keynote speech. this year jonghee han, head of the device experience (dx) division, shared how samsung electronics is crafting systems that help make lives smarter, safer, more convenient, and more connected than ever before. covering everything from knox matrix to holistic household platforms like bixby home studio and smartthings. jh han, vice chairman, ceo and head of device experience (dx) division for those interested in learning more, discover the developer updates shared at sdc in this blog post. samsung electronics integrates matter into the smartthings ecosystem jaeyeon jung, corporate vice president at samsung electronics and head of smartthings, shared how developers can maximize calm technology in the home by tapping into smartthings new integration with matter. jaeyeon jung, vp and head of smartthings, mobile experience business matter-enabled devices will join numerous products and brands already available within smartthings’ vast ecosystem, including devices from google, eve systems, honeywell home by resideo, linksys, nanoleaf, philips hue, schlage, wemo, yale, and more. developers, we invite you to build code with matter-enabled devices and watch the many smartthings tech sessions. dolby atmos releases a 3-d audio plugin for samsung mobile matthew reyes from dolby announced dolby atmos’ a new audio plugin with audiokinetic. the audio plugin enables game developers to create a 3-d surround sound effect for galaxy buds and samsung mobile. now players can feel every part of the action on their phones. dolby’s free plugin offers developers a chance to create an even better immersive experience. check out dolby’s tech session, which provides a plugin tutorial. samsung open-sources bothandy project sebastien seung and the team at samsung research america released samsung bothandy’s "openbothandy" open-source project. openbothandy provides manipulation benchmark scenarios, real-time simulation, and baseline manipulation codes. sebastian seung, president and head of samsung research experiment with samsung bothandy and advance robot manipulation technologies. bixby home studio simplifies voice commands bixby's developer evangelist, roger kibbe, shared what’s new with bixby developer studio and bixby home studio. this year's newest update is bixby home studio's voice control optimization tool on smartthings home devices. asr, nlu, and an entire command system are now completed locally on one device. what this means is bixby home studio allows developers to create code that helps consumers complete multiple tasks with a single command on the phone. imagine, you can ask to turn on your ac, and bixby home studio also checks to see if you have any windows open. roger kibbe, senior developer evangelist, north america bixby labs listen to roger’s tech session for more updates and start developing with bixby home studio. samsung health stack optimizes research studies principal engineer jinwoo song from samsung research’s data research team demonstrated how samsung health stack helps developers, engineers, and health professionals optimize research related to digital health using wearable devices. with samsung health stack’s app sdk, developers can create mobile apps that collect data from participants. applications include medical research studies, clinician services, or whatever your imagination envisions. tune in to jinwoo's recorded tech session, and contribute your visions to samsung health stack. relive sdc22 if you’re not done exploring the latest tech innovations, we welcome you to get inspired by sdc from the comfort of your home. you can experience sdc22 all over again–from watching the highlights to accessing the tech sessions on-demand. thank you for reading through our developer announcement for sdc22 events in the past. let us know your favorite moments from sdc by tagging us with the hashtag #sdc22 on twitter, facebook, linkedin, and youtube to continue the discussion.
Mischa Shankerman
Develop Health
apioverviewpackageclasstreedeprecatedindex com samsung android sdk healthdata class healthconnectionerrorresult java lang object com samsung android sdk healthdata healthconnectionerrorresult public final class healthconnectionerrorresult extends object this class handles errors raised by connection failure to the health data store considerations for connection failure a partner app works with samsung health the partner app can meet the following error cases when it connects to samsung health connection error description platform_not_installed samsung health is not installed old_version_platform installed samsung health's version is old platform_disabled samsung health is disabled user_agreement_needed the user didn't agree to samsung health's terms & conditions and privacy policies user_password_needed samsung health is locked by the user password handling connection exceptions samsung health sdk for android helps you to handle all available error cases with healthconnectionerror when your application connects to the health data store healthconnectionerror is retrieved in healthdatastore connectionlistener's event handler and all samsung health's partner applications need to check the health data store's connection error mandatorily the following example shows how to handle the connection error public class mainactivity extends activity { private healthdatastore mstore; private healthconnectionerrorresult mconnerror; private static mainactivity minstance = null; @override public void oncreate bundle savedinstancestate { // mstore = new healthdatastore this, mconnectionlistener ; mstore connectservice ; } @override public void ondestroy { mstore disconnectservice ; // } private final healthdatastore connectionlistener mconnectionlistener = new healthdatastore connectionlistener { @override public void onconnected { // connected } @override public void onconnectionfailed healthconnectionerrorresult error { // connection fails showconnectionfailuredialog error ; } @override public void ondisconnected { // connection is disconnected } }; private void showconnectionfailuredialog healthconnectionerrorresult error { alertdialog builder alert = new alertdialog builder this ; mconnerror = error; if mconnerror hasresolution { switch error geterrorcode { case healthconnectionerrorresult platform_not_installed message = "please install samsung health"; break; case healthconnectionerrorresult old_version_platform message = "please upgrade samsung health"; break; case healthconnectionerrorresult platform_disabled message = "please enable samsung health"; break; case healthconnectionerrorresult user_agreement_needed message = "please agree to samsung health policy"; break; default message = "please make samsung health available"; break; } } else { // in case that the device doesn't support samsung health, // hasresolution returns false also alert setmessage r string msg_conn_not_available ; } alert setpositivebutton r string ok, dialog, id -> { if error hasresolution { error resolve mainactivity this ; } } ; if error hasresolution { alert setnegativebutton "cancel", null ; } alert show ; } } since 1 0 0 see also healthdatastore connectionlistener field summary fields modifier and type field and description static int connection_failure the connection is not established in the health data framework static int old_version_platform the version of the health data framework is outdated to cooperate with sdk static int old_version_sdk the sdk's data library version is outdated to cooperate with the samsung health's health data framework static int platform_disabled the health data framework is disabled static int platform_not_installed samsung health is not installed static int platform_signature_failure it fails to check the signature of the health data framework static int timeout the connection time exceeded the limit static int unknown unknown error static int user_agreement_needed the user did not agree to terms and conditions, and privacy policy of samsung health yet static int user_password_needed the user cancels the password input explicitly on the password pop-up window method summary all methods instance methods concrete methods modifier and type method and description int geterrorcode gets the error code of connection failure boolean hasresolution checks whether the given error has a resolution void resolve activity activity resolves an error with an activity which is able to get the user's feedback for possible error cases field detail unknown public static final int unknown unknown error its constant value is 0 since 1 0 0 see also constant field values connection_failure public static final int connection_failure the connection is not established in the health data framework its constant value is 1 since 1 0 0 see also constant field values platform_not_installed public static final int platform_not_installed samsung health is not installed to resolve it if your app runs on android 11, check your app manifest whether the "<queries>" element is added see the app manifest guide call resolve android app activity it leads the user to install samsung health on an app seller site its constant value is 2 since 1 0 0 see also resolve android app activity , constant field values old_version_sdk public static final int old_version_sdk the sdk's data library version is outdated to cooperate with the samsung health's health data framework to resolve it apply the latest data library to your app if your app uses the latest data library, create an activity to update to install your latest app its constant value is 3 since 1 0 0 see also constant field values old_version_platform public static final int old_version_platform the version of the health data framework is outdated to cooperate with sdk to resolve it, call resolve android app activity it leads the user to install the latest samsung health on an app seller site its constant value is 4 since 1 0 0 see also resolve android app activity , constant field values timeout public static final int timeout the connection time exceeded the limit its constant value is 5 since 1 0 0 see also constant field values platform_disabled public static final int platform_disabled the health data framework is disabled to resolve it, call resolve android app activity it leads the user to activate samsung health through the phone's settings its constant value is 6 since 1 0 0 see also resolve android app activity , constant field values user_password_needed public static final int user_password_needed the user cancels the password input explicitly on the password pop-up window some devices can request a password to protect the user's data the password for the health data access can be registered in samsung health by the user then the user can enter the password through the password pop-up window if the predetermined time passed without the valid password input, timeout occurs its constant value is 7 since 1 0 0 see also constant field values platform_signature_failure public static final int platform_signature_failure it fails to check the signature of the health data framework its constant value is 8 since 1 0 0 see also constant field values user_agreement_needed public static final int user_agreement_needed the user did not agree to terms and conditions, and privacy policy of samsung health yet the health data framework is not activated before agreement to resolve it, call reslove it leads the user to the samsung health's service agreement page its constant value is 9 since 1 0 0 see also resolve android app activity , constant field values method detail geterrorcode public int geterrorcode gets the error code of connection failure usually it is called in healthdatastore connectionlistener onconnectionfailed healthconnectionerrorresult it's required to resolve the error depending on its returned error code returns the error code since 1 0 0 hasresolution public boolean hasresolution checks whether the given error has a resolution whether the device supports samsung health the sdk supports marshmallow and above android devices including non-samsung devices and it works with samsung health there is no connection issue on most devices but it is not available occasionally depending on the device's specification this api lets you know whether the device supports samsung health the returned false involves that the device is not available for samsung health precondition check the network connection permission android permission internet returns true if the platform provides a resolution for the error call resolve activity false in the following cases if the device doesn't support samsung health if there is no resolution for the error since 1 0 0 resolve public void resolve activity activity resolves an error with an activity which is able to get the user's feedback for possible error cases it handles the following errors and operations show a proper message for each error case in your application before call this method error operation platform_not_installed linked to the application installation page old_version_platform linked to the application installation page platform_disabled linked to settings of the device to turn on samsung health user_agreement_needed linked to the starting screen of samsung health to get the user's agreement precondition check the network connection permission android permission internet parameters activity - an activity which resolves the error with the user's feedback usually it's the main activity of your application throws illegalargumentexception - if the specified input is null or invalid since 1 0 0
Develop Smart TV
apigetting device capabilities using systeminfo api the following keys are available to obtain the device capability information using systeminfo api device capability keys battery camera content api database download api graphics input iotcon push api led location microphone multi-point touch multimedia transcoder network opengl® es platform profile sensor screen shell dynamic box sip speech tv usb vision web service system keys build information model name platform name tizen id the following table lists the keys to check if a device has a battery key type description version http //tizen org/feature/battery boolean the platform returns true for this key, if the device has a battery if it is true, w3c battery status api, battery property in systeminfo api, and power api must be supported 2 3 the following table lists the camera feature keys key type description version http //tizen org/feature/camera boolean the platform returns true for this key, if the device provides any kind of a camera if it is true, w3c getusermedia and html media capture apis are supported 2 2 1 http //tizen org/feature/camera back boolean the platform returns true for this key and the http //tizen org/feature/camera key, if the device provides a back-facing camera 2 2 1 http //tizen org/feature/camera back flash boolean the platform returns true for this key and the http //tizen org/feature/camera back key, if the device provides a back-facing camera with a flash 2 2 1 http //tizen org/feature/camera front boolean the platform returns true for this key and the http //tizen org/feature/camera key, if the device provides a front-facing camera 2 2 1 http //tizen org/feature/camera front flash boolean the platform returns true for this key and the http //tizen org/feature/camera front key, if the device provides a front-facing camera with a flash 2 2 1 the following table lists the keys related to content api features key type description version http //tizen org/feature/content scanning others boolean the platform returns true for this key, if the device supports the media scanning feature for "other"-type files which are not included in the media content types such as "image", "video", "sound" or "music" 4 0 the following table lists the database feature keys key type description version http //tizen org/feature/database encryption boolean the platform returns true for this key, if the device supports database encryption 2 2 1 the following table lists the keys to check if download api is supported on a tizen device key type description version http //tizen org/feature/download boolean the platform returns true for this key, if the device supports download api 2 3 http //tizen org/feature/network telephony boolean the platform returns true for this key, if the device supports all apis which require telephony feature if it is true, "cellular" in downloadnetworktype is supported 2 2 1 http //tizen org/feature/network wifi boolean the platform returns true for this key, if the device supports all apis which require wi-fi if it is true, "wifi" in downloadnetworktype is supported 2 2 1 the following table lists the graphics feature keys key type description version http //tizen org/feature/graphics acceleration boolean the platform returns true for this key, if the device supports graphics hardware acceleration 2 2 1 the following table lists the input feature keys key type description version http //tizen org/feature/input keyboard boolean the platform returns true for this key, if the device provides a built-in keyboard supporting any keyboard layout 2 2 1 http //tizen org/feature/input keyboard layout domstring the platform returns the keyboard layout such as qwerty supported by the built-in keyboard for this key and returns true for the http //tizen org/feature/input keyboard key if the device does not provide a built-in keyboard, the platform returns an empty string for this key and returns false for the http //tizen org/feature/input keyboard key 2 2 1 http //tizen org/feature/input rotating_bezel boolean the platform returns true for this key, if the device provides a built-in rotating bezel 2 3 1 the following table lists the keys related to iotcon api features key type description version http //tizen org/feature/iot ocf boolean the platform returns true for this key, if the device supports the iot connectivity if it is true, iotcon api is supported 4 0 the following table lists the led feature key key type description version http //tizen org/feature/led boolean the platform returns true for this key, if the device supports led 2 3 the following table lists the location feature keys key type description version http //tizen org/feature/location boolean the platform returns true for this key, if the device supports location positioning 2 2 1 http //tizen org/feature/location batch boolean the platform returns true for this key and the http //tizen org/feature/location key, if the device supports gps batch feature 2 3 http //tizen org/feature/location gps boolean the platform returns true and the http //tizen org/feature/location, if the device supports the global positioning system gps 2 2 1 http //tizen org/feature/location wps boolean the platform returns true for this key and the http //tizen org/feature/location key, if the device supports the wi-fi-based positioning system wps 2 2 1 the following table lists the microphone feature keys key type description version http //tizen org/feature/microphone boolean the platform returns true for this key, if the device supports a microphone if it is true, w3c getusermedia and html media capture apis are supported 2 2 1 http //tizen org/feature/media audio_recording boolean the platform returns true for this key, if the device supports to record audio files on a device if it is true, cordova media api is supported 3 0 the following table lists the multi-point touch feature keys key type description version http //tizen org/feature/multi_point_touch pinch_zoom boolean the platform returns true for this key, if the device supports pinch zoom gestures 2 2 1 http //tizen org/feature/multi_point_touch point_count long the platform returns the maximum number of supported multi-touch points for this key the platform returns a value less than 2 for this key, if the device does not support multi-point touch 2 2 1 the following table lists the multimedia transcoder feature key key type description version http //tizen org/feature/multimedia transcoder boolean the platform returns true for this key, if the device supports multimedia transcoder 2 3 the following table lists the network feature keys key type description version http //tizen org/capability/network bluetooth always_on boolean the platform returns true for this key, if the device must always enable bluetooth it means that an application cannot change the bluetooth's state visibility, connectivity, device name 2 3 http //tizen org/feature/network bluetooth boolean the platform returns true for this key, if the device supports bluetooth 2 2 1 http //tizen org/feature/network bluetooth audio call boolean the platform returns true for this key, if the device supports bluetooth handsfree profile hfp 2 3 http //tizen org/feature/network bluetooth audio media boolean the platform returns true for this key, if the device supports bluetooth advanced audio distribute profile a2dp 2 3 http //tizen org/feature/network bluetooth health boolean the platform returns true for this key, if the device supports bluetooth health device profile hdp 2 3 http //tizen org/feature/network bluetooth hid boolean the platform returns true for this key, if the device supports bluetooth human input device hid 2 3 http //tizen org/feature/network bluetooth le boolean the platform returns true for this key, if the device supports bluetooth low energy related methods in bluetooth api 2 3 http //tizen org/feature/network bluetooth opp boolean the platform returns true for this key, if the device supports bluetooth object push profile opp 2 3 http //tizen org/feature/network ethernet boolean the platform returns true for this key, if the device supports ethernet if it is true, "all" in downloadnetworktype and systeminfoethernetnetwork is supported 2 4 http //tizen org/feature/network internet boolean the platform returns true for this key, if the device supports internet 2 3 1 http //tizen org/feature/network net_proxy boolean the platform returns true for this key, if the device supports network proxy for internet connection 3 0 http //tizen org/feature/network nfc boolean the platform returns true for this key, if the device supports near field communication nfc 2 2 1 http //tizen org/feature/network nfc card_emulation boolean the platform returns true for this key, if the device is recognized by the nfc card readers 2 3 http //tizen org/feature/network nfc card_emulation hce boolean the platform returns true for this key, if the device supports nfc host-based card emulation 2 3 1 http //tizen org/feature/network nfc p2p boolean the platform returns true for this key, if the device supports p2p apis which require near field communication nfc 2 3 1 http //tizen org/feature/network nfc reserved_push boolean the platform returns true for this key and the http //tizen org/feature/network nfc key, if the device supports the nfc reserved push feature 2 2 1 http //tizen org/feature/network nfc tag boolean the platform returns true for this key, if the device supports tag apis which require near field communication nfc 2 3 1 http //tizen org/feature/network push boolean the platform returns true for this key, if the device supports push api which requires the ip push service provided by the tizen reference implementation 2 2 1 http //tizen org/feature/network secure_element boolean the platform returns true for this key, if the device supports secure elements 2 2 1 http //tizen org/feature/network telephony boolean the platform returns true for this key, if the device supports the telephony related apis 2 2 1 http //tizen org/feature/network telephony mms boolean the platform returns true for this key and the http //tizen org/feature/network telephony key, if the device supports mms 2 2 1 http //tizen org/feature/network wifi boolean the platform returns true for this key, if the device supports all apis which require wi-fi 2 2 1 http //tizen org/feature/network wifi direct boolean the platform returns true for this key and the http //tizen org/feature/network wifi key, if the device supports wi-fi direct™ 2 2 1 the following table lists the opengl® es feature keys key type description version http //tizen org/feature/opengles boolean the platform returns true for this key, if the device supports any opengl® es version and any texture format 2 2 1 http //tizen org/feature/opengles texture_format domstring the supported texture formats for the opengl® es e g "3dc/atc/etc/ptc" the platform returns an empty string for this key if opengl® es or compressed texture formats are not supported 2 3 http //tizen org/feature/opengles texture_format 3dc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the 3dc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles texture_format atc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the atc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles texture_format etc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the etc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles texture_format ptc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the ptc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles texture_format pvrtc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the pvrtc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles texture_format utc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the utc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles version 1_1 boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the opengl® es version 1 1 2 2 1 http //tizen org/feature/opengles version 2_0 boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the opengl® es version 2 0 2 2 1 the following table lists the platform feature keys key type description version http //tizen org/feature/platform core api version domstring the version of the tizen core api in the [major] [minor] format for example, "1 0" represents a web api version where the major version is 1 and the minor version is 0 if a device doesn't provide tizen core api, it returns an empty string "" 2 3 http //tizen org/feature/platform core cpu arch domstring the platform returns the cpu architecture e g "armv7", "x86" of a device 2 3 http //tizen org/feature/platform core cpu arch armv6 boolean the platform returns true for this key, if the device runs on the armv6 cpu architecture 2 2 1 http //tizen org/feature/platform core cpu arch armv7 boolean the platform returns true for this key, if the device runs on the armv7 cpu architecture 2 2 1 http //tizen org/feature/platform core cpu arch x86 boolean the platform returns true for this key, if the device runs on the x86 cpu architecture 2 2 1 http //tizen org/feature/platform core cpu frequency long the platform returns the frequency at which a core cpu is running unit mhz 2 3 http //tizen org/feature/platform core fpu arch domstring the platform returns the fpu architecture e g "vfpv3", "ssse3" of a device if there is no fpu on a device, it returns an empty string "" 2 3 http //tizen org/feature/platform core fpu arch sse2 boolean the platform returns true for this key, if the device runs on the sse2 fpu architecture 2 2 1 http //tizen org/feature/platform core fpu arch sse3 boolean the platform returns true for this key, if the device runs on the sse3 fpu architecture 2 2 1 http //tizen org/feature/platform core fpu arch ssse3 boolean the platform returns true for this key, if the device runs on the ssse3 fpu architecture 2 2 1 http //tizen org/feature/platform core fpu arch vfpv2 boolean the platform returns true for this key, if the device runs on the vfpv2 fpu architecture 2 2 1 http //tizen org/feature/platform core fpu arch vfpv3 boolean the platform returns true for this key, if the device runs on the vfpv3 fpu architecture 2 2 1 http //tizen org/feature/platform native api version domstring the version of the native api in the [major] [minor] format for example, 1 0 represents a native api version where the major version is 1 and the minor version is 0 if a device doesn't provide tizen native api, it returns an empty string "" 2 2 1 http //tizen org/feature/platform native osp_compatible boolean the platform returns true for this key, if the device supports the bada compatibility mode 2 2 1 http //tizen org/feature/platform version domstring the version of the platform in the [major] [minor] [patch version] format for example, 1 0 0 represents a platform version where the major version is 1 and the minor and build versions are 0 2 2 1 http //tizen org/feature/platform web api version domstring the version of the web api in the [major] [minor] format for example, 1 0 represents a web api version where the major version is 1 and the minor version is 0 2 2 1 http //tizen org/feature/platform version name domstring the platform return the platform version name e g tizen 2 0 magnolia, tizen 2 1 nectarine 2 3 the following table lists the profile feature keys key type description version http //tizen org/feature/profile systeminfoprofile the platform returns a compliant device profile such as "mobile", "wearable" for this key 2 2 1 the following table lists the sensor feature keys key type description version http //tizen org/feature/sensor accelerometer boolean the platform returns true for this key, if the device supports the acceleration sensor 2 2 1 http //tizen org/feature/sensor accelerometer wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor accelerometer key, if the device supports the wake-up operation by the acceleration sensor 2 2 1 http //tizen org/feature/sensor activity_recognition boolean the platform returns true for this key, if the device supports activity recognition 2 3 http //tizen org/feature/sensor barometer boolean the platform returns true for this key, if the device supports the barometer pressure sensor 2 2 1 http //tizen org/feature/sensor barometer wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor barometer key, if the device supports the wake-up operation by the barometer sensor 2 2 1 http //tizen org/feature/sensor gesture_recognition boolean the platform returns true for this key, if the device supports the gesture recognition 2 3 http //tizen org/feature/sensor gravity boolean the platform returns true for this key, if the device supports gravity 2 3 http //tizen org/feature/sensor gyroscope boolean the platform returns true for this key, if the device supports gyroscope 2 2 1 http //tizen org/feature/sensor gyroscope_rotation_vector boolean the platform returns true for this key, if the device supports gyroscope rotation vector 3 0 http //tizen org/feature/sensor gyroscope wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor gyroscope key, if the device supports the wake-up operation by the gyro sensor 2 2 1 http //tizen org/feature/sensor heart_rate_monitor boolean the platform returns true for this key if the device supports hrm 2 3 http //tizen org/feature/sensor heart_rate_monitor led_green boolean the platform returns true for this key if the device supports green light spectrum 2 3 1 http //tizen org/feature/sensor heart_rate_monitor led_ir boolean the platform returns true for this key if the device supports infrared spectrum 2 3 1 http //tizen org/feature/sensor heart_rate_monitor led_red boolean the platform returns true for this key if the device supports red light spectrum 2 3 1 http //tizen org/feature/sensor humidity boolean the platform returns true for this key, if the device supports the humidity sensor 2 3 http //tizen org/feature/sensor linear_acceleration boolean the platform returns true for this key, if the device supports the linear acceleration sensor 2 3 http //tizen org/feature/sensor magnetometer boolean the platform returns true for this key, if the device supports the magnetic sensor 2 2 1 http //tizen org/feature/sensor magnetometer wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor magnetometer key, if the device supports the wake-up operation by the magnetic sensor 2 2 1 http //tizen org/feature/sensor pedometer boolean the platform returns true for this key, if the device supports pedometer 2 3 http //tizen org/feature/sensor photometer boolean the platform returns true for this key, if the device supports the photometer sensor 2 2 1 http //tizen org/feature/sensor photometer wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor photometer key, if the device supports the wake-up operation by the photo sensor 2 2 1 http //tizen org/feature/sensor proximity boolean the platform returns true for this key, if the device supports the proximity sensor 2 2 1 http //tizen org/feature/sensor proximity wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor proximity key, if the device supports the wake-up operation by the proximity sensor 2 2 1 http //tizen org/feature/sensor rotation_vector boolean the platform returns true for this key, if the device supports the rotation vector sensor 2 3 http //tizen org/feature/sensor sleep_monitor boolean the platform returns true for this key, if the device supports sleep_monitor 3 0 http //tizen org/feature/sensor temperature boolean the platform returns true for this key, if the device supports the temperature sensor 2 3 http //tizen org/feature/sensor tiltmeter boolean the platform returns true for this key, if the device supports the tilt sensor 2 2 1 http //tizen org/feature/sensor tiltmeter wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor tiltmeter key, if the device supports the wake-up operation by the tilt sensor 2 2 1 http //tizen org/feature/sensor ultraviolet boolean the platform returns true for this key if the device supports ultraviolet sensor 2 3 http //tizen org/feature/sensor wrist_up boolean the platform returns true for this key if the device supports wrist_up 2 3 the following table lists the screen feature keys key type description version http //tizen org/feature/screen boolean the platform returns true for this key, if the device has a display screen 2 3 http //tizen org/feature/screen auto_rotation boolean the platform returns true for this key, if the device supports screen auto-rotation 2 2 1 http //tizen org/feature/screen bpp long the platform returns the number of bits per pixel supported by the device for this key the value depends on the screen, and is typically 8, 16, 24, or 32 2 2 1 http //tizen org/feature/screen coordinate_system size large boolean the platform returns true for this key, if the device supports the large screen size for the coordinate system 2 2 1 http //tizen org/feature/screen coordinate_system size normal boolean the platform returns true for this key, if the device supports the normal screen size for the coordinate system 2 2 1 http //tizen org/feature/screen dpi long the platform returns the number of dots per inch supported by the device for this key 2 2 1 http //tizen org/feature/screen height long the platform returns the height of the screen in pixels supported by the device for this key 2 2 1 http //tizen org/feature/screen output hdmi boolean the platform returns true for this key, if the device supports hdmi output 2 2 1 http //tizen org/feature/screen output rca boolean the platform returns true for this key, if the device supports rca output 2 2 1 http //tizen org/feature/screen shape circle boolean the platform returns true for this key, if the device supports a circular shaped screen 2 3 1 http //tizen org/feature/screen shape rectangle boolean the platform returns true for this key, if the device supports a rectangular shaped screen 2 3 1 http //tizen org/feature/screen size all boolean the platform can return true if the device supports any of screen sizes and resolutions if the device has a display screen, it returns true 2 2 1 http //tizen org/feature/screen size large boolean the platform can return true if the device supports the large screen size 2 2 1 http //tizen org/feature/screen size normal boolean the platform can return true the device supports the normal screen size 2 2 1 http //tizen org/feature/screen size normal 240 400 boolean the platform returns true for this key, if the device supports the 240 x 400 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 320 320 boolean the platform returns true for this key, if the device supports the 320 x 320 resolution for the normal screen size the platform can return true for multiple resolution keys 2 3 http //tizen org/feature/screen size normal 320 480 boolean the platform returns true for this key, if the device supports the 320 x 480 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 360 360 boolean the platform returns true for this key, if the device supports the 360 x 360 resolution for the normal screen size the platform can return true for multiple resolution keys 2 3 2 http //tizen org/feature/screen size normal 360 480 boolean the platform returns true for this key, if the device supports the 360 x 480 resolution for the normal screen size the platform can return true for multiple resolution keys 2 3 http //tizen org/feature/screen size normal 480 800 boolean the platform returns true for this key, if the device supports the 480 x 800 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 540 960 boolean the platform returns true for this key, if the device supports the 540 x 960 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 600 1024 boolean the platform returns true for this key, if the device supports the 600 x 1024 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 720 1280 boolean the platform returns true for this key, if the device supports the 720 x 1280 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 1080 1920 boolean the platform returns true for this key, if the device supports the 1080 x 1920 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen width long the platform returns the width of the screen in pixels supported by the device for this key 2 2 1 the following table lists the shell dynamic box feature keys key type description version http //tizen org/feature/shell appwidget boolean the platform returns true for this key, if the device supports the widget since 2 3 1, this key indicates only native widget 2 2 1 the following table lists the sip feature keys key type description version http //tizen org/feature/sip voip boolean the platform returns true for this key, if the device supports the voice over internet protocol voip 2 2 1 the following table lists the speech feature keys key type description version http //tizen org/feature/speech recognition boolean the platform returns true for this key, if the device supports speech recognition stt 2 2 1 http //tizen org/feature/speech synthesis boolean the platform returns true for this key, if the device supports speech synthesis tts 2 2 1 http //tizen org/feature/speech control boolean the platform returns true for this key, if the device supports speech control 4 0 the following table lists the tv feature keys key type description version http //tizen org/feature/tv audio boolean the platform returns true for this key, if the device supports control of tv audio if it is true, tvaudiocontrol api is supported 2 3 http //tizen org/feature/tv display boolean the platform returns true for this key, if the device supports getting information about the effects of stereoscopy 3d mode if it is true, tv display control api is supported 2 3 http //tizen org/feature/tv inputdevice boolean the platform returns true for this key, if the device supports receiving key events generated when the user presses a key of an input device for example a tv remote control if it is true, tv input device api is supported 2 3 http //tizen org/feature/tv pip boolean the platform returns true for this key, if the device supports control of tv window e g main window, pip window if it is true, tv window api is supported 2 3 the following table lists the usb feature keys key type description version http //tizen org/feature/usb accessory boolean the platform returns true for this key, if the device supports the usb client or accessory mode 2 2 1 http //tizen org/feature/usb host boolean the platform returns true for this key, if the device supports the usb host mode 2 2 1 the following table lists the vision feature keys key type description version http //tizen org/feature/vision face_recognition boolean the platform returns true for this key, if the device supports face recognition 2 2 1 http //tizen org/feature/vision image_recognition boolean the platform returns true for this key, if the device supports image recognition 2 2 1 http //tizen org/feature/vision qrcode_generation boolean the platform returns true for this key, if the device supports qr code generation 2 2 1 http //tizen org/feature/vision qrcode_recognition boolean the platform returns true for this key, if the device supports qr code recognition 2 2 1 the following table lists the web service model feature keys key type description version http //tizen org/feature/web service boolean the platform returns true for this key, if the device supports the web service model 2 3 the following table lists the build information key key type description version http //tizen org/system/build date domstring the platform returns the build date the format yyyy mm dd 2 3 http //tizen org/system/build string domstring the platform returns the build string including build date and time 2 3 http //tizen org/system/build time domstring the platform returns the build time the format hh mm ss 2 3 http //tizen org/system/manufacturer domstring the platform returns the device manufacturer's name 2 3 http //tizen org/system/build release domstring the platform returns the build version information the build version information is made when the platform image is created 3 0 http //tizen org/system/build type domstring the platform returns the build type, such as "user" or "eng" the build type is made when the platform image is created 3 0 http //tizen org/system/build variant domstring the platform returns the variant release information the variant release information is made when the platform image is created 3 0 http //tizen org/system/build id domstring the platform returns the build id the build id is made when the platform image is created 3 0 the following table lists the model name key key type description version http //tizen org/system/model_name domstring the platform returns the model name 2 3 the following table lists the platform system keys key type description version http //tizen org/system/platform communication_processor domstring the platform returns the device communication processor name 2 3 http //tizen org/system/platform name domstring the platform returns the platform name it must be tizen 2 2 1 http //tizen org/system/platform processor domstring the platform returns the device processor name 2 3 the following table lists the tizen id system key key type description version http //tizen org/system/tizenid domstring the platform returns the tizen id it is a randomly generated value based on the model name 2 3
Develop Smart Hospitality Display
apigetting device capabilities using systeminfo api the following keys are available to obtain the device capability information using systeminfo api device capability keys battery camera content api database download api graphics input iotcon push api led location microphone multi-point touch multimedia transcoder network opengl® es platform profile sensor screen shell dynamic box sip speech tv usb vision web service system keys build information model name platform name tizen id the following table lists the keys to check if a device has a battery key type description version http //tizen org/feature/battery boolean the platform returns true for this key, if the device has a battery if it is true, w3c battery status api, battery property in systeminfo api, and power api must be supported 2 3 the following table lists the camera feature keys key type description version http //tizen org/feature/camera boolean the platform returns true for this key, if the device provides any kind of a camera if it is true, w3c getusermedia and html media capture apis are supported 2 2 1 http //tizen org/feature/camera back boolean the platform returns true for this key and the http //tizen org/feature/camera key, if the device provides a back-facing camera 2 2 1 http //tizen org/feature/camera back flash boolean the platform returns true for this key and the http //tizen org/feature/camera back key, if the device provides a back-facing camera with a flash 2 2 1 http //tizen org/feature/camera front boolean the platform returns true for this key and the http //tizen org/feature/camera key, if the device provides a front-facing camera 2 2 1 http //tizen org/feature/camera front flash boolean the platform returns true for this key and the http //tizen org/feature/camera front key, if the device provides a front-facing camera with a flash 2 2 1 the following table lists the keys related to content api features key type description version http //tizen org/feature/content scanning others boolean the platform returns true for this key, if the device supports the media scanning feature for "other"-type files which are not included in the media content types such as "image", "video", "sound" or "music" 4 0 the following table lists the database feature keys key type description version http //tizen org/feature/database encryption boolean the platform returns true for this key, if the device supports database encryption 2 2 1 the following table lists the keys to check if download api is supported on a tizen device key type description version http //tizen org/feature/download boolean the platform returns true for this key, if the device supports download api 2 3 http //tizen org/feature/network telephony boolean the platform returns true for this key, if the device supports all apis which require telephony feature if it is true, "cellular" in downloadnetworktype is supported 2 2 1 http //tizen org/feature/network wifi boolean the platform returns true for this key, if the device supports all apis which require wi-fi if it is true, "wifi" in downloadnetworktype is supported 2 2 1 the following table lists the graphics feature keys key type description version http //tizen org/feature/graphics acceleration boolean the platform returns true for this key, if the device supports graphics hardware acceleration 2 2 1 the following table lists the input feature keys key type description version http //tizen org/feature/input keyboard boolean the platform returns true for this key, if the device provides a built-in keyboard supporting any keyboard layout 2 2 1 http //tizen org/feature/input keyboard layout domstring the platform returns the keyboard layout such as qwerty supported by the built-in keyboard for this key and returns true for the http //tizen org/feature/input keyboard key if the device does not provide a built-in keyboard, the platform returns an empty string for this key and returns false for the http //tizen org/feature/input keyboard key 2 2 1 http //tizen org/feature/input rotating_bezel boolean the platform returns true for this key, if the device provides a built-in rotating bezel 2 3 1 the following table lists the keys related to iotcon api features key type description version http //tizen org/feature/iot ocf boolean the platform returns true for this key, if the device supports the iot connectivity if it is true, iotcon api is supported 4 0 the following table lists the led feature key key type description version http //tizen org/feature/led boolean the platform returns true for this key, if the device supports led 2 3 the following table lists the location feature keys key type description version http //tizen org/feature/location boolean the platform returns true for this key, if the device supports location positioning 2 2 1 http //tizen org/feature/location batch boolean the platform returns true for this key and the http //tizen org/feature/location key, if the device supports gps batch feature 2 3 http //tizen org/feature/location gps boolean the platform returns true and the http //tizen org/feature/location, if the device supports the global positioning system gps 2 2 1 http //tizen org/feature/location wps boolean the platform returns true for this key and the http //tizen org/feature/location key, if the device supports the wi-fi-based positioning system wps 2 2 1 the following table lists the microphone feature keys key type description version http //tizen org/feature/microphone boolean the platform returns true for this key, if the device supports a microphone if it is true, w3c getusermedia and html media capture apis are supported 2 2 1 http //tizen org/feature/media audio_recording boolean the platform returns true for this key, if the device supports to record audio files on a device if it is true, cordova media api is supported 3 0 the following table lists the multi-point touch feature keys key type description version http //tizen org/feature/multi_point_touch pinch_zoom boolean the platform returns true for this key, if the device supports pinch zoom gestures 2 2 1 http //tizen org/feature/multi_point_touch point_count long the platform returns the maximum number of supported multi-touch points for this key the platform returns a value less than 2 for this key, if the device does not support multi-point touch 2 2 1 the following table lists the multimedia transcoder feature key key type description version http //tizen org/feature/multimedia transcoder boolean the platform returns true for this key, if the device supports multimedia transcoder 2 3 the following table lists the network feature keys key type description version http //tizen org/capability/network bluetooth always_on boolean the platform returns true for this key, if the device must always enable bluetooth it means that an application cannot change the bluetooth's state visibility, connectivity, device name 2 3 http //tizen org/feature/network bluetooth boolean the platform returns true for this key, if the device supports bluetooth 2 2 1 http //tizen org/feature/network bluetooth audio call boolean the platform returns true for this key, if the device supports bluetooth handsfree profile hfp 2 3 http //tizen org/feature/network bluetooth audio media boolean the platform returns true for this key, if the device supports bluetooth advanced audio distribute profile a2dp 2 3 http //tizen org/feature/network bluetooth health boolean the platform returns true for this key, if the device supports bluetooth health device profile hdp 2 3 http //tizen org/feature/network bluetooth hid boolean the platform returns true for this key, if the device supports bluetooth human input device hid 2 3 http //tizen org/feature/network bluetooth le boolean the platform returns true for this key, if the device supports bluetooth low energy related methods in bluetooth api 2 3 http //tizen org/feature/network bluetooth opp boolean the platform returns true for this key, if the device supports bluetooth object push profile opp 2 3 http //tizen org/feature/network ethernet boolean the platform returns true for this key, if the device supports ethernet if it is true, "all" in downloadnetworktype and systeminfoethernetnetwork is supported 2 4 http //tizen org/feature/network internet boolean the platform returns true for this key, if the device supports internet 2 3 1 http //tizen org/feature/network net_proxy boolean the platform returns true for this key, if the device supports network proxy for internet connection 3 0 http //tizen org/feature/network nfc boolean the platform returns true for this key, if the device supports near field communication nfc 2 2 1 http //tizen org/feature/network nfc card_emulation boolean the platform returns true for this key, if the device is recognized by the nfc card readers 2 3 http //tizen org/feature/network nfc card_emulation hce boolean the platform returns true for this key, if the device supports nfc host-based card emulation 2 3 1 http //tizen org/feature/network nfc p2p boolean the platform returns true for this key, if the device supports p2p apis which require near field communication nfc 2 3 1 http //tizen org/feature/network nfc reserved_push boolean the platform returns true for this key and the http //tizen org/feature/network nfc key, if the device supports the nfc reserved push feature 2 2 1 http //tizen org/feature/network nfc tag boolean the platform returns true for this key, if the device supports tag apis which require near field communication nfc 2 3 1 http //tizen org/feature/network push boolean the platform returns true for this key, if the device supports push api which requires the ip push service provided by the tizen reference implementation 2 2 1 http //tizen org/feature/network secure_element boolean the platform returns true for this key, if the device supports secure elements 2 2 1 http //tizen org/feature/network telephony boolean the platform returns true for this key, if the device supports the telephony related apis 2 2 1 http //tizen org/feature/network telephony mms boolean the platform returns true for this key and the http //tizen org/feature/network telephony key, if the device supports mms 2 2 1 http //tizen org/feature/network wifi boolean the platform returns true for this key, if the device supports all apis which require wi-fi 2 2 1 http //tizen org/feature/network wifi direct boolean the platform returns true for this key and the http //tizen org/feature/network wifi key, if the device supports wi-fi direct™ 2 2 1 the following table lists the opengl® es feature keys key type description version http //tizen org/feature/opengles boolean the platform returns true for this key, if the device supports any opengl® es version and any texture format 2 2 1 http //tizen org/feature/opengles texture_format domstring the supported texture formats for the opengl® es e g "3dc/atc/etc/ptc" the platform returns an empty string for this key if opengl® es or compressed texture formats are not supported 2 3 http //tizen org/feature/opengles texture_format 3dc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the 3dc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles texture_format atc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the atc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles texture_format etc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the etc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles texture_format ptc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the ptc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles texture_format pvrtc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the pvrtc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles texture_format utc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the utc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles version 1_1 boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the opengl® es version 1 1 2 2 1 http //tizen org/feature/opengles version 2_0 boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the opengl® es version 2 0 2 2 1 the following table lists the platform feature keys key type description version http //tizen org/feature/platform core api version domstring the version of the tizen core api in the [major] [minor] format for example, "1 0" represents a web api version where the major version is 1 and the minor version is 0 if a device doesn't provide tizen core api, it returns an empty string "" 2 3 http //tizen org/feature/platform core cpu arch domstring the platform returns the cpu architecture e g "armv7", "x86" of a device 2 3 http //tizen org/feature/platform core cpu arch armv6 boolean the platform returns true for this key, if the device runs on the armv6 cpu architecture 2 2 1 http //tizen org/feature/platform core cpu arch armv7 boolean the platform returns true for this key, if the device runs on the armv7 cpu architecture 2 2 1 http //tizen org/feature/platform core cpu arch x86 boolean the platform returns true for this key, if the device runs on the x86 cpu architecture 2 2 1 http //tizen org/feature/platform core cpu frequency long the platform returns the frequency at which a core cpu is running unit mhz 2 3 http //tizen org/feature/platform core fpu arch domstring the platform returns the fpu architecture e g "vfpv3", "ssse3" of a device if there is no fpu on a device, it returns an empty string "" 2 3 http //tizen org/feature/platform core fpu arch sse2 boolean the platform returns true for this key, if the device runs on the sse2 fpu architecture 2 2 1 http //tizen org/feature/platform core fpu arch sse3 boolean the platform returns true for this key, if the device runs on the sse3 fpu architecture 2 2 1 http //tizen org/feature/platform core fpu arch ssse3 boolean the platform returns true for this key, if the device runs on the ssse3 fpu architecture 2 2 1 http //tizen org/feature/platform core fpu arch vfpv2 boolean the platform returns true for this key, if the device runs on the vfpv2 fpu architecture 2 2 1 http //tizen org/feature/platform core fpu arch vfpv3 boolean the platform returns true for this key, if the device runs on the vfpv3 fpu architecture 2 2 1 http //tizen org/feature/platform native api version domstring the version of the native api in the [major] [minor] format for example, 1 0 represents a native api version where the major version is 1 and the minor version is 0 if a device doesn't provide tizen native api, it returns an empty string "" 2 2 1 http //tizen org/feature/platform native osp_compatible boolean the platform returns true for this key, if the device supports the bada compatibility mode 2 2 1 http //tizen org/feature/platform version domstring the version of the platform in the [major] [minor] [patch version] format for example, 1 0 0 represents a platform version where the major version is 1 and the minor and build versions are 0 2 2 1 http //tizen org/feature/platform web api version domstring the version of the web api in the [major] [minor] format for example, 1 0 represents a web api version where the major version is 1 and the minor version is 0 2 2 1 http //tizen org/feature/platform version name domstring the platform return the platform version name e g tizen 2 0 magnolia, tizen 2 1 nectarine 2 3 the following table lists the profile feature keys key type description version http //tizen org/feature/profile systeminfoprofile the platform returns a compliant device profile such as "mobile", "wearable" for this key 2 2 1 the following table lists the sensor feature keys key type description version http //tizen org/feature/sensor accelerometer boolean the platform returns true for this key, if the device supports the acceleration sensor 2 2 1 http //tizen org/feature/sensor accelerometer wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor accelerometer key, if the device supports the wake-up operation by the acceleration sensor 2 2 1 http //tizen org/feature/sensor activity_recognition boolean the platform returns true for this key, if the device supports activity recognition 2 3 http //tizen org/feature/sensor barometer boolean the platform returns true for this key, if the device supports the barometer pressure sensor 2 2 1 http //tizen org/feature/sensor barometer wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor barometer key, if the device supports the wake-up operation by the barometer sensor 2 2 1 http //tizen org/feature/sensor gesture_recognition boolean the platform returns true for this key, if the device supports the gesture recognition 2 3 http //tizen org/feature/sensor gravity boolean the platform returns true for this key, if the device supports gravity 2 3 http //tizen org/feature/sensor gyroscope boolean the platform returns true for this key, if the device supports gyroscope 2 2 1 http //tizen org/feature/sensor gyroscope_rotation_vector boolean the platform returns true for this key, if the device supports gyroscope rotation vector 3 0 http //tizen org/feature/sensor gyroscope wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor gyroscope key, if the device supports the wake-up operation by the gyro sensor 2 2 1 http //tizen org/feature/sensor heart_rate_monitor boolean the platform returns true for this key if the device supports hrm 2 3 http //tizen org/feature/sensor heart_rate_monitor led_green boolean the platform returns true for this key if the device supports green light spectrum 2 3 1 http //tizen org/feature/sensor heart_rate_monitor led_ir boolean the platform returns true for this key if the device supports infrared spectrum 2 3 1 http //tizen org/feature/sensor heart_rate_monitor led_red boolean the platform returns true for this key if the device supports red light spectrum 2 3 1 http //tizen org/feature/sensor humidity boolean the platform returns true for this key, if the device supports the humidity sensor 2 3 http //tizen org/feature/sensor linear_acceleration boolean the platform returns true for this key, if the device supports the linear acceleration sensor 2 3 http //tizen org/feature/sensor magnetometer boolean the platform returns true for this key, if the device supports the magnetic sensor 2 2 1 http //tizen org/feature/sensor magnetometer wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor magnetometer key, if the device supports the wake-up operation by the magnetic sensor 2 2 1 http //tizen org/feature/sensor pedometer boolean the platform returns true for this key, if the device supports pedometer 2 3 http //tizen org/feature/sensor photometer boolean the platform returns true for this key, if the device supports the photometer sensor 2 2 1 http //tizen org/feature/sensor photometer wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor photometer key, if the device supports the wake-up operation by the photo sensor 2 2 1 http //tizen org/feature/sensor proximity boolean the platform returns true for this key, if the device supports the proximity sensor 2 2 1 http //tizen org/feature/sensor proximity wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor proximity key, if the device supports the wake-up operation by the proximity sensor 2 2 1 http //tizen org/feature/sensor rotation_vector boolean the platform returns true for this key, if the device supports the rotation vector sensor 2 3 http //tizen org/feature/sensor sleep_monitor boolean the platform returns true for this key, if the device supports sleep_monitor 3 0 http //tizen org/feature/sensor temperature boolean the platform returns true for this key, if the device supports the temperature sensor 2 3 http //tizen org/feature/sensor tiltmeter boolean the platform returns true for this key, if the device supports the tilt sensor 2 2 1 http //tizen org/feature/sensor tiltmeter wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor tiltmeter key, if the device supports the wake-up operation by the tilt sensor 2 2 1 http //tizen org/feature/sensor ultraviolet boolean the platform returns true for this key if the device supports ultraviolet sensor 2 3 http //tizen org/feature/sensor wrist_up boolean the platform returns true for this key if the device supports wrist_up 2 3 the following table lists the screen feature keys key type description version http //tizen org/feature/screen boolean the platform returns true for this key, if the device has a display screen 2 3 http //tizen org/feature/screen auto_rotation boolean the platform returns true for this key, if the device supports screen auto-rotation 2 2 1 http //tizen org/feature/screen bpp long the platform returns the number of bits per pixel supported by the device for this key the value depends on the screen, and is typically 8, 16, 24, or 32 2 2 1 http //tizen org/feature/screen coordinate_system size large boolean the platform returns true for this key, if the device supports the large screen size for the coordinate system 2 2 1 http //tizen org/feature/screen coordinate_system size normal boolean the platform returns true for this key, if the device supports the normal screen size for the coordinate system 2 2 1 http //tizen org/feature/screen dpi long the platform returns the number of dots per inch supported by the device for this key 2 2 1 http //tizen org/feature/screen height long the platform returns the height of the screen in pixels supported by the device for this key 2 2 1 http //tizen org/feature/screen output hdmi boolean the platform returns true for this key, if the device supports hdmi output 2 2 1 http //tizen org/feature/screen output rca boolean the platform returns true for this key, if the device supports rca output 2 2 1 http //tizen org/feature/screen shape circle boolean the platform returns true for this key, if the device supports a circular shaped screen 2 3 1 http //tizen org/feature/screen shape rectangle boolean the platform returns true for this key, if the device supports a rectangular shaped screen 2 3 1 http //tizen org/feature/screen size all boolean the platform can return true if the device supports any of screen sizes and resolutions if the device has a display screen, it returns true 2 2 1 http //tizen org/feature/screen size large boolean the platform can return true if the device supports the large screen size 2 2 1 http //tizen org/feature/screen size normal boolean the platform can return true the device supports the normal screen size 2 2 1 http //tizen org/feature/screen size normal 240 400 boolean the platform returns true for this key, if the device supports the 240 x 400 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 320 320 boolean the platform returns true for this key, if the device supports the 320 x 320 resolution for the normal screen size the platform can return true for multiple resolution keys 2 3 http //tizen org/feature/screen size normal 320 480 boolean the platform returns true for this key, if the device supports the 320 x 480 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 360 360 boolean the platform returns true for this key, if the device supports the 360 x 360 resolution for the normal screen size the platform can return true for multiple resolution keys 2 3 2 http //tizen org/feature/screen size normal 360 480 boolean the platform returns true for this key, if the device supports the 360 x 480 resolution for the normal screen size the platform can return true for multiple resolution keys 2 3 http //tizen org/feature/screen size normal 480 800 boolean the platform returns true for this key, if the device supports the 480 x 800 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 540 960 boolean the platform returns true for this key, if the device supports the 540 x 960 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 600 1024 boolean the platform returns true for this key, if the device supports the 600 x 1024 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 720 1280 boolean the platform returns true for this key, if the device supports the 720 x 1280 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 1080 1920 boolean the platform returns true for this key, if the device supports the 1080 x 1920 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen width long the platform returns the width of the screen in pixels supported by the device for this key 2 2 1 the following table lists the shell dynamic box feature keys key type description version http //tizen org/feature/shell appwidget boolean the platform returns true for this key, if the device supports the widget since 2 3 1, this key indicates only native widget 2 2 1 the following table lists the sip feature keys key type description version http //tizen org/feature/sip voip boolean the platform returns true for this key, if the device supports the voice over internet protocol voip 2 2 1 the following table lists the speech feature keys key type description version http //tizen org/feature/speech recognition boolean the platform returns true for this key, if the device supports speech recognition stt 2 2 1 http //tizen org/feature/speech synthesis boolean the platform returns true for this key, if the device supports speech synthesis tts 2 2 1 http //tizen org/feature/speech control boolean the platform returns true for this key, if the device supports speech control 4 0 the following table lists the tv feature keys key type description version http //tizen org/feature/tv audio boolean the platform returns true for this key, if the device supports control of tv audio if it is true, tvaudiocontrol api is supported 2 3 http //tizen org/feature/tv display boolean the platform returns true for this key, if the device supports getting information about the effects of stereoscopy 3d mode if it is true, tv display control api is supported 2 3 http //tizen org/feature/tv inputdevice boolean the platform returns true for this key, if the device supports receiving key events generated when the user presses a key of an input device for example a tv remote control if it is true, tv input device api is supported 2 3 http //tizen org/feature/tv pip boolean the platform returns true for this key, if the device supports control of tv window e g main window, pip window if it is true, tv window api is supported 2 3 the following table lists the usb feature keys key type description version http //tizen org/feature/usb accessory boolean the platform returns true for this key, if the device supports the usb client or accessory mode 2 2 1 http //tizen org/feature/usb host boolean the platform returns true for this key, if the device supports the usb host mode 2 2 1 the following table lists the vision feature keys key type description version http //tizen org/feature/vision face_recognition boolean the platform returns true for this key, if the device supports face recognition 2 2 1 http //tizen org/feature/vision image_recognition boolean the platform returns true for this key, if the device supports image recognition 2 2 1 http //tizen org/feature/vision qrcode_generation boolean the platform returns true for this key, if the device supports qr code generation 2 2 1 http //tizen org/feature/vision qrcode_recognition boolean the platform returns true for this key, if the device supports qr code recognition 2 2 1 the following table lists the web service model feature keys key type description version http //tizen org/feature/web service boolean the platform returns true for this key, if the device supports the web service model 2 3 the following table lists the build information key key type description version http //tizen org/system/build date domstring the platform returns the build date the format yyyy mm dd 2 3 http //tizen org/system/build string domstring the platform returns the build string including build date and time 2 3 http //tizen org/system/build time domstring the platform returns the build time the format hh mm ss 2 3 http //tizen org/system/manufacturer domstring the platform returns the device manufacturer's name 2 3 http //tizen org/system/build release domstring the platform returns the build version information the build version information is made when the platform image is created 3 0 http //tizen org/system/build type domstring the platform returns the build type, such as "user" or "eng" the build type is made when the platform image is created 3 0 http //tizen org/system/build variant domstring the platform returns the variant release information the variant release information is made when the platform image is created 3 0 http //tizen org/system/build id domstring the platform returns the build id the build id is made when the platform image is created 3 0 the following table lists the model name key key type description version http //tizen org/system/model_name domstring the platform returns the model name 2 3 the following table lists the platform system keys key type description version http //tizen org/system/platform communication_processor domstring the platform returns the device communication processor name 2 3 http //tizen org/system/platform name domstring the platform returns the platform name it must be tizen 2 2 1 http //tizen org/system/platform processor domstring the platform returns the device processor name 2 3 the following table lists the tizen id system key key type description version http //tizen org/system/tizenid domstring the platform returns the tizen id it is a randomly generated value based on the model name 2 3
Develop Smart Signage
apigetting device capabilities using systeminfo api the following keys are available to obtain the device capability information using systeminfo api device capability keys battery camera content api database download api graphics input iotcon push api led location microphone multi-point touch multimedia transcoder network opengl® es platform profile sensor screen shell dynamic box sip speech tv usb vision web service system keys build information model name platform name tizen id the following table lists the keys to check if a device has a battery key type description version http //tizen org/feature/battery boolean the platform returns true for this key, if the device has a battery if it is true, w3c battery status api, battery property in systeminfo api, and power api must be supported 2 3 the following table lists the camera feature keys key type description version http //tizen org/feature/camera boolean the platform returns true for this key, if the device provides any kind of a camera if it is true, w3c getusermedia and html media capture apis are supported 2 2 1 http //tizen org/feature/camera back boolean the platform returns true for this key and the http //tizen org/feature/camera key, if the device provides a back-facing camera 2 2 1 http //tizen org/feature/camera back flash boolean the platform returns true for this key and the http //tizen org/feature/camera back key, if the device provides a back-facing camera with a flash 2 2 1 http //tizen org/feature/camera front boolean the platform returns true for this key and the http //tizen org/feature/camera key, if the device provides a front-facing camera 2 2 1 http //tizen org/feature/camera front flash boolean the platform returns true for this key and the http //tizen org/feature/camera front key, if the device provides a front-facing camera with a flash 2 2 1 the following table lists the keys related to content api features key type description version http //tizen org/feature/content scanning others boolean the platform returns true for this key, if the device supports the media scanning feature for "other"-type files which are not included in the media content types such as "image", "video", "sound" or "music" 4 0 the following table lists the database feature keys key type description version http //tizen org/feature/database encryption boolean the platform returns true for this key, if the device supports database encryption 2 2 1 the following table lists the keys to check if download api is supported on a tizen device key type description version http //tizen org/feature/download boolean the platform returns true for this key, if the device supports download api 2 3 http //tizen org/feature/network telephony boolean the platform returns true for this key, if the device supports all apis which require telephony feature if it is true, "cellular" in downloadnetworktype is supported 2 2 1 http //tizen org/feature/network wifi boolean the platform returns true for this key, if the device supports all apis which require wi-fi if it is true, "wifi" in downloadnetworktype is supported 2 2 1 the following table lists the graphics feature keys key type description version http //tizen org/feature/graphics acceleration boolean the platform returns true for this key, if the device supports graphics hardware acceleration 2 2 1 the following table lists the input feature keys key type description version http //tizen org/feature/input keyboard boolean the platform returns true for this key, if the device provides a built-in keyboard supporting any keyboard layout 2 2 1 http //tizen org/feature/input keyboard layout domstring the platform returns the keyboard layout such as qwerty supported by the built-in keyboard for this key and returns true for the http //tizen org/feature/input keyboard key if the device does not provide a built-in keyboard, the platform returns an empty string for this key and returns false for the http //tizen org/feature/input keyboard key 2 2 1 http //tizen org/feature/input rotating_bezel boolean the platform returns true for this key, if the device provides a built-in rotating bezel 2 3 1 the following table lists the keys related to iotcon api features key type description version http //tizen org/feature/iot ocf boolean the platform returns true for this key, if the device supports the iot connectivity if it is true, iotcon api is supported 4 0 the following table lists the led feature key key type description version http //tizen org/feature/led boolean the platform returns true for this key, if the device supports led 2 3 the following table lists the location feature keys key type description version http //tizen org/feature/location boolean the platform returns true for this key, if the device supports location positioning 2 2 1 http //tizen org/feature/location batch boolean the platform returns true for this key and the http //tizen org/feature/location key, if the device supports gps batch feature 2 3 http //tizen org/feature/location gps boolean the platform returns true and the http //tizen org/feature/location, if the device supports the global positioning system gps 2 2 1 http //tizen org/feature/location wps boolean the platform returns true for this key and the http //tizen org/feature/location key, if the device supports the wi-fi-based positioning system wps 2 2 1 the following table lists the microphone feature keys key type description version http //tizen org/feature/microphone boolean the platform returns true for this key, if the device supports a microphone if it is true, w3c getusermedia and html media capture apis are supported 2 2 1 http //tizen org/feature/media audio_recording boolean the platform returns true for this key, if the device supports to record audio files on a device if it is true, cordova media api is supported 3 0 the following table lists the multi-point touch feature keys key type description version http //tizen org/feature/multi_point_touch pinch_zoom boolean the platform returns true for this key, if the device supports pinch zoom gestures 2 2 1 http //tizen org/feature/multi_point_touch point_count long the platform returns the maximum number of supported multi-touch points for this key the platform returns a value less than 2 for this key, if the device does not support multi-point touch 2 2 1 the following table lists the multimedia transcoder feature key key type description version http //tizen org/feature/multimedia transcoder boolean the platform returns true for this key, if the device supports multimedia transcoder 2 3 the following table lists the network feature keys key type description version http //tizen org/capability/network bluetooth always_on boolean the platform returns true for this key, if the device must always enable bluetooth it means that an application cannot change the bluetooth's state visibility, connectivity, device name 2 3 http //tizen org/feature/network bluetooth boolean the platform returns true for this key, if the device supports bluetooth 2 2 1 http //tizen org/feature/network bluetooth audio call boolean the platform returns true for this key, if the device supports bluetooth handsfree profile hfp 2 3 http //tizen org/feature/network bluetooth audio media boolean the platform returns true for this key, if the device supports bluetooth advanced audio distribute profile a2dp 2 3 http //tizen org/feature/network bluetooth health boolean the platform returns true for this key, if the device supports bluetooth health device profile hdp 2 3 http //tizen org/feature/network bluetooth hid boolean the platform returns true for this key, if the device supports bluetooth human input device hid 2 3 http //tizen org/feature/network bluetooth le boolean the platform returns true for this key, if the device supports bluetooth low energy related methods in bluetooth api 2 3 http //tizen org/feature/network bluetooth opp boolean the platform returns true for this key, if the device supports bluetooth object push profile opp 2 3 http //tizen org/feature/network ethernet boolean the platform returns true for this key, if the device supports ethernet if it is true, "all" in downloadnetworktype and systeminfoethernetnetwork is supported 2 4 http //tizen org/feature/network internet boolean the platform returns true for this key, if the device supports internet 2 3 1 http //tizen org/feature/network net_proxy boolean the platform returns true for this key, if the device supports network proxy for internet connection 3 0 http //tizen org/feature/network nfc boolean the platform returns true for this key, if the device supports near field communication nfc 2 2 1 http //tizen org/feature/network nfc card_emulation boolean the platform returns true for this key, if the device is recognized by the nfc card readers 2 3 http //tizen org/feature/network nfc card_emulation hce boolean the platform returns true for this key, if the device supports nfc host-based card emulation 2 3 1 http //tizen org/feature/network nfc p2p boolean the platform returns true for this key, if the device supports p2p apis which require near field communication nfc 2 3 1 http //tizen org/feature/network nfc reserved_push boolean the platform returns true for this key and the http //tizen org/feature/network nfc key, if the device supports the nfc reserved push feature 2 2 1 http //tizen org/feature/network nfc tag boolean the platform returns true for this key, if the device supports tag apis which require near field communication nfc 2 3 1 http //tizen org/feature/network push boolean the platform returns true for this key, if the device supports push api which requires the ip push service provided by the tizen reference implementation 2 2 1 http //tizen org/feature/network secure_element boolean the platform returns true for this key, if the device supports secure elements 2 2 1 http //tizen org/feature/network telephony boolean the platform returns true for this key, if the device supports the telephony related apis 2 2 1 http //tizen org/feature/network telephony mms boolean the platform returns true for this key and the http //tizen org/feature/network telephony key, if the device supports mms 2 2 1 http //tizen org/feature/network wifi boolean the platform returns true for this key, if the device supports all apis which require wi-fi 2 2 1 http //tizen org/feature/network wifi direct boolean the platform returns true for this key and the http //tizen org/feature/network wifi key, if the device supports wi-fi direct™ 2 2 1 the following table lists the opengl® es feature keys key type description version http //tizen org/feature/opengles boolean the platform returns true for this key, if the device supports any opengl® es version and any texture format 2 2 1 http //tizen org/feature/opengles texture_format domstring the supported texture formats for the opengl® es e g "3dc/atc/etc/ptc" the platform returns an empty string for this key if opengl® es or compressed texture formats are not supported 2 3 http //tizen org/feature/opengles texture_format 3dc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the 3dc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles texture_format atc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the atc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles texture_format etc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the etc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles texture_format ptc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the ptc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles texture_format pvrtc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the pvrtc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles texture_format utc boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the utc texture format for opengl® es 2 2 1 http //tizen org/feature/opengles version 1_1 boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the opengl® es version 1 1 2 2 1 http //tizen org/feature/opengles version 2_0 boolean the platform returns true for this key and the http //tizen org/feature/opengles key, if the device supports the opengl® es version 2 0 2 2 1 the following table lists the platform feature keys key type description version http //tizen org/feature/platform core api version domstring the version of the tizen core api in the [major] [minor] format for example, "1 0" represents a web api version where the major version is 1 and the minor version is 0 if a device doesn't provide tizen core api, it returns an empty string "" 2 3 http //tizen org/feature/platform core cpu arch domstring the platform returns the cpu architecture e g "armv7", "x86" of a device 2 3 http //tizen org/feature/platform core cpu arch armv6 boolean the platform returns true for this key, if the device runs on the armv6 cpu architecture 2 2 1 http //tizen org/feature/platform core cpu arch armv7 boolean the platform returns true for this key, if the device runs on the armv7 cpu architecture 2 2 1 http //tizen org/feature/platform core cpu arch x86 boolean the platform returns true for this key, if the device runs on the x86 cpu architecture 2 2 1 http //tizen org/feature/platform core cpu frequency long the platform returns the frequency at which a core cpu is running unit mhz 2 3 http //tizen org/feature/platform core fpu arch domstring the platform returns the fpu architecture e g "vfpv3", "ssse3" of a device if there is no fpu on a device, it returns an empty string "" 2 3 http //tizen org/feature/platform core fpu arch sse2 boolean the platform returns true for this key, if the device runs on the sse2 fpu architecture 2 2 1 http //tizen org/feature/platform core fpu arch sse3 boolean the platform returns true for this key, if the device runs on the sse3 fpu architecture 2 2 1 http //tizen org/feature/platform core fpu arch ssse3 boolean the platform returns true for this key, if the device runs on the ssse3 fpu architecture 2 2 1 http //tizen org/feature/platform core fpu arch vfpv2 boolean the platform returns true for this key, if the device runs on the vfpv2 fpu architecture 2 2 1 http //tizen org/feature/platform core fpu arch vfpv3 boolean the platform returns true for this key, if the device runs on the vfpv3 fpu architecture 2 2 1 http //tizen org/feature/platform native api version domstring the version of the native api in the [major] [minor] format for example, 1 0 represents a native api version where the major version is 1 and the minor version is 0 if a device doesn't provide tizen native api, it returns an empty string "" 2 2 1 http //tizen org/feature/platform native osp_compatible boolean the platform returns true for this key, if the device supports the bada compatibility mode 2 2 1 http //tizen org/feature/platform version domstring the version of the platform in the [major] [minor] [patch version] format for example, 1 0 0 represents a platform version where the major version is 1 and the minor and build versions are 0 2 2 1 http //tizen org/feature/platform web api version domstring the version of the web api in the [major] [minor] format for example, 1 0 represents a web api version where the major version is 1 and the minor version is 0 2 2 1 http //tizen org/feature/platform version name domstring the platform return the platform version name e g tizen 2 0 magnolia, tizen 2 1 nectarine 2 3 the following table lists the profile feature keys key type description version http //tizen org/feature/profile systeminfoprofile the platform returns a compliant device profile such as "mobile", "wearable" for this key 2 2 1 the following table lists the sensor feature keys key type description version http //tizen org/feature/sensor accelerometer boolean the platform returns true for this key, if the device supports the acceleration sensor 2 2 1 http //tizen org/feature/sensor accelerometer wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor accelerometer key, if the device supports the wake-up operation by the acceleration sensor 2 2 1 http //tizen org/feature/sensor activity_recognition boolean the platform returns true for this key, if the device supports activity recognition 2 3 http //tizen org/feature/sensor barometer boolean the platform returns true for this key, if the device supports the barometer pressure sensor 2 2 1 http //tizen org/feature/sensor barometer wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor barometer key, if the device supports the wake-up operation by the barometer sensor 2 2 1 http //tizen org/feature/sensor gesture_recognition boolean the platform returns true for this key, if the device supports the gesture recognition 2 3 http //tizen org/feature/sensor gravity boolean the platform returns true for this key, if the device supports gravity 2 3 http //tizen org/feature/sensor gyroscope boolean the platform returns true for this key, if the device supports gyroscope 2 2 1 http //tizen org/feature/sensor gyroscope_rotation_vector boolean the platform returns true for this key, if the device supports gyroscope rotation vector 3 0 http //tizen org/feature/sensor gyroscope wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor gyroscope key, if the device supports the wake-up operation by the gyro sensor 2 2 1 http //tizen org/feature/sensor heart_rate_monitor boolean the platform returns true for this key if the device supports hrm 2 3 http //tizen org/feature/sensor heart_rate_monitor led_green boolean the platform returns true for this key if the device supports green light spectrum 2 3 1 http //tizen org/feature/sensor heart_rate_monitor led_ir boolean the platform returns true for this key if the device supports infrared spectrum 2 3 1 http //tizen org/feature/sensor heart_rate_monitor led_red boolean the platform returns true for this key if the device supports red light spectrum 2 3 1 http //tizen org/feature/sensor humidity boolean the platform returns true for this key, if the device supports the humidity sensor 2 3 http //tizen org/feature/sensor linear_acceleration boolean the platform returns true for this key, if the device supports the linear acceleration sensor 2 3 http //tizen org/feature/sensor magnetometer boolean the platform returns true for this key, if the device supports the magnetic sensor 2 2 1 http //tizen org/feature/sensor magnetometer wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor magnetometer key, if the device supports the wake-up operation by the magnetic sensor 2 2 1 http //tizen org/feature/sensor pedometer boolean the platform returns true for this key, if the device supports pedometer 2 3 http //tizen org/feature/sensor photometer boolean the platform returns true for this key, if the device supports the photometer sensor 2 2 1 http //tizen org/feature/sensor photometer wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor photometer key, if the device supports the wake-up operation by the photo sensor 2 2 1 http //tizen org/feature/sensor proximity boolean the platform returns true for this key, if the device supports the proximity sensor 2 2 1 http //tizen org/feature/sensor proximity wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor proximity key, if the device supports the wake-up operation by the proximity sensor 2 2 1 http //tizen org/feature/sensor rotation_vector boolean the platform returns true for this key, if the device supports the rotation vector sensor 2 3 http //tizen org/feature/sensor sleep_monitor boolean the platform returns true for this key, if the device supports sleep_monitor 3 0 http //tizen org/feature/sensor temperature boolean the platform returns true for this key, if the device supports the temperature sensor 2 3 http //tizen org/feature/sensor tiltmeter boolean the platform returns true for this key, if the device supports the tilt sensor 2 2 1 http //tizen org/feature/sensor tiltmeter wakeup boolean the platform returns true for this key and the http //tizen org/feature/sensor tiltmeter key, if the device supports the wake-up operation by the tilt sensor 2 2 1 http //tizen org/feature/sensor ultraviolet boolean the platform returns true for this key if the device supports ultraviolet sensor 2 3 http //tizen org/feature/sensor wrist_up boolean the platform returns true for this key if the device supports wrist_up 2 3 the following table lists the screen feature keys key type description version http //tizen org/feature/screen boolean the platform returns true for this key, if the device has a display screen 2 3 http //tizen org/feature/screen auto_rotation boolean the platform returns true for this key, if the device supports screen auto-rotation 2 2 1 http //tizen org/feature/screen bpp long the platform returns the number of bits per pixel supported by the device for this key the value depends on the screen, and is typically 8, 16, 24, or 32 2 2 1 http //tizen org/feature/screen coordinate_system size large boolean the platform returns true for this key, if the device supports the large screen size for the coordinate system 2 2 1 http //tizen org/feature/screen coordinate_system size normal boolean the platform returns true for this key, if the device supports the normal screen size for the coordinate system 2 2 1 http //tizen org/feature/screen dpi long the platform returns the number of dots per inch supported by the device for this key 2 2 1 http //tizen org/feature/screen height long the platform returns the height of the screen in pixels supported by the device for this key 2 2 1 http //tizen org/feature/screen output hdmi boolean the platform returns true for this key, if the device supports hdmi output 2 2 1 http //tizen org/feature/screen output rca boolean the platform returns true for this key, if the device supports rca output 2 2 1 http //tizen org/feature/screen shape circle boolean the platform returns true for this key, if the device supports a circular shaped screen 2 3 1 http //tizen org/feature/screen shape rectangle boolean the platform returns true for this key, if the device supports a rectangular shaped screen 2 3 1 http //tizen org/feature/screen size all boolean the platform can return true if the device supports any of screen sizes and resolutions if the device has a display screen, it returns true 2 2 1 http //tizen org/feature/screen size large boolean the platform can return true if the device supports the large screen size 2 2 1 http //tizen org/feature/screen size normal boolean the platform can return true the device supports the normal screen size 2 2 1 http //tizen org/feature/screen size normal 240 400 boolean the platform returns true for this key, if the device supports the 240 x 400 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 320 320 boolean the platform returns true for this key, if the device supports the 320 x 320 resolution for the normal screen size the platform can return true for multiple resolution keys 2 3 http //tizen org/feature/screen size normal 320 480 boolean the platform returns true for this key, if the device supports the 320 x 480 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 360 360 boolean the platform returns true for this key, if the device supports the 360 x 360 resolution for the normal screen size the platform can return true for multiple resolution keys 2 3 2 http //tizen org/feature/screen size normal 360 480 boolean the platform returns true for this key, if the device supports the 360 x 480 resolution for the normal screen size the platform can return true for multiple resolution keys 2 3 http //tizen org/feature/screen size normal 480 800 boolean the platform returns true for this key, if the device supports the 480 x 800 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 540 960 boolean the platform returns true for this key, if the device supports the 540 x 960 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 600 1024 boolean the platform returns true for this key, if the device supports the 600 x 1024 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 720 1280 boolean the platform returns true for this key, if the device supports the 720 x 1280 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen size normal 1080 1920 boolean the platform returns true for this key, if the device supports the 1080 x 1920 resolution for the normal screen size the platform can return true for multiple resolution keys 2 2 1 http //tizen org/feature/screen width long the platform returns the width of the screen in pixels supported by the device for this key 2 2 1 the following table lists the shell dynamic box feature keys key type description version http //tizen org/feature/shell appwidget boolean the platform returns true for this key, if the device supports the widget since 2 3 1, this key indicates only native widget 2 2 1 the following table lists the sip feature keys key type description version http //tizen org/feature/sip voip boolean the platform returns true for this key, if the device supports the voice over internet protocol voip 2 2 1 the following table lists the speech feature keys key type description version http //tizen org/feature/speech recognition boolean the platform returns true for this key, if the device supports speech recognition stt 2 2 1 http //tizen org/feature/speech synthesis boolean the platform returns true for this key, if the device supports speech synthesis tts 2 2 1 http //tizen org/feature/speech control boolean the platform returns true for this key, if the device supports speech control 4 0 the following table lists the tv feature keys key type description version http //tizen org/feature/tv audio boolean the platform returns true for this key, if the device supports control of tv audio if it is true, tvaudiocontrol api is supported 2 3 http //tizen org/feature/tv display boolean the platform returns true for this key, if the device supports getting information about the effects of stereoscopy 3d mode if it is true, tv display control api is supported 2 3 http //tizen org/feature/tv inputdevice boolean the platform returns true for this key, if the device supports receiving key events generated when the user presses a key of an input device for example a tv remote control if it is true, tv input device api is supported 2 3 http //tizen org/feature/tv pip boolean the platform returns true for this key, if the device supports control of tv window e g main window, pip window if it is true, tv window api is supported 2 3 the following table lists the usb feature keys key type description version http //tizen org/feature/usb accessory boolean the platform returns true for this key, if the device supports the usb client or accessory mode 2 2 1 http //tizen org/feature/usb host boolean the platform returns true for this key, if the device supports the usb host mode 2 2 1 the following table lists the vision feature keys key type description version http //tizen org/feature/vision face_recognition boolean the platform returns true for this key, if the device supports face recognition 2 2 1 http //tizen org/feature/vision image_recognition boolean the platform returns true for this key, if the device supports image recognition 2 2 1 http //tizen org/feature/vision qrcode_generation boolean the platform returns true for this key, if the device supports qr code generation 2 2 1 http //tizen org/feature/vision qrcode_recognition boolean the platform returns true for this key, if the device supports qr code recognition 2 2 1 the following table lists the web service model feature keys key type description version http //tizen org/feature/web service boolean the platform returns true for this key, if the device supports the web service model 2 3 the following table lists the build information key key type description version http //tizen org/system/build date domstring the platform returns the build date the format yyyy mm dd 2 3 http //tizen org/system/build string domstring the platform returns the build string including build date and time 2 3 http //tizen org/system/build time domstring the platform returns the build time the format hh mm ss 2 3 http //tizen org/system/manufacturer domstring the platform returns the device manufacturer's name 2 3 http //tizen org/system/build release domstring the platform returns the build version information the build version information is made when the platform image is created 3 0 http //tizen org/system/build type domstring the platform returns the build type, such as "user" or "eng" the build type is made when the platform image is created 3 0 http //tizen org/system/build variant domstring the platform returns the variant release information the variant release information is made when the platform image is created 3 0 http //tizen org/system/build id domstring the platform returns the build id the build id is made when the platform image is created 3 0 the following table lists the model name key key type description version http //tizen org/system/model_name domstring the platform returns the model name 2 3 the following table lists the platform system keys key type description version http //tizen org/system/platform communication_processor domstring the platform returns the device communication processor name 2 3 http //tizen org/system/platform name domstring the platform returns the platform name it must be tizen 2 2 1 http //tizen org/system/platform processor domstring the platform returns the device processor name 2 3 the following table lists the tizen id system key key type description version http //tizen org/system/tizenid domstring the platform returns the tizen id it is a randomly generated value based on the model name 2 3
events mobile, smarttv, iot, marketplace, ai
blogdevelopers, designers, and partners all gathered in the san jose convention center for day 1 of sdc19. the day unfolded with big announcements, inspiring messages, and new updates on tools and sdks that allow developers to scale their services across billions of devices through an extensive, secure and connected ecosystem. check out the highlights below! 1. keynote samsung is advancing experience innovation, in collaboration with developers and partners. in the keynote, dj koh and other samsung leaders laid out the roadmap for the company’s future and highlighted some important product announcements. from new mobile computing experiences with one ui 2 to the smartthings rules api. highlighting ai expansion with bixby templates, devjam, bixby views, and natural language categories, there was plenty to help developers reach more customers on more devices than ever before. sdc19 also showcased how samsung is forging new partnerships with brands such as ibm, microsoft, intel, and more. if you couldn’t attend the keynote, watch the livestream video here or check out these key announcements on what’s next for samsung: redefining the mobile experience samsung is dedicated to expanding and improving the mobile experience. one ui 2 was announced at sdc19’s keynote and is designed for everyday simplicity. it includes new features that declutter the user interface making interactions more natural. now, the developer and user should have consistent experiences across all devices, not just smartphones. one ui 2.0 also show how samsung inspires developers with new experiences across devices and new form factors in the foldable category. devs, get excited! https://twitter.com/samsung_dev/status/1189248674263715840 8k strides for smart tv we know that picture quality is important to developers, and rightfully so. with ai scalenet, we’ve made it possible to stream high-quality 8k videos on networks with lower bandwidth capabilities. plus, check out these tools to help you bring new experiences across the nearly 100 million tizen-powered smart tvs. wits: automatically uploads a code edit to the tv, so developers can see their update almost immediately, significantly trimming development time easyst: makes testing content playback easier because you don’t need to build a test app to make sure your content is streaming correctly tifa (tizen identifier for advertising): gives consumers the option to limit ad tracking or opt-out of targeted advertising third-party availability: samsung is making tizen tv os available to third-party tv makers samsung’s open ecosystem every dev knows about bixby marketplace, and in the past six months the size of the bixby developer community has doubled! to make it easier for developers to keep creating new experiences and to ensure consumers have more intuitive experiences, samsung announced enhanced capabilities in the bixby developer studio. get excited! bixby templates: create capsules using pre-existing forms – adam cheyer built one in seconds at sdc19’s keynote! enhanced bixby views: build capsules with a consistent design beyond just smartphones — the list includes tvs, tablets, smart watches, and refrigerators natural language: when users ask bixby for help related to a category — such as radio, news, or navigatio – bixby suggests a capsule to help them get what they need more quickly and easily, without having to call out the exact capsule name https://twitter.com/samsung_dev/status/1189235374641635328 and the ai/iot highlights weren’t just about bixby! samsung announced new capabilities for devs to build on and integrate existing devices with the smartthings platform. new rules api: a more automated smart home experiences that reflects individual daily routines across a broad range of smartthings devices smartthings device sdk beta program: goes live in early 2020 to enable more third-party manufacturers to create smartthings-compatible devices https://twitter.com/samsung_dev/status/1189239141323755526 2. best of galaxy store awards samsung celebrated app devs and designers at sdc19 today by announcing its best of galaxy store awards 2019 selections — an annual list of what we consider to be the best content available in the galaxy store. here’s the full list of winners! best theme designer (big brand) cogul planet best theme design echo visuals whimsical woods (premium animated aod) best indie theme designer x9 studio best theme brand collaboration cogul planet mlb themes best watch designer (big brand) matteo dini best watchface design summer vacation best indie watch designer vienna studios best watch app igear radio best app to relax with headspace best productivity app degoo best made for samsung app rosetta stone 1:1 english tutoring for samsung best social app tiktok best streaming app mixer best creative app concepts best indie app homeadvisor best travel app app in the air for samsung best use of galaxy store badge skillz best indie game two dots best multiplayer badland brawls best ar game harry potter wizards unite best choose your own adventure hollywood story best casual game candy crush friends saga best adventure game sonic forces best role playing game game of sultans best racing game asphalt 9: legends 3. key tech sessions from day 1 we took note of the most-attended tech sessions from day 1! check out what fellow devs were most excited to learn about. new era of data insights with samsung health: 166 people came to hear jack ahn share how to extract value from data and verifiable insights to close the loop in the end-to-end user health journey. attendees discovered how to build insightful services for their users with a data insight platform that encompasses blockchain and ml models on-device. iot 2.0: the next phase of smartthings: 150 people joined aloknath de, yan rodriguez, and yeshodhan kulkarni to learn more about the smartthings platform service, integrated devices, and future plans for the smartthings iot business. this session specifically related back to the keynote and explored improvements made to the smartthings platform to enable stronger business growth for partners and developers, and highlighted ways new partners can join the smartthings ecosystem. progressive web apps and the evolution of the web: 129 people wanted to learn more about building and distributing apps using web technologies with luis gonzalez-zuniga, dongwoo im, laura morinigo, and jeff burtoft. progressive web apps (pwa) leverages new capabilities that allow for better integration of your app into the os. the in-depth session dove into new features and tools and how pwas can take advantage of webapk, oneui css, and more. 4. devs + drinks after an exciting first day, attendees connected with fellow devs and industry pros at our spook-tacular evening event with cocktails, halloween-themed bites, and music. the "day of the dev" themed night was complete with music, psychic readings, spooky art activities, and more. so, in the spirit of devs + drinks, cheers to day 2! check in tomorrow for our day 2 update and the spotlight session livestream, but in the meantime, follow along with #sdc19 on social media for all the latest updates.
Samsung Developer Program
tutorials mobile, health, game, blockchain, galaxy watch, foldable, iot
blogif you are looking for an opportunity to boost your skills and learn how to use samsung sdks and tools through various hands-on learning experiences, code lab is the right place for you. code lab is a learning platform where you can get started with the latest technologies and services in samsung. through its series of tutorials, it introduces you to the use cases or scenarios for a specific technology. it engages anyone through the step-by-step process of building a sample application or adding a new feature to an existing one. with that, you can integrate your learnings from code lab into your individual or business needs. you can start, by trying out one topic or use case that interests you, and get to know how to easily use a service or tool. it covers topics related to mobile, ai, iot, health, game, security, blockchain, web, or wearables. new topics have been published in code lab for you to learn about samsung’s latest cutting-edge technologies, enabling you to use them to your advantage. with the advent of foldable smartphones, contents like camera web app on foldables, flex mode, app continuity, and multi-window will help you create or modify your applications to adapt seamlessly with different form factors. code lab also provides tutorials on designing your watch face and tracking exercises for the newly released galaxy watch4, operating on wear os powered by samsung. to enhance your hands-on learning experience with code lab, you can simply test sample applications in remote test lab even if you don’t have any physical galaxy devices. it’s a service that allows you to test your apps virtually and remotely, on thousands of samsung galaxy mobile and watch devices. flagship devices are widely available like the galaxy s21 series and the latest galaxy z fold3 and z flip3. not only can you learn with code lab, but you can also test anytime, anywhere. now, are you ready to start your learning journey? visit: https://developer.samsung.com/codelab
Christopher Marquez
Develop Mobile Samsung Automation
docsamsung automation studio get started - samsung automation studio beta the automation studio allows you to integrate samsung bixby, smartthings and 3rd party your apis connect it with samsung bixby and smartthings! you can start a free trial the 6th promotion will end when the free trial code we have prepared are exhausted samsung account a samsung account is your gateway to the world of samsung when you sign up for a samsung account, you gain access to apps and services of samsung smartthings support samsung automation studio supports smartthings integration via smartthings node customization bixby voice support bixby voice can execute your flow that designed with "capsule label" node and "capsule result" node securely stored manage and store your flows simply export and import all files are encrypted and securely stored, protect in what matters pre-defined flows start with pre-defined flow templates for a mashing-up various cases get inspiration and create your new flow runtime environment deploy your flows in secured and isolated containers whose healths and lifecycles are managed automatically by the reliable container platform cf bixby capsule support you can create a flow using the capsule label node and capsule result node you can run this flow using the capsule for automation studio we have already developed the capsule for automation studio it is listed on bixby marketplace remote-endpoint makes your business logic more flexible on bixby voice "capsule label" node allows you to call the remote-endpoint without developing a capsule use a remote-endpoint to your capsules? get a paradigm shift when using bixby and its platform for an advanced state of conversational ai and voice jump on the bixby train and be ready for the 500 million, bixby-enabled, samsung devices that ships yearly as these are enabled with remote-endpoints making it more to flexibly code on bixby capsules capsule node decide which name is called through bixby voice without developing a capsule learn more > smartthings support webhook endpoints in this context is a web services application it serves as an api endpoint on the internet, that receives incoming http post requests webhook endpoints must be an https url rapidly build a smartapp by connecting devices and smartthings services easily what is the automation? automation allows the user to control their smartthings ecosystem without any manual intervention an example of an automation is a webhook that uses the smartthings rest api to control and get status notifications from smartthings devices automation node connect easily with the smartthings smartapp using a web hook endpoint deviceprofile node know what capability you need? find the 71 capabilities of smartthings learn more > get started you can start a free trial the 6th promotion will end when the free trial code we have prepared are exhausted *[sign up][1] for a samsung account, if you do not already have one the minimum requirements are samsung account signed up to smartthings or bixby developers get the subscription code development service level get free trial > use our node on your server! you can find our node named "samsung-automation-studio" in node-red community and can install it in node-red you can keep your flows through the import/export npm install node-red-contrib-samsung-automation-studio-nodes self-managed servers limited features learn more > get started - samsung automation studio beta
We use cookies to improve your experience on our website and to show you relevant advertising. Manage you settings for our cookies below.
These cookies are essential as they enable you to move around the website. This category cannot be disabled.
These cookies collect information about how you use our website. for example which pages you visit most often. All information these cookies collect is used to improve how the website works.
These cookies allow our website to remember choices you make (such as your user name, language or the region your are in) and tailor the website to provide enhanced features and content for you.
These cookies gather information about your browser habits. They remember that you've visited our website and share this information with other organizations such as advertisers.
You have successfully updated your cookie preferences.