Fwd: [Gta04-owner] QtMoko status
Radek, this is very good news which deserves to be forwarded to the community list. Nikolaus Anfang der weitergeleiteten E-Mail: Von: Radek Polak pson...@seznam.cz Datum: 21. November 2011 18:54:21 MEZ An: List for communicating with real GTA04 owners gta04-ow...@goldelico.com Betreff: [Gta04-owner] QtMoko status Antwort an: List for communicating with real GTA04 owners gta04-ow...@goldelico.com Hi, yesterday i have finally stopped my wooden case attempts, put the GTA04 in my Freerunner's case and started working on software. The reason is that i would need better tools for the wooden case and i dont want to damage the GTA04 board or the display. QtMoko has now support for GTA04 keys, it can read battery (only in 60s intervals, polling has to be done yet), it can turn on/off backlight, it seems that the modem can receive SMS, read contacts and i could even make phone call (without sound yet). I found very helpful this page [1]. I will keep you updated. Regards Radek [1] http://projects.goldelico.com/p/gta04-kernel/doc/ ___ Gta04-owner mailing list gta04-ow...@goldelico.com http://lists.goldelico.com/mailman/listinfo/gta04-owner ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Fwd: [Gta04-owner] QtMoko status
Dnia 2011-11-22, wto o godzinie 09:08 +0100, Dr. H. Nikolaus Schaller pisze: Radek, this is very good news which deserves to be forwarded to the community list. [cut] that the modem can receive SMS, read contacts and i could even make phone call (without sound yet). Indeed, good news. I just hope Radek will stil find time to develop QtMoko for GTA02 :) -- Patryk LeadMan Benderz Linux Registered User #377521 () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Fwd: [Gta04-owner] QtMoko status
On 11/22/2011 12:00 PM, community-requ...@lists.openmoko.org wrote: Dnia 2011-11-22, wto o godzinie 09:08 +0100, Dr. H. Nikolaus Schaller pisze: Radek, this is very good news which deserves to be forwarded to the community list. [cut] that the modem can receive SMS, read contacts and i could even make phone call (without sound yet). Indeed, good news. I just hope Radek will stil find time to develop QtMoko for GTA02:) +1 :-) -- ## giacomo 'giotti' mariani gpg --keyserver pool.sks-keyservers.net --recv-key 0x99bfa859 O ASCII ribbon campaign: stop HTML mail www.asciiribbon.org ## ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Fwd: [Gta04-owner] QtMoko status
On Tuesday 22 November 2011 10:00:34 Patryk Benderz wrote: Dnia 2011-11-22, wto o godzinie 09:08 +0100, Dr. H. Nikolaus Schaller pisze: Radek, this is very good news which deserves to be forwarded to the community list. [cut] that the modem can receive SMS, read contacts and i could even make phone call (without sound yet). Indeed, good news. I just hope Radek will stil find time to develop QtMoko for GTA02 :) When using FS, one does not exclude the oter, does it? And in how far are developments in QtMoko device specific? Boudewijn ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Fwd: [Gta04-owner] QtMoko status
--- On Tue, 11/22/11, Patryk Benderz patryk.bend...@esp.pl wrote: Radek, this is very good news which deserves to be forwarded to the community list. [cut] that the modem can receive SMS, read contacts and i could even make phone call (without sound yet). Indeed, good news. I just hope Radek will stil find time to develop QtMoko for GTA02 :) hehe.. His work with qtmoko did me able to use my gta02 as phone for daily use. I read along different versions different contributions. So it is always a good idea to help to do qtmoko better :) (for all the gta02s around, or gta04, or whatever). Rafa ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[SHR] distro upgrade
Hello, I have been quite disconnected from the lists, but I have not found the subject. Thing is, I think it's been like half a year that I haven't been able to upgrade. opkg upgrade does nothing, like there was no new packages. But, looking in the net, I think that SHR is still on development, so I don't know if repos have changed or what. I use unstable SHR. I attach the files under /etc/opkg src/gz shr-all http://build.shr-project.org/shr-unstable/ipk//all arch all 1 arch any 6 arch noarch 11 arch arm 16 arch armv4 21 arch armv4t 26 arch om-gta02 31 src/gz shr-armv4 http://build.shr-project.org/shr-unstable/ipk//armv4 src/gz shr-armv4t http://build.shr-project.org/shr-unstable/ipk//armv4t src/gz shr-om-gta02 http://build.shr-project.org/shr-unstable/ipk//om-gta02 # Must have one or more source entries of the form: # # src src-name source-url # # and one or more destination entries of the form: # # dest dest-name target-path # # where src-name and dest-names are identifiers that # should match [a-zA-Z0-9._-]+, source-url should be a # URL that points to a directory containing a Familiar # Packages file, and target-path should be a directory # that exists on the target system. # Proxy Support #option http_proxy http://proxy.tld:3128 #option ftp_proxy http://proxy.tld:3128 #option proxy_username username #option proxy_password password # Enable GPGME signature # option check_signature 1 # Offline mode (for use in constructing flash images offline) #option offline_root target dest root / lists_dir ext /var/lib/opkg # We have whole /tmp in volatile tmpfs which is better than wear leveling NAND or uSD # But also bad for big upgrades where tmpfs eats whole memory, # device starts swapping (possibly using more NAND/uSD than temporary unpack) and then segfaults because of lack of space option tmp_dir /var/lib/opkg/tmp ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] distro upgrade
I guess they moved from http://build.shr-project.org/shr-unstable/ to http://build.shr-project.org/shr-core/ d On Tue, Nov 22, 2011 at 5:29 PM, ø fla...@member.fsf.org wrote: Hello, I have been quite disconnected from the lists, but I have not found the subject. Thing is, I think it's been like half a year that I haven't been able to upgrade. opkg upgrade does nothing, like there was no new packages. But, looking in the net, I think that SHR is still on development, so I don't know if repos have changed or what. I use unstable SHR. I attach the files under /etc/opkg ___ 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] distro upgrade
On 22.11.2011 17:29, ø wrote: Hello, I have been quite disconnected from the lists, but I have not found the subject. Thing is, I think it's been like half a year that I haven't been able to upgrade. opkg upgrade does nothing, like there was no new packages. But, looking in the net, I think that SHR is still on development, so I don't know if repos have changed or what. I use unstable SHR. I attach the files under /etc/opkg Hi, developement of SHR happens in the shr-core tree[1] these days. It's based on the new openembedded-core and Yocto Project efforts. Lukas [1] http://build.shr-project.org/shr-core/ signature.asc Description: OpenPGP digital signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Sharing TSM30 source
Hello Openmoko community, I am happy to announce that the archivists at Cryptome.org have added my contribution of the TSM30 source to their website collection: http://cryptome.org/tsm30/tsm30.7z The content inside is exactly the same as what I have, they have merely repackaged it from ISO to 7z format to make it more compact. The actual TSM30 firmware source (for both processors, i.e., both the Calypso and the TSM30's unknown other processor) is fully contained in the Official.zip file inside the 7z. The rest is the Windows development environment with which one can actually recompile the beastie. Unfortunately the latter is *not* simply ARM gcc/binutils under Cygwin, it appears to be some proprietary compiler toolchain native to the Windows culture. The build process is driven by DOS *.bat files, which then invoke some Windows version of make. The makefiles for the latter (usually of the *.mak form, DOS/Win-style) are mostly autogenerated from some IDE rather than human-written, and can be quite difficult to human-parse in some places. I haven't actually tested if that Windows dev env can fully recompile the source into flashable fw images. No Windows machines here, and no time to mess with wine or virtual machines or whatever. And even if it does successfully rebuild an fw image for the TSM30, what are we going to do with it? We want something that can run on GTA02 hw, not TSM30 hw, or at least I do... Making that TSM30 code truly useful would practically require porting it from TSM30 hw to some more reasonable Calypso phone platform, such as GTA02 or one of those really basic Calypso phones that OsmocomBB folks are hacking on, and converting the build process to the standard free software way while at it. However, that is much easier said than done. Given that this TSM30 src has originally been leaked and publicly posted back in 2004 (I assume that's well before Om) and has been on various mirror sites for years before various FUD forces had reduced it to a hard-to-find status, I assume that many people, including some here, have had copies of it, had been familiar with it and had studied the code extensively (out of sheer curiosity if nothing else) for quite some time, much longer than I have. Now that the booty is once again publicly available from a well- publicized location that is resistant to non-court-order-backed FUD-style takedown requests and we can discuss it in an open manner, perhaps someone who has been looking at this code for far longer than I have can post some comments regarding its overall architecture, some knowledge that would be helpful to those who might want to attempt porting it from TSM30 to GTA02? MS ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
I2C and GPS
For months now I have had poor performance with my Freerunner's GPS. The GPS problems did not seem to coincide with the two times I have opened my Freerunner to add I2C sensors. I have an infrared thermometer and a barometer. Lately I have missed the GPS enough to look into the issue more. After trying various things in software and messing with the GPS antenna, I started to look at my sensors. The reference schematics for both sensors call for a 100nf decoupling capacitor between ground and VDD. I looked around in my junk bin for some. All I could find were some huge (for the inside of a FR case) ceramic ones. They didn't seem to help. Using frameworkd.log with the log level turned up, I was able to watch the UBX packets as they came down and disconnecting SDA and SCL for both sensors gave an immediate improvement in GPS reception. I didn't notice a problem with reception when I first added the sensors. Was anything done in software that would make I2C cause more interference? Should I pursue the decoupling capacitors? Does it matter what kind if they are 100nf? Thanks for any ideas, Ben ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] distro upgrade
Hi, developement of SHR happens in the shr-core tree[1] these days. It's based on the new openembedded-core and Yocto Project efforts. Lukas [1] http://build.shr-project.org/shr-core/ Many thanks Lukas and Davide. You know if upgrade can be done by simply changing the repositories urls, or a reflash is needed? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
