Slashdot Mirror

Four Samsung Galaxy Fold review units in the hands of major US tech journalists all experienced device-breaking display failures today. AndroidPolice: Steve Kovach of CNBC, Mark Gurman of Bloomberg, and Dieter Bohn of The Verge have reported major failures of their phones' display panels, just two days after receiving them. To say this is a disaster for Samsung is probably underselling it. Well-known YouTuber MKBHD claims to be having similar problems, but hasn't posted any images. Bohn and Kovach claim their displays failed without removing the panel's protective film (Samsung says not to take it off), but both Gurman and Brownlee did. The company has yet to begin shipping the device to consumers. So far it has only handed the phone to select journalists, most of whom reported issue with it today.

Google and Huawei have preliminarily agreed to settle a class action lawsuit from Nexus 6P users who say their devices experienced a bootlooping issue that caused the phones to shut down randomly, regardless of the battery level. Pending court approval, the companies would be liable to a $9.75 million settlement for the class action that began in April 2017, which may result in payments of up to $400 for participating plaintiffs. The Verge reports: The lawsuit alleged that Google, which contracted the design and manufacturing of its early Android smartphones to third-party companies, and Huawei, one of the chosen companies, breached the device warranty since the companies were aware of the issue, but did not respond to the bug. The plaintiffs also said the companies continued selling the faulty devices while failing to acknowledge the issue. If the court approves the settlement at the next hearing on May 9th, Nexus 6P users in the U.S. who purchased the device on or after September 25th, 2015 would be eligible to claim reimbursement.

The proposal currently states that those who are eligible for the settlement could be paid up to $400 for their faulty device, while those who received a Pixel XL in a prior warranty exchange program would only be eligible for up to $10. Those who submit proper documentation for the bug will receive the most settlement money, while those without may be eligible for up to $75. For full details on submitting a claim, check out the as-filed longform notice document, which explains the process that will go into effect following court approval.

An anonymous reader shares a report: Qualcomm has been building laptop processors for a while now, designed for always-on Windows 10 ultraportables. Now that an ARM version of Windows 10 is widely available and works with Snapdragon processors, the gates have opened for porting the operating system to smartphones. @NTAuthority on Twitter already demoed Windows 10 on a Pixel 3 XL, but now they have ported it to the OnePlus 6T. In a series of tweets and replies, NTAuthority showed off the touchscreen working, with many applications (including Google Chrome) fully functional. The most impressive demo was Call of Duty: Modern Warfare 2 running on the phone, using Windows' built-in x86 emulation compatibility layer.

A total of 14 HTC apps have been removed from the Play Store in the last three months. "Looking at the latest HTC Corporation activity in App Brain, we can see that the Sense Home launcher and contacts app People were unpublished just this month," reports Android Police. "12 more apps, including Calendar, Dot View, and Speak suffered a similar fate in February, while the Mail app that went and then returned is once again conspicuous by its absence." From the report: A few of the unpublished apps hadn't been updated in months, so it's likely they simply weren't being used or supported any longer and therefore had no reason to still be on the Play Store. However, apps like Mail, Contacts, and People are supposedly key alternative apps that come preinstalled on HTC devices, so it's a little strange to see those removed.

It's not clear exactly why this is happening, but there are a few possible reasons. HTC's smartphone business hasn't been doing all that well in recent years, and supporting a bunch of apps that few people are using doesn't make much sense. That said, there are still plenty more apps from the Taiwanese company still live on the Play Store. Perhaps the new phones HTC plans to launch in 2019 will ship with Android One, thus eliminating the need for its own stock apps altogether.

A total of 14 HTC apps have been removed from the Play Store in the last three months. "Looking at the latest HTC Corporation activity in App Brain, we can see that the Sense Home launcher and contacts app People were unpublished just this month," reports Android Police. "12 more apps, including Calendar, Dot View, and Speak suffered a similar fate in February, while the Mail app that went and then returned is once again conspicuous by its absence." From the report: A few of the unpublished apps hadn't been updated in months, so it's likely they simply weren't being used or supported any longer and therefore had no reason to still be on the Play Store. However, apps like Mail, Contacts, and People are supposedly key alternative apps that come preinstalled on HTC devices, so it's a little strange to see those removed.

It's not clear exactly why this is happening, but there are a few possible reasons. HTC's smartphone business hasn't been doing all that well in recent years, and supporting a bunch of apps that few people are using doesn't make much sense. That said, there are still plenty more apps from the Taiwanese company still live on the Play Store. Perhaps the new phones HTC plans to launch in 2019 will ship with Android One, thus eliminating the need for its own stock apps altogether.

mfilion shares a report from Android Police: A new "experimental containerized Android environment" from a company called Collabora allows Android apps to run in floating windows alongside native applications on desktop Linux. You can read all the technical details at the source link, but put simply, 'SPURV' creates a virtual Android device on your Linux computer, much like Bluestacks and other similar tools. There are various components of SPURV that allow the Android environment to play audio, connect to networks, and display hardware-accelerated graphics through the underlying Linux system.

The most interesting part is 'SPURV HWComposer,' which renders Android applications in windows, alongside the windows from native Linux applications. This is what sets SPURV apart from (most) other methods of running Android on a computer. For this to work, the Linux desktop has to be using the Wayland display server (some Linux-based OSes use X11). Pre-built binaries for SPURV are not currently available -- you have to build it yourself from the source code. Still, it's an interesting proof-of-concept, and hopefully someone turns it into a full-featured product.

