Re: 2.6.39 failed resume
> i am now running 2.6.39 on my Freerunner for 7days. It works well, except > that > 3 times it failed to resume, or something like that. The symptom is that > after > pressing POWER button it does not react. I tried to make a call to my number > and it was not ringing the voice told me that my number is not responding. I > also tried long POWER button press - but it was not reacting. And last thing > i > tried to plub USB cable, but no response. > > Anyone else seen this too? I am using QtMoko v58 Yep, same here, QtMoko v58. I'm using my Freerunner as a daily phone and it failed to resume at least once in a day in the past week. Deep sleep is disabled, and the Power Management settings should not give any problems. Regards Joif ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Larger capacity battery
On Fri, Dec 20, 2013 at 7:39 AM, joerg Reisenweber wrote: > > Maybe useful background can be found in: > http://talk.maemo.org/showthread.php?t=65568 jOERG, That's a pretty handy page. I hadn't realized LiIon batteries varied much by manufacturer. Is there a similar script for the Freerunner which can perform the same battery capacity test? —B ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v58 - best way to upgrade
I've got v58 working now (thanks to the logging kludge) and have not had a problem with resuming yet. I did have a lot of reports initially of people trying to call me and my phone not ringing, but after I turned off multiplexing in Neocontrol things seem to be better. (I've never had to turn off multiplexing before, so I'm not sure why that helped this time.) Speaking of kernel bugs, I did have a kernel panic when a second call came in while I was already on the phone. [Fortunately, (thanks to the nifty design of the Freerunner) I was able to keep talking on the phone even with a hung kernel!] By the way, call waiting did work in the previous version of qtmoko, but it had a bug such that I wouldn't be able to hear the other person until I put them on speaker phone. —B On Sun, Dec 22, 2013 at 10:24 AM, Radek Polak wrote: > On Sunday, December 22, 2013 06:47:05 PM Nick wrote: > >> Many thanks Radek for keeping QtMoko going! My FreeRunner has been >> my daily phone for about the last year thanks to it, and it >> generally works really well. >> >> Can I upgrade to v58 by just doing a 'apt-get update && apt-get >> dist-upgrade', or should I flash it afresh? > > Hmm there have been a lot of changes, e.g. in apt sources.list, so reflash is > IMO better. It should be ok to backup and restore your /home/root dir. > > Btw i have doubts that our 2.6.39 kernel is really bug free. My Freerunner > failed like 3 times to resume during those 6 days i am using it :( I wonder if > it is just my phone or others seen it too? > > Regards > > Radek > > ___ > 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: Use of a FreeRunner
On Sun, Dec 22, 2013 at 11:43 PM, Philip Rhoades wrote: > Ben, > > > > On 2013-12-23 09:26, Ben Wong wrote: >> >> I'm sure it could; your FreeRunner is a complete computer. >> >> The question is if you have the time (or money to hire someone) to >> write the glue script that will put all the pieces together. Let's >> see, the parts you'll need are: >> >> 1. Check your mail account (fetchmail or python's imaplib) >> 2. Do a regex check to see if it's "important" (egrep/python/perl/awk/...) > > > > I can do those bits. > > > >> 3. Convert it to SMS format >> 3a. MIME extract (munpack or python's email package) >> 3b. Optionally remove HTML markup (lynx -dump or Beautiful Soup's >> get_text() function) > > > > and probably those bits - actually now that I think about it - there would > always just be a little bit of text (the messages would always be coming > from a phone message service) with an appended WAV file so it would have to > be MMS rather that SMS . . > > > >> 4. Send it as an SMS messages (dbus to FSO works but may not be "best >> practices") > > > > This is the bit I know nothing about . . > > Thanks, > > Phil. Sending SMS using FSO is very easy: http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.GSM.SMS.html;hb=HEAD#SendTextMessage You can use mdbus2 or dbus-send, or any dbus binding for your language of choice. SendTextMessage even handles multi-part messages automatically for you. I'm not aware of any existing MMS implementation for FSO. Cheers, -- Sebastian Krzyszkowiak, dos http://dosowisko.net/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Use of a FreeRunner
Ben, On 2013-12-23 09:26, Ben Wong wrote: I'm sure it could; your FreeRunner is a complete computer. The question is if you have the time (or money to hire someone) to write the glue script that will put all the pieces together. Let's see, the parts you'll need are: 1. Check your mail account (fetchmail or python's imaplib) 2. Do a regex check to see if it's "important" (egrep/python/perl/awk/...) I can do those bits. 3. Convert it to SMS format 3a. MIME extract (munpack or python's email package) 3b. Optionally remove HTML markup (lynx -dump or Beautiful Soup's get_text() function) and probably those bits - actually now that I think about it - there would always just be a little bit of text (the messages would always be coming from a phone message service) with an appended WAV file so it would have to be MMS rather that SMS . . 4. Send it as an SMS messages (dbus to FSO works but may not be "best practices") This is the bit I know nothing about . . Thanks, Phil. —B On Sat, Dec 21, 2013 at 2:58 AM, Philip Rhoades wrote: People, I have not used my FreeRunner for ages and probably should donate it someone who can make use of it but a thought occurred to me: It would be good to have something that could act like a SMS server eg I have a demand where if an (urgent) email comes into a particular account, that the contents of the email are able to be resent as an SMS out through a mobile device gateway to a number of phones - could OpenMoko be rejigged to do this somehow? Regards, Phil. -- Philip Rhoades GPO Box 3411 Sydney NSW 2001 Australia E-mail: p...@pricom.com.au ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Philip Rhoades GPO Box 3411 Sydney NSW 2001 Australia E-mail: p...@pricom.com.au ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Use of a FreeRunner
I'm sure it could; your FreeRunner is a complete computer. The question is if you have the time (or money to hire someone) to write the glue script that will put all the pieces together. Let's see, the parts you'll need are: 1. Check your mail account (fetchmail or python's imaplib) 2. Do a regex check to see if it's "important" (egrep/python/perl/awk/...) 3. Convert it to SMS format 3a. MIME extract (munpack or python's email package) 3b. Optionally remove HTML markup (lynx -dump or Beautiful Soup's get_text() function) 4. Send it as an SMS messages (dbus to FSO works but may not be "best practices") —B On Sat, Dec 21, 2013 at 2:58 AM, Philip Rhoades wrote: > People, > > I have not used my FreeRunner for ages and probably should donate it someone > who can make use of it but a thought occurred to me: It would be good to > have something that could act like a SMS server eg I have a demand where if > an (urgent) email comes into a particular account, that the contents of the > email are able to be resent as an SMS out through a mobile device gateway to > a number of phones - could OpenMoko be rejigged to do this somehow? > > Regards, > > Phil. > -- > Philip Rhoades > > GPO Box 3411 > Sydney NSW 2001 > Australia > E-mail: p...@pricom.com.au > > ___ > 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: qtmoko: stuck at no more processes left in this runlevel
On Sunday, December 22, 2013 08:05:25 PM robin wrote: > # cat /etc/modules > g_ether > ppp_generic > joydev > bq27000_battery This is not correct. From rootfs docs it should be: echo g_ether > /etc/modules echo ppp_generic >> /etc/modules echo bq27x00_battery >> /etc/modules echo ohci_hcd >> /etc/modules echo snd-soc-neo1973-wm8753 >> /etc/modules echo ar6000 >> /etc/modules echo btusb >> /etc/modules echo bluetooth >> /etc/modules echo snd-soc-neo1973-wm8753 >> /etc/modules echo snd-soc-wm8753 >> /etc/modules echo snd-soc-dfbmcs320 >> /etc/modules echo snd-soc-neo1973-wm8753 >> /etc/modules echo snd_soc_s3c24xx >> /etc/modules To me this looks like upgrade from some old version, but since we have new kernel and apt sources and so on you have to do all the steps manually according to changes in git. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko: stuck at no more processes left in this runlevel
doing lsmod I get the following if that is of any help root@neo:~# lsmod Module Size Used by ipt_REJECT 1943 1 iptable_filter 958 1 ip_tables 9486 1 iptable_filter ip6t_REJECT 2294 1 xt_tcpudp 1921 2 ip6table_filter 905 1 ip6_tables 10341 1 ip6table_filter x_tables 11091 7 ip6_tables,ip6table_filter,xt_tcpudp,ip6t_REJECT,ip_tables,iptable_filter, ipt_REJECT bnep9360 2 rfcomm 30219 0 bluetooth 115208 10 rfcomm,bnep ipv6 234431 13 ip6t_REJECT nls_iso8859_1 3099 1 vfat8717 1 fat43504 1 vfat joydev 8333 0 ppp_generic19806 0 slhc4619 1 ppp_generic g_ether30661 0 s3c2410_udc11895 1 g_ether ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko: stuck at no more processes left in this runlevel
the directory is there: #ls 2.6.34-qtmoko-v55 2.6.39-qtmoko-v58 # depmod # reboot did not work so I had a look at depmod and thought that the -a option might be what I need, that though expect something lice /etc/modules.conf which did not find, but I find /etc/modules: so I did this: # cat /etc/modules g_ether ppp_generic joydev bq27000_battery # depmod -a # shutdown -r now but still the same situtation: stoops at INIT no more processes left in this runlevel... any final ideas? br robin ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
2.6.39 failed resume
Hi, i am now running 2.6.39 on my Freerunner for 7days. It works well, except that 3 times it failed to resume, or something like that. The symptom is that after pressing POWER button it does not react. I tried to make a call to my number and it was not ringing the voice told me that my number is not responding. I also tried long POWER button press - but it was not reacting. And last thing i tried to plub USB cable, but no response. Anyone else seen this too? I am using QtMoko v58, the kernel sources are here: https://github.com/radekp/linux-2.6/commits/v2.6.39-gta02-qtmoko-v58 they should be same as SHR, same for kernel config. The kernel is natively compiled on wheezy armel qemu. Any ideas. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v58 - best way to upgrade
On Sunday, December 22, 2013 06:47:05 PM Nick wrote: > Many thanks Radek for keeping QtMoko going! My FreeRunner has been > my daily phone for about the last year thanks to it, and it > generally works really well. > > Can I upgrade to v58 by just doing a 'apt-get update && apt-get > dist-upgrade', or should I flash it afresh? Hmm there have been a lot of changes, e.g. in apt sources.list, so reflash is IMO better. It should be ok to backup and restore your /home/root dir. Btw i have doubts that our 2.6.39 kernel is really bug free. My Freerunner failed like 3 times to resume during those 6 days i am using it :( I wonder if it is just my phone or others seen it too? Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v58 - best way to upgrade
Many thanks Radek for keeping QtMoko going! My FreeRunner has been my daily phone for about the last year thanks to it, and it generally works really well. Can I upgrade to v58 by just doing a 'apt-get update && apt-get dist-upgrade', or should I flash it afresh? Nick ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko: stuck at no more processes left in this runlevel
On Sunday, December 22, 2013 08:11:47 AM robin wrote:
> hi radek,
>
> I went back to your previous reply and issued the commands that you
> suggested. now this is the output with the newer kernel loaded:
>
> root@neo:~# . /opt/qtmoko/qpe.env
> root@neo:/root# qpe
> NeoKbdDriverPlugin:create()
> Before call NeoKbdHandler()
> Cannot open input device for Headset Jack
> readFile failed /sys/class/power_supply/battery/status : No such file
> or directory
> 56788 0
> QDBusObjectPath: invalid path ""
> Method call "/->DefaultAdapter()" failed:
> QDBusError("org.bluez.Error.NoSuchAdapter", "No such adapter")
> QDBusObjectPath: invalid path ""
> Method call "/->DefaultAdapter()" failed:
> QDBusError("org.bluez.Error.NoSuchAdapter", "No such adapter")
> QDBusObjectPath: invalid path ""
> Method call "/->DefaultAdapter()" failed:
> QDBusError("org.bluez.Error.NoSuchAdapter", "No such adapter")
> QDBusObjectPath: invalid path ""
> Method call "/->DefaultAdapter()" failed:
> QDBusError("org.bluez.Error.NoSuchAdapter", "No such adapter")
> QDBusObjectPath: invalid path ""
> Method call "/->DefaultAdapter()" failed:
> QDBusError("org.bluez.Error.NoSuchAdapter", "No such adapter")
> QDBusObjectPath: invalid path ""
> Method call "/->DefaultAdapter()" failed:
> QDBusError("org.bluez.Error.NoSuchAdapter", "No such adapter")
> QDBusObjectPath: invalid path ""
> Method call "/->DefaultAdapter()" failed:
> QDBusError("org.bluez.Error.NoSuchAdapter", "No such adapter")
> 0
> snd_mixer_attach error -2
> qpe: mixer.c:788: snd_mixer_first_elem: Assertion `mixer' failed.
> Aborted
> root@neo:/root#
>
>
> does this give you any hints on where this is going wrong?
It looks that you dont have any modules loaded. Can you check if you have
/lib/modules/2.6.39-qtmoko-v58 directory? If yes you can try depmod command
and reboot. If no, you have to unpack it e.g. from the .deb
Reagards
Radek
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
