Confirm
360
edits
Changes
no edit summary
; A log of what was happening around the time the problem happened: This can take the form of the GeckoDump logcat category or a log generated by the secret debug mechanism.
* logcat log of what the e-mail app was doing:
** Make sure that e-mail logging is enabled. It probably isHave the "adb" command available and usable. If you are running can type "adb logcat " with the device plugged in and see some junk show up (especially "LOG: Mail universe/bridge created, notifying"when you start the e-mail app from when it was closed), then it's working! Congrats! No adb? Otherwise, to turn it onNot working? then:*** You can enable the preference in your own gaia builds by creating a file GAIAno adb? [https:/build/custom-prefsdeveloper.mozilla.js (note: this used to be GAIAorg/customen-prefs.js, but it changed) and making sure it includes the line: pref("browser.dom.window.dump.enabled", true);US/Firefox_OS/Firefox_OS_build_prerequisites#Install_adb install adb]*** I hope thereadb doesn's a better way, but if not, if you just want t seem to change the setting on see the device, you will need to modify ? [https:/data/b2gdeveloper.mozilla.org/mozillaen-US/PROFILEDIRFirefox_OS/prefsFirefox_OS_build_prerequisites#For_Linux.js to include 3A_configure_the_udev_rule_for_your_phone enable the line. See below for one way to do this.permissions in udev rules]** Second: make sure the logcat stays connected even when the screen locks / the display turns off. You have to have both :*** [https://developer.mozilla.org/en-US/Firefox_OS/Firefox_OS_usage_tips/Remote_debugging "remote debugging" enabled ] (which is what makes logcat work at all), and from the settings app*** you need to disable the lock screen in order for logcat to remain connected. *** (There are other ways to make this happen, but they are technical and I don't know them. Feel free to edit the wiki and include instructions here.)
** Please provide the logcat by running '''adb logcat -v time -s GeckoDump:V Gecko:V | tee FILENAME-TO-LOG-TO'''. Please start running this command BEFORE you attempt to reproduce the problem. logcat uses a circular buffer that discards older entries when the buffer fills up, so if you run logcat only after the problem happens, you may not have all of the logic. Once you are done, hit control-C and send us the file.
**** The logcat arguments filter out a lot of the noise that we don't care about and gives us timestamps.
== Setting the dump() preference ==
This hopefully isn't needed anymore. I think this is all out of date if it is.
Thanks to Dave Hylands for steps here:
