I did a search in here but there are so many results...
I have been playing with the 1.5 build DZO posted on his page. Bluetooth seems to work, but I am having a hard time synching my contacts. Anyone know other builds with functional Bluetooth?
have u tried to
is ur data the problem or is it just ur contacts?
I actually got the contacts synched after a bit of tinkering. Still, I am wondering what other builds have the working bluetooth. I am assuming this is a different beast than the xROMs of a few months ago as it was taken directly from DZO's site.
Does that mean limited bluetooth drivers have been developed for the touch? I was playing around with mine tonight and it was working. If I can have bluetooth on say a 1.6 or a 2.x version of Android, then I may really give up win-mo for good.
yea
I dont believe there is a working 1.6 or 2 with bluetooth.. for now at least. Ur best bet is that build. Its also one of the fastest (if not the fastest) and stable around.
lgevo said:
I dont believe there is a working 1.6 or 2 with bluetooth.. for now at least. Ur best bet is that build. Its also one of the fastest (if not the fastest) and stable around.
Click to expand...
Click to collapse
I'm pretty sure a 1.6 build (like Donut AOSP by plemen) flashed on NAND with dzo's latest kernel will have bluetooth enabled...along with GPS and usb headset audio
What Is the Difference between each of these? I would like to know why I would want to upgrade from 1.5.
Oh boy.. lol.
1.6 and up do qvga resolution very well, but do not have working bluetooth yet
2.0 and up don't sleep properly because of the audio driver (which we are working on) unless you use a hacked kernel (which I don't recommend) and have a newer interface/livewallpapers etc..
I would suggest to try donut for now if you're thinking of upgrading.
dzo committed a change the other day that supposed to enable bluetooth in 1.6 - i didn't test it with a headset but I was able to pair it with my pc. Although no one has posted a build with that change included yet.
If that helps.
mrkite38 said:
dzo committed a change the other day that supposed to enable bluetooth in 1.6 - i didn't test it with a headset but I was able to pair it with my pc. Although no one has posted a build with that change included yet.
If that helps.
Click to expand...
Click to collapse
Do you have a link to that. Where did you read that? I would like to check it out.
http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/bootenv.git;a=summary
It's currently the most recent commit.
Hi all,
I wonder why no one is asking or investigating the AVRCP issues on ROM's without Sense? It looks like something is missing in those roms that can be found inside Sense ones.
The bt call function is working as designed but play/pause/next/prev doesn't.
Any ideas?
The issue is that HTC have used their own bluetooth stack in their Sense based roms.
This stack supports the features that you are talking about.
Unfortunately, stock roms use a different stack which do not have the same features as the Sense stack.
This isn't an issue only on the HD2.
Can we get that stack and put it to nonSense roms?
AVRCP has been working on every CM6 build I've tried until recently. Just over the last week or so since I've updated to more recent nightlies I've found its stopped working. I'm currently using ginger_hd2 and it doesn't work. Also the mdj aosp gingerbread doesn't work and mdj streak ram v0.5. All the builds I've tried today!
I was using passion nightly 270 (or bravo, can't remember) and that worked fine.
Sent from my HTC HD2 using XDA App
Never worked for me since I tried HyperDroid and other roms.
I'm going to revert back to my old build later today to see if it still works. I thought it might be a problem with my headset as I dropped it the other day but I tested it last night with Windows Media Player on my PC and it worked OK, switching tracks, play, pause, etc.
Will let you know how it goes.
Sent from my HTC HD2 using XDA App
OK - It definitely works with my previous build.
This build is based on the Passion nightly CM6.1 v270
As I say, I've had it working on pretty much every build since the beginning of Android on the HD2 - it's only stopped working on the Gingerbread-type builds.
ie. It doesn't work on MDJs actual 2.3, or the Ginger_HD2 based on 2.2.1 with Gingerbread-style notifications, etc.
I can't work out if it's coincided with me using builds which have the newer initrd.gz...
Let's hope someone who knows about this stuff reads this thread!
What is this build with CM 6.1? Can you link it?
http://www.multiupload.com/FQCU3UV070
Try this... this one's based on 293 nightly.
Mine was a hybrid I kinda created myself using michyprima's nightly build v4, then incorporating the passion 270 files. If you look at this thread:
http://forum.xda-developers.com/showthread.php?t=824601
It'll explain how to do it...
OK, well I did some trying to fix it using MDJs Gingerbread v0.8 but no joy.
I tried replacing the three bluetooth libraries (libbluedroid.so, libbluetooth.so and libbluetoothd.so) with the working ones from my build but that didn't work.
I also tried replacing the AudioBTID.csv file as it had some slight changes and whilst it didn't fix the issue, it doesn't seem to have broken anything.
I'm currently looking at the bluetooth conf files in /system/etc/bluetooth to see if there's any differences there... think we need some dev help on this one though - I'm pretty much at the limit of what I can do....
Nope, no difference in the conf files. Also changed over the two .so files in /system/etc/lib/bluez-plugin
Again, this didn't work but didn't seem to break stuff!
That's bad. Even Sense roms has problems with media controls profile such as connecting automatically to Phone Audio only.
I feel like 1 from 1000 use it, so nobody cares
Just in case anyone finds this thread again...
MDJs NAND CM7 builds now have AVRCP working again. If you want a build without sense but with this working I suggest you try them! I'm a happy camper again!
Sent from my HTC HD2 using XDA App
Any updates on AVRCP on our devices? I am on CM7 (BoyPPC HoneyComB v31), and AVRCP does not work Do the GB sense ROMs have AVRCP capability?
I tested a few SD ROMS and AVRCP works with:
RAFDROID_HD_SD_4_2 (Sense)
AmeriCanAndroid (Gb)
JaguarMIUI-V11 (Gb)
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 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 ...