Re: tangogps and qtmoko
On Thursday 12 May 2011 03:40:59 Robin Paulson wrote: On 12 May 2011 09:12, Tiago Bortoletto Vaz ti...@debian.org wrote: Try to use window manager in setup. I've added Matchbox also; you'll have the X top-right corner to close application. I've done the same to fix it in my device. It works well. Use fullscreen option in tango/foxtrot then you save the X space. thanks for the suggestions guys, that worked great. i've got a further problem now though: i can't get a gps fix. i've installed gpsd, and the port it pushes its data to is the same as the port tangogps looks on, but no go. i've left it outside in areas where i've previously got a good signal (with shr and other distros), so i'm sure it's the software. is there another component in the gps stack i need - there's nothing on the qtmoko or openmoko wiki about it You must indicate in gpsd config file the device to use or init it by profile QX file in tangogps/foxtrot entry. this is my /etc/default/gpsd content: # Default settings for gpsd. # Please do not edit this file directly - use `dpkg-reconfigure gpsd' to # change the options. START_DAEMON=true GPSD_OPTIONS= DEVICES=/dev/ttySAC1 USBAUTO=false GPSD_SOCKET=/var/run/gpsd.sock I get fix in few seconds. -- In the strict scientific sense we all feed on death -- even vegetarians. -- Spock, Wolf in the Fold, stardate 3615.4 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: tangogps and qtmoko
On Tuesday 10 May 2011 02:58:19 Robin Paulson wrote: hi, i have the latest qtmoko (35) installed on my freerunner. i also have tanggogps installed, used via QX. the problem is, when i run tango, it only uses 3/4 of the screen then, if i hit 'info' to show the config, etc., that takes up around a 1/3 of the screen, and can't be closed, plus i can't read all the info on the different tabs. i've tried 'rotate screen' in the qx setup for tango, but it doesn't rotate or make any difference at all. any suggestions? cheers Try to use window manager in setup. I've added Matchbox also; you'll have the X top-right corner to close application. -- War isn't a good life, but it's life. -- Kirk, A Private Little War, stardate 4211.8 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: strange problem with Intenso 4GB SDHC card
Alle 01:16, sabato 26 luglio 2008, Thomas B. ha scritto: 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 Any fix for this problem? I've made many test with a 4G SD. If use it for boot qtopia from vfat and ext2 partions it work fine. Slowly but fine. If I start system from 2007.2 in flash the mounted SD partitions give me many errors. Sometime was mounted 1st partion, sometime all of than. I've tried to access it in reading and writing and frequently I get I/O errors in dmesg. On time was loose partition table (in suspend/resume session). I've tried many partitions schemas (mixed FAT and ext2) but always I/O errors come. I've reformatted in a unique partition with FAT and I've filled in it about 1GB of maps for tangogps from my PC. The partition was mounted in /media/card and when tangogps start to read from SD some file was read good and many other not. The screen become full noised when SD is reading and get I/O errors. After the read go to end the screen come back showing fine. The 4GB SD with my PC work fine, no I/O errors. The 512M SD in FR package always work very well. The 4GB SD is a Apacer Micro SDHC 4GB Class 6. -- The sooner our happiness together begins, the longer it will last. -- Miramanee, The Paradise Syndrome, stardate 4842.6 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: receiving SMS messages
Alle 04:04, giovedì 7 agosto 2008, Robert William Hutton ha scritto: 5. In the meantime the network has accepted that the SMS can't be sent, and puts it into some kind of wait queue. Is not possible, after the GSM is fully up, say to the network I'm ready, is something waiting for me? -- We do not colonize. We conquer. We rule. There is no other way for us. -- Rojan, By Any Other Name, stardate 4657.5 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: receiving SMS messages
Alle 00:17, mercoledì 6 agosto 2008, Tim Coggins ha scritto: I can confirm this; it's been happening for the last week or so. Tim This is also for me. I use gtk and massages (not all) can be recived after hours or days. My TLC is Vodafone (italy) -- Romulan women are not like Vulcan females. We are not dedicated to pure logic and the sterility of non-emotion. -- Romulan Commander, The Enterprise Incident, stardate 5027.3 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: dfu-util upload problems
Alle 02:50, lunedì 21 luglio 2008, Kevin Squire ha scritto: At least one other person (you?) has indicated a similar problem at http://wiki.openmoko.org/wiki/Pre-Flash_Backup. Any ideas, anyone? Thanks, Kevin _ I've same problem. # ./dfu-util -a rootfs -R -U good-rootfs.jffs2 dfu-util - (C) 2007 by OpenMoko Inc. This program is Free Software and has ABSOLUTELY NO WARRANTY Opening USB Device 0x:0x... Claiming USB DFU Runtime Interface... Determining device status: state = appIDLE, status = 0 Device really in Runtime Mode, send DFU detach request... Resetting USB... Opening USB Device... Found Runtime: [0x1d50:0x5119] devnum=15, cfg=0, intf=0, alt=6, name=rootfs Claiming USB DFU Interface... Setting Alternate Setting ... Determining device status: state = dfuIDLE, status = 0 dfuIDLE, continuing Transfer Size = 0x1000 dfu_upload error -84 My system is: OpenSuse 10.2 over AMD Athlon XP -- Even historians fail to learn from history -- they repeat the same mistakes. -- John Gill, Patterns of Force, stardate 2534.7 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Cleared to start Mass production
Alle 17:12, giovedì 5 giugno 2008, steve ha scritto: The latest update I have from the factory indicates that mass Production ( that means running the SMT line without stopping to check stuff every two seconds) has been CLEARED TO START. So a switch is waiting only to be pushed on for make we mega - giga - tera - peta (and so on) happy? -- Immortality consists largely of boredom. -- Zefrem Cochrane, Metamorphosis, stardate 3219.8 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
