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.

Learn more about Contributing to the wiki.

= Known Issues for Maemo Eclipse Integration Edition 2 Final release (R2.0.0) =

More detailed known issues lists can be found from Garage projects for each product https://garage.maemo.org/.

Detailed list of new features implemented to Maemo Eclipse Integration since previous PreFinal release together with feature plan for final release is here: [[Eclipse integration]].

[[Eclipse_integration/ReleaseNotes_final|Release Notes are available]].

== Product baselines ==

* N900 device with Maemo Fremantle 5.x platform releases
* Fremantle 5.0 SDK, the latest final release
* N8x0 devices with Maemo Diablo 4.1.x platform releases
* Diablo 4.1.2 SDK, the latest maintenance release

== Product configuration ==

* 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 hildon-desktop patch to be installed to the Maemo device from pc-connectivity Garage repository (see instructions from here http://pc-connectivity.garage.maemo.org/2nd_edition/) for VNC client to work on host PC

== Maemo Mica plugin framework for Eclipse ==

* none (so far :)

== Maemo ESbox for Eclipse ==

* Hover help for Python does not work on ESBox because documentation has not been integrated.
* Installing Nokia binaries may sometimes fail with exit code 100 when Maemo SDK gets installed. 
** workaround is to restart the Maemo SDK binary installation until it goes through without errors.
* If during Maemo SDK installation to other than Debian based Linux operating systems the default options for Maemo SDK Virtual image installation wizard are chosen and Nokia binaries installation fails, wizard proceeds normally to end (installing Development Environments for C/C++, Python and Qt). If you choose to cancel the installation because failed Nokia binaries Development Environments are not installed properly to the Maemo SDK and Maemo device.
** workaround is to select '''Project -> Validate Installed Packages''' from Eclipse IDE which verifies the integrity of installed development environments and re-installs missing packages for C/C++, Python and Qt to the Maemo SDK and Maemo device.
* Maemo Diablo SDK has ARMEL debugging problems when using Ubuntu Karmic host PC. If Maemo Diablo SDK is installed to Ubuntu Karmic environment <code>native-gdb</code> script will not work but gives segment fault which prevents debugging operations on Maemo SDK ARMEL rootstrap. 
** see more details from this bug report https://bugs.maemo.org/show_bug.cgi?id=7106

== Maemo PluThon for Eclipse ==

* Hover help for Python for Maemo API documents does not work on Pluthon because documentation is not integrated

== Maemo PC Connectivity ==

* Maemo PC Connectivity functionality with [[Nokia N900|N900]] device and [[Open development/Maemo roadmap/Fremantle|Fremantle]] is more limited than with N800/N810 device with Diablo
** N900 will not support USB host mode
*** no workaround (N900 HW issue)
** N900 will not support IP Forwarding (iptable NAT kernel modules)
*** workaround is to rebuild Fremantle kernel with NAT enabled and hack kernel symbols for NAT kernel modules
** N900 will not support BlueTooth connections simultaneously with WLAN connections
*** no known workaround
** N900 will not support "USB Networking" with platform default USB applet but only "PC Suite" and "Mass Storage" mode (applet provided by PC Connectivity supports also USB Networking)
*** workaround is to use ONLY configuration applet provided by PC Connectivity instead of default applet
*** 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
** 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
*** workaround is to use only SSHFS mounts with Cygwin
** 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)
** Fremantle SDK does not support CPU Transparency
*** workaround is to build and install new SBRSH client manually inside Scratchbox
* 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:" may happen when SBRSH is used first time with Maemo device (for example after device flashing when SSH keys need to be reset).
** workaround is to restart Maemo device.
* WLAN connection may get broken if WLAN and USB Networking are used simultaneously. Connection problems may occur after some time (can take hours or days) when device is (re)started and WLAN tries to connect.
** when the problem occurs user gets "Internet connection failed. Unable to retrieve IP address from server" error
** workaround is to re-flash Maemo device or manually assign IP number to the connection (which may cause problems with DHCP)
* Windows 7 (and Vista) support is only beta level because Cygwin 1.7 (first Cygwin release to support Windows 7 and Vista) is on beta level (Windows XP with Cygwin 1.5 is fully supported)
** Cygwin 1.7 beta installation may require manual configuration for Maemo
** Cygwin 1.7 beta X11 may crash when Maemo applications are run with it
** Host PC Connectivity does not install if Vista or Windows 7 machine is part of Windows Domain because it fails to create new user for Cygwin 1.7 SSHD service
*** workaround (but not recommended) is to try manual installation and configuration of Cygwin 1.5 also for Windows 7 (and Vista). Notice that Cygwin project does not support Windows 7 or Vista with Cygwin 1.5 version.
* SSHFS may not be usable for "normal" user account. This is because /dev/fuse is not writable by default for "normal" users. /dev/fuse is usually writable only for group "fuse" 
** workaround is to add user account used to "fuse" group

== Maemo SDK Virtual Images ==

* By default NetworkManager is being started after Scratchbox, so the resolv.conf file used by Scratchbox may be invalid which causes network problems
** workaround is to update resolv.conf file for Scratchbox manually after Maemo SDK installation and/or after network changes
* 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)
** workround is to use VMWare Player version 2.5.x or use only Bridged network mode for Maemo SDK Virtual Image
* 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.  
** workaround is to manually reconfigure network changes to the Virtualisation Environment and Maemo SDK. Log in to the Maemo SDK Virtual Image and invoke DHCP client with "sudo dhclient" to see network configuration or reconfigure network interfaces after network changes

== Maemo Flasher-3.5 Tool ==

* none (so far)

== Integration testing ==

* Some publicly 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

----
Feedback can be sent to eclipse-integration@maemo.org

[[Category:Eclipse]]

Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!

Summary:

Cancel | Editing help (opens in new window)

Retrieved from "https://wiki.maemo.org/Eclipse_integration/Known_issues"

Personal tools

Navigation

Views

Editing Eclipse integration/Known issues

@@ Line 51: / Line 51: @@
 *** 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
+** 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
 *** workaround is to use only SSHFS mounts with Cygwin