yashsingh1/xdaforums huggingface dataset:
[Motorola Droid X2] Emperorr:
changing my lcd density back to 240 fixed it!

That said sixaxis still doesn't work on my phone. Prerooted GB, it gets to where I can have the app connect to my PS3 controller, and it says controller 1 connected, but it will not respond to anything. Sixaxis is enabled as my input device as well. Went in to FPse and check to see if it would map my buttons to the hardware buttons and it wouldn't respond. I believe GB also will no longer work with the wii remote like it did in froyo, so maybe it is a similar problem.

Really hoping the dev gets this working for us. If anyone gets an email back from them pls let us know.
[Motorola Droid X2] wrestler1256:
Has anyone tried this on a rom other than stock pre rooted gb?
[Motorola Droid X2] AuxiliaryPie:
i haven't heard back yet but I will send them the link to this thread so they can see other X2 users are having problems.
[Motorola Droid X2] mastertwiz:
I'm having the same problem. I've established the blue tooth connection. I've successfully seen response within text message fields, but none of the emulators recognize the input.

I also sent an e-mail to tech support - I haven't heard from them in days. I'm running Nitro's Eclipse 0.2.1
[Motorola Droid X2] sir_earl:
Hi all,

I'm the dev of the Sixaxis Controller app. As was suggested earlier, I've been pretty swamped with emails up until now. I just wanted to let you know that I am looking into this issue, and would appreciate some testers to help determine what's going wrong here.

First of all, if anyone is able to get hold of a Wii Remote, I'd really appreciate you trying that out in emulators using the Wiimote Controller app. If the Wiimote Controller app is fine, it's probably something silly I'm doing, otherwise I suspect it is something in the stock roms for the X2.

Which brings me to the second question; can everyone let me know which rom you are running.

Thanks heaps, and I'm sorry this issue has taken me so long to get to!
[Motorola Droid X2] AuxiliaryPie:
I updated my review for your app to 4 stars simply because of this post. Thank you!

I CANNOT get ahold of a wii mote to try out

I am running Pre-Rooted Gingerbread (no other changes besides having root apps)
[Motorola Droid X2] AuxiliaryPie:
PM me if you need a tester or have any questions. Id like to help anyway i can
[Motorola Droid X2] Emperorr:
I have a Wii-mote, so I did a bit of testing..

The Emulators I tried are Fpse, N64oid, and Snes9x EX. The Wii controller software I used was "Wiimote Controller" by CCP Cre@tions.

So firstly I connected my Wii controller to my X2 using the wiimote software, it discovers my Wii controller without problem, and proceeds to report every button press in its list, showing it is functioning. Wiimote is enabled as input device. I tried Fpse, N64oid, and Snes9x EX, by going in to their input options and trying to bind my wii controller inputs with their hardware mapping options. All emulators were non-responsive in detecting my wiimote buttons as hardware inputs.

Interestingly enough, the built in Wiimote software provided in Snes9x EX would connect to my controller AND receive all of its inputs correctly, allowing me to play any of it's games with the Wii controller.

Now, before I switched to my current (I believe P3, the most popular ROM on this subforum) Pre-rooted GB 2.3.3, my wii controller was able to be read as hardware inputs on all emulators I tried. I was using Froyo 2.2.2 and had no problems using the Wii controller. I would be interested to see if anyone still running 2.2.2 can use this sixaxis software without any problems.

So it seems that the problem lies in our 2.3.3 not being able to read our bluetooth connections as hardware input devices, probably due to its updated bluetooth system files. This makes me wonder how Snes9x's built in Wii software gets it to work, regardless. I wonder if ALL 2.3.3 phones have this same problem? I know 2.3.4 has an even newer version of the bluetooth software and wonder if this fixes our problem?

If you (Sir Earl) have any additional things for me to try, let me know.
[Motorola Droid X2] sir_earl:
That confirms my suspicion that Motorola botched something in the 2.3.3 version. I don't believe it has anything to do with bluetooth, but rather they have somehow stopped IME's from working outside of the normal OS menus. The reason Snes9x EX is able to work is because it isn't using an IME.

On a hunch, can I get someone to try installing a different home screen app, such as ADW.Launcher or LauncherPro, then trying the Sixaxis app again. I suspect something in MotoBlur is trapping the input.
[Motorola Droid X2] Emperorr:
I was using LauncherPro Plus during my testing.
[Motorola Droid X2] sir_earl:
Hmmm... It must go deeper into the kernel then. I'll see if I can find the source code and try to find some answers or a workaround.

In the meantime, it would be good to get some confirmation from others that it works with 2.2.2, but not the 2.3.3 update.
[Motorola Droid X2] sir_earl:
Can someone try going to Sixaxis Controllers Preferences->Input Mappings->1st Controller mappings and setting the Up button to the 'SEARCH' key (be sure to disconnect and reconnect the controller for the changes to take effect). Next, make sure your Sixaxis is connected and set as the current input method. Run FPse and go to Settings->Input->Hardware keys, then tap UP, followed by pressing the search button on your phone. If it accepts the button and says something like 'Value: 84', then try running a game, and testing whether the up button on the controller is responsive in game. Also try pressing the search button on your phone to see if that is responsive. Make sure you try this with a game where the up button would produce a noticeable result!

Report back your results!

Thanks!

Earl
[Motorola Droid X2] Emperorr:
Just tried assigning the search key, as well as the back and home key to the up button and the X button and the emulator still didn't see input. Also I can't seem to get the controller to do any of the phone functions outside of emulators as well. So Back/Home/Search seems to do nothing to my phone.
[Motorola Droid X2] sir_earl:
So to confirm, even without using the controller, the back and search buttons on the phone cannot be bound in the emulator?
[Motorola Droid X2] cash_back:
I was able to get up to bind after pressing the search key it read Value: 84 like you said, but then inside of any of the emulators I could still not bind any keys
[Motorola Droid X2] sir_earl:
OK, so you managed to bind the search key in the menu, but are you saying that in game pressing the search key on your phone still does nothing? I'm not concerned with the sixaxis controller at the moment, just the physical keys on the phone.
[Motorola Droid X2] cash_back:
Oh I misunderstood you, when I after I bind the search key to up, it works in game on fpse.
[Motorola Droid X2] sir_earl:
Well that's promising - it means there is at least some hope!

So back to the Sixaxis controller, after setting a button on the controller to be the search key, and also setting the up button in the emulator to the search key, the emulator still just registers when you press the search key on your phone, but not when you press the mapped key on the controller, correct?
[Motorola Droid X2] juhde:
Willing to help in anyway possible, I just want this to work so bad. HDMI out + ps3 controller = epic game time.

Sent from OH MY GOD IS THAT A SQUIRREL!
[Motorola Droid X2] cash_back:
Correct, I have the up button bound to the search key in the 1st controller mappings under Sixaxis settings, and in FPSE i have up bound to the search button and when I try to use the controller I get no input, let me know if you need anything else.
[Motorola Droid X2] sir_earl:
Just to see if there is any point in me following a lead further, can I get someone to go to FPse->Input->Hardware keys, tapping 'UP', and then running this command via adb:

adb shell input keyevent 7

If the key binds, we may just have a way forward.
[Motorola Droid X2] cvmaas:
Doing this, I was able to bind UP to keyevent 7 in FPSE.
[Motorola Droid X2] mastertwiz:
sir earl, thanks for your help with this. Any luck so far? Do you think there is a promising solution for the Droid X2, or should I go back to the market for a refund?

Thanks again for being responsive to our posts, I hope you can get this working for our community!
[Motorola Droid X2] sir_earl:
I'm following the lead mentioned earlier, but it is proving to be not quite as straightforward as anticipated. I'll gladly refund anyone's money in the meantime, as I'm not sure how long the fix will take. Just flick me an email with your order details and I'll reverse the transaction.
[Motorola Droid X2] agentlotek:
You sir are the greatest kind of dev, and so you have won my full support and promise that I shall purchase your app as soon as it is droid x2 compatible.
[Motorola Droid X2] KurioHonoo:
+1 and I shall buy it too when it is compatible

Sent from my DROID X2
[Motorola Droid X2] Emperorr:
Sorry I've been away on vacation, If theres anything more I can do to help I'll be glad to. Thanks for your efforts so far sir_earl.

Also, I don't know why I was unable to assign Up to Home/Search button and have Fpse read it? Everyone else on prerooted 2.3.3?
[Motorola Droid X2] L2_n19h7m4r3:
I hope someone can find away around this soon would be a blast with hdmi out.
[Motorola Droid X2] sir_earl:
I got stumped with all my leads (mainly due to permissions around injecting key events into external apps), but have one more avenue to pursue. Can anyone with a Droid 2x or Droid 3 try running this command on their phones shell and print all the output here:

cat /proc/bus/input/devices

I'm hoping that there is a little consistency across devices with the low level input devices exposed. This will also help me with the touchscreen emulation I'm working on.
[Motorola Droid X2] juhde:
I: Bus=0000 Vendor=0000 Product=0000 Version=0000

N: Name="cpcap-key"

P: Phys=

S: Sysfs=/devices/virtual/input/input0

U: Uniq=

H: Handlers=kbd event0

B: EV=3

B: KEY=4 0 0 0 800 0 0 0

I: Bus=0019 Vendor=0000 Product=0000 Version=0000

N: Name="tegra-kbc"

P: Phys=

S: Sysfs=/devices/platform/tegra-kbc/input/input1

U: Uniq=

H: Handlers=kbd event1

B: EV=3

B: KEY=180 2180000 4 40000800 c16c0 0 61000000 0

I: Bus=0000 Vendor=0000 Product=0000 Version=0000

N: Name="qtouch-obp-ts"

P: Phys=

S: Sysfs=/devices/virtual/input/input2

U: Uniq=

H: Handlers=event2

B: EV=9

B: ABS=650000 0

I: Bus=0000 Vendor=0000 Product=0000 Version=0000

N: Name="accelerometer"

P: Phys=

S: Sysfs=/devices/virtual/input/input3

U: Uniq=

H: Handlers=event3

B: EV=9

B: ABS=100 7

I: Bus=0000 Vendor=0000 Product=0000 Version=0000

N: Name="proximity"

P: Phys=

S: Sysfs=/devices/virtual/input/input4

U: Uniq=

H: Handlers=event4

B: EV=9

B: ABS=2000000

I: Bus=0000 Vendor=0000 Product=0000 Version=0000

N: Name="als"

P: Phys=

S: Sysfs=/devices/virtual/input/input5

U: Uniq=

H: Handlers=event5

B: EV=20001

B: LED=100

I: Bus=0000 Vendor=0000 Product=0000 Version=0000

N: Name="compass"

P: Phys=

S: Sysfs=/devices/virtual/input/input6

U: Uniq=

H: Handlers=event6

B: EV=9

B: ABS=305ff

Sent from OH MY GOD IS THAT A SQUIRREL!
[Motorola Droid X2] sir_earl:
Thanks for that. Can I now get you to look in /system/usr/keylayout/ and post the two files tegra-kbc.kl and cpcap-key.kl.
[Motorola Droid X2] ihavenolife008:
Just wanted to put something out there: As someone earlier mentioned WiiMote on 2.2 reading as hardware inputs, and 2.3.3 it does not. I rememeber when i got the phone and it was on 2.2, under settings -> keyboard, it listed a "Hardware Keyboard" or something along the lines, making it seem like Moto bothced something in the original release software leaving in options for a hardware keyboard which wasn't on the phone. Maybe this has something to do with why that WiiMote worked on 2.2 just fine.

Figured anything could potentionally help and i was looking very foward to this myself when first hearing of Sixaxis connectivity. Could help to compare files or values from the commands he is asking us to check with a stock 2.2 install also.
[Motorola Droid X2] juhde:
Here's the 2 files as requested earl...
[Motorola Droid X2] sir_earl:
That looks promising. Was that on the Droid x2 or Droid 3? Also, which android version? 2.2 or 2.3?
[Motorola Droid X2] juhde:
Droid X2 2.3.3

The Droid3 doesn't have a tegra processor...

Sent from OH MY GOD IS THAT A SQUIRREL!
[Motorola Droid X2] sir_earl:
Hmmm, I wonder why the tegra-kbc.kl contains a full qwerty keyboard mapping.

Can you try the following commands via adb shell and let me know if they have any effect. You should run them with the phone unlocked and watch the phone for a reaction. They should hopefully send key presses:

su

sendevent /dev/input/event1 1 30 1

sendevent /dev/input/event1 1 30 0

You could also try replacing 30 (Letter A) above with 115 (Volume Up), 103 (D-Pad Up), 2 (Number 1), as per the tegra-kbc.kl file.
[Motorola Droid X2] juhde:
I opened xda and started a quote, used adb to issue the commands, the cursor was blinking in a blank area the whole time.

Volume up with either a 1 or 0 after it triggered the volume function.

Dpad up with 1 went up one line, with a 0 jumped to the top most field (which was the thread topic field, the cursor was actually in the post field)

Both A and #1 did nothing either way.

