Post Reply

[Bug report] Nexus 4 wake up screen lag when streaming Bluetooth audio

OP Outrager

12th February 2014, 06:20 AM   |  #1  
OP Senior Member
Thanks Meter: 47
 
375 posts
Join Date:Joined: Jun 2012
After awhile while streaming audio with the Pocket Casts app (probably happens with all audio apps but i only use Pocket casts) over Bluetooth there is a delay turning on the screen. When I press the power button the screen is black but the backlight is on. After a few seconds, sometimes up to 6-7 seconds, the lock screen image will appear and let me swipe to unlock my phone. Changing to no lock screen doesn't fix it.
Turning off Bluetooth or stopping the audio does not fix the problem once it occurs. Only solution seems to be a reboot (and maybe waiting an hour or more but not positive).

Nexus 4 with OmniROM ROM and kernel. Happens on both Dalvik and ART. Latest nightly Feb 9, 2014 and also noticed it in previous week of nightlies.

Update: This only occurs if I manually sleep the display with the power button. If I let the display timeout and go to sleep automatically then the screen turns on instantly like normal.
Last edited by Outrager; 13th February 2014 at 02:04 PM.
12th February 2014, 05:20 PM   |  #2  
Senior Recognized Developer
Flag Owego, NY
Thanks Meter: 24,467
 
13,347 posts
Join Date:Joined: Aug 2007
Donate to Me
More
Quote:
Originally Posted by Outrager

After awhile while streaming audio with the Pocket Casts app (probably happens with all audio apps but i only use Pocket casts) over Bluetooth there is a delay turning on the screen. When I press the power button the screen is black but the backlight is on. After a few seconds, sometimes up to 6-7 seconds, the lock screen image will appear and let me swipe to unlock my phone. Changing to no lock screen doesn't fix it.
Turning off Bluetooth or stopping the audio does not fix the problem once it occurs. Only solution seems to be a reboot (and maybe waiting an hour or more but not positive).

Nexus 4 with OmniROM ROM and kernel. Happens on both Dalvik and ART. Latest nightly Feb 9, 2014 and also noticed it in previous week of nightlies.

1) Bug reports belong on JIRA
2) Unless a developer can reproduce the issue, we can't do anything without a logcat and (in this case) kernel dmesg.
12th February 2014, 05:21 PM   |  #3  
OP Senior Member
Thanks Meter: 47
 
375 posts
Join Date:Joined: Jun 2012
Quote:
Originally Posted by Entropy512

1) Bug reports belong on JIRA
2) Unless a developer can reproduce the issue, we can't do anything without a logcat and (in this case) kernel dmesg.

Sorry, I saw a few other bug report threads so I assumed they go here.
Can you tell me what JIRA is? I'll have to look up how to logcat and get a kernel dmesg.
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes