Changes

*** adb doesn't seem to see the deviceand you're using linux and you've checked all the bullet points below? [https://developer.mozilla.org/en-US/Firefox_OS/Firefox_OS_build_prerequisites#For_Linux.3A_configure_the_udev_rule_for_your_phone enable the permissions in udev rules]** Second: turn on "adb" support on your device and make sure the logcat stays connected even when the screen locks / the display turns off. You have to have both:*** [See https://developer.mozilla.org/en-US/Firefox_OSdocs/Firefox_OS_usage_tipsTools/Remote_debugging WebIDE#Connecting_a_Firefox_OS_device which mentions how to go to the settings UI and enable "Remote Debugging" from the "remote debuggingDeveloper" enabled] (which is what makes logcat work at all) menu and disabling the screen lock from the settings app"Screen Lock" menu.*** you need to disable Capture the lock screen in order for logcat to remain connected.!*** (There are other ways It is very important that you capture the logcat to make this happen, but they are technical a file and I don't know themthat you start the capture process before reproducing the bug. Feel free to edit (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 wiki and include instructions herelogic.)** Please provide * Running logcat:**** Want to see the logcat by running log as it happens and you are using linux or OS X? ***** Run '''adb logcat -v time -s GeckoDump:V Gecko:V GeckoConsole:V OomLogger:V | tee FILENAME-TO-LOG-TO'''. Please start running this command BEFORE you attempt to reproduce the problem. Once you are done, hit control-C and send us the file.**** Using windows or that gave you an error about the command "tee" not existing? Use file redirection:***** Run '''adb logcat uses a circular buffer that discards older entries when the buffer fills up, so if -v time -s GeckoDump:V Gecko:V GeckoConsole:V OomLogger:V > FILENAME-TO-LOG-TO'''. Please start running this command BEFORE you run logcat only after attempt to reproduce the problem happens, you may not have all of the logic. Once you are done, hit control-C and send us the file. *** (What did all those cool flags do?)

*** Make sure the log file does not include any private information / redact any private information**** AlsoThe email app tries hard to avoid including private information, please only include portions of but the log may contain activity from other apps. Specifically, the e-mail email app; searching for "LOGmay include: Mail universe/bridge created" is ***** Your email address (if creating a good way to find out when new account)***** The domain of the e-mail app started. Apparentlyserver you use (anytime we connect to a server, other apps are much more likely and especially during creating a new account)**** It's okay to reveal private dataedit the file, including using search-and we do not want any of -replace to change domain names or stuff like that. We do try to avoid doing thatIf you remove some lines entirely, but please also skim the contents of the log it can be helpful to make sure there are no obvious reveals of personal information. Currentlyyou tell us that, we expect the e-mail domain you are signing up for to be exposed possibly by writing in the log if your problem occurs during the configuration process, but we really need that info anywayswhat was removed.