Re: FR non encrypted calls
Matthias Apitz g...@unixarea.de writes: Is the FR capable to show that the call runs in non encrypted mode because the BS forced the ME to this mode? The question is for Om2008.9 but as well valid for any other distribution running on the FR. I think the GSM part (Calypso) delivers this information in the AT%CPRI message. With ogsmd (part of the python version of fso-frameworkd) I have lines like Jul 3 11:57:43 ginger org.freesmartphone.GSM.Network.CypherStatus: enabled: unknown in /var/log/syslog. om2008.9 does not use ogsmd afaik but gsmd. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
What happened to Freeyourphone.de?
http://freeyourphone.de currently returns This site has been suspended. Someone forgot to extend the contract? Nikolaus ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Freerunner won't charge
I have the same problem. Can you pls report if replacing the chip actually fixes the moko? thx, clemens On Sat, Jul 2, 2011 at 06:46, Paul Fertser fercer...@gmail.com wrote: Hi, Ronald Tallent r...@tallent.ws writes: So, there's no way to fix this thing? If I need to take it to an electronics repair shop to get it fixed I can, just need to know what part(s) will need to be repaired/replaced. Anyone know were I can get hold of schematics for the mainboard? If it's a simple repair proceedure I might be able to do it myself even. Schematics are available from [1]. I hope you'll find the cause and will be able to use your cool device again :) Basically, what you need to know is that charging is controlled by the PMU chip, PCF50633, it's connected over SPI bus and you can easily view dump of its registers from [2] (newer kernels might have a slightly different path but the same filename). Schematics are pretty much obvious but if you have any questions, feel free to ask here or on #openmoko-cdevel irc channel. [1] http://people.openmoko.org/joerg/schematics/ [2] /sys/class/i2c-adapter/i2c-0/0-0073/dump_regs -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Bluetooth keyboards
Any update on BT kayboard? I got mine a few days ago and although it works with my Linux laptop (connecting using Gnome panel applet), I'm not able to use it with FR. I've found both articles on Wiki: http://wiki.openmoko.org/wiki/Freedom_Slim_Keyboard http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#HID_.28Human_Input_Device.29 but the commands doesn't seem to be working. I'm getting the best results with hdid --connect ADDRESS after which command I have this in dmesg: [10713.02] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [10802.37] input: Broadcom Corp. Keyboard as /devices/platform/s3c2410-ohci/usb1/1-1/1-1:1.0/bluetooth/hci0/hci0:42/input6 [10802.38] generic-bluetooth 0005:0A5C:8502.0001: input: BLUETOOTH HID v1.1b Keyboard [Broadcom Corp. Keyboard] on 00:06:6E:17:29:5E And if I cat /dev/input/event6 I can see some garbage on the screen while pressing buttons on my keyboard. But If I open terminal or new message dialog, I can't see any letters while typing on the keyboard. Thanks , Hrabosh Al Johnson píše v Po 02. 05. 2011 v 12:41 +0100: An alternative could be the one from the wiki: http://wiki.openmoko.org/wiki/Freedom_Slim_Keyboard But there is no mention of qtmoko support? The distro only has to serve the needed bt-tools, then everything will work. I recently bought the following one: http://cgi.ebay.it/ws/eBayISAPI.dll?ViewItemitem=260747301433ssPageName= STRK:MEWNX:IT which is quite cheep, small and light. It can pair with QtMoko but I can't use it for input. I tested it with the iphone of a colleague and, indeed, it works. Did you connecting to the keyboard manually after pairing? Depending on whether QtMoko is using bluez3 or bluez4 the method is slightly different, but both are in the wiki: http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#HID_.28Human_Input_Device.29 If it works after manual connection then adding a GUI for it should be relatively simple. If it doesn't then some deeper investigation will be needed. ___ 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: [debian] fso stack does not work
Timo Jyrinki, Jul. 02, 2011, 08:51 +0300: You can try to use stable repositories instead by modifying the install.sh script [...] Thank you for your advice. I managed to install from wheezy branch instead of sid. I got tslib with Timo Juhani Lindfors' patch from http://lindi.iki.fi/lindi/tslib/ and your kernel linux-image-2.6.34-openmoko-gta02_20101212.git049b71de-2 from http://pkg-fso.alioth.debian.org/incoming/ . Touchscreen now works (thanks to both of you!). Unfortunately, I was not able to get the FSO stack to work. When I start fso-frameworkd service and invoke zhone, the latter reports gsm ok: Interface ... implementing 'org.freesmartphone.GSM.Network' at 0x4059aa90, but then stucks with Requesting resource GSM (full log attached). fsousage log says: Resource GSM can't be enabled: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.. Trying to disable instead. frameworkd contains several errors, including two python-related ones. While googleing reveals that the absence of pyrtc (python-rtc) is not fatal (is that correct?), there is more sinister-looking one: frameworkd.subsystem ERRORfactory method not successfully completed for module module 'odeviced.input' from '/usr/lib/pymodules/python2.6/framework/subsystems/odeviced/input.pyc' ...and a python call stack ending with NameError: global name 'c' is not defined. At the first glance I did not manage to mend it, though the issue is quite clear: c is a global variable initialized at the module level (c stands for C library). The log ends with a long sequence of messages from ogsmd continuously trying (unsuccessfully) to open channels MISC, UNSOL, CALL. FSO package versions are included in a separate attachment. Zhone is 0-git20110224+6bcb7fc4-1. Has anyone encountered the same issue? Am I missing something? or is it that Debian FSO packages are broken at the moment? -- Dmitry Chistikov fso-config-gta02 20100210 fso-frameworkd 0.9.5.9+git20100131-4 fso-gpsd 0.8-3.1 fso-gsm0710muxd 0.9.3.1-3 fso-sounds-yue-base 20081031-2 fso-usaged 0.9.1.1+git20100507-1 fso-utils 0.git20090919.1 libfso-glib0 2010.05.11.2-1.2 libfsobasics0 0.9.0+git20100509-2 libfsoframework0 0.2.4+git20100501-1 2011-07-04 19:47:55,605 WARNING could not load illume interface module 2011-07-04 19:47:56,344 DEBUG GUI init 2011-07-04 19:47:59,434 DEBUG GUI init done 2011-07-04 19:47:59,444 DEBUG entering mainloop 2011-07-04 19:47:59,643 DEBUG dbus_objectInit... 2011-07-04 19:47:59,696 INFO cached proxy for org.freesmartphone.frameworkd:/org/freesmartphone/Framework 2011-07-04 19:47:59,745 INFO cached proxy for org.freesmartphone.ousaged:/org/freesmartphone/Usage 2011-07-04 19:47:59,798 DEBUG usage ok: Interface ProxyObject wrapping dbus._dbus.SystemBus (system) at 0x40550390 :1.104 /org/freesmartphone/Usage at 0x4053dc30 implementing 'org.freesmartphone.Usage' at 0x4053dd10 2011-07-04 19:47:59,818 INFO cached proxy for org.freesmartphone.ogpsd:/org/freedesktop/Gypsy 2011-07-04 19:48:00,020 DEBUG gps ok: Interface ProxyObject wrapping dbus._dbus.SystemBus (system) at 0x40550390 :1.96 /org/freedesktop/Gypsy at 0x4053df10 implementing 'org.freedesktop.Gypsy.Accuracy' at 0x4059a110, Interface ProxyObject wrapping dbus._dbus.SystemBus (system) at 0x40550390 :1.96 /org/freedesktop/Gypsy at 0x4053df10 implementing 'org.freedesktop.Gypsy.Position' at 0x4059a390, Interface ProxyObject wrapping dbus._dbus.SystemBus (system) at 0x40550390 :1.96 /org/freedesktop/Gypsy at 0x4053df10 implementing 'org.freedesktop.Gypsy.Satellite' at 0x4059a4d0 2011-07-04 19:48:00,048 INFO cached proxy for org.freesmartphone.ogsmd:/org/freesmartphone/GSM/Device 2011-07-04 19:48:00,088 INFO cached proxy for org.freesmartphone.ogsmd:/org/freesmartphone/GSM/Server 2011-07-04 19:48:00,283 DEBUG gsm ok: Interface ProxyObject wrapping dbus._dbus.SystemBus (system) at 0x40550390 :1.97 /org/freesmartphone/GSM/Device at 0x4059a8b0 implementing 'org.freesmartphone.GSM.Network' at 0x4059aa90 2011-07-04 19:48:00,326 INFO cached proxy for org.freesmartphone.odeviced:/org/freesmartphone/Device 2011-07-04 19:48:00,364 INFO cached proxy for org.freesmartphone.odeviced:/org/freesmartphone/Device/IdleNotifier/0 2011-07-04 19:48:00,463 DEBUG device ok: Interface ProxyObject wrapping dbus._dbus.SystemBus (system) at 0x40550390 :1.94 /org/freesmartphone/Device at 0x405a00d0 implementing 'org.freesmartphone.Device' at 0x405a0190 2011-07-04 19:48:00,483 INFO cached proxy for org.freesmartphone.opreferencesd:/org/freesmartphone/Preferences 2011-07-04 19:48:00,503 DEBUG preferences ok: Interface ProxyObject wrapping dbus._dbus.SystemBus (system) at 0x40550390 :1.101 /org/freesmartphone/Preferences at 0x405a05b0 implementing 'org.freesmartphone.Preferences' at 0x405a0690 2011-07-04 19:48:00,521 DEBUG failcount = 0 2011-07-04 19:48:00,532 DEBUG
Re: FR non encrypted calls
El día Monday, July 04, 2011 a las 09:35:24AM +0300, Timo Juhani Lindfors escribió: Matthias Apitz g...@unixarea.de writes: Is the FR capable to show that the call runs in non encrypted mode because the BS forced the ME to this mode? The question is for Om2008.9 but as well valid for any other distribution running on the FR. I think the GSM part (Calypso) delivers this information in the AT%CPRI message. With ogsmd (part of the python version of fso-frameworkd) I have lines like Jul 3 11:57:43 ginger org.freesmartphone.GSM.Network.CypherStatus: enabled: unknown in /var/log/syslog. om2008.9 does not use ogsmd afaik but gsmd. I did some tests sending down AT-cmds with the 'chat' command and watching the AT chatting in /var/log/messages: Per default it is set to off: root@om-gta02:~# chat -vs /dev/ttySAC0 /dev/ttySAC0 '' 'AT%CPRI?' Jul 5 07:39:50 om-gta02 local2.info chat[1556]: send (AT%CPRI?^M) Jul 5 07:39:50 om-gta02 user.notice root: AtChat : ? : %CPRI: 0 Jul 5 07:39:50 om-gta02 user.notice root: AtChat : ? : OK Then I switched it on with: root@om-gta02:~# chat -vs /dev/ttySAC0 /dev/ttySAC0 '' 'AT%CPRI=1' which gives in the /var/log/messages: Jul 5 07:41:37 om-gta02 local2.info chat[1557]: send (AT%CPRI=1^M) Jul 5 07:41:37 om-gta02 user.notice root: AtChat : ? : OK then I dialed a number: Jul 5 07:43:49 om-gta02 user.notice root: AtChat : T : ATD089; Jul 5 07:43:51 om-gta02 user.notice root: AtChat : N : +CSSI: 1 Jul 5 07:44:17 om-gta02 user.notice root: AtChat : F : OK Jul 5 07:44:17 om-gta02 user.notice root: Modem : QModemCall::dialRequestDone() Jul 5 07:44:17 om-gta02 user.notice root: AtChat : T : AT+CLCC Jul 5 07:44:17 om-gta02 user.notice root: AtChat : F : %CPRI: 1,2 Jul 5 07:44:17 om-gta02 user.notice root: AtChat : F : OK Jul 5 07:44:17 om-gta02 user.notice root: Modem : dialing was ok, we are connected Jul 5 07:44:23 om-gta02 user.notice root: Modem : QModemCall::hangup() Jul 5 07:44:23 om-gta02 user.notice root: AtChat : T : AT+CHLD=1 Jul 5 07:44:23 om-gta02 user.notice root: Modem : hangup groups Jul 5 07:44:23 om-gta02 user.notice root: AtChat : F : OK as you see, one of the result code of the TE is %CPRI: 1,2, where the '1' is for GSM (ciphering enabled) and the '2' for GPRS (ciphering state not applicable), see also page 167 for the values in http://www.cartft.com/support_db/support_files/CTFPND-3_AT_Command_Reference.pdf with a bit of tweaking, at least this information is visible in the log files if the connection is ciphered or not. HIH matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
