View source for Neo FreeRunner Hardware Issues

From Openmoko

Jump to: navigation, search

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Administrators.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page:

Template used on this page:

Return to Neo FreeRunner Hardware Issues.

Personal tools
Key pages on:
Neo FreeRunner

This is a community-written page that discusses hardware issues with the FreeRunner/GTA02 device. Information here is unofficial (and possibly incorrect) unless otherwise stated. Corrections and clarifications from Openmoko employees would be greatly appreciated.

Please DON'T PANIC when reading this page. Please give Openmoko employees time to investigate these issues and to develop a solution. Some of the items may turn out to be non-issues, or may have software workarounds. The FreeRunner's software is still under heavily development and can help fix most of this problems.

Active Issues

Poor Audio Quality

Issue: The person on the other end of a GSM phone call may experience poor audio quality, to the point where he/she cannot carry on a normal conversation.

There are three related aspects to this issue:

  • Call is too quiet (mixer settings for mic and/or earpiece are set too low)
  • Caller hears a loud echo of their own voice #1267
  • Buzzing noise caused by GSM radio interference #883 #1352

Affects: all devices but only some users (depending on many factors)

Status: Under investigation. There is a possibility that the quality can be made "good enough" through software (mixer settings).

The source of the GSM buzz has been identified.

Some hidden Calypso commands may help with the echo problem.


  1. Using a bluetooth headset is a possibility.
  2. Better mixer settings: One confirmed good settings are here: Please change accordingly in /usr/share/openmoko/scenarios/gsmhandset.state. Should eliminate/lessen echo and buzz problems. Neo alsamixer is the main article for setting the mixer settings.

Can't boot with discharged or missing battery

Issue: Neo FreeRunner requires battery power to boot, because Neo FreeRunner consumes too much current while booting to boot with only a charger. Since charging isn't enabled until the Neo FreeRunner has booted, this means that a discharged battery can not be charged. One manifestation of this problem is a kernel panic (red LED flashes constantly) when trying to boot using the power button.

Affects: Unknown.

Status: By properly sequencing module power sequence, a software solution to this problem should exist.

Fixed(?) with Werner Almesberger patches - more here additional information

I think this patch finally fixes the problem: Philipp Hugs patches


  1. Make sure that the battery never discharges completely
  2. Use external stand-alone charger (compatible with the Nokia BL-5C battery)
  3. Boot the FreeRunner with an alternative battery, or with a spare GTA01 or GTA02 battery, plug USB power, then switch to the empty battery.
  4. Boot the FreeRunner with a 4.5VDC external power source (steady hand and great care involved), plug USB power, then insert the empty battery.
  5. Some users have reported that Neo FreeRunner is able to boot on USB power alone using the NOR u-boot, thus: press AUX, plug USB power, select boot. Reports of success would be appreciated.
    1. Does work with sequence described. If after pressing boot it just turns off again (happened a few times), then: press AUX, plug in USB power, cycle through the menu a few times to keep it from turning off without booting, after a minute or so press boot. Imrehg 08:34, 10 September 2008 (UTC)
    2. This does indeed work with sequence described. After pressing boot, the screen went blank for a few seconds, but then the beast came to life again. That saved the day!
    3. Trifirmed. Neither USB connection nor wall charger was able to wake my phone. But in NOR u-boot it worked (connected to the computer). I think this trick hasn't failed to anyone. --Flamma 12:11, 17 September 2008 (UTC)

See also:

Neo FreeRunner Battery

Battery discharges when charging completes

Issue: If the Neo FreeRunner has been charging, when charging completes, it seems to drain the battery and not turn on charging again. This seems to be bug of PMU-registers setup, that shows up when PMU has to handle bat autonomously (=suspend). There might be issues our current scheme relies on wake-interrupt at bat-full which doesn't succeed, or something like that.

Affects: Unknown.



  1. When the battery is full, disconnect the charger

See also:

Suspend/resume corrupts SD card's partition table

Issue: Suspend/resume corrupts the partition table of the SD card

Affects: Unknown.


[Patched kernel] might solve the problem


  1. [Script] as a temporary workaround

See also:

[trac ticket]

Some SIMs Don't Work

Issue: There are reports that some users cannot register with their GSM network when using certain SIM cards. See for example

It is possible that there is more than one issue involved here. The observed problems might (i.e. some items are only speculation at this point) be caused by:

  • User error, not inserting the SIM in the correct orientation or not sliding the holder to the 'locked' position
  • Software issues that result in a locked SIM (not properly prompting the user for a PIN and then passing this to the SIM)
  • Mechanical issues with the SIM holder that prevent the pins from making reliable contact with the pads on the SIM. Note that only 6 of the 8 pins are used, and the remaining two are not connected.
  • Electrical incompatibility (some tests show problems with 1.8V SIMs while 2.9V ones work OK)
  • Firmware bugs in the TI Calypso GSM chipset. Note that one issue in this category was found and fixed on the GTA01 devices (#666 in Trac), and that specific problem should not affect the FreeRunner.
  • Defective SIMs, i.e. ones that do not comply with the applicable standards and are acknowledged as being defective by the carrier (even if they happen to work in some phones).
  • You may have true 3G operating at 2100 and your sim doesn't fallback to GSM. The Phone works on 850/1800/1900 or 900/1800/1900.

See also:

Affects: Only a subset of users (details unknown).

Status: Under investigation. Please add your information to FreeRunner_unable_to_work_with_3G_SIM_cards or GSM network registration


  1. Please document your existing SIM card and provider in the table here.
  2. If the table mentioned above shows any SIM cards known to work with your provider, make note of these numbers.
  3. Contact your network provider and request a new SIM card. You may wish to print out the table mentioned above and bring it with you to the store.
  4. Add your experience with the new SIM card to the table mentioned above.

Known/Accepted Issues

This section lists items that are acknowledged as being less than ideal, but are considered to be acceptable in the shipping product. They will not be discussed in detail on this page.

  • Poor performance + slow bus speed of the Glamo GPU - discussed to death on the mailing lists and IRC.
  • GPS antenna switch driven out-of-spec - does not appear to have a significant effect on device performance
  • Poor low-frequency audio response with low-impedance headphones, e.g. as discussed in this thread: (NOTE - this thread refers to pre-mass-production devices)
    • Can be fixed to an semi-acceptable level (if not high fidelity most probably) by adjusting "Bass Volume" to full (15) and "Bass Filter" to "100Hz @ 8kHz" (bass will be boosted <= 600Hz when playing back at 48kHz) or "200Hz @ 8kHz" (<= 1200Hz @ 48kHz). The default is 130Hz @ 48kHz and does not help much with the more wider scope of low frequencies.
    • Ideally someone would record output and find out which setting produces best output, ie. compensating for the loss of low frequencies without boosting too high frequencies with this "bass" boost.

Resolved Issues

These are issues that have been discussed in the past, but have been fixed (or turned out not to be a problem) for the mass-produced devices.

  • Excessive LED current - Some early units lacked a current-limiting resistor for the LEDs. This has been fixed for the production units.
  • Battery life - At this time it appears that the FreeRunner battery life will be acceptable once suspend/resume support has been implemented in software.
  • slow GPS TTFF - see GPS Problems

Empty NOR Flash

Issue: NOR flash (backup copy of u-boot) is not programmed. #1568

Affects: Unknown - maybe only 1 or 2 devices? Also need to confirm that the bug report was from a mass-production unit rather than an earlier prototype.

Status: Solved. The new devices are tested better if they have the NOR flashed programmed and aren't shipped if the test fail.

Workarounds: Use the NAND copy of u-boot and be careful not to brick the device unless a debug-board is available.

Debug board has wrong vendor/product ID

Issue: A debug board is not reporting the expected USB Vendor/Product ID.

Affects: Only one report has been seen so far.

Status: Probably a single case scenario.

Workarounds: Edit configuration files (e.g. openocd.conf) to use the IDs that the board is reporting.

List of "Current issues" Imported from the "Community update page"

(to be sorted)

The information below has been collected from various sources, feel free to add questions and comments here.

GPS Performance of the FreeRunner

The poor GPS performance on the FreeRunner has been traced to an interaction between the microSD card and the GPS unit. A software and a hardware fixes are available, see GPS Problems.

GTA02 battery status

While writing a device driver for the new battery which provides an accurate counter of the charge state of the GTA02, the driver developer discovered that the device driver does not get a reading of the charge state due to a very long response time with only one I/O signal when trying to read the charge state. To be able to read the battery status properly, it has been written that it will be necessary to re-design that part of the GTA02 for hardware version GTA02A5 to use two I/O signals to reduce the response time (one for transmitting commands, one for receiving data?). This was fixed two months ago (see Bug 957).

Delivery of a GSM firmware update for the 3G SIM bug (#666)

A bug in the GSM firwmare of Neo 1973 caused some 3G SIM cards to not work with Neo 1973. This Neo 1973 GSM firmware update can only be installed by an Openmoko employee due to licensing issues.

This fix is already present in the Neo FreeRunner firwmare, and thus the Neo 1973 GSM firmware update is not required for the Neo FreeRunner. In fact since the firmware differs between the Neo 1973 and the Neo FreeRunner, it would very likely make the GSM module unusable.

There seem to be other GSM issues on the Neo FreeRunner. See Some SIMs Don't Work above.

SMedia 3362 Documentation & OpenGL ES Drivers

There is an open source kdrive driver being written for the GTA02 which will use hardware to accelerate the XRender extension. While the chip is capable of 3D graphics, no OpenGL ES driver/library is avaliable and Openmoko developers will not be writing one in the near future (although they have not ruled it out in the long-term).

Documentation for the SMedia 3362 has been promised (see this post). However, this refers to documentation Openmoko developers will be writing themselves, not the technical documentation SMedia have provided Openmoko with. The Openmoko developers had to sign an NDA with SMedia to obtain this documentation and are therefore unable to pass this information on to community developers. (See this post for details)

Power Management on the Neo1973/FreeRunner

The current battery life of the Neo1973 and FreeRunner is not satisfactory. A lot of changes seem to be necessary to the kernel, drivers and related user-space applications. Hopefully the situation will improve over time.