yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] bally3:
Great job guys, just tested the zimage and the rootfs image - great work :)

I'll report later whats working and whats not in my setup, just managed to get it up and running, but data works fine - connected automatically and neocore reported 20.3fps - I'm still usiing my old data image though so I expect it to be lower than everyone elses - thing is I havent been able to get data working with fresh data images. Might have a go later and see whether I have better luck.
[Touch Cruise Android Development] bally3:
With regard to testing, can we all stick with the cupcake builds when reporting whats working in the kernel developments please?

Correct me if I'm wrong, but as far as I am aware zenulator and mssmisons builds have code unique to their builds.

Until this has been integrated into the main initrd, I would recommend that we stick to cupcake builds for reporting purposes. If it already has done then it should be fine to use for development.
[Touch Cruise Android Development] imfloflo:
I agree with Bally3 we need to have the same base of testing.

zenulator and mssmisons can be speak in the other thread.
[Touch Cruise Android Development] radem205:
You are right Bally! It's better for us to concentrate on the Cupcake builds. I have installed the cupcake version with the latest rootfs and initrd.gz.

I get the following problems:

- On startup Android is trying to connect to the internet, but only the left arrow is flickering, so it doesn't connect to the internet. (during boot he says: GSM phone found).

The carrier I use is vodafone (live.vodafone.com). On previous builds internet was working fine. On modem.apk "Connection attempt failded" appears.

- On startup I get the following message: Acore stopped unexpectedly. When I press wait the message dissapears. (this one I also get on the zonulators' build, but I have renewed all the files before starting cupcake).

- And also I can't send a sms message. Very fast after send the sms I get the message that the message wasn't send. Incoming and outgoing calls are working fine.

BUT.. with the latest zImage everything is working very smooth. What a difference!!! Great job!!
[Touch Cruise Android Development] bally3:
Working wifi??

ROLL UP ROLL UP.. LATEST NEWS .. WORKING WIFI RUMOURED ON KAISER..

Sorry.. just trying to create the mood..but this has to be the best news I've heard all week if its true :)

http://xdaforums.com/showpost.php?p=4260681&postcount=33

reports are that wifi is working.. needs some work done to system image to get it working.. this sounds like a job for life02..<hint hint.. pretty please!>

This works and dzo gets camera working.. I'm android bound for sure.. !
[Touch Cruise Android Development] radem205:
Great news Bally! Two questions for you: How did you get a working data connection? Did you change something in Android or default.txt? And is sms working for you?
[Touch Cruise Android Development] Michel82:
Great news about the wifi!!!!

Test results from the latest initrd and rootfs with vsync zImage.

- Speed is great!

- Data is working without the need to connect modem, including sync and market.

- Still my GPS is off by about 400km, but that could be due to the nkhero system (which are you guys using?).

- Calls are working as they have always worked, both in and out.

- SMS is working both in and out. (Tested 5 in and 5 out).
[Touch Cruise Android Development] radem205:
Did you guys using this initrd: http://code.google.com/p/vogue-android/downloads/detail?name=initrd.gz&can=2&q=&sort=-uploaded ? I don't understand why data connection isn't working for me (before it was working all the time). And you (michel) are living in the same country as I. Did you change the APN settings in Android itself of only in default.txt?

Edit: I'm using the default system.img. Attached you will see my default.txt. Is this ok?

I noticed that with the system of zunatalors pressing the power button was enough to get the phone out of sleepmode.
[Touch Cruise Android Development] Michel82:
I think that your APN settings need to be ok with this build, including the username and password. Previously only your settings in default.txt needed to be exactly right and for the APN in android only the MCC and MNC parameters needed to be correct. ?!
[Touch Cruise Android Development] bally3:
Didnt do anything for data.. still using old image as I said before, from the before msmissons hero themed build.

Data works, but I'm losing connection and then having to click disconnect twice to reset radio and reconnect to get it working again.

SMS sending broken, instantly get a message saying message not sent. SMS receiving works. Sent a message from wifes phone and appeared in milliseconds!

Call making works fine, call receiving - no ringing but this might be at my end.

I'm going to try a fresh image and see what differences I get.
[Touch Cruise Android Development] Leryan:
Hey, can anyone make a full android package, and upload it.

For testing purposes it will be much better.

It looks like everyone is testing with own set of files. :confused:
[Touch Cruise Android Development] briggs81:
With the latest initrd my results are I can send sms messages now, no calling out.

And two benchmark tests with new zimage, first was 22.1, second was 20.1.
[Touch Cruise Android Development] briggs81:
You can download the latest files as they appear, or if a package has been made you can download that.

http://code.google.com/p/vogue-andr... Filename Summary Uploaded Size DownloadCount
[Touch Cruise Android Development] dubbeld00:
1. This was a database created for Android v0.8, maybe the structure of the database has changed...

2. Do you still use the same commit from the android git? Will check your progress tomorrow, and have some spare time this week, so I will definitely give it a try.

Hope to hear your progress as well, so I don't have to do things twice.
[Touch Cruise Android Development] rogro82:
Im building against the latest commit in the vogue-tree.

Ive posted a diff file and some other needed files a few posts back... just use those to build a working kernel and use the rest of the files to boot.

As soon as i make some progress on anything ill post it in here.
[Touch Cruise Android Development] dubbeld00:
Vogue tree in the linuxtogo git or the android git (branch android-msm-2.6.25 commit 07fe2e3914202167a4d314bf5e81bbd2f5d3062b) + vogue diff file (thought I don't have to apply that file, because yours will include that also)

Guessing the last one... Hope to make some progress during the week :)
[Touch Cruise Android Development] rogro82:
vogue tree in the linuxtogo.git commit ( febeb3476fb6f047d9bd987ceeaa61d2c053fce8 )

Just mapped the power button as requested ;)

