1198338 - [Metrics] B2gDroid should support Metrics being collected on FxOS

Status: RESOLVED FIXED

(B2GDroid Graveyard :: General, defect)

Description

[Ravi Dandu]

B2GDroid should support all Metrics that are being collected on FxOS on Gonk. These include
1) FTU Ping: The data should contain the info on HW device, and unique ID ()
   - FTU app should be run for B2GDroid, so the user opt-in (opt-out) for analytics is collected  
2) AppUsage: Collect time of Apps usage 
3) Support of metric roadmap items at https://wiki.mozilla.org/FirefoxOS/Metrics#Roadmap

Comment 1

[Ravi Dandu]

Advanced Metrics Framework & Custom Metrics (Bug 1152000) should also be functional on B2GDroid.

Comment 2

[Peter Dolanjski [:pdol]]

Fabrice, I know we said we'd drop the FTU, in general, but we may need the opt-in/opt-out screen for data collection.  NI'ing you for now to give a heads up.

Comment 3

[[:fabrice] Fabrice Desré]

Not sure which kind of UX we want there though? Jacqueline, help!

Comment 4

[Tamara Hills [:thills]]

Hi Fabrice,

Do we have an API we can call to get the Hardware id?  Also, is there a way for us to tell if we need to call this API?

Thanks,

-tamara

Comment 5

[Jacqueline Savory [:jsavory] UX]

I'm on it!

Ravi, I'm just wondering if this can be a single opt-in check box like the current data collection in FTU? Also, do you have any copy that we can include in the opt-in screen to explain the data collection to the user?

Comment 6

[[:fabrice] Fabrice Desré]

(In reply to Tamara Hills [:thills] from comment #4)
> Hi Fabrice,
> 
> Do we have an API we can call to get the Hardware id?  Also, is there a way
> for us to tell if we need to call this API?

Is that the IMEI? If so, I will add setting to let you get it, and the way to know if you have to use the setting is to test if navigator.mozTelephony is available (it's not on b2gdroid).

Comment 7

[Ravi Dandu]

(In reply to Jacqueline Savory [:jsavory] UX from comment #5)
> Ravi, I'm just wondering if this can be a single opt-in check box like the
> current data collection in FTU? Also, do you have any copy that we can
> include in the opt-in screen to explain the data collection to the user?
This is being worked on in bug 1181295.
There will be a radiobox with three options (basic, advanced, none). The copy for is being discussed in the bug.

Comment 8

[[:fabrice] Fabrice Desré]

Attachment: get-imei.patch

That sets the deviceinfo.imei setting with the expected value.

Comment 9

[Pulsebot]

https://hg.mozilla.org/integration/b2g-inbound/rev/876b48d14ee0

Comment 10

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/876b48d14ee0

Comment 11

[Tamara Hills [:thills]]

Marking as leave-open as we have another part coming for the ftu_ping piece.

Comment 12

[Tamara Hills [:thills]]

Hi Fabrice,

When does this deviceinfo.imei setting get set?  If it fails to get the imei (assuming it uses the *#06# method) because the telephony stack is not available, does it retry?

Thanks,

-tamara

Comment 13

[Tamara Hills [:thills]]

Hi Fabrice,

I need to simulate the condition where navigator.mozTelephony is not available.  Do you have instructions on how I can setup b2gdroid to test this?

I was thinking it could be simpler just to check if deviceinfo.imei exists, but then there could be network stack issues if the radio is not available and getting imei can fail, so it's probably better to know whether it's b2gdroid or not by checking the interface.

Thanks,

-tamara

Comment 14

[[:fabrice] Fabrice Desré]

(In reply to Tamara Hills [:thills] from comment #12)
> Hi Fabrice,
> 
> When does this deviceinfo.imei setting get set?  If it fails to get the imei
> (assuming it uses the *#06# method) because the telephony stack is not
> available, does it retry?

We do that early during b2g startup, but I have no way to know if it's long after Android is initialized. We don't retry for now - let's see if that's needed or not...


> I need to simulate the condition where navigator.mozTelephony is not
> available.  Do you have instructions on how I can setup b2gdroid to test
> this?
> 
> I was thinking it could be simpler just to check if deviceinfo.imei exists,
> but then there could be network stack issues if the radio is not available
> and getting imei can fail, so it's probably better to know whether it's
> b2gdroid or not by checking the interface.

There are build instructions at https://wiki.mozilla.org/B2gdroid
Let me know if they work for you!

Comment 15

[Tamara Hills [:thills]]

Attachment: packageinstall.txt

Hi Fabrice,

I had a little trouble with the instructions.  Everything worked fine until I got to the |mach package| and |mach install| part.  I attached the log of my package and install.  Let me know if you have any thoughts of what I can try.

This is my mozconfig.  Not sure if something can be missing from here:
ac_add_options --enable-application=mobile/android
ac_add_options --target=arm-linux-androideabi
ac_add_options --with-android-sdk="/Volumes/development/android-sdk-macosx"

Thanks,

-tamara

Comment 16

[[:fabrice] Fabrice Desré]

You built fennec, not b2gdroid! Here's my local mozconfig:

ac_add_options --enable-application=mobile/android/b2gdroid

ac_add_options --target=arm-linux-androideabi

# With the following Android SDK and NDK:
ac_add_options --with-android-sdk="/home/fabrice/.mozbuild/android-sdk-linux"
ac_add_options --with-android-ndk="/home/fabrice/.mozbuild/android-ndk-r8e"

ac_add_options --enable-android-apz

# ac_add_options --enable-debug
ac_add_options --enable-debug-symbols

ac_add_options --enable-updater

mk_add_options MOZ_OBJDIR=/home/fabrice/dev/builds/obj-b2gdroid
mk_add_options AUTOCLOBBER=1
mk_add_options MOZ_MAKE_FLAGS="-j8 -s"

ac_add_options --with-branding=mobile/android/b2gdroid/branding/unofficial

ac_add_options --with-ccache

GAIADIR=/home/fabrice/dev/gaia
MOZ_UPDATER=1

MOZTTDIR=/home/fabrice/dev/moztt


You may also need to export MOZ_TELEMETRY_REPORTING=1

Comment 17

[Firefox Bug Husbandry Bot]

Removing leave-open keyword from resolved bugs, per :sylvestre.