Two variants of the Pixel Slate, a tablet-laptop hybrid that Google unveiled last year, have been "out of stock" for months now, leading many to believe that Google may have quietly gotten rid of them. From a report: [The Pixel Slate that are powered by the Celeron processor] are nowhere to be seen. They've been out of stock on the Google Store -- the only place these models were very briefly available -- since shortly after launch, four months ago. The $599 and $699 versions of the Pixel Slate brought sub-iPad Pro pricing to Google's prosumer tablet, even if it turned out that the tablet itself beat the iPad in pretty much no sense that mattered. Marques Brownlee, typically known for his easy-going takes and willingness to embrace misunderstood tech products, basically called the cheaper Celeron Slate a turd. This was not a good look for Google. Shortly after that, the Celeron Pixel Slate showed up as sold out on the Google Store, and that status hasn't changed since.

Bolstering privacy is one of the primary focuses for Google in Android Q, the latest version of its mobile operating system, and that may spell trouble for some of your favorite apps. From a report: In Android Q, Google has restricted access to clipboard data as previously rumored, which means most apps that currently aim to manage that data won't work anymore. Having an app that sits in the background and collects clipboard data can be a handy way to recall past snippets of data. However, that same mechanism could be used for malicious intent. Google's playing it safe by restricting access to clipboard data to input method editors (you might know those as keyboards). Foreground apps that have focus will also be able to access the clipboard, but background apps won't.

With Google+ being shutdown in just a few weeks, the official Android Beta community announced that it will be leaving the dying social media site in exchange for Reddit. The group on Google+ was home to over 163,000 members. Android Police reports: The community's new home will be r/android_beta. In an official announcement, the Android Beta team says they'll keep a close eye on the subreddit for feedback and will use it for announcements and updates. There's nothing there just yet, but when the Android Q beta hits, we're sure things will get much busier. For now, just make sure you subscribe and keep in mind that you have a second address where you can send all your Q beta complaints -- the first is obviously our tips inbox.

Chinese smartphone maker Meizu generated some headlines in January after it unveiled Zero, a $1300 smartphone that doesn't have a headphone jack, or a charging port, or a physical SIM card slot, or any buttons, or a speaker grill. The company said it would make the phone available to consumers via Indiegogo crowdfunding platform. Well, the market has spoken. AndroidPolice: Meizu set itself an eminently reasonably bar for the campaign, too, at $100,000. That may sound like a fair bit of cash, but Meizu would only have had to sell 77 phones in order to meet this goal. It managed just 29. It's unclear how many of those were Meizu employees, other than to say "not enough."

An anonymous reader shares a report: Samsung's mobile internet browser, if you ask its users, is pretty great. A lot of folks even say it's better than Chrome. That appreciation has manifested in the app hitting a very exclusive Play Store milestone: Samsung Internet Browser now has more than one billion installs. That impressive figure puts the browser's install base ahead of those of Firefox and Opera combined. Now, there are a couple of caveats here: for one, Samsung's browser comes pre-loaded on Samsung devices, of which each activation counts as an "install." What's more, both Firefox's and Opera's Play Store listings report that each browser has "100,000,000+" installs, which, because of the somewhat silly way figures are reported on Android's app marketplace, means their combined installs total anywhere between 200 million and 999,999,998. Still, though, Samsung's browser is on more devices than the both of 'em.

According to new job listings (first spotted by Android Police), it looks like Google may start building its own wearable devices. "A job listing posted two days ago on the Google Careers site calls for a Vice President of Hardware Engineering for Wearables," reports Android Police. The description reads, "As the VP of Hardware Engineering for Wearables, you'll work collaboratively with the Senior Leadership team for Google Hardware and will be responsible for the design, development, and shipment of all Google's Wearable products. You will lead and enable the effectiveness of a large engineering organization primarily based in Mountain View to develop multiple next-generation wearable products simultaneously." From the report: Google's only current wearable product is the Pixel Buds, which hasn't been a runaway success. It seems extremely unlikely that the company would want a Vice President dedicated to producing earbuds, so it's safe to assume Google has plans for other wearable products, like fitness trackers and/or smartwatches. Another listing is for a "Wearables Design Manager," but the description is more vague. "As the Design Manager of the Wearables design team within the award-winning Google Hardware Design organization, you will be a critical leader and contributor to guide the efforts in defining and evolving what it means to hold 'Google in your hand.'"

An anonymous reader quotes a report from Android Police: Google announced its plans to sunset its Google+ social media network for consumers on a sour note in October. The platform, which has a small but dedicated user-base, decided to shut down following Google's acknowledgement of a data exposure that affected up to 500,000 Google+ profiles. Shortly after, in December, the shutdown timeline was expedited due to another, larger bug that had the potential to reveal private user information and impacted approximately 52.5 million users. Now, the company has detailed its shutdown timeline for the consumer version of Google+ -- and it's not wasting any time.

The shutdown timeline is as follows:
- As early as February 4th, you will no longer be able to create new Google+ profiles, pages, communities, or events.
- The Google+ feature for website comments will be removed by Blogger by February 4th and other sites by March 7th. All Google+ comments on all sites will be deleted starting April 2nd.
- Google+ sign-in buttons will stop working in the coming weeks, but in some cases will be replaced by a Google sign-in button.
- Google+ Community owners and moderators who are downloading data from their Community will gain additional data for download starting early March 2019. That includes author, body, and photos for every community post in a public community.
-On April 2nd, all Google+ accounts and pages will be shut down and Google will begin deleting content from consumer Google+ accounts. Photos and videos from Google+ in users' Album Archive and Google+ pages will also be deleted. Photos and videos backed up in Google Photos will not be deleted.

