Re: U-Boot improvements? (Was: Qi - why only 3 partitions on SD card?)
El Friday, 25 de September de 2009 06:37:19 Dr. H. Nikolaus Schaller va escriure: Am 24.09.2009 um 22:44 schrieb Rask Ingemann Lambertsen: I tried to merge the two trees a couple of months ago, but the NAND flash code has changed so much that merging in the 2442 support requires knowledge of how the NAND flash interface works. I don't have that knowledge. Is this code somewhere available? I personally don't have the experience for the 2442 you mention, but others could be interested as well. http://git.openmoko.org/?p=u-boot.git;a=summary ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: U-Boot improvements? (Was: Qi - why only 3 partitions on SD card?)
Am 25.09.2009 um 08:46 schrieb Jose Luis Perez Diez: El Friday, 25 de September de 2009 06:37:19 Dr. H. Nikolaus Schaller va escriure: Am 24.09.2009 um 22:44 schrieb Rask Ingemann Lambertsen: I tried to merge the two trees a couple of months ago, but the NAND flash code has changed so much that merging in the 2442 support requires knowledge of how the NAND flash interface works. I don't have that knowledge. Is this code somewhere available? I personally don't have the experience for the 2442 you mention, but others could be interested as well. http://git.openmoko.org/?p=u-boot.git;a=summary Is there the merged tree Rask did mention? As far as I can see it is the OM fork and miles away from the 2009.08 u-boot. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Updated package for the puzzle collection
Aapo Rantalainen wrote: Looks nice. Release makefile in any place and put link to mailing list. 27 icons in desktop is way too much. (...) The author of BootAtor provides a script which checks if sortdesk is installed (only works with the latest version of sortdesk afaik) this script can easily be modified to check for version 0.2 of sortdesk and place the icons in the correct cetegory (i described how to use flaunch sortdsk 0.2 with the nEo theme on jmccloud.jm.funpic.de) some people are using it, i dunno if it is worth the work though. but what might be worth half an hour of script writing is to check if launcher is installed and add the games to the corresponding category, or at least lets th euser choose on install in which category the icons should be placed (very few lines of sqlite in the script). if this script accepts user input wether the icons shoudl be placed in a launcher category, udating will also work very well since the user can choose if he wants the icons to be placed in any launche category or not. if the user updates the games collection and simply chooses no nothign is changed in launcher sqlite database an everythign si still in order. i cannot really contribute myself, because the last time i worked with sql was some years ago and i currently use gprs to connect to teh internet and researchign would take ages. if nothign is doen within the next 4 weeks i could do it (i shoudl have broadband internet till then) this si just a suggestion that can be applied to any package. (or at least packages like oh-puzzles or metapackages which install lots of apps at once with lots of icons) or package a scrip in aseperate package, to categorize apps from commandline, which woudl be much faster than doing it in launcher if you have many icons that need the same category (note the last launcer version i used was 0.2 or something like that i dunno how user friendly categorizing has become since then) br ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Launcher - v 0.37 Release UPDATED (inbuilt contacts, sms and phonelog)
Hi, c_c wrote: I guess I could use text boxes - dont know if that would be significantly better. Probably the only thing that might be ok aould be a genlist. Anyhow, let me know if this binary helps. Thanks. Unfortunately, no. There is no more message like before, just Segmentation fault BTW, wouldn't my missing icons be related to that? ERROR: evas image: 0x174e18 has invalid fill size: 0x0. Ignored ERROR: evas image: 0x174e18 has invalid fill size: 0x0. Ignored ERROR: evas image: 0x174e18 has invalid fill size: 0x0. Ignored ERROR: evas image: 0x174e18 has invalid fill size: 0x0. Ignored I have no icons, even for recently sent/received messages. -- View this message in context: http://n2.nabble.com/Launcher-v-0-37-Release-UPDATED-inbuilt-contacts-sms-and-phonelog-tp3552019p3711448.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
[SHR-u] black screen of death on resume
Is anyone else noticing a black screen of death when pressing the power button for resume? This has been happening to me since I upgrade about a week ago. Yesterday I upgraded gain, but it seems to be the same. This is happening to me in an yet undeterminated way, but quite frequently, and regardless of status of NEW_FAIR_SLEEPERS It looks like off since there's no ssh, no screen light, etc... but if I keep the power button pressed for those magic 8 s then it power's off and I can thus start it again. It has already cost me loosing a few calls. Rui ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-u] black screen of death on resume
This has happened to me twice or so within the past week. I have no idea what's causing it. -Dan On Fri, Sep 25, 2009 at 9:45 AM, Rui Miguel Silva Seabra r...@1407.orgwrote: Is anyone else noticing a black screen of death when pressing the power button for resume? This has been happening to me since I upgrade about a week ago. Yesterday I upgraded gain, but it seems to be the same. This is happening to me in an yet undeterminated way, but quite frequently, and regardless of status of NEW_FAIR_SLEEPERS It looks like off since there's no ssh, no screen light, etc... but if I keep the power button pressed for those magic 8 s then it power's off and I can thus start it again. It has already cost me loosing a few calls. Rui ___ 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: [SHR-u] black screen of death on resume
I had it today, I missed a phone call. I don't know whether it was a bsod or it just didn't wake up from suspend. I heard the buzzing in my hi-fi from the modem, but the phone itself didn't react. 2009/9/25 Rui Miguel Silva Seabra r...@1407.org Is anyone else noticing a black screen of death when pressing the power button for resume? This has been happening to me since I upgrade about a week ago. Yesterday I upgraded gain, but it seems to be the same. This is happening to me in an yet undeterminated way, but quite frequently, and regardless of status of NEW_FAIR_SLEEPERS It looks like off since there's no ssh, no screen light, etc... but if I keep the power button pressed for those magic 8 s then it power's off and I can thus start it again. It has already cost me loosing a few calls. Rui ___ 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: Litephone 0.1
Hi, I have updated FSO in Debian recently. The current package in pkg-fso is still HEAD on git.freesmartphone.org. But I have not updated the FSO configuration package for GTA02 so far, so opimd is disabled by default. You can enable it by editing /etc/frameworkd.conf. The opimd section is supposed to look like this: [opimd] # set 1 to disable a module disable = 0 contacts_default_backend = CSV-Contacts messages_default_backend = SIM-Messages-FSO calls_default_backend = SQLite-Calls dates_default_backend = SQLite-Dates notes_default_backend = SQLite-Notes tasks_default_backend = SQLite-Tasks contacts_merging_enabled = 1 messages_default_folder = Unfiled messages_trash_folder = Trash sim_messages_default_folder = SMS rootdir = ../etc/freesmartphone/opim:/ etc/freesmartphone/opim:/usr/etc/freesmartphone/opim I will update config packages in the next week. The message would have been on pkg-fso-maint [1] by the way ;) [1] http://lists.alioth.debian.org/pipermail/pkg-fso-maint/2009-September/001940.html Excelent, thanks for the answer, Litephone works, I going to update the frameworkd, because litephone dont show the sim contacts and crash when I try create a new contact. -- http://nuevaeracr.blogspot.com Linux user number 478378 Linux machine number 386687 Tec. Esteban Monge Marín Tel: (506) 8379-3562 “No habrá manera de desarrollarnos y salir de la pobreza mientras los pocos negocios grandes de nuestro medio se entreguen a las economías foráneas y nosotros nos quedemos con solo negocios de pobre, mientras en vez de ser propietarios de nuestro propio país nos convirtamos en un ejército de empleados del exterior” José Figueres Ferrer, 1952. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Launcher - v 0.37 Release UPDATED (inbuilt contacts, sms and phonelog)
Ah, a new one :) I sent a message, and got : *** glibc detected *** launcher: corrupted double-linked list: 0x00328c28 *** This thread had 18 messages. By the way : - when deleting all the thread view should be closed, imo - when receiving a new message, the discussion view should be refreshed. Currently i have to close it and reopen it. -- View this message in context: http://n2.nabble.com/Launcher-v-0-37-Release-UPDATED-inbuilt-contacts-sms-and-phonelog-tp3552019p3712982.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: [all/fso?] external battery just mobile gum pro woes
Am Dienstag, den 22.09.2009, 15:05 +0200 schrieb Sebastian Krzyszkowiak: Charging from only 100mA explains oscillating. Check if sysfs paths in opp are up to date with your kernel. Unfortunatelly there is no dbus call in FSO for that yet. Add me a ticket and I'll do it when I'm back from holidays. Cheers, :M: ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [all/fso?] external battery just mobile gum pro woes
Did you set USB charge current to 500mA? If device which you are connecting can't ennumerate USB connection, Neo will charge with only 100mA No, it will try to charge with 1000 mA. This is a bug. well, didn't here, though the gum pro is capable of 1000mA output. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [all/fso?] external battery just mobile gum pro woes
Charging from only 100mA explains oscillating. Check if sysfs paths in opp are up to date with your kernel. Unfortunatelly there is no dbus call in FSO for that yet. Add me a ticket and I'll do it when I'm back from holidays. http://trac.freesmartphone.org/ticket/480 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-u] black screen of death on resume
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I get this every second day. I'm not sure, but I have the impression that it could be caused when gprs-connection is enabled. The last two tomes when it happened, i had opened a gprs-connection shortly bevor. Greetungs Bastian Rui Miguel Silva Seabra schrieb: Is anyone else noticing a black screen of death when pressing the power button for resume? This has been happening to me since I upgrade about a week ago. Yesterday I upgraded gain, but it seems to be the same. This is happening to me in an yet undeterminated way, but quite frequently, and regardless of status of NEW_FAIR_SLEEPERS It looks like off since there's no ssh, no screen light, etc... but if I keep the power button pressed for those magic 8 s then it power's off and I can thus start it again. It has already cost me loosing a few calls. Rui ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFKvPxjlYiDScJJ+7QRAui4AJ9stOt5rtEMuEfmfH8Dw0Nin1R+kQCgk7D5 bj8162XKr9CKjBEXhQWCg9g= =ToBN -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-u] black screen of death on resume
I don't have GPRS (for the obvious reason that 3.5€ / MB is robbery) and it happens to me sometimes after first suspend, sometimes after the second, third, fourth, whatever... Rui On Fri, Sep 25, 2009 at 07:22:44PM +0200, Bastian Muck wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I get this every second day. I'm not sure, but I have the impression that it could be caused when gprs-connection is enabled. The last two tomes when it happened, i had opened a gprs-connection shortly bevor. Greetungs Bastian Rui Miguel Silva Seabra schrieb: Is anyone else noticing a black screen of death when pressing the power button for resume? This has been happening to me since I upgrade about a week ago. Yesterday I upgraded gain, but it seems to be the same. This is happening to me in an yet undeterminated way, but quite frequently, and regardless of status of NEW_FAIR_SLEEPERS It looks like off since there's no ssh, no screen light, etc... but if I keep the power button pressed for those magic 8 s then it power's off and I can thus start it again. It has already cost me loosing a few calls. Rui ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFKvPxjlYiDScJJ+7QRAui4AJ9stOt5rtEMuEfmfH8Dw0Nin1R+kQCgk7D5 bj8162XKr9CKjBEXhQWCg9g= =ToBN -END PGP SIGNATURE- ___ 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: [all/fso?] external battery just mobile gum pro woes
On 9/24/09, Rask Ingemann Lambertsen ccc94...@vip.cybercity.dk wrote: On Tue, Sep 22, 2009 at 02:45:14PM +0200, Sebastian Krzyszkowiak wrote: Did you set USB charge current to 500mA? If device which you are connecting can't ennumerate USB connection, Neo will charge with only 100mA No, it will try to charge with 1000 mA. This is a bug. - and running system eats something about 200mA. Running what? It's charging with only 100mA here by default, and I need to switch it to 500mA when using dumb-charger. -- Sebastian Krzyszkowiak dos ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
HOWTO: Sharing SHR-U GPRS to *buntu laptop
Hi! I got some help at irc setting things up so I thougt I'd share it with you. I'm writing this on Konqueror on my eeepc in a moving train using the GPRS connection of Freerunner. So sharing GPRS from FR to *buntu, here we go: 1) make sure your GPRS on FR works. 2) on fr run opkg install iptables iptables-utils kernel-module-ipt-masquerade kernel-module-iptable-nat 3) create firewall.sh on freerunner, see http://wiki.openmoko.org/wiki/Tethering#Turning_your_FreeRunner_into_a_Network_Address_Translation_.28NAT.29_gateway 4) on *buntu, configure the GUI network manager to understand FR. I run Kubuntu Karmic Netbook remix with these settings: interface: eth2 ip: 192.168.0.202 subnet mask 255.255.255.0 gateway 192.168.0.200 dns: grap an IP address from FR's /etc/resolv.conf when using GPRS (=this is your service provider's dns..) 5) create a script like this on desktop: sudo route add default gw 192.168.0.202 sudo echo nameserver 62.241.198.246 /etc/resolv.conf sudo echo nameserver 62.241.198.245 /etc/resolv.conf Change the nameserver ip addresses to the addresses at /etc/resolv.conf on Freerunner Then: a) start GPRS b) connect USB c) run firewall.sh on freerunner d) run the other script on desktop DONE! I don't know why do I have to add the nameservers manually (why KDE doesn't do it..) or how to add the route automatically.. anyway, happy to surf now on laptop w. fr :) r ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [all/fso?] external battery just mobile gum pro woes
On Thu, Sep 24, 2009 at 10:55:48PM +0200, Rask Ingemann Lambertsen wrote: On Tue, Sep 22, 2009 at 02:45:14PM +0200, Sebastian Krzyszkowiak wrote: Did you set USB charge current to 500mA? If device which you are connecting can't ennumerate USB connection, Neo will charge with only 100mA Rask, Just run the Battery section from Settings and drag the slider from 100 to 500 :) Rui ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: HOWTO: Sharing SHR-U GPRS to *buntu laptop
On Fri, Sep 25, 2009 at 09:17:33PM +0300, Risto H. Kurppa wrote: I got some help at irc setting things up so I thougt I'd share it with you. Thanks for doing this. I have been looking for exactly such instructions. There is a wiki page entitled tethering with some of this info - perhaps you could add your guide there. Regards Jeff signature.asc Description: Digital signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Qi - why only 3 partitions on SD card?
Hi, On Fri, Sep 25, 2009 at 6:59 AM, Paul Fertser fercer...@gmail.com wrote: And in fact if anybody of those talking about bootmenu, multiboot and such really needed it he would have done it himself long time ago. I bet trying and tweaking all distros including Qtopia, Qtmoko, Android, H:1 etc etc took them 10x time required to build a minimal bootmenu. Well, this (statements like those above) is why the shoemaker's children is still running around barefoot. :-) (For those not catching the reference - the shoemaker can make shoes for his children at any time, he just never makes it a priority.) Developers and users have different views of what is required to make a device usable. Unless the developers recognize that, and produce something that the users find acceptable, the device in question will remain a gadget for developers. I had hopes that I would be able to use my FreeRunner as a user one day, heck I still have that hope. If that doesn't happen I (and probably a few others) will be a bit dissappointed. Hm, i have my normal one on uSD and in case i screw something up i just boot pre-installed 2007 from NAND by pressing AUX button at the right time (and yes, i can't manage it with 100% success rate but taking out the battery and trying again is not a big deal). Lucky you. I have tried the press AUX button trick a lot of times, I can _never_ make Qi boot anything other that the default (first) partition on my SD card. Like this: - I don't press anything, the default partition gets booted - I press AUX (hopefully at the right time), and Qi never finshes booting anything (not in 5 - 10 minutes anyway). Someone said that Qi is unusable by normal users. I wanted to prove it wrong. IMHO, you failed to prove anything. I still say that Qi is unusable for normal users - it doesn't have a reliable way for users to select which partition to boot. To a user, it might look like this: - U-boot wasn't working correctly with newer (bigger) kernels, so the developer(s) abandoned it - instead they created Qi to be newer, better, faster and so on - Qi isn't living up to promises for users I'm not saying that such a view is correct, but that is how it can look like from a users view. By derfinition, only developers can fix the software. Now, will any developer step up and fix Qi (or U-boot) so that it will be usable for users? If no developer wants to scratch that particular itch, the FreeRunner will remain a gadget for developers only. -- Regards, Torfinn Ingolfsen ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Qi - why only 3 partitions on SD card?
Torfinn Ingolfsen tin...@gmail.com writes: And in fact if anybody of those talking about bootmenu, multiboot and such really needed it he would have done it himself long time ago. I bet trying and tweaking all distros including Qtopia, Qtmoko, Android, H:1 etc etc took them 10x time required to build a minimal bootmenu. Developers and users have different views of what is required to make a device usable. Unless the developers recognize that, and produce something that the users find acceptable, the device in question will remain a gadget for developers. I'm not a dev. I don't maintain anything. And don't write anything. I'm just using FR as my only daily phone since November. Hm, i have my normal one on uSD and in case i screw something up i just boot pre-installed 2007 from NAND by pressing AUX button at the right time (and yes, i can't manage it with 100% success rate but taking out the battery and trying again is not a big deal). Lucky you. I have tried the press AUX button trick a lot of times, I can _never_ make Qi boot anything other that the default (first) partition on my SD card. Like this: - I don't press anything, the default partition gets booted - I press AUX (hopefully at the right time), and Qi never finshes booting anything (not in 5 - 10 minutes anyway). Why don't you add an additional delay or led blink to it to make it more explicit? Someone said that Qi is unusable by normal users. I wanted to prove it wrong. IMHO, you failed to prove anything. I still say that Qi is unusable for normal users - it doesn't have a reliable way for users to select which partition to boot. I'm not sure the majority of users really want it, there was no such poll. To a user, it might look like this: - U-boot wasn't working correctly with newer (bigger) kernels, so the developer(s) abandoned it False statement. - instead they created Qi to be newer, better, faster and so on Qi was created to have a minimal simple easily maintainable bootloader, take a look at coreboot project to understand the idea behind Qi. U-boot is just wrong for this kind of device: it's neverending porting of Linux drivers to u-boot which doesn't make much sense when you can boot Linux, the kernel directly. Qi is really simple and (almost) clean, and it can boot kernels. I don't understand why you think one should want to maintain huge and complex u-boot instead of small simple Qi. It boots kernels - good enough. KISS - Qi isn't living up to promises for users Qi is working almost bugfree. It does what was promised. If anyone with a debugboard or the simplest UART-whatever converter (i've just built one myself based on FT232R, damn simple; the same goes for MAX232 etc, it's not _that_ hard to find RS-232 even nowadays) can reproduce any bug with it, please report it on trac, i promise i will try to fix it. Lack of menu with initramfs says imho that nobody really needs it or else it would have been created long time ago. I'm not saying that such a view is correct, but that is how it can look like from a users view. I hope now i clarified it enough to explain why it's not correct. By derfinition, only developers can fix the software. It would be interesting to see this definition... Now, will any developer step up and fix Qi (or U-boot) so that it will be usable for users? If you're ok with initramfs solution (and i haven't yet seen a single point why it's not ok) then it seems it's not a matter of fixing Qi, rather a matter of implementing an initramfs menu... If no developer wants to scratch that particular itch, the FreeRunner will remain a gadget for developers only. Hehe, how scary ;) BTW, no offense meant, take it easy dude :) -- 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: HOWTO: Sharing SHR-U GPRS to *buntu laptop
Jeffrey Ratcliffe jeffrey.ratcli...@gmail.com writes: On Fri, Sep 25, 2009 at 09:17:33PM +0300, Risto H. Kurppa wrote: I got some help at irc setting things up so I thougt I'd share it with you. Thanks for doing this. I have been looking for exactly such instructions. There is a wiki page entitled tethering with some of this info - perhaps you could add your guide there. Perhaps knowledge about configuring networks in general and iptables in particular should be obtained from iptables manuals [1] rather than being spread in some weird hard-coded and sometimes plain wrong forms all over the internet including OM wiki? [1] http://iptables.org/documentation/index.html -- 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
OT: SIM contact limitations
Hello list, I am marking this message as OT because it is not specific to Openmoko, but I thought someone here may know because I think most members of this list are relatively technical. Anyway, why are SIM contacts (contacts stored on a SIM) so limited? 1. Cannot have multiple phone numbers per contact. 2. Cannot change the type (home, work, mobile, etc.) of the phone number. 3. Names are truncated to 18 chars. Why do I have to store contacts in the phone instead of on the SIM to do anything useful? Thanks, Brolin -- Sometimes I forget how to do small talk: http://xkcd.com/222/ “If you have to ask why, you’re not a member of the intended audience.” — Bob Zimbinski, http://webpages.mr.net/bobz/ttyquake/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
FreeRunner case + stylus holder (was Re: New case)
Dead thread resurrection time! :) 2009/6/19 David Ford da...@blue-labs.org to whomever does this, please put a small stylus into a recess in the new case :) I have been wondering why the FreeRunner has a resistive touch screen, which I prefer because I like the greater precision of a stylus than my finger, but lacks a stylus holder. My FreeRunner, which I ordered from SDG Systems, included a stylus, but I have to keep the stylus separate in my pants pocket because the FreeRunner lacks a stylus holder! I bought my FreeRunner to replace my Nokia 6103b cell phone, which has no touch screen, and my Palm Z22 PDA, which has a resistive touch screen and nice stylus holder but is not a phone. Because of my Palm Z22, I expected all devices with a resistive touch screen intended for use with a stylus to include a stylus holder, but the FreeRunner has no stylus holder! Why? PS: Instead of buying my Palm Z22 PDA, I now know it would have made more sense to buy a GSM phone to use as a PDA without cellular service so I could continue using a single device if I needed cellular service, but I did not think I needed cellular service when I bought my Palm Z22. I was actually not even sure if I would use the Palm Z22 as a PDA because I completed elementary/primary + high/secondary school with paper organisers, but I found a PDA far better than a paper organiser! :) And yes, I know it is strange how computers have been my primary interest and how I have spent most of my free time with computers since about grade 7 (or earlier), yet I did not use a PDA nor have a cell phone until after high school. :) I also loved playing driving games since I was 11 or younger, but did not get a driver’s licence nor learn to drive a real car until I was almost 19. I live in Canada, so I could have got a driver’s licence when I turned 16! (I assume the age to get a driver’s licence is the same in all of Canada? It is 16 in British Columbia, where I live.) Anyway, enough rambling. :P ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Launcher - v 0.37 Release UPDATED (inbuilt contacts, sms and phonelog)
Hi, Hmmm. There seems to be something odd here. The sms window _is_ closed when the Del All button is pressed (since the last three binaries). I've repacked the newer binary and icons as the latest package. Try this. I'm getting no glibc errors though the largest conversation I had was about 12 sms's. And I haven't yet got a SQL:library out of sequence error either. Can you tell me how many contacts/sms's you have in total? I must be missing something obvious. This newer version is faster because it doesn't delete and re-sync all the contacts every time. The settings window lets you sync contacts if you've changed something from another program and need to get launcher up to date. Changes * doesn't re-sync contacts every time * contacts can categorised * resync sms/contacts/calls from settings page * fixes bug where opim was not updated correctly for sms' sent/not sent http://n2.nabble.com/file/n3715862/launcher_0.38_arm.ipk launcher_0.38_arm.ipk -- View this message in context: http://n2.nabble.com/Launcher-v-0-37-Release-UPDATED-inbuilt-contacts-sms-and-phonelog-tp3552019p3715862.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: [qtmoko] battery level indicator
Jim Morris wrote: It looks like the battery indicator does not work, at least after a suspend, maybe these errors have something to do with it, they appear after coming out of the first suspend, after that the battery always looks full, unless its charging which does indicate. [ 814.75] Restarting tasks ... done. [ 814.87] bq27000-battery bq27000-battery.0: battery service reschedule failed [ 817.695000] pcf50633 0-0073: usb curlim to 500 mA [ 3254.28] HDQ error: 1 [ 3254.295000] HDQ responds again [ 3254.435000] power_supply battery: driver failed to report `temp' property [ 4977.83] HDQ error: 1 [ 4977.845000] HDQ responds again [ 5129.84] HDQ error: 1 [ 5129.855000] HDQ responds again [ 5129.995000] power_supply battery: driver failed to report `temp' property [ 5712.895000] HDQ error: 1 [ 5712.915000] power_supply battery: driver failed to report `voltage_now' property [ 5737.91] HDQ responds again [ 6929.315000] HDQ error: 1 [ 6929.33] HDQ responds again [ 7005.32] HDQ error: 1 [ 7005.335000] HDQ responds again [ 7005.585000] power_supply battery: driver failed to report `charge_full' property [ 7664.26] HDQ error: 1 [ 7664.275000] HDQ responds again [ 7664.52] power_supply battery: driver failed to report `charge_full' property Ok I have done some research, and the above messages do come from the kernel, but may be transient errors, and not affecting this bug. The battery indicator showing full when it should show 75% does not always happen, but after a few suspend/resume cycles I can make it happen. When it does happen I can cat /sys/class/power_supply/battery/capacity and get the correct answer of 75. but both the value space /Hardware/Accessories/QPowerSource/DefaultBattery/Charge (which is what the battery indicator uses) and the QPowerSource::capacity() calls return 100, which is obviously wrong. This points to a bug in QtMoko (actually Qt Extended). It is odd because tracing the calls they ultimately just read /sys/class/power_supply/battery/capacity, so I suspect the QPowerSource service is dying or something like that. I'll continue to track this down, as it is quite a serious bug. I also got a dialog pop up saying the battery was critically low, when in fact it was at 75%. -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Auto home revision 1.1
On Thu, Sep 24, 2009 at 11:36 PM, Torfinn Ingolfsen tin...@gmail.comwrote: Hi, On Thu, Sep 24, 2009 at 6:26 PM, RANJAN infi...@gmail.com wrote: Well,in time we will release it.We are doing this in the free time and after it is properly done we will put it in the applications page . Might I suggest release early, release often (Not my idea, but I like it) IMHO, providing the code to the general public as early as possible improves testing and feedback. +1 Rakshat ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
