1169657 - [Peak][v2.2] unable to accept some calls from the lockscreen

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::Dialer, defect)

Description

[Jovan Gerodetti]

Since I upgraded to 2.2 I'm unable to accept some incoming calls.

When I pull the "unlock circle" to the right just nothing happens. If I pull it to the left the call gets rejected. 

A company is trying to call me for a few days now, but I can not accept the call. When I'm trying to reproduce the problem with my home phone, I have no problem with accepting the call.

I'm not sure how to provide future information to this issue since I can't reproduce the issue my self, but it happens daily. 

The only thing I noticed is that I can't see the calling number on the call screen. When I call my self I see my number. (I don't have any contact for it) 
Later I can look up the number in the phone app...

Comment 1

[Johan Lorenzo [:jlorenzo]]

As code-complete for 2.2 is near, steps-wanted ASAP.

Comment 2

[Johan Lorenzo [:jlorenzo]]

:PBylenga has a good suggestion: Can you tell us what is the usage of the partition /data? To do so:
> adb root
> adb shell 
> df /data/

Also can you tell us on what device you installed 2.2? 

Finally, another thing that can help us could be to have the logs when the company calls you. To do so, please follow https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#RIL_Debugging and then:
> adb logcat | tee phoneCall.log
and attach phoneCall.log.

Comment 3

[Jovan Gerodetti]

> Filesystem             Size   Used   Free   Blksize
> /data/                1.9G  191.8M  1.7G   4096
> [1] + Done                 df /data 

I received the call a few minutes after I filed the bug and I was able to accept it... Now I will try to call my self from different phones to see if the problem will occur again... 

How should I take a logcat log when device is locked? adb is disabled when the device is locked.

Comment 4

[Jovan Gerodetti]

okay I tired three different phones and I always was able to accept the call O.o I have no idea what happened. I didn't change anything.

Comment 5

[Jayme Mercado [:JMercado] (Inactive 3/4/2016)]

I've tried quite a few different scenarios trying to reproduce this bug on both shallow and full flash on Flame builds from today and was unable to reproduce this issue.

It would really help if we could get the build id and device type for the DUT that was reproducing this issue.
	
Environmental Variables:
Device: Flame 2.2 KK Shallow Flash 319 MB
BuildID: 20150529051139
Gaia: ef9efcc658321f3d7dce27e3e423caf6dcb0f388
Gecko: ff7b17af990a
Gonk: Could not pull gonk.  Did you shallow Flash?
Version: 37.0 (2.2) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Environmental Variables:
Device: Flame 2.2 KK Full Flash 319 MB
BuildID: 20150529002502
Gaia: a57ec5786c9f941c690266bbb26049dbb8482b05
Gecko: 6e9875ef5297
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 37.0 (2.2) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Comment 6

[Jovan Gerodetti]

yes sorry, is there a script to pull these Environmental Variables?

Comment 7

[Pi Wei Cheng [:piwei] (inactive)]

I was also unable to reproduce the bug after multiple attempts. The original report seems to hint that the reporter had the phone sleeping because the unlocking UI that they described only appears when screen is off. So I also tried to let the phone sleep for awhile (up to 20 min) before receiving a call and still couldn't reproduce the issue.

Device: Flame 2.2 (full flashed, 319MB, KK)
BuildID: 20150529002502
Gaia: a57ec5786c9f941c690266bbb26049dbb8482b05
Gecko: 6e9875ef5297
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 37.0 (2.2) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Leaving the tag for others to attempt.

Comment 8

[Johan Lorenzo [:jlorenzo]]

Jovan: You can clone this repository[1] and run check_version.py.

The issue couldn't be reproduced, let's clear the 2.2 nomination, until we have more details about the builds.

[1] https://github.com/Mozilla-TWQA/B2G-flash-tool

Comment 9

[Jovan Gerodetti]

Build ID               20150407212508
Gaia Revision          922131eb994ed0db9b5d911e020d36bdf1d2cf18
Gaia Date              2015-05-26 08:05:06
Gecko Revision         c6d786be2960aa3bd8c6e7d68544795f6478f966
Gecko Version          37.0
Device Name            peak
Firmware(Release)      4.0.4.0.4.0.4
Firmware(Incremental)  46
Firmware Date          Tue Apr  7 20:51:13 CEST 2015

Yesterday I received a call and wasn't able to accept it. I had to reject it. The same person immediately called again and now I was able to accept the call and also could see who was calling. A few minutes later the same person called again and I was still able to accept the call.

Unfortunately my device wasn't plugged at the time I got the call.

Comment 10

[Johan Lorenzo [:jlorenzo]]

The gecko you have is from April 7th, but the Gaia is from last week. I don't think it'll change the results, but could you try to update gecko to a more recent version?

If it doesn't solve the issue, we'll need the RIL debugging and the gaia debug traces. You can activate the last one in the developer settings.

Comment 11

[Jovan Gerodetti]

Well I really would like to update, but Geeksphone dropped the support and building on OS X Yosemite does not work for me. 

I'm still trying to get a recent build but I'm not sure when that will be possible. So I guess it would be good to get RIL log already? Whats the way to do it?

Comment 12

[Johan Lorenzo [:jlorenzo]]

What problem do you have on OS X 10.9?

See comment 2 for the link to the instructions about RIL debugging.

Comment 13

[Jovan Gerodetti]

I had a thread about it in the dev-b2g mailing list:
https://groups.google.com/forum/#!searchin/mozilla.dev.b2g/build$20on$20yosemite/mozilla.dev.b2g/diKEtkyBFUY/yLiLYuNZlu8J

Comment 14

[Jovan Gerodetti]

Attachment: catlog.log

Today I received a call I couldn't accept while my phone was connected to via USB. So I immediately started adb logcat. I hope it's helpful.