## Nexus 5x: Second Impressions

Here's a follow-up to last week's Nexus 5x: First Impressions post.

## What I've liked so far

Basically, it's all the same stuff that impressed me at first—mainly the camera and the fingerprint sensor.

## What's bothered me so far

While this list may look long, it doesn't mean I'm not enjoying using the phone, but I do have some nitpicks, so here they are:

1. Even though the double-tap on the power button launches up the camera no matter where you are (great!), you'd think (as it did on the Moto X after a double-twist) that the phone being already unlocked would return you to an unlocked state after you launch up the camera. Nope. Whether the phone was unlocked or not before you launch the camera with the power button double-tap, it will be relocked after you're done with the camera. Sure, you can unlock it again quickly using the fingerprint sensor, but in terms of usability and user expectations, there's no reason launching up the camera should change the phone from an unlocked state to a locked state.
2. Google will prompt you to enable Google Now cards and Google Now on Tap. That's fine. That's what I expect them to do. But even after you click to enable them and then decide to disable them again, there will still be a prompt, when you hold the home button, to enable them. Advertise once, please. Once I've seen it, I don't need to see it again. I opted out. Don't bug me.
3. If you plug your Nexus 5x in to a computer, it will always default to charging only and not to transferring files. There is no way to change this default. The behavior is even more bothersome if your main computer is a Mac, because Android File Transfer (the Mac program you have to use to transfer files to/from Android) will automatically launch up when a phone is plugged in, but since the phone isn't set to transfer files, Android File Transfer will think the phone is just locked and give you an error message, which means you have to temporarily (again, no way to permanently change this setting) set the phone to transfer files and then re-launch Android File Transfer.
4. When you first set up the phone, it asks if you want to require a password every time the phone boots up. Two issues with this—if you select to require a password, there's no way to change it back without factory resetting your phone; and even if you select not to require the password, it will still require a password!
5. Apps aren't all updated to work with Marshmallow yet. Not exactly the fault of the phone, but just something to keep in mind. I tried using Firefox with Adblock. and it would constantly cause the phone to reboot (Chrome and Opera operate just fine). VolumeNext doesn't work to skip forward with a regular auxiliary cable (not headphones) but can skip backwards—didn't have that issue with lollipop. Those are just two examples. There will probably be others for other users. After a while, the app developers will update their apps to be more compatible with Marshmallow.
6. The camera aspect ratio defaults to 4:3 instead of 16:9. The phone is advertised at having a 12 megapixel camera, but if you change it to 16:9, it drops to 8 megapixels. It may be fine to have 4:3 for Instagram, but when you look at your photos in the Photos app, there will be black bars (because the phone itself has closer to a 16:9 aspect ratio). I've changed it to 16:9, and it seems to be much better. I don't believe the drop in megapixels adversely affects the quality of the photos.

## Do I still recommend this phone?

Hell, yes! As I mentioned before, those are tiny nitpicks people should be aware of, but the day-to-day use of the phone is great. Still a bit too large for my tastes, but there is no 4.3-inch screen on a new Nexus phone, so it's at least smaller than the 6p.

## Nexus 5x: First Impressions

Two years ago, I posted up Moto X: First Impressions. I just got the new Nexus 5x, and I thought I'd post my first impressions of that phone as well.

## The Good

