Related
Will my huawei e1550 work under android?
I see that some other Adroid devices (china tablet pc like Zenithink and other) have the software, which can config internet connections.
Will Gen8 init this device?
ncuxxx said:
Will my huawei e1550 work under android?
I see that some other Adroid devices (china tablet pc like Zenithink and other) have the software, which can config internet connections.
Will Gen8 init this device?
Click to expand...
Click to collapse
For now, no. Unless Huawei or 3rd party develop driver for it.
My E1550 now also collecting dust coz i'm using 101 most of the time rather than laptop.
If i understand, we need root access to add 3rd party driver? Or there uis no way to compile driver?
This would be quite interesting if it would work.
Would this also enable call/sms functionalities?
I have an AT&T Laptop Connect Dongle which does not work. I have been able to bluetooth tether using PAN. I would rather use adhoc, i haven't found a way yet.
I prefer Archos to improve the stabilities of his 2.2 firmware first before adding more "new" features.
3G dongles
Correct me if I'm wrong, but as far as I was able to digg around, it seems that USB host mode (wich is already in Archos), __usbserial.ko__, and adeqaute parts of devfs rules, are only three really necessary things that are needed on any linux, for USB 3G dongles to get properly recognized (at least Huawei ones).
rest of the things regarding "dial-up" a 3G connection, are done with commands from ppp package (should be in froyo), can be done from shell (busysbox __should__ be sufficient) for a start.
usb_modeswitch package is needed also, but only for the modems that are USB composites with virtual CD-ROM and/or MMC card reader (like mine E1552) in order to switch them to a serial mode (because their are detected as mass-storage initialy). For a start, this can be overcomed by sending adequate AT command's to dongle, that disable dongle's virtual CD-ROM and/or MMC card reader, from some windows machine prior to experimenting with dongle on linux/archos (setting is saved on dongle - you only need to do it once).
Since I still don't have my A101 (should receive it beggining of 2011), can someone tell me from kernel .config file is USB serial support compiled in archos kernel, and if not can we compile it as a additional module (like archos unionfs/ntfs modules is see in other thread) ?
Like in topic... How to ? i make my wlan card to Ad-hoc but my Ace don't see this
plbubu said:
Like in topic... How to ? i make my wlan card to Ad-hoc but my Ace don't see this
Click to expand...
Click to collapse
If you're using Windows 7, the easiest way is Connectify..
windows xp unfortunetly
AFAIK SGA cannot connect to an Ad Hoc connection. I already asked this one in the development section. I think most android phones with a stock firmware have the same problem . Any Ad hoc connection is hidden. The WPA supplicant needs to be edited to show this type of connection which is not yet available here.
plbubu said:
windows xp unfortunetly
Click to expand...
Click to collapse
It's actually for all windows. I cant test it on XP but it definetely work on Windows 7.
http://www.connectify.me/download/windows.html
roninxt said:
AFAIK SGA cannot connect to an Ad Hoc connection. I already asked this one in the development section. I think most android phones with a stock firmware have the same problem . Any Ad hoc connection is hidden. The WPA supplicant needs to be edited to show this type of connection which is not yet available here.
Click to expand...
Click to collapse
For internet via wifi, I can do this since I updated to KPN stock.
if you can... please do this
There is a file named wpa_supplicant.conf in /etc. May be the solution is there. I look the the file but i don't have any knowledge about this.
Lines: 87-106:
# AP scanning/selection
# By default, wpa_supplicant requests driver to perform AP scanning and then
# uses the scan results to select a suitable AP. Another alternative is to
# allow the driver to take care of AP scanning and selection and use
# wpa_supplicant just to process EAPOL frames based on IEEE 802.11 association
# information from the driver.
# 1: wpa_supplicant initiates scanning and AP selection
# 0: driver takes care of scanning, AP selection, and IEEE 802.11 association
# parameters (e.g., WPA IE generation); this mode can also be used with
# non-WPA drivers when using IEEE 802.1X mode; do not try to associate with
# APs (i.e., external program needs to control association). This mode must
# also be used when using wired Ethernet drivers.
# 2: like 0, but associate with APs using security policy and SSID (but not
# BSSID); this can be used, e.g., with ndiswrapper and NDIS drivers to
# enable operation with hidden SSIDs and optimized roaming; in this mode,
# the network blocks in the configuration file are tried one by one until
# the driver reports successful association; each network block should have
# explicit security policy (i.e., only one option in the lists) for
# key_mgmt, pairwise, group, proto variables
ap_scan=1
Click to expand...
Click to collapse
Maybe when we change:
ap_scan=2
problem can be solved.
I didnt tried it because i dont have a laptop to make adhoc network. Or somebody can find another solution.
i tried using connectify on win 7...it gives me a blue screen
i have a evdo connection on my laptop which i would like to use for my phone too through wifi...
i read somewhere that android doesnt natively enable ad hoc although you can use your mobile as a hot spot, wonder why cant work the other way around.
but yes if anybody knows how to change the code or make it work...pls help
Quite possibly it may not work. There is another thread here on XDA with a hack, although is outdated. May be some workable info there.
Found solution
while trying to find out why there is a blue screen through connectify found something that works for me...Mhotspot
nice software which is clean and easy to install and best of all it works...quite possibly with all android phones
you can get it here www(dot)mhotspot(dot)com
(tl;dr, experienced modders: skip to the steps section below)
I've spent several days trying to set up sharing of my mobile phone's Internet connection with my tf201. The phone (Nokia 6120 classic, running Symbian S60) has neither WIFI, nor bluetooth PAN (don't worry, the terminology is explained below), and there's no PDANet version available for it, which left me with two ways to tether with it: wired USB connection or bluetooth DUN. I show here how to configure both. You might want to do this if you're in a similar position as myself, but also if you want to replace wifi tethering with bluetooth DUN (bluetooth is said to be less power-hungry).
While I'd like the howto to be accessible to novices (such as myself), I can't cover basic/trivial parts and in general will assume a reader capable of googling and with a basic Linux familiarity.
This post does NOT relate to the issue of enabling bluetooth DUN on your Android phone or changing the server side of the connection in other ways. Please don't comment about that in this thread.
My primary source is this outstanding article in Russian, which solves the same problem for a different tablet: notioninkinfo.ru/telefon_kak_3g_edge_modem_dlya_adama/
The process turned out to be much simpler for Prime, since it has most of the necessary software in place.
Background
Sharing internet connection from your mobile phone to another device is called "tethering". Obviously, tethering has great importance when mobile devices are involved, thus a naive soul could hope that it works perfectly in Android. Surprisingly, the opposite is the truth: Android hates tethering with passion; so much that (stupidity being inapplicable) I have no choice but to suspect malice on Google's/ASUS's part. It's not that they lack the resources to implement it; or that the feature requires some kind of special know-how they don't have. No: all these features are present and work in vanilla Linux; the appropriate kernel drivers exist and work; in some cases, the features worked in earlier versions of Android, but have been disabled in later ones. Some bugtracker issues related to this have not received any attention, despite having tens to hundreds of comments from angry users. code.google.com/p/android/issues/detail?id=16717&q=dun&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
/rant
About tethering
There are multiple ways to do tethering that I know of (and probably then a few more). Most of them, unfortunately, are not enabled out of the box or even implemented in Prime at all.
1. Wifi hotspot: this works well *if* your phone supports it. "Hotspot" means that the device acts as a kind of router that is "meant" to accept connections from other devices and not just "happens" to have wifi. AFAIK, from the practical perspective, the only distinction is that the devices present themselves differently.
2. Adhoc wifi: this is the opposite of "hotspot wifi". Transformer Prime with Ice Cream Sandwich (ICS) does not currently support connecting to an adhoc wifi network directly. The feature was present and worked fine in some previous Android versions, but thanks to an offending kernel commit, no longer works in ICS. The only known workarounds are PDANet (see below) or making a custom ROM with a patched kernel. I don't recommend trying the latter at this time, as very few brave souls have already done it, and that was the last anyone heard of them I don't know if all the issues have been ironed out.
3. Bluetooth. There are two ways of connecting through Bluetooth (that I know of). In order to work, both require certain capabilities, or profiles, to be enabled on your phone. It is quite possible none of the two profiles are enabled or even implemented, in which case you're screwed.
3.1. PAN (Personal Area Network): treats the phone as an intelligent device. When connecting to the Internet, the client "asks" the server to establish the link and only forward data from and to the client. This is one of the best ways to do tethering, and fully supported by Prime's user interface out of the box.
3.2. DUN (Dial-Up Networking): treats the phone as a "dumb" device: the client takes over the phone's modem and uses it directly by sending it both commands and data through an emulated serial (RS232) link. This has several disadvantages, among them it requires the client to be aware of the line provider's dial-up config, such as service number, service name, user and password. Prime does not support it out of the box, despite (as we will see) having adequate hardware and software for it.
4. PDANet: this is an application (accessible from the market) that somehow circumvents Prime's and Android's restrictions on wifi and BT connectivity. You install it on both devices, configure it, and it should work. This method is only applicable to a few platforms that PDANet supports, including Android, but not Symbian.
5. USB: if your Prime has the dock, you've got a full-size USB port on it, which can act as a USB host. You can use this port to connect to your mobile phone (if your phone supports it). In some cases, connecting the phone will cause the Prime to discover the phone's modem, and once it is discovered, you can use it just like DUN.
Methods available out of the box: (1), (3.1). Methods this howto is concerned with: (3.2) and (5).
Prerequisites
1. Ice Cream Sandwich (ICS). It is possible the guide will work with earlier versions, but I didn't try it.
2. The tablet is rooted.
3. adb is installed.
There are plenty of other topics that explain how to get these.
Steps
(Note that I'm writing this from memory, so some inaccuracies are inevitable.)
1. connect the tablet to your PC with adb and execute:
Code:
adb shell
2. become superuser:
Code:
su
3. make /system writable:
Code:
mount -o rw,remount /system
4. download the attached ppp scripts
5. download a pre-compiled rfcomm binary here: omappedia.org/wiki/Android:_Working_with_pre-built_binaries
... or build it yourself. Or, if you're stupid enough to trust a random person on the internet, you can use the rfcomm binary included in the attachment.
6. gather the necessary info:
6.1. for USB:
6.1.1. connect your phone to the tablet by USB cable and try to make the tablet recognize it as a modem. This could vary from phone to phone. My 6120c Nokia needs to be connected in "Nokia PC Suite" mode.
6.1.2.
Code:
ls /dev/tty*
. If it worked, you should see new device(s) in the list. In my case, I got /dev/ttyACM0 and /dev/ttyACM1. I'm not sure why it creates two devices instead of one, but using /dev/ttyACM0 seems to work fine.
6.2. for DUN:
6.2.1. enable bluetooth both in the tablet and in the phone and pair them
6.2.2.
Code:
sdptool search DUN
The output should look like this:
Code:
Searching for DUN on [B]00:1E:A4:66:94:2E[/B] ...
Service Name: Dial-Up Networking
Service RecHandle: 0x10019
Service Class ID List:
"Dialup Networking" (0x1103)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: [B]2[/B]
7. Using the above information, fill the placeholders in the scripts you downloaded. In particular, the following must be replaced with real settings:
7.1. the device on line 8 in 3g_usb. Replace "/dev/ttyACM0" with the device you got in step 6.1.2
7.2. MAC and channel in 3g_bt_up. Use the values you got in step 6.2.2.
7.3. username and password in 3g_usb and 3g_bt. If you can use mobile internet from your phone, these values are already stored in the phone, so you just need to find them in the settings. Failing that, search for the correct values for your operator on the net (they are often the same for all users of the operator) or inquire the operator.
7.4. host name in 3gchat. Again, this varies from operator to operator. Note that the host name need not end with "com" or another valid root domain, and can thus sound nonsensical, e.g. "internet.internet". In my case (Israeli operator called Rami Levi), it was "internet.rl".
7.5. There are more operator-specific settings you might need to change in 3gchat, e.g. the dial-up number. In case the current value (*99***1# in my script) doesn't work, you can most likely find those on the net. If it doesn't work, search the net with query like "pppd chat <MY OPERATOR>" (without the quotes).
8.
Code:
adb push 3gchat /etc/ppp/
adb push 3g_bt_pdown /system/bin/
8.1. for usb connectivity:
Code:
adb push 3g_usb /etc/ppp/peers/
adb push 3g_usb_pup /system/bin/
6.2. for DUN connectivity (mind the trailing slashes):
Code:
adb push 3g_bt /etc/ppp/peers/
adb push 3g_bt_pup /system/bin/
adb push rfcomm /system/xbin/
7.
Code:
adb shell
chmod 0755 /etc/ppp/3gchat /system/bin/3g_usb_pup /system/bin/3g_usb_pdown /system/bin/3g_bt_pup /system/bin/3g_bt_pdown /system/xbin/rfcomm
8. try running 3g_bt_pup and 3g_usb_pup in adb
9. if it works, find a way to run these scripts directly on the Prime. E.g., you might want to make a GUI launcher for every one of 3g_bt_pup, 3g_usb_pup, 3g_pdown. The author of the original article recommends an app called GScript. I personally never tried it, as I just use Terminal Emulator from the market.
10. (Don't forget to remount /system in ro mode.)
Known issues
1. DNS refuses to work when you connect through the scripts. A workaround that I found is to connect to a wifi, then disconnect, then connect using the scripts. DNS will continue working until the next reboot. (I didn't have enough time to play with it yet, so not sure this is consistent.)
2. I consistently get 2-3 times slower download speed through DUN than through USB. Perhaps this has something to do with my phone, OTOH could be a problem in the scripts.
Enjoy! Corrections, tweaks, fixes are welcome.
Thank you very much!
I was trying to bring the tablet into the internet using bluetooth DUN for days. Your rfcomm, skripts and complete explanations did the trick: Archos G9 10.1 with Android 4.0.4 (Archos: 4.0.25) connects to Nokia N79 and dials into the internet.
neatfires said:
Known issues
1. DNS refuses to work when you connect through the scripts. A workaround that I found is to connect to a wifi, then disconnect, then connect using the scripts. DNS will continue working until the next reboot. (I didn't have enough time to play with it yet, so not sure this is consistent
Click to expand...
Click to collapse
Do you already have a solution for this problem?
I see strange behavior:
What I tried:
I had a look into syslog (using logcat) which reveals the DNS servers of the 3g provider.
Then I entered this IP-address in /etc/resolv.conf
Result:
* traceroot resolves the names but
* ping does not,
* ICS Browser+ does not and
* K9 does not resolve the DNS names
Do you have any idea how this problem could be solved?
Best regards,
Pfeffer2de.
Hi pfeffer2de,
Unfortunately, I don't have any other solution to this problem than the workaround I mentioned (connecting to the wifi before using DUN). I haven't used DUN at all since late spring, so I have no new input on this. If you find a solution, please post it here for other people to learn about it.
Hi neatfires!
neatfires said:
Unfortunately, I don't have any other solution to this problem than the workaround I mentioned (connecting to the wifi before using DUN). I haven't used DUN at all since late spring, so I have no new input on this. If you find a solution, please post it here for other people to learn about it.
Click to expand...
Click to collapse
I have to admit that I do not really understand what do you mean: Of couse the tablet has been connected to an Wifi access point some time before.
I rooted the device, connected to a wifi hotspot, made your steps and connected bluetooth DUN finally. Ok, I had some tries to succeed in connecting DUN. Anyway I had the DNS problems. So what is the difference to your work a round, at what point in time the wifi should be connected?
BTW: I switched wifi off before connecting bluetooth DUN.
Best regards,
Pfeffer2de.
pfeffer2de said:
Hi neatfires!
I have to admit that I do not really understand what do you mean: Of couse the tablet has been connected to an Wifi access point some time before.
I rooted the device, connected to a wifi hotspot, made your steps and connected bluetooth DUN finally. Ok, I had some tries to succeed in connecting DUN. Anyway I had the DNS problems. So what is the difference to your work a round, at what point in time the wifi should be connected?
BTW: I switched wifi off before connecting bluetooth DUN.
Best regards,
Pfeffer2de.
Click to expand...
Click to collapse
I can't remember all the details now, but the post says that you need to connect to a wifi, and then DNS works until the reboot, so it must be true . Anyway, try this:
1. fill in a valid DNS host in resolv.conf
2. connect to a wifi network, make sure you can reach internet
3. disconnect from the wifi network, but don't turn off the wifi
4. connect through the DUN
If it works, try doing the same but turn off the wifi. I can't remember currently if I had to have wifi on or off (I think I didn't), but this is the only thing I can think of.
Almost working, bit missing on
neatfires said:
I can't remember all the details now, but the post says that you need to connect to a wifi, and then DNS works until the reboot, so it must be true . Anyway, try this:
1. fill in a valid DNS host in resolv.conf
2. connect to a wifi network, make sure you can reach internet
3. disconnect from the wifi network, but don't turn off the wifi
4. connect through the DUN
If it works, try doing the same but turn off the wifi. I can't remember currently if I had to have wifi on or off (I think I didn't), but this is the only thing I can think of.
Click to expand...
Click to collapse
I tried it on my Motorola Atrix 4G which doesn't support 'reverse DUN' as such and I had to use my GPRS phone due to data plans reaching limits on Atrix 4G.
OK, here is original '3gchat' file, I just filled in releavant APN
--------------------------------------------------------------------------
#!/system/bin/sh
exec /system/bin/chat \
TIMEOUT 5 \
ECHO ON \
ABORT '\nBUSY\r' \
ABORT '\nERROR\r' \
ABORT '\nNO ANSWER\r' \
ABORT '\nNO CARRIER\r' \
ABORT '\nNO DIALTONE\r' \
ABORT '\nRINGING\r\n\r\nRINGING\r' \
'' AT \
OK ATH \
OK ATE1 \
OK 'AT+CGDCONT=1,"IP","<APN>","0.0.0.0",0,0' \
OK ATDT*99***1# \
TIMEOUT 22 \
CONNECT ""
----------------------------------------------------------------------------
It hangs at $ exec /system/bin/chat \ 'Permission Denied'
If i delete above line (exec /system/bin/chat \ ) from 3gchat, it connects and remain conencted to BTDUN to my GPRS phone until I diconenct it, however there is no data. Following is after deleting line "exec /system/bin/chat \ "
-----------------------------------------------------------------------------
#!/system/bin/sh
TIMEOUT 5 \
ECHO ON \
ABORT '\nBUSY\r' \
ABORT '\nERROR\r' \
ABORT '\nNO ANSWER\r' \
ABORT '\nNO CARRIER\r' \
ABORT '\nNO DIALTONE\r' \
ABORT '\nRINGING\r\n\r\nRINGING\r' \
'' AT \
OK ATH \
OK ATE1 \
OK 'AT+CGDCONT=1,"IP","<APN>","0.0.0.0",0,0' \
OK ATDT*99***1# \
TIMEOUT 22 \
CONNECT ""
---------------------------------------------------------------------------------
Infact, there wasn't any /system/bin/chat directory so I created one to comply with 3gchat sript. Yet above permission denied issue remained, until I deleted the "exec...." line.
I found someone adding follwing line in the shell script file connecting his chat file to /usr/sbin/chat :
connect '/usr/sbin/chat -v -f /etc/ppp/<chatfile name>'
Above quotes /usr/sbin/chat while '3gchat' script uses /system/bin/chat.
I am missing something here.
One a side note, I tried BlueVPN from the marked which worked.
UPDATEver
OK I installed BlueDUN on my Xolo X900 (which doesn't support reverseDUN, i.e. it doesn't natively support Bluetooth Dial-Up Modem profile, butr it can dial-up other Bluetooth Dial-Up Modems, i.e. other phones). This software enabled Xolo X900 to become a software Bluetooth Dial-Up Modem (as it natively doesn't have this feature like most android devices)
On another anrdoid device (Atrix 4G) I installed BlueVPN (please note this becomes almost mandatory somehow as until target phone natively supports reverseDUN, other btDial-Up softwares will not be able to detect (via sdptool) target phone until it has native reverseDUN (Bluetooth SPP per say). Then removed old pairing and repaired both devices again. After that, the most importatnt is to swicth on WiFi Tethering on target phone (in my case Xolo X900) and connect host phone (Atrix 4G in my case) to the WiFi Tether of Xolo X900. Whie WiFiTether is active, start BlueDUN on target phone (Xolo X900) and then start BlueVPN on host android device (Atrix 4G). This will make a working internet connection and you will be able to connect it via VPN setup. After net is connected you can turn off WiFi tethering and switch off wifi on both devices. WiFi thethering is required initially till internet starts working as it sorts out DNS issues.
As long as target phone is 3G or 4G, speed is not a problem. I am usining this BlueDUN + BlueVPN combo to post this.
I am resolved that BT tethering method of OP will not work in my setup wihout setting up VPN because I have been able to establish connection but still couldn't get any net traffic.
For the record, its not android that "hates tethering" - its the carriers that block, disable, or remove those capabilities, because they want to charge you more for the same service based on what device (eg your laptop) you use it with.
hi,
for use with Hackintosh, I installed a Dell DW1510 (Broadcom BCM4322) Wifi PCI card in my ThinkPad X220. It only barely works with Android x86 / Remix OS.
Out of the box, it is detected, Mac Address is displayed and it can be enabled, but it searches for wifi networks forever.
Using Linux, I installed newer (closed-source) firmware files. Now it does find wifi networks, but only 5GHz / -ac ones. Beside that, it's extremely slow (only getting about 4Mbit download, normally around 50Mbit). I know the "open-source" b43 is slower than the propietary broadcom-wl one, but it wasn't THAT much on Linux.
Is it possible to use/install the propietary broadcom-wl driver, or getting at least 2.4GHz working and more speed (It was around 15Mbit on Linux with b43)?
Xorg
TheXorg said:
hi,
for use with Hackintosh, I installed a Dell DW1510 (Broadcom BCM4322) Wifi PCI card in my ThinkPad X220. It only barely works with Android x86 / Remix OS.
Out of the box, it is detected, Mac Address is displayed and it can be enabled, but it searches for wifi networks forever.
Using Linux, I installed newer (closed-source) firmware files. Now it does find wifi networks, but only 5GHz / -ac ones. Beside that, it's extremely slow (only getting about 4Mbit download, normally around 50Mbit). I know the "open-source" b43 is slower than the propietary broadcom-wl one, but it wasn't THAT much on Linux.
Is it possible to use/install the propietary broadcom-wl driver, or getting at least 2.4GHz working and more speed (It was around 15Mbit on Linux with b43)?
Xorg
Click to expand...
Click to collapse
Did you have any success with your Wifi? I am running the same chip in a Macbook & experience the same problem... searching for networks forever. Could you describe how you installed the newer firmware files?
Whitest said:
Did you have any success with your Wifi? I am running the same chip in a Macbook & experience the same problem... searching for networks forever. Could you describe how you installed the newer firmware files?
Click to expand...
Click to collapse
Use this method for now, works better than the open-source-method: https://m.reddit.com/r/RemixOS/comments/40rjvg/how_to_get_broadcom_wifi_to_work/
TheXorg said:
Use this method for now, works better than the open-source-method: https://m.reddit.com/r/RemixOS/comments/40rjvg/how_to_get_broadcom_wifi_to_work/
Click to expand...
Click to collapse
hi guy, thx :laugh::laugh::laugh::laugh:
work
TheXorg said:
Use this method for now, works better than the open-source-method: https://m.reddit.com/r/RemixOS/comments/40rjvg/how_to_get_broadcom_wifi_to_work/
Click to expand...
Click to collapse
i tested your post for my broadcom wifi.
i activated terminal, i load remix with debug=1
when tape this entry "modprobe wl" i have nothing in my screen
and when reboot wifi doesn't work
z750leovince said:
i tested your post for my broadcom wifi.
i activated terminal, i load remix with debug=1
when tape this entry "modprobe wl" i have nothing in my screen
and when reboot wifi doesn't work
Click to expand...
Click to collapse
It's normal, modprobe does not Output anything. Don't reboot, just type exit to continue booting. If RemixOS reboots then, something else is wrong.
TheXorg said:
It's normal, modprobe does not Output anything. Don't reboot, just type exit to continue booting. If RemixOS reboots then, something else is wrong.
Click to expand...
Click to collapse
ok....i type modprobe in terminal in remix os...not at boot at remix
i tested but my wifi dosn't work...i have searching wifi and nothing appared
i have Broadcom BCM4352
I'd like to point out the exact way how to do this workaround to avoid any missunderstandings:
1. add the DEBUG=1 flag to your grub parameters and press F10 (only (U)EFI Booting, for Legacy Booting just press Enter)
2. wait for the debug terminal to come up
3. type modprobe wl (if no message appeared you're good to go) and then type exit to continue booting
4. enjoy your perfectly working WiFi (hopefully)
Please note this is only a temporary solution that you would have to repeat at each boot-up. Searching for a permament solution I only came across the same Reddit thread that @TheXorg already linked: by renaming/deleting a folder in the kernel/driver section I managed to achieve the same working WiFi result without having to type anything at boot-up.
Here's how:
In debug mode.. Delete ssb folder from /lib/modules/4.0.9-android-x86+/kernel/drivers.. It helped me wid other x86 android and the new pheonix os.. Idk abt remix but its worth a try
Click to expand...
Click to collapse
By Elflord5431 (on reddit)
I simply installed a root explorer (Solid Explorer in my case) and renamed the folder within RemixOs. After a normal reboot without DEBUG=1 flag WiFi worked absolutely fine.
- tested and working on my Macbook 5,2 (Early 2009) with Broadcom 4322 Wifi Chip. Credits & thanks to TheXorg for starting this thread, to Turtle5204 and Elflord5431 for sharing these workarounds
Whitest said:
I'd like to point out the exact way how to do this workaround to avoid any missunderstandings:
1. add the DEBUG=1 flag to your grub parameters and press F10 (only (U)EFI Booting, for Legacy Booting just press Enter)
2. wait for the debug terminal to come up
3. type modprobe wl (if no message appeared you're good to go) and then type exit to continue booting
4. enjoy your perfectly working WiFi (hopefully)
Please note this is only a temporary solution that you would have to repeat at each boot-up. Searching for a permament solution I only came across the same Reddit thread that @TheXorg already linked: by renaming/deleting a folder in the kernel/driver section I managed to achieve the same working WiFi result without having to type anything at boot-up.
Here's how:
By Elflord5431 (on reddit)
I simply installed a root explorer (Solid Explorer in my case) and renamed the folder within RemixOs. After a normal reboot without DEBUG=1 flag WiFi worked absolutely fine.
- tested and working on my Macbook 5,2 (Early 2009) with Broadcom 4322 Wifi Chip. Credits & thanks to TheXorg for starting this thread, to Turtle5204 and Elflord5431 for sharing these workarounds
Click to expand...
Click to collapse
Hi @Whitest, did you try this on the latest version? Because I'm facing some issues with the mac mini 3.1 (early 2009 and broadcom chip like yours) and without success... Nothing happens with the modprobe and cant delete the folder on debug (it gives an error deleting).
5T0RM said:
Hi @Whitest, did you try this on the latest version? Because I'm facing some issues with the mac mini 3.1 (early 2009 and broadcom chip like yours) and without success... Nothing happens with the modprobe and cant delete the folder on debug (it gives an error deleting).
Click to expand...
Click to collapse
Did you boot with REMOUNT_RW=1 kernel boot flag?
I have compiled a kernel from Floppy kernel source, to make it contain an ATH9K driver for TP-Link usb wifi card TL-WN722N, but when I plug it in on OTG usb and execute command in Termux to list available devices, it's not there, and the wifi network card's LED is not on. I'm not sure if it's the kernel driver is not working or it's app's level issue, Is there a way to check if the driver is successfully installed? Thanks!
The device is a Xiaomi MI 5, running official miui dev ver of Android 8, kernel is compiled from Floppy Kernel for miui Oreo
The app I'm trying to run is airmon-ng via Termux, device is rooted by Magisk, and bootlock is unlocked.
kdlsw said:
I have compiled a kernel from Floppy kernel source, to make it contain an ATH9K driver for TP-Link usb wifi card TL-WN722N, but when I plug it in on OTG usb and execute command in Termux to list available devices, it's not there, and the wifi network card's LED is not on. I'm not sure if it's the kernel driver is not working or it's app's level issue, Is there a way to check if the driver is successfully installed? Thanks!
The device is a Xiaomi MI 5, running official miui dev ver of Android 8, kernel is compiled from Floppy Kernel for miui Oreo
The app I'm trying to run is airmon-ng via Termux, device is rooted by Magisk, and bootlock is unlocked.
Click to expand...
Click to collapse
IMHO to get to know all the drivers, you need to go through the /sys directory.
jwoegerbauer said:
IMHO to get to know all the drivers, you need to go through the /sys directory.
Click to expand...
Click to collapse
Thanks, that really helped, I checked /sys/module, and the driver (ath9k_htc) is there, then I checked lsmod, there is only one item:
Code:
gemini:/sys/module # lsmod
Module Size Used by
wlan 5801121 0
I think this is the one I added to the kernel, but is it a bit weird that there is no other loaded module?
And the usb wifi card is still not working, even I can see the device is showing in lsusb -t, the driver is not loading to the device.
I'm really out of ideas, can anyone please give some suggestions? Thanks!
@kdlsw
Loaded and hence currently running modules ( drivers ) are to be found in file /proc/modules
jwoegerbauer said:
@kdlsw
Loaded and hence currently running modules ( drivers ) are to be found in file /proc/modules
Click to expand...
Click to collapse
Here is what I see in there:
Code:
wlan 5801121 0 - Live 0x00000000000000 (O)
So it's definitely there, loaded. But the wifi card is still not working, I really don't have too much idea of how to proceed from this point.
The function I have selected from make menuconfig when compile kernel was called ATH9K and ATH9K_HTC, here it's wlan, is there something wrong? I checked the same wifi card plug into a desktop Debian, there is no module named wlan, the driver showed in lsusb is ath9k_htc.
And the offset of this being all zero seems not normal?
And it's the only one as not in tree external module, maybe external modules don't work? Should I try to compile it as in the tree?
Can you please point me some direction? What should I try from this point? Thanks
I finally got it working, what I did is to bind the driver to the usb device, and download a firmware for the device and put it in firmware' corresponding directory, I noticed it because there was an error message of loading firmware failed in dmesg when usb device is plugged. THANKS!!