Has anyone tested if tiwlan0 can go into monitor mode under debian? (searched the forum, but got no concrete answer).
I don't have a G1 at the moment(but going to get one soon ), so I can't test it myself.
If anyone is kind enough to help with some information? From a debian shell just type 'sudo iwconfig', 'sudo iwconfig tiwlan0 mode monitor' and then 'sudo iwconfig' (without quotes), and please let me know the output and which version do you have.
Thanks in advance, and hope we could get this done soon
Related
Has anybody tried this? having Lynx accessible via adb shell would be - imo - very handy. For example, my work terminal has no internet access, but I can install the USB driver for my Galaxy S and access the shell that way.
Of course, since I'm not allowed to play with my phone while working, it would be very nifty to open up a cmd window and just type "adb shell lynx" and have at it if I need to.
Has anybody tried this? I'm no coder by any stretch of the imagination, otherwise I'd be having a go at it now..
Hey guys.
Just a heads up, the Xoom can run ADB natively. Full ADB. Haven't tested it over USB Host, but it works with ADBwireless.
Doesn't seem to be documented anywhere, but it does work. Try ADB devices from a terminal on your xoom.
Meaning that the Xoom can run ADB, just like your computer. Pull APKs, ringtones, media, whatever over wifi.
EDIT: These commands should make it work without the apk.
To trigger adb wifi on your phone/non-Xoom:
Code:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
To stop adb wifi and return to USB listening:
Code:
setprop service.adb.tcp.port -1
stop adbd
start adbd
To connect:
Code:
adb connect [IPAddress]:[port]
For example, adb connect 192.168.1.4:5555
Or from USB on your comp:
Code:
adb tcpip 5555
adb connect 192.168.0.101:5555
To get back to USB mode:
Code:
adb usb
thats awesome thanks!
good to know thanks
you could also use adbwireless from the market to do the same thing
it's a lot easier, I think.
Yes, but some of us don't feel like paying...or just prefer command line. :]
smaskell said:
you could also use adbwireless from the market to do the same thing
it's a lot easier, I think.
Click to expand...
Click to collapse
What is included in the sdk on the xoom? I know that you can build apps from the command line on windows and linux. I think that this function would really be what I need to buy a tablet (again). Or you might be able to borrow things from the linux sdk.
Someone should take these commands and put them together into one easy to use app and launch it on the market. Many would benefit from one click type methods to natively run adb commands from the Xoom. If someone would be willing to do that of course. I'm just sayin'.
yep, weve been using the functionality for a while now!
you should also look into moto utils, which come preinstalled on the xoom and can do all sorts of funky stuff!
diablo2224 said:
Someone should take these commands and put them together into one easy to use app and launch it on the market. Many would benefit from one click type methods to natively run adb commands from the Xoom. If someone would be willing to do that of course. I'm just sayin'.
Click to expand...
Click to collapse
search "adb wireless"，you can get this awesome free app, it has a widget built-in.
and born at a bit long ago.
ftgg99 said:
yep, weve been using the functionality for a while now!
you should also look into moto utils, which come preinstalled on the xoom and can do all sorts of funky stuff!
Click to expand...
Click to collapse
So I checked out the field utils...
Apparently the Xoom has a WCDMA component? That's HSPA+ if I'm right...further supported in the iFixIt teardown.
Turned off the GSM functionality (on by default), hoping it'll save battery...not that I can complain. Battery life on this thing kicks ass.
Here's my question: Does it have an IMEI? As in can I put an AT&T SIM in there and it'll work? I'll try testing it out later. Might be time to pull out the ole' faraday cage...
schould get the commands into scripts, executable from a homescreen/the app drawer
@oshigeru YES it has an IMEI. If the AT&T Sim is on CDMA, you should have no problem to use it on the xoom, cuz i can see no restriction/branding/something on it
RinTinTigger said:
schould get the commands into scripts, executable from a homescreen/the app drawer
@oshigeru YES it has an IMEI. If the AT&T Sim is on CDMA, you should have no problem to use it on the xoom, cuz i can see no restriction/branding/something on it
Click to expand...
Click to collapse
Gscript should be able to do it.
AT&T on cdma? Lolwut?
It has an MEID that looks one hell of a lot like an imei, but I can't see an imei anywhere in the tablet. I don't know if the sim slot is active or not. (3g version.)
Sent from my Xoom using Tapatalk
I know this is an older thread but I need some direction in how to get adb in xoom to recognize my NS4G device when plugged in via usbOTG. Is it possible?
Daniel Smith1953
Jewremy said:
Hey guys.
Just a heads up, the Xoom can run ADB natively. Full ADB. Haven't tested it over USB Host, but it works with ADBwireless.
Doesn't seem to be documented anywhere, but it does work. Try ADB devices from a terminal on your xoom.
Meaning that the Xoom can run ADB, just like your computer. Pull APKs, ringtones, media, whatever over wifi.
EDIT: These commands should make it work without the apk.
To trigger adb wifi on your phone/non-Xoom:
Code:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
To stop adb wifi and return to USB listening:
Code:
setprop service.adb.tcp.port -1
stop adbd
start adbd
To connect:
Code:
adb connect [IPAddress]:[port]
For example, adb connect 192.168.1.4:5555
Or from USB on your comp:
Code:
adb tcpip 5555
adb connect 192.168.0.101:5555
To get back to USB mode:
Code:
adb usb
Click to expand...
Click to collapse
thanks for the info but, I can't get adb on my pc! says it doesn't exist! No idea of where to go for that. Any suggestions?
Dan [email protected]
Thank you for these commands.
so i transferred my music from my laptop to my tab, but while looking at my music on the tab it all of a sudden exits and asks me to either force close or report. Anyone have any idea why this could be happening? I thought all was good once i got the files to tranfer, but then this happened...
could you try reproducing the issue with logcat running?
Sure, would you mind explaining how to do that though? Not wuite sure what logcat is... Appreciate all the help! Hope to get this squared away.
yeah, I figured I would have to do that but I hate writing out instructions just to find out that the person already knows everything I had to say.
I'll write this assuming you're using windows.. hopefully that's not a mistake
this may be a lot more work than you're willing to do and it may not give any useful results. you're certainly more than welcome to try it though.
for a much easier, but less helpful method, skip to the end.
first, install the adb driver. there is a link floating around somewhere to just the driver, but I can't find it so you're probably better off just installing samsung kies. this will install the drivers for you.
http://www.samsung.com/ca/support/m...softwaremanual.do?page=MOBILE.SOFTWARE.MANUAL
then, you'll need to download the android sdk.
http://developer.android.com/sdk/index.html
download it, open the sdk manager and then let it install it's stuff. all you really need is "Android SDK Platform-tools, revision X." I believe the most recent revision is 5, but it doesn't really matter.
now, open a command prompt. in windows 7, you can just hit start and then type cmd. in xp or vista I believe if you have to use start->run or windows key + r, then type cmd and click run.
from here, change directory to the platform tools folder of your sdk. most likely something like this
Code:
cd C:\Program Files\android-sdk-windows\platform-tools\
though it will depend on where you installed your sdk
now go into settings->applications->development and check "usb debugging" on your tablet. after that is done, connect it to your computer with usb and type
Code:
adb devices
if something shows up, your device is recognized. otherwise.. ask for help, I guess
finally, type
Code:
adb logcat -c
adb logcat
and then try to reproduce the error. this will give you tons of information about what's going on in the system. hopefully, it will give you some idea why it is crashing.
Note: the "-c" will clear all previous logs
now, for the short version.
In the android market, download "Android Terminal Emulator"
attempt to reproduce the error then open the terminal emulator and type
Code:
logcat &
this will show you all logs since the last reboot, assuming you haven't cleared them with "logcat -c." It might be a good idea to use "logcat -c" before you start trying to reproduce the error.
hope that helps,
Sam
First of all cant thank you enough for trying to help out. So i went with the second option as to limit my chances of having to ask more questions...yeah about that. With option 2 i could not run the "logcat -c" and after reproducing the error and running "logcat &" i get a permission error... Ideas? Thanks again!
hard to say, man.. what does the error say exactly?
Hi everyone!
I don't know what else to do. Every time I had a problem, I always find the answer here. Regrettably, this time I couldn't find a solution for this.
My background:
I'm trying to make AWUS036NH (RT3070) to work with Nexus 7 grouper. More precisely, with a chroot of Kali (made with Linux Deploy). Currently I have CM11.0 Nightly, and recently I flashed the the kernel kangarooV2 from this post, which have the driver (rt2800) I need to make the external Wi-Fi adapter work.
Everything works fine, but when I connect the adapter, nothing happens.
So I searched and tried a lot of things, and finally got the adapter recognized as wlan1 (in Terminal Emulator) doing this:
Code:
$ su
$ insmod mac80211.ko
$ insmod rt2x00lib.ko
$ insmod rt2800lib.ko
$ insmod rt2x00usb.ko
$ insmod rt2800lib.ko
Have to load all those modules because of dependencies, it wouldn't load just the ones I needed.
Ok, with that, now in netcfg I see wlan1, which is the usb wifi adapter.
The thing is, now I can't get the interface up, i tried "ifconfig wlan1 up" but all I get is:
error: SIOCSIFFLAGS (No such file or directory)
How can I get the interface to work?
Thanks in advance.
You have a lovely community here. Cheers!
This may or may not help you: http://ac100.wikispaces.com/Android+rt3070+or+rt2x00
Erovia said:
This may or may not help you:
Click to expand...
Click to collapse
Thanks, I'll have a look at it right now.
Hi Folks,
I'm trying to send AT command and retrieve it's output via adb shell or an app.
I tried several stuff I already found here, like service ATFwdCmd but it didn't exist in MTK device.
I found with getprop that the "baseband" device must be on /dev/ttyC0 but on my device it didn't exist.
output of getprop
[rild.libargs]: [-d /dev/ttyC0]
[rild.libpath]: [/system/lib/mtk-ril.so]
So I started reversing the mtk-ril.so and found that there is a "property_get("mux.debuglog.enable")", and I tried to set this property with setpropex but it's not working too.
I tried using atinout tool at sourceforge with echo 'at+cops?' | atinout - /dev/ttyGS0 -. I also tried the MTK Engineering App and tried to enable full modem log, without luck again.
I'm stuck at here now, if anyone has an idea, i will be very happy to speak with him
PS: sorry for my bad english
Cheers,
Jon
hi, did you solved this ?
I also need to send AT commands on a MTK device, but I have no luck .
Using "cat /dev/pts/4 &" & "echo -e 'ATI\r' > /dev/pts/4" approach gives me no predictive response (the output is sent to logcat and ...partially to the above background process (even when calling "stop ril-daemon", i suspect this is doing nothing, the mtkrild process is still running, killing the mtkrild ..is no solution, the connectivity is lost).
Is there any reliable way we can use mtkrild directly to send AT Commands "