Update:
handsets are becoming very hot when wifi is used, you can make them use less power by using the rootfs.img provided, changes where made to tiwlan.ini during testing which keeps the wifi on active even when not in use, this version has reverted the changes and now power saving can be used once more.
http://drop.io/coolerwifikaiser
Aims:
Wakelocks?
Looks like this thread has served its purpose
Wow, are you actually doing all of these commands through the phone? >_<
I really want to see wifi rollin on android too, can't wait to load the ol' Tilt up with it.
the '-f' option
Hi,
a short question, you wrote...
Code:
'wpa_supplicant -f -Dtiwlan0 -itiwlan0 -c/data/misc/wifi/wpa_supplicant.conf &'
...and I've allready seen this in different ohter posts, but I don't know what the '-f' option effects.
I allready browsed the manpages an this option ins't listed. I just tried the command without this statement and it also worked (but did not create the output '-Dtiwlan0' to '/data/local/tmp'). But wlan also doesn't work...
For Polaris users who might need this info:
First things first, make sure wlan works in Windows Mobile. This seems to be the procedure for getting the wlan into do something in Android. It seems to be very similar to the wifi tethering guides on the G1.
Custom Kernel
We need a kernel, the kernel config produced by make vogue_defconfig ARCH=arm leaves the wireless extensions disabled, so this might the cause of the missing mac address in ifconfig. Current attempts to produce a kernel with these extensions have caused the settings dialogues and ifconfig to hang, Ctrl+C does not force an exit. I'll continue to investigate this.
Tiwlan kernel module
I've found another version of the tiwlan driver, other than the one that is currently in git master which loads the firmware and gives the ok - OK
Download Update: This driver skipped checks, ignore it
so lets see if we can merge this with the newer driver to get a working one.
Initial Variables
Code:
setprop wifi.interface tiwlan0
WLan Commands
Modprobe Method:
Code:
mkdir -p /lib/modules/`uname -r`
cp /sdcard/wlan.ko /lib/modules/`uname -r`/
Insmod Method:
Code:
insmod /sdcard/wlan.ko
Tiwlan0 Mac address: No
Required Output: TIWLAN: Driver loaded
WLAN_Loader
Code:
wlan_loader -f /sdcard/Fw1251r1c.bin -e /proc/calibration -i /sdcard/tiwlan.ini
Tiwlan0 Mac address: No
Required Output: Set property wlan.driver.status = ok - Ok
ifconfig -a might need to show a mac address at this point, i'm still not sure when ifconfig -a gets the mac address info
Code:
wpa_supplicant -ddK -Dtiwlan0 -itiwlan0 -c/sdcard/wpa_supplicant.conf &
ifconfig -a must show a mac address or the next step will error out, you can assign one using the following command, just change it to mac address you see in windows. However simply assigning one with this command might not be enough, it could be the sign of a bigger problem.
Code:
ifconfig tiwlan0 hw ether 00:00:00:00:00:00
Code:
ifconfig tiwlan0 192.168.1.100 netmask 255.255.255.0
ifconfig tiwlan0 up
Log Collecting:
Dmesg - Its a ring buffer so as new info is added old info will be removed, you need to run the command right after insmod or modprobe to see if it worked ok.
Code:
[B]dmesg|grep -i wlan[/B]
TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
TIWLAN: Driver initialized (rc 0)
TIWLAN: 1251 PG [B]1.1[/B]
TIWLAN: Driver loaded
If i'm right The kaiser has 1.1. the G1 has 1.2, its a reference to the chip used.
Logcat
You can run logcat at the start to keep a log of everything the machine has done since android has started. If you run it like this it will keep logging to the file as you run other commands so when you boot back to WM and sync you can open the file in an editor like Notepad++ and see what happened. This is the first thing i run when i get to the root shell
Code:
logcat -f /sdcard/debuglog.txt &
After running the wlan_loader you can run this to check it worked ok:
Code:
[B]grep -i 'wlan' /sdcard/debuglog.txt[/B]
D/wlan_loader( 395): adapter tiwlan0, eeprom /proc/calibration, init /sdcard/tiwlan.ini, firmware /sdcard/Fw1251r1c.bin
D/wlan_loader( 395): Configuring adapter
D/wlan_loader( 395): Adapter configuration rc = 0
D/wlan_loader( 395): Starting configMge
D/wlan_loader( 395): ConfigMge start rc = 0
D/wlan_loader( 395): Driver configured
D/wlan_loader( 395): Firmware loaded and running OK
D/wlan_loader( 395): Set property wlan.driver.status = ok - Ok
i did once end up with the ok - Ok but it was hit and miss, and i've ended up with all sorts from ok - Fail to fail - Ok to fail - Fail but ifconfig has never shown a mac address on its own
Email to...
The terminal emulator in android should have an option in the menu to email everything you've seen to an email address, use that to keep logs of the entire session. Better terminal has this feature, but it stopped working, try
Files
Fw1251r1c.bin
The firmware filenames of the G1 and the Kaiser have the same name. So we should get a list of good kaiser firmware to rule firmware issues out as soon as possible. If you can connect in windows mobile to a wpa secured AP then the Fw1251r1c.bin in the windows folder on the rom should be the one you are using in Android.
File, Size in bytes, MD5SUM, Source
Fw1251r1c.bin, 185388, ebf5c2036d37bc56b4d41ddcbda4311e, 6.1 WWE ROM shifu, Download
tiwlan.ini
Lets get a good tiwlan.ini file, so we know if its causing issues.
Values:
Comming Soon...
wpa_supplicant.conf
Code:
ctrl_interface=tiwlan0
ap_scan=1
eapol_version=1
fast_reauth=1
eapol_version=1
update_config=1
network={
ssid="WIFISSID"
...
priority=1
}
-------------------------------------------------------------------------------------
Quick Scripts:
Its hard to type long commands on the keyboard so here are some scripts to help:
Code:
[B]/sdcard/cmd1[/B]
#!/bin/sh
echo 'Setting Variables...'
setprop wifi.interface tiwlan0
echo 'Variables Set!'
echo 'Logging to /sdcard/debuglog.txt...'
pkill logcat
logcat -f /sdcard/debuglog.txt &
echo 'Logger Started!'
echo 'Copying WLan Module...'
mkdir -p /lib/modules/`uname -r`
cp /system/lib/modules/wlan.ko /lib/modules/`uname -r`/
echo 'Module Coppied!'
echo 'Loading Module...'
modprobe wlan
lsmod
echo 'Module Loaded!'
#
Code:
[B]/sdcard/cmd2[/B]
#!/bin/sh
echo 'Running Loader...'
wlan_loader -f /sdcard/Fw1251r1c.bin -e /sdcard/calibration -i /sdcard/tiwlan.ini
echo 'Loder Completed'
echo 'Ifconfig Output'
ifconfig -a
dmesg|grep -i wlan
cat /sdcard/debuglog.txt... |grep -i wlan
#
Output:
$ su
~ # cd /sdcard/
/sdcard # ./cmd1
Setting Variables...
Variables Set!
Logging to /sdcard/debuglog.txt...
Logger Started!
Copying WLan Module...
Module Coppied!
Loading Module...
wlan 584168 0 - Live 0xbf000000
Module Loaded!
/sdcard # ./cmd2
Running Loader...
Loder Completed
Ifconfig Output
tiwlan0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
[ 96.701234] TIWLAN: Driver loading
[ 97.593872] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
[ 97.599251] TIWLAN: Driver initialized (rc 0)
[ 97.599511] TIWLAN: 1251 PG 1.1
[ 97.599547] TIWLAN: Driver loaded
D/wlan_loader( 518): adapter tiwlan0, eeprom /sdcard/calibration, init /system/etc/wifi/tiwlan.ini, firmware /sdcard/Fw1251r1c.bin
D/wlan_loader( 518): Configuring adapter
D/wlan_loader( 518): Adapter configuration rc = 0
D/wlan_loader( 518): Starting configMge
D/wlan_loader( 518): ConfigMge start rc = 0
D/wlan_loader( 518): Driver configured
D/wlan_loader( 518): Firmware loaded and running OK
D/wlan_loader( 518): Set property wlan.driver.status = ok - Ok
thanks,
how did you manage that configMge doesn't fail on start? I still get 'rc = -1'. Did you build a new 'wlan.ko' with the Kernelsource from git (Vogue/Kaiser)? And what firmware are you using (the original or the extracted?)
maybe you can post your files for testing...
toasty_ said:
thanks,
how did you manage that configMge doesn't fail on start? I still get 'rc = -1'. Did you build a new 'wlan.ko' with the Kernelsource from git (Vogue/Kaiser)? And what firmware are you using (the original or the extracted?)
maybe you can post your files for testing...
Click to expand...
Click to collapse
Its either the variable being set or modprobe being used that does the trick, so try those, i'm in the middle of compiling a newer kernel to see if it works better
Thx for the short Tutorial and the scripts. Unfortunately I still get the message:
Code:
'ConfigMge start rc = -1'
I think the reason is the (my) wlan.ko module - it shows following message/warning while loading (insmod and modprobe)
Code:
wlan: version magic '2.6.25-00818-gf668526 preempt mod_unload ARMv6 ' should be '2.6.25-00832-g42c5da5 preempt mod_unload ARMv6'
but its loaded...
especialy lsmod gives me another value for the second number (think the allocated memory):
Code:
wlan 583852 0 - Live 0xbf000000
I use the firmware from '3.34.shifuv11F WWE':
Size: 185388 byte
MD5: ebf5c2036d37bc56b4d41ddcbda4311e
dmesg:
Code:
[ 114.718730] TIWLAN: Driver loading
[ 115.079288] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
[ 115.084840] TIWLAN: Driver initialized (rc 0)
[ 115.084952] TIWLAN: Driver loaded
[ 122.852419] TIWLAN: TIWLAN: Failed to start config manager
logcat:
Code:
D/wlan_loader( 444): adapter tiwlan0, eeprom /proc/calibration, init /sdcard/wlan/tiwlan.ini, firmware /sdcard/wlan/Fw1251r1c.bin
D/wlan_loader( 444): Configuring adapter
D/wlan_loader( 444): Adapter configuration rc = 0
D/wlan_loader( 444): Starting configMge
D/wlan_loader( 444): ConfigMge start rc = -1
D/wlan_loader( 444): Driver configuration failed (-1)
E/wlan_loader( 444): init_driver() failed
D/wlan_loader( 444): Set property wlan.driver.status = failed - Ok
can you tell me what wlan.ko you are using - maybe a link...
Upon further investigation it turns out that a specific version of the firmware and a compatible wlan.ko are needed to get it to work, i'm rolling up a fresh system.img to test now, i'll post it if it works
http://forum.xda-developers.com/showthread.php?p=4231219
toasty_ said:
Thx for the short Tutorial and the scripts. Unfortunately I still get the message:
Code:
'ConfigMge start rc = -1'
I think the reason is the (my) wlan.ko module - it shows following message/warning while loading (insmod and modprobe)
Code:
wlan: version magic '2.6.25-00818-gf668526 preempt mod_unload ARMv6 ' should be '2.6.25-00832-g42c5da5 preempt mod_unload ARMv6'
but its loaded...
especialy lsmod gives me another value for the second number (think the allocated memory):
Code:
wlan 583852 0 - Live 0xbf000000
I use the firmware from '3.34.shifuv11F WWE':
Size: 185388 byte
MD5: ebf5c2036d37bc56b4d41ddcbda4311e
dmesg:
Code:
[ 114.718730] TIWLAN: Driver loading
[ 115.079288] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
[ 115.084840] TIWLAN: Driver initialized (rc 0)
[ 115.084952] TIWLAN: Driver loaded
[ 122.852419] TIWLAN: TIWLAN: Failed to start config manager
logcat:
Code:
D/wlan_loader( 444): adapter tiwlan0, eeprom /proc/calibration, init /sdcard/wlan/tiwlan.ini, firmware /sdcard/wlan/Fw1251r1c.bin
D/wlan_loader( 444): Configuring adapter
D/wlan_loader( 444): Adapter configuration rc = 0
D/wlan_loader( 444): Starting configMge
D/wlan_loader( 444): ConfigMge start rc = -1
D/wlan_loader( 444): Driver configuration failed (-1)
E/wlan_loader( 444): init_driver() failed
D/wlan_loader( 444): Set property wlan.driver.status = failed - Ok
can you tell me what wlan.ko you are using - maybe a link...
Click to expand...
Click to collapse
So you'll have to compile a custom kernel, then a custom wlan.ko before you try this. I have also uploaded the wifi firmware, a link is in the first post
Custom Kernel:
I use the Kernelsources from git ("git.linuxtogo.org", vogue branch). I also tried to build the 'wlan.ko' from Android-source (I set 'KERNEL_DIR' to the Folder of my Kernel source). If I run make I get some errors because of missing include-files.
//Edit: just made symlink to arm-msm
If I'm home on weekend I try to build a new wlan.ko for my kernel. Is there anything, that needs to be patched for kernel 2.6.25?
btw. I found this page http://www.johandekoning.nl/index.php, there are some information about wlan and firmware loading issues (for the G1, but nearly the same problemes)
I didn't do anything special to get a wlan.ko, just compiled it as normal:
Code:
KERNEL_DIR=/Android/kernel make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-
Current status from error log:
Code:
D/wlan_loader( 406): adapter tiwlan0, eeprom /proc/calibration, init /system/etc/wifi/tiwlan.ini, firmware /system/etc/wifi/Fw1251r1c.bin
D/wlan_loader( 406): Configuring adapter
D/wlan_loader( 406): Adapter configuration rc = 0
D/wlan_loader( 406): Starting configMge
D/wlan_loader( 406): ConfigMge start rc = 0
D/wlan_loader( 406): Driver configured
D/wlan_loader( 406): Firmware loaded and running OK
D/wlan_loader( 406): Set property wlan.driver.status = ok - Ok
D/dalvikvm( 161): GC freed 11747 objects / 572968 bytes in 363ms
V/WifiMonitor( 161): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2]
V/WifiMonitor( 161): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=1]
D/SettingsWifiEnabler( 390): Received wifi state changed from Enabling to Enabled
V/WifiMonitor( 161): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2]
V/WifiMonitor( 161): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=1]
[B]D/WifiHW ( 161): 'DRIVER RSSI' command timed out.[/B]
[B]D/WifiHW ( 161): 'DRIVER LINKSPEED' command timed out.[/B]
[B]D/WifiHW ( 161): 'DRIVER MACADDR' command timed out.[/B]
V/WifiStateTracker( 161): Connection to supplicant established, state=INACTIVE
[B]D/WifiHW ( 161): 'DRIVER RXFILTER-ADD 0' command timed out.[/B]
[B]D/WifiHW ( 161): 'DRIVER BTCOEXSCAN-STOP' command timed out.[/B]
V/WifiStateTracker( 161): Changing supplicant state: INACTIVE ==> SCANNING
I/WindowManager( 161): Setting rotation to 1, animFlags=1
I/WindowManager( 161): Config changed: { scale=1.0 imsi=0/0 locale=en touch=3 key=2/1/1 nav=1 orien=2 }
[B]D/WifiHW ( 161): 'DRIVER SCAN-PASSIVE' command timed out.[/B]
V/WifiStateTracker( 161): Changing supplicant state: SCANNING ==> INACTIVE
V/WifiStateTracker( 161): Changing supplicant state: INACTIVE ==> SCANNING
V/WifiStateTracker( 161): Changing supplicant state: SCANNING ==> INACTIVE
W/WindowManager( 161): Window freeze timeout expired.
W/WindowManager( 161): Force clearing orientation change: Window{43120508 StatusBar paused=false}
[B]D/WifiHW ( 161): 'SCAN_RESULTS' command timed out.[/B]
D/StatusBar( 161): updateResources
I/WindowManager( 161): Config changed: { scale=1.0 imsi=0/0 locale=en touch=3 key=2/1/2 nav=1 orien=2 }
D/dalvikvm( 161): GC freed 5792 objects / 384744 bytes in 220ms
D/StatusBar( 161): updateResources
[B]D/WifiHW ( 161): 'LIST_NETWORKS' command timed out.[/B]
W/SurfaceFlinger( 161): timeout expired mFreezeDisplay=1, mFreezeCount=1
W/WindowManager( 161): App freeze timeout expired.
W/WindowManager( 161): Force clearing freeze: AppWindowToken{43358af8 token=HistoryRecord{43358808 {com.android.settings/com.android.settings.wifi.WifiSettings}}}
D/WifiHW ( 161): 'STATUS' command timed out.
D/dalvikvm( 161): GC freed 946 objects / 43184 bytes in 188ms
D/dalvikvm( 317): GC freed 356 objects / 32824 bytes in 105ms
D/WifiHW ( 161): 'DRIVER RSSI' command timed out.
W/WindowManager( 161): Key dispatching timed out sending to com.android.settings/com.android.settings.wifi.WifiSettings
W/WindowManager( 161): Dispatch state: null
W/WindowManager( 161): Current state: {{null to Window{4335b828 com.android.settings/com.android.settings.wifi.WifiSettings paused=false} @ 1247587631205 lw=Window{4335b828 com.android.settings/com.android.settings.wifi.WifiSettings paused=false} [email protected] fin=false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{4335b828 com.android.settings/com.android.settings.wifi.WifiSettings paused=false}}}
I/ActivityManager( 161): ANR (application not responding) in process: com.android.settings
I/ActivityManager( 161): Annotation: keyDispatchingTimedOut
I/ActivityManager( 161): CPU usage:
I/ActivityManager( 161): Load: 5.21 / 3.21 / 1.36
I/ActivityManager( 161): CPU usage from 9963ms to 28ms ago:
I/ActivityManager( 161): system_server: 8% = 7% user + 0% kernel
I/ActivityManager( 161): com.android.alarmclock: 1% = 1% user + 0% kernel
I/ActivityManager( 161): com.android.phone: 0% = 0% user + 0% kernel
I/ActivityManager( 161): loop0: 0% = 0% user + 0% kernel
I/ActivityManager( 161): rild: 0% = 0% user + 0% kernel
I/ActivityManager( 161): android.process.acore: 0% = 0% user + 0% kernel
I/ActivityManager( 161): com.android.inputmethod.latin: 0% = 0% user + 0% kernel
I/ActivityManager( 161): android.process.media: 0% = 0% user + 0% kernel
I/ActivityManager( 161): TOTAL: 8% = 7% user + 1% kernel + 0% irq
toasty_ said:
Custom Kernel:
I use the Kernelsources from git ("git.linuxtogo.org", vogue branch). I also tried to build the 'wlan.ko' from Android-source (I set 'KERNEL_DIR' to the Folder of my Kernel source). If I run make I get some errors because of missing include-files.
If I'm home on weekend I try to build a new wlan.ko for my kernel. Is there anything, that needs to be patched for kernel 2.6.25?
btw. I found this page http://www.johandekoning.nl/index.php, there are some information about wlan and firmware loading issues (for the G1, but nearly the same problemes)
Click to expand...
Click to collapse
Sorry, my mistake, i did in fact have a different driver version. I have uploaded it, check the first post. This driver does not seem to work and will need to be modified.
thanks for the files, where did you get them? Compiling worked without any failure (just had to create a symlink to 'arch-msm'
it seem as if the firmware is loaded (on my phone it only works with the fw of the G1). I think it is realiy loaded because you get 'failed - OK' if you try to load it a 2nd time.
by the way have you extraced wlan-eeprom ('/proc/calibration') http://projects.linuxtogo.org/tracker/index.php?func=detail&aid=32&group_id=37&atid=273
toasty_ said:
thanks for the files, where did you get them? Compiling worked without any failure (just had to create a symlink to 'arch-msm'
it seem as if the firmware is loaded (on my phone it only works with the fw of the G1). I think it is realiy loaded because you get 'failed - OK' if you try to load it a 2nd time.
by the way have you extraced wlan-eeprom ('/proc/calibration') http://projects.linuxtogo.org/tracker/index.php?func=detail&aid=32&group_id=37&atid=273
Click to expand...
Click to collapse
Yes, i have extracted my eeprom file and i have found my mac address in there 3 times, which seems strange. I found the area which has the same start as the carlibration of a G1 (found here) and extracted a chunk to get the same size file. I tried it but it doesn't seem to make a difference. Maybe the data is read after the point at which we are having errors?
So I've played a bit around with the files. At the moment the driver is loaded and the firmware is accepted. But the wlan adapter still doesn't get a Mac.
Btw. if you take a look at the eeprom-file you find the MAC from Offset 0x5C to 0x61 in reverse order. Would be interesting the G1 eeprom-file looks like. Maybe somebody can 'cat /proc/calibration > /sdcard/calibration.bin'.
//***OK nearly the same as you said - should write faster***//
OK, yes found the offset in my file, but the its a bit different
Code:
G1:
02 11 56 06 1C 06 01 16 60 03 07 01 09 56 12 00 00 00 01 0D 56 40
Kaiser:
02 11 56 06 1C 06 [COLOR="Red"]00[/COLOR] 16 60 03 [COLOR="Red"]02[/COLOR] 01 09 56 12 00 00 00 01 0D 56 40
Ah, i made a mistake, still need to find where the contents of calibration are in the rom dump
Ok in romdump there are some more Offsets (0x243E5C8, 0x2500040, 0x2500840, 0x2520040 from full rom-dump) that have nearly the same byte order
But only in 0x2500840 and 0x2500040 my MAC is included --> I've checked with 'diff' both extracted Offsets (752 Byte) and they are same
toasty_ said:
So I've played a bit around with the files. At the moment the driver is loaded and the firmware is accepted. But the wlan adapter still doesn't get a Mac.
Btw. if you take a look at the eeprom-file you find the MAC from Offset 0x5C to 0x61 in reverse order. Would be interesting the G1 eeprom-file looks like. Maybe somebody can 'cat /proc/calibration > /sdcard/calibration.bin'.
//***OK nearly the same as you said - should write faster***//
OK, yes found the offset in my file, but the its a bit different
Code:
G1:
02 11 56 06 1C 06 01 16 60 03 07 01 09 56 12 00 00 00 01 0D 56 40
Kaiser:
02 11 56 06 1C 06 [COLOR="Red"]00[/COLOR] 16 60 03 [COLOR="Red"]02[/COLOR] 01 09 56 12 00 00 00 01 0D 56 40
Click to expand...
Click to collapse
Ok i found the correct location, I searched for 021156061c in the eeprom dump and found it. I haven't had a chance to test this yet. Also another interesting thing to note is that both the kaiser' and G1's mac address started with 00:18 :41
Newbie16 said:
Ok i found the correct location, I searched for 021156061c in the eeprom dump and found it. I haven't had a chance to test this yet. Also another interesting thing to note is that both the kaiser' and G1's mac address started with 00:18 :41
Click to expand...
Click to collapse
yap, my does it too...
Hi.
I need some help trying to fix WiFi on a tablet I was given to fix.
Its some chinese thing so off to a good start!
So its an A13 Allwinner based tablet.
I have re-flashed it with the same firmware that was on it when I got it and the wifi is still not working.
Wifi just wont turn on.
I have done some digging and found that the tablet uses an RTL8188ETV chip.
The module thats being loaded on the tablet is 8188eu.ko IS that right? Or should it be a 8188etv.ko module that I need?
Diagnostic wise, I can see some errors in the error log like:
E/WifiHW ( 159): insmod 8192cu ko failed!
E/WifiStateMachine( 159): Failed to load driver!
E/WifiStateMachine( 159): DriverFailedState
E/WifiHW ( 159): timeout, register netdevice wlan0 failed.
E/WifiStateMachine( 159): Failed to load driver!
E/WifiStateMachine( 159): DriverFailedState
E/WifiHW ( 159): timeout, register netdevice wlan0 failed.
E/WifiStateMachine( 159): Failed to load driver!
E/WifiStateMachine( 159): DriverFailedState
I tried to manually load the 8188eu.ko but all i got was "file already exists"
Anyone got any ideas on how I can get this thing going again?
Seansmit17 said:
Hi.
I need some help trying to fix WiFi on a tablet I was given to fix.
[snip]
The module thats being loaded on the tablet is 8188eu.ko IS that right? Or should it be a 8188etv.ko module that I need?
[snip]
Anyone got any ideas on how I can get this thing going again?
Click to expand...
Click to collapse
This applies to something I'm working on right now. Did you ever find/figure out a solution?
Looks like Realtek supplies Linux (specifically Android-compatible) drivers on their website, but they don't have the ETV version explicitly: http://www.realtek.com/downloads/do...n=4&DownTypeID=3&GetDown=false&Downloads=true
I have now flashed both the latest CROMi and/or cyanogen, but I end up without wifi on both. I cannot enable wifi (i.e.switch the button to ON)
Thanks
Good luck. I have flashed CROMI-X without problems. Have you cold-booted after the install/flash to see if that does anything? If not, try flash again after wiping cache/dalvik. Maybe someone with more experience will post as well. Wish I could offer more suggestions - I'm learning as I go.
jt1998 said:
Good luck. I have flashed CROMI-X without problems. Have you cold-booted after the install/flash to see if that does anything? If not, try flash again after wiping cache/dalvik. Maybe someone with more experience will post as well. Wish I could offer more suggestions - I'm learning as I go.
Click to expand...
Click to collapse
Probably some left over settings from one ROM or the other. You must do a full wipe when switchingbetween the two. Did you try that?
Yes, have done a factory reset, flushed cash and dalvik, etc.
only thing I haven't done is wipe data (for obvious reasons).
In a nutshell, followed all the guides to the letter, but never get wifi.
lister171254 said:
Yes, have done a factory reset, flushed cash and dalvik, etc.
only thing I haven't done is wipe data (for obvious reasons).
In a nutshell, followed all the guides to the letter, but never get wifi.
Click to expand...
Click to collapse
Well unless you have a hardware failure? factory resetting should get it working.....BTW a factory reset in TWRP does wipe data so I'm not sure what you mean by not wiping data.... You need to wipe data as you'll have all your old data settings present. Back up in tibu the stuff you want to keep and wipe data please. What have you got to lose?
Yes, you are quite correct about wiping data. Leaves media though, as that's where the TWRP backups are.
So can confirm that I do a factory reset.
As mentioned in the original post. Everything comes up as expected, except wifi.
extract from logcat
The following is an extract from logcat when I ran cyanogen
--------------------------------------------------------------
D/PhoneStatusBar( 1344): disable: < expand icons alerts ticker system_info back* home* recent clock* search >
V/Sensors ( 1168): Changed Polling period to 400ms
V/TAG ( 1168): bug 7643792: fitSystemWindows([0,38][0,0])
E/wpa_supplicant( 1834): Could not set interface wlan0 flags (UP): Operation not permitted
E/wpa_supplicant( 1834): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 1834): wlan0: Failed to initialize driver interface
W/hwcomposer( 899): Potential underflow detected, enacting countermeasures
I/dalvikvm( 1168): Jit: resizing JitTable from 4096 to 8192
E/WifiHW ( 1168): Supplicant not running, cannot connect
E/WifiHW ( 1168): Supplicant not running, cannot connect
E/WifiHW ( 1168): Supplicant not running, cannot connect
E/WifiHW ( 1168): Supplicant not running, cannot connect
E/WifiHW ( 1168): Supplicant not running, cannot connect
E/WifiStateMachine( 1168): Failed to setup control channel, restart supplicant
D/SoftapController( 897): Softap fwReload - Ok
D/CommandListener( 897): Setting iface cfg
D/CommandListener( 897): Trying to bring down wlan0
I/wpa_supplicant( 1851): Successfully initialized wpa_supplicant
I/wpa_supplicant( 1851): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 1851): Could not set interface wlan0 flags (UP): Operation not permitted
E/wpa_supplicant( 1851): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 1851): wlan0: Failed to initialize driver interface
E/WifiHW ( 1168): Supplicant not running, cannot connect
E/WifiHW ( 1168): Supplicant not running, cannot connect
E/WifiHW ( 1168): Supplicant not running, cannot connect
E/WifiHW ( 1168): Supplicant not running, cannot connect
E/WifiHW ( 1168): Supplicant not running, cannot connect
E/WifiStateMachine( 1168): Failed to setup control channel, restart supplicant
D/SoftapController( 897): Softap fwReload - Ok
D/CommandListener( 897): Setting iface cfg
D/CommandListener( 897): Trying to bring down wlan0
I/wpa_supplicant( 1853): Successfully initialized wpa_supplicant
I/wpa_supplicant( 1853): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 1853): Could not set interface wlan0 flags (UP): Operation not permitted
E/wpa_supplicant( 1853): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 1853): wlan0: Failed to initialize driver interface
E/WifiHW ( 1168): Supplicant not running, cannot connect
E/WifiHW ( 1168): Supplicant not running, cannot connect
E/WifiHW ( 1168): Supplicant not running, cannot connect
-------------------------------------------------------------
Still stuck without a solution.
Given that some of you got Wifi working on your TF700, maybe somebody can post the steps.
Only other difference I can think of is that my device is encrypted.
Thanks
lister171254 said:
Still stuck without a solution.
Given that some of you got Wifi working on your TF700, maybe somebody can post the steps.
Only other difference I can think of is that my device is encrypted.
Thanks
Click to expand...
Click to collapse
Do you have external SD and willing to follow instructions? I will try to help you out and see if you can get your wifi back..
Yep. Have an external card, but not recognised by latest TWRP (still) if that's needed.
Happy to follow your lead.
Thanks
lister171254 said:
Yep. Have an external card, but not recognised by latest TWRP (still) if that's needed.
Happy to follow your lead.
Thanks
Click to expand...
Click to collapse
First, you need to format your external SD with a fat32 for the TWRP to see it. Then you may want to back up your whole system to your external SD just in case you want to restore it later. Also, you need to move all your data to your external SD because you will need to format your internal SD and install a fresh rom on it. Please make sure that you use a "Format" option in the TWRP, not "Wipe". After the installation of the custom rom, you need to shut down your device for at least 10 second and power it up for the rom to set up. When you see the device set up screen, you must let it stabilizes for at least one minute and reboot your device one more time. During the device set up, you want to skip the wifi set up and do not sign in the google app store to prevent any app to install. When your device are up and running, you can check to see if you can enable your wifi. Please follow all the steps and report back. Good luck.
Hi,
problem:
i can´t see any wifi networks, that im not connected to
i´m able to add manuelly any wifi network without problems.. wifi on those manually added networks, works perfect
notification of open networks is enabled.. and i got a notification that there is an open wifi network in range.. so scanning itself seems to work? but my device doesn´t show any network but the one im connected to.
EDIT: "MotoTool AIO" shows me at "SysInfo" -> "wifi" a wifi scan... so this seems really a problem on just displaying the wifi scan results on the device?!?!?
tools like "wifi analyzer" don´t show ANY network
what i tried/looked for, without a positive result:
wifi_display_on has still value 0 in settings.db
file WCNSS_qcom_wlan_factory_nv.bin is existing in /persists (http://forum.xda-developers.com/showpost.php?p=49656627&postcount=3)
flashed stock baseband (http://forum.xda-developers.com/showthread.php?t=2649763)
i did more.. but can´t remember everything.. im sorry...
im on latest gapps.. latest cm12 nightly.. (problem exists since some nightly in the summer of 2014)
im on moto g XT1032
i did not a clean install.. i just upgraded via adb sideload in TWRP (and i don´t really want to do a clean install)
after fixing systemUI Crash and launcher3 crash on myself (look: http://forum.xda-developers.com/showpost.php?p=58316659&postcount=768) i just have this problem (also no GPS Signal, tried to fastboot erasing modemst1 and modemst2)
im really really interested in finding the problem instead of just do a clean install..
so i also take a look at logcat.. and found those errors:
the errors:
I/wpa_supplicant(4981): CTRL_IFACE: Detach monitor /data/misc/wifi/sockets/wpa_ctrl_774-5\x00 that cannot receive messages
E/WifiHW (774): Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory
E/WifiHAL (774): wifi_error wifi_set_scanning_mac_oui(wifi_interface_handle, byte*): requestResponse Error:-95
E/WifiHAL (774): wifi_error wifi_get_gscan_capabilities(wifi_interface_handle, wifi_gscan_capabilities*): GSCAN is not supported by driver
more details:
I/wpa_supplicant(4981): CTRL_IFACE: Detach monitor /data/misc/wifi/sockets/wpa_ctrl_774-5\x00 that cannot receive messages
E/WifiHW (774): Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory
I/wpa_supplicant(6513): Successfully initialized wpa_supplicant
I/wpa_supplicant(6513): rfkill: Cannot open RFKILL control device
E/WifiHW (774): Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory
I/wpa_supplicant(6513): rfkill: Cannot open RFKILL control device
D/WifiConfigStore(774): Loading config and enabling all networks
I/wpa_supplicant(6513): wlan0: CTRL-EVENT-SCAN-STARTED
D/WifiNative-HAL(774): Setting external_sim to 1
D/WifiStateMachine(774): Setting OUI to DA-A1-19
I/WifiNative-HAL(774): startHal
D/wifi (774): setting scan oui 0x977ece20
I/WifiHAL (774): ******HexDump len:0*********
I/WifiHAL (774): ******HexDump End***********
E/WifiHAL (774): virtual int WifiVendorCommand::create() ifindex obtained:29
E/WifiHAL (774): virtual int WifiVendorCommand::set_iface_id(const char*) ifindex obtained:29
I/WifiHAL (774): MAC_OUI - da:a1:19
D/WifiHAL (774): virtual int WifiVendorCommand::requestResponse(): request a response
E/WifiHAL (774): wifi_error wifi_set_scanning_mac_oui(wifi_interface_handle, byte*): requestResponse Error:-95
D/RttService(774): SCAN_AVAILABLE : 3
D/WifiScanningService(774): SCAN_AVAILABLE : 3
D/RttService(774): DefaultState got{ when=-1ms what=160512 target=com.android.internal.util.StateMachine$SmHandler }
D/WifiScanningService(774): DefaultState got{ when=-1ms what=160006 target=com.android.internal.util.StateMachine$SmHandler }
I/WifiNative-HAL(774): startHal
D/wifi (774): getting scan capabilities on interface[0] = 0x977ece20
E/WifiHAL (774): wifi_error wifi_get_gscan_capabilities(wifi_interface_handle, wifi_gscan_capabilities*): GSCAN is not supported by driver
D/wifi (774): failed to get capabilities : -3
E/WifiScanningService(774): could not get scan capabilities
D/WifiMonitor(774): startMonitoring(p2p0) with mConnected = true
D/class com.mobisystems.wifi_direct.StartWifiDirectReceiver(6198): Wifi notification received.
D/class com.mobisystems.wifi_direct.StartWifiDirectReceiver(6198): WIFI State Changed.
Click to expand...
Click to collapse
added important info in first post!