Re: kernel 2.6.3x?
El Monday, 9 de November de 2009 19:05:04 arne anka va escriure: ... so, simple question: how's the state of the new kernel? anybody working on it? GTA02 boots mainline 2.6.32 and Lars is working on pending patches see http://article.gmane.org/gmane.comp.handhelds.openmoko.kernel/10406 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [OffTopic]Geek'sPhone: New android actor?
2009/11/9 David Lanzendörfer david.lanzendoer...@o2s.ch: Would be nice, if it could become a new development platform for OM/SHR too. Yes Are there some development boards to get? No With JTAG interface and so on? No And a documentation for writing free drivers for the linux kernel? No (AFAIK) Using android kernel is not an option, because they put the mostpart of theire drivers into the apache licensed userspace. In binary format. I know. So the basic idea of opensource handies is died in android, because the linux kernel cant support the hardware on its own, theres alway a binary compatible android userspace needed to have the devices working properly. I hope, if they call theire phone geeky then they are also open to sell developmentboards and documentation. If they dont. Then the word geeky is a lie and we could even call a htc-raph or other windows-ce generation handies geeky. Then we can call every ** smartphone geeky. Because they are all hackable in someway... Totally agree, we are trying to bring this openness you describe to that device but there is a lot of political work to be done ... So please ask them to inform about development boards on theire page. They dont have to make UMTS/GSM open, its clear that they cant, but the rest of the pcb and schematics they could give us in a documentation, so that some smart linux kernel hackers could write some drivers in the propriate section (Board, CPU, Devices) That's precisely our goal but don't hold your breath it might happens or not, I will transmit to them the willing on participate of the Openmoko community to improve the FOSS level status on the device ;) Something which the Android developers didnt manage to do either. Theire drivers are sooo ugly. This time, the development should start from our site. Linux shouldnt have only BIOS function, but should have the user and kernel space consequently separated. Lets do it on our own, an we are sure, that it will be respected. We can certainly do it better then proprietary enterprises and google. :) I agree too regards leviathan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community David Reyes Samblas Martinez http://www.tuxbrain.com Open ultraportable embedded solutions Openmoko, Openpandora, Arduino Hey, watch out!!! There's a linux in your pocket!!! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: kernel 2.6.3x?
On Tue, 10 Nov 2009 09:09:00 +0100 Jose Luis Perez Diez jl...@escomposlinux.org wrote: El Monday, 9 de November de 2009 19:05:04 arne anka va escriure: ... so, simple question: how's the state of the new kernel? anybody working on it? GTA02 boots mainline 2.6.32 and Lars is working on pending patches see http://article.gmane.org/gmane.comp.handhelds.openmoko.kernel/10406 Well my neo freerunner made a nice kernel panic when booting the 2.6.32 with a config that should have everything needed, (I even tried with the config file given in this reply http://article.gmane.org/gmane.comp.handhelds.openmoko.kernel/10407 ) so I really don't know... as for now I am on a custom andy-tracking kernel because I can't find another version source that boot on my neo... (I don't use openembedded I'm a I do it my way kind of guy ^^) Oh I found out that the 2.6.32_rc6 has an undefined reference to GTA02_GPIO_AMP_HP_IN something really bad because it never apprear anywhere else in the code (grep -R proved that) offending file is sound/soc/s3c24xx/neo1973_gta02_wm8753.c compiled with SND_S3C24XX_SOC_NEO1973_GTA02_WM8753=y I alsa found out that the compilation fails at link time if debug is not activated because of an undefined reference to printascii() (defined in assembly only when debug activated) function is called anyway in s3c_pm_dbg() which is called even if debug is deactivated) I don't know if I should post it on the official kernel mailinglist or not so I post it here. signature.asc Description: PGP signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WikiReader - first impressions
Not full but some replies, snip Annoyances: - it is impossible (for me at least) to take out the microSD card without using a tool (pliers or something). Why do I want to take it out? To actually show people the small size of a Wikipedia database. :-) Did you push down first? as in other uSD readers you have to push it down until you feel a click then it unbloks and a spring will pull out enough the card to ease taike it out Some things I haven't figured out yet: - how do I get another Wikipedia (for example the Norwegian one) onto a MicroSD card? Download the source code from http://github.com/wikireader/wikireader tools are there and instructions on how to create wikireaders files form a Wikipedia xml is in a quickguide on the doc directory. - how do I convert an e-book and put it onto a microSD card for the device? Right now you have to put this ebook in a mediawiki , and then export it to xml and run the process mentioned avobe. All in all - I really like this device. -- Regards, Torfinn Ingolfsen ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community David Reyes Samblas Martinez http://www.tuxbrain.com Open ultraportable embedded solutions Openmoko, Openpandora, Arduino Hey, watch out!!! There's a linux in your pocket!!! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Ideal screen rotation
On Tue, Nov 10, 2009 at 12:00:31AM +, Dave Ball wrote: Carsten Haitzler (The Rasterman) wrote: wm needs to track both and determine which one takes precedence based on policy and th en implement that rotation, if needed. policy is what a wm implements - that's the nature of the beast. that policy may be hard-coded in the wm or configuration for it. I've been looking at existing window properties [1] to try and understand the best way to do this. option1: New atoms in the _NET_WM_STATE property. - _NET_WM_STATE_LANDSCAPE - _NET_WM_STATE_PORTRAIT If neither is present for a given window, WM can choose (based on the accelerometers). Both present is an error - or could be defined as leave the window in it's current orientation. option2: New property. _NET_WM_ORIENTATION 0 = Either / WM decides 1 = Landscape 2 = Portrait There are two landscape positions and 2 portrait positions :) Rui ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Ideal screen rotation
Rui Miguel Silva Seabra wrote: On Tue, Nov 10, 2009 at 12:00:31AM +, Dave Ball wrote: option1: New atoms in the _NET_WM_STATE property. - _NET_WM_STATE_LANDSCAPE - _NET_WM_STATE_PORTRAIT If neither is present for a given window, WM can choose (based on the accelerometers). Both present is an error - or could be defined as leave the window in it's current orientation. option2: New property. _NET_WM_ORIENTATION 0 = Either / WM decides 1 = Landscape 2 = Portrait There are two landscape positions and 2 portrait positions :) Doh - of course! Which would lead to: _NET_WM_STATE_ORIENTATION_LANDSCAPE _NET_WM_STATE_ORIENTATION_PORTRAIT _NET_WM_STATE_ORIENTATION_INVERTED or _NET_WM_ORIENTATION 0 = Either / WM decides 1 = Landscape 2 = Portrait 3 = Landscape inverted 4 = Portrait inverted However, what's the use-case for an application requesting either of the inverted states? I can't see when those would be useful - in terms of hints the app would supply. Obviously, if the WM was deciding orientation based on the device position, you would correctly rotate to the inverted states, but if an application is built for portrait or landscape is there any reason a developer would not want the normal portrait/landscape orientation for the device? Dave ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: kernel 2.6.3x?
Where can I download the kernel 2.6.3x? 2009/11/10 Abelenda diego.abele...@gmail.com On Tue, 10 Nov 2009 09:09:00 +0100 Jose Luis Perez Diez jl...@escomposlinux.org wrote: El Monday, 9 de November de 2009 19:05:04 arne anka va escriure: ... so, simple question: how's the state of the new kernel? anybody working on it? GTA02 boots mainline 2.6.32 and Lars is working on pending patches see http://article.gmane.org/gmane.comp.handhelds.openmoko.kernel/10406 Well my neo freerunner made a nice kernel panic when booting the 2.6.32 with a config that should have everything needed, (I even tried with the config file given in this reply http://article.gmane.org/gmane.comp.handhelds.openmoko.kernel/10407 ) so I really don't know... as for now I am on a custom andy-tracking kernel because I can't find another version source that boot on my neo... (I don't use openembedded I'm a I do it my way kind of guy ^^) Oh I found out that the 2.6.32_rc6 has an undefined reference to GTA02_GPIO_AMP_HP_IN something really bad because it never apprear anywhere else in the code (grep -R proved that) offending file is sound/soc/s3c24xx/neo1973_gta02_wm8753.c compiled with SND_S3C24XX_SOC_NEO1973_GTA02_WM8753=y I alsa found out that the compilation fails at link time if debug is not activated because of an undefined reference to printascii() (defined in assembly only when debug activated) function is called anyway in s3c_pm_dbg() which is called even if debug is deactivated) I don't know if I should post it on the official kernel mailinglist or not so I post it here. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- A.A. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Ericsson releases free cell-id lookup API
Agree, as far as I know, there is no way to most on the device to access to these informations. What I know is that now Google Map use frequently location provided by operators (and not by their own database). On the operator side, you can have a better location than just the cell because the networks also knows the neighbouring cells and other parameters, but this require changes or new equipement in the network, which is costly. 2009/11/3 jeanmatthew jeanmatthewjohns...@gmail.com: Are there any devices that supports access to these measures? To do any kind of combination you still need to extract all of the data from the device and send to the server. Google doesn't have access to any kind of data from the network. Google Maps apps even on pre-android phones (Java Mobile Edition) have had access to cell-id via the various proprietary java interfaces (com.sonyericsson.net.cellid, net.rim.device.api.system.GPRSInfo.getCellInfo().getCellId() on the blackberry etc). These interfaces are what allowed the OpenCellID project to exist before the freerunner was released. But are there any devices that support the reading of signal_strength and timing_advance from all neighbouring cells so that these can be supplied in the request to the Geolocation Network API? The proprietary interfaces I have seen only supports the cell you are currently registered to and not the neighbours. -- View this message in context: http://n2.nabble.com/Ericsson-releases-free-cell-id-lookup-API-tp3869908p3937224.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 -- Thomas LANDSPURG 8Motions Founder/CTO http://www.8motions.com http://www.opencellid.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[Om2008.9] symbol for battery and signal switched locations
Hello, Yesterday I realised that the two symbols in the upper right corner for status of battery and signal quality have switched their position, signal is now on the most right; first I could not believe this and compared it with older screen-shoots I have, but it is true; what could cause such a change/move? Thx matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WikiReader - first impressions
Hi Torfinn Really appreciate your feedback. My comments are inline: On Tue, Nov 10, 2009 at 5:48 AM, Torfinn Ingolfsen tin...@gmail.com wrote: Hello, After a few days with the WikiReader, here are my first impressions: The obvious things: - good size: this device is small enough to drag along (ok, it won't fit in my trouser pockets), but has a big enough screen to read on comfortably - use in places: I knew about the missing backlight. I can read the WikiReader while commuting (most tram's have good lighting), but on the other hand it is difficult in a cosy cafe, because the lighting is not s good there. - scrolling: this works great, even better than I thought. One friend asked: how do I get to the next page, but was happy with scrolling after I told him to use that instead. Are you running the latest kernel? (The way to tell is if you have kinetic scrolling, yes == latest kernel) http://cloud.github.com/downloads/wikireader/wikireader/kernel-2009-10-30.zip Scrolling is really really good there. - history: it's there when I turn on the device - and I like that. - the search button removes the on screen keyboard so I can scroll on the search screen. Yes! I like that. That's another fun random like way of searching. The questions: - search screen: where is the delete word and start over button? (this was the first question I got from two friends trying the device) You can hold down the backspace key. It will delete the word extremely fast. We're working on a few minor UI changes for the next release. Clear will be more obvious. - why isn't there a back button? Sure, I can use the history button and select from the list (and that works quite well), but a back button would save one keypress We didn't want to add another button. We might use left to right swipes in a later release. Not sure yet... Annoyances: - it is impossible (for me at least) to take out the microSD card without using a tool (pliers or something). Why do I want to take it out? To actually show people the small size of a Wikipedia database. :-) Push it in and it will pop out (beware it will *really* pop sometimes) - the buttons on the on screen keyboard is a bit small for my fingers (it is easy to press the character left or right of the one I want). I don't know how to solve this yet. Software. If you've used an iPhone, the keypad is 70% of WikiReader's size. And typing is a lot better. So just bear with us. We're working on this big time. - sometimes, the history screen is unresponsible, I have to press the other two buttons a couple of times before I can select anything on the history screen Working on this, too... small annoyances: - the moment it takes to display an article (after selecting it, either from the search screen or from a link) is just long enough that the device feels a bit slow sometimes. Same as my last comment :) Some things I haven't figured out yet: - how do I get another Wikipedia (for example the Norwegian one) onto a MicroSD card? - how do I convert an e-book and put it onto a microSD card for the device? Like David said, we encourage you to check out github.com/wikireader for now. All in all - I really like this device. Great. We love to hear this! -Sean ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SIP Client
On Monday 09 November 2009, Eric Smith wrote: Hi I have not used my freerunnner much since I bought it soon after public launch due to battery issues. Recently flashed the latest unstable SHR and initially looked reliable and promising as a regular phone. But then I experienced missed calls and failure to dial. (perhaps I will try Qt Extended Improved to see if this works better as a regular phone) But I know there is a lot of new work on SHR and I hope that it allow me to have a reliable regular phone. Meanwhile, I want to use the freerunner as a WIFI connected SIP client. No need to make cellular calls or do *anything* else than VOIP. Your battery won't last long in this case because you can't suspend and still receive calls. You could save a bit of battery by turning off the GSM though. What is the advice on both the platform and application above it to reliably support WIFI and a sip client? I see linphone is mentioned in this forum. linphone worked for me a while back, but would need some work to make it usable. The main problem is the lack of alsa scenario switching between ring and call. The gui could be made more suitable for a handheld device too. I do have a problem with batterys not charging well and discharging fast, maybe some distributions fix this? I don't have any problem with battery on shr-u, but we may just have different expectations. Thanks for suggestions. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2008.9] symbol for battery and signal switched locations
El Tuesday, 10 de November de 2009 15:19:08 Matthias Apitz va escriure: Hello, Yesterday I realised that the two symbols in the upper right corner for status of battery and signal quality have switched their position, signal is now on the most right; first I could not believe this and compared it with older screen-shoots I have, but it is true; what could cause such a change/move? Press on the icon for second and you can drag it ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Ideal screen rotation
perhaps the landscape / portrait flag should just contrain the rotation? So if you flip the phone 180 degrees, you get the 'expected' behaviour, but if you just flip it 90 degrees nothing changes? Warren On Tue, Nov 10, 2009 at 7:08 AM, Dave Ball openm...@underhand.org wrote: Rui Miguel Silva Seabra wrote: On Tue, Nov 10, 2009 at 12:00:31AM +, Dave Ball wrote: option1: New atoms in the _NET_WM_STATE property. - _NET_WM_STATE_LANDSCAPE - _NET_WM_STATE_PORTRAIT If neither is present for a given window, WM can choose (based on the accelerometers). Both present is an error - or could be defined as leave the window in it's current orientation. option2: New property. _NET_WM_ORIENTATION 0 = Either / WM decides 1 = Landscape 2 = Portrait There are two landscape positions and 2 portrait positions :) Doh - of course! Which would lead to: _NET_WM_STATE_ORIENTATION_LANDSCAPE _NET_WM_STATE_ORIENTATION_PORTRAIT _NET_WM_STATE_ORIENTATION_INVERTED or _NET_WM_ORIENTATION 0 = Either / WM decides 1 = Landscape 2 = Portrait 3 = Landscape inverted 4 = Portrait inverted However, what's the use-case for an application requesting either of the inverted states? I can't see when those would be useful - in terms of hints the app would supply. Obviously, if the WM was deciding orientation based on the device position, you would correctly rotate to the inverted states, but if an application is built for portrait or landscape is there any reason a developer would not want the normal portrait/landscape orientation for the device? Dave ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WikiReader - first impressions
Hi Sean, I was playing around a bit with the sources on github lately. I have stumbled over some issues. I know I can go to c...@thewikireader.com (and I will) But I guess we should have a mailing list for software aspects of WikiReader... Just a thought. :) Sean Moss-Pultz wrote: Hi Torfinn Really appreciate your feedback. My comments are inline: On Tue, Nov 10, 2009 at 5:48 AM, Torfinn Ingolfsen tin...@gmail.com wrote: Hello, After a few days with the WikiReader, here are my first impressions: The obvious things: - good size: this device is small enough to drag along (ok, it won't fit in my trouser pockets), but has a big enough screen to read on comfortably - use in places: I knew about the missing backlight. I can read the WikiReader while commuting (most tram's have good lighting), but on the other hand it is difficult in a cosy cafe, because the lighting is not s good there. - scrolling: this works great, even better than I thought. One friend asked: how do I get to the next page, but was happy with scrolling after I told him to use that instead. Are you running the latest kernel? (The way to tell is if you have kinetic scrolling, yes == latest kernel) http://cloud.github.com/downloads/wikireader/wikireader/kernel-2009-10-30.zip Scrolling is really really good there. - history: it's there when I turn on the device - and I like that. - the search button removes the on screen keyboard so I can scroll on the search screen. Yes! I like that. That's another fun random like way of searching. The questions: - search screen: where is the delete word and start over button? (this was the first question I got from two friends trying the device) You can hold down the backspace key. It will delete the word extremely fast. We're working on a few minor UI changes for the next release. Clear will be more obvious. - why isn't there a back button? Sure, I can use the history button and select from the list (and that works quite well), but a back button would save one keypress We didn't want to add another button. We might use left to right swipes in a later release. Not sure yet... Annoyances: - it is impossible (for me at least) to take out the microSD card without using a tool (pliers or something). Why do I want to take it out? To actually show people the small size of a Wikipedia database. :-) Push it in and it will pop out (beware it will *really* pop sometimes) - the buttons on the on screen keyboard is a bit small for my fingers (it is easy to press the character left or right of the one I want). I don't know how to solve this yet. Software. If you've used an iPhone, the keypad is 70% of WikiReader's size. And typing is a lot better. So just bear with us. We're working on this big time. - sometimes, the history screen is unresponsible, I have to press the other two buttons a couple of times before I can select anything on the history screen Working on this, too... small annoyances: - the moment it takes to display an article (after selecting it, either from the search screen or from a link) is just long enough that the device feels a bit slow sometimes. Same as my last comment :) Some things I haven't figured out yet: - how do I get another Wikipedia (for example the Norwegian one) onto a MicroSD card? - how do I convert an e-book and put it onto a microSD card for the device? Like David said, we encourage you to check out github.com/wikireader for now. All in all - I really like this device. Great. We love to hear this! -Sean ___ 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: Ideal screen rotation
Warren Baird wrote: perhaps the landscape / portrait flag should just contrain the rotation? So if you flip the phone 180 degrees, you get the 'expected' behaviour, but if you just flip it 90 degrees nothing changes? Given that these properties are for the orientation an application requests (to the WM) should ideally be used, I'm not sure how the actual rotation would help? Working from rotation would also complicate the behaviour on devices that are normally landscape - such as the Nokia N900. What I'm suggesting is that the application just says landscape or portrait, and then the WM would decide the most appropriate way to orient the screen for that device. If an application doesn't request either landscape or portrait, then the WM would rotate the screen according to the device orientation, through each of the positions the device could be held (including inverted). So the WM definitely needs to know the actual orientation of the device (such as from the FSO api), but I think the application itself only needs to request Landscape, Portrait or neither. Dave ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SIP Client
Al Johnson openm...@mazikeen.demon.co.uk writes: On Monday 09 November 2009, Eric Smith wrote: Meanwhile, I want to use the freerunner as a WIFI connected SIP client. No need to make cellular calls or do *anything* else than VOIP. Your battery won't last long in this case because you can't suspend and still receive calls. You could save a bit of battery by turning off the GSM though. I suspect that it's possible to utilize wake-on-wifi capability but i've not tried it yet. Though hardware-wise everything needed seems to be there. Probably it's even enabled by default, you just need to disable suspending of s3c_mci and ar6000 drivers. -- 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: Ideal screen rotation
On Tue, Nov 10, 2009 at 12:08:06PM +, Dave Ball wrote: Rui Miguel Silva Seabra wrote: On Tue, Nov 10, 2009 at 12:00:31AM +, Dave Ball wrote: option1: New atoms in the _NET_WM_STATE property. - _NET_WM_STATE_LANDSCAPE - _NET_WM_STATE_PORTRAIT If neither is present for a given window, WM can choose (based on the accelerometers). Both present is an error - or could be defined as leave the window in it's current orientation. option2: New property. _NET_WM_ORIENTATION 0 = Either / WM decides 1 = Landscape 2 = Portrait There are two landscape positions and 2 portrait positions :) Doh - of course! Which would lead to: _NET_WM_STATE_ORIENTATION_LANDSCAPE _NET_WM_STATE_ORIENTATION_PORTRAIT _NET_WM_STATE_ORIENTATION_INVERTED or _NET_WM_ORIENTATION 0 = Either / WM decides 1 = Landscape 2 = Portrait 3 = Landscape inverted 4 = Portrait inverted However, what's the use-case for an application requesting either of the inverted states? I can't see when those would be useful - in terms of hints the app would supply. Obviously, if the WM was deciding orientation based on the device position, you would correctly rotate to the inverted states, but if an application is built for portrait or landscape is there any reason a developer would not want the normal portrait/landscape orientation for the device? Yes, certain devices may be better prepared (in terms of connectivity for power, usb, etc...) for one kind of landscape rather than the other. Rui ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SIP Client
On Tuesday 10 November 2009, Paul Fertser wrote: Al Johnson openm...@mazikeen.demon.co.uk writes: On Monday 09 November 2009, Eric Smith wrote: Meanwhile, I want to use the freerunner as a WIFI connected SIP client. No need to make cellular calls or do *anything* else than VOIP. Your battery won't last long in this case because you can't suspend and still receive calls. You could save a bit of battery by turning off the GSM though. I suspect that it's possible to utilize wake-on-wifi capability but i've not tried it yet. Though hardware-wise everything needed seems to be there. Probably it's even enabled by default, you just need to disable suspending of s3c_mci and ar6000 drivers. I had wondered if this might be possible. I've not looked at the idle time between packets to see whether we would get to spend a worthwhile time asleep though. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Ideal screen rotation
Rui Miguel Silva Seabra wrote: On Tue, Nov 10, 2009 at 12:08:06PM +, Dave Ball wrote: However, what's the use-case for an application requesting either of the inverted states? I can't see when those would be useful - in terms of hints the app would supply. Obviously, if the WM was deciding orientation based on the device position, you would correctly rotate to the inverted states, but if an application is built for portrait or landscape is there any reason a developer would not want the normal portrait/landscape orientation for the device? Yes, certain devices may be better prepared (in terms of connectivity for power, usb, etc...) for one kind of landscape rather than the other. Yup - although that would be at the device level rather than the application level. If the WM knows what the device's policy is, I can't see a situation where one app wants to be in landscape, and a different app wants to be in landscape inverted on the same device? Dave ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Ideal screen rotation
I meant that it should *constrain* the behaviour of rotation - more or less like omnewrotate behaves now, but skipping over the two 'incorrect' orientations. so if the app says 'landscape', it's still flip between xrandr -o 1 and xrandr -o 3 as you rotate the phone, but won't flip to xrandr -o 0 or xrandr -o 2. I don't think it will normally makes sense for an application to specficially request 'xrandr -o 3' - they will usually just want to be sure that they are displayed in portrait or landscape mode. I've been using epdfview a lot lately, and I'd love to be able to constrain it to only show up in landscape mode... Warren On Tue, Nov 10, 2009 at 11:11 AM, Dave Ball openm...@underhand.org wrote: Warren Baird wrote: perhaps the landscape / portrait flag should just contrain the rotation? So if you flip the phone 180 degrees, you get the 'expected' behaviour, but if you just flip it 90 degrees nothing changes? Given that these properties are for the orientation an application requests (to the WM) should ideally be used, I'm not sure how the actual rotation would help? Working from rotation would also complicate the behaviour on devices that are normally landscape - such as the Nokia N900. What I'm suggesting is that the application just says landscape or portrait, and then the WM would decide the most appropriate way to orient the screen for that device. If an application doesn't request either landscape or portrait, then the WM would rotate the screen according to the device orientation, through each of the positions the device could be held (including inverted). So the WM definitely needs to know the actual orientation of the device (such as from the FSO api), but I think the application itself only needs to request Landscape, Portrait or neither. Dave ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Ideal screen rotation
On Tue, Nov 10, 2009 at 05:15:54PM +, Dave Ball wrote: Rui Miguel Silva Seabra wrote: On Tue, Nov 10, 2009 at 12:08:06PM +, Dave Ball wrote: However, what's the use-case for an application requesting either of the inverted states? I can't see when those would be useful - in terms of hints the app would supply. Obviously, if the WM was deciding orientation based on the device position, you would correctly rotate to the inverted states, but if an application is built for portrait or landscape is there any reason a developer would not want the normal portrait/landscape orientation for the device? Yes, certain devices may be better prepared (in terms of connectivity for power, usb, etc...) for one kind of landscape rather than the other. Yup - although that would be at the device level rather than the application level. If the WM knows what the device's policy is, I can't see a situation where one app wants to be in landscape, and a different app wants to be in landscape inverted on the same device? If you want to standardize something, better be prepared for uses such as a device. For some reason xrandr allows different options rathen than just 3. 0 == normal 1 == turned left 2 == normal inverted 3 == turned right Now... on my laptop, landscape == 0 or 2, but on the Free Runner landscape = 1 or 3 Rui ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Ideal screen rotation
Warren Baird wrote: I meant that it should *constrain* the behaviour of rotation - more or less like omnewrotate behaves now, but skipping over the two 'incorrect' orientations. so if the app says 'landscape', it's still flip between xrandr -o 1 and xrandr -o 3 as you rotate the phone, but won't flip to xrandr -o 0 or xrandr -o 2. I don't think it will normally makes sense for an application to specficially request 'xrandr -o 3' - they will usually just want to be sure that they are displayed in portrait or landscape mode. ok, we can make that a policy decision in the WM, but the app only needs to specify portrait or landscape. Dave ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Some questions about android on Freerunner
I would like some suggestions on where to go, and wether I can export my google code svn history. Please let us know your conclusions :) Thanks, Rui On Tue, Nov 10, 2009 at 01:00:34PM -0500, Jim Ancona wrote: It appears that Google is actively blocking access to Google Code from Iran and several other countries. See their TOS: http://code.google.com/tos.html and these threads on their groups list: http://groups.google.com/group/google-code-hosting/search?group=google-code-hostingq=iran I'm the owner of the android-on-freerunner Google Code project. I will initiate a discussion about moving the project to another site on the a-o-f mailing list, http://groups.google.com/group/android-on-freerunner, which doesn't appear to be blocked. Jim On Mon, Nov 9, 2009 at 10:36 PM, Levy levy.santa...@gmail.com wrote: On Thu, Nov 5, 2009 at 14:12, Rui Miguel Silva Seabra If you prove me it's Google who's actively blocking Iran, then I will remove both omnewrotate and elmdentica from Google Code in protest. Nice, I would like to suggest the same for other Free projects! Best regards from a portuguese, Rui Best regards from a brazillian, Levy ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SIP Client
Al Johnson openm...@mazikeen.demon.co.uk writes: On Tuesday 10 November 2009, Paul Fertser wrote: Al Johnson openm...@mazikeen.demon.co.uk writes: On Monday 09 November 2009, Eric Smith wrote: Meanwhile, I want to use the freerunner as a WIFI connected SIP client. No need to make cellular calls or do *anything* else than VOIP. Your battery won't last long in this case because you can't suspend and still receive calls. You could save a bit of battery by turning off the GSM though. I suspect that it's possible to utilize wake-on-wifi capability but i've not tried it yet. Though hardware-wise everything needed seems to be there. Probably it's even enabled by default, you just need to disable suspending of s3c_mci and ar6000 drivers. I had wondered if this might be possible. I've not looked at the idle time between packets to see whether we would get to spend a worthwhile time asleep though. From my quick googling it looks like it's only SIP client that usually sends some kind of keep-alive; some registrars can do that too but it seems uncommon. -- 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: Ideal screen rotation
If you want to standardize something, better be prepared for uses such as a device. For some reason xrandr allows different options rathen than just 3. 0 == normal 1 == turned left 2 == normal inverted 3 == turned right Now... on my laptop, landscape == 0 or 2, but on the Free Runner landscape = 1 or 3 in my oppinion this is quite simple and contrary to carsten, i say: landscape := more broad than high portrait := more high than broad ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WikiReader - first impressions
Hi, On Tue, Nov 10, 2009 at 9:48 AM, David Reyes Samblas Martinez da...@tuxbrain.com wrote: Did you push down first? as in other uSD readers you have to push it down until you feel a click then it unbloks and a spring will pull out enough the card to ease taike it out Yes, I did push it down first - this is not the first microSD card I have used :-) Now, after a lot of practice, I can actually manage to get the card out using my fingernails. But it is very hard, because space is extremely tight in there. As a workaround, I have attached a bit of tape to the end of the microSD card, and bent it (the tape) upwards. This gives me a handle that I have the chance to get a grasp on. Download the source code from http://github.com/wikireader/wikireader tools are there and instructions on how to create wikireaders files form a Wikipedia xml is in a quickguide on the doc directory. Thanks for the info. -- Regards, Torfinn Ingolfsen ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Some questions about android on Freerunner
On Tue, Nov 10, 2009 at 1:22 PM, Rui Miguel Silva Seabra r...@1407.org wrote: I would like some suggestions on where to go, and wether I can export my google code svn history. Please let us know your conclusions :) Some resources I found: There's a comparison page at Wikipedia: http://en.wikipedia.org/wiki/Comparison_of_free_software_hosting_facilities There's an API for Google's Issues database: http://code.google.com/p/support/wiki/IssueTrackerAPI And the wiki content is in source control and can be exported, although syntax may be an issue. Jim Thanks, Rui On Tue, Nov 10, 2009 at 01:00:34PM -0500, Jim Ancona wrote: It appears that Google is actively blocking access to Google Code from Iran and several other countries. See their TOS: http://code.google.com/tos.html and these threads on their groups list: http://groups.google.com/group/google-code-hosting/search?group=google-code-hostingq=iran I'm the owner of the android-on-freerunner Google Code project. I will initiate a discussion about moving the project to another site on the a-o-f mailing list, http://groups.google.com/group/android-on-freerunner, which doesn't appear to be blocked. Jim On Mon, Nov 9, 2009 at 10:36 PM, Levy levy.santa...@gmail.com wrote: On Thu, Nov 5, 2009 at 14:12, Rui Miguel Silva Seabra If you prove me it's Google who's actively blocking Iran, then I will remove both omnewrotate and elmdentica from Google Code in protest. Nice, I would like to suggest the same for other Free projects! Best regards from a portuguese, Rui Best regards from a brazillian, Levy ___ 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: WikiReader - first impressions
Hi, On Tue, Nov 10, 2009 at 3:55 PM, Sean Moss-Pultz s...@openmoko.com wrote: Are you running the latest kernel? (The way to tell is if you have kinetic scrolling, yes == latest kernel) I am running whatever version the device was delivered with. It doesn't look like scrolling is kinetic. http://cloud.github.com/downloads/wikireader/wikireader/kernel-2009-10-30.zip Ah! I was looking around on the WikiReader web site for updates, I didn't think about github. Scrolling is really really good there. I'll get it and see if I can update my card. You can hold down the backspace key. It will delete the word extremely fast. We're working on a few minor UI changes for the next release. Clear will be more obvious I really hope you will implement a clear button - one button press is faster than holding down the backspace key, IMHO. We didn't want to add another button. We might use left to right swipes in a later release. Not sure yet... Swipes might work. It doesn't have to be a physical button - how about using a corner of the screen for that purpose? Not really sure it would work - if I am right handed, I will use the thumb of my right hand to scroll on the right side of the screen, and a button on the lower left corner of the screen wouldn't interfere. However, if a left handed person used the device, he or she might use the left side of the screen to scroll. Hmm, this idea needs more thinking. Annoyances: - it is impossible (for me at least) to take out the microSD card without using a tool (pliers or something). Why do I want to take it out? To actually show people the small size of a Wikipedia database. :-) Push it in and it will pop out (beware it will *really* pop sometimes) Not on mine. I have tried - it never pos out. I also tried shakking the device - no, the card doesn't want to come out. My workaround is a handle made of tape - see my other post. Without that, I need something that can grab the cardon the sides - my fingers / nails doesn't fit in there (ok, I can do it, but it takes almost a minute, and a lot of cursing :-) ). - the buttons on the on screen keyboard is a bit small for my fingers (it is easy to press the character left or right of the one I want). I don't know how to solve this yet. Software. If you've used an iPhone, the keypad is 70% of WikiReader's size. And typing is a lot better. So just bear with us. We're working on this big time. Cool. I never have used an iPhone - I have a FreeRunner (and a 1973). FWIW, I had this idea about the keyboard: if nothing else works, you could always split the keyboard in a left and a right half, and only show one half at a time (with a button to switch to the other half). Not ideal, but then the buttons could be almost twice as wide. Like David said, we encourage you to check out github.com/wikireader for now. I will do that. -- Regards, Torfinn Ingolfsen ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WikiReader - github problems?
On Tue, Nov 10, 2009 at 9:45 PM, Torfinn Ingolfsen tin...@gmail.com wrote: When I go to http://github.com/wikireader/wikireader (now, Tueday 10.11.2009, at 21:43 CET, I get: 404 Not Found Why is that? Aha - GitHub is Temporarily Offline. -- Regards, Torfinn ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WikiReader - github problems?
On Tue, 10 Nov 2009 21:45:30 +0100 Torfinn Ingolfsen tin...@gmail.com wrote: When I go to http://github.com/wikireader/wikireader (now, Tueday 10.11.2009, at 21:43 CET, I get: 404 Not Found Why is that? Nothing to worry about. See: http://twitter.com/github Tom -- Thomas White t...@bitwiz.org.uk ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WikiReader - github problems?
not problem to access here ... David Reyes Samblas Martinez http://www.tuxbrain.com Open ultraportable embedded solutions Openmoko, Openpandora, Arduino Hey, watch out!!! There's a linux in your pocket!!! 2009/11/10 Torfinn Ingolfsen tin...@gmail.com: When I go to http://github.com/wikireader/wikireader (now, Tueday 10.11.2009, at 21:43 CET, I get: 404 Not Found Why is that? -- Regards, Torfinn Ingolfsen ___ 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: SIP Client
2009/11/10 Paul Fertser fercer...@gmail.com: Al Johnson openm...@mazikeen.demon.co.uk writes: I had wondered if this might be possible. I've not looked at the idle time between packets to see whether we would get to spend a worthwhile time asleep though. From my quick googling it looks like it's only SIP client that usually sends some kind of keep-alive; some registrars can do that too but it seems uncommon. If you're suggesting a client/server distinction here, I think that's false: most SIP phones want both to call out and to be called. Keepalives are used to keep firewall/NAT pinholes open, so whether they're needed depends on whether the phone is in a private or public network. At home would usually mean private and so require keepalives. That said, the standards are still in flux and there are different possible solutions. I guess what really matters here is what linphone does, since being in a private network must be its mainline scenario, and I'm afraid I don't know that. Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
WikiReader - github problems?
When I go to http://github.com/wikireader/wikireader (now, Tueday 10.11.2009, at 21:43 CET, I get: 404 Not Found Why is that? -- Regards, Torfinn Ingolfsen ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Ideal screen rotation
2009/11/10 Warren Baird wjba...@alumni.uwaterloo.ca: I meant that it should *constrain* the behaviour of rotation - more or less like omnewrotate behaves now, but skipping over the two 'incorrect' orientations. so if the app says 'landscape', it's still flip between xrandr -o 1 and xrandr -o 3 as you rotate the phone, but won't flip to xrandr -o 0 or xrandr -o 2. I don't think it will normally makes sense for an application to specficially request 'xrandr -o 3' - they will usually just want to be sure that they are displayed in portrait or landscape mode. This subtlety hadn't occurred to me before, but I actually have a use case for it! I have an in-car phone holder that happens to work better with the phone upside down, so that the USB connection can be on the left. So yes, it would be better if a prefers-portrait app (like tangogps) could be shown in either -o 0 or -o 2, depending on actual phone position. Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SIP Client
On Mon, Nov 9, 2009 at 10:14 PM, Eric Smith e...@fruitcom.com wrote: [...] Meanwhile, I want to use the freerunner as a WIFI connected SIP client. No need to make cellular calls or do *anything* else than VOIP. There are some softwares not adapted for the freerunner GUI, but an upcoming one is very promising, it's name is apathy, the SIP support is on the road, you may contact developers to know about their roadmap. Niko ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[SHR-U] Neomis - a computer version of the electronic game Simon
Hi, Neomis is a computer version of the well-known electronic game named Simon. It's a game of memory and concentration. You must follow the pattern of sounds and lights as long as you can remember! The game will flash quadrants in turn and expect you to repeat the sequence. If you get the sequence correct, the game will respond with a longer sequence. It's written in Python / Elementary. NumberX is tested on SHR unstable ONLY. Homepage : http://code.google.com/p/neomis/ Package : http://neomis.googlecode.com/files/neomis_1.0.0-r0_all.ipk Best Regards, -- Valéry ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SIP Client
On 10 Nov 2009, at 21:32, Nicola Mfb wrote: On Mon, Nov 9, 2009 at 10:14 PM, Eric Smith e...@fruitcom.com wrote: [...] Meanwhile, I want to use the freerunner as a WIFI connected SIP client. No need to make cellular calls or do *anything* else than VOIP. There are some softwares not adapted for the freerunner GUI, but an upcoming one is very promising, it's name is apathy, the SIP support is on the road... Google says: Did you mean: empathy sip client ? Stroller. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SIP Client
On Wed, Nov 11, 2009 at 1:06 AM, Stroller strol...@stellar.eclipse.co.uk wrote: [...] Google says: Did you mean: empathy sip client ? Sorry for missing the link. http://www.openapathy.org/ Niko ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SIP Client
On Wednesday 11 November 2009, Stroller wrote: On 10 Nov 2009, at 21:32, Nicola Mfb wrote: On Mon, Nov 9, 2009 at 10:14 PM, Eric Smith e...@fruitcom.com wrote: [...] Meanwhile, I want to use the freerunner as a WIFI connected SIP client. No need to make cellular calls or do *anything* else than VOIP. There are some softwares not adapted for the freerunner GUI, but an upcoming one is very promising, it's name is apathy, the SIP support is on the road... Google says: Did you mean: empathy sip client iirc apathy is a telepathy-based IM client optimised for the freerunner and similar devices. Empathy is a different telepathy-based client. Telepathy has SIP support that both could use. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Ideal screen rotation
On Tue, 10 Nov 2009 16:11:40 + Dave Ball openm...@underhand.org said: Warren Baird wrote: perhaps the landscape / portrait flag should just contrain the rotation? So if you flip the phone 180 degrees, you get the 'expected' behaviour, but if you just flip it 90 degrees nothing changes? Given that these properties are for the orientation an application requests (to the WM) should ideally be used, I'm not sure how the actual rotation would help? Working from rotation would also complicate the behaviour on devices that are normally landscape - such as the Nokia N900. What I'm suggesting is that the application just says landscape or portrait, and then the WM would decide the most appropriate way to orient the screen for that device. If an application doesn't request either landscape or portrait, then the WM would rotate the screen according to the device orientation, through each of the positions the device could be held (including inverted). So the WM definitely needs to know the actual orientation of the device (such as from the FSO api), but I think the application itself only needs to request Landscape, Portrait or neither. you want a bitmask for 4 rotations as well as flips. why? because this is what xrandr supports. you want to give a mask for which rotations the app wants why do u need both 90 and 270 degrees for example? look at a g1. u slide kbd open to one side of the screen. now imaging if u slid the screen the other way you have a different button set along the other side. eg a set of psp-style game-pad controllers for games. so games would request 270 and aps rthat are built for text input with hw kbd are 90. etc. etc. -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
