Sony Vaio Tap 11 Pen Pressure issues?

Hey everyone, I have a Sony Vaio Tap 11 and for some reasno the Pen Pressure feature isnt functioning within Adobe Products, I have tested it in another program and it worked fine, just not in Adobe products. Any suggestions?

I remembered coming across threads on issues with Sony Vaio, that they were about other models had been unclear to me.
But does Mr.Cox assessment
If the driver isnt' reporting pressure correctly, then it won't work in Photoshop.
The other 2 apps you mention use a different API for pen pressure -- so probably the older API is broken in your driver.
You'll probably have to go through Sony for driver updates.
from this thread
http://forums.adobe.com/message/4856888#4856888
not probably also apply in your case?

Similar Messages

Flash Pro crash after VAIO PS CC pen pressure driver update

I have a tablet PC, VAIO flip... installed the Sony driver update to enable pressure sensitivity in Photoshop CC, works great, but since install, attempting to use pen in Flash CC crashes Flash.
Flash CS6 has no such problem, so no immediate dramas, but would like to know if there is a fix for Flash Pro. Thanks!

Just had this issue with the latest drivers from Wacom (6.3.11-4a) and my old Intuos 3 and found a solution.
It seems any time Wacom updates their drivers, it breaks pressure sensitivity in a random adobe application. This has been happening since.. well.. forever. Wacom and Adobe need to get their **** together.
I fixed my issue by installing an older wacom legacy driver (6.1.7-3). I didn't try any other versions, this one just happened to work for me. You might need to try multiple older versions.
Legacy Drivers | Wacom
My Steps:
- Download an older legacy driver (6.1.7-3 worked for me)
- Unplug your tablet USB
- Uninstall your wacom driver
- Restart
- Install the old driver
- Plug in your tablet and let windows do its thing
- Pressure sensitivity should be working now
I was also having issues with the color picker in Flash CC taking a while to load when using the tablet. That seems to have been fixed as well.
Hope this helps!

Vaio Duo 11 pen pressure unsupported?

Hi, I've just bought Sony Vaio Duo 11 i7 edition with Windows 8 Pro, but I found pen pressure isn't working on neither Photoshop CS5.0.4 or Photoshop Elements 10, while its pen pressure works on Fresh Paint and Artrage 3.5.5. Can anyone help?

