Samsung screen does not auto lock and screen does not sleep; help with BBS log - Galaxy Note II Q&A, Help & Troubleshooting

Hello,
I have a Samsung Galaxy Note 2, GT-N7108.
I have been using it for over a year with out problems. Since last couple of weeks the problem of phone screen started. Screen would not go to sleep even though I press the sleep button, it would wake up immediately. It would keep doing that for ever. I read all the answers related to this problem on internet and tried all, the problem disappeared shortly but it reappeared. Due the screen being constantly switched on the battery drains very fast!
I clean installed the OS, I cleared the cache partition, changed several settings on the phone, finally I seek your help by posting the Better Battery Stats log file. I will be glad to answer your questions, thank you in advance for the help! I really appreciate that.
Let me know if you see something with the BBS log dump file below:
Code:
===================
General Information
===================
BetterBatteryStats version: 2.1.0.0
Creation Date: 2016-01-20 05:13:54
Statistic Type: Unplugged to Current
Since 5 h 47 m 49 s
VERSION.RELEASE: 4.3
BRAND: samsung
DEVICE:
MANUFACTURER: samsung
MODEL: GT-N7108
OS.VERSION: 3.0.31-2848223
BOOTLOADER: N7108ZMUEOI3
HARDWARE:
FINGERPRINT:
ID:
TAGS: release-keys
USER:
PRODUCT:
RADIO:
Rooted: true
SELinux Policy: Enforcing
BATTERY_STATS permission granted: true
XPosed BATTERY_STATS module enabled: false
============
Battery Info
============
Level lost [%]: Bat.: -63%(66% to 3%) [10.9%/h]
Voltage lost [mV]: (3861-3589) [47.0%/h]
===========
Other Usage
===========
Awake (Screen Off) (): 47 s 0.2%
Screen On (): 5 h 47 m 49 s 100.0%
Screen dark (): 5 h 47 m 49 s 100.0%
======================================================
Wakelocks (requires root / system app on Android 4.4+)
======================================================
RILJ (Phone): 2 m 22 s Count:4189 0.7%
AlarmManager (Android System): 1 m 23 s Count:2998 0.4%
ActivityManager-Sleep (Android System): 1 m 11 s Count:5346 0.3%
TimaService (Android System): 48 s Count:3105 0.2%
NfcService:mRoutingWakeLock (com.android.nfc.Nfc Service): 20 s Count:2438 0.1%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats.BetterBatteryStats): 13 s Count:6 0.1%
AudioOut_2 (1013): 8 s Count:2 0.0%
WifiSuspend (Android System): 1 s Count:4028 0.0%
================
Kernel Wakelocks
================
"battery-update" (): Cnt:(c/wc/ec)45/0/45 0.0%
"unknown_wakeups" (): Cnt:(c/wc/ec)1/0/1 0.0%
"PowerManagerService.Broadcasts" (): Cnt:(c/wc/ec)1293/0/0 0.0%
"sync_system" (): Cnt:(c/wc/ec)1303/0/0 0.0%
"PowerManagerService.Display" (): Cnt:(c/wc/ec)631/0/0 0.0%
======================================================
Processes (requires root / system app on Android 4.4+)
======================================================
system (Android System): Uid: 1000 Sys: 27 s Us: 60 s Starts: 0
surfaceflinger (Android System): Uid: 1000 Sys: 12 s Us: 2 s Starts: 0
sensorhubservice (Android System): Uid: 1000 Sys: 5 s Us: Starts: 0
mc_fastcall (0): Uid: 0 Sys: 4 s Us: Starts: 0
com.asksven.betterbatterystats (com.asksven.betterbatterystats.BetterBatteryStats): Uid: 10151 Sys: 1 s Us: 3 s Starts: 0
com.sec.android.app.launcher (UID): Uid: 10103 Sys: Us: 2 s Starts: 0
com.android.systemui (com.android.systemui.System UI): Uid: 10136 Sys: Us: 2 s Starts: 0
su (com.asksven.betterbatterystats.BetterBatteryStats): Uid: 10151 Sys: 2 s Us: Starts: 0
com.android.phone (Phone): Uid: 1001 Sys: Us: 1 s Starts: 0
mmcqd/0 (0): Uid: 0 Sys: 2 s Us: Starts: 0
gpsd (1021): Uid: 1021 Sys: 2 s Us: Starts: 0
kworker/0:4 (0): Uid: 0 Sys: 2 s Us: Starts: 0
daemonsu:10151 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/0:0 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/0:2 (0): Uid: 0 Sys: 1 s Us: Starts: 0
com.sec.android.widgetapp.alarmclock (com.sec.android.widgetapp.alarmclock.Simple Alarm Clock): Uid: 10130 Sys: Us: 1 s Starts: 1
kworker/0:3 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/0:1 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:0 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:1 (0): Uid: 0 Sys: Us: Starts: 0
com.sec.android.app.clockpackage (com.sec.android.app.clockpackage.Clock): Uid: 10020 Sys: Us: Starts: 1
com.sec.android.app.keyguard (com.sec.android.app.keyguard.com.sec.android.app.keyguard): Uid: 10061 Sys: Us: Starts: 12
com.sec.android.widgetapp.digitalclock (com.sec.android.widgetapp.digitalclock.Clock (digital)): Uid: 10025 Sys: Us: Starts: 12
rild (Phone): Uid: 1001 Sys: Us: Starts: 0
com.samsung.inputmethod (Android System): Uid: 1000 Sys: Us: Starts: 1
kworker/u:2 (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:26 (0): Uid: 0 Sys: Us: Starts: 0
com.sec.android.widgetapp.activeapplicationwidget (com.sec.android.widgetapp.activeapplicationwidget.Active Apps Manager): Uid: 10107 Sys: Us: Starts: 2
kworker/u:3 (0): Uid: 0 Sys: Us: Starts: 0
com.android.nfc (com.android.nfc.Nfc Service): Uid: 1027 Sys: Us: Starts: 1
mediaserver (1013): Uid: 1013 Sys: Us: Starts: 0
zygote (0): Uid: 0 Sys: Us: Starts: 0
com.sec.android.favoriteappwidget (com.sec.android.favoriteappwidget.Favorite Apps): Uid: 10108 Sys: Us: Starts: 2
kworker/u:4 (0): Uid: 0 Sys: Us: Starts: 0
jbd2/mmcblk0p16 (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:29 (0): Uid: 0 Sys: Us: Starts: 0
com.sec.android.widgetapp.favoriteswidget (UID): Uid: 10103 Sys: Us: Starts: 2
com.kingouser.com (com.kingouser.com.SuperUser): Uid: 10149 Sys: Us: Starts: 12
com.wsdm (Android System): Uid: 1000 Sys: Us: Starts: 12
servicemanager (Android System): Uid: 1000 Sys: Us: Starts: 0
kworker/0:5 (0): Uid: 0 Sys: Us: Starts: 0
com.samsung.android.providers.context (com.samsung.android.providers.context.ContextProvider): Uid: 10021 Sys: Us: Starts: 1
com.android.mms (com.android.mms.Messaging): Uid: 10121 Sys: Us: Starts: 1
com.sec.android.widgetapp.dualclockanalog (com.sec.android.widgetapp.dualclockanalog.Dual Clock (analog)): Uid: 10033 Sys: Us: Starts: 2
com.sec.android.app.SPenKeeper (com.sec.android.app.SPenKeeper.SPenKeeper): Uid: 10101 Sys: Us: Starts: 12
com.android.email (com.android.email.Email): Uid: 10115 Sys: Us: Starts: 1
com.android.contacts (Android Core Apps): Uid: 10008 Sys: Us: Starts: 1
com.wssyncmldm (Android System): Uid: 1000 Sys: Us: Starts: 12
/init (0): Uid: 0 Sys: Us: Starts: 0
s3c-fb (0): Uid: 0 Sys: Us: Starts: 0
flush-179:0 (0): Uid: 0 Sys: Us: Starts: 0
s3c-fb-vsync (0): Uid: 0 Sys: Us: Starts: 0
======================
Alarms (requires BATTERY_STATS permissions)
======================
android (): Wakeups: 1323 (3.8 / min)
Alarms: 0, Intent: android.intent.action.TIME_TICK
Alarms: 1313, Intent: com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD
Alarms: 0, Intent: NETWORK_STAT_LRU
Alarms: 0, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 11, Intent: android.appwidget.action.APPWIDGET_UPDATE cmp={com.sec.android.widgetapp.favoriteswidget/com.sec.android.widgetapp.favoriteswidget.SeniorFavoriteWidgetProviderSmall}
Alarms: 0, Intent: edm.intent.action.elm.cleanrecords
Alarms: 0, Intent: com.android.server.NetworkTimeUpdateService.action.POLL
Alarms: 0, Intent: com.android.internal.policy.impl.Keyguard.LANDSCAPE_WAKE_TIME_LIMIT_EXPIRED
com.sec.spp.push (): Wakeups: 5 (0.9 / h)
Alarms: 5, Intent: {com.sec.spp.push/com.sec.spp.push.notisvc.alarm.AlarmEventManager}
com.sec.esdk.elm (): Wakeups: 1 (0.2 / h)
Alarms: 1, Intent: com.sec.esdk.elm.alarm.SAVE_APICALLLOG
======================
Network (requires root)
======================
0 (Mobile) (0): 2.0 MBytes 50.0%
1021 (Mobile) (1021): 2.0 MBytes 50.0%
==========
CPU States
==========
1.6 GHz (): 12 m 7 s 3.5%
1.5 GHz (): 9 s 0.0%
1.4 GHz (): 1 m 8 s 0.3%
1.3 GHz (): 12 s 0.1%
1.2 GHz (): 23 s 0.1%
1.1 GHz (): 1 m 34 s 0.5%
1 GHz (): 16 s 0.1%
900 MHz (): 11 s 0.1%
800 MHz (): 8 m 2.3%
700 MHz (): 31 s 0.1%
600 MHz (): 16 s 0.1%
500 MHz (): 7 m 51 s 2.3%
200 MHz (): 5 h 18 m 37 s 91.6%
========
Services
========
Active since: The time when the service was first made active, either by someone starting or binding to it.
Last activity: The time when there was last activity in the service (either explicit requests to start it or clients binding to it)
See
com.android.phone (com.android.phone.TelephonyDebugService)
Active since: 16 s
Last activity: 16 s
Crash count:0
system (com.android.server.DrmEventService)
Active since: 23 s
Last activity: 23 s
Crash count:0
com.sec.spp.push (com.sec.spp.push.PushClientService)
Active since: 27 s
Last activity: 5 h 32 m 15 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.pan.PanService)
Active since: 14 s
Last activity: 4 h 30 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.btservice.AdapterService)
Active since: 13 s
Last activity: 18 s
Crash count:0
com.tencent.engine (com.tencent.engine.InterceptEngineService)
Active since: 20 s
Last activity: 29 s
Crash count:0
com.sec.android.app.keyguard (com.sec.android.app.keyguard.KeyguardClockWidgetService)
Active since: 60 s
Last activity: 5 h 33 m 49 s
Crash count:0
com.sec.android.widgetapp.digitalclock (com.sec.android.widgetapp.digitalclock.DigitalClockService)
Active since: 28 s
Last activity: 5 h 32 m 48 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.a2dp.A2dpService)
Active since: 19 s
Last activity: 19 s
Crash count:0
com.android.systemui (com.android.systemui.SystemUIService)
Active since: 15 s
Last activity: 15 s
Crash count:0
com.baidu.map.location (com.baidu.map.location.BaiduNetworkLocationService)
Active since: 15 s
Last activity: 15 s
Crash count:0
com.policydm (com.policydm.ObserverService)
Active since: 25 s
Last activity: 5 h 33 m 4 s
Crash count:0
com.samsung.inputmethod (com.samsung.inputmethod.SamsungIME)
Active since: 23 s
Last activity: 23 s
Crash count:0
com.android.phone (com.sec.enterprise.mdm.services.simpin.EnterpriseSimPin)
Active since: 16 s
Last activity: 16 s
Crash count:0
com.samsung.android.providers.context (com.samsung.android.providers.context.ContextService)
Active since: 24 s
Last activity: 24 s
Crash count:0
com.android.phone (com.sec.android.app.bluetoothtest.BluetoothBDTestService)
Active since: 23 s
Last activity: 23 s
Crash count:0
com.samsung.inputmethod (com.samsung.inputmethod.service.xt9.SimeDecoderService)
Active since: 23 s
Last activity: 23 s
Crash count:0
com.android.systemui (com.android.systemui.ImageWallpaper)
Active since: 15 s
Last activity: 15 s
Crash count:0
com.sec.android.widgetapp.alarmclock (com.sec.android.widgetapp.alarmclock.ClockAlarmWidgetService)
Active since: 22 s
Last activity: 28 s
Crash count:0
com.android.phone (com.android.phone.BluetoothPhoneService)
Active since: 16 s
Last activity: 16 s
Crash count:0
com.sec.knox.seandroid (com.sec.knox.seandroid.service.SEAndroidLauncher)
Active since: 25 s
Last activity: 25 s
Crash count:0
com.tencent.engine (com.tencent.engine.DemoSecureService)
Active since: 20 s
Last activity: 20 s
Crash count:0
com.sec.esdk.elm (com.sec.esdk.elm.service.ElmAgentService)
Active since: 24 s
Last activity: 5 h 44 m 59 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.pbap.BluetoothPbapService)
Active since: 18 s
Last activity: 18 s
Crash count:0
system (com.android.location.fused.FusedLocationService)
Active since: 15 s
Last activity: 15 s
Crash count:0
com.android.phone (com.android.phone.BluetoothVoIPService)
Active since: 16 s
Last activity: 16 s
Crash count:0
com.baidu.map.location (com.baidu.location.f)
Active since: 15 s
Last activity: 15 s
Crash count:0
com.wssyncmldm (com.wssyncmldm.XDMService)
Active since: 27 s
Last activity: 5 h 33 m 33 s
Crash count:0
com.sec.knox.eventsmanager (com.sec.knox.eventsmanager.ContainerEventsRelayManager)
Active since: 15 s
Last activity: 15 s
Crash count:0
org.simalliance.openmobileapi.service:remote (org.simalliance.openmobileapi.service.SmartcardService)
Active since: 15 s
Last activity: 26 s
Crash count:0
com.asksven.betterbatterystats (com.asksven.betterbatterystats.services.EventWatcherService)
Active since: 27 s
Last activity: 5 h 51 m 13 s
Crash count:0
com.wsdm (com.wsdm.DMService)
Active since: 27 s
Last activity: 5 h 33 m 17 s
Crash count:0
system (com.sec.knox.containeragent.service.notification.EnterpriseNotificationCenter)
Active since: 24 s
Last activity: 25 s
Crash count:0
com.sec.android.pagebuddynotisvc (com.sec.android.pagebuddynotisvc.PageBuddyNotiSvc)
Active since: 25 s
Last activity: 25 s
Crash count:0
com.android.phone (com.samsung.sec.android.application.csc.CscUpdateService)
Active since: 23 s
Last activity: 30 s
Crash count:0
com.kingouser.com (com.kingouser.com.service.RunningService)
Active since: 23 s
Last activity: 5 h 33 m 59 s
Crash count:0
com.android.phone (com.android.stk.StkAppService)
Active since: 26 s
Last activity: 26 s
Crash count:0
com.android.nfc:handover (com.android.nfc.handover.HandoverService)
Active since: 15 s
Last activity: 15 s
Crash count:0
com.sec.android.app.SPenKeeper (com.sec.android.app.SPenKeeper.SPenKeeperService)
Active since: 25 s
Last activity: 5 h 32 m
Crash count:0
system (android.hardware.location.GeofenceHardwareService)
Active since: 15 s
Last activity: 15 s
Crash count:0
com.sec.phone (com.sec.phone.SecPhoneServiceCPOnUPG)
Active since: 23 s
Last activity: 5 h 32 m 32 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.hfp.HeadsetService)
Active since: 16 s
Last activity: 19 s
Crash count:0
==================
Reference overview
==================
ref_unplugged: Reference ref_unplugged created 7 m 54 s (Wl: 8 elements; KWl: 17elements; NetS: 2 elements; Alrm: 3 elements; Proc: 9 elements; Oth: 5 elements; CPU: 14 elements)
ref_custom: Reference ref_custom created 12 m 13 s (Wl: 9 elements; KWl: 17elements; NetS: 2 elements; Alrm: 3 elements; Proc: 12 elements; Oth: 5 elements; CPU: 14 elements)
ref_current: Reference ref_current created 5 h 55 m 44 s (Wl: 11 elements; KWl: 11elements; NetS: 2 elements; Alrm: 4 elements; Proc: 52 elements; Oth: 4 elements; CPU: 14 elements)

