Closed Bug 924999 Opened 11 years ago Closed 10 years ago

Telephony ( SIM / RIL ) seems broken for 1.2 Keon devices

Categories

(Firefox OS Graveyard :: GonkIntegration, defect)

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: armenzg, Unassigned)

References

Details

(Whiteboard: [from-geeksphone])

Attachments

(1 file)

log.txt
3.37 MB, text/plain
Details 
Phone type (Keon, Peak, other): Keon
OS version (Settings>Device information>More information>): 1.2.0.0-prerelease
Build Identifier (...>More information>): 20131008225041
Update channel (...>More information>): default

Steps to Reproduce:
1) follow steps in http://downloads.geeksphone.com/drivers/Manual_flash_geeksphone-eng.txt
2) with 1.2 image: http://downloads.geeksphone.com/keon/latest_v1.2.html

NOTE: you have to modify the flash_mac.sh file to use $REPLY instead of $yn to be able to proceed (bug 924947)

Expected Result:
* flash phone and you can make calls and send text messages

Actual Result:
* flash phone and you can _not_ make calls and send text messages

Is this issue sometimes or always reproducible: Yes
FTR, I went from 1.0.0.x to 1.3.x and then downgraded to 1.2.x since I thought it would be the right target to test.
I don't know if when I upgraded to 1.3.x I had carrier services and it got broken when downgrading to 1.2.x.
Attached file log.txt — 
I managed to get a push through, however, it took an eternity.
I got a log to help spot issues. The size of the log is kind of ridiculous.
(In reply to Armen Zambrano [:armenzg] (Release Engineering) (EDT/UTC-4) from comment #2)
> Created attachment 815423 [details]
> log.txt
> 
> I managed to get a push through, however, it took an eternity.
> I got a log to help spot issues. The size of the log is kind of ridiculous.

This comment was not for this bug.
I've tried resetting the phone through software.
I have tried flashing 1.2.x again and saying "No" to preserving the data.
I have tried upgrading back to 1.3.x again and saying "No" to preserving the data.
I'm going to try 1.1.x and 1.0.x
I will also try using the MDN instructions.
It might be an issue with the RIL for the build. 
Can you turn the ril debug on : 

 adb pull /system/b2g/defaults/pref/user.js .
 < edit user.js and set "ril.debugging.enabled" to true >
 adb shell mount -o remount,rw /system
 adb push user.js /system/b2g/defaults/pref
 adb shell mount -o remount,ro /system
 adb shell sync && adb reboot

And then give us a logcat based on : adb logcat -b radio
please?
I thought I was on 1.3.x, however, after I applied the update I found myself on 1.1.1.x

For my own sanity, here's a working state:
1.1.1.0-prerelease
18.1
20131001050209
Git commit: 2013-09-27 22:32:29
Last updated: 10/10/2013

######################################################

1.2.x on Keon seems to have telephony broken.
Is there any value on me testing 1.1 until it gets fixed?

1.2.0.0-rerelease
26.0a2
20131009225222
Git commit: 2013-10-09 18:58:09


### 1.2 flashing steps output: ###
Armens-MacBook-Air 1.2-latest $ unzip images-keon-v1.2-2013-10-09.Gecko-9240f5c.Gaia-51f3c79.zip 
Archive:  images-keon-v1.2-2013-10-09.Gecko-9240f5c.Gaia-51f3c79.zip
  inflating: adb                     
  inflating: adb.exe                 
  inflating: AdbWinApi.dll           
  inflating: AdbWinUsbApi.dll        
  inflating: boot.img                
  inflating: fastboot                
  inflating: fastboot.exe            
  inflating: flash.bat               
  inflating: flash_mac.sh            
  inflating: flash.sh                
  inflating: recovery.img            
  inflating: system.img              
  inflating: userdata.img            
Armens-MacBook-Air 1.2-latest $ adb devices
List of devices attached 
full_keon       device

# I have to change $yn to $REPLY
Armens-MacBook-Air 1.2-latest $ vi flash_mac.sh 
Armens-MacBook-Air 1.2-latest $ ./flash_mac.sh 
< waiting for device >
sending 'boot' (3424 KB)...
OKAY [  0.323s]
writing 'boot'...
OKAY [  0.625s]
finished. total time: 0.948s
Do you want to keep your user data ? (Some users has problems in first reboot, if you have, please reflash and select not to keep the data)
1) Yes
2) No
#? No
sending 'userdata' (26364 KB)...
OKAY [  2.444s]
writing 'userdata'...
OKAY [  4.885s]
finished. total time: 7.330s
sending 'system' (152580 KB)...
OKAY [ 14.051s]
writing 'system'...
OKAY [ 28.469s]
finished. total time: 42.520s
sending 'recovery' (4556 KB)...
OKAY [  0.429s]
writing 'recovery'...
OKAY [  0.831s]
finished. total time: 1.260s
erasing 'cache'...
OKAY [  0.006s]
finished. total time: 0.006s
rebooting...

