http://openmoko.org/api.php?action=feedcontributions&user=Vanous&feedformat=atomOpenmoko - User contributions [en]2024-03-29T07:11:49ZUser contributionsMediaWiki 1.19.24http://openmoko.org/wiki/User_talk:VanousUser talk:Vanous2012-02-10T08:05:24Z<p>Vanous: /* MediaWiki */</p>
<hr />
<div>Česky prosím. :)<br />
<br />
==SHR manual: link to simple-agent==<br />
<br />
Hi! Thanks for updating the SHR Manual! Great job! <br />
<br />
I just noticed that you pointed out problems with the download of simple-agent. I tried the download link at this page and it's working fine for me - So I have removed your notice about an incorrect link. Furthermore I have added another link to a download from kernel.org. So I think we could delete the page [[simple-agent]] again. Is that okay for you ? --[[User:Marko Knöbl|Marko Knöbl]] 13:39, 21 February 2010 (UTC)<br />
<br />
: Hi Marko, yes, it seems to work now, when i tried last night the page didn't exist. Yes, simple-agent page can be deleted :) --[[User:Vanous|Vanous]] 13:44, 21 February 2010 (UTC)<br />
<br />
==Countless spam==<br />
Hi! Please do something against this countless spam attacks. I have already marked a lot pages as spam (cleared content), that spammer Marshall Nielsen may require your attention. :) --[[User:Quix0r|Quix0r]] 09:13, 31 July 2011 (UTC)<br />
<br />
: see my reply: http://wiki.openmoko.org/wiki/User_talk:Quix0r --[[User:Vanous|vanous]] 13:39, 31 July 2011 (UTC)<br />
:: more spam to delete and accounts to block: http://wiki.openmoko.org/wiki/Category:Candidates_for_speedy_deletion and it is good to have you back. :) --[[User:Quix0r|Quix0r]] 13:43, 14 September 2011 (UTC)<br />
::: i have been travelling and day job overloaded a bit, i am cleaning the mess little by little... thank you for your spam cleaning!--[[User:Vanous|vanous]] 11:13, 18 September 2011 (UTC)<br />
:::: Can you please check if [[Special:Log/upload|all spambots]] are blocked? --[[User:Quix0r|Quix0r]] 00:08, 29 September 2011 (UTC)<br />
:::::I have looked around, but understand that to block, i would need further permitions. I don't know the MW very well, so perhaps i have missed something obvious...? I block the spammers by name, but ofcourse this doesn't help much, as it is all automated... --[[User:Vanous|vanous]] 18:45, 30 September 2011 (UTC)<br />
<br />
==Combat web-spam==<br />
Please try to make an account on this wiki to see how they combat webspam:<br />
* http://multicopter.org<br />
I assume that after a few anti-web-spams the "are you human"-tests stops.<br />
<br>I think it is [http://multicopter.org/wiki/User_talk:Esden Esden] that has implemented it.<br>Please tell the other web-administrators and web-maintainers/developers about it.<br />
<br>--[[User:Glenn|Glenn]] 07:23, 13 November 2011 (UTC)<br />
<br />
** (re)captcha is one of the ways to go, but it requires admin access... i will try to email the admin. --[[User:Vanous|vanous]] 08:58, 19 November 2011 (UTC)<br />
<br />
Hi Vanous<br />
<br />
Please forward this information to the admin:<br />
<br />
*Automatically applies restrictions to Tor exit nodes.:<br />
*http://www.mediawiki.org/wiki/Extension:TorBlock<br />
*http://meta.wikimedia.org/wiki/Category:Open_proxies_blocked_on_all_participating_projects<br />
<br />
*The SpamBlacklist extension prevents edits that contain URLs whose domains match regular expression patterns defined in specified files or wiki pages:<br />
*http://www.mediawiki.org/wiki/Extension:SpamBlacklist<br />
*http://meta.wikimedia.org/wiki/Spam_blacklist<br />
*http://meta.wikimedia.org/wiki/Category:Anti_Spam<br />
--[[User:Glenn|Glenn]] 10:06, 20 November 2011 (UTC)<br />
:I'm dependent on Tor. :'( --[[User:Spdel|Spdel]] 10:16, 20 November 2011 (UTC)<br />
<br />
::I am pretty sure that exceptions can be made for registered users. And many thanks for your anti-spam effort. ;-) --[[User:Glenn|Glenn]] 10:21, 20 November 2011 (UTC)<br />
::: OK. I'm relieved to hear that. :-) --[[User:Spdel|Spdel]] 10:26, 20 November 2011 (UTC)<br />
<br />
I am planing to write a perl boot with MediaWiki::Bot but I need to know if the the edit api can be enabled or if I should investigate other modules as I'm tired of cuting & pasting { { spam } } { { delete-sp } } [[User:Jluis|jluis]]<br />
:Good idea. I think most of spam can reliably detected. --[[User:Spdel|Spdel]] 14:19, 7 February 2012 (UTC)<br />
::most of the new pages enter in this concept and edits to main:fi :) [[User:Jluis|jluis]]<br />
<br />
:::This sounds great. You need to contact the server admins for access...--[[User:Vanous|vanous]] 18:46, 7 February 2012 (UTC)<br />
<br />
===User rights===<br />
thx. It's an honour for me. :-)<br />
It works.<br />
<br />
Can the list of 'recent changes' cleaned too?<br />
--[[User:Spdel|Spdel]] 20:25, 8 February 2012 (UTC)<br />
:I don't know how :( , i tried to add myself also the bot permissions, but still i don't know how to clean the recent changes...--[[User:Vanous|vanous]] 21:33, 8 February 2012 (UTC)<br />
<br />
<br />
User rights are sufficient for me. But I don't know what is needed for jluis bot.<br />
--[[User:Spdel|Spdel]] 20:50, 8 February 2012 (UTC)<br />
:i have no experiences with the media wiki, so i don't know. yesterday, i finally cleaned all pages marked as for deletion, fortunately i found xdotool that helped me to generate all the hundreds (even thousands) of clicks and page moves, it still took some time, but was rather fast... . i am sure mediawiki can do all the blocking etc... we can contact the admins and get permissions needed, let me know what is required.--[[User:Vanous|vanous]] 21:33, 8 February 2012 (UTC)<br />
<br />
::Nice tool. Didn't know this.<br />
::I noticed your speed and wondered how. :-)<br />
::By the next spam-flood I start to understand, how to use this tool, at the latest. :-)<br />
::Should I leave spam-users unblocked and only block users with more than one spam-edit?<br />
::Maybe this would make it a little bit harder for spam-bots.<br />
::It's no problem for me. I have the time. :-)<br />
::Is the right for (manual) spam-cleaning given to jluis already?<br />
::So we can complete us. One for day-time, one for night.<br />
::(Until the anti-spam-bot is running) :-)<br />
::--[[User:Spdel|Spdel]] 22:59, 8 February 2012 (UTC)<br />
<br />
====MediaWiki====<br />
I found out; edits are automatically marked as bot-edit and not listed in 'recent changes' (by default) if you are a member of 'Bot'.<br />
<br />
And spam-revisions can deleted:<br />
*Delete Page<br />
*Restore<br />
*Select only revisions to restore<br />
*Restore<br />
*Reload History (CTRL+SHIFT+R or empty cache)<br />
**After this in 'history' are only restored revisions listed.<br />
**As you can see: [http://wiki.openmoko.org/index.php?title=Main_Page/fi&action=history Main Page/fi (History)] :-)<br />
--[[User:Spdel|Spdel]] 02:30, 9 February 2012 (UTC)<br />
<br />
Cool --[[User:Vanous|vanous]] 08:05, 10 February 2012 (UTC)<br />
<br />
==Blbej dotaz ke spamu==<br />
Nestačila by dát jen na stránku s vytvořením nového učtu věta do formuláře: Jaké je jméno zakladatele Openmoko?<br />
--[[User:Kukide|Kukide]] 18:48, 3 January 2012 (UTC)<br />
'''(Machine) translation:'''<br />
Stupid question to spam<br />
Enough to give only the page with the creation of new account forms the sentence:<br />
'What is the name of the founder of Openmoko?'<br />
''--[[User:Kukide|Kukide]] 18:48, 3 January 2012 (UTC)''<br />
<br />
asi jo, chceš to provést? --[[User:Vanous|vanous]] 21:34, 8 February 2012 (UTC)</div>Vanoushttp://openmoko.org/wiki/User_talk:VanousUser talk:Vanous2012-02-08T21:34:11Z<p>Vanous: /* Blbej dotaz ke spamu */</p>
<hr />
<div>Česky prosím. :)<br />
<br />
==SHR manual: link to simple-agent==<br />
<br />
Hi! Thanks for updating the SHR Manual! Great job! <br />
<br />
I just noticed that you pointed out problems with the download of simple-agent. I tried the download link at this page and it's working fine for me - So I have removed your notice about an incorrect link. Furthermore I have added another link to a download from kernel.org. So I think we could delete the page [[simple-agent]] again. Is that okay for you ? --[[User:Marko Knöbl|Marko Knöbl]] 13:39, 21 February 2010 (UTC)<br />
<br />
: Hi Marko, yes, it seems to work now, when i tried last night the page didn't exist. Yes, simple-agent page can be deleted :) --[[User:Vanous|Vanous]] 13:44, 21 February 2010 (UTC)<br />
<br />
==Countless spam==<br />
Hi! Please do something against this countless spam attacks. I have already marked a lot pages as spam (cleared content), that spammer Marshall Nielsen may require your attention. :) --[[User:Quix0r|Quix0r]] 09:13, 31 July 2011 (UTC)<br />
<br />
: see my reply: http://wiki.openmoko.org/wiki/User_talk:Quix0r --[[User:Vanous|vanous]] 13:39, 31 July 2011 (UTC)<br />
:: more spam to delete and accounts to block: http://wiki.openmoko.org/wiki/Category:Candidates_for_speedy_deletion and it is good to have you back. :) --[[User:Quix0r|Quix0r]] 13:43, 14 September 2011 (UTC)<br />
::: i have been travelling and day job overloaded a bit, i am cleaning the mess little by little... thank you for your spam cleaning!--[[User:Vanous|vanous]] 11:13, 18 September 2011 (UTC)<br />
:::: Can you please check if [[Special:Log/upload|all spambots]] are blocked? --[[User:Quix0r|Quix0r]] 00:08, 29 September 2011 (UTC)<br />
:::::I have looked around, but understand that to block, i would need further permitions. I don't know the MW very well, so perhaps i have missed something obvious...? I block the spammers by name, but ofcourse this doesn't help much, as it is all automated... --[[User:Vanous|vanous]] 18:45, 30 September 2011 (UTC)<br />
<br />
==Combat web-spam==<br />
Please try to make an account on this wiki to see how they combat webspam:<br />
* http://multicopter.org<br />
I assume that after a few anti-web-spams the "are you human"-tests stops.<br />
<br>I think it is [http://multicopter.org/wiki/User_talk:Esden Esden] that has implemented it.<br>Please tell the other web-administrators and web-maintainers/developers about it.<br />
<br>--[[User:Glenn|Glenn]] 07:23, 13 November 2011 (UTC)<br />
<br />
** (re)captcha is one of the ways to go, but it requires admin access... i will try to email the admin. --[[User:Vanous|vanous]] 08:58, 19 November 2011 (UTC)<br />
<br />
Hi Vanous<br />
<br />
Please forward this information to the admin:<br />
<br />
*Automatically applies restrictions to Tor exit nodes.:<br />
*http://www.mediawiki.org/wiki/Extension:TorBlock<br />
*http://meta.wikimedia.org/wiki/Category:Open_proxies_blocked_on_all_participating_projects<br />
<br />
*The SpamBlacklist extension prevents edits that contain URLs whose domains match regular expression patterns defined in specified files or wiki pages:<br />
*http://www.mediawiki.org/wiki/Extension:SpamBlacklist<br />
*http://meta.wikimedia.org/wiki/Spam_blacklist<br />
*http://meta.wikimedia.org/wiki/Category:Anti_Spam<br />
--[[User:Glenn|Glenn]] 10:06, 20 November 2011 (UTC)<br />
:I'm dependent on Tor. :'( --[[User:Spdel|Spdel]] 10:16, 20 November 2011 (UTC)<br />
<br />
::I am pretty sure that exceptions can be made for registered users. And many thanks for your anti-spam effort. ;-) --[[User:Glenn|Glenn]] 10:21, 20 November 2011 (UTC)<br />
::: OK. I'm relieved to hear that. :-) --[[User:Spdel|Spdel]] 10:26, 20 November 2011 (UTC)<br />
<br />
I am planing to write a perl boot with MediaWiki::Bot but I need to know if the the edit api can be enabled or if I should investigate other modules as I'm tired of cuting & pasting { { spam } } { { delete-sp } } [[User:Jluis|jluis]]<br />
:Good idea. I think most of spam can reliably detected. --[[User:Spdel|Spdel]] 14:19, 7 February 2012 (UTC)<br />
::most of the new pages enter in this concept and edits to main:fi :) [[User:Jluis|jluis]]<br />
<br />
:::This sounds great. You need to contact the server admins for access...--[[User:Vanous|vanous]] 18:46, 7 February 2012 (UTC)<br />
<br />
===User rights===<br />
thx. It's an honour for me. :-)<br />
It works.<br />
<br />
Can the list of 'recent changes' cleaned too?<br />
--[[User:Spdel|Spdel]] 20:25, 8 February 2012 (UTC)<br />
:I don't know how :( , i tried to add myself also the bot permissions, but still i don't know how to clean the recent changes...--[[User:Vanous|vanous]] 21:33, 8 February 2012 (UTC)<br />
<br />
<br />
User rights are sufficient for me. But I don't know what is needed for jluis bot.<br />
--[[User:Spdel|Spdel]] 20:50, 8 February 2012 (UTC)<br />
:i have no experiences with the media wiki, so i don't know. yesterday, i finally cleaned all pages marked as for deletion, fortunately i found xdotool that helped me to generate all the hundreds (even thousands) of clicks and page moves, it still took some time, but was rather fast... . i am sure mediawiki can do all the blocking etc... we can contact the admins and get permissions needed, let me know what is required.--[[User:Vanous|vanous]] 21:33, 8 February 2012 (UTC)<br />
<br />
==Blbej dotaz ke spamu==<br />
Nestačila by dát jen na stránku s vytvořením nového učtu věta do formuláře: Jaké je jméno zakladatele Openmoko?<br />
--[[User:Kukide|Kukide]] 18:48, 3 January 2012 (UTC)<br />
'''(Machine) translation:'''<br />
Stupid question to spam<br />
Enough to give only the page with the creation of new account forms the sentence:<br />
'What is the name of the founder of Openmoko?'<br />
''--[[User:Kukide|Kukide]] 18:48, 3 January 2012 (UTC)''<br />
<br />
asi jo, chceš to provést? --[[User:Vanous|vanous]] 21:34, 8 February 2012 (UTC)</div>Vanoushttp://openmoko.org/wiki/User_talk:VanousUser talk:Vanous2012-02-08T21:33:13Z<p>Vanous: /* User rights */</p>
<hr />
<div>Česky prosím. :)<br />
<br />
==SHR manual: link to simple-agent==<br />
<br />
Hi! Thanks for updating the SHR Manual! Great job! <br />
<br />
I just noticed that you pointed out problems with the download of simple-agent. I tried the download link at this page and it's working fine for me - So I have removed your notice about an incorrect link. Furthermore I have added another link to a download from kernel.org. So I think we could delete the page [[simple-agent]] again. Is that okay for you ? --[[User:Marko Knöbl|Marko Knöbl]] 13:39, 21 February 2010 (UTC)<br />
<br />
: Hi Marko, yes, it seems to work now, when i tried last night the page didn't exist. Yes, simple-agent page can be deleted :) --[[User:Vanous|Vanous]] 13:44, 21 February 2010 (UTC)<br />
<br />
==Countless spam==<br />
Hi! Please do something against this countless spam attacks. I have already marked a lot pages as spam (cleared content), that spammer Marshall Nielsen may require your attention. :) --[[User:Quix0r|Quix0r]] 09:13, 31 July 2011 (UTC)<br />
<br />
: see my reply: http://wiki.openmoko.org/wiki/User_talk:Quix0r --[[User:Vanous|vanous]] 13:39, 31 July 2011 (UTC)<br />
:: more spam to delete and accounts to block: http://wiki.openmoko.org/wiki/Category:Candidates_for_speedy_deletion and it is good to have you back. :) --[[User:Quix0r|Quix0r]] 13:43, 14 September 2011 (UTC)<br />
::: i have been travelling and day job overloaded a bit, i am cleaning the mess little by little... thank you for your spam cleaning!--[[User:Vanous|vanous]] 11:13, 18 September 2011 (UTC)<br />
:::: Can you please check if [[Special:Log/upload|all spambots]] are blocked? --[[User:Quix0r|Quix0r]] 00:08, 29 September 2011 (UTC)<br />
:::::I have looked around, but understand that to block, i would need further permitions. I don't know the MW very well, so perhaps i have missed something obvious...? I block the spammers by name, but ofcourse this doesn't help much, as it is all automated... --[[User:Vanous|vanous]] 18:45, 30 September 2011 (UTC)<br />
<br />
==Combat web-spam==<br />
Please try to make an account on this wiki to see how they combat webspam:<br />
* http://multicopter.org<br />
I assume that after a few anti-web-spams the "are you human"-tests stops.<br />
<br>I think it is [http://multicopter.org/wiki/User_talk:Esden Esden] that has implemented it.<br>Please tell the other web-administrators and web-maintainers/developers about it.<br />
<br>--[[User:Glenn|Glenn]] 07:23, 13 November 2011 (UTC)<br />
<br />
** (re)captcha is one of the ways to go, but it requires admin access... i will try to email the admin. --[[User:Vanous|vanous]] 08:58, 19 November 2011 (UTC)<br />
<br />
Hi Vanous<br />
<br />
Please forward this information to the admin:<br />
<br />
*Automatically applies restrictions to Tor exit nodes.:<br />
*http://www.mediawiki.org/wiki/Extension:TorBlock<br />
*http://meta.wikimedia.org/wiki/Category:Open_proxies_blocked_on_all_participating_projects<br />
<br />
*The SpamBlacklist extension prevents edits that contain URLs whose domains match regular expression patterns defined in specified files or wiki pages:<br />
*http://www.mediawiki.org/wiki/Extension:SpamBlacklist<br />
*http://meta.wikimedia.org/wiki/Spam_blacklist<br />
*http://meta.wikimedia.org/wiki/Category:Anti_Spam<br />
--[[User:Glenn|Glenn]] 10:06, 20 November 2011 (UTC)<br />
:I'm dependent on Tor. :'( --[[User:Spdel|Spdel]] 10:16, 20 November 2011 (UTC)<br />
<br />
::I am pretty sure that exceptions can be made for registered users. And many thanks for your anti-spam effort. ;-) --[[User:Glenn|Glenn]] 10:21, 20 November 2011 (UTC)<br />
::: OK. I'm relieved to hear that. :-) --[[User:Spdel|Spdel]] 10:26, 20 November 2011 (UTC)<br />
<br />
I am planing to write a perl boot with MediaWiki::Bot but I need to know if the the edit api can be enabled or if I should investigate other modules as I'm tired of cuting & pasting { { spam } } { { delete-sp } } [[User:Jluis|jluis]]<br />
:Good idea. I think most of spam can reliably detected. --[[User:Spdel|Spdel]] 14:19, 7 February 2012 (UTC)<br />
::most of the new pages enter in this concept and edits to main:fi :) [[User:Jluis|jluis]]<br />
<br />
:::This sounds great. You need to contact the server admins for access...--[[User:Vanous|vanous]] 18:46, 7 February 2012 (UTC)<br />
<br />
===User rights===<br />
thx. It's an honour for me. :-)<br />
It works.<br />
<br />
Can the list of 'recent changes' cleaned too?<br />
--[[User:Spdel|Spdel]] 20:25, 8 February 2012 (UTC)<br />
:I don't know how :( , i tried to add myself also the bot permissions, but still i don't know how to clean the recent changes...--[[User:Vanous|vanous]] 21:33, 8 February 2012 (UTC)<br />
<br />
<br />
User rights are sufficient for me. But I don't know what is needed for jluis bot.<br />
--[[User:Spdel|Spdel]] 20:50, 8 February 2012 (UTC)<br />
:i have no experiences with the media wiki, so i don't know. yesterday, i finally cleaned all pages marked as for deletion, fortunately i found xdotool that helped me to generate all the hundreds (even thousands) of clicks and page moves, it still took some time, but was rather fast... . i am sure mediawiki can do all the blocking etc... we can contact the admins and get permissions needed, let me know what is required.--[[User:Vanous|vanous]] 21:33, 8 February 2012 (UTC)<br />
<br />
==Blbej dotaz ke spamu==<br />
Nestačila by dát jen na stránku s vytvořením nového učtu věta do formuláře: Jaké je jméno zakladatele Openmoko?<br />
--[[User:Kukide|Kukide]] 18:48, 3 January 2012 (UTC)<br />
'''(Machine) translation:'''<br />
Stupid question to spam<br />
Enough to give only the page with the creation of new account forms the sentence:<br />
'What is the name of the founder of Openmoko?'<br />
''--[[User:Kukide|Kukide]] 18:48, 3 January 2012 (UTC)''</div>Vanoushttp://openmoko.org/wiki/User_talk:VanousUser talk:Vanous2012-02-07T18:46:29Z<p>Vanous: /* Combat web-spam */</p>
<hr />
<div>Česky prosím. :)<br />
<br />
==SHR manual: link to simple-agent==<br />
<br />
Hi! Thanks for updating the SHR Manual! Great job! <br />
<br />
I just noticed that you pointed out problems with the download of simple-agent. I tried the download link at this page and it's working fine for me - So I have removed your notice about an incorrect link. Furthermore I have added another link to a download from kernel.org. So I think we could delete the page [[simple-agent]] again. Is that okay for you ? --[[User:Marko Knöbl|Marko Knöbl]] 13:39, 21 February 2010 (UTC)<br />
<br />
: Hi Marko, yes, it seems to work now, when i tried last night the page didn't exist. Yes, simple-agent page can be deleted :) --[[User:Vanous|Vanous]] 13:44, 21 February 2010 (UTC)<br />
<br />
==Countless spam==<br />
Hi! Please do something against this countless spam attacks. I have already marked a lot pages as spam (cleared content), that spammer Marshall Nielsen may require your attention. :) --[[User:Quix0r|Quix0r]] 09:13, 31 July 2011 (UTC)<br />
<br />
: see my reply: http://wiki.openmoko.org/wiki/User_talk:Quix0r --[[User:Vanous|vanous]] 13:39, 31 July 2011 (UTC)<br />
:: more spam to delete and accounts to block: http://wiki.openmoko.org/wiki/Category:Candidates_for_speedy_deletion and it is good to have you back. :) --[[User:Quix0r|Quix0r]] 13:43, 14 September 2011 (UTC)<br />
::: i have been travelling and day job overloaded a bit, i am cleaning the mess little by little... thank you for your spam cleaning!--[[User:Vanous|vanous]] 11:13, 18 September 2011 (UTC)<br />
:::: Can you please check if [[Special:Log/upload|all spambots]] are blocked? --[[User:Quix0r|Quix0r]] 00:08, 29 September 2011 (UTC)<br />
:::::I have looked around, but understand that to block, i would need further permitions. I don't know the MW very well, so perhaps i have missed something obvious...? I block the spammers by name, but ofcourse this doesn't help much, as it is all automated... --[[User:Vanous|vanous]] 18:45, 30 September 2011 (UTC)<br />
<br />
==Combat web-spam==<br />
Please try to make an account on this wiki to see how they combat webspam:<br />
* http://multicopter.org<br />
I assume that after a few anti-web-spams the "are you human"-tests stops.<br />
<br>I think it is [http://multicopter.org/wiki/User_talk:Esden Esden] that has implemented it.<br>Please tell the other web-administrators and web-maintainers/developers about it.<br />
<br>--[[User:Glenn|Glenn]] 07:23, 13 November 2011 (UTC)<br />
<br />
** (re)captcha is one of the ways to go, but it requires admin access... i will try to email the admin. --[[User:Vanous|vanous]] 08:58, 19 November 2011 (UTC)<br />
<br />
Hi Vanous<br />
<br />
Please forward this information to the admin:<br />
<br />
*Automatically applies restrictions to Tor exit nodes.:<br />
*http://www.mediawiki.org/wiki/Extension:TorBlock<br />
*http://meta.wikimedia.org/wiki/Category:Open_proxies_blocked_on_all_participating_projects<br />
<br />
*The SpamBlacklist extension prevents edits that contain URLs whose domains match regular expression patterns defined in specified files or wiki pages:<br />
*http://www.mediawiki.org/wiki/Extension:SpamBlacklist<br />
*http://meta.wikimedia.org/wiki/Spam_blacklist<br />
*http://meta.wikimedia.org/wiki/Category:Anti_Spam<br />
--[[User:Glenn|Glenn]] 10:06, 20 November 2011 (UTC)<br />
:I'm dependent on Tor. :'( --[[User:Spdel|Spdel]] 10:16, 20 November 2011 (UTC)<br />
<br />
::I am pretty sure that exceptions can be made for registered users. And many thanks for your anti-spam effort. ;-) --[[User:Glenn|Glenn]] 10:21, 20 November 2011 (UTC)<br />
::: OK. I'm relieved to hear that. :-) --[[User:Spdel|Spdel]] 10:26, 20 November 2011 (UTC)<br />
<br />
I am planing to write a perl boot with MediaWiki::Bot but I need to know if the the edit api can be enabled or if I should investigate other modules as I'm tired of cuting & pasting { { spam } } { { delete-sp } } [[User:Jluis|jluis]]<br />
:Good idea. I think most of spam can reliably detected.<br />
::most of the new pages enter in this concept and edits to main:fi :)<br />
<br />
:::This sounds great. You need to contact the server admins for access...--[[User:Vanous|vanous]] 18:46, 7 February 2012 (UTC)<br />
<br />
==Blbej dotaz ke spamu==<br />
Nestačila by dát jen na stránku s vytvořením nového učtu věta do formuláře: Jaké je jméno zakladatele Openmoko?<br />
--[[User:Kukide|Kukide]] 18:48, 3 January 2012 (UTC)<br />
'''(Machine) translation:'''<br />
Stupid question to spam<br />
Enough to give only the page with the creation of new account forms the sentence:<br />
'What is the name of the founder of Openmoko?'<br />
''--[[User:Kukide|Kukide]] 18:48, 3 January 2012 (UTC)''</div>Vanoushttp://openmoko.org/wiki/User_talk:VanousUser talk:Vanous2011-11-19T08:58:44Z<p>Vanous: /* Combat web-spam */</p>
<hr />
<div>Česky prosím. :)<br />
<br />
==SHR manual: link to simple-agent==<br />
<br />
Hi! Thanks for updating the SHR Manual! Great job! <br />
<br />
I just noticed that you pointed out problems with the download of simple-agent. I tried the download link at this page and it's working fine for me - So I have removed your notice about an incorrect link. Furthermore I have added another link to a download from kernel.org. So I think we could delete the page [[simple-agent]] again. Is that okay for you ? --[[User:Marko Knöbl|Marko Knöbl]] 13:39, 21 February 2010 (UTC)<br />
<br />
: Hi Marko, yes, it seems to work now, when i tried last night the page didn't exist. Yes, simple-agent page can be deleted :) --[[User:Vanous|Vanous]] 13:44, 21 February 2010 (UTC)<br />
<br />
==Countless spam==<br />
Hi! Please do something against this countless spam attacks. I have already marked a lot pages as spam (cleared content), that spammer Marshall Nielsen may require your attention. :) --[[User:Quix0r|Quix0r]] 09:13, 31 July 2011 (UTC)<br />
<br />
: see my reply: http://wiki.openmoko.org/wiki/User_talk:Quix0r --[[User:Vanous|vanous]] 13:39, 31 July 2011 (UTC)<br />
:: more spam to delete and accounts to block: http://wiki.openmoko.org/wiki/Category:Candidates_for_speedy_deletion and it is good to have you back. :) --[[User:Quix0r|Quix0r]] 13:43, 14 September 2011 (UTC)<br />
::: i have been travelling and day job overloaded a bit, i am cleaning the mess little by little... thank you for your spam cleaning!--[[User:Vanous|vanous]] 11:13, 18 September 2011 (UTC)<br />
:::: Can you please check if [[Special:Log/upload|all spambots]] are blocked? --[[User:Quix0r|Quix0r]] 00:08, 29 September 2011 (UTC)<br />
:::::I have looked around, but understand that to block, i would need further permitions. I don't know the MW very well, so perhaps i have missed something obvious...? I block the spammers by name, but ofcourse this doesn't help much, as it is all automated... --[[User:Vanous|vanous]] 18:45, 30 September 2011 (UTC)<br />
<br />
==Combat web-spam==<br />
Please try to make an account on this wiki to see how they combat webspam:<br />
* http://multicopter.org<br />
I assume that after a few anti-web-spams the "are you human"-tests stops.<br />
<br>I think it is [http://multicopter.org/wiki/User_talk:Esden Esden] that has implemented it.<br>Please tell the other web-administrators and web-maintainers/developers about it.<br />
<br>--[[User:Glenn|Glenn]] 07:23, 13 November 2011 (UTC)<br />
<br />
** (re)captcha is one of the ways to go, but it requires admin access... i will try to email the admin. --[[User:Vanous|vanous]] 08:58, 19 November 2011 (UTC)</div>Vanoushttp://openmoko.org/wiki/User_talk:VanousUser talk:Vanous2011-09-30T18:45:06Z<p>Vanous: /* Countless spam */</p>
<hr />
<div>Česky prosím. :)<br />
<br />
==SHR manual: link to simple-agent==<br />
<br />
Hi! Thanks for updating the SHR Manual! Great job! <br />
<br />
I just noticed that you pointed out problems with the download of simple-agent. I tried the download link at this page and it's working fine for me - So I have removed your notice about an incorrect link. Furthermore I have added another link to a download from kernel.org. So I think we could delete the page [[simple-agent]] again. Is that okay for you ? --[[User:Marko Knöbl|Marko Knöbl]] 13:39, 21 February 2010 (UTC)<br />
<br />
: Hi Marko, yes, it seems to work now, when i tried last night the page didn't exist. Yes, simple-agent page can be deleted :) --[[User:Vanous|Vanous]] 13:44, 21 February 2010 (UTC)<br />
<br />
==Countless spam==<br />
Hi! Please do something against this countless spam attacks. I have already marked a lot pages as spam (cleared content), that spammer Marshall Nielsen may require your attention. :) --[[User:Quix0r|Quix0r]] 09:13, 31 July 2011 (UTC)<br />
<br />
: see my reply: http://wiki.openmoko.org/wiki/User_talk:Quix0r --[[User:Vanous|vanous]] 13:39, 31 July 2011 (UTC)<br />
:: more spam to delete and accounts to block: http://wiki.openmoko.org/wiki/Category:Candidates_for_speedy_deletion and it is good to have you back. :) --[[User:Quix0r|Quix0r]] 13:43, 14 September 2011 (UTC)<br />
::: i have been travelling and day job overloaded a bit, i am cleaning the mess little by little... thank you for your spam cleaning!--[[User:Vanous|vanous]] 11:13, 18 September 2011 (UTC)<br />
:::: Can you please check if [[Special:Log/upload|all spambots]] are blocked? --[[User:Quix0r|Quix0r]] 00:08, 29 September 2011 (UTC)<br />
:::::I have looked around, but understand that to block, i would need further permitions. I don't know the MW very well, so perhaps i have missed something obvious...? I block the spammers by name, but ofcourse this doesn't help much, as it is all automated... --[[User:Vanous|vanous]] 18:45, 30 September 2011 (UTC)</div>Vanoushttp://openmoko.org/wiki/GSM_oscillating_between_registered_and_not_registered_aka_1024GSM oscillating between registered and not registered aka 10242011-09-23T13:59:42Z<p>Vanous: Reverted edits by Ularedmond (Talk); changed back to last version by Glenn</p>
<hr />
<div>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]].<br />
<br />
==Description==<br />
Hardware bug #1024 creates a condition when the gsm modem is oscillating between registered / not-registered. 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.<br />
<br />
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.<br />
<br />
Bug trac: http://docs.openmoko.org/trac/ticket/1024<br />
<br />
==Bug detection==<br />
Not every Freerunner suffers this issue. To check if your phone has the bug #1024 please use this test script:<br />
<br />
(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)<br />
<br />
<pre><br />
#!/usr/bin/python<br />
<br />
import dbus<br />
import dbus.glib<br />
import gobject<br />
import datetime<br />
<br />
def onNetworkStatus(status):<br />
if 'cid' in status:<br />
print '[%s] Signal : cid=%s, lac=%s' % (datetime.datetime.now(),status['cid'],status['lac'] )<br />
else:<br />
print 'register first'<br />
<br />
bus = dbus.SystemBus();<br />
<br />
bus.add_signal_receiver(onNetworkStatus,<br />
"Status",<br />
"org.freesmartphone.GSM.Network",<br />
"org.freesmartphone.ogsmd",<br />
"/org/freesmartphone/GSM/Device")<br />
<br />
gobject.threads_init()<br />
dbus.glib.init_threads()<br />
main_loop = gobject.MainLoop()<br />
main_loop.run()<br />
</pre><br />
<br />
<br />
Run it like this:<br />
<br />
root@om-gta02 ~ $ deep-sleep-check.py > dsc.log<br />
<br />
If you have something like this:<br />
<br />
[2009-09-09 12:36:09.189663] Signal : cid=3BB3, lac=0D48<br />
[2009-09-09 12:36:15.088936] Signal : cid=3BB3, lac=0D48<br />
[2009-09-09 12:38:10.442808] Signal : cid=3BB3, lac=0D48<br />
[2009-09-09 12:38:13.020126] Signal : cid=3BB3, lac=0D48<br />
[2009-09-09 12:40:25.772918] Signal : cid=3BB3, lac=0D48<br />
[2009-09-09 12:40:28.620096] Signal : cid=3BB3, lac=0D48<br />
[2009-09-09 12:41:17.557676] Signal : cid=3BB3, lac=0D48<br />
[2009-09-09 12:41:20.404582] Signal : cid=3BB3, lac=0D48<br />
<br />
Then you have the bug (trying to connect to GSM every second). Please note that cid is always the same.<br />
<br />
Correct output might not show any messages or look like this:<br />
<br />
[2009-10-18 07:51:27.107655] Signal : cid=4E91, lac=006A<br />
[2009-10-18 07:52:45.145288] Signal : cid=4E7B, lac=006A<br />
[2009-10-18 07:53:18.218122] Signal : cid=4E91, lac=006A<br />
<br />
You can see the cid changing.<br />
<br />
==Bug detection by fso==<br />
Just use frameworkd with ti_calypso_sleep_mode = 'adaptive' and inspect <br />
the logs. Frameworkd will tell you, when a real recamping exists.<br />
<br />
==Hardware bug fixing==<br />
To perform the hardware update, please check description here:<br />
http://lists.openmoko.org/pipermail/hardware/2009-May/001192.html<br />
http://www.neofundas.blogspot.com/ <br />
<br />
[[Image:1024fix.jpg]]<br />
<br />
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.<br />
<br />
If your fix was successful you can change setting to allow Calypso deep sleep:<br />
<br />
==Enabling/allowing Calypso GSM modem deep sleep==<br />
===FSO2 based distros (SHR, Debian)===<br />
<br />
Edit /etc/freesmartphone/conf/GTA02/fsogsmd.conf <br />
<br />
deep_sleep == "always"<br />
<br />
Then kill fsogsmd and restart fsodeviced or reboot the phone. <br />
<br />
===FSO based distros (SHR, Debian, OM2009...)===<br />
<br />
Edit /etc/frameworkd.conf , it should contain:<br />
<br />
ti_calypso_deep_sleep = always<br />
<br />
Then restart framework or reboot the phone.<br />
<br />
/etc/init.d/frameworkd restart<br />
<br />
<br />
===QT based distos (Qtopia, QTExtended, QTMoko...)===<br />
Since qtmoko v24 you can use program called NeoControl which is installed by default.<br />
<br />
Or you can edit /opt/qtmoko/etc/default/Trolltech/Modem.conf , it should contain:<br />
<br />
[DeepSleep]<br />
Active=always<br />
<br />
Make sure it's also in users directory:<br />
<br />
cp /opt/qtmoko/etc/default/Trolltech/Modem.conf /home/root/Settings/Trolltech/Modem.conf<br />
<br />
And reboot.<br />
<br />
===Hackable:1 (rev.5)===<br />
<br />
As said in http://lists.hackable1.org/pipermail/hackable1-user/2010-January/000718.html and other discussions:<br />
hackable:1 does not use frameworkd but gsmd.<br />
<br />
To enable deep-sleep mode:<br />
<br />
-download and install (or extract)<br />
http://build.hackable1.org/debian/dists/wip/main/binary-armel/gsmd_0.0.2+svn1571-1_armel.deb<br />
-edit /etc/default/gsmd and uncomment the "VENDOR=ti-deepsleep" line: this will add a <br />
"-v ti-deepsleep" to the deamon command line. <br />
-Restart gsmd.<br />
<br />
===Android===<br />
<br />
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.<br />
<br />
==See also==<br />
*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<br />
<br />
[[Category:Neo FreeRunner reworks and mods]]</div>Vanoushttp://openmoko.org/wiki/Om_2007.2Om 2007.22011-09-23T13:59:25Z<p>Vanous: Reverted edits by Ularedmond (Talk); changed back to last version by Glenn</p>
<hr />
<div>{{Languages|Om 2007.2}}<br />
{{OM2007.2}}<br />
{{Distributions|Om 2007.2}}<br />
<br />
'''Om 2007.2''' was the second version of the Openmoko distribution. Development began on 2007-07-26. This distribution is not developed anymore.<br />
<br />
Goals of this version were an improved set of PIM applications, improved theming that fixes a lot of the usability problems of the first generation design, more formalized UI guidelines and a number of changes in the build system. The latter had the goal of introducing more recent software by staying closer in sync with upstream org.openembedded.dev.<br />
<br />
An official announcement was made by Sean Moss-Pultz on August 20:<br />
* http://lists.openmoko.org/pipermail/announce/2007-August/000018.html<br />
<br />
(Initially this was named OM-2008 in SVN but renamed shortly after that.)<br />
<br />
== Known Issues ==<br />
<br />
For the very latest status, see [http://docs.openmoko.org/trac/search?q=2007.2 all tickets with 2007.2] in the bug tracker.<br />
<br />
===Missing Esc key===<br />
<br />
With the default image you can't escape edit mode in vi due to the missing Esc key. You need to [[Switching_Keyboards|install a new on-screen keyboard]], and in order to do this you'll need to set up USB networking first. You can then SSH into the FreeRunner from your computer and use the keyboard on that computer to edit files in vi. <br />
<br />
Alternative on-screen keyboards feature an escape key.<br />
<br />
If you are stuck in vi you can type <tt>:q</tt> or <tt>:q!</tt> to exit without saving, or <tt>ZZ</tt> to save and exit.<br />
<br />
===Missing /, | and > keys===<br />
<br />
These keys are missing from the 0 button. This can be fixed by editing <tt>/etc/multitap-pad/im-multipress.conf</tt>, see [[Switching_Keyboards#Fix_Default| this page]], but unfortunately you need vi, or some other editor to do so. Therefore you need to SSH in and [[Getting_Started_with_your_Neo_FreeRunner#Set_up_USB-based_networking_and_update|set up USB networking]] first.<br />
<br />
Alternative on-screen keyboards should have these characters.<br />
<br />
==="Signature Check Failed" errors when running `opkg update`===<br />
<br />
The signatures are missing from the repository.<br />
<br />
Workaround: If the Packages.gz files are downloading ok you can ignore this error.<br />
After your first <tt>opkg upgrade</tt> you should get these signatures.<br />
<br />
===The SSH / Dropbear connections over the USB link frequently freezes===<br />
<br />
This happens when the phone goes to sleep after a few minutes. To unfreeze, unplug and replug the USB cable. To stop this from happening, press the Power button to get the Power menu, then choose Power Management: Disabled.<br />
<br />
===My device is unresponsive. How do I perform a hard reset?===<br />
<br />
For different boot methods, see [[Booting the Neo FreeRunner]].<br />
<br />
===No GUI for controlling sound volume===<br />
<br />
As of this writing, there is no way to adjust the volume from the screen.<br />
<br />
Workaround:<br />
Run the terminal application or [[USB_Networking|log in via usb]], and run the [[Neo alsamixer]] application. To see all the options, including Mic2, run<br />
:alsamixer -V all<br />
The mixer is simpler than it looks. Use the left and right arrow keys to select "headphone" or "PCM" and use the up and down arrow keys to adjust the volume. You can also adjust your microphone volume with the "mic2" adjustment. Press ESC when finished. Then exit the terminal application or log out of the USB login.<br />
<br />
You may need to update configuration files in <br />
:/usr/share/openmoko/scenarios/ <br />
to make the microphone setting permanent. type<br />
:alsactl -f ''path-to-statefile'' store<br />
to do this.<br />
<br />
The default files are as follows (in /usr/share/openmoko/scenarios/): <br />
:gsmhandset.state<br />
:gsmheadset.state<br />
:gsmspeakerout.state<br />
:headset.state<br />
:stereoout.state<br />
<br />
These correspond to the various Sound Profiles accessible in the Debug Tool under Applications.<br />
<br />
To manually restore one of the state files,<br />
:alsactl -f ''path-to-statefile'' restore<br />
<br />
One way to increase the volume of the microphone is to do the following:<br />
# ssh into your FreeRunner<br />
# vi /usr/share/openmoko/scenarios/gsmhandset.state<br />
# search for "Mic2"<br />
# change to "value 3"<br />
If people report not being able to hear you when you call, then setting the Mic2 value to 2 or 3 should fix that.<br />
<br />
'''Question: I am using headphones but only the right speaker work the left don't work how can I fix this ?'''<br />
<br />
This should be set correctly by restoring gsmheadset.state.<br />
Pull and replug the headset jack to make sure the correct state-file is restored.<br />
To manually control the switch between Speaker and headset:<br />
Start alsamixer, scroll along to the right until you find "Amp Spk" and mute it (m), the sound will then come out from both channels of the <br />
headphones and not out of the speaker.<br />
<br />
== Installing ==<br />
<br />
If you want install this software distribution to your device, you have to follow these steps:<br />
* Download the recent image of Om2007.2 .<br />
* [[Flashing the Neo FreeRunner|Flash]] to your Neo FreeRunner<br />
<br />
[[Image:Openmoko2007.2 home screen.png|thumb|right|home screen of Om 2007.2]]<br />
<br />
==Building 2007.2==<br />
<br />
=== Why to build ===<br />
<br />
Before getting your feet wet, step back a moment and ask yourself why you want to build the Openmoko distribution image. Chances are you are a kernel and application developer and just want to develop on your package -- in that case building Openmoko is completely unnecessary and a waste of time. You may rather want to use the Openmoko [[Toolchain]] and build only the stuff that is interesting to you.<br />
<br />
=== How to build ===<br />
<br />
The MokoMakefile is now able to build Om 2007.2 images. If you use this new version of the MokoMakefile, you can ignore everything below and just continue building Om 2007.2 in the same way that you previously built images (i.e. according to [[MokoMakefile]]). Make sure you set the generation correctly at the top of the file.<br />
<br />
Follow the [http://wiki.openembedded.net/index.php/Getting_Started getting started] steps of OpenEmbedded. It is suggested to use Bitbake 1.8.8 at least.<br />
<br />
{{note|Instead of using '''git.openembedded.net''' (as indicated in OE GettingStarted), please make sure to use '''git://git.openmoko.org/git/openmoko''' as [[MonotoneServer|monotone server]]. This ensures you have a working revision of the metadata and will render a successful build}}<br />
<br />
Put the following in your local.conf<br />
<br />
BBFILES = "${HOME}/oe/org.openembedded.dev/packages/*/*.bb"<br />
<br />
MACHINE = "om-gta01"<br />
DISTRO = "openmoko"<br />
<br />
ENABLE_BINARY_LOCALE_GENERATION = "1"<br />
GLIBC_GENERATE_LOCALES = "en_GB.UTF-8"<br />
<br />
For multi-core machines, the following additions can be used for a speed-up (numbers should be tweaked based on the actual number of cores):<br />
<br />
PARALLEL_MAKE = "-j 4"<br />
BB_NUMBER_THREADS = "4"<br />
<br />
To free disk space after builds, add:<br />
<br />
INHERIT += "rm_work"<br />
<br />
Replace "${HOME}/oe" with the path to where your "org.openembedded.dev" folder lives. For the other entries have a look at ''conf/local.conf.sample'' about their meaning.<br />
<br />
Run ''bitbake <package name>'' (e.g. openmoko-devel-image).<br />
<br />
=== How to enable autorev ===<br />
<br />
First apply the following patch to bitbake.<br />
<br />
http://lists.linuxtogo.org/pipermail/openembedded-devel/2007-September/003035.html<br />
<br />
Add the following line to your local.conf<br />
<br />
require conf/distro/include/moko-autorev.inc<br />
<br />
Then run bitbake as normal. Openmoko will now build with latest SVN checkouts.<br />
<br />
=== Build issues ===<br />
<br />
==== Wrong certificate ====<br />
You may get something like this while the bitbake recipes are parsed:<br />
<br />
Error validating server certificate for 'https://libw100.svn.sf.net:443':<br />
- The certificate hostname does not match.<br />
Certificate information:<br />
- Hostname: *.svn.sourceforge.net<br />
- Valid: from Fri, 27 Oct 2006 12:05:58 GMT until Sun, 28 Oct 2007 13:05:58 GMT<br />
- Issuer: Equifax Secure Certificate Authority, Equifax, US<br />
- Fingerprint: f2:6c:fe:bb:82:92:30:09:72:dd:1c:b3:e7:56:69:c7:7a:df:67:3e<br />
<br />
That is an issue in a bitbake file. One should not use the short-name for sourceforge (sf.net) when certificates are only for exact host names. Accept the certificate and everything is fine for now.<br />
<br />
==== openmoko-libs FTBFS ====<br />
Some applications have not been fully modified to build with the new libraries of Openmoko and still need the old-style ''openmoko-libs'' package. ''libmokogsm'' which is needed for ''openmoko-libs'' then fails to build. As a workaround you can remove the not yet ported applications that need ''openmoko-libs'' making it unnecessary itself. To do this edit ''packages/tasks/openmoko-taks.bb'' and find the following lines:<br />
<br />
.<br />
.<br />
.<br />
openmoko-terminal \<br />
matchbox-panel-2 \<br />
matchbox-panel-2-applets \<br />
matchbox-applet-inputmanager \<br />
# openmoko-appmanager \<br />
matchbox-keyboard \<br />
matchbox-stroke \<br />
openmoko-keyboard \<br />
.<br />
.<br />
.<br />
<br />
Now put a hash (''#'') before ''openmoko-terminal'' and ''openmoko-keyboard''. You can verify that ''openmoko-libs'' is not needed any more by issuing ''bitbake -g openmoko-devel-image'' (= creates a dependency graph). There should be no mentioning of ''openmoko-libs'' in the file ''task-depends.dot''. '''Please note that the graphical terminal and the virtual keyboard will be missing now.''' You can still have terminal access by following the [[USB Networking]] guide. For keyboard input in Qemu add the ''-usbdevice keyboard'' switch.<br />
<br />
<br />
==== gtk+ fails building w/ gtkcombobox.c ====<br />
<br />
If you get these errors:<br />
<br />
gtkcombobox.c: In function 'gtk_combo_box_size_request':<br />
gtkcombobox.c:1859: warning: unused variable 'font_desc'<br />
gtkcombobox.c:1858: warning: unused variable 'metrics'<br />
gtkcombobox.c:1857: warning: unused variable 'context'<br />
gtkcombobox.c:1855: warning: unused variable 'arrow_size'<br />
gtkcombobox.c:1854: warning: unused variable 'font_size'<br />
gtkcombobox.c: In function 'gtk_combo_box_size_allocate':<br />
gtkcombobox.c:1962: error: 'arrow_size' undeclared (first use in this function)<br />
gtkcombobox.c:1962: error: (Each undeclared identifier is reported only once<br />
gtkcombobox.c:1962: error: for each function it appears in.)<br />
gtkcombobox.c:1965: error: 'font_desc' undeclared (first use in this function)<br />
gtkcombobox.c:1966: error: 'context' undeclared (first use in this function)<br />
gtkcombobox.c:1967: error: 'metrics' undeclared (first use in this function)<br />
gtkcombobox.c:1969: error: 'font_size' undeclared (first use in this function)<br />
<br />
Go to your /build/tmp/work/fic-gta01-angstrom-linux-gnueabi/gtk+-2.10.14-r3/gtk+-2.10.14/gtk directory, and patch gtkcombobox.c with the following:<br />
<br />
Thanks to rmoravcik in #openmoko (patch was taken from http://pastebin.ca/654717 )<br />
<br />
--- gtkcombobox.c 2007-08-12 20:30:07.000000000 +0200<br />
+++ gtkcombobox.c 2007-08-12 20:29:58.000000000 +0200<br />
@@ -1948,6 +1948,12 @@<br />
gtk_combo_box_size_allocate (GtkWidget *widget,<br />
GtkAllocation *allocation)<br />
{<br />
+ gint font_size;<br />
+ gint arrow_size;<br />
+ PangoContext *context;<br />
+ PangoFontMetrics *metrics;<br />
+ PangoFontDescription *font_desc;<br />
+<br />
GtkComboBox *combo_box = GTK_COMBO_BOX (widget);<br />
gint focus_width, focus_pad;<br />
GtkAllocation child;<br />
<br />
<br />
==== Building glibc fails with a segfault in QEMU ====<br />
<br />
If your build aborts and you see something like this:<br />
<br />
NOTE: package glibc-2.5: started<br />
NOTE: package glibc-2.5-r6: task do_package: started<br />
NOTE: preparing tree for binary locale generation<br />
NOTE: generating locale en_US (UTF-8)<br />
qemu: uncaught target signal 11 (Segmentation fault) - exiting<br />
<br />
...<br />
<br />
NOTE: Tasks Summary: Attempted 271 tasks of which 0 didn't need to be rerun and 1 failed.<br />
ERROR: '/home/moko/oe/org.openembedded.dev/packages/glibc/glibc_2.5.bb' failed<br />
<br />
Try editing your local.conf file. Change:<br />
<br />
ENABLE_BINARY_LOCALE_GENERATION = "1"<br />
<br />
to<br />
<br />
ENABLE_BINARY_LOCALE_GENERATION = "0"<br />
<br />
and restart the build. This may have some effect on internationalization (you will see a warning indicating that), but at least the build will continue. Thanks to rwhitby for the tip.<br />
<br />
Alternatively, as suggested by XorA in #openmoko, if you are running a 64-bit host distribution, try forcing a different QEMU rev, also in local.conf:<br />
<br />
PREFERRED_VERSION_qemu-native = "0.9.0+cvs20070701"<br />
SRCDATE_qemu-native = 20070701<br />
<br />
<br />
==== libxml2-native fails with xmlCatalogPtr errors ====<br />
<br />
Go to your build/tmp/work/i686-linux/libxml2-native-2.6.29-r1/libxml2-2.6.29/include/libxml/ directory and patch xmlversion.h with the following:<br />
<br />
--- xmlversion.h 2007-08-17 10:45:42.000000000 +0100<br />
+++ xmlversion.h 2007-08-17 10:51:36.000000000 +0100<br />
@@ -219,7 +219,7 @@<br />
*<br />
* Whether the Catalog support is configured in<br />
*/<br />
-#if 0<br />
+#if 1<br />
#define LIBXML_CATALOG_ENABLED<br />
#endif<br />
<br />
On my system the libxml2-native-2.6.29-r1 directory is in a directory named i686-linux, yours may be different. I believe this patch to be a workaround to make libxml2-native build. I am not yet sure what the consequences of enabling XML catalogue support are.<br />
<br />
== Updating your image ==<br />
<br />
'''REVIEW this section - buildhost is down, replaced. '''<br />
<br />
Now that you have a functional 2007.2 image on your Neo, you will want to keep it updated. Fortunately, ipkg is already set up to pull updated packages from the Openmoko buildhost.<br />
<br />
On the phone, in the terminal (or via ssh), if you have a live internet connection and DNS resolution set up in /etc/resolv.conf:<br />
<br />
ipkg update && ipkg upgrade<br />
<br />
will bring your installed packages up to the most recent versions. Also have a look at alternative/additional ipkg sources at [[download]].<br />
<br />
If you are also building your own images and packages, you can also run a simple httpd on your build host and serve your own ipkg files to the Neo.<br />
<br />
On the build host, for example:<br />
<br />
thttpd -d <path_to_moko/tmp/deploy/glibc/ipk> -p 8080<br />
<br />
will serve your packages on port 8080.<br />
<br />
Then, on the neo, make a new file at /etc/ipkg/local-feed.conf with these contents:<br />
<br />
src/gz local-all http://192.168.0.200:8080/all<br />
src/gz local-armv4t http://192.168.0.200:8080/armv4t<br />
src/gz local-om-gta01 http://192.168.0.200:8080/om-gta01<br />
<br />
and ipkg on the Neo (update-upgrade) will pick up files from your local build host's repository (assuming its IP address is 192.168.0.200, as is default in the [[USB Networking]] setup) in addition to the openmoko buildhost.<br />
<br />
Or better yet, change the 192.168.0.200:8080 addresses above to the eth0 IP address of your build machine (instead of the usb0 IP address), and then you can access your local repository with your Neo plugged into any machine on your local net, or even via bluetooth.<br />
<br />
Also if you are building your own packages or packages from the OE database that aren't part of Openmoko by default, you can install those packages as follows.<br />
<br />
On the build host:<br />
<br />
bitbake <name_of_package><br />
bitbake -crebuild package-index<br />
<br />
Then on the Neo:<br />
<br />
ipkg update<br />
ipkg install <name_of_package><br />
<br />
The new package might not show up in the program menu until you reboot or restart X.<br />
<br />
==FAQ==<br />
=== Q: What are differences between 2007.1 and 2007.2? ===<br />
<br />
* UI redesigned for small and recessed screen<br />
* Simplified visuals for performance<br />
* Simplified UI<br />
* More interactions including finger scrolling<br />
* openmoko-today rewritten; works as application launcher and task manager as well<br />
* neod takes care of basic powermanagement, supports AUX and POWER buttons for navigation / additional functionality<br />
* Updated upstream packages<br />
<br />
=== Q: Where to get snapshot images? ===<br />
<br />
* See [[Download]]<br />
<br />
=== Q: My mrxvt (terminal) fonts are huge. ===<br />
<br />
Edit src/feature.h to set MIN_XFT_FONT_SIZE to lower value:<br />
#define MIN_XFT_FONT_SIZE (2)<br />
and rebuild mrxvt & openmoko-devel-image.<br />
<br />
End edit /etc/mrxvt/mrxvt.conf<br />
Mrxvt.xftSize: 4<br />
Mrxvt.xftHint: 1<br />
<br />
{{Languages|Om 2007.2}}<br />
<br />
[[Category:Om 2007.2| ]]</div>Vanoushttp://openmoko.org/wiki/User_talk:Quix0rUser talk:Quix0r2011-09-18T11:25:12Z<p>Vanous: /* Spam on wiki */</p>
<hr />
<div>Something to say to me?<br />
<br />
== reverted changes ==<br />
<br />
http://wiki.openmoko.org/wiki/Template:Works_on_GameRunner<br />
<br />
Of course this is template, what's the problem in changing it?<br />
<br />
Had anybody made GameRunner work on Neo1973? Apparently not. I tryed, with different kernels and I didn't manage to make it work. So? What else should be considered as the fact it doesn't work on 1973? Of course it "could" work if I modified the distribution, but no one did yet. So now it does NOT work on Neo1973.<br />
<br />
--[[User:Ivosh|Ivosh]] 06:46, 8 July 2011 (UTC)<br />
: My idea was to keep templates generic, but okay, maybe this is to very generic. :) Just (again) undo my revert if you feel more comfortable with your idea.--[[User:Quix0r|Quix0r]] 07:33, 8 July 2011 (UTC)<br />
<br />
== Spam on wiki ==<br />
<br />
Hi,<br />
<br />
i have been out on holidays, but have deleted all marked as spam now + blocked the user. i cannot do anything more, as this exceeds my permitions.... so we just keep on watching and cleaning... :( thank you for all your work!<br />
<br />
kind regards<br />
--[[User:Vanous|vanous]] 13:07, 31 July 2011 (UTC)<br />
<br />
:: spam erased, thanks a bunch for watching and marking as spam!--[[User:Vanous|vanous]] 11:25, 18 September 2011 (UTC)</div>Vanoushttp://openmoko.org/wiki/User_talk:VanousUser talk:Vanous2011-09-18T11:13:57Z<p>Vanous: /* Countless spam */</p>
<hr />
<div>Česky prosím. :)<br />
<br />
==SHR manual: link to simple-agent==<br />
<br />
Hi! Thanks for updating the SHR Manual! Great job! <br />
<br />
I just noticed that you pointed out problems with the download of simple-agent. I tried the download link at this page and it's working fine for me - So I have removed your notice about an incorrect link. Furthermore I have added another link to a download from kernel.org. So I think we could delete the page [[simple-agent]] again. Is that okay for you ? --[[User:Marko Knöbl|Marko Knöbl]] 13:39, 21 February 2010 (UTC)<br />
<br />
: Hi Marko, yes, it seems to work now, when i tried last night the page didn't exist. Yes, simple-agent page can be deleted :) --[[User:Vanous|Vanous]] 13:44, 21 February 2010 (UTC)<br />
<br />
==Countless spam==<br />
Hi! Please do something against this countless spam attacks. I have already marked a lot pages as spam (cleared content), that spammer Marshall Nielsen may require your attention. :) --[[User:Quix0r|Quix0r]] 09:13, 31 July 2011 (UTC)<br />
<br />
: see my reply: http://wiki.openmoko.org/wiki/User_talk:Quix0r --[[User:Vanous|vanous]] 13:39, 31 July 2011 (UTC)<br />
:: more spam to delete and accounts to block: http://wiki.openmoko.org/wiki/Category:Candidates_for_speedy_deletion and it is good to have you back. :) --[[User:Quix0r|Quix0r]] 13:43, 14 September 2011 (UTC)<br />
::: i have been travelling and day job overloaded a bit, i am cleaning the mess little by little... thank you for your spam cleaning!--[[User:Vanous|vanous]] 11:13, 18 September 2011 (UTC)</div>Vanoushttp://openmoko.org/wiki/Manuals/SHRManuals/SHR2011-09-14T07:42:05Z<p>Vanous: Reverted edits by Xadmin (Talk); changed back to last version by Sharwin F</p>
<hr />
<div>{{Languages|Manuals/SHR}}<br />
{| align="right"<br />
| __TOC__<br />
|}<br />
<br />
==SHR Introduction==<br />
<br />
Welcome to '''[[SHR]]''', a community driven distribution for (not only) Openmoko, HTC Dream, PalmPré and Nokia n900 phones.<br />
<br />
<br />
<br />
[[Image:SHR-Logo.png|200px|thumb|center|SHR]]<br />
<br />
'''SHR''' (Stable Hybrid Release) is here to provide you with Root FileSystem images that you can easily install into your device to use as a daily phone and PDA. There are many prepackaged programs available that can be installed upon demand by users, it can also be used by developers as a base image for customized and flavored distribution or release. '''SHR unstable (SHR-U)''' is a testing environment before software gets stabilized and it is the main testing ground for [[FSO]] releases. '''SHR testing (SHR-T)''' images provide as much stability as possible for day-to-day usage. Some users find the SHR-U releases preferable for everyday use. [http://lists.shr-project.org/pipermail/shr-user/2010-September/006187.html]<br />
<br />
==Installation==<br />
Use [[Qi]] as bootloader to avoid [[GPS]] problems on suspend/resume.<br />
Switch off you freerunner (if necessary) and start NOR uBoot by pressing AUX and Power-On at the same time and then start [[dfu-util]] on your computer with the following parameters for GTA2:<br />
# dfu-util -a u-boot -R -D [http://wiki.openmoko.org/wiki/Qi#Download qi-s3c2442-master-hist_3b8513d8b3d9615e.udfu]<br />
See [[Flashing the Neo FreeRunner]] or [[Flashing the Neo 1973]] for more details on flashing your phone.<br />
<br />
===Getting SHR===<br />
<br />
You need to download two files for your version as above: kernel and root filesystem. Depending whether you will be installing into the internal [[NAND memory]] or on the [[microSD]] card, you need to either get .jffs2 file for NAND or .tar.gz file for microSD.<br />
<br />
- Get the latest kernel from the below linkpages. Starts with uImage-...<br />
<br />
- Get the root filesystem, for NAND: full-om-gta0_.jffs2, for µSD: full-om-gta0_.tar.gz<br />
<br />
The above are '''full''' images. You can also choose images with less packages, marked as '''lite'''.<br />
<br />
;GTA02 Neo FreeRunner<br />
*testing line: http://build.shr-project.org/shr-testing/images/om-gta02/<br />
*unstable line: http://build.shr-project.org/shr-unstable/images/om-gta02/<br />
<br />
;GTA01 Neo 1973<br />
*testing line: http://build.shr-project.org/shr-testing/images/om-gta01/<br />
*unstable line: http://build.shr-project.org/shr-unstable/images/om-gta01/<br />
<br />
;Image lite to image full<br />
If you flashed a '''lite''' image and want to upgrade to the '''full''' image run:<br />
<br />
opkg update<br />
opkg install task-shr-apps task-shr-games task-shr-gtk<br />
<br />
;Kernel modules<br />
The images of the filesystems mentioned above (.jffs2, .tar.gz), already contain the newest kernel modules.<br />
<br />
Get the new kernel modules if you only want to flash a new kernel, but not a whole new file system. From the same page as the kernel download the modules to match your kernel (their dates should be the same). Use sftp to put that file on the FreeRunner via the usb connection. Run gzip to unwrap the modules:<br />
# gzip -dc modules-...tar.gz | tar -xf - -C /<br />
<br />
===Installation on Flash===<br />
<br />
In order to install your SHR distribution directly to your FreeRunner Flash memory (NAND), you need to get the desired filesystem file ( <tt>.jffs2</tt> ) as described above and flash your device using the <tt>dfu-util</tt> tool.<br />
<br />
Please visit [[Flashing the Neo FreeRunner]] for more details about flashing and see [[Dfu-util]] for detailed information about the dfu-util.<br />
<br />
{{Note|Your battery must be charged (sufficiently) before NAND flashing. Symptom of insufficient charge: Your progress bar "####" stops while flashing. If so, you must charge, and later you should be able to make the complete flash.}}<br />
Commands to flash the filesystem and the kernel:<br />
<br />
for the GTA02 Neo FreeRunner:<br />
<br />
# dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D full-om-gta02.jffs2<br />
# dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-om-gta02-latest.bin<br />
<br />
for the GTA01 Neo 1973:<br />
<br />
# dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a rootfs -R -D full-om-gta01.jffs2<br />
# dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a kernel -R -D uImage-om-gta01-latest.bin<br />
<br />
===Installation on the microSD Card===<br />
<br />
Installing SHR on your microSD Card depends on the Bootloader you are using, ''uBoot'' or ''Qi''.<br />
<br />
In simple words, the difference between both systems resides on how you must prepare your microSD Card and files you use to fill them:<br />
==== uBoot and SHR on microSD Card ====<br />
If you use ''uBoot'', you need to create two partitions. First partition, not so big, in FAT16 or ext2 where you have to place the kernel file (<tt>uImage-om-gta02-latest.bin</tt>) and second partition in ext2 or ext3 where you have to uncompress the filesystem file (<tt>shr-image-om-gta02.tar.gz</tt>).<br />
<br />
==== Qi and SHR on microSD Card ====<br />
If you use ''[[Qi]]'', you only need an ext2 partition (e.g. with [[fdisk]]) into your µSD Card.<br />
# mkfs.ext2 /dev/sde1<br />
If your µSD Card drive has the device name <tt>/dev/sde1</tt>.<br />
Download <tt>[http://build.shr-project.org/shr-testing/images/om-gta02/ shr-image-om-gta02.tar.gz]</tt>.<br />
Uncompress the filesystem image file (<tt>[http://build.shr-project.org/shr-testing/images/om-gta02/ shr-image-om-gta02.tar.gz]</tt>) on the µSD Card (e.g. with a µSD-SD-Card-Adapter on your Linux Desktop Computer. Insert the µSD Card back into your Freerunner and boot your Neo.<br />
<br />
In this case Qi Bootloader is going to look for the kernel image into the <tt>/boot</tt> directory for file named <tt>uImage-GTA02.bin</tt> .<br />
<br />
===Bootloaders===<br />
<br />
Make sure you have recent and correct versions of [[Booting_from_SD | uBoot]] or [[Qi]] installed, please visit the links for detailed information and tips. For example [[Android]] uses modified [[Qi]] which can cause you troubles when using SHR.<br />
<br />
===SHR version===<br />
<br />
Should you ever later wonder what version of SHR you have actually installed, please run<br />
<br />
timestamp of image creation:<br />
cat /etc/timestamp<br />
<br />
latest shr version from opkg upgrade (this version is changed everytime someone builds task-base on shr buildhost):<br />
cat /etc/shr-version<br />
<br />
{{Note|Please note that this is true only for shr-u, with shr-t running opkg update;opkg upgrade does not change the SHR version. Only flashing or a new image download can change the SHR version. But this will be also merged to shr-t later.}}<br />
<br />
==Running SHR==<br />
<br />
===First boot===<br />
[[Image:Shr-boot-preview.png|200px|thumb|center|SHR Boot Splash screen]]<br />
<br />
First boot usually takes a bit longer as your phone's new software needs to do some initial setting up. It is recommended to reboot after this first boot (and after the initial setup), to make sure that all packages get initialized properly. The application switching shelve (shr_elm_softkey) doesn't show up during first boot when the initial wizards are at work, [http://shr-project.org/trac/ticket/1105 reboot is required] and then application switching works as expected.<br />
<br />
====Initial Setup====<br />
<br />
During the first run, Setup is automatically initiated to walk the user through basic setup of the Enlightenment desktop environment. These steps vary as both Enlightenment desktop and SHR evolve, at this point preferred language and desktop profile options are available. The Profile offers to choose a preconfigured way of displaying the desktop. Illume2-SHR (with continuous development) and Illume-SHR (discontinued) profiles are available. '''Illume2-SHR''' is the recommended Profile. <br />
<br />
{| class="wikitable"<br />
| [[Image:SHR-Setup-Language.png|200px|thumb|language selection]]<br />
| [[Image:SHR-Setup-Profile.png|200px|thumb|theme selection]]<br />
| [[Image:SHR-Wizard.png|200px|thumb|SHR Wizard]]<br />
<br />
|}<br />
<br />
Note, you may need to ssh into the device and run /usr/bin/xinput_calibrator_once.sh if calibration is wrong. I found this using a Neo1973 and SHR images from around May 2010.<br />
<br />
====SHR Wizard====<br />
After the initial Setup, SHR Setting Wizard is launched to allow setting up your local phone settings and setting up root password. Sometimes a '''Please wait''' message is displayed for a long time, as the wizzard is waiting for the SIM card to be initialized.<br />
<br />
===First look===<br />
[[Image:SHR-First-Look.png|200px|thumb|Desktop screen]]<br />
[[Image:SHR-Task-Buttons.png|200px|thumb|Task switch buttons]]<br />
====Illume desktop====<br />
Illume desktop is the default home screen of the SHR desktop. <br />
<br />
Application definition files located in /usr/share/applications are displayed here as icons. All applications are ran fullscreen and you can switch between them by using the the '''< left''' or '''right >''' arrows on sliding shelve available by tapping Top Shelf on any empty space. To close applications, choose '''X''' from the same sliding shelve.<br />
<br />
Several icons (e-gadgets) are placed in the Top Shelve:<br />
<br />
The '''L''' icon is to switch between left/right mouse click. By taping this icon the icon gets changed to R and next tap will be as right click. After the click, the behavior is automatically switched back to Left click so any following taps are left click again.<br />
<br />
'''Mode Switch Icon''' allows to split the screen horizontally or vertically, thus allowing to display two applications at the same time.<br />
<br />
'''Keyboard icon''' pops up or hides the Keyboard.<br />
<br />
'''Illume Settings''' icon (represented by SHR logo) invokes the [[#Illume_settings | Illume desktop settings]]. <br />
<br />
'''Home Icon''' allows quick go to the home desktop/application.<br />
<br />
'''GSM''' and '''Battery''' status icons, as well as '''time''' are displayed by default, Bluetooth and WiFi status icons available in the setting of the Top Shelve content.<br />
<br />
<br />
To '''reconfigure the Top Shelve''' itself, use the L/R click icon to Right click on the Top Panel and choose: Illume Indicator->Set Content to add or remove items from the Top Panel. Or, upon right click on the Top Panel you can also choose Illume Indicator->Begin Move/Resize to move your icons around. To escape this mode, you must click on the L/R gadget's edge, it will switch to L, then choose R again, right click on the Top Panel and select Illume Indicator->Stop Move/Resize.<br />
<br />
<br />
====Keyboard====<br />
<br />
Keyboard comes up automagically when a text field is tapped or you can also toggle the keyboard by it's icon in the Top Shelve. In the Keyboard, dictionary switcher is the arrow-up on left side, alternative keyboard layouts are under the ABC button on the right. The Default keyboard has English dictionary enabled. For Space quick slide left-to-right, for Enter, quick slide up-down, to quick change keyboard layout quick slide down-up. While typing with a dictionary enabled keyboard, possible word options start appearing in the keyboard's upper part or more word options are available under the arrow-up on the left. When happy with the word, tap it, it will be pasted into the text field with a space attached. The Keyboard and dictionary can [[#Illume_keyboard_and_dictionaries | easily be localized]].<br />
<br />
Problem with external USB keyboard mapping (arrows keys doesn't work) can be solved with [http://wiki.openmoko.org/wiki/Usb_keyboard#Arrow_keys_disfunction this little script].<br />
<br />
====Copy and Paste====<br />
<br />
In '''E based''' applications, for example the phone suite (contacts, messages...), by tapping and holding down for over two seconds the Select-Paste menu will pop up. By pressing Select, you can now swipe through the text to select desirable part. Tap and hold down again, Copy-Cut-Cancel menu will appear to Copy to clipboard. Another long tap will provide Select-Paste for Paste.<br />
<br />
In '''Gtk''' based application, you can use keyboard for Ctrl-C (Copy) and Ctrl-V (Paste) or items in Menu if provided.<br />
<br />
In the Vala '''Terminal''', you can select simply by swiping through the text and for Paste there is an icon in the menu bar of this application.<br />
<br />
Copy & Paste between different toolkits has some limitations. See the table below. In Ventura, select is possible, but copy/paste doesn't seem to work at all.<br />
<br />
{| cellspacing="0" class="wikitable" border="1" style="font-size: 85%; text-align: left;width="100%"<br />
|-<br />
! From -> To <br />
! to GTK<br />
! to E<br />
! to Terminal<br />
|-<br />
| from GTK<br />
|style="background:#88FF88;"|Works<br />
|style="background:#88FF88;"|Works<br />
|style="background:red"|Doesn't work <br />
|-<br />
| from E<br />
|style="background:red"|Doesn't work <br />
|style="background:#88FF88;"|Works <br />
|style="background:#88FF88;"|Works<br />
|-<br />
| from Terminal<br />
|style="background:red"|Doesn't work <br />
|style="background:#88FF88;"|Works <br />
|style="background:#88FF88;"|Works<br />
|-<br />
|}<br />
<br />
====Alarm====<br />
<br />
The Alarms application (installed by default) allows alarm presetting for single or repeatable alarms. If you set an alarm and turn your Openmoko FreeRunner off, at the time of the alarm the phone will be powered up and alarm will sound.<br />
<br />
====Phone applications====<br />
<br />
Besides other software, SHR comes with 4 main phone applications: ''Dialer'', ''Contacts'', ''Messages'' and ''Phone log''.<br />
<br />
{|<br />
| [[Image:SHR-Dialer.png|200px|thumb|Dialer]]<br />
| [[Image:SHR-Contacts.png|200px|thumb|Contacts]]<br />
| [[Image:SHR-Mesages.png|200px|thumb|Messages]]<br />
| [[Image:SHR-Phonelog.png|200px|thumb|Phone log]]<br />
|}<br />
<br />
<br />
=====PIM data=====<br />
<br />
======Storage======<br />
PIM data (contacts, messages etc.) are stored through internal opimd storage mechanism into <br />
<br />
/etc/freesmartphone/opim/pim.db<br />
<br />
This database can easily be copied from one SHR installation to another, for example due to a need for reflashing. The Contacts application can display a picture of the contact. As the pim.db database contains a path to the picture files only but not the pictures themselves, therefore, in case of PIM data backup or transfer, these picture files '''need to be copied too'''.<br />
<br />
======SIM Contacts======<br />
<br />
SHR phone applications do not read SIM contacts by default but you can use SIM Manager to access your SIM contacts '''SHR Settings -> Others -> SIM Manager''', which allows you to edit and import the SIM contacts into the internal storage. You can also use Pisi to import your SIM contacts into opimd.<br />
<br />
======Synchronization======<br />
<br />
'''[[Pisi]]''' is an application for synchronizing PIM data and can be used for import and export your contacts, calendar entries etc. between various sources, like VCF, LDAP, Google and more. To install Pisi:<br />
<br />
opkg install pisi<br />
<br />
After installation, edit Pisi configuration in '''.pisi/conf''' in your home directory. To have a correct opimd fields support, make sure '''field_support=TRUE''' is enabled in opimd section.<br />
<br />
With the installed package you have a well-documented sample that is placed at <br />
/usr/share/doc/pisi/conf.example<br />
You may copy the file and rename this file to<br />
/home/root/.pisi/conf<br />
as a starting point - then edit this file in order to configure your PIM synchronization data sources. Look at section<br />
<br />
[opimd]<br />
description=OPIMD Contacts<br />
module=contacts_opimd<br />
field_support=TRUE<br />
<br />
=====Idle screen=====<br />
[[Image:SHR-Idle_Screen.png|200px|thumb|Idle Screen with GSM operator strength and name. GPS, WiFi, Display and CPU are requested, Battery status.]]<br />
Upon press of the AUX button Idle Screens locks up the display. AUX press or a finger slide on the Slider unlocks the screen.<br />
<br />
At the top, status icons are shown to indicate what is going on in the phone:<br />
<br />
From left to right:<br />
GSM strength and operator. Requested Resources (GPS, Display etc., when for example Display is requested, the screen will not dim). Battery capacity.<br />
<br />
====Hardware Buttons====<br />
<br />
=====Power Button=====<br />
<br />
[[Image:SHR-Quick-Settings.png|200px|thumb|Quick Settings]]<br />
<br />
The '''PWR''' (Power) button is mapped to start [[#quick_settings | Quick Settings]] screen (Illume System menu in older versions) on a short press. <br />
<br />
Mapping of the PWR button be configured via the '''Illume Settings-> Input -> Key Bindings'''.<br />
<br />
Pressing the Power button for longer then 8 seconds will force a complete power down of the device. This is hardconfigured in the kernel.<br />
<div id="quick_settings"> </div><br />
The '''Quick Settings''' screen provides several toggles: Airplane mode, Phone profiles, Power settings and Power buttons.<br />
<br />
=====Auxiliary Button=====<br />
The '''AUX''' (Auxiliary) button is mapped to toggle on/off the SHR Idle screen. Mapping of this button is configured in /etc/phonefsod.conf<br />
<br />
idle_screen = aux,lock<br />
<br />
You can configure the [[#idle_screen | Idle Screen]] to come up even during active phone call by adding '''phone''' to the setting: <br />
<br />
idle_screen = aux,lock, phone<br />
<br />
<div id="idle_screen"> </div><br />
The '''Idle Screen''' shows current date and time, missed calls and messages and also what [[#FSO_Resources | FSO resources]] are currently being requested - used.<br />
<br />
======Replacing idle screen======<br />
<br />
If you wish to use the E simple LOCKED screen instead of the SHR Idle Screen, edit '''/etc/phonefsod.conf''' to this:<br />
<br />
# when to show idle screen<br />
# ...<br />
# idle_screen = aux,lock<br />
idle_screen =<br />
<br />
You need to restart phonefsod to make the change happen.<br />
<br />
Also, change key mapping for the AUX button by setting '''Illume Settings''' -> '''Input''' -> '''Key Bindings''', bind the key '''XF86Phone''' to '''Desktop Simple Lock'''<br />
<br />
====Settings applications====<br />
<br />
Many desktop and phone settings are possible to do via graphical interface. [[#SHR_Settings | SHR Settings]] provides access to most common phone personality settings and is accessible by tapping Settings icon on the desktop. [[#Illume_settings | Illume settings]] (and Enlightenment desktop settings) are accessible on Top shelve by tapping the "SHR Logo" icon. Also, FSO and SHR phoneui applications have configuration files in /etc where some of the above mentioned apps write and that can be edited manually.<br />
<br />
===First steps===<br />
<br />
Right after installation and first boot you might want to do a few initial steps like adjusting the call volume and some other tasks.<br />
<br />
====Audio - Call Volume====<br />
<br />
During the first phone call please use the Volume and Mic sliders on the Active Call Screen and adjust them to fit your preferences. The new improved settings will be used for all in/out-going calls thereafter.<br />
<br />
====Network Connection====<br />
<br />
[[#Networking|Establish network connection]] and SSH into your phone. You can establish connection either via USB to your desktop and enable NAT or you can connect through Wifi.<br />
<br />
====Initializing the opkg database====<br />
''Initialize the opkg database'' in order to install some applications from SHR repositories or from other sources, for example [http://opkg.org opkg.org]. While being online, you need to run<br />
<br />
opkg update<br />
<br />
Searching in the opkg database can take a long time. You can speed things up by dumping the database into a file and grepping it through. Do this only once or after every opkg update:<br />
<br />
opkg list > packages.txt<br />
<br />
Then you can search quickly for package name, for example for [[Navit|navit]]:<br />
<br />
grep navit packages.txt<br />
<br />
====SwapSpace====<br />
<br />
When the RAM is used up, applications get killed. This is particularly bad while doing opkg upgrade. Therefore you might want to create a swap space. Read [[SwapSpace]] article or the [http://shr-project.org/trac/wiki/swap swap article on the SHR wiki].<br />
<br />
==Settings==<br />
===SHR Settings===<br />
[[Image:SHR-Settings-main.png|200px|thumb|SHR Settings]]<br />
<br />
SHR Settings is the main setting application of SHR. It provides an easy way of setting up your phone to your liking - from phone related settings, to requesting resources in order to prevent screen dim or suspend (for example while using GPS).<br />
<br />
Please refer to [[#FSO_Resources | this section]] about a better way to manage preventing screen dim or suspend.<br />
<br />
While some settings are persistent over reboots, others are not.<br />
<br />
====Main Screen====<br />
The main screen is divided into eight categories, which contain several modules. Every SHR Settings module has a specified task - for example controlling the GSM antenna power, setting the time etc.<br />
<br />
====Phone====<br />
Here you can set if the GSM antenna is on and if your phone number is shown when you call someone.<br />
<br />
'''GSM'''<br />
In GSM settings you can turn off and on GSM module. After turning off antenna, whole GSM modem is turned off.<br />
<br />
To list available providers, click on Operators button. Scanning can take some time. After a while, a list of operators should pop up.<br />
<br />
You can't connect to operators marked [forbidden].<br />
<br />
Selecting an operator from the list also changes modem registration mode to manual. It won't register to other network, even if some is available and has better signal strengh. To return to automatic mode, click "Automatic" button in operator list.<br />
<br />
'''Call'''<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Phone.png|200px|thumb|Phone settings]]<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-List-providers.png|200px|thumb|List providers]]<br />
<br />
|}<br />
<br />
You can set if your phone number should be displayed to other party. You can either depend on network decision ("By network") or force it manually ("Manual")<br />
<br />
'''Phoneutils'''<br />
<br />
For the default SHR phone applications to be able to correctly parse incoming calls/messages and match them with your contacts, you will need to set the right country code for your location. (for example 420 for Czech republic) for more info, please go to: http://wiki.openmoko.org/wiki/Phone_Prefixes<br />
<br />
'''SIM'''<br />
<br />
Here you can view some informations about your SIM card and clean phone and messagebooks.<br />
<br />
====Profiles====<br />
<br />
Here you can select the current profile, which the device should use to determine ring tone etc.<br />
<br />
'''Current profile'''<br />
<br />
Here you can adjust properties of the currently used profile. <br />
<br />
To change the ring tone, click the "Change" button.<br />
<br />
To use your own ring tone, place it in /usr/share/sounds directory.<br />
<br />
After selecting a sid tune as the ring tone, there are available controls to select tune number from the file.<br />
<br />
If you like to test a .sid you can play it using this command on the FR:<br />
<br />
gst-launch filesrc location=Arkanoid_PSID.sid ! siddec tune=2 ! alsasink<br />
<br />
Note that it's a ! used and not a | to construct the gstreamer pipe command.<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Profiles.png|200px|thumb|Profiles]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Profiles-Ringtones.png|200px|thumb|Ringtones]]<br />
<br />
|}<br />
<br />
====Connectivity====<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Connectivity.png |200px|thumb|Connectivity top]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Connectivity2.png |200px|thumb|Connectivity bottom]]<br />
|}<br />
<br />
'''WiFi'''<br />
<br />
With the "WiFi radio" toggle you can set, if the wifi module is powered. WiFi radio has to be turned on before trying to connect to a WiFi network, unless you try to connect through [[Mokonnect]] which is capable of powering it up.<br />
<br />
'''GPRS'''<br />
<br />
To enter APN, login and password fields, just click on the actual value (default: "internet"). Your phone provider can provide the required configuration options.<br />
<br />
{{Note|You can also use Mokonnect to manage your GPRS connection}}<br />
<br />
'''USB'''<br />
<br />
With this toggle you can switch USB port between device (Neo to PC) or host (device to Neo) modes.<br />
<br />
'''Bluetooth'''<br />
<br />
To power up Bluetooth module, switch the "Bluetooth radio" toggle to "On". After that, the "Visibility" toggle should arrive - set it to "On" if you want your FR to be visible by other Bluetooth devices on scanning.<br />
<br />
====Power====<br />
<br />
'''Battery'''<br />
<br />
This module displays informations about battery state - charge, voltage, remaining time etc. To update the data, click the "Update" button.<br />
<br />
Here you can also force enable 500mA charging.<br />
<br />
'''Display'''<br />
<br />
With this slider you can easily set the backlight brightness.<br />
<br />
{{Note|This setting isn't permanent over sessions. At boot backlight is set back to 80%.}}<br />
<br />
'''Power'''<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Power.png |200px|thumb|Power]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Timeouts.png |200px|thumb|Timeouts]]<br />
|}<br />
<br />
'''Timeouts'''<br />
<br />
Timeouts are reached in this order: Busy state -> idle -> idle dim -> idle prelock -> lock -> suspend. <br />
<br />
{{Note|Storing of this setting via D-bus calls is not supported in the new API of Vala rewrite of FSO2 and therefore SHR Settings doesn't have a functional setting for this.}}<br />
<br />
You can set values of idle timeouts manually. The default parameters are stored in '''/etc/freesmartphone/conf/GTA02/fsodeviced.conf''' but customized '''.fsodeviced.conf''' file in your home directory will take precedence (if it exists, the one in /etc/... will be ignored, so you have to copy the whole file and tweak it):<br />
<br />
[fsodevice.kernel_idle]<br />
suspend = 20<br />
lock = 2<br />
idle_prelock = 12<br />
idle = 10<br />
idle_dim = 20<br />
<br />
To turn off a timeout, set it to -1.<br />
<br />
====Appearance====<br />
<br />
'''Theming'''<br />
[[Image:SHR-Neo-Theme.png|200px|thumb|Neo theme]]<br />
<br />
The Apperance section allows you to change between installed themes. To install more themes, see also [[#Installing themes | Installing themes]].<br />
<br />
You can change finger size - this will mainly effect vertical spacing between widgets.<br />
<br />
Switching between engines:<br />
<br />
E can be switched to use different engines. The default engine is x11. Alternative engine x11-16 is not supported and results in buggy behavior of several applications, for example the phone suite or Ventura browser. It's usage is not recommended.<br />
<br />
Changing system boot Splash screen is also possible in this module. To install more splash screens, see also [[#Installing splash screen themes|Installing splash themes]].<br />
<br />
====Position====<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-GPS.png |200px|thumb|center|GPS]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-GPS-Satelites.png |200px|thumb|GPS Satelite details]]<br />
|}<br />
<br />
'''GPS'''<br />
<br />
By default, GPS is turned on only when requested by an application. That state corresponds to "Auto" setting. After changing to "Manual", you can force set it to on or off.<br />
<br />
'''GPS information'''<br />
<br />
This page can be used to monitor GPS status. You either have to turn GPS on manually or start another application to enable the GPS.<br />
<br />
You can also view information about every visible satellite and check, which are used for getting a fix. To do that, click "Satellite details".<br />
<br />
'''Remove AGPS data'''<br />
If you experience problems with GPS, turn it off, click "Remove AGPS data" and reboot your Neo.<br />
Assisted GPS ([[aGPS]]) support GPS receiver to find position by non-satellite information.<br />
<br />
====Date/time====<br />
<br />
[[Image:SHR-Settings-Date-Time.png |200px|thumb|Date & Time]]<br />
<br />
'''Time'''<br />
<br />
Here you can view and set the time. By default, the time is just displayed, To adjust it, click on "Set time".<br />
<br />
After finishing adjusting, click the "OK" button.<br />
<br />
'''Date'''<br />
<br />
This module displays the current date.<br />
<br />
====Others====<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
[[Image:SHR-Settings-Others.png |200px|thumb|Others]]<br />
<br />
'''PIM'''<br />
<br />
Pim data are stored in opimd domains. Every opimd domain has different backends to store its data to. The domain reads data from every backend and writes data to the default backend. This elector allows you to choose the backend that stores newly generated data, it doesn't copy or move existing data to a different backend.<br />
<br />
'''Services'''<br />
<br />
The services selector is listing scripts from /etc/init.d/ directory.<br />
<br />
After clicking on a servis, you can either start, restart or stop the service and view the result.<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Services.png |200px|thumb|center|Services]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Service-restart.png |200px|thumb|Services debug screen]]<br />
|}<br />
<br />
<br />
'''Userspace backups'''<br />
<br />
Here you can either archive or restore your files and configurations.<br />
<br />
=== Illume settings ===<br />
<br />
The Illume desktop can be easily customized - tap the Settings icon (SHR Logo) on the Top Shelve.<br />
<br />
'''Illume settings''' provides various options to alter the desktop environment. You can change sizes of elements, single or double click, wallpaper. To access all the various options, open Illume Settings and slide the visible icons to the left, to view more options on the right hand side.<br />
<br />
Some setting screens are not resized properly to fit the phone's display - for example the Wallpapper setting. This is a known bug already reported upstream.<br />
<br />
<!-- [[Image:SHR-Top-Shelve.png|200px|thumb|Top Shelf]] --><br />
<br />
==Localization==<br />
<br />
=== Localize SHR manually ===<br />
<br />
[[Image:SHR-Illume-Settings-Languages.png|200px|thumb|Setting Language]]<br />
<br />
====Desktop environment====<br />
<br />
You can change the language of the SHR desktop environment by using the Settings of Illume. For Example, for Czech language: in the Illume top shelf go to Settings (SHR Logo) -> Language -> Language Settings -> and choose: Čeština. If your language is not in the menu you can install by using opkg.<br />
<br />
You can list all available languages by running:<br />
<br />
opkg list | grep eglibc-locale-<br />
<br />
And install the language of your choice (for example czech):<br />
<br />
opkg install eglibc-locale-cs<br />
<br />
After this, the Language Settings of Illume will offer Czech. <br />
<br />
This will localize the Illume environment and will also set correct lang environment variable of your desktop. <br />
<br />
====Applications====<br />
<br />
If you wish to have other applications localized, you need to install translation for each of them (presuming it is available):<br />
<br />
This will install czech localization for SHR phone applications, SHR Settings and TangoGps:<br />
<br />
opkg install libframeworkd-phonegui-efl-locale-cs shr-settings-locale-cs tangogps-locale-cs<br />
<br />
====Terminal environment====<br />
<br />
For localized terminal environment (ssh login) set lang variables in /etc/profile.d/locale.sh, example for Czech language:<br />
<br />
export LANG=cs_CZ<br />
export LC_ALL=cs_CZ<br />
<br />
====Illume keyboard and dictionaries====<br />
[[Image:Illume-keyboards-terminal-dutch-nl-screenshot.png| Dutch terminal virtual keyboard|256px|thumb]]<br />
→ more details on page [[Illume keyboard]]<br />
<br />
Unlike other input methods for mobile devices, the Illume keyboard is corrective rather than predictive. It detects what you mean, even if some letters mistyped. If you accidently hit some keys next to the correct one Illume still recognizes the word. This kind of input method compensates for the small size of the keys. Keep a key pressed for a longer time to affirm you really mean it. <br />
<br />
An English dictionary is used by default. A few dictionaries for other languages are included in the SHR distribution. In addition, every dictionary for [http://en.wikipedia.org/wiki/MySpell myspell] can be used. <br />
<br />
You can install a different keyboard with a layout which fits your language or alternatives for the default keyboards like the numerical one. The localized [[Illume keyboard]]s are available in the SHR repository under the name ''illume-keyboard-LANG''.<br />
<br />
==== German (and Austria) Language ====<br />
<br />
See [[Configure_SHR_for_German-speaking_use]] for detailed customization for german speaking.<br />
<br />
===Date and time===<br />
{{Note|This needs a complete and correct rewrite.}}<br />
<br />
Date and time are automatically set from GPS or Network. The easiest way of setting the time for the first time is to run TangoGps (GPS & Map icon) and obtaining GPS fix. Time will then be set automatically.<br />
<br />
The local timezone is automatically retrieved from the GSM network.<br />
<br />
It is possible to instruct framework on how to set the time and timezone in /etc/frameworkd.conf :<br />
<br />
[otimed]<br />
# a list of time/zone sources to use or NONE<br />
timesources = GPS,NTP<br />
zonesources = GSM<br />
# use an ip address here, otherwise DNS resolution will block<br />
ntpserver = 134.169.172.1<br />
<br />
To disable automatic date/zone settings, simply create an empty [otimed] section in /etc/frameworkd.conf<br />
<br />
Timezone change<br />
<br />
Create a symlink named /etc/localtime which points to the appropriate file in /usr/share/zoneinfo. For example, if you're in France., the following command will link the correct zoneinfo file to your /etc/localtime, giving you the correct time:<br />
<br />
ln -sf /usr/share/zoneinfo/Europe/Paris /etc/localtime<br />
<br />
Afterwards, edit /etc/timezone if necessary [?]<br />
<br />
Local timezone work instantly for the current boot when:<br />
<br />
TZ="Europe/Paris"<br />
export TZ<br />
<br />
For a permanent timezone change edit /etc/profile and change to:<br />
<br />
TZ="Europe/Paris"<br />
<br />
<br />
If you use UTC time, set '''UTC=yes''' in '''/etc/default/rcS'''.<br />
<br />
Adjusting time manually:<br />
<br />
Via SHR-Settings -> Date/time -> Set time<br />
<br />
From the Freerunner console:<br />
<br />
date -s "YYYY-MM-DD hh:mm"<br />
<br />
From linux based desktop:<br />
<br />
ssh root@192.168.0.202 "date -u -s `date -u +%m%d%H%M%Y.%S`"<br />
<br />
The above does NOT work from Ubuntu as of 4/2/2010, the proper format is:<br />
<br />
ssh root@192.168.0.202 "date -u -s `date -u +%Y.%m.%d-%H:%M:%S`"<br />
<br />
Set the hardware clock to the system time:<br />
<br />
hwclock --systohc<br />
<br />
Is this better?:<br />
<br />
hwclock --utc --systohc<br />
<br />
==FSO Resources==<br />
<br />
[[FSO]] is in control of each device. These are called ''resources''. If the software wanting to use the device is capable of requesting this resource via <tt>d-bus</tt>, FSO will do this, otherwise you might need to power the device manually. After the requested resource is released, FSO will power it down. Manual resource request can be done through ''SHR Setting'' or you can use <tt>fsoraw</tt> command. (Using fsoraw is faster and better than running dbus commands)<br />
<br />
opkg install fsoraw<br />
<br />
Example of usage fsoraw:<br />
<br />
fsoraw -r Display mokomaze<br />
<br />
See [[FSO Resources]] for more details on using the following resources:<br />
<br />
'''Wifi'''<br />
<br />
Unless this resource is enabled you've no eth0 and wifi module is completely un-powered. Use the [[Mokonnect]] network manager to set up networks, it will power Wifi up automatically when needed.<br />
<br />
'''Bluetooth'''<br />
<br />
You need to have this resource requested to have bluetooth module powered.<br />
<br />
'''GPS'''<br />
<br />
The fso-gpsd is a daemon waiting for gsmd connections, automatically powering the device on and off. When a connection exists, it powers up the GSM. In SHR Settings you can switch GPS completely off SHR Settings -> GPS -> Manual > Off<br />
<br />
'''GSM'''<br />
<br />
You need to have this resource requested to have GSM module powered.<br />
<br />
'''Display'''<br />
<br />
While this resource is requested the display won't be blanked and suspend is disabled.<br />
<br />
'''CPU'''<br />
<br />
While this resource is requested then suspend is disabled. Display will blank as normal.<br />
<br />
'''Test'''<br />
<br />
A test resource.<br />
<br />
'''UsbHost'''<br />
<br />
While this resource is requested the USB is turned into powered USB Host mode.<br />
<br />
'''Accelerometer'''<br />
<br />
You need to have this resource requested to have the Accelerometer module powered.<br />
<br />
==Networking==<br />
<br />
There are several ways of networking - Wifi, USB, Bluetooth and Gprs:<br />
<br />
===USB===<br />
<br />
By default, USB networking is enabled in <tt>/etc/network/interfaces</tt>, where enhanced configuration can be direct edited. The phone default IP address is 192.168.0.202. Some setup is required on the desktop side, please read [[USB Networking]].<br />
<br />
===WiFi===<br />
<br />
WiFi manager [[iliwi]] is available by default for search/connect/making default a wifi connection. ''iliwi'' uses key only in hex format. The Wifi device is not required to be manually turned on via SHR-Settings as ''iliwi'' will automatically enable the device when needed and disable it after use. iliwi needs to stay running to keep the WiFi connection enabled.<br />
<br />
When WiFi is connected, the Idle screen show the icon of the WiFi resource being occupied.<br />
<br />
===GPRS===<br />
<br />
GPRS Credentials are set during the first run in SHR Wizard and you may edit them at any time via SHR settings or direct editing of /etc/phonefsod.conf. GPRS connection can then be established/closed via SHR Settings or through SHR Quick Settings (available under the Power button). SHR Quick Settings - Network tab allows also connection sharing - this will share the GPRS connection with USB network and run DHCP server to provide the client with an IP address.<br />
<br />
When GPRS is connected, the idle screen shows a small G above the signal strength indicator.<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |<br />
[[Image:SHR-Gprs-Share.png|200px|thumb|GPRS + Connection sharing]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " | <br />
[[Image:SHR-Iliwi-Scan.png|200px|thumb|Iliwi WiFi scanning]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " | <br />
<br />
[[Image:SHR-Iliwi-Connect.png|200px|thumb|Iliwi WiFi connecting]]<br />
<br />
|}<br />
<br />
==Bluetooth==<br />
<br />
Bluetooth can be used for several different applications - file transfer (OBEX), networking, input devices (HIDD), music playing (A2DP), calling etc. In some occasions, the devices need to be authorized - paired. At the moment, support for some bluetooth functions is better than for others - it is possible to do all mentioned above with the notice that phone calls with bluetooth headset are always routed to the bluetooth even if the bluetooth headset is not around, making it quite difficult to use.<br />
<br />
In the SHR repositories are applications ready to be installed (by opkg) that already do provide bluetooth support. This means that they request the bluetooth resource automatically, can search bluetooth devices around, help you with pairing and can perhaps even reconnect bluetooth headset upon resume from suspend. From applications that have some bluetooth support some are for example [[Launcher]] (home screen launcher and phone suite), [[Podboy]] (podcast player), [[Emtooth]] (bluetooth manager). In order to set up bluetooth for phone calls, some manual setup from [[#GSM_phone_calls_with_bluetooth_headset | bellow]] is still required.<br />
<br />
===Bluez3 - the manual non D-Bus way===<br />
<br />
If you want to use the bluetooth device directly, you need to turn the bluetooth radio on in SHR Settings -> Connectivity -> Bluetooth Radio: On. You can also make the bluetooth device visible here.<br />
<br />
====OBEX file transfer====<br />
<br />
There are several obex programs allowing file transfer, all in console at the moment. Obexpush installs obextool, and opd daemon:<br />
<br />
opkg install obexpush<br />
<br />
Default receiving path (editable in /etc/default/opd_args ) does not exist, so create it<br />
<br />
mkdir /var/obexpush<br />
<br />
Files are then received automatically, no notice, no confirmation... they just silently appear in /var/obexpush<br />
<br />
To send some files, first scan for devices:<br />
<br />
hcitool scan<br />
Scanning ...<br />
00:16:41:F5:A5:BC laptop<br />
<br />
Then send the file onto bluetooth address found in the scan:<br />
<br />
obextool push image.jpg 00:16:41:F5:A5:BC 10<br />
<br />
====Connect Bluetooth keyboard====<br />
<br />
hidd --search<br />
<br />
Editors note: This is the old bluez3 way, but it works. New bluez4 way will replace this.<br />
<br />
===Bluez4 - D-Bus based way===<br />
<br />
SHR uses bluez4 which is completely different from bluez3. The bluetoothd is taking care of most of the bluetooth now. Please see [[Manually using Bluetooth]] for detailed information about using bluetooth and also for a list of supported devices.<br />
<br />
====Pairing====<br />
<br />
[[Emtooth]] is a bluetooth manager. It provides setting up bluetooth device name, pairing/unpairing, visibility setting and more. Install Emtooth:<br />
<br />
opkg install emtooth2<br />
<br />
It will discover nearby devices, double tapping on found device will initiate pairing process.<br />
<br />
====GSM with bluetooth headset====<br />
<br />
In order to use bluetooth headset for phone calls, several simple steps need to be done.<br />
<br />
1). Your bluetooth headset device must be [[#Pairing | paired]] first.<br />
<br />
2). [[#Configuring_FSO | Add]] your bluetooth headset into FSO configuration.<br />
<br />
<br />
Please note: phonecalls are now always routed to the bluetooth headset. <br />
After startup and after every resume, the headset needs to be [[#Re-Connecting_the_bluetooth_headset |reconnected]].<br />
<br />
=====Configuring FSO=====<br />
<br />
Now we must tell frameworkd that you have a bluetooth headset. Headset parameters should be set in<br />
<br />
/etc/freesmartphone/opreferences/conf/phone/default.yaml<br />
<br />
Parameters bt-headset-enabled and bt-headset-address (see opreferences/schema/phone.yaml for semantics).<br />
<br />
You need to restart FSO for the changes to take effect.<br />
<br />
# /etc/init.d/frameworkd restart<br />
<br />
example of my /etc/freesmartphone/opreferences/conf/phone/default.yaml:<br />
<br />
message-length: 7<br />
message-tone: notify_message.wav<br />
message-vibration: 1<br />
message-volume: 10<br />
ring-loop: 1<br />
ring-tone: ringtone_ringnroll.wav<br />
ring-vibration: 1<br />
ring-volume: 10<br />
bt-headset-enabled: 1<br />
bt-headset-address: 00:09:DD:31:92:98<br />
<br />
=====Re-Connecting the headset=====<br />
<br />
You might need to get the bluetooth headset connected manually on the beginning and also after suspend:<br />
<br />
mdbus -s org.bluez $BTADAPTER/dev_xx_xx_xx_xx_xx_xx org.bluez.Headset.Connect<br />
<br />
where xx_xx_xx_xx_xx_xx is address of the device, for example:<br />
<br />
mdbus -s org.bluez $BTADAPTER/dev_00_09_DD_31_92_98 org.bluez.Headset.Connect<br />
<br />
Hopefully, your bluetooth headset now works. Good luck!<br />
<br />
==System Customizing==<br />
<br />
===Command scheduling===<br />
<br />
The traditional ''at'' command in ''SHR'' is modified to work over dbus. This modified ''at_over_dbus'' will run scheduled task at required time - actually it will even automatically wake up the phone from suspend or start it if the phone was switched off.<br />
<br />
To schedule a command to be executed at a particular time, one must:<br />
<br />
Place commands in a script in ''/var/spool/at'' and name it like <br />
<br />
TIMESTAMP.NAME.NUMBER<br />
<br />
where<br />
<br />
where TIMESTAMP is the seconds since 1970-01-01 00:00:00 UTC when the command should be run. <br />
The rest (NAME, NUMBER) is up to you. Finally you have to:<br />
<br />
touch /var/spool/at/trigger<br />
<br />
Also, make sure to have atd running. You are responsible to remove the script when unnecessary. It will run once more if you/other program write to the trigger file during the execution, so you may consider removing the<br />
executable flag of the script (if it is long running) or rename the script from within for example like this: <br />
<br />
mv "$0" "x$0.$$"<br />
<br />
===Installing splash screen themes===<br />
<br />
List available splash screen themes<br />
<br />
opkg list | grep splash-theme<br />
<br />
Install one of the available themes<br />
<br />
opkg install shr-splash-theme-dontpanic<br />
<br />
Then go to '''SHR Settings -> Appearance -> Splash settings'''. Here you can preview installed themes and change the default one.<br />
<br />
===Installing themes===<br />
<br />
Every theme is made of several components (a theme for illume, theme for the phone applications, theme for etk and so on). There is a SHR metapackage for each theme that allows installing the complete theme in one go.<br />
<br />
List available SHR theme metapackages:<br />
<br />
opkg list | grep shr-theme<br />
<br />
Install one of the available themes<br />
<br />
opkg install shr-theme-gry<br />
<br />
Then go to '''SHR Settings -> Appearance -> Elementary Settings'''. Here you can preview installed themes and choose the preferred one.<br />
<br />
The Illume screen requires to change theme via '''Settings (SHR Logo) -> Look -> Theme'''. Here you can preview installed themes and choose the preferred one.<br />
<br />
===Enable mouse cursor=== <br />
<br />
edit line 143 of /etc/X11/Xserver and erase '''-nocursor'''<br />
<br />
ARGS="$ARGS"<br />
<br />
<br />
<br />
===Random errors===<br />
No icons, no GSM functions etc. happen mostly due to '''errors on your µSD''' card. Remove your card and fix it in card reader or by booting to another partition (nand) or by reboot and mount read only, then run fsck.<br />
<br />
For reboot into nand and fix 1st partition of ext2 on your card<br />
<br />
fsck.ext2 /dev/mmcblk0p1<br />
<br />
===GSM modem 1024 suspend bug===<br />
<br />
The calypso GSM modem suffers a known [[1024]] hardware bug that causes unreliable GSM function. To work around it, SHR by default doesn't suspend the modem completely. If you have undertaken a fix for this bug you can extend your battery time by enabling the modem to fully suspend when possible.<br />
<br />
Edit the following in file:<br />
<br />
For the new FSO2 edit /etc/freesmartphone/conf/GTA02/fsogsmd.conf <br />
<br />
deep_sleep == "always"<br />
<br />
Then kill fsogsmd and restart fsodeviced - or reboot the phone.<br />
<br />
<br />
For old FSO (frameworks) edit /etc/frameworkd.conf <br />
<br />
ti_calypso_deep_sleep = always<br />
<br />
Then restart framework or reboot the phone.<br />
<br />
==Reporting bugs==<br />
<br />
SHR is a work in progress. If you experience issues, please report them back to SHR. With your report provide relevant logs from<br />
<br />
/var/log/<br />
<br />
To report a bug, please go to http://shr-project.org/trac/report<br />
<br />
Check if the bug is already reported. If not, add a ticket, be as much precise as you can in the title and the description, in what circumstances the issue happened and so on. If bug already exists, see if you can help fixing it by providing some fresh info.<br />
<br />
==More information==<br />
<br />
For SHR home page, source code and other resources, visit:<br />
<br />
* [http://trac.shr-project.org SHR Project Homepage]<br />
* [http://blog.shr-project.org SHR Blog]<br />
* [http://trac.shr-project.org Trac Bugtracker]<br />
* [http://git.shr-project.org Git Sourcecode-repository]<br />
* [http://build.shr-project.org Downloads on buildhost]<br />
* [http://lists.shr-project.org SHR User and Development Mailing Lists]<br />
<br />
==About this manual==<br />
<br />
This manual makes use of the updated SHR-Unstable distribution which means that for example SHR-Testing or not updated SHR-Unstable might behave differently then stated in this manual.<br />
<br />
Please help extending this manual by correcting typos or discussing proposals on the talk page or email <tt>vanous @ penguin . cz</tt>. Thank you.<br />
<br />
[[Category:SHR]]<br />
[[Category:Manuals]]</div>Vanoushttp://openmoko.org/wiki/User_talk:VanousUser talk:Vanous2011-07-31T13:39:25Z<p>Vanous: /* Countless spam */</p>
<hr />
<div>Česky prosím. :)<br />
<br />
==SHR manual: link to simple-agent==<br />
<br />
Hi! Thanks for updating the SHR Manual! Great job! <br />
<br />
I just noticed that you pointed out problems with the download of simple-agent. I tried the download link at this page and it's working fine for me - So I have removed your notice about an incorrect link. Furthermore I have added another link to a download from kernel.org. So I think we could delete the page [[simple-agent]] again. Is that okay for you ? --[[User:Marko Knöbl|Marko Knöbl]] 13:39, 21 February 2010 (UTC)<br />
<br />
: Hi Marko, yes, it seems to work now, when i tried last night the page didn't exist. Yes, simple-agent page can be deleted :) --[[User:Vanous|Vanous]] 13:44, 21 February 2010 (UTC)<br />
<br />
==Countless spam==<br />
Hi! Please do something against this countless spam attacks. I have already marked a lot pages as spam (cleared content), that spammer Marshall Nielsen may require your attention. :) --[[User:Quix0r|Quix0r]] 09:13, 31 July 2011 (UTC)<br />
<br />
: see my reply: http://wiki.openmoko.org/wiki/User_talk:Quix0r --[[User:Vanous|vanous]] 13:39, 31 July 2011 (UTC)</div>Vanoushttp://openmoko.org/wiki/User_talk:Quix0rUser talk:Quix0r2011-07-31T13:07:53Z<p>Vanous: /* Spam on wiki */ new section</p>
<hr />
<div>Something to say to me?<br />
<br />
== reverted changes ==<br />
<br />
http://wiki.openmoko.org/wiki/Template:Works_on_GameRunner<br />
<br />
Of course this is template, what's the problem in changing it?<br />
<br />
Had anybody made GameRunner work on Neo1973? Apparently not. I tryed, with different kernels and I didn't manage to make it work. So? What else should be considered as the fact it doesn't work on 1973? Of course it "could" work if I modified the distribution, but no one did yet. So now it does NOT work on Neo1973.<br />
<br />
--[[User:Ivosh|Ivosh]] 06:46, 8 July 2011 (UTC)<br />
: My idea was to keep templates generic, but okay, maybe this is to very generic. :) Just (again) undo my revert if you feel more comfortable with your idea.--[[User:Quix0r|Quix0r]] 07:33, 8 July 2011 (UTC)<br />
<br />
== Spam on wiki ==<br />
<br />
Hi,<br />
<br />
i have been out on holidays, but have deleted all marked as spam now + blocked the user. i cannot do anything more, as this exceeds my permitions.... so we just keep on watching and cleaning... :( thank you for all your work!<br />
<br />
kind regards<br />
--[[User:Vanous|vanous]] 13:07, 31 July 2011 (UTC)</div>Vanoushttp://openmoko.org/wiki/Zagg_Protection_Discount_NumberZagg Protection Discount Number2011-06-29T11:26:51Z<p>Vanous: removing possible spam hidden in a plain link, in case of my mistake, please fix back, thx</p>
<hr />
<div>'''Here a simple page to list all [http://www.zagg.com/invisibleshield/openmoko-neo-freerunner-cases-screen-protectors-covers-skins-shields.php zagg protection] discount codes (20%).''' Get [http://www.codes4discount.com 20-50% OFF] with the latest sales!<br />
'''You can use these numbers when buying [[InvisibleShield]] protectors'''.<br />
<br />
'''Take a discount code from the top when buying your protector.'''<br />
Please edit this page, remove the number you used and add "I used this code" in the "Summary:" field of the edit page. You can mention in the summary if you need to edit the page because you find a code invalid & need to take another.<br />
<br />
'''When adding your discount code to the list please do so sorted by chronological date expiration''' (normally at the bottom).<br />
<br />
(This list should grow quicker than it's used, please add your entries after using)<br />
<br />
50% OFF:<br />
# zdaapjd0 (ZAGG discount code expires Sept 30/found Sept 27)<s><br />
# zdpd1fw9 (ZAGG discount code expires Sept 30/found Sept 23)<br />
# zdwja10z (ZAGG discount code expires Sept 30/found Sept 23)<br />
# zdp6nsnd (ZAGG discount code expires Sept 30/found Sept 23)<br />
# zd3affsd (ZAGG discount code expires Sept 30/found Sept 23)<br />
# zd4apfa4 (ZAGG discount code expires Sept 30/found Sept 23)<br />
# zda3jdbp (ZAGG discount code expires Sept 30/found Sept 23)<br />
# zdsphhef (ZAGG discount code expires Sept 30/found Sept 23)<br />
# zdaxss2q (ZAGG discount code expires Sept 30/found Sept 23)<br />
# zdaspsqa (ZAGG discount code expires Sept 30/found Sept 23)<br />
# zdsphhef (ZAGG discount code expires Sept 30/found Sept 23)<br />
# zds1jf9b (ZAGG discount code expires Sept 30/found Sept 23)<br />
# zdwsapjw (ZAGG discount code expires Sept 30/found Sept 22)<br />
# zdaoqozg (ZAGG discount code expires Sept 30/found Sept 22)<br />
# zdspp73a (ZAGG discount code expires Sept 30/found Sept 22)<br />
# zdaqiikss (ZAGG discount code expires Sept 30/found Sept 22)<br />
# zdsfx8dw (ZAGG discount code expires Sept 30/found Sept 22)<br />
# zd1aa6bs (ZAGG discount code expires Sept ??/found Sept 20)<br />
# zdwnjznb (ZAGG discount code expires Sept ??/found Sept 20)<br />
# zdwnjwfd (ZAGG discount code expires Sept ??/found Sept 20)<br />
# zdyhccq39 (ZAGG discount code expires Sept ??/found Sept 20)<br />
# zdfcv5aq (ZAGG discount code expires Sept ??/found Sept 20)<br />
# zdahhsjfg (ZAGG discount code expires Sept ??/found Sept 20)<br />
# zdaxxq56s (ZAGG discount code expires Sept ??/found Sept 20)<br />
# zdzdd1b7 (ZAGG discount code expires Sept ??/found Sept 20)<br />
# zdwbf6fz (ZAGG discount code expires Sept 30/found Sept 16)<br />
# zdwbdj6p (ZAGG discount code expires Sept 30/found Sept 16)<br />
# zdpfdn43 (ZAGG discount code expires Sept 15/found Sept 15)<br />
# zdwazz4b (ZAGG discount code expires Sept 15/found Sept 15)<br />
# idpffja0 (ZAGG discount code expires Sept 15/found Sept 15)<br />
# zdwwp3wn (ZAGG discount code expires Sept 30/found Sept 14)<br />
# zdpa16sp (ZAGG discount code expires Sept 30/found Sept 14)<br />
# zdwfdd7d (ZAGG discount code expires Sept 30/found Sept 13)<br />
# zdp61wwd (ZAGG discount code expires Sept ??/found Sept 13)<br />
# zdwfsdj0 (ZAGG discount code expires Sept ??/found Sept 13)<br />
# zdps6wd3 (ZAGG discount code expires Sept ??/found Sept 13)<br />
# zdpz77aw (ZAGG discount code expires Sept ??/found Sept 13)<br />
# idfs0apa ZAGG discount code expires Sept 15/found Sept 13)<br />
# zdaaqlao (ZAGG discount code expires Sept ??/found Sept 13)<br />
# zdfpplaq (ZAGG discount code expires Sept 15/found Sept 13)<br />
# idfsf4db (ZAGG discount code expires Sept 15/found Sept 13)<br />
# idfs0apa (ZAGG discount code expires Sept 15/found Sept 13)<br />
# zdpz77aw (ZAGG discount code expires Sept 30/found Sept 13)</s><br />
<br />
40% OFF:<br />
* ia7spsb0 (ZAGG discount code expires Aug. 15/found Aug 7)<br />
<br />
30% OFF:<br />
* ian31n3d (ZAGG discount code expires Aug. 15/found Aug 7)<br />
<br />
25% OFF:<br />
* ianajzs0<br />
* ianajzw9<br />
* ia7ajp4z<br />
* ian4jp4j<br />
* ia7dwbsn<br />
* ia7dwbsb<br />
<br />
20% OFF:<br />
* <s>z5h67x (posted on 8 September)</s><br />
* ZAGG20 (end date: unknown, good as of Aug. 7, 2010)<br />
<br />
This one can be reused, and appears to be a 15% discount.<br />
* techound1 (end date: unknown, good as of 25 September, worked at 14 October and Oct 18th and Dec 23rd and Jan 2nd 2009)<br />
<br />
<br />
Daily Discount Codes on Invisible Shield's [http://www.facebook.com/codes4discount Facebook Page] with codes for ongoing 20% savings. <br />
<br />
<br />
Another location for [http://www.codes4discount.com/ daily discount codes] with savings of 20% off! <br />
<br />
[http://www.codes4discount.com/2009/zaggsparq-by-zagg-available-for-pre-order/ ZAGGsparq]: new product by ZAGG for charging USB devices on the go.<br />
<br />
Get instructions and videos for help on how to install invisibleSHIELD [http://www.codes4discount.com/2009/invisible-shield-installation-videos/ here].<br />
<br />
If your discount does not appear in the invoice, ask for it using Zagg's contact web form, and it should be given as a partial refund.<br />
<br />
[http://www.codes4discount.com/2010/weekly-ipad-giveaway-and-10-50-off-zagg-discount-codes/ Enter to win an iPad and get 10-50% off ZAGG discount codes].<br />
<br />
[[Category:Purchase]]</div>Vanoushttp://openmoko.org/wiki/Edit_WikiEdit Wiki2010-12-08T20:22:56Z<p>Vanous: Undo revision 83247 by Trevor75 (Talk)spam</p>
<hr />
<div>{{Languages|Edit Wiki}}<br />
<br />
The Openmoko Wiki is open. YOU can edit its content. People usually start editing a wiki by fixing small things, like obvious grammar and style mistakes. If you spot one, click on the '''edit''' tab, [http://wiki.openmoko.org/index.php?title=Special:Userlogin&type=signup register] by creating an account on the wiki, and you are set up to share and help others. <br />
<br />
Typically, wiki pages start small and grow up organically. Someone fixes a broken reference, another adds a missing item in a list, or updates an outdated paragraph. This is fine, don't worry about being incomplete or about fine-tuning the language. Wiki means "fast" in Hawaïan, so if you have any information to share, go for it !<br />
<br />
If you are extra cautious or want to get familiar with the system, go to the [[Sandbox]] page to try various editing options. <br />
<br />
== How can I help ? ==<br />
<br />
===Update !===<br />
<br />
The most important contribution is to report relevant facts, or fix potentially misleading inaccuracies.<br />
<br />
===Reformat !===<br />
<br />
Good documentation needs logical outlines and conceptual integrity. But wikis are distributed and dynamic, they put forward speed and ease of change instead. This is why serious cleaning and refactoring is regularly needed. Oftentimes, whole pages and even whole pagesets need reorganization. The [[Openmoko Wiki Editing Guidelines]] explain how to write and format text.<br />
<br />
===Translate !===<br />
<br />
You can help by this wiki to other languages. See<br />
<br />
*[[Translation|List of translators]]<br />
*[[Translation HOWTO]]<br />
<br />
===Coordinate !===<br />
<br />
There are many tasks awaiting you listed in the [[Wiki Maintenance Agenda]] and [[Wiki Issues]]. <br />
<br />
If you are interested in helping improve our wiki, please join the [https://lists.openmoko.org/mailman/listinfo/documentation documentation mailing list] to coordinate ideas and work with other wiki editors. Visit [[Wiki Maintainers]] to learn about the wiki maintainers, a team of community volunteers who have committed to working with the Openmoko team to improve the wiki in particular and all documentation in general.<br />
<br />
===Categorize !===<br />
<br />
If you create a new wiki page, an editor should come have a look and put it on the right [[:Category:Categories|category]] (or categories).<br />
<br />
===Tag !===<br />
<br />
[[Templates]] provide a powerful way to annotate pages quickly and visibly. Tag obsolete pages with <pre>{{Delete|Reason why|your name}}</pre> for example.<br />
<br />
===Explore !===<br />
<br />
The 'toolbox' in the left column allows to browse the wiki faster. For example [[Special:Specialpages]] - List and find various content. For the full picture of Openmoko Wiki, please visit the [[Openmoko Wiki Official Index Page|Openmoko Wiki Official Index Page]].<br />
<br />
===Patrol !===<br />
<br />
Patroling is the way to keep the wiki up to date.<br />
* The [http://lists.openmoko.org/mailman/listinfo/ mailing lists] patrols follows the discussions and harvests the glimmering pearls of wisdoms and shining tricks to store on the Wiki (oftentimes, finding that someone else has beaten him/her to it).<br />
* The [[Special:Recentchanges]] patrol checks against vandalism, spam, and questions on the Talk pages.<br />
* The [[Special:Newpages]] patrol gets the pleasure to look early at cool fresh content from the community, categorize it and link to it to integrate it in the information structure.<br />
So far the documentation team has not formally organized patrols.<br />
<br />
== Letter to an interested editor ==<br />
<br />
Hi ***You***,<br />
<br />
Welcome to the documentation team.<br />
<br />
Want to know what is happening in the Wiki this September ?<br />
<br />
Glad you asked. Well, you see, we are storming the place to turn the big disorganized pile of words into a useful (and hopefully someday good looking) reference site. Things have improved a lot already, but the categorization is still being redone (I think a hierarchical approach cannot work well, but that's just me). Meanwhile, we are also learning<br />
how to use Wikimedia (what are templates, namespaces, subpages, how to archive properly etc...) and writing our own guidelines. So it's still starting, you are not late to the party.<br />
<br />
We have not done much on the social organization side. So the governance model, if you may call it as such, is the default one in Open Source. Just add our name to http://wiki.openmoko.org/wiki/Wiki_Maintainers, share viewpoints on the mailing list and use the 'Discussion' pages of the wiki. To the best of my knowledge, we have not anything formal and none of the community members has elevated priviledges. Sysops (wiki administrators) are Brenda (coolcat) and Michael S. both from Openmoko<br />
[http://wiki.openmoko.org/index.php?title=Special%3AListusers&username=&group=sysop&limit=50 and a few others]<br />
, [http://www.mediawiki.org/wiki/Manual:Administrators which means only they can lock or delete pages].<br />
<br />
Traditionally we have left it to Brenda to update the navigation bar templates, after discussing modifications here. So how precisely do you suggest to make it better ?<br />
<br />
As for the big level structure, so far we have been thinking about how to clearly separate user and developper oriented pages, with a half conclusion that we should categorize better (I am not sure how, though. Must check the guidelines. Or convince the others to write them the right way.). I think that the "Key pages" navigation box can potentially give a multi-page narrative story, structure chapters if you prefer.<br />
<br />
http://wiki.openmoko.org/wiki/Om_2008.8<br />
http://wiki.openmoko.org/wiki/FreeRunner_Overview<br />
<br />
I agree that we have too many navigation boxes. IMHO the three on the left column should be revised to two, but see above about the left navigation. I also think that having "Table of content" + "Key pages" + "Language chooser" + the usual wiki header stuff is hard on the eyes of the persons of good typographical taste, but I don't have time to propose and implement a better page layout. If you want ideas on what to do, I would say that giving a more uniform look to all the "Key pages on Om 2008.8" would be an easy, significant and visible contribution.<br />
<br />
As for translation, we have been too busy with content to think about it. I guess we are waiting for the translators to team up themselves and take charge. Here is another exciting task for You !<br />
<br />
Replacing "Main page" with something else is technically beyond the power of wiki editors.<br />
<br />
Yours,<br />
[[User:MinhHaDuong|MinhHaDuong]] 19:16, 2 September 2008 (UTC)<br />
<br />
[[Category:Wiki Editing]]</div>Vanoushttp://openmoko.org/wiki/User_talk:CbladeUser talk:Cblade2010-12-01T19:44:56Z<p>Vanous: </p>
<hr />
<div>hmm, not sure now. If you are a legitimate user, please undo my cleaning.<br />
<br />
thank you<br />
--[[User:Vanous|vanous]] 07:51, 1 December 2010 (UTC)<br />
<br />
== Response ==<br />
<br />
Nice to see that somebody actually takes care of this wiki, nice work!<br />
<br />
*No worries about your FB page, i thought you were a spammer :)<br />
<br />
*--[[User:Vanous|vanous]] 19:44, 1 December 2010 (UTC)</div>Vanoushttp://openmoko.org/wiki/User_talk:CbladeUser talk:Cblade2010-12-01T07:51:38Z<p>Vanous: </p>
<hr />
<div>{{Delete-sp}}<br />
<br />
hmm, not sure now. If you are a legitimate user, please undo my cleaning.<br />
<br />
thank you<br />
--[[User:Vanous|vanous]] 07:51, 1 December 2010 (UTC)</div>Vanoushttp://openmoko.org/wiki/User_talk:CbladeUser talk:Cblade2010-12-01T07:49:24Z<p>Vanous: spam</p>
<hr />
<div>{{Delete-sp}}</div>Vanoushttp://openmoko.org/wiki/User:CbladeUser:Cblade2010-12-01T07:49:09Z<p>Vanous: spam</p>
<hr />
<div>{{Delete-sp}}</div>Vanoushttp://openmoko.org/wiki/Create_User_ManualsCreate User Manuals2010-11-24T18:33:37Z<p>Vanous: Undo revision 82924 by Michellejohnston (Talk) SPAM</p>
<hr />
<div>{{Languages|Create User Manuals}}<br />
Openmoko is a project driven by a community of passionate volunteers. This includes the implementation, testing and improving of the open source code on the one side. On the other side any software is created for the benefit of users and these users are normally not developers. User Maunals like the [[SHR User Manual]] helps people, who are not involved the coding part of the project to use the distributions and applications on the freerunner. User Manuals make it easier for them to get started. Involving people that are not developers could be of benefit for the developers to keep usability in mind so that feedback will be possible for the non-developers at early developing stages. If you are not a developer you have certainly the ability to share, your problems especially with GUIs (Graphical User Interfaces) and discriptions of workflows in installations procedures. Your contributions are extremly welcome to improve the User Manuals itself and in the long run having influence on the software itself. <br />
<br />
Openmoko's ambitions far exceed the resources available, so your contributions as a non developer could be:<br />
* '''Improve existing User Manuals''' like [[SHR User Manual]], when you install the e.g. SHR for the first time and configure SHR on your OpenMoko with the help of the user manual, mention problems with the manual according to your personal installation procedure and if your solved the problem document your solution in this wiki or add a link that . differences in the way.<br />
* '''Add screenshots''' to the manual at the explaintions when images can say more than 1000 words and make it easier for other users to follow the procedure. You can make screenshots on many distributions with <br />
** e.g. [[gpe-scap]] which you can install on your FreeRunner, if it is not installed on you system. <br />
** Download the screenshots from you freerunner with scp or sftp from your desktop computer<br />
** Create a link for images in the wiki edit mode (press ''edit'' in the manual and look for this text in the manual, there you find the link for embedded images) [[Image:Example123.jpg]]. You can click on the link and upload the image to the wiki.<br />
** You can replace images by new ones due to change in graphical user interfaces. The wiki keep track of older versions and replacing an image will not overwrite it.<br />
<br />
'''Remark:''' Please do not upload images to <tt>Example123.jpg</tt> here on this page, so that people can see the results of just inserting an image tag in wiki text without uploading.<br />
<br />
'''Note:'''register as a wiki user by creating an account in the wiki system when want you upload images. Please read the [[Openmoko Wiki Editing Guidelines]] before changing a manual.<br />
<br />
[[Category:Manuals]]<br />
[[Category:Community]]</div>Vanoushttp://openmoko.org/wiki/FAQFAQ2010-10-31T17:02:26Z<p>Vanous: Undo revision 82738 by Valera (Talk)spam</p>
<hr />
<div>{{Languages|FAQ}}<br />
<br />
== Getting Started with your Neo FreeRunner == <!-- Do not rename section! This section is linked from pages which linked to Getting_Started_FAQ. --><br />
<br />
=== I just received my Neo FreeRunner. Where should I start?===<br />
<br />
See [[Getting_Started_with_your_Neo_FreeRunner|Getting Started with your Neo FreeRunner]]<br />
<br />
=== I have a problem or a question. Where should I go? ===<br />
<br />
First place to check is this FAQ. <br />
<br />
If your question isn't answered here, you should search the archives of the [http://lists.openmoko.org/mailman/listinfo/community community] or [http://lists.openmoko.org/mailman/listinfo/support support] mailing lists<br />
<br />
Next, try a larger Google search. <br />
<br />
If you still haven't found the answer to your question, post it on the appropriate list, [http://lists.openmoko.org/mailman/listinfo/community community] or [http://lists.openmoko.org/mailman/listinfo/support support]. <br />
<br />
Provide detailed information about what you are trying to find out, and use<br />
the Subject line to summarize your question. More tips to asking effective<br />
questions can be found<br />
[[http://www.catb.org/~esr/faqs/smart-questions.html|here]]<br />
<br />
If your question requires confidentiality, you are welcome to contact [mailto:michael@openmoko.org Michael Shiloh] directly.<br />
<br />
You might also look for [[Openmoko_Local_Groups|local Openmoko users]] to find<br />
some local support. A few minutes with a live person might solve a simple<br />
misunderstanding that would take hours to understand via email. (If a local<br />
club doesn't exist, this might be the perfect opportunity to start one!)<br />
<br />
=== I'd like to develop a custom product or application based on Openmoko and/or the Neo FreeRunner. How should I proceed? ===<br />
<br />
Send mail to michael@openmoko.org or to steve@openmoko.com<br />
<br />
=== Where are the latest downloads? ===<br />
<br />
Right [[Download|here]].<br />
<br />
==Openmoko==<br />
<br />
===What is Openmoko?===<br />
Openmoko is two things:<br />
<br />
Openmoko is a Linux distribution designed for open mobile computing platforms, such as, but not limited to, cellphones.<br />
<br />
Openmoko is the company behind the Openmoko Linux distribution. Openmoko also manufactures mobile computing platforms, such as the Neo FreeRunner.<br />
<br />
===What is the purpose of this project?===<br />
<br />
By providing a completely open source Linux distribution, and by opening the schematics and CAD files, Openmoko's goal is to nurture explosive innovation (such as occurred with the Personal Computer) in the field of connected mobile computing, cellphones, and ubiquitous computing.<br />
<br />
===How do I join the Openmoko project? ===<br />
<br />
Join one or more of the mailing lists. A great place to start is the community list.<br />
<br />
Browse the wiki, and help improve it.<br />
<br />
Start or join an [[http://projects.openmoko.org/ Openmoko project]].<br />
<br />
Start or join a local group near you.<br />
<br />
===I'm not a programmer, but I have other skills. Can I still be of use? ===<br />
<br />
Absolutely. If you're a visual artist, you can help us with icons and other visuals. Musicians can help contribute ringtones and other sounds. Marketing? Sales? Information visualization? Join the community mailing lists, introduce yourself, and you'll soon find a place to put your skills to good use.<br />
<br />
== Neo FreeRunner - Introductory/Overview/Conceptual Information==<br />
<br />
=== What is the [[Neo FreeRunner]]? === <br />
<br />
The [[Neo FreeRunner]] is an open cellphone designed for the Openmoko Linux distribution. By open we mean that (a) all chips have been chosen to allow their drivers to be completely open sourced and (b) the schematics and the plastic (CAD) files are available as well.<br />
<br />
For more details, see [[Neo FreeRunner|Neo FreeRunner specifications]]<br />
<br />
=== What can I do with the Neo FreeRunner? ===<br />
<br />
The Neo FreeRunner is designed for everyday use by end users and for continued software development and improvements by the Openmoko team and the Openmoko community.<br />
<br />
The Openmoko software is not yet ready for everyday use.<br />
<br />
The question is almost what can you NOT do with this phone - eventually there will be a huge range of free software applications allowing both end users and developers to get much more out of this phone than a standard "locked" mobile phone using features like the integrated GPS, bluetooth, wifi and accelerometers.<br />
<br />
=== What are the buttons on the Neo FreeRunner for? ===<br />
=== What are the LEDs on the Neo FreeRunner for? ===<br />
<br />
There are two buttons on the Neo FreeRunner: One just below the USB socket, and one on the other side, near the top. Both buttons are clear, and both have LEDs behind them. <br />
<br />
All buttons and LEDs are software-controlled; that is, their behavior depends on what the installed software implements.<br />
<br />
See [[FreeRunner/Buttons and LEDs|here]] for more details, along with some programs which implement a variety of behaviors.<br />
<br />
=== What are the benefits of an "open" phone over a "closed" phone? ===<br />
<br />
In a conventional closed phone, the handset maker and the mobile network operator work together to provide a service to you that best suits their business model. The capabilities of a modern smartphone equipped with GPS, Wifi and bluetooth are amazing yet unfortunately inaccessible: many features are "locked down" because they do not suit the network operator. Up until now it has been difficult to buy a phone on which you have freedom to install sofware which is not controlled by the network operators - Openmoko changes that!<br />
<br />
A list of examples of "closed" behaviour has been started here - [[Problems of typical "closed" phones]]<br />
<br />
=== What can we expect in future Neos? ===<br />
<br />
Please join one of the [http://lists.openmoko.org mailing lists] to follow and participate in this discussion.<br />
<br />
=== Purchasing / Shipping / Versions ===<br />
<br />
==== Where can I buy the [[Neo FreeRunner]]? How much?====<br />
<br />
See [[distributors]]<br />
<br />
==== On what bands does the Neo FreeRunner operate? Will it work in my area? ====<br />
<br />
* The Neo FreeRunner is a tri-band GSM phone. It is available in a 850/1800/1900MHz version for North America and a 900/1800/1900MHz version for the rest of the world.<br />
<br />
==== Do I need the debug board? ==== <br />
<br />
With the Neo FreeRunner and NO debug board you can do:<br />
* Kernel development<br />
* Application development<br />
* U-boot updates(equivalent to PC BIOS). Neo 1973 users should only use a tested image to avoid the possibility of bricking the Neo 1973. Neo FreeRunner users do not have this concern, as a bad u-boot can always be updated using the failsafe u-boot in NOR flash<br />
* Kernel and/or rootfs updates using [[Dfu-util]].<br />
<br />
With a debug board you can additionally do:<br />
* Use JTAG to debug u-boot, device drivers, or the kernel<br />
* Use the kernel console<br />
* Neo 1973 users can unbrick their device if they flash a wrong or non-working u-boot image.<br />
* Neo FreeRunner users can update u-boot in NOR flash<br />
<br />
In summary, it is rare for a Neo FreeRunner user to require a debug board.<br />
<br />
To emphasize, the debug board is '''not''' required in order to develop applications, system software, or even kernel or device drivers. The debug board is '''not''' required in order to gain access to the source code or the development tools.<br />
<br />
==== Where do I ask a shipping related question? ==== <br />
<br />
Visit [http://www.openmoko.com/ openmoko.com]<br />
<br />
=== How do I find out what version of hardware I have? ===<br />
<br />
:cat /proc/cpuinfo<br />
<br />
Search for the line that says "Revision". There will be 4 digits, of the form "0350". The '5' in this example indicates hardware revision 5.<br />
<br />
== Neo FreeRunner Known Issues==<br />
<br />
=== Software issues, distribution-wise ===<br />
<br />
Issues relating to software are in the "known issues" section for each distribution. Navigate there via the distributions page - [[Distributions]].<br />
<br />
=== Firmware and hardware issues ===<br />
<br />
Issues relating to firmware and hardware are in [[Neo_FreeRunner_Hardware_Issues|Neo FreeRunner Hardware Issues]].<br />
<br />
Note that some issues might involve a combination of hardware and software.<br />
<br />
=== Selected, commonly-encountered issues ===<br />
<br />
Some selected known issues that are commonly encountered and reported on mailing lists are described below.<br />
<br />
==== My FreeRunner won't register with my cellphone network. What should I do?====<br />
<br />
Please see [[Neo_FreeRunner_Hardware_Issues#Some_SIMs_Don.27t_Work|some SIMs don't work]].<br />
<br />
==== SIM compatibility: It looks like my SIM card is not working; how do I run diagnostics? ====<br />
<br />
Here is how to check: follow [[Manually_using_GSM]] until you get an OK prompt. <br />
<br />
For more detailed documentation, please refer to [[FreeRunner_unable_to_work_with_3G_SIM_cards]] and [[Carriers]].<br />
<br />
==== I read somewhere that a GSM firmware update is available to fix this problem====<br />
<br />
The GSM firmware update is applicable only to the Neo 1973. Any fixes in the update are already implemented in the GSM firmware in the Neo FreeRunner.<br />
<br />
==== Why won't the FreeRunner boot even with the charger connected? ====<br />
<br />
See [[Neo_FreeRunner_Hardware_Issues#Can.27t_boot_with_discharged_or_missing_battery|Can't boot with discharged or missing battery]].<br />
<br />
==== Flashing (dfu-util) -- dfu-util does not find the phone. ====<br />
<br />
In brief, you need to boot the phone into the NAND or NOR u-boot menu before dfu-util will be able to connect. dfu-util uses the USB DFU (Universal Serial Bus Device Firmware Upgrade) protocol, which is only available at the u-boot menu, and '''not''' Ethernet over USB, which is what is available when the phone has booted fully. <br />
<br />
Tip: If you're just trying out different distributions, you don't need to flash them with dfu-util; you can try out new distributions by putting them on the microSD card and booting from the card instead. If you'd like to do this instead of flashing, see [[Booting from SD]].<br />
<br />
To get the u-boot menu:<br />
# Press and hold the AUX button <br />
# Press the Power button until the phone powers on and displays the boot menu<br />
# Release both buttons <br />
# Press and release AUX to move the lightbar, so that the menu will not time out and boot the phone). <br />
<br />
Also see the wiki pages/sections:<br />
* [[Booting the Neo FreeRunner]]<br />
* [[Bootloader#Device Firmware Upgrade]]<br />
* [[Flashing the Neo FreeRunner]]<br />
* [[Dfu-util]]<br />
<br />
==== Why do I experience poor audio quality or buzzing noises during calls?====<br />
See [http://wiki.openmoko.org/wiki/Neo_FreeRunner_Hardware_Issues#Poor_Audio_Quality this issue on the FreeRunner Hardware Issues page]<br />
<br />
====Suspend/resume may corrupt SD card's partition table====<br />
<br />
See [http://wiki.openmoko.org/wiki/Neo_FreeRunner_Hardware_Issues#Suspend.2Fresume_corrupts_SD_card.27s_partition_table this issue on the FreeRunner Hardware Issues page]. See ticket [https://docs.openmoko.org/trac/ticket/1802 #1802].<br />
<br />
==Hardware and Usage-related Questions==<br />
<br />
=== Booting ===<br />
<br />
==== How do I boot into U-boot? How do I select NAND or NOR FLASH? ====<br />
<br />
See [[Booting_the_Neo_FreeRunner|here]]<br />
<br />
=== Battery and Battery Charging===<br />
<br />
==== What is the expected battery life? ====<br />
See [[Neo FreeRunner (GTA02) Battery#Notes_about_expected_battery_life]] and more battery information in [[Neo_FreeRunner_(GTA02)_Battery]]<br />
<br />
==== How do I enable fast charge mode for anything but the official mains charger? ====<br />
See [[Forcing fast charge mode]].<br />
<br />
==== Can the Neo FreeRunner charge when turned off? When suspended? ====<br />
<br />
The Neo FreeRunner can '''not''' charge when turned off.<br />
<br />
The Neo FreeRunner '''can''' charge when suspended.<br />
<br />
==== Can the Neo charge and use devices on a USB hub at the same time? ====<br />
<br />
See [[USB_host#Providing_power_to_run_and_charge_the_Neo_while_in_host_mode|here]]<br />
<br />
===Wireless Connectivity===<br />
<br />
====What kind of wireless connectivity does the FreeRunner have? ====<br />
<br />
The FreeRunner has the following connectivity options:<br />
* Tri-band GSM (850/1800/1900 MHz in North America, and 900/1800/1900 MHz, commonly referred to as "European tri-band", for other parts of the world). For a list of compatible service providers, see [[Neo1973 compatible cellphone providers]].<br />
* GPRS Class12/CS4 2.5G (Not EDGE)<br />
* Bluetooth 2.0 EDR<br />
* WiFi: Atheros AR6K in [[GTA02#.22Phase_2.22_.28GTA02.2C_.22Mass_Market.22.29|GTA02]]. (No 3G in year 2007 models)<br />
<br />
<br />
==== GSM/GPRS information ====<br />
<br />
The following pages contain very useful information:<br />
<br />
* [[Gsmd|GSM Daemon]]<br />
<br />
* [[GSM|General GSM page]]<br />
<br />
* [[Hardware:AT_Commands|AT commands]]<br />
<br />
* [http://freeyourphone.de/portal_v1/viewtopic.php?f=21&t=295#p2956 Useful script for GPRS]<br />
<br />
==== How do I get the WLAN (802.11, Wi-Fi, wireless network) working? ====<br />
<br />
See [[Neo FreeRunner Wifi]]<br />
<br />
==== How do I get the GPS working? ====<br />
<br />
See [[GTA02 GPS]]<br />
<br />
==== It takes a long time (10min+) before the FreeRunner gets the first GPS data/readings ====<br />
<br />
See [[GPS Problems]].<br />
<br />
==== How do I get Bluetooth working manually? ====<br />
<br />
See [[Manually_using_Bluetooth]]<br />
<br />
==== How do I use an external Bluetooth keyboard with the FreeRunner ? ====<br />
..TBA..<br />
<br />
(It is mentioned as being a bit funky, but preliminary documentation can be found [http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#HID_.28Human_Input_Device.29 here])<br />
<br />
====Can I bridge to an Ethernet (wired or unwired) network via a suitable Bluetooth enabled router? ====<br />
<br />
Yes - see [http://gentoo-wiki.com/HOWTO_Configure_a_bluetooth_network_access_point this howto for how to configure a linux computer to act as such a router] and [[Bluetooth Support]].<br />
<br />
<br />
=== USB ===<br />
<br />
==== How do I connect a USB memory-stick etc? ====<br />
<br />
This requires an adapter Mini-B 5-pole => Type A jack or an adapter jack => jack. See [[USB host]] for more information.<br />
<br />
====Once I have such an adapter, can I use it to connect 2 Neos to each other?====<br />
<br />
This question is equivalent to '''How to connect two [Unix/Linux] computers via USB cable and what sort of special cable is needed?''' -> http://www.linuxquestions.org/questions/linux-general-1/connecting-two-computers-with-a-usb-cable-data-cable-411073<br />
<br />
It should work if one Neo is set to Host mode and the other one set to Device mode. One Neo could give power to the USB-port it the other Neo's battery is low. ''(I have to verify this)''<br />
<br />
==== How do I use an external USB keyboard with the FreeRunner ? ====<br />
<br />
Run:<br />
echo "host" > /sys/devices/platform/s3c2410-ohci/usb_mode<br />
echo "1" > /sys/devices/platform/neo1973-pm-host.0/hostmode<br />
<br />
These commands will put the FreeRunner into powered USB host mode. After this, just plug in the keyboard and it'll work. Personally, I've made a .desktop file to switch into and out of host mode.<br />
<br />
To switch back to unpowered device mode just run:<br />
<br />
echo "device" > /sys/devices/platform/s3c2410-ohci/usb_mode<br />
echo "0" > /sys/devices/platform/neo1973-pm-host.0/hostmode<br />
<br />
Finally you will need a<br />
USB Type A Female to Female adapter. For more details see<br />
[[Specialized_USB_cables#Attaching_the_Neo_.28acting_as_a_USB_host.29_to_a_USB_device|here]]<br />
<br />
'''The above does not work with QtExtended on mwester's kernel, it gives an invalid argument on the first command.'''<br />
<br />
No, stable-tracking kernels give that error too but they still work. --[[User:Lindi|Lindi]]<br />
<br />
=== Display ===<br />
<br />
==== Can the phone play VGA video? ====<br />
<br />
No, it can do about 20 fps QVGA with software, and something beetween QVGA and VGA playing MPEG-4 using hardware (at resonable fps). Scaling is also done with GPU hardware.<br />
<br />
<br />
<br />
=== Storage ===<br />
<br />
==== What microSDHC-cards are supported? ====<br />
<br />
See [[Supported_microSD_cards|here]]<br />
<br />
==== What is the best file system for microSDHC-cards? ====<br />
<br />
Short answer: for OM it is ext3. Other options: ext2 and vfat. Don't use wear-aware file systems like jffs2 and ubifs.<br />
<br />
For a longer explanation, see [[FileSystem_microSD_cards|here]].<br />
<br />
===System-level information===<br />
<br />
==== What hardware signals are available?====<br />
<br />
To simplify extending the hardware, various signals of interest are brought out via the JTAG connector and can be easily accessed with the debug board:<br />
<br />
(TBA: List of signals)<br />
<br />
Some additional signals that did not fit on the JTAG connector are brought out to solder pads:<br />
<br />
(TBA: List of signals)<br />
<br />
==== Is the JTAG interface that comes with GTA01 compatible with GTA02?====<br />
<br />
Yes<br />
<br />
==== How do I get low-level hardware-related functions, like power up device, dump register? ====<br />
<br />
See [[GTA02_sysfs]]<br />
<br />
<br />
<br />
=== Miscellaneous ===<br />
<br />
====Will Openmoko "Just Work" with Mac OS X? ====<br />
<br />
There has been some discussion of this on the mailing list. There is motivation, and there are interested developers. <br />
Not being a Mac OS X user, I don't know enough<br />
to summarize the discussion to answer this question. Can someone please fill in?<br />
<br />
For IP over USB cable connectivity, it is planned to improve/adapt the AJZaurusUSB driver, allowing ssh into the Openmoko.<br />
<br />
It is expected that (Bluetooth/UB) SyncML based interoperation for<br />
contacts and events can easily be achieved by a patch<br />
to the Apple iSync configuration tables.<br />
<br />
There is an open source implementation of Cocoa (GNUstep) that aims to run MacOS X compatible applications (sort of<br />
PPC/x86/ARM universal binaries) on Openmoko devices: mySTEP.<br />
<br />
====Why is resuming from suspend so slow ====<br />
The suspend / resume speed is influenced by the kernel loglevel, i.e. how many messages are printed on the console during suspend / resume. The loglevel can be set using the kernel boot parameters. Setting 'loglevel=1' using the u-boot console for example improves resume speed drastically compared to 'loglevel=8'.<br />
<br />
As an alternate to changing the kernel parameter from the boot loader, you can pass "-c 1" to klogd. You can add this parameter to /etc/default/klogd in debian, for example.<br />
<br />
==Software==<br />
<br />
===General Questions===<br />
<br />
====Is it completely free software/open source? ====<br />
<br />
Yes. All software that runs on the main CPU and can be updated by the user is available in source.<br />
<br />
Firmware in "black box" hardware modules that can not be modified by users is not available in source form. Effectively, these modules are "hardware only".<br />
<br />
This allows, for example, that the driver for the GSM module be completely open sourced without violating any FCC rules.<br />
<br />
<br />
<br />
==== Does Openmoko run on any other hardware? ====<br />
<br />
You can run it on your [[How_to_run_Openmoko_Apps_on_PC|PC]]. You may be able to run it on other [[Openmoko_supported_devices|mobile platforms]]<br />
<br />
==== Can Java applications from other mobile phones run on the FreeRunner? ====<br />
<br />
I think a lot of work must still be done, but [[Java|this]] wiki page has some information<br />
<br />
===Distributions===<br />
<br />
====What distributions are available for the Neo FreeRunner?====<br />
<br />
See [[Distributions|Distributions]]<br />
<br />
==== How do I find out what image versions are in use on the phone? ====<br />
<br />
You can run the commands given below on the phone (in an SSH session from your host PC, or in the Terminal application on the phone itself)<br />
{| border="1" cellspacing="0" cellpadding="5" align=""<br />
! To find out<br />
! Run<br />
|- <br />
| Kernel version that is currently running<br />
| <br />
uname -a<br />
|-<br />
| The version of the root filesystem that you are currently using<br />
| <br />
cat /etc/version <br />
or <br />
cat /etc/om-version<br />
|-<br />
| The versions of u-boot on the phone (The FreeRunner has one u-boot image in NOR memory, and one in NAND - see [[Booting the Neo FreeRunner]] for more information)<br />
| <br />
grep Bootloader /dev/mtdblock0 (yields the NOR u-boot version)<br />
or<br />
grep Bootloader /dev/mtdblock1 (yields the NAND u-boot version)<br />
|}<br />
<br />
====Can the Neo FreeRunner dual boot? Multiple boot?====<br />
<br />
Since the Neo FreeRunner can boot from the micro SD card, you can install and boot from as many distributions as will fit on your card. See [[Booting from SD]].<br />
<br />
<br />
====How do I install Debian on the Neo FreeRunner?====<br />
<br />
See [[Debian#Installation|Debian Installation]]<br />
<br />
=====Are there any known issues with Debian on the Neo FreeRunner?=====<br />
<br />
See [[Debian#Known_Issues|Debian Known Issues]]<br />
<br />
=====How do I replace the matchbox window manager with the xfce window manager?=====<br />
<br />
Replace the matchbox-wm line in zhone-session with xfwm4 to start the xfce-wm.<br />
<br />
Here's my (Fox Mulder) /usr/bin/zhone-session file which works with xfwm and matchbox keyboard popup:<br />
<br />
#!/bin/sh<br />
<br />
#zhone &<br />
exec startxfce4 &<br />
matchbox-keyboard-toggle &<br />
#exec matchbox-window-manager -use_titlebar yes<br />
exec xfwm4<br />
<br />
=== Applications ===<br />
<br />
<br />
====What software is on the phone?====<br />
<br />
At the moment, almost no 'end-user' applications are present and working in a usable state.<br />
It is possible to make and receive calls in some software revisions, this frequently breaks though.<br />
<br />
====What software can be installed on the phone?====<br />
<br />
Pretty much any that can be cross-compiled for the ARM architecture.<br />
<br />
====Will it be possible to use popular VoIP applications on the Openmoko platform? ====<br />
<br />
Since it has WiFi the FreeRunner should be a good platform for VOIP use. <br />
<br />
In either case please check for softphone apps ported to the Openmoko distribution at the [http://projects.openmoko.org/ projects] page. We need to focus efforts on free software. Not convincing non-free software companies to release binaries for our Neos.<br />
<br />
====Will it be possible to use popular Instant Messaging applications ? ====<br />
<br />
There many Open Source IM clients, many of which have a plugin architecture and so support the use of more than one IM protocol, even simultaneously. One example is [[Pidgin]], formerly called GAIM. GPRS does induce a certain amount of latency but that should not be a problem for simple, text-oriented chat between parties. And the GTA02's WiFi will make it even better.<br />
<br />
==== Does it support Flash so can I watch YouTube? ====<br />
You don't really need Flash to watch YouTube videos, for example, if you want to watch www.youtube.com/watch?v=k9QLdK6pFCI just install mplayer and use this command: <br />
mplayer http://ytpocket.com/getflv.php?id=k9QLdK6pFCI<br />
or use this small script with the video URL as the first parametre:<br />
#!/bin/sh<br />
vid=`echo "$1" | sed 's/.*\?.*=\(.*\)/\1/'`<br />
mplayer http://ytpocket.com/getflv.php?id=$vid<br />
<br />
If you don't want to tell ytpocket.com about every video you watch on debian you can also<br />
sudo apt-get install youtube-dl<br />
mplayer `youtube-dl --get-url www.youtube.com/watch?v=k9QLdK6pFCI`<br />
<br />
=== Package Management===<br />
<br />
==== How do I install and manage software on Openmoko? ====<br />
<br />
See [http://handhelds.org/moin/moin.cgi/Ipkg here]<br />
<br />
==== What about opkg? ====<br />
<br />
See [[Opkg|here]]<br />
<br />
==== What is the meaning of the error codes from ipkg? ====<br />
<br />
See [[Opkg#Error_Codes|here]]<br />
<br />
<br />
==== Does opkg support packages autocompletion ? ====<br />
<br />
It's possible now, see [http://blog.upme.fr/?/Linux/28-Openmoko-Opkg-Autocompletion-With-Packages-Names 0pkg : The opkg autocompletion]<br />
<br />
===Development===<br />
<br />
====How can I compile programs for the Neo FreeRunner? ====<br />
<br />
See [[Toolchain]].<br />
<br />
====Is there an emulator available for Openmoko? ====<br />
<br />
For a lot of testing and development work you can simply run Openmoko directly on your PC.<br />
<br />
=====QEMU=====<br />
<br />
QEMU can emulate the Neo 1973 and the Neo FreeRunner. The [[MokoMakefile]] has support for automatically building, flashing, and running [[Openmoko under QEMU|the Neo emulator]].<br />
<br />
*Ubuntu users can follow the instructions in [[Automatic_emulation_in_Ubuntu]]<br />
<br />
*Users of other Linux distributions can try the following:<br />
:"make qemu” will build qemu-neo1973, download the latest official openmoko images, flash the images into the virtual NAND flash, and run the emulator.<br />
<br />
See [[Qemu]] for more advanced information on running Openmoko in Qemu.<br />
<br />
=====Xoo=====<br />
<br />
[http://projects.o-hand.com/xoo Xoo]. Koen says: "Xoo should be enough for most applications people will develop, since most don't need access to the GSM uart directly. If you're hardcore you could use qemu + xoo, but that still doesn't emulate all the hardware quirks (e.g. unaligned access)".<br />
<br />
Update: Stefan Schmidt has resized the [[Neo1973]] Mock-up and written a small description for xoo. In his words:<br />
<br />
It's not really usable at all, as you need a really high screen resolution to fit the whole picture on your screen. And of course the dpi are wrong. Even no buttons because I can't remember where they are at the case.<br />
<br />
http://www.datenfreihafen.org/~stefan/OpenMoko/neo1973-xoo-device.tar.bz2<br />
<br />
Start with 'xoo --device /path/to/neo1973.xml'<br />
<br />
Some more details [[Getting_Openmoko_working_on_host_with_Xoo|here]].<br />
<br />
=====Xephyr=====<br />
<br />
Or use Xephyr directly with locally compiled programs (e.g. matchbox svn + openmoko):<br />
Xephyr -screen 480x640 -nolisten tcp -ac :1 &<br />
export DISPLAY=:1<br />
export LD_LIBRARY_PATH=/usr/local/lib<br />
matchbox-window-manager -display $DISPLAY -use_titlebar no \<br />
-use_super_modal yes -use_lowlight yes -use_dialog_mode static \<br />
-use_cursor yes &<br />
matchbox-panel --geometry=480x44 --end-applets=clock &<br />
openmoko-footer &<br />
openmoko-taskmanager &<br />
<br />
====Where can I find some type of tutorial for a 'Hello, world' on Openmoko? ====<br />
<br />
This should get you started:<br />
* [[Building_a_hello_world_application]]<br />
* http://www.gtk.org/documentation.html#Tutorials<br />
<br />
====Can PalmOS apps applications be ported to run on Openmoko? ====<br />
<br />
Making legacy apps written for the "Garnet" OS (née "Palm OS") run on Linux<br />
is decidedly non-trivial.<br />
<br />
PalmOS apps are in general very hard to simply 'port'. Particularly well-designed programs may make it possible.<br />
<br />
The ACCESS Linux Platform will include Garnet on Host (GHost), a PalmOS emulator that will support M68000 (68k) and ARM PalmOS applications. This part (GarnetVM and the .prc loader) will however be closed-source and likely under a restrictive license (fact confirmed by ACCESS Co. employees), making it rather unusable. In addition GarnetVM depends on Hiker and other packages.<br />
<br />
It is possible that POSE, an emulator that simulates a Palm device on a Linux host could be used to allow 68k based applications to run. This emulator has been around a long time; one expects that it will also run on Openmoko, but this has to be considered a short-term bandaid rather than a long-term solution.<br />
<br />
Hopefully emulation will be necessary only for M68000 code (pre-PalmOS 5) while native ARM programs can run natively under Linux, provided a proper set of PalmOS libraries and a .prc executable loader.<br />
<br />
==== Does it support Java? ====<br />
It will have eventually, if you help us to get it working. Some good places to keep track of would be [http://projects.openmoko.org/projects/java-pkg/ projects.openmoko.org] and [https://phoneme.dev.java.net/ PhoneME].<br />
<br />
Project [[https://wiki.evolvis.org/jalimo/index.php/Jalimo Jalimo]] is a project aiming to provide a Java stack on mobile devices. There is a [https://wiki.evolvis.org/jalimo/index.php/Openmoko port of Jalimo] for Openmoko.<br />
The [[Debian]] distribution supports CacaoVM and JamVM through apt-get. See [[Java]] for more infos.<br />
<br />
==== Does it support Ruby? ====<br />
<br />
For Ruby 1.9, please refer to http://blog.sparkymat.net/2008/08/10/ruby-19-on-openmoko/<br />
<br />
For Ruby 1.8.6, please refer to http://blog.wolfman.com/articles/2008/08/10/ruby-1-8-6-on-openmoko-freerunner<br />
<br />
==== Does it support Python? ====<br />
<br />
Yes, with some caveats. See [[Python]] for more information.<br />
<br />
<br />
====How do I dump details about X11 configuration and extensions? ====<br />
<br />
Run the command xdpyinfo. Generally, you would do this via an SSH session to the phone, so you may need to first <br />
<br />
export DISPLAY=":0.0"<br />
<br />
and then run<br />
<br />
xdpyinfo<br />
<br />
For an example invocation, see [http://lists.openmoko.org/pipermail/community/2007-January/001353.html xdpyinfo output].<br />
<br />
== Distribution Customization ==<br />
<br />
{{Note| Suggestion: this should be split off into a separate page, since many of the questions below aren't really overview-level but specialized; a question like "How do I customize a distribution?" could be added to the Software - Distributions part, linking to the new page. --[[User:Eddsouza|eddsouza]] 07:35, 7 September 2008 (UTC)}}<br />
<br />
=== Compilation & packaging ===<br />
==== What is the 'overlay' approach to bitbake development? ====<br />
:You can create a local overlay for the bitbake build chain and develop in the overlay as described in [[Application_Development_Crash_Course| Application Development Crash Course]].<br />
<br />
==== Which .bb files are related with the Openmoko? ====<br />
==== Are there any configuration files for Openmoko? ====<br />
==== How can I port an application written with autotools to Openmoko? ====<br />
After you source the [[Toolchain|Openmoko toolchain]] variables, the Openmoko processor compiler becomes the default compiler. You can compile any GNU - like project just typing ''./configure --host i686'' and then ''make'' - it will produce libraries and executables as expected. Just these executables will not run on your i686 host - they will run on Openmoko ARM processor. Use scp to upload the executables to your phone.<br />
<br />
==== How can I add an application written with autotools to the openmoko tree? ====<br />
<br />
==== How can I make changes in the openmoko applications? ====<br />
==== How can I submit my changes? ====<br />
==== Can I use the mokomakefile in the development process? How? ====<br />
<br />
:Yes, [[MokoMakefile]] can be used in the development process. See [[MokoMakefile#Developing_with_MokoMakefile| Developing with MokoMakefile]].<br />
<br />
==== What's the way to include/exclude a newly added package to/from the final rootfs? ====<br />
==== Where do the final ipk & binary files reside? ====<br />
:ipk files are in <br />
./build/tmp/deploy/glibc/ipk/<br />
:binary images are in<br />
./build/tmp/deploy/glibc/images/fic-gta01/<br />
<br />
==== How can I add an application to the applications list? ====<br />
==== How can I assign an image to my new application to be seen in the applications list? ====<br />
The Openmoko project tree contains the folder 'data' where you can put any 128*128 icon. You need to mention the icon in two places in this folder: <br />
* Makefile.am must contain the line dist_appicon_DATA = <icon_name>.png<br />
* The <application_name>.desktop file that must be in this folder should contain the Icon=<icon_name> (without file type).<br />
<br />
<br />
<br />
==Misc==<br />
<br />
===On the lists on lists.openmoko.org, should replies be added above or below the original text? ===<br />
<br />
Please reply UNDER post.<br />
<br />
===How can I find out if a question or topic has already been discussed on the mailing lists? ===<br />
<br />
By searching the mailing list archives. For example, using Google searches:<br />
<br />
site:openmoko.org text<br />
<br />
For example, to search for accelerometer:<br />
<br />
site:openmoko.org accelerometer<br />
<br />
If you only want to read the "official" mails from FIC people or from Openmoko people:<br />
<br />
site:openmoko.org text "at fic.com.tw"<br />
site:openmoko.org text "at openmoko.org"<br />
<br />
For example to search for "release date" from FIC people:<br />
<br />
site:openmoko.org "release date" "at fic.com.tw"<br />
<br />
Alternatively you can use the [http://www.google.com/coop/cse?cx=018430699993342716089%3Aszsaurhronw custom Openmoko search engine] that is using [http://www.google.com/coop/ Google Co-op].<br />
<br />
===how many dead pixels may the LCM have before calling it defect? ===<br />
<br />
The answer for the display used in GTA01 and GTA02 is '2'<br />
<br />
=== how many visits does this wiki have? ===<br />
See this [[Wiki_statistic_numbers|wiki's statistics]] page.<br />
<br />
=Historical=<br />
The Neo1973 was last available in Febuary 2008. <br />
<br />
==Neo1973 Hardware== <br />
<br />
===What are the hardware specifications of Neo 1973 ? ===<br />
<br />
See page [[Neo1973_Hardware]] and category [[:Category:Neo1973 Hardware | Neo1973 Hardware]] and [[Disassembling Neo1973]]<br />
<br />
===How do I input text? ===<br />
<br />
Use provided keyboard app.<br />
<br />
Use Bluetooth keyboard.<br />
<br />
For more methods and ideas see [[Wishlist:Text_Input]].<br />
<br />
===Can I record calls and/or play audio files in calls? ===<br />
<br />
Yes, audio path from GSM to/from mic and speakers is completely controllable by user. For example recording calls (both sides) and implementing an [[Answering Machine]] is possible. Also using text->speech should be possible or modifying outgoing voice. <br />
<br />
Tom Hacohen has written a program called [[Call Recorder]] which allows both sides of a conversation to be saved to a .wav file.<br />
<br />
Note that there are only 2 A/D inputs and three D/A outputs (one dedicated to the earpiece). This means that stereo audio playback cannot happen at the same time as the [[Answering Machine]] functionality, amongst other things. See the audio page. [[Neo1973_Audio_Subsystem|Neo1973 Audio Subsystem]]<br />
<br />
===What is the battery life? ===<br />
<br />
There has been no word on this so far, but see [[Neo1973 Power Management#Approximate_power_draw_of_various_subsystems|these estimates]] for a rough idea. More information about the battery [[Neo1973 Battery|here]].<br />
<br />
=== USB ===<br />
<br />
====What can I do with the USB port on the Neo? ====<br />
Charge the phone, communicate with it over USB-serial, or USB-networking.<br />
<br />
Plug external devices, such as wifi, cameras, or mass-storage devices.<br />
<br />
====What can't I do with the USB? ====<br />
<br />
The only limitation on current hardware seems to be no usb 2.0 support, which means slower communication with 2.0 devices.<br />
<br />
====Why is only USB 1.1 provided? ====<br />
<br />
The processor has USB 1.1 built in. One with USB2 built in would have been more expensive, and might not be open.<br />
<br />
The FreeRunner has the same processor as the Neo1973.<br />
<br />
====What are the details of the USB port on the Neo? How does it compare to USB On-The-Go? ====<br />
<br />
The Neo will have mini-USB-B, and will be able to function as either a host or a device. It will NOT be USB On-The-Go. OTG is a complex specification, and it comprises way more than just<br />
an AB socket, but also electrical and software components which cannot be provide by the S3C2410.<br />
<br />
You will need a special Mini-B to regular-B cable (note that this won't actually comply with the USB standard: a compliant cable has to have an A or Mini-A plug on one end, and B or Mini-B on the other).<br />
<br />
== Q: Can the Neo charge and use devices on a USB hub at the same time? ==<br />
<br />
It's entirely a cabling problem.<br />
The neo essentially has two ports in one - there is the mini-AB port, which is missing the 5V line, and the 5V charging line.<br />
<br />
When the Neo is plugged into one of the the outputs of a USB hub, the 5V line is used to charge the battery.<br />
The 5V line is not otherwise used in the neo.<br />
<br />
To use peripheral devices plugged into a hub, the Neo must be plugged into the input of a powered hub, that is capable of working without 5V input (the Belkin Tetrahub for example will not recognise a host without it).<br />
<br />
To use peripheral devices and charge at the same time, you need to make up a special cable, that plugs into the output of a powered hub - to pick up the charge current, and into the input of a powered hub at the same time - to act as a USB host.<br />
These cables are wired together for 5V and 0V, but only the input cable has the data pins wired.<br />
In some cases (the belkin hub mentioned above) this will also allow the hub to recognise the neo as a host, when it would not before.<br />
In other cases - where the hub keeps the outputs unpowered until it senses a host - an external source of 5V would need to be plugged into the 'output' cable.<br />
<br />
See [[USB host#Providing power to run and charge the Neo while in host mode]]<br />
<br />
[[Category:FAQ]]<br />
[[Category:Power]]</div>Vanoushttp://openmoko.org/wiki/Main_PageMain Page2010-09-20T15:16:39Z<p>Vanous: SPAM Undo revision 82388 by Lcdtvs22 (Talk)</p>
<hr />
<div>{{Languages|Main Page}}__NOTOC__<br />
__NOEDITSECTION__[[Image:Neo front 3.gif|right]]<br />
<div style="padding: 2.5ex; text-align: center; font: bold x-large sans">Openmoko™ - Open. Mobile. Free.</div><br />
'''Openmoko™''' is a project dedicated to delivering mobile phones with an open source software stack. Openmoko is currently selling the [[Neo FreeRunner]] phone to advanced users and will start selling it to the general public as soon as the software is more developed.<br />
<br />
* [[Introduction]]<br />
* [[Why Openmoko|Why Openmoko?]]<br />
<br />
[[More Information]]<br />
<br />
===Get Involved===<br />
Openmoko is a project driven by a community of passionate and intelligent volunteers. If you have the ability, please contribute to our cause. Openmoko's ambitions far exceed the resources available. <br />
<br />
* [[Community Resources]]<br />
* [[Gta02-core|Create a new hardware revision of the gta02 hardware]]<br />
* [[Create User Manuals]] for [[Distributions]] and [[Applications]]<br />
* Enhance the multi-device multi-vendor [[FSO]] middleware.<br />
<br />
===How To Purchase===<br />
The Neo FreeRunner is sold by various [[distributors]] around the world.<br />
<br />
See [[Getting Openmoko]] for more information.<br />
<br />
----<br />
<br />
====Latest News====<br />
<br />
{{News}}<br />
[[News Archive|more news...]]<br />
<br />
----</div>Vanoushttp://openmoko.org/wiki/Community_Updates/2010-11-01Community Updates/2010-11-012010-09-09T07:35:38Z<p>Vanous: /* New Applications */ atrack</p>
<hr />
<div>{{Improve}}<br />
{{Note|<br />
*Take a moment and look at Discussion page to get a clue on how to contribute to Community Updates while following OM wiki editing guidelines please.<br />
*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><br />
*Please fill in everything you think the community should know.<br />
*On YYYY-MM-DD this content should be _moved_ to http://wiki.openmoko.org/wiki/Community_Updates/YYYY-MM-DD, feel free to do it.<br />
*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).<br />
}}<br />
<!--{{Editing|USER|DATE|Community Update Draft conforming to OM Wiki editing guidelines}}--><br />
<!--{{Editing|~~~|~~~~~|your comment...}}--><br />
<br />
====='''Period YYYY-MM-DD to YYYY-MM-DD'''=====<br />
<br />
==Distributions==<br />
<br />
{{DistributionBox|<br />
Name=Distro Name [version]|<br />
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.|<br />
Screenshot=System_boot.png|<br />
Codename='codename'|<br />
Homepage=http://www.homepage.org|<br />
Image=[http://www.homepage.org/path/to/ images]|<br />
Works={{Works}}<br />
}}<br />
<br />
==Applications== <br />
<br />
===New Applications===<br />
<br />
{{ApplicationBox|<br />
Name=aTrack 0.8|<br />
Description=APRS tracker and communicator for mobile devices. It turns your Neo into bidirectional APRS unit and besides others it allows you to track your position, do text messaging, object creation or display stations around.|<br />
Screenshot=ATrack-title.png|<br />
Homepage=http://atrack.googlecode.com/|<br />
TestedOn=SHR-Unstable|<br />
PackageName=[http://atrack.googlecode.com/files/atrack_0.0.81%2Bsvnr128-r0.5_all.ipk]<br />
}}<br />
<br />
<br />
{{ApplicationBox|<br />
Name=Exampleapp 0.0.1|<br />
Description=Exampleapp 0.0.1 is an application to do some stuff..|<br />
Screenshot=System_boot.png|<br />
Homepage=http://wiki.openmoko.org/|<br />
TestedOn=SHR-Unstable,Om2009T5|<br />
PackageName=[http:// www.some.srv/path_to/Exampleapp.ipk Exampleapp]<br />
}}<br />
<br />
===Application Updates===<br />
<br />
{{ApplicationBox|<br />
Name=Exampleapp 0.0.1|<br />
Description=Exampleapp 0.0.1 is an application to do some stuff...<br />
* new example feature 1<br />
* new example feature 2|<br />
Screenshot=System_boot.png|<br />
Homepage=http://wiki.openmoko.org/|<br />
TestedOn=SHR-Unstable,Om2009T5|<br />
PackageName=[http:// www.some.srv/path_to/Exampleapp.ipk Exampleapp]<br />
}}<br />
<br />
==Community==<br />
<br />
Most important and change making mails on the mailing lists, blogs etc.. Coolest hacks, screenshots, themes etc..<br />
<br />
==Event News==<br />
<br />
* '''2010 Autumn''' [http://wiki.openmoko.org/wiki/Open_HW_SW_Event/de German Open Hard&Software Workshop ] in Munich; will cover Openmoko, Beagle Board, Arduino, OpenPandora, ...; still in planing phase, Doodle scheduling link: http://www.doodle.com/93cu86vm2s69zsxc<br />
<br />
* '''2010-mm-dd''' [http://example.url.xom Example event] | add your event here<br />
<br />
<br />
[[Category:Community Update]]</div>Vanoushttp://openmoko.org/wiki/ClassifiedsClassifieds2010-09-07T17:05:03Z<p>Vanous: </p>
<hr />
<div>This page is for selling, buying or exchanging Openmoko devices and accessories. <br />
<br />
== For Sale ==<br />
<br />
List here if you have one for sale. By location.<br />
<br />
=== Canada ===<br />
<br />
==== Ontario ====<br />
I am in the market for a used phone vw ride at g mail $200<br />
<br />
=== USA ===<br />
==== New Hampshire / New England Area ====<br />
*GTA02 850Hz(US). Great condition, 512MB SD-Card(and adapter), Wall-Charger, stylus, neoprene case, headset, and has Android on it currently. PayPal Accepted. Will ship anywhere in the US. $250 Nick: doobe01 AT gmail DOT com<br />
<br />
==== San Francisco ====<br />
* Two spare GTA02 batteries, and a Neoprene GTA02 carrying case for sale. Make me an offer. Email ken at restivo dot org<br />
* One barely-used GTA02, $300 OBO. Email comptona at gmail dot com.<br />
<br />
====Seattle====<br />
*GTA02 850hz(US). Great condition, screen protector, 1 gig card. Don't have time for this device anymore. Will to negotiate. Matt: mttsmth DOT ai AT gmail DOT com --SOLD<br />
<br />
<br />
<br />
<br />
<br />
=== Europe ===<br />
<br />
==== Sevilla, Spain ====<br />
*GTA02 Neo FreeRunner v6, europe version (900Hz), GPS fixed, no buzzfixed. I can include all the original stuff it came with (original battery, multiple nationalities charger, USB wire, stylus, neoprene carrying case, headphones and even the original box). No memory card included. It has the InvisibleShield on the screen as protection. Everything is well kept and in mostly new condition. I accept offers at yyprum at gmail dot com. I'm selling it because I lack time for it. I don't remember which is the FW I last used on it, maybe SHR, maybe Android.<br />
___Translation into Spanish___<br />
GTA02 Neo FreeRunner v6, version europea (900Hz), arreglado el problema del GPS, pero sin el buzzfix. Puedo incluir los articulos que venian originalmente con el (batería original, el cargador con adaptadores para otros paises, cable USB, el stylus-boli-laser, la bolsa de neopreno para llevarlo, los cascos e incluso la caja original). No incluyo la pastilla de memoria. Tiene como proteccion de pantalla el InvisibleShield. Todo esta como nuevo. Acepto ofertas en yyprum arroba gmail punto com. Lo vendo por que me falta el tiempo para usarlo. No recuerdo que Firmware tiene ahora mismo, puede ser SHR o Android.<br />
<br />
<br />
<br />
<br />
== Wanted ==<br />
<br />
List here if you want a phone and what price you're willing to pay. By location.<br />
<br />
*New Jersey (Flemington, NJ/Hunterdon County)<br />
I'm starting a GNU/Linux business targeted at the masses and want to buy a Neo FreeRunner. Can't afford more than $150 or so (need money for stock / advertising / other expenses). Willing to work out a deal of some kind 50% now 50% later / trial basis (since it might not suffice given development status) / open to ideas. email: chris (at) domain: kglug.org<br />
<br />
*Charleston(South Carolina,USA)<br />
I just purchased freerunner. I was looking on linuxdevices.com and say when the Neo 1973 came out, it had an upgraded package that included several accessories and was all included in a plastic carry box. if anyone has one they would like to part with alonog with an openmoko lanyard, contact me please. nismoadam(at)gmail dot com<br />
<br />
* Mijail<br />
I want to buy NeoFrerunners phone to sell in Argentina. My mail is mijailnils@gmail.com<br />
<br />
* StealthCP (UK)<br />
I want to purchase a used (or spares/repair) Neo 1973 in order to replace the damaged TFT screen in my Freerunner, condition depends on screen will purchase from anywhere, would pay no more than £100, more if other components/peripherals are included. Contactable in #openmoko or via e-mail at dpreid AT gmail DOT com.<br />
<br />
* klon (Lithuania)<br />
I want to purchase Openmoko stock stylus — the original one with pen, laser pointer and flashlight. My adress is abdullakh ET gmail DOT com<br />
<br />
[[Category:Community]]<br />
[[Category:Purchase]]</div>Vanoushttp://openmoko.org/wiki/MokosuiteMokosuite2010-09-07T10:27:45Z<p>Vanous: /* Hardware buttons */</p>
<hr />
<div>{{Languages|Mokosuite}}<br />
<br />
<onlyinclude><br />
{{ApplicationBox|<br />
Name=[[Mokosuite]]|<br />
Description=Elementary based phone suite |<br />
Screenshot=MokoWM.png |<br />
Homepage=http://gitorious.org/mokosuite2|<br />
TestedOn=SHR |<br />
PackageName=mokosuite2<br />
}}<br />
</onlyinclude><br />
<br />
{{application|Mokosuite}}<br />
<br />
=Overview=<br />
<br />
The mokosuite phone suite package is made up several components. Outside the mokosuite tree there is mokowm-imf-ecore, an input method module for<br />
Ecore.<br />
<br />
{|align=center<br />
|__TOC__<br />
|}<br />
<br />
<br />
{|<br />
| [[Image:Mokohome.png|200px|thumb|Launcher]]<br />
| [[Image:Mokosettings.png|200px|thumb|Settings]]<br />
| [[Image:Mokokeyboard.png|200px|thumb|Keyboard]]<br />
| [[Image:Mokopanel.png|200px|thumb|Panel]]<br />
|}<br />
<br />
=Installation=<br />
<br />
Installation on SHR:<br />
<br />
opkg install mokosuite2<br />
<br />
=The phone application=<br />
<br />
The phone application is used to actually make phone calls. It manages also<br />
the actual connection to the GSM network.<br />
The phone app has an integrated call log and contacts list, for now stored in<br />
SQLite databases. My idea is to write my own implementation of opimd backed by<br />
mokophone.<br />
<br />
When a phone call starts or is incoming, the phone app sends notification<br />
through D-Bus to the panel, creating a green active call icon and filling the<br />
notification list with the current active call. If a call gets lost, another<br />
notification is pushed to the panel (with a red lost call icon :)<br />
<br />
<br />
=The messages application=<br />
<br />
There is actually a stub with some builtin messages, but my objective is to<br />
modify some of the opimd specs to accomplish a more threaded message management.<br />
This shall be discussed with mickeyl or anyone else is involved. We should find<br />
a way to make a custom SQL query, optimized for retrieving information about<br />
SMS threads, not wasting resources.<br />
<br />
I still have to decide to integrate e-mail support with sms... but I don't know,<br />
there are many points of view about this approach.<br />
<br />
<br />
=The settings application=<br />
<br />
<br />
<br />
This app is in charge to manage much all of the aspects of the suite and of the<br />
phone itself. For now it manages only a few things, but it's going to be a very<br />
big application :)<br />
<br />
<br />
=The mail application=<br />
<br />
Much TODO :)<br />
<br />
<br />
=The window manager=<br />
[[Image:Mokodesk2.png|thumb]]<br />
As of now, mokowm is a veeeery basic X window manager based on Ecore_X APIs,<br />
which have made things very easy. However, a phone window manager should do<br />
many things, and this will be a major part of the project.<br />
The wm right now has also a builtin simple virtual keyboard, not very complete<br />
yet, but working :)<br />
It is activable using signals: USR1 to show, USR2 to hide (the input method<br />
module actually sends a signal to the wm).<br />
<br />
<br />
=Home and desktop=<br />
[[Image:Mokohome.png|thumb]]<br />
This app is the home for the application launchers and the desktop, which can<br />
contain widgets (for now only launcher widgets :). At some point a public API<br />
will be made available for writing widgets. They should not be D-Bus, but more<br />
like module API.<br />
In the close future there is a major issue to be fixed: single instance<br />
launchers.<br />
<br />
<br />
=The panel application=<br />
<br />
The panel is responsible for the upper side panel window, showing push<br />
notifications to the user as needed. There is also a notification list window,<br />
activated by clicking the panel window itself at any point.<br />
Notifications are pushed using a simple dbus API, available in a dbus xml file<br />
in the source code repository.<br />
The panel has also a idle screen (or screensaver) that inhibits the touchscreen<br />
when is active, preventing any user action. Screensaver is hidden by pressing<br />
the POWER button. The panel manages also display dimming.<br />
<br />
<br />
=Libmokosuite=<br />
<br />
The library is used by every app but the window manager. It contains a lot of<br />
useful functions (primarly UI utilities) connected to notification management,<br />
windows and dialogs, many fso and misc utilities, etc.<br />
Actually my aim is to write a complete UI widget library (as extension to the<br />
Elementary toolkit) for improving UI consinstency and co-operation.<br />
The library includes a basic interface (not fully working actually) to the bluez<br />
API, using Eggdbus (I wish to make it the primary Dbus library of the suite).<br />
<br />
<br />
=Hardware buttons=<br />
<br />
Hardware buttons are set to perform these events upon release:<br />
<br />
* AUX button short press - app close (applies also on keyboard)<br />
* AUX button long >2seconds press and release - go on home screen<br />
* PWR button short press lock/unlock locked screen<br />
<br />
[[User:daniele_athome]]<br />
[[Category:Telephony]]<br />
[[Category:ApplicationsElementary]]</div>Vanoushttp://openmoko.org/wiki/MokosuiteMokosuite2010-09-07T10:26:33Z<p>Vanous: gitorious</p>
<hr />
<div>{{Languages|Mokosuite}}<br />
<br />
<onlyinclude><br />
{{ApplicationBox|<br />
Name=[[Mokosuite]]|<br />
Description=Elementary based phone suite |<br />
Screenshot=MokoWM.png |<br />
Homepage=http://gitorious.org/mokosuite2|<br />
TestedOn=SHR |<br />
PackageName=mokosuite2<br />
}}<br />
</onlyinclude><br />
<br />
{{application|Mokosuite}}<br />
<br />
=Overview=<br />
<br />
The mokosuite phone suite package is made up several components. Outside the mokosuite tree there is mokowm-imf-ecore, an input method module for<br />
Ecore.<br />
<br />
{|align=center<br />
|__TOC__<br />
|}<br />
<br />
<br />
{|<br />
| [[Image:Mokohome.png|200px|thumb|Launcher]]<br />
| [[Image:Mokosettings.png|200px|thumb|Settings]]<br />
| [[Image:Mokokeyboard.png|200px|thumb|Keyboard]]<br />
| [[Image:Mokopanel.png|200px|thumb|Panel]]<br />
|}<br />
<br />
=Installation=<br />
<br />
Installation on SHR:<br />
<br />
opkg install mokosuite2<br />
<br />
=The phone application=<br />
<br />
The phone application is used to actually make phone calls. It manages also<br />
the actual connection to the GSM network.<br />
The phone app has an integrated call log and contacts list, for now stored in<br />
SQLite databases. My idea is to write my own implementation of opimd backed by<br />
mokophone.<br />
<br />
When a phone call starts or is incoming, the phone app sends notification<br />
through D-Bus to the panel, creating a green active call icon and filling the<br />
notification list with the current active call. If a call gets lost, another<br />
notification is pushed to the panel (with a red lost call icon :)<br />
<br />
<br />
=The messages application=<br />
<br />
There is actually a stub with some builtin messages, but my objective is to<br />
modify some of the opimd specs to accomplish a more threaded message management.<br />
This shall be discussed with mickeyl or anyone else is involved. We should find<br />
a way to make a custom SQL query, optimized for retrieving information about<br />
SMS threads, not wasting resources.<br />
<br />
I still have to decide to integrate e-mail support with sms... but I don't know,<br />
there are many points of view about this approach.<br />
<br />
<br />
=The settings application=<br />
<br />
<br />
<br />
This app is in charge to manage much all of the aspects of the suite and of the<br />
phone itself. For now it manages only a few things, but it's going to be a very<br />
big application :)<br />
<br />
<br />
=The mail application=<br />
<br />
Much TODO :)<br />
<br />
<br />
=The window manager=<br />
[[Image:Mokodesk2.png|thumb]]<br />
As of now, mokowm is a veeeery basic X window manager based on Ecore_X APIs,<br />
which have made things very easy. However, a phone window manager should do<br />
many things, and this will be a major part of the project.<br />
The wm right now has also a builtin simple virtual keyboard, not very complete<br />
yet, but working :)<br />
It is activable using signals: USR1 to show, USR2 to hide (the input method<br />
module actually sends a signal to the wm).<br />
<br />
<br />
=Home and desktop=<br />
[[Image:Mokohome.png|thumb]]<br />
This app is the home for the application launchers and the desktop, which can<br />
contain widgets (for now only launcher widgets :). At some point a public API<br />
will be made available for writing widgets. They should not be D-Bus, but more<br />
like module API.<br />
In the close future there is a major issue to be fixed: single instance<br />
launchers.<br />
<br />
<br />
=The panel application=<br />
<br />
The panel is responsible for the upper side panel window, showing push<br />
notifications to the user as needed. There is also a notification list window,<br />
activated by clicking the panel window itself at any point.<br />
Notifications are pushed using a simple dbus API, available in a dbus xml file<br />
in the source code repository.<br />
The panel has also a idle screen (or screensaver) that inhibits the touchscreen<br />
when is active, preventing any user action. Screensaver is hidden by pressing<br />
the POWER button. The panel manages also display dimming.<br />
<br />
<br />
=Libmokosuite=<br />
<br />
The library is used by every app but the window manager. It contains a lot of<br />
useful functions (primarly UI utilities) connected to notification management,<br />
windows and dialogs, many fso and misc utilities, etc.<br />
Actually my aim is to write a complete UI widget library (as extension to the<br />
Elementary toolkit) for improving UI consinstency and co-operation.<br />
The library includes a basic interface (not fully working actually) to the bluez<br />
API, using Eggdbus (I wish to make it the primary Dbus library of the suite).<br />
<br />
<br />
=Hardware buttons=<br />
<br />
Hardware buttons are set to perform these events upon release:<br />
<br />
* AUX button short press - app close (applies also on keyboard)<br />
* AUX button long >2seconds press and release - go on home screen<br />
* PWR button short press unlock locked screen<br />
<br />
[[User:daniele_athome]]<br />
[[Category:Telephony]]<br />
[[Category:ApplicationsElementary]]</div>Vanoushttp://openmoko.org/wiki/MokosuiteMokosuite2010-09-07T10:25:16Z<p>Vanous: /* Libmokosuite */ buttons</p>
<hr />
<div>{{Languages|Mokosuite}}<br />
<br />
<onlyinclude><br />
{{ApplicationBox|<br />
Name=[[Mokosuite]]|<br />
Description=Elementary based phone suite |<br />
Screenshot=MokoWM.png |<br />
Homepage=svn://svn.casaricci.it/openmoko/trunk|<br />
TestedOn=SHR |<br />
PackageName=mokosuite2<br />
}}<br />
</onlyinclude><br />
<br />
{{application|Mokosuite}}<br />
<br />
=Overview=<br />
<br />
The mokosuite phone suite package is made up several components. Outside the mokosuite tree there is mokowm-imf-ecore, an input method module for<br />
Ecore.<br />
<br />
{|align=center<br />
|__TOC__<br />
|}<br />
<br />
<br />
{|<br />
| [[Image:Mokohome.png|200px|thumb|Launcher]]<br />
| [[Image:Mokosettings.png|200px|thumb|Settings]]<br />
| [[Image:Mokokeyboard.png|200px|thumb|Keyboard]]<br />
| [[Image:Mokopanel.png|200px|thumb|Panel]]<br />
|}<br />
<br />
=Installation=<br />
<br />
Installation on SHR:<br />
<br />
opkg install mokosuite2<br />
<br />
=The phone application=<br />
<br />
The phone application is used to actually make phone calls. It manages also<br />
the actual connection to the GSM network.<br />
The phone app has an integrated call log and contacts list, for now stored in<br />
SQLite databases. My idea is to write my own implementation of opimd backed by<br />
mokophone.<br />
<br />
When a phone call starts or is incoming, the phone app sends notification<br />
through D-Bus to the panel, creating a green active call icon and filling the<br />
notification list with the current active call. If a call gets lost, another<br />
notification is pushed to the panel (with a red lost call icon :)<br />
<br />
<br />
=The messages application=<br />
<br />
There is actually a stub with some builtin messages, but my objective is to<br />
modify some of the opimd specs to accomplish a more threaded message management.<br />
This shall be discussed with mickeyl or anyone else is involved. We should find<br />
a way to make a custom SQL query, optimized for retrieving information about<br />
SMS threads, not wasting resources.<br />
<br />
I still have to decide to integrate e-mail support with sms... but I don't know,<br />
there are many points of view about this approach.<br />
<br />
<br />
=The settings application=<br />
<br />
<br />
<br />
This app is in charge to manage much all of the aspects of the suite and of the<br />
phone itself. For now it manages only a few things, but it's going to be a very<br />
big application :)<br />
<br />
<br />
=The mail application=<br />
<br />
Much TODO :)<br />
<br />
<br />
=The window manager=<br />
[[Image:Mokodesk2.png|thumb]]<br />
As of now, mokowm is a veeeery basic X window manager based on Ecore_X APIs,<br />
which have made things very easy. However, a phone window manager should do<br />
many things, and this will be a major part of the project.<br />
The wm right now has also a builtin simple virtual keyboard, not very complete<br />
yet, but working :)<br />
It is activable using signals: USR1 to show, USR2 to hide (the input method<br />
module actually sends a signal to the wm).<br />
<br />
<br />
=Home and desktop=<br />
[[Image:Mokohome.png|thumb]]<br />
This app is the home for the application launchers and the desktop, which can<br />
contain widgets (for now only launcher widgets :). At some point a public API<br />
will be made available for writing widgets. They should not be D-Bus, but more<br />
like module API.<br />
In the close future there is a major issue to be fixed: single instance<br />
launchers.<br />
<br />
<br />
=The panel application=<br />
<br />
The panel is responsible for the upper side panel window, showing push<br />
notifications to the user as needed. There is also a notification list window,<br />
activated by clicking the panel window itself at any point.<br />
Notifications are pushed using a simple dbus API, available in a dbus xml file<br />
in the source code repository.<br />
The panel has also a idle screen (or screensaver) that inhibits the touchscreen<br />
when is active, preventing any user action. Screensaver is hidden by pressing<br />
the POWER button. The panel manages also display dimming.<br />
<br />
<br />
=Libmokosuite=<br />
<br />
The library is used by every app but the window manager. It contains a lot of<br />
useful functions (primarly UI utilities) connected to notification management,<br />
windows and dialogs, many fso and misc utilities, etc.<br />
Actually my aim is to write a complete UI widget library (as extension to the<br />
Elementary toolkit) for improving UI consinstency and co-operation.<br />
The library includes a basic interface (not fully working actually) to the bluez<br />
API, using Eggdbus (I wish to make it the primary Dbus library of the suite).<br />
<br />
<br />
=Hardware buttons=<br />
<br />
Hardware buttons are set to perform these events upon release:<br />
<br />
* AUX button short press - app close (applies also on keyboard)<br />
* AUX button long >2seconds press and release - go on home screen<br />
* PWR button short press unlock locked screen<br />
<br />
[[User:daniele_athome]]<br />
[[Category:Telephony]]<br />
[[Category:ApplicationsElementary]]</div>Vanoushttp://openmoko.org/wiki/AtrackAtrack2010-09-06T17:02:19Z<p>Vanous: </p>
<hr />
<div>{{Languages|aTrack}}<br />
<br />
<onlyinclude><br />
{{ApplicationBox|<br />
Name=[[aTrack]]|<br />
Description=APRS tracker and communicator for mobile devices |<br />
Screenshot=ATrack-1.png |<br />
Homepage=http://atrack.googlecode.com/|<br />
TestedOn=SHR |<br />
PackageName=atrack<br />
}}<br />
</onlyinclude><br />
<br />
{{application|aTrack}}<br />
<br />
=Overview=<br />
<br />
APRS tracker and communicator for mobile devices written in [http://python.org python] / [http://trac.enlightenment.org/e/wiki/Elementary elementary]. Targeted especially for the [http://www.openmoko.org Openmoko Freerunner] it utilizes [http://www.freesmartphone.org/ FSO freesmartphone middleware framework]. Tested and used on [http://shr-project.org/ SHR], where atrack is in repos.<br />
<br />
<br />
{|align=center<br />
|__TOC__<br />
|}<br />
<br />
<br />
{|<br />
| [[Image:ATrack-title.png|200px|thumb|Front page]]<br />
| [[Image:ATrack-create.png|200px|thumb|Create object/Item/message/Query]]<br />
| [[Image:ATrack-details.png|200px|thumb|Station detail]]<br />
| [[Image:ATrack-setup.png|200px|thumb|Settings]]<br />
|}<br />
<br />
=Disclaimer=<br />
<br />
aTrack is a hobby project started out of need and interest for mobile programming. The code is not perfect but the quality might be evolving. Hopefully :)<br />
<br />
<br />
=Installation=<br />
<br />
Installation on SHR:<br />
<br />
opkg install atrack<br />
<br />
<br />
=HAM licensing explanation=<br />
<br />
Please note that usage within the aprs-is network requires amateur radio license, but for non-commercial usage you can run your own FOSS aprsd server http://sourceforge.net/projects/aprsd/, this is given by the license of the APRS protocol, both aprsd server and atrack are FOSS).<br />
<br />
The username/login is a combination of your callsign, the password is generated by ''aprspass'' program, which comes from the aprsd package on your Linux desktop.<br />
<br />
=YouLoc=<br />
<br />
Atrack can also track on different services, i.e. has support for [http://youloc.net youloc.net], but then it acts as a dumb tracker only.<br />
<br />
= Your server=<br />
<br />
You can also run a fake small perl script server [http://code.google.com/p/atrack/wiki/PrivateAPRS_IS_FakeServer PrivateAPRS_IS_FakeServer] <br />
<br />
<br />
=Features=<br />
<br />
* aprs login with a try to autoreconnect on failure<br />
* aprs filter support<br />
* receive messages/bulletins<br />
* create/reply/forward message<br />
* predefined text strings for quick messaging<br />
* predefined list of recipients <br />
* ack autosend<br />
* tracking + smart tracking - corner pegging (tracking on APRS and also on http://youloc.net/ )<br />
* packet compression used on all packets<br />
* pause tracking during phone call<br />
* send status message<br />
* send last know location<br />
* calculate locator grid<br />
* display nearby stations, objects, items<br />
* edit/save into conf file<br />
* portrait/landscape/fullscreen/day/night mode<br />
* screen dim/suspend blocking<br />
* APRS Query - replying to aprs query for position and status <br />
* send any Direct query, predefined Q for P, S, M, O, H, D<br />
* create, edit Objects and Items with predefined names<br />
* Mic-E encoded packets initial support (shows some funny failures sometimes)<br />
* display a map with position if an object/station - based on Openstreetmap or actually on http://ojw.dev.openstreetmap.org/StaticMap/<br />
<br />
=Known bugs=<br />
<br />
* tracking is sometimes reduced to bearing change only. This is probably due to the tracking function calling ecore.timer, exiting with error at some point. Ideas welcomed.<br />
<br />
<br />
=Links=<br />
<br />
* [http://code.google.com/p/atrack/wiki/Screenshots Screenshots]<br />
* [http://atrack.googlecode.com/svn/trunk/ Source code]<br />
=Requires=<br />
<br />
* [http://python.org python]<br />
* [http://trac.enlightenment.org/e/wiki/Elementary elementary]<br />
* [http://www.freesmartphone.org/ FSO freesmartphone middleware framework]<br />
<br />
<br />
<br />
[[User:vanous]]<br />
[[Category:GPS]]<br />
[[Category:GPS Applications]]<br />
[[Category:ApplicationsElementary]]</div>Vanoushttp://openmoko.org/wiki/AtrackAtrack2010-09-06T16:59:13Z<p>Vanous: initial commit</p>
<hr />
<div>{{Languages|aTrack}}<br />
<br />
<onlyinclude><br />
{{ApplicationBox|<br />
Name=[[aTrack]]|<br />
Description=APRS tracker and communicator for mobile devices |<br />
Screenshot=ATrack-1.png |<br />
Homepage=http://atrack.googlecode.com/|<br />
SourceCode=http://atrack.googlecode.com/svn/trunk/|<br />
TestedOn=SHR |<br />
PackageName=atrack<br />
}}<br />
</onlyinclude><br />
<br />
{{application|aTrack}}<br />
<br />
=Overview=<br />
<br />
APRS tracker and communicator for mobile devices written in [http://python.org python] / [http://trac.enlightenment.org/e/wiki/Elementary elementary]. Targeted especially for the [http://www.openmoko.org Openmoko Freerunner] it utilizes [http://www.freesmartphone.org/ FSO freesmartphone middleware framework]. Tested and used on [http://shr-project.org/ SHR], where atrack is in repos.<br />
<br />
<br />
{|align=center<br />
|__TOC__<br />
|}<br />
<br />
<br />
{|<br />
| [[Image:ATrack-title.png|200px|thumb|Front page]]<br />
| [[Image:ATrack-create.png|200px|thumb|Create object/Item/message/Query]]<br />
| [[Image:ATrack-details.png|200px|thumb|Station detail]]<br />
| [[Image:ATrack-setup.png|200px|thumb|Settings]]<br />
|}<br />
<br />
=Disclaimer=<br />
<br />
aTrack is a hobby project started out of need and interest for mobile programming. The code is not perfect but the quality might be evolving. Hopefully :)<br />
<br />
<br />
=Installation=<br />
<br />
Installation on SHR:<br />
<br />
opkg install atrack<br />
<br />
<br />
=HAM licensing explanation=<br />
<br />
Please note that usage within the aprs-is network requires amateur radio license, but for non-commercial usage you can run your own FOSS aprsd server http://sourceforge.net/projects/aprsd/, this is given by the license of the APRS protocol, both aprsd server and atrack are FOSS).<br />
<br />
The username/login is a combination of your callsign, the password is generated by ''aprspass'' program, which comes from the aprsd package on your Linux desktop.<br />
<br />
=YouLoc=<br />
<br />
Atrack can also track on different services, i.e. has support for [http://youloc.net youloc.net], but then it acts as a dumb tracker only.<br />
<br />
= Your server=<br />
<br />
You can also run a fake small perl script server [http://code.google.com/p/atrack/wiki/PrivateAPRS_IS_FakeServer PrivateAPRS_IS_FakeServer] <br />
<br />
<br />
=Features=<br />
<br />
* aprs login with a try to autoreconnect on failure<br />
* aprs filter support<br />
* receive messages/bulletins<br />
* create/reply/forward message<br />
* predefined text strings for quick messaging<br />
* predefined list of recipients <br />
* ack autosend<br />
* tracking + smart tracking - corner pegging (tracking on APRS and also on http://youloc.net/ )<br />
* packet compression used on all packets<br />
* pause tracking during phone call<br />
* send status message<br />
* send last know location<br />
* calculate locator grid<br />
* display nearby stations, objects, items<br />
* edit/save into conf file<br />
* portrait/landscape/fullscreen/day/night mode<br />
* screen dim/suspend blocking<br />
* APRS Query - replying to aprs query for position and status <br />
* send any Direct query, predefined Q for P, S, M, O, H, D<br />
* create, edit Objects and Items with predefined names<br />
* Mic-E encoded packets initial support (shows some funny failures sometimes)<br />
* display a map with position if an object/station - based on Openstreetmap or actually on http://ojw.dev.openstreetmap.org/StaticMap/<br />
<br />
=Known bugs=<br />
<br />
* tracking is sometimes reduced to bearing change only. This is probably due to the tracking function calling ecore.timer, exiting with error at some point. Ideas welcomed.<br />
<br />
<br />
=Links=<br />
<br />
* [http://code.google.com/p/atrack/wiki/Screenshots Screenshots]<br />
<br />
=Requires=<br />
<br />
* [http://python.org python]<br />
* [http://trac.enlightenment.org/e/wiki/Elementary elementary]<br />
* [http://www.freesmartphone.org/ FSO freesmartphone middleware framework]<br />
<br />
<br />
<br />
[[User:vanous]]<br />
[[Category:GPS]]<br />
[[Category:ApplicationsElementary]]</div>Vanoushttp://openmoko.org/wiki/File:ATrack-title.pngFile:ATrack-title.png2010-09-06T16:44:17Z<p>Vanous: </p>
<hr />
<div></div>Vanoushttp://openmoko.org/wiki/File:ATrack-details.pngFile:ATrack-details.png2010-09-06T16:43:42Z<p>Vanous: </p>
<hr />
<div></div>Vanoushttp://openmoko.org/wiki/File:ATrack-create.pngFile:ATrack-create.png2010-09-06T16:43:04Z<p>Vanous: </p>
<hr />
<div></div>Vanoushttp://openmoko.org/wiki/File:ATrack-setup.pngFile:ATrack-setup.png2010-09-06T16:42:22Z<p>Vanous: </p>
<hr />
<div></div>Vanoushttp://openmoko.org/wiki/File:ATrack-1.pngFile:ATrack-1.png2010-09-06T16:39:24Z<p>Vanous: aTRack around page</p>
<hr />
<div>aTRack around page</div>Vanoushttp://openmoko.org/wiki/Manuals/SHRManuals/SHR2010-09-05T12:10:20Z<p>Vanous: /* Booting */</p>
<hr />
<div>{{Languages|Manuals/SHR}}<br />
{| align="right"<br />
| __TOC__<br />
|}<br />
<br />
==SHR Introduction==<br />
<br />
Welcome to '''[[SHR]]''', a community driven distribution for (not only) Openmoko, HTC Dream, PalmPré and Nokia n900 phones.<br />
<br />
<br />
<br />
[[Image:SHR-Logo.png|200px|thumb|center|SHR]]<br />
<br />
'''SHR''' (Stable Hybrid Release) is here to provide you with Root FileSystem images that you can easily install into your device to use as a daily phone and PDA. There are many prepackaged programs available that can be installed upon demand by users, it can also be used by developers as a base image for customized and flavored distribution or release. '''SHR unstable (SHR-U)''' is a testing environment before software gets stabilized and it is the main testing ground for [[FSO]] releases. '''SHR testing (SHR-T)''' images provide as much stability as possible for day-to-day usage.<br />
<br />
==Installation==<br />
<br />
===Getting SHR===<br />
<br />
You need to download two files for your version as above: kernel and root filesystem. Depending whether you will be installing into the internal [[NAND memory]] or on the [[microSD]] card, you need to either get .jffs2 file for NAND or .tar.gz file for microSD.<br />
<br />
- Get the latest kernel from the below linkpages. Starts with uImage-...<br />
<br />
- Get the root filesystem, for NAND: full-om-gta0_.jffs2, for µSD: full-om-gta0_.tar.gz<br />
<br />
The above are '''full''' images. You can also choose images with less packages, marked as '''lite'''.<br />
<br />
;GTA02 Neo FreeRunner<br />
*testing line: http://build.shr-project.org/shr-testing/images/om-gta02/<br />
*unstable 2.6.3* line: http://build.shr-project.org/shr-unstable/images/om-gta02/<br />
*( unstable 2.6.29 line: http://build.shr-project.org/shr-unstable.29/images/om-gta02/ )<br />
<br />
;GTA01 Neo 1973<br />
*testing line: http://build.shr-project.org/shr-testing/images/om-gta01/<br />
*unstable 2.6.29 line: http://build.shr-project.org/shr-unstable.29/images/om-gta01/<br />
<br />
;Image lite to image full<br />
If you flashed a '''lite''' image and want to upgrade to the '''full''' image run:<br />
<br />
opkg update<br />
opkg install task-shr-apps task-shr-games task-shr-gtk<br />
<br />
;Kernel modules<br />
The images of the filesystems mentioned above (.jffs2, .tar.gz), already contain the newest kernel modules.<br />
<br />
Get the new kernel modules if you only want to flash a new kernel, but not a whole new file system. From the same page as the kernel download the modules to match your kernel (their dates should be the same). Use sftp to put that file on the FreeRunner via the usb connection. Run gzip to unwrap the modules:<br />
# gzip -dc modules-...tar.gz | tar -xf - -C /<br />
<br />
===Installation on Flash===<br />
<br />
In order to install your SHR distribution directly to your FreeRunner Flash memory (NAND), you need to get the desired filesystem file ( <tt>.jffs2</tt> ) as described above and flash your device using the <tt>dfu-util</tt> tool.<br />
<br />
Please visit [[Flashing the Neo FreeRunner]] for more details about flashing and see [[Dfu-util]] for detailed information about the dfu-util.<br />
<br />
{{Note|Your battery must be charged (sufficiently) before NAND flashing. Symptom of insufficient charge: Your progress bar "####" stops while flashing. If so, you must charge, and later you should be able to make the complete flash.}}<br />
Commands to flash the filesystem and the kernel:<br />
<br />
for the GTA02 Neo FreeRunner:<br />
<br />
# dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D full-om-gta02.jffs2<br />
# dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-om-gta02-latest.bin<br />
<br />
for the GTA01 Neo 1973:<br />
<br />
# dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a rootfs -R -D full-om-gta01.jffs2<br />
# dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a kernel -R -D uImage-om-gta01-latest.bin<br />
<br />
===Installation on the microSD Card===<br />
<br />
Installing SHR on your microSD Card depends on the Bootloader you are using, ''uBoot'' or ''Qi''.<br />
<br />
In simple words, the difference between both systems resides on how you must prepare your microSD Card and files you use to fill them:<br />
<br />
* If you use ''uBoot'', you need to create two partitions. First partition, not so big, in FAT16 or ext2 where you have to place the kernel file (<tt>uImage-om-gta02-latest.bin</tt>) and second partition in ext2 or ext3 where you have to uncompress the filesystem file (<tt>shr-image-om-gta02.tar.gz</tt>).<br />
<br />
* If you use ''Qi'', you only need an ext2 partition into your µSD Card where you uncompress the filesystem image file (<tt>shr-image-om-gta02.tar.gz</tt>). In this case Qi Bootloader is going to look for the kernel image into the <tt>/boot</tt> directory for file named <tt>uImage-GTA02.bin</tt> .<br />
<br />
===Bootloaders===<br />
<br />
Make sure you have recent and correct versions of [[Booting_from_SD | uBoot]] or [[Qi]] installed, please visit the links for detailed information and tips. For example [[Android]] uses modified [[Qi]] which can cause you troubles when using SHR.<br />
<br />
===SHR version===<br />
<br />
Should you ever later wonder what version of SHR you have actually installed, please run<br />
<br />
timestamp of image creation:<br />
cat /etc/timestamp<br />
<br />
latest shr version from opkg upgrade (this version is changed everytime someone builds task-base on shr buildhost):<br />
cat /etc/shr-version<br />
<br />
{{Note|Please note that this is true only for shr-u, with shr-t running opkg update;opkg upgrade does not change the SHR version. Only flashing or a new image download can change the SHR version. But this will be also merged to shr-t later.}}<br />
<br />
==Running SHR==<br />
<br />
===First boot===<br />
[[Image:Shr-boot-preview.png|200px|thumb|center|SHR Boot Splash screen]]<br />
<br />
First boot usually takes a bit longer as your phone's new software needs to do some initial setting up. It is recommended to reboot after this first boot (and after the initial setup), to make sure that all packages get initialized properly. The application switching shelve (shr_elm_softkey) doesn't show up during first boot when the initial wizards are at work, [http://shr-project.org/trac/ticket/1105 reboot is required] and then application switching works as expected.<br />
<br />
====Initial Setup====<br />
<br />
During the first run, Setup is automatically initiated to walk the user through basic setup of the Enlightenment desktop environment. These steps vary as both Enlightenment desktop and SHR evolve, at this point preferred language and desktop profile options are available. The Profile offers to choose a preconfigured way of displaying the desktop. Illume2-SHR (with continuous development) and Illume-SHR (discontinued) profiles are available. '''Illume2-SHR''' is the recommended Profile. <br />
<br />
{| class="wikitable"<br />
| [[Image:SHR-Setup-Language.png|200px|thumb|language selection]]<br />
| [[Image:SHR-Setup-Profile.png|200px|thumb|theme selection]]<br />
| [[Image:SHR-Wizard.png|200px|thumb|SHR Wizard]]<br />
<br />
|}<br />
<br />
Note, you may need to ssh into the device and run /usr/bin/xinput_calibrator_once.sh if calibration is wrong. I found this using a Neo1973 and SHR images from around May 2010.<br />
<br />
====SHR Wizard====<br />
After the initial Setup, SHR Setting Wizard is launched to allow setting up your local phone settings and setting up root password. Sometimes a '''Please wait''' message is displayed for a long time, as the wizzard is waiting for the SIM card to be initialized.<br />
<br />
===First look===<br />
[[Image:SHR-First-Look.png|200px|thumb|Desktop screen]]<br />
[[Image:SHR-Task-Buttons.png|200px|thumb|Task switch buttons]]<br />
====Illume desktop====<br />
Illume desktop is the default home screen of the SHR desktop. <br />
<br />
Application definition files located in /usr/share/applications are displayed here as icons. All applications are ran fullscreen and you can switch between them by using the the '''< left''' or '''right >''' arrows on sliding shelve available by tapping Top Shelf on any empty space. To close applications, choose '''X''' from the same sliding shelve.<br />
<br />
Several icons (e-gadgets) are placed in the Top Shelve:<br />
<br />
The '''L''' icon is to switch between left/right mouse click. By taping this icon the icon gets changed to R and next tap will be as right click. After the click, the behavior is automatically switched back to Left click so any following taps are left click again.<br />
<br />
'''Mode Switch Icon''' allows to split the screen horizontally or vertically, thus allowing to display two applications at the same time.<br />
<br />
'''Keyboard icon''' pops up or hides the Keyboard.<br />
<br />
'''Illume Settings''' icon (represented by SHR logo) invokes the [[#Illume_settings | Illume desktop settings]]. <br />
<br />
'''Home Icon''' allows quick go to the home desktop/application.<br />
<br />
'''GSM''' and '''Battery''' status icons, as well as '''time''' are displayed by default, Bluetooth and WiFi status icons available in the setting of the Top Shelve content.<br />
<br />
<br />
To '''reconfigure the Top Shelve''' itself, use the L/R click icon to Right click on the Top Panel and choose: Illume Indicator->Set Content to add or remove items from the Top Panel. Or, upon right click on the Top Panel you can also choose Illume Indicator->Begin Move/Resize to move your icons around. To escape this mode, you must click on the L/R gadget's edge, it will switch to L, then choose R again, right click on the Top Panel and select Illume Indicator->Stop Move/Resize.<br />
<br />
<br />
====Keyboard====<br />
<br />
Keyboard comes up automagically when a text field is tapped or you can also toggle the keyboard by it's icon in the Top Shelve. In the Keyboard, dictionary switcher is the arrow-up on left side, alternative keyboard layouts are under the ABC button on the right. The Default keyboard has English dictionary enabled. For Space quick slide left-to-right, for Enter, quick slide up-down, to quick change keyboard layout quick slide down-up. While typing with a dictionary enabled keyboard, possible word options start appearing in the keyboard's upper part or more word options are available under the arrow-up on the left. When happy with the word, tap it, it will be pasted into the text field with a space attached. The Keyboard and dictionary can [[#Illume_keyboard_and_dictionaries | easily be localized]].<br />
<br />
====Copy and Paste====<br />
<br />
In '''E based''' applications, for example the phone suite (contacts, messages...), by tapping and holding down for over two seconds the Select-Paste menu will pop up. By pressing Select, you can now swipe through the text to select desirable part. Tap and hold down again, Copy-Cut-Cancel menu will appear to Copy to clipboard. Another long tap will provide Select-Paste for Paste.<br />
<br />
In '''Gtk''' based application, you can use keyboard for Ctrl-C (Copy) and Ctrl-V (Paste) or items in Menu if provided.<br />
<br />
In the Vala '''Terminal''', you can select simply by swiping through the text and for Paste there is an icon in the menu bar of this application.<br />
<br />
Copy & Paste between different toolkits has some limitations. See the table below. In Ventura, select is possible, but copy/paste doesn't seem to work at all.<br />
<br />
{| cellspacing="0" class="wikitable" border="1" style="font-size: 85%; text-align: left;width="100%"<br />
|-<br />
! From -> To <br />
! to GTK<br />
! to E<br />
! to Terminal<br />
|-<br />
| from GTK<br />
|style="background:#88FF88;"|Works<br />
|style="background:#88FF88;"|Works<br />
|style="background:red"|Doesn't work <br />
|-<br />
| from E<br />
|style="background:red"|Doesn't work <br />
|style="background:#88FF88;"|Works <br />
|style="background:#88FF88;"|Works<br />
|-<br />
| from Terminal<br />
|style="background:red"|Doesn't work <br />
|style="background:#88FF88;"|Works <br />
|style="background:#88FF88;"|Works<br />
|-<br />
|}<br />
<br />
====Alarm====<br />
<br />
The Alarms application (installed by default) allows alarm presetting for single or repeatable alarms. If you set an alarm and turn your Openmoko FreeRunner off, at the time of the alarm the phone will be powered up and alarm will sound.<br />
<br />
====Phone applications====<br />
<br />
Besides other software, SHR comes with 4 main phone applications: ''Dialer'', ''Contacts'', ''Messages'' and ''Phone log''.<br />
<br />
{|<br />
| [[Image:SHR-Dialer.png|200px|thumb|Dialer]]<br />
| [[Image:SHR-Contacts.png|200px|thumb|Contacts]]<br />
| [[Image:SHR-Mesages.png|200px|thumb|Messages]]<br />
| [[Image:SHR-Phonelog.png|200px|thumb|Phone log]]<br />
|}<br />
<br />
<br />
=====PIM data=====<br />
<br />
======Storage======<br />
PIM data (contacts, messages etc.) are stored through internal opimd storage mechanism into <br />
<br />
/etc/freesmartphone/opim/pim.db<br />
<br />
This database can easily be copied from one SHR installation to another, for example due to a need for reflashing. The Contacts application can display a picture of the contact. As the pim.db database contains a path to the picture files only but not the pictures themselves, therefore, in case of PIM data backup or transfer, these picture files '''need to be copied too'''.<br />
<br />
======SIM Contacts======<br />
<br />
SHR phone applications do not read SIM contacts by default but you can use SIM Manager to access your SIM contacts '''SHR Settings -> Others -> SIM Manager''', which allows you to edit and import the SIM contacts into the internal storage. You can also use Pisi to import your SIM contacts into opimd.<br />
<br />
======Synchronization======<br />
<br />
'''[[Pisi]]''' is an application for synchronizing PIM data and can be used for import and export your contacts, calendar entries etc. between various sources, like VCF, LDAP, Google and more. To install Pisi:<br />
<br />
opkg install pisi<br />
<br />
After installation, edit Pisi configuration in '''.pisi/conf''' in your home directory. To have a correct opimd fields support, make sure '''field_support=TRUE''' is enabled in opimd section.<br />
<br />
With the installed package you have a well-documented sample that is placed at <br />
/usr/share/doc/pisi/conf.example<br />
You may copy the file and rename this file to<br />
/home/root/.pisi/conf<br />
as a starting point - then edit this file in order to configure your PIM synchronization data sources. Look at section<br />
<br />
[opimd]<br />
description=OPIMD Contacts<br />
module=contacts_opimd<br />
field_support=TRUE<br />
<br />
=====Idle screen=====<br />
[[Image:SHR-Idle_Screen.png|200px|thumb|Idle Screen with GSM operator strength and name. GPS, WiFi, Display and CPU are requested, Battery status.]]<br />
Upon press of the AUX button Idle Screens locks up the display. AUX press or a finger slide on the Slider unlocks the screen.<br />
<br />
At the top, status icons are shown to indicate what is going on in the phone:<br />
<br />
From left to right:<br />
GSM strength and operator. Requested Resources (GPS, Display etc., when for example Display is requested, the screen will not dim). Battery capacity.<br />
<br />
====Hardware Buttons====<br />
<br />
=====Power Button=====<br />
<br />
[[Image:SHR-Quick-Settings.png|200px|thumb|Quick Settings]]<br />
<br />
The '''PWR''' (Power) button is mapped to start [[#quick_settings | Quick Settings]] screen (Illume System menu in older versions) on a short press. <br />
<br />
Mapping of the PWR button be configured via the '''Illume Settings-> Input -> Key Bindings'''.<br />
<br />
Pressing the Power button for longer then 8 seconds will force a complete power down of the device. This is hardconfigured in the kernel.<br />
<div id="quick_settings"> </div><br />
The '''Quick Settings''' screen provides several toggles: Airplane mode, Phone profiles, Power settings and Power buttons.<br />
<br />
=====Auxiliary Button=====<br />
The '''AUX''' (Auxiliary) button is mapped to toggle on/off the SHR Idle screen. Mapping of this button is configured in /etc/phonefsod.conf<br />
<br />
idle_screen = aux,lock<br />
<br />
You can configure the [[#idle_screen | Idle Screen]] to come up even during active phone call by adding '''phone''' to the setting: <br />
<br />
idle_screen = aux,lock, phone<br />
<br />
<div id="idle_screen"> </div><br />
The '''Idle Screen''' shows current date and time, missed calls and messaged and also what [[#FSO_Resources | FSO resources]] are currently being requested - used.<br />
<br />
======Replacing idle screen======<br />
<br />
If you wish to use the E simple LOCKED screen instead of the SHR Idle Screen, edit '''/etc/phonefsod.conf''' to this:<br />
<br />
# when to show idle screen<br />
# ...<br />
# idle_screen = aux,lock<br />
idle_screen =<br />
<br />
You need to restart phonefsod to make the change happen.<br />
<br />
Also, change key mapping for the AUX button by setting '''Illume Settings''' -> '''Input''' -> '''Key Bindings''', bind the key '''XF86Phone''' to '''Desktop Simple Lock'''<br />
<br />
====Settings applications====<br />
<br />
Many desktop and phone settings are possible to do via graphical interface. [[#SHR_Settings | SHR Settings]] provides access to most common phone personality settings and is accessible by tapping Settings icon on the desktop. [[#Illume_settings | Illume settings]] (and Enlightenment desktop settings) are accessible on Top shelve by tapping the "SHR Logo" icon. Also, FSO and SHR phoneui applications have configuration files in /etc where some of the above mentioned apps write and that can be edited manually.<br />
<br />
===First steps===<br />
<br />
Right after installation and first boot you might want to do a few initial steps like adjusting the call volume and some other tasks.<br />
<br />
====Audio - Call Volume====<br />
<br />
During the first phone call please use the Volume and Mic sliders on the Active Call Screen and adjust them to fit your preferences. The new improved settings will be used for all in/out-going calls thereafter.<br />
<br />
====Network Connection====<br />
<br />
[[#Networking|Establish network connection]] and SSH into your phone. You can establish connection either via USB to your desktop and enable NAT or you can connect through Wifi.<br />
<br />
====Initializing the opkg database====<br />
''Initialize the opkg database'' in order to install some applications from SHR repositories or from other sources, for example [http://opkg.org opkg.org]. While being online, you need to run<br />
<br />
opkg update<br />
<br />
Searching in the opkg database can take a long time. You can speed things up by dumping the database into a file and grepping it through. Do this only once or after every opkg update:<br />
<br />
opkg list > packages.txt<br />
<br />
Then you can search quickly for package name, for example for [[Navit|navit]]:<br />
<br />
grep navit packages.txt<br />
<br />
====SwapSpace====<br />
<br />
When the RAM is used up, applications get killed. This is particularly bad while doing opkg upgrade. Therefore you might want to create a swap space. Read [[SwapSpace]] article or the [http://shr-project.org/trac/wiki/swap swap article on the SHR wiki].<br />
<br />
==Settings==<br />
===SHR Settings===<br />
[[Image:SHR-Settings-main.png|200px|thumb|SHR Settings]]<br />
<br />
SHR Settings is the main setting application of SHR. It provides an easy way of setting up your phone to your liking - from phone related settings, to requesting resources in order to prevent screen dim or suspend (for example while using GPS).<br />
<br />
Please refer to [[#FSO_Resources | this section]] about a better way to manage preventing screen dim or suspend.<br />
<br />
While some settings are persistent over reboots, others are not.<br />
<br />
====Main Screen====<br />
The main screen is divided into eight categories, which contain several modules. Every SHR Settings module has a specified task - for example controlling the GSM antenna power, setting the time etc.<br />
<br />
====Phone====<br />
Here you can set if the GSM antenna is on and if your phone number is shown when you call someone.<br />
<br />
'''GSM'''<br />
In GSM settings you can turn off and on GSM module. After turning off antenna, whole GSM modem is turned off.<br />
<br />
To list available providers, click on Operators button. Scanning can take some time. After a while, a list of operators should pop up.<br />
<br />
You can't connect to operators marked [forbidden].<br />
<br />
Selecting an operator from the list also changes modem registration mode to manual. It won't register to other network, even if some is available and has better signal strengh. To return to automatic mode, click "Automatic" button in operator list.<br />
<br />
'''Call'''<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Phone.png|200px|thumb|Phone settings]]<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-List-providers.png|200px|thumb|List providers]]<br />
<br />
|}<br />
<br />
You can set if your phone number should be displayed to other party. You can either depend on network decision ("By network") or force it manually ("Manual")<br />
<br />
'''Phoneutils'''<br />
<br />
For the default SHR phone applications to be able to correctly parse incoming calls/messages and match them with your contacts, you will need to set the right country code for your location. (for example 420 for Czech republic) for more info, please go to: http://wiki.openmoko.org/wiki/Phone_Prefixes<br />
<br />
'''SIM'''<br />
<br />
Here you can view some informations about your SIM card and clean phone and messagebooks.<br />
<br />
====Profiles====<br />
<br />
Here you can select the current profile, which the device should use to determine ring tone etc.<br />
<br />
'''Current profile'''<br />
<br />
Here you can adjust properties of the currently used profile. <br />
<br />
To change the ring tone, click the "Change" button.<br />
<br />
To use your own ring tone, place it in /usr/share/sounds directory.<br />
<br />
After selecting a sid tune as the ring tone, there are available controls to select tune number from the file.<br />
<br />
If you like to test a .sid you can play it using this command on the FR:<br />
<br />
gst-launch filesrc location=Arkanoid_PSID.sid ! siddec tune=2 ! alsasink<br />
<br />
Note that it's a ! used and not a | to construct the gstreamer pipe command.<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Profiles.png|200px|thumb|Profiles]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Profiles-Ringtones.png|200px|thumb|Ringtones]]<br />
<br />
|}<br />
<br />
====Connectivity====<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Connectivity.png |200px|thumb|Connectivity top]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Connectivity2.png |200px|thumb|Connectivity bottom]]<br />
|}<br />
<br />
'''WiFi'''<br />
<br />
With the "WiFi radio" toggle you can set, if the wifi module is powered. WiFi radio has to be turned on before trying to connect to a WiFi network, unless you try to connect through [[Mokonnect]] which is capable of powering it up.<br />
<br />
'''GPRS'''<br />
<br />
To enter APN, login and password fields, just click on the actual value (default: "internet"). Your phone provider can provide the required configuration options.<br />
<br />
{{Note|You can also use Mokonnect to manage your GPRS connection}}<br />
<br />
'''USB'''<br />
<br />
With this toggle you can switch USB port between device (Neo to PC) or host (device to Neo) modes.<br />
<br />
'''Bluetooth'''<br />
<br />
To power up Bluetooth module, switch the "Bluetooth radio" toggle to "On". After that, the "Visibility" toggle should arrive - set it to "On" if you want your FR to be visible by other Bluetooth devices on scanning.<br />
<br />
====Power====<br />
<br />
'''Battery'''<br />
<br />
This module displays informations about battery state - charge, voltage, remaining time etc. To update the data, click the "Update" button.<br />
<br />
Here you can also force enable 500mA charging.<br />
<br />
'''Display'''<br />
<br />
With this slider you can easily set the backlight brightness.<br />
<br />
{{Note|This setting isn't permanent over sessions. At boot backlight is set back to 80%.}}<br />
<br />
'''Power'''<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Power.png |200px|thumb|Power]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Timeouts.png |200px|thumb|Timeouts]]<br />
|}<br />
<br />
'''Timeouts'''<br />
<br />
Timeouts are reached in this order: Busy state -> idle -> idle dim -> idle prelock -> lock -> suspend. <br />
<br />
{{Note|Storing of this setting via D-bus calls is not supported in the new API of Vala rewrite of FSO2 and therefore SHR Settings doesn't have a functional setting for this.}}<br />
<br />
You can set values of idle timeouts manually. The default parameters are stored in '''/etc/freesmartphone/conf/GTA02/fsodeviced.conf''' but customized '''.fsodeviced.conf''' file in your home directory will take precedence (if it exists, the one in /etc/... will be ignored, so you have to copy the whole file and tweak it):<br />
<br />
[fsodevice.kernel_idle]<br />
suspend = 20<br />
lock = 2<br />
idle_prelock = 12<br />
idle = 10<br />
idle_dim = 20<br />
<br />
To turn off a timeout, set it to -1.<br />
<br />
====Appearance====<br />
<br />
'''Theming'''<br />
[[Image:SHR-Neo-Theme.png|200px|thumb|Neo theme]]<br />
<br />
The Apperance section allows you to change between installed themes. To install more themes, see also [[#Installing themes | Installing themes]].<br />
<br />
You can change finger size - this will mainly effect vertical spacing between widgets.<br />
<br />
Switching between engines:<br />
<br />
E can be switched to use different engines. The default engine is x11. Alternative engine x11-16 is not supported and results in buggy behavior of several applications, for example the phone suite or Ventura browser. It's usage is not recommended.<br />
<br />
Changing system boot Splash screen is also possible in this module. To install more splash screens, see also [[#Installing splash screen themes|Installing splash themes]].<br />
<br />
====Position====<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-GPS.png |200px|thumb|center|GPS]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-GPS-Satelites.png |200px|thumb|GPS Satelite details]]<br />
|}<br />
<br />
'''GPS'''<br />
<br />
By default, GPS is turned on only when requested by an application. That state corresponds to "Auto" setting. After changing to "Manual", you can force set it to on or off.<br />
<br />
'''GPS information'''<br />
<br />
This page can be used to monitor GPS status. You either have to turn GPS on manually or start another application to enable the GPS.<br />
<br />
You can also view information about every visible satellite and check, which are used for getting a fix. To do that, click "Satellite details".<br />
<br />
'''Remove AGPS data'''<br />
If you experience problems with GPS, turn it off, click "Remove AGPS data" and reboot your Neo.<br />
Assisted GPS ([[aGPS]]) support GPS receiver to find position by non-satellite information.<br />
<br />
====Date/time====<br />
<br />
[[Image:SHR-Settings-Date-Time.png |200px|thumb|Date & Time]]<br />
<br />
'''Time'''<br />
<br />
Here you can view and set the time. By default, the time is just displayed, To adjust it, click on "Set time".<br />
<br />
After finishing adjusting, click the "OK" button.<br />
<br />
'''Date'''<br />
<br />
This module displays the current date.<br />
<br />
====Others====<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
[[Image:SHR-Settings-Others.png |200px|thumb|Others]]<br />
<br />
'''PIM'''<br />
<br />
Pim data are stored in opimd domains. Every opimd domain has different backends to store its data to. The domain reads data from every backend and writes data to the default backend. This elector allows you to choose the backend that stores newly generated data, it doesn't copy or move existing data to a different backend.<br />
<br />
'''Services'''<br />
<br />
The services selector is listing scripts from /etc/init.d/ directory.<br />
<br />
After clicking on a servis, you can either start, restart or stop the service and view the result.<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Services.png |200px|thumb|center|Services]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Service-restart.png |200px|thumb|Services debug screen]]<br />
|}<br />
<br />
<br />
'''Userspace backups'''<br />
<br />
Here you can either archive or restore your files and configurations.<br />
<br />
=== Illume settings ===<br />
<br />
The Illume desktop can be easily customized - tap the Settings icon (SHR Logo) on the Top Shelve.<br />
<br />
'''Illume settings''' provides various options to alter the desktop environment. You can change sizes of elements, single or double click, wallpaper. To access all the various options, open Illume Settings and slide the visible icons to the left, to view more options on the right hand side.<br />
<br />
Some setting screens are not resized properly to fit the phone's display - for example the Wallpapper setting. This is a known bug already reported upstream.<br />
<br />
<!-- [[Image:SHR-Top-Shelve.png|200px|thumb|Top Shelf]] --><br />
<br />
==Localization==<br />
<br />
=== Localize SHR manually ===<br />
<br />
[[Image:SHR-Illume-Settings-Languages.png|200px|thumb|Setting Language]]<br />
<br />
====Desktop environment====<br />
<br />
You can change the language of the SHR desktop environment by using the Settings of Illume. For Example, for Czech language: in the Illume top shelf go to Settings (SHR Logo) -> Language -> Language Settings -> and choose: Čeština. If your language is not in the menu you can install by using opkg.<br />
<br />
You can list all available languages by running:<br />
<br />
opkg list | grep eglibc-locale-<br />
<br />
And install the language of your choice (for example czech):<br />
<br />
opkg install eglibc-locale-cs<br />
<br />
After this, the Language Settings of Illume will offer Czech. <br />
<br />
This will localize the Illume environment and will also set correct lang environment variable of your desktop. <br />
<br />
====Applications====<br />
<br />
If you wish to have other applications localized, you need to install translation for each of them (presuming it is available):<br />
<br />
This will install czech localization for SHR phone applications, SHR Settings and TangoGps:<br />
<br />
opkg install libframeworkd-phonegui-efl-locale-cs shr-settings-locale-cs tangogps-locale-cs<br />
<br />
====Terminal environment====<br />
<br />
For localized terminal environment (ssh login) set lang variables in /etc/profile.d/locale.sh, example for Czech language:<br />
<br />
export LANG=cs_CZ<br />
export LC_ALL=cs_CZ<br />
<br />
====Illume keyboard and dictionaries====<br />
[[Image:Illume-keyboards-terminal-dutch-nl-screenshot.png| Dutch terminal virtual keyboard|256px|thumb]]<br />
→ more details on page [[Illume keyboard]]<br />
<br />
Unlike other input methods for mobile devices, the Illume keyboard is corrective rather than predictive. It detects what you mean, even if some letters mistyped. If you accidently hit some keys next to the correct one Illume still reckognizes the word. This kind of compensates for the small size of the keys. Keep a key pressed for a longer time to affirm you really mean it. <br />
<br />
An English dictionary is used by default. A few dictionaries for other languages are included in the SHR distribution. In addition, every dictionary for [http://en.wikipedia.org/wiki/MySpell myspell] can be used. <br />
<br />
You can install a different keyboard with a layout which fits your language or alternatives for the default keyboards like the numerical one. The localized [[Illume keyboard]]s are available in the SHR repository under the name ''illume-keyboard-LANG''.<br />
<br />
==== German (and Austria) Language ====<br />
<br />
See [[Configure_SHR_for_German-speaking_use]] for detailed customization for german speaking.<br />
<br />
===Date and time===<br />
{{Note|This needs a complete and correct rewrite.}}<br />
<br />
Date and time are automatically set from GPS or Network. The easiest way of setting the time for the first time is to run TangoGps (GPS & Map icon) and obtaining GPS fix. Time will then be set automatically.<br />
<br />
The local timezone is automatically retrieved from the GSM network.<br />
<br />
It is possible to instruct framework on how to set the time and timezone in /etc/frameworkd.conf :<br />
<br />
[otimed]<br />
# a list of time/zone sources to use or NONE<br />
timesources = GPS,NTP<br />
zonesources = GSM<br />
# use an ip address here, otherwise DNS resolution will block<br />
ntpserver = 134.169.172.1<br />
<br />
To disable automatic date/zone settings, simply create an empty [otimed] section in /etc/frameworkd.conf<br />
<br />
Timezone change<br />
<br />
Create a symlink named /etc/localtime which points to the appropriate file in /usr/share/zoneinfo. For example, if you're in France., the following command will link the correct zoneinfo file to your /etc/localtime, giving you the correct time:<br />
<br />
ln -sf /usr/share/zoneinfo/Europe/Paris /etc/localtime<br />
<br />
Afterwards, edit /etc/timezone if necessary [?]<br />
<br />
Local timezone work instantly for the current boot when:<br />
<br />
TZ="Europe/Paris"<br />
export TZ<br />
<br />
For a permanent timezone change edit /etc/profile and change to:<br />
<br />
TZ="Europe/Paris"<br />
<br />
<br />
If you use UTC time, set '''UTC=yes''' in '''/etc/default/rcS'''.<br />
<br />
Adjusting time manually:<br />
<br />
Via SHR-Settings -> Date/time -> Set time<br />
<br />
From linux based desktop:<br />
<br />
ssh root@192.168.0.202 "date -u -s `date -u +%m%d%H%M%Y.%S`"<br />
<br />
The above does NOT work from Ubuntu as of 4/2/2010, the proper format is:<br />
<br />
ssh root@192.168.0.202 "date -u -s `date -u +%Y.%m.%d-%H:%M:%S`"<br />
<br />
Set the hardware clock to the system time:<br />
<br />
hwclock --systohc<br />
<br />
Is this better?:<br />
<br />
hwclock --utc --systohc<br />
<br />
==FSO Resources==<br />
<br />
[[FSO]] is in control of each device. These are called ''resources''. If the software wanting to use the device is capable of requesting this resource via <tt>d-bus</tt>, FSO will do this, otherwise you might need to power the device manually. After the requested resource is released, FSO will power it down. Manual resource request can be done through ''SHR Setting'' or you can use <tt>fsoraw</tt> command. (Using fsoraw is faster and better than running dbus commands)<br />
<br />
opkg install fsoraw<br />
<br />
Example of usage fsoraw:<br />
<br />
fsoraw -r Display mokomaze<br />
<br />
See [[FSO Resources]] for more details on using the following resources:<br />
<br />
'''Wifi'''<br />
<br />
Unless this resource is enabled you've no eth0 and wifi module is completely un-powered. Use the [[Mokonnect]] network manager to set up networks, it will power Wifi up automatically when needed.<br />
<br />
'''Bluetooth'''<br />
<br />
You need to have this resource requested to have bluetooth module powered.<br />
<br />
'''GPS'''<br />
<br />
The fso-gpsd is a daemon waiting for gsmd connections, automatically powering the device on and off. When a connection exists, it powers up the GSM. In SHR Settings you can switch GPS completely off SHR Settings -> GPS -> Manual > Off<br />
<br />
'''GSM'''<br />
<br />
You need to have this resource requested to have GSM module powered.<br />
<br />
'''Display'''<br />
<br />
While this resource is requested the display won't be blanked and suspend is disabled.<br />
<br />
'''CPU'''<br />
<br />
While this resource is requested then suspend is disabled. Display will blank as normal.<br />
<br />
'''Test'''<br />
<br />
A test resource.<br />
<br />
'''UsbHost'''<br />
<br />
While this resource is requested the USB is turned into powered USB Host mode.<br />
<br />
'''Accelerometer'''<br />
<br />
You need to have this resource requested to have the Accelerometer module powered.<br />
<br />
==Networking==<br />
<br />
There are several ways of networking - Wifi, USB, Bluetooth and Gprs:<br />
<br />
===USB===<br />
<br />
By default, USB networking is enabled in <tt>/etc/network/interfaces</tt>, where enhanced configuration can be direct edited. The phone default IP address is 192.168.0.202. Some setup is required on the desktop side, please read [[USB Networking]].<br />
<br />
===WiFi===<br />
<br />
WiFi manager [[iliwi]] is available by default for search/connect/making default a wifi connection. ''iliwi'' uses key only in hex format. The Wifi device is not required to be manually turned on via SHR-Settings as ''iliwi'' will automatically enable the device when needed and disable it after use. iliwi needs to stay running to keep the WiFi connection enabled.<br />
<br />
When WiFi is connected, the Idle screen show the icon of the WiFi resource being occupied.<br />
<br />
===GPRS===<br />
<br />
GPRS Credentials are set during the first run in SHR Wizard and you may edit them at any time via SHR settings or direct editing of /etc/phonefsod.conf. GPRS connection can then be established/closed via SHR Settings or through SHR Quick Settings (available under the Power button). SHR Quick Settings - Network tab allows also connection sharing - this will share the GPRS connection with USB network and run DHCP server to provide the client with an IP address.<br />
<br />
When GPRS is connected, the idle screen shows a small G above the signal strength indicator.<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |<br />
[[Image:SHR-Gprs-Share.png|200px|thumb|GPRS + Connection sharing]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " | <br />
[[Image:SHR-Iliwi-Scan.png|200px|thumb|Iliwi WiFi scanning]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " | <br />
<br />
[[Image:SHR-Iliwi-Connect.png|200px|thumb|Iliwi WiFi connecting]]<br />
<br />
|}<br />
<br />
==Bluetooth==<br />
<br />
Bluetooth can be used for several different applications - file transfer (OBEX), networking, input devices (HIDD), music playing (A2DP), calling etc. In some occasions, the devices need to be authorized - paired. At the moment, support for some bluetooth functions is better than for others - it is possible to do all mentioned above with the notice that phone calls with bluetooth headset are always routed to the bluetooth even if the bluetooth headset is not around, making it quite difficult to use.<br />
<br />
In the SHR repositories are applications ready to be installed (by opkg) that already do provide bluetooth support. This means that they request the bluetooth resource automatically, can search bluetooth devices around, help you with pairing and can perhaps even reconnect bluetooth headset upon resume from suspend. From applications that have some bluetooth support some are for example [[Launcher]] (home screen launcher and phone suite), [[Podboy]] (podcast player), [[Elmtooth]] (bluetooth manager). In order to set up bluetooth for phone calls, some manual setup from [[#GSM_phone_calls_with_bluetooth_headset | bellow]] is still required.<br />
<br />
===Bluez3 - the manual non D-Bus way===<br />
<br />
If you want to use the bluetooth device directly, you need to turn the bluetooth radio on in SHR Settings -> Connectivity -> Bluetooth Radio: On. You can also make the bluetooth device visible here.<br />
<br />
====OBEX file transfer====<br />
<br />
There are several obex programs allowing file transfer, all in console at the moment. Obexpush installs obextool, and opd daemon:<br />
<br />
opkg install obexpush<br />
<br />
Default receiving path (editable in /etc/default/opd_args ) does not exist, so create it<br />
<br />
mkdir /var/obexpush<br />
<br />
Files are then received automatically, no notice, no confirmation... they just silently appear in /var/obexpush<br />
<br />
To send some files, first scan for devices:<br />
<br />
hcitool scan<br />
Scanning ...<br />
00:16:41:F5:A5:BC laptop<br />
<br />
Then send the file onto bluetooth address found in the scan:<br />
<br />
obextool push image.jpg 00:16:41:F5:A5:BC 10<br />
<br />
====Connect Bluetooth keyboard====<br />
<br />
hidd --search<br />
<br />
Editors note: This is the old bluez3 way, but it works. New bluez4 way will replace this.<br />
<br />
===Bluez4 - D-Bus based way===<br />
<br />
SHR uses bluez4 which is completely different from bluez3. The bluetoothd is taking care of most of the bluetooth now. Please see [[Manually using Bluetooth]] for detailed information about using bluetooth and also for a list of supported devices.<br />
<br />
====Pairing====<br />
<br />
[[Emtooth]] is a bluetooth manager. It provides setting up bluetooth device name, pairing/unpairing, visibility setting and more. Install Emtooth:<br />
<br />
opkg install emtooth<br />
<br />
It will discover nearby devices, double tapping on found device will initiate pairing process.<br />
<br />
====GSM with bluetooth headset====<br />
<br />
In order to use bluetooth headset for phone calls, several simple steps need to be done.<br />
<br />
1). Your bluetooth headset device must be [[#Pairing | paired]] first.<br />
<br />
2). [[#Configuring_FSO | Add]] your bluetooth headset into FSO configuration.<br />
<br />
<br />
Please note: phonecalls are now always routed to the bluetooth headset. <br />
After startup and after every resume, the headset needs to be [[#Re-Connecting_the_bluetooth_headset |reconnected]].<br />
<br />
=====Configuring FSO=====<br />
<br />
Now we must tell frameworkd that you have a bluetooth headset. Headset parameters should be set in<br />
<br />
/etc/freesmartphone/opreferences/conf/phone/default.yaml<br />
<br />
Parameters bt-headset-enabled and bt-headset-address (see opreferences/schema/phone.yaml for semantics).<br />
<br />
You need to restart FSO for the changes to take effect.<br />
<br />
# /etc/init.d/frameworkd restart<br />
<br />
example of my /etc/freesmartphone/opreferences/conf/phone/default.yaml:<br />
<br />
message-length: 7<br />
message-tone: notify_message.wav<br />
message-vibration: 1<br />
message-volume: 10<br />
ring-loop: 1<br />
ring-tone: ringtone_ringnroll.wav<br />
ring-vibration: 1<br />
ring-volume: 10<br />
bt-headset-enabled: 1<br />
bt-headset-address: 00:09:DD:31:92:98<br />
<br />
=====Re-Connecting the headset=====<br />
<br />
You might need to get the bluetooth headset connected manually on the beginning and also after suspend:<br />
<br />
mdbus -s org.bluez $BTADAPTER/dev_xx_xx_xx_xx_xx_xx org.bluez.Headset.Connect<br />
<br />
where xx_xx_xx_xx_xx_xx is address of the device, for example:<br />
<br />
mdbus -s org.bluez $BTADAPTER/dev_00_09_DD_31_92_98 org.bluez.Headset.Connect<br />
<br />
Hopefully, your bluetooth headset now works. Good luck!<br />
<br />
==System Customizing==<br />
<br />
===Command scheduling===<br />
<br />
The traditional ''at'' command in ''SHR'' is modified to work over dbus. This modified ''at_over_dbus'' will run scheduled task at required time - actually it will even automatically wake up the phone from suspend or start it if the phone was switched off.<br />
<br />
To schedule a command to be executed at a particular time, one must:<br />
<br />
Place commands in a script in ''/var/spool/at'' and name it like <br />
<br />
TIMESTAMP.NAME.NUMBER<br />
<br />
where<br />
<br />
where TIMESTAMP is the seconds since 1970-01-01 00:00:00 UTC when the command should be run. <br />
The rest (NAME, NUMBER) is up to you. Finally you have to:<br />
<br />
touch /var/spool/at/trigger<br />
<br />
Also, make sure to have atd running. You are responsible to remove the script when unnecessary. It will run once more if you/other program write to the trigger file during the execution, so you may consider removing the<br />
executable flag of the script (if it is long running) or rename the script from within for example like this: <br />
<br />
mv "$0" "x$0.$$"<br />
<br />
===Installing splash screen themes===<br />
<br />
List available splash screen themes<br />
<br />
opkg list | grep splash-theme<br />
<br />
Install one of the available themes<br />
<br />
opkg install shr-splash-theme-dontpanic<br />
<br />
Then go to '''SHR Settings -> Appearance -> Splash settings'''. Here you can preview installed themes and change the default one.<br />
<br />
===Installing themes===<br />
<br />
Every theme is made of several components (a theme for illume, theme for the phone applications, theme for etk and so on). There is a SHR metapackage for each theme that allows installing the complete theme in one go.<br />
<br />
List available SHR theme metapackages:<br />
<br />
opkg list | grep shr-theme<br />
<br />
Install one of the available themes<br />
<br />
opkg install shr-theme-gry<br />
<br />
Then go to '''SHR Settings -> Appearance -> Elementary Settings'''. Here you can preview installed themes and choose the preferred one.<br />
<br />
The Illume screen requires to change theme via '''Settings (SHR Logo) -> Look -> Theme'''. Here you can preview installed themes and choose the preferred one.<br />
<br />
===Enable mouse cursor=== <br />
<br />
edit line 143 of /etc/X11/Xserver and erase '''-nocursor'''<br />
<br />
ARGS="$ARGS"<br />
<br />
<br />
<br />
===Random errors===<br />
No icons, no GSM functions etc. happen mostly due to '''errors on your µSD''' card. Remove your card and fix it in card reader or by booting to another partition (nand) or by reboot and mount read only, then run fsck.<br />
<br />
For reboot into nand and fix 1st partition of ext2 on your card<br />
<br />
fsck.ext2 /dev/mmcblk0p1<br />
<br />
===GSM modem 1024 suspend bug===<br />
<br />
The calypso GSM modem suffers a known [[1024]] hardware bug that causes unreliable GSM function. To work it around, SHR by default doesn't suspend the modem completely. If you have undertaken a fix for this bug you can extend your battery time by enabling the modem to fully suspend when possible.<br />
<br />
Edit the following in file:<br />
<br />
For the new FSO2 edit /etc/freesmartphone/conf/GTA02/fsogsmd.conf <br />
<br />
deep_sleep == "always"<br />
<br />
Then kill fsogsmd and restart fsodeviced or reboot the phone.<br />
<br />
<br />
For old FSO (frameworks) edit /etc/frameworkd.conf <br />
<br />
ti_calypso_deep_sleep = always<br />
<br />
Then restart framework or reboot the phone.<br />
<br />
<br />
<br />
==Reporting bugs==<br />
<br />
SHR is a work in progress. If you experience issues, please report them back to SHR. With your report provide relevant logs from<br />
<br />
/var/log/<br />
<br />
To report a bug, please go to http://shr-project.org/trac/report<br />
<br />
Check if the bug is already reported. If not, add a ticket, be as much precise as you can in the title and the description, in what circumstances the issue happened and so on. If bug already exists, see if you can help fixing it by providing some fresh info.<br />
<br />
==More information==<br />
<br />
For SHR home page, source code and other resources, visit:<br />
<br />
* [http://trac.shr-project.org SHR Project Homepage]<br />
* [http://blog.shr-project.org SHR Blog]<br />
* [http://trac.shr-project.org Trac Bugtracker]<br />
* [http://git.shr-project.org Git Sourcecode-repository]<br />
* [http://build.shr-project.org Downloads on buildhost]<br />
* [http://lists.shr-project.org SHR User and Development Mailing Lists]<br />
<br />
==About this manual==<br />
<br />
This manual makes use of updated SHR-Unstable distribution which means that for example SHR-Testing or not updated SHR-Unstable might behave differently then stated in this manual.<br />
<br />
Please help extending this manual by correcting typos or discussing proposals on the talk page or email <tt>vanous @ penguin . cz</tt>. Thank you.<br />
<br />
[[Category:SHR]]<br />
[[Category:Manuals]]</div>Vanoushttp://openmoko.org/wiki/Manuals/SHRManuals/SHR2010-09-05T12:09:52Z<p>Vanous: /* Booting */ switching shelve notice</p>
<hr />
<div>{{Languages|Manuals/SHR}}<br />
{| align="right"<br />
| __TOC__<br />
|}<br />
<br />
==SHR Introduction==<br />
<br />
Welcome to '''[[SHR]]''', a community driven distribution for (not only) Openmoko, HTC Dream, PalmPré and Nokia n900 phones.<br />
<br />
<br />
<br />
[[Image:SHR-Logo.png|200px|thumb|center|SHR]]<br />
<br />
'''SHR''' (Stable Hybrid Release) is here to provide you with Root FileSystem images that you can easily install into your device to use as a daily phone and PDA. There are many prepackaged programs available that can be installed upon demand by users, it can also be used by developers as a base image for customized and flavored distribution or release. '''SHR unstable (SHR-U)''' is a testing environment before software gets stabilized and it is the main testing ground for [[FSO]] releases. '''SHR testing (SHR-T)''' images provide as much stability as possible for day-to-day usage.<br />
<br />
==Installation==<br />
<br />
===Getting SHR===<br />
<br />
You need to download two files for your version as above: kernel and root filesystem. Depending whether you will be installing into the internal [[NAND memory]] or on the [[microSD]] card, you need to either get .jffs2 file for NAND or .tar.gz file for microSD.<br />
<br />
- Get the latest kernel from the below linkpages. Starts with uImage-...<br />
<br />
- Get the root filesystem, for NAND: full-om-gta0_.jffs2, for µSD: full-om-gta0_.tar.gz<br />
<br />
The above are '''full''' images. You can also choose images with less packages, marked as '''lite'''.<br />
<br />
;GTA02 Neo FreeRunner<br />
*testing line: http://build.shr-project.org/shr-testing/images/om-gta02/<br />
*unstable 2.6.3* line: http://build.shr-project.org/shr-unstable/images/om-gta02/<br />
*( unstable 2.6.29 line: http://build.shr-project.org/shr-unstable.29/images/om-gta02/ )<br />
<br />
;GTA01 Neo 1973<br />
*testing line: http://build.shr-project.org/shr-testing/images/om-gta01/<br />
*unstable 2.6.29 line: http://build.shr-project.org/shr-unstable.29/images/om-gta01/<br />
<br />
;Image lite to image full<br />
If you flashed a '''lite''' image and want to upgrade to the '''full''' image run:<br />
<br />
opkg update<br />
opkg install task-shr-apps task-shr-games task-shr-gtk<br />
<br />
;Kernel modules<br />
The images of the filesystems mentioned above (.jffs2, .tar.gz), already contain the newest kernel modules.<br />
<br />
Get the new kernel modules if you only want to flash a new kernel, but not a whole new file system. From the same page as the kernel download the modules to match your kernel (their dates should be the same). Use sftp to put that file on the FreeRunner via the usb connection. Run gzip to unwrap the modules:<br />
# gzip -dc modules-...tar.gz | tar -xf - -C /<br />
<br />
===Installation on Flash===<br />
<br />
In order to install your SHR distribution directly to your FreeRunner Flash memory (NAND), you need to get the desired filesystem file ( <tt>.jffs2</tt> ) as described above and flash your device using the <tt>dfu-util</tt> tool.<br />
<br />
Please visit [[Flashing the Neo FreeRunner]] for more details about flashing and see [[Dfu-util]] for detailed information about the dfu-util.<br />
<br />
{{Note|Your battery must be charged (sufficiently) before NAND flashing. Symptom of insufficient charge: Your progress bar "####" stops while flashing. If so, you must charge, and later you should be able to make the complete flash.}}<br />
Commands to flash the filesystem and the kernel:<br />
<br />
for the GTA02 Neo FreeRunner:<br />
<br />
# dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D full-om-gta02.jffs2<br />
# dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-om-gta02-latest.bin<br />
<br />
for the GTA01 Neo 1973:<br />
<br />
# dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a rootfs -R -D full-om-gta01.jffs2<br />
# dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a kernel -R -D uImage-om-gta01-latest.bin<br />
<br />
===Installation on the microSD Card===<br />
<br />
Installing SHR on your microSD Card depends on the Bootloader you are using, ''uBoot'' or ''Qi''.<br />
<br />
In simple words, the difference between both systems resides on how you must prepare your microSD Card and files you use to fill them:<br />
<br />
* If you use ''uBoot'', you need to create two partitions. First partition, not so big, in FAT16 or ext2 where you have to place the kernel file (<tt>uImage-om-gta02-latest.bin</tt>) and second partition in ext2 or ext3 where you have to uncompress the filesystem file (<tt>shr-image-om-gta02.tar.gz</tt>).<br />
<br />
* If you use ''Qi'', you only need an ext2 partition into your µSD Card where you uncompress the filesystem image file (<tt>shr-image-om-gta02.tar.gz</tt>). In this case Qi Bootloader is going to look for the kernel image into the <tt>/boot</tt> directory for file named <tt>uImage-GTA02.bin</tt> .<br />
<br />
===Bootloaders===<br />
<br />
Make sure you have recent and correct versions of [[Booting_from_SD | uBoot]] or [[Qi]] installed, please visit the links for detailed information and tips. For example [[Android]] uses modified [[Qi]] which can cause you troubles when using SHR.<br />
<br />
===SHR version===<br />
<br />
Should you ever later wonder what version of SHR you have actually installed, please run<br />
<br />
timestamp of image creation:<br />
cat /etc/timestamp<br />
<br />
latest shr version from opkg upgrade (this version is changed everytime someone builds task-base on shr buildhost):<br />
cat /etc/shr-version<br />
<br />
{{Note|Please note that this is true only for shr-u, with shr-t running opkg update;opkg upgrade does not change the SHR version. Only flashing or a new image download can change the SHR version. But this will be also merged to shr-t later.}}<br />
<br />
==Running SHR==<br />
<br />
===First boot===<br />
[[Image:Shr-boot-preview.png|200px|thumb|center|SHR Boot Splash screen]]<br />
<br />
====Booting====<br />
First boot usually takes a bit longer as your phone's new software needs to do some initial setting up. It is recommended to reboot after this first boot (and after the initial setup), to make sure that all packages get initialized properly. The application switching shelve (shr_elm_softkey) doesn't show up during first boot when the initial wizards are at work, [http://shr-project.org/trac/ticket/1105 reboot is required] and then application switching works as expected.<br />
<br />
====Initial Setup====<br />
<br />
During the first run, Setup is automatically initiated to walk the user through basic setup of the Enlightenment desktop environment. These steps vary as both Enlightenment desktop and SHR evolve, at this point preferred language and desktop profile options are available. The Profile offers to choose a preconfigured way of displaying the desktop. Illume2-SHR (with continuous development) and Illume-SHR (discontinued) profiles are available. '''Illume2-SHR''' is the recommended Profile. <br />
<br />
{| class="wikitable"<br />
| [[Image:SHR-Setup-Language.png|200px|thumb|language selection]]<br />
| [[Image:SHR-Setup-Profile.png|200px|thumb|theme selection]]<br />
| [[Image:SHR-Wizard.png|200px|thumb|SHR Wizard]]<br />
<br />
|}<br />
<br />
Note, you may need to ssh into the device and run /usr/bin/xinput_calibrator_once.sh if calibration is wrong. I found this using a Neo1973 and SHR images from around May 2010.<br />
<br />
====SHR Wizard====<br />
After the initial Setup, SHR Setting Wizard is launched to allow setting up your local phone settings and setting up root password. Sometimes a '''Please wait''' message is displayed for a long time, as the wizzard is waiting for the SIM card to be initialized.<br />
<br />
===First look===<br />
[[Image:SHR-First-Look.png|200px|thumb|Desktop screen]]<br />
[[Image:SHR-Task-Buttons.png|200px|thumb|Task switch buttons]]<br />
====Illume desktop====<br />
Illume desktop is the default home screen of the SHR desktop. <br />
<br />
Application definition files located in /usr/share/applications are displayed here as icons. All applications are ran fullscreen and you can switch between them by using the the '''< left''' or '''right >''' arrows on sliding shelve available by tapping Top Shelf on any empty space. To close applications, choose '''X''' from the same sliding shelve.<br />
<br />
Several icons (e-gadgets) are placed in the Top Shelve:<br />
<br />
The '''L''' icon is to switch between left/right mouse click. By taping this icon the icon gets changed to R and next tap will be as right click. After the click, the behavior is automatically switched back to Left click so any following taps are left click again.<br />
<br />
'''Mode Switch Icon''' allows to split the screen horizontally or vertically, thus allowing to display two applications at the same time.<br />
<br />
'''Keyboard icon''' pops up or hides the Keyboard.<br />
<br />
'''Illume Settings''' icon (represented by SHR logo) invokes the [[#Illume_settings | Illume desktop settings]]. <br />
<br />
'''Home Icon''' allows quick go to the home desktop/application.<br />
<br />
'''GSM''' and '''Battery''' status icons, as well as '''time''' are displayed by default, Bluetooth and WiFi status icons available in the setting of the Top Shelve content.<br />
<br />
<br />
To '''reconfigure the Top Shelve''' itself, use the L/R click icon to Right click on the Top Panel and choose: Illume Indicator->Set Content to add or remove items from the Top Panel. Or, upon right click on the Top Panel you can also choose Illume Indicator->Begin Move/Resize to move your icons around. To escape this mode, you must click on the L/R gadget's edge, it will switch to L, then choose R again, right click on the Top Panel and select Illume Indicator->Stop Move/Resize.<br />
<br />
<br />
====Keyboard====<br />
<br />
Keyboard comes up automagically when a text field is tapped or you can also toggle the keyboard by it's icon in the Top Shelve. In the Keyboard, dictionary switcher is the arrow-up on left side, alternative keyboard layouts are under the ABC button on the right. The Default keyboard has English dictionary enabled. For Space quick slide left-to-right, for Enter, quick slide up-down, to quick change keyboard layout quick slide down-up. While typing with a dictionary enabled keyboard, possible word options start appearing in the keyboard's upper part or more word options are available under the arrow-up on the left. When happy with the word, tap it, it will be pasted into the text field with a space attached. The Keyboard and dictionary can [[#Illume_keyboard_and_dictionaries | easily be localized]].<br />
<br />
====Copy and Paste====<br />
<br />
In '''E based''' applications, for example the phone suite (contacts, messages...), by tapping and holding down for over two seconds the Select-Paste menu will pop up. By pressing Select, you can now swipe through the text to select desirable part. Tap and hold down again, Copy-Cut-Cancel menu will appear to Copy to clipboard. Another long tap will provide Select-Paste for Paste.<br />
<br />
In '''Gtk''' based application, you can use keyboard for Ctrl-C (Copy) and Ctrl-V (Paste) or items in Menu if provided.<br />
<br />
In the Vala '''Terminal''', you can select simply by swiping through the text and for Paste there is an icon in the menu bar of this application.<br />
<br />
Copy & Paste between different toolkits has some limitations. See the table below. In Ventura, select is possible, but copy/paste doesn't seem to work at all.<br />
<br />
{| cellspacing="0" class="wikitable" border="1" style="font-size: 85%; text-align: left;width="100%"<br />
|-<br />
! From -> To <br />
! to GTK<br />
! to E<br />
! to Terminal<br />
|-<br />
| from GTK<br />
|style="background:#88FF88;"|Works<br />
|style="background:#88FF88;"|Works<br />
|style="background:red"|Doesn't work <br />
|-<br />
| from E<br />
|style="background:red"|Doesn't work <br />
|style="background:#88FF88;"|Works <br />
|style="background:#88FF88;"|Works<br />
|-<br />
| from Terminal<br />
|style="background:red"|Doesn't work <br />
|style="background:#88FF88;"|Works <br />
|style="background:#88FF88;"|Works<br />
|-<br />
|}<br />
<br />
====Alarm====<br />
<br />
The Alarms application (installed by default) allows alarm presetting for single or repeatable alarms. If you set an alarm and turn your Openmoko FreeRunner off, at the time of the alarm the phone will be powered up and alarm will sound.<br />
<br />
====Phone applications====<br />
<br />
Besides other software, SHR comes with 4 main phone applications: ''Dialer'', ''Contacts'', ''Messages'' and ''Phone log''.<br />
<br />
{|<br />
| [[Image:SHR-Dialer.png|200px|thumb|Dialer]]<br />
| [[Image:SHR-Contacts.png|200px|thumb|Contacts]]<br />
| [[Image:SHR-Mesages.png|200px|thumb|Messages]]<br />
| [[Image:SHR-Phonelog.png|200px|thumb|Phone log]]<br />
|}<br />
<br />
<br />
=====PIM data=====<br />
<br />
======Storage======<br />
PIM data (contacts, messages etc.) are stored through internal opimd storage mechanism into <br />
<br />
/etc/freesmartphone/opim/pim.db<br />
<br />
This database can easily be copied from one SHR installation to another, for example due to a need for reflashing. The Contacts application can display a picture of the contact. As the pim.db database contains a path to the picture files only but not the pictures themselves, therefore, in case of PIM data backup or transfer, these picture files '''need to be copied too'''.<br />
<br />
======SIM Contacts======<br />
<br />
SHR phone applications do not read SIM contacts by default but you can use SIM Manager to access your SIM contacts '''SHR Settings -> Others -> SIM Manager''', which allows you to edit and import the SIM contacts into the internal storage. You can also use Pisi to import your SIM contacts into opimd.<br />
<br />
======Synchronization======<br />
<br />
'''[[Pisi]]''' is an application for synchronizing PIM data and can be used for import and export your contacts, calendar entries etc. between various sources, like VCF, LDAP, Google and more. To install Pisi:<br />
<br />
opkg install pisi<br />
<br />
After installation, edit Pisi configuration in '''.pisi/conf''' in your home directory. To have a correct opimd fields support, make sure '''field_support=TRUE''' is enabled in opimd section.<br />
<br />
With the installed package you have a well-documented sample that is placed at <br />
/usr/share/doc/pisi/conf.example<br />
You may copy the file and rename this file to<br />
/home/root/.pisi/conf<br />
as a starting point - then edit this file in order to configure your PIM synchronization data sources. Look at section<br />
<br />
[opimd]<br />
description=OPIMD Contacts<br />
module=contacts_opimd<br />
field_support=TRUE<br />
<br />
=====Idle screen=====<br />
[[Image:SHR-Idle_Screen.png|200px|thumb|Idle Screen with GSM operator strength and name. GPS, WiFi, Display and CPU are requested, Battery status.]]<br />
Upon press of the AUX button Idle Screens locks up the display. AUX press or a finger slide on the Slider unlocks the screen.<br />
<br />
At the top, status icons are shown to indicate what is going on in the phone:<br />
<br />
From left to right:<br />
GSM strength and operator. Requested Resources (GPS, Display etc., when for example Display is requested, the screen will not dim). Battery capacity.<br />
<br />
====Hardware Buttons====<br />
<br />
=====Power Button=====<br />
<br />
[[Image:SHR-Quick-Settings.png|200px|thumb|Quick Settings]]<br />
<br />
The '''PWR''' (Power) button is mapped to start [[#quick_settings | Quick Settings]] screen (Illume System menu in older versions) on a short press. <br />
<br />
Mapping of the PWR button be configured via the '''Illume Settings-> Input -> Key Bindings'''.<br />
<br />
Pressing the Power button for longer then 8 seconds will force a complete power down of the device. This is hardconfigured in the kernel.<br />
<div id="quick_settings"> </div><br />
The '''Quick Settings''' screen provides several toggles: Airplane mode, Phone profiles, Power settings and Power buttons.<br />
<br />
=====Auxiliary Button=====<br />
The '''AUX''' (Auxiliary) button is mapped to toggle on/off the SHR Idle screen. Mapping of this button is configured in /etc/phonefsod.conf<br />
<br />
idle_screen = aux,lock<br />
<br />
You can configure the [[#idle_screen | Idle Screen]] to come up even during active phone call by adding '''phone''' to the setting: <br />
<br />
idle_screen = aux,lock, phone<br />
<br />
<div id="idle_screen"> </div><br />
The '''Idle Screen''' shows current date and time, missed calls and messaged and also what [[#FSO_Resources | FSO resources]] are currently being requested - used.<br />
<br />
======Replacing idle screen======<br />
<br />
If you wish to use the E simple LOCKED screen instead of the SHR Idle Screen, edit '''/etc/phonefsod.conf''' to this:<br />
<br />
# when to show idle screen<br />
# ...<br />
# idle_screen = aux,lock<br />
idle_screen =<br />
<br />
You need to restart phonefsod to make the change happen.<br />
<br />
Also, change key mapping for the AUX button by setting '''Illume Settings''' -> '''Input''' -> '''Key Bindings''', bind the key '''XF86Phone''' to '''Desktop Simple Lock'''<br />
<br />
====Settings applications====<br />
<br />
Many desktop and phone settings are possible to do via graphical interface. [[#SHR_Settings | SHR Settings]] provides access to most common phone personality settings and is accessible by tapping Settings icon on the desktop. [[#Illume_settings | Illume settings]] (and Enlightenment desktop settings) are accessible on Top shelve by tapping the "SHR Logo" icon. Also, FSO and SHR phoneui applications have configuration files in /etc where some of the above mentioned apps write and that can be edited manually.<br />
<br />
===First steps===<br />
<br />
Right after installation and first boot you might want to do a few initial steps like adjusting the call volume and some other tasks.<br />
<br />
====Audio - Call Volume====<br />
<br />
During the first phone call please use the Volume and Mic sliders on the Active Call Screen and adjust them to fit your preferences. The new improved settings will be used for all in/out-going calls thereafter.<br />
<br />
====Network Connection====<br />
<br />
[[#Networking|Establish network connection]] and SSH into your phone. You can establish connection either via USB to your desktop and enable NAT or you can connect through Wifi.<br />
<br />
====Initializing the opkg database====<br />
''Initialize the opkg database'' in order to install some applications from SHR repositories or from other sources, for example [http://opkg.org opkg.org]. While being online, you need to run<br />
<br />
opkg update<br />
<br />
Searching in the opkg database can take a long time. You can speed things up by dumping the database into a file and grepping it through. Do this only once or after every opkg update:<br />
<br />
opkg list > packages.txt<br />
<br />
Then you can search quickly for package name, for example for [[Navit|navit]]:<br />
<br />
grep navit packages.txt<br />
<br />
====SwapSpace====<br />
<br />
When the RAM is used up, applications get killed. This is particularly bad while doing opkg upgrade. Therefore you might want to create a swap space. Read [[SwapSpace]] article or the [http://shr-project.org/trac/wiki/swap swap article on the SHR wiki].<br />
<br />
==Settings==<br />
===SHR Settings===<br />
[[Image:SHR-Settings-main.png|200px|thumb|SHR Settings]]<br />
<br />
SHR Settings is the main setting application of SHR. It provides an easy way of setting up your phone to your liking - from phone related settings, to requesting resources in order to prevent screen dim or suspend (for example while using GPS).<br />
<br />
Please refer to [[#FSO_Resources | this section]] about a better way to manage preventing screen dim or suspend.<br />
<br />
While some settings are persistent over reboots, others are not.<br />
<br />
====Main Screen====<br />
The main screen is divided into eight categories, which contain several modules. Every SHR Settings module has a specified task - for example controlling the GSM antenna power, setting the time etc.<br />
<br />
====Phone====<br />
Here you can set if the GSM antenna is on and if your phone number is shown when you call someone.<br />
<br />
'''GSM'''<br />
In GSM settings you can turn off and on GSM module. After turning off antenna, whole GSM modem is turned off.<br />
<br />
To list available providers, click on Operators button. Scanning can take some time. After a while, a list of operators should pop up.<br />
<br />
You can't connect to operators marked [forbidden].<br />
<br />
Selecting an operator from the list also changes modem registration mode to manual. It won't register to other network, even if some is available and has better signal strengh. To return to automatic mode, click "Automatic" button in operator list.<br />
<br />
'''Call'''<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Phone.png|200px|thumb|Phone settings]]<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-List-providers.png|200px|thumb|List providers]]<br />
<br />
|}<br />
<br />
You can set if your phone number should be displayed to other party. You can either depend on network decision ("By network") or force it manually ("Manual")<br />
<br />
'''Phoneutils'''<br />
<br />
For the default SHR phone applications to be able to correctly parse incoming calls/messages and match them with your contacts, you will need to set the right country code for your location. (for example 420 for Czech republic) for more info, please go to: http://wiki.openmoko.org/wiki/Phone_Prefixes<br />
<br />
'''SIM'''<br />
<br />
Here you can view some informations about your SIM card and clean phone and messagebooks.<br />
<br />
====Profiles====<br />
<br />
Here you can select the current profile, which the device should use to determine ring tone etc.<br />
<br />
'''Current profile'''<br />
<br />
Here you can adjust properties of the currently used profile. <br />
<br />
To change the ring tone, click the "Change" button.<br />
<br />
To use your own ring tone, place it in /usr/share/sounds directory.<br />
<br />
After selecting a sid tune as the ring tone, there are available controls to select tune number from the file.<br />
<br />
If you like to test a .sid you can play it using this command on the FR:<br />
<br />
gst-launch filesrc location=Arkanoid_PSID.sid ! siddec tune=2 ! alsasink<br />
<br />
Note that it's a ! used and not a | to construct the gstreamer pipe command.<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Profiles.png|200px|thumb|Profiles]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Profiles-Ringtones.png|200px|thumb|Ringtones]]<br />
<br />
|}<br />
<br />
====Connectivity====<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Connectivity.png |200px|thumb|Connectivity top]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Connectivity2.png |200px|thumb|Connectivity bottom]]<br />
|}<br />
<br />
'''WiFi'''<br />
<br />
With the "WiFi radio" toggle you can set, if the wifi module is powered. WiFi radio has to be turned on before trying to connect to a WiFi network, unless you try to connect through [[Mokonnect]] which is capable of powering it up.<br />
<br />
'''GPRS'''<br />
<br />
To enter APN, login and password fields, just click on the actual value (default: "internet"). Your phone provider can provide the required configuration options.<br />
<br />
{{Note|You can also use Mokonnect to manage your GPRS connection}}<br />
<br />
'''USB'''<br />
<br />
With this toggle you can switch USB port between device (Neo to PC) or host (device to Neo) modes.<br />
<br />
'''Bluetooth'''<br />
<br />
To power up Bluetooth module, switch the "Bluetooth radio" toggle to "On". After that, the "Visibility" toggle should arrive - set it to "On" if you want your FR to be visible by other Bluetooth devices on scanning.<br />
<br />
====Power====<br />
<br />
'''Battery'''<br />
<br />
This module displays informations about battery state - charge, voltage, remaining time etc. To update the data, click the "Update" button.<br />
<br />
Here you can also force enable 500mA charging.<br />
<br />
'''Display'''<br />
<br />
With this slider you can easily set the backlight brightness.<br />
<br />
{{Note|This setting isn't permanent over sessions. At boot backlight is set back to 80%.}}<br />
<br />
'''Power'''<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Power.png |200px|thumb|Power]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Timeouts.png |200px|thumb|Timeouts]]<br />
|}<br />
<br />
'''Timeouts'''<br />
<br />
Timeouts are reached in this order: Busy state -> idle -> idle dim -> idle prelock -> lock -> suspend. <br />
<br />
{{Note|Storing of this setting via D-bus calls is not supported in the new API of Vala rewrite of FSO2 and therefore SHR Settings doesn't have a functional setting for this.}}<br />
<br />
You can set values of idle timeouts manually. The default parameters are stored in '''/etc/freesmartphone/conf/GTA02/fsodeviced.conf''' but customized '''.fsodeviced.conf''' file in your home directory will take precedence (if it exists, the one in /etc/... will be ignored, so you have to copy the whole file and tweak it):<br />
<br />
[fsodevice.kernel_idle]<br />
suspend = 20<br />
lock = 2<br />
idle_prelock = 12<br />
idle = 10<br />
idle_dim = 20<br />
<br />
To turn off a timeout, set it to -1.<br />
<br />
====Appearance====<br />
<br />
'''Theming'''<br />
[[Image:SHR-Neo-Theme.png|200px|thumb|Neo theme]]<br />
<br />
The Apperance section allows you to change between installed themes. To install more themes, see also [[#Installing themes | Installing themes]].<br />
<br />
You can change finger size - this will mainly effect vertical spacing between widgets.<br />
<br />
Switching between engines:<br />
<br />
E can be switched to use different engines. The default engine is x11. Alternative engine x11-16 is not supported and results in buggy behavior of several applications, for example the phone suite or Ventura browser. It's usage is not recommended.<br />
<br />
Changing system boot Splash screen is also possible in this module. To install more splash screens, see also [[#Installing splash screen themes|Installing splash themes]].<br />
<br />
====Position====<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-GPS.png |200px|thumb|center|GPS]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-GPS-Satelites.png |200px|thumb|GPS Satelite details]]<br />
|}<br />
<br />
'''GPS'''<br />
<br />
By default, GPS is turned on only when requested by an application. That state corresponds to "Auto" setting. After changing to "Manual", you can force set it to on or off.<br />
<br />
'''GPS information'''<br />
<br />
This page can be used to monitor GPS status. You either have to turn GPS on manually or start another application to enable the GPS.<br />
<br />
You can also view information about every visible satellite and check, which are used for getting a fix. To do that, click "Satellite details".<br />
<br />
'''Remove AGPS data'''<br />
If you experience problems with GPS, turn it off, click "Remove AGPS data" and reboot your Neo.<br />
Assisted GPS ([[aGPS]]) support GPS receiver to find position by non-satellite information.<br />
<br />
====Date/time====<br />
<br />
[[Image:SHR-Settings-Date-Time.png |200px|thumb|Date & Time]]<br />
<br />
'''Time'''<br />
<br />
Here you can view and set the time. By default, the time is just displayed, To adjust it, click on "Set time".<br />
<br />
After finishing adjusting, click the "OK" button.<br />
<br />
'''Date'''<br />
<br />
This module displays the current date.<br />
<br />
====Others====<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
[[Image:SHR-Settings-Others.png |200px|thumb|Others]]<br />
<br />
'''PIM'''<br />
<br />
Pim data are stored in opimd domains. Every opimd domain has different backends to store its data to. The domain reads data from every backend and writes data to the default backend. This elector allows you to choose the backend that stores newly generated data, it doesn't copy or move existing data to a different backend.<br />
<br />
'''Services'''<br />
<br />
The services selector is listing scripts from /etc/init.d/ directory.<br />
<br />
After clicking on a servis, you can either start, restart or stop the service and view the result.<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Services.png |200px|thumb|center|Services]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Service-restart.png |200px|thumb|Services debug screen]]<br />
|}<br />
<br />
<br />
'''Userspace backups'''<br />
<br />
Here you can either archive or restore your files and configurations.<br />
<br />
=== Illume settings ===<br />
<br />
The Illume desktop can be easily customized - tap the Settings icon (SHR Logo) on the Top Shelve.<br />
<br />
'''Illume settings''' provides various options to alter the desktop environment. You can change sizes of elements, single or double click, wallpaper. To access all the various options, open Illume Settings and slide the visible icons to the left, to view more options on the right hand side.<br />
<br />
Some setting screens are not resized properly to fit the phone's display - for example the Wallpapper setting. This is a known bug already reported upstream.<br />
<br />
<!-- [[Image:SHR-Top-Shelve.png|200px|thumb|Top Shelf]] --><br />
<br />
==Localization==<br />
<br />
=== Localize SHR manually ===<br />
<br />
[[Image:SHR-Illume-Settings-Languages.png|200px|thumb|Setting Language]]<br />
<br />
====Desktop environment====<br />
<br />
You can change the language of the SHR desktop environment by using the Settings of Illume. For Example, for Czech language: in the Illume top shelf go to Settings (SHR Logo) -> Language -> Language Settings -> and choose: Čeština. If your language is not in the menu you can install by using opkg.<br />
<br />
You can list all available languages by running:<br />
<br />
opkg list | grep eglibc-locale-<br />
<br />
And install the language of your choice (for example czech):<br />
<br />
opkg install eglibc-locale-cs<br />
<br />
After this, the Language Settings of Illume will offer Czech. <br />
<br />
This will localize the Illume environment and will also set correct lang environment variable of your desktop. <br />
<br />
====Applications====<br />
<br />
If you wish to have other applications localized, you need to install translation for each of them (presuming it is available):<br />
<br />
This will install czech localization for SHR phone applications, SHR Settings and TangoGps:<br />
<br />
opkg install libframeworkd-phonegui-efl-locale-cs shr-settings-locale-cs tangogps-locale-cs<br />
<br />
====Terminal environment====<br />
<br />
For localized terminal environment (ssh login) set lang variables in /etc/profile.d/locale.sh, example for Czech language:<br />
<br />
export LANG=cs_CZ<br />
export LC_ALL=cs_CZ<br />
<br />
====Illume keyboard and dictionaries====<br />
[[Image:Illume-keyboards-terminal-dutch-nl-screenshot.png| Dutch terminal virtual keyboard|256px|thumb]]<br />
→ more details on page [[Illume keyboard]]<br />
<br />
Unlike other input methods for mobile devices, the Illume keyboard is corrective rather than predictive. It detects what you mean, even if some letters mistyped. If you accidently hit some keys next to the correct one Illume still reckognizes the word. This kind of compensates for the small size of the keys. Keep a key pressed for a longer time to affirm you really mean it. <br />
<br />
An English dictionary is used by default. A few dictionaries for other languages are included in the SHR distribution. In addition, every dictionary for [http://en.wikipedia.org/wiki/MySpell myspell] can be used. <br />
<br />
You can install a different keyboard with a layout which fits your language or alternatives for the default keyboards like the numerical one. The localized [[Illume keyboard]]s are available in the SHR repository under the name ''illume-keyboard-LANG''.<br />
<br />
==== German (and Austria) Language ====<br />
<br />
See [[Configure_SHR_for_German-speaking_use]] for detailed customization for german speaking.<br />
<br />
===Date and time===<br />
{{Note|This needs a complete and correct rewrite.}}<br />
<br />
Date and time are automatically set from GPS or Network. The easiest way of setting the time for the first time is to run TangoGps (GPS & Map icon) and obtaining GPS fix. Time will then be set automatically.<br />
<br />
The local timezone is automatically retrieved from the GSM network.<br />
<br />
It is possible to instruct framework on how to set the time and timezone in /etc/frameworkd.conf :<br />
<br />
[otimed]<br />
# a list of time/zone sources to use or NONE<br />
timesources = GPS,NTP<br />
zonesources = GSM<br />
# use an ip address here, otherwise DNS resolution will block<br />
ntpserver = 134.169.172.1<br />
<br />
To disable automatic date/zone settings, simply create an empty [otimed] section in /etc/frameworkd.conf<br />
<br />
Timezone change<br />
<br />
Create a symlink named /etc/localtime which points to the appropriate file in /usr/share/zoneinfo. For example, if you're in France., the following command will link the correct zoneinfo file to your /etc/localtime, giving you the correct time:<br />
<br />
ln -sf /usr/share/zoneinfo/Europe/Paris /etc/localtime<br />
<br />
Afterwards, edit /etc/timezone if necessary [?]<br />
<br />
Local timezone work instantly for the current boot when:<br />
<br />
TZ="Europe/Paris"<br />
export TZ<br />
<br />
For a permanent timezone change edit /etc/profile and change to:<br />
<br />
TZ="Europe/Paris"<br />
<br />
<br />
If you use UTC time, set '''UTC=yes''' in '''/etc/default/rcS'''.<br />
<br />
Adjusting time manually:<br />
<br />
Via SHR-Settings -> Date/time -> Set time<br />
<br />
From linux based desktop:<br />
<br />
ssh root@192.168.0.202 "date -u -s `date -u +%m%d%H%M%Y.%S`"<br />
<br />
The above does NOT work from Ubuntu as of 4/2/2010, the proper format is:<br />
<br />
ssh root@192.168.0.202 "date -u -s `date -u +%Y.%m.%d-%H:%M:%S`"<br />
<br />
Set the hardware clock to the system time:<br />
<br />
hwclock --systohc<br />
<br />
Is this better?:<br />
<br />
hwclock --utc --systohc<br />
<br />
==FSO Resources==<br />
<br />
[[FSO]] is in control of each device. These are called ''resources''. If the software wanting to use the device is capable of requesting this resource via <tt>d-bus</tt>, FSO will do this, otherwise you might need to power the device manually. After the requested resource is released, FSO will power it down. Manual resource request can be done through ''SHR Setting'' or you can use <tt>fsoraw</tt> command. (Using fsoraw is faster and better than running dbus commands)<br />
<br />
opkg install fsoraw<br />
<br />
Example of usage fsoraw:<br />
<br />
fsoraw -r Display mokomaze<br />
<br />
See [[FSO Resources]] for more details on using the following resources:<br />
<br />
'''Wifi'''<br />
<br />
Unless this resource is enabled you've no eth0 and wifi module is completely un-powered. Use the [[Mokonnect]] network manager to set up networks, it will power Wifi up automatically when needed.<br />
<br />
'''Bluetooth'''<br />
<br />
You need to have this resource requested to have bluetooth module powered.<br />
<br />
'''GPS'''<br />
<br />
The fso-gpsd is a daemon waiting for gsmd connections, automatically powering the device on and off. When a connection exists, it powers up the GSM. In SHR Settings you can switch GPS completely off SHR Settings -> GPS -> Manual > Off<br />
<br />
'''GSM'''<br />
<br />
You need to have this resource requested to have GSM module powered.<br />
<br />
'''Display'''<br />
<br />
While this resource is requested the display won't be blanked and suspend is disabled.<br />
<br />
'''CPU'''<br />
<br />
While this resource is requested then suspend is disabled. Display will blank as normal.<br />
<br />
'''Test'''<br />
<br />
A test resource.<br />
<br />
'''UsbHost'''<br />
<br />
While this resource is requested the USB is turned into powered USB Host mode.<br />
<br />
'''Accelerometer'''<br />
<br />
You need to have this resource requested to have the Accelerometer module powered.<br />
<br />
==Networking==<br />
<br />
There are several ways of networking - Wifi, USB, Bluetooth and Gprs:<br />
<br />
===USB===<br />
<br />
By default, USB networking is enabled in <tt>/etc/network/interfaces</tt>, where enhanced configuration can be direct edited. The phone default IP address is 192.168.0.202. Some setup is required on the desktop side, please read [[USB Networking]].<br />
<br />
===WiFi===<br />
<br />
WiFi manager [[iliwi]] is available by default for search/connect/making default a wifi connection. ''iliwi'' uses key only in hex format. The Wifi device is not required to be manually turned on via SHR-Settings as ''iliwi'' will automatically enable the device when needed and disable it after use. iliwi needs to stay running to keep the WiFi connection enabled.<br />
<br />
When WiFi is connected, the Idle screen show the icon of the WiFi resource being occupied.<br />
<br />
===GPRS===<br />
<br />
GPRS Credentials are set during the first run in SHR Wizard and you may edit them at any time via SHR settings or direct editing of /etc/phonefsod.conf. GPRS connection can then be established/closed via SHR Settings or through SHR Quick Settings (available under the Power button). SHR Quick Settings - Network tab allows also connection sharing - this will share the GPRS connection with USB network and run DHCP server to provide the client with an IP address.<br />
<br />
When GPRS is connected, the idle screen shows a small G above the signal strength indicator.<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |<br />
[[Image:SHR-Gprs-Share.png|200px|thumb|GPRS + Connection sharing]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " | <br />
[[Image:SHR-Iliwi-Scan.png|200px|thumb|Iliwi WiFi scanning]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " | <br />
<br />
[[Image:SHR-Iliwi-Connect.png|200px|thumb|Iliwi WiFi connecting]]<br />
<br />
|}<br />
<br />
==Bluetooth==<br />
<br />
Bluetooth can be used for several different applications - file transfer (OBEX), networking, input devices (HIDD), music playing (A2DP), calling etc. In some occasions, the devices need to be authorized - paired. At the moment, support for some bluetooth functions is better than for others - it is possible to do all mentioned above with the notice that phone calls with bluetooth headset are always routed to the bluetooth even if the bluetooth headset is not around, making it quite difficult to use.<br />
<br />
In the SHR repositories are applications ready to be installed (by opkg) that already do provide bluetooth support. This means that they request the bluetooth resource automatically, can search bluetooth devices around, help you with pairing and can perhaps even reconnect bluetooth headset upon resume from suspend. From applications that have some bluetooth support some are for example [[Launcher]] (home screen launcher and phone suite), [[Podboy]] (podcast player), [[Elmtooth]] (bluetooth manager). In order to set up bluetooth for phone calls, some manual setup from [[#GSM_phone_calls_with_bluetooth_headset | bellow]] is still required.<br />
<br />
===Bluez3 - the manual non D-Bus way===<br />
<br />
If you want to use the bluetooth device directly, you need to turn the bluetooth radio on in SHR Settings -> Connectivity -> Bluetooth Radio: On. You can also make the bluetooth device visible here.<br />
<br />
====OBEX file transfer====<br />
<br />
There are several obex programs allowing file transfer, all in console at the moment. Obexpush installs obextool, and opd daemon:<br />
<br />
opkg install obexpush<br />
<br />
Default receiving path (editable in /etc/default/opd_args ) does not exist, so create it<br />
<br />
mkdir /var/obexpush<br />
<br />
Files are then received automatically, no notice, no confirmation... they just silently appear in /var/obexpush<br />
<br />
To send some files, first scan for devices:<br />
<br />
hcitool scan<br />
Scanning ...<br />
00:16:41:F5:A5:BC laptop<br />
<br />
Then send the file onto bluetooth address found in the scan:<br />
<br />
obextool push image.jpg 00:16:41:F5:A5:BC 10<br />
<br />
====Connect Bluetooth keyboard====<br />
<br />
hidd --search<br />
<br />
Editors note: This is the old bluez3 way, but it works. New bluez4 way will replace this.<br />
<br />
===Bluez4 - D-Bus based way===<br />
<br />
SHR uses bluez4 which is completely different from bluez3. The bluetoothd is taking care of most of the bluetooth now. Please see [[Manually using Bluetooth]] for detailed information about using bluetooth and also for a list of supported devices.<br />
<br />
====Pairing====<br />
<br />
[[Emtooth]] is a bluetooth manager. It provides setting up bluetooth device name, pairing/unpairing, visibility setting and more. Install Emtooth:<br />
<br />
opkg install emtooth<br />
<br />
It will discover nearby devices, double tapping on found device will initiate pairing process.<br />
<br />
====GSM with bluetooth headset====<br />
<br />
In order to use bluetooth headset for phone calls, several simple steps need to be done.<br />
<br />
1). Your bluetooth headset device must be [[#Pairing | paired]] first.<br />
<br />
2). [[#Configuring_FSO | Add]] your bluetooth headset into FSO configuration.<br />
<br />
<br />
Please note: phonecalls are now always routed to the bluetooth headset. <br />
After startup and after every resume, the headset needs to be [[#Re-Connecting_the_bluetooth_headset |reconnected]].<br />
<br />
=====Configuring FSO=====<br />
<br />
Now we must tell frameworkd that you have a bluetooth headset. Headset parameters should be set in<br />
<br />
/etc/freesmartphone/opreferences/conf/phone/default.yaml<br />
<br />
Parameters bt-headset-enabled and bt-headset-address (see opreferences/schema/phone.yaml for semantics).<br />
<br />
You need to restart FSO for the changes to take effect.<br />
<br />
# /etc/init.d/frameworkd restart<br />
<br />
example of my /etc/freesmartphone/opreferences/conf/phone/default.yaml:<br />
<br />
message-length: 7<br />
message-tone: notify_message.wav<br />
message-vibration: 1<br />
message-volume: 10<br />
ring-loop: 1<br />
ring-tone: ringtone_ringnroll.wav<br />
ring-vibration: 1<br />
ring-volume: 10<br />
bt-headset-enabled: 1<br />
bt-headset-address: 00:09:DD:31:92:98<br />
<br />
=====Re-Connecting the headset=====<br />
<br />
You might need to get the bluetooth headset connected manually on the beginning and also after suspend:<br />
<br />
mdbus -s org.bluez $BTADAPTER/dev_xx_xx_xx_xx_xx_xx org.bluez.Headset.Connect<br />
<br />
where xx_xx_xx_xx_xx_xx is address of the device, for example:<br />
<br />
mdbus -s org.bluez $BTADAPTER/dev_00_09_DD_31_92_98 org.bluez.Headset.Connect<br />
<br />
Hopefully, your bluetooth headset now works. Good luck!<br />
<br />
==System Customizing==<br />
<br />
===Command scheduling===<br />
<br />
The traditional ''at'' command in ''SHR'' is modified to work over dbus. This modified ''at_over_dbus'' will run scheduled task at required time - actually it will even automatically wake up the phone from suspend or start it if the phone was switched off.<br />
<br />
To schedule a command to be executed at a particular time, one must:<br />
<br />
Place commands in a script in ''/var/spool/at'' and name it like <br />
<br />
TIMESTAMP.NAME.NUMBER<br />
<br />
where<br />
<br />
where TIMESTAMP is the seconds since 1970-01-01 00:00:00 UTC when the command should be run. <br />
The rest (NAME, NUMBER) is up to you. Finally you have to:<br />
<br />
touch /var/spool/at/trigger<br />
<br />
Also, make sure to have atd running. You are responsible to remove the script when unnecessary. It will run once more if you/other program write to the trigger file during the execution, so you may consider removing the<br />
executable flag of the script (if it is long running) or rename the script from within for example like this: <br />
<br />
mv "$0" "x$0.$$"<br />
<br />
===Installing splash screen themes===<br />
<br />
List available splash screen themes<br />
<br />
opkg list | grep splash-theme<br />
<br />
Install one of the available themes<br />
<br />
opkg install shr-splash-theme-dontpanic<br />
<br />
Then go to '''SHR Settings -> Appearance -> Splash settings'''. Here you can preview installed themes and change the default one.<br />
<br />
===Installing themes===<br />
<br />
Every theme is made of several components (a theme for illume, theme for the phone applications, theme for etk and so on). There is a SHR metapackage for each theme that allows installing the complete theme in one go.<br />
<br />
List available SHR theme metapackages:<br />
<br />
opkg list | grep shr-theme<br />
<br />
Install one of the available themes<br />
<br />
opkg install shr-theme-gry<br />
<br />
Then go to '''SHR Settings -> Appearance -> Elementary Settings'''. Here you can preview installed themes and choose the preferred one.<br />
<br />
The Illume screen requires to change theme via '''Settings (SHR Logo) -> Look -> Theme'''. Here you can preview installed themes and choose the preferred one.<br />
<br />
===Enable mouse cursor=== <br />
<br />
edit line 143 of /etc/X11/Xserver and erase '''-nocursor'''<br />
<br />
ARGS="$ARGS"<br />
<br />
<br />
<br />
===Random errors===<br />
No icons, no GSM functions etc. happen mostly due to '''errors on your µSD''' card. Remove your card and fix it in card reader or by booting to another partition (nand) or by reboot and mount read only, then run fsck.<br />
<br />
For reboot into nand and fix 1st partition of ext2 on your card<br />
<br />
fsck.ext2 /dev/mmcblk0p1<br />
<br />
===GSM modem 1024 suspend bug===<br />
<br />
The calypso GSM modem suffers a known [[1024]] hardware bug that causes unreliable GSM function. To work it around, SHR by default doesn't suspend the modem completely. If you have undertaken a fix for this bug you can extend your battery time by enabling the modem to fully suspend when possible.<br />
<br />
Edit the following in file:<br />
<br />
For the new FSO2 edit /etc/freesmartphone/conf/GTA02/fsogsmd.conf <br />
<br />
deep_sleep == "always"<br />
<br />
Then kill fsogsmd and restart fsodeviced or reboot the phone.<br />
<br />
<br />
For old FSO (frameworks) edit /etc/frameworkd.conf <br />
<br />
ti_calypso_deep_sleep = always<br />
<br />
Then restart framework or reboot the phone.<br />
<br />
<br />
<br />
==Reporting bugs==<br />
<br />
SHR is a work in progress. If you experience issues, please report them back to SHR. With your report provide relevant logs from<br />
<br />
/var/log/<br />
<br />
To report a bug, please go to http://shr-project.org/trac/report<br />
<br />
Check if the bug is already reported. If not, add a ticket, be as much precise as you can in the title and the description, in what circumstances the issue happened and so on. If bug already exists, see if you can help fixing it by providing some fresh info.<br />
<br />
==More information==<br />
<br />
For SHR home page, source code and other resources, visit:<br />
<br />
* [http://trac.shr-project.org SHR Project Homepage]<br />
* [http://blog.shr-project.org SHR Blog]<br />
* [http://trac.shr-project.org Trac Bugtracker]<br />
* [http://git.shr-project.org Git Sourcecode-repository]<br />
* [http://build.shr-project.org Downloads on buildhost]<br />
* [http://lists.shr-project.org SHR User and Development Mailing Lists]<br />
<br />
==About this manual==<br />
<br />
This manual makes use of updated SHR-Unstable distribution which means that for example SHR-Testing or not updated SHR-Unstable might behave differently then stated in this manual.<br />
<br />
Please help extending this manual by correcting typos or discussing proposals on the talk page or email <tt>vanous @ penguin . cz</tt>. Thank you.<br />
<br />
[[Category:SHR]]<br />
[[Category:Manuals]]</div>Vanoushttp://openmoko.org/wiki/Manuals/SHRManuals/SHR2010-09-05T12:00:05Z<p>Vanous: /* SHR Introduction */ more supported devices</p>
<hr />
<div>{{Languages|Manuals/SHR}}<br />
{| align="right"<br />
| __TOC__<br />
|}<br />
<br />
==SHR Introduction==<br />
<br />
Welcome to '''[[SHR]]''', a community driven distribution for (not only) Openmoko, HTC Dream, PalmPré and Nokia n900 phones.<br />
<br />
<br />
<br />
[[Image:SHR-Logo.png|200px|thumb|center|SHR]]<br />
<br />
'''SHR''' (Stable Hybrid Release) is here to provide you with Root FileSystem images that you can easily install into your device to use as a daily phone and PDA. There are many prepackaged programs available that can be installed upon demand by users, it can also be used by developers as a base image for customized and flavored distribution or release. '''SHR unstable (SHR-U)''' is a testing environment before software gets stabilized and it is the main testing ground for [[FSO]] releases. '''SHR testing (SHR-T)''' images provide as much stability as possible for day-to-day usage.<br />
<br />
==Installation==<br />
<br />
===Getting SHR===<br />
<br />
You need to download two files for your version as above: kernel and root filesystem. Depending whether you will be installing into the internal [[NAND memory]] or on the [[microSD]] card, you need to either get .jffs2 file for NAND or .tar.gz file for microSD.<br />
<br />
- Get the latest kernel from the below linkpages. Starts with uImage-...<br />
<br />
- Get the root filesystem, for NAND: full-om-gta0_.jffs2, for µSD: full-om-gta0_.tar.gz<br />
<br />
The above are '''full''' images. You can also choose images with less packages, marked as '''lite'''.<br />
<br />
;GTA02 Neo FreeRunner<br />
*testing line: http://build.shr-project.org/shr-testing/images/om-gta02/<br />
*unstable 2.6.3* line: http://build.shr-project.org/shr-unstable/images/om-gta02/<br />
*( unstable 2.6.29 line: http://build.shr-project.org/shr-unstable.29/images/om-gta02/ )<br />
<br />
;GTA01 Neo 1973<br />
*testing line: http://build.shr-project.org/shr-testing/images/om-gta01/<br />
*unstable 2.6.29 line: http://build.shr-project.org/shr-unstable.29/images/om-gta01/<br />
<br />
;Image lite to image full<br />
If you flashed a '''lite''' image and want to upgrade to the '''full''' image run:<br />
<br />
opkg update<br />
opkg install task-shr-apps task-shr-games task-shr-gtk<br />
<br />
;Kernel modules<br />
The images of the filesystems mentioned above (.jffs2, .tar.gz), already contain the newest kernel modules.<br />
<br />
Get the new kernel modules if you only want to flash a new kernel, but not a whole new file system. From the same page as the kernel download the modules to match your kernel (their dates should be the same). Use sftp to put that file on the FreeRunner via the usb connection. Run gzip to unwrap the modules:<br />
# gzip -dc modules-...tar.gz | tar -xf - -C /<br />
<br />
===Installation on Flash===<br />
<br />
In order to install your SHR distribution directly to your FreeRunner Flash memory (NAND), you need to get the desired filesystem file ( <tt>.jffs2</tt> ) as described above and flash your device using the <tt>dfu-util</tt> tool.<br />
<br />
Please visit [[Flashing the Neo FreeRunner]] for more details about flashing and see [[Dfu-util]] for detailed information about the dfu-util.<br />
<br />
{{Note|Your battery must be charged (sufficiently) before NAND flashing. Symptom of insufficient charge: Your progress bar "####" stops while flashing. If so, you must charge, and later you should be able to make the complete flash.}}<br />
Commands to flash the filesystem and the kernel:<br />
<br />
for the GTA02 Neo FreeRunner:<br />
<br />
# dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D full-om-gta02.jffs2<br />
# dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-om-gta02-latest.bin<br />
<br />
for the GTA01 Neo 1973:<br />
<br />
# dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a rootfs -R -D full-om-gta01.jffs2<br />
# dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a kernel -R -D uImage-om-gta01-latest.bin<br />
<br />
===Installation on the microSD Card===<br />
<br />
Installing SHR on your microSD Card depends on the Bootloader you are using, ''uBoot'' or ''Qi''.<br />
<br />
In simple words, the difference between both systems resides on how you must prepare your microSD Card and files you use to fill them:<br />
<br />
* If you use ''uBoot'', you need to create two partitions. First partition, not so big, in FAT16 or ext2 where you have to place the kernel file (<tt>uImage-om-gta02-latest.bin</tt>) and second partition in ext2 or ext3 where you have to uncompress the filesystem file (<tt>shr-image-om-gta02.tar.gz</tt>).<br />
<br />
* If you use ''Qi'', you only need an ext2 partition into your µSD Card where you uncompress the filesystem image file (<tt>shr-image-om-gta02.tar.gz</tt>). In this case Qi Bootloader is going to look for the kernel image into the <tt>/boot</tt> directory for file named <tt>uImage-GTA02.bin</tt> .<br />
<br />
===Bootloaders===<br />
<br />
Make sure you have recent and correct versions of [[Booting_from_SD | uBoot]] or [[Qi]] installed, please visit the links for detailed information and tips. For example [[Android]] uses modified [[Qi]] which can cause you troubles when using SHR.<br />
<br />
===SHR version===<br />
<br />
Should you ever later wonder what version of SHR you have actually installed, please run<br />
<br />
timestamp of image creation:<br />
cat /etc/timestamp<br />
<br />
latest shr version from opkg upgrade (this version is changed everytime someone builds task-base on shr buildhost):<br />
cat /etc/shr-version<br />
<br />
{{Note|Please note that this is true only for shr-u, with shr-t running opkg update;opkg upgrade does not change the SHR version. Only flashing or a new image download can change the SHR version. But this will be also merged to shr-t later.}}<br />
<br />
==Running SHR==<br />
<br />
===First boot===<br />
[[Image:Shr-boot-preview.png|200px|thumb|center|SHR Boot Splash screen]]<br />
<br />
====Booting====<br />
First boot usually takes a bit longer as your phone's new software needs to do some initial setting up. It is recommended to reboot after this first boot (and after the initial setup), to make sure that all packages get initialized properly.<br />
<br />
====Initial Setup====<br />
<br />
During the first run, Setup is automatically initiated to walk the user through basic setup of the Enlightenment desktop environment. These steps vary as both Enlightenment desktop and SHR evolve, at this point preferred language and desktop profile options are available. The Profile offers to choose a preconfigured way of displaying the desktop. Illume2-SHR (with continuous development) and Illume-SHR (discontinued) profiles are available. '''Illume2-SHR''' is the recommended Profile. <br />
<br />
{| class="wikitable"<br />
| [[Image:SHR-Setup-Language.png|200px|thumb|language selection]]<br />
| [[Image:SHR-Setup-Profile.png|200px|thumb|theme selection]]<br />
| [[Image:SHR-Wizard.png|200px|thumb|SHR Wizard]]<br />
<br />
|}<br />
<br />
Note, you may need to ssh into the device and run /usr/bin/xinput_calibrator_once.sh if calibration is wrong. I found this using a Neo1973 and SHR images from around May 2010.<br />
<br />
====SHR Wizard====<br />
After the initial Setup, SHR Setting Wizard is launched to allow setting up your local phone settings and setting up root password. Sometimes a '''Please wait''' message is displayed for a long time, as the wizzard is waiting for the SIM card to be initialized.<br />
<br />
===First look===<br />
[[Image:SHR-First-Look.png|200px|thumb|Desktop screen]]<br />
[[Image:SHR-Task-Buttons.png|200px|thumb|Task switch buttons]]<br />
====Illume desktop====<br />
Illume desktop is the default home screen of the SHR desktop. <br />
<br />
Application definition files located in /usr/share/applications are displayed here as icons. All applications are ran fullscreen and you can switch between them by using the the '''< left''' or '''right >''' arrows on sliding shelve available by tapping Top Shelf on any empty space. To close applications, choose '''X''' from the same sliding shelve.<br />
<br />
Several icons (e-gadgets) are placed in the Top Shelve:<br />
<br />
The '''L''' icon is to switch between left/right mouse click. By taping this icon the icon gets changed to R and next tap will be as right click. After the click, the behavior is automatically switched back to Left click so any following taps are left click again.<br />
<br />
'''Mode Switch Icon''' allows to split the screen horizontally or vertically, thus allowing to display two applications at the same time.<br />
<br />
'''Keyboard icon''' pops up or hides the Keyboard.<br />
<br />
'''Illume Settings''' icon (represented by SHR logo) invokes the [[#Illume_settings | Illume desktop settings]]. <br />
<br />
'''Home Icon''' allows quick go to the home desktop/application.<br />
<br />
'''GSM''' and '''Battery''' status icons, as well as '''time''' are displayed by default, Bluetooth and WiFi status icons available in the setting of the Top Shelve content.<br />
<br />
<br />
To '''reconfigure the Top Shelve''' itself, use the L/R click icon to Right click on the Top Panel and choose: Illume Indicator->Set Content to add or remove items from the Top Panel. Or, upon right click on the Top Panel you can also choose Illume Indicator->Begin Move/Resize to move your icons around. To escape this mode, you must click on the L/R gadget's edge, it will switch to L, then choose R again, right click on the Top Panel and select Illume Indicator->Stop Move/Resize.<br />
<br />
<br />
====Keyboard====<br />
<br />
Keyboard comes up automagically when a text field is tapped or you can also toggle the keyboard by it's icon in the Top Shelve. In the Keyboard, dictionary switcher is the arrow-up on left side, alternative keyboard layouts are under the ABC button on the right. The Default keyboard has English dictionary enabled. For Space quick slide left-to-right, for Enter, quick slide up-down, to quick change keyboard layout quick slide down-up. While typing with a dictionary enabled keyboard, possible word options start appearing in the keyboard's upper part or more word options are available under the arrow-up on the left. When happy with the word, tap it, it will be pasted into the text field with a space attached. The Keyboard and dictionary can [[#Illume_keyboard_and_dictionaries | easily be localized]].<br />
<br />
====Copy and Paste====<br />
<br />
In '''E based''' applications, for example the phone suite (contacts, messages...), by tapping and holding down for over two seconds the Select-Paste menu will pop up. By pressing Select, you can now swipe through the text to select desirable part. Tap and hold down again, Copy-Cut-Cancel menu will appear to Copy to clipboard. Another long tap will provide Select-Paste for Paste.<br />
<br />
In '''Gtk''' based application, you can use keyboard for Ctrl-C (Copy) and Ctrl-V (Paste) or items in Menu if provided.<br />
<br />
In the Vala '''Terminal''', you can select simply by swiping through the text and for Paste there is an icon in the menu bar of this application.<br />
<br />
Copy & Paste between different toolkits has some limitations. See the table below. In Ventura, select is possible, but copy/paste doesn't seem to work at all.<br />
<br />
{| cellspacing="0" class="wikitable" border="1" style="font-size: 85%; text-align: left;width="100%"<br />
|-<br />
! From -> To <br />
! to GTK<br />
! to E<br />
! to Terminal<br />
|-<br />
| from GTK<br />
|style="background:#88FF88;"|Works<br />
|style="background:#88FF88;"|Works<br />
|style="background:red"|Doesn't work <br />
|-<br />
| from E<br />
|style="background:red"|Doesn't work <br />
|style="background:#88FF88;"|Works <br />
|style="background:#88FF88;"|Works<br />
|-<br />
| from Terminal<br />
|style="background:red"|Doesn't work <br />
|style="background:#88FF88;"|Works <br />
|style="background:#88FF88;"|Works<br />
|-<br />
|}<br />
<br />
====Alarm====<br />
<br />
The Alarms application (installed by default) allows alarm presetting for single or repeatable alarms. If you set an alarm and turn your Openmoko FreeRunner off, at the time of the alarm the phone will be powered up and alarm will sound.<br />
<br />
====Phone applications====<br />
<br />
Besides other software, SHR comes with 4 main phone applications: ''Dialer'', ''Contacts'', ''Messages'' and ''Phone log''.<br />
<br />
{|<br />
| [[Image:SHR-Dialer.png|200px|thumb|Dialer]]<br />
| [[Image:SHR-Contacts.png|200px|thumb|Contacts]]<br />
| [[Image:SHR-Mesages.png|200px|thumb|Messages]]<br />
| [[Image:SHR-Phonelog.png|200px|thumb|Phone log]]<br />
|}<br />
<br />
<br />
=====PIM data=====<br />
<br />
======Storage======<br />
PIM data (contacts, messages etc.) are stored through internal opimd storage mechanism into <br />
<br />
/etc/freesmartphone/opim/pim.db<br />
<br />
This database can easily be copied from one SHR installation to another, for example due to a need for reflashing. The Contacts application can display a picture of the contact. As the pim.db database contains a path to the picture files only but not the pictures themselves, therefore, in case of PIM data backup or transfer, these picture files '''need to be copied too'''.<br />
<br />
======SIM Contacts======<br />
<br />
SHR phone applications do not read SIM contacts by default but you can use SIM Manager to access your SIM contacts '''SHR Settings -> Others -> SIM Manager''', which allows you to edit and import the SIM contacts into the internal storage. You can also use Pisi to import your SIM contacts into opimd.<br />
<br />
======Synchronization======<br />
<br />
'''[[Pisi]]''' is an application for synchronizing PIM data and can be used for import and export your contacts, calendar entries etc. between various sources, like VCF, LDAP, Google and more. To install Pisi:<br />
<br />
opkg install pisi<br />
<br />
After installation, edit Pisi configuration in '''.pisi/conf''' in your home directory. To have a correct opimd fields support, make sure '''field_support=TRUE''' is enabled in opimd section.<br />
<br />
With the installed package you have a well-documented sample that is placed at <br />
/usr/share/doc/pisi/conf.example<br />
You may copy the file and rename this file to<br />
/home/root/.pisi/conf<br />
as a starting point - then edit this file in order to configure your PIM synchronization data sources. Look at section<br />
<br />
[opimd]<br />
description=OPIMD Contacts<br />
module=contacts_opimd<br />
field_support=TRUE<br />
<br />
=====Idle screen=====<br />
[[Image:SHR-Idle_Screen.png|200px|thumb|Idle Screen with GSM operator strength and name. GPS, WiFi, Display and CPU are requested, Battery status.]]<br />
Upon press of the AUX button Idle Screens locks up the display. AUX press or a finger slide on the Slider unlocks the screen.<br />
<br />
At the top, status icons are shown to indicate what is going on in the phone:<br />
<br />
From left to right:<br />
GSM strength and operator. Requested Resources (GPS, Display etc., when for example Display is requested, the screen will not dim). Battery capacity.<br />
<br />
====Hardware Buttons====<br />
<br />
=====Power Button=====<br />
<br />
[[Image:SHR-Quick-Settings.png|200px|thumb|Quick Settings]]<br />
<br />
The '''PWR''' (Power) button is mapped to start [[#quick_settings | Quick Settings]] screen (Illume System menu in older versions) on a short press. <br />
<br />
Mapping of the PWR button be configured via the '''Illume Settings-> Input -> Key Bindings'''.<br />
<br />
Pressing the Power button for longer then 8 seconds will force a complete power down of the device. This is hardconfigured in the kernel.<br />
<div id="quick_settings"> </div><br />
The '''Quick Settings''' screen provides several toggles: Airplane mode, Phone profiles, Power settings and Power buttons.<br />
<br />
=====Auxiliary Button=====<br />
The '''AUX''' (Auxiliary) button is mapped to toggle on/off the SHR Idle screen. Mapping of this button is configured in /etc/phonefsod.conf<br />
<br />
idle_screen = aux,lock<br />
<br />
You can configure the [[#idle_screen | Idle Screen]] to come up even during active phone call by adding '''phone''' to the setting: <br />
<br />
idle_screen = aux,lock, phone<br />
<br />
<div id="idle_screen"> </div><br />
The '''Idle Screen''' shows current date and time, missed calls and messaged and also what [[#FSO_Resources | FSO resources]] are currently being requested - used.<br />
<br />
======Replacing idle screen======<br />
<br />
If you wish to use the E simple LOCKED screen instead of the SHR Idle Screen, edit '''/etc/phonefsod.conf''' to this:<br />
<br />
# when to show idle screen<br />
# ...<br />
# idle_screen = aux,lock<br />
idle_screen =<br />
<br />
You need to restart phonefsod to make the change happen.<br />
<br />
Also, change key mapping for the AUX button by setting '''Illume Settings''' -> '''Input''' -> '''Key Bindings''', bind the key '''XF86Phone''' to '''Desktop Simple Lock'''<br />
<br />
====Settings applications====<br />
<br />
Many desktop and phone settings are possible to do via graphical interface. [[#SHR_Settings | SHR Settings]] provides access to most common phone personality settings and is accessible by tapping Settings icon on the desktop. [[#Illume_settings | Illume settings]] (and Enlightenment desktop settings) are accessible on Top shelve by tapping the "SHR Logo" icon. Also, FSO and SHR phoneui applications have configuration files in /etc where some of the above mentioned apps write and that can be edited manually.<br />
<br />
===First steps===<br />
<br />
Right after installation and first boot you might want to do a few initial steps like adjusting the call volume and some other tasks.<br />
<br />
====Audio - Call Volume====<br />
<br />
During the first phone call please use the Volume and Mic sliders on the Active Call Screen and adjust them to fit your preferences. The new improved settings will be used for all in/out-going calls thereafter.<br />
<br />
====Network Connection====<br />
<br />
[[#Networking|Establish network connection]] and SSH into your phone. You can establish connection either via USB to your desktop and enable NAT or you can connect through Wifi.<br />
<br />
====Initializing the opkg database====<br />
''Initialize the opkg database'' in order to install some applications from SHR repositories or from other sources, for example [http://opkg.org opkg.org]. While being online, you need to run<br />
<br />
opkg update<br />
<br />
Searching in the opkg database can take a long time. You can speed things up by dumping the database into a file and grepping it through. Do this only once or after every opkg update:<br />
<br />
opkg list > packages.txt<br />
<br />
Then you can search quickly for package name, for example for [[Navit|navit]]:<br />
<br />
grep navit packages.txt<br />
<br />
====SwapSpace====<br />
<br />
When the RAM is used up, applications get killed. This is particularly bad while doing opkg upgrade. Therefore you might want to create a swap space. Read [[SwapSpace]] article or the [http://shr-project.org/trac/wiki/swap swap article on the SHR wiki].<br />
<br />
==Settings==<br />
===SHR Settings===<br />
[[Image:SHR-Settings-main.png|200px|thumb|SHR Settings]]<br />
<br />
SHR Settings is the main setting application of SHR. It provides an easy way of setting up your phone to your liking - from phone related settings, to requesting resources in order to prevent screen dim or suspend (for example while using GPS).<br />
<br />
Please refer to [[#FSO_Resources | this section]] about a better way to manage preventing screen dim or suspend.<br />
<br />
While some settings are persistent over reboots, others are not.<br />
<br />
====Main Screen====<br />
The main screen is divided into eight categories, which contain several modules. Every SHR Settings module has a specified task - for example controlling the GSM antenna power, setting the time etc.<br />
<br />
====Phone====<br />
Here you can set if the GSM antenna is on and if your phone number is shown when you call someone.<br />
<br />
'''GSM'''<br />
In GSM settings you can turn off and on GSM module. After turning off antenna, whole GSM modem is turned off.<br />
<br />
To list available providers, click on Operators button. Scanning can take some time. After a while, a list of operators should pop up.<br />
<br />
You can't connect to operators marked [forbidden].<br />
<br />
Selecting an operator from the list also changes modem registration mode to manual. It won't register to other network, even if some is available and has better signal strengh. To return to automatic mode, click "Automatic" button in operator list.<br />
<br />
'''Call'''<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Phone.png|200px|thumb|Phone settings]]<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-List-providers.png|200px|thumb|List providers]]<br />
<br />
|}<br />
<br />
You can set if your phone number should be displayed to other party. You can either depend on network decision ("By network") or force it manually ("Manual")<br />
<br />
'''Phoneutils'''<br />
<br />
For the default SHR phone applications to be able to correctly parse incoming calls/messages and match them with your contacts, you will need to set the right country code for your location. (for example 420 for Czech republic) for more info, please go to: http://wiki.openmoko.org/wiki/Phone_Prefixes<br />
<br />
'''SIM'''<br />
<br />
Here you can view some informations about your SIM card and clean phone and messagebooks.<br />
<br />
====Profiles====<br />
<br />
Here you can select the current profile, which the device should use to determine ring tone etc.<br />
<br />
'''Current profile'''<br />
<br />
Here you can adjust properties of the currently used profile. <br />
<br />
To change the ring tone, click the "Change" button.<br />
<br />
To use your own ring tone, place it in /usr/share/sounds directory.<br />
<br />
After selecting a sid tune as the ring tone, there are available controls to select tune number from the file.<br />
<br />
If you like to test a .sid you can play it using this command on the FR:<br />
<br />
gst-launch filesrc location=Arkanoid_PSID.sid ! siddec tune=2 ! alsasink<br />
<br />
Note that it's a ! used and not a | to construct the gstreamer pipe command.<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Profiles.png|200px|thumb|Profiles]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Profiles-Ringtones.png|200px|thumb|Ringtones]]<br />
<br />
|}<br />
<br />
====Connectivity====<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Connectivity.png |200px|thumb|Connectivity top]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Connectivity2.png |200px|thumb|Connectivity bottom]]<br />
|}<br />
<br />
'''WiFi'''<br />
<br />
With the "WiFi radio" toggle you can set, if the wifi module is powered. WiFi radio has to be turned on before trying to connect to a WiFi network, unless you try to connect through [[Mokonnect]] which is capable of powering it up.<br />
<br />
'''GPRS'''<br />
<br />
To enter APN, login and password fields, just click on the actual value (default: "internet"). Your phone provider can provide the required configuration options.<br />
<br />
{{Note|You can also use Mokonnect to manage your GPRS connection}}<br />
<br />
'''USB'''<br />
<br />
With this toggle you can switch USB port between device (Neo to PC) or host (device to Neo) modes.<br />
<br />
'''Bluetooth'''<br />
<br />
To power up Bluetooth module, switch the "Bluetooth radio" toggle to "On". After that, the "Visibility" toggle should arrive - set it to "On" if you want your FR to be visible by other Bluetooth devices on scanning.<br />
<br />
====Power====<br />
<br />
'''Battery'''<br />
<br />
This module displays informations about battery state - charge, voltage, remaining time etc. To update the data, click the "Update" button.<br />
<br />
Here you can also force enable 500mA charging.<br />
<br />
'''Display'''<br />
<br />
With this slider you can easily set the backlight brightness.<br />
<br />
{{Note|This setting isn't permanent over sessions. At boot backlight is set back to 80%.}}<br />
<br />
'''Power'''<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Power.png |200px|thumb|Power]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Timeouts.png |200px|thumb|Timeouts]]<br />
|}<br />
<br />
'''Timeouts'''<br />
<br />
Timeouts are reached in this order: Busy state -> idle -> idle dim -> idle prelock -> lock -> suspend. <br />
<br />
{{Note|Storing of this setting via D-bus calls is not supported in the new API of Vala rewrite of FSO2 and therefore SHR Settings doesn't have a functional setting for this.}}<br />
<br />
You can set values of idle timeouts manually. The default parameters are stored in '''/etc/freesmartphone/conf/GTA02/fsodeviced.conf''' but customized '''.fsodeviced.conf''' file in your home directory will take precedence (if it exists, the one in /etc/... will be ignored, so you have to copy the whole file and tweak it):<br />
<br />
[fsodevice.kernel_idle]<br />
suspend = 20<br />
lock = 2<br />
idle_prelock = 12<br />
idle = 10<br />
idle_dim = 20<br />
<br />
To turn off a timeout, set it to -1.<br />
<br />
====Appearance====<br />
<br />
'''Theming'''<br />
[[Image:SHR-Neo-Theme.png|200px|thumb|Neo theme]]<br />
<br />
The Apperance section allows you to change between installed themes. To install more themes, see also [[#Installing themes | Installing themes]].<br />
<br />
You can change finger size - this will mainly effect vertical spacing between widgets.<br />
<br />
Switching between engines:<br />
<br />
E can be switched to use different engines. The default engine is x11. Alternative engine x11-16 is not supported and results in buggy behavior of several applications, for example the phone suite or Ventura browser. It's usage is not recommended.<br />
<br />
Changing system boot Splash screen is also possible in this module. To install more splash screens, see also [[#Installing splash screen themes|Installing splash themes]].<br />
<br />
====Position====<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-GPS.png |200px|thumb|center|GPS]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-GPS-Satelites.png |200px|thumb|GPS Satelite details]]<br />
|}<br />
<br />
'''GPS'''<br />
<br />
By default, GPS is turned on only when requested by an application. That state corresponds to "Auto" setting. After changing to "Manual", you can force set it to on or off.<br />
<br />
'''GPS information'''<br />
<br />
This page can be used to monitor GPS status. You either have to turn GPS on manually or start another application to enable the GPS.<br />
<br />
You can also view information about every visible satellite and check, which are used for getting a fix. To do that, click "Satellite details".<br />
<br />
'''Remove AGPS data'''<br />
If you experience problems with GPS, turn it off, click "Remove AGPS data" and reboot your Neo.<br />
Assisted GPS ([[aGPS]]) support GPS receiver to find position by non-satellite information.<br />
<br />
====Date/time====<br />
<br />
[[Image:SHR-Settings-Date-Time.png |200px|thumb|Date & Time]]<br />
<br />
'''Time'''<br />
<br />
Here you can view and set the time. By default, the time is just displayed, To adjust it, click on "Set time".<br />
<br />
After finishing adjusting, click the "OK" button.<br />
<br />
'''Date'''<br />
<br />
This module displays the current date.<br />
<br />
====Others====<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
[[Image:SHR-Settings-Others.png |200px|thumb|Others]]<br />
<br />
'''PIM'''<br />
<br />
Pim data are stored in opimd domains. Every opimd domain has different backends to store its data to. The domain reads data from every backend and writes data to the default backend. This elector allows you to choose the backend that stores newly generated data, it doesn't copy or move existing data to a different backend.<br />
<br />
'''Services'''<br />
<br />
The services selector is listing scripts from /etc/init.d/ directory.<br />
<br />
After clicking on a servis, you can either start, restart or stop the service and view the result.<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Services.png |200px|thumb|center|Services]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Service-restart.png |200px|thumb|Services debug screen]]<br />
|}<br />
<br />
<br />
'''Userspace backups'''<br />
<br />
Here you can either archive or restore your files and configurations.<br />
<br />
=== Illume settings ===<br />
<br />
The Illume desktop can be easily customized - tap the Settings icon (SHR Logo) on the Top Shelve.<br />
<br />
'''Illume settings''' provides various options to alter the desktop environment. You can change sizes of elements, single or double click, wallpaper. To access all the various options, open Illume Settings and slide the visible icons to the left, to view more options on the right hand side.<br />
<br />
Some setting screens are not resized properly to fit the phone's display - for example the Wallpapper setting. This is a known bug already reported upstream.<br />
<br />
<!-- [[Image:SHR-Top-Shelve.png|200px|thumb|Top Shelf]] --><br />
<br />
==Localization==<br />
<br />
=== Localize SHR manually ===<br />
<br />
[[Image:SHR-Illume-Settings-Languages.png|200px|thumb|Setting Language]]<br />
<br />
====Desktop environment====<br />
<br />
You can change the language of the SHR desktop environment by using the Settings of Illume. For Example, for Czech language: in the Illume top shelf go to Settings (SHR Logo) -> Language -> Language Settings -> and choose: Čeština. If your language is not in the menu you can install by using opkg.<br />
<br />
You can list all available languages by running:<br />
<br />
opkg list | grep eglibc-locale-<br />
<br />
And install the language of your choice (for example czech):<br />
<br />
opkg install eglibc-locale-cs<br />
<br />
After this, the Language Settings of Illume will offer Czech. <br />
<br />
This will localize the Illume environment and will also set correct lang environment variable of your desktop. <br />
<br />
====Applications====<br />
<br />
If you wish to have other applications localized, you need to install translation for each of them (presuming it is available):<br />
<br />
This will install czech localization for SHR phone applications, SHR Settings and TangoGps:<br />
<br />
opkg install libframeworkd-phonegui-efl-locale-cs shr-settings-locale-cs tangogps-locale-cs<br />
<br />
====Terminal environment====<br />
<br />
For localized terminal environment (ssh login) set lang variables in /etc/profile.d/locale.sh, example for Czech language:<br />
<br />
export LANG=cs_CZ<br />
export LC_ALL=cs_CZ<br />
<br />
====Illume keyboard and dictionaries====<br />
[[Image:Illume-keyboards-terminal-dutch-nl-screenshot.png| Dutch terminal virtual keyboard|256px|thumb]]<br />
→ more details on page [[Illume keyboard]]<br />
<br />
Unlike other input methods for mobile devices, the Illume keyboard is corrective rather than predictive. It detects what you mean, even if some letters mistyped. If you accidently hit some keys next to the correct one Illume still reckognizes the word. This kind of compensates for the small size of the keys. Keep a key pressed for a longer time to affirm you really mean it. <br />
<br />
An English dictionary is used by default. A few dictionaries for other languages are included in the SHR distribution. In addition, every dictionary for [http://en.wikipedia.org/wiki/MySpell myspell] can be used. <br />
<br />
You can install a different keyboard with a layout which fits your language or alternatives for the default keyboards like the numerical one. The localized [[Illume keyboard]]s are available in the SHR repository under the name ''illume-keyboard-LANG''.<br />
<br />
==== German (and Austria) Language ====<br />
<br />
See [[Configure_SHR_for_German-speaking_use]] for detailed customization for german speaking.<br />
<br />
===Date and time===<br />
{{Note|This needs a complete and correct rewrite.}}<br />
<br />
Date and time are automatically set from GPS or Network. The easiest way of setting the time for the first time is to run TangoGps (GPS & Map icon) and obtaining GPS fix. Time will then be set automatically.<br />
<br />
The local timezone is automatically retrieved from the GSM network.<br />
<br />
It is possible to instruct framework on how to set the time and timezone in /etc/frameworkd.conf :<br />
<br />
[otimed]<br />
# a list of time/zone sources to use or NONE<br />
timesources = GPS,NTP<br />
zonesources = GSM<br />
# use an ip address here, otherwise DNS resolution will block<br />
ntpserver = 134.169.172.1<br />
<br />
To disable automatic date/zone settings, simply create an empty [otimed] section in /etc/frameworkd.conf<br />
<br />
Timezone change<br />
<br />
Create a symlink named /etc/localtime which points to the appropriate file in /usr/share/zoneinfo. For example, if you're in France., the following command will link the correct zoneinfo file to your /etc/localtime, giving you the correct time:<br />
<br />
ln -sf /usr/share/zoneinfo/Europe/Paris /etc/localtime<br />
<br />
Afterwards, edit /etc/timezone if necessary [?]<br />
<br />
Local timezone work instantly for the current boot when:<br />
<br />
TZ="Europe/Paris"<br />
export TZ<br />
<br />
For a permanent timezone change edit /etc/profile and change to:<br />
<br />
TZ="Europe/Paris"<br />
<br />
<br />
If you use UTC time, set '''UTC=yes''' in '''/etc/default/rcS'''.<br />
<br />
Adjusting time manually:<br />
<br />
Via SHR-Settings -> Date/time -> Set time<br />
<br />
From linux based desktop:<br />
<br />
ssh root@192.168.0.202 "date -u -s `date -u +%m%d%H%M%Y.%S`"<br />
<br />
The above does NOT work from Ubuntu as of 4/2/2010, the proper format is:<br />
<br />
ssh root@192.168.0.202 "date -u -s `date -u +%Y.%m.%d-%H:%M:%S`"<br />
<br />
Set the hardware clock to the system time:<br />
<br />
hwclock --systohc<br />
<br />
Is this better?:<br />
<br />
hwclock --utc --systohc<br />
<br />
==FSO Resources==<br />
<br />
[[FSO]] is in control of each device. These are called ''resources''. If the software wanting to use the device is capable of requesting this resource via <tt>d-bus</tt>, FSO will do this, otherwise you might need to power the device manually. After the requested resource is released, FSO will power it down. Manual resource request can be done through ''SHR Setting'' or you can use <tt>fsoraw</tt> command. (Using fsoraw is faster and better than running dbus commands)<br />
<br />
opkg install fsoraw<br />
<br />
Example of usage fsoraw:<br />
<br />
fsoraw -r Display mokomaze<br />
<br />
See [[FSO Resources]] for more details on using the following resources:<br />
<br />
'''Wifi'''<br />
<br />
Unless this resource is enabled you've no eth0 and wifi module is completely un-powered. Use the [[Mokonnect]] network manager to set up networks, it will power Wifi up automatically when needed.<br />
<br />
'''Bluetooth'''<br />
<br />
You need to have this resource requested to have bluetooth module powered.<br />
<br />
'''GPS'''<br />
<br />
The fso-gpsd is a daemon waiting for gsmd connections, automatically powering the device on and off. When a connection exists, it powers up the GSM. In SHR Settings you can switch GPS completely off SHR Settings -> GPS -> Manual > Off<br />
<br />
'''GSM'''<br />
<br />
You need to have this resource requested to have GSM module powered.<br />
<br />
'''Display'''<br />
<br />
While this resource is requested the display won't be blanked and suspend is disabled.<br />
<br />
'''CPU'''<br />
<br />
While this resource is requested then suspend is disabled. Display will blank as normal.<br />
<br />
'''Test'''<br />
<br />
A test resource.<br />
<br />
'''UsbHost'''<br />
<br />
While this resource is requested the USB is turned into powered USB Host mode.<br />
<br />
'''Accelerometer'''<br />
<br />
You need to have this resource requested to have the Accelerometer module powered.<br />
<br />
==Networking==<br />
<br />
There are several ways of networking - Wifi, USB, Bluetooth and Gprs:<br />
<br />
===USB===<br />
<br />
By default, USB networking is enabled in <tt>/etc/network/interfaces</tt>, where enhanced configuration can be direct edited. The phone default IP address is 192.168.0.202. Some setup is required on the desktop side, please read [[USB Networking]].<br />
<br />
===WiFi===<br />
<br />
WiFi manager [[iliwi]] is available by default for search/connect/making default a wifi connection. ''iliwi'' uses key only in hex format. The Wifi device is not required to be manually turned on via SHR-Settings as ''iliwi'' will automatically enable the device when needed and disable it after use. iliwi needs to stay running to keep the WiFi connection enabled.<br />
<br />
When WiFi is connected, the Idle screen show the icon of the WiFi resource being occupied.<br />
<br />
===GPRS===<br />
<br />
GPRS Credentials are set during the first run in SHR Wizard and you may edit them at any time via SHR settings or direct editing of /etc/phonefsod.conf. GPRS connection can then be established/closed via SHR Settings or through SHR Quick Settings (available under the Power button). SHR Quick Settings - Network tab allows also connection sharing - this will share the GPRS connection with USB network and run DHCP server to provide the client with an IP address.<br />
<br />
When GPRS is connected, the idle screen shows a small G above the signal strength indicator.<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |<br />
[[Image:SHR-Gprs-Share.png|200px|thumb|GPRS + Connection sharing]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " | <br />
[[Image:SHR-Iliwi-Scan.png|200px|thumb|Iliwi WiFi scanning]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " | <br />
<br />
[[Image:SHR-Iliwi-Connect.png|200px|thumb|Iliwi WiFi connecting]]<br />
<br />
|}<br />
<br />
==Bluetooth==<br />
<br />
Bluetooth can be used for several different applications - file transfer (OBEX), networking, input devices (HIDD), music playing (A2DP), calling etc. In some occasions, the devices need to be authorized - paired. At the moment, support for some bluetooth functions is better than for others - it is possible to do all mentioned above with the notice that phone calls with bluetooth headset are always routed to the bluetooth even if the bluetooth headset is not around, making it quite difficult to use.<br />
<br />
In the SHR repositories are applications ready to be installed (by opkg) that already do provide bluetooth support. This means that they request the bluetooth resource automatically, can search bluetooth devices around, help you with pairing and can perhaps even reconnect bluetooth headset upon resume from suspend. From applications that have some bluetooth support some are for example [[Launcher]] (home screen launcher and phone suite), [[Podboy]] (podcast player), [[Elmtooth]] (bluetooth manager). In order to set up bluetooth for phone calls, some manual setup from [[#GSM_phone_calls_with_bluetooth_headset | bellow]] is still required.<br />
<br />
===Bluez3 - the manual non D-Bus way===<br />
<br />
If you want to use the bluetooth device directly, you need to turn the bluetooth radio on in SHR Settings -> Connectivity -> Bluetooth Radio: On. You can also make the bluetooth device visible here.<br />
<br />
====OBEX file transfer====<br />
<br />
There are several obex programs allowing file transfer, all in console at the moment. Obexpush installs obextool, and opd daemon:<br />
<br />
opkg install obexpush<br />
<br />
Default receiving path (editable in /etc/default/opd_args ) does not exist, so create it<br />
<br />
mkdir /var/obexpush<br />
<br />
Files are then received automatically, no notice, no confirmation... they just silently appear in /var/obexpush<br />
<br />
To send some files, first scan for devices:<br />
<br />
hcitool scan<br />
Scanning ...<br />
00:16:41:F5:A5:BC laptop<br />
<br />
Then send the file onto bluetooth address found in the scan:<br />
<br />
obextool push image.jpg 00:16:41:F5:A5:BC 10<br />
<br />
====Connect Bluetooth keyboard====<br />
<br />
hidd --search<br />
<br />
Editors note: This is the old bluez3 way, but it works. New bluez4 way will replace this.<br />
<br />
===Bluez4 - D-Bus based way===<br />
<br />
SHR uses bluez4 which is completely different from bluez3. The bluetoothd is taking care of most of the bluetooth now. Please see [[Manually using Bluetooth]] for detailed information about using bluetooth and also for a list of supported devices.<br />
<br />
====Pairing====<br />
<br />
[[Emtooth]] is a bluetooth manager. It provides setting up bluetooth device name, pairing/unpairing, visibility setting and more. Install Emtooth:<br />
<br />
opkg install emtooth<br />
<br />
It will discover nearby devices, double tapping on found device will initiate pairing process.<br />
<br />
====GSM with bluetooth headset====<br />
<br />
In order to use bluetooth headset for phone calls, several simple steps need to be done.<br />
<br />
1). Your bluetooth headset device must be [[#Pairing | paired]] first.<br />
<br />
2). [[#Configuring_FSO | Add]] your bluetooth headset into FSO configuration.<br />
<br />
<br />
Please note: phonecalls are now always routed to the bluetooth headset. <br />
After startup and after every resume, the headset needs to be [[#Re-Connecting_the_bluetooth_headset |reconnected]].<br />
<br />
=====Configuring FSO=====<br />
<br />
Now we must tell frameworkd that you have a bluetooth headset. Headset parameters should be set in<br />
<br />
/etc/freesmartphone/opreferences/conf/phone/default.yaml<br />
<br />
Parameters bt-headset-enabled and bt-headset-address (see opreferences/schema/phone.yaml for semantics).<br />
<br />
You need to restart FSO for the changes to take effect.<br />
<br />
# /etc/init.d/frameworkd restart<br />
<br />
example of my /etc/freesmartphone/opreferences/conf/phone/default.yaml:<br />
<br />
message-length: 7<br />
message-tone: notify_message.wav<br />
message-vibration: 1<br />
message-volume: 10<br />
ring-loop: 1<br />
ring-tone: ringtone_ringnroll.wav<br />
ring-vibration: 1<br />
ring-volume: 10<br />
bt-headset-enabled: 1<br />
bt-headset-address: 00:09:DD:31:92:98<br />
<br />
=====Re-Connecting the headset=====<br />
<br />
You might need to get the bluetooth headset connected manually on the beginning and also after suspend:<br />
<br />
mdbus -s org.bluez $BTADAPTER/dev_xx_xx_xx_xx_xx_xx org.bluez.Headset.Connect<br />
<br />
where xx_xx_xx_xx_xx_xx is address of the device, for example:<br />
<br />
mdbus -s org.bluez $BTADAPTER/dev_00_09_DD_31_92_98 org.bluez.Headset.Connect<br />
<br />
Hopefully, your bluetooth headset now works. Good luck!<br />
<br />
==System Customizing==<br />
<br />
===Command scheduling===<br />
<br />
The traditional ''at'' command in ''SHR'' is modified to work over dbus. This modified ''at_over_dbus'' will run scheduled task at required time - actually it will even automatically wake up the phone from suspend or start it if the phone was switched off.<br />
<br />
To schedule a command to be executed at a particular time, one must:<br />
<br />
Place commands in a script in ''/var/spool/at'' and name it like <br />
<br />
TIMESTAMP.NAME.NUMBER<br />
<br />
where<br />
<br />
where TIMESTAMP is the seconds since 1970-01-01 00:00:00 UTC when the command should be run. <br />
The rest (NAME, NUMBER) is up to you. Finally you have to:<br />
<br />
touch /var/spool/at/trigger<br />
<br />
Also, make sure to have atd running. You are responsible to remove the script when unnecessary. It will run once more if you/other program write to the trigger file during the execution, so you may consider removing the<br />
executable flag of the script (if it is long running) or rename the script from within for example like this: <br />
<br />
mv "$0" "x$0.$$"<br />
<br />
===Installing splash screen themes===<br />
<br />
List available splash screen themes<br />
<br />
opkg list | grep splash-theme<br />
<br />
Install one of the available themes<br />
<br />
opkg install shr-splash-theme-dontpanic<br />
<br />
Then go to '''SHR Settings -> Appearance -> Splash settings'''. Here you can preview installed themes and change the default one.<br />
<br />
===Installing themes===<br />
<br />
Every theme is made of several components (a theme for illume, theme for the phone applications, theme for etk and so on). There is a SHR metapackage for each theme that allows installing the complete theme in one go.<br />
<br />
List available SHR theme metapackages:<br />
<br />
opkg list | grep shr-theme<br />
<br />
Install one of the available themes<br />
<br />
opkg install shr-theme-gry<br />
<br />
Then go to '''SHR Settings -> Appearance -> Elementary Settings'''. Here you can preview installed themes and choose the preferred one.<br />
<br />
The Illume screen requires to change theme via '''Settings (SHR Logo) -> Look -> Theme'''. Here you can preview installed themes and choose the preferred one.<br />
<br />
===Enable mouse cursor=== <br />
<br />
edit line 143 of /etc/X11/Xserver and erase '''-nocursor'''<br />
<br />
ARGS="$ARGS"<br />
<br />
<br />
<br />
===Random errors===<br />
No icons, no GSM functions etc. happen mostly due to '''errors on your µSD''' card. Remove your card and fix it in card reader or by booting to another partition (nand) or by reboot and mount read only, then run fsck.<br />
<br />
For reboot into nand and fix 1st partition of ext2 on your card<br />
<br />
fsck.ext2 /dev/mmcblk0p1<br />
<br />
===GSM modem 1024 suspend bug===<br />
<br />
The calypso GSM modem suffers a known [[1024]] hardware bug that causes unreliable GSM function. To work it around, SHR by default doesn't suspend the modem completely. If you have undertaken a fix for this bug you can extend your battery time by enabling the modem to fully suspend when possible.<br />
<br />
Edit the following in file:<br />
<br />
For the new FSO2 edit /etc/freesmartphone/conf/GTA02/fsogsmd.conf <br />
<br />
deep_sleep == "always"<br />
<br />
Then kill fsogsmd and restart fsodeviced or reboot the phone.<br />
<br />
<br />
For old FSO (frameworks) edit /etc/frameworkd.conf <br />
<br />
ti_calypso_deep_sleep = always<br />
<br />
Then restart framework or reboot the phone.<br />
<br />
<br />
<br />
==Reporting bugs==<br />
<br />
SHR is a work in progress. If you experience issues, please report them back to SHR. With your report provide relevant logs from<br />
<br />
/var/log/<br />
<br />
To report a bug, please go to http://shr-project.org/trac/report<br />
<br />
Check if the bug is already reported. If not, add a ticket, be as much precise as you can in the title and the description, in what circumstances the issue happened and so on. If bug already exists, see if you can help fixing it by providing some fresh info.<br />
<br />
==More information==<br />
<br />
For SHR home page, source code and other resources, visit:<br />
<br />
* [http://trac.shr-project.org SHR Project Homepage]<br />
* [http://blog.shr-project.org SHR Blog]<br />
* [http://trac.shr-project.org Trac Bugtracker]<br />
* [http://git.shr-project.org Git Sourcecode-repository]<br />
* [http://build.shr-project.org Downloads on buildhost]<br />
* [http://lists.shr-project.org SHR User and Development Mailing Lists]<br />
<br />
==About this manual==<br />
<br />
This manual makes use of updated SHR-Unstable distribution which means that for example SHR-Testing or not updated SHR-Unstable might behave differently then stated in this manual.<br />
<br />
Please help extending this manual by correcting typos or discussing proposals on the talk page or email <tt>vanous @ penguin . cz</tt>. Thank you.<br />
<br />
[[Category:SHR]]<br />
[[Category:Manuals]]</div>Vanoushttp://openmoko.org/wiki/OpenWrtOpenWrt2010-09-02T19:57:57Z<p>Vanous: /* Add packages from extra feeds */</p>
<hr />
<div>{{Languages|OpenWrt}}<br />
<br />
News about OpenWrt on Neo FreeRunner is at [http://nanl.de/blog/] and [http://nanl.de/blog/category/tech/embedded-systems/openmoko/].<br />
<br />
= Installing pre-built image =<br />
<br />
== Installing to [[NAND-flash]] ==<br />
<br />
As usual, you need rootfs and kernel (assuming you're using [[Qi]] or [[U-Boot]]) which are available at :<br />
http://nanl.de/files/openwrt/openmoko/<br />
<br />
wget http://nanl.de/files/openwrt/openmoko/LATEST_openwrt-s3c24xx-2.6-root.jffs2-128k<br />
wget http://nanl.de/files/openwrt/openmoko/LATEST_openwrt-s3c24xx-2.6-uImage<br />
<br />
# Neofreerunner flashing:<br />
#<br />
sudo dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D LATEST_openwrt-s3c24xx-2.6-root.jffs2-128k<br />
sudo dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D LATEST_openwrt-s3c24xx-2.6-uImage<br />
#<br />
# The IDs (0x1d50:0x5119) was found by using the command #dfu-util --list<br />
# and looking for name="USB Device Firmware Upgrade".<br />
<br />
Then boot from flash.<br />
<br />
== Installing to SD card via PC and Freerunner ==<br />
{{note|Not succesful yet (20090728_r16973, [[U-Boot]]), but files seems ok.}}<br />
<br />
For booting from SD card fetch this rootfs and the kernel image (same than above mentioned):<br />
wget http://nanl.de/files/openwrt/openmoko/LATEST_openwrt-s3c24xx-rootfs.tgz<br />
wget http://nanl.de/files/openwrt/openmoko/LATEST_openwrt-s3c24xx-2.6-uImage<br />
<br />
[[Booting_from_SD#Prepare_the_SD_card|Prepare your SD, SDHC card for kernel and rootfs partitions]].<br />
<br />
Assuming 8MB kernel partition mounted as /mnt/mokokernel and /path is where the file is stored on your PC. Run command from PC:<br />
<br />
scp /path/LATEST_openwrt-s3c24xx-2.6-uImage root@192.168.0.202:/mnt/mokokernel/uImage-GTA02.bin<br />
<br />
Assuming rootfs partition mounted as /media/card :<br />
<br />
cat /path/LATEST_openwrt-s3c24xx-rootfs.tgz |ssh root@192.168.0.202 "gunzip -d | tar -C /media/card/ -xf -"<br />
<br />
== Installing to SD card via PC ==<br />
{{note|This part assume you use [[Qi]] as bootloader. [[U-Boot]] will not work using this setup }}<br />
For booting from SD card fetch this rootfs and the kernel image (same than above mentioned):<br />
wget http://nanl.de/files/openwrt/openmoko/LATEST_openwrt-s3c24xx-rootfs.tgz<br />
wget http://nanl.de/files/openwrt/openmoko/LATEST_openwrt-s3c24xx-2.6-uImage<br />
<br />
Following instructions assume that you are using a SD card reader on host PC.<br />
* Format SD card using ext2 or ext3.<br />
mkfs.ext2 /dev/sdf1<br />
* Mount this partion <br />
mount /dev/sdf1 /mnt/disk<br />
* Unpack rootfs archive to card.<br />
tar xvzf LATEST_openwrt-s3c24xx-rootfs.tgz -C /mnt/disk<br />
* Copy kernel to card /boot/uImage-GTA02.bin<br />
cp LATEST_openwrt-s3c24xx-2.6-uImage /mnt/disk/boot/uImage-GTA02.bin<br />
* Umount SD card partition<br />
umount /mnt/disk<br />
* Then boot from SD card with your FreeRunner.<br />
<br />
= Usage =<br />
After flashing both images, reboot your phone and depending on what packages were built into the image (if compiled yourself this means the packages you've selected) you might be able to initiate and receive phonecalls with your FreeRunner running OpenWrt :)<br />
<br />
'''First start'''<br />
<br />
You see nice OpenWrt bootsplash and message "split_squashfs: no squashfs found in neo1973-nand", but just wait minute or two and X will start. Enlightenment+illume starts. There are xterm installed and qwerty-button for [[on-screen-keyboard]].<br />
<br />
You can reach the Freerunner over wlan or [[USB_Networking|usb network]] as usual but Freerunner under OpenWrt have '''192.168.1.1 IP address''' as default.<br />
<br />
'''Enable wifi'''<br />
echo s3c2440-sdi > /sys/bus/platform/drivers/s3c2440-sdi/unbind<br />
echo s3c2440-sdi > /sys/bus/platform/drivers/s3c2440-sdi/bind<br />
<br />
ifconfig eth0 up<br />
iwconfig eth0 essid NAME<br />
udhcpc<br />
<br />
If your router has ip 192.168.1.1 (which is recommend in usb-networking), use this to stop usb0:<br />
ifconfig br-lan down<br />
Or you can change the address of usb0. Is it in file: ''/etc/config/network''<br />
<br />
'''Enable SSH'''<br />
<br />
To be able to SSH your phone, you must setup a password. You can use xterm and command 'passwd' or you can use telnet (if you connects over wlan, use proper ip-address):<br />
<br />
$ telnet 192.168.1.1<br />
Trying 192.168.1.1...<br />
Connected to 192.168.1.1.<br />
Escape character is '^]'.<br />
=== IMPORTANT ============================<br />
Use 'passwd' to set your login password<br />
this will disable telnet and enable SSH<br />
------------------------------------------<br />
.<br />
BusyBox v1.13.4 (2009-07-06 01:59:55 CEST) built-in shell (ash)<br />
Enter 'help' for a list of built-in commands.<br />
.<br />
_______ ________ __<br />
| |.-----.-----.-----.| | | |.----.| |_<br />
| - || _ | -__| || | | || _|| _|<br />
|_______|| __|_____|__|__||________||__| |____|<br />
|__| W I R E L E S S F R E E D O M<br />
KAMIKAZE (bleeding edge, r16703) -------------------<br />
* 10 oz Vodka Shake well with ice and strain<br />
* 10 oz Triple sec mixture into 10 shot glasses.<br />
* 10 oz lime juice Salute!<br />
---------------------------------------------------<br />
root@OpenWrt:/# passwd<br />
Changing password for root<br />
New password:<br />
Retype password:<br />
Password for root changed by root<br />
root@OpenWrt:/#<br />
<br />
== Installing packages ==<br />
It uses opkg and default repository is http://downloads.openwrt.org/snapshots/trunk/s3c24xx/packages/<br />
<br />
opkg update<br />
opkg install nano<br />
<br />
If the opkg install quits with error "* Packages were found, but none compatible with the architectures configured" then the following line should be checked in /etc/opkg.conf (error occured with nanl.de rootfs (22. September 09))<br />
<br />
arch s3c24xx 1<br />
<br />
Where ’s3c24xx’ is the architecture and ‘1′ is a ‘priority'.<br />
<br />
= Build custom image =<br />
== Fetching OpenWrt trunk ==<br />
First you have to create a svn checkout of the OpenWrt base system<br />
<br />
svn co svn://svn.openwrt.org/openwrt/trunk openwrt<br />
<br />
The command will fetch the OpenWrt base system and put it into the openwrt subfolder of your current working directory. From now on this HOWTO assumes that your working direcory will be the newly created openwrt folder. <br />
<br />
cd openwrt<br />
<br />
== Add packages from extra feeds ==<br />
Although this is sufficient enough to build an image for the freerunner you will not be able to build a lot of packages useful on your phone. Those packages are in extra feeds. To enable those feeds:<br />
<br />
cp feeds.conf.default feeds.conf<br />
<br />
Then edit your feeds.conf and enable the efl (for enlightenment) and phone (for fso, paroli, ...) feeds, by removing the '#' at the beginning of these lines, so that it might look like:<br />
<br />
src-svn packages svn://svn.openwrt.org/openwrt/packages<br />
src-svn xwrt http://x-wrt.googlecode.com/svn/trunk/package<br />
src-svn luci http://svn.luci.subsignal.org/luci/branches/luci-0.8/contrib/package<br />
src-svn phone svn://svn.openwrt.org/openwrt/feeds/phone<br />
src-svn efl svn://svn.openwrt.org/openwrt/feeds/efl<br />
src-svn desktop svn://svn.openwrt.org/openwrt/feeds/desktop<br />
#src-svn xfce svn://svn.openwrt.org/openwrt/feeds/xfce<br />
<br />
Please mind that this config does not define what packages will be compiled - it just defines which package-descriptions (OpenWrt-Makefiles) will be fetched which will be listed within the menuconfig later.<br />
<br />
After that update your feeds to download the OpenWrt-Makefiles of these packages and provide (install) them<br />
<br />
./scripts/feeds update -a<br />
./scripts/feeds install -a<br />
<br />
== Configure target and packages ==<br />
Now you'll have to select the target platform for the freerunner. Run<br />
<br />
make menuconfig<br />
<br />
and select s3c24xx as the Target System. As Target Profile you have to choice between <br />
* '''Openmoko GTA-02 (full)''': This is the one you probably want since it has enlightenment and paroli preselected.<br />
* '''Openmoko GTA-02 (minimal)''': This profile contains only the basic OpenWrt packages, so you'll only get a shell and some command-line utils.<br />
<br />
You now can also select additional packages you want to be installed in your image. Make sure you select as build in [*] else [M] you'll only get the packages but they will not be in the image, but can be installed later on.<br />
<br />
You maybe also want to change the IP address under which the freerunner will be reachable. To do so select "[*] Image configuration". In its submenu you can change the images network configuration.<br />
<br />
Per default OpenWrt is using the uclibc as libc implementation. You can use another libc (e.g. the glibc) by changing that via "[*] Advanced configuration options (for developers)" -> "--- Toolchain Options" -> "LIBC implementation".<br />
<br />
== Build your OpenWrt image ==<br />
If your done configuring the image you can build it by just running:<br />
<br />
make<br />
<br />
'''Attention''' - at least in OpenWRT rev 19632, it seems, you need to have sdcc installed in order to compile the image.<br />
'''Warning:''' OpenWrt build system have more or less requirements depends on selected packages. Using GTA-02 full profile, we need: <br />
* ''subversion'' and git to retrieve some external sources. (On Debian Lenny: ''subversion git-core'')<br />
* full ''autotools'' suite. (On Debian Lenny: ''automake autoconf autotools-dev libtool pkg-config'')<br />
* ''dbus-binding-tool'' to be able to compile "gsm0710muxd". (On Debian Lenny: ''libdbus-glib-1-dev'')<br />
* ''autopoint'' and ''cvs'' is used by enlightenment building process. (On Debian Lenny: ''gettext cvs'')<br />
* --- also needs "libxml-parser-perl"<br />
This will now take some time. Please make sure you have enough free space left (~4 GB for full-profile).<br />
Instead you can use "make V=99" to get debug output to see what's going on / went wrong.<br />
<br />
== Flash Neo FreeRunner ==<br />
When the build process is finished you will find a rootfs (openwrt-s3c24xx-2.6-root.jffs2-128k) and a kernel image (openwrt-s3c24xx-2.6-uImage) in the bin/ subfolder of your OpenWrt installation, which can be installed on your freerunner with the [[Dfu-util|dfu util]] as normal. Then you can continue as usage section says (beware if you have disable something).<br />
<br />
<br />
= Congratulations! =<br />
<br />
Please help us making this site better! Give feedback on the mailinglist (Openmoko as well as OpenWrt), change this site, file bug-reports or just tell us how much you love OpenWrt ;)<br />
<br />
'''State'''<br />
http://oldwiki.openwrt.org/Hardware%282f%29Openmoko.html<br />
<br />
= Alternative (untested?) OpenWrt distribution and pre-built boot image =<br />
* http://downloads.openwrt.org/snapshots/trunk/s3c24xx/<br />
<br />
[[Category:OpenWrt| ]]</div>Vanoushttp://openmoko.org/wiki/MokosuiteMokosuite2010-08-30T20:23:11Z<p>Vanous: /* Libmokosuite */</p>
<hr />
<div>{{Languages|Mokosuite}}<br />
<br />
<onlyinclude><br />
{{ApplicationBox|<br />
Name=[[Mokosuite]]|<br />
Description=Elementary based phone suite |<br />
Screenshot=MokoWM.png |<br />
Homepage=svn://svn.casaricci.it/openmoko/trunk|<br />
TestedOn=SHR |<br />
PackageName=mokosuite2<br />
}}<br />
</onlyinclude><br />
<br />
{{application|Mokosuite}}<br />
<br />
=Overview=<br />
<br />
The mokosuite phone suite package is made up several components. Outside the mokosuite tree there is mokowm-imf-ecore, an input method module for<br />
Ecore.<br />
<br />
{|align=center<br />
|__TOC__<br />
|}<br />
<br />
<br />
{|<br />
| [[Image:Mokohome.png|200px|thumb|Launcher]]<br />
| [[Image:Mokosettings.png|200px|thumb|Settings]]<br />
| [[Image:Mokokeyboard.png|200px|thumb|Keyboard]]<br />
| [[Image:Mokopanel.png|200px|thumb|Panel]]<br />
|}<br />
<br />
=Installation=<br />
<br />
Installation on SHR:<br />
<br />
opkg install mokosuite2<br />
<br />
=The phone application=<br />
<br />
The phone application is used to actually make phone calls. It manages also<br />
the actual connection to the GSM network.<br />
The phone app has an integrated call log and contacts list, for now stored in<br />
SQLite databases. My idea is to write my own implementation of opimd backed by<br />
mokophone.<br />
<br />
When a phone call starts or is incoming, the phone app sends notification<br />
through D-Bus to the panel, creating a green active call icon and filling the<br />
notification list with the current active call. If a call gets lost, another<br />
notification is pushed to the panel (with a red lost call icon :)<br />
<br />
<br />
=The messages application=<br />
<br />
There is actually a stub with some builtin messages, but my objective is to<br />
modify some of the opimd specs to accomplish a more threaded message management.<br />
This shall be discussed with mickeyl or anyone else is involved. We should find<br />
a way to make a custom SQL query, optimized for retrieving information about<br />
SMS threads, not wasting resources.<br />
<br />
I still have to decide to integrate e-mail support with sms... but I don't know,<br />
there are many points of view about this approach.<br />
<br />
<br />
=The settings application=<br />
<br />
<br />
<br />
This app is in charge to manage much all of the aspects of the suite and of the<br />
phone itself. For now it manages only a few things, but it's going to be a very<br />
big application :)<br />
<br />
<br />
=The mail application=<br />
<br />
Much TODO :)<br />
<br />
<br />
=The window manager=<br />
[[Image:Mokodesk2.png|thumb]]<br />
As of now, mokowm is a veeeery basic X window manager based on Ecore_X APIs,<br />
which have made things very easy. However, a phone window manager should do<br />
many things, and this will be a major part of the project.<br />
The wm right now has also a builtin simple virtual keyboard, not very complete<br />
yet, but working :)<br />
It is activable using signals: USR1 to show, USR2 to hide (the input method<br />
module actually sends a signal to the wm).<br />
<br />
<br />
=Home and desktop=<br />
[[Image:Mokohome.png|thumb]]<br />
This app is the home for the application launchers and the desktop, which can<br />
contain widgets (for now only launcher widgets :). At some point a public API<br />
will be made available for writing widgets. They should not be D-Bus, but more<br />
like module API.<br />
In the close future there is a major issue to be fixed: single instance<br />
launchers.<br />
<br />
<br />
=The panel application=<br />
<br />
The panel is responsible for the upper side panel window, showing push<br />
notifications to the user as needed. There is also a notification list window,<br />
activated by clicking the panel window itself at any point.<br />
Notifications are pushed using a simple dbus API, available in a dbus xml file<br />
in the source code repository.<br />
The panel has also a idle screen (or screensaver) that inhibits the touchscreen<br />
when is active, preventing any user action. Screensaver is hidden by pressing<br />
the POWER button. The panel manages also display dimming.<br />
<br />
<br />
=Libmokosuite=<br />
<br />
The library is used by every app but the window manager. It contains a lot of<br />
useful functions (primarly UI utilities) connected to notification management,<br />
windows and dialogs, many fso and misc utilities, etc.<br />
Actually my aim is to write a complete UI widget library (as extension to the<br />
Elementary toolkit) for improving UI consinstency and co-operation.<br />
The library includes a basic interface (not fully working actually) to the bluez<br />
API, using Eggdbus (I wish to make it the primary Dbus library of the suite).<br />
<br />
<br />
[[User:Daniele Ricci]]<br />
[[Category:Telephony]]<br />
[[Category:ApplicationsElementary]]</div>Vanoushttp://openmoko.org/wiki/MokosuiteMokosuite2010-08-30T20:21:52Z<p>Vanous: initial commit</p>
<hr />
<div>{{Languages|Mokosuite}}<br />
<br />
<onlyinclude><br />
{{ApplicationBox|<br />
Name=[[Mokosuite]]|<br />
Description=Elementary based phone suite |<br />
Screenshot=MokoWM.png |<br />
Homepage=svn://svn.casaricci.it/openmoko/trunk|<br />
TestedOn=SHR |<br />
PackageName=mokosuite2<br />
}}<br />
</onlyinclude><br />
<br />
{{application|Mokosuite}}<br />
<br />
=Overview=<br />
<br />
The mokosuite phone suite package is made up several components. Outside the mokosuite tree there is mokowm-imf-ecore, an input method module for<br />
Ecore.<br />
<br />
{|align=center<br />
|__TOC__<br />
|}<br />
<br />
<br />
{|<br />
| [[Image:Mokohome.png|200px|thumb|Launcher]]<br />
| [[Image:Mokosettings.png|200px|thumb|Settings]]<br />
| [[Image:Mokokeyboard.png|200px|thumb|Keyboard]]<br />
| [[Image:Mokopanel.png|200px|thumb|Panel]]<br />
|}<br />
<br />
=Installation=<br />
<br />
Installation on SHR:<br />
<br />
opkg install mokosuite2<br />
<br />
=The phone application=<br />
<br />
The phone application is used to actually make phone calls. It manages also<br />
the actual connection to the GSM network.<br />
The phone app has an integrated call log and contacts list, for now stored in<br />
SQLite databases. My idea is to write my own implementation of opimd backed by<br />
mokophone.<br />
<br />
When a phone call starts or is incoming, the phone app sends notification<br />
through D-Bus to the panel, creating a green active call icon and filling the<br />
notification list with the current active call. If a call gets lost, another<br />
notification is pushed to the panel (with a red lost call icon :)<br />
<br />
<br />
=The messages application=<br />
<br />
There is actually a stub with some builtin messages, but my objective is to<br />
modify some of the opimd specs to accomplish a more threaded message management.<br />
This shall be discussed with mickeyl or anyone else is involved. We should find<br />
a way to make a custom SQL query, optimized for retrieving information about<br />
SMS threads, not wasting resources.<br />
<br />
I still have to decide to integrate e-mail support with sms... but I don't know,<br />
there are many points of view about this approach.<br />
<br />
<br />
=The settings application=<br />
<br />
<br />
<br />
This app is in charge to manage much all of the aspects of the suite and of the<br />
phone itself. For now it manages only a few things, but it's going to be a very<br />
big application :)<br />
<br />
<br />
=The mail application=<br />
<br />
Much TODO :)<br />
<br />
<br />
=The window manager=<br />
[[Image:Mokodesk2.png|thumb]]<br />
As of now, mokowm is a veeeery basic X window manager based on Ecore_X APIs,<br />
which have made things very easy. However, a phone window manager should do<br />
many things, and this will be a major part of the project.<br />
The wm right now has also a builtin simple virtual keyboard, not very complete<br />
yet, but working :)<br />
It is activable using signals: USR1 to show, USR2 to hide (the input method<br />
module actually sends a signal to the wm).<br />
<br />
<br />
=Home and desktop=<br />
[[Image:Mokohome.png|thumb]]<br />
This app is the home for the application launchers and the desktop, which can<br />
contain widgets (for now only launcher widgets :). At some point a public API<br />
will be made available for writing widgets. They should not be D-Bus, but more<br />
like module API.<br />
In the close future there is a major issue to be fixed: single instance<br />
launchers.<br />
<br />
<br />
=The panel application=<br />
<br />
The panel is responsible for the upper side panel window, showing push<br />
notifications to the user as needed. There is also a notification list window,<br />
activated by clicking the panel window itself at any point.<br />
Notifications are pushed using a simple dbus API, available in a dbus xml file<br />
in the source code repository.<br />
The panel has also a idle screen (or screensaver) that inhibits the touchscreen<br />
when is active, preventing any user action. Screensaver is hidden by pressing<br />
the POWER button. The panel manages also display dimming.<br />
<br />
<br />
=Libmokosuite=<br />
<br />
The library is used by every app but the window manager. It contains a lot of<br />
useful functions (primarly UI utilities) connected to notification management,<br />
windows and dialogs, many fso and misc utilities, etc.<br />
Actually my aim is to write a complete UI widget library (as extension to the<br />
Elementary toolkit) for improving UI consinstency and co-operation.<br />
The library includes a basic interface (not fully working actually) to the bluez<br />
API, using Eggdbus (I wish to make it the primary Dbus library of the suite).<br />
<br />
<br />
[[User:Daniele Ricci]]<br />
[[Category:Phone Applications]]<br />
[[Category:ApplicationsElementary]]</div>Vanoushttp://openmoko.org/wiki/File:MokoWM.pngFile:MokoWM.png2010-08-30T20:11:01Z<p>Vanous: </p>
<hr />
<div></div>Vanoushttp://openmoko.org/wiki/File:Mokosettings2.pngFile:Mokosettings2.png2010-08-30T20:10:43Z<p>Vanous: </p>
<hr />
<div></div>Vanoushttp://openmoko.org/wiki/File:Mokosettings.pngFile:Mokosettings.png2010-08-30T20:10:32Z<p>Vanous: </p>
<hr />
<div></div>Vanoushttp://openmoko.org/wiki/File:Mokopanel_Illume2.pngFile:Mokopanel Illume2.png2010-08-30T20:10:21Z<p>Vanous: </p>
<hr />
<div></div>Vanoushttp://openmoko.org/wiki/File:Mokopanel.pngFile:Mokopanel.png2010-08-30T20:10:02Z<p>Vanous: </p>
<hr />
<div></div>Vanoushttp://openmoko.org/wiki/File:Mokokeyboard.pngFile:Mokokeyboard.png2010-08-30T20:09:27Z<p>Vanous: </p>
<hr />
<div></div>Vanoushttp://openmoko.org/wiki/File:Mokohome.pngFile:Mokohome.png2010-08-30T20:09:15Z<p>Vanous: </p>
<hr />
<div></div>Vanoushttp://openmoko.org/wiki/File:Mokodesk2.pngFile:Mokodesk2.png2010-08-30T20:08:54Z<p>Vanous: </p>
<hr />
<div></div>Vanoushttp://openmoko.org/wiki/Smedia_Glamo_3362Smedia Glamo 33622010-08-30T18:39:25Z<p>Vanous: /* Timing settings */</p>
<hr />
<div>== Summary ==<br />
Glamo3362 is the graphics chip in the [[Neo FreeRunner]]. It supports 2D and 3D acceleration, and provides an extra SD interface which is used for the uSD card slot (the other one is used for the [[Wlan]] adaptor).<br />
<br />
Glamo's 2D engine is currently used to accelerate solid fills and blits in both XGlamo (Kdrive) and X.org (xf86-video-glamo).<br />
<br />
The datasheets for the chip are not public, but have been made available (under NDA) to a few community volunteers who are interested in working on accelerated drivers. Please post to the [http://lists.openmoko.org/mailman/listinfo/devel devel mailing list] if you are interested in joining in this effort. [http://kerneltrap.org/mailarchive/openmoko-community/2008/11/13/4088744 This mailing list thread] has some discussion on the topic.<br />
<br />
== MicroSD support ==<br />
* Supports SDHC (Secure Digital High Capacity) cards up to 8GB<br />
* Connected to: Glamo 3362 MMC/SD controller<br />
* [[Supported microSD cards]]<br />
* Specifications: [http://www.sdcard.org/about/memory_card/pls/ SD Simplified Specification], [http://www.mmca.org/compliance/buy_spec/AN_MMCA050419.pdf MMC (partial)], [http://www.sandisk.com/Assets/File/OEM/Manuals/manual-rs-mmcv1.0.pdf MMC (product manual)]<br />
<br />
== Bus Interface ==<br />
* Glamo is connected to the [[Samsung S3C2442B B54]] address/data bus, accessed via MMIO.<br />
<br />
== Hardware Acceleration ==<br />
This is a compilation of all the publicly available information that is known about the Glamo 3362 used in the Neo FreeRunner GTA02 and links to past and present projects utilizing the Glamo's hardware acceleration. If anyone is working or has worked on hardware acceleration with the Glamo please add any links and any further information to this page.<br />
<br />
===Hardware Accelerated Projects===<br />
* [http://unadventure.wordpress.com/2008/06/08/accelerating-in-my-pocket Blog post] by balrog accounting his working creating an accelerated mplayer driver using the Glamo 3362<br />
** [http://repo.or.cz/w/mplayer/glamo.git?a=tree;f=drivers/libglamo;h=c268ca2a4a98517b6e218669b0a46d2dad737abb;hb=HEAD Source for libglamo] interface used for mplayer acceleration<br />
* Xglamo<br />
** [[Media:xglamo-graphics.pdf | xglamo-graphics.pdf]]<br />
** [http://git.openmoko.org/?p=xglamo.git;a=summary Xglamo source]<br />
* [http://www.bitwiz.org.uk/freerunner-dri Tom White's DRI project]<br />
* xf86-video-glamo (driver for X.org)<br />
** [http://git.openmoko.org/?p=xf86-video-glamo.git;a=summary Git repository]<br />
<br />
===Known Features===<br />
* 8MB internal SDRAM<br />
* 16bit local bus interface to S3C2410<br />
** The bus is limited in speed to about 7 Mb/s. This means that rendering is slow unless it can follow an accelerated path, and that texture uploads for 3D graphics would be slow.<br />
* 2D acceleration<br />
* 3D acceleration<br />
** 256x256 Max Texture Size<br />
** No Render-To-Texture Support<br />
** 511x511 Max 3D Destination Buffer Size<br />
*** Note that this is smaller than the VGA screen.<br />
** Pipeline: Transform, cull, lighting, clipping, setup, rasterizer<br />
** Standards compliance: OpenGL ES 1.0, OpenGL ES 1.1 and Mobile D3D.<br />
* [http://en.wikipedia.org/wiki/H.263 h.263] codec (encode/decode)<br />
* LCM controller<br />
* SD-Card controller<br />
* hardware JPEG encoder/decoder<br />
* Camera interface and imapge processing (unused)<br />
<br />
<br />
===Timing settings===<br />
<br />
The CPU (S3C2440) memory bank setting values can be adjusted in such a way that Glamo performance is increased. Bootloader usually takes care of this setup so to change these settings at startup, bootloader with different values can be flashed. Besides flashing bootloader, one can use other tools that can set the memory bank.<br />
<br />
In depth description and discussion can ge found [http://www.mail-archive.com/community@lists.openmoko.org/msg60256.html here].<br />
<br />
Qi with applied patch (binary only!):<br />
<br />
* [http://www.openmobile.nl/pages/downloads.php#qiglamo Openmobile.de website's page]<br />
* [http://www.openmobile.nl/modules/download_gallery/dlc.php?file=53 direct download link]<br />
<br />
Runtime tweaking can be done by direct writing via [http://www.bsdmn.com/openmoko/glamo/timings/ memwrite] or [http://git.debian.org/?p=pkg-fso/omhacks.git;a=blob;f=README omhacks]:<br />
<br />
To apply 2.4.2 timings:<br />
<br />
./memwrite $((0x48000008)) $((0x1380))<br />
<br />
or<br />
<br />
om screen glamo-bus-timings 2-4-2<br />
<br />
To see the timings that are currently in use:<br />
<br />
./memwrite $((0x48000008)) <br />
<br />
or<br />
<br />
om screen glamo-bus-timings<br />
<br />
[[Category:Used chip]]<br />
[[Category:Neo FreeRunner Hardware]]<br />
[[Category:Hardware ideas]]<br />
<br />
[[Category:Used chip]]<br />
[[Category:Neo FreeRunner Hardware]]<br />
[[Category:Hardware ideas]]</div>Vanoushttp://openmoko.org/wiki/Smedia_Glamo_3362Smedia Glamo 33622010-08-30T18:38:50Z<p>Vanous: /* Timing settings */ qi links</p>
<hr />
<div>== Summary ==<br />
Glamo3362 is the graphics chip in the [[Neo FreeRunner]]. It supports 2D and 3D acceleration, and provides an extra SD interface which is used for the uSD card slot (the other one is used for the [[Wlan]] adaptor).<br />
<br />
Glamo's 2D engine is currently used to accelerate solid fills and blits in both XGlamo (Kdrive) and X.org (xf86-video-glamo).<br />
<br />
The datasheets for the chip are not public, but have been made available (under NDA) to a few community volunteers who are interested in working on accelerated drivers. Please post to the [http://lists.openmoko.org/mailman/listinfo/devel devel mailing list] if you are interested in joining in this effort. [http://kerneltrap.org/mailarchive/openmoko-community/2008/11/13/4088744 This mailing list thread] has some discussion on the topic.<br />
<br />
== MicroSD support ==<br />
* Supports SDHC (Secure Digital High Capacity) cards up to 8GB<br />
* Connected to: Glamo 3362 MMC/SD controller<br />
* [[Supported microSD cards]]<br />
* Specifications: [http://www.sdcard.org/about/memory_card/pls/ SD Simplified Specification], [http://www.mmca.org/compliance/buy_spec/AN_MMCA050419.pdf MMC (partial)], [http://www.sandisk.com/Assets/File/OEM/Manuals/manual-rs-mmcv1.0.pdf MMC (product manual)]<br />
<br />
== Bus Interface ==<br />
* Glamo is connected to the [[Samsung S3C2442B B54]] address/data bus, accessed via MMIO.<br />
<br />
== Hardware Acceleration ==<br />
This is a compilation of all the publicly available information that is known about the Glamo 3362 used in the Neo FreeRunner GTA02 and links to past and present projects utilizing the Glamo's hardware acceleration. If anyone is working or has worked on hardware acceleration with the Glamo please add any links and any further information to this page.<br />
<br />
===Hardware Accelerated Projects===<br />
* [http://unadventure.wordpress.com/2008/06/08/accelerating-in-my-pocket Blog post] by balrog accounting his working creating an accelerated mplayer driver using the Glamo 3362<br />
** [http://repo.or.cz/w/mplayer/glamo.git?a=tree;f=drivers/libglamo;h=c268ca2a4a98517b6e218669b0a46d2dad737abb;hb=HEAD Source for libglamo] interface used for mplayer acceleration<br />
* Xglamo<br />
** [[Media:xglamo-graphics.pdf | xglamo-graphics.pdf]]<br />
** [http://git.openmoko.org/?p=xglamo.git;a=summary Xglamo source]<br />
* [http://www.bitwiz.org.uk/freerunner-dri Tom White's DRI project]<br />
* xf86-video-glamo (driver for X.org)<br />
** [http://git.openmoko.org/?p=xf86-video-glamo.git;a=summary Git repository]<br />
<br />
===Known Features===<br />
* 8MB internal SDRAM<br />
* 16bit local bus interface to S3C2410<br />
** The bus is limited in speed to about 7 Mb/s. This means that rendering is slow unless it can follow an accelerated path, and that texture uploads for 3D graphics would be slow.<br />
* 2D acceleration<br />
* 3D acceleration<br />
** 256x256 Max Texture Size<br />
** No Render-To-Texture Support<br />
** 511x511 Max 3D Destination Buffer Size<br />
*** Note that this is smaller than the VGA screen.<br />
** Pipeline: Transform, cull, lighting, clipping, setup, rasterizer<br />
** Standards compliance: OpenGL ES 1.0, OpenGL ES 1.1 and Mobile D3D.<br />
* [http://en.wikipedia.org/wiki/H.263 h.263] codec (encode/decode)<br />
* LCM controller<br />
* SD-Card controller<br />
* hardware JPEG encoder/decoder<br />
* Camera interface and imapge processing (unused)<br />
<br />
<br />
===Timing settings===<br />
<br />
The CPU (S3C2440) memory bank setting values can be adjusted in such a way that Glamo performance is increased. Bootloader usually takes care of this setup so to change these settings at startup, bootloader with different values can be flashed. Besides flashing bootloader, one can use other tools that can set the memory bank.<br />
<br />
In depth description and discussion can ge found [http://www.mail-archive.com/community@lists.openmoko.org/msg60256.html here].<br />
<br />
Qi with applied patch (binary only!):<br />
<br />
* [http://www.openmobile.nl/pages/downloads.php#qiglamo Openmobile.de website's page]<br />
* [http://www.openmobile.nl/modules/download_gallery/dlc.php?file=53 direct download link]<br />
<br />
Runtime tweaking can be done by direct writing via [http://www.bsdmn.com/openmoko/glamo/timings/ memwrite] or [http://git.debian.org/?p=pkg-fso/omhacks.git;a=blob;f=README omhacks]:<br />
<br />
To apply 2.4.2 timings:<br />
<br />
./memwrite $((0x48000008)) $((0x1380))<br />
<br />
or<br />
<br />
om screen glamo-bus-timings 2-4-2<br />
<br />
To see the timings that are currently in use:<br />
<br />
./memwrite $((0x48000008)) <br />
<br />
or<br />
<br />
om screen glamo-bus-timings<br />
<br />
[[Category:Used chip]]<br />
[[Category:Neo FreeRunner Hardware]]<br />
[[Category:Hardware ideas]]<br />
<br />
[[Category:Used chip]]<br />
[[Category:Neo FreeRunner Hardware]]<br />
[[Category:Hardware ideas]]</div>Vanoushttp://openmoko.org/wiki/Smedia_Glamo_3362Smedia Glamo 33622010-08-29T19:43:36Z<p>Vanous: /* Timing settings */</p>
<hr />
<div>== Summary ==<br />
Glamo3362 is the graphics chip in the [[Neo FreeRunner]]. It supports 2D and 3D acceleration, and provides an extra SD interface which is used for the uSD card slot (the other one is used for the [[Wlan]] adaptor).<br />
<br />
Glamo's 2D engine is currently used to accelerate solid fills and blits in both XGlamo (Kdrive) and X.org (xf86-video-glamo).<br />
<br />
The datasheets for the chip are not public, but have been made available (under NDA) to a few community volunteers who are interested in working on accelerated drivers. Please post to the [http://lists.openmoko.org/mailman/listinfo/devel devel mailing list] if you are interested in joining in this effort. [http://kerneltrap.org/mailarchive/openmoko-community/2008/11/13/4088744 This mailing list thread] has some discussion on the topic.<br />
<br />
== MicroSD support ==<br />
* Supports SDHC (Secure Digital High Capacity) cards up to 8GB<br />
* Connected to: Glamo 3362 MMC/SD controller<br />
* [[Supported microSD cards]]<br />
* Specifications: [http://www.sdcard.org/about/memory_card/pls/ SD Simplified Specification], [http://www.mmca.org/compliance/buy_spec/AN_MMCA050419.pdf MMC (partial)], [http://www.sandisk.com/Assets/File/OEM/Manuals/manual-rs-mmcv1.0.pdf MMC (product manual)]<br />
<br />
== Bus Interface ==<br />
* Glamo is connected to the [[Samsung S3C2442B B54]] address/data bus, accessed via MMIO.<br />
<br />
== Hardware Acceleration ==<br />
This is a compilation of all the publicly available information that is known about the Glamo 3362 used in the Neo FreeRunner GTA02 and links to past and present projects utilizing the Glamo's hardware acceleration. If anyone is working or has worked on hardware acceleration with the Glamo please add any links and any further information to this page.<br />
<br />
===Hardware Accelerated Projects===<br />
* [http://unadventure.wordpress.com/2008/06/08/accelerating-in-my-pocket Blog post] by balrog accounting his working creating an accelerated mplayer driver using the Glamo 3362<br />
** [http://repo.or.cz/w/mplayer/glamo.git?a=tree;f=drivers/libglamo;h=c268ca2a4a98517b6e218669b0a46d2dad737abb;hb=HEAD Source for libglamo] interface used for mplayer acceleration<br />
* Xglamo<br />
** [[Media:xglamo-graphics.pdf | xglamo-graphics.pdf]]<br />
** [http://git.openmoko.org/?p=xglamo.git;a=summary Xglamo source]<br />
* [http://www.bitwiz.org.uk/freerunner-dri Tom White's DRI project]<br />
* xf86-video-glamo (driver for X.org)<br />
** [http://git.openmoko.org/?p=xf86-video-glamo.git;a=summary Git repository]<br />
<br />
===Known Features===<br />
* 8MB internal SDRAM<br />
* 16bit local bus interface to S3C2410<br />
** The bus is limited in speed to about 7 Mb/s. This means that rendering is slow unless it can follow an accelerated path, and that texture uploads for 3D graphics would be slow.<br />
* 2D acceleration<br />
* 3D acceleration<br />
** 256x256 Max Texture Size<br />
** No Render-To-Texture Support<br />
** 511x511 Max 3D Destination Buffer Size<br />
*** Note that this is smaller than the VGA screen.<br />
** Pipeline: Transform, cull, lighting, clipping, setup, rasterizer<br />
** Standards compliance: OpenGL ES 1.0, OpenGL ES 1.1 and Mobile D3D.<br />
* [http://en.wikipedia.org/wiki/H.263 h.263] codec (encode/decode)<br />
* LCM controller<br />
* SD-Card controller<br />
* hardware JPEG encoder/decoder<br />
* Camera interface and imapge processing (unused)<br />
<br />
<br />
===Timing settings===<br />
<br />
The CPU (S3C2440) memory bank setting values can be adjusted in such a way that Glamo performance is increased. Bootloader usually takes care of this setup so to change these settings at startup, bootloader with different values can be flashed. Besides flashing bootloader, one can use other tools that can set the memory bank.<br />
<br />
In depth description and discussion can ge found [http://www.mail-archive.com/community@lists.openmoko.org/msg60256.html here].<br />
<br />
Runtime tweaking can be done by direct writing via [http://www.bsdmn.com/openmoko/glamo/timings/ memwrite] or [http://git.debian.org/?p=pkg-fso/omhacks.git;a=blob;f=README omhacks]:<br />
<br />
To apply 2.4.2 timings:<br />
<br />
./memwrite $((0x48000008)) $((0x1380))<br />
<br />
<br />
[[Category:Used chip]]<br />
[[Category:Neo FreeRunner Hardware]]<br />
[[Category:Hardware ideas]]<br />
<br />
[[Category:Used chip]]<br />
[[Category:Neo FreeRunner Hardware]]<br />
[[Category:Hardware ideas]]</div>Vanous