Android 4.3 SDK

[Nate2]

I became so intrigued with the ongoing Android 4.3 issues that I actually updated my SDK to take a close look at what 4.3 was up to:

As soon as I launched my Nexus 7 Android 4.3 (JWR66V) AVD, it locked up!
I have used 4.1, 4.0 and 2.x and have never seen this happen in my Emulator.
Launched AVD again, and this time the Launcher crashed when I tried to get into the app drawer:

About screen:

Going to leave it running for a while...

 

[Nate2]

My Nexus 7 Emulator running Android 4.3 JRW66V locked up this morning (less than 24 hours). I was simply navigating screens to see what apps were installed by default, and what options were available for some settings, and when I returned to the Home screen, it locked up.

I had to "kill -9" it's process id to exit
I am going to run a Android 4.1.2 AVD next to it now, to highlight how much more stable that is.

The Linux PC the Android Emulator is running on is fine: over 396 days of System Uptime (yes, it's been over a year since I rebooted this machine), and fairly heavy use too.

 

[rmm200]

You don't show your AVD definition. There are some known restrictions, like set your memory size to 512.

Sent from my Nexus 7 using xda app-developers app

 

[Nate2]

You don't show your AVD definition. There are some known restrictions, like set your memory size to 512.

Thanks for the info!
The default heap size was not big enough. Increasing it fixed the Launcher issue:

 

[Nate2]

I'm seeing some errors in the logcat, that kinda look serious:

 

[rmm200]

Looks like application warnings as opposed to error. A whole stack trace only refers to one event. Exciting a process without issuing a specific close is just poor practice. Likewise doing too much on a main thread is poor practice.

Sent from my Nexus 7 using xda app-developers app

 

[Nate2]

The 2nd looks like it may cause a resource leak. I see multiple instances of that stack trace.
Can Finalization (and proper Garbage Collection) occur if there are still references to the file handle, since it is not being explicitly closed?

 

[Nate2]

nbench numbers for the emulator: http://forum.xda-developers.com/showthread.php?p=44662246

 

[Nate2]

Another possible resource leak:

This one looks like "IBackupAgent" (an intrinsic Android app? ) not closing a file descriptor (Parcel class? )

 

[Nate2]

And another, this one from Google Messaging Services (gms) ?

 

[Nate2]

2 more... This is from Google Maps/Navigation:

And this is from the Contacts editor:

We also see a cursor being finalized without a prior close().

And what are those "screenshot failure" messages? I am not taking any screenshots using the Android emulator.

 

[Nate2]

Angry Birds seems to run fine on the emulator without generating any error messages in the logcat.

 

[Nate2]

Encountered this error while trying to send an e-mail with the built in e-mail app. The e-mail was delivered.

 

[Nate2]

And this new error has to do with the native AlarmScheduler / AlertService:

 

[Nate2]

This error caused by the browser:

 

[autophone]

My nexus 7 has horrible battery life ever since I updated to 4.3. It drains in a few hours from full charge on standby. Just now I took it off the charger after recharging it for 5+ hours only to find that it had 80℅ left. Its been like 10 mins and I am already down to 75℅. I am not sure if I have a damage battery or the update. I am running stock and never root it since I bought it.

Sent from my Nexus 7 using xda app-developers app

 

[Nate2]

My nexus 7 has horrible battery life ever since I updated to 4.3. It drains in a few hours from full charge on standby.

What apps are running? Post a screenshot of battery settings (shows battery consumption by apps) and history (shows periods of wifi use and when device was not asleep).

Sent from my Nexus 7 using Tapatalk 4