Re: The myth of missed phone calls (was: OM2008.12 - basic usage instructions?)
Paul wrote: >The distro I've used that missed phone calls the most was FSO, zhone was >pretty unstable. But I have missed calls on SHR and OM2008.12. >OM2008.12 has terrible echo and is unusable last I tried. It's true that Om2008.12 is unusable (for mobile phone use). But is this relevant any longer? And which version of FSO did you use? Testing versions of Om2009 (based on FSO milestone 5.5) are available: http://wiki.openmoko.org/wiki/Om2009 Nick ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: The myth of missed phone calls (was: OM2008.12 - basic usage instructions?)
Am Do 23. April 2009 schrieb Nicola Mfb: > 2009/4/20 Daniel Willmann : > [...] > > I'm curious, what distro are you using? I would be pretty surprised if > > carrier differences are having that effect. > > May the gsm firmware influence that? For sure. MOKO11 fixes the "doesn't resume from 1. suspend after GSM powerup" issue. We recommend flashing MOKO11 using the uSD method described in http://wiki.openmoko.org/wiki/GSM/Flashing#uSD-card_Image /j signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [SHR] Vibrate only on alarm
Jeffrey Ratcliffe wrote: > ATM, the alarm app rings a nice old alarm clock ring. Is there any way > of getting it to honour the profile, and when needed only vibrate? Not without changing the source code significantly. elementary-alarm is a test app in the enlightenment source repository that doesn't know anything about profiles (and probably shouldn't need to rely on them either. spaetz ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [SHR testing] Phonelog borks Dbus
I think the order is different - Phonelog crashes because frameworkd dBus is not running. Happens sometimes. Leonti On Thu, Apr 23, 2009 at 8:46 AM, wrote: > If I start Phonelog, it crashes, borking Dbus along the way. > > I seem to have to reboot the phone to sort things out. > > What can I do to fix this? > > Regards > > Jeff > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [SHR testing] Phonelog borks Dbus
On Thursday 23 April 2009 02:46:36 am jeffrey.ratcli...@gmail.com wrote: > If I start Phonelog, it crashes, borking Dbus along the way. > > I seem to have to reboot the phone to sort things out. > > What can I do to fix this? > > Regards > > Jeff Which SHR-Testing are you using? In the release prior to the 4/16 one I have noticed that and got use to restarting my phone at the first sign of something crashing. In the latest release this seems fixed, I am able to use the phonelog just fine, after the wait while it gets the information or what ever it does. In the latest release the only way I have been able to bork Dbus is if I try and go into the Settings and change something before my phone is registered with my network. signature.asc Description: This is a digitally signed message part. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Re: [SHR testing] Phonelog borks Dbus
On Apr 23, 2009 12:49pm, Adam Jimerson wrote: Which SHR-Testing are you using? In the release prior to the 4/16 one I have noticed that and got use to restarting my phone at the first sign of something crashing. In the latest release this seems fixed, I am able to use the phonelog just fine, after the wait while it gets the information or what ever it does. In the latest release the only way I have been able to bork Dbus is if I try and go into the Settings and change something before my phone is registered with my network. I downloaded the image a couple of days ago, and have been opkg update and upgrading daily. Up to now, I have not managed to get Phonelog to start, and after every attempt, nothing else works either. If I don't start Phonelog, then I can access the settings, etc. OK. Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: The myth of missed phone calls (was: OM2008.12 - basic usage instructions?)
On Wed, Apr 22, 2009 at 11:08:14PM -0400, Paul wrote: > The distro I've used that missed phone calls the most was FSO, zhone was > pretty unstable. But I have missed calls on SHR and OM2008.12. OM2008.12 > has terrible echo and is unusable last I tried. > > If there were new patches since Feb, I'll be out of date. I had to get a > real phone because I couldn't use my freerunner. There was a GSM firmware bug such that you would miss all calls during the first suspend after a reboot or power on[1]. It will happen when the firmware is moko10 or older and your kernel is older than 2009-02-22. Later kernels include a workaround[2] for the firmware bug and the moko11 firmware[3] from 2009-02-24 fixes the bug. [1] https://lists.openmoko.org/pipermail/openmoko-kernel/2009-February/008497.html [2] https://lists.openmoko.org/pipermail/openmoko-kernel/2009-February/008832.html [3] https://people.openmoko.org/joerg/calypso_moko_FW/moko11/ -- Rask Ingemann Lambertsen Danish law requires addresses in e-mail to be logged and stored for a year ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: The myth of missed phone calls (was: OM2008.12 - basic usage instructions?)
I would like to see with a release of a distro, a list (and links to) all the images to recreate the build exactly. Right now there are way too many variables, what version of Qi, bootloader, etc. This will enable people to recreate, exactly, the desired distro in question. On Thu, Apr 23, 2009 at 8:45 AM, Rask Ingemann Lambertsen wrote: > On Wed, Apr 22, 2009 at 11:08:14PM -0400, Paul wrote: > > The distro I've used that missed phone calls the most was FSO, zhone was > > pretty unstable. But I have missed calls on SHR and OM2008.12. > OM2008.12 > > has terrible echo and is unusable last I tried. > > > > If there were new patches since Feb, I'll be out of date. I had to get a > > real phone because I couldn't use my freerunner. > >There was a GSM firmware bug such that you would miss all calls during > the first suspend after a reboot or power on[1]. It will happen when the > firmware is moko10 or older and your kernel is older than 2009-02-22. Later > kernels include a workaround[2] for the firmware bug and the moko11 > firmware[3] from 2009-02-24 fixes the bug. > > [1] > > https://lists.openmoko.org/pipermail/openmoko-kernel/2009-February/008497.html > [2] > > https://lists.openmoko.org/pipermail/openmoko-kernel/2009-February/008832.html > [3] https://people.openmoko.org/joerg/calypso_moko_FW/moko11/ > > -- > Rask Ingemann Lambertsen > Danish law requires addresses in e-mail to be logged and stored for a year > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > -- Paul Email - pault...@gmail.com There were moments when he looked on evil simply as a mode through which he could realize his conception of the beautiful. Oscar Wilde - The Picture of Dorian Gray ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[SHR testing] opkg error
I'm getting the following errors after opkg update;opkg upgrade: Collected errors: * ERROR: The following packages conflict with e-wm-menu-shr: * e-wm-menu * * ERROR: Cannot satisfy the following dependencies for task-shr-minimal-x: * glibc-binary-localedata-en-gb * What can I do to fix them? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [SHR testing] opkg error
don't know about the localedate thingy, but try opkg remove -force-depends e-wm-menu opkg install e-wm-menu-shr y On Thu, Apr 23, 2009 at 10:22 PM, Jeffrey Ratcliffe wrote: > I'm getting the following errors after opkg update;opkg upgrade: > > Collected errors: > * ERROR: The following packages conflict with e-wm-menu-shr: > * e-wm-menu * > * ERROR: Cannot satisfy the following dependencies for task-shr-minimal-x: > * glibc-binary-localedata-en-gb * > > What can I do to fix them? > > Regards > > Jeff > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [SHR testing] opkg error
2009/4/23 Yorick Moko : > don't know about the localedate thingy, > > but try > opkg remove -force-depends e-wm-menu > opkg install e-wm-menu-shr Thanks. That sorted out the one error. Anyone else with ideas on the other one? Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [SHR testing] opkg error
Am 23.04.2009 um 16:52 schrieb Jeffrey Ratcliffe: > 2009/4/23 Yorick Moko : >> don't know about the localedate thingy, >> >> but try >> opkg remove -force-depends e-wm-menu >> opkg install e-wm-menu-shr > > Thanks. That sorted out the one error. > > Anyone else with ideas on the other one? I did force it: > opkg install -nodeps task-shr-minimal-x I don't think that the "missing dependency" on glibc-binary-localedata- en-gb does break things (I haven't noticed anything) it made "opkg upgrade" stop complaining. Dirk ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
