Garbled ls output and permissions problems

[Guest Dan Mullen]

I posted this in the main MCR3.2 thread but I think it got lost among all of the other posts <_<

Since upgrading to 3.2, when I connect via an ADB shell in Windows I'm getting the old problem of a garbled display due to the dodgy colour codes, plus I can't remove files from /system due to the "read-only filesystem"... as it's a while since I've flashed a ROM, have I missed something?! Or is there something not quite right in this version? 3.1 was fine.

Cheers,

Dan

[Guest kendon]

adb remount will solve the readonly error. and if you push the busybox binary from 3.1 the colored output should be gone.

[Guest Dan Mullen]

adb remount will solve the readonly error. and if you push the busybox binary from 3.1 the colored output should be gone.

Cheers Kendon - adb remount did indeed solve the permissions issue. I'm surprised that the busybox binary in 3.2 reintroduces the colour codes problem. I didn't try any of the 3.2 betas as I didn't particularly like the idea of having an MCR based on a 3 ROM, but I upgraded once it came out of beta. Any idea why the version of busybox changed between 3.1 and 3.2?

[Guest zorm]

Re the colour problem, why not just:

alias ls="ls --color=never"

in the shell?

I was going to add this to the shell config, when I realised I couldn't find one. It seems $HOME isn't set either <_< Anyone know how one can safely configure the shell in Android?

Along related lines, I have Better Terminal Emulator Pro installed & I was hoping to be able to persuade Android to use the shell BTEP provides for adb shell, to give colour support, tab completion & a command history. I assume this means using an appropriate shell /&/ configuring the terminal in the host os to support the relevant control codes in the case of colour suppport. I take it this is a no go with Windows command prompt, as this recent change to busybox's shell implementation shows, but any suggestions on how to get it to work with another terminal?

[Guest kendon]

Cheers Kendon - adb remount did indeed solve the permissions issue. I'm surprised that the busybox binary in 3.2 reintroduces the colour codes problem. I didn't try any of the 3.2 betas as I didn't particularly like the idea of having an MCR based on a 3 ROM, but I upgraded once it came out of beta. Any idea why the version of busybox changed between 3.1 and 3.2?

i'd guess paul recompiled it from newer sources and forgot to disable the color output... never used 3.2 any version or beta, don't trust the 3 rom....

[Guest zorm]

I've been experimenting a little. If you connect via adb from Windows & would like those colour codes to do what they're supposed to, here's one solution:

Install Cygwin if you're not already using it. Install puttycyg. Running the command:

putty -cygterm -

will now give you a shell from which you can launch adb shell. Colour codes will be correctly interpreted within this.

[Edit:] If you have BTEP installed, you can launch its shell from within the default adb shell, which offers hope of tab completion & a command history. Unfortunately, atm it doesn't render correctly, though I guess that's not much of a surprise.

Edited March 13, 2010 by zorm