Related

HTC Diamond - stock - 1.34.831.1 - ROM - WWE

http://uploaded.to/?id=ma0u71 - HTC Diamond - stock - 1.34.831.1 - ROM - WWE
Enjoy
tupisdin said:
http://uploaded.to/?id=ma0u71 - HTC Diamond - stock - 1.34.831.1 - ROM - WWE
Enjoy
Click to expand...
Click to collapse
anyone have an rapidshare link? uploaded.to blows...
What's the core?
19585? not 19581
Core 19588.
kewl thnks PhamQuang bro
SYS: 5.2.19581.1101 -> \SYS(LANG)\Autoupdate_Lang_0409\89fc53c1-ec65-4648-9972-24afb3dcad3c.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\Base_Lang_0409_DPI_192\5cad3bed-e21d-4768-a965-5e359d6d32b8.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\Bluetooth_Lang_0409\ba94b89b-3bb8-4f41-bada-121dbdab1fde.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\Browsing_Lang_0409\f65c1b88-2732-470a-88c8-de964e9f9ca7.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\Bth_A2DP_Lang_0409\9ca8818d-8eec-479d-a9be-81305c52d303.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\Bth_HID_Lang_0409\c9b03c4a-50ff-4e86-b92f-2eb3f9968eb3.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\Catalog_Lang_0409\33ee5583-5698-4cc4-bc01-47743f5cc5cd.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\Enterprise_Lang_0409\abf26ee8-18d2-42c7-b355-1ff0d582d792.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\Enterprise_Lang_0409_DPI_192\0a50114c-65c7-4b33-b2e1-490070653abf.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\Entertainment_Lang_0409\2401a89d-1c1a-448a-b204-051d1866e37f.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\Entertainment_Lang_0409_DPI_192\1ff5ad39-05ff-4fed-8797-1b94b62dbd40.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\Fwupdate_Lang_0409\141bf632-56d3-4f0b-a808-c2fd1f40065d.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\IPSECVPN_Lang_0409\0ebf993d-b6af-4a12-b6da-fceb49c9690b.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\MediaOS_Lang_0409\71da3033-fae4-442a-9fc6-8182fd7b974f.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\Office_Lang_0409\6226602c-2ba3-40bf-83e4-ea9173088ac9.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\Office_Lang_0409_DPI_192\2c656d9c-d8a3-4a5c-93b8-57d13b5dbaa6.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\OneNote_lang_0409\d83b7202-2af0-4199-af12-d073bc63732f.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\Phone_Lang_0409\25f4da29-9280-48e9-8f2e-28a91294ce74.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\Phone_Lang_0409_DPI_192\5e1147c6-380d-467e-a646-2f8e63d6b1a8.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\PhoneRedist_Lang_0409\70bf28e9-b87c-4b43-be51-e804d08276b1.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\PhoneRedist_Lang_0409_DPI_192\37d983b9-32ef-4b74-ad2d-4bf227434aca.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\Redist_Lang_0409\12e09329-dd44-4d62-a5b7-25124bb2ef88.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\Redist_Lang_0409_DPI_192\41ae8aba-7577-4c7f-bede-7ec53105498f.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\RemoteDesktopMobile_Lang_0409\b58170c7-67d4-4f57-af5b-a4134867f4d4.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\SqlCeMobile_Lang_0409\90f7cab5-db46-4341-b395-7aca3d47055c.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\Transcriber_Lang_0409\5f9ca691-2a85-4db5-b6a0-ce35ef2618dc.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\Transcriber_Lang_0409_DPI_192\ed78a746-d604-478b-a359-dbbbf88fa1f8.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\WelcomeCenter_Lang_0409\37ed0d5d-7978-4dcf-b3f9-2768426fb1bf.dsm
SYS: 5.2.19581.1101 -> \SYS(LANG)\WindowsLive_Lang_0409\6949fb3f-d582-4e5d-9d11-15f960afc045.dsm
SYS: 5.2.19581.1101 -> \SYS\AUTOUPDATE\8be73c02-3437-4c06-88c9-0a2e25bfaf2c.dsm
SYS: 5.2.19581.1101 -> \SYS\base_dpi_192_resh_480_resv_640\4e453988-2990-4f66-8d21-b1e375182c7e.dsm
SYS: 5.2.19581.1101 -> \SYS\Browsing_DPI_192\31851e81-cb8e-4508-b36b-64706380c16a.dsm
SYS: 5.2.19581.1101 -> \SYS\Bth_HID\a492bb92-210b-4933-9a65-272cc8ad9a5b.dsm
SYS: 5.2.19581.1101 -> \SYS\CommonNonEA\7bb5f499-6b7f-4ee0-bcb9-a89ae3fc3e2c.dsm
SYS: 5.2.19581.1101 -> \SYS\DRM\29306538-2ad1-42a5-8414-502a65277eb5.dsm
SYS: 5.2.19581.1101 -> \SYS\Enterprise\fd7ec796-412f-4352-9a71-04da841dc265.dsm
SYS: 5.2.19581.1101 -> \SYS\Enterprise_DPI_192\297557a9-7937-47c0-a5dc-ca70ac0d3492.dsm
SYS: 5.2.19581.1101 -> \SYS\Entertainment\0cfc3dc0-5fbc-4153-9ce9-72df4d8c2922.dsm
SYS: 5.2.19581.1101 -> \SYS\Entertainment_DPI_192\1f037daf-1ebb-49ff-b6b8-9e3bda1bcbb7.dsm
SYS: 5.2.19581.1101 -> \SYS\FWUPDATE\23ba5346-78b8-4436-b7d2-f30712c3cef4.dsm
SYS: 5.2.19581.1101 -> \SYS\GPSID\d13b7447-0248-462a-bba4-d868f31642ed.dsm
SYS: 5.2.19581.1101 -> \SYS\INTERNETSHARING\ed0ab1a4-a456-4fb0-ad9d-93feccf351a3.dsm
SYS: 5.2.19581.1101 -> \SYS\IPSECVPN\429b237a-cc04-4166-a65b-5cd54a4f1b7d.dsm
SYS: 5.2.19581.1101 -> \SYS\IPSECVPN_DPI_192\4a84adf3-cb38-4e3d-9ee9-19efad6958e5.dsm
SYS: 5.2.19581.1101 -> \SYS\MediaOS_dpi_192_resh_480_resv_640\59340c3c-b30c-438d-8128-0c0e14c18866.dsm
SYS: 5.2.19581.1101 -> \SYS\Office_DPI_192\9510f529-0d35-4218-8d8d-a5fb34b6ab25.dsm
SYS: 5.2.19581.1101 -> \SYS\OneNote\2f863e61-941d-4fb6-bcdf-35bf606e613a.dsm
SYS: 5.2.19581.1101 -> \SYS\Phone_DPI_192\9e13ae76-4e06-4a04-8d8a-42ac632cab1c.dsm
SYS: 5.2.19581.1101 -> \SYS\Phone_dpi_192_resh_480_resv_640\77eb8dac-ca45-480e-aca3-bb6db056ea56.dsm
SYS: 5.2.19581.1101 -> \SYS\PhoneRedist_DPI_192\2a9e3618-ebed-4b3d-b501-a0baa6742283.dsm
SYS: 5.2.19581.1101 -> \SYS\ppgprov\7562ae5a-418d-4b4b-ae27-5bd29dfd9393.dsm
SYS: 5.2.19581.1101 -> \SYS\Redist_dpi_192_resh_480_resv_640\9b1b925a-6f1f-47d2-92d0-140632d19135.dsm
SYS: 5.2.19581.1101 -> \SYS\SampleMusic\7949cb6e-e0ad-41ec-b61f-f1aa4f6b122e.dsm
SYS: 5.2.19581.1101 -> \SYS\SIM_TKit\1dc3da02-499f-4547-9fd2-78cddfda9c62.dsm
SYS: 5.2.19581.1101 -> \SYS\SMIME\8cb4ac12-6bc5-4bda-ab45-539988c36a95.dsm
SYS: 5.2.19581.1101 -> \SYS\SMS_Providers\582f7a58-3c50-4301-970a-ed5ec8947692.dsm
SYS: 5.2.19581.1101 -> \SYS\SQLCE\8a1287c3-da0a-4eb8-8ba7-b70019890abb.dsm
SYS: 5.2.19581.1101 -> \SYS\SqlCeMobile\29356830-10de-437d-ad6a-6c7d60a7dea4.dsm
SYS: 5.2.19581.1101 -> \SYS\SQM\76bd787c-86b5-4b63-a1d8-1a910f86c8e1.dsm
SYS: 5.2.19581.1101 -> \SYS\Transcriber\60fa7e75-fb9b-45c0-b99c-16d9182e9f72.dsm
SYS: 5.2.19581.1101 -> \SYS\WindowsLive_DPI_192\f0326319-2644-4c54-8e69-2c1d84d767b7.dsm
SYS: 5.2.19581.1101 -> \SYS\WWAN\77f38251-db87-4e5d-96d9-9e8e35b6dc1d.dsm
SYS: 5.2.19588.1104 -> \SYS(LANG)\Base_Lang_0409\813fd1d1-ca6f-4b6d-96d2-c97fb99bd535.dsm
SYS: 5.2.19588.1104 -> \SYS(LANG)\Base_Lang_0409_DPI_192_RESH_480_RESV_640\e3f1876e-2ebd-4a41-bcc1-0fbfadb15c44.dsm
SYS: 5.2.19588.1104 -> \SYS\Base_DPI_192\86311d83-c59a-4fa7-9eec-c19dd059f21b.dsm
SYS: 5.2.19588.1104 -> \SYS\BaseApps\f50e9a40-aed9-497a-bdea-84451210e960.dsm
SYS: 5.2.19588.1104 -> \SYS\BaseAppsFiles\b04e8c7f-f0f6-4201-83c6-4876404128c9.dsm
SYS: 5.2.19588.1104 -> \SYS\Bluetooth\25c125d4-0a18-487d-a709-9b4242bbf4c3.dsm
SYS: 5.2.19588.1104 -> \SYS\BROWSING\b183f2a7-06c3-4f27-9679-7baf97e94efa.dsm
SYS: 5.2.19588.1104 -> \SYS\BROWSINGCORE\d81b11e0-3299-4b65-8305-78f1fa03dc07.dsm
SYS: 5.2.19588.1104 -> \SYS\BTDUN\d7904a7e-6226-443b-8c8c-439683b0b55a.dsm
SYS: 5.2.19588.1104 -> \SYS\Bth_A2DP\6b4ed31c-5ced-41b2-b917-2c006f046a5e.dsm
SYS: 5.2.19588.1104 -> \SYS\Catalog\e4200be3-87fc-4415-9a57-d96456c4ba10.dsm
SYS: 5.2.19588.1104 -> \SYS\MediaOS\ae879543-c73e-4888-812b-d8177c404612.dsm
SYS: 5.2.19588.1104 -> \SYS\MediaOSFiles\da5e9e89-c2c4-4ff9-ae88-c90a50ec09c9.dsm
SYS: 5.2.19588.1104 -> \SYS\Office\331439cf-a636-4243-8424-e501be3a39d2.dsm
SYS: 5.2.19588.1104 -> \SYS\OS\d0b41563-b345-4444-aa15-986e7c7fff99.dsm
SYS: 5.2.19588.1104 -> \SYS\OSFiles\b51fcecc-a738-463b-93a4-7b44d03c30b7.dsm
SYS: 5.2.19588.1104 -> \SYS\Phone\2a6583ff-6047-46cc-b9be-b7deca1152c3.dsm
SYS: 5.2.19588.1104 -> \SYS\PhoneRedist\d9d7d86d-3f83-4289-bd32-aa1972a1447e.dsm
SYS: 5.2.19588.1104 -> \SYS\Redist\208f8be6-1362-45b3-ae17-95d4ab426c11.dsm
SYS: 5.2.19588.1104 -> \SYS\Redist_DPI_192\7815d5a3-2281-4eec-911d-1a924ebf48d5.dsm
SYS: 5.2.19588.1104 -> \SYS\RemoteDesktopMobile\adc19413-37b2-4018-af8a-148b50f6ea13.dsm
SYS: 5.2.19588.1104 -> \SYS\RUNTIMES\e658c544-26bf-45ac-a458-2044a5d1e698.dsm
SYS: 5.2.19588.1104 -> \SYS\Shell\1f1aca24-d942-464a-9281-10567741499c.dsm
SYS: 5.2.19588.1104 -> \SYS\WelcomeCenter\40723732-841f-40d3-8dd0-af7d0d6156de.dsm
SYS: 5.2.19588.1104 -> \SYS\WindowsLive\27790533-c966-4097-8a93-c1a83969c574.dsm
[Language]
0409 - English (United States) -> \SYS(LANG)\Base_Lang_0409\813fd1d1-ca6f-4b6d-96d2-c97fb99bd535.dsm
[DPI]
192 -> \SYS\Base_DPI_192\86311d83-c59a-4fa7-9eec-c19dd059f21b.dsm
can anyone help in guiding on how to port this build SYS to other ppc, like elfin or touch? i tried my hand and it did flash well, but screwed up a few control panel applets and contacts.. got something to do with the MyCPL.cpl and few entries.. hope someone can guide me
How to download
yanghw said:
How to download
Click to expand...
Click to collapse
you dont download it
tupisdin said:
http://uploaded.to/?id=ma0u71 - HTC Diamond - stock - 1.34.831.1 - ROM - WWE
Enjoy
Click to expand...
Click to collapse
thanks bro, already ported this XIP n SYS to Elfin
thanks a lot
2 weeks back, this would have made my day. I wanted to cook my own rom based on diamond. but i got stuck and gave up when my bootloader got screwed
Mirrored this for ya ppls.
Clickety.
Mirror
This is a direct download link: http://rapidshare.com/files/1177086...K_WWE_1.34.831.1_52.24.25.08_0.93.25_Ship.exe
Does it work on HTC Prophet?
German_LuTz said:
Does it work on HTC Prophet?
Click to expand...
Click to collapse
it will.. you will have to port it first
Lot Of Fun!!!!
Thanks now we have a lot of FUN !!! trying to port some of the apps inside this ROM to other devices... I will try to do for trinity... also manila, don´t have so much hope for it to work... but I will try...
Others, like new Camera app, think may work fine... i will try ALL!!! packages!!!
Thanks a lot for sharing.
Thanks tupisdin !
ababrekar said:
can anyone help in guiding on how to port this build SYS to other ppc, like elfin or touch? i tried my hand and it did flash well, but screwed up a few control panel applets and contacts.. got something to do with the MyCPL.cpl and few entries.. hope someone can guide me
Click to expand...
Click to collapse
guys, experts any help here?
Nice release bro
Do you think anyone make an release for htc prophet?