for devs:

board-htcvogue.c

add the following entry to the keymap:

{.gpio=20,.code=0x6b},

This should allow you to lock the phone using a short press and should show a menu with sound/power options on a long press.

Does anyone know the gpio of the call button? I want to map it to 0xe7 so that the phone app shows up.
[Touch Cruise Android Development] radem205:
It's working correctly indeed! But power off doesn't work yet, am I right?

I have to say that your guys doing a very great job. Especcialy when I remember that Rogro didn't have any experience with linux!
[Touch Cruise Android Development] excogitation:
sure thing
[Touch Cruise Android Development] roms5:
I allwayst get the error:

Failed to Mount SD Card

/bin/Sh: can´t access tty; job control turned off
[Touch Cruise Android Development] excogitation:
Put the files in the root directory of your SD-card!
[Touch Cruise Android Development] tavos:
me too...:confused:

on udK Syrius R4 and also on M-Amine 2.0 FINAL.

(radio 1.59.44.02)

any solution?

thx
[Touch Cruise Android Development] Swifty:
Can't seem to get this latest image going.. when I run haret and click to launch the linux the screen just goes white and seems to be flashing slightly - it just sits there doing that, no tux boot screen like the previous image :(

UDK R4, Latest Radio, Orbit 2 (o2 UK)
[Touch Cruise Android Development] radem205:
I have tried installing an older Radio ROM (1.59.42.15) but the error "Old Radio found - Audio disabled" still exists. My previous radio was the newest (1.59.44.02). So, I think this isn't related to the radio ROM installed, but related to a wrong setting in Android, isn't it?
[Touch Cruise Android Development] bally3:
Same here with Maxnipers rom, the lassst one worked fine for me. Will play around and see what I can do to fix it.
[Touch Cruise Android Development] excogitation:
Definitely not related to the radio ROM.
[Touch Cruise Android Development] rogro82:
Martin made changes to the ril... maybe thats the reason? Does any one have the original libreference-ril.so?
[Touch Cruise Android Development] bally3:
Theres something about that here: http://xdaforums.com/showthread.php?t=382265&page=24

I cant get past the white blinking screen at the mo.
[Touch Cruise Android Development] dubbeld00:
+ {.gpio=19 ,.code=0x69}, // Wheel left = Left

+ {.gpio=20 ,.code=0x74}, // Power button = power

+ // {.gpio=21,.code=38}, // USB cable

+ // {.gpio=29,.code=0xe7}, // Camera button (mapped by vogue-ts ?)

+ {.gpio=31,.code=0x6a}, // Wheel rotate

+ // {.gpio=35,.code=0x67}, // Voice recorder button

+ {.gpio=37,.code=0x6c}, // Wheel down = down

+ {.gpio=38,.code=0x67}, // Wheel up = Up

+ {.gpio=40,.code=0x9e}, // Dial / hangup key

