yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Development and Hacking General] fb_oo:
I did try this app. However, I found out some of my friends could not receive sms messages thru this app... so then I gave it up (uninstalled). Actually, you can use the registry editor to edit the string value and have the same feature but without any addition app.

I am using WM 6.5
[Windows Mobile Development and Hacking General] fsjon:
Mind sharing which string value you changed?? Thanks!
[Windows Mobile Development and Hacking General] whoispetty:
Any progress on this??
[Windows Mobile Development and Hacking General] vallick:
Does anybody knows if it is possible to use the Win Mo 6.5 Icons on the 6.1? And where could I get it in a cab or something like that? :confused:
[Touch Pro, Fuze General] hertel04:
Hey guys,

I have picked up on some pretty tough(to me) things from this forum, yet I can't figure out what seems to be an easy thing.

How do I put my own personal Text at the top of the Today/Home Page?

It goes right next to the Date, I believe.

Such as a nickname, phrase, etc.
[Touch Pro, Fuze General] AkumaMax:
Instead of having lie AT&T there. I use Personalizer works great. Can be buggy with some Roms so be careful.
[G1 Android Development] silby:
I have been trying to stretch my abilities and see if I can figure out what is wrong with bluetooth in the latest Hero builds. I have come to a point where I "think" I know what is up, however I haven't a clue how to fix it.

Normal case

1) Bluetooth uses the DBUS to communicate with other processes.

2) DBUS uses a system socket called /dev/socket/dbus.

3) the dbus socket is created by the init.rc file with the following commands:

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

4) after the dbus -daemon is started HCI is started. All of these processes are used for bluetooth communication.

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 group bluetooth net_bt_admin misc disabled​

What I am seeing:

1) the sockets are never created for HCI (bluetooth and dbus_bluetooth) because dbus-daemon is never started.

2) dbus-daemon is never started because upon initialization it is getting a "permissions error"

06-01 17:29:01.614: ERROR/android_bluetooth_AG.cpp(112): Could not get onto the system bus: Failed to connect to socket /dev/socket/dbus: Permission denied​

3) when I look at the socket it has 660 permissions (as set above in init.rc). I venture to guess that this could be fixed by simply changing the permissions to 666, however I don't have any idea on how to update the init.rc file to test my theory.

Any thoughts? Am I way off base
[G1 Android Development] johnsonnc:
re

With out modifying the main init.rc, i changed the permission of the socket (as root). D-Bus was already running, btw. I then manually launched the:

# /system/bin/hcid -s -n -f /etc/bluez/hcid.conf socket bluetooth stream 660 bluetooth bluetooth socket dbus_bluetooth stream 660 bluetooth bluetooth group bluetooth net_bt_admin misc disabled

Which launched just fine the first time.

Except now, when I try to enable it logcat is showing this error:

E/bluetooth_common.cpp( 63): 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)

So what is the new provider?
[G1 Android Development] silby:
How did you check that dbus was already running? If I do a PS on it, it does not show up for me.
[G1 Android Development] knaries2000:
to update the init.rc, you have to unpack the boot.img in the room, and repack it.. there was a thread explaining now to do that.

http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
[G1 Android Development] johnsonnc:
It was running.
[G1 Android Development] vettejock99:
Can someone explain the dev challenge to get bluetooth in Hero?

So there was a thread about getting BT working and while I thought it would stay active it has dropped from "above the fold". Someone was speculating DBUS daemon was starting, but HCI wasn't. Is anyone making any progress? Is this a limitation of the current SDK and if so, why? Where would I start looking? I presume we can solve this if as has been speculated HTC is releasing a Hero phone for AT&T in less than 3 weeks.
[G1 Android Development] xyrcncp:
http://xdaforums.com/showthread.php?t=521500&highlight=hero+bluetooth

Yes, it's dropped from the front page, but not necessarily out of reach.
[G1 Android Development] johnsonnc:
From what I can have gathered and haven't been able to work on since is that HCI and DBUS can both be started with the proper permissions (the init.rc script still needs to be modified, which requires unpacking and repacking the image I looked at the procedure but haven't attempted it yet). I manaually started them on mine.

However, once started the UI can't control or read settings because there is service provider doesn't exist/registered.

E/bluetooth_common.cpp( 63): 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)

The "com.ti.btips" (Texas Instruments?) doesn't exist and/or wasn't registered by the system. That's where I am lost. I am assuming that there is an APK missing (maybe HTC didn't have it in the ROM yet) that provides the service. On that assumption i would look for "com.ti.btips.apk".

OR

The may have changed chipsets for bluetooth in Hero, which means while the kernel can interface with it, they have customized DBUS to read in some different settings or interfaces for the chipset. Again shouldn't be -too- difficult to pull those mods out of the other roms and copy them so long as the versions of dbus match and the modification match what the kernel is capable of.

Needless to say I haven't had the time to dive completely into it.
[G1 Android Development] johnsonnc:
Keeping things together

From what I can have gathered and haven't been able to work on since is that HCI and DBUS can both be started with the proper permissions (the init.rc script still needs to be modified, which requires unpacking and repacking the image I looked at the procedure but haven't attempted it yet). I manaually started them on mine.

However, once started the UI can't control or read settings because there is service provider doesn't exist/registered.

E/bluetooth_common.cpp( 63): 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)

The "com.ti.btips" (Texas Instruments?) doesn't exist and/or wasn't registered by the system. That's where I am lost. I am assuming that there is an APK missing (maybe HTC didn't have it in the ROM yet) that provides the service. On that assumption i would look for "com.ti.btips.apk".

OR

The may have changed chipsets for bluetooth in Hero, which means while the kernel can interface with it, they have customized DBUS to read in some different settings or interfaces for the chipset. Again shouldn't be -too- difficult to pull those mods out of the other roms and copy them so long as the versions of dbus match and the modification match what the kernel is capable of.

Needless to say I haven't had the time to dive completely into it.

edit: reposted here to keep things together
[G1 Android Development] vettejock99:
This sounds like reasonable thinking. Today stinks for me but I will try to audit the files from my other 1.5 ROMs this weekend to see if I can find anything there to contribute.
[G1 Android Development] buttkicker:
I don't know if anyone else noticed.

Haykuro's Hero build has 2 liba2dp.so files.

One of them is capitalized.

/system/lib/liba2dp.so (53.1 KB, same as other builds)

/system/lib/libA2DP.so (9.1 KB, smaller)

I believe the update might be overwriting the first file with the second while applying the update.

I am not running hero right now.

If anyone running hero can check the lib folder on the phone and see which file is there, it will be of great help.

On terminal:
ls -l /system/lib/lib*2*.so

From adb:
adb shell ls -l /system/lib/lib*2*.so

If the lib on the phone is the smaller one, can anyone push the bigger file and report the result.

If this works, all we have to do is remove the second file from the hero update.
[G1 Android Development] Dladu:
It's running the larger liba2dp.so

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Admin>adb shell ls -l /system/lib/lib*2*.so
-rw-r--r-- root root 130600 2008-08-01 08:00 libOmxH264Dec.so
-rw-r--r-- root root 54412 2008-08-01 08:00 liba2dp.so
-rw-r--r-- root root 79240 2008-08-01 08:00 libon2.so
-rw-r--r-- root root 9476 2008-08-01 08:00 libxml2wbxml.so

C:\Documents and Settings\Admin>
[G1 Android Development] vettejock99:
Is it posts like that which get one to 381 posts since Feb of 09? Feel free to actually contribute to this discussion about the problem at hand. Although this discussion is much like that one, this one was made to identify whether there is something lacking altogether that would prevent debugging until additional code is dropped.
[G1 Android Development] silby:
vettejock99,

Can you explain your point? The other post is much more relevant as it talks about the technical issues. Also, it only has 7 posts in it, not 309.