Hi, one of the posters from the "N-Trig Tablet Not Recognized" thread there. I figured the matter was settled and I just needed to have some patience when Chris assured me that somebody was "working on Lemonade recipes" as it were, but I simply must interject after seeing HiDPI support getting completed today:
New Photoshop Features and Team Version Headline Major Update to Adobe Creative Cloud (the announcement)
New MacBook Pro Retina Display Support (blog post for background)
Really? Wikipedia says that the "MacBook Pro with Retina display" came out on June 11th, and the HiDPI announcement was released on December 11th. Six months exactly? That is seriously an amazing ability to make deadlines. (Everybody, take note - no matter what Adobe says, they can do things in a timely manner after all!)
Now, I have to point out that one of the things the blog post said was that a staggering 2,500 icons needed to be drawn, in addition to other engineering work. That is a ton to have to do, and it sounds like it was a modern-day miracle for it to be completed in such a short amount of time.
I think my next words must be so obvious that I could probably click "Post" right here and still get the message across anyway, but I'll spell it out: Three years? Your product teams could move mountains in six months for Apple users, but a digitizer that was ubiquitous in 2009 and is practically the Windows 8 flagship today couldn't be tackled in three years?
I can just imagine that poor lemonade-making engineer, sitting alone in a dark cubicle for three years, struggling and flailing to make N-Trig work with no luck at all, eventually developing clinical depression. (Don't worry, I'm not actually crazy; I assumed nobody was seriously working on the problem back then, although I did hope that work would eventually happen if people were patient and polite.)
To quote commenter Tom U from this article (it ranks highly in searches about the Adobe/N-Trig debacle, despite not actually being about that at all), "According to N-Trig it’s Adobe’s Problem, according to Adobe it’s N-Trig's problem. Neither one cares that it’s your problem. And they would both like to deny there IS a problem, so rest assured that nobody is fixing any problems." Couldn't have said it better myself.
For one last quote, I defer to the aforementioned Adobe blog post. "At Adobe we work hard to support the latest innovations. We will continue to release security patches, bug fixes and support new hardware changes, like HiDPI display support, to all of our customers outside of our regular development cycles just as we have always done."
Haha, okay guys. Whatever you say.
I said it three years ago, and apparently I have to say it again - if Adobe fixed this, they'd stand to gain some massively good PR with artists all over the world, who would love to buy a shiny new tablet for the holidays but feel they can't because of this issue.
I myself would love to buy an Adobe product this time around (seeing as all of my Adobe software is rather old and due for an upgrade), but other than the lack of Adobe support, the Duo 11 is perfect for me. I don't expect it to compare feature-wise in the least, but I'm willing to put up with IllustStudio if it means that I can get 90% of the functionality for 10% of the fuss. But I don't want to have to do that. Why compromise when you can have Adobe, a company which reliably makes some of the best software on the planet?
If anyone at Adobe can see which way the wind is blowing, it should quickly become obvious that (1) N-Trig is only going to keep growing; (2) N-Trig is not fixing it (not in any useful way - that makeshift Wintab patch of theirs was a joke); (3) there are a whole lot of people who really do believe Adobe will fix it, not because it's their problem to fix, but because Adobe is just so awesome a company that they take responsibility for things even when they don't have to. Other companies would kill to have that kind of customer loyalty, you know?
By the way, since the idea of having to cripple Photoshop's user experience to make way for N-Trig's defects was a sticking point last time, I'll take this moment to point out that we don't care if there's a few features missing, we just want it to work at all. Put an obnoxious warning every time the application loads that we're using a bad digitizer! Just let us have that option, pretty please.
We want that. We want to pay you for that. Please?
Just spend a few hours on the Internet and you'll find thousands of potential sales from people reluctantly making do with N-Trig compatible software, saying things like "Well, I guess ArtRage is kind of okay, but I wish I could be using Photoshop." What sane person would turn those sales down?
I get it. I really do get it, okay? Adobe's a relatively old company in tech terms, people are set in their ways, and the idea of sucking it up and doing something unpleasant like supporting a cheap lazy digitizer such as N-Trig would leave a bad taste in a lot of people's mouths.
But please, I implore you, if any of you aren't snobbish about things like that - if there's any new blood in the company at all - please try to convince your managers that this would be a good idea. For us, the customers who want to like you but sometimes find it rather difficult, this would be a big deal.
You have the chance to be the "bigger man", as it were. That's it. Period. Doesn't matter if N-Trig should be handling it, or Microsoft, or anyone else. You can be the bigger people here. You can be the grown-ups, and gain a lot of relatively low-cost advertising as a result. Please actually consider it this time around, okay?
It seems crazy to me for Adobe to have spent so much sweat and blood creating versions of their software for iPad and Android tablets, while they've been actively fighting tooth and nail for a very long time (since before those platforms even existed!) to avoid fully supporting the Windows world's version of the same.
In summary, if you can do one thing, why not the other? If you can write entire software suites for new devices, why not this? If you can meticulously repaint 2,500 icons for a bunch of yuppies, why not this? It's not like the demand isn't there. It is, in droves. So please, carefully and seriously consider supporting N-Trig, and please pass the idea along to the proper brass instead of letting it die here on the forums.
Even though you don't have to, it would mean an awful lot to an ever-growing number of people if you did.

Photoshop Pen Pressure Issues

I'm not actually sure that this is the correct place to post this. I don't have a question per se, as I've fixed the problem, but I would like to address an issue with Photoshop and my pen tablet and hopefully help others who might have the same problems. I recently built a new computer and, upon installing my Wacom Bamboo and Photoshop, found myself unable to use the pen pressure settings in Photoshop, which had previously worked just fine on my old machine. I tried everything I could find on the web to fix the problem: reinstalling the tablet drivers, installing old driver versions, turning on and off various settings, nothing worked, when finally I stumbled across a post by someone who offhandedly mentioned that they started Photoshop with their pen, instead of their mouse, and that their pressure settings worked just fine. I was kinda skeptical that such a trivial-seeming thing could be the fix, but I tried it, and lo and behold, it worked! If anyone here knows why I'd be interested in knowing, just for the sake of curiosity, but I hope this simple fix can save some time and frustration for other users.