An anonymous reader shares a report: Google took a long, long break from Google Voice a while back. After letting the app fall into disrepair, Google expressed a renewed commitment to Voice in 2017. It has since announced a handful of feature updates, including VoIP calling in 2018. However, that feature never actually rolled out to everyone. Google's Scott Johnston says it's almost time, though. We know that some Voice users got VoIP calling as far back as September. Like far too many Google features lately, this is a server-side change and not controlled by an app update. For some unknown reason, Google has dragged its feet rolling it out to everyone. According to Johnston, things are back on track and the VoIP calling feature will be live for all users by next week.If you're looking for another option besides Google Voice, check out alternatives.

Ryne Hager, writing for AndroidPolice: Late last year, Google decided it was time to crack down on apps requesting SMS and call log permissions. Ostensibly, exceptions would be granted for categories including backups and automation, but as of now, there are still gaps which cover legitimate use cases. While some popular apps like Tasker have successfully secured exemptions, others like Cerberus have not. Instead, they've decided to strip out those permissions or risk facing the wrath of Google's upcoming January 9th banhammer, killing associated functionality and disappointing millions of long-time users to adhere to the Play Store's new policy.

The Play Console support page for the applicable set of permissions notifies developers that they can submit what is effectively an application for an exemption, categories for which are listed on the same page. (And that list of exceptions has grown since the original announcement.) Nonetheless, a further set of prohibitions are also included in the form itself, which explicitly preclude support for phone security/device location apps like Cerberus.

Several reports indict that at least some of Sony's recent Android TVs are actively blocking Kodi, the open-source, cross-platform streaming and media player that allows you to access and play local, network, and remote content. Android Police reports: The official Kodi project Twitter account pointed out Sony's deficiency a couple of days ago, but reports on the Kodi forums of issues installing and running the app from the Play Store go even further back to last year. A handful of affected enthusiasts believe they have discovered the cause of the problem: Sony seems to be blocking the package ID for the app from being installed/run. Supporting this theory is the fact that recompiling the app from scratch with a different ID allows it to work.

An anonymous reader shares a report: Speaking to a source familiar with the company's plans, we've learned that Google intends to launch two new Pixel smartphones on Verizon in early spring 2019 -- the Pixel 3 and 3 XL "Lite." An exact announcement date and pricing are not yet known. A Pixel 3 Lite prototype was leaked on a Russian tech blog last month, fueling rampant speculation about where the phone would be sold and how it would be positioned in Google's larger smartphone lineup. Later, renders of the 3 Lite and a larger XL variant were released by OnLeaks. These "Lite" Pixels will be the first phones in the mid-range Google has released since the Nexus 5X, which launched at $379 in the US in 2015.

An anonymous reader shares a report: Google's been messing around with indoor maps for years; you can check the layout of many department stores and other large indoor spaces in Google Maps. Find My Device can show on those maps where your device is located. Here's the changelog for the latest version: "Support for indoor maps to help you find your device in airports, malls, or other large buildings. And, Support for work profiles."

Those of you who detest display notches will find this bug especially unpleasant. A small number of Pixel 3 XL users are reportedly experiencing a bug where an additional notch appears on the right side of the display. Android Police reports: Turns out that it's a real-life bug experienced by several users, including Jessie Burroughs, Kyle Gutschow, and UrAvgConsumer. We're not sure what's causing it, but it could be something to do with the screen rotation setting getting a bit confused about its orientation. In all three of the examples we've seen, the users reported that the issue went away after a restart or fiddling with the developer settings, so at least it's not a permanent problem. Anyone who bought a Pixel 3 XL probably decided that the notch didn't bother them that much, but we're not sure how they'd feel about another one showing up unannounced. Google is aware of this bug and says a fix is "coming soon."

An anonymous reader quotes a report from Ars Technica: Google's Pixel 3 smartphone is shipping out to the masses, and people hoping to take advantage of the new Qi wireless charging capabilities have run into a big surprise. For some unexplained reason, Google is locking out third-party Qi chargers from reaching the highest charging speeds on the Pixel 3. Third-party chargers are capped to a pokey 5W charging speed. If you want 10 watts of wireless charging, Google hopes you will invest in its outrageously priced Pixel Stand, which is $79.

Android Police reports that a reader purchased an Anker wireless charger for their Pixel 3, and, after noticing the slow charging speed, this person contacted the company. Anker confirmed that something screwy was going on with Google's charging support, saying "Pixel sets a limitation for third-party charging accessories and we are afraid that even our fast wireless charger can only provide 5W for these 2x devices." Normally we would chalk this up to some kind of bug, but apparently Google told Android Police that this was on purpose. The site doesn't have a direct quote, but it writes that, after reaching out to Google PR, it was "told that the Pixel 3 would charge at 10W on the Pixel Stand [and that] due to a 'secure handshake' being established that third-party chargers would indeed be limited to 5W." In an update, Google said the reason has to do with the "proprietary wireless charging technology" it has via its Pixel Stand and other select wireless chargers. The Pixel 3 only supports 5W Qi charging; "Google's 10W proprietary wireless charging technology" is what will allow the phone to charge at faster speeds.

