[Q] Working Froyo gapps? or FMradio?

---

As Ginger waste my battery too quick, I decided to put Froyo on my Tattoo.
I tried first with [ROM] ProjectSense 0.1 [2.2.1] [Sense], which is going great ... but no radioFM.
As I use FMradio a lot (for football, of course), I have been looking and I found [ROM] Latest Froyo AOSP for Tattoo v0.50 released (Final Version) and flashed it.
After a long search to find a working GAPPS for that rom (I found it at goo-inside.me), I've flashed it, but my phone stucks on trying to access Google's servers, and have no way out of there unless you turn off the phone.
Anyone else with him?
So difícult is making an FM radio app to work in sense? (the only thing missing from the ProjectSense to be perfect)
Do not be a matter of adding a "driver" or library to "activate" the chip, and so run the "Spirit FM Radio", for example?

If anyone has any answer is welcome.

Sorry for my english (Google Translator doesn't help too much)

Flash this gapps they will work.

http://forum.xda-developers.com/atta...9&d=1287687798







Hit that tiny tnx button if they work xDD

Originally Posted by VuK$3

Flash this gapps they will work.

http://forum.xda-developers.com/atta...9&d=1287687798







Hit that tiny tnx button if they work xDD

Thanx. By the moment, i'm gonna use ProjectSense Rom. I'll try later if I need it.

Enviado desde mi HTC Tattoo usando Tapatalk

Originally Posted by GbermuG

As I use FMradio a lot (for football, of course), I have been looking and I found [ROM] Latest Froyo AOSP for Tattoo v0.50 released (Final Version) and flashed it.
After a long search to find a working GAPPS for that rom (I found it at goo-inside.me), I've flashed it, but my phone stucks on trying to access Google's servers, and have no way out of there unless you turn off the phone.
Anyone else with him?
So difícult is making an FM radio app to work in sense? (the only thing missing from the ProjectSense to be perfect)
Do not be a matter of adding a "driver" or library to "activate" the chip, and so run the "Spirit FM Radio", for example?

"Spirit FM Radio" is my app. It doesn't care about Sense.

But for a TI chip device like the Click/Tattoo, it requires a Bluez compatible Bluetooth stack, as is found on CM and some other ROMs.

Also, my app needs a way to turn on the FM audio path. On a Sense based ROM this might be the "HTC" Audio Method that needs to be configured.

Originally Posted by mikereidis

"Spirit FM Radio" is my app. It doesn't care about Sense.

But for a TI chip device like the Click/Tattoo, it requires a Bluez compatible Bluetooth stack, as is found on CM and some other ROMs.

Also, my app needs a way to turn on the FM audio path. On a Sense based ROM this might be the "HTC" Audio Method that needs to be configured.

I supose the problem is ar bluetooth stack, as you say, because ProjetcSense isn't a CM based rom. I installed your app, and configured audio method in all the posibilities, included "HTC", but it's allways saying me "compatible chip not found", or something like.

Today I'm gonna make a backup, an change some files from other Froyo Rom with FMradio working. Another thing I'm going to try is changing some values in build.pro, cause this Rom has BT chip identified as BCM4329-B1, but I read in some threads it's a different one.

Thanks anyway.

The exact message is:
"Sorry, compatible FM chip not found...
FM:TI Sh:1 Su:1 Bt:0 Ht:0 H2:0 M0:TIU"

I think it means.. "FM chip is TI, but BT is 0, so I can't make it works". And now, th question is... why BT:0, if Bluetooth is on?

I was cooking a sense 2.2.1 ROM and I made everything work except FM radio.I fond mikereidis thread about TI chip but i was unable to enable it
When I try shell command it always says access denied....
Any ideas ?

Something has changed.
I tried to use the fm_script by cm.fyodor, and when I wrote the comman at Terminal CMD, I receive many lines resumed on two: "bttest: not found" and "hcitool not found".
Looked for the files at Fyodor's [ROM] Latest Froyo AOSP for Tattoo v0.50 released (Final Version), and found them at /system/xbin. So, I'd copy the files to my phone, and retry the "Spirit FM Radio".
But the message I had (2nd line) now is "FM:BC Sh:1 Su:1 Bt:1 Ht:1 H2:0 Mo:BCU".

After it, I edit settings->debug and check "Use fm_hcitool" and set FM chip to "Automatic", but app is still not working.

I've deleted info about BT chip in build.prop. Now, when I try to execute fm_script, the message is "HCI command: XXXXXX Send failed: File descriptor in bad state". Back to previous build.prop, same message: "Send failed"

I'll keep on trying things...

I'm pretty sure this device uses a TI chip for FM, BT and WiFi. My app, and the script that I think came from me originally, was working on this device back when my app generally only ran on the HTC Legend. I think these are the only 2 HTC devices using the TI chip.

Yes, I think the problem is that stock HTC ROMs use the Broadcom or TI proprietary Bluetooth stack. So just about anyone making a Sense based ROM uses that same stack.

"Send failed: File descriptor in bad state" happens when trying to use hcitool with the proprietary stack. (But can also happen with other fatal errors that are fixed by restarting BT.)

If I am correct, then I'd think the HTC FM app would work. Is there a btipsd process running ? That's the proprietary TI stack. On the Legend, there is a btipsd_cli binary that my app can use with this stack. I don't think anyone by myself has ever used this mode, LOL.

Here's the binary if you want to try. The btipsd version might need to match somewhat though: http://www.mediafire.com/file/p0w159...btipsd_cli.zip

If you copy files from a Broadcom based BT device, then you can confuse the automatic FM chip detection, which is why I think you saw "Mo: BCU" (Broadcom unknown.) You can force to TI still.

Changing audio method won't help until we can see RSSI and seek working,

So, options:

- There's likely some way to run the HTC FM app for Tattoo/Click or Legend if the TI stack.
- My app will work with Bluez stack
- My app might work with btipsd in the TI stack via btipsd_cli.
- I may at some point support a "direct to BT UART mode" that works with BT off, as I have for Broadcom chips.
- I'm also looking to support the Broadcom and TI stacks more directly, but this likely won't happen for several months at least.

Originally Posted by GbermuG

The exact message is:
"Sorry, compatible FM chip not found...
FM:TI Sh:1 Su:1 Bt:0 Ht:0 H2:0 M0:TIU"

I think it means.. "FM chip is TI, but BT is 0, so I can't make it works". And now, th question is... why BT:0, if Bluetooth is on?

This part of my code doesn't care whether or not Android thinks BT is running.

If any of the following processes are running, it will show "BT: 1":

For Bluez BT:
hcid
bluetoothd
hciattach

For TI proprietary BT:
btipsd

For Broadcom proprietary BT:
btld
brcm_patchram_plus