简体   繁体   English

是否可以在无根的普通android设备上启用checkjni?

[英]Is it possible to enable checkjni on unrooted normal android device?

I want to enable checkjni on my android device. 我想在我的Android设备上启用checkjni。 However, i am unable to set properties those were given in stackoverflow, because they use "su" or "root". 但是,我无法设置那些在stackoverflow中给定的属性,因为它们使用“ su”或“ root”。

Can't i enable checkjni on the device without root access? 没有root用户访问权限的设备不能启用checkjni吗? I want to see "checkJNI ON" on logcat when i use the device 使用设备时,我想在logcat上看到“ checkJNI ON”

UPDATE: I got these from the device when i unlock the screen of my audio track playing app. 更新:当我解锁音轨播放应用程序的屏幕时,我是从设备上获得这些的。 How can i extend details? 如何扩展细节? I want to enable every checkjni options. 我想启用每个checkjni选项。 This block tells me nothing, or does it? 这个方块告诉我什么,还是没有?

10-26 20:47:16.720: A/libc(18272): Fatal signal 11 (SIGSEGV) at 0x00000078 (code=1)



10-26 20:47:17.145: W/SurfaceView(2094): CHECK surface infomation creating=false formatChanged=false sizeChanged=false visible=false visibleChanged=true surfaceChanged=true realSizeChanged=false redrawNeeded=false left=false top=false
10-26 20:47:17.145: I/SurfaceFlinger(1903): id=1615 Removed SurfaceView idx=4 Map Size=6
10-26 20:47:17.145: D/KeyguardViewMediator(2094): setHidden false
10-26 20:47:17.145: I/SurfaceFlinger(1903): id=1615 Removed SurfaceView idx=-2 Map Size=6
10-26 20:47:17.150: D/WallpaperWidget(2094): cleanUp()
10-26 20:47:17.150: I/DEBUG(17071):          #00  pc 0007831e  /system/lib/libdvm.so (_Z13dvmImplementsPK11ClassObjectS1_)
10-26 20:47:17.150: I/DEBUG(17071):          #01  pc 000783fa  /system/lib/libdvm.so
10-26 20:47:17.150: I/DEBUG(17071):          #02  pc 00078390  /system/lib/libdvm.so (dvmInstanceofNonTrivial)
10-26 20:47:17.155: D/KeyguardUpdateMonitor(2094): handleClockVisibilityChanged()
10-26 20:47:17.155: I/DEBUG(17071):          #03  pc 00026fcc  /system/lib/libdvm.so (dvmAsmSisterStart)
10-26 20:47:17.155: D/KeyguardViewMediator(2094): adjustStatusBarLocked: mShowing=false mHidden=false isSecure=true --> flags=0x0
10-26 20:47:17.155: I/DEBUG(17071):          #04  pc 000343b0  /system/lib/libdvm.so (_Z12dvmInterpretP6ThreadPK6MethodP6JValue)
10-26 20:47:17.155: I/DEBUG(17071):          #05  pc 0006c8c6  /system/lib/libdvm.so (_Z15dvmInvokeMethodP6ObjectPK6MethodP11ArrayObjectS5_P11ClassObjectb)
10-26 20:47:17.155: I/DEBUG(17071):          #06  pc 00073eba  /system/lib/libdvm.so
10-26 20:47:17.155: I/DEBUG(17071):          #07  pc 00030bcc  /system/lib/libdvm.so
10-26 20:47:17.155: I/DEBUG(17071):          #08  pc 000343b0  /system/lib/libdvm.so (_Z12dvmInterpretP6ThreadPK6MethodP6JValue)
10-26 20:47:17.155: I/DEBUG(17071):          #09  pc 0006cb96  /system/lib/libdvm.so (_Z14dvmCallMethodVP6ThreadPK6MethodP6ObjectbP6JValueSt9__va_list)
10-26 20:47:17.155: D/KeyguardViewMediator(2094): setHidden false
10-26 20:47:17.155: I/DEBUG(17071):          #10  pc 00054ff6  /system/lib/libdvm.so
10-26 20:47:17.155: D/STATUSBAR-StatusBarManagerService(2094): manageDisableList what=0x0 pkg=android
10-26 20:47:17.160: I/DEBUG(17071):          #11  pc 00049a7a  /system/lib/libandroid_runtime.so
10-26 20:47:17.160: I/DEBUG(17071):          #12  pc 0004b362  /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime5startEPKcS2_)
10-26 20:47:17.160: I/DEBUG(17071):          #13  pc 00008f0a  /system/bin/app_process
10-26 20:47:17.160: I/DEBUG(17071):          #14  pc 0001684c  /system/lib/libc.so (__libc_init)
10-26 20:47:17.160: I/DEBUG(17071): code around pc:
10-26 20:47:17.160: I/DEBUG(17071): 409a32fc e8bd4648 f1b883fe d1050f02 f8d9e7ee  HF..............
10-26 20:47:17.160: I/DEBUG(17071): 409a330c 6ad93000 d1f32907 f8406938 e7ef9026  .0.j.)..8i@.&...
10-26 20:47:17.160: I/DEBUG(17071): 409a331c 6f82b510 e0072300 f8546fc4 428c4033  ...o.#...oT.3@.B
10-26 20:47:17.160: I/DEBUG(17071): 409a332c 2001d101 3301e003 dbf54293 bd102000  ... ...3.B... ..
10-26 20:47:17.160: I/DEBUG(17071): 409a333c e92d4b1b 447b41f3 460e681b ea864607  .K-..A{D.h.F.F..
10-26 20:47:17.160: I/DEBUG(17071): code around lr:
10-26 20:47:17.160: I/DEBUG(17071): 409a33dc 6c93e004 bf144299 20012000 bf00bd10  ...l.B... . ....
10-26 20:47:17.160: I/DEBUG(17071): 409a33ec 6a09460a 0589b510 d5034603 f7ff4611  .F.j.....F...F..
10-26 20:47:17.160: I/DEBUG(17071): 409a33fc e01cff8f 78086981 d110285b f8906990  .....i.x[(...i..
10-26 20:47:17.160: I/DEBUG(17071): 409a340c f1bcc000 d0050f5b 428a6c99 2000bf14  ....[....l.B... 
10-26 20:47:17.160: I/DEBUG(17071): 409a341c e00c2001 6c196bd8 ffc4f7ff 4293e007  . ...k.l.......B
10-26 20:47:17.160: I/DEBUG(17071): stack:
10-26 20:47:17.160: I/DEBUG(17071):     bede46f8  bede4701  [stack]
10-26 20:47:17.160: I/DEBUG(17071):     bede46fc  409a2b5f  /system/lib/libdvm.so
10-26 20:47:17.160: I/DEBUG(17071):     bede4700  40fa0b80  /dev/ashmem/dalvik-heap (deleted)
10-26 20:47:17.160: I/DEBUG(17071):     bede4704  000000c2  
10-26 20:47:17.160: I/DEBUG(17071):     bede4708  57099d68  /dev/ashmem/dalvik-LinearAlloc (deleted)
10-26 20:47:17.160: I/DEBUG(17071):     bede470c  583a91d4  /system/framework/framework.odex
10-26 20:47:17.160: I/DEBUG(17071):     bede4710  00000000  
10-26 20:47:17.160: I/DEBUG(17071):     bede4714  00000000  
10-26 20:47:17.160: I/DEBUG(17071):     bede4718  01b31468  [heap]
10-26 20:47:17.160: I/DEBUG(17071):     bede471c  01aed2e0  [heap]
10-26 20:47:17.160: I/DEBUG(17071):     bede4720  409def9c  /system/lib/libdvm.so
10-26 20:47:17.160: I/DEBUG(17071):     bede4724  586591ec  /system/framework/framework.odex
10-26 20:47:17.160: I/DEBUG(17071):     bede4728  fffffe4c  
10-26 20:47:17.160: I/DEBUG(17071):     bede472c  4095f740  /system/lib/libdvm.so
10-26 20:47:17.160: I/DEBUG(17071):     bede4730  df0027ad  
10-26 20:47:17.160: I/DEBUG(17071):     bede4734  00000000  
10-26 20:47:17.160: I/DEBUG(17071): #00 bede4738  34000000  
10-26 20:47:17.160: I/DEBUG(17071):     bede473c  409a33ff  /system/lib/libdvm.so
10-26 20:47:17.160: I/DEBUG(17071): #01 bede4740  34000000  
10-26 20:47:17.160: I/DEBUG(17071):     bede4744  409a3395  /system/lib/libdvm.so

You should be able to do adb shell setprop debug.checkjni 1 on an unrooted device. 您应该能够在无根设备上执行adb shell setprop debug.checkjni 1 It will affect any apps started after that point, and you should see D Late-enabling CheckJNI in the log when you start an app. 这将影响在此之后启动的所有应用程序,并且在启动应用程序时,您应该在日志中看到D Late-enabling CheckJNI

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 是否可以通过编程方式重新引导有根和无根的android设备? - Is it possible to reboot both rooted & unrooted android device Programmatically? 在Android 4.x设备(无根)上,可以在应用程序内禁用checkJNI吗? - On Android 4.x devices (unrooted), can checkJNI be disabled from within an app? 在未经验证的Android设备上运行本机C程序 - Run a native C program on unrooted Android device 想以编程方式从未经验证的Android设备的ram中清除未使用的内存 - Want to clean unused memory from ram of unrooted android device programatically / system / app中的Android应用程序可以在无根设备上写入/ system吗? - Can an Android app in /system/app write into /system on unrooted device? SQLite文件能否成功复制到未经授权的Android设备的数据文件夹中? - Can SQLite file copied successfully on the data folder of an unrooted android device ? 将Android设备从用户切换到工程师版本,反之亦然? 从根设备到无根设备? - Switch android device from user to engineer version and vise-versa? Root device to Unrooted device? 如何通过USB访问未经验证的Android设备在Win7 PC上运行的Web服务? - How to access a webservice running on a Win7 PC from an unrooted Android device via USB? RtAudio软件可以在无根用户情况下录制Android OS设备的输出音频吗? - Can a RtAudio software record output audio of an Android OS Device, in an unrooted user case? unrooted设备的Android应用程序的默认数据库位置是什么? 是否与root用户相同? - What is the default database location of an android app for an unrooted device?? Is it same as for rooted one?
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM