Quantcast
Jump to content

tizen os


krishan
 Share

Recommended Posts

Worst software fb donot run images donot open on fb msgs get to users when we open whatsapp application only....

Had complaint so many times but no response fed up with this phone.

App dont run like fb share it mx player have to uninstall them and again run repeat in 2 or 5 days uninstall reinstall fed up.....i want my money back

Link to comment
Share on other sites



  • Replies 0
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

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

×   Your previous content has been restored.   Clear editor

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

Loading...
 Share

  • Similar Topics

    • By STF News
      The web doesn’t have a marketing team. It doesn’t have a single developer program you can sign up to. And it doesn’t have a manual. That’s by design. Like the Internet, the web isn’t controlled by any single entity. But this decentralisation can also be a pain for web developers and designers.
      The web has lots of documentation, but it’s often an issue for developers to find documentation that is not written from a perspective of one web product — for example, a browser or a framework. The web needs a place where people can go to get the ground truth.
      Over the last decade, MDN has become that trusted source of information — a place where developers know they can get the documentation they need about how to build for the web. That’s because, even though it’s a project run by Mozilla, it documents the web across all browsers. Cross-browser compatibility is one of the key pain points of web development, and good documentation is one of the ways we can mitigate that pain. Ask any developer where they go first for documentation and they will likely cite MDN.
      That’s why, in 2017, I jumped at the chance of joining the Product Advisory Board of MDN. I saw it as an opportunity to give back, and also to be a part of a project to reinforce this cross-browser message. By the way, I started my career as a technical writer, so I have opinions on the importance of good technical writing when it comes to the developer experience. The product advisory board was an experiment from MDN to bring in an external advisory group — including members from Microsoft, Google and W3C. These organisations were all already investing time in building and maintaining MDN. The PAB gave them a way to advise on product direction and hear about future planning.

      Open Web Docs

      Fast forward to 2020. Mozilla restructured and MDN took a hit. As a response, the same organisations (and people) who had come together to support MDN via the Product Advisory Board came together again, with others, to launch something called Open Web Docs. Open Web Docs is a new open source project, set up to help support and maintain documentation on the web — via MDN. In practice, this means that Open Web Docs will be paying writers to help write documentation and build the tools that are required to produce high-quality web documentation (for example, to maintain browser compatibility data), in collaboration with Mozilla. Open Web Docs will help to ensure the stability of MDN and will focus the activities of the multiple stakeholders in good web documentation. I’m proud to have been a part of the planning for this effort. I’m also glad that Samsung Internet will be investing our time and energy, both through our continued participation in the MDN Product Advisory Board and via Open Web Docs, in helping to document the web platform.
      A beautiful library at Trinity College, Dublin. Photo by Alex Block on Unsplash
      View the full blog at its source
    • By STF News
      Looking to show off your design chops? You can now submit your portfolio to Samsung and apply to become a Galaxy Watch face or Galaxy Themes seller. The submission window is open October 14 - October 27.
      Galaxy Watch
      Check out our latest how-to blog and read up on the new process for watch face design reviews. Then head over to the submission page and complete your application.
      Galaxy Themes
      Watch our video for an overview of the process and what you need to prepare. Then download the Themes Submission Starter Kit and let the creative juices flow. Once you've assembled everything, complete your application here.
      While you're working on your portolfio, listen to Tony show Diego how to use Galaxy Themes Studio. It will livestream on Thursday, October 15 at 10am PT and will be available on YouTube for replay.
      Submit Now
      The application process is very selective, and only the best of the best are selected. Think you have what it takes? We can't wait to find out.
      View the full blog at its source
    • By STF News
      Adaptive Scalable Texture Compression (ASTC) is an advanced lossy texture compression format, developed by Arm and AMD and released as royalty-free open standard by the Khronos Group. It supports a wide range of 2D and 3D color formats with a flexible choice of bitrates, enabling content creators to compress almost any texture asset, using a level of compression appropriate to their quality and performance requirements.
      ASTC is increasingly becoming the texture compression format of choice for mobile 3D applications using the OpenGL ES and Vulkan APIs. ASTC’s high compression ratios are a perfect match for the mobile market that values smaller download sizes and optimized memory usage to improve energy efficiency and battery life.

      ASTC 2D Color Formats and Bitrates
      astcenc 2.0
      The ‘astcenc’ ASTC compression tool was first developed by Arm while ASTC was progressing through the Khronos standardization process seven years ago. astcenc has become widely used as the de facto reference encoder for ASTC, as it leverages all format features, including the full set of available block sizes and color profiles, to deliver high-quality encoded textures that are possible when effectively using ASTC’s flexible capabilities.
      Today, Arm is delighted to announce astcenc 2.0! This is a major update which provides multiple significant improvements for middleware and content creators.
      Apache 2.0 Open Source License
      The original astcenc software was released under an Arm End User License Agreement. To make it easier for developers to use, adapt, and contribute to astcenc development, including integration of the compressor into application runtimes, Arm relicensed the astcenc 1.X source code on GitHub in January 2020 under the standard Apache 2.0 open source license.
      The new astcenc 2.0 source code is now also available on GitHub under Apache 2.0.
      Compression Performance
      astcenc 1.X emphasized high image quality over fast compression speed. Some developers have told Arm they would love to use astcenc for its superior image quality, but compression was too slow to use in their tooling pipelines. The importance of this was reflected in the recent ASTC developer survey organized by Khronos where developer responses rated compression speed above image quality in the list of factors that determine texture format choices.
      For version 2.0, Arm reviewed the heuristics and quality refinement passes used by the astcenc compressor—optimizing those that were adding value and removing those that simply didn’t justify their added runtime cost. In addition, hand-coded vectorized code was added to the most compute intensive sections of the codec, supporting SSE4.2 and AVX2 SIMD instruction sets.
      Overall, these optimizations have resulted in up to 3x faster compression times when using AVX2, while typically losing less than 0.1 dB PSNR in image quality. A very worthwhile tradeoff for most developers.

      astcenc 2.0 - Significantly Faster ASTC Encoding
      Command Line Improvements
      The tool now supports a clearer set of compression modes that directly map to ASTC format profiles exposed by the Khronos API support and API extensions.
      Textures compressed using the LDR compression modes (linear or sRGB) will be compatible with all hardware implementing OpenGL ES 3.2, the OpenGL ES KHR_texture_compression_astc_ldr extension, or the Vulkan ASTC optional feature.
      Textures compressed using the HDR compression mode will require hardware implementing an appropriate API extension, such as KHR_texture_compression_astc_hdr.
      In addition, astcenc 2.0 now supports commonly requested input and output file formats:
      Loading LDR images in BMP, JPEG, PNG, and TGA formats Loading HDR images in OpenEXR and Radiance HDR formats Loading compressed textures in the “.astc” file format provided by astcenc, and the DDS and KTX container formats Storing LDR images into BMP, PNG, and TGA formats Storing HDR images into OpenEXR and Radiance HDR formats Storing compressed texturesinto the “.astc” file format provided by astcenc, and the DDS or KTX container formats Core Codec Library
      Finally, the core codec is now separable from the command line front-end logic, enabling the astcenc compressor to be integrated directly into applications as a library.
      The core codec library interface API provides a programmatic mechanism to manage codec configuration, texture compression, and texture decompression. This API enables use of the core codec library to process data stored in memory buffers, leaving file management to the application. It supports parallel processing for compression of a single image with multiple threads or compressing multiple images in parallel.
      Using astcenc 2.0
      You can download astcenc 2.0 on GitHub today, with full source code and pre-built binaries available for Windows, macOS, and Linux hosts.
      For more information about using the tool, please refer to the project documentation:
      Getting started: learn about the high-level operation of the compressor. Format overview: learn about the ASTC data format and how the underlying encoding works. Efficient encoding: learn about using the command line to effectively compress textures, and the encoding and sampling needed to get functional equivalents to other texture formats that exist on the market today. Arm have also published an ASTC guide, which gives an overview of the format and some of the available tools, including astcenc .
      Arm ASTC Guide: an overview of ASTC and available ASTC tools. If you have any questions, feedback, or pull requests, please get in touch via the GitHub issue tracker or the Arm Mali developer community forums:
      https://github.com/ARM-software/astc-encoder https://community.arm.com/graphics/ Khronos® and Vulkan® are registered trademarks, and ANARI™, WebGL™, glTF™, NNEF™, OpenVX™, SPIR™, SPIR-V™, SYCL™, OpenVG™ and 3D Commerce™ are trademarks of The Khronos Group Inc. OpenXR™ is a trademark owned by The Khronos Group Inc. and is registered as a trademark in China, the European Union, Japan and the United Kingdom. OpenCL™ is a trademark of Apple Inc. and OpenGL® is a registered trademark and the OpenGL ES™ and OpenGL SC™ logos are trademarks of Hewlett Packard Enterprise used under license by Khronos. All other product names, trademarks, and/or company names are used solely for identification and belong to their respective owners.
      View the full blog at its source
  • Similar Tagged Content






×
×
  • Create New...