High number of Wakeups-from-idle.

I need a little help. I just ran PowerTOP and my wakeups-from-idle are super high. What can I do to reduce these? I'm currently running Fresh Evo 0.5.3 and everything is great with the exception of pretty poor battery life. I have to think that the high number of W-F-I is the reason, but I am not well versed in Linux or PowerTOP and I'm not sure what I can to to reduce these. On the report there are tips on what can be done, but as I'm not really sure what they mean, they might as well be written in Latin.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BB15 said:
I need a little help. I just ran PowerTOP and my wakeups-from-idle are super high. What can I do to reduce these? I'm currently running Fresh Evo 0.5.3 and everything is great with the exception of pretty poor battery life. I have to think that the high number of W-F-I is the reason, but I am not well versed in Linux or PowerTOP and I'm not sure what I can to to reduce these. On the report there are tips on what can be done, but as I'm not really sure what they mean, they might as well be written in Latin.
Click to expand...
Click to collapse
here is my powertop. Similar prob as you are having....
friggin audiotrack and gp timer.... bastards!!!
Code:
Wakeups-from-idle per second : 722.3 interval: 15.0s
no ACPI power usage estimate available
Top causes for wakeups:
56.1% (392.6) AudioTrackThrea : do_nanosleep (hrtimer_wakeup)
39.6% (277.1) <interrupt> : gp_timer
0.7% ( 5.2) <interrupt> : msm_i2c
0.7% ( 5.1) <interrupt> : msm_hsusb
0.4% ( 3.0) er.ServerThread : schedule_hrtimeout_range (hrtimer_wakeup)
0.3% ( 2.1) WebViewCoreThre : futex_wait (hrtimer_wakeup)
0.3% ( 2.0) rild : __netdev_watchdog_up (dev_watchdog)
Curious too as to what the tweaks are to get it into the 50-80 range.
Mine is at 369.3 with top 2:
34.0% (114.0) <interrupt> : msm_i2c
22.3% ( 75.0) <interrupt> : gp_timer
Are you guys running this while the phone is awake?
If so then that's your problem. Plug your phone into your computer. Adb shell. Put your phone to sleep. Wait 15-20 seconds and run powertop from the shell.
Wakeups should be in the 50-70 range.
That could be the culprit. Will try that out and report back.
nebenezer said:
Are you guys running this while the phone is awake?
If so then that's your problem. Plug your phone into your computer. Adb shell. Put your phone to sleep. Wait 15-20 seconds and run powertop from the shell.
Wakeups should be in the 50-70 range.
Click to expand...
Click to collapse
def not while it's awake. left it for a min before posting my stats....
Hmm, I didn't think about that!
I'll give this a try when I get home and report back.
nebenezer said:
Are you guys running this while the phone is awake?
If so then that's your problem. Plug your phone into your computer. Adb shell. Put your phone to sleep. Wait 15-20 seconds and run powertop from the shell.
Wakeups should be in the 50-70 range.
Click to expand...
Click to collapse
The readings below are after letting it sit for about 30 sec with the screen off.
Edit: Image wouldn't attach, I'm at about 125
Edit2: ran it again and now I'm at about 118
I just plugged my phone in and let it sit for about 5 minutes. Ran PowerTOP and got 156. Better than the 250+ I was getting before, but still more than what Flipz mentioned as "normal". Since the phone is responsive and quick I wonder how much of an issue this actually is. My battery life sucks, but not abnormally so (I get about 10 hours with moderate use).
I had same issue on flipz rom. I went back to damage control and now am 50 or lower my batery life is AMAZING. Something is real wrong with fresh rom.
fallentimm said:
I had same issue on flipz rom. I went back to damage control and now am 50 or lower my batery life is AMAZING. Something is real wrong with fresh rom.
Click to expand...
Click to collapse
I really like Flipz's work with Fresh ROMs, but I may have to give DC a try.
Similar Results here:
C:\android-sdk-windows\tools>adb shell dcpowertop
PowerTOP 1.11 (C) 2007, 2008 Intel Corporation
/sbin/modprobe: not found
Collecting data for 15 seconds
< Detailed C-state information is not available.>
P-states (frequencies)
576 Mhz 0.0%
499 Mhz 0.0%
461 Mhz 0.0%
384 Mhz 0.0%
245 Mhz 100.0%
Wakeups-from-idle per second : 645.3 interval: 15.0s
no ACPI power usage estimate available
Top causes for wakeups:
61.8% (391.3) AudioTrackThrea : do_nanosleep (hrtimer_wakeup)
35.2% (222.9) <interrupt> : gp_timer
0.7% ( 4.2) <interrupt> : msm_hsusb
0.5% ( 3.0) er.ServerThread : schedule_hrtimeout_range (hrtimer_wakeup)
0.3% ( 2.1) er.ServerThread : futex_wait (hrtimer_wakeup)
0.3% ( 2.0) rild : __netdev_watchdog_up (dev_watchdog)
0.3% ( 2.0) SearchDialog : futex_wait (hrtimer_wakeup)
0.2% ( 1.0) m.android.phone : futex_wait (hrtimer_wakeup)
0.2% ( 1.0) <kernel core> : msmsdcc_probe (msmsdcc_check_status)
0.1% ( 0.5) Thread-95 : futex_wait (hrtimer_wakeup)
0.1% ( 0.5) Smack : Packet Wr futex_wait (hrtimer_wakeup)
0.1% ( 0.5) <kernel core> : schedule_delayed_work_on (delayed_work_timer_fn)
0.1% ( 0.4) <kernel core> : neigh_table_init_no_netlink (neigh_periodic_timer)
0.1% ( 0.3) iqfd:tombstone : schedule_hrtimeout_range (hrtimer_wakeup)
0.1% ( 0.3) iqd:cserial : do_nanosleep (hrtimer_wakeup)
0.0% ( 0.2) SurfaceFlinger : do_nanosleep (hrtimer_wakeup)
0.0% ( 0.2) iqfd : schedule_hrtimeout_range (hrtimer_wakeup)
0.0% ( 0.1) ObexHelper : schedule_hrtimeout_range (hrtimer_wakeup)
0.0% ( 0.1) Transaction : futex_wait (hrtimer_wakeup)
0.0% ( 0.1) m.android.phone : sk_reset_timer (tcp_write_timer)
0.0% ( 0.1) er.ServerThread : update_timer_locked (alarm_timer_triggered)
0.0% ( 0.1) <kernel core> : queue_delayed_work (delayed_work_timer_fn)
0.0% ( 0.1) <kernel core> : page_writeback_init (wb_timer_fn)
0.0% ( 0.1) iqd:jjob : schedule_hrtimeout_range (hrtimer_wakeup)
0.0% ( 0.1) iqd:jjob : sk_reset_timer (tcp_delack_timer)
0.0% ( 0.1) iqd:jjob : sk_reset_timer (tcp_write_timer)
xrandr: not found
Suggestion: Enable the CONFIG_HPET_TIMER kernel configuration option.
Without HPET support the kernel needs to wake up every 20 milliseconds for
some housekeeping tasks.
Suggestion: Enable the CONFIG_ACPI_BATTERY kernel configuration option.
This option is required to get power estimages from PowerTOP
Suggestion: Enable the CONFIG_USB_SUSPEND kernel configuration option.
This option will automatically disable UHCI USB when not in use, and may
save approximately 1 Watt of power.
Recent USB suspend statistics
Active Device name
By the way, I am on the latest DamageControl Rom:
C:\android-sdk-windows\tools>adb shell top -n 1 -t
User 3%, System 5%, IOW 0%, IRQ 0%
User 11 + Nice 0 + Sys 19 + Idle 299 + IOW 0 + IRQ 0 + SIRQ 0 = 329
PID TID CPU% S VSS RSS PCY UID Thread Proc
1560 1560 8% R 1028K 544K fg root top top
460 1399 0% S 319696K 53140K fg system AudioTrackThrea system_server
460 1421 0% S 319696K 53140K fg system AudioTrackThrea system_server
460 1456 0% S 319696K 53140K fg system AudioTrackThrea system_server
460 1170 0% S 319696K 53140K fg system SearchDialog system_server
460 1493 0% S 319696K 53140K fg system AudioTrackThrea system_server
7 7 0% S 0K 0K fg root suspend
Ok, so I flashed the latest DC ROM, set it up identical to how I had Fresh EVO 0.5.3 set up and ran a PowerTOP. I came in at 67 wakeups per second. A significant and obvious improvement. Seems the issue may indeed be with the Fresh ROM. Hopefully Flipz can get it figured out and fixed because I really do like his ROMs a lot.
BB15 said:
Ok, so I flashed the latest DC ROM, set it up identical to how I had Fresh EVO 0.5.3 set up and ran a PowerTOP. I came in at 67 wakeups per second. A significant and obvious improvement. Seems the issue may indeed be with the Fresh ROM. Hopefully Flipz can get it figured out and fixed because I really do like his ROMs a lot.
Click to expand...
Click to collapse
Exactly howe things should be. Try batery saver mode in dconfig, I swear by it
I found the culprit on my system: Audible Selection
I was able to turn this off and on several times and recreate the high number of wakes with it on.
Since this is a part of the OS, can anybody recreate this?
MCLFLN said:
I found the culprit on my system: Audible Selection
I was able to turn this off and on several times and recreate the high number of wakes with it on.
Since this is a part of the OS, can anybody recreate this?
Click to expand...
Click to collapse
How do I turn off audible selection?
Nevermind... Found it. It was already off when I posted my results
I was having a problem with my wakes from idle. I returned the phone for screen separation and with my new 003 (previous was an 002) and everything else the same it was down to around 75-85. With the new Fresh 1.0.1 it's down to around 45-55.
ausch30 said:
I was having a problem with my wakes from idle. I returned the phone for screen separation and with my new 003 (previous was an 002) and everything else the same it was down to around 75-85. With the new Fresh 1.0.1 it's down to around 45-55.
Click to expand...
Click to collapse
Got mine knocked down by turning off the sounds in the swype keyboard. My high wake ups was being caused by audio track thread and narrowed it down to swype.
shad0w77 said:
How do I turn off audible selection?
Nevermind... Found it. It was already off when I posted my results
Click to expand...
Click to collapse
How do you turn it off? I'm getting 736 on wake on idle. I turned off all audible sound on swype and all other keyboards.

