|
2011-10-31
, 22:24
|
|
Posts: 597 |
Thanked: 490 times |
Joined on Dec 2009
@ Germany
|
#312
|
|
2011-11-01
, 15:04
|
Posts: 197 |
Thanked: 101 times |
Joined on Dec 2009
@ Netherlands
|
#313
|
|
2011-11-01
, 15:43
|
|
Posts: 597 |
Thanked: 490 times |
Joined on Dec 2009
@ Germany
|
#314
|
I'm sorry you got into trouble with the device.
maybe there is a way to reinstall the obexd package.
It might be that they setup selinux on the device to guard against overwrites. Guess someone must know about that on the meego forums...
|
2011-11-01
, 16:05
|
Posts: 1,203 |
Thanked: 3,027 times |
Joined on Dec 2010
|
#315
|
|
2011-11-01
, 17:33
|
|
Posts: 738 |
Thanked: 983 times |
Joined on Apr 2010
@ London
|
#316
|
No worries, wasnīt your fault, appreciate your support on this!
Did everything on my own risk and canīt even tell what exactly bricked the device. When I tried to investigate this further I noticed that ps | grep obex didnīt give me the usual startup command. So I did a chmod a+x obexd and tried to restart obex manually. But restarting was denied with permission denied (yes I was root). Then I wanted to reboot, but phone just gave me a warning as described before.
Thus, reinstalling obexd package wasnīt possible and I had to reflash.
Reflash worked like a charm, so I am again a happy N9 user...Besides the PBAP-issue of course
The Following User Says Thank You to erendorn For This Useful Post: | ||
|
2011-11-03
, 19:17
|
|
Posts: 597 |
Thanked: 490 times |
Joined on Dec 2009
@ Germany
|
#317
|
The aegis security checks the hashes of the binaries, and compare them to authorized ones. It will prevent you from running your non Nokia signed version, even as root (permission denied), and will prevent the system from running it during boot (bricked device).
If you don't need too many privileges for obexd, you can try to package your custom version, and install (dpkg) it in devel mode (which may get aegis to register and trust the binary).
If this needs privileges restricted to Nokia, then you won't be able to change the obexd without using a custom, aegis-free kernel.
See there for details.
A lot of work has been put to better interoperability of BT with cars. I don't know of the exact model you have, but likely the situation is better in PR1.1
|
2011-11-04
, 13:32
|
Posts: 31 |
Thanked: 7 times |
Joined on Jan 2010
|
#318
|
It is not that the n9 does not supprot IrMC. It is just that pbap is enabled (--pbap) while irmc is not (there is no --irmc commandline option in your ps output) Adding --irmc should enable IrMC.
|
2011-11-04
, 13:42
|
Posts: 31 |
Thanked: 7 times |
Joined on Jan 2010
|
#319
|
|
2011-11-04
, 19:47
|
|
Posts: 597 |
Thanked: 490 times |
Joined on Dec 2009
@ Germany
|
#320
|
Wrong forum, but do anyone know where the startup options for obexd are specified?
Can't find it anywhere, and I can't kill the obexd-process, so I can't start it manually with the right options either...
The Following User Says Thank You to Reflektorfalke For This Useful Post: | ||
This is what I did:
Copied from N900 to N9:
obexd to /usr/lib/obex and
libopenobex.so.2.0.0 to /usr/lib
Then
ln -s libopenobex.so.2.0.0 libopenobex.so.2
Can still pair phone and carkit, but when it tries to transfer contacts it cancels immediately. Nothing transferred at all...
Thanks again anyway mirakels, your efforts are highly appreciated!
------------------------------------------------------------
Bluetooth PBAP-Profile/Carkit support - Check Wiki-Page
Sociality FB-Client, MAG strikes again - Check Wiki-Page
QNeptunea -Best Twitter Client for N9/N950 - HowTo Create Themes