Hey everybody. I'm on windows and adb's shell just keeps on pissing me off. Mainly, how pressing tab actually inserts a tab rather than tab completion . I'd really like to do something about this.
Here's a list of the things i've tried to get rid of this super-annoying behaviour.
-rolled a cross-compiler toolchain (glibc-based) for my phone (HTC Magic) and cross-compiled bash (in a vm). I actually made this work even with dynamic linking, and can start bash from within an instance of "adb shell". Unfortunatly, this doesn't change the tab behaviour, which appears to be baked into adb rather than a problem with the default shell.
-I thought i'd try something fancy by doing...
adb shell mkfifo /fifo
adb shell "bash > /fifo < fifo 2> /fifo"
adb forward tcp:9001 dev:/fifo
and starting putty in raw mode, connecting to localhost:9001. Unfortunatly, all is what happens is i get an echo of what i type and if i press enter a few times putty spits out ": command not found". I can't see why this shouldn't work but I suspect i'm Doing It Wrong.
-Searching the forum revealed puttycyg, which is actually really handy but unfortunatly suffers from the same tab completion problem as using adb shell in cmd.exe
How do you guys do it? Am I onto something with the adb forward thing? If so, how do I make that work?
I have also compiled bash but I have tab completion though adb. I do however use Linux as my desktop OS and am connecting through Konsole. So you could just try to install KDE for Windows. I know that I've looked for good terminal applications for windows but found none. They're all **** compared to what's available on nix.
This is my simple bashrc:
Code:
# If interactive do nothing.
[ -z "$PS1" ] && return
export HOME="/sdcard/"
PS1='[email protected]\h:\w\$ '
Also it's full of aliases for busybox. By replacing built in ls and similar you even get nice colors But still no line editing for some reason. I figure I might just need a proper libreadline or similar for that.
If anybody's interested in how I got this working, i cross-compiled socat for the droid. Required configuring with --disable-termios and manually editing config.h to set the #define for CRDLY_SHIFT and a couple other *_SHIFT macros to some values i found in Config/linux-2.6.24.h (or something similar, posting from memory here)
Once socat is on the phone, I made it pipe data from a bash shell to a unix socket it is listening on:
socat unix-listen:/dev/adbsock,fork exec:"/bin/bash -li",pty,stderr,setsid,sigint
(command shamelessly copied from http://superuser.com/questions/123790/socat-and-rich-terminals-with-ctrlc-ctrlz-ctrld-propagation ).
Then, on the pc i run adb forward tcp:9001 localfilesystem:/tmp/adbsock
And if i connect putty to localhost:9001 in raw mode (disabling line editing and local echo) I get a fairly complete bash shell that you can not only use tab completion on but even vi works
Again, posting from memory here so if anyone wants to try this and is running into problems i can dig it up from my ~/.bash_history.
Any chance you can post your socat port?
The tab completion thing is driving me insane! I don't understand why the ADB shell in *nix is proper, but the windows version sucks so much hairy donkey balls.
I've been using Ansicon so I at least get color in my shell, but ADB still mangles tab, and I don't even want to talk about what it does to Nano. Ugh!
Oh wow, this takes me back. I don't even have my android phone anymore (cancelled the contract due to terribly crap network service, and (unfortunately) the iPhone was the best phone in its price range from my new carrier).
So I don't have any files to give to you...
But, from what I can remember, to make it work, I built a cross binutils and gcc loosely following the instructions from the LFS book, compiled glibc + a few other libs socat wanted with it, and then socat itself, and then bash. I then copied the cross libc.so.6, ld-linux.so.2 (or whatever it's called on ARM) and all the libs socat wanted to /lib on the phone, and the socat and bash binaries to /bin. It's convenient that android keeps its important stuff in /system because it means you can avoid screwing around with your toolchain to make it look for a dynamic linker in some location other than /lib.
From memory socat was the only thing I had problems compiling, and thankfully I've already posted roughly what i had to do to it to make it build (because there's no way I remember lol)
Sorry I can't be more helpful!
Related
Hello, i would like to have BASH like default shell,how can i do that? I try extract bash from debian armel image and it doesnt work. And debian image doesnt solution.Thank you for answer.
Theres always ash, which ain't too bad, just type ash at a command prompt. Gives you tab completion and you can use the ball to scroll back thru history which saves much typing
I want to edit with busybox vi running from the phone within an adb shell.
I am running a DOS box cmd window or a cygwin rxvt shell window, both don't work, where I connect to the phone with an adb shell. Then I run busybox vi. The vi runs but the default termcap or terminfo or whatever it is doesn't seem to be right because busybox vi comes up but I can't seem to get the ESC key to take so I can switch between command and insert modes of operation. On the phone it works correctly.
I hate editing on the phone. I would much rather work on the workstation.
I've read on a wiki busybox vi page that busybox vi only supports vt102. Any ideas if this should work or what I could try?
Thanks in advance.
Same here. I spend half the morning playing with TERMs, trying to get a dos or cygwin terminal to run vi. vi runs fine in Terminal emulator, but like you, I don't wan to edit on the phone.
I found JOE (Joe's Own Editor) ported to Android. I installed it because it supposedly uses TERM=unknown. That didn't work from DOS either. But it did work from a cygwin bash shell, with TERM=linux in the adb shell. Now there is the learning curve to use JOE...
I too would be happy to hear which TERM setting will work with a DOS adb shell.
Face same situation here. Is it resolved?
If not, how you gurus work around on this basic issue?
I don't know much about VNC yet. Could it be a viable direction that worth spending effort?
Adb shell and Vi - info
I too just spent a lot of time trying to get vi to work under "adb shell". ESC was especially a problem. Ultimately, I wasn't able to get it to work correctly, but SSH seems to work fine.
There are a lot of details about what I learned on Stackoverflow (I'm a new member here, so I can't post the link, but you can search for it -- the title is "adb shell: can't use the ESCAPE KEY").
Has anyone gotten this to work correctly? Or is it simply an incomplete/buggy implementation of adb's shell?
Thanks,
Barry
hey everyone,
so i finally got the dock for my TF a couple weeks ago.. i have several friends that are not as tech savvy as i am, but still like android, well i want to offer to root their devices for them. more out of curiosity then need i was wondering if it is possible to unlock and push the recovery from a TF? i know that the TF has ADB on it, but i havent really started any development on the TF its more for fun, i use my nexus 1 for development.. any light you can share on this would be appreciated.
Interesting...
Nice thread i hope some one comes up with further info about this idea i would like to do this too!!!! I have sold mi laptop TF can do everything... And soon W8 will be possible on it and STABLE Ubuntu!!!
I was contemplating this also since a girl I work with wanted me to root her Galaxy S1 but I only had my TF with me and we can't install drivers on the work computers.
I assume it should be possible, you just may need more of the Linux binaries, for example you may need to do it via a chroot install of Ubuntu or as a native (dual-boot) system. Look at the shell scripts and see what binary tools they require (cp, mv, cd etc...), you may be able to do it with Android's toolchain.
There's something in the market called "remote adb" which "might" be of use, but I kind of doubt it. It could also be one of those adbwireless versions of adb where you still do the heavy lifting from the PC.
My take would be to look at the results of google "+source +adb +android" and you'll get a couple of hits that point at adb repos in git format.
Then use a linux box to clone one and point it at some crossbuild tools (see for example the howto build kernel threads that are here and there) and built it for our architecture (arm{le}). I've done this for the bash shell and a few other things I liked in linux and it should be possible. One built, push it into /system/xbin, chmod 755 adb and see how things go.
I don't have the keyboard dock or the OTG dongle so no point in my doing it since I can't test.
Good luck -
edit: http://lackingrhoticity.blogspot.com/2010/02/how-to-build-adb-android-debugger.html seems like as good a place as any since it has source, instructions, etc. So probably all you have to do (if this nutty project will work at all) would be to modify the Makefile so that it's pointing to the toolchain for armv7le (or that's what uname -a shows on my eeepad).
edit: Another one that's already been built for android (I tested it), is sshd or dropbear and here is a link: http://jhulst.com/c/dropbear-ssh-android .
The main thing is being able to hit the device you want to setup using either ssh or scp, and functionally this'll do most if not all or more than adb will. What won't work are any scripts written that are already using adb commands.
thanks for the input originally i was thinking being able to use terminal inside honeycomb, but i suppose the easier (or perhaps better stated, the "road more traveled") route would be dual booting linux and just setting up the dev kit on there..
Latest version of ubuntu by little stevie is your best bet
So, looks like we have Carrier IQ on our phones, thanks to AT&T. Any luck on getting a 3rd party ROM on here yet? Any estimates as to when?
Can you give us more information? like how you found it on the phone, what steps did you take?
With more info, those of us in the know can figure out how to disable it, or remove it, without having to resort to waiting for a rom.
I have been looking for it for quite some time without much luck.
It's the device health app.it calls the ciq agent . Easily frozen.
Sent from my MB865
mtnlion said:
It's the device health app.it calls the ciq agent . Easily frozen.
Sent from my MB865
Click to expand...
Click to collapse
Thanks, I will see what else I can come up with for the ciq agent, maybe a way I can fake it out on the *NIX side of the house.
Yep first thing I went looking for after I got root.
Bloat freezer. It's free, finds it fast. When you freeze device health it doesn't want to close and keeps force closing, just reboot, it will be frozen and not running.
Douchewithaphone said:
Bloat freezer. It's free, finds it fast. When you freeze device health it doesn't want to close and keeps force closing, just reboot, it will be frozen and not running.
Click to expand...
Click to collapse
Must be rooted.
Sent from my mAtrix2!!
Well, I have found a way from the UNIX end to stop this thing in it's tracks, but it is not pretty for those unfamiliar with command line....
What we have to do is uncompress the kernel image in the boot.img remove the sys.DeviceHealth from the init.rc file there, then compress the kernel back up, all using cpio.... now to see if I can possibly make it work, and not brick any phones in the process, maybe I can throw a quick apk together next week.
I have tried the bloat freezer and the android assistant and I can still find the sys.DeviceHealth running on the UNIX side with the ps command, so this is a nasty one.
I will keep you guys posted, If I can find a better way.
Here is the link I saw, and how I figured out where sys.DeviceHealth is starting from.
For those interested ONLY. PLEASE do not try this yet, give me some more time to play with this in an emulator and see what I can come up with.
I am just sharing information at this time. BTW Zygote is the process that is calling the sys.DeviceHealth on the Atrix 2.
To see this Do the following from the terminal emulator app on your phone or though adb shell.
ps | grep -i Heal
ps | grep -i zygote
If you notice on the sys.DeviceHealth process that the second number is the same number as the first number of the zygote process.... What that means is that the zygote process starts the sys.DeviceHealth process. The first number is process ID (the processes "adress" so to speak), and the second number is the Parent process ID (The process that started the next one).
http://vinnysoft.blogspot.com/2009/12/zygote-system-process.html
jimbridgman said:
Here is the link I saw, and how I figured out where sys.DeviceHealth is starting from.
For those interested ONLY. PLEASE do not try this yet, give me some more time to play with this in an emulator and see what I can come up with.
I am just sharing information at this time. BTW Zygote is the process that is calling the sys.DeviceHealth on the Atrix 2.
To see this Do the following from the terminal emulator app on your phone or though adb shell.
ps | grep -i Heal
ps | grep -i zygote
If you notice on the sys.DeviceHealth process that the second number is the same number as the first number of the zygote process.... What that means is that the zygote process starts the sys.DeviceHealth process. The first number is process ID (the processes "adress" so to speak), and the second number is the Parent process ID (The process that started the next one).
http://vinnysoft.blogspot.com/2009/12/zygote-system-process.html
Click to expand...
Click to collapse
zygote appears to be a process respawner (watchdog) of some type. The trick is to find out where its config lies and tweak that to prevent the launching of sys.DeviceHealth.
I've just got the busybox installed that came with TiBackup and the shell tools are sorely limited (no grep for eg.). The shell itself is also pretty limited (no pipe??? WTF?). I had a version of bash on my atrix4g, and I'm wondering if you know of a reliable source for bash and shell tools for the atrix2?
A lil info on what AT&T says and how it uses Carrier IQ and some of the devices it is on can be read here http://m.androidcentral.com/atts-us...its-own-analytics-app-not-just-embedded-phone
razholio said:
zygote appears to be a process respawner (watchdog) of some type. The trick is to find out where its config lies and tweak that to prevent the launching of sys.DeviceHealth.
I've just got the busybox installed that came with TiBackup and the shell tools are sorely limited (no grep for eg.). The shell itself is also pretty limited (no pipe??? WTF?). I had a version of bash on my atrix4g, and I'm wondering if you know of a reliable source for bash and shell tools for the atrix2?
Click to expand...
Click to collapse
Yes that is exactly what zygote is. You would disable the sys.DeviceHealth in the EXACT way it says in the in link I posted, but you have to uncompress the kernel image, and extract the init.rc in there, then edit it to not include the sys.DeviceHealth, then re-compress it with cpio. This is just for information right now, so that later on when the ROM developers get started, they can use this info for their ROMs. I am testing this using a couple Android emulators to see what I can do with this.
As for a reliable busybox, I like the version from JRummy16 in the market, go grab that an install the latest version of busybox from his installer you downloaded (I think it is 1.19.3 or something similar).
also go get the hackers keyboard in the market, it helps a lot if you EVER use the terminal app ON the phone, heck I like for text and typing as well.
Jim: I'm assuming you mean the initrd image and not the kernel, or is that all wrapped up into one in android? the initrd is an odd place for the system's watchdog config. I suppose putting it in the kernel image prevents disabling it because presumably we don't have the key to sign the new image...
that's a new version of busybox, but I'm more interested in one with all of the options compiled in. What I have is pretty bare-bones... Does his busybox have grep at least? what do you do for a decent shell?
razholio said:
Jim: I'm assuming you mean the initrd image and not the kernel, or is that all wrapped up into one in android? the initrd is an odd place for the system's watchdog config. I suppose putting it in the kernel image prevents disabling it because presumably we don't have the key to sign the new image...
that's a new version of busybox, but I'm more interested in one with all of the options compiled in. What I have is pretty bare-bones... Does his busybox have grep at least? what do you do for a decent shell?
Click to expand...
Click to collapse
Yes in the initrd image the kernel is packed in there, as well as the init.rc file on Android, as well the filesystem subset, etc.
The init.rc file in / on the phone is NOT the one the kernel itself executes, take a look at that link I posted, Here is the excerpt we are interested in, I am pretty sure that the sys.DeviceHealth is in the exact same place:
I want to get a bit more control of what things are starting up when. To do this I need to modify the init.rc file. To do this I first extracted the the ramdisk to the fileystem so that I can modify it (gnucpio -iz -F ramdisk.img).
After this I simply commented out the line from init.rc. Then we can recreate it: (gnucpio -i -t -F ../ramdisk.img | gnucpio -o -H newc -O ../rootfs.img).
Click to expand...
Click to collapse
Yes both the stericson and JRummy16 busybox have most every command in the busybox you really need, oh and they create links in /system/bin for you, so that you can run commands without needing to always type busybox in front of the command.
As far as shells, I am a bourne or korn guy, so I just use the default /system/bin/sh, since I am closely intimate with bourne, being the UNIX Engineer that I am, and handling anything at the lowest level of the OS still requires bourne. But I love to program in korn (ksh), but I have not found any android shells that are useable beyond the basics, since we really are not going to spend much time there, it does not matter much. I would get aquainted the bourne, that android uses, since android seems be using the old school UNIX style bourne, more and more, yes there is some bourne again in there too.
P.S. pipe is in the /system/bin/sh, just make sure you source the /osh/apath.sh file, to get the /system/bin and /system/xbin in the shell...
The hackers keyboard has things like the arrow keys so that you can command recall, and other helpful things.
If you really need to run something, from the shell, just make sure put sh in front of it, or it won't run in a shell, one of the oddities about Android.
I have tested the method I mentioned before, and uncompressing the ramdisk that holds the kernel, and removing the sys.DeviceHealth from the init,rc, and it does work, after packaging it back up with CPIO. I tested this on an older phone that does not have a locked bootloader.
I am afraid to test it on the Atrix 2 since we still do not have a true way to get back after a soft brick at that low level.
Given the fact that this was another style of phone, and an unlocked bootloader, and the fact that the process name is a little different, I am still confident we can do something similar for our phone.
If you follow the directions on my post, you'll find it much easier to disable the Carrier IQ.
http://forum.xda-developers.com/show...6#post20281786
mrpoet said:
If you follow the directions on my post, you'll find it much easier to disable the Carrier IQ.
http://forum.xda-developers.com/show...6#post20281786
Click to expand...
Click to collapse
^^^^^^^^^^^Page not found^^^^^^^^^^^
kirkgbr said:
^^^^^^^^^^^Page not found^^^^^^^^^^^
Click to expand...
Click to collapse
Try this Link. I am not sure if it will do the job for us or not, because we don't have the same Apps installed as the Epic 4g that this original post was copied from.
Here is the thread, mrpoet created and pointed to:
http://forum.xda-developers.com/showthread.php?t=1390874
Here is the original one, that he does link to in his references:
http://forum.xda-developers.com/showthread.php?t=1373394
I am going to see if it works.
----Edit---
I just gave this a try and all the commands ran successfully, but sys.DeviceHealth is still running after following the above post.
JRW 28 said:
A lil info on what AT&T says and how it uses Carrier IQ and some of the devices it is on can be read here http://m.androidcentral.com/atts-us...its-own-analytics-app-not-just-embedded-phone
Click to expand...
Click to collapse
Just to let everyone know, the information contained in the link that JRW 28 posted, is an accurate statement from AT&T.
I have inside information that, that is BS. There are 100's of Terrabytes of Disk Storage just for this purpose.
They're a pack of bastards.
*YO! New version can connect to a TV via HDMI. If you have a USB-host, you can also connect a keyboard and a mouse!*
Hi. I want to introduce you Wishnu. The essence of our project is the launch of computer OS Linux Debian inside an Android mobile device. Then this device connects to a computer by means of the USB-cable. Actually that allows transforming any Android device into a real computer. You can connect the phone to different computers at home, at work and on a visit and use the phone’s own screen and input equipment on the journey.
We have taken "running chrooted debian/ubuntu on android" idea as the base and created something interesting with it.
First, we have created Android application which starts Debian on android mobile device with one click (no need to type any commands in the terminal etc).
Second, we have written desktop client application which shows Debian desktop running on mobile phone on the PC or laptop with wide screen, mouse and keyboard, so this actually turns the solution to the docking station like Motorola Lapdock or devices such as Pocket Desktop, but much better, cause you don't need to buy additional docking station device and you will immediately receive tons of common desktop applications available from Debian MIPS/ARM repositories (even pdf document viewers, image editors, office with spreadsheets and presentations editors etc).
Also device SD card available inside chrooted system in /media/sharedSD dir.
Watch the video in action
And this one (sorry for the quality, I used my matreshka as a camera).
Screenshots
Currently Wishnu uses Debian 5.0 ARM image taken from this thread. We are planning to add more customized and fresh Debian and Ubuntu OS images.
System requirements
PC client
- OS Windows XP, Vista, 7 (x86) or Linux (x86, x64)
- Java Runtime Environment must be pre-installed.
- Device ADB driver on Windows (on linux no adb driver needed, but adb server should be started as root in most cases)
Android device
- MIPS or ARM
- Mobile processor 500 MHz, 256 mb RAM (Recommended: processor 1 GHz and >512 mb RAM)
- Android OS 1.5 or higher.
- The device must be rooted.
Download and install instructions
Or download on Android Market
This one is much easier to start with than existing LinuxInstaller - no need to type any commands in terminal or adb shell - just download image file and press start. Also desktop client is great idea.
Needs more options for system control though and also Ubuntu image for desktop instead of old debian.
yo, we need some response, please download our awesome application! or at least tell us why you won't do it (maybe Wishnu is useless or smb is better). Thank you!
How does it do with running heavier weight applications such as thunderbird?
agoodm said:
How does it do with running heavier weight applications such as thunderbird?
Click to expand...
Click to collapse
Actually it depends on your phone's performance. We use Sony Ericsson Xperia arc for testing and have no problems running such applications. You better try it and inform us about results)
Are you using the armel or armhf Debian distribution?
nicktastique said:
Are you using the armel or armhf Debian distribution?
Click to expand...
Click to collapse
Currently we have images of debian squeezy for armel and mipsel.
A bit busy with the holidays and all, but I will give it a look. I definitely recommend checking out armhf. I've been testing it on my Droid 3 and cursory benchmarks show it to be something like 850% faster than armel. armel is basically useless in comparison.
Debian's armhf Icweasel 9.0 was actually faster than the native Firefox Mobile 9.0 app on the SunSpider benchmark (by 80ms, but still).
Thanks for your work, looking forward to checking it out.
lokosokol said:
Currently we have images of debian squeezy for armel and mipsel.
Click to expand...
Click to collapse
Very interesting idea, and I'd love to give it a go. Unfortunately, it doesn't work for me. I get an error, "Can't connect to OS image".
The checks run okay, so everything appears to be okay.
I'm using a Samsung GS2, on 2.3.5 (stock ROM), so hardware and OS are more than adequate.
Edit: Okay, so it was the stock ROM that was the problem. I assume it doesn't support loop devices (whatever that actually means!) I've got a custom ROM on there now and it gets a lot further, but I still have an issue.
It gets to the "Starting System" stage and I get the error message "OS start failed (bad program identificator)".
So, any advice?
Thank you for your advice, guys!
nicktastique said:
A bit busy with the holidays and all, but I will give it a look. I definitely recommend checking out armhf. I've been testing it on my Droid 3 and cursory benchmarks show it to be something like 850% faster than armel. armel is basically useless in comparison.
Debian's armhf Icweasel 9.0 was actually faster than the native Firefox Mobile 9.0 app on the SunSpider benchmark (by 80ms, but still).
Thanks for your work, looking forward to checking it out.
Click to expand...
Click to collapse
Thank you very much for this hint — we are working on preparing better system images and will definitely give this option a try.
Archer said:
Very interesting idea, and I'd love to give it a go. Unfortunately, it doesn't work for me. I get an error, "Can't connect to OS image".
The checks run okay, so everything appears to be okay.
I'm using a Samsung GS2, on 2.3.5 (stock ROM), so hardware and OS are more than adequate.
Edit: Okay, so it was the stock ROM that was the problem. I assume it doesn't support loop devices (whatever that actually means!) I've got a custom ROM on there now and it gets a lot further, but I still have an issue.
It gets to the "Starting System" stage and I get the error message "OS start failed (bad program identificator)".
So, any advice?
Click to expand...
Click to collapse
Could you give us a log file of that failed launch? It should be in "/path_to_application_data/log" folder.
I tried it out and I get "Error:OS start failed (timeout expired)
Here is the log:
Code:
############Preparing Base System############
############Preparing Base System Check############
***Checking Ext2 exists/not exists***
true
***Checking system loop device file '/dev/block/wishnuloop' exists***
true
############Preparing Base System Check Finishes############
############Preparing Base System Ends############
############Mounting System Image############
############Mounting System Check############
**Checking /dev/block/wishnuloop mounted/not mounted**
#busybox losetup /dev/block/wishnuloop
/dev/block/wishnuloop: 0 /mnt/sdcard/wishnu/system.img
Return code: 0
**Check /data/data/edu.phystech.wishnu/system mounted/not mounted**
#busybox mountpoint /data/data/edu.phystech.wishnu/system
Return code: 0
############All Correct############
############Mounting System Image Ends############
############Preparing System############
############Preparing System Check############
**Check /data/data/edu.phystech.wishnu/system/dev/pts mounted/not mounted**
#busybox mountpoint /data/data/edu.phystech.wishnu/system/dev/pts
Return code: 0
**Check /data/data/edu.phystech.wishnu/system/proc mounted/not mounted**
#busybox mountpoint /data/data/edu.phystech.wishnu/system/proc
Return code: 0
**Check /data/data/edu.phystech.wishnu/system/sys mounted/not mounted**
#busybox mountpoint /data/data/edu.phystech.wishnu/system/sys
Return code: 0
**Check /data/data/edu.phystech.wishnu/system/media/sharedSD mounted/not mounted**
#busybox mountpoint /data/data/edu.phystech.wishnu/system/media/sharedSD
Return code: 0
############All Correct############
############Preparing System Ends############
############Starting System############
############Starting System Check############
############start from ip_forward############
#busybox sysctl -w net.ipv4.ip_forward=1
net.ipv4.ip_forward = 1
Return code: 0
#busybox chroot /data/data/edu.phystech.wishnu/system /bin/bash -l
su: applet not found
#busybox fuser -k /data/data/edu.phystech.wishnu/system
Return code: 1
#rm /data/data/edu.phystech.wishnu/system/root/.vnc/localhost:1.pid
rm failed for /data/data/edu.phystech.wishnu/system/root/.vnc/localhost:1.pid, No such file or directory
Return code: 255
############Start Failed############
According to the log your busybox is a bit "incomplete" - it doesn't include a chroot applet (which is really strange). I think reinstalling it should solve the problem (in this case busybox installer or BusyBox from android market should help).
I have tried several versions of busybox (1.19.3, 1.18.4, etc) and they all give the same error. It seems that it tries to run "busybox su" when it does not exist..
Ok, this means that we also have some problems with log printing.
Using "busybox su" seemed to be a bit safe command (it worked on all devices we have for testing). Now it turned out that it doesn't work on every device.
By the way I think I should introduce myself - I'm one of the Wishnu developers, so with any problems you can write to me.
The website claims the app on android can run by itself without using a computer. Does this mean the Debian environment is self-contained and can be run as such? The app seems to start linux, but a computer is then required to view the desktop, correct? How does one view the linux desktop from the phone itself?
The app runs fine on my phone. The image file needs to be place on the internal memory, rather than the SD card itself for it to run properly.
Droid 3 running Steel Droid 3 with root.
GoTeamScotch said:
The app seems to start linux, but a computer is then required to view the desktop, correct? How does one view the linux desktop from the phone itself?
Click to expand...
Click to collapse
You can use any VNC client from the android market to get the picture from the linux desktop on your phone.
There connection address is "localhost", port 5901 and password is "android".
You can check gallery on our site to see how it works (photo with phone connected to the TV).
e334 said:
It seems that it tries to run "busybox su" when it does not exist..
Click to expand...
Click to collapse
Checked the source code of the app - version that should be on the android market and the site shouldn't run any "busybox su" command (however it is always possible that we made a mistake).
So first of all I want to make sure that your busybox has chroot applet.
Please, could you perform "busybox chroot " command from the adb shell (or in the terminal emulator in your phone) and post here a result of this command?
If it works I'll attach the launching script (nearly the same we have in the app) and I hope we will find out what's wrong with the launching procedure.
Awesome, thank you very much for the tip! I downloaded a free VNC viewer app from the market and entered the info you gave and it worked! The desktop is a little sluggish but that's sort of to be expected, even with a dual-core phone.
This is very cool software! I didn't realize running Linux on a Droid 3 was possible as of yet because of loopback support. I've been looking into ways of installing Linux since I got the phone, but couldn't find a way around my kernel's lack of loopback. How does your software overcome this obstacle? Are there any plans of improving speed in future releases?
By the way, if your group would like a graphics designer for UI elements or website images I am available! I work for a company in Olympia, Washington making graphics (in-store signs, exterior posters, skins, icons, etc...). This seems like a cool project and I'd be willing to help out for a cup of coffee or something.
Great project.
Do you have more info on building Debian for Android? Also, how much of the "native" Debian UI apps are transferable (and usable) from the phone?