yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] Mormy:
When I tried turn wifi on, yesterday, I've got a MAC address.

But when I turn it off, Android frozen I need to soft reset to get rid of it.
[Touch Cruise Android Development] bally3:
in irc room now with newbie16 trying to get it working :)

feel free to drop in and have a go.. lots to learn!
[Touch Cruise Android Development] cbandarrinha:
bally3, here they are:

rootfs-2009-08-18.zip from here

zImage-18-08-09 from here

mssmisonsystem.img from here

I hope this is what you were asking for.
[Touch Cruise Android Development] bally3:
Thanks cb :)

seem pretty standard to me.
[Touch Cruise Android Development] imfloflo:
Ok so now we must use the mssmisonsystem.img and not the nkhero system.img for testing?
[Touch Cruise Android Development] bally3:
For the testers I recommend the last nkhero - its used by both our Polaris developers, its fast has auto-apn setup and is multilingual.

Its trouble-free and stable as its going to get at the moment so perfect for kernel development.

Thanks to the guys who popped in and helped last night btw :)
[Touch Cruise Android Development] radem205:
Great job Bally! But something else, is there any progress on the audio problem during incoming calls? I know we have to first dial a number to let it work, but it would be great when we don't have to do that anymore.

Thanks to all the developers (and Bally offcourse!)
[Touch Cruise Android Development] imfloflo:
And if you make a call under WM before launching haret is it good? cause at the beginning that was the solution to have call working.
[Touch Cruise Android Development] bally3:
tiwlan0 Link encap:Ethernet HWaddr 00:18:41:78:32:1F
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)

This is what I get when I type: ifconfig -a in adb shell with nkkero and the latest rootfs and zimage with nkhero.

Can someone post up their ifconfig -a results from last nights files that we updated with newbie16's wlan.ko please? I messed mine up thinking a fresh data image might help but now it doesnt connect to wifi on that build anymore.

thanks.
[Touch Cruise Android Development] bally3:
I assume that with addisu's wlan.ko its using the kaiser firmware.

Last night newbie put the polaris firmware in the new one so it should be interesting to see whether that produces different results.
[Touch Cruise Android Development] Softec:
tiwlan0

tiwlan0 Link encap:Ethernet HWaddr 00:18:41:3D:6C:06

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)

i don't see this MAC Address in advances settings, whi?
[Touch Cruise Android Development] bally3:
You need to run adb shell and type: ifconfig -a in there.

Actually in settings I dont see a MAC address either though ifconfig -a shows one.

Are we looking at the right address - anyone?
[Touch Cruise Android Development] bally3:
its definately the right mac address - just checked it in Windows and its the same address.

softec, thanks for the result.. so in the one from last night we also have a mac address in ifconfig -a but none in settings... interesting.. that means that the firmware file hasnt shown to do anything different so far.
[Touch Cruise Android Development] bally3:
I/SystemServer( 136): Starting NetStat Service.
I/SystemServer( 136): Starting Connectivity Service.
I/WifiService( 136): WifiService starting up with Wi-Fi enabled
D/wlan_loader( 181): adapter tiwlan0, eeprom /sdcard/calibration, init /etc/wifi/tiwlan.ini, firmware /etc/wifi/Fw1251r1c.bin
D/wlan_loader( 181): Configuring adapter
D/wlan_loader( 181): Adapter tiwlan0 configuration rc = 0
D/wlan_loader( 181): Starting configMge
D/wlan_loader( 181): ConfigMge start rc = 0
D/wlan_loader( 181): Driver configured
D/wlan_loader( 181): Firmware loaded and running OK
D/wlan_loader( 181): Set property wlan.driver.status = ok - Ok

This is what logcat gives me.. everything looks fine according to what newbie16 and addisu wrote on the kaiser wifi thread, so why wont it work!?! :confused:
[Touch Cruise Android Development] bally3:
hmm.. found this line a bit below that last bit I posted in the logcat:

D/WifiHW ( 136): 'DRIVER RSSI' command timed out.
[Touch Cruise Android Development] zy2zyy:
i wanna give some help, could tell me how to connect my polaris with computer via usb? my os is vista sp2 ultimate.
[Touch Cruise Android Development] bally3:
I did a debuglog and its had this addition in it:

V/WifiMonitor( 136): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2]
V/WifiStateTracker( 136): Connection to supplicant established, state=DISCONNECTED
V/WifiStateTracker( 136): Changing supplicant state: DISCONNECTED ==> SCANNING

and this is when I changed the network notification to disable/enable:

D/SettingsWifiEnabler( 422): Received wifi state changed from Enabling to Enabled
I/ActivityManager( 136): Displayed activity com.android.settings/.WirelessSettings: 1360 ms
I/ActivityManager( 136): Starting activity: Intent { action=android.intent.action.MAIN comp={com.android.settings/com.android.settings.wifi.WifiSettings} }
D/SettingsWifiEnabler( 422): Received wifi state changed from Enabling to Enabled
I/ActivityManager( 136): Displayed activity com.android.settings/.wifi.WifiSettings: 1999 ms
[Touch Cruise Android Development] bally3:
disable all firewalls, make sure activesync is connected in WinMo and then hit haret.

After boot, go to your adb folder (it should be c:\adb ideally)

type: adb shell

if you get a # then you're root in the device.. simple!
[Touch Cruise Android Development] zy2zyy:
ok, quite simple, i can do this.

and i notice that when i turn on wifi, the back of my phone becomes hot just as it does in WinMo, i think the wifi device is working! :p
[Touch Cruise Android Development] bally3:
Can you test this for me please softec?

In Android, Put your phone in Airplane Mode. give it a minute or so to calm down and then back off Airplane Mode, (you can do this either by holding the power button to bring up the menu or in Settings).

Check Wifi - mine says "unable to start".

If you know how to log and pastebin then you can do:
[Touch Cruise Android Development] zy2zyy:
@bally3, i've done the connection thing! there is nothing different to u.

and after i turn on wifi, my phoned dies when i turn airplane on or turn wifi off.

any thing u want? i'll post here.
[Touch Cruise Android Development] bally3:
thats fine thanks, it looks like its doing the same thing. I'll do a log and post it up for Newbie16 to look at.

But you're right, its getting warm so its working.. and the logs show is loading and we have a MAC address.. its falling over somewhere and I've been reading the wifi thread to see whether they had the same on the kaiser and what they did.
[Touch Cruise Android Development] imfloflo:
Apparantly @dzo is working on the bluetooth and success to make it working for vogue.

So soon for polaris too :p
[Touch Cruise Android Development] bally3:
only if we get those donations up.. !

We've raised about $120 so far, we need to raise at least $200 - we get that raised and its bluetooth and camera city for us. With wifi almost done, we're almost close to seeing that flashable rom.

Lets keep going and get those donations in - dzo is due to come to the UK soon so we can save on the postage as well if we get the donations in quick enough! :)
[Touch Cruise Android Development] w04g005:
Whats up with vilord? Is he on vacation? He hasn't posted here for a long time. Maybe he can help with Wifi?! If not, what is he working on?

greetings
[Touch Cruise Android Development] Softec:
freeze

Hi Bally3,

airplane Mode freeze my phone :(
[Touch Cruise Android Development] Mormy:
Hi, Bally. I'm just come back from work. I read the last news but I don't understand where/when I must type iconfig -a

Is it a win command?? Because my vista doesn't recognize it :(

Remember that I had MAC address BEFORE the wifi.ko, now I have "unable to start wifi"
[Touch Cruise Android Development] bally3:
Dont worry.. it does mine too. We'll have to get a log to life02 about it.

Yes mine disappeared too after a reboot, dont worry.. it was only a test anyway.

type ifconfig -a in adb shell on your pc with android connected.
[Touch Cruise Android Development] Mormy:
My fault, I wrong typed the command :(

The result is:

dummy0 Link encap:Ethernet HWaddr 3A:CF:6E:BD:AF:16
BROADCAST NOARP 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:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:360 errors:0 dropped:0 overruns:0 frame:0
TX packets:360 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:27776 (27.1 KiB) TX bytes:27776 (27.1 KiB)

usb0 Link encap:Ethernet HWaddr 86:DE:D8:A6:41:1D
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:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

And I just discover that my sms don't start anymore :(

Could I fresh install again or do you want more info??
[Touch Cruise Android Development] briggs81:
lol maybe he wants a break, relax :P
[Touch Cruise Android Development] iseeka:
tried rootfs-20-08-09.img and zImage-20-08-09 and as espected

no wifi no bluetooth
[Touch Cruise Android Development] bally3:
no its fine.. go for it.. I just tested sms and it works fine on mine.
[Touch Cruise Android Development] Leryan:
Hey, bally3, can you test SMS delivery reports.

Previously they didn't worked for me. (My Polaris need some repairs, so I am 2 weeks with out the phone :(:(:(:(:( )
[Touch Cruise Android Development] Mormy:
Just formatted the sd and install with zimage and rootfs 20-08:

Turned on wifi, under information this is my MAC address:00:18:41:4e:e9:99

After I reboot the phone in order to be visible to the pc, android says that wifi is on, but no MAC under status menu.

So I turn it off, wait a couple of second and turn it on:

tiwlan0 Link encap:Ethernet HWaddr 00:18:41:4E:E9:99

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)

That's the result

Edit: Now sms works :)
[Touch Cruise Android Development] bally3:
According to newbie16, the firmware files for the Polaris and Kaiser are different.

