Database Users

[PROJECT] JIT enabled Dalvik VM

Just saw this and I was wondering how much work it would take to get this working.
http://forum.xda-developers.com/showthread.php?t=637419

Based on what I've seen on blogs and in various other cooked rom projects, it's a lot of work for something that is very unstable.

I already have a working patch for 0.3 but it does cause some instability.

We've already got JIT's running. They're not in any of the public roms/updates yet though. I've been running them, and so has jcase I think. Myself, I haven't had any issues really.
They definitely make the phone a little snappier, and I haven't had any stability issues so far.
Here's some benchmarks I ran with Linpack:
No JIT's MFLOPS: 2.239
JIT's MFLOPS: 3.453
(average of 3 tests each)

ivanmmj said:
I already have a working patch for 0.3 but it does cause some instability.
Click to expand...
Click to collapse
Can I get a copy of the patch just to play with?

binny1007 said:
Can I get a copy of the patch just to play with?
Click to expand...
Click to collapse
PM sent
..

Binny,
Come hit me on irc. I have been wrong it for a while now, with what ivan gave me.
-jcase

from my workings with jit in various roms. is that in some roms it works well and others it doesnt. ive found that aosp builds tend to have the best luck with jit as in not having high issue rates. ive added and removed it from builds that ive made for the heroc for my own reasons. one being as i or the beta testers i used wouldnt have any issues. but as soon as i released it and the rest of the community would use the build, issues would then begin to arise from having JIT enabled. because not everyone sets up their phone the same nor uses it in the same manner. so i ended up making it a users choice to setup jit or not and just leaving it out of my hands to deal with. as when i release a build i shoot for stable and fast for all users. with as little bugs and issues as possible. ive found other methods to increase speed and stability that have show good results for all users of my builds. plus i found most users want a fast and stable base build that they can just add to or mod to their liking.
again this is all based on the users on the Heroc forums. i assume the Eris will be in the same boat, as its basically the same device.

I have been running jit fine for a while now, however I reboot my phone atleast twice a day messing with stuff.

jcase said:
I have been running jit fine for a while now, however I reboot my phone atleast twice a day messing with stuff.
Click to expand...
Click to collapse
only twice

jcase said:
I have been running jit fine for a while now, however I reboot my phone atleast twice a day messing with stuff.
Click to expand...
Click to collapse
Alteast twice

trying to get this running on my rom experimentally and it loads fine then dalvik crashes the system
this is what logcat gives me
Code:
D/VoiceDialerReceiver( 661): onReceive Intent { act=android.intent.action.BOOT_COMPLETED cmp=com.android.voicedialer/.VoiceDialerReceiver }
I/HtcLockScreen( 472): touch ACTION_DOWN
D/LockExchangeUtils( 472): isLockExchangeEnabled = false
D/LockExchangeUtils( 472): isLockExchangeEnabled = false
I/HtcLockScreen( 472): touch ACTION_UP
W/dalvikvm( 472): No implementation found for native Ldalvik/system/VMRuntime;.disableGcForExternalAlloc (Z)V
W/dalvikvm( 472): threadid=41: thread exiting with uncaught exception (group=0x4001e2e0)
E/AndroidRuntime( 472): Uncaught handler: thread WindowManagerPolicy exiting due to uncaught exception
E/AndroidRuntime( 472): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
E/AndroidRuntime( 472): java.lang.UnsatisfiedLinkError: disableGcForExternalAlloc
E/AndroidRuntime( 472): at dalvik.system.VMRuntime.disableGcForExternalAlloc(Native Method)
E/AndroidRuntime( 472): at com.htc.lockscreen.HtcLockScreen.onInterceptTouchEvent(HtcLockScreen.java:2643)
E/AndroidRuntime( 472): at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:897)
E/AndroidRuntime( 472): at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:924)
E/AndroidRuntime( 472): at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:924)
E/AndroidRuntime( 472): at android.view.ViewRoot.handleMessage(ViewRoot.java:1697)
E/AndroidRuntime( 472): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 472): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 472): at com.android.server.WindowManagerService$PolicyThread.run(WindowManagerService.java:611)
I/Process ( 472): Sending signal. PID: 472 SIG: 9
D/dalvikvm( 594): GC freed 2926 objects / 229136 bytes in 167ms
D/CalendarProvider( 644): deleteRowsForRemovedAccounts need to check count: 0
D/CalendarProvider( 644): deleteRowsForRemovedAccounts need to check count: 0
V/CalendarProvider( 644): onAccountsChanged
D/CalendarProvider( 644): deleteRowsForRemovedAccounts need to check count: 2
V/CalendarProvider( 644): accounts didn't contains: Account {[email protected], type=com.google} -- SKIP [no need to delete]
E/ActivityThread( 531): Failed to find provider info for call_log
I/ServiceManager( 52): service 'activity' died
I/ServiceManager( 52): service 'meminfo' died
I/ServiceManager( 52): service 'batteryinfo' died
I/ServiceManager( 52): service 'telephony.registry' died
I/ServiceManager( 52): service 'entropy' died
I/ServiceManager( 52): service 'power' died
i would really like to get it working any help is appreciated

i ran into constant crashing trying to get this working? It seems as though sense does not play nice with jit enabled.

binny1007 said:
i ran into constant crashing trying to get this working? It seems as though sense does not play nice with jit enabled.
Click to expand...
Click to collapse
yeah, its the main sense elements that don't play nice with jit. i've tried messing with it a few times before, but eventually its pretty much the non-sense roms(or AOSP) that work with jit. unless there's some sort of tweak we can do to sense(both the lockscreen and sense itself), jit probably won't work with non-aosp roms.

I got it to work! =)
jamezelle said:
trying to get this running on my rom experimentally and it loads fine then dalvik crashes the system
this is what logcat gives me
Code:
D/VoiceDialerReceiver( 661): onReceive Intent { act=android.intent.action.BOOT_COMPLETED cmp=com.android.voicedialer/.VoiceDialerReceiver }
I/HtcLockScreen( 472): touch ACTION_DOWN
D/LockExchangeUtils( 472): isLockExchangeEnabled = false
D/LockExchangeUtils( 472): isLockExchangeEnabled = false
I/HtcLockScreen( 472): touch ACTION_UP
W/dalvikvm( 472): No implementation found for native Ldalvik/system/VMRuntime;.disableGcForExternalAlloc (Z)V
W/dalvikvm( 472): threadid=41: thread exiting with uncaught exception (group=0x4001e2e0)
E/AndroidRuntime( 472): Uncaught handler: thread WindowManagerPolicy exiting due to uncaught exception
E/AndroidRuntime( 472): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
E/AndroidRuntime( 472): java.lang.UnsatisfiedLinkError: disableGcForExternalAlloc
E/AndroidRuntime( 472): at dalvik.system.VMRuntime.disableGcForExternalAlloc(Native Method)
E/AndroidRuntime( 472): at com.htc.lockscreen.HtcLockScreen.onInterceptTouchEvent(HtcLockScreen.java:2643)
E/AndroidRuntime( 472): at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:897)
E/AndroidRuntime( 472): at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:924)
E/AndroidRuntime( 472): at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:924)
E/AndroidRuntime( 472): at android.view.ViewRoot.handleMessage(ViewRoot.java:1697)
E/AndroidRuntime( 472): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 472): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 472): at com.android.server.WindowManagerService$PolicyThread.run(WindowManagerService.java:611)
I/Process ( 472): Sending signal. PID: 472 SIG: 9
D/dalvikvm( 594): GC freed 2926 objects / 229136 bytes in 167ms
D/CalendarProvider( 644): deleteRowsForRemovedAccounts need to check count: 0
D/CalendarProvider( 644): deleteRowsForRemovedAccounts need to check count: 0
V/CalendarProvider( 644): onAccountsChanged
D/CalendarProvider( 644): deleteRowsForRemovedAccounts need to check count: 2
V/CalendarProvider( 644): accounts didn't contains: Account {[email protected], type=com.google} -- SKIP [no need to delete]
E/ActivityThread( 531): Failed to find provider info for call_log
I/ServiceManager( 52): service 'activity' died
I/ServiceManager( 52): service 'meminfo' died
I/ServiceManager( 52): service 'batteryinfo' died
I/ServiceManager( 52): service 'telephony.registry' died
I/ServiceManager( 52): service 'entropy' died
I/ServiceManager( 52): service 'power' died
i would really like to get it working any help is appreciated
Click to expand...
Click to collapse
I have been spending some hours reversing the libdvm.so and how dalvik works and i have been successfull on enabling it.
What I did was to get the latest android sources, enable jit in buildspec.mk.
After this, i get the same error as you got.
So i modified the dalvik/vm/native/dalvik_system_VMRuntime.c, here is a diff:
Code:
--- a/vm/native/dalvik_system_VMRuntime.c
+++ b/vm/native/dalvik_system_VMRuntime.c
@@ -178,6 +178,13 @@ static void
Dalvik_dalvik_system_VMRuntime_getExternalBytesAllocated(
RETURN_LONG((s8)dvmGetExternalBytesAllocated());
}
+static void Dalvik_dalvik_system_VMRuntime_disableGcForExternalAlloc(
+ const u4* args, JValue* pResult)
+{
+ RETURN_VOID();
+}
+
+
const DalvikNativeMethod dvm_dalvik_system_VMRuntime[] = {
{ "getTargetHeapUtilization", "()F",
Dalvik_dalvik_system_VMRuntime_getTargetHeapUtilization },
@@ -195,6 +202,10 @@ const DalvikNativeMethod dvm_dalvik_system_VMRuntime[] = {
Dalvik_dalvik_system_VMRuntime_trackExternalFree },
{ "getExternalBytesAllocated", "()J",
Dalvik_dalvik_system_VMRuntime_getExternalBytesAllocated },
+ { "disableGcForExternalAlloc", "(Z)V",
+ Dalvik_dalvik_system_VMRuntime_disableGcForExternalAlloc },
{ NULL, NULL, NULL },
};
I have also attached the compiled libdvm.so if anyone wants to try.
Note: Sense is crashing some times,with OutOfMemory exception, probably due to my dummy implementation of the function.
Would be cool to get this "stable" =)

nilo85 said:
I have been spending some hours reversing the libdvm.so and how dalvik works and i have been successfull on enabling it.
What I did was to get the latest android sources, enable jit in buildspec.mk.
After this, i get the same error as you got.
So i modified the dalvik/vm/native/dalvik_system_VMRuntime.c, here is a diff:
Code:
--- a/vm/native/dalvik_system_VMRuntime.c
+++ b/vm/native/dalvik_system_VMRuntime.c
@@ -178,6 +178,13 @@ static void
Dalvik_dalvik_system_VMRuntime_getExternalBytesAllocated(
RETURN_LONG((s8)dvmGetExternalBytesAllocated());
}
+static void Dalvik_dalvik_system_VMRuntime_disableGcForExternalAlloc(
+ const u4* args, JValue* pResult)
+{
+ RETURN_VOID();
+}
+
+
const DalvikNativeMethod dvm_dalvik_system_VMRuntime[] = {
{ "getTargetHeapUtilization", "()F",
Dalvik_dalvik_system_VMRuntime_getTargetHeapUtilization },
@@ -195,6 +202,10 @@ const DalvikNativeMethod dvm_dalvik_system_VMRuntime[] = {
Dalvik_dalvik_system_VMRuntime_trackExternalFree },
{ "getExternalBytesAllocated", "()J",
Dalvik_dalvik_system_VMRuntime_getExternalBytesAllocated },
+ { "disableGcForExternalAlloc", "(Z)V",
+ Dalvik_dalvik_system_VMRuntime_disableGcForExternalAlloc },
{ NULL, NULL, NULL },
};
I have also attached the compiled libdvm.so if anyone wants to try.
Note: Sense is crashing some times,with OutOfMemory exception, probably due to my dummy implementation of the function.
Would be cool to get this "stable" =)
Click to expand...
Click to collapse
hmm i tried running your patch but it didnt fully take on the source
Code:
[email protected]:~/mydroid/dalvik$ patch -p1 < /home/jamezelle/desktop/dalvikpatch
patching file vm/native/dalvik_system_VMRuntime.c
Hunk #1 succeeded at 177 with fuzz 2 (offset -1 lines).
missing header for unified diff at line 18 of patch
can't find file to patch at input line 18
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
| Dalvik_dalvik_system_VMRuntime_getTargetHeapUtilization },
--------------------------
File to patch:

Patch
Hi, it was just a simple "git diff" command, seems to be a little bit different from patch format.
I was recently wiping my phone, and at init starting with this libdvm.so, and i noticed that there was another symbol not beeing exported, was to tired to look it up at that time, but running a already dexopted system, seems pretty "stable", except of Launcher crashing from time to time of OutOfMemory.
Here's a patch for the previous post:
Code:
*** mydroid/dalvik/vm/native/dalvik_system_VMRuntime.c 2010-03-12 12:15:12.000000000 +0100
--- mydroid_edit/dalvik/vm/native/dalvik_system_VMRuntime.c 2010-04-08 19:38:12.000000000 +0200
***************
*** 178,183 ****
--- 178,190 ----
RETURN_LONG((s8)dvmGetExternalBytesAllocated());
}
+ static void Dalvik_dalvik_system_VMRuntime_disableGcForExternalAlloc(
+ const u4* args, JValue* pResult)
+ {
+ RETURN_VOID();
+ }
+
+
const DalvikNativeMethod dvm_dalvik_system_VMRuntime[] = {
{ "getTargetHeapUtilization", "()F",
Dalvik_dalvik_system_VMRuntime_getTargetHeapUtilization },
***************
*** 195,200 ****
--- 202,209 ----
Dalvik_dalvik_system_VMRuntime_trackExternalFree },
{ "getExternalBytesAllocated", "()J",
Dalvik_dalvik_system_VMRuntime_getExternalBytesAllocated },
+ { "disableGcForExternalAlloc", "(Z)V",
+ Dalvik_dalvik_system_VMRuntime_disableGcForExternalAlloc },
{ NULL, NULL, NULL },
};

Crash Log?

