[Samsung Galaxy Nexus] m.is.for.michael:
Hi Moles,

Just thought I'd say I'm loving the 2.99 build. I tried 4.2 for about 4 days until this morning to get a feel for it, and I think 2.99 is slicker and faster. I especially like the new t*ggles, as Google's implementation is just plain lame. And I REALLY missed [t|p]hablet view and expanded desktop. For the record, I'm using Trinity a4.

I've noticed a couple of things I thought I'd share...

1. I still needed a full wipe coming from bigxie's odexed 4.2 build. I thought I would try with a dirty flash, but (surprise!) it continuously told me systemUi had crashed.

2. Sometimes the dialler lags like crazy. As in you press numbers on the dial pad, and nothing happens for 3s, then they all appear at once.

3. I initially had trouble connecting to 5Ghz wifi; funny... just tried it as I write and it's ok now. I had a bug on 4.1 where you had to turn wifi off and on after rebooting before it would connect to the 5GHz network, so maybe it's followed me.

4. Twice, after a reboot, I've had a message telling me that com.google.process.gapps has stopped. Not sure what this means, as my phone seems to be working perfectly. Maybe it's related to the fact that I freeze some gapps (eg Talk & Currents) which I never use; logcat says around this time that it's restarting some services:

I/ActivityManager( 389): Process com.google.process.gapps (pid 721) has died.
W/ActivityManager( 389): Scheduling restart of crashed service com.google.andro
id.gsf/.gtalkservice.service.GTalkServiceProxy in 13339ms
W/ActivityManager( 389): Scheduling restart of crashed service com.google.andro
id.syncadapters.contacts/.ContactsSyncAdapterService in 23339ms
W/ActivityManager( 389): Scheduling restart of crashed service com.google.andro
id.gsf/.gtalkservice.service.GTalkService in 33338ms
I/ActivityManager( 389): Kill com.google.process.location (pid 669): provider c
om.google.android.gsf.settings.GoogleSettingsProvider in dying process com.googl
e.process.gapps
I/ActivityManager( 389): Kill com.google.android.apps.maps:GoogleLocationServic
e (pid 1006): provider com.google.android.gsf.settings.GoogleSettingsProvider in
dying process com.google.process.gapps
W/InputMethodManagerService( 389): Window already focused, ignoring focus gain
of: com.android.internal.view.IInputMethodClient$Stub$Proxy@42bc97b8 attribute=n
ull, token = android.os.BinderProxy@42d3b150
I/ActivityManager( 389): Process com.google.android.apps.maps:GoogleLocationSer
vice (pid 1006) has died.
W/ActivityManager( 389): Scheduling restart of crashed service com.google.andro
id.apps.maps/com.google.android.location.internal.server.GoogleLocationService i
n 43306ms
I/ActivityManager( 389): Process com.google.process.location (pid 669) has died
.
W/ActivityManager( 389): Scheduling restart of crashed service com.google.andr
oid.location/.internal.server.NetworkLocationService in 53304ms
W/ActivityManager( 389): Scheduling restart of crashed service com.google.andr
oid.location/.NetworkLocationService in 63304ms
W/ActivityManager( 389): Scheduling restart of crashed service com.google.andr
oid.location/.GeocodeService in 73304ms
I/ActivityManager( 389): Start proc com.google.process.gapps for service com.g
oogle.android.gsf/.subscribedfeeds.SubscribedFeedsSyncAdapterService: pid=2735
uid=10045 gids={50045, 3003, 1007, 1028, 2001, 3006}
I/ActivityManager( 389): START u0 {flg=0x4000000 cmp=com.android.email/.activi
ty.setup.AccountSetupBasics} from pid 1220
I/ActivityManager( 389): START u0 {act=android.intent.action.MAIN cat=[android
.intent.category.LAUNCHER] dat=content://ui.email.android.com/view/mailbox?ACCO
UNT_ID=1 flg=0x14000000 cmp=com.android.email/.activity.Welcome} from pid 1220
D/ConnectivityService( 389): handleInetConditionHoldEnd: net=0, condition=100,
published condition=100
I/ActivityManager( 389): Start proc com.google.android.gallery3d for service c
om.google.android.gallery3d/com.google.android.picasasync.PicasaSyncService: pi
d=2776 uid=10046 gids={50046, 1006, 3003, 1015, 1028}

As I said, though, nothing major. I had significant lag on stock when answering calls which is basically gone now (well, it's gone, but I haven't had enough calls today that I can comprehensively say it), and my battery drain on stock was appalling.

So happy to be 'home'.