search

fangkaow / android-os-monitor

Automatically exported from code.google.com/p/android-os-monitor
0 stars 0 forks source link

content of tabs is empty #45

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Build OSMonitor with sources 3.0.6.5 and ActionBarSherlock 4.3.1
2. Push it on the target (Android 2.3.3)
3. Launch it

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

Expected : 
Application working as it works when installing the application with 
OSMonitor-3.0.6.5.apk available on git repository 
(http://code.google.com/p/android-os-monitor/downloads/list)

Instead : 
Application doesn't work fully. Some tab content (Process,Connection,Message) 
are empty. 
About Misc tab, it is not fully empty : Tab category are printed 
(System,Battery,CPU,...) but its content have no data, 
just fields are printed (Memory for example : Total, Free, Cached and Buffered 
are printed but there is no  amount data printed).

What version of the product are you using? On what operating system?

Version product : 
OSMonitor sources : 3.0.6.5
ActionBarSherlock : 4.3.1

Operating system:
Android 2.3.3

Please provide any additional information below.
Extract of Logcat attached : 
beginning of logcat extract corresponds at the moment when I launched the 
application
At the beggining, the application was on Process tab and I have selected 
Message tab.
That's all I have done.

Original issue reported on code.google.com by dev.embe...@gmail.com on 4 Jul 2013 at 10:15

Attachments:

GoogleCodeExporter commented 9 years ago 
Problem solved : The executable osmcore was not compiled and so not included in 
the APK.

To solve the problem :

-build osmcore with android ndk 
For Android 4.2 the ndk r8e can be used directly
For android 2.3.3 the ndk r5b must be used (need to delete the line "APP_ABI := 
armeabi x86" in jni/Application.mk to be able compiling)

-osmcore is created in libs/armeabi/osmcore. Move it in assets directory and 
rename it in osmcore_arm

-Build the APK normaly (osmcore_arm will be automaticaly included in the APK) 
and  install the APK on the target. It should works!

Original comment by dev.embe...@gmail.com on 11 Jul 2013 at 7:58

GoogleCodeExporter commented 9 years ago 
Sorry for lack reply, I didn't see your post until today, because I didn't 
check this site since moving project to GitHub, your information is very 
useful, I would like to keep it on  issue list.

Thanks!

Original comment by eolw...@gmail.com on 30 Aug 2013 at 5:55

GoogleCodeExporter commented 9 years ago 
Hi,

  I am facing the same issue in the OSMonitor as posted above.    Process,Connection,Message tabs are empty.

I have an Android tablet with OS version : 4.0.4. I built the osmcore using NDK 
r9. The NDK builds the osmcore successfully but the library is not loaded in 
the .apk. I went through the code, the code does not contain 'native' keywords 
nor does it contain System.loadLibrary() function call as explained in the NDK 
docs. 

How do I load the osmcore ?

Thanks in advance.

Original comment by androidD...@gmail.com on 3 Sep 2013 at 8:21

GoogleCodeExporter commented 9 years ago 
Hello,

I don't use JNI anymore, osmcore is not a library, it is a binary execute, you 
can find a file calls install_binary.bat on /jni directory, the batch file will 
do a simple task, after compiling JNI via NDK, osmcore will be generated on 
/libs, batch file will move those files to /assest diectroy.

Exporting  a new apk, those files also are included, when you launch OSMonitor, 
osmcore will be put into /data/data/com.eolwral.osmonitor/files/ and  executed 
via Java. :)

Original comment by eolw...@gmail.com on 15 Sep 2013 at 2:44

GoogleCodeExporter commented 9 years ago 
Encountering the same issue. I use NDK r9, ADT 22.2.1 and ActionBarSherlock 
v4.4.0. I have tried to move osmcore to assest directory but still fail to show 
the contents within tabs, any solution for it?

Original comment by kitton...@gmail.com on 16 Oct 2013 at 3:17

GoogleCodeExporter commented 9 years ago 
I have upgraded my NDK to r9 2 days ago and seen some errors when compiling 
code, because I use some ASM code on sysinfo.S, it can't be compiled on new 
NDK, I am going to fix it now. :)

Original comment by eolw...@gmail.com on 17 Oct 2013 at 9:26

GoogleCodeExporter commented 9 years ago 
I have upgraded the code with NDR r9 and removed ASM code with C function, it 
should work, please fetch the latest source code from Github and try again, if 
you still can't run it on your device,  just tell me. :)

Original comment by eolw...@gmail.com on 23 Oct 2013 at 6:18