finished. total time: 0.001s
Summary: Following flash instructions for Keon leaves the phone without being able to connect to a phone carrier (make phone calls or send text messages) → Telephony seems broken for 1.2 and 1.3 on Keon devices
:nhirata, does it still have value doing your requested steps on comment 5?

I've verified that flashing back to 1.1 and telephony works again.

I assume there's no value on testing 1.1 since we have already released it.

I will go back to my Android until 1.2 has telephony working again.
Flags: needinfo?(nhirata.bugzilla)
My guess is that the RIL is outdated for 1.2/1.3; I was wanting to confirm that with your logcat and hope that there was some evidence there, rather than just assuming.  :)
Flags: needinfo?(nhirata.bugzilla)
Is this good?

Armens-MacBook-Air 1.2-latest $ adb logcat -b radio
E/RILD    (  111): **RIL Daemon Started**
E/RILD    (  111): **RILd param count=1**
E/RILD    (  111): RIL_Init argc = 5 client = 0
E/RILPROXY(  108): Could not connect to rild socket, retrying: Connection refused
E/RILPROXY(  108): Could not connect to rild socket, retrying: Connection refused
E/RILPROXY(  108): Could not connect to rild socket, retrying: Connection refused
E/RILPROXY(  108): Could not connect to rild socket, retrying: Connection refused
E/RILPROXY(  108): Could not connect to rild socket, retrying: Connection refused
W/RILC    (  111): RIL_onUnsolicitedSendResponse called before RIL_register
E/RILC    (  111): RIL_register: RIL version 6
E/RILC    (  111): s_registerCalled = 1, s_started = 1, RIL_getMaxNumClients = 1
I flashed 1.1 (which has working telephony) and I get the same output:

Armens-MacBook-Air 1.1 $ adb logcat -b radio
E/RILD    (  118): **RIL Daemon Started**
E/RILD    (  118): **RILd param count=1**
E/RILD    (  118): RIL_Init argc = 5 client = 0
E/RILPROXY(  111): Could not connect to rild socket, retrying: Connection refused
E/RILPROXY(  111): Could not connect to rild socket, retrying: Connection refused
E/RILPROXY(  111): Could not connect to rild socket, retrying: Connection refused
E/RILPROXY(  111): Could not connect to rild socket, retrying: Connection refused
E/RILPROXY(  111): Could not connect to rild socket, retrying: Connection refused
W/RILC    (  118): RIL_onUnsolicitedSendResponse called before RIL_register
E/RILC    (  118): RIL_register: RIL version 6
E/RILC    (  118): s_registerCalled = 1, s_started = 1, RIL_getMaxNumClients = 1


when I have a locked screen I can see above the time a message of "no network".
Nevertheless, I can see radio bars and I can dial a number without getting an "airplane mode" message.
The differences in user.js between the two are quite significant.
nhirata: why do you think the logcat output for both 1.1 and 1.2 are the same even though radio only works on 1.1?
Flags: needinfo?(nhirata.bugzilla)
Hrm, ok.  I guess I dismissed this a little too early.

I guess it may just have been that we haven't seen enough of the logcat.  Could we get more of the logcat for 1.2 and 1.1 please?
Flags: needinfo?(nhirata.bugzilla)
I was still successfully using a keon on a central/master build last week (and for the past 2 months I think, riding central/master).

I wonder if geeksphone's img is somehow broken.

> Could not connect to rild socket, retrying: Connection refused

definitely doesn't look good.
In 1.1 is working fine. There is any changes in the way that gecko communicate with RIL in 1.2? There is any difference in the code between central/master and 1.2 that could be causing this issue?

