Eclipse integration/Known issues

(Maemo Flasher-3.5 Tool)
(Known Issues for Maemo Eclipse Integration Edition 2 Final release)
Line 3: Line 3:
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/.
 +
Detailed list of new features implemented to Maemo Eclipse Integration since previous PreFinal release together with feature plan for final release is here http://wiki.maemo.org/Eclipse_integration.
 +
 +
Release Notes file is here http://wiki.maemo.org/Eclipse_integration/ReleaseNotes_final.
== Product baselines ==
== Product baselines ==

Revision as of 11:54, 14 December 2009

Contents

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/.

Detailed list of new features implemented to Maemo Eclipse Integration since previous PreFinal release together with feature plan for final release is here http://wiki.maemo.org/Eclipse_integration.

Release Notes file is here http://wiki.maemo.org/Eclipse_integration/ReleaseNotes_final.

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 Mica plugin framework for Eclipse

  • none (so far :)

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.
  • 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 plugin for Eclipse

  • 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 functionality with N900 device and 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
      • will be (hopefully) fixed for final release
    • 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)
  • 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 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.
    • when the problem occurs user gets "Internet connection failed. Unable to retrieve IP address from server" error
    • 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
  • 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
    • Cygwin 1.7 beta sshd daemon launch may fail

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)
  • 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".

Maemo Flasher-3.5 Tool

  • none (so far)

Integration testing

  • 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

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