CES 2023 travel-tech report: a stand-in laptop and a renewed phone

For the first time since 2011, I shipped out to CES with somebody else’s laptop. The HP Spectre x360 that I’d taken to the 2018, 2019, 2020 and 2022 showed signs in November of a serious motherboard meltdown, so I took a Lenovo ThinkPad X13s loaned by the company’s PR department.

Beyond having a reliable laptop on which to work, my main objective in taking this computer to Vegas was to see if I’d notice a day-to-day difference in the ThinkPad running on a Qualcomm Snapdragon 8cx Gen 3 instead of the usual Intel processor. The answer: less than I thought.

Hardware I took to CES 2023, shot from above: Pixel 5a and Pixel 7 smartphones, Inseego MiFi X Pro hotspots from T-Mobile and Verizon, chargers for the laptop and phones, headphones and my CES badge.

Battery life definitely seemed better, but I had neither the opportunity nor the motivation to see if the X13s would approach the “up to 28 hours” touted by Lenovo. That’s because every time I found myself sitting next to an outlet, I plugged in the laptop as CES best practices dictate.

Meanwhile, running x86-coded programs on that Qualcomm chip did not reveal any awkward incompatibility moments–even though so few Windows apps have been revised for that ARM processor architecture and therefore must run in Microsoft’s Windows 11 emulation. The uncomplicated nature of the apps I used (Chrome, Firefox, Word, Evernote, Slack and Skype) may have had something to do with that.

I had worried that the laptop only offering two USB ports, both USB-C, might require me to fish out an adapter for any USB-A devices or cables, but this was the first CES in a long time where nobody handed me a press kit on a USB flash drive. And while the X13s isn’t a convertible laptop that can be folded into a tablet, I only ever needed to use it as a standard keyboard-below-screen computer.

I also packed a review phone, a Pixel 7 Google had loaned earlier (and which I reviewed for Patreon readers last month). The 7 has better cameras than my Pixel 5a, so I used that device for most of my photography from the show. As for own Pixel 5a–now on its second life after my successful at-home replacement of the screen I’d shattered in September–it operated with pleasant reliability. Its battery life continued to impress me, although every time I found myself sitting next to an outlet, I plugged in the phone as CES best practices dictate. My one complaint with the 5a: the fingerprint sensor on the back sometimes balks at recognizing my biometrics, even after I’d tried cleaning it a few weeks ago.

On both my phone and that laptop, I stuck to past habits and took all my notes in Evernote. And for once, I didn’t have a single sync conflict between devices! I have no idea how that happened, but it did make me feel better about the subscription fee hitting my credit card the day before I flew to Vegas.

I made some room in my messenger bag for twin loaner hotspots, the T-Mobile and Verizon versions of Inseego’s MiFi Pro X 5G. T-Mobile generally offered faster 5G connectivity, but Verizon’s network sometimes reached where T-Mo’s did not. Both hotspots took far too long to boot up–easily a minute and a half before I could tether the laptop to either–and so more than once, I just used the mobile-hotspot function on the Pixel 5a.

This was also the first CES 2023 where Twitter wasn’t the obvious choice for sharing real-time observations. Instead, I alternated between that social network and Mastodon; that seems unsustainable over the long run, but since my next big trip to a tech event doesn’t happen until MWC Barcelona at the end of February, I have some time to figure that out.

Late or never Android updates remain a problem

Here’s yet another unintentional benefit of my shattering my Pixel 5a’s screen last weekend: an opportunity to reacquaint myself with how slowly many Android smartphone manufacturers still ooze out Google’s system updates.

This is not a new problem, as I can see from re-reading a piece I wrote almost 10 years ago that’s aged a little too well. I had thought that architectural changes Google made to Android starting back in 2017 would have put a dent into this problem by removing much of the recoding work from manufacturers. But dusting off the budget-priced Android phones I reviewed for CNN Underscored early this year (most of which I had not yet returned to the companies responsible, because my desk is a mess) revealed the error of that thought.

Photo shows Android phones stacked on a wooden floor, each showing their software-information screen. The Samsung Galaxy A13's screen is most visible, showing it's running Android 12 with the July 1 security patch.

After multiple cycles of checking for updates on these six phones, installing these updates, rebooting these phones, and checking for updates again until every device reported it was current, here’s where they wound up:

  • Moto G Power: Android 11, August 1 security update
  • Nokia X100: Android 11, August 1 security update
  • OnePlus Nord N200 5G: Android 12, September 5 security update
  • Samsung Galaxy A13 5G: Android 12, July 1security update
  • TCL 20 SE: Android 11, August 1 security update
  • TCL 20 Pro 5G: Android 11, April security update

The current month is October and the current Android version is 13, so the problem should be immediately obvious. And not only did none of these devices have the Android release that I installed on my beloved, now battered Pixel 5a in the middle of August, only one of these devices had Google’s latest security fixes–and only two had the Android release that Google shipped a year ago.

The good news, such as it may be, is that a low price doesn’t condem an Android phone to obsolescence. The A13 sells for $250 and the N200 $240, but both have aged better, software-wise, than the pricier Android devices in that review. You may want to consider that a factor in favor of OnePlus and Samsung if you’re shopping for a low-cost Android phone–while the lagging performance of those other vendors should rate as a serious strike against them.

A humbling gadget-handling lesson

The past four weeks have involved four work trips that took me to events in two other countries and two other states, with travel fatigue compounded by unchacteristically bad sleep in hotel rooms and jet lag from going five time zones to the right, twice, and then three to the left–so of course the place where I would break my phone was less than a mile from my home.

On my walk to Metro to go to Saturday afternoon’s Nationals game, as a drizzle started to turn into real rain, I thought I’d check to see if the team had announced a rain delay. I grabbed my Pixel 5a, opened Twitter, checked the Nats’ Twitter feed and saw an announcement that the game would start half an hour late, and one-handed the phone back into my pocket–except the rain-slicked device slipped free and fell to the sidewalk with a sickening little splat.

A Pixel 5a's screen shows a wide-ranging web of cracks, with trees above reflected in the glass.

Cursing too loudly at myself, I picked up the phone and saw a web of cracks sparkling out from the bottom right, plus a smaller crack on the right above the power button.

First thoughts: You dumbass! You couldn’t have waited until you were in the station and out of the rain?! I mean, I had somehow never shattered a phone’s screen before; the worst I’ve done is drop my Nexus 4 years ago at just the right angle to put a crack in its glass back cover.

Second thoughts: Now what?

The phone that I bought barely 10 months ago not only looks hopelessly janky but makes any sort of onscreen interaction a trying experience. It is usable only under duress.

(Having my phone borderline offline did at least force me to experience the game much more in the moment, in between hearing my friend Anthony recount his recent experience hiking to the top of Kilimanjaro.)

Then I remembered the deal Google announced with iFixit in April to provide “genuine parts” for Pixel devices. Alas, that DIY hub’s $99.99 Pixel 5a repair kit is out of stock at the moment. And while I could obviously pay any third-party shop to fix my phone, that would probably cost more and certainly wouldn’t yield any how-to recap for me to sell somewhere afterwards.

Google no longer lists the Pixel 5a in its online store, and while the Pixel 6a that replaced it seems to be a fine phone in its own right, it lacks a headphone jack and otherwise doesn’t represent a huge advance over the 2021-vintage 5a. There’s also the upcoming, also headphone-jack-deprived Pixel 7–but as I trust I’ve made clear, I’m not a fan of buying the next high-profile phone on the day it ships.

Speaking two weeks ago at a conference hosted by the refurbished-device marketplace BackMarket reminded me that buying a refurb Pixel 5a is an option as well. But unless my phone abuse inflicted injuries beyond my 5a’s screen, I’d feel a little dirty spending a large fraction of the original device’s purchase price when it only needs that one major component replaced.

(No, the iPhone 14 is not an option. Neither is any other iPhone until Apple kills off its Lightning cable. I am so done needing proprietary charging cables.)

Fortunately, I don’t have to decide just yet. My old Pixel 3a continues to gather dust at home as a backup device, and I also still happen to have too many of the budget-priced phones I tested for CNN Underscored at the start of the year. And since it’s been a while since I’ve drunk deeply of Samsung’s flavor of Android, that makes my temporary decision for me: I’ll spend a few weeks, hopefully not more, with a Galaxy A52 A13 5G (I forgot that I’d already shipped back the A52) as my daily phone. And I will do my utmost not to drop the damn thing.

I still don’t get the iPhone pre-order feeding frenzy

Today, Apple started taking pre-orders for a new lineup of smartphones–the same thing it’s done every year since 2007. And just as they have every year since 2007, enough people tried throwing their credit cards at Apple that the company’s online store struggled to respond, leading to one of the more entitled forms of tweeting: Apple won’t let me buy its new smartphone right away!

I don’t get it. But I also didn’t get this customer behavior a dozen years ago, when about the same thing happened at the debut of the iPhone 4. After having seen this kind of self-defeating crowd psychology yield predictable results over the previous three years, I had to vent in my blog at the Post:

So why do people put themselves through the cybernetic equivalent of driving to Tysons Corner Center at 5 p.m. on a Friday in mid-December? A new iPhone–or any other device–isn’t like a ticket to Stephen Strasburg’s pitching debut; your opportunity to buy it does not expire within hours. Nor will they stop making the thing after meeting an initial quota. What’s the point of joining yet another “OMG must buy now!!” shopping stampede?

And yet after 12 more years in which we all should have learned definitively that Apple will crank out new iPhones by the tens of millions, many smartphone shoppers seem to have learned little.

(You can argue that Apple has learned just as little about building an online retail system that can scale to meet this level of demand. But I can understand the company not going too crazy to optimize its retail infrastructure for a one-day-a-year corner case.)

To be clear, I’m not talking about people who have been limping along with damaged smartphones because they didn’t want to buy last year’s Apple gadget weeks or days before its replacement by a shinier successor. I’m also not talking about people who evaluate gadgets for a living–I did once buy a new iPhone on the day of its in-store debut because CNNMoney.com paid me to do that as part of a review.

But if you set an alarm on your completely functional smartphone for 8 a.m. EDT Friday so you could spend $799 and up for a new model that you have not seen or touched and know only from Apple’s staged presentation and the hands-on reports of journalists and analysts at its product-launch event Wednesday, and then you found yourself repeatedly refreshing Apple’s online store to see if your order went through… I hope you’re not asking for sympathy after gadget-hype water once again turned out to be wet.

The multitasking interface in iPadOS 15 is not aging well for me

It didn’t take too long after I installed iPadOS on my iPad mini 5 for me to restore order to my app-icon grid–even if I’m still tweaking that arrangement and dreading the moment when the next iPad system update sends it higgledy piggledy. But another part of Apple’s tablet operating system continues to grind my gears: its multitasking options.

I can’t fault Apple for trying to make this UI more discoverable. In the previous release, I had to look up how to run one app on a third of the screen and leave the other two-thirds to another app every time I wanted to have the clock app and my notes visible side by side for a virtual panel. But in iPadOS 15, I have the opposite problem–the system keeps thinking I’m trying to split the screen between two apps when I have no such intention.

The most common scenario involves me wanting to go to a different site in Safari, when tapping the browser’s address bar routinely invokes the three-dot multitasking button that Apple added to iPadOS 15. That bit of chrome may stay out of the way more often on a larger-screen iPad, but on the 7.9-in. display of my iPad mini, it’s a different story. There, only a few millimeters of screen real estate–either from the top of the screen to the address bar, or between the center of the address bar and address-bar controls like the text-size/display/privacy button and 1Password’s button–seem to separate me from successfully entering a Web address or having the multitasking button thwart that attempt.

The other involves a situation almost as common: iPadOS flashes a notification, and I swipe down to see what it was. From the home screen, this continues to work as it did before–but in an app, iPadOS keeps acting as if I’d meant to invoke the Split View multitasking display by tapping that dreaded three-dot button. Eventually, I will reprogram my muscle memory to swipe slightly off-center to avoid running my finger across that ellipsis icon, except the home-screen behavior keeps telling me I don’t have to change.

So here I am, more than six months after installing this update, and I’m still thumb-wrestling my way around one of its core features. And I’m not alone in feeling this irritated, to judge from my mom’s review of this wayward user experience: “the most distracting thing in the world.” She’s right, and Apple’s wrong.

Post-purchase Pixel 5a praise

Near the end of last year, I retired a functioning smartphone that had aged at a remarkably slow pace over a year of pandemic-induced home confinement and replaced it with a new model. Almost four months later, that $422.94 purchase has proven to be the right call.

The immediate upgrade I got with the Google Pixel 5a I bought on sale for $50 off to succeed the Pixel 3a I’d purchased in the innocent summer days of 2019 is storage space. As in, the 3a’s 64 GB had become an increasing irritant, requiring regular dives into the Settings app to clear app caches and data; the 5a has twice as much storage, and so far I’ve only used up 69 GB of it even after I haven’t bothered to uninstall conference apps after coming home from those events.

Photo shows Pixel 5a on a wooden surface, with the afternoon sun glinting off the cameras on its back.

The advertised upgrade with the 5a–formally known as the “Google Pixel 5a with 5G”–was its 5G connectivity. The next generation of wireless broadband hasn’t delivered much for many wireless customers, but T-Mobile’s midband 5G (which it brands “Ultra Capacity”) has frequently served up download speeds in excess of 500 megabits per second outdoors.

I did not expect to get a comparable advance in battery life on this phone, knowing how often smartphone vendors have hyped that metric. But in everyday use, even at battery-abusing events like CES, my 5a has been a champion. As I type this after more than 11 hours of low-key use, the phone is estimating one day and 12 hours of additional runtime. That’s nuts–and believable after what I’ve seen over the past four months.

The one upgrade I didn’t even think about when buying the 5a but have since come to appreciate on a daily basis is the 16 megapixel wide-angle camera on its back that augments its regular 12.2 MP camera (the same Sony IMX363 that Google has been sticking in its phones since the Pixel 3). This extra lens has opened up my phone photographic possibilities, by which I mean it’s freed me from having to step off a sidewalk to get an especially large building in the frame.

I do wish the 5a were a little smaller, as its 6.34-in. touchscreen is just big enough to thwart easy placement of a thumb at the far corners of that display when I’m using the device one-handed. But as I realized testing $500-and-under smartphones for CNN Underscored (the 5a came away as my top pick), almost every other Android phone is bigger.

The compromises this phone has entailed have been unobjectionable. It lacks cordless charging, but the only place I could have used that has been my home. It doesn’t support millimeter-wave 5G, but T-Mobile barely offers those fast, fragile frequencies anywhere and even Verizon’s mm-wave network remains evanescent. I would like to see Google commit to more than three years of operating-system updates, but over the time I’m likely to keep this phone I’m unlikely to exhaust that support but do stand to benefit from Google’s recent move to sell authorized repair parts through iFixit.

But while I expect my 5a to serve me well through at least late 2023, I don’t expect it to be sold nearly that long: All signs point to Google introducing the Pixel 6a at Google I/O next month. And while that model will apparently add Google’s faster Tensor processor, its fingerprint sensor will reside under the screen and may be fussier to use–and it will apparently omit a headphone jack. The prospect of that unnecessary, unrequested “simplification” already has me dreading the next upgrade cycle.

One of my newer travel rituals: setting up a TV hit away from home

AUSTIN

Normal people don’t check into lodging at a destination and then evaluate the room for its TV-backdrop potential, but I have never pretended too hard to be a member of the normal-people demographic.

Picture shows a Pixel 5a phone cradled in a GorillaPod tripod mounted to the screen of an HP Spectre x360 laptop.

So when I got a message from my usual producer at Al Jazeera on my flight here Friday (my thanks to United for adding free messaging to the inflight WiFi in December) asking if I could comment on the White House’s attempts to add TikTok to its public-diplomacy strategy, I knew I’d need to find a workable background.

Fortunately, the house I’m renting (and had rented for several years in a row for SXSW in the Before Times) has an excellent bookshelf in the living room. It also had enough room in front for two chairs: one for me to sit in, another to serve as a stand of sorts for my laptop.

Because that 2017-vintage HP Spectre x360 has a woeful webcam, I don’t just park it on a table or another suitable flat surface. At the same time, I don’t want to do a video interview looking at my interviewer on a phone screen that’s more than a foot away. Instead, I use my Pixel 5a phone’s back camera in place of the laptop’s camera–a workaround that requires running Dev47Apps’ DroidCam app on that Android device and on my Windows laptop and connecting the two devices with a USB-C cable.

Then I place the laptop, folded open to its “tent mode,” over the top rail on a chair so I can see Zoom, Skype or whatever app I’m using for the interview (or virtual panel) on the computer’s screen, and then use an old Joby GorillaPod flexible tripod to position the phone atop the laptop.

That gadget accessory is now among the first things I toss into my suitcase before a trip: Instead of flip-out, rigid legs, this tripod features a trio of flexible legs that you can wrap around a nearby object. Or, in this case, splay out across the hinge on a Windows laptop in tent mode, such that the smartphone camera sits just about at eye level.

That may look like a ton of work, but I’ve now gone through this routine enough times that it doesn’t feel like it demands much time–certainly not when the TV hit starts a bit behind schedule, as this one Friday did.

CES 2022 travel-tech report: a new phone and a renewed laptop

Uncharacteristically light attendance at CES this week allowed me to pack uncharacteristically light. With so many tech-news sites canceling plans to send journalists to the Consumer Technology Association’s annual gathering, I knew I wouldn’t need my traditional CES accessory of a travel power strip to free up outlets in any crowded press room.

I also opted not to pack any of the WiFi hotspots I had sitting on my desk from the last update of Wirecutter’s guide to same. Even in the likely event of the show’s WiFi being its usual inadequate self, I figured I had sufficient backup bandwidth in the form of the new Pixel 5a in my pocket, the expanded mobile-hotspot quota on my account, and the T-Mobile 5G network my previous phone couldn’t use.

Photo shows my HP Spectre x360 laptop sitting on the wood floor of my home office, on top of which sit my CES badge, the laptop's charger, a USB-C cable to charge the phone, a USB-to-Ethernet adapter, headphones and my Pixel 5a phone.

My other smart move before heading out to Vegas was replacing my late-2017 HP laptop’s battery with an aftermarket unit, a bit of laptop surgery I did in October. All of this helped make CES much less of a gadget-abuse scenario in my return to covering it in-person after last year’s distanced, digital-only conference.

The Google Pixel 5a, the only new device in my messenger bag, acquitted itself especially well. On a good day, its battery can run well into the next afternoon, and even at CES–where I did rely frequently on the phone’s mobile-hotspot feature to get my laptop online–I never saw this Android device’s battery get into the under-33% state that would get me nervous. My charging the phone at lunch happened out of habit, not necessity.

I also quickly grew to appreciate how the 5a’s wide-angle lens helped capture some of the bigger exhibits on and off the show floor. The sole quibble I can think of: The phone reported that it restarted overnight Friday morning, and I’d like to know what caused that crash.

My HP Spectre x360, meanwhile, was one of the oldest items in my bag but felt much newer with that replacement battery. It was nice to sit down to watch a panel and not need a spot next to a power outlet. And for whatever reason, this computer ran much more reliably than it had at CES two years ago, without any mysterious reboots sometimes interrupted by boot-device-not-found errors.

Lower CES attendance, estimated by CTA Friday at “well over 40,000,” did not banish CES bandwidth struggles. My laptop did not always connect to conference WiFi networks–have I mentioned that Windows 10’s “Can’t connect to this network” is not a helpful error message?–but all three press rooms had abundant Ethernet cables. The $10 and change I spent on a USB-to-Ethernet adapter in 2012 has turned out to be an exceptional deal.

As before, I took all of my notes in Evernote, but this time the app generated a few note conflicts when I switched from phone to laptop and back. If I could click or tap a “sync now” button before each device switch, I would–but Evernote removed that bit of UI out of a belief that its automatic sync is now reliable enough to make it obsolete.

The other app I leaned on heavily during my time at CES was the conference’s own mobile app. I hadn’t bothered with that in previous years, but learning that CTA had hired Web Summit to provide this event’s digital platform made me want to try it. Unsurprisingly, the CES app looks and works like the Web Summit and Collision apps, so I didn’t have much to figure out.

As at those other conferences, I leaned on this app to manage my schedule while ignoring in-app connection requests in favor of the kind of networking impossible at last year’s CES: masked-face-to-masked-face conversations that ended with an exchange of business cards.

Android phone migration has gotten easier–except for Google Pay and Google Voice

Moving from my old Pixel 3a to my new Pixel 5a provided my smoothest Android phone-migration experience yet. I had much less home-screen housekeeping to do on my new device than two years ago, and one key Google app showed a particularly dramatic improvement. But then I had to deal with Google Pay and Google Voice.

Overall, Google’s instructions get across how easy process has become. Tap yes in the “Copy apps & data” button on the new phone, unlock the old phone, connect the two with a USB-C cable, tap yes in the old phone’s “Copy data to new phone?” dialog, then wait–about 21 minutes in my case.