"Google says it is 'certifying' chargers for the Pixel 3 via the 'Made for Google' program and pointed us to one such device, a Belkin charger called the 'Boost Up Wireless Charging Pad 10W for Pixel 3 and Pixel 3 XL,'" reports Ars Technica. "Belkin's description is very enlightening, saying 'Made with the Google Pixel 3 and Pixel 3 XL in mind, this wireless charging pad uses Google's 10W proprietary wireless charging technology. It's certified for Pixel, so you know that the BOOST UP Wireless Charging pad has been made specifically for your Pixel 3 and meets Google's high product standards.'"

Corbin Davenport, writing for AndroidPolice: For years, SuperSU was one of the most popular root applications for Android. Chainfire, the creator of SuperSU, handed over development to CCMT in 2015. He ended his involvement with the app last year, so CCMT has been in full control of it since then. For reasons currently unknown, SuperSU has now vanished from the Play Store. The app's Twitter and Google+ accounts for SuperSU haven't made a post since last year, the Facebook page has been inactive since March, and the official forum is currently offline. As such, it seems like the app was largely abandoned. The latest version available from APKMirror was published in January. Further reading: End of an era: Chainfire is halting development on all root-related apps.

Google is now selling an updated headphone adapter that's supposed to be more responsive and drain less of your phone's battery. But these minor improvements come at a cost. The new dongle costs $12, whereas the old dongle sold for just $9. "That also means Google's headphone adapter now costs more than Apple's equivalent adapter for the iPhone," The Verge notes. From the report: Physically, though, the dongle is nearly identical to the USB-C to 3.5mm adapter that Google has been selling since last October: this new version is just a hair smaller in almost every dimension. Google says the new dongle will connect to your phone ever so slightly faster, and, more importantly, it's supposed to draw less power, translating to 38 percent more playback time. Android Police first spotted the update.

AT&T has almost tripled the cost of the "Administrative Fee" featured in its wireless service bills. "Up until early this year, that 'fee' was typically assessed at $0.76 per postpaid line -- not nothing, but over the course of two years of service, it ends up being a little over $18," reports Android Police. From the report: Most recently, subscribers getting their statements for June are finding an Administrative Fee charge of $1.99 per line every month. That brings the two-year cost of this "administrative fee" to almost $50 for each line on your account. The fee was raised earlier this year incrementally in March (by $0.54), but this new hike comes just three months after the first one, and it's not even clear why.

AT&T is likely hoping subscribers just won't notice their per-line bill is going up $1.23 a month versus where it was a few months ago, and in the process, could net almost a billion dollars in additional revenue according to one analyst. This could allow AT&T to finance up to $10 billion in new debt to expand its ever-broadening media empire. The fee is being assessed against all postpaid subscribers, regardless of their service plan or any grandfathering. AT&T says the fee is related to its cost of doing business, in terms of interconnect fees with other operators and cell site rents.

An anonymous reader quotes a report from Ars Technica: Back in January 2017, Google and Uber teamed up to put a cool feature in Google Maps: You could search for, book, and pay for an Uber all directly from Google Maps. You didn't even need the Uber app installed. Now, 18 months later, the feature is dead. Google posted a new support page (first spotted by Android Police) that flatly states, "You can no longer book Uber rides directly in Google Maps."

The feature would have you search for a location in Google Maps and ask for directions like normal, but instead of choosing walking, driving, biking, or mass transit directions, a tab for ride-sharing would allow you to book a ride directly. The ride-sharing tab still exists, but instead of booking an Uber, it just gives you an estimate and offers to kick you out to the Uber app.

Google Lens is now available as an app in the Play Store for devices with Android Marshmallow and above. The app is designed to bring up relevant information using visual analysis. Android Police reports: When you open the app, it goes right into a live viewfinder with Lens looking for things it can ID. Like the Assistant version of Lens, you can tap on items to get more information (assuming Google can figure out what they are) and copy text from documents. However, I've noticed that copying text doesn't work on the OnePlus 6 right now. It works fine with the built-in Lens version. Some users are reporting that it's not working properly on some devices, so keep that mind if you decide to give it a whirl.

Google has quietly crept out of the tablet business, removing the "tablets" heading from its Android page. It was there yesterday, but it's gone today. TechCrunch reports: Google in particular has struggled to make Android a convincing alternative to iOS in the tablet realm, and with this move has clearly indicated its preference for the Chrome OS side of things, where it has inherited the questionable (but lucrative) legacy of netbooks. They've also been working on broadening Android compatibility with that OS. So it shouldn't come as much surprise that the company is bowing out.

Sales have dropped considerably, since few people see any reason to upgrade a device that was originally sold for its simplicity and ease of use, not its specs. Google's exit doesn't mean Android tablets are done for, of course. They'll still get made, primarily by Samsung, Amazon and a couple of others, and there will probably even be some nice ones. But if Google isn't selling them, it probably isn't prioritizing them as far as features and support. Android Police was first to break the news.

Currently, you can head to the "History and Privacy" settings in YouTube and toggle on the options to pause watch and search history if you don't want the site to track your searches and watched videos, but that can be a bit complicated each time you want to search for something weird. According to Android Police, "YouTube will make it a little easier to go into incognito without digging into many settings and without having to disable it later." A new "Incognito Mode" will appear when you tap your account avatar in the top right of the app. From the report: With "Incognito Mode" on, all your activity from the current session is not saved and subscriptions are hidden too. It's as if you were signed out without being so, and there's a neat incognito icon replacing your avatar. If you turn off Incognito or become inactive on YouTube, you'll be back to using your own account.

