Active Topics

 


Closed Thread
Thread Tools
Posts: 101 | Thanked: 50 times | Joined on Nov 2010 @ Liverpool, England
#5151
Originally Posted by ejasmudar View Post
I am not using qtlockscreen and can confirm that my N900 behaves just like what algiz said. ie,
desktop > lock > unlock > desktop
app > lock > unlock > app
taskswitcher > lock > unlock > taskswitcher
app menu > lock > unlock > app menu
i am thinking guilledocs problem might be because of qtlockscreen
but algiz has qtlockscreen and is working as normal
 
travla's Avatar
Posts: 397 | Thanked: 241 times | Joined on Mar 2010 @ Melbourne, Australia
#5152
Hi guys, of those users who have reported ApMeFo as working with CSSU, can any of you tell me what version you are running? Pre-CSSU, I was on v0.9.5, which worked great but has now been cleaned out by repository managment. The current version, 0.11.1 (not uploaded by the original dev) will not update the Hildon Menu for me.

Anyone know how to get an old deb or does it need to be rebuilt (of which I have no idea how to do)?
 
Posts: 250 | Thanked: 126 times | Joined on Dec 2010
#5153
Originally Posted by poogash View Post
i am thinking guilledocs problem might be because of qtlockscreen
but algiz has qtlockscreen and is working as normal
probably thats the problem becouse I do have installed qtlockscreen recently and this started to happend but i wanted to ask becouse it started at same time the upgrade of the cssu.
this is anoying maybe Ill try to uninstall the qtlockscreen and see what happen
 
travla's Avatar
Posts: 397 | Thanked: 241 times | Joined on Mar 2010 @ Melbourne, Australia
#5154
Okay, got the Currency Exchange Widget to update, but only reliably over Packet Data (frequently fails to update over WiFi). I'm guessing this condition has been there for some times, when an update fails, the currency conversion rate goes orange (which I do recall seeing pre CSSU).
 

The Following User Says Thank You to travla For This Useful Post:
algiz's Avatar
Posts: 24 | Thanked: 14 times | Joined on Sep 2011 @ Germany
#5155
Originally Posted by guilledoc View Post
probably thats the problem becouse I do have installed qtlockscreen recently and this started to happend but i wanted to ask becouse it started at same time the upgrade of the cssu.
this is anoying maybe Ill try to uninstall the qtlockscreen and see what happen
I was happy too early. Yesterday just some hours after my "works for me" post I experienced that problem too I was browsing with opera and locked the screen. After unlocking I saw opera for less than a second and then qtlockscreen showed up for moment. After that I got the desktop instead opera.

But as rotoflex said this problem doesn't seem to be CSSU related. So it should be reported in the qtlockscreen thread (and/or bugtracker) if it hasn't been already done.
 

The Following 3 Users Say Thank You to algiz For This Useful Post:
forsagar's Avatar
Posts: 64 | Thanked: 65 times | Joined on May 2011 @ india
#5156
Originally Posted by maxximuscool View Post
Here you go my personal transitions.ini. This will help improve your device animation and rotation is very similar to those on Android.
Fast rotation and fast transition. This transition is best with/without HWSync. Hope you like it. If you do like it then do Thanks me click the button.

Incase those who'd not have a clue of where to do it. Here is the detail:

sudo gainroot
leafpad /usr/share/hildon-desktop/transitions.ini

Copy and paste this and save
==================================================

# 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 = 200

# 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 = 250
fly_duration = 250
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
# -- zoom_on_press: set to 1 to include a zoom effect when the screen is pressed
# -- parallax: Amount of parallax between desktop and widget layers when panning

[home]
radius = 0
radius_more = 0
saturation = 1.0
brightness = 1.0
zoom = 1.0
zoom_applets = 1.0
zoom_on_press = 0
parallax = 1.4

# 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 = 100
duration_out = 200
radius = 14
brightness = 0.95

# 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 = 50
sequenced = 0
depth = 225
keyframes = 0,0.17,0.39,0.65,0.87,1.13,1.26,1.22,1.17,1.13,1.0 9,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 = 50
depth = 150

# launcher top layer disappearing when a layer in front
[launcher_out_back]
duration = 50
depth = 150

# 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 = 400
delay = 500
duration_out = 700
depth = 100

# sub-menu appearing
[launcher_in_sub]
duration = 50
sequenced = 0
depth = 200
keyframes = 0,0.17,0.39,0.65,0.87,1.13,1.26,1.22,1.17,1.13,1.0 9,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 = 50
depth = 150
sequenced =1

