Hi. I have a treo 700w and have been trying to work the a2dp hack that has been posted in other sections of this forum. It works partly but has severe performance issues. Now on another forum some people have theorized that this is since the files for the fix are for an OMAP processor that our freezing is based on the dll's being for the wrong processor. I am aware that there are xscale devices working fine, however I must, at this point check all logical avenues. My issue is that I can't seem to get ahold of the bta2dp.dll, avrcp_mplugin.dll and sbc.dll from an xscale based device that has supported a2dp support. can someone who has a2dp working without hacks get ahold of the files and send them to me.
also any ideas as to the issue are welcome as well. basically it works but it sputters... not the audio connection but the phone actually pauses like 100 times per song.. watching the track timer shows that the phone is actually stopping altogether
I'm looking for the same files on this thread...
http://forum.xda-developers.com/viewtopic.php?p=277931#277931
Related
hi guys, i couldnt help noticing that when i previously used nokia 6600 (symbian s60) they had few 3rd party that is able to make use of their audio mechanism during callls. for example, one software can make selected background noise for opposite callers so they think that u are at a train station for example when infact u r silently at home. another software is an on board answering machine, which after the phone rang for a few times it answer the fonecall with your automated recorded voice and recorded a msg left by the caller on the fone. this is convenient for us so we dont need to call back our voicemail and reduce cost as well as some telco charge to use their voicemail service. im surprised these kind of software have not came out for our windows mobile device when its already available for symbian. im sure it shouldnt be that hard to make it. any coder expert wanna give it a go??
cutefox, what kind of searches have you made for this software on this board? Did you have much luck?
V
i already tried commercial such as handango and pocket gear.. even freeware sites also no luck.. jus dun understand why no 1 made one yet.. shouldnt b too hard to make one.. it will be a big market to sell such a software for our ppc phone device now that more devices is coming out..
Cutefox: have you tried searching this board? Let me save you the effort, but it'll be a good idea next time. It's not generally considered possible, at least on WM2003 devices because of both hardware and software limitations. It's not that no one has thought of it before: someone seems to think of it approximately every two days... but there are many many threads on this issue.
V
Look at what I said here...
http://forum.xda-developers.com/viewtopic.php?t=9761
That sums up why we can't do it using the api's available to us now. The funny thing is the way bluetooth sends the audio stream to a headset. Obviously the data is getting there somehow but I suspect it is not (directly) via windows. Dose anyone know if the radio hardware for bluetooth is connected to the radio hardware for the phone? My guess is that if you could write a program that windows "sees" as a headset then you could get the audio that way. But thats a problem in itself.
I would love this kind of program myself. How is it that such usefull devices with so many capeabilities can be kept secret from us. We can't use the camera, we can't get the cell id on towers, we can't programatically controll the partnerships in blutooth, we cant get the audio stream of our own phone, the events on some ppc's that control brightness are secret..... the list goes on. This kind of #@!!$$ is going to hurt the future of these devices which I otherwise love.
OdeeanRDeathshead: I had read your previous posts, and as ever, very interesting and informative reading. I had the same idea regarding a "dummy" bluetooth device a while back, but mamaich put me in my place!
http://forum.xda-developers.com/viewtopic.php?p=179839#179839
V
thanks vijay555, thats what I have suspected about the hardware. What I want to do is a bit different. The bluetooth can communicate to many devices at once. If your program could appear to be a headset to the os, then the phone bluetooth hardware could transmit the audio to the headset at the same time your program uses bluetooth to receive it. Kind of like a loop out of the box to bridge the lack of functionality. This shifts the problem to how dose a hardware bluetooth headset communicate. Emulate this and we are on a winner. I don't think I have the willingness to pull my devices appart. I also do not have the money for some of the hardware (eg good digital oscilliscope) that I would need to measure whats going on. I did read that microsoft are about to expose some new api to allow control over the pairing process (but not the audio stream). I hope that we get some soon.
Is there going to be any new (for 2005) free development tools like the evc versions used today?
OdeeanRDeathshead: re eVC, I don't think so. The "express editions" are free, but they specifically omit the functionality to develop "mobile solutions".
Re the loop back. That's a good idea. I think mamaich is our best bet on schematics, I think that would be very helpful. As you "rave", it's mindboggling that Microsoft still haven't revealed or implemented a way to interact with the audio channels. It must have been one of the first things one could imagine doing once you develop a PDA with a phone stuck on the back of it.
Any idea if the bluetooth stacks could support transmitting and receiving simultaneously in this manner? I know some of the boys are working on alternative bluetooth support for the stereo headset profiles, so they might be able to shed some light on the issues involved. I guess the processor overhead could be hefty, but for the benefit it would be beneficial.
V
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
Hi,
I am currently looking for a piece of software that will do a specific job, or possibly a better solution to what I am trying to do. Let me give you a little bit of background...
I have got an O2 XDA Mini S, and a Parrot hands-free kit that does not support the A2DP bluetooth profile (only the handsfree profile). I am currently using TomTom 6 on my XDA with a bluetooth GPS unit. Everything works really nicely together, except I cannot get instructions from TomTom through my parrot (which is ultimately my goal).
The only way I can see of getting the TT instructions through my Parrot is to make use of the programs floating about that allow you to turn on and off redirection of sound through bluetooth. The idea I had was that if there was a program about (or maybe even write something myself) that would be able to signal when the sound coming out of the XDA exceeded and then dropped back below a threshold level, and then somehow link that into the bluetooth redirection programs, I could basically have any sound that is produced go through the Parrot only when they occur (including obviously the TT instructions).
Does anybody have any ideas on this? Any help would be greatly appreciated.
Thanks.
Point UI, a UI wrapper, has a feature similar to what you're describing. It's used just to save battery power by turning on BT only when an incoming call is detected, and then killing BT after the call is ended. I don't know if it's open source, but you might want to head over to their forums and see if you can find out how they did it.
You probably also want to haunt any TomTom forum sites (if any even exist).
As a final option, look into Mortscripts. People have done amazing tricks with Mortscripts, and this might be just the ticket. Mort haunts these boards, and may pipe in with an "I can (or cannot) do that with Mortscript" too...
I have a question, though. What's wrong with using the Wizard's built-in speakers for getting directions?
Myrddin Wyllt said:
I have a question, though. What's wrong with using the Wizard's built-in speakers for getting directions?
Click to expand...
Click to collapse
To be honest, it's not too bad through the speakers although if I have my radio on which I usually do, sometimes it can be a little bit hard to hear, and it would be nice to just have the radio mute while it gives me the directions.
It's more of a "want" than a "need" really.
Thanks very much for the info
Myrddin Wyllt said:
Point UI, a UI wrapper, has a feature similar to what you're describing. It's used just to save battery power by turning on BT only when an incoming call is detected, and then killing BT after the call is ended. I don't know if it's open source, but you might want to head over to their forums and see if you can find out how they did it.
Click to expand...
Click to collapse
It is quite easy for programs to detect when you're in a call - MortScript, I presume, probably can detect that quite easily as it's an overall Windows feature and will probably have a readily available part in the API.
The problem is not with turning the bluetooth on and off, it's actually detecting when TomTom is giving an instruction. To be honest I think I'll look into MortScript and if that can't do it then I'll probably just give up.
Detecting phone calls isn't that easy, and it's especially not easy to make a check in a simple procedural script language like MortScript (up to WM5, there's no way to check whether a call is active, you have to monitor all the time if a call is accepted or hung up).
Detecting sound output of another application is entirely impossible - at least for most applications. If the app opens the output channel only during output (which most don't because it takes valuable time and causes ugly "click" noises on some devices), one could maybe query the number of free output channels - but that would need a CPU hog monitoring all the time, or half of the message would be over until it's detected.
And even if that would work, there's simply no way to redirect output to a BT headset (except with A2DP). At least on most devices. Once there was a simple way to do that (you just had to open a virtual port, and as long as it's open, everything was redirected similar to the A2DP way nowadays), but most manufacturers didn't implement it, and nowadays it seems like no modern device supports it anymore. (Had it for test purposes in a MortPlayer beta, no user reported it works...)
So, to put it short: Currently it's impossble. Maybe WM8 might change that... (Few hope for WM7, it's proposed to have the same kernel as WM5 and WM6.x)
Hi,
I was checking the Rhodium Android forum, and found the following developing work:
http://forum.xda-developers.com/showthread.php?t=1076884
Is anyone able to check if this may work on our blackstone?
I'm happy with the FRX6, but audio shutering and lack of BT make it not suitable for daily basis.
If someone make this fixes to work, pls post a tutorial!
Thanks
Audio stuttering has been 'worked around' ages ago, see http://forum.xda-developers.com/showthread.php?t=999544
As for BT, i don't know about that. In the second post there's something about Broadcom an TI chips, so if the Blackstone has a Broadcom chip why not just try it out. The instructions for the setup are all there in the thread
Let us know how it turns out
ypsmav said:
Is anyone able to check if this may work on our blackstone?
Click to expand...
Click to collapse
Why can't You try on your phone?
i had test libhtc_acoustic with acoustic supported kernel.Sound working but only on call speaker but not on loud speaker or audio jack.Need for viruscrazy to update the lib and kernel to support all devices.Audio stutter still there.Still no clean fix when u disable battery service during listen to mp3.You will end up listening to mp3 not knowing your phone going to die.Audio stutter will be fix when there are no resource and excessive service running
I just purchased an A501, rooted it and am running the Alexander III rom, (very nice job on the rom!!!)
I was hoping I would get the bluetooth Headset HSP profile in the new rom but sadly it was not there.
A little research has shown that there is a Bluez driver plugin installed and various bluetooth libraries, my question is can I potentially just replace these libraries with bluez libraries from another rom that has the HSP profile?
I really need to get the bluetooth headset profile working on this A501, and am willing to pay a bounty for help in getting it working
Sorry to say, it doesn't work... as with most other Tablets.
Just using some libs from another ROM isn't going to work either, unless they are extremely similar... and all ROMs similar enough to try such a stunt are almost definitely broken as well.
Sorry, but you'll have to roll your own BT stack if you're desperate enough to try... I'm not gonna.
haag498 said:
Sorry to say, it doesn't work... as with most other Tablets.
Just using some libs from another ROM isn't going to work either, unless they are extremely similar... and all ROMs similar enough to try such a stunt are almost definitely broken as well.
Sorry, but you'll have to roll your own BT stack if you're desperate enough to try... I'm not gonna.
Click to expand...
Click to collapse
Still doing a little research on this. I discovered, in the Bluetooth folder, a couple of files pertaining to what Acer has deemed "black listed", which simply means, certain brands and models are not allowed to work with bluetooth. System/etc/bluetooth/
Also noted, if you modify the files, you need to make changes in a couple of other module files (android_bluetooth_ScoSocket.cpp). The info in the above files tell you where to look.
Not sure why Acer black listed those devices. Legal reasons maybe? Plain incompatibility? Who knows.
My dev skills, are not quite up to modifying .cpp files. Probably enough to muck things up really good Not to mention, I would have no way to test them. But when I get a chance, I'll see what's in them.
Of course most of this pertains to Auto pairing, so might not be of much use. As with the .so files in the Bluez folder, you'll need to de-compile them first to see what's in there.
Also, I saw some bluetooth apps onn the market that some folks had some success with getting HSP. Not the off/on widgets but an app itself. Might want to give them a try and see if you can get the headsets to connect.
Additionally, it seems bluetooth headset problems seems to be across all devices, and not just the a501, but Zoom, Transformer and Thrive as well. Hit and miss with what works. Most issues say the mic doesn't work.
I tried a couple of the apps with no joy on my plantronics earpiece but one of the widgets actually connects...for just 2 seconds...then disconnects...I think the capability is there and you are correct there is some file manipulation that needs to occur...
I have a friend in Egypt that is very good with android bluetooth, he is working on another project right now but when he finishes his current project I will send him these files...he might be able to figure it out ...