# Phones Published articles for Phones. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Putting sign language AI into users' hands DevFeed: [Putting sign language AI into users' hands]() Original publisher: [Read original article]() Author: Google DeepMind Sign Language Team Published: 2026-08-12T14:01:59Z Content type: article Language: en Sources: [Google DeepMind News]() Topics: [Artificial Intelligence](), [Accessibility](), [Google](), [Android](), [Frontier AI]() Tags: [accessibility](), [ai](), [android](), [community](), [devices](), [evaluation](), [frontier-ai](), [google](), [models](), [phones](), [release](), [research]() ### AI overview Google introduces sign-language-to-text (SL2T), a model integrated into Gboard and Live Transcribe to support Deaf and hard-of-hearing users. The article describes community-led development, evaluation with Deaf users and experts, responsible deployment, expansion to additional sign languages, and initial availability on Pixel 11 at no additional cost. ### Source excerpt Introducing sign-language-to-text (SL2T), our breakthrough model powering new sign language features for Deaf and hard of hearing users. ## Accelerating Gemini Nano models on Pixel with frozen Multi-Token Prediction DevFeed: [Accelerating Gemini Nano models on Pixel with frozen Multi-Token Prediction]() Original publisher: [Read original article]() Published: 2026-06-26T18:30:00Z Content type: article Language: en Sources: [The latest research from Google]() Topics: [AI Inference](), [On-device AI](), [Google](), [LLMs](), [gemma]() Tags: [ai](), [efficiency](), [energy](), [gemini](), [inference](), [machine-intelligence](), [mobile-systems](), [natural-language-processing](), [on-device](), [on-device-ai](), [phones]() ### AI overview Google Research describes a method for retrofitting Multi-Token Prediction onto frozen Gemini Nano v3 production models to accelerate on-device inference on Pixel phones. The approach targets mobile energy and memory constraints, improving the speed and energy efficiency of features such as notification summaries and proofreading without requiring separate drafting models. ### Source excerpt Machine Intelligence ## Apple and Google Failed to Enforce App Store Policies Against Musk's Abusive Apps DevFeed: [Apple and Google Failed to Enforce App Store Policies Against Musk's Abusive Apps]() Original publisher: [Read original article]() Author: Alex Russell Published: 2026-01-20T00:00:00Z Content type: opinion Language: en Sources: [Alex Russell]() Topics: [X (Twitter)](), [Mobile](), [Google](), [App]() Tags: [app-store](), [apple](), [browsers](), [business](), [competition](), [elon-musk](), [google](), [mobile](), [phones](), [speech](), [twitter]() ### AI overview An opinion article argues that Apple and Google failed to enforce their App Store policies against abusive Twitter apps, exposing tensions between stated safety principles, antitrust defenses and business interests. ### Source excerpt Twitter's descent into a gutter of the lowest order has been wrenching: Elon Musk's Grok and the Mass Undressing Scandal As I draft this, a week later, it appears pressure from civil society, investigations by regulators, and outright bans on multiple continents have forced Musk to back down to an uncertain degree. As this scandal roiled, Twitter's apps have been continuously available in Google's Play and Apple's App Store, marking new lows in moral cowardice and non-enforcement of the duopolist's own policies. Now we sit on tenterhooks, wondering if the worst has actually passed. What outrage the will the valley's billionaire man-children unleash next? Meanwhile, we brace for this episode to embolden censorious authoritarians keen to suppress a free press and legitimate speech they dislike. This is the backdrop to Elizabeth Lopatto's must-read denunciation in The Verge: It is genuinely unbelievable to me that I wasted hours of my actual life on a court case where Apple explained it needed total control of its App Store to protect its users. Total control of the App Store was Apple's main argument against antitrust enforcement: The company insisted that its monopolistic control of what users could install on their phones was essential to create a walled garden where it could protect children from unsafe content. Ha! Ha ha ha!! -- Elizabeth Lopatto, "Tim Cook and Sundar Pichai are cowards, The Verge" Failure to react to the "everything app" going all-in on abuse of women and girls for weeks reveals the illegitimacy of their mobile monopolies1; anyone pretending otherwise is a fool or a dupe. We don't need to guess why they sat on their hands. Acting against Musk's abusive apps might put Apple and Google out of favour with an erratic, power-tripping administration which in turn could impact short-term business prospects. Their stated principles are incompatible with maximizing shareholder value under competitive authoritarianism. Recall that both firms lent their mono ## Android Phones Might Ask for /64 Delegated Prefix DevFeed: [Android Phones Might Ask for /64 Delegated Prefix]() Original publisher: [Read original article]() Published: 2025-09-29T05:43:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Android](), [Networks]() Tags: [android](), [developers](), [dhcp](), [ipv6](), [network](), [phones]() ### AI overview The article critiques Android 11's support for DHCPv6 prefix delegation, which is limited to assigning delegated prefixes. It questions the rationale for giving phones dedicated /64 prefixes on Wi-Fi networks and challenges arguments concerning IPv4, battery use, IPv6 address assignment, and ND cache exhaustion. ### Source excerpt I'm too old to be fighting with windmills, but sometimes I have to get a rant off my chest. This one was triggered by the latest episode of the hilarious1 "DHCPv6 on Android" soap opera In a 720-degree turnaround, Android 11 supports DHCPv6, but only for prefix delegation purposes. Yes, you got it right, in a year or two, every phone might want to have a dedicated /64 prefix assigned to it on WiFi segments2. Want more details? Well, there's a high-level overview published on the Android Developers blog and a corresponding message sent to the v6ops mailing list. Let's see how much sense that makes. Read more ... ## ScreenshotWhale Generates App Store Screenshots with a Layer-Based Editor and Automatic Localization DevFeed: [ScreenshotWhale Generates App Store Screenshots with a Layer-Based Editor and Automatic Localization]() Original publisher: [Read original article]() Author: Jorge Castillo Published: 2025-09-16T16:36:22Z Content type: article Language: en Sources: [Effective Android]() Topics: [App](), [Artificial Intelligence](), [Vibe coding](), [Figma](), [Internationalization (i18n)](), [Cloud](), [User Experience]() Tags: [ai](), [android](), [app](), [app-store](), [building](), [cloud](), [code](), [coding](), [editor](), [export](), [figma](), [i18n](), [ios](), [languages](), [phones](), [templates]() ### AI overview The article introduces ScreenshotWhale, a cloud-based service for creating app store screenshots. It offers a Figma-style layer-based editor, templates, support for Android and iOS device formats, and automatic internationalization during export. The product is in its initial stages and is presented as seeking user feedback. ### Source excerpt Some words for the people who joined the newsletter these days. ## On-device AI may shape the future of Android phone development DevFeed: [On-device AI may shape the future of Android phone development]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2025-02-09T18:53:19Z Content type: opinion Language: en Sources: [Kaushik Gopal's Site]() Topics: [Artificial Intelligence](), [On-device AI](), [Mobile](), [Android](), [Google]() Tags: [ai](), [android](), [development](), [gemini](), [google](), [mobile](), [models](), [on-device](), [on-device-ai](), [phones](), [samsung]() ### AI overview This commentary predicts that on-device AI, including smaller models running locally on phones, will become a major focus of Android development. It also suggests Google or Samsung could gain mobile market share as Apple struggles to establish a strong AI position. ### Source excerpt In Vinay's latest newsletter, he asks a few of us #AndroidDev to predict what the future of Android development is going to look like. Yours truly had this as one of the predictions: AI everything 🙄 ... On the product side, we'll see more on-device AI, with smaller models like Gemini Flash/o3-mini running locally to provide operator-like intelligence directly on phones and this will probably be what most folks are geared towards doing for mobile development. Looking at this Youtube video that's now doing the rounds, I'm starting to feel ever so slightly validated. Google (or Samsung) truly have their shot of gaining significant Mobile market share again, especially given how much Apple has been floundering in the AI space. ## Advances in private training for production on-device language models DevFeed: [Advances in private training for production on-device language models]() Original publisher: [Read original article]() Author: Google AI (noreply@blogger.com) Published: 2024-02-21T20:15:00Z Content type: article Language: en Sources: [Google Research]() Topics: [Language models](), [Federated Learning](), [Google](), [Mobile]() Tags: [differential-privacy](), [federated-learning](), [gboard](), [google](), [language-models](), [on-device](), [on-device-learning](), [phones](), [privacy](), [production](), [research](), [responsible-ai](), [training]() ### AI overview This Google Research article describes advances in privately training Gboard's on-device language models. It explains how federated learning keeps training data on users' devices while differential privacy provides formal privacy guarantees. The article reports that all Gboard next-word-prediction neural language models use federated learning with formal differential privacy guarantees, across more than 30 models, 7 or more languages, and 15 or more countries. ### Source excerpt Posted by Zheng Xu, Research Scientist, and Yanxiang Zhang, Software Engineer, Google Language models (LMs) trained to predict the next word given input text are the key technology for many applications [1, 2]. In Gboard, LMs are used to improve users' typing experience by supporting features like next word prediction (NWP), Smart Compose, smart completion and suggestion, slide to type, and proofread. Deploying models on users' devices rather than enterprise servers has advantages like lower latency and better privacy for model usage. While training on-device models directly from user data effectively improves the utility performance for applications such as NWP and smart text selection, protecting the privacy of user data for model training is important. Gboard features powered by on-device language models. In this blog we discuss how years of research advances now power the private training of Gboard LMs, since the proof-of-concept development of federated learning (FL) in 2017 and formal differential privacy (DP) guarantees in 2022. FL enables mobile phones to collaboratively learn a model while keeping all the training data on device, and DP provides a quantifiable measure of data anonymization. Formally, DP is often characterized by (ε, δ) with smaller values representing stronger guarantees. Machine learning (ML) models are considered to have reasonable DP guarantees for ε=10 and strong DP guarantees for ε=1 when δ is small. As of today, all NWP neural network LMs in Gboard are trained with FL with formal DP guarantees, and all future launches of Gboard LMs trained on user data require DP. These 30+ Gboard on-device LMs are launched in 7+ languages and 15+ countries, and satisfy (ɛ, δ)-DP guarantees of small δ of 10-10 and ɛ between 0.994 and 13.69. To the best of our knowledge, this is the largest known deployment of user-level DP in production at Google or anywhere, and the first time a strong DP guarantee of ɛ < 1 is announced for models trained directly on ## How we redesigned Slack for the iPad DevFeed: [How we redesigned Slack for the iPad]() Original publisher: [Read original article]() Author: skazan2 Published: 2022-09-02T00:50:18Z Content type: article Language: en Sources: [Slack Design]() Topics: [Slack](), [Mobile](), [App]() Tags: [app](), [customers](), [multitasking](), [navigation](), [os](), [phones](), [search](), [slack](), [threads](), [what-we-do]() ### AI overview Slack Design describes how the Slack team redesigned the iPad app after researching user needs and auditing the existing experience. The article identifies triage, search, and staying mobile as key use cases, and discusses navigation and productivity challenges in the earlier app. ### Source excerpt We all get our work done differently. Some of us are at our desks from 9 to 5, while others work more flexible hours. Some of us commute to work, while others work from home (or do both). Regardless of our setup, we are always connected and available, either through our desktop or our phones. [...] The post How we redesigned Slack for the iPad appeared first on Slack Design. ## Android App Shortcuts DevFeed: [Android App Shortcuts]() Original publisher: [Read original article]() Author: Sanskar Agrawal Published: 2021-12-11T09:31:59Z Content type: tutorial Language: en Sources: [Sanskar's Stuff]() Topics: [Android](), [App](), [coding]() Tags: [android](), [android-app-development](), [android-studio](), [app](), [coding](), [how-to](), [kotlin](), [mobile-apps](), [phones](), [shortcuts]() ### AI overview A tutorial on adding static launcher shortcuts to Android apps using shortcuts.xml. It explains how these shortcuts expose app destinations or features from the launcher, covers compatibility with lower minSdkVersion values, and discusses intents, activities, and fragment-centric architectures. ### Source excerpt Most popular apps on Android phones have launcher shortcuts; app-specific destinations or features that appear when you long tap their icon in the launcher. Users can even drag the shortcuts outside to your home screen as demoed below: This has bee... ## What does Matter mean to you? DevFeed: [What does Matter mean to you?]() Original publisher: [Read original article]() Author: John Lee Published: 2021-11-23T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [Matter](), [Internet of things](), [Wi-Fi](), [Network](), [zigbee]() Tags: [802-15-4](), [amazon](), [android](), [apple](), [blog](), [collaboration](), [connectivity](), [esp32](), [google](), [iot](), [matter](), [outages](), [phones](), [router](), [samsung](), [standards](), [thread](), [voice](), [wi-fi](), [zigbee]() ### AI overview The article explains how the Matter standard could affect end-users and device-makers. It describes interoperability across vendors, local device-to-device automation, support for Wi-Fi and Thread, operation during Internet outages, and bridges for existing ZigBee or BLE Mesh products. ### Source excerpt You may have recently read about the newly introduced standard, Matter. Matter is an initiative of the Connectivity Standards Alliance, and developed through collaboration amongst all the leaders of the IoT industry. There is a high level of excitement about Matter and what it aims to achieve. We often hear questions from device-makers and end-users as to how they can benefit from the Matter standard. ## 2021-05-17 Status update DevFeed: [2021-05-17 Status update]() Original publisher: [Read original article]() Author: Mobian team Published: 2021-05-17T00:00:00Z Content type: release Language: en Sources: [Mobian's Blog]() Topics: [Linux](), [Mobile](), [Debian](), [Development](), [kernels](), [maintenance](), [Tooling]() Tags: [debian](), [development](), [linux](), [maintenance](), [mobile](), [phones](), [porting](), [tooling](), [update](), [updated]() ### AI overview This Mobian status update reports progress on distribution stability and tooling, the positive reception of the Mobian Community Edition PinePhone, donations to Debian and investment in infrastructure, and official support for the Pocophone F1 and OnePlus 6 and 6T. The newly supported phones remain unsuitable as daily drivers because modem, audio, and camera functionality is not yet working. ### Source excerpt The past few months have been quieter than usual regarding Mobian development, but that's not to say we didn't make progress! Actually, even though user-visible changes are few, we kept working on improving both the stability of our distribution and our tooling, so that new developments can be better tested, and reach users faster than they used to. Mobian CE reception and outcomes The Mobian Community Edition PinePhone has been a great success for us, with of course a few hiccups, but the feedback we received so far has been extremely positive. We'd like to take this opportunity to thank Pine64 once again for allowing us to be part of this amazing journey! As you probably know, Pine64 generously donated 10$ per device to the Mobian project, which we received early last month. Out of this amount, we chose to donate 5000EUR back to the Debian project (which provides the foundation for all of our work on Mobian), and invested about the same amount into our own infrastructure (workstation, build servers...). Finally, we purchased a few additional mobile devices we considered interesting targets and started porting Mobian to those. New supported devices Let's play with Android phones! Until recently, Mobian supported only Pine64's PinePhone, PineTab and Purism's Librem 5. This is partly related to our choice of only using mainline kernels, instead of vendor-provided Android kernels: those use a number of non-standard interfaces, and require additional software, such as Halium, in order to be used with a "standard" Linux userspace. In addition, vendor kernels are generally outdated and very rarely updated to newer kernel releases, which is obviously a concern for long-term maintenance. Fortunately, our friends at postmarketOS have committed to mainlining devices for quite some time now, and by encouraging such development have reached great results so far! Based on their initiative, and more specifically thanks to @calebccff's and @Joel's work on the SDM845 kernel, we have b ## Multi-Signal GNSS & the Curious Case of Galileo E24: Part 1 DevFeed: [Multi-Signal GNSS & the Curious Case of Galileo E24: Part 1]() Original publisher: [Read original article]() Published: 2020-07-18T07:07:23Z Content type: article Language: en Sources: [Bert Hubert's writings]() Topics: [systems]() Tags: [engineering](), [equipment](), [gnss](), [phones](), [signal](), [standard]() ### AI overview This article investigates why Galileo satellite E24 was reported as being 1.5 meters off while phones and other positioning equipment showed no problems. It introduces multi-frequency GNSS and explains how ionospheric delays affect satellite-distance measurements. ### Source excerpt GPS, GLONASS, Galileo, BeiDou (Global Navigational Satellite Systems, GNSS) are miracles of engineering. And within any complex system hide surprises and unsuspected complications. In this post I go over how we resolved an odd observation: that everyone (including major institutions) reported that one of the Galileo satellites (E24) appeared to be off by 1.5 meters, while actual positioning equipment (like phones) showed no problems at all. Through the explanation, we'll casually learn a thing or two about the cool concept of multi-frequency GNSS. ## October Update: PineTime, Delays and Shipping News DevFeed: [October Update: PineTime, Delays and Shipping News]() Original publisher: [Read original article]() Published: 2019-10-05T00:00:00Z Content type: news Language: en Sources: [Community blog on PINE64]() Topics: [Pinephone](), [Users]() Tags: [community](), [news](), [phones](), [pinebook-pro](), [pinephone](), [pinetime](), [update]() ### AI overview Pine64's October update covers PineTime, PinePhone and Pinebook Pro developments, including prototype shipments, community involvement and delays caused by miscommunications, factory errors and other issues. ### Source excerpt This month's update will be slightly shorter than usual - I have been dealing with some health issues recently, which significantly reduced my time to actively engage with the community. Hopefully I'll make it up to you in November. September has been a bitter-sweet month for us. On the one hand, we've seen a lot of great developments: the first Pinebook Pros have reached their owners, and the reception has so far been great; core developers have started receiving their PinePhone prototype handsets and dev pre-order coupons have started going out; and we've announced the PineTime smartwatch - a companion for the PinePhone and other Linux phones. On the other hand, (and I have no intention of sugar-coating the situation) things haven't gone exactly according to plan regarding shipments of developers' PinePhones and Pinebook Pros for end-users. A series of miscommunications, factory errors as well as just good 'ol bad luck resulted in dates slipping by a few weeks. To those of you who had to wait for your units and to those whom are still waiting - we apologize for the delay, we're very sorry. Read on to find out what happened. [EDIT 18/10/2019] Since writing this blog entry I provided an update on the situation (Pinebook Pro, PinePhone and PineTime dev kits shipping) on the forum. Click here. Bullet Points: Pinebook Pro first batch shipping delay causes explained ; we're sorry Future shipments 2 weeks delay ; we won't put shipping staff at risk Pinebook Pro early adopter feedback very positive ; issues noted and worked on PinePhone Dev edition delay explained ; prototypes run great The PineTime ; a side-project with a lot of potential ; community driven Closing thoughts - are we being stretched thin? Pinebook Pro shipping delay detailed explanation Let me give you a run-down of the events that caused the delay in the shipment of Pinebook Pros to customers. The delay was caused by a series of intertwined events, so it's just appropriate that I list them in chronologic ## Recent fixes to reduce backlog on Android phones DevFeed: [Recent fixes to reduce backlog on Android phones]() Original publisher: [Read original article]() Author: elvis314 Published: 2019-07-17T19:54:00Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Android](), [Docker](), [Linux](), [Testing](), [USB]() Tags: [android](), [docker](), [linux](), [phones](), [testing](), [uncategorized](), [unit-testing](), [update](), [upgrade](), [usb]() ### AI overview This post describes fixes that reduced a backlog of Android phone jobs hosted at Bitbar, including recovering offline devices, restarting host machines, updating Taskcluster scripts, improving scheduling, disabling duplicate jobs, and removing old worker devices. It also outlines possible future improvements. ### Source excerpt Last week it seemed that all our limited resource machines were perpetually backlogged. I wrote yesterday to provide insight into what we run and some of our limitations. This post will be discussing the Android phones backlog last week specifically. ... Continue reading -> ## TIP: Adapting to Tablets DevFeed: [TIP: Adapting to Tablets]() Original publisher: [Read original article]() Author: Shai Almog Published: 2019-03-04T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [App](), [Development](), [API]() Tags: [api](), [app-development](), [classes](), [compilation](), [development](), [how-to](), [phone-app](), [phones](), [subclass]() ### AI overview This tutorial presents a "phone first" approach for adapting Codename One applications to tablets. It describes building the phone version first, then restructuring forms and subclasses to support a tablet layout with a permanent side menu and replaceable content. The author notes that generalizing the approach into a standardized API has been difficult. ### Source excerpt A while back someone asked on stackoverflow how to adapt a Codename One app to tablets. I provided quite a few references in the answer and following discussion but I think a better approach is to explain what we did with the recent Codename One Build app because that's what I've been doing in all recent apps I worked on. I call this approach the "phone first" approach for universal app development. It starts by forgetting about the tablet and focusing on building a good looking phone app. In this app I usually subclass Form for all the classes which instantly creates an app that's very suitable for phones. ## Amicus brief in "Carpenter" Supreme Court Case DevFeed: [Amicus brief in "Carpenter" Supreme Court Case]() Original publisher: [Read original article]() Author: Adam Published: 2017-08-16T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [data]() Tags: [blog](), [blog-post](), [government](), [law](), [location](), [phones](), [update]() ### AI overview The article discusses an amicus brief filed in the U.S. Supreme Court arguing that the Fourth Amendment prohibits the government from accessing cell-site location information tracked by cellphone providers without a warrant. ### Source excerpt [no description provided] ## How to turn an Android phone into a cycling GPS DevFeed: [How to turn an Android phone into a cycling GPS]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2016-07-21T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [Android](), [App]() Tags: [android](), [app](), [blogs](), [cycling](), [download](), [gps](), [howto](), [leaderboard](), [maps](), [navigation](), [offline](), [people](), [phones](), [route]() ### AI overview A tutorial for repurposing an Android phone as a cycling GPS using OsmAnd and Dropsync. It explains how to track activities, import GPX tracks, navigate with screen and voice directions, plan routes with Strava, and use offline maps. ### Source excerpt Cycling is all about exploring: visiting new places and making existing routes more fun with better streets. So there must be an app that allows to plan your route and start cycling right? ## Reduce, reuse, recycle DevFeed: [Reduce, reuse, recycle]() Original publisher: [Read original article]() Author: gbrown-mozilla Published: 2016-03-10T23:53:41Z Content type: tutorial Language: en Sources: [Mozilla Automation]() Topics: [LineageOS](), [USB](), [Ubuntu](), [make](), [Java](), [Assembly](), [Bash]() Tags: [android](), [aosp](), [boot](), [build](), [building](), [firefox](), [firefox-for-android](), [java](), [make](), [mozilla](), [phones](), [root](), [testing](), [usb]() ### AI overview The article describes rebuilding AOSP on Ubuntu 14.04 and flashing Android 4.3 onto a Galaxy Nexus after older Android versions could no longer run current Firefox for Android builds. It covers the build, bootloader, USB, fastboot, root, and Java configuration steps, and reports that the Galaxy Nexus became functional and rooted. ### Source excerpt As Firefox for Android drops support for ancient versions of Android, I find my collection of test phones becoming less ... Continue reading -> ## Graded browser support version 1.1 DevFeed: [Graded browser support version 1.1]() Original publisher: [Read original article]() Author: espen Published: 2011-06-27T13:41:23Z Content type: article Language: en Sources: [Finn.no]() Topics: [browser](), [browsers](), [Mobile](), [Website]() Tags: [browser](), [browsers](), [ipad](), [mobile](), [mobile-web](), [phones](), [updated](), [version]() ### AI overview The article announces version 1.1 of the company's graded browser support matrix. It simplifies browser version targeting, adds support guidance for the mobile web service m.finn.no, and includes tablets in the desktop service matrix. Android-powered devices are not supported. ### Source excerpt We have reworked our graded browser support matrix which was released last year. Following the Laws of Simplicity we reduced the complexity in order to make it easier for everyone at our company to understand. We cut a lot of the version number into targeting latest for browsers which are frequently updated. There is also a support matrix for mobile phones which is targeting our new mobile web service m.finn.no. In addition to updating the versions we have also made the decision to include tablets in the support matrix for our desktop verison of our service. This is because we are currently not looking at creating specialized versions for tablets and our service works just fine on the tablets currently hitting our site. Currently almost all of our trafic is coming from iPad's, therefor Andoid powered devices are not supported.