Nexus 6 random issues from stock

[codycook]

I really just want to document my experience with Nexus Support and Motorola.

I have been having non-stop issues with my Nexus 6.
Model: Nexus 6
Android version: 5.1
Baseband version: MDM9625_104446.01.02.95R
Kernel version: 3.10.40-geec2459
Build number: LMY47D
Model XT1103 / FCC ID: IHDT56QD1


Basically, I used the Google Developers page to install this firmware version.
Ever since then, I've been having the most bizarre issues.

1. The phone becomes unresponsive, slow to wake up, slow to type, slow to do ANYTHING
2. I enabled show screen touches on Dev menu
3. I can see that the screen knows I'm touching it, but it's not actually computing those changes.
4. After some time, it kinda wakes up and slowly processes my input.
5. It is only 'resolvable' by restarting the phone.
6. incoming call? Nah, you don't get to swipe to answer... call drops before it even responds
7. My LG G Watch will ring and my phone never will. I can't afford that.
8. Keyboard will provide haptic feedback that I'm trying to type, and the focus APPEARS to be on the search bar or in a hangouts window, but it never popualtes the text far.

So basically, I have had it.
I chatted with Nexus Support and spoke to Deven who told me that I should contact Motorola, where I purchased my phone. He also told me that the images found on https://developers.google.com/android/nexus/images are not valid for the Motorola purchased Nexus 6. I was very mad about hearing this, I only buy Nexus so I can get these latest updates. He said that the phone Google sales is the "Google Play edition" and the one that Motorola sells, he has no idea but it isn't the same. He told me to downgrade to 5.0 and wait for OTA upgrades to the "correct" version of 5.1. since I told him I installed 5.1 through that site. He told me not to tell Motorola about using the dev.google.com page to install 5.1.
Apathetic to Deven's support, I went to Motorola and chatted with them. Gave them the same story about my device. They escalated me to Level 2. I called Level 2 and the guy did an RMA for my phone because of the kinds of problems.
After the RMA was processed, I asked him if I should be using the Google Developers page to flash my ROM on my phone. He informed me that Motorola is aware of an issue and are addressing it with the factory images (basically confirming to me that using factory images can have problems at this time). I asked if those are being addressed in the 5.1.1 factory image and he confirmed. He said they're not sure on date but expecting 5.1.1 release in July.

I just wish I had a fully functional phone I didn't have to restart every few hours.

My Motorola RMA reference also mentions that the phone is (XT1112, XT1107). From another thread, I noticed that some people saw this from Motorola but also get another US version of their phone (XT1103).

 

[danarama]

He also told me that the images found on https://developers.google.com/android/nexus/images are not valid for the Motorola purchased Nexus 6

He is talking rubbish there.

He said that the phone Google sales is the "Google Play edition"

This is also pretty much rubbish,

the one that Motorola sells, he has no idea but it isn't the same.

It is EXACTLY the same.

He told me to downgrade to 5.0 and wait for OTA upgrades to the "correct" version of 5.1.

Rubbish, they use the same ROM. Also I believe that it Isn't possible, the 5.1 Bootloader cannot be downgraded. Attempts I believe result in what many may have thought to be a brick.

 

[gee2012]

Bought my XT-1100 in a regular local store and i presume they get the devices from Motorola rather then from Google and i haven`t had a problem flashing roms from the Google Developers page. Look here http://www.randomphantasmagoria.com/firmware/nexus-6/ for the XT-1100/1103 firmwares and they should all be comaptible with your device.

 

[GuestK0087]

I'm curious, did you factory reset from recovery after flashing the factory image?

 

[danarama]

Bought my XT-1100 in a regular local store and i presume they get the devices from Motorola rather then from Google and i haven`t had a problem flashing roms from the Google Developers page. Look here http://www.randomphantasmagoria.com/firmware/nexus-6/ for the XT-1100/1103 firmwares and they should all be comaptible with your device.

Basically, same device. Only difference is bought from play = googles honour warranty. Bought from anywhere else = Motorola honour warranty

 

[gee2012]

Basically, same device. Only difference is bought from play = googles honour warranty. Bought from anywhere else = Motorola honour warranty

Off course, there are no seperate Google and Motorola roms. Moto tech. support is realy good

---------- Post added at 11:10 PM ---------- Previous post was at 10:55 PM ----------

I'm curious, did you factory reset from recovery after flashing the factory image?

