[TESTING] - NAND OMGB (1.2.3) - Page 68

**arrrghhh** · #**671** (**permalink**) 12-11-2011, 08:50 PM

Quote:

Originally Posted by [ACL]

we need a vote on this lol. or just setup a how to butcher your own keys. But this is minimal.

We've been down this road, and there are almost as many people that want the end call key to be end call as there are people who want the home button. At first I didn't really care about the long press recent apps, but now that I've gotten used to it (and the prox sensor works for calls) I don't really care about the end call key anymore

.

So no matter what is chosen people are not going to be happy, so the best option is some easily customizable way. I'm sure an app could easily take care of this, will just need root access to change around the keymaps. Perhaps this could be a one stop shop for keymaps, so those with other keyboards can swap out keyboard map to whatever they want. Eh?

Quote:

Originally Posted by [ACL]

I know its a little early for xmas gifts but here is how i took my anger out on htc.

http://rhodium-nand.googlecode.com/files/tscalib.apk

Sweet dude, gonna check it out now. Good work.

**[ACL]** · #**672** (**permalink**) 12-12-2011, 02:44 AM

Quote:

Originally Posted by vzihome

Guess maybe a script and just place it in the init.d folder pull it off of sdcard? No biggie anyways, any luck with my logs?

Sent from my Touch Pro 2 using Tapatalk

sorry what logs again ?

Starfox · #**673** (**permalink**) 12-12-2011, 07:47 AM

You can use the keychar/layout that works on FRX for use on OMGB. Personally I use call-as-home.

-- Starfox

**arrrghhh** · #**674** (**permalink**) 12-12-2011, 11:02 AM

Quote:

Originally Posted by Starfox

You can use the keychar/layout that works on FRX for use on OMGB. Personally I use call-as-home.

-- Starfox

Of course, but having some user-customizable way that doesn't involve hacking the keymaps would be nice.

Not something that's critical/urgent, but at the same time I don't want it to get lost in the ether

. There's obviously a lot of other things that need a-fixin'.

huckl3b3rry · #**675** (**permalink**) 12-12-2011, 02:18 PM

Forgive me if this is common knowledge, but bluetooth headPHONE (not in-call BT headset) audio works just fine with with 1.2.3 (I haven't upgraded to the Dec 5th yet). In-call bluetooth audio of course doesn't work, but I did notice in my car stereo that recognizes the call and the stereo starts counting the seconds of the call etc, the audio just isn't routed to out BT.

Also, thanks ACL for the calib app. Worked great for me. I had already pulled my calib file FRX, but wanted to give the app a try.

**arrrghhh** · #**676** (**permalink**) 12-12-2011, 03:13 PM

Quote:

Originally Posted by huckl3b3rry

Forgive me if this is common knowledge, but bluetooth headPHONE (not in-call BT headset) audio works just fine with with 1.2.3 (I haven't upgraded to the Dec 5th yet). In-call bluetooth audio of course doesn't work, but I did notice in my car stereo that recognizes the call and the stereo starts counting the seconds of the call etc, the audio just isn't routed to out BT.

This build doesn't include the new acoustic code yet. Once that has settled and is solid, I'm sure it can be implemented and (holds breath) hopefully all of the audio routing problems are solved, magically.

huckl3b3rry · #**677** (**permalink**) 12-12-2011, 03:23 PM

Roger. I just didn't know if you guys know that the Blue tooth audio routing for headphones was working. It kind of surprised me because I knew that the in-call BT headset audio routing was not working.

anish88 · #**678** (**permalink**) 12-12-2011, 03:30 PM

Quote:

Originally Posted by arrrghhh

This build doesn't include the new acoustic code yet. Once that has settled and is solid, I'm sure it can be implemented and (holds breath) hopefully all of the audio routing problems are solved, magically.

Even the 3.5mm will start working too?

**[ACL]** · #**679** (**permalink**) 12-12-2011, 03:44 PM

Quote:

Originally Posted by huckl3b3rry

Roger. I just didn't know if you guys know that the Blue tooth audio routing for headphones was working. It kind of surprised me because I knew that the in-call BT headset audio routing was not working.

There is a ticket opened about this.

Issue 6 - rhodium-nand - bluetooth incoming audio during phone call not working - Touch pro 2 on NAND - Google Project Hosting

Not sure if you are talking about the same thing.

**[ACL]** · #**680** (**permalink**) 12-12-2011, 03:48 PM

Quote:

Originally Posted by anish88

Even the 3.5mm will start working too?

No, 3.5mm is not working because we aren't initializing some hardware. Its a bit confusing because the interrupts for the gsensor are the ones that drive the 3.5mm detection (crazy htc guys).

But its on my list of things to do.