Jump to content

Sign in to follow this  

Samsung Z1 Tizen OS Phone Review

Recommended Posts

Join the conversation

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

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

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

×   Your previous content has been restored.   Clear editor

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

Sign in to follow this  

  • Similar Topics

    • By STF News
      An updated version of the Samsung Blockchain Keystore SDK has been released. New features in v1.3.0 include:
      Added APIs to support Stellar transactions Added APIs to support Sign Personal Message in Tron transactions View the full blog at its source
    • By STF News
      Continuing our overview of Tizen .NET development, today we will go through the basics of installing the Tizen extension for Visual Studio on a Mac computer.
      Traditionally, you would develop Xamarin and .NET applications on a Windows machine. Now, cross platform developers can take advantage of the provided tools to create Tizen applications on MacOS.
      The Tizen Tidbits video series covers core concepts of Tizen app development in ten minutes or less.
      Stay tuned for more .NET development for the Samsung Galaxy Watch, and don’t forget to visit our developer portal to learn more about this and other topics.
      View the full blog at its source
    • By STF News
      You may have encountered the following error when launching a .NET application on your Tizen device, although the DLL file specified by the error message is already included in the application package (.tpk).
      Note: You can view the log from the Tizen Log Viewer window or dlogutil.
      Unhandled exception. System.IO.FileNotFoundException: Could not load file or assembly 'System.Collections.Immutable, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified. File name: 'System.Collections.Immutable, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' at TizenAppTemplate.App.OnCreate() at Tizen.Applications.CoreBackend.UICoreBackend.OnCreateNative(IntPtr data) at Tizen.Applications.CoreBackend.UICoreBackend.Run(String[] args) at Tizen.Applications.CoreApplication.Run(String[] args) at Tizen.Applications.CoreUIApplication.Run(String[] args) at TizenAppTemplate.App.Main(String[] args) onSigabrt called tpkroot └── bin ├── System.Collections.Immutable.dll ├── System.Runtime.CompilerServices.Unsafe.dll └── TizenAppTemplate.dll This error appears when the following conditions are met.
      The application package contains one or more system DLLs (System.* or Tizen.*) The DLLs are newer than DLLs installed in the device image This usually happens when you reference a system package from your application. The following example shows an application project file (.csproj) that contains such a dependency.
      <PropertyGroup> <OutputType>Exe</OutputType> <TargetFramework>tizen50</TargetFramework> </PropertyGroup> <ItemGroup> <PackageReference Include="System.Collections.Immutable" Version="1.7.0" /> </ItemGroup> In some cases, the file doesn't reference the system package directly. However, it may have such a dependency recursively in its dependency graph.
      <ItemGroup> <!-- This library is dependent on System.Collections.Immutable 1.7.0. --> <PackageReference Include="SomeLibrary" Version="1.0.0" /> </ItemGroup> Why do I see this error?
      As the error message implies, the error results from an AssemblyVersion mismatch. Your application expects a newer version of system DLL than the device has.
      Note: AssemblyVersion, AssemblyFileVersion, and NuGet PackageVersion are all different properties. For example, the NuGet package System.Collections.Immutable 1.7.0 comes with System.Collections.Immutable.dll of version (AssemblyVersion). Only AssemblyVersion is used by the runtime to verify DLL dependencies.
      ### Application-owned DLL $ sdb pull /opt/usr/globalapps/org.tizen.example.TizenAppTemplate/bin/System.Collections.Immutable.dll $ dotnet-ildasm System.Collections.Immutable.dll | grep '\.ver' | tail -n 1 .ver 1:2:0:5 ### Pre-installed DLL $ sdb pull /usr/share/dotnet.tizen/netcoreapp/System.Collections.Immutable.dll $ dotnet-ildasm System.Collections.Immutable.dll | grep '\.ver' | tail -n 1 .ver 1:2:0:4 The current implementation of the application launcher in Tizen (which hosts the .NET runtime) always prioritizes DLLs found in the system image and disregards application-owned DLLs, even though they are newer. It also ignores any properties defined in the application's .deps.json file.
      In fact, this restriction is intentionally added in Tizen for performance reasons. The launcher prefetches several runtime components commonly used by applications (for reduced startup time) by assuming a unified set of Trusted Platform Assemblies across all applications. Because of the fundamental design of CoreCLR, a DLL cannot be loaded into the default LoadContext if there exists a DLL with the same name in Trusted Platform Assemblies.
      For further details, you can read:
      Framework-dependent deployments (FDD) CoreCLR hosting APIs AssemblyLoadContext Class Tizen's launcher implementation Possible solutions
      Here are some solutions you can try:
      Remove or downgrade the package
      The first, most basic thing you can try is to eliminate the dependency itself. Check if the package is being used in the code and, if possible, reimplement the code without the package. You can otherwise downgrade the package from NuGets so that its DLL versions are compatible with all target devices. However, this is not always feasible if you cannot find a working version or you cannot control dependencies of libraries used by your application.
      <ItemGroup> <!--<PackageReference Include="System.Collections.Immutable" Version="1.7.0" />--> <PackageReference Include="System.Collections.Immutable" Version="1.6.0" /> </ItemGroup> Handle AssemblyResolve events
      Another workaround is to install a custom AssemblyResolve event handler inside your application. This handler is invoked when the runtime cannot find a DLL with a matching version. Note that if an application DLL has its native image, the native image is not automatically resolved by Assembly.LoadFile().
      static void Main(string[] args) { AppDomain.CurrentDomain.AssemblyResolve += (object s, ResolveEventArgs eventArgs) => { var appDir = Path.GetDirectoryName(typeof(App).Assembly.Location); var assemblyName = eventArgs.Name.Split(',')[0]; var assemblyPath = Path.Combine(appDir, assemblyName + ".dll"); return File.Exists(assemblyPath) ? Assembly.LoadFile(assemblyPath) : null; }; ... app.Run(args); } Use this API with care since it can cause some unexpected behaviors, such as a type identity problem (see Best Practices for Assembly Loading). Also, you cannot use Assembly.Load() (with a full assemblyRef) or Assembly.LoadFrom(), because they implicitly load an assembly into the default LoadContext.
      Unhandled exception. System.IO.FileLoadException: Could not load file or assembly 'System.Collections.Immutable, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. Could not find or load a specific file. (0x80131621) File name: 'System.Collections.Immutable, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' ---> System.IO.FileLoadException: Could not load file or assembly 'System.Collections.Immutable, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. at System.Runtime.Loader.AssemblyLoadContext.InternalLoadFromPath(String assemblyPath, String nativeImagePath) at System.Runtime.Loader.AssemblyLoadContext.LoadFromAssemblyPath(String assemblyPath) at System.Reflection.Assembly.LoadFrom(String assemblyFile) ... onSigabrt called Use custom AssemblyLoadContext
      For advanced scenarios, you can create your own AssemblyLoadContext in your application to isolate any specific DLLs. The following CustomAssemblyLoadContext class overrides Load() method to resolve DLLs explicitly from an application directory. See Understanding System.Runtime.Loader.AssemblyLoadContext for detailed information.
      // Inherit AssemblyLoadContext. private class CustomAssemblyLoadContext : AssemblyLoadContext { protected override Assembly Load(AssemblyName assemblyName) { var appDir = Path.GetDirectoryName(typeof(App).Assembly.Location); var assemblyPath = Path.Combine(appDir, assemblyName.Name + ".dll"); return File.Exists(assemblyPath) ? LoadFromAssemblyPath(assemblyPath) : null; } } // In application code, var alc = new CustomAssemblyLoadContext(); var assembly = alc.LoadFromAssemblyName(new AssemblyName("SomeLibrary")); assembly.GetType("SomeLibrary.SomeClass").GetMethod("SomeMethod").Invoke(null, null); The sample code shown above may not work if the prefer_dotnet_aot manifest property is enabled in tizen-manifest.xml file, because application DLLs can have their native images in either bin or bin/.native_image. In such cases, consider using ApplicationInfo.ExecutablePath in TizenFX API instead of Assembly.Location.
      If you need help, please contact me at [email protected]
      View the full blog at its source
    • By STF News
      So far this video series has focused on development of web apps with Tizen. Today we are going to cover the latest addition to the Tizen family: Tizen .NET. This option is perfect for developers that have previous experience with the Microsoft stack, or simply want to get ahead learning more of cross platform development with Xamarin.
      The Tizen Tidbits video series covers in ten minutes, or less, core concepts of Tizen app development.
      In upcoming videos, we will cover web and .NET app development for the Samsung Galaxy Watch, and will start creating small samples and modifying existing projects.
      View the full blog at its source
    • By STF News
      NOTE: This article was updated on 7 February 2020
      If you are interested in designing and selling UI themes for Samsung mobile devices, you must first pass a design evaluation. The design evaluation is where a team at Samsung reviews a design mockup that you create: the screens of your UI theme concept. We call this your “Themes Studio Portfolio Submission”.
      Show us what the different screens and app icons look like, and if we like your skills, we’ll give you access to Themes Studio, our free software for building UI themes for Samsung Galaxy mobile devices. Your themes can then be sold globally on the Galaxy Store.
      Designing The Mockup, Your Themes Studio Portfolio
      Using your favorite design program, create a mockup of a Samsung UI theme. The mockup must include the 6 required screens: Lock, Home, Messages, Dialer, Contacts, and Settings. If any of the 6 screens are not included in your Themes Studio Portfolio, your application will be rejected.

      In addition to the 6 screens, your mockup must include re-designs of the 8 app icons. Do not use the default Samsung app icons. Doing so will cause your application to be rejected.

      Download Our Starter Kit
      To help ensure that your submission meets the requirements, download our Starter Kit to assist with designing the required 6 screens. The starter kit includes a Photoshop template that utilizes “Smart” objects and the Generate Image Assets feature.
      For designers not using Photoshop, we have included an example PDF showing the required 6 screens, app icons, and symbols, as well as a transparent PNG of a Samsung mobile device. Feel free to use any design program that you like, just make sure each screen design is 1440 pixels wide by 3040 pixels tall.

      Theme Portfolio Design Tips
      Be unique. There are a lot of themes available on the Galaxy Store, and the best way to stand out is to create something different. Don’t use copyrighted or stock images. We want to see your talents as a designer to create a custom design. If you use copyrighted or stock images, your portfolio will be rejected.
      Cohesive design. Make sure all of your 6 screens feel like the same theme. Adjust and revise your artwork for each screen, but make sure they match the overall design concept.
      Nice colors. Design your theme within a specific color palette. This will ensure that your theme conveys a specific mood. For help with selecting a color palette, search online for websites that have color palette generating tools, such as color.adobe.com/create
      Careful with fonts. Fonts can be fun, but fonts can also be too crazy. You can use a stylistic font, just choose one that people can actually read, and read quickly.
      Simple App Icons. The symbols you design for each app icon should have a clear meaning. Do not place a distracting background behind each app icon. All design elements within the app icon should relate to that specific icon. Refrain from using a common design element across all app icons.
      Take a Break. When you are done with your theme mockup, step away for a moment. Do something that takes your mind off of your designs. When you return, you will look at your designs as a whole and not see the specific elements of your theme. Is it cohesive? Do all of the screens within your theme go together? Are the apps and fonts easy to read? Have you designed something unique? If you are confident that your theme mockup is strong, excellent! Time to submit!
      Looking For Inspiration?
      View the Samsung Galaxy Themes Magazine to see the latest designs from top sellers and interviews from top designers. Get inspired by the best of the best.

      Submitting Your Application and Themes Portfolio
      To apply to become a themes designer, visit developer.samsung.com/galaxy-themes and click the “GET STARTED” button. This will open the Themes Overview page. If the window is open, the “GET ACCESS” button will be displayed for you to apply and submit your themes portfolio. See below for the open window dates.
      To submit your themes portfolio, compress the 6 UI screens of your theme design as a ZIP file, and upload with your application.
      Submit More Than One Themes Portfolio?
      Sure. In fact, this is encouraged. Keep in mind though that you will be judged on all of your theme designs. If you submit one strong design and one weak design, they will be judged together. Remember, you are being judged as a Themes designer so be sure that all of your theme portfolios are equally strong.
      Cover Letter
      Submitting a cover letter with your application is not required, but it definitely helps. We would love to learn more about you as a designer. Tell us why you want to design Samsung Themes and sell them to the world. Tell us something interesting about yourself. Share links to other design projects or portfolios. Samsung is looking for great designers to sell their themes on the Galaxy Store. Don't say you only want to learn the software or just create themes for yourself.
      When Can You Submit Your Themes Portfolio?
      Because this is an exclusive group of designers, your portfolio can only be submitted during certain times of the year. We call this the “open window”. For two weeks every other month, Samsung opens the window for applying to become a themes designer. Along with your application you will include the 6 UI screens of your themes portfolio.
      2020 Submission Open Window Dates:
      February 19 - March 4 April 15- April 29 June 17 - July 1 August 19 - September 2 October 21 - November 4 December 16 - December 30 The Review Process
      After the submission window has closed, a team at Samsung will take approximately 4-5 weeks to review all applications and portfolios.
      If your application has been accepted, you will receive an email with instructions on how to access the Themes Studio software and further information about how to begin publishing your theme designs to the Galaxy Store.
      Rejection & Resubmitting
      If your application was rejected, you will receive an email with a link to modify your application and upload a new themes portfolio. Take some time to address the potential reasons as to why your original theme might have been rejected.
      Top reasons for rejection:
      Did not submit the required 6 screens Did not re-design all app icons Graphics were not high-res Theme portfolio was not cohesive Theme design was not well executed Another cause for rejection is the use of imagery that you did not design yourself. It is not allowed to use copyrighted, stock imagery or pictures you find on the internet. Your theme design must contain only custom artwork that you created yourself.
      Start Designing!
      Samsung is looking for designers that are ready and excited to sell their UI theme designs to the world. Take advantage of this unique opportunity and submit your Themes Portfolio during the next open window!
      View the full blog at its source
  • Similar Tagged Content

    • By Alex
      Three weeks ago, the company released in India the Samsung Z1, its first smartphone powered by Tizen, a homegrown alternative to Google Inc.’s Android operating system.
      This week, Samsung is pushing the Samsung Z1 into Bangladesh, a neighbor of India with more than 150 million people and a similarly low rate of smartphone penetration.
      After several missteps and rethinks, Samsung’s strategy for its Tizen smartphones is taking a clear shape: the company is aiming the fledgling platform squarely at first-time smartphone users, many of whom may not even have a bank account. The Samsung Z1 is selling in India for about $90.
      To that end, Samsung has been touting the “lightweight” nature of the Tizen operating system, meaning that it requires relatively little computing power and can handle most tasks without requiring pricey high-end specifications.
      That same lightweight approach has also allowed Samsung to use Tizen as the platform for many of the devices it is hoping will populate its “connected home,” from televisions to smart watches and home appliances.
      Despite concerns that Samsung’s new smartphone would face stiff competition in India, where several local handset makers are touting low-end smartphones — some of them in partnership with Google — Samsung says that its Tizen smartphones have received “positive responses” there.
      Positive enough, it seems, to at least push Tizen into a second country.
      Source: http://blogs.wsj.com/digits/2015/02/06/samsung-extends-tizen-smartphone-to-bangladesh/
    • By Alex
      Samsung to make the Tizen Z1 in India, but can the phone compete with rivals?
      The Samsung Tizen-OS phone, the Z1, may seem like just another phone launch amongst dozens that take place every month in India, the hottest smartphone market in the world, where a little under 70 percent of the population still operate "dumb" feature phones.
      But it's not. It has a multitude of narratives wrapped into it, the most important being Samsung's future in the country. The latest news that extends this conversation is the company's announcement yesterday that the Z1 will soon be manufactured in India.
      Source: http://www.zdnet.com/article/samsung-to-make-the-tizen-z1-in-india-but-phone-faces/
    • By Alex
      Samsung's first Tizen phone the Z1 is finally here and being sold in India for roughly $92.
      Samsung Electronics started selling its first Tizen smartphone in India on Wednesday, priced at 5,700 Indian rupees ($92).
      The Z1 runs the open-source Tizen operating system backed by Samsung and other vendors including Intel, and which already powers some of the South Korean company’s wearables and TVs.
      Samsung announced a different Tizen smartphone, the Z, in June, ahead of the Tizen Developer Conference in San Francisco. It said then that it would launch it first in Russia, in the third quarter of 2014, but that phone never appeared. According to some accounts, the release of a Tizen phone in India was also delayed.
      The Z1 has relatively low-end specs compared to the planned Z, which was to have a 4.8-inch HD Super AMOLED display and a 2.3 GHz quad-core application processor, indicating that Samsung has shifted its focus with Tizen to the low end of the market, a booming segment in India and other emerging markets.
      In India, the Z1 will have to compete with Android phones with similar hardware capabilities and similar prices, said Vishal Tripathi, principal research analyst at Gartner. Tizen phones may take time to take off because people are not familiar with the operating system, he added.
      The Z1 runs Tizen 2.3 and has a 4-inch, 480x800 pixel screen and a 1.2GHz dual-core processor. It has 768MB of RAM and 4GB of internal storage, expandable by up to 64GB with a microSD card. Samsung claims the 1500mAh battery will play video for 7 hours or provide 8 hours of talk time.
      Available in white, black and wine red, the smartphone has a 3.1 megapixel rear camera and a VGA front camera with face detection software.
      A key focus of the device seems to be entertainment. Samsung has bundled the phone with three months’ free access to movies and songs from Indian digital entertainment websites. The company is also providing users free access to premium content on its own Club Samsung digital entertainment storefront, and has tied with local mobile service providers Reliance Communications and Aircel to provide 500MB of free 3G data services per month for six months.

      Source: http://www.pcworld.com/article/2868792/samsungs-first-tizen-phone-arrives-in-india-at-92.html

  • Create New...