Dingoonity.org

Hello again everyone, first of all i really appreciate everyone that took some time and answered so kindly my message, even though the topic has gone a little off-topic. Anyway, i must admit that i'm excited about the DROID X360. I saw the video review from our friend qbertaddict, but then i got kind of sad about the controls. Later i saw that furan has released a patch that fix the problems about the controls, and hailrazer said that with this patch they work just fine, is that right? I think that Deen0X understood what i've been asking. What i want is one of these chinese and cheap handhelds, even though xperia play and others are better. Right now i really want the DROID X360 that seems to be the best choice, if you consider the price and the relation cost/benefit, and i would like to know from you guys, how well the controls responds today, and just another question: How is the emulation for the N64 and PSX on a scale from 0 to 10. Once again, thanks everyone. The users from Dingoonity are just great. 

Can a Droid X360 owner confirm it is the same size as PSVita or not? Yinlips isnt so cases are not compatible...  Would be nice if one of these "clones" actually was the same size!!!

It's the exact same size as the Yinlips.

BTW QB, FWIW, I don't understand why all these other people are saying the gamepad driver improved their scenario and it didn't do much for you. It only targeted button presses, not stuff like menu opening, etc.

I'll continue to try to tweak this. I posted info on reassigning what the buttons do. You might try disabling the menu button using that info and a hex editor to see if it fixes your problem (I suspect the lines are multiplexed and pressing the two buttons is shorting both lines for the menu button)

Can you clarify autofire? This is a game thing, so it shouldn't affect anything system-wise.

And the yinlips for comparison.

BTW QB, FWIW, I don't understand why all these other people are saying the gamepad driver improved their scenario and it didn't do much for you. It only targeted button presses, not stuff like menu opening, etc.

I'll continue to try to tweak this. I posted info on reassigning what the buttons do. You might try disabling the menu button using that info and a hex editor to see if it fixes your problem (I suspect the lines are multiplexed and pressing the two buttons is shorting both lines for the menu button)

Can you clarify autofire? This is a game thing, so it shouldn't affect anything system-wise.

I said it DID improve the controls but not enough to where it makes it better than any of the other devices.  There are still issues. In my OPINION this device is like the s5110 all over again most people don't want to spend the time to fix these issues. As for the auto fire I will edit it but we should not have to do all of this to get it to work at an acceptable rate. What I will do is buy a new one when I get back from my trip and see if I have the same issues with a brand new unit. Hopefully I will not. I will do a new review then. Can someone take theirs apart and see if the board design and layout is the same as mine? Don't think I appreciate the work being done my review is my first impression experience with the device

Quote from: furan on August 05, 2012, 09:33:45 PM

BTW QB, FWIW, I don't understand why all these other people are saying the gamepad driver improved their scenario and it didn't do much for you. It only targeted button presses, not stuff like menu opening, etc.

I'll continue to try to tweak this. I posted info on reassigning what the buttons do. You might try disabling the menu button using that info and a hex editor to see if it fixes your problem (I suspect the lines are multiplexed and pressing the two buttons is shorting both lines for the menu button)

Can you clarify autofire? This is a game thing, so it shouldn't affect anything system-wise.

I said it DID improve the controls but not enough to where it makes it better than any of the other devices.  There are still issues. In my OPINION this device is like the s5110 all over again most people don't want to spend the time to fix these issues. As for the auto fire I will edit it but we should not have to do all of this to get it to work at an acceptable rate. What I will do is buy a new one when I get back from my trip and see if I have the same issues with a brand new unit. Hopefully I will not. I will do a new review then. Can someone take theirs apart and see if the board design and layout is the same as mine? Don't think I appreciate the work being done my review is my first impression experience with the device

What does autofire have to do with anything? The driver synthesizes input from the gamepad. It doesn't know anything about autofire. Can you please clarify what you're doing to get autofire here, and why it has to do with anything? If it's just a setting in a game, then all it means is you're holding the button down.

In tubrografx 16 for example there is an option for 3 different degrees of autofire. If you hold down autofire which is B then press A while holding the autofire the keyboard pops up Also if you bring up a menu button and scroll down then switch to up it sometimes does not register unless you let go of the down first. There is a problem when rocking the d-pad. Your patch HAS HELPED with this but some twitch games still have an issue. Please realize that I am not trying to argue or put down your hard work in any way. I was just expressing my opinion. I will not continue posting in this topic as it seems to be headed off topic and I'm sorry if anyone took offense to anything I have said.

I'm grumpy. It would make things easier if you could keep the issues separate - I'm only focusing on one at a time, so everything is not going to get great right away. I've posted an updated driver in the x360 willgoo thread that may fix the menu problem, at the sacrifice of disabling the menu button (which I believe the two gamepad buttons are multiplexed with).

Quote from: furan on August 06, 2012, 09:55:02 PM

Quote from: qbertaddict on August 06, 2012, 04:38:37 PM

In tubrografx 16 for example there is an option for 3 different degrees of autofire. If you hold down autofire which is B then press A while holding the autofire the keyboard pops up Also if you bring up a menu button and scroll down then switch to up it sometimes does not register unless you let go of the down first. There is a problem when rocking the d-pad. Your patch HAS HELPED with this but some twitch games still have an issue. Please realize that I am not trying to argue or put down your hard work in any way. I was just expressing my opinion. I will not continue posting in this topic as it seems to be headed off topic and I'm sorry if anyone took offense to anything I have said.

I'm grumpy. It would make things easier if you could keep the issues separate - I'm only focusing on one at a time, so everything is not going to get great right away. I've posted an updated driver in the x360 willgoo thread that may fix the menu problem, at the sacrifice of disabling the menu button (which I believe the two gamepad buttons are multiplexed with).

I will have to wait a while to test it. I broke my device today cracked the screen. It will be a while until I get another.

If it's difficult to get a new one, nab this to replace it:
http://www.newark.com/kentec-electronics/k50dwn0-v1-f/lcd-module-5-800x480-touch-screen/dp/82T4653?Ntt=K50DWN0-V1-F

Remove the digitizer glass and desolder the thin cable coming from it from the flex pcb.
$48.00, but I think it's a better screen.