Closed Bug 909855 Opened 11 years ago Closed 11 years ago

[PEAK] Cell connection doesn't work at all

Categories

(Firefox OS Graveyard :: Vendcom, defect)

ARM
Gonk (Firefox OS)
defect
Not set
major

Tracking

(blocking-b2g:-, b2g-v1.1hd affected)

RESOLVED DUPLICATE of bug 924999
blocking-b2g -
Tracking Status
b2g-v1.1hd --- affected

People

(Reporter: mcepl, Unassigned)

Details

(Keywords: regression)

Attachments

(3 files)

Attached file logcat.txt
It is like two weeks or so when the nightlies for Peak seem to be very much willing to loose a connection (both Wifi at home where I have perfect coverage with a strong signal) and sometimes even cellphone (so that people tell me they couldn't call me, even though I was sitting whole day next to my phone without knowing it disconnected from the cell network).

Known bug? Which logs should I send?

Device: PEAK
Image version: NIGHTLY
BuildID: 20130818082717
Host OS: Linux/more or less Fedora 19 (kernel 3.10.0-4.el7.x86_64)
More info: My carrier is Czech Telefonica O2, attached is output of adb logcat from the phone with already missing both wifi and cell connection)
OS: Linux → Gonk (Firefox OS)
Hardware: x86_64 → ARM
matej@wycliff: ~$ adb logcat -b radio|&tee logcat.txt
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
E/RILD    (  159): **RIL Daemon Started**
E/RILD    (  159): **RILd param count=1**
E/RILD    (  159): RIL_Init argc = 5 client = 0
E/RILPROXY(  120): Could not connect to rild socket, retrying: Connection refused
E/RILPROXY(  120): Could not connect to rild socket, retrying: Connection refused
E/RILPROXY(  120): Could not connect to rild socket, retrying: Connection refused
E/RILPROXY(  120): Could not connect to rild socket, retrying: Connection refused
W/RILC    (  159): RIL_onUnsolicitedSendResponse called before RIL_register
E/RILC    (  159): RIL_register: RIL version 6
E/RILC    (  159): s_registerCalled = 1, s_started = 1, RIL_getMaxNumClients = 1

This is with today's nightly from Geeksphone (BUILD ID: 20130827082743)
Severity: normal → major
Attached file logcat.txt
Wifi more or less works with the current 1.1HD branch from Geeksphone images, but GSM connection is still very problematic (which kind of sucks ... I would love to be accessible via my phone; I know, I know, I shouldn't use developer's phone for the normal traffic ... OTOH, you will never get that comprehensive testing).

Anyway, I have added more details on http://forum.geeksphone.com/index.php?topic=5622.msg60731#msg60731 where I have also attached this fresh logcat from booting up the phone to the full desktop (but without GSM connection active).
I confirm this bug.

phone/data network connection gets lost at random times. Only emergency calls are available.
When trying to call a normal number, the message "please turn off airplane mode" appears while airplane mode is not toggled on.

Restarting the phone did not help; only updating the phone with a newer image did make the problem disappear (for now).

It might be a nightly build, but this is pretty bad 4 months after release.
blocking-b2g: --- → hd?
Keywords: regression
Hello Mozilla people,

I don't mean to bitch or anything, but this bug is a real show-stopper as far as v1.1 is concerned.
If you need us to run commands or try things so you get a better understanding of the problem, by all means please let us know.
If this is a known regression and you are working on it, please let us know.

At the moment, this turns the phone into an expensive door stop :P
Attached file logcat-phone-on02.txt
So we have progress! With the latest 1.1hd images from geeksphone, we seem to have reliably working phone connection (THANK YOU!), but wrong indicators (they still show that only Emergency Calls are available though I can call/receive both voice calls and SMS).

I have now tried 1.2hd image from http://downloads.geeksphone.com/peak/latest_v1.2.html and we are back at square one. Wifi works, but there is no cell-network connection whatsoever.

See attached log from the start of the phone (from the SIM card PIN entry page).
(In reply to Matěj Cepl from comment #5)

> So we have progress! With the latest 1.1hd images from geeksphone, we seem
> to have reliably working phone connection (THANK YOU!), but wrong indicators
> (they still show that only Emergency Calls are available though I can
> call/receive both voice calls and SMS).

This is bug 903700 I think.
(In reply to Hubert Figuiere [:hub] from comment #6)
> (In reply to Matěj Cepl from comment #5)
> 
> > So we have progress! With the latest 1.1hd images from geeksphone, we seem
> > to have reliably working phone connection (THANK YOU!), but wrong indicators
> > (they still show that only Emergency Calls are available though I can
> > call/receive both voice calls and SMS).
> 
> This is bug 903700 I think.

Most likely, but it is comparatively minor issue comparing to this bug which changes my phone to too small tablet.
With the Geeksphone image ID 201310050003338 I have another variant of this problem: cell phone connection works reliably (at least that!), but wifi connection after some time closes (not sure how long exactly; something around a minute? or perhaps it relates to how much active the connection is before it is terminated). When the connection is manually switched off and back on(in Settings), it works again (for the same short amount of time).
Summary: Connection gets lost (both wifi and cell) with the latest nightlies. → [PEAK] Connection gets lost (both wifi and cell) with the latest nightlies.
Not blocking the v1.1hd release with this bug as it is so far only observed on peak, which is not the target launch device for the release.

Shawn, can you however check the logs available and provide some feedback if there's anything valuable?
blocking-b2g: hd? → -
Flags: needinfo?(sku)
There is nothing I could help to check (lack of RIL related information).
only stk setup menu is reported, and one SIM EF is requested.



E/GeckoConsole(  125): [JavaScript Error: "stack is undefined" {file: "app://system.gaiamobile.org/js/trusted_ui.js" line: 293}]
I/GeckoDump(  125): Crash reporter : Submitting crash: 0bfade49-da64-8aa7-1235687d-25c38c98
Flags: needinfo?(sku)
(In reply to Wayne Chang [:wchang] from comment #9)
> Not blocking the v1.1hd release with this bug as it is so far only observed
> on peak, which is not the target launch device for the release.

Supporting only unreleased hardware is so great strategy how to avoid those pesky users with all their stupid complaints! I will have to suggest this strategy to my boss! ... errr, we actually depend on those users. Oh well :(
Just updating the name ... it got fixed for 1.1HD, but I still cannot use 1.2HD (I haven't dared to try higher versions with this bug being completely ignored by everybody).
blocking-b2g: - → 1.3?
Component: Wifi → Hardware
Summary: [PEAK] Connection gets lost (both wifi and cell) with the latest nightlies. → [PEAK] Cell connection doesn't work at all
(In reply to Matěj Cepl from comment #12)
> Just updating the name ... it got fixed for 1.1HD, but I still cannot use
> 1.2HD (I haven't dared to try higher versions with this bug being completely
> ignored by everybody).

Peak isn't a target production device, so this can never block the release. In fact, this is likely a bug on geeksphones side, not our side. Please contact their support to get help on this.
blocking-b2g: 1.3? → -
Component: Hardware → Vendcom
(In reply to Jason Smith [:jsmith] from comment #13)
> Peak isn't a target production device, ...

Right ... when MoFo gets into too close contact with phone company it starts to behave like them and starts to lie to their customers. https://hacks.mozilla.org/2013/04/geeksphone-to-start-selling-firefox-os-developer-preview-phones/ ... "Mozilla, Geeksphone and Telefonica have been working together to create a Firefox OS developer preview phone, ..." and half a year later you don't care because you jumped on new shiny model.

OK, I accept that you haven't got any money from me, so you don't me anything. Lesson learned ... I still want to believe in the Web-based phone experience, but obviously Firefox OS won't be the one, because MoFo won't deal with the manufacturers (or it cannot deal with them), and in the end will let users of their OS on their own.
Let's finish this unfortunate bug here.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
The original Peak's got official Firefox logo... makes me feel like a sucker to have bought this device to see it being dropped by Mozilla only 6 months after release. Nice going.
Nobody has "dropped" support for this device, it was always for Geeksphone to support it and they are doing that.
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #17)
> Nobody has "dropped" support for this device, it was always for Geeksphone
> to support it and they are doing that.

My comment refers to the shift from "Mozilla, Geeksphone and Telefonica have been working together to create a Firefox OS developer preview phone, ..." to "Peak isn't a target production device".

Disappointing. Anyway last comment from me in this closed bug.
It never was a "target production device", but a "developer preview device", from Mozilla's POV.
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #19)
> It never was a "target production device", but a "developer preview device",
> from Mozilla's POV.

Which sounds like a pretty bad legalese to get out of the responsibility (I can say it as a former lawyer ;)).

Anyway, let's hope, there is a brighter future at bug 924999.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: