No sound or wifi widget

my z2 with lollipop has lost widgets of sound, gps, wifi, etc
so I don't have direct access o direct button on screen to silence my z2 or turn on/off my wifi
those buttons are essentials!!!!!

Please see this:
https://talk.sonymobile.com/t5/Xperia-Z2/silent-problem-after-upgrading-to-lollipop/m-p/965955#M2553...
And about widgets,lock screen widgets are gone.
All we have to decide is what to do with the time that is given to us - J.R.R. Tolkien

Similar Messages

Sound in a widget

I am trying to embed a sound in a widget for iBooks author.
The sound format is arc, extension is .m4a
The audio works fine in dashboard on a mac, and gives no errors importing into iBooks author, but fails to play once on the device. the iBook displays the message 'Cannot play audio file'.
Has anyone else expereiced htis problem?

okay I have version 6.02.325
Dumb question but I have to ask it...If the frame is paused how do I go in and un-pause it?Also, I may have caused the pause because I inserted a "button" on the slide so that the slide would not advance automatically. As you well know inserting a button and adding it to the top of your timeline making it clear in color sets it up as a pause button. Does that mean if I take that button out my audio will work? And if that makes my audio work will my slide then automatically advance to the next slide?
So many questions....

IPod 2nd gen on iOS 4.2.1 has no sound or wifi

Hi, I have an iPod touch 2nd gen on iOS 4.2.1 which has the following problems
1) sound does not play with or without headphones plugged in
2) if I try to play a song in iTunes it tries to play for one second then pauses and returns back to the playlist
3) games crash
4) no wifi routers appear (with or without hidden SSIDs, regardless of encryption on or off)
I've tried downgrading to iOS 4.1 and tried resetting, dfu, iTunes reset as a new iPod etc but no joy!
I also tried going back to iOS 2.2.1 which apparently is the most stable but that errored in iTunes
Any ideas?
Thanks!

Is this the wifi proble:
iOS: Wi-Fi or Bluetooth settings grayed out or dim
If not successful, an appointment at the Genius Bar of an Apple store is usually in order.
Apple Retail Store - Genius Bar
If you restored to factory settings/new iPod and still have the problem that indicates a hardware problem.
Make an appointment at the Genius Bar of an Apple store..
Apple Retail Store - Genius Bar

After ICS update, WiFi widget causes phone reboot

After installing the ICS update on my Xperia PRO USA unlocked model via PC Companion... when I turn off WiFi using the widget, it does so - it turns it off. When I use the widget again to turn WiFi back on, it causes my phone to reboot.
I don't seem to have this problem if I turn WiFi on and off inside the WiFi settings area. But using the widget is now broken for me.
Anyone else?
When I use this, to turn WiFi back on, the phone reboots:
When I use this, to turn WiFi back on, I have no problems:

Have you tried repairing the phone software via PC Companion?
http://www.sonymobile.com/gb/tools/pc-companion/
If it doesn't help I suggest that you contact your local support team to get your phone examined at an repair center.
- Community Manager Sony Xperia Support Forum
If you're new to our forums make sure that you have read our Discussion guidelines.
If you want to get in touch with the local support team for your country please visit our contact page.

Will a wifi widget be released for the status bar or is there already one that I don't know about??

I'm a new iphone user. I have an iphone 4. Maybe there is one as it is a common feature on smartphones. I probably just haven't found it but can someone steer me in the right direction please

crap I meant to select the answer from as most helpful and best .... Meg St._Clair. sorry accidentally selected my own . silly comp stalled at wrong time.

How to get the sound to play in a widget through an LMS?

Mac operating systerm
Captivate 6
I have files that are aggregated. My reporting is set to SCORM 1.2. I know my project is not SCORM compliant. My project plays and transitions when in the LMS however when I get to the widget for my history sections no sound is produced. I have two widgets that do not play sound. Is there something I can do to make the sound play? I've inserted the sound into the widgets as normal.
Please any advice would be appreciated.
Thanks,
Maree

okay I have version 6.02.325
Dumb question but I have to ask it...If the frame is paused how do I go in and un-pause it?Also, I may have caused the pause because I inserted a "button" on the slide so that the slide would not advance automatically. As you well know inserting a button and adding it to the top of your timeline making it clear in color sets it up as a pause button. Does that mean if I take that button out my audio will work? And if that makes my audio work will my slide then automatically advance to the next slide?
So many questions....

[SOLVED] awesomewm vicious.widgets.wifi returns nil

I cant seem to figure out why the returning args (all of them) are nil..
this is the widget code I have:
wifiwidget = wibox.widget.textbox()
vicious.register(wifiwidget, vicious.widgets.wifi,
function( widget, args)
return string.format("%.8s - %sdB", args[1], args[7])
end, 19, "wlp2s0")
although, i feel thats not the culprit because regardless of what i put there, every entry in args[] is nil.
I have iwconfig installed and it returns the correct information for wlp2s0
vicious wifi script is in /usr/share/lua/5.2/vicious/widgets
any thoughts or further info needed?
Last edited by pdizzle (2014-10-02 13:18:42)

resolved...
in the case of the wifi widget, the returned value is a table.
so to call the values i was looking for it should be formatted:
wifiwidget = wibox.widget.textbox()
vicious.register(wifiwidget, vicious.widgets.wifi,
function( widget, args)
return string.format("%.8s - %sdB", args["{ssid}"], args["{sign}"])
end, 19, "wlp2s0")

Awesome systray is not showing all icons, perhaps overlapping widgets?

