yashsingh1/xdaforums huggingface dataset:
[Desire Q&A, Help & Troubleshooting] ieftm:
ok, got a bit further by playing with dbus.

First I connected the BT keyboard using the normal pairing system (entering 1234 as pairing code, then entering '1234 - enter' on the keyboard itself.

It said paired but not connected.

I went on to investigate:

./dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/965/hci0 org.bluez.Adapter.ListDevices
method return sender=:1.3 -> dest=:1.57
array [
object path "/org/bluez/965/hci0/dev_DC_2C_26_B4_3B_CC"
object path "/org/bluez/965/hci0/dev_00_09_DD_50_2F_E5"
]

Then getting properties for the BT keyboard:

./dbus-send --system --type=method_call --print-reply --dest=org.bluez /org/bluez/965/hci0/dev_DC_2C_26_B4_3B_CC org.bluez.Device.GetProperties
method return sender=:1.3 -> dest=:1.58
array [
dict entry(
string "Address"
variant string "DC:2C:26:B4:3B:CC"
)
dict entry(
string "Name"
variant string "Bluetooth Mini Keyboard"
)
dict entry(
string "Alias"
variant string "Bluetooth Mini Keyboard"
)
dict entry(
string "Class"
variant uint32 9536
)
dict entry(
string "Icon"
variant string "input-keyboard"
)
dict entry(
string "Paired"
variant boolean true
)
dict entry(
string "Trusted"
variant boolean true
)
dict entry(
string "Connected"
variant boolean false
)
dict entry(
string "UUIDs"
variant array [
]
)
dict entry(
string "Adapter"
variant object path "/org/bluez/965/hci0"
)
]
[Desire Q&A, Help & Troubleshooting] DJorgio:
Watching this thread closely, have been trying to get my BT keyboard working aswell, good luck in finding a solution.
[Desire Q&A, Help & Troubleshooting] paopaomj:
Hi,I wonder if this keyboard can works with my G1(donut) please?
[Desire Q&A, Help & Troubleshooting] yt8181:
I don't quite understand, if the keyboard can be used finally? how to use those codes?

sorry, I'm a beginner of those code things.
[Desire Q&A, Help & Troubleshooting] lnxtux:
There is no input device exposed via dbus in proprietary HTC (well, Broadcom) Bluetooth stack used in Desire. However, btld may be capable of dealing with the input devices. I guess we need to research the btld interfaces.
[Desire Q&A, Help & Troubleshooting] phi770:
i posted my results here bluetooth hid, whats missing? and here bluetooth hid, whats missing? Part 2

I think that it's just a config file or a missing service...

I would like to use a bluetooth mouse + keyboard on htc desire. I know it works on cyanogenmod (for example), but I really like HTC sync on Pays Rom...

Maybe anybody has a good advice ?? Senior devs, please... :)
[Desire Q&A, Help & Troubleshooting] ieftm:
It's not a config file.

Check out the Desire BlueZ sourcecode (froyo) that HTC released.

That gives hints on how they modified BlueZ to have it's own proprietary (broadcom) transport/communication layer.

The HID service is obviously missing from that. Now, if we could only -add- it :P
[Desire Q&A, Help & Troubleshooting] phi770:
Yeah, i just noticed that in /system/framework/services.jar - classes.dex from cyanogenmod there are a lot of strings like bluetoothHID whereas in the version from orig. Desire or Pays Rom there is nothing.

If we could just inject a bluetooth HID after booting manually to the list that the command "service list" outputs...
[Desire Q&A, Help & Troubleshooting] gatsu_1981:
BTW, in cyanogen mod 6 it is native. Just add a new Bluetooth device, insert a pin, then push the pin on the keyboard and press enter. No more script for us cm6 users.

I think that we even have mouse cursor visible on screen.
[Desire Q&A, Help & Troubleshooting] hackm0d:
I paired a Bluetooth mouse with my N1 that works fine otherwise with a computer, and a mouse pointer appeared and moved for what seemed like a second, then froze. I had to repair the mouse to get the pointer to move again.

Two other users have the problem.

Here is the CyanogenMod link: http://code.google.com/p/cyanogenmod/issues/detail?id=2268
[Desire Q&A, Help & Troubleshooting] phi770:
I decompiled classes.dex from framework.apk copied hid-snippets and compiled it again, inserted it into framework.apk and pushed it via the recovery console to the phone.

result: phone still boots, bluetooth hid still not working because of my lacking asm skills...

great tool to decompile here: smali
[Desire Q&A, Help & Troubleshooting] knightccs:
just subscribing
[Desire Q&A, Help & Troubleshooting] kubilay.demir:
@ccabreu

I have same keyboard.But i cannot connect it.

Must i use a non sense rom?

Used gscript but it gives a error like ; No Device found.
[Desire Q&A, Help & Troubleshooting] ccabreu:
Have to be a non-sense Rom.
[Desire Q&A, Help & Troubleshooting] Gurdjieff:
I have the same keyboard, with a wildfire, on a non sense rom it is working, with sense it isnt, what is the problem? What is missing from the sense?
[Desire Q&A, Help & Troubleshooting] dd4502:
Based on this success, is it possible to somehow adjust the datapool of ones bluetooth on say....an Evo that is rooted??
[Desire Q&A, Help & Troubleshooting] LeoNg628:
Oh you are very nice!! I am really look forward into this.

But it required ROOT....Hoping Desire HD also can rooted soon...
[Desire Q&A, Help & Troubleshooting] peterrus:
I own exactly the same keyboard. On my desire with Defrosted 6.0c everything worked out off the box. put keyboard in pairing mode. find it on phone, connect, enter 1111 as code. then press 1111 on the keyboard and hit the keyboards enter. done.
[Desire Q&A, Help & Troubleshooting] archongtv:
Hmm have anybody tried replace kernel module with that from working roms (same android build/kernel)?
[Desire Q&A, Help & Troubleshooting] marcopivetta:
Hi, Cabreu!

What a great tutorial. I followed all the instructions and, as you said, voilá, the keyboard has been connected like a charm.

Despite of that, I could not see it working, because I could not change the input method (I´m using an Xperia 10 mini).

Using the default input method, any character is send to the application; it only accepts characters from the touch screen.

Does anyone has an idea how to make it works?
[Desire Q&A, Help & Troubleshooting] blast0id:
just bumping this to keep it alive, would REALLY LOVE to have my XTBT01 working on my G2 running a sense rom... anything I can do to help? PLEASE let me know ASAP!!!
[Desire Q&A, Help & Troubleshooting] mcschweg:
Maybe you can help me out: I have also the exact same keyboard, managed to pair, but get the info (in BT Menu) that i am not connected. No matter what i try.

I went with finding, typing (any code will do) and retyping on kb.

My system is Desire root Oxygene 2.0 RC6
[Desire Q&A, Help & Troubleshooting] blast0id:
hey guys... guess what... if you want bluetooth HID keyboard on your Desire here's how...

1. install one of the Sense 3.0 roms that is GINGERBREAD based

2. push the settings.apk from the doubleshot rom

3. when you connect your keyboard it will now prompt you to enter a randomly generated 6 digit number, enter it on your keyboard only then press enter (kb).

4. boom, you're now connected!!!

worked for me on my G2, should work for you as well... I used RMK's Virtuous-Fusion rom (based on rider) and then pushed the settings.apk...

I'm not sure because I don't use rosie, I use LP+P, but you MIGHT lose the ability to set the lockscreen widgets by doing this, so my suggestion is to set those up first before pushing the settings.apk...

GOOD LUCK!!! Lovin' being able to use my stowaway bluetooth kb with gingerbread sense! w00t w00t!!!
[Desire Q&A, Help & Troubleshooting] Sulphy:
Tried all the suggestions in this whole thread... no joy on a desire with TCMixS 1.6.1 CM7 Hboot.....

keeping this thread alive :)
[HD2 General] vnb28:
I need help...i am having a problem w/ my HD2, when i my 3.5 headset attached to my phone i am able to use the phone fine. When i disconnect it i am able to use the phone to my ear for a couple of minutes and then I can't hear it anymore. i put the headset back in and out and the same thing happens.

Here is my question, if i manage to open up the phone am i able to disconnect the headset port completly and still be able to use the phone?

Any help would be great
[EVO 4G Android Development] awesomeindeed:
I'll be a guinea pig and try this out soon as my phone is done charging.

Quick question, though. Have you done this yet yourself? If you have, are you able to write to /system outside of recovery after flashing everything?
[EVO 4G Android Development] Land Master:
This is interesting and certainly worth watching.

So...after this procedure we are basically left with a

stock (1.47xxxx)

ROM?
[EVO 4G Android Development] jonathaflores:
trying this as soon the files finish downloading!!
[EVO 4G Android Development] whitslack:
The contents of your /system will be exactly as though you had never heard of xda-developers, with these exceptions:

/system/xbin/su is added

/system/bin/su (a symlink to /system/xbin/su) is added

/system/app/Superuser.apk is added

Everything else is identical to stock, and in fact, future OTA updates would apply without complaining (and rob you of your root, so always decline them!).
[EVO 4G Android Development] bprinehart:
Pardon my ignorance, but I didn't see it mentioned, will this bypass the "mainver" check that prevents me from reflashing the original PC36IMG.ZIP?

Thanks for you effort!
[EVO 4G Android Development] whitslack:
I actually did this process twice, back to back. So yes, I was able to flash the PC36IMG.zip linked in the OP directly over the latest 1.47.651.1 with the latest radio. Nothing complained of a MainVer.
[EVO 4G Android Development] bprinehart:
Dude...if this works...I'm going to hunt you down and kiss you. Or at least buy you a six-pack!! I'm dead in the water right now, I can boot into the hboot menu, or fastboot, but nothing else. Going to try right now!
[EVO 4G Android Development] Land Master:
WOW! Keeping my fingers crossed on this one. Its exactly what I was waiting (hoping) for.

Is NAND unlocked?

Assuming yes..... then we would still need to stick with ROM's that are based on the 1.47xx code correct?

The radio/wimax debacle would stick from this point forward?

Thanks!

Edit: Nevermind the NAND question. I re-read the OP and see that it is. Just install Clockwork and rock and roll...
[EVO 4G Android Development] whitslack:
Yes, I have. I made a backup of the su binary in another directory on /system, as a little insurance against a future stealth OTA update. NAND is definitely unlocked.
[EVO 4G Android Development] jonathaflores:
flashing 1st file the Pc file!!
[EVO 4G Android Development] whitslack:
Unless the ROM you're going to install comes with its own radio+WiMAX images (and you're confident that it actually installs them correctly), you would want to stick with ROMs that are based on the 1.47.651.1 system, yes.
[EVO 4G Android Development] bprinehart:
Damnit...no dice for me. Just got to the second checking PC36IMG.zip stage and then went back to hboot menu. Thank you for at least giving me a shred of hope for a second.
[EVO 4G Android Development] Land Master:
Excellent!! Thanks.

Honestly if this works I would hope the other Dev's just incorporate it rather than package a separate radio + WiMax. I have been following this for three days and I'm not confident in anything at this point.

Truly have my fingers crossed for yours.
[EVO 4G Android Development] whitslack:
What version of HBOOT are you running? (It will say at the top of the HBOOT screen.)

Have you tried going into FASTBOOT and flashing the mtd-eng.img to the misc partition?

If you have fastboot access, you can flash any image you want to any partition. You could even flash the system and userdata partitions to get yourself back into a working state. Try unzipping the PC36IMG.zip on your computer and using the fastboot utility to flash the system.img to the system partition and the userdata.img to the userdata partition.
[EVO 4G Android Development] jonathaflores:
i am already installing the last file!!! hopefully it works nd we get 4g, i live in a 4g city!!
[EVO 4G Android Development] whitslack:
*shrug* Really no credit is due to me. These files are almost straight from HTC. The only change I made to the OTAs was to add one line so they don't blow away the setuid-root permissions on /system/xbin/su.
[EVO 4G Android Development] awesomeindeed:
Flashing the last file as well... here's to hoping.
[EVO 4G Android Development] bprinehart:
hboot version: 0.79.0000

Whenever I try to flash, I get a signature verification failure, or a remote: not allowed

Any ideas?
[EVO 4G Android Development] jonathaflores:
We tried, 4g, went on scan and then went off!!

trying to update profile!!
[EVO 4G Android Development] frankenstein\:
OK, you have in essence completed both part 1 and part 2 of Toast's root method. your in good shape.

As for where you should begin in this process, that depends on a few things.

The first question is what ROM are you currently running?

If the answer is Flipz rooted .6 ota ROM then your most of the way to being ready to run the latest update. Flipz modified the build.prop to prevent the phone from applying HTC/Sprint released OTA updates to protect your root status. In order for this update to run you need to replace Flipz build.prop with the original one.

If you've removed any of the .apk and/or .odex files from the /system/app directory like unwanted htc or sprint bloatware then you will have to replace those files or the patch will fail.

If you modified the /system/lib/modules/bcm4329.ko file to enable wireless n networking you will need to restore the original file or the update will fail.

The ota is a patch that updates existing files. If those files are missing or altered from their original state the update will fail.

If your not sure about these things or your running a different ROM like DC or Fresh or ... then you will need to start at step one of this process.
[EVO 4G Android Development] Hero's Hero:
Worked perfect. Thank you.
[EVO 4G Android Development] tcd2004:
I used flipz rooted .6 OTA. I didn't change anything at all after it was done installing. How would I go about replacing the build.prop with the original one? After I do that, would I be safe to update to the latest software by flashing? And could I just wipe the cache and install or would I have to wipe the cache and do a factory reset?
[EVO 4G Android Development] Land Master:
The essence of this procedure is so simple why are you contemplating taking the chance? As frankenstein pointed out there seems to be too many variables that would need to be checked/verified. The purpose of this method is to keep things clean and start from a "known" point. This makes troubleshooting easier in any cases where problems pop up.
[EVO 4G Android Development] tcd2004:
Im aware it is simple, I was trying to avoid wiping my phone for the 2nd time this week when I just got everything back to normal
[EVO 4G Android Development] Land Master:
Ahh..Good point.

I guess I have just gotten used to doing a full wipe every time I flash and have become accustomed to backing up everything using different tools like titanium and MyBackup.

That's why I like what the OP had to say about going back to a "known" state. It just seems like most issues with any new flash always revolve around...did you wipe.

My .02
[EVO 4G Android Development] chandlerw88:
did this and lost my root and nand unlock, not looking like iama be able to get it back either

edit. lost nand unlock but still rooted.
[EVO 4G Android Development] Land Master:
Thats all that matters..Flash a new recovery and you are good to go.
[EVO 4G Android Development] chandlerw88:
alright im confused. Am i supposed to be able to use toast first method to get to recovery but it wont let me
[EVO 4G Android Development] Land Master:
I made the assumption that you thought NAND was NOT unlocked because you couldn't boot into a custom recovery. This was a mistake on my part as i should have asked before posting my reply.

"IF" my assumption was correct than this is the expected performance of this method. See my post(s) a few pages back regarding clockwork (ROM Manager) and RA recoveries and how to get them flashed.

If my assumptions is "NOT" correct, I would ask if you followed the steps in Post 1 letter by letter?

By your question above it appears as if you are stuck just performing the steps in the original post in which case more information would be required and I'm probably not the man for the job.
[EVO 4G Android Development] chandlerw88:
yeah iama take a look into clockwork. im pretty sure in my noobiness to android i made a couple mistakes that i probably shouldnt have. appreciate the advice.
[EVO 4G Android Development] fibrizo:
Went from Fresh 0.5.3, followed all the steps. Worked great, except at the end it really does flash the recovery back to stock, so I had to use clockwork recovery manager to flash back the amon recovery.
[EVO 4G Android Development] frankenstein\:
The original build.prop file and the update as built by Whit can be found here: http://xdaforums.com/showthread.php?t=714511

Sorry, I fell asleep...
[EVO 4G Android Development] chandlerw88:
yeah i tried the clockwork recovery and all i get now is the evo with the exclamation mark
[EVO 4G Android Development] redsolar:
*Does an uber happy dance*

I got it!! 4G is working again. After botched wimax w/ MAC address broken.

Instructions coming soon.
[EVO 4G Android Development] Cordy:
Thanks in advance my friend. I look forward to those instructions.
[EVO 4G Android Development] mpa4712:
Hold on let me go put my life on pause..

Excited!
[EVO 4G Android Development] redsolar:
I moved the discussion to a different thread to be able to keep a better track of all this

http://xdaforums.com/showthread.php?t=716694
[EVO 4G Android Development] mpa4712:
Red,

Have you actually seen the encryption keys in plain text? How many bits are they?
[EVO 4G Android Development] canteli:
Hello everybody,

I've been reading a ton in the last couple of days as, like many others, I managed to screw my wimax MAC with some improper update. Ever since then, whenever trying to connect, it would run through the loop "turning on, scanning, connecting to Sprint, turning off" endlessly. At the beginning I thought, like everyone, it was entirely related to the wrong address, so at first I run this method described in the thread "[GUIDE] Bad WiMax MAC? Broken 4G after update? Fix HERE!" to hardcode my original MAC.

Everything went smooth, meaning that my MAC did change and I could see it reflected "almost" everywhere. I checked all the usual spots, and everything was sounding(wimax_mtd, dsmeg, wimax_properties) but ifconfig -a would still show me the default MAC as the address of the interface. Nevertheless, it was correctly showing under About Phone/Hardware Information. Furthermore, under /data/misc/wimax I would have 2 tree.xml files, one for the real and one for the default MAC, and If i were to delete/move both, only the latter would regenerate. Bottom line, the MAC was changed almost everyone, but where evidently counts to have the correct one, as I would always have the default MAC tree.xml file coming back, and beside, the real problem is that while trying to connect to sprint, the interface would power cycle(if the MAC is wrong or the authentication credentials are wrong/missing it should just deny the access to the network, not impose a power cycle over the wimax interface).

Either way, I decided to try this other method suggested by whitslack, and I can successfully get rooted and updated to the latest system/radio/wimax as advertised...but that didn't change anything about the deadly wimax loop i was trying to fix since the beginning... I saw somebody else in this thread and others, intermittently reporting being victims of the same endless loop, but couldn't read a single post to address this issue...

Anyone has a clue, I mean a real clue?

Cheers
[EVO 4G Android Development] Nitro2985:
So I ran through the whole roll back procedure and reflashed everything. 4g still gets stuck "searching" for the network when I turn it on.

I also tried the procedure suggested here and all it did was get 4g stuck on "turning on" with the option to change it greyed out in "wireless & networks"

I'm at my wits end. I'm about to just reflash it back to stock ota and return the phone at this point.
[EVO 4G Android Development] jonathaflores:
We are stuck the only solution its to go back to stock and bring the phone to sprint, the unrevoked team say they were gonna have news tonight for us, so i am just waiting on those news, and if they dont work, ill bring my phone to sprint and act stupid!!
[EVO 4G Android Development] canteli:
I won't have to act stupid cause my phone is also exhibiting the screen separation issue with light leaking from the bottom(as I don't let myself miss A THING! :P) so the dudes at the store already know that as soon as a new unit gets in they'll have to swap pronto... But to go back to the issue, I've never used any moethod unrevoked-related....i was coming from a full NAND unlock "by toast", DC 3.2.2.1 and then some stupid, probably custom update for the wimax posted on the DC thread. I'll look into unrevoked, although, again, as far as I can tell, I never had anything to do with their method..So you also get the power cycle loop of the wimax interface?
[EVO 4G Android Development] jonathaflores:
yes i was coming from the full rooted 3click program, with the OMJ rom, but i flash the wimax update from Unrevoked, because my stupid self didnt wanted to wait for OMJ!!
[EVO 4G Android Development] whitslack:
It's worth a try to simply flash the OTA 1.47.651.1 update. It'll let you know if something's not right, and it won't touch anything in that case. If it applies without complaining, you're good to go. If not, start from the top.
[EVO 4G Android Development] sjwaste:
Has anyone noticed some new 4G behavior? Specifically, I'm noticing that at home where I have very weak signal, if it picks up 4G initially and drops, it won't try to reconnect. That might be a plus since it's not constantly trying to hand off between 3G and some 4G signal just above the cutoff threshold.

I will test this at work on Tuesday. In my office, I have 0 bars of 4G (just enough to connect though), but get full (3?) outside. I'll check to see if its locking and staying connected where coverage is good. Otherwise, potential bug there.

Not saying it has anything to do with this method - might be a new "feature" of the OTA.
[EVO 4G Android Development] Wire P. Snyder:
Outstanding work... Very good.. And glad to hear you stayed away from Clockwork... Its a peice of "&*^%"... :)
[EVO 4G Android Development] koaltech:
This process worked perfectly for me...I have a stock system + root + 4g + the latest updates now...

and can remove Sprint bloatware using titanium backup...
[EVO 4G Android Development] kck33:
Wow this worked great! Thanx! :-)
[EVO 4G Android Development] meatgel:
Thanks for this. It was a big help.
[EVO 4G Android Development] chandlerw88:
I did this and tried to return to stock afterwards now I'm stuck with the new build and the old radio after the pcimg36 failed to update everything BUT the radio, I'm pretty sure I lost root or my recovery is to shat now, and ideas that can help will be greatly appreciated
[EVO 4G Android Development] madj1:
Just want to say thank you. This was just just what I was looking for. Im not really interested in flashing custom roms or really messing with nand much, I just like to be able to have access to programs that require root. I was just using unrevoked until someone came up with a way to use the new update properly. I started by backing everything up with titanium backup and mybackup than using the simple 3 click root method to get the correct hboot and nand unlocked. Then followed the directions in the OP and everything worked great. Thanks again!

Edit: Sorry, to clarify I only used unrevoked v 1. I never ran v 2 or the patched ota update they put out.
[EVO 4G Android Development] Smac61:
Has anyone running Unrevoked 2 (v1 specifically) tried this method yet? Details?

Thanks.

EDIT: question stands regardless of WiMax issue. I am concerned about the method of root Unrevoked used and whether or not Toast 1 or 2 was required.
[EVO 4G Android Development] GumboChief:
This will not fix your wimax.