Openmoko - User contributions [en]

Template:News

2009-04-05T02:17:17Z

Imrehg: added latest community update

* 04-05: [[Community Updates/April 05, 2009]]
* 03-20: [[Community Updates/March 20, 2009]]
* 03-12: [[Freedom Slim Keyboard|Connect Neo with keyboard via bluetooth]]
* 03-06: [[Community Updates/March 6, 2009|Community Update]]
* 02-16: [[Fyp]] a distributions for a Debian released beta image.
* 02-02: [[OpenmokoFramework/Status Update 6|Openmoko Framework Team Status Report]]

Community Updates/2009-03-20

2009-03-20T15:23:31Z

Imrehg: Distributions: more info about Android updates

{{Languages|Community Updates/March 20, 2009}}

__NOTOC__
__NOEDITSECTION__

====='''Period 6, Mar ~ 20, Mar, 2009'''=====

==Distributions ==

* '''Om2009''' - Openmoko continues its work on the [http://lists.openmoko.org/pipermail/devel/2009-March/004976.html release plan]. Members from Paroli, Distribution and FSO met in Chemnitz, Germany to further discuss their commitments to a future release.

* '''QT Extended''' [http://wiki.openmoko.org/wiki/Qt_Extended_4.4.3 moving along as a community project] The community created a fork of it and called it Qt Extended Improved:
** [http://trac.karadog.net/qt-extended-improved bug tracking system]
** [http://dashi-x02.karadog.net/~lihouyu/qtextended/4.4.3/ prebuild rootfs images]
** [http://git.karadog.net/qt-extended-improved.git git repository]

* '''Android''' - Beta 4 announced (where?) , cupcake image - can someone add to this.
The images produced by the community driven (not Koolu) Android images can be found at [http://panicking.kicks-ass.org/download/], with information on their use at the [http://forum.koolu.org/ koolu forum], or on other pages, e.g. [http://jms.id.au/wiki/AndroidOnFreerunner]. Latest features include working GPRS (see forum) and using the Cupcake branch with the on-screen keyboard built in (see e.g. [http://www.newlc.com/en/freerunner-mobile-which-support-android-cupcake]).

* '''Fyp 3.18''' [[Fyp | released]]

==Applications ==

===New Applications===

* [http://www.opkg.org/package_168.html Xboard + GNUChess]
** XBoard is an open source graphical chess user interface for numerous chess engines

* [http://www.opkg.org/package_166.html knjMokoCalendar]
** Google Calendar for the Openmoko (unstable)

* [http://wiki.openmoko.org/wiki/KnjMokoOPKG knjmokoopkg]
** A package-browser which both creates a SQLite3-database with all packages from the OPKG-cache (enabling fast searches through packages < 1 sec) and is able to install and remove packages. You can also perform updates and upgrades through it.

===Application Updates===

* '''Mokometeo 0.2''' the small python/GTK application fetching the weather forecast from Yahoo weather pages,has been released with some improvements and bug fixes. Changes that went in are:
** added some "print" in the code
** debug the .mokometeo folder ; put the config folder in /home/root/.mokometeo/ instead of /.mokometeo/
** test if the connection to internet is ok. If not, display question marks
** backup the data each time data is downloaded and displayed. This data is used on the next Mokometeo startup
** added the date and time when the data has been downloaded
** http://wiki.openmoko.org/wiki/Mokometeo

* '''Fennec Beta 1''' Released its twelfth development milestone and the first beta release of the mobile version of Firefox, for testing purposes only. No version for Freerunner yet. More details about this on:
** http://blog.pavlov.net/2009/03/17/fennec-1-beta-1/
** http://www.mozilla.org/projects/fennec/1.0b1/releasenotes/
** https://wiki.mozilla.org/Mobile/Build/Fennec

* '''Orrery 2.5''' Released a new version of the orrery sky-chart program has been released. In addition to several bug fixes, the new version includes support for displaying informal constellations (asterisms like the Big Dipper), a new to-scale display of the Solar System, information about the number of satellites used for the position fix in GPS mode and better support for displaying stars too faint for the unaided eye to see.
** http://wiki.openmoko.org/wiki/Orrery

* [http://www.opkg.org/package_137.html GTick] is a metronome application written for GNU/Linux and other UN*X-like operting systems supporting different meters (Even, 2/4, 3/4, 4/4 and more) and speeds ranging from 10 to 1000 bpm. It utilizes GTK+ and OSS (ALSA compatible). It is part of the GNU Project.
** Please test the package and leave some feedback (comment or [[GTick wikipage]])

* '''GridPad v.2.1''' Released

* '''gvSIG Mobile 0.11''' Released

* '''KnjMokoWifi''' Released
** [[http://wiki.openmoko.org/wiki/KnjMokoWifi More information]]
*[http://www.opkg.org/package_96.html ZOMG!] package fixed

==Community ==

* A [[Browser review|browser review/comparison]] study of the best suitable browser
** Everyone can add test results of the browser compatibility to any of the distributions being used so that we may find the one that has the most potential and can be developed to a actual working browser.

* If anyone is looking for a [http://repository.maemo.org/pool/maemo4.1/free/g/gnuchess/ Chess game on the Neo], you could try Maemo. This might be a good start for the application:
** http://repository.maemo.org/pool/maemo4.1/free/o/osso-chess-ui/
** http://repository.maemo.org/pool/maemo4.1/free/g/gnuchess/

* Mid April: [http://lists.openmoko.org/pipermail/community/2009-March/043971.html GSM buzz-fix party in Braunschweig, Germany] Daniel Williams has been glad to perform buzz fixes for phones that needs the fix.In order to gauge interest and plan ahead with respect to ordering Resistors/Capacitors he would like to know how many phones would come. If you are interested and would show up please mail him privately and also give information on how many phones you would bring.

* Also there is another Fix party in Barcelona organized by David Samblas from [http://www.tuxbrain.com Tuxbrain] visit [http://www.openmoko-spain.org/tiki-view_blog_post.php?blogId=1&postId=7 this blog post] for more information

* [http://software.cofundos.org Software.Cofundos.org] - Following the programming contest, software.Cofundos.org will help to boost any idea one has in mind and give an opportunity to earn some money for people who have the time/skills you may not have.This is a great platform for discussing and enriching ideas on upcoming/existing projects. You can view only openmoko related projects at [http://openmoko.cofundos.org openmoko.cofundos.org]. A feed for new projects from cofundos.org has been uploaded to [http://planet.openmoko.org Openmoko Planet]. [http://www.tuxbrain.com Tuxbrain] has also started a [http://www.openmoko-spain.org/tiki-view_blog_post.php?blogId=1&postId=8 cofundos.org campaign]

* Kustomizer 0.4 released for 2008.12 [http://groups.google.com/group/kustomizer/browse_thread/thread/58b14dd6893d7242]

* [http://lists.openmoko.org/pipermail/community/2009-March/043615.html Freerunner For Application Ideas]

===Competitions===

* Announcing the [http://lists.openmoko.org/pipermail/community/2009-March/043240.html first programming competition] for Openmoko phones
** [http://risto.kurppa.fi/blog/announcing-the-first-programming-competition-for-openmoko-phones/ read the rules]

* [http://lists.openmoko.org/pipermail/community/2009-March/044153.html New application contest] organized by Rakshat Hooja 'Call Recorder cum Dictaphone Application for the Freerunner' on cofundus.org. Any one who wishes to contribute their time/skills and also get more details can check the following link:
** http://www.cofundos.org/project.php?id=154

===Event News===

[[Image:IEEE-LINUXeOMD.preview.jpg|250px|align|right]]
* '''2009-03-01/03-31''' [http://wiki.openmoko.org/wiki/user:Harry Harry' Openmoko Survey] | Please help me with my free software and Openmoko related academic research | Harry Tsai of [http://www.cgu.edu.tw Chang Gung Universtiy]

* '''2009-03-21/03-22''' [http://fsf.org/conference LibrePlanet conference], Cambridge, MA | [[User:JohnSullivan|John Sullivan]] and other Openmoko users will be around, if critical mass then there will be related unconference hacking on Sunday.
* '''2009-03-23/27''' [http://www.bits-apogee.org/ Apogee 2009] | Rakshat Hooja of IDA Systems will be speaking about Openmoko

* '''2009-03-30/04-03''' [http://www.confabb.com/conferences/57983-embedded-systems-conference-silicon-valley-2009 EMBEDDED SYSTEMS CONFERENCE - SILICON VALLEY 2009] | San Jose McEnery Convention Center, California | A huge Openmoko marketing event and Sean's speech

* '''2009-04-01/02''' [http://www.openexpo.ch/en/openexpo-2008-bern/travel-and-accommodation/ Swiss Open Source Software Conference & Exposition] | Bern, Switzerland | Openmoko Sean will give a speech

* '''2009-04-06/08''' CELF Embedded Linux Conference | ELC 2009 San Francisco, California.

* '''2009-04-18''' [http://http://www.openmoko-spain.org/tiki-view_blog_post.php?blogId=1&postId=7 Openmoko Fix it Party] | Repairing buzz hardware bug live and for free , Barcelona.

* '''2009-04-18/19''' [http://register.osdc.tw/ Open Source Developer's Conference] | OSDC will hold in Taipei , Taiwan.

[[category:Community Update]]

Community Updates/2009-03-20

2009-03-20T15:18:05Z

Imrehg: Distributions

{{Languages|Community Updates/March 20, 2009}}

__NOTOC__
__NOEDITSECTION__

====='''Period 6, Mar ~ 20, Mar, 2009'''=====

==Distributions ==

* '''Om2009''' - Openmoko continues its work on the [http://lists.openmoko.org/pipermail/devel/2009-March/004976.html release plan]. Members from Paroli, Distribution and FSO met in Chemnitz, Germany to further discuss their commitments to a future release.

* '''QT Extended''' [http://wiki.openmoko.org/wiki/Qt_Extended_4.4.3 moving along as a community project] The community created a fork of it and called it Qt Extended Improved:
** [http://trac.karadog.net/qt-extended-improved bug tracking system]
** [http://dashi-x02.karadog.net/~lihouyu/qtextended/4.4.3/ prebuild rootfs images]
** [http://git.karadog.net/qt-extended-improved.git git repository]

* '''Android''' - Beta 4 announced (where?) , cupcake image - can someone add to this.
The images produced by the community driven (not Koolu) Android images can be found [http://panicking.kicks-ass.org/download/], with information on their use at [http://forum.koolu.org/], or on other pages, e.g. [http://jms.id.au/wiki/AndroidOnFreerunner]. Latest features include working GPRS (see forum) and using the Cupcake branch (see e.g. [http://www.newlc.com/en/freerunner-mobile-which-support-android-cupcake]).

* '''Fyp 3.18''' [[Fyp | released]]

==Applications ==

===New Applications===

* [http://www.opkg.org/package_168.html Xboard + GNUChess]
** XBoard is an open source graphical chess user interface for numerous chess engines

* [http://www.opkg.org/package_166.html knjMokoCalendar]
** Google Calendar for the Openmoko (unstable)

* [http://wiki.openmoko.org/wiki/KnjMokoOPKG knjmokoopkg]
** A package-browser which both creates a SQLite3-database with all packages from the OPKG-cache (enabling fast searches through packages < 1 sec) and is able to install and remove packages. You can also perform updates and upgrades through it.

===Application Updates===

* '''Mokometeo 0.2''' the small python/GTK application fetching the weather forecast from Yahoo weather pages,has been released with some improvements and bug fixes. Changes that went in are:
** added some "print" in the code
** debug the .mokometeo folder ; put the config folder in /home/root/.mokometeo/ instead of /.mokometeo/
** test if the connection to internet is ok. If not, display question marks
** backup the data each time data is downloaded and displayed. This data is used on the next Mokometeo startup
** added the date and time when the data has been downloaded
** http://wiki.openmoko.org/wiki/Mokometeo

* '''Fennec Beta 1''' Released its twelfth development milestone and the first beta release of the mobile version of Firefox, for testing purposes only. No version for Freerunner yet. More details about this on:
** http://blog.pavlov.net/2009/03/17/fennec-1-beta-1/
** http://www.mozilla.org/projects/fennec/1.0b1/releasenotes/
** https://wiki.mozilla.org/Mobile/Build/Fennec

* '''Orrery 2.5''' Released a new version of the orrery sky-chart program has been released. In addition to several bug fixes, the new version includes support for displaying informal constellations (asterisms like the Big Dipper), a new to-scale display of the Solar System, information about the number of satellites used for the position fix in GPS mode and better support for displaying stars too faint for the unaided eye to see.
** http://wiki.openmoko.org/wiki/Orrery

* [http://www.opkg.org/package_137.html GTick] is a metronome application written for GNU/Linux and other UN*X-like operting systems supporting different meters (Even, 2/4, 3/4, 4/4 and more) and speeds ranging from 10 to 1000 bpm. It utilizes GTK+ and OSS (ALSA compatible). It is part of the GNU Project.
** Please test the package and leave some feedback (comment or [[GTick wikipage]])

* '''GridPad v.2.1''' Released

* '''gvSIG Mobile 0.11''' Released

* '''KnjMokoWifi''' Released
** [[http://wiki.openmoko.org/wiki/KnjMokoWifi More information]]
*[http://www.opkg.org/package_96.html ZOMG!] package fixed

==Community ==

* A [[Browser review|browser review/comparison]] study of the best suitable browser
** Everyone can add test results of the browser compatibility to any of the distributions being used so that we may find the one that has the most potential and can be developed to a actual working browser.

* If anyone is looking for a [http://repository.maemo.org/pool/maemo4.1/free/g/gnuchess/ Chess game on the Neo], you could try Maemo. This might be a good start for the application:
** http://repository.maemo.org/pool/maemo4.1/free/o/osso-chess-ui/
** http://repository.maemo.org/pool/maemo4.1/free/g/gnuchess/

* Mid April: [http://lists.openmoko.org/pipermail/community/2009-March/043971.html GSM buzz-fix party in Braunschweig, Germany] Daniel Williams has been glad to perform buzz fixes for phones that needs the fix.In order to gauge interest and plan ahead with respect to ordering Resistors/Capacitors he would like to know how many phones would come. If you are interested and would show up please mail him privately and also give information on how many phones you would bring.

* Also there is another Fix party in Barcelona organized by David Samblas from [http://www.tuxbrain.com Tuxbrain] visit [http://www.openmoko-spain.org/tiki-view_blog_post.php?blogId=1&postId=7 this blog post] for more information

* [http://software.cofundos.org Software.Cofundos.org] - Following the programming contest, software.Cofundos.org will help to boost any idea one has in mind and give an opportunity to earn some money for people who have the time/skills you may not have.This is a great platform for discussing and enriching ideas on upcoming/existing projects. You can view only openmoko related projects at [http://openmoko.cofundos.org openmoko.cofundos.org]. A feed for new projects from cofundos.org has been uploaded to [http://planet.openmoko.org Openmoko Planet]. [http://www.tuxbrain.com Tuxbrain] has also started a [http://www.openmoko-spain.org/tiki-view_blog_post.php?blogId=1&postId=8 cofundos.org campaign]

* Kustomizer 0.4 released for 2008.12 [http://groups.google.com/group/kustomizer/browse_thread/thread/58b14dd6893d7242]

* [http://lists.openmoko.org/pipermail/community/2009-March/043615.html Freerunner For Application Ideas]

===Competitions===

* Announcing the [http://lists.openmoko.org/pipermail/community/2009-March/043240.html first programming competition] for Openmoko phones
** [http://risto.kurppa.fi/blog/announcing-the-first-programming-competition-for-openmoko-phones/ read the rules]

* [http://lists.openmoko.org/pipermail/community/2009-March/044153.html New application contest] organized by Rakshat Hooja 'Call Recorder cum Dictaphone Application for the Freerunner' on cofundus.org. Any one who wishes to contribute their time/skills and also get more details can check the following link:
** http://www.cofundos.org/project.php?id=154

===Event News===

[[Image:IEEE-LINUXeOMD.preview.jpg|250px|align|right]]
* '''2009-03-01/03-31''' [http://wiki.openmoko.org/wiki/user:Harry Harry' Openmoko Survey] | Please help me with my free software and Openmoko related academic research | Harry Tsai of [http://www.cgu.edu.tw Chang Gung Universtiy]

* '''2009-03-21/03-22''' [http://fsf.org/conference LibrePlanet conference], Cambridge, MA | [[User:JohnSullivan|John Sullivan]] and other Openmoko users will be around, if critical mass then there will be related unconference hacking on Sunday.
* '''2009-03-23/27''' [http://www.bits-apogee.org/ Apogee 2009] | Rakshat Hooja of IDA Systems will be speaking about Openmoko

* '''2009-03-30/04-03''' [http://www.confabb.com/conferences/57983-embedded-systems-conference-silicon-valley-2009 EMBEDDED SYSTEMS CONFERENCE - SILICON VALLEY 2009] | San Jose McEnery Convention Center, California | A huge Openmoko marketing event and Sean's speech

* '''2009-04-01/02''' [http://www.openexpo.ch/en/openexpo-2008-bern/travel-and-accommodation/ Swiss Open Source Software Conference & Exposition] | Bern, Switzerland | Openmoko Sean will give a speech

* '''2009-04-06/08''' CELF Embedded Linux Conference | ELC 2009 San Francisco, California.

* '''2009-04-18''' [http://http://www.openmoko-spain.org/tiki-view_blog_post.php?blogId=1&postId=7 Openmoko Fix it Party] | Repairing buzz hardware bug live and for free , Barcelona.

* '''2009-04-18/19''' [http://register.osdc.tw/ Open Source Developer's Conference] | OSDC will hold in Taipei , Taiwan.

[[category:Community Update]]

Android

2009-02-06T06:35:40Z

Imrehg: /* News */ Koolu Beta 3 & changelog

{{Languages|Android}}
{{Distributions|Android}}

{|align=right
|__TOC__
|}
[[Image:android.png]]
= Introduction =
This page is the central place for documentation about Android on the [[Neo1973 Hardware|Neo 1973]] and [[Neo_FreeRunner_GTA02_Hardware|FreeRunner]] handsets.

[http://code.google.com/android/ Android] is a software stack for mobile devices developed by the [http://www.openhandsetalliance.com/ The Open Handset Alliance.] Although Android is publicised as being open source software (most of the source code has been released) parts of the code have not been released yet, namely the GSM library. This makes porting Android to the OpenMoko phones difficult. However, there are promises that the remaining parts of the code will be released.

A lot of work is being done to get Android functioning properly on the FreeRunner and it is likely, in the near future, to be the distribution closest to enabling the FreeRunner to function as an everyday phone.

= Development =
See: [[Android porting]]

= Usage =
See: [[Android usage]]

= Installation =
See: [[Android on Freerunner]]

= News =
* 20090204 Koolu releases its Beta3 Android [http://freerunner.android.koolu.com/release-files release].
** Changelog:
*** Added GPS library that supports GPS under Android
*** MAX_PROCESSES patch to enable more background processes to be run (fixes Pictures application)
*** Added Dalvik optimization setting
*** Started including 3rd party applications
*** Updated user interfaces for GPS and Bluetooth to match new kernel
*** Now report RSSI of Wifi signals to upper application layer
*** Enable libsoundpool compilation to support audible clicks

* 20090122 Koolu releases its Beta2 Android [http://freerunner.android.koolu.com/release-files release].

* 20081219 Koolu releases its Beta Android [http://forum.koolu.org/files/androidfs-koolu-1_0.jffs2 Image] and [http://forum.koolu.org/files/uImage-android-patched_bc2caff9cdef8a16.bin kernel].

* 20081202 [http://www.koolu.com Koolu], a Freerunner distributor, has released the source code of their Android port at [http://git.koolu.org http://git.koolu.org]. See the [[#Building the Koolu Android Source]] instructions below for how to build an Android image for Freerunner.

* 20081104 The first Android-image has been successfully created by Sean McNeil! - sms and calling works, wifi and bluetooth doesn't. [http://onlinedev.blogspot.com/2008/11/porting-android-phase-3-done.html ''news-source'']

= See also =
* [http://tw.youtube.com/watch?v=m4NbsLmF9j0 YouTube Video 1]
* [http://tw.youtube.com/watch?v=r6Op-7tNTiw YouTube Video 2]

[[Category:Distributions]]

User talk:Seanmcneil3

2008-12-24T10:03:35Z

Imrehg: /* Android running problems */ extra info for Low memory fail

==What's new?==
This would be a nice area for a changelog. What's new in the November 17th image? Anything worth noting?

== Android running problems ==

I had flashed it now on my FR but it doesn't work. I see only a black screen.

It works, but you need 2 partition on your SD card. First about 8MB formated vfat, secound ext3. That partitions must be empty.

--

Hi Sean, how can the imgages be put on the GTA02? I also flashed my GTA02 and android will not start, only black screen.

Sean:
I've just begun adding more information to the page which explains what is necessary to bring up Android. Sorry for the delay.

--

Hi Sean I split sd card to 2 partition fat32 and ext3, noting in fat32(1.5g) and in ext3(2.2G) have lostxxfound directory,I never set boot flag to sd card's partition, now I flash image and rootfs according your "setup guide" but now it not start just black screen. what's wrong with it

--

Hi Sean,
same problem: I flashed the kernel and rootfs. My SDcard has a primary 100MB FAT16 and an other primay 400MB EXT3 partition. I only get a black screen.

--

Hi,
When using Android, some menu items are don't work. E.g. when trying to set the Phone Ringtone, the menu shows for a split second and then I'm back to the Sound settings. The log shows the following:
<pre>
I/ActivityManager( 855): Starting activity: Intent { action=android.intent.action.RINGTONE_PICKER comp={android/com.android.internal.app.RingtonePickerActivity} (has extras) }
I/ActivityManager( 855): Start proc android.process.media for content provider com.android.providers.media/.MediaProvider: pid=1385 uid=10003 gids={1006, 3003, 2001}
I/ActivityThread( 1385): Publishing provider downloads: com.android.providers.downloads.DownloadProvider
I/ActivityThread( 1385): Publishing provider drm: com.android.providers.drm.DrmProvider
I/ActivityThread( 1385): Publishing provider media: com.android.providers.media.MediaProvider
V/MediaProvider( 1385): Attached volume: internal
V/MediaProvider( 1385): /sdcard volume ID: -1
V/MediaProvider( 1385): Attached volume: external
I/ActivityManager( 855): Exiting empty application process android.process.media (android.os.BinderProxy@435052d8)
I/Process ( 855): Sending signal. PID: 1385 SIG: 9
I/ActivityManager( 855): Killing app com.android.settings (pid 1377) because provider com.android.providers.media.MediaProvider is in dying process android.process.media
I/Process ( 855): Sending signal. PID: 1377 SIG: 9
I/ActivityManager( 855): Killing app com.android.settings (pid 1377) because provider com.android.providers.drm.DrmProvider is in dying process android.process.media
I/Process ( 855): Sending signal. PID: 1377 SIG: 9
D/ActivityManager( 855): Received spurious death notification for thread android.os.BinderProxy@435052d8
I/ActivityManager( 855): Process com.android.settings (pid 1377) has died.
I/WindowManager( 855): WIN DEATH: Window{434e8b10 com.android.settings/com.android.settings.SoundAndDisplaySettings}
I/WindowManager( 855): WIN DEATH: Window{434f1520 android/com.android.internal.app.RingtonePickerActivity}
I/ActivityManager( 855): Start proc com.android.settings for activity com.android.settings/.SoundAndDisplaySettings: pid=1396 uid=1000 gids={3001, 3003}
I/ActivityManager( 855): Low Memory: No more background processes.
D/dalvikvm( 855): GC freed 2248 objects / 104336 bytes in 727ms
W/SurfaceComposerClient( 855): lock_layer timed out (is the CPU pegged?) layer=1, lcblk=0x423800a0, state=0000000c (was 0000000c)
D/dalvikvm( 888): GC freed 167 objects / 6208 bytes in 958ms
D/dalvikvm( 894): GC freed 15 objects / 560 bytes in 998ms
I/ActivityManager( 855): Displayed activity com.android.settings/.SoundAndDisplaySettings: 2675 ms
</pre>
I was not sure if it is because I had relatively small space dedicated to teh VFAT and Ext3 partitions on the SD card (so I can have another distro on the 3rd partition), but it seems to be enough:
<pre>
/: 252544K total, 38468K used, 214076K available (block size 4096)
/: 252544K total, 38468K used, 214076K available (block size 4096)
/dev: 59952K total, 0K used, 59952K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/data: 30985K total, 19413K used, 11572K available (block size 1024)
/sdcard: 31912K total, 1782K used, 30130K available (block size 2048)
</pre>
Other menu items do the same thing sometimes, but I forgot which one I found last time. In the log they also had the "Low memory" warning, so should originate the same place. --[[User:Imrehg|Imrehg]] 05:10, 20 December 2008 (UTC)

'''Update:''' the menu works fine from the contact list, when trying to change the ringtones for individual contacts. --[[User:Imrehg|Imrehg]] 10:03, 24 December 2008 (UTC)

--

Sending message breaks network connection.
When I'm trying to send a message, the network disconnects (without sending the SMS) and won't work even with reboot, until I delete the message thread and reboot (sometimes even need reboot a few times after message delete). Receiving a message works just fine.
The log of the message send (after clicking the send button):
<pre>
D/SmsProvider( 888): insert url=content://sms/outbox, match=8
I/ActivityManager( 855): Stopping service: com.android.mms/.transaction.SmsReceiverService
I/ActivityManager( 855): Stopping service: com.android.mms/.transaction.SmsReceiverService
I/NotificationService( 855): enqueueToast pkg=com.android.mms callback=android.app.ITransientNotification$Stub$Proxy@435bc740 duration=0
</pre>
Not sure whether it matters, my network is TWN GSM (Taiwan) --[[User:Imrehg|Imrehg]] 05:34, 20 December 2008 (UTC)

--

Volume during call is too low. When not in call, the soft-keyboard has the Vol+ and Vol- buttons, but of course they don't do anything. During call, the volume is too low, I can hardly hear anything. On the receiving end they can hear me perfectly clear. If trying to bring up the soft-keyboard during call with the Menu (the Power button at the moment), then instead of the previously mentioned menu (which has the keyboard option) the Contacts menu comes up... Thus no way to adjust the volume and making the phone almost unusable for calls, unless I'm in a perfectly silent environment. --[[User:Imrehg|Imrehg]] 05:38, 20 December 2008 (UTC)

'''Update:''' Could access the keyboard as: Pressing Menu (power) button once -> Phone displays contacts menu -> Menu button again -> Soft-keyboard key. The displayed Vol+/Vol- buttons (and probably the rest of the function buttons) don't have any effect on the call, it is still the same low sound level. --[[User:Imrehg|Imrehg]] 07:18, 20 December 2008 (UTC)

== Android doesn't accept the pin ==

I have flashed my GTA02 and android will boot but it does not accept the pin code for my SIM-card.
Jofry

Sean:
Hi Jofry, I've never really tried a locked SIM, so I don't know if the dialpad comes up to let you type in the code. Does it? If so, then I can probably fix the issue. Otherwise, we are kind of stuck until a virtual keyboard is developed.

Jofry: Yes, the dialpad comes up and ask for my pin number. But if i type in the number the application means that it was the wrong number. But it is the right one.

Skamster: i've got the same problem. i could enter the pin as much as i want but it doesn't let me in. normaly, it lock the sim after 3 try's (i try 4-6 times), but here it doesn't. i flashed with qtopia again and don't need a puck. maybe it doesn't "send" the pin to the simcard?

That's a known issue. For more information about the things you have to do, before you can successful use Android, look at http://onlinedev.blogspot.com/2008/11/getting-started-with-android-on-neo.html [[User:Dolfje|Dolfje]] 12:03, 5 November 2008 (UTC)

I got the same problem but can not fix it through disabling the pin, because my sim does not allow to disable the pin neither with qtopia, nor with my other mobile phone.

== Android rootfs for µSD boot ==

Treviño: Could you set-up a rootfs for running Android from MicroSD?

== Android and replying calls ==

Actually it is not possible to reply to a call due to the missing hardware "accept" button.

Treviño: So, what about adding a workaround to it by using the AUX button as an "accept" button if pressed briefly (below 0.5 second), while keeping it to the "reject" (home) button when pressed longer?!

ahk05: It seems that Yann neveu-2 has managed to modify the Phone app to allow you to answer phone calls with the power button. Maybe his apk should be included in your image?
http://n2.nabble.com/-Android--Soft-keyboard-td1518369.html
http://gabuzomeu.fr/openmoko/Phone.apk

== Android Misc requests ==

--

dilersam: thanks for having added more informations to the page. It helps a lot.

-

fate: thanks for all your great work. i was wondering when will the next flash image be released?

== u-boot environment changes for large kernel ==

I'm using [[neocon]] to connect to the u-boot console. What env variable should we change and to what values?

Thanks!

- I'm using Kermit, and this is what I change in the console

setenv bootargs ${bootargs_base} ${mtdparts}; nand read.e 0x32000000 kernel; bootm 0x32000000

User talk:Seanmcneil3

2008-12-20T07:18:55Z

Imrehg: /* Android running problems */ Low sound level - update

==What's new?==
This would be a nice area for a changelog. What's new in the November 17th image? Anything worth noting?

== Android running problems ==

I had flashed it now on my FR but it doesn't work. I see only a black screen.

It works, but you need 2 partition on your SD card. First about 8MB formated vfat, secound ext3. That partitions must be empty.

--

Hi Sean, how can the imgages be put on the GTA02? I also flashed my GTA02 and android will not start, only black screen.

Sean:
I've just begun adding more information to the page which explains what is necessary to bring up Android. Sorry for the delay.

--

Hi Sean I split sd card to 2 partition fat32 and ext3, noting in fat32(1.5g) and in ext3(2.2G) have lostxxfound directory,I never set boot flag to sd card's partition, now I flash image and rootfs according your "setup guide" but now it not start just black screen. what's wrong with it

--

Hi Sean,
same problem: I flashed the kernel and rootfs. My SDcard has a primary 100MB FAT16 and an other primay 400MB EXT3 partition. I only get a black screen.

--

Hi,
When using Android, some menu items are don't work. E.g. when trying to set the Phone Ringtone, the menu shows for a split second and then I'm back to the Sound settings. The log shows the following:
<pre>
I/ActivityManager( 855): Starting activity: Intent { action=android.intent.action.RINGTONE_PICKER comp={android/com.android.internal.app.RingtonePickerActivity} (has extras) }
I/ActivityManager( 855): Start proc android.process.media for content provider com.android.providers.media/.MediaProvider: pid=1385 uid=10003 gids={1006, 3003, 2001}
I/ActivityThread( 1385): Publishing provider downloads: com.android.providers.downloads.DownloadProvider
I/ActivityThread( 1385): Publishing provider drm: com.android.providers.drm.DrmProvider
I/ActivityThread( 1385): Publishing provider media: com.android.providers.media.MediaProvider
V/MediaProvider( 1385): Attached volume: internal
V/MediaProvider( 1385): /sdcard volume ID: -1
V/MediaProvider( 1385): Attached volume: external
I/ActivityManager( 855): Exiting empty application process android.process.media (android.os.BinderProxy@435052d8)
I/Process ( 855): Sending signal. PID: 1385 SIG: 9
I/ActivityManager( 855): Killing app com.android.settings (pid 1377) because provider com.android.providers.media.MediaProvider is in dying process android.process.media
I/Process ( 855): Sending signal. PID: 1377 SIG: 9
I/ActivityManager( 855): Killing app com.android.settings (pid 1377) because provider com.android.providers.drm.DrmProvider is in dying process android.process.media
I/Process ( 855): Sending signal. PID: 1377 SIG: 9
D/ActivityManager( 855): Received spurious death notification for thread android.os.BinderProxy@435052d8
I/ActivityManager( 855): Process com.android.settings (pid 1377) has died.
I/WindowManager( 855): WIN DEATH: Window{434e8b10 com.android.settings/com.android.settings.SoundAndDisplaySettings}
I/WindowManager( 855): WIN DEATH: Window{434f1520 android/com.android.internal.app.RingtonePickerActivity}
I/ActivityManager( 855): Start proc com.android.settings for activity com.android.settings/.SoundAndDisplaySettings: pid=1396 uid=1000 gids={3001, 3003}
I/ActivityManager( 855): Low Memory: No more background processes.
D/dalvikvm( 855): GC freed 2248 objects / 104336 bytes in 727ms
W/SurfaceComposerClient( 855): lock_layer timed out (is the CPU pegged?) layer=1, lcblk=0x423800a0, state=0000000c (was 0000000c)
D/dalvikvm( 888): GC freed 167 objects / 6208 bytes in 958ms
D/dalvikvm( 894): GC freed 15 objects / 560 bytes in 998ms
I/ActivityManager( 855): Displayed activity com.android.settings/.SoundAndDisplaySettings: 2675 ms
</pre>
I was not sure if it is because I had relatively small space dedicated to teh VFAT and Ext3 partitions on the SD card (so I can have another distro on the 3rd partition), but it seems to be enough:
<pre>
/: 252544K total, 38468K used, 214076K available (block size 4096)
/: 252544K total, 38468K used, 214076K available (block size 4096)
/dev: 59952K total, 0K used, 59952K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/data: 30985K total, 19413K used, 11572K available (block size 1024)
/sdcard: 31912K total, 1782K used, 30130K available (block size 2048)
</pre>
Other menu items do the same thing sometimes, but I forgot which one I found last time. In the log they also had the "Low memory" warning, so should originate the same place. --[[User:Imrehg|Imrehg]] 05:10, 20 December 2008 (UTC)

--

Sending message breaks network connection.
When I'm trying to send a message, the network disconnects (without sending the SMS) and won't work even with reboot, until I delete the message thread and reboot (sometimes even need reboot a few times after message delete). Receiving a message works just fine.
The log of the message send (after clicking the send button):
<pre>
D/SmsProvider( 888): insert url=content://sms/outbox, match=8
I/ActivityManager( 855): Stopping service: com.android.mms/.transaction.SmsReceiverService
I/ActivityManager( 855): Stopping service: com.android.mms/.transaction.SmsReceiverService
I/NotificationService( 855): enqueueToast pkg=com.android.mms callback=android.app.ITransientNotification$Stub$Proxy@435bc740 duration=0
</pre>
Not sure whether it matters, my network is TWN GSM (Taiwan) --[[User:Imrehg|Imrehg]] 05:34, 20 December 2008 (UTC)

--

Volume during call is too low. When not in call, the soft-keyboard has the Vol+ and Vol- buttons, but of course they don't do anything. During call, the volume is too low, I can hardly hear anything. On the receiving end they can hear me perfectly clear. If trying to bring up the soft-keyboard during call with the Menu (the Power button at the moment), then instead of the previously mentioned menu (which has the keyboard option) the Contacts menu comes up... Thus no way to adjust the volume and making the phone almost unusable for calls, unless I'm in a perfectly silent environment. --[[User:Imrehg|Imrehg]] 05:38, 20 December 2008 (UTC)

'''Update:''' Could access the keyboard as: Pressing Menu (power) button once -> Phone displays contacts menu -> Menu button again -> Soft-keyboard key. The displayed Vol+/Vol- buttons (and probably the rest of the function buttons) don't have any effect on the call, it is still the same low sound level. --[[User:Imrehg|Imrehg]] 07:18, 20 December 2008 (UTC)

== Android doesn't accept the pin ==

I have flashed my GTA02 and android will boot but it does not accept the pin code for my SIM-card.
Jofry

Sean:
Hi Jofry, I've never really tried a locked SIM, so I don't know if the dialpad comes up to let you type in the code. Does it? If so, then I can probably fix the issue. Otherwise, we are kind of stuck until a virtual keyboard is developed.

Jofry: Yes, the dialpad comes up and ask for my pin number. But if i type in the number the application means that it was the wrong number. But it is the right one.

Skamster: i've got the same problem. i could enter the pin as much as i want but it doesn't let me in. normaly, it lock the sim after 3 try's (i try 4-6 times), but here it doesn't. i flashed with qtopia again and don't need a puck. maybe it doesn't "send" the pin to the simcard?

--

i've got the same problem like jofry. i could enter the pin as much as i want but it doesn't let me in. normaly, it lock the sim after 3 try's (i try 4-6 times), but here it doesn't. i flashed with qtopia again and don't need a puck. maybe it doesn't "send" the pin to the simcard?

That's a known issue. For more information about the things you have to do, before you can successful use Android, look at http://onlinedev.blogspot.com/2008/11/getting-started-with-android-on-neo.html [[User:Dolfje|Dolfje]] 12:03, 5 November 2008 (UTC)

== Android rootfs for µSD boot ==

Treviño: Could you set-up a rootfs for running Android from MicroSD?

== Android and replying calls ==

Actually it is not possible to reply to a call due to the missing hardware "accept" button.

Treviño: So, what about adding a workaround to it by using the AUX button as an "accept" button if pressed briefly (below 0.5 second), while keeping it to the "reject" (home) button when pressed longer?!

ahk05: It seems that Yann neveu-2 has managed to modify the Phone app to allow you to answer phone calls with the power button. Maybe his apk should be included in your image?
http://n2.nabble.com/-Android--Soft-keyboard-td1518369.html
http://gabuzomeu.fr/openmoko/Phone.apk

== Android Misc requests ==

--

dilersam: thanks for having added more informations to the page. It helps a lot.

-

fate: thanks for all your great work. i was wondering when will the next flash image be released?

== u-boot environment changes for large kernel ==

I'm using [[neocon]] to connect to the u-boot console. What env variable should we change and to what values?

Thanks!

- I'm using Kermit, and this is what I change in the console

setenv bootargs ${bootargs_base} ${mtdparts}; nand read.e 0x32000000 kernel; bootm 0x32000000

User:Imrehg

2008-12-20T05:44:24Z

Imrehg: Added interests

Openmoko user from Miskolc,Hungary; Oxford,UK; Taipei,Taiwan (been living around places....)

--

Interests:
* Om2008.X/FSO:
** GSM positioning app
** Network Time setting
** GPS Mapping app
** Games
* Android on Openmoko:
** Improving usability (lots of testing and feedback)
** Getting useful apps from Om distro work, or get substitutes (e.g. mapping)
** SIM contacts import app

User talk:Seanmcneil3

2008-12-20T05:38:29Z

Imrehg: /* Android running problems */ No way to adjust incoming call volume.

==What's new?==
This would be a nice area for a changelog. What's new in the November 17th image? Anything worth noting?

== Android running problems ==

I had flashed it now on my FR but it doesn't work. I see only a black screen.

It works, but you need 2 partition on your SD card. First about 8MB formated vfat, secound ext3. That partitions must be empty.

--

Hi Sean, how can the imgages be put on the GTA02? I also flashed my GTA02 and android will not start, only black screen.

Sean:
I've just begun adding more information to the page which explains what is necessary to bring up Android. Sorry for the delay.

--

Hi Sean I split sd card to 2 partition fat32 and ext3, noting in fat32(1.5g) and in ext3(2.2G) have lostxxfound directory,I never set boot flag to sd card's partition, now I flash image and rootfs according your "setup guide" but now it not start just black screen. what's wrong with it

--

Hi Sean,
same problem: I flashed the kernel and rootfs. My SDcard has a primary 100MB FAT16 and an other primay 400MB EXT3 partition. I only get a black screen.

--

Hi,
When using Android, some menu items are don't work. E.g. when trying to set the Phone Ringtone, the menu shows for a split second and then I'm back to the Sound settings. The log shows the following:
<pre>
I/ActivityManager( 855): Starting activity: Intent { action=android.intent.action.RINGTONE_PICKER comp={android/com.android.internal.app.RingtonePickerActivity} (has extras) }
I/ActivityManager( 855): Start proc android.process.media for content provider com.android.providers.media/.MediaProvider: pid=1385 uid=10003 gids={1006, 3003, 2001}
I/ActivityThread( 1385): Publishing provider downloads: com.android.providers.downloads.DownloadProvider
I/ActivityThread( 1385): Publishing provider drm: com.android.providers.drm.DrmProvider
I/ActivityThread( 1385): Publishing provider media: com.android.providers.media.MediaProvider
V/MediaProvider( 1385): Attached volume: internal
V/MediaProvider( 1385): /sdcard volume ID: -1
V/MediaProvider( 1385): Attached volume: external
I/ActivityManager( 855): Exiting empty application process android.process.media (android.os.BinderProxy@435052d8)
I/Process ( 855): Sending signal. PID: 1385 SIG: 9
I/ActivityManager( 855): Killing app com.android.settings (pid 1377) because provider com.android.providers.media.MediaProvider is in dying process android.process.media
I/Process ( 855): Sending signal. PID: 1377 SIG: 9
I/ActivityManager( 855): Killing app com.android.settings (pid 1377) because provider com.android.providers.drm.DrmProvider is in dying process android.process.media
I/Process ( 855): Sending signal. PID: 1377 SIG: 9
D/ActivityManager( 855): Received spurious death notification for thread android.os.BinderProxy@435052d8
I/ActivityManager( 855): Process com.android.settings (pid 1377) has died.
I/WindowManager( 855): WIN DEATH: Window{434e8b10 com.android.settings/com.android.settings.SoundAndDisplaySettings}
I/WindowManager( 855): WIN DEATH: Window{434f1520 android/com.android.internal.app.RingtonePickerActivity}
I/ActivityManager( 855): Start proc com.android.settings for activity com.android.settings/.SoundAndDisplaySettings: pid=1396 uid=1000 gids={3001, 3003}
I/ActivityManager( 855): Low Memory: No more background processes.
D/dalvikvm( 855): GC freed 2248 objects / 104336 bytes in 727ms
W/SurfaceComposerClient( 855): lock_layer timed out (is the CPU pegged?) layer=1, lcblk=0x423800a0, state=0000000c (was 0000000c)
D/dalvikvm( 888): GC freed 167 objects / 6208 bytes in 958ms
D/dalvikvm( 894): GC freed 15 objects / 560 bytes in 998ms
I/ActivityManager( 855): Displayed activity com.android.settings/.SoundAndDisplaySettings: 2675 ms
</pre>
I was not sure if it is because I had relatively small space dedicated to teh VFAT and Ext3 partitions on the SD card (so I can have another distro on the 3rd partition), but it seems to be enough:
<pre>
/: 252544K total, 38468K used, 214076K available (block size 4096)
/: 252544K total, 38468K used, 214076K available (block size 4096)
/dev: 59952K total, 0K used, 59952K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/data: 30985K total, 19413K used, 11572K available (block size 1024)
/sdcard: 31912K total, 1782K used, 30130K available (block size 2048)
</pre>
Other menu items do the same thing sometimes, but I forgot which one I found last time. In the log they also had the "Low memory" warning, so should originate the same place. --[[User:Imrehg|Imrehg]] 05:10, 20 December 2008 (UTC)

--

Sending message breaks network connection.
When I'm trying to send a message, the network disconnects (without sending the SMS) and won't work even with reboot, until I delete the message thread and reboot (sometimes even need reboot a few times after message delete). Receiving a message works just fine.
The log of the message send (after clicking the send button):
<pre>
D/SmsProvider( 888): insert url=content://sms/outbox, match=8
I/ActivityManager( 855): Stopping service: com.android.mms/.transaction.SmsReceiverService
I/ActivityManager( 855): Stopping service: com.android.mms/.transaction.SmsReceiverService
I/NotificationService( 855): enqueueToast pkg=com.android.mms callback=android.app.ITransientNotification$Stub$Proxy@435bc740 duration=0
</pre>
Not sure whether it matters, my network is TWN GSM (Taiwan) --[[User:Imrehg|Imrehg]] 05:34, 20 December 2008 (UTC)

--

Volume during call is too low. When not in call, the soft-keyboard has the Vol+ and Vol- buttons, but of course they don't do anything. During call, the volume is too low, I can hardly hear anything. On the receiving end they can hear me perfectly clear. If trying to bring up the soft-keyboard during call with the Menu (the Power button at the moment), then instead of the previously mentioned menu (which has the keyboard option) the Contacts menu comes up... Thus no way to adjust the volume and making the phone almost unusable for calls, unless I'm in a perfectly silent environment. --[[User:Imrehg|Imrehg]] 05:38, 20 December 2008 (UTC)

== Android doesn't accept the pin ==

I have flashed my GTA02 and android will boot but it does not accept the pin code for my SIM-card.
Jofry

Sean:
Hi Jofry, I've never really tried a locked SIM, so I don't know if the dialpad comes up to let you type in the code. Does it? If so, then I can probably fix the issue. Otherwise, we are kind of stuck until a virtual keyboard is developed.

Jofry: Yes, the dialpad comes up and ask for my pin number. But if i type in the number the application means that it was the wrong number. But it is the right one.

Skamster: i've got the same problem. i could enter the pin as much as i want but it doesn't let me in. normaly, it lock the sim after 3 try's (i try 4-6 times), but here it doesn't. i flashed with qtopia again and don't need a puck. maybe it doesn't "send" the pin to the simcard?

--

i've got the same problem like jofry. i could enter the pin as much as i want but it doesn't let me in. normaly, it lock the sim after 3 try's (i try 4-6 times), but here it doesn't. i flashed with qtopia again and don't need a puck. maybe it doesn't "send" the pin to the simcard?

That's a known issue. For more information about the things you have to do, before you can successful use Android, look at http://onlinedev.blogspot.com/2008/11/getting-started-with-android-on-neo.html [[User:Dolfje|Dolfje]] 12:03, 5 November 2008 (UTC)

== Android rootfs for µSD boot ==

Treviño: Could you set-up a rootfs for running Android from MicroSD?

== Android and replying calls ==

Actually it is not possible to reply to a call due to the missing hardware "accept" button.

Treviño: So, what about adding a workaround to it by using the AUX button as an "accept" button if pressed briefly (below 0.5 second), while keeping it to the "reject" (home) button when pressed longer?!

ahk05: It seems that Yann neveu-2 has managed to modify the Phone app to allow you to answer phone calls with the power button. Maybe his apk should be included in your image?
http://n2.nabble.com/-Android--Soft-keyboard-td1518369.html
http://gabuzomeu.fr/openmoko/Phone.apk

== Android Misc requests ==

--

dilersam: thanks for having added more informations to the page. It helps a lot.

-

fate: thanks for all your great work. i was wondering when will the next flash image be released?

== u-boot environment changes for large kernel ==

I'm using [[neocon]] to connect to the u-boot console. What env variable should we change and to what values?

Thanks!

- I'm using Kermit, and this is what I change in the console

setenv bootargs ${bootargs_base} ${mtdparts}; nand read.e 0x32000000 kernel; bootm 0x32000000

User talk:Seanmcneil3

2008-12-20T05:34:13Z

Imrehg: /* Android running problems */ Sending message disconnects network

==What's new?==
This would be a nice area for a changelog. What's new in the November 17th image? Anything worth noting?

== Android running problems ==

I had flashed it now on my FR but it doesn't work. I see only a black screen.

It works, but you need 2 partition on your SD card. First about 8MB formated vfat, secound ext3. That partitions must be empty.

--

Hi Sean, how can the imgages be put on the GTA02? I also flashed my GTA02 and android will not start, only black screen.

Sean:
I've just begun adding more information to the page which explains what is necessary to bring up Android. Sorry for the delay.

--

Hi Sean I split sd card to 2 partition fat32 and ext3, noting in fat32(1.5g) and in ext3(2.2G) have lostxxfound directory,I never set boot flag to sd card's partition, now I flash image and rootfs according your "setup guide" but now it not start just black screen. what's wrong with it

--

Hi Sean,
same problem: I flashed the kernel and rootfs. My SDcard has a primary 100MB FAT16 and an other primay 400MB EXT3 partition. I only get a black screen.

--

Hi,
When using Android, some menu items are don't work. E.g. when trying to set the Phone Ringtone, the menu shows for a split second and then I'm back to the Sound settings. The log shows the following:
<pre>
I/ActivityManager( 855): Starting activity: Intent { action=android.intent.action.RINGTONE_PICKER comp={android/com.android.internal.app.RingtonePickerActivity} (has extras) }
I/ActivityManager( 855): Start proc android.process.media for content provider com.android.providers.media/.MediaProvider: pid=1385 uid=10003 gids={1006, 3003, 2001}
I/ActivityThread( 1385): Publishing provider downloads: com.android.providers.downloads.DownloadProvider
I/ActivityThread( 1385): Publishing provider drm: com.android.providers.drm.DrmProvider
I/ActivityThread( 1385): Publishing provider media: com.android.providers.media.MediaProvider
V/MediaProvider( 1385): Attached volume: internal
V/MediaProvider( 1385): /sdcard volume ID: -1
V/MediaProvider( 1385): Attached volume: external
I/ActivityManager( 855): Exiting empty application process android.process.media (android.os.BinderProxy@435052d8)
I/Process ( 855): Sending signal. PID: 1385 SIG: 9
I/ActivityManager( 855): Killing app com.android.settings (pid 1377) because provider com.android.providers.media.MediaProvider is in dying process android.process.media
I/Process ( 855): Sending signal. PID: 1377 SIG: 9
I/ActivityManager( 855): Killing app com.android.settings (pid 1377) because provider com.android.providers.drm.DrmProvider is in dying process android.process.media
I/Process ( 855): Sending signal. PID: 1377 SIG: 9
D/ActivityManager( 855): Received spurious death notification for thread android.os.BinderProxy@435052d8
I/ActivityManager( 855): Process com.android.settings (pid 1377) has died.
I/WindowManager( 855): WIN DEATH: Window{434e8b10 com.android.settings/com.android.settings.SoundAndDisplaySettings}
I/WindowManager( 855): WIN DEATH: Window{434f1520 android/com.android.internal.app.RingtonePickerActivity}
I/ActivityManager( 855): Start proc com.android.settings for activity com.android.settings/.SoundAndDisplaySettings: pid=1396 uid=1000 gids={3001, 3003}
I/ActivityManager( 855): Low Memory: No more background processes.
D/dalvikvm( 855): GC freed 2248 objects / 104336 bytes in 727ms
W/SurfaceComposerClient( 855): lock_layer timed out (is the CPU pegged?) layer=1, lcblk=0x423800a0, state=0000000c (was 0000000c)
D/dalvikvm( 888): GC freed 167 objects / 6208 bytes in 958ms
D/dalvikvm( 894): GC freed 15 objects / 560 bytes in 998ms
I/ActivityManager( 855): Displayed activity com.android.settings/.SoundAndDisplaySettings: 2675 ms
</pre>
I was not sure if it is because I had relatively small space dedicated to teh VFAT and Ext3 partitions on the SD card (so I can have another distro on the 3rd partition), but it seems to be enough:
<pre>
/: 252544K total, 38468K used, 214076K available (block size 4096)
/: 252544K total, 38468K used, 214076K available (block size 4096)
/dev: 59952K total, 0K used, 59952K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/data: 30985K total, 19413K used, 11572K available (block size 1024)
/sdcard: 31912K total, 1782K used, 30130K available (block size 2048)
</pre>
Other menu items do the same thing sometimes, but I forgot which one I found last time. In the log they also had the "Low memory" warning, so should originate the same place. --[[User:Imrehg|Imrehg]] 05:10, 20 December 2008 (UTC)

--

Sending message breaks network connection.
When I'm trying to send a message, the network disconnects (without sending the SMS) and won't work even with reboot, until I delete the message thread and reboot (sometimes even need reboot a few times after message delete). Receiving a message works just fine.
The log of the message send (after clicking the send button):
<pre>
D/SmsProvider( 888): insert url=content://sms/outbox, match=8
I/ActivityManager( 855): Stopping service: com.android.mms/.transaction.SmsReceiverService
I/ActivityManager( 855): Stopping service: com.android.mms/.transaction.SmsReceiverService
I/NotificationService( 855): enqueueToast pkg=com.android.mms callback=android.app.ITransientNotification$Stub$Proxy@435bc740 duration=0
</pre>
Not sure whether it matters, my network is TWN GSM (Taiwan) --[[User:Imrehg|Imrehg]] 05:34, 20 December 2008 (UTC)

== Android doesn't accept the pin ==

I have flashed my GTA02 and android will boot but it does not accept the pin code for my SIM-card.
Jofry

Sean:
Hi Jofry, I've never really tried a locked SIM, so I don't know if the dialpad comes up to let you type in the code. Does it? If so, then I can probably fix the issue. Otherwise, we are kind of stuck until a virtual keyboard is developed.

Jofry: Yes, the dialpad comes up and ask for my pin number. But if i type in the number the application means that it was the wrong number. But it is the right one.

Skamster: i've got the same problem. i could enter the pin as much as i want but it doesn't let me in. normaly, it lock the sim after 3 try's (i try 4-6 times), but here it doesn't. i flashed with qtopia again and don't need a puck. maybe it doesn't "send" the pin to the simcard?

--

i've got the same problem like jofry. i could enter the pin as much as i want but it doesn't let me in. normaly, it lock the sim after 3 try's (i try 4-6 times), but here it doesn't. i flashed with qtopia again and don't need a puck. maybe it doesn't "send" the pin to the simcard?

That's a known issue. For more information about the things you have to do, before you can successful use Android, look at http://onlinedev.blogspot.com/2008/11/getting-started-with-android-on-neo.html [[User:Dolfje|Dolfje]] 12:03, 5 November 2008 (UTC)

== Android rootfs for µSD boot ==

Treviño: Could you set-up a rootfs for running Android from MicroSD?

== Android and replying calls ==

Actually it is not possible to reply to a call due to the missing hardware "accept" button.

Treviño: So, what about adding a workaround to it by using the AUX button as an "accept" button if pressed briefly (below 0.5 second), while keeping it to the "reject" (home) button when pressed longer?!

ahk05: It seems that Yann neveu-2 has managed to modify the Phone app to allow you to answer phone calls with the power button. Maybe his apk should be included in your image?
http://n2.nabble.com/-Android--Soft-keyboard-td1518369.html
http://gabuzomeu.fr/openmoko/Phone.apk

== Android Misc requests ==

--

dilersam: thanks for having added more informations to the page. It helps a lot.

-

fate: thanks for all your great work. i was wondering when will the next flash image be released?

== u-boot environment changes for large kernel ==

I'm using [[neocon]] to connect to the u-boot console. What env variable should we change and to what values?

Thanks!

- I'm using Kermit, and this is what I change in the console

setenv bootargs ${bootargs_base} ${mtdparts}; nand read.e 0x32000000 kernel; bootm 0x32000000

User talk:Seanmcneil3

2008-12-20T05:10:34Z

Imrehg: /* Android running problems */ Low memory prevents some menus.

==What's new?==
This would be a nice area for a changelog. What's new in the November 17th image? Anything worth noting?

== Android running problems ==

I had flashed it now on my FR but it doesn't work. I see only a black screen.

It works, but you need 2 partition on your SD card. First about 8MB formated vfat, secound ext3. That partitions must be empty.

--

Hi Sean, how can the imgages be put on the GTA02? I also flashed my GTA02 and android will not start, only black screen.

Sean:
I've just begun adding more information to the page which explains what is necessary to bring up Android. Sorry for the delay.

--

Hi Sean I split sd card to 2 partition fat32 and ext3, noting in fat32(1.5g) and in ext3(2.2G) have lostxxfound directory,I never set boot flag to sd card's partition, now I flash image and rootfs according your "setup guide" but now it not start just black screen. what's wrong with it

--

Hi Sean,
same problem: I flashed the kernel and rootfs. My SDcard has a primary 100MB FAT16 and an other primay 400MB EXT3 partition. I only get a black screen.

--

Hi,
When using Android, some menu items are don't work. E.g. when trying to set the Phone Ringtone, the menu shows for a split second and then I'm back to the Sound settings. The log shows the following:
<pre>
I/ActivityManager( 855): Starting activity: Intent { action=android.intent.action.RINGTONE_PICKER comp={android/com.android.internal.app.RingtonePickerActivity} (has extras) }
I/ActivityManager( 855): Start proc android.process.media for content provider com.android.providers.media/.MediaProvider: pid=1385 uid=10003 gids={1006, 3003, 2001}
I/ActivityThread( 1385): Publishing provider downloads: com.android.providers.downloads.DownloadProvider
I/ActivityThread( 1385): Publishing provider drm: com.android.providers.drm.DrmProvider
I/ActivityThread( 1385): Publishing provider media: com.android.providers.media.MediaProvider
V/MediaProvider( 1385): Attached volume: internal
V/MediaProvider( 1385): /sdcard volume ID: -1
V/MediaProvider( 1385): Attached volume: external
I/ActivityManager( 855): Exiting empty application process android.process.media (android.os.BinderProxy@435052d8)
I/Process ( 855): Sending signal. PID: 1385 SIG: 9
I/ActivityManager( 855): Killing app com.android.settings (pid 1377) because provider com.android.providers.media.MediaProvider is in dying process android.process.media
I/Process ( 855): Sending signal. PID: 1377 SIG: 9
I/ActivityManager( 855): Killing app com.android.settings (pid 1377) because provider com.android.providers.drm.DrmProvider is in dying process android.process.media
I/Process ( 855): Sending signal. PID: 1377 SIG: 9
D/ActivityManager( 855): Received spurious death notification for thread android.os.BinderProxy@435052d8
I/ActivityManager( 855): Process com.android.settings (pid 1377) has died.
I/WindowManager( 855): WIN DEATH: Window{434e8b10 com.android.settings/com.android.settings.SoundAndDisplaySettings}
I/WindowManager( 855): WIN DEATH: Window{434f1520 android/com.android.internal.app.RingtonePickerActivity}
I/ActivityManager( 855): Start proc com.android.settings for activity com.android.settings/.SoundAndDisplaySettings: pid=1396 uid=1000 gids={3001, 3003}
I/ActivityManager( 855): Low Memory: No more background processes.
D/dalvikvm( 855): GC freed 2248 objects / 104336 bytes in 727ms
W/SurfaceComposerClient( 855): lock_layer timed out (is the CPU pegged?) layer=1, lcblk=0x423800a0, state=0000000c (was 0000000c)
D/dalvikvm( 888): GC freed 167 objects / 6208 bytes in 958ms
D/dalvikvm( 894): GC freed 15 objects / 560 bytes in 998ms
I/ActivityManager( 855): Displayed activity com.android.settings/.SoundAndDisplaySettings: 2675 ms
</pre>
I was not sure if it is because I had relatively small space dedicated to teh VFAT and Ext3 partitions on the SD card (so I can have another distro on the 3rd partition), but it seems to be enough:
<pre>
/: 252544K total, 38468K used, 214076K available (block size 4096)
/: 252544K total, 38468K used, 214076K available (block size 4096)
/dev: 59952K total, 0K used, 59952K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/data: 30985K total, 19413K used, 11572K available (block size 1024)
/sdcard: 31912K total, 1782K used, 30130K available (block size 2048)
</pre>
Other menu items do the same thing sometimes, but I forgot which one I found last time. In the log they also had the "Low memory" warning, so should originate the same place. --[[User:Imrehg|Imrehg]] 05:10, 20 December 2008 (UTC)

== Android doesn't accept the pin ==

I have flashed my GTA02 and android will boot but it does not accept the pin code for my SIM-card.
Jofry

Sean:
Hi Jofry, I've never really tried a locked SIM, so I don't know if the dialpad comes up to let you type in the code. Does it? If so, then I can probably fix the issue. Otherwise, we are kind of stuck until a virtual keyboard is developed.

Jofry: Yes, the dialpad comes up and ask for my pin number. But if i type in the number the application means that it was the wrong number. But it is the right one.

Skamster: i've got the same problem. i could enter the pin as much as i want but it doesn't let me in. normaly, it lock the sim after 3 try's (i try 4-6 times), but here it doesn't. i flashed with qtopia again and don't need a puck. maybe it doesn't "send" the pin to the simcard?

--

i've got the same problem like jofry. i could enter the pin as much as i want but it doesn't let me in. normaly, it lock the sim after 3 try's (i try 4-6 times), but here it doesn't. i flashed with qtopia again and don't need a puck. maybe it doesn't "send" the pin to the simcard?

That's a known issue. For more information about the things you have to do, before you can successful use Android, look at http://onlinedev.blogspot.com/2008/11/getting-started-with-android-on-neo.html [[User:Dolfje|Dolfje]] 12:03, 5 November 2008 (UTC)

== Android rootfs for µSD boot ==

Treviño: Could you set-up a rootfs for running Android from MicroSD?

== Android and replying calls ==

Actually it is not possible to reply to a call due to the missing hardware "accept" button.

Treviño: So, what about adding a workaround to it by using the AUX button as an "accept" button if pressed briefly (below 0.5 second), while keeping it to the "reject" (home) button when pressed longer?!

ahk05: It seems that Yann neveu-2 has managed to modify the Phone app to allow you to answer phone calls with the power button. Maybe his apk should be included in your image?
http://n2.nabble.com/-Android--Soft-keyboard-td1518369.html
http://gabuzomeu.fr/openmoko/Phone.apk

== Android Misc requests ==

--

dilersam: thanks for having added more informations to the page. It helps a lot.

-

fate: thanks for all your great work. i was wondering when will the next flash image be released?

== u-boot environment changes for large kernel ==

I'm using [[neocon]] to connect to the u-boot console. What env variable should we change and to what values?

Thanks!

- I'm using Kermit, and this is what I change in the console

setenv bootargs ${bootargs_base} ${mtdparts}; nand read.e 0x32000000 kernel; bootm 0x32000000

ReMoko

2008-11-30T01:52:18Z

Imrehg: /* Wish List */

{{InProgress}}

{{application|ReMoko}}
[[Image:Remoko_menu.jpg|thumb]]

==About==

* Openmoko remote controller is a [[Summer of Code 2008]] project, that aims to write a application that can make Openmoko-powered devices appear to be a mixed Bluetooth keyboard-and-mouse device.
*'''Student:''' [http://www.valeriovalerio.org Valério Valério]
*'''Mentor:''' Daniel Willmann

==Videos==

[http://www.youtube.com/watch?v=S_eSvEOGaJc ReMoko video]

==ReMoko v0.3==

===Downloads===

[http://code.google.com/p/remoko/downloads/list ReMoko Packages]

===Install Instructions===

*'''ReMoko dependencies'''
**bluez-utils (>= 3.23) remokoserver python-ecore python-edbus python-edje python-evas python-dbus python-textutils

*'''FSO Milestone 2'''
** Runs "out of the box"

*'''FSO Milestone 3'''
** Runs "out of the box"
** Requires ReMoko version >= 0.3.2.

*'''FSO Milestone 4'''
** Runs "out of the box"
** Requires ReMoko version >= 0.3.2.

*'''ASU 2008.08'''
** Runs "out of the box", if all dependencies are satisfied
** Careful with this bug: [https://docs.openmoko.org/trac/ticket/1744 Ticket #1744];

*'''ASU 2008.09'''
** Runs "out of the box", if all dependencies are satisfied
** Careful with this bug: [https://docs.openmoko.org/trac/ticket/1744 Ticket #1744];

*'''FDOM'''
** Runs "out of the box", if all dependencies are satisfied

*'''Debian'''
** Runs "out of the box" - Thanks to Joachim Breitner
** Could require a small fix dependent on the BlueZ-utils version, see readme.debian in the doc folder of ReMoko for more details

===Usage===

* Linux
** Start the remoko app in the neo;
** In a shell type 'hcitool scan' to find the address of the neo.
** In a shell type 'hidd --connect <neo_bt_addr>' (need root privileges) or use a user interface to choose the neo as a bluetooth keyboard; '''Note:''' In Ubuntu Intrepid Ibex you have to install bluez-compat package to get hidd. Otherwise you can try using the bluetooth GUI, but as of now (2008-10-23) this is not working for me.

* Windows XP and Media Center Edition
** Start the remoko app in the neo;
** Go to the bluetooth preferences and choose 'Add a new device';
** Choose the neo (default name is 'BlueZ (0)') and choose 'no password';

===Using custom keys===
* The keys bellow don't exist by default in the Illume/qtopia keyboard's, to add this keys to a profile you have to write the keys (e.g: f1 -> press f and then 1).
Allowed Keys:
f1-f12
win (plus any letter or number)

===Using Gestures===
* To use [[gestures]] to send events, you just need to install the gestures package (no need to start the gestures listener). You can also train the gestures.

===Features===
*'''Connection'''
** Connection to the majority of the bluetooth stacks;
** Connection status daemon (possibility to connect to the remote device when the connection are closed);
** Information about the remote device;
*'''Mouse Profile'''
** 3 button's mouse;
** Left button mouse holding (for drawing for example);
** Tapping functionality, like a touchpad;
** Vertical Scroll;
*'''Keyboard Profile'''
** Full qwerty keyboard;
** Numeric keyboard;
** Holding for Capslock, Shift, Control, Alt and Control + Alt;
** Mouse area with tapping functionality;
*'''Settings Profile'''
** Option to run the app in fullscreen mode or window mode;
** Option to set the sensitivity of the mouse scroll;

===Known Issus===
* The installer is a little bit broken at the moment, so check all the ReMoko dependencies, for Om 2008.8 the package: python-textutils should be the only dependence missing by default.
* In some images (last FSO) the keyboard only show up, if the app is in window mode;
* The mouse profile can slow down a little bit if you have the gestures daemon and other program running on the phone.
* Connection problems with Symbian S60 devices with BT-HID keyboard app provided by Nokia;

===Tested Bluetooth Stacks ===
*'''Working'''
** Linux BlueZ Stack
** Windows XP SP2
** Windows Media Center Edition (Toshiba Bluetooth Stack)
** Nokia Maemo bluetooth stack (based in BlueZ)

*'''Not Working'''
** Symbian Nokia's S60 - tested with Nokia Navigator (probably a BlueZ SDP bug)

===TODO===

* Games profile;

===Need help in:===
* Application logo (Tag name: ReMoko);
* Set of menu icon related to the neo (Icons in use are from the Gnome project, enlightenment project and [http://wiki.openmoko.org/wiki/User:Nenadgrujicic Nenadgrujicic]. ReMoko icon made by [http://wiki.openmoko.org/wiki/User:Fradeve11 Fradeve11])

===ScreenShots===
*Remoko Menu [[Image:Remoko_menu.jpg|150px]]
*Remoko Mouse profile [[Image:remoko_mouse.jpg|150px]]
*Remoko Presentation menu [[Image:remoko_presentation_menu.jpg|150px]]
*Remoko Multimedia menu [[Image:remoko_multimedia_menu.jpg|150px]]
*Remoko Multimedia menu configurations [[Image: remoko_multimedia_conf.jpg|150px]]
*Remoko About Screen [[Image:remoko_about.jpg|150px]]

==Ideas for the application name==

*MokoRemote
*BlueRemote
*ReMoko or ReMoto (maybe some character that's a combination of t and k, at least in the splash/logo)
*Mokomote
*Mokomo (shorter) -- + 1 vote
*FreeMote (Builds on freerunner and remote) -- +2 vote
*MokoKeyMouse (It can be a bit too long, so you can make it shorter as: MKM)

*'''Add your idea here'''

==Ideas for the application logo==
* [[Image:Mokomote.png]] svg source avaiable, contact me --[[User:Fradeve11|Fradeve11]] 15:14, 27 April 2008 (CEST)
* '''Add your idea here'''

==Wish List==
*Possibility to use it with a PS3
* Possibility to control presentations easily (few buttons, PG-UP, PG-DOWN for example) - Done
** maybe even navigation via gestures[+1]
** possibly use the touchscreen similar to a touchpad (mouse) - Done
*** maybe it is too much, but if you manage to make the touchpad, you could get a small screenshot of the big screen (it is useful for presentations if you want to draw/write something without quality). - unsupported feature in HID Bluetooth profile
* ideally generic GUI that loads controls from some xml config file to make it fully customizable for different purposes (media remote, presenter stick, ...)
* Connect as a Bluetooth remote to a Sony Playstation 3 for Bluray/DVD playback. (JReese)
* Make use of profiles to change the interface easy and fast (interface for mouse, keyboard, a mix of those two, presentations, remote controller for videos and music, ...) - Done
** Use a number of different profiles for the media players. MediaPlayer uses different buttons then Real or VLC or Winamp or Exaile... One could switch between apps without tedious remapping of keys. Of course one could change the key bindings on some of the controlled software to be the same, but that's not always possible, so shouldn't be assumed as an option.
* Top part of screen as touch-pad, row of three mouse buttons across middle and whichever keyboard the user usually uses on the phone popped-up at the bottom as when adding text in any other app. - Done
* A MythTV remote would be handy, just a subset of a BT keyboard for common commands with a few nice icons rather than letters on (large) keys.
** E.g. all four arrows, 'Enter', 'p' (for play/pause), 'Escape', and 'a' and 'z' (or 'home' and 'end', to skip forward and back to flagged points, such as the beginning and end of commercials). Perhaps also comma and period, for rewind and fast-forward, respectively.
* Avahi search for HTTP services labeled say "remote" via ethernet (BT/LAN or Wifi). MythTV/Elisa and OOPresentation can develop their own html/flash/javascript/etc. "remotes" to hearts content without fine-grain syncing every change of code/GUI/API with your "Openmoko Remote App". Avahi/HTTP also lets desktop/laptop browsers to control "remotes"; this means a bigger community. - unsupported feature in HID Bluetooth profile
* Have one Neo work as a keyboard for another Neo (which becomes the screen)! (should be possible even now i guess)
* Change the icons on the mouse screen, so they are oriented as one's mouse would be. Right now the left mouse button is on the left, which is good. However, the image of the mouse is facing the user and the left mouse button is to the right of the image.
* Do all that, but through usb0 or Wifi next to bluetooth. Not every computer has bluetooth.
* Playlist data of running media application on computer could be send through bluetooth and than controled via BT. - unsupported feature in HID Bluetooth profile
* Using mouse through accelerometers, much like wiimote. A softbutton can be used to enable and disable this at will.
* See on the FreeRunner screen the notifications of the pc. eg "new mail received" or "playing song xxx" or "xxx connected on jabber"... - unsupported feature in HID Bluetooth profile
* Use FreeRunners AUX button as left mouse key. On other hardware a userdefineable key can be used. This would make things like drag-n-drop much more handy than the actual solution. Disabling the default screen locking functionality of the AUX button while in remote controle mode should be acceptable.
* '''Add your wish here'''

==Roadmap==

* 1- Write a HID BlueZ driver that can enable the Openmoko to be seen as a mixed keyboard and mouse in the three major OS's. - Done
* 2- Map keys and mouse gestures to the USB HID usage tables. - Done
* 3- Write the UI and some other features. - In progress

<onlyinclude>
{{ApplicationBox|
Name=[[ReMoko]]|
Description=ReMoko connects through Bluetooth and turns your FreeRunner into a remote control for presentations, a multimedia (or media player) remote control, a mouse for another computer and much more.|
Screenshot=Remoko_menu.jpg|
Homepage=http://code.google.com/p/remoko|
TestedOn=|
PackageName=
}}
</onlyinclude>

[[Category:System Applications]]
[[Category:Bluetooth]]

Neo FreeRunner Hardware Issues

2008-09-10T08:34:07Z

Imrehg: /* Can't boot with discharged or missing battery */ added report of successfuly booting when discharged

{{Neo FreeRunner Menu}}

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 [http://docs.openmoko.org/trac/ticket/1267 #1267]
* Buzzing noise caused by GSM radio interference [http://docs.openmoko.org/trac/ticket/883 #883] [http://docs.openmoko.org/trac/ticket/1352 #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 [http://lists.openmoko.org/pipermail/hardware/2008-August/000415.html identified].

Some [http://lists.openmoko.org/pipermail/hardware/2008-August/000451.html hidden Calypso commands] may help with the echo problem.

Workarounds:

# Using a bluetooth headset is a possibility.

# Better mixer settings: One confirmed good settings are here: http://www.mail-archive.com/support@lists.openmoko.org/msg00564.html. Please change accordingly in /usr/share/openmoko/scenarios/gsmhandset.state. Should eliminate/lessen echo and buzz problems.

==== 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 [http://lists.openmoko.org/pipermail/openmoko-kernel/2008-July/003799.html Werner Almesberger patches] - [http://lists.openmoko.org/pipermail/commitlog/2008-July/005403.html more here] [http://lists.openmoko.org/pipermail/community/2008-July/023392.html additional information]

Workarounds:

# Make sure that the battery never discharges completely
# Use external stand-alone charger (compatible with the Nokia BL-5C battery)
# Boot the FreeRunner with an [[Neo_FreeRunner_Battery#Compatible_Replacement_Batteries|alternative battery]], or with a spare GTA01 or GTA02 battery, plug USB power, then switch to the empty battery.
# Boot the FreeRunner with a 4.5VDC external power source (steady hand and great care involved), plug USB power, then insert the empty battery.
# 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.
## 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. [[User:Imrehg|Imrehg]] 08:34, 10 September 2008 (UTC)

See also:
:[[Neo_FreeRunner_Battery|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.

Status:

Workarounds:

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

Status:

[[https://docs.openmoko.org/trac/ticket/1802#comment:6 Patched kernel]] might solve the problem

Workarounds:

# [[https://docs.openmoko.org/trac/ticket/1802#comment:5 Script]] as a temporary workaround

See also:

:[[https://docs.openmoko.org/trac/ticket/1802 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 http://lists.openmoko.org/pipermail/community/2008-July/020370.html

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:
* http://wiki.openmoko.org/wiki/Carriers/ATT
* http://wiki.openmoko.org/wiki/Carriers/Rogers

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]]

Workarounds:

# Please document your existing SIM card and provider in the table [[FreeRunner_unable_to_work_with_3G_SIM_cards|here]]
# If the table mentioned above shows any SIM cards known to work with your provider, make note of these numbers
# 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.
# 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.
* [http://lists.openmoko.org/pipermail/hardware/2008-April/000055.html 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: http://lists.openmoko.org/pipermail/openmoko-kernel/2008-March/001999.html (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. [http://docs.openmoko.org/trac/ticket/1568 #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 [http://lists.openmoko.org/pipermail/device-owners/2008-July/001775.html 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 [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=957#c1 Bug 957]).

===Delivery of a GSM firmware update for the 3G SIM bug ([http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=666 #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.27t_Work|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 ([http://lists.openmoko.org/pipermail/community/2007-September/010175.html 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 [http://lists.openmoko.org/pipermail/community/2007-November/011349.html 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.

[[Category:Neo FreeRunner Hardware]]

User:Imrehg

2008-09-04T16:25:31Z

Imrehg: creation

Openmoko user from Miskolc,Hungary; Oxford,UK; Taipei,Taiwan (been living around places....)