[Om2009] a community effort
Hey there, A lot has happened over the past couple of months, but most important in my mind has been getting OM2009 out into the hands of the community. When we set the very limited goals of OM2009 we had two goals in mind: 1. Give those members of the community who only wanted a daily phone, a distro they could use 2. Introduce technology that would allow the community to come together and improve on these basics Community interaction, open development and user driven decision making are at the core of Om2009. Going forward this will be an effort with the community for the community. The help and support I have gotten from the community over the past couple of days and weeks has been remarkable and I can see things starting to move and slowly coming together. We need more of this! I invite you to join the effort to make om2009 with paroli the best Om-labeled distribution for the Freerunner. How can you help? Test the distro, let us know about bugs you find, or even fix them and send us patches. Tell us about your experiences using om2009, what should we change, where can we improve? Paroli has come a long way but it still needs a lot of love and optimizing, so if you are into python or efl, check out the code from git.paroli.org, join #paroli on irc and let's get crackin'. There is lots of things to do, opimd needs to be integrated and improved, the UI needs polishing, overall speed can be increased etc etc More into Chat and email? Feel like writing a jabber/irc/xxx or email client that really fits the screen? Or do you know of one? Let's hear about it. See a list of proposals on: http://wiki.openmoko.org/wiki/Om_2009_get_active and http://wiki.openmoko.org/wiki/Paroli-issues This device has a lot of potential and we are so close to reaching the far corners, the kernel is in good shape, the framework is doing great and telephony apps such as paroli or the shr suite are steadily improving. So, get your Freerunner in shape again. Flash it with a nice current distro and let it do what it was meant to do :) Let's make Om2009 a community product, something all of us can be proud of and say we did this. Regards, /Mirko ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2009] a community effort
Hi How can you help? OK, I am inclined to try that. Installations instructions say http://wiki.openmoko.org/wiki/Om2009 If you have not upgraded the GSM firmware do that too but it doesnt say which version of firmware needs upgrading, or any way to check your current firmware version, neither on the Flashing page; The instructions on the Flashing page http://wiki.openmoko.org/wiki/GSM/Flashing sound very scary, and I am not inclined to do that yet. Is upgrading the frimware required to install 2009/testing ? My hardware has been fine using QTExtended. thanks, *-pike ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2009] a community effort
Community: if you want to write some opimd support (for instance in Paroli) or improve opimd itself, please contact me. It was hard to understand everything, but now, after fixing Contacts domain, I think I can give you some useful knowledge :) I have also few nice and helpful python test scrips. I'm going to post them on maillist soon. Right now we have working Contacts domain with three backends: SIM, CSV and SQLite. Now I'm going to work on Messages domain, which ATM can only read from SIM backend. People who helped me to fix opimd: Heinervdm (SQLite backend), mirko-paroli (adding items with SIM backend) and mrmoku (opimd feeded SHR GUI:[ libframeworkd-phonegui-elf2). I would like to see also you on this list! :) Regards, Sebastian Krzyszkowiak On 5/16/09, Mirko Lindner mi...@openmoko.org wrote: Hey there, A lot has happened over the past couple of months, but most important in my mind has been getting OM2009 out into the hands of the community. When we set the very limited goals of OM2009 we had two goals in mind: 1. Give those members of the community who only wanted a daily phone, a distro they could use 2. Introduce technology that would allow the community to come together and improve on these basics Community interaction, open development and user driven decision making are at the core of Om2009. Going forward this will be an effort with the community for the community. The help and support I have gotten from the community over the past couple of days and weeks has been remarkable and I can see things starting to move and slowly coming together. We need more of this! I invite you to join the effort to make om2009 with paroli the best Om-labeled distribution for the Freerunner. How can you help? Test the distro, let us know about bugs you find, or even fix them and send us patches. Tell us about your experiences using om2009, what should we change, where can we improve? Paroli has come a long way but it still needs a lot of love and optimizing, so if you are into python or efl, check out the code from git.paroli.org, join #paroli on irc and let's get crackin'. There is lots of things to do, opimd needs to be integrated and improved, the UI needs polishing, overall speed can be increased etc etc More into Chat and email? Feel like writing a jabber/irc/xxx or email client that really fits the screen? Or do you know of one? Let's hear about it. See a list of proposals on: http://wiki.openmoko.org/wiki/Om_2009_get_active and http://wiki.openmoko.org/wiki/Paroli-issues This device has a lot of potential and we are so close to reaching the far corners, the kernel is in good shape, the framework is doing great and telephony apps such as paroli or the shr suite are steadily improving. So, get your Freerunner in shape again. Flash it with a nice current distro and let it do what it was meant to do :) Let's make Om2009 a community product, something all of us can be proud of and say we did this. Regards, /Mirko ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2009] a community effort
Hi, pike wrote: OK, I am inclined to try that. Yay :) Installations instructions say http://wiki.openmoko.org/wiki/Om2009 If you have not upgraded the GSM firmware do that too but it doesnt say which version of firmware needs upgrading, or any way to check your current firmware version, neither on the Flashing page; it is called Moko11 iirc. The instructions on the Flashing page http://wiki.openmoko.org/wiki/GSM/Flashing sound very scary, and I am not inclined to do that yet. Is upgrading the frimware required to install 2009/testing ? My hardware has been fine using QTExtended. No, updating the firmware will give you a more stable system but it is not a must. /mirko ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2009] a community effort
On 5/16/09, pike pike-openm...@kw.nl wrote: Hi How can you help? OK, I am inclined to try that. Installations instructions say http://wiki.openmoko.org/wiki/Om2009 If you have not upgraded the GSM firmware do that too but it doesnt say which version of firmware needs upgrading, or any way to check your current firmware version, neither on the Flashing page; The instructions on the Flashing page http://wiki.openmoko.org/wiki/GSM/Flashing sound very scary, and I am not inclined to do that yet. Is upgrading the frimware required to install 2009/testing ? My hardware has been fine using QTExtended. thanks, *-pike ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community GSM firmware upgrade to Moko11 is recommended to EVERYONE using EVERY distro. If you didn't flashed firmware yet, it means that you have older version. Don't worry, flashing is safe. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2009] a community effort
but it doesnt say which version of firmware needs upgrading, or any way to check your current firmware version, neither on the Flashing page; the flashing issue has been discussed so much the last few weeks that i honestly do not understand, how you can come up with the questions again. the archives ar full with multiple times the answers. anyway. see http://wiki.openmoko.org/wiki/OpenmokoFramework/mickeyterm for checking your current fw version, command is at+cgmr. if you never knowingly updated your modem's firmware and nobody did it for you, you very likely don't have fw 11. The instructions on the Flashing page http://wiki.openmoko.org/wiki/GSM/Flashing sound very scary, and I am not inclined to do that yet. please, read the full page, not just the first ten lines or so! in the last part is described how to do everything by simply booting an image. get that image, write it to an sd card, boot from said sd card, watch the automatic flashing, done. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2009] a community effort
Hi Is upgrading the firmware required to install 2009/testing ? No, updating the firmware will give you a more stable system but it is not a must. And I assume I can do it later, when its even more monkeyfriendly. Don't worry, flashing is safe. It's a scary read. And I don't have a uSD card reader in my mac. OK, next question - I assume Qi has to be flashed first, is that correct ? It is last on the list at http://wiki.openmoko.org/wiki/Om2009. And after flashing Qi, I can continue with the normal procedure ? Sorry for the obvious questions, but you asked for it :-D thanks, *-pike ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
GSM Firmware upgrade (was: Re: [Om2009] a community effort)
pike pike-openm...@kw.nl writes: The instructions on the Flashing page http://wiki.openmoko.org/wiki/GSM/Flashing sound very scary, and I am not inclined to do that yet. Is upgrading the frimware required to install 2009/testing ? My hardware has been fine using QTExtended. Upgrading GSM gives you: compatibility with all SIM-cards (and don't forget that you might be forced to switch your working simcard to the one incompatible with moko8 when you'll have no time to think about GSM firmware), more robust resume on incoming call/message, proper flow control support (less risk of data loss and buffer overruns). Upgrading firmware is not scary at all, and is especially easy with the uSD image prepared by Joerg. I strongly recommend that (you can ask low-level devs but i'm sure they'll tell the same). -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GSM Firmware upgrade
arne anka openm...@ginguppin.de writes: but it doesnt say which version of firmware needs upgrading, or any way to check your current firmware version, neither on the Flashing page; the flashing issue has been discussed so much the last few weeks that i honestly do not understand, how you can come up with the questions again. the archives ar full with multiple times the answers. Well... and apparently nobody cared enough at OpenMoko Inc to issue a statement with proper instructions for regular users ? ... nor updating the wiki pages to make it user-friendly either :-/ Not everyone has time to read avery threads I suppose... Just my 2 cents, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Comments questions abou Paroli UI design
Hi, Risto H. Kurppa wrote: I really like the simple design but it must be easy to use, too, for a someone that steals my phone (or who I give my phone to :). On the other hand I'd like it to be colourful, with background image and everything but maybe that comes with the themes (if Paroli is themeable?) Paroli is indeed themeable. Due to its plugin-nature every app comes with its own edc files that can be adapted which is highly encouraged. If anyone wants to give it a go or improve the default design get in touch with me, I help where I can. * For a new user it's a mess not knowing when to slide things sideways and when to click on 'nothing' (=black area) to get to phonebook etc. I think I'd like to see small arrows on top/bottom or left/right on the screen when user can slide. Maybe this could be a 'beginners mode' and then the 'advanced mode' turns them off? I like the idea of adding small hints and had thought about a first use mode myself. my idea included windows explaining the screens, but you approach is much nicer :) * No colours (delete, recharge, adding name) Recharging should turn the battery icon yellow and delete should be red everywhere ... I am open to more color as well, although I do like the combination of black and white as the dominating colors and would like the standard theme to keep this focus, but then again I am no designer. * When there's a screen to type in something, it should read what are you typing in. Is it the name for a phonebook item, a SMS, WLAN network password ...? That is more my fault than a design issue, that can be fixed. http://www.paroli-project.org/trac/ticket/154 * Empty I/O shows an 'edit' button.. maybe it should be hidden and instead a text 'no logged events' could be shown? That I already implemented (after reading this mail), it is currently still only on my machine as the commit would break other things, but it is done :) * There's nothing (no text/button) telling one should click in the black area to get to phonebook to select recipient in 'msgs' - '+' or 'Tele' Maybe a little magnifying glass in beginner mode when no number is entered and a + once a number has been entered? * No visual feedback of shutting down (bug #93) hehe, yeah, that is listed just not a high priority for now * when not in fullscreen mode (=illume enabled), one can't see the used profile in the home view - is it intentional that the top bar of Paroli doesn't show if running not-fullscreen? I am fighting this since I first changed profiles...I hunting and hope to get this fixed. * could the dial volume change (AUX during call) either have % char with the number or a graphical scale. Now it's just a number, seeing 60 there doesn't tell you that it's 60% of the max 256 of Calypso.. hmm, I think graphical scale wouldn't be too readable either ... I am personally not a big fan of the % sign. Any icon ideas anyone? * The screen now has (in some views) 4 fields: top bar, navigation bar (next/previous), num view and the keypad. I think I don't get the message... * SMS: There's no feedback after sending a message (bug #3) fixed * The date doesn't need the | -bars in the home view: it's | Sunday, May 10, 2009 | - the bars just make it more difficult to read That also depends on you liking I guess... I don't find them too bad. Opinions anyone? * renaming of I/O, Tele and Msgs in the menu (maybe to call log, SMS and dialer?) Hehe, I got so used to the names I don't even notice them anymore. * The numbers in the home view showing missed calls or received messages could be bigger/colorful/something or even say 'one missed call' or 'new SMS received Making them bigger I agree, we should do that. The text based output ... difficult as the text would need to change according to number etc. I prefer the numbers (from an implementation point of view as well as internationalization). * When shutting down Paroli the dialog asking to leave paroli in the background has buttons aligned to bottom left. When getting the error messages for failing with loading GSMGPRS, the button is aligned in the bottom center. Should they be aligned to the same place maybe? Should the not look like E dialog but look more like the rest of Paroli? I haven't spend any time in position those buttons, it is elm's standard behavior, so there was no intention behind it. * Going back or closing apps doesn't always work the same: sometimes there's the 'back' button and sometimes you have to press the top bar to go back. It's not easy to understand why there's this difference. And not easy to use as the top bar is hidden when using non-fullscreen, and there's nothin indicating I should click on the top bar to go back/close the app. Apps never have a back-button, they are closed using the topbar. Subwindows should always have a back-button which allows you to navigate an app without closing it. *
Re: GSM Firmware upgrade
I did it now. It taken 5 minutes. Really easy No Problem. It's work. Thx 2009/5/16 Olivier Berger ober...@ouvaton.org arne anka openm...@ginguppin.de writes: but it doesnt say which version of firmware needs upgrading, or any way to check your current firmware version, neither on the Flashing page; the flashing issue has been discussed so much the last few weeks that i honestly do not understand, how you can come up with the questions again. the archives ar full with multiple times the answers. Well... and apparently nobody cared enough at OpenMoko Inc to issue a statement with proper instructions for regular users ? ... nor updating the wiki pages to make it user-friendly either :-/ Not everyone has time to read avery threads I suppose... Just my 2 cents, -- Olivier BERGER (OpenPGP: 1024D/B4C5F37F) http://www.olivierberger.com/weblog/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GSM Firmware upgrade
Olivier Berger ober...@ouvaton.org writes: but it doesnt say which version of firmware needs upgrading, or any way to check your current firmware version, neither on the Flashing page; the flashing issue has been discussed so much the last few weeks that i honestly do not understand, how you can come up with the questions again. the archives ar full with multiple times the answers. Well... and apparently nobody cared enough at OpenMoko Inc to issue a statement with proper instructions for regular users ? ... nor updating the wiki pages to make it user-friendly either :-/ I spent considerable time making the wiki page precise and user-friendly btw. I can't see what you don't like about it. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GSM Firmware upgrade (was: Re: [Om2009] a community effort)
2009/5/16 Paul Fertser fercer...@gmail.com: pike pike-openm...@kw.nl writes: The instructions on the Flashing page http://wiki.openmoko.org/wiki/GSM/Flashing sound very scary, and I am not inclined to do that yet. Upgrading firmware is not scary at all, and is especially easy with the uSD image prepared by Joerg. I strongly recommend that (you can ask low-level devs but i'm sure they'll tell the same). i'll second that. i'd been avoiding it for weeks, and did it last night, using the microsd image. it was very simple, and there was little i could have done wrong it didn't fix the problem, but that's another issue ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] Still wlan problems with 2.6.29 kernels
2009/5/16 Fox Mulder quakem...@gmx.net: Hi, since i upgraded from kernel 2.6.24 to 2.6.29 many things has gotten better. But since than wlan isn't working anymore and i tried many different kernels. [...] You may add your test cases to http://docs.openmoko.org/trac/ticket/2277 there are a couple of bug on shr tracker too if you are interested, as network scripts should be debian based: http://trac.shr-project.org/trac/ticket/419 http://trac.shr-project.org/trac/ticket/418 Regards Nicola ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GSM Firmware upgrade (was: Re: [Om2009] a community effort)
How big of uSD card is needed to use the image to upgrade the GSM Firmware? On May 16, 2009, at 4:56 AM, Paul Fertser wrote: pike pike-openm...@kw.nl writes: The instructions on the Flashing page http://wiki.openmoko.org/wiki/GSM/Flashing sound very scary, and I am not inclined to do that yet. Is upgrading the frimware required to install 2009/testing ? My hardware has been fine using QTExtended. Upgrading GSM gives you: compatibility with all SIM-cards (and don't forget that you might be forced to switch your working simcard to the one incompatible with moko8 when you'll have no time to think about GSM firmware), more robust resume on incoming call/message, proper flow control support (less risk of data loss and buffer overruns). Upgrading firmware is not scary at all, and is especially easy with the uSD image prepared by Joerg. I strongly recommend that (you can ask low-level devs but i'm sure they'll tell the same). -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GSM Firmware upgrade (was: Re: [Om2009] a community effort)
On Saturday 16 May 2009 18:13:39 Yorick Moko wrote: untar the image of http://wiki.openmoko.org/wiki/GSM/Flashing#uSD-card_Image and you'll know it... i'm quite sure 128MB will suffice the 512MB one, delivered with the FR surely will On Sat, May 16, 2009 at 6:07 PM, Adam Jimerson vend...@gmail.com wrote: How big of uSD card is needed to use the image to upgrade the GSM Firmware? george-laptop~/openmoko/fluid☮:du -h flash-moko11-2.image 271Mflash-moko11-2.image I think you'll need the 512meg one. solar.george signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[SHR] Cannot see sdcard
Hi I upgrade my SHR and I cannot see the sdcard r...@om-gta02 ~ $ ls /dev/mm* ls: /dev/mm*: No such file or directory dmesg says r...@om-gta02 ~ $ dmesg | grep mmc [21474571.21] mmc1: queuing CIS tuple 0x01 length 3 [21474571.24] mmc1: queuing CIS tuple 0x1a length 5 [21474571.245000] mmc1: queuing CIS tuple 0x1b length 8 [21474571.25] mmc1: queuing CIS tuple 0x80 length 1 [21474571.25] mmc1: queuing CIS tuple 0x81 length 1 [21474571.25] mmc1: queuing CIS tuple 0x82 length 1 [21474571.255000] mmc1: new SDIO card at address 0001 [21474688.305000] mmc1: card 0001 removed what does this means? Why is the card removed? How can I solve it? Best Regards Alex ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Automatic screen lock
As of simple lock (which does not turn off display backlight power),
I think you don't need configure simple lock in frameworkd.
The AUX key binding is enough -- just a press to lock screen.
If you really need the way of auto + manual, you have to write a ROBUST
application,
which listens to DBUS signals (idle + input event). Here is the pseudo C
code:
int locking = 0;
pthread_mutex lk = ...;
void lock_screen()
{
pop up screen lock window which lay on top of other windows;
optionally turn off display backlight power;
locking = 1;
}
void unlock_screen()
{
close the screen lock window;
turn on display backlight power if it was turned off.
locking = 0;
}
void dbus_idle_signal_handler()
{
if (should lock screen) {
lock(lk);
if (! locking)
lock_screen();
unlock(lk);
}
}
void dbus_input_event_signal handler()
{
if (input event type == pressed) {
lock(lk);
if (locking) {
if (button is AUX || button is POWER)
unlock_screen();
} else {
if (button is AUX)
lock screen();
}
unlock(lk);
}
}
Christian Rüb wrote:
Hi,
as I could not find another way to lock the screen I currently use this
little script (illume + frameworkd):
/usr/local/bin/simple_lock:
#!/bin/sh
export E_IPC_SOCKET=$(find /var/ -type s | grep enlightenment | cut -d\|
-f1)
enlightenment_remote -exec-action simple_lock
in /etc/freesmartphone/oevents/rules.yaml:
-
trigger: IdleState()
filters: HasAttr(status, lock)
actions: Command('/usr/local/bin/simple_lock')
AUX button is also bound to desktop simple lock - otherwise it is
impossible to unlock (withou sshing onto the phone)!
Unfortunately it does not always lock the screen, as the simple_lock
action seems to be a toggle. Thus when you manually turn the lock on (via
AUX) the power state lock now reverts the manually acquired simple lock.
Are there any plans to support a real locking in frameworkd - something
like a touchscreen/keyboard resource? Or is there a way in enlightenment
to force the lock and off?
Cheers,
Christian
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
--
View this message in context:
http://n2.nabble.com/Automatic-screen-lock-tp2913196p2913876.html
Sent from the Openmoko Community mailing list archive at Nabble.com.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] Still wlan problems with 2.6.29 kernels
Yep, the same occurs with new shr kernels... I have your very same need of hving a working wlan, right now i use a 2.6.28-rc4 kernel that works only with static ip wifi... so, at least, you're not alone ;-) d On Sat, May 16, 2009 at 5:34 PM, Nicola Mfb nicola@gmail.com wrote: 2009/5/16 Fox Mulder quakem...@gmx.net: Hi, since i upgraded from kernel 2.6.24 to 2.6.29 many things has gotten better. But since than wlan isn't working anymore and i tried many different kernels. [...] You may add your test cases to http://docs.openmoko.org/trac/ticket/2277 there are a couple of bug on shr tracker too if you are interested, as network scripts should be debian based: http://trac.shr-project.org/trac/ticket/419 http://trac.shr-project.org/trac/ticket/418 Regards Nicola ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2009] a community effort
On Sat, May 16, 2009 at 11:50 AM, pike pike-openm...@kw.nl wrote: No, updating the firmware will give you a more stable system but it is not a must. And I assume I can do it later, when its even more monkeyfriendly. Cleaned the GSM Flashing wiki page a bit. See http://wiki.openmoko.org/wiki/GSM/Flashing - and you also can do it without uSD reader in your mac, see NOTE at http://wiki.openmoko.org/wiki/GSM/Flashing#NOTE OK, next question - I assume Qi has to be flashed first, is that correct ? It is last on the list at http://wiki.openmoko.org/wiki/Om2009. And after flashing Qi, I can continue with the normal procedure ? Sorry for the obvious questions, but you asked for it :-D Cleaned the OM2009 wiki page. See http://wiki.openmoko.org/wiki/Om2009#Installing r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2009] a community effort
Awesome Mirko see this mail. Yes, it's an invitation for the community to start working on OM2009 and I take that since it comes from Openmoko, Openmoko has some resources to commit to enable the community to participate. Let's see where this'll take us! On Sat, May 16, 2009 at 9:39 AM, Mirko Lindner mi...@openmoko.org wrote: Hey there, A lot has happened over the past couple of months, but most important in my mind has been getting OM2009 out into the hands of the community. When we set the very limited goals of OM2009 we had two goals in mind: 1. Give those members of the community who only wanted a daily phone, a distro they could use 2. Introduce technology that would allow the community to come together and improve on these basics And I think we're nicely heading to both goals! Community interaction, open development and user driven decision making are at the core of Om2009. Nice, nice, more of this :) I invite you to join the effort to make om2009 with paroli the best Om-labeled distribution for the Freerunner. I'm in! Anyone else? Test the distro, let us know about bugs you find, or even fix them and send us patches. Some for people to start with: http://wiki.openmoko.org/wiki/Paroli-issues :) Paroli has come a long way but it still needs a lot of love and optimizing, so if you are into python or efl, check out the code from git.paroli.org, join #paroli on irc and let's get crackin'. There is lots of things to do, opimd needs to be integrated and improved, the UI needs polishing, overall speed can be increased etc etc Now that you mention it, maybe someone could describe us what opimd is (please write it here: http://wiki.openmoko.org/wiki/Opimd ) Let's make Om2009 a community product, something all of us can be proud of and say we did this. \o/ r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GSM Firmware upgrade
On Sat, May 16, 2009 at 1:33 PM, Olivier Berger ober...@ouvaton.org wrote: Thanks for your efforts, but my understanding of a user-friendly procedure would be a max. 7 steps with 50 lines long description or something like that, which could be understood (at least to grasp if it's needed and the general idea of the required technical level needed) in 2 minutes reading time... and currently, the instructions fail to comply with such standards :( Understanding the Introduction itself takes at least more than 5 minutes to really figure out what/when/why... IMHO. Of course your mileage may vary, and the proportion of hackers here is probably above average ;-) Try again: http://wiki.openmoko.org/wiki/GSM/Flashing And if not happy, feel free to make it clearer, after all, it's a wiki... r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GSM Firmware upgrade (was: Re: [Om2009] a community effort)
On Saturday 16 May 2009 01:33:38 pm George Brooke wrote: george-laptop~/openmoko/fluid☮:du -h flash-moko11-2.image 271Mflash-moko11-2.image I think you'll need the 512meg one. solar.george Thanks, good thing I keep a hold of the 512MB one that came with my phone. -- We must plan for freedom, and not only for security, if for no other reason than only freedom can make security more secure. Karl Popper signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Comments questions abou Paroli UI design
On Sat, May 16, 2009 at 12:32 PM, Mirko Lindner mi...@openmoko.com wrote: Paroli is indeed themeable. Due to its plugin-nature every app comes with its own edc files that can be adapted which is highly encouraged. If anyone wants to give it a go or improve the default design get in touch with me, I help where I can. It'd be actually very nice to see a new theme for Paroli. Not because I wouldn't like the b/w but to show what it can be. Bling bling, anyone :) * For a new user it's a mess not knowing when to slide things sideways and when to click on 'nothing' (=black area) to get to phonebook etc. I think I'd like to see small arrows on top/bottom or left/right on the screen when user can slide. Maybe this could be a 'beginners mode' and then the 'advanced mode' turns them off? I like the idea of adding small hints and had thought about a first use mode myself. my idea included windows explaining the screens, but you approach is much nicer :) The KDE-approach here would be to present the user with a long list of options s/he could select what to use and what not :) * Empty I/O shows an 'edit' button.. maybe it should be hidden and instead a text 'no logged events' could be shown? That I already implemented (after reading this mail), it is currently still only on my machine as the commit would break other things, but it is done :) Great :) * There's nothing (no text/button) telling one should click in the black area to get to phonebook to select recipient in 'msgs' - '+' or 'Tele' Maybe a little magnifying glass in beginner mode when no number is entered and a + once a number has been entered? I maybe wouldn't want to have there one extra icon as it now already shows the top bar woth profile, time, GPS signal strength and battery, on the next row it has the arrow left 'back' text and 'next' button then the somewhat unclearly shaped empty space (because of the backspace button) and the keyboard. Since no colours are used I really think the concept of 'button' should be around.. How do I know that the arrow left (backspace) is a button, time is not, empty space is, profile name is not, 'next' is and gsm/battery signal again is not, date in home view is not, time you have to slide sideways... I guess this actually is what disturbs me most (atm) in the UI. One really has to struggle to find the places where to press. Think about it: a door with 10 handles - and only one of them actually opens the door. The others would make it rain, close windows, turn alarm on, delete your backups etc.. A pain, right..? * when not in fullscreen mode (=illume enabled), one can't see the used profile in the home view - is it intentional that the top bar of Paroli doesn't show if running not-fullscreen? I am fighting this since I first changed profiles...I hunting and hope to get this fixed. I guess this comes down to the integration: having two bars is not ideal (especially having all time, battery and GSM statuses all there twice, both in Paroli and Illume). I think a nice solution would be to get paroli profile visible in the illume bar but I guess that becomes more difficult... * could the dial volume change (AUX during call) either have % char with the number or a graphical scale. Now it's just a number, seeing 60 there doesn't tell you that it's 60% of the max 256 of Calypso.. hmm, I think graphical scale wouldn't be too readable either ... I am personally not a big fan of the % sign. Any icon ideas anyone? So no text, no graphics.. Not many option? A blinking light that uses morse to tell the %, or maybe using the vibrator.. OTOH, if you think a graphical scale is not readable, I guess you have already thought something else for battery gsm signals too...? So why not something like this, with our 280+ dpi screen: http://www.changing-places.org/images/icon-speaker.gif * The screen now has (in some views) 4 fields: top bar, navigation bar (next/previous), num view and the keypad. I think I don't get the message... oops, I think I was distrubted when writing this..I guess my point was that the UI elements keep moving around in these areas. Or maybe it was that it'd maybe want to see the navigation bar in the bottom, not top or something. Just ignore it, if this stuff still bothers me I'll come back to it.. * The date doesn't need the | -bars in the home view: it's | Sunday, May 10, 2009 | - the bars just make it more difficult to read That also depends on you liking I guess... I don't find them too bad. Opinions anyone? I think it's against this minimalistic UI that Paroli seems to be following. I'd rather see those lines around a button.. (it won't make me stop using Paroli but I'd rather see usability, not eyecandy. I've noticed I've stopped writing SMS's as I have to struggle with Illume keyboard (compared to a phone with physical numbad to write SMS). Just an example of usability, I'd really want to see a fullscreen (transparent) keyboard - but this is