A new screenshot that Google recently shared (and since deleted) is stirring up theories about a possible iPhone X-like gesture navigation interface for Android P. Android Police reports: What we see is a decidedly odd navigation layout, with this short little bar in place of the expected home button, a back arrow that's now hollowed-out, and an app-switcher that seems utterly absent. So how would Google's presumably screen-only implementation work? Well, not only does that home bar look like a narrower version of the bar you'll find on the iPhone X, but we hear that the Android version may function in a quite similar way, with users swiping up to access their home screens. While we still haven't heard any details about how app switching might work with this new regime, the back button will reportedly only appear when needed, disappearing on the home screen, for example. As to other controls we can only speculate, like how you would gesture to conjure up the Google Assistant.

A new screenshot that Google recently shared (and since deleted) is stirring up theories about a possible iPhone X-like gesture navigation interface for Android P. Android Police reports: What we see is a decidedly odd navigation layout, with this short little bar in place of the expected home button, a back arrow that's now hollowed-out, and an app-switcher that seems utterly absent. So how would Google's presumably screen-only implementation work? Well, not only does that home bar look like a narrower version of the bar you'll find on the iPhone X, but we hear that the Android version may function in a quite similar way, with users swiping up to access their home screens. While we still haven't heard any details about how app switching might work with this new regime, the back button will reportedly only appear when needed, disappearing on the home screen, for example. As to other controls we can only speculate, like how you would gesture to conjure up the Google Assistant.

It might be a holiday for most of us today, but for tech companies, April Fool's is the day when they work overtime to send weird press releases. So far we have seen Google Maps help users find Waldo, and Google Australia rethink its brand name (to Googz). T-Mobile has revivedthe Sidekick as the world's first smart shoe phone. Google has also added a feature to its file manager app Files Go that detects bad jokes from your phone. Snapchat has finally found a way to make fun of Facebook. Languages learning app Duolingo has launched a range of craft beers. Chinese smartphone maker OnePlus has launched a cryptocurrency. Some more here. What's your favorite prank so far today?

Verizon is planning on launch a Palm-branded smartphone later this year, an anonymous source told Android Police. The rumor backs up what a TCL executive said last August, when they confirmed that the company would launch a Palm phone this year. From the report: Sadly, we don't know anything about the phone itself at this time (well, we know it runs Android), but the fact that TCL is working with Verizon is telling. The carrier was a longtime Palm partner, selling most of the brand's webOS handsets all the way through the Pre 2. Verizon had intended to carry the ill-fated Pre 3, but the phone was cancelled by Palm's then-buyer HP before it could be released in the U.S. TCL acquired the rights to the Palm name back in 2015, and it's starting to get something of a reputation for reviving dead and dying brands: the Chinese firm manufactures BlackBerry handsets, which have received a surprising amount of attention in the mainstream press.

Foxconn, the Taiwan-based company best-known for manufacturing Apple products announced that one of its subsidiaries (Foxconn Interconnect Technology) is purchasing U.S.-based Belkin for $866 million in cash. "Belkin owns a number of major brands, including Linksys and Wemo," notes Android Police. From the report: The buyout would make Foxconn a major player in consumer electronics, instead of just a contract manufacturing company. Belkin primarily sells phone/tablet accessories, but also manufactures networking equipment like routers and Wi-Fi range extenders. The company also sells a range of smart home products under the Wemo brand. According to The Financial Times, the purchase is subject to approval from the U.S. Committee on Foreign Investment. In other words, there is a very real chance the acquisition could be blocked. President Trump blocked Broadcom's acquisition of Qualcomm earlier this month, based on advice from the committee.

hyperclocker shares a report from Android Police: The touchscreen on your phone is the primary way you interact with it, so it absolutely needs to work. That makes problems like so-called "dead zones" or ignored/unregistered inputs among the most annoying out there. Based on reports, many are running into those types of touchscreen input problems with Samsung's Galaxy S9+. It's tough to tell precisely how common the problem might be. Few users are as apt to report issues as Pixel-purchasers, so we can't quite compare things against our coverage for Google's hardware. But from what we have seen in places like Reddit, it's reasonably widespread. The problem manifests as you'd expect: a chunk of the touchscreen's digitizer just doesn't seem to work. Interestingly, not all users are reporting issues with the same physical areas of the display. For some, it's the top of the screen that isn't accepting input -- resulting in an inability to pull down the notification tray -- but for others, it's the bottom of the screen that's wonking out in the traditional keyboard input area. A few people have been able to diminish the effect by cranking up the touchscreen sensitivity, and there's at least one report of a factory reset fixing things. But for many, the problem persists between wipes. Worse, some people with the problem have experienced further issues seeking help via Samsung's support process if a trade-in was involved. Samsung has released a statement concerning these reports: "At Samsung, customer satisfaction is core to our business and we aim to deliver the best possible experience. We are looking into a limited number of reports of Galaxy S9/S9+ touchscreen responsiveness issues. We are working with affected customers and investigating. We encourage any customer with questions to contact us directly at 1-800-SAMSUNG."

Firefox is working on a blocker for annoying in-page alerts that often ask you to input your email address to receive a newsletter from the site. "The feature is still in the planning stages, but Mozilla is asking users for any examples of sites with annoying pop-ups," reports Android Police. "Mozilla wants to make Firefox automatically detect and dismiss the popups." From the report: If you know of sites that use in-page popups (whether it be newsletter signups, surveys, or something else), you can fill out the survey here. There are also Firefox and Chrome extensions that make the process easier. I'll be interested to see how Mozilla pulls this off, it will no doubt be difficult to detect the difference between helpful and not-helpful popups.