• The camera photos seem crisp and the camera focuses quickly. I haven't had a chance to thoroughly test it in low light, but I've done a few indoor shots, and they seem immensely better than what I could capture on my (albeit two-year-old) Moto X.
• The fingerprint sensor is amazing. It is indeed fast—almost instantaneous. And I find its placement on the back of the phone to be very convenient. Even though the phone is tall, the fingerprint sensor isn't toward the top of the phone... it's more toward the middle, so I don't have to reach up that high to get it. It's close to where my index finger would naturally rest. I was also able to register two of my index fingers and also two of my spouse's, so either of us can use the phone without always having to enter a password. The other up side to this is, since I don't need the password often (not at all, so far), I can make it a fairly complex one. When you have to enter a password/pin/pattern ten or twenty times a day, it's tempting to make it short and simple.
• The screen looks good. I don't know anything about resolution numbers and pixels per inch or types of displays, but it looks good to me. Not too much glare. Not too much color saturation (or too little). Video looks good. I also like that the display brightness can go low. The lowest brightness on my old Moto X was still too bright in a dark room (so I ended up having to download a "night mode" app for my old phone).
• Double-tap power button camera activation is a good call. I know Google was considering implementing the double-twist to activate the camera, the feature that debuted with my old Moto X, and I'm glad they went with a double-tap of the power button instead. The double-twist was an awesome feature, but the Moto X was a nice tiny-sized phone you could easily hold in one hand and twist around without worrying about dropping. Even though the Nexus 5x is smaller than the Nexus 6p, the 5x is still enormous, and so having a double-twist action ups the risk on dropping the phone.
• The physical build is good. I know a lot of people like to bag on plastic (vs. metal), but the plastic of the Nexus 5x feels and looks nice. The phone still has a premium feel to it. Even though visually it looks as if the rear camera bulges out the back, the phone is still able to sit flat on a table without wobbling.
• Power and volume buttons are well placed. The phone, as I mentioned before, is tall. So it's good the power and volume buttons, although above the middle, are closer to the middle than the top of the phone, making them all easy to reach (no, I don't have giant man-hands).

## The Okay

• One front speaker is fine. I'd love two front-facing stereo speakers. Since every other phone I've had has had one rear-facing speaker, even having only one front-facing mono speaker is a huge upgrade for me. I know some audiophiles out there will be disappointed in this. The volume is adequate. If you turn the volume up, you can hear things fine, but you won't ever have to worry about turning the volume too high. Having two visual speakers even though only one is functional is a terrible idea, especially since the speaker design attracts fuzz and lint.
• The camera app is not terrible. A lot of reviews have been down on the Google Camera app as being too simplified and barebones. I'm coming from the Moto X, which has basically nothing on the screen, and you tap anywhere on the screen to take a picture, so the controls for the Google Camera seem almost overwhelming to me. I've always felt with Android that you can get a more sophisticated camera app from the Google Play Store if that stuff matters to you. I will say the noises that the camera app emits when you switch to video or start a video or take a picture are annoying.
• 32 GB is all right, but 64 GB would be better. One of the reasons I was tempted by the Moto X Pure is its microSD expansion. The Nexus 5x has only internal flash storage, and the max is 32 GB. To be honest, if 64 GB was an option, I don't know that I would have gotten it, but I know a lot of Android fans love to put as much crap as they can on their phones. I had 16 GB on my old Moto X, so 32 GB seems like a wonderland of space.

• The Google Now launcher is horrible. This is probably more of a Marshmallow thing than a Nexus 5x thing, but I hate the new Google Now launcher. The icons are enormous. There is no longer the press and move up action to launch something (which, in the past, I was able to link to Opera instead of Google Now). Not only that, but you can't have any screens to the left of the home screen. By default, there's only one home screen and any home screens you add all have to be to the right of it. So I've opted to replace the Google Now launcher with my old buddy, the Nova Launcher. Now my icons are the right size, and I can configure my screens (and the home button gestures) however I want.
• The phone is too big. Yes, I've mentioned this several times, but it really is bad. My spouse assures me I'll get used to the size, but for now (first impressions, remember?) it's extremely annoying. I take public transit, which means I'm often standing with only one hand available. The phone is definitely too big for one-handed use (unless you have giant man-hands). Unfortunately, this is just the direction phones are going. I was debating between the Moto X Pure and the Nexus phones, and of the three (Pure, 5x, 6p), the 5x is the smallest. Nevertheless, it's a bit too big for my tastes.
• The accessories it comes with are meager. You get a standard power adapter and USB-C-to-USB-C cable. You also get a little SIM card ejector tool. That's pretty much it. I was hoping for a USB-C-to-USB-A or USB-C-to-microUSB adapter. USB-C may be the "new thing," but it's far away from mass adoption, very far away. I also found it odd that no headphones were included. Every Android phone I've gotten in the past has come with a pair of crappy headphones. I know the audiophiles out there usually ditch the crappy headphones anyway, but I'm not an audiophile. I appreciate an included pair of headphones. Could be just me.

## The Untested

• Phone call quality. Some people on the Android Forums complained about the phone quality being terrible. I haven't had a chance to see if that's really the case.
• Battery life. I've had the phone one day. And I've been charging it a lot and not using it very extensively, so it's really hard for me to say how the battery life is at this point.

## Summary of first impressions

No real big surprises. I'd read a lot of reviews of the phone before getting it. The three big draws for me were the fingerprint sensor, the better camera, and the timely OTA updates from Google. I guess eventually I get used to using an enormous phone...

## Useless Backstory: Moto X to Nexus 5x

My by far favorite Android phone since 2009 has been the Moto X 2013. Indeed, if it were not for its subpar camera, I would say it is, even now, still the best Android phone. The Moto X 2013 had innovative new features (ones that—had Apple released them in the iPhone—iPhone fans would be gushing about as evidence of Apple pushing new boundaries and being very user-centered in its design... since Motorola's marketing department isn't as good, most people just ignored these features): ambient display, double-twist to activate camera, OK Google Now, etc.

That said, I find myself using my phone's camera more and more often and being very sad about especially the low-light shots from the Moto X 2013. I've also found the fingerprint sensor on the new iOS devices to be pretty cool, and the reviews said the sensor on the Nexus 5x is even more responsive. I also find it a bit awkward to press my thumb on the home button of an iOS device to unlock it. I like the idea of the sensor being on the back of the phone where your index finger might naturally rest when picking up the phone.

## More Useless Backstory: Fed Ex Annoyances

I was dumb and decided to have Google deliver to my apartment instead of my workplace. So Fed Ex attempted a delivery when I wasn't home, and then I tried to get it over the weekend and called Fed Ex, but the customer service representative, whom I could barely understand, said the facility was closed over the weekend, so I couldn't pick it up in person. Oddly, I couldn't redirect the destination either—something I'm pretty sure I've done in the past. When I did happen to be home the second time, the Fed Ex delivery person said, "This is the second time I've tried to deliver this," as if he were scolding me. Seriously? I'm supposed to be always home? What the...? I didn't say anything smarmy back to him, though, because I was excited to check out the new phone.

## The Unboxing: Featuring my bad photography skills

Yes, I like having a good camera. No, I'm a terrible photographer. Most of these shots I took with a shaky hand using my old Moto X 2013. A few of the later ones I took using an iPad Mini.

It comes in a very cute small square box.

Once you get the cover off, the front of the box has a logo that's supposed to be an X, I suppose.

You can open the box without scissors. It's taped down on only one side of the square.

LG took a cue from IKEA and put in some cryptic wordless instructions. The phone itself comes in a translucent sleeve, which is really just for show (my Moto X 2013 came with a screen protector on it, which I used for two full years and never had to buy a third-party protector to replace it with).

Then, there's the USB-C cable and the charger.

Beneath the phone is a playing card that tells you you get a 90-day trial for Google Play Music. There's also a small Safety + Warranty booklet.

The tiny, shiny circle with a pin at the end lets you pop up the SIM card holder from the phone. I was also able to use this same one to pop out the SIM card holder for my old Moto X 2013.

Another random shot of the cable and charger.

Here is the Nexus 5x next to my Moto X 2013. The Nexus 5x is enormous compared to my old phone, which I'm a bit sad about. I really wanted a new Nexus phone, and the Nexus 5x is smaller than the 6p, so I opted for the 5x, but it's still huge!

I didn't do any actual measurements, but the phone thickness seems okay, It's more flat than curved but about the same thickness as the Moto X 2013.

Another gratuitous "Why is this phone so big?!" shot.

I haven't had a ton of time to play around with the phone yet, but the camera seems good (I haven't tried it in low light yet, though), and the fingerprint sensor is indeed fast in terms of responsiveness.

## Some Background

I did my first proper unroot of my Moto X 2013 recently, and I learned something interesting in the process. In the past, when I've rooted and unrooted my Moto X 2013, I'd request/download the factory image straight from the Motorola website and restore that back.

Recently, though, I tried to take an OTA (over-the-air) update from Motorola, and it would download the update, try to install the update, and then error out. I'd then get a message about how the update was unsuccessful. I tried reflashing the recovery and the system. Reflashing everything, clearing the cache, clearing the user data. The OTA update (from Motorola, mind you) did not like the factory image from Motorola's website.

The only way I could get it to work (big shoutout to mastarifla from the XDA forums for the tip) was downloading a factory image from a third-party website. Then the OTA update (from Motorola) liked it and installed the update successfully. Go figure.