Sent from OH MY GOD IS THAT A SQUIRREL!
[Motorola Droid X2] sir_earl:
Can you try 'A' or '#1' again in an emulator with the bind key screen up (i.e. Where you are asked to press a key to bind to the emulator button).
[Motorola Droid X2] juhde:
I'm afraid I don't follow you.

You want me to launch an emulator and assign any button to up? If so, how? I don't actually have an "up" key.

If not, please explain more thoroughly.

Sent from OH MY GOD IS THAT A SQUIRREL!
[Motorola Droid X2] sir_earl:
Open say Snes9x EX and go to Options->Key Config, then tap the 'Up' item. It should then say 'Push a key to set'. Now run 'adb shell' and issue the following commands:

su

sendevent /dev/input/event1 1 30 1

sendevent /dev/input/event1 1 30 0

If it works, the 'Push a key to set' screen should vanish, and the 'Up' item should now have 'A' assigned to it.
[Motorola Droid X2] sir_earl:
As well as that, can someone try 'droid VNC server BETA' with an emulator. If the keys bind with that I think that will be the most promising lead. You will of course need a VNC client running on your PC, such as TightVNC or UltraVNC.
[Motorola Droid X2] juhde:
After following your instructions regarding binding a key in SNES9x EX I have to report that the attempt was unsuccessful... It simply sat there still waiting for me to enter a key press.

As per the VNC connection, after about an hour of trying to get the stupid thing to even connect. I gave up in frustration. Perhaps someone else will give it a go.

I'll try again later as well, I just need to step away from this thing for awhile...
[Motorola Droid X2] akaruna:
im about to get the x2 and was wondering if sixasix works on 2.2? thx

Sent from my DROIDX using the XDA mobile application powered by Tapatalk
[Motorola Droid X2] sir_earl:
Yes it should. If not, I'm happy to refund.
[Motorola Droid X2] L2_n19h7m4r3:
Tried droid VNC server, server starts but when I try to connect either through VNC or http, server stops. :\
[Motorola Droid X2] ihavenolife008:
Same here, also tried doing so through adb/usb connection, just stops.
[Motorola Droid X2] sir_earl:
Well hopefully that's nothing to do with the input handling, as I've nearly finished implementing the same approach... When it's up, I'll let you guys know and get you to test it out.
[Motorola Droid X2] cash_back:
It works with the new 2.3.4 ATRIX port.
[Motorola Droid X2] sir_earl:
Good to know that not all of Motorola's new roms have broken Input Methods!
[Motorola Droid X2] juhde:
Concerning the Atrix 2.3.4 port:

I can't reassign any key presses in a emulator, it doesn't register the controllers key press, but if I change the bind in the sixaxis app to whatever the emulator had as default it works beautifully.

So there is hope it can be fully functional, and with a little creativity you can actually use it.
[Motorola Droid X2] cash_back:
My bindings works perfectly with fpse.
[Motorola Droid X2] zack2o:
If it matters, scrolling works in the messaging application and system file explorers(like ASTRO) and all searching fields. It types nubmers when i hit any of the keys other than the D-pad and Axis
[Motorola Droid X2] sir_earl:
New version is up! I haven't tested it on the Droid x2, so fingers crossed! To enable the feature, you need to go to Preferences and enable 'Bypass IME'.

Any feedback welcome!
[Motorola Droid X2] agentlotek:
You telling me that nobody has tried the new version yet? Someone get on that A.S.A.P. This app is the only reason I'd root my X2
[Motorola Droid X2] L2_n19h7m4r3:
Are you kidding me? This is the only reason you'd root? Man, I feel sorry for you.

Anyway +1 can anyone confirm Sixaxis Controller 0.3 working on X2?
[Motorola Droid X2] agentlotek:
I don't feel compelled to do so..I mean I can already take screen shots with either adb or with "AndroSS" and I can tether with PDAnet...my phone is fast enough with stock and Go Launcher Ex... I had to root my Droid Eris for roms to replace the laggy Sense UI laden os...but with the X2 it feels fast enough.
[Motorola Droid X2] zack2o:
So i tried out this new version with the Bypass IME checked on Droid x2 and i can use the controller just fine in the menus in the app itself but not on the main screen where you start the server for the controller to connect for some reason.