The rootfs included in google code is likely to have the kaiser firmware with it and we clearly need to have one with ours.

Newbie16 spotted that in the logs yesterday with his rootfs with polaris firmware. it wasn't complaining when making the reads or writes and it still failed, which means something else is wrong.

I would suspend any more tests with the current rootfs (unless you happen to be a dev then go for it!. It it likely another rootfs file will be released with the changes for Polaris when they have been made.
[Touch Cruise Android Development] bally3:
If you want to have a play with the polaris firmware included rootfs, the files are here:

http://drop.io/wifitest/asset/28-export-zip
[Touch Cruise Android Development] iseeka:
is it necessary Android folder or it was just for testing procedures?
[Touch Cruise Android Development] meknb:
Wifi looks very promising now cant wait to try it out "working away till tomorrow with no computer" looks like i missed alot this week. I read somewhere you could hard code your ap in wpa_supplicant.conf i think this does the scanning and stores results it might be under /data/misc/wifi ?? mount -o remount,rw / should make it writable if its a problem writing to it,i'll try and find the post.Also how is tiwlan0 being created is it via ifup tiwlan0 should create /etc/network/interfaces or ifconfig tiwlan0 up. does this creat a interfaces file?

Are we using the firmware from windows or a dump from android?
[Touch Cruise Android Development] bally3:
to push wlan.ko file:

adb shell mount -o remount,rw /

adb push wlan.ko /initetc/wifi/wlan.ko

adb shell sync

then reboot the phone.

----------------------------------------------------

Another way:

mkdir -p /lib/modules/`uname -r`/

adb psuh wlan.ko /lib/modules/`uname -r`/

rmmod wlan

ismod /lib/modules/`uname -r`/wlan.ko

then try starting wifi
[Touch Cruise Android Development] bally3:
http://www.aptedit.com/download/adsetup.zip

for comparing hex files.. needed to compare the calibration files
[Touch Cruise Android Development] bally3:
For my reference only:

drop.io/polarkaiser2

put all files in root of sd card.

All thanks to Newbie16.. damn lot of effort on his part.

right...I'm off to bed.. its been a LONG day...
[Touch Cruise Android Development] imfloflo:
@Bally3 Huum sounds good

BTW is somebody try the lastest dzo release to make BT working apparently this is the same chips?
[Touch Cruise Android Development] bally3:
I'll have a go this weekend and let you know.

Ignore the posted files and links, they are for devs only.

RE: tiwlan0, you're probably better asking life02 or Newbie16, its beyond me a little.

RE: firmware, its from windows. the kaiser has its own firmware as does the polaris. Newbie16 created a rootfs for us with our firmware in it to test, this is what we're currently working on.

Meknb, you seem to know enough about this for us to make progress, I propose tonight, me you and newbie16 get together and do some serious dev on this. We're all in the UK so we can arrange a convenient time.

I'll be home from 5pm UK time and available all evening and can even do a late night to get this sorted.

Let me know if you can make it and I'll speak to Newbie16 about it. We need to ease off on these guys and take some of the pressure away as they are not Polaris owners and its frustrating work for them to have to do something, send it to us, get the result and then try something where they could have done it in far less time if they had the device there, though they never once complain about it.

Newbie16 and Addisu have both supported us greatly and there efforts are well appreciated.
[Touch Cruise Android Development] imfloflo:
Question when you speak about firmware, what do you mean exactly?

How can you get this ? is this the spl part?

[Off topic]

Most of Polaris devs are from UK :p

I will come to London for 5 month start my last year at Supinfo university 4november09 :)

I would be honor to have a coffe with you.

