[APP] FM Radio for the Droid 2!!

[xzillerationer]

I got the radio working, and I find that I get insanely better reception with the usb plugged in

Sent from my Liberated Droid 2

 

[chamoart]

Hi guys! I've read the full post, try installing the software to use the radio manually, with scrypt posted earlier, but I can not make it work. Is there anything else I can do to help me?

Check the permissions and change them manually with the Rootexplorer. I really can't think of anything else.

Greetings!

 

[enlight22]

installed this on my droid pro and im sad to say it doesnt work, just sits on loading fm radio message. Is it safe to forcibly remove the app and libraries somehow.. how would that be done. it isnt available for uninstall in the applications manager. can i just mount the filesystem as RW and then rm the files? i assume these libraries and application are all stand alone, and nothing was overwritten durring this process?

 

[lrfabreu]

This trik should be used for milestone 2?
Milestone 2 (GSM) = Droid2??
Tks...

 

[WangDino]

Not working for Milestone 2

I confirm also that Milestone 2 will stop at "FM Radio is being launched..." interface.
Fully sure that permissions are correct.

 

[psicodelico]

something is missing...

 

[jason.b]

mine is Droid 2 Global, followed the setup instruction, but still... "is being launched. please wait"... it keeps running.

while another thing is the FMRadioService.apk can't be installed successfully...

please help to take a look....

btw, i got the root permission.

 

[yipyipyip]

Thanks slayher

just to let you know that I've tweaked your FMradio.apk, so it can runs in flight mode (could it be that listening to radio before takeoff can damage airplane electronics ? LOL.).

warning: almost certain that I've added bugs
warning: if slayher package don't work for you, mine won't neither ... it's the same thing

see the thread for the defy:
http://forum.xda-developers.com/showthread.php?p=11859057

yip

 

[hymanhe]

Help ! Help ! Help!

Hei, I dont know the linux cmd, but I used the android software " root explore" to change the tree files in /system/lib's permission to :rw-r--r--(if this means:644 ?) and also change one file in /system/bin's permission to :rwxr-xr-x(if this means:755?), but I still cant solve the problem:FM Radio is being launched, please wait.........

if anynoe can help me.......

 

[danilo2k]

Sorry to bother, but is there a chance this can be adapted to work on an Atrix?

 

[James62370]

Sorry to bother, but is there a chance this can be adapted to work on an Atrix?

+1 that would be awesome if this would work for the Atrix...

 

[cybdroid]

Droid 2 Global Rooted Froyo 2.2 noob here. Just got it a week ago, and of course it's like crack for a hardware engineering geek like me, with all you can do with Android/Linux. The FM Radio caught my attention after I saw another Android phone with it, HTC I think. It is supossed to be possible with the Droid 2 so I gave it a shot.

I tried DarKOnions adb scripted method. The batch fille succesfully copied the 6 files to the sdcard root but adb's shell could not get su permissions so the batch file died at the system mount and copy level of course. I didn't quite know how to sort that out through the USB connection. So...

I loaded a Terminal app and did it the hard way from the instructions in this thread: su at the # command line and linux mount, cp, chmod and such commands carefully typed out and verified for file existence and permissions etc. No errors on the commands.

Like a few people here, the app comes up, and I see the GUI, but it gets stuck at "FM Radio is being launched, please wait..."

I tried everything I could find, and asking for wisdom of the forum please.

 

[Abowersq]

Im using Apex's rom....great one by the way, and it has the FM radio in the rom itself.

Dont know how it was done, but it works.

 

[cybdroid]

Not giving up yet...

FM radio still not working, and I'm a droid noob, so no idea how to use roms.

Grasping at straws and not wanting to give up, I went back into the terminal and looked at the permissions for the 6 files again.

They are supposed to be (from earlier in this thread)

-rw-rw-rw- root root 317886 2010-07-01 19:32 FMRadio.apk
-rw-rw-rw- root root 29286 2010-07-01 19:32 FMRadioService.apk
-rwxr-xr-x root root 20540 2010-07-01 19:32 fmradioserver (ok)
-rw-r--r-- root root 14148 2010-07-01 19:32 libfmradio_jni.so (ok)
-rw-r--r-- root root 45492 2010-07-01 19:32 libfmradioplayer.so (ok)
-rw-r--r-- root root 501712 2010-07-01 19:32 libFMRadio.so (ok)

using ls -l the first 4 files in /lib and /bin matched

-rwxr-xr-x root root 20540 2010-07-01 19:32 fmradioserver
-rw-r--r-- root root 14148 2010-07-01 19:32 libfmradio_jni.so
-rw-r--r-- root root 45492 2010-07-01 19:32 libfmradioplayer.so
-rw-r--r-- root root 501712 2010-07-01 19:32 libFMRadio.so

but in /app I saw this

# ls -l fmradio*

----rwxr-x root root 317886 2011-03-27 10:53 fmradio.apk
----rwxr-x root root 29286 2011-03-27 10:52 fmradioservice.apk

they are supposed to be (according to earlier poster)

-rw-rw-rw- root root 317886 2010-07-01 19:32 FMRadio.apk
-rw-rw-rw- root root 29286 2010-07-01 19:32 FMRadioService.apk


So, I used chmod to make these two from "----rwxr-x" to "-rw-rw-rw-"

#
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cd /system/app
chmod 0666 fmradio.apk
chmod 0666 fmradioService.apk
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
# exit
rebooted D2G

Still no joy. "FM Radio is being launched, please wait..." forever



I have a few questions for the gurus:

- Does case matter in the filenames i.e. "FMRadio.apk" vs "fmradio.apk"

- In the 2 .apk files in /apps, is "----rwxr-x" (what they had default)
or "-rw-rw-rw-"?


I'm posting this because I'm a linux lameoid and I figure there may be a few here also having similar difficulties.

 

[Spitemare]

To help clear up and consolidate information:

Permissions
Permission in *nix, which included Android, work like so. Every file recognizes three boundaries: user, group, others. When doing a long listing of a file (ls -l) the first set of information displays permission. For example

-rwxr-xr-x

The line above should be read in four parts.

• The first dash indicates whether a file is a directory or no. If it's a 'd' then the file is a directory; a dash (-) means it's just a file.
• The next three spots (2, 3, 4) indicate the permissions for the user, i.e. the owner of the file.
• The next three spots (5, 6, 7) indicate the permissions for the group; each file has a group and each user can be part of multiple groups.
• The last three spots (8, 9, 10) indicate the permissions for everyone else; if you're not the file's owner or part of its group these are the permissions you get.

r means you can read the file. w means you can write to the file. x means you can execute the file or move into that directory.

So what's up with the numbers like 644 in the commands listed in other posts? The chmod command changes the permissions of a file; it takes the intended permissions as a group of three octals. Each digit is an octal number that corresponds to a certain mixture of permissions. To decode a chmod argument like 644 let's break it down:

• Each number in 644 corresponds to one of the same three groups above: user, group, others.
• The order is the same as in the long listing: 6 = user, 4 = group, 4 = others.
• To figure out how a single number translates into the three permissions (read, write, execute) you have to look at each permission in binary. This is a little complex so bear with me:
  1. Start with 0.
  2. If execute is on add 1.
  3. If write is on add 2.
  4. If read is on add 4.
  5. Using these rules you will result in some number between 0 and 7 (hence the octal part). A value of 6 can only be created by turning on write and read. A value of 5 would be read and execute.
• If you do this for each digit in the argument you can determine just what permissions the file should have. 644 means the user has read and write, group has read, and others have read. 755 means the user has read, write, and execute; user has read and execute; and others have read and execute.

For FM Radio specifically only bin/fmradioserver should have execute permissions. Write permissions on each file should be given solely to user. Read permissions should be granted to user, group, and others.

It breaks down as thus:
app/FMRadio.apk -rw-r--r-- (chmod 644)
app/FMRadioService.apk -rw-r--r-- (chmod 644)
bin/fmradioserver -rwx-r-x-r-x (chmod 755)
lib/libfmradio_jni.so -rw-r--r-- (chmod 644)
lib/libfmradioplayer.so -rw-r--r-- (chmod 644)
lib/libFMRadio.so -rw-r--r-- (chmod 644)

Capitalization is important. *nix systems are case sensitive when it comes to file names.

Fission ROM
This just won't work on Fission. There's probably some library Fission isn't including that the service expects. Fission does delete a lot of stuff when you install it so I assume something in there is needed.

 

[cybdroid]

Thanks for the lesson Spitemare !

Looks like I have a bit of tidying up to do on permissions per your settings and capitalization from the original files. Maybe that will help. I currently do see the UI for the FM radio and can drag the needle back and forth and save presets, but no sound. Running the OEM Verizon 2.4.330.A956.Verizon.en.US build Android 2.2 on my D2G.

 

[ElectroGeek]

So what is the bottom line? Does this work on D2G and if so, which Roms and how?

Sent from my DROID2 GLOBAL using XDA App

 

[Abowersq]

It does work, albeit only in one ear. Apex rom

Sent from my DROID2 using XDA App

 

[ElectroGeek]

Btw off topic a bit. The spell checker is great but sometimes changes words on me D2G Changes to DOG. Guess I need to update my user dictionary.

Sent from my DROID2 GLOBAL using XDA App

 

[ElectroGeek]

I thought the only rom available to us on D2G was fission.

Sent from my DROID2 GLOBAL using XDA App