Confirmed users
2,204
edits
Gaia/Hacking: Difference between revisions
Jump to navigation
Jump to search
→Blank screen when b2g starts
| Line 358: | Line 358: | ||
=== Blank screen when b2g starts === | === Blank screen when b2g starts === | ||
When you start b2g using <code>b2g -profile $GAIA/profile</code> a blank screen shows up and you see an error <code>Cannot reach app://system.gaiamobile.org</code>. To fix this there are a couple of things you can check | When you start b2g using <code>b2g -profile $GAIA/profile</code> a blank screen shows up and you see an error <code>Cannot reach app://system.gaiamobile.org</code>. To fix this there are a couple of things you can check | ||
# Rebuild the gaia profile using <code>DEBUG =1 make profile</code> in the $GAIA directory | # Rebuild the gaia profile using <code>DEBUG=1 make profile</code> in the $GAIA directory | ||
# Run b2g again | # Run b2g again | ||
# If this doesn't fix it, check if there is any other process listening on port 8080. The default profile of gaia starts [https://developer.mozilla.org/en-US/docs/Httpd.js/HTTP_server_for_unit_tests httpd.js], which listens on port 8080. When running a debug profile, b2g connects to [http://localhost:8080 localhost:8080]. If some other process is running on port 8080, b2g will fail to display the home screen of gaia | # If this doesn't fix it, check if there is any other process listening on port 8080. The default profile of gaia starts [https://developer.mozilla.org/en-US/docs/Httpd.js/HTTP_server_for_unit_tests httpd.js], which listens on port 8080. When running a debug profile, b2g connects to [http://localhost:8080 localhost:8080]. If some other process is running on port 8080, b2g will fail to display the home screen of gaia | ||
## To find out if this is the case, you can enable logging on httpd.js. The httpd.js in the profile resides in this location - <code>$GAIA/profile/extensions/httpd/content/httpd.js</code>. Edit the variable <code>var DEBUG=false;</code> to change the <code>DEBUG</code> to <code>true</code>. Save the file and restart b2g. On the console now, you will be able to view the <code>httpd's</code> logs | ## To find out if this is the case, you can enable logging on httpd.js. The httpd.js in the profile resides in this location - <code>$GAIA/profile/extensions/httpd/content/httpd.js</code>. Edit the variable <code>var DEBUG=false;</code> to change the <code>DEBUG</code> to <code>true</code>. Save the file and restart b2g. On the console now, you will be able to view the <code>httpd's</code> logs | ||