We just build the images using the 1.2 code.
(In reply to Geeksphone from comment #15)
> In 1.1 is working fine. There is any changes in the way that gecko
> communicate with RIL in 1.2?

needinfo-ing Hsin Yi about that :)
Flags: needinfo?(htsai)
nhirata: there's no more output.

This is from nightly:
Armens-MacBook-Air nightly $ adb logcat -b radio
E/RILD    (  120): **RIL Daemon Started**
E/RILD    (  120): **RILd param count=1**
E/RILD    (  120): RIL_Init argc = 5 client = 0
E/RILPROXY(  114): Could not connect to rild socket, retrying: Connection refused
E/RILPROXY(  114): Could not connect to rild socket, retrying: Connection refused
E/RILPROXY(  114): Could not connect to rild socket, retrying: Connection refused
E/RILPROXY(  114): Could not connect to rild socket, retrying: Connection refused
W/RILC    (  120): RIL_onUnsolicitedSendResponse called before RIL_register
E/RILC    (  120): RIL_register: RIL version 6
E/RILC    (  120): s_registerCalled = 1, s_started = 1, RIL_getMaxNumClients = 1
Summary: Telephony seems broken for 1.2 and 1.3 on Keon devices → Telephony seems broken for 1.2 Keon devices
(In reply to Etienne Segonzac (:etienne) from comment #16)
> (In reply to Geeksphone from comment #15)
> > In 1.1 is working fine. There is any changes in the way that gecko
> > communicate with RIL in 1.2?
> 
> needinfo-ing Hsin Yi about that :)

I compared mozillaorg/v1.0.1 and mozillaorg/v1.2. Bug 826931 changes the way to talking to rild.
Flags: needinfo?(htsai)
(In reply to Armen Zambrano [:armenzg] (Release Engineering) (EDT/UTC-4) from comment #17)
> nhirata: there's no more output.
> 
> This is from nightly:
> Armens-MacBook-Air nightly $ adb logcat -b radio
> E/RILD    (  120): **RIL Daemon Started**
> E/RILD    (  120): **RILd param count=1**
> E/RILD    (  120): RIL_Init argc = 5 client = 0
> E/RILPROXY(  114): Could not connect to rild socket, retrying: Connection
> refused
> E/RILPROXY(  114): Could not connect to rild socket, retrying: Connection
> refused
> E/RILPROXY(  114): Could not connect to rild socket, retrying: Connection
> refused
> E/RILPROXY(  114): Could not connect to rild socket, retrying: Connection
> refused
> W/RILC    (  120): RIL_onUnsolicitedSendResponse called before RIL_register
> E/RILC    (  120): RIL_register: RIL version 6
> E/RILC    (  120): s_registerCalled = 1, s_started = 1, RIL_getMaxNumClients
> = 1

As you can see in this line: 
> W/RILC    (  120): RIL_onUnsolicitedSendResponse called before RIL_register

The problem is that it tries to talk to rild before rild is up. This is not the error, because after some time it tries again an get a connection.
(In reply to Hsin-Yi Tsai (OOO 10/2 ~ 10/13)  [:hsinyi] from comment #18)
> (In reply to Etienne Segonzac (:etienne) from comment #16)
> > (In reply to Geeksphone from comment #15)
> > > In 1.1 is working fine. There is any changes in the way that gecko
> > > communicate with RIL in 1.2?
> > 
> > needinfo-ing Hsin Yi about that :)
> 
> I compared mozillaorg/v1.0.1 and mozillaorg/v1.2. Bug 826931 changes the way
> to talking to rild.

And between 1.1.0hd and 1.2? Because in 1.1.0.hd is working ok. I will take a look...
Summary: Telephony seems broken for 1.2 Keon devices → Telephony ( SIM / RIL ) seems broken for 1.2 Keon devices
I have flashed my device on today's Keon 1.2 build and calling and receiving calls works.

However, neither 3g nor wifi seem to be working
sms also working on today's fresh flash of a 1.2
Preeti, can you help us driving this? Seems like the hardware functionality problems are going to hinder us in driving 1.2 to a good end, in particular with many of the localizer doogfood phones being keons.
FYI, I'm seeing this every now and then on the Peak with m-c/master ("nightly", currently 1.3), and after restarting once or twice or more times, it works fine, so it sounds to me like an intermittent race condition or something.
I have also hit it on my ZTE Open with a self-compiled 1.2 once or twice, but very rarely.

(In reply to Geeksphone from comment #19)
> The problem is that it tries to talk to rild before rild is up. This is not
> the error, because after some time it tries again an get a connection.

The first part sounds like the race condition,maybe it's more likely on the Peak due to the dual core processor (AFAIK all phones currently on the market are single core).

If it really tries again, though, I wonder why it never succeeds....
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #24)
> 
> (In reply to Geeksphone from comment #19)
> > The problem is that it tries to talk to rild before rild is up. This is not
> > the error, because after some time it tries again an get a connection.
> 
> The first part sounds like the race condition,maybe it's more likely on the
> Peak due to the dual core processor (AFAIK all phones currently on the
> market are single core).
> 
> If it really tries again, though, I wonder why it never succeeds....

Maybe because it has some kind of counter, that when it reaches to its limit it stops trying to connect. But it's only a thinking, i'm not sure about it, because I search for it and didnt find anything.
Oh, and i repeat my question. There is any change between 1.1 and 1.2 in gecko about RIL?
(In reply to Geeksphone from comment #26)
> Oh, and i repeat my question. There is any change between 1.1 and 1.2 in
> gecko about RIL?

Quite a lot. Please see https://wiki.mozilla.org/NewAPIsInFxOS1.2#RIL.2FTelephony for more information.
Well, i was thinking about a more specific information about which of this changes could make that only when the device is rebooted some times it gets network. Because there is no change in our base between 1.1 and 1.2 and in 1.1 is woking ok.
I've just updated to images-keon-v1.2-2014-01-09.Gecko-0f36774.Gaia-539a25e.zip and Telephony seems to work fine :-)
(In reply to Ognyan Kulev from comment #30)
> I've just updated to
> images-keon-v1.2-2014-01-09.Gecko-0f36774.Gaia-539a25e.zip and Telephony
> seems to work fine :-)

a) I am not sure whether the problem was same on Keon as on Peak,
b) Even not all users of Peak had the problem.

Did you have the problem before when trying 1.2?
Flags: needinfo?(ogi)
(In reply to Matěj Cepl from comment #31)
> a) I am not sure whether the problem was same on Keon as on Peak,
> b) Even not all users of Peak had the problem.
> 
> Did you have the problem before when trying 1.2?

Yes, I did have problems in 2013-10 with my Keon. v1.2 Telephony didn't work at all despite trying things like wiping user data.

Yesterday I upgraded to v1.2 and after the first boot, it asked about SIM PIN but Telephony didn't work. I rebooted and Telephony works since then. I've made several calls too.

Today I upgraded to v1.3 and it works too :-)
Flags: needinfo?(ogi)
I have Keon v1.2 images from 2013-10-14 and I just re-flashed the Keon with wiping user data. Telephony didn't work even after rebooting a couple of times. Build Identifier is 20131014225246. Git commit info is 2013-10-14 14:36:58 94e3088c56c73....

I agreed to do System update (105.84 MB). After the first boot, Telephony worked. Build Identifier and Git commit info remain the same as above! Something is not correct with this update process, it's the same build. After next reboots Telephony don't work. If I do System update again, Telephony works after the first boot and not afterwards. Build Id stays the same.

Then I upgraded to v1.2 2014-01-09 via USB. Telephony worked after the first boot. I rebooted a couple of times and Telephony works every time.

Summary: v1.2 2013-10-14 Telephony doesn't work except right after trying System update that always fails. v1.2 2014-01-09 Telephony works except one time: the first boot after upgrading without wiping user data.

I hope this helps.
It is working now.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
(In reply to Armen Zambrano (*team week* on the week of the 28th) [:armenzg] (EDT/UTC-4) from comment #34)
> It is working now.

Which version? And you claim that phone is working with Peak and that version?
Flags: needinfo?(armenzg)
I will take a while to reply to this as I'm at a work week.
Actually, I can comment that I have upgraded to 1.4 myself with my Peak (and lost all my data ... oh well), and suddenly telephone works.

THANK YOU, THANK YOU, MOZILLA, THANK YOU!
Flags: needinfo?(armenzg)
This bug is present in v1.4 on keon devices in Gecko-b23f3b3.Gaia-2f0c49e build from geeksphone site. Adb shows the same output as in comment #47 . I noticed that some people mentioned to restart phone several times and wipe all data but the result is the same: no usable network.
My bad, the relevant comment is comment #17
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: