Does anybody know on which release the PR 1.1 is based? If it is based on the 51 build or later a lot of important bugs are fixed.
What I already know is that USSD codes (*#) will be working (https://bugs.maemo.org/show_bug.cgi?id=5357) and IMAP will be faster (https://bugs.maemo.org/show_bug.cgi?id=3762) so PR 1.1 must be based on build 46 or later.
You can check in the big reports, but I can tell you this firmware is based on the build 51-1 (2.2009.51-1) so all the bugs fixed before that (in bugzilla) are in this build.
As you know build 51 is the week and 51 is this week, so.. many bugs fixes are included in this one.
Btw, if the whole UI was to support portrait and rotation between the two modes, I wonder how on earth you would make the home-screens work with the sizes of widgets, shortcuts etc. not being standard?
I would assume that in N79 you can turn off the auto rotate feature like in any S60. And I would assume this will be the case with Maemo too.
Maemo 5's UI home screen will never officially support portrait is what I am guessing. Maemo 6 has an entirely different approach to the home screen which solves the rotation issue.
trust me video recording is amazing and one of the features up to scratch already imo, could do with a few more options in settings but recording ability i cant say anything bad about it
Well it misses frames on mine. Apar from that great phone.
then the phone app doesnt completely follow that guide line, it has the option of 'potrait' of 'automatic'
or do you mean that if they can switch it must be automatic? i agree thats a bit stupid better would be 2 have 4 options: landscape,portrait,automatic,user
and when it is user the program menu has a toggle button.
From the Hildon 2.2 UI Style Guidelines:
Originally Posted by
For one-handed use, the touch screen device cannot be used properly in landscape orientation.
For these tasks a separate portrait UI mode can be provided. The Maemo 5 devices should
feature a sensor detecting the device’s orientation. Switching the UI between landscape and
portrait should be automatic based on the input from this sensor.
This language doesn't preclude options for manual toggling; and guidelines are just that, not set in stone.