Android News

It used to be that the thing Samsung's most loyal fans used to complain about a lot was software updates. One could cut the company some slack. It launches dozens of smartphones every year and not only do they require software support, but the dozens released in the previous years also do so as well. Providing software support for so many devices is certainly a challenge but it got to a point where users were really fed up with having to wait a very long time to get a firmware update. Samsung has really switched gears over the past couple of years and drastically reduced wait times for updates. It streamlined the product portfolio, start rolling out monthly updates even ahead of schedule and has even done a good job of providing considerable feature parity across its different lineups with One UI . The company has even started sending out updates for unlocked Galaxy device owners much faster in the United States. They were particularly made to wait far more than anyone else ju

Unless otherwise noted, changes described below apply to the newest Chrome beta channel release for Android, Chrome OS, Linux, macOS, and Windows. Learn more about the features listed here through the provided links or from the list on ChromeStatus.com . Chrome 84 is beta as of May 28, 2020. Web OTP API The Web OTP API (formerly called the SMS Receiver API) helps users enter an OTP on a web page when a specially-crafted SMS message is delivered to the user's Android phone. When verifying the ownership of a phone number, it is typically done by sending a one-time-password (OTP) over SMS which must be manually entered by the user (or copied and pasted). This manual user flow requires directing the user to the native SMS app and back to their web app with the code. With the Web OTP API, developers can help users enter the code with one tap. For more information, see Verify phone numbers on the web with the Web OTP API . Web Animations Animations on the web help users n

Notifications on the web help users receive important updates for a wide range of applications including messaging, calendars, email clients, ride sharing, social media and delivery services.  Unfortunately, browser notifications can be used to mislead users, phish for private information or promote malware. These abusive patterns fall into two broad categories, "permission request issues" and "notification issues."  Permission request issues are requests designed to mislead, trick, or force users into allowing notifications. One example of this is websites that require users to allow notifications in order to gain access to site content or that are preceded by misleading pre-prompts. Notification issues include fake messages that resemble chat messages, warnings, or system dialogs. They also include phishing attacks, an abusive tactic that tries to steal or trick users into sharing personal information, and malware notifications that promote or link to

In April , we temporarily rolled back the enforcement of SameSite cookie labeling to ensure stability for websites providing essential services in the critical initial stage of COVID-19 response. We indicated plans to resume the rollout over the summer. Since April we have continued to monitor overall ecosystem readiness, and engage with websites and services to ensure they are prepared for the SameSite labeling policy. We are planning to resume our SameSite cookie enforcement coinciding with the stable release of Chrome 84 on July 14, with enforcement enabled for Chrome 80+. As with the previous rollout, the enforcement will be gradual and we will keep you informed on timing and any possible changes on the SameSite Updates page on Chromium.org. Our overall guidance for developers hasn't changed and you can find more information along with resources and channels to provide feedback in this previous Chromium post and on Web.dev . Posted by Justin Schuh - Director, Chro

After picking up a key certification in China earlier this week, the upcoming Galaxy Watch reappeared in the database of another regulatory agency, namely the FCC. The next-gen Galaxy Watch bearing model numbers SM-R845 and SM-R855 got listed at the FCC earlier today with some interesting specs in tow. The model numbers correspond to the LTE variants, whereas the Wi-Fi-only models – which haven't appeared at the FCC yet – should bear the model numbers SM-R840 and SM-R850 . 45mm, circular dial, solid construction These are the specs revealed by the FCC documents for the next-gen Galaxy Watch. The filings include a sketch of the smartwatch's backside, confirming a circular design with a 45mm stainless steel case (45mm for the larger variant), Gorilla Glass DX, 5ATM and MIL-STD-810G, as well as GPS and LTE connectivity. Keep in mind that even though the FCC sketch mentions a stainless steel construction, the Galaxy Watch should also be released in aluminum and titanium, as

Your Android developer newsletter ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍  Can't see this email? View in Browser . Developer Newsletter Announcing more Android development talks Join us for #Android11: The Beta Launch Show at 11 a.m. ET on June 3rd . We'll unveil new features packed inside Android 11, as well as exciting updates to help you get the most out of modern Android development. In addition to the show, we're dropping 12 binge-worthy talks on your favorite Android development topics. Oh my! Check out what's in store. View talk details Ask the experts with