[AT&T HTC One (M7)] Cipherblox:
I know we can't submit bug reports on JIRA for nightlies so I figured I would report a few things here. I was wondering if these are experienced by everyone and if there is a fix in the pipeline.

1. When making a call, ending a call (or perhaps whenever starting and stopping audio) there is an audible pop.

2. When long pressing an icon on the homescreen, even with vibration off, there is a very short very light vibration. (I'm not overly bothered by this and it may be a design decision)

3. I can reproduce this reliably within a zoomable E-Mail (in the G-Mail app) and unreliably on webpages. If you open an E-Mail and the first (and only first) touch/drag is slow the E-Mail zooms in. After this initial zoom it doesn't happen again unless you close the E-Mail, reopen it, and drag slowly again. If you open the E-Mail and quickly drag your finger, it doesn't appear to trigger this condition (and effectively prevents it from happening as the quick drag was your first touch). I monitored logcat in verbose mode and nothing occurred when dragging the message around.

4. Although I saw the commit for the TFA9887 which will probably address this, the speaker does not appear to reach the same sound levels possible outside of AOSP.

5. Wi-Fi performance seems to be suffering a little bit. This may be erroneous but I was wondering what everyone else's experiences were.

6. Tapping the NFC toggle either in Settings or in Quick Settings does not appear to update properly. I believe the tap actually turns it off, but the the options just remains greyed out like it is processing something until I restart.

Addtionally, I was curious regarding a couple of features:

1. AMR-WB - Is this good to go on our end pending carrier?

2. Tunnel Audio - Is this enabled on the M7 or do we use a similar low power/low latency mechanism?

3. I appear to be in an area with poor LTE coverage but excellent coverage otherwise. Even with WiFi on, would it be at all beneficial to toggle LTE off to avoid constant switching back and forth? I'm probably not thinking of something (MMS maybe?), but is there a reason to not fall back completely to 2G with WiFi on and connected?

While I don't know if the following are CM specific issues and would certainly have no objections if you felt this needed it's own thread, I thought it might be something CM might be able to address.

1. When powering the display on or powering it off, it takes a quick moment to respond. I have the electron beam animation disabled. I noticed in logcat that Google feels that these are excessive delays as evidenced by the warning:

D/PowerManagerService-JNI( 576): Excessive delay in autosuspend_disable() while turning screen on: 456ms
D/SurfaceControl( 576): Excessive delay in unblankDisplay() while turning screen on: 517ms
D/SurfaceControl( 576): Excessive delay in blankDisplay() while turning screen off: 153ms

I know we have a very large display and it probably takes a minute to rewake everything, populate, and finally flush the framebuffer to the screen - but I was simply curious as to whether anyone from CM has looked into this methods so see what may be taking up so much time.

2. Google Services appear to use up a larger chunk of power than I am used to after coming from a Galaxy S2. While it may be due to differences in how different threads are grouped, after looking at BetterBatteryStats, I've noticed that NLP (Network Location Provider) and NLL (Network Location Locator) appear to hold and release a lot of wake locks. While this is to be expected, I was particular interested in what everyone thought of this:

D/YouTube MDX(14235): Recieved intent android.intent.action.SCREEN_ON
E/LocSvc_eng( 576): I/===> int loc_eng_inject_location(loc_eng_data_s_type&, double, double, float) line 729
E/LocSvc_utils_q( 576): D/msg_q_snd: Sending message with handle = 0x7211D6A8
E/LocSvc_utils_ll( 576): D/linked_list_add: Adding to list data_obj = 0x7211D6A8
E/LocSvc_utils_ll( 576): D/linked_list_remove: Removing from list
E/LocSvc_utils_q( 576): D/msg_q_rcv: Received message 0x7211D6A8 rv = 0
E/LocSvc_eng( 576): D/void loc_eng_deferred_action_thread(void*):1415] received msg_id = LOC_ENG_MSG_INJECT_LOCATION context = 0x729d36f0
E/LocSvc_api_v02( 576): I/---> locClientSendReq line 2084 QMI_LOC_INJECT_POSITION_REQ_V02
E/LocSvc_utils_q( 576): D/msg_q_snd: Finished Sending message with handle = 0x7211D6A8
D/QMI_FW ( 576): QCCI: QMI_CCI_TX: cntl_flag - 00, txn_id - 0069, msg_id - 0039, msg_len - 0021
D/QMI_FW ( 576): QCCI: QMUXD: xport_send[1 -> 16]: 40 bytes on conn_id=9
D/QMI_FW ( 576): QCCI: QMUXD: xport_rx[1 <- 16]: 14 bytes on conn_id: 9
D/QMI_FW ( 576): QCCI: QMI_CCI_RX: cntl_flag - 02, txn_id - 0069, msg_id - 0039, msg_len - 0007
E/LocSvc_adapter( 576): I/<--- void globalRespCb(locClientHandleType, uint32_t, locClientRespIndUnionType, void*) line 115 QMI_LOC_INJECT_POSITION_REQ_V02
E/LocSvc_api_v02( 576): D/loc_free_slot:298]: freeing slot 0
E/LocSvc_eng( 576): D/void loc_eng_deferred_action_thread(void*):1402] 414 listening ...
E/LocSvc_utils_q( 576): D/msg_q_rcv: Waiting on message
D/QMI_FW ( 576): QCCI: QMUXD: xport_rx[1 <- 16]: 14 bytes on conn_id: 9
D/QMI_FW ( 576): QCCI: QMI_CCI_RX: cntl_flag - 04, txn_id - 0000, msg_id - 0039, msg_len - 0007

This series of events fires every single time the screen is turned on. I can guarantee that Google Now, Network Location Reporting, and Network Location History have all been turned off on my phone. Does anyone have any insight on why this series of events (many of which are Errors if the E/ designation is to be believed) is firing on every screen on?

Thanks,

-GP