Hi,
qtmoko v55 is now available. You can get it from here [1] or visit our
homepage [2].
Changes since v54:
* back to cruxus media engine until gstreamer bugs are fixed
* whereabouts use gpsd (Stefan Wildemann)
* navit bugs in town search and program exit fixed (Stefan Wildemann)
Let's
Hi,
i tried to update and get:
root@neo:~# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
qtmoko-navit
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
root@neo:~# apt-get
Hi, I updated and got the following problem:
root@neo:~# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
qtmoko-navit
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
root@n
On Monday, March 25, 2013 08:49:17 AM Radek Polak wrote:
> Hi,
> qtmoko v55 is now available. You can get it from here [1] or visit our
> homepage [2].
>
> Changes since v54:
>
> * back to cruxus media engine until gstreamer bugs are fixed
> * whereabouts use gpsd (Ste
Il 25/03/2013 10.13, Radek Polak ha scritto:
Hmms, i should have tested it better. It seems that web browser now
does not start. I'll have a look and see what we can do...
Regards
Radek
___
Openmoko community mailing list
community@lists.openmok
On Tuesday, March 26, 2013 08:07:06 AM nitpi...@arcor.de wrote:
> Hi, I updated and got the following problem:
>
> root@neo:~# apt-get upgrade
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages have been kept back:
> qtmoko-na
This is surely a basic question, but I am stuck.
If i lock my phone I can't unlock it.
Pressing the power key brings up a tool tip
"press unlock then * to unlock phone"
I've tried following these instructions
pressing the padlock (1) on the left hand border (2) on the bottom left
corner or (3) in
On Thursday, April 25, 2013 12:54:36 AM Liz wrote:
> This is surely a basic question, but I am stuck.
> If i lock my phone I can't unlock it.
> Pressing the power key brings up a tool tip
> "press unlock then * to unlock phone"
> I've tried following these instructions
> pressing the padlock (1) o
On Thu, 25 Apr 2013 08:46:12 +0200
Radek Polak wrote:
> On Thursday, April 25, 2013 12:54:36 AM Liz wrote:
>
> > This is surely a basic question, but I am stuck.
> > If i lock my phone I can't unlock it.
> > Pressing the power key brings up a tool tip
> > "press unlock then * to unlock phone"
>
After upgrade of QTMoko to latest v55 my GTA02 don't wake-up to fully
functional state after some random time (more suspends/resumes and
uptime of some days). Looks like the flash didn't become available/writable.
Seeing these messages:
[64691.81] s3c-sdi s3c2440-sdi: running at 400kHz (reque
On Sunday, January 19, 2014 08:21:20 PM Peter Viskup wrote:
> After upgrade of QTMoko to latest v55 my GTA02 don't wake-up to fully
> functional state after some random time (more suspends/resumes and
> uptime of some days). Looks like the flash didn't become
> available/writable.
>
> Seeing thes
Radek Polak:
> On Sunday, January 19, 2014 08:21:20 PM Peter Viskup wrote:
> Btw can you try if USB networking works in this state?
>
Yes - USB network is available and screen is blank with non-blinking
cursor in left top corner.
___
Openmoko community
Hi,
i have now moved the experimental wheezy based qtmoko v55 to stable. I have
also fixed the ubifs image so that it now boots ok (thanks to gena2x).
I am not aware of any regressions and now it should be easier to support GTA02
and GTA04 because of same package versions etc...
The wheezy
Hi Radek,
thanks a lot.
I've tried it and found no regressions as well.
Just a stupid question: do have I to change something in the repo list?
Cheers,
Giacomo
> Hi,
>
> i have now moved the experimental wheezy based qtmoko v55 to stable. I
> have also fixed the ubifs ima
Thank you very much Radek! I will try it this evening.
Best regards
Matteo
Il 16/04/2013 14.35, Radek Polak ha scritto:
Hi,
i have now moved the experimental wheezy based qtmoko v55 to stable. I
have also fixed the ubifs image so that it now boots ok (thanks to
gena2x).
I am not aware
Thank you
uro
On Tue, 16 Apr 2013 15:16:50 +0200, Matteo Zaffonato
wrote:
Thank you very much Radek! I will try it this evening.
Best regards
Matteo
Il 16/04/2013 14.35, Radek Polak ha scritto:
Hi,
i have now moved the experimental wheezy based qtmoko v55 to stable. I
have also fixed
649.86] ar6000_ioctl_siwauth(): Unknown flag 0xc
[ 9176.57] ar6000_ioctl_siwauth(): Unknown flag 0xc
[ 9196.61] ar6000_ioctl_siwauth(): Unknown flag 0xc
Any hint?
Regards,
On Tue, 2013-04-16 at 14:35 +0200, Radek Polak wrote:
> Hi,
>
> i have now moved the experimental wheezy
On Thursday, April 18, 2013 04:59:54 PM Tiago B. Vaz wrote:
> Thanks Radek!
>
> I don't know if it's a hardware issue, but after upgrading to v55 my
> wireless stopped working. Relevant output from dmesg:
>
> [3.72] AR6000 Reg Code = 0x4060
> [ 8417.06] AR6000 disconnected
> [ 84
I have a wpa psk secured network at home and everything worked out of the
box.
Many thanks for keeping the GTA02 image of qtmoko alive!!!
br
robin
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/list
hi radek,
thanks a lot again for the new gta02 version.
what is the best way to do a clean upgrade (transferring sms and contacts?)
if I remember correctly one can send the contacts to onself via email and
then clicking on the mail would import them. is this still correct? do
alternative options
hi,
I tried to run navit (installed directly from qtmoko apps) but it
instantaneously crashes.
what is the best way to get the logs?
br
robin
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinf
Hi,
I had the same problem with navit, but not yet reported it,
because there are so many other weak points that take time to find.
To see the console messages, including error messages,
login via ssh for a shell command line, then enter
root@neo:/root# . /opt/qtmoko/qpe.env
to set the environm
Am Sonntag, 21. April 2013, 07:47:50 schrieb Rainer Glaschick:
> Hi,
>
> I had the same problem with navit, but not yet reported it,
> because there are so many other weak points that take time to find.
>
> To see the console messages, including error messages,
> login via ssh for a shell command
On Saturday, April 20, 2013 09:02:11 AM robin wrote:
> hi radek,
>
> thanks a lot again for the new gta02 version.
> what is the best way to do a clean upgrade (transferring sms and contacts?)
> if I remember correctly one can send the contacts to onself via email and
> then clicking on the mail
On Tue, 16 Apr 2013 14:35:47 +0200, Radek Polak wrote:
Hi,
i have now moved the experimental wheezy based qtmoko v55 to stable.
Just a heads-up for the next pure-wheezy version:
Upgrading gpsd from 2.95 (squeeze, and installed in v55) to 3.6 (wheezy)
results in gpsd no longer recognizing
On Sunday, May 12, 2013 11:47:26 AM Raphael Wimmer wrote:
> On Tue, 16 Apr 2013 14:35:47 +0200, Radek Polak wrote:
> > Hi,
> > i have now moved the experimental wheezy based qtmoko v55 to stable.
>
> Just a heads-up for the next pure-wheezy version:
> Upgrading gpsd
On Sun, 12 May 2013 17:36:35 +0200, Radek Polak wrote:
[...]
Hi,
is it configured properly? Make sure you have these values in
/etc/default/gpsd:
START_DAEMON="true"
DEVICES="/dev/ttySAC1"
GPSD_OPTIONS="-b"
The config file is correct. I'll reinstall v55 from scratch to check if I
did any o
Am 16.04.2013 14:35, schrieb Radek Polak:
..
The wheezy images are now here:
https://sourceforge.net/projects/qtmoko/files/GTA02/
Hallo,
i installed the wheezy-Version 55 for GTA02 on a uSD-Card.
Formatted as ext3, copyd the archiv and:
$ tar xzvpf qtmoko-debian-gta02-v55.tar.gz
After reboot
Hello!
I don't remember the solution, but there was already a discussion about
that here :
http://comments.gmane.org/gmane.comp.handhelds.openmoko.community/63237
IIRC, udevd isn't relevant for GTA02 (but needed for GTA04) and so it
can be deactivated.
Regards,
Adrien
Le mercredi 22 mai 2013 à
On Monday, January 20, 2014 05:04:53 PM Jake Drexel wrote:
> the mmc0 device is actually where the ar6000 (wifi) is conneted. I had
> the same problem with the 2.6.39 kernel on shr. The issue looks hw and
> sw related. My wifi-board was not connected very well but with older
> kernel it still work
On Tue, Jan 21, 2014 at 08:15:27AM +0100, Radek Polak wrote:
> I tried rmmod ar6000 and i cant reproduce my resume issues anymore! I had
> running my dial script over night. Freerunner now shows 333 succesful
> resumes,
> while it used to fail after 30 resumes before.
>
> So please if you are u
hi radek,
thank for digging in so deep to find the bug. If I remove the ar6000 does
that also mean that I will not be able to use wifi (that would be my guess)?
and as an off topic question: if I remove btusb and bluetooth (as I am not
using bluetooth at all) would this somehow interfere with qt
On Tuesday, January 21, 2014 10:53:08 AM robin wrote:
> hi radek,
>
> thank for digging in so deep to find the bug. If I remove the ar6000 does
> that also mean that I will not be able to use wifi (that would be my
> guess)?
Yes
Maybe it would be possible to use before-suspend.sh and after-resu
On Tuesday, January 21, 2014 10:21:09 AM Jake Drexel wrote:
> On 1/21/14, Jake Drexel wrote:
> > Good to hear that. The strange thing is that the issue also is hw
> > dependend. After I took apart my phone, reseated the wifi-board, put
> > it back together, and replaced the two screws which I uns
Hi Radek, all,
>
>
> Hi,
>
> it seems that thanks to your mail we have discovered resume problems
> on 2.6.39 kernels!
>
>
>
> I tried rmmod ar6000 and i cant reproduce my resume issues anymore! I
> had running my dial script over night. Freerunner now shows 333
> succesful resumes, while it us
On Monday, January 27, 2014 02:29:10 PM Giacomo 'giotti' Mariani wrote:
> Hi Radek, all,
>
> > Hi,
> >
> > it seems that thanks to your mail we have discovered resume problems
> > on 2.6.39 kernels!
> >
> >
> >
> > I tried rmmod ar6000 and i cant reproduce my resume issues anymore! I
> > had r
Radek Polak:
> On Monday, January 20, 2014 05:04:53 PM Jake Drexel wrote:
>
>> the mmc0 device is actually where the ar6000 (wifi) is conneted. I had
>> the same problem with the 2.6.39 kernel on shr. The issue looks hw and
>> sw related. My wifi-board was not connected very well but with older
>>
37 matches
Mail list logo