Re: qtmoko v27
Oh, that's true, i didn't paid attention to that ... It's a relief ^^ -- Gand' On Sun, Oct 3, 2010 at 2:46 PM, Ole Carlsen wrote: > Den 03-10-2010 14:08, Gand' skrev: > > Since i moved to the v27, my touchscreen is kind of weird ... I can't > > draw a straight line, and when i keep the stylus on the screen, it draws > > a tiny star (more or less 9mm²) It makes the docked keyboard pretty > > unusable as when press a key, one of the surrounding key often responds > ... > > -- > >Gand' > > That was also one of the things that Radek mentioned when releasing it: > > -- > I have been testing 2.6.34 kernel for one week now and to me it looks ok. > There can be issues with SD card [6], the touchscreen driver is missing > filtering so it's a bit jittery and i think accelerometers are somehow > strange now. > -- > > As a work-around, for the keyboard, I have rotated my screen 90 degrees > and now I don't hit the wrong key very often anymore. I would though > prefer the possibility to personally decide the size of my keyboard. > > -- > Ole @ Carlsen-web.dk > > ___ > 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 v27
Since i moved to the v27, my touchscreen is kind of weird ... I can't draw a straight line, and when i keep the stylus on the screen, it draws a tiny star (more or less 9mm²) It makes the docked keyboard pretty unusable as when press a key, one of the surrounding key often responds ... -- Gand' On Tue, Sep 28, 2010 at 11:52 AM, Patryk Benderz wrote: > [cut] > > Also it can compare only system clock with RTC, so we always assume that > > system time is correct. Calypso time - do we need it at all? > Maybe to correct drifting RTC? > -- > 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 > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v24
Thank you very much dear ^^ -- Gand' On Tue, Jun 8, 2010 at 10:07 AM, Radek Polak wrote: > On Tuesday 08 June 2010 09:04:49 Gand' wrote: > > > Unfortunatly, i tweaked my alsamixer config, and i'm afraid i did it > pretty > > wrong ... > > is it possible to reset all those settings ? > > Either extract /usr/share/openmoko/scenarios from release tarbal or they > are > also in my git [1] > > Regards > > Radek > > [1] > > http://github.com/radekp/qtmoko/tree/master/devices/neo/alsa_scenarios/gta02_2.6.29/ > > > ___ > 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 v24
Thank you ! Unfortunatly, i tweaked my alsamixer config, and i'm afraid i did it pretty wrong ... is it possible to reset all those settings ? -- Gand' On Fri, Jun 4, 2010 at 7:42 PM, Alex Samorukov wrote: > On 06/04/2010 10:39 AM, Russell Hay wrote: > > Hey Alex, > > > > can you share your settings? > I think it was taken from this page: > > http://wiki.openmoko.org/wiki/Neo_Freerunner_audio_subsystem > > Also, you can call to some number an play with alsamixer (thrue ssh) to > find optimal values. > > > ___ > 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 v24
The only issue i have with qtmoko is call volume ... Even if both sliders are at their maximum, i often can barelly hear anything ... -- Gand' On Thu, Jun 3, 2010 at 11:55 PM, Jim Morris wrote: > Jim Morris wrote: > > > > I did notice that a quick click of the power button used to put the FR > into suspend, but that no > > longer seems to work, is that by design or not? > > Never mind, it seems to work after a fresh reboot. > > Thanks again. > > -- > Jim Morris, http://blog.wolfman.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 v22
I have the same 'problem' here with the v21 instead of v22 ... but mine is rock stable ^^ -- Gand' On Thu, May 27, 2010 at 11:50 AM, Yann SLADEK wrote: > Hi Radek, > > after a test on Gand's FR with v22, I decided to reflash from v21 to v22 > > But, every times the FR goes into sleep, I got a WSOD > I tried to see if I didn't mess with files when flashing but everything was > ok > Then, I realized that, at start, QI says the kernel is qtmoko-v21 (creation > date : 06-04-2010). For the record, I always boot by pressing the AUX+power > buttons > > Is there any problems with qtmoko-v22.bin ? Maybe, it's exactly the same > version as qtmoko-v21 ? > > Regards, > > Yann > > Hi, > i have uploaded new stable QtMoko debian images [1]. > > QtMoko is stable distribution based on Qtopia (or QtExtended). For more info > check our homepage. > > This new version is mainly bug fix release. Changes from previous version > include: > > - fixed power management to correctly detect cable > - fixed GPS power up script (NeronGPS now works just fine again) > - workaround for the GSM (restart not needed now) > - added omhacks for controlling Neo hardware from command line > - new application Neocontrol for controlling Neo sysfs and other tasks > - implemented power management for locked/unlocked screen > - build fixes and code improvements (Bartlomiej Zimon) > > As for the fixes: first two are quite clear. The problem with GSM not > registering can be partially solved by putting sleep after we power the modem > on. GSM registering now failed for me only first time after flashing. Then i > tried many times and haven't hit the problem again so let's hope it's fixed > now. Anyway 2.6.32 does not have this problem - so 2.6.32 is long term > solution. > > Omhacks [4] is great for various low level openmoko setting. It's from Debian > and credits to it's authors. I will slowly migrate everything to use it's API. > > Neocontrol is work in progress application. Most of the functionality is not > implemented yet. The switching to QVGA is only experimental and it will most > probably not work for you. Watching the sysfs is on the other hand working and > is useful. > > I have also implemented power management for locked/unlocked screen. If you > set intervals to 0 in "When locked" mode - it will not be used and Qtmoko will > use suspend intervals based on power source. This feature is still quite > experiment and i think sometimes it does now properly. > > As for upgrading to new version: the kernel, rootfs and all except /opt is the > same. You can just grab qtmoko-update-v22.tar.gz, stop Qtopia and unpack it. > > ssh r...@192.168.0.202 > > cd / > wget http://sourceforge.net/projects/qtmoko/files/qtmoko-update- > v22.tar.gz/download > /etc/init.d/qpe.sh stop > tar xzvpf qtmoko-update-v22.tar.gz > > Btw please check MD5SUMs: > > 7bd189c4ab152f92517b82d748f22a8a qtmoko-debian-v22.jffs2 > 79012074ea1c2c6498b7524ab2e70fb7 qtmoko-debian-v22.tar.gz > 96e7c199a9001b6b1d0a4f8a45effc47 qtmoko-update-v22.tar.gz > 8ea022a3eaaba471ad6809b8923934e0 uImage-v22.bin > > > Plans for next version remain the same except that i have now GTA01 device > (thanks to Pavel Machek), so if all goes right i will release also gta01 > images. > > Hope you'll like this new version > > Cheers > > Radek > > [1] http://sourceforge.net/projects/qtmoko/files/ > [2] http://qtmoko.org/ > [3] http://activationrecord.net/radekp/qtmoko/ > [4] http://git.debian.org/?p=pkg-fso/omhacks.git > > __ > _ > Openmoko community mailing list > commun...@lists.openmoko.orghttp://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: QtMoko v22
Oh ok, so i'll give it a try :) Improved reactivity worth the shorter battery :D -- Gand' On Fri, May 14, 2010 at 10:24 AM, Radek Polak wrote: > On Friday 14 May 2010 00:33:48 Gand' wrote: > > > Do you mean it's significantly more unstable than the v20 ? > > 'Cause i've been using it for a while, and there was nothing critical in > it > > ... > > It should be better then v20, but both have the problem that it eats > battery > in suspend - much more then stable ones. > > 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 v22
Do you mean it's significantly more unstable than the v20 ? 'Cause i've been using it for a while, and there was nothing critical in it ... -- Gand' On Thu, May 13, 2010 at 10:01 PM, Radek Polak wrote: > Gand' wrote: > > > Is this possible to update from v20 to v23 without flashing ? > > You can always update manually if you replace /opt and check the > differences in > rootfs. > > But v23 is experimental based on 2.6.32. I'd recommend it only for testing > not > for serious using now. > > 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 v22
Is this possible to update from v20 to v23 without flashing ? -- Gand' On Wed, May 12, 2010 at 7:43 AM, Radek Polak wrote: > On Wednesday 12 May 2010 02:13:13 Denis Johnson wrote: > > > I re-flashed with latest v23 files > > Just a warning note: v23 is still not good enough for daily use. It's based > on > 2.6.32 and it has problems with power management. For daily use i'd > recommend > v22. > > 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] Bug 1024
really ?
because "always" doesn't seem to work, as my battery life doesn't exceed a
day with QTmoko, whereas it lasts more or less 3 days with SHR ...
if it's not the #1024, what else ?
--
Gand'
On Wed, Apr 28, 2010 at 11:46 AM, Radek Polak wrote:
> On Wednesday 28 April 2010 10:31:30 Gand' wrote:
>
> > The correct value to fix #1024 in qtmoko in */opt/qtmoko
> > /etc/default/Trolltech/Modem.conf*
> > is "*yes*" instead of "always" ("always" is the value to use with SHR)
>
>
> It's the same if you have "always" or "yes". The code checks for "never"
> and
> activates deep sleep otherwise.
>
>
> http://github.com/radekp/qtmoko/blob/master/devices/neo/src/plugins/phonevendors/neo/vendor_neo.cpp
>
>if (deepsleep == "never")
>chat("AT%SLEEP=2");
>else
>chat("AT%SLEEP=4");
>
> 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] Bug 1024
The correct value to fix #1024 in qtmoko in */opt/qtmoko
/etc/default/Trolltech/Modem.conf*
is "*yes*" instead of "always" ("always" is the value to use with SHR)
--
Gand'
On Sat, Apr 17, 2010 at 1:31 PM, Alfa21 wrote:
>
> another cause maybe:
>
> [quoting from wiki about debian]
> echo 500 > /sys/module/glamo_mci/parameters/sd_max_clk
> echo 3 > /sys/module/glamo_mci/parameters/sd_drive
>
> If that resolves the problem and installation completes, you are that much
> wiser. However, SD card performance is reduced even from the default, power
> consumption increases and SD card power could interfere with GPS
> functionality.
> [/quote]
>
> ...and qtmoko uses sd_max_clk in /etc/init.d/qpe.sh for compatibility
> reasons
>
> --
> 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
>
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v22
I'm also using kernel 2.6.32, and there is no problem with it (if you except the poor battery life ...) -- Gand' On Tue, Apr 27, 2010 at 6:15 PM, Radek Polak wrote: > On Tuesday 27 April 2010 17:00:52 Yann SLADEK wrote: > > > What are the annoying bugs you're talking about ? > > I'm on v21 (or v20 I don't remember but 2.6.32 kernel) for a month now > and > > I didn't see any regressions (touchscreen is smoother, speed has been > > improved, etc..) > > Oki, nice to hear it. > > > The only weird thing I got is a poor battery life (24h > > max) althought I have a buzzfixed GTA02 (the battery goes up to 80h with > > SHR for example). I did the modification of the right file but I have the > > same behaviour than with Android who didn't implement the software fix. > > I have #1024 fix since Saturday, but havent tried it yet. But in the Modem > AT > logs it seems ok. This is my log line after modifying DeepSleep to yes: > > Apr 27 18:08:53 neo Qtopia: AtChat : T : "AT%SLEEP=4" > > if it was not active you should get AT%SLEEP=2. But maybe the command has > to > be issued also after resume. I'll have to check if it's correctly > implemented... > > 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: Voice quality on FreeRunner A7 ?
i have a very annoying buzzing sound with the latest SHR for the caller on my openmoko A7 i hear everything pretty well and clear, but the other side is hearing a mettalic buzz ... i think this is the "awful" here ... can you share your tweaked volume settings ? best regards -- Gand' On Sat, Feb 20, 2010 at 6:51 PM, Al Johnson wrote: > On Saturday 20 February 2010, pbondo wrote: > > Hi folks > > > > My current FreeRunner A6 (buzz fixed) has at best had a medium voice > > quality during phone calls. I.e. I could heat the other party well, but > > (s)he could only hear me just about acceptable. Now my phone has started > > freezing on me. I believe it is a hardware problem so I plan to toss it > > away (or use it as a developer phone). > > > > I have then borrowed another buzz fixed A6 from a friend. It does not > > freeze (with the same SDCard), but the voice quality on the other end of > a > > phone call is just plain awful. > > Describe 'awful'. It probably just needs a tweak to the volume settings, > and > we can help with that. With the right volume settings my FR is on a par > with > my k700i. > > > I am considering buying a new A7+ simply because there some things about > > this phone and the software that I like :-) > > > > However I would like to hear about other peoples experiences with voice > > quality on A7 phones e.g. compared to other mobile phones. Have they just > > fixed the buzz, or can I expect a good voice quality on phone calls ? > > Audio is AFAIK the same as a buzz-fixed A5 and A6. > > ___ > 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: deep sleep on Android, was Re: QtMoko v14
any news ?
--
Gand'
On Sun, Oct 18, 2009 at 11:09 AM, Chris Samuel wrote:
> On Sun, 18 Oct 2009 05:53:36 pm Petr Vanek wrote:
>
> > thank you, please keep us posted if anything changes...
>
> Michael Trimarchi ("Panicking") is on the case already. :-)
>
> cheers,
> Chris
> --
> Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
>
> This email may come with a PGP signature as a file. Do not panic.
> For more info see: http://en.wikipedia.org/wiki/OpenPGP
>
> ___
> 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: Some questions about android on Freerunner
no, the page you can't access only contains software ... to use android on freerunner, you only need content from that page : Index of /android <http://panicking.kicks-ass.org/download/> -- Gand' On Tue, Nov 3, 2009 at 9:31 PM, a dehqan wrote: > In The Name Of God The compassionate merciful > > Good day everyone ; > > Access to this page <http://code.google.com/> is forbidden from server to > iranians . > To installing and using android on Freerunner do we need that address > content ? > > but android.com is open for us . > by and large can we use android legally ? > > Regards dehqan > > ___ > 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: Launcher v0.41 - New Release
and how should that be done ? -- Gand' On Fri, Oct 30, 2009 at 5:27 PM, Al Johnson wrote: > On Friday 30 October 2009, Sebastian Krzyszkowiak wrote: > > On 10/30/09, Gand' wrote: > > > hi > > > > > > is it possible to define launcher as the default desktop application > (ie > > > making it disappear from the task list)? > > > it's kind of annoying using it as an application ... > > > -- > > > Gand' > > > > > > On Fri, Oct 30, 2009 at 1:48 PM, Adam Jimerson > wrote: > > >> On Fri, Oct 30, 2009 at 3:09 AM, Petr Vanek > wrote: > > >>> >> it feels very responding, after all data is loaded. (most delays > > >>> >> seem to be caused by waiting for the opimd data). > > >>> > > > >>> > Actually, the contacts are synced the first time only. The SMS's > are > > >>> >typically not that many, but for opimd to go through all the calls, > > >>> >parse them and send them through the dbus really takes long. Since > > >>> >launcher doesn't know if you received calls when it wasn't running, > it > > >>> >uses the time of the last call it has in its local db to query for > > >>> >newer calls from opim. Hence the delay. Typically, about 10 - 12 > secs. > > >>> >Keeping a smaller log will speed up launcher. > > >>> > I've been thinking of deleting all the calls older than those > > >>> > launcher > > >>> >displays - or some x days automatically. What do you think? > > >>> > > >>> if the number of days is configurable (possible to set to > "unlimited"), > > >>> this would be very good. > > >> > > >> +1 for configurable number of days for the logs > > >> > > >> >Did you like the the fact that your contacts now show > > >> >when you contacted them last? > > >> > > >> Yes I like the fact that it shows when and how you contacted someone > > >> last, I have found this feature very useful already thank you for > > >> adding it! > > > > It should be possible. Launcher has to obtain X root window, just like > > openmoko-today2 was doing (someone reported recently that it works > > with Illume) > > Interesting - I didn't know that would work with illume. > > ___ > 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: Launcher v0.41 - New Release
hi is it possible to define launcher as the default desktop application (ie making it disappear from the task list)? it's kind of annoying using it as an application ... -- Gand' On Fri, Oct 30, 2009 at 1:48 PM, Adam Jimerson wrote: > On Fri, Oct 30, 2009 at 3:09 AM, Petr Vanek wrote: > >> >> it feels very responding, after all data is loaded. (most delays seem >> >> to be caused by waiting for the opimd data). >> >> >> > Actually, the contacts are synced the first time only. The SMS's are >> >typically not that many, but for opimd to go through all the calls, >> >parse them and send them through the dbus really takes long. Since >> >launcher doesn't know if you received calls when it wasn't running, it >> >uses the time of the last call it has in its local db to query for >> >newer calls from opim. Hence the delay. Typically, about 10 - 12 secs. >> >Keeping a smaller log will speed up launcher. >> > I've been thinking of deleting all the calls older than those >> > launcher >> >displays - or some x days automatically. What do you think? >> >> if the number of days is configurable (possible to set to "unlimited"), >> this would be very good. >> >> > +1 for configurable number of days for the logs > > > >Did you like the the fact that your contacts now show > >when you contacted them last? > > > Yes I like the fact that it shows when and how you contacted someone last, > I have found this feature very useful already thank you for adding it! > > > ___ > 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
