From mychaela.falconia at gmail.com Tue Aug 8 21:27:42 2017 From: mychaela.falconia at gmail.com (Mychaela Falconia) Date: Tue, 8 Aug 2017 13:27:42 -0800 Subject: moko13-beta1 firmware release candidate for GTA01/02 Message-ID: Hello Om community, It has been a long time since the last official modem fw release for Openmoko GTA01/02 devices (leo2moko-r1 aka moko12 in late 2013), so I decided that it is time for moko13. The differences from moko11/12 are fairly minor, and mostly serve to bring the FreeRunner target up-to-date with the recent FC firmware developments which FreeCalypso users have already been enjoying on our own newly made FC modem hardware: * The binary blob version of L1 has been replaced with recompilation from our reconstructed TCS211 L1 C source. This change has a side effect of reverting the L1 patch from TI-Taiwan from 20080421 which was a stab-in-the-dark at the infamous bug #1024: L1 binary libs with this patch included were used in moko10, moko11 and moko12 releases, but when I was deblobbing L1 (reconstructing recompilable C source that fits exactly in the place of the original blobs), my reconstruction produced C source that compiles into an equivalent of the original 20070608 version (used in moko3 through moko8), rather than the patched 20080421 version. Because the patch in question did NOT fix or improve anything, was probably made as an experimental hack and was not on TI's internal mainline (as evidenced by not being present in the TCS3.2 L1 source for LoCosto), I have every reason to believe that this patch is unnecessary and that its removal will not cause any regressions. * When the Calypso is used as a basic modem like in the GTA0x, most of its peripheral interface signals are unused, and typically left unconnected in the hardware. Previous fw versions configured many of the unconnected GPIO and multifunction pins as inputs, resulting in floating inputs. Standard hw engineering wisdom says that floating inputs are generally bad. The new fw configures all unused and unconnected GPIOs as well as the unused and unconnected DSR_MODEM/LPG signal as outputs instead, eliminating the floating input situation. * In the process of deblobbing the init module a bogon was discovered (which existed in all previous fw versions) that configured the IO1 output (output, not input!) to also act as an interrupt source. This bogon has been removed. Changes visible only to developers who use the debug trace interface provided on the headset jack, and I mean use it to talk to the fw as it runs, rather than just for flashing: * An additional AT command channel is provided over RVTMUX, in addition to the standard one going to the phone's AP. This mechanism makes it possible to exercise the modem to a large extent from an external host with no working software on the FreeRunner itself except U-Boot. * The FFS access protocol has been changed from TMFFS1 to TMFFS2. The new protocol is supported by our fc-fsio GSM device file system manipulation utility, but some old Windows tools that must have been used by Openmoko (of which I never found a copy, thus it is not known for certain if this sw still exists anywhere at all or not) may stop working. * TI's GPF misfeature that suppressed the responses to "system primitive" commands has been fixed: if you send an sp command through fc-shell, you'll get the expected response as per GPF documentation. The developer features listed above have been standard in FreeCalypso for the past two years and are now taken for granted when doing any FC work, but they had not made their way into a mokoN fw release until now. Following the tradition established by my predecessors in Openmoko's modem fw department, I am releasing the new firmware initially as moko13-beta1, to be tested; if the test reports indicate that it is good, the -beta1 designation will be dropped and the new fw will become the official moko13. The moko13-beta1 tarball for testing is here: https://www.freecalypso.org/members/falcon/experimental-builds/moko13-beta1.tar.bz2 The Corresponding Source is here: https://bitbucket.org/falconian/fc-magnetite For help with flashing and testing this firmware update, please join the FreeCalypso community mailing list: https://www.freecalypso.org/mailman/listinfo/community Sincerely, Mychaela Falconia Mother of FreeCalypso www.freecalypso.org From mychaela.falconia at gmail.com Fri Aug 18 23:12:21 2017 From: mychaela.falconia at gmail.com (Mychaela Falconia) Date: Fri, 18 Aug 2017 15:12:21 -0800 Subject: Openmoko IMEI survey Message-ID: Hello Openmoko and FreeCalypso communities, I am doing a survey of Openmoko device users to see what portions of Openmoko's IMEI number range (TAC 35465101, a range of 1 million possible numbers) have been used to number the 15 thousand or so devices that have been made, and what portions are unused. Given that fewer than 20 thousand units have been made out of the range of 1 million IMEI numbers, simple logic says that at least 980000 numbers out of Openmoko's IMEI range must be still unused, and thus potentially usable for new production of GTA02 verbatim clones and/or FCDEV3B boards which are just the modem part of the GTA02. But I need to make my very best effort to determine WHICH portions of Om's IMEI range have already been used, so I use a different subrange for new device numbering. Unfortunately it appears that no official factory records of IMEI assignments have survived the demise of Openmoko-Inc (I tried asking Sean M-P several times by email, but never heard anything back), hence I am making my best effort to reconstruct this lost knowledge by way of a community survey. To everyone reading this solicitation who owns an Openmoko device: I would love to hear from you if your device falls into one of the following 3 cases: 1: If you have a GTA01 (I have never seen one with my own eyes) as opposed to the more common GTA02, I would love to hear if the first 8 digits of its IMEI are 35465101 (same as GTA02) or something different. 2: If you have a GTA02 hardware variant with "US" bands, i.e., 850/1800/1900 MHz (FCC ID EUNGTA02), as opposed to the much more common "EU" variant (900/1800/1900 MHz, FCC ID EUNGTA02E), same request as above: I would like to know if the first 8 digits of the IMEI are 35465101 or something different. Like with the GTA01, I have never seen a "US" FreeRunner with my own eyes. 3: All Openmoko devices, whether GTA01 or GTA02, "EU" or "US": if the first 8 digits of your IMEI are 35465101, but the following two digits are something other than 16 or 96, I would like to know what those two digits are. The two digits after the 35465101 TAC prefix are the first 2 digits of the 6-digit SNR (serial number) field, and it is the usage of this SNR space that I am after. So far the only Openmoko devices I have laid my hands on have been GTA02 "EU" version units, their TAC has always been 35465101, and the SNR field has always been either 16xxxx on older units or 96xxxx on newer ones. However, if there have been Openmoko devices made with something other than 16xxxx or 96xxxx in the SNR field of the IMEI, I would really like to know about them so I can avoid stepping on those subranges and pick a subrange that has not been used at all. TIA for your participation in the survey, Mychaela Falconia Mother of FreeCalypso www.freecalypso.org From ben_deering at jeepingben.net Sat Aug 19 01:51:07 2017 From: ben_deering at jeepingben.net (Benjamin Deering) Date: Sat, 19 Aug 2017 01:51:07 +0000 Subject: Openmoko IMEI survey In-Reply-To: References: Message-ID: <20170819015107.4bb6dbb0@jeepingben.net> The US GTA02 I still have (FCC EUNGTA02) uses 3546510116xxxxx. I have not tried inserting a SIM, but I have heard that frequencies have been repurposed and that it probably wouldn't work in the US and more. On Fri, 18 Aug 2017 15:12:21 -0800 Mychaela Falconia wrote: > Hello Openmoko and FreeCalypso communities, > > I am doing a survey of Openmoko device users to see what portions of > Openmoko's IMEI number range (TAC 35465101, a range of 1 million > possible numbers) have been used to number the 15 thousand or so > devices that have been made, and what portions are unused. Given that > fewer than 20 thousand units have been made out of the range of > 1 million IMEI numbers, simple logic says that at least 980000 numbers > out of Openmoko's IMEI range must be still unused, and thus > potentially usable for new production of GTA02 verbatim clones and/or > FCDEV3B boards which are just the modem part of the GTA02. But I > need to make my very best effort to determine WHICH portions of Om's > IMEI range have already been used, so I use a different subrange for > new device numbering. > > Unfortunately it appears that no official factory records of IMEI > assignments have survived the demise of Openmoko-Inc (I tried asking > Sean M-P several times by email, but never heard anything back), hence > I am making my best effort to reconstruct this lost knowledge by way > of a community survey. > > To everyone reading this solicitation who owns an Openmoko device: I > would love to hear from you if your device falls into one of the > following 3 cases: > > 1: If you have a GTA01 (I have never seen one with my own eyes) as > opposed to the more common GTA02, I would love to hear if the first > 8 digits of its IMEI are 35465101 (same as GTA02) or something > different. > > 2: If you have a GTA02 hardware variant with "US" bands, i.e., > 850/1800/1900 MHz (FCC ID EUNGTA02), as opposed to the much more > common "EU" variant (900/1800/1900 MHz, FCC ID EUNGTA02E), same > request as above: I would like to know if the first 8 digits of the > IMEI are 35465101 or something different. Like with the GTA01, I > have never seen a "US" FreeRunner with my own eyes. > > 3: All Openmoko devices, whether GTA01 or GTA02, "EU" or "US": if the > first 8 digits of your IMEI are 35465101, but the following two > digits are something other than 16 or 96, I would like to know what > those two digits are. > > The two digits after the 35465101 TAC prefix are the first 2 digits of > the 6-digit SNR (serial number) field, and it is the usage of this SNR > space that I am after. So far the only Openmoko devices I have laid > my hands on have been GTA02 "EU" version units, their TAC has always > been 35465101, and the SNR field has always been either 16xxxx on > older units or 96xxxx on newer ones. However, if there have been > Openmoko devices made with something other than 16xxxx or 96xxxx in > the SNR field of the IMEI, I would really like to know about them so I > can avoid stepping on those subranges and pick a subrange that has not > been used at all. > > TIA for your participation in the survey, > > Mychaela Falconia > Mother of FreeCalypso > www.freecalypso.org > > _______________________________________________ > Openmoko community mailing list > community at lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > From mychaela.falconia at gmail.com Sat Aug 19 02:43:06 2017 From: mychaela.falconia at gmail.com (Mychaela Falconia) Date: Fri, 18 Aug 2017 18:43:06 -0800 Subject: Openmoko IMEI survey In-Reply-To: References: Message-ID: Ben Deering wrote: > The US GTA02 I still have (FCC EUNGTA02) uses 3546510116xxxxx. Thank you for the info! Thanks to this tidbit from you, we know now that FIC was quite lax in (not) following the official IMEI rules, using the same TAC (the first 8 digits of the IMEI) for devices with different frequency band hardware configs, which is a no-no per the official rules... I am still waiting for confirmation on that one, but it also appears that they used the same TAC for both GTA01 and GTA02, contrary to the official rule that the TAC must be different for every new model no matter how minor the change is. (The *only* difference they allow to exist within one TAC is the case color!) The entry for TAC 35465101 in GSMA's IMEI database lists the manufacturer as "FIC" (not Openmoko) and the model as "FIC Neo1973 Smartphone", so all evidence suggests that it was originally obtained for GTA01 and later reused for GTA02. The same IMEI database entry also lists the frequency bands as "GSM 1800,GSM 1900,GSM 900", so clearly the reuse of the same TAC for the "US" GTA02 version was a later hack. My own opinion: while I do not particularly agree with reusing the same device type code (TAC) for devices with different frequency bands in the hardware, I fully applaud FIC (or was it OM after they split off?) for breaking the absolutely idiotic rule about getting a new TAC for every change in the hardware model, no matter how invisible and irrelevant a change like GTA01->GTA02 is from the perspective of GSM networks. Seeing FIC (or OM) take the TAC that was officially assigned for GTA01 devices only and reuse it for the GTA02 will certainly help me justify further reusing the same TAC for my GTA02- derived FCDEV3B modems. :-) > I have not tried inserting a SIM, but I have heard that frequencies > have been repurposed and that it probably wouldn't work in the US and > more. I live in USA-occupied Incalia (one of the ancient names for the continent now called North America), specifically on land which USA wrongfully and forcibly took from Mexico (California), and I use nothing but GSM/2G cellular devices. Furthermore, none of these GSM/2G devices that I use even have that "US" 850 MHz band, instead they are all "European triband" or what I call tri900 in FreeCalypso, i.e., 900/1800/1900 MHz, and they make use of the GSM/2G services in the 1900 MHz PCS band. The operator is T-Mobile USA. The FCDEV3B modem board I have built is a clone of the tri900 ("EU") version of the GTA02 in RF hardware terms. I would not know how to build a tri850 version unless someone tells me what SAW filter part number I should populate for the 850 MHz band in the place of the B7820 for the 900 MHz band. I am hoping to never need to build Om-style tri850 hardware and to go directly to quadband instead (following TI's Leonardo+ and E-Sample designs) for my next hardware iteration. M~ From nitpilot at arcor.de Sun Aug 20 07:01:32 2017 From: nitpilot at arcor.de (nitpilot) Date: Sun, 20 Aug 2017 09:01:32 +0200 Subject: Openmoko IMEI survey In-Reply-To: References: Message-ID: <751607976.bsGsxgd3jU@azo> Hello Mychaela, my GTA02 in Germany (which I had to search for on the shelf) has 35465101 16xxxxx nitpilot On Friday 18 August 2017 15:12:21 Mychaela Falconia wrote: > Hello Openmoko and FreeCalypso communities, > > I am doing a survey of Openmoko device users to see what portions of > Openmoko's IMEI number range (TAC 35465101, a range of 1 million > possible numbers) have been used to number the 15 thousand or so > devices that have been made, and what portions are unused. Given that > fewer than 20 thousand units have been made out of the range of > 1 million IMEI numbers, simple logic says that at least 980000 numbers > out of Openmoko's IMEI range must be still unused, and thus potentially > usable for new production of GTA02 verbatim clones and/or FCDEV3B > boards which are just the modem part of the GTA02. But I need to make > my very best effort to determine WHICH portions of Om's IMEI range > have already been used, so I use a different subrange for new device > numbering. > > Unfortunately it appears that no official factory records of IMEI > assignments have survived the demise of Openmoko-Inc (I tried asking > Sean M-P several times by email, but never heard anything back), hence > I am making my best effort to reconstruct this lost knowledge by way > of a community survey. > > To everyone reading this solicitation who owns an Openmoko device: I > would love to hear from you if your device falls into one of the > following 3 cases: > > 1: If you have a GTA01 (I have never seen one with my own eyes) as > opposed to the more common GTA02, I would love to hear if the first > 8 digits of its IMEI are 35465101 (same as GTA02) or something > different. > > 2: If you have a GTA02 hardware variant with "US" bands, i.e., > 850/1800/1900 MHz (FCC ID EUNGTA02), as opposed to the much more > common "EU" variant (900/1800/1900 MHz, FCC ID EUNGTA02E), same > request as above: I would like to know if the first 8 digits of the > IMEI are 35465101 or something different. Like with the GTA01, I > have never seen a "US" FreeRunner with my own eyes. > > 3: All Openmoko devices, whether GTA01 or GTA02, "EU" or "US": if the > first 8 digits of your IMEI are 35465101, but the following two > digits are something other than 16 or 96, I would like to know what > those two digits are. > > The two digits after the 35465101 TAC prefix are the first 2 digits of > the 6-digit SNR (serial number) field, and it is the usage of this SNR > space that I am after. So far the only Openmoko devices I have laid > my hands on have been GTA02 "EU" version units, their TAC has always > been 35465101, and the SNR field has always been either 16xxxx on > older units or 96xxxx on newer ones. However, if there have been > Openmoko devices made with something other than 16xxxx or 96xxxx in > the SNR field of the IMEI, I would really like to know about them so I > can avoid stepping on those subranges and pick a subrange that has not > been used at all. > > TIA for your participation in the survey, > > Mychaela Falconia > Mother of FreeCalypso > www.freecalypso.org > > _______________________________________________ > Openmoko community mailing list > community at lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community From ba1020 at homie.homelinux.net Thu Aug 24 19:41:29 2017 From: ba1020 at homie.homelinux.net (Juergen Schinker) Date: Thu, 24 Aug 2017 20:41:29 +0100 (BST) Subject: Openmoko reactivated? In-Reply-To: <751607976.bsGsxgd3jU@azo> References: <751607976.bsGsxgd3jU@azo> Message-ID: <1214359405.4260.1503603689288.JavaMail.zimbra@homie.homelinux.net> https://puri.sm/shop/librem-5/ sieht gut aus From joerg at openmoko.org Sat Aug 26 06:17:32 2017 From: joerg at openmoko.org (joerg Reisenweber) Date: Sat, 26 Aug 2017 08:17:32 +0200 Subject: Openmoko IMEI survey In-Reply-To: References: Message-ID: <1582089.2dR9SCsouP@saturn> On Fri 18 August 2017 15:12:21 Mychaela Falconia wrote: > simple logic says that at least 980000 numbers > out of Openmoko's IMEI range must be still unused, and thus potentially > usable for new production of GTA02 verbatim clones and/or FCDEV3B > boards which are just the modem part of the GTA02. Why would you want to abuse OpenMoko IMEIs in an illegal way, instead of arbitrary other larger manufacturer, for a series of phones not built and not in use anymore? You're not owning those IMEIs (they need to be purchased/rented), for OM it would be illegal and punishable to support or invite you to use them in the way you plan to. And you're exposing OpenMoko device owners to public scrutiny by hijacking and abusing this particular IMEI range, possibly resulting in the whole IMEI range getting blacklisted on carriers. @community: It's generally considered a poor idea to disclose your devices' IMEIs and particularly in this case you should think twice before you do. I strongly suggest to use Nokia's 2110 IMEI range instead, or some other similar zombie IMEI range for Motorola or whatever. For Falconia there's not a single benefit from using OM IMEI for that illegal purpose. Best Regards jOERG -- () ascii ribbon campaign /\ against html e-mail - against proprietary attachments http://www.georgedillon.com/web/html_email_is_evil.shtml http://www.nonhtmlmail.org/campaign.html http://www.georgedillon.com/web/html_email_is_evil_still.shtml http://www.gerstbach.at/2004/ascii/ (German) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From mail at dmatthews.org Mon Aug 28 10:29:17 2017 From: mail at dmatthews.org (mail at dmatthews.org) Date: Mon, 28 Aug 2017 11:29:17 +0100 Subject: modem firmware Message-ID: <437858991.11.1503916157087@eurydice.default.davcmat.uk0.bigv.io> hello There are step by step instructions to upgrade the modem firmware of your freerunner to the latest moko13 release from the freecalypso community. https://www.freecalypso.org/members/david/howtos/ The relevant howto includes a link to the release notes which include reasons why you might wish to do this. -- David Matthews mail at dmatthews.org From joerg at openmoko.org Tue Aug 29 01:05:29 2017 From: joerg at openmoko.org (joerg Reisenweber) Date: Tue, 29 Aug 2017 03:05:29 +0200 Subject: modem firmware In-Reply-To: <437858991.11.1503916157087@eurydice.default.davcmat.uk0.bigv.io> References: <437858991.11.1503916157087@eurydice.default.davcmat.uk0.bigv.io> Message-ID: <2021292.XZTDSvm9t1@saturn> On Mon 28 August 2017 11:29:17 mail at dmatthews.org wrote: > hello > > There are step by step instructions to upgrade the modem firmware of your > freerunner to the latest moko13 release from the freecalypso community. > > https://www.freecalypso.org/members/david/howtos/ > > The relevant howto includes a link to the release notes which include > reasons why you might wish to do this. > > -- > David Matthews > mail at dmatthews.org Please carefully note that this update is not based on the original licensed firmware for Openmoko devices, has not been checked and is not endorsed by original manufacturer Openmoko and thus will void your device's (FCC/CE/...) approval thus rendering any operation of the device outside controlled self- contained lab environment illegal. Best Regards jOERG (OM EE) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From joerg at openmoko.org Tue Aug 29 01:14:18 2017 From: joerg at openmoko.org (joerg Reisenweber) Date: Tue, 29 Aug 2017 03:14:18 +0200 Subject: modem firmware In-Reply-To: <437858991.11.1503916157087@eurydice.default.davcmat.uk0.bigv.io> References: <437858991.11.1503916157087@eurydice.default.davcmat.uk0.bigv.io> Message-ID: <2911574.yt7oTRAWBp@saturn> On Mon 28 August 2017 11:29:17 mail at dmatthews.org wrote: > The relevant howto includes a link to the release notes which include > reasons why you might wish to do this. Can't find any such link to release notes in the howto /j -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From mail at dmatthews.org Tue Aug 29 06:25:41 2017 From: mail at dmatthews.org (mail at dmatthews.org) Date: Tue, 29 Aug 2017 07:25:41 +0100 Subject: modem firmware Message-ID: <1437656688.14.1503987941545@eurydice.default.davcmat.uk0.bigv.io> hi Joerg >Can't find any such link to release notes in the howto https://www.freecalypso.org/pipermail/community/2017-August/000452.html for the beta release of the firmware (the moko13 release has no significant changes from the beta) and https://www.freecalypso.org/pipermail/community/2017-August/000464.html for the latest release of fc host tools Both those links are in the howto -- David Matthews mail at dmatthews.org From mychaela.falconia at gmail.com Tue Aug 29 06:33:03 2017 From: mychaela.falconia at gmail.com (Mychaela Falconia) Date: Mon, 28 Aug 2017 22:33:03 -0800 Subject: modem firmware Message-ID: joerg Reisenweber wrote: > Please carefully note that this update is not based on the original licensed > firmware for Openmoko devices, Your original licensed firmware has bugs in it; the updated firmware has some of these bugs fixed. Want examples? Here are just a few in no particular order: * Your firmware configures many Calypso signals which are unconnected in the hardware as inputs, resulting in floating inputs. As an EE you surely know that floating digital inputs are generally bad. I even found a document from TI specific to the chips in question that says that such floating inputs can result in excessive current draw, wasting the battery: https://www.freecalypso.org/LoCosto-docs/SW%20doc/0002_4006_power_consumption_APN.PDF * In April of 2008 some clueless moron at TI-Taiwan sent you a patch for L1 in the form of a binary blob with mystery content that attempted to fix the infamous bug #1024. Later you figured out that it was a hardware bug that cannot be fixed by firmware means, but even before that realization you knew that TI's patch from 20080421 did not improve anything, and you even knew that the patch in question was unofficial from TI's perspective and had not passed TI's internal quality assurance processes: http://lists.openmoko.org/pipermail/openmoko-devel/2008-April/002582.html Yet you included that bogus patch in moko10 and moko11, and unfortunately I also kept it in moko12 (my first post-OM-Inc fw from late 2013) because I didn't know any better back then. In moko13 the bogon has been removed, restoring L1 to the way it was in TI's baseline TCS211 firmware, but even better, I have successfully reconstructed recompilable C source that compiles into a bit-for-bit match to the original blobs, i.e., essentially the lost source which TI had wrongfully withheld from various customers including OM has been reconstructed and We The People now have the Corresponding Source to what used to be a bunch of blobs. * A different clueless moron (this one had to be an employee of OM, as the bogon in question is present in your code but not in TI's reference version) has put in a "gem" in fw versions moko6 through moko11, inclusive, that tells the RR (Radio Resource) layer of the G23M protocol stack that the hardware is quadband, when it is only triband in reality. As a result the fw will attempt to search for GSM cells in all 4 bands, and you even posted on this list back in 2014 that you had a US-band FreeRunner kinda-sorta-work in the 900 MHz band. However, the factory production line calibration on GTA01/02 devices was only performed for the 3 properly supported bands, not for the 4th band, hence if the fw allows the use of that 4th band and the modem's Rx tract manages to pick up a particularly strong signal that passes through the wrong-band SAW filter, when the modem subsequently turns its transmitter on in that band, it will be transmitting without calibration. When no calibration has been done for a given Tx band, the fw will use its hard-coded values, but because you have always said that you only got binary blobs and no source for that part of the fw, I have every good reason to assume that those hard-coded values (which are overridden by factory calibration values written into FFS for the 3 properly supported bands) are not correct for Openmoko hardware at all, and were probably set up for some earlier TI board, most likely Leonardo. The RF tract on TI's historical Leonardo boards was quite different from yours, including a different RF PA, hence when your bogus firmware operates the modem in an uncalibrated band, the Tx power levels are going to be wildly out of spec. I will have some actual measured dBm numbers for you in a few months when I save up the money to get my CMU200 properly recalibrated by Rohde&Schwarz. The firmware bug in question has been fixed in moko12 and moko13: these newer fw versions no longer overwrite the /gsm/com/rfcap file in FFS on every boot, so if you do a 'set-rfcap tri900' or 'set-rfcap tri850' via fc-fsio as appropriate to your GTA01/02 hw variant, your correct rfcap setting will stay, the modem will no longer waste time trying to receive in the unsupported 4th band, and it will never act as an out- of-spec transmitter in that 4th band. > has not been checked and is not endorsed by > original manufacturer Openmoko And what exactly is the worth of an endorsement by the dead ghosts of a no-longer-existing company that did a shitty job of supporting this modem back when it was in business? > and thus will void your device's (FCC/CE/...) > approval The fact that a modem running your official firmware that falsely believes itself to be quadband when running on triband-calibrated hw VIOLATES the actual technical specs for the transmitted signals can only mean that the approval you got was fraudulent or at least erroneous (the certification testers overlooked the technical spec violation), and the actual radio operation of the modem with my fw is in BETTER compliance with the specs than with your fw. > thus rendering any operation of the device outside controlled self- > contained lab environment illegal. Yup, just like using hormonal birth control from an overseas pharmacy without allowing a doctor to sexually violate you under the guise of a necessary exam. Laws like that are MEANT to be broken. Oh, and on the subject of Openmoko IMEIs: unfortunately for you but fortunately for the FreeCalypso community, your instruction to GTA0x device owners to not participate in my survey came a little too late, and I have already gathered all of the info I needed from the numerous helpful off-list responses I got. And yes, if I ever make a production run of new GTA02 devices verbatim- identical to Openmoko-made ones (such that if you were given two FRs, one made by OM and the other made by me, you would not be able to tell which is which without looking at manufacturing dates and IMEIs and such), they will most certainly be numbered from the same TAC 35465101 which you used for your GTA01 and GTA02 devices, and I already know which number ranges are virtually certain to be unused. You have already violated the official rules of the IMEI registry by reusing the GTA01 TAC for the GTA02 and even more seriously by using the same TAC for 900/1800/1900 and 850/1800/1900 band devices, so you rebuking me for making further reuse of that TAC for new production of very faithful clones of your hw is the pot calling the kettle black. Shitty regards, Miss Mychaela P.S. Yes, I know how to be a bitch when you leave me with no other option. P.P.S. I am currently using Gmail (the personal mail server I had in my old male life is down and will never come back up, and I have not yet set up a new one for my new female identity), and there is some problem between the elderly lists.openmoko.org server and Gmail, with the result being that Gmail does not receive any OM list mail at all, and I can only see list activity through the web archive. I don't know what will happen if you send me a unicast email from your openmoko.org domain, but Gmail might blackhole that one as well, so if you ever feel inclined to actually talk to me beyond just posting negativity on the list, you might need to use a different domain. From joerg at openmoko.org Tue Aug 29 08:14:57 2017 From: joerg at openmoko.org (joerg Reisenweber) Date: Tue, 29 Aug 2017 10:14:57 +0200 Subject: modem firmware In-Reply-To: References: Message-ID: <1877847.VzPEkmzeRn@saturn> On Mon 28 August 2017 22:33:03 Mychaela Falconia wrote: > > thus rendering any operation of the device outside controlled self- > > contained lab environment illegal. > > Yup, just like using hormonal birth control from an overseas pharmacy > without allowing a doctor to sexually violate you under the guise of a > necessary exam. Laws like that are MEANT to be broken. Thanks for taking care to lure users into breaking laws that need to get broken according to your definition. Just, I don't need any help on that, I need clear information about what I into when I follow your advice. Can't you see how you're acting wrong? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From joerg at openmoko.org Tue Aug 29 08:34:26 2017 From: joerg at openmoko.org (joerg Reisenweber) Date: Tue, 29 Aug 2017 10:34:26 +0200 Subject: modem firmware In-Reply-To: References: Message-ID: <12230150.ElUzv0LCD7@saturn> for the rest: telling OM about alleged violations of rules while bluntly admitting that you yourself don't care abouzt rules, have no clue about them and think they are made to get violated... YES that is the spacefalcon we know and love ... *NOT* wanna come shoot me once more? Or do you think you tricked us once more? Honestly you never were close to that. The only one's foot you are constantly shooting is your own. -- () ascii ribbon campaign /\ against html e-mail - against proprietary attachments http://www.georgedillon.com/web/html_email_is_evil.shtml http://www.nonhtmlmail.org/campaign.html http://www.georgedillon.com/web/html_email_is_evil_still.shtml http://www.gerstbach.at/2004/ascii/ (German) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From fernando at cmartins.nl Tue Aug 29 09:06:29 2017 From: fernando at cmartins.nl (Fernando) Date: Tue, 29 Aug 2017 11:06:29 +0200 Subject: modem firmware In-Reply-To: <1877847.VzPEkmzeRn@saturn> References: <1877847.VzPEkmzeRn@saturn> Message-ID: <1503997589132.119622.100510@webmail8> I think it is good that you warn people about the illegality of the situation. I don't think it is good you claim the high ground of morals. According to your definition of right, the status of society would never change. Yes, one could do the legal fights to change the law, I guess. Good luck with that. You appear to disregard that society has changed mostly with revolutions, fights for workers rights, etc, to arrive to a better world from which you probably benefit. And there is clearly room for improvement for a better society. "The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man." George Bernard Shaw , Having said that, I find the physical threats out of proportion for the intended benefit. Not to mention counterproductive. Regards, Fernando Martins On August 29, 2017 at 10:14:57 am +02:00, joerg Reisenweber wrote: > On Mon 28 August 2017 22:33:03 Mychaela Falconia wrote: > > > > thus rendering any operation of the device outside controlled self- > > > contained lab environment illegal. > > > > > > > Yup, just like using hormonal birth control from an overseas pharmacy > > without allowing a doctor to sexually violate you under the guise of a > > necessary exam. Laws like that are MEANT to be broken. > > > Thanks for taking care to lure users into breaking laws that need to get > broken according to your definition. Just, I don't need any help on that, I > need clear information about what I into when I follow your advice. > > Can't you see how you're acting wrong? > > _______________________________________________ > Openmoko community mailing list > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From joerg at openmoko.org Tue Aug 29 09:20:29 2017 From: joerg at openmoko.org (joerg Reisenweber) Date: Tue, 29 Aug 2017 11:20:29 +0200 Subject: modem firmware In-Reply-To: <1503997589132.119622.100510@webmail8> References: <1877847.VzPEkmzeRn@saturn> <1503997589132.119622.100510@webmail8> Message-ID: <4465446.i5TK5xsvFh@saturn> the moral aspects of calling somebody out for removing "no parking" signs so people would have to pay tickets for unknowingly parking there, or not telling people that they are in danger to even *do time in jail* when they install and use a firmware that person provides, are not arguable in my world. I won't comment the rest since it's totally missing the point BR /j -- () ascii ribbon campaign /\ against html e-mail - against proprietary attachments http://www.georgedillon.com/web/html_email_is_evil.shtml http://www.nonhtmlmail.org/campaign.html http://www.georgedillon.com/web/html_email_is_evil_still.shtml http://www.gerstbach.at/2004/ascii/ (German) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From fernando at cmartins.nl Tue Aug 29 09:38:30 2017 From: fernando at cmartins.nl (Fernando) Date: Tue, 29 Aug 2017 11:38:30 +0200 Subject: modem firmware In-Reply-To: <4465446.i5TK5xsvFh@saturn> References: <1877847.VzPEkmzeRn@saturn> <1503997589132.119622.100510@webmail8> <4465446.i5TK5xsvFh@saturn> Message-ID: <1503999510156.96087.33792@webmail7> Obviously freecalypso should have a disclaimer about the legal aspects involved, but I guess people actually interested in this would be aware (e.g., discussed many times) and the lack (?) of such a disclaimer is not necessarily done in bad-faith as you claim ("lure"). But I do understand you are entitled to a fair bias against the possible good faith of their actions. On August 29, 2017 at 11:20:29 am +02:00, joerg Reisenweber wrote: > the moral aspects of calling somebody out for removing "no parking" signs so > people would have to pay tickets for unknowingly parking there, or not telling > people that they are in danger to even *do time in jail* when they install and > use a firmware that person provides, are not arguable in my world. > > I won't comment the rest since it's totally missing the point > > BR > /j > -- > () ascii ribbon campaign > /\ > against html e-mail - against proprietary attachments > > > > > > (German) > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mychaela.falconia at gmail.com Tue Aug 29 19:02:31 2017 From: mychaela.falconia at gmail.com (Mychaela Falconia) Date: Tue, 29 Aug 2017 11:02:31 -0800 Subject: modem firmware In-Reply-To: References: Message-ID: Fernando wrote: > Having said that, I find the physical threats out of proportion > for the intended benefit. Not to mention counterproductive. Please cite at least one physical threat within the last 4 y, i.e., later than 2013-08, after the FreeCalypso social justice project successfully ended and the FreeCalypso technical project began. OTOH, if you are still hung up about ancient history, i.e., about the unpleasant things I had to do back in 2013, I am sorry if you don't like it, but there was no other way. The people in question were sitting on the *world's last remaining copy* of TI's TCS211 firmware for the Calypso+Iota+Rita chipset, *no one else in the world* including TI had a copy of this chipset fw any more, all other available TI sources were only for their later LoCosto chipset. The TCS211 source in question has been liberated in the fall of 2013 thanks to another comrade who did what I was not able to do myself. It is unfortunate that no such person had stepped forward sooner, but willingness of other people to step forward and do something which I could not do myself is not something that I ever had any control over. joerg Reisenweber wrote: > wanna come shoot me once more? For what purpose? Just to shut you up, to stop the flow of negative commentary from your mouth/fingers onto this list? No thanks, I have no interest in spending the rest of my life in prison for killing someone who does nothing more than post a bunch of bitter commentary on mailing lists - instead I would much rather spend my life doing some actual productive work, like building new libre phones and modems with the Calypso chipset and finishing the deblobbing of their fw. Wanna show us some examples of some actual productive work YOU have done lately? Have a nice day! M~ From mychaela.falconia at gmail.com Tue Aug 29 20:13:26 2017 From: mychaela.falconia at gmail.com (Mychaela Falconia) Date: Tue, 29 Aug 2017 12:13:26 -0800 Subject: modem firmware In-Reply-To: References: Message-ID: joerg Reisenweber wrote: > the moral aspects of calling somebody out for removing "no parking" signs so > people would have to pay tickets for unknowingly parking there, or not telling > people that they are in danger to even *do time in jail* when they install and > use a firmware that person provides, are not arguable in my world. Please explain *just how* someone can be in danger of doing time in jail for installing and using my bugfix updates for your buggy fw when the actual radio transmissions from the modem remain exactly the same whether you run the old buggy fw or one of my newer versions. They remain exactly the same because: a) The hardware is obviously unchanged. b) The RF calibration values in FFS originally written there on your factory production line remain the same. I do plan on offering a recalibration service whereby a GTA01/02 device owner can send their device to my FreeCalypso warranty service center, it gets recalibrated at my family company on our R&S CMU200 (the same RF test machine we use to calibrate the new FreeCalypso devices we produce ourselves) and sent back to the owner with this fresh calibration, but this service is not up yet, and when it does become available, it is naturally quite separate from an end user merely installing a firmware update. c) The L1 code in my current firmware is a perfect match in logic to TI's 20070608 version which appears in your old fw versions moko3 through moko8, inclusive, a range which certainly includes whatever fw version you used in your type approval process. d) The radio protocol stack layers above L1 (collectively called L23) have not changed since moko8 all the way through my current moko13, with the exception of a few functional bugfixes which do not affect radio operation in any way. The only way in which the modem's radio operation can be changed after installing one of my fw updates would be if the user not only installs the actual fw update, but also changes the /gsm/com/rfcap file afterward (with the fc-fsio utility's set-rfcap command) to reflect the actual triband configuration of the hw. But even in that case the only change will be that the modem will no longer attempt to operate in the unsupported and uncalibrated 4th band, which means *less* possible radio transmission, not more. Or are you saying that my fw updates are illegal simply because you have made that public post from an openmoko.org email address saying that is not officially endorsed by Openmoko the company? If that is your argument, then it can be easily proven that Openmoko the company no longer exists as a legal entity in any country and that you personally as a mere ex-employee of that no-longer-existing company have no special power to make statements on its behalf. And please give me at least one documented example of any police force using extrasensory psychic powers to detect and arrest a user of a phone whose firmware has been updated in a way which they deem to be illegal. Given that the actual radio transmissions remain absolutely unchanged, they would need ESP in order to detect such an illegal fw update. > telling OM about alleged violations of rules while bluntly admitting that you > yourself don't care abouzt rules, have no clue about them and think they are > made to get violated... YES that is the spacefalcon we know and love ... *NOT* While I do not care for any of the laws imposed by any of the self- appointed and ultimately illegitimate national governments, as an engineer I am very diligent about making my very best effort to comply with sensible technical standards, and I continue to argue that my products are better in this regard than yours. M~ From hozer at hozed.org Tue Aug 29 20:34:04 2017 From: hozer at hozed.org (Troy Benjegerdes) Date: Tue, 29 Aug 2017 20:34:04 +0000 Subject: modem firmware In-Reply-To: References: Message-ID: <20170829203404.GA4885@hostname.unassigned> > > and thus will void your device's (FCC/CE/...) > > approval > > The fact that a modem running your official firmware that falsely > believes itself to be quadband when running on triband-calibrated hw > VIOLATES the actual technical specs for the transmitted signals can > only mean that the approval you got was fraudulent or at least > erroneous (the certification testers overlooked the technical spec > violation), and the actual radio operation of the modem with my fw is > in BETTER compliance with the specs than with your fw. Please advise how I may best encourage you to stop talking and take my money. This is quite likely the most usefull public service I have seen done in quite awhile. It is unfortunate that previous bankrupt vendors released a product with shoddy qualifications. Now if only we could properly finance you to find bugs and reverse-engineer a better 4GLTE software defined radio... From mychaela.falconia at gmail.com Tue Aug 29 23:01:09 2017 From: mychaela.falconia at gmail.com (Mychaela Falconia) Date: Tue, 29 Aug 2017 15:01:09 -0800 Subject: modem firmware In-Reply-To: References: Message-ID: Troy Benjegerdes wrote: > Please advise how I may best encourage you to stop talking > and take my money. Take your money? Which product are you seeking to buy? An FCDEV3B board? I am hoping to have those boards available for retail sale by the end of September, i.e., only one month of waiting left. I have an outstanding order for a batch of boards with my contract manufacturer, the CM acknowledged the order on 20170810 and said it was going to be 3 to 4 weeks, so they are supposed to deliver by Thursday of next week (20170907) and I am going to bug them at that time if they don't deliver by then. Once the CM delivers the assembled boards to me, I will need to take them to my home lab and put them through the production test and calibration process (I have successfully recreated the CMU200-based RF calibration process despite never having obtained a copy of OM's original software for it), that production test will reveal how many of the assembled boards are actually good (so far the good yield has been about 50%), and then the good boards will become sellable. > Now if only we could > properly finance you to find bugs and reverse-engineer a > better 4GLTE software defined radio... Reverse engineering and SDR do not go together; with an SDR approach there is nothing to reverse-eng and instead you have to forward-eng everything yourself from scratch. However, none of the mainstream commercial 4G/LTE modems are SDR-based, instead they all use custom silicon. USRP-style SDR approach is totally unsuitable for a cellphone which you could carry in your pocket, instead you would need custom silicon of the kind that Qualcomm and MTK and their ilk make. On the note of "if only we could properly finance you", I actually happen to know some very good recently retired ASIC design engineers, and if there were "proper" financing available, I might be able to convince them to come out of retirement and work on a libre LTE modem ASIC project with me. But the "proper" financing for a project of that sort would need to be well into millions of dollars, hence I am not holding my breath for any such venture. On the other hand, you can have a libre modem for GSM/2G based on the elderly Calypso chipset for much much less: the already-developed FCDEV3B modem boards for hobbyists and tinkerers will probably go for somewhere in the $500-600 USD range retail, and if you are interested in an SMT modem module (directly competing with SIM900 etc) based on the FreeCalypso core, the development cost would be somewhere in the low 5 digits USD, as opposed to the 7 digits for a new LTE modem ASIC. M~ From hozer at hozed.org Tue Aug 29 23:26:33 2017 From: hozer at hozed.org (Troy Benjegerdes) Date: Tue, 29 Aug 2017 23:26:33 +0000 Subject: modem firmware In-Reply-To: References: Message-ID: <20170829232633.GC4885@hostname.unassigned> > On the note of "if only we could properly finance you", I actually > happen to know some very good recently retired ASIC design engineers, > and if there were "proper" financing available, I might be able to > convince them to come out of retirement and work on a libre LTE modem > ASIC project with me. But the "proper" financing for a project of > that sort would need to be well into millions of dollars, hence I am > not holding my breath for any such venture. > > On the other hand, you can have a libre modem for GSM/2G based on the > elderly Calypso chipset for much much less: the already-developed > FCDEV3B modem boards for hobbyists and tinkerers will probably go for > somewhere in the $500-600 USD range retail, and if you are interested > in an SMT modem module (directly competing with SIM900 etc) based on > the FreeCalypso core, the development cost would be somewhere in the > low 5 digits USD, as opposed to the 7 digits for a new LTE modem ASIC. Have you looked at the crazy things that have raised stupid amounts just because they say 'blockchain buzzword buzzword PROFIT' recently? If there was ever a time to do a $100 million dollar coin offering for open-source hardware silicon, it would probably be now. Choice of venue to incorporate said offering should be left to supporting blockchain partner company lawyers.