yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] daldroid:
I remember that when you launch bts executable (I suppose bts=BlueToothService) the error about no implementation for com.ti.... dsappears. It doesn't complain anymore about not implemented .service.

So I think it dynamically registers the class implementation.

I suppose com.ti stands for Texas Instruments. The error when you stop bts with a ctrl-C or when it crashes (sometimes it siply hangs) refers to a vendor/ti platform source tree (I found no sources in my searches).

Finally, i grepped for string bts in some binaries and libraries: you get matches in some files, some of them had names that could be bluetooth related.

Likely bts implements the BTIPS.

No init.rc starts it as a service and when you toggle bluetooth on/off logcat seems to show btips is called and passend on/off parameter. If you run bts, the could not create BMG error disappears, bluetooth turns on and discovery and pairing works. when you switch off bluetooth in settings menu, it says off, but then you are unable to turn on again without stopping and restarting bts.

That's all I can remeber about my investigation. Hope this helps.

Bye

daldroid

--- edit ---

Forgot to add that later on I verified the size for my working brf6300 I copied from original rom is the same as TIInit_5.3.53.bts. Didn't try binari compare or renaming TIInit_5.3.53.bts to brf6300.bin
[G1 Android Development] shafty023:
I've tried launching /system/bin/bts manually and then turning on bluetooth but it still won't launch. Did you place the brf6300.bin file in /etc/firmware? Or did you place it in /system/lib/modules ?
[G1 Android Development] shafty023:
For anyone still following, here's the progress I've made so far. I noticed /dev/socket/dbus has permissions 661 which is giving an error in the logs when bluetooth tries to launch. Only way to modify this at boot time is by modifying boot.img and adding "chmod 666 /dev/socket/dbus" to init.rc. I haven't compiled the android src yet so I don't have the necessary tools to unpack/pack the boot.img file. Any here have that ability and want to upload a new boot.img file :-D
[G1 Android Development] silby:
Shafty023, I was able to modify the boot.img with the correct permissions and did a fastboot with it. When the phone rebooted, the permissions issue went away, however unfortunately it didn't solve the problem. I think this might be a red herring, or maybe the outer layer of this onion.
[G1 Android Development] shafty023:
Hmmm, well at least we've pushed another hurdle out of the way. Soon as I get a new boot.img loaded and that permissions moved out of the way I'll continue digging into the issue
[G1 Android Development] shafty023:
It looks like at the bottom of init.rc the following is called

service dbus /system/bin/dbus-daemon --system --nofork
socket dbus stream 660 bluetooth bluetooth
user bluetooth
group bluetooth net_bt_admin

This is actually where the incorrect permissions are coming from on /dev/socket/dbus. Because it is setting it to 660 it is giving a permissions error in the logs when the phone is booting up that it does not have access to /dev/socket/dbus. Anyone with the ability to recompile a new boot.img, can you change init.rc to read the following

service dbus /system/bin/dbus-daemon --system --nofork
socket dbus stream 666 bluetooth bluetooth
user bluetooth
group bluetooth net_bt_admin

**EDIT**

Could you also change the following in init.rc

service hcid /system/bin/hcid -s -n -f /etc/bluez/hcid.conf
socket bluetooth stream 660 bluetooth bluetooth
socket dbus_bluetooth stream 660 bluetooth bluetooth
# init.rc does not yet support applying capabilities, so run as root and
# let hcid drop uid to bluetooth with the right linux capabilities
group bluetooth net_bt_admin misc
disabled

To

service hcid /system/bin/hcid -s -n -f /etc/bluez/hcid.conf
socket bluetooth stream 666 bluetooth bluetooth
socket dbus_bluetooth stream 666 bluetooth bluetooth
# init.rc does not yet support applying capabilities, so run as root and
# let hcid drop uid to bluetooth with the right linux capabilities
group bluetooth net_bt_admin misc
disabled
[G1 Android Development] rigamrts:
i've been following you guys on this and have had a thought about this. what if the rom that haykuro had never had a working bluetooth stack built into it at all. since all the other parts of the rom have been tweaked it would come to the conclution that bluetooth would be tweaked too. since this is an alpha the bluetooth stack might not even be complete in this build since they might have been working on getting other parts of the build working first. it might just be thrown in there to keep the phone from crashing kinda like a placeholder till they add the real bluetooth stack in. kinda like if the build ever got into the wild the only thing we'd have is a working rosie apk with no way to get bluetooth working till the real deal was released. it's the best way to protect property from being stolen or get into the hands of the competitors. since rosie would be easily indentifiable if another competitor tried to use it rosie not that big of a hit. the bluetooth parts are there just not the real ones to get it to work.

they also could be using a whole new radio not even related to the one provided for cupcake.
[G1 Android Development] shafty023:
These builds are built off the source code for Android 1.5 which has a functional bluetooth stack. The only part that gets tweaked from the manufacturers is the bluetooth module which is loaded into the kernel. That module all depends on which chipset the mfg uses in their phone. Of course, the HTC Hero uses a Texas Instruments chip while ours (G1) uses something else. Even though the module in /etc/firmware/ is named TII..... can't remember the name, it has the exact same md5sum as the one on the G1 phone brf6300.bin which means all they did was rename the module. I strongly feel HTC didn't explicitly go in and break the bluetooth libraries as they're all still present in /system/lib. The Android framework in /system/framework is still there along with some HTC jar files so I think they were extending the framework and not re-writing it.
[G1 Android Development] shafty023:
FYI, I'm finally building the Android 1.5 source code so that I can create my own boot.img files and continue working on the bluetooth issues. Currently I've been waiting for justanothercrowd to compile them for me based on changes I ask him to make. I'll keep everyone updated as I continue work. As always, everyone chime in with ideas and debugging of their own. 2 minds are better than one.
[G1 Android Development] silby:
Shafty,

As I said previously, I did build the boot file with the correct changes to init.rc and it did get beyond the permissions issue, however BT continued to fail :( . I can provide the boot.img to you if you would like to further debug past that point. Unfortunately, it appears that there are many issues.

FYI, I checked many other builds and the permissions are set to 660. However that doesn't mean too much as DBUS could be used in a different way in this build.

I am painstakingly stepping through the code now to see where it is failing. Hopefully it will turn up something. I will report if/when it does.
[G1 Android Development] shafty023:
Hmmm I wonder how yours is working and mine isn't. I have a boot.img with the "chmod" command in there but it's not fixing the permissions as the permissions are set under the "service dbus" line in init.rc. So if we don't change that part then putting "chmod 666 /dev/socket/dbus" will do no good.
[G1 Android Development] silby:
I just changed the init.rc file directly.

So, it appears that JacHero 1.6 is available that has already made these changes, amongst others. I think I am going to upgrade to his and use that as a baseline.
[G1 Android Development] shafty023:
Ya I was messaging him with my progress so he could incorporate it into his ROM. I've now got the ability to create/edit my own boot.img files so it should help move progress along. I made the changes to the services permissions and I now have all bluetooth related errors fixed in the logs.

Now when bluetooth is launched it brings up the following error

E/sky ( 358): turn on/off BT from UI

D/BluetoothDeviceService( 78): Bluetooth state 0 -> 1

V/BluetoothDeviceService.cpp( 78): enableNative

V/BluetoothDeviceService.cpp( 78): Starting btips daemon--BtStartBts()

V/bluetooth_common.cpp( 78): Current bts daemon state: BTS_DISABLED

I/bluetooth_common.cpp( 78): BT Start btips daemon

V/BluetoothEventRedirector( 358): Received android.bluetooth.intent.action.BLUETOOTH_STATE_CHANGED

I/bluetooth_common.cpp( 78): Current bts daemon state: BTS_BT_ENABLED

I/bluetooth_common.cpp( 78): com.ti.btips, /com/ti/btips, com.ti.btips.bmg, Create

E/bluetooth_common.cpp( 78): dbus_func_args_timeout_valist: D-Bus error in Create: org.freedesktop.DBus.Error.ServiceUnknown (The name com.ti.btips was not provided by any .service files)

V/BluetoothDeviceService.cpp( 78): Error BMG Create!
[G1 Android Development] justanothercrowd:
I am going to put the seconds changes for good measure in my boot.img

just haven't had time to make one up for ya
[G1 Android Development] shafty023:
Looks like we need to track down where in /system/framework it is calling the TI chipset for bluetooth and change it back to brf6300. Unfortunately unpacking the .jar files in there only results in have DEX optimized files which are cryptic and unable to be modified easily. Anyone else have luck decompressing them?
[G1 Android Development] UnkzDomain:
I talked to haykuro and he told me that we need to edit the init.rc in the ramdisk (in the boot.img) to start the btips service at startup. Unfortunately, I know enough to be able to extract the ramdisk and the like, but I dont know how to edit the init.rc so it starts a service...

EDIT: I think i got the basics down for starting a service from init.rc, but I cant even find the location of this "btips" service that Haykuro told me about... The closest I got was /system/bin/bts and that was when I did a "find / -name bt*"
[G1 Android Development] jaygajay:
i know how to unpack and repack boot.img and edit init.rc. Just need to know where to start the service from
[G1 Android Development] daldroid:
As I told in my previous post, on sapphire running bts solves the problem of activating bluetooth, but sometimes the process crashes or stops reacting to the requests. I still had no time to reflash hero rom, I'll let you know.
[G1 Android Development] UnkzDomain:
OK, well haykuro told me that we need to edit the init.rc and start /system/bin/bts AS the btips service.. Also, he told me that all that you need in order to get bluetooth functioning in Hero is already included in Hero. You dont need to go copying files from other builds if you configure it correctly in hero... He's busy right now tho so idk if he'll tell me anything else today..
[G1 Android Development] jaygajay:
well i modified init.rc in boot.img with

service btips /system/bin/bts

socket btips stream 660 bluetooth bluetooth

user bluetooth

group bluetooth net_bt_admin

I flashed it back to the phone and booted up and tried starting blueooth. Bluetooth didnt come on but there was changes in logcat.

I can't changed any of the settings yet as they are still grayed out.
[G1 Android Development] Dladu:
Would changing the 660 to 666 do anything? Seen this on other posts don't know if with your new findings that would help any but its worth a try.

Maybe try: http://xdaforums.com/showpost.php?p=3935269&postcount=44

*shrug*
[G1 Android Development] jaygajay:
It doesn't seem to change anything,
[G1 Android Development] daldroid:
Hi all, the following seems to work on sapphire.

I only had time to try running it as root and with the socket definition.

Not enough time to fully test, but try this if you like

Bye

daldroid

--------------------------------------------------

service btips /system/bin/bts

socket btips stream 660 bluetooth bluetooth

group bluetooth net_bt_admin misc

# disabled
[G1 Android Development] jaygajay:
Tried this in init.rc but still ends up as ....BTIPS ignored plus an abort is called. Need help on that one.

I/bluetooth_common.cpp( 70): Current bts daemon state: BTS_BT_ENABLED
I/bluetooth_common.cpp( 70): com.ti.btips, /com/ti/btips, com.ti.btips.bmg, Create
V/BluetoothDeviceService.cpp( 70): Sucess BMG Create!
I/bluetooth_common.cpp( 70): com.ti.btips, /com/ti/btips, com.ti.btips.ag, Create
I/bluetooth_common.cpp( 70): com.ti.btips, /com/ti/btips, com.ti.btips.ag, Enable
I/bluetooth_common.cpp( 70): com.ti.btips, /com/ti/btips, com.ti.btips.a2dp, Create
I/bluetooth_common.cpp( 70): com.ti.btips, /com/ti/btips, com.ti.btips.a2dp, Enable
I/bluetooth_common.cpp( 70): com.ti.btips, /com/ti/btips, com.ti.btips.avrcp, Create
I/bluetooth_common.cpp( 70): com.ti.btips, /com/ti/btips, com.ti.btips.avrcp, Enable
I/ActivityManager( 70): Displayed activity com.android.settings/.bluetooth.BluetoothSettings: 858 ms
I/bluetooth_common.cpp( 70): com.ti.btips, /com/ti/btips, com.ti.btips.common, RadioOn
V/BluetoothEventLoop.cpp( 70): setUpEventLoopNative
V/BluetoothEventLoop.cpp( 70): ... BTIPS ignored
D/libc-abort( 35): abort() called in pid 35
V/BluetoothEventLoop.cpp( 70): ... BTIPS ignored
V/BluetoothEventLoop.cpp( 70): ... BTIPS ignored
V/BluetoothEventLoop.cpp( 70): ... BTIPS ignored
V/BluetoothEventLoop.cpp( 70): ... BTIPS ignored
[G1 Android Development] daldroid:
My sapphire gives the same BTIPS ignore (only once or twice), but if you try toggling bluetooth and discovering, it works.

Didn't test with a bluetooth headset anyway. I have brf6300 in /etc/firmware and rebuilt the odex files with dexopt.
[G1 Android Development] shafty023:
Strangely brf6300.bin is the exact same file as the TIInit file that is in /etc/firmware. They have the same md5sum. Looks like they just changed the name on it.

I have done the following to give everyone an update and so far bluetooth is not working in Hero

In /init.rc

CHANGE
socket bluetooth stream 660 bluetooth bluetooth
TO
socket bluetooth stream 666 bluetooth bluetooth

CHANGE
socket dbus_bluetooth stream 660 bluetooth bluetooth
TO
socket dbus_bluetooth stream 666 bluetooth bluetooth

CHANGE
socket dbus stream 660 bluetooth bluetooth
TO
socket dbus stream 666 bluetooth bluetooth

ADD
service btips /system/bin/bts
socket btips stream 666 bluetooth bluetooth
user bluetooth
group bluetooth net_bt_admin misc
# disabled

Turning on bluetooth will show everything is enabled but will yield BTIPS ignored messages.

The following services are started now which weren't before these mods.

bluetooth 47 1 1188 352 c00bb774 afe0d25c S /system/bin/dbus-daemon

bluetooth 473 1 5720 868 ffffffff afe0d25c S /system/bin/bts
[G1 Android Development] wizern23:
so does it work?
[G1 Android Development] shafty023:
Nope, still won't bring up the device hardware. I'm still working on it. I did just get LED working in Hero. You can check out the post here http://xdaforums.com/showthread.php?t=526614
[G1 Android Development] lmfwtw:
how about renaming TIInit file that is in /etc/firmware to brf6300, did you try that?
[G1 Android Development] shafty023:
Yup that was one of the first things I tried but it didn't yield any results. I did "cat /system/bin/bts | strings | grep -i tii" and notice that it is referencing the TII chipset and not the brf6300. Therefore there's no point in changing the name to brf6300.bin IMO.
[G1 Android Development] daldroid:
Sorry, but I told you it's working for me AS ROOT. in my post I didn't include the line

user bluetooth

also you can omit # disabled, it's just a comment.

Try again, I hope you'll succeed.

Bye

daldroid
[G1 Android Development] shafty023:
ya I added the "user bluetooth" line as I noticed you were missing it. I'm getting close to getting it working. There isn't a direct relation between Hero & Sapphire in terms of hardware but that btips line you gave me will DEFINITELY be needed. Thanks again
[G1 Android Development] Kinslayer81:
Yeah, he's saying DON'T ADD the line so the process will run as root. Does it work without this line?
[G1 Android Development] shafty023:
Ya I removed the line after I realized that the process needed root privs in order to write to /sys/class/rfkill/rfkill0/state
[G1 Android Development] MortICi:
Does this have anything to do with our issue:

# btips DDB location
mkdir /data/btips 0770 bluetooth bluetooth
mkdir /data/btips/TI 0770 bluetooth bluetooth
symlink /data/local /data/drm
mkdir /data/local/rights 0777 shell shell
chown shell shell /data/drm

Its in init.rc
[G1 Android Development] MortICi:
see my bolded change, i think if you add that line the user bluetooth should be fine.

Im gonna compile and test this boot.img in a minute.
[G1 Android Development] vettejock99:
Looks like shafty has that in his config now.....looking at another error here:

http://xdaforums.com/showthread.php?t=527027
[G1 Android Development] MortICi:
My boot.img didn't seem to work, either i compiled incorrectly or i did something wrong cause it just hangs after the g1 screen. Doesn't dump into recovery.
[G1 Android Development] jerpelea:
in my rom

bluetooth works

paires

but audio is lost after 2 seconds(i got 2 seconds of phone audio after that is silence)

br
[G1 Android Development] MortICi:
This is on a HERO rom? Can you tell us some more info?
[G1 Android Development] shafty023:
He's probably using the htc magic with hero rom, not the g1 with hero rom. different devices, BT chipsets.
[G1 Android Development] jerpelea:
vodafone magic

but i am trying to get bt to work

br
[Touch Pro CDMA] jrodizzkool01:
*Let me start off by saying that i searched both xda devs and ppc geeks for answers to these questions and still havent found anything that solves my problems. I usually am able to find answers to my questions and thats why this is my first thread:D*

I flashed my Alltel touch pro to a 6.5 rom (http://xdaforums.com/showthread.php?t=509544) and I have a few questions about the scrolling feature in wm6.5. These questions pertain to all 6.5 roms and not specifically the one that i have on my phone now.

1) When i want to use a kinetic "finger scrolling" method in contacts (and most other applications like file explorer), i realized that i have to hold my finger down on the screen for about a second then i can scroll kinetically. If i dont hold my finger before i scroll, the whole list scrolls just like how it did in wm6.1 contacts. Is there a way i can keep the kinetic scrolling without having to hold my finger down for a second?

2) In 6.5 the start menu, the kinetic scrolling works well but after flicking up or down, it seems like i am only scrolling page by page. No matter how fast i flick up or down, i can never get to the bottom of the list and just wind up going a page down. Is there a way to get continuous scrolling?

3) When i scroll down the home page to favorites, there is a link to internet explorer. I prefer the Opera browser and was wondering if there was a way for me to either change it to Opera or be able to flick to the left or right and be able to start up Opera.
[Touch Pro CDMA] jrodizzkool01:
ANY HELP?!?!

ANY HELP?!?!?
[Touch Pro CDMA] FAST5:
I had this same problem.

Do a hard reset, take the battery out, put the battery back in, then do another hard reset, then take the stylus out, then put the stylus back in, then do a hard reset, then push the D-pad button 17 times, then do a hard reset, then you should be good to go.
[Touch Pro CDMA] jrodizzkool01:
Im not looking for some stupid joke, I want a solution to my problem. Ive already tweaked with the registry and cant seem to change the scrolling to my liking. Are there any HELPFUL people out there who could answer my question?
[Touch Pro CDMA] mickeyx323:
I honestly think it has to do with your rom. I am using 6.5 and i can flick up and down with ease. You can try a hard reset and see if that helps and if not just try another rom. NFSFAN has a nice rom, but the scrolling freezes for about 3-5 sec after a while. The current rom i am using (Energy Rom from ppcgeeks) works fine but there is a time issue with it. It goes back an hour by itself, but there is a fix for it. Or you could try dodge longhorn's rom. Both are pretty stable. If you flash and need a fix for the time issue just pm. Hope this helps.
[Touch Pro CDMA] MOBGangsta184:
Just Flash Mighty Rom 6 and you'll be good, scrolling works perfectly.
[Touch Pro CDMA] jrodizzkool01:
yeah youre right it has been just that rom. Ive tried others and they dont have the scrolling problem but i wish there was a way to fix it. ive tried energy rom and it looks nice but has been slow for me:(
[Touch Pro CDMA] mickeyx323:
Like MOBGansta 184 said mighty rom 6 is really stable and fast. The only thing is that it doesnt have TF3D2. So if you dont mind having TF3D, then thats prob the best rom out there.
[Touch Pro CDMA] Tipharet:
I found this quite entertaining and he had me until the stylus part.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kickindrummerkid:
I upgraded the OS on my rom (I took a rom from the Jade forums and extracted xip and imgfs, a new 21728 OS) following http://www.bepe80.com/test/2/. It built everything ok and I followed the directions exactly. Except the only problem is when I flash it to my phone, the first screen comes up with the red text at the bottom, the console eMo text with the version and radio numbers, and then it freezes there and won't continue to boot. I can reflash via SDCard so I'm not worried about my phone. I just want to fix my ROM and upgrade it successfully. What did I do wrong? I need to get my rom to work. Please help? Any suggestions?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DaveShaw:
You can re-flash using the bootloader mode and USB or using SD Card, don't worry I think all chef's have created a non booting ROM. It's probably just a bad XIP port.

Ta

Dave
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kickindrummerkid:
thanks for you help. did you read my post completely? Flashing isn't the problem. "I can reflash via SDCard so I'm not worried about my phone". But thanks for your help, I just need to know why the port was bad because I followed the tutorial exactly. Any suggestions? Is the video correct with porting xip? Or do you have to do something different for kaiser?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DaveShaw:
Try porting the XIP again. I'm not an expert on it. But Usually with cooking it's trial and error, try not to do everything at once. Do a step, cook a ROM, test it, try the next step and so on.

Good luck,

Dave
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] twopumpchump:
what part of new xip did you put in new rom? the only part of new os xip that you use is shared xip(msxipkernel), the rest is from your original kaiser rom.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ai6908:
I am trying to figure out the same thing as well! If did find out why, just let us know in here...:D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ai6908:
I think I fixed that problem by changing SYS!
[Touch Cruise Accessories] 1nsan3:
I have been checking some online-shops (inc. ebay) in the search of the keypad(plastic thingie, without circuits) with a wheel but with no luck - they are not sold separately from housing, nor many housings are sold without them.

Can anyone give me a clue if I can find that piece somewhere?:confused:
[Touch Cruise Accessories] wagner51:
It seems there is a thin metalic layer. This one is very fragile: on my phone, this layer begins to peel off. Does anyone know how to change it?
[Touch Cruise Accessories] Nicolais86:
that same **** happens to me, but no that serious, only the little "line" that its in the red and green icons. I guess that your using your fingernails, right?
[Touch Cruise Accessories] wagner51:
Nope. But when cleaning my screen, I put a little bit of water on it, then rub it with a tissue. I think the tissue gets caught on the small holes and tear off the metallic layer... One of my colleague has the same problem.

Once it has begun, you cannot stop the layer unsticking.
[Touch Cruise Accessories] mmojc:
Uh! need!!

Yes I me too..

please help... broken idem.-