Which app lets sharing location?

2014-01-19 Thread a dehqan 
Good day all

Hello ;

Yes , Tangogps let sharing location but Tangogps isn't being
maintained - I think the website is even gone. Tangogps proxies
everything through the tangogps site (route finding + location
sharing) so it won't work.
Also,There is a feature request for Foxtrotgps to support a new
location sharing service without the need for a proxy. but it needs a
valid IP that i don't have it on FR.

Do you know any other application that lets sharing location like tangoGPS ?


Regards Dehqan

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

Looking for Info on Neo Freerunner

2014-01-19 Thread auto78240314 
I am wondering if someone can tell me about the Neo Freerunner's 
features?  How long does the battery last between charges?  How 
many megapixels is the camera?  What is the contact for the 
manufacturer of the phone?  

123



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

QTMoko v55 GTA02 flash issue

2014-01-19 Thread Peter Viskup 
After upgrade of QTMoko to latest v55 my GTA02 don't wake-up to fully
functional state after some random time (more suspends/resumes and
uptime of some days). Looks like the flash didn't become available/writable.

Seeing these messages:

[64691.81] s3c-sdi s3c2440-sdi: running at 400kHz (requested: 400kHz).
[64691.81] mmc0: queuing unknown CIS tuple 0x01 (3 bytes)
[64691.82] mmc0: queuing unknown CIS tuple 0x1a (5 bytes)
[64691.825000] mmc0: queuing unknown CIS tuple 0x1b (8 bytes)
[64691.83] s3c-sdi s3c2440-sdi: powered down.
[64691.83] mmc0: error -110 whilst initialising SDIO card
[64692.61] mapped channel 10 to 2

Full log available on http://pastebin.com/eA99YjHa

Not sure whether anybody else experiencing the same or if it could be
caused by some bad cells on internal mmc flash...or other HW components.

-- 
Peter

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

Re: Looking for Info on Neo Freerunner

2014-01-19 Thread Paul Wise 
On Mon, Jan 20, 2014 at 2:27 AM, auto78240314 wrote:

 I am wondering if someone can tell me about the
 Neo Freerunner's features?

Please take a look at the wiki page:

http://wiki.openmoko.org/wiki/Neo_FreeRunner

 How long does the battery last between charges?

http://wiki.openmoko.org/wiki/Neo_FreeRunner_%28GTA02%29_Battery#Notes_about_expected_battery_life

 How many megapixels is the camera?

The device doesn't include a camera.

 What is the contact for the manufacturer of the phone?

It is no longer being manufactured but the contact details of the
former manufacturer are here:

http://openmoko.com/contact.html

-- 
bye,
pabs

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

Re: QTMoko v55 GTA02 flash issue

2014-01-19 Thread Radek Polak 
On Sunday, January 19, 2014 08:21:20 PM Peter Viskup wrote:

 After upgrade of QTMoko to latest v55 my GTA02 don't wake-up to fully
 functional state after some random time (more suspends/resumes and
 uptime of some days). Looks like the flash didn't become
 available/writable.
 
 Seeing these messages:
 
 [64691.81] s3c-sdi s3c2440-sdi: running at 400kHz (requested: 400kHz).
 [64691.81] mmc0: queuing unknown CIS tuple 0x01 (3 bytes)
 [64691.82] mmc0: queuing unknown CIS tuple 0x1a (5 bytes)
 [64691.825000] mmc0: queuing unknown CIS tuple 0x1b (8 bytes)
 [64691.83] s3c-sdi s3c2440-sdi: powered down.
 [64691.83] mmc0: error -110 whilst initialising SDIO card
 [64692.61] mapped channel 10 to 2
 
 Full log available on http://pastebin.com/eA99YjHa
 
 Not sure whether anybody else experiencing the same or if it could be
 caused by some bad cells on internal mmc flash...or other HW components.

I have experienced something similar and i can even reproduce it by repeated 
dialing FR from another phone (i do it from script on N900). Btw can you try 
if USB networking works in this state?

I dont think this is HW problem, because under old 2.6.28 openmoko kernel it 
does not happen.

I could do 2.6.28 based QtMoko image if you or someone else would like to try.

Regards

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

Re: Looking for Info on Neo Freerunner

2014-01-19 Thread Radek Polak 
On Monday, January 20, 2014 03:24:13 AM Paul Wise wrote:

 On Mon, Jan 20, 2014 at 2:27 AM, auto78240314 wrote:
  I am wondering if someone can tell me about the
  Neo Freerunner's features?
 
 Please take a look at the wiki page:
 
 http://wiki.openmoko.org/wiki/Neo_FreeRunner
 
  How long does the battery last between charges?
 
 http://wiki.openmoko.org/wiki/Neo_FreeRunner_%28GTA02%29_Battery#Notes_abou
 t_expected_battery_life

With 2.6.39 kernel you can get standby  100 hours

Regards

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

CSD calls from Neo Freerunner

2014-01-19 Thread Michael Spacefalcon 
For those who don't know what CSD is:

http://en.wikipedia.org/wiki/Circuit_Switched_Data

Here is an AT command session log of me making a CSD call from my
GTA02 on T-Mobile USA:

at+cgmm
+CGMM: Neo1973 GTA02

OK
at+cgmr
+CGMR: FreeCalypso leo2moko port

OK
at+cops?
+COPS: 0,0,T-Mobile

OK
atd13034944774
CONNECT

National Institute of Standards and Technology
Telephone Time Service, Generator 1b
Enter the question mark character for HELP
D  L
 MJD  YR MO DA HH MM SS ST S UT1 msADV OTM

56677 14-01-20 05:30:54 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:30:55 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:30:56 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:30:57 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:30:58 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:30:59 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:00 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:01 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:02 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:03 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:04 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:05 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:06 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:07 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:08 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:09 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:10 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:11 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:12 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:13 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:14 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:15 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:16 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:17 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:18 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:19 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:20 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:21 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:22 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:23 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:24 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:25 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:26 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:27 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:28 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:29 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:30 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:31 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:32 00 0 -.1 045.0 UTC(NIST) *
56677 14-01-20 05:31:33 00 0 -.1 045.0 UTC(NIST) *
NO CARRIER

-- end of log --

The number I dialed in this test is the Automated Computer Time Service
provided by the National Institute of Standards and Technology:

http://www.nist.gov/pml/div688/grp40/acts.cfm

Note how the above web page says, in part: Digital modems, such as
[...] wireless modems, cannot synchronize using ACTS.  Well, the log
above clearly shows that they are wrong, at least in the case of
high-quality wireless modems like Calypso. :-)

CSD calls may be placed from a GSM mobile either to a land line or to
another mobile.  (I don't know if it's possible to establish a CSD
connection from a land line to a mobile.)  When placing a CSD call to
a land line, one can connect to a traditional dial-up modem on the
receiving end - that's how I connected to ACTS, and if you've got your
own UNIX etc server at home with an old-fashioned modem on a land
line, it is really neat to be able to connect to it from anywhere in
the world via CSD, *bypassing the Internet*!

When you place a CSD call to another mobile, the network tells the
latter that it is a CSD call rather than voice.  If you have a GTA02,
you can have some fun by testing how various other mobile phones react
to incoming CSD calls: just have your FR dial a CSD call to the number
belonging to some standard cellphone (dumb or smart), running
standard proprietary fw, and see how the latter reacts to receiving
such an unusual call. :-)  To dial a CSD call, just omit the ending
';' from the ATD command you would normally use to dial an ordinary
voice call - see my log above.

But not all modems are created equal.  I've got a Huawei E303 3G modem
in the USB stick form factor to play with, and it appears that this
modem's fw does not support CSD at all.  After doing the usb_modeswitch
voodoo typically needed for these USB 3G modems (usually automated via
udev rules, but I had to install an updated usb_modeswitch package on
my Slackware 13.37 laptop), the modem shows up as a bunch of
/dev/ttyUSBx devices, supported by the option kernel module - hence
I wonder if it's anything like the modem in the GTA04.  /dev/ttyUSB0
presents an AT command interface, and the following observations can
be made from the latter:

* One can dial voice calls with ATDnumber; - makes the phone ring on
  the other end; upon answering that call one hears noise - the modem
  must be implementing some way to pass digital audio over USB, which
  is not being