As far as you know (afaYk), is the notification bug specific only to xtrROM (and not xtrSENSE)?
Sadly, it happens to me on both. It may just be the way that I am set up.
I did try running xtrSENSE with Conap's CFS kernel, but I had a hard freeze after about a day and a half. I knew that xtrROM/xtrSENSE was running Zanfur's kernel, but I didn't know it was different from the original OC kernel.
There is also Tainted Tenzo - the only thing I didn't like about that was the transparent lockscreen, but a little metamorph or maybe widgetlocker can fix that. It's possible that there is a notification issue with that; I may check that out.
I tried running CELB for a few days last week, and that was ok (one restart), but I forgot about the GPS issue and was surprised to come home from a 105 minute run to find in Runkeeper Pro that I had run 210 miles, including an extremely rapid swim 40 miles into the Atlantic Ocean and back. And I live about 40 miles away from the Atlantic. So, it's GSB from scratch for me. My GSB 2.1 was flashed over 2.0 (which was running the cache2cache script over as well) and I wondered if that was part of the issue. When I left 2.1 I was running with about 40 MB free space for apps, and I now have over 60 (with some more apps). I think flashing over GSB that was set up with cache2cache is problematic. At least I hope so.
Upvote
0