All GAC/Managed are "Test Signed"

I noticed when going through the GAC_* from the WP7 Emu dump, that ALL have the same signature.
There is a "TEST Cert" applied so they become "trusted" by the phone, or else it just exit the app.
I think this is the certificate that they apply before adding it to marketplace list, that the app gets "OK".
"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\Silverlight\v4.0\Profile\WindowsPhone\Microsoft.Phone.Interop.dll"
Signatures:
Microsoft Code Signing PCA
Microsoft Time-Stamp PCA
Microsoft Time-Stamp Service
Microsoft Corporation
"C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v7.0\Emulation\Images\dump\GAC_Microsoft.Phone.Interop_v7_0_0_0_cneutral_1.dll"
Signatures:
One certificate?
Windows Mobile TCB Test CA (mobile WTF?, is'nt this Windows "Phone")
--->
//****************************************************************************
//Authenticode Signature
This digital signature is not valid.
Digest Algorithm = SHA1
Link Checksum = 0000D5FF
Real Checksum = 0000D5FF
Signed File Hash = B5 58 B3 7E AE 00 1F 68 A3 20 79 A5 E1 4B 90 BD BC 1A D2 17
Real File Hash = B5 58 B3 7E AE 00 1F 68 A3 20 79 A5 E1 4B 90 BD BC 1A D2 17
//****************************************************************************
//****************************************************************************
//Signature Details
//----------------------------------------------------------------------------
//Item 0 (Not available)
This digital signature is not valid.
Name of Signer = Not available
Email Address = Not available
Signing Time = Not available
Version = 2
Issuer = Common Name = Windows Mobile TCB Test CA
Serial Number = AA 5F 33 25 37 24 96 86 4F 18 FE D0 30 94 E7 7D
Digest Algorithm = SHA1 (2B 0E 03 02 1A)
Digest Encryption Algorithm = RSA (2A 86 48 86 F7 0D 01 01 01)
Authenticated Attributes:
1.3.6.1.4.1.311.2.1.12 = 30 00
Content Type = 06 0A 2B 06 01 04 01 82 37 02 01 04
1.3.6.1.4.1.311.2.1.11 = 30 0C 06 0A 2B 06 01 04 01 82 37 02 01 15
Message Digest = 04 14 7E C2 F2 A6 12 C9 44 EE 2F EF C5 05 3F 4B
42 FF BC 23 AF 2E
//****************************************************************************
//****************************************************************************
//Certificate Details
//----------------------------------------------------------------------------
//Item 0 (Windows Mobile TCB Test Signing Cert)
Version = 3
Issued by = Windows Mobile TCB Test CA
Issued to = Windows Mobile TCB Test Signing Cert
Valid from = 1/1/2001 7:00:00 AM
Valid to = 1/1/2039 7:00:00 AM
Issued to:
Common Name = Windows Mobile TCB Test Signing Cert
Issued by:
Common Name = Windows Mobile TCB Test CA
Serial Number = 00 AA 5F 33 25 37 24 96 86 4F 18 FE D0 30 94 E7
7D
Signature Algorithm = SHA1 with RSA
Issuer = Common Name = Windows Mobile TCB Test CA
Valid from = 1/1/2001 7:00:00 AM
Valid to = 1/1/2039 7:00:00 AM
Subject = Common Name = Windows Mobile TCB Test Signing Cert
Size = 864
Signature = 0B 5D 0D 72 A2 43 0D 43 BA 6E EB 88 D9 71 09 27
DF DF 49 E6 8F FB 82 D7 AC 04 BD 22 40 44 C2 3B
3C 89 24 56 5B 2A 1A BE D4 F6 07 82 80 DC 91 24
FA 93 AD D6 11 8C F6 71 65 AC 3E A8 55 72 D1 3D
F5 18 6B 07 80 C6 BA BC B7 CD 9D F8 6A 93 11 B0
7D 2B 9D 3D 09 30 82 59 B2 C2 BF 84 B3 2D 00 C5
99 5C 40 12 90 B7 47 0F 84 3C 3E 14 FF 65 77 DD
91 7E EE 6A 40 1A 4D 93 8A 58 1A 48 25 56 A2 53
7A 89 62 E8 73 C8 E0 E4 EE 20 45 96 C3 4E A3 FB
BD A0 81 05 CB 29 28 5C 18 AD 5E 58 C3 AC 26 55
04 96 3E 5A FD E2 6D 07 A9 DA D7 A5 FB 91 81 F0
8C 8B DF F2 44 67 78 CB D7 93 35 B0 A6 A4 06 5B
A8 29 AC D3 58 1A 36 32 DD D6 64 CE D6 AA 7A 03
50 53 69 F9 57 62 D3 FB AC 6F 54 1F A4 5C 60 5C
6C 6E 33 A7 B6 39 F4 0B B3 B9 7A 71 71 D2 DF CF
DA 6B 92 77 16 97 D1 6F 2F C7 3D 05 BD 9D 90 3D
Self signed = False
Public key = RSA (2056)
RSA Modulus = 00 8E AF 08 1B 5A 81 60 78 84 8B E0 ED 43 75 7D
D1 F4 4C CE 72 07 2C F4 94 2D FA 51 B7 0F 28 CF
60 D5 36 02 7B 89 01 3E D2 26 85 85 F8 2D 18 FF
89 19 23 F3 41 19 77 C7 46 C2 E5 02 28 F0 AD 25
E0 FF 1D E1 4D 63 0A 5F 2E 77 26 3C D3 13 01 87
06 90 FD 12 7F 6B 29 0B 3C 91 06 EC 3A 27 80 79
D4 28 D8 63 FD FB 1A 29 D1 D0 C5 66 48 2A 99 D4
FB 75 81 8F AE 42 A7 D1 49 33 32 EC 25 42 B5 C7
DB 7B AF 63 74 0A 8E CD 4A B8 C5 3D 99 9C 24 FF
AD 6C 4F 0F 2A BD E8 5E 08 67 AC D1 F0 26 13 35
95 BD D0 45 39 FC A8 9F 6F 43 F2 A4 FA 46 C8 ED
18 B0 17 A8 3E 05 AF AB 14 A2 60 15 1A 37 70 2D
44 2A D2 FE 3F EF 53 B7 30 B9 FF A1 D4 7C DC A8
48 9C 74 69 01 56 94 6B 4D 22 CB 74 48 DC A9 93
6C 48 CB 94 6E D4 76 C2 8C 02 FD DA 47 33 44 D3
67 A7 5A 7A 09 CE 97 35 56 9A A6 A1 40 E3 DB 12
99
RSA Public Key = 01 00 01
Authority Key Identifier = Authority Cert Serial=70 12 58 A6 24 F4 3B 46 96 4D E9 64 47 83 EA 20
Key Identifier=31 74 43 25 4D 91 FC 02 0D 5D EF 29 D5 CE 98 A4
Authority Cert Issuer.Directory Name=Common Name = Windows Mobile Test Signing Root
Basic constraints = 30 04 03 02 06 40
Extended key usage = Code signing, Custom Usage : 0
//****************************************************************************
Nice. Did you check to see what the executables are signed with? Say, TIMETEST.exe or ToggleDog.exe? That would be useful to know.
Just using my lovley program "PE Explorer" -> possible to see everything the exe is containing, including signings.
Ther is another way to, the easy way but not all signature data gets extracted
-right click dll -> properties -> {tab} Digital signatures ->
The only info i can get from the dll (ur question), no info about what program it was signed with
  0‚  *†H†÷
*‚ñ0‚í10 + 0h
+‚7*Z0X03
+‚70% * ¢€ < < < O b s o l e t e > > >0!0 + ö½ô⹏ì½cÑzi{E…]Õ#ˆ*‚†0‚‚0‚n*WLj.pA¬MÇе÷´)¡0 + 081604U-Windows Mobile Restricted Rights Test Cert CA0
010101070000Z
[email protected]>U7Windows Mobile Restricted Rights Test Cert Signing Cert0‚"0
 *†H†÷
 ‚ 0‚
‚ óAE¡{òïÝ?±Ù‡- Œ,ý‹Øcƒë7Ã*ô]j»,Ïtí²Q›k•ÜÒl¿*&{fiQEòyu¢ð
Ø@y]õù‚Ž¨ñk]¦bÒ€trýu”¯µ^J$´Br6Ûv,ª±Šþ0`„-HÕ,úˆ°iM£¬\&pGÏ¥aCì-Ýk’pÑ‘I3ù£º`¢7ZN˘èÖÅõükª†œÈ¬ãv—y°ÉåP«ù<B¥»¬âHÄòǁ@sÀ1àjgìç3Xzô&ÊO2ŸŸ¼Eµ’»fíçbÈZ¥•ŸhˆZjýKØ
Bºã]t% ¥zõòëÖúoA2±A £…0‚0
U
0@0U%0
+0\UU0S€€ðy>¶gSf¡ÆÚց¡j¡-0+1)0'U Windows Mobile Test Signing Root‚#šÉg'x¬¤O»n¯—ï"Ã0 + ‚ "Oáìw‹¢$&O‚Ø*žÝê ‰õB…eÒw¢z°-s²`Î\§.N‡>x„²"(.yÝНð£l§ø«ºí†pS„%bžjŠíÉÌ[email protected]‰»
l;ôù2ñhE©§é/":“¥;*׳šÒ‘†¥ûÔ®–(Nd‹Q ¶Ù|}2ÀA·½ÿyô‰Öiµ“Þ’(8aßÛ*ãªx*ÆA8Øü`XÂ5Ê¥²†VöŠWîqƒ!z;*p¿èò•ÁHóŠ›ÄHáÃáíyûî!GÃÊáé¬íâ`‚*üá-Ok°W¤`ñEQnÏ„hé†3ñÔw6*1‚å0‚á0L081604U-Windows Mobile Restricted Rights Test Cert CAWLj.pA¬MÇе÷´)¡0 + *p0
+‚710 0 *†H†÷
 1