On Friday, Lenovo confirmed layoffs for the Motorola group in Chicago, where the company designs its modular Moto Z smartphones. "In a statement to 9to5Google, Lenovo denied that it was axing 50% of the workforce, as the site had suggested, but didn't provide any further specifics," reports Fast Company. Android Police now reports that 190 people were laid off. A separate report of theirs claims that the company has "completely abandoned plans to launch the successor to last year's Moto X4, the as-yet unannounced Moto X5." Furthermore, "Motorola will be narrowing its focus back to E, G, and Z phones for the time being," reports Android Police. "It's possible the Moto X name could return at some point, but that's looking unlikely in light of this news." The source also says Motorola will be largely discontinuing its efforts to develop all-new, eccentric MotoMods for its Z phone. The likelihood that MotoMods will continue to be sold after 2019 is looking very slim.

On Friday, Lenovo confirmed layoffs for the Motorola group in Chicago, where the company designs its modular Moto Z smartphones. "In a statement to 9to5Google, Lenovo denied that it was axing 50% of the workforce, as the site had suggested, but didn't provide any further specifics," reports Fast Company. Android Police now reports that 190 people were laid off. A separate report of theirs claims that the company has "completely abandoned plans to launch the successor to last year's Moto X4, the as-yet unannounced Moto X5." Furthermore, "Motorola will be narrowing its focus back to E, G, and Z phones for the time being," reports Android Police. "It's possible the Moto X name could return at some point, but that's looking unlikely in light of this news." The source also says Motorola will be largely discontinuing its efforts to develop all-new, eccentric MotoMods for its Z phone. The likelihood that MotoMods will continue to be sold after 2019 is looking very slim.

Google has launched the first developer preview of Android P, the company's new mobile operating system that brings new features and improvements over Android Oreo. Unfortunately, developers will only have a small set of blessed hardware to choose from with Android P: the Pixel, Pixel XL, Pixel 2, and Pixel 2 XL. Google's Nexus smartphones and Pixel C tablet will not get Android P when it's fully released. The Verge reports: Eventually, Android P will ship on new phones from other manufacturers, along with the handful of handsets that third-parties bother to update, but there are a couple Android mainstays that won't get to enjoy this marvelous future: Google's Nexus 5X and Nexus 6P phones, and the oft-forgotten Pixel C tablet. As Ars Technica confirmed with Google, those devices won't be getting Android P when it's released fully. Also, as Android Police notes, there's no Developer Preview image for the Nexus Player, which came out in 2014, so it might be done getting updates as well. It's 2018, and we're beyond the two years of major OS update support these devices were promised, so this isn't hugely surprising. All three devices will continue to get monthly security updates through at least November of this year, but they'll remain stuck on Android 8.1 for an underlying OS as far as official Google updates go.

After being purchased by Fandango in 2016, Flixster Video is officially shutting down. The site has been sending users regular emails over the past several months about the shutdown, reports Android Police. Now, the site is no longer operational, and only points people to its mobile app, which can still be used for getting movie reviews and tickets. The Verge reports: Flixster first announced it was closing in 2016, after being acquired by Fandango along with subsidiary Rotten Tomatoes. That year, Fandango also bought video streaming service M-Go, later rebranding it under FandangoNow. Flixster Video, which let people access their UltraViolet movie collection, was not a part of that deal. The shutdown began with the service telling customers it would no longer be able to redeem digital codes on the site for video playback. Over the past few months, emails have been sent out encouraging people to migrate their Flixster accounts to Vudu and Movies Anywhere in order to make sure nothing was lost. The company says it's not too late for users to do so.

Android Police dug into the code for the latest version of Android Messages and found two very intriguing features: Rich Communication Services (RCS) support and support for all the popular web browsers. From the report: Google is developing a web interface to run on a desktop or laptop, and it will pair with your phone for sending messages. Internally, the codename for this feature is "Ditto," but it looks like it will be labeled "Messages for web" when it launches. You'll be guided to visit a website on the computer you want to pair with your phone, then simply scan a QR code. Once that's done, you'll be able to send and receive messages in the web interface and it will link with the phone to do the actual communication through your carrier. I can't say with any certainty that all mainstream browsers will be supported right away, but all of them are named, so most users should be covered.

Another major move appears to be happening with RCS, and it looks like Google may be tired of letting it progress slowly. A lot of new promotional text has been added to encourage people to "text over Wi-Fi" and suggesting that they "upgrade" immediately. There's a lot of text in that block, but most of it is purely promotional. It describes features that are already largely familiar as capabilities of RCS, including texting through a data connection, seeing messaging status (if somebody is typing) and read receipts, and sending photos. Google does put a lot of emphasis that if it's handling the photos, that they are high-quality. Android Police also notes the ability to make purchases via Messages.

Early last year, a class-action lawsuit was filed against LG over bootloop issues affecting their G4 and V10 smartphones. Now, according to a settlement website set up by the law firm Girard Gibbs, members of the lawsuit have received a settlement offer. The only catch is that the settlement is only for plaintiffs of the initial case. Android Police reports: LG is offering plaintiffs either $425 as a cash settlement or a $700 rebate toward the purchase of a new LG phone. That's pretty generous, and it's clear that's going to help offset some of the anger LG's created with this whole incident. If you're one of the plaintiffs, you don't have to mail in your broken phone or anything, you just get the settlement offer, straight up. Members of the class will be contacted shortly with instructions on how to take advantage of the settlement. Payments will be distributed beginning in March.

