maemo.org - Talk - The in-development Maemo 5 Community SSU

maemo.org - Talk (https://talk.maemo.org/index.php)

- Maemo 5 / Fremantle (https://talk.maemo.org/forumdisplay.php?f=40)

- - The in-development Maemo 5 Community SSU (https://talk.maemo.org/showthread.php?t=67905)

Re: The in-development Maemo 5 Community SSU

hey
how is the SSU?
still buggy?
Can I update without having after that problems with my n900, like camera etc.

Re: The in-development Maemo 5 Community SSU

see video of new portrait mode HERE!
http://www.youtube.com/watch?v=9MxR1VrDFeI

Re: The in-development Maemo 5 Community SSU

i installed it, but no portrait here.

Re: The in-development Maemo 5 Community SSU

Quote:

Originally Posted by Mentalist Traceur (Post 950291)

Hmmm... I'll be honest with you, I don't have that many Qt programs on my N900, but the one's I've tested this on, I don't seem to see any problems (I've tested FastSMS, and HealthCheck.)

I do see a problem with HealthCheck, something about certain images not found according to an error it prints to X-Term, but it seems to appear regardless of whether it's launched in portrait mode or not.

What Qt apps do you have this error in? I'd be happy to test further.

Either way, I'm sorry, but I don't get the logic of that. It's basically saying "it's not going to be perfectly supporting everything, so we shouldn't include it at all". By the same reasoning, why bother doing anything? Why bother developing a system-wide portrait keyboard, if portrait support didn't yet exist everywhere? Etc, etc.

It just really seems like a very moot point. Portrait support has been wanted since this phone came out. If it's not implemented globally, it works peacemeal like it does now, but always with manual auto-rotate, etc. If it IS implemented globally, it still works peacemeal, but it works for a lot more things, and it works automatically for a lot more programs where it didn't work before. The ones it works glitch-ish-ly for, it still effectively doesn't completely work for, but there's a bunch of programs the usability of which gets increased.

I mean, really, if you look at all the programs that the N900 has, how many of them are actually in Qt? And most of those are at least made to work in portrait mode, if not to be launched in portrait mode. Having global auto-rotation would be wonderfully useful, and even if you're right and those Qt apps have problems with it, it's not hard to mentally remember that a few of your phone's apps shouldn't be launched in portrait mode - far more convenient, it is, then clicking some shortcutd mapped key to use Ctrl+Shift+R, let alone manually entering that combination.

Actually my point was that before launching system-wide portrait mode we (and by saying we I mean even me if I have some damn free hours) should fix at least known problems. And if you check extkbd thread you will see that latest version has portrait mode support. I absolutely agree with you that one should not stop system-wide portrait mode because not all of the closed bits support it, but knowing that there are bugs in QT libraries re portrait mode and not fixing them does not look good to me. Are we on a hurry, do we have some schedule from management? Or the idea of Community SSU is to show that something can be done, even incomplete and ugly.

Don't get me wrong, I fully support the idea of having full portrait mode on our phones, just want things to be done in the right way not in the same half-baked Nokia way.

Re: The in-development Maemo 5 Community SSU

well the work is just awsome since the last update !!!!!
great thanks all the team ( can't use the same 'thanks' button more than 1 time xD )
keep going on you made in few weeks what Nokia didn't do 8n more than a year :o
cheers

Re: The in-development Maemo 5 Community SSU

Quote:

Originally Posted by clovis86 (Post 952284)

and the congregations said:

AAAAAAAMEEEEN!

Re: The in-development Maemo 5 Community SSU

Quote:

Originally Posted by ceroberts75 (Post 952277)

i installed it, but no portrait here.

need to activate it in transitions.ini

Re: The in-development Maemo 5 Community SSU

could you please point me to where i would get that setting taken care of?

i searched this thread, but only see the blur effect stuff...of which i dont think is what i would be looking for?

Re: The in-development Maemo 5 Community SSU

weird no new updates for me...

Re: The in-development Maemo 5 Community SSU

hmm...damn.

i changed the setting in the transistions.ini file to 1. and saved it.

rebooted, but still no rotation. what am i doing wrong?

Re: The in-development Maemo 5 Community SSU

hmm odd, are you sure you saved?

Re: The in-development Maemo 5 Community SSU

yes. i just checked and still shows:

http://ceroberts75.001webs.com/pictu...rcedrotate.png

Re: The in-development Maemo 5 Community SSU

quick question. what is the purpose of the tactile patch? the package note says, " tactile provides improved tactile feedback with different patterns to improve the user experience on the N900", but what exactly does that mean?

edit: never mind. i went ahead and installed it anyways. the package description pretty much sums it up. not being one who finds tactile feedback to be particularity useful, i think i will uninstall it to save on battery life. eh...different strokes for different folks.

thanks for the update, everything seems to be working as expected.

Re: The in-development Maemo 5 Community SSU

can anyone plz pass me the new transition.ini maemoder replaced mine ,,thnx in advance

Re: The in-development Maemo 5 Community SSU

Quote:

Originally Posted by mike_shenoda (Post 952321)

can anyone plz pass me the new transition.ini maemoder replaced mine ,,thnx in advance

dang. sorry i already over-writ mine with my modded one. i guess i can upload it anyways. take it or leave it, your call.

EDIT:

this is the only part that changed. when you installed the CSSU update, it should have backed up your old one with a .old extension. you can just copy this new bit of code into it and remove the .old extension and you should be good to go.

Code:

##

# Special tweaks (a restart might be required)

##

[thp_tweaks]

# Blurless desaturation (0 = default, 1 = MeeGo/Symbian-style)

blurless = 1



# Bigger task switcher (0 = default, 1 = single column, 2 = two columns)

taskswitcher = 0



# Rotation around the Z axis (0 = rotate around X/Y, 1 = rotate around Z)

zaxisrotation = 0



# Forced app auto-rotation (0 = default, 1 = auto-rotate every app)

forcerotation = 1



# Popup feedback using the "tactile" utility (0 = disabled, 1 = enabled)

# You need to install "tactile" from the maemo.org repositories for this

tactilepopups = 0

Re: The in-development Maemo 5 Community SSU

It's exactly what the name says - it provides 'tactile' feedback to on-screen events. Currently, popup element movements will trigger the vibrate motor as they provide damage to the backdrop. Enable it, install `tactile` and open the status menu or the power key menu.

Perhaps this can be integrated into the "bounce" scrolling - but that might be on a per-process basis.

Re: The in-development Maemo 5 Community SSU

Quote:

Originally Posted by mike_shenoda (Post 952321)

can anyone plz pass me the new transition.ini maemoder replaced mine ,,thnx in advance

`dpkg --configure hildon-desktop`

Re: The in-development Maemo 5 Community SSU

Quote:

Originally Posted by alcockell (Post 952248)

I have a little over a year to go on my N900's contract, but once it's over, I reckon I'd be ready to load it onto my phone... Do the devs think that the new Community N900 base build will be Gold Release by then?

As in released into Extras, ready for full release?

Why are you going to wait until your contract is over to install this? :confused:

Do you think it's going to void your warranty? Because it won't.

Re: The in-development Maemo 5 Community SSU

Is there a fix to the Virtual keyboard? Like changing the size of the font displaying on the v.keyboard buttons. Would love to see some improvement on this as well :)

Re: The in-development Maemo 5 Community SSU

Can you include the FM-transmitter patch as well?

It's in my signature :) This would make a lot of people happy

Re: The in-development Maemo 5 Community SSU

Quote:

Originally Posted by maxximuscool (Post 952347)

Can you include the FM-transmitter patch as well?

It's in my signature :) This would make a lot of people happy

While you yourself claiming this:??? I do not see it happening.

Quote:

Originally Posted by maxximuscool (Post 789989)

WARNING: Use this at your own risks :) It might be illegal to use the FM frequencies any lower than your country allowed. I'm not paying responsibility to any unlawful fine that you may get from your country authority, This is not my responsibility nor the developer responsibility. This is an open device, so do what ever you'd like as long you don't abusing your power. Like the spiderman said: Great power comes with great responsibility

Re: The in-development Maemo 5 Community SSU

playing around with this a little more. noticed some interesting things. for some application (i.e. H-A-M and Conversations) the device must be in portrait mode whilst launching the application for portrait mode to be invoked; also the application seems to be locked into portrait mode until exit, or keyboard is slid out; however then the application is locked in landscape mode. furthermore, if i launch an application in portrait mode, exit, then click on status menu, the the status menu loads in portrait mode, regardless of the devices orientation, and will continue to do so until another application is opened in landscape mode, or the keyboard is opened and closed whilst the device is in landscape mode. perhaps there is something funky going on in my device and this is an isolated case, or maybe this is the desired effect; but these results seem to be reproduce-able 100 per cent of the time. i'm not bothered by this, now that i figured out what is going on that is, i just thought i would bring it to your attention and share my finding with other users whom might be experiencing similar results. keep up the great work!

Re: The in-development Maemo 5 Community SSU

hmm...its working now! lol.

stubborn thing! lol

Re: The in-development Maemo 5 Community SSU

Conversations is not loading up on portrait for me, but HAM is, as well as the Launcher. Hmm...

Re: The in-development Maemo 5 Community SSU

I found rotation with Z axis got some problem
when rotating, there is a effect "Brinking" happen in progress

u all same?

Re: The in-development Maemo 5 Community SSU

Quote:

Originally Posted by TMavica (Post 952360)

I found rotation with Z axis got some problem
when rotating, there is a effect "Brinking" happen in progress

u all same?

i'm not really sure what you mean by "brinking", but you can try adjusting the values of:

Code:

[rotate]

duration_in = x

duration_out = x

damage_timeout = x

damage_timeout_plus = x

damage_timeout_max = x

angle = x

# changed from 100 in order to reduce jerkiness of transition (also changed the fade-out so it doesn't fade to black completely)

in your transition.ini file to obtain your desired rotational effect. hope this helps.

Re: The in-development Maemo 5 Community SSU

what urs setting? i follow u

Re: The in-development Maemo 5 Community SSU

so are all your apps forced?

i have the same settings and in order for me to see my conversations, email, etc...i still have to use the ctrl+shift+R

Re: The in-development Maemo 5 Community SSU

hmmm... at first it seems to force rotate all my apps, but after tweaking transitions for a bit... now it doesn't force rotate...

Code:

# This file contains timings and values for transitions in hildon-desktop

# duration = time in milliseconds

# zoom = amount to zoom out the background. 1 = none, 0.5 = zoom to half size

# radius = radius of blur (this is actually the number of blur iterations,

#          so the bigger the number the longer it takes)

# saturation = the amount of colour left in the background (0 = grey, 1 = normal)

# brightness = brightness of the background (0 = black, 1 = normal)          



[blur]

turbo = 0

duration = 0



# Zoom out of the task navigator before it fades out

# -- zoom: how much to scale the switcher when going to launcher

#           (the second layer of the launcher would scale it twice

#            as much but the switcher is hidden by that time currently)

# -- zoom_for_home: how much to scale the switcher when leaving for home

# -- zoom_duration: the number of miliseconds to spend on zooming

#                    a thumbnail

# -- fly_duration: how long should it take for the thumbnails to rearrange

# -- notifade_in/out: time to fade the notifications

# 

[task_nav]

zoom = 0.85

zoom_for_home = 1.4

zoom_duration = 150

fly_duration = 150

notifade_in = 150

notifade_out = 150

tile_font = Nokia Sans 15



# Blurring of the home view

# -- radius: amount of iterations of blur filter to perform when not zoooming

#            eg. for dialogs

# -- radius_more: amount of iterations of blur filter to perform when zooming

#                 eg. for launcher/task navigator

# -- saturation: saturation of the background when blurred

# -- brightness: brightness of the background when blurred

# -- zoom: Basic amount to scale the home view by (gets multiplied by how many 

#          'levels' deep the UI is - eg. launcher is one level, launcher submenu

#          is another)

# -- zoom_applets: Amount to scale applets by when zooming out

[home]

radius = 3.2

radius_more = 3.2

saturation = 1

brightness = 1

zoom = 1

zoom_applets = 1



# These control the deceleration of the launcher pages.  When panning freely

# (decelerating) the velocity of the launcher page is adjusted by this much.

# strong_deceleration_rate is effective in the bouncing zones.  Uncomment if

# you want faster panning.

[launcher]

#deceleration_rate = 0.98

#strong_deceleration_rate = 0.7



# The glow effect around launcher buttons

[launcher_glow]

duration_in = 150

duration_out = 150

radius = 10

brightness = 0.75



# The items below are for the transitions that are applied

# to a 'page' of launcher icons

# -- duration: time in ms

# -- depth: amount to move icons backwards and forwards (with perspective)

#           this is pretty much how big or small the icons get     

# -- sequenced: for in and in_sub, whether icons swoop nicely in (1)

#               or whether they just all zoom in as one (0)

# -- keyframes: A list of values that are linearly interpolated between 

#               to produce the movement of the launcher tiles. There can 

#               be any number of values as long as there are 2 or more. 

#               <1 means nearer the viewer, >1 means further away

# -- keyframes_label: The values used for fading in the labels. 0=transparent

#                     1=opaque

# -- keyframes_icon: The values used for fading in the icons. 0=transparent

#                     1=opaque

# Launcher top layer first appearing

[launcher_in]

duration = 150

sequenced = 0

depth = 50

keyframes = 0,0.17,0.39,0.65,0.87,1.13,1.26,1.22,1.17,1.13,1.09,1.04,1,1,1,1,1,1,1,1,1

keyframes_icon = 0,0.1,0.2,0.3,0.4,0.5,0.6,0.7,0.8,0.9,1,1,1,1,1,1,1,1,1,1,1

keyframes_label = 0,0,0,0,0,0,0,0,0,0,0,0.1,0.2,0.3,0.4,0.5,0.6,0.7,0.8,0.9,1



# Launcher top layer disappearing

[launcher_out]

duration = 150

depth = 50



# launcher top layer disappearing when a layer in front

[launcher_out_back]

duration = 150

depth = 50



# launch animation

# duration_out - amount of time to take when fading the launcher out and application in

# delay - the amount of time to wait after the window has appeared before we fade out

#         (this time is *included* in duration_out, so it must be <= duration_out)  

[launcher_launch]

duration = 150

delay = 150

duration_out = 150

depth = 50



# sub-menu appearing

[launcher_in_sub]

duration = 150

sequenced = 0

depth = 150

keyframes = 0,0.17,0.39,0.65,0.87,1.13,1.26,1.22,1.17,1.13,1.09,1.04,1,1,1,1,1,1,1,1,1

keyframes_icon = 0,0.1,0.2,0.3,0.4,0.5,0.6,0.7,0.8,0.9,1,1,1,1,1,1,1,1,1,1,1

keyframes_label = 0,0,0,0,0,0,0,0,0,0,0,0.1,0.2,0.3,0.4,0.5,0.6,0.7,0.8,0.9,1



# sub-menu disappearing

[launcher_out_sub]

duration = 150

depth = 50



# main disappearing when sub-menu appears

[launcher_back]

duration = 150

depth = 50



# main appearing when sub-menu disappears

[launcher_forward]

duration = 150

depth = 50



# Screen rotation transition

# duration_in = time for rotation before blanking

# duration_out = time for rotation after blanking

# damage_timeout = in the rotation transition, the amount of milliseconds to

#                  leave after we get a damage event before we transition back

#                  from blanking.

# damage_timeout_max = maximum amount of time we may wait if we keep getting

#                      damage events.

# angle = rotation angle for each transition, in degrees. Ideally this is set

#         so that the screen looks like it keeps turning at the same speed 

#         during blanking. 0 is none, 90 degrees is side-on

[rotate]

duration_in = 200

duration_out = 200

damage_timeout = 0

damage_timeout_plus = 0

damage_timeout_max = 0

angle = 45

# changed from 100 in order to reduce jerkiness of transition (also changed the 

# fade-out so it doesn't fade to black completely)



# App close transition

[app_close]

duration = 150



# Popup for dialogs and status menu

[popup]

duration_in = 150

duration_out = 150



# Fade in for banners

# _alpha specifies the final transparency of various things

# currently only banner_note and info_note are supported

[fade]

duration_in = 150

duration_out = 150

banner_note_alpha = 0.85

info_note_alpha = 0.85



# Transition for notification previews

[notification]

is_cool = 0

duration_in = 150

duration_out = 150



# Sliding subview window transition

[subview]

duration_in = 150

duration_out = 150



[loading_timeout]

# This is multiplied by the load average to find the timeout

# in seconds. before "Unable to load" is displayed.  There is

# a minimum of 10s.

load_average_factor = 7.5



# Edit mode configuration

[edit_mode]

snap_grid_size=8

# Set to 0 if snap to grid should be only happen when widget is released

snap_to_grid_while_move = 1



##

# Special tweaks (a restart might be required)

##

[thp_tweaks]

# Blurless desaturation (0 = default, 1 = MeeGo/Symbian-style)

blurless = 1



# Bigger task switcher (0 = default, 1 = single column, 2 = two columns)

taskswitcher = 0



# Rotation around the Z axis (0 = rotate around X/Y, 1 = rotate around Z)

zaxisrotation = 1



# Forced app auto-rotation (0 = default, 1 = auto-rotate every app)

forcerotation = 1



# Popup feedback using the "tactile" utility (0 = disabled, 1 = enabled)

# You need to install "tactile" from the maemo.org repositories for this

tactilepopups = 0

i do get the 'blinking' effect too... it rotates, blinks out for a sec, then continues to rotate normally

Re: The in-development Maemo 5 Community SSU

For the next update of the firmware done by the community we should include the bluetooth PABAP fix the community found so it works with car bt systems.

http://wiki.maemo.org/Bluetooth_PBAP

so we finally have to stop installing every time we update firmware

Thanks

Re: The in-development Maemo 5 Community SSU

Quote:

Originally Posted by TMavica (Post 952369)

what urs setting? i follow u

sorry i didn't include my values as they pretty much disable the visual rotation effect making the switch more snappy rather than fluid. i didn't feel they would be much use to you and might cause confusion.

Re: The in-development Maemo 5 Community SSU

congratulations to the CSSU team for this fantastic update!

Re: The in-development Maemo 5 Community SSU

Brillian work !!!!!!!!!.

Re: The in-development Maemo 5 Community SSU

Quote:

Originally Posted by jd4200 (Post 952333)

Why are you going to wait until your contract is over to install this? :confused:

Do you think it's going to void your warranty? Because it won't.

I'm more of an end-user - and if I *did* brick my phone - would Carphone Warehouse be able to get it fixed for me?

OR would they say that I was on my own.. but unable to get another device?

SO yes - I was concerned that it may void the support from them.

Re: The in-development Maemo 5 Community SSU

Oh - and just as I do with my laptops - which both came preinstalled from Linux Emporium - I stick to the Ubuntu repositories, as I know the software will work... I'm cagey about stepping outside Nokia and Extras repos...

I am looking forward to openOffice for Hildon making it out of extras-devel and actually being released to extras...

Re: The in-development Maemo 5 Community SSU

forced apps rotate in my case only works in these circumstances:
1. when i've unlocked the screen in portrait mode.
2. when in conversations, fastsmsevo pops out.

besides that, after a reboot for example, it doesn't force them to rotate on it's own. i'll have to do one of the above and then the apps will rotate automatically... all except for the ones that already rotate on their own and the apps launcher... apps launcher rotates all the time...

also, when rotating, there's a half a second of blinking...

hope this helps

Re: The in-development Maemo 5 Community SSU

Quote:

Originally Posted by tokag (Post 952349)

playing around with this a little more. noticed some interesting things. for some application (i.e. H-A-M and Conversations) the device must be in portrait mode whilst launching the application for portrait mode to be invoked; also the application seems to be locked into portrait mode until exit. furthermore, if i launch an application in portrait mode, exit, then click on status menu, the the status menu loads in portrait mode, regardless of the devices orientation, and will continue to do so until another application is opened in landscape mode. perhaps there is something funky going on in my device and this is an isolated case, or maybe this is the desired effect; but these results seem to be reproduce-able 100 per cent of the time. i'm not bothered by this, now that i figured out what is going on that is, i just thought i would bring it to your attention and share my finding with other users whom might be experiencing results. keep up the great work!

I'm experiencing the same thing - from the desktop, the launcher works and rotates normally. If I load any app while holding the device in landscape mode, it will not rotate no matter what I do (including CTRL-SHIFT-R). If I hold the device in portrait mode and launch the app, it will launch then rotate to portrait and stay there until I quit the app.

Also - one small nuisance - I seem to have lost my transition fade effects for the launcher as well.

Any thoughts, ideas - maybe someone who has this all working can share their transitions.ini file?

Re: The in-development Maemo 5 Community SSU

I now deactivate the force rotation until next update

Re: The in-development Maemo 5 Community SSU

Hi.

I've just installed it, everything looks good, excellent job.

I'd like to enable the portrait mode and rotation the way it is shown in a video some posts behind.

I'm using "Plastic Dark Black" theme, and I tune up my setting using "Theme Customizer".

How can I make CSSU rotation/portrait/etc live along "Theme Customizer" settings?

I tried first saving all changes from "Theme Customizer", then reboot and then I added the thp_tweaks (zaxisrotation = 1, forcerotation = 1, tactilepopups = 1) to my:

/usr/share/hildon-desktop/transitions.ini file.

After a reboot, nohing changed :-/

I tried also adding the lines to the file:

/home/opt/theme-customizer/transitions.ini

but I did not succeed either.

Any help appreciated.

EDIT: After one more reboot, my phone behaves like @dannycamps described. No zaxis rotation yet though.