# main disappearing when sub-menu appears
[launcher_back]
duration = 50
depth = 200
sequenced = 0

# main appearing when sub-menu disappears
[launcher_forward]
duration = 50
depth = 200
sequenced = 0


# 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 = 0
duration_out = 0
damage_timeout = 0
damage_timeout_plus = 0
damage_timeout_max = 0
angle = 0
# 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 = 450

# Popup for dialogs and status menu
[popup]
duration_in = 250
duration_out = 250

# Fade in for banners
# _alpha specifies the final transparency of various things
# currently only banner_note and info_note are supported
[fade]
duration_in = 200
duration_out = 500
banner_note_alpha = 0.85
info_note_alpha = 0.85

# Transition for notification previews
[notification]
is_cool = 0
duration_in = 400
duration_out = 450

# Sliding subview window transition
[subview]
duration_in = 250
duration_out = 250

[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 = 4.5

# Edit mode configuration
[edit_mode]
snap_grid_size = 4
# 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 = 0

# Popup feedback using the "tactile" utility (0 = disabled, 1 = enabled)
# You need to install "tactile" from the maemo.org repositories for this
tactilepopups = 0

how to change app menu background to black ? It's impossible to view apps in white backgroud.

sorry but I did this using cssu tuner.

Last edited by forsagar; 2011-10-06 at 14:38.
 
Posts: 1,397 | Thanked: 2,126 times | Joined on Nov 2009 @ Dublin, Ireland
#5157
I think we really need a better way to deal with transitions, desktop settings and theme management directly integrated in the CSSU to avoid obsolescence.

Theme Customizer is not maintained any more and using it with latest CSSU results in loosing any changes made by CSSU Features Configuration utility or any manual change.

What I would like to propose is to add more options in the default configuration menu for theme management. Not only the ability to choose a theme but also, choosing the icon pack, fonts or even a predefined transitions file. This way Theme Customizer wouldn't be needed any more.

I would also propose to update packages dependant on Theme Customizer to avoid that dependency (i.e. some icon packs) and theme packs.

Then a transitions tuning utility (such as CSSU Tuner but more fine grained) should be integrated in the setup menu of CSSU. But it's important to separate transitions tuning from any other desktop options enabled by CSSU. Maybe the thp_tweaks section could go even into another file. This way we could have packages for specific transition styles such as a Harmattan Style transitions or the dibble doddle transitions to be downloaded and selected in the configuration menu.

Finally a third item in the setup menu could be a desktop options menu, where the thp_tweaks or other options could be configured.

Hope it makes sense.
 

The Following 9 Users Say Thank You to ivgalvez For This Useful Post:
travla's Avatar
Posts: 397 | Thanked: 241 times | Joined on Mar 2010 @ Melbourne, Australia
#5158
I have been unable to send e-mails via Modest when using Tree View mode, is this possible? Can anyone else confirm whether they've had this problem. E-mail just sits there with a Sending status in the Outbox and eventually it's status changes to Failed. I'm using Modest with Nokia Messaging (and always have). I switched tree mode off, which restarts Modest, sent a new e-mail and it was sent within seconds.

I had a search for this issue and couldn't find someone with the same problem, and it isn't listed in bugs.maemo.org either.
 
woody14619's Avatar
Posts: 1,455 | Thanked: 3,309 times | Joined on Dec 2009 @ Rochester, NY
#5159
Originally Posted by travla View Post
I have been unable to send e-mails via Modest when using Tree View mode, is this possible?
I use tree view mode all the time, mail sends just fine. Maybe it's a setting wrong on your SMTP service?
 

The Following 2 Users Say Thank You to woody14619 For This Useful Post:
travla's Avatar
Posts: 397 | Thanked: 241 times | Joined on Mar 2010 @ Melbourne, Australia
#5160
Originally Posted by woody14619 View Post
I use tree view mode all the time, mail sends just fine. Maybe it's a setting wrong on your SMTP service?
I thought the same, but I double checked every setting, and they were correct; I have 4 e-mails linked to Nokia Messaging. But what I don't understand is the problem will only appear if I switch to Tree View mode.
 
Closed Thread

Tags
community ssu, f**k nokia, fremantle, maemo 5, nokia-who?, portrait mode, rotate, task-switcher, update, upgrade


 
Forum Jump


All times are GMT. The time now is 13:36.