yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] bally3:
dmesg | grep -i wlan only gives me the same back in adb shell

the new build doesnt seem to want to give me su on the phone.

I get this in dmesg if I hit wifi in settings:

[ 624.008393] wlan: version magic '2.6.25-01843-gfea26b0 preempt mod_unload ARMv6 ' should be '2.6.25-00852-g534f7a9 preempt mod_unload ARM
v6 '
[ 624.030779] select 272 (app_process), adj 14, size 3635, to kill
[ 624.030859] send sigkill to 272 (app_process), adj 14, size 3635
[ 624.091763] TIWLAN: Driver loading
[ 624.092139] Headset status change 1
[ 624.305746] trout_wifi_power: 1
[ 624.305811] trout_wifi_reset: 0
[ 624.357191] trout_wifi_set_carddetect: 1
[ 624.357244] trout_wifi_set_carddetect: Nobody to notify
[ 625.030835] ds2746: 4065mV 498mA charge: 81/100 (3539 units)
[ 625.030860] aux0: 236 (1299) aux1: 68 (341)
[ 625.030935] HTC Polaris: USB cable detected
[ 625.030980] msm_hsusb_set_vbus_state(1)
[ 625.033425] battery_charging_ctrl 1
[ 628.420553] tiwlan_module_init: Timed out waiting for device detect
[ 628.420950] trout_wifi_set_carddetect: 0
[ 628.420995] trout_wifi_set_carddetect: Nobody to notify
[ 628.421030] trout_wifi_reset: 1
[ 628.575963] Headset status change 0
[ 628.683921] trout_wifi_power: 0
# # #
#
[Touch Cruise Android Development] bally3:
Life02 worked on this last night with dzo so either one of them should know.
[Touch Cruise Android Development] bally3:
anyone else having issues getting su on the new build? this doing my nut! :confused:

going back to previous build to see whats changed.
[Touch Cruise Android Development] life02:
While I was testing the wifi I was using the kaiser wifi build from here: http://drop.io/wifikaiser

I was using my on zImage from here: http://code.google.com/p/vogue-android/downloads/detail?name=zImage&can=1&q=&sort=-uploaded

I am able to get su.
[Touch Cruise Android Development] life02:
I am using the patched wlan.ko and system.img from the kaiser wifi page.

I am using my own zImage.

I used ./wlan_loader -f /system/etc/wifi/Fw1251r1c.bin -e /sdcard/calibration -i /system/etc/wifi/tiwlan.ini

Fw1251r1c.bin and tiwlan.ini are not on my sdcard.. they are in the system.img right?

/sdcard # dmesg | grep -i wlan

dmesg | grep -i wlan

[ 144.429861] wlan: version magic '2.6.25-01843-gfea26b0 preempt mod_unload ARMv6 ' should be '2.6.25-00852-g534f7a9-dirty preempt mod_unload ARMv6 '

[ 146.604147] wlan: version magic '2.6.25-01843-gfea26b0 preempt mod_unload ARMv6 ' should be '2.6.25-00852-g534f7a9-dirty preempt mod_unload ARMv6 '

/sdcard #
[Touch Cruise Android Development] meknb:
I've tried with the kaiser files from my sd card still same error.

ifconfig -a shows the tiwlan0 device with no mac address.ifconfig tiwlan0 up gives me ifconfig: SIOCSIFFLAGS: Cannot assign requested address.

im using a build from the latest git and no probs with su.
[Touch Cruise Android Development] life02:
ditto.... lunch time over... back to work... I'll look at it more tonight
[Touch Cruise Android Development] smaaland:
I seem to still just get a strange multicolored screen every time I launch haret. I heard about a lot of people having the same problem, but was there ever a solution for it? It happens _almost_ every time. Any ideas?
[Touch Cruise Android Development] Septavius:
Just a little update.

It's the "IPC_DeviceIoControl" call in "tiwlan_loader.c" that fails. Tracing this call it's actually the call to "ioctl" in "ipc_user.c" ("IPC_DeviceIoControl") that returns "-1".

Unfortunately the errno from the call isn't returned in the debug information, so we need add a line to tiwlan_loader.c like "print_debug("Errno = %d\n", errno);" or something. Then we should get a clue to why the "ioctl" call fails.
[Touch Cruise Android Development] meknb:
if you use the wlan_loader from the kaiser forum i think theres one with a debug ?

well it creates a wifidbg file in the proc folder.
[Touch Cruise Android Development] bally3:
Guess we'll have to wait for life02 to get home.
[Touch Cruise Android Development] life02:
The file is there but it is blank.
[Touch Cruise Android Development] Mormy:
I tried the latest pack "android-1.5-2009-08-04.zip" with "system-nkhero-2009-08-04.img" and Life02 "zImage-polaris-vsync":

I set the APN inside android and I have data connection without modem :)

But still I can't send sms :(
[Touch Cruise Android Development] bally3:
I'm using the kaiser wifi initrd, it wont have the vsync fix dont think, but sms works.

I take it we didnt have any movement with the wifi last night? oh well..another day.. another eager awaitng.. :)
[Touch Cruise Android Development] SuperJMN:
Will we have the option to flash Android instead of running on top of WM with haret?
[Touch Cruise Android Development] briggs81:
Sure, one day.
[Touch Cruise Android Development] Michel82:
I woke up early this morning. All excited about what progress would've been made in the wifi department in the opposite timezones. First thing i did was refreshing this page, but trusting on the few messages over here it seems like it's not working yet.

I guess it'll be another night dreaming of wifi since we don't have any driver skilled xda devs over here in CET.
[Touch Cruise Android Development] bally3:
yup.. hoping either life02 or vilord can pick up on it tonight or whenever they can.
[Touch Cruise Android Development] Septavius:
Addisu built a wlan_loader with the errno output. The "ioctl" call fails with:

""Errno = 95, Operation not supported on transport endpoint"

So it seems like the tiwlan0 interface is found, but for some reason doesn't support the init operation. I'm no expert at "ioctl", so I'm not sure if this is because of something in the kernel, wlan.ko or the wlan_loader itself...
[Touch Cruise Android Development] vilord:
bally3 i'd really like to get the SMS issue squared away, please let me know if you'll be available to do some testing this evening? I get home about 6pm my time which i guess is very late for you... but if you could grab a log of what is happening I can fix it.
[Touch Cruise Android Development] bally3:
I'll stay up for you all night if I have to Jesse.. or until I fall asleep at the keyboard again like last night! :rolleyes:
[Touch Cruise Android Development] meknb:
I think i read somewhere about people getting this error when loading wpa_supplicant

Have you got a link for Addisu wlan_loader i've been using the newbie from the kaiser thread.

Thanks bally3 for wlan_loader_errno the error im getting is fatal error opening "/sys/power/wake_lock"
[Touch Cruise Android Development] bally3:
here it is:
[Touch Cruise Android Development] Leryan:
Played with the previous release (bundle from 04.08), for me sending and receiving SMS is ok. The only thing i've found yet: delivery reports are not working. Message have statuss pending.
[Touch Cruise Android Development] radem205:
Hi Vilord, I have send you the radiolog by email after I sent a text message.The status of the sms, which I tried to send, is on the bottom of that file.

Thanks for your great work.
[Touch Cruise Android Development] iseeka:
tried android-1.5-2009-08-06.zip

very nice version, no wifi
[Touch Cruise Android Development] briggs81:
At least the battery is accurate when it's down to barely anything and charging. it's also pretty accurate if you disconnect it at like 15, it goes down like it should. Haha, half the battle!
[Touch Cruise Android Development] radem205:
With the new rootfs sms is working great Vilord! Thank you very much Vilord !
[Touch Cruise Android Development] imfloflo:
A new package in the first post and in the wiki would be very appreciate.

Like that n00b can test it and we can have more bug report.

I read dzo code an autopanel detection code that would be nice to port it too on polaris.
[Touch Cruise Android Development] bally3:
Its a good idea indeed and not hard to do at all, but the development is moving at such a pace at this moment, its pointless to create more packages than the ones the devs are posting up.

If someone wants to list each file in any post and keep that list maintained as new files are released, I'll be happy to post a link to it in the first post..

Not wanting to sound harsh, but there are scores of us now with the Google code page in their signature. ff users - regardless of their noobity - cannot figure out what the latest files are from that page, maybe they should be well advised to stay clear of Android until we have something more solid to offer them.

A development level OS is not something people with limited general IT skills should be taking on. The rest of us, just like each of and every one of us had to, are advised to do some reading before even attempting to use Android at this stage and feel free to ask questions in the testing and reporting thread - remember, its good to ask these questions, it normally answers the question for someone else's issue as well.
[Touch Cruise Android Development] imfloflo:
We could have a website like dzo where we post the lastest full package for polaris with all the good settings no ?

I only saids that to let people without knowledge test android on there Device.

BTW is there any progress with wifi? here or on other device?
[Touch Cruise Android Development] bally3:
Havent had a chance to test it yet, but good news indeed. It may not look it sometimes folks, but these guys are doing a lot in the back end to fix and tweak little things that make Android better, faster and compatible with all our different devices.
[Touch Cruise Android Development] bally3:
No need to port this, dzo has been working with us to resolve this too. The vogue was a test run to see if it worked. He will fix it for all devices once he's happy it works.
[Touch Cruise Android Development] Mormy:
I just tried a few thing with the last release of this files (2009-08-07):

System.img, zimage, rootfs.

Call in/out: ok

Sms in/out: ok

Data connection: ok, but only by modem

mms: It remains with the lteerbx and the red clock over it. I've got modem connected, but I don't understand if it starts or not :-/
[Touch Cruise Android Development] briggs81:
Just wondering what the point of that is? I think the Google Code site has everything they need, the only thing that would be different in a polaris package is a default.txt with the 1723.

I think having more websites is more confusing to everyone. I am happy to see that basically everyone is putting their changes on the Google Code site, just one repository to get stuff. No going to multiple sites is good.

Anyways.. is anyone else still have problems not being able to call out wtih latest stuff? I have to make a bunch of log files because the radio is really messed up for me still.. just wondering if anyone else has had their calling out issues fixed.
[Touch Cruise Android Development] :
Hi,

Up to bundle android-1.5-2009-08-06.zip I still was not able to make outgoing calls with my USIM.

With bundle android-1.5-2009-08-07.zip I have not been able to test, I keep getting the strange colored screen, even with old data.img, or without it... May be I will roll back to bundle 0806 and then update file by file ...

I'll keep you posted.

JM
[Touch Cruise Android Development] fsahaf:
Google Ion Screen

Hi guys I am new to this I install the latest image and when my phone boots up it is stuck at the google signin screen I am unablle to connect ot my XP machine and use HTC sync

I am with rogers

installed the android-1.5-2009-08-07.zip files with polaris default.txt file

can someone help?
[Touch Cruise Android Development] meknb:
I agree with briggs81 google code site has all you need,no need to scatter images everywhere, theres no need to bundle it all up because the system and initrd is rarely updated it's mainly the zimage updated.

All people need to do is read a little before installing theres no shortage of info out there.

fsahaf you cant use sync with android only adb try and skip the google login.
[Touch Cruise Android Development] 188236:
GPS Calibration

Hello,

some Off-Topic stuff amongst all the wifi development and bundle-discussion (which is important and good!):

My GPS is working, thats the good news. That bad news: It locates me about 200 kilometer south of my location. Any ideas why this happens? And anyone else who has this problems?

Keep on working on the OS, its a very good one and I like it very much! Thank you!
[Touch Cruise Android Development] briggs81:
My friend, I have just made my first successful call with Android, EVER. I used the new stuff in 2009-08-07.zip.

I still have issue when i boot up phone, i have no cell signal unless i disconnect modem,which happens randomly, but i went to test just now to make a log and the call actually worked!

i actually have no cell signal right now for about 2 minutes, but i just received an SMS then all of a sudden i haev cell signal and data connection.. weird!
[Touch Cruise Android Development] briggs81:
Like Mek says forget htc sync. just skip all the setup stuff and then go into wireless settings and enter your apn connection details.

you don't need to hook it up to your pc except to transfer files to your sd card or to run ADB to get log files.

I am with Fido and making calls just started workign for me today so should be interesting if it works for you too.
[Touch Cruise Android Development] life02:
use polaris default.txt
[Touch Cruise Android Development] fsahaf:
calls working

Thanks guys its working for me now. I can now make calls and receive calls now.

I love it!!! will play with it more and update. will try the wifi and gps next
[Touch Cruise Android Development] :
Hi all,

Im glad that today I was able to place my first call using my USIM (which

previously did not work).

The time to connect to mobile network, for me it have always been a couple of seconds after completely booted ANDROID and appeared the legend "Press Menu to Unlock".