I have a problem with my Awesome configuration that results in some of the icons being missing or partially missing from my systray. I suspect this is because of some overlapping, since they are partially hidden. You can see the problem in the top right corner.
rc.lua:
-- Standard awesome library
require("awful")
require("awful.autofocus")
require("awful.rules")
-- Theme handling library
require("beautiful")
-- Notification library
require("naughty")
--Wiget Library
require("vicious")
-- awesoMPD Widget
--require("awesompd/awesompd")
-- {{{ Variable definitions
-- Themes define colours, icons, and wallpapers
beautiful.init("/usr/share/awesome/themes/blind-alien/theme.lua")
-- This is used later as the default terminal and editor to run.
terminal = "urxvt"
editor = os.getenv("EDITOR") or "vim"
editor_cmd = terminal .. " -e " .. editor
-- Enable or disable widgets:
-- You also have to edit the wiboxes!
useSysInfo = true
usePacman = true
useMpd = true
useWifi = false
useNet = true
useBat = false
useCpu = true
useMem = true
useTemp = false
-- Widget Settings
cpuCores = 2 --Number of CPU Cores
thermalZone = "coretemp.0" --Thermal Zone to read cpu temperature from (check vicious docu)
thermalData = "core" --Data Source: "proc", "core" or "sys"
netAdapter = "eth0" --Network adapter to monitor
wifiAdapter = "wlan0" --Wifi adapter for wifi widget
pacUpdate = "yaourt -Sy" --Command to update pacman cache
pacUpgrade = "yaourt -Su" --Command to upgrade system
networkManager = terminal .. " -e wicd-curses"
battery = "BAT1" --Battery to monitor
widthMpd = 420 --Width of MPD widget
-- Widget update intervals in seconds
updateCpu = 1
updatePac = 1801
updateMpd = 1
updateWifi = 7
updateNet = 1
updateBat = 31
updateMem = 7
-- For Dual-Screen setups:
-- Set "dualScreen" to "2" if you want a different, optimized widget layout for every screen.
-- If you set it to "-1" it will copy the same widget layout to both screens. (default Awesome behavior)
dualScreen = -1
screencount = screen.count()
-- Default modkey.
-- Usually, Mod4 is the key with a logo between Control and Alt.
-- If you do not like this or do not have such a key,
-- I suggest you to remap Mod4 to another key using xmodmap or other tools.
-- However, you can use another modifier like Mod1, but it may interact with others.
modkey = "Mod4"
-- Table of layouts to cover with awful.layout.inc, order matters.
layouts =
awful.layout.suit.tile,
awful.layout.suit.tile.left,
awful.layout.suit.tile.bottom,
awful.layout.suit.tile.top,
awful.layout.suit.fair,
awful.layout.suit.fair.horizontal,
awful.layout.suit.magnifier,
awful.layout.suit.floating,
awful.layout.suit.max
-- {{{ Tags
-- Define a tag table which will hold all screen tags.
tags = {
--names = { "1", "2", "3", "4", "5", "6"},
--names = { "⌘", "♐", "⌥", "ℵ"},
--names = { "⠪", "⠫", "⠬", "⠭", "⠮", "⠳"},
names = { "⠐", "⠡", "⠪", "⠵", "⠻", "⠿" },
--names = { " ∙", "⠡", "⠲", "⠵", "⠻", "⠿"},
--names = { " ⠐ ", " ⠡ ", " ⠲ ", " ⠵ ", " ⠾ ", " ⠿ "},
--names = { "⢷", "⣨", "⡪", "⣌", "⣪", "⡝"},
layout = {
layouts[8], layouts[8], layouts[8], layouts[5], layouts[8], layouts[8]
for s = 1, screencount do
tags[s] = awful.tag(tags.names, s, tags.layout)
end
-- {{{ Menu
-- Create a laucher widget and a main menu
myawesomemenu = {
{ "manual", terminal .. " -e man awesome" },
{ "edit config", editor_cmd .. " " .. awful.util.getdir("config") .. "/rc.lua" },
{ "restart WM", awesome.restart },
{ "logout", awesome.quit },
{ "shutdown" , "sudo /sbin/halt -p" },
{ "reboot" , "sudo /sbin/reboot" }
myinternet = {
{ "Chromium", "chromium" },
{ "Firefox" , "firefox" },
{ "IM" , "pidgin" },
{ "IRC" , "xchat"}
mymedia = {
{ "Spotify", "spotify" },
{ "Rhythmbox", "rhythmbox" },
{ "ncmpcpp", "urxvt -e ncmpcpp" },
{ "Gnome Mplayer", "gnome-mplayer" },
{ "VLC" , "vlc" }
mygraphics = {
{ "GIMP" , "gimp" },
{ "Inkscape" , "inkscape" },
{ "Image viewer" , "eog" }
myoffice = {
{ "Base" , "lobase" },
{ "Calc" , "localc" },
{ "Impress" , "loimpress" },
{ "LibreOffice" , "loffice" },
{ "Writer" , "lowriter" },
{ "Lyx" , "lyx" },
{ "Document viewer" , "evince" }
mysystem = {
{ "htop" , "urxvt -e htop" },
{ "Partition" , "gksudo gparted" },
{ "Sys mon" , "gnome-system-monitor" }
myutilities = {
{ "Gedit" , "gedit" },
{ "Virtualbox" , "VirtualBox" },
{ "File Manager" , "nautilus --no-desktop" }
myplaces = {
{ "Home" , "nautilus --no-desktop /home/johan/" },
{ "Documents" , "nautilus --no-desktop /home/johan/Documents/" },
{ "Downloads" , "nautilus --no-desktop /home/johan/Downloads/" },
{ "Music" , "nautilus --no-desktop /home/johan/Music/" },
{ "Pictures" , "nautilus --no-desktop /home/johan/Pictures/" }
myserverplaces = {
{ "Server root" , "nautilus --no-desktop /srv/" },
{ "Downloads" , "nautilus --no-desktop /srv/download/" },
{ "Movies" , "nautilus --no-desktop /srv/movies/" },
{ "Tv-Series" , "nautilus --no-desktop /srv/tv-series/" },
{ "Misc" , "nautilus --no-desktop /srv/misc/" }
mymainmenu = awful.menu({ items = {
{ "Terminal", terminal },
{ "Places" , myplaces },
{ "Server" , myserverplaces },
{ "Internet" , myinternet },
{ "Media" , mymedia },
{ "Graphics" , mygraphics },
{ "Office" , myoffice },
{ "Utilities" , myutilities },
{ "Systools" , mysystem },
{ "Awesome", myawesomemenu }
mylauncher = awful.widget.launcher({ image = image(beautiful.awesome_icon),
menu = mymainmenu })
-- Separators
bubble = widget({ type = "textbox" })
spacer = widget({ type = "textbox" })
space = widget({ type = "textbox" })
separator = widget({ type = "textbox" })
bracketl = widget({ type = "textbox" })
bracketr = widget({ type = "textbox" })
vertline = widget({ type = "textbox" })
dash = widget({ type = "textbox" })
bubble.text = " ∘ "
spacer.text = " "
space.text = " "
--separator.text = " ⡾ "
separator.text = "] ["
vertline.text = "|"
dash.text = "-"
bracketl.text = "["
bracketr.text = "]"
-- Status Labels
cpuLabel = {}
for s = 1, cpuCores do
cpuLabel[s] = widget({ type = "textbox" })
cpuLabel[s].text = "Core " .. s
end
rlabel = widget({ type = "textbox" })
rlabel.text = "Root:"
hlabel = widget({ type = "textbox" })
hlabel.text = "Home:"
-- WIDGETS --
-- OS info
if useSysInfo == true then
sys = widget({ type = "textbox" })
vicious.register(sys, vicious.widgets.os, "$1 $2")
end
-- Pacman updates
if usePacman == true then
-- Widget
pnoghosticon = widget({ type = "imagebox" })
pnoghosticon.image = image(beautiful.widget_pacnoghost)
pnoghosticon.visible = true
pghosticon = awful.widget.launcher({
image = beautiful.widget_pacghost,
command = terminal .. " -e " .. pacUpgrade .. " && echo -e 'vicious.force({ pacup, })' | awesome-client"
pghosticon.visible = false
-- Icon
-- picon = widget({ type = "imagebox" })
-- picon.image = image(beautiful.widget_pacnew)
-- Use the Pacman icon as launcher to update the package list (change to fit your package-management system)
picon = awful.widget.launcher({
image = beautiful.widget_pacnew,
command = pacUpdate .. " && echo -e 'vicious.force({ pacup, })' | awesome-client"
runpicon = awful.widget.launcher({
image = beautiful.widget_pacman_run,
command = pacUpdate .. " && echo -e 'vicious.force({ pacup, })' | awesome-client"
runpicon.visible = false
pacup = widget({ type = "textbox" })
vicious.register(pacup, vicious.widgets.pkg,
function(widget, args)
local nr = tonumber(args[1])
if nr ~= 0 then
pnoghosticon.visible = false
pghosticon.visible = true
picon.visible = false
runpicon.visible = true
else
pghosticon.visible = false
pnoghosticon.visible = true
runpicon.visible = false
picon.visible = true
end
end, updatePac, "Arch")
end
-- MPD Widget
if useMpd == true then
-- PLAY, STOP, PREV/NEXT Buttons
-- requires modification of /usr/share/awesome/lib/awful/widget/launcher.lua
-- b = util.table.join(w:buttons(), button({}, 1, nil, function () util.spawn(args.command) end))
-- to:
-- b = util.table.join(w:buttons(), button({}, 1, nil, function () util.spawn_with_shell(args.command) end))
music_play = awful.widget.launcher({
image = beautiful.widget_play,
command = "mpc toggle && echo -e 'vicious.force({ mpdwidget, })' | awesome-client"
music_pause = awful.widget.launcher({
image = beautiful.widget_pause,
command = "mpc toggle && echo -e 'vicious.force({ mpdwidget, })' | awesome-client"
music_pause.visible = false
music_stop = awful.widget.launcher({
image = beautiful.widget_stop,
command = "mpc stop && echo -e 'vicious.force({ mpdwidget, })' | awesome-client"
music_prev = awful.widget.launcher({
image = beautiful.widget_prev,
command = "mpc prev && echo -e 'vicious.force({ mpdwidget, })' | awesome-client"
music_next = awful.widget.launcher({
image = beautiful.widget_next,
command = "mpc next && echo -e 'vicious.force({ mpdwidget, })' | awesome-client"
mpdicon = widget({ type = "imagebox" })
mpdicon.image = image(beautiful.widget_mpd)
-- Initialize widget
mpdwidget = widget({ type = "textbox" })
--mpdwidget.wrap = "none"
mpdwidget.width = widthMpd
--mpdwidget.wrap = "word_char"
-- Register Widget
--vicious.register(mpdwidget, vicious.widgets.mpd, "(${state}) : ${Artist} - ${Title} ]", 13)
-- Set the maximum width of the MPD widget inside the string.format function as "%.<length>s"
vicious.register(mpdwidget, vicious.widgets.mpd,
function(widget, args)
--local maxlength = 85
local font = beautiful.font
local string = args["{Artist}"] .. " - " .. args["{Title}"]
--local string = "[" .. args["{state}"] .. "]" .. " : " .. args["{Artist}"] .. " - " .. args["{Title}"]
--[[ if maxlength < string.len(string) then
return "" .. string.sub(string, 0, maxlength-6) .. " ..."
else
return "" .. string .. ""
end]]
if args["{state}"] == "Play" then
music_play.visible = false
music_pause.visible = true
else
music_play.visible = true
music_pause.visible = false
end
return string
end, updateMpd)
end
---- WIFI Widget
--if useWifi == true then
-- wifiwidget = widget({ type = "textbox" })
-- wifiwidget.width = 22
-- wifiwidget.align = "right"
-- --wifiimage = widget({ type = "imagebox" })
-- wifiimage0 = awful.widget.launcher({
-- image = beautiful.widget_wifi0,
-- command = networkManager
-- wifiimage0.image.visible = true
-- wifiimage1 = awful.widget.launcher({
-- image = beautiful.widget_wifi1,
-- command = networkManager
-- wifiimage1.image.visible = false
-- wifiimage2 = awful.widget.launcher({
-- image = beautiful.widget_wifi2,
-- command = networkManager
-- wifiimage2.image.visible = false
-- wifiimage3 = awful.widget.launcher({
-- image = beautiful.widget_wifi3,
-- command = networkManager
-- wifiimage3.image.visible = false
-- wifiimage4 = awful.widget.launcher({
-- image = beautiful.widget_wifi4,
-- command = networkManager
-- wifiimage4.image.visible = false
-- -- Register Widget
-- -- change to the desired network adapter if needed
-- --vicious.register(wifiwidget, vicious.widgets.wifi, "~ ${link}%", 5, "wlan0")
-- vicious.register(wifiwidget, vicious.widgets.wifi,
-- function(widget, args)
-- if tonumber(args["{link}"]) > 75 then
-- wifiimage0.visible = false
-- wifiimage1.visible = false
-- wifiimage2.visible = false
-- wifiimage3.visible = false
-- wifiimage4.visible = true
-- elseif tonumber(args["{link}"]) > 50 then
-- wifiimage0.visible = false
-- wifiimage1.visible = false
-- wifiimage2.visible = false
-- wifiimage3.visible = true
-- wifiimage4.visible = false
-- elseif tonumber(args["{link}"]) > 25 then
-- wifiimage0.visible = false
-- wifiimage1.visible = false
-- wifiimage2.visible = true
-- wifiimage3.visible = false
-- wifiimage4.visible = false
-- elseif tonumber(args["{link}"]) > 0 then
-- wifiimage0.visible = false
-- wifiimage1.visible = true
-- wifiimage2.visible = false
-- wifiimage3.visible = false
-- wifiimage4.visible = false
-- else
-- wifiimage0.visible = true
-- wifiimage1.visible = false
-- wifiimage2.visible = false
-- wifiimage3.visible = false
-- wifiimage4.visible = false
-- end
-- return string.format("%02d%%", tonumber(args["{link}"]))
-- end, updateWifi, wifiAdapter)
--end
-- NETWORK Widget
if useNet == true then
dnicon = widget({ type = "imagebox" })
upicon = widget({ type = "imagebox" })
dnicon.image = image(beautiful.widget_down)
upicon.image = image(beautiful.widget_up)
-- Initialize widget
netdnwidget = widget({ type = "textbox" })
netdnwidget.width = 55
--netdnwidget.align = "right"
netupwidget = widget({ type = "textbox" })
netupwidget.width = 55
--netupwidget.align = "right"
-- Register widget
-- change to the desired network adapter if needed
--vicious.register(netdnwidget, vicious.widgets.net, "${eth0 down_kb} kB/s", 1)
--vicious.register(netupwidget, vicious.widgets.net, "${eth0 up_kb} kB/s", 1)
-- The following code formats the output to fill with zeroes at the beginning i.e. 013 kB/s instead of 13 kB/s.
-- It also automatically switches to MB/s if there is more than 999 kB/s
vicious.register(netdnwidget, vicious.widgets.net,
function(widget, args)
if tonumber(args["{" .. netAdapter .. " down_kb}"]) > 999 then
return string.format("%04.1f MB/s", tonumber(args["{" .. netAdapter .. " down_mb}"]))
else
return string.format("%03d kB/s", tonumber(args["{" .. netAdapter .. " down_kb}"]))
end
end, updateNet)
vicious.register(netupwidget, vicious.widgets.net,
function(widget, args)
if tonumber(args["{" .. netAdapter .. " up_kb}"]) > 999 then
return string.format("%04.1f MB/s", tonumber(args["{" .. netAdapter .. " up_mb}"]))
else
return string.format("%03d kB/s", tonumber(args["{" .. netAdapter .. " up_kb}"]))
end
end, updateNet)
end
---- BATTERY widget
--if useBat == true then
-- baticon = widget({ type = "imagebox" })
-- --baticon.image = image(beautiful.widget_batfull)
-- --Initialize widget
-- batwidget = widget({ type = "textbox" })
-- batwidget.width = 22
-- batwidget.align = "right"
-- --Register widget
-- --vicious.register(batwidget, vicious.widgets.bat, "$1$2", 31, "BAT1")
-- vicious.register(batwidget, vicious.widgets.bat,
-- function(widget, args)
-- if string.match(args[1], "[+↯]") then
-- baticon.image = image(beautiful.widget_ac)
-- elseif tonumber(args[2]) > 40 then
-- baticon.image = image(beautiful.widget_batfull)
-- elseif tonumber(args[2]) > 20 then
-- baticon.image = image(beautiful.widget_batlow)
-- else
-- baticon.image = image(beautiful.widget_batempty)
-- end
-- if tonumber(args[2]) == 100 then
-- return "Full"
-- end
-- return args[2] .. "%"
-- end, updateBat, battery)
--end
-- {{{ CPU
--if useTemp == true then
-- -- Core Temp
-- tempwidget = widget({ type = "textbox" })
-- tempwidget.width = 26
-- tempwidget.align = "right"
-- vicious.register(tempwidget, vicious.widgets.thermal, "$1 C", updateCpu, { thermalZone, thermalData })
-- --vicious.register(tempwidget, vicious.widgets.thermal, "$1°C", 5, { "thermal_zone0", "sys" })
-- -- Icon
-- tempicon = widget({ type = "imagebox" })
-- tempicon.image = image(beautiful.widget_temp)
--end
-- Readout
if useCpu == true then
-- Icon
cpuicon = widget({ type = "imagebox" })
cpuicon.image = image(beautiful.widget_cpu)
-- Core 1 Meter
cpubar = {}
freq = {}
displayCores = {}
displayCpu = {}
for s = 1, cpuCores do
cpubar[s] = awful.widget.progressbar()
cpubar[s]:set_width(50)
cpubar[s]:set_height(6)
cpubar[s]:set_vertical(false)
cpubar[s]:set_background_color("#434343")
--cpubar:set_color(beautiful.fg_normal)
cpubar[s]:set_gradient_colors({ beautiful.fg_normal, beautiful.fg_normal, beautiful.fg_normal, beautiful.bar })
--Delete the following line if you want to put the widget on the left side of the wibox
cpubar[s].layout = awful.widget.layout.horizontal.rightleft
vicious.register(cpubar[s], vicious.widgets.cpu, "$" .. s, updateCpu)
awful.widget.layout.margins[cpubar[s].widget] = { top = 6 }
-- Frequency
freq[s] = widget({ type = "textbox" })
freq[s].width = 44
freq[s].align = "right"
--vicious.register(freq1, vicious.widgets.cpufreq, "$2 GHz", 9, "cpu0")
vicious.register(freq[s], vicious.widgets.cpufreq,
function(widget, args)
return string.format("%03.1f GHz", args[2])
end, updateCpu, "cpu" .. s - 1)
-- Cache that shit
vicious.cache(vicious.widgets.cpu)
end
end
-- }}} CPU
-- {{{ MEM
if useMem == true then
-- Icon
memicon = widget({ type = "imagebox" })
memicon.image = image(beautiful.widget_mem)
-- Percentage
--mem = widget({ type = "textbox" })
--vicious.register(mem, vicious.widgets.mem, "$1%")
-- Meter
membar = awful.widget.progressbar()
membar:set_width(50)
membar:set_height(6)
membar:set_vertical(false)
membar:set_background_color("#434343")
--membar:set_color(beautiful.fg_normal )
membar:set_gradient_colors({ beautiful.fg_normal, beautiful.fg_normal, beautiful.fg_normal, beautiful.bar })
--This bar should be placed on the right side of the wibox unless
--it's a dual-screen config in which case the default (leftright)
--layout is used... change that if you need!
if screencount ~= dualScreen then
membar.layout = awful.widget.layout.horizontal.rightleft
end
--Register the widget
vicious.register(membar, vicious.widgets.mem, "$1", updateMem)
-- Align progressbars
awful.widget.layout.margins[membar.widget] = { top = 6 }
-- MEM Usage
--mem_total = widget({ type = "textbox" })
--vicious.register(mem_total, vicious.widgets.mem, "$3 MB", 9)
--mem_used = widget({ type = "textbox" })
--vicious.register(mem_total, vicious.widgets.mem, "$2 MB", 9,)
-- Cache that shit
vicious.cache(vicious.widgets.mem)
end
-- }}} MEM
-- Create a textclock widget
mytextclock = awful.widget.textclock({ align = "right" }, "%H:%M")
awful.widget.layout.margins[mytextclock] = { top = -1 }
-- Create a systray
mysystray = widget({ type = "systray"})
-- Create a wibox for each screen and add it
mywibox = {}
mybottomwibox = {}
mypromptbox = {}
mylayoutbox = {}
mytaglist = {}
mytaglist.buttons = awful.util.table.join(awful.button({}, 1, awful.tag.viewonly),
awful.button({ modkey }, 1, awful.client.movetotag),
awful.button({}, 3, awful.tag.viewtoggle),
awful.button({ modkey }, 3, awful.client.toggletag),
awful.button({}, 4, awful.tag.viewnext),
awful.button({}, 5, awful.tag.viewprev))
mytasklist = {}
mytasklist.buttons = awful.util.table.join(awful.button({}, 1, function(c)
if not c:isvisible() then
awful.tag.viewonly(c:tags()[1])
end
client.focus = c
c:raise()
end),
awful.button({}, 3, function()
if instance then
instance:hide()
instance = nil
else
instance = awful.menu.clients({ width = 250 })
end
end),
awful.button({}, 4, function()
awful.client.focus.byidx(1)
if client.focus then client.focus:raise() end
end),
awful.button({}, 5, function()
awful.client.focus.byidx(-1)
if client.focus then client.focus:raise() end
end))
for s = 1, screencount do
-- Set a screen margin for borders
awful.screen.padding(screen[s], { top = 0 })
-- Create a promptbox for each screen
mypromptbox[s] = awful.widget.prompt()
-- Create an imagebox widget which will contains an icon indicating which layout we're using.
-- We need one layoutbox per screen.
mylayoutbox[s] = awful.widget.layoutbox(s)
mylayoutbox[s]:buttons(awful.util.table.join(awful.button({}, 1, function() awful.layout.inc(layouts, 1) end),
awful.button({}, 3, function() awful.layout.inc(layouts, -1) end),
awful.button({}, 4, function() awful.layout.inc(layouts, 1) end),
awful.button({}, 5, function() awful.layout.inc(layouts, -1) end)))
mylayoutbox[s].resize = false
-- Create a taglist widget
mytaglist[s] = awful.widget.taglist(s, awful.widget.taglist.label.all, mytaglist.buttons)
awful.widget.layout.margins[mytaglist[s]] = { top = -2 }
-- WARNING: In order to properly view the tasklist some lua files have been modified. For the
-- tasklist_floating_icon icon to be placed on the left side of the task name instead of the
-- right alignment, /usr/share/awesome/lib/awful/widget/tasklist.lua in function new(label, buttons) the
-- variable widgets.textbox has to be modified like this:
-- remove bg_align = "right" and
-- modify the left margin from 2 to icon width + 2 (i.e.: 18).
-- Create a tasklist widget
mytasklist[s] = awful.widget.tasklist(function(c)
return awful.widget.tasklist.label.currenttags(c, s,
-- WARNING: Requires modified /usr/share/awesome/lib/awful/widget/tasklist.lua !!!
-- This basically hides the application icons on the tasklist. If you don't want this or
-- prefer not to change your tasklist.lua remove the following line!
{ hide_icon = true })
end, mytasklist.buttons)
awful.widget.layout.margins[mytasklist[s]] = { top = 2 }
-- WIBOXES --
-- Here we create the wiboxes if it's not a dual-screen layout
if screencount ~= dualScreen then
-- Create the wibox
mywibox[s] = awful.wibox({ position = "top", screen = s, border_width = 0, height = 18 })
-- Add widgets to the wibox - order matters
mywibox[s].widgets = {
mytaglist[s],
mypromptbox[s],
displaySysInfo,
layout = awful.widget.layout.horizontal.leftright
mytextclock,
mylayoutbox[s],
s == 1 and mysystray or nil,
mytasklist[s],
layout = awful.widget.layout.horizontal.rightleft
mybottomwibox[s] = awful.wibox({ position = "bottom", screen = s, border_width = 0, height = 18 })
mybottomwibox[s].widgets = {
space, music_play, music_pause, music_stop, music_prev, music_next, space, mpdwidget,
layout = awful.widget.layout.horizontal.leftright
spacer,
bracketr,
-- spacer, batwidget, spacer, baticon, spacer,
-- separator,
-- spacer, wifiwidget, spacer, wifiimage0, wifiimage1, wifiimage2, wifiimage3, wifiimage4, spacer,
-- separator,
-- spacer, tempwidget, spacer, tempicon, spacer,
-- separator,
spacer, freq[1], spacer, cpubar[1], spacer,
--cpuLabel[1], spacer,
cpuicon, spacer,
separator,
spacer, membar, spacer, memicon, spacer,
separator,
spacer, netupwidget, spacer, upicon, spacer, separator, spacer, netdnwidget, spacer, dnicon, spacer,
separator,
space, pghosticon, pnoghosticon, runpicon, picon, space,
bracketl,
layout = awful.widget.layout.horizontal.rightleft
end
end
if screencount == dualScreen then
-- Here we create the wiboxes if it is a dual screen configuration:
mywibox[1] = awful.wibox({ position = "top", screen = 1, border_width = 0, height = 18 })
-- Add widgets to the wibox - order matters
mywibox[1].widgets = {
mytaglist[1],
spacer,
mypromptbox[1],
mytasklist[1],
layout = awful.widget.layout.horizontal.leftright
spacer,
mytextclock,
-- spacer,
mylayoutbox[1],
-- spacer,
-- mytasklist[1],
layout = awful.widget.layout.horizontal.rightleft
mybottomwibox[1] = awful.wibox({ position = "bottom", screen = 1, border_width = 0, height = 18 })
mybottomwibox[1].widgets = {
space, music_play, music_pause, music_stop, music_prev, music_next, space, mpdwidget,
layout = awful.widget.layout.horizontal.leftright
space,
s == 1 and mysystray or nil,
layout = awful.widget.layout.horizontal.rightleft
mywibox[2] = awful.wibox({ position = "top", screen = 2, border_width = 0, height = 18 })
mywibox[2].widgets = {
space,
mytaglist[2],
spacer,
mypromptbox[2],
layout = awful.widget.layout.horizontal.leftright
spacer,
mytextclock,
space,
mylayoutbox[2],
spacer,
mytasklist[2],
layout = awful.widget.layout.horizontal.rightleft
mybottomwibox[2] = awful.wibox({ position = "bottom", screen = 2, border_width = 0, height = 18 })
mybottomwibox[2].widgets = {
spacer,
bracketl,
spacer, sys, spacer,
separator,
space, runpicon, picon, pghosticon, pnoghosticon, space,
separator,
spacer, dnicon, spacer, netdnwidget, spacer, separator, spacer, upicon, spacer, netupwidget, spacer,
separator,
spacer, memicon, spacer, membar, spacer,
bracketr,
layout = awful.widget.layout.horizontal.leftright
spacer,
bracketr,
spacer, tempwidget, spacer, tempicon, spacer,
separator,
spacer, freq[2], spacer, cpubar[2], spacer,
cpuLabel[2], spacer,
cpuicon, spacer,
separator,
spacer, freq[1], spacer, cpubar[1], spacer,
cpuLabel[1], spacer,
cpuicon, spacer,
bracketl,
layout = awful.widget.layout.horizontal.rightleft
end
-- {{{ Mouse bindings
root.buttons(awful.util.table.join(awful.button({}, 3, function() mymainmenu:toggle() end),
awful.button({}, 4, awful.tag.viewnext),
awful.button({}, 5, awful.tag.viewprev)))
-- {{{ Key bindings
globalkeys = awful.util.table.join(awful.key({ modkey, }, "Left", awful.tag.viewprev),
awful.key({ }, "Print", function () awful.util.spawn("gnome-screenshot") end),
awful.key({ modkey, }, "Right", awful.tag.viewnext),
awful.key({ modkey, }, "Escape", awful.tag.history.restore),
awful.key({ modkey, }, "j",
function()
awful.client.focus.byidx(1)
if client.focus then client.focus:raise() end
end),
awful.key({ modkey, }, "k",
function()
awful.client.focus.byidx(-1)
if client.focus then client.focus:raise() end
end),
awful.key({ modkey, }, "w", function() mymainmenu:show({ keygrabber = true }) end),
--Volume manipulation
-- awful.key({}, "XF86AudioRaiseVolume", function() awful.util.spawn("amixer set Master 5+") end),
-- awful.key({}, "XF86AudioLowerVolume", function() awful.util.spawn("amixer set Master 5-") end),
-- Layout manipulation
awful.key({ modkey, "Shift" }, "j", function() awful.client.swap.byidx(1) end),
awful.key({ modkey, "Shift" }, "k", function() awful.client.swap.byidx(-1) end),
awful.key({ modkey, "Control" }, "j", function() awful.screen.focus_relative(1) end),
awful.key({ modkey, "Control" }, "k", function() awful.screen.focus_relative(-1) end),
awful.key({ modkey, }, "u", awful.client.urgent.jumpto),
awful.key({ modkey, }, "Tab",
function()
awful.client.focus.history.previous()
if client.focus then
client.focus:raise()
end
end),
-- Standard program
awful.key({ modkey, }, "Return", function() awful.util.spawn(terminal) end),
awful.key({ modkey, "Control" }, "r", awesome.restart),
awful.key({ modkey, "Shift" }, "q", awesome.quit),
awful.key({ modkey, }, "l", function() awful.tag.incmwfact(0.05) end),
awful.key({ modkey, }, "h", function() awful.tag.incmwfact(-0.05) end),
awful.key({ modkey, "Shift" }, "h", function() awful.tag.incnmaster(1) end),
awful.key({ modkey, "Shift" }, "l", function() awful.tag.incnmaster(-1) end),
awful.key({ modkey, "Control" }, "h", function() awful.tag.incncol(1) end),
awful.key({ modkey, "Control" }, "l", function() awful.tag.incncol(-1) end),
awful.key({ modkey, }, "space", function() awful.layout.inc(layouts, 1) end),
awful.key({ modkey, "Shift" }, "space", function() awful.layout.inc(layouts, -1) end),
-- Prompt
awful.key({ modkey }, "r", function() mypromptbox[mouse.screen]:run() end),
awful.key({ modkey }, "x",
function()
awful.prompt.run({ prompt = "Run Lua code: " },
mypromptbox[mouse.screen].widget,
awful.util.eval, nil,
awful.util.getdir("cache") .. "/history_eval")
end))
clientkeys = awful.util.table.join(awful.key({ modkey, }, "f", function(c) c.fullscreen = not c.fullscreen end),
awful.key({ modkey, }, "q", function(c) c:kill() end),
awful.key({ modkey, "Control" }, "space", awful.client.floating.toggle),
awful.key({ modkey, "Control" }, "Return", function(c) c:swap(awful.client.getmaster()) end),
awful.key({ modkey, }, "o", awful.client.movetoscreen),
awful.key({ modkey, "Shift" }, "m", function () awful.util.spawn("urxvt -T ncmpcpp -e 'ncmpcpp'") end),
awful.key({ modkey, "Shift" }, "w", function () awful.util.spawn("chromium") end),
awful.key({ modkey, }, "b", function () awful.util.spawn("nautilus --no-desktop") end),
awful.key({ modkey, "Shift" }, "r", function(c) c:redraw() end),
awful.key({ modkey, }, "t", function(c) c.ontop = not c.ontop end),
awful.key({ modkey, }, "n", function(c) c.minimized = not c.minimized end),
awful.key({ modkey, }, "m",
function(c)
c.maximized_horizontal = not c.maximized_horizontal
c.maximized_vertical = not c.maximized_vertical
end))
-- Compute the maximum number of digit we need, limited to 9
keynumber = 0
for s = 1, screencount do
keynumber = math.min(9, math.max(#tags[s], keynumber));
end
-- Bind all key numbers to tags.
-- Be careful: we use keycodes to make it works on any keyboard layout.
-- This should map on the top row of your keyboard, usually 1 to 9.
for i = 1, keynumber do
globalkeys = awful.util.table.join(globalkeys,
awful.key({ modkey }, "#" .. i + 9,
function()
local screen = mouse.screen
if tags[screen][i] then
awful.tag.viewonly(tags[screen][i])
end
end),
awful.key({ modkey, "Control" }, "#" .. i + 9,
function()
local screen = mouse.screen
if tags[screen][i] then
awful.tag.viewtoggle(tags[screen][i])
end
end),
awful.key({ modkey, "Shift" }, "#" .. i + 9,
function()
if client.focus and tags[client.focus.screen][i] then
awful.client.movetotag(tags[client.focus.screen][i])
end
end),
awful.key({ modkey, "Control", "Shift" }, "#" .. i + 9,
function()
if client.focus and tags[client.focus.screen][i] then
awful.client.toggletag(tags[client.focus.screen][i])
end
end))
end
clientbuttons = awful.util.table.join(awful.button({}, 1, function(c) client.focus = c; c:raise() end),
awful.button({ modkey }, 1, awful.mouse.client.move),
awful.button({ modkey }, 3, awful.mouse.client.resize))
-- Set keys
root.keys(globalkeys)
-- {{{ Rules
awful.rules.rules = {
-- All clients will match this rule.
rule = {},
properties = {
border_width = beautiful.border_width,
border_color = beautiful.border_normal,
size_hints_honor = false,
focus = true,
keys = clientkeys,
buttons = clientbuttons
rule = { class = "MPlayer" },
properties = { floating = true }
rule = { class = "pinentry" },
properties = { floating = true }
rule = { class = "gimp" },
properties = { floating = true }
{ rule = { class = "firefox" },
properties = { tag = tags[1][2] } },
{ rule = { class = "Chromium" },
properties = { tag = tags[1][2] } },
{ rule = { class = "Pidgin" },
properties = { tag = tags[1][3] } },
{ rule = { class = "Xchat" },
properties = {tag = tags[1][4] } },
-- Set Firefox to always map on tags number 2 of screen 1.
-- { rule = { class = "Firefox" },
-- properties = { tag = tags[1][2] } },
-- {{{ Signals
-- Signal function to execute when a new client appears.
client.add_signal("manage", function(c, startup)
-- Add a titlebar
-- awful.titlebar.add(c, { modkey = modkey })
-- Enable sloppy focus
c:add_signal("mouse::enter", function(c)
if awful.layout.get(c.screen) ~= awful.layout.suit.magnifier
and awful.client.focus.filter(c) then
client.focus = c
end
end)
if not startup then
-- Set the windows at the slave,
-- i.e. put it at the end of others instead of setting it master.
-- awful.client.setslave(c)
-- Put windows in a smart way, only if they does not set an initial position.
if not c.size_hints.user_position and not c.size_hints.program_position then
awful.placement.no_overlap(c)
awful.placement.no_offscreen(c)
end
end
end)
client.add_signal("focus", function(c) c.border_color = beautiful.border_focus end)
client.add_signal("unfocus", function(c) c.border_color = beautiful.border_normal end)
-- {{{ Tag signal handler - selection
-- - ASCII tags 1 [2] 3 4...
-- - start with tag 1 named [1] in tag setup
for s = 1, screencount do
for t = 1, #tags[s] do
tags[s][t]:add_signal("property::selected", function ()
if tags[s][t].selected then
tags[s][t].name = "[" .. tags[s][t].name .. "]"
else--]]
--tags[s][t].name = tags[s][t].name:gsub("[%[%]]", "")
--[[ end
end)
end
end
I have tried to search around for a solution to this, but I am coming up short. Any idea on how to solve this?
Last edited by kveras (2011-11-21 09:01:47)

First of all, did you check the wiki and forums? We'll help you, but you have to try to fix it yourself first.
You will need to provide more info if you want help.
Did you set up Gnome to force fallback mode?
Did you look at the Gnome wiki article? There's a few sections that sound like what your looking to do, but the examples are USING OTHER WM's. They still might be able to point you in the right direction.

HT1222 I have a Bose Sound link which no longer connects to iTunes for 64 bit, what to do?

I have just installed Windows 8.1 64 bit and then up graded iTunes to 64 bit but my Bose Sound Link (wifi) will now not connect to my computer.

I am all sorted. The Sound Link Air Digital Music System needed to be reset. Followed the manual instructions and now all is good

No sound / audio after 10.8.5 update

I just updated updated my iMac's OSX to 10.8.5 from the app store, it asked for a restart to complete the update, i clicked restart and it said it there was a error so the update wawsnt complete. After restart, there is no sound. I went to the system preferences, and there's no audio device. I downloaded the combo update from the apple site and it also failed, this is what i got after trying 4 times.
Same thing happened with my 10.8.3 update, since then, my wifi hasnt been working, i'm stuck with the cable now and i cant afford to backup everything and have a fresh OSX installation. Please help me with my sound and wifi, i really need the sound badly, i make music, Pleeease help
(27inch, Late 2012) 3.4 GHz Intel Core i7, 32 GB 1600 MHz DDR3, NVIDIA GeForce GTX 680MX 2048 MB, OS X 10.8.5 (12F37)

You really need to have at least 2 backups as you are risking losing all your data.
First check to see what version of 10.8 you have installed.  menu/About this Mac.
You can reinstall the OS from the Recovery Volume and it shouldn't affect your data files. Boot to the Recovery Volume (command - R on a restart) or hold down the option key during a restart and select Recovery Volume. Run Disk Utility Verify/Repair and Repair Permissions. Then reinstall the OS.
OS X Recovery
OS X Recovery (2)

Apple TV wifi speakers

Can I stream visual to my TV using apple TV and sound to wifi speakers at the same time.
This is easy for itunes, but for browser stuff like iplayer can this be done?

airfoil will play any audio from the computer to all devices which support airplay
wireless speakers is a useless term
some wireless speakers have a dongle one have to connect to the device and it make the normal analog signal wireless and the speaker then recieve it
some wireless speakers use the sonos system
some wireless speakers use the logitech squeese box system
and I'm sure tons of others have their own system too think samsung and likely sony have a wireless speaker std.
so if you use airfoil you can play audio out of appletv's and airport express with speakers or stereos connected
or other systems which support airplay

I want to add sound to pictures, please help.

Hi i would like to add some sound to a widget, so when i get the right answer, it play the sound. Thanks

I think what you desire is a triggered event ---- mentioned earlier in the forum...I tried to find implementation of this and made no progress...maybe others can point a way forward......

IPod Touch 4g says "No Wifi"

I can't even get into the Wifi widget.

Try out following tip.
http://support.apple.com/kb/TS1559?viewlocale=en_US&locale=en_US
-- kaz-k

Nokia N8 Customer's experience [Pros, Cons, and Ti...

   I am a Fan and Nokia user since the release of Nokia 3310, then Nokia N37, then Nokia 5230, and now Nokia N8. when I see the history of improvements that Nokia did achieve so far I feel glad to be a Nokia fan and user, and when I look for the future I hope for more and more.
   I got my N8 almost 6 days ago; this phone is extremely powerful cellphone, it really in a level to compete with iphone. I was lucky to have mine as a second batch, and it does not have any problem so far , only it restarted once and hanged once and this was due to the over limit multi-tasking which I did in purpose to test the ability of the phone and to know experimentally the limit of the processor.
   This is my experience summary about my N8:
Pros*:
1- Simbian^3 is a very powerful improvement to Nokia’s history, it is really fast. The processor is working fast even with such a good operating system.
2- Multi home screens and widgets are very powerful feature.
3- Contacts list had improved very well.
4- Messaging and Social networks had improved very much.
5- Photos and Videos editor had received a very excellent improvement.
6- Web browser is very fast in the second batch (Same speed as Opera 10).
7- The music player was improved very much (since the N73).
8- The GPS was improved, and connects quickly to satellite.
9- The ability to assign different themes to each profile mode is a very cool feature.
10- The screen visibility and quality is very good even under direct sunlight.
11- Sound quality is very good (however if it had 2 speakers like my N73, it would be a good addition).
12- The ability to use USB keys is very powerful, and I really enjoyed using this feature.
13- USB charging is very good, I wish Nokia standardize it in all its new phones.
14- HDMI connection is a very extent addition, especially when you do have a BT mouse and keyboard with the HDTV home theatre one, as if you are using your laptop.
15- Gaming experience is very good, especially if you connect it to TV with the HDMI.
16- OVI store offers a good pack of apps, hopefully it will expand in the near future.
Cons*:
1- Simbian^3 is little bit sophisticated.
2- No customized equalizer in the music player (I don’t like the Nokia standard equalizer sets).
3- The FM transmitter does not support the GPS voice guidance, only music player.
4- The WiFi widget has some problems to turn off the WiFi (It is not a one step process; I wish Nokia fix it quickly).
5- When watching a movie, the menu key does not dim or turn off, I should hide it with my hand.
6- Only 3 home screens (I wish it has n number of customizable home screens).
7- Keyboard is very retarded in the vertical mood (multi letter for each key is not likely to exist with touch screens, they should replace it with a full keyboard mood even with the number rows).
8- Keyboard is very tight in the horizontal mood (Also it is confusing for the people who used to use S60^5th ed touch) [I wish if the numbers are displayed in the top as a fourth row, as my language (Arabic with English letters) has numbers as equivalent missingletters in the English alphabet, so it is painful to such back and forth between number mood and letter mood].
9- Only the Nokia default languages are the only set of languages for the phone (I hope one day, Nokia allow customers to select their suitable language packs, as the screen is touch and Nokia will not need to customize a set of letters on numerical pads as in N73).
10- The camera is 2x zoom only (I wish that extended zoom could be applied to boost it up to 6x with the 3 mp resolution as it was in the N73 when selecting less resolution option we get more zoom). Also there is no way to silent the camera sound nor the red light of the capture, my Samsung digital camera has it. Also no sequence picture support.
11- The display resolution is poor; more pixels would make it better. I know that a higher resolution means a faster processor, means a much powerful battery.
12- Battery life is not enough (One day with high usage. ie. music & GPS all the day + some Wifi).
13- 16 gb is not enough specially with apps that can reach over 100mb in the near future.
14- The speaker position on the back cover is not good, when the phone is on the table, the sound is blocked.
15- The plastic covers of the top and bottom is a big disadvantage (it could break for sure if it felt on its tip), as it would be better if it was aluminum and leave the top black part only plastic for the antenna functionality, or merge the antenna in the casing body as in the iphone.
     All in all, this phone is a good step from Nokia in its learning and improving experience, I would like Nokia to learn from the costumer’s experience, and listen to their suggestions and requests for improvements. Nokia is Nokia I know, but learning from “others” will save Nokia time and money to improve and to be creative in adding new ideas instead of being just in the average area. I believe that Nokia will take back the lead in the cellphones creativity as it was with the announcement of the first N-series device 4 years ago.
*Future Pros and Cons will be added as I get more experience with N8

You are very lucky you don't care about email. For those of us who want to make Blackberry users jealous, the N8 experience is a humiliation.
If you call your prejudices standards, please lower them.

N8 = 480 euros worth of fail

Long time Nokia user. Started in 1996 with their banana phone, used 9200/9300i/E70/72/75/90 and now I bought a Nokia N8. Since I've had it, i had nothing but problems.
1. Wifi on the phone is mediocre. There is no simple off button and it takes 20 million menus to turn everything off but wait ... the phone still reconnects without me wanting it. Then you start configuring each widget and untick days on your e-mail accounts. You say you succeeded but wait ... the Nokia N8 phone reconnects yet again to your wifi network. Then you go back in the menu and sub menus and options and advanced settings and you turn everything off again and you disconnect manually from your hotspot ... but wait the phone reconnects again to your router. Now, the only option you have is ... delete destination.
2. You take your brand new toy to work and want to hook up to your corporate wifi network. You swipe to the second screen, tap your wifi widget to enable scanning, select your network, configure, open the nokia browser and the phone freezes. You look at it and give it a few seconds. Then you push the menu button and load the task manager. You click X on the browser, nothing. You click close all nothing. You press the menu button again and ... the phone is not responding. You are left with the power button. You push the power button, hold of 8 seconds and wait for the phone to switch off. Phone switches off, you give it a minute, turn it back on but it gets stuck on the Nokia logo. You wait 2 minutes and what happens? The screen saver kicks in. You unlock the phone, its the nokia logo. You lock the phone, its the screen saver. You reset the phone again. This time it works like a charm but reconnects to wifi whenever it wants not whenever you want. None of the solutions here on the board worked. Having it hog my service provided contract is not an option.
3. Theme effects are better viewed off. Putting them on simply ruins the UI experience on this phone. Use the phone a bit with theme effects on and at one point you have 2-3 menus in overlay mode and you cannot make heads or tails. Swiping with theme effects is poor and you are better off with the button to change home screens.
4. Favourite contact carousel. Good idea, poorly done. I have 4 main contacts, Superman, Batman, Julia and Bruce. I want to call John who is number 6, i swipe with my finger and call John. Afterwards, I want to return the carousel to the 4 contacts I call more often: Superman, Bartman, Julia and Bruce. I use my finger to swipe these 4 contacts into place, release the finger, the carousel moves on its own and shows other contacts. I try again with my finger, position these 4 contacts to the millimetre, release finger and the carousel moves again. After I manage to put my 4 contacts, I reboot the phone and the carousel shows other contacts not the 4 I left before I rebooted.
5. Image gallery. I have 100 pictures. Swiping from pic 1 to pic 2 pic 3 is all good. Swiping from pic 100 to pic 99 to pic 98 is good. Swiping from pic 1 backwards to pic 100 shows a double jump in transition. People on other boards have said this is the Nokia way of showing that you are at the end of the gallery. If this is true, Nokia engineers ran out of ideas. Jumping like that between the first and last picture makes you cringe. The animation seems broken!
6. Light sensor. A mind of its own really. You set it one way, it ends up in another. You hold the phone in your hand without having changes in light conditions and the phone changes its brightness on its own.
7. Nokia N8 and OVI Suite. A lethal duo. Crash after crash after crash. OVI crashes 2-3 times a day and formatiing doesn't help.
8. Camera. Impressive, fast, accurate, interface is 10 years old. I made the mistake of enabling "save location". My phone drove me crazy with the GPS. Every 2 seconds " Define access point, define access point, define access point?" I kept saying NO but the phone ignored me.
9. E-MAIL Client. Back to the drawing board guys. Not efficient and badly done. I would use the web interface but the browser is not good either. Try writing in landscape mode an e-mail on an outlook web access account. The layout is so bad you cannot even arrange the text in a decent manner. That landscape keyboard has got to go.
10. Ovi Store App on the phone. Slow and often fails to sign in eventhough you have proper internet.
11. Third party apps. Gravity is the only app worth praising, the Nokia social needs to go too. I bought quick office full and look at the attachments what happens.
I can say one thing. If the coming updates do not make this phone work the way it is intended and for the price I paid, I will sell it on eBay and jump ship like most of the symbian users. Now I understand why Nokia's market share is in tatters. My blind loyalty for this company kept me with this N8 and I should not compromise so much for the money I paid.
P.S: I have the latest updates on it, including the one that came out yesterday.
Attachments:
Scr000008.jpg ‏41 KB
Scr000010.jpg ‏107 KB
Scr000012.jpg ‏108 KB

Ok dude, I understand your frustration. Thats why i said you are always welcome to switch the board. I have no gain in defending N8 or Nokia. It is not my point. I read your post and I saw your phone history, it was fully comprised of E series devices and iPhone.
Ok, If you are not aware, N8 is not a flagship device from Nokia, It is Nokia's Imaging Flagship and there is no denial in the fact that N8 is the best camera phone available to date, I bought N8 only for its imaging capabilities and i never expect a DSLR quality in it, I just want it to replace a point and shoot, so that i can carry my camera with me always. It Does what i wanted. I know there are Number of Unhappy N8 users too.
"Some users report that their Nokia N8 would crash when connected to a Wi-Fi network secured with WPA2 (that didn’t happen with our unit though). They suggested switching off Power saving to remedy the problem.........
....Performance near the router improved for both N modes – it went from about -8% to 10% on the positive side....
That’s still not a huge improvement over Wireless G, but it answers why the Nokia N8 was the only phone losing speed near the router when using Wireless N. Performance away from the router remained the same though"
"However further away from the router, it was the Nokia N8 that came on top. Although it didn't show much benefit from the Wireless N mode, the N8 had the most consistent throughput (between 10 and 14 Mbps) that kept its pace from all locations and in all test modes"
GSM ARENA: Its a nice article comparing the WiFi modes of all phones with N band (including iPhone) it tels you about the router settings and the functionality of WiFi n- band (http://www.gsmarena.com/wireless_n_bluetooth_3_speed_test-review-551.php)
I hope it will give you some insight of the problem or at least the impression that I'm aware of the problem. I have read so many forums, and i know a bit about the frustrations too.
This review (it is all about connectivity) http://www.fonearena.com/blog/26520/nokia-n8-review-week-%E2%80%93-day-7-%E2%80%93-connectivity.html will give you more idea about the problem.
Wishmaker
"This cameraphone point on the N8 is moot because I did not buy the phone just for the camera. Let's assume for the sake of argument that I agree with you, what about the issues i've mentioned. I want to use this device for other things than taking pictures"
I was using an HTC desire and i bought N8 for its camera, I'm pretty happy with it. I was aware that N8 is not gonna give me the better browser, or the seamless social networking integration before i bought the phone, I was ready to sacrifice it because of the camera. I know its not the same for all users, And certainly Nokia knows it, thats why they have C6-01, C7 and E7 (Not released yet though) all running in S^3 to address the problem.
Wishmaker
"You are telling me to find a work around to overcome basic functionality problems? What are we, the 90s where the end user had to put a tin foil on his head and pray to god that it works? Wifi is like SMS nowadays"
How are you using your iPhone, without the bumper or with the bumper? Do you really need a Bumper to use a phone? - I'm not trying to put the iPhone down here, What i say is people do compromises and workarounds to use even the expected phone function of a phone. So why can't you find a workaround to use it for sometime. In N8's case the problem can be sorted out with a firmware update (Hopefully it will), but in the other case, it will never be.
mate, you got me wrong, My smartphone adoption started with 6600 (Symbian first edition), I was really tired off with the Symbian after some time (playing with 6630, SE P900, 7610), then i purposefully chose a series 40 (to stay away from smart phone). I switched to WinMO 6.1 then after annoyed with the UI, came to Symbian^1 aka V5 (5800). It was full of double tap single tap nonsenses (I loved the phone though and I'm still using it), i was frustrated more than you and i switched to android. Used HTC desire, wildfire (for about 2 months only) then I came back to S^3. i didn't try iPhone only because i don't like the icon centric design of iOS. Before to jump into S^3 my serious consideration was WP7 (i didn't coz WM6.1 really spoiled me, only alternative to the functionality of WM6.1 is Symbian, you will never get what you want in Android or WP7 after using WM6.1). I say this because to let you know that i have a little background in Smartphone OS too. I know whats wrong with S^3. I will say S^3 is the first touchscreen OS from Symbian (Not the UI) Because S^1 is not at all a touch OS, the OS itself. It was just a translation from D-Pad. I consider S^3 equal to android cupcake in 2009. So I'm giving it a fair chance to prove itself.
S^3 is not ready yet. For example, In call log, it miss the feature "filter by this number", Just because S^3 cant select something, Press and hold popup menu should have it, but the filter is there in the option, you cant select so you don't have filter by selected. There are so many glitches, including the WiFi auto connect. S^1 or any other Symbian controls the connection from within app, S^3 has kind of a universal connection, (its not closed as S^1 or open as iOS or Android, its a hybrid approach, But S^3 didn't get it correct, it gives the priority to some apps (especially email app) than the system settings). S^3 is Complete as a multimedia OS (thats why Nokia released it in N series). its not yet ready for the corporate computing (thats why they pushed the E7 release - E series was never my boat, Because i don't need what they offer).
If you want More understanding about N-Series and E-Series Wikipedia is a nice place.
The Nokia Eseries consists of business-oriented smartphones, with emphasis on enhanced connectivity and support for corporate e-mail push services. All devices have advanced office features. Phones equipped with Wireless LAN also provide a VoIP client (SIP Protocol).
Nokia Nseries is a product family that includes multimedia smartphones. These are mobile devices supporting digital multimedia services such as music playback, video capture, photography, mobile gaming and Internet services. Some Nseries devices support high-speed wireless technology, such as 3G, or Wireless LAN.
A little more in to it:
The numbers describe the traits of the phone -N7x - 7 series are the balanced phones. they have balanced features and are the cheapest Nseries phones -N8x - 8 series are the camera phones (except N90 and N93) -N9x - 9 series are the high end part of the Nseries
Wishmaker
"Playing games, taking pictures, filming, HDMI and listening to music? These are the only things that the N8 does right. If by your definition, the phone is defined by these major features then you are not doing this board justice"
Unfortunately that is what turns out to be the focus of N8 as per the branding.
I know what i bought, and I have no complain, If some one don't know what he bought and complain (Like my grinder doesn't play video) it is totally insane.
I'm sorry if I sounded harsh, but that is the truth. otherwise there are no point in branding, Numbering and so on. Nokia can also have a one ultimate product, a superpower almighty and Keep on investing only in that. That is not the goal, You can find a device that is suitable for you in Nokia's product line, if you don't like it, you have other options.
Finally I give Damian Dinning (if you don't know, he is one of the man behind the superb camera of N8) words here
"What may not be right for you doesn't mean it's rubbish. That would be like me saying that a 2-seater sports car is useless and therefore rubbish because I can't get four people in it. What was the manufacturer thinking of!? Probably that there are some people who that's all they want. For me (as much as I would like a sports car) it's simply not practical (due to two young children), but I don't go around telling others it’s bad. It wasn’t designed with me in mind, that’s all"
".....But if you’re not one of them, that's OK. I hope in our portfolio of products there will be one which suits your needs better. ........."
".....If we still don’t have a product that fits your needs, on to point 5…
You can find the rest here: http://conversations.nokia.com/2010/11/23/damian-dinning-on-nokias-full-focus-cameras/
Sorry pal, I don't wanna undermine you, What you say are problems, for sure, I too Hope they will get fixed soon, I too Frustrated in times, But lets first understand these things and try to adopt them. We are frustrated because we don't understand what Nokia are aiming at, We all think that N8 is a "Flag ship" from Nokia so it should be an iPhone killer, No it is not, It is not the ultimate (N9 may sometimes, or it may also turn out to be a geek's phone - more unlikely)
It is not personal, so don't get a grudge, if you want to continue a healthy discussion ya we may, I will try to do this board justice

No sound or wifi widget

Similar Messages

Maybe you are looking for