Opened 10 years ago

Closed 9 years ago

Last modified 8 years ago

#1125 closed enhancement (fixed)

fast kernel like android, usability improvement

Reported by: robin Owned by: ainulindale
Priority: minor Milestone:
Component: SHR Image Version: SHR-unstable
Keywords: usability improvement Cc:

Description

I was wondering if there is also a fast kernel for shr-u, as for qtmoko and android, which react much more quickly.

Change History (18)

comment:1 Changed 10 years ago by elhennig

I use the qtmoko kernel of version v24 for SHR-U and it works very well

comment:2 follow-ups: Changed 10 years ago by robin

I also use qtmoko v24 and shr-u (with the latest opkg upgrade), but I really have the feeling of a much longer delay, between pressing the icon on the home screen and the application actually appearing on the screen. I also noted that qtmoko now has the logging turned off; is that the case for shr-u as well?
one good comparison in my view is navit:
it is much much more responsive on qtmoko v24 and android compared to shr-u (I would say almost twice as fast).

comment:3 in reply to: ↑ 2 Changed 10 years ago by elhennig

Replying to robin:

one good comparison in my view is navit:
it is much much more responsive on qtmoko v24 and android compared to shr-u (I would say almost twice as fast).

I don't think this is a good measure to compare since the performance of navit stronglyy depends on the used graphics and gui type. I use (SDL/internal) and that works pretty well, except for a 5-10 secs delay in the position calculation.

comment:4 in reply to: ↑ 2 Changed 10 years ago by elhennig

Replying to robin:

I also use qtmoko v24 and shr-u (with the latest opkg upgrade)

Just to clarify this: I am running the latest SHR-U on top of the qtmoko v24 kernel. With this combination of the two distros the gui reacts pretty well.

comment:5 Changed 10 years ago by robin

now I understand. Could you please be so kind and give me some information on how this is done (eg. does one need to install some modules, ...) that would be great. Thanks for your help!

comment:6 Changed 10 years ago by robin

@ the navit issue.
the only reason I brought this up was that I had the chance to test it on all three distributions (shr-u own kernel, qtmoko and android) and it was just way faster on the last two of the list.

comment:7 Changed 10 years ago by elhennig

You have to get the kernel image and addintionally you need the root.tar.gz of v24 in order to extract the modules dir /lib/modules/2.6.29-rc3-v24/
This you need to copy to the freerunner, run depmod -a 2.6.29-rc3-v24, flash the kernel image to nand and reboot....

comment:8 Changed 10 years ago by robin

subperb, thanks a lot. I will try this tonight

comment:9 Changed 10 years ago by robin

  • Type changed from defect to enhancement

@ elhenning: everything worked nicely. thanks for your advice.
shr-u indeed behaves much more responsive than before. though it is still, at least in my opinion, a good bit slower than qtmoko and android (which is running java, which is supposed to be quite slow by itself). I still have no idea why this may be, especially if one reads more about e17 and everyone is considering it the about the fastest window manager you can get for slow hardware. If anyone could shed some light I would be very thankful. best regards

comment:10 Changed 10 years ago by yorambh

It's possible that DBUS based user-space (FSO) is lower then Android's java implementation.
Considering the fact that DBUS is actually OO abstraction layer that is implemented by passing XML between processes, is might have more performance penalty then Java.
Also, X11 is not necessarily the fastest way to supply graphic capabilities for slow hardware.

comment:11 Changed 10 years ago by robin

@ yorambh; first of all thanks for your explanation. I am no software design expert so I will try to summarise what you said for the ignorant.
shr-u is using dbus (fso) which itself uses xml to exchange information between processes. This may be slower than having a java system beneath (android).
where does qtextended (qtmoko) stand in this game; I know it's not x11 as this had is a "subprocess" which has to be started. The interesting thing from my point of view is that if I use qtmokos x11 with navit and compare it to navit on shr-u, navit is way more responsive (pressing the action/settings/whatelse button) than shr-u. To say it is as responsive as navit on android...

comment:12 Changed 10 years ago by Heinervdm

  • Milestone set to MS2

Faster kernel will come with switch to 2.6.3*
You can already try this kernel: http://build.shr-project.org/tests/mrmoku/2.6.34/images/om-gta02/

comment:13 Changed 10 years ago by elhennig

Currently 2.6.34 does not work for me, as the sd card is not being recognized.

comment:14 Changed 10 years ago by yorambh

QtMoko? supplies X11 for programs that need it, but it does not use it for it's own GUI and does not really have window-management. that can have performance benefit.
As for 2.6.34, it does seem faster but it still have to many annoying issues.
The SD problem (not identifying partition table) can be worked around by running:
# mioctl /dev/mmcblk0 0x0000125F 0
this ioctl() cause partition table reload for the device.

comment:15 Changed 10 years ago by robin

@ yorambh. I currently run qtmoko with kernel 2.6.29 and it is significantly faster than shr (its own non X11 applications and X11 applications like navit). I also followed ehellings advice to change shr kernel to qtmoko-v24 kernel which makes shr-u somewhat faster but as I stated earlier by no means near qtmoko.
I very much like shr (style, applications, ...) but was just wondering if it was ever going to reach the speed which apparently the hardware is able to deliver.

comment:16 Changed 10 years ago by robin

Does anyone know if one can make illume have three desktops like android with fixed icons on each of them and a change between them by sliding left or right over the screen?

comment:17 Changed 9 years ago by Heinervdm

  • Resolution set to fixed
  • Status changed from new to closed

Since switch to 2.6.3x we are using a fast kernel too, so this is fixed

comment:18 Changed 8 years ago by morphis

  • Milestone MS2 deleted

Milestone MS2 deleted

Note: See TracTickets for help on using tickets.