http://wiki.openmoko.org/api.php?action=feedcontributions&user=Wurp&feedformat=atom 2013-05-19T18:23:01Z User contributions MediaWiki 1.19.6 http://wiki.openmoko.org/wiki/Manually_using_Bluetooth 2009-04-24T18:38:34Z

<p>Wurp: add references for bluez4</p> <hr /> <div>{{InProgress}}<br /> Bluetooth is one of the core functions of the Neo1973, however it is basically unimplemented on the software side at the moment.<br /> Hardware problems in the P1 phone mean that the CPU has to be active in order to wake on external bluetooth events, which will reduce the battery life to some 2 days at best in standby.<br /> <br /> This page details how to use bluetooth from the command line.<br /> We have quite a lot of plans about what exactly Bluetooth should be used for.<br /> <br /> == Power it up ==<br /> <br /> Power up the adapter by clicking on the bluetooth icon in the top bar and selecting power on.<br /> <br /> The old way to do it is a shell command (for kernels before 2.6.24):<br /> <br /> root@fic-gta01:~# echo 1 &gt; /sys/bus/platform/devices/gta01-pm-bt.0/power_on<br /> <br /> For kernel 2.6.24 (or later) use<br /> <br /> root@om-gta02:~# echo 1 &gt; /sys/bus/platform/devices/neo1973-pm-bt.0/power_on<br /> <br /> and on the GTA02 *only* (i.e. not on the GTA01) also use<br /> <br /> root@om-gta02:~# echo 0 &gt; /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br /> <br /> But nowadays[http://permalink.gmane.org/gmane.comp.hardware.smartphones.userland/165], one should use [[Dbus device API]]s!<br /> <br /> At the shell, &quot;hciconfig&quot; should print information about the adapter if it powered up properly:<br /> <br /> hciconfig<br /> <br /> The devices should show as UP. If not you can use<br /> <br /> hciconfig &lt;device&gt; up<br /> <br /> == Bluetooth Functions ==<br /> <br /> ===Configuring Bluetooth on Openmoko 2007.2 (August 27 snapshot with kernel 2.6.21.6-moko11) ===<br /> <br /> In file /etc/bluetooth/hcid.conf you should change the passkey from BlueZ to something numeric. For testing you may use &quot;0000&quot;. Also, you can set the name to &quot;Neo (%d)&quot;.<br /> <br /> === Scanning for bluetooth devices ===<br /> <br /> hcitool scan<br /> <br /> This will list the addresses of any discoverable bluetooth devices in the vicinity<br /> <br /> === passkey agent example ===<br /> <br /> There should be a passkey agent built into openmoko, but for now you can start up the example passkey agent and set the pin code there. This will allow for new pairings to be made when you attempt a connection.<br /> <br /> passkey-agent --default 0000 &amp;<br /> <br /> Note: the passkey-agent is not required in Openmoko 2007.2 with kernel 2.6.21.6 as of at least since August 27 (maybe earlier).<br /> <br /> In debian there is no passkey-agent binary but the package bluez-utils has its source code at /usr/share/doc/bluez-utils/examples/passkey-agent.c.gz.<br /> <br /> === HID (Human Input Device) ===<br /> <br /> ==== Being able to use HID devices ====<br /> <br /> If you are trying to connect a keyboard and you have bluez4, see [[Freedom_Slim_Keyboard]].<br /> <br /> Using a bluetooth keyboard with the built-in terminal is a little funky... I can only type into the console using the bt keyboard if the onscreen keyboard is visible. Also, pressing &quot;p&quot; twice on the bt keyboard actually gives you a &quot;q&quot;.<br /> <br /> We want to be able to use a bluetooth keyboard to type into the various applications of our Neo1973.<br /> To use a Bluetooth Keyboard type: (11:22:33:44:55:66 is the Address of your BT-Keyboard)<br /> <br /> hidd --connect 11:22:33:44:55:66<br /> <br /> and press &quot;Connect&quot; on your BT-KB. Alternately, if you know that only one BT-Keyboard is within range, you can just:<br /> <br /> hidd --search<br /> <br /> to find and connect to any BT-Keyboard. There are some bluetooth keyboard only support SPP profile can't direct using hidd comannd to connect. Please reference the discussion of this page for more information.<br /> <br /> Tested on:<br /> * [http://www.logitech.com/index.cfm/keyboards/keyboard/devices/3848&amp;cl=us,en Logitech diNovo Mini] Works well, very portable and the touchpad also works just fine. Also has no problems with double letters.<br /> * [http://www.logitech.com/index.cfm/products/details/US/EN,CRID=2166,CONTENTID=10717 Logitech Dinovo Edge]<br /> * [http://www.logitech.com/index.cfm/keyboards/keyboard_mice_combos/devices/164&amp;cl=us,en Logitech Dinovo Media Desktop (keyboard)]<br /> * [http://www.nokia.es/A4181580 Nokia SU-8W]. Switched on the BT keyboard, scanned for BT address and ran the connect statement above. Works fine.<br /> * [http://blog.russnelson.com/chordite Chordite]. This keyboard uses the Broadcom BCM2042 BT keyboard controller along with a custom driver.<br /> * [http://www.apple.com/keyboard/ Apple's Aluminum Keyboard]. You may have to add 'auth enable; encrypt enable;' to device {} in hcid.conf. Run the passkey agent the first time. --search works to pair and every time after. (Might be obvious for those who have used BT in other spots, but you have to type in y our passkey on the keyboard as the connect is happening, otherwise pairing doesn't take place. I don't think there is a prompt on the Neo for this)<br /> * [http://www.apple.com/support/keyboard/ Apple's white &quot;Wireless Keyboard (original)&quot;] - details may be the same as above. (tested some time ago)<br /> * [http://www.frogpad.com/ FrogPad] - as above<br /> * [http://freedominput.com The freedom keyboard] and its many rebranded models (they look like this: [http://rabenfrost.net/openmoko/keyboard.jpg]) need 'modprobe uinput' to circumvent the 'Can't open input device: No such file or directory (2)' error of 'hidd --search'. It works as of february 7th 2008.<br /> ** Freeedom Universal Keyboard Model G912 does not work (see Discussion Page)<br /> * [http://www.nextag.com/Playstation-3-Logitech-Cordless-564345667/prices-html?nxtg=f8320a24052a-7789F8FE732FF6E3 Logitech Playstation 3 Keyboard] Works well, Mouse pad works.<br /> * [http://corporate.igo.com/product_details.aspx?id=16 iGo Stowaway UltraSlim] (which was apparently discontinued early 2008, but can still be bought in some places) ([[user:ChristW]] I have 2008.8 on it, and using hidd --search to connect to the iGo works perfectly. I also used it to edit a new contact, dial a number and edit a settings text box in [[TangoGPS]]. So far, no problems...)<br /> * [http://www.vkb-support.com/ I-Tech Virtual Laser Keyboard] works. Cursor keys not recognized as such, but produce keycodes than can be mapped.<br /> <br /> This is a script that I've ([[User:ChristW]]) been using with varying results. YMMV:<br /> &lt;pre&gt;<br /> echo Power on<br /> echo 1 &gt; /sys/bus/platform/devices/neo1973-pm-bt.0/power_on<br /> sleep 1<br /> echo Reset on<br /> echo 1 &gt; /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br /> sleep 1<br /> echo Reset off<br /> echo 0 &gt; /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br /> sleep 1<br /> echo hciconfig down<br /> hciconfig hci0 down<br /> sleep 1<br /> echo hciconfig up<br /> hciconfig hci0 up<br /> sleep 1<br /> echo Connect<br /> hidd --connect XX:XX:XX:XX:XX:XX<br /> &lt;/pre&gt;<br /> <br /> (See also [[Freedom_Slim_Keyboard]] for fso scripts which work with bluez4.)<br /> <br /> ==== Acting as HID device ====<br /> <br /> We want to be able to use the Neo as a HID device, being able to use it as controller for presentations. See [[ReMoko]]<br /> <br /> === RFCOMM ===<br /> <br /> Here's how to connect to an external Bluetooth GPS and read NMEA data (Tested with a Holux GPSSlim236 and a Nokia LD-3W ).<br /> <br /> First, switch on the GPS and identify the BT address:<br /> <br /> hcitool scan<br /> <br /> Then, edit /etc/bluetooth/rfcomm.conf, which by default has all settings commented out, to something like this:<br /> <br /> rfcomm0 {<br /> # Automatically bind the device at startup<br /> bind no;<br /> # Bluetooth address of the device<br /> device 00:11:22:33:44:55;<br /> # RFCOMM channel for the connection (check your GPS docs for details)<br /> channel 1;<br /> # Description of the connection<br /> comment &quot;Bluetooth GPS&quot;;<br /> }<br /> <br /> Restart the BT services:<br /> <br /> root@neo:~$ /etc/init.d/bluetooth stop<br /> root@neo:~$ /etc/init.d/bluetooth start<br /> <br /> You should now be able to bind the GPS to /dev/rfcomm0, like this:<br /> <br /> root@neo:~$ rfcomm bind 0<br /> <br /> Confirm the connect:<br /> <br /> root@neo:~$ rfcomm<br /> rfcomm0: 00:11:22:33:44:55 channel 1 clean <br /> <br /> ... and watch the NMEA strings coming from your GPS:<br /> <br /> root@neo:~$ cat /dev/rfcomm0 <br /> $GPGGA,111748.000,5907.6964,N,01121.1787,E,1,06,1.2,57.7,M,40.1,M,,0000*6F<br /> $GPRMC,111748.000,A,5907.6964,N,01121.1787,E,0.00,94.94,160807,,,A*50<br /> $GPVTG,94.94,T,,M,0.00,N,0.0,K,A*3D<br /> <br /> If you have nothing better to do, you can now pinpoint my office :-).<br /> <br /> === OBEX ===<br /> OBEX (abbreviation of OBject EXchange, also termed IrOBEX) is a communications protocol that facilitates the exchange of binary objects between devices. Here is the notes about how to use OBEX to send/receive files via bluetooth in NEO.<br /> <br /> power on bluetooth: <br /> if you use FSO image<br /> root@om-gta02:~# dbus-send --system --dest=org.freesmartphone.odeviced --type=method_call --print-reply <br /> /org/freesmartphone/Device/PowerControl/Bluetooth org.freesmartphone.Device.PowerControl.SetPower int32:1<br /> else: (GTA02 only)<br /> root@om-gta02:~# echo 1 &gt; /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br /> root@om-gta02:~# echo 0 &gt; /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br /> <br /> [http://linux.die.net/man/5/hcid.conf hcid.conf] <br /> modify /etc/bluetooth/hcid.conf<br /> <br /> &lt;pre&gt;<br /> #<br /> # HCI daemon configuration file.<br /> #<br /> <br /> # HCId options<br /> options {<br /> # Automatically initialize new devices<br /> autoinit yes;<br /> <br /> # Security Manager mode<br /> # none - Security manager disabled<br /> # auto - Use local PIN for incoming connections<br /> # user - Always ask user for a PIN<br /> #<br /> security auto;<br /> <br /> # Pairing mode<br /> # none - Pairing disabled<br /> # multi - Allow pairing with already paired devices<br /> # once - Pair once and deny successive attempts<br /> pairing multi;<br /> <br /> # Default PIN code for incoming connections<br /> passkey &quot;1234&quot;;<br /> }<br /> <br /> # Default settings for HCI devices<br /> device {<br /> # Local device name<br /> # %d - device id<br /> # %h - host name<br /> name &quot;%h-%d&quot;;<br /> <br /> # Local device class<br /> class 0x000100;<br /> <br /> # Default packet type<br /> pkt_type DH1,DM1,HV1;<br /> <br /> # Inquiry and Page scan<br /> iscan enable; pscan enable;<br /> <br /> # Default link mode<br /> # none - no specific policy <br /> # accept - always accept incoming connections<br /> # master - become master on incoming connections,<br /> # deny role switch on outgoing connections<br /> lm accept;<br /> <br /> # Default link policy<br /> # none - no specific policy<br /> # rswitch - allow role switch<br /> # hold - allow hold mode<br /> # sniff - allow sniff mode<br /> # park - allow park mode<br /> lp rswitch,hold,sniff,park;<br /> }<br /> &lt;/pre&gt;<br /> <br /> [http://linux.die.net/man/8/hcid hcid] - Bluetooth Host Controller Interface Daemon <br /> <br /> All paired devices information are stored in /var/lib/bluetooth/BT HW addr folder <br /> eg. <br /> &lt;pre&gt;<br /> root@om-gta02:/var/lib/bluetooth/00:06:6E:16:EB:C7# ls<br /> classes features lastused names panu<br /> config gn manufacturers nap<br /> &lt;/pre&gt;<br /> <br /> Display local devices<br /> root@om-gta02:/# hcitool dev<br /> <br /> Scan all nearby bluetooth devices<br /> root@om-gta02:~# hcitool scan<br /> <br /> Browse what kind of services in this device<br /> root@om-gta02:~# sdptool browse 00:18:C5:42:18:78<br /> <br /> &lt;pre&gt;<br /> Browsing 00:18:C5:42:18:78 ...<br /> <br /> Service Name: OBEX File Transfer<br /> Service RecHandle: 0x1005b<br /> Service Class ID List:<br /> &quot;OBEX File Transfer&quot; (0x1106)<br /> Protocol Descriptor List:<br /> &quot;L2CAP&quot; (0x0100)<br /> &quot;RFCOMM&quot; (0x0003)<br /> Channel: 11<br /> &quot;OBEX&quot; (0x0008)<br /> Language Base Attr List:<br /> code_ISO639: 0x454e<br /> encoding: 0x6a<br /> base_offset: 0x100<br /> Profile Descriptor List:<br /> &quot;OBEX File Transfer&quot; (0x1106)<br /> Version: 0x0100<br /> <br /> Service Name: OBEX Object Push<br /> Service RecHandle: 0x1005e<br /> Service Class ID List:<br /> &quot;OBEX Object Push&quot; (0x1105)<br /> Protocol Descriptor List:<br /> &quot;L2CAP&quot; (0x0100)<br /> &quot;RFCOMM&quot; (0x0003)<br /> Channel: 9<br /> &quot;OBEX&quot; (0x0008)<br /> Language Base Attr List:<br /> code_ISO639: 0x454e<br /> encoding: 0x6a<br /> base_offset: 0x100<br /> Profile Descriptor List:<br /> &quot;OBEX Object Push&quot; (0x1105)<br /> Version: 0x0100<br /> <br /> &lt;/pre&gt;<br /> <br /> Use obexpush and obexftp tools<br /> <br /> install obexpush, obexftp packages<br /> opkg install obexpush [http://www.go2linux.org/linux-command-line-obexftp-man-page obexftp]<br /> <br /> obexpush would launch 'opd' and it's a obex data server. It starts OBEX file transfer service. The default folder is \home\root and it would store all received files here. <br /> <br /> &lt;pre&gt;<br /> root@om-gta02:~# ps aux | grep opd<br /> root 1322 0.0 0.4 1972 604 ? Ss 16:21 0:00 opd: waiting for incomming OBEX connections on channel 10...<br /> &lt;/pre&gt; <br /> <br /> How to pair with a bluetooth device, check [http://wiki.bluez.org/wiki/Security bluez wiki]<br /> <br /> === Networking ===<br /> <br /> ==== Using PC's connection from Neo ====<br /> <br /> ===== Bluetooth networking with a Linux system =====<br /> <br /> Bluetooth should behave just like our usbnet and provide full TCP/IP access to the phone. BNEP has to be used.<br /> <br /> '''On the laptop'''<br /> <br /> * Start bluetooth<br /> /etc/init.d/bluetooth start<br /> <br /> * Start pand as server<br /> pand -s<br /> <br /> * As soon as pand is started on the phone configure your IP address<br /> ip a add 10.0.0.1/24 dev bnep0<br /> ip l set bnep0 up<br /> <br /> * Configure IP forwarding and masquerading to your liking (see [[USB_Networking]]). You can even set up Udev rules to do this for you once the bnep0 interface appears.<br /> <br /> <br /> '''On the Neo'''<br /> <br /> * There is a little script that does the steps below (and retries the pand -c command; I had issues with it not working the first time every time) at [[Bt-net-script]] You shouldn't need the other steps below if you use the script.<br /> <br /> * Power on bluetooth (see above)<br /> <br /> * Scan for the laptop<br /> root@fic-gta01:~$ hcitool scan<br /> Scanning ...<br /> 00:0E:6D:C0:0l:6A Sho<br /> 00:20:E0:5A:FE:C8 BlueZ (0)<br /> <br /> * Connect to the laptop pand<br /> root@fic-gta01:~$ pand -c 00:20:E0:5A:FE:C8<br /> <br /> * Configure your IP address<br /> ip a add 10.0.0.2/24 dev bnep0<br /> ip r add default via 10.0.0.1<br /> <br /> * Sometimes you may need to bring up the bnep0 on the phone as well:<br /> ip l set bnep0 up<br /> * Enjoy<br /> <br /> <br /> *--[[User:Mantis|Mantis]] 18:37, 15 October 2008 (UTC) Note for use on OpenSuse 11.0 - I was getting a connection failure with 'Host is down(112)' errors in /var/log/messages (on neo).<br /> I found that editing /etc/bluetooth/hcid.conf to set 'pscan enable' instead of 'pscan disable' and making passkey consistent with Neo Freerunner made it work.<br /> <br /> Should see log line like<br /> ''pand[17965]: New connection from 00:06:6E:XX:XX:XX at bnep0''<br /> <br /> if connection is successful in server's /var/log/messages.<br /> <br /> ===== Bluetooth networking with a MacOS X system =====<br /> <br /> Please refer to [[MacOS_X#Bluetooth_2]]<br /> <br /> For using the Neo as a dialup Bluetooth server and the Mac as the client, please see below at [[Manually_using_Bluetooth#PPP_Networking]]<br /> <br /> ===== Bluetooth networking with a Windows XP system =====<br /> <br /> This was tested with a Windows XP SP2 on a IBM Thinkpad T41 with the Widcomm BT stack<br /> <br /> * Start bluetooth on Windows XP<br /> <br /> * Enable &quot;Network Access&quot; in the Bluetooth configuration<br /> <br /> * Scan for the Neo and pair with the Neo (right click, select pair)<br /> <br /> <br /> On the Neo<br /> <br /> * Enable PAN support on the Neo by changing Autostart from false to true in /etc/bluetooth/network.service<br /> <br /> * Power on bluetooth (see above)<br /> <br /> * Scan for the laptop<br /> root@fic-gta01:~$ hcitool scan<br /> Scanning ...<br /> &lt;laptop_bt_address&gt; Thinkpad<br /> ...<br /> <br /> <br /> * Connect to the laptop pand<br /> pand -c &lt;laptop_bt_address&gt; -r PANU -d NAP -e bnep0 -A -E -S<br /> (add '-n' to see the pand status messages until you get it right)<br /> <br /> For some reason, I was not able to initiate PAN connections from the Neo, I got 'Permission denied (13)' even when I had explicitly allowed the Neo to connect (right click on Neo icon, set properties, on Authorization tab). But initiating 'PAN User' from Windows worked when executing on Neo:<br /> pand -l -r PANU -d NAP -e bnep0 -A -E -S<br /> (add '-n' to see the pand status messages until you get it right)<br /> <br /> <br /> * Configure your IP address. It should work like when connecting to Linux:<br /> ip a add 10.0.0.2/24 dev bnep0<br /> ip r add default via 10.0.0.1<br /> If this does not work, the IP stacks may have auto-assigned network addresses to themselves. You can look this up with 'ifconfig' on the Neo and with 'ipconfig' on Windows.<br /> <br /> <br /> * You should now be able to ssh/putty from Windows to your Neo. Enjoy!<br /> By setting up the Windows Bluetooth connection properly, it should also be possible to share the Internet Connection of the Windows box with the Neo.<br /> <br /> ===== PPP Networking =====<br /> <br /> If you are unable to use the 'BNEP' method described above, you may be able to use [[PPP]] and a DUN (dialup-networking) emulation mode. On the Neo:<br /> <br /> * Edit the /etc/default/bluetooth file and set the following options:<br /> RFCOMM_ENABLE=true<br /> DUND_ENABLE=true<br /> DUND_OPTIONS=&quot;--listen --persist call dun&quot;<br /> <br /> * Create an /etc/ppp/peers/dun file with options like the following:<br /> 115200<br /> 192.168.2.202:192.168.2.200<br /> passive<br /> local<br /> noipdefault<br /> noauth<br /> nodefaultroute<br /> <br /> * Restart bluetooth (/etc/init.d/bluetooth stop ; /etc/init.d/bluetooth start)<br /> <br /> To connect from a MacOS 10.3 client:<br /> <br /> * Open &quot;Applications/Utilities/Bluetooth Serial Utility&quot;<br /> <br /> * Click on &quot;New&quot;<br /> <br /> * Choose a name, then click &quot;Choose Device&quot;<br /> <br /> * Locate your Neo, then select the &quot;LAN Access Point&quot; service. If your device is not found, or if this service does not show up, then you will need to troubleshoot and fix that before continuing. Bluetooth is designed for short-range communication, so make sure that the devices are physically close to each other. <br /> <br /> * Select &quot;Port type: RS-232&quot; and &quot;Show in Network Preferences&quot;. Click OK.<br /> <br /> * Open the Network Preferences page then &quot;Show: Network Port Configurations&quot;. Enable the new device that you defined in the previous step and drag it to the bottom of the device list (so that it will not interfere with your other network connections)<br /> <br /> * Choose &quot;Show: &lt;your-device-name&gt;&quot;, then click &quot;Modem&quot;<br /> <br /> * Select &quot;Null Modem 115200&quot; from the list of available devices. Uncheck &quot;Wait for dial tone&quot; and &quot;Enable error correction and compression in modem&quot;. Optionally check &quot;Show modem status in menu bar&quot;. <br /> <br /> * Click &quot;Connect&quot;. If everything worked, you will end up with a 'ppp0' device on your Mac with a local address of 192.168.2.200 and you will be able to access your Neo at 192.168.2.202.<br /> <br /> ===== Bluetooth networking with a Linux system - More secure way =====<br /> <br /> ''Check this, probably needs some corrections''<br /> <br /> Bluetooth should behave just like our usbnet and provide full TCP/IP access to the phone. BNEP has to be used.<br /> <br /> On the laptop<br /> <br /> * check these options in /etc/bluetooth/hcid.conf<br /> security auto;<br /> passkey &quot;your pin&quot;;<br /> lm master;<br /> <br /> * Start bluetooth<br /> # /etc/init.d/bluetooth start<br /> <br /> * Start pand as server<br /> pand --listen --role NAP --encrypt<br /> <br /> * Add in /etc/network/interfaces (see [[USB_Networking]])<br /> auto bnep0<br /> iface bnep0 inet static<br /> address 192.168.1.1<br /> netmask 255.255.255.0<br /> network 192.168.1.0<br /> post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.1.0/24<br /> post-up echo 1 &gt; /proc/sys/net/ipv4/ip_forward<br /> post-up iptables -P FORWARD ACCEPT<br /> <br /> On the Neo<br /> <br /> * Power on bluetooth (see above)<br /> <br /> * Scan for the laptop<br /> root@fic-gta01:~$ hcitool scan<br /> Scanning ...<br /> 00:20:E0:5A:FE:C8 laptop<br /> <br /> * Set pin<br /> root@fic-gta01:~$ passkey-agent 'your pin' 00:20:E0:5A:FE:C8 &amp;<br /> <br /> * Connect to the laptop pand<br /> root@fic-gta01:~$ pand -c 00:20:E0:5A:FE:C8<br /> <br /> * Configure your IP address<br /> root@fic-gta01:~$ ifconfig bnep0 192.168.1.2<br /> root@fic-gta01:~$ route add default gateway 192.168.1.1<br /> <br /> * Enjoy<br /> <br /> ==== Using Neo's connection from PC ====<br /> <br /> ===== Calling Neo's GPRS modem via Bluetooth =====<br /> <br /> In this mode, Neo would behave like any other phone which can be used from a PC to get a network connection.<br /> <br /> This section not written yet. Has someone set it up?<br /> <br /> ===== Sharing existing Neo's connection =====<br /> <br /> In this mode, Neo already has a network connection (GPRS, WLAN, ...), and it should get shared to the PC. This guide is general on how to forward network connection from a machine running Linux to another machine. If interested, please see more information for example at http://www.gentoo.org/doc/en/bluetooth-guide.xml.<br /> <br /> On the PC<br /> # Check with hciconfig you have working Bluetooth<br /> On the Neo<br /> (if on Debian etc., remember modprobe ohci_hcd hci_usb)<br /> # Initialize Bluetooth as told before:<br /> ## echo 1 &gt; /sys/bus/platform/devices/neo1973-pm-bt.0/power_on<br /> ## echo 0 &gt; /sys/bus/platform/devices/neo1973-pm-bt.0/reset<br /> # install iptables: opkg install http://www.angstrom-distribution.org/feeds/2008/ipk/glibc/armv4t/base/iptables_1.3.8-r4.1_armv4t.ipk<br /> # modprobe bnep<br /> # Check that hcid is running both on Neo and PC (Bluetooth 4.x: install bluez-compat)<br /> # Use default passkey &quot;1234&quot; in /etc/bluetooth/hcid.conf<br /> # pand --listen --role NAP --master --autozap # note: after this you might have to the the step 1 below (&quot;On the PC&quot;) or the next step of getting the interface up does not work # note2: you could automate pand listener to start automatically when Bluetooth is turned on<br /> # ifconfig bnep0 10.0.5.2 up<br /> # echo 1 &gt; /proc/sys/net/ipv4/ip_forward<br /> # iptables -t nat -A POSTROUTING -j MASQUERADE -o ppp0<br /> On the PC:<br /> # sudo pand --connect &lt;your bluetooth mac address&gt; --service NAP --autozap<br /> # ifconfig bnep0 10.0.5.1 up<br /> # You can test the connection with ping 10.0.5.2<br /> # sudo ip route add default via 10.0.5.2 dev bnep0<br /> # [not automated yet] add GPRS connection's nameservers to /etc/resolv.conf<br /> <br /> == Advanced Audio Distribution Profile (A2DP) ==<br /> <br /> See [[A2DP]].<br /> <br /> == Headset Audio ==<br /> <br /> [[Neo1973_Audio_Subsystem]] has detail about alsa settings and a proposal for audio scenario management.<br /> <br /> To try this out, follow the instructions on the [[A2DP]] page to install software and run the passkey agent.<br /> <br /> Remove or disable the stuff you put in asound.conf. When using a voice headset, the application uses the regular system audio device and it gets routed to bluetooth in the codec.<br /> <br /> Put the headset in pairing mode. Replace the bluetooth address below with your headset's and run the python script:<br /> <br /> #!/usr/bin/python<br /> import dbus<br /> bus = dbus.SystemBus()<br /> manager = dbus.Interface(bus.get_object('org.bluez', '/org/bluez'), 'org.bluez.Manager')<br /> conn = manager.ActivateService('audio')<br /> audio = dbus.Interface(bus.get_object(conn, '/org/bluez/audio'), 'org.bluez.audio.Manager')<br /> path = audio.CreateHeadset('00:0B:2E:39:33:22')<br /> audio.ChangeDefaultHeadset(path)<br /> headset = dbus.Interface (bus.get_object(conn, path), 'org.bluez.audio.Headset')<br /> headset.Connect()<br /> headset.Play()<br /> <br /> Now place a call and try to route it to bluetooth (after it's in progress):<br /> <br /> alsactl -f /etc/gsmbluetooth.state restore<br /> <br /> You may also be able to listen to system audio given the right state file:<br /> <br /> alsactl -f /etc/systembluetooth.state restore<br /> madplay song.mp3<br /> <br /> ==Bluetooth Headset on Freerunner ==<br /> <br /> [http://lists.openmoko.org/pipermail/support/2008-September/thread.html#2627 This thread] suggests the following:<br /> <br /> :Turn on bluetooth. If some of the scripts below fail you may need to reboot [https://docs.openmoko.org/trac/ticket/1744 Bluetooth after suspend]<br /> <br /> :Pair your headset according to [http://wiki.bluez.org/ these] instructions or use the script below. The script will change your .asoundrc so make a backup before you run it.<br /> <br /> :http://handheldshell.com/BtConfigure.py<br /> :Put the headset in pairing mode ( this only needs to be done once for each new headset ) and run<br /> BtConfigure.py <br /> <br /> :Download the the following python scripts to set up the audio service and set the headset as the default device:<br /> <br /> :http://handheldshell.com/BtHeadset.py<br /> :http://handheldshell.com/passkey.py<br /> :http://handheldshell.com/BtHeadsetDisconnect.py<br /> :http://handheldshell.com/python-pyalsaaudio_0.3-ml0_armv4t.ipk - can someone add python-pyalsa to the feeds ?<br /> <br /> :Download the the following python scripts if you prefer not to mess around with alsactl:<br /> <br /> :http://handheldshell.com/pymixer.py<br /> :http://handheldshell.com/volume.desktop<br /> <br /> :put pymixer in /usr/bin<br /> <br /> chmod u+x /usr/bin/pymixer.py<br /> <br /> :put volume.desktop in /usr/share/applications<br /> <br /> :Get the [[http://handheldshell.com/gsm_headset.txt alsa state file]] - this state file _WORKS_, mic and earphones are properly routed<br /> <br /> cp gsm_headset.txt /usr/share/openmoko/scenarios/btheadset.state<br /> <br /> :from the home screen run Volume<br /> <br /> :from the terminal run<br /> <br /> BtHeadset.py <br /> <br /> :Wait until it says waiting for call to end, you should hear static in the headset. If you don't something has gone wrong.<br /> <br /> :Now start the call<br /> <br /> :In the volume control switch to the btheadset tab. press restore<br /> <br /> :You should now hear the call in your headset. <br /> <br /> :End the call<br /> <br /> BtHeadsetDisconnect.py <br /> <br /> :This was all done with the 2008-updates image from sept 4. <br /> <br /> :The new scripts rely on a specific format for the .asoundrc . A stanza like this is required :<br /> <br /> pcm.headset {<br /> type bluetooth<br /> device &lt;headset mac&gt;<br /> profile &quot;voice&quot;<br /> }<br /> <br /> == Once Again, Bluetooth Headset on Freerunner ==<br /> <br /> I managed to connect my bluetooth headset to the Freerunner and route calls to it. However, I couldn't get an actual voice over it, just crackling. Those who know more about this than I suggest this is due to the fact that my bluetooth headset is very cheap, so your mileage may vary.<br /> <br /> PLEASE NOTE: You will need a recent git revision of frameworkd (latest in SHR-Unstable repos will do) and bluez4 to do this.<br /> <br /> To prepare, you will need a fixed statefile for bluetooth. You can download this at:<br /> http://dl.getdropbox.com/u/453116/gsmbluetooth.state<br /> You need to put it on your Freerunner in the /usr/share/openmoko/scenarios/ directory. You will also need to modify your rules.yaml file. You should replace the entire section from '''Call -&gt; Audio Scenario Handling''' (Which is shown) to (but not including) '''while: PowerStatus()''' with the following:<br /> <br /> -<br /> #<br /> # Call -&gt; Audio Scenario Handling<br /> #<br /> trigger: IncomingMessage()<br /> actions: MessageTone(play)<br /> <br /> -<br /> while: CallListContains(&quot;incoming&quot;)<br /> filters: Not(CallListContains(&quot;active&quot;))<br /> actions:<br /> - RingTone()<br /> - SetDisplayBrightness(&quot;0&quot;, 90)<br /> - OccupyResource(CPU)<br /> <br /> -<br /> while: CallStatus()<br /> filters: Or(HasAttr(status, &quot;outgoing&quot;), HasAttr(status, &quot;active&quot;))<br /> actions:<br /> - OccupyResource(CPU)<br /> -<br /> while: CallStatus()<br /> filters:<br /> - Or(HasAttr(status, &quot;outgoing&quot;), HasAttr(status, &quot;active&quot;))<br /> - Not(BTHeadsetIsConnected())<br /> actions:<br /> - SetScenario(gsmhandset)<br /> -<br /> while: CallStatus()<br /> filters:<br /> - Or(HasAttr(status, &quot;outgoing&quot;), HasAttr(status, &quot;active&quot;))<br /> - BTHeadsetIsConnected()<br /> actions:<br /> - SetScenario(gsmbluetooth)<br /> - BTHeadsetPlaying()<br /> -<br /> <br /> Now you will need to restart frameworkd:<br /> /etc/init.d/frameworkd restart<br /> This causes problems for me, so you may find it easier to reboot.<br /> <br /> Now, you must pair the bluetooth headset with your Freerunner. Make sure the bluetooth chip is powered up (can be done through the Connectivity section in the SHR-Unstable settings manager) and that bluetoothd is running:<br /> /etc/init.d/bluetooth start<br /> Now, to actually pair the bluetooth headset, you will need the simple-agent script. If you already have it, excellent. If you, like me, do not, then you can get it here:<br /> http://dl.getdropbox.com/u/453116/simple-agent<br /> Put it in /usr/bin/ and run '''chmod a+x /usr/bin/simple-agent'''<br /> <br /> Now put your headset into pairing mode and run '''hcitool scan'''. Find your headset and use its address in the command '''simple-agent hci0 XX:XX:XX:XX:XX:XX'''. If you give a third parameter (what it is doesn't matter) to simple-agent, it will disconnect then reconnect to the headset. 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 /> Hopefully, your bluetooth headset now works. Good luck!<br /> <br /> == Debugging ==<br /> <br /> If anything goes wrong, capture the bluetooth traffic with<br /> sudo hcidump -l 4096 -w bt.dump<br /> and attach bt.dump to your bug reports etc.<br /> <br /> == Further reading ==<br /> <br /> http://www.holtmann.org/papers/bluetooth/ols2006_slides.pdf<br /> http://wiki.bluez.org/wiki/Audio#org.bluez.Audio<br /> http://www.gentoo.org/doc/en/bluetooth-guide.xml<br /> <br /> {{Languages|Manually_using_Bluetooth}}<br /> <br /> [[Category:Bluetooth| ]]<br /> [[Category:Networking]]<br /> [[Category:Application Developer]]</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-10-14T04:46:22Z

<p>Wurp: /* Installing an image */</p> <hr /> <div>{{Distributions|SHR}}<br /> {{SHR}}<br /> == Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a community driven distribution composed of the [[OpenmokoFramework|FSO]] and some basic applications, that can be configured to use several diffrent graphical toolkits, for example GTK or EFL. SHR is based on the FSO build.<br /> <br /> == Why SHR exists ==<br /> At first, SHR was introduced in order to use the [[Openmoko2007.2]] GTK software in combination with the new [[OpenmokoFramework|FSO]].<br /> Things have changed. SHR is now mainly a community driven distribution, that contains some basic applications which make use of the [[OpenmokoFramework|FSO]].<br /> <br /> ====Why not FSO?====<br /> FSO is the initiative by Mickey Lauer and crew to create a good [[D-Bus]] infrastructure which runs on the neos, among other devices.<br /> <br /> FSO is by far the most stable &amp; usable release, if all you want is a phone. (I mean *all*. It just has a dialer, which is a demo application, right now.)<br /> <br /> FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br /> <br /> Other people are supposed to put a front end on FSO. So that's what we're doing.<br /> <br /> == Interest ==<br /> See the Developer Info on the upper right side of the [http://projects.openmoko.org/projects/shr SHR project page].<br /> <br /> == How to join ==<br /> * Hang out in ''#openmoko-cdevel'' on ''irc.freenode.net'' between 5pm and 11pm GMT to chat with the people developing SHR. (Primarily MarcOChapeau, Ainulindale and quickdev.)<br /> * Send a request to join on the [http://projects.openmoko.org/projects/shr SHR project] on the OM projects page.<br /> * Join [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel shr-devel@lists.projects.openmoko.org] and send an introductory email. The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.<br /> * See [[SHR Development]] to find out how to set up your development environment to work on existing SHR packages.<br /> <br /> == Tasks &amp; status ==<br /> <br /> The list of tasks is available at the [http://shr.bearstech.com/trac/ SHR Milestone] page. Some information is missing this is why the table below is still valid.<br /> <br /> {|cellpadding=&quot;6&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |Comment<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |<br /> |Nobody<br /> |<br /> |<br /> |}<br /> <br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://projects.openmoko.org/projects/shr/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |fork media player for SHR<br /> |Done!<br /> |2008-08-07<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> [[Category:new trac location]]<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * frameworkd<br /> <br /> Additionally:<br /> * libframeworkd-glib (C bindings for frameworkd dbus interface)<br /> * ophonekitd (daemon that handles frameworkd events, for example showing the UI on an incoming call)<br /> * openmoko-dialer3<br /> <br /> <br /> == Download ==<br /> <br /> There's a buildhost sponsored by bearstech.com, which builds the shr images:<br /> <br /> http://shr.bearstech.com/shr-testing/images/neo1973/<br /> <br /> <br /> == Technical Help ==<br /> <br /> === Installing an image ===<br /> Download the appropriate uImage and jffs2 from http://shr.bearstech.com/shr-testing/images/neo1973/ and install as normal. Afterwards, run opkg update &amp;&amp; opkg upgrade. You may need to edit /etc/resolv.conf and put something like this in it:&lt;br/&gt;<br /> nameserver 208.67.222.222&lt;br/&gt;<br /> nameserver 208.67.220.220&lt;br/&gt;<br /> <br /> === Getting the source code ===<br /> <br /> We're currently hosted by [[User:Ainulindale|Ainulindale]] on svn://daria.forty-two.fr/shr . In order to contribute, you have to ask Ainulindale to get your public key on the server.<br /> <br /> There is no need to download the code independently as it is automatically obtained when setting the development environment described in [[SHR Development]].<br /> <br /> === Build logic ===<br /> <br /> Current applications (openmoko-dialer3 and openmoko-panel-gsm) use frameworkd.<br /> So in order to be able to build and test these applications, you have to build frameworkd and gsm0710muxd.<br /> <br /> === [[libframeworkd-glib]] ===<br /> <br /> In order to be able to use in an easy way frameworkd, without bothering about dbus calls (which could be difficult for new developers), we built a library allowing everyone to use the functions of frameworkd as if it were simple C functions. We're using asynchronous callbacks for dbus. libfraemworkd-glib is heavily used by SHR applications and now hosted on http://git.freesmartphone.org/?p=libframeworkd-glib.git;a=summary.<br /> <br /> === Architecture ===<br /> SHR uses FSO to interface to the hardware, so see the FSO architecture documentation, too. For how the openmoko*3 applications that SHR forked off 2007.2 access FSO, see http://www.calaquendi.org/om/lf.png.<br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:SHR]]</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-10-14T04:46:01Z

<p>Wurp: /* Technical Help */</p> <hr /> <div>{{Distributions|SHR}}<br /> {{SHR}}<br /> == Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a community driven distribution composed of the [[OpenmokoFramework|FSO]] and some basic applications, that can be configured to use several diffrent graphical toolkits, for example GTK or EFL. SHR is based on the FSO build.<br /> <br /> == Why SHR exists ==<br /> At first, SHR was introduced in order to use the [[Openmoko2007.2]] GTK software in combination with the new [[OpenmokoFramework|FSO]].<br /> Things have changed. SHR is now mainly a community driven distribution, that contains some basic applications which make use of the [[OpenmokoFramework|FSO]].<br /> <br /> ====Why not FSO?====<br /> FSO is the initiative by Mickey Lauer and crew to create a good [[D-Bus]] infrastructure which runs on the neos, among other devices.<br /> <br /> FSO is by far the most stable &amp; usable release, if all you want is a phone. (I mean *all*. It just has a dialer, which is a demo application, right now.)<br /> <br /> FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br /> <br /> Other people are supposed to put a front end on FSO. So that's what we're doing.<br /> <br /> == Interest ==<br /> See the Developer Info on the upper right side of the [http://projects.openmoko.org/projects/shr SHR project page].<br /> <br /> == How to join ==<br /> * Hang out in ''#openmoko-cdevel'' on ''irc.freenode.net'' between 5pm and 11pm GMT to chat with the people developing SHR. (Primarily MarcOChapeau, Ainulindale and quickdev.)<br /> * Send a request to join on the [http://projects.openmoko.org/projects/shr SHR project] on the OM projects page.<br /> * Join [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel shr-devel@lists.projects.openmoko.org] and send an introductory email. The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.<br /> * See [[SHR Development]] to find out how to set up your development environment to work on existing SHR packages.<br /> <br /> == Tasks &amp; status ==<br /> <br /> The list of tasks is available at the [http://shr.bearstech.com/trac/ SHR Milestone] page. Some information is missing this is why the table below is still valid.<br /> <br /> {|cellpadding=&quot;6&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |Comment<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |<br /> |Nobody<br /> |<br /> |<br /> |}<br /> <br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://projects.openmoko.org/projects/shr/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |fork media player for SHR<br /> |Done!<br /> |2008-08-07<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> [[Category:new trac location]]<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * frameworkd<br /> <br /> Additionally:<br /> * libframeworkd-glib (C bindings for frameworkd dbus interface)<br /> * ophonekitd (daemon that handles frameworkd events, for example showing the UI on an incoming call)<br /> * openmoko-dialer3<br /> <br /> <br /> == Download ==<br /> <br /> There's a buildhost sponsored by bearstech.com, which builds the shr images:<br /> <br /> http://shr.bearstech.com/shr-testing/images/neo1973/<br /> <br /> <br /> == Technical Help ==<br /> <br /> === Installing an image ===<br /> Download the appropriate uImage and jffs2 from http://shr.bearstech.com/shr-testing/images/neo1973/ and install as normal. Afterwards, run opkg update &amp;&amp; opkg upgrade. You may need to edit /etc/resolv.conf and put something like this in it:<br /> nameserver 208.67.222.222<br /> nameserver 208.67.220.220<br /> <br /> === Getting the source code ===<br /> <br /> We're currently hosted by [[User:Ainulindale|Ainulindale]] on svn://daria.forty-two.fr/shr . In order to contribute, you have to ask Ainulindale to get your public key on the server.<br /> <br /> There is no need to download the code independently as it is automatically obtained when setting the development environment described in [[SHR Development]].<br /> <br /> === Build logic ===<br /> <br /> Current applications (openmoko-dialer3 and openmoko-panel-gsm) use frameworkd.<br /> So in order to be able to build and test these applications, you have to build frameworkd and gsm0710muxd.<br /> <br /> === [[libframeworkd-glib]] ===<br /> <br /> In order to be able to use in an easy way frameworkd, without bothering about dbus calls (which could be difficult for new developers), we built a library allowing everyone to use the functions of frameworkd as if it were simple C functions. We're using asynchronous callbacks for dbus. libfraemworkd-glib is heavily used by SHR applications and now hosted on http://git.freesmartphone.org/?p=libframeworkd-glib.git;a=summary.<br /> <br /> === Architecture ===<br /> SHR uses FSO to interface to the hardware, so see the FSO architecture documentation, too. For how the openmoko*3 applications that SHR forked off 2007.2 access FSO, see http://www.calaquendi.org/om/lf.png.<br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:SHR]]</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-10-13T15:50:12Z

<p>Wurp: /* Tasks &amp; status */</p> <hr /> <div>{{Distributions|SHR}}<br /> {{SHR}}<br /> == Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a community driven distribution composed of the [[OpenmokoFramework|FSO]] and some basic applications, that can be configured to use several diffrent graphical toolkits, for example GTK or EFL. SHR is based on the FSO build.<br /> <br /> == Why SHR exists ==<br /> At first, SHR was introduced in order to use the [[Openmoko2007.2]] GTK software in combination with the new [[OpenmokoFramework|FSO]].<br /> Things have changed. SHR is now mainly a community driven distribution, that contains some basic applications which make use of the [[OpenmokoFramework|FSO]].<br /> <br /> ====Why not FSO?====<br /> FSO is the initiative by Mickey Lauer and crew to create a good [[D-Bus]] infrastructure which runs on the neos, among other devices.<br /> <br /> FSO is by far the most stable &amp; usable release, if all you want is a phone. (I mean *all*. It just has a dialer, which is a demo application, right now.)<br /> <br /> FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br /> <br /> Other people are supposed to put a front end on FSO. So that's what we're doing.<br /> <br /> == Interest ==<br /> See the Developer Info on the upper right side of the [http://projects.openmoko.org/projects/shr SHR project page].<br /> <br /> == How to join ==<br /> * Hang out in ''#openmoko-cdevel'' on ''irc.freenode.net'' between 5pm and 11pm GMT to chat with the people developing SHR. (Primarily MarcOChapeau, Ainulindale and quickdev.)<br /> * Send a request to join on the [http://projects.openmoko.org/projects/shr SHR project] on the OM projects page.<br /> * Join [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel shr-devel@lists.projects.openmoko.org] and send an introductory email. The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.<br /> * See [[SHR Development]] to find out how to set up your development environment to work on existing SHR packages.<br /> <br /> == Tasks &amp; status ==<br /> <br /> The list of tasks is available at the [http://shr.bearstech.com/trac/ SHR Milestone] page. Some information is missing this is why the table below is still valid.<br /> <br /> {|cellpadding=&quot;6&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |Comment<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |<br /> |Nobody<br /> |<br /> |<br /> |}<br /> <br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://projects.openmoko.org/projects/shr/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |fork media player for SHR<br /> |Done!<br /> |2008-08-07<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> [[Category:new trac location]]<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * frameworkd<br /> <br /> Additionally:<br /> * libframeworkd-glib (C bindings for frameworkd dbus interface)<br /> * ophonekitd (daemon that handles frameworkd events, for example showing the UI on an incoming call)<br /> * openmoko-dialer3<br /> <br /> <br /> == Download ==<br /> <br /> There's a buildhost sponsored by bearstech.com, which builds the shr images:<br /> <br /> http://shr.bearstech.com/shr-testing/images/neo1973/<br /> <br /> <br /> == Technical Help ==<br /> <br /> === Getting the source code ===<br /> <br /> We're currently hosted by [[User:Ainulindale|Ainulindale]] on svn://daria.forty-two.fr/shr . In order to contribute, you have to ask Ainulindale to get your public key on the server.<br /> <br /> There is no need to download the code independently as it is automatically obtained when setting the development environment described in [[SHR Development]].<br /> <br /> === Build logic ===<br /> <br /> Current applications (openmoko-dialer3 and openmoko-panel-gsm) use frameworkd.<br /> So in order to be able to build and test these applications, you have to build frameworkd and gsm0710muxd.<br /> <br /> === [[libframeworkd-glib]] ===<br /> <br /> In order to be able to use in an easy way frameworkd, without bothering about dbus calls (which could be difficult for new developers), we built a library allowing everyone to use the functions of frameworkd as if it were simple C functions. We're using asynchronous callbacks for dbus. libfraemworkd-glib is heavily used by SHR applications and now hosted on http://git.freesmartphone.org/?p=libframeworkd-glib.git;a=summary.<br /> <br /> === Architecture ===<br /> SHR uses FSO to interface to the hardware, so see the FSO architecture documentation, too. For how the openmoko*3 applications that SHR forked off 2007.2 access FSO, see http://www.calaquendi.org/om/lf.png.<br /> <br /> <br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:SHR]]</div>

Wurp http://wiki.openmoko.org/wiki/Qtopia_/_Qt_Extended_on_FreeRunner 2008-10-03T20:53:25Z

<p>Wurp: </p> <hr /> <div>{{Languages|Qtopia_on_FreeRunner}}<br /> <br /> This page provides instructions on how to install Qtopia (proper, not the [[ASU]] or [[QtopiaOnX11]] efforts) on the GTA02 (FreeRunner) phone. It is similar to the [[Qtopia on Neo1973]] page.<br /> <br /> {|align=right<br /> |__TOC__<br /> |}<br /> <br /> == Current status ==<br /> On 29 August 2008, Trolltech released the [http://qtextended.org/modules/mydownloads/visit.php?lid=79 Qtopia flash image for the FIC Neo FreeRunner (gta02)] containing the Qtopia 4.3.2 release (Version: 4.3.2-290808) (GPL version). <br /> See [http://doc.trolltech.com/qtopia4.3/release-4-3-2.html Release-Notes]<br /> <br /> This image can successfully make and receive calls and text messages. It can read all contacts from the SIM card (which the updated 2007.2 does not appear to be able to do). It contains apps that appear to be more stable than the ones found in the 2007.2 image. It has multiple input methods that appear to be more mature. It does not, however, have a web browser or a GPS application. There are however at least two third-party GPS applications available:<br /> * [http://blog.wolfman.com/articles/2008/08/27/porting-xgps-to-qtopia-for-the-freerunner xgps here]<br /> * [http://www.linux4.be/fr/roadmap.html RoadMap(experimental) here]<br /> <br /> On 2nd of September 2008 Trolltech also released a 4.3.3-snapshot which fixes a number issues (sms messages not retrieved after resume; Qtopia getting confused between two calls; Make default call volume down and mic up; Added echo fix.)<br /> <br /> You can find all the Qtopia images [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6 here] (including Qtextended/Qtopia 4.4 for FreeRunner and Neo1973!)<br /> <br /> === What to expect in the next release (Qtopia 4.4)? ===<br /> Qtopia 4.4 has been released with the name of [http://doc.trolltech.com/qtextended4.4/release-4-4-1.html QtExtended 4.4]. The FreeRunner image will be ready in 3 days (3 okt).<br /> * a [http://n2.nabble.com/qtopia-update-tp832851p832888.html browser] based on webkit<br /> * [http://n2.nabble.com/-qtopia--rotate-screen--tp841805p841841.html screen rotation in the settings application] (so no automatic rotation)<br /> * [http://n2.nabble.com/Echo-issue-on-OM2008.08-potentially-solved-tp791642.html noise reduction]<br /> * GPS api<br /> * usb net/storage switching<br /> * Gtalk support<br /> * [http://n2.nabble.com/forum/Permalink.jtp?root=841805&amp;post=1083388&amp;page=y better support for non-english languages in the keyboard]<br /> <br /> == Option 1: Flashing Qtopia to FreeRunner ==<br /> <br /> Download the image mentioned above and follow the instructions here: [[Flashing the Neo FreeRunner]]<br /> <br /> == Option 2: Dual-Booting between Qtopia and 2007.2 (Qtopia boots from MicroSD card) ==<br /> <br /> Installation Requirements: <br /> <br /> # SSH shell access to 2007.2 based image of the FreeRunner through USB interface or WLAN.<br /> # A Desktop Linux distro (to unpack the .jffs2 image, I ran Ubuntu under VMWare)<br /> <br /> <br /> === Preparing the SD card ===<br /> <br /> See the [[Booting from SD#Prepare the SD card| Preparing the SD Card]] section of the [[Booting from SD]] page for partitioning and formatting instructions. After you complete the &quot;Formatting the SD Card&quot; steps, return here and execute the following:<br /> <br /> mount /dev/mmcblk0p1 /media/card<br /> mkdir /media/card/boot<br /> <br /> mkdir /media/mmcblk0p2<br /> mount /dev/mmcblk0p2 /media/mmcblk0p2<br /> <br /> This will set you up properly for the installation of the root filesystem and the kernel in the steps below.<br /> <br /> === Installing Qtopia ===<br /> <br /> ==== Unpacking the Qtopia Root Filesystem Image ====<br /> <br /> Download the Qtopia FLASH image from [[Latest Images#Qtopia images]] to your Linux box and extract its contents:<br /> <br /> tar xzf qtopia-4.3.2-gta02-flash-*.tgz<br /> <br /> You should now have two files: <br /> #uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin<br /> #qtopia-4.3.2-gta02-rootfs-07172049.jffs2 <br /> Now, mount the root file system from the jffs2 using the commands found [[Userspace root image#Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) |here]]. However, in the mount command, substitute the image filename for &quot;/dev/mtdblock0&quot;.<br /> <br /> ==== Creating a compressed tarball ====<br /> <br /> Next, tar up the root filesystem:<br /> <br /> # tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz -C &lt;mountpoint&gt; .<br /> <br /> Where ''&lt;mountpoint&gt;'' is the location where the jff2 filesystem was mounted. Note the space and the period after the mountpoint.<br /> <br /> ==== Installing Root Filesystem ====<br /> <br /> Transfer this compressed tarball to the second partition of the MicroSD that is mounted on the FreeRunner:<br /> <br /> scp qtopia-4.3.2-gta02-rootfs-07172049.tar.gz root@192.168.0.202:/media/mmcblk0p2/<br /> <br /> Log in to your FreeRunner and unpack the root filesystem:<br /> <br /> cd /media/mmcblk0p2<br /> tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz<br /> rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz<br /> rm -f /media/mmcblk0p2/boot/*<br /> <br /> '''''Note:''''' the last step removes the kernel image from the second partition. For some reason, U-Boot cannot find the uImage.bin file in the first partition if a kernel image exists in the second partition boot/ directory.<br /> <br /> ==== Installing Kernel ====<br /> <br /> From your Linux box, rename &lt;tt&gt;uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin&lt;/tt&gt; to &lt;tt&gt;uImage.bin&lt;/tt&gt; and copy it to the boot directory on the first partition of the MicroSD card. Depending on the version of U-Boot you have installed, this may not work. To prevent any possible issues, copy it to the &lt;tt&gt;/media/card&lt;/tt&gt; directory as well. There is plenty of room on the first partition to have &lt;tt&gt;uImage.bin&lt;/tt&gt; in both locations.<br /> <br /> mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin<br /> scp uImage.bin root@192.168.0.202:/media/card/boot/<br /> scp uImage.bin root@192.168.0.202:/media/card/<br /> <br /> ==== Pointing Qtopia to the SD Card ====<br /> <br /> Lorn Potter on the mailing lists pointed this out:<br /> <br /> Qtopia was designed to be run from the root partition on a flash chip, not from a removable sd card.<br /> <br /> You would have to edit the etc/default/Trolltech/Storage.conf file to make it forget about the sd <br /> /dev node, to be able to run it this way&quot;<br /> <br /> Another user's solution to this is the following:<br /> <br /> Edit this file: &quot; /opt/Qtopia/etc/default/Trolltech/Storage.conf<br /> And change the [MountPoint0] section so it resembles this:<br /> -[ <br /> [MountPoint0]<br /> Name[] = SD Card<br /> Path=/dev/mmcblk0p1<br /> Removable = 0<br /> Applications = 0<br /> Documents = 0<br /> ContentDatabase = 0<br /> <br /> == Option 3: updating from source ==<br /> <br /> {{note|This will upgrade only opt/Qtopia directory, you should use opkg update/upgrade for the rest}}<br /> Original Qtopia images (the distribution released by Trolltech, not ASU) are rarely released as a rootfs image, but the source code is often updated. If you want to reflash your OM with the latest version of Qtopia you might build it from sources. This has been explained in [http://lists.openmoko.org/pipermail/community/2008-August/024785.html this thread] of the community mailing list. Summing up:<br /> <br /> * get the latest toolchain released by trolltech: http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=38 and unzip it on your PC (as root)<br /> cd /<br /> wget http://qtopia.net/downloads/neo/arm920t-eabi-ficgta01-toolchain.tgz<br /> tar xvzf arm920t-eabi-ficgta01-toolchain.tgz<br /> * get the latest snapshot from trolltech: ftp://ftp.trolltech.com/qtopia/snapshots/<br /> * once dowloaded untar it<br /> tar xvzf qtopia-opensource-src-4.3.2-snapshot-20080806.tar.gz<br /> * make a &quot;build&quot; dir <br /> mkdir build<br /> cd build<br /> * configure and make:<br /> ../qtopia-opensource-src-4.3.2-snapshot-20080806/configure -device ficgta01<br /> make <br /> This will take some time (couple hours). Note that the option &quot;-device ficgta01&quot; should work for both neo and freerunner. Then:<br /> <br /> make install<br /> <br /> will make a root directory into the ''build'' directory. There you can find an ''image'' that directory should be copied to /opt/Qtopia of your phone with scp. once done restart qpe or whole phone.<br /> <br /> == Booting into Qtopia ==<br /> <br /> Now shutdown the FreeRunner<br /> <br /> shutdown -h now<br /> <br /> Log into U-Boot in the NAND Flash to boot from the MicroSD card: (instructions from [[Booting the Neo FreeRunner]])<br /> <br /> * Press and hold Power button<br /> * Then while still pressing the Power button, press and hold AUX button for 5 to 8 seconds. <br /> * A boot menu will appear. <br /> * Press the AUX button to select &quot;[[Boot from sd card|Boot from MicroSD]]&quot; and then press the Power button to execute.<br /> <br /> Qtopia should now boot.<br /> <br /> '''''Note:''''' you may get a kernel panic which says that &quot;optional features not supported&quot;. If this is the case, boot back into 2007.2 and run<br /> <br /> umount /dev/mmcblk0p2<br /> fsck.ext3.e2fsprogs /dev/mmcblk0p2<br /> <br /> This will clean up the file system and clear recovery flags in ext3 that ext2 does not support, then try booting from the MicroSD again.<br /> <br /> == Internationalization ==<br /> <br /> Qtopia comes with support for German and American English, and users from other countries will find that Qtopia's predictive keyboard makes writing in another language near impossible. One way to disable the predictive keyboard is to simply replace /opt/Qtopia/etc/dict/en_US/common.dawg and words.dawg with empty files (after backing them up). Qtopia normally looks in these files for words to suggest, and if it doesn't find any words that fit, it simply shows what you actually wrote.<br /> <br /> Adding characters to the keyboard requires modifications to the source code, as described [http://www.qtopia.net/modules/newbb_plus/viewtopic.php?topic_id=512&amp;forum=16 here].<br /> <br /> [[Category:Qtopia]]<br /> <br /> == Suspend /Resume ==<br /> It seems that suspend/resume only works when the FreeRunner has been connected to a powersource (only a few seconds if sufficient). If you boot from battery, it will never suspend until you have plugged it in at least for a couple of seconds.<br /> <br /> == Bugs ==<br /> <br /> See [http://trolltech.org/developer/task-tracker/index_html?method=front Trolltech's tracker] ([http://trolltech.org/developer/task-tracker/index_html?method=advsearch&amp;searchstr=&amp;bugs=on&amp;sugs=on&amp;product=2&amp;functionalarea=&amp;versionfound=&amp;versionfixed=&amp;priority=-1&amp;status=0&amp;resolution=-1 Qtopia Tracker]).<br /> <br /> Bug reports should be sent to qt-bugs@trolltech.com.<br /> == Bugs in 4.4.1 ==<br /> * Timezone &amp; time on latest Qt 4.4.1<br /> * The first item in a list is missing the top half</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-09-15T20:24:17Z

<p>Wurp: /* Architecture */</p> <hr /> <div>{{Distributions|SHR}}<br /> {{SHR}}<br /> == Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the [[Openmoko2007.2]] GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br /> <br /> (We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the ''discussion'' tab of this page.)<br /> <br /> Follow the project here: [http://projects.openmoko.org/projects/shr SHR Project Homepage]<br /> <br /> == Why SHR exists ==<br /> This is long and rambling, and maybe more of a tirade than information, but it does give some background on why this project was started. The overview gives, well, the overview, this is more of a deeper examination of the existing releases and why we felt we needed something new.<br /> <br /> Feel free to skip this whole section if you already think SHR is a good idea :-)<br /> <br /> === Why not ASU? ===<br /> ASU is the distro that OM is putting their main effort into right now. ASU looks very slick, but is very unstable right now, and is likely to be unstable and feature-poor for some time.<br /> <br /> === Why not 2007.2? ===<br /> 2007.2 is the &quot;old&quot; Openmoko distribution, now unsupported. Unsupported == often broken. Also, neither calls nor suspend/resume ever worked reliably.<br /> <br /> === Why not Qtopia? ===<br /> You can also install Qtopia on the phone.<br /> <br /> Qtopia is stable but you can only build qt apps on Qtopia, which means lots of linux apps you might want to port suddenly got a lot harder to port. And some people just don't like developing for qt.<br /> <br /> Also, as far as I know, there is no documented build procedure for Qtopia on Openmoko.<br /> <br /> === Why not FSO? ===<br /> FSO is the initiative by Mickey Lauer and crew to create a good [[D-Bus]] infrastructure which runs on the neos, among other devices.<br /> <br /> FSO is by far the most stable &amp; usable release, if all you want is a phone. (I mean *all*. It just has a dialer right now, not even call history.)<br /> <br /> FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br /> <br /> Other people are supposed to put a front end on FSO. So that's what we're doing.<br /> <br /> === Why SHR? ===<br /> So SHR is FSO, with us doing the necessary work to port the old high-functionality 2007.2 stuff on a stable call platform. We have an adapter from the 2007.2 call service to the FSO call service and we're installing the basic 2007.2 apps on the FSO baseline install.<br /> <br /> In theory, it should be very simple, and should give us dialer, contact management, SMS, terminal, media player, gps app, etc. since all those already work on 2007.2. And the dialer should be stable, which it wasn't in 2007.2<br /> <br /> == First steps ==<br /> The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br /> <br /> We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br /> <br /> == Interest ==<br /> See the Developer Info on the upper right side of the [http://projects.openmoko.org/projects/shr SHR project page].<br /> <br /> == How to join ==<br /> * Send a request to join on the [http://projects.openmoko.org/projects/shr SHR project] on the OM projects page.<br /> * Join [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel shr-devel@lists.projects.openmoko.org] and send an introductory email. The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.<br /> * Hang out in ''#openmoko-cdevel'' on ''irc.freenode.net'' between 5pm and 11pm GMT to chat with the people developing SHR. (Primarily MarcOChapeau and Ainulindale.)<br /> * See [[SHR Development]] to find out how to set up your development environment to work on existing SHR packages.<br /> <br /> == Tasks &amp; status ==<br /> <br /> The list of tasks is available at the [http://docs.openmoko.org/trac/milestone/SHR SHR Milestone] page. Some information is missing this is why the table below is still valid.<br /> <br /> {|cellpadding=&quot;6&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |Comment<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space; just need to talk about git branches<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |[[User:Kevin_Dean|Kevin Dean]]<br /> |Nobody<br /> |2008-07-05<br /> |<br /> |}<br /> <br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://projects.openmoko.org/projects/shr/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |fork media player for SHR<br /> |Done!<br /> |2008-08-07<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> == Technical Help ==<br /> <br /> === Getting the source code ===<br /> <br /> We're currently hosted by [[User:Ainulindale|Ainulindale]] on svn://daria.forty-two.fr/shr as projects went down for a whole week-end.<br /> <br /> There is no need to download the code independently as it is automatically obtained when setting the development environment described in [[SHR Development]].<br /> <br /> === Build logic ===<br /> <br /> Current applications (openmoko-dialer3 and openmoko-panel-gsm) use frameworkd.<br /> So in order to be able to build and test these applications, you have to build frameworkd (MS2) and gsm0710muxd.<br /> <br /> === [[libframeworkd-glib]] ===<br /> <br /> In order to be able to use in an easy way frameworkd, without bothering about dbus calls (which could be difficult for new developers), we built a library allowing everyone to use the functions of frameworkd as if it were simple C functions. We're using asynchronous callbacks for dbus.<br /> <br /> === Architecture ===<br /> SHR uses FSO to interface to the hardware, so see the FSO architecture documentation, too. For how the openmoko*3 applications that SHR forked off 2007.2 access FSO, see http://img117.imageshack.us/my.php?image=lfiv9.png<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * ophoned<br /> * preferencesd<br /> * pimd<br /> * odeviced<br /> * lots more...<br /> <br /> From 2007.2:<br /> * TODO<br /> * lots more...<br /> <br /> From ASU:<br /> * TODO<br /> * lots more...<br /> <br /> == IRC conversation about how we're using revision control ==<br /> <br /> ''This is deprecated, for now we use shr-devel as our only repository. This will change after the first SHR release.''&lt;br/&gt;<br /> From 2007-07-07<br /> &lt;pre&gt;<br /> 12:36 &lt; wurp2&gt; Everything *new* goes on OM projects site<br /> 12:36 &lt; Ainulindale&gt; I totally agree<br /> 12:36 &lt; wurp2&gt; Updates to 2007.2 apps go back into the home svn<br /> 12:36 &lt; Ainulindale&gt; paulproteus: no, you're an external cabal all by yourself<br /> :-)<br /> 12:36 &lt; cb22&gt; anyone planning on drawing up a roadmap?<br /> 12:36 &lt; paulproteus&gt; cb22, We can do that in Trac in fact.<br /> 12:36 &lt; wurp2&gt; And changes to the underlying release go as patches into our OE<br /> branch, yes?<br /> 12:36 &lt; paulproteus&gt; (or on the wiki page)<br /> 12:36 &lt; paulproteus&gt; wurp2, Right<br /> 12:36 &lt; paulproteus&gt; mwester, Sanity-check my terminology where I mess things<br /> up!<br /> 12:37 &lt; Ainulindale&gt; hmmm fuzzy for me but what should go in OM and what should<br /> go in OE ?<br /> 12:37 &lt;@mwester&gt; Sure<br /> 12:37 &lt;@mwester&gt; What do you mean by OM?<br /> 12:37 &lt; paulproteus&gt; Ainulindale, New software we write goes in the<br /> projects.openmoko.org.<br /> 12:37 &lt;@mwester&gt; right.<br /> 12:37 &lt; Ainulindale&gt; Ok so the wrapper for example<br /> 12:37 &lt; wurp2&gt; Anything stand-alone goes in OM (projects.openmoko.org)<br /> 12:37 &lt; wurp2&gt; yeah<br /> 12:37 &lt;@mwester&gt; So we will use projects.openmoko.org for as much as we can,<br /> and OE to build the distro.<br /> 12:37 &lt; Ainulindale&gt; Sounds right to me<br /> 12:37 &lt; wurp2&gt; Great!<br /> 12:38 &lt;@mwester&gt; We *will not* use the OM git repo, as that is owned and<br /> controlled by Openmoko the company...<br /> &lt;/pre&gt;<br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:SHR]]</div>

Wurp http://wiki.openmoko.org/wiki/Qtopia_on_Neo1973 2008-09-03T20:56:02Z

<p>Wurp: /* Build Qtopia from source */</p> <hr /> <div>[http://en.wikipedia.org/wiki/Qtopia Qtopia] is a complete mobile phone and PDA platform which can be built for many devices and is dual-licensed under the GPL and a proprietary license, but since version 3.4.0, everything needed to use Qtopia on the Neo1973 is licensed under the GPL.<br /> {|align=right<br /> |__TOC__<br /> |}<br /> <br /> Please refer to [[Qtopia on FreeRunner]] for Qtopia on the GTA02! See also [[QtopiaOnX11]].<br /> <br /> == Current status ==<br /> On 27 November 2007, Lorn Potter of Trolltech released the [http://www.qtopia.net/modules/mydownloads/visit.php?lid=50 latest flash image for the FIC Neo 1973] containing the Qtopia 4.3.1 snapshot of that day (GPL version). This introduces the new Cruxus mediaengine, which has a few plugins already, which include libmad, tremor (ogg) and timidity, for .wav, .mp3, ogg and .mid file support.<br /> <br /> For installing it, follow the instructions on [[#Flashing Qtopia images|flashing Qtopia images]] below.<br /> <br /> Bug: The dialer might not ask for a PIN (even if your SIM card needs it) on first boot after flashing to Qtopia.&lt;br&gt;<br /> Workaround: Somehow, completely powering down the Neo seems to cure this issue. You do can do it in two ways:<br /> # Remove the USB cable and the Battery for a moment to remove all power from the Neo, or<br /> # Remove the USB cable, press the power button for a second, select &quot;Shutdown device&quot; (Note: &quot;Restart Device&quot; does not help - you need to power it down completely!)<br /> <br /> If your SIM card does not require a PIN, you can skip the above possibly, but otherwise you won't be able to use GSM networks at all!<br /> <br /> '''After this power-cycle of the Neo, the Qtopia dialer should ask for the PIN if it's needed, and you should be able to make and receive calls, each side should hear each other and you should be able to send and receive SMS, and use Contacts for Calls and SMS!!!'''.<br /> <br /> The Call, SMS and contact interface is quite intuitive and should be usable by non-expert users from that point on. Also the rest of Qtopia looks very polished.<br /> <br /> For the latest information on this snapshot read the thread following its [http://lists.openmoko.org/pipermail/community/2007-November/011836.html announcement].<br /> <br /> === Suspend issues ===<br /> The area of battery time and/or suspend still needs improvement. By default, Suspend is disabled in Qtopia because at the moment, you are not able to receive a phone call or an SMS when the Neo is suspended. At the moment (with suspend not enabled, which is the default), Qtopia lasts about 3-5 hours, depending on the amount of use.<br /> <br /> The current maximum standby time seems to be around 7 hours - if there is no use of the phone and the phone is not getting any touches and just sitting on the desk with Bluetooth disabled and getting no touches so that the display is off, just being ready to receive calls and SMS.<br /> <br /> Note that if the Neo [[Neo1973_Battery_Charger#Neo1973_emergency_charging | runs out of battery]], simply connecting USB is not sufficient at that point, the battery has too little voltage to allow the Neo to turn on and enable 500mA charging current. At this point, the Neo is just dead as a brick and charges very slowly with 100mA charging current for about 4 to 6 hours until the battery is recharged enough to allow turning on the Neo and charge with 500mA charging current.<br /> <br /> Current status regarding suspend: Suspending and resuming works, when you remove console=ttySAC0,115200 from bootargs_base (see this [http://blog.rot13.org/2007/09/openmoko_as_a_phone.html howto]), it even wakes up with the GSM part working, but it does not make Qtopia wake up on incoming calls or SMS, so you are not getting notified if you turn on suspend.<br /> After pressing the AUX button, the Neo should wake up from suspend though and should inform you of missed calls and received SMS.<br /> <br /> This bug seems to be [http://labs.trolltech.com/blogs/2007/12/04/neo-neuros-and-other-things/ half-workedarounded], but the fix is not included in the most recent (as of 2007-12-16) official Qtopia image yet. There is an unofficial image from Lorn at http://llornkcor.com/neo/qtopia-4.3-snapshot-12192309-neo-flash.tgz that you can try out that includes his fix.<br /> <br /> == Flashing Qtopia images ==<br /> These are instructions for flashing the latest release of Qtopia (27112007). This seems to be the best working<br /> image yet, eg. voice _and_ SMS seems to work.<br /> <br /> The link to the archive file, Qtopia flash image for FIC Neo 1973,<br /> is mentioned below <br /> <br /> http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=50 [http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=50]<br /> <br /> Get that and save it on your computer. It should be:<br /> &quot;qtopia-4.3.1-snapshot-1127.tgz&quot;<br /> <br /> Unpack it with:<br /> <br /> tar zxvf qtopia-4.3.1-snapshot-1127.tgz<br /> <br /> This should make you have the following two files, ie. a kernel file and<br /> a rootfs file:<br /> <br /> -rw-r--r-- 1 plr 1000 31956148 2007-11-27 06:55<br /> qtopia-rootfs.2-11270550.jffs2<br /> <br /> -rw-r--r-- 1 plr 1000 1538620 2007-11-10 20:57<br /> uImage-2.6.22.5-moko11+svnr3238-r7-neo1973.bin<br /> <br /> In case you already do not have a dfu-util utility, you will need to download it. The following version has been tried out and seemed to work.<br /> <br /> http://buildhost.automated.it/OM2007.2/dfu-util [http://buildhost.automated.it/OM2007.2/dfu-util]<br /> <br /> Before moving forward please make sure of the following<br /> <br /> 1. You have the necessary permissions in your system (i.e. root access)<br /> <br /> 2. dfu-util is executable<br /> <br /> 3. Your Neo is in uboot mode<br /> <br /> 4. And a USB cable is connected between your computer and the Neo<br /> <br /> 5. Realize that the following is low-level stuff and doing something<br /> wrong may brick your Neo<br /> <br /> execute the following from a command line:<br /> <br /> cu -l /dev/ttyACM0<br /> <br /> Which should get you the following:<br /> <br /> Connected.<br /> In: usbtty<br /> Out: usbtty<br /> Err: usbtty<br /> GTA01Bv4 # DEVICE_CONFIGURED: 1<br /> Enabling automatic fast charge<br /> <br /> Press &lt;Enter&gt; and you should get:<br /> <br /> GTA01Bv4 #<br /> <br /> <br /> {{warning|Before flashing the rootfs image, be sure to erase the rootfs using [[nand erase]]. Otherwise, the Neo may hang somewhere after on boot. Before you hit enter on one of the following commands, make sure that you are *not* issuing a plain &quot;nand erase&quot; command - always make sure you tell it which partition to erase. If you forget this you'll brick the Neo and you'll need a debug board to recover it.}}<br /> <br /> At that prompt type:<br /> <br /> nand erase rootfs<br /> <br /> <br /> and the &lt;Enter&gt; key, which should get you:<br /> <br /> NAND erase: device 0 offset 0x2e4000, size 0x3d1c000<br /> OK<br /> GTA01Bv4 #<br /> <br /> At that prompt don't press anything else, but:<br /> <br /> ~.<br /> <br /> and the &lt;Enter&gt; key, which should disconnect you from the bootloader.<br /> <br /> <br /> Now, from the computer prompt, execute the following:<br /> <br /> ./dfu-util -a kernel -R -D uImage-2.6.22.5-moko11+svnr3238-r7-neo1973.bin<br /> <br /> which should get you the following, and it should only take a few<br /> seconds to finish:<br /> <br /> dfu-util - (C) 2007 by Openmoko Inc.<br /> This program is Free Software and has ABSOLUTELY NO WARRANTY<br /> <br /> Opening USB Device 0x0000:0x0000...<br /> Claiming USB DFU Runtime Interface...<br /> Determining device status: state = appIDLE, status = 0<br /> Device really in Runtime Mode, send DFU detach request...<br /> Resetting USB...<br /> Opening USB Device...<br /> Found Runtime: [0x1457:0x5119] devnum=3, cfg=0, intf=0, alt=3, name=&quot;kernel&quot;<br /> Claiming USB DFU Interface...<br /> Setting Alternate Setting ...<br /> Determining device status: state = dfuIDLE, status = 0<br /> dfuIDLE, continuing<br /> Transfer Size = 0x1000<br /> bytes_per_hash=30772<br /> Starting download: [##################################################]<br /> finished!<br /> state(2) = dfuIDLE, status(0) = No error condition is present<br /> Done!<br /> Resetting USB to switch back to runtime mode<br /> <br /> After that, execute the following:<br /> <br /> ./dfu-util -a rootfs -R -D qtopia-rootfs.2-11270550.jffs2<br /> <br /> which should get you the following, and it should take between 5-10min<br /> to finish:<br /> <br /> dfu-util - (C) 2007 by Openmoko Inc.<br /> This program is Free Software and has ABSOLUTELY NO WARRANTY<br /> <br /> Opening USB Device 0x0000:0x0000...<br /> Claiming USB DFU Runtime Interface...<br /> Determining device status: state = appIDLE, status = 0<br /> Device really in Runtime Mode, send DFU detach request...<br /> Resetting USB...<br /> Opening USB Device...<br /> Found Runtime: [0x1457:0x5119] devnum=5, cfg=0, intf=0, alt=5, name=&quot;rootfs&quot;<br /> Claiming USB DFU Interface...<br /> Setting Alternate Setting ...<br /> Determining device status: state = dfuIDLE, status = 0<br /> dfuIDLE, continuing<br /> Transfer Size = 0x1000<br /> bytes_per_hash=639122<br /> Starting download: [##################################################]<br /> finished!<br /> state(2) = dfuIDLE, status(0) = No error condition is present<br /> Done!<br /> Resetting USB to switch back to runtime mode<br /> <br /> In both cases, some text on your Neo should appear, indicating that the<br /> kernel or the rootfs are being downloaded.<br /> <br /> After this, the Neo should be able to boot, and depending on how you<br /> have your boot menu set up, choose &quot;Boot&quot; or perhaps &quot;Boot from NAND&quot;.<br /> The method described above in any case puts the software on the NAND<br /> flash, and not on an SD card, if you have that installed.<br /> <br /> <br /> The latest official Qtopia flash images are found at: http://www.qtopia.net/modules/mydownloads/ (Scroll down on this page to find them)<br /> <br /> Unofficial Qtopia images can be found in the ScaredyCat and Chooseopen [[repositories]].<br /> <br /> For more details on the the process of flashing the Neo, see [[Flashing openmoko]].<br /> <br /> == Dual-booting between Qtopia and X ==<br /> <br /> Both examples described here require you to reformat your MicroSD card to ext3, so this is the first step for both:<br /> <br /> {{warning|The following step will reformat your MicroSD card with the ext3 filesystem. We need it because we need support for symbolic or/and static links, which other filesystems like FAT do not support directly. After reformatting, no data on the card will be accessible to you anymore, so create good backups of anything which you need before starting!}}<br /> <br /> Then ssh to your neo and reformat your MicroSD card with:<br /> umount /dev/mmcblk0p1<br /> mkfs.ext3 /dev/mmcblk0p1<br /> mount /dev/mmcblk0p1<br /> <br /> === Installing Qtopia into an openmoko rootfs ===<br /> <br /> On [http://www.qtopia.net/modules/devices/openmoko.php], click &quot;Developer root filesystem&quot;. Then extract opt/Qtopia and the qpe init script and copy both to the mmc card of your neo:<br /> <br /> tar xzf ficgta01-qtopia-developer-rootfs.tgz opt/Qtopia etc/init.d/qpe<br /> mv opt/Qtopia etc/init.d/qpe . &amp;&amp; rm -r opt etc<br /> tar czf Qtopia.tar.gz Qtopia qpe<br /> scp Qtopia.tar.gz root@192.168.0.202:/media/card/<br /> <br /> Log in to your Neo and unpack the archive and install it:<br /> <br /> cd /media/card<br /> tar xzf Qtopia.tar.gz<br /> mkdir -p /opt<br /> ln -s /media/card/Qtopia /opt/Qtopia<br /> mv qpe /etc/init.d<br /> <br /> Now kill the X server and gsmd and start Qtopia (this can take some time):<br /> <br /> /etc/init.d/xserver-nodm stop<br /> /etc/init.d/gsmd stop<br /> /etc/init.d/qpe start<br /> <br /> Now, in theory, it should be possible to could create a new entry in the [[uboot]] boot menu which adds a new boot argument to the kernel, say &quot;qtopia=1&quot; and you could could write a script which checks that boot parameter by checking if &quot;$qtopia&quot; is set to &quot;1&quot; or by checking /proc/cmdline and then boot Qtopia instead of X.<br /> <br /> === Installing Qtopia on the SD card ===<br /> <br /> * format your SD card with ext3 and mount it (see above)<br /> * unpack rootfs from qtopia-4.3.0-preview-neo-flash.tgz to SD card (see above)<br /> * copy the uImage-2.6.22.5-moko11-r2-fic-gta01.bin kernel to the boot/ on SD card and rename it to uImage<br /> * put a 'Boot from SD' menu item in uboot menu as explained here: [[Booting_from_SD#Step_3:_Add_uboot_boot_entry]]<br /> <br /> == Build Qtopia from source ==<br /> <br /> The source code for qtopia is available from<br /> [ftp://ftp.trolltech.com/qtopia/ ftp.Trolltech.com/Qtopia]<br /> <br /> See http://blog.wolfman.com/articles/2008/08/27/porting-xgps-to-qtopia-for-the-freerunner for some instructions on building.<br /> <br /> == Tips ==<br /> Most things seem to work out of the box, however you might need to use the following command to get audio (but not with the official flash image available from Trolltech):<br /> alsactl -f /etc/gsmhandset.state restore<br /> Or put this command in /etc/init.d/qpe line 64<br /> <br /> Do not switch themes. Only the default theme is usable. For example, once you switch themes, the lock feature continues to work, but only if you unlock using the smallest # keypad in the world.<br /> <br /> Suspend support is very flaky. The neo often shuts off from a suspend state. It will not wake from suspend for an incoming call or text message (someone try setting an alarm and report results here). To turn suspend off (this will of course use the batteries very quickly), hit the down arrow next to the suspend setting in the power management until it says &quot;Off&quot;.<br /> <br /> When using the &quot;Predictive keyboard,&quot; do a quick flick up or down over the keyboard to access numbers/symbols/capitals. In snapshot builds, you can select virtual keyboard by tapping on the little arrow icon to the left of the battery status icon.<br /> <br /> In summary, Qtopia on the Neo1973 is much closer to being ready than Openmoko as of this writing. However, sound and suspend support prevent it from being at all useful as a cell phone (as a landline that doesn't ring but instead vibrates, it works ok).<br /> <br /> The [http://www.qtopia.net/modules/newbb_plus/viewtopic.php?topic_id=473&amp;forum=4 Qtopia forum area on the FIC GTA01] might be helpful, but it is preferred that you update this section with issues and fixes you find.<br /> <br /> == Screenshots ==<br /> <br /> {|<br /> |-<br /> |[[Image:Qtopia001.png|thumb|center|240px]]<br /> |[[Image:Qtopia002.png|thumb|center|240px]]<br /> |[[Image:Qtopia003.png|thumb|center|240px]]<br /> |-<br /> |[[Image:Qtopia004.png|thumb|center|240px]]<br /> |[[Image:Qtopia005.png|thumb|center|240px]]<br /> |[[Image:Qtopia006.png|thumb|center|240px]]<br /> |}<br /> <br /> == Videos ==<br /> <br /> http://www.youtube.com/watch?v=YW5q8SpY7t4<br /> http://www.youtube.com/watch?v=iOG_mtSEMgs<br /> <br /> For full size videos, 346 MiB:<br /> <br /> http://linuxtracker.org/download.php?id=4613&amp;name=qt_on_neo1973_videos.torrent<br /> <br /> {{Languages|Qtopia_on_Neo1973}}<br /> <br /> [[Category:Software (non openmoko)]]<br /> [[Category:Applications]]<br /> [[Category:Qtopia]]</div>

Wurp http://wiki.openmoko.org/wiki/SHR_Development 2008-09-03T16:35:35Z

<p>Wurp: /* Set up your local.conf */ simplify directory information</p> <hr /> <div>{{SHR}}<br /> = New way (using FSO/SHR Makefile) =<br /> <br /> There is a new (much simpler) way to build SHR that is under construction right now.<br /> <br /> === Before beginning ===<br /> <br /> * Download the FSO/SHR ''Makefile'' from [http://shr.bearstech.com/ Bearstech] (see README for details):<br /> <br /> $ wget &lt;nowiki&gt;http://shr.bearstech.com/Makefile&lt;/nowiki&gt;<br /> <br /> * Run:<br /> <br /> $ make setup<br /> <br /> make setup will download FSO, bitbake and SHR in the shr directory (SHR root directory from now on).<br /> <br /> * Change this line in ''common/setup-env'':<br /> <br /> export BBPATH=&quot;${TOPDIR}:${TOPDIR}/openembedded:${TOPDIR}/bitbake&quot;<br /> <br /> for:<br /> <br /> export BBPATH=&quot;${TOPDIR}:${TOPDIR}/shr/openembedded:${TOPDIR}/openembedded:${TOPDIR}/bitbake&quot;<br /> <br /> === Set up your local.conf ===<br /> <br /> Before building the image, you might want to update ''shr-unstable/conf/local.conf'' to speed up the building process with:<br /> <br /> PARALLEL_MAKE = &quot;-j 4&quot;<br /> BB_NUMBER_THREADS = &quot;4&quot;<br /> <br /> To avoid multiple locales generation, add:<br /> <br /> GLIBC_GENERATE_LOCALES = &quot;en_US.UTF-8&quot;<br /> <br /> this will also speed up the whole build.<br /> <br /> === First build ===<br /> <br /> * You are now ready to build the SHR image:<br /> <br /> $ cd shr-unstable<br /> $ make image<br /> <br /> By default, this will build the image for OM-GTA02. If you want to build the image for OM-GTA01:<br /> <br /> $ cd shr-unstable<br /> $ make setup-machine-om-gta01<br /> <br /> you can change it back to OM-GTA02 with ''make setup-machine-om-gta02''.<br /> <br /> === Making changes ===<br /> <br /> Make changes to an SHR project (e.g. openmoko-dialer3, under the SHR root directory), then under the top directory:<br /> <br /> $ cd shr-unstable<br /> $ . setup-env (only once per session)<br /> $ bitbake -c clean openmoko-dialer3<br /> $ bitbake -c build openmoko-dialer3<br /> <br /> There is no need to check-in the changes to the repo as the system now looks for SHR packages in the local filesystem. The problem is that it is necessary to '''always''' clean the packages so bitbake gets the new changes next time you compile.<br /> <br /> Also, note that we are using ''bitbake -c build'', this is because bitbake needs to do all the necessary steps before compiling (i.e. fetch, unpack, configure...).<br /> <br /> When you are satisfied with your changes and want to create a new SHR image:<br /> <br /> $ make image<br /> <br /> === Updating from other people's changes ===<br /> <br /> Under the top directory:<br /> <br /> $ make update-shr<br /> <br /> Or under the SHR root directory:<br /> <br /> $ svn update<br /> <br /> If you want to update everything (FSO, bitbake and SHR), from the top directory:<br /> <br /> $ make update<br /> <br /> = Old way =<br /> == Building openmoko-dialer3 ==<br /> Currently this is the only package of any size being developed for SHR, and it's the only one with any instructions. If you start another SHR project (please check with [[User:Wurp|Bobby]] before starting one), put instructions for working on the project here!<br /> <br /> === Before beginning ===<br /> You must build openembedded before you can build SHR packages. The easiest way is to go to http://wiki.openmoko.org/wiki/Mokomakefile and build using the instructions for FSO.<br /> <br /> * Note: if building FSO fails using MokoMakefile (zhone! or no dbus show up on the top of the newly booted image), try using this<br /> method: http://wiki.openmoko.org/wiki/FSO<br /> <br /> The rest of these instructions are written assuming that you used Mokomakefile and that the directory you downloaded the base Makefile into (using wget) is $MOKO.<br /> <br /> You must also download the SHR code using subversion. See http://projects.openmoko.org/projects/shr. We will refer to the directory to which you downloaded the project as $SHRSVN. (This directory should contain $SHRSVN/packages/openmoko-dialer3.bb)<br /> <br /> === Set up your BBPATH ===<br /> <br /> export BBPATH=.:$MOKO/openembedded/:$MOKO/bitbake/:$MOKO/:$SHRSVN/trunk/packages/<br /> <br /> === Set up the CACHE ===<br /> <br /> export CACHE=tmp/cache<br /> <br /> === Set up your local.conf ===<br /> <br /> Edit $MOKO/build/conf/local.conf and append the following lines:<br /> BBFILES += &quot;$SHRSVN/trunk/packages/*.bb $MOKO/openembedded/packages/*/*.bb&quot;<br /> SELECTED_OPTIMIZATION = &quot;-Os -g&quot;<br /> <br /> ''Note: Spaces are important in your bitbake conf files! You must have spaces before &amp; after the = or +=''<br /> <br /> (Environment variables, $SHRSVN and $MOKO, can not be used inside local.conf, so absolute paths must be used instead)<br /> <br /> === Set up your openmoko.conf (if using 2007.2) ===<br /> <br /> Edit $MOKO/openembedded/conf/distro/openmoko.conf<br /> <br /> and make sure that these Gtk+ options are set:<br /> <br /> # Select package versions we want to use.<br /> PREFERRED_PROVIDER_gtk+ = &quot;gtk+-fastscaling&quot;<br /> PREFERRED_VERSION_gtk+-fastscaling = &quot;2.10.14&quot;<br /> <br /> <br /> === Add your cross-compiler to your PATH ===<br /> <br /> export PATH=$MOKO/build/tmp/cross/bin/:$MOKO/build/tmp/staging/x86_64-linux/usr/bin:$PATH<br /> <br /> === Run bitbake ===<br /> <br /> (Don't forget to source the setup-env file in the shell before running bitbake)<br /> <br /> bitbake openmoko-dialer3<br /> <br /> After the first time you build successfully, you can build with<br /> <br /> bitbake -b openmoko-dialog3_svn<br /> <br /> which is much faster.<br /> <br /> === To recompile, and only recompile ===<br /> <br /> bitbake -c compile -b $SHRSVN/trunk/packages/openmoko-dialer3.bb<br /> <br /> === Troubleshooting ===<br /> <br /> ==== General ====<br /> One thing to try is to unset all environment variables not listed in this page. LIBPATH and INCLUDE can be particularly troublesome.<br /> <br /> [[Category:SHR]]<br /> [[Category:System Developers]]</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-08-29T14:46:44Z

<p>Wurp: /* Technical Help */</p> <hr /> <div>{{Distributions|SHR}}<br /> {{SHR}}<br /> == Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the [[Openmoko2007.2]] GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br /> <br /> (We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br /> <br /> Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br /> <br /> == Why SHR exists ==<br /> This is long and rambling, and maybe more of a tirade than information, but it does give some background on why this project was started. The overview gives, well, the overview, this is more of a deeper examination of the existing releases and why we felt we needed something new.<br /> <br /> Feel free to skip this whole section if you already think SHR is a good idea :-)<br /> <br /> === Why not ASU? ===<br /> ASU is the distro that OM is putting their main effort into right now. ASU looks very slick, but is very unstable right now, and is likely to be unstable and feature-poor for some time.<br /> <br /> === Why not 2007.2? ===<br /> 2007.2 is the &quot;old&quot; Openmoko distribution, now unsupported. Unsupported == often broken. Also, neither calls nor suspend/resume ever worked reliably.<br /> <br /> === Why not Qtopia? ===<br /> You can also install Qtopia on the phone.<br /> <br /> Qtopia is stable but you can only build qt apps on Qtopia, which means lots of linux apps you might want to port suddenly got a lot harder to port. And some people just don't like developing for qt.<br /> <br /> Also, as far as I know, there is no documented build procedure for Qtopia on Openmoko.<br /> <br /> === Why not FSO? ===<br /> FSO is the initiative by Mickey Lauer and crew to create a good [[D-Bus]] infrastructure which runs on the neos, among other devices.<br /> <br /> FSO is by far the most stable &amp; usable release, if all you want is a phone. (I mean *all*. It just has a dialer right now, not even call history.)<br /> <br /> FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br /> <br /> Other people are supposed to put a front end on FSO. So that's what we're doing.<br /> <br /> === Why SHR? ===<br /> So SHR is FSO, with us doing the necessary work to port the old high-functionality 2007.2 stuff on a stable call platform. We have an adapter from the 2007.2 call service to the FSO call service and we're installing the basic 2007.2 apps on the FSO baseline install.<br /> <br /> In theory, it should be very simple, and should give us dialer, contact management, SMS, terminal, media player, gps app, etc. since all those already work on 2007.2. And the dialer should be stable, which it wasn't in 2007.2<br /> <br /> == First steps ==<br /> The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br /> <br /> We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br /> <br /> == Interest ==<br /> See the Developer Info on the upper right side of the [http://projects.openmoko.org/projects/shr SHR project page].<br /> <br /> == How to join ==<br /> * Send a request to join on the [http://projects.openmoko.org/projects/shr SHR project] on the OM projects page.<br /> * Join [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel shr-devel@lists.projects.openmoko.org] and send an introductory email.<br /> <br /> The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.<br /> <br /> See [[SHR Development]] to find out how to set up your development environment to work on existing SHR packages.<br /> <br /> Hang out in #openmoko-cdevel on chat.freenode.net between 5pm and 11pm GMT to chat with the people developing SHR. (Primarily MarcOChapeau and Ainulindale.)<br /> <br /> == Tasks &amp; status ==<br /> Here's a list of the tasks for the SHR:<br /> {|cellpadding=&quot;6&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |Comment<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space; just need to talk about git branches<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |<br /> |-<br /> |Implement libframeworkd-glib<br /> |alpha. <br /> |[[User:Ainulindale|Ainulindale]]<br /> |<br /> |2008-08-07<br /> |Usable for call purposes / network registration and such.<br /> |-<br /> |port 2007.2 dialer2 (now dialer3) to use ophoned instead<br /> |Pre-Alpha<br /> |[[User:Ainulindale|Ainulindale]]<br /> |MarcOChapeau<br /> |2008-07-28<br /> |<br /> |-<br /> |port 2007.2 gsm-panel apps to use ophoned instead<br /> |Beta<br /> |[[User:Ainulindale|Ainulindale]]<br /> |no one yet<br /> |2008-07-30<br /> |Should be tested regarding the signal strength updates.<br /> |-<br /> |switch media player to use alsa directly<br /> |not started<br /> |[[User:Abraxa|Abraxa]]<br /> |no one yet<br /> |2008-07-30<br /> |<br /> |-<br /> |verify that no other important apps in 2007.2 need ported off of pulseaudio (perhaps by putting all 2007.2 apps (minus pulseaudio) on FSO milestone 2 and verifying which ones still have sound :-)<br /> |not started<br /> |no one yet<br /> |no one yet<br /> |2008-07-30<br /> |<br /> |-<br /> |get neod workalike that uses ophoned to determine if you're on a call<br /> |Pre-Alpha<br /> |No one yet<br /> |no one yet<br /> |2008-07-28<br /> |<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |[[User:Kevin_Dean|Kevin Dean]]<br /> |Nobody<br /> |2008-07-05<br /> |<br /> |-<br /> |[[#List_of_packages_included|Identify packages to go into SHR]]<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Anyone &amp; everyone<br /> |2008-07-12<br /> |<br /> |-<br /> |Identify differences between FSO &amp; 2007.2 that need investigation<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-12<br /> |<br /> |-<br /> |Integrate [http://moko.mwester.net/fixes.html mwester's pulseaudio resume fix] into SHR<br /> |Not started<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-15<br /> |<br /> |-<br /> |Create messages3 as a copy of 2007.2's messages2 and get it compiling (comment out phonekit calls)<br /> |Pre-Alpha<br /> |[[User:Andreas.dalsgaard|AndreasD]]<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |port messages3 to use libframework-glib<br /> |Pre-Alpha<br /> |[[User:Andreas.dalsgaard|AndreasD]]<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |Create contacts3 as a copy of 2007.2's contacts2 and get it compiling (comment out phonekit calls)<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |port contacts3 to use libframework-glib<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |make ophonekitd switch the sound over to gsmhandset when a call is initiated/received<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |port dialer2's journal to dialer3/ophonekitd/libframework-glib<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |}<br /> <br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://projects.openmoko.org/projects/shr/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |fork media player for SHR<br /> |Done!<br /> |2008-08-07<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> == Technical Help ==<br /> <br /> === SVN ===<br /> <br /> We're currently hosted by [[User:Ainulindale|Ainulindale]] on svn://daria.forty-two.fr/shr as projects went down for a whole week-end.<br /> <br /> === Build logic ===<br /> <br /> Current applications (dialer3 and openmoko-panel-gsm) use frameworkd.<br /> So in order to be able to build and test these applications, you have to build frameworkd (MS2) and gsm0710muxd.<br /> <br /> === [[libframeworkd-glib]] ===<br /> <br /> In order to be able to use in an easy way frameworkd, without bothering about dbus calls (which could be difficult for new developers), we built a library allowing everyone to use the functions of frameworkd as if it were simple C functions. We're using asynchronous callbacks for dbus.<br /> <br /> === Architecture ===<br /> SHR uses FSO to interface to the hardware, so see the FSO architecture documentation, too. For how the openmoko*3 applications that SHR forked off 2007.2 access FSO, see http://www.calaquendi.org/om/ophonekitd.png.<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * ophoned<br /> * preferencesd<br /> * pimd<br /> * odeviced<br /> * lots more...<br /> <br /> From 2007.2:<br /> * TODO<br /> * lots more...<br /> <br /> From ASU:<br /> * TODO<br /> * lots more...<br /> <br /> == Project links ==<br /> [http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br /> <br /> == IRC conversation about how we're using revision control ==<br /> <br /> ''This is deprecated, for now we use shr-devel as our only repository. This will change after the first SHR release.''&lt;br/&gt;<br /> From 2007-07-07<br /> &lt;pre&gt;<br /> 12:36 &lt; wurp2&gt; Everything *new* goes on OM projects site<br /> 12:36 &lt; Ainulindale&gt; I totally agree<br /> 12:36 &lt; wurp2&gt; Updates to 2007.2 apps go back into the home svn<br /> 12:36 &lt; Ainulindale&gt; paulproteus: no, you're an external cabal all by yourself<br /> :-)<br /> 12:36 &lt; cb22&gt; anyone planning on drawing up a roadmap?<br /> 12:36 &lt; paulproteus&gt; cb22, We can do that in Trac in fact.<br /> 12:36 &lt; wurp2&gt; And changes to the underlying release go as patches into our OE<br /> branch, yes?<br /> 12:36 &lt; paulproteus&gt; (or on the wiki page)<br /> 12:36 &lt; paulproteus&gt; wurp2, Right<br /> 12:36 &lt; paulproteus&gt; mwester, Sanity-check my terminology where I mess things<br /> up!<br /> 12:37 &lt; Ainulindale&gt; hmmm fuzzy for me but what should go in OM and what should<br /> go in OE ?<br /> 12:37 &lt;@mwester&gt; Sure<br /> 12:37 &lt;@mwester&gt; What do you mean by OM?<br /> 12:37 &lt; paulproteus&gt; Ainulindale, New software we write goes in the<br /> projects.openmoko.org.<br /> 12:37 &lt;@mwester&gt; right.<br /> 12:37 &lt; Ainulindale&gt; Ok so the wrapper for example<br /> 12:37 &lt; wurp2&gt; Anything stand-alone goes in OM (projects.openmoko.org)<br /> 12:37 &lt; wurp2&gt; yeah<br /> 12:37 &lt;@mwester&gt; So we will use projects.openmoko.org for as much as we can,<br /> and OE to build the distro.<br /> 12:37 &lt; Ainulindale&gt; Sounds right to me<br /> 12:37 &lt; wurp2&gt; Great!<br /> 12:38 &lt;@mwester&gt; We *will not* use the OM git repo, as that is owned and<br /> controlled by Openmoko the company...<br /> &lt;/pre&gt;<br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]<br /> [[Category:SHR]]</div>

Wurp http://wiki.openmoko.org/wiki/SHR_Development 2008-08-28T21:38:12Z

<p>Wurp: Add outline of mokomakefile build process</p> <hr /> <div>{{SHR}}<br /> = New way (using MokoMakefile) =<br /> Thanks to Aleix, There is a new (much simpler) way to build SHR that is under construction right now.<br /> <br /> === First build ===<br /> * Install MokoMakefile<br /> * make setup<br /> * make shr-image<br /> <br /> === Making changes ===<br /> * cd into the directory for the project you wish to change (e.g. openmoko-dialer3)<br /> * bitbake -c clean openmoko-dialer3<br /> * bitbake -c compile openmoko-dialer3<br /> * make shr-image<br /> <br /> === Updating from other people's changes ===<br /> * svn update in the SHR root directory<br /> * make shr-image<br /> <br /> = Old way =<br /> == Building openmoko-dialer3 ==<br /> Currently this is the only package of any size being developed for SHR, and it's the only one with any instructions. If you start another SHR project (please check with [[User:Wurp|Bobby]] before starting one), put instructions for working on the project here!<br /> <br /> === Before beginning ===<br /> You must build openembedded before you can build SHR packages. The easiest way is to go to http://wiki.openmoko.org/wiki/Mokomakefile and build using the instructions for FSO.<br /> <br /> * Note: if building FSO fails using MokoMakefile (zhone! or no dbus show up on the top of the newly booted image), try using this<br /> method: http://wiki.openmoko.org/wiki/FSO<br /> <br /> The rest of these instructions are written assuming that you used Mokomakefile and that the directory you downloaded the base Makefile into (using wget) is $MOKO.<br /> <br /> You must also download the SHR code using subversion. See http://projects.openmoko.org/projects/shr. We will refer to the directory to which you downloaded the project as $SHRSVN. (This directory should contain $SHRSVN/packages/openmoko-dialer3.bb)<br /> <br /> === Set up your BBPATH ===<br /> <br /> export BBPATH=.:$MOKO/openembedded/:$MOKO/bitbake/:$MOKO/:$SHRSVN/trunk/packages/<br /> <br /> === Set up the CACHE ===<br /> <br /> export CACHE=tmp/cache<br /> <br /> === Set up your local.conf ===<br /> <br /> Edit $MOKO/build/conf/local.conf and append the following lines:<br /> BBFILES += &quot;$SHRSVN/trunk/packages/*.bb $MOKO/openembedded/packages/*/*.bb&quot;<br /> SELECTED_OPTIMIZATION = &quot;-Os -g&quot;<br /> <br /> ''Note: Spaces are important in your bitbake conf files! You must have spaces before &amp; after the = or +=''<br /> <br /> (Environment variables, $SHRSVN and $MOKO, can not be used inside local.conf, so absolute paths must be used instead)<br /> <br /> === Set up your openmoko.conf (if using 2007.2) ===<br /> <br /> Edit $MOKO/openembedded/conf/distro/openmoko.conf<br /> <br /> and make sure that these Gtk+ options are set:<br /> <br /> # Select package versions we want to use.<br /> PREFERRED_PROVIDER_gtk+ = &quot;gtk+-fastscaling&quot;<br /> PREFERRED_VERSION_gtk+-fastscaling = &quot;2.10.14&quot;<br /> <br /> <br /> === Add your cross-compiler to your PATH ===<br /> <br /> export PATH=$MOKO/build/tmp/cross/bin/:$MOKO/build/tmp/staging/x86_64-linux/usr/bin:$PATH<br /> <br /> === Run bitbake ===<br /> <br /> (Don't forget to source the setup-env file in the shell before running bitbake)<br /> <br /> bitbake openmoko-dialer3<br /> <br /> After the first time you build successfully, you can build with<br /> <br /> bitbake -b openmoko-dialog3_svn<br /> <br /> which is much faster.<br /> <br /> === To recompile, and only recompile ===<br /> <br /> bitbake -c compile -b $SHRSVN/trunk/packages/openmoko-dialer3.bb<br /> <br /> === Troubleshooting ===<br /> <br /> ==== General ====<br /> One thing to try is to unset all environment variables not listed in this page. LIBPATH and INCLUDE can be particularly troublesome.<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]<br /> [[Category:SHR]]<br /> [[Category:SHR Devel]]</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-08-28T20:38:00Z

<p>Wurp: /* How to join */</p> <hr /> <div>{{Distributions|SHR}}<br /> {{SHR}}<br /> == Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the [[Openmoko2007.2]] GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br /> <br /> (We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br /> <br /> Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br /> <br /> == Why SHR exists ==<br /> This is long and rambling, and maybe more of a tirade than information, but it does give some background on why this project was started. The overview gives, well, the overview, this is more of a deeper examination of the existing releases and why we felt we needed something new.<br /> <br /> Feel free to skip this whole section if you already think SHR is a good idea :-)<br /> <br /> === Why not ASU? ===<br /> ASU is the distro that OM is putting their main effort into right now. ASU looks very slick, but is very unstable right now, and is likely to be unstable and feature-poor for some time.<br /> <br /> === Why not 2007.2? ===<br /> 2007.2 is the &quot;old&quot; Openmoko distribution, now unsupported. Unsupported == often broken. Also, neither calls nor suspend/resume ever worked reliably.<br /> <br /> === Why not Qtopia? ===<br /> You can also install Qtopia on the phone.<br /> <br /> Qtopia is stable but you can only build qt apps on Qtopia, which means lots of linux apps you might want to port suddenly got a lot harder to port. And some people just don't like developing for qt.<br /> <br /> Also, as far as I know, there is no documented build procedure for Qtopia on Openmoko.<br /> <br /> === Why not FSO? ===<br /> FSO is the initiative by Mickey Lauer and crew to create a good [[D-Bus]] infrastructure which runs on the neos, among other devices.<br /> <br /> FSO is by far the most stable &amp; usable release, if all you want is a phone. (I mean *all*. It just has a dialer right now, not even call history.)<br /> <br /> FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br /> <br /> Other people are supposed to put a front end on FSO. So that's what we're doing.<br /> <br /> === Why SHR? ===<br /> So SHR is FSO, with us doing the necessary work to port the old high-functionality 2007.2 stuff on a stable call platform. We have an adapter from the 2007.2 call service to the FSO call service and we're installing the basic 2007.2 apps on the FSO baseline install.<br /> <br /> In theory, it should be very simple, and should give us dialer, contact management, SMS, terminal, media player, gps app, etc. since all those already work on 2007.2. And the dialer should be stable, which it wasn't in 2007.2<br /> <br /> == First steps ==<br /> The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br /> <br /> We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br /> <br /> == Interest ==<br /> See the Developer Info on the upper right side of the [http://projects.openmoko.org/projects/shr SHR project page].<br /> <br /> == How to join ==<br /> * Send a request to join on the [http://projects.openmoko.org/projects/shr SHR project] on the OM projects page.<br /> * Join [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel shr-devel@lists.projects.openmoko.org] and send an introductory email.<br /> <br /> The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.<br /> <br /> See [[SHR Development]] to find out how to set up your development environment to work on existing SHR packages.<br /> <br /> Hang out in #openmoko-cdevel on chat.freenode.net between 5pm and 11pm GMT to chat with the people developing SHR. (Primarily MarcOChapeau and Ainulindale.)<br /> <br /> == Tasks &amp; status ==<br /> Here's a list of the tasks for the SHR:<br /> {|cellpadding=&quot;6&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |Comment<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space; just need to talk about git branches<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |<br /> |-<br /> |Implement libframeworkd-glib<br /> |alpha. <br /> |[[User:Ainulindale|Ainulindale]]<br /> |<br /> |2008-08-07<br /> |Usable for call purposes / network registration and such.<br /> |-<br /> |port 2007.2 dialer2 (now dialer3) to use ophoned instead<br /> |Pre-Alpha<br /> |[[User:Ainulindale|Ainulindale]]<br /> |MarcOChapeau<br /> |2008-07-28<br /> |<br /> |-<br /> |port 2007.2 gsm-panel apps to use ophoned instead<br /> |Beta<br /> |[[User:Ainulindale|Ainulindale]]<br /> |no one yet<br /> |2008-07-30<br /> |Should be tested regarding the signal strength updates.<br /> |-<br /> |switch media player to use alsa directly<br /> |not started<br /> |[[User:Abraxa|Abraxa]]<br /> |no one yet<br /> |2008-07-30<br /> |<br /> |-<br /> |verify that no other important apps in 2007.2 need ported off of pulseaudio (perhaps by putting all 2007.2 apps (minus pulseaudio) on FSO milestone 2 and verifying which ones still have sound :-)<br /> |not started<br /> |no one yet<br /> |no one yet<br /> |2008-07-30<br /> |<br /> |-<br /> |get neod workalike that uses ophoned to determine if you're on a call<br /> |Pre-Alpha<br /> |No one yet<br /> |no one yet<br /> |2008-07-28<br /> |<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |[[User:Kevin_Dean|Kevin Dean]]<br /> |Nobody<br /> |2008-07-05<br /> |<br /> |-<br /> |[[#List_of_packages_included|Identify packages to go into SHR]]<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Anyone &amp; everyone<br /> |2008-07-12<br /> |<br /> |-<br /> |Identify differences between FSO &amp; 2007.2 that need investigation<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-12<br /> |<br /> |-<br /> |Integrate [http://moko.mwester.net/fixes.html mwester's pulseaudio resume fix] into SHR<br /> |Not started<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-15<br /> |<br /> |-<br /> |Create messages3 as a copy of 2007.2's messages2 and get it compiling (comment out phonekit calls)<br /> |Pre-Alpha<br /> |[[User:Andreas.dalsgaard|AndreasD]]<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |port messages3 to use libframework-glib<br /> |Pre-Alpha<br /> |[[User:Andreas.dalsgaard|AndreasD]]<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |Create contacts3 as a copy of 2007.2's contacts2 and get it compiling (comment out phonekit calls)<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |port contacts3 to use libframework-glib<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |make ophonekitd switch the sound over to gsmhandset when a call is initiated/received<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |port dialer2's journal to dialer3/ophonekitd/libframework-glib<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |}<br /> <br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |fork media player for SHR<br /> |Done!<br /> |2008-08-07<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> == Technical Help ==<br /> <br /> === SVN ===<br /> <br /> We're currently hosted by [[User:Ainulindale|Ainulindale]] on svn://daria.forty-two.fr/shr as projects went down for a whole week-end.<br /> <br /> === Build logic ===<br /> <br /> Current applications (dialer3 and openmoko-panel-gsm) use frameworkd.<br /> So in order to be able to build and test these applications, you have to build frameworkd (MS2) and gsm0710muxd.<br /> <br /> === [[libframeworkd-glib]] ===<br /> <br /> In order to be able to use in an easy way frameworkd, without bothering about dbus calls (which could be difficult for new developers), we built a library allowing everyone to use the functions of frameworkd as if it were simple C functions. We're using asynchronous callbacks for dbus.<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * ophoned<br /> * preferencesd<br /> * pimd<br /> * odeviced<br /> * lots more...<br /> <br /> From 2007.2:<br /> * TODO<br /> * lots more...<br /> <br /> From ASU:<br /> * TODO<br /> * lots more...<br /> <br /> == Project links ==<br /> [http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br /> <br /> == IRC conversation about how we're using revision control ==<br /> <br /> ''This is deprecated, for now we use shr-devel as our only repository. This will change after the first SHR release.''&lt;br/&gt;<br /> From 2007-07-07<br /> &lt;pre&gt;<br /> 12:36 &lt; wurp2&gt; Everything *new* goes on OM projects site<br /> 12:36 &lt; Ainulindale&gt; I totally agree<br /> 12:36 &lt; wurp2&gt; Updates to 2007.2 apps go back into the home svn<br /> 12:36 &lt; Ainulindale&gt; paulproteus: no, you're an external cabal all by yourself<br /> :-)<br /> 12:36 &lt; cb22&gt; anyone planning on drawing up a roadmap?<br /> 12:36 &lt; paulproteus&gt; cb22, We can do that in Trac in fact.<br /> 12:36 &lt; wurp2&gt; And changes to the underlying release go as patches into our OE<br /> branch, yes?<br /> 12:36 &lt; paulproteus&gt; (or on the wiki page)<br /> 12:36 &lt; paulproteus&gt; wurp2, Right<br /> 12:36 &lt; paulproteus&gt; mwester, Sanity-check my terminology where I mess things<br /> up!<br /> 12:37 &lt; Ainulindale&gt; hmmm fuzzy for me but what should go in OM and what should<br /> go in OE ?<br /> 12:37 &lt;@mwester&gt; Sure<br /> 12:37 &lt;@mwester&gt; What do you mean by OM?<br /> 12:37 &lt; paulproteus&gt; Ainulindale, New software we write goes in the<br /> projects.openmoko.org.<br /> 12:37 &lt;@mwester&gt; right.<br /> 12:37 &lt; Ainulindale&gt; Ok so the wrapper for example<br /> 12:37 &lt; wurp2&gt; Anything stand-alone goes in OM (projects.openmoko.org)<br /> 12:37 &lt; wurp2&gt; yeah<br /> 12:37 &lt;@mwester&gt; So we will use projects.openmoko.org for as much as we can,<br /> and OE to build the distro.<br /> 12:37 &lt; Ainulindale&gt; Sounds right to me<br /> 12:37 &lt; wurp2&gt; Great!<br /> 12:38 &lt;@mwester&gt; We *will not* use the OM git repo, as that is owned and<br /> controlled by Openmoko the company...<br /> &lt;/pre&gt;<br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]<br /> [[Category:SHR]]</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-08-28T20:37:18Z

<p>Wurp: /* Interest */</p> <hr /> <div>{{Distributions|SHR}}<br /> {{SHR}}<br /> == Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the [[Openmoko2007.2]] GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br /> <br /> (We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br /> <br /> Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br /> <br /> == Why SHR exists ==<br /> This is long and rambling, and maybe more of a tirade than information, but it does give some background on why this project was started. The overview gives, well, the overview, this is more of a deeper examination of the existing releases and why we felt we needed something new.<br /> <br /> Feel free to skip this whole section if you already think SHR is a good idea :-)<br /> <br /> === Why not ASU? ===<br /> ASU is the distro that OM is putting their main effort into right now. ASU looks very slick, but is very unstable right now, and is likely to be unstable and feature-poor for some time.<br /> <br /> === Why not 2007.2? ===<br /> 2007.2 is the &quot;old&quot; Openmoko distribution, now unsupported. Unsupported == often broken. Also, neither calls nor suspend/resume ever worked reliably.<br /> <br /> === Why not Qtopia? ===<br /> You can also install Qtopia on the phone.<br /> <br /> Qtopia is stable but you can only build qt apps on Qtopia, which means lots of linux apps you might want to port suddenly got a lot harder to port. And some people just don't like developing for qt.<br /> <br /> Also, as far as I know, there is no documented build procedure for Qtopia on Openmoko.<br /> <br /> === Why not FSO? ===<br /> FSO is the initiative by Mickey Lauer and crew to create a good [[D-Bus]] infrastructure which runs on the neos, among other devices.<br /> <br /> FSO is by far the most stable &amp; usable release, if all you want is a phone. (I mean *all*. It just has a dialer right now, not even call history.)<br /> <br /> FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br /> <br /> Other people are supposed to put a front end on FSO. So that's what we're doing.<br /> <br /> === Why SHR? ===<br /> So SHR is FSO, with us doing the necessary work to port the old high-functionality 2007.2 stuff on a stable call platform. We have an adapter from the 2007.2 call service to the FSO call service and we're installing the basic 2007.2 apps on the FSO baseline install.<br /> <br /> In theory, it should be very simple, and should give us dialer, contact management, SMS, terminal, media player, gps app, etc. since all those already work on 2007.2. And the dialer should be stable, which it wasn't in 2007.2<br /> <br /> == First steps ==<br /> The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br /> <br /> We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br /> <br /> == Interest ==<br /> See the Developer Info on the upper right side of the [http://projects.openmoko.org/projects/shr SHR project page].<br /> <br /> == How to join ==<br /> * Please add your name (with a link to your user page) to the list above.<br /> * You should also send a request to join on the [http://projects.openmoko.org/projects/shr SHR project] on the OM projects page to join.<br /> * Join [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel shr-devel@lists.projects.openmoko.org] and send an introductory email.<br /> <br /> The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.<br /> <br /> See [[SHR Development]] to find out how to set up your development environment to work on existing SHR packages.<br /> <br /> Hang out in #openmoko-cdevel on chat.freenode.net between 5pm and 11pm GMT to chat with the people developing SHR. (Primarily MarcOChapeau and Ainulindale.)<br /> <br /> == Tasks &amp; status ==<br /> Here's a list of the tasks for the SHR:<br /> {|cellpadding=&quot;6&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |Comment<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space; just need to talk about git branches<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |<br /> |-<br /> |Implement libframeworkd-glib<br /> |alpha. <br /> |[[User:Ainulindale|Ainulindale]]<br /> |<br /> |2008-08-07<br /> |Usable for call purposes / network registration and such.<br /> |-<br /> |port 2007.2 dialer2 (now dialer3) to use ophoned instead<br /> |Pre-Alpha<br /> |[[User:Ainulindale|Ainulindale]]<br /> |MarcOChapeau<br /> |2008-07-28<br /> |<br /> |-<br /> |port 2007.2 gsm-panel apps to use ophoned instead<br /> |Beta<br /> |[[User:Ainulindale|Ainulindale]]<br /> |no one yet<br /> |2008-07-30<br /> |Should be tested regarding the signal strength updates.<br /> |-<br /> |switch media player to use alsa directly<br /> |not started<br /> |[[User:Abraxa|Abraxa]]<br /> |no one yet<br /> |2008-07-30<br /> |<br /> |-<br /> |verify that no other important apps in 2007.2 need ported off of pulseaudio (perhaps by putting all 2007.2 apps (minus pulseaudio) on FSO milestone 2 and verifying which ones still have sound :-)<br /> |not started<br /> |no one yet<br /> |no one yet<br /> |2008-07-30<br /> |<br /> |-<br /> |get neod workalike that uses ophoned to determine if you're on a call<br /> |Pre-Alpha<br /> |No one yet<br /> |no one yet<br /> |2008-07-28<br /> |<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |[[User:Kevin_Dean|Kevin Dean]]<br /> |Nobody<br /> |2008-07-05<br /> |<br /> |-<br /> |[[#List_of_packages_included|Identify packages to go into SHR]]<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Anyone &amp; everyone<br /> |2008-07-12<br /> |<br /> |-<br /> |Identify differences between FSO &amp; 2007.2 that need investigation<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-12<br /> |<br /> |-<br /> |Integrate [http://moko.mwester.net/fixes.html mwester's pulseaudio resume fix] into SHR<br /> |Not started<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-15<br /> |<br /> |-<br /> |Create messages3 as a copy of 2007.2's messages2 and get it compiling (comment out phonekit calls)<br /> |Pre-Alpha<br /> |[[User:Andreas.dalsgaard|AndreasD]]<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |port messages3 to use libframework-glib<br /> |Pre-Alpha<br /> |[[User:Andreas.dalsgaard|AndreasD]]<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |Create contacts3 as a copy of 2007.2's contacts2 and get it compiling (comment out phonekit calls)<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |port contacts3 to use libframework-glib<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |make ophonekitd switch the sound over to gsmhandset when a call is initiated/received<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |port dialer2's journal to dialer3/ophonekitd/libframework-glib<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |}<br /> <br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |fork media player for SHR<br /> |Done!<br /> |2008-08-07<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> == Technical Help ==<br /> <br /> === SVN ===<br /> <br /> We're currently hosted by [[User:Ainulindale|Ainulindale]] on svn://daria.forty-two.fr/shr as projects went down for a whole week-end.<br /> <br /> === Build logic ===<br /> <br /> Current applications (dialer3 and openmoko-panel-gsm) use frameworkd.<br /> So in order to be able to build and test these applications, you have to build frameworkd (MS2) and gsm0710muxd.<br /> <br /> === [[libframeworkd-glib]] ===<br /> <br /> In order to be able to use in an easy way frameworkd, without bothering about dbus calls (which could be difficult for new developers), we built a library allowing everyone to use the functions of frameworkd as if it were simple C functions. We're using asynchronous callbacks for dbus.<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * ophoned<br /> * preferencesd<br /> * pimd<br /> * odeviced<br /> * lots more...<br /> <br /> From 2007.2:<br /> * TODO<br /> * lots more...<br /> <br /> From ASU:<br /> * TODO<br /> * lots more...<br /> <br /> == Project links ==<br /> [http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br /> <br /> == IRC conversation about how we're using revision control ==<br /> <br /> ''This is deprecated, for now we use shr-devel as our only repository. This will change after the first SHR release.''&lt;br/&gt;<br /> From 2007-07-07<br /> &lt;pre&gt;<br /> 12:36 &lt; wurp2&gt; Everything *new* goes on OM projects site<br /> 12:36 &lt; Ainulindale&gt; I totally agree<br /> 12:36 &lt; wurp2&gt; Updates to 2007.2 apps go back into the home svn<br /> 12:36 &lt; Ainulindale&gt; paulproteus: no, you're an external cabal all by yourself<br /> :-)<br /> 12:36 &lt; cb22&gt; anyone planning on drawing up a roadmap?<br /> 12:36 &lt; paulproteus&gt; cb22, We can do that in Trac in fact.<br /> 12:36 &lt; wurp2&gt; And changes to the underlying release go as patches into our OE<br /> branch, yes?<br /> 12:36 &lt; paulproteus&gt; (or on the wiki page)<br /> 12:36 &lt; paulproteus&gt; wurp2, Right<br /> 12:36 &lt; paulproteus&gt; mwester, Sanity-check my terminology where I mess things<br /> up!<br /> 12:37 &lt; Ainulindale&gt; hmmm fuzzy for me but what should go in OM and what should<br /> go in OE ?<br /> 12:37 &lt;@mwester&gt; Sure<br /> 12:37 &lt;@mwester&gt; What do you mean by OM?<br /> 12:37 &lt; paulproteus&gt; Ainulindale, New software we write goes in the<br /> projects.openmoko.org.<br /> 12:37 &lt;@mwester&gt; right.<br /> 12:37 &lt; Ainulindale&gt; Ok so the wrapper for example<br /> 12:37 &lt; wurp2&gt; Anything stand-alone goes in OM (projects.openmoko.org)<br /> 12:37 &lt; wurp2&gt; yeah<br /> 12:37 &lt;@mwester&gt; So we will use projects.openmoko.org for as much as we can,<br /> and OE to build the distro.<br /> 12:37 &lt; Ainulindale&gt; Sounds right to me<br /> 12:37 &lt; wurp2&gt; Great!<br /> 12:38 &lt;@mwester&gt; We *will not* use the OM git repo, as that is owned and<br /> controlled by Openmoko the company...<br /> &lt;/pre&gt;<br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]<br /> [[Category:SHR]]</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-08-19T22:36:01Z

<p>Wurp: /* Tasks &amp; status */</p> <hr /> <div>{{Distributions|SHR}}<br /> {{SHR}}<br /> == Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the [[Openmoko2007.2]] GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br /> <br /> (We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br /> <br /> Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br /> <br /> == Why SHR exists ==<br /> This is long and rambling, and maybe more of a tirade than information, but it does give some background on why this project was started. The overview gives, well, the overview, this is more of a deeper examination of the existing releases and why we felt we needed something new.<br /> <br /> Feel free to skip this whole section if you already think SHR is a good idea :-)<br /> <br /> === Why not ASU? ===<br /> ASU is the distro that OM is putting their main effort into right now. ASU looks very slick, but is very unstable right now, and is likely to be unstable and feature-poor for some time.<br /> <br /> === Why not 2007.2? ===<br /> 2007.2 is the &quot;old&quot; Openmoko distribution, now unsupported. Unsupported == often broken. Also, neither calls nor suspend/resume ever worked reliably.<br /> <br /> === Why not Qtopia? ===<br /> You can also install Qtopia on the phone.<br /> <br /> Qtopia is stable but you can only build qt apps on Qtopia, which means lots of linux apps you might want to port suddenly got a lot harder to port. And some people just don't like developing for qt.<br /> <br /> Also, as far as I know, there is no documented build procedure for Qtopia on Openmoko.<br /> <br /> === Why not FSO? ===<br /> FSO is the initiative by Mickey Lauer and crew to create a good [[D-Bus]] infrastructure which runs on the neos, among other devices.<br /> <br /> FSO is by far the most stable &amp; usable release, if all you want is a phone. (I mean *all*. It just has a dialer right now, not even call history.)<br /> <br /> FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br /> <br /> Other people are supposed to put a front end on FSO. So that's what we're doing.<br /> <br /> === Why SHR? ===<br /> So SHR is FSO, with us doing the necessary work to port the old high-functionality 2007.2 stuff on a stable call platform. We have an adapter from the 2007.2 call service to the FSO call service and we're installing the basic 2007.2 apps on the FSO baseline install.<br /> <br /> In theory, it should be very simple, and should give us dialer, contact management, SMS, terminal, media player, gps app, etc. since all those already work on 2007.2. And the dialer should be stable, which it wasn't in 2007.2<br /> <br /> == First steps ==<br /> The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br /> <br /> We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br /> <br /> == Interest ==<br /> Here's a list of people who've expressed an interest in working on the SHR.<br /> <br /> * [[User:Wurp|wurp2]]<br /> * [[User:Ferric|ferric]]<br /> * [[User:Paulproteus|paulproteus]]<br /> * [[User:Ainulindale|Ainulindale]]<br /> * [[User:jluis|Jose Luis]]<br /> * [[User:Kevin_Dean|Kevin Dean]]<br /> * [[User:Cb22|cb22]]<br /> * [[User:Jeremy-list|Jeremy List]]<br /> * mwester<br /> * [[User:MarcOChapeau|MarcO'Chapeau]]<br /> * [[User:kd8ikt|kd8ikt]]<br /> * [[User:Mywave|Mywave]]<br /> * [[User:nigelTheBold|Anthony Taylor]]<br /> * [[User:Pwgen|Eric Weiss]]<br /> * [[User:Andre613|Andre Racicot]]<br /> * [[User:Pyknite|Pyknite]]<br /> <br /> == How to join ==<br /> * Please add your name (with a link to your user page) to the list above.<br /> * You should also send a request to join on the [http://projects.openmoko.org/projects/shr SHR project] on the OM projects page to join.<br /> * Join [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel shr-devel@lists.projects.openmoko.org] and send an introductory email.<br /> <br /> The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.<br /> <br /> See [[SHR Development]] to find out how to set up your development environment to work on existing SHR packages.<br /> <br /> Hang out in #openmoko-cdevel on chat.freenode.net between 5pm and 11pm GMT to chat with the people developing SHR. (Primarily MarcOChapeau and Ainulindale.)<br /> <br /> == Tasks &amp; status ==<br /> Here's a list of the tasks for the SHR:<br /> {|cellpadding=&quot;6&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |Comment<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space; just need to talk about git branches<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |<br /> |-<br /> |Implement libframeworkd-glib<br /> |alpha. <br /> |[[User:Ainulindale|Ainulindale]]<br /> |<br /> |2008-08-07<br /> |Usable for call purposes / network registration and such.<br /> |-<br /> |port 2007.2 dialer2 (now dialer3) to use ophoned instead<br /> |Pre-Alpha<br /> |[[User:Ainulindale|Ainulindale]]<br /> |MarcOChapeau<br /> |2008-07-28<br /> |<br /> |-<br /> |port 2007.2 gsm-panel apps to use ophoned instead<br /> |Beta<br /> |[[User:Ainulindale|Ainulindale]]<br /> |no one yet<br /> |2008-07-30<br /> |Should be tested regarding the signal strength updates.<br /> |-<br /> |switch media player to use alsa directly<br /> |not started<br /> |[[User:Abraxa|Abraxa]]<br /> |no one yet<br /> |2008-07-30<br /> |<br /> |-<br /> |verify that no other important apps in 2007.2 need ported off of pulseaudio (perhaps by putting all 2007.2 apps (minus pulseaudio) on FSO milestone 2 and verifying which ones still have sound :-)<br /> |not started<br /> |no one yet<br /> |no one yet<br /> |2008-07-30<br /> |<br /> |-<br /> |get neod workalike that uses ophoned to determine if you're on a call<br /> |Pre-Alpha<br /> |No one yet<br /> |no one yet<br /> |2008-07-28<br /> |<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |[[User:Kevin_Dean|Kevin Dean]]<br /> |Nobody<br /> |2008-07-05<br /> |<br /> |-<br /> |[[#List_of_packages_included|Identify packages to go into SHR]]<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Anyone &amp; everyone<br /> |2008-07-12<br /> |<br /> |-<br /> |Identify differences between FSO &amp; 2007.2 that need investigation<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-12<br /> |<br /> |-<br /> |Integrate [http://moko.mwester.net/fixes.html mwester's pulseaudio resume fix] into SHR<br /> |Not started<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-15<br /> |<br /> |-<br /> |Create messages3 as a copy of 2007.2's messages2 and get it compiling (comment out phonekit calls)<br /> |Pre-Alpha<br /> |[[User:Andreas.dalsgaard|AndreasD]]<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |port messages3 to use libframework-glib<br /> |Pre-Alpha<br /> |[[User:Andreas.dalsgaard|AndreasD]]<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |Create contacts3 as a copy of 2007.2's contacts2 and get it compiling (comment out phonekit calls)<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |port contacts3 to use libframework-glib<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |make ophonekitd switch the sound over to gsmhandset when a call is initiated/received<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |port dialer2's journal to dialer3/ophonekitd/libframework-glib<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |}<br /> <br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |fork media player for SHR<br /> |Done!<br /> |2008-08-07<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> == Technical Help ==<br /> <br /> === SVN ===<br /> <br /> We're currently hosted by [[User:Ainulindale|Ainulindale]] on svn://daria.forty-two.fr/shr as projects went down for a whole week-end.<br /> <br /> === Build logic ===<br /> <br /> Current applications (dialer3 and openmoko-panel-gsm) use frameworkd.<br /> So in order to be able to build and test these applications, you have to build frameworkd (MS2) and gsm0710muxd.<br /> <br /> === [[libframeworkd-glib]] ===<br /> <br /> In order to be able to use in an easy way frameworkd, without bothering about dbus calls (which could be difficult for new developers), we built a library allowing everyone to use the functions of frameworkd as if it were simple C functions. We're using asynchronous callbacks for dbus.<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * ophoned<br /> * preferencesd<br /> * pimd<br /> * odeviced<br /> * lots more...<br /> <br /> From 2007.2:<br /> * TODO<br /> * lots more...<br /> <br /> From ASU:<br /> * TODO<br /> * lots more...<br /> <br /> == Project links ==<br /> [http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br /> <br /> == IRC conversation about how we're using revision control ==<br /> <br /> ''This is deprecated, for now we use shr-devel as our only repository. This will change after the first SHR release.''&lt;br/&gt;<br /> From 2007-07-07<br /> &lt;pre&gt;<br /> 12:36 &lt; wurp2&gt; Everything *new* goes on OM projects site<br /> 12:36 &lt; Ainulindale&gt; I totally agree<br /> 12:36 &lt; wurp2&gt; Updates to 2007.2 apps go back into the home svn<br /> 12:36 &lt; Ainulindale&gt; paulproteus: no, you're an external cabal all by yourself<br /> :-)<br /> 12:36 &lt; cb22&gt; anyone planning on drawing up a roadmap?<br /> 12:36 &lt; paulproteus&gt; cb22, We can do that in Trac in fact.<br /> 12:36 &lt; wurp2&gt; And changes to the underlying release go as patches into our OE<br /> branch, yes?<br /> 12:36 &lt; paulproteus&gt; (or on the wiki page)<br /> 12:36 &lt; paulproteus&gt; wurp2, Right<br /> 12:36 &lt; paulproteus&gt; mwester, Sanity-check my terminology where I mess things<br /> up!<br /> 12:37 &lt; Ainulindale&gt; hmmm fuzzy for me but what should go in OM and what should<br /> go in OE ?<br /> 12:37 &lt;@mwester&gt; Sure<br /> 12:37 &lt;@mwester&gt; What do you mean by OM?<br /> 12:37 &lt; paulproteus&gt; Ainulindale, New software we write goes in the<br /> projects.openmoko.org.<br /> 12:37 &lt;@mwester&gt; right.<br /> 12:37 &lt; Ainulindale&gt; Ok so the wrapper for example<br /> 12:37 &lt; wurp2&gt; Anything stand-alone goes in OM (projects.openmoko.org)<br /> 12:37 &lt; wurp2&gt; yeah<br /> 12:37 &lt;@mwester&gt; So we will use projects.openmoko.org for as much as we can,<br /> and OE to build the distro.<br /> 12:37 &lt; Ainulindale&gt; Sounds right to me<br /> 12:37 &lt; wurp2&gt; Great!<br /> 12:38 &lt;@mwester&gt; We *will not* use the OM git repo, as that is owned and<br /> controlled by Openmoko the company...<br /> &lt;/pre&gt;<br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]<br /> [[Category:SHR]]</div>

Wurp http://wiki.openmoko.org/wiki/Wish_List 2008-08-08T18:17:19Z

<p>Wurp: /* Media */</p> <hr /> <div>This article is a place to collect various thoughts about the future of the [[OpenMoko]] software platform. Most wish list ideas have been linked from this page, but you may also wish to check all pages [[:Category:Ideas|that have a category of 'Ideas']].<br /> <br /> == Development ==<br /> === Painless SDK installation &amp; Setup ===<br /> Our goal should be a completely painless setup for somebody wanting to develop using [[OpenMoko]]<br /> <br /> * one command for installation (apt-get install openmoko)<br /> * one command to start Xnest (openmoko-xephyr?)<br /> * one command to start an i386 shell (openmoko-386-shell)<br /> * one command to start an armel shell (openmoko-armel-shell)<br /> <br /> No extra configuration required.<br /> <br /> ==== IDE Plugins ====<br /> People like to see plugins for<br /> * [http://anjuta.sourceforge.net Anjuta]<br /> * [http://www.eclipse.org Eclipse] (some things are possible - see [[Development with Eclipse]].<br /> * [http://www.netbeans.org NetBeans]<br /> * Game engine - Game Creation plugins<br /> evaluate eclipse project [http://www.eclipse.org/dsdp/index.php Device Software Development Platform Project from eclipse] and subproject [http://www.eclipse.org/proposals/tml/ Tool for Mobile Linux]<br /> * [http://www.kdevelop.org KDevelop]<br /> * [http://developer.apple.com/tools/xcode/ XCode]<br /> * [http://www.monodevelop.com MonoDevelop]<br /> * [http://msdn.microsoft.com/vstudio/ Microsoft Visual Studio 2005]<br /> <br /> ==== UI Designer ====<br /> Glade code generation is deprecated, so we don't want to use it. The Gtk+ powers told me that the plan is to have gtk 2.12 (out early 2007) with support for GtkBuilder, a libglade derivative which breaks a bit the XML definition in order to support all the new widgets and properties; as soon as it's in the other ui builders will add support for this format. See also [http://bugzilla.gnome.org/show_bug.cgi?id=172535 the relevant bug entry]<br /> * Possibly a Landscape (rotated) view for the screen (480x640 *or* 640x480)?<br /> <br /> <br /> ==== Built-in Scripting Language ====<br /> {{Main|Wishlist:BuiltInScriptingLanguage}}<br /> There was a [http://lists.openmoko.org/pipermail/community/2007-January/001909.html fruitful discussion about a built-in scripting language on the mailing list in January.] Many people feel that it is very important for OpenMoko to choose a scripting language to ship as default in the standard OpenMoko firmware.<br /> ==== Easy build of the existing autotools - based packages ====<br /> In the ideal case OpenMoko should exist on the top of the usual ./configure - make workflow which is typical for the majority of the C/C++ based open source projects. It should not require to rewrite or even replace the existing Makefile.am files of the project being ported, and it should allow to pass the needed parameters to the project configure script. Maybe OpenMoko project could be a bigger project having one or more (if some are libraries) autotools - based packages in its separate folders and include the proper documentation how to &quot;wire&quot; the standard autotools based package to the OpenMoko infrastructure.<br /> <br /> ===Foreign Widget Set Bindings ===<br /> ==== Qt Integration ====<br /> The Trolltech folks have a great widget library. I'd like to interface OpenMoko with Qt4, so that we can write Qt4 applications for the phone which don't look alienated.<br /> <br /> ==== Maemo Integration ====<br /> The Maemo folks have created a successful standard for Webpad applications. I'd like to have a set of MaemoMoko and MokoMaemo wrapper classes that allow me add support for running OpenMoko applications on Maemo and vice versa. Perhaps we can get help from the Nokia OSS folks for that.<br /> <br /> ==== wxWidgets Integration ====<br /> wxWidgets is a cross-platform application framework that's very popular (I'd say, #3 after Qt and Gtk+). On Linux, wxWidgets uses Gtk+ to implement the widgets. It shouldn't be hard to add support for the additional OpenMoko classes to wxWidgets hence supporting the native OpenMoko look and feel for wxWidgets applications.<br /> <br /> wxWidgets team wants OpenMoko classes too and we (wxWidgets) plan to include this project as one of our ideas for [http://google-code-updates.blogspot.com/2007/02/speaking-of-summer.html GSoC 2007]<br /> <br /> ==== SDL Integration ====<br /> SDL is ''the'' game developer library. There are tons of SDL games out there. We should add OpenMoko support into SDL.<br /> <br /> ==== Cocoa / GNUstep ====<br /> Allows to use MacOS X as a development platform.<br /> <br /> === Software: Language bindings ===<br /> ==== Python bindings ====<br /> Python bindings seem to be a commonly requested feature. <br /> <br /> [[User:Mickey]] says, &quot;They are kind of usable on the [http://www.maemo.org Nokia 770], but it's at the lower end of being bearable. We should keep this in mind -- Gtk+ already comes with Python Bindings, so we &quot;just&quot; would need to wrap libmoko*. I would prefer to leave this to the community do though, since it doesn't make sense to start wrapping the API until we have a stable API -- and I can imagine it will take us a couple of months after going open until we can start with stabilizing the libmoko API.&quot;<br /> <br /> ==== C++ bindings ====<br /> There is a whole skilled C++ community coming from the [http://qtopia.net Qtopia] and [http://opie.handhelds.org Opie] projects. If we would consider basing OpenMoko C++ Bindings on [http://www.gtkmm.org/ Gtkmm], then we could drag these guys in.<br /> <br /> ==== Ruby bindings ====<br /> Ruby and ruby-(gtk|glade) already ported to OpenMoko according to [http://lists.openmoko.org/pipermail/openmoko-apps/2007-May/000040.html this ] and [http://groups.google.de/group/comp.lang.ruby/browse_thread/thread/6bee9970cf055504 this] mesages. It just have to be included to distribution (only 4.9 MB!)<br /> <br /> ==== Java bindings ====<br /> People who concentrate on Java programming would like to have the OpenMoko port of some java virtual machine. GNU Classpath team a lot of great work in the past creating easily portable implementation. Sun's recently open sourced code could also be ported. <br /> ==== Other bindings ====<br /> * Perl<br /> * C#<br /> * I think you could skip a bunch of these by binding to Dbus; most languages already have Dbus bindings<br /> <br /> == Community Support ==<br /> <br /> === [http://projects.openmoko.org projects.openmoko.org] ===<br /> Infrastructure for developers with<br /> * One bugzilla for all projects (makes moving bugs forth and backwards between projects ''very'' easy)<br /> * One mailing list for project<br /> <br /> == Platform ==<br /> === Community Images ===<br /> In the future there could be complete, unofficial &quot;product images&quot; that are created by the community, for example maybe one that incorporates only free software (in the GNU or OSI sense). Or images build with a particular niche market in mind -- a student for example.<br /> <br /> === Wishlist voting ===<br /> There could be a kind of voting system like they have at one of those big computer manufacturers homepage. Then the community could vote for the ideas that are most important to them. This would especially make sense for the hardware wishlist, because the hardware is still the part which can't be done by the community that easily.<br /> <br /> Here: [http://www.fevote.com/openmoko OpenMoko suggestion board]<br /> <br /> == Software: Additional features ==<br /> <br /> ===PDA Mode===<br /> <br /> There are times when you wish to power up the device and not power up the gsm/cellphone portion of the phone. For example in meetings you might wish to access the PDA side with wifi as is the case for example on an aircraft. On booting some method of booting to pda mode would be good - several other phones offer this feature.<br /> <br /> ===Driving Mode===<br /> <br /> It may be forbidden in many countries, but many people use their cell phones while driving. With the touchscreen phones<br /> this is very dangerous: You have to stare at the tiny numbers on the screen and try to hit them with your thumb or try to decipher tiny script of contacts, while steering with the other hand. There should be a configurable driving mode where the interface has a reduced functionality (e.g. only contacts and dialing) with HUGE interface buttons that are easy to use with limited attention.<br /> <br /> Idea: insted of using GPS for speed measurement, number of handovers (other word: cell switches) shall be measured - as one traveling a car switches cells more often than walkers)<br /> <br /> ===Calling===<br /> <br /> ==== Mask ID based on dialed numbers ====<br /> It would be nice if my number only showed up when I call people in my address book and was otherwise masked. The phone I have now either always shows my number or never or can be set on a per call basis. Having it done automatically based on the number dialed would be good.<br /> <br /> ==== Use calling cards and similar routing techniques for lower-cost calling ====<br /> Many people use calling cards, low-cost numbers and similar ways of reducing the costs of their calls. It would be nice to have a single panel that would allow you to configure the rules of dialing a number taking in to account such systems.<br /> <br /> ==== Outgoing black/white lists ====<br /> The ability to allow or deny outoging calls to certain numbers can be useful in a number of situations (e.g. the holder of the 'phone is a child, untrusted, etc.). This could be related to entries in the contact list, for example a user is only allowed to call people who are in their contact list.<br /> <br /> Also lists for incoming calls? Some friends always come through, unknown numbers get rejected automatically.<br /> <br /> ==== Time-based blocking/unblocking of calls ====<br /> Allowing or disallowing outgoing calls at certain times of the day could be useful, e.g. blocking a business phone from making calls outside of business hours.<br /> <br /> ====Speaker-phone====<br /> * A speaker-phone is more than simply connecting the speakers to GSM audio, it's also echo cancellation, and eliminating the feedback that will otherwise happen between the speakers and the mic. This software has not been written.&lt;BR&gt;<br /> The problem of speaker-phones is that the microphone &quot;hears&quot; what the speaker outputs - directly and every reflection in the surroundings of the telephone. Since the telephone line will allow noise from the microphone to pass to the speaker again - if the speaker is loud enough and the microphone sensitive enough we have a feedback loop producing echos or even a very loud beep.&lt;BR&gt;<br /> A very crappy alternative that is used by some companies that just want to be able to print a feature on the front cover without needing to bring this feature to a useful state first now is the following:&lt;BR&gt;<br /> Turn either the Microphone sensitivity or the speaker volume down alternatively depending on what the telephone thinks might be better in this second.<br /> <br /> Sounds as crappy, as this sounds, though, - and tends to make people very angry.<br /> <br /> ====Advanced Airtime Tracking====<br /> Many phone users have complicated plans, things like unlimited incoming, 100 anytime minutes, 1000 evening minutes, etc. It would be nice if a user could input the various monthly airtime chunks their plan gives them, and then the phone could track how much is left in each chunk, i.e. How much anytime minutes are left this month? Optionally, the software could warn when someone is close to the monthly limit, to help avoid bigger bills.<br /> On (at least some) prepaid [http://en.wikipedia.org/wiki/Unstructured_Supplementary_Service_Data USSD] can be used to check current balance.<br /> <br /> * Call duration should consider billing increments and show the durations according to accounting period<br /> <br /> <br /> <br /> ==== Anti-stutter software ====<br /> Delayed Auditory Feedback (DAF) has shown to reduce stuttering in individuals by 70%. By using the microphone, it should be pretty simple to implement this on the OpenMoko. The DAF functionality should also be present during phone calls. See http://en.wikipedia.org/wiki/Delayed_auditory_feedback for more information.<br /> <br /> ====Minimize In-Call mode (check address book while in call)====<br /> On my locked phones I always find it annoying that one can not use other features while a call is in progress. In particular, I'd like to access the address book so that we can (1) give a caller someone else's phone number (or other info) and (2) lookup a phone number when using a calling card or some other proxy.<br /> <br /> Similar request when using the browser (lookup passwords, todo list, etc).<br /> <br /> ====Hold Music (Ringback Tone)====<br /> On some cellphone networks you can pay to change the normal [http://en.wikipedia.org/wiki/Ringback_tone Ringback Tone] that the caller hears when ringing, to a customised sound.<br /> This can partially be implemented on the phone.<br /> Issues are:<br /> *In countries where callers pay, this will make you unpopular.<br /> *In countries where the called party pays, it will use your minutes, or cost you money.<br /> **A list of people to activate this function for would alleviate this.<br /> *[[GPRS]] internet connection will stall while the hold music is being played.<br /> *Extra battery used when playing music.<br /> <br /> Also see [[Answering Machine]].<br /> <br /> ====Play sound clips over the air====<br /> Dialer could have a tab with big buttons which, when push, send sound clips over GSM to the person on the other end of the call. This feature is included in GizmoProject and is called sound blasts: http://support.gizmoproject.com/index.php?_a=knowledgebase&amp;_j=questiondetails&amp;_i=104<br /> The buttons can have default sounds, but also have the ability to be customized.<br /> <br /> It would also be useful for notifying people why you can't talk (for example, having an &quot;I can't talk tight now - I'm in the library - this is a pre-recorded message&quot; would be good. Also perhaps you could loop a pre-recorded sound in the background so you can lie about where you are, and have the ability to simulate a really bad connection.<br /> <br /> ==== DTMF Landline Dialing ====<br /> The ability to hold the Neo near the microphone of a landline handset and have the Neo dial the landline by sounding DTMF tones. The DTMF tones could be generated in software or be pre-recorded files.<br /> <br /> Graphically this could be done by adding a 'DTFM dial' button to a context menu. The user would select a contact then presses the 'DTMF dial' button to start the process. A small delay could also be added to allow time to put the Neo near the landline handset.<br /> <br /> For the Neo to know which area code to use (or not use) the current or last GPS coordinates could be utilised.<br /> <br /> ==== Conversation Recorder ====<br /> <br /> An option to record phone conversations. Would be helpful to have the device always recording for every call, with the sound data encoded to low quality Ogg Vorbis or SPEEX and stored in RAM. At the end of the conversation the user would have the option to save to flash or discard the conversation. This idea could also be applied to voicemail so you could save voicemails locally.<br /> <br /> ====Unlicensed Mobile Access (UMA)====<br /> T-Mobile recently rolled out a UMA service that hands off calls between the GSM network and WiFi access points. Only a few phones support it right now, this could be a rather unique feature if OpenMoko can implement it.<br /> <br /> This can be combined with a GPS map to show where local free hubs are.<br /> <br /> kd8ikt says a modded dialer with IAX/SIP (VOIP) or a stand alone VOIP client/dialer as an asterisk/FWD/IAXTEL/teliax stuff, i mainly just care about being able to connect to my own asterisk server in turn i can setup my asterisk server to route where ever i want i think one hardcore digium guy already ported iaxclient to arm so now i guess it needs a gui http://projects.openmoko.org/projects/mokoiax/ it wouldnt suprise me if underneath their UMA setup is a network of asterisk servers<br /> <br /> ==== Ignore-Call Button ====<br /> {{Main|Wishlist:Ignore Call Button}}<br /> <br /> Shut up a ringing phone, without accepting or rejecting the call.<br /> <br /> Another alternative might be to use microphone to recognize when the user gives an audible &quot;Shhh!&quot; command. This could prove difficult to determine with the simultaneous ringing, and possible in-pocket shuffling noises. <br /> <br /> A really usable feature is to &quot;reject with SMS/text message&quot; - letting the user reply the caller choosing a previously setup template or typical response: &quot;I'm in a meeting - I'll call you later&quot; or &quot;Can't take your call now, please call back in 10 minutes&quot;. This feature typically is a much better way to get your co-workers (ie boss) to back off, than to silently ignore the call.<br /> <br /> The accelerometers could be queried while the phone is ringing to detect a firm tap on the phone. This would avoid the delays of fumbling to remove the phone from one's pocket to silence the ringer when you've forgotten to set it to silent mode. Just firmly tap the phone through your pocket, and the ringer will silence, like some Motorola pagers. Maybe single tap = silence; double tap = (activate voicemail or preset SMS).<br /> <br /> ==== Voice Mailbox ====<br /> {{Main|Voice Mailbox}}<br /> On-Phone voice mailbox that records calls on the phone and retrieves voice messages from your mobile service provider's voice mailbox and saves them locally.<br /> Can act profile-dependent.<br /> <br /> ==== Hold Button ====<br /> <br /> Similar to mute, but plays a sound file for the user on the other end while they wait. The sound file could be chosen in some setup beforehand.<br /> <br /> ==== Unanswered Call, Fast Call ====<br /> <br /> In Greece because of the various bill programs some people call a mobile phone, rings one time and then hangup.<br /> Then the user of the mobile phone calls the other user(using the CallerID recognition).<br /> <br /> ===Audio===<br /> <br /> ==== Ambient Noise Detection ====<br /> {{Main|Wishlist:Software:Ambient Noise Detection}}<br /> <br /> Using the microphone to detect ambient noise the ringtone volume could be adjusted automatically.<br /> <br /> If the ambient noise exceeds a preset threshold, the ring vibrator could be activated. This is good for when people forget to enable vibrate mode when entering noisy environments.<br /> <br /> Detection of ambient noise could also be used to subtract the noise from the audio signal. However this approach is best performed using two Microphones, one for the voice and the other to detect the noise.<br /> <br /> ==== Active noise control ====<br /> <br /> Using the microphone to do [http://en.wikipedia.org/wiki/Anti-noise active noise control] on media player playback or telephone calls. This should be an independent module/library which can be used by any application which might require this feature. also provide a way to easily alter the parameters of the active noise control.<br /> <br /> ==== Hear Impaired Mode ====<br /> <br /> Hearing impaired people need louder speaker(but with less volume than hands free) and equalized sound, based on their hearing problems(example 20dB hearing loss from 2KHz to 4KHz).<br /> Older people 50+ years old need slower speech rate(time stretch, cut the big speech gups) and cleaner voice.<br /> <br /> Please note also the Hearing Aid Compatibility regulations in the US. I have tried to summarize and clarify them [http://quux.wiki.zoho.com/WhereAreHACphones.html here]. I haven't yet discovered whether the FIC device is M or T rated. For many hearing impaired users, a tcoil coupling to their hearing aid (t3/T4 rating) would be preferable to manipulating sound output in other ways.<br /> <br /> ==== Mute Button ====<br /> <br /> Button to temporarily disable microphone while talking for applications such as telephone, audio recording and (when available) movie recording.<br /> <br /> <br /> ===Web Browser===<br /> <br /> ==== Full-page Zoom Support ====<br /> Full page zoom is a very good feature. If possible, people would want to browse the internet with normal layout than a distorted one. It's best if I could double-tap a text or image block and zoom to a fit size.<br /> <br /> The [[BigPageWidget]] proposal suggests 'Full Page Zoom' should be implemented as a widget available to all applications.<br /> <br /> * If the processor and memory could afford, it is good to just use [http://www.mozilla.org/projects/firefox/3.0a8/releasenotes/ Firefox 3] in OpenMoko. It has implemented latest gecko's full-page-zoom ability. With certain modification, we could do the same zoom like iPhone's Safari.<br /> * Firefox 3 may be a big eater. A cut-down version of it may be good enough.<br /> * If this is not practical, Minimo with full-page-zoom ability is good.<br /> <br /> ==== Plugins Support ====<br /> * While an extensive browser plugin system would be costly to the efficacy of the platform four particular browser plugins as poplularized by Mozilla firefox should be adapted to the web-browser, namely: [http://noscript.net/ noscript], [http://adblockplus.org/en/ adblock plus], [http://www.greasespot.net/ greasemonkey] and [http://www.foxmarks.com/ foxmarks].<br /> * Careful use of these can dramatically reduce bandwidth, page space, and rendering costs even if it comes at the risk of some hard drive space in the form of block lists.<br /> * Greasemonkey, in particular, gives users control to set up scripts for commonly traveled pages to further reduce unnecessary or unwanted content.<br /> <br /> ==== Widget support ====<br /> Built-in browser with the ability to install widget shortcuts (aka links) in the main phone menu, also some apis for interfacing with the other functionality of the phone like adding contacts, reading contacts, reading gps-psoition etc.. (maybe there is some defacto widget standard that could be used)<br /> <br /> There is a [http://www.w3.org/TR/widgets/ W3C spec] being developed, which may not be exactly what the original proposal had in mind, but it is about writing simple applications with HTML, SVG and JavaScript. It is mainly Opera's work, and while most [http://widgets.opera.com/ developed widgets are not very useful], there are some that are, and it creates a very nice development platform, especially for mobile devices. So, I think it makes an awful lot of sense for OpenMoko to support this spec.<br /> <br /> ===Media===<br /> ====Music/Video Software====<br /> A real good programming area for competition with the iPhone, a singular video/music player would be great for multimedia. A seamless integration system, a la iTunes and iPod, would be extremely popular. <br /> <br /> Using the Wi-Fi connectivity, a separate music program that supports wireless music sharing/ streaming (similar to what can be done when two computer running iTunes that are both on the same network) and that also supports internet radio.<br /> <br /> It would also be nice to have some kind of &quot;announce your musical taste&quot; mode. This could be implemented using last.fm profiles, such that when e.g. in a crowded place a user nearby has a similar musical taste, both users get notified so they can share their music files with each other (perhaps using a photo for id). Great for discovering new music - and making friends!<br /> <br /> - Possible copyright issues sharing music files?<br /> <br /> Sure, but that's the user's concern, not the developer's. There's no way for us to know which audio files the user is permitted/not permitted to share.<br /> <br /> ==== Reading Support ====<br /> It would be really great to be able to read :<br /> <br /> *PDF<br /> *Open Document files<br /> *Text / RTF files<br /> *fb2 files (fbreader)<br /> *MS Office files<br /> *Aportis Doc (pdb)<br /> *DjVu<br /> *...<br /> <br /> In both landscape and portrait<br /> <br /> ==== Wikipedia Mirror ====<br /> {{Main|Wishlist:Wikipedia_Mirror}}<br /> <br /> ==== Blog ScribblePad ====<br /> <br /> Draw an image (and maybe add some text), then post to your blog.<br /> <br /> ==== E-Book Reader ====<br /> * Neos brilliant ultra-sharp screen makes for a very good e-book reading device. All it takes is a good e-book reader with touch-screen page turning / scrolling (see the [[BigPageWidget]] proposal). FBReader could probably be adjusted easily by an experienced GTK hacker. Note that e-book reading is different to pure text/pdf displaying as it requires at least auto-bookmarking of the last read page, proper text and image scaling and text formatting.<br /> <br /> ==== Personal Wiki ====<br /> {{Main|Wishlist:PersonalWiki}}<br /> <br /> Display the notes database as a Wiki. Inspiration: [http://www.acrocat.com/AcroWiki/default.asp?lang=en AcroWiki].<br /> <br /> [http://www.didiwiki.org/ Didiwiki]<br /> <br /> <br /> ==== Dictionary, thesaurus, translator and flashcards ====<br /> Native lookup dictionary and thesaurus and foreign translation dictionaries, also with support for Asian languages. Optional custom configurable (though preconfigured) interface with on-line versions of dictionaries, thesaurus and translation services.<br /> <br /> '''Dictionary'''<br /> Something like [http://www-user.tu-chemnitz.de/~fri/ding/ ding]:<br /> <br /> advantages:<br /> * small<br /> * very efficient + useful<br /> * only limited to really needed functions<br /> <br /> Support for vocabulary training with flashcard system (also usable for other content than foreign language words!)<br /> <br /> ==== Flickr uploader ====<br /> A simply, drag &amp; drop uploader, tagger and organizer to upload images on phone to [http://flickr.com Flickr], with support for various languages. A good base could be the cross-platform uploader [http://juploadr.org/ jUploadr], written in Java and working on Windows, Mac and Linux. But, most of all, the best '''GPL''' program which actually do this work is '''[http://mobilepushr.jottit.com/ Mobile Pushr]''', written in C and Cocoa for iPhone, must be probably ported in python to work on OpenMoko.<br /> <br /> ==== Virtual picture viewer ====<br /> I believe you could display pictures larger than the FR screen by using the accelerometer data to simulate the physical screen as a window into a larger pic.<br /> <br /> You would use the accelerometer data to figure out the current FR location &amp; orientation relative to when the pic was loaded, then display the part of the picture that the window overlaps. Then you could flick the neo back &amp; forth and see an image bigger than the screen.<br /> <br /> I haven't done any calculations to see what the accuracy would be like, but my wild ass guess is that if you moved it quickly enough it would overwhelm the error margin of the accelerometer. I'm also not sure if the refresh rate is fast enough to make it look good, but again my guess is that it would be.<br /> <br /> ===PIM (Personal Information Managment)===<br /> ====Context Sensitivity====<br /> Any email or sms message or application that contains a telephone number should be click to dial, eg [http://123567890 1234567890]. Addresses link to mapping software too?<br /> <br /> ==== Notes ====<br /> <br /> Something for taking notes would be a nice feature:<br /> [http://www.gnome.org/projects/tomboy/ Tomboy] has some nice syncing features and is gtk based.<br /> <br /> Some Screenshots are [http://www.gnome.org/projects/tomboy/images/ here].<br /> <br /> ==== Calendar ====<br /> <br /> A nice calendar application should be implemented in OpenMoko. This tool should have a syncing feature with your desktop computer.<br /> The tool should have a reminder feature and other features like other mobile phones already have.<br /> <br /> I think synchronization sould be handled by computer with opensync+syncml based tool, not by calendar itself. --[[User:Antono|Antono]] 12:25, 7 January 2008 (CET)<br /> <br /> * If this cellphone is thought also as a PDA, of course it needs a calendar. But I would like to see something better than just a calendar, I was thinking that there could be some application using &quot;fisheye&quot; view. Just like [http://www.cs.umd.edu/hcil/datelens/], though that example seem a bit chaotic. --[[User:Yprum|Yprum]] 22:27, 21 February 2008 (CEST)<br /> <br /> ==== Address Book ====<br /> <br /> * Option to search not just the stored list of addresses, but one or more of the online phonebooks. Probably should be modular to make adding/changing phonebook sites easy. Also allows for future integration with LDAP servers or whatever.<br /> * Also the possibility to search all info on the contact, like number, email, postal address and so on, in case someone asks you to identify a known number.<br /> * Web-based map-lookup. 'How do I get there from here? (here = current GPS location)' This could also be done by integrating with whatever on-phone GPS mapping software the Neo ends up using.<br /> * Random text input 'notes' about a contact<br /> * Overall, this should more resemble a Palm-pilot's address-book than your average cellphone's<br /> * Automated Daily backup of phone book to a website archive (similar to Verizon's Back-up Assistant)<br /> *Ability to integrate address book with web-based email (such as gmail) account, for those who use web based email as their primary account<br /> * '''[[Wishlist:Tagging|Tagging]]''' Place tags for contacts. Enhance message application to send messages to all contacts tagged with ... . Enhance other applications (GPS, ...) with tags.<br /> * Support for:<br /> **[http://en.wikipedia.org/wiki/SyncML SyncML]<br /> **[http://abook.sourceforge.net/ abook] a text-based addressbook program<br /> **[http://en.wikipedia.org/wiki/Ldap LDAP] address book<br /> **[http://en.wikipedia.org/wiki/LDIF LDIF], [http://en.wikipedia.org/wiki/Xml XML] and [http://en.wikipedia.org/wiki/Comma-separated_values CSV] export and import (when possible).<br /> *Store Bluetooth IDs of friends and notify (configurable only on this device or on both devices) when a one of these Bluetooth ID has been detected (this is more a separate application but has requirements on the address book. Should also be able to create an address book entry from a Bluetooth ID. Could be used as a nice tool to detect people who you're avoiding.<br /> * Support for family relations (explained further on the [[Talk:Wish_List#Address_book:_Support_for_family_relations|talk page]]).<br /> * Id like the GPS location of the phone at the time the contact was made to be stored. This would be displayed along with a map of know n locations, eg, at hom on the train, at work. <br /> * Id like the date I created a contact to be stored, and the ability to search by date. I know I put that estate agent in last saturday, but I cant remember his name!<br /> <br /> ==== Database/List Display/Edit ====<br /> {{Main|Wishlist:PilotDB}}<br /> <br /> One of the most useful apps on my Palm Pilot for me is [http://pilot-db.sourceforge.net/ pilot-db]. It's GPL'd.<br /> <br /> ==== To-Do lists ====<br /> <br /> * It'd be nice to have something like [http://www.joesgoals.com Joe's Goals] always available, like my phone is, even when I'm disconnected from the net.<br /> * I would like to be able update my [http://todotxt.com/ todo.txt] which is stored on a personal server from the phone.<br /> <br /> <br /> ==== Context based To-Do list ====<br /> {{Main|Wishlist:context based to-do list}}<br /> <br /> If I arrive home and there are &quot;@home&quot; things in the to-do list, the Context based to-do list reminds me of that.<br /> <br /> ==== Workout ====<br /> <br /> Use your phone instead of your notebook while at the gym, and get pretty graphs to admire after you're done.<br /> <br /> ==== Shopping List ====<br /> keep Track of Prices in different shops and the products you have/don't have. Ideally using a barcode reader and gps.<br /> If it was made aware of recipes it could even tell you what to buy without entering a shoppinglist manually.<br /> <br /> ==== [[Fuel Log]] ====<br /> File data about fueling your car (date/time, liters, price, mileage, ...) and display some information (costs per month, average consumption, ...).<br /> Advanced features could include:<br /> * Automatically storing the GPS coordinates of the place where the car has been fueled (can be deactivated)<br /> * Sending the data to a central server which collects the information ( spritmonitor.de, anything else ?)<br /> * Let the OpenMoko receive fuel logs per SMS (e.g. if my wife with a non-openmoko mobile fuels the car and wants to file the data using her mobile phone)<br /> * Let the OpenMoko device act as SMS gateway for non-openmoko devices to easily send the data to the central server<br /> * Also support for air log for divers. Not that you will take this device under water but for the crew at the surface.<br /> <br /> ==== Keep in touch reminder ====<br /> A background application which keeps track of your friends and reminds you when you have not talked, SMS, IM or mailed a person for more than # days.<br /> <br /> <br /> ==== Menstruation period timer ====<br /> Fill in statistics and compute probabilities for menstruation, fertility, mood.<br /> See http://www.getjar.com/products/48/MyGirls<br /> <br /> ==== Tagging ====<br /> {{Main|Wishlist:Tagging}}<br /> Tags can be used by various applications. Requirement is interoperability for further enhancement.<br /> Tags should be applied to contacts, calendar events, mail/sms, calls, places(GPS) and files.<br /> http://tracker-project.org has all needed tagging-and-searching functionality and ready to be used on low-resourced devices.<br /> <br /> <br /> <br /> ==== Exchange Integration ====<br /> <br /> Once there is good TCP/IP connectivity on this phone, integration with corporate email/calendar/to do/contacts/etc servers would be a big advantage... near-real-time automatic email downloads and automatic bi-directional syncing are productivity boosters that you have to experience to appreciate. It turns your phone from a 'nice gadget to fiddle with' to a natural-feeling extension of your day-to-day life.<br /> <br /> * Is the time right to name names ? Add as your liking...<br /> ** Plugin/integration to &amp; from Kontact<br /> ** Same with Evolution - Thunderbird - Seamonkey<br /> ** ?? Google Calendars ?? (this one is tough)<br /> ** Ms Exchange<br /> <br /> ==== An electronic wallet ====<br /> <br /> A database which stores securely PIN codes, login data, bank and email accounts, membership informations, and other valuable and private data. Entries can be ordered in a folder-like manner. Access to the database is given by a master password. The database as well as the master password are stored with strong encryption. For security reasons, the program asks again for entry of the master password after a certain period of inactivity. The database can be synchronized with a PC application (ideally written in Java for cross platform compatibility).<br /> <br /> Examples: KWallet [http://docs.kde.org/stable/en/kdeutils/kwallet/index.html], Viskeeper [http://www.sfr-software.de/cms/EN/pocketpc/viskeeperpro/index.html], KeePass [http://keepass.info/], KMyMoney2<br /> <br /> ==== Easy business card sharing for a small group (in the same room) over bluetooth or WIFI ====<br /> <br /> Six Neo1973 owners are having a chat in a cafe. They agree to split but meet later. They want to exchange their numbers with each other before they go.... The normal way to do this is for a rather longwinded repeating of numbers to each other, or half the people manually inputting numbers before phoning/texting the other half to complete the process. All in all its a fair number of button presses to get it sorted.<br /> <br /> Instead the NEO could have a small app where the phones link up in a small peer to peer Bluetooth network and share automatically with one person initiating a request and the other detected NEOS agreeing/acknowledging the share. The initiating NEO would then sync the mini-group automatically by interrogating each phone and then sending the table of results. The NEOs would have to be clever about checking for duplicates in the address book and offering a choice to the user if there are any conflicts.<br /> <br /> PROS: <br /> *genuine saving in time for social and business situations<br /> <br /> CONS: <br /> *I am sure there are some security hassles to be pondered....<br /> *not going to be used every day... definitely not an immediate priority.....<br /> *only at geek conferences will all have a neo....<br /> <br /> ==== SMS Counter ====<br /> <br /> An application which shows on the today-screen how many SMS i've already sent in this actual month. Some have for example 150 free SMS to write each month. With that program you can see all the time how many SMS are left until the end of the period. As an alternative it could be a counter which counts backwards from a predefined number over a defined period.<br /> <br /> ==== Data Storage ====<br /> <br /> Store all the data about communications with a contact (SMS, MMS, phone calls, emails, IM, etc) in a database and make them available in one list or one timeline.<br /> Make this list available through the address book.<br /> This would be great for people who are switching between one or more communication channels frequently<br /> <br /> ===Profiles===<br /> {{Main|Wishlist:Profiles}}<br /> <br /> The Wishlist:Profiles page documents many possible profiles - ways to configure the phone. Including ways to respond to calls, wifi and GPS events.<br /> And how to automatically switch between them.<br /> <br /> ===Text Messaging===<br /> For '''Text Input related ideas''' see [[Wishlist:Text_Input]]. Bear in mind that T9 can not be included<br /> For current development status of the messaging-app see: [[Messages]].<br /> <br /> There are many useful options that now can be used to full capacity:<br /> <br /> * '''Instant Messaging'''<br /> Bringing a new GTK gui or a resized Qt gui out for the serverless Instant Messenger http://Retroshare.sf.net<br /> <br /> * '''Acknowledge/status SMS'''<br /> In GSM networks so-called acknowledge-SMS are sent back to the SMS's dispatcher in order to indicate that the primal sms was received (as message delivery is only best effort and is not guaranteed). So in the SMS dialog there could be equal sized buttons with captions as 'send only', 'send and receive delivery status message' and 'send and notify (e.g. ring) when delivery succeeded'.<br /> <br /> ** '''Special handling of status-SMS''' <br /> Related to the previous entry, these acknowledgment-sms' should be handled in a different way than normal SMS'. Most Motorola do this, while Samsung SGH series don't &amp; clog the inbox, warn of a &quot;new&quot; message upon Status notification: Delivery Status Messages should be stored in a separate menu so they don't bloat the received-folder and you are able to quickly review the status of the messages you had sent.<br /> * '''SMS at time/date''' You could be able to set up messages that are sent at a certain time/date<br /> * '''Binary SMS''' Send binary SMS. Could be used to feign WAP pushes. [http://en.wikipedia.org/wiki/Multimedia_Messaging_Service] See: <br /> ** Resource for SMS encoding: [http://web.archive.org/web/20021016104345/www.dreamfabric.com/sms/] [http://web.archive.org/web/20060411222332/] [http://home.student.utwente.nl/s.p.ekkebus/portfolio/resource/sms_pdu.html] [http://www.ihub.com/Binary%20Messages.htm]<br /> ** [http://www.gammu.org www.gammu.org] - you can use Gammu/Gammu+ source for this software and/or understanding various SMS formats including EMS, WAP, Nokia Smart Messaging, Siemens &amp; Alcatel encoding ([[User:Marcin|I could]] eventually help)<br /> ** Resource for SMS encoding (German): http://de.wikipedia.org/wiki/SMS-Kodierung<br /> ** The infamous pocketpc-attack: http://www.mulliner.org/pocketpc/<br /> * '''Profile-override-SMS''' SMS that start with a certain code word override the silent profile and have the phone ring. So someone could alert you in case of some emergency.<br /> * '''Codeword-SMS''' An expansion of the above: check for code words and allow selectable tones for matches. E.g. &quot;Server Down!&quot; has a loud klaxon, &quot;Disk Warning&quot; has a quiet chirp.<br /> * '''(De-)Abreviation-script''' Implement a script that de-abbreviates: &quot;hi m8 u k?-sry i 4gt 2 cal u lst nyt-y dnt we go c film 2moz&quot; becomes &quot;Hi mate. Are you okay? I am sorry that I forgot to call you last night. Why don't we go and see a film tomorrow?&quot; (taken from: [http://en.wikipedia.org/wiki/SMS_language])<br /> ** Implement a script that abbreviates :-)<br /> * '''Anti-Spam''' ...feature for SMS. May be it's possible to port some Bayesian based application like bogofilter.<br /> * '''Rule based authorizations''' ...for received messages. For example, delete messages from one source between 9h00 and 18h00 (workday) allow them otherwise (to get alerting messages).<br /> * '''Enable chat-like SMS-viewing''' SMS-Email-like: retain SMS app, but store 'conversations' rather than pile-up. Group/archive conversations by Caller Group (Work / Friends / Home / any user-defined Caller Group). Show appropriate icon from either Caller Group or Caller ID at the source of conversations panel<br /> * '''Searching''' allow full-text search or string search.<br /> * '''Massive SMS Deletion''' based on Conversation, author, before-date-xx.xx.xxxx, caller group, [[Wishlist:Tagging|tags]]...<br /> * '''Call Back''' Prompt 'Call Back' alongside other first-line options (Delete, Save number,.. this kind of options) that appear when reading an SMS.<br /> * '''Non-destructive deletion''', deleted messages goes to trash, and are recoverable.<br /> * '''SMS-EMail-Gateway'''<br /> SMS comes in, gets forward to your inbox, like any other piece of mail. Appropriate alerts and etc occur - again, just like for email. A simple SMTPD running on 127.0.0.1 that is hooked to an email-to-SMS translator that will send email addressed to 'SMS@localhost' (or whatever special address) out via SMS<br /> * '''SMS-filter chain''', for stuff like Codeword-SMS above, Theft-mode activation, auto-response (reply with gsm-position for &quot;Where are you?&quot;), auto-substitution (like replace $POS with gsm-position in outgoing SMS).<br /> * '''SCROOGE-SMS''' This is an intelligent SMS router. When you write your SMS you get the option of how to send it<br /> ** By standard carrier SMS - cost 10cents<br /> ** By OpenMoko SCROOGE SERVER - this will send your SMS to the OpenMoko Community SCROOGE SERVER next time you have WiFi - the phone will remind you to turn on WiFi when it knows you are in places where you have WiFi access. The person you are sending to picks up when they come into WiFi Range. This comes with an intelligent reminder that tells you that message has still not been delivered in 24 hours and would you now like to send it by a paymethod. This is better than IM because both parties do not have to have WiFi at the same time. - cost FREE<br /> ** By email/Wifi - cost FREE<br /> ** By email/GPRS - cost ?<br /> ** Too many options!!!<br /> ** Alternatively SCROOGE SERVER could auto launch IM client if it detects both parties have WiFi at the same time (Status kept on SCROOGE SERVER?) to allow instant reply..... Person who receives has the option to reply in SMS or in IM or in VOIP phone.<br /> <br /> === Text input ===<br /> {{Main|Wishlist:Text Input}}<br /> There are many good suggestions for text input on the specific text input ideas page.<br /> <br /> === More/Custom Input Method Widgets ===<br /> {{Main|Wishlist:More/Custom_Input_Method_Widgets}}<br /> Additional and customizable Input Method Widgets (similar to virtual keyboard). <br /> This could add soft-key functionality to games or other applications such as:<br /> *D-Pads<br /> *buttons<br /> *virtual trackballs<br /> *...<br /> Personalized layouts could be associated with each application.<br /> <br /> === Games ===<br /> {{Main|Wishlist:Games}}<br /> <br /> === Mesh Networking ===<br /> {{Main|Wishlist:Mesh Networking}}<br /> <br /> === Printing Support ===<br /> It would be really neat to be able to print over either bluetooth, Wifi, or USB. I can imagine wanting to print:<br /> <br /> * Notes<br /> * Maps<br /> * Email<br /> * Calendars<br /> * ...<br /> <br /> Cups contains a bluetooth printing backend, so (in theory) once you have your data in postscript format, you could hand it to cups and it'll do the rest. In practice, it depends on<br /> <br /> # GTK+'s printing support<br /> # Making cups run on a really small system<br /> <br /> {{note| GTK+'s printing support seems to be very immature in 2.6 (which we need to use for some time). Gtk+ 2.10 contains much better printing support -- once we can use this, it should be more easy.}}<br /> <br /> There's always the possibility to render postscript ourselves, but this is not a piece of cake -- in general, printing is much harder than one would imagine.<br /> <br /> Further details:<br /> * [http://groups.osdl.org/apps/group_public/download.php/2205/print-summit-gtk.pdf#search=%22gtk%2B%20printing%20API%22 osdl.org]<br /> * [http://www.gnome.org/~alexl/presentations/guadec2006-printing.pdf#search=%22gtk%2B%20printing%20API%22 gnome.org]<br /> * [http://www.j5live.com/?p=204 j5live.com]<br /> <br /> ===Misc Software===<br /> ====Clocks/timers/Activity meters====<br /> ===== Sport tracker =====<br /> {{Main|Wishlist:Sport_tracker}}<br /> Sport tracker can be used to measure the distance/velocity from point A to point B (or it could have several intermediate stopping points) using GPS. This would be extremely useful for running, biking, hiking, etc.<br /> <br /> ===== Standby clock =====<br /> {{Main|Wishlist:Standby_clock}}<br /> A quick way to see what time it is.<br /> <br /> ===== Egg Timer =====<br /> {{Main|Wishlist:EggTimer}}<br /> <br /> Very simple (one click) count up / count down timers are very useful.<br /> <br /> ===== Cycle Computer =====<br /> As already mentioned by [http://wiki.openmoko.org/wiki/User_talk:Technil Technil], a cycle computer could be created using gps. The sensor at the bike's wheel could transmit data via bluetooth or some cable that would be attached to an openmoko device. In order to save power, one could switch off the gps and only use the bike's sensor.<br /> * Just another idea that came to me: Why don't have sensor's transmit cable plug into the headphone/microphone plug? A tool reads the signals created by the induction of the passing magnet, then gives them to the cycle-computer-app :) --[[User:Minime|Minime]] 19:50, 12 April 2007 (CEST)<br /> <br /> ===== NTP Server =====<br /> <br /> Run the [http://www.ntp.org NTP] daemon using the GPS chipset as a reference clock, so that the Neo would have a very accurate time-of-day clock and would be able to serve time to other networked devices. <br /> <br /> I don't know what it would take to implement this. Items to consider would be the availability of a 1 pulse-per-second hardware signal, the accuracy of timestamps delivered in NMEA messags, etc. Dealing with power-management issues (such as the device going to sleep) would also be challenging.<br /> <br /> <br /> ===== Find Keys/locate stuff =====<br /> <br /> This would require an additional accessory: a tag which transmits a signal that the Openmoko device can pick up. The tag could for example be attached with a ring loop to your keys, put in your wallet, or be attached with high strength adhesive strips to your remotely controlled aircraft. Whenever you can't find back your keys, wallet, RC aircraft,... you activate this application. When the device picks up the signal of the tag, it translates it to clear audio and visual prompts to guide you in the right direction.<br /> <br /> A commercial device that offers this functionality is the [http://loc8tor.com/ loc8tor]. Having this in the Openmoko phone would obliviate the need for a separate device. Murphy's law dictates that you'll only loose your keys when you don't know any more where you've put the loc8tor tracking device. But you're bound to always have your phone with you. <br /> <br /> Additionally, you could also set a safety perimeter. Whenever a tagged item moves more then X meters from the phone, a signal will be given.<br /> <br /> For a related idea, see [[Wishlist#Dude.2C_Where.27s_My_Car.3F|Dude, Where's my car]].<br /> <br /> ===== Reality check reminder =====<br /> {{Main|Wishlist:Reality check reminder}}<br /> <br /> A tool to [http://www.phrack.org/issues.html?issue=64&amp;id=16 hack your brain]<br /> <br /> ===== Automatic timezone changing (GPS) =====<br /> <br /> Check the timezone with GPS and adapt them.<br /> <br /> ====Calculators====<br /> ===== A Universal Unit Converter Tool =====<br /> <br /> One never knows when one may have to convert acre-feet into deciliters. A unit conversion tool makes all engineers and engineer wannabes much happier. And not only the engineers. <br /> <br /> Ideas what kind of conversions a converter tool could do:<br /> <br /> Length<br /> - Acceleration<br /> - Angle<br /> - Angular Velocity<br /> - Area<br /> - Capacitance<br /> - Radioactivity<br /> - Currency <br /> - Charge<br /> - Computer Memory<br /> - Conductance<br /> - Density<br /> - Energy<br /> - Illumination<br /> - Power<br /> - Force <br /> - Flow<br /> - Pressure<br /> - Speed<br /> - Temperature<br /> - Time<br /> - Torque<br /> - Viscosity<br /> - Volume<br /> - Weight<br /> <br /> Roman Numerals<br /> - ASCII, Hex<br /> - Cooking<br /> - BMI<br /> - Clothing Sizes<br /> <br /> Money Converter based on current rates from Internet...<br /> e. g. Dollar &lt;-&gt; Euro<br /> <br /> Physical and Mathematical Constants<br /> GPS conversions <br /> <br /> - link to or integration of a scientific calculator<br /> - link to or integration of a simple calculator<br /> <br /> A good basis for such a converter tool could be the Palm program &quot;units&quot; from <br /> François Pessaux [http://francois.pessaux.neuf.fr/files/units1_11.tgz]. The GPL'd program comes with full documentation.<br /> <br /> For GPS conversions see gpsbabel [http://www.gpsbabel.org]<br /> <br /> ===== An Postfix Notation (RPN) calculator =====<br /> <br /> Many engineers, computer scientists and other groups who have grown to enjoy the simplicity and ease of an postfix notation calculator will miss them when they give up other platforms to move to OpenMoko. A RPN calculator will increase adoption by providing one of the tools that other platforms have provided for many years.<br /> <br /> ===== Scientific Functions =====<br /> <br /> For lab and desktop use. ln &lt;i&gt;x&lt;/i&gt; / &lt;i&gt;e&lt;sup&gt;x&lt;/sup&gt;&lt;/i&gt;, sin &lt;i&gt;x&lt;/i&gt; / cos &lt;i&gt;x&lt;/i&gt; / tan &lt;i&gt;x&lt;/i&gt;, statistical capabilities, etc. . .<br /> <br /> ==== Windows CE Emulator ====<br /> <br /> On ARM machine, Windows CE API emulator, like Wine on x86 machines. <br /> <br /> ==== PalmOS Emulator ====<br /> <br /> The Access group is probably coming out with their Linux platform any time soon. One of the components is a PalmOS emulator which I'd like to see working on OpenMoko as well. There are literally thousands of PalmOS apps.<br /> <br /> I'd like to see a Windows CE Emulator with active sync support.<br /> <br /> ==== Chumby Emulator ====<br /> <br /> Would be very cool if the neo can act as a chumby. see http://chumby.com for more details about a chumby.<br /> <br /> ==== TV Guide ====<br /> Display a TV guide using [http://xmltv.org xmltv].<br /> Something like [http://mtvg.sourceforge.net/ Maxemum TV-Guide] (QT)<br /> <br /> ==== Alcohol meter ====<br /> Give the phone some info about your body (gender, size, weigth) and when/what you drink and it will compute an approximation of the amount of alcohol in your blood. Updates automatically, could have an alarm, when you are probably sober again.<br /> See, for example (German text) http://www.misterio-online.de/promille.htm<br /> <br /> ==== Interaction with LEGO Mindstorm ====<br /> With the accelerometers, GPS and good CPU, the phone could be used to control/serve as input with robots built with LEGO Mindstorm, which can be accessed by USB and Bluetooth.<br /> <br /> ==== Flashlight ====<br /> Simple finger application that makes every pixel on the entire screen white to be as bright as possible until you tap the screen again to turn it off. This way, you can use your Neo as a (short term) flashlight!<br /> <br /> ==== Wii Controller Emulator ====<br /> Use the accelerometers and buttons on screen to work as a Wii controller via Bluetooth.<br /> <br /> ==== FUSE support ====<br /> Ability to use FUSE to mount larger file systems over wireless. (even gmailfs, sshfs, etc.) '''in openembedded'''<br /> <br /> ==== Interactive Sky Map ====<br /> Application that displays the current sky map. Using GPS, the application determines the direction over ground<br /> and rotates the map appropriately. Furthermore, when the phone is tilted, the map is also moved appropriately.<br /> If everything works fine, you should have the impression that you can lift the phone over your head and<br /> &quot;look through&quot; it and see the stars at the correct positions.<br /> <br /> === Accessibility ===<br /> Accessibility features for the visually impaired.<br /> * High Contrast Themes.<br /> * Screen Magnifier. Features should include automatic cursor tracking when navigating menus and entereing text and provide manual controls to zoom in on other section of the screen.<br /> * Text to speech. The software should read out menu item ,contact lists ,text messages etc. Would also be useful for operating the phone while driving. see: [[Wishlist:Speech synthesis]]<br /> <br /> ==== VOIP ====<br /> * [[Dialer]] should be able to use SIP.<br /> Ability to use the phone for VOIP over wi-fi such as Vonage. They currently have 2 different pieces of software for pc . Basically software creates a mac address which is paired with your Vonage account. Skype could also be implemented but I prefer Vonage. Only available when connected to wi-fi with a good connection. Phone treats calls the same as a cellular call, could keep a separate log of minutes, ability to record conversations, etc. Option to use VOIP if connection is available automaticly or manually. Small icon to show when call is using VOIP.<br /> * A standard SIP client would probably fit better into the &quot;free and open&quot; philosophy.<br /> * Ideally a SIP client that includes ZRTP/SRTP for secure communications.<br /> (Note: Vonage will not give you your SIP credentials, so you cannot log into their network with a non-approved softphone. Other VoIP providers have different policies.)<br /> <br /> ''This seems very similar to what [http://en.wikipedia.org/wiki/Generic_Access_Network UMA] offers.''<br /> <br /> Asterisk is a great communication platform that can run on small devices. I have an Asterisk server running on a Nokia 770 and I read about running Asterisk on an iPhone. With the crosscompiler available it sould be possible to compile it and run Asterisk on an openmoko phone and let it take care of almost everything on the wishlist below.<br /> Edw/<br /> <br /> [http://www.freeswitch.org/ Freeswitch] is also well worth a look -- it's a project started by a long time contributor to Asterisk, and seems to be more scalable on similar hardware, so might well scale down to small hardware quite nicely.<br /> <br /> ==== Power Meter ====<br /> If the power bar is clicked on it will show time left on charge and if charging it will show time until full.<br /> <br /> Also a rrdtool type of configurable timespan/frequency graphical overview would be very cool and usefull to some people?<br /> <br /> === Accelerometer wishes ===<br /> ==== Flick interface ====<br /> Ability to &quot;flick&quot; the phone for page up/down by simply and rapidly tilting the phone back-and-forth for up and forth-and-back for down. The same motion can be implemented for sideways motion. This will take advantage of the 2 3d accelerators.<br /> <br /> Sensitivity of the scrolling should be configurable and a test option provided.<br /> <br /> ==== Reading navigation of documents enhanced by accelerometers ====<br /> If the two accelerometers in Neo1973 allows it, it will be nice if when you're reading, give a newspaper, you can move up, down, left and to the right the viewing of the document just moving the phones to the corresponding direction.<br /> <br /> I don't know if this is possible (haven't seen the project in detail yet) but this feature could be very attractive for final users (and this is good). (sorry for my english but i'm italian)<br /> <br /> ==== Wand UI ====<br /> In keeping with the requests to think outside of the box... the dual 3d accelerometers should enable a 'magic wand'-style UI for certain uses. Macros could be recorded and edited, or presets could be used. For example, flipping the device playfully could initiate a game mode or could signal the end of the work day.<br /> ==== Panning interface ====<br /> Some applications display underlying data that is larger than the screen. Typically they let you pan across the data using scroll bars.<br /> <br /> In cases where the data is only (say) 3 or 4 screens wide or high, it may be very intuitive to just shift the hand held device a few centimeters to the left or right, up or down to pan in that direction. The screen would appear to be a hole into the world of the data, and you're just moving the hole to look at something else.<br /> <br /> When the underlying data is very large, you obviously wouldn't want to use this mechanism unaltered; you'd have to walk to the next room to see the data 100 screens away. Instead different accelerations can be used for different panning sizes. This is the same adaption used for accelerated mouse pointers typical on touch pads. A quick flick moves the mouse pointer fast and far. A slower drag over the same area on a touch pad moves the pointer slower and with more precision.<br /> <br /> ==== Shake-to-Wake ====<br /> Giving the phone a shake enables voice commands for a few seconds.<br /> Usage Examples: <br /> <br /> * {Shake} &quot;Call&quot; ''ContactName'' ''PhoneType''<br /> * {Shake} &quot;Call John Mobile&quot; (Calls John's mobile)<br /> * {Shake} ''ApplicationName''<br /> * {Shake} &quot;Reader&quot; (Opens the e-book application)<br /> <br /> Would require a method of inputting voice tags for applications and contacts and obviously will only work for P2 (accelerometers)<br /> But lets get voice command functionality working before P2 (just by pressing a button on the screen instead of shaking)<br /> <br /> I think that is possibly to replace &quot;Shake&quot; with double hit with finger in the side of phone. Proper algorithms(with accelerometers) should recognize any similar activities.<br /> <br /> ==== Emergency call ====<br /> When the accelerometer detects a great acceleration (i.e. 5G) start a countdown sequence, if it is not stopped make a call to a preconfigured emergency number. If the data from the GPS is accurate give it.<br /> <br /> A first version could use a recorded message (an audio file). In next version it could use a synthesizer, so it can give more information (add GPS information when it is ready).<br /> <br /> :I would worry that most such events would be false positives, and hard to distinguish from the real thing. A user dropping their phone (an event very common in the life of any cellphone) is far more likely than a user being in a car accident with their phone, and the clatter of a cell phone on asphalt could reach 5G. Additionally, it has to be very hard to distinguish hitting pavement from hitting a windshield, as from a physics standpoint the two are the same thing. [[User:Hashbrowncipher|Hashbrowncipher]] 02:06, 26 October 2007 (CEST)<br /> ::It could use the gps data to calculate the speed it is traveling with. Let's say it has been moving for more than 50 km/h for more than 10 seconds. Then it could activate the &quot;emergency call if more than 5g&quot; function. Aside from the countdown timer, it could increase the volume to max and warn the user that an automatic emergency call will take place in x seconds. While it is counting down it could listen for &quot;Never mind, I'm fine, phone&quot; and stop the countdown in case it hears that. It could also output the warning sound to the attached bluetooth headset and let the user talk to emergency services if the user is still conscious. [[User:Tommy|Tommy]] 17:48, 8 January 2008 (CET)<br /> :::Perhaps have the phone yell loudly that it's about to do the emergency call for a decent amount of time, disabled by touching the screen or entering the pin number. In the case of any bluetooth device attached to the user, the phone could check to see if it's in range before calling. [[User:sin|sin]]<br /> <br /> ==== Movement detection ====<br /> By detecting that the owner is walking a user defined profile can be activated with a specific set of notification settings. For example you may wish to use a cheap old sounding ringtone so you don't attract attention from muggers. Or you may wish to have a louder ringtone if you carry your phone in a bag where it can't be so easily heard.<br /> <br /> ==== Games ====<br /> Imagine a first person shooter that you look around by turning your body.<br /> <br /> ==== Sloshing battery indicator ====<br /> Shaking the phone will produce a sloshing sound, as if it contained a liquid. As the battery loses charge, so the sound produced on being shaken, will replicate a decreasingly empty container. [http://mobile.slashdot.org/article.pl?sid=07/11/28/1342248] for an example.<br /> [http://www.dcs.gla.ac.uk/~jhw/shoogle/index.html Shoogle] [http://www.dcs.gla.ac.uk/~jhw/audioclouds/ Audioclouds] [http://www.dcs.gla.ac.uk/~rod/dynamics.html Dynamics]<br /> <br /> ==== Steady screen ====<br /> It may be hard to read the screen when the device is shaking from some source of vibration. E.g.<br /> * being mounted inside a vehicle<br /> * during certain sports<br /> * while the internal vibrator is activated (perhaps)<br /> The accelerometers could be used to determine the frequency of the shaking and to make the screen appear to be steady by offsetting the contents at the same frequency in the opposite direction. If this was handled by the graphics processor it might not even be an intensive operation or produce significant battery usage.<br /> <br /> At slower movements, (say just being held in an older unsteady hand) the accelerometer data could be fed directly into the screen offset. This would allow you to compensate for unpredictable movements. <br /> <br /> Such a mode would cancel out shaking, producing what would appear to be a slightly smaller but steady screen. (Smaller because pixels at the edge of the screen may not have ''any'' screen in the same location in the next fraction of the vibration). Gross movements that move the screen to an entirely different position would not be cancelled, effectively 'panning' to keep up with the large movement.<br /> <br /> In situations where the hand is not experiencing the same source of vibration that the screen is, the areas of touch sensitivity should be offset at the same time as the screen. So a steady hand touching a vibrating screen isn't interpretted by the application software as a vibrating hand.<br /> <br /> These features would best be implemented in the rendering and touch libraries so they could be activated for all applications.<br /> <br /> ==== Tapping as input ====<br /> If I understand correctly the accelerometer should be capable to be used as a simple input. When OpenMoko is in the pocket, simple taps against the pocket should be possible to use as input. For example when there is an incoming call and the user is notified using a headset then one tap would accept the call and two concurrent taps against the pocket would cancel it. This can also be used for lot more.<br /> ==== Pedometer ====<br /> The accelerometers should be able to detect each step and record it. If the time when the step is recorded you would then be able to determine the time used walking, the distance traveled and approximate the energy used. Acording to [http://en.wikipedia.org/wiki/Pedometer Wikipedia] this has been done in other devices.<br /> <br /> ==== &quot;Spirit&quot; Level ====<br /> The accelerometers don't just detect movement, they also detect the direction of gravitational force. Because the sides of the case are straight, the phone could be used as a torpedo level to determine vertical plumb or horizontal level. The back is flat as well, allowing for two-axis leveling. <br /> <br /> The phone should switch automatically between vertical, horizontal single axis (holding the side of the phone against the top of a beam) and horizontal dual-axis (laying the phone flat on a surface) modes. <br /> <br /> Along the same lines, it could be used as a leveling protractor, to determine slope.<br /> <br /> ==== Others ====<br /> Also see the pages[[Wishlist:Auto Align Map]], [[Wishlist:Determine Position]], [[Distance Measuring]], [[Wishlist:Computer Mouse]], [[Wishlist:Dynamic Screen Orientation]].<br /> <br /> === Connectivity ===<br /> <br /> ==== VNC ====<br /> A good, stylus friendly VNC client/host combo would be easy to add and terribly useful. '''in openembedded'''<br /> <br /> ==== Networked X-Windows ====<br /> <br /> Whether it's running true X-Windowing over the network, or your bog-standard VNC connection as mentioned above, the ability to have your phone's screen available on your laptop or palmtop would be most desirable.<br /> <br /> ==== NX client ====<br /> <br /> A form of X-windows forwarding optimized for performance over slow, or high-latency links, which could prove extremely useful. Capable of streaming a good quality, full desktop session over modem speeds. The protocol and at least one implementation is gpl'd. [http://en.wikipedia.org/wiki/NX_technology wikipedia]<br /> <br /> ==== OpenOffice Presenter Control ====<br /> <br /> I Think it is a good idea to control your OO Presentation with Openmoko about WLAN or Bluetooth.<br /> I think it needs some buttons to go back or forward and control the mouse to show something and take normal mouse clicks.<br /> But with the mouse clicks I think that we need a short time between the clicks in example 1 second. Because when you make a mouse <br /> click than to fast than you must go back.<br /> <br /> Some similar functionality will be implemented during SoC 08. More info at [[OpenMoko Bluetooth remote controller]]<br /> <br /> ==== Amarok and other Media Player remote control ====<br /> <br /> Control Amarok or any other Media Player with OpenMoko (as a remote control). Bluetooth or WLAN could be used as protocol to send and receive the data. Maybe a WebInterface of Amarok is a start. Can be used on parties for a mobile music management.<br /> <br /> ==== Read informations with SMS ====<br /> Send a SMS with Code to the OpenMoko (from a specific number).<br /> For example to send get the GPS coordinates from a stolen Neo (or if you don't know where your Neo is).<br /> <br /> ==== OpenRemote ====<br /> Support an [http://openremote.org/ OpenRemote] controller interface.<br /> <br /> === Security ===<br /> <br /> ==== General Filesystem Encryption ====<br /> <br /> If anyone wants to get your private data saved on your OpenMoko device, he should have to get through a high security mechanism like dm-crypt. The question is how much CPU power would be needed. <br /> Would it be an idea to encrypt only the private data like phone numbers, preferences, address book etc. (like /home/$USER).<br /> <br /> http://luks.endorphin.org<br /> <br /> ==== My Account ====<br /> {{Main|My Account}}<br /> A way to securely store information about the phone, and ensure that a phone you may be considering purchasing is not stolen.<br /> <br /> Can we keep a serial number/user registry here on the OM wiki? Not really secure, but something most thieves wouldn't know about.<br /> <br /> ==== [http://zfoneproject.com/ Zfone] or similar ====<br /> <br /> Something that allows the user to speak with another person securely.<br /> <br /> ==== GSM Encryption ====<br /> <br /> This software application would allow GSM encrypted calls to be made using the GSM Data Call Channel. <br /> <br /> [[OSvS]]<br /> <br /> ==== My Voice is my Passport ====<br /> Use voice recognition to unlock the phone. &quot;Hi. My name is ... My voice is my passport. Verify me.&quot;<br /> <br /> ==== Firewall ====<br /> A network firewall<br /> <br /> ==== Full Mac Support ====<br /> Full mac support, preferably with full software and full sync capabilities with iCal and iMail <br /> <br /> ==== Anti Theft Application ====<br /> <br /> This application would enter the phone into an [[Anti-Theft Mode]] which activates particular security features to reduce the risk of theft and also to ensure a higher probability of recovery of a stolen handset.<br /> <br /> Hmm, if you're away from your home for more than a few days (via GPS), it starts sending its coordinates home.<br /> <br /> ====RFID based personal alerts====<br /> Assuming an RFID reader is available: You'd put an RFID tag on your keys, wallet, etc and train a program on the phone to give you a soft or hard alert when one of them leaves detection range. That way, if you're walking away from one of them, the phone could alert you.<br /> <br /> Actually there is a RFID reader available. Take a look at this: http://www.wdi.ca/ We only need driver for that thing. .... Well, never mind. I think it doesn't work because of the size. Anyway an interesting idea.<br /> <br /> ====OpenVPN Client====<br /> This application allows to configure the device as an OpenVPN client using the GUI including support for X.509 certificates.<br /> <br /> === Integrated Help System ===<br /> <br /> A help system that is either on or off. It could be activated and deactivated by a [[five-second-press]] on a button, for example the AUX button. When the help system is activated, it will explain the use of any item you touch on screen (with stylus or finger). Example: if you touch the battery icon, it will explain that this shows battery level / remaining time. If you touch the date / time icon, it will explain that this icon shows date and time, and that if you press it, you can set date and time. Primarily, this help system should be able to explain all user interface elements in the main screen, but if it proves popular, it could be expanded to cover other applications as well.<br /> <br /> ===Performance optimisation===<br /> ==== Use DMA engine in CPU for blitter ====<br /> The DMA engine in the CPU can substantially speed up moving of large areas of screen in some cases.<br /> <br /> ==== Use virtual screen to optimise scrolling ====<br /> In some other cases, the hardware supported virtual screen may also speed it up.<br /> ===Reusable Display/UI Widgets===<br /> ====Use BigPage for full page zoom, scroll, scale in many apps====<br /> The [[BigPageWidget]] Page decribes a widget that could bring full natural page viewing, scaling, scrolling to the OM platform - allowing all applications to make intuitive UIs. A good way to read documents of any type without reformatting them massively increases the utility of a device with a small screen<br /> <br /> ==Bluetooth==<br /> <br /> === Voice Dialing ===<br /> <br /> Dial by voice commands.<br /> &lt;br&gt;Dial by dictating phone number. This way we can voice dial any number even if not in our contact list.<br /> <br /> === Music through Bluetooth Headset ===<br /> <br /> Music can be played through a Bluetooth headset, but would stop playing when a call comes in.<br /> <br /> === Walkie Talkie ===<br /> <br /> Let OpenMoko devices connect to one another via bluetooth or another connection method (GPRS for long distance but high latency, probably Wifi on P2), and hold a conversation.<br /> <br /> Features for this applications can be:<br /> * Push To Talk (PTT) button<br /> * Voice Activated Control (VAC) which will set it in transmit mode when input has is detected above a certain predefined level.<br /> * Optionally a full duplex mode<br /> * Different channels to choose from<br /> * Monitor different (preselected or all) channels for traffic.<br /> * Content encryption<br /> * Active noise control<br /> * Allow zero config use (units can talk without any access point helping)<br /> * Overview of all connected people trough sending GPS data to everyone who is in the Walkie Talkie channel<br /> <br /> Local (non-GPRS) use cases include chatting while biking<br /> or motorcycling in a group; perhaps also in a car caravan.<br /> This application could also be used as a baby-phone to monitor your siblings.<br /> <br /> This would be more useful if the Neo had Class 1 bluetooth, though probable Wifi on P2 will also offer more range.<br /> <br /> (One thumbs up from me) Jackcday<br /> <br /> See also [[Wish_List#WiFi_Walkie_Talkie|WiFi Walkie Talkie]] and perhaps construct one application that can handle both Bleutooth and Wifi.<br /> <br /> === Automatic Sync ===<br /> <br /> Automatically synchronize with desktop computer (or with any [http://en.wikipedia.org/wiki/SyncML SyncML] server) when within range based on user profile. This may require the use of a secure data transfer.<br /> <br /> === GPS Assisted Bluetooth Management ===<br /> <br /> Allow Bluetooth to automatically turn off after loosing connectivity and to automatically turn back on based upon GPS location.<br /> <br /> A Bluetooth device is configured for automatic reacquisition based on the following profiles:<br /> * Manual - only when Bluetooth is on<br /> * Non-mobile - the target device is not mobile, periodically attempt reacquisition when in the general area of the device.<br /> * Mobile - the target device is mobile, periodically attempt reacquisition when in the general area of the device.<br /> <br /> Each target device is configured as follows:<br /> * Automatic acquisition at last known location: enable/disable<br /> * Automatic acquisition at these locations: list of nickname + coordinates + range<br /> <br /> ==== Non-mobile devices ====<br /> <br /> Examples devices include: computers<br /> <br /> The location and range of the target device is determined via training. Periodically, the current GPS coordinates and Bluetooth signal strength are logged. Additionally, connectivity loss events are logged. An algorithm uses these logs to determine the device location and range.<br /> <br /> Connection attempts are made when in a configurable proximity to the device. The first attempt when entering the proximity and further attempts at a configurable interval.<br /> <br /> ==== Mobile devices ====<br /> <br /> Example devices include: automobiles<br /> <br /> Mobile devices are configured to have two types of locations:<br /> # Last known location<br /> # Non-mobile locations (homes)<br /> <br /> ===== Last known location =====<br /> <br /> A car is mobile, ideally, when you leave your car, the phone should note the car's location when connectivity is lost and then attempt to reacquire the car when you return to the location of the car.<br /> <br /> ===== Non-mobile locations (homes) =====<br /> <br /> As mobile devices may have multiple users, it is not sufficient to always use the last known location. In this case, the device may additionally have multiple homes. For example, a car might have as its homes: home garage and work parking lot.<br /> <br /> === Bluetooth neighbor detection and multiuser apps ===<br /> <br /> Like the [http://en.wikipedia.org/wiki/One_laptop_per_child one laptop per child] (OLPC) interface, keep a number in the status bar that represents a count of other openmoko or compatible bluetooth devices in the area. Allow for the spontaneous initiation of a chatroom or multiplayer game or file trading with any moko in the area.<br /> <br /> === Bluetooth environment detection ===<br /> <br /> Capability to detect when a predetermined bt device enters/leaves bt range and launch a system-wide event accordingly. This would feed not only the &quot;Neighbour detection&quot; idea described above, but also the &quot;Profiles&quot;, &quot;Context based TO-DO list&quot; and &quot;Location-based reminders&quot; ideas. Reminders could be set to trigger in the presence of a specific person X (with BT device Y). Profiles can take into account which devices are present around the phone (car kit, for ex.). To-do list could also change according to present devices.<br /> <br /> === Remote control ===<br /> <br /> ==== Wireless presenter ====<br /> Use the phone to run your OpenOffice.org Impress presentation remotely using Bluetooth. Cool features: <br /> * Display the text notes for the presenter on the phone's display and update it whenever the slide is changing.<br /> ** OO.org has implemented support for [http://www.openoffice.org/issues/show_bug.cgi?id=12719 dual monitor]/[http://www.openoffice.org/issues/show_bug.cgi?id=18486 presenter mode] that can be used as a starting point<br /> * A small timer showing the time passed (and perhaps remaining if the presentation app supports such a feature). <br /> * If you want to be super-cool, you give a preview of the notes of the next slide in the show. <br /> * At the end of a presentation, a &quot;navigator&quot; could allow to easily jump to any slide in the presentation by clicking on it on the phone.<br /> ** When you right-click in a running OO.org Impress presentation, you can choose &quot;got o slide...&quot; and select any slide to jump to.<br /> <br /> Some similar functionality will be implemented during SoC 08. More info at [[OpenMoko Bluetooth remote controller]]<br /> <br /> ==== Initiated from another device ====<br /> Remote control over Bluetooth from other devices to control media player (play, pause, next, previous, volume control), camera (capture image), etc.<br /> ==== Directed at another device ====<br /> Remote control over Bluetooth to other devices to control media player, lights in your house, etc.<br /> <br /> [http://mjr.iki.fi/software/remote-0.9.0.tar.gz Remote] is my draft of a python-based remote control app that allows you to define button sets and commands to run on the local or a remote host (through ssh, for instance). Error handling and command interface need work.--[[User:Mjr|Mjr]] 11:14, 18 October 2007 (CEST)<br /> <br /> Z-wave uses web-browser control of devices that is said to be compatible with mobile phone browsers so should work with openmoko browser. [http://www.z-wave.com www.z-wave.com]<br /> <br /> === Bluetooth Car Connection ===<br /> <br /> Have a deeper connection to the car than just handsfree speakerphone. For instance a transceiver with challenge/response systems to open, possibly even start the car. Possibly go as far as OBD connection to monitor car status on screen/log for later.<br /> <br /> Could be done with a port of [https://garage.maemo.org/projects/carman/ Carman] or similar that can connect to an OBD2 adapter via USB or Bluetooth and display various information collect from the car, GPS, and accelerometers. --[http://wiki.openmoko.org/wiki/User:Bmk789 bmk789]<br /> <br /> ==== Dude, Where's My Car? ====<br /> <br /> When in range of the car navigation system, remember the position (perhaps check with the car GPS). When not in range, assumme that you are not in the car, and offer the opportunity to navigate to the car's last known position. That way, you can find your car e.g. on a large parking lot.<br /> <br /> === [[Bluetooth powered Multi-SIM support]] ===<br /> <br /> As the Neo1971 does not come with dual-SIM support this could be solved by joining your old bluetooth-enabled mobile to your OpenMoko-phone.<br /> <br /> Let SIM card A be in your OpenMoko-phone and SIM card B in your old mobile:<br /> * Incoming call on SIM card B - the OpenMoko-phone acts as a headset(Bluetooth Headset profile)<br /> * Calling out via SIM card B - the OpenMoko-phone acts again as a headset<br /> * Same for Short Messages/MMS/Internet<br /> This way you'd have your old phone switched silent and connected to your OpenMoko-phone that handles all the calls and one can select which SIM card to use.<br /> Advantage: No 'switching' between cards<br /> Disadvantage: Second mobile needs to be in range(e.g. handbag) and charged every once in a while.<br /> <br /> ===Internet Gateway===<br /> <br /> If the device could function as a Bluetooth router/gateway to the internet via the GPRS/data connector, then you could use it to get network connectivity from your laptop and other devices while on the road. Many smartphones can be configured as modems via Bluetooth for use as Dial-Up Networking connectors, and that should be the minimum target. Ideally, if the WiFi functionality was used so the OpenMoko could be an 802.11 router or peer to peer gateway for a laptop, this would be even better. The full bandwidth of GPRS or whatever network is available would then be available.<br /> <br /> === Social Networking ===<br /> <br /> Anybody running the social networking app will be broadcasting a profile, and when certain keywords are matched with other users who are also running the application, an alert is sounded. Each mokoid can be added as a hexstring to a profile page, and xml filters can be developed for each social service to convert various keywords and interests to moko-friendly format.<br /> <br /> === Give userspace api control over bluetooth signal strength ===<br /> <br /> I have tried bluetooth handsfree sets with other phones and don't get perfect reception due to low signal strength. I suppose the reason the signal is so weak is because the manufacturer wants the battery to last long on its latest charge. Can you please make the strength setting configurable by the user of the phone through an api and perhaps even through the phones gui? I would gladly waste some battery time in exchange for stronger bluetooth signal strength.<br /> <br /> === UMTS tether mode ===<br /> <br /> Support UMTS via tether mode over Bluetooth (see [[UMTS]] for detailed information).<br /> <br /> == USB ==<br /> <br /> === UMTS tether mode ===<br /> <br /> Support UMTS via tether mode over USB (see [[UMTS]] for detailed information).<br /> <br /> == WiFi ==<br /> <br /> === Industrial grade Wifi management ===<br /> One annoyance I've had with Wifi enabled gadgets is that they simply keep the connections in a dumb list. What I'd like to see is more granular connection management, which enables me to specify whether a given connection is friend &amp; family (mom's place), professional client (joe's copies and coffee), commercially available (panera), onetime use, or anything else, as well as managing router config backups, firmware images, and security keys.<br /> <br /> : [[User:lally|Lally]] 13:01 12 May 2008 (EST) -- Profiles of connections. Mac OS (9 &amp; X) have 'Locations', which do exactly that. A UI for setting up/choosing them is nice, plus maybe some GPS-driven autoselection.<br /> <br /> === Captive portal auto-login support ===<br /> Having a nice front-end to some sort of script that checks the authenticity of a captive portal login page (SSL cert), then passes your username and password login information to automatically log you into your account would be very nice as well. This can be done with curl, but it is difficult to make it work on all captive portals out there. Perhaps just a field that you can specify &quot;once I am connected to this AP, run this script: &quot;.<br /> <br /> === WiFi Walkie Talkie ===<br /> Provide walktie talkie functionality like http://www.domain17.net/walkietalkie/index.html See also [[Wish_List#Walkie_Talkie|Bluetooth Walkie Talkie]] and perhaps construct one application that can handle both Bleutooth and Wifi.<br /> <br /> === UMTS tether mode ===<br /> <br /> Support UMTS via tether mode over WiFi (see [[UMTS]] for detailed information).<br /> <br /> == Wireless Piggyback ==<br /> <br /> HSDPA support and the like, so that users can connect directly with the internet with G3/G4 mobile service providers at speeds at or above 3.6 Mb/s.<br /> <br /> == Other ==<br /> <br /> === Auto Update ===<br /> <br /> A small tool which is configurable to download the latest OpenMoko and OpenMoko related software. Maybe if any internet connection is available or a minimum of bandwith is available then the auto update would download only security related or the whole system etc. .<br /> <br /> === Vibrate Pattern Recorder ===<br /> <br /> An application that would allow the user to define their own vibration patterns, and possibly link them to audio files. Recording would be done in real time initiated with a &quot;Record&quot; button, optionally playing the associated sound file in sync with recording). While recording, the user would press and hold a button to define the timing and duration of vibration. The user would press &quot;Stop&quot; when finished. Vibration patterns would have the option of being looped(would terminate at some global ringtone length maximum).<br /> <br /> One simple suggested vibration file format would be a sort of run-length encoding: First byte defines the length of a &quot;time-slice&quot; in milliseconds, which would determine the overall tempo(actually the inverse of tempo). The next byte would define the number of time-slices to leave the vibration on, and then another byte for how long to pause after. Continue alternating these on/off bytes until the entire pattern is defined.<br /> <br /> - or just use MIDI, using a separate channel for the vibrator.<br /> <br /> An implementation of RTTL could also be used to define vibration patterns.<br /> <br /> === PC Input Device ===<br /> <br /> Provide a method to use the touchscreen as input device for a nearby desktop machine. Could connect over USB or bluetooth.<br /> <br /> Could emulate a pointer device (mouse) or even keyboard using standard bluetooth/USB interfaces for such a device.<br /> <br /> Use case: Alice is lazing on a couch and doesn't want to get up to do some minor interaction with the computer. She can see the screen and uses the OpenMoko device as a mouse and/or keyboard to interact with the computer.<br /> <br /> === Advanced Notification And Ringtone Manager ===<br /> {{Main|Wishlist-ANARM}}<br /> <br /> ANARM would be an application for handling all event-based audible notifications from an OpenMoko device.<br /> <br /> === Location based reminders ===<br /> {{Main|Wishlist:Location_based_reminders}}<br /> Location based reminders can be used to notify users of various events or reminders that are location based.<br /> <br /> === Synergy Client ===<br /> A synergy client would enable the user to place the device next to a desktop PC and share the desktop`s mouse, keyboard and clipboard over a TCP/IP network. [http://synergy2.sourceforge.net/ Synergy]<br /> <br /> === Next device ===<br /> List features for your fantasy device to come from FIC (or anyone else, for that matter). Define the GTA03 here ;-)<br /> <br /> ==== There is no device ====<br /> From [http://wurp.blogspot.com/2008/01/teh-future.html Wurp's blog]:<br /> <br /> Clearly the Next Big Thing has to be for the device to go away altogether. I know the basic idea for wearables has been around forever, but it seems to me that the time has come.<br /> <br /> I wanna wear a bluetooth earpiece and cool shades, possibly with [ here's where my imagination is failing me :-( ] gloves, or fingerless gloves, or (ew) wristbands, and let any surface, including my hand, or no surface, be my interface. Tap the earpiece when you get a phone call, see a dial pad on your palm and tap out the number with the other hand, watch movies on a giant screen hovering in the air...<br /> <br /> (equipment list: bluetooth earpiece, some brick in my pocket or on my belt, glasses w/ minute camera, painted video display, &amp; variable darkness lenses, and gloves)<br /> <br /> Why the hell do I want to dig out a device every time I want mindless entertainment or superficial conversation?<br /> <br /> Ideally, you could then sell any little doohickey with whatever interface you want (switches, knobs, g-spots, ...) and all it needs to do is network with some software on the brick to be anything at all...<br /> <br /> A rubberized shell, like some of the other new phones. Helps me not drop it, especially when drunken wardriving. [anon ;-)]<br /> <br /> ====Phone subsidies====<br /> Get carriers to give you an Openmoko like they will give away other phones when you sign a contract.<br /> <br /> == GPS Software ==<br /> * implement &quot;Cheap GPS&quot; as demonstrated in the image, may be useful for geocaching.<br /> [[Image:Cheap_gps.png|right|300px|From xkcd.com :-)]]<br /> *Providing GPS Support also for outdoor users in addition to ordinary street navigation features<br /> ** Overlay of satellite images with existing streetmaps<br /> ** Incorporating SRTM digital elevation model: for example using the VRML/X3D as data format (see http://www.ai.sri.com/geovrml/) which is interesting for e.g. mountaineering: using a 3d browser rendering VRML/X3D Model, displaying the current position and track (possibly also other gps-tracks of the different routes to a summit downloaded before could be mapped onto the 3d model), (what about 3d hardware support? there is nothing written in the hardware specs about graphics: thinking of OpenGL for embedded systems (see http://www.khronos.org/opengles/)<br /> ** Using sth like a tracking mode to allow certain people to determine the current position and track (for rescue missions - like they have for example at http://www.steiger-stiftung.de (a German beneficence for rescue issues) There you can register your mobile phone so the rescue service is able to track you immediately if necessary. The interesting thing: It seems like some mobile phones with GPS have special support for this issue. If your phone is registered, the rescue service is able to get your GPS coordinates directly from the phone without any user assistance. Openmoko should also support this! )<br /> * Implementation of 3dTracking's (http://free.3dtracking.net/) tracking software or equivalent.<br /> * &quot;Geomark&quot; function: if you have to save the current time with your current location, only hit one button...<br /> ** You also should be able to navigate with a small &quot;compass&quot; and the distance should be displayed to your saved point (maybe where you parked your car on a big car parking area)...<br /> * '''Measure the distance between two points (air line or walked way) -&gt; no need for a tape measure'''<br /> **I think it would be good if you could either use Bluetooth, GPRS or AdHoc Wifi, and see near Neo1972 on the GPS map so you could see where your friends are, e.g &quot;You want to know if you friend is on the bus behind&quot; You would need a strong wifi and GPRS would be too expensive.<br /> *A bicycle sat-nav would be cool, speciayl designed for bicycles, e.g. cycle routes<br /> * A user friendly app to collect data for the open street map project. http://www.openstreetmap.org/<br /> * '''GPS proxy''' - allowing other people to use and share GPS data from NEO over bluetooth {{Main|Wishlist:Software:GPS proxy}} <br /> &lt;br&gt;[[Community Based Traffic Information]]<br /> <br /> == Hardware ==<br /> {{Main|Wish List - Hardware}}<br /> <br /> It could be use for beepway Online service too <br /> [http://www.beepway.com]<br /> <br /> === Dedicated Power / Charger Pinout ===<br /> <br /> Having not yet seen a physical Neo device, I haven't been able to examine any of the IOs to see if there already is a dedicated power / charger input. However, I can imagine that it might be very tempting to have the device charge solely via USB. For any device that is capable of USB-host, that is a '''horrible''' idea.<br /> <br /> Since the device is able to run in USB host mode, it might be a good idea to allow for an alternate power supply, if say, a USB keyboard was being used for several hours. Rather than drain the battery, one could just supply power via the wall outlet while still providing endless hours of USB-host enjoyment for those hard-coders on the go.<br /> <br /> The main question is just deciding on where to take power from if in USB-client mode and the power cable is inserted, but really, that's not too big of a deal and can be solved with very minimal circuitry.<br /> <br /> This might sound extraneous at first, but when the device shuts down in the middle of an important USB file transfer, or right before that great piece of code was saved, you can bet that those users will be saying &quot;Hmm... a separate power adapter would have really come in handy right now&quot;. <br /> <br /> I suggest a tiny 3mm, dedicated +5V power input (something a la Nokia).<br /> <br /> === Inductive charging ===<br /> <br /> [http://en.wikipedia.org/wiki/Inductive_charging Inductive charging] is the sort of charging where you place the device in a cradle, and a coil in the cradle induces a current in a coil inside the device, allowing it to recharge without wires. This should eliminate proprietary power connections.<br /> <br /> === Tactile feedback via buzzer ===<br /> Assuming the hardware has a vibrator/buzzer for silent calls, use a lightly pulsed version of that to simulate tactile feedback when dragging finger across buttons on-screen. Implemented properly, it would almost feel as if the buttons were real.<br /> : 25 ms bump on the buzzer feels about right. Does this harm the vibrator motor? --[[User:Sagacis|Sagacis]] 05:15, 2 October 2007 (CEST)<br /> :: Created a patch to do this [[User:Sagacis/ForceFeedback]] --[[User:Sagacis|Sagacis]] 05:05, 3 October 2007 (CEST)<br /> <br /> === Detachable keyboard ===<br /> Hardware keyboard that can be attached with magnets to a future version of the Neo.<br /> <br /> A bluetooth mini-qwerty keyboard that straps to my wrist!<br /> <br /> : A BT keyboard would be nice, but do you need openmoko to provide it? [[http://www.intomobile.com/2007/11/07/targus-bluetooth-mobile-tumbpad-when-the-tiny-keyboard-on-your-smartphone-just-doesnt-cut-it.html Targus bluetooth keyboard]]<br /> <br /> === SD Card Slot ===<br /> I think the Neo1973 should have a normal SD card slot as the micro is too small, and the SDs have more space. [unknown author]<br /> <br /> SD Cards now support 32GB. Their storage density will always be multiples ahead of microSD (now at only 2GB). An SD Card slot will:<br /> * Provide enough storage to '''turn an OpenMoko into a music (MP3) jukebox''' large enough for entire music collections, like an iPod with Bluetooth for the car.<br /> * Enable '''storage''' of:<br /> ** podcasts, full-length movies, or large photo collections<br /> ** photo and video from an on-board high-res camera<br /> ** entire email database at your fingertips, even in poor phone signal areas<br /> ** more detailed maps and charts<br /> ** encrypted work databases that are not available online<br /> * Have easy '''external access''', without requiring battery removal like the microSD card<br /> * Support '''SDIO''' accessories<br /> * Enable '''transfer''' of data from an external camera's full SD memory to:<br /> ** a portable USB hard drive, offsetting the need to travel with a notebook PC<br /> ** the internet, via wifi or phone network<br /> * Enable editing of videos and photos obtained from external cameras<br /> <br /> Without an easily accessible higher storage SD Card slot, many users will soon be playing the juggling game of which data to delete from the much smaller and harder to swap microSD card. This is especially true for OpenMoko users, who are more likely to be power users than is the average mobile phone carrying population. Why carry an OpenMoko and an iPod, when you can simply add an SD Card slot?<br /> --[[User:Pedro|Pedro]] 20:06, 17 March 2008 (CET)<br /> <br /> : This is not true. Now you can find 2GB micros at the price of 20-30 euros. Too small for what?? --[[User:V0n0|V0n0]] 22:06, 28 December 2007 (CET)<br /> <br /> : Think of putting a few '''movies''' on that SD memory card. It could really help if it was a little bigger (8GB, 16GB, 32GB). Also think of going '''offline''' for 1-2 weeks, far away from any computer you can access and then wanting to listen to some music. What you get in turn with a 2 GB memory slot is the same music over and over. Or you have to switch memory a cards a lot.<br /> <br /> : This situation is far more common than one would think: going in the mountains, going offshore (on a cruise ship). Or simply you may want to store many types of music, and '''share''' your device with friends. --[[User:Bogdanbiv|Bogdanbiv]] 13:47, 10 January 2008 (EEST)<br /> <br /> : Well, it can be micro SD, but why to put it so deep inside, under the battery and even under the SIM card? I would suggest to have a simple slot on the side where we could insert/remove the SD card equally easily as we swap CD's in computer. [[User:AudriusA|AudriusA]] 16:36, 12 January 2008 (CET)<br /> <br /> [[User:Cfriedt|Cfriedt]] 12:40, 24 February 2008 (CET) -- I completely agree with a more accessible SD card slot. It should be made external for quick removal / insertion. I realize that would mean program data shouldn't reside on the SD, but really 256 MB of on-board flash is plenty. Micro or normally-sized, a regular-sized SD is still trivial to implement in terms of solder pads and traces.<br /> <br /> : Sorry, but this looks like useless chat. Micro-SD cards are perfect for mobile devices as they don't get too much space on the pcb. Also, we can find micro-sd up to 8gb, if you want more space just wait a while and they'll produce a bigger one in a few months :-p. Really, almost every single phone that has a sd slot has in its micro version, why would we need a full-sized, huge normal sd slot ? It gets too much space on the pcb it's not only about sw configuration or pin soldering, it's more regarding pcb layout.<br /> <br /> : What about something like this adapter[http://linitx.com/viewproduct.php?prodid=11922]? Is there any place in the case left to put this into? Nevertheless there is a 12GB microSD card announced from SanDisk and a 8GB card costs about 40€ or 15€ for 4GB. (But a 8GB SD card costs only about 25€) --[[user:kelvan|Kelvan]]<br /> <br /> : Maybe just an additional microSD that is easily accessible and hot-swappable. I imagine replacing the huge lanyard hole could help with this. --[[User:Sin|Sin]] 02:30, 4 May 2008 (CEST)<br /> <br /> : My thoughts exactly. Two slots: 1 internal microSD for our storage, and a second external one for more immediate expansion. My thoughts are more towards hardware expansion. For example, some of us could put in a second wifi card that does have promiscuous mode. External VGA connections, etc would also be possible. The external slot should be chosen by availability of hardware expansions as well as memory availability/price. --[[User:lally|Lally]] 13:01 12 May 2008 (EST)<br /> <br /> === IR port ===<br /> Remote control applications<br /> <br /> Would be great to use openmoko as a Harmony remote controller.<br /> <br /> :I'd like to add that i fully support this. An IR port on future openmoko devices capable of controlling set-top boxes like TV/DVD/Stereo is necessary to make the device as universal as possible. A cellphone should be your window to the world and allow you to interact with it in as many ways as possible.<br /> <br /> :Care must be taken to use the correct type of IR chipset/controller in the phone. Most IR ports you find on devices like computers, some cellphones etc. Are for high speed data communication and CAN'T control TVs/DVDplayers/Stereos etc.<br /> <br /> :In order to reduce cost it maybe possible to use the sound chipset in the phone to generate the waveform sent to the IR led. IR remotes work at ~38Khz which is within the range of the sound chipset. The sound output could be internally switched between the IR led or the speakers.<br /> <br /> ===USB Monitor===<br /> Have a few different models of monitors, maybe 7 inch, 14 in and 19 inches... be able to plug the Openmoko into one, and then use it like a desktop. Then be able to plug other peripherals into the monitor (keyboard, laser mouse, thumb drive, camera, etc.) and use those. Better yet, be able to use Bluetooth for the keyboard, mouse, thumb drive, camera, and so forth.<br /> <br /> ===Firefox Mobile UI===<br /> Integrate the whole interface with this Firefox mobile concept: [http://azarask.in/blog/post/firefox-mobile-concept-video/].&lt;br&gt;<br /> Eg. Kernel-&gt;OS-&gt;Browser-&gt;Webapps/Dailer/Contacts..&lt;br&gt;<br /> More info om this concept here: FennecVision [http://wiki.mozilla.org/Mobile/FennecVision]<br /> <br /> <br /> [[Category:User]]<br /> [[Category:Ideas| ]]</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-08-07T22:20:17Z

<p>Wurp: /* Tasks &amp; status */</p> <hr /> <div>{{Distributions|SHR}}<br /> <br /> == Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the [[Openmoko2007.2]] GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br /> <br /> (We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br /> <br /> Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br /> <br /> == Why SHR exists ==<br /> This is long and rambling, and maybe more of a tirade than information, but it does give some background on why this project was started. The overview gives, well, the overview, this is more of a deeper examination of the existing releases and why we felt we needed something new.<br /> <br /> Feel free to skip this whole section if you already think SHR is a good idea :-)<br /> <br /> === Why not ASU? ===<br /> ASU is the distro that OM is putting their main effort into right now. ASU looks very slick, but is very unstable right now, and is likely to be unstable and feature-poor for some time.<br /> <br /> === Why not 2007.2? ===<br /> 2007.2 is the &quot;old&quot; Openmoko distribution, now unsupported. Unsupported == often broken. Also, neither calls nor suspend/resume ever worked reliably.<br /> <br /> === Why not Qtopia? ===<br /> You can also install Qtopia on the phone.<br /> <br /> Qtopia is stable but you can only build qt apps on Qtopia, which means lots of linux apps you might want to port suddenly got a lot harder to port. And some people just don't like developing for qt.<br /> <br /> Also, as far as I know, there is no documented build procedure for Qtopia on Openmoko.<br /> <br /> === Why not FSO? ===<br /> FSO is the initiative by Mickey Lauer and crew to create a good [[D-Bus]] infrastructure which runs on the neos, among other devices.<br /> <br /> FSO is by far the most stable &amp; usable release, if all you want is a phone. (I mean *all*. It just has a dialer right now, not even call history.)<br /> <br /> FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br /> <br /> Other people are supposed to put a front end on FSO. So that's what we're doing.<br /> <br /> === Why SHR? ===<br /> So SHR is FSO, with us doing the necessary work to port the old high-functionality 2007.2 stuff on a stable call platform. We have an adapter from the 2007.2 call service to the FSO call service and we're installing the basic 2007.2 apps on the FSO baseline install.<br /> <br /> In theory, it should be very simple, and should give us dialer, contact management, SMS, terminal, media player, gps app, etc. since all those already work on 2007.2. And the dialer should be stable, which it wasn't in 2007.2<br /> <br /> == First steps ==<br /> The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br /> <br /> We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br /> <br /> == Interest ==<br /> Here's a list of people who've expressed an interest in working on the SHR.<br /> <br /> * [[User:Wurp|wurp2]]<br /> * [[User:Ferric|ferric]]<br /> * [[User:Paulproteus|paulproteus]]<br /> * [[User:Ainulindale|Ainulindale]]<br /> * [[User:jluis|Jose Luis]]<br /> * [[User:Kevin_Dean|Kevin Dean]]<br /> * [[User:Cb22|cb22]]<br /> * [[User:Jeremy-list|Jeremy List]]<br /> * mwester<br /> * [[User:MarcOChapeau|MarcO'Chapeau]]<br /> * [[User:kd8ikt|kd8ikt]]<br /> * [[User:Mywave|Mywave]]<br /> * [[User:nigelTheBold|Anthony Taylor]]<br /> * [[User:Pwgen|Eric Weiss]]<br /> * [[User:Andre613|Andre Racicot]]<br /> <br /> == How to join ==<br /> * Please add your name (with a link to your user page) to the list above.<br /> * You should also send a request to join on the [http://projects.openmoko.org/projects/shr SHR project] on the OM projects page to join.<br /> * Join [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel shr-devel@lists.projects.openmoko.org] and send an introductory email.<br /> <br /> The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.<br /> <br /> See [[SHR Development]] to find out how to set up your development environment to work on existing SHR packages.<br /> <br /> Hang out in #openmoko-cdevel on chat.freenode.net between 5pm and 11pm GMT to chat with the people developing SHR. (Primarily MarcOChapeau and Ainulindale.)<br /> <br /> == Tasks &amp; status ==<br /> Here's a list of the tasks for the SHR:<br /> {|cellpadding=&quot;6&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |Comment<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space; just need to talk about git branches<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |<br /> |-<br /> |Implement libframeworkd-glib<br /> |alpha. <br /> |[[User:Ainulindale|Ainulindale]]<br /> |<br /> |2008-08-07<br /> |Usable for call purposes / network registration and such.<br /> |-<br /> |port 2007.2 dialer2 (now dialer3) to use ophoned instead<br /> |Pre-Alpha<br /> |[[User:Ainulindale|Ainulindale]]<br /> |MarcOChapeau<br /> |2008-07-28<br /> |<br /> |-<br /> |port 2007.2 gsm-panel apps to use ophoned instead<br /> |Beta<br /> |[[User:Ainulindale|Ainulindale]]<br /> |no one yet<br /> |2008-07-30<br /> |Should be tested regarding the signal strength updates.<br /> |-<br /> |switch media player to use alsa directly<br /> |not started<br /> |[[User:Abraxa|Abraxa]]<br /> |no one yet<br /> |2008-07-30<br /> |<br /> |-<br /> |verify that no other important apps in 2007.2 need ported off of pulseaudio (perhaps by putting all 2007.2 apps (minus pulseaudio) on FSO milestone 2 and verifying which ones still have sound :-)<br /> |not started<br /> |no one yet<br /> |no one yet<br /> |2008-07-30<br /> |<br /> |-<br /> |get neod workalike that uses ophoned to determine if you're on a call<br /> |Pre-Alpha<br /> |No one yet<br /> |no one yet<br /> |2008-07-28<br /> |<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |[[User:Kevin_Dean|Kevin Dean]]<br /> |Nobody<br /> |2008-07-05<br /> |<br /> |-<br /> |[[#List_of_packages_included|Identify packages to go into SHR]]<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Anyone &amp; everyone<br /> |2008-07-12<br /> |<br /> |-<br /> |Identify differences between FSO &amp; 2007.2 that need investigation<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-12<br /> |<br /> |-<br /> |Integrate [http://moko.mwester.net/fixes.html mwester's pulseaudio resume fix] into SHR<br /> |Not started<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-15<br /> |<br /> |-<br /> |Create messages3 as a copy of 2007.2's messages2 and get it compiling (comment out phonekit calls)<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |port messages3 to use libframework-glib<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |Create contacts3 as a copy of 2007.2's contacts2 and get it compiling (comment out phonekit calls)<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |port contacts3 to use libframework-glib<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |make ophonekitd switch the sound over to gsmhandset when a call is initiated/received<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |port dialer2's journal to dialer3/ophonekitd/libframework-glib<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |}<br /> <br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |fork media player for SHR<br /> |Done!<br /> |2008-08-07<br /> |<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> == Technical Help ==<br /> <br /> === SVN ===<br /> <br /> We're currently hosted by [[User:Ainulindale|Ainulindale]] on svn://daria.forty-two.fr/shr as projects went down for a whole week-end.<br /> <br /> === Build logic ===<br /> <br /> Current applications (dialer3 and openmoko-panel-gsm) use frameworkd.<br /> So in order to be able to build and test these applications, you have to build frameworkd (MS2) and gsm0710muxd.<br /> <br /> === [[libframeworkd-glib]] ===<br /> <br /> In order to be able to use in an easy way frameworkd, without bothering about dbus calls (which could be difficult for new developers), we built a library allowing everyone to use the functions of frameworkd as if it were simple C functions. We're using asynchronous callbacks for dbus.<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * ophoned<br /> * preferencesd<br /> * pimd<br /> * odeviced<br /> * lots more...<br /> <br /> From 2007.2:<br /> * TODO<br /> * lots more...<br /> <br /> From ASU:<br /> * TODO<br /> * lots more...<br /> <br /> == Project links ==<br /> [http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br /> <br /> == IRC conversation about how we're using revision control ==<br /> <br /> ''This is deprecated, for now we use shr-devel as our only repository. This will change after the first SHR release.''&lt;br/&gt;<br /> From 2007-07-07<br /> &lt;pre&gt;<br /> 12:36 &lt; wurp2&gt; Everything *new* goes on OM projects site<br /> 12:36 &lt; Ainulindale&gt; I totally agree<br /> 12:36 &lt; wurp2&gt; Updates to 2007.2 apps go back into the home svn<br /> 12:36 &lt; Ainulindale&gt; paulproteus: no, you're an external cabal all by yourself<br /> :-)<br /> 12:36 &lt; cb22&gt; anyone planning on drawing up a roadmap?<br /> 12:36 &lt; paulproteus&gt; cb22, We can do that in Trac in fact.<br /> 12:36 &lt; wurp2&gt; And changes to the underlying release go as patches into our OE<br /> branch, yes?<br /> 12:36 &lt; paulproteus&gt; (or on the wiki page)<br /> 12:36 &lt; paulproteus&gt; wurp2, Right<br /> 12:36 &lt; paulproteus&gt; mwester, Sanity-check my terminology where I mess things<br /> up!<br /> 12:37 &lt; Ainulindale&gt; hmmm fuzzy for me but what should go in OM and what should<br /> go in OE ?<br /> 12:37 &lt;@mwester&gt; Sure<br /> 12:37 &lt;@mwester&gt; What do you mean by OM?<br /> 12:37 &lt; paulproteus&gt; Ainulindale, New software we write goes in the<br /> projects.openmoko.org.<br /> 12:37 &lt;@mwester&gt; right.<br /> 12:37 &lt; Ainulindale&gt; Ok so the wrapper for example<br /> 12:37 &lt; wurp2&gt; Anything stand-alone goes in OM (projects.openmoko.org)<br /> 12:37 &lt; wurp2&gt; yeah<br /> 12:37 &lt;@mwester&gt; So we will use projects.openmoko.org for as much as we can,<br /> and OE to build the distro.<br /> 12:37 &lt; Ainulindale&gt; Sounds right to me<br /> 12:37 &lt; wurp2&gt; Great!<br /> 12:38 &lt;@mwester&gt; We *will not* use the OM git repo, as that is owned and<br /> controlled by Openmoko the company...<br /> &lt;/pre&gt;<br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]<br /> [[Category:SHR]]</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-08-07T22:18:25Z

<p>Wurp: /* Tasks &amp; status */</p> <hr /> <div>{{Distributions|SHR}}<br /> <br /> == Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the [[Openmoko2007.2]] GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br /> <br /> (We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br /> <br /> Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br /> <br /> == Why SHR exists ==<br /> This is long and rambling, and maybe more of a tirade than information, but it does give some background on why this project was started. The overview gives, well, the overview, this is more of a deeper examination of the existing releases and why we felt we needed something new.<br /> <br /> Feel free to skip this whole section if you already think SHR is a good idea :-)<br /> <br /> === Why not ASU? ===<br /> ASU is the distro that OM is putting their main effort into right now. ASU looks very slick, but is very unstable right now, and is likely to be unstable and feature-poor for some time.<br /> <br /> === Why not 2007.2? ===<br /> 2007.2 is the &quot;old&quot; Openmoko distribution, now unsupported. Unsupported == often broken. Also, neither calls nor suspend/resume ever worked reliably.<br /> <br /> === Why not Qtopia? ===<br /> You can also install Qtopia on the phone.<br /> <br /> Qtopia is stable but you can only build qt apps on Qtopia, which means lots of linux apps you might want to port suddenly got a lot harder to port. And some people just don't like developing for qt.<br /> <br /> Also, as far as I know, there is no documented build procedure for Qtopia on Openmoko.<br /> <br /> === Why not FSO? ===<br /> FSO is the initiative by Mickey Lauer and crew to create a good [[D-Bus]] infrastructure which runs on the neos, among other devices.<br /> <br /> FSO is by far the most stable &amp; usable release, if all you want is a phone. (I mean *all*. It just has a dialer right now, not even call history.)<br /> <br /> FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br /> <br /> Other people are supposed to put a front end on FSO. So that's what we're doing.<br /> <br /> === Why SHR? ===<br /> So SHR is FSO, with us doing the necessary work to port the old high-functionality 2007.2 stuff on a stable call platform. We have an adapter from the 2007.2 call service to the FSO call service and we're installing the basic 2007.2 apps on the FSO baseline install.<br /> <br /> In theory, it should be very simple, and should give us dialer, contact management, SMS, terminal, media player, gps app, etc. since all those already work on 2007.2. And the dialer should be stable, which it wasn't in 2007.2<br /> <br /> == First steps ==<br /> The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br /> <br /> We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br /> <br /> == Interest ==<br /> Here's a list of people who've expressed an interest in working on the SHR.<br /> <br /> * [[User:Wurp|wurp2]]<br /> * [[User:Ferric|ferric]]<br /> * [[User:Paulproteus|paulproteus]]<br /> * [[User:Ainulindale|Ainulindale]]<br /> * [[User:jluis|Jose Luis]]<br /> * [[User:Kevin_Dean|Kevin Dean]]<br /> * [[User:Cb22|cb22]]<br /> * [[User:Jeremy-list|Jeremy List]]<br /> * mwester<br /> * [[User:MarcOChapeau|MarcO'Chapeau]]<br /> * [[User:kd8ikt|kd8ikt]]<br /> * [[User:Mywave|Mywave]]<br /> * [[User:nigelTheBold|Anthony Taylor]]<br /> * [[User:Pwgen|Eric Weiss]]<br /> * [[User:Andre613|Andre Racicot]]<br /> <br /> == How to join ==<br /> * Please add your name (with a link to your user page) to the list above.<br /> * You should also send a request to join on the [http://projects.openmoko.org/projects/shr SHR project] on the OM projects page to join.<br /> * Join [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel shr-devel@lists.projects.openmoko.org] and send an introductory email.<br /> <br /> The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.<br /> <br /> See [[SHR Development]] to find out how to set up your development environment to work on existing SHR packages.<br /> <br /> Hang out in #openmoko-cdevel on chat.freenode.net between 5pm and 11pm GMT to chat with the people developing SHR. (Primarily MarcOChapeau and Ainulindale.)<br /> <br /> == Tasks &amp; status ==<br /> Here's a list of the tasks for the SHR:<br /> {|cellpadding=&quot;6&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |Comment<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space; just need to talk about git branches<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |<br /> |-<br /> |Implement libframeworkd-glib<br /> |alpha. <br /> |[[User:Ainulindale|Ainulindale]]<br /> |<br /> |2008-08-07<br /> |Usable for call purposes / network registration and such.<br /> |-<br /> |port 2007.2 dialer2 (now dialer3) to use ophoned instead<br /> |Pre-Alpha<br /> |[[User:Ainulindale|Ainulindale]]<br /> |MarcOChapeau<br /> |2008-07-28<br /> |<br /> |-<br /> |port 2007.2 gsm-panel apps to use ophoned instead<br /> |Beta<br /> |[[User:Ainulindale|Ainulindale]]<br /> |no one yet<br /> |2008-07-30<br /> |Should be tested regarding the signal strength updates.<br /> |-<br /> |switch media player to use alsa directly<br /> |not started<br /> |[[User:Abraxa|Abraxa]]<br /> |no one yet<br /> |2008-07-30<br /> |<br /> |-<br /> |verify that no other important apps in 2007.2 need ported off of pulseaudio (perhaps by putting all 2007.2 apps (minus pulseaudio) on FSO milestone 2 and verifying which ones still have sound :-)<br /> |not started<br /> |no one yet<br /> |no one yet<br /> |2008-07-30<br /> |<br /> |-<br /> |get neod workalike that uses ophoned to determine if you're on a call<br /> |Pre-Alpha<br /> |No one yet<br /> |no one yet<br /> |2008-07-28<br /> |<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |[[User:Kevin_Dean|Kevin Dean]]<br /> |Nobody<br /> |2008-07-05<br /> |<br /> |-<br /> |[[#List_of_packages_included|Identify packages to go into SHR]]<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Anyone &amp; everyone<br /> |2008-07-12<br /> |<br /> |-<br /> |Identify differences between FSO &amp; 2007.2 that need investigation<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-12<br /> |<br /> |-<br /> |Integrate [http://moko.mwester.net/fixes.html mwester's pulseaudio resume fix] into SHR<br /> |Not started<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-15<br /> |<br /> |-<br /> |Create messages3 as a copy of 2007.2's messages2 and get it compiling (comment out phonekit calls)<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |port messages3 to use libframework-glib<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |Create contacts3 as a copy of 2007.2's contacts2 and get it compiling (comment out phonekit calls)<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |port contacts3 to use libframework-glib<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |make ophonekitd switch the sound over to gsmhandset when a call is initiated/received<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |port dialer2's journal to dialer3/ophonekitd/libframework-glib<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |}<br /> <br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |fork media player for SHR<br /> |Done!<br /> |Dunno, Julien told me it's done :-)<br /> |2008-08-07<br /> |<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> == Technical Help ==<br /> <br /> === SVN ===<br /> <br /> We're currently hosted by [[User:Ainulindale|Ainulindale]] on svn://daria.forty-two.fr/shr as projects went down for a whole week-end.<br /> <br /> === Build logic ===<br /> <br /> Current applications (dialer3 and openmoko-panel-gsm) use frameworkd.<br /> So in order to be able to build and test these applications, you have to build frameworkd (MS2) and gsm0710muxd.<br /> <br /> === [[libframeworkd-glib]] ===<br /> <br /> In order to be able to use in an easy way frameworkd, without bothering about dbus calls (which could be difficult for new developers), we built a library allowing everyone to use the functions of frameworkd as if it were simple C functions. We're using asynchronous callbacks for dbus.<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * ophoned<br /> * preferencesd<br /> * pimd<br /> * odeviced<br /> * lots more...<br /> <br /> From 2007.2:<br /> * TODO<br /> * lots more...<br /> <br /> From ASU:<br /> * TODO<br /> * lots more...<br /> <br /> == Project links ==<br /> [http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br /> <br /> == IRC conversation about how we're using revision control ==<br /> <br /> ''This is deprecated, for now we use shr-devel as our only repository. This will change after the first SHR release.''&lt;br/&gt;<br /> From 2007-07-07<br /> &lt;pre&gt;<br /> 12:36 &lt; wurp2&gt; Everything *new* goes on OM projects site<br /> 12:36 &lt; Ainulindale&gt; I totally agree<br /> 12:36 &lt; wurp2&gt; Updates to 2007.2 apps go back into the home svn<br /> 12:36 &lt; Ainulindale&gt; paulproteus: no, you're an external cabal all by yourself<br /> :-)<br /> 12:36 &lt; cb22&gt; anyone planning on drawing up a roadmap?<br /> 12:36 &lt; paulproteus&gt; cb22, We can do that in Trac in fact.<br /> 12:36 &lt; wurp2&gt; And changes to the underlying release go as patches into our OE<br /> branch, yes?<br /> 12:36 &lt; paulproteus&gt; (or on the wiki page)<br /> 12:36 &lt; paulproteus&gt; wurp2, Right<br /> 12:36 &lt; paulproteus&gt; mwester, Sanity-check my terminology where I mess things<br /> up!<br /> 12:37 &lt; Ainulindale&gt; hmmm fuzzy for me but what should go in OM and what should<br /> go in OE ?<br /> 12:37 &lt;@mwester&gt; Sure<br /> 12:37 &lt;@mwester&gt; What do you mean by OM?<br /> 12:37 &lt; paulproteus&gt; Ainulindale, New software we write goes in the<br /> projects.openmoko.org.<br /> 12:37 &lt;@mwester&gt; right.<br /> 12:37 &lt; Ainulindale&gt; Ok so the wrapper for example<br /> 12:37 &lt; wurp2&gt; Anything stand-alone goes in OM (projects.openmoko.org)<br /> 12:37 &lt; wurp2&gt; yeah<br /> 12:37 &lt;@mwester&gt; So we will use projects.openmoko.org for as much as we can,<br /> and OE to build the distro.<br /> 12:37 &lt; Ainulindale&gt; Sounds right to me<br /> 12:37 &lt; wurp2&gt; Great!<br /> 12:38 &lt;@mwester&gt; We *will not* use the OM git repo, as that is owned and<br /> controlled by Openmoko the company...<br /> &lt;/pre&gt;<br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]<br /> [[Category:SHR]]</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-08-07T22:10:13Z

<p>Wurp: /* Tasks &amp; status */</p> <hr /> <div>{{Distributions|SHR}}<br /> <br /> == Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the [[Openmoko2007.2]] GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br /> <br /> (We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br /> <br /> Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br /> <br /> == Why SHR exists ==<br /> This is long and rambling, and maybe more of a tirade than information, but it does give some background on why this project was started. The overview gives, well, the overview, this is more of a deeper examination of the existing releases and why we felt we needed something new.<br /> <br /> Feel free to skip this whole section if you already think SHR is a good idea :-)<br /> <br /> === Why not ASU? ===<br /> ASU is the distro that OM is putting their main effort into right now. ASU looks very slick, but is very unstable right now, and is likely to be unstable and feature-poor for some time.<br /> <br /> === Why not 2007.2? ===<br /> 2007.2 is the &quot;old&quot; Openmoko distribution, now unsupported. Unsupported == often broken. Also, neither calls nor suspend/resume ever worked reliably.<br /> <br /> === Why not Qtopia? ===<br /> You can also install Qtopia on the phone.<br /> <br /> Qtopia is stable but you can only build qt apps on Qtopia, which means lots of linux apps you might want to port suddenly got a lot harder to port. And some people just don't like developing for qt.<br /> <br /> Also, as far as I know, there is no documented build procedure for Qtopia on Openmoko.<br /> <br /> === Why not FSO? ===<br /> FSO is the initiative by Mickey Lauer and crew to create a good [[D-Bus]] infrastructure which runs on the neos, among other devices.<br /> <br /> FSO is by far the most stable &amp; usable release, if all you want is a phone. (I mean *all*. It just has a dialer right now, not even call history.)<br /> <br /> FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br /> <br /> Other people are supposed to put a front end on FSO. So that's what we're doing.<br /> <br /> === Why SHR? ===<br /> So SHR is FSO, with us doing the necessary work to port the old high-functionality 2007.2 stuff on a stable call platform. We have an adapter from the 2007.2 call service to the FSO call service and we're installing the basic 2007.2 apps on the FSO baseline install.<br /> <br /> In theory, it should be very simple, and should give us dialer, contact management, SMS, terminal, media player, gps app, etc. since all those already work on 2007.2. And the dialer should be stable, which it wasn't in 2007.2<br /> <br /> == First steps ==<br /> The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br /> <br /> We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br /> <br /> == Interest ==<br /> Here's a list of people who've expressed an interest in working on the SHR.<br /> <br /> * [[User:Wurp|wurp2]]<br /> * [[User:Ferric|ferric]]<br /> * [[User:Paulproteus|paulproteus]]<br /> * [[User:Ainulindale|Ainulindale]]<br /> * [[User:jluis|Jose Luis]]<br /> * [[User:Kevin_Dean|Kevin Dean]]<br /> * [[User:Cb22|cb22]]<br /> * [[User:Jeremy-list|Jeremy List]]<br /> * mwester<br /> * [[User:MarcOChapeau|MarcO'Chapeau]]<br /> * [[User:kd8ikt|kd8ikt]]<br /> * [[User:Mywave|Mywave]]<br /> * [[User:nigelTheBold|Anthony Taylor]]<br /> * [[User:Pwgen|Eric Weiss]]<br /> * [[User:Andre613|Andre Racicot]]<br /> <br /> == How to join ==<br /> * Please add your name (with a link to your user page) to the list above.<br /> * You should also send a request to join on the [http://projects.openmoko.org/projects/shr SHR project] on the OM projects page to join.<br /> * Join [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel shr-devel@lists.projects.openmoko.org] and send an introductory email.<br /> <br /> The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.<br /> <br /> See [[SHR Development]] to find out how to set up your development environment to work on existing SHR packages.<br /> <br /> Hang out in #openmoko-cdevel on chat.freenode.net between 5pm and 11pm GMT to chat with the people developing SHR. (Primarily MarcOChapeau and Ainulindale.)<br /> <br /> == Tasks &amp; status ==<br /> Here's a list of the tasks for the SHR:<br /> {|cellpadding=&quot;6&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |Comment<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space; just need to talk about git branches<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |<br /> |-<br /> |Implement libframeworkd-glib<br /> |Pre-Alpha. <br /> |[[User:Ainulindale|Ainulindale]]<br /> |<br /> |2008-07-30<br /> |Usable for call purposes / network registration and such.<br /> |-<br /> |port 2007.2 dialer2 (now dialer3) to use ophoned instead<br /> |Pre-Alpha<br /> |[[User:Ainulindale|Ainulindale]]<br /> |MarcOChapeau<br /> |2008-07-28<br /> |<br /> |-<br /> |port 2007.2 gsm-panel apps to use ophoned instead<br /> |Beta<br /> |[[User:Ainulindale|Ainulindale]]<br /> |no one yet<br /> |2008-07-30<br /> |Should be tested regarding the signal strength updates.<br /> |-<br /> |fork media player for SHR<br /> |not started<br /> |[[User:Wurp|Wurp]]<br /> |no one yet<br /> |2008-07-30<br /> |<br /> |-<br /> |switch media player to use alsa directly<br /> |not started<br /> |[[User:Abraxa|Abraxa]]<br /> |no one yet<br /> |2008-07-30<br /> |<br /> |-<br /> |verify that no other important apps in 2007.2 need ported off of pulseaudio (perhaps by putting all 2007.2 apps (minus pulseaudio) on FSO milestone 2 and verifying which ones still have sound :-)<br /> |not started<br /> |no one yet<br /> |no one yet<br /> |2008-07-30<br /> |<br /> |-<br /> |get neod workalike that uses ophoned to determine if you're on a call<br /> |Pre-Alpha<br /> |No one yet<br /> |no one yet<br /> |2008-07-28<br /> |<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |[[User:Kevin_Dean|Kevin Dean]]<br /> |Nobody<br /> |2008-07-05<br /> |<br /> |-<br /> |[[#List_of_packages_included|Identify packages to go into SHR]]<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Anyone &amp; everyone<br /> |2008-07-12<br /> |<br /> |-<br /> |Identify differences between FSO &amp; 2007.2 that need investigation<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-12<br /> |<br /> |-<br /> |Integrate [http://moko.mwester.net/fixes.html mwester's pulseaudio resume fix] into SHR<br /> |Not started<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-15<br /> |<br /> |-<br /> |Create messages3 as a copy of 2007.2's messages2 and get it compiling (comment out phonekit calls)<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |port messages3 to use libframework-glib<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |Create contacts3 as a copy of 2007.2's contacts2 and get it compiling (comment out phonekit calls)<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |-<br /> |port contacts3 to use libframework-glib<br /> |Not started<br /> |Nobody yet<br /> |Nobody yet<br /> |2008-08-07<br /> |<br /> |}<br /> <br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> == Technical Help ==<br /> <br /> === SVN ===<br /> <br /> We're currently hosted by [[User:Ainulindale|Ainulindale]] on svn://daria.forty-two.fr/shr as projects went down for a whole week-end.<br /> <br /> === Build logic ===<br /> <br /> Current applications (dialer3 and openmoko-panel-gsm) use frameworkd.<br /> So in order to be able to build and test these applications, you have to build frameworkd (MS2) and gsm0710muxd.<br /> <br /> === [[libframeworkd-glib]] ===<br /> <br /> In order to be able to use in an easy way frameworkd, without bothering about dbus calls (which could be difficult for new developers), we built a library allowing everyone to use the functions of frameworkd as if it were simple C functions. We're using asynchronous callbacks for dbus.<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * ophoned<br /> * preferencesd<br /> * pimd<br /> * odeviced<br /> * lots more...<br /> <br /> From 2007.2:<br /> * TODO<br /> * lots more...<br /> <br /> From ASU:<br /> * TODO<br /> * lots more...<br /> <br /> == Project links ==<br /> [http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br /> <br /> == IRC conversation about how we're using revision control ==<br /> <br /> ''This is deprecated, for now we use shr-devel as our only repository. This will change after the first SHR release.''&lt;br/&gt;<br /> From 2007-07-07<br /> &lt;pre&gt;<br /> 12:36 &lt; wurp2&gt; Everything *new* goes on OM projects site<br /> 12:36 &lt; Ainulindale&gt; I totally agree<br /> 12:36 &lt; wurp2&gt; Updates to 2007.2 apps go back into the home svn<br /> 12:36 &lt; Ainulindale&gt; paulproteus: no, you're an external cabal all by yourself<br /> :-)<br /> 12:36 &lt; cb22&gt; anyone planning on drawing up a roadmap?<br /> 12:36 &lt; paulproteus&gt; cb22, We can do that in Trac in fact.<br /> 12:36 &lt; wurp2&gt; And changes to the underlying release go as patches into our OE<br /> branch, yes?<br /> 12:36 &lt; paulproteus&gt; (or on the wiki page)<br /> 12:36 &lt; paulproteus&gt; wurp2, Right<br /> 12:36 &lt; paulproteus&gt; mwester, Sanity-check my terminology where I mess things<br /> up!<br /> 12:37 &lt; Ainulindale&gt; hmmm fuzzy for me but what should go in OM and what should<br /> go in OE ?<br /> 12:37 &lt;@mwester&gt; Sure<br /> 12:37 &lt;@mwester&gt; What do you mean by OM?<br /> 12:37 &lt; paulproteus&gt; Ainulindale, New software we write goes in the<br /> projects.openmoko.org.<br /> 12:37 &lt;@mwester&gt; right.<br /> 12:37 &lt; Ainulindale&gt; Ok so the wrapper for example<br /> 12:37 &lt; wurp2&gt; Anything stand-alone goes in OM (projects.openmoko.org)<br /> 12:37 &lt; wurp2&gt; yeah<br /> 12:37 &lt;@mwester&gt; So we will use projects.openmoko.org for as much as we can,<br /> and OE to build the distro.<br /> 12:37 &lt; Ainulindale&gt; Sounds right to me<br /> 12:37 &lt; wurp2&gt; Great!<br /> 12:38 &lt;@mwester&gt; We *will not* use the OM git repo, as that is owned and<br /> controlled by Openmoko the company...<br /> &lt;/pre&gt;<br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]<br /> [[Category:SHR]]</div>

Wurp http://wiki.openmoko.org/wiki/Libframeworkd-glib 2008-08-07T16:18:45Z

<p>Wurp: /* Calling a method */</p> <hr /> <div>= Purpose =<br /> <br /> libframeworkd-glib is a library conceived to help users develop with frameworkd without bothering about the dbus calls/marshalling/etc... while building a C glib software.<br /> <br /> It uses dbus-glib to bind to frameworkd, then calls the asynchronous methods of the interfaces. Thus, in order to use one method, you have to implement a callback.<br /> <br /> = Integration with other software =<br /> <br /> As for now, libframeworkd-glib is used mostly in [[SHR]] in order to be able to port openmoko-dialer2, openmoko-messages2, openmoko-panel-gsm, etc.<br /> <br /> = Current status =<br /> <br /> Today (August 7th), libframeworkd-glib almost implements the whole GSM stack from frameworkd.<br /> <br /> = Sources =<br /> <br /> You can find the sources on the [https://projects.openmoko.org/projects/shr/ SHR project page].<br /> <br /> = Example =<br /> <br /> ophonekitd is a simple example on how to use libframeworkd-glib to listen to events on frameworkd, and then launch the appropriate UI. It handles, in SHR, the whole &quot;call&quot; UI.<br /> <br /> == Connecting to the bus ==<br /> <br /> To connect to the bus, you have to explicitly ask for it. You also have to give to libframeworkd-glib a list of handlers for the events you want to listen to.<br /> <br /> &lt;pre&gt;<br /> FrameworkdHandlers fwHandler;<br /> fwHandler.networkStatus = NULL;<br /> fwHandler.simAuthStatus = ophonekitd_sim_auth_status_handler;<br /> fwHandler.callCallStatus = NULL;<br /> fwHandler.smsMessageSent = NULL;<br /> fwHandler.smsIncomingMessage = NULL;<br /> fwHandler.networkSignalStrength = NULL;<br /> dbus_connect_to_bus(&amp;fwHandler);<br /> &lt;/pre&gt;<br /> <br /> == Calling a method ==<br /> <br /> Libframeworkd-glib reflects the asynchronous nature of dbus. Calls to dbus return immediately, with the return values (or error values) coming back in a later call.<br /> <br /> In order to call a method you have to provide a callback which will give you the information you asked for, or some other stuff (errors as an example).<br /> <br /> &lt;pre&gt;<br /> boolean power_up_antenna() {<br /> device_set_antenna_power(TRUE, power_up_antenna_callback, NULL);<br /> <br /> return false; // End timeout<br /> }<br /> <br /> void power_up_antenna_callback(GError *error, gpointer userdata) {<br /> if(error != NULL) {<br /> if(IS_SIM_ERROR(error, SIM_ERROR_AUTH_FAILED)) {<br /> sim_display_code_UI();<br /> }<br /> }<br /> }<br /> &lt;/pre&gt;<br /> <br /> == Source code ==<br /> <br /> &lt;pre&gt;<br /> int main(int argc, char ** argv) {<br /> GMainLoop *mainloop = NULL;<br /> FrameworkdHandlers fwHandler;<br /> g_type_init();<br /> mainloop = g_main_loop_new (NULL, FALSE);<br /> <br /> fwHandler.networkStatus = NULL;<br /> fwHandler.simAuthStatus = ophonekitd_sim_auth_status_handler;<br /> fwHandler.callCallStatus = NULL;<br /> fwHandler.smsMessageSent = NULL;<br /> fwHandler.smsIncomingMessage = NULL;<br /> fwHandler.networkSignalStrength = NULL;<br /> dbus_connect_to_bus(&amp;fwHandler);<br /> g_timeout_add(5000, power_up_antenna, NULL);<br /> g_main_loop_run (mainloop);<br /> <br /> exit(EXIT_SUCCESS);<br /> }<br /> <br /> boolean power_up_antenna() {<br /> device_set_antenna_power(TRUE, power_up_antenna_callback, NULL);<br /> <br /> return false; // End timeout<br /> }<br /> <br /> void power_up_antenna_callback(GError *error, gpointer userdata) {<br /> if(error != NULL) {<br /> if(IS_SIM_ERROR(error, SIM_ERROR_AUTH_FAILED)) {<br /> sim_display_code_UI();<br /> }<br /> }<br /> }<br /> <br /> void ophonekitd_sim_auth_status_handler(const int status) {<br /> if(status == SIM_READY) {<br /> phonegui_destroy_pin_UI();<br /> }<br /> else {<br /> phonegui_display_pin_UI(status);<br /> }<br /> }<br /> <br /> &lt;/pre&gt;<br /> <br /> This example, built with the appropriate headers, listens to events on SIM authentication. It powers up the antenna, and presents the SIM &quot;code&quot; UI, that is to say the UI prompting the user for its PIN.<br /> <br /> [[Category:Implemented]]<br /> [[Category:Software]]<br /> [[Category:Framework]]</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-07-30T15:27:37Z

<p>Wurp: /* Tasks &amp; status */</p> <hr /> <div>== Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the [[Openmoko2007.2]] GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br /> <br /> (We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br /> <br /> Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br /> <br /> == Why SHR exists ==<br /> This is long and rambling, and maybe more of a tirade than information, but it does give some background on why this project was started. The overview gives, well, the overview, this is more of a deeper examination of the existing releases and why we felt we needed something new.<br /> <br /> Feel free to skip this whole section if you already think SHR is a good idea :-)<br /> <br /> === Why not ASU? ===<br /> ASU is the distro that OM is putting their main effort into right now. ASU looks very slick, but is very unstable right now, and is likely to be unstable and feature-poor for some time.<br /> <br /> === Why not 2007.2? ===<br /> 2007.2 is the &quot;old&quot; Openmoko distribution, now unsupported. Unsupported == often broken. Also, neither calls nor suspend/resume ever worked reliably.<br /> <br /> === Why not Qtopia? ===<br /> You can also install Qtopia on the phone, once TrollTech puts the images up again :-(<br /> <br /> Qtopia is stable, but it doesn't suspend &amp; resume (so the battery life is crap). And you can only build qt apps on Qtopia, which means lots of linux apps you might want to port suddenly got a lot harder to port. And some people just don't like developing for qt.<br /> <br /> Also, as far as I know, there is no documented build procedure for Qtopia on Openmoko.<br /> <br /> === Why not FSO? ===<br /> FSO is the initiative by Mickey Lauer and crew to create a good [[D-Bus]] infrastructure which runs on the neos, among other devices.<br /> <br /> FSO is by far the most stable &amp; usable release, if all you want is a phone. (I mean *all*. It just has a dialer right now, not even call history.)<br /> <br /> FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br /> <br /> Other people are supposed to put a front end on FSO. So that's what we're doing.<br /> <br /> === Why SHR? ===<br /> So SHR is FSO, with us doing the necessary work to port the old high-functionality 2007.2 stuff on a stable call platform. We have an adapter from the 2007.2 call service to the FSO call service and we're installing the basic 2007.2 apps on the FSO baseline install.<br /> <br /> In theory, it should be very simple, and should give us dialer, contact management, SMS, terminal, media player, gps app, etc. since all those already work on 2007.2. And the dialer should be stable, which it wasn't in 2007.2<br /> <br /> == First steps ==<br /> The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br /> <br /> We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br /> <br /> == Interest ==<br /> Here's a list of people who've expressed an interest in working on the SHR.<br /> <br /> * [[User:Wurp|wurp2]]<br /> * [[User:Ferric|ferric]]<br /> * [[User:Paulproteus|paulproteus]]<br /> * [[User:Ainulindale|Ainulindale]]<br /> * [[User:jluis|Jose Luis]]<br /> * [[User:Kevin_Dean|Kevin Dean]]<br /> * [[User:Cb22|cb22]]<br /> * [[User:Jeremy-list|Jeremy List]]<br /> * mwester<br /> * [[User:MarcOChapeau|MarcO'Chapeau]]<br /> * [[User:kd8ikt|kd8ikt]]<br /> * [[User:Mywave|Mywave]]<br /> * [[User:nigelTheBold|Anthony Taylor]]<br /> * [[User:Pwgen|Eric Weiss]]<br /> <br /> == How to join ==<br /> * Please add your name (with a link to your user page) to the list above.<br /> * You should also send a request to join on the [http://projects.openmoko.org/projects/shr SHR project] on the OM projects page to join.<br /> * Join [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel shr-devel@lists.projects.openmoko.org] and send an introductory email.<br /> <br /> The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.<br /> <br /> See [[SHR Development]] to find out how to set up your development environment to work on existing SHR packages.<br /> <br /> Hang out in #openmoko-cdevel on chat.freenode.net between 5pm and 11pm GMT to chat with the people developing SHR. (Primarily MarcOChapeau and Ainulindale.)<br /> <br /> == Tasks &amp; status ==<br /> Here's a list of the tasks for the SHR:<br /> {|cellpadding=&quot;6&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |Comment<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space; just need to talk about git branches<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |<br /> |-<br /> |Implement libframeworkd-glib<br /> |Pre-Alpha. <br /> |[[User:Ainulindale|Ainulindale]]<br /> |<br /> |2008-07-30<br /> |Usable for call purposes / network registration and such.<br /> |-<br /> |port 2007.2 dialer2 (now dialer3) to use ophoned instead<br /> |Pre-Alpha<br /> |[[User:Ainulindale|Ainulindale]]<br /> |MarcOChapeau<br /> |2008-07-28<br /> |<br /> |-<br /> |port 2007.2 gsm-panel apps to use ophoned instead<br /> |Beta<br /> |[[User:Ainulindale|Ainulindale]]<br /> |no one yet<br /> |2008-07-30<br /> |Should be tested regarding the signal strength updates.<br /> |-<br /> |fork media player for SHR<br /> |not started<br /> |[[User:Wurp|Wurp]]<br /> |no one yet<br /> |2008-07-30<br /> |<br /> |-<br /> |switch media player to use alsa directly<br /> |not started<br /> |[[User:Abraxa|Abraxa]]<br /> |no one yet<br /> |2008-07-30<br /> |<br /> |-<br /> |verify that no other important apps in 2007.2 need ported off of pulseaudio<br /> |not started<br /> |no one yet<br /> |no one yet<br /> |2008-07-30<br /> |<br /> |-<br /> |get neod workalike that uses ophoned to determine if you're on a call<br /> |Pre-Alpha<br /> |No one yet<br /> |no one yet<br /> |2008-07-28<br /> |<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |[[User:Kevin_Dean|Kevin Dean]]<br /> |Nobody<br /> |2008-07-05<br /> |<br /> |-<br /> |[[#List_of_packages_included|Identify packages to go into SHR]]<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Anyone &amp; everyone<br /> |2008-07-12<br /> |<br /> |-<br /> |Identify differences between FSO &amp; 2007.2 that need investigation<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-12<br /> |<br /> |-<br /> |Switch FSO to use the 2007.2 matchbox session<br /> |Pre-alpha<br /> |[[User:MarcOChapeau|MarcOChapeau]]<br /> |[[User:Wurp|Wurp]]<br /> |2008-07-12<br /> |<br /> |-<br /> |Integrate [http://moko.mwester.net/fixes.html mwester's pulseaudio resume fix] into SHR<br /> |Not started<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-15<br /> |<br /> |}<br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> == Technical Help ==<br /> <br /> === SVN ===<br /> <br /> We're currently hosted by [[User:Ainulindale|Ainulindale]] on svn://daria.forty-two.fr/shr as projects went down for a whole week-end.<br /> <br /> === Build logic ===<br /> <br /> Current applications (dialer3 and openmoko-panel-gsm) use frameworkd.<br /> So in order to be able to build and test these applications, you have to build frameworkd (MS2) and gsm0710muxd.<br /> <br /> === libframeworkd-glib ===<br /> <br /> In order to be able to use in an easy way frameworkd, without bothering about dbus calls (which could be difficult for new developers), we built a library allowing everyone to use the functions of frameworkd as if it were simple C functions. We're using asynchronous callbacks for dbus.<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * ophoned<br /> * preferencesd<br /> * pimd<br /> * odeviced<br /> * lots more...<br /> <br /> From 2007.2:<br /> * TODO<br /> * lots more...<br /> <br /> From ASU:<br /> * TODO<br /> * lots more...<br /> <br /> == Project links ==<br /> [http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br /> <br /> == IRC conversation about how we're using revision control ==<br /> <br /> ''This is deprecated, for now we use shr-devel as our only repository. This will change after the first SHR release.''&lt;br/&gt;<br /> From 2007-07-07<br /> &lt;pre&gt;<br /> 12:36 &lt; wurp2&gt; Everything *new* goes on OM projects site<br /> 12:36 &lt; Ainulindale&gt; I totally agree<br /> 12:36 &lt; wurp2&gt; Updates to 2007.2 apps go back into the home svn<br /> 12:36 &lt; Ainulindale&gt; paulproteus: no, you're an external cabal all by yourself<br /> :-)<br /> 12:36 &lt; cb22&gt; anyone planning on drawing up a roadmap?<br /> 12:36 &lt; paulproteus&gt; cb22, We can do that in Trac in fact.<br /> 12:36 &lt; wurp2&gt; And changes to the underlying release go as patches into our OE<br /> branch, yes?<br /> 12:36 &lt; paulproteus&gt; (or on the wiki page)<br /> 12:36 &lt; paulproteus&gt; wurp2, Right<br /> 12:36 &lt; paulproteus&gt; mwester, Sanity-check my terminology where I mess things<br /> up!<br /> 12:37 &lt; Ainulindale&gt; hmmm fuzzy for me but what should go in OM and what should<br /> go in OE ?<br /> 12:37 &lt;@mwester&gt; Sure<br /> 12:37 &lt;@mwester&gt; What do you mean by OM?<br /> 12:37 &lt; paulproteus&gt; Ainulindale, New software we write goes in the<br /> projects.openmoko.org.<br /> 12:37 &lt;@mwester&gt; right.<br /> 12:37 &lt; Ainulindale&gt; Ok so the wrapper for example<br /> 12:37 &lt; wurp2&gt; Anything stand-alone goes in OM (projects.openmoko.org)<br /> 12:37 &lt; wurp2&gt; yeah<br /> 12:37 &lt;@mwester&gt; So we will use projects.openmoko.org for as much as we can,<br /> and OE to build the distro.<br /> 12:37 &lt; Ainulindale&gt; Sounds right to me<br /> 12:37 &lt; wurp2&gt; Great!<br /> 12:38 &lt;@mwester&gt; We *will not* use the OM git repo, as that is owned and<br /> controlled by Openmoko the company...<br /> &lt;/pre&gt;<br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]<br /> [[Category:SHR]]</div>

Wurp http://wiki.openmoko.org/wiki/SHR_Development 2008-07-29T17:40:22Z

<p>Wurp: /* Set up your local.conf */</p> <hr /> <div>== Building openmoko-dialer3 ==<br /> Currently this is the only package of any size being developed for SHR, and it's the only one with any instructions. If you start another SHR project (please check with [[User:Wurp|Bobby]] before starting one), put instructions for working on the project here!<br /> <br /> === Before beginning ===<br /> You must build openembedded before you can build SHR packages. The easiest way is to go to http://wiki.openmoko.org/wiki/Mokomakefile and build using the instructions for FSO.<br /> <br /> * Note: if building FSO fails using MokoMakefile (zhone! or no dbus show up on the top of the newly booted image), try using this<br /> method: http://wiki.openmoko.org/wiki/FSO<br /> <br /> The rest of these instructions are written assuming that you used Mokomakefile and that the directory you downloaded the base Makefile into (using wget) is $MOKO.<br /> <br /> You must also download the SHR code using subversion. See http://projects.openmoko.org/projects/shr. We will refer to the directory to which you downloaded the project as $SHRSVN. (This directory should contain $SHRSVN/packages/openmoko-dialer3.bb)<br /> <br /> === Set up your BBPATH ===<br /> <br /> export BBPATH=.:$MOKO/openembedded/:$MOKO/bitbake/:$MOKO/:$SHRSVN/trunk/packages/<br /> <br /> === Set up the CACHE ===<br /> <br /> export CACHE=tmp/cache<br /> <br /> <br /> <br /> === Set up your local.conf ===<br /> Cd to $MOKO/openembedded<br /> <br /> Append the following lines to conf/local.conf:<br /> BBFILES += &quot;$SHRSVN/trunk/packages/*.bb $MOKO/openembedded/packages/*/*.bb&quot;<br /> SELECTED_OPTIMIZATION = &quot;-Os -g&quot;<br /> <br /> ''Note: Spaces are important in your bitbake conf files! You must have spaces before &amp; after the = or +=''<br /> <br /> === Set up your openmoko.conf (if using 2007.2) ===<br /> <br /> edit $MOKO/openembedded/conf/distro/openmoko.conf<br /> <br /> and make sure that these Gtk+ options are set:<br /> <br /> # Select package versions we want to use.<br /> PREFERRED_PROVIDER_gtk+ = &quot;gtk+-fastscaling&quot;<br /> PREFERRED_VERSION_gtk+-fastscaling = &quot;2.10.14&quot;<br /> <br /> <br /> === Add your cross-compiler to your PATH ===<br /> <br /> export PATH=$MOKO/build/tmp/cross/bin/:$MOKO/build/tmp/staging/x86_64-linux/usr/bin:$PATH<br /> <br /> === Run bitbake ===<br /> <br /> bitbake openmoko-dialer3<br /> <br /> After the first time you build successfully, you can build with<br /> <br /> bitbake -b openmoko-dialog3_svn<br /> <br /> which is much faster.<br /> <br /> === To recompile, and only recompile ===<br /> <br /> bitbake -c compile -b $SHRSVN/trunk/packages/openmoko-dialer3.bb<br /> <br /> === Troubleshooting ===<br /> <br /> ==== General ====<br /> One thing to try is to unset all environment variables not listed in this page. LIBPATH and INCLUDE can be particularly troublesome.<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]<br /> [[Category:SHR]]<br /> [[Category:SHR Devel]]</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-07-28T18:11:09Z

<p>Wurp: /* Tasks &amp; status */</p> <hr /> <div>== Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the [[Openmoko2007.2]] GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br /> <br /> (We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br /> <br /> Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br /> <br /> == Why SHR exists ==<br /> This is long and rambling, and maybe more of a tirade than information, but it does give some background on why this project was started. The overview gives, well, the overview, this is more of a deeper examination of the existing releases and why we felt we needed something new.<br /> <br /> Feel free to skip this whole section if you already think SHR is a good idea :-)<br /> <br /> === Why not ASU? ===<br /> ASU is the distro that OM is putting their main effort into right now. ASU looks very slick, but is very unstable right now, and is likely to be unstable and feature-poor for some time.<br /> <br /> === Why not 2007.2? ===<br /> 2007.2 is the &quot;old&quot; Openmoko distribution, now unsupported. Unsupported == often broken. Also, neither calls nor suspend/resume ever worked reliably.<br /> <br /> === Why not Qtopia? ===<br /> You can also install Qtopia on the phone, once TrollTech puts the images up again :-(<br /> <br /> Qtopia is stable, but it doesn't suspend &amp; resume (so the battery life is crap). And you can only build qt apps on Qtopia, which means lots of linux apps you might want to port suddenly got a lot harder to port. And some people just don't like developing for qt.<br /> <br /> Also, as far as I know, there is no documented build procedure for Qtopia on Openmoko.<br /> <br /> === Why not FSO? ===<br /> FSO is the initiative by Mickey Lauer and crew to create a good [[D-Bus]] infrastructure which runs on the neos, among other devices.<br /> <br /> FSO is by far the most stable &amp; usable release, if all you want is a phone. (I mean *all*. It just has a dialer right now, not even call history.)<br /> <br /> FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br /> <br /> Other people are supposed to put a front end on FSO. So that's what we're doing.<br /> <br /> === Why SHR? ===<br /> So SHR is FSO, with us doing the necessary work to port the old high-functionality 2007.2 stuff on a stable call platform. We have an adapter from the 2007.2 call service to the FSO call service and we're installing the basic 2007.2 apps on the FSO baseline install.<br /> <br /> In theory, it should be very simple, and should give us dialer, contact management, SMS, terminal, media player, gps app, etc. since all those already work on 2007.2. And the dialer should be stable, which it wasn't in 2007.2<br /> <br /> == First steps ==<br /> The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br /> <br /> We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br /> <br /> == Interest ==<br /> Here's a list of people who've expressed an interest in working on the SHR.<br /> <br /> * [[User:Wurp|wurp2]]<br /> * [[User:Ferric|ferric]]<br /> * [[User:Paulproteus|paulproteus]]<br /> * [[User:Ainulindale|Ainulindale]]<br /> * [[User:jluis|Jose Luis]]<br /> * [[User:Kevin_Dean|Kevin Dean]]<br /> * [[User:Cb22|cb22]]<br /> * [[User:Jeremy-list|Jeremy List]]<br /> * mwester<br /> * [[User:MarcOChapeau|MarcO'Chapeau]]<br /> * [[User:kd8ikt|kd8ikt]]<br /> * [[User:Mywave|Mywave]]<br /> * [[User:nigelTheBold|Anthony Taylor]]<br /> * [[User:Pwgen|Eric Weiss]]<br /> <br /> == How to join ==<br /> * Please add your name (with a link to your user page) to the list above.<br /> * You should also send a request to join on the [http://projects.openmoko.org/projects/shr SHR project] on the OM projects page to join.<br /> * Join [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel shr-devel@lists.projects.openmoko.org] and send an introductory email.<br /> <br /> The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.<br /> <br /> See [[SHR Development]] to find out how to set up your development environment to work on existing SHR packages.<br /> <br /> Hang out in #openmoko-cdevel on chat.freenode.net between 5pm and 11pm GMT to chat with the people developing SHR. (Primarily MarcOChapeau and Ainulindale.)<br /> <br /> == Tasks &amp; status ==<br /> Here's a list of the tasks for the SHR:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space; just need to talk about git branches<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |-<br /> |port 2007.2 dialer2 to use ophoned or ogsmd instead (now dialer3)<br /> |Pre-Alpha<br /> |[[User:Ainulindale|Ainulindale]]<br /> |MarcOChapeau<br /> |2008-07-28<br /> |-<br /> |port 2007.2 gsm-panel apps to use ophoned or ogsmd instead<br /> |Pre-Alpha<br /> |No one yet<br /> |no one yet<br /> |2008-07-28<br /> |-<br /> |get neod workalike that uses ophoned to determine if you're on a call<br /> |Pre-Alpha<br /> |No one yet<br /> |no one yet<br /> |2008-07-28<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |[[User:Kevin_Dean|Kevin Dean]]<br /> |Nobody<br /> |2008-07-05<br /> |-<br /> |[[#List_of_packages_included|Identify packages to go into SHR]]<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Anyone &amp; everyone<br /> |2008-07-12<br /> |-<br /> |Identify differences between FSO &amp; 2007.2 that need investigation<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-12<br /> |-<br /> |Switch FSO to use the 2007.2 matchbox session<br /> |Pre-alpha<br /> |[[User:MarcOChapeau|MarcOChapeau]]<br /> |[[User:Wurp|Wurp]]<br /> |2008-07-12<br /> |-<br /> |Integrate [http://moko.mwester.net/fixes.html mwester's pulseaudio resume fix] into SHR<br /> |Not started<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-15<br /> |}<br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * ophoned<br /> * preferencesd<br /> * pimd<br /> * odeviced<br /> * lots more...<br /> <br /> From 2007.2:<br /> * TODO<br /> * lots more...<br /> <br /> From ASU:<br /> * TODO<br /> * lots more...<br /> <br /> == Project links ==<br /> [http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br /> <br /> == IRC conversation about how we're using revision control ==<br /> <br /> ''This is deprecated, for now we use shr-devel as our only repository. This will change after the first SHR release.''&lt;br/&gt;<br /> From 2007-07-07<br /> &lt;pre&gt;<br /> 12:36 &lt; wurp2&gt; Everything *new* goes on OM projects site<br /> 12:36 &lt; Ainulindale&gt; I totally agree<br /> 12:36 &lt; wurp2&gt; Updates to 2007.2 apps go back into the home svn<br /> 12:36 &lt; Ainulindale&gt; paulproteus: no, you're an external cabal all by yourself<br /> :-)<br /> 12:36 &lt; cb22&gt; anyone planning on drawing up a roadmap?<br /> 12:36 &lt; paulproteus&gt; cb22, We can do that in Trac in fact.<br /> 12:36 &lt; wurp2&gt; And changes to the underlying release go as patches into our OE<br /> branch, yes?<br /> 12:36 &lt; paulproteus&gt; (or on the wiki page)<br /> 12:36 &lt; paulproteus&gt; wurp2, Right<br /> 12:36 &lt; paulproteus&gt; mwester, Sanity-check my terminology where I mess things<br /> up!<br /> 12:37 &lt; Ainulindale&gt; hmmm fuzzy for me but what should go in OM and what should<br /> go in OE ?<br /> 12:37 &lt;@mwester&gt; Sure<br /> 12:37 &lt;@mwester&gt; What do you mean by OM?<br /> 12:37 &lt; paulproteus&gt; Ainulindale, New software we write goes in the<br /> projects.openmoko.org.<br /> 12:37 &lt;@mwester&gt; right.<br /> 12:37 &lt; Ainulindale&gt; Ok so the wrapper for example<br /> 12:37 &lt; wurp2&gt; Anything stand-alone goes in OM (projects.openmoko.org)<br /> 12:37 &lt; wurp2&gt; yeah<br /> 12:37 &lt;@mwester&gt; So we will use projects.openmoko.org for as much as we can,<br /> and OE to build the distro.<br /> 12:37 &lt; Ainulindale&gt; Sounds right to me<br /> 12:37 &lt; wurp2&gt; Great!<br /> 12:38 &lt;@mwester&gt; We *will not* use the OM git repo, as that is owned and<br /> controlled by Openmoko the company...<br /> &lt;/pre&gt;<br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]<br /> [[Category:SHR]]</div>

Wurp http://wiki.openmoko.org/wiki/Openmoko:Community_Portal 2008-07-25T20:46:28Z

<p>Wurp: /* IRC */</p> <hr /> <div>{|align=right<br /> |__TOC__<br /> |}<br /> == Community Updates ==<br /> <br /> The [[Community Updates]] article is updated at least twice a month by Michael Shiloh. Updates are also mailed to the openmoko-community mailing list, and major updates are also sent to the announce list. <br /> <br /> == IRC ==<br /> <br /> There is always a good group in the IRC channel #openmoko on FreeNode. If you aren't an IRC-er, you might want to review the discussions anyways:<br /> <br /> * [http://logs.nslu2-linux.org/livelogs/openmoko.txt Current 24h live log]<br /> * [http://logs.nslu2-linux.org/livelogs/openmoko-prev.txt Previous 24h log]<br /> * [http://logs.nslu2-linux.org/livelogs/openmoko/ Archives back to 29 November 2006]<br /> <br /> (Courtesy of the NSLU2-Linux project)<br /> <br /> Within the time contstraints of middle Europe, the Freenode channel #neo1973-germany is also active and members switch to english on demand.<br /> <br /> You can also hang out in #openmoko-cdevel (the community developers channel) on chat.freenode.net if you have development questions.<br /> <br /> == Community site based on trac ==<br /> The German Neo1973 community created a Trac-based web site with SVN version control for their community projects: http://neo1973-germany.de/ The most notable project is Zad, which consists of a GUI and daemons for GSM/GPRS muxing, GSM, GPS and more, written using Enlightment for smooth, smooth, fast, alpha-blended graphics and glib and dbus for daemons, but the actual code of the project is all python. And yes, you can even make phone calls with it (even without &quot;echo&quot;).<br /> <br /> == Wiki ==<br /> The old community wiki is at http://www.linuxtogo.org/gowiki/OpenMoko/, since the release of the official wiki at http://wiki.openmoko.org/, it should no longer be used for OpenMoko. Please help integrating the content of the old wiki into this wiki. Please note that you cannot just copy from the old wiki, as the old wiki is (unfortunately) not clearly licensed and the content on this wiki is licensed under GNU FDL. You will instead need to rewrite the articles.<br /> <br /> When you have integrated/rewritten an article, please update the old wiki with clear information that you have moved the information, so others do not update the old page.<br /> <br /> <br /> <br /> === Useful content that should be transfered ===<br /> ==== FAQ about the whole project ====<br /> &lt;strike&gt;<br /> *[http://www.linuxtogo.org/gowiki/OpenMoko/QuestionsAndAnswers some FAQ about the whole project]&lt;/strike&gt;i created the [[FAQ]] page and added it to the introduction section on the main page. There are a few links on this page that will need to be fixed after all the content has been migrated [[User:Ryanlerch|Ryanlerch]] 12:55, 16 February 2007 (CET) <br /> *&lt;strike&gt;[http://www.linuxtogo.org/gowiki/OpenMoko/Providers Cell phone providers]&lt;/strike&gt;--[[User:Denis std|denis_std]] 16:25, 16 February 2007 (CET) - '''Done''' - [[OpenMoko compatible cellphone providers]]<br /> <br /> ====Software ideas ====<br /> *[http://www.linuxtogo.org/gowiki/OpenMoko/Ideas a really mixed up list of software and hardware ideas] - Please name your page Wishlist:''Pagename'' and add 'Category:Ideas' if you rewrite one of these<br /> *[http://www.linuxtogo.org/gowiki/OpenMoko/Software software ideas]<br /> <br /> ==== Hardware stuff ====<br /> *&lt;strike&gt;[http://www.linuxtogo.org/gowiki/OpenMoko/iPhone comparison Neo / iPhone]&lt;/strike&gt;--[[User:Mikesh|Mikesh]] 09:15, 18 February 2007 (CET) '''DONE''' - [[iPhone]]<br /> *&lt;strike&gt;[http://www.linuxtogo.org/gowiki/OpenMoko/AT_Commands At Commands]&lt;/strike&gt;--[[User:AndreasHochsteger|Andreas Hochsteger]] 22:11, 24 February 2007 (CET) '''DONE''' - [[Hardware:AT_Commands|AT Commands]]<br /> *[http://www.linuxtogo.org/gowiki/OpenMoko/GPRS information on GPRS]<br /> *&lt;strike&gt;[http://www.linuxtogo.org/gowiki/OpenMoko/A%28ssisted%29_GPS information on (A)GPS]&lt;/strike&gt;--[[User:Denis std|denis_std]] 01:57, 16 February 2007 (CET) '''DONE''' - [[Hardware:AGPS|AGPS]]<br /> <br /> ==== Content used on OpenMoko ====<br /> *&lt;strike&gt;[http://www.linuxtogo.org/gowiki/OpenMoko/Content content ideas]&lt;/strike&gt;--[[User:Denis std|denis_std]][http://www.usome.com] 16:35, 16 February 2007 (CET) - '''Done''' - [[Media Content]]<br /> <br /> ==== Coding instructions ====<br /> *[http://www.linuxtogo.org/gowiki/OpenMoko/OpenEmbedded open embedded]<br /> *[http://www.linuxtogo.org/gowiki/OpenMoko/ToolChain tool chain]<br /> *<br /> ==== Other useful stuff ====<br /> *&lt;strike&gt;[http://www.linuxtogo.org/gowiki/OpenMoko/PressCoverage Press Coverage]&lt;/strike&gt;--[[User:Denis std|denis_std]] 16:54, 16 February 2007 (CET) - '''Done''' - [[Press Coverage]]<br /> *&lt;strike&gt;[http://www.linuxtogo.org/gowiki/OpenMoko/Testimonials Testimonials]&lt;/strike&gt;--[[User:Denis std|denis_std]] 17:34, 16 February 2007 (CET) - '''Done''' - [[Testimonials]]<br /> *&lt;strike&gt;[http://www.linuxtogo.org/gowiki/OpenMoko/Translation Translation of OpenMoko]&lt;/strike&gt;--[[User:Mikesh|Mikesh]] 11:42, 18 February 2007 (CET) '''DONE''' - [[Translation]]<br /> *&lt;strike&gt;[http://www.linuxtogo.org/gowiki/OpenMoko/AtFOSDEM FOSDEM]&lt;/strike&gt; <br /> *&lt;strike&gt;[http://www.linuxtogo.org/gowiki/OpenMoko/Glossary Glossary]&lt;/strike&gt;--[[User:AndreasHochsteger|Andreas Hochsteger]] 22:41, 24 February 2006 (CET) - '''DONE''' - [[Glossary]]<br /> *&lt;strike&gt;[http://www.linuxtogo.org/gowiki/OpenMoko/Video_Bounty Video Bounty]&lt;/strike&gt;-- '''ABANDONED''' - New hardware renders this task trivial<br /> <br /> == Development news ==<br /> <br /> Developer news of progress being made on OpenMoko.<br /> <br /> * [http://planet.openmoko.org/ Main planet openmoko feed]<br /> * [http://blogs.gnome.org/thos/2007/08/21/openmoko-20072/ OpenMoko 2007.2 new User Interface style for OpenMoko by OpenedHand]<br /> <br /> <br /> === [[User's Manual]] ===<br /> <br /> An user manual should be created for non geeks. I mean one of those small books you get when you buy a new phone. They are full of pictures, describe basic steps of phone usage and are translated into as many languages as possible.<br /> <br /> The wiki is a mess, somebody should suggest a structure easier to navigate.<br /> <br /> I do not see a point in translating developer pages in other languages than English, but this is subjective.<br /> <br /> --[[User:Iztok.jeras|Iztok.jeras]] 10:56, 23 May 2007 (CEST)<br /> <br /> I am French, but I don't see a point either in translating the developer manual. Mickael.<br /> <br /> My mother language is Spanish. I think that a developer manual written in English is enough -no need for translation to other languages. Raul.<br /> <br /> I have the same idea, but, its free for translate to other laguages. Freddy<br /> <br /> I am French, I think that a basic manual for non-geek could be a good idea…<br /> <br /> --[[User:Bart|Bart]] 10:14, 2 October 2007 (CEST)<br /> I am Dutch, if a dutch user manual is needed I'd love to help.<br /> <br /> [[User:Fradeve11|Fradeve11]]: I give my appreciament and time to translate an user basic manual in Italian ;) very good idea!<br /> <br /> [[User:darktim|darktim]]: I will do the German part. I'm not a coder, so that could be my contribution ;)<br /> <br /> <br /> [[User:Yorick|Yorick]]: I'm willing to do some Dutch translation<br /> <br /> === USB Keyboards ===<br /> <br /> I'm not sure if this is the proper place to post this, but I think it would be an excellent idea to test out the Neo with a USB keyboard and even for OpenMoko to have at least one suggested &amp;&amp; compatible device. I haven't seen details about what standards the Neo's USB device will adhere to (host capabilities? - although that might be somewhat power hungry). Is there even a thing as a keyboard that operates as its own USB host? Actually, even a bluetooth keyboard would be reasonable. I only pose this question because I would like to be able to write snippets of code, and I have some doubts about using the stylus with an on-screen keyboard - especially for certain syntax patterns that are common in most programming languages. <br /> <br /> '''Update''': I'm glad someone else has thought about this too :: [http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#HID_.28Human_Input_Device.29 Neo1973 &amp; Bluetooth HIDs (Human Input Devices)]<br /> <br /> --[[User:Cfriedt|Cfriedt]] 02:07, 20 November 2007 (CET)<br /> <br /> [[Category:Community]]<br /> [[Category:Information]]</div>

Wurp http://wiki.openmoko.org/wiki/Openmoko:Community_Portal 2008-07-25T20:44:53Z

<p>Wurp: /* IRC */</p> <hr /> <div>{|align=right<br /> |__TOC__<br /> |}<br /> == Community Updates ==<br /> <br /> The [[Community Updates]] article is updated at least twice a month by Michael Shiloh. Updates are also mailed to the openmoko-community mailing list, and major updates are also sent to the announce list. <br /> <br /> == IRC ==<br /> <br /> There is always a good group in the IRC channel #openmoko on FreeNode. If you aren't an IRC-er, you might want to review the discussions anyways:<br /> <br /> * [http://logs.nslu2-linux.org/livelogs/openmoko.txt Current 24h live log]<br /> * [http://logs.nslu2-linux.org/livelogs/openmoko-prev.txt Previous 24h log]<br /> * [http://logs.nslu2-linux.org/livelogs/openmoko/ Archives back to 29 November 2006]<br /> <br /> (Courtesy of the NSLU2-Linux project)<br /> <br /> Within the time contstraints of middle Europe, the Freenode channel #neo1973-germany is also active and members switch to english on demand.<br /> <br /> You can also hang out in #openmoko-cdevel (the community developers channel) on chat.freenode.net if you have development questions or if #openmoko is just too noisy for you.<br /> <br /> == Community site based on trac ==<br /> The German Neo1973 community created a Trac-based web site with SVN version control for their community projects: http://neo1973-germany.de/ The most notable project is Zad, which consists of a GUI and daemons for GSM/GPRS muxing, GSM, GPS and more, written using Enlightment for smooth, smooth, fast, alpha-blended graphics and glib and dbus for daemons, but the actual code of the project is all python. And yes, you can even make phone calls with it (even without &quot;echo&quot;).<br /> <br /> == Wiki ==<br /> The old community wiki is at http://www.linuxtogo.org/gowiki/OpenMoko/, since the release of the official wiki at http://wiki.openmoko.org/, it should no longer be used for OpenMoko. Please help integrating the content of the old wiki into this wiki. Please note that you cannot just copy from the old wiki, as the old wiki is (unfortunately) not clearly licensed and the content on this wiki is licensed under GNU FDL. You will instead need to rewrite the articles.<br /> <br /> When you have integrated/rewritten an article, please update the old wiki with clear information that you have moved the information, so others do not update the old page.<br /> <br /> <br /> <br /> === Useful content that should be transfered ===<br /> ==== FAQ about the whole project ====<br /> &lt;strike&gt;<br /> *[http://www.linuxtogo.org/gowiki/OpenMoko/QuestionsAndAnswers some FAQ about the whole project]&lt;/strike&gt;i created the [[FAQ]] page and added it to the introduction section on the main page. There are a few links on this page that will need to be fixed after all the content has been migrated [[User:Ryanlerch|Ryanlerch]] 12:55, 16 February 2007 (CET) <br /> *&lt;strike&gt;[http://www.linuxtogo.org/gowiki/OpenMoko/Providers Cell phone providers]&lt;/strike&gt;--[[User:Denis std|denis_std]] 16:25, 16 February 2007 (CET) - '''Done''' - [[OpenMoko compatible cellphone providers]]<br /> <br /> ====Software ideas ====<br /> *[http://www.linuxtogo.org/gowiki/OpenMoko/Ideas a really mixed up list of software and hardware ideas] - Please name your page Wishlist:''Pagename'' and add 'Category:Ideas' if you rewrite one of these<br /> *[http://www.linuxtogo.org/gowiki/OpenMoko/Software software ideas]<br /> <br /> ==== Hardware stuff ====<br /> *&lt;strike&gt;[http://www.linuxtogo.org/gowiki/OpenMoko/iPhone comparison Neo / iPhone]&lt;/strike&gt;--[[User:Mikesh|Mikesh]] 09:15, 18 February 2007 (CET) '''DONE''' - [[iPhone]]<br /> *&lt;strike&gt;[http://www.linuxtogo.org/gowiki/OpenMoko/AT_Commands At Commands]&lt;/strike&gt;--[[User:AndreasHochsteger|Andreas Hochsteger]] 22:11, 24 February 2007 (CET) '''DONE''' - [[Hardware:AT_Commands|AT Commands]]<br /> *[http://www.linuxtogo.org/gowiki/OpenMoko/GPRS information on GPRS]<br /> *&lt;strike&gt;[http://www.linuxtogo.org/gowiki/OpenMoko/A%28ssisted%29_GPS information on (A)GPS]&lt;/strike&gt;--[[User:Denis std|denis_std]] 01:57, 16 February 2007 (CET) '''DONE''' - [[Hardware:AGPS|AGPS]]<br /> <br /> ==== Content used on OpenMoko ====<br /> *&lt;strike&gt;[http://www.linuxtogo.org/gowiki/OpenMoko/Content content ideas]&lt;/strike&gt;--[[User:Denis std|denis_std]][http://www.usome.com] 16:35, 16 February 2007 (CET) - '''Done''' - [[Media Content]]<br /> <br /> ==== Coding instructions ====<br /> *[http://www.linuxtogo.org/gowiki/OpenMoko/OpenEmbedded open embedded]<br /> *[http://www.linuxtogo.org/gowiki/OpenMoko/ToolChain tool chain]<br /> *<br /> ==== Other useful stuff ====<br /> *&lt;strike&gt;[http://www.linuxtogo.org/gowiki/OpenMoko/PressCoverage Press Coverage]&lt;/strike&gt;--[[User:Denis std|denis_std]] 16:54, 16 February 2007 (CET) - '''Done''' - [[Press Coverage]]<br /> *&lt;strike&gt;[http://www.linuxtogo.org/gowiki/OpenMoko/Testimonials Testimonials]&lt;/strike&gt;--[[User:Denis std|denis_std]] 17:34, 16 February 2007 (CET) - '''Done''' - [[Testimonials]]<br /> *&lt;strike&gt;[http://www.linuxtogo.org/gowiki/OpenMoko/Translation Translation of OpenMoko]&lt;/strike&gt;--[[User:Mikesh|Mikesh]] 11:42, 18 February 2007 (CET) '''DONE''' - [[Translation]]<br /> *&lt;strike&gt;[http://www.linuxtogo.org/gowiki/OpenMoko/AtFOSDEM FOSDEM]&lt;/strike&gt; <br /> *&lt;strike&gt;[http://www.linuxtogo.org/gowiki/OpenMoko/Glossary Glossary]&lt;/strike&gt;--[[User:AndreasHochsteger|Andreas Hochsteger]] 22:41, 24 February 2006 (CET) - '''DONE''' - [[Glossary]]<br /> *&lt;strike&gt;[http://www.linuxtogo.org/gowiki/OpenMoko/Video_Bounty Video Bounty]&lt;/strike&gt;-- '''ABANDONED''' - New hardware renders this task trivial<br /> <br /> == Development news ==<br /> <br /> Developer news of progress being made on OpenMoko.<br /> <br /> * [http://planet.openmoko.org/ Main planet openmoko feed]<br /> * [http://blogs.gnome.org/thos/2007/08/21/openmoko-20072/ OpenMoko 2007.2 new User Interface style for OpenMoko by OpenedHand]<br /> <br /> <br /> === [[User's Manual]] ===<br /> <br /> An user manual should be created for non geeks. I mean one of those small books you get when you buy a new phone. They are full of pictures, describe basic steps of phone usage and are translated into as many languages as possible.<br /> <br /> The wiki is a mess, somebody should suggest a structure easier to navigate.<br /> <br /> I do not see a point in translating developer pages in other languages than English, but this is subjective.<br /> <br /> --[[User:Iztok.jeras|Iztok.jeras]] 10:56, 23 May 2007 (CEST)<br /> <br /> I am French, but I don't see a point either in translating the developer manual. Mickael.<br /> <br /> My mother language is Spanish. I think that a developer manual written in English is enough -no need for translation to other languages. Raul.<br /> <br /> I have the same idea, but, its free for translate to other laguages. Freddy<br /> <br /> I am French, I think that a basic manual for non-geek could be a good idea…<br /> <br /> --[[User:Bart|Bart]] 10:14, 2 October 2007 (CEST)<br /> I am Dutch, if a dutch user manual is needed I'd love to help.<br /> <br /> [[User:Fradeve11|Fradeve11]]: I give my appreciament and time to translate an user basic manual in Italian ;) very good idea!<br /> <br /> [[User:darktim|darktim]]: I will do the German part. I'm not a coder, so that could be my contribution ;)<br /> <br /> <br /> [[User:Yorick|Yorick]]: I'm willing to do some Dutch translation<br /> <br /> === USB Keyboards ===<br /> <br /> I'm not sure if this is the proper place to post this, but I think it would be an excellent idea to test out the Neo with a USB keyboard and even for OpenMoko to have at least one suggested &amp;&amp; compatible device. I haven't seen details about what standards the Neo's USB device will adhere to (host capabilities? - although that might be somewhat power hungry). Is there even a thing as a keyboard that operates as its own USB host? Actually, even a bluetooth keyboard would be reasonable. I only pose this question because I would like to be able to write snippets of code, and I have some doubts about using the stylus with an on-screen keyboard - especially for certain syntax patterns that are common in most programming languages. <br /> <br /> '''Update''': I'm glad someone else has thought about this too :: [http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#HID_.28Human_Input_Device.29 Neo1973 &amp; Bluetooth HIDs (Human Input Devices)]<br /> <br /> --[[User:Cfriedt|Cfriedt]] 02:07, 20 November 2007 (CET)<br /> <br /> [[Category:Community]]<br /> [[Category:Information]]</div>

Wurp http://wiki.openmoko.org/wiki/Neo_FreeRunner_FAQ 2008-07-24T18:26:51Z

<p>Wurp: added keyboards questions</p> <hr /> <div>== Frequently Asked Questions ==<br /> ===Booting===<br /> '''Q: I can't boot Neo with charger?''' <br /> <br /> '''A:'''<br /> 1. You can't boot GTA02 without a spare battery. You should boot Neo with spare battery and attach your charger, then you can boot into neo.<br /> <br /> 2. Once your phone is booted, remove the spare battery. Freerunner will remain running, <br /> <br /> 3. Insert dead battery and let it charge.<br /> <br /> '''Q:Uable to flash FreeRunner after booting either into NAND or NOR.'''<br /> {{note|Please check [[Getting_Started_with_your_Neo_FreeRunner]] for more information about the flashing image.}}<br /> <br /> I can ssh into the phone via USB per the wiki instructions, but dfu-util does not find the phone. <br /> <br /> This is what I need to run as root and the everything works fine:<br /> root(eno,freerunner)# cat upom<br /> #!/bin/sh<br /> /sbin/ifconfig usb0 192.168.0.200 netmask 255.255.255.0<br /> /sbin/route add -host 192.168.0.202/32 dev usb0<br /> <br /> /bin/echo 1 &gt; /proc/sys/net/ipv4/ip_forward<br /> iptables -F<br /> iptables -A INPUT -s 192.168.0.202 -i usb0 -d 192.168.0.200 -j ACCEPT<br /> iptables -A INPUT -s 192.168.0.200 -i eth+ -d 192.168.0.202 -j ACCEPT<br /> iptables -A INPUT -s 192.168.2.0/24 -i eth+ -d 192.168.0.202 -j ACCEPT<br /> iptables -A INPUT -s 192.168.2.0/24 -i eth+ -d 192.168.2.0/24 -j ACCEPT<br /> <br /> iptables -A FORWARD -s 192.168.0.202 -i usb0 -d 192.168.2.0/24 -o eth+ -j <br /> ACCEPT<br /> iptables -A FORWARD -s 192.168.2.0/24 -i eth+ -d 192.168.0.202 -o usb0 -j <br /> ACCEPT<br /> <br /> iptables -A OUTPUT -d 192.168.2.0/24 -o eth+ -j ACCEPT<br /> iptables -A OUTPUT -d 192.168.0.202 -o usb0 -j ACCEPT<br /> iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24<br /> root(eno,freerunner)#<br /> <br /> '''Q: What image version I used?''' <br /> <br /> '''A:'''<br /> <br /> 1. Kernel version using: uname -a<br /> <br /> 2. Root filesystem using: cat /etc/version or cat /etc/om-version<br /> <br /> 3. u-boot using: grep Bootloader /dev/mtdblock0<br /> <br /> === Battery ===<br /> ==== What is the expected battery life? ====<br /> See [[Neo FreeRunner (GTA02) Battery#Notes_about_expected_battery_life]]<br /> <br /> === GSM ===<br /> <br /> ==== SIM compatibility ====<br /> '''Q:'''Sim card is not working, how do I run diagnostics?<br /> <br /> '''A:'''<br /> Here is the &quot;how to&quot; check.<br /> <br /> Follow [[Manually_using_GSM]] until you get an OK prompt. More detalied documenation please refer [[FreeRunner_unable_to_work_with_3G_SIM_cards]] and [[Carriers]].<br /> <br /> ==== GSM/GPRS information ====<br /> <br /> Following page contain very usaful information:<br /> <br /> * [http://wiki.openmoko.org/wiki/Gsmd GSM Daemon]<br /> <br /> * [http://wiki.openmoko.org/wiki/Gsm General GSM page]<br /> <br /> * [http://wiki.openmoko.org/wiki/Hardware:AT_Commands AT commands]<br /> <br /> * [http://freeyourphone.de/portal_v1/viewtopic.php?f=21&amp;t=295#p2956 Useful script for GPRS]<br /> <br /> <br /> === GPS ===<br /> <br /> '''Q: How do I get the GPS working?''' <br /> <br /> '''A: '''See [http://wiki.openmoko.org/wiki/GTA02_GPS GTA02 GPS]<br /> <br /> === Wi-Fi ===<br /> <br /> '''Q: How do I get the wlan working? '''<br /> <br /> '''A: ''' See [[GTA02 WLAN]]<br /> <br /> === Bluetooth ===<br /> <br /> '''Q: How do I get the Bluetooth working? '''<br /> <br /> '''A: ''' See [[Manually_using_Bluetooth]]<br /> <br /> === Display ===<br /> <br /> ==== Can it 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 /> ==== How to change the background picture of the root window? ====<br /> <br /> Copy '''whatyouwant.png''' over '''/usr/share/pixmaps/wallpaper.png''', best results may come up with pictures that have '''width=480''' and '''height=640'''. I think that the X-server must be restarted, at least it will show up after the next boot.<br /> <br /> === Software ===<br /> <br /> ==== Does it support Java? ====<br /> There is a [https://wiki.evolvis.org/jalimo/index.php/OpenMoko port of Jalimo] for Openmoko.<br /> <br /> ==== Does it support Flash? So can I watch YouTube? ====<br /> <br /> ==== How can I type a '/' in the software keyboard? ====<br /> <br /> See [[Switching Keyboards]]<br /> <br /> ==== How do I get a qwerty software keyboard? ====<br /> <br /> See [[Switching Keyboards]]<br /> <br /> <br /> [[Category:GTA02 Hardware]]</div>

Wurp http://wiki.openmoko.org/wiki/SHR_Development 2008-07-22T03:02:41Z

<p>Wurp: /* Run bitbake */</p> <hr /> <div>== Building openmoko-dialer3 ==<br /> Currently this is the only package of any size being developed for SHR, and it's the only one with any instructions. If you start another SHR project (please check with [[User:Wurp|Bobby]] before starting one), put instructions for working on the project here!<br /> <br /> === Before beginning ===<br /> You must build openembedded before you can build SHR packages. The easiest way is to go to http://wiki.openmoko.org/wiki/Mokomakefile and build using the instructions for FSO.<br /> <br /> The rest of these instructions are written assuming that you used Mokomakefile and that the directory you downloaded the base Makefile into (using wget) is $MOKO.<br /> <br /> You must also download the SHR code using subversion. See http://projects.openmoko.org/projects/shr. We will refer to the directory to which you downloaded the project as $SHRSVN. (This directory should contain $SHRSVN/packages/openmoko-dialer3.bb)<br /> <br /> === Set up your BBPATH ===<br /> <br /> export BBPATH=.:$MOKO/openembedded/:$MOKO/bitbake/:$MOKO/:$SHRSVN/trunk/packages/<br /> <br /> === Set up the CACHE ===<br /> <br /> export CACHE=tmp/cache<br /> <br /> <br /> <br /> === Set up your local.conf ===<br /> Cd to your selected build directory.<br /> <br /> Create a directory under your current directory called 'conf'.<br /> <br /> cp $MOKO/openembedded/conf/local.conf conf/local.conf.<br /> <br /> Append the following lines to your local.conf:<br /> BBFILES += &quot;$SHRSVN/trunk/packages/*.bb $MOKO/openembedded/packages/*/*.bb&quot;<br /> SELECTED_OPTIMIZATION = &quot;-Os -g&quot;<br /> <br /> ''Note: Spaces are important in your bitbake conf files! You must have spaces before &amp; after the = or +=''<br /> <br /> === Add your cross-compiler to your PATH ===<br /> <br /> export PATH=$MOKO/build/tmp/cross/bin/:$MOKO/build/tmp/staging/x86_64-linux/usr/bin:$PATH<br /> <br /> === Run bitbake ===<br /> <br /> bitbake openmoko-dialer3<br /> <br /> After the first time you build successfully, you can build with<br /> <br /> bitbake -b openmoko-dialog3_svn<br /> <br /> which is much faster.<br /> <br /> === To recompile, and only recompile ===<br /> <br /> bitbake -c compile -b $SHRSVN/trunk/packages/openmoko-dialer3.bb<br /> <br /> === Troubleshooting ===<br /> <br /> ==== General ====<br /> One thing to try is to unset all environment variables not listed in this page. LIBPATH and INCLUDE can be particularly troublesome.<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]<br /> [[Category:SHR]]<br /> [[Category:SHR Devel]]</div>

Wurp http://wiki.openmoko.org/wiki/SHR_Development 2008-07-22T00:33:31Z

<p>Wurp: /* Run bitbake */</p> <hr /> <div>== Building openmoko-dialer3 ==<br /> Currently this is the only package of any size being developed for SHR, and it's the only one with any instructions. If you start another SHR project (please check with [[User:Wurp][Bobby]] before starting one), put instructions for working on the project here!<br /> <br /> === Before beginning ===<br /> You must build openembedded before you can build SHR packages. The easiest way is to go to http://wiki.openmoko.org/wiki/Mokomakefile and build using the instructions for FSO.<br /> <br /> The rest of these instructions are written assuming that you used Mokomakefile and that the directory you downloaded the base Makefile into (using wget) is $MOKO.<br /> <br /> You must also download the SHR code using subversion. See http://projects.openmoko.org/projects/shr. We will refer to the directory to which you downloaded the project as $SHRSVN. (This directory should contain $SHRSVN/packages/openmoko-dialer3.bb)<br /> <br /> === Set up your BBPATH ===<br /> <br /> export BBPATH=.:$MOKO/openembedded/:$MOKO/bitbake/:$MOKO/:$SHRSVN/trunk/packages/<br /> <br /> === Set up the CACHE ===<br /> <br /> export CACHE=tmp/cache<br /> <br /> <br /> <br /> === Set up your local.conf ===<br /> Cd to your selected build directory.<br /> <br /> Create a directory under your current directory called 'conf'.<br /> <br /> cp $MOKO/openembedded/conf/local.conf conf/local.conf.<br /> <br /> Append the following lines to your local.conf:<br /> BBFILES += &quot;$SHRSVN/trunk/packages/*.bb $MOKO/openembedded/packages/*/*.bb&quot;<br /> SELECTED_OPTIMIZATION = &quot;-Os -g&quot;<br /> <br /> ''Note: Spaces are important in your bitbake conf files! You must have spaces before &amp; after the = or +=''<br /> <br /> === Add your cross-compiler to your PATH ===<br /> <br /> export PATH=$MOKO/build/tmp/cross/bin/:$MOKO/build/tmp/staging/x86_64-linux/usr/bin:$PATH<br /> <br /> === Run bitbake ===<br /> <br /> bitbake openmoko-dialer3<br /> <br /> === To recompile, and only recompile ===<br /> <br /> bitbake -c compile -b $SHRSVN/trunk/packages/openmoko-dialer3.bb<br /> <br /> === Troubleshooting ===<br /> <br /> ==== General ====<br /> One thing to try is to unset all environment variables not listed in this page. LIBPATH and INCLUDE can be particularly troublesome.<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]<br /> [[Category:SHR]]<br /> [[Category:SHR Devel]]</div>

Wurp http://wiki.openmoko.org/wiki/SHR_Development 2008-07-22T00:32:56Z

<p>Wurp: /* Set up your local.conf */</p> <hr /> <div>== Building openmoko-dialer3 ==<br /> Currently this is the only package of any size being developed for SHR, and it's the only one with any instructions. If you start another SHR project (please check with [[User:Wurp][Bobby]] before starting one), put instructions for working on the project here!<br /> <br /> === Before beginning ===<br /> You must build openembedded before you can build SHR packages. The easiest way is to go to http://wiki.openmoko.org/wiki/Mokomakefile and build using the instructions for FSO.<br /> <br /> The rest of these instructions are written assuming that you used Mokomakefile and that the directory you downloaded the base Makefile into (using wget) is $MOKO.<br /> <br /> You must also download the SHR code using subversion. See http://projects.openmoko.org/projects/shr. We will refer to the directory to which you downloaded the project as $SHRSVN. (This directory should contain $SHRSVN/packages/openmoko-dialer3.bb)<br /> <br /> === Set up your BBPATH ===<br /> <br /> export BBPATH=.:$MOKO/openembedded/:$MOKO/bitbake/:$MOKO/:$SHRSVN/trunk/packages/<br /> <br /> === Set up the CACHE ===<br /> <br /> export CACHE=tmp/cache<br /> <br /> <br /> <br /> === Set up your local.conf ===<br /> Cd to your selected build directory.<br /> <br /> Create a directory under your current directory called 'conf'.<br /> <br /> cp $MOKO/openembedded/conf/local.conf conf/local.conf.<br /> <br /> Append the following lines to your local.conf:<br /> BBFILES += &quot;$SHRSVN/trunk/packages/*.bb $MOKO/openembedded/packages/*/*.bb&quot;<br /> SELECTED_OPTIMIZATION = &quot;-Os -g&quot;<br /> <br /> ''Note: Spaces are important in your bitbake conf files! You must have spaces before &amp; after the = or +=''<br /> <br /> === Add your cross-compiler to your PATH ===<br /> <br /> export PATH=$MOKO/build/tmp/cross/bin/:$MOKO/build/tmp/staging/x86_64-linux/usr/bin:$PATH<br /> <br /> === Run bitbake ===<br /> <br /> bitbake -b $SHRSVN/trunk/packages/openmoko-dialer3.bb<br /> <br /> === To recompile, and only recompile ===<br /> <br /> bitbake -c compile -b $SHRSVN/trunk/packages/openmoko-dialer3.bb<br /> <br /> === Troubleshooting ===<br /> <br /> ==== General ====<br /> One thing to try is to unset all environment variables not listed in this page. LIBPATH and INCLUDE can be particularly troublesome.<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]<br /> [[Category:SHR]]<br /> [[Category:SHR Devel]]</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-07-21T22:54:27Z

<p>Wurp: /* How to join */</p> <hr /> <div>== Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the [[Openmoko2007.2]] GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br /> <br /> (We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br /> <br /> Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br /> <br /> == Why SHR exists ==<br /> This is long and rambling, and maybe more of a tirade than information, but it does give some background on why this project was started. The overview gives, well, the overview, this is more of a deeper examination of the existing releases and why we felt we needed something new.<br /> <br /> Feel free to skip this whole section if you already think SHR is a good idea :-)<br /> <br /> === Why not ASU? ===<br /> ASU is the distro that OM is putting their main effort into right now. ASU looks very slick, but is very unstable right now, and is likely to be unstable and feature-poor for some time.<br /> <br /> === Why not 2007.2? ===<br /> 2007.2 is the &quot;old&quot; Openmoko distribution, now unsupported. Unsupported == often broken. Also, neither calls nor suspend/resume ever worked reliably.<br /> <br /> === Why not Qtopia? ===<br /> You can also install Qtopia on the phone, once TrollTech puts the images up again :-(<br /> <br /> Qtopia is stable, but it doesn't suspend &amp; resume (so the battery life is crap). And you can only build qt apps on Qtopia, which means lots of linux apps you might want to port suddenly got a lot harder to port. And some people just don't like developing for qt.<br /> <br /> Also, as far as I know, there is no documented build procedure for Qtopia on Openmoko.<br /> <br /> === Why not FSO? ===<br /> FSO is the initiative by Mickey Lauer and crew to create a good [[D-Bus]] infrastructure which runs on the neos, among other devices.<br /> <br /> FSO is by far the most stable &amp; usable release, if all you want is a phone. (I mean *all*. It just has a dialer right now, not even call history.)<br /> <br /> FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br /> <br /> Other people are supposed to put a front end on FSO. So that's what we're doing.<br /> <br /> === Why SHR? ===<br /> So SHR is FSO, with us doing the necessary work to port the old high-functionality 2007.2 stuff on a stable call platform. We have an adapter from the 2007.2 call service to the FSO call service and we're installing the basic 2007.2 apps on the FSO baseline install.<br /> <br /> In theory, it should be very simple, and should give us dialer, contact management, SMS, terminal, media player, gps app, etc. since all those already work on 2007.2. And the dialer should be stable, which it wasn't in 2007.2<br /> <br /> == First steps ==<br /> The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br /> <br /> We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br /> <br /> == Interest ==<br /> Here's a list of people who've expressed an interest in working on the SHR.<br /> <br /> * [[User:Wurp|wurp2]]<br /> * [[User:Ferric|ferric]]<br /> * [[User:Paulproteus|paulproteus]]<br /> * [[User:Ainulindale|Ainulindale]]<br /> * [[User:jluis|Jose Luis]]<br /> * [[User:Kevin_Dean|Kevin Dean]]<br /> * [[User:Cb22|cb22]]<br /> * [[User:Jeremy-list|Jeremy List]]<br /> * mwester<br /> * [[User:MarcOChapeau|MarcO'Chapeau]]<br /> * [[User:kd8ikt|kd8ikt]]<br /> <br /> == How to join ==<br /> * Please add your name (with a link to your user page) to the list above.<br /> * You should also send a request to join on the [http://projects.openmoko.org/projects/shr SHR project] on the OM projects page to join.<br /> * Join [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel shr-devel@lists.projects.openmoko.org] and send an introductory email.<br /> <br /> The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.<br /> <br /> See [[SHR Development]] to find out how to set up your development environment to work on existing SHR packages.<br /> <br /> Hang out in #openmoko-cdevel on chat.freenode.net between 5pm and 11pm GMT to chat with the people developing SHR. (Primarily MarcOChapeau and Ainulindale.)<br /> <br /> == Tasks &amp; status ==<br /> Here's a list of the tasks for the SHR:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space; just need to talk about git branches<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |-<br /> |port 2007.2 gsm-using apps to use ophoned or ogsmd instead<br /> |Pre-Alpha<br /> |[[User:Ainulindale|Ainulindale]]<br /> |MarcOChapeau<br /> |2008-07-10<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |[[User:Kevin_Dean|Kevin Dean]]<br /> |Nobody<br /> |2008-07-05<br /> |-<br /> |[[#List_of_packages_included|Identify packages to go into SHR]]<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Anyone &amp; everyone<br /> |2008-07-12<br /> |-<br /> |Identify differences between FSO &amp; 2007.2 that need investigation<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-12<br /> |-<br /> |Switch FSO to use the 2007.2 matchbox session<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |MarcOChapeau<br /> |2008-07-12<br /> |-<br /> |Integrate [http://moko.mwester.net/fixes.html mwester's pulseaudio resume fix] into SHR<br /> |Not started<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-15<br /> |}<br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * ophoned<br /> * preferencesd<br /> * pimd<br /> * odeviced<br /> * lots more...<br /> <br /> From 2007.2:<br /> * TODO<br /> * lots more...<br /> <br /> From ASU:<br /> * TODO<br /> * lots more...<br /> <br /> == Project links ==<br /> [http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br /> <br /> == IRC conversation about how we're using revision control ==<br /> <br /> ''This is deprecated, for now we use shr-devel as our only repository. This will change after the first SHR release.''&lt;br/&gt;<br /> From 2007-07-07<br /> &lt;pre&gt;<br /> 12:36 &lt; wurp2&gt; Everything *new* goes on OM projects site<br /> 12:36 &lt; Ainulindale&gt; I totally agree<br /> 12:36 &lt; wurp2&gt; Updates to 2007.2 apps go back into the home svn<br /> 12:36 &lt; Ainulindale&gt; paulproteus: no, you're an external cabal all by yourself<br /> :-)<br /> 12:36 &lt; cb22&gt; anyone planning on drawing up a roadmap?<br /> 12:36 &lt; paulproteus&gt; cb22, We can do that in Trac in fact.<br /> 12:36 &lt; wurp2&gt; And changes to the underlying release go as patches into our OE<br /> branch, yes?<br /> 12:36 &lt; paulproteus&gt; (or on the wiki page)<br /> 12:36 &lt; paulproteus&gt; wurp2, Right<br /> 12:36 &lt; paulproteus&gt; mwester, Sanity-check my terminology where I mess things<br /> up!<br /> 12:37 &lt; Ainulindale&gt; hmmm fuzzy for me but what should go in OM and what should<br /> go in OE ?<br /> 12:37 &lt;@mwester&gt; Sure<br /> 12:37 &lt;@mwester&gt; What do you mean by OM?<br /> 12:37 &lt; paulproteus&gt; Ainulindale, New software we write goes in the<br /> projects.openmoko.org.<br /> 12:37 &lt;@mwester&gt; right.<br /> 12:37 &lt; Ainulindale&gt; Ok so the wrapper for example<br /> 12:37 &lt; wurp2&gt; Anything stand-alone goes in OM (projects.openmoko.org)<br /> 12:37 &lt; wurp2&gt; yeah<br /> 12:37 &lt;@mwester&gt; So we will use projects.openmoko.org for as much as we can,<br /> and OE to build the distro.<br /> 12:37 &lt; Ainulindale&gt; Sounds right to me<br /> 12:37 &lt; wurp2&gt; Great!<br /> 12:38 &lt;@mwester&gt; We *will not* use the OM git repo, as that is owned and<br /> controlled by Openmoko the company...<br /> &lt;/pre&gt;<br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]<br /> [[Category:SHR]]</div>

Wurp http://wiki.openmoko.org/wiki/SHR_Development 2008-07-19T16:22:10Z

<p>Wurp: </p> <hr /> <div>== Building openmoko-dialer3 ==<br /> Currently this is the only package of any size being developed for SHR, and it's the only one with any instructions. If you start another SHR project (please check with [[User:Wurp][Bobby]] before starting one), put instructions for working on the project here!<br /> <br /> === Before beginning ===<br /> You must build openembedded before you can build SHR packages. The easiest way is to go to http://wiki.openmoko.org/wiki/Mokomakefile and build using the instructions for FSO.<br /> <br /> The rest of these instructions are written assuming that you used Mokomakefile and that the directory you downloaded the base Makefile into (using wget) is $MOKO.<br /> <br /> You must also download the SHR code using subversion. See http://projects.openmoko.org/projects/shr. We will refer to the directory to which you downloaded the project as $SHRSVN. (This directory should contain $SHRSVN/packages/openmoko-dialer3.bb)<br /> <br /> === Set up your BBPATH ===<br /> <br /> export BBPATH=.:$MOKO/openembedded/:$MOKO/bitbake/:$MOKO/:$SHRSVN/trunk/packages/<br /> <br /> === Set up the CACHE ===<br /> <br /> export CACHE=tmp/cache<br /> <br /> <br /> <br /> === Set up your local.conf ===<br /> Cd to your selected build directory.<br /> <br /> Create a directory under your current directory called 'conf'.<br /> <br /> cp $MOKO/openembedded/conf/local.conf conf/local.conf.<br /> <br /> Append the following lines to your local.conf:<br /> BBFILES+=&quot;$SHRSVN/trunk/packages/*.bb $MOKO/openembedded/packages/*/*.bb&quot;<br /> SELECTED_OPTIMIZATION = &quot;-Os -g&quot;<br /> <br /> === Add your cross-compiler to your PATH ===<br /> <br /> export PATH=$MOKO/build/tmp/cross/bin/:$MOKO/build/tmp/staging/x86_64-linux/usr/bin:$PATH<br /> <br /> === Run bitbake ===<br /> <br /> bitbake -b $SHRSVN/trunk/packages/openmoko-dialer3.bb<br /> <br /> === To recompile, and only recompile ===<br /> <br /> bitbake -c compile -b $SHRSVN/trunk/packages/openmoko-dialer3.bb<br /> <br /> === Troubleshooting ===<br /> <br /> ==== General ====<br /> One thing to try is to unset all environment variables not listed in this page. LIBPATH and INCLUDE can be particularly troublesome.<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]<br /> [[Category:SHR]]<br /> [[Category:SHR Devel]]</div>

Wurp http://wiki.openmoko.org/wiki/SHR_Development 2008-07-19T16:20:26Z

<p>Wurp: /* Add your cross-compiler to your PATH */</p> <hr /> <div>== Building openmoko-dialer3 ==<br /> Currently this is the only package of any size being developed for SHR, and it's the only one with any instructions. If you start another SHR project (please check with [[User:Wurp][Bobby]] before starting one), put instructions for working on the project here!<br /> <br /> === Before beginning ===<br /> You must build openembedded before you can build SHR packages. The easiest way is to go to http://wiki.openmoko.org/wiki/Mokomakefile and build using the instructions for FSO.<br /> <br /> The rest of these instructions are written assuming that you used Mokomakefile and that the directory you downloaded the base Makefile into (using wget) is $MOKO.<br /> <br /> You must also download the SHR code using subversion. See http://projects.openmoko.org/projects/shr. We will refer to the directory to which you downloaded the project as $SHRSVN. (This directory should contain $SHRSVN/packages/openmoko-dialer3.bb)<br /> <br /> === Set up your BBPATH ===<br /> <br /> export BBPATH=.:$MOKO/openembedded/:$MOKO/bitbake/:$MOKO/:$SHRSVN/trunk/packages/<br /> <br /> === Set up the CACHE ===<br /> <br /> export CACHE=tmp/cache<br /> <br /> <br /> <br /> === Set up your local.conf ===<br /> Cd to your selected build directory.<br /> <br /> Create a directory under your current directory called 'conf'.<br /> <br /> cp $MOKO/openembedded/conf/local.conf conf/local.conf.<br /> <br /> Append the following lines to your local.conf:<br /> BBFILES+=&quot;$SHRSVN/trunk/packages/*.bb $MOKO/openembedded/packages/*/*.bb&quot;<br /> SELECTED_OPTIMIZATION = &quot;-Os -g&quot;<br /> <br /> === Add your cross-compiler to your PATH ===<br /> <br /> export PATH=$MOKO/build/tmp/cross/bin/:$MOKO/build/tmp/staging/x86_64-linux/usr/bin:$PATH<br /> <br /> === Run bitbake ===<br /> <br /> bitbake -b $SHRSVN/trunk/packages/openmoko-dialer3.bb<br /> <br /> === To recompile, and only recompile ===<br /> <br /> bitbake -c compile -b $SHRSVN/trunk/packages/openmoko-dialer3.bb<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]<br /> [[Category:SHR]]<br /> [[Category:SHR Devel]]</div>

Wurp http://wiki.openmoko.org/wiki/SHR_Development 2008-07-19T16:19:23Z

<p>Wurp: /* Set up your local.conf */</p> <hr /> <div>== Building openmoko-dialer3 ==<br /> Currently this is the only package of any size being developed for SHR, and it's the only one with any instructions. If you start another SHR project (please check with [[User:Wurp][Bobby]] before starting one), put instructions for working on the project here!<br /> <br /> === Before beginning ===<br /> You must build openembedded before you can build SHR packages. The easiest way is to go to http://wiki.openmoko.org/wiki/Mokomakefile and build using the instructions for FSO.<br /> <br /> The rest of these instructions are written assuming that you used Mokomakefile and that the directory you downloaded the base Makefile into (using wget) is $MOKO.<br /> <br /> You must also download the SHR code using subversion. See http://projects.openmoko.org/projects/shr. We will refer to the directory to which you downloaded the project as $SHRSVN. (This directory should contain $SHRSVN/packages/openmoko-dialer3.bb)<br /> <br /> === Set up your BBPATH ===<br /> <br /> export BBPATH=.:$MOKO/openembedded/:$MOKO/bitbake/:$MOKO/:$SHRSVN/trunk/packages/<br /> <br /> === Set up the CACHE ===<br /> <br /> export CACHE=tmp/cache<br /> <br /> <br /> <br /> === Set up your local.conf ===<br /> Cd to your selected build directory.<br /> <br /> Create a directory under your current directory called 'conf'.<br /> <br /> cp $MOKO/openembedded/conf/local.conf conf/local.conf.<br /> <br /> Append the following lines to your local.conf:<br /> BBFILES+=&quot;$SHRSVN/trunk/packages/*.bb $MOKO/openembedded/packages/*/*.bb&quot;<br /> SELECTED_OPTIMIZATION = &quot;-Os -g&quot;<br /> <br /> === Add your cross-compiler to your PATH ===<br /> (I'm not sure if this stage is necessary, or even a good idea.)<br /> <br /> export PATH=$MOKO/build/tmp/staging/*/usr/bin<br /> <br /> === Run bitbake ===<br /> <br /> bitbake -b $SHRSVN/trunk/packages/openmoko-dialer3.bb<br /> <br /> === To recompile, and only recompile ===<br /> <br /> bitbake -c compile -b $SHRSVN/trunk/packages/openmoko-dialer3.bb<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]<br /> [[Category:SHR]]<br /> [[Category:SHR Devel]]</div>

Wurp http://wiki.openmoko.org/wiki/SHR_Development 2008-07-19T16:17:35Z

<p>Wurp: /* Set up your BBPATH */</p> <hr /> <div>== Building openmoko-dialer3 ==<br /> Currently this is the only package of any size being developed for SHR, and it's the only one with any instructions. If you start another SHR project (please check with [[User:Wurp][Bobby]] before starting one), put instructions for working on the project here!<br /> <br /> === Before beginning ===<br /> You must build openembedded before you can build SHR packages. The easiest way is to go to http://wiki.openmoko.org/wiki/Mokomakefile and build using the instructions for FSO.<br /> <br /> The rest of these instructions are written assuming that you used Mokomakefile and that the directory you downloaded the base Makefile into (using wget) is $MOKO.<br /> <br /> You must also download the SHR code using subversion. See http://projects.openmoko.org/projects/shr. We will refer to the directory to which you downloaded the project as $SHRSVN. (This directory should contain $SHRSVN/packages/openmoko-dialer3.bb)<br /> <br /> === Set up your BBPATH ===<br /> <br /> export BBPATH=.:$MOKO/openembedded/:$MOKO/bitbake/:$MOKO/:$SHRSVN/trunk/packages/<br /> <br /> === Set up the CACHE ===<br /> <br /> export CACHE=tmp/cache<br /> <br /> <br /> <br /> === Set up your local.conf ===<br /> Cd to your selected build directory.<br /> <br /> Create a directory under your current directory called 'conf'.<br /> <br /> cp $MOKO/openembedded/conf/local.conf conf/local.conf.<br /> <br /> Append the following lines to your local.conf:<br /> BBFILES+=&quot;$SHRSVN/trunk/packages/*.bb&quot;<br /> SELECTED_OPTIMIZATION = &quot;-Os -g&quot;<br /> <br /> <br /> === Add your cross-compiler to your PATH ===<br /> (I'm not sure if this stage is necessary, or even a good idea.)<br /> <br /> export PATH=$MOKO/build/tmp/staging/*/usr/bin<br /> <br /> === Run bitbake ===<br /> <br /> bitbake -b $SHRSVN/trunk/packages/openmoko-dialer3.bb<br /> <br /> === To recompile, and only recompile ===<br /> <br /> bitbake -c compile -b $SHRSVN/trunk/packages/openmoko-dialer3.bb<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]<br /> [[Category:SHR]]<br /> [[Category:SHR Devel]]</div>

Wurp http://wiki.openmoko.org/wiki/SHR_Development 2008-07-18T05:07:23Z

<p>Wurp: </p> <hr /> <div>== Building openmoko-dialer3 ==<br /> Currently this is the only package of any size being developed for SHR, and it's the only one with any instructions. If you start another SHR project (please check with [[User:Wurp][Bobby]] before starting one), put instructions for working on the project here!<br /> <br /> === Before beginning ===<br /> You must build openembedded before you can build SHR packages. The easiest way is to go to http://wiki.openmoko.org/wiki/Mokomakefile and build using the instructions for FSO.<br /> <br /> The rest of these instructions are written assuming that you used Mokomakefile and that the directory you downloaded the base Makefile into (using wget) is $MOKO.<br /> <br /> You must also download the SHR code using subversion. See http://projects.openmoko.org/projects/shr. We will refer to the directory to which you downloaded the project as $SHRSVN. (This directory should contain $SHRSVN/packages/openmoko-dialer3.bb)<br /> <br /> === Set up your BBPATH ===<br /> <br /> export BBPATH=.:$MOKO/openembedded/:$MOKO/<br /> <br /> <br /> === Set up the CACHE ===<br /> <br /> export CACHE=tmp/cache<br /> <br /> <br /> <br /> === Set up your local.conf ===<br /> Cd to your selected build directory.<br /> <br /> Create a directory under your current directory called 'conf'.<br /> <br /> cp $MOKO/openembedded/conf/local.conf conf/local.conf.<br /> <br /> Append the following lines to your local.conf:<br /> BBFILES+=&quot;$SHRSVN/trunk/packages/*.bb&quot;<br /> SELECTED_OPTIMIZATION = &quot;-Os -g&quot;<br /> <br /> <br /> === Add your cross-compiler to your PATH ===<br /> (I'm not sure if this stage is necessary, or even a good idea.)<br /> <br /> export PATH=$MOKO/build/tmp/staging/*/usr/bin<br /> <br /> === Run bitbake ===<br /> <br /> bitbake -b $SHRSVN/trunk/packages/openmoko-dialer3.bb<br /> <br /> === To recompile, and only recompile ===<br /> <br /> bitbake -c compile -b $SHRSVN/trunk/packages/openmoko-dialer3.bb<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]<br /> [[Category:SHR]]<br /> [[Category:SHR Devel]]</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-07-18T04:59:17Z

<p>Wurp: </p> <hr /> <div>== Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the [[Openmoko2007.2]] GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br /> <br /> (We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br /> <br /> Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br /> <br /> == Why SHR exists ==<br /> This is long and rambling, and maybe more of a tirade than information, but it does give some background on why this project was started. The overview gives, well, the overview, this is more of a deeper examination of the existing releases and why we felt we needed something new.<br /> <br /> Feel free to skip this whole section if you already think SHR is a good idea :-)<br /> <br /> === Why not ASU? ===<br /> ASU is the distro that OM is putting their main effort into right now. ASU looks very slick, but is very unstable right now, and is likely to be unstable and feature-poor for some time.<br /> <br /> === Why not 2007.2? ===<br /> 2007.2 is the &quot;old&quot; Openmoko distribution, now unsupported. Unsupported == often broken. Also, neither calls nor suspend/resume ever worked reliably.<br /> <br /> === Why not Qtopia? ===<br /> You can also install Qtopia on the phone, once TrollTech puts the images up again :-(<br /> <br /> Qtopia is stable, but it doesn't suspend &amp; resume (so the battery life is crap). And you can only build qt apps on Qtopia, which means lots of linux apps you might want to port suddenly got a lot harder to port. And some people just don't like developing for qt.<br /> <br /> Also, as far as I know, there is no documented build procedure for Qtopia on Openmoko.<br /> <br /> === Why not FSO? ===<br /> FSO is the initiative by Mickey Lauer and crew to create a good [[D-Bus]] infrastructure which runs on the neos, among other devices.<br /> <br /> FSO is by far the most stable &amp; usable release, if all you want is a phone. (I mean *all*. It just has a dialer right now, not even call history.)<br /> <br /> FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br /> <br /> Other people are supposed to put a front end on FSO. So that's what we're doing.<br /> <br /> === Why SHR? ===<br /> So SHR is FSO, with us doing the necessary work to port the old high-functionality 2007.2 stuff on a stable call platform. We have an adapter from the 2007.2 call service to the FSO call service and we're installing the basic 2007.2 apps on the FSO baseline install.<br /> <br /> In theory, it should be very simple, and should give us dialer, contact management, SMS, terminal, media player, gps app, etc. since all those already work on 2007.2. And the dialer should be stable, which it wasn't in 2007.2<br /> <br /> == First steps ==<br /> The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br /> <br /> We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br /> <br /> == Interest ==<br /> Here's a list of people who've expressed an interest in working on the SHR.<br /> <br /> * [[User:Wurp|wurp2]]<br /> * [[User:Ferric|ferric]]<br /> * [[User:Paulproteus|paulproteus]]<br /> * [[User:Ainulindale|Ainulindale]]<br /> * [[User:jluis|Jose Luis]]<br /> * [[User:Kevin_Dean|Kevin Dean]]<br /> * [[User:Cb22|cb22]]<br /> * [[User:Jeremy-list|Jeremy List]]<br /> * mwester<br /> * [[User:MarcOChapeau|MarcO'Chapeau]]<br /> * [[User:kd8ikt|kd8ikt]]<br /> <br /> == How to join ==<br /> * Please add your name (with a link to your user page) to the list above.<br /> * You should also send a request to join on the [http://projects.openmoko.org/projects/shr SHR project] on the OM projects page to join.<br /> * Join [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel shr-devel@lists.projects.openmoko.org] and send an introductory email.<br /> <br /> The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.<br /> <br /> See [[SHR Development]] to find out how to set up your development environment to work on existing SHR packages.<br /> <br /> == Tasks &amp; status ==<br /> Here's a list of the tasks for the SHR:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space; just need to talk about git branches<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |-<br /> |port 2007.2 gsm-using apps to use ophoned or ogsmd instead<br /> |Pre-Alpha<br /> |[[User:Ainulindale|Ainulindale]]<br /> |MarcOChapeau<br /> |2008-07-10<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |[[User:Kevin_Dean|Kevin Dean]]<br /> |Nobody<br /> |2008-07-05<br /> |-<br /> |[[#List_of_packages_included|Identify packages to go into SHR]]<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Anyone &amp; everyone<br /> |2008-07-12<br /> |-<br /> |Identify differences between FSO &amp; 2007.2 that need investigation<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-12<br /> |-<br /> |Switch FSO to use the 2007.2 matchbox session<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |MarcOChapeau<br /> |2008-07-12<br /> |-<br /> |Integrate [http://moko.mwester.net/fixes.html mwester's pulseaudio resume fix] into SHR<br /> |Not started<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-15<br /> |}<br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * ophoned<br /> * preferencesd<br /> * pimd<br /> * odeviced<br /> * lots more...<br /> <br /> From 2007.2:<br /> * TODO<br /> * lots more...<br /> <br /> From ASU:<br /> * TODO<br /> * lots more...<br /> <br /> == Project links ==<br /> [http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br /> <br /> == IRC conversation about how we're using revision control ==<br /> <br /> ''This is deprecated, for now we use shr-devel as our only repository. This will change after the first SHR release.''&lt;br/&gt;<br /> From 2007-07-07<br /> &lt;pre&gt;<br /> 12:36 &lt; wurp2&gt; Everything *new* goes on OM projects site<br /> 12:36 &lt; Ainulindale&gt; I totally agree<br /> 12:36 &lt; wurp2&gt; Updates to 2007.2 apps go back into the home svn<br /> 12:36 &lt; Ainulindale&gt; paulproteus: no, you're an external cabal all by yourself<br /> :-)<br /> 12:36 &lt; cb22&gt; anyone planning on drawing up a roadmap?<br /> 12:36 &lt; paulproteus&gt; cb22, We can do that in Trac in fact.<br /> 12:36 &lt; wurp2&gt; And changes to the underlying release go as patches into our OE<br /> branch, yes?<br /> 12:36 &lt; paulproteus&gt; (or on the wiki page)<br /> 12:36 &lt; paulproteus&gt; wurp2, Right<br /> 12:36 &lt; paulproteus&gt; mwester, Sanity-check my terminology where I mess things<br /> up!<br /> 12:37 &lt; Ainulindale&gt; hmmm fuzzy for me but what should go in OM and what should<br /> go in OE ?<br /> 12:37 &lt;@mwester&gt; Sure<br /> 12:37 &lt;@mwester&gt; What do you mean by OM?<br /> 12:37 &lt; paulproteus&gt; Ainulindale, New software we write goes in the<br /> projects.openmoko.org.<br /> 12:37 &lt;@mwester&gt; right.<br /> 12:37 &lt; Ainulindale&gt; Ok so the wrapper for example<br /> 12:37 &lt; wurp2&gt; Anything stand-alone goes in OM (projects.openmoko.org)<br /> 12:37 &lt; wurp2&gt; yeah<br /> 12:37 &lt;@mwester&gt; So we will use projects.openmoko.org for as much as we can,<br /> and OE to build the distro.<br /> 12:37 &lt; Ainulindale&gt; Sounds right to me<br /> 12:37 &lt; wurp2&gt; Great!<br /> 12:38 &lt;@mwester&gt; We *will not* use the OM git repo, as that is owned and<br /> controlled by Openmoko the company...<br /> &lt;/pre&gt;<br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]<br /> [[Category:SHR]]</div>

Wurp http://wiki.openmoko.org/wiki/SHR_Development 2008-07-18T04:58:53Z

<p>Wurp: </p> <hr /> <div>== Building openmoko-dialer3 ==<br /> Currently this is the only package of any size being developed for SHR, and it's the only one with any instructions. If you start another SHR project (please check with [[User:Wurp][Bobby]] before starting one), put instructions for working on the project here!<br /> <br /> === Before beginning ===<br /> You must build openembedded before you can build SHR packages. The easiest way is to go to http://wiki.openmoko.org/wiki/Mokomakefile and build using the instructions for FSO.<br /> <br /> The rest of these instructions are written assuming that you used Mokomakefile and that the directory you downloaded the base Makefile into (using wget) is $MOKO.<br /> <br /> You must also download the SHR code using subversion. See http://projects.openmoko.org/projects/shr. We will refer to the directory to which you downloaded the project as $SHRSVN. (This directory should contain $SHRSVN/packages/openmoko-dialer3.bb)<br /> <br /> === Set up your BBPATH ===<br /> <br /> export BBPATH=.:$MOKO/openembedded/:$MOKO/<br /> <br /> <br /> === Set up the CACHE ===<br /> <br /> export CACHE=tmp/cache<br /> <br /> <br /> <br /> === Set up your local.conf ===<br /> Cd to your selected build directory.<br /> <br /> Create a directory under your current directory called 'conf'.<br /> <br /> cp $MOKO/openembedded/conf/local.conf conf/local.conf.<br /> <br /> Append the following lines to your local.conf:<br /> BBFILES+=&quot;$SHRSVN/trunk/packages/*.bb&quot;<br /> SELECTED_OPTIMIZATION = &quot;-Os -g&quot;<br /> <br /> <br /> === Add your cross-compiler to your PATH ===<br /> (I'm not sure if this stage is necessary, or even a good idea.)<br /> <br /> export PATH=$MOKO/build/tmp/staging/*/usr/bin<br /> <br /> === Run bitbake ===<br /> <br /> bitbake -b $SHRSVN/trunk/packages/openmoko-dialer3.bb<br /> <br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]<br /> [[Category:SHR]]<br /> [[Category:SHR Devel]]</div>

Wurp http://wiki.openmoko.org/wiki/SHR_Development 2008-07-18T04:57:43Z

<p>Wurp: New page: == Building openmoko-dialer3 == Currently this is the only package of any size being developed for SHR, and it's the only one with any instructions. If you start another SHR project (plea...</p> <hr /> <div>== Building openmoko-dialer3 ==<br /> Currently this is the only package of any size being developed for SHR, and it's the only one with any instructions. If you start another SHR project (please check with [[User:Wurp][Bobby]] before starting one), put instructions for working on the project here!<br /> <br /> === Before beginning ===<br /> You must build openembedded before you can build SHR packages. The easiest way is to go to http://wiki.openmoko.org/wiki/Mokomakefile and build using the instructions for FSO.<br /> <br /> The rest of these instructions are written assuming that you used Mokomakefile and that the directory you downloaded the base Makefile into (using wget) is $MOKO.<br /> <br /> You must also download the SHR code using subversion. See http://projects.openmoko.org/projects/shr. We will refer to the directory to which you downloaded the project as $SHRSVN. (This directory should contain $SHRSVN/packages/openmoko-dialer3.bb)<br /> <br /> === Set up your BBPATH ===<br /> <br /> export BBPATH=.:$MOKO/openembedded/:$MOKO/<br /> <br /> <br /> === Set up the CACHE ===<br /> <br /> export CACHE=tmp/cache<br /> <br /> <br /> <br /> === Set up your local.conf ===<br /> Cd to your selected build directory.<br /> <br /> Create a directory under your current directory called 'conf'.<br /> <br /> cp $MOKO/openembedded/conf/local.conf conf/local.conf.<br /> <br /> Append the following lines to your local.conf:<br /> BBFILES+=&quot;$SHRSVN/trunk/packages/*.bb&quot;<br /> SELECTED_OPTIMIZATION = &quot;-Os -g&quot;<br /> <br /> <br /> === Add your cross-compiler to your PATH ===<br /> (I'm not sure if this stage is necessary, or even a good idea.)<br /> <br /> export PATH=$MOKO/build/tmp/staging/*/usr/bin<br /> <br /> === Run bitbake ===<br /> <br /> bitbake -b $SHRSVN/trunk/packages/openmoko-dialer3.bb<br /> <br /> <br /> [[Category:SHR]]<br /> [[Category:SHR Devel]]</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-07-18T04:54:06Z

<p>Wurp: /* How to join */</p> <hr /> <div>''This page is a placeholder to get us organized until we can get a build started.''<br /> <br /> == Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the [[Openmoko2007.2]] GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br /> <br /> (We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br /> <br /> Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br /> <br /> == Why SHR exists ==<br /> This is long and rambling, and maybe more of a tirade than information, but it does give some background on why this project was started. The overview gives, well, the overview, this is more of a deeper examination of the existing releases and why we felt we needed something new.<br /> <br /> Feel free to skip this whole section if you already think SHR is a good idea :-)<br /> <br /> === Why not ASU? ===<br /> ASU is the distro that OM is putting their main effort into right now. ASU looks very slick, but is very unstable right now, and is likely to be unstable and feature-poor for some time.<br /> <br /> === Why not 2007.2? ===<br /> 2007.2 is the &quot;old&quot; Openmoko distribution, now unsupported. Unsupported == often broken. Also, neither calls nor suspend/resume ever worked reliably.<br /> <br /> === Why not Qtopia? ===<br /> You can also install Qtopia on the phone, once TrollTech puts the images up again :-(<br /> <br /> Qtopia is stable, but it doesn't suspend &amp; resume (so the battery life is crap). And you can only build qt apps on Qtopia, which means lots of linux apps you might want to port suddenly got a lot harder to port. And some people just don't like developing for qt.<br /> <br /> Also, as far as I know, there is no documented build procedure for Qtopia on Openmoko.<br /> <br /> === Why not FSO? ===<br /> FSO is the initiative by Mickey Lauer and crew to create a good [[D-Bus]] infrastructure which runs on the neos, among other devices.<br /> <br /> FSO is by far the most stable &amp; usable release, if all you want is a phone. (I mean *all*. It just has a dialer right now, not even call history.)<br /> <br /> FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br /> <br /> Other people are supposed to put a front end on FSO. So that's what we're doing.<br /> <br /> === Why SHR? ===<br /> So SHR is FSO, with us doing the necessary work to port the old high-functionality 2007.2 stuff on a stable call platform. We have an adapter from the 2007.2 call service to the FSO call service and we're installing the basic 2007.2 apps on the FSO baseline install.<br /> <br /> In theory, it should be very simple, and should give us dialer, contact management, SMS, terminal, media player, gps app, etc. since all those already work on 2007.2. And the dialer should be stable, which it wasn't in 2007.2<br /> <br /> == First steps ==<br /> The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br /> <br /> We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br /> <br /> == Interest ==<br /> Here's a list of people who've expressed an interest in working on the SHR.<br /> <br /> * [[User:Wurp|wurp2]]<br /> * [[User:Ferric|ferric]]<br /> * [[User:Paulproteus|paulproteus]]<br /> * [[User:Ainulindale|Ainulindale]]<br /> * [[User:jluis|Jose Luis]]<br /> * [[User:Kevin_Dean|Kevin Dean]]<br /> * [[User:Cb22|cb22]]<br /> * [[User:Jeremy-list|Jeremy List]]<br /> * mwester<br /> * [[User:MarcOChapeau|MarcO'Chapeau]]<br /> * [[User:kd8ikt|kd8ikt]]<br /> <br /> == How to join ==<br /> * Please add your name (with a link to your user page) to the list above.<br /> * You should also send a request to join on the [http://projects.openmoko.org/projects/shr SHR project] on the OM projects page to join.<br /> * Join [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel shr-devel@lists.projects.openmoko.org] and send an introductory email.<br /> <br /> The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.<br /> <br /> See [[SHR Development]] to find out how to set up your development environment to work on existing SHR packages.<br /> <br /> == Tasks &amp; status ==<br /> Here's a list of the tasks for the SHR:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space; just need to talk about git branches<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |-<br /> |port 2007.2 gsm-using apps to use ophoned or ogsmd instead<br /> |Pre-Alpha<br /> |[[User:Ainulindale|Ainulindale]]<br /> |MarcOChapeau<br /> |2008-07-10<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |[[User:Kevin_Dean|Kevin Dean]]<br /> |Nobody<br /> |2008-07-05<br /> |-<br /> |[[#List_of_packages_included|Identify packages to go into SHR]]<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Anyone &amp; everyone<br /> |2008-07-12<br /> |-<br /> |Identify differences between FSO &amp; 2007.2 that need investigation<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-12<br /> |-<br /> |Switch FSO to use the 2007.2 matchbox session<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |MarcOChapeau<br /> |2008-07-12<br /> |-<br /> |Integrate [http://moko.mwester.net/fixes.html mwester's pulseaudio resume fix] into SHR<br /> |Not started<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-15<br /> |}<br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * ophoned<br /> * preferencesd<br /> * pimd<br /> * odeviced<br /> * lots more...<br /> <br /> From 2007.2:<br /> * TODO<br /> * lots more...<br /> <br /> From ASU:<br /> * TODO<br /> * lots more...<br /> <br /> == Project links ==<br /> [http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br /> <br /> == IRC conversation about how we're using revision control ==<br /> <br /> ''This is deprecated, for now we use shr-devel as our only repository. This will change after the first SHR release.''&lt;br/&gt;<br /> From 2007-07-07<br /> &lt;pre&gt;<br /> 12:36 &lt; wurp2&gt; Everything *new* goes on OM projects site<br /> 12:36 &lt; Ainulindale&gt; I totally agree<br /> 12:36 &lt; wurp2&gt; Updates to 2007.2 apps go back into the home svn<br /> 12:36 &lt; Ainulindale&gt; paulproteus: no, you're an external cabal all by yourself<br /> :-)<br /> 12:36 &lt; cb22&gt; anyone planning on drawing up a roadmap?<br /> 12:36 &lt; paulproteus&gt; cb22, We can do that in Trac in fact.<br /> 12:36 &lt; wurp2&gt; And changes to the underlying release go as patches into our OE<br /> branch, yes?<br /> 12:36 &lt; paulproteus&gt; (or on the wiki page)<br /> 12:36 &lt; paulproteus&gt; wurp2, Right<br /> 12:36 &lt; paulproteus&gt; mwester, Sanity-check my terminology where I mess things<br /> up!<br /> 12:37 &lt; Ainulindale&gt; hmmm fuzzy for me but what should go in OM and what should<br /> go in OE ?<br /> 12:37 &lt;@mwester&gt; Sure<br /> 12:37 &lt;@mwester&gt; What do you mean by OM?<br /> 12:37 &lt; paulproteus&gt; Ainulindale, New software we write goes in the<br /> projects.openmoko.org.<br /> 12:37 &lt;@mwester&gt; right.<br /> 12:37 &lt; Ainulindale&gt; Ok so the wrapper for example<br /> 12:37 &lt; wurp2&gt; Anything stand-alone goes in OM (projects.openmoko.org)<br /> 12:37 &lt; wurp2&gt; yeah<br /> 12:37 &lt;@mwester&gt; So we will use projects.openmoko.org for as much as we can,<br /> and OE to build the distro.<br /> 12:37 &lt; Ainulindale&gt; Sounds right to me<br /> 12:37 &lt; wurp2&gt; Great!<br /> 12:38 &lt;@mwester&gt; We *will not* use the OM git repo, as that is owned and<br /> controlled by Openmoko the company...<br /> &lt;/pre&gt;<br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]</div>

Wurp http://wiki.openmoko.org/wiki/SHR 2008-07-18T04:53:00Z

<p>Wurp: </p> <hr /> <div>See [[Stable Hybrid Release]].<br /> <br /> ''This page was deleted before, but it is useful both as a shorter page name to type in and to help people who don't know what the abbreviation stands for.''</div>

Wurp http://wiki.openmoko.org/wiki/SHR 2008-07-18T04:52:33Z

<p>Wurp: New page: See [Stable Hybrid Release]. (This page was deleted before, but it is useful both as a shorter page name to type in and to help people who don't know what the abbreviation stands for.)</p> <hr /> <div>See [Stable Hybrid Release].<br /> <br /> (This page was deleted before, but it is useful both as a shorter page name to type in and to help people who don't know what the abbreviation stands for.)</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-07-15T17:32:46Z

<p>Wurp: /* IRC conversation about how we're using revision control */</p> <hr /> <div>''This page is a placeholder to get us organized until we can get a build started.''<br /> <br /> == Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the [[Openmoko2007.2]] GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br /> <br /> (We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br /> <br /> Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br /> <br /> == Why SHR exists ==<br /> This is long and rambling, and maybe more of a tirade than information, but it does give some background on why this project was started. The overview gives, well, the overview, this is more of a deeper examination of the existing releases and why we felt we needed something new.<br /> <br /> Feel free to skip this whole section if you already think SHR is a good idea :-)<br /> <br /> === Why not ASU? ===<br /> ASU is the distro that OM is putting their main effort into right now. ASU looks very slick, but is very unstable right now, and is likely to be unstable and feature-poor for some time.<br /> <br /> === Why not 2007.2? ===<br /> 2007.2 is the &quot;old&quot; Openmoko distribution, now unsupported. Unsupported == often broken. Also, neither calls nor suspend/resume ever worked reliably.<br /> <br /> === Why not Qtopia? ===<br /> You can also install Qtopia on the phone, once TrollTech puts the images up again :-(<br /> <br /> Qtopia is stable, but it doesn't suspend &amp; resume (so the battery life is crap). And you can only build qt apps on Qtopia, which means lots of linux apps you might want to port suddenly got a lot harder to port. And some people just don't like developing for qt.<br /> <br /> Also, as far as I know, there is no documented build procedure for Qtopia on Openmoko.<br /> <br /> === Why not FSO? ===<br /> FSO is the initiative by Mickey Lauer and crew to create a good [[D-Bus]] infrastructure which runs on the neos, among other devices.<br /> <br /> FSO is by far the most stable &amp; usable release, if all you want is a phone. (I mean *all*. It just has a dialer right now, not even call history.)<br /> <br /> FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br /> <br /> Other people are supposed to put a front end on FSO. So that's what we're doing.<br /> <br /> === Why SHR? ===<br /> So SHR is FSO, with us doing the necessary work to port the old high-functionality 2007.2 stuff on a stable call platform. We have an adapter from the 2007.2 call service to the FSO call service and we're installing the basic 2007.2 apps on the FSO baseline install.<br /> <br /> In theory, it should be very simple, and should give us dialer, contact management, SMS, terminal, media player, gps app, etc. since all those already work on 2007.2. And the dialer should be stable, which it wasn't in 2007.2<br /> <br /> == First steps ==<br /> The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br /> <br /> We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br /> <br /> == Interest ==<br /> Here's a list of people who've expressed an interest in working on the SHR.<br /> <br /> * [[User:Wurp|wurp2]]<br /> * [[User:Ferric|ferric]]<br /> * [[User:Paulproteus|paulproteus]]<br /> * [[User:Ainulindale|Ainulindale]]<br /> * [[User:jluis|Jose Luis]]<br /> * [[User:Kevin_Dean|Kevin Dean]]<br /> * [[User:Cb22|cb22]]<br /> * [[User:Jeremy-list|Jeremy List]]<br /> * mwester<br /> * [[User:MarcOChapeau|MarcO'Chapeau]]<br /> * [[User:kd8ikt|kd8ikt]]<br /> <br /> == How to join ==<br /> * Please add your name (with a link to your user page) to the list above.<br /> * You should also send a request to join on the [http://projects.openmoko.org/projects/shr SHR project] on the OM projects page to join.<br /> * Join [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel shr-devel@lists.projects.openmoko.org] and send an introductory email.<br /> <br /> The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.<br /> <br /> == Tasks &amp; status ==<br /> Here's a list of the tasks for the SHR:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space; just need to talk about git branches<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |-<br /> |port 2007.2 gsm-using apps to use ophoned or ogsmd instead<br /> |Pre-Alpha<br /> |[[User:Ainulindale|Ainulindale]]<br /> |MarcOChapeau<br /> |2008-07-10<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |[[User:Kevin_Dean|Kevin Dean]]<br /> |Nobody<br /> |2008-07-05<br /> |-<br /> |[[#List_of_packages_included|Identify packages to go into SHR]]<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Anyone &amp; everyone<br /> |2008-07-12<br /> |-<br /> |Identify differences between FSO &amp; 2007.2 that need investigation<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-12<br /> |-<br /> |Switch FSO to use the 2007.2 matchbox session<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |MarcOChapeau<br /> |2008-07-12<br /> |-<br /> |Integrate [http://moko.mwester.net/fixes.html mwester's pulseaudio resume fix] into SHR<br /> |Not started<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-15<br /> |}<br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * ophoned<br /> * preferencesd<br /> * pimd<br /> * odeviced<br /> * lots more...<br /> <br /> From 2007.2:<br /> * TODO<br /> * lots more...<br /> <br /> From ASU:<br /> * TODO<br /> * lots more...<br /> <br /> == Project links ==<br /> [http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br /> <br /> == IRC conversation about how we're using revision control ==<br /> <br /> ''This is deprecated, for now we use shr-devel as our only repository. This will change after the first SHR release.''&lt;br/&gt;<br /> From 2007-07-07<br /> &lt;pre&gt;<br /> 12:36 &lt; wurp2&gt; Everything *new* goes on OM projects site<br /> 12:36 &lt; Ainulindale&gt; I totally agree<br /> 12:36 &lt; wurp2&gt; Updates to 2007.2 apps go back into the home svn<br /> 12:36 &lt; Ainulindale&gt; paulproteus: no, you're an external cabal all by yourself<br /> :-)<br /> 12:36 &lt; cb22&gt; anyone planning on drawing up a roadmap?<br /> 12:36 &lt; paulproteus&gt; cb22, We can do that in Trac in fact.<br /> 12:36 &lt; wurp2&gt; And changes to the underlying release go as patches into our OE<br /> branch, yes?<br /> 12:36 &lt; paulproteus&gt; (or on the wiki page)<br /> 12:36 &lt; paulproteus&gt; wurp2, Right<br /> 12:36 &lt; paulproteus&gt; mwester, Sanity-check my terminology where I mess things<br /> up!<br /> 12:37 &lt; Ainulindale&gt; hmmm fuzzy for me but what should go in OM and what should<br /> go in OE ?<br /> 12:37 &lt;@mwester&gt; Sure<br /> 12:37 &lt;@mwester&gt; What do you mean by OM?<br /> 12:37 &lt; paulproteus&gt; Ainulindale, New software we write goes in the<br /> projects.openmoko.org.<br /> 12:37 &lt;@mwester&gt; right.<br /> 12:37 &lt; Ainulindale&gt; Ok so the wrapper for example<br /> 12:37 &lt; wurp2&gt; Anything stand-alone goes in OM (projects.openmoko.org)<br /> 12:37 &lt; wurp2&gt; yeah<br /> 12:37 &lt;@mwester&gt; So we will use projects.openmoko.org for as much as we can,<br /> and OE to build the distro.<br /> 12:37 &lt; Ainulindale&gt; Sounds right to me<br /> 12:37 &lt; wurp2&gt; Great!<br /> 12:38 &lt;@mwester&gt; We *will not* use the OM git repo, as that is owned and<br /> controlled by Openmoko the company...<br /> &lt;/pre&gt;<br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-07-15T16:41:52Z

<p>Wurp: /* Tasks &amp; status */</p> <hr /> <div>''This page is a placeholder to get us organized until we can get a build started.''<br /> <br /> == Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the [[Openmoko2007.2]] GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br /> <br /> (We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br /> <br /> Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br /> <br /> == Why SHR exists ==<br /> This is long and rambling, and maybe more of a tirade than information, but it does give some background on why this project was started. The overview gives, well, the overview, this is more of a deeper examination of the existing releases and why we felt we needed something new.<br /> <br /> Feel free to skip this whole section if you already think SHR is a good idea :-)<br /> <br /> === Why not ASU? ===<br /> ASU is the distro that OM is putting their main effort into right now. ASU looks very slick, but is very unstable right now, and is likely to be unstable and feature-poor for some time.<br /> <br /> === Why not 2007.2? ===<br /> 2007.2 is the &quot;old&quot; Openmoko distribution, now unsupported. Unsupported == often broken. Also, neither calls nor suspend/resume ever worked reliably.<br /> <br /> === Why not Qtopia? ===<br /> You can also install Qtopia on the phone, once TrollTech puts the images up again :-(<br /> <br /> Qtopia is stable, but it doesn't suspend &amp; resume (so the battery life is crap). And you can only build qt apps on Qtopia, which means lots of linux apps you might want to port suddenly got a lot harder to port. And some people just don't like developing for qt.<br /> <br /> Also, as far as I know, there is no documented build procedure for Qtopia on Openmoko.<br /> <br /> === Why not FSO? ===<br /> FSO is the initiative by Mickey Lauer and crew to create a good [[D-Bus]] infrastructure which runs on the neos, among other devices.<br /> <br /> FSO is by far the most stable &amp; usable release, if all you want is a phone. (I mean *all*. It just has a dialer right now, not even call history.)<br /> <br /> FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br /> <br /> Other people are supposed to put a front end on FSO. So that's what we're doing.<br /> <br /> === Why SHR? ===<br /> So SHR is FSO, with us doing the necessary work to port the old high-functionality 2007.2 stuff on a stable call platform. We have an adapter from the 2007.2 call service to the FSO call service and we're installing the basic 2007.2 apps on the FSO baseline install.<br /> <br /> In theory, it should be very simple, and should give us dialer, contact management, SMS, terminal, media player, gps app, etc. since all those already work on 2007.2. And the dialer should be stable, which it wasn't in 2007.2<br /> <br /> == First steps ==<br /> The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br /> <br /> We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br /> <br /> == Interest ==<br /> Here's a list of people who've expressed an interest in working on the SHR.<br /> <br /> * [[User:Wurp|wurp2]]<br /> * [[User:Ferric|ferric]]<br /> * [[User:Paulproteus|paulproteus]]<br /> * [[User:Ainulindale|Ainulindale]]<br /> * [[User:jluis|Jose Luis]]<br /> * [[User:Kevin_Dean|Kevin Dean]]<br /> * [[User:Cb22|cb22]]<br /> * [[User:Jeremy-list|Jeremy List]]<br /> * mwester<br /> * [[User:MarcOChapeau|MarcO'Chapeau]]<br /> * [[User:kd8ikt|kd8ikt]]<br /> <br /> == How to join ==<br /> * Please add your name (with a link to your user page) to the list above.<br /> * You should also send a request to join on the [http://projects.openmoko.org/projects/shr SHR project] on the OM projects page to join.<br /> * Join [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel shr-devel@lists.projects.openmoko.org] and send an introductory email.<br /> <br /> The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.<br /> <br /> == Tasks &amp; status ==<br /> Here's a list of the tasks for the SHR:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space; just need to talk about git branches<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |-<br /> |port 2007.2 gsm-using apps to use ophoned or ogsmd instead<br /> |Pre-Alpha<br /> |[[User:Ainulindale|Ainulindale]]<br /> |MarcOChapeau<br /> |2008-07-10<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |[[User:Kevin_Dean|Kevin Dean]]<br /> |Nobody<br /> |2008-07-05<br /> |-<br /> |[[#List_of_packages_included|Identify packages to go into SHR]]<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Anyone &amp; everyone<br /> |2008-07-12<br /> |-<br /> |Identify differences between FSO &amp; 2007.2 that need investigation<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-12<br /> |-<br /> |Switch FSO to use the 2007.2 matchbox session<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |MarcOChapeau<br /> |2008-07-12<br /> |-<br /> |Integrate [http://moko.mwester.net/fixes.html mwester's pulseaudio resume fix] into SHR<br /> |Not started<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-15<br /> |}<br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * ophoned<br /> * preferencesd<br /> * pimd<br /> * odeviced<br /> * lots more...<br /> <br /> From 2007.2:<br /> * TODO<br /> * lots more...<br /> <br /> From ASU:<br /> * TODO<br /> * lots more...<br /> <br /> == Project links ==<br /> [http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br /> <br /> == IRC conversation about how we're using revision control ==<br /> From 2007-07-07<br /> &lt;pre&gt;<br /> 12:36 &lt; wurp2&gt; Everything *new* goes on OM projects site<br /> 12:36 &lt; Ainulindale&gt; I totally agree<br /> 12:36 &lt; wurp2&gt; Updates to 2007.2 apps go back into the home svn<br /> 12:36 &lt; Ainulindale&gt; paulproteus: no, you're an external cabal all by yourself<br /> :-)<br /> 12:36 &lt; cb22&gt; anyone planning on drawing up a roadmap?<br /> 12:36 &lt; paulproteus&gt; cb22, We can do that in Trac in fact.<br /> 12:36 &lt; wurp2&gt; And changes to the underlying release go as patches into our OE<br /> branch, yes?<br /> 12:36 &lt; paulproteus&gt; (or on the wiki page)<br /> 12:36 &lt; paulproteus&gt; wurp2, Right<br /> 12:36 &lt; paulproteus&gt; mwester, Sanity-check my terminology where I mess things<br /> up!<br /> 12:37 &lt; Ainulindale&gt; hmmm fuzzy for me but what should go in OM and what should<br /> go in OE ?<br /> 12:37 &lt;@mwester&gt; Sure<br /> 12:37 &lt;@mwester&gt; What do you mean by OM?<br /> 12:37 &lt; paulproteus&gt; Ainulindale, New software we write goes in the<br /> projects.openmoko.org.<br /> 12:37 &lt;@mwester&gt; right.<br /> 12:37 &lt; Ainulindale&gt; Ok so the wrapper for example<br /> 12:37 &lt; wurp2&gt; Anything stand-alone goes in OM (projects.openmoko.org)<br /> 12:37 &lt; wurp2&gt; yeah<br /> 12:37 &lt;@mwester&gt; So we will use projects.openmoko.org for as much as we can,<br /> and OE to build the distro.<br /> 12:37 &lt; Ainulindale&gt; Sounds right to me<br /> 12:37 &lt; wurp2&gt; Great!<br /> 12:38 &lt;@mwester&gt; We *will not* use the OM git repo, as that is owned and<br /> controlled by Openmoko the company...<br /> &lt;/pre&gt;<br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-07-15T16:40:40Z

<p>Wurp: /* Tasks &amp; status */</p> <hr /> <div>''This page is a placeholder to get us organized until we can get a build started.''<br /> <br /> == Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the [[Openmoko2007.2]] GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br /> <br /> (We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br /> <br /> Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br /> <br /> == Why SHR exists ==<br /> This is long and rambling, and maybe more of a tirade than information, but it does give some background on why this project was started. The overview gives, well, the overview, this is more of a deeper examination of the existing releases and why we felt we needed something new.<br /> <br /> Feel free to skip this whole section if you already think SHR is a good idea :-)<br /> <br /> === Why not ASU? ===<br /> ASU is the distro that OM is putting their main effort into right now. ASU looks very slick, but is very unstable right now, and is likely to be unstable and feature-poor for some time.<br /> <br /> === Why not 2007.2? ===<br /> 2007.2 is the &quot;old&quot; Openmoko distribution, now unsupported. Unsupported == often broken. Also, neither calls nor suspend/resume ever worked reliably.<br /> <br /> === Why not Qtopia? ===<br /> You can also install Qtopia on the phone, once TrollTech puts the images up again :-(<br /> <br /> Qtopia is stable, but it doesn't suspend &amp; resume (so the battery life is crap). And you can only build qt apps on Qtopia, which means lots of linux apps you might want to port suddenly got a lot harder to port. And some people just don't like developing for qt.<br /> <br /> Also, as far as I know, there is no documented build procedure for Qtopia on Openmoko.<br /> <br /> === Why not FSO? ===<br /> FSO is the initiative by Mickey Lauer and crew to create a good [[D-Bus]] infrastructure which runs on the neos, among other devices.<br /> <br /> FSO is by far the most stable &amp; usable release, if all you want is a phone. (I mean *all*. It just has a dialer right now, not even call history.)<br /> <br /> FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br /> <br /> Other people are supposed to put a front end on FSO. So that's what we're doing.<br /> <br /> === Why SHR? ===<br /> So SHR is FSO, with us doing the necessary work to port the old high-functionality 2007.2 stuff on a stable call platform. We have an adapter from the 2007.2 call service to the FSO call service and we're installing the basic 2007.2 apps on the FSO baseline install.<br /> <br /> In theory, it should be very simple, and should give us dialer, contact management, SMS, terminal, media player, gps app, etc. since all those already work on 2007.2. And the dialer should be stable, which it wasn't in 2007.2<br /> <br /> == First steps ==<br /> The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br /> <br /> We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br /> <br /> == Interest ==<br /> Here's a list of people who've expressed an interest in working on the SHR.<br /> <br /> * [[User:Wurp|wurp2]]<br /> * [[User:Ferric|ferric]]<br /> * [[User:Paulproteus|paulproteus]]<br /> * [[User:Ainulindale|Ainulindale]]<br /> * [[User:jluis|Jose Luis]]<br /> * [[User:Kevin_Dean|Kevin Dean]]<br /> * [[User:Cb22|cb22]]<br /> * [[User:Jeremy-list|Jeremy List]]<br /> * mwester<br /> * [[User:MarcOChapeau|MarcO'Chapeau]]<br /> * [[User:kd8ikt|kd8ikt]]<br /> <br /> == How to join ==<br /> * Please add your name (with a link to your user page) to the list above.<br /> * You should also send a request to join on the [http://projects.openmoko.org/projects/shr SHR project] on the OM projects page to join.<br /> * Join [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel shr-devel@lists.projects.openmoko.org] and send an introductory email.<br /> <br /> The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.<br /> <br /> == Tasks &amp; status ==<br /> Here's a list of the tasks for the SHR:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space; just need to talk about git branches<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |-<br /> |phonekit to ophoned adapter<br /> |Pre-Alpha<br /> |[[User:Ainulindale|Ainulindale]]<br /> |[[User:Ferric|ferric]], [[User:Wurp|Wurp]]<br /> |2008-07-10<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |[[User:Kevin_Dean|Kevin Dean]]<br /> |Nobody<br /> |2008-07-05<br /> |-<br /> |[[#List_of_packages_included|Identify packages to go into SHR]]<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Anyone &amp; everyone<br /> |2008-07-12<br /> |-<br /> |Identify differences between FSO &amp; 2007.2 that need investigation<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-12<br /> |-<br /> |Switch FSO to use the 2007.2 matchbox session<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-12<br /> |-<br /> |Integrate [http://moko.mwester.net/fixes.html mwester's pulseaudio resume fix] into SHR<br /> |Not started<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-15<br /> |}<br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * ophoned<br /> * preferencesd<br /> * pimd<br /> * odeviced<br /> * lots more...<br /> <br /> From 2007.2:<br /> * TODO<br /> * lots more...<br /> <br /> From ASU:<br /> * TODO<br /> * lots more...<br /> <br /> == Project links ==<br /> [http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br /> <br /> == IRC conversation about how we're using revision control ==<br /> From 2007-07-07<br /> &lt;pre&gt;<br /> 12:36 &lt; wurp2&gt; Everything *new* goes on OM projects site<br /> 12:36 &lt; Ainulindale&gt; I totally agree<br /> 12:36 &lt; wurp2&gt; Updates to 2007.2 apps go back into the home svn<br /> 12:36 &lt; Ainulindale&gt; paulproteus: no, you're an external cabal all by yourself<br /> :-)<br /> 12:36 &lt; cb22&gt; anyone planning on drawing up a roadmap?<br /> 12:36 &lt; paulproteus&gt; cb22, We can do that in Trac in fact.<br /> 12:36 &lt; wurp2&gt; And changes to the underlying release go as patches into our OE<br /> branch, yes?<br /> 12:36 &lt; paulproteus&gt; (or on the wiki page)<br /> 12:36 &lt; paulproteus&gt; wurp2, Right<br /> 12:36 &lt; paulproteus&gt; mwester, Sanity-check my terminology where I mess things<br /> up!<br /> 12:37 &lt; Ainulindale&gt; hmmm fuzzy for me but what should go in OM and what should<br /> go in OE ?<br /> 12:37 &lt;@mwester&gt; Sure<br /> 12:37 &lt;@mwester&gt; What do you mean by OM?<br /> 12:37 &lt; paulproteus&gt; Ainulindale, New software we write goes in the<br /> projects.openmoko.org.<br /> 12:37 &lt;@mwester&gt; right.<br /> 12:37 &lt; Ainulindale&gt; Ok so the wrapper for example<br /> 12:37 &lt; wurp2&gt; Anything stand-alone goes in OM (projects.openmoko.org)<br /> 12:37 &lt; wurp2&gt; yeah<br /> 12:37 &lt;@mwester&gt; So we will use projects.openmoko.org for as much as we can,<br /> and OE to build the distro.<br /> 12:37 &lt; Ainulindale&gt; Sounds right to me<br /> 12:37 &lt; wurp2&gt; Great!<br /> 12:38 &lt;@mwester&gt; We *will not* use the OM git repo, as that is owned and<br /> controlled by Openmoko the company...<br /> &lt;/pre&gt;<br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]</div>

Wurp http://wiki.openmoko.org/wiki/GTA02_FAQ 2008-07-14T18:33:10Z

<p>Wurp: </p> <hr /> <div>See [[Neo FreeRunner (GTA02) FAQ]]</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-07-12T20:46:15Z

<p>Wurp: /* Tasks &amp; status */</p> <hr /> <div>''This page is a placeholder to get us organized until we can get a build started.''<br /> <br /> == Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the 2007.2 GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br /> <br /> (We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br /> <br /> Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br /> <br /> == Why SHR exists ==<br /> This is long and rambling, and maybe more of a tirade than information, but it does give some background on why this project was started. The overview gives, well, the overview, this is more of a deeper examination of the existing releases and why we felt we needed something new.<br /> <br /> Feel free to skip this whole section if you already think SHR is a good idea :-)<br /> <br /> === Why not ASU? ===<br /> ASU is the distro that OM is putting their main effort into right now. ASU looks very slick, but is very unstable right now, and is likely to be unstable and feature-poor for some time.<br /> <br /> === Why not 2007.2? ===<br /> 2007.2 is the &quot;old&quot; Openmoko distribution, now unsupported. Unsupported == often broken. Also, neither calls nor suspend/resume ever worked reliably.<br /> <br /> === Why not Qtopia? ===<br /> You can also install Qtopia on the phone, once TrollTech puts the images up again :-(<br /> <br /> Qtopia is stable, but it doesn't suspend &amp; resume (so the battery life is crap). And you can only build qt apps on Qtopia, which means lots of linux apps you might want to port suddenly got a lot harder to port. And some people just don't like developing for qt.<br /> <br /> Also, as far as I know, there is no documented build procedure for Qtopia on Openmoko.<br /> <br /> === Why not FSO? ===<br /> FSO is the initiative by Mickey Laurer and crew to create a good dbus infrastructure which runs on the neos, among other devices.<br /> <br /> FSO is by far the most stable &amp; usable release, if all you want is a phone. (I mean *all*. It just has a dialer right now, not even call history.)<br /> <br /> FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br /> <br /> Other people are supposed to put a front end on FSO. So that's what we're doing.<br /> <br /> === Why SHR? ===<br /> So SHR is FSO, with us doing the necessary work to port the old high-functionality 2007.2 stuff on a stable call platform. We have an adapter from the 2007.2 call service to the FSO call service and we're installing the basic 2007.2 apps on the FSO baseline install.<br /> <br /> In theory, it should be very simple, and should give us dialer, contact management, SMS, terminal, media player, gps app, etc. since all those already work on 2007.2. And the dialer should be stable, which it wasn't in 2007.2<br /> <br /> == First steps ==<br /> The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br /> <br /> We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br /> <br /> == Interest ==<br /> Here's a list of people who've expressed an interest in working on the SHR.<br /> <br /> * [[User:Wurp|wurp2]]<br /> * [[User:Ferric|ferric]]<br /> * [[User:Paulproteus|paulproteus]]<br /> * [[User:Ainulindale|Ainulindale]]<br /> * [[User:jluis|Jose Luis]]<br /> * [[User:Kevin_Dean|Kevin Dean]]<br /> * [[User:Cb22|cb22]]<br /> * [[User:Jeremy-list|Jeremy List]]<br /> * mwester<br /> * [[User:MarcOChapeau|MarcO'Chapeau]]<br /> * [[User:kd8ikt|kd8ikt]]<br /> <br /> == How to join ==<br /> * Please add your name (with a link to your user page) to the list above.<br /> * You should also send a request to join on the [http://projects.openmoko.org/projects/shr SHR project] on the OM projects page to join.<br /> * Join [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel shr-devel@lists.projects.openmoko.org] and send an introductory email.<br /> <br /> The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.<br /> <br /> == Tasks &amp; status ==<br /> Here's a list of the tasks for the SHR:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space; just need to talk about git branches<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |-<br /> |phonekit to ophoned adapter<br /> |Pre-Alpha<br /> |[[User:Ainulindale|Ainulindale]]<br /> |[[User:Ferric|ferric]], [[User:Wurp|Wurp]]<br /> |2008-07-10<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |[[User:Kevin_Dean|Kevin Dean]]<br /> |Nobody<br /> |2008-07-05<br /> |-<br /> |[[#List_of_packages_included|Identify packages to go into SHR]]<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Anyone &amp; everyone<br /> |2008-07-12<br /> |-<br /> |Identify differences between FSO &amp; 2007.2 that need investigation<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-12<br /> |-<br /> |Switch FSO to use the 2007.2 matchbox session<br /> |Pre-alpha<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-12<br /> |}<br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * ophoned<br /> * preferencesd<br /> * pimd<br /> * odeviced<br /> * lots more...<br /> <br /> From 2007.2:<br /> * TODO<br /> * lots more...<br /> <br /> From ASU:<br /> * TODO<br /> * lots more...<br /> <br /> == Project links ==<br /> [http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br /> <br /> == IRC conversation about how we're using revision control ==<br /> From 2007-07-07<br /> &lt;pre&gt;<br /> 12:36 &lt; wurp2&gt; Everything *new* goes on OM projects site<br /> 12:36 &lt; Ainulindale&gt; I totally agree<br /> 12:36 &lt; wurp2&gt; Updates to 2007.2 apps go back into the home svn<br /> 12:36 &lt; Ainulindale&gt; paulproteus: no, you're an external cabal all by yourself<br /> :-)<br /> 12:36 &lt; cb22&gt; anyone planning on drawing up a roadmap?<br /> 12:36 &lt; paulproteus&gt; cb22, We can do that in Trac in fact.<br /> 12:36 &lt; wurp2&gt; And changes to the underlying release go as patches into our OE<br /> branch, yes?<br /> 12:36 &lt; paulproteus&gt; (or on the wiki page)<br /> 12:36 &lt; paulproteus&gt; wurp2, Right<br /> 12:36 &lt; paulproteus&gt; mwester, Sanity-check my terminology where I mess things<br /> up!<br /> 12:37 &lt; Ainulindale&gt; hmmm fuzzy for me but what should go in OM and what should<br /> go in OE ?<br /> 12:37 &lt;@mwester&gt; Sure<br /> 12:37 &lt;@mwester&gt; What do you mean by OM?<br /> 12:37 &lt; paulproteus&gt; Ainulindale, New software we write goes in the<br /> projects.openmoko.org.<br /> 12:37 &lt;@mwester&gt; right.<br /> 12:37 &lt; Ainulindale&gt; Ok so the wrapper for example<br /> 12:37 &lt; wurp2&gt; Anything stand-alone goes in OM (projects.openmoko.org)<br /> 12:37 &lt; wurp2&gt; yeah<br /> 12:37 &lt;@mwester&gt; So we will use projects.openmoko.org for as much as we can,<br /> and OE to build the distro.<br /> 12:37 &lt; Ainulindale&gt; Sounds right to me<br /> 12:37 &lt; wurp2&gt; Great!<br /> 12:38 &lt;@mwester&gt; We *will not* use the OM git repo, as that is owned and<br /> controlled by Openmoko the company...<br /> &lt;/pre&gt;<br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-07-10T22:59:31Z

<p>Wurp: /* Why SHR exists */</p> <hr /> <div>''This page is a placeholder to get us organized until we can get a build started.''<br /> <br /> == Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the 2007.2 GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br /> <br /> (We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br /> <br /> Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br /> <br /> == Why SHR exists ==<br /> This is long and rambling, and maybe more of a tirade than information, but it does give some background on why this project was started. The overview gives, well, the overview, this is more of a deeper examination of the existing releases and why we felt we needed something new.<br /> <br /> Feel free to skip this whole section if you already think SHR is a good idea :-)<br /> <br /> === Why not ASU? ===<br /> ASU is the distro that OM is putting their main effort into right now. ASU looks very slick, but is very unstable right now, and is likely to be unstable and feature-poor for some time.<br /> <br /> === Why not 2007.2? ===<br /> 2007.2 is the &quot;old&quot; Openmoko distribution, now unsupported. Unsupported == often broken. Also, neither calls nor suspend/resume ever worked reliably.<br /> <br /> === Why not Qtopia? ===<br /> You can also install Qtopia on the phone, once TrollTech puts the images up again :-(<br /> <br /> Qtopia is stable, but it doesn't suspend &amp; resume (so the battery life is crap). And you can only build qt apps on Qtopia, which means lots of linux apps you might want to port suddenly got a lot harder to port. And some people just don't like developing for qt.<br /> <br /> Also, as far as I know, there is no documented build procedure for Qtopia on Openmoko.<br /> <br /> === Why not FSO? ===<br /> FSO is the initiative by Mickey Laurer and crew to create a good dbus infrastructure which runs on the neos, among other devices.<br /> <br /> FSO is by far the most stable &amp; usable release, if all you want is a phone. (I mean *all*. It just has a dialer right now, not even call history.)<br /> <br /> FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br /> <br /> Other people are supposed to put a front end on FSO. So that's what we're doing.<br /> <br /> === Why SHR? ===<br /> So SHR is FSO, with us doing the necessary work to port the old high-functionality 2007.2 stuff on a stable call platform. We have an adapter from the 2007.2 call service to the FSO call service and we're installing the basic 2007.2 apps on the FSO baseline install.<br /> <br /> In theory, it should be very simple, and should give us dialer, contact management, SMS, terminal, media player, gps app, etc. since all those already work on 2007.2. And the dialer should be stable, which it wasn't in 2007.2<br /> <br /> == First steps ==<br /> The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br /> <br /> We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br /> <br /> == Interest ==<br /> Here's a list of people who've expressed an interest in working on the SHR.<br /> <br /> * [[User:Wurp|wurp2]]<br /> * [[User:Ferric|ferric]]<br /> * [[User:Paulproteus|paulproteus]]<br /> * [[User:Ainulindale|Ainulindale]]<br /> * [[User:jluis|Jose Luis]]<br /> * [[User:Kevin_Dean|Kevin Dean]]<br /> * [[User:Cb22|cb22]]<br /> * [[User:Jeremy-list|Jeremy List]]<br /> * mwester<br /> <br /> == How to join ==<br /> * Please add your name (with a link to your user page) to the list above.<br /> * You should also send a request to join on the [http://projects.openmoko.org/projects/shr SHR project] on the OM projects page to join.<br /> * Join [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel shr-devel@lists.projects.openmoko.org] and send an introductory email.<br /> <br /> The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.<br /> <br /> == Tasks &amp; status ==<br /> Here's a list of the tasks for the SHR:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space; just need to talk about git branches<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |-<br /> |phonekit to ophoned adapter<br /> |Pre-Alpha<br /> |[[User:Ainulindale|Ainulindale]]<br /> |[[User:Ferric|ferric]], [[User:Wurp|Wurp]]<br /> |2008-07-10<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |[[User:Kevin_Dean|Kevin Dean]]<br /> |Nobody<br /> |2008-07-05<br /> |-<br /> |[[#List_of_packages_included|Identify packages to go into SHR]]<br /> |Started<br /> |[[User:Wurp|Wurp]]<br /> |Anyone &amp; everyone<br /> |2008-07-10<br /> |-<br /> |Identify differences between FSO &amp; 2007.2 that need investigation<br /> |Started<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-08<br /> |-<br /> |Switch FSO to use the matchbox window manager (as does 2007.2)<br /> |Started<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-08<br /> |}<br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * ophoned<br /> * preferencesd<br /> * pimd<br /> * odeviced<br /> * lots more...<br /> <br /> From 2007.2:<br /> * TODO<br /> * lots more...<br /> <br /> From ASU:<br /> * TODO<br /> * lots more...<br /> <br /> == Project links ==<br /> [http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br /> <br /> == IRC conversation about how we're using revision control ==<br /> From 2007-07-07<br /> &lt;pre&gt;<br /> 12:36 &lt; wurp2&gt; Everything *new* goes on OM projects site<br /> 12:36 &lt; Ainulindale&gt; I totally agree<br /> 12:36 &lt; wurp2&gt; Updates to 2007.2 apps go back into the home svn<br /> 12:36 &lt; Ainulindale&gt; paulproteus: no, you're an external cabal all by yourself<br /> :-)<br /> 12:36 &lt; cb22&gt; anyone planning on drawing up a roadmap?<br /> 12:36 &lt; paulproteus&gt; cb22, We can do that in Trac in fact.<br /> 12:36 &lt; wurp2&gt; And changes to the underlying release go as patches into our OE<br /> branch, yes?<br /> 12:36 &lt; paulproteus&gt; (or on the wiki page)<br /> 12:36 &lt; paulproteus&gt; wurp2, Right<br /> 12:36 &lt; paulproteus&gt; mwester, Sanity-check my terminology where I mess things<br /> up!<br /> 12:37 &lt; Ainulindale&gt; hmmm fuzzy for me but what should go in OM and what should<br /> go in OE ?<br /> 12:37 &lt;@mwester&gt; Sure<br /> 12:37 &lt;@mwester&gt; What do you mean by OM?<br /> 12:37 &lt; paulproteus&gt; Ainulindale, New software we write goes in the<br /> projects.openmoko.org.<br /> 12:37 &lt;@mwester&gt; right.<br /> 12:37 &lt; Ainulindale&gt; Ok so the wrapper for example<br /> 12:37 &lt; wurp2&gt; Anything stand-alone goes in OM (projects.openmoko.org)<br /> 12:37 &lt; wurp2&gt; yeah<br /> 12:37 &lt;@mwester&gt; So we will use projects.openmoko.org for as much as we can,<br /> and OE to build the distro.<br /> 12:37 &lt; Ainulindale&gt; Sounds right to me<br /> 12:37 &lt; wurp2&gt; Great!<br /> 12:38 &lt;@mwester&gt; We *will not* use the OM git repo, as that is owned and<br /> controlled by Openmoko the company...<br /> &lt;/pre&gt;<br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-07-10T22:55:41Z

<p>Wurp: </p> <hr /> <div>''This page is a placeholder to get us organized until we can get a build started.''<br /> <br /> == Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the 2007.2 GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br /> <br /> (We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br /> <br /> Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br /> <br /> == Why SHR exists ==<br /> This is long and rambling, and maybe more of a tirade than information, but it does give some background on why this project was started. The overview gives, well, the overview, this is more of a deeper examination of the existing releases and why we felt we needed something new.<br /> <br /> === Why not ASU? ===<br /> ASU is the distro that OM is putting their main effort into right now. ASU looks very slick, but is very unstable right now, and is likely to be unstable and feature-poor for some time.<br /> <br /> === Why not 2007.2? ===<br /> 2007.2 is the &quot;old&quot; Openmoko distribution, now unsupported. Unsupported == often broken. Also, neither calls nor suspend/resume ever worked reliably.<br /> <br /> === Why not Qtopia? ===<br /> You can also install Qtopia on the phone, once TrollTech puts the images up again :-(<br /> <br /> Qtopia is stable, but it doesn't suspend &amp; resume (so the battery life is crap). And you can only build qt apps on Qtopia, which means lots of linux apps you might want to port suddenly got a lot harder to port. And some people just don't like developing for qt.<br /> <br /> Also, as far as I know, there is no documented build procedure for Qtopia on Openmoko.<br /> <br /> === Why not FSO? ===<br /> FSO is the initiative by Mickey Laurer and crew to create a good dbus infrastructure which runs on the neos, among other devices.<br /> <br /> FSO is by far the most stable &amp; usable release, if all you want is a phone. (I mean *all*. It just has a dialer right now, not even call history.)<br /> <br /> FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br /> <br /> Other people are supposed to put a front end on FSO. So that's what we're doing.<br /> <br /> === Why SHR? ===<br /> So SHR is FSO, with us doing the necessary work to port the old high-functionality 2007.2 stuff on a stable call platform. We have an adapter from the 2007.2 call service to the FSO call service and we're installing the basic 2007.2 apps on the FSO baseline install.<br /> <br /> In theory, it should be very simple, and should give us dialer, contact management, SMS, terminal, media player, gps app, etc. since all those already work on 2007.2. And the dialer should be stable, which it wasn't in 2007.2<br /> <br /> <br /> == First steps ==<br /> The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br /> <br /> We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br /> <br /> == Interest ==<br /> Here's a list of people who've expressed an interest in working on the SHR.<br /> <br /> * [[User:Wurp|wurp2]]<br /> * [[User:Ferric|ferric]]<br /> * [[User:Paulproteus|paulproteus]]<br /> * [[User:Ainulindale|Ainulindale]]<br /> * [[User:jluis|Jose Luis]]<br /> * [[User:Kevin_Dean|Kevin Dean]]<br /> * [[User:Cb22|cb22]]<br /> * [[User:Jeremy-list|Jeremy List]]<br /> * mwester<br /> <br /> == How to join ==<br /> * Please add your name (with a link to your user page) to the list above.<br /> * You should also send a request to join on the [http://projects.openmoko.org/projects/shr SHR project] on the OM projects page to join.<br /> * Join [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel shr-devel@lists.projects.openmoko.org] and send an introductory email.<br /> <br /> The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.<br /> <br /> == Tasks &amp; status ==<br /> Here's a list of the tasks for the SHR:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space; just need to talk about git branches<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |-<br /> |phonekit to ophoned adapter<br /> |Pre-Alpha<br /> |[[User:Ainulindale|Ainulindale]]<br /> |[[User:Ferric|ferric]], [[User:Wurp|Wurp]]<br /> |2008-07-10<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |[[User:Kevin_Dean|Kevin Dean]]<br /> |Nobody<br /> |2008-07-05<br /> |-<br /> |[[#List_of_packages_included|Identify packages to go into SHR]]<br /> |Started<br /> |[[User:Wurp|Wurp]]<br /> |Anyone &amp; everyone<br /> |2008-07-10<br /> |-<br /> |Identify differences between FSO &amp; 2007.2 that need investigation<br /> |Started<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-08<br /> |-<br /> |Switch FSO to use the matchbox window manager (as does 2007.2)<br /> |Started<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-08<br /> |}<br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * ophoned<br /> * preferencesd<br /> * pimd<br /> * odeviced<br /> * lots more...<br /> <br /> From 2007.2:<br /> * TODO<br /> * lots more...<br /> <br /> From ASU:<br /> * TODO<br /> * lots more...<br /> <br /> == Project links ==<br /> [http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br /> <br /> == IRC conversation about how we're using revision control ==<br /> From 2007-07-07<br /> &lt;pre&gt;<br /> 12:36 &lt; wurp2&gt; Everything *new* goes on OM projects site<br /> 12:36 &lt; Ainulindale&gt; I totally agree<br /> 12:36 &lt; wurp2&gt; Updates to 2007.2 apps go back into the home svn<br /> 12:36 &lt; Ainulindale&gt; paulproteus: no, you're an external cabal all by yourself<br /> :-)<br /> 12:36 &lt; cb22&gt; anyone planning on drawing up a roadmap?<br /> 12:36 &lt; paulproteus&gt; cb22, We can do that in Trac in fact.<br /> 12:36 &lt; wurp2&gt; And changes to the underlying release go as patches into our OE<br /> branch, yes?<br /> 12:36 &lt; paulproteus&gt; (or on the wiki page)<br /> 12:36 &lt; paulproteus&gt; wurp2, Right<br /> 12:36 &lt; paulproteus&gt; mwester, Sanity-check my terminology where I mess things<br /> up!<br /> 12:37 &lt; Ainulindale&gt; hmmm fuzzy for me but what should go in OM and what should<br /> go in OE ?<br /> 12:37 &lt;@mwester&gt; Sure<br /> 12:37 &lt;@mwester&gt; What do you mean by OM?<br /> 12:37 &lt; paulproteus&gt; Ainulindale, New software we write goes in the<br /> projects.openmoko.org.<br /> 12:37 &lt;@mwester&gt; right.<br /> 12:37 &lt; Ainulindale&gt; Ok so the wrapper for example<br /> 12:37 &lt; wurp2&gt; Anything stand-alone goes in OM (projects.openmoko.org)<br /> 12:37 &lt; wurp2&gt; yeah<br /> 12:37 &lt;@mwester&gt; So we will use projects.openmoko.org for as much as we can,<br /> and OE to build the distro.<br /> 12:37 &lt; Ainulindale&gt; Sounds right to me<br /> 12:37 &lt; wurp2&gt; Great!<br /> 12:38 &lt;@mwester&gt; We *will not* use the OM git repo, as that is owned and<br /> controlled by Openmoko the company...<br /> &lt;/pre&gt;<br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-07-10T22:42:36Z

<p>Wurp: /* Interest */</p> <hr /> <div>''This page is a placeholder to get us organized until we can get a build started.''<br /> <br /> == Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the 2007.2 GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br /> <br /> (We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br /> <br /> Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br /> <br /> == First steps ==<br /> The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br /> <br /> We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br /> <br /> == Interest ==<br /> Here's a list of people who've expressed an interest in working on the SHR.<br /> <br /> * [[User:Wurp|wurp2]]<br /> * [[User:Ferric|ferric]]<br /> * [[User:Paulproteus|paulproteus]]<br /> * [[User:Ainulindale|Ainulindale]]<br /> * [[User:jluis|Jose Luis]]<br /> * [[User:Kevin_Dean|Kevin Dean]]<br /> * [[User:Cb22|cb22]]<br /> * [[User:Jeremy-list|Jeremy List]]<br /> * mwester<br /> <br /> == How to join ==<br /> * Please add your name (with a link to your user page) to the list above.<br /> * You should also send a request to join on the [http://projects.openmoko.org/projects/shr SHR project] on the OM projects page to join.<br /> * Join [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel shr-devel@lists.projects.openmoko.org] and send an introductory email.<br /> <br /> The introductory email can just be a couple of lines if you like. It should include what part would you want to work on, and any special knowledge you have that would relate to the project, e.g. if you are an OE guru or linux kernel geek, matchbox-window manager guru, etc.<br /> <br /> == Tasks &amp; status ==<br /> Here's a list of the tasks for the SHR:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space; just need to talk about git branches<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |-<br /> |phonekit to ophoned adapter<br /> |Pre-Alpha<br /> |[[User:Ainulindale|Ainulindale]]<br /> |[[User:Ferric|ferric]], [[User:Wurp|Wurp]]<br /> |2008-07-10<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |[[User:Kevin_Dean|Kevin Dean]]<br /> |Nobody<br /> |2008-07-05<br /> |-<br /> |[[#List_of_packages_included|Identify packages to go into SHR]]<br /> |Started<br /> |[[User:Wurp|Wurp]]<br /> |Anyone &amp; everyone<br /> |2008-07-10<br /> |-<br /> |Identify differences between FSO &amp; 2007.2 that need investigation<br /> |Started<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-08<br /> |-<br /> |Switch FSO to use the matchbox window manager (as does 2007.2)<br /> |Started<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-08<br /> |}<br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * ophoned<br /> * preferencesd<br /> * pimd<br /> * odeviced<br /> * lots more...<br /> <br /> From 2007.2:<br /> * TODO<br /> * lots more...<br /> <br /> From ASU:<br /> * TODO<br /> * lots more...<br /> <br /> == Project links ==<br /> [http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br /> <br /> == IRC conversation about how we're using revision control ==<br /> From 2007-07-07<br /> &lt;pre&gt;<br /> 12:36 &lt; wurp2&gt; Everything *new* goes on OM projects site<br /> 12:36 &lt; Ainulindale&gt; I totally agree<br /> 12:36 &lt; wurp2&gt; Updates to 2007.2 apps go back into the home svn<br /> 12:36 &lt; Ainulindale&gt; paulproteus: no, you're an external cabal all by yourself<br /> :-)<br /> 12:36 &lt; cb22&gt; anyone planning on drawing up a roadmap?<br /> 12:36 &lt; paulproteus&gt; cb22, We can do that in Trac in fact.<br /> 12:36 &lt; wurp2&gt; And changes to the underlying release go as patches into our OE<br /> branch, yes?<br /> 12:36 &lt; paulproteus&gt; (or on the wiki page)<br /> 12:36 &lt; paulproteus&gt; wurp2, Right<br /> 12:36 &lt; paulproteus&gt; mwester, Sanity-check my terminology where I mess things<br /> up!<br /> 12:37 &lt; Ainulindale&gt; hmmm fuzzy for me but what should go in OM and what should<br /> go in OE ?<br /> 12:37 &lt;@mwester&gt; Sure<br /> 12:37 &lt;@mwester&gt; What do you mean by OM?<br /> 12:37 &lt; paulproteus&gt; Ainulindale, New software we write goes in the<br /> projects.openmoko.org.<br /> 12:37 &lt;@mwester&gt; right.<br /> 12:37 &lt; Ainulindale&gt; Ok so the wrapper for example<br /> 12:37 &lt; wurp2&gt; Anything stand-alone goes in OM (projects.openmoko.org)<br /> 12:37 &lt; wurp2&gt; yeah<br /> 12:37 &lt;@mwester&gt; So we will use projects.openmoko.org for as much as we can,<br /> and OE to build the distro.<br /> 12:37 &lt; Ainulindale&gt; Sounds right to me<br /> 12:37 &lt; wurp2&gt; Great!<br /> 12:38 &lt;@mwester&gt; We *will not* use the OM git repo, as that is owned and<br /> controlled by Openmoko the company...<br /> &lt;/pre&gt;<br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]</div>

Wurp http://wiki.openmoko.org/wiki/Stable_Hybrid_Release 2008-07-10T16:32:37Z

<p>Wurp: /* Tasks &amp; status */</p> <hr /> <div>''This page is a placeholder to get us organized until we can get a build started.''<br /> <br /> == Overview ==<br /> The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the 2007.2 GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br /> <br /> (We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br /> <br /> Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br /> <br /> == First steps ==<br /> The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br /> <br /> We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br /> <br /> == Interest ==<br /> Here's a list of people who've expressed an interest in working on the SHR. Please add your name (with a link to your user page) if you'd like to help. Also, please put a way to contact you on your user page.<br /> <br /> * [[User:Wurp|wurp2]]<br /> * [[User:Ferric|ferric]]<br /> * [[User:Paulproteus|paulproteus]]<br /> * [[User:Ainulindale|Ainulindale]]<br /> * [[User:jluis|Jose Luis]]<br /> * [[User:Kevin_Dean|Kevin Dean]]<br /> * [[User:Cb22|cb22]]<br /> * [[User:Jeremy-list|Jeremy List]]<br /> * mwester<br /> <br /> == Tasks &amp; status ==<br /> Here's a list of the tasks for the SHR:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Status<br /> |Owner<br /> |Helping out<br /> |Last update<br /> |-<br /> |Run the build host<br /> |Have server CPU time and disk space; just need to talk about git branches<br /> |[[User:Paulproteus|paulproteus]]<br /> |<br /> |2008-07-03<br /> |-<br /> |phonekit to ophoned adapter<br /> |Pre-Alpha<br /> |[[User:Ainulindale|Ainulindale]]<br /> |[[User:Ferric|ferric]], [[User:Wurp|Wurp]]<br /> |2008-07-10<br /> |-<br /> |Test &amp; label good SHR releases<br /> |Awaiting builds<br /> |[[User:Kevin_Dean|Kevin Dean]]<br /> |Nobody<br /> |2008-07-05<br /> |-<br /> |[[#List_of_packages_included|Identify packages to go into SHR]]<br /> |Started<br /> |[[User:Wurp|Wurp]]<br /> |Anyone &amp; everyone<br /> |2008-07-10<br /> |-<br /> |Identify differences between FSO &amp; 2007.2 that need investigation<br /> |Started<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-08<br /> |-<br /> |Switch FSO to use the matchbox window manager (as does 2007.2)<br /> |Started<br /> |[[User:Wurp|Wurp]]<br /> |Nobody yet<br /> |2008-07-08<br /> |}<br /> <br /> Completed tasks:<br /> {|cellpadding=&quot;5&quot; cellspacing=&quot;0&quot; border=&quot;1&quot; width=&quot;600&quot;<br /> |+<br /> |Task<br /> |Resolution<br /> |When resolved<br /> |-<br /> |Set up launcher (home) page and document how to add new apps to it<br /> |The launcher will be the apps tab of openmoko-today2<br /> |2008-07-08<br /> |-<br /> |Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br /> |Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br /> |2008-07-08<br /> |-<br /> |}<br /> <br /> Statuses:<br /> * '''Needs owner!''' - someone needs to take responsibility for this task<br /> * Not started - someone has taken responsibility, but hasn't done anything yet...<br /> * Started - someone has started work, but there is nothing usable yet<br /> * Alpha - it might work, maybe<br /> * Beta - it probably works most of the time<br /> * Maintained - a stable release is out there, working on oddball bugs &amp; new features<br /> * Done - a stable release is out there, no activity on this task now<br /> <br /> == List of packages included ==<br /> <br /> From FSO:<br /> * ophoned<br /> * preferencesd<br /> * pimd<br /> * odeviced<br /> * lots more...<br /> <br /> From 2007.2:<br /> * TODO<br /> * lots more...<br /> <br /> From ASU:<br /> * TODO<br /> * lots more...<br /> <br /> == Project links ==<br /> [http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br /> <br /> == IRC conversation about how we're using revision control ==<br /> From 2007-07-07<br /> &lt;pre&gt;<br /> 12:36 &lt; wurp2&gt; Everything *new* goes on OM projects site<br /> 12:36 &lt; Ainulindale&gt; I totally agree<br /> 12:36 &lt; wurp2&gt; Updates to 2007.2 apps go back into the home svn<br /> 12:36 &lt; Ainulindale&gt; paulproteus: no, you're an external cabal all by yourself<br /> :-)<br /> 12:36 &lt; cb22&gt; anyone planning on drawing up a roadmap?<br /> 12:36 &lt; paulproteus&gt; cb22, We can do that in Trac in fact.<br /> 12:36 &lt; wurp2&gt; And changes to the underlying release go as patches into our OE<br /> branch, yes?<br /> 12:36 &lt; paulproteus&gt; (or on the wiki page)<br /> 12:36 &lt; paulproteus&gt; wurp2, Right<br /> 12:36 &lt; paulproteus&gt; mwester, Sanity-check my terminology where I mess things<br /> up!<br /> 12:37 &lt; Ainulindale&gt; hmmm fuzzy for me but what should go in OM and what should<br /> go in OE ?<br /> 12:37 &lt;@mwester&gt; Sure<br /> 12:37 &lt;@mwester&gt; What do you mean by OM?<br /> 12:37 &lt; paulproteus&gt; Ainulindale, New software we write goes in the<br /> projects.openmoko.org.<br /> 12:37 &lt;@mwester&gt; right.<br /> 12:37 &lt; Ainulindale&gt; Ok so the wrapper for example<br /> 12:37 &lt; wurp2&gt; Anything stand-alone goes in OM (projects.openmoko.org)<br /> 12:37 &lt; wurp2&gt; yeah<br /> 12:37 &lt;@mwester&gt; So we will use projects.openmoko.org for as much as we can,<br /> and OE to build the distro.<br /> 12:37 &lt; Ainulindale&gt; Sounds right to me<br /> 12:37 &lt; wurp2&gt; Great!<br /> 12:38 &lt;@mwester&gt; We *will not* use the OM git repo, as that is owned and<br /> controlled by Openmoko the company...<br /> &lt;/pre&gt;<br /> <br /> == Reference Material ==<br /> * [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br /> * [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br /> <br /> [[Category:Openmoko]]<br /> [[Category:Community]]</div>

Wurp http://wiki.openmoko.org/wiki/Manuals/Zhone 2008-07-08T22:41:13Z

<p>Wurp: </p> <hr /> <div>Need a screenshot :-)<br /> <br /> == On first boot ==<br /> After it boots all the way up the first time after you install, boot again. I dunno why, but you gotta.<br /> <br /> == Date &amp; time ==<br /> On the home screen, the very top middle of the screen shows the date, and time is displayed in large text above the four primary buttons mid-screen.<br /> <br /> == Network &amp; Signal Strength ==<br /> On the home screen, the top left bar on Zhone is the signal strength. The length of the blue bar compared to the black box it's in is how strong your signal is. No blue bar, no signal. Above the signal strength bar is your network name.<br /> <br /> == Battery life &amp; some other stuff... ==<br /> On the home screen, the top right bar is the battery remaining. The length of the green bar compared to the black box it's in is how much battery is remaining. Above the battery remaining bar should be a series of letters (b G1 w s). I don't know what they mean :-) If it says &quot;no dbus&quot; above the battery bar instead of no letters, try rebooting the phone.<br /> <br /> == Rebooting ==<br /> Yank the battery. No kidding.<br /> <br /> == Suspend ==<br /> Push the power button twice briefly.<br /> <br /> == Resume ==<br /> Push the power button once, or receive a phone call. Sometimes the neo immediately suspends again after resuming via the power button (I have no idea why). Just try again.<br /> <br /> == Making calls ==<br /> Touch the button with the phone on it. Type in your number. You may have to backspace (using the left arrow) to remove the previous number you called. Touch the green checkmark.<br /> <br /> == Hold &amp; hang up ==<br /> It should switch to showing your number, with a hold &amp; hang up button underneath. I'm not sure what the hold button does (or if it works). The hang up button does the obvious.<br /> <br /> == Returning to the main screen ==<br /> After you hang up, it remains on the same screen, with the hold &amp; hang up buttons blanked out. Above the number it will say &quot;Release&quot;. You can just click the X on the lower right to return to the home screen.<br /> <br /> == Unknown functionality ==<br /> The two left buttons on the bottom of the screen don't appear to do anything.<br /> <br /> Of the four buttons in the middle of the home screen, the top right button starts a demo of a keyboard. You touch &amp; drag to type characters. There doesn't appear to be a way to delete, and the characters can't actually be fed anywhere, so it's not good for much now.<br /> <br /> == Unlocking handset ==<br /> Sometimes you'll see the background faded and four numbered buttons on the screen. Press 1, then 2, then 3, then 4 to unlock the handset.</div>

Wurp http://wiki.openmoko.org/wiki/OpenmokoFramework 2008-07-08T22:38:28Z

<p>Wurp: </p> <hr /> <div>{{Languages|OpenmokoFramework}}<br /> <br /> <br /> {{Introbox}}<br /> <br /> <br /> ''Note: This is the (ongoing) description of the new framework architecture that is '''in development'''. See [[OpenmokoOldFramework]] for the framework architecture of 2007.1 and 2007.2 and [[NeoSoftwareStack]] for the current status (which has nothing to do yet with this framework)''<br /> <br /> &lt;categorytree mode=pages style=&quot;float:right; clear:right; margin-left:1ex; border:1px solid gray; padding:0.7ex; background-color:white;&quot;&gt;Framework&lt;/categorytree&gt;<br /> <br /> =Q/A=<br /> * ''Question'': Is this an Openmoko-only thing?<br /> * ''Answer'': No. It's going to be available for all kinds of mobile hardware running Linux, i.e. OpenEZX, XanaduX, HTC/iPAQ, ...<br /> * ''Question'': Is this a part of the current images yet? Is it perhaps the mystic ASU?<br /> * ''Answer'': No.<br /> * ''Question'': When can I see this as part of an image?<br /> * ''Answer'': Not before winter '08.<br /> * ''Question'': What's the current status?<br /> * ''Answer'': See right below or hop over to http://trac.freesmartphone.org<br /> ** [[OpenmokoFramework/Status Update 1|Status Update 1]]<br /> ** [[OpenmokoFramework/Status Update 2|Status Update 2]]<br /> * ''Question'': How do I work the Zhone (FSO demo app) UI?<br /> * ''Answer'': [[FSO UI Tutorial]]<br /> =Purposes=<br /> * '''Give people the infrastructure to create solid and exciting software products based on the Openmoko platform'''<br /> * '''Support competing UIs while collaborating on developing services'''<br /> * '''Encourage framework users (e.g. application developers) to also contribute to the framework'''<br /> <br /> =Requirements=<br /> * Make it simple<br /> * Concentrate on core services<br /> * Be programming language agnostic<br /> * Be UI toolkit agnostic<br /> * Try to reuse existing technologies as much as possible, but not at the cost of a bad API<br /> <br /> =How to achieve that technically=<br /> * Chose [[Dbus]] as the collaboration line. Below dbus, we can work together. Above dbus, we can differentiate.<br /> * Expose features through dbus APIs implemented by UI-agnostic and language-agnostic services (daemons).<br /> * Optimize for Openmoko devices, but support multiple architectures and purposes through plugin interfaces and suitable hardware abstraction mechanisms.<br /> * Be not afraid of reinventing the wheel for a wheel-barrow if all the existing wheels are made for sports cars.<br /> <br /> =Mandatory Readings=<br /> * [http://adam.gomaa.us/blog/frameworks-exist-for-conceptual-integrity/ Frameworks exist for conceptual integrity]<br /> * [http://humanized.com/weblog/2007/10/05/make_oss_humane/ Ten ways to make more humane open source software]<br /> * [http://www.freesmartphone.org FreeSmartPhone.org Wiki]<br /> <br /> =What this is NOT about=<br /> This initiative does not cover low level services such as<br /> * Bootloader, Kernel, or System Init.<br /> <br /> This initiative does not cover high level services such as<br /> * X-Window-System, Window Manager, UI Toolkits,<br /> * Application Launchers, Applications, or Fancy UIs.<br /> <br /> =Architectural Overview=<br /> [[Image:OpenmokoFramework08.png |823px|frontside]]<br /> <br /> =Software Components=<br /> <br /> We differenciate between low-level and high-level services -- dbus will be used to communicate horizontally and vertically.<br /> <br /> ===Low-Level Services===<br /> <br /> ====Device Control====<br /> The low level device control service manages peripheral control, i.e. controlling power for individual subsystems such as<br /> * GSM, WiFi, Bluetooth, GPS, as well as<br /> * Backlight brightness and power,<br /> * turning LEDs on and off, etc.<br /> It also deals with<br /> * charging, suspend/resume,<br /> * accellerometers, and buttons.<br /> Last but not least, it sends notifications about the user's activity so that listeners have a chance to<br /> * change to powersaving modes, or<br /> * lock the device.<br /> We implement the following software for that:<br /> * [http://www.freesmartphone.org/index.php/Implementations/OpenDeviceDaemon odeviced]<br /> <br /> ====Audio====<br /> The low level audio service relies on a working alsa device driver. On top of that, there are two components:<br /> # [http://gstreamer.freedesktop.org/ gstreamer]<br /> # [http://pulseaudio.org pulseaudio]<br /> <br /> '''Gstreamer''' is to be used for all kinds of event sounds where a) multiple audio formats need to be supported and b) a latency of about one second is acceptable. This goes for e.g. ring tones, welcome tones, plug indication.<br /> <br /> '''Pulseaudio''' is to be used for event sounds, where low-latency is necessary, e.g. touch click sounds and UI event acknowledge sounds. Pulseaudio is our general all-purpose mixer. Gstreamer will use the pulseaudio sink to feed audio through.<br /> <br /> ====GSM====<br /> The low level GSM services expect a modem complying to GSM 07.07, GSM 07.05, and assorted GSM specifications, talking an AT-protocol over a serial line. If GSM 07.10 is supported, we use the multiplexing daemon<br /> * [http://www.freesmartphone.org/index.php/Implementations/gsm0710muxd gsm0710muxd]<br /> to export virtual serial lines over -- again -- AT-protocol can be spoken.<br /> <br /> ====Bluetooth====<br /> The low level Bluetooth services rely on the official Linux Bluetooth subsystem:<br /> * [http://www.bluez.org BlueZ].<br /> <br /> ====GPS====<br /> The low level GPS services assume a GPS device that talks NMEA over a device node. We rely on the following software:<br /> * [http://gypsy.freedesktop.org Gypsy]<br /> <br /> ====Network====<br /> The low level networking service assumes network interfaces, such as USB, Ethernet, Wifi, etc. We rely on the following software here:<br /> * Network Manager or Intel Connection Manager (undecided yet)<br /> * ppp<br /> <br /> ===High Level===<br /> <br /> ====Usage====<br /> The Usage subsystem is coordinating application I/O requirements preventing. Applications are not supposed to turn on or off devices, since they do not have any knowledge about concurrent applications that may be also using the device -- think ''reference counting'' for I/O requirements.<br /> <br /> With this added layer, we could later think about monitoring subsystems, subsystem usage statistics, or accounting.<br /> <br /> See discussion page about PolicyKit.<br /> <br /> ====Events====<br /> * signaling events via I/O (ringing, blinking, vibrating)<br /> * might use fd.o notification API<br /> <br /> ====PIM====<br /> An intelligent storage database server. This is being carried out as a Google Summer of Code project. See complete description [http://www.neo1973-germany.de/wiki/pyPimd here]<br /> <br /> ====Context====<br /> * Intelligent context API, integrating location as one -- among other -- sources<br /> TBD<br /> Reference Geoclue<br /> <br /> ====Telephony====<br /> * Voice<br /> * Data<br /> <br /> === [http://www.freesmartphone.org/index.php/Implementations/OpenPreferencesDaemon Preferences] ===<br /> * settings database<br /> <br /> ====Network====<br /> * high level networking queries<br /> <br /> =Implementation=<br /> <br /> ===Completion Status===<br /> <br /> ====Low Level====<br /> * device control: 50%<br /> * audio: 80%<br /> * GSM: 80%<br /> * Bluetooth: 80%<br /> * GPS: 80%<br /> * Network: 50%<br /> <br /> ====High Level====<br /> * Usage: 0%<br /> * Event: 0%<br /> * [http://www.freesmartphone.org/index.php/Implementations/OpenPreferencesDaemon Preferences]: 50%<br /> * Context: 0%<br /> * Telephony: 50%<br /> * Networking: 0%<br /> * PIM: 0%<br /> <br /> =The role of Python=<br /> <br /> Where we write new code, we will use Python to implement the dbus services. The reason for that being the rapid prototyping nature of Python and the emphasis on the Dbus APIs. Using Python, the turnaround times to experiment with APIs are incredibly faster than for using a compiled language such as C or C++.<br /> <br /> Once the APIs have been used by application programmers, we can start profiling and possibly reimplement some of the services with daemons written in Vala, ''if'' necessary. We might as well succeed in improving performance by using Pyrex/Cython/Ctypes to keep the benefits of Python.<br /> <br /> =Team &amp; Roadmap=<br /> <br /> ==Team==<br /> <br /> * [[User:Mickey|Michael 'Mickey' Lauer]] (team leader) -- Openmoko freelancer, working in Frankfurt/Main, Germany.<br /> * [[User:Charlie| Guillaume 'Charlie' Chereau]] -- Openmoko employee, working fulltime in the Openmoko office, Taipei, Taiwan.<br /> * [[User:Shoragan|Jan 'Shoragan' Luebbe]] -- Openmoko student, working part-time in Brunswick, Germany.<br /> * [[User:DanielWillmann|Daniel 'Alphaone' Willmann]] -- Openmoko student, working part-time in Brunswick, Germany.<br /> * (Holger 'Zecke' Freyther -- hopefully joining the team after releasing ASU, working in Berlin, Germany.)<br /> <br /> '''Subsystem Ownership'''<br /> <br /> ''Phase 1 subsystems''<br /> <br /> * odeviced (mickey)<br /> * ophoned (mickey)<br /> * ousaged (jan)<br /> * oeventd (jan)<br /> * opreferencesd (guillaume)<br /> * ocontextd (guillaume)<br /> <br /> ''Phase 2 subsystems''<br /> <br /> * network (to be defined)<br /> * pim (to be defined)<br /> <br /> ==Roadmap==<br /> <br /> The milestone releases are combined Openmoko Framework and [[Zhone]] releases. Remember: A feature that isn't visible, working, and tested in our framework testing application (Zhone) does ''not'' exist. Until Framework 1.0.0 (later this year), we will not use any versioning in components. Afterwards, individual components may see individual releases.<br /> <br /> '''Note: The milestones and tasks moved over to our [http://trac.freesmartphone.org issue tracker].'''<br /> <br /> ----<br /> <br /> [[Category:Openmoko ]]<br /> [[Category:Framework ]]</div>

Wurp http://wiki.openmoko.org/wiki/Manuals/Zhone 2008-07-08T22:37:31Z

<p>Wurp: New page: Need a screenshot :-) == Date &amp; time == On the home screen, the very top middle of the screen shows the date, and time is displayed in large text above the four primary buttons mid-screen...</p> <hr /> <div>Need a screenshot :-)<br /> <br /> == Date &amp; time ==<br /> On the home screen, the very top middle of the screen shows the date, and time is displayed in large text above the four primary buttons mid-screen.<br /> <br /> == Network &amp; Signal Strength ==<br /> On the home screen, the top left bar on Zhone is the signal strength. The length of the blue bar compared to the black box it's in is how strong your signal is. No blue bar, no signal. Above the signal strength bar is your network name.<br /> <br /> == Battery life &amp; some other stuff... ==<br /> On the home screen, the top right bar is the battery remaining. The length of the green bar compared to the black box it's in is how much battery is remaining. Above the battery remaining bar should be a series of letters (b G1 w s). I don't know what they mean :-) If it says &quot;no dbus&quot; above the battery bar instead of no letters, try rebooting the phone.<br /> <br /> == Rebooting ==<br /> Yank the battery. No kidding.<br /> <br /> == Suspend ==<br /> Push the power button twice briefly.<br /> <br /> == Resume ==<br /> Push the power button once, or receive a phone call. Sometimes the neo immediately suspends again after resuming via the power button (I have no idea why). Just try again.<br /> <br /> == Making calls ==<br /> Touch the button with the phone on it. Type in your number. You may have to backspace (using the left arrow) to remove the previous number you called. Touch the green checkmark.<br /> <br /> == Hold &amp; hang up ==<br /> It should switch to showing your number, with a hold &amp; hang up button underneath. I'm not sure what the hold button does (or if it works). The hang up button does the obvious.<br /> <br /> == Returning to the main screen ==<br /> After you hang up, it remains on the same screen, with the hold &amp; hang up buttons blanked out. Above the number it will say &quot;Release&quot;. You can just click the X on the lower right to return to the home screen.<br /> <br /> == Unknown functionality ==<br /> The two left buttons on the bottom of the screen don't appear to do anything.<br /> <br /> Of the four buttons in the middle of the home screen, the top right button starts a demo of a keyboard. You touch &amp; drag to type characters. There doesn't appear to be a way to delete, and the characters can't actually be fed anywhere, so it's not good for much now.<br /> <br /> == Unlocking handset ==<br /> Sometimes you'll see the background faded and four numbered buttons on the screen. Press 1, then 2, then 3, then 4 to unlock the handset.</div>

Wurp