Re: Anti-Whining: Happy Moko Moments
rakshat hooja schrieb: You also asked for happy moments so when I palyed Duke Nukeem 3D with accelerometers on the Freerunner almost 8 months ago I was one happy person. It was my favourite game on my 486 when I was in school! I loved to be able to play Monkey Island and Day of the Tentacle on my Freerunner using ScummVM. Those were my favorite games of that time ;-) Regards, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: pidgin development version of glib and gtk requirements
Jeff Sadowski wrote: current pidgin development is talking about requiring a minimum of glib 2.12.0 and gtk 2.10.0 I'm wondering what versions of glib and gtk openmoko is on? Depends on the distro you are using; my SHR-unstable has glib 2.18.3 and gtk+ 2.14.2. Regards, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Debuzzing
Dr. H. Nikolaus Schaller schrieb: Dear community, it is the philisophy of Golden Delicious Computers to find solutions for important topics that the community has and can't solve alone. Therefore, we (Golden Delicious Computers and TRIsoft) have worked behind the scenes and are close to offer a Buzz rework solution that can in principle serve all Freerunner Owners in the EU harmonized market. This is great! I have a small question: My Freerunner has a full body InvisibleShield applied. Should I remove it from the Freerunner before sending it in, or can I leave it on? Regards, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
On Thu, Mar 05, 2009 at 01:19:07AM +0100, Fox Mulder wrote: Andy Green wrote: Johnny Tenfinger is right despite it sounds strange. On some or all A5s there is no base current limit resistor on the bipolar transistor used to light the AUX LED. This 50mA fault current then flows not through the LED (which has a reasonable series current limit resistor), but through the GPIO IO cell and the driver transistor base. If this is the problem than it really is a bad design flaw... Maybe i should test the AUX LED on my gta02v5 how much current it uses when it is on. Ouch. I just tested mine, and the AUX LED really uses that much (about 50mA). Does a SOP exist to fix this? Regards, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] network link down on windows after opkg update
On Mon, Dec 15, 2008 at 11:41:01AM +0100, KaZeR wrote: Hi everyone. I ran opkg update opkg upgrade this morning. I saw a new kernel was installed, so i rebooted the phone. After reboot, windows sees the usb device, but no link.. I'm currently not at home, so i only have access to a windows computer. Anything i could do to try to get back access to my FR? Anyone else has the same issue? Yep, had the same issue. I noticed that networking wasn't started at boot anymore after an okpg upgrade. Try to open the terminal on the FR and do ifup usb0 to bring up USB networking manually. I think the reason for this issue is a change in the initscripts. I fixed it by forcing an install of the package initscripts-shr as a replacement for initscripts (opkg hadn't done that automatically, because the difference in versioning made it look like a downgrade). HTH, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Changing layout of Qtopia predictive keyboard
On Sun, Nov 23, 2008 at 10:19:51PM +0100, Ivar Mossin wrote: Hello. I am wondering if and how it is possible to change the keyboard layout of the Qtopia predictive keyboard. I've tried to search around, but only find info on the Matchbox and Rasters Illume keyboard. I'm running 2008.testing. 1) How can I change the keyboard layout of the Qtopia predictive keyboard? I assume it is possible, I just didn't find out how yet. The layout can't be hardcoded in the source code, can it? Yes, it can: http://git.openmoko.org/?p=qtopia.git;a=blob;f=src/plugins/inputmethods/predictivekeyboard/predictivekeyboard.cpp;h=94ef081719d4a7af16e3f4e6dbc842031696ac9d;hb=master#l137 If it's not possible, the next question will be 2) How can I use Rasters Illume keyboard without using Illume theme as can be specified in /etc/enlightenment/default_profile? Hm, that I don't know. Regards, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Debian fails to boot after some reboots
On Fri, Sep 26, 2008 at 10:29:39AM +0200, Sven Bretfeld wrote: Hi list-members Craig B. Allen [EMAIL PROTECTED] writes: There are some workarounds that seem to prevent this from happening, but I don't know whether they apply to Qtopia. See http://docs.openmoko.org/trac/ticket/1802 Strange enough Qtopia seems to know that suspending is not good for the SD-card. I don't know why, but every time I have a working Debian system on the SD card, Qtopia refuses to suspend automatically (i.e. the powermanagement settings are ignored). After I forced the first suspend by 'apm -s', everything works like normal again. But then, the SD card's boot partition is corrupted. I guess what happens is that Qtopia starts scanning all the files on the SD card. It is designed to be run from internal flash with your MP3s on the SD card, so it scans all the files there and makes a database of them. With a Debian system on SD, this probably takes hours, and during that Qtopia probably refuses to suspend. You can turn this feature off in a file called Storage.conf lying around somewhere, IIRC. HTH, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD corruption(no suspend and sd_max_clk tested)
On Fri, Sep 19, 2008 at 03:53:36PM +0100, Andy Green wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | glamo3362 glamo3362.0: Glamo core now 49119232Hz CPU / 81887232Hz Memory) The kernel is not from the last week or so? It should have 89MHz PLLB on the Glamo now not 81MHz. The kernel in the Om2008.8 repository is built from git revision a1e97c611253511ffc2d8c45e3e6d6894fa03fa3 according to the package version, which is about 4 weeks old. Regards, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Two u-boots?
On Mon, Sep 15, 2008 at 09:28:10PM +0100, Linus Gasser wrote: Hello all, I tried a couple of different distros (ASU 2008.8, Debian, now FDOM) and have something strange: sometimes when powering on the device with Aux+Power (because most of the time the power-button alone only vibrates the phone shortly, but does nothing else), I get a u-boot from May 2008 (IIRC), and sometimes it's another one from August 2008. That's intended. See http://wiki.openmoko.org/wiki/Booting_the_Neo_FreeRunner HTH, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: FDOM updated
On Sat, Sep 13, 2008 at 01:04:09PM +0200, julien cubizolles wrote: Le samedi 13 septembre 2008 à 11:46 +0200, David Samblas a écrit : Any posibility to obtain the already compiled patched binary files? I asked this very question on the ticket page but didn't get an answer. Did you read the ticket? The searchbar patch is already in stable, it's just not enabled by default. See here for instructions on how to enable it: http://git.openmoko.org/?p=qtopia.git;a=commit;h=906a00fdcb89fdcc8252f84a76625eb42c8fe302 I just tried it, and it works for me. Regards, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Customized layout for illume keyboard
On Thu, Sep 11, 2008 at 11:19:35AM +0200, David Samblas wrote: This will be added to the future FDOM too :) Cool! :) I hope the FDOM users will find it useful. Regards, Thomas El jue, 11-09-2008 a las 02:17 +0200, Thomas B. escribió: On Thu, Sep 11, 2008 at 12:40:18AM +0100, Thomas White wrote: Thomas B. [EMAIL PROTECTED] wrote: I customized the layout of the illume Numbers keyboard a bit, and thought I'd share the result with the community. EXACTLY what I was looking for (and was about to have a go at creating myself). Many thanks! Glad that I could help! Regards, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Display of Images on GTA-02
On Wed, Sep 10, 2008 at 10:42:12AM -0400, Iain B. Findleton wrote: After doing some experiments which involve displaying an image on the screen of the GTA-02 I have the impression that things are unduly slow. The problem is to display a single image (jpg,png,gif) which is currently in a file on the root file system. Image size is 570 x 420 pixels in 32 bit color. It appears to take several (~10) seconds to read the image from the file and then display it on the screen. This is incredibly slow for a 400 MHZ machine and I am wondering if others have had similar experiences. Well, the performance of my Freerunner regularly breaks down because of [1]. Also [2] might be relevant for you. What does top say while the image is loading? Regards, Thomas [1] http://docs.openmoko.org/trac/ticket/1597 [2] http://docs.openmoko.org/trac/ticket/1315 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Customized layout for illume keyboard
Hi, I customized the layout of the illume Numbers keyboard a bit, and thought I'd share the result with the community. I love the illume keyboard, the only minor annoyance was that the keys in the Numbers layout were pretty small, so I had to fumble quite a bit when entering my PIN without a stylus. Also, I desperately needed an F5 key to be able to bring up the menu in ScummVM ;-) So, I basically split up the Numbers layout into two layouts: One contains only the numbers, allowing for more space for each key and thus improving finger-friendliness. The other one, called Symbols, is basically the original Numbers layout, but with a row of F-keys (including F5! :-)) instead of the numbers. I have attached my layouts: Extract the tarball in ~/.e/e (which will create a subdirectory keyboards), killall -HUP enlightenment and enjoy! Regards, Thomas keyboards.tar.gz Description: Binary data ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Customized layout for illume keyboard
On Thu, Sep 11, 2008 at 12:40:18AM +0100, Thomas White wrote: Thomas B. [EMAIL PROTECTED] wrote: I customized the layout of the illume Numbers keyboard a bit, and thought I'd share the result with the community. EXACTLY what I was looking for (and was about to have a go at creating myself). Many thanks! Glad that I could help! Regards, Thomas PS: I forgot to provide uninstallation instructions: In the case you or anyone trying this eventually finds that they don't like the layouts, getting rid of them is as easy as rm -rf ~/.e/e/keyboards; killall -HUP enlightenment (provided that you don't have your own custom layouts in there). Illume will then reload the default layouts from /usr/lib/enlightenment/modules/illume/keyboards. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: gsm log on my gta02 makes mention of gta01
On Tue, Sep 09, 2008 at 09:49:22AM -0500, Stephen Shelton wrote: I installed 2008.8 last night and GSM worked well immediately on boot. I did a number of things, particularly opkg update / opkg upgrade (although the latter output nothing). After rebooting, gsm ceased to work. I pull up it's log and keep seeing output attributed to a machine_gta01.c. Perhaps said code should work wight gta02, but regardless the gsm is not working. Here is my log file about 8 minutes into restarting gsm: Tue Sep 9 09:30:25 2008 6 log.c:106:gsmdlog_init() logfile successfully opened [...] ...and this pattern continues... Any hints would be appreciated. Do you have gsmd and qtopia-phone-x11 installed at the same time? The two packages are conflicting, because qtopia has its own GSM stack. So if this is the case, deinstall either one of them. HTH, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: gsm log on my gta02 makes mention of gta01
On Tue, Sep 09, 2008 at 02:51:38PM -0500, Stephen Shelton wrote: On Tue, 9 Sep 2008 20:42:13 +0200 Thomas B. [EMAIL PROTECTED] wrote: Do you have gsmd and qtopia-phone-x11 installed at the same time? The two packages are conflicting, because qtopia has its own GSM stack. So if this is the case, deinstall either one of them. This must be it. Which one is the default? I'm not sure if I installed gsmd implicitly, or if qtopia-phone-x11 was pulled in as a dependency. qtopia-phone-x11 is the default on OM2008.8. If the latter is true, this should be noted in the installer... http://docs.openmoko.org/trac/ticket/1827 Regards, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QTopia 4.3.2 resume on incomming SMS bug
On Sun, Aug 31, 2008 at 11:16:14AM +0200, Clemens Kirchgatterer wrote: Daniel Selinger [EMAIL PROTECTED] wrote: The only thing i recognized is, when receiving an sms while in suspend, the phone resumes, but doesn't notify me about an incoming sms, and when i go to the messaging app, there is nothing new in the inbox. In fact i know 'something' arrived, because the phone woke up from suspend. All messages which were received during suspend 'arrive' when the first sms comes in while the phone is awake. Sent 3 sms during suspend (always waited between until the phone suspended again), no alert. Wake the phone up manually, no alert. Send the first sms while awake. Phone alerts me that i have received 4 new sms messages. Maybe someone can tell me where to report bugs in the QTopia image. this sounds awully like: https://docs.openmoko.org/trac/ticket/1792 hope this helps. Sounds similar, but I doubt that it is the same issue, because #1792 was caused by an Openmoko specific patch to the Qtopia source, which probably isn't included in the original Qtopia. Anyway, a hint for diagnosing this problem is to get log data to see how and where it fails. I guess logging isn't enabled by default in Qtopia, but AFAIK it can be enabled by copying /opt/Qtopia/etc/default/Trolltech/Log.conf to ~/Settings/Trolltech/Log.conf and enabling some logging options there (in particular AtChat for the communication with the GSM modem). The logs can then be read with logread. HTH, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Om2008.8 - latest update - FR suspends after 30 secs - unconditionally
On Sun, Aug 31, 2008 at 02:46:05PM +0200, Torfinn Ingolfsen wrote: Hello, I just flashed my FreeRunner with the latest kernel and rootfs from Om2008.8 update[1]. Images dated August 31st, to be precise. After booting, I discovered that the FR suspends after 30 secs. No problem, I'll just go into settings and turn off suspend. But it doesn't work. No matter what I set suspend to, it always suspends after 30 secs (unless I continually tap the screen). I guess everybody understands how frustrating it is trying to work with a device that suspends every 30 secs. Since I don't have three hands, it is very difficult to to try to fix things via usb. I see from the support list that a couple of other people also have disovered this issue, but no solution. I tried looking at trac, but couldn't find anything. http://docs.openmoko.org/trac/ticket/1928 Please, any hints on how to fix this? Not yet, AFAIK. Regards, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ASU wifi gui
On Tue, Aug 26, 2008 at 02:28:15PM +0200, julien cubizolles wrote: Where does exposure store its wlan settings (WPA key mainly) ? For me it (or rather connman) created a config file in /var/lib/connman. Unfortunately, it is useless to me, as OM-Settings asks for a wireless password every time (even if it is already saved in that file), and I won't enter my huge random passphrase using the on-screen keyboard every time I want to connect to my WLAN. I'll check out mofi or something like that when I have time. Regards, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GSM registration still takes time - OM2008.08 with Zecke-testing
On Tue, Aug 26, 2008 at 08:52:24AM -0500, Alexey Kurochkin wrote: On Tue, 2008-08-26 at 13:19 +0200, Thomas B. wrote: You have both the dialer from OM2007.2 and the Qtopia dialer installed? Then that's probably why it takes so long for your phone to register to the network: OM-dialer depends on gsmd, but Qtopia has its own GSM stack, and the two are conflicting. So either remove Qtopia completely, or remove gsmd. Both dialers are in repos and I bet a lot of folks will install them not knowing that OM dialer really brakes things. That's what http://docs.openmoko.org/trac/ticket/1827 is for. I don't know what the progress there is, though. Regards, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: debugging qpe -- please help me to confirm
On Sun, Aug 10, 2008 at 10:47:53AM -0400, Yaroslav Halchenko wrote: It seems that many issues are linked to qpe shipped with 2008.2 thus it would be great if people know how to get valuable debug information I didn't install famous 2008.2 yeat so I am asking someone to confirm that this works (it came from irc chat with lpotter): cp /opt/Qtopia/etc/default/Trolltech/Log.conf ~/Settings/Trolltech and then you might enable some debug targets, /etc/init.d/qpe restart and see/dump logread into a file it should provide significant amount of information of what qpe is doing if that works on qpe -- craft a wiki page describing it or just confirm here and I will do that. Good idea. But I had a look into that file on my OM2008.8 and it looks like (nearly) all of the logging options are already enabled (see attachment). Maybe the OpenMoko developers already tweaked it for maximum logging? Regards, Thomas [Translation] File=QtopiaDefaults Context=Logging [ApplicationLauncher] Enabled = 1 Name[] = Application Execution Help[] = Application lifecycle management, from launching to termination. [ApplicationLayer] Enabled = 1 Name[] = Application Layer Help[] = Qtopia Value Space - application layer. [AtChat] Enabled = 1 Name[] = Modem AT communication Help[] = Communication between Qtopia and the Modem, in the form of AT commands and modem responses. Requires = CELL [Bluetooth] Enabled = 1 Name[] = Bluetooth Help[] = Anything to do with Bluetooth support. [Camera] enabled = 0 Name[] = Camera Help[] = Camera application. [CleanupWizard] enabled = 0 Name[] = Cleanup Wizard Help[] = Cleanup wizard activity. [DataLinking] Enabled = 1 Name[] = Data Linking (QDL) Help[] = Qtopia Data Linking (QDL) activities. [DataSharing] Enabled = 1 Name[] = Data Sharing (QDS) Help[] = Qtopia Data Sharing (QDS) activities. [DBUS] Enabled = 1 Name[] = DBUS Help[] = DBUS activity. [DocAPI] Enabled = 1 Name[] = Document system Help[] = Interactions with the document server. See also DRM. [DRMAgent] Enabled = 1 Name[] = DRM Help[] = DRM agent interactions. Requires = DRM [Hardware] Enabled = 1 Name[] = Hardware Help[] = Detailed logging of hardware messages. [Help] Enabled = 1 Name[] = Helpbrowser Help[] = Context-sensitive help interaction. [I18n] Enabled = 1 Name[] = Internationalization Help[] = Anything to do with alternative behaviours in different languages. [ILFramework] Enabled = 1 Name[] = IL Framework Help[] = Qtopia Integration Layer Framework activity. [IMAP] Enabled = 1 Name[] = IMAP Help[] = Verbose debugging of incoming email data from IMAP accounts. [Infrared] Enabled = 1 Name[] = Infrared Help[] = Infrared functionality. [IniLayer] Enabled = 1 Name[] = Ini Layer Help[] = Qtopia Value Space - Ini Layer. [Input] Enabled = 1 Name[] = Text input methods Help[] = Keypad and touchscreen plugins. [Media] Enabled = 1 Name[] = Multimedia Help[] = Media related functionality. [Messaging] Enabled = 1 Name[] = Messaging Help[] = Messaging activity. [Modem] Enabled = 1 Name[] = Modem Other Help[] = Modem activity other than I/O. Requires = CELL [ModemEmulator] Enabled = 1 Name[] = Modem Emulator Help[] = Modem emulator related functionality. Requires = CELL [Mux] Enabled = 1 Name[] = Modem Multiplexing Help[] = Detailed packet information for GSM 07.10 multiplexing. Requires = CELL [Network] Enabled = 1 Name[] = Networking Help[] = Network activity. [Obex] Enabled = 1 Name[] = OBEX Help[] = OBEX functionality. [Package] Enabled = 1 Name[] = Package Management Help[] = Package management activity. [Performance] Enabled = 1 Name[] = Performance Analysis Help[] = Performance logging of Qtopia Server and Applications. [POP] Enabled = 1 Name[] = POP Help[] = Verbose debugging of incoming email data from POP accounts. [PowerManagement] Enabled = 1 Name[] = Power Management Help[] = Power management activity. [QAudioInput] Enabled = 1 Name[] = Audio Input Help[] = ALSA Audio Input. [QAudioOutput] Enabled = 1 Name[] = Audio Output Help[] = ALSA Audio Output. [QSS] Enabled = 1 Name[] = Qtopia Sound Server Help[] = Qtopia Sound Server output activity. [Quicklauncher] Enabled = 1 Name[] = Quicklauncher Help[] = Quicklauncher spawning and application loading. [QtopiaServer] Enabled = 1 Name[] = Server Help[] = Qtopia Server tasks and startup. [Qtopiatest] Enabled = 1 Name[] = Qtopiatest Help[] = Qtopiatest plugin activity. [Resource] Enabled = 1 Name[] = Resource Lookup Help[] = Resource lookup information. [Services] Enabled = 1 Name[] = Services Help[] = General services activity. [SharedMemCache] Enabled = 1 Name[] = Shared Memory Cache Help[] = QSharedMemoryCache activity. [Sip] Enabled = 1 Name[] = Sip Help[] = Debug messages pertaining to SIP sessions. Requires = VOIP [SipAudioData] Enabled = 1 Name[] = Sip Audio Data Help[] = Verbose SIP debugging of incoming and outgoing audio data. Requires = VOIP [SMTP] Enabled = 1 Name[] = SMTP Help[] = Verbose debugging of outgoing
Re: debugging qpe -- please help me to confirm
On Sun, Aug 10, 2008 at 12:21:55PM -0400, Yaroslav Halchenko wrote: no -- the same was on qtopia -- but on OM it wasn't under ~/Settings/Trolltech right? so it wasn't yet enabled -- to enable it you need to copy it there afaik have you tried to copy it and see if logread gets populated with messages? :-) Ok, I've tried copying it there now. I don't know whether it makes a difference - it looks pretty much the same as before. There are actually lots of messages, though, e.g. lots of AtChat messages documenting the communication with the GSM modem. So maybe logging is really enabled by default on OM2008.8. Regards, Thomas On Sun, 10 Aug 2008, Thomas B. wrote: On Sun, Aug 10, 2008 at 10:47:53AM -0400, Yaroslav Halchenko wrote: It seems that many issues are linked to qpe shipped with 2008.2 thus it would be great if people know how to get valuable debug information I didn't install famous 2008.2 yeat so I am asking someone to confirm that this works (it came from irc chat with lpotter): cp /opt/Qtopia/etc/default/Trolltech/Log.conf ~/Settings/Trolltech and then you might enable some debug targets, /etc/init.d/qpe restart and see/dump logread into a file it should provide significant amount of information of what qpe is doing if that works on qpe -- craft a wiki page describing it or just confirm here and I will do that. Good idea. But I had a look into that file on my OM2008.8 and it looks like (nearly) all of the logging options are already enabled (see attachment). Maybe the OpenMoko developers already tweaked it for maximum logging? Regards, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: debugging qpe -- please help me to confirm
On Sun, Aug 10, 2008 at 01:50:10PM -0400, Yaroslav Halchenko wrote: did you restart qpe? (just wanted to make sure) I rebooted, so, yes. But anyway, with or without that file, I can't complain about a lack of debugging information at the moment, at least regarding GSM. The complete communication with the GSM modem is in the logs, which is often pretty informative. Regards, Thomas On Sun, 10 Aug 2008, Thomas B. wrote: On Sun, Aug 10, 2008 at 12:21:55PM -0400, Yaroslav Halchenko wrote: no -- the same was on qtopia -- but on OM it wasn't under ~/Settings/Trolltech right? so it wasn't yet enabled -- to enable it you need to copy it there afaik have you tried to copy it and see if logread gets populated with messages? :-) Ok, I've tried copying it there now. I don't know whether it makes a difference - it looks pretty much the same as before. There are actually lots of messages, though, e.g. lots of AtChat messages documenting the communication with the GSM modem. So maybe logging is really enabled by default on OM2008.8. Regards, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: receiving SMS messages
On Tue, Aug 05, 2008 at 09:36:08PM +0100, Dan Weatherill wrote: I recently received my freerunner, and am enjoying it so far! I have mainly been using the qtopia image from qtopia.net, but have been regularly updating my kernel from buildhost.openmoko.org. On doing some testing, I find the following: I can receive SMS messages perfectly whilst the phone is on, in qtopia. Not always so well in the GTK stack. If the phone is in standby, and I receive a text message, the phone wakes up but does not receive a text message. The person sending the message does, however, receive a delivery report. This occurs in both images as well. If I then subsequently receive a message after the others, whilst the phone is out of standby, I receive all the messages together. Hence, no messages are lost in the ether, but it seems that messages received whilst the phone is on standby are temporarily mislaid. If there is any information I can provide to help you sort this please just let me know. This is one of very few things preventing me using the neo as a day to day phone with qtopia. I observed this too, and filed a bug: https://docs.openmoko.org/trac/ticket/1792 Regards, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GPS problems, summary
On Thu, Jul 24, 2008 at 10:58:48PM -0700, Katrin Tomanek wrote: Hi, I am running the kernel from yesterday (uImage-2.6.24+git20080424-om-gta02.bin). Is the fix included in it or do I have to do anything else to get the software fix? Umm, 20080424 sounds more like April. I use [1], that one definitely has the fixes in it. Regards, Thomas [1] http://buildhost.openmoko.org/daily/freerunner/200807/20080725/uImage-2.6.24+git25+8533927964761f4e2078ccd8607b90f5acc60b93-r0-om-gta02.bin ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: strange problem with Intenso 4GB SDHC card
On Fri, Jul 25, 2008 at 11:44:37PM +0200, AVee wrote: On Friday 25 July 2008 10:54, arne anka wrote: i got a 4 gig card too (can't say if from intenso, have to check the wrapping). my card's boot sector is not erased but -- after a resume the card is mounted wrongly! fstab says as mountpoint /media/card and after booting that's where the card is. after suspend/resume the card (often) is mounted to /media/mmcblk1p1 instead -- thus every attempt to read from or write to the sd card goes to the built-in memory instead. I can confirm seeing the same behaviour with a Sandisk 8GB card... Me too (also Sandisk 8GB). It bit me while running Qtopia from SD card: Upon resuming the system crashed, probably because the rootfs was gone... I could reproduce this after having booted from flash. dmesg log of the suspend/resume cycle is attached. Regards, Thomas PM: Preparing system for mem sleep Freezing user space processes ... (elapsed 0.09 seconds) done. Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done. PM: Entering mem sleep Suspending console(s) pcf50633 0-0073: pcf50633_suspend glamo-mci glamo-mci.0: faking cmd 7 during suspend mmc_set_power(power_mode=0, vdd=0 glamo-mci glamo-mci.0: glamo_mci_set_ios: power down. gta02_udc_command(2) suspending dma channel 0 suspending dma channel 1 suspending dma channel 2 suspending dma channel 3 GSTATUS3 0x30376074 GSTATUS4 0x s3c2440-i2c s3c2440-i2c: slave address 0x10 s3c2440-i2c s3c2440-i2c: bus frequency set to 390 KHz gta02_udc_command(1) s3c2440-nand s3c2440-nand: Tacls=3, 30ns Twrph0=7 70ns, Twrph1=3 30ns not changing prescaler of PWM 3, since it's shared with timer4 (clock tick) timer_usec_ticks = 7864 timer tcon=00599109, tcnt a2c1, tcfg 0200,2000, usec 1eb8 mmc_set_power(power_mode=1, vdd=20 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 0kHz div=255 (req: 0kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: Error after cmd: 0x120 mmc0: card d555 removed MMC: killing requests for dead queue mmc_set_power(power_mode=0, vdd=0 glamo-mci glamo-mci.0: glamo_mci_set_ios: power down. mmc_set_power(power_mode=1, vdd=20 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 0kHz div=255 (req: 0kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: Error after cmd: 0x120 glamo-mci glamo-mci.0: Error after cmd: 0x8120 glamo-mci glamo-mci.0: Error after cmd: 0x120 glamo-mci glamo-mci.0: Error after cmd: 0x8120 glamo-mci glamo-mci.0: Error after cmd: 0x120 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 soc-audio soc-audio: scheduling resume work PM: Finishing wakeup. Restarting tasks ... 6soc-audio soc-audio: starting resume work glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 1kHz div=2 (req: 1kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 1kHz div=2 (req: 1kHz). Bus width=2 mmc0: new high speed SDHC card at address d555 mmcblk1: mmc0:d555 SU08G 7977472KiB mmcblk1: p1 p2 p3 done. soc-audio soc-audio: resume work completed dma2: channel has nothing loaded EXT2-fs error (device mmcblk1): ext2_check_descriptors: Block bitmap for group 0 not in group (block 0)! EXT2-fs: group descriptors corrupted! EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: pre-flash backup fails
On Sun, Jul 20, 2008 at 05:32:01PM -0700, Jim Morris wrote: I followed the directions here http://wiki.openmoko.org/wiki/Pre-Flash_Backup I could backup the kernel of my GTA02 but trying to use that method to backup the rootfs failed several times I had similar problems (see [1]), although I got error -84 most of the time instead of -110. Unfortunately, I never solved this problem. After several unsuccessful tries and no feedback from the list I gave up on this backup method. Does anyone else have ideas? Regards, Thomas [1] http://lists.openmoko.org/pipermail/community/2008-July/020707.html ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Different ways to boot an image?
On Tue, Jul 15, 2008 at 10:33:22AM -0400, John Reese wrote:
Thomas B. wrote:
I have also summarized my own experiences with booting Qtopia from a SD
card here:
http://lists.openmoko.org/pipermail/community/2008-July/021524.html
How do you set up / use the u-boot console over usb? Is there a wiki
page on how to do that? I'd really love to get my FR dual-booting, but
the ext2/ext3 issue is what's stopping me...
Yep, there's a wiki page:
http://wiki.openmoko.org/wiki/Bootloader#Bootloader_prompt
Bootloader commands are described here:
http://wiki.openmoko.org/wiki/Bootloader_commands
The command I used to change the command sequence for booting from SD
card from NAND flash is (note that semicolons, dollar signs and curly
braces have to be escaped so that they are not interpreted right away...
actually I'm not sure about the curly braces, but it worked for me):
setenv menu_1 Boot from microSD (FAT+ext3): setenv bootargs \$\{bootargs_base\}
rootfstype=ext3 root=/dev/mmcblk0p2 rootdelay=5 \$\{mtdparts\} ro\; mmcinit\;
fatload mmc 1 0x3200 \$\{sd_image_name\}\; bootm 0x3200
Then do a printenv to check whether everything is right, and if it is,
do saveenv.
HTH,
Thomas
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Different ways to boot an image?
On Mon, Jul 14, 2008 at 11:54:15AM -0700, Ken Restivo wrote: So far I've come up with this list of ways to boot: ... 3) From a rootfs and/or kernel image located on a FAT or EXT2 partition on the SD card (I don't remember where I saw this documented, and can't seem to find it now) You probably mean this page in the wiki: http://wiki.openmoko.org/wiki/Boot_from_sd_card I have also summarized my own experiences with booting Qtopia from a SD card here: http://lists.openmoko.org/pipermail/community/2008-July/021524.html Haven't tried any of the other boot options, yet. HTH, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [qtopia on freerunner] - What is the right place to discuss Qtopia on Openmoko?
On Tue, Jul 15, 2008 at 04:54:40AM +1000, Lorn Potter wrote: Kai Stian Olstad wrote: On Mon, Jul 14, 2008 at 9:27 AM, Lorn Potter [EMAIL PROTECTED] wrote: If anyone knows how to get a real battery status on the freerunner I can fix this up. I only know of /sys/devices/platform/bq27000-battery.0/power_supply/bat/status. Maybe that helps? not on my devices: [EMAIL PROTECTED]:~# cat /sys/devices/platform/bq27000-battery.0/power_supply/bat/status cat: read error: Timer expired On my device: [EMAIL PROTECTED]:~# cat /sys/devices/platform/bq27000-battery.0/power_supply/bat/status Charging hmm ok. so mine is a prototype hardware glitch. thats good to know. Hmm, maybe that thing isn't that reliable anyway... I just observed that it seems to oscillate between Charging and Discharging when the battery is nearly 100% full. Looking around in the /sys tree I found something else: /sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/chgstate It says enabled usb_present when charger is plugged in, and is empty when running from battery. I'm just guessing, though. Is there anyone here who can tell a reliable method to find out whether a charger is present or not on the Freerunner? Regards, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [qtopia on freerunner] - What files do I have to download?
Hi!
On Sun, Jul 13, 2008 at 04:40:09AM +0200, Cédric Berger wrote:
I would like to boot Qtopia from SD, but couldn't yet...
Can I do that with the image of Qtopia you mentioned ?
I extracted the files form the .jffs2 and copied them on the microSD card.
I then put the uImage bin in /boot
You have to put uImage.bin in a FAT partition... at least that's how
it's supposed to be when you use the default U-Boot environment. See
here:
http://wiki.openmoko.org/wiki/Boot_from_sd_card
I tried with SD card formated in ext3 and ext2.
It seems you have to use ext3 for the rootfs partition, because current
kernel builds have ext2 support only as a module (which is not yet
available before the rootfs is mounted).
Then I had the following problem: U-Boot told the kernel that the rootfs
was ext2, even if it was ext3, so the kernel couldn't mount it. I solved
that by logging in to the U-Boot console via USB and modifying the
command sequence to boot from SD so that it looks like this (I just
replaced ext2 with ext3):
menu_1=Boot from microSD (FAT+ext3): setenv bootargs ${bootargs_base}
rootfstype=ext3 root=/dev/mmcblk0p2 rootdelay=5 ${mtdparts} ro; mmcinit;
fatload mmc 1 0x3200 ${sd_image_name}; bootm 0x3200
Here you can also see that it expects the kernel to be on a FAT
partition (it uses the command fatload). Maybe that could be changed,
so that it reads the kernel from the ext2 or ext3 partition itself, but
I don't know which commands U-Boot supports.
HTH,
Thomas
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [qtopia on freerunner] - What is the right place to discuss Qtopia on Openmoko?
Hi! On Sat, Jul 12, 2008 at 06:48:41AM +1000, Lorn Potter wrote: Kevin Dean wrote: Plugging a Freerunner up via USB to a Debian system while running this image doesn't appear to charge. Is this a purely visual thing, or is Qtopia unable to charge a Freerunner? I'm assuming that since the other software can, this is a Qtopia thing? actually, it is an apm thing. apm battery status on the freerunner does not work correctly. I guess I need to back port a workaround from the 4.4. branch for at least showing when it is charging. I have a slightly different problem: The battery does get charged, but the screen doesn't dim or get switched off, although I told it to do that in the settings. That's a bit annoying, and it's probably not very healthy for the display, too. Is this also an apm problem, and can it be worked around? If anyone knows how to get a real battery status on the freerunner I can fix this up. I only know of /sys/devices/platform/bq27000-battery.0/power_supply/bat/status. Maybe that helps? Regards, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [qtopia on freerunner] - What is the right place to discuss Qtopia on Openmoko?
On Sun, Jul 13, 2008 at 10:16:01PM +0200, Thomas B. wrote: I have a slightly different problem: The battery does get charged, but the screen doesn't dim or get switched off, although I told it to do that in the settings. That's a bit annoying, and it's probably not very healthy for the display, too. Is this also an apm problem, and can it be worked around? I just noticed that there is already a newer Qtopia snapshot available for download than the one I have installed (mine is from Friday). I'd love to try that one out, maybe it solves my problem quoted above. Now my next question is: Is there a way to upgrade Qtopia to the new snapshot without losing my data (e.g. contacts and messages)? Backing up the data and writing it back after the upgrade would be fine, but I don't know where the data is stored. Regards, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First boot
On Sat, Jul 12, 2008 at 12:21:48PM +0200, Philippe Guillebert wrote: Contacts are read from the simcard all right, that was a nice surprise, didn't expect it to work so well. This is gonna sound dumb, but how do you slide the list views (like the contact list) on Openmoko ? It works somehow like this: http://wiki.openmoko.org/wiki/UI_Improvements#Kinetic_scrolling Basically, just slide the list up or down with your finger (or stylus). Regards, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [qtopia on freerunner] - What files do I have to download?
Hi! On Sat, Jul 12, 2008 at 02:32:10AM +, Clare wrote: Also please can you supply a root.tar.gz in addition to a root.jffs2? Obviously you can, I should have said Will you? please? (Or is there some way i can make .jffs2 into tar.gz?) I got the files out of that .jffs2 by following this guide: http://wiki.openmoko.org/wiki/Userspace_root_image#Mounting_the_JFFS2_image_on_a_loop_back_.28MTD_RAM.29_device I definitely agree that a .tar.gz would be much simpler, though. I need the files from the rootfs because I boot Qtopia off the SD card, not from internal flash, therefore I have to extract the files into an ext3 partition. A positive note: I installed Qtopia on my FreeRunner a few hours ago, and it seems to work really well. Good work, Lorn! Regards, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
dfu-util upload problems
Hi, I have a little problem with dfu-util and my new Freerunner. I thought I'd make a backup of my Neo's filesystem before flashing new images onto it, so I tried to use dfu-util in upload mode to transfer the content of the Neo's flash to my desktop PC. Backing up the kernel partition works, but when I back up the rootfs partition dfu-util transfers about 247MB and then dies with dfu_upload error -84, while the phone immediately reboots. It always dies at the same position, but I'm not sure whether the backup is complete or not. Further details: I've tried it on my desktop and on my laptop PC, with Ubuntu 7.10, Ubuntu 8.04 and a grml live-cd, with various dfu-util binaries and one built from SVN, but the error appeared every time. The phone was hooked up directly to the host (no hub or something), U-Boot version on the phone is the originally installed 1.3.2-moko12 from May 9. Any ideas what's wrong? Regards, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
