Re: Heidelberg/Mannheim Cafe Meet

[Michael Tansella]

Very nice I'm from Karlsruhe, too

Greets
Michael


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Someone stole my Neo Freerunner... :(

[Michal Brzozowski]

2009/1/27 Lothar Behrens 

> Hi,
>
> sorry for you all that lost your phone, stolen or lost anyhow by being
> careless. I also had lost a phone, but not my FR :-)
>
> I read the thread, and think about my contract. I have no gprs as of my old
> phone didn't let me opening
> web or wap pages.
>
> I have some questions and ideas that are in my brain :-)
>

I don't know why you guys assume that there will be another user. A scenario
that I think is more probable:

The thief steals the phone, immediately turns it off by taking out the
battery. He then takes it to some 'dealer'. The dealer says, 'what the 
is this, I will never sell it', and throws it away.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: FDOM and GPRS?

[Margo Koppelmann]

On Mon, Jan 26, 2009 at 4:17 PM, Steffen Winkler  wrote:
> Hi,
>
> is it possible to use GPRS with the current FDOM image?
>
> If yes: Is there a GUI or do I have to adjust the config files by hand?
>
> If I've to adjust the config files by hand, is there a howto? (which
> files and what do I've to edit there)


The current FDOM image - you mean FDOM 20081023? I don't know about
that (because it had so many problems and bugs, that I flashed back to
FDOM 20080927 right after trying 20081023), but in FDOM 20080927 it
was easy to get GPRS working. I followed the instructions here -
http://www.teaparty.net/technotes/openmoko-2.html#GPRS . FDOM already
has gsm0710muxd installed, so you have to start from where it says:
"The files needed are ...". I just copied these files to my phone,
changed "mobile.o2.co.uk" in chat-gprs file to my GPRS providers
address and started the connection with ./pppd-start and later killed
the connection with "killall -15 pppd". Probably you can install some
GUI too, but I didn't think it is nessecary. If you don't want to
start it from command line, just make two .desktop files - one for
pppd-start and one for "killall -15 pppd".

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Modified old multitap-pad keyboard‏

[Matthias Camenzind]

Hi,
I modified multitap-pad (wasn't usable). I changed the usability a bit. Now you 
can write by moving your finger around. I tested it on Om2008.12.
I included many special characters. Short list: Ctrl+c, Ctrl+z, Tab, Enter, 
PgUp, PgDn, F1-F12, " ' ()[]{}<>,~/\|*:; ... 
International characters are also included.
 
http://www.opkg.org/package_116.html
install: opkg install libfakekey0 
http://www.opkg.org/packages/multitap-pad_0.1_armv4t.ipk
screenshots: http://www.opkg.org/images/screenshots/written.png 
http://www.opkg.org/images/screenshots/mousedown.png
 
To start the keyboard you need to be faster then other installed keyboards. 
Start it directly after you see the icon called "Mutlitap".

Attached is the modified .c-file. Original source: 
http://downloads.openmoko.org/sources/multitap-pad_svn.o-hand.com_.repos.misc.trunk_373_.tar.gz
_
Die neue Generation der Windows Live Services - jetzt downloaden!
http://download.live.com

multitap-pad-main.c.gz
Description: GNU Zip compressed data
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Alsa state chooser

[Al Johnson]

On Tuesday 27 January 2009, TL Mieszkowski wrote:
> I'm not sure what the status of the Dbus sound stuff is, but I wrote a
> little program to choose the alsa state file with a simple gui. Attached is
> the code in anyone is interested. All it is is 1 button for each state
> file, very simplistic, uses elementary. (which btw kicks ass Raster)
>
> You would run it like so:
> scalpel `ls -1 /usr/share/openmoko/scenarios/`
> meh, whatever, works for me
>
> -Tim
>
> http://n2.nabble.com/file/n224/scalpel.c scalpel.c

The FSO API can list and change the alsa scenarios with stack based 
management. It will also send a signal on scenario change so that interested 
apps are aware of it. See:

http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.Device.Audio.html;hb=HEAD

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

RE: buzz fix

[KaZeR]

They've been really silent (ignoring us?) on this point each time it has
been asked.
 

> -Message d'origine-
> De : community-boun...@lists.openmoko.org 
> [mailto:community-boun...@lists.openmoko.org] De la part de 
> Christoph Siegenthaler
> Envoyé : lundi 26 janvier 2009 13:21
> À : community@lists.openmoko.org
> Objet : RE: buzz fix
> 
> 
> Hello,
> 
> are there any updates from resellers, FIC or any 
> half-official DIY-tutorials on the hardware problems, i.e. 
> the buzzing?
> 
> Best regards, Chris
> 
> 
> 
> KaZeR wrote:
> >  
> > 
> >> -Message d'origine-
> >> [mailto:community-boun...@lists.openmoko.org] De la part 
> de Christoph 
> >> Pulster Envoyé : mardi 13 janvier 2009 08:20 À : 
> >> community@lists.openmoko.org Objet : Re: buzz fix
> >> 
> >> Hello,
> >> 
> >> thanks for asking about hardware fixes (I read this list daily).
> >> At the moment I'm working out a solution with Openmoko how 
> to handle 
> >> any repair (buzz SOP, GPS fix etc).
> >> In any way I want to offer my customers best service and we try to 
> >> find a solution which does avoid time-consuming return 
> shipments to 
> >> Taiwan.
> >> Please allow us some days to work that out.
> >> 
> > 
> > Thanks Christoph. 
> > It's nice to see that you are so involved.
> > I hope that you will lead the way for other resellers. 
> > Bearstech maybe? :)
> > 
> > 
> > ___
> > Openmoko community mailing list
> > community@lists.openmoko.org
> > http://lists.openmoko.org/mailman/listinfo/community
> > 
> > 
> 
> --
> View this message in context: 
> http://n2.nabble.com/buzz-fix-%28was%3A-Pulster-offer---Freeru
> nner-now-249-eur%29-tp2141213p2217591.html
> Sent from the Openmoko Community mailing list archive at Nabble.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: Someone stole my Neo Freerunner... :(

[arne anka]

> I don't know why you guys assume that there will be another user. A  
> scenario
> that I think is more probable:
>
> The thief steals the phone, immediately turns it off by taking out the
> battery. He then takes it to some 'dealer'. The dealer says, 'what the  
> 
> is this, I will never sell it', and throws it away.


exactly.
therefore i think, the proposed label inside the back cover, offering a  
reward when contacted via / and fr returned, would be far  
more promising.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

RE: Someone stole my Neo Freerunner... :(

[KaZeR]

 

> -Message d'origine-
 
> 
> exactly.
> therefore i think, the proposed label inside the back cover, 
> offering a  
> reward when contacted via / and fr returned, 
> would be far  
> more promising.

Would sound like a trap for the thief, no? (even if it's worth trying).

I got a bag stolen in train last month. It only contained papers for my work, 
my mail from the day, and my glasses.
Bag itself was worth something like 10€. I guess it ended in a trash.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Someone stole my Neo Freerunner... :(

[Matthias Apitz]

El día Tuesday, January 27, 2009 a las 10:58:49AM +0100, arne anka escribió:

> > I don't know why you guys assume that there will be another user. A  
> > scenario
> > that I think is more probable:
> >
> > The thief steals the phone, immediately turns it off by taking out the
> > battery. He then takes it to some 'dealer'. The dealer says, 'what the  
> > 
> > is this, I will never sell it', and throws it away.
> 
> 
> exactly.
> therefore i think, the proposed label inside the back cover, offering a  
> reward when contacted via / and fr returned, would be far  
> more promising.

exactly; mine has a label inside:

 +---+
 | If you got this device, let's |
 | asume you have found it, please   |
 | call +49-89-61308-351. I offer a  |
 | 100 Euro reward on device return. |
 +---+

HIH :-)

matthias


-- 
Matthias Apitz
Manager Technical Support - OCLC GmbH
Gruenwalder Weg 28g - 82041 Oberhaching - Germany
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e  - w http://www.oclc.org/ http://www.UnixArea.de/
b http://gurucubano.blogspot.com/

SPAMer of the year: Subject: Alle Software ist Deutsche Sprachen
>From: -40 % die Neujahrsaktion 

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: multitouch possible?

[Fernando Martins]

kris Occhipinti wrote:
> I agree that it is a hardware limitation.
> But, you never know what some one will come up.
> One day someone may come up with an idea the rest of us never thought 
> about.
Yes, just for the folklore, this reminds me of the old ZX Spectrum 
console which had only 16 colours until someone figured out that if they 
switched two colours on a pixel fast enough the eye would perceive the 
combined colour. A new era of beautiful games started there :-)

Fernando

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: what tests for (non working) 3G SIM?

[Robert Piasek]

On Monday 26 January 2009 20:53:24 Chris Syntichakis wrote:
> Hi,
>
> As I see the SIM from 3mobile (UK) is not working with the GTA02v6 (running
> SHR unstable).

As far as I'm aware (Hutchison 3G) - Three - is UMTS 2100 _only_ and won't 
work with 2G phones like GTA02/GTA03. I've updated my firmware and still can't 
use it with Three. That makes my Freerunner a toy and not daily phone. 
Currently I've got 3G simcard from O2 (which is 2G/3G network) and it 
registers (after firmware update). 

Let's hope GTA04/05 will be 3G.

> Should I run any debugging tests (just for your info..)?
> If so, what can I do?

There is nothing you can do.

Rob



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: Someone stole my Neo Freerunner... :(

[Helge Hafting]

The Digital Pioneer wrote:
> And when you think you've tracked down the thief and are close to
> him, send an sms to make it play some music really really loud, and
> go bang the thief on the head :)
> 
> Sounds fun. I send the SMS, and suddenly a piercing siren goes off from 
> the guy 10 feet away, so I tackle him and take back my phone. :D I like 
> how you think. 
> 
> Just one little consideration: how best to turn off stolen-mode when I 
> get it back? Sending an SMS won't do (way too easy to spoof), it needs 
> to be something that can only be done by SSH or the like I think.

Enter the 20-letter password that only you know about - or reflash.

The thief also has the option of reflashing - but most of them don't 
know how. If they did - they'd likely be able to earn better working 
with electronics/computers.

If you really hate thieves, fill all free space inside the case with 
explosive. Send the stolen phone a sms containing the key for 
self-destruct mode. In this mode it explodes a few seconds after 
accepting a call - the maximum damage moment when you get both the hand 
and the head.

I would not recommend this though. It'd be illegal most places, and 
you'd have to be really confident about programming the trigger. (And 
then there is static electricity...)

A safer self-destruct mode would be to erase all the flashes, including 
the one in the gsm modem. No boot or usb-based reflash after that, and 
thieves will not likely bother trying a debug board "to see if it can be 
fixed". If they are that good, they probably make a decent living 
unlocking/servicing other brands of phone already.

Such a self-destruct might be useful when the phone is stolen on a trip 
and you don't want to follow the thief into a dubious and unknown 
district. And you probably don't have all the tracking equipment (extra 
gps & phone) with you either.