This thread should be closed and all communication should go in the other one.
[G1 Android Development] vettejock99:
I don't need to explain my point. It is quite evident. Maybe the subject of the other should be edited to something like trying to solve the bluetooth issue in Hero. Or maybe not - maybe I just believe in accurately stating the problem. My point is you can't debug it (at least not fully) if some of the code flat out isn't there yet (which I do not believe to be the case but wanted to confirm). Anyway, I do support closing\merging this thread as I have my answer now.
[G1 Android Development] Kinslayer81:
The liba2dp.so on other builds with working bluetooth is also 54412 bytes, so I don't think this is our problem.
[G1 Android Development] Jrbourque:
I wonder what would happen if we deleted the second one thats there
[G1 Android Development] silby:
I also found that /system/etc/firmware has a different TI driver there than other builds. Most builds have brf6300.bin. I tried replacing what was there with the brf one and it didn't make a difference. I suspect there is a confi file that might be pointing to the other firmware.
[G1 Android Development] shafty023:
# ls -l lib*2*.so

-rw-r--r-- root root 9336 2008-08-01 07:00 libA2DP.so

-rw-r--r-- root root 130600 2008-08-01 07:00 libOmxH264Dec.so

-rw-r--r-- root root 54412 2008-08-01 07:00 liba2dp.so

-rw-r--r-- root root 79240 2008-08-01 07:00 libon2.so

-rw-r--r-- root root 9476 2008-08-01 07:00 libxml2wbxml.so
[G1 Android Development] shafty023:
This type of post is counter-productive. There should be no room for it and you should think twice before you post something so rude. We're all here trying to help each other out and figure out how to fix issues with the Hero rom.
[G1 Android Development] silby:
Sorry, I have to respond to you, as you are pulling the same exact thing. What does your post accomplish?

I responded originally as vettejock99 made some incorrect statements about the validity of this post. He claimed there were 309 post since February and that it was off topic. If you are going to bash somebodies post, especially when they are working hard to fix a problem that everybody has, make sure you have valid points. I am not sure how you find my post rude, and yours and his not.

I have to laugh. I am new to this community and thought I would try and help everybody out by starting an investigation into BT. It is hard to be motivated when there are folks that just want to pick apart what everybody says.

Stick to the topic of debugging BT, and perhaps we will all benefit.
[G1 Android Development] vettejock99:
Sorry you have to respond? First, debugging has 3 G's in it. Second, I made no incorrect statements. My observation was about a worthless post (just like the additional 3 now that you've chosen to take exception) where the poster (who had 309 posts in 3 months) added no value except to point to a thread I'd already referenced. I've' already stated a couple of actions I was willing to take to help everyone with this so if you, silby, would stay on post or at least try harder to comprehend then we could get back to business. I hate posting stuff like this because ultimately we all lose, but it is holier than thou people like you that start this stuff to begin with. I've been on here for 3 years, and I took over a year before I posted. Maybe more people should consider doing the same. Shafty has been here for a couple - seems like the old school members know how this whole forum things works just fine.

To the others......okay, so we've narrowed down the radio file swap and the lib files as not helping, anyone come up with a config referencing the radio drivers?
[G1 Android Development] johnsonnc:
My suggestion is to check the DBUS config. I don't have hero installed (I was having radio issues and had to swap mine back out for a new one, waiting for other to settle the Rosie issues before I dive back in.), however I will try and dump the ROM and see my self at the DBUS config.

The only other thing is to unpack the SettingsProvider.apk and see where it is making calls to and check if it exists (what it's calling to) or if that config is right.
[G1 Android Development] johnsonnc:
Ok scratch the DBUS config. Nothing it in relavent.
[G1 Android Development] silby:
vettejock99 - Thanks for clarifying. That was what I was after (which post you were referring to). I thought you were referring to the bluetooth post having 309 messages.... Nuf said on this subject.

To all - I have tried the following routes - none seemed to be too helpful.

1) Changed the permissions of the DBUS socket to 666 in boot.img and reflashed. The permissions error went away on boot, however it didn't seem to affect anything.

2) I copied the old brf6300.bin file back to the /system/etc/firmware directory - didn't help too much either. I assume there are other pointers elsewhere that need to be changed to this module.
[G1 Android Development] johnsonnc:
My thoughts is DBUS is just fine.