Photoshop CC 2014 changes stylus use to use Microsoft system API's, with these API's you need to have Windows Ink enabled. These API's give better stroke results and improve the out of the box experience for users using Windows tablet/convertible devices. If you want to go back to the old WinTab implementation of previous versions do the following:
Create a file that contains instructions to revert to the WinTab functionality.
Create a text file in a text editor such as Notepad.
Type in the following lines:
# Use WinTab
UseSystemStylus 0
Save the file as a plain text file named PSUserConfig.txt, and save the file into the Photoshop settings folder: C:\Users\[User Name]\AppData\Roaming\Adobe\Adobe Photoshop CC 2014\Adobe Photoshop CC 2014 Settings\.
To turn off the gestalt's functionality, delete the PSUSerConfig.txt file. Or, move it to a different folder if it doesn't contain any other commands, or change the lines so they read:
# Use Win8 native tablet support
UseSystemStylus 1

Pen pressure issues with CS6

So, I'm having an odd issue with my tablet and its pressure sensitivity with CS6. I've got a Genius MousePen tablet; M508W model. I can use it on my mac computer with photoshop elements; pen pressure works just fine with it. In CS6, when I do the stroke preview for all of my burshes, it shows the tapering-- as well as in the brush settings. When I go to make an actual rush stroke though, it doesn't apply the pressure settings. I've got the most recent drivers for the tablet downloaded, All of the old driver software was uninstalled, I've made sure that the drivers are for my version of windows, I've tried setting the compatability back to windows 7 and using the windows 7 drivers, but STILL nothing. The only reason I'm lead to believe that this is an issue with CS6 is that the tablet works with PS Elements just fine. If anyone could help shed some light on the situation, I'd greatly appreciate it.

I am having a similar issue.
Working in CS6 on a Cintiq Companion.
Pressure sensitivity disappears while I'm working.
The only way to get it back is to quit out of Photoshop and relaunch.
The pressure sensitivity works fine in Autodesk Sketchbook.

Photoshop CC on Sony's Vaoi Fit15A (pen pressure problems)

This question is very specific. I just downloaded the trial version of Photoshop CC on a new Vaoi Fit15A. It's like a hybrid between a tablet so I can supposedly draw on the screen directly. (So I don't have a pen tablet.) My problem is it doesn't register the pen pressure. I also tried borrowing a wacom bamboo to see if it can feel that, but nope, PS CC still won't recognize the pen pressure even from a pen tab. What should I do? Thanks to anyone who can help!

Hi! Thanks so much for replying
I tried attaching a bamboo create to see if it could sense the pen pressure. Alas, it still couldn't. I already installed the drivers but it still wouldn't.
So um, just letting you know that I did take it to the store where I bought it. They told me that Adobe wasn't keeping up with something something industry-wise. Sorry I'm in Japan and my Japanese isn't that good but basically they told me that I have to wait for Adobe elements 12 (which isn't out yet) before I can hope that my Vaoi recognizes the pen pressure. So they basically told me that Vaoi fit15A, using PS CC, isn't compatible. There's no way I can get pen pressure using that program.
But is this true? Adobe is late that's why I can't get it to work in Vaoi Fit 15A ? They just didn't tell me this because they couldn't get it to work right? When is this "Adobe elements 12" suppose to come out anyway? If I can't get it to work I'll have to return the Vaoi itself since I need my pen pressure working in PS.
Thanks for your time!!!

Pen Pressure in Photoshop on MS Surface Pro..

Did anyone get the new update today and did it fix the pen pressure issue for Photoshop use on the MS Surface Pro Tablet???? I know this is an aging die hard issue but man do I need it bad,.....-Joe

Hey there folks,
I figure I take some time to respond to the surface pro things,.....
@Alanomaly, yes pretty good so far, I can not complain about the pen pressure. MS had nothing to do with it except to communicatge with Adobe, and Wacom..as things go, all three needed to agree on working on this. The driver is through Wacom on their site under the Tablet PC select. Thats it. You load, restart PC an it works.
Now as far as comparing it to Intuos/Cintiq, well, its not a question really. The Surface Pro tablet functions like a PC but is smaller than a 9x12 Intuos and Cintiq, with the exception of the smallest sizes of eother of those. But, I do not use the smaller sizes. I do have a Cintiq 24 HD, love it!!! When Im away, the road, at the shore,..or at work and want to doodle, sketch, concept draw, whatever, Im not using Surface Pro to do full fledged digital content, ..Ill take it home and finish or expand on it.....but I wont divulge my personal reasons for using it , but, that is why I think Surface Pro exists, so I can use it for what I want and be happy. Now, if Wacom comes out w a tablet and its a tablet like Surface Pro, and a user wont need to hook up a Wacom type of tablet to a PC to work on it as a mobile device, then, I ll be rethinking my options....maybe.
Now, I have a Xeon cpu in my machine and a second one when Im ready to use it, and I see the i5 and i7 cpus really taking advantage of the mixer brushes and interactive brushes better than my xeon cpus. I wish to make that better on my machine but thats another story.
I hope tht helps.....
-J

Pen pressure not working. Tried everything.

Tried techniques in both Adobe and Corel.
Any suggestions on how to get the pen pressure to work would be greatly appreciated!

Notably Wacom has *just* released a new driver for their tablets to correct pen pressure issues, and at least one person has reported that it has corrected pen pressure problems.
I haven't read too carefully here, and I don't know if their driver could help you directly. I just mentioned it because you said you saw Wacom people reporting problems too.
http://www.wacom.com/en/CustomerCare/Drivers.aspx?model=Intuos3&os=Windows+7
-Noel

Brightness not adjustable in Windows 8.1 Sony Vaio (formerly sleep issue)

AAAAAARGH. Whenever I hear the word VAIO my blood pressure rises. Model: VPCYB13KX/P (P=Pink) but the problem seems to be a universal oneMajor problems: cannot change brightness at all, closing the lid puts computer in non-responsive but 100% CPU state (judging by the CPU cooler fan turning on to max and enough heat radiating from the base of the laptop to fry an egg)OS: Windows 8.1 upgraded from a clean install of Windows 8 64 bit So, in my case I clean installed Windows 8 followed by 8.1. Vaio "care" (if that's what you want to call it) and all the ancillary junk was installed as well (much of it removed in trouble shooting). Before I did trouble shooting I had four major problems:1 FN keys (F5/F6) did not adjust brightness at all (still broken, and officially broken for the VPCYB series according to http://esupport.sony.com/US/p/support-info.pl?info_id=1380)2 FN keys (F3/F4) did not adjust sound (fixed, not sure when)3 Brightness could not be changed AT ALL (broken, fixed and now broken again by solution to sleep problem)4 Closing the laptop's lid would cause the computer to go into a "frozen" but active state out of which it couldn't be woken up (fixed by steps at end of post)5 Complaint during boot about missing file (see http://community.sony.com/t5/Windows-8/iolorgdf32-program-can-not-be-found-Skipping-Autocheck/td-p/161333 for someone else's description of problem) (not fixed; not bothered to try... seems like a minor problem compared to everything else)6 mf110u DLL missing dialogue box upon startup (see http://answers.microsoft.com/en-us/windows/forum/windows_8-windows_update/mfc110udll-missing-windows-8-pro-updates-wont/9596536f-a405-4b1e-b8cf-b06e28b7fea4?msgId=28e1af2b-d536-4258-aea2-a1155cc6464b) (fixed) Re: 3 brightness. Before the sleep fix (billed as a brightness fix) was applied I was able to adjust brightness using the Windows brightness controls (one in the new interface and one in the desktop/traditional interface). Now I can't. Re: 5 and 6 My guess is that #5 and #6 have to do with the Vaio Care software (which seems to be someone else's software repackaged?). This laptop has been a support headache from day one, even under the 'clean' OEM Windows 7 Home Premium with Vaio drivers and software being the culprits 95% of the time (terrible QAQC). Until very recently I had problems with the wifi cutting out daily in Windows 7 Home Premium (only fixed when I clean installed Ultimate and used non-Sony driver for wifi... I should've stuck with 7 Ultimate and not boethered with 8). What others have been told would correct their brightness problem fixed my sleep problem (I can close the lid now) but it broke my brightness adjustment ability. I'm now stuck at 100% no matter what I do. PS These are the instructions for how to fix the brightness problem (and, to reiterate, it broke my brightness solution but fixed my sleep problem): 1.Launch Task Manager
2.Terminate two tasks
•esrv.exe
•esrv_svc.exe
3.Delete “sony_acpi_battery_input.dll” Under “C:\Program Files\Sony\VAIO Care\ESRV\sony_acpi_battery_input.dll”
4.Restart PC So, if anyone has a suggestion about how to get brightness working without breaking sleep please let me know. If I don't have any success fixing this I'm simply going to downgrade the laptop to Windows 7 Ultimate again and transfer my Windows 8 licence to my home built desktop machine (I was going to pick up a second licence but maybe I won't bother since I'll only need one).

I did try that IIRC but no luck. I've simply given up and gone back to Windows 7 because I don't have the luxury of devoting time to re-installing software when I've got toddlers screaming for my attention and work taking up the rest of my time. I haven't installed a single piece of Sony software on my Windows 7 install and so far only two things were not working: brightness control and a broken wifi driver. I fixed the driver (Sony doesn't provide a fix for the faulty wifi driver for the VPCYB13KX, nor does Microsoft) by installing a driver from the web (care of Atheros.cz). And, i haven't bothered to go after the brightness control because it's not as pressing an issue as the faulty wifi driver. Plus, I don't have any of the Sony bloatware slowing things down (installing an SSD at the same time may have had something to do with the speed up ;-). Plus, in many ways going back to Windows 7 simplifies my life big time since it is a computer that's being used by two people and Windows 8.1 makes accomodating the work flow of two separate people in one account difficult. Tangent... And, it means that at least one computer isn't subject to the prying eyes of Microsoft Live. I am becoming really leery of the amount of information that private companies (which means there is zero transparency) are able to collect and sell about private individuals through Windows 8.1, Mac OS X 10.9 and Google OS. If you happen to allow the wrong settings these OSes are able to track and store phenomenal levels of personal information (which police would never be able to find out about you without a warrant, let alone store in perpetuity). And, who knows if these OSes even honour your opt-outs. Or, if through coding errors they still continue to collect the data anyway.

Problems with Illustrator CC 2014 in Sony Vaio Fit 15A with N-Trig touch screen and digitizer pen.

Hello to everybody!
Some times ago Adobe has updated Illustrator to CC 2014 version and now it support touch pressure\pan\zoom in Windows 8 tablets. I have Sony Vaio Fit 15A with N-Trig touch screen and digitizer pen with pressure-sensitive support.
I was extremely disappointed that the brush in new version does not work correctly. Watch the video please that I did specifically for the demonstration.
I use Adobe Illustrator CS6 and Adobe Illustrator CC 2014 for comparison. In the old version the brush is works correctly. You must do a lot of clicks to start the brush in CC 2014 version (please see video). What causes of the problem? Please help me!

Hello to everybody!
Some times ago Adobe has updated Illustrator to CC 2014 version and now it support touch pressure\pan\zoom in Windows 8 tablets. I have Sony Vaio Fit 15A with N-Trig touch screen and digitizer pen with pressure-sensitive support.
I was extremely disappointed that the brush in new version does not work correctly. Watch the video please that I did specifically for the demonstration.
I use Adobe Illustrator CS6 and Adobe Illustrator CC 2014 for comparison. In the old version the brush is works correctly. You must do a lot of clicks to start the brush in CC 2014 version (please see video). What causes of the problem? Please help me!

[SOLVED] ACPI power issues with Sony Vaio Pro 13

tl;dr backstory:
Sony VAIO Pro 13 (SVP13215CDB) laptop was working great (Win 8.1).
Installed Win10 Tech Preview. A week later, it started going to sleep randomly and on certain key-presses (perhaps after performing Sony Vaio Software updates. I'm not 100% sure). I wiped all partitions installing Win7 in legacy mode. It still went to sleep randomly.
I restored to factory default Win8.1 with Sony Vaio software up-to-date. It still went to sleep randomly.
Took it to an electronics repair shop, to see if they could fix it, and they said it can't be fixed in any way without replacing motherboard, but that's basically a new laptop.
So I turned to Arch Linux.
I have completed the basic install from the Wiki, and it no longer sleeps/shuts down randomly, but it will gracefully shutdown when certain events/keypresses occur.
I installed acpid and used "acpi_listen >> acpi.log" to determine what causes the system to perform a graceful shutdown. Here is the result of acpi.log (each line was a shutdown event):
button/power PBTN 00000080 00000000 # Unplugged power adapter.
button/power PBTN 00000080 00000000 # Running on battery and idle. Perhaps battery percent update caused this?
button/power PBTN 00000080 00000000 # Plugged in power adapter.
button/power PBTN 00000080 00000000 # Fn-F1 Touchpad Disable
button/power PBTN 00000080 00000000 # Fn-F5 Brightness Down
button/power PBTN 00000080 00000000 # Fn-F6 Brightness Up
button/power PBTN 00000080 00000000 # Fn-F7 LCD/External Display
button/power PBTN 00000080 00000000 # Fn-1 (Weird. It has no extra function).
As you can see, they all seem to trigger the same shutdown event.
I have seen on other posts that these ACPI signals can be disabled or assigned to other commands, which would be an acceptable workaround if it stops my laptop from erroneously shutting down. Is this doable?
Also, I was not able to reflash the Sony VAIO firmware when using Windows, as Sony's package software is amazing wouldn't allow flashing an equal or lesser firmware version. Perhaps there is a way in Arch to force a reflash if I can get my hands on the firmware blob?
Thanks .
Last edited by SafeToRemoveACPI (2014-11-25 22:55:55)

linux /boot/vmlinuz-linux root=UUID=<UUID here> rw quiet acpi=off
Like this?
I did that, and it disabled my laptop keyboard entirely. In doing so, it disables the key-presses that would normally shutdown the laptop, including the power button. So the only way to shut it down is a hard shutdown via long-press of the power button. Thanks, though.
Update: Issue Solved. I will update post tonight. Flashing the BIOS again resolved the ACPI issues.
Last edited by SafeToRemoveACPI (2014-11-25 22:54:13)

Sony Vaio FW issues

Hello. I have some problems with my Sony Vaio FW laptop.
1. the fan is strangely always running
2. can't shutdown via the GNOME menu
3. brightness doesn't work (xbacklight says "No outputs have backlight property")
All of the above worked on a previous Arch installation and in Ubuntu >= 9.04.
I have:
- acpi-cpufreq, cpufreq_ondamend, sony_laptop in MODULES()
- @acpid, cpufreq in DAEMONS()
- my user is a member of the following groups: network, video, audio, scanner, power, users, dbus, avahi, hal, vboxusers,
- my video driver is 'radeon'; xfree86-video-ati and gnome composition works perfect.
Am I missing some vital daemon or configuration? Please help.
Last edited by napsy (2010-03-12 16:33:48)

I had acpid as marked as asynchronous in DAEMONS. When I removed the @ and rebooted the issue with the gnome menu and brightness was fixed. But the fan is still strangely very active. I've read somewhere that the radeon drivers don't work well and get the GPU going 100% all the time. But didn't go into details.

[SOLVED] Sony Vaio Keys don't work (probably udev issue)

Hardware: SONY VAIO VPC-EH2L1R
Linux distribution: archlinux, XFCE
udev versions: 177, 178 (core), udev-git 20120123-1 (AUR)
keyboard driver: evdev
At least a week earlier I had some of Sony Vaio Keys working: Volume control (Fn+F2: mute, Fn+F3: down, Fn+F4: up) and Brightness control (Fn+F5: down, Fn+F6: up). Other Vaio Keys (Fn+F1: touchpad switch, Fn+F7: switch video mode, Fn+F12: suspend) never worked.
At some point (I think after updating to udev-177-1) Brightness control keys stopped working. Volume control keys still work.
Brightness control still works directly via acpi.
I know this may sound like this bug, but that solution doesn't work for me - neither updating to udev-git nor manually loading the keymap.
My keyboards are:
[ajaxas@r2d2 ~]$ /lib/udev/findkeyboards
AT keyboard: input/event0
module: input/event1
which are actually:
[ajaxas@r2d2 ~]$ cat /proc/bus/input/devices
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=120013
B: KEY=402000000 3803078f800d001 feffffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7
I: Bus=0010 Vendor=104d Product=0000 Version=0000
N: Name="Sony Vaio Keys"
P: Phys=
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/SNY5001:00/input/input1
U: Uniq=
H: Handlers=kbd rfkill event1
B: PROP=0
B: EV=13
B: KEY=1f16cf0000 c00000000 10010000000000 200000000 600e00102c00 380000240300400 e000000000000 0
B: MSC=10
Now, the funny thing is that (I think) udev loads my keymap correctly:
[ajaxas@r2d2 ~]$ cat /sys/class/dmi/id/{sys_vendor,product_name}
Sony Corporation
VPCEH2L1R
Here is this keymap module-sony (which worked until recently!):
[ajaxas@r2d2 ~]$ cat /lib/udev/keymaps/module-sony
0x06 mute # Fn+F2
0x07 volumedown # Fn+F3
0x08 volumeup # Fn+F4
0x09 brightnessdown # Fn+F5
0x0A brightnessup # Fn+F6
0x0B switchvideomode # Fn+F7
0x0E zoom # Fn+F10
0x10 suspend # Fn+F12
- but here is where it starts getting curiouser and curiouser.
My Volume control keys seem to be mapped to input/event0 (keyboard itself):
[root@r2d2 ajaxas]# /lib/udev/keynap -i input/event0
scan code: 0xA0 key code: mute
scan code: 0xAE key code: volumedown
scan code: 0xB0 key code: volumeup
and these scan codes correspond not to my keymap (0x06, 0x07, 0x08), but to /lib/udev/keymaps/force-release/common-volume-keys:
[ajaxas@r2d2 ~]$ cat /lib/udev/keymaps/force-release/common-volume-keys
0xa0 #mute
0xae #volume down
0xb0 #volume up
So I assume, udev uses force-release rules before other keymaps and maps my Volume control keys to input/event0 (how? I couldn't find the rule!), which is more or less fine with me, but!
My Brightness control keys, mapped as 0x09 and 0x0A in the keymap, are reported by udev as:
[root@r2d2 ajaxas]# /lib/udev/keymap -i input/event1
scan code: 0x10 key code: brightnessdown
scan code: 0x11 key code: brightnessup
If I change my keymap file (0x09 -> 0x10, 0x0A -> 0x11) and load keymap manually, nothing changes. And when I reboot with this changed keymap, udev reports this for my Brightness control keys:
[root@r2d2 ajaxas]# /lib/udev/keymap -i input/event1
scan code: 0x10 key code: fn_f5
scan code: 0x11 key code: fn_f6
Again, nothing works, and keys are not reported as Brightness control keys anymore.
As I said earlier, updating udev doesn't help.
Could somebody please help me?
EDIT: added keyboard driver (evdev) reference.
Last edited by ajaxas (2012-01-25 13:52:54)

jst wrote:
ajaxas wrote:Okay, this is stupid but it was XFCE's fault. If anyone with the same problem reads this, try creating a new user account and see if it's actually udev or only your shitty DE. -_-
How did you solve this? I realized I have the same problem with XFCE, but could not solve it
I don't really remember. As a matter of fact, I've already switched to KDE and I'm quite content with it

Tablet + pen pressure + illustrator CS5 issue

Hello all,
I just installed Illustrator CS5 and I can't get the brushes to recognize pen pressure from my graphics tablet (intuos3).
I have tried all the combos of brushes, strokes, etc. It looks like all the 6D options (bearing, tilt, pressure) are greyed out. Thus, the ap doesn't recognize when I am using my pen.
Oddly, the pen works great in Photoshop CS5.
I am working on Windows 7.
Any thoughts?
Thanks!
_Todd

I'm with Todditron and the others with lack of pressure problem.
I'm on a Mac running OSX 10.6.6, with a Wacom Graphire4.
Pressure works in Photoshop CS5. In illustrator, pen works-making lines and scribbles as directed, but no variation with increased/decreased pressure. In the Brushes panel, I can double click on selected brush, opening an Art Brush Options window, and change width, roundness, etc from "fixed" to "pressure," but those qualities remain fixed, regardless of my pressure.
Wrote to and heard back from Wacom Help Desk. Followed their instructions..
"I would recommend removing your current driver by opening your Applications folder and double clicking on the Remove Wacom tablet icon or the Wacom tablet utility icon found in the Wacom tablet folder there. Inside that removal utility you’ll want to click on the remove tablet software button and then enter your password to remove your current driver. Once the driver has been removed you’ll then want to repair your disk permissions before installing the latest. To do this if you open your Utilities folder at the bottom of your Applications folder, in there will be an icon for Disk Utility that you’ll want to double click on. In the Disk Utility you’ll then want to select your Macintosh HD on the left hand side and then click the repair disk permissions button towards the bottom. Once the permissions repair is complete you can then download and install the latest driver for your tablet from our website."
to no avail. Tried the process again, restarting the computer after repairing Disk Permissions and reinstalling newest tablet driver. No go.
Wrote Wacom Help Desk again. Will follow up here once I hear back.
-F

[Sony Vaio TZ] Xorg mapping wrong resolution

I recently bought a Sony Vaio TZ - awesome piece of equipment - but noticed my actual Xorg resolution was higher than what the specs said (by 2 pixels). This is kinda annoying...
Xrandr output before I use xrandr to set the correct resolution:
[root@hermes stijn]# xrandr
Screen 0: minimum 1024 x 768, current 1368 x 768, maximum 1368 x 768
default connected 1368x768+0+0 (normal left inverted right) 0mm x 0mm
1366x768 60.0
1360x768 60.0
1024x768 60.0
1368x768 60.0*
As you can see it says it detects 1368x768 as maximum resolution but lists the correct resolution (1366x768) as a possibility too. My first reaction was to generate a modeline that would make Xorg behave, but that does not have the desired effect (it returns a 1368x768 line!):
[root@hermes stijn]# gtf 1366 768 60
# 1368x766 @ 60.00 Hz (GTF) hsync: 47.58 kHz; pclk: 85.64 MHz
Modeline "1368x766_60.00" 85.64 1368 1440 1584 1800 766 767 770 793 -HSync +Vsync
I have tried setting a Modes line in xorg.conf like this:
Modes "1366x768"
but that gives me the following message in Xorg's log:
(II) I810(0): Not using mode "1366x768" (no mode of this name)
Adding a 'Virtual' line with the correct dimensions like this:
Virtual 1366 768
doesn't do the trick either.
Grepping Xorg's log for both X sizes returns the following:
[root@hermes stijn]# egrep "1366|1368" /var/log/Xorg.0.log
(II) I810(0): Display Info: LFP (local flat panel): attached: TRUE, present: TRUE, size: (1366,768)
(II) I810(0): Size of device LFP (local flat panel) is 1366 x 768
(II) I810(0): Lowest common panel size for pipe B is 1366 x 768
(II) I810(0): PanelID returned panel resolution : 1366x768
Mode: 60 (1366x768)
XResolution: 1366
Mode: 61 (1366x768)
XResolution: 1366
*Mode: 62 (1366x768)
XResolution: 1366
(II) I810(0): Not using mode "1366x768" (no mode of this name)
(II) I810(0): Correcting stride (1368 -> 5504)
(**) I810(0): Virtual size is 1368x768 (pitch 2048)
(II) I810(0): [drm] init sarea width,height = 1368 x 768 (pitch 2048)
Why the heck does the i810 map to this resolution? Xorg recognises the 1366x766 correctly no? Is there a way to make Xorg use 1366x766 without having to resort to xrandr? For what it's worth, I had this issue also with the vesa driver.
Last edited by B (2008-03-31 03:20:54)

Ok. I went with xmodmap because xbindkeys basically does the same, only requiring you to install an extra package .
I mapped the eject button to eject too (surprisingly, as I didn't know at first the slim drive had a button, I thought the whole thing was pressure sensitive...). I mapped the AV button to a fullscreen instance of VLC .
I fixed all Fn keys except for the zoom key (don't know how to map that to e.g. Opera's zoom functionality yet) and the external VGA connector which I should still write a script for.
Anyways, here's my handler.sh patch:
--- handler.sh.old 2008-04-04 22:59:23.000000000 +0200
+++ handler.sh 2008-04-04 22:59:12.000000000 +0200
@@ -7,6 +7,7 @@
minspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq`
maxspeed=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq`
setspeed="/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed"
+presbright=`cat /sys/class/backlight/sony/brightness`
set $*
@@ -18,29 +19,34 @@
*) logger "ACPI action undefined: $2" ;;
esac
+
button/sleep)
case "$2" in
SLPB) echo -n mem >/sys/power/state ;;
*) logger "ACPI action undefined: $2" ;;
esac
+
ac_adapter)
case "$2" in
- AC)
+ ACAD)
case "$4" in
00000000)
echo -n $minspeed >$setspeed
#/etc/laptop-mode/laptop-mode start
+ echo 2 > /sys/class/backlight/sony/brightness
00000001)
echo -n $maxspeed >$setspeed
#/etc/laptop-mode/laptop-mode stop
+ echo 6 > /sys/class/backlight/sony/brightness
esac
*) logger "ACPI action undefined: $2" ;;
esac
+
battery)
case "$2" in
BAT0)
@@ -60,6 +66,32 @@
button/lid)
#echo "LID switched!">/dev/tty5
+
+ sony/hotkey)
+ case "$2" in
+ SPIC)
+ case "$4" in
+ 0000000c)
+ [ -e /var/run/daemons/bluetooth ] && /etc/rc.d/bluetooth stop || /etc/rc.d/bluetooth start
+ ;;
+ 00000010)
+ echo $(( ${presbright}-1 )) > /sys/class/backlight/sony/brightness
+ ;;
+ 00000011)
+ echo $(( ${presbright}+1 )) > /sys/class/backlight/sony/brightness
+ ;;
+ 00000017)
+ /usr/sbin/pm-suspend
+ ;;
+ 0000001b)
+ eject -r
+ ;;
+ esac
+ ;;
+ *) logger "ACPI action undefined: $2" ;;
+ esac
+ ;;
+
logger "ACPI group/action undefined: $1 / $2"
Xmodmap gives names to the Fn volume keys and the multimedia keys, and they are bound to the related actions through my Openbox rc.xml.

Sony Vaio Tap 11 Pen Pressure issues?

Similar Messages

Maybe you are looking for