search

drbf / texasice-cream-sandwich-mirror

Automatically exported from code.google.com/p/texasice-cream-sandwich-mirror
0 stars 0 forks source link

Uncaught exception while waking up the phone from sleep #3

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Wake the phone up from sleep either using power button or track ball
2. Follow exception will be displayed in logcat

What is the expected output? What do you see instead?

What version of the product are you using?
Evervolv-Perdo-2.1.0p5

Logcat and/or dmesg output.

 java.lang.ArrayIndexOutOfBoundsException: length=5; index=6
    at com.android.internal.os.BatteryStatsImpl.updateAllPhoneStateLocked(BatteryStatsImpl.java:1907)
    at com.android.internal.os.BatteryStatsImpl.notePhoneSignalStrengthLocked(BatteryStatsImpl.java:1937)
    at com.android.server.am.BatteryStatsService.notePhoneSignalStrength(BatteryStatsService.java:211)
    at com.android.server.TelephonyRegistry.broadcastSignalStrengthChanged(TelephonyRegistry.java:564)
    at com.android.server.TelephonyRegistry.notifySignalStrength(TelephonyRegistry.java:325)
    at com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact(ITelephonyRegistry.java:95)
    at android.os.Binder.execTransact(Binder.java:338)
    at dalvik.system.NativeStart.run(Native Method)

Please provide any additional information below.

Original issue reported on code.google.com by shahr...@gmail.com on 18 Jan 2012 at 9:53

GoogleCodeExporter commented 8 years ago 
This has to do with the sixbar signal. It should be resolved in p6. can anyone 
confirm this?

Original comment by dr3wsuth...@gmail.com on 20 Jan 2012 at 4:39

GoogleCodeExporter commented 8 years ago 
Used the power button to wake up the phone on Evervolv-Perdo-2.1.0p6:

logcat
--------- beginning of /dev/log/main
I/power   (  188): *** set_screen_state 1
D/SurfaceFlinger(  125): Screen about to return, flinger = 0xfbd918
D/AK8973  (  132): Compass Start
--------- beginning of /dev/log/system
I/WindowManager(  188): Lock screen displayed!
D/dalvikvm(13349): GC_CONCURRENT freed 461K, 7% free 10107K/10759K, paused 9ms+8
4ms
D/dalvikvm(10479): GC_CONCURRENT freed 474K, 6% free 10197K/10823K, paused 5ms+2
5ms
D/androidNetworkLocationListeners(  341): Still have listener com.google.android
.location.internal.client.NetworkLocationClient$1@41363208
D/androidNetworkLocationListeners(  341): Still have listener com.google.android
.location.internal.client.NetworkLocationClient$1@41363208
D/androidNetworkLocationListeners(  341): Still have listener com.google.android
.location.internal.client.NetworkLocationClient$1@41363208
D/dalvikvm(  341): GC_CONCURRENT freed 459K, 6% free 10581K/11207K, paused 3ms+3
ms
I/power   (  188): *** set_screen_state 0
D/dalvikvm(  188): GC_FOR_ALLOC freed 2315K, 26% free 19401K/26183K, paused 125m
s
D/SurfaceFlinger(  125): About to give-up screen, flinger = 0xfbd918
E/libEGL  (  125): validate_display:188 error 3008 (EGL_BAD_DISPLAY)
D/AK8973  (  132): Compass CLOSE
V/TransportControlView(  188): Create TCV com.android.internal.widget.TransportC
ontrolView@418c2f48
W/IInputConnectionWrapper(  188): getExtractedText on inactive InputConnection
W/IInputConnectionWrapper(  188): getExtractedText on inactive InputConnection
W/IInputConnectionWrapper(  188): beginBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(  188): endBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(  188): getExtractedText on inactive InputConnection
W/IInputConnectionWrapper(  188): beginBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(  188): endBatchEdit on inactive InputConnection
W/IInputConnectionWrapper(  188): getExtractedText on inactive InputConnection
I/power   (  188): *** set_screen_state 1
D/SurfaceFlinger(  125): Screen about to return, flinger = 0xfbd918
D/AK8973  (  132): Compass Start
I/WindowManager(  188): Lock screen displayed!

Original comment by kai.kalt...@gmail.com on 20 Jan 2012 at 7:47

GoogleCodeExporter commented 8 years ago 
[quote]It should be resolved in p6. can anyone confirm this?[/quote]

I can confirm that i can not reproduce this issue with p6 - doesn't matter how 
hard/often i try.

Original comment by eyecatchup@gmail.com on 20 Jan 2012 at 9:42

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
good enough for me

Original comment by dr3wsuth...@gmail.com on 24 Jan 2012 at 7:50