As a regular trackball user on desktops, I've been looking for a Bluetooth one to go with the Tablet S to give me a bit more precision for tasks like text editing. Unfortunately apart from one very hard to source and expensive Mac targeted device my search has been fruitless.
I finally bit the bullet and ordered a mouse and would just like to recommend Dell's mini 5 button Bluetooth travel mouse.
It's length is just under half the screen height of the Tablet and is black/silver, so slightly smaller than a regular mouse and matches the tablet well. Using 2 AA batteries it paired straight away and only requires about an inch of movement for the pointer to traverse the whole screen. It also wakes the tablet up on movement. Scroll wheel works but the browser back & forward and right mouse button don't. If anyone has any tips for an app that would allow for these buttons that would be great but otherwise picked up for less than £20 I'm a happy bunny.
Cool. The ones I have used require a USB plug in.
dtaylorr said:
Cool. The ones I have used require a USB plug in.
Click to expand...
Click to collapse
Tthere are others without usb recievers but i read on another forum if u use it u cant use sony's bluetooth keyboard simultaneously is that true?
cuts103 said:
Tthere are others without usb recievers but i read on another forum if u use it u cant use sony's bluetooth keyboard simultaneously is that true?
Click to expand...
Click to collapse
Not sure I'm afraid, the on screen keyboard is good enough for my young slender fingers.
If it's a multiple bluetooth device issue I'll try it out with my PS3 controller tonight and see if both work together.
Here's the mouse anyway.
http://www.amazon.co.uk/Dell-Blueto...8DRC/ref=sr_1_1?ie=UTF8&qid=1329987831&sr=8-1
Well there's no problems talking to 2 bluetooth devices at the same time. But can't vouch for a keyboard I'm afraid.
I recently purchased a dell 20 inch touch screen. One of the major selling points was that it supported an MHL-HDMI, meaning 1 simple cable would supply both an HDMI and USB connection from my phone to the monitor... which it does. The issue however is that the touch screen does not respond correctly to input. Anywhere I touch on the screen it simply hits the same spot near the top left over and over. USB devices plugged into the monitor (it's also a hub) work just fine.
I thought it might have been the cable so I tried an external MHL adapter and ended up with the same result. Then I hooked up some other android devices(tronsmart prometheus, and an ouya (running CM11)) through hdmi with USB attached and again received the same response. It does however work normally with every variety of x86 computer I've tried; even android x86.
This seems very similar to a configuration issue I fixed on an a touchscreen Ubuntu laptop years ago. Some googling helped me solve that one quickly and easily, but the problem is that I have no idea where to start on this one. Searching is almost impossible as any combination of "android" and "touch screen" tends to take me off in the wrong direction. Even here 4 out of the 5 threads I've found are at least 5 years old and quite hypothetical.
Of course it could always be a deeper issue involving a lack of kernel support, in which case I'm probably screwed.
Any suggestions on where/how to start? If nothing else this can at least act as a warning for people not to buy MHL HDMI touchscreens and expect them to work with android phones out of the box. At least not yet.
Thanks for any ideas in advance
i`am exactly in the same position right now, beside not having bought a touchscreen yet.
my thoughts were also to buy a dockingstation for the htc one x (m8), to have
hdmi and usb , then just connect both to a touchscreen monitor and make use of mhl
to make it work, meaning having proper touch functionallity on the monitor.
and you`re right, i`am searching this topic for some time now, seems like this idea diyed out in 2011,
at least according to the internet
so, not much of help from my side, but def. interested to see how this thread goes !
The Ubuntu Touch OS is a pretty big topic as of late, and I'm really hyped to see it come along... but I have to say, I'm shocked by the lack of docks for a lot of devices lately.
Why do I say this? Well, I suppose it's less relevant to UbTouch, but it's pretty important and worth mentioning. More and more, these modern devices are coming out, offering crazy specs like Quad-HD displays and quad-core processors, but it's given a hardcore hardware limitation, usually defined by the USB port with the MHL/OTG nature. I don't know enough docks where a phone does it, but I know Samsung has that on lock. You look at their products, their USB port is designed well, able to plug into a dock that has an HDMI port, a micro-USB cable for syncing/charging/powering the dock, and a USB host port, for keyboards, mice, etc.
Samsung's devices, from a functional standpoint, seem perfect for UbTouch's offering of the convergence with the desktop functionality, but their specs don't fit it. The specs are catered to a simpler crowd, as Samsung's done for a while. The company's that DO offer the specs for it have skimped on things, or at least, they've not bothered to mention that they can do simultaneous display output with USB host functionality, because we haven't seen docks that have such things.
A few years ago, backing to the HTC Evo 3D and 4G LTE, that device offered a dock, or KiDiGi at least, with an HDMI output and a microUSB for powering the dock and charging. Custom ROMs make it possible to use USB host, amazingly, but I need to wonder where we are that we aren't seeing docks more.
I believe I can guess the answer: Miracast. That's right. The screen casting feature. They don't look to HDMI and docks with it because of the fact that, with a small plug-and-forget dongle or the like, you can just wirelessly cast your screen. You don't need a keyboard and mouse, no bluetooth and junk. You sync it, you send it, you use it, and that's that.
Because of this, and the fact that only Canonical, and the companies behind them, believe in this convergence right now, I can't say it's a surprise that no one's trying to bring on this expanded environment through their phones, with a dock that, having it set up, allows that convergence.
Maybe I'm missing something. Who's got a device and dock, and who's experimented with Ubuntu Touch, assuming it was ever part of the choice for your device? And is it a Samsung?
I've been using Ubuntu on my Nexus 4 since February. While you are right that there currently aren't too many devices which have pins for a dock, it would not bring any benefits to the Ubuntu Touch experience if there were, as Ubuntu hasn't reached convergence yet. Moreover, the work on Unity 8 for the desktop hasn't even started yet (besides their initial creation of a version of Ubuntu which runs Unity 8 and Mir but looks like the phone/tablet version). The work to create a desktop UI for Unity 8 will start after the release of 14.10. Let's see when we will get full convergence.
(What is, however, already converged are apps. You can already install the Ubuntu core apps on your Ubuntu desktop.)
Sent from my awesome Ubuntu Touch device using the Forum Browser app
I have no dock, but I still use an S3 i9300, will be upgrading to an Xperia Z3 sometime this year, but I don't' think the Sony dock is anymore than a charging stand, which seems to be an utter waste to me.
Docks are mostly useless for current phones. With Ubuntu we hope to change that.
Sent from my awesome Ubuntu Touch device using the Forum Browser app
A 'dock' is as simple as a usb cable while charging or even a link though bluetooth/wifi.
Personally I am looking forward to linux based ability on a phone.
I really want to edit the deadzones on the ipega 9023 telescopic bluetooth controller. I have seen very little information regarding this gamepad (and if it is even possible to adjust the deadzone successfully at all).
All I know is that I have to edit the .kl file for the ipega 9023, but I can't find the .kl file for this device at all. All I have to go on is the following:
First download root power explorer
Mount rw
Go to root
System/usr/keylayout
Search for your controler id vendor if u cant find it just go through all of them till you find this
# Left and right stick.
# The reported value for flat is 128 out of a range from -32767 to 32768, which is absurd.
# This confuses applications that rely on the flat value because the joystick actually
# settles in a flat range of +/- 4096 or so.
axis 0x00 X flat 4096
axis 0x01 Y flat 4096
axis 0x03 Z flat 4096
axis 0x04 RZ flat 4096
I wnt to the directory above and found nothing for the ipega. I also installed a terminal emulator and typed cat /proc/bus/input/devices to see all connected devices. I saw info on a device called "Broadcom Bluetooth HID" with vendor 1949 product 0402, but I saw no .kl file at all with that vendor id or product id.
Has anyone successfully calibrated the ipega 9023 and edited the deadzones at all? Should I just give up and deal with the deadzones?
Search this thread here https://forum.xda-developers.com/showthread.php?t=2033780
Just search for your specific controller. I'm sure someone has already configured your controller, also with the correct vendor ID and product ID as they did mine, the file I found also had the Vendor ID as 1949 and the Product ID as 0402, but my controller is the iPega PG-9021.
I also read somewhere in that thread there is a tutorial to make your own .kl file. Worth a look!
Ok, thanks for the info!
Don't bother, the dead zones on the Ipega controllers are hard coded into the microcontroller on the gamepad itself. Yes Android keylayout files can then add their own additional deadzone, which is what you're looking at, but lowering it from 4096 won't do a damn thing because the Ipega's deadzone is already MUCH larger than that.
moeburn said:
Don't bother, the dead zones on the Ipega controllers are hard coded into the microcontroller on the gamepad itself. Yes Android keylayout files can then add their own additional deadzone, which is what you're looking at, but lowering it from 4096 won't do a damn thing because the Ipega's deadzone is already MUCH larger than that.
Click to expand...
Click to collapse
yeah, i've been stuck with the same problem also. i've read somewhere that relodering a ps3 analog stick helped with the problem, but not much. i wish there was some way to fix the deadzones, the gamepad would be perfect
lukas.trop said:
yeah, i've been stuck with the same problem also. i've read somewhere that relodering a ps3 analog stick helped with the problem, but not much. i wish there was some way to fix the deadzones, the gamepad would be perfect
Click to expand...
Click to collapse
Sorry to resurrect an old thread. New ipega offering on the market. Ipega 9083. Can't find any info on deadzone improvement or changes. Form factor is better than 9023 so maybe they tweaked internals as well. Any one want to gamble?
i threw my 9023 in the bin it was terrible
Canadave1 said:
Sorry to resurrect an old thread. New ipega offering on the market. Ipega 9083. Can't find any info on deadzone improvement or changes. Form factor is better than 9023 so maybe they tweaked internals as well. Any one want to gamble?
Click to expand...
Click to collapse
Hi, just saw this new model myself and was looking for the same info. In the end I finished ordering it since it's not so expensive (which is not really a good sign per se, I should add). Should arrive in about a week, I'll let you know then! Fingers crossed!
Definitely post back. If you don't mind me asking what will you be using it on and what will you be playing?
Sent from my SHIELD Tablet K1 using Tapatalk
Canadave1 said:
Definitely post back. If you don't mind me asking what will you be using it on and what will you be playing?
Click to expand...
Click to collapse
It'll be coming from China, so it'll take more than expected (should arrive by the end of the month, I could swear it was a Prime product so I thought it was a next-day deal, but oh well).
The main thing is that I fear it could be a rebrand of another pad I tried in the past, the STG-ONE (look for it on Google) which was utter **** as not only it had the same deadzone troubles, it also didn't record analog sticks clicking (L3 and R3 inputs, in other words) even if the sticks clicked themselves, and bluetooth connectivity was completely unreliable.
Sure it looks identical, but anyway for 30 euros or so it's a test I can undertake.
EDIT: I've tried the STG-ONE again just to be sure and it's not as ****ty as I remembered, the deadzones are a bit better than i remembered (but still difficult to use in aiming for FPS games, tried on Dead Trigger 2), but the L3/R3 thing is a bummer. I'll try again the PG-9023 as soon as it charges enough, to see STG-ONE deadzones are at least better than its ones, or if they're the same.
Plan is to use with my Galaxy Tab S2 with Moonlight to stream PC games on it, the streaming works surprisingly well and is almost completely lag-free (works better on my S9 but i prefer the bigger screen). Also emulators, of course, MAME in particular, but such old games don't usually need analog sticks so the pads I already own are more than enough for them.
brigcam said:
I'll try again the PG-9023 as soon as it charges enough, to see STG-ONE deadzones are at least better than its ones, or if they're the same.
Click to expand...
Click to collapse
Tried it. In hindsight, they pretty both suck. Will update when the PG-9083 arrives!
Hello everyone,
so, the PG-9083 arrived a couple days ago, but I've found just now the time to write here.
TL;DR: The analogs still suck, unless you connect the pad with an OTG cable and your phone supports Xbox 360 pads
So as soon as the package arrived I connected the pad to an USB cable coming from my PC, and I noticed the pad got recognized as an Xbox 360 controller. Didn't care much about it at that moment, but it actually was an important detail.
So I bluetooth connect the PG-9083 to my Samsung Galaxy Tab S2 and after many tests the conclusion is that the analog sticks still suck. I even rooted the tablet and tried messing up with the keyboard layout files, but even changing the deadzone settings there didn't improve anything.
Then, I don't even remember why, I connected the PG-9083 directly to the Tab S2 with an OTG cable. The tablet didn't recognize the pad (for some reason Samsung didn't include Xbox 360 gamepad drivers in its Tab S2 and its Galaxy S9, which are the two devices that I own), but then I tried starting Moonlight (which is the main reason I'm interested in an Android pad) which has an internal custom Xbox 360 driver, and lo and behold, it worked like a charm, with the analog sticks performing perfectly.
So some final considerations:
- It seems it's a software problem rather than a hardware one, although it seems to be on the driver level and not on the keyboard layout one
- Even when using the faulty bluetooth mode, I achieved some good results in Shadow of War (again, streaming it from my PC by using Moonlight) by reducing the stick deadzones to zero in the game's settings. Why does it work when changing the settings in-game, but not from the keyboard layout file? No idea!
- Can't exclude it could be some quirk in Samsung devices
- I've tried the OTG method just with Moonlight, can't say if the sticks would be fine also with other apps or with devices that natively support Xbox 360 pads
- The sticks are fine when connected to PC, both via USB (in which case the PG-9083 acts as a standard Xinput, Xbox 360 pad) and, surprisingly, via bluetooth (in which case the PG-9083 acts as a standard DirectInput pad, I had to try this with the first Dead Rising since most recent games seem to accept Xinput pads only)
- So which other Android pads can work as an Xbox 360 pad when used via USB? Our old friend the PG-9023 doesn't, and neither the STG-ONE (surprisingly, since the PG-9083 seems a relabel of it). PG-9055 also works via USB (but the USB cable must be placed on the left handle, making it impractical to use when connected). Good old PG-9037 also works via USB. Mars Gaming MGP1, nope.
So I hope this was useful and maybe could shed some light in how Android handles gamepads and maybe inspire someone to write some custom driver to fix everything?
Cheers!
I wanted to post up on this thread that I too just received a pg-9083 and tried it out with my nvidia tablet.
It is exactly as brigcam says. The bluetooth mode on Android has the deadzone issue but the PC usb method does not. I did not try PC Bluetooth or Android OTG.
So who would need to fix this??? I emailed iPega but don't expect a helpful resolution. I will try tincore with a rooted tablet i have to see if it can change the deadzones, but I don't want to root my k1.
brigcam said:
Hello everyone,
so, the PG-9083 arrived a couple days ago, but I've found just now the time to write here.
TL;DR: The analogs still suck, unless you connect the pad with an OTG cable and your phone supports Xbox 360 pads
So as soon as the package arrived I connected the pad to an USB cable coming from my PC, and I noticed the pad got recognized as an Xbox 360 controller. Didn't care much about it at that moment, but it actually was an important detail.
So I bluetooth connect the PG-9083 to my Samsung Galaxy Tab S2 and after many tests the conclusion is that the analog sticks still suck. I even rooted the tablet and tried messing up with the keyboard layout files, but even changing the deadzone settings there didn't improve anything.
Then, I don't even remember why, I connected the PG-9083 directly to the Tab S2 with an OTG cable. The tablet didn't recognize the pad (for some reason Samsung didn't include Xbox 360 gamepad drivers in its Tab S2 and its Galaxy S9, which are the two devices that I own), but then I tried starting Moonlight (which is the main reason I'm interested in an Android pad) which has an internal custom Xbox 360 driver, and lo and behold, it worked like a charm, with the analog sticks performing perfectly.
So some final considerations:
- It seems it's a software problem rather than a hardware one, although it seems to be on the driver level and not on the keyboard layout one
- Even when using the faulty bluetooth mode, I achieved some good results in Shadow of War (again, streaming it from my PC by using Moonlight) by reducing the stick deadzones to zero in the game's settings. Why does it work when changing the settings in-game, but not from the keyboard layout file? No idea!
- Can't exclude it could be some quirk in Samsung devices
- I've tried the OTG method just with Moonlight, can't say if the sticks would be fine also with other apps or with devices that natively support Xbox 360 pads
- The sticks are fine when connected to PC, both via USB (in which case the PG-9083 acts as a standard Xinput, Xbox 360 pad) and, surprisingly, via bluetooth (in which case the PG-9083 acts as a standard DirectInput pad, I had to try this with the first Dead Rising since most recent games seem to accept Xinput pads only)
- So which other Android pads can work as an Xbox 360 pad when used via USB? Our old friend the PG-9023 doesn't, and neither the STG-ONE (surprisingly, since the PG-9083 seems a relabel of it). PG-9055 also works via USB (but the USB cable must be placed on the left handle, making it impractical to use when connected). Good old PG-9037 also works via USB. Mars Gaming MGP1, nope.
So I hope this was useful and maybe could shed some light in how Android handles gamepads and maybe inspire someone to write some custom driver to fix everything?
Cheers!
Click to expand...
Click to collapse
Anyone try an Xbox one or other "good" controller paired to their tablet or phone using bluetooth? In words is the deadzone problem android based foe any controller over bluetooth or specific to the ipega controller?
Sent from my SHIELD Tablet K1 using Tapatalk
So, I have tried the Nvidia Controller 2017, and it works great ofc. Don't have any other controllers to try unfortunately.
Other weird things:
1. If I open up my gamepad tester app I can see that the hardware is registering the axis values of the sticks with no deadzone, so the hardware is working properly. So I don't get where in software the deadzone is being enforced. Earlier posters said that changing the .kl files do nothing, and anyways I don't want to root the tablet and lose access to other apps.
2. I connected the controller to my clamshell Nvidia portable and there are no deadzone issues! Admittedly there's no use for the controller in this context but why does it work on this device and not the other??? Is it because of the Android versions?
Canadave1 said:
Anyone try an Xbox one or other "good" controller paired to their tablet or phone using bluetooth? In words is the deadzone problem android based foe any controller over bluetooth or specific to the ipega controller?
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
The only reason I can think of is that its trying to emulate a keyboard WASD instead of a joystick or its in some conflict with the keyboard selection when connected via bluetooth. The DS4 controller has no issues with deadzone on the gamepad tester via Bluetooth. Its actualy detected as a wireless gamepad and has a gamepad logo on the bluetooth screen. That being said I can be totally off and android has other issues with bluetooth
Canadave1 said:
Anyone try an Xbox one or other "good" controller paired to their tablet or phone using bluetooth? In words is the deadzone problem android based foe any controller over bluetooth or specific to the ipega controller?
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
Its an ipega issue. With xbone controller over Bluetooth there are no analog stock issues. Games control like being played with gamepad on the PC or console.
I'm now using my Shield K1 with a clip that attaches to my xbone controller. Too bad since I like ipega form factor.
Sent from my SHIELD Tablet K1 using Tapatalk
I see that iPega have released an updated version of the PG-9083 controller. Any improvement with this dead zone issue?
I got the PG-9083S (which I assume is the updated version) this afternoon and the dead zones are massive and not configurable in any way obvious to me. Galaxy Tab S6+, tried a bunch of FPS games with steam link and game pass cloud streaming. Playable but very much still an annoyance with this hardware.