On 03/05/2013 10:20 AM, Mateor wrote:
Hi,
I have been building SEAndroid for grouper for the last several days,
continually experiencing a crash after setting SE policy to enforced
(the display dies, and I get some sort of 'transaction too large' error):
"E/JavaBinder( 483): !!! FAILED BINDER TRANSACTION !!!
E/ServiceManager( 483): error in getService
E/ServiceManager( 483): android.os.TransactionTooLargeException"
Is this perhaps because I need to spend some more time crafting my
individual policy? I was thinking that it would be at a usable default,
but perhaps I am missing a step.
This build was done from a clobber immediately after the release of the
4.2.2 merge yesterday, but I had a similar experience when using the
4.2.2 branch for several days before that merge. This is the [manifest](
https://bitbucket.org/seandroid/manifests/src/d67d7700b32d3fbd44258a7231fe368230538aac/?at=seandroid-4.2)
that I used for the below logs.
My logcat from the crash is here (excerpting out tens of thousands of
"W/DisplayEventReceiver( 1954): Failed to get events from display event
receiver, status=-13" lines): http://pastebin.com/YH8SjUnA
And the subsequent boot loop is here: http://pastebin.com/BpS6tHWb.
A factory reset is required to boot the device subsequently. Anyone have
an idea of where I am having trouble?
Have you previously run 4.2.1 successfully on the device?
Can you send a copy of your /data/misc/audit/audit.log file?
--
This message was distributed to subscribers of the seandroid-list mailing list.
If you no longer wish to subscribe, send mail to majord...@tycho.nsa.gov with
the words "unsubscribe seandroid-list" without quotes as the message.