I know this is only a minor step for most users, but for me (and everybody who were not able to make ougoing calls) it has been a major achievement because now I'm able to use for longer periods and maybe for the whole day.

I want to thank everybody involved in this project, specially Briggs, Hikeit, Vilord and Life02 for their kind support and guidance during this early stage of involvement in to Android.

Please count on me for further testing and logging, I will be more than glad to help.

BTW, the issue with the strange colored screen came up because in my default.txt the end of line characters apeared together and my first line was looking as: #alloctest 0x2000 (all in the same row).
[Touch Cruise Android Development] life02:
Just FYI, hikeit=vilord

;)
[Touch Cruise Android Development] Michel82:
I'm having the same issue, but only with the nkhero system.img. Are you using that one too? When i try a different system.img the GPS is spot on.
[Touch Cruise Android Development] bally3:
what a difference vilord has made to the polaris side of android now he's got a polaris in his hand.

I'm convinced this is the way to go and we need to get one out to dzo so he can get camera and some of the other stuff that needs doing.

The todo list for the major items has shrunk considerably... but we have a long way to go still with the kernel.

please donate to dzo. the donatons have stopped. seems like those pledges arent coming through, to those that pledged we need those donations now, not after the kernel is completed.

so far 20 dollars have been donated to dzo, I only made the suggestion as people were still pledging donations after we had raised the full amount for vilords device.

I dont ask just for myself, but those who followed the project since last year will remember how close we came to shelving the project - lets keep the momentum going! :)
[Touch Cruise Android Development] radem205:
the progress is great so far! goog job!

the biggest problems I ve noticed with the latest pzckage are:

- most of the time incoming and outgoimg calls work great, but sometimes I can't pick up the phone (green button doesn't do anything) and sometimes the phone is ringing and android freezes

- wakeup the phone is very laggy. sometimes it doesn't do anything when you click on several buttons.

Keep up the great work!

Edit: Does this zImage contains auto detection of the panel type for polaris (because I saw auto detection was added on the repro): http://code.google.com/p/vogue-android/downloads/detail?name=zImage-08-08-09&can=2&q=&sort=-uploaded
[Touch Cruise Android Development] bally3:
Panel detection didnt work last night, we tested it. it was vogue anyway. and will need working on to get the Polaris panel detection correct.

If you're struggling radem, try changing it back to htcvogue.panel and try "1".
[Touch Cruise Android Development] radem205:
Thanks for your reply Bally. But could you wakeup android by pressing the power button once? Or do you have to press several buttons to wakeup the phone?
[Touch Cruise Android Development] briggs81:
We have always had to press buttons a few times to wake it up.
[Touch Cruise Android Development] SuperJMN:
I have a key combination that always works to wake up the device:

Press End key and immediately, press the Internet Explorer key.

The device lights up and you just have to press again the IE key to unblock it.

Tell me if it works.
[Touch Cruise Android Development] 188236:
So many system-images...

