Originally Posted by FadeFx
Probably i am just stupid, but i dont get that adb stuff, you want to start the service on the device from your pc, or what?
tapatalked from lollipopped i9300
, your probably following along better than you think its just what I had to do was notably a cheat at best. So when I was trying earlier to execute it as su the service was starting but the SDCard was not being shared out so I had to dig from my local PC via adb to better understand how the script was seeing things and thats when things got odd and I realized that ADB sees things differently than the applications do in terms of the sdcard location however with ADB I was actually able to start up the service and get /sdcard shared out (kinda, ill get back to that). So, as I sit there kicking myself over it I realized that the script could actually just take advantage of the adb emulator on the device itself by just executing the commands as 'adb -s emulator-5554 shell '<put command here>' ' and then the script would work exactly how I was telling it to and work that way.
So, back to the "kinda" part, thats when I recognized to my dismay that ADB and applications and android see the sdcard in different ways that are not entirely compatible with each other and thats where things get dirty, while you can share out the sdcard that way its availalbe to root only and not applications so its a no-go. The only reason I even know about that method is because its a workaround for mounting CIFS shares in android post 4.3 and I just got done setting up a script for this very same device to do so on boot. If this leaves your head spinning don't worry your not alone and thats why my inital post was really about figuring out a way to get this to boot just for eth0 because that settles all the workarounds or having to use a different application. There's a way, I am probably over complicating it but thats what I do best. Thanks for the assists.