no ... its maemo..
install Nokia qtcomponents, and the scaffold of the theme along with it..and malit keyboard quick ..and you'll be able to use it in qt apps in maemo
no ... its maemo..
install Nokia qtcomponents, and the scaffold of the theme along with it..and malit keyboard quick ..and you'll be able to use it in qt apps in maemo
what we need is a virtual keyboard that works on all type of apps/program...not just qt apps....
well it does only if the qt app has portrait mode in it.. it will go out of screen in forced rotation mode..i.e in MAG's media player and all..while it works fine in Miniature..basically if the app is essentially a portrait mode one..then it will work fine :P
im happy as it helps a lot while playing miniature!
I've always been curious why people with a n900 want a virtual portrait keyboard. Portrait mode is great, if the tasks needed can be performed with the thumb. For example, it is excellent to read SMSs, check missed calls, etc.
But if I need -for example- to write a new SMS, physical keyboard is the best choice, that's one of the main reasons we love our n900, right ? :-)
I have an issue with camera which is maybe CSSU related, so it would be very helpful if other users can check this.
Start video recording and during recoding close camera cover. Then check if the recorded video is playable or not. I tried many times and I always end up with unplayable (corrupted) video.
I have latest CSSU and kernel power 48. Because I have multiboot I also tested stock kernel and the result is the same. But on friend's phone without installed CSSU the recorded video is fine.
Another thing, my phone has installed fcam-drivers 1.0.7-2, but on the friend's it is 1.0.7-1.
I have an issue with camera which is maybe CSSU related, so it would be very helpful if other users can check this.
Start video recording and during recoding close camera cover. Then check if the recorded video is playable or not. I tried many times and I always end up with not playable (corrupted) video.
This does not work currently. This is a bug in the camera-ui.