• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root MildWild bluetooth problem

skerryman

Lurker
I have Mildwild installed on my desire and am finding it pretty good, except I can't seem to transfer files with bluetooth or connect to the bluetooth on my car stereo (which is a deal breaker for me). The device will pair but won't connect. I googled around and the only thing I found was to go into bluetooth setting with Terminal Emulator and try change the settings from there. The only command that gives me the Bluetooth chip id is /data/misc/bluetoothd/*/ but once I enter that Terminal emulator says permission denied. I have S-Off/ rooted and all that so can't understand why I can't get permissions. Does any one out there know how I can fix this, need bluetooth in my car and like the ROM except for that one thing. Thanks in advance
 
Maybe because that isn't an executable file? If I look in /data/misc/bluetoothd on my phone what I see is a folder whose name looks like a mac address, containing a number of config files. Nothing you can actually run.

Try instead:

ls /data/misc/bluetoothd

since I guess it's the folder name you want.

Or use Root Explorer or ES File Explorer (or any other root capable file manager) to browse /data/misc/bluetoothd
 
Maybe because that isn't an executable file? If I look in /data/misc/bluetoothd on my phone what I see is a folder whose name looks like a mac address, containing a number of config files. Nothing you can actually run.

Try instead:

ls /data/misc/bluetoothd

since I guess it's the folder name you want.

Or use Root Explorer or ES File Explorer (or any other root capable file manager) to browse /data/misc/bluetoothd

Thanks for the reply. I tried "ls /data/misc/bluetoothd and when I press enter I get 38:E7:D8:21:3E:6A which I guess is the chip ID, but I don't get any folder like you described.
 
It isn't obvious that it's a folder. If you do "ls -l" instead you will see a "d" in its attributes, which means it's a directory (linux term for a folder) - I am assuming that this isn't ROM-dependent, but I think that should be a safe assumption.
 
It isn't obvious that it's a folder. If you do "ls -l" instead you will see a "d" in its attributes, which means it's a directory (linux term for a folder) - I am assuming that this isn't ROM-dependent, but I think that should be a safe assumption.

The fix I found says the following
"There I found a directory named by the bluetooth chip's ID, in my case '38:E7:D8:45:21:a4'. I renamed this directory
mv 3* hidden , turned bluetooth off and back on and could use bluetooth again.

Which seems like what I did earlier, just not sure how to rename the directory as I'm not very familiar with the commands or why he used them to be honest. Thanks for your help so far.
 
You can rename with terminal using the "mv" (short for "move") command:

mv filename newname

* is a wildcard character, so it seems here he was saying "rename folder whose name starts with 3 to "hidden"".

Alternatively you can use a root-capable file explorer to rename it.

Make a note of the original name first, of course (which you have here, except that the forum interprets some of the characters as a smiley :)).

Why this should work I don't know though, which is why I say note the original name in case it doesn't help.

Edit: well I say I don't know why it should work, but it's obviously renaming the directory so that the bluetooth daemon can't find whatever is in it. So my guess is that it's a trick to force it to rebuild the directory, but safer than deleting it as you can always rename back if need be.
 
You can rename with terminal using the "mv" (short for "move") command:

mv filename newname

* is a wildcard character, so it seems here he was saying "rename folder whose name starts with 3 to "hidden"".

Alternatively you can use a root-capable file explorer to rename it.

Make a note of the original name first, of course (which you have here, except that the forum interprets some of the characters as a smiley :)).

Why this should work I don't know though, which is why I say note the original name in case it doesn't help.

Edit: well I say I don't know why it should work, but it's obviously renaming the directory so that the bluetooth daemon can't find whatever is in it. So my guess is that it's a trick to force it to rebuild the directory, but safer than deleting it as you can always rename back if need be.

OK I did all that and I get the option as follows:
"Rename SOURCE to DEST, or move SOURCE(s) to DIRECTORY
-fin Don't prompt before overwriting
-i Interactive prompt before overwrite
-n Don't overwrite an existing file"

Any idea how I rename the file from those options, apologies for the spoon feeding, I'm just not that familiar with the commands yet, only rooted at the weekend. Thanks
 
Sounds like a syntax problem - that's listing the options of the mv command.

Remember that it's all case sensitive, and to leave spaces between the command and the 2 filenames. Don't try to type the source folder name completely, just do the 3* thing, because there are special characters in the folder name (":") so it won't work if you just type that all out (you'll need to put \ in front of each : or something tiresome like that. Filenames with spaces are similarly irritating from the linux command line).

If it really plays up, just install ES File Explorer from the market (free) and use that.
 
Oh, and talk of missing the obvious: did you type the command "su" before the "mv" command?

su
mv 3* hidden

"su" is the "superuser" command. Without that you are running the terminal session as an ordinary user, so you probably won't be able to move the file anyway.

Stupid of me not to think of that immediately, since I did it myself before I started poking around on my phone! I think I've just been doing it for too long...
 
Oh, and talk of missing the obvious: did you type the command "su" before the "mv" command?

su
mv 3* hidden

"su" is the "superuser" command. Without that you are running the terminal session as an ordinary user, so you probably won't be able to move the file anyway.

Stupid of me not to think of that immediately, since I did it myself before I started poking around on my phone! I think I've just been doing it for too long...

Had superuser command activated. Gave up on Terminal and tried ES file explorer. Eventually found folder after changing settings to show root files. Deleted the folder and rebooted and its all good, connected and sharing files with laptop and more importantly, connecting to Bluetooth in car. Thanks a bunch for all your help, you sir are a legend !!
 
Back
Top Bottom