Google Fi Notes

I moved over to using Google Fi about a month ago. It’s been great. This is a pile of notes about what I’ve tested, and what I’ve seen, along with tidbits that weren’t in the manual.

Google Fi Dialer codes:

xdathread, One engineer’s test,

Dialer code Dialer code (numeric) Function
FI SPR *#*#34777#*#* Use Sprint
FI TMO *#*#34866#*#* Use T-Mobile
FI NEXT *#*#346398#*#* Next carrier
FI AUTO *#*#342886#*#* Automatic carrier
FI INFO *#*#344636#*#* SIM/network info
FIX ME *#*#34963#*#* Network/configuration reset?

Google Fi email to sms gateway

Doesn’t exist.
Sending messages to the tmobile phonenumber@tmomail.net or the sprint phonenumber@messaging.sprintpcs.com doesn’t get a message to my phone.

This is a non-issue for me. It may be an issue for you.

Update :
Still Doesn’t exist. (11 Feb 2016)

There is now a claim a email to sms gateway does exist. Based on my testing, it appears to actually be an email to MMS gateway, and thus won’t work if you can’t retrieve MMS, aka, no data service, but do have voice and text. Also, doesn’t work with Hangouts SMS integration. So, uh, halfway, sorta?

Dealing with Exchange, Android Marshmellow, and Reoccuring Calendar Appointments

I’ve recently moved to using Android M on a Nexus 5x. I’ve connected to my employer’s Exchange server so I could see my work calendar on my cell phone.

The Problem:

My calendar is broken. A little bit. Some reoccurring appointments were showing up an hour off.

I figured out why. The timezone of the reoccurring appointment is being set based on the first occurrence of the appointment. The timezone is a fixed offset from UTC, and doesn’t change over the Daylight Saving Time shift.

The workaround:

Open the appointment in outlook. Edit the re-occurrence. Set the start date to be in the same DST zone as you presently are. The calendar on your phone will correct shortly thereafter.

I expect to have to fix all the re-occurring events after the next DST shift.

The Solution:

I don’t know. I hope somebody finds this bug and fixes it where ever it is.

Blackphone 2: 3 Months of experience

As many people now know, I sold my BlackPhone 2 recently. That happened for many reasons, and in this post, I will attempt to outline some of them.

First and foremost, the Black Phone 2 did exactly what it claimed on the label. This is, in it’s self, unusual. In this regard, I strongly recommend the BP2 to anybody who needs the facilities it advertises.

In the end, I didn’t need those facilities. But let me back up. Picking a security technology needs to be done in context of what you are trying to protect, and how.

I have a very specific threat model that I’m working with.

  • I use my phone to contain 2 factor authentication tokens ( TOTP to be specific.)
  • Wiping my phone will destroy those tokens, by design.
  • To integrate with my employer’s email/calendar system, they demand the ability to wipe my phone remotely.
  • But I use many two factor tokens on my phone, only a minority of which are my employer’s. I don’t wish to lose these because my phone gets wiped, for any reason.

Thus, the BlackPhone 2’s ‘spaces’ feature looked perfect. Attach my employers account to a ‘non-owner’ space, and thus, when a remote wipe command comes for my phone, the space is wiped, and not my whole phone. Place the two factor tokens that I wish to survive in a different space, and I get the best of both worlds.

This actually works.
Every time.
I tested it 3 times while I owned the BP2. It’s really quite impressive.

But with that feature space, comes some serious challenges.

I also own a Pebble Time. I really like this smart watch. It works great. But that’s a different review. The Pebble Time talks to your phone over Bluetooth, using an android app.

Android apps are constrained to the space in which they are installed. Bluetooth associations are also constrained to the space in which they are made. Thus, every time I switched away from the ‘work’ space, the connection to my pebble would drop and all notifications would stop.

Working as designed, but not as desired.

But I can install that app in all the spaces I’m using. Doing so then requires the pebble to associate to each one of those spaces, independently. The data shared to the pebble then varies by space. Not wrong, but darn inconvenient.

Of course, to make this work, for notifications, every app that I wanted to work ‘across spaces’ had to be installed in each one of those spaces separately. Which then required each one to maintain it’s state database separately. Which then implied independent communication to the cloud providers.

So, in exchange for spaces, I ended up burning 2-3x more data, and with it, 2-3x times more battery.

But I wasn’t planning on needing to move much data. The BlackPhone 2 comes with a microSD slot. I’ll put a big microSD card in it and cache what I want to use.

  1. As documented, the microSD card isn’t secure and isn’t encrypted.
  2. An awful lot of applications will use the microSD card in the ‘owner’ space, but not in a non-owner space. The one that got me was Google Play Music. This seems to be an android thing, not a BlackPhone 2 thing.

So, use of the microSD for bulk data was largely a bust.

Which brings me to the part that pushed me over the edge. The size.

3 months with the BP2 showed me that I’m a 5.2 inch max cell phone person. I fly my phone single handed. Get much over that and I can’t hit the buttons with my thumb. The BP2 is only a half inch larger, but that’s a half inch too much for me.

So, I got a Nexus 5x, Google Fi, and a Yubikey-neo. This set of hardware solves my current threat model, but that’s a different post.

Silent Circle builds a solid product that does what it claims on the label. That’s rare these days, and I wish them the best of luck. I’ll continue watching their products, and I will continue to use Silent Phone.

I’ve sold my BP2 to a friend. I hope to hear how it goes for him.