Re: bugs QtMoko v31
2011-01...@18:07 Radek Polak > > - I'm no longer able to connect to wifi and while I try I see console > > messages over the framebuffer graphic screen - gprs does not connect too > > No longer means that in v30 it worked? I dont see any messages and my wifi > connects. Maybe we have different setup? Do you use qi or uboot? > > I have tested both gprs and wifi and it works, also it works for others. We > have to find out what is wrong. Please give as much details as possible. sorry, with wifi I was out of the covered range due of interferences from a cordless phone near the antenna: in other words it's ok! btw I do see console messages through the framebuffer screen (like white terminal line over the graphic gui) every time I enable/disable the wifi connection. maybe it's related to the vt switch? about the gprs the problem is the multiplexer: when it's enabled it's not possible to use the gprs data connection. when you turn off the multiplexer it's ok but it's highly probable to loose sms or calls. > > > - the long awaited rollback for the power profile "when locked" is still on > > the to-do list > > I was trying to look at it and at first sight i havent found what is wrong. I > have to find the discussion we had last time to refresh my memory. the culprit is the "on lock" scenario because all the profiles (general, silent, meeting...etc) could support different power management properties each, but maybe the saved array does not take in account a third choice other than on cable and on battery and so begin the chaos both in the gui and in the actual values used in memory. by now it'd be safe to rollback to the original state and forget about the "on lock" buggy feature. we can achieve the same feature just configuring ad-hoc different profiles. the current implementation has too much negative side effects. > > > - if you put qtmoko on uSD you cannot use the usb-storage > > because /opt/qtmoko/bin/usb-mass-storage-on.sh tries to use (and unmount) > > the whole uSD instead of a single partition and the root with qtmoko is on > > the same device > > Any ideas how to solve this? I sent to you an early suggested workaround: in the current "on" script you have to specify a single partition instead of the whole uSD eg: my current partition table is mmcblk0p1=/media/card (fat32 used as usb storage), p2=/ (qtmoko root), p3=swap (little extra memory). in the script I've specified to use only p1 and commented out / modified all the mount checks because they works only with a whole device in mind. I'm not saying this is a nice solution but at least it does not destroy your qtmoko/root filesystem! (->dangerous only if you have qtmoko on uSD too) kind regards and good year to all folks! -- ALFA21 IS PROVIDED "AS IS" AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: bugs QtMoko v31
BTW ... mine Eyepiece did ask for some aditional libraries on the first run and then succesfully apt-got them. Zb. Radek Polak píše v St 05. 01. 2011 v 10:34 +0100: > Nashvin Gangaram wrote: > > > Hi Radek > > > > Everything's working great in QtMoko v31... except for Eyepiece. > > > > I get an error: > > "Error: cannot load plugin" > > when trying to open PDF files. Is libdjvulibre21 required to view PDF > > files now? > > Yup it's needed for PDF files. Eyepiece should install it on the first run, > but > if that somehow does not work, you can install manually with apt-get from > command line. > > 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: bugs QtMoko v31
Nashvin Gangaram wrote: > Hi Radek > > Everything's working great in QtMoko v31... except for Eyepiece. > > I get an error: > "Error: cannot load plugin" > when trying to open PDF files. Is libdjvulibre21 required to view PDF > files now? Yup it's needed for PDF files. Eyepiece should install it on the first run, but if that somehow does not work, you can install manually with apt-get from command line. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: bugs QtMoko v31
Hi Radek Everything's working great in QtMoko v31... except for Eyepiece. I get an error: "Error: cannot load plugin" when trying to open PDF files. Is libdjvulibre21 required to view PDF files now? Thanks -Nashvin ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: bugs QtMoko v31
>> - the long awaited rollback for the power profile "when locked" is still on >> the to-do list > I was trying to look at it and at first sight i havent found what is > wrong. I > have to find the discussion we had last time to refresh my memory. >- Power management still confuses or loses battery/cable settings, only "when locked" settings work. In $HOME/Settings/Trolltech/qpe.conf paste "Lock/External/BatteryPower" settings from previously working version, and do not run "Settings/Power management". - Thank you for your attention. -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/QtMoko-v31-tp5881425p5888394.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: bugs QtMoko v31
Marco wrote: > Everything's working fine, except a few glitches when using > programs under QX. In particular even if I select "Use virtual > keyboard" in the setting, it still doesn't appear; It has simple workaround. Go to the textbox (which reads "xterm") and switch to docked keyboard there. Now when you launch your app the docked keyboard should appear. > even when selecting "use window manager" there's no window > around the application, so the only way to close the application > is pressing the AUX button. The default window manager in QX is very simple (just a few lines). It just handles window size so that it does not redraw qtopia toolbar. If you need real window manager, you can select "use matchbox" in app settings. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: bugs QtMoko v31
Hi Radek, amazing work as always, this version is as faster as ever. Everything's working fine, except a few glitches when using programs under QX. In particular even if I select "Use virtual keyboard" in the setting, it still doesn't appear; also, even when selecting "use window manager" there's no window around the application, so the only way to close the application is pressing the AUX button. Again, thank for all your efforts and support!! -- Marco ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: bugs QtMoko v31
Alfa21 wrote: > you can now remove the folded arrows keys and make the others bigger (home, > ins, del...) Well it's just half of normal key, so you can make just one button 50% wider. Maybe the folded are could have some good use - fn keys or something else. Let's give it a few more days what people will come with. But removing that key is for sure good option. > bugs: > - I'm no longer able to connect to wifi and while I try I see console > messages over the framebuffer graphic screen - gprs does not connect too No longer means that in v30 it worked? I dont see any messages and my wifi connects. Maybe we have different setup? Do you use qi or uboot? I have tested both gprs and wifi and it works, also it works for others. We have to find out what is wrong. Please give as much details as possible. > - the long awaited rollback for the power profile "when locked" is still on > the to-do list I was trying to look at it and at first sight i havent found what is wrong. I have to find the discussion we had last time to refresh my memory. > - if you put qtmoko on uSD you cannot use the usb-storage > because /opt/qtmoko/bin/usb-mass-storage-on.sh tries to use (and unmount) > the whole uSD instead of a single partition and the root with qtmoko is on > the same device Any ideas how to solve this? Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
bugs QtMoko v31
2010-12...@16:40 Radek Polak > - better layout in docked keyboard you can now remove the folded arrows keys and make the others bigger (home, ins, del...) bugs: - I'm no longer able to connect to wifi and while I try I see console messages over the framebuffer graphic screen - gprs does not connect too - the long awaited rollback for the power profile "when locked" is still on the to-do list - if you put qtmoko on uSD you cannot use the usb-storage because /opt/qtmoko/bin/usb-mass-storage-on.sh tries to use (and unmount) the whole uSD instead of a single partition and the root with qtmoko is on the same device -- ALFA21 IS PROVIDED "AS IS" AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