[Off topic off]
[Touch Cruise Android Development] majo_scigo:
Hi guys. I am not a dev and you might know it already, but two days ago i tried to load nkhero when i spoke to you guys on irc. Yesterday I updated my radio. With WIFI OFF i started android and I was able to turn on WIFI and it was showing my correct MAC in advanced. I was abla to click SCAN and it was showing scanning but never found anything. I tried to add network manually but device was not happy to save it :(

When I filled in my IP and DNS etc. it was showing connected under WIFI.

LAter I have restarted polaris and turned on WIFI in WM and connected to my network. Then when I started android I was not able to turn the WIFI on at all.
[Touch Cruise Android Development] bally3:
firmware file is in the Windows folder that we extract and use for wifi. Ours (and Kaisers I believe) is called: Fw1251r1c.bin

ps. Life02 is in London, I'm up north so you'll struggle to catch up with me, but you're welcome to come up :)
[Touch Cruise Android Development] imfloflo:
When your are under Android and you thinks it's connected you should test with a soft from your pc if you can see other device in connected in the same network.

With my internet provider i can see all people who are connect on my "box" router.

If your router see your Htc it's maybe good.
[Touch Cruise Android Development] majo_scigo:
I have checked that. Router didn't pick up polaris running android. I only had an wifi icon with changing signal bar, quite weird. Also I left it and went to bad and the battery was dead in the morning. so i believe the device was scanning all night long.
[Touch Cruise Android Development] imfloflo:
For my information : Is it possible with another device (wifi scanner/reader dunno) to show if polaris is scanning the network or if it's just the icon in the top bar and that's all?
[Touch Cruise Android Development] bally3:
Just to update you where we are with wifi:

Newbie16 is creating a rootfs file which links all the wifi files (wpa_supplicant, firmware etc) to the root of the sdcard so we should be able to place any new files in the root and test it.

I need to check a few things:

Firmware file for Polaris is attached, where do the other files come from? tiwlan.ini, wpa_supplicant etc? do they need to be Polaris specific?

Which firmware file is in the rootfs that one we have?
[Touch Cruise Android Development] bally3:
Newbie16 mentioned incompatibility with newer kernel version and that the modules needed to be updated. Need to look at getting that done tonight.
[Touch Cruise Android Development] bally3:
http://xdaforums.com/showpost.php?p=3409143&postcount=3902

This is where the files came from, I remember reading this post a while back.

I propose going back and putting all our files in manually and seeing whether we can make it work using the wifi enabled files that we have.

so the files to use:

nkhero themed

Fw1251r1c.bin - I know this is for Polaris as I took it off my phone.

tiwlan.ini - find the right one (Polaris specific?)

wlan.ko - Newbie16 will supply this as he goes as he makes changes

wpa_supplicant.conf

Calibration file your own.

zimage - newest one if we get all the required modules loaded.

rootfs - latest one (preferably already wifi enabled?)
[Touch Cruise Android Development] bally3:
My current thinking is that we need the new kernel with all the required wifi module(s) loaded and our firmware and retry, get a dmesg and logcat and make sure we still are not getting write errors, which we currently are not.

Overall, no read or write errors, loading and scanning.

Its timing out somewhere and we need to find it, as I posted yesterday and highlighted in bold.
[Touch Cruise Android Development] bally3:
ifconfig tiwlan0 192.168.2.30 netmask 255.255.255.0wlan_loader -f /system/etc/wi
fi/Fw1251r1c.bin -e /proc/calibration -i /system/etc/wifi/tiwlan.ini
===IPC_DeviceIoControl('tiwlan0', cmd=2242612 (SET), data=0x40009008 (0), size=2
02423, sizeRet = 0x0(ffffffff))
===== send_ioctl: socket=7, cmd=35312, &req=0xbec08a9c
===== send_ioctl: req={name='tiwlan0', sub_cmd=2242612, size=202423 (max=4), dat
a=0x40009008
Printing memory dump:
TI_CU:0xbec08a9c: 74 69 77 6c 61 6e 30 00 00 00 00 00 00 00 00 00
TI_CU:0xbec08aac: 34 38 22 00 02 00 00 00 b7 16 03 00 08 90 00 40
===== send_ioctl: res=0, sizeRet=0x0 (ffffffff)
===IPC_DeviceIoControl('tiwlan0', cmd=2242588 (SET), data=0xbec08afc (0x1), size
=4, sizeRet = 0x0(ffffffff))
===== send_ioctl: socket=7, cmd=35312, &req=0xbec08a9c
===== send_ioctl: req={name='tiwlan0', sub_cmd=2242588, size=4 (max=4), data=0x1

Printing memory dump:
TI_CU:0xbec08a9c: 74 69 77 6c 61 6e 30 00 00 00 00 00 00 00 00 00
TI_CU:0xbec08aac: 1c 38 22 00 02 00 00 00 04 00 00 00 01 00 00 00
** IPC_DeviceIoControl() return -1
#
[Touch Cruise Android Development] bally3:
can someone with a win 6.5 rom copy the firmware file Fw1251r1c.bin from their windows directory and post it up please?

if you can make it into irc room please come and let me know.
[Touch Cruise Android Development] majo_scigo:
where do i find it? I copy will post it for you

I have got it.
[Touch Cruise Android Development] majo_scigo:
Here it is. It is from PDAVIAT 6.5

Just rename zip to bin...I couldn't post bin file here
[Touch Cruise Android Development] bally3:
thanks scigo :)
[Touch Cruise Android Development] bally3:
Last night Newbie16 spent from 6pm till 2am in the morning without breaks trying to fix the wifi for a device he doesnt own with a few of our testers.

He has found a repeating read error that he will be investigating (imfloflo can you paste one of the repeating read lines from the kdmesg file please?).

Nothing hits home harder of the frustration and difficulty to the developer when he's working blind for a device when you're there yourself asking dozens of questions and posting logs and testing stuff. I myself felt tiired near the end and had to call it a night (I think Newbie16 may have continued through the night had I not stopped!)

I'd like everyone to, if nothing more, say a little thank you and a prayer for our kaiser friend whose working so hard to help us and showing great spirit and unrelenting patience.

Thanks Newbie16 - you're a star :)
[Touch Cruise Android Development] bally3:
Found the log file again on dropio.

the repeating line is:

Small Read >> addr:63664 count:4

This is also causing the Wifi Settings to crash.
[Touch Cruise Android Development] iseeka:
When i managed to get a log i got that repeating line aswell
[Touch Cruise Android Development] SuperJMN:
Thanks, Newbie16! I hope you work won't be in vain.
[Touch Cruise Android Development] polum:
Awesome developer !!!!!

Thanks Newbie16
[Touch Cruise Android Development] zy2zyy:
thank you very much, Newbie16!
[Touch Cruise Android Development] Mormy:
Thanks a lot to all of you that spend night over night to help us :)
[Touch Cruise Android Development] bally3:
Anyone struggling with connecting to Market and Google, I've found a reliable way to get that first connections:

Go to Settings > Wireless Controls > Mobile Networks

Tick the "Use only 2G networks" box (if you're connected then it will be greyed out so disconnect data first).

Go back and connect.. it should connect and ask you to accept terms and conditions for Market.

Once you've made the connection you can go back and untick the 2G box.

My theory is that Market needs a strong and steady connection when you first connect, the fail message does say that a reliable connection could not be made so it could be the case.

I've tried this a number of times today whilst doing my wifi tests, and its worked each time, most of you wont have this problem, but I have from the start as Three is rubbish and the signal where I am is equally bad on non-three branded phones.
[Touch Cruise Android Development] bally3:
For dev use only
[Touch Cruise Android Development] freddycs:
thanks Newbie16 & bally3! keep up the good work!! :)
[Touch Cruise Android Development] meknb:
I think the Small Read errors are from wifi.settings trying to read the scan results from the buffer,the main problems are the command timeouts from WifiHW which are called by wpa_suplicant.

I've tried altering the wpa_suplicant.conf on how wifi scans but still no joy.

I've also tried kismet to scan for wifi client's while testing it still cant see my polaris.

How can we tell if the interface is created ?

I've tried creating a interface file for ifup and setprop wifi.interface tiwlan0.

Thanks for the great work newbie16 and bally3.
[Touch Cruise Android Development] bally3:
Interesting... we havent looked at the wpa_supplicant yet.

I'm in the polaris dev irc room now if you want to chat about it.
[Touch Cruise Android Development] bally3:
The Polaris firmware does not load.

The Kaiser firmware loads but freezes and does not scan then times out.

Guys, some support would be appreciated. The ones with adb an come into the irc room and do some testing. Newbie16 is doing this almost full-time at the moment and the times when I cant be there, it would be useful if someone else was or we'll lose invaluable dev opportunities.

The testing isnt difficult, take the files and boot android, ruun dmesg and logcat to files and pass them to Newbie16 - simple stuff.

Please dont waste posts by posting that you'd love to help but lack of experience.. if you cant then you cant.

so come on guys,, we all want wifi.. help us out :(
[Touch Cruise Android Development] bally3:
ok.. step by step instructions how to help Newbie16: