mystery test failures

[jim-skippy]

I left a verizon tablet connected to power with WiFi shut off expecting repetitive tests. When I review the tests, it worked for a while and then started skipping tests. I can tell from traffic use graphs that it just stopped trying. I gave the tablet a VERY generous data allocation so that shouldn't be the problem. I did several manual tests when I stopped by to scoop up the first week's results. They work OK. I used both FCC program, Ookla and Calspeed. They both work OK. All I get is a report "no data." And I get no results. Here's a transcribed log built from the report sheets:

1/13 10:52 a.m. lte 44.39 Mb/s / 14.68 Mb/s manual test
1/13 8:20 a.m. lte no data
1/12 1:05 p.m. lte no data
1/12 8:27 a.m. lte no data
1/11 7:09 p.m. lte no data
1/11 2:14 p.m. lte no data
1/11 8:10 p.m. lte no data
1/10 10:49 a.m. lte no data
1/10 8:46 a.m. lte no data
1/09 5:22 p.m. lte no data
1/09 1:48 p.m. lte no data
1/09 8:19 a.m. lte no data
1/08 3:32 p.m. lte 47.35 Mb/s / 15.59 Mb/s
1/08 7:35 a.m. lte no data
1/07 6:21 p.m. lte 17.72 Mb/s / 16.61 Mb/s
1/07 11:19 a.m. lte 38.29 Mb/s / 15.23 Mb/s
1/07 7:45 a.m. lte no data
1/06 10:29 a.m. lte 33.05 Mb/s / 16.30 Mb/s
1/06 7:20 a.m. lte 52.17 Mb/s / 16.89 Mb/s
1/05 6:19 p.m. lte 7.48 / 16.31
1/05 1:46 p.m. lte 24.4 / 16.07
1/05 8:35 a.m. lte 51.10 / 16.77
1/04 6:56 p.m. lte 39.07 / 16.48
1/04 7:45 a.m. lte 51.00 / 18.20
1/03 5:53 p.m. lte no data
1/03 9:15 a.m. lte 24.99 / 16.10
1/03 7:30 a.m. lte 49.40 / 18.99
1/02 6:07 p.m. lte 12.38 / 15.59
1/02 7:57 a.m. 250 Kbps / 6.02 Kbps

used 602 MB out of 2000 permitted

jim warner, warner@ucsc.edu

[yositune]

Thanks Jim. Those are some impressive numbers!

What version of the app are you running?

There are a number of files stored on the protected area of the file system
that I'd like to pass along to SamKnows provided 1) you have the device
rooted and/or are willing to hunt for the files; 2) you would permit me to
share your result and config files with SamKnows.

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Thu, Jan 16, 2014 at 7:33 PM, jim-skippy notifications@github.comwrote:

I left a verizon tablet connected to power with WiFi shut off expecting
repetitive tests. When I review the tests, it worked for a while and then
started skipping tests. I can tell from traffic use graphs that it just
stopped trying. I gave the tablet a VERY generous data allocation so that
shouldn't be the problem. I did several manual tests when I stopped by to
scoop up the first week's results. They work OK. I used both FCC program,
Ookla and Calspeed. They both work OK. All I get is a report "no data." And
I get no results. Here's a transcribed log built from the report sheets:

1/13 10:52 a.m. lte 44.39 Mb/s / 14.68 Mb/s manual test
1/13 8:20 a.m. lte no data
1/12 1:05 p.m. lte no data
1/12 8:27 a.m. lte no data
1/11 7:09 p.m. lte no data
1/11 2:14 p.m. lte no data
1/11 8:10 p.m. lte no data
1/10 10:49 a.m. lte no data
1/10 8:46 a.m. lte no data
1/09 5:22 p.m. lte no data
1/09 1:48 p.m. lte no data
1/09 8:19 a.m. lte no data
1/08 3:32 p.m. lte 47.35 Mb/s / 15.59 Mb/s
1/08 7:35 a.m. lte no data
1/07 6:21 p.m. lte 17.72 Mb/s / 16.61 Mb/s
1/07 11:19 a.m. lte 38.29 Mb/s / 15.23 Mb/s
1/07 7:45 a.m. lte no data
1/06 10:29 a.m. lte 33.05 Mb/s / 16.30 Mb/s
1/06 7:20 a.m. lte 52.17 Mb/s / 16.89 Mb/s
1/05 6:19 p.m. lte 7.48 / 16.31
1/05 1:46 p.m. lte 24.4 / 16.07
1/05 8:35 a.m. lte 51.10 / 16.77
1/04 6:56 p.m. lte 39.07 / 16.48
1/04 7:45 a.m. lte 51.00 / 18.20
1/03 5:53 p.m. lte no data
1/03 9:15 a.m. lte 24.99 / 16.10
1/03 7:30 a.m. lte 49.40 / 18.99
1/02 6:07 p.m. lte 12.38 / 15.59
1/02 7:57 a.m. 250 Kbps / 6.02 Kbps

used 602 MB out of 2000 permitted

jim warner, warner@ucsc.edu

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/6
.

[jim-skippy]

I left the tablet where it collected the week's sample. It is about 0.25
mile from the serving cell site. Hence the good readings. I have time to
go collect it tomorrow. I can probably find the program version number. The
device is not rooted, but it does have a file manager.

I have lots of information on spacial variation of verizon data service. I
was looking for some temporal info -- but of course, the tests need to
actually run :+). Let me know what to look for.

On Thu, Jan 16, 2014 at 8:12 PM, James Miller notifications@github.comwrote:

Thanks Jim. Those are some impressive numbers!

What version of the app are you running?

There are a number of files stored on the protected area of the file
system
that I'd like to pass along to SamKnows provided 1) you have the device
rooted and/or are willing to hunt for the files; 2) you would permit me to
share your result and config files with SamKnows.

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Thu, Jan 16, 2014 at 7:33 PM, jim-skippy notifications@github.comwrote:

I left a verizon tablet connected to power with WiFi shut off expecting
repetitive tests. When I review the tests, it worked for a while and
then
started skipping tests. I can tell from traffic use graphs that it just
stopped trying. I gave the tablet a VERY generous data allocation so
that
shouldn't be the problem. I did several manual tests when I stopped by
to
scoop up the first week's results. They work OK. I used both FCC
program,
Ookla and Calspeed. They both work OK. All I get is a report "no data."
And
I get no results. Here's a transcribed log built from the report sheets:

1/13 10:52 a.m. lte 44.39 Mb/s / 14.68 Mb/s manual test
1/13 8:20 a.m. lte no data
1/12 1:05 p.m. lte no data
1/12 8:27 a.m. lte no data
1/11 7:09 p.m. lte no data
1/11 2:14 p.m. lte no data
1/11 8:10 p.m. lte no data
1/10 10:49 a.m. lte no data
1/10 8:46 a.m. lte no data
1/09 5:22 p.m. lte no data
1/09 1:48 p.m. lte no data
1/09 8:19 a.m. lte no data
1/08 3:32 p.m. lte 47.35 Mb/s / 15.59 Mb/s
1/08 7:35 a.m. lte no data
1/07 6:21 p.m. lte 17.72 Mb/s / 16.61 Mb/s
1/07 11:19 a.m. lte 38.29 Mb/s / 15.23 Mb/s
1/07 7:45 a.m. lte no data
1/06 10:29 a.m. lte 33.05 Mb/s / 16.30 Mb/s
1/06 7:20 a.m. lte 52.17 Mb/s / 16.89 Mb/s
1/05 6:19 p.m. lte 7.48 / 16.31
1/05 1:46 p.m. lte 24.4 / 16.07
1/05 8:35 a.m. lte 51.10 / 16.77
1/04 6:56 p.m. lte 39.07 / 16.48
1/04 7:45 a.m. lte 51.00 / 18.20
1/03 5:53 p.m. lte no data
1/03 9:15 a.m. lte 24.99 / 16.10
1/03 7:30 a.m. lte 49.40 / 18.99
1/02 6:07 p.m. lte 12.38 / 15.59
1/02 7:57 a.m. 250 Kbps / 6.02 Kbps

used 602 MB out of 2000 permitted

jim warner, warner@ucsc.edu

—
Reply to this email directly or view it on GitHub<
https://github.com/FCC/mobile-mba-androidapp/issues/6>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/6#issuecomment-32578940
.

[jim-skippy]

An updated log with the most recent data prepended is below. And the
application version is at the bottom.

1/16 5:17 p.m. lte 31.29 Mb/s / 15:47 Mb/s
1/16 2:26 p.m. lte 22:33 Mb/s / 15.84 Mb/s
1/16 8:15 a.m. lte 43.41 Mb/s / 18.51 Mb/s
1/15 6:14 p.m. lte 28.65 Mb/s / 16.15 Mb/s
1/15 9:40 a.m. lte 33.19 Mb/s / 16.25 Mb/s
1/15 7:03 a.m. lte no data found
1/14 2:38 p.m. lte no data found
1/14 8:20 a.m. lte 43.45 Mb/s / 16.50 Mb/s
1/13 6:25 p.m. lte 13.19 Mb/s / 11.70 Mb/s
1/13 10:52 a.m. lte 44.39 Mb/s / 14.68 Mb/s manual test
1/13 8:20 a.m. lte no data found
1/12 1:05 p.m. lte no data found
1/12 8:27 a.m. lte no data found
1/11 7:09 p.m. lte no data found
1/11 2:14 p.m. lte no data found
1/11 8:10 p.m. lte no data found
1/10 10:49 a.m. lte no data found
1/10 8:46 a.m. lte no data found
1/09 5:22 p.m. lte no data found
1/09 1:48 p.m. lte no data found
1/09 8:19 a.m. lte no data found
1/08 3:32 p.m. lte 47.35 Mb/s / 15.59 Mb/s
1/08 7:35 a.m. lte no data found
1/07 6:21 p.m. lte 17.72 Mb/s / 16.61 Mb/s
1/07 11:19 a.m. lte 38.29 Mb/s / 15.23 Mb/s
1/07 7:45 a.m. lte no data found
1/06 10:29 a.m. lte 33.05 Mb/s / 16.30 Mb/s
1/06 7:20 a.m. lte 52.17 Mb/s / 16.89 Mb/s
1/05 6:19 p.m. lte 7.48 Mb/s / 16.31 Mb/s
1/05 1:46 p.m. lte 24.4 Mb/s / 16.07 Mb/s
1/05 8:35 a.m. lte 51.10 Mb/s / 16.77 Mb/s
1/04 6:56 p.m. lte 39.07 Mb/s / 16.48 Mb/s
1/04 7:45 a.m. lte 51.00 Mb/s / 18.20 Mb/s
1/03 5:53 p.m. lte no data found
1/03 9:15 a.m. lte 24.99 Mb/s / 16.10 Mb/s
1/03 7:30 a.m. lte 49.40 Mb/s / 18.99 Mb/s
1/02 6:07 p.m. lte 12.38 Mb/s / 15.59 Mb/s
1/02 7:57 a.m. 250 Kbps / 6.02 Kbps

used 602 MB out of 2000 permitted
version 1.71, schedule 1.0
tablet SCH-1815 android OS version 15

On Thu, Jan 16, 2014 at 9:28 PM, Jim Warner warner@ucsc.edu wrote:

I left the tablet where it collected the week's sample. It is about 0.25
mile from the serving cell site. Hence the good readings. I have time to
go collect it tomorrow. I can probably find the program version number. The
device is not rooted, but it does have a file manager.

I have lots of information on spacial variation of verizon data service.
I was looking for some temporal info -- but of course, the tests need to
actually run :+). Let me know what to look for.

On Thu, Jan 16, 2014 at 8:12 PM, James Miller notifications@github.comwrote:

Thanks Jim. Those are some impressive numbers!

What version of the app are you running?

There are a number of files stored on the protected area of the file
system
that I'd like to pass along to SamKnows provided 1) you have the device
rooted and/or are willing to hunt for the files; 2) you would permit me
to
share your result and config files with SamKnows.

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Thu, Jan 16, 2014 at 7:33 PM, jim-skippy notifications@github.comwrote:

I left a verizon tablet connected to power with WiFi shut off expecting
repetitive tests. When I review the tests, it worked for a while and
then
started skipping tests. I can tell from traffic use graphs that it just
stopped trying. I gave the tablet a VERY generous data allocation so
that
shouldn't be the problem. I did several manual tests when I stopped by
to
scoop up the first week's results. They work OK. I used both FCC
program,
Ookla and Calspeed. They both work OK. All I get is a report "no data."
And
I get no results. Here's a transcribed log built from the report
sheets:

1/13 10:52 a.m. lte 44.39 Mb/s / 14.68 Mb/s manual test
1/13 8:20 a.m. lte no data
1/12 1:05 p.m. lte no data
1/12 8:27 a.m. lte no data
1/11 7:09 p.m. lte no data
1/11 2:14 p.m. lte no data
1/11 8:10 p.m. lte no data
1/10 10:49 a.m. lte no data
1/10 8:46 a.m. lte no data
1/09 5:22 p.m. lte no data
1/09 1:48 p.m. lte no data
1/09 8:19 a.m. lte no data
1/08 3:32 p.m. lte 47.35 Mb/s / 15.59 Mb/s
1/08 7:35 a.m. lte no data
1/07 6:21 p.m. lte 17.72 Mb/s / 16.61 Mb/s
1/07 11:19 a.m. lte 38.29 Mb/s / 15.23 Mb/s
1/07 7:45 a.m. lte no data
1/06 10:29 a.m. lte 33.05 Mb/s / 16.30 Mb/s
1/06 7:20 a.m. lte 52.17 Mb/s / 16.89 Mb/s
1/05 6:19 p.m. lte 7.48 / 16.31
1/05 1:46 p.m. lte 24.4 / 16.07
1/05 8:35 a.m. lte 51.10 / 16.77
1/04 6:56 p.m. lte 39.07 / 16.48
1/04 7:45 a.m. lte 51.00 / 18.20
1/03 5:53 p.m. lte no data
1/03 9:15 a.m. lte 24.99 / 16.10
1/03 7:30 a.m. lte 49.40 / 18.99
1/02 6:07 p.m. lte 12.38 / 15.59
1/02 7:57 a.m. 250 Kbps / 6.02 Kbps

used 602 MB out of 2000 permitted

jim warner, warner@ucsc.edu

—
Reply to this email directly or view it on GitHub<
https://github.com/FCC/mobile-mba-androidapp/issues/6>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/6#issuecomment-32578940
.

[yositune]

Jim,

Why don't you call me and we can walk through copying the App test result
files and emailing it off the device.
202-423-9643

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Fri, Jan 17, 2014 at 1:59 PM, jim-skippy notifications@github.comwrote:

An updated log with the most recent data prepended is below. And the
application version is at the bottom.

1/16 5:17 p.m. lte 31.29 Mb/s / 15:47 Mb/s
1/16 2:26 p.m. lte 22:33 Mb/s / 15.84 Mb/s
1/16 8:15 a.m. lte 43.41 Mb/s / 18.51 Mb/s
1/15 6:14 p.m. lte 28.65 Mb/s / 16.15 Mb/s
1/15 9:40 a.m. lte 33.19 Mb/s / 16.25 Mb/s
1/15 7:03 a.m. lte no data found
1/14 2:38 p.m. lte no data found
1/14 8:20 a.m. lte 43.45 Mb/s / 16.50 Mb/s
1/13 6:25 p.m. lte 13.19 Mb/s / 11.70 Mb/s
1/13 10:52 a.m. lte 44.39 Mb/s / 14.68 Mb/s manual test
1/13 8:20 a.m. lte no data found
1/12 1:05 p.m. lte no data found
1/12 8:27 a.m. lte no data found
1/11 7:09 p.m. lte no data found
1/11 2:14 p.m. lte no data found
1/11 8:10 p.m. lte no data found
1/10 10:49 a.m. lte no data found
1/10 8:46 a.m. lte no data found
1/09 5:22 p.m. lte no data found
1/09 1:48 p.m. lte no data found
1/09 8:19 a.m. lte no data found
1/08 3:32 p.m. lte 47.35 Mb/s / 15.59 Mb/s
1/08 7:35 a.m. lte no data found
1/07 6:21 p.m. lte 17.72 Mb/s / 16.61 Mb/s
1/07 11:19 a.m. lte 38.29 Mb/s / 15.23 Mb/s
1/07 7:45 a.m. lte no data found
1/06 10:29 a.m. lte 33.05 Mb/s / 16.30 Mb/s
1/06 7:20 a.m. lte 52.17 Mb/s / 16.89 Mb/s
1/05 6:19 p.m. lte 7.48 Mb/s / 16.31 Mb/s
1/05 1:46 p.m. lte 24.4 Mb/s / 16.07 Mb/s
1/05 8:35 a.m. lte 51.10 Mb/s / 16.77 Mb/s
1/04 6:56 p.m. lte 39.07 Mb/s / 16.48 Mb/s
1/04 7:45 a.m. lte 51.00 Mb/s / 18.20 Mb/s
1/03 5:53 p.m. lte no data found
1/03 9:15 a.m. lte 24.99 Mb/s / 16.10 Mb/s
1/03 7:30 a.m. lte 49.40 Mb/s / 18.99 Mb/s
1/02 6:07 p.m. lte 12.38 Mb/s / 15.59 Mb/s
1/02 7:57 a.m. 250 Kbps / 6.02 Kbps

used 602 MB out of 2000 permitted
version 1.71, schedule 1.0
tablet SCH-1815 android OS version 15

On Thu, Jan 16, 2014 at 9:28 PM, Jim Warner warner@ucsc.edu wrote:

I left the tablet where it collected the week's sample. It is about 0.25
mile from the serving cell site. Hence the good readings. I have time to
go collect it tomorrow. I can probably find the program version number.
The
device is not rooted, but it does have a file manager.

I have lots of information on spacial variation of verizon data service.
I was looking for some temporal info -- but of course, the tests need to
actually run :+). Let me know what to look for.

On Thu, Jan 16, 2014 at 8:12 PM, James Miller notifications@github.comwrote:

Thanks Jim. Those are some impressive numbers!

What version of the app are you running?

There are a number of files stored on the protected area of the file
system
that I'd like to pass along to SamKnows provided 1) you have the device
rooted and/or are willing to hunt for the files; 2) you would permit me
to
share your result and config files with SamKnows.

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Thu, Jan 16, 2014 at 7:33 PM, jim-skippy notifications@github.comwrote:

I left a verizon tablet connected to power with WiFi shut off
expecting
repetitive tests. When I review the tests, it worked for a while and
then
started skipping tests. I can tell from traffic use graphs that it
just
stopped trying. I gave the tablet a VERY generous data allocation so
that
shouldn't be the problem. I did several manual tests when I stopped
by
to
scoop up the first week's results. They work OK. I used both FCC
program,
Ookla and Calspeed. They both work OK. All I get is a report "no
data."
And
I get no results. Here's a transcribed log built from the report
sheets:

1/13 10:52 a.m. lte 44.39 Mb/s / 14.68 Mb/s manual test
1/13 8:20 a.m. lte no data
1/12 1:05 p.m. lte no data
1/12 8:27 a.m. lte no data
1/11 7:09 p.m. lte no data
1/11 2:14 p.m. lte no data
1/11 8:10 p.m. lte no data
1/10 10:49 a.m. lte no data
1/10 8:46 a.m. lte no data
1/09 5:22 p.m. lte no data
1/09 1:48 p.m. lte no data
1/09 8:19 a.m. lte no data
1/08 3:32 p.m. lte 47.35 Mb/s / 15.59 Mb/s
1/08 7:35 a.m. lte no data
1/07 6:21 p.m. lte 17.72 Mb/s / 16.61 Mb/s
1/07 11:19 a.m. lte 38.29 Mb/s / 15.23 Mb/s
1/07 7:45 a.m. lte no data
1/06 10:29 a.m. lte 33.05 Mb/s / 16.30 Mb/s
1/06 7:20 a.m. lte 52.17 Mb/s / 16.89 Mb/s
1/05 6:19 p.m. lte 7.48 / 16.31
1/05 1:46 p.m. lte 24.4 / 16.07
1/05 8:35 a.m. lte 51.10 / 16.77
1/04 6:56 p.m. lte 39.07 / 16.48
1/04 7:45 a.m. lte 51.00 / 18.20
1/03 5:53 p.m. lte no data
1/03 9:15 a.m. lte 24.99 / 16.10
1/03 7:30 a.m. lte 49.40 / 18.99
1/02 6:07 p.m. lte 12.38 / 15.59
1/02 7:57 a.m. 250 Kbps / 6.02 Kbps

used 602 MB out of 2000 permitted

jim warner, warner@ucsc.edu

—
Reply to this email directly or view it on GitHub<
https://github.com/FCC/mobile-mba-androidapp/issues/6>
.

—
Reply to this email directly or view it on GitHub<
https://github.com/FCC/mobile-mba-androidapp/issues/6#issuecomment-32578940>

.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/6#issuecomment-32636097
.

[yositune]

Note that in a current beta we are working on an export feature (that we
discussed last year) but are still working through file handling and other
issues. I'll see if i can get a link for an APK for you if that would be
helpful.

Please confirm the version of hte App your running, also note that you can
get the newest public release in the Android Play store (version 1.71).

Please browse to a directory on
/<USB Storage/Android/data/com.samknows.fcc/cache

If you could archive and email the contents that'd be great.

Here's what I see off my box looking at my Verizon LTE Tablet but note
several of these files are the csv and JSON raw exports from the
application. You will likely only see the log and results files.

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc
mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/app_metadata
mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/closesttarget.csv
mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/cpuactivity.csv
mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/datacap.csv
mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/extract.zip
mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/jhttpgetmt.csv
mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/jhttppostmt.csv
mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/judplatency.csv
mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/location.csv
mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/log.file
mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/netactivity.csv
mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/net_usage.csv
mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/network_data.csv
mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/phone_identity.csv
mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/results.json
mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/test_results_submited

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Fri, Jan 17, 2014 at 2:00 PM, James Miller
jamesmilleresquire@gmail.comwrote:

Jim,

Why don't you call me and we can walk through copying the App test result
files and emailing it off the device.
202-423-9643

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Fri, Jan 17, 2014 at 1:59 PM, jim-skippy notifications@github.comwrote:

An updated log with the most recent data prepended is below. And the
application version is at the bottom.

1/16 5:17 p.m. lte 31.29 Mb/s / 15:47 Mb/s
1/16 2:26 p.m. lte 22:33 Mb/s / 15.84 Mb/s
1/16 8:15 a.m. lte 43.41 Mb/s / 18.51 Mb/s
1/15 6:14 p.m. lte 28.65 Mb/s / 16.15 Mb/s
1/15 9:40 a.m. lte 33.19 Mb/s / 16.25 Mb/s
1/15 7:03 a.m. lte no data found
1/14 2:38 p.m. lte no data found
1/14 8:20 a.m. lte 43.45 Mb/s / 16.50 Mb/s
1/13 6:25 p.m. lte 13.19 Mb/s / 11.70 Mb/s
1/13 10:52 a.m. lte 44.39 Mb/s / 14.68 Mb/s manual test
1/13 8:20 a.m. lte no data found
1/12 1:05 p.m. lte no data found
1/12 8:27 a.m. lte no data found
1/11 7:09 p.m. lte no data found
1/11 2:14 p.m. lte no data found
1/11 8:10 p.m. lte no data found
1/10 10:49 a.m. lte no data found
1/10 8:46 a.m. lte no data found
1/09 5:22 p.m. lte no data found
1/09 1:48 p.m. lte no data found
1/09 8:19 a.m. lte no data found
1/08 3:32 p.m. lte 47.35 Mb/s / 15.59 Mb/s
1/08 7:35 a.m. lte no data found
1/07 6:21 p.m. lte 17.72 Mb/s / 16.61 Mb/s
1/07 11:19 a.m. lte 38.29 Mb/s / 15.23 Mb/s
1/07 7:45 a.m. lte no data found
1/06 10:29 a.m. lte 33.05 Mb/s / 16.30 Mb/s
1/06 7:20 a.m. lte 52.17 Mb/s / 16.89 Mb/s
1/05 6:19 p.m. lte 7.48 Mb/s / 16.31 Mb/s
1/05 1:46 p.m. lte 24.4 Mb/s / 16.07 Mb/s
1/05 8:35 a.m. lte 51.10 Mb/s / 16.77 Mb/s
1/04 6:56 p.m. lte 39.07 Mb/s / 16.48 Mb/s
1/04 7:45 a.m. lte 51.00 Mb/s / 18.20 Mb/s
1/03 5:53 p.m. lte no data found
1/03 9:15 a.m. lte 24.99 Mb/s / 16.10 Mb/s
1/03 7:30 a.m. lte 49.40 Mb/s / 18.99 Mb/s
1/02 6:07 p.m. lte 12.38 Mb/s / 15.59 Mb/s
1/02 7:57 a.m. 250 Kbps / 6.02 Kbps

used 602 MB out of 2000 permitted
version 1.71, schedule 1.0
tablet SCH-1815 android OS version 15

On Thu, Jan 16, 2014 at 9:28 PM, Jim Warner warner@ucsc.edu wrote:

I left the tablet where it collected the week's sample. It is about
0.25
mile from the serving cell site. Hence the good readings. I have time
to
go collect it tomorrow. I can probably find the program version number.
The
device is not rooted, but it does have a file manager.

I have lots of information on spacial variation of verizon data
service.
I was looking for some temporal info -- but of course, the tests need
to
actually run :+). Let me know what to look for.

On Thu, Jan 16, 2014 at 8:12 PM, James Miller notifications@github.comwrote:

Thanks Jim. Those are some impressive numbers!

What version of the app are you running?

There are a number of files stored on the protected area of the file
system
that I'd like to pass along to SamKnows provided 1) you have the
device
rooted and/or are willing to hunt for the files; 2) you would permit
me
to
share your result and config files with SamKnows.

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Thu, Jan 16, 2014 at 7:33 PM, jim-skippy notifications@github.comwrote:

I left a verizon tablet connected to power with WiFi shut off
expecting
repetitive tests. When I review the tests, it worked for a while and
then
started skipping tests. I can tell from traffic use graphs that it
just
stopped trying. I gave the tablet a VERY generous data allocation so
that
shouldn't be the problem. I did several manual tests when I stopped
by
to
scoop up the first week's results. They work OK. I used both FCC
program,
Ookla and Calspeed. They both work OK. All I get is a report "no
data."
And
I get no results. Here's a transcribed log built from the report
sheets:

1/13 10:52 a.m. lte 44.39 Mb/s / 14.68 Mb/s manual test
1/13 8:20 a.m. lte no data
1/12 1:05 p.m. lte no data
1/12 8:27 a.m. lte no data
1/11 7:09 p.m. lte no data
1/11 2:14 p.m. lte no data
1/11 8:10 p.m. lte no data
1/10 10:49 a.m. lte no data
1/10 8:46 a.m. lte no data
1/09 5:22 p.m. lte no data
1/09 1:48 p.m. lte no data
1/09 8:19 a.m. lte no data
1/08 3:32 p.m. lte 47.35 Mb/s / 15.59 Mb/s
1/08 7:35 a.m. lte no data
1/07 6:21 p.m. lte 17.72 Mb/s / 16.61 Mb/s
1/07 11:19 a.m. lte 38.29 Mb/s / 15.23 Mb/s
1/07 7:45 a.m. lte no data
1/06 10:29 a.m. lte 33.05 Mb/s / 16.30 Mb/s
1/06 7:20 a.m. lte 52.17 Mb/s / 16.89 Mb/s
1/05 6:19 p.m. lte 7.48 / 16.31
1/05 1:46 p.m. lte 24.4 / 16.07
1/05 8:35 a.m. lte 51.10 / 16.77
1/04 6:56 p.m. lte 39.07 / 16.48
1/04 7:45 a.m. lte 51.00 / 18.20
1/03 5:53 p.m. lte no data
1/03 9:15 a.m. lte 24.99 / 16.10
1/03 7:30 a.m. lte 49.40 / 18.99
1/02 6:07 p.m. lte 12.38 / 15.59
1/02 7:57 a.m. 250 Kbps / 6.02 Kbps

used 602 MB out of 2000 permitted

jim warner, warner@ucsc.edu

�
Reply to this email directly or view it on GitHub<
https://github.com/FCC/mobile-mba-androidapp/issues/6>
.

�
Reply to this email directly or view it on GitHub<
https://github.com/FCC/mobile-mba-androidapp/issues/6#issuecomment-32578940>

.

�
Reply to this email directly or view it on GitHubhttps://github.com//issues/6#issuecomment-32636097
.

[jim-skippy]

The log file is about 3 Mb. That appears to be too large for github. The
test results file is much smaller.

On Fri, Jan 17, 2014 at 11:11 AM, James Miller notifications@github.comwrote:

Note that in a current beta we are working on an export feature (that we
discussed last year) but are still working through file handling and other
issues. I'll see if i can get a link for an APK for you if that would be
helpful.

Please confirm the version of hte App your running, also note that you can
get the newest public release in the Android Play store (version 1.71).

Please browse to a directory on
/<USB Storage/Android/data/com.samknows.fcc/cache

If you could archive and email the contents that'd be great.

Here's what I see off my box looking at my Verizon LTE Tablet but note
several of these files are the csv and JSON raw exports from the
application. You will likely only see the log and results files.

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc
mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/app_metadata

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/closesttarget.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/cpuactivity.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/datacap.csv
mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/extract.zip
mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/jhttpgetmt.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/jhttppostmt.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/judplatency.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/location.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/log.file
mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/netactivity.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/net_usage.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/network_data.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/phone_identity.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/results.json

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/test_results_submited

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Fri, Jan 17, 2014 at 2:00 PM, James Miller
jamesmilleresquire@gmail.comwrote:

Jim,

Why don't you call me and we can walk through copying the App test
result
files and emailing it off the device.
202-423-9643

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Fri, Jan 17, 2014 at 1:59 PM, jim-skippy notifications@github.comwrote:

An updated log with the most recent data prepended is below. And the
application version is at the bottom.

1/16 5:17 p.m. lte 31.29 Mb/s / 15:47 Mb/s
1/16 2:26 p.m. lte 22:33 Mb/s / 15.84 Mb/s
1/16 8:15 a.m. lte 43.41 Mb/s / 18.51 Mb/s
1/15 6:14 p.m. lte 28.65 Mb/s / 16.15 Mb/s
1/15 9:40 a.m. lte 33.19 Mb/s / 16.25 Mb/s
1/15 7:03 a.m. lte no data found
1/14 2:38 p.m. lte no data found
1/14 8:20 a.m. lte 43.45 Mb/s / 16.50 Mb/s
1/13 6:25 p.m. lte 13.19 Mb/s / 11.70 Mb/s
1/13 10:52 a.m. lte 44.39 Mb/s / 14.68 Mb/s manual test
1/13 8:20 a.m. lte no data found
1/12 1:05 p.m. lte no data found
1/12 8:27 a.m. lte no data found
1/11 7:09 p.m. lte no data found
1/11 2:14 p.m. lte no data found
1/11 8:10 p.m. lte no data found
1/10 10:49 a.m. lte no data found
1/10 8:46 a.m. lte no data found
1/09 5:22 p.m. lte no data found
1/09 1:48 p.m. lte no data found
1/09 8:19 a.m. lte no data found
1/08 3:32 p.m. lte 47.35 Mb/s / 15.59 Mb/s
1/08 7:35 a.m. lte no data found
1/07 6:21 p.m. lte 17.72 Mb/s / 16.61 Mb/s
1/07 11:19 a.m. lte 38.29 Mb/s / 15.23 Mb/s
1/07 7:45 a.m. lte no data found
1/06 10:29 a.m. lte 33.05 Mb/s / 16.30 Mb/s
1/06 7:20 a.m. lte 52.17 Mb/s / 16.89 Mb/s
1/05 6:19 p.m. lte 7.48 Mb/s / 16.31 Mb/s
1/05 1:46 p.m. lte 24.4 Mb/s / 16.07 Mb/s
1/05 8:35 a.m. lte 51.10 Mb/s / 16.77 Mb/s
1/04 6:56 p.m. lte 39.07 Mb/s / 16.48 Mb/s
1/04 7:45 a.m. lte 51.00 Mb/s / 18.20 Mb/s
1/03 5:53 p.m. lte no data found
1/03 9:15 a.m. lte 24.99 Mb/s / 16.10 Mb/s
1/03 7:30 a.m. lte 49.40 Mb/s / 18.99 Mb/s
1/02 6:07 p.m. lte 12.38 Mb/s / 15.59 Mb/s
1/02 7:57 a.m. 250 Kbps / 6.02 Kbps

used 602 MB out of 2000 permitted
version 1.71, schedule 1.0
tablet SCH-1815 android OS version 15

On Thu, Jan 16, 2014 at 9:28 PM, Jim Warner warner@ucsc.edu wrote:

I left the tablet where it collected the week's sample. It is about
0.25
mile from the serving cell site. Hence the good readings. I have time
to
go collect it tomorrow. I can probably find the program version
number.
The
device is not rooted, but it does have a file manager.

I have lots of information on spacial variation of verizon data
service.
I was looking for some temporal info -- but of course, the tests need
to
actually run :+). Let me know what to look for.

On Thu, Jan 16, 2014 at 8:12 PM, James Miller <
notifications@github.com>wrote:

Thanks Jim. Those are some impressive numbers!

What version of the app are you running?

There are a number of files stored on the protected area of the file
system
that I'd like to pass along to SamKnows provided 1) you have the
device
rooted and/or are willing to hunt for the files; 2) you would permit
me
to
share your result and config files with SamKnows.

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Thu, Jan 16, 2014 at 7:33 PM, jim-skippy <
notifications@github.com>wrote:

I left a verizon tablet connected to power with WiFi shut off
expecting
repetitive tests. When I review the tests, it worked for a while
and
then
started skipping tests. I can tell from traffic use graphs that it
just
stopped trying. I gave the tablet a VERY generous data allocation
so
that
shouldn't be the problem. I did several manual tests when I
stopped
by
to
scoop up the first week's results. They work OK. I used both FCC
program,
Ookla and Calspeed. They both work OK. All I get is a report "no
data."
And
I get no results. Here's a transcribed log built from the report
sheets:

1/13 10:52 a.m. lte 44.39 Mb/s / 14.68 Mb/s manual test
1/13 8:20 a.m. lte no data
1/12 1:05 p.m. lte no data
1/12 8:27 a.m. lte no data
1/11 7:09 p.m. lte no data
1/11 2:14 p.m. lte no data
1/11 8:10 p.m. lte no data
1/10 10:49 a.m. lte no data
1/10 8:46 a.m. lte no data
1/09 5:22 p.m. lte no data
1/09 1:48 p.m. lte no data
1/09 8:19 a.m. lte no data
1/08 3:32 p.m. lte 47.35 Mb/s / 15.59 Mb/s
1/08 7:35 a.m. lte no data
1/07 6:21 p.m. lte 17.72 Mb/s / 16.61 Mb/s
1/07 11:19 a.m. lte 38.29 Mb/s / 15.23 Mb/s
1/07 7:45 a.m. lte no data
1/06 10:29 a.m. lte 33.05 Mb/s / 16.30 Mb/s
1/06 7:20 a.m. lte 52.17 Mb/s / 16.89 Mb/s
1/05 6:19 p.m. lte 7.48 / 16.31
1/05 1:46 p.m. lte 24.4 / 16.07
1/05 8:35 a.m. lte 51.10 / 16.77
1/04 6:56 p.m. lte 39.07 / 16.48
1/04 7:45 a.m. lte 51.00 / 18.20
1/03 5:53 p.m. lte no data
1/03 9:15 a.m. lte 24.99 / 16.10
1/03 7:30 a.m. lte 49.40 / 18.99
1/02 6:07 p.m. lte 12.38 / 15.59
1/02 7:57 a.m. 250 Kbps / 6.02 Kbps

used 602 MB out of 2000 permitted

jim warner, warner@ucsc.edu

—
Reply to this email directly or view it on GitHub<
https://github.com/FCC/mobile-mba-androidapp/issues/6>
.

—
Reply to this email directly or view it on GitHub<

https://github.com/FCC/mobile-mba-androidapp/issues/6#issuecomment-32578940>

.

—
Reply to this email directly or view it on GitHub<
https://github.com/FCC/mobile-mba-androidapp/issues/6#issuecomment-32636097>

.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/6#issuecomment-32637087
.

[yositune]

You can attach the files in Gmail pretty easily with some attachment apps
available in the store. I also have installed some gzip, JSON viewers and
other apps on my tablet that have been helpful.

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Fri, Jan 17, 2014 at 2:22 PM, jim-skippy notifications@github.comwrote:

The log file is about 3 Mb. That appears to be too large for github. The
test results file is much smaller.

On Fri, Jan 17, 2014 at 11:11 AM, James Miller notifications@github.comwrote:

Note that in a current beta we are working on an export feature (that we
discussed last year) but are still working through file handling and
other
issues. I'll see if i can get a link for an APK for you if that would be
helpful.

Please confirm the version of hte App your running, also note that you
can
get the newest public release in the Android Play store (version 1.71).

Please browse to a directory on
/<USB Storage/Android/data/com.samknows.fcc/cache

If you could archive and email the contents that'd be great.

Here's what I see off my box looking at my Verizon LTE Tablet but note
several of these files are the csv and JSON raw exports from the
application. You will likely only see the log and results files.

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/app_metadata

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/closesttarget.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/cpuactivity.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/datacap.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/extract.zip

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/jhttpgetmt.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/jhttppostmt.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/judplatency.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/location.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/log.file

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/netactivity.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/net_usage.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/network_data.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/phone_identity.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/results.json

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/test_results_submited

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Fri, Jan 17, 2014 at 2:00 PM, James Miller
jamesmilleresquire@gmail.comwrote:

Jim,

Why don't you call me and we can walk through copying the App test
result
files and emailing it off the device.
202-423-9643

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Fri, Jan 17, 2014 at 1:59 PM, jim-skippy notifications@github.comwrote:

An updated log with the most recent data prepended is below. And the
application version is at the bottom.

1/16 5:17 p.m. lte 31.29 Mb/s / 15:47 Mb/s
1/16 2:26 p.m. lte 22:33 Mb/s / 15.84 Mb/s
1/16 8:15 a.m. lte 43.41 Mb/s / 18.51 Mb/s
1/15 6:14 p.m. lte 28.65 Mb/s / 16.15 Mb/s
1/15 9:40 a.m. lte 33.19 Mb/s / 16.25 Mb/s
1/15 7:03 a.m. lte no data found
1/14 2:38 p.m. lte no data found
1/14 8:20 a.m. lte 43.45 Mb/s / 16.50 Mb/s
1/13 6:25 p.m. lte 13.19 Mb/s / 11.70 Mb/s
1/13 10:52 a.m. lte 44.39 Mb/s / 14.68 Mb/s manual test
1/13 8:20 a.m. lte no data found
1/12 1:05 p.m. lte no data found
1/12 8:27 a.m. lte no data found
1/11 7:09 p.m. lte no data found
1/11 2:14 p.m. lte no data found
1/11 8:10 p.m. lte no data found
1/10 10:49 a.m. lte no data found
1/10 8:46 a.m. lte no data found
1/09 5:22 p.m. lte no data found
1/09 1:48 p.m. lte no data found
1/09 8:19 a.m. lte no data found
1/08 3:32 p.m. lte 47.35 Mb/s / 15.59 Mb/s
1/08 7:35 a.m. lte no data found
1/07 6:21 p.m. lte 17.72 Mb/s / 16.61 Mb/s
1/07 11:19 a.m. lte 38.29 Mb/s / 15.23 Mb/s
1/07 7:45 a.m. lte no data found
1/06 10:29 a.m. lte 33.05 Mb/s / 16.30 Mb/s
1/06 7:20 a.m. lte 52.17 Mb/s / 16.89 Mb/s
1/05 6:19 p.m. lte 7.48 Mb/s / 16.31 Mb/s
1/05 1:46 p.m. lte 24.4 Mb/s / 16.07 Mb/s
1/05 8:35 a.m. lte 51.10 Mb/s / 16.77 Mb/s
1/04 6:56 p.m. lte 39.07 Mb/s / 16.48 Mb/s
1/04 7:45 a.m. lte 51.00 Mb/s / 18.20 Mb/s
1/03 5:53 p.m. lte no data found
1/03 9:15 a.m. lte 24.99 Mb/s / 16.10 Mb/s
1/03 7:30 a.m. lte 49.40 Mb/s / 18.99 Mb/s
1/02 6:07 p.m. lte 12.38 Mb/s / 15.59 Mb/s
1/02 7:57 a.m. 250 Kbps / 6.02 Kbps

used 602 MB out of 2000 permitted
version 1.71, schedule 1.0
tablet SCH-1815 android OS version 15

On Thu, Jan 16, 2014 at 9:28 PM, Jim Warner warner@ucsc.edu wrote:

I left the tablet where it collected the week's sample. It is about
0.25
mile from the serving cell site. Hence the good readings. I have
time
to
go collect it tomorrow. I can probably find the program version
number.
The
device is not rooted, but it does have a file manager.

I have lots of information on spacial variation of verizon data
service.
I was looking for some temporal info -- but of course, the tests
need
to
actually run :+). Let me know what to look for.

On Thu, Jan 16, 2014 at 8:12 PM, James Miller <
notifications@github.com>wrote:

Thanks Jim. Those are some impressive numbers!

What version of the app are you running?

There are a number of files stored on the protected area of the
file
system
that I'd like to pass along to SamKnows provided 1) you have the
device
rooted and/or are willing to hunt for the files; 2) you would
permit
me
to
share your result and config files with SamKnows.

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Thu, Jan 16, 2014 at 7:33 PM, jim-skippy <
notifications@github.com>wrote:

I left a verizon tablet connected to power with WiFi shut off
expecting
repetitive tests. When I review the tests, it worked for a while
and
then
started skipping tests. I can tell from traffic use graphs that
it
just
stopped trying. I gave the tablet a VERY generous data
allocation
so
that
shouldn't be the problem. I did several manual tests when I
stopped
by
to
scoop up the first week's results. They work OK. I used both FCC
program,
Ookla and Calspeed. They both work OK. All I get is a report "no
data."
And
I get no results. Here's a transcribed log built from the report
sheets:

1/13 10:52 a.m. lte 44.39 Mb/s / 14.68 Mb/s manual test
1/13 8:20 a.m. lte no data
1/12 1:05 p.m. lte no data
1/12 8:27 a.m. lte no data
1/11 7:09 p.m. lte no data
1/11 2:14 p.m. lte no data
1/11 8:10 p.m. lte no data
1/10 10:49 a.m. lte no data
1/10 8:46 a.m. lte no data
1/09 5:22 p.m. lte no data
1/09 1:48 p.m. lte no data
1/09 8:19 a.m. lte no data
1/08 3:32 p.m. lte 47.35 Mb/s / 15.59 Mb/s
1/08 7:35 a.m. lte no data
1/07 6:21 p.m. lte 17.72 Mb/s / 16.61 Mb/s
1/07 11:19 a.m. lte 38.29 Mb/s / 15.23 Mb/s
1/07 7:45 a.m. lte no data
1/06 10:29 a.m. lte 33.05 Mb/s / 16.30 Mb/s
1/06 7:20 a.m. lte 52.17 Mb/s / 16.89 Mb/s
1/05 6:19 p.m. lte 7.48 / 16.31
1/05 1:46 p.m. lte 24.4 / 16.07
1/05 8:35 a.m. lte 51.10 / 16.77
1/04 6:56 p.m. lte 39.07 / 16.48
1/04 7:45 a.m. lte 51.00 / 18.20
1/03 5:53 p.m. lte no data
1/03 9:15 a.m. lte 24.99 / 16.10
1/03 7:30 a.m. lte 49.40 / 18.99
1/02 6:07 p.m. lte 12.38 / 15.59
1/02 7:57 a.m. 250 Kbps / 6.02 Kbps

used 602 MB out of 2000 permitted

jim warner, warner@ucsc.edu

�
Reply to this email directly or view it on GitHub<
https://github.com/FCC/mobile-mba-androidapp/issues/6>
.

�
Reply to this email directly or view it on GitHub<

https://github.com/FCC/mobile-mba-androidapp/issues/6#issuecomment-32578940>

.

�
Reply to this email directly or view it on GitHub<

https://github.com/FCC/mobile-mba-androidapp/issues/6#issuecomment-32636097>

.

�
Reply to this email directly or view it on GitHub<
https://github.com/FCC/mobile-mba-androidapp/issues/6#issuecomment-32637087>

.

�
Reply to this email directly or view it on GitHubhttps://github.com//issues/6#issuecomment-32638059
.

[jim-skippy]

I have the files on my Windows desktop. I tried to send them using gmail.
The bounce message I get says:

Google tried to deliver your message, but it was rejected by the server for
the recipient domain reply.github.com by github-smtp2-ext8.iad.github.net.
[192.30.252.199].

The error that the other server returned was:
552 5.3.4 Error: message file too big

On Fri, Jan 17, 2014 at 11:30 AM, James Miller notifications@github.comwrote:

You can attach the files in Gmail pretty easily with some attachment apps
available in the store. I also have installed some gzip, JSON viewers and
other apps on my tablet that have been helpful.

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Fri, Jan 17, 2014 at 2:22 PM, jim-skippy notifications@github.comwrote:

The log file is about 3 Mb. That appears to be too large for github. The
test results file is much smaller.

On Fri, Jan 17, 2014 at 11:11 AM, James Miller notifications@github.comwrote:

Note that in a current beta we are working on an export feature (that
we
discussed last year) but are still working through file handling and
other
issues. I'll see if i can get a link for an APK for you if that would
be
helpful.

Please confirm the version of hte App your running, also note that you
can
get the newest public release in the Android Play store (version
1.71).

Please browse to a directory on
/<USB Storage/Android/data/com.samknows.fcc/cache

If you could archive and email the contents that'd be great.

Here's what I see off my box looking at my Verizon LTE Tablet but note
several of these files are the csv and JSON raw exports from the
application. You will likely only see the log and results files.

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/app_metadata

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/closesttarget.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/cpuactivity.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/datacap.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/extract.zip

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/jhttpgetmt.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/jhttppostmt.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/judplatency.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/location.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/log.file

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/netactivity.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/net_usage.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/network_data.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/phone_identity.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/results.json

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/test_results_submited

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Fri, Jan 17, 2014 at 2:00 PM, James Miller
jamesmilleresquire@gmail.comwrote:

Jim,

Why don't you call me and we can walk through copying the App test
result
files and emailing it off the device.
202-423-9643

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Fri, Jan 17, 2014 at 1:59 PM, jim-skippy <
notifications@github.com>wrote:

An updated log with the most recent data prepended is below. And
the
application version is at the bottom.

1/16 5:17 p.m. lte 31.29 Mb/s / 15:47 Mb/s
1/16 2:26 p.m. lte 22:33 Mb/s / 15.84 Mb/s
1/16 8:15 a.m. lte 43.41 Mb/s / 18.51 Mb/s
1/15 6:14 p.m. lte 28.65 Mb/s / 16.15 Mb/s
1/15 9:40 a.m. lte 33.19 Mb/s / 16.25 Mb/s
1/15 7:03 a.m. lte no data found
1/14 2:38 p.m. lte no data found
1/14 8:20 a.m. lte 43.45 Mb/s / 16.50 Mb/s
1/13 6:25 p.m. lte 13.19 Mb/s / 11.70 Mb/s
1/13 10:52 a.m. lte 44.39 Mb/s / 14.68 Mb/s manual test
1/13 8:20 a.m. lte no data found
1/12 1:05 p.m. lte no data found
1/12 8:27 a.m. lte no data found
1/11 7:09 p.m. lte no data found
1/11 2:14 p.m. lte no data found
1/11 8:10 p.m. lte no data found
1/10 10:49 a.m. lte no data found
1/10 8:46 a.m. lte no data found
1/09 5:22 p.m. lte no data found
1/09 1:48 p.m. lte no data found
1/09 8:19 a.m. lte no data found
1/08 3:32 p.m. lte 47.35 Mb/s / 15.59 Mb/s
1/08 7:35 a.m. lte no data found
1/07 6:21 p.m. lte 17.72 Mb/s / 16.61 Mb/s
1/07 11:19 a.m. lte 38.29 Mb/s / 15.23 Mb/s
1/07 7:45 a.m. lte no data found
1/06 10:29 a.m. lte 33.05 Mb/s / 16.30 Mb/s
1/06 7:20 a.m. lte 52.17 Mb/s / 16.89 Mb/s
1/05 6:19 p.m. lte 7.48 Mb/s / 16.31 Mb/s
1/05 1:46 p.m. lte 24.4 Mb/s / 16.07 Mb/s
1/05 8:35 a.m. lte 51.10 Mb/s / 16.77 Mb/s
1/04 6:56 p.m. lte 39.07 Mb/s / 16.48 Mb/s
1/04 7:45 a.m. lte 51.00 Mb/s / 18.20 Mb/s
1/03 5:53 p.m. lte no data found
1/03 9:15 a.m. lte 24.99 Mb/s / 16.10 Mb/s
1/03 7:30 a.m. lte 49.40 Mb/s / 18.99 Mb/s
1/02 6:07 p.m. lte 12.38 Mb/s / 15.59 Mb/s
1/02 7:57 a.m. 250 Kbps / 6.02 Kbps

used 602 MB out of 2000 permitted
version 1.71, schedule 1.0
tablet SCH-1815 android OS version 15

On Thu, Jan 16, 2014 at 9:28 PM, Jim Warner warner@ucsc.edu
wrote:

I left the tablet where it collected the week's sample. It is
about
0.25
mile from the serving cell site. Hence the good readings. I have
time
to
go collect it tomorrow. I can probably find the program version
number.
The
device is not rooted, but it does have a file manager.

I have lots of information on spacial variation of verizon data
service.
I was looking for some temporal info -- but of course, the tests
need
to
actually run :+). Let me know what to look for.

On Thu, Jan 16, 2014 at 8:12 PM, James Miller <
notifications@github.com>wrote:

Thanks Jim. Those are some impressive numbers!

What version of the app are you running?

There are a number of files stored on the protected area of the
file
system
that I'd like to pass along to SamKnows provided 1) you have the
device
rooted and/or are willing to hunt for the files; 2) you would
permit
me
to
share your result and config files with SamKnows.

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Thu, Jan 16, 2014 at 7:33 PM, jim-skippy <
notifications@github.com>wrote:

I left a verizon tablet connected to power with WiFi shut off
expecting
repetitive tests. When I review the tests, it worked for a
while
and
then
started skipping tests. I can tell from traffic use graphs
that
it
just
stopped trying. I gave the tablet a VERY generous data
allocation
so
that
shouldn't be the problem. I did several manual tests when I
stopped
by
to
scoop up the first week's results. They work OK. I used both
FCC
program,
Ookla and Calspeed. They both work OK. All I get is a report
"no
data."
And
I get no results. Here's a transcribed log built from the
report
sheets:

1/13 10:52 a.m. lte 44.39 Mb/s / 14.68 Mb/s manual test
1/13 8:20 a.m. lte no data
1/12 1:05 p.m. lte no data
1/12 8:27 a.m. lte no data
1/11 7:09 p.m. lte no data
1/11 2:14 p.m. lte no data
1/11 8:10 p.m. lte no data
1/10 10:49 a.m. lte no data
1/10 8:46 a.m. lte no data
1/09 5:22 p.m. lte no data
1/09 1:48 p.m. lte no data
1/09 8:19 a.m. lte no data
1/08 3:32 p.m. lte 47.35 Mb/s / 15.59 Mb/s
1/08 7:35 a.m. lte no data
1/07 6:21 p.m. lte 17.72 Mb/s / 16.61 Mb/s
1/07 11:19 a.m. lte 38.29 Mb/s / 15.23 Mb/s
1/07 7:45 a.m. lte no data
1/06 10:29 a.m. lte 33.05 Mb/s / 16.30 Mb/s
1/06 7:20 a.m. lte 52.17 Mb/s / 16.89 Mb/s
1/05 6:19 p.m. lte 7.48 / 16.31
1/05 1:46 p.m. lte 24.4 / 16.07
1/05 8:35 a.m. lte 51.10 / 16.77
1/04 6:56 p.m. lte 39.07 / 16.48
1/04 7:45 a.m. lte 51.00 / 18.20
1/03 5:53 p.m. lte no data
1/03 9:15 a.m. lte 24.99 / 16.10
1/03 7:30 a.m. lte 49.40 / 18.99
1/02 6:07 p.m. lte 12.38 / 15.59
1/02 7:57 a.m. 250 Kbps / 6.02 Kbps

used 602 MB out of 2000 permitted

jim warner, warner@ucsc.edu

—
Reply to this email directly or view it on GitHub<
https://github.com/FCC/mobile-mba-androidapp/issues/6>
.

—
Reply to this email directly or view it on GitHub<

https://github.com/FCC/mobile-mba-androidapp/issues/6#issuecomment-32578940>

.

—
Reply to this email directly or view it on GitHub<

https://github.com/FCC/mobile-mba-androidapp/issues/6#issuecomment-32636097>

.

—
Reply to this email directly or view it on GitHub<

https://github.com/FCC/mobile-mba-androidapp/issues/6#issuecomment-32637087>

.

—
Reply to this email directly or view it on GitHub<
https://github.com/FCC/mobile-mba-androidapp/issues/6#issuecomment-32638059>

.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/6#issuecomment-32638682
.

[yositune]

Can you resend to my emails? thanks Jim.

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Fri, Jan 17, 2014 at 2:41 PM, jim-skippy notifications@github.comwrote:

I have the files on my Windows desktop. I tried to send them using gmail.
The bounce message I get says:

Google tried to deliver your message, but it was rejected by the server
for
the recipient domain reply.github.com by github-smtp2-ext8.iad.github.net.

[192.30.252.199].

The error that the other server returned was:
552 5.3.4 Error: message file too big

On Fri, Jan 17, 2014 at 11:30 AM, James Miller notifications@github.comwrote:

You can attach the files in Gmail pretty easily with some attachment
apps
available in the store. I also have installed some gzip, JSON viewers
and
other apps on my tablet that have been helpful.

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Fri, Jan 17, 2014 at 2:22 PM, jim-skippy notifications@github.comwrote:

The log file is about 3 Mb. That appears to be too large for github.
The
test results file is much smaller.

On Fri, Jan 17, 2014 at 11:11 AM, James Miller <
notifications@github.com>wrote:

Note that in a current beta we are working on an export feature
(that
we
discussed last year) but are still working through file handling and
other
issues. I'll see if i can get a link for an APK for you if that
would
be
helpful.

Please confirm the version of hte App your running, also note that
you
can
get the newest public release in the Android Play store (version
1.71).

Please browse to a directory on
/<USB Storage/Android/data/com.samknows.fcc/cache

If you could archive and email the contents that'd be great.

Here's what I see off my box looking at my Verizon LTE Tablet but
note
several of these files are the csv and JSON raw exports from the
application. You will likely only see the log and results files.

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/app_metadata

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/closesttarget.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/cpuactivity.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/datacap.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/extract.zip

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/jhttpgetmt.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/jhttppostmt.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/judplatency.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/location.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/log.file

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/netactivity.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/net_usage.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/network_data.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/phone_identity.csv

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/results.json

