Openmoko - User contributions [en]

Community Updates/2011-05-01

2011-04-18T08:44:02Z

Psonek: chess screenshot

{{Improve}}
{{Note|
*Take a moment and look at [[Talk:Community_Updates/Draft|this page]] to get a clue on how to contribute to Community Updates while following OM wiki editing guidelines please.
*I you are planning longer edition, please use <nowiki>{{Editing|your_username_here|date_here|editing_summary_here}}tag. Remember to remove/comment out it right after you save your work.</nowiki>
*Please fill in everything you think the community should know.
*On 2011-05-01 this content should be _moved_ to http://wiki.openmoko.org/wiki/Community_Updates/YYYY-MM-DD, feel free to do it.
*Post the CU release also on the community mailing list, since some people prefer to read news directly there. Regarding this, it helps copy-pasting from browser page to mailing list post if relevant URLs are included as is in addition to having linked parts of text (if in hurry you can also just post a note that CU is readable on web page).
}}



====='''Period 2011-03-01 to 2011-04-30'''=====

== Hardware ==

* [[Freerunner RFID Board]] - new hardware mod announced
* [[Freerunner Navigation Board v3]] - new version ready

== Distributions ==

Distributions lists releases and other significant updates in distributions that have some support for the Openmoko devices.

{{DistributionBox|
Name=Android Cupcake [Stable, January 2011]|
Description=The AoF community has uploaded an update of the stable Cupcake release of AoF. This release contains:
* All fixes from Android Cupcake (Google via scarhill)
* Separate NAND or SD based installations (ran)
* Improved GPS timestamps (michael)
* Updated APN list from Cyanogenmod (scarhill)
* WMIConfig for boosting WiFi power (niels)
|
Screenshot=Android-on-Freerunner-Splash.png|
Codename='Android Cupcake on Freerunner'|
Homepage=http://code.google.com/p/android-on-freerunner/|
Image=[http://code.google.com/p/android-on-freerunner/wiki/GetIt How to install]|
Works={{works on Android}}
}}

{{DistributionBox|
Name=Android Froyo [Experimental, April 2011]|
Description=The AoF community has uploaded an update of the experimental Froyo release of AoF. This release contains:
* All fixes from Android Froyo (Google via scarhill)
* Separate NAND or SD based installations (ran)
* Improved GPS timestamps (michael)
* Updated APN list from Cyanogenmod (scarhill)
* WMIConfig for boosting WiFi power (niels)
* GPRS fix (scarhill)
* Bluetooth, sound an performance improvements (ran)
* Freeze fixes (ran)
* Improved battery status indication (ran)
* CMUX fix (panicking)|
Screenshot=Android-on-Freerunner-Splash.png|
Codename='Android Froyo on Freerunner'|
Homepage=http://code.google.com/p/android-on-freerunner/|
Image=[http://code.google.com/p/android-on-freerunner/wiki/GetIt How to install]|
Works={{works on Android}}
}}

{{DistributionBox|
Name=QtMoko [Stable, March and April 2011]|
Description=New experimental (v34) and then stable (v35) QtMoko release:
* QX installs Xglamo as debian package
* WLAN with wpa-psk can now connect more then once (Alfa21)
* QNetWalk package has been fixed
* accelerometers in QtMaze now work
* NeronGPS moved back to old nice version
* disabled disk cache in Arora
* qtmoko bookmarks in Arora
* usb mass storage has now param removable=y for happy winxp (Alfa21)
* faenqo theme - added golden debian background (Tiago Bortoletto Vaz)
* themes now use jpg for backgrounds to save space (Tiago Bortoletto Vaz)
* docked keyboard - fix ctl and alt keys always pressed (Gennady Kupava)
* disabled login on tty1..tty6 to save memory
* qterminal - dont display unused back icon (Gennady Kupava)
* fix back icon in help browser (Gennady Kupava)
* new beautiful theme faenqomod (Joif)
* correct package dependencies in eyepiece
* qtmoko internal package manager has been disabled
* building kernel as debian package
* Fix missing icon for qtmoko apps web
* Build with translations
* Fix Xglamo install in QX
* Dont build qx_helper, it's not needed anymore
* Fixed package description for gta02-gsm-bt-fix|

Screenshot=Qtmokomain.png|
Codename='QtMoko v35'|
Homepage=http://qtmoko.org|
Image=[http://sourceforge.net/projects/qtmoko/files/]|
Works={{Works_on_QtMoko}}
}}

{{DistributionBox|
Name=Distro Name [version]|
Description=Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.|
Screenshot=System_boot.png|
Codename='codename'|
Homepage=http://www.homepage.org|
Image=[http://www.homepage.org/path/to/ images]|
Works={{Works}}
}}

==Applications==

===New Applications===

{{ApplicationBox|
Name=QtMoko-Chess|
Description=GNUChess frontend for QtMoko|
Screenshot=qtmoko-chess.png|
Homepage=http://qtmoko.sourceforge.net/apps/qtmoko-chess.html|
TestedOn=QtMoko v35|
PackageName=[http://qtmoko.sourceforge.net/apps/qtmoko-chess_35-1_armel.deb QtMoko-Chess]
}}

===Application Updates===

{{ApplicationBox|
Name=Exampleapp 0.0.1|
Description=Exampleapp 0.0.1 is an application to do some stuff...
* new example feature 1
* new example feature 2|
Screenshot=System_boot.png|
Homepage=http://wiki.openmoko.org/|
TestedOn=SHR-Unstable,Om2009T5|
PackageName=[http:// www.some.srv/path_to/Exampleapp.ipk Exampleapp]
}}

==General News==

Most important and change making mails on the mailing lists, blogs etc.. Coolest hacks, screenshots, themes etc..

==Event News==

* '''2011-05-11-14''' [http://www.linuxtag.org/2011/en/exhibitors/exhibitors-partners.html Linux Tag] | Openmoko GTA04 on LinuxTag, Hall 7.2a, Booth 115, Berlin, Germany

[[Category:Community Update]]

File:Qtmoko-chess.png

2011-04-18T08:40:09Z

Psonek:

Community Updates/2011-05-01

2011-04-18T08:39:19Z

Psonek: /* New Applications */

{{Improve}}
{{Note|
*Take a moment and look at [[Talk:Community_Updates/Draft|this page]] to get a clue on how to contribute to Community Updates while following OM wiki editing guidelines please.
*I you are planning longer edition, please use <nowiki>{{Editing|your_username_here|date_here|editing_summary_here}}tag. Remember to remove/comment out it right after you save your work.</nowiki>
*Please fill in everything you think the community should know.
*On 2011-05-01 this content should be _moved_ to http://wiki.openmoko.org/wiki/Community_Updates/YYYY-MM-DD, feel free to do it.
*Post the CU release also on the community mailing list, since some people prefer to read news directly there. Regarding this, it helps copy-pasting from browser page to mailing list post if relevant URLs are included as is in addition to having linked parts of text (if in hurry you can also just post a note that CU is readable on web page).
}}



====='''Period 2011-03-01 to 2011-04-30'''=====

== Hardware ==

* [[Freerunner RFID Board]] - new hardware mod announced
* [[Freerunner Navigation Board v3]] - new version ready

== Distributions ==

Distributions lists releases and other significant updates in distributions that have some support for the Openmoko devices.

{{DistributionBox|
Name=Android Cupcake [Stable, January 2011]|
Description=The AoF community has uploaded an update of the stable Cupcake release of AoF. This release contains:
* All fixes from Android Cupcake (Google via scarhill)
* Separate NAND or SD based installations (ran)
* Improved GPS timestamps (michael)
* Updated APN list from Cyanogenmod (scarhill)
* WMIConfig for boosting WiFi power (niels)
|
Screenshot=Android-on-Freerunner-Splash.png|
Codename='Android Cupcake on Freerunner'|
Homepage=http://code.google.com/p/android-on-freerunner/|
Image=[http://code.google.com/p/android-on-freerunner/wiki/GetIt How to install]|
Works={{works on Android}}
}}

{{DistributionBox|
Name=Android Froyo [Experimental, April 2011]|
Description=The AoF community has uploaded an update of the experimental Froyo release of AoF. This release contains:
* All fixes from Android Froyo (Google via scarhill)
* Separate NAND or SD based installations (ran)
* Improved GPS timestamps (michael)
* Updated APN list from Cyanogenmod (scarhill)
* WMIConfig for boosting WiFi power (niels)
* GPRS fix (scarhill)
* Bluetooth, sound an performance improvements (ran)
* Freeze fixes (ran)
* Improved battery status indication (ran)
* CMUX fix (panicking)|
Screenshot=Android-on-Freerunner-Splash.png|
Codename='Android Froyo on Freerunner'|
Homepage=http://code.google.com/p/android-on-freerunner/|
Image=[http://code.google.com/p/android-on-freerunner/wiki/GetIt How to install]|
Works={{works on Android}}
}}

{{DistributionBox|
Name=QtMoko [Stable, March and April 2011]|
Description=New experimental (v34) and then stable (v35) QtMoko release:
* QX installs Xglamo as debian package
* WLAN with wpa-psk can now connect more then once (Alfa21)
* QNetWalk package has been fixed
* accelerometers in QtMaze now work
* NeronGPS moved back to old nice version
* disabled disk cache in Arora
* qtmoko bookmarks in Arora
* usb mass storage has now param removable=y for happy winxp (Alfa21)
* faenqo theme - added golden debian background (Tiago Bortoletto Vaz)
* themes now use jpg for backgrounds to save space (Tiago Bortoletto Vaz)
* docked keyboard - fix ctl and alt keys always pressed (Gennady Kupava)
* disabled login on tty1..tty6 to save memory
* qterminal - dont display unused back icon (Gennady Kupava)
* fix back icon in help browser (Gennady Kupava)
* new beautiful theme faenqomod (Joif)
* correct package dependencies in eyepiece
* qtmoko internal package manager has been disabled
* building kernel as debian package
* Fix missing icon for qtmoko apps web
* Build with translations
* Fix Xglamo install in QX
* Dont build qx_helper, it's not needed anymore
* Fixed package description for gta02-gsm-bt-fix|

Screenshot=Qtmokomain.png|
Codename='QtMoko v35'|
Homepage=http://qtmoko.org|
Image=[http://sourceforge.net/projects/qtmoko/files/]|
Works={{Works_on_QtMoko}}
}}

{{DistributionBox|
Name=Distro Name [version]|
Description=Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.|
Screenshot=System_boot.png|
Codename='codename'|
Homepage=http://www.homepage.org|
Image=[http://www.homepage.org/path/to/ images]|
Works={{Works}}
}}

==Applications==

===New Applications===

{{ApplicationBox|
Name=QtMoko-Chess|
Description=GNUChess frontend for QtMoko|
Screenshot=System_boot.png|
Homepage=http://qtmoko.sourceforge.net/apps/qtmoko-chess.html|
TestedOn=QtMoko v35|
PackageName=[http://qtmoko.sourceforge.net/apps/qtmoko-chess_35-1_armel.deb QtMoko-Chess]
}}

===Application Updates===

{{ApplicationBox|
Name=Exampleapp 0.0.1|
Description=Exampleapp 0.0.1 is an application to do some stuff...
* new example feature 1
* new example feature 2|
Screenshot=System_boot.png|
Homepage=http://wiki.openmoko.org/|
TestedOn=SHR-Unstable,Om2009T5|
PackageName=[http:// www.some.srv/path_to/Exampleapp.ipk Exampleapp]
}}

==General News==

Most important and change making mails on the mailing lists, blogs etc.. Coolest hacks, screenshots, themes etc..

==Event News==

* '''2011-05-11-14''' [http://www.linuxtag.org/2011/en/exhibitors/exhibitors-partners.html Linux Tag] | Openmoko GTA04 on LinuxTag, Hall 7.2a, Booth 115, Berlin, Germany

[[Category:Community Update]]

Community Updates/2011-05-01

2011-04-15T07:33:07Z

Psonek: QtMoko v35

{{Improve}}
{{Note|
*Take a moment and look at [[Talk:Community_Updates/Draft|this page]] to get a clue on how to contribute to Community Updates while following OM wiki editing guidelines please.
*I you are planning longer edition, please use <nowiki>{{Editing|your_username_here|date_here|editing_summary_here}}tag. Remember to remove/comment out it right after you save your work.</nowiki>
*Please fill in everything you think the community should know.
*On 2011-05-01 this content should be _moved_ to http://wiki.openmoko.org/wiki/Community_Updates/YYYY-MM-DD, feel free to do it.
*Post the CU release also on the community mailing list, since some people prefer to read news directly there. Regarding this, it helps copy-pasting from browser page to mailing list post if relevant URLs are included as is in addition to having linked parts of text (if in hurry you can also just post a note that CU is readable on web page).
}}



====='''Period 2011-03-01 to 2011-04-30'''=====

== Hardware ==

* [[Freerunner RFID Board]] - new hardware mod announced
* [[Freerunner Navigation Board v3]] - new version ready

== Distributions ==

Distributions lists releases and other significant updates in distributions that have some support for the Openmoko devices.

{{DistributionBox|
Name=Android Cupcake [Stable, January 2011]|
Description=The AoF community has uploaded an update of the stable Cupcake release of AoF. This release contains:
* All fixes from Android Cupcake (Google via scarhill)
* Separate NAND or SD based installations (ran)
* Improved GPS timestamps (michael)
* Updated APN list from Cyanogenmod (scarhill)
* WMIConfig for boosting WiFi power (niels)
|
Screenshot=Android-on-Freerunner-Splash.png|
Codename='Android Cupcake on Freerunner'|
Homepage=http://code.google.com/p/android-on-freerunner/|
Image=[http://code.google.com/p/android-on-freerunner/wiki/GetIt How to install]|
Works={{works on Android}}
}}

{{DistributionBox|
Name=Android Froyo [Experimental, February 2011]|
Description=The AoF community has uploaded an update of the experimental Froyo release of AoF. This release contains:
* All fixes from Android Froyo (Google via scarhill)
* Separate NAND or SD based installations (ran)
* Improved GPS timestamps (michael)
* Updated APN list from Cyanogenmod (scarhill)
* WMIConfig for boosting WiFi power (niels)
* GPRS fix (scarhill)
* Bluetooth, sound an performance improvements (ran)

The upcomming release will contain:
* Freeze fixes when on SD (ran)
* Improved battery status indication(ran)
* CMUX fix (panicking)|
Screenshot=Android-on-Freerunner-Splash.png|
Codename='Android Froyo on Freerunner'|
Homepage=http://code.google.com/p/android-on-freerunner/|
Image=[http://code.google.com/p/android-on-freerunner/wiki/GetIt How to install]|
Works={{works on Android}}
}}

{{DistributionBox|
Name=QtMoko [Stable, March and April 2011]|
Description=New experimental (v34) and then stable (v35) QtMoko release:
* QX installs Xglamo as debian package
* WLAN with wpa-psk can now connect more then once (Alfa21)
* QNetWalk package has been fixed
* accelerometers in QtMaze now work
* NeronGPS moved back to old nice version
* disabled disk cache in Arora
* qtmoko bookmarks in Arora
* usb mass storage has now param removable=y for happy winxp (Alfa21)
* faenqo theme - added golden debian background (Tiago Bortoletto Vaz)
* themes now use jpg for backgrounds to save space (Tiago Bortoletto Vaz)
* docked keyboard - fix ctl and alt keys always pressed (Gennady Kupava)
* disabled login on tty1..tty6 to save memory
* qterminal - dont display unused back icon (Gennady Kupava)
* fix back icon in help browser (Gennady Kupava)
* new beautiful theme faenqomod (Joif)
* correct package dependencies in eyepiece
* qtmoko internal package manager has been disabled
* building kernel as debian package
* Fix missing icon for qtmoko apps web
* Build with translations
* Fix Xglamo install in QX
* Dont build qx_helper, it's not needed anymore
* Fixed package description for gta02-gsm-bt-fix|

Screenshot=Qtmokomain.png|
Codename='QtMoko v35'|
Homepage=http://qtmoko.org|
Image=[http://sourceforge.net/projects/qtmoko/files/]|
Works={{Works_on_QtMoko}}
}}

{{DistributionBox|
Name=Distro Name [version]|
Description=Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.Here comes some additional text to show you guys, how Template:DistributionBox will behave under heavy load of text. It is copied several times on purpose. This way you can see how layout would looke like if description of distribution is very complex or expanded.|
Screenshot=System_boot.png|
Codename='codename'|
Homepage=http://www.homepage.org|
Image=[http://www.homepage.org/path/to/ images]|
Works={{Works}}
}}

==Applications==

===New Applications===

{{ApplicationBox|
Name=Exampleapp 0.0.1|
Description=Exampleapp 0.0.1 is an application to do some stuff..|
Screenshot=System_boot.png|
Homepage=http://wiki.openmoko.org/|
TestedOn=SHR-Unstable,Om2009T5|
PackageName=[http:// www.some.srv/path_to/Exampleapp.ipk Exampleapp]
}}

===Application Updates===

{{ApplicationBox|
Name=Exampleapp 0.0.1|
Description=Exampleapp 0.0.1 is an application to do some stuff...
* new example feature 1
* new example feature 2|
Screenshot=System_boot.png|
Homepage=http://wiki.openmoko.org/|
TestedOn=SHR-Unstable,Om2009T5|
PackageName=[http:// www.some.srv/path_to/Exampleapp.ipk Exampleapp]
}}

==General News==

Most important and change making mails on the mailing lists, blogs etc.. Coolest hacks, screenshots, themes etc..

==Event News==

* '''2011-05-11-14''' [http://www.linuxtag.org/2011/en/exhibitors/exhibitors-partners.html Linux Tag] | Openmoko GTA04 on LinuxTag, Berlin, Germany

[[Category:Community Update]]

List of bluetooth headsets

2011-01-16T22:49:58Z

Psonek: Added motorola H5000

{{todo|All headsets listed on this page need additional testings. Please add your impressions/suggestions}}
{{Improve}}

List of all headsets known to work fully or partially, or don't work at all.

=Mono headsets=

Note: Please report using headset buttons to pick/release call.

{| border="1" cellspacing=0 cellpadding=4
!Model
!Person
!Link to official website
!Price
!GSM Call
!Controls
!Remark
|-
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|-
|no-name "Jabra"
|PaulFertser
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|discovered as "Bluetooth headset"
|-
|"Jabra BT 125"
|chaitanya chandel
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|Connect/Vol
|also responds to IndicateCall
|-
|Plantronics Voyager 855
|DigitalPioneer
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|
|-
|Plantronics Explorer 220
|Vendion
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|
|-
|BT Headset-12
|Vanous
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|no-name
|-
|Insmat (HS200?)
|Rakshasa
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|a real cheap one
|-
|qstarz BT-Q360
|Martin JaMa Jansa
|[http://www.qstarz.com/Products/Bluetooth%20Products/BH-Q360.html www.qstarz.com]
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|
|-
|Iqua BHS-333
|PaulFertser
|{{Unknown}}
|{{Unknown}}
|{{No}}
|{{Unknown}}
|it turns on/off, beeps etc properly, but gives no sound
|-
|Nokia BH-200
|Vanous
|{{Unknown}}
|{{Unknown}}
|{{No}}
|{{Unknown}}
|same as above :(
|-
|Nokia BH-203
|Lindi
|{{Unknown}}
|{{Unknown}}
|{{No}}
|{{Unknown}}
|same as above :( Works with one USB-BT dongle, does not work with another USB-BT dongle and does not work with the builtin USB-BT dongle of openmoko
|-
|Plantronics model 330
|Jim Morris
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Yes}}
| Must connect as headset profile and not handsfree for buttons to work
|}

=Stereo headsets=

Note: None of the below headsets have been tested with GSM calls unless that is explicitly mentioned.

Note: To test play controls (AVRCP) please test with [[Intone]]. For now (31-07-2009) it's only known player to support AVRCP. [[User:Any Key|Any Key]]

{| border="1" cellspacing=0 cellpadding=4
!Model
!Person
!Link to official website
!Price
!A2DP
!GSM Call
!play controls (AVRCP)
!Remark
|-
|B-Speech Calypso
|DJDAS
|[http://www.b-speech.de/en/produkt-information/stereo-headsets-und-adapter/b-speech_calypso/ B-Speech.de]
|{{Unknown}}
|{{Yes}}
|{{Yes}}
|{{Unknown}}
|both A2DP and Headset, tested in FDOM
|-
|BCK-08
|Zorkman
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
| tested on shr unstable from 09 feb) ; very cheap on e-bay (A2DP Stereo Bluetooth Headphone Headset) -ONLY TESTED WITH MUSIC PLAYBACK, NOT GSM CALL-
|-
|Jabra BT620s
|radekp
|[http://www.jabra.com/Sites/Jabra/NA-US/Headsets/Pages/Jabrabt620s.aspx www.jabra.com]
|32-60 EUR
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|Tested on SHR with bluez4 and QtMoko bluez3; A2DP works correctly, GSM calls untested.
|-
|Jabra BT650s
|radekp
|[http://www.jabra.com/Sites/Jabra/ee-Uk/Headsets/Pages/Jabrahalo.aspx www.jabra.com]
|80 EUR
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|Tested on QtMoko bluez3; A2DP works correctly, GSM calls untested.
|-
|Jabra BT3030
|Elleo
|[http://www.jabra.com/Sites/Jabra/na-us/Headsets/Pages/JabraBT3030.aspx www.jabra.com]
|{{Unknown}}
|{{Yes}}
|{{Yes}}
|{{Unknown}}
|Tested on SHR with bluez3 and bluez4.
|-
|Jabra BT8010
|Montgoss
|[http://www.jabra.com/Sites/Jabra/ee-uk/Headsets/Pages/JabraBT8010.aspx jabra.com]
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Yes}}
|Tested on SHR-Unstable 20090708. A2DP works correctly, GSM calls untested.
|-
|Lubix UBHS-NC1
|Dan Staley
|[http://www.lubixmobile.com/content.php?mode=view&c_idx=c0005&c_type=06&str_block=l001 lubixmobile.com]
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Yes}}
|Stero Music via mplayer or Intone works great. All buttons work. I havent tried GSM calls yet. (Tested on SHR-U)
|-
|Motorola HT820
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|headset (need to restart bluetoothd to get headset working after pairing) tested in SHR testing (and unstable) with bluez4 and kernel 2.6.29
|-
|Motorola S9-HD
|BillK
|[http://www.motorola.com/staticfiles/Consumers/global/flash_content/microsites/s9hd/index.html motorola.com]
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|SHR-unstable - A2DP works fine(mplayer/intone), gsm may work but have NOT tried it. Good for active use (walking/running/bike etc) - but sound may not be highest quality.
|-
|Nokia BH-103
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|tested in Om 2008.12
|-
|Nokia BH-214
|c-punk-t
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|SHR-testing-20100309
|-
|Nokia BH-505
|TimoJyrinki
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|Debian testing. Paired with gnome-bluetooth, music played with intone.
|-
|Nokia BH-604
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|DJ-style headphones, tested in FDOM and FSO milestone 5
|-
|Nokia CK-15W
|pb0
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|Car bluetooth, tested with SHR-unstable

|-
|Plantronics 320
|shoragan (#openmoko)
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|tested to work with GSM calls according to shoragan on #openmoko.
|-
|Plantronics P590
|mita_ore (SkypeID)
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|-
|Plantronics Voyager 855
|The Digital Pioneer
|[http://www.plantronics.com/north_america/en_US/products/mobile/bluetooth-headsets/voyager-855 plantronics.com]
|$30-$60 on Newegg
|{{Yes}}
|{{Yes}}
|{{Yes}}
|Stereo for music, mono for calls. Other person reported: stereo bluetooth tested in SHR-Unstable with bluez4 and kernel 2.6.29 -- A2DP/mplayer works perfectly. Works with GSM calls and AVRCP (media player buttons)
|-
|Sennheiser MM200
|CyrusDreams
|[http://www.sennheiser.com/sennheiser/home_en.nsf/root/private_headsets_mobile_music_502411?Open&row=3 sennheiser.com]
|90-160EUR
|{{yes}}
|{{Unknown}}
|{{yes}}
|Manually configured, SHR-unstable, bluez4. A2DP/mplayer works, Intone works with controls. GSM untested.
|-
|Sony Ericsson HBH-DS200
|Valos
|[http://www.sonyericsson.com/cws/products/accessories/overview/hbh-ds200?lc=en&cc=gb sonyericsson.com]
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|tested in SHR-Unstable with bluez4 and kernel 2.6.29 -- A2DP/mplayer works
perfectly; GSM calls not tested yet
|-
|Sony HBH-DS970
|KaZeR
|[http://www.sonyericsson.com/cws/products/accessories/overview/hbh-ds970?lc=en&cc=gb sonyericsson.com]
|{{Unknown}}
|{{Yes}}
|{{Yes}}
|{{Yes}}
|Intone works, with buttons. Calls untested yet
|-
|Venturi Mini
|KaZeR
|[http://www.myventuri.com/home.aspx MyVenturi]
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|Intone works, calls and phonebook sync not tested yet.
|-
|Iqua BHS-701
|Yogiz
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Yes}}
|Just tried A2DP for now. Works perfectly, volume controls, track changing, everything. Will try gsm calls later. Used SHR unstable.
|}

=Audio systems=

{| border="1" cellspacing=0 cellpadding=4
!Model
!Person
!Link to official website
!Price
!A2DP
!GSM Call
!play controls (AVRCP)
!Remark
|-
|Gear4 Blackbox
|mita_ore (SkypeID)
|[http://www.gear4.com Gear4]
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|
|}

=Handsfree Devices=

{| border="1" cellspacing=0 cellpadding=4
!Model
!Person
!Link to official website
!Price
!GSM Call
!Controls
!Caller ID
!Distro
!Remark
|-
|Motorola T505
|Jim Morris
|[http://direct.motorola.com/hellomoto/t505 Motorola]
|$56 US
|{{Yes}}
|{{No}}
|{{No}}
| qtmoko
|Connect as Handsfree, call button does hangup and answer calls, but sporadically, connect as headset doesn't work well at all
|-
|VR3 VRBT200V
|Jim Morris
|{{Unknown}}
|Cheap
|{{Yes}}
|{{Yes}}
|{{Yes}}
| qtmoko
|Connect as Handsfree profile, gets incoming number and accepts call on button press and hangsup on button press.
|-
|Motorola H500
|Radek Polak
|{{Unknown}}
|Cheap
|{{Yes}}
|{{Yes}}
|{{Unknown}}
| qtmoko v32 (based on squeeze and bluez4)
|Connect as Handsfree profile, gets incoming number and accepts call on button press and hangsup on button press.
|}

[[Category:Headsets]]
[[Category:Bluetooth]]

Template:Works on QtMoko

2010-06-02T11:30:55Z

Psonek: Updated QtMoko working on Neo1973

{{Works|
Neo1973={{yes}}|
FreeRunner={{yes}}|
HTC-Dream={{unknown}}|
Other={{unknown}}
}}

<noinclude>
Here sits the hidden <nowiki>[[Category:Templates]]</nowiki> link: "[[Category:Templates]]"
</noinclude>

GSM oscillating between registered and not registered aka 1024

2010-05-18T21:21:17Z

Psonek: better word

This page describes how to enable Calypso GSM modem deep sleep after performing a hardware fix of bug [http://docs.openmoko.org/trac/ticket/1024 #1024] aka recamping or oscillating of the Calypso GSM modem used in Openmoko [[Neo Freerunner]].

==Description==
Hardware bug #1024 creates a condition when the gsm modem is oscillating between registrated / not-registrated. This causes the phone to be unavailable at times. Distribution maintainers have been able to use a software setting to disable suspend of the gsm modem in order to work around this bug. The downside is that with this workaround the modem never sleeps and consumer more energy then needed.

If you decide to undergo a hardware fix of your phone you have to reconfigure your distribution to allow the gsm modem to go to sleep again in order to actually make use of the modem sleep function and therefore extend your battery life.

Bug trac: http://docs.openmoko.org/trac/ticket/1024

==Bug detection==
Not every Freerunner suffers this issue. To check if your phone has the bug #1024 please use this test script:

(This script will only work on FSO based distro. Also, this script is not 100% perfect, another way is to use frameworkd with ti_calypso_sleep_mode = 'adaptive' and inspect the logs. Frameworkd will tell you, when a real recamping exists)

<pre>
#!/usr/bin/python

import dbus
import dbus.glib
import gobject
import datetime

def onNetworkStatus(status):
if 'cid' in status:
print '[%s] Signal : cid=%s, lac=%s' % (datetime.datetime.now(),status['cid'],status['lac'] )
else:
print 'register first'

bus = dbus.SystemBus();

bus.add_signal_receiver(onNetworkStatus,
"Status",
"org.freesmartphone.GSM.Network",
"org.freesmartphone.ogsmd",
"/org/freesmartphone/GSM/Device")

gobject.threads_init()
dbus.glib.init_threads()
main_loop = gobject.MainLoop()
main_loop.run()
</pre>

Run it like this:

root@om-gta02 ~ $ deep-sleep-check.py > dsc.log

If you have something like this:

[2009-09-09 12:36:09.189663] Signal : cid=3BB3, lac=0D48
[2009-09-09 12:36:15.088936] Signal : cid=3BB3, lac=0D48
[2009-09-09 12:38:10.442808] Signal : cid=3BB3, lac=0D48
[2009-09-09 12:38:13.020126] Signal : cid=3BB3, lac=0D48
[2009-09-09 12:40:25.772918] Signal : cid=3BB3, lac=0D48
[2009-09-09 12:40:28.620096] Signal : cid=3BB3, lac=0D48
[2009-09-09 12:41:17.557676] Signal : cid=3BB3, lac=0D48
[2009-09-09 12:41:20.404582] Signal : cid=3BB3, lac=0D48

Then you have the bug (trying to connect to GSM every second). Please note that cid is always the same.

Correct output might not show any messages or look like this:

[2009-10-18 07:51:27.107655] Signal : cid=4E91, lac=006A
[2009-10-18 07:52:45.145288] Signal : cid=4E7B, lac=006A
[2009-10-18 07:53:18.218122] Signal : cid=4E91, lac=006A

You can see the cid changing.

==Bug detection by fso==
Just use frameworkd with ti_calypso_sleep_mode = 'adaptive' and inspect
the logs. Frameworkd will tell you, when a real recamping exists.

==Hardware bug fixing==
To perform the hardware update, please check description here:
http://lists.openmoko.org/pipermail/hardware/2009-May/001192.html
http://www.neofundas.blogspot.com/

[[Image:1024fix.jpg]]

After the fix, please recheck again with the script as above. Under normal circumstances you would only see these messages with a change of cell, so cid would be different.

If your fix was successful you can change setting to allow Calypso deep sleep:

==Enabling/allowing Calypso GSM modem deep sleep==
===FSO2 based distros (SHR, Debian)===

Edit /etc/freesmartphone/conf/GTA02/fsogsmd.conf

deep_sleep == "always"

Then kill fsogsmd and restart fsodeviced or reboot the phone.

===FSO based distros (SHR, Debian, OM2009...)===

Edit /etc/frameworkd.conf , it should contain:

ti_calypso_deep_sleep = always

Then restart framework or reboot the phone.

/etc/init.d/frameworkd restart

===QT based distos (Qtopia, QTExtended, QTMoko...)===
Since qtmoko v24 you can use program called NeoControl which is installed by default.

Or you can edit /opt/qtmoko/etc/default/Trolltech/Modem.conf , it should contain:

[DeepSleep]
Active=always

Make sure it's also in users directory:

cp /opt/qtmoko/etc/default/Trolltech/Modem.conf /home/root/Settings/Trolltech/Modem.conf

And reboot.

===Hackable:1 (rev.5)===

As said in http://lists.hackable1.org/pipermail/hackable1-user/2010-January/000718.html and other discussions:
hackable:1 does not use frameworkd but gsmd.

To enable deep-sleep mode:

-download and install (or extract)
http://build.hackable1.org/debian/dists/wip/main/binary-armel/gsmd_0.0.2+svn1571-1_armel.deb
-edit /etc/default/gsmd and uncomment the "VENDOR=ti-deepsleep" line: this will add a
"-v ti-deepsleep" to the deamon command line.
-Restart gsmd.

===Android===

Currently Android on Freerunner is hard coded to use AT%SLEEP=2 to avoid deep sleep mode entirely; there is a discussion about providing editable property in Androids init.rc startup file.

==See also==
*[[GSM oscillating between registered and not registered]]
*Golden Delicious Computers offers to handle the rework or provides devices (GTA02A7+) which already have this rework applied: http://lists.openmoko.org/pipermail/community/2010-April/061171.html

[[Category:Neo FreeRunner reworks and mods]]

GSM oscillating between registered and not registered aka 1024

2010-05-18T21:16:58Z

Psonek: QtMoko - using GUI and also make sure it's in user settings

This page describes how to enable Calypso GSM modem deep sleep after performing a hardware fix of bug [http://docs.openmoko.org/trac/ticket/1024 #1024] aka recamping or oscillating of the Calypso GSM modem used in Openmoko [[Neo Freerunner]].

==Description==
Hardware bug #1024 creates a condition when the gsm modem is oscillating between registrated / not-registrated. This causes the phone to be unavailable at times. Distribution maintainers have been able to use a software setting to disable suspend of the gsm modem in order to work around this bug. The downside is that with this workaround the modem never sleeps and consumer more energy then needed.

If you decide to undergo a hardware fix of your phone you have to reconfigure your distribution to allow the gsm modem to go to sleep again in order to actually make use of the modem sleep function and therefore extend your battery life.

Bug trac: http://docs.openmoko.org/trac/ticket/1024

==Bug detection==
Not every Freerunner suffers this issue. To check if your phone has the bug #1024 please use this test script:

(This script will only work on FSO based distro. Also, this script is not 100% perfect, another way is to use frameworkd with ti_calypso_sleep_mode = 'adaptive' and inspect the logs. Frameworkd will tell you, when a real recamping exists)

<pre>
#!/usr/bin/python

import dbus
import dbus.glib
import gobject
import datetime

def onNetworkStatus(status):
if 'cid' in status:
print '[%s] Signal : cid=%s, lac=%s' % (datetime.datetime.now(),status['cid'],status['lac'] )
else:
print 'register first'

bus = dbus.SystemBus();

bus.add_signal_receiver(onNetworkStatus,
"Status",
"org.freesmartphone.GSM.Network",
"org.freesmartphone.ogsmd",
"/org/freesmartphone/GSM/Device")

gobject.threads_init()
dbus.glib.init_threads()
main_loop = gobject.MainLoop()
main_loop.run()
</pre>

Run it like this:

root@om-gta02 ~ $ deep-sleep-check.py > dsc.log

If you have something like this:

[2009-09-09 12:36:09.189663] Signal : cid=3BB3, lac=0D48
[2009-09-09 12:36:15.088936] Signal : cid=3BB3, lac=0D48
[2009-09-09 12:38:10.442808] Signal : cid=3BB3, lac=0D48
[2009-09-09 12:38:13.020126] Signal : cid=3BB3, lac=0D48
[2009-09-09 12:40:25.772918] Signal : cid=3BB3, lac=0D48
[2009-09-09 12:40:28.620096] Signal : cid=3BB3, lac=0D48
[2009-09-09 12:41:17.557676] Signal : cid=3BB3, lac=0D48
[2009-09-09 12:41:20.404582] Signal : cid=3BB3, lac=0D48

Then you have the bug (trying to connect to GSM every second). Please note that cid is always the same.

Correct output might not show any messages or look like this:

[2009-10-18 07:51:27.107655] Signal : cid=4E91, lac=006A
[2009-10-18 07:52:45.145288] Signal : cid=4E7B, lac=006A
[2009-10-18 07:53:18.218122] Signal : cid=4E91, lac=006A

You can see the cid changing.

==Bug detection by fso==
Just use frameworkd with ti_calypso_sleep_mode = 'adaptive' and inspect
the logs. Frameworkd will tell you, when a real recamping exists.

==Hardware bug fixing==
To perform the hardware update, please check description here:
http://lists.openmoko.org/pipermail/hardware/2009-May/001192.html
http://www.neofundas.blogspot.com/

[[Image:1024fix.jpg]]

After the fix, please recheck again with the script as above. Under normal circumstances you would only see these messages with a change of cell, so cid would be different.

If your fix was successful you can change setting to allow Calypso deep sleep:

==Enabling/allowing Calypso GSM modem deep sleep==
===FSO2 based distros (SHR, Debian)===

Edit /etc/freesmartphone/conf/GTA02/fsogsmd.conf

deep_sleep == "always"

Then kill fsogsmd and restart fsodeviced or reboot the phone.

===FSO based distros (SHR, Debian, OM2009...)===

Edit /etc/frameworkd.conf , it should contain:

ti_calypso_deep_sleep = always

Then restart framework or reboot the phone.

/etc/init.d/frameworkd restart

===QT based distos (Qtopia, QTExtended, QTMoko...)===

From qtmoko v24 you can use program called NeoControl which is installed by default.

Or you can edit /opt/qtmoko/etc/default/Trolltech/Modem.conf , it should contain:

[DeepSleep]
Active=always

Make sure it's also in users directory:

cp /opt/qtmoko/etc/default/Trolltech/Modem.conf /home/root/Settings/Trolltech/Modem.conf

And reboot.

===Hackable:1 (rev.5)===

As said in http://lists.hackable1.org/pipermail/hackable1-user/2010-January/000718.html and other discussions:
hackable:1 does not use frameworkd but gsmd.

To enable deep-sleep mode:

-download and install (or extract)
http://build.hackable1.org/debian/dists/wip/main/binary-armel/gsmd_0.0.2+svn1571-1_armel.deb
-edit /etc/default/gsmd and uncomment the "VENDOR=ti-deepsleep" line: this will add a
"-v ti-deepsleep" to the deamon command line.
-Restart gsmd.

===Android===

Currently Android on Freerunner is hard coded to use AT%SLEEP=2 to avoid deep sleep mode entirely; there is a discussion about providing editable property in Androids init.rc startup file.

==See also==
*[[GSM oscillating between registered and not registered]]
*Golden Delicious Computers offers to handle the rework or provides devices (GTA02A7+) which already have this rework applied: http://lists.openmoko.org/pipermail/community/2010-April/061171.html

[[Category:Neo FreeRunner reworks and mods]]

List of bluetooth headsets

2010-03-24T18:28:49Z

Psonek: Jabra halo

{{todo|All headsets listed on this page need additional testings. Please add your impressions/suggestions}}
{{Improve}}

List of all headsets known to work fully or partially, or don't work at all.

=Mono headsets=

Note: Please report using headset buttons to pick/release call.

{| border="1" cellspacing=0 cellpadding=4
!Model
!Person
!Link to official website
!Price
!GSM Call
!Controls
!Remark
|-
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|-
|no-name "Jabra"
|PaulFertser
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|discovered as "Bluetooth headset"
|-
|"Jabra BT 125"
|chaitanya chandel
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|Connect/Vol
|also responds to IndicateCall
|-
|Plantronics Voyager 855
|DigitalPioneer
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|
|-
|Plantronics Explorer 220
|Vendion
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|
|-
|BT Headset-12
|Vanous
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|no-name
|-
|Insmat (HS200?)
|Rakshasa
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|a real cheap one
|-
|qstarz BT-Q360
|Martin JaMa Jansa
|[http://www.qstarz.com/Products/Bluetooth%20Products/BH-Q360.html www.qstarz.com]
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|
|-
|Iqua BHS-333
|PaulFertser
|{{Unknown}}
|{{Unknown}}
|{{No}}
|{{Unknown}}
|it turns on/off, beeps etc properly, but gives no sound
|-
|Nokia BH-200
|Vanous
|{{Unknown}}
|{{Unknown}}
|{{No}}
|{{Unknown}}
|same as above :(
|-
|Nokia BH-203
|Lindi
|{{Unknown}}
|{{Unknown}}
|{{No}}
|{{Unknown}}
|same as above :( Works with one USB-BT dongle, does not work with another USB-BT dongle and does not work with the builtin USB-BT dongle of openmoko
|}

=Stereo headsets=

Note: None of the below headsets have been tested with GSM calls unless that is explicitly mentioned.

Note: To test play controls (AVRCP) please test with [[Intone]]. For now (31-07-2009) it's only known player to support AVRCP. [[User:Any Key|Any Key]]

{| border="1" cellspacing=0 cellpadding=4
!Model
!Person
!Link to official website
!Price
!A2DP
!GSM Call
!play controls (AVRCP)
!Remark
|-
|B-Speech Calypso
|DJDAS
|[http://www.b-speech.de/en/produkt-information/stereo-headsets-und-adapter/b-speech_calypso/ B-Speech.de]
|{{Unknown}}
|{{Yes}}
|{{Yes}}
|{{Unknown}}
|both A2DP and Headset, tested in FDOM
|-
|BCK-08
|Zorkman
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
| tested on shr unstable from 09 feb) ; very cheap on e-bay (A2DP Stereo Bluetooth Headphone Headset) -ONLY TESTED WITH MUSIC PLAYBACK, NOT GSM CALL-
|-
|Jabra BT620s
|radekp
|[http://www.jabra.com/Sites/Jabra/NA-US/Headsets/Pages/Jabrabt620s.aspx www.jabra.com]
|32-60 EUR
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|Tested on SHR with bluez4 and QtMoko bluez3; A2DP works correctly, GSM calls untested.
|-
|Jabra BT650s
|radekp
|[http://www.jabra.com/Sites/Jabra/ee-Uk/Headsets/Pages/Jabrahalo.aspx www.jabra.com]
|80 EUR
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|Tested on QtMoko bluez3; A2DP works correctly, GSM calls untested.
|-
|Jabra BT3030
|Elleo
|[http://www.jabra.com/Sites/Jabra/na-us/Headsets/Pages/JabraBT3030.aspx www.jabra.com]
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|Tested on SHR with bluez3 and bluez4; A2DP works correctly, GSM calls untested.
|-
|Jabra BT8010
|Montgoss
|[http://www.jabra.com/Sites/Jabra/ee-uk/Headsets/Pages/JabraBT8010.aspx jabra.com]
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Yes}}
|Tested on SHR-Unstable 20090708. A2DP works correctly, GSM calls untested.
|-
|Lubix UBHS-NC1
|Dan Staley
|[http://www.lubixmobile.com/content.php?mode=view&c_idx=c0005&c_type=06&str_block=l001 lubixmobile.com]
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Yes}}
|Stero Music via mplayer or Intone works great. All buttons work. I havent tried GSM calls yet. (Tested on SHR-U)
|-
|Motorola HT820
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|headset (need to restart bluetoothd to get headset working after pairing) tested in SHR testing (and unstable) with bluez4 and kernel 2.6.29
|-
|Motorola S9-HD
|BillK
|[http://www.motorola.com/staticfiles/Consumers/global/flash_content/microsites/s9hd/index.html motorola.com]
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|SHR-unstable - A2DP works fine(mplayer/intone), gsm may work but have NOT tried it. Good for active use (walking/running/bike etc) - but sound may not be highest quality.
|-
|Nokia BH-103
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|tested in Om 2008.12
|-
|Nokia BH-214
|c-punk-t
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|SHR-testing-20100309
|-
|Nokia BH-604
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|DJ-style headphones, tested in FDOM and FSO milestone 5
|-
|Nokia CK-15W
|pb0
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|Car bluetooth, tested with SHR-unstable

|-
|Plantronics 320
|shoragan (#openmoko)
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|tested to work with GSM calls according to shoragan on #openmoko.
|-
|Plantronics P590
|mita_ore (SkypeID)
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|-
|Plantronics Voyager 855
|The Digital Pioneer
|[http://www.plantronics.com/north_america/en_US/products/mobile/bluetooth-headsets/voyager-855 plantronics.com]
|$30-$60 on Newegg
|{{Yes}}
|{{Yes}}
|{{Yes}}
|Stereo for music, mono for calls. Other person reported: stereo bluetooth tested in SHR-Unstable with bluez4 and kernel 2.6.29 -- A2DP/mplayer works perfectly. Works with GSM calls and AVRCP (media player buttons)
|-
|Sennheiser MM200
|CyrusDreams
|[http://www.sennheiser.com/sennheiser/home_en.nsf/root/private_headsets_mobile_music_502411?Open&row=3 sennheiser.com]
|90-160EUR
|{{yes}}
|{{Unknown}}
|{{yes}}
|Manually configured, SHR-unstable, bluez4. A2DP/mplayer works, Intone works with controls. GSM untested.
|-
|Sony Ericsson HBH-DS200
|Valos
|[http://www.sonyericsson.com/cws/products/accessories/overview/hbh-ds200?lc=en&cc=gb sonyericsson.com]
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|tested in SHR-Unstable with bluez4 and kernel 2.6.29 -- A2DP/mplayer works
perfectly; GSM calls not tested yet
|-
|Sony HBH-DS970
|KaZeR
|[http://www.sonyericsson.com/cws/products/accessories/overview/hbh-ds970?lc=en&cc=gb sonyericsson.com]
|{{Unknown}}
|{{Yes}}
|{{Yes}}
|{{Yes}}
|Intone works, with buttons. Calls untested yet
|-
|Venturi Mini
|KaZeR
|[http://www.myventuri.com/home.aspx MyVenturi]
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|Intone works, calls and phonebook sync not tested yet.
|-
|Iqua BHS-701
|Yogiz
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Yes}}
|Just tried A2DP for now. Works perfectly, volume controls, track changing, everything. Will try gsm calls later. Used SHR unstable.
|}

=Audio systems=

{| border="1" cellspacing=0 cellpadding=4
!Model
!Person
!Link to official website
!Price
!A2DP
!GSM Call
!play controls (AVRCP)
!Remark
|-
|Gear4 Blackbox
|mita_ore (SkypeID)
|[http://www.gear4.com Gear4]
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|
|}

[[Category:Headsets]]
[[Category:Bluetooth]]

List of bluetooth headsets

2010-03-04T08:50:53Z

Psonek: Jabra BT620s

{{todo|All headsets listed on this page need additional testings. Please add your impressions/suggestions}}
{{Improve}}

List of all headsets known to work fully or partially, or don't work at all.

=Mono headsets=

Note: Please report using headset buttons to pick/release call.

{| border="1" cellspacing=0 cellpadding=4
!Model
!Person
!Link to official website
!Price
!GSM Call
!Controls
!Remark
|-
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|-
|no-name "Jabra"
|PaulFertser
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|discovered as "Bluetooth headset"
|-
|"Jabra BT 125"
|chaitanya chandel
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|Connect/Vol
|also responds to IndicateCall
|-
|Plantronics Voyager 855
|DigitalPioneer
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|
|-
|Plantronics Explorer 220
|Vendion
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|
|-
|BT Headset-12
|Vanous
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|no-name
|-
|Insmat (HS200?)
|Rakshasa
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|a real cheap one
|-
|qstarz BT-Q360
|Martin JaMa Jansa
|[http://www.qstarz.com/Products/Bluetooth%20Products/BH-Q360.html www.qstarz.com]
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|
|-
|Iqua BHS-333
|PaulFertser
|{{Unknown}}
|{{Unknown}}
|{{No}}
|{{Unknown}}
|it turns on/off, beeps etc properly, but gives no sound
|-
|Nokia BH-200
|Vanous
|{{Unknown}}
|{{Unknown}}
|{{No}}
|{{Unknown}}
|same as above :(
|-
|Nokia BH-203
|Lindi
|{{Unknown}}
|{{Unknown}}
|{{No}}
|{{Unknown}}
|same as above :( Works with one USB-BT dongle, does not work with another USB-BT dongle and does not work with the builtin USB-BT dongle of openmoko
|}

=Stereo headsets=

Note: None of the below headsets have been tested with GSM calls unless that is explicitly mentioned.

Note: To test play controls (AVRCP) please test with [[Intone]]. For now (31-07-2009) it's only known player to support AVRCP. [[User:Any Key|Any Key]]

{| border="1" cellspacing=0 cellpadding=4
!Model
!Person
!Link to official website
!Price
!A2DP
!GSM Call
!play controls (AVRCP)
!Remark
|-
|B-Speech Calypso
|DJDAS
|[http://www.b-speech.de/en/produkt-information/stereo-headsets-und-adapter/b-speech_calypso/ B-Speech.de]
|{{Unknown}}
|{{Yes}}
|{{Yes}}
|{{Unknown}}
|both A2DP and Headset, tested in FDOM
|-
|BCK-08
|Zorkman
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
| tested on shr unstable from 09 feb) ; very cheap on e-bay (A2DP Stereo Bluetooth Headphone Headset) -ONLY TESTED WITH MUSIC PLAYBACK, NOT GSM CALL-
|-
|Jabra BT620s
|radekp
|[http://www.jabra.com/Sites/Jabra/NA-US/Headsets/Pages/Jabrabt620s.aspx www.jabra.com]
|32-60 EUR
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|Tested on SHR with bluez4 and QtMoko bluez3; A2DP works correctly, GSM calls untested.
|-
|Jabra BT3030
|Elleo
|[http://www.jabra.com/Sites/Jabra/na-us/Headsets/Pages/JabraBT3030.aspx www.jabra.com]
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|Tested on SHR with bluez3 and bluez4; A2DP works correctly, GSM calls untested.
|-
|Jabra BT8010
|Montgoss
|[http://www.jabra.com/Sites/Jabra/ee-uk/Headsets/Pages/JabraBT8010.aspx jabra.com]
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Yes}}
|Tested on SHR-Unstable 20090708. A2DP works correctly, GSM calls untested.
|-
|Lubix UBHS-NC1
|Dan Staley
|[http://www.lubixmobile.com/content.php?mode=view&c_idx=c0005&c_type=06&str_block=l001 lubixmobile.com]
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Yes}}
|Stero Music via mplayer or Intone works great. All buttons work. I havent tried GSM calls yet. (Tested on SHR-U)
|-
|Motorola HT820
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|headset (need to restart bluetoothd to get headset working after pairing) tested in SHR testing (and unstable) with bluez4 and kernel 2.6.29
|-
|Motorola S9-HD
|BillK
|[http://www.motorola.com/staticfiles/Consumers/global/flash_content/microsites/s9hd/index.html motorola.com]
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|SHR-unstable - A2DP works fine(mplayer/intone), gsm may work but have NOT tried it. Good for active use (walking/running/bike etc) - but sound may not be highest quality.
|-
|Nokia BH-103
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|tested in Om 2008.12
|-
|Nokia BH-604
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|DJ-style headphones, tested in FDOM and FSO milestone 5
|-
|Nokia CK-15W
|pb0
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|Car bluetooth, tested with SHR-unstable

|-
|Plantronics 320
|shoragan (#openmoko)
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|tested to work with GSM calls according to shoragan on #openmoko.
|-
|Plantronics P590
|mita_ore (SkypeID)
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|{{Unknown}}
|-
|Plantronics Voyager 855
|The Digital Pioneer
|[http://www.plantronics.com/north_america/en_US/products/mobile/bluetooth-headsets/voyager-855 plantronics.com]
|$30-$60 on Newegg
|{{Yes}}
|{{Yes}}
|{{Yes}}
|Stereo for music, mono for calls. Other person reported: stereo bluetooth tested in SHR-Unstable with bluez4 and kernel 2.6.29 -- A2DP/mplayer works perfectly. Works with GSM calls and AVRCP (media player buttons)
|-
|Sennheiser MM200
|CyrusDreams
|[http://www.sennheiser.com/sennheiser/home_en.nsf/root/private_headsets_mobile_music_502411?Open&row=3 sennheiser.com]
|90-160EUR
|{{yes}}
|{{Unknown}}
|{{yes}}
|Manually configured, SHR-unstable, bluez4. A2DP/mplayer works, Intone works with controls. GSM untested.
|-
|Sony Ericsson HBH-DS200
|Valos
|[http://www.sonyericsson.com/cws/products/accessories/overview/hbh-ds200?lc=en&cc=gb sonyericsson.com]
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|tested in SHR-Unstable with bluez4 and kernel 2.6.29 -- A2DP/mplayer works
perfectly; GSM calls not tested yet
|-
|Sony HBH-DS970
|KaZeR
|[http://www.sonyericsson.com/cws/products/accessories/overview/hbh-ds970?lc=en&cc=gb sonyericsson.com]
|{{Unknown}}
|{{Yes}}
|{{Yes}}
|{{Yes}}
|Intone works, with buttons. Calls untested yet
|-
|Venturi Mini
|KaZeR
|[http://www.myventuri.com/home.aspx MyVenturi]
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|Intone works, calls and phonebook sync not tested yet.
|-
|Iqua BHS-701
|Yogiz
|{{Unknown}}
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Yes}}
|Just tried A2DP for now. Works perfectly, volume controls, track changing, everything. Will try gsm calls later. Used SHR unstable.
|}

=Audio systems=

{| border="1" cellspacing=0 cellpadding=4
!Model
!Person
!Link to official website
!Price
!A2DP
!GSM Call
!play controls (AVRCP)
!Remark
|-
|Gear4 Blackbox
|mita_ore (SkypeID)
|[http://www.gear4.com Gear4]
|{{Unknown}}
|{{Yes}}
|{{Unknown}}
|{{Unknown}}
|
|}

[[Category:Headsets]]
[[Category:Bluetooth]]

A2DP

2010-03-02T23:00:58Z

Psonek: Describe error for missing libasound-module-bluez

The [http://en.wikipedia.org/wiki/A2DP A2DP] bluetooth profile allows high quality audio to be transferred from the phone.

This page describes how to setup A2DP on the Freerunner.

== How to setup A2DP manually ==
This information is mostly taken from [http://lists.openmoko.org/nabble.html#nabble-td2176481 this mail thread]. It has been tested on [[FDOM]] and [[FSO]] milestone 5, but should also work on [[2008.12]].

=== 1. Check installed packages ===
First check that you have the correct package versions installed with {{{opkg list_installed | grep blue}}}. The versions should be these:

bluez-audio - 3.33-r3
bluez-utils - 3.33-r3
bluez-utils-alsa - 3.33-r3
bluez-utils-compat - 3.33-r3
libbluetooth2 - 3.33-r0

=== 1.1 Check installed packages (Bluez4) ===
For user with bluez4 (SHR-unstable ecc.) bluez-audio 3.33 and bluez-utils-alsa 3.33 are not compatible with bluez4

bluez4 - 4.30-r1
connman-plugin-bluetooth - 0.10-r0 -
kernel-module-bluetooth - 2.6.28-oe1+xxxxx
libasound-module-bluez - 4.30-r0
libbluetooth2 - 3.33-r0

If you are willing to risk your installationand want to stay on bluez3, you can remove bluez4 to resolve this issue by doing

opkg remove -recursive bluez4

(will also remove connman-plugin-bluetooth). After that you need to edit /etc/init.d/bluetooth and replace '''DAEMON_NAME=bluetoothd''' with '''DAEMON_NAME=hcid'''. This has been tested and works on FSO MS5.

=== 2. Add bluetooth device to /etc/asound.conf ===
Your /etc/asound.conf should contain these:

pcm.!default {
type plug
slave.pcm "dmix"
}

ctl.mixer0 {
type hw
card 0
}

pcm.bluetooth {
type bluetooth
device "XX:XX:XX:XX:XX:XX"
profile "auto"
}

XX:XX:XX should be replaced with your device ID.

=== 3. Connect to the device ===
Turn on bluetooth in the GUI and then do

export DEVICE=XX:XX:XX:XX:XX:XX

/etc/init.d/bluetooth stop
/etc/init.d/bluetooth start

passkey-agent --default 0000 &

dbus-send --system --type=method_call --print-reply --dest=org.bluez \
/org/bluez/hci0 org.bluez.Adapter.CreateBonding string:$DEVICE

dbus-send --system --print-reply --dest=org.bluez \
/org/bluez org.bluez.Manager.ActivateService string:audio

dbus-send --system --type=method_call --print-reply --dest=org.bluez \
/org/bluez/audio org.bluez.audio.Manager.CreateDevice string:$DEVICE

dbus-send --system --type=method_call --print-reply --dest=org.bluez \
"/org/bluez/audio/device0" org.bluez.audio.Sink.Connect

If the last step fails, see to it that the device returned in the step before is device0 - otherwise use the other number.

=== 3.1 Connect to the device (Bluez4) ===
Turn on bluetooth in the GUI and then pair with simple-agent (passkey-agent from bluez-utils 3.33 won't work)
simple-agent is included in bluez4 source package (src folder) or you can find it there : http://shr-project.org/trac/wiki/Using

/etc/init.d/bluetooth stop
/etc/init.d/bluetooth start

python simple-agent hci0 XX:XX:XX:XX:XX:XX

Response is something like this :

RequestPinCode (/org/bluez/XXXX/hci0/dev_XX_XX_XX_XX_XX_XX)
Enter PIN Code: XXXX
Release
New device (/org/bluez/XXXX/hci0/dev_XX_XX_XX_XX_XX_XX)

Now you can start playing, no need to connect manualy.

=== 4. Start playing ===
To play a file with [[mplayer]] use the following command:

mplayer -ao alsa:device=bluetooth /path/to/file.ogg

== 5. Potential troubles ==
* If you experience problems with choppiness, try changing your hcid.conf to include "lm accept,master;" and "lp hold,sniff,park;" You may also have to bond (commonly known as 'pairing') your phone and your headset. See http://wiki.bluez.org/wiki/HOWTO/Bonding for details. [[User:Mercury|Mercury]] 17:36, 5 September 2008 (UTC). On bluez4, use on commandline 'hciconfig hci0 lm master; hciconfig hci0 lp hold,sniff,park' as hcid.conf doesn't exist

* If you don't install all required packages (see above) namely libasound-module-bluez you will get:
Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_bluetooth.so

== 6. Devices that work==

Moved to [[List_of_bluetooth_headsets]]

[[Category:Audio]]

A2DP

2010-03-02T23:00:08Z

Psonek: Move troubleshooting to section below

The [http://en.wikipedia.org/wiki/A2DP A2DP] bluetooth profile allows high quality audio to be transferred from the phone.

This page describes how to setup A2DP on the Freerunner.

== How to setup A2DP manually ==
This information is mostly taken from [http://lists.openmoko.org/nabble.html#nabble-td2176481 this mail thread]. It has been tested on [[FDOM]] and [[FSO]] milestone 5, but should also work on [[2008.12]].

=== 1. Check installed packages ===
First check that you have the correct package versions installed with {{{opkg list_installed | grep blue}}}. The versions should be these:

bluez-audio - 3.33-r3
bluez-utils - 3.33-r3
bluez-utils-alsa - 3.33-r3
bluez-utils-compat - 3.33-r3
libbluetooth2 - 3.33-r0

=== 1.1 Check installed packages (Bluez4) ===
For user with bluez4 (SHR-unstable ecc.) bluez-audio 3.33 and bluez-utils-alsa 3.33 are not compatible with bluez4

bluez4 - 4.30-r1
connman-plugin-bluetooth - 0.10-r0 -
kernel-module-bluetooth - 2.6.28-oe1+xxxxx
libasound-module-bluez - 4.30-r0
libbluetooth2 - 3.33-r0

If you are willing to risk your installationand want to stay on bluez3, you can remove bluez4 to resolve this issue by doing

opkg remove -recursive bluez4

(will also remove connman-plugin-bluetooth). After that you need to edit /etc/init.d/bluetooth and replace '''DAEMON_NAME=bluetoothd''' with '''DAEMON_NAME=hcid'''. This has been tested and works on FSO MS5.

=== 2. Add bluetooth device to /etc/asound.conf ===
Your /etc/asound.conf should contain these:

pcm.!default {
type plug
slave.pcm "dmix"
}

ctl.mixer0 {
type hw
card 0
}

pcm.bluetooth {
type bluetooth
device "XX:XX:XX:XX:XX:XX"
profile "auto"
}

XX:XX:XX should be replaced with your device ID.

=== 3. Connect to the device ===
Turn on bluetooth in the GUI and then do

export DEVICE=XX:XX:XX:XX:XX:XX

/etc/init.d/bluetooth stop
/etc/init.d/bluetooth start

passkey-agent --default 0000 &

dbus-send --system --type=method_call --print-reply --dest=org.bluez \
/org/bluez/hci0 org.bluez.Adapter.CreateBonding string:$DEVICE

dbus-send --system --print-reply --dest=org.bluez \
/org/bluez org.bluez.Manager.ActivateService string:audio

dbus-send --system --type=method_call --print-reply --dest=org.bluez \
/org/bluez/audio org.bluez.audio.Manager.CreateDevice string:$DEVICE

dbus-send --system --type=method_call --print-reply --dest=org.bluez \
"/org/bluez/audio/device0" org.bluez.audio.Sink.Connect

If the last step fails, see to it that the device returned in the step before is device0 - otherwise use the other number.

=== 3.1 Connect to the device (Bluez4) ===
Turn on bluetooth in the GUI and then pair with simple-agent (passkey-agent from bluez-utils 3.33 won't work)
simple-agent is included in bluez4 source package (src folder) or you can find it there : http://shr-project.org/trac/wiki/Using

/etc/init.d/bluetooth stop
/etc/init.d/bluetooth start

python simple-agent hci0 XX:XX:XX:XX:XX:XX

Response is something like this :

RequestPinCode (/org/bluez/XXXX/hci0/dev_XX_XX_XX_XX_XX_XX)
Enter PIN Code: XXXX
Release
New device (/org/bluez/XXXX/hci0/dev_XX_XX_XX_XX_XX_XX)

Now you can start playing, no need to connect manualy.

=== 4. Start playing ===
To play a file with [[mplayer]] use the following command:

mplayer -ao alsa:device=bluetooth /path/to/file.ogg

== 5. Potential troubles ==
* If you experience problems with choppiness, try changing your hcid.conf to include "lm accept,master;" and "lp hold,sniff,park;" You may also have to bond (commonly known as 'pairing') your phone and your headset. See http://wiki.bluez.org/wiki/HOWTO/Bonding for details. [[User:Mercury|Mercury]] 17:36, 5 September 2008 (UTC). On bluez4, use on commandline 'hciconfig hci0 lm master; hciconfig hci0 lp hold,sniff,park' as hcid.conf doesn't exist

== 6. Devices that work==

Moved to [[List_of_bluetooth_headsets]]

[[Category:Audio]]

A2DP

2010-03-02T22:56:12Z

Psonek: Troubleshooting for missing libasound_module_pcm_bluetooth.so

The [http://en.wikipedia.org/wiki/A2DP A2DP] bluetooth profile allows high quality audio to be transferred from the phone.

This page describes how to setup A2DP on the Freerunner.

== How to setup A2DP manually ==
This information is mostly taken from [http://lists.openmoko.org/nabble.html#nabble-td2176481 this mail thread]. It has been tested on [[FDOM]] and [[FSO]] milestone 5, but should also work on [[2008.12]].

=== 1. Check installed packages ===
First check that you have the correct package versions installed with {{{opkg list_installed | grep blue}}}. The versions should be these:

bluez-audio - 3.33-r3
bluez-utils - 3.33-r3
bluez-utils-alsa - 3.33-r3
bluez-utils-compat - 3.33-r3
libbluetooth2 - 3.33-r0

=== 1.1 Check installed packages (Bluez4) ===
For user with bluez4 (SHR-unstable ecc.) bluez-audio 3.33 and bluez-utils-alsa 3.33 are not compatible with bluez4

bluez4 - 4.30-r1
connman-plugin-bluetooth - 0.10-r0 -
kernel-module-bluetooth - 2.6.28-oe1+xxxxx
libasound-module-bluez - 4.30-r0
libbluetooth2 - 3.33-r0

If you are willing to risk your installationand want to stay on bluez3, you can remove bluez4 to resolve this issue by doing

opkg remove -recursive bluez4

(will also remove connman-plugin-bluetooth). After that you need to edit /etc/init.d/bluetooth and replace '''DAEMON_NAME=bluetoothd''' with '''DAEMON_NAME=hcid'''. This has been tested and works on FSO MS5.

=== 2. Add bluetooth device to /etc/asound.conf ===
Your /etc/asound.conf should contain these:

pcm.!default {
type plug
slave.pcm "dmix"
}

ctl.mixer0 {
type hw
card 0
}

pcm.bluetooth {
type bluetooth
device "XX:XX:XX:XX:XX:XX"
profile "auto"
}

XX:XX:XX should be replaced with your device ID.

=== 3. Connect to the device ===
Turn on bluetooth in the GUI and then do

export DEVICE=XX:XX:XX:XX:XX:XX

/etc/init.d/bluetooth stop
/etc/init.d/bluetooth start

passkey-agent --default 0000 &

dbus-send --system --type=method_call --print-reply --dest=org.bluez \
/org/bluez/hci0 org.bluez.Adapter.CreateBonding string:$DEVICE

dbus-send --system --print-reply --dest=org.bluez \
/org/bluez org.bluez.Manager.ActivateService string:audio

dbus-send --system --type=method_call --print-reply --dest=org.bluez \
/org/bluez/audio org.bluez.audio.Manager.CreateDevice string:$DEVICE

dbus-send --system --type=method_call --print-reply --dest=org.bluez \
"/org/bluez/audio/device0" org.bluez.audio.Sink.Connect

If the last step fails, see to it that the device returned in the step before is device0 - otherwise use the other number.

=== 3.1 Connect to the device (Bluez4) ===
Turn on bluetooth in the GUI and then pair with simple-agent (passkey-agent from bluez-utils 3.33 won't work)
simple-agent is included in bluez4 source package (src folder) or you can find it there : http://shr-project.org/trac/wiki/Using

/etc/init.d/bluetooth stop
/etc/init.d/bluetooth start

python simple-agent hci0 XX:XX:XX:XX:XX:XX

Response is something like this :

RequestPinCode (/org/bluez/XXXX/hci0/dev_XX_XX_XX_XX_XX_XX)
Enter PIN Code: XXXX
Release
New device (/org/bluez/XXXX/hci0/dev_XX_XX_XX_XX_XX_XX)

Now you can start playing, no need to connect manualy.

=== 4. Start playing ===
To play a file with [[mplayer]] use the following command:

mplayer -ao alsa:device=bluetooth /path/to/file.ogg

Troubleshooting: if you don't install all required packages (see above) you will get:
Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_bluetooth.so

== 5. Potential troubles ==
* If you experience problems with choppiness, try changing your hcid.conf to include "lm accept,master;" and "lp hold,sniff,park;" You may also have to bond (commonly known as 'pairing') your phone and your headset. See http://wiki.bluez.org/wiki/HOWTO/Bonding for details. [[User:Mercury|Mercury]] 17:36, 5 September 2008 (UTC). On bluez4, use on commandline 'hciconfig hci0 lm master; hciconfig hci0 lp hold,sniff,park' as hcid.conf doesn't exist

== 6. Devices that work==

Moved to [[List_of_bluetooth_headsets]]

[[Category:Audio]]

Successful Use Cases

2009-07-18T02:18:47Z

Psonek: Video player

{{Languages|Successful Use Cases}}

This page is intended to collect all of the successful use cases people have managed to make work with their freerunners. The goal is to both provide examples of the kinds of interesting things people are doing, but also to provide info on how others can make use of the same use case.

If you've been using your FR successfully for something not listed below - please copy the template block at the bottom and fill it in with details like what Distro and software you used, and any interesting setup steps.

__TOC__

=== PDF Reader ===

I use the FR as a PDF reader when I'm away from my laptop, or in a situation where I can't easily use a laptop, such as walking, standing up on a bus or metro, etc.

Distro: OM2009 TR5 - but should work on any X based distro

Software: [[Epdfview]] - make sure that you have the recent version with a way to get out of fullscreen mode, and a way to switch pages in fullscreen mode.

The process I use is to just scp the pdfs into a 'doc' directory on the FR, and leave the edpfview open dialog on that folder. Scrolling through the files is a little annoying, but it works passably well. some kind of a 'bookshelf' program that would display the list of PDFs in a better way and launch epdfview on each would be a great addition.

=== IM Client - Pidgin ===

With Pidgin and GPRS, I can use many different IM protocols whereever I am.

Distro: OM 2009 TR5 - but should work on any X based distro

Software: [[Pidgin]]

I use the OM settings screen to join gprs, and then start up pidgin. I've only added a google talk account so far, and I think I might have needed to rotate the screen horizontal to fill in some of the account details, but aside from that it works quite well for IM.

=== GPS - tangoGPS ===

I use my freerunner as a GPS device. While I am connected on a fast connection, I can use tangoGPS to download many tiles. However the omgps tool has become just as capable as tangoGPS. It also has some additional features like AGPS to get faster fixes when connected to GPRS and a GPS data screen to show alot of information about the GPS module/current fix.

I sometimes use the tangoGPS POI tool to mark down possible additions and corrections for the OpenStreetMap project. I can easily extract these later using a python script to read the sqlite database they are stored in. The POI feature can also be combined with a program called [[Gtkaddpoi]] to add markers for addresses and locations to your map, so you can find them when you are travelling.

When I am using the GPS module, I usually leave the openBmap program open to help collect data about GSM cell ids that could one day allow me to get my position without activating the GPS.

Distro: SHR-Unstable

Software: [[tangoGPS]] + [http://code.google.com/p/omgps/ omgps] + [[openBmap]]

Setup:

I linked ~/Maps to /media/card/Maps which means the maps are stored on the sd card.

I also like to use the differently stylised [http://developers.cloudmade.com/wiki/tiles tiles from the Cloudmade site] but you have to register for a free API key to get a URL for that. Also trying to enter the URL in tangoGPS crashed it but I was able to use the following command to set it:

<code>
gconftool-2 -s /apps/tangogps/repos
"[OSM|http://tile.cloudmade.com/APIKEYHERE/1/256/%d/%d/%d.png|/media/card/Maps/OSM|0]"
--type list --list-type string
</code>

=== Video player - mplayer ===

Freerunner is very good playing videos. It has very good display with nice colors and is fast enough to play fullscreen videos in 240x320 resolution. I have seen several movies on Freerunner and the experience was very good.

Distro: QtMoko

Software: [[QMplayer]]

QMplayer is installed in QtMoko by default. On the first use it will automatically download and install codecs from internet. You can also use QMplayer to browse movies and music on your PC and on sigle click you can play or download selected file (automatically transcoded for Freerunner resolution.)

=== Template ===

Put a brief description of the use case here

Distro:

Software:

Setup:

Put any other details here

Manuals/Android

2009-01-24T16:37:00Z

Psonek: /* Suspend */

{|align=right
|__TOC__
|}
[[Image:android.png]]

= Introduction =
This page is dedicated to the daily usage of Android on the [[Neo 1973]] and [[Neo FreeRunner]] handsets.

The informations here have been updated for the following release : [http://freerunner.android.koolu.com/release-files Koolu Beta2 Android release]. But should be the same for any not too old release.

You can find general informations (porting/development and day to day usage) about Android and Neo phones here : [[Android]]

= Subsystems =

== Accelerometers ==
Works, can be tested with simple game called Amazed

== Bluetooth ==
Works, latest kernels need permissions for second rfkill interface in init.rc to turn it on.

== GPS ==
Once i got it working, you can test with AndNav2 program.

== GPRS ==
Does not work, GSM get's confused when you try to use it

== GSM ==
Sources for libmuxgsm-ril.so not released yet, latest images have binary from ML that works fine.
The SIM's PIN code cannot be validated. For now disable the PIN code using another phone.

== Wifi ==
Works, but i have problems with scanning when just one AP is in range, it fails most of the time.

= Data management =

== Contacts ==

=== Importing ===

==== From SIM =====
Works, Contacts->menu->Settings->SIM contacts importer.

=== Synchronization ===

== Calendar ==

=== Alarm ===
Can add new alarms, but details of an alarm can't be edited.

=== Importing ===

=== Synchronization ===

== Media ==
Can play OGG audio files, picture application crashes

== SMS ==
Some received SMS's can't be read.

= Others =

== Software keyboard ==
Works, can be brought up with short press to power button.

== Suspend ==
* Works, can be done with 1s press of power button, wake up with long power button press, don't use screen timeouts, disable it in Settings->Sound & display->Screen timeout->Never timeout.
* Michael Trimarchi's images allow resume from suspend after two short presses. However, sometimes it takes a few tries for the phone to wake up.
* For me resume works best if i long press power until the main screen appears and the short power press that unlocks screen.
* During suspend the phone seems to wake up make an audible click and go back to sleep.

== USB networking ==

== USB keyboard ==

== USB Host mode ==

= Software installation and updates =
For initial Android flashing, take a look at: [[Android_on_Freerunner]]

== Install new software ==

== Update software (without reflashing) ==

= Links =

Android on Freerunner

2009-01-19T09:27:06Z

Psonek: gps comment

{{Languages|Android on Freerunner}}
== Android on Freerunner ==
Google has released their open source version of the Android phone software distribution. In order to use it on the Freerunner, a number of patches need to be applied and a compiler with armv4 java exception support needs to be used to compile the software.

== Status ==

Most of the hardware on Freerunner seems to work on latest Android images, but not always perfectly.

{| border="1"
|-
| SW keyboard || works, can be brought up with short press to power button
|-
| Suspend || works, can be done with 1s press of power button, wake up with long power button press, don't use screen timeouts, disable it in Settings->Sound & display->Screen timeout->Never timeout
|-
| GSM || sources for libmuxgsm-ril.so not released yet, latest images have binary from ML that works fine
|-
| GPRS || does not work, GSM get's confused when you try to use it
|-
| Contacts on SIM || works, Contacts->menu->Settings->SIM contacts importer
|-
| Bluetooth || works, latest kernels need permissions for second rfkill interface in init.rc to turn it on
|-
| Wifi || works, but i have problems with scanning when just one AP is in range, it fails most of the time
|-
| GPS || once i got it working, you can test with AndNav2 program
|-
| Accelerometers || works, can be tested with simple game called Amazed
|-
| Media || can play OGG audio files, picure application crashes
|}

== Compiler suite ==

Android is a little picky about the version of gcc compiler. It also requires some java exception support that isn't available for armv4 without a minor modification. The following tools are what I use to build Android:

=== Binutils 2.18 ===

At one time I had some armv5t code that was compiled into Android which would cause the linker to generate these blx instructions which fail on armv4. I'm not sure if this is still necessary, but I still have the following change applied to binutils:

<pre>
diff -urN binutils-2.18-orig/bfd/elf32-arm.c binutils-2.18/bfd/elf32-arm.c
--- binutils-2.18-orig/bfd/elf32-arm.c 2007-08-07 02:59:23.000000000 +0700
+++ binutils-2.18/bfd/elf32-arm.c 2008-03-15 11:30:17.000000000 +0700
@@ -3093,8 +3093,8 @@
static void check_use_blx(struct elf32_arm_link_hash_table *globals)
{
if (bfd_elf_get_obj_attr_int (globals->obfd, OBJ_ATTR_PROC,
- Tag_CPU_arch) > 2)
- globals->use_blx = 1;
+ Tag_CPU_arch) >= TAG_CPU_ARCH_V5T)
+ globals->use_blx = 0;
}

bfd_boolean
</pre>

configure --prefix={devel path}/android/cross --target=arm-eabi

=== gcc 4.2.4 with gcc41-java-arm4.patch ===

configure --prefix={devel path}/android/cross --target=arm-eabi --with-arch=armv4t --enable-shared --enable-threads --disable-nls --disable-libmudflap --enable-target-optspace --with-abi=aapcs --enable-multilib --disable-libssp --disable-libstdcxx --enable-languages=c,c++

=== java-6-sun ===

This is the standard Linux package available for most (all?) distributions.

== Patches ==

Coming soon. I've posted a number of them on the devel mailing list so far. Eventually, I expect to provide everything necessary for people to build Android for themselves.

== Android on internal flash ==

=== Images ===

There are currently a few prebuild images:

[http://panicking.kicks-ass.org/download/ Michael Trimarchi's images with latest fixes]
[http://people.openmoko.org/sean_mcneil/ Sean McNeil images]

To use the Kernel you have to either :

* adjust your [[Uboot]] environment to support a Kernel of more then 2 MB
* change to the [[Qi]] Bootloader. It supports 2MB kernels out of the box.

I have placed an older 2.6.26 kernel with Android support at:

[http://people.openmoko.org/sean_mcneil/uImage-android uImage-android]

I have put up a jffs2 image that replaces rootfs on the Freerunner at:

[http://people.openmoko.org/sean_mcneil/androidfs.jffs2 androidfs.jffs2]

=== Installation on internal flash ===

As noted above, this installation requires you to wipe out the existing kernel and rootfs in NAND on your Freerunner. You also must have an SDCARD and it needs to be configured with two (2) primary partitions: First is VFAT/MSDOS (16 or 32) which acts as the /sdcard storage area for pictures, movies, music, etc. and the Second is an ext3 primary partition for use of internal Android /data area to store settings, caches, etc.

The first thing I suggest is to setup an SDCARD. You can flash the NAND first, but you must have an SDCARD with two partitions as stated before you'll be able to boot. I use a 2GB card which I have split in half. fdisk shows me:

/dev/mmcblk0p1 1 2454 996310 6 FAT16 
/dev/mmcblk0p2 2455 4908 996324 83 Linux

formatted as

sudo mkfs.vfat /dev/mmcblk0p1 
sudo mkfs.ext3 /dev/mmcblk0p2

There is no need to populate the ext3 partition at all. The VFAT partition can be populated with media content if you so desire.

With your SDCARD all set, you are ready to flash the kernel and rootfs:

sudo {path_to}/dfu-util -d 0x1d50:0x5119 -a kernel -D uImage-android 
sudo {path_to}/dfu-util -d 0x1d50:0x5119 -a rootfs -D androidfs.jffs2 

== Android on SDcard ==

=== Images ===

There are currently a few prebuild images:
[http://activationrecord.net/radekp/openmoko/android/ Radek Polak's SD card images] (install on ext3, first partition on SD must be FAT16)

Some notes about booting android from sdcard :

=== Setup ===

* Build android from source. See [http://trac.koolu.org/ koolu website] for directions.
* Use the first script in [http://lists.openmoko.org/pipermail/community/2008-December/036982.html this mail] (adapt to your filesystem) to stage your android install.
* copy the contents of this directory on a ext3 partition on your sdcard.
* add a /boot directory on your sdcard.
* copy the uImage-android kernel (see above) and copy it inside your /boot with the exact name '''uImage-GTA02.bin'''
* I changed the init.rc (in your root on the sd) to remove mounts that could be problematic (/data for example) :
<pre>
--- filesystem/root/init.rc 2008-12-15 17:51:14.000000000 +0100
+++ phyce.init.rc 2008-12-19 15:56:25.000000000 +0100
@@ -24,7 +24,7 @@
mkdir /sqlite_stmt_journals 01777 root root
mount tmpfs tmpfs /sqlite_stmt_journals size=4m

- mount rootfs rootfs / ro remount
+ mount rootfs rootfs / rw remount

write /proc/sys/kernel/panic_on_oops 1
write /proc/sys/kernel/hung_task_timeout_secs 0
@@ -38,14 +38,14 @@
# mount yaffs2 mtd@system /system ro remount

# We chown/chmod /data again so because mount is run as root + defaults
- mount ext3 /dev/block/mmcblk0p2 /data nosuid nodev
- chown system system /data
- chmod 0771 /data
+# mount ext3 /dev/block/mmcblk0p2 /data nosuid nodev
+# chown system system /data
+# chmod 0771 /data

# Same reason as /data above
- mount yaffs2 mtd@cache /cache nosuid nodev
- chown system cache /cache
- chmod 0770 /cache
+# mount yaffs2 mtd@cache /cache nosuid nodev
+# chown system cache /cache
+# chmod 0770 /cache
</pre>

* Install [[Qi]] on you NAND flash. You can still boot whatever distro you've got on internal flash using the NOR bootloader. You should try the magic file in /boot to show kernel messages.
* boot the GTA02, and pray.

=== Status ===

Android boots and graphic UI appears (hurray) ! But, i cannot unlock my SIM so I can't tell more ;) Maybe you wanna try to remove PIN protection in your SIM (using another phone) and see what happens next.

[[User:Phyce|Phyce]] 16:25, 1 January 2009 (UTC)

== Android Debug Bridge ==

To assist in debugging and to gain shell access to the phone with Android, you can use

[http://people.openmoko.org/sean_mcneil/adb adb]

You should be able to connect to the phone as long as you start it up with the USB connected to your host. I don't think it will work if you plug it in after starting. Of course, you need to setup [[USB_Networking]] (<tt>ifconfig usb0</tt> ...) on your host before connecting.

Some helpful commands are:

ADBHOST=192.168.0.202 ./adb logcat - like a tail -f of the android log
ADBHOST=192.168.0.202 ./adb logcat -b radio - same as above for the radio logs
ADBHOST=192.168.0.202 ./adb shell - bring up a command shell to the phone
ADBHOST=192.168.0.202 ./adb kill-server - kill the background server on the host

Sometimes, adb gets stuck: if you cannot to the device run "adb kill-server" before trying other commands.

== Known Issues ==

This version of the linux kernel will not successfully wake from suspend mode. Your battery life will be significantly lowered because of this and the phone will lock up unless you setup the phones screen timeout to never.

This version of the kernel also uses a keypad hack. The buttons layout is as follows:

Aux left-hand upper button is the "back" key.
Power button is:
menu button when pushed quickly,
end button when held for more than a second and released,
power-off if held for 10 seconds.
[[category|Distribution]]
[[Category:Flashing Openmoko]]

Android on Freerunner

2009-01-19T09:17:21Z

Psonek: table with current status, links to prebuild images

{{Languages|Android on Freerunner}}
== Android on Freerunner ==
Google has released their open source version of the Android phone software distribution. In order to use it on the Freerunner, a number of patches need to be applied and a compiler with armv4 java exception support needs to be used to compile the software.

== Status ==

Most of the hardware on Freerunner seems to work on latest Android images, but not always perfectly.

{| border="1"
|-
| SW keyboard || works, can be brought up with short press to power button
|-
| Suspend || works, can be done with 1s press of power button, wake up with long power button press, don't use screen timeouts, disable it in Settings->Sound & display->Screen timeout->Never timeout
|-
| GSM || sources for libmuxgsm-ril.so not released yet, latest images have binary from ML that works fine
|-
| GPRS || does not work, GSM get's confused when you try to use it
|-
| Contacts on SIM || works, Contacts->menu->Settings->SIM contacts importer
|-
| Bluetooth || works, latest kernels need permissions for second rfkill interface in init.rc to turn it on
|-
| Wifi || works, but i have problems with scanning when just one AP is in range, it fails most of the time
|-
| Accelerometers || works, can be tested with simple game called Amazed
|-
| Media || can play OGG audio files, picure application crashes
|}

== Compiler suite ==

Android is a little picky about the version of gcc compiler. It also requires some java exception support that isn't available for armv4 without a minor modification. The following tools are what I use to build Android:

=== Binutils 2.18 ===

At one time I had some armv5t code that was compiled into Android which would cause the linker to generate these blx instructions which fail on armv4. I'm not sure if this is still necessary, but I still have the following change applied to binutils:

<pre>
diff -urN binutils-2.18-orig/bfd/elf32-arm.c binutils-2.18/bfd/elf32-arm.c
--- binutils-2.18-orig/bfd/elf32-arm.c 2007-08-07 02:59:23.000000000 +0700
+++ binutils-2.18/bfd/elf32-arm.c 2008-03-15 11:30:17.000000000 +0700
@@ -3093,8 +3093,8 @@
static void check_use_blx(struct elf32_arm_link_hash_table *globals)
{
if (bfd_elf_get_obj_attr_int (globals->obfd, OBJ_ATTR_PROC,
- Tag_CPU_arch) > 2)
- globals->use_blx = 1;
+ Tag_CPU_arch) >= TAG_CPU_ARCH_V5T)
+ globals->use_blx = 0;
}

bfd_boolean
</pre>

configure --prefix={devel path}/android/cross --target=arm-eabi

=== gcc 4.2.4 with gcc41-java-arm4.patch ===

configure --prefix={devel path}/android/cross --target=arm-eabi --with-arch=armv4t --enable-shared --enable-threads --disable-nls --disable-libmudflap --enable-target-optspace --with-abi=aapcs --enable-multilib --disable-libssp --disable-libstdcxx --enable-languages=c,c++

=== java-6-sun ===

This is the standard Linux package available for most (all?) distributions.

== Patches ==

Coming soon. I've posted a number of them on the devel mailing list so far. Eventually, I expect to provide everything necessary for people to build Android for themselves.

== Android on internal flash ==

=== Images ===

There are currently a few prebuild images:

[http://panicking.kicks-ass.org/download/ Michael Trimarchi's images with latest fixes]
[http://people.openmoko.org/sean_mcneil/ Sean McNeil images]

To use the Kernel you have to either :

* adjust your [[Uboot]] environment to support a Kernel of more then 2 MB
* change to the [[Qi]] Bootloader. It supports 2MB kernels out of the box.

I have placed an older 2.6.26 kernel with Android support at:

[http://people.openmoko.org/sean_mcneil/uImage-android uImage-android]

I have put up a jffs2 image that replaces rootfs on the Freerunner at:

[http://people.openmoko.org/sean_mcneil/androidfs.jffs2 androidfs.jffs2]

=== Installation on internal flash ===

As noted above, this installation requires you to wipe out the existing kernel and rootfs in NAND on your Freerunner. You also must have an SDCARD and it needs to be configured with two (2) primary partitions: First is VFAT/MSDOS (16 or 32) which acts as the /sdcard storage area for pictures, movies, music, etc. and the Second is an ext3 primary partition for use of internal Android /data area to store settings, caches, etc.

The first thing I suggest is to setup an SDCARD. You can flash the NAND first, but you must have an SDCARD with two partitions as stated before you'll be able to boot. I use a 2GB card which I have split in half. fdisk shows me:

/dev/mmcblk0p1 1 2454 996310 6 FAT16 
/dev/mmcblk0p2 2455 4908 996324 83 Linux

formatted as

sudo mkfs.vfat /dev/mmcblk0p1 
sudo mkfs.ext3 /dev/mmcblk0p2

There is no need to populate the ext3 partition at all. The VFAT partition can be populated with media content if you so desire.

With your SDCARD all set, you are ready to flash the kernel and rootfs:

sudo {path_to}/dfu-util -d 0x1d50:0x5119 -a kernel -D uImage-android 
sudo {path_to}/dfu-util -d 0x1d50:0x5119 -a rootfs -D androidfs.jffs2 

== Android on SDcard ==

=== Images ===

There are currently a few prebuild images:
[http://activationrecord.net/radekp/openmoko/android/ Radek Polak's SD card images] (install on ext3, first partition on SD must be FAT16)

Some notes about booting android from sdcard :

=== Setup ===

* Build android from source. See [http://trac.koolu.org/ koolu website] for directions.
* Use the first script in [http://lists.openmoko.org/pipermail/community/2008-December/036982.html this mail] (adapt to your filesystem) to stage your android install.
* copy the contents of this directory on a ext3 partition on your sdcard.
* add a /boot directory on your sdcard.
* copy the uImage-android kernel (see above) and copy it inside your /boot with the exact name '''uImage-GTA02.bin'''
* I changed the init.rc (in your root on the sd) to remove mounts that could be problematic (/data for example) :
<pre>
--- filesystem/root/init.rc 2008-12-15 17:51:14.000000000 +0100
+++ phyce.init.rc 2008-12-19 15:56:25.000000000 +0100
@@ -24,7 +24,7 @@
mkdir /sqlite_stmt_journals 01777 root root
mount tmpfs tmpfs /sqlite_stmt_journals size=4m

- mount rootfs rootfs / ro remount
+ mount rootfs rootfs / rw remount

write /proc/sys/kernel/panic_on_oops 1
write /proc/sys/kernel/hung_task_timeout_secs 0
@@ -38,14 +38,14 @@
# mount yaffs2 mtd@system /system ro remount

# We chown/chmod /data again so because mount is run as root + defaults
- mount ext3 /dev/block/mmcblk0p2 /data nosuid nodev
- chown system system /data
- chmod 0771 /data
+# mount ext3 /dev/block/mmcblk0p2 /data nosuid nodev
+# chown system system /data
+# chmod 0771 /data

# Same reason as /data above
- mount yaffs2 mtd@cache /cache nosuid nodev
- chown system cache /cache
- chmod 0770 /cache
+# mount yaffs2 mtd@cache /cache nosuid nodev
+# chown system cache /cache
+# chmod 0770 /cache
</pre>

* Install [[Qi]] on you NAND flash. You can still boot whatever distro you've got on internal flash using the NOR bootloader. You should try the magic file in /boot to show kernel messages.
* boot the GTA02, and pray.

=== Status ===

Android boots and graphic UI appears (hurray) ! But, i cannot unlock my SIM so I can't tell more ;) Maybe you wanna try to remove PIN protection in your SIM (using another phone) and see what happens next.

[[User:Phyce|Phyce]] 16:25, 1 January 2009 (UTC)

== Android Debug Bridge ==

To assist in debugging and to gain shell access to the phone with Android, you can use

[http://people.openmoko.org/sean_mcneil/adb adb]

You should be able to connect to the phone as long as you start it up with the USB connected to your host. I don't think it will work if you plug it in after starting. Of course, you need to setup [[USB_Networking]] (<tt>ifconfig usb0</tt> ...) on your host before connecting.

Some helpful commands are:

ADBHOST=192.168.0.202 ./adb logcat - like a tail -f of the android log
ADBHOST=192.168.0.202 ./adb logcat -b radio - same as above for the radio logs
ADBHOST=192.168.0.202 ./adb shell - bring up a command shell to the phone
ADBHOST=192.168.0.202 ./adb kill-server - kill the background server on the host

Sometimes, adb gets stuck: if you cannot to the device run "adb kill-server" before trying other commands.

== Known Issues ==

This version of the linux kernel will not successfully wake from suspend mode. Your battery life will be significantly lowered because of this and the phone will lock up unless you setup the phones screen timeout to never.

This version of the kernel also uses a keypad hack. The buttons layout is as follows:

Aux left-hand upper button is the "back" key.
Power button is:
menu button when pushed quickly,
end button when held for more than a second and released,
power-off if held for 10 seconds.
[[category|Distribution]]
[[Category:Flashing Openmoko]]

User talk:Seanmcneil3

2009-01-04T11:55:08Z

Psonek:

==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?
Radek: You can download one from http://activationrecord.net/radekp/openmoko/android/ More info in this mail http://lists.openmoko.org/pipermail/community/2008-December/038677.html

== 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:Psonek

2009-01-03T22:24:29Z

Psonek: New page: Here is my OpenMoko Freerunner stuff: http://activationrecord.net/radekp/openmoko/

Here is my OpenMoko Freerunner stuff:

http://activationrecord.net/radekp/openmoko/

Openmoko Local Groups: Czech

2009-01-03T22:22:57Z

Psonek:

[[Category:Openmoko Local Groups]]
Welcome to Openmoko Czech Republic users group!

Join to our [http://www.jabber.cz Jabber] conference: '''openmoko@chat.linjab.net''' [http://chat.linjab.net/logs/openmoko@chat.linjab.net/ logs]

Our discussion forum is http://openmoko.ohin.cz

{|border=1
!Name
!Skills
!Interest
!Location
!Jabber
|-
|[[User:Martix|Martix]]
|Python
|SHR, accelerometers, XMPP/Jabber, GPS
|Luhačovice
|martix@njs.netlab.cz
|-
|[[User:MMlosh|MMlosh]]
|C#, pascal, x51 assembler
|usable ASU E17 theme (to get that damn wrench to show.. and switch to different keyboard), Openstreetmaping, supertux-editor development
|Týniště nad Orlicí
|MMlosh@jabber.cz
|-
|[[User:MrBobby|MrBobby]]
|Java,C/C++,Python,etc.
|development of [http://projects.openmoko.org/projects/mojo/ Mojo] - Java Mail Client for Openmoko, Java on OM - Jalimo (cacao,GNU classpath,swt-gtk)
|Brno/Znojmo
|MrBobby@jabber.cz
|-
|[[User:xkucf03|xkucf03]]
|Linux, Java, SQL
|SHR, Jabber, Geocaching, [http://frantovo.cz/blog blog], economy, political science
|Praha
|xkucf03@jabber.cz
|-
|[[User:pv_|pedro]]
|Linux, SQL, Psychology
|dtto
|Praha
|admin@jabber.svoboda.cz
|-
|[[User:xcerj01|xcerj01]]
|GNU/Linux, C, SQL
|XMPP, GPS
|Praha
|cerny.honza@jabber.root.cz
|-
|[[User:psonek|psonek]]
|C, C#, Java, SQL
|GPS, Android, Openstreetmap
|Olomouc/Tršice
|psonek@njs.netlab.cz
|}

[[GroupSales/Czech Republic]]

[[Translation#Czech]]

==Another members list==

[http://www.abclinuxu.cz/openmoko?action=members ABCLinuxu]

[http://ohin.cz/openmoko/memberlist.php openmoko.ohin.cz]

Scummvm

2008-12-29T11:36:59Z

Psonek:

= ScummVM =

ScummVM is a program which allows you to run certain classic graphical point-and-click adventure games, provided you already have their data files. The clever part about this: ScummVM just replaces the executables shipped with the game, allowing you to play them on systems for which they were never designed!

You can obtain it either by using [[Mokomakefile]] via

# make build-package-scummvm

or using a binary, like so:

opkg install http://www.angstrom-distribution.org/feeds/2007/ipk/glibc/armv4t/base/libmad0_0.15.1b-r0_armv4t.ipk \
http://www.angstrom-distribution.org/feeds/2007/ipk/glibc/armv4t/base/libmpeg2-0_0.4.0b-r4_armv4t.ipk \
http://downloads.tuxfamily.org/3v1deb/openmoko/scummvm_0.12.0_armv4t.ipk

[[Image:MonkeyIsland.png|Monky Island]]

The games are copyrighted and the copyright holder has not given you a license to redistribute them so you'll only be able to play those you own. You can also download some free games from [http://www.scummvm.org/downloads.php#extras scummvm.org] and from the [http://www.the-underdogs.info Home of the Underdogs].

When starting ScummVM use the command

# openmoko-scummvm

This will map '''AUX''' button to the '''F5''' key, which is used to access the ScummVM menu. You should also find an entry on the main menu under ''Games''.

'''Note:''' On the Neo Freerunner the wrong keycode (not '''AUX''') is mapped to '''F5'''. Here is a corrected version of the file ''/usr/bin/openmoko-scummvm'':

<pre>#!/bin/sh

# Save current AUX Key mapping
SAVE_KEY="$(xmodmap -pke | grep 'keycode 177')"

# Map AUX Key to F5
xmodmap -e "keycode 177 = F5"

# Turn LCD feft
xrandr -o left

# Start the scummvm in fullscreen mode
scummvm --fullscreen --themepath=/usr/share/scummvm/

# Turn LCD normal
xrandr -o normal

# Restore the AUX Key mapping
xmodmap -e "$SAVE_KEY"</pre>

'''Note:''' It would be great if it where possible to get audio through the headphones and speaker muted.

More information on ScummVM can be found on the [http://www.scummvm.org/ official] site

=== Problems with mouse cursor ===

If the mouse cursor is shifted from where you click, just move your finer on touchscreen until you catch the cursor in corner. Now it will work correctly.

=== Monkey Island 2 ===

To be able to play Monkey Island 2 you need to pass ScummVM a parameter: 
root@fic-gta01:/$ DISPLAY=:0 openmoko-scummvm --boot-param=10001 monkey2

For easy access from the menu you can create a menu entry by creating the file /usr/share/applications/monkeyisland2.desktop with the following content:

<pre>[Desktop Entry]
Encoding=UTF-8
Name=LeChuck's Revenge
Comment=Monkey Island 2: LeChuck's Revenge
Exec=openmoko-scummvm --boot-param=10001 monkey2
Icon=monkeyisland2.png
Terminal=false
Type=Application
Categories=Games;
StartupNotify=false</pre>

'''No Desktop Icon Method'''

Making a change to your scummvmrc does not clutter up your desktop with another icon and keeps the interface consistent. Add the following to your scummvmrc (default location of ~/.scummvmrc) at the top global section add:

copy_protection=0

And after adding the Monkey Island 2 via the Scummvm GUI add the following below the [monkey2] section:

boot_param=10001

Then you can launch Monkey Island 2 from the menu like any other game without the annoying copy protection screens.

<onlyinclude>
{{ApplicationBox|
Name=[[Scummvm]]|
Description=ScummVM is a program which allows you to run certain classic graphical point-and-click adventure games, provided you already have their data files. The clever part about this: ScummVM just replaces the executables shipped with the game, allowing you to play them on systems for which they were never designed!|
Screenshot=MonkeyIsland.png|
Homepage=http://www.scummvm.org|
TestedOn=|
PackageName=
}}
</onlyinclude>
'''Source Code released : http://www.scummvm.org/downloads.php#source'''

[[Category:Gaming]]