Advertisements

I am trying to figure out the connection between all these, a mention of “Android Telephony” and Nexus devices within Chromium OS code.

This morning, I came across a very interesting piece of code in Chromium OS. As I have said many times before, I am not a developer, and I might be making stupid assumptions here. So, with that, here is the commit log:

Advertisements

Create a nightly telephony test suite.

Create a new test suite, and add the appropriate control files.

Also add a new data only test.

Here is the breakdown of what to check:

– Each control file needs to have a carrier:xxx

– carrier:att

– carrier:sprint

– carrier:tmobile

– carrier:verizon

– These must match exactly as above

– Each control file should have the suite for the nightly

test as an attribute:

– suite:android_telephony_nightly_att

– suite:android_telephony_nightly_spt

– suite:android_telephony_nightly_tmo

– suite:android_telephony_nightly_vzw

– These must match exactly as above.

– The TMO and ATT Basic files are also run for the Nexus

nightly tests since there is no Nexus campaign for those

networks.

– Additional dependencies are use to make sure the correct

features are run on supported phones:

– No additional dependencies: all phones

– telephony:conf: all phones except Shamu

– telephony:cep: Shamu only

– telephony:vt: Marlin/Sailfish only

– telephony:data, Volantisg

– These will need to be added as labels to the appropriate

test stations in cautotest.

Now, there are a few interesting things to note here:

ACTS mentioned here is Android Comms Test Suite. It is a lightweight Python-based automation tool set that is used to perform automated testing of current and upcoming Android devices.

Android Telephony Provides APIs for monitoring the basic phone information, such as the network type and connection state, plus utilities for manipulating phone number strings.

There are mentions of all the major US carriers.

They are testing connections using all these carriers, an automated test using ACTS.

Nexus devices and Pixel devices are being used for these tests.

We have had Chromebooks with SIM card slots in the past. It may not be surprising to see if Google is testing newer Chromebooks with SIM card slots and 4G data connectivity. That theory however does not explain the presence of Nexus and Pixel devices there.

Back at I/O 2014 Google showed off notification sync between Android phones and Chromebooks. Is Google finally honoring that promise?

Or, is this something completely new, like, I mean, Andromeda, may be?

If you are into code reading, take a look at the commit here.

Thank you Matthew for the help!