Related
Somewhere in inetrnet some say that there is the hardware for FM radio and requires only an application to make it work? Fact or fantasy?
nemocool said:
Somewhere in inetrnet some say that there is the hardware for FM radio and requires only an application to make it work? Fact or fantasy?
Click to expand...
Click to collapse
The Snapdragon chip has FM in it.
But the Liquid doesn't have FM, dunno if it's disabled or took out (hardware)
So what I read is not a fantasy, I hope someone develops a utility that allows us to use it!
I think its the bluetooth chip that have FM receiver, not the CPU.
Check this out:
http://forum.xda-developers.com/showthread.php?t=608340
If Bluetooth chip is same then Liquid should have radio and since F1 has radio and F1 and Liquid hardware are pretty much the same, I think there is big possibility Liquid to have radio, which is disabled.
Also I have seen in a dump from HTC Espresso a radio application.
Look at this:
http://www.broadcom.com/products/Bluetooth/Bluetooth-RF-Silicon-and-Software-Solutions/BCM4325
I wonder then why FM radio is disabled and the bluetooth is 2.0 instead of 2.1??
nemocool said:
I wonder then why FM radio is disabled and the bluetooth is 2.0 instead of 2.1??
Click to expand...
Click to collapse
bluetooth might be because android just started supporting bt 2.1 in eclair (who knows if updating the radio will make it work in 2.1 instead of 2.0)... fm radio who knows...
[[ Cold ]] said:
bluetooth might be because android just started supporting bt 2.1 in eclair (who knows if updating the radio will make it work in 2.1 instead of 2.0)... fm radio who knows...
Click to expand...
Click to collapse
It occurs to me that we are experiencing growth Andorid day to day, who knows if in a not too distant future we will also see an application that runs the FM receiver
Exactly, giving the limited resources Acer has to making Android phones (probably just ramping up), they decided to skip on developing software drivers for the FM radio since they figured most people will use 3G streaming. but I like FM radio since it uses way less power and for those who don't have a data plan to burn through. Hopefully someone is able to write software drivers for the FM radio.
Some notes on this subject:
1.Acer has little to nothing to do to get the FM working, it's broadcom who makes the bluetooth (and thus FM) driver. What Acer has to do is only a GUI, which isn't hard to do
2.Nexus One has the same chip (ok, not the same, but they share the same driver), and doesn't have FM enabled either, that makes me think their might be some problem somewhere. (but the previous posts stating that using FM on a recent smartphone is unusual seems like a good guess.)
3.I've seen linux FM drivers for BCM4325, in Samsung Galaxy ROM (It's the btld daemon)
The thing is that this driver is fully closed source and doesn't use the bluez stack (linux bluetooth stuff), that's perhaps the reason why Acer and Google decided not to use it.
Anyway these chips are used by N1, Samsung Galaxy (I7500), iPhone 3GS, HTC HD2, HTC Touch Pro2, well, all brand new shiny phones, so it's likely someone of these developers will get something at some point
Does have milestone same chip?
Any news on radio fm recevier on liquid??
luca_v3r said:
Does have milestone same chip?
Click to expand...
Click to collapse
No, milestone have TI wl1271, we have Broadcom bcm4325
an fm radio would rock my world...any news
do you say FM radio!!!!!
If yes, is it possible somehow to enable it....because I realize games,mp3 and chatting doesn't mean entertainment for me on the road.....
I've heard bradcomm released data sheets for their liquid bluetooth chip...
any news on this topic, or fm is just too simple ?
and what about terrestrial digital radio (sorry, french..) ?
can it be supported or received at all by our phones ?
may be it need new hardware ?
well, i'm glad to wake up this thread, as i've got some good news
i'm not able to use it myself, so i'll wait for others or the release of the thing in question.
No more waiting, here it is : fm is coming to our liquids
"://android.modaco.com/content/acer-liquid-liquid-modaco-com/320945/radio-fm-for-acer-liquid-finally/"
I am wondering if there has been any improvements to bluetooth on any of the roms out there. I know there has been some threads regarding the issues with bluetooth since 2.1 and I personally am having issues with my phone staying synced to my car (worked perfect in 1.5). Also does anyone know if froyo get an update to address bluetooth bugs? Thanks.
Bluetooth in 2.1 has been hit or miss depending on the brand you are trying to attach to. I have bluetooth on my computer and can use it fine with my phone. Audio works fine and it stays connected. It could be because I have froyo. IDK.
BTW-This should be in Q&A
BlueTooth does seem to be a little less picky in FroYo.
Hummm maybe its time to try froyo and see if it fixes my issues
Sent from my HERO using XDA App
Hi,
Any zeemote users? There is a zeemote driver on the market which seems to replicate the functionality of GamePro.
Zeemote JS Ctrl Input Method
It works fine with an N1/Zeemote, but not on the SGS.
Are there any known bluetooth issues with the stock ROM that might cause this?
I'm thinking of trying Froyo to see if this fixes it.
Thanks.
they did include mouse and keyboard support in froyo
so chances of getting those bluetooth controller working are greater
in 2.1 mouse and keyboard are not supported
AllGamer said:
they did include mouse and keyboard support in froyo
so chances of getting those bluetooth controller working are greater
in 2.1 mouse and keyboard are not supported
Click to expand...
Click to collapse
Ok, thanks.
Anyway, I updated to Froyo JPK, and the damn app disappeared from the market. I rooted and tried eris market fix, but it just won't show up. I did a wipe after flashing, so it's not a market cache issue I don't think.
Is there any way of grabbing the apk from the N1 I got it working on?
Any chance of one of the Devs having time to look into why the microphone input is not recognised or enabled on bt headsets in CM7?
Great progress has been made getting BT enabled, but I'd love to be able to Skype or record audio via BT...
Ill put a +1 on interest in this; but i know realistically, there are more critical things being fixed right now, so i am ok waiting..
I'm sure down the road, more devices will work, but I'm interested in the range issue. Is it a hardware issue (antenna) or is it a software?
sark666 said:
I'm sure down the road, more devices will work, but I'm interested in the range issue. Is it a hardware issue (antenna) or is it a software?
Click to expand...
Click to collapse
software. the wifi shares the antenna with the BT.
I'm sure it's just a matter of time before the bluetooth is able to handle a microphone. That's what I'm waiting for. I am loving the latest CM7 stable 4-11-11.
That's the only thing my nook is missing.... mic. I've been through all the ROMS and nothing beats the CM7 ...IMO. I will be more than happy to test any kernels for bluetooth stacks that the developers may come up with. I'm not familiar with what all they have to overcome to make it work but I am rooting for them. All the hard work that has already gone into this is AMAZING!!!!!!!
"We need more Cowbell"
Hi Guys
Would really appreciate some help with this one, i am sure it been covered to some degree in other threads.
Since owning my unit I have wanted one application to run and I am not fussed about anything else, the app is ALPconnect.
ALPconnect is a application that connects to my radar detector via BT 4.0 only so it displays all the information on the dash for radar frequencies.
https://play.google.com/store/apps/details?id=com.alpriority.alpconnect&hl=en
Due to the limitations in the Bluetooth, no current rom has been able to allow the application to turn the BT on and search for the ALPconnnect Module
http://www.alpriority.com/product/alpconnect-bluetooth-module-gen2/
Over on the other forum i am apart of http://radarandlaserforum.com, one member has spent upwards of 2000$ buying android head-units to see if this app would run and connect on it.
our small thread is ongoing at @ http://radarandlaserforum.com/showt...-InCar-Enetertainment-unit-ALPconnect-Testing about this issue.
I don't normally ask for help, but I could really use some help and I am sure others on the forum that purchased it for that reason would greatly appreciate it too.
This is the last information I received from agentdr8, thank you aswell
agentdr8 said:
It's severely limited, when compared to any other Android device with BT. This is due to the OEM's choice of the BC5/BC6 module, and their poor BT implementation. Instead of routing BT audio traffic through the Android system, like a normal device would, they route it through the MCU. That would be fine on its own, except they route pretty much all BT interactions through the MCU, via serial AT commands, which is very non-standard. Simple things like pairing, or using SPP profile just don't work, or require a bit of finagling.
On top of that, there's code (at least in MTCB; dunno about newer MTCD) in MTCManager that filters which devices can pair via BT for OBD use. It checks the device name and if it starts with OBD, it will allow it to pass to the next step during pairing. I can only imagine they chose to do that so they could sell their companion BT OBD adapters with the headunits?
My XMTC module had accounted for this limitation in name-based filtering (apparently not the only limitation though; if your adapter was at least v1.4 it should work), but it hasn't been updated to work on any 2016 roms. Since I no longer have time to maintain that project, it's been open sourced on my github. The BT pieces could be extracted into their own module, but I thought I had read someone else (maybe MVG70?) had made a BT xposed module for these devices to try and address compatibility issues.
Click to expand...
Click to collapse
Just as a thought
Would the MTCB be able to support external USB BT 4.0 thus removing the need for the messy internal BT
Sent from my iPhone using Tapatalk
shanetrainST said:
Just as a thought
Would the MTCB be able to support external USB BT 4.0 thus removing the need for the messy internal BT
Click to expand...
Click to collapse
I think it's been discussed before, and no one has successfully added an external BT adapter to these headunits.
Has that group tried the app on the Parrot Asteroid? I know it wasn't the highest rated Android headunit, but it might be more "standard" than how these ones are configured.
agentdr8 said:
I think it's been discussed before, and no one has successfully added an external BT adapter to these headunits.
Has that group tried the app on the Parrot Asteroid? I know it wasn't the highest rated Android headunit, but it might be more "standard" than how these ones are configured.
Click to expand...
Click to collapse
Thanks agentdr8, but it does not really help the ones that splashed out and bought the HuFei units
Is the reasoning behind the external BT not working because nobody is interested in making it work or is it not technically possible?
shanetrainST said:
Thanks agentdr8, but it does not really help the ones that splashed out and bought the HuFei units
Is the reasoning behind the external BT not working because nobody is interested in making it work or is it not technically possible?
Click to expand...
Click to collapse
Since the kernel is not open source, there's very little hope of adding the necessary drivers to support external BT adapters. Aside from that, I don't believe the BT stack that is included in these roms is standard.
I won't say it's impossible, as given enough time and money, anything is possible. But I doubt it's something anyone here can address without the sources.
Guess the manufacturer is reluctant to release the source then.
Sent from my iPhone using Tapatalk
agentdr8 said:
Since the kernel is not open source, there's very little hope of adding the necessary drivers to support external BT adapters. Aside from that, I don't believe the BT stack that is included in these roms is standard.
I won't say it's impossible, as given enough time and money, anything is possible. But I doubt it's something anyone here can address without the sources.
Click to expand...
Click to collapse
Just a couple of questions
1.Do you know if any developer is currently working injecting the drivers into the kernel, as impossible as it sounds.
2.If the manufactures were to fix this issue, what things should they include to make external BT work?
3.Have any of the manufactures hinted at releasing the source and letting other developers fix the issue with custom roms
Just on another note
I have 30 emails from Eonon saying that their tech cannot do this and have assured me that.
We have our own brand and R&D department.
We use our software.
Click to expand...
Click to collapse
Which I don't believe for a second
I'm quite interested in getting this fixed as well - I have both an ODB2 adapter and Navdy that I'm unable to connect due to this limitation. And the fact that there's no available workaround via External BT is infuriating.
shanetrainST said:
Just a couple of questions
2.If the manufactures were to fix this issue, what things should they include to make external BT work?
Click to expand...
Click to collapse
From my understanding, the only way to get this to work is through an external (USB) BT adapter, since the built-in BT stack sends everything through the MCU instead of directly to android. So enabling the proper USB drivers for BT in the Kernel would fix it. I'm not aware of any other USB devices that don't work (maybe gamepads or other HID devices, unconfirmed) so it seems they've cherry picked which USB devices to allow. Considering the otherwise hackable nature of these devices, it'd make sense to me to just enable all available USB devices and let us plug in whatever we want to plug in.
I'm in the same boat. I have an OBD adapter (Hondash) which refuses to pair. I've tried 2 Xposed modules which are supposed to sort this. I'm wondering if my particular issue is down to my 5.1.1 ROM so might try it on my old RK3066 4.4.4 HU which I gave to my Dad.
So I'm monitoring this thread in the hope a fix is found.
I am doubtful, I have contacted Klyde/Eonon/others and nobody is willing to release the kernel source code or address the issue.
So when someone gets a copy from Klyde/some reseller/MTC or whoever and a developer has the motivation to correct it, that can be the only solution.
I have given up hope on this one
Sent from my iPhone using Tapatalk
Does anyone know the location in the Android file system where the Bluetooth pairings are saved?
FINALLY! Someone with a similar issue. I've got a Valentine One, and the BT module for android, (connecting using YaV1) and I've been trying to get my android unit to pair with it as well. In for potential solutions.
This question may be off topic, and I apologize for that, but are you referring to the app not being able to turn on BT and look for the adapter; just getting stuck at "Turning on bluetooth..."?
I have an OBDII scanner which I can pair no problem. When I use a specific app (OBD Card Doctor Pro (or reg)) and attempt to connect it, I get a prompt letting me know that an app wants to turn on BT. I click allow and then it just sits there and never does anything. Is that the problem ALPconnect has?
Torque does not prompt me with this and initiates the BT connection just fine.
The main issue here is that the bluetooth hardware is in effect emulated to the android subsystem for the nice bluetooth dialler front end so android has no real control over the bluetooth hardwrae. These headunits have some real downfalls and this is one of them What we need is to break this open and rewrite it. Without sources we can't do that. We could maybe dissasemble bits and replace them in code but the rom is factory odd and hacked to bits!
monza20vt said:
The main issue here is that the bluetooth hardware is in effect emulated to the android subsystem for the nice bluetooth dialler front end so android has no real control over the bluetooth hardwrae. These headunits have some real downfalls and this is one of them What we need is to break this open and rewrite it. Without sources we can't do that. We could maybe dissasemble bits and replace them in code but the rom is factory odd and hacked to bits!
Click to expand...
Click to collapse
So this emulated effect is what causes my system get stuck "Turnning on bluetooth..." if I understand you correctly? There's no Android control over the BT hardware so the request is just lot in limbo?