It's got me thinking about this whole thing.
WHAT IF you could "rewrite" the radio stack, much like Linksys has provided the source code so that avid developers and Linux lovers could mess around with it?
Could we possibly enable EDGE capability? Could we retune to get 850 instead of 900 MHz? Could we get 802.11g out of b devices?
Since the radio stack can obviously be changed regardless of the CE ROM, it may not be tied too directly to jump points in memory (unless the developers are following a fixed structure on how to build the stack).
I'm thinking back in the days when latter 33.6k modems were flash-upgradable to 56k with that K56Flex/X2 fiasco back then...
If the hardware is there and is primarily software-controlled, it just takes the right reprogramming to get it right.
Anyone care to support or debunk the theory?
i thought most of this stuff is hardware related.
BeyondtheTech said:
Could we get 802.11g out of b devices?
Click to expand...
Click to collapse
Radio stack has nothing to WiFi or bluetooth. It is only for GSM part of device. On BA bluetooth chip can be software-upgraded to BT 1.2, WiFi - cannot be upgraded.
Regarding adding EDGE, etc. Even in the case if hardware supports it, noone would share complete sources of radio stack (it has a proprietary ATI nucleos inside), noone would give you complete technical documentation, and noone would spend his time on making such changes in a ROM. For example, Siemens SL45i hardware supports GPRS, but it was never implemented and noone could do that.
BeyondtheTech said:
It's got me thinking about this whole thing.
WHAT IF you could "rewrite" the radio stack, much like Linksys has provided the source code so that avid developers and Linux lovers could mess around with it?
Could we possibly enable EDGE capability? Could we retune to get 850 instead of 900 MHz? Could we get 802.11g out of b devices?
Since the radio stack can obviously be changed regardless of the CE ROM, it may not be tied too directly to jump points in memory (unless the developers are following a fixed structure on how to build the stack).
I'm thinking back in the days when latter 33.6k modems were flash-upgradable to 56k with that K56Flex/X2 fiasco back then...
If the hardware is there and is primarily software-controlled, it just takes the right reprogramming to get it right.
Anyone care to support or debunk the theory?
Click to expand...
Click to collapse
Depending on the implementation, at least in theory, some of this may be possible. Some of the 56k modems were designed to use a DSP that was capable of support both protocols, and possibly others depending on the capability of the DSP. However, there are also several hardware limitations in some of the phones that will make some of these changes impossible.
As far as supporting EDGE, I believe that it would be quite a bit more difficult because of the modulation techniques required. If this was even feasable, the radio stack (DSP) code would be needed to be re-written to support more modulation techniques (assuming that this wasn't done in hardware).
Considering that there is a serially programmed clock synthesizer chip built into the Wallaby to address each 200 kHz channel, in theory it should be relatively easy to modify the codes to use 850 MHz channels in place of the 900 MHz ones (Assuming you have the source code). The only other limiting factor I can think of would be the RF section.
As already mentioned, I seriously doubt that you would be able to re-write code to make 802.11b support 802.11g because of some of the hardware differences.
As already mentioned, I seriously doubt that you would be able to re-write code to make 802.11b support 802.11g because of some of the hardware differences.
Click to expand...
Click to collapse
Of course, if we had the radio stack code, we could potentially make BT emulate Wifi - since they both technically share the same frequency at 2.4ghz.
(Edit: Then again, maybe not. )
And also, proprietary GSM/CDMA/whatnot modules are pretty much the only obstacle to a truly Open Source phone. >_>
Related
As per the xda-developers Wiktionary:
"The radio stack is responsible for the phone functionality of the Hermes (or any other...). This includes GPRS, GSM and UMTS operations"
Fine! Now, What are the bolts and nuts that make a radio to work better or worst than other for such and such operator and devices? Like: Better signal, Clearer voice / sound from one side or the other, Drop calls, Lost calls.... etc.
not sure what you ask but the radio stack is embedded software for the chip in the gsm/umts module in the device's
newer versions could both be fixing issues and interducing new ones if they are unlucky
Rudegar said:
not sure what you ask but the radio stack is embedded software for the chip in the gsm/umts module in the device's
newer versions could both be fixing issues and interducing new ones if they are unlucky
Click to expand...
Click to collapse
Well, we can add your description to the xda-developers wiktionary, thanks!
But I´m trying to dig in more detail on what precisely makes the "newer versions could both fix issues and introduce new ones", I´ll edit the original post to try to make myself clearer.
without having looked into it
i'd guess it was a dsp and the radio stack was the embedded
software which makes the dsp chip do the
gsm demodulation and downmixing
what makes the difference is most likely just timings
and possible different resolutions of the filters
the better the filter the worse the timing
so it's really about the balance
and varies between different operations and the age of their
gsm equipment
I thought it was so strange that when I scanned for bluetooth devices I picked up my (pc) internet modem (which is wireless enabled) so I thought bluetooth and wifi must share a lot of the same characteristics.
I was browsing for the latest Android developments and stumbled on the following
Please take a look at this page http://focus.ti.com/general/docs/wtbu/wtbuproductcontent.tsp?templateId=6123&navigationId=12000&contentId=4679
And this one http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12019&contentId=4635&DCMP=WTBU&HQS=Other+OT+bluetooth
This seems to mean that FM Radio and WiFi is a standard feature of OMAP 850 chips and (for the touch owners look at this page http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12028&contentId=4636&DCMP=WTBU&HQS=Other+OT+agps)
Seems If you have Bluetooth you also have wifi and possibly fm radio built in only lacking the drivers (no special wifi antenna is used in the omap 850 solution accoriding to TI)
It would seem that all we need is the right drivers and regsettings (so no new rom or radio rom should be needed)
Who can make it a working cab?
Woooooooooo!
Good news.
great job
if some solution, make me to buy one.
by the soft solution, strange story !no idea for none cost effective option. why do HTC designers make a 2008 PDA with no WiFi Option!
wow
wow...it might be dream come ture if it happens....please some body develop a driver for pharos Fm radio n wifi.....please buit up some regsettings......
This is a good information. Hope that we could make it work on our Pharos.
Good News... I hope who will make it soon because I don't understand about ARM work.
That is an awesome find man. I hope this info is used to get a wifi working ROM.
I thought it was some kind of cost saving to not include wifi, i.e. some missing hardware. If it's just a driver, that is the so friggen stupid! Why have such a great phone and then neuter it by taking away wifi? And the price is still just as high as the Artemis when it came out. The lack of wifi is the only thing that would keep me from buying one. Otherwise, it would be a great upgrade phone for me since I don't need nor have 3G with my service and and it has the cool flush screen that I wish my Artemis had.
someone knows if the touch dual then also could have the wifi option turned on by drivers? the touch normal has wifi, so i guess it should be possible.
anyone tried the drivers from the htc wizard? it also has a ti omap 850, so driver from such a rom could be coocked into the rom of other devices.
@VOODOOS!L
The touch dual uses the Qualcomm 7200 chipset. That chipset uses the arm926tesj as a co processor but i dont think its the full OMAP 850 chiset.
but there is a project for enabling niki wifi (started out as a project ot enabkle both wifi and gps)
@shawndh
Phone manufacterors do it all the time. Look at the Kaiser story, yes they have some great graphical chip (would be too expensive to make a different chiset with another graphical chip) so they just didnt include the drivers for it.
With some other phones like the touch HTC disabled the wifi in the radio rom... maybe some techies here could try to put an artemis radio rom in the pharos... but for none techies this would probably be an instant brick (thats why i didnt try it) tom_codon maybe you could say something about this....input would be apreciated.
Come to think of it, I remember that they had a crippled GPS radio or something in the TyTn I. The only reason I could think of for disabling wifi is so people who need wifi would buy the the Artemis. To be honest, if I had a choice btwn the two, I would get the Pharos over the Artemis if they both had wifi. Even so, it should still have wifi.
This ia a good news.
I'm waiting.
you know what... im giving up.
ive tried pm ing some guys working on the wifi on nike project, asking tomcodon. no response as yet and prolly not going to get one.
And tried to get qtopia and winlizard(gizard) working.
but in the linux world up is down, left is right, and smart is stupid. those people are (in dutch: contactgestoord) communicationally challenged. you cant find anything on their sites. there is no(or very little) documentation on how stuff works ...noone explains anything... so in order to learn linux you have to know it.
thats why m$ can afford to be so sucky: their competition sucks so much more
i said to the guys at irc #linzwizard hey thnx for the build, i can boot it too (gizard aka linwizard 0.3.0) but the touchscreen driver crashes.
he then said make a support request at sourceforge which i did (btw it isnt obvious how to .. it should be very simple. but hey... thats the linux way, isnt it) response was.. and this is a shocker.. your touchscreen driver doesnt work(.... grrreeeaat) you should disable it...(no description on how)
up for the rom with wifi for the pharos!
Thanks
Not to rain on anyone parade but from the first page from TI, it looks like to get wifi support you have to have a special chip in the phone(upper left corner) thats diferent that the chip to get wifi, so unless someone knows for sure that the WiLink chips are present, I think we are without wifi
Wait and see...
The only problem is... How long does it take to finalize such a ROM?
If it takes 1 yr, for example, I think I will have already changed to at least TouchHD..
Anyway, good news!
Hello! I have a HTC Pharos for one month. Yesterday, i accidentally have wetted phone by tea, and then i disassembled it for cleaning. Cleaning was finish sucсessfully, now phone is working
During disassembly of the device I have made some pictures. I think Wlan module is in the device. Look at the photo! Motherboard have many connectors for external antennas, and Wlan connector is on the board!
http://www.flash-remont.narod.ru/pharos/pharos.jpg
thank you for the picture, its in a good resolution! but what would have made it more clear is if you would have looked for a specific Texas instruments chip with letter combinaton BRF or BL (there are 4 chips mentioned with a dual solution BL6450 BRF 6350 BRF6300 and BRF6150 last one is not good because its a bluetooth only chip) we should also be looking for TI chips with a WL designation and number 1271 1273 1251 1253
at least (BRF6300) - Bluetooth specification v2.0 + EDR single chip should be in the Pharos since we have that bluetooth spec.
in the picture i can make out the TWL3027 chip with extra designation BZQW (at least i think its that chip ... according to the ti site that would be the baseband chip but it doesnt describe on the site what the extra letters mean)http://focus.ti.com/general/docs/wtbu/wtbuproductcontent.tsp?templateId=6123&navigationId=12311&contentId=4706
[URL="http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12025&contentId=4645&DCMP=WTBU&HQS=Other+OT+mwlan"]http://focus.ti.com/general/docs/wtbu/wtbugencontent.tsp?templateId=6123&navigationId=12019&contentId=4635&DCMP=WTBU&HQS=Other+OT+bluetooth[/URL]
hope this is readable since i have a hangover
Kostyan could you post the other pics you made of the interior of the Pharos
avathar behemoth said:
thank you for the picture, its in a good resolution! but what would have made it more clear is if you would have looked for a specific Texas instruments chip with letter combinaton BRF or BL (there are 4 chips mentioned with a dual solution BL6450 BRF 6350 BRF6300 and BRF6150 last one is not good because its a bluetooth only chip) we should also be looking for TI chips with a WL designation and number 1271 1273 1251 1253
=skipped=
Click to expand...
Click to collapse
Maybe this iron box is Wlan module?
http://flash-remont.narod.ru/pharos/pharos2.jpg
I may open this box, if it is requires for this research
And on this picture, front side of device it is found Wlan antenna? (if overwind board, supposed Wlan module with connector correspond (matched) to on position with Wlan antenna, and it connected with module)
http://flash-remont.narod.ru/pharos/pharos3.jpg
avathar behemoth said:
Kostyan could you post the other pics you made of the interior of the Pharos
Click to expand...
Click to collapse
Of course, there is all photos:
http://www.flash-remont.narod.ru/pharos/pharos.jpg
http://www.flash-remont.narod.ru/pharos/pharos2.jpg
http://www.flash-remont.narod.ru/pharos/pharos3.jpg
http://www.flash-remont.narod.ru/pharos/pharos4.jpg
http://www.flash-remont.narod.ru/pharos/pharos5.jpg
http://www.flash-remont.narod.ru/pharos/pharos6.jpg
http://www.flash-remont.narod.ru/pharos/pharos7.jpg
http://www.flash-remont.narod.ru/pharos/pharos8.jpg
Hi,
An idea just hits my mind when I put my nexus s beside my key fob for my room, nexus has shown an unknown tag using NFC technology. The idea is to make nexus reads the key-fob id then use nexus as an alternative key-fob.
Hopefully someone can get this idea out and make it real.
Thank you.
I guess to start, someone will need to be able to tell the NFC to *transmit* instead of just receive.
Sorta like the FM radio chip that's supposedly on board. Someone said in another Nexus S thread that there's an FM radio chip in there somewhere (in the wifi chip maybe?) and that it was intended to be a transmitter.
cormyn said:
I guess to start, someone will need to be able to tell the NFC to *transmit* instead of just receive.
Sorta like the FM radio chip that's supposedly on board. Someone said in another Nexus S thread that there's an FM radio chip in there somewhere (in the wifi chip maybe?) and that it was intended to be a transmitter.
Click to expand...
Click to collapse
this is the chip in the Nexus S and it does indeed transmit and receive FM
http://www.broadcom.com/products/Wireless-LAN/802.11-Wireless-LAN-Solutions/BCM4329
It should be possible. The NFC chip on the NS can do write/card emulation/P2P modes, but they're not enabled in the Gingerbread API. There's library code to get close to doing this in previous revisions of the AOSP projects (see libnfc-nxp.git and Nfc.git projects), but the NFC library's hairy and poorly documented, so it'd be a bit of an effort (I've looked).
Google have said they'll be enabling the write and P2P modes later, so it's either more hackery now, or wait for Google to enable it.
mwak14 said:
Hi,
An idea just hits my mind when I put my nexus s beside my key fob for my room, nexus has shown an unknown tag using NFC technology. The idea is to make nexus reads the key-fob id then use nexus as an alternative key-fob.
Hopefully someone can get this idea out and make it real.
Thank you.
Click to expand...
Click to collapse
The only problem I can think of is the method in which key fobs work. I have a 135i with comfort access and I know for a fact they use a type of rolling code to prevent this kind of thing. You would have to be able to adjust the frequency each time and make sure that your car picked up that same frequency.
That probably doesn't make too much sense, and I'm having a hard time putting it into words so here, this explains rolling codes and how key fobs work:
http://electronics.howstuffworks.com/gadgets/automotive/unlock-car-door-remote1.htm
booyakasha said:
The only problem I can think of is the method in which key fobs work. I have a 135i with comfort access and I know for a fact they use a type of rolling code to prevent this kind of thing. You would have to be able to adjust the frequency each time and make sure that your car picked up that same frequency.
That probably doesn't make too much sense, and I'm having a hard time putting it into words so here, this explains rolling codes and how key fobs work:
...
Click to expand...
Click to collapse
If it's not NFC-compliant tech (which from what you describe, isn't), it won't work, that's a given.
Nfc can be used for secure access so like your coprorate buildings and is liminlted to about 10cm distance. So yes, a car manufacturer could implement it.
As for a radio fob, most of those are 868Mhz low power RF. Funny thing is, NXP, the semi company that makes the nfc chip also makes the 868Mhz RF chip in most car fobs.
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 want to develop a GSM/3G PacketAnalyzer for study purposes, a somewhat more simplified version of OsmocomBB withouth any TX modules. As some of you may know, even though OsmocomBB is open source it has not been ported but to some very old Motorola and SonyEricsson phones. I would love to be able to do something like OsmocomBB on a newer phone so I can link it with a modern android OS system. I've read that Broadcom is one of the open-sourcest Gsm baseband processor manufacturers out there, so - sorry if I have passed some of the information accumulated over here - is there any way I can find any open source RTOS (Real Time Operating System) that is compatible with say Broadcom's BCM28155 so I can modify it and be able to read all GSM/3G stack and transfer this layer 1/2 data to android os? And also be able to re-flash the BCM with a high success rate? Did Broadcom release any CPU drivers or RTOS info on BCM28155?