hi, i installed sshdroid on my galaxy s2 so i am wondering if there is any way to mess around with anything like start a fone call or send a text message from the terminal ?
i am looking for programs like netcat, sshfs, aplay, ... but none can be found.
i also notice this (not sure why):
Code:
/data/data/berserker.android.apps.sshdroid # ps auxw | grep tv
2594 system 0:59 /system/bin/tvoutserver
has anybody done anything cool from the android command line ?
is there someway i can run com.cooliris.media from the commandline ?
schneidz said:
hi, i installed sshdroid on my galaxy s2 so i am wondering if there is any way to mess around with anything like start a fone call or send a text message from the terminal ?
i am looking for programs like netcat, sshfs, aplay, ... but none can be found.
i also notice this (not sure why):
Code:
/data/data/berserker.android.apps.sshdroid # ps auxw | grep tv
2594 system 0:59 /system/bin/tvoutserver
has anybody done anything cool from the android command line ?
is there someway i can run com.cooliris.media from the commandline ?
Click to expand...
Click to collapse
I don't know what sshdroid does, but for sure you can use terminal emulator or adb shell to launch apps.
The "am" command can be used to launch applications.
The example below is to open Email app:
Code:
su
Code:
am start com.android.email
to dig in more:
http://forum.xda-developers.com/showpost.php?p=30175170&postcount=3
easy for sms less easy to make a direct call:
Code:
su
Code:
service call phone 2 s16 "123456789"
where 123456789 is the number you want to call
fyi, sshdroid turns your fone into an ssh server so i can log into my fone via wifi from my fedora machine and use an actual keyboard to issue commands instead of an on-screen keyboard.
its also useful for things like scp/sftp... i can mount the fones harddrive/sd-card with sshfs on my pc but i cant mount my pc's harddrive to the fone with sshfs. is there a solution for this yet (i think the problem is that there is no fuse module for android yet) ?
this is weird:
Code:
~ # am start com.cooliris.media
sh: am: not found
~ # which am
/system/bin/am
~ # /system/bin/am start com.cooliris.media
sh: /system/bin/am: not found
~ # whoami
root
~ # service call phone 2 s16 "0151234567"
Result: Parcel(
0x00000000: ffffffff 00000022 006e004f 0079006c '...."...O.n.l.y.'
0x00000010: 00530020 0061006d 00740072 00610063 ' .S.m.a.r.t.c.a.'
0x00000020: 00640072 00410020 00490050 006d0020 'r.d. .A.P.I. .m.'
0x00000030: 00790061 00610020 00630063 00730065 'a.y. .a.c.c.e.s.'
0x00000040: 00200073 00490055 00430043 00000000 's. .U.I.C.C.....')
made a little bit more progress:
Code:
/system/bin/am start com.cooliris.media
Starting: Intent { act=android.intent.action.VIEW dat=com.cooliris.media }
Error: Activity not started, unable to resolve Intent { act=android.intent.action.VIEW dat=com.cooliris.media flg=0x10000000 }
schneidz said:
fyi, sshdroid turns your fone into an ssh server so i can log into my fone via wifi from my fedora machine and use an actual keyboard to issue commands instead of an on-screen keyboard.
its also useful for things like scp/sftp... i can mount the fones harddrive/sd-card with sshfs on my pc but i cant mount my pc's harddrive to the fone with sshfs. is there a solution for this yet (i think the problem is that there is no fuse module for android yet) ?
this is weird:
Code:
~ # am start com.cooliris.media
sh: am: not found
~ # which am
/system/bin/am
~ # /system/bin/am start com.cooliris.media
sh: /system/bin/am: not found
~ # whoami
root
~ # service call phone 2 s16 "0151234567"
Result: Parcel(
0x00000000: ffffffff 00000022 006e004f 0079006c '...."...O.n.l.y.'
0x00000010: 00530020 0061006d 00740072 00610063 ' .S.m.a.r.t.c.a.'
0x00000020: 00640072 00410020 00490050 006d0020 'r.d. .A.P.I. .m.'
0x00000030: 00790061 00610020 00630063 00730065 'a.y. .a.c.c.e.s.'
0x00000040: 00200073 00490055 00430043 00000000 's. .U.I.C.C.....')
Click to expand...
Click to collapse
Informative.. thanks!!
Related
Hi all,
I have an elocity A7 Tablet running 2.2 Dexters ElocityA7 Modv1.2, full root access.
I managed to get usb ADB functionality working correctly after forcing the usb mode to client - i can run shell commands etc...
When I first attempted to launch applications from Eclipse I was getting messages stating /sbin/sh : am: not found. I finally managed to get that corrected by editing the am/pm files and creating the correct references with vi.
So now the applications finally install from Eclipse - HOWEVER - they do not launch when I attempt to run or debug. The Apps do get installed correctly, it just appears it Eclipse can't start the activity.
-USB debugging is enabled
Console output when I attempt to run:
==============================================
Code:
[2011-09-25 19:40:58 - test] Android Launch!
2011-09-25 19:40:58 - test] adb is running normally.
[2011-09-25 19:40:58 - test] Performing com.test.TestActivity activity launch
[2011-09-25 19:40:58 - test] Automatic Target Mode: using device '028041454220f4d7'
[2011-09-25 19:40:59 - test] Application already deployed. No need to reinstall.
[2011-09-25 19:40:59 - test] Starting activity com.test.TestActivity on device 028041454220f4d7
At this point nothing further happens - The logcat below just displays the debugger detaches but I don't know exactly why.
LogCat Output when I attempt to run:
==============================================
Code:
09-25 19:40:56.242: DEBUG/AndroidRuntime(12380): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
09-25 19:40:56.242: DEBUG/AndroidRuntime(12380): CheckJNI is OFF
09-25 19:40:56.242: DEBUG/dalvikvm(12380): creating instr width table
09-25 19:40:56.252: DEBUG/dalvikvm(12380): Unable to stat classpath element '/system/framework/com.nvidia.graphics.jar'
09-25 19:40:56.272: DEBUG/AndroidRuntime(12380): --- registering native functions ---
09-25 19:40:56.322: ERROR/BluetoothHidDeviceService.cpp(12380): register_android_server_BluetoothHidDeviceService: Registering HIDD Native Methods
09-25 19:40:56.402: DEBUG/AndroidRuntime(12380): Shutting down VM
09-25 19:40:56.402: DEBUG/dalvikvm(12380): Debugger has detached; object registry had 1 entries
09-25 19:40:56.412: INFO/AndroidRuntime(12380): NOTE: attach of thread 'Binder Thread #3' failed
09-25 19:40:56.592: DEBUG/dalvikvm(1331): GC_EXPLICIT freed 1088 objects / 60016 bytes in 35ms
Grateful if anyone has any ideas or can point me in a direction to determine what the cause may be? I know eclipse is configured correctly as I can launch and debug on my Sony Arc 2.3.3 - I think this might be related to a setting on the A7 system
I've narrowed it down to being a problem with my 'am' command - it's not actually doing anything. Anyone know the proper setup for the am command?
Currently this is what I have:
/sbin/am
--EMPTY-- I think this is the problem. If i delete this file however the am command is not found. Do i need to point this somewhere?
/system/bin/am
# Script to start "am" on the device, which has a very rudimentary
# shell.
#
#!/system/bin/sh
base=/system
export CLASSPATH=$base/framework/am.jar
exec app_process $base/bin com.android.commands.am.Am "[email protected]"
Wow as if - problem solved.
#!/system/bin/sh
Needs to be the FIRST line in the file.
Hi all,
I managed to successfully configure BT5, using the image, set up and managed to successfully use SSH and VNC (for ssh tunnel via adb).
But my need is a little different, I just need to open applications and export display over ssh (putty). Specifically Firefox you have installed Flash (FF's BT5 not have flash installed and when I execute the "dist upgrade" the FF stops working).
In summary:
I need to know if there is the possibility of running only Firefox's installed on my Webtop and export display over ssh.
What have a done:
I managed to solve the problem of xauth, copying what was already the "/ osh / usr / bin / xauth" to "/ usr/X11R6/bin/xauth."
FF running the command:
"export DISPLAY =: 0" after
"sudo-u adas dbus-launch / osh/usr/lib/firefox-6.0.2/firefox"
I'm getting this:
"
root @ (unknown) :/ # export DISPLAY =: 0
root @ (unknown) :/ # sudo-u adas dbus-launch / osh/usr/lib/firefox-6.0.2/firefox
No protocol specified
No protocol specified
No protocol specified
No protocol specified
Error: can not open display :: 0
root @ (unknown) :/ # uname-a
Linux localhost 2.6.35.7-g3798510 # 1 SMP PREEMPT Thu Oct 20 23:16:00 EDT 2011 armv7l unknown
"
I'm using a Razr GSM Droid
Android: 2.35
System Version: 651.73.240.xt910.Vivo.en.BR
Webtop: WT-2.0.0-82
Rooted and unblocked
Im good on network stuffs but just a newbie in linux.
Thanks in advance,
Storm
Did i post this question in wrong section?
stormclaws said:
Did i post this question in wrong section?
Click to expand...
Click to collapse
Will call someone that may help on this
See u
Sent from my XT910 using Tapatalk 2
I am a regulair Linux user but never used webtop.
The only reason I can get up with is that you try to run remote X as a non-authorised user, mostly after a sudo or su. So are you sure the autorisation (magic-cookie) is good?
Hope this points in the right direction.
That happens because you're using the wrong commands.
You're doing:
"export DISPLAY =: 0"
"sudo-u adas dbus-launch / osh/usr/lib/firefox-6.0.2/firefox"
You have to enter:
export DISPLAY= :0
sudo -u adas dbus-launch
Thank you for answering me, but apparently not working.
---
[email protected](unknown):/# export DISPLAY=:0
[email protected](unknown):/# sudo -u adas dbus-launch
No protocol specified
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-xSUDt7Zo5x,guid=b3a4338d764e43e81d27d8b700007bc2
DBUS_SESSION_BUS_PID=7635
---
I could try something else?
Thanks in advance,
Storm
---------------------
kholk said:
That happens because you're using the wrong commands.
You're doing:
"export DISPLAY =: 0"
"sudo-u adas dbus-launch / osh/usr/lib/firefox-6.0.2/firefox"
You have to enter:
export DISPLAY= :0
sudo -u adas dbus-launch
Click to expand...
Click to collapse
Guys, anyone coult gimme a hint?
stormclaws said:
Guys, anyone coult gimme a hint?
Click to expand...
Click to collapse
I can. Try asking kholk in his thread in the dev section. He did a webtop mod and probably have a solution.
Cheers
Sent from my XT910 using Tapatalk 2
I was looking up the partition layout of the Galaxy S III while I stumbled upon this problem.
The first time you run a command in 'adb shell' everything is fine, but when you try to run a second command, it just hangs. It doesn't crash, it just hangs.
So, I tried to find out what could be wrong, by doing the following: Instead of going into the shell itself, I just entered a semi-random command 'adb shell mount', which returned the normal result.
Then, I typed 'adb shell' and guess what? It returns a commonly known error: 'error: protocol fault (status 72 6f 6f 74?!)'
The status code is HEX, which translates to: 'error: protocol fault (status root?!)'
So I suppose this has something to do with the fact that my SGS3 is rooted.
I don't feel like unrooting it, but if someone would be so kind to test this on an unrooted SGS3 and report back the results here so we can investigate this further that would be greatly appreciated.
it works without any error.
do you know what to backup which contains kernel and ramdisk ?
Mine is rooted, with Omega Rom V3 and everything works perfect with adb.
Cranck said:
Mine is rooted, with Omega Rom V3 and everything works perfect with adb.
Click to expand...
Click to collapse
Have you tried multiple shell commands? I know adb functions, but it's about using adb shell.
I'm on the stock rom, rooted manually with CF's insecure kernel by the way.
I'm not sure this is related, but there is some very suspicious new functionality in the FactoryTest.apk, called "SysScope". Its some kind of service checking and verifying the authenticity of "something". But I have no idea of what, only that a related java file (ResultCode.class [sysscope.service] contain the following code segment:
Code:
[SIZE=2] arrayOfResultCode[0] = OK;
arrayOfResultCode[1] = ADB_RUNNING_AS_ROOT;
arrayOfResultCode[2] = PARTITION_TAMPERED;
arrayOfResultCode[3] = ROOT_PROCESS_FOUND;
arrayOfResultCode[4] = DANGEROUS_FILE_DETECTED;
arrayOfResultCode[5] = NOT_OFFICIAL_BINARY;
[/SIZE]
Then it looks for SysScope files in the SysScopeVerifyer.class like this:
Code:
[SIZE=2]/data/app/com.sec.android.app.sysscope-1.apk
/data/app/com.sec.android.app.sysscope-2.apk[/SIZE]
I suggest you to back these up, and then replace them, with empty files of the same name, and see what happens.
I have the exact same problem on the GS2, OneX, and OneS. I have no problem shelling into the devices using another system, but on one of my computers I have the same issue. Windows 7 64bit with jdk7 installed.
Also, I enabled adb trace to see what was being returned: set ADB_TRACE=all
-Entering ls three times on the OneX, the first time works correctly
Code:
ls
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): post uni
x_read(fdi=0,...)
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): pre unix
_read(fdi=0,...)
system/core/adb/commandline.c::read_and_dump():read_and_dump(): post adb_read(fd
=101): len=5
ls
system/core/adb/commandline.c::read_and_dump():read_and_dump(): pre adb_read(fd=
101)
system/core/adb/commandline.c::read_and_dump():read_and_dump(): post adb_read(fd
=101): len=32
acct
cache
config
cwkeys
d
system/core/adb/commandline.c::read_and_dump():read_and_dump(): pre adb_read(fd=
101)
system/core/adb/commandline.c::read_and_dump():read_and_dump(): post adb_read(fd
=101): len=318
data
default.prop
dev
devlog
etc
firmware_dsps
firmware_q6
firmware_radio
firmware_wcnss
init
init.elite.rc
init.goldfish.rc
init.qcom.rc
init.qcom.sh
init.rc
init.target.rc
init.usb.rc
mnt
proc
root
sbin
sdcard
sys
system
tombstones
ueventd.goldfish.rc
ueventd.rc
vendor
[email protected]:/ $ system/core/adb/commandline.c::read_and_dump():read_and_dump()
: pre adb_read(fd=101)
ls
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): post uni
x_read(fdi=0,...)
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): pre unix
_read(fdi=0,...)
ls
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): post uni
x_read(fdi=0,...)
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): pre unix
_read(fdi=0,...)
Dear all,
I installed Unbuntu Touch on my Nexus 4 yesterday (18.09.2013, with the build 20130917.1). It is working more or less, as expected :silly:
One of the problem I am facing is that the ssh server is not working. I could install (and --reinstall) it without problem (apt-get install openssh-server ssh), but if I check with "ps -ef|grep ssh") I only see the ssh-agent and the connection from another computer is not working.
Any idea?
Best regards,
Pierre
[email protected]:/# apt-get install --reinstall openssh-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/231 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 38659 files and directories currently installed.)
Preparing to replace openssh-server 1:6.2p2-6 (using .../openssh-server_1%3a6.2p2-6_armhf.deb) ...
Unpacking replacement openssh-server ...
Processing triggers for ureadahead ...
Processing triggers for ufw ...
WARN: / is world writable!
WARN: / is group writable!
Setting up openssh-server (1:6.2p2-6) ...
[email protected]:/#
[email protected]:~$ ssh [email protected]
ssh: connect to host 192.168.1.69 port 22: No route to host
[email protected]:/home/phablet/Downloads# ps -ef | grep ssh
phablet 739 711 0 09:11 ? 00:00:00 ssh-agent
I just noticed that I have the same problem...
If I had time I would look at it, too, but right now I have other things to do...
To98 said:
I just noticed that I have the same problem...
If I had time I would look at it, too, but right now I have other things to do...
Click to expand...
Click to collapse
Same problem here. ssh to another device is possible, but no acces to phablet.
Same In GNex
try
sudo service ssh start
(if you are root or not you must use sudo)
but it does not automatically start when reboot
Still not wokring
[email protected]:/# service ssh start
ssh start/running, process 5890
[email protected]:~$ ssh [email protected]
ssh: connect to host 192.168.1.69 port 22: No route to host
[email protected]:~$ ps -ef|grep 5890
vmalep 12613 12544 0 13:00 pts/4 00:00:00 grep --color=auto 5890
chaoskernel said:
try
sudo service ssh start
(if you are root or not you must use sudo)
but it does not automatically start when reboot
Click to expand...
Click to collapse
thank you! installed version 57 and used
sudo service ssh start
work fine!
Hello, I was given a Gtablet by a friend. Everything is in proper working order except for the wifi. The wifi will endlessly scan, never pulling up any SSIDs. Here's what I've done to troubleshoot:
Ascertained flight mode was off (it was)
Enabled wifi through the developer options (Did nothing)
Manually enter SSID/Security information (Claims that SSID is not in range)
Reloaded the OS (He had VEGAn Tab on there. I reloaded the 5.1 Beta. I don't know what version he had on there, oops.)
After a clean install I have the exact same issue, which leads me to believe it is a hardware issue rather than a software issue. Is this common? Am I forgetting something? Would loading an entirely different ROM be of any use or do they also use the same driver?
My apologies if this has been answered previously, but in all my searching I can only find people who have this problem temporarily; a reboot fixes it for them. I haven't been able to find someone who has had this as a persistent issue.
JungleWallace said:
Hello, I was given a Gtablet by a friend. Everything is in proper working order except for the wifi. The wifi will endlessly scan, never pulling up any SSIDs.
Click to expand...
Click to collapse
I'll have to look at some logs to ascertain what your WiFi problem is.
Run the commands in this post (after rebooting the tablet) and then post the text files that're created.
rajeevvp said:
I'll have to look at some logs to ascertain what your WiFi problem is.
Click to expand...
Click to collapse
Thanks, see attached are the logs as per request. As a side note, now that I have the terminal emulator on there I tried a few commands I dug up on the internet after I looked over the logs.
Code:
$ su
# ifconfig tiwlan0 up
# ifconfig eth0 up
Both gave an error message
Code:
error: SIOCGIFFLAGS (No such device)
Also
Code:
# svc wifi enable
did not solve my issues. Oh well.
FYI:
JungleWallace said:
...I tried a few commands I dug up on the internet after I looked over the logs.
Code:
$ su
# ifconfig tiwlan0 up
# ifconfig eth0 up
Both gave an error message
Code:
error: SIOCGIFFLAGS (No such device)
Click to expand...
Click to collapse
The wireless LAN interface name on the gTab is wlan0. Hence your error messages: "No such device" for the ifnames tiwlan0 and eth0. (The latter would work for the ethernet I/F on the dock--if you had one connected.)
Also
Code:
# svc wifi enable
did not solve my issues. Oh well.
Click to expand...
Click to collapse
1. You have to look at the Android system logs (using logcat) to see the result of that svc command.
2. Your Android logs indicate that your WiFi interface is a) disabled at startup and b) then not enabled thereafter:
Code:
01-07 23:21:10.429 V/ConnectivityService( 990): Starting Wifi Service.
01-07 23:21:10.429 I/WifiService( 990): WifiService starting up with Wi-Fi [B]disabled[/B]
Suggestions:
Since this now looks like a ROM problem (ie. not HW):
1. See this thread. Run the script to disable Airplane Mode which might be causing your problem. If that doesn't work, try step 2:
2. Boot into CWM and then a) Format /cache and b) Repartition the Internal SD card (take the external one out first).
You'll lose all your current apps and data with this step, essentially reverting to a "fresh" install of your ROM.
Re-setup WiFi, time & date and other things again.
If step 2. doesn't work, report back next year, and I'll give you more commands to run then.
rajeevvp said:
If step 2. doesn't work, report back next year, and I'll give you more commands to run then.
Click to expand...
Click to collapse
Negative. Ran the airplane fix script, nothing. Reset cache/re-partitioned, still nothing. It's still endlessly scanning/shutting off/scanning.
JungleWallace said:
Negative. Ran the airplane fix script, nothing. Reset cache/re-partitioned, still nothing.
Click to expand...
Click to collapse
OK. Not one of the common simple problems, then.
It's still endlessly scanning/shutting off/scanning.
Click to expand...
Click to collapse
This is puzzling because from your last logs, it doesn't look like the wlan kernel driver was even loaded, so no AP scanning should be possible. A little background will clarify what I mean.
On all the 2.6.32.x kernels for the gTablet, the wlan driver is not compiled into the kernel. Instead, it is built as a separate kernel module which is loaded and unloaded as needed by Android (from the files in /system/lib/hw/wlan/). When the wlan driver is loaded both the kernel (dmesg) and Android (logcat) will show some characteristic messages and until the driver is inserted into the kernel no AP scanning, or other wireless functions, should be possible. And, no wlan driver-related messages in your logs tells me that the driver was likely not loaded. (Also, only after the wlan driver is loaded does it check and initialize the wireless HW. So, only after its been loaded, strictly speaking, can we rule out a HW problem.)
Sometimes the Android logs are not complete, so I want to you setup ADB on your PC, enable USB debugging on the gTablet (Setting > Applications > Development) and collect the Android logs like this from now on:
1. Power off gTab; attach the USB cable to it.
2. Open a CMD.exe window on the PC, then run this command (and keep the window minimized):
Code:
C:\> [B]adb logcat -v time > logcat.txt[/B]
After all the tests/commands have been done, restore this window and press Ctrl-C to kill ADB and terminate Android log collection.
3. Power on the gTablet. The ADB command will wait for the gTablet and keep collecting logs on the PC.
Post also the output of these commands:
Code:
C:\> [B]adb shell dmesg > dmesg.txt[/B]
C:\> [B]adb shell lsmod > lsmod.txt[/B]
C:\> [B]adb shell "cd /; find system -type f -print0 | xargs -0 sha1sum" > sha1sum.txt[/B]
Is this the ROM you currently have?
Have you applied the VEGAn 1.00 beta 5.1.1 supplement also?
rajeevvp said:
OK. Not one of the common simple problems, then.
.........
Is this the ROM you currently have?
Have you applied the VEGAn 1.00 beta 5.1.1 supplement also?
Click to expand...
Click to collapse
That was the current ROM I was using. I had not applied the supplement yet, but now I have. Still the same issue. Here are the logs.
JungleWallace said:
That was the current ROM I was using. I had not applied the supplement yet, but now I have. Still the same issue. Here are the logs.
Click to expand...
Click to collapse
In this one I can see the kernel WiFi driver being loaded, and the driver is not reporting any HW chip, SDIO bus, or other errors:
Code:
<4>[ 23.485281] sdio_reset_comm():
<4>[ 23.503617] DHD: dongle ram size is set to 294912(orig 294912)
<4>[ 23.676913] Firmware version = wl0: May 17 2010 22:38:50 version 4.218.223.1
<4>[ 23.887647] wlan0: Broadcom Dongle Host Driver mac=e0:2a:82:08:3e:81
<4>[ 23.894047] Enter wl_control_wl_start
<4>[ 23.897864] Exited wl_control_wl_start
<4>[ 23.907103]
<4>[ 23.907109] Dongle Host Driver, version 4.218.223.1
As far as the kernel driver is concrned, everything looks OK, but the Android logs still don't show any SSID associations.
What're the exact outputs of these commands? (You can post a screenshot. Mask the psk= value from the 1st output, if present)
Code:
C:\> [B]adb shell "fgrep -v '#' /data/misc/wifi/wpa_supplicant.conf | tr -s '\n'"[/B]
ctrl_interface=wlan0
update_config=1
...
C:\> [B]adb shell wpa_cli -i wlan0 driver rssi[/B]
...
C:\> [B]adb shell wpa_cli -i wlan0 driver linkspeed[/B]
LinkSpeed [I]nn[/I]
C:\> [B]adb shell wpa_cli -i wlan0 scan[/B]
OK
C:\> [B]adb shell wpa_cli -i wlan0 scan_results[/B]
bssid / frequency / signal level / flags / ssid
aa:bb:cc:dd:ee:ff 2452 185 [WPA2-PSK-CCMP] [I]YourSSID[/I]
Collect also the dmesg and logcat outputs as before.
[/FONT]
rajeevvp said:
What're the exact outputs of these commands? (You can post a screenshot. Mask the psk= value from the 1st output, if present) [...] Collect also the dmesg and logcat outputs as before.
Click to expand...
Click to collapse
See attached. Ignore my syntax errors that I underlined. I was typing wlan instead of wlan0.
JungleWallace said:
Ignore my syntax errors that I underlined. I was typing wlan instead of wlan0.
Click to expand...
Click to collapse
Those are OK since you've corrected them. But, these commands you'll have to redo:
1. In the first command (fgrep ... | tr), you've typed a '/' (forward slash) instead of what I've given in the example, which is a '\' (back-slash) character.
The correct character will remove all those blank lines. But, this is a minor typo compared to:
2. The last 2 commands (wpa_cli scan* ...), which you'll have to redo. This time without the extraneous driver argument (again, see the example)--which turns it into a completely different (and non-existent) command. This is why the output doesn't look like what I've shown.
Instead of typing the commands in manually, select and copy the command lines from the browser and paste them into the shell window.
You might also want to increase the no. of columns that CMD.exe displays: Right-click on the title-bar; choose Properties; select Layout; increase the no. of Columns to, let's say, 150.
3. That dmesg.txt file is not very useful because you've not rebooted the tablet before issuing that command.
The kernel has a fixed-size message buffer, so all the HW initialization messages printed only at system boot will be overwritten by later, and irrelevent, messages as time passes. From the timestamps, it looks like your tablet's been on for a couple of weeks, at least--I can't see any of the earlier boot-up messages.