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