Guess not, neither did he flash the userdata.img most likely.

 

[codycook]

He is talking rubbish there.
This is also pretty much rubbish,
It is EXACTLY the same.
Rubbish, they use the same ROM. Also I believe that it Isn't possible, the 5.1 Bootloader cannot be downgraded. Attempts I believe result in what many may have thought to be a brick.

I know. I haven't tried to downgrade the boot loader but this is just what they were telling me.

Bought my XT-1100 in a regular local store and i presume they get the devices from Motorola rather then from Google and i haven`t had a problem flashing roms from the Google Developers page. Look here http://www.randomphantasmagoria.com/firmware/nexus-6/ for the XT-1100/1103 firmwares and they should all be comaptible with your device.

I have looked at that page before. That's where I knew that the ROMs should be the same.

I'm curious, did you factory reset from recovery after flashing the factory image?

Yes. I did both in the ROM and also through Recovery. I tried it all.

Off course, there are no seperate Google and Motorola roms. Moto tech. support is realy good
---------- Post added at 11:10 PM ---------- Previous post was at 10:55 PM ----------

Guess not, neither did he flash the userdata.img most likely.

Actually, the way I flashed the rom was using the FLASH ALL script built into the factory images.

 

[gee2012]

I know. I haven't tried to downgrade the boot loader but this is just what they were telling me.

I have looked at that page before. That's where I knew that the ROMs should be the same.

Yes. I did both in the ROM and also through Recovery. I tried it all.

Actually, the way I flashed the rom was using the FLASH ALL script built into the factory images.

Flash All doesn`t work as it should. Flash the seperate img`s in fastboot and all should be well.
Flash: bootloader.img, radio.img, system.img, userdata.img, boot.img and erase and flash cache.img. Flashing the bootloader and radio are only necessary if you haven`t got the latest ones allready.

 

[codycook]

Flash All doesn`t work as it should. Flash the seperate img`s in fastboot and all should be well.
Flash: bootloader.img, radio.img, system.img, userdata.img, boot.img and erase and flash cache.img. Flashing the bootloader and radio are only necessary if you haven`t got the latest ones allready.

PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy47i.zip

So from what you're telling me, it doesn't properly extract the image-shamu-xyz.zip, which includes cache.img, boot.img, recovery.img, userdata.img, or system.img? And why wouldn't that be addressed here in the flash all script? isn't this the whole point?

 

[danarama]

PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy47i.zip

So from what you're telling me, it doesn't properly extract the image-shamu-xyz.zip, which includes cache.img, boot.img, recovery.img, userdata.img, or system.img? And why wouldn't that be addressed here in the flash all script? isn't this the whole point?

They've not worked properly since 5.0 even on the Nexus 5.

Just manually flash again, like suggested.

 

[gee2012]

PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy47i.zip

So from what you're telling me, it doesn't properly extract the image-shamu-xyz.zip, which includes cache.img, boot.img, recovery.img, userdata.img, or system.img? And why wouldn't that be addressed here in the flash all script? isn't this the whole point?

Follow this guide http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008, method 2 and you`re done. Flash-All is flawed atm.

 

[codycook]

They've not worked properly since 5.0 even on the Nexus 5.
Just manually flash again, like suggested.

That's interesting. I'll try it when I get my RMA since they're expecting this phone back now at Motorola.