Yes, you are right. The problem exists only with nk hero. What a pitty, thats my favourite one :-(

By the way: Why are there so many different system.img? Hero, hero light, Ion, Zenulator, mssmisions etc.... Its very confusing for me to find the "right" one. Is there a list anywhere, which system.img is designed for what purpose, and where they derive from? (G1, HTC etc...) Or could anyone post such a (brief) list please?
[Touch Cruise Android Development] 188236:
telephone-"kicker"

Hi,

as I already mentioned, I tried all kinds of system.img today.

I know that the images originally have not been built for a polaris, but I have no use for the "telephone"-starter in the program-kicker task-bar at all. I like the simple starter-version in the nk here build much better. Is it somehow possible to exchange this starter (e.g. for a e-mail or browser-symbol)?
[Touch Cruise Android Development] freddycs:
How to capture screenshot in Android

Just a little tips to share with everyone on how to capture screenshots in Android. I found this method in a chinese android forum. you need to have adb interface detected in your pc and android sdk 1.5 to get this work.

1. first connect polaris to pc in winmo, then execute haret and load android (if i load android first then only connect to pc, adb interface won't get detected in windows.....)

2. once android is loaded, ensure that adb interface is detected by pc.

3. now, locate ddms.bat in your tools folder in android sdk. execute it and a little tool will come up and there is an option for you to save captured screenshots.

let me know if you have problem doing it. :)

by the way, with the new bundle dated 7-aug, i managed to make outgoing call now and the signal is pretty good and stable. the system is responding very fast. but i experience once where the android is just freeze on the desktop and the program menu, i'm not able to slide to the left or right panel on destop and not able to call up the program menu. however, after reboot its gone.
[Touch Cruise Android Development] life02:
strange the gps problem only exists for me on the mssmison builds. Both of yall are using a pola200?
[Touch Cruise Android Development] meknb:
The new mssmison looks nice gps seems ok not far off, looks great in lanscape mode check orientation under sound and display, click settings,about phone,contributors,scroll through then click the back(windows) button landscape seem's to stay on till screen times out.
[Touch Cruise Android Development] dzo:
Can somebody try this kernel:

http://cs-alb-pc3.massey.ac.nz/vogue/files/zImage-polaris

Just check if the panel comes on properly after power collapse, I changed the gpio it uses. This doesn't do auto panel detection on polaris.

Out of interest what different panel types to polaris have, if there's only one type that would explain why I cant find any autodetection code in the wince drivers.
[Touch Cruise Android Development] imfloflo:
Hi dzo just try your zImage and i have some trouble with.

If i collapse the screen with the power button, i can't wake up it with the same power button.

I must type green,red,Interet,gps button twice to wake up the device.

The red button go to sleep mode, i prefered when it was the return/cancel button like on G1
[Touch Cruise Android Development] SuperJMN:
I discovered the right key sequence. Just do what I say:

Press the End key

Press Internet Explorer key

The device lights up. Just press IE again and ready!
[Touch Cruise Android Development] imfloflo:
Yeah but we must type 2 keys to wake up it's not very normal, and don't like the new mapping on this zimage. Very disapointing compare to my G1 and lastest zimage for polaris
[Touch Cruise Android Development] briggs81:
Just press any buttons 3 times. Don't think we need to worqry aabout it. It will get fixed at some point.

Is anyone else having problems calling out, or was it just me and juanmre?
[Touch Cruise Android Development] Mormy:
Just tried it:

Calls in and out: works

Sms out: works (I can't tried in)

Data connection through "Modem": works

Neocore 324x432: 22.9fps

I've installed package release 2009-08-07 (apart the zimage that I'm testing)

I'm Italian and I've got an USIM, my carrier is H3G
[Touch Cruise Android Development] freddycs:
Hi briggs81,I was facing problem making out going calls until the 7-8-09 bundle.now everything is back to normal.
[Touch Cruise Android Development] worstenbrood:
i have alwyas have to use paneltype 3 otherwise i have a white screen ..
[Touch Cruise Android Development] Mormy:
oops, sorry. I use panel type 0, otherwise white screen
[Touch Cruise Android Development] bally3:
Panel type "3" is the only one that works for me with board-htcpolaris.panel_type.

But I can also use "2" if I use board-htcvogue.panel_type

:rolleyes:
[Touch Cruise Android Development] vilord:
briggs, are you still having calling out issues? juanmre, what about you? is it spotty or always working or always not working?

Maybe there needs to be a delay timer added somewhere...
[Touch Cruise Android Development] Septavius:
From what I've seen POLA100 users usually must use panel type "1", while POLA200 use panel type "3".
[Touch Cruise Android Development] briggs81:
Nope, i have been able to make calls whenever I want, tried about 8-10 times so far.

I still have the odd issue of the signal not attaching very quickly though, but it doesn't happen al the time, or sometimes it happens quicker then usual.
[Touch Cruise Android Development] dzo:
This isn't a kernel for everyday use, I just wanted to know if the panel powers up correctly. If this works it should give you some power savings. I didn't change anything else, apart from panel power it's the latest kernel from git.
[Touch Cruise Android Development] bally3:
Power collapse is working fine, havent tested how long I can get the battery to last. Hoping to take the phone with me upstairs tonight and leave it with Android running and monitor how much battery I lose overnight.

With mssmison's latest full image (an awesome image btw!) a quick double press of any button wakes up the phone nicely. I like this quick double press way, it stops the phone waking up accidently in my pocket.
[Touch Cruise Android Development] Mormy:
It seems to me that I am the only one with a POLA200 that MUST use panel 0 (polaris type obviously), with all the other types I obtained a white screen. ( I also try to delete data, so to start a new one)
[Touch Cruise Android Development] radem205:
Make sure you use the polaris paneltype and not the htcvogue paneltype in default.txt (I think you know this but for sure).