I can not debug app on my phone, it dont stop at break point, i think boot.img have problem, i use HTC desire 616 chip mtk6592, how to fix that?, it is important with me. Thanks you
Code:
01-20 17:34:18.719: I/dalvikvm(27238): Debugger is active
01-20 17:34:18.759: D/jdwp(27238): --> SLEEPING, Not SUSPENDED
01-20 17:34:18.760: D/jdwp(27238): --> SLEEPING, Not SUSPENDED
01-20 17:34:18.768: D/jdwp(27238): --> RUNNING, Not SUSPENDED
01-20 17:34:18.774: D/jdwp(27238): --> RUNNING, Not SUSPENDED
01-20 17:34:18.786: D/jdwp(27238): --> RUNNING, Not SUSPENDED
01-20 17:34:18.787: D/jdwp(27238): --> RUNNING, Not SUSPENDED
01-20 17:34:18.812: D/jdwp(27238): --> WAIT, Not SUSPENDED
01-20 17:34:18.814: D/jdwp(27238): --> WAIT, Not SUSPENDED
01-20 17:34:18.840: D/jdwp(27238): --> WAIT, Not SUSPENDED
01-20 17:34:18.842: D/jdwp(27238): --> WAIT, Not SUSPENDED
01-20 17:34:18.895: D/jdwp(27238): --> WAIT, Not SUSPENDED
01-20 17:34:18.897: D/jdwp(27238): --> WAIT, Not SUSPENDED
01-20 17:34:18.904: D/jdwp(27238): --> WAIT, Not SUSPENDED
01-20 17:34:18.905: D/jdwp(27238): --> WAIT, Not SUSPENDED
01-20 17:34:18.913: D/jdwp(27238): --> WAIT, Not SUSPENDED
01-20 17:34:18.916: I/System.out(27238): Debugger has connected
01-20 17:34:18.916: D/jdwp(27238): +++ debugger interval=2
01-20 17:34:18.916: I/System.out(27238): waiting for debugger to settle...
01-20 17:34:18.917: D/jdwp(27238): --> WAIT, Not SUSPENDED
01-20 17:34:18.983: D/jdwp(27238): --> WAIT, Not SUSPENDED
01-20 17:34:18.984: D/jdwp(27238): --> WAIT, Not SUSPENDED
01-20 17:34:19.116: D/jdwp(27238): +++ debugger interval=2
01-20 17:34:19.116: I/System.out(27238): waiting for debugger to settle...
01-20 17:34:19.316: D/jdwp(27238): +++ debugger interval=23
01-20 17:34:19.316: I/System.out(27238): waiting for debugger to settle...
01-20 17:34:19.517: D/jdwp(27238): +++ debugger interval=223
01-20 17:34:19.517: I/System.out(27238): waiting for debugger to settle...
01-20 17:34:19.717: D/jdwp(27238): +++ debugger interval=423
01-20 17:34:19.717: I/System.out(27238): waiting for debugger to settle...
01-20 17:34:19.918: D/jdwp(27238): +++ debugger interval=624
01-20 17:34:19.918: I/System.out(27238): waiting for debugger to settle...
01-20 17:34:20.119: D/jdwp(27238): +++ debugger interval=825
01-20 17:34:20.119: I/System.out(27238): waiting for debugger to settle...
01-20 17:34:20.320: D/jdwp(27238): +++ debugger interval=1026
01-20 17:34:20.320: I/System.out(27238): waiting for debugger to settle...
01-20 17:34:20.520: D/jdwp(27238): +++ debugger interval=1227
01-20 17:34:20.520: I/System.out(27238): waiting for debugger to settle...
01-20 17:34:20.721: D/jdwp(27238): +++ debugger interval=1427
01-20 17:34:20.722: I/System.out(27238): debugger has settled (1427)
01-20 17:34:20.723: E/dalvikvm(27238): HEY: invalid 'this' ptr 0x1 (Ljava/lang/Object;.<init> ()V)
01-20 17:34:20.723: E/dalvikvm(27238): VM aborting
01-20 17:34:20.724: A/libc(27238): Fatal signal 11 (SIGSEGV) at 0xdeadd00d (code=1), thread 27238 (kerlabs.starhub)
01-20 17:34:20.727: A/libc(27238): Send stop signal to pid:27238 in debugger_signal_handler
01-20 17:34:21.344: D/jdwp(27808): received file descriptor 49 from ADB
01-20 17:34:21.346: D/asset(27808): AssetManager-->addDefaultAssets CIP path not exsit!
01-20 17:34:21.355: D/dalvikvm(27808): open_cached_dex_file : /data/app/com.rainmakerlabs.starhub-1.apk /data/dalvik-cache/[email protected]@[email protected]
01-20 17:34:21.364: I/System.out(27808): Sending WAIT chunk
Link boot.img https://app.box.com/s/3w7rl14kurajs8vn4rcqu53tbg4yvp6y
Related
I'm writing monitoring application and need to get some communication events.
Using the 'tstril' I can get the incoming SMS events and also captured out SMS and incoming/outgoing voice calls events. My problem now is that I captured the events but don't know how to parse their data in the RILMESSAGE struct since it have data struct just for few events.
Any ideas how can I get the missing data?
Thanks
If anyone has spare time, the WM5 automatic keylock application would be great :
- It notices system event which occurs when device goes to
suspended state
- It automatically locks (WM5 integrated keylock) keyboard
when above mentioned event occurs (if the keyboard was
not locked already)
- It's hidden so that it never gets unloaded
Every application I've tried this far uses "on-resume" notification queue, which will prevent alarm clock triggering alarms
further details...
I've studied PM internals and I suppose this is how it could be done :
1) Application thread is THREAD_PRIORITY_TIME_CRITICAL
2) Application creates message queue, where power state
messages will be stored
3 Application requests PM for all notifications :
RequestPowerNotifications
3) Application does nothing but waits
POWER_STATE_SUSPEND message
into it's queue
4) As soon as it's received, application
invokes integrated keyboard locking
mechanism
ok, here it is...
I coded it myself then...
http://mobilitytoday.com/forum/showthread.php?t=13030
This utility lock WM5 based devices' keyboard automatically when
device goes to suspended state.
---
1) Application creates message queue, where power state
messages will be stored
3 Application requests PM for all notifications :
RequestPowerNotifications
3) Application does nothing but waits
POWER_STATE_SUSPEND message
into it's queue
4) As soon as it's received, application
invokes integrated keyboard locking
mechanism by sending special keycode VK_F22
Jussi77: Neat app!
Seems to be working well on my apache, also I saw what you're planning on adding (hiding it from running tasks, etc) and that should be real nice.
anything for wm2003se?
i've just searched for it! will try it at home
I have a strange behaviour of BroadcastReceiver when trying to listen
incoming call. I set up the BroadcastReceiver to listen to both
incoming calls and sms. The BroadcastReceiver run after the booting is
complete. When first i fake a call into the emulator, i can not catch
the call. I try again with sms and my Broadcastreceiver can catch the
sms correctly. I try again with the incoming call and now the
BroadcastReceiver works. I restart the emulator and try again. It
seems that i always have to fake a sms to trigger the
BroadcastReceiver. After that the BroadcastReceiver behaves correctly
as i want.
What did i do wrong?
just wondering if i'm the only one who's noticed this, but when i receive a message i get the alert followed by a notification.
when i pull down notification menu and click the message, the messaging app appears but it takes about 5 seconds for the new message to appear in the thread.
the same thing happens with both stock messaging and handcent.
even if my screen is on, and the messaging app is open there's still a delay.
i -think- this problem was introduced with froyo.
the same thing happens in all froyo roms.
i've tried debugging but the logcat was awfully short;
Code:
I/AudioService( 125): AudioFocus requestAudioFocus() from [email protected]
W/AudioFlinger( 66): write blocked for 85 msecs, 66 delayed writes, thread 0xdc20
D/dalvikvm( 125): GC_EXTERNAL_ALLOC freed 9210 objects / 420488 bytes in 208ms
I/AudioService( 125): AudioFocus abandonAudioFocus() from [email protected]
D/dalvikvm( 417): GC_EXPLICIT freed 10756 objects / 565536 bytes in 136ms
V/Telephony( 212): getOrCreateThreadId uri: content://mms-sms/threadID?recipient=%2B492937488882
V/Telephony( 212): getOrCreateThreadId cursor cnt: 1
the above logcat was ~5 seconds long.
can this be a bug in message store or something?
note: when sending a message, it's a small delay too before it appears in the thread, but only ~2 seconds.
[Q] "Rolled up" notifications triggers onNotificationRemoved in NotificationListener
Not sure about the proper term for this, but sometimes when an app posts multiple notifications, the subsequent notifications are rolled up into the first one. Example will be
Code:
Notification 1
Contact 1: Hello!
Then when another notification comes in (e.g. Contact 2: Hey!):
Code:
You have 2 notifications from User 1 and User 2.
I am writing a service that aggregates notifications posted by other apps. I opt for the 4.3 NotificationListener service because that's what Google recommends over accessibility services.
My idea is when the notification of the apps are cleared, onNotificationRemoved will be triggered and I can clear the notifications with my service accordingly.
Code:
@Override
public void onNotificationRemoved(StatusBarNotification sbn) {
if (sbn.getPackageName().equals("com.some.app.im.monitoring")) {
// some code that removes the aggregation for this app
}
}
The problem I have right now is when the "roll up" happens, the incoming notification is cleared by the app itself and rolled up with other notifications it received. This triggers onNotificationRemoved for the incoming notification, and there is no way for me to know whether it is triggered by user or by the roll up.
Any idea on how I can avoid this getting trigger by the roll up?