So I've been putzing around with this thing for a few days since I got it. One thing I've been trying to do now that I have root access is get it to connect to adhoc wifi. To be specific, I want to use my data-enabled cellphone as an adhoc wireless access point so that I can connect the LePan to it over wifi to surf the net, email, play games, etc. Of course, by default, Android is set up NOT to connect to adhoc wireless, or even recognize adhoc networks.
I installed a wifi sniffer app on the LePan, and it can see the adhoc network that my phone is broadcasting, but it won't connect. I managed to find a few webpages with instructions on how to mod android to connect to adhoc, but most of the instructions are device specific, and obviously there's nothing out there for the LePan yet, as its a relatively new device (I would have posted this in the TC970 forum here on xda, but there isn't one yet). Most of the instructions talk about modifying two files in the /system/etc/wifi folder. The first is tiwlan.ini, and the other is wpa_supplicant.conf.
I basically mixed/followed the instructions on these two webpages:
http://www.slatedroid.com/topic/1054...adhoc-on-a81e/
and
http://www.slatedroid.com/topic/1819...rk-android-22/
So right now I've added the following lines to tiwlan.ini:
WiFiAdhoc = 1 (Change from 0 to 1)
dot11DesiredSSID = InsertyourSSIDhere
dot11DesiredBSSType = 0 (Add this line in)
And I've replaced everything in the wpa_supplicant.conf file with this:
ctrl_interface=tiwlan0
update_config=1
eapol_version=1
ap_scan=2
network={
ssid="Ad-hoc ssid here"
scan_ssid=1
key_mgmt=NONE
mode=1
priority=1
}
network={
ssid="Your Accesspoint ssid here"
psk="your wpa key here"
key_mgmt=WPA-PSK
priority=2
}
(obviously I have my own settings in the real file)
In addition, I copied the wpa_supplicant file from the zip in this post:
http://forum.xda-developers.com/showthread.php?t=754961
into /system/bin/.
Now when I try to use my wifi, it turns on, says its trying to connect for a bit, but then the eventually just turns off without connecting or detecting any networks (so it probably doesn't actually turn on at all).
I've backed up all my files, so no problem getting it all back and working like stock, but I'd really like to be able to connect to adhoc with my new tablet. Suggestions are most welcome.
***Sorry if this is posted in the wrong forum. Like I said, there is not yet a dedicated forum for this device, otherwise I would have posted there. Mods - any chance of creating a forum for this device? I've seen a few other stray TC970 posts here on xda.
Sandmonkee,
After messing about with this myself, I found a supplicant that works on our tablet (I tried about 6 different supplicants until I found this one). It is the one for a nook color. See this thread http://forum.xda-developers.com/showthread.php?t=868354
It works on my Nokia N900 with the MobileHotspot app.
I believe that the problem with the supplicants that were in the post that you referred to is that they were linked to use wext instead of the statically linked libCustomWifi for the TI chip. See the comments section on szym's blog about the patch.
It would be better to apply szym's patches to the code tree that was used to create the wpa_supplicant for this tablet instead of TI's reference code as this one did. That might fix the sleep problem. I don't know where to find the sources. Anybody have any ideas? If the sleep issue becomes a problem, I might look into modifying the reference code (altho' I have enough on my plate without spending too much time on this toy).
***** UPDATE ****
This supplicant doesn't have a problem on this tablet with sleep as was described in the above thread.
***** END UPDATE ****
BTW the wpa_supplicant.conf that you want to modify is in /data/misc/wifi NOT /system/etc/wifi
Here is my version (replace the ****** with values appropriate for you)
The 1st entry is for my AP using WPA, the 2nd one is for my ad-hoc phone using WEP. You might need to add the line "ap_scan=2" if you don't broadcast a SSID.
Code:
ctrl_interface=tiwlan0
update_config=1
network={
ssid="*****"
psk="*********"
key_mgmt=WPA-PSK
priority=1
}
network={
ssid="*********"
scan_ssid=1
key_mgmt=NONE
group=WEP104
auth_alg=SHARED
wep_key0="********"
priority=2
mode=1
}
I don't know if the "group=WEP104" line is needed, I found it in another thread somewhere but it doesn't seem to hurt.
Let me know if this works for you too.
-Shawn
Works!
Shawn, yer a genius.
I have been struggling with this for a week or so now, and it is finally working. You just increased the usefulness of my tablet by 100x
Thanks again man!!
Mike
yeah, bro. That's what's up.Thanks!
This is great stuff...thanks for sharing. One quick question for you guys: are you using adb to modify the files? I can't seem to get adb to work...do i need a driver different than the one derkoch linked to in the root achieved thread?
joofeloof,
I used the one that you referred to. I rooted the tablet. Then for my own sanity I installed HackersKeyboard to get a real keyboard, bash shell so I could get filename completion, and nano for a small editor from the shell. Now the tablet is much like a standard linux system from the command line. I used adb to push the files to the sdcard and copied the files to the correct locations from a local shell. Don't forget the permissions. Any text editor will work to edit the configuration files, altho' I prefer nano. If you are familiar with vi, it is available also.
If you can't get adb to work, you could just copy the files to your sdcard and move them locally.
To do this mod, the tablet must be rooted.
Hope this answers your questions.
-Shawn
P.S. Does anybody know how to get a bluetooth hid device (keyboard/mouse) to work on this tablet? There is a nice folio that has a BT keyboard built in that would make this a great terminal for doing remote system admin stuff.
**** UPDATE****
Found it. For BT keyboard use EasyConnect which is available in the market.
**** END UPDATE ****
Non-terminal instructions
joofeloof said:
This is great stuff...thanks for sharing. One quick question for you guys: are you using adb to modify the files? I can't seem to get adb to work...do i need a driver different than the one derkoch linked to in the root achieved thread?
Click to expand...
Click to collapse
Shawn's method above will work, but I did it using ES File Explorer with root permissions enabled.
1. Root your phone as described in DerKoch's post
2. Download Shawn's wpa_supplicant file to your PC and extract
3. On your tablet, download and install ES file explorer from the market (its free)
4. Open ES explorer and go into the settings. At the bottom of the list, enable "root explorer" and "mount file system"
5. Use ES file explorer to copy your /data/misc/wifi/wpa_supplicant.conf to your SD card
6. Plug the tablet into your PC and turn on USB file sharing and USB debugging
7. Copy the wpa_supplicant.conf file from your SD card to your PC and modify per Shawn's instructions above, with your own settings.
8. Save the file and then copy it back to your SD card, along with Shawn's wpa_supplicant file
9. Stop USB file sharing on the tablet
10. turn off wifi on your tablet.
11. Open ES file explorer on the tablet, copy the wpa_supplicant.conf file from your SD card to the /data/misc/wifi directory (overwrite), then copy Shawn's wpa_supplicant file to /system/bin (also overwrite).
11.5 Note that these files need to have the right permissions (by default, they should already). In ES file explorer, do a long press of the wpa_supplicant file you just copied to /system/bin, then click on properties, then "change permissions". It should be chmod755, ie the X's should look like this:
X X X
X 0 X
X 0 X
For the wpa_supplicant.conf file, it should be chmod777 (ie ALL the boxes should have X's)
12. Turn on wifi. That should do it.
I noted that although I included the lines from Shawn's file for the adhoc WEP security, when my tablet saw the phone (which was unsecured), it created a new entry in the list of available networks for the open signal. So those lines may not be necessary. In fact, I suspect the only part that may have been necessary would be the header information (ap_scan=2 and all that), since Andriod just makes entries in the wpa_supplicant.conf file when you tell it to remember an access point. If its not already in the .conf file, it still shows up in your list of available AP's, it just doesn't remember it in your list.
Either way, thanks again to Shawn for figuring this out!
Much appreciated! Working fine, just fine...I was heading down this path anyway, more curious about how to get adb working than anything.
Many thanks.
Also, does or has anyone play[ed] around much with /proc settings?
I'm more familiar with linux server admin than any of the android specifics - but it seems like many of the kernel settings are readily configurable. I just don't know which would really be of interest in a tablet configuration/setting.
Now, my next question is.. anyway to enable Wifi channel 12-14?
Worked Great. Thank you for figuring this out. Now I can make use of that 6gb data plan.
Wireless Tether 3.1 Beta Supports ad-hoc
SilverFang83 said:
Worked Great. Thank you for figuring this out. Now I can make use of that 6gb data plan.
Click to expand...
Click to collapse
hey y'all....
just a heads up (and y'all might already have this info but jussssst in case there are ppl like me out there that read this thread and said, "um, maybe i don't need to have my LePan use my phone's network after all"...(lol) it seems the most recent version of wireless tether 3.1 beta i think http://code.google.com/p/android-wifi-tether/) supports ad-hoc. I just downloaded it, changed from "disabled to enabled" in Acess Control, and then "in CHANGE Device Settings" picked a phone like mine (they didn't have The Infuse but Galaxy S worked)
You might have to restart the Wireless tether ap but after it automatically showed my network on LePan. made a quick video on it here: http://www.youtube.com/watch?v=wACwGZ0XyuA&list=UU-xOxPoQXnvEQKqkucrM_Cg&index=1&feature=plcp
No matter what settings i tried on earlier versions of Wireless Tether it would NOT work, but the new 3.1 v8 Beta did : )
Anyway, i'm a little out of my depth here so if i have posted this in wrong place or if it doesn't directly correspond to the issue at hand, please forgive, just tryin' to help other numbnuts like me : )
Ms D
Alright! Gave it a try with MyWi 4.0 on Iphone 4, can see the SSID and try to connect but fails to get an IP, goes to a loop of trying then scanning then trying to obtain IP. Oh well.
EDIT: made it forget network and re-entered password from settings, worked. I'll post the .conf file in a sec.
EDIT2:
Here are my settings for MyWi 4.0 using Iphone 4
--------------------
ctrl_interface=tiwlan0
update_config=1
network={
ssid="yournetwork"
key_mgmt=NONE
auth_alg=OPEN SHARED
wep_key0=yourkey
priority=4
mode=1
--------------------
The tablet should enter those for you when you first try to connect to your network, though.
GOOD JOB EVERYONE
Now this is bizarre to me... The supplicant and the mods on the *.conf file works great, yet if I reboot the tablet, the *.conf file's permissions gets automatically modified to
X X 0
X X 0
0 0 0
thus causing an error on the wifi's startup.
I used Es file explorer to set the permissions and when I change 'em back, well everything works fine.
I'm quite puzzled atm.
Tried to use Terminal Emulator app to set the permissions with adb but I get a permission denied, and no SuperUser prompt :/ .. do you guys use adb from sdk via usb?
Help? Trouble with Barnacle
First off great work guys.
I never connected ad hoc before, and didn't realize I needed to root at first. I finally got it to see my droid eris' wifi network (thanks largely to Sandmonkee's step by step guide) using barnacle and to actually connect but as soon I try going to a webpage on the tablet barnacle freezes and then generates a boat-load of NAT:restart: network is unreachable errors.
What are you all using to broadcast the ad hoc network?
***EDIT
NEVERMIND, Ms.Dummbunny's solution worked for me too
BreeZyer said:
Now this is bizarre to me... The supplicant and the mods on the *.conf file works great, yet if I reboot the tablet, the *.conf file's permissions gets automatically modified to
X X 0
X X 0
0 0 0
thus causing an error on the wifi's startup.
I used Es file explorer to set the permissions and when I change 'em back, well everything works fine.
I'm quite puzzled atm.
Tried to use Terminal Emulator app to set the permissions with adb but I get a permission denied, and no SuperUser prompt :/ .. do you guys use adb from sdk via usb?
Click to expand...
Click to collapse
I have been trying to do this for the past two days without success too. I have this permission problem. Plus, my tablet just shows "obtaining IP address" for a moment then disconnects. I am not trying to tether from my phone though, I have an old laptop with an intel 3945 card, trying to setup an adhoc network and connect to it. My SGS2 with MIUI works perfectly fine, so it is doable. Any suggestions what else I can try?
OK, this is sort of related...
I go Le Pan TC970 connected on Ch 12!
Base on http://forum.xda-developers.com/showthread.php?t=1067944
I manually modified the settings.db and it sort of worked (Ch 12 only, and no go on Ch 13 for some reasons....)
Steps...
Copy /data/data/com.android.providers.settings/databases/settings.db to sdcard
Modify settings.db using SQLite "Manager" by adding extra row 116, wifi_country_code, EU in "secure" table
Rename /data/data/com.android.providers.settings/databases/settings.db to /data/data/com.android.providers.settings/databases/settings.db.bk just in case
copy the newly modified settings.db from sdcard back to /data/data/com.android.providers.settings/databases folder
Reboot
==
Update: WiFi Analyzer can see my AP when set to Ch13 too. But it can't connect, and I think maybe is my router....
whatid said:
OK, this is sort of related...
I go Le Pan TC970 connected on Ch 12!
..
Click to expand...
Click to collapse
Hey whatid,
Just curious - what is the advantage of having channel 12? Also, did you have to mod your router at all?
Sandmonkee said:
Hey whatid,
Just curious - what is the advantage of having channel 12? Also, did you have to mod your router at all?
Click to expand...
Click to collapse
Depends where you are located, in Europe you can use Ch 12&13 and Japan with additional Ch14.
Some router will let you select Ch 12-14. Or if you have DDWRT installed.
MsD...Thanks for the info. I tried this on my phone (Xperia Play R800X) and none of the phones in the list worked for me...but I did get a nice little interruption from Verizon in my browser about using my phone as a hotspot when I decided to give up and just opened my browser. It would not go away until I rebooted the phone...I'm guessing Verizon doesn't like tethering...lol
Hey whatid,
Thanks for the info. Are you using the unit in North America? If so, you might just want to double check the frequencies on some of the other devices in your house (phone, microwave, etc), as they are often very close to wifi frequencies (~2.4GHz). I know its unlikely to actually happen, but you could get crosstalk.
Also, would you consider starting a new thread with your method of unlocking these channels? I don't mind the info being here in this thread, I was just thinking it might make it easier for other people to find, and it is good info. Plus, the more we pollute the general forum with our TC970 stuff, the more likely they are to finally give us our own forum
Related
This is a program I wrote a while back that allows transparent tethering over USB without requiring root access. It works by simulating an unencrypted OpenVPN server and then internally running everything through a Java-based NAT. I get decent speeds off it, but your mileage may vary. It's a bit beta! Might explode! Wear eye protection!
It has a really basic website at http://lfx.org/azilink/, but to spare your eyes I'll just paste the instructions below:
Required files:
- ADB from the 1.1 SDK or from http://lfx.org/azilink/adb.zip
- OpenVPN 2.1 (not 2.0) from http://openvpn.net/index.php/downloads.html
- AziLink.apk from http://lfx.org/azilink/azilink.apk
- AziLink.ovpn from http://lfx.org/azilink/azilink.ovpn
Installation:
1) Install OpenVPN on the host. I use version 2.1_rc15, but any version should work. Apparently if you use version 2.0 you'll need to remove the NO_DELAY option from the AziLink.ovpn configuration file. You can find OpenVPN at:
http://openvpn.net/index.php/downloads.html
2) Enable USB debugging on the phone. From the home screen, this is under
Settings>Applications>Development>USB debugging.
3) Install the Android USB driver (if you don't already have one installed).
See http://code.google.com/android/intro/develop-and-debug.html#developingondevicehardware
4) Install the program. You can either use ADB to install by typing
"adb install azilink.apk" with the file in the current directory, or you can browse (on the phone!) to: http://lfx.org/azilink/azilink.apk
Either way you might need to allow installation from unknown sources
under Settings>Applications>Unknown Sources.
Configuration steps:
1) On the host, run "adb forward tcp:41927 tcp:41927" to set up port forwarding. Be sure to use adb from the Android 1.1 SDK! The version from 1.0 will lock up under heavy load. If you don't want to download the entire SDK, you can get a copy of ADB+drivers from http://lfx.org/azilink/adb.zip
2) On the phone, run AziLink and make sure "Service active" is checked.
3) Right click AziLink.ovpn on the host (not in the web browser!) and select "Start OpenVPN on this configuration file." You can find this file at: http://lfx.org/azilink/azilink.ovpn. If you're using Linux or, god forbid, MacOS, you'll also need to manually set the nameserver to 192.168.56.1 (the phone's NAT IP address).
Nice work around.
Wow, amazing work! I'll definitely have to mess around with this tomorrow...
OpenVPN 2.0.9
Thnx for the manual..!! Took me something to get it working, i'll find out, that it isn't working with OpenVPN version 2.0.9
OpenVPN 2.0.9 doesn't recognize the following rule in azilink.ovpn:
socket-flags TCP_NODELAY
And it worked with version 2.1rc15...
So no more Internet Sharing on Windows Mobile...
OpenVPN 2.0.9
Thnx for the manual..!! Took me sometime to get it working, i'll find out, that it isn't working with OpenVPN version 2.0.9
OpenVPN 2.0.9 doesn't recognize the following rule in azilink.ovpn:
socket-flags TCP_NODELAY
And it worked with version 2.1rc15...
So no more Internet Sharing on Windows Mobile...
help
Ok I'm a complete noob and I've played about with this but can't get it to work. How do I run adb? As in the very first step? Where do I type that. Do I need to install adb and how do I do it?
Thanks
Got it working
Man this is awesome.
I realised i needed to run the adb from cmd. see when i tried to open adb.exe it just kept closing.
thanks alot. this rocks
ps im writing this off my tethered pc
zecbmo said:
Ok I'm a complete noob and I've played about with this but can't get it to work. How do I run adb? As in the very first step? Where do I type that. Do I need to install adb and how do I do it?
Thanks
Click to expand...
Click to collapse
Nah, you can just unzip adb and run it directly from that folder. It's a command line program, so you'd need to run it from a command prompt (cmd.exe). I'm not sure whether adb needs to run as an administrator or not (I disable all that UAC garbage in Vista). If you have the proper driver installed, then the ADB command should return immediately without saying anything. If it says "waiting for device..." that means it wasn't able to find the Android debug driver.
I know this is all a bit hacky, but now that we've got root and wifi tethering I figured that there wouldn't be too much interest.
cheers
its working great like. im using this cus i havent rooted my phone yet. tethering was the only reason why i wanted to root it but this is a great alternative
Works Great. Thanks for the easy instructions.
Here is translation of post on Russian with images http://androidteam.ru/faq/azilink-tethering-with-android-usb.html
I have repacked all in one zip, and make some command files to make process a little easy.
another trick that may help on XP machines, probably other versions as well.
Create a shortcut to adb.exe on your windows desktop (mine is located in C:\and\tools)
Modify the 'target' (right-click,properties) of the shortcut to read C:\and\tools\adb.exe forward tcp:41927 tcp:41927 <I think this is the right code, I'm still using tetherbot on 1080>
That's it. Once everything's set up connecting is easy. one click on the computer, no cmds required
does this allow for media such as flash on web site to play on the laptop?
clevetbs said:
does this allow for media such as flash on web site to play on the laptop?
Click to expand...
Click to collapse
If you've got enough bandwidth. I'm not really sure what bitrate flash video runs at though.
Many thanks for this, aziwoqpd. I've not had the time to root, but have been looking for an easy way to tether. A usb connection is great, since the battery drains so quickly anyway it's nice to keep a charge going.
sonikamd - thanks for the suggestion, it's a great idea. Unfortunately my XP doesn't want to accept your syntax. I wish I could offer something else, but my skills (ha!) are nonexistant. I'm embarassed to say that I had to refresh my memory on how to maneuver around command lines...
Got any other suggestions?
Thanks again for all your work!
the AziLink.ovpn file wont download for me.
works fine for me, GREAT WORK!
Okay, so I'm trying this out on a mac. I've successfully built openvpn and have my tunneling device (/dev/tun0, /dev/tun1, etc.). I run the adb forward command and it starts the daemon successfully, I fire up azilink on the phone and it says it's waiting for the connection, I fire up openvpn and the phone changes to stating that it's connected. Openvpn does not exit out - it starts the tunnel - BUT in the logging it reports " ROUTE: problem writing to routing socket" twice (which oddly appears to be a non-fatal error to the application), and traffic is unable to flow. I'm guessing it's something about openvpn not correctly manipulating the darwin routing tables, but I've been unsuccessful thus far in figuring out the nature of the problem so I thought I'd check here.
I'm running the straight azilink openvpn config file, which means if I need any syntactical changes for darwin I haven't applied them. The openvpn documentation is not terribly good and I was unable to find any documentation of routing command differences for MacOS (if that's even the problem, of course).
Edit: I forgot to mention, I've been trying to ping known-good IPs by address to test the routing - after my first attempt at loading a web page failed I figured it best to remove name services from the possible list of problems. The bytes sent count was slowly incrementing (up to about 23K bytes in ten minutes of diagnosis), and the inbound count got up to about 900 bytes in the same period, so clearly *something* was getting through - unless those counters are counting all traffic into and out of the phone and just going over the cable - but I got no ping responses, no websites could load, and by all appearances from the terminal, no data was moving.
lindsayt said:
I'm running the straight azilink openvpn config file, which means if I need any syntactical changes for darwin I haven't applied them. The openvpn documentation is not terribly good and I was unable to find any documentation of routing command differences for MacOS (if that's even the problem, of course).
Edit: I forgot to mention, I've been trying to ping known-good IPs by address to test the routing - after my first attempt at loading a web page failed I figured it best to remove name services from the possible list of problems. The bytes sent count was slowly incrementing (up to about 23K bytes in ten minutes of diagnosis), and the inbound count got up to about 900 bytes in the same period, so clearly *something* was getting through - unless those counters are counting all traffic into and out of the phone and just going over the cable - but I got no ping responses, no websites could load, and by all appearances from the terminal, no data was moving.
Click to expand...
Click to collapse
The byte counters only include traffic that OpenVPN is forwarding, so something is making it over. Did you try changing the DNS server to either 192.168.56.1 or an external address like 4.2.2.2? OpenVPN on MacOS and Linux won't set the nameserver automatically.
Also, there's a bit of a problem with pinging. The app on the phone can't generate ICMP ping packets since it isn't running as root. When you send an ICMP ping, the phone translates it to a UDP ping, sends it, and translates the reply back to a ICMP ping. Unfortunately, probably about 50% of hosts don't reply to UDP pings. Some that I've tested with that do work are lfx.org and he.net.
I'll see if I can give it a quick test on a Mac sometime tomorrow.
EDIT: I managed to get it working, although T-Mobile's so-called "transparent" web proxy is barely working today so I was having trouble accessing websites without getting errors. SSH was working fine, though. Anyway, here's what I did:
1- Installed a MacOS port of OpenVPN called Tunnelblick (didn't have XCode handy to compile my own and it's got a pretty GUI)
2- Copied azilink.ovpn to /users/azi/library/openvpn or whatever it is
3- Click the Tunnelblick icon in the upper-right, go to details, click "set nameserver"
4- Remove the TCP_NODELAY line because it was complaining that my kernel didn't support it (and would cause my connection to timeout after about 30 seconds).
5- Clicked connect
If you want to see what traffic's going over openvpn, you can just run "sudo tcpdump -n -i tun0"
wow ... this works great ... tested using a german G1 under linux (arch 686), win vista (x64) & win xp (x86) ... pretty good speed and low latency (actually i can't notice any latency at all - no mather if using wlan or 3g)!
GREAT WORK!!!
Hi again guys!
Ever since the ATT update usb connecting to the phone in ubuntu is sporadic and unreliable. I can usually get my photos off of it. Sometime I can even get into a non-root basic filesystem as well
However this isn't my main problem. I want to root the phone and install custom ROM's etc... Tried the VMware and a version of windows and installed the samsung drivers to XP but have trouble (again) with the usb and VMware.
Any help would be appreciated.
Additionally I'm pretty pissed off about the update thing. I don't care about tethering per se but that underhanded **** is why I dumped microsoft in the first place. I'll dump ATT too and spend my money elsewhere.
maskvp said:
Hi again guys!
Ever since the ATT update usb connecting to the phone in ubuntu is sporadic and unreliable. I can usually get my photos off of it. Sometime I can even get into a non-root basic filesystem as well
However this isn't my main problem. I want to root the phone and install custom ROM's etc... Tried the VMware and a version of windows and installed the samsung drivers to XP but have trouble (again) with the usb and VMware.
Any help would be appreciated.
Additionally I'm pretty pissed off about the update thing. I don't care about tethering per se but that underhanded **** is why I dumped microsoft in the first place. I'll dump ATT too and spend my money elsewhere.
Click to expand...
Click to collapse
Linux user here. I haven't had the problems you describe. I have lately been using ES File Explorer to copy to and from a shared folder on my desktop. avoiding the USB for file transfers all together. when I do connect via USB I usually use ' adb push' and 'adb pull' to move files around.
To Root your phone there is an 'update.zip' method that I used (no computer needed)
There is also a tool called ClockworkMod Recovery that you can use to install custom rom's and create nandroid backups. (no computer needed)
And finally if you manage to screw up and can not boot, you can use Heimdall on linux like you would use Odin on Windows.
enjoy your phone...
-p
Thank-you so much!!!
I was thinking about exactly what you wrote. Why not do it the linux way? Admittedly my skills are weak.
Had a little trouble with the update.zip but went to the wiki (again) and the info on how to do it from the phone was there. BTW the wiki has improved since last week.
Rooted phone and installed Titanium Backup and Clockwork Recovery. In my excitement I deleted all the ATT bloatware before backing them up and the ROM. Oh well... Too bad.
Now I just feel great about my phone. Needs some customization but no hurry. Only thing was that TB prompted me to go to settings/applications/ and tick "unknown sources". Doesn't exist.
Thanks again! If you have anymore nuggets of info...?
linux newb here but i try
edit:
the phone can mount to a vm in dowload mode for use with odin or in kies mtp mode as long as debugging is off, otherwise it likes to mount to the host pc as a drive, i dont know a work around but you can make the phone a shared folder with the vm client so you can see the files in the vm, it'll be seen as a network location in that case.
it can mount as a drive in linux but you need to select to mount from the phone. i was having problems with it in eclair in windows and didnt try it in linux but froyo is working great. in eclair it may help to try with debugging on then you can mount from the notification bar.
maskvp said:
Rooted phone and installed Titanium Backup and Clockwork Recovery. In my excitement I deleted all the ATT bloatware before backing them up and the ROM. Oh well... Too bad.
Click to expand...
Click to collapse
I did that also...
maskvp said:
Now I just feel great about my phone. Needs some customization but no hurry. Only thing was that TB prompted me to go to settings/applications/ and tick "unknown sources". Doesn't exist.
Click to expand...
Click to collapse
To enable side loading(unknown sources). I used method 5 from this post.
http://forum.xda-developers.com/showthread.php?t=738376
and here is a link to my comments on the method later in the thread regarding some punctuation corrections.
This method uses adb from the SDK to pull the settings.db file off and edit it using sqlite3 before pushing it back on.
I believe you can edit the file directly on your phone once you have root and install a terminal app from the marketplace.
The above forum post is also in the wiki you referenced previously. basically you want to look for methods to "enable side loading"
-p
I'm using Ubuntu and have had no problems. Rooted and removed market restrictions without a hitch.
In progress upgrading to 10.10 64bit. Will see, but right now my machine sees my phone but it won't mount. Though I haven't tried to force it.
maskvp said:
In progress upgrading to 10.10 64bit. Will see, but right now my machine sees my phone but it won't mount. Though I haven't tried to force it.
Click to expand...
Click to collapse
On the phone I leave my usb settings set to ask on connection. And then chose 'mass storage' when it asks. It then mounts /sdcard as an external drive. (make sure you haven't left usb debuging on)
pietro_spina said:
On the phone I leave my usb settings set to ask on connection. And then chose 'mass storage' when it asks. It then mounts /sdcard as an external drive. (make sure you haven't left usb debuging on)
Click to expand...
Click to collapse
Oh I've tried it all-wichaways! That hasn't worked either. The card(s) are seen but no longer mount like they used to. When I choose media player I get this message on the phone: PC connection only available in idle screen. Close all running applications. I think something may be corrupted on the phone.
Before I start flashing anything I'm going to give 10.10 a go. Ubuntu specifies that 10.10 plays nice with Android. Unfortunately, I'm having trouble with my startup disks and have wasted three of them on three different downloads. Won't fully boot. Unfortunately, I've had this experience before with other releases, and it almost always was something being wrong with the .iso that was downloaded. Even tried a usb startup and same experience.
Woes. PITA!
maskvp said:
I've had this experience before with other releases, and it almost always was something being wrong with the .iso that was downloaded. Even tried a usb startup and same experience.
Woes. PITA!
Click to expand...
Click to collapse
Make sure you burn your disks at a slow speed. Like 4x. Also try downloading over a stable wired connection. Use the md5 tool to check your download and your burn. If you can figure out when it is getting corrupt you have a fighting chance.
Reporting back. Finally got 10.10 to boot from a usb flashdrive by disabling the BootParameters. I guess 10.10 is so cutting edge my 2.5 yo toshiba can't boot it easily.
Reinstalled 10.04 without a hitch and since I didn't format my /home still kept everything. But I tried connecting by usb before any updates. No worky. And not after the 256M of updates either.
It's the phone I'm sure. Not really keen on flashing the ROM yet just to fix this. Recollection is that Samsung didn't put a good effort into this part of the phone. But I think again..
Why not eschew the usb for file transfers? I've got Bluetooth and wifi right here. Who needs clunky old usb? Adhoc network?
Ideas? Wifi would be easiest since my laptop doesn't have Bluetooth.
maskvp said:
Ideas? Wifi would be easiest since my laptop doesn't have Bluetooth.
Click to expand...
Click to collapse
I think I mentioned in an earlier post that I use an app called ES File Explorer (free in the market) to navagate to a shared folder on my desktop.
My (samba) shared folder has no restrictions and works well. Only issue is I have to fix ownership and permissions on things copied over to the computer from the phone. If you choose to password protect yours let me know how that works out for you.
pietro_spina said:
I think I mentioned in an earlier post that I use an app called ES File Explorer (free in the market) to navagate to a shared folder on my desktop.
My (samba) shared folder has no restrictions and works well. Only issue is I have to fix ownership and permissions on things copied over to the computer from the phone. If you choose to password protect yours let me know how that works out for you.
Click to expand...
Click to collapse
OK thanks. I'm going to investigate this. I take it ESFE works over the 3g connection as long as the host (my laptop) is connected to the internet?
maskvp said:
OK thanks. I'm going to investigate this. I take it ESFE works over the 3g connection as long as the host (my laptop) is connected to the internet?
Click to expand...
Click to collapse
It supports FTP for sure. I'm no security expert but I doubt its a good idea to share a samba share over the internet.
If you want remote access to you desktop there are secure methods for that. The method I would choose would depend on my desire/need for a remote connection.
If I just want to access my shared folder I would probably set up a VPN connection and then use ES FileExplorer.
To fully control the computer, use VNC or other "remote desktop" application.
Been reading up on Samba. It is the linux way lol. Also, I went and got a Bluetooth micro-adapter. Installed drivers from the repository.
Transferred some pics and music back and forth. All GUI based. Worked first time. I'm still this side of the learning curve but my base needs are met.
The Bluetooth works great but I'd like to learn a bit more about the wifi. Seems to me one should be able to move files with a VPN via the wireless adapters and no router. I just lack the knowledge and skill to do it.
But thanks for reminding me about the ES FileExplorer! As far as the permissions in Ubuntu for the shared folder I just checked the box under right-click- sharing options allow others to create and delete files from this folder. I think that works.
I stumbled upon the following thread over in the EVO forum about enabling ad-hoc support for both 0.5.x and 0.6.x wpa_supplicant versions. Following the instructions there, but using a terminal emulator on the xoom I entered:
adb shell wpa_supplicant -v
and it returned v0.6.10 on my (wifi only) xoom.
Now, the problem i'm running into is that the files provided are to be flashed in a recovery--and since the xoom doesn't have one yet, i instead unziped the update, extracted the file, and used root explorer to mount system/bin and replace the "wpa_supplicant". I did a chmod to change the permissions to 775, then flipped my wifi back on to see if it worked....
The result was wifi turned on, but just scanned indefinitely and didn't pick anything up (not even the access points ). Luckily, i made a backup of the original "wpa_supplicant" and restored it using root explorer and fixing permissions as described above. That at least got my wifi up and going again
My question is, does anyone know how to edit the honeycomb file to work with ad-hoc? I'll attach a link below if anyone wants the original to play around with.
I guess it is worth noting that if someone could get this going, i'd be willing to throw a few bucks their way. I'm just stumped, but it seems like it is so close i can almost taste it!
Thanks for your help!
-amruthwo
Stock wpa_supplicant file from Xoom
(lives in system/bin)
amruthwo said:
I stumbled upon the following thread over in the EVO forum about enabling ad-hoc support for both 0.5.x and 0.6.x wpa_supplicant versions. Following the instructions there, but using a terminal emulator on the xoom I entered:
adb shell wpa_supplicant -v
and it returned v0.6.10 on my (wifi only) xoom.
Now, the problem i'm running into is that the files provided are to be flashed in a recovery--and since the xoom doesn't have one yet, i instead unziped the update, extracted the file, and used root explorer to mount system/bin and replace the "wpa_supplicant". I did a chmod to change the permissions to 775, then flipped my wifi back on to see if it worked....
The result was wifi turned on, but just scanned indefinitely and didn't pick anything up (not even the access points ). Luckily, i made a backup of the original "wpa_supplicant" and restored it using root explorer and fixing permissions as described above. That at least got my wifi up and going again
My question is, does anyone know how to edit the honeycomb file to work with ad-hoc? I'll attach a link below if anyone wants the original to play around with.
I guess it is worth noting that if someone could get this going, i'd be willing to throw a few bucks their way. I'm just stumped, but it seems like it is so close i can almost taste it!
Thanks for your help!
-amruthwo
Stock wpa_supplicant file from Xoom
(lives in system/bin)
Click to expand...
Click to collapse
ooooh You are close. Imma gonna play with this over the weekend. I want this.
next question...
Ok, i'm drawing a blank here--what can you use to actually view and edit the wpa_supplicant file? I've kind of tried with notepad, but it seems futile with how many of the characters fail to render, basically making my attempts to understand the subtle changes impossible.
Can anyone shed some light on a good program for win/linux that might work better?
amruthwo said:
Ok, i'm drawing a blank here--what can you use to actually view and edit the wpa_supplicant file? I've kind of tried with notepad, but it seems futile with how many of the characters fail to render, basically making my attempts to understand the subtle changes impossible.
Can anyone shed some light on a good program for win/linux that might work better?
Click to expand...
Click to collapse
we cant edit it directly with notepad, we need the source code of HC then add the adhoc code then compile it..
one thing that curious for me is the wpa_supplicant version is the same as in froyo or ginger android, but we can't just put that already adhoc enable compiled wpa_supplicant file to our HC..it will make our wifi can't see any wifi network..
hmm perhaps there is some other file involved..lets dig it..
exactly, i've been rubbing my chin for about a week on this one. I don't see why the froyo/ginger v0.6.10 file doesn't work...
maybe there is another file involved though, i'm going to go digging in the system folder to see if anything looks related i guess.
hopefully source is released soon, it would make this a little easier...
Pretty sure wpa_supplicant is a GPL project so you shouldn't need to wait for HC source for that.
What errors are you seeing in the logcat after replacing it?
i actually didn't record the log, let me do it again and i'll see what the log says. I'll report back.
log file
here is a bit of the log when trying to connect to wifi...
basically, it says wpa supplicant unable to initiate ap scan
Being Android noob, and since I'm trying to get this xoom to see ad-hoc networks for work (this is really important.. spent 600, expecting it to connect it to adhoc.. dang it.), would it be worthwhile to port wpa_supplicant from droid x?
Droid x reports 0.6.10. Unlike EVO, since they are both motorola products, they have something in common??
Or maybe, xoom uses a different driver? I see that droid x has tiwlan0 as its wireless, whereas xoom simply says wlan0.
Reading from here: htt p:/ /sz ym . ne t/2 01 0/1 2/a dh oc - w i fi - in - an d ro i d /
(sorry, being a new user, it doesn't let me post a link... )
someone says that wpa_supplicant needs to be compiled with the correct driver.
Does anyone know how to do this? Or am I just wrong? lol
from what i understand, the wpa_supplicant is part of the gpl, not unique to any phone manufacture. I'm no expert on the subject either though. I have no idea what is different in the xoom, but i have used the v0.6.10 which matches that of the xoom, but no dice. If you want to extract one from the droid x and edit it (assuming you know how) then it is definitely worth a shot!
let us know what you find
lesjaw said:
we cant edit it directly with notepad, we need the source code of HC then add the adhoc code then compile it..
one thing that curious for me is the wpa_supplicant version is the same as in froyo or ginger android, but we can't just put that already adhoc enable compiled wpa_supplicant file to our HC..it will make our wifi can't see any wifi network..
hmm perhaps there is some other file involved..lets dig it..
Click to expand...
Click to collapse
You're right about not being able to edit in notepad, but I opened it in notepad++ to at least view it. I don't have visual studio installed on my laptop at the moment or else I would try with that.
At any rate searching through the file in notepad++ I found two instances where it refers to adhoc that looked interesting.
One line says: WPA: Invalid mode %d (not IBSS/ad-hoc) for WPA-None
and the other line says: skip - IBSS (adhoc) network
That second line looks to tell it to skip adhoc networks when scanning.
Pretty sure wpa_supplicant is a GPL project so you shouldn't need to wait for HC source for that.
Click to expand...
Click to collapse
It is. It even says so within the file.
EDIT: I was able to open it in Visual Studio and it looked much better. I'll see if I can figure something out with what to edit in the file.
Solution found!
hey, someone finally got the binary figured out!
check out the thread here
and, if you're away from your computer, or just hate using adb, my buddy mr_wrong_0 has root explorer instructions here!
Hi All,
My first post here, I am not sure I am posting in the correct section.
I need to update the wpa_supplicant conf of my Andorid 9 phone (an Asus Zenfore Max Pro M1) in order to allow it to connect to a MFP (managed frame protected) network.
I managed to configure my home linux machines to do so but with my Android phone it is a disaster.
From what I know the device needs to be rooted...for this I am just proceding with the proper steps but...I am not sure that the wpa_supplicant.conf to be modified is the one settled in the /etc directory as I ve read that on Android the conf file for the wpa_supplicant service may be different.
Is there any way to understand which configuration files a binary executable is bound with?
What I am trying to do is to set the pmf option in the correct wpa_supplicant.conf file in orded to let the device connect to a MFP network.
Any help will be so much appreciated.
Thanks!
Well...it is nice to discover that Android 9 is not using wpa_supplicant any more and that it will be a nightmare to crosscompile it and configure it as a daemon
This is my last android shxt phone.
A quick search reveals that WifiConfigStore.xml should be the file you want. requirePMF might help, from source for WifiConfiguration.java. I can't find any more documentation than that (opening source files kills my phone browser) but that should be a good start.
Thanks Efreak2004 but have tried that way as well.
Have modified the WifiConfigStore.xml by setting to true the requirePMF option but it did nothing.
My suspect is that the java wrapping useless stuff is not doing anything more than trying to "steer/drive" the native processes preposed to do the job. It has always be this way since the invention of java which was wrapping lib C in any aspect.
I am almost convinced that without the wap_supplicant binary/daemon there is no way to let the java fancy wifi manager do the job by its own.
Have WiFi issues in my house. Want to hookup an ethernet cord to my phone. Purchased an Ethernet (RJ45) to USB-C dongle on Amazon. Doesn't work. Watched several videos online to make sure I wasn't missing anything. Dongle simply doesn't work. Returned. Looking at new dongles now.
Found one that says it should work if your vendor included the driver "ASIX AX88772A" in the Android OS. Found another that says the dongle uses the "RTL8153B Chipset". I have two different model phones here and am wondering how I can verify before purchase if my phone supports a particular chipset or contains a certain driver. Tried searching online but haven't found anything yet. Feeling stuck.
goto Device Manager then view>show hidden devices from there just find the hardware with warning logo beside there name...
ineedroot69 said:
goto Device Manager then view>show hidden devices
Click to expand...
Click to collapse
This sounds like you are describing an action I could take in Windows. But I am asking for instructions related to the Android OS. Maybe I have misunderstood something?
Mulsiphix said:
Have WiFi issues in my house. Want to hookup an ethernet cord to my phone. Purchased an Ethernet (RJ45) to USB-C dongle on Amazon. Doesn't work. Watched several videos online to make sure I wasn't missing anything. Dongle simply doesn't work. Returned. Looking at new dongles now.
Found one that says it should work if your vendor included the driver "ASIX AX88772A" in the Android OS. Found another that says the dongle uses the "RTL8153B Chipset". I have two different model phones here and am wondering how I can verify before purchase if my phone supports a particular chipset or contains a certain driver. Tried searching online but haven't found anything yet. Feeling stuck.
Click to expand...
Click to collapse
To get to know all the drivers, you need to go through the /sys directory.
jwoegerbauer said:
To get to know all the drivers, you need to go through the /sys directory.
Click to expand...
Click to collapse
I tried to use Solid Explorer to access the /sys directory.
I went to Settings -> Storage -> System
I plugged my phone into my PC and accessed it using my file browser. It did not show me root, but /storage/emulated/0 instead, with no way to move higher in the folder hierarchy.
I setup an FTP Server app and accessed my phone using Filezilla from my PC. I configured the FTP Server's "home" directory to Root. All it showed was an empty folder. None of the system folders were listed there. When I configured it to /storage/emulated/0 I was unable to move higher in the folder hierarchy.
In all cases I am unable to view the contents of the /sys directory. My phone is not rooted. Is this something I can check without having a rooted phone?
@Mulsiphix
You might use ES FileExplorer to access / read the protected directories / files on Android: ES FileExplorer can get turned into ES RootExplorer.
jwoegerbauer said:
@Mulsiphix
You might use ES FileExplorer to access / read the protected directories / files on Android: ES FileExplorer can get turned into ES RootExplorer.
Click to expand...
Click to collapse
I just tried this but none of the files show in the root, even with Show Hidden Files and Folders and Root Explorer options enabled. I'm trying to figure out how to root my phone but I am having trouble finding any evidence the Kyocera DuraForce Pro 2 can even be rooted. I hope this super expensive phone wasn't a poor choice =(
Mulsiphix said:
I just tried this but none of the files show in the root, even with Show Hidden Files and Folders and Root Explorer options enabled. I'm trying to figure out how to root my phone but I am having trouble finding any evidence the Kyocera DuraForce Pro 2 can even be rooted. I hope this super expensive phone wasn't a poor choice =(
Click to expand...
Click to collapse
I believe it might have been a poor choice friend. For rooting purposes that is. The phone is encrypted from the factory and uses several layers of security to impede attempts to even capture useful logs. It's a military grade phone with I believe 4 or 5 layers of security between the user and the kernel. I myself have been looking for a way to root this to exploit the NFC feature to read and spoof my work badge for ****s and giggles.... not no avail. BUT..... I beat the living **** out of the phone and being I own the Verizon variant with Sapphire Glass, there is not one single blemish on my screen and works with my NFC FIDO2 U2F key for almost all auths where I choose not to op for bio. If you do run across something, DM me~!
Alucard0rJok3r said:
If you do run across something, DM me~!
Click to expand...
Click to collapse
Thank you for the feedback Alucard0rJok3r. If I find something, I will be sure to let you know.