Re: 1024#
On Saturday 10 October 2009 16:19:10 joan@gmx.net wrote: On Fri, 9 Oct 2009 14:27:44 -0500 Mikhail Umorin mike...@gmail.com wrote: On Friday 09 October 2009 06:42:11 joan@gmx.net wrote: On Fri, 9 Oct 2009 00:31:43 +0100 Stroller strol...@stellar.eclipse.co.uk wrote: On 8 Oct 2009, at 22:15, Mikhail Umorin wrote: On Thursday 08 October 2009 11:57:38 Rui Miguel Silva Seabra wrote: either you are in a zone with weak signal from 4508 and 2DF1 (so you jump frequently from one to the other) or yes, you probably are suffering from #1024 :( What's the best way to differentiate? Stand by a cell tower and wait for a couple of hours? It has already been posted here: Under normal circumstances you would only see these messages with a change of cell, so cid would be different. The only time I know of that you might legitimately see repeated reconnection to the same cell is if you've got very low signal and it's the only cell visible. I am really unclear why you feel the need to ask - yet again - if you're affected by #1024, when all the symptoms so clearly seem to point to it. Your Freerunner is of one of the batches affected, yes? Your Freerunner is reregistering. Obviously. Do you really have reason to believe you're in an area which receives poor coverage from these two towers? What signal strength do mobile phones generally show in your house? Or are you just grasping at straws, hoping your Freerunner is unaffected? Stroller. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community Am i the only one who sees 3 towers? if you are referring to my log, there are actually 8 towers: 2DF1, 2CED, 4508, 4506, 4507, 2B20, 2B21, and 2B04 What's up with that? Sorry pedantic post, like to withdraw the previous post. Oh, I did not even think of that. (It took me a perl script to count all the different ones). I am just really interested in why so many towers? Here is a log with deep sleep disabled. It started around 2009-10-09 21:00 [2009-10-10 06:15:17.647316] Signal : cid=2DF1, lac=2775 [2009-10-10 06:15:51.057840] Signal : cid=4508, lac=2775 [2009-10-10 07:14:58.962122] Signal : cid=2DF1, lac=2775 [2009-10-10 07:15:31.443058] Signal : cid=4508, lac=2775 [2009-10-10 07:43:48.193318] Signal : cid=2DF1, lac=2775 [2009-10-10 07:44:22.093633] Signal : cid=4508, lac=2775 [2009-10-10 12:43:26.834672] Signal : cid=2DF1, lac=2775 [2009-10-10 12:43:50.832594] Signal : cid=4508, lac=2775 so, I guess, this is normal ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 1024#
On Friday 09 October 2009 06:42:11 joan@gmx.net wrote: On Fri, 9 Oct 2009 00:31:43 +0100 Stroller strol...@stellar.eclipse.co.uk wrote: On 8 Oct 2009, at 22:15, Mikhail Umorin wrote: On Thursday 08 October 2009 11:57:38 Rui Miguel Silva Seabra wrote: either you are in a zone with weak signal from 4508 and 2DF1 (so you jump frequently from one to the other) or yes, you probably are suffering from #1024 :( What's the best way to differentiate? Stand by a cell tower and wait for a couple of hours? It has already been posted here: Under normal circumstances you would only see these messages with a change of cell, so cid would be different. The only time I know of that you might legitimately see repeated reconnection to the same cell is if you've got very low signal and it's the only cell visible. I am really unclear why you feel the need to ask - yet again - if you're affected by #1024, when all the symptoms so clearly seem to point to it. Your Freerunner is of one of the batches affected, yes? Your Freerunner is reregistering. Obviously. Do you really have reason to believe you're in an area which receives poor coverage from these two towers? What signal strength do mobile phones generally show in your house? Or are you just grasping at straws, hoping your Freerunner is unaffected? Stroller. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community Am i the only one who sees 3 towers? if you are referring to my log, there are actually 8 towers: 2DF1, 2CED, 4508, 4506, 4507, 2B20, 2B21, and 2B04 What's up with that? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 1024#
On Thursday 08 October 2009 03:18:23 ivanshirok...@gmail.com wrote: Mikhail Umorin пишет: On Wednesday 07 October 2009 13:23:48 Eric Olson wrote: Mikhail, This should all be on one line: print '[%s] Signal : cid=%s, lac=%s' % (datetime.datetime.now(),status['cid'],status['lac'] ) Eric Thanks, that worked. I even warmed up the phone with a heating pad and ran the script for a couple of minutes (with deep sleep = always, of course) -- and no lines in the log file! I got A6, so, I guess, I am lucky! Did u set ti_calypso_deep_sleep = always Yes, I did. I ran the script overnight (ca. 12 hours) and this is what I got: [2009-10-07 21:51:05.999018] Signal : cid=2B04, lac=2775 [2009-10-07 21:51:43.439188] Signal : cid=4508, lac=2775 [2009-10-07 21:57:45.501663] Signal : cid=2DF1, lac=2775 [2009-10-07 21:58:09.491458] Signal : cid=4508, lac=2775 [2009-10-07 21:58:32.559254] Signal : cid=2DF1, lac=2775 [2009-10-07 21:58:51.403635] Signal : cid=4508, lac=2775 [2009-10-07 22:08:04.577409] Signal : cid=2DF1, lac=2775 [2009-10-07 22:08:27.640410] Signal : cid=4508, lac=2775 [2009-10-07 22:27:56.636141] Signal : cid=2DF1, lac=2775 [2009-10-07 22:28:32.396817] Signal : cid=4508, lac=2775 [2009-10-07 22:30:09.581581] Signal : cid=4508, lac=2775 [2009-10-07 22:30:11.996154] Signal : cid=4508, lac=2775 [2009-10-07 22:37:01.968110] Signal : cid=4508, lac=2775 [2009-10-07 22:37:04.771834] Signal : cid=4508, lac=2775 [2009-10-07 22:38:38.016193] Signal : cid=4508, lac=2775 [2009-10-07 22:38:40.456745] Signal : cid=2DF1, lac=2775 [2009-10-07 22:38:59.501991] Signal : cid=4508, lac=2775 [2009-10-07 22:42:20.996318] Signal : cid=4506, lac=2775 [2009-10-07 22:42:41.712490] Signal : cid=4508, lac=2775 [2009-10-07 22:46:37.117484] Signal : cid=2DF1, lac=2775 [2009-10-07 22:47:37.377656] Signal : cid=4508, lac=2775 [2009-10-07 22:48:08.620849] Signal : cid=4508, lac=2775 [2009-10-07 22:48:11.086460] Signal : cid=2DF1, lac=2775 [2009-10-07 22:48:24.942362] Signal : cid=4508, lac=2775 [2009-10-07 22:56:21.373120] Signal : cid=4506, lac=2775 [2009-10-07 22:56:34.555647] Signal : cid=4508, lac=2775 [2009-10-07 22:57:32.640541] Signal : cid=4508, lac=2775 [2009-10-07 22:57:34.357571] Signal : cid=4508, lac=2775 [2009-10-07 23:00:00.492293] Signal : cid=4508, lac=2775 [2009-10-07 23:00:02.896863] Signal : cid=4508, lac=2775 [2009-10-07 23:00:32.467281] Signal : cid=4508, lac=2775 [2009-10-07 23:00:34.916526] Signal : cid=4508, lac=2775 [2009-10-07 23:02:17.305925] Signal : cid=4506, lac=2775 [2009-10-07 23:02:43.192305] Signal : cid=4508, lac=2775 [2009-10-07 23:04:19.394357] Signal : cid=4508, lac=2775 [2009-10-07 23:04:21.135537] Signal : cid=4508, lac=2775 [2009-10-07 23:05:49.777196] Signal : cid=4508, lac=2775 [2009-10-07 23:05:51.518800] Signal : cid=4508, lac=2775 [2009-10-07 23:07:29.914118] Signal : cid=4506, lac=2775 [2009-10-07 23:08:10.858446] Signal : cid=4508, lac=2775 [2009-10-07 23:08:39.108456] Signal : cid=4506, lac=2775 [2009-10-07 23:08:48.990273] Signal : cid=4508, lac=2775 [2009-10-07 23:09:09.703847] Signal : cid=2DF1, lac=2775 [2009-10-07 23:09:58.673736] Signal : cid=4508, lac=2775 [2009-10-07 23:10:37.900469] Signal : cid=4508, lac=2775 [2009-10-07 23:10:39.648699] Signal : cid=2DF1, lac=2775 [2009-10-07 23:10:53.301876] Signal : cid=4508, lac=2775 [2009-10-07 23:11:40.357405] Signal : cid=2DF1, lac=2775 [2009-10-07 23:12:32.612333] Signal : cid=4508, lac=2775 [2009-10-07 23:14:03.482989] Signal : cid=2DF1, lac=2775 [2009-10-07 23:14:33.618424] Signal : cid=4508, lac=2775 [2009-10-07 23:16:29.897189] Signal : cid=2DF1, lac=2775 [2009-10-07 23:17:30.151953] Signal : cid=4508, lac=2775 [2009-10-07 23:18:11.762712] Signal : cid=4508, lac=2775 [2009-10-07 23:18:13.486081] Signal : cid=4506, lac=2775 [2009-10-07 23:18:45.666565] Signal : cid=4506, lac=2775 [2009-10-07 23:18:47.392123] Signal : cid=4508, lac=2775 [2009-10-07 23:19:17.667250] Signal : cid=4508, lac=2775 [2009-10-07 23:19:19.516853] Signal : cid=4508, lac=2775 [2009-10-07 23:19:51.562417] Signal : cid=4508, lac=2775 [2009-10-07 23:19:53.302078] Signal : cid=4508, lac=2775 [2009-10-07 23:21:40.612072] Signal : cid=4506, lac=2775 [2009-10-07 23:21:54.268411] Signal : cid=4508, lac=2775 [2009-10-07 23:22:24.095872] Signal : cid=4508, lac=2775 [2009-10-07 23:22:25.828675] Signal : cid=4508, lac=2775 [2009-10-07 23:22:54.225873] Signal : cid=4508, lac=2775 [2009-10-07 23:22:55.967579] Signal : cid=4508, lac=2775 [2009-10-07 23:24:39.508603] Signal : cid=2DF1, lac=2775 [2009-10-07 23:24:53.180934] Signal : cid=4508, lac=2775 [2009-10-07 23:25:22.072722] Signal : cid=4508, lac=2775 [2009-10-07 23:25:24.496914] Signal : cid=4508, lac=2775 [2009-10-07 23:25:55.956373] Signal : cid=4508, lac=2775 [2009-10-07 23:25:58.397659] Signal : cid=2DF1, lac=2775 [2009-10-07 23:26:12.263459] Signal : cid=4508, lac=2775 [2009-10-07 23:26:43.803461] Signal : cid=2DF1, lac=2775 [2009-10-07 23:27:17.694092] Signal : cid=4508, lac
Re: 1024#
On Thursday 08 October 2009 11:57:38 Rui Miguel Silva Seabra wrote: either you are in a zone with weak signal from 4508 and 2DF1 (so you jump frequently from one to the other) or yes, you probably are suffering from #1024 :( What's the best way to differentiate? Stand by a cell tower and wait for a couple of hours? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 1024#
On Thursday 08 October 2009 18:31:43 Stroller wrote: On 8 Oct 2009, at 22:15, Mikhail Umorin wrote: On Thursday 08 October 2009 11:57:38 Rui Miguel Silva Seabra wrote: either you are in a zone with weak signal from 4508 and 2DF1 (so you jump frequently from one to the other) or yes, you probably are suffering from #1024 :( What's the best way to differentiate? Stand by a cell tower and wait for a couple of hours? It has already been posted here: Under normal circumstances you would only see these messages with a change of cell, so cid would be different. The only time I know of that you might legitimately see repeated reconnection to the same cell is if you've got very low signal and it's the only cell visible. I am really unclear why you feel the need to ask - yet again - if you're affected by #1024, when all the symptoms so clearly seem to point to it. Your Freerunner is of one of the batches affected, yes? Your Freerunner is reregistering. Obviously. Do you really have reason to believe you're in an area which receives poor coverage from these two towers? What signal strength do mobile phones generally show in your house? Or are you just grasping at straws, hoping your Freerunner is unaffected? Stroller. Grasping at straws :) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 1024#
On Wednesday 07 October 2009 04:36:01 Thomas HOCEDEZ wrote: David Garabana Barro a écrit : On Wednesday 07 October 2009 10:57:02 Christ van Willegen wrote: Hi, On Wed, Oct 7, 2009 at 10:50 AM, Ivan Shirokov ivanshirok...@gmail.com wrote: I've been wondering if all the freerunners are affected by bug #1024? No, not all FR are affected, AFAIK I've been wondering the same thing... It would seem that the extra current draw in suspend would affect all FRs, so having a #1024 fix-party would be a good idea in any case (?). #1024 is not causing extra current drain, but the software solution to this bug: Not allowing Calypso entering deep sleep mode. You can check if your FR is suffering from #1024 editting /etc/frameworkd.conf and changing ti_calypso_deep_sleep = never to ti_calypso_deep_sleep = always then restarting framework: /etc/init.d/frameworkd restart After doing so, if your FR suffers from this bug, your modem will continuously register/unregister from GSM network when suspended, and you will lose calls On my case, it was nearly impossible to call FR when suspended + calypso deep sleep. But not all FR suffer from this bug. You should try it after fixing it. Most of GTA02-A5/A6 have this bug. Once TI_CALYPSO_DEEP_SLEEP set to always, you can check with a little script done by KaZEr (see bleow) Launch it on screen, and redirect output to a file. If you have something like [2009-09-09 12:36:09.189663] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:36:15.088936] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:38:10.442808] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:38:13.020126] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:40:25.772918] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:40:28.620096] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:41:17.557676] Signal : cid=3BB3, lac=0D48 [2009-09-09 12:41:20.404582] Signal : cid=3BB3, lac=0D48 Then you have the bug (trying to connect to GSM every second!) regards AstHrO Here's KaZeR's script : -- #!/usr/bin/python import dbus import dbus.glib import gobject import datetime def onNetworkStatus(status ): print '[%s] Signal : cid=%s, lac=%s' % (datetime.datetime.now(),status['cid'],status['lac'] ) bus = dbus.SystemBus(); bus.add_signal_receiver( onNetworkStatus, Status, org.freesmartphone.GSM.Network, org.freesmartphone.ogsmd, /org/freesmartphone/GSM/Device ) gobject.threads_init() dbus.glib.init_threads() main_loop = gobject.MainLoop() main_loop.run() -- I am trying to run the script and I get: r...@om-gta02 ~ $ deep-sleep-check.py dsc.log File /usr/bin/deep-sleep-check.py, line 9 print '[%s] Signal : cid=%s, lac=%s' % ^ SyntaxError: invalid syntax I am not familiar with Python, so, can someone help me to fix this? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 1024#
On Wednesday 07 October 2009 13:23:48 Eric Olson wrote: Mikhail, This should all be on one line: print '[%s] Signal : cid=%s, lac=%s' % (datetime.datetime.now(),status['cid'],status['lac'] ) Eric Thanks, that worked. I even warmed up the phone with a heating pad and ran the script for a couple of minutes (with deep sleep = always, of course) -- and no lines in the log file! I got A6, so, I guess, I am lucky! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [fso based] Simplified mixer app
Thanks for the app, Al (see below) On Monday 05 October 2009 19:43:37 Al Johnson wrote: On Friday 02 October 2009, Laszlo KREKACS wrote: On Fri, Oct 2, 2009 at 4:17 PM, Laszlo KREKACS laszlo.krekacs.l...@gmail.com wrote: But there is so many things what changed, that Im completely lost. Just wanted to notice you, that restoring the original gsmhandset.state file (and rebooting) does solve my problem. Im able to take call, and hear the other party. (and he able to hear me). Although your program was nice. It changed the mic way better, what I had. Other party said, its much louder and clearer. Hope you can sort out, why the broken .state file is broken. And where the bugs comes from ... Updated version now available: http://www.mazikeen.demon.co.uk/openmoko/fso-simplemixer.py In simple view if I slide volume all the way to the right, it goes to 101 (not 100) is that correct? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [fso based] Simplified mixer app
On Tuesday 06 October 2009 12:28:37 Al Johnson wrote: On Tuesday 06 October 2009, Mikhail Umorin wrote: Thanks for the app, Al (see below) On Monday 05 October 2009 19:43:37 Al Johnson wrote: On Friday 02 October 2009, Laszlo KREKACS wrote: On Fri, Oct 2, 2009 at 4:17 PM, Laszlo KREKACS laszlo.krekacs.l...@gmail.com wrote: But there is so many things what changed, that Im completely lost. Just wanted to notice you, that restoring the original gsmhandset.state file (and rebooting) does solve my problem. Im able to take call, and hear the other party. (and he able to hear me). Although your program was nice. It changed the mic way better, what I had. Other party said, its much louder and clearer. Hope you can sort out, why the broken .state file is broken. And where the bugs comes from ... Updated version now available: http://www.mazikeen.demon.co.uk/openmoko/fso-simplemixer.py In simple view if I slide volume all the way to the right, it goes to 101 (not 100) is that correct? That depends which slider it is ;-) It is correct. I map the alsa channels to a single slider giving equal increments covering the full range possible from those channels. For the outputs this is usually gives steps 0 to 101 while for the mic it is usually 0 to 119. If you uncomment self.gta02mixer.PrintGains() and start it from the cli it will show you the gain setting in dB for each step in the debug output. Unfortunately pyalsaaudio only accepts integer percentages when setting volume, so there are rounding errors when actually setting the volumes. I was talking about Stereo Out for Speaker (when not in call). Sorry to be unclear. So, how does the simple slider correspond to Bypass and Headphone in the advanced view? Or are those things all different controls? Moving the simple speaker slider seem to change Bypass and Headphone, but at different rates for different ranges of the simple slider. When I max out the simple slider (to 101), bypass and headphone are at 100, but at lower simple slider settings they change very non-linear. This was probably discussed numerous times. But your visual application makes the channels easier to control and I finally feel that I have a chance to get the volume I want during calls. It's all so confusing What's a good place to learn the relations between all the channels/controls/bugs that make sound? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Internal pressure sensor
On Wednesday 30 September 2009 16:18:51 Christoph Mair wrote: Hi, I successfully added a pressure sensor to my Freerunner. The BMP085 chip from Bosch Sensortec is a small (5x5x1.5mm) chip which includes a pressure and a temperature sensor. Power and I2C is enough to get it working. I glued it next to the BT antenna. The wiki page contains some pictures: http://wiki.openmoko.org/wiki/I2C_Pressure_Sensor Sourcecode is available from http://gitorious.org/freerunner-navigation- board/bmp085 Christoph ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community Cool! can be very helpful during mountain hiking (not that GPS does not help already -- but it may not be always available) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
GSM roaming question
Hello -- I cannot access network in certain locations (in Texas, USA) on my FR using ATT SIM card. However, when I use the same SIM in the ATT GoPhone that came with the card, I have access to a network. Operators button in the phone settings in SHR-U shows only Automatic and T-Mobile. So, is this roaming problem a bug? misconfiguration? not implemented? not possible? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Only one chance to enter PIN?
On Friday 18 September 2009 19:42:52 Al Johnson wrote: On Friday 18 September 2009, Mikhail Umorin wrote: Hello -- I have enabled PIN for my SIM (rhymes, ah?). As I turn FR on it asks me to enter it. However, it takes awhile and I usually forget to wait for the PIN dialogue to come up. After a while, either due to suspend, or due to accidentally pressed buttons, the PIN entry dialogue vanishes and I am left with No service. Is there a way to enter the PIN at this time? What is the original GUI app that asks for the PIN in the first place? That depends on the distro. Which one are you using? SHR-unstable ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
fsomixer crushes
Hello -- I am trying to use fsomixer [1,2] to adjust headset output volume. When not in call the program runs. However, when launching the app when in call (the way it's supposed to be used), it crashes with Volume.log: Error Information: An exit code of 1 was returned from /usr/bin/fsomixer.py. Output Data: There was no output Error Logs: There was no error message the _init() function misspelling in __init__.py is not an issue -- i checked. Also, there is a label Bypass but the slider seems to be covered by the Save button -- is this correct? Can someone help? Mikhail. [1] http://lists.openmoko.org/nabble.html#nabble-td1676346 [2] http://wiki.openmoko.org/wiki/Neo_Freerunner_audio_subsystem#Volume_Control ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Only one chance to enter PIN?
Hello -- I have enabled PIN for my SIM (rhymes, ah?). As I turn FR on it asks me to enter it. However, it takes awhile and I usually forget to wait for the PIN dialogue to come up. After a while, either due to suspend, or due to accidentally pressed buttons, the PIN entry dialogue vanishes and I am left with No service. Is there a way to enter the PIN at this time? What is the original GUI app that asks for the PIN in the first place? Mikhail. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [all / linux] neo as gps unit?
It is possible, indeed. You might be interested in reading [1] K- [1] http://wiki.openmoko.org/wiki/Neo_FreeRunner_GPS#Using_GPS Neither of the two methods offered in that wiki worked for me... ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
FR Battery fell into water, is it still useable?
It was fresh (tap) water. I pulled it out within 1 min. Has it been damaged (did it retain its capacity and won't damage the FR)? Mikhail. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: FR Battery fell into water, is it still useable?
On Tuesday 11 August 2009 10:24:57 Mikhail Umorin wrote: It was fresh (tap) water. I pulled it out within 1 min. Has it been damaged (did it retain its capacity and won't damage the FR)? Mikhail. Thank you all for the suggestions and comments. I dried my battery with a paper towel and let it sit on my desk for about 6 hours (no desiccant but I think it would be the best way to go). Phone booted without any problems, except ophonekitd would not start, strange. Battery seem to have the same charge as I remember. It started charging without any problems. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: The trivial #1024 GSM fix
On Tuesday 11 August 2009 00:43:53 Paul Fertser wrote: On Mon, Aug 10, 2009 at 08:47:01PM -0500, Mikhail Umorin wrote: Ok, maybe I'll give it a try (i.e. ask some one else to do it) :-) What's a good website to get the required cap (and what cap, brand, product #)? What you need is 0805 ceramic capacitor, 22uF, 6.3V (or more). If you're in Moscow, i suggest buying here: http://chipdip.ru/product0/276924954.aspx This was bought and used successfully by Q-Master. HTH Thank you for the info, Paul. Thanks also for the hint about digikey.com as the source for those caps in the US. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: The trivial #1024 GSM fix
On Monday 10 August 2009 06:51:59 Paul Fertser wrote: But I think you should still not assume that every Neo owner has access to the #1024 GSM fix necessary for the 140 hour standby time. Should i also refrain from assuming every Neo owner has access to some *nix box? Or to ssh client? This might make sense _if_ Neo wasn't a geek/hacker/developer device. But it is so its users are supposed to be able to solve small riddles along their ways to freedom. Paul, I think you are missing the risk part of it: if I screw up in software I can just reflash the device if I break a tiny piece of hardware -- my $400 fr is gone. Software and hardware are two totally different animals and being a geek in one does not imply being a geek in the other. I don't feel comfortable with any hw work exactly because of the risks involved. So, I would like some else fix this hw bug, but not just a guy around the corner -- I want a high degree of certainty that I shall get back a working device. Mikhail. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: The trivial #1024 GSM fix
On Monday 10 August 2009 17:22:12 Paul Fertser wrote: Mikhail Umorin mike...@gmail.com writes: But I think you should still not assume that every Neo owner has access to the #1024 GSM fix necessary for the 140 hour standby time. Should i also refrain from assuming every Neo owner has access to some *nix box? Or to ssh client? This might make sense _if_ Neo wasn't a geek/hacker/developer device. But it is so its users are supposed to be able to solve small riddles along their ways to freedom. Paul, I think you are missing the risk part of it: if I screw up in software I can just reflash the device if I break a tiny piece of hardware -- my $400 fr is gone. I'm somehow certain that's a wrong assumption. Unless you do something really cruel you're not likely to foobar the whole device. Also even some fatal mistake will cost you less than $400 because the prices really dropped lately. Software and hardware are two totally different animals and being a geek in one does not imply being a geek in the other. Being a geek is a way of life, that's how i see it. I don't feel comfortable with any hw work exactly because of the risks involved. So, I would like some else fix this hw bug, but not just a guy around the corner -- I want a high degree of certainty that I shall get back a working device. Well, i had a talk with cell phone repair guy today. Showed him my FR with front case dismounted so he could see how much work is involved in doing the buzz-fix. He said the work itself is very-very easy and he'd charge $30 or probably $15 if he liked the client. Probably you just can't imagine what cell phone repair guys usually do, comparing to that buzzfixing is really easy. Ok, maybe I'll give it a try (i.e. ask some one else to do it) :-) What's a good website to get the required cap (and what cap, brand, product #)? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: The trivial #1024 GSM fix
BTW... is this bug fixed in A7? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ZAGG invisible sheild for Neo Freerunner
On Friday 07 August 2009 05:44:09 Biagio Marino wrote: Hello, ... What do you think about the use of latex glove to prevent the formation of fingerprints? I don't think it's a good idea. First, latex gloves seem to have some kind of a powder on them -- that will stick to the screen. Second, the glove itself will be sticky even with with the spray. And, once it sticks, it will be much harder to unstick it than you finger. Vinyl, powder-free gloves may be better. But you still would have to spray them every 30 -- 60 sec or so.. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ZAGG invisible sheild for Neo Freerunner
I can't believe you say this! I found it a nightmare to try to fit, and eventually gave up. It's a bit of a pain, especially the full body one. You need steady hands and a lot of patience. The installation takes about an hour, then ZAGG recommends to leave it overnight. Then the plastic snugs like a glove on the device. It's shiny, so it looks a little cheesy (but my wife thinks the opposite). Also, Zagg undersupplies the SHIELD spray for the full body option, so use sparingly, but liberally when installing the screen piece because any fingerprints will be visible (like on mine :) ) -- even if you wash you hands really well. HTH, Mikhail. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Unabel to SSH into Neo Freerunner
On Thursday 06 August 2009 21:48:48 tom wrote: mhh, i dont know what to do, - latest ubuntu - android 1.5 alpha AFAIK android does not have ssh server. you can use adb to connect. check http://wiki.openmoko.org/wiki/Android_usage Mikhail. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: External GPS antenna question
On Friday 03 July 2009 22:42:04 Mikhail Umorin wrote: Hello -- Thank you all for the feedback! I have decided to get a passive antenna (Arcon: GPS-ANT-MMCX, from Amazon.com) for just a good reception and more accurate fix in the open. And for car/indoor/rainforest situations I shall get a retransmitting antenna like at http://pc-mobile.net/gpsant.htm when I really need it. This way I shall not be draining the battery to amplify the signal like with an active antenna. Mikhail. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Hello world. Is the Neo Freerunner dead?
On Tuesday 07 July 2009 07:45:33 li...@kitepilot.com wrote: Will it talk to the ATT's US network? Yes, I just recently I got a pay as you go phone (cheapest phone, they would not sell just the SIM for pay-as-you-go service, but would for a contract) -- took SIM out (it was 3G-capable, but would not make FR 3G, obviously), put it into FR -- got service under OM 2008.8, 2008.12, QT extended-improved, Android, and recent OM 2009 (with Paroli). T-Mobile has very similar setup with pay-as-you-go and contract wireless service. What do I tell them? What kind of plan/service you need, and whether you need SIM or a cheap phone -- that's all. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
External GPS antenna question
Hello -- I want to buy an external GPS antenna and would like to know what is the difference between active, passive (?), powered, and amplified antennas (antennae). What are the implications of their use with FR (power consumption, performance, etc)? Which ones of the above should work in FR? Should any antenna with MMCX connector work in FR? Thank you for your time, Mikhail. P.S. I checked http://wiki.openmoko.org/wiki/External_GPS_antennas but I want to know more of the general info. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: DNS fix disappears on android beta 7
Thanks for the tips, Arne -- In addition, gsm service is gone. does it come back, wheh you undo the dns changes? i'd guess, it is unrelated. Since the init.rc goes back to it's original state upon reboot, there is nothing to be undone. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
DNS fix disappears on android beta 7
Hello -- I am trying to apply DNS fix as per http://wiki.openmoko.org/wiki/Android_usage cat init.rc confirms that the changes are there. However, after reboot the changes the the DNS section in init.rc disappear. In addition, gsm service is gone. What is the problem and how to fix it? Mikhail. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: How to get started with Openmoko phone?
Just FYI 1) Is there any particular kind of wireless carrier (in US) I need to subscribe to? Any that use a SIM card. So ATT or T-Mobile. (I use ATT just fine) Slightly off. It also needs to be a GSM network. Right now, that's only ATT T-Mobile for the US. I tried both t-mobile and att pre-paid phones. t-mobile sold me just a SIM card ($20 in store, $7 online), att sold me with a phone ($20 cheapest, with 3G card). Both worked fine. To keep an old cell number one has to sign up for a contract. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: How to get started with Openmoko phone?
On Tuesday 16 June 2009 00:15:02 David Ford wrote: Mikhail Umorin wrote: I tried both t-mobile and att pre-paid phones. t-mobile sold me just a SIM card ($20 in store, $7 online), att sold me with a phone ($20 cheapest, with 3G card). Both worked fine. To keep an old cell number one has to sign up for a contract. i'm fairly sure that is marketing BS. afaik, there is nothing required to keep an old number. Well, when the salesperson tells you that they will not transfer the phone number unless you sign up for a contract there's not much you can do... At least, that's what I got. ___ 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: some questions before buying FreeRunner
Paul -- I use screen protection from day 1. It's a regular PDA screen protector, bought in a nearby cellphone shop. I don't think it decreases TS precision. Does a particular model of invisibleSHIELD fit FR or you had to cut an oversized one to shape? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Upgraded using angstrom rep -- infinite loop on startup
Hello -- I upgraded to the latest (?) version from Angstrom rep using opkg upgrade. Now, after the screen OPENMOKO (please wait) I get infinite loop saying: pcf50633_irq: entering(irq=53, pcf=c7d36c00): scheduling work pcf50633_work: INT1=0x00 INT2=0x00 INT3=0x40 INT4=0x00 INT5=0x00 ADCRDY the last line changes every other time to SECOND ADCRDY I can still ssh to FR, but I never get to GUI What is the problem? Thank you for your time, Mikhail. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Upgraded using angstrom rep -- infinite loop on startup
Thanks for the clarification, Robin -- the wiki is confusing on the matter: Here (http://wiki.openmoko.org/wiki/Getting_Started_with_your_Neo_FreeRunner#Update_with_the_package_manager) I read that need to point my reps to unofficial User reps, but, in User reps (http://wiki.openmoko.org/wiki/Users_Repositories) it says Angstrom is the base distribution of Openmoko Linux distribution. So, I assumed that Angstrom is the one that should replace defunct http://buildhost.openmoko.org/ So, where are the stable repositories and how to set them up? On Friday 12 June 2009 07:10:46 Robin Paulson wrote: 2009/6/12 Mikhail Umorin mike...@gmail.com: I upgraded to the latest (?) version from Angstrom rep using opkg upgrade. Now, after the screen OPENMOKO (please wait) I get infinite loop saying: oops, i think that might be your problem. there are some compatibility issues between openmoko OS and angstrom OS - the former is a fork of the latter, and one should be very careful when mixing the feeds, and certainly not blithely running opkg upgrade. the angstrom repos are useful for getting one or two apps in a controlled way, but nothing more there is a warning on the wiki about this, where i assume you got the angstrom feed info from? pcf50633_irq: entering(irq=53, pcf=c7d36c00): scheduling work pcf50633_work: INT1=0x00 INT2=0x00 INT3=0x40 INT4=0x00 INT5=0x00 ADCRDY i think pcf50633 is the power management chip? i could well be wrong. i don't think it matters too much What is the problem? you borked it! i don't know, maybe you can manually downgrade the packages that caused the problems. do you know what opkg upgraded? hmm, probably not. it may be best to copy all your valuable data off, then re-flash ___ 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: Upgraded using angstrom rep -- infinite loop on startup
Alright -- What is the problem? you borked it! i don't know, maybe you can manually downgrade the packages that caused the problems. do you know what opkg upgraded? hmm, probably not. it may be best to copy all your valuable data off, then re-flash I have flashed both rootfs and kernel and now I have a functioning FR again! Thanks! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: proprietary firmware
On Friday February 15 2008 13:54:27 Brandon Kruse wrote: In that case it is not an open phone or platform. It is well worth the investigation to go fully open somehow IMO. But I guess we could be like olpc and have a MOSTLY open platform (wifi chip is not, as you could have guessed) Basically what I thought was: a customer buys a phone with whatever firmware is in it and what ever mechanism the OS uses to upload it to the hardware on startup if necessary; if a customer wants to update/upgrade firmware then one has to download a binary update app (say from OM website) and the firmware update itself (from OM or a hardware vendor). Then install the app, the firmware and be happy about new features/speed and the fact that there is a (small) binary module on his/her system he/she knows nothing about. Alternatively, one can send the phone to OM and request an firmware update; Alternatively, one can refuse to put anything non-FOSS on the phone and live happily with (presumably buggy/malfunctioning) existing firmware and try to fix any problems the FOSS-way. I do not think OM can achieve *completely* (=absolutely) open OS with any sensible effort. Let's be realistic. What OM/community needs to decide is the degree (or ratio) of open to non-open soft. I would not even demand a certain, community decided API from firmware vendors -- just that they *open* whatever API they have. The greatest problem for community to produce software is not that some API has changed: it's when API is not available in the first place. So, let's get the functioning hardware in our hands -- there is plenty of things to do beyond firmware updates. M. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
