Mit einem Firefox-OS-Gerät verbinden
Wenn Du mit einem Firefox-OS-Gerät eine Verbindung zur WebIDE versuchst und Dein Gerät wird nicht angezeigt, prüfe folgendes:
- Überprüfe die Version von Firefox OS:
Stell sicher, dass auf Deinem Gerät Firefox OS 1.2/ Boot2Gecko 1.2 oder höher läuft. Um die Version zu prüfen, starte die SettingsApp (Einstellungen) und gehe nachDevice Information > Software (Geräteinformationen > Software)
. Wenn Deine Version zu alt ist, finde dein Gerät im Developer Phone Guide und folge den Anweisungen zum Upgraden. - Erlaube das Remote Debugging (Entferntes debuggen):
In der SettingsApp (Einstellungen) gehe nachDevice Information > More information > Developer (Geräteinformation > Weitere Informationen > Entwickler).
sc- in Firefox OS 1.3 und früher: "Remote Debugging" ist eine einfach Checkbox - einfach anklicken.
- in Firefox OS 1.4 und später: "Remote Debugging" fragt ob nur ADB oder ADB und DevTools erlaubt werden sollen. Wähle hier "ADB und DevTools"
- Deaktiviere das Abschalten des Bildschirms:
- Deaktivieren das Abschlaten des Bildschirms:
In den Einstellungen auf Deinem Gerät (Settings-App) gehe nach "Bildschrim sperren" und nimm das Häckchen raus. Warum: wenn der Bildschirm gesperrt wird, verliert das Gerät die Verbindung und steht für das Remote Debugging nicht mehr zur Verfügung. - Achte darauf, daß kein anderes Android-Gerät zur selben Zeit mit dem Computer verbunden ist, ausser dem Firefox OS Gerät.
- Überprüfe das USB-Kabel:
- Zieh das USB-Kabel raus und verbinde es erneut.
- Prüfe das Kabel an einem anderen Rechner und auch an anderen USB-Anschlüssen.
- Versuche ein anderes USB-Kabel. Die mit dem Gerät mitgelieferten Kabel sind meist von minderer Qualität und fallen of aus.
- Versuche ein kürzeres USB-Kabel. Es ist bekannt, daß längere Kabel nicht so gut arbeiten.
- Deaktivere und Aktiviere erneut das Remote Debugging auf dem Firefox OS-Gerät.
- If you disabled the ADB Addon Helper, did you successfully run the
adb forward
command? - If you use Linux:
- Make sure you added add a
udev
rules file, as documented in step 3 of this guide to setting up an Android device. TheidVendor
attribute to use for the Geeksphone is "05c6", and this page lists otheridVendor
values.
- Make sure you added add a
- If you use Windows:
- You need to install drivers, as documented in step 3 of this guide to setting up an Android device. You can find drivers for Geeksphone devices on the Geeksphone web site and drivers for Google devices on Google web site. Windows 8 by default will not let you install unsigned drivers. See this tutorial on "How to install an unsigned driver on Windows 8".
- If WebIDE can't see your device after following all the steps, you may have to edit adb_usb.ini.
- If you use Mac OS X:
- If you're getting timeout errors connecting to both simulators and real devices, you may be unable to connect to localhost due to an empty /etc/hosts file. You can solve the problem by populating the file and flushing DNS cache as described here.
- If you're an EasyTether user, you will need to uninstall or disable EasyTether:
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
Unrestricted debugging (including certified apps, built-in apps, apps already installed on a device)
If you are finding that you can't debug certified apps, built-in apps, or apps already installed on a real device, then you may be coming across WebIDE's restricted privileges security policy. To find out more, see the section on Unrestricted app debugging (including certified apps, main process, etc.).
Connecting to Firefox for Android
If you're trying to connect to a Firefox instance running on the Android OS and it doesn't show up, here are some things you can try:
- Check your Firefox version: make sure your device is running Firefox 36 or higher. WebIDE will not detect older versions automatically, so you need to enable port forwarding and connect to the device port - follow the instructions here.
- Make sure you have enabled remote debugging in Firefox: open Firefox for Android, open its menu, select
Settings
, and then check the checkbox atDeveloper Tools > Remote debugging
. - Make sure that USB debugging is allowed in the device's developer settings
- If you still do not see your device in the WebIDE window, try toggling
Remote debugging
on the phone.- Disconnect your device from your computer and turn off
Remote debugging
on the phone. - Reconnect the device and turn on
Remote debugging
- this restarts the debugger instance on the phone. - Try connecting via WebIDE again.
- Disconnect your device from your computer and turn off
Connecting to other browsers (Chrome, Safari)
WebIDE makes use of Valence (formerly Firefox Tools Adapter) to reach other browsers, like Chrome and Safari.
If you are having trouble connecting to these other browsers, check the setup steps and other notes for those browsers on the Valence page.
Unable to load project list
If you open WebIDE in one version of Firefox, and then downgrade to a previous Firefox version with the same profile, you may see the error "Unable to load project list" when opening WebIDE in the earlier Firefox version.
This can occur when the storage system that WebIDE uses (IndexedDB) needs to move or restructure its internal files for the newer Firefox version. The project list then becomes effectively inaccessible to older versions of Firefox.
No data has been lost, but you will need to keep using the newest version of Firefox that was used with your profile to get the project list back.
If really want to use the older version of Firefox, you can attempt to delete just the project list in the following way, but this is unsupported and could result in the further problems or additional data loss:
- Close Firefox
- Find your Firefox profile directory
- Find the
storage
folder inside the profile directory - Under some part of this file tree, there should be files and/or directories that start with
4268914080AsptpcPerjo
(a hashed name of the database) - Remove any such files and directories
- Start Firefox and WebIDE again
Enable logging
You can also enable verbose logging to gather diagnostics:
- Open about:config, and add a new preference called
[email protected]
, with the string valueall
, and set[email protected]
totrue
. - In the Add-ons Manager, disable and then re-enable the ADB Helper add-on.
- Open the Browser Console and you'll now see console messages prefixed with
adb
. If the messages don't mean anything to you, ask for help.
Get help
Go to the #devtools room on IRC and we will try to help.