Re: Recalibration, band conversion and bug #1024 rework
On Wed 14 February 2018 14:40:01 Mychaela Falconia wrote: > Hello OM community, > > I am pleased to announce that my company Falconia Partners LLC is now > offering GSM RF tract recalibration services ... Excellent news. Sounds like you're doing a great job there. Many thanks for that cheers jOERG signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Recalibration, band conversion and bug #1024 rework
Hello OM community, I am pleased to announce that my company Falconia Partners LLC is now offering GSM RF tract recalibration services for Openmoko's Neo 1973 and Neo FreeRunner devices. Like all other commercial GSM phones and modems, these smartphones had their GSM RF parameters individually calibrated on the factory production line. This factory calibration normally persists for the lifetime of the device, but because the calibration values are stored in the Calypso modem's flash file system, it is possible that some Neo owners may have lost theirs as a result of careless playing with modem flashing tools. The latter scenario is quite likely to have happened in the bad old days before FreeCalypso when the modem was treated as some kind of "thou shalt not enter" forbidden zone, and the modem flashing tools and documentation were available only in a hush-hush, whisper-whisper manner. GSM RF calibration also needs to be redone if the RF hardware has been physically modified in any way, e.g., to convert a 900 MHz device to 850 MHz or vice-versa. Because my company produces new Calypso GSM modems that are very similar to Openmoko's, we have the necessary facilities to perform our own RF calibration that is no worse than what OM's factory did. The RF test instrument that is used to perform the calibration is a Rohde CMU200, and this instrument itself needs to be kept in good calibration standing - the chain of traceability goes back to national standards labs like NIST. Our CMU200 instrument has just been calibrated by Rohde in Maryland; here is the official calibration certificate: https://www.freecalypso.org/members/falcon/calibration/CD_5000-309076293.pdf In addition to the measuring instrument, the process of calibrating the RF tract on a Calypso GSM device involves special software that talks both to the firmware running on the Calypso (which naturally needs to be TI-based) and to the CMU200 or other external RF test equipment. The original software that was used by OM's factory appears to have been lost, hence an entirely new replacement had to be developed from scratch here at Falconia Partners LLC, based on the available bits of documentation from TI and meticulous reverse engineering. Our new calibration software is freely published, so you can see exactly what we do when we calibrate a Calypso GSM device: https://bitbucket.org/falconian/fc-rfcal-tools If anyone has a GTA02 or GTA01 device that needs to be recalibrated or could benefit from such, you can send it to Falconia Partners LLC to be serviced. As long as the demand is low, there will be no charge for the recalibration service other than return shipping. If you are going to sending your device in for service, please take the battery out, i.e., send the device WITHOUT the battery. Postal services have become very uptight about lithium batteries recently, hence the return shipping will cost a lot more if I have to deal with the extra bureaucratic hurdles of shipping the device back to you with that Li-ion battery in it. The calibration service is completely non-invasive, i.e., your device won't need to be disassembled beyond taking the back cover off. Your Neo will have 3 cables plugged into it (USB for talking to U-Boot, another USB-serial cable in the headset jack for talking to the Calypso, and an RF test cable going to the CMU200 inserted into the RF test port under the back cover), the application processor will be booted into NOR U-Boot, the latter will be used to execute neo gsm on and neo gsm off commands via USB, and the headset jack serial port will be used to operate on the Calypso modem. Whatever software you are running on the phone's application processor will be left completely untouched. If there is interest, my company may also be able to offer a band conversion service, i.e., converting a 900 MHz FreeRunner to 850 MHz or vice-versa. To make such conversion, one SAW filter part in the GSM section of the motherboard needs to be changed (populate Epcos B7820 for 900 MHz or B7845 for 850 MHz), followed by recalibration. However, unlike pure recalibration, band conversion would require a bit of invasive surgery on the hardware, and this hw surgery would need to be performed at a professional board assembly and rework shop. If there is any serious interest, I can have a discussion with Technotronix (the shop where our new FreeCalypso modem boards are assembled) and see if they would be able to perform rework on Openmoko devices, and how much they would charge for the service. I won't be adding any margin of my own on top of whatever Technotronix folks will charge, but I would need to act as a middlewoman for logistics because devices would need to be recalibrated after the SAW filter change, and the calibration station with the CMU200 (a big, heavy and expensive instrument) resides in my own lab, not at Technotronix. Finally, if anyone has a FreeRunner that hasn't had the rework for
Neo FR disassembly for bug #1024 rework
Hello OM community, I know that a good number of Neo FreeRunner units have been subjected to the hardware rework to fix the infamous bug #1024, and it is my understanding that one or more shops used to perform this rework service professionally once upon a time. I am now looking into the possibility of having my company Falconia Partners LLC offer this hw rework service, as I have heard reports from FreeRunner owners who say that their units never got the rework and do suffer from the bug, and I would also like to be able to offer a band conversion service, i.e., converting any given FreeRunner between 850 MHz and 900 MHz bands in either direction. The band conversion would involve changing one SAW filter component at reference designator U402 (populate Epcos B7820 for 900 MHz or B7845 for 850 MHz, I have the parts readily available) followed by recalibration - and my little company has just the right RF test equipment setup (and newly developed calibration software that fully replicates the functionality of the apparently-lost Windows version used by OM/FIC) to do the latter. The extent of required disassembly is exactly the same for bug #1024 rework and for the SAW filter change - in both cases the metal shieldcan cover over the GSM section of the motherboard needs to be removed, and both reworks can be done in the same surgery. I do wonder, however, if any of the people who used to perform bug #1024 rework in the past on a professional basis (i.e., on customer devices, not their own personal ones) might be willing to share some tips as to what would be the absolutely least invasive way to open that shieldcan and then put it all back together after the surgery. One complication that exists on GTA02 devices but not on GTA01 (nor on my newly made FCDEV3B modems) is that the WLAN daughterboard sits directly on top of the shieldcan cover over the GSM section, and the two are bonded together with some material that seems to be some form of conductive glue. It is not a strong glue, i.e., the WLAN module can be easily pulled off by hand, but pulling it off like this leaves a mess underneath, and thus I assume that my naive way of doing it is probably not the right way. Hence I wonder if any of the people who used to do the rework for bug #1024 professionally might be willing to share the secret of how to do it right: 1) Did you remove the WLAN daughterboard first and then lift the shieldcan cover, or did you somehow remove these two pieces together so they remain attached to each other with that bonding material? 2) If you removed the two pieces separately, how did you restore the bonding between them upon reassembly? 3) If it is possible to remove the shieldcan cover along with the WLAN module on top of it as a single piece, how does one do it? TIA for any tips, Mychaela ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
gta02 bass and #1024 bug rework
Hi list I have a GTA02A7, is there someone in Europe who still offer the bass (not buzz) and #1024 bug rework? Thanks. Regards Joif ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Neo FreeRunner rework party and Openmobility conference 2011 (Czech Republic)
Martix wrote: I hope that we have the first GTA04-EA units shipped by that time and I know that two early adopters come from Czech republic. Nice to hear that! But, I don't know who had ordered these GTA04 and I'm not sure whether they heard about our conference. Please, could you forward them an invitation for Openmobility conference? We really like to see these GTA04 units. I have one ordered and i will bring it to the conference if it will be possible. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Neo FreeRunner rework party and Openmobility conference 2011 (Czech Republic)
Report from the last year's Openmobility conference is on the SHR blog: http://blog.shr-project.org/2010/04/shr-project-gets-a-successful-presentation-at-openmobility-conference.html And photos: http://pcmlich.fit.vutbr.cz/fotky-openmobility/ Best Regards, Martin Martix Holec openmobility.cz/openmoko.cz 2011/5/19 Martix martix...@gmail.com: Hello community, Firstly, I like to invite you (especially Czech and Slovak guys) to Openmobility conference 2011, which will be held on Saturday 18th June 2011 in Brno on FI MUNI. You can look forward to many talks and workshops (in Czech/Slovak language) about open mobile platforms and open source hardware. organizators: people from Czech Openmoko community (Openmobility o.s.) attending platforms: MeeGo/Maemo, webOS, Android... attending devices: Nokia N900, Neo FreeRunner, Touch Book, Genesi Efika, Panda Board, STAX, Arduino…feel free to bring yours! More informations and program here: http://www.openmobility.cz/konference/openmobility-konference-2011/ Secondly, we are going to setup Neo FreeRunner rework party again and fix your Neo FreeRunner's favourite hardware bugs! This rework party will be day after Openmobility conference on Sunday 19th June 2011 in Brno on FIT VUT room L220. GSM buzz fix: http://wiki.openmoko.org/wiki/Buzz_Fix GSM recamping fix: http://wiki.openmoko.org/wiki/1024 Headphones bass fix: http://wiki.openmoko.org/wiki/GTA02_bass_fix NEW reworks: RTC backup battery replace by supercapacitor: http://wiki.openmoko.org/wiki/GTA02_RTC_backup_battery Navigation Board v3 with 3D gyroscope, 3D magnetometer, air pressure/temperature sensor and other parts: http://wiki.openmoko.org/wiki/Freerunner_Navigation_Board_v3 We will order Navigation Boards from Golden Delicious Computers: http://www.handheld-linux.com/wiki.php?page=Navigation%20Board Registrations for FR rework party: http://www.doodle.com/4uhndmddtuvepkbz Please choose your rework before 22th May (this Sunday!) we need to order parts in time. We are looking forward to meeting you. Best Regards, Martin Martix Holec openmobility.cz/openmoko.cz ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Neo FreeRunner rework party and Openmobility conference 2011 (Czech Republic)
Hi Martix, what a pity that I don't speak or understand Czech/Slovak language... Am 21.05.2011 um 10:38 schrieb Martix: Report from the last year's Openmobility conference is on the SHR blog: http://blog.shr-project.org/2010/04/shr-project-gets-a-successful-presentation-at-openmobility-conference.html And photos: http://pcmlich.fit.vutbr.cz/fotky-openmobility/ Best Regards, Martin Martix Holec openmobility.cz/openmoko.cz 2011/5/19 Martix martix...@gmail.com: Hello community, Firstly, I like to invite you (especially Czech and Slovak guys) to Openmobility conference 2011, which will be held on Saturday 18th June 2011 in Brno on FI MUNI. You can look forward to many talks and workshops (in Czech/Slovak language) about open mobile platforms and open source hardware. organizators: people from Czech Openmoko community (Openmobility o.s.) attending platforms: MeeGo/Maemo, webOS, Android... attending devices: Nokia N900, Neo FreeRunner, Touch Book, Genesi Efika, Panda Board, STAX, Arduino…feel free to bring yours! I hope that we have the first GTA04-EA units shipped by that time and I know that two early adopters come from Czech republic. More informations and program here: http://www.openmobility.cz/konference/openmobility-konference-2011/ Secondly, we are going to setup Neo FreeRunner rework party again and fix your Neo FreeRunner's favourite hardware bugs! This rework party will be day after Openmobility conference on Sunday 19th June 2011 in Brno on FIT VUT room L220. GSM buzz fix: http://wiki.openmoko.org/wiki/Buzz_Fix GSM recamping fix: http://wiki.openmoko.org/wiki/1024 Headphones bass fix: http://wiki.openmoko.org/wiki/GTA02_bass_fix NEW reworks: RTC backup battery replace by supercapacitor: http://wiki.openmoko.org/wiki/GTA02_RTC_backup_battery Navigation Board v3 with 3D gyroscope, 3D magnetometer, air pressure/temperature sensor and other parts: http://wiki.openmoko.org/wiki/Freerunner_Navigation_Board_v3 We will order Navigation Boards from Golden Delicious Computers: http://www.handheld-linux.com/wiki.php?page=Navigation%20Board Please let me know as soon as possible so that we can produce enough. Production starts next week. Registrations for FR rework party: http://www.doodle.com/4uhndmddtuvepkbz Please choose your rework before 22th May (this Sunday!) we need to order parts in time. We are looking forward to meeting you. I wish a great success! Nikolaus BTW: there are plans for a new Open HardSoftware Workshop in Germany (German language) this summer/fall. Please register to the mailing list if you want to participate in planning and attending: http://lists.goldelico.com/mailman/listinfo/open-hard-software-event http://freeyourphone.de/portal_v1/viewtopic.php?p=19016sid=25b03499f5c7a29e53081feeb4e73940#p19016 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Neo FreeRunner rework party and Openmobility conference 2011 (Czech Republic)
2011/5/21 Dr. H. Nikolaus Schaller h...@goldelico.com: Hi Martix, what a pity that I don't speak or understand Czech/Slovak language... Hi Nikolaus, unfortunately, we don't have yet enough experiences, people and resources for organizing international english-spoken event. Although, I like to see this happening in the future, when more people gets involved in organisation. Next year, we would like to invite some foreign guest(s) involved in open mobile platforms or open source hardware development to have a talks about their projects. I hope that we have the first GTA04-EA units shipped by that time and I know that two early adopters come from Czech republic. Nice to hear that! But, I don't know who had ordered these GTA04 and I'm not sure whether they heard about our conference. Please, could you forward them an invitation for Openmobility conference? We really like to see these GTA04 units. I wish a great success! Nikolaus Thanks. BTW: there are plans for a new Open HardSoftware Workshop in Germany (German language) this summer/fall. Please register to the mailing list if you want to participate in planning and attending: http://lists.goldelico.com/mailman/listinfo/open-hard-software-event http://freeyourphone.de/portal_v1/viewtopic.php?p=19016sid=25b03499f5c7a29e53081feeb4e73940#p19016 Sorry, I don't speak German, but I'll forward your invitation to other people. Next time, we could join our efforts and make some english-spoken event together... Best Regards, Martin Holec ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Neo FreeRunner rework party and Openmobility conference 2011 (Czech Republic)
Hello community, Firstly, I like to invite you (especially Czech and Slovak guys) to Openmobility conference 2011, which will be held on Saturday 18th June 2011 in Brno on FI MUNI. You can look forward to many talks and workshops (in Czech/Slovak language) about open mobile platforms and open source hardware. organizators: people from Czech Openmoko community (Openmobility o.s.) attending platforms: MeeGo/Maemo, webOS, Android... attending devices: Nokia N900, Neo FreeRunner, Touch Book, Genesi Efika, Panda Board, STAX, Arduino…feel free to bring yours! More informations and program here: http://www.openmobility.cz/konference/openmobility-konference-2011/ Secondly, we are going to setup Neo FreeRunner rework party again and fix your Neo FreeRunner's favourite hardware bugs! This rework party will be day after Openmobility conference on Sunday 19th June 2011 in Brno on FIT VUT room L220. GSM buzz fix: http://wiki.openmoko.org/wiki/Buzz_Fix GSM recamping fix: http://wiki.openmoko.org/wiki/1024 Headphones bass fix: http://wiki.openmoko.org/wiki/GTA02_bass_fix NEW reworks: RTC backup battery replace by supercapacitor: http://wiki.openmoko.org/wiki/GTA02_RTC_backup_battery Navigation Board v3 with 3D gyroscope, 3D magnetometer, air pressure/temperature sensor and other parts: http://wiki.openmoko.org/wiki/Freerunner_Navigation_Board_v3 We will order Navigation Boards from Golden Delicious Computers: http://www.handheld-linux.com/wiki.php?page=Navigation%20Board Registrations for FR rework party: http://www.doodle.com/4uhndmddtuvepkbz Please choose your rework before 22th May (this Sunday!) we need to order parts in time. We are looking forward to meeting you. Best Regards, Martin Martix Holec openmobility.cz/openmoko.cz ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [ANN] Buzz/#1024/Bass-Rework = Headset Audio Quality Enhancement available in EU
because we have been asked: we continue to offer these rework services and the GTA02A7++ variant. Regards, Nikolaus Am 23.03.2010 um 10:42 schrieb Dr. H. Nikolaus Schaller: just let me follow-up that we can ship A7++ devices by end of the week. They are originals from factory and we have applied #1024 and Bass-Rework (Buzz-Rework is not required for A7 units). Please look at http://www.handheld-linux.com/wiki.php?page=Neo%20Freerunner BR, Nikolaus Am 18.03.2010 um 14:39 schrieb Dr. H. Nikolaus Schaller: Am 18.03.2010 um 13:41 schrieb Xavier Cremaschi: Is it possible to do bass-fix and 1024-fix on a device which had already been to Munchen to be buzz-fixed, or does it involve too many soldering operation to be reliable ? yes, no problem. All three reworks are done in very different areas of the device (Buzz is done at the Microphone; #1024 within the tin-can under the WLAN module and the Bass-Rework under the tin-can under the Bluetooth module). And therefore they can be done independently - or all together (which saves a lot of handling and shipment cost). And, they use professional equipment that does the least harm to the board that is possible. BR, Nikolaus Thanks for providing this service btw. Regards, Xavier. ___ 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 ___ 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: [ANN] Bass-Rework = Headset Audio Quality Enhancement available in EU
just let me follow-up that we can ship A7++ devices by end of the week. They are originals from factory and we have applied #1024 and Bass-Rework (Buzz-Rework is not required for A7 units). Please look at http://www.handheld-linux.com/wiki.php?page=Neo%20Freerunner BR, Nikolaus Am 18.03.2010 um 14:39 schrieb Dr. H. Nikolaus Schaller: Am 18.03.2010 um 13:41 schrieb Xavier Cremaschi: Is it possible to do bass-fix and 1024-fix on a device which had already been to Munchen to be buzz-fixed, or does it involve too many soldering operation to be reliable ? yes, no problem. All three reworks are done in very different areas of the device (Buzz is done at the Microphone; #1024 within the tin-can under the WLAN module and the Bass-Rework under the tin-can under the Bluetooth module). And therefore they can be done independently - or all together (which saves a lot of handling and shipment cost). And, they use professional equipment that does the least harm to the board that is possible. BR, Nikolaus Thanks for providing this service btw. Regards, Xavier. ___ 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 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [ANN] Bass-Rework = Headset Audio Quality Enhancement available in EU
Is it possible to do bass-fix and 1024-fix on a device which had already been to Munchen to be buzz-fixed, or does it involve too many soldering operation to be reliable ? Thanks for providing this service btw. Regards, Xavier. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [ANN] Bass-Rework = Headset Audio Quality Enhancement available in EU
Am 18.03.2010 um 13:41 schrieb Xavier Cremaschi: Is it possible to do bass-fix and 1024-fix on a device which had already been to Munchen to be buzz-fixed, or does it involve too many soldering operation to be reliable ? yes, no problem. All three reworks are done in very different areas of the device (Buzz is done at the Microphone; #1024 within the tin-can under the WLAN module and the Bass-Rework under the tin-can under the Bluetooth module). And therefore they can be done independently - or all together (which saves a lot of handling and shipment cost). And, they use professional equipment that does the least harm to the board that is possible. BR, Nikolaus Thanks for providing this service btw. Regards, Xavier. ___ 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
[ANN] Bass-Rework = Headset Audio Quality Enhancement available in EU
Dear Freerunner owners in the EU harmonized market, a known problem of the Neo Freerunner design is that the headset output lacks some low frequency signals (bass). Thererfore music played through the headsets does not sound as expected and compared to other digital music players. There is an improvement rework by adding larger coupling capacitors to the output amplifier. This became known as the Bass Rework (http://wiki.openmoko.org/wiki/GTA02_bass_fix ). Although there is a description of a rework solution (http://people.openmoko.org/andy/additional-headset-audio-caps.pdf ) we do not expect that you can do it yourself and not in the required quality. Just a note what the problem is: we need 47 uF in 0805 dimensions and they are a little expensive and difficult to get and space is very close. Therefore, we have worked on a professional approach. With the help of a local SMD specialist company in Munich, we can now offer a rework service to those who want to improve audio quality. The price is 49 EUR (incl. German VAT) plus shipment. Details can be found at: http://www.handheld-linux.com/wiki.php?page=Bass-Rework Finally a note of caution: acoustic quality is very subjective so that we can't guarantee that the result is good enough for your expectations. We can only guarantee that there is a technical improvement. Nikolaus Schaller Some Pictures How the rework looks like: http://www.handheld-linux.com/images/Bass-Rework1.jpg Oscilloscope signals of a sine wave sweeping from 10 Hz to 100 Hz (for an original unit and for a reworked unit): http://www.handheld-linux.com/images/Bass-Rework2.jpg http://www.handheld-linux.com/images/Bass-Rework3.jpg Mobile Office Solutions by Golden Delicious Computers GmbHCo. KG Buchenstr. 3 D-82041 Oberhaching +49-89-54290367 http://www.handheld-linux.com AG München, HRA 89571 VAT DE253626266 Komplementär: Golden Delicious Computers Verwaltungs GmbH Oberhaching, AG München, HRB 16602 Geschäftsführer: Dr. Nikolaus Schaller Digital Tools for Independent People ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [ANN] Bass-Rework = Headset Audio Quality Enhancement available in EU
On Sat, 2010-03-13 at 12:35 +0100, Dr. H. Nikolaus Schaller wrote: Dear Freerunner owners in the EU harmonized market, a known problem of the Neo Freerunner design is that the headset output lacks some low frequency signals (bass). Thererfore music played through the headsets does not sound as expected and compared to other digital music players. There is an improvement rework by adding larger coupling capacitors to the output amplifier. This became known as the Bass Rework (http://wiki.openmoko.org/wiki/GTA02_bass_fix ). Although there is a description of a rework solution (http://people.openmoko.org/andy/additional-headset-audio-caps.pdf ) we do not expect that you can do it yourself and not in the required quality. Just a note what the problem is: we need 47 uF in 0805 dimensions and they are a little expensive and difficult to get and space is very close. Therefore, we have worked on a professional approach. With the help of a local SMD specialist company in Munich, we can now offer a rework service to those who want to improve audio quality. The price is 49 EUR (incl. German VAT) plus shipment. [snip] Wow! Last night I was hoping the bass-fix would be made available as this is the last problem I have. Thank you! Benedikt ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: #1024-rework service available
Hi Michael, i'm also interested in doing teh rework on my own, but on this page http://wiki.openmoko.org/wiki/1024 and related links there are only few images... so can you please post yours when your work is done? thanks d (if you want/can you can contact me directly) On Fri, Oct 23, 2009 at 11:29 AM, Michael Smith michael.sm...@netapps.com.au wrote: On Fri, 23 Oct 2009 21:05:50 +1100 Chris Samuel ch...@csamuel.org wrote: Or Australia ? Hi. I'm in Melbourne too. Needing to buzz fix an A6 I asked a few electronics engineers. I was looking for somebody who would do delicate soldering work for an hourly rate. The consensus from people I spoke to was that while there are a few small businesses who do electronic work, few would be interested in small jobs. A co-worker of mine offered to do the buzz fix for me. This person tends to over rate his ability. I should have remembered this when I agreed for him to do the work. I plan to tool up and redo the soldering on that phone in the next couple of weeks. The problem with little jobs like this is liability. If he stuffs up, who takes responsibility? On small jobs it is impossible to get insurance. So I am going to do a buzz fix soon. The #1024 fix seems more complicated because you have to disassemble parts of the phone which may be hard to put back together. I might try this procedure on the phone which I am going to do the buzz fix on. I can more afford to stuff that one up. I will post the results here: http://glitch.tl/working_with_shr.html Regards, -- Michael Smith Network Applications www.netapps.com.au | +61 (0) 416 062 898 Web Hosting | Internet Services ___ 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: #1024-rework service available
On Wed, 28 Oct 2009 13:04:54 +0100 Davide Scaini dsca...@gmail.com wrote: Hi Michael, i'm also interested in doing teh rework on my own, but on this page http://wiki.openmoko.org/wiki/1024 and related links there are only few images... so can you please post yours when your work is done? Okay I will do that. -- Michael Smith Network Applications www.netapps.com.au | +61 (0) 416 062 898 Web Hosting | Internet Services signature.asc Description: PGP signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: #1024-rework service available
Michael Smith a écrit : On Wed, 28 Oct 2009 13:04:54 +0100 Davide Scaini dsca...@gmail.com wrote: Hi Michael, i'm also interested in doing teh rework on my own, but on this page http://wiki.openmoko.org/wiki/1024 and related links there are only few images... so can you please post yours when your work is done? Okay I will do that. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community some of mine here in the mess : http://freerunner.daily.free.fr/wp-content/ it was my first attempt with HUGE cap ! (but it worked !) Really easy to do ! Good luck AstHrO ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: #1024-rework service available
On Thu, Oct 22, 2009 at 08:16:59AM +0200, Dr. H. Nikolaus Schaller wrote: How to test if my devices works or needs rework • obtain a command line (e.g. ssh from outside) • open /usr/bin/mickeyterm • type these commands (one after the other) AT+CFUN? AT+CFUN=1 --- only if CFUN? does not report 1 AT+CPIN=insert your pin AT%SLEEP=4 AT%CSQ=1 AT+CREG=2 AT+COPS=0,0 • wait some minutes. If you see +CREG: 0 and/or %CSQ: 99, 99, 0 your device is recamping. here a good device: +CREG: 2 +CREG: 1,033F,5BC4 %CSQ: 13, 99, 1 %CSQ: 7, 99, 0 %CSQ: 10, 99, 1 +CREG: 1,033F,2992 %CSQ: 18, 99, 2 %CSQ: 15, 99, 1 and here a bad device: +CREG: 2 +CREG: 1,033F,2992 %CSQ: 15, 99, 1 +CREG: 0 %CSQ: 99, 99, 0 +CREG: 1,033F,2992 %CSQ: 18, 99, 2 +CREG: 0 %CSQ: 99, 99, 0 +CREG: 1,033F,2992 %CSQ: 17, 99, 1 +CREG: 0 Can you give me an estimate of how much and how long it would take to send a fixed freerunner from your place to Portugal? I want to know the total cost before deciding wether to order it from you... Thanks, Rui ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: #1024-rework service available
On Fri, 23 Oct 2009 08:59:06 am Steven ** wrote: Is there someone offering a similar service in the US? Or Australia ? -- Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC This email may come with a PGP signature as a file. Do not panic. For more info see: http://en.wikipedia.org/wiki/OpenPGP signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: #1024-rework service available
On Fri, 23 Oct 2009 21:05:50 +1100 Chris Samuel ch...@csamuel.org wrote: Or Australia ? Hi. I'm in Melbourne too. Needing to buzz fix an A6 I asked a few electronics engineers. I was looking for somebody who would do delicate soldering work for an hourly rate. The consensus from people I spoke to was that while there are a few small businesses who do electronic work, few would be interested in small jobs. A co-worker of mine offered to do the buzz fix for me. This person tends to over rate his ability. I should have remembered this when I agreed for him to do the work. I plan to tool up and redo the soldering on that phone in the next couple of weeks. The problem with little jobs like this is liability. If he stuffs up, who takes responsibility? On small jobs it is impossible to get insurance. So I am going to do a buzz fix soon. The #1024 fix seems more complicated because you have to disassemble parts of the phone which may be hard to put back together. I might try this procedure on the phone which I am going to do the buzz fix on. I can more afford to stuff that one up. I will post the results here: http://glitch.tl/working_with_shr.html Regards, -- Michael Smith Network Applications www.netapps.com.au | +61 (0) 416 062 898 Web Hosting | Internet Services signature.asc Description: PGP signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: #1024-rework service available
On 10/22/09, Dr. H. Nikolaus Schaller h...@computer.org wrote: Hi all, some users of Neo Freerunner devices have experienced a limited standby time if the GSM modem goes to the deepest sleep mode. This became known as the #1024 bug, because that was the number it got in the bug tracker (https://docs.openmoko.org/trac/ticket/1024). The software workaround was to disable sleep mode 4 as the default. Although there is a description of a hardware rework solution (http://lists.openmoko.org/pipermail/hardware/2009-May/001192.html ) we do not expect that you can do it yourself. Therefore, we have worked on a professional approach. With the help of a local SMD specialist company in Munich, Golden Delicious Computers can now offer a rework service to those who really suffer from this problem. Price is 45 EUR (incl. German VAT of 19%). If you combine with the Buzz-Rework (for A5 and A6 versions only) it is 75 EUR. And there is a rebate for groups of 5 or 10 units. http://www.handheld-linux.com/wiki.php?page=1024-Rework Nikolaus Conditions • This service is for the EU harmonized market only (sorry for Norway Switzerland) • Customer will send in, get rework and get the device sent back within approx. two weeks • The 2 way shipping cost will be covered by the customer. • When choosing a parcel service, please choose one that allows you to track your parcel since we are not responsible for incoming parcels. For German customers we recommend Hermes-Versand and for UK Royal Mail. • Please pack carefully, but just the Neo Freerunner (without battery, battery cover, headset, pouch, stylus, SIM card, SDcard etc.). We are not responsible for lost accessories - only for the device. We strongly recommend to use the original black box. • In the rare case that we damage your device, you will get a fresh Neo Freerunner (but your data is lost). • If you have several Freerunners to rework, please add as many Reworks as you want to the shopping cart. This will reduce shipment cost compared to several single shipments. And, we offer a volume discount to encourage group buys (5: 5%; 10: 10%; 50: 15%). Rebates are automatically shown in the shopping cart. Important notes • After payment is done, please follow the Rework Instructions (http://www.handheld-linux.com/images/Instructions.pdf ) • Please note that we can handle this service only for customers in the EU harmonized market because temporary import/export is too complicated if we want to avoid that you (or we) have to pay again the import tax for your original Freerunner. • This is not a Bass-Fix: http://wiki.openmoko.org/wiki/GTA02_bass_fix How to test if my devices works or needs rework • obtain a command line (e.g. ssh from outside) • open /usr/bin/mickeyterm • type these commands (one after the other) AT+CFUN? AT+CFUN=1 --- only if CFUN? does not report 1 AT+CPIN=insert your pin AT%SLEEP=4 AT%CSQ=1 AT+CREG=2 AT+COPS=0,0 • wait some minutes. If you see +CREG: 0 and/or %CSQ: 99, 99, 0 your device is recamping. here a good device: +CREG: 2 +CREG: 1,033F,5BC4 %CSQ: 13, 99, 1 %CSQ: 7, 99, 0 %CSQ: 10, 99, 1 +CREG: 1,033F,2992 %CSQ: 18, 99, 2 %CSQ: 15, 99, 1 and here a bad device: +CREG: 2 +CREG: 1,033F,2992 %CSQ: 15, 99, 1 +CREG: 0 %CSQ: 99, 99, 0 +CREG: 1,033F,2992 %CSQ: 18, 99, 2 +CREG: 0 %CSQ: 99, 99, 0 +CREG: 1,033F,2992 %CSQ: 17, 99, 1 +CREG: 0 Mobile Office Solutions by Golden Delicious Computers GmbHCo. KG Buchenstr. 3 D-82041 Oberhaching +49-89-54290367 http://www.handheld-linux.com AG München, HRA 89571 VAT DE253626266 Komplementär: Golden Delicious Computers Verwaltungs GmbH Oberhaching, AG München, HRB 16602 Geschäftsführer: Dr. Nikolaus Schaller Digital Tools for Independent People ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community Hi, thanks for offering this service! (although too bad I already sent my device once to Germany) can you give us an indication on how much this would improve batterylife? I'm assuming it only extends standby-time. I once saw a graph that indicated that it was a huge boost, but can't find it anymore y ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: #1024-rework service available
Am Freitag, den 23.10.2009, 12:39 +0200 schrieb Yorick Moko: thanks for offering this service! (although too bad I already sent my device once to Germany) can you give us an indication on how much this would improve batterylife? I'm assuming it only extends standby-time. I once saw a graph that indicated that it was a huge boost, but can't find it anymore In optimal conditions, it's going to double your standby time from ~70h to ~140h. :M: ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: #1024-rework service available
Hi all, here some answers to recent questions: Q: Rework service for USA, Canada, Australia? A: unfortunately handling import/re-export is too much paperwork and if anything goes wrong, someone might have to pay taxes again. And, shipment is either very slow or much more expensive than within EU. This would make it cheaper to buy a new one... You could ask SDG Systems since they also had organized the Buzz- Rework in Canada, i.e. they have a company capable of doing it. Q: Bass-Rework? A: we currently have no plans because it is again a different work which has to be evaluated, tested, prepared for the public. And demand appears to be lower. Q: how much does it improve? A: here is a report of 143 hours standby time: http://totalueberwachung.de/blog/2009/06/03/freerunner-deep-sleep-standby-time Q: when does GTA02-core or GTA03 come fixing all these issues? A: we don't know either Nikolaus Am 23.10.2009 um 12:39 schrieb Yorick Moko: On 10/22/09, Dr. H. Nikolaus Schaller h...@computer.org wrote: Hi all, some users of Neo Freerunner devices have experienced a limited standby time if the GSM modem goes to the deepest sleep mode. This became known as the #1024 bug, because that was the number it got in the bug tracker (https://docs.openmoko.org/trac/ticket/1024). The software workaround was to disable sleep mode 4 as the default. Although there is a description of a hardware rework solution (http://lists.openmoko.org/pipermail/hardware/2009-May/001192.html ) we do not expect that you can do it yourself. Therefore, we have worked on a professional approach. With the help of a local SMD specialist company in Munich, Golden Delicious Computers can now offer a rework service to those who really suffer from this problem. Price is 45 EUR (incl. German VAT of 19%). If you combine with the Buzz-Rework (for A5 and A6 versions only) it is 75 EUR. And there is a rebate for groups of 5 or 10 units. http://www.handheld-linux.com/wiki.php?page=1024-Rework Nikolaus Conditions • This service is for the EU harmonized market only (sorry for Norway Switzerland) • Customer will send in, get rework and get the device sent back within approx. two weeks • The 2 way shipping cost will be covered by the customer. • When choosing a parcel service, please choose one that allows you to track your parcel since we are not responsible for incoming parcels. For German customers we recommend Hermes-Versand and for UK Royal Mail. • Please pack carefully, but just the Neo Freerunner (without battery, battery cover, headset, pouch, stylus, SIM card, SDcard etc.). We are not responsible for lost accessories - only for the device. We strongly recommend to use the original black box. • In the rare case that we damage your device, you will get a fresh Neo Freerunner (but your data is lost). • If you have several Freerunners to rework, please add as many Reworks as you want to the shopping cart. This will reduce shipment cost compared to several single shipments. And, we offer a volume discount to encourage group buys (5: 5%; 10: 10%; 50: 15%). Rebates are automatically shown in the shopping cart. Important notes • After payment is done, please follow the Rework Instructions (http://www.handheld-linux.com/images/Instructions.pdf ) • Please note that we can handle this service only for customers in the EU harmonized market because temporary import/export is too complicated if we want to avoid that you (or we) have to pay again the import tax for your original Freerunner. • This is not a Bass-Fix: http://wiki.openmoko.org/wiki/GTA02_bass_fix How to test if my devices works or needs rework • obtain a command line (e.g. ssh from outside) • open /usr/bin/mickeyterm • type these commands (one after the other) AT+CFUN? AT+CFUN=1 --- only if CFUN? does not report 1 AT+CPIN=insert your pin AT%SLEEP=4 AT%CSQ=1 AT+CREG=2 AT+COPS=0,0 • wait some minutes. If you see +CREG: 0 and/or %CSQ: 99, 99, 0 your device is recamping. here a good device: +CREG: 2 +CREG: 1,033F,5BC4 %CSQ: 13, 99, 1 %CSQ: 7, 99, 0 %CSQ: 10, 99, 1 +CREG: 1,033F,2992 %CSQ: 18, 99, 2 %CSQ: 15, 99, 1 and here a bad device: +CREG: 2 +CREG: 1,033F,2992 %CSQ: 15, 99, 1 +CREG: 0 %CSQ: 99, 99, 0 +CREG: 1,033F,2992 %CSQ: 18, 99, 2 +CREG: 0 %CSQ: 99, 99, 0 +CREG: 1,033F,2992 %CSQ: 17, 99, 1 +CREG: 0 Mobile Office Solutions by Golden Delicious Computers GmbHCo. KG Buchenstr. 3 D-82041 Oberhaching +49-89-54290367 http://www.handheld-linux.com AG München, HRA 89571 VAT DE253626266 Komplementär: Golden Delicious Computers Verwaltungs GmbH Oberhaching, AG München, HRB 16602 Geschäftsführer: Dr. Nikolaus Schaller Digital Tools for Independent People
Re: #1024-rework service available
thanks for offering this service! (although too bad I already sent my device once to Germany) can you give us an indication on how much this would improve batterylife? I'm assuming it only extends standby-time. I once saw a graph that indicated that it was a huge boost, but can't find it anymore Did you mean this pointer: http://totalueberwachung.de/blog/2009/06/03/freerunner-deep-sleep-standby-time ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: #1024-rework service available
On Fri, 23 Oct 2009 13:06:07 +0200 Michael 'Mickey' Lauer mic...@vanille-media.de (M'L) wrote: Am Freitag, den 23.10.2009, 12:39 +0200 schrieb Yorick Moko: thanks for offering this service! (although too bad I already sent my device once to Germany) can you give us an indication on how much this would improve batterylife? I'm assuming it only extends standby-time. I once saw a graph that indicated that it was a huge boost, but can't find it anymore In optimal conditions, it's going to double your standby time from ~70h to ~140h. During first live tests this week, qtmoko managed to last two full days (plus nights) of quite a bit of calls and messaging with occasional checking of status, gprs connection andgps. Previously, one day of use would drain the battery so this is an improvement. As the testing is subjective to usage, we will see in the near future what the real stand by time might be. Petr ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: #1024-rework service available
On Fri, Oct 23, 2009 at 1:07 PM, Dr. H. Nikolaus Schaller h...@computer.org wrote: Q: Bass-Rework? A: we currently have no plans because it is again a different work which has to be evaluated, tested, prepared for the public. And demand appears to be lower. But having bass rework the same time as the 1024 fix, its a huge benefit and also more attractive service. I for example will never send my phone for just to the #1024 fix, because I plan to in a way or another apply the bass fix. So no point to sending you to do the half of the job. (the easier half actually) Frankly, when you dismounted the phone, and you have the necessary tools in your hand, than applying the bass rework in plus, is a negligible price In my really biased view, I find ugly to coming up each quarter year to provide a separate fix, and thus requireing people to send you their freerunner multiple times... ((also I find not fair to having the two fix together involves almost the double price, as it does not require double amount of work)) Best regards, Laszlo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: #1024-rework service available
Am 23.10.2009 um 13:21 schrieb Laszlo KREKACS: On Fri, Oct 23, 2009 at 1:07 PM, Dr. H. Nikolaus Schaller h...@computer.org wrote: Q: Bass-Rework? A: we currently have no plans because it is again a different work which has to be evaluated, tested, prepared for the public. And demand appears to be lower. But having bass rework the same time as the 1024 fix, its a huge benefit and also more attractive service. I for example will never send my phone for just to the #1024 fix, because I plan to in a way or another apply the bass fix. So no point to sending you to do the half of the job. (the easier half actually) Frankly, when you dismounted the phone, and you have the necessary tools in your hand, than applying the bass rework in plus, is a negligible price No. You have to open a different tin can. You have to cut and solder different cables. The test procedure is different. We want to make sure that every fix we offer really works, is reproducible and has high quality. Therfore, it is not just doing the same thing again. The common work is of course the logistics which is done only once. In my really biased view, I find ugly to coming up each quarter year to provide a separate fix, and thus requireing people to send you their freerunner multiple times... Nobody is required to ask for the reworks at all... ((also I find not fair to having the two fix together involves almost the double price, as it does not require double amount of work)) We are a community. Therfore, you are free (and I hope open) to come up with your own, cheaper offers... Nikolaus Best regards, Laszlo ___ 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: #1024-rework service available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dr. H. Nikolaus Schaller schrieb: Am 23.10.2009 um 13:21 schrieb Laszlo KREKACS: On Fri, Oct 23, 2009 at 1:07 PM, Dr. H. Nikolaus Schaller h...@computer.org wrote: Q: Bass-Rework? A: we currently have no plans because it is again a different work which has to be evaluated, tested, prepared for the public. And demand appears to be lower. But having bass rework the same time as the 1024 fix, its a huge benefit and also more attractive service. I for example will never send my phone for just to the #1024 fix, because I plan to in a way or another apply the bass fix. So no point to sending you to do the half of the job. (the easier half actually) Frankly, when you dismounted the phone, and you have the necessary tools in your hand, than applying the bass rework in plus, is a negligible price No. You have to open a different tin can. You have to cut and solder different cables. The test procedure is different. We want to make sure that every fix we offer really works, is reproducible and has high quality. Therfore, it is not just doing the same thing again. The common work is of course the logistics which is done only once. In my really biased view, I find ugly to coming up each quarter year to provide a separate fix, and thus requireing people to send you their freerunner multiple times... Nobody is required to ask for the reworks at all... ((also I find not fair to having the two fix together involves almost the double price, as it does not require double amount of work)) We are a community. Therfore, you are free (and I hope open) to come up with your own, cheaper offers... Nikolaus Best regards, Laszlo ___ 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 Have any effords been done to prepare a bass-fix? Can you guess a date where and if you will offer it? When it will be offered I would prefer to let both be fixed. Greeti+ngs Bastian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFK4cNmlYiDScJJ+7QRAghCAJ4id8XY0jvNiiS4JJ64hozNjfmOcQCgxGmI UDej8HKJjUbL+RWSu9bwrSM= =K9Pi -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
#1024-rework service available
Hi all, some users of Neo Freerunner devices have experienced a limited standby time if the GSM modem goes to the deepest sleep mode. This became known as the #1024 bug, because that was the number it got in the bug tracker (https://docs.openmoko.org/trac/ticket/1024). The software workaround was to disable sleep mode 4 as the default. Although there is a description of a hardware rework solution (http://lists.openmoko.org/pipermail/hardware/2009-May/001192.html ) we do not expect that you can do it yourself. Therefore, we have worked on a professional approach. With the help of a local SMD specialist company in Munich, Golden Delicious Computers can now offer a rework service to those who really suffer from this problem. Price is 45 EUR (incl. German VAT of 19%). If you combine with the Buzz-Rework (for A5 and A6 versions only) it is 75 EUR. And there is a rebate for groups of 5 or 10 units. http://www.handheld-linux.com/wiki.php?page=1024-Rework Nikolaus Conditions • This service is for the EU harmonized market only (sorry for Norway Switzerland) • Customer will send in, get rework and get the device sent back within approx. two weeks • The 2 way shipping cost will be covered by the customer. • When choosing a parcel service, please choose one that allows you to track your parcel since we are not responsible for incoming parcels. For German customers we recommend Hermes-Versand and for UK Royal Mail. • Please pack carefully, but just the Neo Freerunner (without battery, battery cover, headset, pouch, stylus, SIM card, SDcard etc.). We are not responsible for lost accessories - only for the device. We strongly recommend to use the original black box. • In the rare case that we damage your device, you will get a fresh Neo Freerunner (but your data is lost). • If you have several Freerunners to rework, please add as many Reworks as you want to the shopping cart. This will reduce shipment cost compared to several single shipments. And, we offer a volume discount to encourage group buys (5: 5%; 10: 10%; 50: 15%). Rebates are automatically shown in the shopping cart. Important notes • After payment is done, please follow the Rework Instructions (http://www.handheld-linux.com/images/Instructions.pdf ) • Please note that we can handle this service only for customers in the EU harmonized market because temporary import/export is too complicated if we want to avoid that you (or we) have to pay again the import tax for your original Freerunner. • This is not a Bass-Fix: http://wiki.openmoko.org/wiki/GTA02_bass_fix How to test if my devices works or needs rework • obtain a command line (e.g. ssh from outside) • open /usr/bin/mickeyterm • type these commands (one after the other) AT+CFUN? AT+CFUN=1 --- only if CFUN? does not report 1 AT+CPIN=insert your pin AT%SLEEP=4 AT%CSQ=1 AT+CREG=2 AT+COPS=0,0 • wait some minutes. If you see +CREG: 0 and/or %CSQ: 99, 99, 0 your device is recamping. here a good device: +CREG: 2 +CREG: 1,033F,5BC4 %CSQ: 13, 99, 1 %CSQ: 7, 99, 0 %CSQ: 10, 99, 1 +CREG: 1,033F,2992 %CSQ: 18, 99, 2 %CSQ: 15, 99, 1 and here a bad device: +CREG: 2 +CREG: 1,033F,2992 %CSQ: 15, 99, 1 +CREG: 0 %CSQ: 99, 99, 0 +CREG: 1,033F,2992 %CSQ: 18, 99, 2 +CREG: 0 %CSQ: 99, 99, 0 +CREG: 1,033F,2992 %CSQ: 17, 99, 1 +CREG: 0 Mobile Office Solutions by Golden Delicious Computers GmbHCo. KG Buchenstr. 3 D-82041 Oberhaching +49-89-54290367 http://www.handheld-linux.com AG München, HRA 89571 VAT DE253626266 Komplementär: Golden Delicious Computers Verwaltungs GmbH Oberhaching, AG München, HRB 16602 Geschäftsführer: Dr. Nikolaus Schaller Digital Tools for Independent People ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: #1024-rework service available
Am 22.10.2009 um 12:48 schrieb George Brooke: On Thursday 22 Oct 2009 07:16:59 Dr. H. Nikolaus Schaller wrote: Hi all, some users of Neo Freerunner devices have experienced a limited standby time if the GSM modem goes to the deepest sleep mode. This became known as the #1024 bug, because that was the number it got in the bug tracker (https://docs.openmoko.org/trac/ticket/1024). The software workaround was to disable sleep mode 4 as the default. Although there is a description of a hardware rework solution (http://lists.openmoko.org/pipermail/hardware/2009-May/ 001192.html ) we do not expect that you can do it yourself. Therefore, we have worked on a professional approach. With the help of a local SMD specialist company in Munich, Golden Delicious Computers can now offer a rework service to those who really suffer from this problem. Price is 45 EUR (incl. German VAT of 19%). If you combine with the Buzz-Rework (for A5 and A6 versions only) it is 75 EUR. And there is a rebate for groups of 5 or 10 units. http://www.handheld-linux.com/wiki.php?page=1024-Rework Nikolaus Conditions • This service is for the EU harmonized market only (sorry for Norway Switzerland) • Customer will send in, get rework and get the device sent back within approx. two weeks • The 2 way shipping cost will be covered by the customer. • When choosing a parcel service, please choose one that allows you to track your parcel since we are not responsible for incoming parcels. For German customers we recommend Hermes-Versand and for UK Royal Mail. • Please pack carefully, but just the Neo Freerunner (without battery, battery cover, headset, pouch, stylus, SIM card, SDcard etc.). We are not responsible for lost accessories - only for the device. We strongly recommend to use the original black box. • In the rare case that we damage your device, you will get a fresh Neo Freerunner (but your data is lost). • If you have several Freerunners to rework, please add as many Reworks as you want to the shopping cart. This will reduce shipment cost compared to several single shipments. And, we offer a volume discount to encourage group buys (5: 5%; 10: 10%; 50: 15%). Rebates are automatically shown in the shopping cart. Important notes • After payment is done, please follow the Rework Instructions (http://www.handheld-linux.com/images/Instructions.pdf ) • Please note that we can handle this service only for customers in the EU harmonized market because temporary import/export is too complicated if we want to avoid that you (or we) have to pay again the import tax for your original Freerunner. • This is not a Bass-Fix: http://wiki.openmoko.org/wiki/GTA02_bass_fix How to test if my devices works or needs rework • obtain a command line (e.g. ssh from outside) • open /usr/bin/mickeyterm • type these commands (one after the other) AT+CFUN? AT+CFUN=1 --- only if CFUN? does not report 1 AT+CPIN=insert your pin AT%SLEEP=4 AT%CSQ=1 AT+CREG=2 AT+COPS=0,0 • wait some minutes. If you see +CREG: 0 and/or %CSQ: 99, 99, 0 your device is recamping. here a good device: +CREG: 2 +CREG: 1,033F,5BC4 %CSQ: 13, 99, 1 %CSQ: 7, 99, 0 %CSQ: 10, 99, 1 +CREG: 1,033F,2992 %CSQ: 18, 99, 2 %CSQ: 15, 99, 1 and here a bad device: +CREG: 2 +CREG: 1,033F,2992 %CSQ: 15, 99, 1 +CREG: 0 %CSQ: 99, 99, 0 +CREG: 1,033F,2992 %CSQ: 18, 99, 2 +CREG: 0 %CSQ: 99, 99, 0 +CREG: 1,033F,2992 %CSQ: 17, 99, 1 +CREG: 0 Do you need to enable deep sleep mode before doing the test? I think the command AT%SLEEP=4 enables the deep sleep of the modem. Also is this a time-limited service? No, we offer it as long as there is demand. Well, nobody knows what we can provide in 10 or 20 years :) And if we extrapolate technology innovation you probably won't be interested then... solar.george ___ 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: #1024-rework service available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dr. H. Nikolaus Schaller schrieb: Hi all, some users of Neo Freerunner devices have experienced a limited standby time if the GSM modem goes to the deepest sleep mode. This became known as the #1024 bug, because that was the number it got in the bug tracker (https://docs.openmoko.org/trac/ticket/1024). The software workaround was to disable sleep mode 4 as the default. Although there is a description of a hardware rework solution (http://lists.openmoko.org/pipermail/hardware/2009-May/001192.html ) we do not expect that you can do it yourself. Therefore, we have worked on a professional approach. With the help of a local SMD specialist company in Munich, Golden Delicious Computers can now offer a rework service to those who really suffer from this problem. Price is 45 EUR (incl. German VAT of 19%). If you combine with the Buzz-Rework (for A5 and A6 versions only) it is 75 EUR. And there is a rebate for groups of 5 or 10 units. http://www.handheld-linux.com/wiki.php?page=1024-Rework Nikolaus Conditions • This service is for the EU harmonized market only (sorry for Norway Switzerland) • Customer will send in, get rework and get the device sent back within approx. two weeks • The 2 way shipping cost will be covered by the customer. • When choosing a parcel service, please choose one that allows you to track your parcel since we are not responsible for incoming parcels. For German customers we recommend Hermes-Versand and for UK Royal Mail. • Please pack carefully, but just the Neo Freerunner (without battery, battery cover, headset, pouch, stylus, SIM card, SDcard etc.). We are not responsible for lost accessories - only for the device. We strongly recommend to use the original black box. • In the rare case that we damage your device, you will get a fresh Neo Freerunner (but your data is lost). • If you have several Freerunners to rework, please add as many Reworks as you want to the shopping cart. This will reduce shipment cost compared to several single shipments. And, we offer a volume discount to encourage group buys (5: 5%; 10: 10%; 50: 15%). Rebates are automatically shown in the shopping cart. Important notes • After payment is done, please follow the Rework Instructions (http://www.handheld-linux.com/images/Instructions.pdf ) • Please note that we can handle this service only for customers in the EU harmonized market because temporary import/export is too complicated if we want to avoid that you (or we) have to pay again the import tax for your original Freerunner. • This is not a Bass-Fix: http://wiki.openmoko.org/wiki/GTA02_bass_fix How to test if my devices works or needs rework • obtain a command line (e.g. ssh from outside) • open /usr/bin/mickeyterm • type these commands (one after the other) AT+CFUN? AT+CFUN=1 --- only if CFUN? does not report 1 AT+CPIN=insert your pin AT%SLEEP=4 AT%CSQ=1 AT+CREG=2 AT+COPS=0,0 • wait some minutes. If you see +CREG: 0 and/or %CSQ: 99, 99, 0 your device is recamping. here a good device: +CREG: 2 +CREG: 1,033F,5BC4 %CSQ: 13, 99, 1 %CSQ: 7, 99, 0 %CSQ: 10, 99, 1 +CREG: 1,033F,2992 %CSQ: 18, 99, 2 %CSQ: 15, 99, 1 and here a bad device: +CREG: 2 +CREG: 1,033F,2992 %CSQ: 15, 99, 1 +CREG: 0 %CSQ: 99, 99, 0 +CREG: 1,033F,2992 %CSQ: 18, 99, 2 +CREG: 0 %CSQ: 99, 99, 0 +CREG: 1,033F,2992 %CSQ: 17, 99, 1 +CREG: 0 Mobile Office Solutions by Golden Delicious Computers GmbHCo. KG Buchenstr. 3 D-82041 Oberhaching +49-89-54290367 http://www.handheld-linux.com AG München, HRA 89571 VAT DE253626266 Komplementär: Golden Delicious Computers Verwaltungs GmbH Oberhaching, AG München, HRB 16602 Geschäftsführer: Dr. Nikolaus Schaller Digital Tools for Independent People ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community That are great news. I guess that I will buy the rework. Greetungs Bastian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFK4IgklYiDScJJ+7QRAuuOAJ93sAosN+Dqd5gIUQ5q6dSoMB96fgCgzzNI g3ZU3NZSLHa+4vSBPFnyvtI= =Komc -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: #1024-rework service available
Dr.H.NikolausS wrote: • This is not a Bass-Fix: http://wiki.openmoko.org/wiki/GTA02_bass_fix Is this planned in the future? I'd like to buy all the fixes at once... ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: #1024-rework service available
On Thu, Oct 22, 2009 at 1:16 AM, Dr. H. Nikolaus Schaller h...@computer.org wrote: Hi all, Conditions • This service is for the EU harmonized market only (sorry for Norway Switzerland) So, this excludes US customers? Is there someone offering a similar service in the US? Thanks, Steven ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: #1024-rework service available
|-Original Message- |From: community-boun...@lists.openmoko.org [mailto:community- |boun...@lists.openmoko.org] On Behalf Of Steven ** |Sent: Thursday, October 22, 2009 2:59 PM |To: List for Openmoko community discussion |Subject: Re: #1024-rework service available | |On Thu, Oct 22, 2009 at 1:16 AM, Dr. H. Nikolaus Schaller |h...@computer.org wrote: | Hi all, | | Conditions | |. This service is for the EU harmonized market only (sorry for |Norway | Switzerland) | |So, this excludes US customers? | |Is there someone offering a similar service in the US? | |Thanks, |Steven +1 [Russell Dwiggins] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: #1024-rework service available
On Thu, Oct 22, 2009 at 11:04:33PM +0200, Marco Trevisan (Treviño) wrote: Dr.H.NikolausS wrote: ??? This is not a Bass-Fix: http://wiki.openmoko.org/wiki/GTA02_bass_fix Is this planned in the future? I'd like to buy all the fixes at once... Me too. My freerunner happily went to Germany once but I don't want to make him sad with too much travelling :-( ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
rework
hi, i was lucky enough to get someone to perform the gsm buzz rework. i find the images used in the http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP_rc2.pdf quite rather _small_ therefore please find some of my pictures done via microscope here: http://vanous.penguin.cz/files/om/SOP/ Please feel free to use them to improve your manual. Also, we found that placing the 100uF cap according to the manual is rather strange and could cause problems in future - so we placed the cap in a way that is will be soldered to the PCB on both ends, making it hold really tight (that particular picture is somewhat blurry) We didn't have 2k2 in 0402 size so we used 2x 80Ohm in series (we just built a A shape with them). The fix works - done on two units, one showed gsm buzz before and now it's gone. Some of the other pictures show D4301, D4302, as under the microscope we found one of them damaged from manufacturing - placing the cover - something om might watch for. cheers petr ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB headset detection (Was: Pulster fixe(s) and rework)
On Sunday 08 March 2009, Andy Green wrote: Somebody in the thread at some point said: |1. Charger (maybe with Y-cable) connected. Detected by 47 kOhm seen on ID |pin. Set USB mode to host and turn off USB power supply. | |2. USB headset connected. Detected by ? Set USB mode to host and turn on |USB power supply. | |3. USB host connected. Detected by ? Set USB mode to device and turn off |USB power supply. ? here is meant to be ID pin level. But we don't supply a USB device breakout cable which would consistently do the right thing to ID, so it means we can't make decisions based on ID level like a normal OTG setup. We don't supply a USB device breakout cable at all, but we can specify how they should be made to do detection. Is there a standard set of ID levels for OTG that we could follow? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
http://wiki.openmoko.org/wiki/GTA02_bass_fix /j signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | http://wiki.openmoko.org/wiki/GTA02_bass_fix Yes it's a different way to come at it. By putting the caps in that case void 100uF will fit easily, but it needs long leads, the leads violate the can frame / can clearance, you have to cut the can and make some kind of grommet for the leads to pass through. I dunno what happens to BT antenna effectiveness either. The way I documented you keep the leads short, the components are all in the can and the can is unchanged, but you're limited to 22uF or maybe 47uF. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkm0BrEACgkQOjLpvpq7dMpKEgCffFr8lSOttUjCypf7dJJeCkN2 q5AAnig1L9yZhI/ot2gZuIbPkED4wG6D =3L+d -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Bass fix (Was: Pulster fixe(s) and rework)
On Thu, Mar 05, 2009 at 12:56:06PM +0100, Helge Hafting wrote: Another question - is a single big capacitor enough, if it is put into the ground line instead of having one cap for each of the stereo channels? Or will that wreck stereo sound? One could then use a even bigger cap. I think it won't solve the problem of DC through the speakers. Think of the case where the left output is at 0 V and the right output is at 3 V. -- Rask Ingemann Lambertsen Danish law requires addresses in e-mail to be logged and stored for a year ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
Andy Green a...@openmoko.com writes: Somebody in the thread at some point said: | http://wiki.openmoko.org/wiki/GTA02_bass_fix Yes it's a different way to come at it. The way I documented you keep the leads short, the components are all in the can and the can is unchanged, but you're limited to 22uF or maybe 47uF. Reworked the page, included your fix and description as well. Thanks! -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
Andy Green wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | I have suggested a refinement on the second approach: short the small | capacitors. Add big caps outside the shielded unit - there are places | with room. But don't put wires from the caps into the shielded | unit. Connect them to the headset plug instead, and break the plug's | normal connection to the circuit board. This approach won't pick up any | more buzz than the headset based solution, or the current bassless | setup. And you can use any headset you want. | | The big question is - is it safe to short those small capacitors? Or | will that have other side effects, such as draining the battery or | disturbing sound on the built-in speaker? There are a couple of 1K resistors to 0V that will then connect directly ~ to the amp outputs all the time before the new DC blocking caps you will add back in. But thanks to some recent patches by Mark Brown on andy-tracking, we should keep the amp turned off more often. Can these be safely removed? Are they there just to make sure the capacitors slowly drain, so you don't get a pop when plugging something in? Or do they have other purposes as well? | Another question - is a single big capacitor enough, if it is put into | the ground line instead of having one cap for each of the stereo | channels? Or will that wreck stereo sound? One could then use a even | bigger cap. You'd need to do both channels; the one with the unchanged cap will sound the same as always otherwise. You misunderstand. I did not propose to do only one channel. I planned on shorting both the small caps. Then, instead of one big cap on each of the stereo lines: LEave the stereo lines connected as-is. Break the ground line (which is common to both channels) and insert a single big cap there instead. Slightly less work, and perhaps a bigger capacitor will fit. (It'd probably have to be bigger too, as the two channels often enough have the same signal.) | There is lots of easily accessible room next to the battery, above the | SIM card. | | I'd love to see a good answer to those questions. Currently, it's | unusable as an MP3 player and that's an important use for me (if | I could use it as an MP3 player, I'd carry it with me that much more | often, which would in turn increase my use of it). Lifting the can and meddling with the caps is nontrivial. Somebody did give this plan a go on the list about 6 months ago and reported some success though. But I don't recommend considering it unless you are in an experimental frame of mind and can deal with the fiddling and risk involved. I understand that it won't be trivial. Maybe not for me. But if openmoko creates a standard procedure for this improvement too, then I can have an electronic repair shop do everything in one go - both buzz and bass fixes. That will cost me less than having the fixes done separately, even if both fixes together may cost a bit more than buzz only. I hope to ship the phone only once, the repair guy will need to open it only once... A mass fix will be especially cheap - a good technician doing identical fixes on a big stack of phones won't need much time on each. It seems like pulster might set up something like that - but they surely need a procedure, before they can train someone for the job! I hope some thought goes into this for the gta03. Sound output from a phone obviously has low power, but it should be as hi-fi as the sound chip allows. Ideally, a balanced output that don't use (or need) caps. One can play uncompressed wav files, and use a high-quality headset or connect to a regular stereo system. Openmoko could have sound enthusiast customers, as well as linux enthusiasts. Helge Hafting ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
Esben Stien wrote: Stefan Monnier monn...@iro.umontreal.ca writes: (if I could use it as an MP3 player, I'd carry it with me that much more often Until a fix, you can plug in a USB headset;). Won't that rule out simultanous charging with the usb car charger? Anyway, some setup will be necessary, right? A usb headset headset will be a completely new sound device. Can the phone detect it when it gets plugged in, and then do all the configuration? So the sound player will just work Or will we have to go into the settings and change between host and device mode each time the phone is switched between usb headset and pc connection? :-/ Helge Hafting ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
Have you tried tweaking the alsa profiles and set Bass Filter to either 100Hz @ 8kHz (== 600Hz @ 48kHz) or 200Hz @ 8kHz (== 1200Hz @ 48kHz) and Bass Boost to 15? I find the quality just fine for eg. any chance somebody translates that audiophile gibberish into alsa state file gibberish? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | There are a couple of 1K resistors to 0V that will then connect directly | ~ to the amp outputs all the time before the new DC blocking caps you | will add back in. But thanks to some recent patches by Mark Brown on | andy-tracking, we should keep the amp turned off more often. | | Can these be safely removed? Are they there just to make sure the | capacitors slowly drain, so you don't get a pop when plugging something in? | | Or do they have other purposes as well? The headphone action is overloaded with a digital connection to the GSM chipset. It's only used in factory though. I guess the 1Ks were added as some protection against large voltages developing on what would be floating nets on headset insertion, etc. | | Another question - is a single big capacitor enough, if it is put into | | the ground line instead of having one cap for each of the stereo | | channels? Or will that wreck stereo sound? One could then use a even | | bigger cap. | | You'd need to do both channels; the one with the unchanged cap will | sound the same as always otherwise. | | You misunderstand. I did not propose to do only one channel. | I planned on shorting both the small caps. Then, instead of one big cap | on each of the stereo lines: LEave the stereo lines connected as-is. | Break the ground line (which is common to both channels) and insert a | single big cap there instead. Slightly less work, and perhaps a bigger | capacitor will fit. (It'd probably have to be bigger too, as the two | channels often enough have the same signal.) Yes I didn't get your point. But I don't think it's the same action as one cap before each transducer and a direct common low-impedence ground reference. The two signals will mix where they join at the single capacitor and the impedence depends on the frequency. | | There is lots of easily accessible room next to the battery, above the | | SIM card. | | | | I'd love to see a good answer to those questions. Currently, it's | | unusable as an MP3 player and that's an important use for me (if | | I could use it as an MP3 player, I'd carry it with me that much more | | often, which would in turn increase my use of it). | | Lifting the can and meddling with the caps is nontrivial. Somebody did | give this plan a go on the list about 6 months ago and reported some Well, point taken. | I hope some thought goes into this for the gta03. Sound output from a | phone obviously has low power, but it should be as hi-fi as the sound | chip allows. Ideally, a balanced output that don't use (or need) caps. | One can play uncompressed wav files, and use a high-quality headset or | connect to a regular stereo system. Openmoko could have sound | enthusiast customers, as well as linux enthusiasts. We have 47uF series caps on this circuit right now on 3D7K (new name for old GTA03). - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmw74sACgkQOjLpvpq7dMrJ/QCfV0j30BJKibqrQBgSVRwge97b fB0Amwcbt4IK1rcQ0QyGmJzrhGX+nu0t =OfX+ -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
Anyway, some setup will be necessary, right? A usb headset headset will be a completely new sound device. Can the phone detect it when it gets plugged in, and then do all the configuration? So the sound player will just work Or will we have to go into the settings and change between host and device mode each time the phone is switched between usb headset and pc connection? :-/ nothing an appropriate udev rule couldn't handle, i think. on a more generic level it could be handled by fso-frameworkd as well. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
2009/3/6 arne anka openm...@ginguppin.de:
Have you tried tweaking the alsa profiles and set Bass Filter to
either 100Hz @ 8kHz (== 600Hz @ 48kHz) or 200Hz @ 8kHz (== 1200Hz @
48kHz) and Bass Boost to 15? I find the quality just fine for eg.
any chance somebody translates that audiophile gibberish into alsa state
file gibberish?
Sure:
control.15 {
comment.access 'read write'
comment.type ENUMERATED
comment.count 1
comment.item.0 'Linear Control'
comment.item.1 'Adaptive Boost'
iface MIXER
name 'Bass Boost'
value 'Linear Control'
}
control.16 {
comment.access 'read write'
comment.type ENUMERATED
comment.count 1
comment.item.0 '130Hz @ 48kHz'
comment.item.1 '200Hz @ 48kHz'
comment.item.2 '100Hz @ 16kHz'
comment.item.3 '400Hz @ 48kHz'
comment.item.4 '100Hz @ 8kHz'
comment.item.5 '200Hz @ 8kHz'
iface MIXER
name 'Bass Filter'
value '200Hz @ 8kHz'
}
control.17 {
comment.access 'read write'
comment.type INTEGER
comment.count 1
comment.range '0 - 15'
iface MIXER
name 'Bass Volume'
value 15
}
I find the sound breaks sometimes with Adaptive, so I have kept it at Linear.
-Timo
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | 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? No there's no real hardware fix that's practical. We could have done something extreme like PWM the enable by software in FIQ ISR, but it would result in dim AUX LED even so, since the LED is not seeing the excess current but just normally lit. It was fixed on A6, I'm afraid we just have to let it lie and not use the AUX LED much as pointed out unless we're on external power. Overall, it's a small issue about small excess current on one GPIO that spends 99.9% of its life off anyway, as a customer this would bother me so much less than the buzz or bass issues it wouldn't really bother me at all. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmvlWwACgkQOjLpvpq7dMrppwCfcfKKKjYBRZtU3/OkBmteMeA8 2CcAoI0olr8DO0vo8I8n5YYPhNWr7Dxb =flcr -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
Andy Green wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | 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? No there's no real hardware fix that's practical. We could have done something extreme like PWM the enable by software in FIQ ISR, but it would result in dim AUX LED even so, since the LED is not seeing the excess current but just normally lit. It was fixed on A6, I'm afraid we just have to let it lie and not use the AUX LED much as pointed out unless we're on external power. Now that's an idea. How about using it as a battery charging indicator? the orange thing can be used for other purposes then. Helge Hafting ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
On Thursday 05 March 2009 10:38:56 Helge Hafting wrote: Andy Green wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | 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? No there's no real hardware fix that's practical. We could have done something extreme like PWM the enable by software in FIQ ISR, but it would result in dim AUX LED even so, since the LED is not seeing the excess current but just normally lit. It was fixed on A6, I'm afraid we just have to let it lie and not use the AUX LED much as pointed out unless we're on external power. Now that's an idea. How about using it as a battery charging indicator? the orange thing can be used for other purposes then. Thats how it is used currently in Om2008.x. Now that I know of the issue I think it would make sense to change the framework to also use this LED as the battery indicator I also like to use the Orange/Blue LEDs to indicate the current USB mode state: Off - Device Mode + Networking Orange - Device Mode + Storage Blue - Host Mode Blue+Orange - Powered Host mode Using Orange/Blue as a charging indicator wastes all 4 LEDs to just indicate charging/not charging... The red one is useless due to this bug. The orange and blue are busy because of the charging indication and you can't use the violet mode because you can't reuse the orange and blue ones... So, please consider changing the framework to use the red LED to indicate the battery charge state. Michael ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
Am Donnerstag, den 05.03.2009, 10:33 + schrieb Andy Green: I did not find a way myself to list the triggers available in the kernel otherwise I would mention it; if someone found one I'm also interested to know. r...@om-gta02:/sys/class/leds/gta02-aux:red# cat trigger [none] nand-disk battery-charging-or-full battery-charging battery-full adapter-online usb-online ac-online timer heartbeat netdev backlight rfkill0 mmc1 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
Andy Green a...@openmoko.com writes: So, please consider changing the framework to use the red LED to indicate the battery charge state. ... I did not find a way myself to list the triggers available in the kernel otherwise I would mention it; if someone found one I'm also interested to know. Probably this is what you're talking about: debian-gta02:/sys# cat /sys/class/leds/gta02-aux:red/trigger [none] rfkill0 nand-disk rfkill1 mmc0 adapter-online usb-online ac-online battery-charging-or-full battery-charging battery-full timer netdev backlight After activating a trigger some additional parameters become available in the same dir, e.g. after activating netdev device_name, interval, mode appear. As to the original question, one changes frameworkd rules in /etc/freesmartphone/oevents/rules.yaml to use any led he likes for whatever event. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Andy Green a...@openmoko.com writes: | So, please consider changing the framework to use the red LED to | indicate the | battery charge state. | ... | I did not find a way myself to list the triggers available in the kernel | otherwise I would mention it; if someone found one I'm also interested | to know. | | Probably this is what you're talking about: | | debian-gta02:/sys# cat /sys/class/leds/gta02-aux:red/trigger | [none] rfkill0 nand-disk rfkill1 mmc0 adapter-online usb-online | ac-online battery-charging-or-full battery-charging battery-full timer | netdev backlight Ah there we go. I guess it's pretty much every reason you would like to light an LED from kernel side, gsm rfkill is missing but I'm not sure anyone wants to burn the battery just knowing that the GSM modem is powered all the time. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmvr/EACgkQOjLpvpq7dMppHQCgj5H1Fg4xDsw6OpRdgM6V9FjM CcIAoIpW7Ip3qI55Gu0BtjEROpDDD/k9 =IQ+X -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
David Reyes Samblas Martinez wrote: any sop on the bass fix? Not yet, jsut descriptions of workarounds. Two small capacitors needs to be replaced with much bigger ones. Unfortunately, they are in a shielded enclosure where there apparently isn't room for sufficiently big capacitors. One aproach then, is to put the big caps outside the shield, and use wires to connect them inside. But that might lead buzz into the shielded unit - not recommended. Another approach is to short-circuit those small capacitors, and put big capacitors on the headset wire instead. But that means only that one headset fits your freerunner. I have suggested a refinement on the second approach: short the small capacitors. Add big caps outside the shielded unit - there are places with room. But don't put wires from the caps into the shielded unit. Connect them to the headset plug instead, and break the plug's normal connection to the circuit board. This approach won't pick up any more buzz than the headset based solution, or the current bassless setup. And you can use any headset you want. The big question is - is it safe to short those small capacitors? Or will that have other side effects, such as draining the battery or disturbing sound on the built-in speaker? Another question - is a single big capacitor enough, if it is put into the ground line instead of having one cap for each of the stereo channels? Or will that wreck stereo sound? One could then use a even bigger cap. There is lots of easily accessible room next to the battery, above the SIM card. Helge Hafting ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
I have suggested a refinement on the second approach: short the small capacitors. Add big caps outside the shielded unit - there are places with room. But don't put wires from the caps into the shielded unit. Connect them to the headset plug instead, and break the plug's normal connection to the circuit board. This approach won't pick up any more buzz than the headset based solution, or the current bassless setup. And you can use any headset you want. The big question is - is it safe to short those small capacitors? Or will that have other side effects, such as draining the battery or disturbing sound on the built-in speaker? Another question - is a single big capacitor enough, if it is put into the ground line instead of having one cap for each of the stereo channels? Or will that wreck stereo sound? One could then use a even bigger cap. There is lots of easily accessible room next to the battery, above the SIM card. I'd love to see a good answer to those questions. Currently, it's unusable as an MP3 player and that's an important use for me (if I could use it as an MP3 player, I'd carry it with me that much more often, which would in turn increase my use of it). Stefan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | I have suggested a refinement on the second approach: short the small | capacitors. Add big caps outside the shielded unit - there are places | with room. But don't put wires from the caps into the shielded | unit. Connect them to the headset plug instead, and break the plug's | normal connection to the circuit board. This approach won't pick up any | more buzz than the headset based solution, or the current bassless | setup. And you can use any headset you want. | | The big question is - is it safe to short those small capacitors? Or | will that have other side effects, such as draining the battery or | disturbing sound on the built-in speaker? There are a couple of 1K resistors to 0V that will then connect directly ~ to the amp outputs all the time before the new DC blocking caps you will add back in. But thanks to some recent patches by Mark Brown on andy-tracking, we should keep the amp turned off more often. | Another question - is a single big capacitor enough, if it is put into | the ground line instead of having one cap for each of the stereo | channels? Or will that wreck stereo sound? One could then use a even | bigger cap. You'd need to do both channels; the one with the unchanged cap will sound the same as always otherwise. | There is lots of easily accessible room next to the battery, above the | SIM card. | | I'd love to see a good answer to those questions. Currently, it's | unusable as an MP3 player and that's an important use for me (if | I could use it as an MP3 player, I'd carry it with me that much more | often, which would in turn increase my use of it). Lifting the can and meddling with the caps is nontrivial. Somebody did give this plan a go on the list about 6 months ago and reported some success though. But I don't recommend considering it unless you are in an experimental frame of mind and can deal with the fiddling and risk involved. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmwESIACgkQOjLpvpq7dMrOYwCgg84IEzmPEoGSozNU+2kl7v3R edgAn2war5CTGE2912IvQ0tROeRbtUTB =qFA+ -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
2009/3/5 Stefan Monnier monn...@iro.umontreal.ca: I'd love to see a good answer to those questions. Currently, it's unusable as an MP3 player and that's an important use for me (if I could use it as an MP3 player, I'd carry it with me that much more often, which would in turn increase my use of it). Have you tried tweaking the alsa profiles and set Bass Filter to either 100Hz @ 8kHz (== 600Hz @ 48kHz) or 200Hz @ 8kHz (== 1200Hz @ 48kHz) and Bass Boost to 15? I find the quality just fine for eg. in-car music playing. Even when using headphones (Koss KSC-35) I find the quality acceptable, even though the color of the sound is not completely neutral. I tend to prefer 200Hz @ 8kHz, and probably the high-pass filter effect of the output on Neo is indeed quite high, though sometimes I wonder if the midrange is overemphasized with that setting still. I was planning to see about playing back a frequency sweep on Neo, but seemingly forgot about it. Anyway, I now put one 20Hz-2Hz sweep file at http://users.tkk.fi/~tajyrink/moko/20-20k_60s.ogg (vorbis quality 8, should be good enough), if someone with proper(ish) recording equipment can record with eg. 100Hz @ 8kHz and 200Hz @ 8kHz settings with Bass Boost at some level like 15. I don't know what quality an average motherboard HD Audio recording is, but will try it anyway myself at some point with various settings to see what kind of slopes one gets. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
| I'd love to see a good answer to those questions. Currently, it's | unusable as an MP3 player and that's an important use for me (if | I could use it as an MP3 player, I'd carry it with me that much more | often, which would in turn increase my use of it). Lifting the can and meddling with the caps is nontrivial. Somebody did give this plan a go on the list about 6 months ago and reported some success though. But I don't recommend considering it unless you are in an experimental frame of mind and can deal with the fiddling and risk involved. I have no intention to do it myself. But if a good how to gets written, I could probably find someone who does have the necessary expertise. Stefan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework (was: Re: buzz fix)
Am So 11. Januar 2009 schrieb Alexandre Ghisoli: Le Sun, 11 Jan 2009 19:07:40 +0100, Konstantin chaosspaw...@gmx.net a écrit : Matthias Apitz schrieb: Hello Christoph, Could you please also make an offer for the hardware buzz fix in DE: http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP_rc2.pdf Would be great! Thx matthias (one of your happy GTA02 customers) I second this one - offering the hardware fix for the freerunner would be great :) Regards, Konstantin (One of your other happy GTA02 customers ;) ) Yes, hardware fixes (rework) made by resellers would be great. By fixes, I mean : * GPS - SDIO fix (add a capacitor if I remember correctly) There's a sw-fix for that, which mostly just works * Add a GSM IR resistor for deep sleep Huh? * Change the led transistor power hungry stuff Guys, this has been fixed for *ALL* FR ever sold!!! * fix the GSM buzz ok, agree here. * ... ??? /j signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
Joerg Reisenweber wrote: Am So 11. Januar 2009 schrieb Alexandre Ghisoli: Le Sun, 11 Jan 2009 19:07:40 +0100, Konstantin chaosspaw...@gmx.net a écrit : Matthias Apitz schrieb: Hello Christoph, Could you please also make an offer for the hardware buzz fix in DE: http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP_rc2.pdf Would be great! Thx matthias (one of your happy GTA02 customers) I second this one - offering the hardware fix for the freerunner would be great :) Regards, Konstantin (One of your other happy GTA02 customers ;) ) Yes, hardware fixes (rework) made by resellers would be great. By fixes, I mean : * GPS - SDIO fix (add a capacitor if I remember correctly) There's a sw-fix for that, which mostly just works * Add a GSM IR resistor for deep sleep Huh? * Change the led transistor power hungry stuff Guys, this has been fixed for *ALL* FR ever sold!!! * fix the GSM buzz ok, agree here. If I ship the phone somewhere to have a technician fix the buzz, I definitely want the small capacitors on headset output issue fixed too. The capacitor, combined with the resistance of earphones, form a high-pass filter. The cutoff frequency is 1/(2*pi*R*C), where R is headphone resistance and C is the size of the capacitor. The capacitor in the FR has been reported as 1 microfarad. My headset is about 40 ohm, which gives a cutoff frequency of about 4kHz. At 4kHz the sound is halved, and drops by 6db per octave below that. Above, the sound is almost normal. Unfortunately, most of the sound we hear is below 4kHz. A headset usually works down to about 20HZ. If I want the cutoff frequency there, a 200 microfarad capacitor is needed. Is there a plan for such a fix as well? Helge Hafting ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework (was: Re: buzz fix)
And a bass boost fix would be great too. On Wed, Mar 4, 2009 at 8:32 AM, Joerg Reisenweber jo...@openmoko.org wrote: Am So 11. Januar 2009 schrieb Alexandre Ghisoli: Le Sun, 11 Jan 2009 19:07:40 +0100, Konstantin chaosspaw...@gmx.net a écrit : Matthias Apitz schrieb: Hello Christoph, Could you please also make an offer for the hardware buzz fix in DE: http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP_rc2.pdf Would be great! Thx matthias (one of your happy GTA02 customers) I second this one - offering the hardware fix for the freerunner would be great :) Regards, Konstantin (One of your other happy GTA02 customers ;) ) Yes, hardware fixes (rework) made by resellers would be great. By fixes, I mean : * GPS - SDIO fix (add a capacitor if I remember correctly) There's a sw-fix for that, which mostly just works * Add a GSM IR resistor for deep sleep Huh? * Change the led transistor power hungry stuff Guys, this has been fixed for *ALL* FR ever sold!!! * fix the GSM buzz ok, agree here. * ... ??? /j ___ 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: Pulster fixe(s) and rework
any sop on the bass fix? 2009/3/4 Joerg Reisenweber jo...@openmoko.org: Am Mi 4. März 2009 schrieb Helge Hafting: Joerg Reisenweber wrote: Am So 11. Januar 2009 schrieb Alexandre Ghisoli: Le Sun, 11 Jan 2009 19:07:40 +0100, Konstantin chaosspaw...@gmx.net a écrit : Matthias Apitz schrieb: Hello Christoph, Could you please also make an offer for the hardware buzz fix in DE: http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP_rc2.pdf Would be great! Thx matthias (one of your happy GTA02 customers) I second this one - offering the hardware fix for the freerunner would be great :) Regards, Konstantin (One of your other happy GTA02 customers ;) ) Yes, hardware fixes (rework) made by resellers would be great. By fixes, I mean : * GPS - SDIO fix (add a capacitor if I remember correctly) There's a sw-fix for that, which mostly just works * Add a GSM IR resistor for deep sleep Huh? * Change the led transistor power hungry stuff Guys, this has been fixed for *ALL* FR ever sold!!! * fix the GSM buzz ok, agree here. If I ship the phone somewhere to have a technician fix the buzz, I definitely want the small capacitors on headset output issue fixed too. The capacitor, combined with the resistance of earphones, form a high-pass filter. The cutoff frequency is 1/(2*pi*R*C), where R is headphone resistance and C is the size of the capacitor. The capacitor in the FR has been reported as 1 microfarad. My headset is about 40 ohm, which gives a cutoff frequency of about 4kHz. At 4kHz the sound is halved, and drops by 6db per octave below that. Above, the sound is almost normal. Unfortunately, most of the sound we hear is below 4kHz. A headset usually works down to about 20HZ. If I want the cutoff frequency there, a 200 microfarad capacitor is needed. Is there a plan for such a fix as well? Helge Hafting Hey, you copied my mail from ~1year ago ;-) /j ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- David Reyes Samblas Martinez http://www.tuxbrain.com Open ultraportable embedded solutions Openmoko, Openpandora, GP2X the Wiz, Letux 400, Arduino Hey, watch out!!! There's a linux in your pocket!!! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework (was: Re: buzz fix)
On Wed, Mar 4, 2009 at 08:32, Joerg Reisenweber jo...@openmoko.org wrote: * Change the led transistor power hungry stuff Guys, this has been fixed for *ALL* FR ever sold!!! No, no, no. You are right only for GTA02v6. On GTA02v5 (which I have) this has been fixed only for orange and blue LEDs under POWER button. Red AUX button is still power hungry - it is eating 50mA. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
Johny Tenfinger wrote: On Wed, Mar 4, 2009 at 08:32, Joerg Reisenweber jo...@openmoko.org wrote: * Change the led transistor power hungry stuff Guys, this has been fixed for *ALL* FR ever sold!!! No, no, no. You are right only for GTA02v6. On GTA02v5 (which I have) this has been fixed only for orange and blue LEDs under POWER button. Red AUX button is still power hungry - it is eating 50mA. Your mentioned 50mA for the AUX LED is ridiculous. It would burn out with this high current. Normal LEDs only use ~20mA and low current LEDs ~2mA. 50mA would be for a higher power led which isn't build into the freerunner. And when you are on battery the AUX led is off by default and even if it blinks (like i modified my led behaviour) it isn't really much it uses. Ciao, Rainer ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Johny Tenfinger wrote: | On Wed, Mar 4, 2009 at 08:32, Joerg Reisenweber jo...@openmoko.org wrote: | * Change the led transistor power hungry stuff | Guys, this has been fixed for *ALL* FR ever sold!!! | No, no, no. You are right only for GTA02v6. On GTA02v5 (which I have) | this has been fixed only for orange and blue LEDs under POWER button. | Red AUX button is still power hungry - it is eating 50mA. | | Your mentioned 50mA for the AUX LED is ridiculous. It would burn out | with this high current. Normal LEDs only use ~20mA and low current LEDs | ~2mA. 50mA would be for a higher power led which isn't build into the | freerunner. | And when you are on battery the AUX led is off by default and even if it | blinks (like i modified my led behaviour) it isn't really much it uses. 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. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmu21kACgkQOjLpvpq7dMrRmQCfZqaeELLNiPfCWfJWz2U1cUIq 39EAoI5cfSObn7zEG5m4aaolg2zuj6k9 =kWYq -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
Andy Green wrote: Somebody in the thread at some point said: | Johny Tenfinger wrote: | On Wed, Mar 4, 2009 at 08:32, Joerg Reisenweber jo...@openmoko.org wrote: | * Change the led transistor power hungry stuff | Guys, this has been fixed for *ALL* FR ever sold!!! | No, no, no. You are right only for GTA02v6. On GTA02v5 (which I have) | this has been fixed only for orange and blue LEDs under POWER button. | Red AUX button is still power hungry - it is eating 50mA. | | Your mentioned 50mA for the AUX LED is ridiculous. It would burn out | with this high current. Normal LEDs only use ~20mA and low current LEDs | ~2mA. 50mA would be for a higher power led which isn't build into the | freerunner. | And when you are on battery the AUX led is off by default and even if it | blinks (like i modified my led behaviour) it isn't really much it uses. 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. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework
Your mentioned 50mA for the AUX LED is ridiculous. It is. Sadly it's also true. And when you are on battery the AUX led is off by default and even if it blinks (like i modified my led behaviour) it isn't really much it uses. Indeed, it's not lit very often... I'll let you guess why that is. Stefan ___ 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: Pulster fixe(s) and rework
Am Mi 4. März 2009 schrieb Fox Mulder: Johny Tenfinger wrote: On Wed, Mar 4, 2009 at 08:32, Joerg Reisenweber jo...@openmoko.org wrote: * Change the led transistor power hungry stuff Guys, this has been fixed for *ALL* FR ever sold!!! No, no, no. You are right only for GTA02v6. On GTA02v5 (which I have) this has been fixed only for orange and blue LEDs under POWER button. Red AUX button is still power hungry - it is eating 50mA. Your mentioned 50mA for the AUX LED is ridiculous. It would burn out with this high current. Normal LEDs only use ~20mA and low current LEDs ~2mA. 50mA would be for a higher power led which isn't build into the freerunner. And when you are on battery the AUX led is off by default and even if it blinks (like i modified my led behaviour) it isn't really much it uses. Ciao, Rainer The power is consumed by driving a common-emitter transistor driver for LED without base resistor. Current flows from GPIO via base to emitter, and it for sure had been wiser to drive LED directly from GPIO ;-), instead of burning 40mA base current for 10mA collector current. (ballpark numbers) For the non-fixed AUX LED: I wasn't aware these versions have been sold :-/ cheers jOERG signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework (was: Re: buzz fix)
2009/1/11 Alexandre Ghisoli a...@ghisoli.ch: Yes, hardware fixes (rework) made by resellers would be great. By fixes, I mean : * GPS - SDIO fix (add a capacitor if I remember correctly) * Add a GSM IR resistor for deep sleep * Change the led transistor power hungry stuff * fix the GSM buzz * ... Please feel free to comment and complete this list. And I would like to hear something from pulster on this area. I heartily concur. In fact, one of the things that's made me hold off buying a FR is that there isn't an easy way to get this stuff done. If the reseller could make the fixes for me for a reasonable charge, and under warranty, the FR would suddenly become a much more attractive proposition. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pulster fixe(s) and rework (was: Re: buzz fix)
As a Pulster customer I'd really appreciate such service. :) -- Marcel Am Sunday 11 January 2009 20:05:38 schrieb Sam Kuper: 2009/1/11 Alexandre Ghisoli a...@ghisoli.ch: Yes, hardware fixes (rework) made by resellers would be great. By fixes, I mean : * GPS - SDIO fix (add a capacitor if I remember correctly) * Add a GSM IR resistor for deep sleep * Change the led transistor power hungry stuff * fix the GSM buzz * ... Please feel free to comment and complete this list. And I would like to hear something from pulster on this area. I heartily concur. In fact, one of the things that's made me hold off buying a FR is that there isn't an easy way to get this stuff done. If the reseller could make the fixes for me for a reasonable charge, and under warranty, the FR would suddenly become a much more attractive proposition. ___ 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: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL
You can find out the version you have via software query. otherwise take the front faceplate off and see the PCB rev printed there. There are roughly 3K V5 in the feild all built early on.. in june/july I believe, so the datecode can also give you a clue. There is no rework for a5-a6. the differences are listed in the wiki and I'm fairly confident that a large portion of the a5 were reworked, covered this a long time ago.. anyways, both a5/a6 can be reworked to improve the buzz issue some people have. Neil Jerram wrote: 2008/12/17 Joel Newkirk freerun...@newkirk.us: I find myself wondering how many V5 FreeRunners are in the field and whether the owners thereof would want the ability to 'update' to the V6 hardware fixes. Before that I'd like to know how I find out which version I have. Tried googling/wiki/just looking inside, but couldn't find anything clear yet. Neil ___ 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: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL
The A5 to A6 rework was handled at the factory for the most part. see http://wiki.openmoko.org/wiki/GTA02_revisions for details. WRT the a5/a6 rework, I've got to get back with Joerg and Tony Tu to finalize the SOP and then put in place a testing method. One problem is that the Buzz can be location specific. For example, when the Buzz first became apparently Sean flew out to me in SF with a sample of phone that buzzed. Mine didnt. ( he was on other travel ) Anyways, we turned on his phone--no buzz. Now imagine if you have a buzz and send it to person X to fix it. As part of the testing person X would operate the phone and verify that it buzzed. Well, what if it doesnt? does he apply the fix? If it does buzz applying the fix is a straightforward decision. On completion of the fix the phone is tested again and then returned. Does it still buzz after it's returned? So, here is where I stand. my todo list. 1. finalize the SOP and testing protocal. 2. recruit individuals and organizations to do the field rework. 3. Procure parts required for the fix. These parts will be given away either through distys or direct to people willing to do fixes. 4. Finalize rewards program. I'm not likely to get to any of this done before CES which is jan 8-11. It's not a matter of me taking time off for Xmas, but rather the Everest of other tasks and priorities. Experienced sherpas apply within. Staley, Daniel L wrote: I have a V5 unit and would be interested in getting a full upgrade if I sent it off to get the soldering done. Not sure if you wanted people to respond to that question, or you were just thinking aloud... -Dan Staley From: Joel Newkirk [freerun...@newkirk.us] Sent: Tuesday, December 16, 2008 8:33 PM To: List for Openmoko community discussion Subject: Re: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL On Tue, 16 Dec 2008 14:21:11 -0800, Sargun Dhillon xbmodder+openm...@gmail.com wrote: Joel, any update on this? Still waiting for an answer from OM. (I posted a question in this thread Friday regarding Tanatalum instead of Ceramic cap - the difference being $0.25 vs $2 each in qty 100, and my radio guy thinks Tant is a good choice for filtering, but waiting for word from Steve or Jeorg) Boss said he's willing to do the jobs, but we have no caps, can't order until we know which ones to order. We're also hoping to find out what help them/reward them involves. (IE, OM provide parts? OM underwrite repair? Cover part of repair? Send me a Christmas card? :) Boss ballparked the job at $25 but nothing definite yet. (depends in part on parts) The only concern they had when I showed them the pdf and my FreeRunner was regarding damaging the housing while soldering - at which point I demonstrated removing the board from the FR with about 30 seconds effort and they said ooh OK then. :) I find myself wondering how many V5 FreeRunners are in the field and whether the owners thereof would want the ability to 'update' to the V6 hardware fixes. I know of the cap on the uSD pins fix for the GPS vs uSD issue (though not the identity of that capacitor), I don't know what change allows a V6 to run without battery or if other differences exist. Dropping a cap on the two pins of the uSD socket is pretty trivial if you're already doing SMD work, so if we're already performing the Big-C rework I'd guess (pure personal speculation) that we could add the cap to the SD lines for little more expense and time. j On Thu, Dec 11, 2008 at 7:44 PM, Joel Newkirk freerun...@newkirk.us wrote: I'm going to talk to the guys at work tomorrow and show them the rework PDF - we are equipped to make this fix, could probably offer it inexpensively to those nearby (southeastern North Carolina) or those willing to ship. (among other things - like security systems and internet services - we repair handheld radios and wireless broadband networking gear, including replacing BGAs and more mundane SMD components) I'm betting we have the resistors on hand, would probably need to order a hundred or so of the caps. I'll post back here if the answer is positive. We're located in Hamlet NC, near Ft Bragg, but we're gearing up to offer repairs nationwide for specific wireless networking gear, so shipping and processing of customer repair items in/out is forthcoming anyway, this is just a different board with a much simpler fix to be performed, I'm just not sure they'll be interested in offering it as inexpensively as I'd like. j On Thu, 11 Dec 2008 17:29:32 -0800, Steve Mosher st...@openmoko.com wrote: If guys raise there hand to help others out I'll come up with a program to help them out/ reward them. If you are willing to raise your hand, drop me a mail. st...@openmoko.com Sargun Dhillon wrote: Very cool. Now, all the hardware hackers out there who want to make a buck to fix our Free runners
[big C rework] Anyone in Chile doing this?
Hello list, I wonder if anyone in Chile with a freerunner is interested in doing the rework proposed by joerg. I´m cuerrently checking prices and they are making a big discount if they repair 10 or more units. If anyone is interested just email me. Tom PS. I´m going to post this to the spanish mailing list too in case people don´t read the english one. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Answer from Joerg (was: Re: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL)
Joel Newkirk freerun...@newkirk.us writes: Still waiting for an answer from OM. (I posted a question in this thread Friday regarding Tanatalum instead of Ceramic cap - the difference being $0.25 vs $2 each in qty 100, and my radio guy thinks Tant is a good choice for filtering, but waiting for word from Steve or Jeorg) Joel, Joerg overlooked your question on the community mailing list, you should have asked at hardware list instead. I asked him on IRC: here's the answer: 12:57 PaulFertser DocScrutinizer: could you please answer a question wrt capacitor type for the gsm buzz fix? Joel Newkirk asks whether he can use tantalum instead of ceramic ones as tantalum are much cheaper and he's going to perform a rework on a reasonable quantity of units (IIRC). 13:00 DocScrutinizer PaulFertser: we don't have any tantalum caps here, and I would guess they are just too big. I was about to suggest a free caeramic cap for everyone asking for it. actually I'll bring a handfull of those to Germany on Sunday 13:00 DocScrutinizer PaulFertser: technically there is nothing wrong with tantalum 13:01 DocScrutinizer though I'd guess they are somewhat harder to solder, as they're basically electrolytic caps and so won't stand much heat 13:01 PaulFertser DocScrutinizer: if you don't mind, i'm going to post your answer on the community mailing list in the corresponding thread. 13:02 DocScrutinizer go ahead, you're welcome 13:02 DocScrutinizer just quote this dialog is fine 13:04 DocScrutinizer also, to whom it may concern, I plan to join 25C3 congress in Berlin, and maybe rework a couple of devices there for free, or at very least give away caps -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL
On Thursday 18 December 2008, Joel Newkirk wrote: On Wed, 17 Dec 2008 17:00:34 +, Al Johnson openm...@mazikeen.demon.co.uk wrote: On Wednesday 17 December 2008, Joel Newkirk wrote: I don't know what the physical difference is for the power tweak. (V6 can power up from wall power without battery) It's a bigger C1767 - according to the schematics it's 4.7uF on A5, 47uF on A6 and 100uF on A7. Werner's writeup of the investigations is here: http://people.openmoko.org/werner/gta02-chg/ Thanks - that was most of what I was needing. Unfortunately it doesn't identify the real estate occupied by C1767 there, nor in the component placement diagrams. Can someone point me at the right spot on the board? If it's got enough room for the same 3528 cap we're looking at for the big-C rework (which I doubt, though it looks like it will fit for the big-C position) that would be great. j I've replied on the hardware list since the thread has turned pure hardware, and we're more likely to get an answer there. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Answer from Joerg (was: Re: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL)
I did the big-c buzzing rework myself, with the precious help of a much more smd-experienced colleague. It was very difficult to replace the resistor because of the proximity of the components around the mic. A very sharp soldering iron is critical. I used a 1k resistor (didn't have a 2k2 of the same size at hand), and a 100uF/10V tantalum capacitor. So far, so good! The buzz seems to be gone for good. :) One caller has reported that I sounded like at the bottom of a pit, but this can be the other older issue... Citando Paul Fertser fercer...@gmail.com: Joel Newkirk freerun...@newkirk.us writes: Still waiting for an answer from OM. (I posted a question in this thread Friday regarding Tanatalum instead of Ceramic cap - the difference being $0.25 vs $2 each in qty 100, and my radio guy thinks Tant is a good choice for filtering, but waiting for word from Steve or Jeorg) Joel, Joerg overlooked your question on the community mailing list, you should have asked at hardware list instead. I asked him on IRC: here's the answer: 12:57 PaulFertser DocScrutinizer: could you please answer a question wrt capacitor type for the gsm buzz fix? Joel Newkirk asks whether he can use tantalum instead of ceramic ones as tantalum are much cheaper and he's going to perform a rework on a reasonable quantity of units (IIRC). 13:00 DocScrutinizer PaulFertser: we don't have any tantalum caps here, and I would guess they are just too big. I was about to suggest a free caeramic cap for everyone asking for it. actually I'll bring a handfull of those to Germany on Sunday 13:00 DocScrutinizer PaulFertser: technically there is nothing wrong with tantalum 13:01 DocScrutinizer though I'd guess they are somewhat harder to solder, as they're basically electrolytic caps and so won't stand much heat 13:01 PaulFertser DocScrutinizer: if you don't mind, i'm going to post your answer on the community mailing list in the corresponding thread. 13:02 DocScrutinizer go ahead, you're welcome 13:02 DocScrutinizer just quote this dialog is fine 13:04 DocScrutinizer also, to whom it may concern, I plan to join 25C3 congress in Berlin, and maybe rework a couple of devices there for free, or at very least give away caps -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL
Am Mi 17. Dezember 2008 schrieb Esben Stien: Steve Mosher st...@openmoko.com writes: If guys raise there hand to help others out I'll come up with a program to help them out/ reward them. If you are willing to raise your hand, drop me a mail. I've talked to a local electronics repair shop here in Bergen, Norway and they said they will do this operation. There, however, should be a package which contain all relevant documentation and complete circuitry and dismantling the freerunner to help a technician easily and quickly do this operation and not waste time finding the documents. ok, I'll rework SOP another time to meet these needs. for now lease refer to wiki about opening he case, and search my people/ folder for recent document (rc2 atm). /jOERG signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL
I have a V5 unit and would be interested in getting a full upgrade if I sent it off to get the soldering done. Not sure if you wanted people to respond to that question, or you were just thinking aloud... -Dan Staley From: Joel Newkirk [freerun...@newkirk.us] Sent: Tuesday, December 16, 2008 8:33 PM To: List for Openmoko community discussion Subject: Re: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL On Tue, 16 Dec 2008 14:21:11 -0800, Sargun Dhillon xbmodder+openm...@gmail.com wrote: Joel, any update on this? Still waiting for an answer from OM. (I posted a question in this thread Friday regarding Tanatalum instead of Ceramic cap - the difference being $0.25 vs $2 each in qty 100, and my radio guy thinks Tant is a good choice for filtering, but waiting for word from Steve or Jeorg) Boss said he's willing to do the jobs, but we have no caps, can't order until we know which ones to order. We're also hoping to find out what help them/reward them involves. (IE, OM provide parts? OM underwrite repair? Cover part of repair? Send me a Christmas card? :) Boss ballparked the job at $25 but nothing definite yet. (depends in part on parts) The only concern they had when I showed them the pdf and my FreeRunner was regarding damaging the housing while soldering - at which point I demonstrated removing the board from the FR with about 30 seconds effort and they said ooh OK then. :) I find myself wondering how many V5 FreeRunners are in the field and whether the owners thereof would want the ability to 'update' to the V6 hardware fixes. I know of the cap on the uSD pins fix for the GPS vs uSD issue (though not the identity of that capacitor), I don't know what change allows a V6 to run without battery or if other differences exist. Dropping a cap on the two pins of the uSD socket is pretty trivial if you're already doing SMD work, so if we're already performing the Big-C rework I'd guess (pure personal speculation) that we could add the cap to the SD lines for little more expense and time. j On Thu, Dec 11, 2008 at 7:44 PM, Joel Newkirk freerun...@newkirk.us wrote: I'm going to talk to the guys at work tomorrow and show them the rework PDF - we are equipped to make this fix, could probably offer it inexpensively to those nearby (southeastern North Carolina) or those willing to ship. (among other things - like security systems and internet services - we repair handheld radios and wireless broadband networking gear, including replacing BGAs and more mundane SMD components) I'm betting we have the resistors on hand, would probably need to order a hundred or so of the caps. I'll post back here if the answer is positive. We're located in Hamlet NC, near Ft Bragg, but we're gearing up to offer repairs nationwide for specific wireless networking gear, so shipping and processing of customer repair items in/out is forthcoming anyway, this is just a different board with a much simpler fix to be performed, I'm just not sure they'll be interested in offering it as inexpensively as I'd like. j On Thu, 11 Dec 2008 17:29:32 -0800, Steve Mosher st...@openmoko.com wrote: If guys raise there hand to help others out I'll come up with a program to help them out/ reward them. If you are willing to raise your hand, drop me a mail. st...@openmoko.com Sargun Dhillon wrote: Very cool. Now, all the hardware hackers out there who want to make a buck to fix our Free runners, raise your hands. On Wed, Dec 10, 2008 at 5:31 PM, Steve Mosher st...@openmoko.com wrote: Probably best to send the requests directly to Joerg. Vasco Névoa wrote: I'd really like pictures with better focus and a little more light... especially the last one, which is very blurred! Citando Steve Mosher st...@openmoko.com: Sorry, I pulled the old copy. See below SOP paper (draft3, 2008-12-10 19:00) placed here: http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP__DRAFT3__.pdf Please have a look and report on any mistakes or things that need improvement. Thanks jOERG Neil Jerram wrote: 2008/12/10 Steve Mosher st...@openmoko.com: The DRAFT fix for the buzz problem is here: CP of joerg's mail. http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP__DRAFT!!__.pdf I'm getting 404 for this URL. Neil ___ 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 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list
Re: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL
On Wednesday 17 December 2008, Joel Newkirk wrote: I don't know what the physical difference is for the power tweak. (V6 can power up from wall power without battery) It's a bigger C1767 - according to the schematics it's 4.7uF on A5, 47uF on A6 and 100uF on A7. Werner's writeup of the investigations is here: http://people.openmoko.org/werner/gta02-chg/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL
2008/12/17 Neil Jerram neiljer...@googlemail.com: 2008/12/17 Joel Newkirk freerun...@newkirk.us: I find myself wondering how many V5 FreeRunners are in the field and whether the owners thereof would want the ability to 'update' to the V6 hardware fixes. Before that I'd like to know how I find out which version I have. Tried googling/wiki/just looking inside, but couldn't find anything clear yet. Neil Hi, http://wiki.openmoko.org/wiki/FAQ#How_do_I_find_out_what_version_of_hardware_I_have.3F Cheers, Mateusz -- AKA f3nix AKA metyl AKA skowri ;) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL
On Wed, 17 Dec 2008 10:56:46 +, Neil Jerram neiljer...@googlemail.com wrote: 2008/12/17 Joel Newkirk freerun...@newkirk.us: I find myself wondering how many V5 FreeRunners are in the field and whether the owners thereof would want the ability to 'update' to the V6 hardware fixes. Before that I'd like to know how I find out which version I have. Tried googling/wiki/just looking inside, but couldn't find anything clear yet. Neil Take out the battery, SIM and uSD. Where the contacts for the uSD meet the PC board there will be a SMD capacitor (about .5x1mm) between two of the contacts, _IF_ it's newer than V5. I don't know what the physical difference is for the power tweak. (V6 can power up from wall power without battery) You can also look at the datecode on the serial/imei sticker under the battery, but I don't know the exact cutoff date. I know that datecodes from June are V5 and from August are V6. j -- Joel Newkirk http://jthinks.com (blog) http://newkirk.us/om (FR stuff) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL
2008/12/17 Joel Newkirk freerun...@newkirk.us: On Wed, 17 Dec 2008 10:56:46 +, Neil Jerram neiljer...@googlemail.com wrote: 2008/12/17 Joel Newkirk freerun...@newkirk.us: I find myself wondering how many V5 FreeRunners are in the field and whether the owners thereof would want the ability to 'update' to the V6 hardware fixes. Before that I'd like to know how I find out which version I have. Tried googling/wiki/just looking inside, but couldn't find anything clear yet. Neil Take out the battery, SIM and uSD. Where the contacts for the uSD meet the PC board there will be a SMD capacitor (about .5x1mm) between two of the contacts, _IF_ it's newer than V5. Thanks, there's something of that size there. Also the date is 20080717, and /proc/cpuinfo's Revision is 0360. So mine is a v6. Regards, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL
2008/12/17 Mateusz Skowroński sko...@gmail.com: Hi, http://wiki.openmoko.org/wiki/FAQ#How_do_I_find_out_what_version_of_hardware_I_have.3F Many thanks; I don't know how my googling missed that! Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL
2008/12/17 Joel Newkirk freerun...@newkirk.us: I find myself wondering how many V5 FreeRunners are in the field and whether the owners thereof would want the ability to 'update' to the V6 hardware fixes. Before that I'd like to know how I find out which version I have. Tried googling/wiki/just looking inside, but couldn't find anything clear yet. Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL
On Wed, 17 Dec 2008 17:00:34 +, Al Johnson openm...@mazikeen.demon.co.uk wrote: On Wednesday 17 December 2008, Joel Newkirk wrote: I don't know what the physical difference is for the power tweak. (V6 can power up from wall power without battery) It's a bigger C1767 - according to the schematics it's 4.7uF on A5, 47uF on A6 and 100uF on A7. Werner's writeup of the investigations is here: http://people.openmoko.org/werner/gta02-chg/ Thanks - that was most of what I was needing. Unfortunately it doesn't identify the real estate occupied by C1767 there, nor in the component placement diagrams. Can someone point me at the right spot on the board? If it's got enough room for the same 3528 cap we're looking at for the big-C rework (which I doubt, though it looks like it will fit for the big-C position) that would be great. j -- Joel Newkirk http://jthinks.com (blog) http://newkirk.us/om (FR stuff) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL
Steve Mosher st...@openmoko.com writes: If guys raise there hand to help others out I'll come up with a program to help them out/ reward them. If you are willing to raise your hand, drop me a mail. I've talked to a local electronics repair shop here in Bergen, Norway and they said they will do this operation. There, however, should be a package which contain all relevant documentation and complete circuitry and dismantling the freerunner to help a technician easily and quickly do this operation and not waste time finding the documents. -- Esben Stien is b...@e s a http://www. s tn m irc://irc. b - i . e/%23contact sip:b0ef@ e e jid:b0ef@n n ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL
Joel, any update on this? On Thu, Dec 11, 2008 at 7:44 PM, Joel Newkirk freerun...@newkirk.us wrote: I'm going to talk to the guys at work tomorrow and show them the rework PDF - we are equipped to make this fix, could probably offer it inexpensively to those nearby (southeastern North Carolina) or those willing to ship. (among other things - like security systems and internet services - we repair handheld radios and wireless broadband networking gear, including replacing BGAs and more mundane SMD components) I'm betting we have the resistors on hand, would probably need to order a hundred or so of the caps. I'll post back here if the answer is positive. We're located in Hamlet NC, near Ft Bragg, but we're gearing up to offer repairs nationwide for specific wireless networking gear, so shipping and processing of customer repair items in/out is forthcoming anyway, this is just a different board with a much simpler fix to be performed, I'm just not sure they'll be interested in offering it as inexpensively as I'd like. j On Thu, 11 Dec 2008 17:29:32 -0800, Steve Mosher st...@openmoko.com wrote: If guys raise there hand to help others out I'll come up with a program to help them out/ reward them. If you are willing to raise your hand, drop me a mail. st...@openmoko.com Sargun Dhillon wrote: Very cool. Now, all the hardware hackers out there who want to make a buck to fix our Free runners, raise your hands. On Wed, Dec 10, 2008 at 5:31 PM, Steve Mosher st...@openmoko.com wrote: Probably best to send the requests directly to Joerg. Vasco Névoa wrote: I'd really like pictures with better focus and a little more light... especially the last one, which is very blurred! Citando Steve Mosher st...@openmoko.com: Sorry, I pulled the old copy. See below SOP paper (draft3, 2008-12-10 19:00) placed here: http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP__DRAFT3__.pdf Please have a look and report on any mistakes or things that need improvement. Thanks jOERG Neil Jerram wrote: 2008/12/10 Steve Mosher st...@openmoko.com: The DRAFT fix for the buzz problem is here: CP of joerg's mail. http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP__DRAFT!!__.pdf I'm getting 404 for this URL. Neil ___ 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 ___ 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 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Joel Newkirk http://jthinks.com (blog) http://newkirk.us/om (FR stuff) ___ 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: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL
On Tue, 16 Dec 2008 14:21:11 -0800, Sargun Dhillon xbmodder+openm...@gmail.com wrote: Joel, any update on this? Still waiting for an answer from OM. (I posted a question in this thread Friday regarding Tanatalum instead of Ceramic cap - the difference being $0.25 vs $2 each in qty 100, and my radio guy thinks Tant is a good choice for filtering, but waiting for word from Steve or Jeorg) Boss said he's willing to do the jobs, but we have no caps, can't order until we know which ones to order. We're also hoping to find out what help them/reward them involves. (IE, OM provide parts? OM underwrite repair? Cover part of repair? Send me a Christmas card? :) Boss ballparked the job at $25 but nothing definite yet. (depends in part on parts) The only concern they had when I showed them the pdf and my FreeRunner was regarding damaging the housing while soldering - at which point I demonstrated removing the board from the FR with about 30 seconds effort and they said ooh OK then. :) I find myself wondering how many V5 FreeRunners are in the field and whether the owners thereof would want the ability to 'update' to the V6 hardware fixes. I know of the cap on the uSD pins fix for the GPS vs uSD issue (though not the identity of that capacitor), I don't know what change allows a V6 to run without battery or if other differences exist. Dropping a cap on the two pins of the uSD socket is pretty trivial if you're already doing SMD work, so if we're already performing the Big-C rework I'd guess (pure personal speculation) that we could add the cap to the SD lines for little more expense and time. j On Thu, Dec 11, 2008 at 7:44 PM, Joel Newkirk freerun...@newkirk.us wrote: I'm going to talk to the guys at work tomorrow and show them the rework PDF - we are equipped to make this fix, could probably offer it inexpensively to those nearby (southeastern North Carolina) or those willing to ship. (among other things - like security systems and internet services - we repair handheld radios and wireless broadband networking gear, including replacing BGAs and more mundane SMD components) I'm betting we have the resistors on hand, would probably need to order a hundred or so of the caps. I'll post back here if the answer is positive. We're located in Hamlet NC, near Ft Bragg, but we're gearing up to offer repairs nationwide for specific wireless networking gear, so shipping and processing of customer repair items in/out is forthcoming anyway, this is just a different board with a much simpler fix to be performed, I'm just not sure they'll be interested in offering it as inexpensively as I'd like. j On Thu, 11 Dec 2008 17:29:32 -0800, Steve Mosher st...@openmoko.com wrote: If guys raise there hand to help others out I'll come up with a program to help them out/ reward them. If you are willing to raise your hand, drop me a mail. st...@openmoko.com Sargun Dhillon wrote: Very cool. Now, all the hardware hackers out there who want to make a buck to fix our Free runners, raise your hands. On Wed, Dec 10, 2008 at 5:31 PM, Steve Mosher st...@openmoko.com wrote: Probably best to send the requests directly to Joerg. Vasco Névoa wrote: I'd really like pictures with better focus and a little more light... especially the last one, which is very blurred! Citando Steve Mosher st...@openmoko.com: Sorry, I pulled the old copy. See below SOP paper (draft3, 2008-12-10 19:00) placed here: http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP__DRAFT3__.pdf Please have a look and report on any mistakes or things that need improvement. Thanks jOERG Neil Jerram wrote: 2008/12/10 Steve Mosher st...@openmoko.com: The DRAFT fix for the buzz problem is here: CP of joerg's mail. http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP__DRAFT!!__.pdf I'm getting 404 for this URL. Neil ___ 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 ___ 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 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Joel Newkirk http://jthinks.com (blog) http://newkirk.us/om (FR stuff) ___ Openmoko community mailing list community@lists.openmoko.org http
Re: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL
Quick question for Steve/Jeorg: Would a 3528 package capacitor fit? And if so, would Tantalum be suitable instead of Ceramic? My guy here says he'd chose tantalum for filter use like this, and the cost difference is dramatic, though the size is larger than the ceramic shown in the pdf. (price diff: Ceramic around $2 each qty 100, tantalum around $0.25 each qty 100) The resistors are $0.02 each qty 100, so they're practically free. Ceramic: http://mouser.com/Search/ProductDetail.aspx?qs=t7T%252bw6J1MVWG%252bwA9gt9uDg%3d%3d Tantalum: http://mouser.com/Search/ProductDetail.aspx?qs=N31o%252bt096gsr1Po3ON6skg%3d%3d j On Thu, 11 Dec 2008 22:44:30 -0500, Joel Newkirk freerun...@newkirk.us wrote: I'm going to talk to the guys at work tomorrow and show them the rework PDF - we are equipped to make this fix, could probably offer it inexpensively to those nearby (southeastern North Carolina) or those willing to ship. (among other things - like security systems and internet services - we repair handheld radios and wireless broadband networking gear, including replacing BGAs and more mundane SMD components) I'm betting we have the resistors on hand, would probably need to order a hundred or so of the caps. I'll post back here if the answer is positive. We're located in Hamlet NC, near Ft Bragg, but we're gearing up to offer repairs nationwide for specific wireless networking gear, so shipping and processing of customer repair items in/out is forthcoming anyway, this is just a different board with a much simpler fix to be performed, I'm just not sure they'll be interested in offering it as inexpensively as I'd like. j On Thu, 11 Dec 2008 17:29:32 -0800, Steve Mosher st...@openmoko.com wrote: If guys raise there hand to help others out I'll come up with a program to help them out/ reward them. If you are willing to raise your hand, drop me a mail. st...@openmoko.com Sargun Dhillon wrote: Very cool. Now, all the hardware hackers out there who want to make a buck to fix our Free runners, raise your hands. On Wed, Dec 10, 2008 at 5:31 PM, Steve Mosher st...@openmoko.com wrote: Probably best to send the requests directly to Joerg. Vasco Névoa wrote: I'd really like pictures with better focus and a little more light... especially the last one, which is very blurred! Citando Steve Mosher st...@openmoko.com: Sorry, I pulled the old copy. See below SOP paper (draft3, 2008-12-10 19:00) placed here: http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP__DRAFT3__.pdf Please have a look and report on any mistakes or things that need improvement. Thanks jOERG Neil Jerram wrote: 2008/12/10 Steve Mosher st...@openmoko.com: The DRAFT fix for the buzz problem is here: CP of joerg's mail. http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP__DRAFT!!__.pdf I'm getting 404 for this URL. Neil -- Joel Newkirk http://jthinks.com (blog) http://newkirk.us/om (FR stuff) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL
If guys raise there hand to help others out I'll come up with a program to help them out/ reward them. If you are willing to raise your hand, drop me a mail. st...@openmoko.com Sargun Dhillon wrote: Very cool. Now, all the hardware hackers out there who want to make a buck to fix our Free runners, raise your hands. On Wed, Dec 10, 2008 at 5:31 PM, Steve Mosher st...@openmoko.com wrote: Probably best to send the requests directly to Joerg. Vasco Névoa wrote: I'd really like pictures with better focus and a little more light... especially the last one, which is very blurred! Citando Steve Mosher st...@openmoko.com: Sorry, I pulled the old copy. See below SOP paper (draft3, 2008-12-10 19:00) placed here: http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP__DRAFT3__.pdf Please have a look and report on any mistakes or things that need improvement. Thanks jOERG Neil Jerram wrote: 2008/12/10 Steve Mosher st...@openmoko.com: The DRAFT fix for the buzz problem is here: CP of joerg's mail. http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP__DRAFT!!__.pdf I'm getting 404 for this URL. Neil ___ 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 ___ 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 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL
I'm going to talk to the guys at work tomorrow and show them the rework PDF - we are equipped to make this fix, could probably offer it inexpensively to those nearby (southeastern North Carolina) or those willing to ship. (among other things - like security systems and internet services - we repair handheld radios and wireless broadband networking gear, including replacing BGAs and more mundane SMD components) I'm betting we have the resistors on hand, would probably need to order a hundred or so of the caps. I'll post back here if the answer is positive. We're located in Hamlet NC, near Ft Bragg, but we're gearing up to offer repairs nationwide for specific wireless networking gear, so shipping and processing of customer repair items in/out is forthcoming anyway, this is just a different board with a much simpler fix to be performed, I'm just not sure they'll be interested in offering it as inexpensively as I'd like. j On Thu, 11 Dec 2008 17:29:32 -0800, Steve Mosher st...@openmoko.com wrote: If guys raise there hand to help others out I'll come up with a program to help them out/ reward them. If you are willing to raise your hand, drop me a mail. st...@openmoko.com Sargun Dhillon wrote: Very cool. Now, all the hardware hackers out there who want to make a buck to fix our Free runners, raise your hands. On Wed, Dec 10, 2008 at 5:31 PM, Steve Mosher st...@openmoko.com wrote: Probably best to send the requests directly to Joerg. Vasco Névoa wrote: I'd really like pictures with better focus and a little more light... especially the last one, which is very blurred! Citando Steve Mosher st...@openmoko.com: Sorry, I pulled the old copy. See below SOP paper (draft3, 2008-12-10 19:00) placed here: http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP__DRAFT3__.pdf Please have a look and report on any mistakes or things that need improvement. Thanks jOERG Neil Jerram wrote: 2008/12/10 Steve Mosher st...@openmoko.com: The DRAFT fix for the buzz problem is here: CP of joerg's mail. http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP__DRAFT!!__.pdf I'm getting 404 for this URL. Neil ___ 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 ___ 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 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Joel Newkirk http://jthinks.com (blog) http://newkirk.us/om (FR stuff) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL
I'd really like pictures with better focus and a little more light... especially the last one, which is very blurred! Citando Steve Mosher [EMAIL PROTECTED]: Sorry, I pulled the old copy. See below SOP paper (draft3, 2008-12-10 19:00) placed here: http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP__DRAFT3__.pdf Please have a look and report on any mistakes or things that need improvement. Thanks jOERG Neil Jerram wrote: 2008/12/10 Steve Mosher [EMAIL PROTECTED]: The DRAFT fix for the buzz problem is here: CP of joerg's mail. http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP__DRAFT!!__.pdf I'm getting 404 for this URL. Neil ___ 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 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Crackly Calls and Battery Tips! A5/A6 rework. Corrected URL
Probably best to send the requests directly to Joerg. Vasco Névoa wrote: I'd really like pictures with better focus and a little more light... especially the last one, which is very blurred! Citando Steve Mosher [EMAIL PROTECTED]: Sorry, I pulled the old copy. See below SOP paper (draft3, 2008-12-10 19:00) placed here: http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP__DRAFT3__.pdf Please have a look and report on any mistakes or things that need improvement. Thanks jOERG Neil Jerram wrote: 2008/12/10 Steve Mosher [EMAIL PROTECTED]: The DRAFT fix for the buzz problem is here: CP of joerg's mail. http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP__DRAFT!!__.pdf I'm getting 404 for this URL. Neil ___ 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 ___ 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: GPS rework: Please test and report on software fix prior toattempting any hardware fix
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Josh Thompson Sent: Monday, August 04, 2008 5:03 PM To: community@lists.openmoko.org Subject: Re: GPS rework: Please test and report on software fix prior toattempting any hardware fix Could we get a link to some image files to use for this testing? I'm not quite sure when Andy's fix made it in the kernel. It would also help standardize the tests if we all use the same images. Josh On Mon August 4 2008 7:29:17 pm Michael Shiloh wrote: Before we conclude that the hardware fix is required, we'd really like to gather a lot of statistics from you about the behavior of the software fix. We have been able to test in only a limited number of locations, and a limited number of phones. We'd like to ask you to run some tests and report back the TTFF in each case: 1. Prior to Andy's software fix 1a. Without SD card 1b. With SD card 2. Using Andy's software fix 2a. Without SD card 2b. With SD card Preferably run this test in multiple locations. Results should be reported on a wiki page, which should include your location (so we can assess other influences e.g. satellite elevation and weather conditions) Thanks, Michael ___ 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: GPS rework: Please test and report on software fix priorto attempting any hardware fix
A wiki wont do. A proper test proceedure and test report is called for. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Shiloh Sent: Monday, August 04, 2008 5:33 PM To: List for Openmoko community discussion Subject: Re: GPS rework: Please test and report on software fix priorto attempting any hardware fix Agreed. I've been trying to gather that information for the past little while. It's proven rather elusive, and I didn't want more people to try the hardware fix until we really understand what the software fix can do, so I thought I'd better ask for the test ASAP, and then continue working on the info. Andy, can you provide links to two kernels: one before, and one after the fix? The test will consist something like cat /dev/ttySAC1 | grep GPGGA and then time it until it gets a fix. I'll be more specific. Perhaps I'll set up a wiki page for this. Michael Josh Thompson wrote: Could we get a link to some image files to use for this testing? I'm not quite sure when Andy's fix made it in the kernel. It would also help standardize the tests if we all use the same images. Josh On Mon August 4 2008 7:29:17 pm Michael Shiloh wrote: Before we conclude that the hardware fix is required, we'd really like to gather a lot of statistics from you about the behavior of the software fix. We have been able to test in only a limited number of locations, and a limited number of phones. We'd like to ask you to run some tests and report back the TTFF in each case: 1. Prior to Andy's software fix 1a. Without SD card 1b. With SD card 2. Using Andy's software fix 2a. Without SD card 2b. With SD card Preferably run this test in multiple locations. Results should be reported on a wiki page, which should include your location (so we can assess other influences e.g. satellite elevation and weather conditions) Thanks, Michael ___ 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 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GPS rework: Please test and report on software fix priorto attempting any hardware fix
Hello, It seems I have an issue with my GPS, I did the software upgrade (last uboot, abd ASU 2008.8 kernel and rootfs) but still, it takes more than 5 minutes for my GPS to get a fix, without SIM card, without SD card, Without Wifi enable, in a open area What should I do ? do you have a reliable procedure that will concude I have a problem, if it is determine I have a problem, what is the next step ? Regards Philippe On Sun, Aug 10, 2008 at 8:21 PM, steve [EMAIL PROTECTED] wrote: A wiki wont do. A proper test proceedure and test report is called for. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Shiloh Sent: Monday, August 04, 2008 5:33 PM To: List for Openmoko community discussion Subject: Re: GPS rework: Please test and report on software fix priorto attempting any hardware fix Agreed. I've been trying to gather that information for the past little while. It's proven rather elusive, and I didn't want more people to try the hardware fix until we really understand what the software fix can do, so I thought I'd better ask for the test ASAP, and then continue working on the info. Andy, can you provide links to two kernels: one before, and one after the fix? The test will consist something like cat /dev/ttySAC1 | grep GPGGA and then time it until it gets a fix. I'll be more specific. Perhaps I'll set up a wiki page for this. Michael Josh Thompson wrote: Could we get a link to some image files to use for this testing? I'm not quite sure when Andy's fix made it in the kernel. It would also help standardize the tests if we all use the same images. Josh On Mon August 4 2008 7:29:17 pm Michael Shiloh wrote: Before we conclude that the hardware fix is required, we'd really like to gather a lot of statistics from you about the behavior of the software fix. We have been able to test in only a limited number of locations, and a limited number of phones. We'd like to ask you to run some tests and report back the TTFF in each case: 1. Prior to Andy's software fix 1a. Without SD card 1b. With SD card 2. Using Andy's software fix 2a. Without SD card 2b. With SD card Preferably run this test in multiple locations. Results should be reported on a wiki page, which should include your location (so we can assess other influences e.g. satellite elevation and weather conditions) Thanks, Michael ___ 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 ___ 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: GPS rework: Please test and report on software fix prior to attempting any hardware fix
On Tuesday August 5, [EMAIL PROTECTED] wrote: For a bit more consistency of timing, less manual intervention, and enough readings to get an idea of the run to run variation in that location, can I suggest a script? It could do with a timeout when waiting for a fix since with deivestrength 3 and idleclk 1 this can take a _very_ long time, possibly forever in some locations! Thanks for the script. After wondering for a while why it didn't work at all for me, I added stty min 1 /dev/ttySAC1 because either frameworkd in FSO or openmoko-agpsui did an stty min 0 /dev/ttySAC1 and that caused grep to exit immediately. Anyway, I haven't let it run completely yet, but the first result is d i time 0 0 real 9m 52.15s Yes, nearly 10 minutes. This is indoors, but I have had problems getting a GPS fix everywhere, inside, outside, in a car, in the park. Once it fixes it tracks OK (though it doesn't recover from going into a shopping complex and coming out again). It seems a lot like the originally reported problem, but this is with a kernel that has the fix and the magic sysfs files: Linux om-gta02 2.6.24 #1 PREEMPT Tue Jul 29 01:19:38 UTC 2008 armv4tl unknown I have the wireless going, but GSM is possibly turned off as I killed frameworkd to make sure it wasn't touching the GPS. I know someone who I trust to solder the capacitor - should I try that (if I can get hold of him)? Another result just came in: d i time 0 0 real 9m 52.15s 0 1 real 8m 29.79s These numbers are actually pretty good. openmoko-agpsui was giving me 1000 or 2100 seconds! I decided to take out the SD card (and the SIM card) and try again. (just chat quietly among yourselves while we wait for the first result). d i time 0 0 real 5m 14.32s 0 1 real 2m 56.78s 1 0 real 5m 37.79s Well, that wasn't so bad. But still not what I hoped for. I'm wondering if I got a lemon :-( NeilBrown ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SDcard holder - convenience rework
Hehe, i have had a similar idea, but in my case it was the battery. Thanks to jOERG i was able to improve my hack :) papa-piet http://freeyourphone.de Joerg Reisenweber schrieb: for a nice handle to save your fingernails and do no violence on SD-holder by using a knife etc, see: http://people.openmoko.org/joerg/sdcard-handle note the pretty original scotchtape-end of the transparent sticky tape ;-) Works like a charm! cheers jOERG ps: thanks to XorA for triggering the idea by complaining about the varnish-killer ;-) ___ 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