Follow this guide http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008, method 2 and you`re done. Flash-All is flawed atm.

Thanks, will do.

I didn't start a thread here originally because I felt like the issue was related more to that memory leak issue that they've been reporting on 5.1 (which I never saw on 5.0). I figured it was a software bug and I've been waiting endlessly for 5.1.1.

 

[danarama]

That's interesting. I'll try it when I get my RMA since they're expecting this phone back now at Motorola.



Thanks, will do.

I didn't start a thread here originally because I felt like the issue was related more to that memory leak issue that they've been reporting on 5.1 (which I never saw on 5.0). I figured it was a software bug and I've been waiting endlessly for 5.1.1.

You should try it before. We think this will fix phone. I think it's highly unlikely that you developed a hardware fault at the exact time you updated.. If it doesn't fix it, send it back as arranged but it.probably will

 

[codycook]

You should try it before. We think this will fix phone. I think it's highly unlikely that you developed a hardware fault at the exact time you updated.. If it doesn't fix it, send it back as arranged but it.probably will

I'll see about formatting it tonight. I use my phone for work and am working now and the RMA comes tomorrow to work. I don't know how long it'd take to actually reproduce, I'll just try restoring the profile and see if that helps out.

Thanks again.

 

[codycook]

As an update for today, phone has been on for 13 hours. I'm going to try and ride the phone out for the rest of the day and then do the swap over tonight with my replacement. I am not seeing the same exact problems at this time, but I'll wait until I get to work to be totally sure.

 

[gee2012]

As an update for today, phone has been on for 13 hours. I'm going to try and ride the phone out for the rest of the day and then do the swap over tonight with my replacement. I am not seeing the same exact problems at this time, but I'll wait until I get to work to be totally sure.

If you wiped and flashed correctly the problems should be gone for good

 

[codycook]

I'm back! The problem is back!
I finally got the chance to get into bug report and run it.
It's like 13 MB of data.
...
<6>[28779.226485] lowmemorykiller: Killing 'ola.service.ims' (13608), adj 1000,
<6>[28779.226485] to free 39280kB on behalf of 'kswapd0' (108) because
<6>[28779.226485] cache 162880kB is below limit 184320kB for oom_score_adj 1000
<6>[28779.226485] Free memory is 47184kB above reserved
<6>[28779.409308] lowmemorykiller: Killing 'lugins.sprintdm' (13625), adj 1000,
<6>[28779.409308] to free 40300kB on behalf of 'kswapd0' (108) because
<6>[28779.409308] cache 157444kB is below limit 184320kB for oom_score_adj 1000
<6>[28779.409308] Free memory is 52268kB above reserved
<6>[28779.496058] lowmemorykiller: Killing 'ogle.android.gm' (13568), adj 1000,
<6>[28779.496058] to free 54636kB on behalf of 'kswapd0' (108) because
<6>[28779.496058] cache 155972kB is below limit 184320kB for oom_score_adj 1000
<6>[28779.496058] Free memory is 55340kB above reserved
<6>[28779.591225] binder: undelivered transaction 15176061
<6>[28780.245170] binder: 810:1538 transaction failed 29189, size 920-0
<6>[28782.771913] lowmemorykiller: Killing 'm.verizon.omadm' (13644), adj 764,
<6>[28782.771913] to free 38968kB on behalf of 'kswapd0' (108) because
<6>[28782.771913] cache 147328kB is below limit 147456kB for oom_score_adj 529
<6>[28782.771913] Free memory is 55180kB above reserved
<6>[28788.029112] binder: release 13124:13124 transaction 15179191 out, still active
<6>[28788.029129] binder: release 13124:13320 transaction 15179411 out, still active
...
<6>[29016.744588] lowmemorykiller: Killing 'id.apps.fitness' (15173), adj 1000,
<6>[29016.744588] to free 52508kB on behalf of 'kswapd0' (108) because
<6>[29016.744588] cache 184220kB is below limit 184320kB for oom_score_adj 1000
<6>[29016.744588] Free memory is 53656kB above reserved
<6>[29016.881597] lowmemorykiller: Killing 'le.android.talk' (15686), adj 1000,
<6>[29016.881597] to free 54468kB on behalf of 'kswapd0' (108) because
<6>[29016.881597] cache 184216kB is below limit 184320kB for oom_score_adj 1000
<6>[29016.881597] Free memory is 55464kB above reserved
<6>[29017.164324] lowmemorykiller: Killing 'roid.music:main' (14991), adj 1000,
<6>[29017.164324] to free 49592kB on behalf of 'kswapd0' (108) because
<6>[29017.164324] cache 183752kB is below limit 184320kB for oom_score_adj 1000
<6>[29017.164324] Free memory is 52200kB above reserved
<6>[29017.303049] lowmemorykiller: Killing 'ndroid.calendar' (15576), adj 1000,
<6>[29017.303049] to free 46048kB on behalf of 'kswapd0' (108) because
<6>[29017.303049] cache 184116kB is below limit 184320kB for oom_score_adj 1000
<6>[29017.303049] Free memory is 52220kB above reserved
<6>[29017.333869] lowmemorykiller: Killing 'oadcastreceiver' (15869), adj 1000,
<6>[29017.333869] to free 41216kB on behalf of 'kswapd0' (108) because
<6>[29017.333869] cache 183528kB is below limit 184320kB for oom_score_adj 1000
<6>[29017.333869] Free memory is 54576kB above reserved
<6>[29018.963012] lowmemorykiller: Killing '.editors.sheets' (15740), adj 1000,
<6>[29018.963012] to free 65164kB on behalf of 'kswapd0' (108) because
<6>[29018.963012] cache 151608kB is below limit 184320kB for oom_score_adj 1000
<6>[29018.963012] Free memory is 54024kB above reserved
...
It looks like it keeps trying to suspend and unsuspend itself.

<6>[28069.451099] PM: suspend entry 2015-06-01 19:49:34.890829433 UTC
<6>[28069.451125] PM: Syncing filesystems ... done.
<7>[28069.485664] PM: Preparing system for mem sleep
<4>[28069.487176] Freezing user space processes ...
<6>[28069.488241] active wakeup source: PowerManagerService.WakeLocks
<6>[28069.488258] active wakeup source: msm_hsic_host
<4>[28069.488282]
<3>[28069.488291] Freezing of tasks aborted after 0.001 seconds (23 tasks refusing to freeze, wq_busy=0):
<4>[28069.488297]
<4>[28069.488303] Restarting tasks ... done.
<6>[28069.489709] PM: suspend exit 2015-06-01 19:49:34.929447037 UTC
<6>[28079.292437] PM: suspend entry 2015-06-01 19:49:44.732152554 UTC
<6>[28079.292477] PM: Syncing filesystems ... done.
<7>[28079.333747] PM: Preparing system for mem sleep
<4>[28079.335442] Freezing user space processes ...
<6>[28079.337167] active wakeup source: PowerManagerService.WakeLocks
<4>[28079.337222]
<3>[28079.337231] Freezing of tasks aborted after 0.001 seconds (23 tasks refusing to freeze, wq_busy=0):
<4>[28079.337236]
<4>[28079.337242] Restarting tasks ... done.
<6>[28079.339108] PM: suspend exit 2015-06-01 19:49:44.778846304 UTC
<6>[28088.655696] PM: suspend entry 2015-06-01 19:49:54.095409009 UTC
<6>[28088.655747] PM: Syncing filesystems ... done.
<7>[28088.688787] PM: Preparing system for mem sleep
<4>[28088.690432] Freezing user space processes ... (elapsed 0.003 seconds) done.
<4>[28088.694397] Freezing remaining freezable tasks ... (elapsed 0.004 seconds) done.
<7>[28088.698662] PM: Entering mem sleep
<4>[28088.698668] Suspending console(s) (use no_console_suspend to debug)
<3>[28088.736025] dpm_run_callback(): platform_pm_suspend+0x0/0x58 returns -16
<3>[28088.736030] PM: Device alarmtimer failed to suspend: error -16
<3>[28088.736035] PM: Some devices failed to suspend
<6>[28088.924950] PM: resume of devices complete after 188.906 msecs
<7>[28088.928486] PM: Finishing wakeup.
<4>[28088.928491] Restarting tasks ... done.
<6>[28088.945588] PM: suspend exit 2015-06-01 19:49:54.385306821 UTC
...
<6>[28585.854223] atmel_mxt_ts_mmi: mxt_set_sensor_state: state change SUSPEND -> ACTIVE
<3>[28588.295545] mdss_mdp_pipe_init: no 3 type pipes available
<3>[28588.295565] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.295615] mdss_mdp_pipe_init: no 3 type pipes available
<3>[28588.295621] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.295644] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.295661] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.295680] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.295685] mdss_mdp_pipe_init: no 1 type pipes available
<3>[28588.295692] mdss_mdp_overlay_pipe_setup: error allocating pipe. flags=0x60200
<3>[28588.295908] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.295927] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.295945] mdss_mdp_pipe_init: no 3 type pipes available
<3>[28588.295951] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.295969] mdss_mdp_pipe_init: no 3 type pipes available
<3>[28588.295975] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.295994] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.296004] mdss_mdp_pipe_init: no 1 type pipes available
<3>[28588.296013] mdss_mdp_overlay_pipe_setup: error allocating pipe. flags=0x60200
<3>[28588.296110] mdss_mdp_pipe_init: no 3 type pipes available
<3>[28588.296118] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.296141] mdss_mdp_pipe_init: no 3 type pipes available
<3>[28588.296149] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.296167] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28588.296185] mdss_mdp_pipe_init: no 2 type pipes available
<3>[28589.059032] mdss_mdp_pipe_init: no 1 type pipes available
<3>[28589.059044] mdss_mdp_overlay_pipe_setup: error allocating pipe. flags=0x860000
<3>[28589.075860] mdss_mdp_pipe_init: no 1 type pipes available
<3>[28589.075871] mdss_mdp_overlay_pipe_setup: error allocating pipe. flags=0x860000
<3>[28589.092918] mdss_mdp_pipe_init: no 1 type pipes available
<3>[28589.092929] mdss_mdp_overlay_pipe_setup: error allocating pipe. flags=0x860000
<3>[28589.109957] mdss_mdp_pipe_init: no 1 type pipes available
<3>[28589.109969] mdss_mdp_overlay_pipe_setup: error allocating pipe. flags=0x860000
<3>[28589.127331] mdss_mdp_pipe_init: no 1 type pipes available

 

[codycook]

Adding s'more data.

------ SYSTEM LOG (logcat -v threadtime -d *:v) ------
--------- beginning of crash
05-31 20:27:03.832 326 329 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 329 (BootAnimation)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: FATAL EXCEPTION: main
06-01 15:21:19.714 6246 6246 E AndroidRuntime: Process: com.google.android.gms.persistent, PID: 6246
06-01 15:21:19.714 6246 6246 E AndroidRuntime: java.lang.RuntimeException: Unable to create service com.google.android.location.reporting.service.ReportingAndroidService: java.lang.IllegalStateException: Not in location process
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at android.app.ActivityThread.handleCreateService(ActivityThread.java:2771)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at android.app.ActivityThread.access$1800(ActivityThread.java:151)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1386)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at android.os.Looper.loop(Looper.java:135)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5254)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at java.lang.reflect.Method.invoke(Method.java:372)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: Caused by: java.lang.IllegalStateException: Not in location process
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at com.google.android.location.reporting.d.b.c(SourceFile:73)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at com.google.android.location.reporting.config.h.a(SourceFile:92)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at com.google.android.location.reporting.service.ReportingAndroidService.onCreate(SourceFile:61)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: at android.app.ActivityThread.handleCreateService(ActivityThread.java:2761)
06-01 15:21:19.714 6246 6246 E AndroidRuntime: ... 9 more


here's the part where my navbar vanishes...
06-01 17:34:17.268 810 992 I InputDispatcher: Application is not responding: Window{15501760 u0 NavigationBar}. It has been 5057.5ms since event, 5057.2ms since wait started. Reason: Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 3. Wait queue head age: 5840.2ms.
06-01 17:34:17.271 810 992 I WindowManager: Input event dispatching timed out sending to NavigationBar. Reason: Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 3. Wait queue head age: 5840.2ms.

and where smartcard flips out, making my simcard vanish and kick me off the network
06-01 17:34:20.729 18884 18899 W TRThreadPoolExecutor: Task "GmsLocationReporting[getReportingState]" is a ac. Failures of FutureTask can not be detected and exceptions will not be propagated by the executor
06-01 17:34:20.779 18884 18899 W TRThreadPoolExecutor: Task "p[Get token]" is a o. Failures of FutureTask can not be detected and exceptions will not be propagated by the executor
06-01 17:34:20.822 8392 8414 I SmartcardService ACE ARF: Logical channels are used to access to PKC15
06-01 17:34:20.822 8392 8414 V ACE ARF EF_Dir: Analysing EF_DIR...
06-01 17:34:20.901 8392 8414 D SmartcardService ACE ARF: SelectFile [3*38b]
06-01 17:34:20.901 8392 8414 D SmartcardService ACE ARF: ReadRecord [1/38b]
06-01 17:34:20.921 8392 8414 D SmartcardService ACE ARF: ReadRecord [2/38b]
06-01 17:34:20.941 8392 8414 D SmartcardService ACE ARF: ReadRecord [3/38b]
06-01 17:34:20.965 8392 8414 E SmartcardService ACE ARF: SIM - UICC rules not correctly initialized! [Parser] Cannot retreive type
06-01 17:34:21.012 8392 8414 E SmartcardService: [Parser] Cannot retreive type
06-01 17:34:21.012 8392 8414 I SmartcardService: Deny any access to:SIM - UICC
06-01 17:34:21.012 8392 8414 E SmartcardService: Fail to load rules: Let's try another time (5 remaining attempt
06-01 17:34:21.183 810 838 I Process : Sending signal. PID: 18884 SIG: 3
06-01 17:34:21.183 18884 18893 I art : Thread[5,tid=18893,WaitingInMainSignalCatcherLoop,Thread*=0xb4a17c00,peer=0x32c070a0,"Signal Catcher"]: reacting to signal 3
06-01 17:34:21.383 810 838 I Process : Sending signal. PID: 28578 SIG: 3
06-01 17:34:21.384 28578 28587 I art : Thread[5,tid=28587,WaitingInMainSignalCatcherLoop,Thread*=0xb4a17c00,peer=0x12c000a0,"Signal Catcher"]: reacting to signal 3
06-01 17:34:21.481 18884 18893 I art : Wrote stack traces to '/data/anr/traces.txt'
06-01 17:34:21.482 810 838 I Process : Sending signal. PID: 1452 SIG: 3
06-01 17:34:21.482 1452 1461 I art : Thread[5,tid=1461,WaitingInMainSignalCatcherLoop,Thread*=0xb4a17c00,peer=0x32c070a0,"Signal Catcher"]: reacting to signal 3
06-01 17:34:21.657 1452 1461 I art : Wrote stack traces to '/data/anr/traces.txt'
06-01 17:34:21.657 810 838 I Process : Sending signal. PID: 1222 SIG: 3
06-01 17:34:21.657 1222 1231 I art : Thread[5,tid=1231,WaitingInMainSignalCatcherLoop,Thread*=0xb4a17c00,peer=0x12c000a0,"Signal Catcher"]: reacting to signal 3
06-01 17:34:21.716 28578 28587 I art : Wrote stack traces to '/data/anr/traces.txt'
06-01 17:34:21.742 810 838 E ActivityManager: ANR in com.android.systemui
06-01 17:34:21.742 810 838 E ActivityManager: PID: 27358
06-01 17:34:21.742 810 838 E ActivityManager: Reason: Input dispatching timed out (Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 3. Wait queue head age: 5788.5ms.)
06-01 17:34:21.742 810 838 E ActivityManager: Load: 13.92 / 13.68 / 13.22
06-01 17:34:21.742 810 838 E ActivityManager: CPU usage from 3245ms to -4458ms ago with 99% awake:
06-01 17:34:21.742 810 838 I ActivityManager: Killing 27358:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:34:21.819 810 1486 E JavaBinder: !!! FAILED BINDER TRANSACTION !!!
06-01 17:34:21.828 810 1537 W AudioService: Current remote volume controller died, unregistering
06-01 17:34:21.828 810 1148 I WindowState: WIN DEATH: Window{238d62cd u0 com.android.systemui.ImageWallpaper}
06-01 17:34:21.828 810 1002 D WifiService: Client connection lost with reason: 4
06-01 17:34:21.829 810 1002 D WifiService: Client connection lost with reason: 4
06-01 17:34:21.832 810 825 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ id=22, legacyType=-1, [] ], [email protected])
06-01 17:34:21.832 810 992 W InputDispatcher: channel '3c41bdeb StatusBar (server)' ~ Consumer closed input channel or an error occurred. events=0x9
06-01 17:34:21.832 810 992 E InputDispatcher: channel '3c41bdeb StatusBar (server)' ~ Channel is unrecoverably broken and will be disposed!


Last but not least, a grep from the log of all "bg anr" and what processes they killed.

C:\Users\Cody
λ cat "Google Drive\bugreport-2015-06-01-17-36-25.txt" | grep "bg anr"
06-01 17:34:21.742 810 838 I ActivityManager: Killing 27358:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:34:26.336 810 838 I ActivityManager: Killing 32592:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:34:30.768 810 838 I ActivityManager: Killing 32649:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:34:35.522 810 838 I ActivityManager: Killing 32680:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:34:40.425 810 838 I ActivityManager: Killing 32709:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:34:46.032 810 838 I ActivityManager: Killing 32731:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:34:49.976 810 838 I ActivityManager: Killing 32755:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:34:54.337 810 838 I ActivityManager: Killing 441:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:34:59.135 810 838 I ActivityManager: Killing 506:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:35:03.670 810 838 I ActivityManager: Killing 642:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:35:07.939 810 838 I ActivityManager: Killing 769:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:35:12.454 810 838 I ActivityManager: Killing 834:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:35:20.498 810 838 I ActivityManager: Killing 890:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:35:25.806 810 838 I ActivityManager: Killing 931:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:35:31.339 810 838 I ActivityManager: Killing 974:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:35:36.446 810 838 I ActivityManager: Killing 1016:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:35:41.876 810 838 I ActivityManager: Killing 1067:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:35:47.047 810 838 I ActivityManager: Killing 1086:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:35:52.348 810 838 I ActivityManager: Killing 1106:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:35:57.114 810 838 I ActivityManager: Killing 1132:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:01.769 810 838 I ActivityManager: Killing 1154:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:07.001 810 838 I ActivityManager: Killing 1184:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:12.497 810 838 I ActivityManager: Killing 1207:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:17.704 810 838 I ActivityManager: Killing 1227:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:23.281 810 838 I ActivityManager: Killing 1272:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:27.638 810 838 I ActivityManager: Killing 1302:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:32.760 810 838 I ActivityManager: Killing 1331:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:37.050 810 838 I ActivityManager: Killing 1405:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:42.110 810 838 I ActivityManager: Killing 1499:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:46.501 810 838 I ActivityManager: Killing 1645:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:51.847 810 838 I ActivityManager: Killing 1713:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:36:57.029 810 838 I ActivityManager: Killing 1796:com.android.systemui/u0a29 (adj -12): bg anr
06-01 17:20:34.507 810 838 I am_kill : [0,20151,com.facebook.orca,0,bg anr]
06-01 17:20:57.425 810 838 I am_kill : [0,4992,com.android.phone,-12,bg anr]
06-01 17:21:07.090 810 838 I am_kill : [0,6150,com.google.process.gapps,0,bg anr]
06-01 17:21:23.924 810 838 I am_kill : [0,28314,com.android.systemui,-12,bg anr]
06-01 17:21:54.441 810 838 I am_kill : [0,4717,com.facebook.katana,8,bg anr]
06-01 17:22:08.164 810 838 I am_kill : [0,21453,com.facebook.orca,0,bg anr]
06-01 17:22:38.877 810 838 I am_kill : [0,21794,com.android.phone,-12,bg anr]
06-01 17:22:51.845 810 838 I am_kill : [0,22025,com.google.process.gapps,0,bg anr]
06-01 17:25:14.145 810 838 I am_kill : [0,23249,com.facebook.katana,8,bg anr]
06-01 17:25:24.330 810 838 I am_kill : [0,23344,com.facebook.orca,0,bg anr]
06-01 17:25:43.528 810 838 I am_kill : [0,24369,com.google.process.gapps,0,bg anr]
06-01 17:25:47.753 810 838 I am_kill : [0,9549,com.google.android.gms.persistent,0,bg anr]
06-01 17:26:08.244 810 838 I am_kill : [0,24180,com.android.phone,-12,bg anr]
06-01 17:26:18.016 810 838 I am_kill : [0,26446,com.google.android.gms.persistent,0,bg anr]
06-01 17:26:26.658 810 838 I am_kill : [0,26315,com.google.process.gapps,0,bg anr]
06-01 17:26:32.981 810 838 I am_kill : [0,22508,com.android.systemui,-12,bg anr]
06-01 17:26:37.034 810 838 I am_kill : [0,26941,com.android.phone,-12,bg anr]
06-01 17:26:44.325 810 838 I am_kill : [0,27147,com.google.android.gms.persistent,0,bg anr]
06-01 17:27:02.016 810 838 I am_kill : [0,27378,com.android.phone,-12,bg anr]
06-01 17:27:23.184 810 838 I am_kill : [0,27806,com.google.android.gms.persistent,0,bg anr]
06-01 17:27:55.398 810 838 I am_kill : [0,28182,com.google.android.gms.persistent,0,bg anr]
06-01 17:28:20.566 810 838 I am_kill : [0,28423,com.google.android.gms.persistent,0,bg anr]
06-01 17:33:03.267 810 838 I am_kill : [0,26054,com.facebook.orca,5,bg anr]
06-01 17:33:19.084 810 838 I am_kill : [0,28129,com.android.phone,-12,bg anr]
06-01 17:33:44.191 810 838 I am_kill : [0,31344,com.android.phone,-12,bg anr]
06-01 17:34:21.742 810 838 I am_kill : [0,27358,com.android.systemui,-12,bg anr]
06-01 17:34:26.336 810 838 I am_kill : [0,32592,com.android.systemui,-12,bg anr]
06-01 17:34:30.768 810 838 I am_kill : [0,32649,com.android.systemui,-12,bg anr]
06-01 17:34:35.522 810 838 I am_kill : [0,32680,com.android.systemui,-12,bg anr]
06-01 17:34:40.425 810 838 I am_kill : [0,32709,com.android.systemui,-12,bg anr]
06-01 17:34:46.032 810 838 I am_kill : [0,32731,com.android.systemui,-12,bg anr]
06-01 17:34:49.976 810 838 I am_kill : [0,32755,com.android.systemui,-12,bg anr]
06-01 17:34:54.337 810 838 I am_kill : [0,441,com.android.systemui,-12,bg anr]
06-01 17:34:59.135 810 838 I am_kill : [0,506,com.android.systemui,-12,bg anr]
06-01 17:35:03.670 810 838 I am_kill : [0,642,com.android.systemui,-12,bg anr]
06-01 17:35:07.939 810 838 I am_kill : [0,769,com.android.systemui,-12,bg anr]
06-01 17:35:12.454 810 838 I am_kill : [0,834,com.android.systemui,-12,bg anr]
06-01 17:35:20.499 810 838 I am_kill : [0,890,com.android.systemui,-12,bg anr]
06-01 17:35:25.806 810 838 I am_kill : [0,931,com.android.systemui,-12,bg anr]
06-01 17:35:31.339 810 838 I am_kill : [0,974,com.android.systemui,-12,bg anr]
06-01 17:35:36.446 810 838 I am_kill : [0,1016,com.android.systemui,-12,bg anr]
06-01 17:35:41.876 810 838 I am_kill : [0,1067,com.android.systemui,-12,bg anr]
06-01 17:35:47.047 810 838 I am_kill : [0,1086,com.android.systemui,-12,bg anr]
06-01 17:35:52.348 810 838 I am_kill : [0,1106,com.android.systemui,-12,bg anr]
06-01 17:35:57.114 810 838 I am_kill : [0,1132,com.android.systemui,-12,bg anr]
06-01 17:36:01.769 810 838 I am_kill : [0,1154,com.android.systemui,-12,bg anr]
06-01 17:36:07.002 810 838 I am_kill : [0,1184,com.android.systemui,-12,bg anr]
06-01 17:36:12.498 810 838 I am_kill : [0,1207,com.android.systemui,-12,bg anr]
06-01 17:36:17.704 810 838 I am_kill : [0,1227,com.android.systemui,-12,bg anr]
06-01 17:36:23.281 810 838 I am_kill : [0,1272,com.android.systemui,-12,bg anr]
06-01 17:36:27.638 810 838 I am_kill : [0,1302,com.android.systemui,-12,bg anr]
06-01 17:36:32.760 810 838 I am_kill : [0,1331,com.android.systemui,-12,bg anr]
06-01 17:36:37.050 810 838 I am_kill : [0,1405,com.android.systemui,-12,bg anr]
06-01 17:36:42.110 810 838 I am_kill : [0,1499,com.android.systemui,-12,bg anr]
06-01 17:36:46.502 810 838 I am_kill : [0,1645,com.android.systemui,-12,bg anr]
06-01 17:36:51.847 810 838 I am_kill : [0,1713,com.android.systemui,-12,bg anr]
06-01 17:36:57.029 810 838 I am_kill : [0,1796,com.android.systemui,-12,bg anr]

 

[codycook]

I'd consider posting my bugreport if 1) it wasn't so damn huge, and 2) there wasn't so much identifying information in it.

If there really is a memory leak issue as most of the Android 5 news articles mention, and it's something that Google'll address, I'm okay with that, but if it isn't , w...t...f....
p.s. I sent back the Motorola replacement, mainly because they sent me a phone without the screen protector on it (I still have the factory screen protector on my original N6), but it was really because I had hoped I fixed my phone based on these suggestions.

 

[Android The Greek]

I'd consider posting my bugreport if 1) it wasn't so damn huge, and 2) there wasn't so much identifying information in it.

If there really is a memory leak issue as most of the Android 5 news articles mention, and it's something that Google'll address, I'm okay with that, but if it isn't , w...t...f....
p.s. I sent back the Motorola replacement, mainly because they sent me a phone without the screen protector on it (I still have the factory screen protector on my original N6), but it was really because I had hoped I fixed my phone based on these suggestions.

Could be a hardware issue or the HAL