Hello, I am wondering if there is some sort of crash log on my G1? I am running cyanogens 4.2.15.1, and I recently started having a problem after wiping dalvik cache for the first time this weekend.
The problem is that the phone randomly turns itself off now. I take the phone out of my pocket to use it, and find it powered off. It would be helpful to have some sort of log to find out why it crashed?

well, I suppose a temporary solution is to run
[email protected]:/sdcard# (logcat > log.txt&)
and wait for the next crash and read the text file in /sdcard. phone crashed/turned off again today, twice already today. very annoying.

well I was messing with the phone and had the logcat running all it got was this:
Code:
[email protected]:sdcard# tail logcat.log
I/Term ( 824): waiting for: 830
D/dalvikvm( 824): GC freed 716 objects / 59248 bytes in 95ms
I/dalvikvm-heap( 824): Grow heap (frag case) to 5.186MB for 1360016-byte allocation
I/ActivityManager( 144): Process com.android.camera (pid 765) has died.
D/dalvikvm( 824): GC freed 138 objects / 6520 bytes in 105ms
I/ActivityManager( 144): Displayed activity com.android.term/.Term: 923 ms (total 923 ms)
D/dalvikvm( 800): GC freed 788 objects / 444000 bytes in 117ms
D/dalvikvm( 187): GC freed 155 objects / 6576 bytes in 136ms
D/dalvikvm( 507): GC freed 47 objects / 1864 bytes in 291ms
W/Process ( 144): Unable to open /proc/765/status
[email protected]:sdcard#
not too useful. anyone have better ideas how to log this crash?

tried it again, phone crashed again. the last action performed on the phone was switching orientation and i watched the device power off.
heres whatever that is relevant to the last crash that happened at 9:11 AM:
Code:
04-14 08:57:45.829 D/SurfaceFlinger( 143): About to give-up screen, flinger = 0x1009f8
04-14 08:57:46.049 D/su ( 1964): 10061:10061 org.freecoder.widgets.overclock executing 0:0 /system/bin/sh
04-14 09:01:55.118 D/NetworkLocationProvider( 143): onCellLocationChanged [-1,-1]
04-14 09:06:17.798 D/NetworkLocationProvider( 143): onCellLocationChanged [26293,59156224]
04-14 09:06:22.798 D/LocationMasfClient( 143): getNetworkLocation(): Location not found in cache, making network request
04-14 09:06:25.118 D/LocationMasfClient( 143): getNetworkLocation(): Number of prefetched entries 1
04-14 09:06:25.168 D/LocationMasfClient( 143): getNetworkLocation(): Returning network location with accuracy 1491.0
04-14 09:06:27.998 D/dalvikvm( 440): GC freed 157 objects / 9800 bytes in 204ms
04-14 09:11:06.537 D/KeyguardViewMediator( 143): wakeWhenReadyLocked(82)
04-14 09:11:06.577 D/KeyguardViewMediator( 143): handleWakeWhenReady(82)
04-14 09:11:06.597 D/KeyguardViewMediator( 143): pokeWakelock(5000)
04-14 09:11:06.657 D/Sensors ( 143): sensors=00000001, real=00000001
04-14 09:11:06.657 D/AKMD ( 130): Compass OPEN
04-14 09:11:06.667 W/WindowManager( 143): No focus window, dropping: KeyEvent{action=1 code=82 repeat=0 meta=0 scancode=139 mFlags=8}
04-14 09:11:06.797 D/SurfaceFlinger( 143): Screen about to return, flinger = 0x1009f8
04-14 09:11:07.017 I/WindowManager( 143): onOrientationChanged, rotation changed to 0
04-14 09:11:07.337 D/su ( 1979): 10061:10061 org.freecoder.widgets.overclock executing 0:0 /system/bin/sh
04-14 09:11:07.507 D/KeyguardViewMediator( 143): pokeWakelock(5000)
04-14 09:11:07.557 W/InputManagerService( 143): Window already focused, ignoring focus gain of: [email protected]
04-14 09:11:07.607 D/NetworkLocationProvider( 143): onCellLocationChanged [26293,59155814]
04-14 09:11:10.437 W/AudioFlinger( 125): write blocked for 91 msecs
04-14 09:11:12.417 I/ActivityManager( 143): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.term/.Term }
04-14 09:11:12.497 I/ActivityManager( 143): Start proc com.android.term for activity com.android.term/.Term: pid=1984 uid=10014 gids={}
04-14 09:11:12.837 E/Term ( 1984): onCreate
04-14 09:11:12.957 I/Term ( 1984): waiting for: 1990
04-14 09:11:13.137 D/dalvikvm( 1984): GC freed 717 objects / 59344 bytes in 86ms
04-14 09:11:13.147 I/dalvikvm-heap( 1984): Grow heap (frag case) to 4.747MB for 900016-byte allocation
04-14 09:11:13.247 D/dalvikvm( 1984): GC freed 18 objects / 888 bytes in 96ms
04-14 09:11:13.317 I/ActivityManager( 143): Displayed activity com.android.term/.Term: 835 ms (total 835 ms)
04-14 09:11:14.037 I/WindowManager( 143): Setting rotation to 1, animFlags=1
04-14 09:11:14.047 I/WindowManager( 143): Config changed: { scale=1.0 imsi=0/0 loc=en_US touch=3 keys=2/1/1 nav=3 orien=2 layout=18}
04-14 09:11:14.047 I/ActivityManager( 143): Config changed: { scale=1.0 imsi=310/260 loc=en_US touch=3 keys=2/1/1 nav=3 orien=2 layout=18}
04-14 09:11:14.557 D/dalvikvm( 1984): GC freed 235 objects / 10976 bytes in 205ms
04-14 09:11:14.577 I/dalvikvm-heap( 1984): Grow heap (frag case) to 6.055MB for 1360016-byte allocation
04-14 09:11:14.717 D/dalvikvm( 1984): GC freed 43 objects / 901640 bytes in 136ms
04-14 09:11:14.767 I/ActivityManager( 143): Process android.process.media (pid 332) has died.
04-14 09:11:15.807 D/su ( 1995): 10014:10014 /system/bin/sh executing 0:0 /system/bin/sh
04-14 09:11:16.967 D/dalvikvm( 143): GC freed 11326 objects / 677736 bytes in 238ms
04-14 09:11:19.877 D/dalvikvm( 185): GC freed 65 objects / 2576 bytes in 138ms

Calendar notification not working

Just recently noticed that my calendar music notifications aren't triggering, the alert shows but the tone i selected doesn't play

anyone?
I've logged a call with HTC as I''m still running stock ROM but thought someone here would have a few ideas..

