Editing Eclipse integration/Known issues
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
- | = Known Issues for Maemo Eclipse Integration Edition 2 Final release | + | = Known Issues for Maemo Eclipse Integration Edition 2 Final release = |
More detailed known issues lists can be found from Garage projects for each product https://garage.maemo.org/. | More detailed known issues lists can be found from Garage projects for each product https://garage.maemo.org/. | ||
- | |||
- | |||
- | |||
== Product baselines == | == Product baselines == | ||
Line 18: | Line 15: | ||
* Maemo SDK ARMEL rootstrap is meant to be used only for cross-compiling and it does not support running or debugging applications | * Maemo SDK ARMEL rootstrap is meant to be used only for cross-compiling and it does not support running or debugging applications | ||
* Diablo 4.1.2 device requires kernel patch from here http://tablets-dev.nokia.com/maemo-dev-env-downloads.php to be flashed to the Tablet for USB Networking to work with Windows host PC | * Diablo 4.1.2 device requires kernel patch from here http://tablets-dev.nokia.com/maemo-dev-env-downloads.php to be flashed to the Tablet for USB Networking to work with Windows host PC | ||
- | * Diablo 4.1.2 device requires hildon-desktop patch to be installed to the | + | * Diablo 4.1.2 device requires hildon-desktop patch to be installed to the Tablet from pc-connectivity Garage repository (see instructions from here http://pc-connectivity.garage.maemo.org/2nd_edition/main.html#SECTION00030000000000000000) for VNC client to work on host PC |
== Maemo Mica plugin framework for Eclipse == | == Maemo Mica plugin framework for Eclipse == | ||
- | |||
- | == Maemo ESbox for Eclipse == | + | == Maemo ESbox plugin for Eclipse == |
+ | * When running or debugging SBRSH applications using sandbox mode, applications cannot be terminated from the UI. | ||
* Hover help for Python does not work on ESBox because documentation has not been integrated. | * Hover help for Python does not work on ESBox because documentation has not been integrated. | ||
- | * | + | * Maemo Qt 4.5 support for Fremantle is only for Fremantle SDK but not for N900 device because N900 device does not have development environment available (Qt 4.5 works fine with Dibalo SDK and N8x0 devices). |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | == Maemo PluThon for Eclipse == | + | == Maemo PluThon plugin for Eclipse == |
* Hover help for Python for Maemo API documents does not work on Pluthon because documentation is not integrated | * Hover help for Python for Maemo API documents does not work on Pluthon because documentation is not integrated | ||
+ | * Python installation package creation with N900 device does not work because Python for Maemo Fremantle does not install python-distutil package to the device. N8x0 devices work fine. See https://bugs.maemo.org/show_bug.cgi?id=6161 | ||
== Maemo PC Connectivity == | == Maemo PC Connectivity == | ||
- | * Maemo PC Connectivity functionality with | + | * Maemo PC Connectivity functionality with N900 device and Fremantle is more limited than with N800/N810 device with Diablo |
** N900 will not support USB host mode | ** N900 will not support USB host mode | ||
*** no workaround (N900 HW issue) | *** no workaround (N900 HW issue) | ||
Line 51: | Line 44: | ||
*** Notice that USB mode changes are possible only if USB cable is plugged-out and plugged-in between mode changes with both applets | *** Notice that USB mode changes are possible only if USB cable is plugged-out and plugged-in between mode changes with both applets | ||
*** Notice that if both applets (platform default USB applet and PC Connectivity applet) are used for mode changes device may fail to change mode after first change | *** Notice that if both applets (platform default USB applet and PC Connectivity applet) are used for mode changes device may fail to change mode after first change | ||
+ | ** Fremantle platform does not have libicd-dummy package available until final release and thus user cannot navigate to Internet through the browser using USB and BlueTooth. He/she will be able to navigate only using WLAN (standard behavior) | ||
+ | *** final PC Connectivity release will have libicd-dummy package | ||
** Samba does not work with Fremantle platform and N900 causing disk mounts between N900 and Windows host PC to fail | ** Samba does not work with Fremantle platform and N900 causing disk mounts between N900 and Windows host PC to fail | ||
- | *** | + | *** will be (hopefully) fixed for final release |
** Fremantle platform and SDK support ONLY 16-bit color depth for X Server | ** Fremantle platform and SDK support ONLY 16-bit color depth for X Server | ||
*** workaround is to configure host PC X Server (in Windows and Mac OS X) to use 16-bit depth instead of default one (if default does not happen to be 16-bit) | *** workaround is to configure host PC X Server (in Windows and Mac OS X) to use 16-bit depth instead of default one (if default does not happen to be 16-bit) | ||
- | |||
- | |||
* Configuring connectivity to work between Maemo device and host PC after installation is still partly manual work on host PC side for all supported operating systems | * Configuring connectivity to work between Maemo device and host PC after installation is still partly manual work on host PC side for all supported operating systems | ||
- | * When creating a project and setting SBRSH as download method errors like "sbrsh server: fuse: bad mount point" and "sbrsh server: Can't mount to point:" | + | * When creating a project and setting SBRSH as download method quite often errors like "sbrsh server: fuse: bad mount point" and "sbrsh server: Can't mount to point:" happens. As a workaround you need to restart SBRSHD (on Maemo device side) and restart ESBox (on host PC side) |
- | + | * WLAN connection may get broken if using WLAN and USB Networking simultaneously. Connection problems may occur after some time (can take hours or days) when device is (re)started and WLAN tries to connect. | |
- | * WLAN connection may get broken if WLAN and USB Networking | + | |
** when the problem occurs user gets "Internet connection failed. Unable to retrieve IP address from server" error | ** when the problem occurs user gets "Internet connection failed. Unable to retrieve IP address from server" error | ||
- | ** workaround is to | + | ** workaround is to reflash Maemo device or manually assign IP number to the connection (which may cause problems with DHCP) |
- | * | + | * If FileZilla has already been installed to the Mac OS X host PC, installation of Host PC Connectivity with default settings fails |
- | + | ** workaround is to move FileZilla first to trash and then reinstall Host PC Connectivity or select not to install FileZilla with Host PC Connectivity | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | == Maemo SDK Virtual | + | == Maemo SDK Virtual Image == |
- | * | + | * NetworkManager is being started after Scratchbox, so the resolv.conf file used by Scratchbox may be invalid which causes network problems |
- | + | ||
* VMWare Player version 3.0 may have problems to keep ssh connection live in NAT mode (notice that VMWare Player 2.5 or Bridged mode works fine) | * VMWare Player version 3.0 may have problems to keep ssh connection live in NAT mode (notice that VMWare Player 2.5 or Bridged mode works fine) | ||
- | + | * Changing network configuration after installation of VMWare, VirtualBox or QEMu and Maemo SDK VIrtual Image may require reconfiguration of network also for the virtualisation environment and Maemo SDK. Usually, log in to the image and invoke "sudo dhclient". | |
- | * Changing network configuration after installation of VMWare, VirtualBox or | + | |
- | + | ||
== Maemo Flasher-3.5 Tool == | == Maemo Flasher-3.5 Tool == | ||
- | * | + | * Flasher-3.5 for Mac OS X supports only Mac OS X 10.6 Snow Leopard. Flasher-3.5 binary built for 10.6 does not work with Mac OS X 10.5 Leopard but requires new build and new 10.5 binary to be added to the Mac installation package. |
+ | ** will be fixed to the final release | ||
== Integration testing == | == Integration testing == | ||
- | * Some | + | * Some publically available test suites (for Eclipse components and NFS mounts, for example) are run on Linux, Windows and Mac OS X during integration testing but frameworks and test sets are not yet ready to be published |
+ | |||
* Test results (for unit tests and integration tests) for official releases are not yet ready to be published together with products | * Test results (for unit tests and integration tests) for official releases are not yet ready to be published together with products | ||
Learn more about Contributing to the wiki.