When I connect my bluetooth keyboard to my infuse I get a mouse pointer in the middle of the screen. Appearently this is new with gingerbread.
Since no one on the planet knows how to get rid of this pointer, is there any way of changing the look of it? Other threads suggest looking in framework-res.apk for an image, but there's no resource in the apk that has to do with the pointer.
I'm amazed that most of you guys can write apps to make your phones do somersaults, but no one has any idea how to change or remove this "pointless" pointer.
MikeyFTL said:
When I connect my bluetooth keyboard to my infuse I get a mouse pointer in the middle of the screen. Appearently this is new with gingerbread.
Since no one on the planet knows how to get rid of this pointer, is there any way of changing the look of it? Other threads suggest looking in framework-res.apk for an image, but there's no resource in the apk that has to do with the pointer.
I'm amazed that most of you guys can write apps to make your phones do somersaults, but no one has any idea how to change or remove this "pointless" pointer.
Click to expand...
Click to collapse
Never tried a bluetooth keyboard but pairing a bluetooth mouse to a stock froyo Infuse (and any other ROM I've tried it with, Froyo or GB) gives you a mouse you can move around and control the phone with. If you have one, you could try pairing it, moving the cursor out of the way and going about your business. Just a thought.
im not sure, the keyboard i pair with my phone has a touchpad for the pointer, it's not pointless. maybe froyo could detect if the keyboard had support for a pointer and gb doesnt discriminate? i really have no idea. ive never seen a complaint for this and that's probably why nobody has looked into a mod for it.
Have you tried any different ROMs?
Sent from my SAMSUNG-SGH-I997 using XDA App
Wow this went downhill fast. I assume you've already had a look here as it was fairly high in my google results but if not, there are some options in this thread.
http://forum.xda-developers.com/showthread.php?t=799079&page=12
Thread cleaned.
If this continues infractions are in order....
Thanks for the link, jvanlew. It was probably the most helpful thread on the subject. Just need to find the ellusive pointer.png for the infuse I guess. Not sure why it's not located in any of the framework apks like everyone else. I'm sure as more people get annoyed by it a solution will arise. Perhaps the android sdk has a MOUSE_MOVE of some kind. A tiny app just might do the trick.
Related
Please read after vote !!!!!!!!!!
If you use FW JF version with multi-touch (JF1.4x) you will see these bug :
If you play some game, when you touch 2 fingers to the screen, the device understand that you touch 1 finger between 2 fingers
Because of it, when you use chompSMS, you will take mistake easily, sometime when using chompSMS soft keyboard, the screen vibrate longer and very inconvenience . I tried chompSMS on other phone use original FW of Google (without multi-touch) and chompSMS work perfect.
I sent some email to REM and JF to request an update without multi-touch, but they said it's not really need.
The multi-touch driver of lukehutch is not perfect. Thank for multi-touch and root phone, JF. But the multi-touch is not perfect and you should make an option to enable/disable it or make 2 update files : one comes with multi-touch and one without multi-touch.
funbacon said:
The multi-touch driver of lukehutch is not perfect. Thank for multi-touch and root phone, JF. But the multi-touch is not perfect and you should make an option to enable/disable it or make 2 update files : one comes with multi-touch and one without multi-touch.
[/B]
Click to expand...
Click to collapse
Are you seriously telling someone who dedicates his time on a volunteer basis what they should do? He is doing us all a favor, and he should do whatever he wants to, if you don't appreciate his work - don't use it.
Honestly, if you want a different ROM for your phone, because you aren't happy with the stock ROM or JF's ROM, either develop your own or find someone else to do it. But don't demand that JF does what you want him to.
Btw - the only onscreen keyboard I have used is in Steel, and it is just as accurate with the multi touch as it was before.
And, I for one love imperfect things, the world is full of them and life wouldn't exist as we know it if it were not for imperfections. So bring them on!
daveid said:
Are you seriously telling someone who dedicates his time on a volunteer basis what they should do? He is doing us all a favor, and he should do whatever he wants to, if you don't appreciate his work - don't use it.
Honestly, if you want a different ROM for your phone, because you aren't happy with the stock ROM or JF's ROM, either develop your own or find someone else to do it. But don't demand that JF does what you want him to.
Btw - the only onscreen keyboard I have used is in Steel, and it is just as accurate with the multi touch as it was before.
And, I for one love imperfect things, the world is full of them and life wouldn't exist as we know it if it were not for imperfections. So bring them on!
Click to expand...
Click to collapse
Couldnt have said it any better myself, i have JFV.141RC33 W/ Multi-Touch and i have no problems using the onscreen keyboard or anything else for that matter. I think its just you OP.
This has already been addressed.
You can find the RC33 version without multi touch that I compiled here http://forum.xda-developers.com/showthread.php?t=480633
Please use the search function in the future.
daveid said:
Are you seriously telling someone who dedicates his time on a volunteer basis what they should do? He is doing us all a favor, and he should do whatever he wants to, if you don't appreciate his work - don't use it.
Honestly, if you want a different ROM for your phone, because you aren't happy with the stock ROM or JF's ROM, either develop your own or find someone else to do it. But don't demand that JF does what you want him to.
Btw - the only onscreen keyboard I have used is in Steel, and it is just as accurate with the multi touch as it was before.
And, I for one love imperfect things, the world is full of them and life wouldn't exist as we know it if it were not for imperfections. So bring them on!
Click to expand...
Click to collapse
I agree. I have used ChompSMS and I don't have a problem. I also have played some of the free version of the games (from glu) and I don't have any problems with the multi-touch. There are a lot of things that we would certainly want improved upon with the G1 however the multi-touch is one of the enhancements that we want to KEEP not to lose. I would personally like to see MT on Map and in pictures. Even if someone was to disable it why would he/she go through the trouble? I can see if several people urged him/her to do so and perhaps that's your point and goal of this thread but at the moment all of us are working on making it BETTER... not original. Multi-touch is in fact something that makes it better and sets it apart from stock. Bottom line... there really is no need.
justanothercrowd said:
This has already been addressed.
You can find the RC33 version without multi touch that I compiled here http://forum.xda-developers.com/showthread.php?t=480633
Please use the search function in the future.
Click to expand...
Click to collapse
Thank you very much. I search and didn't find. Thank you for the link.
i have been using chomp onscreen keyboard and have had zero problems.
multi-touch is da bomb.
There is no need for polls in a developement thread unlless you are a developer.
Thread will be locked.
I was wondering if anyone has tried the x86 android 1.6 port on their pc. Also, can we expect to see further development for this? Like custom ROMs, themes, and an online market of some sort? It seems awesome.
I don't know anything about but I'd like to hear about this too...
I've been able to get the froyo version to boot through Virtual PC just fine. The only problem I was having is the lag from manipulating the screens with my mouse or even anything that may require hardware acceleration. Its a great step in the right direction.. but at this time its only something to play with.
Sent from my MB200 using Tapatalk
I tested it a couple of times, but it's ment for subnetbooks, not PC.
But if I'd find people interested to create a PC-Distro, I'm there...
I didn't even know they made one! o: Could someone link me towards the right information
There's some YouTube videos and stuff on it, it's pretty neat!
My Xoom is running Tiamat ROM "hammerhead". I used the basic install from their post. That gives you some idea of what my software looks like.
I bought the Motorola Xoom camera kit to use a ps3 controller with my xoom. I used sixaxis controller for a while. Unfortunately that application does not support analog sticks. It will use them as the Dpad but it's a no go for certain games requiring both analog sticks. My hope was that this method DID prove fruitful with those games; However after plugging the ps3 controller in i noticed that the lights blink, but im unable to use the controller. It doesn't work with any of my emulators when trying to map the keys for playing.
The last thing i can think is that it's the ROM im using and I need to go back to stock, but i htoiught i'd try here first before spending a few hours reflashing stock roms and loading MicroSD card scripts.
Nv1dia said:
My Xoom is running Tiamat ROM "hammerhead". I used the basic install from their post. That gives you some idea of what my software looks like.
I bought the Motorola Xoom camera kit to use a ps3 controller with my xoom. I used sixaxis controller for a while. Unfortunately that application does not support analog sticks. It will use them as the Dpad but it's a no go for certain games requiring both analog sticks. My hope was that this method DID prove fruitful with those games; However after plugging the ps3 controller in i noticed that the lights blink, but im unable to use the controller. It doesn't work with any of my emulators when trying to map the keys for playing.
The last thing i can think is that it's the ROM im using and I need to go back to stock, but i htoiught i'd try here first before spending a few hours reflashing stock roms and loading MicroSD card scripts.
Click to expand...
Click to collapse
I can't help you with this but you could make your post title more descriptive of your issue to attract attention from gamers.
I appreciate the reply, though I wanted more Input than a gamer could possibly provide. The issue has been resolved though. I don't quite know what I did but hitting buttons on the desktop made it work. So I'm happy.
Nv1dia said:
I appreciate the reply, though I wanted more Input than a gamer could possibly provide. The issue has been resolved though. I don't quite know what I did but hitting buttons on the desktop made it work. So I'm happy.
Click to expand...
Click to collapse
I'm glad you resolved it. I doubt the problem had anything to do with the rom, but I had hoped someone that used those emulators would be able to assist.
Simple enough. After a long time of searching here and elsewhere, I have found no way to install the official HTC_IME keyboard on a ROM that doesn't already have it. Any attempts to do so just cause a Force Close upon trying to interact with it in any way.
And do not bother saying "just try _____ instead". If I wanted to try a different keyboard, I wouldn't be posting this thread.
I have a logcat that says "Unable to instantiate activity ComponentInfo", which I read is a problem with activities not being defined in AndroidManifest.xml. But unfortunately, the AndroidManifest.xml that comes with HTC_IME is junk. Trying to open it in any program either shows you what looks like non-western encoding, or it won't open it at all.
If anybody has any insight, that would be delightful. Either something I could try to make it work, or providing the logcat that shows all the errors that popped up, or something. Anything to finally get the Sense 3.5/3.6 HTC_IME working on our phones.
If nobody has any idea about this, does anybody at least know how I might go about figuring out any aspects of this problem besides the shot-in-the-dark Googling I've been doing trying to figure this out?
Just in case, I have attached the aLogcat file that I saved, filtered by the app to just show errors (which in this case, is only the errors generated by trying to access the keyboard via the Settings menu). If desired, I can generate and attach one for when you try to actually activate the keyboard via the Input Method operation.
I took the HTC IME apk from the HD revolution rom (system/apps) and pushed it onto my sensation's Virtuous Inquisition and I got it working except for the swype part.
I tried that. But unfortunately, CM7 is definitely missing libraries and/or other files needed by the apk file. Virtuous would be likely to have them because it's built from a Sense ROM, as opposed to CM7 most definitely *not* being built from anything but pure Android.
Someone had thought they found all the files needed to use the keyboard, but trying that did nothing for me, which means either more files are needed, or maybe something has to be done with the very messy and nearly uneditable AndroidManifest.xml file. But it seems that nobody on the forums has any idea. I had rather hoped that a developer might at least know, but of course I appreciate any input.
Would this work?
I'm not sure, but I'm certainly going to download it and give it a shot. Whether it works or not, thanks for the heads up. You've reminded me that I should also look around the forums of other qHD HTC phones in case somebody has figured something out in one of those.
Edit: Bah, of course the download link doesn't work. Every time I try, ESET kicks in and complains. Even when I shut it off. And once I finally got ESET to shut up, IE just refused to download the file anyway.
nvm i signed up for swype beta lol.
The user ukdutypaid request me and
LNEt - I don't found the profile yet
Robbie P
qazzi76
sergiocabraljr
With some words:
So can anybody tell me either a) why is BT HID so 'rubbish' on Android, ie why is it so rare that anybody seems to have got it to work e.g "Look. It's a massive problem, nobody really knows how to do it. Count yourself lucky that you've got found a GB build where it does work at all. Put the problem down and walk away"; or b) what a solution might be?
I've tried rooting round in builds, until I'm blue in the face but unless the *.so file either has a BT and or an HID in the file name, then I'm in the dark.
qazzi76 ; GregórioAxiaMagno and sergiocabraljr have found various solutions for GB builds I think and I know Samsung seems to have solved the problem. (I've seen videos of the Galaxy Nexus and it worked with no problems on an SII a friend of mine has).
Could it simply be a case of isolating and extracting the magic HID file and putting it into any/all custom roms, or it's a case (for some just to make it harder reason) that the BT files have to be recompiled for each and every build; as GregórioAxiaMagno has kindly pointed out with some of his work.
The holy grail I suppose is a set of files that can be uploaded to any build by apt, that resolve the lack of BT keyboard with every/any build.
Click to expand...
Click to collapse
:good:
The point here is, as always I say, the bluetooth stack on Android is a issue like call recording. And with this cenario, I think we can join people to help on this thread to post information about mods, replacements, hacking, apps and more. Until we find the optimal solution for the largest number of phones what we can. :fingers-crossed:
All is valid: kernels, modules, CWM, apps, tips, :angel: pray... any way of help.
I will ask for you people to post solutions here, and along of the time I will quote it in the second post of this thread.
Also, I want discuss with you about an optimal solution.
So keep this thread clean and focused only about bluetooth.
No, I and nobody thinks what the bluetooth is the world conquest, I want only use the totally potential of this "old" tecnology.
I know we have other tecnologies like OTG, but this thread must be only about how to deal with bluetooth in our daily use and experiences.
Lets start! :highfive: I have your help?
Please, press thanks instead to manifest your support with posts.
Current solutions
[app][beta][2.1+] myblucon v1.0 & mybluime v1.0 - bluetooth kit to hid devices
so you buy a bluetooth mouse but your ginger won't connect it?
Or you have an bluetooth keyboard and can't write at your ice cream?
Solution for:
* ST15a/i - GB/ICS
* Others
Click to expand...
Click to collapse
Bluetooth Keyboard problem resolved
Infamous "paired but not connected."
Solution for:
* Galaxy Note GT-N7000
Click to expand...
Click to collapse
[APP]Bluetooth Keyboard Easy Connect
A service which connects your bluetooth keyboard device.
Android 2.3 has support for HID devices but is not able to connect bluetooth keyboard devices correctly (yet).
This service automates the connection to your keyboard.
Solution for:
* Many Androids
Click to expand...
Click to collapse
Solving Bluetooth connecting problems
My Desire's bluetooth allways worked like a charme untill rooting REDUX 1,2
Connecting to any previously known device, or any new once for that matter, did not work.
Some grey hairs, upgrading to Redux 2.0 and many tries later I concluded some data must be corrupted somewhere.
Deleting the content, not the files, just the content of the following files did the trick, much to my relief.
Solution for:
* HTC - Redux
Click to expand...
Click to collapse
HID Bluetooth Device FIX for 2.3.5 and 2.3.6!!
Like many of you I was extremely excited to learn that android now supports HID devices and immediately rushed out to purchase a HID-BT Keyboard. Getting home, I fired up the phone and keyboard, entered the 6 digit code to pair them and saw the device connecting and disconnecting in an infinite loop. I was crushed and disappointed.
What went wrong? As stated above this is merely a workaround. But the problem lies somewhere between the kernel and broadcom chipset. This fix will reset your bluetooth pairings. It has been tested on my Samsung Galaxy SII I727 but it should work with any other device.
Solution for:
* Many Androids
Click to expand...
Click to collapse
resv 2
:good::good::good:
Congratz... keep going
Looking here:
/data/misc/bluetoothd/<A BLUETOOTH ADDRES>
I was thinking one of this files have a value to set for make an device manually connectable. Like disabling/enabling auto connect. So the market apps to HID devies will work better.
What do you think?
I was messing into the system and looking at this path
system\etc\bluetooth
Inside, we can found some confs, so I was editing and guessing about input.conf.
So I made some mods and I will test today, but if anyone know something more about or want to test, please a hand will be cool xP.
Regards.
EDIT: yeah nothing changes... haha