mtrax said:
anyone?
I've logged a call with HTC as I''m still running stock ROM but thought someone here would have a few ideas..
Click to expand...
Click to collapse
I created a test event can copied the system log
Can any one compare with a working phone.
D/AlertReceiver( 323): beginStartingService
D/AlertService( 323): allDay:false instanceBegin=1282114948000 minutes=5 alarmTime=1282114648000
D/BT HS/HF( 146): gsmAsuToSignal=19
D/dalvikvm( 323): GC freed 7567 objects / 442728 bytes in 107ms
D/AlertService( 323): >>>>>>> makeNewAlertNotification <<<<<<<
D/AlertService( 323): >>>>>>> eventId:296 <<<<<<<
D/AlertService( 323): >>>>>>> title:Hello <<<<<<<
I/AlertService( 323): get calendarId:5
I/AlertService( 323): Type:0 Vibrate:true Ringtone:content://media/internal/audio/media/23 <<< New Setting
D/NotificationFlashLightUtility getIncomingCall( 323): load success~~~~~~~~~~
V/AlertService( 323): changeNotificationSound: false
V/AlertService( 323): notification.sound != null: null
V/AlertService( 323): reminderType: 0
I/ActivityManager( 80): Starting activity: Intent { flg=0x10000000 cmp=com.htc.calendar/.AlertActivity }
Click to expand...
Click to collapse

Hi there pal!
I've got the same problem, my notifications don't show up in a notification bar ... any reminding whatsoever ...
I'm running stock rom as well ... if you figure out more I'd be glad for more info.
The think is, I'm just new to the android platform, so I can't really think of anything

latorante said:
Hi there pal!
I've got the same problem, my notifications don't show up in a notification bar ... any reminding whatsoever ...
I'm running stock rom as well ... if you figure out more I'd be glad for more info.
The think is, I'm just new to the android platform, so I can't really think of anything
Click to expand...
Click to collapse
yours might be a different problem as I see the notifications but it doesn't play the ringtone.
I extracted the syslog using the following App ( http://www.appbrain.com/app/org.jtb.alogcat) you might try using this immediately after you expect your calendar alarm.. to see what message show..

Tell you what, I've done some research on my Legend and it seems, that all calendrs work except the facebook one - the birthday notifications. And thats the one I was interested in...
I'll try the program you posted ...
cheers

Can someone run a quick test for me please?
Set a ringtone on a Calender alert
1. Open the Calendar application.
2. Press Menu then More then Settings.
3. Tap on Reminder settings.
4. Make sure that there is a tick mark on “All calendars.”
5. Tap on Set alerts & notifications and select Alert.
6. Tap on Select ringtone and tap the ring tone that you prefer.
Then set a calender event and when it triggers the ringtone should play.
If could send me the snippet of the system log so I can compare with mine,
thanks

I got a working one:
/AudioHardwareMSM72XX( 57): AUDIO_START: start kernel pcm_out driver.
D/AlertReceiver(12956): beginStartingService
D/AlertService(12956): allDay:false instanceBegin=1282455968000 minutes=5 alarmTime=1282455668000
D/AlertService(12956): >>>>>>> makeNewAlertNotification <<<<<<<
D/AlertService(12956): >>>>>>> eventId:721 <<<<<<<
D/AlertService(12956): >>>>>>> title:Test <<<<<<<
I/AlertService(12956): get calendarId:1
I/AlertService(12956): Type:0 Vibrate:true Ringtone:content://media/internal/audio/media/49 <<< New Setting
D/NotificationFlashLightUtility getIncomingCall(12956): load fail~~~~~~~~~~
V/AlertService(12956): changeNotificationSound: false
V/AlertService(12956): notification.sound != null: content://media/internal/audio/media/49
V/AlertService(12956): reminderType: 0
I/ActivityManager( 79): Starting activity: Intent { flg=0x10000000 cmp=com.htc.calendar/.AlertActivity }
D/MediaPlayer( 79): setDataSource(291, 0, 576460752303423487) pid = 79
D/PVPlayer( 57): setDataSource(31, 0, 11183)
I/AlertActivity(12956): mCursor.count: 1
I/PlayerDriver( 57): OpenCore enable firewall payload
I/ ( 57): OpenCore codec name PVMFOMXAudioDecNode , OMX.PV.mp3dec
W/MediaPlayer( 79): info/warning (1, 44)
I/AudioPolicyService( 57): startOutput(): before lock
W/NotificationService( 79): Notification sound delayed by 1211msecs
I/ActivityManager( 79): Displayed activity com.htc.calendar/.AlertActivity: 1401 ms (total 1401 ms)
I/AudioPolicyService( 57): stopOutput(): before lock
D/BT HS/HF_S( 153): gsmAsuToSignal=5
Click to expand...
Click to collapse
my log seems to vary slightly yours has:
V/AlertService(12956): notification.sound != null: content://media/internal/audio/media/49
where as mine has:
V/AlertService( 323): notification.sound != null: null

Wimax 4G won't start up (logcat in post)

Wimax won't start since I went to ACS from dk28 quantum. No idea why. Anyone?
Edit: Sorry this post is a little sloppy. 2 dif logs but I don't think the one in this post will help. Yes I had 4g with dk28 (quantum rom). No matter what version of acs ..eb13 or ec05 or flashin is fixing this. I really don't want to go back to stock. Hoping for some insight before I take the last resort.
Log Collector version: 1.1.0
Device model: SPH-D700
Firmware version: 2.2.1
Kernel version: 2.6.32.9
[email protected] )
#1 Sat Mar 26 23:06:04 CDT 2011
Build number: SRF 1.1.0/Twilight Zone 1.1.0
ng/com.android.vending.TabbedAppBrowser paused=false}
03-30 21:25:43.809 V/InputDevice( 2908): ID[0]=0(0) Up(1=>0)
03-30 21:25:46.476 D/BatteryService( 2908): update start
03-30 21:25:46.506 D/BatteryService( 2908): updateBattery level:27 scale:100 status:4 health:2 present:true voltage: 3671 temperature: 270 technology: Li-ion AC powered:false USB powered:false icon:17302163
03-30 21:25:46.553 V/InputDevice( 2908): ID[0]=0(0) Dn(0=>1)
03-30 21:25:46.556 V/WindowManager( 2908): Dsptch > Window{48448308 com.android.vending/com.android.vending.TabbedAppBrowser paused=false}
03-30 21:25:46.576 D/SyncmlService( 2987): mBatteryReceiver: action - android.intent.action.BATTERY_CHANGED
03-30 21:25:46.599 V/NotificationService( 2908): notification manager receiver action = android.intent.action.BA

D/alogcat ( 6016): stopped
D/alogcat ( 6016): starting ...
V/WindowManager( 2908): Dsptch > Window{483ca3a0 StatusBar paused=false}
I/NotificationService( 2908): mScreenOn: true, mNotificationPulseEnabled: true, mInCall: false
I/NotificationService( 2908): turning off
I/NotificationService( 2908): mScreenOn: true, mNotificationPulseEnabled: true, mInCall: false
I/NotificationService( 2908): turning off
V/WindowManager( 2908): Dsptch > Window{483ca3a0 StatusBar paused=false}
V/WindowManager( 2908): Dsptch > Window{484038e0 StatusBarExpanded paused=false}
V/WindowManager( 2908): Dsptch > Window{484038e0 StatusBarExpanded paused=false}
I/WimaxService( 2908): ------WakeLock will be acquired----------------
D/WimaxService( 2908): + Received { what=0 when=4281182 arg1=1 arg2=1000 }
I/WimaxService( 2908): [setWimaxEnabledBlocking] Workmode = 0
I/WimaxHandler( 4958): WimaxStateReceiver: android.net.wimax.WIMAX_STATUS_CHANGED
I/WimaxHandler( 4958): WimaxStateReceiver: Wimax Status 2
I/WimaxService( 2908): wimax ON ---mModeWhieAPsleep = 1 mModemReset = false mEnableUSB = false mIsDMmode = false mbUSBTethered = false
D/StatusBarPolicy( 2908): received mWimaxStatus: 2
D/SyncManager( 2908): failed sync operation authority: gmail-ls account: Account {[email protected], type=com.google} extras: [ignore_settings=true sendwithoutsync=true ignore_backoff=true sendwithoutsyncMessageId=1364762305589411840 force=true expedited=true sendwithoutsyncConversationId=1364762305589411840 ] syncSource: 3 when: 7048379 expedited: true, SyncResult: stats [ numIoExceptions: 1]
D/SyncmlService( 2987): mBatteryReceiver: action - android.intent.action.BATTERY_CHANGED
V/NotificationService( 2908): notification manager receiver action = android.intent.action.BATTERY_CHANGED
W/PowerManagerService( 2908): Timer 0x7->0x3|0x0
D/SyncmlService( 2987): mBatteryReceiver: action - android.intent.action.BATTERY_CHANGED
V/NotificationService( 2908): notification manager receiver action = android.intent.action.BATTERY_CHANGED
D/dalvikvm( 6016): GC_FOR_MALLOC freed 5763 objects / 738616 bytes in 31ms
D/SyncmlService( 2987): mBatteryReceiver: action - android.intent.action.BATTERY_CHANGED
V/NotificationService( 2908): notification manager receiver action = android.intent.action.BATTERY_CHANGED
E/WimaxService( 2908): Failed to start Wimax.
D/StatusBarPolicy( 2908): received mWimaxStatus: 4
I/WimaxService( 2908): ------release WakeLock----------------
I/WimaxHandler( 4958): WimaxStateReceiver: android.net.wimax.WIMAX_STATUS_CHANGED
I/WimaxHandler( 4958): WimaxStateReceiver: Wimax Status 4
D/SyncmlService( 2987): mBatteryReceiver: action - android.intent.action.BATTERY_CHANGED
V/NotificationService( 2908): notification manager receiver action = android.intent.action.BATTERY_CHANGED
V/WindowManager( 2908): Dsptch > Window{483f6c58 TrackingView paused=false}
V/WindowManager( 2908): Dsptch > Window{483f6c58 TrackingView paused=false}
E/imdg81* ( 2908): IsShutDownStarted()
E/imdg81* ( 2908): IsShutDownStarted()
V/WindowManager( 2908): Dsptch > Window{484e5808 AtchDlgrg.jtb.alogcat/org.jtb.alogcat.LogActivity paused=false}

Problem with Gnuplot and Octave

I have just installed Gnuplot and Octave from Internet using APK packages.
They are called from and work under Android Terminal Emulator. I updated ATE to the last version (the one that is on the project page) as Gnuplot and Octave requested.
I searched for the last versions of those ones. They installed OK
But there is a little issue. So little issue.
WHEN I RUN THEM, THEY MAKE MY NOOK REBOOT.
What can be the problem?
I make the question in this forum 'cause the last week people from here helped me to pimp my Nook. It's so useful now
Although everybody knows that one is not satisfied ever
I wanted to install Octave and Gnuplot. Those two programs would be really useful to me. Gnuplot to graph some functions and data.
Octave to analyze data and make Dynamical Systems and graph them after.
I ask you for the issue of the reboot.
I have though it would be a Memory Dump, but I don't know.
Another tip. They run under ATE. I don't know if that info is useful....
Specs of my device:
1.2.1 Operating System rooted with Nook Manager.
Nook Simple Touch.
I downloaded Octave 3.7.0 and Droidplot (Gnuplot for Android) 0.0.6. The ones who are in Google Play Store.
They should work because of the Android Version, but the don't

serpastor said:
I have just installed Gnuplot and Octave from Internet using APK packages.
They are called from and work under Android Terminal Emulator. I updated ATE to the last version (the one that is on the project page) as Gnuplot and Octave requested.
I searched for the last versions of those ones. They installed OK
But there is a little issue. So little issue.
WHEN I RUN THEM, THEY MAKE MY NOOK REBOOT.
What can be the problem?
I make the question in this forum 'cause the last week people from here helped me to pimp my Nook. It's so useful now
Although everybody knows that one is not satisfied ever
I wanted to install Octave and Gnuplot. Those two programs would be really useful to me. Gnuplot to graph some functions and data.
Octave to analyze data and make Dynamical Systems and graph them after.
I ask you for the issue of the reboot.
I have though it would be a Memory Dump, but I don't know.
Another tip. They run under ATE. I don't know if that info is useful....
Specs of my device:
1.2.1 Operating System rooted with Nook Manager.
Nook Simple Touch.
I downloaded Octave 3.7.0 and Droidplot (Gnuplot for Android) 0.0.6. The ones who are in Google Play Store.
They should work because of the Android Version, but the don't
Click to expand...
Click to collapse
Connect your NOOK to PC and establish ADB connection.
- ADB shell
- logcat
- run problematic APK on nook
- copy logcat content to your PC
- post logcat output in this thread
How else can we know why some apk is rebooting your NOOK?
(INB4 how to use ADB -> google + search through this forum)

Thanks, but....
osowiecki said:
Connect your NOOK to PC and establish ADB connection.
- ADB shell
- logcat
- run problematic APK on nook
- copy logcat content to your PC
- post logcat output in this thread
How else can we know why some apk is rebooting your NOOK?
(INB4 how to use ADB -> google + search through this forum)
Click to expand...
Click to collapse
I have just installed Android SDK on my Debian Wheezy desktop PC.
When I invoke "adb devices" as Google says, I get
Code:
[email protected]:~# adb devices
List of devices attached
[email protected]:~#
Even being superuser.
Of course, I can't access the device. It's not recognized by ADB
I have read that ADB only works when the device is recognized by the framework (obviously). This is not the case.
On the other hand, I realized Opera Mini doesn't download anything.
I recently installed Swapper, and made a Swap partition on the SD Card. I configured Sapper to access directly the swap partition, that is the second partition in the SD Card. It's already configured.
I have this little problem.
Thanks for ur attention. Excuse me 'cause I didn't answer you anything in the last days. I was quite busy.
PD: I've tried also connect the device and invoke adb with the device powered down. It didn't work either....

