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...
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...
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
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 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.
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.
This was my guess, Aegis being the bad boy here
But thanks for the details and clarification anyway!
Unfortunately I have no idea how to package my own version, but at least there is some hope: Konttori said...
Originally Posted by
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
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.
Aha, this is very interesting. Is there any reason that this wouldn't be enabled by default?
