Ok.... Firstly if i have this wrong I apologise in advance... I have read the Q&A's going back a good time and searched the forums for HTC touch2 threads but cant find this subject anywhere... I hope i havent just missed or misunderstood the jargon !!
I have just been issued a HTC touch2 phone and i am having compatability problems setting it up to use via bluetooth with my VW UHV PREM in car system. I have read tons of forum pieces on similar problems with HTC Phones but dont fully understand the solution and the touch2 isn't specifically mentioned... VW say the phone should be rSAP complatible... what is rSAP and how do i make this thing work... I have enabled SAP and the car has found and paired the phone but refuses to connect at all ... HEEELLLPPPP ...
you need a combination of ROM and kernel that support that. gingerbread had some roms and kernels which were able to connect via rsap to you vw uhv.
but to be honest, i dont know much about htc roms or kernels, which means you need to try for yourself.
this app is afaik the only solution for recent ICS versions and runs as form of an addon to your rom / kernel. just search for bluetooth sim access profile in the market
note, that this app will not guarantee you a succesful rsap connection, but with my sgs2 it is recently the only solution to get it working somehow.+
for an explanation about rsap i suggest google
in short terms it provides the sim to another device (like your radio), which includes the possibility to call, read sms, use contacts directly through your car.
which leaves your phone in kind of airplane mode.
combinations of android build + kernel for bluetooth SIM access profile
Hello
Can anyone provide a list of suitable combinations of android build + kernel for bluetooth SIM access profile (e. g. rSAP)?
I have Slim ROM with android 4.3.1, there it does not work.
Thanks.
I can not figured out the reason
why we still not have working FM Radio under Android/Froyo on Polaris?
Nexus One, Motorola Droid2, Dell Streak seems to have it already working:
http://forum.xda-developers.com/showthread.php?t=723373
http://forum.xda-developers.com/showthread.php?t=769894
http://forum.xda-developers.com/showthread.php?t=795299
Why not we?
Do we have other chip responsible for FM radio?
Which? (can not find model/name too)
Could somebody from gurus explain what we need for it?
Missed files? Patched kernel?
(and please don't offer to use any internet radio instead: I know I may do it)
I think its BRF6350 is the chip we are using for bluetooth and the fm radio (same chip) ,cant think what firmware we use brf6350.bin or brf6300.bin.
Also we'd have to sort the antenna out as the bluetooth uses internal and radio use's external (headphone's).
http://focus.ti.com/general/docs/wtbu/wtbuproductcontent.tsp?contentId=14646&navigationId=12659&templateId=6123
As I am a new user I can't post on specific thread so I post here my test
I installed Spirit PAK ver 01 07 and after turn on all device in my Nexus S I tried apk
Here some photos of test with stock ROM 2.3.4
It can be useful for developmetn ....
http :// imageshack.us/photo/my-images/27/dscf0009hc.jpg/
http :// imageshack.us/photo/my-images/18/dscf0011js.jpg/
http :// imageshack.us/photo/my-images/825/dscf0012su.jpg/
result : Signal are instable and no sound (
If can I help in some other way ....
The technical is in the next post.
Thanks for posting publicly. I prefer open discussion so that everyone can benefit and contribute.
I created my main thread in a forum dedicated to discussing apps, but didn't realise it was under a dev forum and thus users with less than 10 posts couldn't post. I wonder if I should create a 2nd thread...
You can't post full URLs either so here they are:
http://imageshack.us/photo/my-images/27/dscf0009hc.jpg/
http://imageshack.us/photo/my-images/18/dscf0011js.jpg/
http://imageshack.us/photo/my-images/825/dscf0012su.jpg/
BTW, screenshots are great !
The short answer is I don't think the Nexus S is capable of receiving or transmitting FM, but I would never say never without hard proof.
I've been asked a few times over the last several months, and if I recall correctly, every time I've Googled the issue I found no evidence that anyone has EVER made FM work on the Nexus S.
I think my app is probably the closest it will get. It WILL manipulate the FM registers over HCI and it will look like it works, to some extent. But no audio, not even static, will be heard.
And there will be no indications of reception, like a more or less steady RSSI reading on strong channels, and RDS data.
Samsung manufactured this phone, and it seems to be a derivative of the Galaxy S. The Galaxy S, like the Nexus S, has an FM/BT/WiFi combo chip from Broadcom. The stock Galaxy S supports FM, but via a dedicated Silicon Labs FM chip, which the Nexus S does not seem to have. (BTW, the FmTwoO app also works on Galaxy S.)
AFAICT it's not possible to use the Broadcom chip for FM on the Nexus S. The antenna and audio connections are to the Silicon Labs chip and not to the matching pins on the Broadcom chip. If the Nexus S PCB/circuitry is reasonably similar to the Galaxy S, then it probably won't work on the Nexus S either.
There are two Samsung devices that I've been trying to help owners get FM working on. that have a Broadcom chip, but no other chip. Thus far we've had no success with either the Galaxy Tab, or the Spica i5700. There are two problems:
(1) The RSSI signal strength shows strange values and may jump around. I think this is due to no antenna connection and/or some FM RF power pins may not be connected.
(2) No analog audio output has been achieved, not even static, despite trying the 8 or so Audio Methods my app currently supports, and ALSA as well.
(2) might be fixable if I ever achieve digital audio transfer or even direct audio to BT headsets within the chip.
But (1) might only be fixable with much investigation and soldering etc.
Sorry... I'd love to find out I'm wrong about this.
Other info for BCM4329 chip :
http :// www . datasheetdir.com/BCM4329+download
in these datasheet we can read
Code:
Host Interface support
- Host Controller Interface (HCI): High-speed UART
-Audio: PCM
- FM Control: HCI and BSC (I2C-compliant) ports
- FM Audio: Stereo analog input and output, bidirectional
I2S, and PCM ports
In schematic we can notice BT and wifi use same ant , FM has dedicated one ....
But SPI / I2C / I2s are the same of BT and WIFI so it's possible to comunicate with FM part in chip with no problem ....
Code:
FMHost Interface: High-speed UART, I2C for control
.....
if not mistaken spirit apk use only HCI .... not I2C !
magicko said:
Code:
FMHost Interface: High-speed UART, I2C for control
.....
if not mistaken spirit apk use only HCI .... not I2C !
Click to expand...
Click to collapse
All devices that uses the combo chip for Bluetooth support the HCI UART interface. That can be accessed via the BT stack or directly by reasonably standard and common methods.
I don't know what fraction of devices can use the other interface, but some don't. I believe the Galaxy Tab schematic showed a digital connection to the Wolfson audio chip...
The next issue would be accessing the interface, and I think that would require a device driver. If I wanted to support multiple devices and kernels by this method I'd have to create multiple device drivers.
So even if possible, I think the work required would be excessive.
But if somebody can figure this out, I'd be happy to hear about it.
EDIT: A digital audio connection MAY not be as hard as I envision, at least for some devices.
IF the ROM supports a digital / "SCO" connection to the chip, it might be possible to call an audio API to set this up.
I haven't worked with these SCO connections yet, so I don't know how easy or feasible it is, but I'll try to find out.
Hi mikereidis, I don't want flooding to be able write on developers section, as well be superfluous create a new topic on the DroidX tree so I would write here...
I tried the latest SpiritFM version on DroidX CM7. Several times I was able tune to the pre-programmed frequency and receive audio using FM_launch method. In most cases, I only get noise. To get the sound the speaker/headphones button should on and then off. Without such manipulation sound does not appear.
The big problem is that your program give low radio sensitivity. This is not a hardware problem because stock FM program allows 15 radiostations on the my area.
I also tried FM_launch2 but without success.
Here is the catlog with FM_launch, and then FM_launch2. I'm also ready to provide any logs or make any test if it helps you improve SpiritFM for Motorola phones.
evgenln said:
Hi mikereidis, I don't want flooding to be able write on developers section, as well be superfluous create a new topic on the DroidX tree so I would write here...
I tried the latest SpiritFM version on DroidX CM7. Several times I was able tune to the pre-programmed frequency and receive audio using FM_launch method. In most cases, I only get noise. To get the sound the speaker/headphones button should on and then off. Without such manipulation sound does not appear.
The big problem is that your program give low radio sensitivity. This is not a hardware problem because stock FM program allows 15 radiostations on the my area.
I also tried FM_launch2 but without success.
Here is the catlog with FM_launch, and then FM_launch2. I'm also ready to provide any logs or make any test if it helps you improve SpiritFM for Motorola phones.
Click to expand...
Click to collapse
Thanks for the log evgenln. I'll let you know what I find.
Some other people have enabled audio by toggling speaker/headset. It would be a hack, but perhaps I can create an option that toggles it automatically. But it would be better if I figure out what's happening, and fix it right.
Regarding signal strength: My guess would be that there is a function call required to enable the FM antenna, and that you are receiving without an antenna. I'll try to find out.
But since the headphone cable is the antenna, it's possible this is related to audio issues.
evgenln said:
I tried the latest SpiritFM version on DroidX CM7. Several times I was able tune to the pre-programmed frequency and receive audio using FM_launch method. In most cases, I only get noise.
Click to expand...
Click to collapse
It appears something has broken horribly for Texas Instruments FM chips. I can confirm the same errors you are having on my HTC Legend.
I can trigger the errors when I switch headset to speaker, and I'm not sure why yet.
Most phones have Broadcom chips, but I still don't understand why I haven't seen this problem before; it seems to go back at least a month.
Regardless, I've found a workaround that I hope will also work for you. If you deny SuperUser privileges to the app it will use hcitool instead of the daemon. It will consume more CPU/power when RDS is working and the screen is on though.
So, open the SuperUser app and select Spirit FM Radio and press Forget.
Then restart the app and when SuperUser asks for permission, select Deny and Remember.
Let me know, thanks !
I will determine the root cause and a fix.
Here's a preferable workaround for TI chip devices (and reason I wasn't seeing this issue).
This operation is useful for Broadcom based devices on CyanogenMod also because CM tries to use hcitool to set FM volume, so this can avoid some interference:
Remove or rename the hcitool binary. During audio switching, CyanogenMod (and likely some derivative ROMs) calls hcitool for some reason. This causes problems in the daemon mode.
The downside to this is that the CM FM app won't work.
I do this:
adb remount
adb shell mv /system/xbin/hcitool /system/xbin/hcitoo
My app can still use "hcitoo" if needed.
mikereidis said:
I do this:
adb remount
adb shell mv /system/xbin/hcitool /system/xbin/hcitoo
Click to expand...
Click to collapse
I tried this but without success. Still have on and then off the speaker/headphones button to get the sound.
In the attached files logs for the stock FM applications running on stock moto 2.2 and for the current SpiritFM on CM7.
evgenln said:
I tried this but without success. Still have on and then off the speaker/headphones button to get the sound.
In the attached files logs for the stock FM applications running on stock moto 2.2 and for the current SpiritFM on CM7.
Click to expand...
Click to collapse
OK thanks, I'm looking now.
To respond to your PM about Regional Band Russia frequency steps, it works OK for me as 100 KHz.
It's harder to see now though because the frequency up and down buttons have been removed in favor of the graphic thumbwheel. If you carefully nudge the thumbwheel you can see frequency move 0.1 MHz at a time, while for North America it's 0.2 MHz and odd frequencies.
The frequency step for seek might have a problem; it's done by the chip and there may be a problem there.
evgenln said:
I tried this but without success. Still have on and then off the speaker/headphones button to get the sound.
In the attached files logs for the stock FM applications running on stock moto 2.2 and for the current SpiritFM on CM7.
Click to expand...
Click to collapse
I've started a new thread here that should work for people with less than 10 posts: http://forum.xda-developers.com/showthread.php?p=15607830
Technically it's in a paid app forum and it's technically for the paid Unlocker (converts free app to paid app), but unless some moderator decides it's a really bad idea it's open for discussion of the free app also.
Has anyone else noticed that updating to 2.3.5 and sense 3 has changed the bluetooth version.
Before the update, m bluetooth version was 2.1, now after the update if i look in the same place (settings, ,about phone, hardware information), it says bluetooth version is 3.0. How is this possible? is this just a mistake or can the software actually upgrade the version of bluetooth that the phone uses, i would have assumed that this was limited by the hardware itself.
BT 3.0
Actually it is possible because the software controls the chip. I did the upgrade to 2.3.5/sense 3 and indeed the BT upgrades from 2.1 to 3.0.
Have you tried any transfers?...cause' you'll probably feel the differences. Although the bt 3.0 is a bit of exaggeration as long as the bt chip was designed to support 2.1. That makes me think that the improvements are made exclusively via software. So if you'll transfer a file from your phone to another device lower than 3.0 the transfer will like in 2.1. You can compare the power of the new improvement only when you send/receive files with a compatible 3.0 BT.
Hope you'll understand my english and my explanation was useful to you.
cheers
Hey guys,
It appears that several devices are experiencing a Bluetooth music pitch and static issue. I've been researching this issue and it appears to actually have nothing to do with WiFi or Bluetooth modes, but, a Bluetooth chipset incompatibility across the board including on Android, Windows, and Apple IOS devices. It can be corrected through both ROM and firmware updates in the future. With the devices, the issue might actually be partially with the OS Kernel on several portable (phone/tablet/etc.) devices since 2012. It affects Bluetooth devices that use a very common Broadcom/VIDCOMM chipset that has not changed much since 2008. This chipset can be found in several to multiple computers and audio systems, including most car audio systems, and, especially those running Windows portable. For Android developers, watch those kernels and keep Bluetooth in mind. Also, everyone with this issue should check with their Bluetooth receiving audio system/device manufacturer as well for firmware updates to those devices.
Thought I'd share this info with a few that are still having the issue. I have an LG Optimus L90 D415 that is experiencing this issue with the stock ROM (rooted), however, I experience it a little less with a custom ROM. The only reason I'm stuck on the stock ROM is due to the ability to move apps to SD. The best custom ROM for this phone so far does not have that option to move the apps. My vehicle uses a factory integration iSimple Connect that apparently uses one of the affected chipsets and am waiting for a good solution from them also.
I have a Samsung Galaxy Exhibit and an older LG Optimus One T509 (both rooted and custom ROMS) that at which neither appear to have the issue at all as well, so, it appears to only affect certain phone Bluetooth chipsets.
Anyway, I hope this helps some people experiencing the issue. If anyone knows of a good solution or app to help with this, please chime in. I've tried several apps with no luck just to let you know.
Thank you,
Starflare5.