[FDOM] GPRS has stopped working - ServiceUnknown (latest fdom)
(I upgraded to testing, didn't get phone working, flashed latest FDOM) I've tried to get GPRS working but for some reason, even though it worked before with 0927 FDOM image easily (just changing the APN), I now get always the following when running gprson: --- Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.pyneo.muxer was not provided by any .service files 1226042707 +++ --- So... what should be done to get GPRS working nowadays? GSM works fine. -Timo ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[FSO] Battery Indicator Problem
I just downloaded the latest FSO image, kernel, and modules, and installed them on my SD card. Everything boots without problems but the battery indicator seems to show a 0% charge even though Qt Extended (installed on the flash) detects the battery as full. If I try to charge the battery, FSO detects the status as charging, but the time to full charge does not change no matter how long I keep charging it. My battery is a CC, and below are the "cat" results which FSO seems to detect (while charging): cat /sys/devices/platform/bq27000-battery.0/power_supply/bat/charge_full: 1184526 cat /sys/devices/platform/bq27000-battery.0/power_supply/bat/current_now: 138750 cat /sys/devices/platform/bq27000-battery.0/power_supply/bat/time_to_full_now: 3932100 cat /sys/devices/platform/bq27000-battery.0/power_supply/bat/capacity: 0 Any ideas on what could be causing this problem and how I can fix it? -- View this message in context: http://n2.nabble.com/-FSO--Battery-Indicator-Problem-tp1467719p1467719.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: connecting to debug board v3
On Thu, Nov 6, 2008 at 4:28 PM, Lars Noodén <[EMAIL PROTECTED]> wrote: > I seem to be unable to connect using cu from either Debian Lenny or > Kubuntu Intrepid. It appears that the connection settings are not correct: > >$ cu -eo -s 115200 -l /dev/ttyUSB0 >Connected. >[EMAIL PROTECTED] > > The board is Openmoko Neo1973 v3 Hi Lars. The serial console is in /dev/ttyUSB1 and not in /dev/ttyUSB0. Regards, Nelson.- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
connecting to debug board v3
I seem to be unable to connect using cu from either Debian Lenny or Kubuntu Intrepid. It appears that the connection settings are not correct: $ cu -eo -s 115200 -l /dev/ttyUSB0 Connected. [EMAIL PROTECTED] The board is Openmoko Neo1973 v3 What are the proper settings for connecting to the debug board? Regards, -Lars ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
2007.9: Anybody found a fix for the events/0 problem yet?
Anybody found a fix for the events/0 problem yet? Woke up this morning and found it at 27% and battery rapidly draining again. And when rebooted 2 SMS messages sent 12 hours before "appeared", again ... Seems like the freerunner just will not run for more that 24hrs (and lucky to get even that long) if you use gps and/or wifi during a session Frustrating ... BillK -- William Kenworthy <[EMAIL PROTECTED]> Home in Perth! ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Accelerometers jerky with new stable kernels?
Timo Jyrinki wrote: > 2008/11/6 Michael Zanetti <[EMAIL PROTECTED]>: >> What do you mean with "working fine now"? Are they working as they were >> always >> or are they now really working (no crashes on suspend or after some minutes >> of >> use)? > > "Working fine" as in accelerometer using applications (I have > AccelGame and Doom) work, unlike with the patch (jerkiness). I don't > use suspend with my own kernels since resume is always broken - > probably because I only flash the self-compiled kernel and don't know > how I could easily also copy the compiled modules into use on Neo. Using this reverting list [1] to get a woking stable kernel (image [2]). With itthe accelerometers work well also after suspend/resume (that works here, since it seems needed to the fix-glamo-mci-slow-clock-until-first-bulk.patch as reported in the kernel ML). I'm using my moko with OpenDoom in these days and all is completely usable! [1] git-revert list to stable. Not completely studied: git-revert --no-edit 933f18caaf8f96d1094f064312d416a2fe0b4337 git-revert --no-edit ca57dbb5effd245e2619f4b730f8247f7279f954 git-revert --no-edit d3c59382c7e8429e2c86eb92cc2518dce26c4a69 git-revert --no-edit 5e2b5ddaf95985744e0e0c28ba6dac83c093fd15 git-revert --no-edit 3318a7cb3165a33046e122294e1878e3bd6555d8 git-revert --no-edit 35d910f40ce2c7c959edfbaa671f88e8da5fa6b1 git-revert --no-edit 1c6f5a92c816db43128444606c26507ebe6e5a43 git-revert --no-edit 73a16ab06c18ae6da52178c8997f097363ca0a17 git-revert --no-edit f43814abe0f52033d5915881016408bd1da29d2b git-revert --no-edit f5b973489beb1a1239dfad53e3ad6e36ff7ee958 git-revert --no-edit 2a6788eaaf0185f8db56353777e8f3f5dab1d665 git-revert --no-edit bc2caff9cdef8a16297a2cb196306f88fa5ea2c2 git-revert --no-edit 968c41d0c32099d78927849a71e2ef3143cc05e7 git-revert --no-edit 9e7ba57b104e9293f746342b7450b10d5fa0c4cd git-revert --no-edit f6b1f49300a24c329f5d1049031f711c6268be95 git-revert --no-edit 853fcd2329b427788677d11431e6165d108f935b git-revert --no-edit ca19d156400f817960efe0d14680324b2ea34171 [2] http://downloads.tuxfamily.org/3v1deb/openmoko/uImage-gta02-stable-3v1n0-git-mixture-2.bin -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Accelerometers jerky with new stable kernels?
2008/11/6 Timo Jyrinki <[EMAIL PROTECTED]>: > -Timo (waiting for the evening or weekend to play more) Ok, lied. Doing echo 10 > /sys/devices/platform/lis302dl.1/threshold echo 10 > /sys/devices/platform/lis302dl.2/threshold fixes the problem on the current testing problem. cat /sys/devices/platform/lis302dl.1/threshold still says 0, and I don't know what's the default value either, but doing those two echo commands after reboot makes it work. So possibly some default could be set according to those... -Timo ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Accelerometers jerky with new stable kernels?
2008/11/6 Timo Jyrinki <[EMAIL PROTECTED]>: > I installed/flashed back the kernel from testing. It might be the > threshold should just be lower. Unfortunately currently it seems that > /sys/devices/platform/lis302dl.1/sample_rate is fixed to 100. Ie. if I > do echo 10 > > /sys/devices/platform/lis302dl.1/sample_rate, it's immediately back to > 100 if I cat it. So I really can't test if the lower value would help. Uh, clearly too busy right now. Anyway the _threshold_ seems to be likewise fixed to 0 currently, ie. cannot be changed. The sample_rate was talked about in the commit notes. -Timo (waiting for the evening or weekend to play more) ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Accelerometers jerky with new stable kernels?
2008/11/6 Michael Zanetti <[EMAIL PROTECTED]>: > What do you mean with "working fine now"? Are they working as they were always > or are they now really working (no crashes on suspend or after some minutes of > use)? "Working fine" as in accelerometer using applications (I have AccelGame and Doom) work, unlike with the patch (jerkiness). I don't use suspend with my own kernels since resume is always broken - probably because I only flash the self-compiled kernel and don't know how I could easily also copy the compiled modules into use on Neo. 2008/11/6 Alastair Johnson <[EMAIL PROTECTED]>: > Does it need reverting, or do you just need to echo a smaller value to > threshold when you want to use the accels for game control? I installed/flashed back the kernel from testing. It might be the threshold should just be lower. Unfortunately currently it seems that /sys/devices/platform/lis302dl.1/sample_rate is fixed to 100. Ie. if I do echo 10 > /sys/devices/platform/lis302dl.1/sample_rate, it's immediately back to 100 if I cat it. So I really can't test if the lower value would help. Reverting is probably pointless as such, as most probably the whole rework on the accelerometer side has it meanings (like the suggested suspend problems), but I just haven't found another way to get accelerometers working fluently without reverting the patch in question. -Timo ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Accelerometers jerky with new stable kernels?
Timo Jyrinki wrote: > 2008/11/6 Andy Green <[EMAIL PROTECTED]>: >> | During the weekend I tried one self-compiled kernel with all the >> | "lis302dl" starting patches from >> | http://git.openmoko.org/?p=kernel.git;a=shortlog;h=stable reverted, >> | but it didn't help at all. Any idea which patch would be causing the >> | problem? >> >> How about this one: >> >> http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=35d910f40ce2c7c959edfbaa671f88e8da5fa6b1 > > Right! Reverting also that one fixed the problem, accelerometers work > fine now again. So apparently that patch would need some more work or > reverting. Does it need reverting, or do you just need to echo a smaller value to threshold when you want to use the accels for game control? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Accelerometers jerky with new stable kernels?
Am Donnerstag 06 November 2008 11:00:02 schrieb Timo Jyrinki: > Right! Reverting also that one fixed the problem, accelerometers work > fine now again. So apparently that patch would need some more work or > reverting. > What do you mean with "working fine now"? Are they working as they were always or are they now really working (no crashes on suspend or after some minutes of use)? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Accelerometers jerky with new stable kernels?
2008/11/6 Andy Green <[EMAIL PROTECTED]>: > | During the weekend I tried one self-compiled kernel with all the > | "lis302dl" starting patches from > | http://git.openmoko.org/?p=kernel.git;a=shortlog;h=stable reverted, > | but it didn't help at all. Any idea which patch would be causing the > | problem? > > How about this one: > > http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=35d910f40ce2c7c959edfbaa671f88e8da5fa6b1 Right! Reverting also that one fixed the problem, accelerometers work fine now again. So apparently that patch would need some more work or reverting. -Timo ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Accelerometers jerky with new stable kernels?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Hi, | | I get huge "stalls" with accelerometers if using the current kernel in | testing or self-compiled stable branch kernel. Eg. in accelgame or | opendoom, the fps is ca. 1-3, sometimes a few frame rapidly in | succession and then 1 second of stalling. Anyone else experiencing the | problem, possibly with a cure? | | During the weekend I tried one self-compiled kernel with all the | "lis302dl" starting patches from | http://git.openmoko.org/?p=kernel.git;a=shortlog;h=stable reverted, | but it didn't help at all. Any idea which patch would be causing the | problem? | | Okay, while writing this I noticed I didn't revert | "fix-lid302dl-bitbang-all-the-way-baby.patch", so it might be it, but | I'd like to hear from others and also if it's a known problem to be | fixed. | | -Timo, wants the accelerometers back (without losing other goodies in | recent stable kernel) How about this one: http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=35d910f40ce2c7c959edfbaa671f88e8da5fa6b1 - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkkSuygACgkQOjLpvpq7dMoQUgCggZ1GSNemdnhdV1BnegngF+3U a5YAniuPHsER0WLhv2k6HSiKlMEhw8sn =zn5m -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Accelerometers jerky with new stable kernels?
Hi, I get huge "stalls" with accelerometers if using the current kernel in testing or self-compiled stable branch kernel. Eg. in accelgame or opendoom, the fps is ca. 1-3, sometimes a few frame rapidly in succession and then 1 second of stalling. Anyone else experiencing the problem, possibly with a cure? During the weekend I tried one self-compiled kernel with all the "lis302dl" starting patches from http://git.openmoko.org/?p=kernel.git;a=shortlog;h=stable reverted, but it didn't help at all. Any idea which patch would be causing the problem? Okay, while writing this I noticed I didn't revert "fix-lid302dl-bitbang-all-the-way-baby.patch", so it might be it, but I'd like to hear from others and also if it's a known problem to be fixed. -Timo, wants the accelerometers back (without losing other goodies in recent stable kernel) ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: gps external antenna
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | How do I tell the FR to use the external antenna instead of the | internal? Nothing about that in the wiki. As folks already said it's automatic: it detects the current eaten by the LNA in the external antenna when it is connected, and switches over to using that instead of internal antenna for the duration. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkkSsuUACgkQOjLpvpq7dMoGnQCgk26Z23UOtAn+UF2mNfScJ6Lz JsAAn25OYGIuJBY7DPfwtUETiuOnltzz =Va8M -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
