SpazeDog / mounts2sd

Android SD-Ext Script+App
GNU General Public License v3.0
78 stars 27 forks source link

empty paths to binaries #42

Closed diggit closed 6 years ago

diggit commented 8 years ago

Hi, I own Motorola Photon Q and I tried your script to work around CM13 (6.0 Marshamllow) problem with writing to external sdcard and found weird bug.

I just added Log v "grep binary: '$_grep'" before mmcdevice lookup for mmcPartition in system data cache; do ....

$ logcat| grep -i mounts2sd
04-04 23:56:25.115   194   194 I sysinit : Running /system/etc/init.d/10mounts2sd-runner 
04-05 00:56:28.335   656   656 V Mounts2SD: Setting up the script enviroment 
04-05 00:56:29.354   703   703 V Mounts2SD: Using the shell environment '/system/xbin/busybox sh' 
04-05 00:56:30.022   736   736 V Mounts2SD: Using the busybox binary located at '/system/xbin/busybox' 
04-05 00:56:31.182   805   805 V Mounts2SD: Collecting MMC partition information 
04-05 00:56:31.632   843   843 V Mounts2SD: grep binary: '' 
04-05 00:56:32.015   869   869 V Mounts2SD: Located the 'system' partition at '' 
04-05 00:56:32.507   900   900 V Mounts2SD: Located the 'data' partition at '' 
04-05 00:56:33.017   929   929 V Mounts2SD: Located the 'cache' partition at '' 
04-05 00:56:33.450   957   957 V Mounts2SD: Optimizing MMC devices and partitions 
04-05 00:56:34.816  1045  1045 V Mounts2SD: Setting optimized mount parameters on '' 
04-05 00:56:35.373  1082  1082 V Mounts2SD: Setting optimized mount parameters on '' 
04-05 00:56:36.054  1147  1147 V Mounts2SD: Setting optimized mount parameters on '' 
04-05 00:56:37.570  1245  1245 I Mounts2SD: The system partition is S-On protected and it is therefore not possible to link system content to the '/system' location! 
04-05 00:56:50.998   974   974 W PackageManager: Unknown permission android.permission.ACCESS_SUPERUSER in package com.spazedog.mounts2sd
04-05 00:56:52.483   974  2010 W PackageManager: Unknown permission android.permission.ACCESS_SUPERUSER in package com.spazedog.mounts2sd
04-05 00:57:22.061   974  2836 I ActivityManager: Start proc 4666:com.spazedog.mounts2sd/u0a87 for broadcast com.spazedog.mounts2sd/.ReceiverBoot
04-05 00:57:22.283  4666  4666 W System  : ClassLoader referenced unknown path: /data/app/com.spazedog.mounts2sd-1/lib/arm
04-05 00:57:22.503  4711  4711 D su      : Checking whether app [uid:10087, pkgName: com.spazedog.mounts2sd] is allowed to be root
04-05 00:57:25.834  4666  5193 I RootFW.ShellExtender::run(): Running attempt number 1 [( busybox test -e '/mounts2sd-tmp/safemode.result' && echo true ) || ( busybox test ! -e '/mounts2sd-tmp/safemode.result' && echo false ) 2>/dev/null]
04-05 00:57:25.952  4666  5208 I RootFW.ShellExtender::run(): Running attempt number 1 [( busybox test -e '/mounts2sd-tmp/init.type' && echo true ) || ( busybox test ! -e '/mounts2sd-tmp/init.type' && echo false ) 2>/dev/null]
04-05 00:57:28.128  4666  5480 I RootFW.ShellExtender::run(): Running attempt number 1 [( busybox test -e '/mounts2sd-tmp/e2fsck.result' && echo true ) || ( busybox test ! -e '/mounts2sd-tmp/e2fsck.result' && echo false ) 2>/dev/null]
04-05 00:57:31.086  4711  4711 D su      : Finishing su operation for app [uid:10087, pkgName: com.spazedog.mounts2sd]

It looks like $_grep is empty and I suspect that $_awk has same problem. What can be the reason?