A Pixel 5a showing the "Transfer accounts" screen in Google Authenticator sits atop a Pixel 3a showing the same screen in the same app.

Google’s Android-transfer system accurately reproduced my app-icon layout (the contrast with upgrading to iPadOS 15 did not escape my attention) and wallpaper, with the only missing item being a home-screen icon for Android Auto.

I did still have to wait for most individual apps to download off Google’s Play Store, and their new-phone user experience varied awkwardly. Some, such as Feedly, LinkedIn and FlightRadar24, didn’t need me to log back in; most demanded a new entry of usernames and passwords (made much easier by 1Password); a few required extra bouts of authentication.

One Google app pleasantly surprised me, given the sensitivity of its stored data. Google Authenticator previously required renewing each two-step verification code securing a site login as if your old phone had fallen into the ocean, an experience that Google security chief Stephan Somogyi in 2017 apologetically described to me as “a complete, total and unmitigated pain.”

But in 2021, an old phone’s Google Authenticator can generate a catchall QR Code for its saved accounts; scan it with the new phone’s copy of Authenticator, and you’ve got your one-time passcodes for those accounts ready there. Great!

And then two other Google apps showed how awkward this process can remain. Google Pay–not the mobile-payments app that debuted as Google Wallet, but the new release that shipped this spring and then required some non-trivial settings restoration–landed on the new Pixel 5a as if I had never used it before.

I had to start by typing in my cell number because this Google service relies on that for authentication instead of a Google account. As Ars Technica’s Ron Amadeo explained/warned back in March, this setup resulted from Google electing to build a new Google Pay off code optimized for the Indian market, where SMS authentication apparently reigns supreme. And then I then had to add back my saved credit cards, one at a time.

The last hiccup, I hope, came with Google Voice. The oft-neglected Internet-telephony app that I use for my work number seemed to be configured properly on the new phone, but then a journalist trying to reach me for a radio interview had her call go to voicemail. Eight times in a row. The answer turned out to be that Google Voice’s account settings had my number associated with two smartphones and two copies of the same number, a level of confusion that the system evidently resolved by not patching calls through to the newest device.

But now that’s squared away, and I think I can make it through the rest of this trying year without further mobile-app troubleshooting. I hope that’s the case for everybody reading this too.

Android 12 early impressions: improvement via imprecision

Two weeks after I installed Android 12 on my aging, yet well-maintaned Pixel 3a smartphone, the biggest selling point of this release is not the self-tinting interface colors that Google talked up this summer. Instead, I’m appreciating a new option to leave apps a little fuzzier about my whereabouts.

In adding the ability to deny an app access to your precise location, Android 12 returns to the earliest days of Google’s mobile operating system, when an app could ask for either “fine” or “coarse” location. But it also reflects what we’ve learned since then about how location-data brokers will embed location-tracking code in other apps, often without disclosure, and then exploit that harvested info to build vast databases.

Photo shows the Android 12 Settings app open to a page denying the Today Weather access to my precise location; in the background, the print edition of the Nov. 12, 2021 Washington Post reveals a bit of the weather forecast.

So my first move after my phone rebooted into Android 12 was to take the GPS keys away from some apps. I started with one I already paid for, Today Weather. Why bother depriving a paid-for and therefore ad-free app of my exact location? Because the forecast shouldn’t change that much between here and a mile away–but keeping my precise coordinates from a third party means they can’t get exposed if that firm suffers a data breach later on.

My second move was much less exciting, in that I swapped out some of the default screen widgets: I like scallops and I like having a large display of the time on my home screen, but I don’t like the scallop-shaped clock widget that comes standard in Android 12.

My first software-update-induced moment of confusion, meanwhile, came a day after I installed this update when I mashed down the power button to invove the Google Pay shortcut to choose a different stored credit card for a purchase–and nothing happened. That’s because Android 12 moved that from the power-button menu to the Quick Settings menu. Broken muscle memory aside, I get that relocating this setting from a non-obvious spot to a menu that people use all the time should make it more discoverable.

Finally, one Android 12 detail that’s gotten less attention than the others in press coverage just might save me from waking up with a phone at 10% of a charge: When you plug a phone into a charger, a wave of sparkles washes up the screen to confirm that current is flowing to the device. Considering my own record of inattentive device charging, that’s a feature I could have used 10 years ago.