If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[Keon] Sometimes, Firefox OS is crashing after receiving a sms or call

UNCONFIRMED
Unassigned

Status

Firefox OS
Gaia
--
major
UNCONFIRMED
3 years ago
3 years ago

People

(Reporter: Marcela Oniga, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:30.0) Gecko/20100101 Firefox/30.0 (Beta/Release)
Build ID: 20140608211132

Steps to reproduce:

1. Receive a sms or a call
2. Right after hanging up, close all the apps (long tap on homescreen).


Actual results:

Sometimes, after hanging up or after reading a sms the OS is crashing. The message "firefox OS crashed" is displayed on the bottom screen and I'm forced to reboot the phone.

This issue is reproducing using Keon device, build identifier 20140727221949 , OS version 2.1.0.0. prerelease.

@Marcia can you please explain how to get the crash logs from the device? I tried with "adb shell ls -l /data/b2g/mozilla/Crash\ Reports/submitted/" command but I get "error: insufficient permissions for device". I also tried to open the device in safe mode but I haven't figured it out where exactly are the crash logs. Please assist, your answer is hightly appreciated.


Expected results:

All the opened apps should be closed, no errors.
(Reporter)

Updated

3 years ago
Severity: normal → major
Marcela: If you cannot get the crash report from the command line on the Keon, I am not sure if you can get them other ways (Geeksphone does their builds differently). Typically another way to do it is to open ADB with ddms (uses java) and then navigate to the file explorer. Under data | b2g | mozilla | Crash Reports you will find the pending and submitted reports and you can copy them to your desktop.
Summary: Sometimes, Firefox OS is crashing after receiving a sms or call → [Keon] Sometimes, Firefox OS is crashing after receiving a sms or call
You need to log in before you can comment on or make changes to this bug.