Some of you all may be skeptical about downloading "factory images" frmo third-party websites, and that's fine, but this was the only one that I could get an official OTA from Motorola to install on properly. Your mileage may vary.

Before you begin, make sure you do the following:

1. Back up any important data—either to the Cloud or your computer's hard drive or both. This includes but isn't limited to photos, music, apps, bookmarks.
2. Download the appropriate moto-fastboot files for your operating system from the first post in this thread. For some reason, the regular fastboot can't do some of the larger files, so a special moto-fastboot has to be used.

## Note for Windows users

I don't use Windows, but I've heard that you can use RSD Lite to restore the phone instead of running the commands below. Unfortunately, I can't walk you through those steps. You can find details here.

## Actual Steps

I'm basing these off of what I did on Mac OS X. There's a terminal in Windows and one in Linux, too, so similar principles will apply, but the exact steps may be slightly different.

1. Once the factory build is downloaded, double-click it to unzip it.
2. Move the unzipped moto-fastboot file into the unzipped folder. For Macs, that would be moto-fastboot-x64.
3. Open up the /Applications/Utilities/Terminal.app and type in
cd
with a space at the end
4. Drag the factory build unzipped folder to the terminal, and then hit Enter. Your terminal should now be focused on that directory.
5. With your phone unplugged, hold down the power button until it prompts you to power off. Then power it off when prompted.
6. While holding the volume-down key, tap the power button and wait for it to boot up. It should boot into something called "fastboot mode" with a black screen and some colored text.
7. Keeping the phone in fastboot mode, connect it to your computer via USB.
8. Run the following commands (note: it may be better to copy and paste them one by one than to do them all at once in a script or to retype them manually).
./moto-fastboot-osx64 erase cache
./moto-fastboot-osx64 erase userdata
./moto-fastboot-osx64 flash partition gpt.bin
./moto-fastboot-osx64 flash motoboot motoboot.img
./moto-fastboot-osx64 flash logo logo.bin
./moto-fastboot-osx64 flash motoboot motoboot.img
./moto-fastboot-osx64 flash logo logo.bin
./moto-fastboot-osx64 flash boot boot.img
./moto-fastboot-osx64 flash recovery recovery.img
./moto-fastboot-osx64 flash system system.img
./moto-fastboot-osx64 flash modem NON-HLOS.bin
./moto-fastboot-osx64 erase modemst1
./moto-fastboot-osx64 erase modemst2
./moto-fastboot-osx64 flash fsg fsg.mbn
./moto-fastboot-osx64 erase customize
./moto-fastboot-osx64 erase clogo
./moto-fastboot-osx64 oem fb_mode_clear

It's possible that erasing userdata may not be necessary. More details in XT1053 222.27.5 Stagefright OTA Update Guide.

After that, when you reboot your Moto X, it should be back to factory settings and able to take OTA updates.

## Responses to Danielle Lan’s Quora post on the high cost of living in the Bay Area

I recently saw someone tweet out a link to Danielle Lan's answer to a question on Quora about cost of living in the Bay Area.

Basically, Danielle Lan confirms that the asker's friend declaring "his life is shitty" is correct, and she says "I'm living his life, except I'm a DINK (double income no kids) and it's still terrible."

Most of the responses to her post are the usual awful comments that you're not supposed to read when people say "Don't read the comments"—everything from misreading her "530K house" to be "350K house" and then chastising her about her mortgage payments, to accusing her of being a gold-digging leech of her husband. I was impressed with the calm, measured replies she had to these trolls. I would have just ignored them, but she was careful to explain all of her financial circumstances and divulged a lot about her family situation and debt... a lot more than most people are willing to share in a public forum.

Even though I felt some sympathy for her—since people were piling on and nitpicking her finances and giving her lots of unsolicited (and unnecessary) financial advice—I wouldn't exactly called putting away $300-500 in savings per month "still terrible." That's about$5000 in savings per year after car payments, mortgage payments, student loans, and other expenses. I'd say that's not bad. Now, granted, I get her general point: if you're making almost six figures and your husband is making well into the six figures, you would be living in the lap of luxury in almost any other part of the country, and that's not true in the Bay Area now.

I would like to add a piece that was missing, even in all the troll replies to her original comment: Most people in the Bay Area do not make anywhere near the amount of money she and her husband make..

So, yes, I absolutely feel bad for her that her student loans are massive. I feel bad that she and her husband can save "only" \$300-500 per month. I feel bad that they thought they'd be rich with the salaries they have but they're "only" middle class in the Bay Area. At the same time, they're a technical writer and a software engineer.

My spouse and I are educators and our combined salary is probably less than what her husband makes. And we probably make more than even a lot of other people in the Bay Area who work minimum-wage jobs.

I don't judge her for feeling frustrated. And this post is not a poor-is-me or oppression olympics entry. It's just odd that in all the responses to her Quora post (people were telling her to sell her cars for cheaper ones, to move away from her friends and family, to telecommute even when her employer won't let her), very few mentioned anything about the non-techies and their non-techie salaries, and how do those people manage?

The Bay Area is an absolutely wonderful place to live, but it is becoming far more expensive even than it's been in the past. It's hard on a lot of techies who thought they'd be super-rich. But it's even harder on most of the folks out here, who aren't pulling those techie salaries.

SFUSD scrambling to fill classrooms amid teacher shortage

## Why Script Importing into Photos?

Recently, Apple deprecated iPhoto on the Mac in favor of a new iPhoto-like app called Photos. The nice thing about iPhoto was that you could drag a bunch of photos onto the iPhoto icon, and those photos would automatically import as a new album. I've found a bit of bugginess with Photos (perhaps it will be fixed in newer versions). Sometimes dragging photos into the app won't do anything. Sometimes it will launch up a preview and then ask to import. Other times it will just import.

I use Dropbox's camera upload function to have the pictures from my Android phone automatically upload to Dropbox's servers and then down to my Mac.

## The Automator Script

I made an Automator .app with a Run AppleScript action that runs the following script (substitute in your own path and username to whatever folder you want to import):

set extensionsList to {"jpg", "png", "tiff"}
tell application "Finder" to set theFiles to every file of importFolder whose name extension is in extensionsList

set timeNow to time string of (current date)
set today to date string of (current date)
set albumName to today & " " & timeNow
set imageList to {}
repeat with i from 1 to number of items in theFiles
set this_item to item i of theFiles as alias
set the end of imageList to this_item
end repeat

tell application "Photos"
activate
delay 10
import imageList into (make new album named albumName) skip check duplicates no end tell

tell application "Finder"
delete imageList
end tell

## Acknowledgements

The basis for this script (with my own tweaks, of course) is how to easily import images into new Photos.app.

## Tweaks in This Script

The main differences in my version of the script are:

• Specification of the folder ahead of time instead of a prompt for the user to choose a folder
• No check that there are images in the folder (Photos itself will tell you there's nothing to import if the Dropbox folder is empty).
• Album name is based only on the date and time instead of prompting for a name and then appending a date and time.
• Waiting longer after launching ("activat[ing]") Photos before doing the import. I found (on my non-SSD hard drive) that 2 seconds would make the Automator .app crash before importing.
• Deleting (moving to the Trash, actually) the imported folders when done.

## Pure Kubuntu 15.04

These removal commands were created based on what Ubuntu, Xubuntu, etc. packages were added to a default Kubuntu 15.04 installation. It's possible that the commands might remove some other packages you have since added to the default and want to keep. If that's the case, keep track of which packages those are and reinstall them. Theoretically, your settings should still be there. I am not responsible for any damage you do to your *buntu installation. If you're worried about breaking anything, do a full back up of your *buntu installation.

Remove Ubuntu
Paste this command into the terminal.

Remove Xubuntu
Paste this command into the terminal.

Remove Lubuntu
Paste this command into the terminal.

Remove Edubuntu
Paste this command into the terminal.

## Installing a custom rom on an unlocked Moto X 2013

I've been rooting and installing custom roms on Android phones since 2009. In general, it's been a fairly standard procedure. With the Moto X 2013 (and this may apply to the 2014 as well—I don't know—I can vouch only for the 2013), the procedure is slightly different.

Get Motorola's fastboot
Get TWRP
Get the custom rom you want
Flash TWRP recovery to phone
Flashing the rom (and Google Apps)

Go to the Motorola website to request to unlock your phone's bootloader. If you got a phone not locked to a carrier, there should be no issue with this.

The first time you unlock your bootloader, it will erase everything on your phone. Back up important stuff before you unlock the bootloader!

## Get Motorola's fastboot

I'm not sure why, but apparently Motorola has its own fastboot, so you're supposed to use that one instead of the regular fastboot you'd find in the Android SDK (Google has also switched things up so if you go to get the Android SDK, you'll get an Android IDE app instead of just the raw files).

The weird thing is it's very difficult to find this Moto Fastboot anywhere on the Motorola website. I've found it only via third parties.

Here you can find a link to the Mac version.

And here you can find a link to the Windows version.

I wasn't able to track down Linux versions, but they supposedly exist.

## Get TWRP

Next, you want to download the TWRP (Team Win Recovery Project) recovery for the Moto X 2013 (codenamed ghost). You can find the latest version on the TWRP website.

## Get the custom rom you want

For this example, I'm going to recommend the Nexus Experience, but you can pick whatever rom you want. Unless you know you don't want Google Apps, be sure to download not just the rom but also the Google Apps .zip.

So one file should look something like Android5.1.1_NX_R9.4_MotoX2013.zip and another something like NX-GAPPS_L_Release3.3_Full.zip.

Plug your phone into your computer, and then copy those two files to the top-level /sdcard directory on your phone.

## Flash TWRP recovery to phone

I'm sure there's a Windows equivalent for this using DOS, but I've done this only on a Mac, so I'm not 100% sure on the Windows procedure.

For Mac, put the TWRP file (something like twrp-2.8.6.0-ghost.img) in the same directory as your moto-fastboot-osx64 file (may be slightly different for Windows and Linux users, of course). For simplicity's sake, rename the TWRP file to be twrp.img.

Turn your Moto X 2013 off. Unplug it from your computer. Then, while holding the volume-down button down, press the power button. Don't let go of the volume-down button until your phone boots into fastboot mode.

In the Terminal.app (similar but different for Windows and Linux), navigate to the directory where your moto fastboot and twrp .img files are. If you don't know how to do that, type cd in the terminal (with a space after it), and then drag the folder over to the terminal. Then hit Enter.

Then, run the commands

./moto-fastboot-osx64 flash recovery twrp.img

## Flashing the rom (and Google Apps)

You should still be at the fastboot screen, press the volume-down button once to highlight Recovery, and then press the volume-up button once to select it.

You should then see the teamwin logo.

After that, you'll get some touch-screen options.

First, select Wipe to wipe your current installation (you already backed up before unlocking the bootloader, right?). Then do a swipe to factory reset.

Once you're done, hit the back button to go back to the main menu. Next, select Install. Find your main rom (e.g., Android5.1.1_NX_R9.4_MotoX2013.zip) and flash that.

Go back to Install and flash Google Apps if you want (e.g., NX-GAPPS_L_Release3.3_Full.zip). If you don't know if you want Google Apps, flash it, just to be safe.

Then, go back to the main menu and select Reboot and then System.

It may take a while for your rom to boot up the first time, but then you're all set to use your custom rooted rom!

## Pure Ubuntu 15.04

These removal commands were created based on what Kubuntu, Xubuntu, etc. packages were added to a default Ubuntu 15.04 installation. It's possible that the commands might remove some other packages you have since added to the default and want to keep. If that's the case, keep track of which packages those are and reinstall them. Theoretically, your settings should still be there. I am not responsible for any damage you do to your *buntu installation. If you're worried about breaking anything, do a full back up of your *buntu installation.

Remove Kubuntu
Paste this command into the terminal.

Remove Xubuntu
Paste this command into the terminal.

sudo apt-get remove abiword abiword-common abiword-plugin-grammar abiword-plugin-mathview apt-offline blueman brltty-x11 catfish desktop-base espeak exo-utils fonts-lyx gawk gigolo gimp gimp-data gir1.2-gconf-2.0 gmusicbrowser gnome-desktop-data gnome-icon-theme gnome-icon-theme-symbolic gnome-system-tools gnumeric gnumeric-common gnumeric-doc greybird-gtk-theme gstreamer1.0-libav gtk-theme-config hddtemp i965-va-driver inxi libabiword-3.0 libamd2.3.1 libavcodec56 libavformat56 libavresample2 libavutil54 libbabl-0.1-0 libblas-common libblas3 libcairo-perl libcamd2.3.1 libccolamd2.8.0 libchamplain-0.12-0 libchamplain-gtk-0.12-0 libcholmod2.1.2 libdigest-crc-perl libencode-locale-perl libexo-1-0 libexo-common libexo-helpers libfile-listing-perl libfont-afm-perl libgarcon-1-0 libgarcon-common libgdome2-0 libgdome2-cpp-smart0c2a libgegl-0.2-0 libgfortran3 libgimp2.0 libglade2-0 libglib-perl libgoffice-0.10-10 libgoffice-0.10-10-common libgsf-1-114 libgsf-1-common libgsm1 libgstreamer-perl libgtk2-notify-perl libgtk2-perl libgtk2-trayicon-perl libgtkmathview0c2a libgtkspell0 libhtml-form-perl libhtml-format-perl libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl libhttp-cookies-perl libhttp-daemon-perl libhttp-date-perl libhttp-message-perl libhttp-negotiate-perl libilmbase6 libintl-perl libio-html-perl libjpeg-progs libjpeg-turbo-progs libkeybinder0 liblapack3 liblink-grammar4 libloudmouth1-0 liblwp-mediatypes-perl liblwp-protocol-https-perl libmp3lame0 libnet-dbus-perl libnet-http-perl liboobs-1-5 libopenexr6 libopenjpeg5 libopus0 libotr5 libots0 libpango-perl libschroedinger-1.0-0 libsdl1.2debian libsigsegv2 libtagc0 libthunarx-2-0 libtidy-0.99-0 libtie-ixhash-perl libtumbler-1-0 libumfpack5.6.2 libunique-1.0-0 libva1 libvdpau1 libvte-common libvte9 libwnck-common libwnck22 libwv-1.2-4 libwww-perl libwww-robotrules-perl libx264-142 libxfce4ui-1-0 libxfce4ui-2-0 libxfce4ui-common libxfce4ui-utils libxfce4util-bin libxfce4util-common libxfce4util7 libxfcegui4-4 libxfconf-0-2 libxml-parser-perl libxml-twig-perl libxml-xpathengine-perl libxvidcore4 light-locker light-locker-settings lightdm-gtk-greeter lightdm-gtk-greeter-settings link-grammar-dictionaries-en lm-sensors menulibre mesa-utils mousepad mugshot numix-gtk-theme orage parole pastebinit pavucontrol pidgin pidgin-data pidgin-libnotify pidgin-otr plymouth-theme-xubuntu-logo plymouth-theme-xubuntu-text python-defusedxml python-gtk2 python-magic python-psutil python-soappy python-wstools python3-psutil ristretto shimmer-themes system-tools-backends thunar thunar-archive-plugin thunar-data thunar-media-tags-plugin thunar-volman tumbler tumbler-common va-driver-all vdpau-va-driver xfburn xfce4-appfinder xfce4-cpugraph-plugin xfce4-dict xfce4-indicator-plugin xfce4-mailwatch-plugin xfce4-netload-plugin xfce4-notes xfce4-notes-plugin xfce4-notifyd xfce4-panel xfce4-places-plugin xfce4-power-manager xfce4-power-manager-data xfce4-power-manager-plugins xfce4-quicklauncher-plugin xfce4-screenshooter xfce4-session xfce4-settings xfce4-systemload-plugin xfce4-taskmanager xfce4-terminal xfce4-verve-plugin xfce4-volumed xfce4-weather-plugin xfce4-whiskermenu-plugin xfce4-xkb-plugin xfconf xfdesktop4 xfdesktop4-data xfwm4 xscreensaver xscreensaver-data xubuntu-artwork xubuntu-community-wallpapers xubuntu-core xubuntu-default-settings xubuntu-desktop xubuntu-docs xubuntu-icon-theme xubuntu-wallpapers && sudo apt-get install ubuntu-desktop

Remove Lubuntu
Paste this command into the terminal.

Remove Edubuntu
Paste this command into the terminal.

## Angry Asian What?

I don't know how well these two folks are known outside the AAPI community, but I've been a big fan of both Lela Lee (creator of Angry Little Girls) and Phil Yu (a.k.a. Angry Asian Man) for years.

In the past couple of days, there's been a bit of a dust-up between the two of them regarding trademarks. If you believe Phil Yu's account, he's a victim being attacked by Lela Lee even though they've been "friends" and "collegial" with each other for years. If you believe Lela Lee's account, he has been stealing her stuff forever and now that he's gone from hobbyist to career blogger, he's now a threat to her trademark.

I can honestly see both sides of this.

## In defense of Lela Lee

On the one hand, Lela Lee's lawyers are probably advising that if she doesn't aggressively defend her trademark, she may lose it. And she probably didn't think Phil was even thinking trademarks until he actually tried to trademark Angry Asian Man and then heard back from the USPTO that it was too similar to her patent.

## In defense of Phil Yu

On the other hand, Phil Yu does have a good point that she has not been telling him for years "Hey, you're infringing on my trademark and need to change your name." They have, in fact, been collegial professionally (if not actual friends). To have this drop on him with lawyers and stuff may seem to come out of the blue for him.

## In defense of Lela Lee

That said, even in his own account of things...

• He does seem to take unnecessarily long to get back to her on stuff.
• Saying to her "I am honestly taking your advice seriously, and have been actively researching what it would take to gradually transition the name of my brand. It won't be easy, and it's going to take a while, but it's the right move in the long run" does essentially say he is going to transition, even though he contends "at no point in this message do I ever agree to change the name." Uh, saying it's the right move in the long run pretty much says to me you're going to transition, even if not right away.
• If you try to trademark Angry Asian Man and then USPTO tells you it's too similar to Angry Little Asian Girl, the USPTO may, in fact, be wrong, but that would certainly raise my legal/business alarms if I were Lela Lee, not because I'd necessarily think Phil Yu was trying to get in on my turf, but because I'd be worried that the USPTO may still consider it a dilution of my brand.
• In the correspondence Phil Yu posts from Lela Lee, she actually seems to be offering a lot of help in terms of trying to help him transition—certainly a lot more than she's legally obligated to do (which is zero)—even though he doesn't like any of the names she suggests.

I know Phil Yu has a lot invested in Angry Asian Man, but if he does feel it's best to transition out in the long term, he can transition out, and his loyal fanbase will go along with him (I certainly will). If he decides to call himself "Pissed Off Asian Dude" or "Not Really Angry But Outraged About Racism Guy," I'll just link to that blog and follow that blog on Facebook and whatnot. Check out this list of Bands Forced to Change Their Names. The Verve, apparently, dodged a lawsuit by changing its name from Verve to The Verve.

## In defense of Phil Yu

Okay. I get that Lela Lee's lawyers are probably telling her to defend her trademark aggressively. So why get out the personal attacks about Phil Yu being "a Korean boy prince who was probably doted on by his parents"? Why not just say "I like you, but this is what my lawyers are telling me to do"? Do the good cop, bad cop. Be the good cop. Let your lawyers be the bad cop.

Also, really, USPTO—Angry Little Asian Girls and Angry Asian Man are easily confused? Seriously? One is a series of cute and clever (but angry) cartoons. Another is a series of blog posts about current events. One has a cartoon drawing as a logo. Another has a photo of a G.I. Joe action figure as the mascot.

## What I'd like to see happen

I don't know Lela Lee or Phil Yu, either in real life or virtually. I'm a fan of both and have been following both for years. I like the work they do, but I don't know if they're nice people or jerks. I honestly think this is a terrible misunderstanding, and I'd like to see both parties try to work it out with the USPTO that the two names are distinct. If not, I guess Phil Yu should change the name and take his followers with him. And then I think Lela Lee should give Phil a huge apology... not that they'd ever really be on speaking terms again, but it'd be at least some kind of gesture of good will.

Honestly, I've been Psychocats for years, actually about as long as Phil Yu has been Angry Asian Man. If The Psycho Cats (some band, apparently?) successfully made a legal case that I was infringing on their trademark and diluting their brand, I honestly don't give a rat's posterior, and I would take my Ubuntu fans (and anyone else who reads this blog) and pick a different name. I'd be pissed. Sure, I'd be pissed. I would think the USPTO is batty (which is common knowledge but hopefully will change in the future), but I'd do it. I sure as hell would wait a lot longer than 30 days to relinquish control of the domain name, though, because that's traffic.

I hope this resolves itself soon. As one commenter on Lela Lee's site said, it's like Mom and Dad are fighting. Stay angry, you two, but don't stay angry at each other... I hope.