Closed Bug 1132333 Opened 11 years ago Closed 11 years ago

Bluetooth does not work on latest base build for community on MDN

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: pmathur, Assigned: nhirata)

Details

Steps to Reproduce: 1. Take a brand new Flame device out of the box. Bring it into fastboot mode. (Without putting in the battery, press the Power button and the Volume down button, and connect it to a computer running Mac / Linux via USB cable. The phone screen will show "FASTBOOT" in purple text.) 2. Go to https://developer.mozilla.org/en-US/Firefox_OS/Phone_guide/Flame/Updating_your_Flame#Updating_your_Flame%27s_software and download the latest base image from there: http://cds.w5v8t3u9.hwcdn.net/v18D_nightly.zip 3. Unzip the file v18D_nightly.zip and execute the script flash.sh 4. When the phone boots into Firefox OS, enable WiFi and wait for Over The Air (OTA) update notifications. 5. Tap the OTA update notification, download the System update and apply it. 6. When the phone reboots into Firefox OS, skip the FTU tour. 7. Go to Settings > Bluetooth and toggle Bluetooth on. Expected Results: Bluetooth is enabled. Actual Results: Bluetooth is not enabled. Output of check_versions.sh script after flashing base build from MDN (Step #2 above): Gaia-Rev e2a3e606675c346b6e6f35351a458040be599b09 Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/f14dcd1c8c0b Build-ID 20141214040212 Version 37.0a1 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20141214.073044 FW-Date Sun Dec 14 07:30:57 EST 2014 Bootloader L1TC000118D0 Output of check_versions.sh script after OTA (Step #6 above): Gaia-Rev e280a660955bbdab265d50f8d9e009de34082332 Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/650863f6987b Build-ID 20150211160231 Version 38.0a1 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20141214.073044 FW-Date Sun Dec 14 07:30:57 EST 2014 Bootloader L1TC000118D0
I think the bluetooth configuration is off... and that probably happens in the boot partition. turning on bluetooth output and capturing logcat shows : I/GeckoBluetooth( 208): OnError: BluetoothInterface::Init failed: 1 The interface failed to initialize.
Bruce, could you take a look please?
Flags: needinfo?(brsun)
I've tried |v18D_nightly.zip|[1], but |/init.target.rc| is not update-to-date, so it doesn't import |init.bluetooth.rc| well[2]. Moreover, |/init.bluetooth.rc|[3], |/system/lib/libfdio.so|, and |/system/bin/bluetoothd| don't even exist on the device. It doesn't work by only flashing gecko/gaia onto the device. [1] http://cds.w5v8t3u9.hwcdn.net/v18D_nightly.zip [2] https://github.com/mozilla-b2g/device-flame/blob/kitkat/init.target.rc#L149 [3] https://github.com/mozilla-b2g/platform_system_bluetoothd/blob/master/scripts/init.bluetooth.rc Naoki, would you please help flash latest |boot.img| and |system.img| to see if it helps or not?
Flags: needinfo?(brsun) → needinfo?(nhirata.bugzilla)
According to an email thread, it seems like the build for 18D that was picked out doesn't have the up-to-date drivers with the proper configuration. Bruce has confirmed this in the previous comment. I'll work on creating a new zip file to upload and test + have mlien test then ask wesley to have T2M host. Thanks. Wesley, FYI.
Assignee: nobody → nhirata.bugzilla
Flags: needinfo?(whuang)
redirect ni to Wesly (TAM)
Flags: needinfo?(whuang) → needinfo?(wehuang)
Thanks Wesley, we have a mail for this and I'll follow with Naoki for new nightly SW release.
Flags: needinfo?(wehuang)
c478c5b4a28a4f4c3d630d91592e2309caf9546b239fcf1703ed704d284b0d95 v18D_nightly_v2.zip
We ran into an issue with the bluetooth settings being displayed due to being caused by bug 1075670. I will need to create a new build, based on the last known good flame build on master.
Flags: needinfo?(nhirata.bugzilla)
Tested the fourth version of the v18D_nightly build (v18D_nightly_v2.zip built from releng build 2015-02-12-01-02-13 ; with a boot.img from engineering build. Included is a flash_settings.sh script that changes the device to have adb turned on, + a few other amenities. The script is not executable by default.) 1. Steps to reproduce: same as in comment 0. Actual Results: (1) Bluetooth is enabled. (2) The v18D_nightly_v2.zip file does not have a __MACOSX folder inside it. 2. Check if adb is running as root. (Community members need this for app development and custom modification.) $ adb root Actual Results: adbd is already running as root 3. Run a light sanity check on the build Actual Results: Build passes sanity checks. 4. Do an Over The Air (OTA) update. Actual Results: Update notification, download, application and phone reboot successful. Output of check_versions.sh script after flashing base build: Gaia-Rev d5a71cedb37dd45f439f672489db3994b349ac43 Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/3094601af679 Build-ID 20150212010213 Version 38.0a1 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20150212.043653 FW-Date Thu Feb 12 04:37:04 EST 2015 Bootloader L1TC000118D0 Output of check_versions.sh script after OTA update: Gaia-Rev e4f7c67378e33e83f88d38ddb4a6c2cabf1423c3 Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/1b4c5daa7b7a Build-ID 20150220010206 Version 38.0a1 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20150212.043653 FW-Date Thu Feb 12 04:37:04 EST 2015 Bootloader L1TC000118D0
Status: NEW → ASSIGNED
I think we're just waiting for mlien to sign off and then T2M to host.
Flags: needinfo?(wehuang)
Flags: needinfo?(mlien)
My test result is the same as Parul's verification from comment 10. MDN publish process is on-going and the new nightly build has already sent to T2M for uploading to their ftp sever. Current stage is waiting for T2M's URL reply.
Flags: needinfo?(mlien)
URL is posted and it's posted on MDN. https://developer.mozilla.org/en-US/Firefox_OS/Phone_guide/Flame/Updating_your_Flame
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Parul's comments in regards to the testing: Tested the 2 builds hosted on T2M and available on MDN by flashing the builds on a new Flame device: (A) http://cds.w5v8t3u9.hwcdn.net/v18D.zip (B) http://cds.w5v8t3u9.hwcdn.net/v18D_nightly_v2.zip (A) http://cds.w5v8t3u9.hwcdn.net/v18D.zip Test Results: 1. The flash.sh file is not set to be executable by default. 2. After the flashing process ends, it drops the command line into |adb logcat|. (Both these points have been raised as annoyances by our community members.) 3. The Flame device is successfully flashed to b2g v2.0. 4. After enabling adb, this is the version information on the device: Software Boot2Gecko 2.0.0-prerelease Update Channel default Git Commit Info 2014-12-15 08:12:45 Gaia-Rev 79f6218c4f30c2739575c3ab800078c2cda135cb Gecko-Rev d9d4000dd43a3637345a41d716dc97fdd700d715 Build-ID 20141215191148 Version 32.0 Device-Name flame FW-Release 4.4.2 FW-Incremental 65 FW-Date Mon Dec 15 18:51:29 CST 2014 Bootloader L1TC000118D0 5. When Bluetooth is enabled, it works as expected. 6. When WiFi is enabled, an update notification appears only for Marketplace. 7. After enabling adb, the latest b2g 2.2 build is flashed from the public build available on MDN (https://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-b2g37_v2_2-flame-kk/). ./shallow_flash.sh --gaia gaia.zip --gecko b2g-37.0.en-US.android-arm.tar.gz ### Waiting for device... please ensure it is connected, switched on and remote debugging is enabled in Gaia ### Restarting adb with root permissions... adbd is already running as root .... 8. The Flame device is successfully flashed to b2g v2.2. 9. After enabling adb, this is the version information on the device: Software Boot2Gecko 2.2.0.0-prerelease Update Channel nightly-b2g37 Git Commit Info 2015-03-10 19:17:12 Gaia-Rev 5af6f8d5d6161dea02002634c6d0a570a122e5dd Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/ec87adb8cf13 Build-ID 20150310162504 Version 37.0 Device-Name flame FW-Release 4.4.2 FW-Incremental 65 FW-Date Mon Dec 15 18:51:29 CST 2014 Bootloader L1TC000118D0 10. When Bluetooth is enabled, it works as expected. ~*~*~ (B) http://cds.w5v8t3u9.hwcdn.net/v18D_nightly_v2.zip Test Results: 1. The flash.sh file is set to be executable by default. 2. After the flashing process ends, it drops the command line into |adb logcat|. 3. The Flame device is successfully flashed to b2g v2.0. 4. After enabling adb this is the version information on the device: Software Boot2Gecko 3.0.0.0-prerelease Update Channel nightly Git Commit Info 2015-02-11 21:38:07 Gaia-Rev d5a71cedb37dd45f439f672489db3994b349ac43 Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/3094601af679 Build-ID 20150212010213 Version 38.0a1 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20150212.043653 FW-Date Thu Feb 12 04:37:04 EST 2015 Bootloader L1TC000118D0 5. When Bluetooth is enabled, it works as expected. 6. When WiFi is enabled, an update notification appears for a System Update. 7. The OTA is applied successfully. After OTA, this is the version information on the device: Gaia-Rev 4ef1fa9b2870499fc9c77cac4a15f62e12a3ad2c Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/23f1f0369df5 Build-ID 20150309160227 Version 39.0a1 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20150212.043653 FW-Date Thu Feb 12 04:37:04 EST 2015 Bootloader L1TC000118D0
Status: RESOLVED → VERIFIED
Flags: needinfo?(wehuang)
QA Contact: pmoore → mshal
You need to log in before you can comment on or make changes to this bug.