An anonymous reader quotes a report from ZDNet: Google on Wednesday said it will release an update Jan. 18 to fix a bug in Cast software on Android phones that dramatically slows down WiFi networks. Reports have been circulating this week that the Google Home Max speaker can knock the TP-Link Archer C7 router offline. In a support page, Google explains a bug caused the Cast software that connects with Chromecast devices to send a large amount of network traffic routers can't handle. Google said the update will roll out via a Google Play services update. Until the update is released, Google advises users to try rebooting their Android phone, and check that their WiFi router is updated with the latest firmware. Google didn't list specific routers impacted by the bug, but reports have indicated routers from Linksys and Synology are seeing network crashes as well.

If you purchased a OnePlus smartphone recently from the official OnePlus website, you might want to check your transactions to make sure there aren't any you don't recognize. "A poll was posted on the OnePlus forum on Thursday asking users if they had noticed fraudulent charges on their credit cards since purchasing items on the OnePlus site," reports Android Police. "More than 70 respondents confirmed that they had been affected, with the majority saying they had bought from the site within the past 2 months." From the report: A number of FAQs and answers follow, in which OnePlus confirms that only customers who made credit card payments are affected, not those who used PayPal. Apparently, card info isn't stored on the site but is instead sent directly to a "PCI-DSS-compliant payment processing partner" over an encrypted connection. [...] OnePlus goes on to say that intercepting information should be extremely difficult as the site is HTTPS encrypted, but that it is nevertheless carrying out a complete audit. In the meantime, affected customers are advised to contact their credit card companies immediately to get the payments canceled/reversed (called a chargeback). OnePlus will continue to investigate alongside its third-party service providers, and promises to update with its findings as soon as possible.

According to infosec firm Fidus, there is actually a brief window in which data could be intercepted. Between entering your card details into the form and hitting 'submit,' the details are apparently hosted on-site, which could give attackers all the time they need to steal those precious digits and head off on a spending spree. Fidus also notes that the company doesn't appear to be PCI-compliant, but that directly contradicts OnePlus' own statement. We'll have to wait until more details emerge before we pass judgment. Here's OnePlus' official statement on the matter: "At OnePlus, we take information privacy extremely seriously. Over the weekend, members of the OnePlus community reported cases of unknown credit card transactions occurring on their credit cards post purchase from oneplus.net. We immediately began to investigate as a matter of urgency, and will keep you updated. This FAQ document will be updated to address questions raised."

A few months ago, LG announced a partnership with NextRadio to unlock the FM chip in its smartphones. Now, Samsung is doing the same. Android Police reports: NextRadio made the announcement, rightly explaining that FM radio is essential in areas with low connectivity and in emergency and disaster situations where a connection might be difficult to obtain or maintain and where access to information could be a matter of life and death. With the chip unlocked, users will be able to listen to local radio on their phone using the NextRadio Android app. The press release mentions that "upcoming [Samsung] smartphone models in the U.S. and Canada" will have the FM chip unlocked, however I did find several existing Samsung devices with their FM chip enabled on NextRadio's site.

Google is no longer selling the Pixel C, its flagship Android tablet released about two years ago. "Google's commitment to Android on tablets wasn't strong even then, and now the Pixel C is gone from the Google Store -- the listing page redirects you to the Pixelbook," reports Android Police. From the report: The Pixel C was an odd device. By all accounts, the hardware was originally intended to run Chrome OS, but Google couldn't get the platform ready for an all-touch device in time. So, the Pixel C became an Android slate. Google has been selling the device continuously since late 2015. It even offered some discounts on the tablet via the Google Store, which it almost never does for other devices. The 32GB Pixel C was pulled a while back, but Google kept the 64GB variant around. At a whopping $599, I doubt many people were buying it. Now, the Pixel C is completely gone from the Google Store, and there's no new tablet to replace it.

The FCC recently announced a new alert program called "Blue Alert" that will notify the public of threats to law enforcement in real time. "With the creation of a dedicated Blue Alert event code in the Emergency Alert System, state and local law enforcement will have the capability to push immediate warnings out to the public via broadcast, cable, and satellite providers, as well as to consumer smartphones through the Wireless Emergency Alert system," reports Android Police. From the report: Much like both the SILVER and AMBER alert programs, and utilizing the same notification system, Blue Alerts aim to warn the general public of threats to public safety and/or imminent danger. However, the police force focused alert system provides timely information to the public when police officers may be in danger. Chairman of the FCC and recent deregulator of the internet, Ajit Pai detailed the new FCC order saying, "Similar to the Amber Alerts that many are familiar with, Blue Alerts will enable authorities to warn the public when there is actionable information related to a law enforcement officer who is missing, seriously injured or killed in the line of duty, or when there is an imminent credible threat to an officer."

The December 14 order from the FCC activates the Blue Alerts service for one calendar year to deliver the notifications over the Emergency Alert System, and for 18 months over the Wireless Emergency Alert system.

