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 <yann.sla...@free.fr> 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