+‚70
+‚710
+‚70# *†H†÷
 1¬Ò×ǵrb=Âê«Šü±H:W0
 *†H†÷
 ‚ A““¸¤~*§
_z§‚^³ü ¢0yyLIU§ç/óh*a}8a·).Ž/n2böþÊ(ºYúAy9´“]ùi”Ö=Ôg5ô¨Ò_ Ëm3Á¼O!ÃWL~bïÅóœþš’v굌†÷®~Õæ+_ê#Nu/ÊÍbö %TTâ´æ¨D©1^GÕø(A¦È¾Ó_ö¬¥Š«£– ¡ØY·Ž0ðš·‘[÷¥«Ç~«#×Á<Cü§¨³ÔÛMQTwn{ Ù-ðÞhò!`òšò,Èc)˜QæC.7TÔp}¯Â+8±@OËÓ‡Wèí³E!åý
A few things...
Unless you've got the private key (you don't) there's no way to just sign our apps. So it doesn't really matter what they're signed with or the signatures, etc. The public key does us no good.
WP7 was referred to as Windows Mobile 7 by the teams inside Microsoft probably up until the Mobile World Congress announcement earlier in the year. It's obvious because many of the softies kept calling it that even after the launch. It takes some time to get used to a name change like that.
Who cares that it says "Windows Mobile"? You don't just create new certificates/CAs willy nilly. And besides, what's the point? The only people that will ever see it are people like us who are poking at things we're not supposed to be poking at.
Are you looking at RTM/production binaries or just the emulator dump? I wouldn't be surprised if they were signed using two different certs. Either way, it doesn't really matter (see above).
They probably just used signtool. I've never heard of TIMETEST or ToggleDog and google shows nothing. signtool has long since been the Microsoft signing tool of choice and there's no sign of that changing anytime soon.
here you go :

[Q] Cyanogenmod 7 Nightlies PPTP problem

Hello,
i´m using the latest nightly build of cyanogenmod an i have problems connecting via pptp. Connections is up but no traffic is flowing.
The server is throwing out this in the log file
Code:
2011:03:15-12:41:40 gateway pppd-pptp[14189]: rcvd [LCP ProtRej id=0x59 60 89 31 13 72 c3 22 be 21 d4 f3 ba b1 31 bd 53 33 6a 68 de 9c 22 3c 18 33 77 0d 2f 2d 58 ea c4 ...]
2011:03:15-12:41:40 gateway pppd-pptp[14189]: Protocol-Reject for unsupported protocol 0x6089
2011:03:15-12:41:41 gateway pppd-pptp[14189]: rcvd [LCP ProtRej id=0x5a 00 7d 8a 81 f9 02 5c 2d 7d 46 ed 77 a3 f8 af 9a ee 6e 90 0d 11 d3 db d7 49 c6 a3 a3 cd 32 99 b4 ...]
2011:03:15-12:41:41 gateway pppd-pptp[14189]: Protocol-Reject for unsupported protocol 0x7d
2011:03:15-12:41:42 gateway pppd-pptp[14189]: rcvd [LCP ProtRej id=0x5b 32 c0 30 78 97 25 fd 0b 05 35 5b dd 37 a8 6f 19 3c e4 a0 21 17 e7 21 98 58 c9 e4 3f 4f 1a ed c0 ...]
2011:03:15-12:41:42 gateway pppd-pptp[14189]: Protocol-Reject for unsupported protocol 0x32c0
2011:03:15-12:41:43 gateway pppd-pptp[14189]: rcvd [LCP ProtRej id=0x5c 48 33 fa 47 8a 95 fb cf 32 93 85 1d d1 67 2f bc 9e b2 c5 60 c6 4e 67 7c 65 c8 2f cb c3 c5 93 2a ...]
2011:03:15-12:41:43 gateway pppd-pptp[14189]: Protocol-Reject for unsupported protocol 0x4833
i thought this was fixed a few builds ago in the nightlies?
Sorry for posting here, but i have not enought postings i to ask my question in
the nightlies thread.

Google maps reboots froyo

