Enabling bluetooth throws a on the 10-23-2012 unagi device, enabling bluetooth option triggers this error. Bluetooth is detected correctly, so not sure if this is a benign error. Dupeme if i'm bug 804769. Partial Logcat: (full logcat attached) 10-23 14:20:42.799: D/memalloc(2124): /dev/pmem: Allocated buffer base:0x4cb00000 size:81920 offset:12959744 fd:281 10-23 14:20:42.809: D/memalloc(8637): /dev/pmem: Mapped buffer base:0x4844b000 size:13041664 offset:12959744 fd:67 10-23 14:20:42.819: E/memalloc(2124): unrecognized pixel format: 9 10-23 14:20:42.819: W/GraphicBufferAllocator(2124): alloc(54, 22, 9, 00000133, ...) failed -22 (Invalid argument) 10-23 14:20:42.819: I/Gonk(2124): GraphicBufferAllocator::alloc failed Repro: 1) 10-23-2012 daily unagi build, buildID: 20121023071141 2) settings > enable bluetooth 3) Verify error: Gonk(2124): GraphicBufferAllocator::alloc failed Expected: - no error on enabling Note: nom for blocking-basecamp just because i dont know what this does. -, if harmless.

Ok, I used to see something like this on desktop, related to the slider button graphic used for bluetooth power and visibility. I also can't repro it on trunk with an unagi. So assuming this still happens in nightlies tomorrow: 1. Does this happen when you use the top pull down menu to start/stop bluetooth? 2. Does this happen when bluetooth is already enabled and you try to turn on/off visibility? If 1 is no and 2 is yes, then it may be a graphics corruption issue with that widget.

This is a benign error. We're trying to create a gralloc buffer for an A8 surface, and our vendor library doesn't support that. We end up falling back on shmem+texture upload.

Kyle says: "not a crasher, we have a fallback".