Well from reading other threads I learned that an answering machine software is not possible due to lacking ability to record from the radio audio output (on most phones, possible on univ?).
Well then how about not recording, but automatic pickup and sending prerecorded audio? Would that be possible? Like in: someone calls my phone->software picks up and plays back prerecorded message to caller "I'm in a meeting, please call back at 5pm" ->software hangs up.
Possible or not? Who would be willing to write something like this?
I think there's the same issue - the phone audio path is seperated from the PDA audio path. Read Odeean's posts on TAPI and his frustrations. However, the http://teksoftco.com boys seem to have hinted that this may in fact be possible anyway.
It may be possible I suppose, by writing specific drivers, but I don't think any of us have ever tried I guess.
V
We'll keep you updated with what can be done altough the system is not built to support this kind of features. Firstly because in the US recording audio on phone conversation is ilegal so MSFT doesn't supports this and onestly i don't see HTC being able to offer this kind of support.
Also what Vijay outlined is correct... but we have a few more ideas that we are curently testing...as i said we'll post it if we succeded.
Cheers,
Raul
i believe that it is not a hardware limitation.
The sound from the gsm is not analogue. It passes through the OS somehow, otherwise how is the audio transmitted to the bt hfree?
I don't believe that the transmition of audio (from gsm) to the bt hfree is done only by hardware.
Please comment
andrew_sh is making a good point there. Maybe something can be done by "faking" bluetooth data input?
We have a working answering machine on Himalaya.
See last ROM from TofClock...
Good point made by Andrew. A new bluetooth headset driver or a fake one might do the trick. Cross your fingers guys.
The OS has evolved since Himalaya and HTC has restricted access to drivers by creating a locking mechanism and also the signing process is a hop to pass.
Guys, from my understanding and a poll I've run:
http://forum.xda-developers.com/viewtopic.php?t=40100&highlight=telephone+poll
it doesn't seem like many people have succeeded in recording calls, and those that have are generally using the Himalaya only. The gigabyte can, but it has custom hardware.
We've discussed spoofing the bluetooth audio path before by using a dummy driver and receiver, but mamaich has stated that the audio path for the bluetooth is in hardware only, and seperated from the interceptable paths in the OS.
Rain (for those who don't know, is one of the genii at http://teksoftco.com) - if you have any new ideas, may I ask you to PM me?
Odeean, Mamaich and I have had numerous discussions about this and I'd be interested to know how your research is going. I read that you guys have experience at low level audio driver work (great work on the speakerphone btw!), and I think that might be a good way to go. There is certainly some OS control of the audio path (speakerphone, mute, headset<>bluetooth etc), so I've thought about this way...
V
Hello.
Before you tell me... I already searched the forum and I can see many posts about the problems with BlueTooth in the Hero based ROM's, but none of these posts I read (I could have missed some, of course) say what the problems are exactly, so I don't know if it can be a problem for me or not.
The only things that I need from BT are connection to the Parrot CK3000 handsfree on my car, and to send/receive files over BT. Ocassionally I will use the Magic as a 3G modem, but I can do it through USB if not working through BT.
Are these BT features affected by these BT problems on Hero based ROM's?
Thanks in advance.
Not sure if this applies to all hero roms but in the 'jacxheroskiv' rom the problem is a missing shared object (just a missing file in the filesystem)
http://forum.xda-developers.com/showpost.php?p=4479554&postcount=96
Hi There
At the moment Bluetooth is problematic on all hero roms for the sapphire or otherwise. Audio head sets (wireless headphones) seem to work ok but everything else doesn't. So unfortunately your car kit won't work. (I have the same one, it pairs but the audio is garbled) File sharing on the other hand is a problem for all the androids so far (There is an app on the market that provides the functionality but it's not as elegant as it could be) so don't expect that to work on hero roms. I haven't tried Bluetooth tethering because WiFi tether works so well. Perhaps someone else could comment.
Now for the difficult part...
So far as I can tell a willing developer, correct me if I'm wrong, could make the Bluetooth work if the source code for the hero was made available (should be available in a few months if the recent release of the sapphires source code is anything to go by) There seem to be quite a number of people who need this functionality so I'm sure one of the rom cookers will get to it but unfortunately there is no way to know exactly when. For this reason I've decided to stick to the ion roms for now. In any event, Touchflo/Sense UI will be made officially available for the magics in due course...for a price of course
On another note any support financial or otherwise is greatly appreciated by the developers so if you want to encourage a particular functionality a few bucks and a friendly message will go a long way. Please remember though that the developers do this kind of thing for the love of it and provide no explicit support for their roms. Any and all risk is taken upon yourself but in most cases caveats will have been picked up by someone before hand.
Sorry if I've mentioned some things you already knew but I thought to add some info applicable to other newcomers.
Enjoy hacking!!
Thanks both.
I guess I'll have to use a non-Hero ROM then. As for the BT file transfer, I've seen at least one Cupcake ROM with it enabled and available as an option in the BT menu. I don't know what ROM it was though, I think I saw it in a Youtube video.
P.S.: I noticed that this thread was moved to "Sapphire general", sorry for put it in "development", I did it for it was related to Hero ROM's. Thanks mods for move it.
A2DP works for my Sony Ericsson HBH-DS205 - music streams flawlessly.
However, the call feature does not work - is this another common bluetooth problem with the HEROs?
Hey guys,
I was just thinking about that nasty little problem with cyanogenmod and our legends and since there was no meaningfull advencment, we could put some money on it. I think from 5 to 10€ for each doner would be enough or what do you think? Of course the developer has to give us an account to send the money to.
I would just like to use the FM radio and since it is working on desire for some time now, why not on legend.
So who is ready to do it?
would support that idea.
It is already stated waaaaaaaaaaayyyy before. The FM radio WILL NOT WORK on the Legend because of it's alien architecture. Don't ask me, I don't know ****. But if you're do want to make a donation then you can donate to Ali Ba which has been the sole reason CM is running on the Legend.
This is a good idea.
Sent from my Legend using XDA App
rajasyaitan said:
It is already stated waaaaaaaaaaayyyy before. The FM radio WILL NOT WORK on the Legend because of it's alien architecture. Don't ask me, I don't know ****. But if you're do want to make a donation then you can donate to Ali Ba which has been the sole reason CM is running on the Legend.
Click to expand...
Click to collapse
here on this link http://forum.cyanogenmod.com/topic/8260-fm-radio-support-for-legend/ ale baba himself says it is possible but that he hasn't got the time for it. So it is possible we just need someone who will do it. But first of all we need more people.
I'd consider doing development on this. I was wondering why there was no FM Radio app on CM7, LOL.
At the very least I can commit to finding all the info I can gather on this issue. I have no (satisfactory) employment at present and want to break into the Android specific field.
I have 14 years experience in embedded Linux development, including lots of low level kernel stuff. In a previous life (more decades ago than I dare admit) I did electronics engineering stuff, and I still love the low level nuts and bolts.
I'm pretty new to Android however, got my first cellphone (ever!) 17 days ago, first Android phone 15 days ago, and my Legend yesterday.
I think I can learn quick, I'm CM7 nightly, S-Off, new radio one day after getting it, LOL.
So my point is I, and this project, could use help in areas of Android specific knowledge.
Does anyone know if the normal FM radio app I've used before is proprietary Google code ?
Are there any generic FM radio apps that would work if standard drivers existed ?
My quick research on this is that only a driver might be needed. A V4L (video 4 linux) driver, which I have already had some experience with.
But there DOES seem to be a V4L driver already for Linux for the TI WL1273 chip apparently used in the Legend, and apparently a number of other phones. So in theory, this job might be as easy as integrating an already written driver in to the CM kernel, as a kernel module or 2. There MIGHT be some copyright issues with any chip firmware though.
Alas, some comments indicate using such a driver might interfere with Bluetooth functionality.
Interesting stuff about the 1273 chip is that it may support an FM transmitter, and it supposedly supports WiFi N. But who knows if needed hardware support might not be on the PCBs.
^ wow! where have you been all our android lives, bro? link on the post above yours answers some, if not of all, of your questions & covers a lot, i guess. cheers!
maxq1 said:
^ wow! where have you been all our android lives, bro? link on the post above yours answers some, if not of all, of your questions & covers a lot, i guess. cheers!
Click to expand...
Click to collapse
Cheers...
I've been reading that there IS an FM Radio app integrated into CM now. It comes from MIUI, a chinese group of some sort that also makes an Android ROM.
The app apparently uses /dev/radio* which is the standard V4L radio interface. I have these also on my Hauuppage PVR boards I used for HTPC before I went completely digital for movies, tv, etc.
So yes, what we need is integration of a driver into CM kernel, but coding may be needed to fix bluetooth driver interference etc. And of course who knows what else might be needed.
I'm reading that FM is much more important to those without data to stream. Not all of us live in wireless data dense cities and countries.
Would be interesting to see what frequency range can be received and maybe transmitted.
Would be MOST cool to stream from video camera to transmitter for local "pirate TV" type functionality, LOL. Actually can't imagine ATSC or even NTSC (or PAL etc.) encoding possible, but wireless streaming will do the job...
@mikereidis
Thanks for joining in, great highly appreciated. If there is any time left it would be nice if you could look into the GPS problem with CM 7 it is currently not addressed.
Anyhow thanks for your participation and contribution.
BR, ojessie
@mikereidis
So are you going to try and port it?? If you will and you'll succeded then you will be the legend in Legend community!
Sent from my Legend using XDA App
ojessie said:
@mikereidis
Thanks for joining in, great highly appreciated. If there is any time left it would be nice if you could look into the GPS problem with CM 7 it is currently not addressed.
Anyhow thanks for your participation and contribution.
BR, ojessie
Click to expand...
Click to collapse
I can keep my eyes and ears open to GPS, but best to concentrate on one issue at a time.
What is the GPS issue ? I thought it didn't work on my phone after new ROM but within a few hours it was working OK for whatever reason. And now I see 2 metre accuracy compared to the minimum of 5 on my Optimus Chic.
qzem said:
@mikereidis
So are you going to try and port it??
Click to expand...
Click to collapse
I'll do whatever it takes.
The userspace FM Radio app shouldn't need any porting work AFAIK. It seems to already be in CM 6.1 ROMs for the Nexus One (any others?). So I'd guess installation would just need to be enabled for other phones.
The tricky part is getting a device driver working that creates a /dev/radio interface for the MUIU FM radio app to use. There IS already a Linux driver for the WL 1273 the Legend uses, but it might need some modifications to run on the Legend.
But there is some complicating factor regarding bluetooth drivers, so it may not be too straight forward. For initial testing at least the bluetooth drivers could be disabled.
What about HTC's kernel source. As I told in cyanogenmod forum the drivers should already be in HTC's kernel source. If the code is there it should be easy to put it into CM7 kernel and use HTC's FM Radio app. Or what do you think?
mikereidis said:
I can keep my eyes and ears open to GPS, but best to concentrate on one issue at a time.
What is the GPS issue ? I thought it didn't work on my phone after new ROM but within a few hours it was working OK for whatever reason. And now I see 2 metre accuracy compared to the minimum of 5 on my Optimus Chic.
Click to expand...
Click to collapse
Yeh, thats the problem. GPS is working on some devices and on others not and nobody knows why. As a matter of fact when I'm running CM 6.1 its working great. Flashing CM 7 no change to get it working. As mentioned others are reporting the same issue with CM 7 on some its working on others not.
ojessie said:
Yeh, thats the problem. GPS is working on some devices and on others not and nobody knows why. As a matter of fact when I'm running CM 6.1 its working great. Flashing CM 7 no change to get it working. As mentioned others are reporting the same issue with CM 7 on some its working on others not.
Click to expand...
Click to collapse
When I get tired of Google maps seeming to take forever to figure out my GPS location, I've downloaded and run the "GPS Test" and "GPS Status" apps. I did so and for some time the status color on one of those showed yellow, meaning no GPS fix, but power on.
Anyway sometime later it was working. One of those apps downloaded data to make cold starts work faster and that may have helped. A few things to try for anyone interested anyway.
ponchofiesta said:
What about HTC's kernel source. As I told in cyanogenmod forum the drivers should already be in HTC's kernel source. If the code is there it should be easy to put it into CM7 kernel and use HTC's FM Radio app. Or what do you think?
Click to expand...
Click to collapse
The problem with running the HTC FM radio app on CM is that it, like many other HTC apps, uses the HTC framework with Sense UI. So CM can't run it, although stock or modded Sense ROMs should be able to.
IMO right now the MIUI app is the way to go, and it's open source so anyone can modify/fork it.
Yeah I think a /dev/radio is likely in HTC source, but it's possible it's something different and/or kind of proprietary.
The Chip manufacturer, TI, and their partners who make RF modules based on the chips, DO have android /dev/radio drivers. So they are definitely out there somewhere.
I think, as usual that "In Theory" this should be a simple matter, in reality there is usually some problems to solve. Otherwise we'd have FM already in CM.
A few pointers:
TI 1273 has a few interfaces for communication. One of them being a (standard) serial via bluetooth, the other one I2C.
HTC did not use I2C because they already had to use the serial interface for bluetooth and it's a lot cheaper that way (that's what all manufacturers do, by the way). The wl1273 driver in the Linux kernel does have support for the FM capabilities, but unfortunately via I2C only.
So basically we already have all the drivers we need in place (tiwlan_drv, sdio), no kernel stuff needed. What's missing is valid documentation about how to enable radio, route it to the headphones, seek/tune, etc.
You could reverse engineer /system/bin/btipsd, which does bluetooth and FM communication in original HTC releases.
Once you are able to control FM stuff (with bluetooth turned on) write a nice summary and I'll ask cyanogen how to implement it. Won't be that hard, given the fact that currently all supported devices use the serial interface via bluetooth.
ali ba said:
The wl1273 driver in the Linux kernel does have support for the FM capabilities, but unfortunately via I2C only.
So basically we already have all the drivers we need in place (tiwlan_drv, sdio), no kernel stuff needed. What's missing is valid documentation about how to enable radio, route it to the headphones, seek/tune, etc.
You could reverse engineer /system/bin/btipsd, which does bluetooth and FM communication in original HTC releases.
Click to expand...
Click to collapse
Thanks ali ba ! Yes I know about cheap manus, I've worked for a few, LOL. Linux VOIP and security appliances mostly though.
By "The wl1273 driver in the Linux kernel" do you mean the TI provided W1273 driver in the CM7 ROM ? I had thought that driver was for WiFi only, or perhaps WiFi + Bluethooth. Or does my seeing an rfkill device mean FM radio is in there too ? Would it create a /dev/radio device ? There are some FM init BTS files that may enable FM.
My understanding is that the WL1273 WiFi driver in the mainline Linux kernel (not the Android kernel) is WiFi only. There's a guy from Nokia trying to get WL1273 FM radio only driver into main Linux kernel but not there yet. That driver will be separate from WiFi driver even though they may both have WL1273 in the name.
I've been finding some HCI commands usable with hcitool to do audio routing stuff at least. RevEng has been a specialty of mine, so I think if it can be done, I have a good chance.
Quickest route to a working FM radio on Legend is to find an existing app for another phone that works.
Phones with the WL1271/1273/1281/1283 chips include original Moto Droid, Droid 2, Droid X, Motorai, Nokia N800 (or N900?), N8 (?), B&N Nook Color.
There's a thread here on XDA about Droid 2 phones using the Droid X FM radio app with success. I tried that app but there seems to be some problem launching the fmradioserver.
I saw a logcat message that may indicate I need to "adb install" the APKs instead of just copying them to /system/app. I tried but got the error that indicates the UID does not match the signature. I guess that's not an issue on Droid 2 (or motorola phones in general?)
Does anyone know if/how to mod/repack an APK to avoid the UID signature issue ?
A few more of my findings for anyone interested. BTW should I or someone create a thread in the dev section at this point ?
As mentioned above a guy from Nokia is trying to get a V4L2/dev/radio driver for WL1273 into mainline Linux kernel. That driver could be integrated into our kernel, but it might take a bit of work. And as mentioned that driver is not in kernel yet and may have lots of changes still coming in the next several months at least.
But TI also has a driver, and it's meant for Android. I haven't been able to grab source code for that driver yet. I think TI driver references WL1283, the biggest baddest version with GPS too. But driver is supposed to work on all 4 variants, down to WL1271.
TI has a command line app for testing fm radio, I think called fmapp if memory serves. It's possible this test app could at least help with exploration.
Unlike the poor original Droid owners, we are lucky that we know our FM receive antenna is connected, since stock Legend has FM radio. But there seems to be a different pin for FM transmit so it's possible we will never be able to transmit FM more than a few inches. But Tx would just be a bonus, but a potentially wonderful bonus.
And, ya know, I'm not even sure if MIUI FM app works with /dev/radio. I was looking at some source and it seems to be hardcoded with Broadcom chip specific stuff.
Oh, and my understanding is that even if we ever managed to get Wireless N working (with a new or improved stack perhaps?), that it will likely kill batteries quickly enough to be effectively unusable. Would be interesting though.
I am getting an audio crackle in my 2005 mini cooper s with a kenwood radio over bluetooth on stock 12b. When on a CM based rom this doesn't happen (lg roms have a built-in equalizer?). If someone knows how to remove the stock eq please post how. Thanks
"I have a similar issue in my 2011 Hyundai Genesis Coupe. The static is only present during loud levels on songs, not at all times during the track. Seems like it is most noticeable on the higher frequencies also. Please reply here if your issue is the same.
I did not have this problem on my HTC One X in the same car.
I have searched all over Android and Hyundai forums and found little to work with. What I have found is that this is not affecting everyone, otherwise it would be all over the forums. I appears to me that it is related to our cars bluetooth receivers and how they communicate with the phone.
I found some posts from a user CBaronne where he had what appeared to be the same issue on another phone and modified the "Bitpool" value with good results. He wanted to do the same on this phone but the variable is buried in a system file and modifying it was beyond his expertise.
I have also flashed several sound mods with no success, as well as different tricks to ensure that APT X is enabled. Nothing has helped.
I think until we get a developer with this phone and has this issue there will not be any attempt made to resolve. You can always just buy another car..."
I have been posting this comment in several threads to try an get some attention on it. This issue is not common enough for it to have consistent comments or investigation. I also can confirm that it does not happen on CyanogenMod, so that's what I use now.
Are you on LG's stock Kit Kat?
Other threads:
http://forum.xda-developers.com/show...0#post47418870
http://forum.xda-developers.com/show...9#post47423589
http://forum.xda-developers.com/show...5#post49735305
Reading other Android forums and Hyundai threads it DOES appear to be a compatibility issue, meaning that it is about the combination of two devices, it does not affect every G2 bluetooth connection. From the first link I posted it DOES appear that if we can adjust the bitpool values of the G2 we could improve the quality.
Slinkynose said:
"I have a similar issue in my 2011 Hyundai Genesis Coupe. The static is only present during loud levels on songs, not at all times during the track. Seems like it is most noticeable on the higher frequencies also. Please reply here if your issue is the same.
I did not have this problem on my HTC One X in the same car.
I have searched all over Android and Hyundai forums and found little to work with. What I have found is that this is not affecting everyone, otherwise it would be all over the forums. I appears to me that it is related to our cars bluetooth receivers and how they communicate with the phone.
I found some posts from a user CBaronne where he had what appeared to be the same issue on another phone and modified the "Bitpool" value with good results. He wanted to do the same on this phone but the variable is buried in a system file and modifying it was beyond his expertise.
I have also flashed several sound mods with no success, as well as different tricks to ensure that APT X is enabled. Nothing has helped.
I think until we get a developer with this phone and has this issue there will not be any attempt made to resolve. You can always just buy another car..."
I have been posting this comment in several threads to try an get some attention on it. This issue is not common enough for it to have consistent comments or investigation. I also can confirm that it does not happen on CyanogenMod, so that's what I use now.
Are you on LG's stock Kit Kat?
Other threads:
http://forum.xda-developers.com/show...0#post47418870
http://forum.xda-developers.com/show...9#post47423589
http://forum.xda-developers.com/show...5#post49735305
Reading other Android forums and Hyundai threads it DOES appear to be a compatibility issue, meaning that it is about the combination of two devices, it does not affect every G2 bluetooth connection. From the first link I posted it DOES appear that if we can adjust the bitpool values of the G2 we could improve the quality.
Click to expand...
Click to collapse
sorry for late reply, I was on 4.2.2 stock. right now I am on cloudyflex 4.2.2 and I have yet to see if it makes a difference.
I had the issue on every 4.2.x ROM I tried. When I moved to Cyanogen 11 the crackle went away. I don't want to switch away until I know that this issue is not present on the 4.4 Stock ROM.
My recommendation is that you try a 4.4 Stock ROM if this is important, if that doesn't resolve, go with Cyanogen.
welcome to the world of botched standards, its often appliences with same technology dont always work, just check compatability of devices such as car radios with mobile phones. contact them and ask if they have or can update compatability with newer tech.
its possible kenwood already has an update
send from the jungle
It's possible to connect by bluetooth, but music and sound wont play.
Of course it is. I've paired before on a device but didn't have sound. Did you read up on this for your device and search before making a thread? There are things that don't work on certain devices. Many things get fixed if reported properly. This would probably be more of a device specific Q&A type question over on your device forum I would think.. Not sure what your device model is but most of the questions we all have are already answered multiple times somewhere here on xda and if we search for it enough and use different wording, enough times we will find the answers we are looking for. This search search search I'm referring to isn't my rules it is XDA rules. And it's partly so that there isnt many different threads scattered all over about the same thing. That can make things confusing.. If you search thoroughly and can locate nothing on the issue then that's when we can make a thread about it in the proper section.
If I were you and wanted to know this about my device I would search: (my device model) Bluetooth audio not working but paired no sound, paired Bluetooth speaker to Android device using ____ GSI but no sound , maybe throw XDA in at end. PHH treble GSI (my device model) documentation , Bluetooth no audio GSI XDA.
The "PHH treble GSI documentation (my device model ) " is one I frequently used when it's GSI related because that will take me to any documentation for my device model, notes, what works, work arounds for GSI...etc etc...
That's some ways I would try and go after that. I'm probably not the greatest searcher on the map and I don't have your device model but I bet there's TONS of information out there on this exact issue. Maybe for different devices than yours or maybe information on same issue but not on a GSI .. But you can try and troubleshoot it that way too. What I'd do is search like hell and bookmark all the decent pages you bring up on your issue and really go through good and see what you can figure out. Hope that helps.
Not working on note 10
It's a phh issue
Unless he fixes
No one else will