mtp://[usb:001,008]/Tablet/Android/data/com.samknows.fcc/cache/test_results_submited

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Fri, Jan 17, 2014 at 2:00 PM, James Miller
jamesmilleresquire@gmail.comwrote:

Jim,

Why don't you call me and we can walk through copying the App test
result
files and emailing it off the device.
202-423-9643

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Fri, Jan 17, 2014 at 1:59 PM, jim-skippy <
notifications@github.com>wrote:

An updated log with the most recent data prepended is below. And
the
application version is at the bottom.

1/16 5:17 p.m. lte 31.29 Mb/s / 15:47 Mb/s
1/16 2:26 p.m. lte 22:33 Mb/s / 15.84 Mb/s
1/16 8:15 a.m. lte 43.41 Mb/s / 18.51 Mb/s
1/15 6:14 p.m. lte 28.65 Mb/s / 16.15 Mb/s
1/15 9:40 a.m. lte 33.19 Mb/s / 16.25 Mb/s
1/15 7:03 a.m. lte no data found
1/14 2:38 p.m. lte no data found
1/14 8:20 a.m. lte 43.45 Mb/s / 16.50 Mb/s
1/13 6:25 p.m. lte 13.19 Mb/s / 11.70 Mb/s
1/13 10:52 a.m. lte 44.39 Mb/s / 14.68 Mb/s manual test
1/13 8:20 a.m. lte no data found
1/12 1:05 p.m. lte no data found
1/12 8:27 a.m. lte no data found
1/11 7:09 p.m. lte no data found
1/11 2:14 p.m. lte no data found
1/11 8:10 p.m. lte no data found
1/10 10:49 a.m. lte no data found
1/10 8:46 a.m. lte no data found
1/09 5:22 p.m. lte no data found
1/09 1:48 p.m. lte no data found
1/09 8:19 a.m. lte no data found
1/08 3:32 p.m. lte 47.35 Mb/s / 15.59 Mb/s
1/08 7:35 a.m. lte no data found
1/07 6:21 p.m. lte 17.72 Mb/s / 16.61 Mb/s
1/07 11:19 a.m. lte 38.29 Mb/s / 15.23 Mb/s
1/07 7:45 a.m. lte no data found
1/06 10:29 a.m. lte 33.05 Mb/s / 16.30 Mb/s
1/06 7:20 a.m. lte 52.17 Mb/s / 16.89 Mb/s
1/05 6:19 p.m. lte 7.48 Mb/s / 16.31 Mb/s
1/05 1:46 p.m. lte 24.4 Mb/s / 16.07 Mb/s
1/05 8:35 a.m. lte 51.10 Mb/s / 16.77 Mb/s
1/04 6:56 p.m. lte 39.07 Mb/s / 16.48 Mb/s
1/04 7:45 a.m. lte 51.00 Mb/s / 18.20 Mb/s
1/03 5:53 p.m. lte no data found
1/03 9:15 a.m. lte 24.99 Mb/s / 16.10 Mb/s
1/03 7:30 a.m. lte 49.40 Mb/s / 18.99 Mb/s
1/02 6:07 p.m. lte 12.38 Mb/s / 15.59 Mb/s
1/02 7:57 a.m. 250 Kbps / 6.02 Kbps

used 602 MB out of 2000 permitted
version 1.71, schedule 1.0
tablet SCH-1815 android OS version 15

On Thu, Jan 16, 2014 at 9:28 PM, Jim Warner warner@ucsc.edu
wrote:

I left the tablet where it collected the week's sample. It is
about
0.25
mile from the serving cell site. Hence the good readings. I
have
time
to
go collect it tomorrow. I can probably find the program version
number.
The
device is not rooted, but it does have a file manager.

I have lots of information on spacial variation of verizon data
service.
I was looking for some temporal info -- but of course, the
tests
need
to
actually run :+). Let me know what to look for.

On Thu, Jan 16, 2014 at 8:12 PM, James Miller <
notifications@github.com>wrote:

Thanks Jim. Those are some impressive numbers!

What version of the app are you running?

There are a number of files stored on the protected area of
the
file
system
that I'd like to pass along to SamKnows provided 1) you have
the
device
rooted and/or are willing to hunt for the files; 2) you would
permit
me
to
share your result and config files with SamKnows.

JamesMillerEsquire@Gmail.com

"Wovon man nicht sprechen kann, darüber muß man schweigen."
(What we cannot speak about we must pass over in silence. )
Ludwig Josef Johann Wittgenstein

On Thu, Jan 16, 2014 at 7:33 PM, jim-skippy <
notifications@github.com>wrote:

I left a verizon tablet connected to power with WiFi shut
off
expecting
repetitive tests. When I review the tests, it worked for a
while
and
then
started skipping tests. I can tell from traffic use graphs
that
it
just
stopped trying. I gave the tablet a VERY generous data
allocation
so
that
shouldn't be the problem. I did several manual tests when I
stopped
by
to
scoop up the first week's results. They work OK. I used both
FCC
program,
Ookla and Calspeed. They both work OK. All I get is a report
"no
data."
And
I get no results. Here's a transcribed log built from the
report
sheets:

1/13 10:52 a.m. lte 44.39 Mb/s / 14.68 Mb/s manual test
1/13 8:20 a.m. lte no data
1/12 1:05 p.m. lte no data
1/12 8:27 a.m. lte no data
1/11 7:09 p.m. lte no data
1/11 2:14 p.m. lte no data
1/11 8:10 p.m. lte no data
1/10 10:49 a.m. lte no data
1/10 8:46 a.m. lte no data
1/09 5:22 p.m. lte no data
1/09 1:48 p.m. lte no data
1/09 8:19 a.m. lte no data
1/08 3:32 p.m. lte 47.35 Mb/s / 15.59 Mb/s
1/08 7:35 a.m. lte no data
1/07 6:21 p.m. lte 17.72 Mb/s / 16.61 Mb/s
1/07 11:19 a.m. lte 38.29 Mb/s / 15.23 Mb/s
1/07 7:45 a.m. lte no data
1/06 10:29 a.m. lte 33.05 Mb/s / 16.30 Mb/s
1/06 7:20 a.m. lte 52.17 Mb/s / 16.89 Mb/s
1/05 6:19 p.m. lte 7.48 / 16.31
1/05 1:46 p.m. lte 24.4 / 16.07
1/05 8:35 a.m. lte 51.10 / 16.77
1/04 6:56 p.m. lte 39.07 / 16.48
1/04 7:45 a.m. lte 51.00 / 18.20
1/03 5:53 p.m. lte no data
1/03 9:15 a.m. lte 24.99 / 16.10
1/03 7:30 a.m. lte 49.40 / 18.99
1/02 6:07 p.m. lte 12.38 / 15.59
1/02 7:57 a.m. 250 Kbps / 6.02 Kbps

used 602 MB out of 2000 permitted

jim warner, warner@ucsc.edu

�
Reply to this email directly or view it on GitHub<
https://github.com/FCC/mobile-mba-androidapp/issues/6>
.

�
Reply to this email directly or view it on GitHub<

https://github.com/FCC/mobile-mba-androidapp/issues/6#issuecomment-32578940>

.

�
Reply to this email directly or view it on GitHub<

https://github.com/FCC/mobile-mba-androidapp/issues/6#issuecomment-32636097>

.

�
Reply to this email directly or view it on GitHub<

https://github.com/FCC/mobile-mba-androidapp/issues/6#issuecomment-32637087>

.

�
Reply to this email directly or view it on GitHub<

https://github.com/FCC/mobile-mba-androidapp/issues/6#issuecomment-32638059>

.

�
Reply to this email directly or view it on GitHub<
https://github.com/FCC/mobile-mba-androidapp/issues/6#issuecomment-32638682>

.

�
Reply to this email directly or view it on GitHubhttps://github.com//issues/6#issuecomment-32639635
.