Related
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...
Hello,
i'm trying urukdroid 0.5 and i can not use ipsec/l2tp with it
logcat say :
...
E/racoon ( 1972): libipsec failed pfkey open: Operation not permitted
I/racoon ( 1972): initiate new phase 2 negotiation: 192.168.0.200[4500]<=>192.168.0.10[4500]
I/racoon ( 1972): NAT detected -> UDP encapsulation (ENC_MODE 2->4).
I/racoon ( 1972): Adjusting my encmode UDP-Transport->Transport
I/racoon ( 1972): Adjusting peer's encmode UDP-Transport(4)->Transport(2)
E/racoon ( 1972): pfkey UPDATE failed: Function not implemented
E/racoon ( 1972): pfkey ADD failed: Function not implemented
...
is there a way to rebuild the urukdroid kernel with all ipsec function implemented ?
First I must thank @ aorth, and @ garyd9. Without these guys, this would not be here. Please smash their thanks button when you see them.Thank you guys so much. Much if not all of this is gard9's mod's just ported to our device. In fact until I make any relevant edits this thread will remain tagged [PORT].
Beta 4 up. Stock Clocks and voltages built a version with voltage tables intact, but lowering even one of them by the min(25mV) and applying in SetCpu causes panic.
Beta testers needed. You know the drill. Backup and feedback is always appreciated.
Im almost positive all 6200 kernel partitions are on mmcblk0p5, you can double check with 'get pit' & heimdall. Mobile Odin says it supports P6200 and works fine. I honestly can not say for sure, but Im 99% confident this is the case. Those with any rare models, please be Warned!Flashing a kernel to the incorrect partition is asking to be bricked.--please put both custom and stock on sdcard in case you cannot boot.--
The 2 .zips that have zImage at the end, are to be extracted and flashed with Mobile Odin(recommend Pro to wipe), or heimdall.
Keep in mind if you use Mobile Odin and it doesnt boot, you will be stuck. Good idea to have stock loaded for heimdall, or stock .zip wit CWM Recovery.
The other 2 that start with GT-P6200 can be flashed in recovery. <WARNING>: SOME People have had to wipe /data ; factory reset to get past stuck boot logo.</WARNING> I have updated the install script, so cache and dalvik should be totally cleared.
Either way my custom binary count hasnt changed any.
Features
custom bootanimation support: place appropriate botoanimation.zip in: /system/media/ with permission rw-r--r--. The ICS one garyd made us works lovely. Im using the xda TV one. link coming soon:
Busybox in /sbin.
Support for init.d scripts. (Personal warning about Supercharger scripts: Nitro lag nullifier is OK, but I dont recommend using the I/O tweaks, put me in a boot loop everytime. Be Warned. Also his 3G tweaks made my 3G speeds worse.)
Removed a lot of debug stuff.
unsecure kernel (adb shell gives root)
reboot bootloader and reboot download support
(quick boot in market is a great app)
Enjoy!!
reserved
Beta 4 up: 3/20
Removed OC/UV, stock clocks and voltages. tried a build with Gary's table sysfs in there, UV even one frequency by 25mV and pressing apply in SetCpu caused seizure. At least were stable now. Im not too concerned about battery life. There are other tweaks we can apply.
github: still updating..
https://github.com/crotoloandroid
Established on LA2 (SER). Far so good, thanks.
Putting it through its paces right now
Thanks
SetCPU set to 200 min, 1400 max
OnDemand governor. No other changes.
Nenamark1: 55.6 fps (no previous record)
Nenamark2: 41.1 fps (47.7 fps pre-oc)... very erratic performance
Stability Test, HQ CPU&GPU, 6 minute test: CPU passes, 7. GPU passes, 55. No failures
GL Benchmark v2.1 (All Tests): Passed, however can't upload to GLBenchmark.com as their captcha service is ****ed
Only one issue I've come across so far, and this is the same issue RichardTrip was having when he compiled some custom kernels for me earlier this year. Random wakelocks bring the tab out of sleep and turn the screen on.
These are caused by the usb scanner looking for external USB devices...
Code:
D/UsbService( 3447): setUsbObserverNotification :: titleId = 0, messageId = 0, icon = 17302785, visible = false, dismissable = false
D/usbhost ( 3447): new device /dev/bus/usb/001/004
D/usbhost ( 3447): usb_device_open /dev/bus/usb/001/004
D/usbhost ( 3447): usb_device_new /dev/bus/usb/001/004 fd: 298
D/usbhost ( 3447): usb_device_new read returned 259 errno 4
D/UsbService( 3447): usbDeviceAdded : device :: /dev/bus/usb/001/004 [1519h:0020h] [02h,00h,00h] (CDC Control)
D/UsbService( 3447): isBlackListed :: deviceName = /dev/bus/usb/001/004
D/UsbService( 3447): isBlackListed :: mHostBlacklist[i] = /dev/bus/usb/001/002
E/UsbService( 3447): isBlackListed :: clazz = 2, subClass = 0, protocol = 0
E/UsbService( 3447): isBlackListed :: clazz2 subClass=0
E/UsbService( 3447): continue...
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [02h,02h,01h] (CDC Control)
E/UsbService( 3447): isBlackListed :: clazz = 2, subClass = 2, protocol = 1
E/UsbService( 3447): isBlackListed :: clazz2 subClass=2
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [0ah,00h,00h] (CDC Data)
E/UsbService( 3447): isBlackListed :: clazz = 10, subClass = 0, protocol = 0
E/NotificationService( 3447): cancelNotification - pkg:android, id:17302785
D/TabletStatusBar( 3529): setVisibility(View.VISIBLE
E/UsbService( 3447): isBlackListed :: clazz10 subClass=0
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [02h,02h,01h] (CDC Control)
E/UsbService( 3447): isBlackListed :: clazz = 2, subClass = 2, protocol = 1
E/UsbService( 3447): isBlackListed :: clazz2 subClass=2
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [0ah,00h,00h] (CDC Data)
D/dalvikvm( 6436): GC_CONCURRENT freed 358K, 11% free 6800K/7559K, paused 2ms+1ms
E/UsbService( 3447): isBlackListed :: clazz = 10, subClass = 0, protocol = 0
E/UsbService( 3447): isBlackListed :: clazz10 subClass=0
D/KeyguardViewMediator( 3447): setHidden false
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [02h,02h,01h] (CDC Control)
E/UsbService( 3447): isBlackListed :: clazz = 2, subClass = 2, protocol = 1
E/UsbService( 3447): isBlackListed :: clazz2 subClass=2
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [0ah,00h,00h] (CDC Data)
E/UsbService( 3447): isBlackListed :: clazz = 10, subClass = 0, protocol = 0
E/UsbService( 3447): isBlackListed :: clazz10 subClass=0
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [02h,02h,01h] (CDC Control)
E/UsbService( 3447): isBlackListed :: clazz = 2, subClass = 2, protocol = 1
E/UsbService( 3447): isBlackListed :: clazz2 subClass=2
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [0ah,00h,00h] (CDC Data)
E/UsbService( 3447): isBlackListed :: clazz = 10, subClass = 0, protocol = 0
E/UsbService( 3447): isBlackListed :: clazz10 subClass=0
D/UsbService( 3447): turnOnLcd ::
D/PowerManagerService( 3447): reactivateScreenLocksLocked mProxIgnoredBecauseScreenTurnedOff=true
I/PowerManagerService( 3447): Ulight 0->3|0
I/PowerManagerService( 3447): setTargetLocked mask=2 curValue=0.0 target=95 targetValue=95 delta=6.3333335 nominalCurrentValue=0
I/PowerManagerService( 3447): scheduling light animator
I/power ( 3447): *** set_screen_state 1
D/KeyguardViewMediator( 3447): onScreenTurnedOn, seq = 3
D/KeyguardViewMediator( 3447): notifyScreenOnLocked
D/KeyguardViewMediator( 3447): handleNotifyScreenOn
D/LockScreen( 3447): updateLayout: status=Normal
D/PowerManagerService( 3447): enableLightSensorLocked enable=true mAutoBrightessEnabled=false
D/PowerManagerService( 3447): jumpToTargetLocked targetValue=95: 2
I/PowerManagerService( 3447): Light Animator Finished curIntValue=95
I/OrientationDebug( 3447): [WindowOrientationListener] in enable(), now call SensorManager.registerListener()
D/SensorManager( 3447): registerListener :: handle = 4 name= MPL accel delay= 60000 Listener= [email protected]0c5dc38
D/MPLSensor( 3447): handle : 4 en: 1
D/MPLSensor( 3447): enabled_sensors: 16 dmp_started: 0
D/MPLSensor( 3447): MLSetMPUSensors: 70
I/MPL-ml ( 3447): Actual ODR: 25 Hz
D/MPLSensor( 3447): set_power_states > MLDmpStart()
I/ ( 3447): mpu3050_resume: Resuming to 0070
D/MPLSensor( 3447): setDelay : handle=4, delay=200000000
I/ ( 3447): mpu3050_suspend: suspending sensors to 0000
I/ ( 3447): mpu3050_suspend: Will resume next to 0070
I/MPL-ml ( 3447): Actual ODR: 25 Hz
I/ ( 3447): mpu3050_resume: Resuming to 0070
D/MPLSensor( 3447): setDelay : handle=4, delay=60000000
I/ ( 3447): mpu3050_suspend: suspending sensors to 0000
I/ ( 3447): mpu3050_suspend: Will resume next to 0070
I/MPL-ml ( 3447): Actual ODR: 25 Hz
I/ ( 3447): mpu3050_resume: Resuming to 0070
V/WindowManager( 3447): Setting event dispatching to true
D/KeyguardViewMediator( 3447): setHidden false
D/WifiStateMachine( 3447): ConnectedState{ what=65659 when=-1ms }
D/WifiStateMachine( 3447): ConnectModeState{ what=65659 when=-1ms }
D/WifiStateMachine( 3447): DriverStartedState{ what=65659 when=-1ms }
D/WifiStateMachine( 3447): SupplicantStartedState{ what=65659 when=-1ms }
E/wpa_supplicant( 3807): initalize the scan timer ( 7 )
D/WifiService( 3447): ACTION_SCREEN_ON
I/ScreenReceiver : ( 4156): android.intent.action.SCREEN_ON
D/ProximityScreenOff( 4156): ScreenReceiver : action = android.intent.action.SCREEN_ON State: IDLEPhoneOn = false
D/WifiStateMachine( 3447): ConnectedState{ what=65618 when=-5ms arg1=1 }
D/SensorManager( 4156): registerListener :: handle = 8 name= GP2A Proximity sensor delay= 10000 Listener= [email protected]
I/ProximityScreenOff( 4156): SensorMonitor onStart::Registered
D/WifiStateMachine( 3447): ConnectedState{ what=65591 when=-12ms }
D/WifiStateMachine( 3447): ConnectModeState{ what=65591 when=-12ms }
D/WifiStateMachine( 3447): DriverStartedState{ what=65591 when=-12ms }
D/WifiStateMachine( 3447): SupplicantStartedState{ what=65591 when=-13ms }
D/WifiStateMachine( 3447): ConnectedState{ what=65608 when=-13ms arg1=1 }
D/WifiStateMachine( 3447): ConnectedState{ what=65549 when=-13ms }
D/WifiStateMachine( 3447): ConnectModeState{ what=65549 when=-13ms }
D/WifiStateMachine( 3447): DriverStartedState{ what=65549 when=-13ms }
D/WifiStateMachine( 3447): SupplicantStartedState{ what=65549 when=-13ms }
D/WifiStateMachine( 3447): DefaultState{ what=65549 when=-14ms }
D/WifiStateMachine( 3447): ConnectedState{ what=65613 when=-14ms }
D/WifiStateMachine( 3447): ConnectModeState{ what=65613 when=-14ms }
D/WifiStateMachine( 3447): DriverStartedState{ what=65613 when=-14ms }
D/JuicePlotter.CollectService( 4252): battery:48, plugged:0, screen:95, wifi:true(0kb/s), apn:false(0kb/s), bluetooth:false,cpu:2
W/googleanalytics( 4331): Store full. Not storing last event.
D/SurfaceFlinger( 3267): Screen about to return, flinger = 0xa920
chrisrotolo said:
1st I must thank @ aorth, and @ garyd. Without these guys, this would not be here. Please smash their thanks button when you see them.Thank you guys so much. Much if not all of this is gard9's mod's just ported to our device.
Beta testers needed. 100% working and stable for me. UWAXME - Malyasia Tab
Im almost positive all 6200 kernel partition is on mmcblk0p5, you can double check with get pit & heimdall. Mobile Odin says it supports P-6200 and works fine. I honestly can not say for sure, but Im 99% confident this is the case. Those with any rare models, please be Warned!--please put both custom and stock on sdcard in case you cannot boot.--
the 2 .zips that have zImage at the end, are to be extracted and flashed with Mobile Odin(recommend Pro to wipe), or heimdall.
Keep in mind if you use Mobile Odin and it doesnt boot, you will be stuck. Good idea to have stock loaded in heimdall, or stock .zip wit CWM Recovery.
the other 2 that start with GT-P6200 can be flashed in recovery.
Either way my custom binary count hasnt changed.
As Im short on time at the moment I will make this brief and update this thread shortly.
contains:
custom bootanimation support place usual in: /system/media/bootanimation.zip with permission rw-r--r--. the ICS one garyd made us works lovely.
OC to 1.4 (NO UV yet, but likely in final release.)
unsecure kernel (adb shell gives root)
and init.d scripts tested with Supercharger. (Personal warning about Supercharger scripts: Nitro lag nullifier is OK, but I dont recommend using the I/O tweaks, put me in a boot loop everytime. Also his 3G tweaks made my actually worse.)
to come: UV, reboot download support, (botologos maybe?), what else? let me know I'll see what I can do. This is my first kernel, Im learning as I go.
This should have been released a week ago, but I was stuck on a permissions issue, that was so easy to fix.
Enjoy!!
Click to expand...
Click to collapse
it great and mega fast i am so pleased we have you on out team bro you are mega awesome....donation on its way.
i installed the cwm version and it wad stuck in boot loop but i wiped data and it worked...thanks got for app extracter haha :-D but well worth it.
thanks man keep up the good work
regards jmar8124 G-tab plus kl3 Malaysia
You had to factory reset? Ill double check my scripts to wipe cache and dalvik
chrisrotolo said:
You had to factory reset? Ill double check my scripts to wipe cache and dalvik
Click to expand...
Click to collapse
ye but it could have been something to do with old tegers haha stupid lum of crap haha its got to be the worst app iv ever purchased. thanos man you kernel is great il try installing it agen with out kernel beeing loaded
Updated my original post above ^^^
double_ofour said:
Pare how can i convert CDL to o2? step-by-step please
Click to expand...
Click to collapse
Thanks chris, will test this. Excited to see some dev going on with international version of 7+. Some suggestions:
Please name your kernel! Make it sound cool as it really is
Add cifs.ko support in the future?
Also just a question, would oc'ng to 1.4 ghz be dangerous without any overvolting. Thanks!
Sent from my GT-P6200 using XDA
download and flash awayyyy.... doing stress test now...
edit...
installation no problem... setting up setcpu now... and doing stress test for max 1400
thanks for the help testing guys. This 1.4 is "hidden" in stock cpufreq commented out as "development only". Should be fine unless you run graphics intense apps with min & man set to 1.4 and performance governor for long periods of time.
I'll add warning about some having to wipe /data with CWM.
I'll look into cifs.ko, should be doable.
I've been getting a lot of dropped signal, may be totally unrelated, I just move to a new building, and also just got word we should be getting AT&T LTE in Hartford CT in a few weeks, so could be network thing.
be back as soon as I can guys. Feedback helps.
u guys getting any deep sleep on cpu spy? im not getting any deep sleep
Edit: a reboot helped got deep sleep back. Reasonable batt life at 1.4ghz
being using it for 2 hours with nova2... current batt from 100% to 60% but full 2 hours on nova... quite ok... runnning setcpu 1400 with ondemand governor... havent face any problem yet...
Flashed the custom kernel with recovery ...everything works just fine.
First boot was a bit long as expected.
I used nofrills cpu control, the default interactive governor was a bit laggy, changed to conservative. No deep sleep problem at all.
Thank you.
Sent from my GT-P6200 using XDA
For anyone interested in cifs.ko or tun.ko, check out this thread...
http://forum.xda-developers.com/showthread.php?t=1400255
Anyone else having wakelocks? / random wake ups? I havent had any.
Welp, likely not going to be able to implement @garyd9's UV, keep getting this mesaage :
arch/arm/mach-s5pv310/built-in.o: In function `s5pv310_set_cpufreq_armvolt':
/home/chris/Desktop/samsung-kernel-p6200/arch/arm/mach-s5pv310/cpufreq.c:735: undefined reference to `exp_UV_mV'
/home/chris/Desktop/samsung-kernel-p6200/arch/arm/mach-s5pv310/cpufreq.c:735: undefined reference to `exp_UV_mV'
arch/arm/mach-s5pv310/built-in.o: In function `s5pv310_cpufreq_init':
/home/chris/Desktop/samsung-kernel-p6200/arch/arm/mach-s5pv310/cpufreq.c:2121: undefined reference to `exp_UV_freq'
/home/chris/Desktop/samsung-kernel-p6200/arch/arm/mach-s5pv310/cpufreq.c:2121: undefined reference to `exp_UV_mV'
make: *** [.tmp_vmlinux1] Error 1
at end of kernel build. The one we have I think should be fine. I will add support for reboot bootloader (& download), and probably release final version tomorrow.
I dont want to make this a long in depth thing anyways (its already been a few weeks for me), becuase hopefully Ice Cream is near.
And my home cpu is in dire need of an upgrade (AMD dual core 4GB) building takes nearly an hour on VM, I will likely be getting a new one shortly.
UPDATE: so I think I am getting wake locks/ USB issue. I think Ive had it wake itself 3 times in a row, and Ive had it lose signal when I press power button to wake device, it signal bars are 0;all grey, and/or says no signal, and occasionally at the same time will says usb device removed.
ive compared my config to garyd9's, at least the one I think he used. didnt see anything I think might cause it, although we do have a bit more hardware in ours. I though I recall something in the kernel menuconfig about wakelocks.
I guess its to be expected, hacking my first kernel. Guess I will just have to run some DMESG's
VENT APPEND: I am finding github push/pull/commit/add/etc to be a steamy pile of crap. I will search for alternatives.
yup got random wake locks... but i haven't face any usb/no signal issue. at least not yet
btw info about governors is quite nice here...
http://forum.xda-developers.com/showthread.php?t=1369817
I found the archive article on wakelocks in galaxy nexus forums. Power management configs are same as garyd9's I believe, maybe because of our always on data connection. Have to look in /proc/wakelocks
chrisrotolo said:
I found the archive article on wakelocks in galaxy nexus forums. Power management configs are same as garyd9's I believe, maybe because of our always on data connection. Have to look in /proc/wakelocks
Click to expand...
Click to collapse
chris,
using cpu spy and betterbatterystats app from xda, i was able to trace my wakelocks to mediascanner. so i just killed mediascanner and i got deep sleep back. im not sure though if i had this problem even before i flashed your custom kernel because i never used cpu spy and betterbatterystats on the stock kernel. maybe this helps? i don't get signal drops
chris... i'm currently testing some of the script for init.d on this thread...
http://forum.xda-developers.com/showthread.php?t=1353903
chrisrotolo said:
I found the archive article on wakelocks in galaxy nexus forums. Power management configs are same as garyd9's I believe, maybe because of our always on data connection. Have to look in /proc/wakelocks
Click to expand...
Click to collapse
im always on wifi, barely use my data plan. but i do have wakelocks draining the battery. i also noticed once that my screen didn't time out, screen was on all the time when i left my tablet, so battery drained quite quickly. i think someone has reported this also. i'll do more observation.
Using Stock 4.3 ROM from here,
http://forum.xda-developers.com/showthread.php?t=2591895
After a fresh install, wipe /data, wipe /cache, wipe /dalvik cache - I tried a full device encryption. I get a picture of a green Android but nothing happens. As I read, the device should reboot and start the encryption process. However, mine never reboots.
I checked logcat and it has some interesting messages,
I/MountService( 872): encrypting storage...
I/power ( 872): *** release_dvfs_lock : lockType : 1
D/SSRMv2:CustomFrequencyManagerService( 872): releaseDVFSLockLocked : Getting Lock type frm List : DVFS_MIN_LIMIT frequency : 1188000 uid : 1000 pid : 872 tag : [email protected]
D/lights ( 872): button : 0 +
D/lights ( 872): button : 0 -
D/qdutils ( 321): getuiClearRegion:70 wormRect( l = 0 t = 0 r = 720 b = 50)
D/qdutils ( 321): getuiClearRegion:76 FinalwormRect( l = 0 t = 0 r = 720 b = 50)
E/SMD ( 346): DCD ON
I/SecureStorage(12345): [INFO]: Secure Storage Daemon is preparing to run
I/SecureStorage(12345): [INFO]: Secure Storage Daemon successfully binded a socket
D/QSEECOMAPI: (12345): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (12345): App is not loaded in QSEE
E/QSEECOMAPI: (12345): Error::Load image request failed ret = -1, errno = 14
E/QSEECOMAPI: (12345): Error::Loading image failed with ret = -1
D/QSEECOMAPI: (12345): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (12345): App is not loaded in QSEE
E/QSEECOMAPI: (12345): Error::Cannot open the file /firmware/image//sec_storage.mdt
E/QSEECOMAPI: (12345): Error::Loading image failed with ret = -1
E/SecureStorage(12345): [ERROR]:Loading app sec_stor and sec_storage failed
E/SecureStorage(12345): [ERROR]:Fail to open session with qualcomm
E/SecureStorage(12345): [ERROR]:Error cannot connect to TA/driver!
Click to expand...
Click to collapse
Any ideas?
ccoager said:
Using Stock 4.3 ROM from here,
http://forum.xda-developers.com/showthread.php?t=2591895
After a fresh install, wipe /data, wipe /cache, wipe /dalvik cache - I tried a full device encryption. I get a picture of a green Android but nothing happens. As I read, the device should reboot and start the encryption process. However, mine never reboots.
I checked logcat and it has some interesting messages,
Any ideas?
Click to expand...
Click to collapse
My recommendation? DON'T DO ENCRYPTION!! you may get your phone in a lockmode and unable to recover data..
Is there anything else that could be causing this?
I have not chosen device encryption and I am also seeing these messages in logcat..
I/SecureStorage(15360): [INFO]: Secure Storage Daemon is preparing to run
I/SecureStorage(15360): [INFO]: Secure Storage Daemon successfully binded a socket
D/QSEECOMAPI: (15360): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (15360): App is not loaded in QSEE
E/QSEECOMAPI: (15360): Error::Cannot open the file /firmware/image//sec_stor.mdt
E/QSEECOMAPI: (15360): Error::Loading image failed with ret = -1
D/QSEECOMAPI: (15360): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (15360): App is not loaded in QSEE
E/QSEECOMAPI: (15360): Error::Cannot open the file /firmware/image//sec_storage.mdt
E/QSEECOMAPI: (15360): Error::Loading image failed with ret = -1
E/SecureStorage(15360): [ERROR]:Loading app sec_stor and sec_storage failed
E/SecureStorage(15360): [ERROR]:Fail to open session with qualcomm
E/SecureStorage(15360): [ERROR]:Error cannot connect to TA/driver!
E/SMD ( 213): DCD ON
Same Problem
I am getting the same thing and when I rooted my SCH-r530u I disabled the Knox thing
02-20 22:57:11.660: I/SecureStorage(10292): [INFO]: Secure Storage Daemon is preparing to run
02-20 22:57:11.660: I/SecureStorage(10292): [INFO]: Secure Storage Daemon successfully binded a socket
02-20 22:57:11.660: D/QSEECOMAPI10292): QSEECom_start_app sb_length = 0x19a040
02-20 22:57:11.660: D/QSEECOMAPI10292): App is not loaded in QSEE
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Cannot open the file /firmware/image//sec_stor.mdt
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Loading image failed with ret = -1
02-20 22:57:11.660: D/QSEECOMAPI10292): QSEECom_start_app sb_length = 0x19a040
02-20 22:57:11.660: D/QSEECOMAPI10292): App is not loaded in QSEE
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Cannot open the file /firmware/image//sec_storage.mdt
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Loading image failed with ret = -1
02-20 22:57:11.660: E/SecureStorage(10292): [ERROR]:Loading app sec_stor and sec_storage failed
02-20 22:57:11.660: E/SecureStorage(10292): [ERROR]:Fail to open session with qualcomm
02-20 22:57:11.660: E/SecureStorage(10292): [ERROR]:Error cannot connect to TA/driver!
02-20 22:57:12.161: V/AlarmManager(411): waitForAlarm result :8
Click to expand...
Click to collapse
What does it mean? I keep getting it every few seconds while the screen is on
* I was going to edit out the sad faces but its too funny cause it fits the situation perfectly*
All of a sudden, on Stock + Root TF700T, WiFi won't turn on. I highly doubt that this is related to my WiFi router ... the WiFi won't even enable on the tablet, and I can't even see a MAC address in About Tablet section.
I also did some digging and have some additional detail, but I cannot find a solution.
logcat:
Code:
E/WifiHW ( 122): Failed to open wlan fw path param (No such file or directory)
E/SoftapController( 122): Softap fwReload - failed: -1
E/WifiStateMachine( 489): Failed to reload STA firmware java.lang.IllegalStateException: command '43 softap fwreload wlan0 STA' failed with '400 43 Softap operation failed (No such file or directory)'
W/CommandListener( 122): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 122): Setting iface cfg
E/WifiStateMachine( 489): Unable to change interface settings: java.lang.IllegalStateException: command '45 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 45 Failed to set address (No such device)'
E/WifiHW ( 489): wpa_ctrl_open fail, retry again
I/wpa_supplicant( 2767): Successfully initialized wpa_supplicant
E/wpa_supplicant( 2767): nl80211: Could not add multicast membership for scan events: -2 (No such file or directory)
E/wpa_supplicant( 2767): Failed to initialize driver 'nl80211'
E/wpa_supplicant( 2767): wlan0: Unsupported driver 'nl80211'
D/dalvikvm( 1258): GC_CONCURRENT freed 427K, 14% free 3700K/4272K, paused 3ms+3ms, total 57ms
D/AsusBrightnessManager( 489): br transform : 35 -> 13
D/DockManagerService( 489): mLastAcOnline:false mAcOnline:false
D/LowBatteryService( 1487): onReceive:Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000010 (has extras) }
D/LowBatteryService( 1487): mAcOnline = false, mDeviceBatteryLevel = 96, mDockBatteryLevel = 0, mDockBatteryStatus = 0
D/LowBatteryService( 1487): Battery level is higher than threshold, no need to apply
D/LowBatteryService( 1487): Battery level is good, no need to apply low battery config.
D/DockManagerService( 489): mLastAcOnline:false mAcOnline:false
D/LowBatteryService( 1487): onReceive:Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000010 (has extras) }
D/LowBatteryService( 1487): mAcOnline = false, mDeviceBatteryLevel = 96, mDockBatteryLevel = 0, mDockBatteryStatus = 0
D/LowBatteryService( 1487): Battery level is higher than threshold, no need to apply
D/LowBatteryService( 1487): Battery level is good, no need to apply low battery config.
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 122): Failed to open wlan fw path param (No such file or directory)
E/SoftapController( 122): Softap fwReload - failed: -1
E/WifiStateMachine( 489): Failed to reload STA firmware java.lang.IllegalStateException: command '46 softap fwreload wlan0 STA' failed with '400 46 Softap operation failed (No such file or directory)'
E/WifiStateMachine( 489): Failed 6 times to start supplicant, unload driver
W/CommandListener( 122): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 122): Setting iface cfg
E/WifiStateMachine( 489): Unable to change interface settings: java.lang.IllegalStateException: command '48 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 48 Failed to set address (No such device)'
E/WifiHW ( 489): wpa_ctrl_open fail, retry again
I/wpa_supplicant( 2792): Successfully initialized wpa_supplicant
E/wpa_supplicant( 2792): nl80211: Could not add multicast membership for scan events: -2 (No such file or directory)
E/wpa_supplicant( 2792): Failed to initialize driver 'nl80211'
E/wpa_supplicant( 2792): wlan0: Unsupported driver 'nl80211'
D/dalvikvm( 1258): GC_CONCURRENT freed 427K, 14% free 3700K/4272K, paused 2ms+1ms, total 22ms
W/NvCpuClient( 489): Failed to bind to service
D/AsusBrightnessManager( 489): br transform : 35 -> 13
E/WifiHW ( 489): Supplicant not running, cannot connect
W/NvCpuClient( 489): Failed to bind to service
Also, output from netcfg:
Code:
[email protected]:/ # netcfg
lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
dummy0 DOWN 0.0.0.0/0 0x00000082 76:ad:93:6b:c9:b7
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
And here is output of my wpa_supplicant.conf:
Code:
[email protected]:/ # cat /etc/wifi/wpa_supplicant.conf
update_config=1
ctrl_interface=wlan0
eapol_version=1
ap_scan=1
fast_reauth=1
And I searched the entire filesystem for "nl80211" and found nothing.
Does anyone have suggestions on where to go next? Did my driver somehow get deleted, or am I just not looking for the right thing?
Thanks.
I will use this question in the future as an example of how to ask for support properly. Unfortunately I don't have a solution for you, but you could check the files in your /data/misc/wifi, maybe you can find something unusual. Your MAC address should come from some file on the FAT filesystem on /dev/block/mmcblk0p5 - I'd recommend making an image of it as a backup and then analyze the image.
_that said:
I will use this question in the future as an example of how to ask for support properly.
Click to expand...
Click to collapse
I provide Enterprise-level support to software devs working in the Cloud and particularly on CentOS/RHEL Linux servers. This is why I know how to ask for help properly.
Well, since I can't find much, and there aren't any definitive answers here, my next thoughts are:
1) Something is seriously jacked up on the filesystem, possibly corrupted driver, possibly something worse. Hopefully, this is the case, because a software problem is possible to fix.
2) The WiFi radio is permanently damaged, or "burnt out".
In the hopes that it's something more like software, I'm going to reimage. I just need to decide what ROM to use. Not having network connectivity will make the prep for this a bit more challenging, but I can work through it using a MicroSD card.
If it's #2, well then I suppose I will have wasted my time reimaging and will be on the market for a new tablet ... and I need to get on that right away because I need to travel soon. Any suggestions are welcome ... I'd like a 9" or 10" tablet and it must have an HDMI out (micro preferred) and be able to handle 1080p video.
Thanks.
[SOLVED]
I am having a heckuva time even doing what I described above.
-I had never unlocked the bootloader before, so when I tried the ASUS unlock util v8, it gave error "INSTALL_FAILED_SHARED_USER_INCOMPATIBLE"
-I tried the ASUS unlock tool v7, and was finally able to install it but when I run and select Unlock I get an error that there is no network connection (FFS that's what I'm trying to resolve!)
-I can't get into recovery, I just get the Android guy with "ERROR!" when I enter fastboot and select "RCK".
My only option is to go back to Stock. So, I tried this:
http://forum.xda-developers.com/showthread.php?t=1833212
The steps in that post result in the same Android guy with the "ERROR!" screen ... not a very helpful error msg.
So, I tried this, and used the stock firmware from ASUS. (NOTE: I downloaded "ASUS Transformer Pad TF700T Firmware: V10.6.1.14.10 Only for US SKU (Android 4.2.1)" directly from ASUS after I read their notes on where to check for which one you need ([Settings]-->[About tablet]-->Build number).):
http://www.transformerforums.com/fo...e-firmware-tf700-tf701-tf300-tf101-tf201.html
From that post ^^ I did Method B: Flash from MicroSD. I extracted the .zip I downloaded from ASUS, and renamed the new zip EP201_768_SDUPDATE.zip per the GUIDE linked above.
I put in my MicroSD, went back into fastboot, and selected "RCK". It was at this point that I began typing the above. Total time to get to this point was about 90 minutes!
-----
FINALLY, for the first time, I saw a progress bar under the Android guy, and he had gears turning in his belly.
*INSERT SIGH OF RELIEF HERE*
As I was typing out all the above, progress bars were moving, and a few reboots happened. I expected that I would be fully back on Stock ROM, and that my data would have been wiped. I never ran a data wipe, I just assumed the ASUS installer would do that by default.
Well, it didn't wipe data. But, what it did do: restore all my device drivers!! After about 10 minutes, and 2-3 reboots, Android loaded with my existing desktop and settings, and the WiFi connected right away!!
So, this fixed it. I documented the above so anyone (even me, months from now) having a similar problem might be able to use these steps.
WOO HOO!
lost root
I should add that I lost root now. I think at this point, after all I've been through with this, I'm just going to press on and install CyanogenMod which is what I was planning to do anyway.
CaptainRewind said:
I should add that I lost root now. I think at this point, after all I've been through with this, I'm just going to press on and install CyanogenMod which is what I was planning to do anyway.
Click to expand...
Click to collapse
Just flash this to get root
http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
sbdags said:
Just flash this to get root
http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Click to expand...
Click to collapse
Yep, I had to do that anyway because I wanted to do a full Titanium Backup first. Still, I'm moving to CM now.