Tag: Android

Posted on
by

The kid has been watching a zillion teardown/repair/dismantling videos of various devices on YouTube, and wants to learn to repair phones.

So I took the old phones and tablet that I’d set aside for e-waste collection, and the tools I used to do battery replacements on a couple of devices a while back, and let him at them.

He disassembled and reassembled the dead Nexus 5x that got stuck bootlooping two years ago. Plugged it in. Waited.

It actually powered on enough for us to get it into recovery mode!

Unfortunately I should have left it in fastboot mode, because now that I’ve downloaded an image to install, I can’t get it to power up again at all.

Posted on
by

I’ve been using Firefox for Android as my main mobile browser for a few weeks now. There are a lot of things I like about it. It works well overall. Unlike Chrome, it supports extensions, so I can install (for instance) Privacy Badger and HTTPS Everywhere. The share menu option includes the two most recent apps instead of just one. Things like that.

But there are a few things that I find incredibly frustrating:

  • PWAs aren’t as stable as Chrome.
  • Auto-fill is inconsistent and interacts badly with scrolling.
  • It’s slower than Chrome, though I’ve found that turning off web fonts helps a lot.
  • Private mode UI differs only by the color of the search bar, so whenever I use it, I have to double-check whether I’m actually in private mode or not.

Plus I miss a few Chrome UI features that just streamline common actions:

  • When clicking on the search bar, if you have a URL in the clipboard, Chrome offers to load that URL. (This is particularly helpful for opening email links in private mode.) (Firefox does this too now.)
  • Auto-fill an entire address form at once
  • Clear the last X minutes of history

On the PWA front: These are packaged web applications that can be “installed” locally and used offline, powered by whichever web browser you used to install them. When I switched browsers, I also reinstalled the PWAs I was using on my phone and tablet, switching them from Chrome-powered to Firefox-powered. These amount to a couple of Mastodon instances and Twitter. (I don’t want to install the full Twitter app on my phone so I’ll be less tempted to get caught in infinite scroll.)

On Firefox, Mastodon’s PWA frequently logs me out. Every other day at least. Sometimes it stops being able to load any new statuses, and I have to close the app entirely and re-open it to get back to normal. (Fortunately that’s fast.) Twitter…well, it worked for a couple of days, then it got into a redirect loop where it kept switching between the regular UI and the login screen. I considered reinstalling it through Chrome, but finally decided I was better off without Twitter on my phone anyway.

Despite these issues, I’m going to stick with mobile Firefox for now. We’re entering another period of near-monopoly in web browser engines, and it’s important to keep a viable alternative going to ensure that the future of the web isn’t built on a single stakeholder’s goals.

Posted on
by

I use extensive filters on Gmail to categorize mail the way I want. I pre-filter some things to look at later, prioritize some lists (like allergy or uptime alerts), and pre-categorize things that I may want to file away after looking at them.

The problem is, I can only change filters on the desktop site. When I’m reading on my phone, I need to remind myself not to archive or delete messages that I want to start filtering.

It occurred to me: I can label those messages “Change Filter.” I could even do it right away – there’s a “Manage labels” option on the Android app!

Nope!

I can’t add labels in the app, just change the download and notification settings for each.

So, website then…

Except I can’t get at the full Gmail website on my phone. Or my tablet. Google insists on showing a stripped-down mobile site, which has even fewer capabilities than the app.

I can’t fault them for starting with the mobile site. It is helpful to focus on the features that work best on small touchscreens, under-powered processors, and high-latency, low-bandwidth networks, and can be done by someone on the go, rather than someone sitting at a keyboard with a big screen and a mouse.

But if someone wants to use the functionality you’ve left out, and is willing to slog through the desktop site on their phone or tablet, you should at least let them get at it!

In this case I waited until I could log in on a desktop, then added the label. But not everyone with a phone has a desktop or a laptop. And as the balance keeps shifting towards phones as people’s primary internet access device, that’s going to be more and more common.

Posted on
by

Google has a new camera mode on its Pixel phones called Night Sight, for handling low-light conditions. The short version is that instead of taking a long exposure, it takes a series of short exposures and stacks them to avoid motion blur from hand movements (plus a lot of additional processing). The long version is fascinating.

My Pixel 2 already takes better low-light photos than I would have expected, but I couldn’t wait to try out the new feature when I learned about it. When the updated Camera app finally hit the Play Store, I had to give it a try.

Two high-rise office buildings at night.

This is adjusted slightly to keep the colors from being too light. And it actually isn’t the best example, as it turns out the nighttime city scene already has enough light for the existing HDR+ mode. I’m going to have to try it on some darker scenes somewhere, but it’s still pretty cool. After the cut I’m posting a version with the phone’s regular mode, and the unaltered Night Sight photo. You can see they’re pretty close, but the Night Sight version picks up a bit more of the color, and it’s a little brighter.

Continue reading →

Posted on
by

I recently dug out my old Samsung Galaxy S4 for some Android testing. I replaced it with a Nexus 5x last fall, and for the most part I love the newer phone, but there are a few things that I really miss about the S4.

  • The size is perfect. It’s literally as big as it can get and still be comfortable to use one-handed and fit in my pants pocket. The Nexus 5X is barely 1/8″ wider and 3/8″ taller, but it’s just enough that I can’t quite reach the whole screen with my thumb. I have to loosen my grip until it feels like I’m going to drop it, which means I’m extra motivated to keep it in the case, which makes it even bigger…
  • The Galaxy S4 display is polarized diagonally, so I can use it in landscape mode while wearing sunglasses. This is helpful for things like daytime GPS navigation. The Nexus 5X is not.
  • The volume buttons are positioned out of the way of the middle, making it easy to clip on a dashboard mount.

Those are three things that the Galaxy S4 does better (for me, anyway) than the Nexus 5X. They’re all form factor. Of course since giant smartphones are all the rage these days, good luck finding another one that’s just the right size for my hand.

Otherwise, I love the Nexus 5X’s display, the up-to-date Android OS without Samsung’s modifications (and knowing I’ll actually get security updates), the camera, the convenience of the fingerprint sensor, the speed, and just about everything else about it.

I wouldn’t go back. I considered setting up the S4 as a dedicated GPS until I realized that it wouldn’t be able to get traffic data without a SIM card. (Maps can store the actual maps offline now, and GPS works independently of cell service.)

But if Google releases their next Nexus device in a form factor just 3/8″ shorter, I’ll be tempted to upgrade early.