Google announced that it is ending support for Project Tango, the company's first attempt to bring a solid augmented-reality experience to the average user. The project used an array of cameras and sensors to accurately map 3D areas, causing the devices support Tango to be relatively large and expensive. Android Police reports: The first Tango device put into production was the "Peanut" phone, which was given to early access partners in 2014. Then came the "Yellowstone" 7-inch tablet, which was initially sold for $1,024 before a massive price drop to $512. The only other devices with Project Tango were the Lenovo Phab2 Pro, which wasn't a very good phone to start off with, and the ZenFone AR. This move isn't entirely surprising, now that Google is working on a software-only solution called ARCore. Not only is ARCore similar to Tango in functionality, but it doesn't require specialized hardware like Tango does.

An anonymous reader quotes a report from Android Police: The Chrome Web Store originally launched in 2010, and serves a hub for installing apps, extensions, and themes packaged for Chrome. Over a year ago, Google announced that it would phase out Chrome apps on Windows, Mac, and Linux in 2018. Today, the company sent out an email to developers with additional information, as well as news about future Progressive Web App support. The existing schedule is mostly still in place -- Chrome apps on the Web Store will no longer be discoverable for Mac, Windows, and Linux users. In fact, if you visit the store right now on anything but a Chromebook, the Apps page is gone. Google originally planned to remove app support on all platforms (except Chrome OS) entirely by Q1 2018, but Google has decided to transition to Progressive Web Apps:

"The Chrome team is now working to enable Progressive Web Apps (PWAs) to be installed on the desktop. Once this functionality ships (roughly targeting mid-2018), users will be able to install web apps to the desktop and launch them via icons and shortcuts; similar to the way that Chrome Apps can be installed today. In order to enable a more seamless transition from Chrome Apps to the web, Chrome will not fully remove support for Chrome Apps on Windows, Mac or Linux until after Desktop PWA installability becomes available in 2018. Timelines are still rough, but this will be a number of months later than the originally planned deprecation timeline of 'early 2018.' We also recognize that Desktop PWAs will not replace all Chrome App capabilities. We have been investigating ways to simplify the transition for developers that depend on exclusive Chrome App APIs, and will continue to focus on this -- in particular the Sockets, HID and Serial APIs."

Google is banning lock screen ads from the Play Store. In the new section on Google's developer monetization page, Google says: "Unless the exclusive purpose of the app is that of a lock screen, apps may not introduce ads or features that monetize the locked display of a device." Android Police reports: So, an app that bills itself as a photo editor, VPN, or file explorer cannot also cram a new lock screen on your device that's infested with ads. However, an app that is actually a lock screen can still monetize with ads. Presumably, you know what you're getting when you install a lock screen app. This policy change is long overdue. It's been a few years since these ads started showing up, and it's getting pretty out of hand.

An anonymous reader shares a report from Android Police: Google's in-development operating system, named "Fuchsia," first appeared over a year ago. It's quite different from Android and Chrome OS, as it runs on top of the real-time "Magenta" kernel instead of Linux. According to recent code commits, Google is working on Fuchsia OS support for the Swift programming language. If you're not familiar with it, Swift is a programming language developed by Apple, which can be used to create iOS/macOS/tvOS/watchOS applications (it can also compile to Linux). Apple calls it "Objective-C without the C," and on the company's own platforms, it can be mixed with existing C/Objective-C/C++ code (similar to how apps on Android can use both Kotlin and Java in the same codebase). We already know that Fuchsia will support apps written in Dart, a C-like language developed by Google, but it looks like Swift could also be supported. On Swift's GitHub repository, a pull request was created by a Google employee that adds Fuchsia OS support to the compiler. At the time of writing, there are discussions about splitting it into several smaller pull requests to make reviewing the code changes easier.

Slashdot reader Lauren Weinstein writes from a blog: My inbox has been filling today with questions regarding Google's new warning to Android application developers that they will no longer be able to access Android accessibility service functions in their apps, unless they can demonstrate that those functions are specifically being used to help users with "disabilities" (a term not defined by Google in the warning). Beyond the overall vagueness when it comes to what is meant by disabilities, this entire approach by Google seems utterly wrongheaded and misguided. "While the intended purpose is for developers to create apps for users with disabilities, the API is often used for other functionality (to overlay content, fill in text fields, etc.)," reports Android Police. "LastPass, Universal Copy, Clipboard Actions, Cerberus, Signal Spy, Tasker, and Network Monitor Mini are just a few examples of applications heavily using this API." It's likely Google is cracking down on apps that use Accessibility Services due to the security risks they pose. "Once granted the right permissions, the API can be used to read data from other apps," reports Android Police.
The developer of BatterySaver received the following message from Google:

We're contacting you because your app, BatterySaver System Shortcut, with package name com.floriandraschbacher.batterysaver.free is requesting the 'android.permission.BIND_ACCESSIBILITY_SERVICE.' Apps requesting accessibility services should only be used to help users with disabilities use Android devices and apps. Your app must comply with our Permissions policy and the Prominent Disclosure requirements of our User Data policy.

Action required: If you aren't already doing so, you must explain to users how your app is using the 'android.permission.BIND_ACCESSIBILITY_SERVICE' to help users with disabilities use Android devices and apps. Apps that fail to meet this requirement within 30 days may be removed from Google Play. Alternatively, you can remove any requests for accessibility services within your app. You can also choose to unpublish your app.

Alternatively, you can choose to unpublish the app. All violations are tracked. Serious or repeated violations of any nature will result in the termination of your developer account, and investigation and possible termination of related Google accounts.

If you've reviewed the policy and feel we may have been in error, please reach out to our policy support team. One of my colleagues will get back to you within 2 business days.

Regards,

The Google Play Review Team