As expected, here's the logcat by adb for Droidplot and Octave
I did what you say (the logcat in de adb shell) connecting the NST with the computer by wireless connection.
That one was the only one who worked....
The logcat left this:
Code:
I/ActivityManager( 786): Starting activity: Intent { act=android.intent.action.
MAIN cat=[android.intent.category.LAUNCHER] flg=0x14000000 cmp=com.octave/.octav
eMain }
I/ActivityManager( 786): Start proc com.octave for activity com.octave/.octaveM
ain: pid=1507 uid=10027 gids={1015, 3003}
E/TC ( 1052): KPICollector: 1371330534540 platform process_start {"processN
ame":"com.octave"}
I/dalvikvm( 1507): Debugger thread not active, ignoring DDM send (t=0x41504e4d l
=38)
E/TC ( 1052): KPICollector: 1371330534627 ActivityManager background {"comp
onent":"com.harasoft.relaunch/.AllApplications"}
E/TC ( 1052): KPICollector: 1371330534631 ActivityManager foreground {"comp
onent":"com.octave/.octaveMain"}
I/dalvikvm( 1507): Debugger thread not active, ignoring DDM send (t=0x41504e4d l
=24)
D/dalvikvm( 1507): GC freed 2173 objects / 137456 bytes in 58ms
V/Activity( 1507): performResume()
D/EPD#ActivityResume( 786): resetRegion 4
D/NATIVE-EPD( 786): epd_reset_region: 0x10
D/EPD#ActivityResume( 786): resetRegion 5
D/NATIVE-EPD( 786): epd_reset_region: 0x20
D/EPD#ActivityResume( 786): resetRegion 6
D/NATIVE-EPD( 786): epd_reset_region: 0x40
D/EPD#ActivityResume( 786): resetRegion 7
D/NATIVE-EPD( 786): epd_reset_region: 0x80
D/EPD#ActivityResume( 786): Disable EPD for 350ms!!!!!!!!
D/EPD#Dialog( 786): set region 2 10 = 0,0 -> 600,800 = GU
D/NATIVE-EPD( 786): epd_set_region: 2 (0,0,600,800) 1,0 10
I/ActivityManager( 786): Starting activity: Intent { cmp=com.droidplot/.droidpl
otMain (has extras) }
D/EPD#Dialog( 786): resetRegion 2
D/NATIVE-EPD( 786): epd_reset_region: 0x04
D/EPD#Dialog( 786): Disable EPD for 100ms!!!!!!!!
I/ActivityManager( 786): Start proc com.droidplot for activity com.droidplot/.d
roidplotMain: pid=1515 uid=10027 gids={1015, 3003}
E/TC ( 1052): KPICollector: 1371330535164 platform process_start {"processN
ame":"com.droidplot"}
W/InputManagerService( 786): Window already focused, ignoring focus gain of: co
[email protected]
D/SurfaceFlinger( 786): Frame buffer posted; elapsed time = 12 msecs
I/dalvikvm( 1515): Debugger thread not active, ignoring DDM send (t=0x41504e4d l
=38)
E/TC ( 1052): KPICollector: 1371330535259 ActivityManager background {"comp
onent":"com.octave/.octaveMain"}
E/TC ( 1052): KPICollector: 1371330535271 ActivityManager foreground {"comp
onent":"com.droidplot/.droidplotMain"}
I/dalvikvm( 1515): Debugger thread not active, ignoring DDM send (t=0x41504e4d l
=30)
D/SurfaceFlinger( 786): Frame buffer posted; elapsed time = 29 msecs
V/Activity( 1515): performResume()
D/EPD#ActivityResume( 786): resetRegion 4
D/NATIVE-EPD( 786): epd_reset_region: 0x10
D/EPD#ActivityResume( 786): resetRegion 5
D/NATIVE-EPD( 786): epd_reset_region: 0x20
D/EPD#ActivityResume( 786): resetRegion 6
D/NATIVE-EPD( 786): epd_reset_region: 0x40
D/EPD#ActivityResume( 786): resetRegion 7
D/NATIVE-EPD( 786): epd_reset_region: 0x80
D/EPD#ActivityResume( 786): Disable EPD for 350ms!!!!!!!!
D/EPD#Dialog( 786): set region 2 10 = 0,0 -> 600,800 = GU
D/NATIVE-EPD( 786): epd_set_region: 2 (0,0,600,800) 1,0 10
I/global ( 1515): Default buffer size used in BufferedWriter constructor. It wo
uld be better to be explicit if an 8k-char buffer is required.
D/EPD#Dialog( 786): resetRegion 2
D/NATIVE-EPD( 786): epd_reset_region: 0x04
D/EPD#Dialog( 786): Disable EPD for 100ms!!!!!!!!
E/TC ( 1052): KPICollector: 1371330535600 ActivityManager background {"comp
onent":"com.droidplot/.droidplotMain"}
I/ActivityManager( 786): Displayed activity com.octave/.octaveMain: 1106 ms (to
tal 1106 ms)
I/ActivityManager( 786): Displayed activity com.droidplot/.droidplotMain: 544 m
s (total 544 ms)
E/TC ( 1052): KPICollector: 1371330535610 ActivityManager foreground {"comp
onent":"com.octave/.octaveMain"}
D/SurfaceFlinger( 786): Frame buffer posted; elapsed time = 76 msecs
D/EPD#Dialog( 786): set region 2 10 = 0,0 -> 600,800 = GU
D/NATIVE-EPD( 786): epd_set_region: 2 (0,0,600,800) 1,0 10
V/Activity( 1507): performResume()
D/EPD#ActivityResume( 786): resetRegion 4
D/NATIVE-EPD( 786): epd_reset_region: 0x10
D/EPD#ActivityResume( 786): resetRegion 5
D/NATIVE-EPD( 786): epd_reset_region: 0x20
D/EPD#ActivityResume( 786): resetRegion 6
D/NATIVE-EPD( 786): epd_reset_region: 0x40
D/EPD#ActivityResume( 786): resetRegion 7
D/NATIVE-EPD( 786): epd_reset_region: 0x80
D/EPD#ActivityResume( 786): Disable EPD for 350ms!!!!!!!!
D/SurfaceFlinger( 786): Frame buffer posted; elapsed time = 45 msecs
D/SurfaceFlinger( 786): Frame buffer posted; elapsed time = 30 msecs
D/SurfaceFlinger( 786): Frame buffer posted; elapsed time = 20 msecs
W/ActivityManager( 786): Duplicate finish request for HistoryRecord{4a05d100 co
m.droidplot/.droidplotMain}
D/SurfaceFlinger( 786): Frame buffer posted; elapsed time = 17 msecs
D/SurfaceFlinger( 786): Frame buffer posted; elapsed time = 19 msecs
I/PowerManagerService( 786): setPowerState: mPowerState=0x3 newState=0x3 noChan
geLights=false reason=1
D/WifiService( 786): ACTION_BATTERY_CHANGED pluggedType: 0
I/PowerManagerService( 786): setPowerState: mPowerState=0x3 newState=0x3 noChan
geLights=false reason=1
I/PowerManagerService( 786): setPowerState: mPowerState=0x3 newState=0x3 noChan
geLights=false reason=1
I/PowerManagerService( 786): setPowerState: mPowerState=0x3 newState=0x3 noChan
geLights=false reason=1
I/NotificationService( 786): enqueueToast pkg=com.octave callback=android.app.I
[email protected] duration=1
I/ActivityManager( 786): Starting activity: Intent { act=jackpal.androidterm.OP
EN_NEW_WINDOW cat=[android.intent.category.DEFAULT] cmp=com.octave/jackpal.andro
idterm.RemoteInterface }
D/EPD#Dialog( 786): resetRegion 2
D/NATIVE-EPD( 786): epd_reset_region: 0x04
D/EPD#Dialog( 786): Disable EPD for 100ms!!!!!!!!
D/EPD#Toast( 786): set region 0 1 = 0,0 -> 600,800 = GU
D/NATIVE-EPD( 786): epd_set_region: 0 (0,0,600,800) 1,0 1
I/PowerManagerService( 786): setPowerState: mPowerState=0x3 newState=0x3 noChan
geLights=false reason=2
D/SurfaceFlinger( 786): Frame buffer posted; elapsed time = 24 msecs
V/Activity( 1507): performResume()
D/EPD#ActivityResume( 786): resetRegion 4
D/NATIVE-EPD( 786): epd_reset_region: 0x10
D/EPD#ActivityResume( 786): resetRegion 5
D/NATIVE-EPD( 786): epd_reset_region: 0x20
D/EPD#ActivityResume( 786): resetRegion 6
D/NATIVE-EPD( 786): epd_reset_region: 0x40
D/EPD#ActivityResume( 786): resetRegion 7
D/NATIVE-EPD( 786): epd_reset_region: 0x80
D/EPD#ActivityResume( 786): Disable EPD for 350ms!!!!!!!!
D/Term ( 1507): TermService started
I/TermService( 1507): Activity called onBind()
I/TermService( 1507): Activity binding to service
D/dalvikvm( 1507): Trying to load lib /data/data/com.octave/lib/libjackpal-andro
idterm4.so 0x49fb2f60
D/dalvikvm( 1507): Added shared lib /data/data/com.octave/lib/libjackpal-android
term4.so 0x49fb2f60
I/libjackpal-androidterm( 1507): JNI_OnLoad
D/dalvikvm( 1507): Trying to load lib /data/data/com.octave/lib/libjackpal-andro
idterm4.so 0x49fb2f60
D/dalvikvm( 1507): Shared lib '/data/data/com.octave/lib/libjackpal-androidterm4
.so' already loaded in same CL 0x49fb2f60
I/ActivityManager( 786): Starting activity: Intent { act=jackpal.androidterm.pr
ivate.libB.OPEN_NEW_WINDOW cat=[android.intent.category.DEFAULT] flg=0x10000000
cmp=com.octave/.TermInternal }
D/dalvikvm( 1507): GC freed 3668 objects / 206576 bytes in 55ms
E/Term ( 1507): onCreate
V/Activity( 1507): performResume()
D/EPD#ActivityResume( 786): resetRegion 4
D/NATIVE-EPD( 786): epd_reset_region: 0x10
D/EPD#ActivityResume( 786): resetRegion 5
D/NATIVE-EPD( 786): epd_reset_region: 0x20
D/EPD#ActivityResume( 786): resetRegion 6
D/NATIVE-EPD( 786): epd_reset_region: 0x40
D/EPD#ActivityResume( 786): resetRegion 7
D/NATIVE-EPD( 786): epd_reset_region: 0x80
D/EPD#ActivityResume( 786): Disable EPD for 350ms!!!!!!!!
I/Term ( 1507): Bound to TermService
I/TermService( 1507): Activity binding to service
I/NotificationService( 786): enqueueToast pkg=com.octave callback=android.app.I
[email protected] duration=0
D/ViewFlipper( 1507): updateRunning() mVisible=true, mStarted=false, mUserPresen
t=true, mRunning=false
I/ActivityManager( 786): Displayed activity com.octave/.TermInternal: 140 ms (t
otal 354 ms)
I/ActivityManager( 786): Displayed activity com.octave/jackpal.androidterm.Remo
teInterface: 378 ms (total 378 ms)
D/SurfaceFlinger( 786): Frame buffer posted; elapsed time = 20 msecs
I/Term ( 1507): waiting for: 1527
D/SurfaceFlinger( 786): Frame buffer posted; elapsed time = 12 msecs
D/SurfaceFlinger( 786): Frame buffer posted; elapsed time = 16 msecs
D/SurfaceFlinger( 786): Frame buffer posted; elapsed time = 19 msecs
D/SurfaceFlinger( 786): Frame buffer posted; elapsed time = 14 msecs
Then the device rebooted (this was trying to run GNU Octave).
After that, naturally, adb stopped making the log.
It was disconnected when the device reboot.
I don't know what does this mean. I'd want to know the meaning of those "Frame buffer *". It could be the answer.
With droidplot, running the program leaves the same result.
Here's the log by logcat for "droidplot", wich is GNUplot for the Android Platform:
Code:
I/ActivityManager( 786): Starting activity: Intent { act=android.intent.action.
MAIN cat=[android.intent.category.LAUNCHER] flg=0x14000000 cmp=com.droidplot/.dr
oidplotMain }
I/ActivityManager( 786): Start proc com.droidplot for activity com.droidplot/.d
roidplotMain: pid=1653 uid=10027 gids={1015, 3003}
E/TC ( 1032): KPICollector: 1371332712292 platform process_start {"processN
ame":"com.droidplot"}
I/dalvikvm( 1653): Debugger thread not active, ignoring DDM send (t=0x41504e4d l
=38)
E/TC ( 1032): KPICollector: 1371332712359 ActivityManager background {"comp
onent":"com.harasoft.relaunch/.AllApplications"}
E/TC ( 1032): KPICollector: 1371332712363 ActivityManager foreground {"comp
onent":"com.droidplot/.droidplotMain"}
I/dalvikvm( 1653): Debugger thread not active, ignoring DDM send (t=0x41504e4d l
=30)
V/Activity( 1653): performResume()
D/EPD#ActivityResume( 786): resetRegion 4
D/NATIVE-EPD( 786): epd_reset_region: 0x10
D/EPD#ActivityResume( 786): resetRegion 5
D/NATIVE-EPD( 786): epd_reset_region: 0x20
D/EPD#ActivityResume( 786): resetRegion 6
D/NATIVE-EPD( 786): epd_reset_region: 0x40
D/EPD#ActivityResume( 786): resetRegion 7
D/NATIVE-EPD( 786): epd_reset_region: 0x80
D/EPD#ActivityResume( 786): Disable EPD for 350ms!!!!!!!!
D/EPD#Dialog( 786): set region 2 10 = 0,0 -> 600,800 = GU
D/NATIVE-EPD( 786): epd_set_region: 2 (0,0,600,800) 1,0 10
I/global ( 1653): Default buffer size used in BufferedWriter constructor. It wo
uld be better to be explicit if an 8k-char buffer is required.
I/ActivityManager( 786): Starting activity: Intent { act=jackpal.androidterm.RU
N_SCRIPT cat=[android.intent.category.DEFAULT] cmp=jackpal.androidterm/.RunScrip
t (has extras) }
D/EPD#Dialog( 786): resetRegion 2
D/NATIVE-EPD( 786): epd_reset_region: 0x04
D/EPD#Dialog( 786): Disable EPD for 100ms!!!!!!!!
D/SurfaceFlinger( 786): Frame buffer posted; elapsed time = 12 msecs
I/ActivityManager( 786): Start proc jackpal.androidterm for activity jackpal.an
droidterm/.RunScript: pid=1663 uid=10024 gids={3003, 1015}
E/TC ( 1032): KPICollector: 1371332712733 platform process_start {"processN
ame":"jackpal.androidterm"}
W/InputManagerService( 786): Window already focused, ignoring focus gain of: co
[email protected]
I/dalvikvm( 1663): Debugger thread not active, ignoring DDM send (t=0x41504e4d l
=38)
E/TC ( 1032): KPICollector: 1371332712800 ActivityManager background {"comp
onent":"com.droidplot/.droidplotMain"}
E/TC ( 1032): KPICollector: 1371332712813 ActivityManager foreground {"comp
onent":"jackpal.androidterm/.RunScript"}
I/dalvikvm( 1663): Debugger thread not active, ignoring DDM send (t=0x41504e4d l
=42)
D/SurfaceFlinger( 786): Frame buffer posted; elapsed time = 23 msecs
V/Activity( 1663): performResume()
D/EPD#ActivityResume( 786): resetRegion 4
D/NATIVE-EPD( 786): epd_reset_region: 0x10
D/EPD#ActivityResume( 786): resetRegion 5
D/NATIVE-EPD( 786): epd_reset_region: 0x20
D/EPD#ActivityResume( 786): resetRegion 6
D/NATIVE-EPD( 786): epd_reset_region: 0x40
D/EPD#ActivityResume( 786): resetRegion 7
D/NATIVE-EPD( 786): epd_reset_region: 0x80
D/EPD#ActivityResume( 786): Disable EPD for 350ms!!!!!!!!
D/Term ( 1663): TermService started
I/TermService( 1663): Activity called onBind()
I/TermService( 1663): Activity binding to service
D/dalvikvm( 1663): Trying to load lib /data/data/jackpal.androidterm/lib/libjack
pal-androidterm4.so 0x49fb3360
D/dalvikvm( 1663): Added shared lib /data/data/jackpal.androidterm/lib/libjackpa
l-androidterm4.so 0x49fb3360
I/libjackpal-androidterm( 1663): JNI_OnLoad
D/dalvikvm( 1663): Trying to load lib /data/data/jackpal.androidterm/lib/libjack
pal-androidterm4.so 0x49fb3360
D/dalvikvm( 1663): Shared lib '/data/data/jackpal.androidterm/lib/libjackpal-and
roidterm4.so' already loaded in same CL 0x49fb3360
I/ActivityManager( 786): Starting activity: Intent { act=jackpal.androidterm.pr
ivate.OPEN_NEW_WINDOW cat=[android.intent.category.DEFAULT] flg=0x10000000 cmp=j
ackpal.androidterm/.TermInternal }
E/Term ( 1663): onCreate
D/SurfaceFlinger( 786): Frame buffer posted; elapsed time = 19 msecs
D/SurfaceFlinger( 786): Frame buffer posted; elapsed time = 13 msecs
I/WindowManager( 786): Setting rotation to 1, animFlags=0
I/ActivityManager( 786): Config changed: { scale=1.0 imsi=0/0 loc=en_US touch=3
keys=1/1/2 nav=1/1 orien=2(1) layout=19}
I/ActivityManager( 786): Displayed activity jackpal.androidterm/.RunScript: 556
ms (total 998 ms)
V/Activity( 1663): performResume()
D/EPD#ActivityResume( 786): resetRegion 4
D/NATIVE-EPD( 786): epd_reset_region: 0x10
D/EPD#ActivityResume( 786): resetRegion 5
D/NATIVE-EPD( 786): epd_reset_region: 0x20
D/EPD#ActivityResume( 786): resetRegion 6
D/NATIVE-EPD( 786): epd_reset_region: 0x40
D/EPD#ActivityResume( 786): resetRegion 7
D/NATIVE-EPD( 786): epd_reset_region: 0x80
D/EPD#ActivityResume( 786): Disable EPD for 350ms!!!!!!!!
I/Term ( 1663): Bound to TermService
I/TermService( 1663): Activity binding to service
I/NotificationService( 786): enqueueToast pkg=jackpal.androidterm callback=andr
[email protected] duration=0
D/ViewFlipper( 1663): updateRunning() mVisible=true, mStarted=false, mUserPresen
t=true, mRunning=false
D/EPD#StatusBar( 786): resetRegion 3
D/NATIVE-EPD( 786): epd_reset_region: 0x08
D/EPD#StatusBar( 786): Disable EPD for 150ms!!!!!!!!
W/ResourceType( 786): Resources don't contain package for resource number 0x7f0
3001e
W/ResourceType( 786): Resources don't contain package for resource number 0x7f0
30003
W/ResourceType( 786): Resources don't contain package for resource number 0x7f0
30010
W/ResourceType( 786): Resources don't contain package for resource number 0x7f0
30014
W/ResourceType( 786): Resources don't contain package for resource number 0x7f0
3004f
W/ResourceType( 786): Resources don't contain package for resource number 0x7f0
30000
I/Term ( 1663): waiting for: 1671
W/ResourceType( 786): Resources don't contain package for resource number 0x7f0
30012
D/dalvikvm( 1663): GC freed 3595 objects / 240440 bytes in 62ms
D/EPD#Toast( 786): set region 0 1 = 0,0 -> 600,800 = GU
D/NATIVE-EPD( 786): epd_set_region: 0 (0,0,600,800) 1,0 1
I/ActivityManager( 786): Displayed activity jackpal.androidterm/.TermInternal:
450 ms (total 450 ms)
I/PowerManagerService( 786): setPowerState: mPowerState=0x3 newState=0x3 noChan
geLights=false reason=2
D/SurfaceFlinger( 786): Frame buffer posted; elapsed time = 17 msecs
D/SurfaceFlinger( 786): Frame buffer posted; elapsed time = 12 msecs
D/SurfaceFlinger( 786): Frame buffer posted; elapsed time = 20 msecs
D/SurfaceFlinger( 786): Frame buffer posted; elapsed time = 19 msecs
Then Nook Touch rebooted....

Further info
osowiecki said:
Connect your NOOK to PC and establish ADB connection.
- ADB shell
- logcat
- run problematic APK on nook
- copy logcat content to your PC
- post logcat output in this thread
How else can we know why some apk is rebooting your NOOK?
(INB4 how to use ADB -> google + search through this forum)
Click to expand...
Click to collapse
I have already posted the logcat by ADB shell. Nobody answered me. Don't matter.
I'm here again to post that I installed Droidplot and Octave in my mother's smartphone, that works under Android 2.2.3, while Nook Touch's OS is Android 2.1 based.
There's another clue to solve this problem.
I realized that those programs ran very well on the smartphone. I haven't to change the permissions of the libraries as I have to in my Nook Touch.
After the installation, without anything else than running Android Terminal Emulator (that thing was actually done by Octave), I saw Octave console!
The message shown by ATE on the Nook Simple Touch when Octave is invoked from the ReLaunch menu is this one:
Code:
$ umask 000; cd /data/data/com.octave/; /data/data/com.octave/freeRoot/lib/ld-linux.so.3 --library-path /data/data/com.octave/freeRoot/lib: /data/data/com.octave/freeRoot/usr/local/lib /data/data/com.octave/freeRoot/bin/octave
/data/data/com.octave/freeRoot/lib/ld-linux.so.3: permission denied
$
The message shown when DroidPlot (again on the Nook Touch) is invoked is:
Code:
$
/data/data/com.droidplot/bin/droidplot
$ /data/data/com.droidplot/bin/droidplot: permission denied
Those message do not appear on my mother's Motorola smartphone.
I hope this can help