Helge Hafting


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

[OM 2008.12] Wicd and Python

[Francesco de Virgilio]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi all,
I've installed Wicd from opkg.org[1] but I get the same error of Pander:

# wicd-client
Traceback (most recent call last):
File "/usr/lib/wcud/wcid-client.py", line 48, in 
import wcid.wpath as wpath
ImportError: No module named wicd.wpath

How could this be solved pratically?

Thanks,

[1] http://www.opkg.org/package_114.html
- --
Francesco de Virgilio
*Ubuntu-it Member and Wiki Editor*
   mailto:frad...@ubuntu-it.org
   http://wiki.ubuntu-it.org/FrancescoDeVirgilio
*Wikimedia Italia Member*
   http://en.wikipedia.org/wiki/User:Fradeve11
*OpenStreetMap Mapper*
   http://www.openstreetmap.org/user/Fradeve11
*Blog*
   http://fradeve.netsons.org
"Love - Peace - Freedom - Free Software"
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkl+678ACgkQRi2TsGSC4FZuugCdEXurhaYLhXUENsXDtekDE240
m+MAn15tU9GgL/IFFaivoXrp9ETyEW5g
=knMn
-END PGP SIGNATURE-

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Someone stole my Neo Freerunner... :(

[Helge Hafting]

Angus Ainslie wrote:
> On Mon, Jan 26, 2009 at 6:19 AM, Helge Hafting  wrote:
>> There is a program around that is supposed to look for a special keyword
>> in a sms, and send a gps reading back. It didn't work when I tried it,
>> but this appraoch can be developed into something more robust. Another
>> other security idea: Send an SMS to put the phone in "stolen" modus. (Do
>> that quickly, before they change the sim card.)
>>
> 
> Are you talking about sms-sentry ?
> 
> Which part didn't work ?

I sent the message, from the phone to itself. This was right after 
installing it. Of course, there was no gps fix inside the building,
I didn't expect that to work well.

Later I was on a car trip, not driving. So I watched tangogps for a 
while. Then I got the idea to test again, knowing that the gps was 
working. So I sent the message again - from the phone to itself. And 
again nothing happened.  The keyed message eventually showed up in the 
sms inbox, with the first letter removed. Tangogps showed movement all 
the time. I tried twice, but I never got a reply with any coordinates.

> What distro did you try it on ?
> 
SHR of dec.16, which I still use. A good distro in that calls, sms, 
music, and gps all works - although it could use some polishing.

> Did you run it from the command line and check what status messages it
> was sending ?
>
I didn't think of that, it is worth a try.


> It works but can take a very very long time to get a fix and return
> the SMS you are waiting for.
> 
I know - so therefore I tested it when I already had a good fix. gpsd is 
supposed to be able to serve several clients at the same time.

Helge Hafting

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: SHR Unstable

[Helge Hafting]

Joel Newkirk wrote:
> On Mon, 26 Jan 2009 09:36:56 -0800 (PST), Chris Syntichakis
>  wrote:
>> Hi,
>>
>> How can I activate the GPS with the SHR?
>>
>> I open the tangoGPS but I got no info if the gps is on or getting data..
>>
>> Chris
> 
> The line of text across below the map view (above the Map|Trip|Track etc
> tabs) shows GPS info as does the Trip display.  Of particular interest on
> the map view is the last group of characters - 0/0/0.0 when first started. 
> On mine (SHR-unstable+updates) it changes to "12/0/0.0" after about 10-15
> seconds.  The "12" is referring to 12 satellites for which it thinks it has
> positions.  The second number is the number of those satellites it is
> actually tracking.  For me that stays at zero (no fix until 3-4 sats
> tracked) for anywhere from 45 secs to 5 mins depending on sky visibility,
> at which point I almost always pick up 3-5 sats at once and have first fix.
> 
when debugging, try the "trip" page of tangogps.
It will show "gps time" long before it gets a fix - I guess this is 
because it tracks 1 satellite. Not enough for a position, but enough to 
get displayable time.

Helge Hafting

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: what tests for (non working) 3G SIM?

[Chris Syntichakis]

Hi,

I see.. Today I tested the card with a Nokia 1110i , it said "card
rejected", then I did a test with a samsung c170 and I got the message "SIM
crashed" (LOL)

Thanx for the tip about O2..

chris


> As far as I'm aware (Hutchison 3G) - Three - is UMTS 2100 _only_ and won't
> work with 2G phones like GTA02/GTA03. I've updated my firmware and still
> can't
> use it with Three. That makes my Freerunner a toy and not daily phone.
> Currently I've got 3G simcard from O2 (which is 2G/3G network) and it
> registers (after firmware update).
>
>
-- 
╒══╕
│░ ≡│
└──┘

-- 
View this message in context: 
http://n2.nabble.com/what-tests-for-%28non-working%29-3G-SIM--tp2220544p2223741.html
Sent from the Openmoko Community mailing list archive at Nabble.com.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Dead Neo 1973 - drained battery

[Niall Haslam]

On Saturday 24 January 2009 18:45, Andy Selby wrote:
> Try leaving the battery out over night then reinserting it and charging it.
> I've got a neo1973 on its original battery so yours should still work
> You can get a very cheap battery and charger from ebay, I provided a
> link in a previous post
> http://www.mail-archive.com/community@lists.openmoko.org/msg28392.html

Those links are no longer active as they link to ebay offers. Could you supply 
a link to something more longterm. I'm interested in getting one of these as 
I am sure are others.

> ___
> 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: svgalib

[Helge Hafting]

Mickael Labrousse wrote:
> Hi,
> 
> Is there a package of svgalib available for the freerunner ?

I am not sure that is possible - my understanding is that the freerunner 
doesn't have a vga-compatible screen. It is vga-sized, thats it.

You should be able to use a framebuffer driver if what you want is 
garphics without X.

Helge Hafting

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

[to moko developers] JOG DIAL

[bytestore]

Can be to make jog dial instead of the button aux? It is convenient to thumb
through upwards downwards in browsers and other. jog dial should be with
function button 

example http://mnovosti.ru/images/old/0/6/img_385762_157.jpg 
-- 
View this message in context: 
http://n2.nabble.com/-to-moko-developers--JOG-DIAL-tp2225172p2225172.html
Sent from the Openmoko Community mailing list archive at Nabble.com.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Pimlico on the Freerunner ?

[Helge Hafting]

The Digital Pioneer wrote:
> I was discussing how you might do this on IRC. The problem is when 
> multiple apps are trying to wake up from suspend; I understand the 
> hwclock interrupt can only have one value. You need a program managing a 
> priority queue of interrupts or the like. I suggested using cron for 
> this, but I'm not strong enough with the source to hack it myself. :P

Apps should definitely not program the timer themselves.
They should call into linux instead, for example by sleeping until the 
desired point in time.

Linux already support hundreds of sleeping apps using only one timer on 
a pc. The timer is simply set to expire at the first upcoming event.
I don't know if the freerunner kernel uses a timer capable of
waking the phone from suspend when managing sleeping processes - but it 
could be made to do so.

Helge Hafting

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [to moko developers] JOG DIAL

[Yorick Moko]

not bad
could also be used to control volume of speakers/mic

On Tue, Jan 27, 2009 at 12:56 PM, bytestore  wrote:
>
> Can be to make jog dial instead of the button aux? It is convenient to thumb
> through upwards downwards in browsers and other. jog dial should be with
> function button
>
> example http://mnovosti.ru/images/old/0/6/img_385762_157.jpg
> --
> View this message in context: 
> http://n2.nabble.com/-to-moko-developers--JOG-DIAL-tp2225172p2225172.html
> Sent from the Openmoko Community mailing list archive at Nabble.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: shr- GPS howto?

[Helge Hafting]

arne anka wrote:

> - the solution you are pointing to, was only some rough first draft.
> the kernel patch used eventuially works different.

Thank you for the information.

Helge Hafting

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: buzz fix

[Al Johnson]

On Monday 26 January 2009, Christoph Siegenthaler wrote:
> are there any updates from resellers, FIC or any half-official
> DIY-tutorials on the hardware problems, i.e. the buzzing?

The current tutorial is here:
http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP_rc2.pdf

This appears to have benefited from feedback regarding capacitor types from 
the few people so far to have attempted the mod, but more feedback is 
requested. The lack of feedback from people trying it may be why it hasn't 
yet made it past release candidate stage.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

[SHR] python-elementary API

[Giorgio Marciano]

Hi,

i want to play with enlightenment gui programming for SHR but i can't
find such a documentation..

where can i find python-elementary APIs and some useful documentation?

-- 
Be Yourself @ mail.com!
Choose From 200+ Email Addresses
Get a Free Account at www.mail.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: what tests for (non working) 3G SIM?

[Al Johnson]

On Tuesday 27 January 2009, Chris Syntichakis wrote:
> Hi,
>
> I see.. Today I tested the card with a Nokia 1110i , it said "card
> rejected", then I did a test with a samsung c170 and I got the message "SIM
> crashed" (LOL)

That mirrors my experience with a friend's 3 SIM last week. This one was 
bought with one of their  USB data dongles. After my GTA02 with moko10 
rejected the SIM we tried it in his Nokia Communcator which also failed to 
recognise it.

If you look at 3's T&Cs you will see that it's a violation to use the SIM in a 
non-3G device anyway.

> Thanx for the tip about O2..

Also works with t-mobile, Virgin and Orange. 

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Conflict when several apps use the accelerometers?

[Helge Hafting]

Gunnar Aastrand Grimnes wrote:
> This page does: http://wiki.openmoko.org/wiki/Accelerometer_Fundamentals
> 
> Noise is around 3cm/s^2, i.e:
> 
> "
> It can fill in _short_ - 3-5s gaps in GPS coverage, if the orientation
> of the phone is known.

Not enough for a 4km tunnel then, which is 3 min when going 80km/h.
5s is enough for a 111m tunnel, but 5s signal loss is usually not a 
problem anyway.

Of course, the car speedometer readout can take care of speed and 
braking/acceleration, the accelerometer would only be needed to notice 
turning. Could be interesting to see where it thinks I am after 3 min, 
if 5s is all I can expect. I guess those 3-5s is the interval where 
precision matces the gps. But it will be useful for longer than that, as 
long as estimate is more accurate than "stopped at the tunnel entrance."

The error increase with time, but so do the real distance from the entrance.

Helge Hafting


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: buzz fix (was: Pulster offer - Freerunner now 249 eur)

[Helge Hafting]

Al Johnson wrote:
> On Tuesday 13 January 2009, Yorick Moko wrote:
>> buzz and gsm fixes are even documented on the wiki (no need to search
>> in the e-mails)
>> only the audio-fix (big capacitator to provide more bass isn't; hoping
>> to see that one documented as well
> 
> There's some fairly detailed discussion of audio mods on the hardware list 
> which could be copied into the wiki, but there is no 'official' mod. I 
> suspect there won't be one either, mostly because big caps won't fit in the 
> space available, and relocating them to outside the screening can could 
> easily reintroduce buzz.

Another option:
Short the too small capacitors, so there are no capacitors at all. Then 
add the big caps outside the screeming, but this time with no need to 
connect to anything inside the screening.  Just break the connection 
anywhere, and insert a nice big cap. The easiest place of all then, is 
obviously to add the caps to the headset. Of course then you only have 
one useable headset.

Or break the connection between the plug and circuit board, and put the 
caps somewhere inside. There is lots of room above the SIM card.

Helge Hafting



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: multitouch possible?

[Charles Pax]

On 1/27/09, Fernando Martins  wrote:
>
> kris Occhipinti wrote:
> > I agree that it is a hardware limitation.
> > But, you never know what some one will come up.
> > One day someone may come up with an idea the rest of us never thought
> > about.
> Yes, just for the folklore, this reminds me of the old ZX Spectrum
> console which had only 16 colours until someone figured out that if they
> switched two colours on a pixel fast enough the eye would perceive the
> combined colour. A new era of beautiful games started there :-)


Hmm. Interesting point. We'll need to know how much control we have over the
touch screen controller, but let's throw around some theories. What would
happen if the voltage given to the touch screen controller were varried at
some frequency or through a rnage of frequencies? Maybe we would find that
we could measure some resonance frequency and coorelate that (along with
some other measurable data) to more than one contact point.

-Charles Pax
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: multitouch possible?

Charles Pax schrieb:
> On 1/27/09, *Fernando Martins*  > wrote:
>
> kris Occhipinti wrote:
> > I agree that it is a hardware limitation.
> > But, you never know what some one will come up.
> > One day someone may come up with an idea the rest of us never
> thought
> > about.
> Yes, just for the folklore, this reminds me of the old ZX Spectrum
> console which had only 16 colours until someone figured out that
> if they
> switched two colours on a pixel fast enough the eye would perceive the
> combined colour. A new era of beautiful games started there :-)
>
>  
> Hmm. Interesting point. We'll need to know how much control we have 
> over the touch screen controller, but let's throw around some 
> theories. What would happen if the voltage given to the touch screen 
> controller were varried at some frequency or through a rnage of 
> frequencies? Maybe we would find that we could measure some resonance 
> frequency and coorelate that (along with some other measurable data) 
> to more than one contact point.
>
> -Charles Pax
> 
i found something, although, they (of course) dont tell how the did it:
http://www.tycoelectronics.com/aboutus/news/prodnews.asp?id=1584
 and i am quite sure they use different hardware
http://www.tycoelectronics.com/aboutus/news/prodnews.asp?id=1584

...btw i read that gta03 will introduce capacitive touchscreen (its in 
the wiki).
why the hell would anyone want this?

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: multitouch possible?

[Christ van Willegen]

On Tue, Jan 27, 2009 at 2:22 PM, Charles Pax  wrote:
> Hmm. Interesting point. We'll need to know how much control we have over the
> touch screen controller, but let's throw around some theories. What would
> happen if the voltage given to the touch screen controller were varried at
> some frequency or through a rnage of frequencies? Maybe we would find that
> we could measure some resonance frequency and coorelate that (along with
> some other measurable data) to more than one contact point.

ISTR that one of the core developers played with the idea of sweeping
the screen in a few directions to see if this would work out. No idea
if he did this, and what he came up with...

Christ van Willegen
-- 
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [SHR] python-elementary API

[Valery Febvre]

Giorgio Marciano wrote:
> Hi,
> 
> i want to play with enlightenment gui programming for SHR but i can't 
> find such a documentation..
> 
> where can i find python-elementary APIs and some useful documentation?

A nice article is available on enlightenment website wiki

http://trac.enlightenment.org/e/wiki/Elementary

Examples are written in C :-(

I don't know if an API doc is avaible for the python binding.

You can find one example in sources:

http://trac.enlightenment.org/e/browser/trunk/BINDINGS/python/python-elementary/tests/test.py

-- 
Valéry

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: buzz fix (was: Pulster offer - Freerunner now 249 eur)

[Al Johnson]

On Tuesday 27 January 2009, Helge Hafting wrote:
> Al Johnson wrote:
> > On Tuesday 13 January 2009, Yorick Moko wrote:
> >> buzz and gsm fixes are even documented on the wiki (no need to search
> >> in the e-mails)
> >> only the audio-fix (big capacitator to provide more bass isn't; hoping
> >> to see that one documented as well
> >
> > There's some fairly detailed discussion of audio mods on the hardware
> > list which could be copied into the wiki, but there is no 'official' mod.
> > I suspect there won't be one either, mostly because big caps won't fit in
> > the space available, and relocating them to outside the screening can
> > could easily reintroduce buzz.
>
> Another option:
> Short the too small capacitors, so there are no capacitors at all. Then
> add the big caps outside the screeming, but this time with no need to
> connect to anything inside the screening.  Just break the connection
> anywhere, and insert a nice big cap. The easiest place of all then, is
> obviously to add the caps to the headset. Of course then you only have
> one useable headset.

Yes, that's one of the options discussed, along with some resistors you might 
like to remove. You could put the caps in a 2.5mm to 3.5mm ( or even 1/4in) 
adaptor cable to make it usable with generic headphones. I don't personally 
like this solution for 2 reasons; one day I will forget and stick dc on a 
headset, and it will probably prevent use of the serial debug interface to 
the gsm. The second objection won't be a consideration for the vast majority 
of people though.

> Or break the connection between the plug and circuit board, and put the
> caps somewhere inside. There is lots of room above the SIM card.

This is harder than it sounds IIRC, but feel free to try. I had my eye on that 
space for caps too as the existing caps are very close to it. You could make 
a small hole in the screening can to pass the wires through, but would need 
to be careful to avoid creating an rf pathway.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: multitouch possible?

[Charles Pax]

On 1/27/09, Fernando Martins  wrote:
>
> kris Occhipinti wrote:
> > I agree that it is a hardware limitation.
> > But, you never know what some one will come up.
> > One day someone may come up with an idea the rest of us never thought
> > about.
> Yes, just for the folklore, this reminds me of the old ZX Spectrum
> console which had only 16 colours until someone figured out that if they
> switched two colours on a pixel fast enough the eye would perceive the
> combined colour. A new era of beautiful games started there :-)


Hmm. Interesting point. We'll need to know how much control we have over the
touch screen controller, but let's throw around some theories. What would
happen if the voltage given to the touch screen controller were varried at
some frequency or through a rnage of frequencies? Maybe we would find that
we could measure some resonance frequency and coorelate that
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: what tests for (non working) 3G SIM?

[Arigead]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Chris Syntichakis wrote:
> Hi,
> 
> As I see the SIM from 3mobile (UK) is not working with the GTA02v6 (running
> SHR unstable).
> 
> Should I run any debugging tests (just for your info..)?
> If so, what can I do?
> 
> Chris
> 

3mobile Ireland SIM doesn't work in the GTA02v05 either. Haven't had a
chance to look into it.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkl/GLQACgkQXlbjSJ5n4BDU6wCghFfOp4GoRVJXL++EgY65M0W0
ea0AoNxKMKVvi+kd5F4+C5nWjuX9WWCF
=NRjg
-END PGP SIGNATURE-

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: what tests for (non working) 3G SIM?

[Sargun Dhillon]

When reporting broken 3G SIMs please give us the output of:
r...@om-gta02:~# cat /dev/ttySAC0 &
r...@om-gta02:~# echo -en 'AT\r' >/dev/ttySAC0
r...@om-gta02:~# echo -en 'AT+CGMR\r' >/dev/ttySAC0
+CGMR: "HW: GTA, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal_amd8_ts0-Moko10"
r...@om-gta02:~# kill %1

-Thanks

On Tue, Jan 27, 2009 at 6:22 AM, Arigead  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Chris Syntichakis wrote:
>> Hi,
>>
>> As I see the SIM from 3mobile (UK) is not working with the GTA02v6 (running
>> SHR unstable).
>>
>> Should I run any debugging tests (just for your info..)?
>> If so, what can I do?
>>
>> Chris
>>
>
> 3mobile Ireland SIM doesn't work in the GTA02v05 either. Haven't had a
> chance to look into it.
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkl/GLQACgkQXlbjSJ5n4BDU6wCghFfOp4GoRVJXL++EgY65M0W0
> ea0AoNxKMKVvi+kd5F4+C5nWjuX9WWCF
> =NRjg
> -END PGP SIGNATURE-
>
> ___
> 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: Someone stole my Neo Freerunner... :(

[Angus Ainslie]

On Tue, Jan 27, 2009 at 4:23 AM, Helge Hafting  wrote:
> Later I was on a car trip, not driving. So I watched tangogps for a
> while. Then I got the idea to test again, knowing that the gps was
> working. So I sent the message again - from the phone to itself. And
> again nothing happened.  The keyed message eventually showed up in the
> sms inbox, with the first letter removed. Tangogps showed movement all
> the time. I tried twice, but I never got a reply with any coordinates.
>

If the first letter is missing then it won't work as the match has to
be complete. This seems to be some kind of network ( or possibly
Freerunner specific issue ) as I've had the missing character reported
before. I have always tested by sending from a different phone. I'll
test again using the freerunner to track itself.

>> What distro did you try it on ?
>>
> SHR of dec.16, which I still use. A good distro in that calls, sms,
> music, and gps all works - although it could use some polishing.
>
>> Did you run it from the command line and check what status messages it
>> was sending ?
>>
> I didn't think of that, it is worth a try.
>
>
>> It works but can take a very very long time to get a fix and return
>> the SMS you are waiting for.
>>
> I know - so therefore I tested it when I already had a good fix. gpsd is
> supposed to be able to serve several clients at the same time.
>

SHR uses fso-gpsd and the will handle multiple clients.

Angus

-- 
Angus Ainslie
http://www.handheldshell.com/

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Buzz fix attempt, tomorrow

[Yoann ARNAUD]

kimaidou a écrit :
> Hi Yoan,
> 
> I am about to buy the capacitor and resistor and ask a friend to do the buzz
> fix. Before diving into trouble water, I would really apreciate some
> feedback on your attemp :

Oh yes, I have to do that. I want to make a useful report but I have no
time for this

> * did you succeed ?

Yes, but it was very very hard. And my fix is very ugly.

> * is the buzz canceled ?

Yes :)

> * have you taken photographs on your work ?

Yes, but they are poor quality. The coponents are very very small and I
had to be close to the phone taking the pictures.

I'll try to make the pictures available tonight.


Just an advice. Be aware that the coponents of the phone are very small
(about 1mm) and it's very hard to desolder just the resistor and not the
other neighbour coponents (I desoldered one conensator...) and it's
harder to solder the new components. (that's why my fix is ugly because
we had to repair that)


-- 
Yoann.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: buzz fix

[Neng-Yu Tu (Tony Tu)]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi KaZeR-

We are not ignoring about the buzz fix issue, actually we are very
serious about this bug and fix.

The buzz issue mostly comes from EMI (Electromagnetic Disturbance), and
it's hardware design related. Buzz comes from
mechanical/layout/component/schematics, and each part could have
eliminate some level EMI effect (buzz).

By apply a filter, and change audio configuration, we could make FR have
better noise resist in audio trace. But EMI still comes through
mechanical(antenna position close to mic), layout (already in FR printed
circuit board), and component (microphone as small antenna get EMI)

joerg already publish release candidate version SOP of buzz fix, the
reason it stay in rc and did not have update is:

#1 Can't tell how much it could improve, yet

As described above, buzz fix actually is EMI resist fix/workaround,
Currently, we have 2 feedback from kindly community member help verify
joerg's SOP, and have positive result. Community do a great work on
verification, but we don't finish internal/mass verification for how
much it could improve.

#2 Don't have the test SOP/audio file for this rework

For GPS hardware SOP, it's easy to tell if you could get a fix within 3
minutes with GPS application and NMEA string, but for audio rework in
field, it could only tell by callee's ear. So after rework's pass/fail
test method and audio alsa (A6 rework) file not ready yet.

Upon this 2 reasons, this fix stay in rc, even this fix already used in
some phones and get positive result.

Regards,

- --
Neng-Yu Tu (Tony Tu)
Openmoko, Inc.
Support.

> They've been really silent (ignoring us?) on this point each time it has
> been asked.
>  
> 
>> -Message d'origine-
>> De : community-boun...@lists.openmoko.org 
>> [mailto:community-boun...@lists.openmoko.org] De la part de 
>> Christoph Siegenthaler
>> Envoyé : lundi 26 janvier 2009 13:21
>> À : community@lists.openmoko.org
>> Objet : RE: buzz fix
>>
>>
>> Hello,
>>
>> are there any updates from resellers, FIC or any 
>> half-official DIY-tutorials on the hardware problems, i.e. 
>> the buzzing?
>>
>> Best regards, Chris
>>
>>
>>
>> KaZeR wrote:
>>>  
>>>
 -Message d'origine-
 [mailto:community-boun...@lists.openmoko.org] De la part 
>> de Christoph 
 Pulster Envoyé : mardi 13 janvier 2009 08:20 À : 
 community@lists.openmoko.org Objet : Re: buzz fix

 Hello,

 thanks for asking about hardware fixes (I read this list daily).
 At the moment I'm working out a solution with Openmoko how 
>> to handle 
 any repair (buzz SOP, GPS fix etc).
 In any way I want to offer my customers best service and we try to 
 find a solution which does avoid time-consuming return 
>> shipments to 
 Taiwan.
 Please allow us some days to work that out.

>>> Thanks Christoph. 
>>> It's nice to see that you are so involved.
>>> I hope that you will lead the way for other resellers. 
>>> Bearstech maybe? :)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkl/O+AACgkQmV6sZhhBn29PUgCgqSNwRikVaM2JIVrmRO35Wg7B
ROkAnjPnP55u855+CkMnbZyqEPHUp5Yp
=+wt6
-END PGP SIGNATURE-

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Someone stole my Neo Freerunner... :(

[bburdette]

If you don't want to risk being sued for a booby trapped phone, how 
about at least a way to render the it useless to thieves?

For instance, you could make it unbootable from a zero power situation, 
and then combine that with a rapid power discharge.  If the thief leaves 
it uncharged for even a day, its bricked!


Jeff Sadowski wrote:
> Oooh :-) Idea: Make it shock the user if its not the right user. I
> smell smoke I think it is coming from over there. Hey look there is my
> phone. next to a flaming POS.
> 
> On Mon, Jan 26, 2009 at 4:59 PM, Lothar Behrens
>  wrote:
>> Hi,
>> sorry for you all that lost your phone, stolen or lost anyhow by being
>> careless. I also had lost a phone, but not my FR :-)
>> I read the thread, and think about my contract. I have no gprs as of my old
>> phone didn't let me opening
>> web or wap pages.
>> I have some questions and ideas that are in my brain :-)
>> Is there any way to use analog modem connections ?
>> I don't know how much CPU power is needed but when possible a phone could
>> send more data to a dedicated
>> number we could provide for that.
>> If a real modem connection couldn't be used, what about creating a tone
>> modulation for the data to be send
>> as a 'spoken' message to be send back to a number as a voice recorder.
>> The voice recorder then (a Linux PC :-) could decode the data and store the
>> data.
>> All the data could be collected on a web service to probably get the bad
>> guys behind to give that information to
>> the police.
>> The web service also could provide information about stolen devices, thus
>> when a phone gets any wlan connection,
>> it could check for stolen state. This is not that spoof able I think,
>> because the web sevice may be as usual password protected.
>> But the server could provide sms, mms or phone gateways for fallback
>> options. More gateways could be provided by us.
>> The new gateway information could be uploaded by interacting with the user
>> (software updates :-)
>> If a phone didn't have gprs, sms, mms, or wlan, sending prepared 'data
>> voices' would be an option. It didn't need to send much at first to get
>> an answer about the stolen state in that way. I think the recorded data
>> could be decoded in both directions, you don't need
>> much cpu power, because it will be unidirectional, or let the 'protocol'
>> enough time between packed sent and anser packets
>> for decoding.
>> Doing an active voice call may save us the cost of callbacks or sending back
>> sms. With a proper longtime protocol with long pauses or a
>> better solution a lot could be done.
>> Usually you could activate this when the sim card get's changed without any
>> notice to the user. He should still use the phone a while
>> to collect information. We then could start a preinstalled application to
>> authenticate the sim card change. If not options are many.
>> The PIN entry of the normal card could be replaced by the PIN you
>> provide. The user then wouldn't realize it, but claims to enter
>> the correct, we simply accept, but start the timer for the above actions.
>> Or we leave the user in claim that the documentation of it's sim card
>> provider doesn't seem to be correct and he/she must issue
>> a call with the service provider.
>> At that point, the service provider couldn't help for that special phone.
>> The new 'user' HAS to contact the manufacturer and so on
>> you probably get your phone back, because the manufacturer should request
>> for sending back the phone.
>> Getting the state of stolen, the phone could anyway send a message to a
>> police station near the user with spd-say, after
>> the 'anti-theft' server has located the next police station's telephone
>> number with any of the above options sent back to the
>> phone. (Maybe with manual data entry of the phone numbers by us users with
>> POI collection, hehe tangoGPS :-)
>> That way the phone could help actively. Not only 'data voices' could be
>> sent.
>> Also the collected wlan, phone towers, GPS, voice, phone numbers and what
>> else could help to locate the guys behind,
>> as the phones will walk up to the key guys before it would reselled. (Where
>> they all are located would be very nice POI data)
>> With that data, we could help the police.
>> A note about the attack to people currently having your phone: They may not
>> know, that they have a stolen phone, thus
>> you get to be a 'criminal' and beware, you may also get reatacked by the
>> person :-)
>> Giving the police the collected data, would propably help much more.
>> What about all my stupid brain stuff ?
>> Discuss about the possibilities - even stupid ideas as the old 'acustic
>> coupler'. You don't really need all the modern GPRS stuff :-)
>> If that is possible also the cost of operation is not very high I think -
>> even you change your card (you know to start a separate unlocker)
>> Lothar
>>
>> -- | Rapid Prototyping | XSLT Codegeneration | http://www.lollisoft.de
>> Lothar Behrens
>> Heinrich-

Re: buzz fix

[Paul Fertser]

Al Johnson  writes:
> On Monday 26 January 2009, Christoph Siegenthaler wrote:
>> are there any updates from resellers, FIC or any half-official
>> DIY-tutorials on the hardware problems, i.e. the buzzing?
>
> This appears to have benefited from feedback regarding capacitor types from 
> the few people so far to have attempted the mod, 

The feedback is that: you can use any cap, including tantalum. :)

> but more feedback is requested. The lack of feedback from people
> trying it may be why it hasn't yet made it past release candidate
> stage.

No more feedback is really needed. Everyone who performed the rework
confirmed that it eliminates the buzz. No single negative report. And
i guess at least 10-20 people have already tried the rework. So, the
reason that no reseller is doing it yet is probably due to
communication/business issues rather than technical.

-- 
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: Someone stole my Neo Freerunner... :(

[Thomas Franck]

bburde...@comcast.net wrote:
> If you don't want to risk being sued for a booby trapped phone, how 
> about at least a way to render the it useless to thieves?

I think that the majority of thieves is not technically inclined, thus
our FR is _already_ rather useless for him/her..


> For instance, you could make it unbootable from a zero power situation, 
> and then combine that with a rapid power discharge.  If the thief leaves 
> it uncharged for even a day, its bricked!

LOL :) yeah.. let's implement that.. oh wait.. this feature is already
implemented.. no battery voltage -> "bricked"
(unless one knows what to do)

Cheers,
-- 
Thomas

-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
The use of anthropomorphic terminology when dealing with computing
systems is a symptom of professional immaturity.
  - Edsgar W. Dijkstra
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: SHR Unstable

[Chris Syntichakis]

btw.. I am unable to ssh (from my linux box) to the SHR .. 
it works when the FR has the FDOM of the hackable1 , but not on SHR.. (i am
using the unstable version)

chris
-- 
View this message in context: 
http://n2.nabble.com/SHR-Unstable-tp2202729p2227042.html
Sent from the Openmoko Community mailing list archive at Nabble.com.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Someone stole my Neo Freerunner... :(

[Yorick Moko]

i'm assuming we don't want to brick it, because the thief is not very
likely to return the phone if it doesn't work, nor can we track it if
it isn't charged. He'(ll just dump the phone.

sending gps location (if available), cell tower information and SIM
card info (contacts, own number...) in the background to a predefined
cellphone number/upload it to a server or e-mail it (when internet is
available) seems to me the smarter choice.

y

On Tue, Jan 27, 2009 at 6:14 PM,   wrote:
> If you don't want to risk being sued for a booby trapped phone, how
> about at least a way to render the it useless to thieves?
>
> For instance, you could make it unbootable from a zero power situation,
> and then combine that with a rapid power discharge.  If the thief leaves
> it uncharged for even a day, its bricked!
>
>
> Jeff Sadowski wrote:
>> Oooh :-) Idea: Make it shock the user if its not the right user. I
>> smell smoke I think it is coming from over there. Hey look there is my
>> phone. next to a flaming POS.
>>
>> On Mon, Jan 26, 2009 at 4:59 PM, Lothar Behrens
>>  wrote:
>>> Hi,
>>> sorry for you all that lost your phone, stolen or lost anyhow by being
>>> careless. I also had lost a phone, but not my FR :-)
>>> I read the thread, and think about my contract. I have no gprs as of my old
>>> phone didn't let me opening
>>> web or wap pages.
>>> I have some questions and ideas that are in my brain :-)
>>> Is there any way to use analog modem connections ?
>>> I don't know how much CPU power is needed but when possible a phone could
>>> send more data to a dedicated
>>> number we could provide for that.
>>> If a real modem connection couldn't be used, what about creating a tone
>>> modulation for the data to be send
>>> as a 'spoken' message to be send back to a number as a voice recorder.
>>> The voice recorder then (a Linux PC :-) could decode the data and store the
>>> data.
>>> All the data could be collected on a web service to probably get the bad
>>> guys behind to give that information to
>>> the police.
>>> The web service also could provide information about stolen devices, thus
>>> when a phone gets any wlan connection,
>>> it could check for stolen state. This is not that spoof able I think,
>>> because the web sevice may be as usual password protected.
>>> But the server could provide sms, mms or phone gateways for fallback
>>> options. More gateways could be provided by us.
>>> The new gateway information could be uploaded by interacting with the user
>>> (software updates :-)
>>> If a phone didn't have gprs, sms, mms, or wlan, sending prepared 'data
>>> voices' would be an option. It didn't need to send much at first to get
>>> an answer about the stolen state in that way. I think the recorded data
>>> could be decoded in both directions, you don't need
>>> much cpu power, because it will be unidirectional, or let the 'protocol'
>>> enough time between packed sent and anser packets
>>> for decoding.
>>> Doing an active voice call may save us the cost of callbacks or sending back
>>> sms. With a proper longtime protocol with long pauses or a
>>> better solution a lot could be done.
>>> Usually you could activate this when the sim card get's changed without any
>>> notice to the user. He should still use the phone a while
>>> to collect information. We then could start a preinstalled application to
>>> authenticate the sim card change. If not options are many.
>>> The PIN entry of the normal card could be replaced by the PIN you
>>> provide. The user then wouldn't realize it, but claims to enter
>>> the correct, we simply accept, but start the timer for the above actions.
>>> Or we leave the user in claim that the documentation of it's sim card
>>> provider doesn't seem to be correct and he/she must issue
>>> a call with the service provider.
>>> At that point, the service provider couldn't help for that special phone.
>>> The new 'user' HAS to contact the manufacturer and so on
>>> you probably get your phone back, because the manufacturer should request
>>> for sending back the phone.
>>> Getting the state of stolen, the phone could anyway send a message to a
>>> police station near the user with spd-say, after
>>> the 'anti-theft' server has located the next police station's telephone
>>> number with any of the above options sent back to the
>>> phone. (Maybe with manual data entry of the phone numbers by us users with
>>> POI collection, hehe tangoGPS :-)
>>> That way the phone could help actively. Not only 'data voices' could be
>>> sent.
>>> Also the collected wlan, phone towers, GPS, voice, phone numbers and what
>>> else could help to locate the guys behind,
>>> as the phones will walk up to the key guys before it would reselled. (Where
>>> they all are located would be very nice POI data)
>>> With that data, we could help the police.
>>> A note about the attack to people currently having your phone: They may not
>>> know, that they have a stolen phone, thus
>>> you get to be a 'criminal' and bewar

Re: SHR Unstable

[Yorick Moko]

On Tue, Jan 27, 2009 at 6:30 PM, Chris Syntichakis  wrote:
>
> btw.. I am unable to ssh (from my linux box) to the SHR ..
> it works when the FR has the FDOM of the hackable1 , but not on SHR.. (i am
> using the unstable version)
>
> chris
> --
> View this message in context: 
> http://n2.nabble.com/SHR-Unstable-tp2202729p2227042.html
> Sent from the Openmoko Community mailing list archive at Nabble.com.
>
>
> ___
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>

have you rebooted?
sometimes it doesn't work on first boot

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Bass fix (was: Re: buzz fix)

[Paul Fertser]

Hi,

Al Johnson  writes:
>> > There's some fairly detailed discussion of audio mods on the hardware
>> > list which could be copied into the wiki, but there is no 'official' mod.
>> > I suspect there won't be one either, mostly because big caps won't fit in
>> > the space available, and relocating them to outside the screening can
>> > could easily reintroduce buzz.

I doubt it can reintroduce the buzz for the calling party. If
improperly shielded, outside caps will definetely introduce buzz to
FR's headphones though.

I propose to look at the page where i outlined my rework:
http://wiki.openmoko.org/wiki/GTA02_bass_fix

Comments are welcome.

-- 
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: Freerunner LightSaber

[Daniel Spies]

"kris Occhipinti"  wrote on Saturday 17 January 2009:
> Well, a few months ago, before I have a FreeRunner I saw a LightSaber
> application for the iPhone, I thought was neat.
>
> So, I made My own for the FreeRunner Yesterday.
>
> Here is the link
> http://filmsbykris.com/freerunner-debian/ko-user/ko-lightsaber.tar.gz
>
> How to install:
> Just un-tar it to your root directory and it should place everything where
> it needs to be
> and give you an icon on your desktop.
>
> What it does:
> Start the App and the phone sounds like a LightSaber Extending and then
> Humming (You know, Like StarWars)
> Swing the Phone Around and it sounds like you're having a LightSaber Fight.
>
> Features so Far:
> Sound, Vibration, and The Power Button LED flashes Blue on Swings.
>
> Todo list:
> Work on the GUI (Currently just a big exit button)
> add buttons to extend and retract Saber ( so you don't have to exit the
> program to stop the sounds )
> And some sort of graphic or image of a Light Saber.
> Add More sounds
> Have buttons so you can choose the color of you lightsaber.
>
> Bugs:
> Sometimes while exiting, if you are still swinging the phone around, the
> LED and/or the vibrator will stay on.
> If this occurs, start the app up again and then close it with out swinging
> the phone around.
> I believe I can fix this with ease.  I just wanted to get what I have done
> out before I continued working on new things.
>
> I got the sound fx off a free sound fx website.  Don't know who made them.
> I hope it is ok that I used them.

Hi Kris,

I wanted to give it a try, but I always get the following error output:

r...@om-gta02:~# ko-lightsaber
Traceback (most recent call last):
  File "/usr/bin/ko-lightsaber", line 4, in 
import pygame.mixer
ImportError: No module named pygame.mixer

Any idea what's the problem here? I installed the pygame package you suggested
http://www.angstrom-distribution.org/unstable/armv4t/python/python-
pygame_1.7.1-ml2_armv4t.ipk

Thanks,
Daniel

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: buzz fix

[Steven **]

I applied [1] the fix to my Neo with positive results.  It's seems to
have greatly reduced if not eliminated the buzz.

-Steven

Note [1]: By "I applied" I mean I bribed a co-worker with some Mt. Dew
to do the soldering for me. ;-)

On Tue, Jan 27, 2009 at 10:52 AM, Neng-Yu Tu (Tony Tu)
 wrote:
> #1 Can't tell how much it could improve, yet
>
> As described above, buzz fix actually is EMI resist fix/workaround,
> Currently, we have 2 feedback from kindly community member help verify
> joerg's SOP, and have positive result. Community do a great work on
> verification, but we don't finish internal/mass verification for how
> much it could improve.
> Regards,
>
> - --
> Neng-Yu Tu (Tony Tu)
> Openmoko, Inc.
> Support

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Buzz fix attempt, tomorrow

[Steven **]

I too applied the fix. Or, I should say, got a co-worker to apply the
fix.  He worked with surface mount components for a few years and our
lab has all the necessary equipment to do surface mount soldering.  As
well as a stock room with a fairly large selection of components.

It took about an hour because the components are so hard to work with.
 I used a tantalum capacitor (as my work's stock room didn't have
ceramic with the needed specs) which made things rather difficult.
The capacitor was just small enough to fit inside the case.  But it
could not be positioned as depicted in the white paper.  We ended up
soldering some copper ribbon to the exposed pad to "extend" it to the
left in order to place the capacitor between the components on the
right and the screw hole.

I did not take any pictures (since cameras are forbidden inside my
place of work).

I have extra capacitors and resistors I don't need/want.  I'm not sure
if anyone would want them though, since the capacitor was so hard to
place well.

-Steven

On Mon, Jan 26, 2009 at 3:44 AM, kimaidou  wrote:
> Hi Yoan,
>
> I am about to buy the capacitor and resistor and ask a friend to do the buzz
> fix. Before diving into trouble water, I would really apreciate some
> feedback on your attemp :
> * did you succeed ?
> * is the buzz canceled ?
> * have you taken photographs on your work ?
>
> Thanks in advance
>
> Kimaidou
>
> 2009/1/6 Yoann ARNAUD 
>>
>> kimaidou a écrit :
>>
>> >> Tommorow, I (my colleague, actually) will try to fix the buzz of my OM
>> >> version A5 according to the manual of Joerg.
>>
>> Since I was asked, here is the documentation I will use :
>>
>>
>> http://people.openmoko.org/joerg/GSM_EMI_noise/big-C_rework_SOP__DRAFT3__.pdf
>>
>> --
>> Yoann ARNAUD
>> Nantes, France.
>>
>> ___
>> 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

gtk+-fastscaling depency

[Daniel Spies]

Hi list,

I got several packages now that are depending on gtk+-fastscaling. I did not 
try if forcing install will work, but I was wondering if this is a known 
thing. Because TangoGPS is a pretty well known app, right? So I was wondering 
why I get these errors...

Collected errors:
 * ERROR: Cannot satisfy the following dependencies for tangogps:
 *  gtk+-fastscaling (>= 2.10.14) *

Any idea?

Thanks,
Daniel

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Bass fix

[Paul Fertser]

Paul Fertser  writes:
> I propose to look at the page where i outlined my rework:
> http://wiki.openmoko.org/wiki/GTA02_bass_fix

Of course, that's only my take on implementation, the rework itself
was proposed and evaluated by Joerg Reisenweber, who also gave many
practical tips on how to do it best and how to test the results.

-- 
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

[SHR] SMS

[Matthew Lane]

I have a question about SHR SMS.  I loved SHR, but I found that call 
volume was very low, and I had trouble finding my SMS messages.  When 
receiving an incoming SMS, I could not delete the notify window with the 
X on the upper illume taskbar, and all of my SMS messages said they were 
received on Jan 1, 1987.  I'm assuming this is because I didn't 
correctly set my system clock, but how would I do that?  And how would I 
raise call volume, and delete the incoming message window?

Thanks!

Matt

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Bass fix

[Al Johnson]

On Tuesday 27 January 2009, Paul Fertser wrote:
> Paul Fertser  writes:
> > I propose to look at the page where i outlined my rework:
> > http://wiki.openmoko.org/wiki/GTA02_bass_fix
>
> Of course, that's only my take on implementation, the rework itself
> was proposed and evaluated by Joerg Reisenweber, who also gave many
> practical tips on how to do it best and how to test the results.

Your component placement is exactly what I proposed on the hardware list. It's 
good to know it works. I was slightly worried by the proximity to the 
bluetooth antenna.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: gtk+-fastscaling depency

[Marco Trevisan (Treviño)]

Daniel Spies wrote:
> I got several packages now that are depending on gtk+-fastscaling. I did not 
> try if forcing install will work, but I was wondering if this is a known 
> thing. Because TangoGPS is a pretty well known app, right? So I was wondering 
> why I get these errors...
> 
> Collected errors:
>  * ERROR: Cannot satisfy the following dependencies for tangogps:
>  *  gtk+-fastscaling (>= 2.10.14) *
> 

In distros like SHR that package is now called gtk+; however maybe its
authors should define something like a "Provides, Replaces, Conflicts:
gtk+-fastscaling" as in Debian.

-- 
Treviño's World - Life and Linux
http://www.3v1n0.net/


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [SHR] SMS

[Damian Spriggs]

To change the date/time:
http://www.linuxsa.org.au/tips/time.html
Even after setting the time, the messages all have the wrong  
timestamp (mine say January 1970)
The [X] button works for me, though (shr unstable, latest updates)

On Jan 27, 2009, at 2:29 PM, Matthew Lane wrote:

