As far as I've seen, this is something that is unsupported -- I'm wondering if it wouldn't be too hard to enable.
Has anyone seen a custom rom where this works?
Any idea regarding difficulty of implementing it?
duraaraa said:
As far as I've seen, this is something that is unsupported -- I'm wondering if it wouldn't be too hard to enable.
Has anyone seen a custom rom where this works?
Any idea regarding difficulty of implementing it?
Click to expand...
Click to collapse
There is a way to get this to work because I've looked it up before. Would definitely drain your battery more. Just do a Google search you will find what your looking for.
Related
Hi there, I've noticed, and read, that the top mic on our phone is disabled in AOSP roms, and that it's likely not to be enabled. I've scoured the forums but can't find a reason. Is it an open source thing? A lack of source code thing? Does anyone know the reason? I know that my knowing why won't fix it, I'm just super curious. Thanks in advance!
weweboom said:
Hi there, I've noticed, and read, that the top mic on our phone is disabled in AOSP roms, and that it's likely not to be enabled. I've scoured the forums but can't find a reason. Is it an open source thing? A lack of source code thing? Does anyone know the reason? I know that my knowing why won't fix it, I'm just super curious. Thanks in advance!
Click to expand...
Click to collapse
To my understanding it did work at one time. It created an echo when on the phone and/or on speakerphone. Thus, its disabled now. I havent seen anything about that it wont be enabled again once someone finds a fix.
Sent from my SPH-L710 using xda app-developers app
I know its not written in the code for google yet but the Gnex has the hardware built in. Has anyone been able to activate the chip and maybe write their own code to make it work?
newtonfb said:
I know its not written in the code for google yet but the Gnex has the hardware built in. Has anyone been able to activate the chip and maybe write their own code to make it work?
Click to expand...
Click to collapse
I've never seen it. It's not a ROM issue either, it's up to the support from the kernel which carries along the drivers.. which talk to the hardware.
akira02rex said:
I've never seen it. It's not a ROM issue either, it's up to the support from the kernel which carries along the drivers.. which talk to the hardware.
Click to expand...
Click to collapse
So nobody knows how or nobody really cares to take the time to do it? Im just curious. I know theres alot of guys on these forums that know how to do a ton, didnt know if it was possible.
newtonfb said:
So nobody knows how or nobody really cares to take the time to do it? Im just curious. I know theres alot of guys on these forums that know how to do a ton, didnt know if it was possible.
Click to expand...
Click to collapse
So you want someone to try to write a driver to fix something that isn't broken?
063_XOBX said:
So you want someone to try to write a driver to fix something that isn't broken?
Click to expand...
Click to collapse
isnt broken..what the hell you talking about? It has to be enabled thats all. Obviously if i was smart enough to do it then i would. It was a simple question and i was hoping somebody with knowledge unlike yourself would give me an answer
newtonfb said:
So nobody knows how or nobody really cares to take the time to do it? Im just curious. I know theres alot of guys on these forums that know how to do a ton, didnt know if it was possible.
Click to expand...
Click to collapse
You'll have to go to Google with that question. It obviously ain't trivial to be done by a community, because I can imagine it would already be done by now.
Actually the work was started on by someone who was developing for the cukoo watch, but was abondonded when google switched bluetooth stack from bluez.
So if you are using an older rom and your hardware supported it you could in theory use this project
https://github.com/android-btle/
Someone else did not like the switch to the new BT stack so they created a project to put the bluez back into android.. Unfourtunately it appears some packages were removed..
http://gitorious.org/android-bluez
Just some of my research into the matter
Has anyone figured out a way to get the Knock On feature? I've done a good bit of searching on this forum and on Google but didn't find anything solid. What's the consensus here?
mityman50 said:
Has anyone figured out a way to get the Knock On feature? I've done a good bit of searching on this forum and on Google but didn't find anything solid. What's the consensus here?
Click to expand...
Click to collapse
You need a custom kernel.
Sorry I'm still a bit of a novice, but that would require a ROM that works with that kernel too, right?
Has anyone found a fix for the bluetooth not finding low energy (BLE) devices on the CM roms? I have been searching for months but have found nothing. I have read that it was a stack issue so tried replacing some of the configuration of the stack.conf file with stock but did not help.. I don't like the stock rom very much but am forced to use it because of this bluetooth issue.
No one?
This looks like it will never happen, so I'm sticking with stock.
arnold88 said:
This looks like it will never happen, so I'm sticking with stock.
Click to expand...
Click to collapse
Yeah looks like it. Posted this in multiple threads and no responses.
Was hoping CM13 would work with BLE but it doesn't look promising. I obviously need to just get over my irrational dislike of the LG stock UX and learn to live with it. I think I might have to go with a different make of phone next time.
Beware stock 6.0 has the same issue.. Google's bug
I read that mirroring works on some custom roms... Possibly RR? If that is the case, does anyone know what changes were implemented to do this? Obviously it's not just the same couple of lines in the buildprop that it used to be, but would still be worth any extra work in my opinion. Can anyone shed some light? Thanks!