I am on 3.4.3-11 and the phone is pretty good, but sometimes when i starts google maps, the phone becomes unresponsive sometimes i can close it, but sometimes it reboots the phone. Does anyone has a solution for that? As i remember i dont had the problem on eclair?
Root your phone, delete/rename the maps.apk that is in system/app/ folder and download a new one from the market.
It is already rooted so i will try it. I experienced it with other versions of froyo. The maps is already updated, should i uninstall the updates before deleting the apk? I will write back but it usually takes a half day before producing the slowdown and freezing. Did you experienced the issue and deleting the apk and installing a new one from the market solved it?
vick33 said:
It is already rooted so i will try it. I experienced it with other versions of froyo. The maps is already updated, should i uninstall the updates before deleting the apk? I will write back but it usually takes a half day before producing the slowdown and freezing. Did you experienced the issue and deleting the apk and installing a new one from the market solved it?
Click to expand...
Click to collapse
In my case starting maps resulted in extremely slow performance, so I uninstalled the updates through market and renamed the apk with root explorer. After that I installed maps through market and now everything is working perfect. I have had the same maps problem on all the froyo versions.
It was the same for me. Somtimes i can close the maps, but sometimes i had to remove the battery or the phone rebooted itself. I will write back if the problem occures again, but either way thanks for your help!
What connection are you using? Slow connection can often freeze connection based applications, but not cause reboot though.
Deleting and reinstalling the maps application did not help. It was good for 8 hours, but after it the slowdowns appeared again. The CPU usage was not high at all, but the io wait was. This is what top prints out:
Code:
$ $top -n 1
User 12%, System 22%, IOW 65%, IRQ 0%
User 16 + Nice 23 + Sys 73 + Idle 0 + IOW 211 + IRQ 0 + SIRQ 0 = 323
PID CPU% S #THR VSS RSS PCY UID Name
10962 10% S 23 194340K 24660K bg app_58 com.google.android.gm
1388 4% S 70 336836K 61732K fg system system_server
671 4% S 1 0K 0K fg root mmcqd
10713 4% S 11 162220K 13992K bg app_24 com.motorola.blur.home.newsstatus
11049 3% R 1 856K 392K fg app_93 top
353 3% D 1 0K 0K fg root kswapd0
1119 2% S 1 0K 0K fg root kjournald
1608 1% S 29 190900K 13588K bg app_39 com.google.process.gapps
9937 0% S 14 174704K 19816K bg app_113 com.rechild.advancedtaskkiller
1453 0% S 1 1992K 320K fg wifi /system/bin/wpa_supplicant
1259 0% S 1 6068K 1824K fg root /system/bin/vpnclientpm
203 0% S 1 0K 0K fg root kblockd/0
219 0% S 1 0K 0K fg root cpcap_irq/0
279 0% S 1 0K 0K fg root ksuspend_usbd
284 0% S 1 0K 0K fg root khubd
311 0% S 1 0K 0K fg root kmmcd
318 0% S 1 0K 0K fg root bluetooth
352 0% S 1 0K 0K fg root khungtaskd
355 0% S 1 0K 0K fg root aio/0
356 0% S 1 0K 0K fg root ecryptfs-kthrea
358 0% S 1 0K 0K fg root crypto/0
457 0% S 1 0K 0K fg root kxtf9_wq
497 0% S 1 0K 0K fg root mtdblockd
521 0% S 1 0K 0K fg root klink_driver_wq
539 0% S 1 0K 0K fg root usb_mass_storag
547 0% S 1 0K 0K fg root qtouch_obp_ts_w
556 0% S 1 0K 0K fg root bu52014hfv_wq
562 0% S 1 0K 0K fg root als_wq
594 0% S 1 0K 0K fg root bridge_work-que
595 0% S 1 0K 0K fg root bridge_recovery
601 0% S 1 0K 0K fg root w1_bus_master1
610 0% S 1 0K 0K fg root kstriped
612 0% S 1 0K 0K fg root kondemand/0
632 0% S 1 0K 0K fg root als_wq
646 0% S 1 0K 0K fg root usbhid_resumer
649 0% S 1 0K 0K fg root binder
666 0% S 1 0K 0K fg root krfcommd
668 0% S 1 0K 0K fg root dsi
703 0% S 1 0K 0K fg root mmcqd
725 0% S 1 0K 0K fg root pvrflip/0
730 0% S 1 0K 0K fg root ksuspend_usb_ip
731 0% S 1 0K 0K fg root kipcd
1109 0% S 1 0K 0K fg root kjournald
1129 0% S 1 0K 0K fg root kjournald
1132 0% S 1 0K 0K fg root flush-179:32
1143 0% S 1 0K 0K fg root kjournald
1 0% S 1 300K 252K fg root /init
1161 0% S 1 0K 0K fg root gannet
1173 0% S 1 0K 0K fg root smodule
1180 0% S 1 832K 84K fg root /system/bin/smoduled
1222 0% S 4 3312K 152K fg shell /sbin/adbd
1223 0% S 1 1036K 80K fg root /system/bin/ecckeyd
1225 0% S 1 716K 68K fg system /system/bin/servicemanager
1226 0% S 3 3648K 132K fg root /system/bin/vold
1227 0% S 3 3644K 128K fg root /system/bin/netd
1228 0% S 1 576K 48K fg root /system/bin/debuggerd
1231 0% S 8 18508K 436K fg radio /system/bin/rild
1233 0% S 1 788K 84K fg root /system/bin/usbd
1234 0% S 1 716K 76K fg radio /system/usr/bin/nvm_daemon
1237 0% S 7 7172K 140K fg radio /system/bin/gkisystem
1238 0% S 3 3312K 132K fg radio /system/bin/rild_tcmd
1239 0% S 1 1248K 128K fg mot_accy /system/bin/battd
1242 0% S 1 114524K 8804K fg root zygote
1243 0% S 9 35280K 1776K fg media /system/bin/mediaserver
1244 0% S 1 1176K 84K fg bluetoot /system/bin/dbus-daemon
1245 0% S 1 776K 128K fg root /system/bin/installd
1247 0% S 1 1528K 72K fg keystore /system/bin/keystore
1248 0% S 1 736K 80K fg radio /system/xbin/ssmgrd
1250 0% S 2 14220K 416K fg mot_tcmd /system/bin/tcmd
1251 0% S 1 1256K 128K fg radio /system/usr/bin/panic_daemon
1252 0% S 1 196K 36K fg compass /system/bin/akmd2
1254 0% S 2 3304K 284K fg radio /system/usr/bin/brcm_guci_drv
1256 0% S 1 1088K 112K fg mot_tpap /system/bin/secclkd
1260 0% S 1 584K 60K fg nobody /system/bin/RescueStarter
1261 0% S 7 17296K 536K fg radio protocol_driver
1262 0% S 9 10308K 256K fg radio location
1263 0% S 4 4172K 104K fg radio opprofdaemon
1283 0% S 1 660K 72K fg bluetoot /system/bin/hciattach
1427 0% S 1 0K 0K fg root sdio_wq
1429 0% S 1 0K 0K fg root tiwlan_wq
1450 0% S 12 166968K 14436K fg app_14 com.motorola.blur.providers.contacts
1471 0% S 10 176212K 18296K fg app_13 com.android.inputmethod.latin
1476 0% S 26 191948K 15844K fg radio com.android.phone
1479 0% S 35 235820K 17688K fg app_14 com.motorola.blur.service.main
1480 0% S 21 172160K 15792K fg app_26 com.motorola.blur.service.blur
1487 0% S 12 220628K 25304K fg app_24 com.motorola.blur.home
1491 0% S 6 150316K 9060K fg system com.motorola.atcmd
1493 0% S 7 152692K 11392K fg app_20 com.motorola.batterymanager
1506 0% S 7 159528K 11216K fg app_30 com.nuance.android.vsuite.vsuiteapp
1534 0% S 6 150388K 9184K fg system com.motorola.inpocket
1535 0% S 7 160144K 15524K fg app_72 com.motorola.PerformanceManager
1537 0% S 8 152736K 9740K fg app_78 com.motorola.usb
1664 0% S 7 155140K 10944K fg app_73 android.tts
1815 0% S 1 0K 0K fg root loop0
1819 0% S 1 0K 0K fg root kdmflush
1831 0% S 1 0K 0K fg root kcryptd_io
1832 0% S 1 0K 0K fg root kcryptd
2052 0% S 1 0K 0K fg root loop1
2055 0% S 1 0K 0K fg root kdmflush
2056 0% S 1 0K 0K fg root kcryptd_io
2057 0% S 1 0K 0K fg root kcryptd
2125 0% S 1 0K 0K fg root loop2
2128 0% S 1 0K 0K fg root kdmflush
2129 0% S 1 0K 0K fg root kcryptd_io
2130 0% S 1 0K 0K fg root kcryptd
2151 0% S 1 0K 0K fg root loop3
2154 0% S 1 0K 0K fg root kdmflush
2155 0% S 1 0K 0K fg root kcryptd_io
2156 0% S 1 0K 0K fg root kcryptd
7904 0% S 6 150648K 9140K bg app_50 com.svox.pico
8443 0% S 1 760K 92K fg dhcp /system/bin/dhcpcd
8998 0% S 6 150540K 9136K bg app_34 com.android.defcontainer
9006 0% S 6 152416K 9356K bg app_115 com.menny.android.anysoftkeyboard
9412 0% S 9 173572K 16776K bg system com.android.settings
9703 0% S 6 156128K 9772K bg app_3 com.android.calendar
9732 0% S 8 153824K 10720K bg app_4 android.process.media
9758 0% S 6 150564K 9140K bg app_18 com.motorola.btlowbattery
9839 0% S 6 155300K 9528K bg app_14 com.motorola.blur.contacts.data
10136 0% S 6 150872K 9600K bg app_53 com.motorola.android.datamanager
10143 0% S 7 151952K 9416K bg system com.motorola.process.system
10158 0% S 6 150932K 9388K bg app_41 com.motorola.nabsync
10183 0% S 6 150544K 9112K bg app_92 com.motorola.globalunplug
10191 0% S 6 151700K 9588K bg app_17 com.motorola.android.syncml.service
10650 0% S 12 174768K 11448K bg app_140 com.google.android.apps.maps:NetworkLocationService
10665 0% S 7 153296K 9552K bg app_105 net.rgruet.android.g3watchdog
10673 0% S 6 153700K 9236K bg app_24 com.motorola.togglewidgets
10679 0% S 9 159908K 10400K bg app_24 com.motorola.blur.friendfeed
10689 0% S 8 165296K 9964K bg app_24 com.motorola.blur.contacts
10699 0% S 10 172128K 10496K bg app_24 com.motorola.blur.weather
10706 0% S 9 191972K 10780K bg app_24 com.motorola.blur.quickcontact
10720 0% S 6 158148K 9684K bg app_24 com.motorola.blur.home.other
10727 0% S 7 156504K 9632K bg app_24 com.motorola.blur.home.message
10734 0% S 6 160932K 10504K bg app_116 com.maxmpz.audioplayer
10743 0% S 9 156112K 13168K fg app_93 jackpal.androidterm
10758 0% S 7 152504K 9448K bg app_101 com.noshufou.android.su
11022 0% S 1 648K 156K fg app_93 /system/bin/sh
1160 0% S 1 0K 0K fg root gannet_queue/0
2 0% S 1 0K 0K fg root kthreadd
3 0% S 1 0K 0K fg root ksoftirqd/0
4 0% S 1 0K 0K fg root watchdog/0
5 0% S 1 0K 0K fg root events/0
6 0% S 1 0K 0K fg root khelper
9 0% S 1 0K 0K fg root async/mgr
12 0% S 1 0K 0K fg root suspend
199 0% S 1 0K 0K fg root sync_supers
201 0% S 1 0K 0K fg root bdi-default
207 0% S 1 0K 0K fg root omap_serial
215 0% S 1 0K 0K fg root omap2_mcspi
So the case is someting polling the IO so fast that even system processes starve. Then i tried to get what are the exact processes using so much io. under linux i can do that, and no wonder it works under android too:
echo 1 > /proc/sys/vm/block_dump ; cat /proc/kmsg ; echo 0 > /proc/sys/vm/block_dump
During normal opareation kjournald, and flush-179:32 are the only processes using io wrting logs to mmcblk1p25, but when the phone starts to lag a couple process starts to read mmcblk1p21(the sytem) like hell. This is just a short example:
Code:
<7>[46906.785827] er.ServerThread(1396): READ block 33756 on mmcblk1p21 (8 sectors)
<7>[46906.786437] er.ServerThread(1396): READ block 33804 on mmcblk1p21 (8 sectors)
<7>[46906.786773] er.ServerThread(1396): READ block 33820 on mmcblk1p21 (56 sectors)
<7>[46906.787445] pal.androidterm(10743): READ block 33540 on mmcblk1p21 (8 sectors)
<7>[46906.787994] pal.androidterm(10743): READ block 33588 on mmcblk1p21 (64 sectors)
<7>[46906.803344] pal.androidterm(10743): READ block 591296 on mmcblk1p21 (40 sectors)
<7>[46906.804077] pal.androidterm(10743): READ block 591344 on mmcblk1p21 (8 sectors)
<7>[46906.804626] pal.androidterm(10743): READ block 591360 on mmcblk1p21 (16 sectors)
<7>[46906.804962] pal.androidterm(10743): READ block 591416 on mmcblk1p21 (16 sectors)
<7>[46906.818817] Binder Thread #(1556): READ block 606582 on mmcblk1p21 (16 sectors)
<7>[46906.819244] Binder Thread #(1556): READ block 606614 on mmcblk1p21 (32 sectors)
<7>[46906.819824] Binder Thread #(1556): READ block 606686 on mmcblk1p21 (136 sectors)
<7>[46906.820404] Binder Thread #(1556): READ block 606822 on mmcblk1p21 (2 sectors)
<7>[46906.828674] ConnectivityThr(1416): READ block 215246 on mmcblk1p21 (32 sectors)
<7>[46906.829254] ConnectivityThr(1416): READ block 215286 on mmcblk1p21 (40 sectors)
<7>[46906.829803] ConnectivityThr(1416): READ block 215334 on mmcblk1p21 (64 sectors)
<7>[46906.830139] ConnectivityThr(1416): READ block 215406 on mmcblk1p21 (16 sectors)
<7>[46906.830657] ConnectivityThr(1416): READ block 215430 on mmcblk1p21 (8 sectors)
<7>[46906.831207] ConnectivityThr(1416): READ block 215478 on mmcblk1p21 (24 sectors)
<7>[46906.840393] Binder Thread #(1556): READ block 606826 on mmcblk1p21 (8 sectors)
<7>[46906.853302] WebViewCoreThre(9943): READ block 285914 on mmcblk1p21 (136 sectors)
<7>[46906.862487] WebViewCoreThre(9943): READ block 285698 on mmcblk1p21 (8 sectors)
<7>[46906.881317] Binder Thread #(1556): READ block 214730 on mmcblk1p21 (8 sectors)
<7>[46906.881927] Binder Thread #(1556): READ block 214746 on mmcblk1p21 (24 sectors)
<7>[46906.882446] Binder Thread #(1556): READ block 214866 on mmcblk1p21 (8 sectors)
<7>[46906.887115] ConnectivityThr(1416): READ block 582618 on mmcblk1p21 (216 sectors)
<7>[46906.887695] ConnectivityThr(1416): READ block 582836 on mmcblk1p21 (40 sectors)
<7>[46906.907348] ConnectivityThr(1416): READ block 16492 on mmcblk1p21 (24 sectors)
<7>[46906.907989] ConnectivityThr(1416): READ block 16518 on mmcblk1p21 (50 sectors)
<7>[46906.923339] ConnectivityThr(1416): READ block 314154 on mmcblk1p21 (32 sectors)
<7>[46906.923950] ConnectivityThr(1416): READ block 314210 on mmcblk1p21 (200 sectors)
<7>[46906.938934] ConnectivityThr(1416): READ block 557382 on mmcblk1p21 (12 sectors)
<7>[46906.943695] WebViewCoreThre(9943): READ block 286404 on mmcblk1p21 (160 sectors)
<7>[46906.954528] WebViewCoreThre(9943): READ block 284516 on mmcblk1p21 (8 sectors)
<7>[46906.955291] WebViewCoreThre(9943): READ block 284526 on mmcblk1p21 (192 sectors)
<7>[46906.971923] WebViewCoreThre(9943): READ block 288636 on mmcblk1p21 (2 sectors)
<7>[46906.977264] ConnectivityThr(1416): READ block 557374 on mmcblk1p21 (8 sectors)
<7>[46906.983459] wpa_supplicant(1453): READ block 22688 on mmcblk1p21 (24 sectors)
<7>[46906.984161] wpa_supplicant(1453): READ block 22714 on mmcblk1p21 (232 sectors)
<7>[46906.996124] Binder Thread #(1556): READ block 313806 on mmcblk1p21 (80 sectors)
<7>[46906.996704] Binder Thread #(1556): READ block 313894 on mmcblk1p21 (32 sectors)
<7>[46907.009613] Binder Thread #(1556): READ block 582884 on mmcblk1p21 (256 sectors)
<7>[46907.022583] Binder Thread #(1556): READ block 109822 on mmcblk1p21 (168 sectors)
<7>[46907.031280] Binder Thread #(1556): READ block 583880 on mmcblk1p21 (232 sectors)
<7>[46907.044342] Binder Thread #(1556): READ block 591336 on mmcblk1p21 (8 sectors)
<7>[46907.044799] Binder Thread #(1556): READ block 591352 on mmcblk1p21 (8 sectors)
<7>[46907.045318] Binder Thread #(1556): READ block 591376 on mmcblk1p21 (8 sectors)
<7>[46907.045654] Binder Thread #(1556): READ block 591432 on mmcblk1p21 (48 sectors)
<7>[46907.046234] Binder Thread #(1556): READ block 591488 on mmcblk1p21 (52 sectors)
<7>[46907.059722] Binder Thread #(1556): READ block 215502 on mmcblk1p21 (72 sectors)
<7>[46907.060150] Binder Thread #(1556): READ block 215576 on mmcblk1p21 (40 sectors)
<7>[46907.066314] Binder Thread #(1556): READ block 606430 on mmcblk1p21 (8 sectors)
<7>[46907.066925] Binder Thread #(1556): READ block 606494 on mmcblk1p21 (88 sectors)
<7>[46907.067260] Binder Thread #(1556): READ block 606646 on mmcblk1p21 (40 sectors)
<7>[46907.083068] pal.androidterm(10743): READ block 606422 on mmcblk1p21 (8 sectors)
<7>[46907.084655] WebViewCoreThre(9943): READ block 288894 on mmcblk1p21 (256 sectors)
<7>[46907.098815] WebViewCoreThre(9943): READ block 280340 on mmcblk1p21 (72 sectors)
<7>[46907.099639] WebViewCoreThre(9943): READ block 280414 on mmcblk1p21 (56 sectors)
<7>[46907.105194] WebViewCoreThre(9943): READ block 283472 on mmcblk1p21 (24 sectors)
<7>[46907.113708] WebViewCoreThre(9943): READ block 280566 on mmcblk1p21 (16 sectors)
<7>[46907.114410] WebViewCoreThre(9943): READ block 280814 on mmcblk1p21 (88 sectors)
<7>[46907.119415] WebViewCoreThre(9943): READ block 280470 on mmcblk1p21 (88 sectors)
<7>[46907.132141] WebViewCoreThre(9943): READ block 283048 on mmcblk1p21 (168 sectors)
<7>[46907.140594] WebViewCoreThre(9943): READ block 623044 on mmcblk1p21 (12 sectors)
<7>[46907.149017] WebViewCoreThre(9943): READ block 282172 on mmcblk1p21
after i restart the phone i cannot get the error for at least 8 hours. It has to be something with the data connections but i can get the problem on wifi and on 3g too... So i am clueless Anyone has any idea?
I have the same problem. Reinstall the app didn't help.

Categories

Resources