Related
I had a couple of questions about using Spirit FM Radio app on CM 7.2. And I would like to know in detail about it.
Firstly, When I ran the Spirit app on CM 7.2 i noticed that it doesn't switch on the Bluetooth. Does that mean that it uses the internal Broad com FM chip instead of Bluetooth to receive FM transmissions just like in the LG stock FM radio app?
Will the Spirit FM app still run properly if I UN-install the CM 7.2 Stock FM app? Or does it need the CM 7.2 Stock FM app to run properly?
In the setting of the app, within audio, I saw various options like cyanogen Mod, LG, lge-msm7x27,etc. Even tough i didn't see any difference in quality while going through different options. Which would be the ideal option for us and What do these options do?
CM9 hasn't got a radio am I right? (Btw I'm new to the forum I couldn't find a topic to write this I'm sorry
What phone are you using?
When Bluetooth is enabled FM is enabled too because they locate at the same chip. It's the easiest way to enable FM and so is CM radio doing. Spirit FM (and stock LG) does it little bit harder by only enabling FM thus saving some starting time and battery (battery part is not a 100% fact though, only my own speculation).
You can remove CM radio, it is not needed.
Recommended method by author in Spirit is CyanogenMod. I don't know exactly what are the differences between different methods but stick with CyanogenMod.
Spirit FM does use Bluetooth, only the icons aren't changed that's all.
Sent from my LG-P500 using xda premium
4silvertooth said:
Spirit FM does use Bluetooth, only the icons aren't changed that's all.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
I might be wrong but if Bluetooth is turned on i see no indication, not only in status bar, settings, no device discovers it (visible), i think i need an app to check the components...
Will check back whit the answer
Edit: It dose use bluetooth
moby_test said:
I might be wrong but if Bluetooth is turned on i see no indication, not only in status bar, settings, no device discovers it (visible), i think i need an app to check the components...
Will check back whit the answer
Edit: It dose use bluetooth
Click to expand...
Click to collapse
How did u finally come to that conclusion that it does use Bluetooth? And if it does... Does that mean that there is no big difference in the way Spirit, Cyanogen mod and LG FM radio app works?
I have my own thread for questions, 1st link in my sig: http://forum.xda-developers.com/showthread.php?p=13379669
And I respond to emails and PMs, but sometimes respond on my thread for all to benefit. Or just let me know a thread's been opened...
See below for answers:
sweettaniyaa said:
Firstly, When I ran the Spirit app on CM 7.2 i noticed that it doesn't switch on the Bluetooth. Does that mean that it uses the internal Broad com FM chip instead of Bluetooth to receive FM transmissions just like in the LG stock FM radio app?
Will the Spirit FM app still run properly if I UN-install the CM 7.2 Stock FM app? Or does it need the CM 7.2 Stock FM app to run properly?
In the setting of the app, within audio, I saw various options like cyanogen Mod, LG, lge-msm7x27,etc. Even tough i didn't see any difference in quality while going through different options. Which would be the ideal option for us and What do these options do?
Click to expand...
Click to collapse
Copied on my thread, because I did a lot of thinking and typing...
Yes you can remove the CM FM app.
On CM7, the default CyanogenMod audio method is generally best. It's the same method the CM7 FM app uses, so it's the most likely to work well, especially when dealing with things like phone calls coming in when FM is on.
If a CM ROM for any phone has a CM FM app, this method should work, but unfortunately that's not yet the case with CM9 ROMs. so low level methods are needed for now on CM9, and there are often issues, and many CM9 ROMs just don't support FM audio routing yet, or I haven't figured them out.
Re: Bluetooth: my app has many ways to access FM chips.
- The first method I supported was via Bluetooth (the HCI API), like the CM FM app. Like it, my app can run commands using the command line hcitool utility, and this is nice because my app can run without root/SU. But it's not too efficient, especially when using RDS where lots of data gets transferred.
- For better efficiency, with root, my app supports direct access to the HCI sockets, through a daemon, because apps don't have the privilege otherwise.
- But because many people were running stock or stock derived ROMs using the Broadcom proprietary BT stack, and I could find no way to send HCI commands with it, I created a "UART mode" that communicates directly with the Bluetooth/FM UART. The wireless part of Bluetooth is not switched on, which saves power. But this mode requires root (unless /dev/ttyHS0 or whatever is accessible from an app), and only works if BT is off.
- A new access method is available now on stock and stock derived ROMs that run the proprietary Broadcom BT stack and that supports the stock LG FM app. This can work on stock, unrooted devices. In this mode the characteristics of the stock FM stack are unavoidable, both positive and negative.
The Broadcom proprietary BT stack has a special mode where Bluetooth is considered off, but FM is on. This enables the Bluetooth HCI "UART" to provide a path to control the FM part of the chip.
- There are different device driver access methods used for dedicated FM chips not contained in a BT/FM combo chip, but those don't apply to the P500.
OK for SGA?
Can I use this FM radio app for my Samsung Galaxy Ace? I have Ice Cream Sunday ROM installed.
donzzy said:
Can I use this FM radio app for my Samsung Galaxy Ace? I have Ice Cream Sunday ROM installed.
Click to expand...
Click to collapse
Off-topic, and you should ask on my thread anyway, or check post 2 of my thread. Please don't respond here.
Canned response now:
The Simpsons taught me that among Hemingway's words of wisdom was:
“The shortest answer is doing the thing.”
IE, why don't you just try it ? It's free and only takes a minute or two I think.
There's even an intro that can be read and will give some useful information on configuration.
Then if you have trouble, you can come back, report it, and hope for an answer.
mikereidis said:
Copied on my thread, because I did a lot of thinking and typing...
Yes you can remove the CM FM app.
On CM7, the default CyanogenMod audio method is generally best. It's the same method the CM7 FM app uses, so it's the most likely to work well, especially when dealing with things like phone calls coming in when FM is on.
If a CM ROM for any phone has a CM FM app, this method should work, but unfortunately that's not yet the case with CM9 ROMs. so low level methods are needed for now on CM9, and there are often issues, and many CM9 ROMs just don't support FM audio routing yet, or I haven't figured them out.
Re: Bluetooth: my app has many ways to access FM chips.
- The first method I supported was via Bluetooth (the HCI API), like the CM FM app. Like it, my app can run commands using the command line hcitool utility, and this is nice because my app can run without root/SU. But it's not too efficient, especially when using RDS where lots of data gets transferred.
- For better efficiency, with root, my app supports direct access to the HCI sockets, through a daemon, because apps don't have the privilege otherwise.
- But because many people were running stock or stock derived ROMs using the Broadcom proprietary BT stack, and I could find no way to send HCI commands with it, I created a "UART mode" that communicates directly with the Bluetooth/FM UART. The wireless part of Bluetooth is not switched on, which saves power. But this mode requires root (unless /dev/ttyHS0 or whatever is accessible from an app), and only works if BT is off.
- A new access method is available now on stock and stock derived ROMs that run the proprietary Broadcom BT stack and that supports the stock LG FM app. This can work on stock, unrooted devices. In this mode the characteristics of the stock FM stack are unavoidable, both positive and negative.
The Broadcom proprietary BT stack has a special mode where Bluetooth is considered off, but FM is on. This enables the Bluetooth HCI "UART" to provide a path to control the FM part of the chip.
- There are different device driver access methods used for dedicated FM chips not contained in a BT/FM combo chip, but those don't apply to the P500.
Click to expand...
Click to collapse
Thank you for clearing it to me. But I don't know... something weird happened to me. I was using Spirit FM radio app whole day yesterday but the Blue-tooth icon never showed up. But today when tried the app again It has been showing the Blue-tooth icon. I don't get it. What changed? I tried re-booting and everything. Still the same.
Does Android 4.1 allow a device to serve as a Hands-Free Profile (HFP) device? Similar to the way many newer cars come with integrated Bluetooth/HFP, I would like to use my tablet (Nexus 7) as a front-end for my phone. When an incoming call comes in, the phone should relay the call over Bluetooth to the tablet; it should also allow the tablet to make outgoing calls via Bluetooth over the phone's network.
Please note that I am not interested in solutions such as GrooveIP, Talkatone, and SIPDroid. I am specifically looking for Bluetooth HFP.
I've done quite a bit of searching but have not seen an app that does this. I wouldn't mind looking into developing such a product - but I first wanted to know if the HSP 1.6 host API was available in Android 4.1. I've seen resources stating it was available in ICS 4.0, but I believe this is to allow Android devices to connect to third-party HSP devices - I'm looking to do the opposite (i.e. have the Android device serve as the HSP host).
i am also curious about this.
fxftwo said:
i am also curious about this.
Click to expand...
Click to collapse
Me too
For those of us that plans to install a Android tablet in the car for music etc. this would be tha last part to make it a complete in-car device.
I am another curious one about this. The only devices I know of for sure that can do this are the 3.6 and 4.2 samsung galaxy players. Unfortunately, I have the 4.0 galaxy player, that doesn't support it. The galaxy players run gb, not jb, btw.
Sent using Tapatalk
Did anybody found a solution, and trying to add this feature to my android app.
anonim1 said:
Does Android 4.1 allow a device to serve as a Hands-Free Profile (HFP) device? Similar to the way many newer cars come with integrated Bluetooth/HFP, I would like to use my tablet (Nexus 7) as a front-end for my phone. When an incoming call comes in, the phone should relay the call over Bluetooth to the tablet; it should also allow the tablet to make outgoing calls via Bluetooth over the phone's network.
Please note that I am not interested in solutions such as GrooveIP, Talkatone, and SIPDroid. I am specifically looking for Bluetooth HFP.
I've done quite a bit of searching but have not seen an app that does this. I wouldn't mind looking into developing such a product - but I first wanted to know if the HSP 1.6 host API was available in Android 4.1. I've seen resources stating it was available in ICS 4.0, but I believe this is to allow Android devices to connect to third-party HSP devices - I'm looking to do the opposite (i.e. have the Android device serve as the HSP host).
Click to expand...
Click to collapse
From what I can gather:
* Bluetooth defines HFP to have two roles: the Audio Gateway (AG) role and the Hands-Free (HF) role.
* Android doesn't natively support the HF role.
I too am interested in exactly what you are describing -- would like to use a tablet as the infotainment hub of a vehicle. I would happy to be a part of or organize a bounty to support development of such a capability in CM10.
-jd
Someone custom-implemented the needed Bluetooth role
Looks like some Android device has custom implementations of both A2DP sink role and hands free unit role. I can't post links yet. Google this:
AllGo Systems Demonstrates Android Based Automotive Infotainment Solutions with Fast Boot-up as a Critical Feature at SAE Convergence 2012 - Detroit, Michigan, USA
n230384 said:
Looks like some Android device has custom implementations of both A2DP sink role and hands free unit role. I can't post links yet. Google this:
AllGo Systems Demonstrates Android Based Automotive Infotainment Solutions with Fast Boot-up as a Critical Feature at SAE Convergence 2012 - Detroit, Michigan, USA
Click to expand...
Click to collapse
any leads if this is available on android yet? (Hands free profile)
There's some development about this but I'm not sure it's possible yet.
have a look at the links here: https://stackoverflow.com/questions...a-receiver-for-a2dp-profile/28892944#28892944
I want, too
to use android device as hands free
Dear all,
I'm working on custom hardware built on Amlogic AML8726-MX SoC. I have the board working with Android 4.2.1 compiled with telephony support. We use standalone GSM module from Telit and I successfully implemented RIL and I'm able to make or receive calls. Unfortunately I'm stucked with routing the audio. The module has digital i2s interface and I connected it through I2S<->USB Audio converter to the SoC.
So now I have two Alsa devices - one is dedicated to analog interfaces (speaker, headphones, microphone) and is working in android applications. The second one represents USB audio and I'm able to use that on kernel level with command line interface. Now I need to to connect these two together to be able to play the voice call using analog interface.
Is there please anyone who can point me into right direction? I'm experienced in kernel development, but going into higher levels is new for me. Can such thing be done just by altering audio_policy.conf and related files or the issue is much more complicated that I expected?
best regards
Jan
Bluetooth v5 introduced a feature named dual audio, through which audio can be played from a single phone to two different speakers/headphones connected over Bluetooth.
Where is this feature in our phone? Even the recent update ColorOS 7.1, this feature is still missing!
please let me know if this feature is available.
Samsung already has the feature
Realme has.......sort of a similar feature
van_helsing_80 said:
Bluetooth v5 introduced a feature named dual audio, through which audio can be played from a single phone to two different speakers/headphones connected over Bluetooth.
Where is this feature in our phone? Even the recent update ColorOS 7.1, this feature is still missing!
please let me know if this feature is available.
Samsung already has the feature
Realme has.......sort of a similar feature
Click to expand...
Click to collapse
Sorry, I don't use BT audio, but is this of any help?
moozer said:
Sorry, I don't use BT audio, but is this of any help?
Click to expand...
Click to collapse
The option you are showing is the feature to connect multiple devices via Bluetooth, which is support to 5 at the same time with possibility of different Bluetooth profiles and I know about this.
Dual Audio feature means to share same Bluetooth profile of "Media Playback" to 2 devices at the same time.
I've tried, but our phone, as of 31st July, still doesn't support sharing Media Playback profile with 2 devices. It will switch the device, if i tend to change it, keeping the profile locked on to just 1 device.
On the other hand, I've tried testing the Samsung's feature and it shares the same profile with 2 different speakers. Bluetooth v5 has the capability to support this by default. Thus, its up to OPPO to provide the software support to it.
van_helsing_80 said:
The option you are showing is the feature to connect multiple devices via Bluetooth, which is support to 5 at the same time with possibility of different Bluetooth profiles and I know about this.
Dual Audio feature means to share same Bluetooth profile of "Media Playback" to 2 devices at the same time.
I've tried, but our phone, as of 31st July, still doesn't support sharing Media Playback profile with 2 devices. It will switch the device, if i tend to change it, keeping the profile locked on to just 1 device.
On the other hand, I've tried testing the Samsung's feature and it shares the same profile with 2 different speakers. Bluetooth v5 has the capability to support this by default. Thus, its up to OPPO to provide the software support to it.
Click to expand...
Click to collapse
Like I said...I don't use it, but thought that might have helped.
Since I upgraded to ColorOs7.0 my Lypertek Tevi Bluetooth headphones now connect each individual earbud with its own Bluetooth connection. The Bluetooth symbol then states 2 devices are connected. The latency in games is massively reduced Vs ColorOS6 where only 1 earbud connected and then the buds talked to each other. Is that the feature you're referring to?
Hello guys, I have done small research.
Our s5e device is based off Snapdragon 670 which is part of multiple interesting devices like Pixel phones. Qualcomm CPUs are including support for other codecs (aside of classic SBC) since few years back, however, to get them working out of the box the device manufacturer have to pay license fees. Since s5e is low cost niche device, Samsung didn't bother to do so, however device is completely capable to support it on hardware level. Essentially, we only need few libraries installed, and if you have necessary root permissions, its possible with classic magisk module.
Such magisk module can be found here:
https://forum.xda-developers.com/apps/magisk/module-aptx-hd-legacy-devices-armv7-t4081693
I have validated it on LineageOS 17.1 via Bluetooth logcat and it does report AptX HD when connected to AptX HD supported headphones
Regular AptX also possible? I have a normal AptX BT Speaker, thanks!
IngoPan said:
Regular AptX also possible? I have a normal AptX BT Speaker, thanks!
Click to expand...
Click to collapse
For sure!
https://www.qualcomm.com/products/snapdragon-670-mobile-platform
Simplest way to confirm on LOS 17.1 is to flash module, open Bluetooth settings of device that you paired to. It should say what codec it will use.