857484 - Proximity sensor does not work on Ikura

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: General, defect, P1)

Description

[David Palomino [:dpalomino]]

Tested on Ikura, during certification testing in Spain. 

Buildid "20130321070205". 

Proximity sensor does not work. Steps: 

1. Make a voice call
2. Block proximity sensor

Expected: screen switched off
Current: screen not switched off, but when blocking proximity sensor the brightness descreases

This is blocking for certification (adding dep). Nominating for tef+.

Comment 1

[Daniel Coloma:dcoloma]

tef+, however, this is working in Buri devices. Alex, how can we distinguish this in order to stress this only happens in some devices, using NPTOB?

Comment 2

[David Palomino [:dpalomino]]

Hi, 

As this is a blocker for certification, changing prio to P1. 

Thks!
David

Comment 3

[Daniel Coloma:dcoloma]

This seems to be very similar to bug 848597, not sure if it is a duplicate

Comment 4

[songsy]

I think it is because the sensor works without calibration.
The proximity sensor need to calibrate first.

Comment 5

[Daniel Coloma:dcoloma]

(In reply to songsy from comment #4)
> I think it is because the sensor works without calibration.
> The proximity sensor need to calibrate first.

And how should the sensor be calibrated? Do we need any changes in Gecko/Gaia for doing so?

Comment 6

[Kai-Chih Hu [:khu]]

Triaged on April 9th: Assigned to Marco.

Comment 7

[Vivien Nicolas (:vingtetun) (:21) - (NOT reading bugmails, needinfo? please)]

Does not sounds like a Gaia bug. Moving to General to reflect this.

Comment 8

[Marco Chen [:mchen]]

The issue is the same on inari. I tried to put calibration file from uangi to inari, then proximity sensor is working during in_call state.

Comment 9

[Marco Chen [:mchen]]

Hi ShenYang,

If the testing image is provided by your side, then please help to update device with calibration file. Thanks.

Comment 10

[Juan Perez-Bedmar [:juanpbf]]

Adding some colleagues in CC

ShenYang, please, give us the info requested
thanks

Comment 11

[Firefox_Mozilla]

I have told Daniel Coloma how to calibrate the sensor. 
And this issue is also existing with successful calibration.

Comment 12

[Marco Chen [:mchen]]

(In reply to Firefox_Mozilla from comment #11)
> I have told Daniel Coloma how to calibrate the sensor. 
> And this issue is also existing with successful calibration.

May I know more detail of calibration procedures?

I think calibration of proximity is not provided by Gaia or Gecko so I guess it needs to be done on Android version first then flashing to firefox OS. But after flashing, the calibration data is gone by new userdata.img.

I can fix this issue on inari by just pushing a calibration file into right place. Does inari use same component of prox with ikula?

Thanks.

Comment 13

[Firefox_Mozilla]

Hi, Marco

I have send you a letter about the details, thanks.

Comment 14

[Marco Chen [:mchen]]

Hi all,

I used 0410 images from partner's FTP site.
And this issue is not exist after I do the calibration. (of course that it is exist before I performed calibration).

Hi Daniel,

May I know your status on 0410 image? And could you see proximity sensor with true when you block the device on calibration screen? Thanks.

Comment 15

[Daniel Coloma:dcoloma]

it works with 0410 build. What should be the next steps to fix this bug?

Comment 16

[David Palomino [:dpalomino]]

Issue reported in LatAm. Adding dep.

Comment 17

[Marco Chen [:mchen]]

Hi all,

Since the issue is classified and verified already, could we close this bug? Or any issue there? Thanks.

Comment 18

[Firefox_Mozilla]

Our engineers will do the calibration for every device before the device is put into market. 

And maybe these device are used for development, so they need user to calibrate by hand. 

Thanks

Comment 19

[David Palomino [:dpalomino]]

Hi, 

Thanks for the update. 

Could you please provide more info about the calibration process? What do you mean with "will do the calibration for every device before the device is put into market"? Is this a manual process?

In any case, we'll need to have the devices that are currently being used for the certification in the same conditions as they will be after mass production.

Comment 20

[Firefox_Mozilla]

Hi, Here is the process to calibrate proximity sensor

1) load the image to the device
2) start the Dialer app
3) Input "*983*0#" and press "send". The device should start zte engineering test app
4) Press "Down" and Select "Sensor"
5) Press "Calibrate" button to do prox sensor calibration
6) The device will show "Calibrate OK", when the calibration is complete.
7) Then you can test the sensor.
     block the sensor, the screen will show "Proximity:true"
     unblock  the sensor, the screen will show "Proximity:false"
8) Press "Back", "Quit" to quit this app, and check whether the sensor can work in voice call.

Comment 21

[John Hammink]

Attachment: Logcat of STR

Comment 22

[Firefox_Mozilla]

Does this problem still happen after sensor calibration? Thanks

Comment 23

[Juan Perez-Bedmar [:juanpbf]]

After callibration is done, my sample works fine.

(In reply to David Palomino [:dpv] from comment #19)
> What do
> you mean with "will do the calibration for every device before the device is
> put into market"? Is this a manual process?
> 

Hi David. Callibration for every sample (not sure if it's done manually or automatically) is part of our usual mass production process.

BR

Comment 24

[Marco Chen [:mchen]]

Just help to add needinfo for comment 23. Thanks.

Comment 25

[Daniel Coloma:dcoloma]

When device is calibrated, everything works properly. Vendor confirm they will do the calibration before device distribution, so we can close this as RESOLVED/FIXED.

Comment 26

[Marco Chen [:mchen]]

Cancel the needinfo flag, because partner already answer it on comment 25.

Comment 27

[Marco Chen [:mchen]]

To change status to WORKSFORME, because there is no any patch needed to land. And this bug is related to calebration process by our partner. After clarification, partner garantee calebration will be a regular process on their mass production line.

Comment 29

[Cody Roesch [:croesch]]

Inari Build: 20130426070207
Gecko  http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/54285d67454b
Gaia   c47ef39de04e634d847cc86b6acc616fabce69eb
Kernel:  Feb 21st

From what I understand it appears that there is not going to be a fix for this on our end, However i will just add my comments anyway because I have something i noticed when trying to work on this bug.

I'm unable to test with a Ikura device, but In the Inari build above,the proximity censor for the phone never triggers while I make a call and am in the dialer app. 

Something interesting I noticed however. Whenever I would pull the phone away from my ear while in the dialer app and trying to make a call, the contact between the touchscreen and my ear would cause the notification screen to drop down. So when I would look to see if the proximity censor worked and the screen would go dark, instead I would see that the notification screen would be on screen now. I doubt this would happen if the proximity censor was working properly.

a. Is this going to be null once the vendors calibrate the sensor? 
b. Any point in filing a bug on this undesired behavior? 
Def don't want to see the notification drop down when making a call.

Comment 30

[Marco Chen [:mchen]]

> a. Is this going to be null once the vendors calibrate the sensor? 
> b. Any point in filing a bug on this undesired behavior? 

If proximity sensor is calibrated well then screen will be turn off and touch disabled in your test case. So that will not be a issue when p-sensor works well.

Comment 31

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

I get a USSD Error when trying to calibrate my device.

Comment 32

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

filed bug 868207