2012
DroidPad 2.0 Beta – testing needed
Android Development DroidPad Linux Windows
I’m getting close to releasing DroidPad 2.0 – a completely new version with more features and greater stability. To make sure that everything is working, I’m releasing a beta version for testing, to remove any bugs before final release.
If you would like to test this version then downloads are available below. If DroidPad does crash while running it would be very useful to file a bug report (either for the PC part or the Android part); I can then see where it went wrong and fix it.
Downloads
Android
The Android part can be downloaded from the Android Market – search for “DroidPad 2.0″. The old version doesn’t have to be uninstalled.
Please report bugs through the Android bug reporter.
Windows
NOTE: This new version doesn’t currently work with Windows 64-bit. If you have problems installing the drivers then this is most likely the cause.
First, the old version of DroidPad will have to be uninstalled (PPJoy is redundant and can be uninstalled too – if not prompted to do so during DroidPad’s uninstall, remove it now). Make sure the old version of DroidPad is completely removed from your PC before proceeding.
Next, download the new version (link below). This new version does not require PPJoy at all, and should install automatically.
Download DroidPad 2.0 Beta for Windows
Reporting Windows Bugs
If something goes wrong or doesn’t happen as expected, please file a bug through the PC bug reporter. If possible please attach the log files; on Windows XP they are located in C:\Documents and Settings\<Username>\Application Data\droidpad, on Windows 7 in C:\Users\<Username>\AppData\Roaming\droidpad.
Linux
DroidPad 2.0 for Ubuntu can be installed using the PPA ppa:w-shackleton/droidpad-daily. This contains latest versions of DroidPad and will be updated with the latest versions.
Installers for other distros aren’t currently provided however a source package can be downloaded here and built manually.
Bugs should also be reported through the PC bug reporter, however please say that the bug is being reported for Linux.
RSS Feed
ola mais como eu uso este voce nao postou para a versao 2.0 o manual ajuda ai como vou achar o ip
not working in usb mode
connection type? wi-fi, bt, usb?
The driver with the sign-code signature is required.
Win7x64
Can you make some better layouts for this? I’ve been trying to use these layouts to play platformer-shooters, and sliders are crap for this compared to joysticks. I’d like dual joysticks, but tilting+joystick was ok at least in the old one.
For the game I’m playing now, Mari0, I need 6 buttons and two joysticks –or 10 buttons and 1 joystick– to actually play. I tried layout 5, but the random useless toggle buttons get in the way. They’re only good for the run function, and even then, setting it that way makes using a fire flower a pain in the ass.
Couldn’t you make some sort of automatic layout, where you decide how many buttons, toggle buttons, sliders, and joysticks you want and it builds it for you? Let me code it myself using GridLayout in Java or something, I don’t care! I just want some customizability!
I cant dload from the App store,can you pass a SlideMe link instead?
Tried testing droidpad-driver-2.0.zip, cant figure out how to compile it.
The driver is compiled using the Windows DDK, however I would strongly recommend using the prebuilt version which comes with the installer unless you need to change parts of the driver.
How to use USE mode??
Oh Sorry not use node.. USB mode
Downloaded 2.0 for Windows yesterday and for Android. It works perfectly. You might as well just release it now, there isn’t a single problem. It found my device in under a second too..
Aaron, there are still some problems on 64-bit Windows; DroidPad will be released after this.
Ziz, DroidPad 2.0 will allow you to save some files to the SD card describing custom layouts, and I might add a proper GUI editor in the future.
Mine stop install at file WUD update
I hope my post is still relevant and this project hasn’t been abandoned yet. First and foremost, I would like to thank you, Digitalsquid, for making this great and solid piece of software. It’s one of those that ‘just work’ and I recommend it to everyone that landed on this site. So far I’ve spent hours with Colin McRae 2 (PC – WinXP SP3; Galaxy S3 on Android 4.1 JB; Wifi connection), therefore I’ll happily oblige to the call of ‘testing needed’ and share my observations from my extensive ‘testing’ (read ‘fun’). I will of course concentrate on constructive feedback and things that would benefit from improvement, since the software itself works beautifully enough.
1. Breaking the Wifi connection is rather too easy. You just have to tap the ‘back’ button of the phone. If you happen to do that, you’ll have to quit the entire game, no less (with CMR2 and other windows-unfriendly oldies anyway), to restore the link via the PC-droidpad.
There are 2 solutions:
a) either never break an established connection until droidpad apk itself is exited (and even then I’d suggest there be a pop-up asking ‘sure to exit app?’), or
b) create a safeguard within the button view itself (and here I’d suggest that this safeguard be implemented in any case, if HW/Android limitations permit): button view will not react to short taps of the back/menu buttons at all, but rather long presses only. In the heat of a game, short taps on the wrong places certainly will happen sooner or later and you can imagine how it might tragically spoil a good track progress, for example.
2. Another issue related to accidental short-tap on phone HW buttons in the button view is that the ‘menu’ button will invoke the calibration pop-up which only needs to be tapped again to go ahead. Again, since you’re definitely not looking at the phone while playing a fast game, you might (and will) unknowingly recalibrate your droidpad a few times causing unpredictable steering, obviously.
The solution:
Do not map the ‘menu’ button in the button view to any function at all and move the calibration option to any other screen in droidpad.
3. I’m uncertain about this last point in regards as to whether it’s the design of droidpad itself or it’s related to Android/Wifi/CMR2. Namely, the buttons don’t react on very short taps. When shifting gears, I tend to tap very shortly on my selected shift up/down buttons. The button will turn white meaning that droidpad indeed registered the tap, but the in-game gear won’t shift. At this point I realize this is a clear issue with CMR2 itself, therefore I’d suggest droidpad would give you the option of tweaking the MINIMAL LENGTH of SIGNAL passed on to the virtual joystick. This, I think, could be implemented either in the Android or PC half of droidpad. And it would help immensely with unresponsive games.
Finally, I will state the obvious and name the functions that are dearly missed:
USB mode
Custom layouts with a nice graphic UI
Win x64 compatibility
Force feedback
That’s all, folks. I’m certainly looking forward to the full droidpad 2 version and hoping my suggestions will be heard at least to some extent. I realize also that a lot of people have downloaded dp and are happily using it as is, but I also tend to think more feedback would be useful to the dev to refine the behaviour of the apk. So everyone, please, feel free to build on my feedback and provide yours, or even confirm (or dispute) mine, it will certainly help Digitalsquid. Take care!
Hey, excellent job !
But i can’t get buttons 9 +.. to work like i did in older version
Any idea why it might happen ?