Hi,
Over the past few days I've tried getting my USB Ethernet cable to work with my Tab 2 10.1 running stock ICS 4.0.4
And now I got it up to the point where my PC and my Tab can ping eachother, but that's about it. Get ready for a long and technical read
Now I know Samsung has neglected to include drivers for commonly used USB to Ethernet cables, so I built my own modules to load into the stock kernel (3.0.8-1060237):
drivers/net/mii.ko - Generic Media Independent Interface device support
drivers/net/usb/usbnet.ko - support for usb network
drivers/net/usb/mcs7830.ko - driver for this specific ethernet cable (moschip 7830 based)
Driver depends on support for USB network, USB network depends on support for media independent interface.
So loading these into the kernel using insmod works. After I plug in the cable the kernel tells me:
Code:
[ 3754.987335] MOSCHIP usb-ethernet driver 1-1:1.0: eth0: register 'MOSCHIP usb-ethernet driver' at usb-musb-hdrc-1, MOSCHIP 7830/7832/7730 usb-NET adapter, 00:60:6e:42:32:8f
And even netcfg agrees eth0 exists:
Code:
[email protected]:/ # netcfg
lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
ifb0 DOWN 0.0.0.0/0 0x00000082 26:d8:ae:9d:18:30
ifb1 DOWN 0.0.0.0/0 0x00000082 3e:2c:67:48:bd:92
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
eth0 DOWN 0.0.0.0/0 0x00001002 00:60:6e:42:32:8f
wlan0 UP 130.161.censored/26 0x00001043 1c:66:aa:50:39:ee
[email protected]:/ #
So for testing I put the device on a simple switch with just my PC.
I gave my PC 192.168.1.253 and the tablet 192.168.1.200 (both netmask 255.255.255.0).
Code:
[email protected]:/ # ifconfig eth0 192.168.1.200 netmask 255.255.255.0
And there was much rejoicing:
Code:
Windows:
Reply from 192.168.1.200: bytes=32 time<1ms TTL=64
Android:
64 bytes from 192.168.1.253: seq=32 ttl=128 time=0.733 ms
Now here is the problem: Half the apps trip over this new eth0 network interface.
For instance:
"kWS - android web server" works great, immediately recognizes eth0 and uses it without any problems.
Android Browser crashes the network driver.
SSHDroid starts up thinking it is an ipv6 interface and crashes the network driver on any incoming connections.
Also when I turn off WiFi (regardless if it is connected to a network or not), eth0 is killed too.
Couple of questions:
What am I missing to make Android treat this as a good, normal network interface?
How can I make the modules load when the tablet boots?
How can set the IP adres so I don't have to use ifconfig eth0 192...etc every time I connect the device?
How can I add the eth0 to the settings GUI of Android?
Can installing a different kernel or something like CyanogenMod fix the problem alltogether?
Many thanks in advance for any answers!
If anyone is interested in the modules I compiled please reply, but note they only work on rooted tablets that have stock ICS kernel version 3.0.8-1060237 because of what Linux calls "version magic".
Kind Regards,
Android has Incomplete Eth0 Support...
baggush said:
Hi,
Couple of questions:
What am I missing to make Android treat this as a good, normal network interface?
How can I make the modules load when the tablet boots?
How can set the IP adres so I don't have to use ifconfig eth0 192...etc every time I connect the device?
How can I add the eth0 to the settings GUI of Android?
Can installing a different kernel or something like CyanogenMod fix the problem alltogether?
Many thanks in advance for any answers!
Click to expand...
Click to collapse
Well, he first thing to know is that Android has incomplete Eth0 support!
As you've seen, it's implemented and correct at the Linux level. Which means programs that are written in C++ and either work at the native linux level or bypass the Android framework will work.
However, the Java implementation is busted. It's incomplete.
I'd highly recommend Ben Zores presentation, "Dive Into Android Networking: Adding Ethernet Connectivity" if you want to understand the issues.
(You'll have to google it, I can't post links yet!)
Basically all the Android API gets you is the ability to see that Eth0 exists. You can't talk to it, set it, get notifications on it, etc. because the Service Manager and the Connection Manager framework components are incomplete.
Some implementations, like Android-IA and Cynogen and Linaro have been patched to work, some better than others.
I ran into this the hard way, because I'm implementing a machine control system using Android as a UI and Control Computer. It's a fixed app, not a mobile/tablet thing. And I'm linking to a WAGO Modbus-based fieldbus system for digital and analog I/O and motion control.
Trust me, it's a real headache. I've gotten around it, but there's no official news or support yet.
Regards,
David Schofield, Hotspot Office LLC, Pittsburgh, PA
Galaxy tab 2 eth0 needed
I need to connect an USB to Ethernet to my Galaxy tab 2 7.0 (GT-P3100) or Galaxy tab 3 7.0 (GT-P3200), is there is a way to add the driver without rebuild the rom (like a patch or update) or if there is a custom ROM that supports Ethernet ? Please help me doing this
Ethernet support for Galaxy tab 2.7.0
MJBLACKEND said:
I need to connect an USB to Ethernet to my Galaxy tab 2 7.0 (GT-P3100) or Galaxy tab 3 7.0 (GT-P3200), is there is a way to add the driver without rebuild the rom (like a patch or update) or if there is a custom ROM that supports Ethernet ? Please help me doing this
Click to expand...
Click to collapse
How to say this gently... umm-m-m,
No.
Each manufacturer has configured Android to their liking, and apparently Samsung DOESN'T like Ethernet.
.
I'm doing just as you did, using a Radio Shack Belkin USB interface to connect to industrial equipment (Modbus/TCP PLC's and fieldbus I/O systems.) I've evaluated a number of tablets, including all Samsung tablets (and Nexus, Lenovo, Curtis, and many, many others.) If they don't fully support wired Ethernet, you can't back-fill it without rooting and flashing the ROMs.
(I wish Toshiba would unroot my original Thrive, which they've orphaned.)
In the end, I've bought cheap tablets like some Proscan's (at BigLots, $80USD ) and the 7" Zeki TBDG773B (K-Mart, $119USD) and in testing them, discovered they supported wired Ethernet. (Note that exact models are important, because I've found ROM differences between almost identical models that make the difference between success and failure. Polaroid-branded tablets are infamous for this.)
To test, go to Settings, Wireless & Networks -> Ethernet, (or sometimes, More...-> Ethernet) then switch Ethernet ON, and click Advanced Configuration or sometimes, Configure Ethernet Device. (Polaroids usually fail at this point, they never included the rest of the module.)
My Zeki gives the choice of DHCP vs. Static IP, .IP Address, Netmask, DNS Address and Gateway Address. Proscan gives you DNS1 and DNS2.
I have tested over 80 Android tablets now... Many are tested, few are worthy.
Check out my video on Android-->Ethernet connectivity on YouTube, search for Hotspot Office modbus, or watch video JCMkvHkeNzw, as in /watch?v=JCMkvHkeNzw
I've got specifics and talk about models and equipment and demonstrate stepper motor control using a WAGO fieldbus system.
Thanks
Hotspot Office said:
How to say this gently... umm-m-m,
No.
Each manufacturer has configured Android to their liking, and apparently Samsung DOESN'T like Ethernet.
.
I'm doing just as you did, using a Radio Shack Belkin USB interface to connect to industrial equipment (Modbus/TCP PLC's and fieldbus I/O systems.) I've evaluated a number of tablets, including all Samsung tablets (and Nexus, Lenovo, Curtis, and many, many others.) If they don't fully support wired Ethernet, you can't back-fill it without rooting and flashing the ROMs.
(I wish Toshiba would unroot my original Thrive, which they've orphaned.)
In the end, I've bought cheap tablets like some Proscan's (at BigLots, $80USD ) and the 7" Zeki TBDG773B (K-Mart, $119USD) and in testing them, discovered they supported wired Ethernet. (Note that exact models are important, because I've found ROM differences between almost identical models that make the difference between success and failure. Polaroid-branded tablets are infamous for this.)
To test, go to Settings, Wireless & Networks -> Ethernet, (or sometimes, More...-> Ethernet) then switch Ethernet ON, and click Advanced Configuration or sometimes, Configure Ethernet Device. (Polaroids usually fail at this point, they never included the rest of the module.)
My Zeki gives the choice of DHCP vs. Static IP, .IP Address, Netmask, DNS Address and Gateway Address. Proscan gives you DNS1 and DNS2.
I have tested over 80 Android tablets now... Many are tested, few are worthy.
Check out my video on Android-->Ethernet connectivity on YouTube, search for Hotspot Office modbus, or watch video JCMkvHkeNzw, as in /watch?v=JCMkvHkeNzw
I've got specifics and talk about models and equipment and demonstrate stepper motor control using a WAGO fieldbus system.
Click to expand...
Click to collapse
Thank you for your reply. As you mentioned, there is a way by rooting and flashing, so Where can we find a ready ROM which we can flash to enable Ethernet on Galaxy tab 2 [P3113]?
Also, is there a way to recompile the kernel of Galaxy tab 2 with enabling the Ethernet module from my side? if there is can you advise me how?
Thanks and regards,
Flashing the Galaxy...
MJBLACKEND said:
Thank you for your reply. As you mentioned, there is a way by rooting and flashing, so Where can we find a ready ROM which we can flash to enable Ethernet on Galaxy tab 2 [P3113]?
Also, is there a way to recompile the kernel of Galaxy tab 2 with enabling the Ethernet module from my side? if there is can you advise me how?
Thanks and regards,
Click to expand...
Click to collapse
There are sources on the internet, if you google for "reflash galaxy 2 ROM" but I don't know if they support wired ethernet.
You'll find sites like galaxys2root.com, etc. Biftor is apparently a popular ROM, and ODIN is a popular facility.
It's an involved process, but not impossible. Strict attention to the right instructions will win you success!
Good Providence!
-d
Bump!
Dear Forum,
has there been any development on this topic?
@Hotspot Office -- kudos for the link!
Like Hotspot Office, We have to build a machine GUI based on the P5110. My application will be bypassing the incomplete Android eth0 support
so most probable baggush's approach could work for us but we ar running Cyanogenmod 11 and the Dhollmen kernel.
I still have to get my legs about this whole issue. So any hints and thoughts will be greatly appreciated.
Martin
Functional Eth0, check out my project vid on youtube!
Well, I got things straight, but it wasn't easy.
Check out my project vid featuring a WAGO fieldbus controlling a stepper motor via a functional Eth0 on youtube
You can google for "youtube android modbus" or search youtube for video JCMkvHkeNzw
Or you can plug it into the youtube url, as in /watch?v=JCMkvHkeNzw
The actual title is "Android Tablet Modbus/TCP Stepper-Motor/Robot Exerciser"
If you like it, be sure to thumbs-up it, and leave a comment!
david schofield
dub-dub-dub dot hotspot office dot net
I'm running 4.2.2 so maybe this won't apply, but did you have to do anything in terms of the Ethernet UI in Settings? I've installed the drivers and it looks like the tablet is detecting it, but the Ethernet settings never show up
diimentio said:
I'm running 4.2.2 so maybe this won't apply, but did you have to do anything in terms of the Ethernet UI in Settings? I've installed the drivers and it looks like the tablet is detecting it, but the Ethernet settings never show up
Click to expand...
Click to collapse
Are you running a full 4.2.2, or a stripped down version? What's its pedigree?
Hotspot Office said:
Are you running a full 4.2.2, or a stripped down version? What's its pedigree?
Click to expand...
Click to collapse
I'm not sure, how can you tell?
diimentio said:
I'm not sure, how can you tell?
Click to expand...
Click to collapse
What kind of device is it? Or try Settings, About?
The thing is, if it isn't under "Settings->Wireless and Networks" or whatever, then you don't have it.
-d
Hotspot Office said:
What kind of device is it? Or try Settings, About?
The thing is, if it isn't under "Settings->Wireless and Networks" or whatever, then you don't have it.
-d
Click to expand...
Click to collapse
Well it definitely says 4.2.2 under Settings, About. I have a Samsung Galaxy Tab 2 GT-P5113 model. I don't know what a "stripped down" version is.
I don't have it under Wireless and Networks but in this video (https://www.youtube.com/watch?v=J-RQwQTjraM) the Ethernet option pops up when it detects a valid Ethernet connection. Obviously it's not the same model but I'm wondering whether I need a UI patch or if it should just work out of the box assuming I have all the correct drivers installed.
diimentio said:
Well it definitely says 4.2.2 under Settings, About. I have a Samsung Galaxy Tab 2 GT-P5113 model. I don't know what a "stripped down" version is.
I don't have it under Wireless and Networks but in this video (https://www.youtube.com/watch?v=J-RQwQTjraM) the Ethernet option pops up when it detects a valid Ethernet connection. Obviously it's not the same model but I'm wondering whether I need a UI patch or if it should just work out of the box assuming I have all the correct drivers installed.
Click to expand...
Click to collapse
In my experience, I've found you'd need the *EXACT* same model. I've checked probably a hundred tablets, and found that the specific model and software version, matters. That's why in my video I detail the exact model number. You need to realize that an Android version, say 4.2.2 isn't the same the whole world over. Like Windows XP Embedded, it's a kit of parts. I can burn a version of 4.2.2 with Ethernet support, and I can burn a version of 4.2.2 WITHOUT Ethernet support apps at the Android level. As the developer, I pick and choose what features and applications I include, and which I leave out--which I customize, and which I leave alone.
Sorry, unless you root your device with a version of 4.2.2. that supports the wired Ethernet applications in the settings, you're at the mercy of the Samsung folks.
Related
Hello,
I have followed the guides for [DEV] Native Ubuntu and [HowTo] Native Ubuntu as well as searching google and these forums to get ubuntu running on the Asus Eee Pad Transformer. It works brilliantly except for one issue. All of the suggestions I have seen about getting wireless working don't seem to work for me. I feel I'm missing something simple and just need to be pointed in the correct direction. I have a UK version of the Eee Pad.
1. I have made the /etc/wpa_supplicant/wpa_supplicant.conf file as suggested by the forums.
2. sudo ifconfig eth0 down gives "eth0: ERROR while getting interface flags: No such device"
3. /etc/init.d/start-networking doesn't seem to exist on my system.
4. ifconfig only lists lo and usb0. usb0 has an ip address oddly enough.
The list of possible network devices ubuntu says I have are as follows:lo, dummy0, usb0, tunl0, sit0, and ip6tnl0. I have followed various suggestions about bringing down the usb0 interface before working with eth0, but it didn't seem to help.
It makes me think that the wireless drivers are missing in my rootfs.ext2 file, but I'd rather not try to download it again to see due to bandwidth limits. I would appreciate any thoughts or places to go that would help get this working. Thank you for your help.
I've been trying to work through the wireless problem, and I've found a little more info:
Code:
dmesg |grep bcm
device: 'bcm4329_wlan.1': device_add
device: 'bcm4329_rfkill': device_add
bcm4329_rfkill_probe : can't find reset gpio
I think this indicates a problem loading the driver, but I am purely speculating here. I've checked and the chipset's firmware is loaded in /lib/firmware/brcm so the driver is present.
I'll keep playing around to see if I can get it working. Any suggestions that could help point me in the right direction would be appreciated.
Hi all,
I spent a couple of days Googling around, trying to get Bluetooth DUN working on Cyanogenmod 7.1.0 on my Viewsonic GTablet.
After some hacking around with the source, I got it working. I can connect my GTablet to the internet through my Blackberry Torch on Rogers (in Ontario, Canada).
I've already posted my notes to the CM forums, but apparently since I'm a noob here I can't post the link to it, so here's my notes (direct copied from the CM forums):
Dial-up networking requires the chat binary, which is included in the standard Linux ppp package. For some reason, this binary was omitted from the Android ppp package, so I downloaded the Android 2.3.7 source, copied the chat source in to the Android ppp package and built it from scratch. The instructions for this were found at afewe DOT wordpress DOT com/android-arm-development/use-point-to-point-protocol-ppp-in-android/
Once the chat binary is installed in the proper location on the Android device (/system/bin/chat) it's just a matter of writing a pppd config and chatscript for your given provider. These configs can be found in the berry4all package at berry4all DOT com.
I copied the 'rogers' file from that package and put it in /etc/ppp/peers/rogers, then the rogers-chat file and put it in /etc/ppp/chatscripts/rogers-chat.
I modified the /etc/ppp/peers/rogers so that the last line, which calls the chat binary, reflected the proper locations of the binary and the chat script.
Finally, I removed the 'novj' option from the pppd config. Once the config was all up and ready to go, I went to the terminal and did:
$ su
# rfcomm bind /dev/rfcomm0 <BT MAC> <channel>
# pppd call rogers
And voila! A stable, bluetooth dial-up network connection through my phone.
I just wanted to throw out my notes first to make people aware that its possible and easy. If there's enough interest, I'll write a more detailed and specific step-by-step howto on getting it set up.
Hi,
I see that CM 7.1 includes "bluetooth tether" support now but it's not clear to me what this actually is. Does CM 7.1 include the DUN bluetooth profile? It sounds like you're using reverse tethering, i.e. you are using a Blackberry's data connection so you're using the DUN profile on the Blackberry and are using the CM device as a client?
I have a stock Desire S and am looking for DUN support so I can use the internet access in my car through the Desire's 3G connection. The car supports only DUN and PDANet doesn't work for some reason.
Thanks,
Tim
Looks like you're out of luck.... same story for my Benz with Comand Online Navcom system.
If you drive an MB like me, you'll have to wait for an update later this year (from MB that is)... or buy a BlackBerry.
Sent from my GT-P7500 using Tapatalk
Is it confirmed that mercedes benz are providing this update?
Sent from my GT-I9100 using Tapatalk
I very much doubt it (I'm also trying to get it working with Comand Online).
http://telematicsnews.info/2011/08/...connectivity-options-to-comand-online_ag2223/
Not great news.
tj80 said:
I very much doubt it (I'm also trying to get it working with Comand Online).
Click to expand...
Click to collapse
From the press release:
"An option for customers having phones without DUN support is the Mercedes-Benz “Bluetooth (SAP) telephone module - V4″, available early 2012. The new version (V4) offers UMTS capability, allowing fast data connection using customer SIM card or accessing SIM information from SAP (SIM Access Profile) enabled mobile phone."
and:
"... Furthermore Mercedes-Benz is in close talks with leading Android phone vendors to enable the DUN feature in their phones by default."
(I have Android 2.3 and Windows Phone 7.5 devices)
Yes, so we can pay £400 for a SAP module or buy a new phone if anyone actually launches an Android handset with DUN - remembering that Google appear to have zero interest so it will be manufacturer specific. Oh yes, I nearly forgot - Android doesn't have SAP profile support either!
I'd say the chances of Mercedes updating existing systems to work with phones which don't support DUN is virtually zero. Hardly ideal on a system which cost £2000...
Cheers,
Tim
I agree. It was a huge mistake of MB to go with this dead BT DUN protocol!
I thought Android phones do support SAP, isn't that why the car can dial a contact?
agupta80 said:
I thought Android phones do support SAP, isn't that why the car can dial a contact?
Click to expand...
Click to collapse
'fraid not, that uses PBAP (phone book access protocol).
I am starting this thread because i found that after all this long time of waiting an improvement from Android guys from Google regarding a complete UI for connecting to the miscellaneous WiFi configurations nothing comes out.
I consider my thread android development related, but if the mods want to move it please do it.
I am not a developer but I'm a user which wants all the cake not just a bite.
I am referring to special type of WiFi connections which wpa_supplicant is capable like:
"
EAP-TLS
EAP-PEAP/MSCHAPv2 (both PEAPv0 and PEAPv1)
EAP-PEAP/TLS (both PEAPv0 and PEAPv1)
EAP-PEAP/GTC (both PEAPv0 and PEAPv1)
EAP-PEAP/OTP (both PEAPv0 and PEAPv1)
EAP-PEAP/MD5-Challenge (both PEAPv0 and PEAPv1)
EAP-TTLS/EAP-MD5-Challenge
EAP-TTLS/EAP-GTC
EAP-TTLS/EAP-OTP
EAP-TTLS/EAP-MSCHAPv2
EAP-TTLS/EAP-TLS
EAP-TTLS/MSCHAPv2
EAP-TTLS/MSCHAP
EAP-TTLS/PAP
EAP-TTLS/CHAP
EAP-SIM
EAP-AKA
EAP-AKA'
EAP-PSK
EAP-FAST
EAP-PAX
EAP-SAKE
EAP-IKEv2
EAP-GPSK
LEAP (note: requires special support from the driver)"
This is copied from here http://hostap.epitest.fi/wpa_supplicant/
Seems that we have the gun and the bullets but we don't have the trigger.
This idea come to me when i was struggling connecting to my work WiFi and never succeeded, phones like Symbian or Windows based laughed into my phone's face (and i think that is not correct, considering it frustrating).
My proposal to all the devs from XDA is to build a new app and wpa_supplicant with all drivers and stuff which will be able to help us connecting very easy to all kind of WiFi methods.
PS: My work network configuration for windows is like this:
SSID, CKIP LEAP, username, domain, password.
Hidden WiFi: http://code.google.com/p/android/issues/detail?id=1041
LEAP WiFi: http://code.google.com/p/android/issues/detail?id=1871 ; http://code.google.com/p/android/issues/detail?id=1386
Ad-Hoc WiFi: http://code.google.com/p/android/issues/detail?id=82
Devices that are capable to connect on my work WiFi network:
Symbian V3 (Nokia N8)
Windows Mobile 6.5 (HTC Diamond)
Devices that are not capable to connect on my work WiFi network:
Android (HTC Desire HD and Samsung Galaxy S I)
iOS 4 (iPhone 3Gs)
iOS 5 (iPod)
Blackbery (Curve 8900)
============================================================
Update: 29/11/2011
After a 2-3 weeks of Google-ing I think that i found the gap with LEAP:
How you can see above LEAP - requires special support from the driver and i found a Linux driver which says like this:
2086 // CCX 1 spec v1.13, A01.1 CKIP Negotiation (page23):
2087 // "A Cisco access point advertises support for CKIP in beacon and probe response packets,
2088 // by adding an Aironet element and setting one or both of the CKIP negotiation bits."
2089 if( (info_element->data[IE_CISCO_FLAG_POSITION]&SUPPORT_CKIP_MIC) ||
2090 (info_element->data[IE_CISCO_FLAG_POSITION]&SUPPORT_CKIP_PK) )
Source:http://lxr.free-electrons.com/source/drivers/staging/rtl8192e/ieee80211/ieee80211_rx.c
My work WiFi require CKIP Encryption so this is root cause for me to not be able to connect to LEAP.
Currently broadcom support: 802.1x; WEP, WEP2, WPA, WPA2 (Personal) TKIP and AES hardware acceleration 802.11i. When "broadcom" will release compatible drivers, we will be able to connect. Until then, all users that are in my situation will better get an alternative.
http://pdf.eccn.com/pdfs/Datasheets/Broadcom/BCM4329.pdf
http://os1a.cs.columbia.edu/lxr/source/drivers/net/wireless/bcm4329/wl_iw.c
So next remaining thing will be a "Complete UI" release for android which offers all type of connections.
================================================================================================
Update: 07/12/2011
In my craziness to find a solution to my problem regarding connection to work corporate WiFi, I found the missing link (in my opinion) between android and Linux capability to access CKIP encrypted networks: http://o2droid.phj.hu/trac/browser/kern_oII/drivers/staging/rt2860/sta/assoc.c . It is about a special characteristic that allow connections to Aironet access points with CCX (CISCO Compatible Extensions).
================================================================================================
Update: 14/03/2012
I need a port from Dell Streak to HTC DHD
I searched Google again and i found this:
http://forum.xda-developers.com/show...62&postcount=1 here is a file listed "system/etc/wlan/sdio-g-cdc-reclaim-idsup-wme-pktfilter-keepalive-aoe-toe-ccx-wapi.bin" and with a F3 in Total Commander contain this:
"NONE WEP1 TKIP WEP128 AES_CCM AES_OCB_MSDU AES_OCB_MPDU CKIP CKIP_MMH WEP_MMH" and
"ccx_auth_mode"
The file is in the Streaksmi.zip which is miui for dell streak that has bcm4325 chipset.
================================================================================================
Update: 10/07/2013
Working Solution Update: 10/07/2013
Flash [ROM][UNOFFICIAL] CyanogenMod 10.1 Nightlies / M-Series [RC5] and say many thanks to Mustaavalkosta !!! - Tested working build: cm-10.1-20130709-UNOFFICIAL-ace.zip
I too have issues with wifi sometimes, but I found using miui and connecting, inputting the password and then using the individual settings to input a manual IP and all that seems to work.
Sorry if I've misunderstood
Sent from my HTC Desire HD using Tapatalk
Difference between OS's
Joey93 said:
I too have issues with wifi sometimes, but I found using miui and connecting, inputting the password and then using the individual settings to input a manual IP and all that seems to work.
Sorry if I've misunderstood
Sent from my HTC Desire HD using Tapatalk
Click to expand...
Click to collapse
So what is different between MIUI and a usual Android system?
No idea apart from that it keeps the individual settings separately so you don't have to input manually every time you need to change, but it seems to be the only thing that works for all the networks I use.
Sent from my HTC Desire HD using Tapatalk
Compatibility with Ad-Hoc
Joey93 said:
No idea apart from that it keeps the individual settings separately so you don't have to input manually every time you need to change, but it seems to be the only thing that works for all the networks I use.
Sent from my HTC Desire HD using Tapatalk
Click to expand...
Click to collapse
Is it capable to connect with Ad-Hoc type of networks too?
And the answer is "Yes", wpa_supplicant from MIUI is capable to connect to Ad-Hoc networks.
Not sure what your problem connecting might be. At uni, we have EAP-PEAP/MSCHAPv2, and I can connect fine, and connect any android phones that come in fine aswell. We use a program called xpressconnect, but can do it manually too.
whiperhack said:
Is it capable to connect with Ad-Hoc type of networks too?
And the answer is "Yes", wpa_supplicant from MIUI is capable to connect to Ad-Hoc networks.
Click to expand...
Click to collapse
I have an application on my laptop that makes a network from it (like a router) which I've always assumed used ad-hoc and it's always connected fine to that so yeah I assume so =)
Old Leedroid ROMs used to work too if you wanted sense, but they were back in August-ish time
Already tried manual config
rorydaredkign said:
Not sure what your problem connecting might be. At uni, we have EAP-PEAP/MSCHAPv2, and I can connect fine, and connect any android phones that come in fine aswell. We use a program called xpressconnect, but can do it manually too.
Click to expand...
Click to collapse
Before i start this thread i tried several combination of configurations, I buyed even Advanced Leap WiFi from market and nothing. This problem is not from configuration because, like I said windows mobile and symbian is piece of cake to connect.
My connection is hidden ssid. After I put my credentials configured with leap, another network with same name but with WEP security appears, saying connecting...disconnected.
Update
I just tried MIUI and conclusions are:
1) Ad-Hoc is connectible (but stock android with a modified(patched) wpa_supplicant is capable to connect to Ad-Hoc too).
2) LEAP is still doing Connecting....Disconnected.
3) MIUI has a file named "/system/bin/wpa_cli" which stock didn't have it.
whiperhack said:
I just tried MIUI and conclusions are:
1) Ad-Hoc is connectible (but stock android with a modified(patched) wpa_supplicant is capable to connect to Ad-Hoc too).
2) LEAP is still doing Connecting....Disconnected.
3) MIUI has a file named "/system/bin/wpa_cli" which stock didn't have it.
Click to expand...
Click to collapse
For number 2 try manually inputting a static ip, dns, gateway and netmask =)
Must be something which makes the difference
Joey93 said:
For number 2 try manually inputting a static ip, dns, gateway and netmask =)
Click to expand...
Click to collapse
Thanks for the tip, I will try tomorrow. But what is the catch? What makes WM and Symbian better than Android when is about connecting to a LEAP network?
So you'd like other people to build an app for you?
Learn how to code!
All android comunity will thank to the courageous developer who will create the tweak
ivolol said:
So you'd like other people to build an app for you?
Learn how to code!
Click to expand...
Click to collapse
Why do you say "YOU"? Is not just me, is the whole android community that has lack of what i said in the thread. The work that will be done by a skilled developer from here will be used in the future by all androiders.
All the info and opinions that will be wrote in here will help the "courageous developer" to build the Complete WiFi UI.
My experience with the WiFi will help others to connect on similar networks.
In my opinion this is true development: trying to reach the impossible, or not yet possible, or not yet known.
I think is at last 1 developer in here which knows very good the WiFi protocols and can give us a hint.
For us (the ordinary users) is very difficult to start now learn coding in android and network protocols, because will last at least six months of staying in codes to get the idea of coding.
Compiling in android OS
ivolol said:
Learn how to code!
Click to expand...
Click to collapse
I checked your thread and is says nothing about compiling in Android OS. In my opinion this is the root cause of not fully working WiFi connectivity. With a proper .conf file of latest wpa_supplicant i think that the issue will become history.
Logcat and new tests
Hello again,
I've made some new tests and I found ......... nothing.
The thread with steps that i followed is this: http://code.google.com/p/android/issues/detail?id=8804
Hi all,
I make a application android for my customers but my customers want to allow their customers access to tablet with my application "blocked". The final user can't quit my application, he can simply use my application.
Tablet must have ethernet (via usb to lan adapter), the bottom button bar must be hidden.
Can you recommend me a model ?
Thanks a lot,
I have tested the Toshiba folio 100, but with no driver video for the graphic card with andro 3.0.
Andro 3.0 is required for the usb to lan adaptater
I have try too the acer iconia a200, but isn't rootable for the moment,
now I try the samsung galaxy tab
hi Alexandre,
we have the same problem for a new project.
Do you think it's possible do do it without rooting the device ?
Hi,
may be if you wantt stay in dhcp and if you have usb lan driver in your os.
Thanks,
Andrdev said:
hi Alexandre,
we have the same problem for a new project.
Do you think it's possible do do it without rooting the device ?
Click to expand...
Click to collapse
Lenovo thinkpad offers alot of security for the tablet and is integrated into the framework and not a app alone, which makes breaking the security alot harder for regular users even with root enabled.
i think its a question of users/companies wanting security they get Thinkpad tablet for that, which cisco client included for vpn as well.
Hi dexter,
Do you test this tablet?
Do you think it's possible to wake up this tablet automaticaly the morming? by a magic packet or a rtc alarm?
Thanks,
Hi Alexandre17220,
I think we are working on similar projects because it seems we have tested the same tablet and we are also lookgin for the followinf important things :
-A- securing the environnement by prohibiting the user to access the Os interface
-B- use a ethernet device via an USB adapter.
We have tested the following ones :
- Toshiba Folio 100 (ok for point A & B but not enough tested on HC 3.2)
- Acer Iconia A200 (the european tablet seems to be not rootable yet)
- Samsung Galaxy Tab P7510 (rootable without any problem so point A must "workable", but we habe problems with point B : do you connect your Tab with Ethernet ?)
Regards,
André
Hi André,
The samsung galaxy is very good, I have rooted it via this link http://galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Yes my application dialog with a server via http request. So I don't want use wifi because it's slow and very limited.
If you want to hide the bottom bar you can use this code :
Code:
try {
Process myproc = Runtime.getRuntime().exec(new String[]{"su","-c","service call activity 79 s16 com.android.systemui"});
myproc.waitFor();
} catch (Exception e) {
Toast.makeText(this, "impossible to kill the bottom bar", Toast.LENGTH_SHORT).show();
}
Thanks,
alexandre17220 said:
Hi dexter,
Do you test this tablet?
Do you think it's possible to wake up this tablet automaticaly the morming? by a magic packet or a rtc alarm?
Thanks,
Click to expand...
Click to collapse
i tested the firmware on my acer a500, but not the physical lenovo hardware, but thats not important here.
and since wifi is going offline during deepsleep on tegra2 tablet, i doubt any magic packet can awaken any tegra tablet unless you force wifi always on, but then alot of angry users will complain about battery life.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Hi everyone,
What is this?
This is a DHCPv6 Client for Android.
Motivation
Google doesn't support DHCPv6. See: https://code.google.com/p/android/issues/detail?id=32621
This is an issue for a lot of people especially for corporations and universities because they need control over the IPv6 addresses they distribute.
I did some research and found out that Fairphone already has support for DHCPv6, they achieve this by implementing the wide-dhcpv6 client and added some own scripts around it.
This gave me the idea to play a little with this client. I did so and the result is this app.
Basically it is an implementation of Fairphone's DHCPv6 solution for every rooted Android phone and not just Fairphone.
Workflow
Broadcast Receiver for CONNECTIVITY_CHANGE (invoked when connectivity is changed)
Check if /system/bin/dhcp6c <interface> is running (this is the master process) if not then invoke it
Sending a signal with /system/bin/dhcp6ctl to the master process to get an IPv6 address (dhcp6ctl -C start interface <interface>)
Why is root required?
Root permissions are required for the DHCPv6 client to work because it binds to port 546.
Permissions
root - see above
access network and wifi state - catching network changes
internet - for checking if internet is available and getting a list of all interfaces available
billing - for donation
Get the app
Simply download it from the app store: Download from Google Play Store
Source Code
DHCPv6 Client for Android on GitHub
-realm_01
hostname/domain name support?
Installed this on my android TV media box, and it now connects to my DHCPv6 server as expected, and a lease is registered, however it does not supply a host name or domain name. The domain name is advertised by my router, and also supplied as option in DHCPv6 scope.
Are these an android problem, or the DHCPv6 client?
Almost working...
Hi !
Thanks for the app. Android really needs this. I'm trying to use it on Motorola XT1058 running Lollipop. I can see in the packet capture of my router (OpenWrt) that the DHCPv6 transaction is working and my router is giving out statefully assigned IPv6 addresses to my phone. Unfortunately, these addresses don't get assigned to wlan0 interface on Android. I'm still seeing only stateless addresses on wlan0. Any help would be appreciated.
Regards,
André
Thank you, as a system administrator it was crazy annoying to not be able to enforce a an IPv6 range for android devices
This app doesn't work until I adb shell into my device and run dhcp6c wlan0 as root manually.
Works on Pixel XL
Works fine on my Pixel XL with Android 7.1.
Thank you!
Hi, great job on this app. Wondering how you were able to override the Android DHCP software from trying to connect to networks and have it use the IPV6 info your client acquired?