Sony experia z3 dual screen problem. (not cracked)
The problem with my phone is the touch screen isn't working. It works sometimes but only a little and I have to press down hard. And even then its registering the touch on a different part of the screen. The screen also doesn't sit flush on the phone. In the top left corner the screen is raise up a bit. I'm stationed in the middle east and everyone wants $240 to fix it!! Any help would be appreciated thanks
Sorry to hear this but you would need to either return your device to the place of purchase or contact Xperia care and have your device inspected http://www.sonymobile.com/global-en/support/contact-us/
For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled. Richard P. Feynman
Similar Messages
-
I dropped my iphone 4 off my balcony. The screen is not cracked at all, but when it happened, the screen had discolored bars on it, and now it doesn't even turn on anymore. Is there any other solution other than buying another?
Try holding down the on/off and home buttons at the same time until you see the Apple logo. If you are still having problems take it to and Apple store for repair.
-
Sony Ericsson Vivaz touch screen problem
I have a sony ericsson vivaz bought on nov 2010. It was working perfectly fine till last two months...... I startd noticing touch screen problem on top left part.. while typing messages in querty mode, i cant select caps ON button.. instead it displays"Z" on the screen. I tried to calibrate. but i could not start it as my top left part is not sensing any input.. what shal i do??
how much wil it cost to repair it??
Im frm India.try
Update Service (SUS)
http://www.sonymobile.com/gb/tools/update-service/
http://www-support-downloads.sonymobile.com/Software%20Downloads/Update_Service_Setup-2.11.12.5.exe
Don't forget to mark the Correct Answers & Helpful Answers
"I'd rather be hated for who I am, than loved for who I am not." Kurt Cobain (1967-1994) -
Dual screen problems after last updates
Hello everyone,
it was long time since our Arch gave me some problems, but then now I'm fighting furiously with dual screen configuration with new gnome. Let me explain.
I upgraded the home PC that I hadn't update for months, so I updated more or less everything ... kernel, nvidia drivers, gnome, etc..
The PC has always been dual screen (no twin view, without xinerama), two screens (one on a LCD monitor and one on a TV) where I could run separate applications independent.
Now, after the update, when I launch any application in the second screen (the TV) it starts on the first (screen).
Obviously I have't made any changes to xorg.conf before and after the upgrade. I also tried to recreate one with the nvidia-tools but nothing ...
Can you help me? Someone had the same problem?
I post my xorg.conf, I hope that someone has a hint. I can no longer watching movies on TV and it is very annoying!
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 1.0 (buildmeister@builder63) Wed Oct 1 15:10:25 PDT 2008
# Auto-generated by Archie mkxcfg
# Auto-generated by Archie mkxcfg
#Section "DRI"
# Mode 0666
#EndSection
Section "ServerLayout"
# PS/2 Mouse not detected
# Serial Mouse not detected
Identifier "Xorg Configured"
Screen 0 "Screen0" 1024 0
Screen 1 "Screen1" LeftOf "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "USB Mouse" "CorePointer"
EndSection
Section "Files"
# Additional fonts: Locale, Gimp, TTF...
# FontPath "/usr/share/lib/X11/fonts/latin2/75dpi"
# FontPath "/usr/share/lib/X11/fonts/latin2/100dpi"
# True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc:unscaled"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/PEX"
FontPath "/usr/share/fonts/cyrillic"
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/ttf/western"
FontPath "/usr/share/fonts/ttf/decoratives"
FontPath "/usr/share/fonts/truetype"
FontPath "/usr/share/fonts/truetype/openoffice"
FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
FontPath "/usr/share/fonts/latex-ttf-fonts"
FontPath "/usr/share/fonts/defoma/CID"
FontPath "/usr/share/fonts/defoma/TrueType"
EndSection
Section "Module"
# Load "type1"
Load "ddc" # ddc probing of monitor
Load "dbe"
# Load "dri"
Load "extmod"
Load "glx"
Load "bitmap" # bitmap-fonts
Load "freetype"
Load "record"
# Load "synaptics"
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail" "true"
Option "Xinerama" "0"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "it"
Option "XkbVariant" ""
EndSection
Section "InputDevice"
Identifier "Serial Mouse"
Driver "mouse"
Option "Protocol" "Microsoft"
Option "Device" "/dev/ttyS0"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "PS/2 Mouse"
Driver "mouse"
Option "Protocol" "auto"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "USB Mouse"
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "SendCoreEvents" "true"
Option "Protocol" "IMPS/2"
Option "ZAxisMapping" "4 5"
Option "Buttons" "5"
EndSection
Section "Monitor"
# Warning: This may fry old Monitors
# Very conservative. May flicker.
# VertRefresh 50.0 - 62.0 # Extreme conservative. Will flicker. TFT default.
# Default modes distilled from
# "VESA and Industry Standards and Guide for Computer Display Monitor
# Timing", version 1.0, revision 0.8, adopted September 17, 1998.
# $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
# 640x350 @ 85Hz (VESA) hsync: 37.9kHz
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Samsung SyncMaster"
HorizSync 30.0 - 81.0
VertRefresh 56.0 - 75.0
ModeLine "640x350" 31.5 640 672 736 832 350 382 385 445 +hsync -vsync
ModeLine "640x400" 31.5 640 672 736 832 400 401 404 445 -hsync +vsync
ModeLine "720x400" 35.5 720 756 828 936 400 401 404 446 -hsync +vsync
ModeLine "640x480" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
ModeLine "640x480" 31.5 640 664 704 832 480 489 491 520 -hsync -vsync
ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -hsync -vsync
ModeLine "640x480" 36.0 640 696 752 832 480 481 484 509 -hsync -vsync
ModeLine "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
ModeLine "800x600" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
ModeLine "800x600" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
ModeLine "800x600" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
ModeLine "800x600" 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync
ModeLine "1024x768" 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync interlace
ModeLine "1024x768" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
ModeLine "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
ModeLine "1024x768" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
ModeLine "1024x768" 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
ModeLine "1152x864" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
ModeLine "1280x960" 108.0 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync
ModeLine "1280x960" 148.5 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync
ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
ModeLine "1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
ModeLine "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
ModeLine "1600x1200" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1600x1200" 175.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1600x1200" 189.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1600x1200" 229.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
ModeLine "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
ModeLine "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
ModeLine "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
ModeLine "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
ModeLine "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
ModeLine "1800x1440" 230.0 1800 1896 2088 2392 1440 1441 1444 1490 +hsync +vsync
ModeLine "1800x1440" 250.0 1800 1896 2088 2392 1440 1441 1444 1490 +hsync +vsync
ModeLine "640x480" 43.2 640 680 744 848 480 481 484 509 -hsync +vsync
ModeLine "768x576" 35.0 768 792 872 976 576 577 580 597 -hsync +vsync
ModeLine "768x576" 42.9 768 800 880 992 576 577 580 601 -hsync +vsync
ModeLine "768x576" 45.5 768 808 888 1008 576 577 580 602 -hsync +vsync
ModeLine "768x576" 51.8 768 808 888 1008 576 577 580 605 -hsync +vsync
ModeLine "768x576" 62.6 768 816 896 1024 576 577 580 611 -hsync +vsync
ModeLine "800x600" 68.2 800 848 936 1072 600 601 604 636 -hsync +vsync
ModeLine "1024x768" 113.3 1024 1096 1208 1392 768 769 772 814 -hsync +vsync
ModeLine "1152x864" 81.6 1152 1216 1336 1520 864 865 868 895 -hsync +vsync
ModeLine "1152x864" 119.7 1152 1224 1352 1552 864 865 868 907 -hsync +vsync
ModeLine "1152x864" 143.5 1152 1232 1360 1568 864 865 868 915 -hsync +vsync
ModeLine "1280x960" 124.5 1280 1368 1504 1728 960 961 964 1001 -hsync +vsync
ModeLine "1280x960" 129.9 1280 1368 1504 1728 960 961 964 1002 -hsync +vsync
ModeLine "1280x960" 179.0 1280 1376 1520 1760 960 961 964 1017 -hsync +vsync
ModeLine "1280x1024" 191.0 1280 1376 1520 1760 1024 1025 1028 1085 -hsync +vsync
ModeLine "1400x1050" 122.6 1400 1488 1640 1880 1050 1051 1054 1087 -hsync +vsync
ModeLine "1400x1050" 149.3 1400 1496 1648 1896 1050 1051 1054 1094 -hsync +vsync
ModeLine "1400x1050" 155.8 1400 1496 1648 1896 1050 1051 1054 1096 -hsync +vsync
ModeLine "1400x1050" 179.3 1400 1504 1656 1912 1050 1051 1054 1103 -hsync +vsync
ModeLine "1400x1050" 214.4 1400 1512 1664 1928 1050 1051 1054 1112 -hsync +vsync
ModeLine "1600x1200" 280.6 1600 1728 1904 2208 1200 1201 1204 1271 -hsync +vsync
Option "DPMS" "true"
# HorizSync 28.0 - 78.0 # Warning: This may fry very old Monitors
EndSection
Section "Monitor"
Identifier "Monitor1"
VendorName "Unknown"
ModelName "TV-0"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
EndSection
Section "Device"
Identifier "Card0"
Driver "nvidia"
VendorName "All"
BoardName "All"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 7300 LE"
BusID "PCI:4:0:0"
Screen 0
EndSection
Section "Device"
Identifier "Videocard1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 7300 LE"
BusID "PCI:4:0:0"
Screen 1
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 7300 LE"
BusID "PCI:4:0:0"
Screen 0
EndSection
Section "Device"
Identifier "Device1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 7300 LE"
BusID "PCI:4:0:0"
Screen 1
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "0"
Option "TwinViewXineramaInfoOrder" "CRT-0"
Option "metamodes" "CRT: 1280x1024 +0+0; CRT: 1024x768 +0+0; CRT: 800x600 +0+0; CRT: 640x480 +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
# Removed Option "metamodes" "TV: nvidia-auto-select +0+0"
Identifier "Screen1"
Device "Device1"
Monitor "Monitor1"
DefaultDepth 24
Option "TwinView" "0"
Option "TwinViewXineramaInfoOrder" "TV-0"
Option "metamodes" "TV: 1024x768 +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Writing the post a tried to install fluxbox, and then... all ok. In fluxbox all works fine. I think this is a problem related to the new gnome screen configurer.
I post an image of gnome screen configurer vs nvidia-tools.
Googling around I found that new gnome screen configuration (using xrandr) is not compatible with nvidia drivers. Could be this the source of the problem?
Help please
Last edited by frullino (2008-10-25 13:17:29)Hi,
Does your Mac go to the sleep status when you close the cover? If so, the remote session can be terminated due to time out and the time out value may be redesigned in the latest versions.
Thanks.
Jeremy Wu
TechNet Community Support -
Hd 6570 i gb dual screen problem
Good day all.
i have a problem with dual screens to my one pc. i am using a AMD Radeon HD 6570 gfx card. dual core 2.77ghz cpu and windows 7 professional 32 bit. The one screen is connected via VGA cable and the other screen is connected via DVI cable (no adapters) but the screens will only display individually and not as extended desktops.
i have updated the graphics driver to the latest as well as the CCC and still no sucess.
I know this is set up is possible because i have other pcs that are using VGA and DVI.
These are the specs of the pc
Windows version: windows 7 professional
64 or 32 bit : 32 bit
Power supply watts : 300w
Memory type, model number and amount: apacer 2 gb unb pc2-6400 cl5
VGA driver Version : 8.930.0.0
Chipset driver Version : 6.1.7600.16385
CPU : Pentium ( R ) dual core cpu E5400 @ 2.70 GHz
Bios version : V02.61
Gpu : hd 6570 1 gb
Your assistance will be greatly appreciatedPlease have a look at the AMD configurator for two or more screens on a video card.
http://www.amd.com/us/products/technologies/amd-eyefinity-technology/how-to/Pages/how-to.aspx
and
http://www.amd.com/us/products/technologies/amd-eyefinity-technology/how-to/Pages/set-up.aspx
Quote
To enable support for more than 2 monitors, “active” DisplayPort™ adapters/dongles are required (or monitors with direct DisplayPort™ connectivity must be used). -
TooltipText used with dual screen problem
Hi,
In my application I use a dual screen, so JComponent may be either on one screen or the other.
My problem is when the mouse rolls over a JComponent on the right screen, the Tooltiptext associated is displayed onto the left screen.
Any idea if I could display it automatically on the good screen or if I have to implement myself the display ?
Thx for advanceDid you get any resolution to your question? I have the Samsung monitor almost like yours, and I posted two seconds ago. I think I have a similar problem. I had been using my Samsung with my PC, and just switched to Mac. I loved my Samsung, but now ,for the first time using as a second. Hooked up to mini dvi to dvi, and reported a glow, or tinge coming around any window that I may place on the Samsung.Also, when Ilook at the background around the window I can see that the resolution is not perfect and is breaking up a little. Did you try VGA? and did it help? Curious to know
-
I have been using dual screens with no problems until I installed PS CS5. Now when I drag an image onto the secondary screen the canvas goes black as soon as I relsease the mouse. I can see the rulers etc. and when dragging across the diaplay the image can be seen but as soon as I 'let go' it's blacked out. The really frustrating thing is that this doesn't happen in AI or Dreamweaver (or indeed any other program!).
So far I have
Reset the monitors
when changed to show the same on both screens (clone) the image can be seen perfectly ok on both screens
when the secondary monitor is made the primary the problem remains (i.e. the PS image is blacked out on that monitor)
Checked for updates for the monitors (none needed)
Checked CS5 up to date (no updates required)
Checked for graphics card updates (none needed) - NVidia GeForce 8600 GTS
Uninstalled and re installed PS
Pointed in an annoyed manner at the useless window open on my secondary screen
Is there something simple that I have mistakenly chosen that is preventing the use of my secondary screen?Check to see if nVidia has released an updated driver for your hardware. Go to their web site to check.
Unfortunately, from my observations nVidia may have neglected to keep their driver quality up with later releases for the 8600 GT. I have reports from some of my own customers using my OpenGL software that the driver is troublesome, and have actually reported better results from an older driver version than the very latest release.
Other things you can try to work around the problem:
In Photoshop, Edit - Preferences - Performance, [Advanced...] and change to Basic mode.
Try disabling OpenGL drawing entirely. If that corrects the issue it's almost a certainty that the nVidia driver is at fault.
-Noel -
I just bought a 24 inch external monitor so i could dual screen on my imac. When I put it on the best resolution (1920x1080) the picture is roughly 2 inches to one side. I tried auto config but it has no effect. Any ideas?
just bought a dvi adaptor, fixed my problem
-
[SOLVED] dual-screen problem with awesome3.2 and firefox/gedit
Hi,
my problem is that firefox/gedit (+maybe other apps, i don't know yet) are starting in awesome like they are fullscreen apps. Firefox covers the wibox at the top of the screen, and even overlaps a bit to the seconds screen. So the keyboard-shortcuts doenst work well, because awesome then changes the tags in bots screens when on one tag firefox is opened.
I dont know why this happens, here is my rc.lua:
-- Load libraries
require("awful")
require("beautiful")
require("wicked")
-- {{{ Variable definitions
-- User styles for windows, statusbars, titlebars and widgets
theme_path = os.getenv("HOME") .. "/.config/awesome/themes/zenburn"
beautiful.init(theme_path)
-- Modifier keys
modkey = "Mod4" -- Super_L
-- Window titlebars
use_titlebar = true
-- Window management layouts
layouts = {
awful.layout.suit.tile, -- 1
awful.layout.suit.tile.left, -- 2
awful.layout.suit.tile.bottom, -- 3
awful.layout.suit.tile.top, -- 4
awful.layout.suit.fair, -- 5
awful.layout.suit.fair.horizontal, -- 6
awful.layout.suit.max, -- 7
-- awful.layout.suit.max.fullscreen, -- /
awful.layout.suit.magnifier, -- 8
awful.layout.suit.floating -- 9
-- Application specific behaviour
apprules = {
-- Class Instance Name Screen Tag Floating
{ "Firefox", nil, nil, nil, 2, false },
{ "Firefox", "Download", nil, nil, nil, true },
{ "Firefox", "Places", nil, nil, nil, true },
{ "Firefox", "Extension", nil, nil, nil, true },
{ "MPlayer", nil, nil, nil, nil, true },
{ nil, nil, "VLC media player", nil, nil, true },
{ "Gimp", nil, nil, nil, nil, true },
{ "Xmessage", "xmessage", nil, nil, nil, true },
{ "Skype", nil, nil, nil, 1, true },
{ "Pidgin", nil, nil, nil, 1, true },
-- {{{ Tags
-- Define tags table
tags = {}
tags.settings = {
{ name = "im", layout = layouts[9] },
{ name = "www", layout = layouts[1] },
{ name = "terms", layout = layouts[3] },
{ name = "dev", layout = layouts[3] },
{ name = "other", layout = layouts[5] },
-- Initialize tags
for s = 1, screen.count() do
tags[s] = {}
for i, v in ipairs(tags.settings) do
tags[s][i] = tag(v.name)
tags[s][i].screen = s
awful.tag.setproperty(tags[s][i], "layout", v.layout)
awful.tag.setproperty(tags[s][i], "setslave", v.setslave)
end
tags[s][1].selected = true
end
-- {{{ Wibox
-- Widgets configuration
-- Reusable separators
myspace = widget({ type = "textbox", name = "myspace", align = "right" })
myseparator = widget({ type = "textbox", name = "myseparator", align = "right" })
myspace.text = " "
myseparator.text = "|"
-- Date, time and...
mydateicon = widget({ type = "imagebox", name = "mydateicon", align = "right" })
mydateicon.image = image(beautiful.widget_date)
mydatewidget = widget({ type = "textbox", name = "mydatewidget", align = "right" })
wicked.register(mydatewidget, wicked.widgets.date, "%b %e, %R", 60)
-- a Calendar
function calendar_select(offset)
local datespec = os.date("*t")
datespec = datespec.year * 12 + datespec.month - 1 + offset
awful.util.spawn("cal -m " .. (datespec % 12 + 1) .. " " .. math.floor(datespec / 12) .. " | xmessage -geometry +1135+17 -file -")
end
mydatewidget:buttons({
button({ }, 1, function () calendar_select(0) end),
button({ }, 4, function () calendar_select(1) end),
button({ }, 5, function () calendar_select(-1) end)
-- System tray
mysystray = widget({ type = "systray", align = "right" })
-- Create a wibox and...
mywibox = {}
mypromptbox = {}
mylayoutbox = {}
mytaglist = {}
mytaglist.buttons = { button({ }, 1, awful.tag.viewonly),
button({ modkey }, 1, awful.client.movetotag),
button({ }, 3, function (tag) tag.selected = not tag.selected end),
button({ modkey }, 3, awful.client.toggletag),
button({ }, 4, awful.tag.viewnext),
button({ }, 5, awful.tag.viewprev) }
-- ...add it to each screen
for s = 1, screen.count() do
-- Create a promptbox
mypromptbox[s] = widget({ type = "textbox", align = "left" })
-- Create an imagebox widget with icons indicating active layout
mylayoutbox[s] = widget({ type = "imagebox", align = "left" })
mylayoutbox[s]:buttons({ button({ }, 1, function () awful.layout.inc(layouts, 1) end),
button({ }, 3, function () awful.layout.inc(layouts, -1) end),
button({ }, 4, function () awful.layout.inc(layouts, 1) end),
button({ }, 5, function () awful.layout.inc(layouts, -1) end) })
-- Create the taglist
mytaglist[s] = awful.widget.taglist.new(s, awful.widget.taglist.label.all, mytaglist.buttons)
-- Create the wibox
mywibox[s] = wibox({ position = "top", height = "14", fg = beautiful.fg_normal, bg = beautiful.bg_normal })
-- Add widgets to the wibox (order matters)
mywibox[s].widgets = { mylayoutbox[s],
mytaglist[s],
mypromptbox[s],
myspace,
mydateicon, mydatewidget,
myspace,
s == screen.count() and mysystray or nil
mywibox[s].screen = s
end
-- {{{ Mouse bindings
root.buttons({
button({ }, 4, awful.tag.viewnext),
button({ }, 5, awful.tag.viewprev)
-- {{{ Key bindings
globalkeys = {
-- Applications
key({ modkey }, "Return",function () awful.util.spawn("uxterm") end),
-- Prompt menus
key({ modkey }, "F2", function () awful.prompt.run({ prompt = "Run: " }, mypromptbox[mouse.screen],
awful.util.spawn, awful.completion.shell, awful.util.getdir("cache") .. "/history")
end),
-- Awesome controls
key({ modkey, "Shift" }, "q", awesome.quit),
key({ modkey, "Shift" }, "r", function () mypromptbox[mouse.screen].text = awful.util.escape(awful.util.restart()) end),
-- Layout manipulation
key({ modkey, "Shift" }, "Plus", function () awful.client.incwfact(-0.05) end),
key({ modkey, "Shift" }, "Minus", function () awful.client.incwfact(0.05) end),
key({ modkey }, "space", function () awful.layout.inc(layouts, 1) end),
key({ modkey, "Shift" }, "space", function () awful.layout.inc(layouts, -1) end),
-- Focus controls
key({ modkey }, "Tab", function () awful.client.focus.history.previous(); if client.focus then client.focus:raise() end end),
key({ modkey }, "Down", function () awful.client.focus.bydirection("down"); if client.focus then client.focus:raise() end end),
key({ modkey }, "Up", function () awful.client.focus.bydirection("up"); if client.focus then client.focus:raise() end end),
key({ modkey }, "Left", function () awful.client.focus.bydirection("left"); if client.focus then client.focus:raise() end end),
key({ modkey }, "Right", function () awful.client.focus.bydirection("right");if client.focus then client.focus:raise() end end),
key({ modkey, "Shift" }, "Down", function () awful.client.swap.bydirection("down") end),
key({ modkey, "Shift" }, "Up", function () awful.client.swap.bydirection("up") end),
key({ modkey, "Shift" }, "Left", function () awful.client.swap.bydirection("left") end),
key({ modkey, "Shift" }, "Right", function () awful.client.swap.bydirection("right") end),
-- Client manipulation
clientkeys = {
key({ modkey, "Control" }, "space", awful.client.floating.toggle),
-- Bind keyboard digits
keynumber = 0
for s = 1, screen.count() do
keynumber = math.min(9, math.max(#tags[s], keynumber));
end
-- Tag controls
for i = 1, keynumber do
table.insert(globalkeys,
key({ modkey }, i,
function ()
local screen = mouse.screen
if tags[screen][i] then
awful.tag.viewonly(tags[screen][i])
end
end))
table.insert(globalkeys,
key({ modkey, "Shift" }, i,
function ()
if client.focus and tags[client.focus.screen][i] then
awful.client.movetotag(tags[client.focus.screen][i])
end
end))
end
-- Set keys
root.keys(globalkeys)
-- {{{ Hooks
-- Hook function to execute when focusing a client
awful.hooks.focus.register(function (c)
if not awful.client.ismarked(c) then
c.border_color = beautiful.border_focus
end
end)
-- Hook function to execute when unfocusing a client
awful.hooks.unfocus.register(function (c)
if not awful.client.ismarked(c) then
c.border_color = beautiful.border_normal
end
end)
-- Hook function to execute when marking a client
awful.hooks.marked.register(function (c)
c.border_color = beautiful.border_marked
end)
-- Hook function to execute when unmarking a client
awful.hooks.unmarked.register(function (c)
c.border_color = beautiful.border_focus
end)
-- Hook function to execute when the mouse enters a client
awful.hooks.mouse_enter.register(function (c)
-- Sloppy focus (but disabled for magnifier layout)
if awful.layout.get(c.screen) ~= awful.layout.suit.magnifier
and awful.client.focus.filter(c) then
client.focus = c
end
end)
-- Hook function to execute when a new client appears
awful.hooks.manage.register(function (c)
-- If we are not managing this application at startup, move it to the screen where the mouse is
if not startup and awful.client.focus.filter(c) then
c.screen = mouse.screen
end
-- Add a titlebar to each client
if use_titlebar then
awful.titlebar.add(c, { modkey = modkey })
end
-- Set client mouse bindings
c:buttons({
button({ }, 1, function (c) client.focus = c; c:raise() end),
button({ modkey }, 1, awful.mouse.client.move),
button({ modkey }, 3, awful.mouse.client.resize)
-- New clients may not receive focus if they're not focusable, so set the border anyway
c.border_width = beautiful.border_width
c.border_color = beautiful.border_normal
-- Check application->screen/tag mappings and floating state
local target_screen
local target_tag
local target_float
for index, rule in pairs(apprules) do
if (((rule[1] == nil) or (c.class and c.class == rule[1]))
and ((rule[2] == nil) or (c.instance and c.instance == rule[2]))
and ((rule[3] == nil) or (c.name and string.find(c.name, rule[3], 1, true)))) then
target_screen = rule[4]
target_tag = rule[5]
target_float = rule[6]
end
end
-- Apply mappings, if any
if target_float then
awful.client.floating.set(c, target_float)
end
if target_screen then
c.screen = target_screen
awful.client.movetotag(tags[target_screen][target_tag], c)
end
-- Focus after tag mapping
client.focus = c
-- Set client key bindings
c:keys(clientkeys)
-- Put windows at the end of others instead of setting them as a master
--awful.client.setslave(c)
-- ...or do it selectively for certain tags
if awful.tag.getproperty(awful.tag.selected(mouse.screen), "setslave") then
awful.client.setslave(c)
end
-- New floating windows don't cover the wibox and don't overlap until it's unavoidable
awful.placement.no_offscreen(c)
--awful.placement.no_overlap(c)
-- Honoring size hints: false to remove gaps between windows
c.size_hints_honor = false
end)
-- Hook function to execute when arranging the screen
awful.hooks.arrange.register(function (screen)
-- Update layout imagebox widget with an icon indicating active layout
local layout = awful.layout.getname(awful.layout.get(screen))
if layout and beautiful["layout_" ..layout] then
mylayoutbox[screen].image = image(beautiful["layout_" .. layout])
else
mylayoutbox[screen].image = nil
end
-- Give focus to the latest client in history if no window has focus
-- or if the current window is a desktop or a dock one
if not client.focus then
local c = awful.client.focus.history.get(screen, 0)
if c then client.focus = c end
end
-- Fine grained border controls
local visible_clients = awful.client.visible(screen)
if #visible_clients > 0 then
for unused, current in pairs(visible_clients) do
-- Floating clients always have borders
if awful.client.floating.get(current) or (layout == 'floating') then
current.border_width = beautiful.border_width
-- Floating clients always on top
if not current.fullscreen then
current.ontop = true
end
-- Don't draw the border if there is only one tiled client visible
elseif (#visible_clients == 1) or (layout == 'max') then
visible_clients[1].border_width = 0
else
current.border_width = beautiful.border_width
end
end
end
end)
I added "xrandr --output DVI-1 -- right-of DVI-0" to the .xinitrc to get the extended desktop i want.
Any suggestions?
Last edited by Wishes (2009-03-29 10:52:00)Still the same
Edit: i deleted my ~/.mozilla folder. Now firefox starts not overlapping with the wibox, but still a bit overlapping to the other screen, so hat my keystrokes toggle both screens. it seems that it start in floating mode, because i can move it with the mouse. When i move it a bit towarts the wibox and a bit right, it seems to get stuck in the chosen tile-layout and everything is fine... until i quit firefox and start it again.
Edit2: Hmmm, ok, i think i found it... or at least something:
-- New floating windows don't cover the wibox and don't overlap until it's unavoidable
--awful.placement.no_offscreen(c) //THIS was first uncommented
awful.placement.no_overlap(c) //THIS was first commented
So now with no_overlap it seems to work finde (although i cannot move gedit between the screens with the mouse, but i dont know if this isn't normal. Firefox is moveable between the screens.), no overlapping anymore with the wibox or to the other screen.
When i uncomment both lines, firefox and gedit are starting both on the 2nd screen (the left one), and gedit cannot be moved to the right one (although firefox can be moved.).
Last edited by Wishes (2009-03-28 20:24:52) -
I'm trying to connect my iMac to a monitor using a DVI lead.
I can get my Macbook conencted, though it only seems to show 16 colors right now, however, when trying with the iMac, I don't get any mention of the second screen.
I had the same problem with the Macbook until I clicked the 'Gather Windows' button, but that is not showing on the iMac.
Message was edited by: MoonworksYou have answered your own question.
If you can get the TV to display 1920x1200, you can mirror that. But a LCD has a "Native resolution" and can't "fudge" a higher one. -
So yeah!! Any one can tell what should I do now? Should i open the case of the iphone and tweek the lcd cables back in place?
All they were asking is if someone could tell them what was wrong with it.......It sounds like your inner LCD screen cracked. I had the same problem. Mine was out of warrenty though so I actually bought the part off of Ebay and replaced it myself. The front screen and inner LCD are connected so you have to buy them the same way to fix it. It was like $28 and came with the tools. Just FYI. Obviously if you are in warrenty....have apple fix it.
-
I have the iphone 5
my lock button is broken
my screen is off set and i cannot type in my password to get into the phone and reset the phone
how or what do i have to do to fix this?
and im at work so i cant get the serial number to youmy lock button is broken
If your lock button is broken, the only solution is to get the phone replaced or repaired. There is no way to reset the phone without a functioning lock button.
and im at work so i cant get the serial number to you
This is a user to user tech support form, not Apple support. The S/N wouldn't provide any solution regardless. -
Sony Experia Neo V WIFI Problem
Hi,
I purchased my sony ericsson neo v in the singapore under a postpaid plan last nov. 2012. Now I am here in the philippines and a few days or a week ago I have problems connecting via wifi. The wife application always turns off everytime I turn it back on. I just upgraded to android 4.0 today and still got the same problem. Is it a hardware problem? Is this still under warranty and if so, where is the nearest sony service center?
Hope to receive feedback as soon as possible. Thanks!I suggest that you check if this problem could be related to some software glitch by reinstalling the phone software using SUS.
http://www.sonymobile.com/gb/tools/update-service/
If the same problem remains after software reinstall I suggest that you contact your local support team to have your phone examined at an repair center.
http://www.sonymobile.com/global-en/support/contact-us/contact-info/
- 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. -
Dual screen problem in 10.5.3
Hello all,
Wonder if anyone has a clue on this: since installing 10.5.3 on my MacBook Pro my second display will start running the screensaver as soon as plugged into the display port. The desktop of my MacBook Por is normal (ie no screensaver) and I set the energy settings control panel to never display the screensaver in all settings. Funny thing is the extra display functions normally, I can drag apps to it and work on it. In the background though the screensaver keeps rolling using up graphics power. Did I stumble into a 10.5.3 bug here or is there an easy fix to this? Thanks for your help! CheersUnless you're running Mac OS X 10.5 Server, you'll be more likely to get a quick and accurate answer if you ask in the Mac OS X 10.5 Leopard forum or perhaps in the MacBook Pro forum.
If you are indeed running Server on your MacBook Pro, please let us know.
Regards. -
My Sony experia C always alert of Roaming warning when I start calling
Dear Sir or Madam
would you please of kind to solve my problem with Sony Experia C as it does not recognize my local sim card (Smart Phone) in Cambodia... every time that I start to call it always alert me about Roaming (Roaming warning "the SIM card that you are about to use is now roaming. Would you like to continue via the local SIM?"). but when I put this SIM card to Samsung (galaxy grand 2) it does not alert like this at all... I try many solution as in the instruction from internet but it still does not help even I contact to the customer care of SIM card to cut out the data roaming from my SIM.
I am looking forward to hearing from you.
Best regards,
DarenHi Daren,
We have a separate community for mobile devices you want to check it out. http://talk.sonymobile.com/. Thanks!
Maybe you are looking for
-
How to get the details of the document uploaded at the catalog area header?
Hi, Can someone explain how we can get the properties(guid class etc) of the uploaded document by using the details of the catalog area (guid)?. Do we have standard FMs available to fetch the required information? Please assist. Regards, Vaibhav
-
Bonjour, J'utilise un boitier USB 6255 avec deux connecteurs 68 pins et les cables correspondant de chez NI. J'ai besoin de contrôler 24 voies en analogique et une 25e voie (somme des 24 précédentes) qui sert de trigger. Normalement chaque voie décle
-
Watermark disappears in Lightroom 5.2
I use Lightroom 5.2 to edit photos and store them in my Flickr gallery. In LR5 I use a Watermark for copyright purposes. However, the photo in Flickr shows the photo without the watermark. Flickr has a standard "Copyright" and "All Rights Reserved" p
-
Page Footer on Cross Tab Reports
How do I get the page footer to show up on all the pages of the Cross-Tab. I have a report where the columns spill over to the second page, but nothing from the footer prints on the second page. It is only printing on the first page.
-
Download / Upload queries gives "Error when generating transport dataset"
Hi! I need to transfer some queries from one system to other. Systems are not connected with each other, so no TRs are available! I am doing like this: - running program RSAQR3TR in "old" system - downloading a query as TXT file into my local PC - ru