Re: qtmoko v21
Radek Polak writes: > alsactl -f /usr/share/openmoko/scenarios/gsmhandset.state store > > This if far from comfortable... Modifying files in /usr is surely a really bad idea? Make it symlink to /etc at least. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v21
On Thursday 22 April 2010 14:10:40 Russell Hay wrote: > Doesn't qalsamixer provide this? You can use it to set volume up/down, but it cannot store alsa state file. You would have to run qalsamixer, make call, tweak volumes, save the state from command line with alsactl -f /usr/share/openmoko/scenarios/gsmhandset.state store This if far from comfortable... Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v21
Doesn't qalsamixer provide this? Russ On 22 April 2010 12:44, Radek Polak wrote: > On Thursday 22 April 2010 11:57:56 Korosu Itai wrote: > > > Suspend seems to work properly to me. I haven't tried sms yet, but I've > > tried some calls and the problem is the audio volume. I can hear the > other > > phone (low, but I can hear it) but the other person (the one not using > the > > neo) almost can't hear me. Is there anyway to change volume in calls? > > Right now only by replacing alsa state files in > /usr/share/openmoko/scenarios. > If your phone has buzz-fix applied this is normal and you should find > somewhere > on mailing list or on wiki more loud states. > > I am working on GUI program for changing alsa states, but it will take some > time. > > 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 v21
On Thu, 2010-04-22 at 11:57 +0200, Korosu Itai wrote: ... > , but I've tried some calls and the problem is the audio volume. I can > hear the other phone (low, but I can hear it) but the other person > (the one not using the neo) almost can't hear me. Is there anyway to > change volume in calls? http://wiki.openmoko.org/wiki/Neo_Freerunner_audio_subsystem#Empirical_Data_for_Mic_Settings should help. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v21
On Thursday 22 April 2010 11:57:56 Korosu Itai wrote: > Suspend seems to work properly to me. I haven't tried sms yet, but I've > tried some calls and the problem is the audio volume. I can hear the other > phone (low, but I can hear it) but the other person (the one not using the > neo) almost can't hear me. Is there anyway to change volume in calls? Right now only by replacing alsa state files in /usr/share/openmoko/scenarios. If your phone has buzz-fix applied this is normal and you should find somewhere on mailing list or on wiki more loud states. I am working on GUI program for changing alsa states, but it will take some time. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v21
On Thursday 22 April 2010 13:07:21 Shashank Bharadwaj wrote: > When I try to resume, (sometimes) the display is shown properly, but > the touch screen is still turned-off I guess. I can see everything on > the phone, if I get calls, I can see them, but can't answer. Even the > hardware keys work fine (the AUX button brings up the Task Manager) > but I can't touch anything. I have this problem sometimes too. It sometimes help to suspend/resume until it starts working. I think it's this bug: http://docs.openmoko.org/trac/ticket/2328 As pointed out by Timo Jyrinki, we might need some sleep after touchscreen if powered up. Any kernel dev knows what to try? Regards Rdadek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v21
Shashank Bharadwaj writes: > When I try to resume, (sometimes) the display is shown properly, but > the touch screen is still turned-off I guess. I can see everything on > the phone, if I get calls, I can see them, but can't answer. Even the > hardware keys work fine (the AUX button brings up the Task Manager) > but I can't touch anything. Does hexdump /dev/input/event1 work? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v21
Hi, On Thu, Apr 22, 2010 at 2:33 PM, Joif wrote: > Also, it happend two times that after a suspend the moko didn't recover, I > had to remove the battery. Even I have faced this issue. Actually 2 times just today. Over the week it has happened quite a few times. The only pattern that I can see if this issue is more prominent if I manually suspend the phone. (i.e. short-press the power button). A bit of detail on my issue: When I try to resume, (sometimes) the display is shown properly, but the touch screen is still turned-off I guess. I can see everything on the phone, if I get calls, I can see them, but can't answer. Even the hardware keys work fine (the AUX button brings up the Task Manager) but I can't touch anything. -- Regards Shashank As our circle of knowledge expands, so does the circumference of darkness surrounding it - Albert Einstein ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v21
Joif writes: > Also, it happend two times that after a suspend the moko didn't recover, I > had to remove the battery. Do you remember the exact time and date when this happened? Here my phone fails to wake up from suspend about every two months: http://docs.openmoko.org/trac/ticket/2309 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v21
Hi! I have installed qtmoko 21 recently and it works mostly fine. Suspend seems to work properly to me. I haven't tried sms yet, but I've tried some calls and the problem is the audio volume. I can hear the other phone (low, but I can hear it) but the other person (the one not using the neo) almost can't hear me. Is there anyway to change volume in calls? http://www.mensab.com On Thu, Apr 22, 2010 at 11:27 AM, Radek Polak wrote: > On Thursday 22 April 2010 11:03:59 Joif wrote: > > > Hi! this is just a feedback. > > Thanks for it :) > > > I tried to send a long sms (3 pages) without succes receiving the usual > > error message about sending sms. The receiver received only a part of the > > sms. > > I think i saw the same error. I can try to take a look. > > > Also, it happend two times that after a suspend the moko didn't recover, > I > > had to remove the battery. > > Hmms hard to say what could go wrong. Most probably kernel which is quite > hard > to debug for me... > > 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 v21
On Thursday 22 April 2010 11:03:59 Joif wrote: > Hi! this is just a feedback. Thanks for it :) > I tried to send a long sms (3 pages) without succes receiving the usual > error message about sending sms. The receiver received only a part of the > sms. I think i saw the same error. I can try to take a look. > Also, it happend two times that after a suspend the moko didn't recover, I > had to remove the battery. Hmms hard to say what could go wrong. Most probably kernel which is quite hard to debug for me... Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v21
Hi! this is just a feedback. I'm using qtmoko v21 on gta02 v7 with an italian vodafone sim. I tried to send a long sms (3 pages) without succes receiving the usual error message about sending sms. The receiver received only a part of the sms. Instead receiving long sms seems to work well, I received a 4 pages long sms without problem. Also, it happend two times that after a suspend the moko didn't recover, I had to remove the battery. Regards Joif -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/qtmoko-v21-tp4879432p4941691.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 v21
On 14 April 2010 08:33, ghislain wrote: > > Radek, > I found that the problems with getting a network connection got worse since > you moved the initialisation from the init-scripts to the code. When I > revert that patch the initialisation goes fine (because of the sleep 2 sec > in the script? or maybe just the moment of init?) > > BTW, I have an installer-image on for the V21 [1] > > [1] http://www.openmobile.nl/pages/downloads.php#qtm21 > > Regards, > Ghislain > BaseTrend - openmobile.nl > -- > View this message in context: > http://n2.nabble.com/qtmoko-v21-tp4879432p4900257.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 > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v21
Radek, I found that the problems with getting a network connection got worse since you moved the initialisation from the init-scripts to the code. When I revert that patch the initialisation goes fine (because of the sleep 2 sec in the script? or maybe just the moment of init?) BTW, I have an installer-image on for the V21 [1] [1] http://www.openmobile.nl/pages/downloads.php#qtm21 Regards, Ghislain BaseTrend - openmobile.nl -- View this message in context: http://n2.nabble.com/qtmoko-v21-tp4879432p4900257.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 v21
On 14 April 2010 10:07, Radek Polak wrote: > Yesterday i was working on qtmoko and was doing restarts very often. First > attempt was always "No network", second was usually ok, sometimes i needed 3rd > attempt. > For me it said "No network" every time. I tried restarting about 10 times. Then I flashed v20 - this one always registers to the GSM succesfully. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v21
On Wednesday 14 April 2010 07:14:35 Shashank Bharadwaj wrote: > The first few boots were no problem, today I rebooted my phone again, > but was not able to get the GSM to register. Previously the > registration happened with one or two QtExtended restarts. I have > tried more than 10 times now without any luck :( > Any ideas where to start looking? Yesterday i was working on qtmoko and was doing restarts very often. First attempt was always "No network", second was usually ok, sometimes i needed 3rd attempt. I wonder if this is some timing issue or if it's also related e.g. to GSM signal strength. It could be timing, because when i build qtmoko without voip (which slightly changes timing) i think the registration was more successful. I could upload somewhere version without voip if you would like to try. Otherwise there can be something in the log if you enable the correct category. Or you can disable multiplexing and it should be working 100%, You can do it by editing /opt/qtmoko/etc/default/Trolltech/Modem.conf and setting Multiplexing to no Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v21
On Sat, Apr 10, 2010 at 2:01 AM, Radek Polak wrote: > Hi, > today we have also new stable qtmoko images still based on andy-tracking > 2.6.29 kernel. It can be dowloaded from usual location [1]. Hi, Thank you so much for this release. I tested SMS a couple of times and was able to receive all of them! Thanks! My notes: * Tried the GoogleContactSync from the feeds and it works great. * Wifi - was able to connect to my Wifi router and browse using arora browser * Call volume is OK for me. >> forgot this one: > > Also forgot important note - if the GSM does not register (you will be in the > screen with big dialer keyboard), use POWER button to "Restart QtExtended" > until registration is sucessful. > > This happens only with 2.6.29 kernel, no idea yet why. The first few boots were no problem, today I rebooted my phone again, but was not able to get the GSM to register. Previously the registration happened with one or two QtExtended restarts. I have tried more than 10 times now without any luck :( Any ideas where to start looking? -- Regards Shashank ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [qtmoko] regression in power management (was: qtmoko v21)
Alfa21 wrote: > fine, > I've opened a ticket on mantis about this: > http://bugs.qtmoko.org/view.php?id=128 No one has patch now? If no i will take a look but i need some time (maybe little break). In meanwhile there is IMO new feature in my git that can be used as workaround. I have added power management options when screen is locked. I use it that i disable suspend for battery and power supply and set 20s interval for suspend when screen is locked. You will be no longer bothered with dimming screen and unwanted suspends. When you want no longer work with Neo, just hit the lock button and it will suspend after 20s. http://scap.linuxtogo.org/files/39cca6cdb72559ae241e7c0783ebc80d.png Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v21
Alfa21 wrote: > is possible to switch back and forth v20/v21? > what I've to do? ...or maybe stable/testing are too different? > regards and tnx :) Yes, only differences are kernel /opt and mplayer configuration (2.6.32 uses fbdev, 2.6.29 glamo). Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v21
> If you have v19 installed, you can try to upgrade without reflashing. > Following > proccess is not tested but should work: Hmmm, the problem with qtmoko is that it works so great that you do not have to reinstall it very often. So I forgot which version I have installed. Is there an info screen somewhere where I can see the installed version number ? System info says I have Qt Extended version 4.4.3 built on 4 fev 2010. Is it v19 ? :-) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [qtmoko] regression in power management (was: qtmoko v21)
fine, I've opened a ticket on mantis about this: http://bugs.qtmoko.org/view.php?id=128 -- 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] regression in power management (was: qtmoko v21)
I can confirm that this happens. I have a freshly installed qtmoko Regards. Rune fr. den 09.04.2010 klokka 22:04 (-0700) skreiv Rafael Ignacio Zurita: > Hello, > > --- On Fri, 4/9/10, Alfa21 wrote: > > > > > I hope there are no regressions from previous version. If yes, please let > > > me > > > know i will try to fix them for next release. > > > > found a regression: > > in v21 if you boot on battery and then attach usb, the > > power profile is still on battery. > > > > eg, if you have enabled suspend: > > - ssh connection will be paused because of std-by > > - recharge will be paused on std-by > > > > btw if you go to power management you can manually disable > > suspend > > the same here. > > Radek, I did the upgrade as you suggested (from v19 to v21) > without reflashing, and after some few shutdown device -> power on > I realized that the system thinks that it is still on battery > when it is usb attached. So it suspends as Alfa21 also reports. > > Regards. > > Rafael > > > > > > ___ > 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] regression in power management (was: qtmoko v21)
Hello, --- On Fri, 4/9/10, Alfa21 wrote: > > > I hope there are no regressions from previous version. If yes, please let > > me > > know i will try to fix them for next release. > > found a regression: > in v21 if you boot on battery and then attach usb, the > power profile is still on battery. > > eg, if you have enabled suspend: > - ssh connection will be paused because of std-by > - recharge will be paused on std-by > > btw if you go to power management you can manually disable > suspend the same here. Radek, I did the upgrade as you suggested (from v19 to v21) without reflashing, and after some few shutdown device -> power on I realized that the system thinks that it is still on battery when it is usb attached. So it suspends as Alfa21 also reports. Regards. Rafael ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[qtmoko] regression in power management (was: qtmoko v21)
2010-04...@22:31 Radek Polak > I hope there are no regressions from previous version. If yes, please let me > know i will try to fix them for next release. found a regression: in v21 if you boot on battery and then attach usb, the power profile is still on battery. eg, if you have enabled suspend: - ssh connection will be paused because of std-by - recharge will be paused on std-by btw if you go to power management you can manually disable suspend regards -- 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 v21
2010-04...@22:31 Radek Polak > If you have v19 installed, you can try to upgrade without reflashing. > Following > proccess is not tested but should work: > > 1/ download v21 tarbal > 2/ replace /opt with the one in tarbal in your existing rootfs > 3/ unpack /lib/modules from tarbal to your existing rootfs > 4/ edit /etc/modules and delete all contents from it > 5/ flash or replace kernel from tarbal (/boot/uImage-GTA02.bin) is possible to switch back and forth v20/v21? what I've to do? ...or maybe stable/testing are too different? regards and tnx :) (ps: I'm upgrading my v19 to v21 following the procedure above...) -- 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 v21
Radek Polak wrote: > forgot this one: Also forgot important note - if the GSM does not register (you will be in the screen with big dialer keyboard), use POWER button to "Restart QtExtended" until registration is sucessful. This happens only with 2.6.29 kernel, no idea yet why. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v21
Radek Polak wrote: > Here is list of changes since previous stable version (v19): forgot this one: - when charging the power led lights orange (credits for implement to Jeroen Nijhof) and also forgot MD5SUMS: 8c06e5b9dc7196932841ad35448b6137 qtmoko-debian-v21.jffs2 c0eae18059b7913fa1703b089504ebfd qtmoko-debian-v21.tar.gz 8ea022a3eaaba471ad6809b8923934e0 uImage-v21.bin feccf46500c45e25e4d56b2c55ebeebe qtmoko-debian-v20-testing.jffs2 5ed753c7d35107a920e1ca0f871225ff qtmoko-debian-v20-testing.tar.gz 9c503c4045901de6f5c905cd079b1071 uImage-v20-testing.bin Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
qtmoko v21
Hi, today we have also new stable qtmoko images still based on andy-tracking 2.6.29 kernel. It can be dowloaded from usual location [1]. QtMoko is distribution based on Qtopia (or QtExtended) from Trolltech for your Neo Freerunner. For more info please see homepage [2][3] or dowload source code [4]. Here is list of changes since previous stable version (v19): - hopefully fixed bug #80 (lost sms, thanks to Judge_Gregg's great bug report) - SMS messages should stay on SIM now - wifi always available after boot (OM bug #2327) thanks to Gennady for his fix. - more sane power management values by default (suspend after 5 minutes) - added path to /usr/games (for scummvm and other games) - modified kernel config - all FR hardware is now build in - in QX you can enable rotation using accelerometers - QMplayer uses /media/card for saving media if possible I hope there are no regressions from previous version. If yes, please let me know i will try to fix them for next release. I am quite scared to say it but hopefully SMS will be working 100% from now on. I know i have told this like 3 times before, but now i had really great bug report and i could reproduce the bug - big thanks to Judge Gregg bug report and idea to revert the commit which was deleting SMS from SIM. Now SMS are also kept on SIM if possible which is good. As for QX and rotation - you can setup application (via Favourites menu) and enable rotation. It will use accelerometers and xrandr to rotate the screen. For me it works only when booted with uboot and still i sometimes get white screen. But i was able to play Broken Sword in scummvm - and it's great experience - this game rocks on Neo. I am now using kernel config with nodebug and nopreempt. All FR's hardware is built in and it will work even when /lib/modules are missing. Drivers for USB devices are still as modules. You can find kernel config and wifi patch here [5]. If you have v19 installed, you can try to upgrade without reflashing. Following proccess is not tested but should work: 1/ download v21 tarbal 2/ replace /opt with the one in tarbal in your existing rootfs 3/ unpack /lib/modules from tarbal to your existing rootfs 4/ edit /etc/modules and delete all contents from it 5/ flash or replace kernel from tarbal (/boot/uImage-GTA02.bin) I have a lot of plans for next version, but now enjoy new version i hope it will serve well. Cheers Radek [1] http://sourceforge.net/projects/qtmoko/files/ [2] http://qtmoko.org/ [3] http://activationrecord.net/radekp/qtmoko/ [4] https://docs.openmoko.org/trac/ticket/2327 [5] http://github.com/radekp/qtmoko/tree/master/devices/neo/linux_kernel/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community