> I have a question about SHR SMS.  I loved SHR, but I found that call
> volume was very low, and I had trouble finding my SMS messages.  When
> receiving an incoming SMS, I could not delete the notify window  
> with the
> X on the upper illume taskbar, and all of my SMS messages said they  
> were
> received on Jan 1, 1987.  I'm assuming this is because I didn't
> correctly set my system clock, but how would I do that?  And how  
> would I
> raise call volume, and delete the incoming message window?
>
> Thanks!
>
> Matt
>
> ___
> 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: Re: gtk+-fastscaling depency

[Daniel Spies]

"Marco Trevisan (Treviño)"  wrote on Tuesday 27 January 2009:
> In distros like SHR that package is now called gtk+; however maybe its
> authors should define something like a "Provides, Replaces, Conflicts:
> gtk+-fastscaling" as in Debian.

That would be great indeed... Thanks for the information!

Daniel

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

[SHR] Kernel 2.6.28 not working on my Freerunner

[E. Boer]

Hello,

My first post on the mailinglist :-) because I don't know how to fix
this :-(

Today I downloaded the latest kernel and shr-lite-testing release, ran
into u-boot and flashed my Freerunner. I'm going with my [AUX]-button to
the boot option and pressed the power-button. The screen says that the
kernel was loaded successfully and stopped at "starting kernel". I
waited for more then a hour, after then I removed the battery for a hard
shutdown.

The kernel is 2.6.28. Kernel 2.6.24 is booting nice. But I want to know
what's going wrong (kernel panic)? What kind of information do you want
to help me fix this? 

Eddy


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [SHR] Kernel 2.6.28 not working on my Freerunner

[Andy Green]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Somebody in the thread at some point said:
| Hello,
|
| My first post on the mailinglist :-) because I don't know how to fix
| this :-(
|
| Today I downloaded the latest kernel and shr-lite-testing release, ran
| into u-boot and flashed my Freerunner. I'm going with my [AUX]-button to
| the boot option and pressed the power-button. The screen says that the
| kernel was loaded successfully and stopped at "starting kernel". I
| waited for more then a hour, after then I removed the battery for a hard
| shutdown.
|
| The kernel is 2.6.28. Kernel 2.6.24 is booting nice. But I want to know
| what's going wrong (kernel panic)? What kind of information do you want
| to help me fix this?

If there is literally a kernel panic, the AUX light will be flashing at
about 4Hz.

Where did you get the kernel from?  Is there a git hash on the filename?

- -Andy
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkl/focACgkQOjLpvpq7dMqh+QCgiotnMUPI/wAu3BWp/1Hp54H9
45gAnAsot9n5gE0mkIONUSEhT41nCXog
=23ih
-END PGP SIGNATURE-

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Conflict when several apps use the accelerometers?

[Hendrik Siedelmann]

2009/1/27, Helge Hafting :
> Gunnar Aastrand Grimnes wrote:
>> This page does: http://wiki.openmoko.org/wiki/Accelerometer_Fundamentals
>>
>> Noise is around 3cm/s^2, i.e:
>>
>> "
>> It can fill in _short_ - 3-5s gaps in GPS coverage, if the orientation
>> of the phone is known.
>
> Not enough for a 4km tunnel then, which is 3 min when going 80km/h.
> 5s is enough for a 111m tunnel, but 5s signal loss is usually not a
> problem anyway.
>
> Of course, the car speedometer readout can take care of speed and
> braking/acceleration, the accelerometer would only be needed to notice
> turning. Could be interesting to see where it thinks I am after 3 min,
> if 5s is all I can expect. I guess those 3-5s is the interval where
> precision matces the gps. But it will be useful for longer than that, as
> long as estimate is more accurate than "stopped at the tunnel entrance."
>
> The error increase with time, but so do the real distance from the entrance.
>
> Helge Hafting

Yes, I too think it would be useful for a longer period. In a time of
3-5 seconds one could propably get away with simply projecting the
route at signal loss with constant speed. And I think navit snaps to
streets anyway, so it wouldn't matter if its off by a bit.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [SHR] Kernel 2.6.28 not working on my Freerunner

[E. Boer]

On Tue, 2009-01-27 at 21:37 +, Andy Green wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Somebody in the thread at some point said:
> | Hello,
> |
> | My first post on the mailinglist :-) because I don't know how to fix
> | this :-(
> |
> | Today I downloaded the latest kernel and shr-lite-testing release, ran
> | into u-boot and flashed my Freerunner. I'm going with my [AUX]-button to
> | the boot option and pressed the power-button. The screen says that the
> | kernel was loaded successfully and stopped at "starting kernel". I
> | waited for more then a hour, after then I removed the battery for a hard
> | shutdown.
> |
> | The kernel is 2.6.28. Kernel 2.6.24 is booting nice. But I want to know
> | what's going wrong (kernel panic)? What kind of information do you want
> | to help me fix this?
> 
> If there is literally a kernel panic, the AUX light will be flashing at
> about 4Hz.

No flashing AUX light nothing, the phone is dead no any reaction.

> 
> Where did you get the kernel from?  Is there a git hash on the filename?

I grabbed the kernel from
http://build.shr-project.org/shr-unstable/images/om-gta02/

The hash is:
gitr34240a1c06ae36180dee695aa25bbae869b2aa26-r2-om-gta02



___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [SHR] Kernel 2.6.28 not working on my Freerunner

[Klaus Kurzmann]

* E. Boer  [090127 23:00]:
> On Tue, 2009-01-27 at 21:37 +, Andy Green wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> > 
> > Somebody in the thread at some point said:
> > | Hello,
> > |
> > | My first post on the mailinglist :-) because I don't know how to fix
> > | this :-(
> > |
> > | Today I downloaded the latest kernel and shr-lite-testing release, ran
> > | into u-boot and flashed my Freerunner. I'm going with my [AUX]-button to
> > | the boot option and pressed the power-button. The screen says that the
> > | kernel was loaded successfully and stopped at "starting kernel". I
> > | waited for more then a hour, after then I removed the battery for a hard
> > | shutdown.
> > |
> > | The kernel is 2.6.28. Kernel 2.6.24 is booting nice. But I want to know
> > | what's going wrong (kernel panic)? What kind of information do you want
> > | to help me fix this?
> > 
> > If there is literally a kernel panic, the AUX light will be flashing at
> > about 4Hz.

> No flashing AUX light nothing, the phone is dead no any reaction.

> > 
> > Where did you get the kernel from?  Is there a git hash on the filename?

> I grabbed the kernel from
> http://build.shr-project.org/shr-unstable/images/om-gta02/

> The hash is:
> gitr34240a1c06ae36180dee695aa25bbae869b2aa26-r2-om-gta02

on shr-testing the new kernel won't work anyway. The included version of
frameworkd is missing the necessary changes...

For the new kernel you have to use shr-unstable right now. This will
changes with the next testing image... which will be due, when we have
sorted out one or two problems of the current unstable image.


mrmoku

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Alsa state chooser

[TL Mieszkowski]

Al Johnson wrote:
> 
> The FSO API can list and change the alsa scenarios with stack based 
> management. It will also send a signal on scenario change so that
> interested 
> apps are aware of it. See:
> 
> http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.Device.Audio.html;hb=HEAD
> 

I can see how having the sound info in a stack might be useful (marginally,
really), but I can't see it justifying the use of D-bus.  I wouldn't say
never, but I really can't think of any pressing reasons to want to know when
the state changes.  Maybe it's just lack of imagination.  And as for playing
sounds off the message bus, why? Am I wrong for instinctively hating D-bus,
and finding any reason to not use it? Or at least only using it for things
that must be asynchronous?

 Something I could see as useful is a signal when headphones are plugged in.
I remember reading in the Wolfson Codec manual that it is possible, by
monitoring voltages or some such, I imagine that would have to be done in
the alsa plugin or maybe in the driver though.
-- 
View this message in context: 
http://n2.nabble.com/Alsa-state-chooser-tp224p2228688.html
Sent from the Openmoko Community mailing list archive at Nabble.com.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [SHR] Kernel 2.6.28 not working on my Freerunner

[E. Boer]

> > > Where did you get the kernel from?  Is there a git hash on the filename?
> 
> > I grabbed the kernel from
> > http://build.shr-project.org/shr-unstable/images/om-gta02/
> 
> > The hash is:
> > gitr34240a1c06ae36180dee695aa25bbae869b2aa26-r2-om-gta02
> 
> on shr-testing the new kernel won't work anyway. The included version of
> frameworkd is missing the necessary changes...
> 
> For the new kernel you have to use shr-unstable right now. This will
> changes with the next testing image... which will be due, when we have
> sorted out one or two problems of the current unstable image.
> 

phew It's not my Freerunner :-) ... just the software. I will
switch back to unstable until the new image is released.

Keep up the good work!

Eddy


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Buzz fix attempt, tomorrow

[Yoann ARNAUD]

Yoann ARNAUD a écrit :

> I'll try to make the pictures available tonight.

Here they are :

http://perso.crans.org/yarnaud/Openmoko/Buzz_Fix/


-- 
Yoann.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Buzz fix attempt, tomorrow

[Peter Strapp]

I'm getting a '403 forbidden' message. looks like we don't have read access.

Peter.

Yoann ARNAUD wrote:
> Yoann ARNAUD a écrit :
>
>   
>> I'll try to make the pictures available tonight.
>> 
>
> Here they are :
>
> http://perso.crans.org/yarnaud/Openmoko/Buzz_Fix/
>
>
>   


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: buzz fix

[Yoann ARNAUD]

Steven ** a écrit :
> I applied [1] the fix to my Neo with positive results.  It's seems to
> have greatly reduced if not eliminated the buzz.

For me, it seems that the buzz is eliminated.

-- 
Yoann.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Buzz fix attempt, tomorrow

[Yoann ARNAUD]

Peter Strapp a écrit :
> I'm getting a '403 forbidden' message. looks like we don't have read access.

Thanks. It's OK now.


-- 
Yoann.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: New Default Illume Keybd Layout

[The Rasterman]

On Sun, 25 Jan 2009 02:22:57 -0500 John Sullivan  said:

> Brock  writes:
> 
> > I extracted it and dropped it into place to work in debian. I've been
> > using it for several days and like this layout quite a bit... I threw in
> > a fuzz factor of 60 for sloppy slapping the keyboard, works great.
> >
> 
> Same here, on Debian. Haven't tried the fuzz factor yet but we'll see.
> 
> But something I've been meaning to look into for a while -- the font
> used for the letters on the keys and for the word suggestions above the
> keyboard is very very small. Is there an interface to set that somewhere
> or do I need to edit the theme file? It's a bigger font on SHR and FSO.

fonts should scale with the illume default profile - according to DPI. making
the fonts bigger will simply reduce the amount you can read. fonts on the
keyboard itself are not relevant as it fuzzy-matches anything nearby. the word
suggestions already have little enough space as-is... but you can play with a
custom scaling factor for e's ui - u'll need a restart for it to fully take
effect (restart of just e). but this will in general scale everything that is
scaleable. other than that the theme very much has a hand in setting the base
font sizes (relative to eachother) and the suggestions font size is the same
standard size used in all buttons/labels etc. etc.

-- 
- Codito, ergo sum - "I code, therefore I am" --
The Rasterman (Carsten Haitzler)ras...@rasterman.com


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [SHR] Kernel 2.6.28 not working on my Freerunner

[Andy Green]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Somebody in the thread at some point said:
|>>> Where did you get the kernel from?  Is there a git hash on the
filename?
|>> I grabbed the kernel from
|>> http://build.shr-project.org/shr-unstable/images/om-gta02/
|>> The hash is:
|>> gitr34240a1c06ae36180dee695aa25bbae869b2aa26-r2-om-gta02
|> on shr-testing the new kernel won't work anyway. The included version of
|> frameworkd is missing the necessary changes...
|>
|> For the new kernel you have to use shr-unstable right now. This will
|> changes with the next testing image... which will be due, when we have
|> sorted out one or two problems of the current unstable image.
|>
|
| phew It's not my Freerunner :-) ... just the software. I will
| switch back to unstable until the new image is released.
|
| Keep up the good work!

Glad to hear it, that particular kernel revision has been used for a
while by quite a few people now with good results... I guess it started
fine and then choked somewhere in the rootfs.

- -Andy
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkl/knUACgkQOjLpvpq7dMqRtwCeJL4XaRSvuO10+fxQK7HI8S6k
TQUAoIijV63Aq3tcaX2/1yxJhrUEWjUb
=QB7W
-END PGP SIGNATURE-

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: SHR Unstable

[Chris Syntichakis]

hi,

GPS works ok (takes arounf 4min to fix)..

also. (as I m flasing a lot the FR in order to try the distros) i reflashed
the FR again with SHR(unstable),
(I flashed it to FDOM, then again back to SHR)
now I see that the FR is somewhat .. slow for example:  the applications
take some time to run! 
(its definitely slower than the first time I flashed the SHR)..

veru strange , eh?

chris

-- 
View this message in context: 
http://n2.nabble.com/SHR-Unstable-tp2202729p2229085.html
Sent from the Openmoko Community mailing list archive at Nabble.com.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Alsa state chooser

[TL Mieszkowski]

WM8753.pdf pg 27:
MICBIAS CURRENT DETECT
The WM8753L includes a microphone bias current detect circuit which allows
the user to set
thresholds for the microphone bias current, above which an interrupt will be
triggered. There are two
separate interrupt bits, MICDET to allow the user to e.g. distinguish
between one or two microphones
connected to the WM8753L, and MICSHT to detect a shorted microphone (mic
button press). The
thresholds for the microphone bias current are set by MBTHRESH[2:0], for
MICDET, and
MBSCTHRESH[1:0] for MICSHT. Thresholds for each code are shown in Table 15.
The circuit is
enabled by setting MBCEN.
See the GPIO and Interrupt Controller sections for details on the interrupt
and status readback for the
microphone bias current detect.
  REGISTERBITLABEL  DEFAULT  
DESCRIPTION
  ADDRESS
 R51 (33h)   5:4 MBSCTHRESH 00   Microphone Bias,
Shorted Current
 Threshold Select
 00: 500uA
 01: 1000uA
 10: 1600uA
 11: 2300uA
 These values are
for 3.3V supply and
 scale with supply
voltage.
 3:1 MBTHRESH   000  Microphone Bias,
Current Threshold
 Select
 000:250uA
 001:410uA
 160uA steps up
to
 111:1370uA
 These values are
for 3.3V supply and
 scale with supply
voltage.
 0   MBCEN  0Mic Bias Current
Comparator Circuit
 enable
 0 : Comparator
disabled
 1 : Comparator
enabled
Table 15 Mic Bias Current Comparator Circuit Control

-- 
View this message in context: 
http://n2.nabble.com/Alsa-state-chooser-tp224p2229301.html
Sent from the Openmoko Community mailing list archive at Nabble.com.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

handset volume,,

[Chris Syntichakis]

I know the "low handset volume" is mentioned on the wiki too, but is there
any patch/solution?
I out the alsa setting to 127 (the high value) but I am not too happy...

Chris
-- 
View this message in context: 
http://n2.nabble.com/handset-volume%2C%2C-tp2229335p2229335.html
Sent from the Openmoko Community mailing list archive at Nabble.com.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Alsa state chooser

[Al Johnson]

On Wednesday 28 January 2009, TL Mieszkowski wrote:
> WM8753.pdf pg 27:
> MICBIAS CURRENT DETECT
> The WM8753L includes a microphone bias current detect circuit which allows
> the user to set
> thresholds for the microphone bias current, above which an interrupt will
> be triggered.

I think this appears as /dev/input/eventX and should be available in FSO's 
rules.yaml if it isn't available as a direct notification.

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Buzz fix attempt, tomorrow

[Tomas Riveros Schober]

Yoann ARNAUD escribió:
> Yoann ARNAUD a écrit :
>
>   
>> I'll try to make the pictures available tonight.
>> 
>
> Here they are :
>
> http://perso.crans.org/yarnaud/Openmoko/Buzz_Fix/
>
>
>   
is this buzz + bass fixes? because the reference pictures from the SOP 
paper don't show that second thing you soldered (not the yellow one, the 
other)

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Spam

[roguemoko]

Paul Boddie wrote:
> To avoid some problems with forged mail, I recommend setting up an SPF policy 
> record:
> 
> http://www.openspf.org/
> 
> See the "Deploying SPF" part of that page and the associated setup wizard.
> 
> When I looked at openmoko.org's DNS records, I couldn't find any evidence of 
> SPF policies, so perhaps someone should look into it. And everyone else who 
> isn't publishing SPF policies for their domain should consider doing so, 
> too - it's a pain to get a deluge of spam backscatter in one's inbox, but you 
> can prevent it from happening.

This should especially be done by mailing list servers and more so in 
openmoko's case as the contact with openmoko personnel and developers is 
pretty crucial.

Preventing your own people from being impersonated and forged mails 
being relayed via your own list seems common sense to some of us, or at 
least me :)

As the from address is maintained when sending to this particular list, 
I guess it's not even necessary for them to be checking records, so long 
as they publish some that we can check ... though they should be doing both.

The only problem with implementing this now would be the multiple 
sending servers required to be added to the records or the set up of 
auth smtp (with increased BW usage) and then the requirement for 
openmoko.org email users to adhere to the set up. Doable but not exactly 
trivial.

Sarton

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: Alsa state chooser

[TL Mieszkowski]

Al Johnson wrote:
> 
>  I think this appears as /dev/input/eventX and should be available in
> FSO's 
> rules.yaml if it isn't available as a direct notification.
> 
Cool, thanks Al
-- 
View this message in context: 
http://n2.nabble.com/Alsa-state-chooser-tp224p2229815.html
Sent from the Openmoko Community mailing list archive at Nabble.com.


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

www.opkg.org - Repository Alpha

[Tobias Kündig]

Dear community

I finally found some time to set up a simple repository for www.opkg.org. It
was difficult for me to figure out how exactly it is built. There isn't a
lot of information in the wiki and I've never done a repo before. However, I
like to try new things, so I wrote some little scripts that build a new
Packages(.gz) file every full hour.
To be honest, I'm not really sure if I've done it correctly. This is why I
ask the community to help me.

The repository's address is http://www.opkg.org/packages/.
Please feel free to test it and report any bugs/mistakes. I also appreciate
any suggestions on how I could make the system better. (How I said, I've
never done it before and actually don't have the knowledge to build a proper
repo.)
There are only the packages available that are stored on the
opkg.orgserver. The ones that are hosted on other servers aren't
included (yet).
I hope it won't break any systems - just to make sure: you test it _on your
own risk_.

Thanks in advance.

--
Regards,
Tobias
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community