+ {.gpio=41,.code=0xe5}, // Explorer key = menu

+ // {.gpio=42,.code=0x6b}, // Tap screen (mapped by vogue-ts ?)

+ // {.gpio=76 ,.code=38}, // Camera button full press

+ {.gpio=90 ,.code=0xe8}, // Wheel button = ok

+ {.gpio=91 ,.code=0x6a}, // Wheel right = right

+ // {.gpio=94,.code=38}, // SD card inserted

should be all available...
[Touch Cruise Android Development] rogro82:
I thought this only was the hangup key and not the dial button.

Any idea on how to get the smd to work? Using the old kaiser smd im able to create a data connection without a problem but using that code Android crashes immediatly.

It boots using the vogue smd code but that doesnt work because of the address differences... when i change it android crashes again :rolleyes:
[Touch Cruise Android Development] dubbeld00:
I will give it a try on Tuesday... But I wanted to try the same as you... just port the Kaiser/Polaris SMD to the Vogue SMD.

About the "Call" button, I couldn't find something else... don't know if premy had implemented the "Call" key (I thought so) but this was the only thing I could find... (only gave it a quick look).
[Touch Cruise Android Development] excogitation:
MTYPE

btw why are we still using MTYPE 1667 when Polaris has it's own one (1723)?

bally3 - can't really tell a difference to mine bally3 <-> excogitation haretlog diff

bally3, what radio version are you using?
[Touch Cruise Android Development] bally3:
Tried a fresh data image,speed increase very noticeable from last data image - I'm using mssmissons hero themed system image btw.

Initially there was no data icon and data said connected but no connection or ip details. Disconnecting and reconnecting made no difference, had to setup APN for the icon to show, but still no connection. When I hit reconnect it stuck on the starting pppd... message.

Rebooted - automatic data connection made - ip details shown in modem.

Tried to sign in to google. Noticed only UP arrow (send) flashing and it failed. Tried browser and no connection.

Disconnected and reset radio and reconnected - saw both arrows flashinng and connectione made. Tried browser again - still only UP arrow flashing - no connection. Tried signing in again as a last hope - failed.

So no connection at all with new data image. :rolleyes:
[Touch Cruise Android Development] radem205:
I have a data connection now (also with a fresh data image). You have to set all the right settings in Android itself (so not alone in default.txt). That was the trick for me. Sorry for my stupid questions :). Only the sms issue for me is now relevant.
[Touch Cruise Android Development] Leryan:
I am checking for new files exactly there. :)

But we are using different system.img, also default.txt not always are the same. Its not good in testing period.
[Touch Cruise Android Development] meknb:
I think just using the latest is best for testing,this is the development thread so were all using different ones just to try and get eveyrthing working.

Good news about the wifi just tried addisu new image and intrd and system files still the same errors though
[Touch Cruise Android Development] life02:
SMS in/out working for me with the newest rootfs posted this morning.
[Touch Cruise Android Development] vilord:
Okay bally3 and others in the UK, sounds like the SMS sending issues might be specific to european phones... can one of you get an "adb logcat -b radio > radiolog.txt" for me when trying to send an SMS?

And bally3 I guess I'll need yet another log from you to fix up data connections.

Briggs81, no change for outgoing calls? Shoot. I was really hoping... More logs the better, you can send them direct to my email, hikeit - atnospam - gmail.com
[Touch Cruise Android Development] briggs81:
No change for calls for me. Is there a particular action you want me to log? I've just been logging me dialing and then pressing send, waiting a few seconds after i get hte red screen, then i just end it.
[Touch Cruise Android Development] radem205:
Hey Vilord, unfortunatly I can't find the correct cable to connect my polaris to the pc and use your command. Is there another way to get the information you need according to the sms problems?
[Touch Cruise Android Development] briggs81:
Well this is odd.

The first time I tried to make a call, i got the usual result, red screen right away.

Right now I just tried running the log command while android was booting up.. then tried to make a call and it's actually stuck on the green call screen.. at least it didn't end right away lol.. ofc ourse there is no dialing, it could just be frozen and still counting how long i am dialing for.. as it's still going. I'll send that log over, and then try again and make another log.
[Touch Cruise Android Development] vilord:
radem:

you can get the log by sending an SMS then very quickly opening a terminal window, and typing the following:

su
logcat -b radio -f /sdcard/radiolog.txt
<wait about 10 or 20 secs>
dpad-c (like ctrl-c, but use the middle of the dpad as the ctrl key)

hopefully that'll work :)

briggs: there are three different logs I'm going from, one is the windows ATDbg0.log which should show everything from powerup through sending and ending a call including all the initialization strings to get there.

The second is a log of the actual call like you had for me last time.

The third is a log of the android initialization. Easiest way to get that is to disconnect with modem, then start the radio log, then press disconnect again in modem (which resets the modem)
[Touch Cruise Android Development] bally3:
So I eagerly pull down the files, from the Kaiser thread and delete all the old files from my test sdcard, notice that the system image says nk, fire it up and it automatically adds my apn details and theres a data icon. Its unconnected so I hit connect in modem and it connects. So. I sit down and type this post on it to prove it!

Do you know which build it is?

Ps:. wifi doesn't work lol
[Touch Cruise Android Development] briggs81:
.

How do I go about getting the ATDbg0.log? Don't think I've ever been able to produce that one.

I will try this modem connect/disconnect one right now.
[Touch Cruise Android Development] radem205:
When I type "su" (without quotes) I get the following message: "must be suid to work properly". How can I solve this?
[Touch Cruise Android Development] briggs81:
A little off topic, but do we need to install the android sdk in order too do commands like "push" and what not? I was thinking about looking into changing things like clock graphics, notification bar graphics, etc.
[Touch Cruise Android Development] bally3:
is there any way of being able to stop the backlight switching off when connected to either usb or power?

I'm running that cat command for the wifi, but screen keeps going off.

#!/bin/sh

cat /dev/mtd/mtd0ro > /sdcard/romdump.img

dd if=/sdcard/romdump.img of=/sdcard/calibration bs=1 count=752 skip=38797376

ls
[Touch Cruise Android Development] meknb:
I think you can stop the backlight under settings sound and display,still not creating the device for wifi thats the main problem ?? try dmesg when you load the module.We dont need to load the firmware till the modules loaded.
[Touch Cruise Android Development] bally3:
has anyone had a go at this yet?

enatefox managed to get it working on his kaiser by doing it line by line because of a broken pipe error which is what I got. He is testing a system image he's just built but I dont know if that means it can work for us.

So want to see this work..I can almost smell it..:rolleyes:

(For my own future reference: files attached are polaris firmware and polaris calibration files)
[Touch Cruise Android Development] meknb:
Yer tried got and failed still cant get the module to create the wifi device. but yer think we are close.But noticed if you try and load the module twice it tells me mem is allready registered ? loading the module creates a file in the proc folder called mem ??
[Touch Cruise Android Development] radem205:
Bally: You have also a problem sending sms messages, right? Could you create a log file after you send a sms message for Vilord? For me it isn't possible to create a logfile without the right usb cable.
[Touch Cruise Android Development] bally3:
aye, I'll work that out with vilord later..right now trying to get wifi working with newbie16 in the vogue-android irc room ... looks like we need the polaris firmware file to make it work.. fingers crossed! :)
[Touch Cruise Android Development] meknb:
Which firmware bally from windows or the romdump? have you managed to load wlan.ko ie create a interface ?
[Touch Cruise Android Development] bally3:
firmware file from windows.. no I havent loaded wlan.ko do I need to?

I just clicked on wifi in settings?

EDIT: no need to do that mknb its already included in the system image.
[Touch Cruise Android Development] meknb:
I still get the nobody to notify error in dmesg and unloading the module so it's not creating a iface by clicking the start wifi, i'll have a look in windows for the firmware.
[Touch Cruise Android Development] bally3:
pop into android-vogue we're looking at it there meknb. no point duplicating effort here. Addisu who got it working is creating a debug version of wlan.ko to see whats going wrong.
[Touch Cruise Android Development] briggs81:
I would like to make my 1000th post here, in this thread.

Thank you for Android on my Polaris. It is has ripped the grip of Windows mobile on me and made me more productive, even with its current faults.

Goodbye Windows Mobile, Hello Android hello to another 1000 posts.
[Touch Cruise Android Development] life02:
Wifi Progress

236.[ 64.341790] TIWLAN: Driver loading

240.[ 64.690915] msm_hsusb_set_vbus_state(1)

241.[ 64.690977] battery_charging_ctrl 1

