If you refer to page 23 (Tips and Tricks) of the Motorola Razr User guide (General Tips - last bullet point), it mentions an FM radio.
I know that though the chipset has the hardware for FM, the application is missing ? Or does anyone know if it is hidden anywhere ?
Yes I have post this many times to Motorola support but they don't want to reply
Also pages 30 and 32 mention the FM radio.
The application is present in software as part of the stock music app, but doesn't work.
Sent from my XT910 using xda premium
My guesses are:
1) The manual is copy/pasted from other model's.
2) No FM radio kernel module/driver yet for the current kernel version.
Since the manual had mentioned it, you complaint it to FTC or equivalent. If there no FM radio driver yet, then, we wait and see. The current Android 2.3.5 implementations in RAZR is horrible. Menu's color scheme has no consistency. Most probably the Motorola was rushing to push the RAZR into the market, hoping it can beat GNex.
The FM radio app is there...
1) Get Anycut
2) Create new -> Activity
3) Find FMplayer and create the shortcut in home screen. For the time being, enjoy the FM Radio app....
bahathir said:
My guesses are:
1) The manual is copy/pasted from other model's.
2) No FM radio kernel module/driver yet for the current kernel version.
Since the manual had mentioned it, you complaint it to FTC or equivalent. If there no FM radio driver yet, then, we wait and see. The current Android 2.3.5 implementations in RAZR is horrible. Menu's color scheme has no consistency. Most probably the Motorola was rushing to push the RAZR into the market, hoping it can beat GNex.
The FM radio app is there...
1) Get Anycut
2) Create new -> Activity
3) Find FMplayer and create the shortcut in home screen. For the time being, enjoy the FM Radio app....
Click to expand...
Click to collapse
Wow this is great thanks for the trick! So happy to have my fm radio. I wonder what other goodies are hiding
Tunein Radio Pro is a great app that allows you to listen to radio stations from all around the country, and it's reasonably priced. A one time $.99 charge.
If you dont want to commit to buying they have a free version you can use to see if you like it or not before you buy.
You can get tune in radio for free at Getjar.
Oaklands said:
You can get tune in radio for free at Getjar.
Click to expand...
Click to collapse
I always forget about getjar *facepalm*, only thing about getjar is they are very slow to release updates, if you recieve them at all.
So, is FM radio working for you? I can only enter to app, but radio can't find any station.
grubynawro said:
So, is FM radio working for you? I can only enter to app, but radio can't find any station.
Click to expand...
Click to collapse
Same here, all I get is the message: " Launching FM Radio please wait...."
Dont know.. but as my common sense says... if there is no APK in the system for the FM radio, then how can the FM radio application can tune in or even work..... food for thought????
Or I am a complete idiot??
There doesn't need to be a dedicated apk if it's built into another app, which it is in this case.
Again, people, the software is there, the hardware either isn't there at all or doesn't have the necessary drivers to work with said software. Best case scenario, the hardware is there and Moto liven it with an update.
Sent from my XT910 using xda premium
It's not hidden. The RAZR and Droid RAZR do not have FM radio hardware. The manual is wrong.
abesh said:
If you refer to page 23 (Tips and Tricks) of the Motorola Razr User guide (General Tips - last bullet point), it mentions an FM radio.
I know that though the chipset has the hardware for FM, the application is missing ? Or does anyone know if it is hidden anywhere ?
Click to expand...
Click to collapse
Well if it doesnt have it then us owners should go after them for advertising things that it doesnt have!
Snippets from dmesg...
Code:
<6>[ 3.803466] asoc: cpcap codec <-> omap-mcbsp-dai.2 mapping ok
<6>[ 3.804504] asoc: cpcap in-call <-> MODEM mapping ok
<6>[ 3.805145] asoc: cpcap fm <-> FMDummy mapping ok
<6>[ 3.805603] asoc: HDMI <-> hdmi-dai mapping ok
<6>[ 3.806610] asoc: cpcap bt-call <-> MODEM mapping ok
The FM feature is being mapped to FMDummy, ie, being disabled in kernel level.
From $ cat /proc/asound/pcm
Code:
00-00: Multimedia null-codec-dai-0 : : playback 1
00-01: McBSP3-Codec cpcap codec-1 : : playback 1 : capture 1
00-02: Modem-Codec cpcap in-call-2 : : playback 1 : capture 1
00-03: FMAudio cpcap fm-3 : : playback 1
00-04: HDMI HDMI-4 : : playback 1
00-05: Modem-BT cpcap bt-call-5 : : playback 1 : capture 1
00-06: McBSP3-BT cpcap bt-6 : : playback 1 : capture 1
00-07: SPDIF dit-hifi-7 : : playback 1
00-08: McBSP3-BP BPVoice-8 : : playback 1 : capture 1
00-09: FM cpcap stdac-9 : : playback 1
Here we can see there is FMAudio audio device exist, but since it being disabled during boot up. and I might be wrong,
I really hope Motorola can get the proper kernel module/driver for WL1285C chipset. because the boot loader is locked for developers to try newer or better driver.
Thank you.
bahathir said:
Snippets from dmesg...
Code:
<6>[ 3.803466] asoc: cpcap codec <-> omap-mcbsp-dai.2 mapping ok
<6>[ 3.804504] asoc: cpcap in-call <-> MODEM mapping ok
<6>[ 3.805145] asoc: cpcap fm <-> FMDummy mapping ok
<6>[ 3.805603] asoc: HDMI <-> hdmi-dai mapping ok
<6>[ 3.806610] asoc: cpcap bt-call <-> MODEM mapping ok
The FM feature is being mapped to FMDummy, ie, being disabled in kernel level.
From $ cat /proc/asound/pcm
Code:
00-00: Multimedia null-codec-dai-0 : : playback 1
00-01: McBSP3-Codec cpcap codec-1 : : playback 1 : capture 1
00-02: Modem-Codec cpcap in-call-2 : : playback 1 : capture 1
00-03: FMAudio cpcap fm-3 : : playback 1
00-04: HDMI HDMI-4 : : playback 1
00-05: Modem-BT cpcap bt-call-5 : : playback 1 : capture 1
00-06: McBSP3-BT cpcap bt-6 : : playback 1 : capture 1
00-07: SPDIF dit-hifi-7 : : playback 1
00-08: McBSP3-BP BPVoice-8 : : playback 1 : capture 1
00-09: FM cpcap stdac-9 : : playback 1
Here we can see there is FMAudio audio device exist, but since it being disabled during boot up. and I might be wrong,
I really hope Motorola can get the proper kernel module/driver for WL1285C chipset. because the boot loader is locked for developers to try newer or better driver.
Thank you.
Click to expand...
Click to collapse
Ok know im really confused, there is or isn´t hardware for FM radio??
You need proper kernel driver for FM device to be working in Android OS. For time being kernel is not "recognizes" the FM device yet.
I am not sure if the WL1285C chipset has no fm radio hw/circuitry, I cannot find the specs sheet yet.
Sent from my XT910 using XDA App
How is going this issue? Any update?
The chipsets from the ogdriod and on have been revisions of similar Texas instruments chips that include Bluetooth, wifi, and FM radio, on one chip, but it is very difficult to find drivers that will compile into a working kernal and not break everything else
Sent from my DROID RAZR using xda premium
Related
Hi All,
Recently, inspired by the progress with the camera, I started an "investigation" on how the FM radio actually works on out Tattoos. Unfortunately I am not able to continue working on that (not atleast until March), so I decided to share the information on the FM radio that I have so one of you folks can try to get it working.
The FM radio on Tattoo is handled by the BRF6350 chip. It is actually responsible mainly for the Bluetooth, but it also handles the FM radio. I've decided to search a bit more about the chip and found that TI has released a library (brflinux available here). That library is actually compiled in the bts daemon (the daemon responsible for both Bluetooth and FM radio on the official 1.6 ROMs). To function, this library also needs "an init script" that is a proprietary file called FMInit_300.bts under /system/etc/firmware/ .
The BRF6350 chip has analog audio output that is connected to a switch, controllable by the sysfs interface. That switch is accessable by the file /sys/class/htc_accessory/fm/flag . If you read from it you can see the current state, if you write to it you can change the current state. The file can handle the following strings:
"disable" - Turn off audio output by the BRF6350 chip
"fm_headset" - Turn on audio and send it to the headphones
"fm_speaker" - Turn on audio and send it to the phone speaker
When FM radio is off the switch should always be set to "disable" and when the radio is turned on the state should be set to "fm_headset" (atleast that is what is done on the official ROMs).
To detect if the headset is connected (that is your anthenna). You should read the following sysfs file /sys/class/switch/h2w/state a number is written there (in ASCII), that describes the state of the headset. The bits in that number have the following meaning:
#define BIT_HEADSET (1 << 0)
#define BIT_HEADSET_NO_MIC (1 << 1)
#define BIT_TTY_FULL (1 << 2)
#define BIT_FM_HEADSET (1 << 3)
#define BIT_FM_SPEAKER (1 << 4)
#define BIT_TTY_VCO (1 << 5)
#define BIT_TTY_HCO (1 << 6)
#define BIT_35MM_HEADSET (1 << 7)
atleast bits 0 or 1 and 7 should be set if the headset is connected.
After I had this basic info gathered, I began to search for application of all that.
In the following topic an interface is described that could be used for the FM radio on ROMs for our Tattoos. If we can connect the brflinux library to the JNI interface at the base of the new CyanogenMod FM radio application, we can have the radio up and running.
In fact the interfaces of the JNI library (at the base of the FM radio app) and the brflinux library are very similar so it would be quite possible.
Hope this was useful.
Cheers,
Rosti (a.k.a pisaro)
thank you very much!!
Why is not this topic in the Click DEVELOPMENT forum?
thanks pisaro for your work. I hope some one could continue with it.
Thanks for your effort
pisaro said:
The FM radio on Tattoo is handled by the BRF6350 chip. It is actually responsible mainly for the Bluetooth, but it also handles the FM radio. I've decided to search a bit more about the chip and found that TI has released a library (brflinux available here). That library is actually compiled in the bts daemon (the daemon responsible for both Bluetooth and FM radio on the official 1.6 ROMs). To function, this library also needs "an init script" that is a proprietary file called FMInit_300.bts under /system/etc/firmware/ .
The BRF6350 chip has analog audio output that is connected to a switch, controllable by the sysfs interface. That switch is accessable by the file /sys/class/htc_accessory/fm/flag . If you read from it you can see the current state, if you write to it you can change the current state. The file can handle the following strings:
"disable" - Turn off audio output by the BRF6350 chip
"fm_headset" - Turn on audio and send it to the headphones
"fm_speaker" - Turn on audio and send it to the phone speaker
Click to expand...
Click to collapse
Much thanks ! Just the info I was looking for.
If I can get this FM audio routing working, I think I'll have FM radio working on my HTC legend, but I'd guess it'd work for many of the phones using BRF6300/BRF6350/BL6450 aka WL1271/1273/1281/1283 etc.
I have the hcitool commands that have the FM working I'm pretty sure. RSSI responds to tuning and antenna movement as I'd expect.
Now, where can I find FMInit_300.bts ? No results on google search. I'm not really convinced I need it, I have other files such as fm_rx_init_1273.2.bts and fmc_init_1273.2.bts, AND I think I've sent all the needed commands via hcitool, except perhaps for audio routing.
thank you very much!!
Looks good mate!
mikereidis said:
Much thanks ! Just the info I was looking for.
If I can get this FM audio routing working, I think I'll have FM radio working on my HTC legend, but I'd guess it'd work for many of the phones using BRF6300/BRF6350/BL6450 aka WL1271/1273/1281/1283 etc.
I have the hcitool commands that have the FM working I'm pretty sure. RSSI responds to tuning and antenna movement as I'd expect.
Now, where can I find FMInit_300.bts ? No results on google search. I'm not really convinced I need it, I have other files such as fm_rx_init_1273.2.bts and fmc_init_1273.2.bts, AND I think I've sent all the needed commands via hcitool, except perhaps for audio routing.
Click to expand...
Click to collapse
I attach the file FMInit_300.bts extracted from a HTC 1.6 ROM. I hope it helps you with your work.
http://www.megaupload.com/?d=NRMYDZI2
Looking forward to seeing more progress!
Our phones would show, with fm radio and gingerbread.
pisaro said:
Hi All,
Recently, inspired by the progress with the camera, I started an "investigation" on how the FM radio actually works on out Tattoos. Unfortunately I am not able to continue working on that (not atleast until March), so I decided to share the information on the FM radio that I have so one of you folks can try to get it working.
The FM radio on Tattoo is handled by the BRF6350 chip. It is actually responsible mainly for the Bluetooth, but it also handles the FM radio. I've decided to search a bit more about the chip and found that TI has released a library (brflinux available here). That library is actually compiled in the bts daemon (the daemon responsible for both Bluetooth and FM radio on the official 1.6 ROMs). To function, this library also needs "an init script" that is a proprietary file called FMInit_300.bts under /system/etc/firmware/ .
The BRF6350 chip has analog audio output that is connected to a switch, controllable by the sysfs interface. That switch is accessable by the file /sys/class/htc_accessory/fm/flag . If you read from it you can see the current state, if you write to it you can change the current state. The file can handle the following strings:
"disable" - Turn off audio output by the BRF6350 chip
"fm_headset" - Turn on audio and send it to the headphones
"fm_speaker" - Turn on audio and send it to the phone speaker
When FM radio is off the switch should always be set to "disable" and when the radio is turned on the state should be set to "fm_headset" (atleast that is what is done on the official ROMs).
To detect if the headset is connected (that is your anthenna). You should read the following sysfs file /sys/class/switch/h2w/state a number is written there (in ASCII), that describes the state of the headset. The bits in that number have the following meaning:
#define BIT_HEADSET (1 << 0)
#define BIT_HEADSET_NO_MIC (1 << 1)
#define BIT_TTY_FULL (1 << 2)
#define BIT_FM_HEADSET (1 << 3)
#define BIT_FM_SPEAKER (1 << 4)
#define BIT_TTY_VCO (1 << 5)
#define BIT_TTY_HCO (1 << 6)
#define BIT_35MM_HEADSET (1 << 7)
atleast bits 0 or 1 and 7 should be set if the headset is connected.
After I had this basic info gathered, I began to search for application of all that.
In the following topic an interface is described that could be used for the FM radio on ROMs for our Tattoos. If we can connect the brflinux library to the JNI interface at the base of the new CyanogenMod FM radio application, we can have the radio up and running.
In fact the interfaces of the JNI library (at the base of the FM radio app) and the brflinux library are very similar so it would be quite possible.
Hope this was useful.
Cheers,
Rosti (a.k.a pisaro)
Click to expand...
Click to collapse
Thanks for your info. Most of the solution to the FM Radio is what you said here some time ago, so I want to congratulate you for this previous vision you gave us
THANKS
Hello,
Is there an application to transformed galaxy S3 into a universal remote can control duplicator replace the remote controls portal, Gara door... of any brand.
for example:
Remote Control Duplicator / Clone Remote for Garage Doors, Gates
http://www.youtube.com/watch?v=WQTvhEMy2ss
Thanks,
DjeDje
djedje_zr7 said:
Hello,
Is there an application to transformed galaxy S3 into a universal remote can control duplicator replace the remote controls portal, Gara door... of any brand.
for example:
Remote Control Duplicator / Clone Remote for Garage Doors, Gates
Thanks,
DjeDje
Click to expand...
Click to collapse
First of all, the SR-RCD-M1 duplicator you mentioned & most on the market are fixed code duplicators, which means the remote control transmit the same signal during each and every transmission. ( it not 'any brand' - especially when your garage doors use rolling code technology ).
Second, you may need to attach a RF module to your phone, to receiver & transmit signal, mostly at 433.92mhz which Came Top432na / Nice Flo uses, and there are other frequencies such as 310 / 315 / 418 / 868 ( which Hormann, Marantec, SR-RCD-868 duplicator uses ) etc, if you don't have matching modules, you simply can't read and duplicate the signal.
And third, you will need to program your own software to read & playback the signal you captured, since you're using a modern phone which has large memory, so you can simply record a fixed timespan signal, such as 1 second, and playback ( like a recorder ).
Hope it helps.
Dear all,
I'm working on custom hardware built on Amlogic AML8726-MX SoC. I have the board working with Android 4.2.1 compiled with telephony support. We use standalone GSM module from Telit and I successfully implemented RIL and I'm able to make or receive calls. Unfortunately I'm stucked with routing the audio. The module has digital i2s interface and I connected it through I2S<->USB Audio converter to the SoC.
So now I have two Alsa devices - one is dedicated to analog interfaces (speaker, headphones, microphone) and is working in android applications. The second one represents USB audio and I'm able to use that on kernel level with command line interface. Now I need to to connect these two together to be able to play the voice call using analog interface.
Is there please anyone who can point me into right direction? I'm experienced in kernel development, but going into higher levels is new for me. Can such thing be done just by altering audio_policy.conf and related files or the issue is much more complicated that I expected?
best regards
Jan
I have a android car stereo. The mic is built into the device, so the capture sound is very else.
It supports usb host, so I found a usb microphone and connected it. But the devices Bluetooth HFP always take the inbuilt microphone. Is there a way I can change just the default audio input to the usb mic and output to the inbuilt audio output
Code:
# cat /proc/asound/cards
0 [smdk ]: HDA-Intel - HDA ATI SB
HDA ATI smdk at 0xfe8f4000 irq 16
1 [tera ]: USB-Audio
Guillemot Corporation Dualpix tera at usb-0000:00:12.2-2, high speed
# cat /proc/asound/devices
1: [ 0] : control
2: [ 0- 1]: digital audio playback
3: [ 0- 2]: digital audio capture
4: [ 1- 0]: digital audio capture
5: [ 1] : control
any help?
Send digital audio out of headunit
Dug around a lot and found no listing for this. It might help some folks so I am posting it expecting to get dumped on for not finding the needle in the haystack nearest the moon on Rygel 7. Fire away. Most Android based head units for cars have USB connectors on them. In the world of audio it is best not to convert audio from analogue to digital and back too many times. I like many have an offboard digital based signal processor between my headunit and power amps. I would like to send digital to the processor but most head units don't offer a digital output even as an option and the few that I have found that do source that signal before the volume control in the signal's path so you can't control your listening level with the volume control on your head unit. Apparently Android Kit Kat (4.??) has some driver compatibility with certain audio devices (sound cards?). Android 5 or Lollipop has more. With that do I assume that most USB audio sound cards would be plug and play? What would a head unit developer need to do in order to maintain function of the volume control of the existing head unit assuming it was a droid device of course.
So first off let me start by saying im a total newbie.
i bought a generic android unit off ebay because i won the auction way cheaper than the asking price.
i cant post a link to it because i am new, so here is a copy of the spec sheet:
General:
- ISO 2 DIN Size
- Android 4.2 Operation System
- CPU Processor: Cortex A9 Dual Core MST786
- RAM Space: DDR3 1GB
- Internal Memory: 4G
- 8 Kinds of Dynamic Background Pictures & 16 Kinds of Static Background Pictures Selectable. Customers can also set their favorite pictures as background.
- Default LED Button Color: Blue
- Steering Wheel Control Function
- Menu Languages:
- English/Spanish/French/German/Portuguese/Italian/ Russian/Turkish/Norwegian/Japanese
- Built-In Amplifier FR/FL/RR/RL 4-Channel Subwoofer Audio Output
- 4X45W Surround Stereo
- Effect Compensation: FLAT TECHNO ROCK POP JAZZ CLASSIC OPTIMAL USER
- Built-In LCD Clock Display Function
- Auto-Memory Function
- Power Supply: DC 12V
- Max Working Current: 15A
- Gross Weight: 2.40kg
- Net Weight: 1.85kg
- Install Size:178(length)×150(width)×100(height)mm
- Panel Size: 178 x 100mm
Screen:
- Screen Size: 6.2 Inch High Definition Digital Capacitive Screen
- Resolution: 800*480(WVGA)
- Full Touch Screen Function
- Image Brightness Adjustable
Bluetooth:
- Connect Code: 1234 Name: canplay-0117
- Built-In Microphone in the control panel
- Support Bluetooth MP3 player function (Attention: This function can only be realized when the mobile phone supports Bluetooth Audio Output).
- Support Bluetooth Phone Book Function. You can quickly search for contacts manually, and it supports displaying caller name.
- Support Bluetooth version 2.0 or above phone connection, such as Apple, Samsung, HTC, Sony, etc.
USB/Micro SD:
- Built-In USB Port/Micro SD Slot
- USB Port：Can support soft drive such as USB flash drive, or MP3 player with maximum 32G compatibility. Can’t support portable hard drive.
- Micro SD Card Slot: Can support SDHC Card of maximum 32G compatibility
- Compatible Formats:
- Video Formats: MPG、MPEG、DAT、VOB、TS、TRP、TP、M2TS、MTS、MP4、MOV、RMVB、
- RM 、MKV、DIVX、 AVI、ASF、WMV、FLV、TS、WEBM. 1080P
- Audio Formats: MP3，M4A，WAV，AMR，AWB，AAC，FLAC，MID，MIDI，XMF，
- RTTTL，RTX，OTA，WMA，RA，MKA，M3U，PLS
- Picture Formats: JPEG、JPG、GIF、PNG、BMP、WBMP
DVD:
- Compatible Formats:
- MP3, WMA, MPEG1/2/4, JPEG, DivX, XviD，CD-DA，CD-TEXT，DVD-Video, DVD±R/RW, DVD-ROM, CD-DA, CD-ROM, CD-R, CD-RW
Radio:
- Built-In Radio Tuner (30 Preset Stations)
- FM(3*6)87.5-108MHz(Europe), Increment 0.05MHz
- AM(2*6)522-1620KHz, Increment: 9 KHz
- Built-In RDS Radio Receiver Function
Input & Output:
- 1*Radio Antenna Input
- 1*GPS Antenna Input
- 1*USB Input
- RCA Video Output*2/ CAM IN Video Input*1 /VIDEO IN Video Input*1
- RCA Audio FR/FL/RR/RL/Subwoofer Output AUX Audio R/L Input
Accessories
- 1x English User Manual
- 1x Power Cable
- 1x GPS Antenna
- 1x USB/3G Adapter Cable
- 1x Audio Output Adapter Cable
- 1x Video Input Adapter Cable
- 1x Subwoofer Output Adapter Cable
so... the only clue i have as to the branding (or rebranding) name is on the boot screen. it has a logo that says "CanPlay"
i have done lots of searching and i cant find anything with a name like that.
the problem i was having turned into a larger problem when i tried fixing it.
i couldnt download any apps or anything at all because i got a message saying "unfortunately the process android.process.media has stopped" every time. so after doing a bunch of research, i read a factory reset might cure it. so i went ahead and did a factory reset using the function already on the unit. not only did it not fix the problem, but now none of my physical buttons along the sides work. this includes volume/power knob, and all other external buttons. the touch screen functions fine.
ive read that this tends to happen on other models after a MCU update or change, but i have done nothing but a factory reset.
the MCU version is Lemon_cp_1.18
i have found some solutions for this problem by upgrading the mcu for different systems that seem very similar, but nothing for the CanPlay which has the "cp" mcu.
i have tried contacting the seller, no response so far. hopefully i will hear something soon.
anybody have any ideas?
Any help from you android car stereo gurus would be much appreciated.
so the seller got back to me and told me to try to set the buttons in the factory setings.
a password is required to enter the settings. its not 1234 or 7890. ive tried a bunch of random combos, any ideas? its a 4 digit code.
me too
i am having the exact same problem with the exact same deck. I have been racking my brain for the past 2 days but no luck. Physical buttons worked out of the box but google play gave error 491. I perfomred a factory reset and now none of the buttons work and play still gives same error. Ive read that the factory settings password for the deck is supposed to be 126 but that hasnt worked. Please post here if you figure it out.
Hello just got the same unit installed and also am getting error 491 from google play. Did you ever get yours sorted out ? Also would like to know if anyone got the navigation to work on this ? Thanks for any help.
W4rm4ch1n3 said:
so the seller got back to me and told me to try to set the buttons in the factory setings.
a password is required to enter the settings. its not 1234 or 7890. ive tried a bunch of random combos, any ideas? its a 4 digit code.
Click to expand...
Click to collapse
passworld is 123