Xperia z1 loss of camera functionality unlocking bootloader - camera

Sony xperia z1
Are Sony working on a fix for the broken camera problem when unlocking the bootloader of Xperia z1?
any estimate of arravial of such an fix?

Same problem here.
For now, you can just root on .534 then upgrade to .257
Use vRoot on .534 then with SuperSU Pro use OTA survival mode and upgrade to .257 with OTA.
If you unlock the bootloader, your DRM keys will be lost, so the camera will stop working correctly (no auto focus, etc.)
Unfortunatly, there is no way to flash a custom kernel without losing the camera functionality.
Tried also to contact sony, but the support for developers is a bit dead.

Related

Arduino as HID device on Windows - Bind external button presses to a keymap in the OS?

Here's the problem: I want to press an external button attached to an Arduino, and I want that button press to translate into Windows as a keystroke.
My question is, is there a programmable device (I already own an Arduino) that can receive signals, and send them over USB to my computer which will understand it as a keypressExample: Button press acts like hitting the S key on my keyboard?
There are three (four) possibilities:
First Get an Arduino Leonardo (32U4 architecture) - there are HID drivers (so windows recognizes the hardware - short explanation: The Arduino LEONARDO is an integrated USB HID Arduino board. Ideal for projects requiring the board to behave (act) as a USB human interface devices = HID).
Two Use any other Arduino and install Processing with the relevant modules. Write code on both and use Processing to translate to windows.
Three I've seen some more or less working implementations.Example 1Example 2Example 3 Scroll down and you will see a picture of your button solution including code.
(Four) This requires also windows programming skills. Write an usb "driver" a translating engine for I/O between Arduino on usb and acting like a virtual (e.g. touch screen) keyboard. Thats the hardest way to go.

How to detect gamepad triggers both pushed with USB HID API?

I use RawInput + Windows USB HID API to receive WM_INPUT message when a gamepad button is pressed and retrieve gamepad state.
There's a problem: two triggers work on same axis which means you can't figure out if two triggers are pressed at the same time. I observe the same behaviour when launch OS Windows gamepad test application. But I need to distinguish these two buttons pushed.
Note that XInput works as desired, it gives you two axises for two triggers, but I don't want use XInput because it's only for XBox controllers and there are dozens of non-xbox controllers in the world.
I suppose there must be a way to read two axises through USB HID API, but until now I couldn't find it. Have you resolved the issue?
Gamepad: XBox 360 used (but any other should be supported).
OS: Windows 7.
IDE: Visual Studio 2010.
Language: C++
If you really need to read XInput data via HID API and get trigger axis independently...
There is xusb22.sys driver option for that:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\xusb22\Parameters]
"GamepadTriggerUsage"=dword:00003532
"GamepadStickUsage"=dword:31303433
Make it report LT/RT on Rx/Ry (0x33/0x34 usage) and RStick on Z/Rz (0x32/0x35 usage) HID Axis - just like DualShock4:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\xusb22\Parameters]
"GamepadTriggerUsage"=dword:00003334
"GamepadStickUsage"=dword:31303532
But still - there is no any way to send vibration to XInput controller via its HID interface.
PS: There are others options exists. See C:\Windows\INF\xusb22.inf file.

Only the User LED 2 gets solid on after reflashing my Beaglebone Black. I cant conect. Why?

I've tryed several times to re-flash my Beaglebone Black with some images downloaded from the beagleboard website and elinux website, following these instructions to re-flash:
http://derekmolloy.ie/write-a-new-image-to-the-beaglebone-black/
And after the process is done (all user leds are solid off), i take off the micro sd and switch on the board and all user leds start to blink (not all together) and a few second later only the user led 2 keeps on (solid) and I cant acess it.
I figure out that for any reason reflashing hadnt completed. That's why the user led 2 was always solid on and all the other leds solid off.
After I insert the micro sd back I could access the board. To reflash I decided to setup the standalone microSD image to automatically flash the eMMC on powerup by editing /boot/uEnv.txt:
##enable BBB: eMMC Flasher:
#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
Changing to:
##enable BBB: eMMC Flasher:
cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
and rebooting the system. It flashes the eMMC on the next bootup. (make sure to remove the microSD after flashing is complete)

Microsoft pixelsense input simulator finger stays pressed

I have a problem with the Input Simulator in the microsoft surface SDK 2.0.
Whenever I try to simulate a finger or a blob click, the first click stays pressed (like when you put it as placeholder with right click+left click).
I don't know the reason of this behaviour since on other computers it work without problem.
Can it be because of I'm using windows in a virtual machine? If yes, is there any workaround?
I fixed this by disabling touch pen utilities which was automatically installed with surface SDK.

Is there a way to access DELL XPS media buttons programmatically

If you have seen a Dell XPS in actions you probably have noticed its nice media buttons above the normal keyboard:
alt text http://blog.evolvedsoftwarestudios.com/wp-content/uploads/2008/03/img-1397.jpg
They are flashing when the notebook is starting and when you touch them.
Does anybody know how to make these buttons flash programmatically?
I had an old IBM laptop that had a keyboard light LED mounted in the top of the LCD frame (where the iSight is on a MacBook or MacBook Pro). I found that I could access this light via /proc/acpi under Linux.
I wrote a simple script that flashed the light on and off by interacting with /proc. There's a posting on my blog with the code.
You might want to try running an Ubuntu live CD and seeing if it detects the buttons, and if you can access them via /proc. A quick search showed that the newer XPS systems work out of the box with Ubuntu, so it'd be a good starting point.