Re: QtMoko v33 - More battery info and questions
Paul, On 2011-03-30 19:31, Paul Fertser wrote: Hi, On Tue, Mar 29, 2011 at 06:00:22PM +1100, Philip Rhoades wrote: Philip Rhoadesp...@pricom.com.au writes: - Even with the dumb battery configuration, the battery charging animated icon continues after USB (power) disconnection - should that happen? Provide uevent files contents for both the battery driver and pcf50633-mbc drivers. /sys/devices/platform/s3c2440-i2c/i2c-0/0-0073/pcf50633-mbc.0/power_supply/usb/uevent POWER_SUPPLY_NAME=usb POWER_SUPPLY_TYPE=USB POWER_SUPPLY_ONLINE=1 With USB unplugged this looks like a manifistation of a bug. Please specify the kernel version you use. Sorry, my mistake - I had it plugged in to get easier access to the device . . - The discharge rate attached for an inactive phone (with a blanked screen) with a new, fully charged battery is not very good (~10 hours) Keep in mind that the SoC was constantly running during that test, so this should be ok. Normal usage assumes you use suspend-to-ram when you do not actually interact with the device, that should give ~70 (without #1024 fix) or ~140 (with it) hours of standby time. At the moment dim is set to 20s, display off to 50s and suspend is off - are you saying that suspend should be set to 120s or something? How does that affect incoming calls? Incoming calls should wake up the device without any issues, there's a dedicated irq line for that. Yes, I tested it and it worked fine. I still have a problem with low battery life - I am testing the second new battery to see how that behaves and will update when I have more info. Thanks, 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
Re: QtMoko v33 - More battery info and questions
Hi, On Tue, Mar 29, 2011 at 06:00:22PM +1100, Philip Rhoades wrote: Philip Rhoadesp...@pricom.com.au writes: - Even with the dumb battery configuration, the battery charging animated icon continues after USB (power) disconnection - should that happen? Provide uevent files contents for both the battery driver and pcf50633-mbc drivers. /sys/devices/platform/s3c2440-i2c/i2c-0/0-0073/pcf50633-mbc.0/power_supply/usb/uevent POWER_SUPPLY_NAME=usb POWER_SUPPLY_TYPE=USB POWER_SUPPLY_ONLINE=1 With USB unplugged this looks like a manifistation of a bug. Please specify the kernel version you use. - The discharge rate attached for an inactive phone (with a blanked screen) with a new, fully charged battery is not very good (~10 hours) Keep in mind that the SoC was constantly running during that test, so this should be ok. Normal usage assumes you use suspend-to-ram when you do not actually interact with the device, that should give ~70 (without #1024 fix) or ~140 (with it) hours of standby time. At the moment dim is set to 20s, display off to 50s and suspend is off - are you saying that suspend should be set to 120s or something? How does that affect incoming calls? Incoming calls should wake up the device without any issues, there's a dedicated irq line for that. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v33 - More battery info and questions
Paul, On 2011-03-27 01:42, Paul Fertser wrote: Hi, Philip Rhoadesp...@pricom.com.au writes: - Even with the dumb battery configuration, the battery charging animated icon continues after USB (power) disconnection - should that happen? Provide uevent files contents for both the battery driver and pcf50633-mbc drivers. /sys/class/power_supply/battery/uevent POWER_SUPPLY_NAME=battery POWER_SUPPLY_TYPE=Battery POWER_SUPPLY_PRESENT=1 POWER_SUPPLY_STATUS=Charging POWER_SUPPLY_VOLTAGE_NOW=387 POWER_SUPPLY_CAPACITY=55 POWER_SUPPLY_CHARGE_FULL=85 POWER_SUPPLY_CHARGE_NOW=459000 /sys/devices/platform/s3c2440-i2c/i2c-0/0-0073/pcf50633-mbc.0/uevent DRIVER=pcf50633-mbc MODALIAS=platform:pcf50633-mbc /sys/devices/platform/s3c2440-i2c/i2c-0/0-0073/pcf50633-mbc.0/power_supply/adapter/uevent POWER_SUPPLY_NAME=adapter POWER_SUPPLY_TYPE=Mains POWER_SUPPLY_ONLINE=0 /sys/devices/platform/s3c2440-i2c/i2c-0/0-0073/pcf50633-mbc.0/power_supply/usb/uevent POWER_SUPPLY_NAME=usb POWER_SUPPLY_TYPE=USB POWER_SUPPLY_ONLINE=1 /sys/devices/platform/s3c2440-i2c/i2c-0/0-0073/pcf50633-mbc.0/power_supply/ac/uevent POWER_SUPPLY_NAME=ac POWER_SUPPLY_TYPE=Mains POWER_SUPPLY_ONLINE=0 - Using the methods above, both bind and unbind files exist in the driver directory - shouldn't there be only one at any one time? If not, don't the files only need to be created once instead of repeatedly each time the scripts/aliases are run? Those files are always present in the sysfs, kernel maintains them automatically for every driver. Right (thanks to Neil Jerram for clarification on this as well). - The discharge rate attached for an inactive phone (with a blanked screen) with a new, fully charged battery is not very good (~10 hours) Keep in mind that the SoC was constantly running during that test, so this should be ok. Normal usage assumes you use suspend-to-ram when you do not actually interact with the device, that should give ~70 (without #1024 fix) or ~140 (with it) hours of standby time. At the moment dim is set to 20s, display off to 50s and suspend is off - are you saying that suspend should be set to 120s or something? How does that affect incoming calls? Looking at this I realise that when the device is disconnected all the dimming etc has stopped working even the values are set correctly . . - Should the phone be shut down after the dumb battery is fully charged? No, charging is the same for gta02 battery and the dumb one, it's safe and doesn't require manual intervention. OK, good. Thanks, 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
QtMoko v33 - More battery info and questions
People, Using: echo bq27000-battery.0 /sys/bus/platform/drivers/bq27000-battery/unbind modprobe platform_battery allows me to check the value of: /sys/class/power_supply/battery/capacity and using: rmmod platform_battery echo bq27000-battery.0 /sys/bus/platform/drivers/bq27000-battery/bind restores the smart battery function. I attach a graph of the resulting discharge rate of the fully charged Nokia BL-6C battery. Questions: - Even with the dumb battery configuration, the battery charging animated icon continues after USB (power) disconnection - should that happen? - Using the methods above, both bind and unbind files exist in the driver directory - shouldn't there be only one at any one time? If not, don't the files only need to be created once instead of repeatedly each time the scripts/aliases are run? - The discharge rate attached for an inactive phone (with a blanked screen) with a new, fully charged battery is not very good (~10 hours) - I would need at least 24 hours with light usage to be able to use the Neo as my regular phone. Is this battery performance typical? - Should the phone be shut down after the dumb battery is fully charged? Thanks, Phil. -- Philip Rhoades GPO Box 3411 Sydney NSW 2001 Australia E-mail: p...@pricom.com.au attachment: ChkOMBattery.png___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v33 - More battery info and questions
On 26 March 2011 09:54, Philip Rhoades p...@pricom.com.au wrote: People, Using: echo bq27000-battery.0 /sys/bus/platform/drivers/bq27000-battery/unbind modprobe platform_battery allows me to check the value of: /sys/class/power_supply/battery/capacity and using: rmmod platform_battery echo bq27000-battery.0 /sys/bus/platform/drivers/bq27000-battery/bind restores the smart battery function. I attach a graph of the resulting discharge rate of the fully charged Nokia BL-6C battery. Questions: - Even with the dumb battery configuration, the battery charging animated icon continues after USB (power) disconnection - should that happen? - Using the methods above, both bind and unbind files exist in the driver directory - shouldn't there be only one at any one time? I would guess not, because the .0 at the end of bq27000-battery.0 suggests that there might be multiple battery instances, of which, at a given moment, some might be bound and others not. If not, don't the files only need to be created once instead of repeatedly each time the scripts/aliases are run? Are you thinking that those echo commands create the files? I doubt it works like that; files in /sys and /proc are special, and it's more like echoing something into them causes some action to happen, or some config change. Cf. echo 1 /proc/sys/net/ipv4/ip_forward to enable IP forwarding. Regards, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v33 - More battery info and questions
Hi, Philip Rhoades p...@pricom.com.au writes: - Even with the dumb battery configuration, the battery charging animated icon continues after USB (power) disconnection - should that happen? Provide uevent files contents for both the battery driver and pcf50633-mbc drivers. - Using the methods above, both bind and unbind files exist in the driver directory - shouldn't there be only one at any one time? If not, don't the files only need to be created once instead of repeatedly each time the scripts/aliases are run? Those files are always present in the sysfs, kernel maintains them automatically for every driver. - The discharge rate attached for an inactive phone (with a blanked screen) with a new, fully charged battery is not very good (~10 hours) Keep in mind that the SoC was constantly running during that test, so this should be ok. Normal usage assumes you use suspend-to-ram when you do not actually interact with the device, that should give ~70 (without #1024 fix) or ~140 (with it) hours of standby time. - Should the phone be shut down after the dumb battery is fully charged? No, charging is the same for gta02 battery and the dumb one, it's safe and doesn't require manual intervention. HTH -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v33
* removed package vim-tiny from v33 .tgz, please re-add it as default;) Hmm i am trying to keep the image as small as possible. I'd rather prefer if people could install they favourite apps with apt-get. I agree, but I think vi/vim is quite a basic tool in any distribution. I'd remove nano instead, not so common as vi is. btw, nano is 1786kB, vim-tiny is 1114kB;) +1 :-) Nah, I much prefer zile. Stefan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v33
On Thursday 17 March 2011 05:54:32 Philip Rhoades wrote: * new theme faenqo (cyberspirit) Is this the default? - it looks the same as before - how do I change themes (I couldn't find the info anywhere) - ahh networking problem on my server - fixed now. Settings-Appearence and select more themes from combo. I'd rather stick with the old theme as default because it's well tested, but on the other hand new themes are really nice... ? mplayer installed when I tried to play an audio file but mencoder is not installed . . Mencoder is installed when you select Encode. You can encode videos this way for Neo resolution. Plans for future is FSO framework in qtmoko. What will that provide? Dbus interface for access to telephony and hardware. There was some discussion on the list previously - mostly people are afraid that it will make phone unstable. But i am not going to remove or break old qtopia phone stack. I'd like to do this FSO integration while keeping old current implementation at least until FSO is working perfectly. Maybe it will be available as separate package, and it can be separate application in git. We will see, but don't be afraid - i am not going to break anything. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [qtmoko33] wifi wpa2-psk issue (was: qtmoko v33)
On Tuesday 08 March 2011 22:29:22 Alfa21 wrote: 2011-03-05@17:14 Alfa21 2011-03-05@12:42 Radek Polak * unable to connect wifi wpa2-psk Was is working in some older versions? It can be bug either in wpa_supplicatant or in qmoko wifi plugin that creates configuration for wpa_supplicant. Does it work when you setup wpa_supplicant from command line? I am trying to connect WPA2-psk here and it does not work too :( previously I had v31 and it was ok, but only on the first attempt and then I needed to reboot (rebooted also because wifi didn't stop and battery drain empty in few hours) the blue led in v31 did never turn on while connected. before v31 it was all ok... IIRC hi, I tried to manually configure the wifi link: as you can read below, seems to be something different with the wpa driver in v33... Hmm i just tested wpa2-psk here at work and it works (only the first connect after reboot). But it can be of course different AP. You could try to enable Networking category in Settings-Logging and send me full log. Or you could try to replace wpa_supplicant with package from lenny. But I am not wifi expert so cant promise anything. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v33
Radek, I just did a clean install with v33, restored my symlinks for /root /home/root to dirs on the SD card and everything worked perfectly! Many thanks for your continuing work! See below for comments/questions: On 2011-03-04 17:37, Radek Polak wrote: Hi, i have uploaded new qtmoko v33 images to sourceforge now [1]. They are still called experimental, because a few things are still not perfect. For more information about qtmoko please see [2][3]. Here is list of changes since v32: * new theme faenqo (cyberspirit) Is this the default? - it looks the same as before - how do I change themes (I couldn't find the info anywhere) - ahh networking problem on my server - fixed now. * qtmoko and it's applications are packaged as debian packages * compiled natively on ARM with debian toolchain * new web with applications and themes [4] * applications are now installed from web browser * new icon for installing qtmoko apps in Applications * you can easily install new themes in appearence settings Nice! * fixed usb mass storage script (thanks to Alfa21) * omhacks are installed as debian package from sid * qmplayer installs mencoder in debian ? mplayer installed when I tried to play an audio file but mencoder is not installed . . * mencoder uses ac3 codec for audio * orange led brightness should be fixed (only in sources) * moved all apps from qtmoko-apps git to qtmoko git * updated docs for building and compiling The list is quite short on how much of work it was. Most of the effort was to package everything with debian package system. This should be done now except for kernel which is on the list for next release. For installing qtmoko with apt there is new line now in /etc/apt/sources.list: deb http://qtmoko.sourceforge.net/debian/ / I might try this next time. Applications and themes are right now not in that repo. They can be installed from web browser from url below [4]. Applications are put in categories, they have tags and screenshots for easy searching and navigation. Please let me know if you have ideas or patches for improving this. The application web is generated from .xml files with xsltproc and bash scripts so it should be quite easy to change look or improve it. Btw .deb packages for most of the apps are still building right now so please be patient - i will upload them as soon as the build is finished. Applications in this version can be still installed with old qtopia package system, but i am going to disable this for next release if new packaging will be ok for you. My plan for next version is to fix regression if you find any, package properly also kernel and release it as stable. Plans for future is FSO framework in qtmoko. What will that provide? Don't forget to try new faenqo theme or use older themes (asthromod) which were only in git until now. They are really nice. Thanks for supporting qtmoko Thanks for continuing to support my Neo! 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
Re: qtmoko v33
On Wednesday 09 March 2011 08:50:35 Nashvin Gangaram wrote: Thanks Radek, for all the great work! I have a suggestion, and don't know if it will be a popular one: Can Eyepiece be included in the default base installation? I'd prefer keeping the base image small. It's much easier to install apps then remove them. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [qtmoko33] wifi wpa2-psk issue (was: qtmoko v33)
On Wednesday, March 16, 2011 13:17:56, Radek Polak wrote: On Tuesday 08 March 2011 22:29:22 Alfa21 wrote: 2011-03-05@17:14 Alfa21 2011-03-05@12:42 Radek Polak * unable to connect wifi wpa2-psk Was is working in some older versions? It can be bug either in wpa_supplicatant or in qmoko wifi plugin that creates configuration for wpa_supplicant. Does it work when you setup wpa_supplicant from command line? I am trying to connect WPA2-psk here and it does not work too :( previously I had v31 and it was ok, but only on the first attempt and then I needed to reboot (rebooted also because wifi didn't stop and battery drain empty in few hours) the blue led in v31 did never turn on while connected. before v31 it was all ok... IIRC hi, I tried to manually configure the wifi link: as you can read below, seems to be something different with the wpa driver in v33... Hmm i just tested wpa2-psk here at work and it works (only the first connect after reboot). But it can be of course different AP. You could try to enable Networking category in Settings-Logging and send me full log. Or you could try to replace wpa_supplicant with package from lenny. But I am not wifi expert so cant promise anything. Regards Radek hi radek, i'm sorry for the silence. i found the solution about this topic: 1) qtmoko doesn't kill wpa-supplicant closing wifi the first good time, this is bad! 2) because of previous point i messed too much and missconfigured my ap.. so i tried with wrong settings, ignore me: current supplicant is ok! 3) remains the problem of battery discharge when you disconnect from wifi:maybe interface doesn't go to sleep?btw i can force this by script (wifi off) regards! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [qtmoko33] wifi wpa2-psk issue (was: qtmoko v33)
Alfa21 mobile wrote: hi radek, i'm sorry for the silence. i found the solution about this topic: 1) qtmoko doesn't kill wpa-supplicant closing wifi the first good time, this is bad! I think i can add this to the wifi script, it should be quite easy. 2) because of previous point i messed too much and missconfigured my ap.. so i tried with wrong settings, ignore me: current supplicant is ok! Great! 3) remains the problem of battery discharge when you disconnect from wifi:maybe interface doesn't go to sleep?btw i can force this by script (wifi off) I think we can add this to wifi script as well. I will do it tomorrow at work where i can test it. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [qtmoko33] wifi wpa2-psk issue (was: qtmoko v33)
3) remains the problem of battery discharge when you disconnect from wifi:maybe interface doesn't go to sleep?btw i can force this by script (wifi off) I think we can add this to wifi script as well. I will do it tomorrow at work where i can test it. Regards Radek no, beware! if you turn off wifi in that way, then the line in internet gui tells no wifi interfaces available! it's too low level in that way, imo. i would prefer a way which put the interface in its initial state but keeps it available and not removed. i've to check but maybe killing supplicant is just enough... i'll verify and report you about that. regards ps: now i'm on wifi with qtmoko email client, from a pub's hotspot ;) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [qtmoko33] wifi wpa2-psk issue (was: qtmoko v33)
Hi, I can confirm that there is no problem with wifi wpa-psk/wpa2-psk in aes encryption mode (qtmoko v.33). But there is other annoying thing: fbreader canot be started from QX, if someone knows a solution please tell me or fix it (radek). On Wed, 16 Mar 2011 13:17:56 +0100, Radek Polak wrote: On Tuesday 08 March 2011 22:29:22 Alfa21 wrote: 2011-03-05@17:14 Alfa21 2011-03-05@12:42 Radek Polak * unable to connect wifi wpa2-psk Was is working in some older versions? It can be bug either in wpa_supplicatant or in qmoko wifi plugin that creates configuration for wpa_supplicant. Does it work when you setup wpa_supplicant from command line? I am trying to connect WPA2-psk here and it does not work too :( previously I had v31 and it was ok, but only on the first attempt and then I needed to reboot (rebooted also because wifi didn't stop and battery drain empty in few hours) the blue led in v31 did never turn on while connected. before v31 it was all ok... IIRC hi, I tried to manually configure the wifi link: as you can read below, seems to be something different with the wpa driver in v33... Hmm i just tested wpa2-psk here at work and it works (only the first connect after reboot). But it can be of course different AP. You could try to enable Networking category in Settings-Logging and send me full log. Or you could try to replace wpa_supplicant with package from lenny. But I am not wifi expert so cant promise anything. 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: QtMoko and FSO (was: qtmoko v33)
Hi, I hope there is still some chances that Radek will change his dicision. From my point of view where is no real need in FSO/qt gibrid, because of following reasons: 1. qt stack has richer functionalily, better performance, and less bugs than that FSO dbus/vala thing (don't throw rotten tomatoes to me plese) 2. qt has it's own resource management, FSO - it's own, rewriting qt one to FSO one is worthless effort 3. where logs of significantly more useful, easier and non-destructive goals to rich, i can suggest few: 3.1 switch back to X11. with new graphical subsystem performance this will work great. 3.2 switch to newer qt versions 3.3 fix 100500 bugs left 3.4 add gta04 support- most important 3.5 improve performance and usability 3.6 implement new features, like: 'geek' theme, sliding buttons in answer screen ^^^ IMO this set can keep everyone busy for a while. where is also no real benefit visible from switching to FSO. qtmoko will become more complicated, more buggy, slower, harder to develop:( I afraid i'll have to stay on non-FSO version forether. And certain, this planned change worth more discussion. If someone wants FSO, better to install it on debian or with SHR. Gennady. +1 Absolutely. -- ## giacomo 'giotti' mariani gpg --keyserver pool.sks-keyservers.net --recv-key 0x99bfa859 O ASCII ribbon campaign: stop HTML mail www.asciiribbon.org ## ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko and FSO (was: qtmoko v33)
+1. I've only recently switched from SHR to qtmoko (v31) and I'm impressed with performance and maturity of applications. I really wouldn't like to lose that again. Regards Bernhard Am Donnerstag, den 10.03.2011, 12:00 +0100 schrieb community-requ...@lists.openmoko.org: Von: Gennady Kupava g...@bsdmn.com Reply-to: List for Openmoko community discussion community@lists.openmoko.org An: List for Openmoko community discussion community@lists.openmoko.org Betreff: Re: QtMoko and FSO (was: qtmoko v33) Datum: Wed, 09 Mar 2011 22:48:28 +0300 (2011-03-09 20:48:28) Hi, I hope there is still some chances that Radek will change his dicision. From my point of view where is no real need in FSO/qt gibrid, because of following reasons: 1. qt stack has richer functionalily, better performance, and less bugs than that FSO dbus/vala thing (don't throw rotten tomatoes to me plese) 2. qt has it's own resource management, FSO - it's own, rewriting qt one to FSO one is worthless effort 3. where logs of significantly more useful, easier and non-destructive goals to rich, i can suggest few: 3.1 switch back to X11. with new graphical subsystem performance this will work great. 3.2 switch to newer qt versions 3.3 fix 100500 bugs left 3.4 add gta04 support - most important 3.5 improve performance and usability 3.6 implement new features, like: 'geek' theme, sliding buttons in answer screen ^^^ IMO this set can keep everyone busy for a while. where is also no real benefit visible from switching to FSO. qtmoko will become more complicated, more buggy, slower, harder to develop :( I afraid i'll have to stay on non-FSO version forether. And certain, this planned change worth more discussion. If someone wants FSO, better to install it on debian or with SHR. Gennady. В Втр, 08/03/2011 в 18:00 +0100, Radek Polak пишет: Dmitry Chistikov wrote: I'm afraid it's too early to ask, but could you give an estimate on how much time it'll take to enable the use of FSO framework? Just something like about a year or, say, not less than four months. Writing simple dialer application could be matter of days/hours. Integrating all the functions so that it looks like qtmoko now will be much more difficult (i cant even guess how much). We also need FSO running on debian - i'd prefer current git version. I am not aware if there are debian packages for recent FSO. Anyone knows? 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: QtMoko and FSO (was: qtmoko v33)
Gennady Kupava, Mar. 09, 2011, 22:48 +0300: 1. qt stack has richer functionalily, better performance, and less bugs than that FSO dbus/vala thing (don't throw rotten tomatoes to me plese) 2. qt has it's own resource management, FSO - it's own, rewriting qt one to FSO one is worthless effort OK, I'd like to ask one question now. Is there a reasonable technical way to *control* qt-stack-managed Freerunner without GUI? This means sending SMS from CLI and all these small things. In other words, I'm interested in command-line interface instead of programming interface. I believe the latter is up and running, but is the former implemented? Frankly, I do not know what the answer is. And yes, in case it is like You just invoke this function from this library with proper arguments, I think I'll go and write a simple CLI wrapper, for this is just what makes Unix-like systems so usable. But if the only correct implementation lives deep in the code of qt stack, then we'd better try and separate it. Generally speaking, I guess it's convenient and powerful interfaces, rather than compatibility with existing applications, that matter more just here. -- Dmitry Chistikov ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[qtmoko33] wifi doesn't power off and drains the battery (was: qtmoko v33)
On Sat, Mar 5, 2011 at 5:14 PM, Alfa21 freerun...@my.is.it wrote: previously I had v31 and it was ok, but only on the first attempt and then I needed to reboot (rebooted also because wifi didn't stop and battery drain empty in few hours) quoting myself to report this bug is present in v33 too: if you successfully connect to any wifi network (in v33 only open networs are accessible) then the hardware remains in active state, draining the battery flat in few hours depsite you disable the connection via the software interface. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [qtmoko33] wifi doesn't power off and drains the battery (was: qtmoko v33)
--- On Wed, 3/9/11, Alfa21-mobile freerun...@my.is.it wrote: if you successfully connect to any wifi network (in v33 only open networs are accessible) then the hardware remains in active state, draining the battery flat in few hours depsite you disable the connection via the software interface. Ah, that explains..! I had such an idea, after my battery ran out much faster than I expected. In general, is there a GUI-feedback on the neo-quick-settings (or what is it, top left icon with the cogwheels when using Faenqo?) For now, I put most of them in favourites, so that I will return to home after successfully clicking something. The current status of some of them I have been able to find back in the GUI, so I understand that for now /proc can be consulted for the current status? Boudewijn ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v33
On 03/04/2011 23:17, community-requ...@lists.openmoko.org wrote: Thanks for keeping up the good work Radek. I'm currently running v31. I added the new repository to the sources.list file, did an apt-get update, then apt-get upgrade and this is what I get: Preparing to replace qtmoko 31-13 (using .../archives/qtmoko_33-1_armel.deb) ... Unpacking replacement qtmoko ... dpkg: error processing /var/cache/apt/archives/qtmoko_33-1_armel.deb (--unpack): trying to overwrite `/opt/qtmoko/help/html/packagemanager-view-app.html', which is also in package qtmoko-files dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/qtmoko_33-1_armel.deb E: Sub-process /usr/bin/dpkg returned an error code (1) What should I do to upgrade to the latest? I think you should delete /opt then update-rc.d -f qpe.sh remove apt-get install qtmoko update-rc.d qtmoko defaults However i have not tested this and i dont promise it will work:-) Please note that this is still experimental. Next version will be probably stable. Regards Radek It worked perfectly, thanks! Moreover, the battery duration looks improved: another good news! Cheers Giacomo PS Is it possible to install all the tool-chain (build-dep, libqt4-dev, qtmoko-debian-toolchain-armv4t-eabi.tar.gz, libmpfr1ldbl_XXX_i386.deb and libgmp3c2_XXX_i386.deb) on Lenny, x86_64, as a normal user? -- ## giacomo 'giotti' mariani gpg --keyserver pool.sks-keyservers.net --recv-key 0x99bfa859 O ASCII ribbon campaign: stop HTML mail www.asciiribbon.org ## ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [qtmoko33] wifi doesn't power off and drains the battery (was: qtmoko v33)
yes, I can confirm, with the command: echo s3c2440-sdi /sys/bus/platform/drivers/s3c-sdi/unbind the battery charge is in safe :) tnx! On Wed, Mar 9, 2011 at 2:29 PM, W. B. Kranendonk wankelwan...@yahoo.com wrote: --- On Wed, 3/9/11, Alfa21-mobile freerun...@my.is.it wrote: if you successfully connect to any wifi network (in v33 only open networs are accessible) then the hardware remains in active state, draining the battery flat in few hours depsite you disable the connection via the software interface. Ah, that explains..! I had such an idea, after my battery ran out much faster than I expected. In general, is there a GUI-feedback on the neo-quick-settings (or what is it, top left icon with the cogwheels when using Faenqo?) For now, I put most of them in favourites, so that I will return to home after successfully clicking something. The current status of some of them I have been able to find back in the GUI, so I understand that for now /proc can be consulted for the current status? Boudewijn ___ 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 and FSO (was: qtmoko v33)
Hi, I hope there is still some chances that Radek will change his dicision. From my point of view where is no real need in FSO/qt gibrid, because of following reasons: 1. qt stack has richer functionalily, better performance, and less bugs than that FSO dbus/vala thing (don't throw rotten tomatoes to me plese) 2. qt has it's own resource management, FSO - it's own, rewriting qt one to FSO one is worthless effort 3. where logs of significantly more useful, easier and non-destructive goals to rich, i can suggest few: 3.1 switch back to X11. with new graphical subsystem performance this will work great. 3.2 switch to newer qt versions 3.3 fix 100500 bugs left 3.4 add gta04 support - most important 3.5 improve performance and usability 3.6 implement new features, like: 'geek' theme, sliding buttons in answer screen ^^^ IMO this set can keep everyone busy for a while. where is also no real benefit visible from switching to FSO. qtmoko will become more complicated, more buggy, slower, harder to develop :( I afraid i'll have to stay on non-FSO version forether. And certain, this planned change worth more discussion. If someone wants FSO, better to install it on debian or with SHR. Gennady. В Втр, 08/03/2011 в 18:00 +0100, Radek Polak пишет: Dmitry Chistikov wrote: I'm afraid it's too early to ask, but could you give an estimate on how much time it'll take to enable the use of FSO framework? Just something like about a year or, say, not less than four months. Writing simple dialer application could be matter of days/hours. Integrating all the functions so that it looks like qtmoko now will be much more difficult (i cant even guess how much). We also need FSO running on debian - i'd prefer current git version. I am not aware if there are debian packages for recent FSO. Anyone knows? 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: QtMoko and FSO (was: qtmoko v33)
Agree with Gennady. Look what happened to SHR! It is also necessary to fix rndis usb-host ) On Wed, 09 Mar 2011 22:48:28 +0300, Gennady Kupava wrote: Hi, I hope there is still some chances that Radek will change his dicision. From my point of view where is no real need in FSO/qt gibrid, because of following reasons: 1. qt stack has richer functionalily, better performance, and less bugs than that FSO dbus/vala thing (don't throw rotten tomatoes to me plese) 2. qt has it's own resource management, FSO - it's own, rewriting qt one to FSO one is worthless effort 3. where logs of significantly more useful, easier and non-destructive goals to rich, i can suggest few: 3.1 switch back to X11. with new graphical subsystem performance this will work great. 3.2 switch to newer qt versions 3.3 fix 100500 bugs left 3.4 add gta04 support - most important 3.5 improve performance and usability 3.6 implement new features, like: 'geek' theme, sliding buttons in answer screen ^^^ IMO this set can keep everyone busy for a while. where is also no real benefit visible from switching to FSO. qtmoko will become more complicated, more buggy, slower, harder to develop :( I afraid i'll have to stay on non-FSO version forether. And certain, this planned change worth more discussion. If someone wants FSO, better to install it on debian or with SHR. Gennady. В Втр, 08/03/2011 в 18:00 +0100, Radek Polak пишет: Dmitry Chistikov wrote: I'm afraid it's too early to ask, but could you give an estimate on how much time it'll take to enable the use of FSO framework? Just something like about a year or, say, not less than four months. Writing simple dialer application could be matter of days/hours. Integrating all the functions so that it looks like qtmoko now will be much more difficult (i cant even guess how much). We also need FSO running on debian - i'd prefer current git version. I am not aware if there are debian packages for recent FSO. Anyone knows? 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 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: messages through background [was Re: qtmoko v33]
On Monday 07 March 2011 19:46:01 Alfa21 wrote: again on this topic: I can see painted over the background image ^@ for each time I press the AUX button This is because commented out lines with getty in /dev/inittab. It can be fixed with command: stty -F /dev/tty1 -echo I'll add it to qtmoko init script. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[qtmoko33] usb storage issue and kernel panic (was Re: qtmoko v33)
On Fri, Mar 4, 2011 at 10:16 PM, Alfa21 freerun...@my.is.it wrote:
* fixed usb mass storage script
I like the added logic to use the whole sdcard or a specific partition!
btw why in fstab you consider swap on p4? is there any doc about use of p3 in
qtmoko?
(I usually set uSD's p1 as storage, p2 as rootfs, p3 as swap)
ah, about fs type... do you consider for future releases using btrfs or ext4?
I know they have optimizations for flash memory kind of storage.
hi radek,
I modified the last line in on script like:
#modprobe g_file_storage file=${DEV_NAME} stall=0
modprobe g_file_storage file=${DEV_NAME} stall=0 removable=y
this because otherwise (at least with a specific single partition
scenario) the usb drive is not usable with windows.
with linux and my home tv-set and home theater is always accessible,
with or without the removable=y directive.
this change just add the compatibility with windows OS (tested on winXP).
btw, both now and before, I get kernel panic changing usb mode back
and forth storage/ethernet more than twice... :(
I'm not able to tell more on this issue because on reboot do not see
anything interesting inside logs :S
regards
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [qtmoko33] usb storage issue and kernel panic (was Re: qtmoko v33)
Alfa21-mobile wrote:
hi radek,
I modified the last line in on script like:
#modprobe g_file_storage file=${DEV_NAME} stall=0
modprobe g_file_storage file=${DEV_NAME} stall=0 removable=y
Oki, i have commited this change.
Thanks!
Radek
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
QtMoko and FSO (was: qtmoko v33)
Radek Polak, Mar. 04, 2011, 07:37 +0100: i have uploaded new qtmoko v33 images to sourceforge now [1]. [...] The list is quite short on how much of work it was. Hello, Radek! Thank you for the work you are doing. Most of the effort was to package everything with debian package system. This should be done now except for kernel which is on the list for next release. [...] My plan for next version is to fix regression if you find any, package properly also kernel and release it as stable. Plans for future is FSO framework in qtmoko. I'm afraid it's too early to ask, but could you give an estimate on how much time it'll take to enable the use of FSO framework? Just something like about a year or, say, not less than four months. Thanks once more. -- Dmitry Chistikov ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko and FSO (was: qtmoko v33)
Dmitry Chistikov wrote: I'm afraid it's too early to ask, but could you give an estimate on how much time it'll take to enable the use of FSO framework? Just something like about a year or, say, not less than four months. Writing simple dialer application could be matter of days/hours. Integrating all the functions so that it looks like qtmoko now will be much more difficult (i cant even guess how much). We also need FSO running on debian - i'd prefer current git version. I am not aware if there are debian packages for recent FSO. Anyone knows? Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[qtmoko33 regression] segfaults moving items in star menu (was: qtmoko v33)
2011-03-05@17:14 Alfa21 * got some segfaults changing the theme and then opening the dialer IIRC it crashed here to, but after restart it was ok. yeah, the same here... it's not a show stopper bug. another segfault always reproducible and no workaround available AFAIK to sort items in preferred menu: - long pres aux button - in starred tab, long press on the item you want to move up/down - select in contextual menu move - select its final position in the list = segmentation fault, qpe restarts, items keeps old positions this was ok in the previous qtmoko release I had (v31) -- 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: [qtmoko33 regression] segfaults moving items in star menu (was: qtmoko v33)
segfault in qtmoko v32 too On Tue, 8 Mar 2011 19:39:36 +0100, Alfa21 freerun...@my.is.it wrote: 2011-03-05@17:14 Alfa21 * got some segfaults changing the theme and then opening the dialer IIRC it crashed here to, but after restart it was ok. yeah, the same here... it's not a show stopper bug. another segfault always reproducible and no workaround available AFAIK to sort items in preferred menu: - long pres aux button - in starred tab, long press on the item you want to move up/down - select in contextual menu move - select its final position in the list = segmentation fault, qpe restarts, items keeps old positions this was ok in the previous qtmoko release I had (v31) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[qtmoko33] wifi wpa2-psk issue (was: qtmoko v33)
2011-03-05@17:14 Alfa21 2011-03-05@12:42 Radek Polak * unable to connect wifi wpa2-psk Was is working in some older versions? It can be bug either in wpa_supplicatant or in qmoko wifi plugin that creates configuration for wpa_supplicant. Does it work when you setup wpa_supplicant from command line? I am trying to connect WPA2-psk here and it does not work too :( previously I had v31 and it was ok, but only on the first attempt and then I needed to reboot (rebooted also because wifi didn't stop and battery drain empty in few hours) the blue led in v31 did never turn on while connected. before v31 it was all ok... IIRC hi, I tried to manually configure the wifi link: as you can read below, seems to be something different with the wpa driver in v33... Initializing interface 'eth0' conf '/etc/wpa_supplicant/test.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A' Configuration file '/etc/wpa_supplicant/test.conf' - '/etc/wpa_supplicant/test.conf' Reading configuration file '/etc/wpa_supplicant/test.conf' ctrl_interface='/var/lib/wpa_supplicant' ctrl_interface_group='0' eapol_version=1 fast_reauth=1 ap_scan=1 Priority group 0 id=0 ssid='A21_net' Initializing interface (2) 'eth0' Interface eth0 set UP - waiting a second for the driver to complete initialization SIOCGIWRANGE: WE(compiled)=22 WE(source)=13 enc_capa=0x0 capabilities: key_mgmt 0x0 enc 0x3 flags 0x0 ioctl[SIOCSIWESSID]: Invalid argument WEXT: Operstate: linkmode=1, operstate=5 Own MAC address: 00:XX:XX:XX:XX:XX wpa_driver_wext_set_wpa wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0 ioctl[SIOCSIWENCODEEXT]: Operation not supported Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0 ioctl[SIOCSIWENCODEEXT]: Operation not supported Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0 ioctl[SIOCSIWENCODEEXT]: Operation not supported Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0 ioctl[SIOCSIWENCODEEXT]: Operation not supported Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE wpa_driver_wext_set_countermeasures wpa_driver_wext_set_drop_unencrypted RSN: flushing PMKID list in the driver Setting scan request: 0 sec 10 usec -- 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: qtmoko v33
Thanks Radek, for all the great work! I have a suggestion, and don't know if it will be a popular one: Can Eyepiece be included in the default base installation? -Nashvin On Fri, Mar 4, 2011 at 8:37 AM, Radek Polak pson...@seznam.cz wrote: Hi, i have uploaded new qtmoko v33 images to sourceforge now [1]. They are still called experimental, because a few things are still not perfect. For more information about qtmoko please see [2][3]. Here is list of changes since v32: * new theme faenqo (cyberspirit) * qtmoko and it's applications are packaged as debian packages * compiled natively on ARM with debian toolchain * new web with applications and themes [4] * applications are now installed from web browser * new icon for installing qtmoko apps in Applications * you can easily install new themes in appearence settings * fixed usb mass storage script (thanks to Alfa21) * omhacks are installed as debian package from sid * qmplayer installs mencoder in debian * mencoder uses ac3 codec for audio * orange led brightness should be fixed (only in sources) * moved all apps from qtmoko-apps git to qtmoko git * updated docs for building and compiling The list is quite short on how much of work it was. Most of the effort was to package everything with debian package system. This should be done now except for kernel which is on the list for next release. For installing qtmoko with apt there is new line now in /etc/apt/sources.list: deb http://qtmoko.sourceforge.net/debian/ / Applications and themes are right now not in that repo. They can be installed from web browser from url below [4]. Applications are put in categories, they have tags and screenshots for easy searching and navigation. Please let me know if you have ideas or patches for improving this. The application web is generated from .xml files with xsltproc and bash scripts so it should be quite easy to change look or improve it. Btw .deb packages for most of the apps are still building right now so please be patient - i will upload them as soon as the build is finished. Applications in this version can be still installed with old qtopia package system, but i am going to disable this for next release if new packaging will be ok for you. My plan for next version is to fix regression if you find any, package properly also kernel and release it as stable. Plans for future is FSO framework in qtmoko. Don't forget to try new faenqo theme or use older themes (asthromod) which were only in git until now. They are really nice. Thanks for supporting qtmoko Regards Radek [1] http://sourceforge.net/projects/qtmoko/files/Experimental/ [2] http://qtmoko.org/ [3] http://qtmoko.sourceforge.net/ [4] http://qtmoko.sourceforge.net/apps/ [5] https://github.com/radekp/qtmoko/tree/master/web/qtmoko-apps ___ 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 v33
On 03/05/2011 18:20, community-requ...@lists.openmoko.org wrote: * removed package vim-tiny from v33 .tgz, please re-add it as default;) Hmm i am trying to keep the image as small as possible. I'd rather prefer if people could install they favourite apps with apt-get. I agree, but I think vi/vim is quite a basic tool in any distribution. I'd remove nano instead, not so common as vi is. btw, nano is 1786kB, vim-tiny is 1114kB;) +1 :-) -- ## giacomo 'giotti' mariani gpg --keyserver pool.sks-keyservers.net --recv-key 0x99bfa859 O ASCII ribbon campaign: stop HTML mail www.asciiribbon.org ## ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v33
On Mon, 07 Mar 2011 11:01:20 +0100, giacomo 'giotti' mariani wrote On 03/05/2011 18:20, community-requ...@lists.openmoko.org wrote: * removed package vim-tiny from v33 .tgz, please re-add it as default;) Hmm i am trying to keep the image as small as possible. I'd rather prefer if people could install they favourite apps with apt-get. I agree, but I think vi/vim is quite a basic tool in any distribution. I'd remove nano instead, not so common as vi is. btw, nano is 1786kB, vim-tiny is 1114kB;) +1 :-) +1 for vim-tiny, but being honest, there's also nano-tiny package which is the sized-winner here :) neo:~# apt-cache show vim-tiny nano-tiny |grep ^Installed Installed-Size: 724 Installed-Size: 168 Regards, -- Tiago Bortoletto Vaz http://tiagovaz.org 0xA504FECA - http://pgp.mit.edu ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v33
Den 07-03-2011 11:01, giacomo 'giotti' mariani skrev: On 03/05/2011 18:20, community-requ...@lists.openmoko.org wrote: * removed package vim-tiny from v33 .tgz, please re-add it as default;) Hmm i am trying to keep the image as small as possible. I'd rather prefer if people could install they favourite apps with apt-get. I agree, but I think vi/vim is quite a basic tool in any distribution. I'd remove nano instead, not so common as vi is. btw, nano is 1786kB, vim-tiny is 1114kB;) +1 :-) I always go for mc and purge whatever text editor that is installed as default but maybe we each have different needs!! :-) -- Ole @ Carlsen-web.dk ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
messages through background [was Re: qtmoko v33]
2011-03-05@17:14 Alfa21 * visible kernel messages through the graphic desktop of qtmoko Kernel should not print anything except serious errors. That should be fixed in kernel instead. Do you know which message did you see? it's the console output, not only kernel messages, sorry. in v31 for example I was able to see messages about wifi connection/dhcp again on this topic: I can see painted over the background image ^@ for each time I press the AUX button -- 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: qtmoko v33
Alfa21 wrote: col! this is the killer point of the new release! ^_^ I suggest you to add a default bookmark in arora browser (maybe instead of reddit!) Nice idea, done: https://github.com/radekp/arora- neo/commit/fc5bd2e36841d61ec6074ea8895994a22be58761 * unable to connect wifi wpa2-psk Was is working in some older versions? It can be bug either in wpa_supplicatant or in qmoko wifi plugin that creates configuration for wpa_supplicant. Does it work when you setup wpa_supplicant from command line? I am trying to connect WPA2-psk here and it does not work too :( * got some segfaults changing the theme and then opening the dialer IIRC it crashed here to, but after restart it was ok. * removed package vim-tiny from v33 .tgz, please re-add it as default ;) Hmm i am trying to keep the image as small as possible. I'd rather prefer if people could install they favourite apps with apt-get. * visible kernel messages through the graphic desktop of qtmoko Kernel should not print anything except serious errors. That should be fixed in kernel instead. Do you know which message did you see? * orange (charge) led is dark, but I like it more :) Should be fixed in sources, but i didnt want to recompile just because of this, so it should be ok for next release. btw why in fstab you consider swap on p4? is there any doc about use of p3 in qtmoko? (I usually set uSD's p1 as storage, p2 as rootfs, p3 as swap) I used to partition my SD card like: p1 for vfat p2 for qtmoko p3 for android/SHR p4 for swap I dont know if it's good idea to change this scheme. You can always make p3 and p4 partitions to match this scheme. ah, about fs type... do you consider for future releases using btrfs or ext4? I know they have optimizations for flash memory kind of storage. IIRC you can use ext4 - it's compiled in kernel. Btrfs could be nice, but i dont know if it makes sence now - e.g. if it performs good on FR. Unless someone benchmarks it and proves that it works good on FR i'd like to keep support only for ext2/ext3/ext4. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v33
2011-03-04@23:50 Gennady Kupava В Птн, 04/03/2011 в 22:16 +0100, Alfa21 пишет: * new theme faenqo (cyberspirit) nice, but how to lock the screen? :P in pull-up menu on main screen, first item is screen lock Gennady doh! thanks a lot ^^' i like it :D -- 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: qtmoko v33
2011-03-05@12:42 Radek Polak * unable to connect wifi wpa2-psk Was is working in some older versions? It can be bug either in wpa_supplicatant or in qmoko wifi plugin that creates configuration for wpa_supplicant. Does it work when you setup wpa_supplicant from command line? I am trying to connect WPA2-psk here and it does not work too :( previously I had v31 and it was ok, but only on the first attempt and then I needed to reboot (rebooted also because wifi didn't stop and battery drain empty in few hours) the blue led in v31 did never turn on while connected. before v31 it was all ok... IIRC * got some segfaults changing the theme and then opening the dialer IIRC it crashed here to, but after restart it was ok. yeah, the same here... it's not a show stopper bug. * removed package vim-tiny from v33 .tgz, please re-add it as default ;) Hmm i am trying to keep the image as small as possible. I'd rather prefer if people could install they favourite apps with apt-get. I agree, but I think vi/vim is quite a basic tool in any distribution. I'd remove nano instead, not so common as vi is. btw, nano is 1786kB, vim-tiny is 1114kB ;) * visible kernel messages through the graphic desktop of qtmoko Kernel should not print anything except serious errors. That should be fixed in kernel instead. Do you know which message did you see? it's the console output, not only kernel messages, sorry. in v31 for example I was able to see messages about wifi connection/dhcp btw why in fstab you consider swap on p4? is there any doc about use of p3 in qtmoko? (I usually set uSD's p1 as storage, p2 as rootfs, p3 as swap) I used to partition my SD card like: p1 for vfat p2 for qtmoko p3 for android/SHR p4 for swap I dont know if it's good idea to change this scheme. You can always make p3 and p4 partitions to match this scheme. ok, no problem for me as I can edit fstab... but at logic level I think p3 for android/shr is not strictly necessary for qtmoko and in general for a clean qtmoko phone ;) ah, about fs type... do you consider for future releases using btrfs or ext4? I know they have optimizations for flash memory kind of storage. IIRC you can use ext4 - it's compiled in kernel. Btrfs could be nice, but i dont know if it makes sence now - e.g. if it performs good on FR. Unless someone benchmarks it and proves that it works good on FR i'd like to keep support only for ext2/ext3/ext4. tried ext4 without success... I think it's just qi(v33) problem, maybe it lacks ext4 support. kind regards, a. -- 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: qtmoko v33
What to say... (harder) better faster stronger! :D Radek Polak wrote: * qtmoko and it's applications are packaged as debian packages * new web with applications and themes * applications are now installed from web browser whoa! you're great! Joif -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/qtmoko-v33-tp6087460p6092149.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: qtmoko v33
* qtmoko and it's applications are packaged as debian packages Yay! Thanks for the rest as well, but this is the big one for me. Stefan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v33
Dnia 2011-03-04, pią o godzinie 07:37 +0100, Radek Polak pisze: Hi, i have uploaded new qtmoko v33 images to sourceforge now [1]. They are still called experimental, because a few things are still not perfect. Thanks for you commitment Radek! -- Patryk LeadMan Benderz Linux Registered User #377521 () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v33
Thanks for keeping up the good work Radek. I'm currently running v31. I added the new repository to the sources.list file, did an apt-get update, then apt-get upgrade and this is what I get: Preparing to replace qtmoko 31-13 (using .../archives/qtmoko_33-1_armel.deb) ... Unpacking replacement qtmoko ... dpkg: error processing /var/cache/apt/archives/qtmoko_33-1_armel.deb (--unpack): trying to overwrite `/opt/qtmoko/help/html/packagemanager-view-app.html', which is also in package qtmoko-files dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/qtmoko_33-1_armel.deb E: Sub-process /usr/bin/dpkg returned an error code (1) What should I do to upgrade to the latest? Bernie -- Forwarded message -- From: Radek Polak pson...@seznam.cz To: List for Openmoko community discussion community@lists.openmoko.org Date: Fri, 4 Mar 2011 07:37:04 +0100 Subject: qtmoko v33 Hi, i have uploaded new qtmoko v33 images to sourceforge now [1]. They are still called experimental, because a few things are still not perfect. For more information about qtmoko please see [2][3]. Here is list of changes since v32: * new theme faenqo (cyberspirit) * qtmoko and it's applications are packaged as debian packages * compiled natively on ARM with debian toolchain * new web with applications and themes [4] * applications are now installed from web browser * new icon for installing qtmoko apps in Applications * you can easily install new themes in appearence settings * fixed usb mass storage script (thanks to Alfa21) * omhacks are installed as debian package from sid * qmplayer installs mencoder in debian * mencoder uses ac3 codec for audio * orange led brightness should be fixed (only in sources) * moved all apps from qtmoko-apps git to qtmoko git * updated docs for building and compiling The list is quite short on how much of work it was. Most of the effort was to package everything with debian package system. This should be done now except for kernel which is on the list for next release. For installing qtmoko with apt there is new line now in /etc/apt/sources.list: deb http://qtmoko.sourceforge.net/debian/ / Applications and themes are right now not in that repo. They can be installed from web browser from url below [4]. Applications are put in categories, they have tags and screenshots for easy searching and navigation. Please let me know if you have ideas or patches for improving this. The application web is generated from .xml files with xsltproc and bash scripts so it should be quite easy to change look or improve it. Btw .deb packages for most of the apps are still building right now so please be patient - i will upload them as soon as the build is finished. Applications in this version can be still installed with old qtopia package system, but i am going to disable this for next release if new packaging will be ok for you. My plan for next version is to fix regression if you find any, package properly also kernel and release it as stable. Plans for future is FSO framework in qtmoko. Don't forget to try new faenqo theme or use older themes (asthromod) which were only in git until now. They are really nice. Thanks for supporting qtmoko Regards Radek [1] http://sourceforge.net/projects/qtmoko/files/Experimental/ [2] http://qtmoko.org/ [3] http://qtmoko.sourceforge.net/ [4] http://qtmoko.sourceforge.net/apps/ [5] https://github.com/radekp/qtmoko/tree/master/web/qtmoko-apps ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v33
On Friday 04 March 2011 11:47:33 giacomo 'giotti' mariani wrote: Do you mean that I can update from QtMoko v32 with a single apt-get update apt-get upgrade? That should be the target goal. Properly packaged kernel is now missing but otherwise it should be possible. Isn't it possible to have them in a repo and install them with apt? I think it should be possible i'll test it. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v33
On Friday 04 March 2011 12:04:56 Bernard Schelberg wrote: Thanks for keeping up the good work Radek. I'm currently running v31. I added the new repository to the sources.list file, did an apt-get update, then apt-get upgrade and this is what I get: Preparing to replace qtmoko 31-13 (using .../archives/qtmoko_33-1_armel.deb) ... Unpacking replacement qtmoko ... dpkg: error processing /var/cache/apt/archives/qtmoko_33-1_armel.deb (--unpack): trying to overwrite `/opt/qtmoko/help/html/packagemanager-view-app.html', which is also in package qtmoko-files dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/qtmoko_33-1_armel.deb E: Sub-process /usr/bin/dpkg returned an error code (1) What should I do to upgrade to the latest? I think you should delete /opt then update-rc.d -f qpe.sh remove apt-get install qtmoko update-rc.d qtmoko defaults However i have not tested this and i dont promise it will work :-) Please note that this is still experimental. Next version will be probably stable. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v33
Great job! FYI: I've just installed Qt Creator and set up git and stuff so be ready for stupid questions :-) I'm going to write simple app to monitor battery (set charging current, check battery state etc.). Hrabosh Radek Polak píše v Pá 04. 03. 2011 v 07:37 +0100: Hi, i have uploaded new qtmoko v33 images to sourceforge now [1]. They are still called experimental, because a few things are still not perfect. For more information about qtmoko please see [2][3]. Here is list of changes since v32: * new theme faenqo (cyberspirit) * qtmoko and it's applications are packaged as debian packages * compiled natively on ARM with debian toolchain * new web with applications and themes [4] * applications are now installed from web browser * new icon for installing qtmoko apps in Applications * you can easily install new themes in appearence settings * fixed usb mass storage script (thanks to Alfa21) * omhacks are installed as debian package from sid * qmplayer installs mencoder in debian * mencoder uses ac3 codec for audio * orange led brightness should be fixed (only in sources) * moved all apps from qtmoko-apps git to qtmoko git * updated docs for building and compiling The list is quite short on how much of work it was. Most of the effort was to package everything with debian package system. This should be done now except for kernel which is on the list for next release. For installing qtmoko with apt there is new line now in /etc/apt/sources.list: deb http://qtmoko.sourceforge.net/debian/ / Applications and themes are right now not in that repo. They can be installed from web browser from url below [4]. Applications are put in categories, they have tags and screenshots for easy searching and navigation. Please let me know if you have ideas or patches for improving this. The application web is generated from .xml files with xsltproc and bash scripts so it should be quite easy to change look or improve it. Btw .deb packages for most of the apps are still building right now so please be patient - i will upload them as soon as the build is finished. Applications in this version can be still installed with old qtopia package system, but i am going to disable this for next release if new packaging will be ok for you. My plan for next version is to fix regression if you find any, package properly also kernel and release it as stable. Plans for future is FSO framework in qtmoko. Don't forget to try new faenqo theme or use older themes (asthromod) which were only in git until now. They are really nice. Thanks for supporting qtmoko Regards Radek [1] http://sourceforge.net/projects/qtmoko/files/Experimental/ [2] http://qtmoko.org/ [3] http://qtmoko.sourceforge.net/ [4] http://qtmoko.sourceforge.net/apps/ [5] https://github.com/radekp/qtmoko/tree/master/web/qtmoko-apps ___ 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 v33
Here is list of changes since v32: any difference since the previous exp. release of qi? I can see a v33 now... * new web with applications and themes [4] col! this is the killer point of the new release! ^_^ I suggest you to add a default bookmark in arora browser (maybe instead of reddit!) My plan for next version is to fix regression if you find any * unable to connect wifi wpa2-psk * got some segfaults changing the theme and then opening the dialer * removed package vim-tiny from v33 .tgz, please re-add it as default ;) * visible kernel messages through the graphic desktop of qtmoko * orange (charge) led is dark, but I like it more :) * new theme faenqo (cyberspirit) nice, but how to lock the screen? :P * fixed usb mass storage script I like the added logic to use the whole sdcard or a specific partition! btw why in fstab you consider swap on p4? is there any doc about use of p3 in qtmoko? (I usually set uSD's p1 as storage, p2 as rootfs, p3 as swap) ah, about fs type... do you consider for future releases using btrfs or ext4? I know they have optimizations for flash memory kind of storage. -- 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: qtmoko v33
В Птн, 04/03/2011 в 22:16 +0100, Alfa21 пишет: * new theme faenqo (cyberspirit) nice, but how to lock the screen? :P in pull-up menu on main screen, first item is screen lock Gennady ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
qtmoko v33
Hi, i have uploaded new qtmoko v33 images to sourceforge now [1]. They are still called experimental, because a few things are still not perfect. For more information about qtmoko please see [2][3]. Here is list of changes since v32: * new theme faenqo (cyberspirit) * qtmoko and it's applications are packaged as debian packages * compiled natively on ARM with debian toolchain * new web with applications and themes [4] * applications are now installed from web browser * new icon for installing qtmoko apps in Applications * you can easily install new themes in appearence settings * fixed usb mass storage script (thanks to Alfa21) * omhacks are installed as debian package from sid * qmplayer installs mencoder in debian * mencoder uses ac3 codec for audio * orange led brightness should be fixed (only in sources) * moved all apps from qtmoko-apps git to qtmoko git * updated docs for building and compiling The list is quite short on how much of work it was. Most of the effort was to package everything with debian package system. This should be done now except for kernel which is on the list for next release. For installing qtmoko with apt there is new line now in /etc/apt/sources.list: deb http://qtmoko.sourceforge.net/debian/ / Applications and themes are right now not in that repo. They can be installed from web browser from url below [4]. Applications are put in categories, they have tags and screenshots for easy searching and navigation. Please let me know if you have ideas or patches for improving this. The application web is generated from .xml files with xsltproc and bash scripts so it should be quite easy to change look or improve it. Btw .deb packages for most of the apps are still building right now so please be patient - i will upload them as soon as the build is finished. Applications in this version can be still installed with old qtopia package system, but i am going to disable this for next release if new packaging will be ok for you. My plan for next version is to fix regression if you find any, package properly also kernel and release it as stable. Plans for future is FSO framework in qtmoko. Don't forget to try new faenqo theme or use older themes (asthromod) which were only in git until now. They are really nice. Thanks for supporting qtmoko Regards Radek [1] http://sourceforge.net/projects/qtmoko/files/Experimental/ [2] http://qtmoko.org/ [3] http://qtmoko.sourceforge.net/ [4] http://qtmoko.sourceforge.net/apps/ [5] https://github.com/radekp/qtmoko/tree/master/web/qtmoko-apps ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