EDIT: Works in N64oid on Droid X2 perfectly!
[Motorola Droid X2] agentlotek:
Can you check compatibility with Snes9xEX?
[Motorola Droid X2] agentlotek:
So, I decided to root my phone yesterday to try the updated app. After switching on the "Bypass IME" setting it worked flawlessly. Played "Killer Instinct" for hours on my 46" Vizio using the Snes9x App and an HDMI cable.
[Galaxy Tab Q&A, Help & Troubleshooting] Byrana:
Hi there,

I read through a couple of threads and found that some people have the same issues with the stock calendar app as me. I mean the one that comes from Samsung and can be found in stock rom and in overcome. I bought the tab for my business.

Unfortunately, the samsung calendar app is pure garbage to say it friendly. Not all calendars show up, they all have the same color and if you add an appointment in your tab, edit it in google calendar on your PC you mysteriously end up with 2 appointments on your tab.

Yesterday, I switched to CM7 to check out how the calendar works in that mod. If CM7 by technomancer wouldn't be still in beta I'd stay on it for obvious reasons. The calendar works perfect and like a charm. All gmail calendars show up, even the ones from my wife. They all have the colors I selected in gmail calendars on my pc. The syncing works perfect.

I was wondering if someone could port that app into the Overcome Rom, because I have no clue how to do that?

Google should do quality assurance to make sure their functions work right.

Any help would be greatly appreciated because I use pure calendar widget and it gets the entries from the calendar app. Calengoo, is okay but the widgets suck.

I am willing to donate some money for a working port :)
[Galaxy Tab Q&A, Help & Troubleshooting] Byrana:
Well I tried a little bit around and got some things working. I took a calendar and googlecalendarsyncadapter.apk from a 2.3.3 aosp rom and copied it into system/app fixed permissions and did a reboot.

Guess what the calendar is working. You'll get all different colors and the sync works totally right. Unfortunately there's only one problem. The calendar will crash when you select what calendars to sync...you have enough time to select them but then it crashes. I think this has something to do with the emailprovider.apk from samsung. I changed it to an aosp version but then the calendar crashes all the time.

There have to be done some changes on the emailprovider.apk to get it all going but I have no clue what it could be. It seems there is a limitation on how many calendars can be synced.
[Eee Pad Transformer General] EizenHower:
So my company bought Ipad 2's to integrate with our business. I suggested we get android tablets because they work better. So end result they didn't listen and bought them anyway. We have smart tags all over our showroom that play videos about our products. They wanted to use the Ipad to let the customers walk around and use the tags to watch the videos. So yesterday one of the managers tries to use it and I notice he looks frustrated. So I pull out my Transformer walk over there and scan the tab and the video plays smooth as butter. He looks at me and says WTF. I said oh Steve Jobs doesn't believe in flash. Hmm those ipads are great huh and walked away. PWNED!
[Eee Pad Transformer General] H3llb0und:
Nice!

My Transformer and my DHD pwn iPads and iPhones almost on a daily basis at my workplace.
[Eee Pad Transformer General] RRtexasranger:
I don't see why business would pick an iOS tablet over Android. iOs is so restrictive on what you can do and prevents you from being productive in the process.
[Eee Pad Transformer General] ryan stewart:
Have you ever worked in IT in a business? Some manager with AP sign off ability makes snap decisions on hardware/software, expects IT to support it and then often it just ends up in a storeroom somewhere until its broken, sold or "lost." Its never touched again because the original idea was abandoned or IT eventually applied what was really needed.

Not that I have any personal experience or anything....
[Eee Pad Transformer General] Ellingsoc:
Ya my boss has a ipad as well and really liked this thing when I took it into work
[Eee Pad Transformer General] rtadams89:
That is exactly why a business would pick iOS. Businesss' favorite devices are BlackBerries, not because they have the most powerful processor, best games, and super-quick facebook access, but because they can be remotely wiped/locked, every setting (from bluetooth to language) can be set via group policy, and everything going into/out of the phone (phone calls, texts, Internet access) can be monitored. And it has been that way for a long time.

When you are buying devices for your company, you want that control. iOS are probably second best in that aspect (and do pretty well with the right software loaded like MobileIron). Android is lacking. It wasn't until the last year (I think) that android officially supported "device administrators" and the ability to enforce pin usage and/or remote wipe. It's getting better, but before Android devices are allowed to access company file shares, Exchange servers, etc., they are going to have to improve significantly.

As a personal choice, I would take a Transformer over an iPad any day. If I was buying for my small business of 2-8 employees, it might be a toss up. If I was buying more than 10 devices though or if my business touched anything with PII or government-regulated data, I wouldn't touch Android.