242.[ 65.294157] trout_wifi_power: 1

243.[ 65.294225] trout_wifi_reset: 0

244.[ 65.519822] trout_wifi_set_carddetect: 1

245.[ 65.519889] mmc0: card_present 1

246.[ 65.542314] mmc0: Slot status change detected (0 -> 1)

247.[ 65.556302] mmc0: Command timeout

248.[ 65.572309] mmc0: card claims to support voltages below the defined range. These will be ignored.

249.[ 65.572429] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.

250.[ 65.575384] clk_set_rate 19:20000000

251.[ 65.577450] set sd clock - 0 1

252.[ 65.772210] mmc0: new SDIO card at address 0001

253.[ 65.780992] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)

254.[ 65.839277] TIWLAN: Driver initialized (rc 0)

255.[ 65.850837] TIWLAN: 1251 PG 1.1

256.[ 65.850912] TIWLAN: Driver loaded

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

Thanks to Septavious and DZO for working on this with me tonight!
[Touch Cruise Android Development] Mormy:
:eek: Yuppiiee :D

All of you are really great :cool:
[Touch Cruise Android Development] Michel82:
OMG! This is awesome. When can we expect a kernel for testing?
[Touch Cruise Android Development] SuperJMN:
Oh mommy! I've got to test it ASAP!
[Touch Cruise Android Development] Leryan:
WOW, released, Downloading right now
[Touch Cruise Android Development] bally3:
Released where?? :confused:

If you're talking about the google code page, thats the Kaiser wifi, and wont work for us.

ps. congrats Briggs81 on your 1000th post- many more to come before we have a fully working kernel.. many many more .. lol
[Touch Cruise Android Development] Leryan:
jap :( , just read the part - WiFi, do not noticed word Kaiser
[Touch Cruise Android Development] iseeka:
oh i downloaded it too...hope we can ger wifi soon. thanks for the hard job!
[Touch Cruise Android Development] Leryan:
WiFi not working, as bally3 promised. :(

But with latest Android bundle (android-1.5-2009-08-04.zip) I've got 23.6 FPS in neocore.

Calls are working for me (have received only 2 yet).

Trying SMS right now.
[Touch Cruise Android Development] bally3:
can someone tell me whether the data is stable for them in the last zimage posted by vilord please?
[Touch Cruise Android Development] life02:
Ok guys, we have the driver loading but Wifi still won't start. Still this is a HUGE step for us. We may have the wrong memory addresses for the wifi device. Will get some haretlogs when I get off work.

The bundle that Jessie posted should allow you to at least get the driver loaded as I uploaded all the changes that I made to the l2g git last night.
[Touch Cruise Android Development] mstrangers:
sms ,phone call and data working with

Life02 test zimage (from 04/08/09)

vilord rooffs (from 04/08/09) not the b version

and system http://vogue-android.googlecode.com/files/mssmisonsystem.img

and with apn setting in default.txt

but i hate the new keymap ( can anyone give me a diff file with the old keymap, i build zimage myself ?)
[Touch Cruise Android Development] briggs81:
Yikes, 10 minutes and still waiting for phone to get signal with this new package. Every time I reboot the time it takes to get a signal gets longer and longer :eek: lol
[Touch Cruise Android Development] toasty_:
Ok I don't know anything about the progress with wlan and the polaris, but after loading wlan.ko you have to call "wlan_loader" to get a MAC for your WLAN-adapter...

wlan_loader -f /sdcard/Fw1251r1c.bin -e /sdcard/calibration -i /sdcard/tiwlan.ini

you have to put Firmware, calibration and tiwlan.ini to sdcard

if you type ...

logcat -f /sdcard/debug.txt &
wlan_loader -f /sdcard/Fw1251r1c.bin -e /sdcard/calibration -i /sdcard/tiwlan.ini
killall logcat
cat /sdcard/debug.txt | grep -i wlan

...you should get an output that is maybe useful for finding problems

extracting the calibration
[Touch Cruise Android Development] toasty_:
OK

nvs_map.bin is the eeprom-file (or also called calibration)

Some questions:

Are you using a patched wlan.ko (wlan.ko working on Kaiser)?

Did you start 'wlan_loader' with all options?

Did you put all these file (Fw1251r1c.bin, calibration, tiwlan.ini) on your sdcard?

And what says 'dmesg | grep -i wlan', is there any output