Tizen

Multi tool use
Tizen
|
Versão do sistema operativo Linux
|

|

|
Produção
|
Linux Foundation, Samsung, Intel, Tizen Community
|
Linguagem
|
HTML5, C++ (além de C e Java de aplicativos Android)
|
Lançamento
|
5 de janeiro de 2012 (7 anos)
|
Versão estável
|
2.2.1 / 9 de novembro de 2013; há 5 anos
|
Versão em teste
|
2.3 alpha / 31 de maio de 2014; há 5 anos
|
Arquitetura(s)
|
ARM, x86
|
Gestão de pacotes
|
RPM
|
Núcleo
|
Monolítico (Linux)
|
Interface
|
Gráfica
|
Licença
|
Apache, BSD, LGPL, Flora, Proprietária
|
Página oficial
|
https://www.tizen.org/
|
Tizen é um sistema operacional de código aberto baseado no Linux Kernel sendo desenvolvido pela Linux Foundation em parceria com a Samsung, Panasonic e Intel para funcionar em smartphones, tablets, smart TVs, netbooks, veículos e todos os outros tipos de sistemas embarcados.[1][2]
Para a criação de aplicativos, o Tizen facilita o desenvolvimentos de aplicações nativas, sem deixar de lado na flexibilidade do uso de HTML 5.[1] Suas APIs têm potencial para contemplar diversas plataformas, como exemplo, setores de comunicação, multimídia, câmera, rede e mídias sociais.
O Tizen está sendo utilizado atualmente em alguns aparelhos, como o Samsung Galaxy Gear 2 por exemplo.
Referências
↑ ab «Tizen, an open source, standards-based software platform for multiple device categories.» (em inglês)
↑ Carlos Morimoto (28 de setembro de 2011). «Tizen OS: O zumbi do Meego»
Ligações externas |
Sistemas operacionais móveis (português brasileiro) ou Sistemas operativos móveis (português europeu) |
| Linux |
| Android |
Baidu Yi · CyanogenMod · Fire OS · MIUI · OPhone · Replicant · Yandex.Kit · Plataforma Nokia X
|
| SHR |
OpenEmbedded (Familiar Linux · OpenZaurus · KaeilOS) · OpenMoko
|
| Outros |
Access Linux · webOS · Ubuntu Touch · EZX Linux · Nemo Mobile · Sailfish OS · Tizen
Descontinuados: Bada · DSLinux · Familiar · iPodLinux · Maemo · MeeGo · Mobilinux · MotoMagx · Ubuntu Touch · Firefox OS
|
|
| XNU |
iOS
|
| QNX |
BlackBerry 10 · BlackBerry PlayBook OS
|
| Windows |
Windows CE · Windows RT · Windows Phone · (Windows Phone 7 · Windows Phone 8 · Windows 10 Mobile) Descontinuados: Windows Mobile
|
Plataforma própria |
BlackBerry OS · GEOS · EPOC · Nintendo DSi · Nintendo 3DS · Nokia OS (S30 · S40 · Asha) · PSP · PS Vita · Symbian (MOAP(S) · UIQ · S60 · S80 · S90) Descontinuados: Palm OS · SavaJe
|
Plataformas relacionadas |
Brew · Java ME (FX Mobile) |
Aplicativos móveis · Open Handset Alliance · Open Mobile Alliance · Desenvolvimento de software móvel
|
 |
Este artigo relativo a GNU/Linux é um esboço. Você pode ajudar a Wikipédia expandindo-o.
|
1 E3t2 T2WBiLBn Wtv7AtdwizQiPremMCrc8,UAxCTGbc 2DevFvhQaNz8FSBRqL4efO BnrN3QHag Ql8eUeJTHx2F2,Y9ltuO10fpu
Popular posts from this blog
0
I found a lot of questions abount appendices and ToC. Many users want appendices to be grouped in an Appendix part, however some problems arise with ToC, hyperref, PDF viewer bookmarks, and so on. There are different solutions which require extra packages, command patching and other extra code, however none of them satisfies me. I almost found an easy way to accomplish a good result, where appendices are added to bookmarks in the right way and hyperref links point to the right page. However, the number of the "Appendix" part page is wrong (it's the number of appendix A). Is there any EASY way to fix that? This is a MWE: documentclass{book} usepackage[nottoc,notlot,notlof]{tocbibind} usepackage{hyperref} begin{document} frontmatter tableofcontents mainmatter part{First} chapter{...
2
I've read in different places that it is done for "performance reasons", but I still wonder what are the particular cases where performance get improved by this 16-byte alignment. Or, in any case, what were the reasons why this was chosen. edit : I'm thinking I wrote the question in a misleading way. I wasn't asking about why the processor does things faster with 16-byte aligned memory, this is explained everywhere in the docs. What I wanted to know instead, is how the enforced 16-byte alignment is better than just letting the programmers align the stack themselves when needed. I'm asking this because from my experience with assembly, the stack enforcement has two problems: it is only useful by less 1% percent of the code that is executed (so in the other 99% is actually overhead); and...
0
I'm working on an Android app where the user has to use a camera view to scan a barcode. I've been using Firebase's ML-Kit barcode scanning utility to achieve the actual barcode recognition bit and it's been fantastic. There's only one issue - if given a photo with multiple barcodes in it, it commonly misses at least one of the barcodes. That's problematic because a lot of the barcodes that my users have to scan are on boxes/containers with multiple barcodes. Here's an example Pixel 2 XL box that may need to be scanned: The IMEI barcode in this picture is never picked up by ML-Kit. However; if I crop out everything else and just send the IMEI barcode through ML-Kit picks it up fine. Is there anything I can do to help ML-Kit pick up on all of the barcodes?
...