Everything went smoothly - but there are a few niggles you should be aware of. Some of these are Google's fault - they truly have contempt for their users - and some could be fixed by Lineage if there were sufficient demand.

I've mostly posted this list so that someone from XDA can tell me I'm an idiot and there's an easy fix for all of these issues.

Google Wallet. I knew this was unlikely to work. Even with Magisk's Deny List and the Universal SafetyNet Fix, I couldn't convince GPay to run. The "lack" of security also stopped the Barclaycard App (Error 00006) and one of my doctor's apps. Weirdly I could run all my other banking, credit card, and health apps.

The default webview doesn't support WebAuthN - so I couldn't use my Yubikey to set up BitWarden. I ended up side loading Firefox so that I could get it to work.

Flicking the 5T's side switch to silent doesn't activate "Do Not Disturb".

It is impossible to disable an inserted SIM card. The UI instructs you that the only option is to remove the card. That's a bit annoying (and battery draining).

Google killed native SIP calling. I now need to find a separate app for making and receiving VoIP calls. Weirdly, carrier VoWiFi works just fine.

Call recording works - but it isn't automatic. I have to remember to press a button. Not a show stopper, but a bit annoying.

Lineage doesn't use the latest Noto fonts. I know this because they don't display the Unicode Power Symbol. There are a few default fonts installed, and you can change between them - but there's no way to install your own fonts. Well, there's a command line Magisk module - but requires a reboot each time.

Themes are still a bit hit and miss. All the light themes have poor contrast on some UI elements (white icon on light backgrounds). The dark themes are OK, but then force most apps and websites into dark mode - which isn't always easy to change back.

I find the "jelly" overscroll animation annoying. The only way to disable it is to remove all animations - which makes any transitions really jerky.

Moving the clock to the centre of the shade leaves an gap on the left where it used to be.

No split windows. The launcher doesn't allow for split screen.

The notification panel sometimes goes behind the on screen navigation buttons.

PIN entry requires you to hit the submit button. Older versions of Android would unlock as soon as the correct PIN was typed. But Quick PIN Unlock is unsupported.

The AOSP keyboard refuses to run if any other keyboards are installed. It kept crashing, so I swapped to OpenBoard

Those are all fairly minor complaints. For daily use, Lineage's Android 13 runs just fine - especially considering this phone is 5¼ years old. The team at Lineage continually prove that older devices can be supported, despite the intransigence of most manufacturers.

If you know how to fix any of these problems, let me know in the comments.

Hello! Your new Nexus One phone has many cool and useful features. Learn more by clicking on the links to watch brief YouTube videos directly on your phone:

• Take pictures with your 5mpx camera and view them in your 3D Media Gallery. Learn more
• Get transcribed voicemails and cheap international calling with Google Voice. Learn more
• Sync your contacts, Facebook and email accounts with QuickContact. Learn more
• Get cool applications and games on Android Market. Learn more

You can find all these videos and more on the Nexus One playlist at youtube.com/googlenexusone.
Enjoy!
The Android Team at Google
Google, Inc.
1600 Amphitheatre Parkway
Mountain View, CA 94043

---

We sent you this one-time welcome message because you recently purchased an Android-powered phone

What's Going On?

Take a look at the bottom of the mail again...

We sent you this one-time welcome message because you recently purchased an Android-powered phone

I haven't recently purchased a new phone. I've had Android phones since early last year. What is different is that I recently hacked my HTC Hero and installed SenseHero 2.1. A modification which allows the ageing HTC Hero to run the very latest Android software.

What has obviously happened is that Google has seen me sign in to a "new" Android 2.1 phone and assumed that I've recently got a Nexus.

When You Assume...

There is a dangerous assumption - reflected in the email - that "phone with OS Z = phone with name Y". At a stroke, Google have confused their users and diluted their brand name(s).

Welcoming new or returning users is definitely a good move. But unless your communications are correctly targeted and accurate, you risk alienating rather than engaging.