droidbox.sh : OSError
GoogleCodeExporter opened this issue · comments
What steps will reproduce the problem?
1.Setup a new AVD "Droid.avd"
2.$ ./startemu.sh Droid, loading a emulator successfully.
3.$ ./droidbox.sh <file.apk>, ERROR!
What is the expected output? What do you see instead?
According to some success case, the output should be
__ ____
\ _`\ __ /\ \/\ _`\\
\ \ \/\ \ _ __ ___ /\_\ \_\ \ \ \L\ \ ___ __ _
\ \ \ \ \/\`'__\ __`\/\ \ /'_` \ \ _ <' / __`\/\ \/'\\
\ \ \_\ \ \ \/\ \L\ \ \ \/\ \L\ \ \ \L\ \\ \L\ \/> </
\ \____/\ \_\ \____/\ \_\ \___,_\ \____/ \____//\_/\_\\
\/___/ \/_/\/___/ \/_/\/__,_ /\/___/ \/___/ \//\/_/
But, after input the order "./droidbox.sh <file.apk>", it output the error-info:
Traceback (most recent call last):
File "scripts/droidbox.py", line 516, in <module>
main(sys.argv)
File "scripts/droidbox.py", line 297, in main
call(['adb', 'logcat', '-c'])
File "/usr/lib/python2.7/subprocess.py", line 524, in call
return Popen(*popenargs, **kwargs).wait()
File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1308, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
What version of the product are you using? On what operating system?
product: DroidBox411RC.tar.gz
operating system: Linux ling-Dell-System-Inspiron-N4120 3.8.0-19-generic
#29-Ubuntu SMP Wed Apr 17 18:16:28 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Android SDK:android-sdk-r22.6.1-linux.tgz
JDK version: Java 1.6.0_45
python version: Python 2.7.4
Please provide any additional information below.
I had tried to find solution online and read the Issue 34, I just opened one
terminal.
Thanks for help!
Original issue reported on code.google.com by Pengling...@gmail.com
on 28 Mar 2014 at 5:20
Execuse,I had resolved this problem.
After ./startemu.sh, emulator will be loading. Once input the ./droidbox.sh,
the format will change, then I press the "Backspace" until the curse cannot
move, input the ./droidbox.sh <file.apk> .
then DroidBox will run successfully.
Note: the <file.apk> should be the complete path.
Original comment by Pengling...@gmail.com
on 28 Mar 2014 at 1:51
issue was fixed by the initial reporter
Original comment by spreitze...@googlemail.com
on 18 Apr 2014 at 11:21
- Changed state: Done