The firmware is probably going to be nesscary in the end.

Where i think the problem is with the data/apps/SettingsProvider.apk and/or system/framework/services.jar

Remember the -

E/bluetooth_common.cpp( 63): 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)

Error

"provided by any .service files" implies the services.jar file (since it was compiled jar it can reference a c++ file [bluetooth_common.cpp])

This makes me think that there is a file missing from the ROM that HTC hadn't added yet.

However, if we can edit bluetooth_common.cpp or services.jar to point to the right file (com.ti.btips eqiv in the other roms??) it would at least get the UI to respond, wiether or not it truely turns on the chip, i dunno.

Is there way to test it and see it we at least can get the chip into a passive or dump mode so we can see if the kernel/dbus is truly working, just to be sure?
[G1 Android Development] vettejock99:
Yup, the info that the two of you have supplied seems to suggest a specific firmware file is missing. This would also align with a statement Haykuro made when he made his release, that it wasn't here. If we can narrow down the file, I wonder if one of these guys can compile a kernel for us which would address it.

--EDIT--

just to help anyone that hasn't collected this info yet - the G1 has the TI BRF6300 bluetooth chipset (consistent with the .bin file silby referenced above). There is some pretty good info in the following link about how this interfaces with the software:

Link
[G1 Android Development] halfwaytothepole:
When you dropped brf3000.bin into the /system/etc/firmware directory, did you rename it? I'm curious to see what results we'd get by renaming it from brf3000.bin to TIInit_5.3.53.bin. I'm at work, or I'd try it myself. If no one has done so by the time I get home tonight, I'll do so and report back.
[G1 Android Development] johnsonnc:
While it's a good start I don't think that will be solution.

I seem to remember that it does register in the kernel ( from ADB shell to 'dmesg' ). And if I remember my kernel compiling correctly, I think the .bin is actually pulled into the kernel on compilation. It's provided separately because of license issues with the GPL. Which is a round about way of saying if we swap out the file it's actually going to take a recompile to see any changes.

None the less, I could be wrong, so it's worth a shot. Just be careful too, if you do swap that out, if I am wrong and the kernel does look at that file directly, it may be looking for specific entry points and bit length, soooo it mayyy panic if you change the file. Eg, backup in order ;)

I still want to investigate that services.jar and (be how I don't have loaded a custom firmware since my new one *cough*) can someone see if there is an APK that is something like com.ti.whatever, that might be worth swapping out if the .bin file doesn't pan out.

just for organization -

* Swap out firmware file (.bin)

* Find decompiled services.jar (look for file pointers)

* TI .apk file??

We will get this licked in no time ;)
[G1 Android Development] daldroid:
Hi all,

I'm trying to fix a bluetooth problem on sapphire.

May I suggest you to try executing /system/bin/bts from a shell then try to use bluetooth?

It's a quick and dirty workaround, sorry, but it works in my case.

/platform/vendor/ti git seems to be changed with the hero build

I've no time to investigate further right now, I hope this will be of help.

Please, let me know if you find a clean way to resolve the bluetoooth problem or if it was already resolved (searched a lot, but didn't find)

Bye

daldroid

-----edit----

I forgot to say that sometimes bluetooth stops to work. "bts" process either hangs-up or terminates.
[G1 Android Development] shafty023:
Tried this and it didn't help, doh!

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

V/BluetoothDeviceService.cpp( 79): enableNative

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

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

V/BluetoothDeviceService.cpp( 79): Sucess BMG Create!

V/BluetoothEventLoop.cpp( 79): setUpEventLoopNative

V/BluetoothEventLoop.cpp( 79): ... BTIPS ignored

V/BluetoothEventLoop.cpp( 79): ... BTIPS ignored

V/BluetoothEventLoop.cpp( 79): ... BTIPS ignored

V/BluetoothEventLoop.cpp( 79): ... BTIPS ignored

V/BluetoothEventLoop.cpp( 79): ... BTIPS ignored

V/BluetoothEventLoop.cpp( 79): ... BTIPS ignored

V/BluetoothEventLoop.cpp( 79): ... BTIPS ignored

V/BluetoothEventLoop.cpp( 79): ... BTIPS ignored

V/BluetoothEventLoop.cpp( 79): ... BTIPS ignored

E/BluetoothDeviceService( 79): can't ON BT because current state is 1

V/LocalBluetoothManager( 619): setBluetoothEnabled call, manager didn't return success for enabled: true

I/ActivityManager( 79): Starting activity: Intent { action=android.intent.action.MAIN comp={com.android.settings/com.android.settings.bluetooth.BluetoothSettings} }

I/ActivityManager( 79): Displayed activity com.android.settings/.bluetooth.BluetoothSettings: 689 ms

W/BluetoothDeviceService( 79): isDiscovering: mIsDiscovering=false
[G1 Android Development] phatman81:
I ran /system/bin/bts; then went to the settings to start BT, it did not start, so i went back to terminal, it then showed: "BTHAL_UTILS_Assert: 0 failed in vendor/ti/btips-linux/EBTIPS/btl/ti_chip_mn: not found"
[G1 Android Development] nolsen311:
Seems to me...

We should probably be looking into modules that are supplied by default with Dream/Sapphire builds for the TI bluetooth module, but aren't supplied with the Hero builds.

It seems to me that these problems are ultimately related to there not being the correct modules for BT, as all the DBus devices/services that are needed to support the corresponding hardware are created when DBus starts, if the modules are already loaded.

It's sort of related to an idea I've had about porting Android to the Diamond for a bit...I'm thinking that the hardware supplied with upcoming Hero-based devices are going to have different hardware, with different modules. You can already see evidence of this in /system/lib/hw/sensors.hero.so (which is, presumably, a sensors module for Hero)

I'm going to try copying the extracted wlan.ko from an old Dudes build and reboot...see what that does for things. I've also deleted /system/lib/hw/sensors.hero.so...which I'm not entirely sure if it will do anything.
[G1 Android Development] afflaq:
sensors.hero.so is likely the auto-dimming light sensor. No proof on that as of yet but I suspect that's the case.
[G1 Android Development] silby:
It seems that a lot of the issue is related to the way the kernel was built for Hero. Would it be possible to swap out the boot.img file from the Rogers ROM and bypass a lot of these driver issues? What would happen if we fastboot with the boot.img from Rogers or ION?
[G1 Android Development] shafty023:
I've checked /system/lib on a cupcake build and the hero build and there's no libraries of importance that are missing. This is definitely going to be hard to get fixed without access to the modified source code that HTC has & Haykuro presumably must have. Of course that's assuming they made changes to the bluetooth stack in some way, if they didn't then we're just looking at a kernel/module issue with some minor changes to an apk file. When any of you guys uncompress an apk file are you able to read the files inside without any issues? I'm using Linux and when I uncompress them all the files are cryptic as if they're binary. Not sure if its just a Linux thing.
[G1 Android Development] daldroid:
I'm sorry, in previous post I forgot to mention that I was booting hero with a sapphire 2.6.27 kernel and added brf6300.bin firmware.

I had to reflash my device with another rom to test a build, I now cannot check out logcat messages when bluetooth goes on, but it activates. Sorry again if I was misleading.

Bye

daldroid
[G1 Android Development] shafty023:
Ok I'm gonna try this when I get home unless someone else can before I do.

1) Copy brf6300.bin from /etc/firmware on a cupcake build into same place on your phone. You should see TIInit_5.3.53.bts in there on the Hero build

2) ln -s /system/lib/modules /system/modules

3) modprobe /etc/firmware/brf6300.bin

It is giving the following error

modprobe: chdir(2.6.29-daproy-haykuro): No such file or directory

Basically it needs the kernel source. I'm running the latest 2.6.29 kernel as you can see, so whoever built this latest kernel if they could incorporate this module into the kernel and test if bluetooth works I have a feeling this could fix our issue. We could then rmmod the TIInit_5.3.53.bts module as we aren't running a Texas Instruments bluetooth chip as the Htc Hero probably will