Closed Bug 1127212 Opened 10 years ago Closed 10 years ago

[2.2] [bluetooth] bluetooth will not initialize

Categories

(Firefox OS Graveyard :: Bluetooth, defect)

Product:
Firefox OS Graveyard
Component:
Bluetooth
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: Jamie_, Assigned: nhirata)

Details

Attachments

(1 file)

logcat
23.92 KB, text/plain
Details
Attached file logcat —
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:37.0) Gecko/20100101 Firefox/37.0 Build ID: 20150125233636 Steps to reproduce: Flame device appid {3c2e2abc-06d4-11e1-ac3b-374f68613e61} apptype b2g vendor Mozilla name B2G version 2.2.0.0-prerelease appbuildid 20150128002506 platformbuildid 20150128002506 platformversion 37.0a2 geckobuildid 20150128002506 geckoversion 37.0a2 changeset d824c65a6a2b locale en-US os B2G hardware qcom processor arm compiler eabi after changing from the firmware update to 2.0 then shallow flashing to 2.2 1.) go into setting 2.) enable blue-tooth Actual results: It still worked fine in 2.0 when I flash the base, but when I shallow flash 2.2 it seems to stop working the blue-tooth will not enable and returns the error of "L10nError: "bluetoothButton-off-initializing" not found in en-US in app://system.gaiamobile.org/index.html" " at reportMissingEntity (app://system.gaiamobile.org/gaia_build_index.js:197:1512)" logcat attached Expected results: blue-tooth enables and is ready to connect to a blue-tooth device.
can you put this where it belongs if not in proper place, and also if that is not the right log i can attach the other one that looks like it gives the right information also.
Flags: needinfo?(pmathur)
Hi, shallow flash is not enough to bring recent Bluetooth changes into your device. This issue should be the same as bug 1125682. Kindly help flashing system.img and boot.img onto your device to make sure you have a proper testing environment.
I purposely reflashed the base 2.0 image to my flame and tested the blue-tooth and it worked and connected to me computer and my keyboard... but after shallow flashing 2.2 nightly it no longer works. Im just saying that the two seems to be related to each other. Also is the instructions linked to above using the current code and compiling the bluetooth daemon pretty much with out the rest of the system then flashing only what is needed to update it?
Also I already have the base image 188
(In reply to charja13 from comment #4) > I purposely reflashed the base 2.0 image to my flame and tested the > blue-tooth and it worked and connected to me computer and my keyboard... but > after shallow flashing 2.2 nightly it no longer works. Im just saying that > the two seems to be related to each other. Also is the instructions linked > to above using the current code and compiling the bluetooth daemon pretty > much with out the rest of the system then flashing only what is needed to > update it? You need to refresh v2.2 all images (boot.img/system.img are required). Using 2.0 image as base image and shallow image leads missing /system/bin/bluetoothd, /system/lib/libfdio.so, and /init.bluetooth.rc files. So shallow flashing v2.2 gecko/gaia won't work.
okay, that makes sense. where can I find the 2.2 base image?
You can build yourself via config your codebase to branch v2.2 if you're not mozilla employee BRANCH=v2.2 ./config.sh flame-kk Your codebase will switch to v2.2 branch configuration. Then run ./build.sh After that you will have boot.img and system.img P.S: If you have permission to access pvt server you can use pvt flash tool to update image.
Would it be possible for me to have the pre-compiled binaries, I am not exactly in a place to compile it myself.
I am afraid that the only way to have a proper boot.img and system.img is building them by yourself if you don't have permission to access PVT server. :(
okay, I will see if I can free up some hard drive space. I’m going try to google for the 2.2 source code for in case no is on any time soon... Also I am also having a problem with my front facing camera, I can view the one facing me, but there is no way to use the front facing one. I know there should be a button to switch but there isn’t. Wasn’t sure if it was also related to the base image being different.
Rebuilding will not help you if you do not have the blue tooth drivers to begin with. We are working with T2M and are currently trying to get our build to be hosted by them. Our build will have the nightly already configured so that you only have to worry about flashing this build in order to get the updated gonk + nightly bits; the only thing you should have to do after 1 flash is to OTA update.
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #12) > Rebuilding will not help you if you do not have the blue tooth drivers to > begin with. > We are working with T2M and are currently trying to get our build to be > hosted by them. > > Our build will have the nightly already configured so that you only have to > worry about flashing this build in order to get the updated gonk + nightly > bits; the only thing you should have to do after 1 flash is to OTA update. The new architecture needs to be updated the following files: /init.bluetooth.rc /system/bin/bluetoothd /system/lib/libfdio.so So users have to flash boot.img (for init.bluetooth.rc), and system.img. Currently OTA only updates gecko/gaia. We have to update FOTA update for users. See Bug 1130288 for detail discussion. :nhirata "We are working with T2M and are currently trying to get our build to be hosted by them." Are you saying 'FOTA update' hosted by them?
Flags: needinfo?(nhirata.bugzilla)
Okay, so in short. Building the 2.2 or 3.0 base image myself and flashing it is not going to help this due to blue-tooth drives are needed to interact with the new base images either way? so contributors are to expect blue-tooth to not work till T2M hosts or releases the divers?
> :nhirata > "We are working with T2M and are currently trying to get our build to be > hosted by them." Are you saying 'FOTA update' hosted by them? No, we have a build that has the boot.img/system.img from our repo that we're trying to get them to host so that people can flash that build themselves. If they FOTA that build, then we're in luck. Having said that I think the build defaults to OTAing off of our servers.
Flags: needinfo?(nhirata.bugzilla)
(In reply to charja13 from comment #14) > so contributors are to expect blue-tooth to not work till T2M hosts or > releases the divers? It's a low level driver which we don't have the right to distribute if I'm not mistaken. So yes, unfortunately that is correct.
Okay, it makes sense due to laws. I was just making sure I understood that right. thanks
Okay, I have flashed the new base image and checked. When you first flash the base image to the phone it it works under the 3.0, but as soon as the phone is updated to the master it no longer works again. Also when you shallow flash 2.2 the blue tooth also stops working in this case too. Naoki and I took a closer look into this, we found that the blue-tooth is failing to initialize. After looking at what it spits out in the console I think that it can not communicate with the blue-tooth hardware. Naoki please add if I left anything out.
Flags: needinfo?(charja13) → needinfo?(nhirata.bugzilla)
How old is the nightly image? Because there's no init.bluetooth.rc in the root directory, which is required to start the Bluetooth daemon.
The build was taken before https://bugzilla.mozilla.org/show_bug.cgi?id=1124760 It's a 12/<something>/2014 build that I was requested to use instead of the latest. I am working on a v2 of the 18D_Nightly build which is based off of Thursday's build:2/12/2015 It's a packaging issue. I have the build out now and we're internally testing.
Assignee: nobody → nhirata.bugzilla
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Flags: needinfo?(nhirata.bugzilla)
Resolution: --- → FIXED
To note : it will then have to go to T2M for them to post before it is released to the public.
Confirmed that bluetooth can be turned on/off on Flame 2.2. I was able to send/receive images via bluetooth. Device: Flame 2.2 BuildID: 20151022033039 Gaia: 885647d92208fb67574ced44004ab2f29d23cb45 Gecko: 7bc753230036 Gonk: bd9cb3af2a0354577a6903917bc826489050b40d Version: 37.0 (2.2) Firmware Version: v18Dv4 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmercado)
Keywords: verifyme
Status: RESOLVED → VERIFIED
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmercado)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: