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 was just wondering if this stupid Super CID prevent FOTA updates ?
I made capture of the update request to HTC servers:
As you can see Super CID is sent ...
POST /check-in/rws/and-app/update HTTP/1.1
Content-type: application/json
Content-Length: 459
Host: apu-chin.htc.com
Connection: Keep-Alive
User-Agent: AppUpdate-Checkin/2.3
{"timestamp":"-1","openSenseSdk":-1,"apiLevel":"10","checkIn":{"connectMedia":"W","mid":"PH06*****","build":{"serialNo":"SH19HVXXXXXX","mainVersion":"1.54.2","bootLoader":"1.07.0000","cl":"189894","radio":" 47.23.35.3033H_7.51.35.19","romVersion":"1.54.401.2 CL189894 release-keys","sku":"401","key":"R"},"clientVersion":"A2.3","cid":"11111111","checkType":"M","ip":"","mccMnc":"20810"},"locale":"fr_FR","imei":"XXXXXXXXXX","modelNum":"HTC ChaCha A810e"}
Answer from server:
HTTP/1.1 200 OK
Date: Sat, 31 Dec 2011 03:57:08 GMT
Transfer-Encoding: chunked
Content-Type: application/json;charset=UTF-8
X-Powered-By: Servlet/2.5 JSP/2.1
0031
{"overall":{"apkNumber":0,"interval":1209600000}}
0000
Other thing, I have a "cwkeys" file on the root of the file system containing a start address and followed by an array of 2 x 64 int64.
Any idea of what this file is ?
Yes it does. As all S-ON devices have a specific CID for each region/provider/brander, the superCID (111111) prevents OTA updates, as the server will ignore the request and respond with a "wrong CID" message.
Thanks for the answer.
I really wish I can get the original CID in the phone one day.
mike796 said:
Hello,
I was just wondering if this stupid Super CID prevent FOTA updates ?
I made capture of the update request to HTC servers:
As you can see Super CID is sent ...
POST /check-in/rws/and-app/update HTTP/1.1
Content-type: application/json
Content-Length: 459
Host: apu-chin.htc.com
Connection: Keep-Alive
User-Agent: AppUpdate-Checkin/2.3
{"timestamp":"-1","openSenseSdk":-1,"apiLevel":"10","checkIn":{"connectMedia":"W","mid":"PH06*****","build":{"serialNo":"SH19HVXXXXXX","mainVersion":"1.54.2","bootLoader":"1.07.0000","cl":"189894","radio":" 47.23.35.3033H_7.51.35.19","romVersion":"1.54.401.2 CL189894 release-keys","sku":"401","key":"R"},"clientVersion":"A2.3","cid":"11111111","checkType":"M","ip":"","mccMnc":"20810"},"locale":"fr_FR","imei":"XXXXXXXXXX","modelNum":"HTC ChaCha A810e"}
Answer from server:
HTTP/1.1 200 OK
Date: Sat, 31 Dec 2011 03:57:08 GMT
Transfer-Encoding: chunked
Content-Type: application/json;charset=UTF-8
X-Powered-By: Servlet/2.5 JSP/2.1
0031
{"overall":{"apkNumber":0,"interval":1209600000}}
0000
Other thing, I have a "cwkeys" file on the root of the file system containing a start address and followed by an array of 2 x 64 int64.
Any idea of what this file is ?
Click to expand...
Click to collapse
I wonder if its due to the same reason that I cannot update to latest version by OTA.
How did you capture the above data ?
As title ;
I've managed to use the wvdial to dial to the 3G network successfully.
(wvdial is shiped from Botbrew-basil)
The ssh connection , telnet , even the w3m in terminal emulator are working properly.
"ifconfig" shows that ppp0 is up and everything seems to be well-settled.
But unfortunately ...... the system status bar said that "there is no available connection" .
And all the browsers and other applications in GUI failed to connect to the Internet.
So......
Is there anyway to tell the android system that "Hey ! The connection is available !!! " ?
Command line solutions are Okay for me , too.
P.S.PPP widget is not suitable for me because its behavior.
(I'll explain in device background.)
=============================
device background :
I flashed my ASUS TF101g from its stock ROM (Honeycomb)
to the REVOLVER 4 ROM (ICS) , which is available from this thread.
Most of things works fine except that 3G seemed not to be detected by the system.
APN settings and any config toward Mobile Network is not responding.
PPP widget is a solution provided and it works well.
However , my tab also plays a role as an access point for my laptops .
After dialing , PPP widget will "wrap" the connection to be "WIFI",
and the hot-spot sharing function will be forced to shutdown by the system immediately.
The wifi card just cannot serve others while it's acting as a client ......
Here are some logs :
System Information:
Code:
# uname -a
Linux localhost 2.6.39.4 #1 SMP PREEMPT Fri May 25 22:47:02 CST 2012 armv7l GNU/Linux
3G module :
Huawei EM820W
Dial Message:
Code:
# wvdial
--> Ignoring malformed input line: ";[Dialer Defaults]"
--> WvDial: Internet dialer version 1.61
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
OK
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E0 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E0 S0=0 &C1 &D2 +FCLASS=0
OK
--> Sending: AT+CGDCONT=1, "IP","Internet"
OK
--> Modem initialized.
--> Sending: ATDT*99#
--> Waiting for carrier.
CONNECT 21600000
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Sat Nov 23 13:57:23 2013
--> Pid of pppd: 8178
--> Using interface ppp0
--> pppd: �"@��u
--> pppd: �"@��u
--> pppd: �"@��u
--> pppd: �"@��u
--> pppd: �"@��u
--> local IP address 100.81.xxx.xx
--> pppd: �"@��u
--> remote IP address 10.64.64.64
--> pppd: �"@��u
--> primary DNS address 61.31.233.1
--> pppd: �"@��u
--> secondary DNS address 168.95.1.1
--> pppd: �"@��u
^C
Caught signal 2: Attempting to exit gracefully...
--> Terminating on signal 15
--> pppd: �"@��u
--> Connect time 1.0 minutes.
--> pppd: �"@��u
--> pppd: �"@��u
--> pppd: �"@��u
--> Disconnecting at Sat Nov 23 13:58:27 2013
I don't know why there is so escape character , the locale is set to be zh_TW.utf8. I tried us_EN.utf8 and POSIX , the problem remains.
Misery Kernel error log:
Code:
[19706.535004] fxz-option_resume entered
[19706.535299] option_open()+
[19706.536024] Wake28 for irq=326
[19706.536749] option_open()-
[19706.540709] option_close()+
[19706.541428] option_close()-
[19709.007449] fxz-option_suspend entered
[19709.008544] option: option_instat_callback: error -2
[19709.008917] fxz-option_suspend entered
[19709.009278] fxz-option_suspend entered
[19709.009936] fxz-option_suspend entered
[19709.010310] fxz-option_suspend entered
[19709.010677] fxz-option_suspend entered
[19709.011732] option: option_instat_callback: error -2
[19709.554349] usb_wwan: version magic '2.6.36.3-00005-g5dff38c SMP preempt mod_unload ARMv7 ' should be '2.6.39.4 SMP preempt mod_unload ARMv7 '
[19709.556632] usb_wwan: Unknown symbol _test_and_set_bit_le (err 0)
[19709.557757] usb_wwan: Unknown symbol _clear_bit_le (err 0)
[19709.564941] option: version magic '2.6.36.3-00005-g5dff38c SMP preempt mod_unload ARMv7 ' should be '2.6.39.4 SMP preempt mod_unload ARMv7 '
[19709.569786] option: module is already loaded
Wondering if anyone else is having this problem:
Prior to NMJ20D i was able to connect to my home VPN hosted by an asus ac88. After the NMJ20D update if i try to connect with my PH-1 - the VPN server will exit with a fatal errror.
I'm on an Asus RT-AC88U with the latest firmware (3.0.0.4.382_15850)
VPN server log (some of the info has been sanitized)
Nov 2 22:37:13 ac88.mydomain.com vpnserver1[19230]: 10.10.10.1:56664 TLS: Initial packet from [AF_INET]10.10.10.1:56664 (via [AF_INET]192.168.1.3%eth0), sid=92a320aa c9bea163
Nov 2 22:37:14 ac88.mydomain.com vpnserver1[19230]: 10.10.10.1:56664 VERIFY OK: depth=1, C=TW, ST=TW, L=Taipei, O=ASUS, CN=RT-AC88U, [email protected]
Nov 2 22:37:14 ac88.mydomain.com vpnserver1[19230]: 10.10.10.1:56664 VERIFY OK: depth=0, C=TW, ST=TW, L=Taipei, O=ASUS, CN=client, [email protected]
Nov 2 22:37:15 ac88.mydomain.com vpnserver1[19230]: 10.10.10.1:56664 Assertion failed at ssl.c:2005
Nov 2 22:37:15 ac88.mydomain.com vpnserver1[19230]: 10.10.10.1:56664 Exiting due to fatal error
Nov 2 22:37:15 ac88.mydomain.com vpnserver1[19230]: 10.10.10.1:56664 /sbin/route del -net 10.8.0.0 netmask 255.255.255.0
Nov 2 22:37:15 ac88.mydomain.com vpnserver1[19230]: 10.10.10.1:56664 Closing TUN/TAP interface
Nov 2 22:37:15 ac88.mydomain.com vpnserver1[19230]: 10.10.10.1:56664 /sbin/ifconfig tun21 0.0.0.0
Note - If I restart the VPN server there are no problems to connect with another device (OnePlus One)
Nov 2 22:53:01 ac88.mydomain.com vpnserver1[19668]: 10.10.10.1:34310 TLS: Initial packet from [AF_INET]10.10.10.1:34310 (via [AF_INET]192.168.1.3%eth0), sid=14cae885 ba9bedbd
Nov 2 22:53:02 ac88.mydomain.com vpnserver1[19668]: 10.10.10.1:34310 VERIFY OK: depth=1, C=TW, ST=TW, L=Taipei, O=ASUS, CN=RT-AC88U, [email protected]
Nov 2 22:53:02 ac88.mydomain.com vpnserver1[19668]: 10.10.10.1:34310 VERIFY OK: depth=0, C=TW, ST=TW, L=Taipei, O=ASUS, CN=client, [email protected]
Nov 2 22:53:02 ac88.mydomain.com vpnserver1[19668]: 10.10.10.1:34310 PLUGIN_CALL: POST /usr/lib/openvpn-plugin-auth-pam.so/PLUGIN_AUTH_USER_PASS_VERIFY status=0
Nov 2 22:53:02 ac88.mydomain.com vpnserver1[19668]: 10.10.10.1:34310 TLS: Username/Password authentication succeeded for username 'sanitized'
Nov 2 22:53:02 ac88.mydomain.com vpnserver1[19668]: 10.10.10.1:34310 Data Channel Encrypt: Cipher 'XX-XXX' initialized with 128 bit key
Nov 2 22:53:02 ac88.mydomain.com vpnserver1[19668]: 10.10.10.1:34310 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Nov 2 22:53:02 ac88.mydomain.com vpnserver1[19668]: 10.10.10.1:34310 Data Channel Decrypt: Cipher 'XX-XXX' initialized with 128 bit key
Nov 2 22:53:02 ac88.mydomain.com vpnserver1[19668]: 10.10.10.1:34310 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Nov 2 22:53:02 ac88.mydomain.com vpnserver1[19668]: 10.10.10.1:34310 Control Channel: TLSv1, cipher TLSv1/SSLv3 XXX-XXX-XXX-XXX-SHA, 1024 bit RSA
Nov 2 22:53:02 ac88.mydomain.com vpnserver1[19668]: 10.10.10.1:34310 [client] Peer Connection Initiated with [AF_INET]10.10.10.1:34310 (via [AF_INET]192.168.1.3%eth0)