yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] phoeniix:
Changing my radio worked for me, as well. I was using 1.70.18.02. Changed back to 1.65.24.36 and Android now boots. Before it was hanging on the SD card error described by dcordes.

Thanks Anod for getting us this far.
[Tilt, TyTN II, MDA Vario III Android Development] KeizerBAAS:
Sounds good! I've got 1.65.28.25 for radio, which works... Who knows it helps...

We had a great new year's champagne blast here in Amsterdam, happy new year!
[Tilt, TyTN II, MDA Vario III Android Development] edzilla:
It didn't work at first for me either, I upgraded the radio to 1.65.24.36, now it boots with the same result as stated before.
[Tilt, TyTN II, MDA Vario III Android Development] dasilva333:
same story as the other users,

i have eOS 4.888 and radio 1.7x and it wasn't working got 417 excited error

then i tried android1.0_kaiser.rar with the 1.65 radio and it works as good as people have been reporting, heres hoping to a great new year

edit: now that android is actually running its all downhill in terms of getting all the features within it to work (i think)

also in terms of getting the keyboard/keypad to work i think its because its been stripped out i was reading rogro's compile log and I think this might be relevant for us to get the input to work:

The msm_copy_keyboard and the onscreen_keyboard are referenced from the video driver of the vogue kernel. You can either strip them out or use them in the vogue-ts to handle the onscreen keyboard.

I did the last because of no physical keyboard on a Polaris.

Luckily Dwaradzyn already posted a working vogue-ts and a full keyboard on xda-developers so i just tried his, and only added a fake msm_copy_keyboard call because his vogue-ts.c didnt have it. I added these files as attachements so you dont have to search for them. Just place the file vogue-ts.c and full_keyboard.c in the arch/arm/mach_msm folder.

and i think we can find the relevant files here:

http://git.linuxtogo.org/?p=groups/...1;hb=febeb3476fb6f047d9bd987ceeaa61d2c053fce8

so maybe just put those files in the android vogue merge compile it and try see what happens

also i'd like to know how to compile the files see if i could help, if someone could point me to a guide/tutorial/ or just a program name so i could make my own zImage that would be great thanks
[Tilt, TyTN II, MDA Vario III Android Development] mmone3:
The radio change worked for me too. Now the fun part is fixing the problems.
[Tilt, TyTN II, MDA Vario III Android Development] anod:
Below updated files with new instruction (now it's step-by-step), how to recompile the vogue merge kernel, i will try to do it, when i will have some free time...

http://xdaforums.com/showpost.php?p=3092252&postcount=159
[Tilt, TyTN II, MDA Vario III Android Development] disturbed4686:
i can also verify that as soon as i updated my radio, android would boot for me. w00ties
[Tilt, TyTN II, MDA Vario III Android Development] greenninja:
I'm sorry if this is a stupid question but how do I upgrade my radio?

I used the latest files from Anod but I hang fairly soon after the keyboard appears at the top of the screen.
[Tilt, TyTN II, MDA Vario III Android Development] anthonws:
greenninja,

Read this thread: http://xdaforums.com/showthread.php?t=393182
[Tilt, TyTN II, MDA Vario III Android Development] lyka:
boot fine for me. Just keypad not well mapped and touchscreen not working, but looks promising.
[Tilt, TyTN II, MDA Vario III Android Development] dasilva333:
update:

ive got limited functionality, up, down, back, ok, menu, enter using the jog wheel keypad/keyboard and i've managed to open every program and visit almost every menu and it all seems to be working, even the global earth app that spins around works with the up and down key. if you go go to the messaging app you'll notice theres already a message that says 'hello' from 11222, another interesting note the camera shows some 3d bouncing and yeah it asks for us to insert the sd-card so im guessing its using the sd-card as the root and the sd-card is not recognized as an external device, so we would have to partition the sd-card or somehow create two logical disks out of one sd-card?
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
So as for this "downhill battle," whats taking so long on our touchscreen drivers and radio(gprs, 3g, edge, the thing phones are supposed to doi think) drivers? Slackers... Too busy celebrating holidays and new years with your families and friends to spend time glued to your pc writing code and sneaking around the forums like a mean sleek ninja of coding doom. What a slacker... :cool:

Im just Joking really, or am I? :D Just had to poke a little fun at something, a bit bored today. :P

Anyway, can't wait to see the development in android pick up again as long as everyone hasn't moved on to other phones and left me behind again... :P

A bit more on topic, I was not able to start it (the android files linked last page or so) using the latest garmin rom and the last radio he included, though not sure what that was.
[Tilt, TyTN II, MDA Vario III Android Development] disturbed4686:
@shadowline

try the radio listed a page or 2 back. that made it work for me
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
I did, and it worked aswell... Quite odd if you ask me... Quite odd... Anyone that has played around with it a bit more, what keys are mapped to what so far? (that youve found)
[Tilt, TyTN II, MDA Vario III Android Development] ryoojin83:
It is kind of fun trying to trick it to do what you want it to with the buttons we have. so far I have something like:

D,E,F - up 2 (at least in the dialer) EDIT: up once on the home screen

S,W,Z - down 1

Jog Wheel Click - Enter (needed twice to open something)

Jog Wheel Roll - Left (until there is no more left - repeating left, even if only clicked once)

Ok - Menu

End - Back

Send - Power (or screen)

Various buttons in the right two columns of the keyboard are also power (or screen)

Space - Back

I am excited for the screen and keyboard to be mapped! Wish I could help out, but I doubt I could do too much.
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
Thank you, I found most all except the ones on the jog wheel... went on a finger happy craze across my keyboard to find what does what, lol.

Now if the keyboard and touchscreen could be patched for the new image, id be in heaven. :D
[Tilt, TyTN II, MDA Vario III Android Development] greenninja:
Great, thanks for the link.

I now have a shiney new Rom.

Unfortunately Android still hangs with a white screen and the keyboard at the top.
[Tilt, TyTN II, MDA Vario III Android Development] Bimboy:
Keyboard mapping may just need to be compiled into the kernel. It looks like the work for button mapping may have already been done.

I was trying to piece together how button mapping occurs, and it appears that HaRET GPIO logging had been useful in creating that above board-kaiser-keypad.c driver. You can right click/save-as. These are not my drivers, I just have been researching and found them, hoping they might get our keypad mostly working.

There may also be similar work already done regarding the touchscreen. Going to research that next.
[Tilt, TyTN II, MDA Vario III Android Development] dasilva333:
this is great, the board-kaiser-keypad.c used in the current build we are using is 18.3 KB and the new one you provided is 18.8 KB, im sure that overwritting the file and rebuilding is our best chance of making it work i just really wish someone would show me what compiler i need to use to make it, i previously asked someone in the area if they can provide the tools/compilers that allows us to build it ourselves but no one has replied.

found a relevant link:

http://xdaforums.com/showpost.php?p=2269384&postcount=184
[Tilt, TyTN II, MDA Vario III Android Development] KeizerBAAS:
I cannot help you with that, don't know a thing about, but you could try to ask in this channel, where the devs meet...

irc://freenode/htc-linux
[Tilt, TyTN II, MDA Vario III Android Development] mmone3:
Guessing your going to need linux box to do build and also dcordes framebuffer changes need to be included too.
[Tilt, TyTN II, MDA Vario III Android Development] ryoojin83:
So who exactly are the users coding/compiling for this project?

dcordes is in charge of the thread and coding? Is he the only one?

EDIT: SORRY! Just saw the list in the wiki. Answered my own question.
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
I don't even know who is still on or off the project. Some have moved on to newer phones (lucky bastards! I hope you are happy with your shiny new, faster, and larger screen phones! :D lol) and some just haven't been seen on here in a bit.
[Tilt, TyTN II, MDA Vario III Android Development] anod:
Ok, for anyone that wants to help us....

this is the steps, that I think need to do to compile current working core

+ need to add dcodes changes of framebuffer

+ need to change keyboard mapping file for example

Original post:

http://xdaforums.com/showthread.php?p=3092252#post3092252

And below attached the instruction from this archive
[Tilt, TyTN II, MDA Vario III Android Development] ryoojin83:
Your link to the original post doesn't seem to be working
[Tilt, TyTN II, MDA Vario III Android Development] SharpieMarker:
I can also confirm that Android works for me after updating to 1.65.24.36. Can't wait for the touchscreen driver and key mapping...and radio. Definitely awesome. Also landscape mode. Still anxious for this as well.
[Tilt, TyTN II, MDA Vario III Android Development] rkadar1:
Dzo

what happened to Dzo and his new phone? is he still on this project?
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
I don't know... I wish anyone was around to at least try to put the keyboard and touchscreen drivers back in.... I could try but I really do not know my way around the filesystem or even linux commands that well.... This is bugging me soo much!!! I was running android on my phone and kept pushing buttons for no reason just to do anything with it because i want it to work soo bad!! lol
[Tilt, TyTN II, MDA Vario III Android Development] ducamie:
can someone upload the booting files for 1.0sdk so i can try them on my nike?
[Tilt, TyTN II, MDA Vario III Android Development] dperren:
He's been online today - hopefully we should hear from him soon now he's back from his break :)
[Tilt, TyTN II, MDA Vario III Android Development] SharpieMarker:
My next question is, when Android is finally released, is it going to be accessible enough to apply updates for bug fixes without having to reflash a brand new Android rom? Similar to the way Google releases updates for the G1.
[Tilt, TyTN II, MDA Vario III Android Development] dperren:
I think we're probably a while off that stage - unfortunately :(
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
Hi,

Just got back from my trip and I now have a kaiser to play with (thanks anonymous kaiser donor). I've been messing with it a bit and it all looks very similar to vogue. The big difference is the radio version, kaiser uses rpc much more that proc_comm for A11-A9 communication so that will have to be documented (that's what the "unknown" smd channels are). My vogue rpc code should work though.

My aim is to build a single kernel that will boot on MSM7200 and MSM7500 with the MTYPE and radio version used to determine behaviour for stuff like power collapse and audio. I'm working on it now.

Happy new year everybody.
[Tilt, TyTN II, MDA Vario III Android Development] dasilva333:
that is really great but can you just get the keyboard to work on it first please, id like to play around with it more but lack of keyboard makes it kinda useless. that would be great thanks
[Tilt, TyTN II, MDA Vario III Android Development] dperren:
You truly are a brilliant person. Hope you had a good trip, and thanks for the effort both in the past, and inevitably in the future.
[Tilt, TyTN II, MDA Vario III Android Development] dy2592:
Couldnt have said it any better myself. DZO, u have a great New Years
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
hi dzo. you should check the last few pages of this thread starting from here .

rogro made the polaris (very close to kaiser, also msm7200) work in the htc-vogue branch. Might save you some time. I don't know if it's the latest revision, maybe he has it available as diffs against your branch.
[Tilt, TyTN II, MDA Vario III Android Development] agentofboom:
error compiling in Ubuntu 8.10

Ive seen reference to this problem in cross compiling other projects but im not clear on the answers given for the solution...

On the last step of compiling the zimage i get this

make zImage ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-

----

make: arm-none-linux-gnueabi-gcc: Command not found

CHK include/linux/version.h

make[1]: `include/asm-arm/mach-types.h' is up to date.

CHK include/linux/utsrelease.h

CC arch/arm/kernel/asm-offsets.s

/bin/sh: arm-none-linux-gnueabi-gcc: not found

make[1]: *** [arch/arm/kernel/asm-offsets.s] Error 127

make: *** [prepare0] Error 2

------

arm-none-linux-gnueabi-gcc is there...I see it when i "echo $PATH"

so what gives? how do I set my environment so i know this works? I know its something stupid im not seeing.

Mind you this is my first actual self compiling of an image...please speak slowly :-) .

Im sick of not feeling like a contributor so im trying to take what i remember from programming and learn what i forgot .

I WANT ANDROID and I wont stop until i get it!

Hell, I installed it on my friend's eeePC...why not the kaiser?
[Tilt, TyTN II, MDA Vario III Android Development] anod:
Hi All!

I'm doing some tests with touchscreen handler...

What is the way to debug it?

I want to print current coords, there is printk command, but how i can see the output? maybe i need another initrd with CLI?

Thanks for any help
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
Are you reimplementing arch/arm/mach-msm/ts2003.c from the htc-msm branch ?

in the angstrom images, printks are always shown on the fbcon. find the latest initrd I made here. If you need any debugging programs let me know. I can install everything openembedded has and more.

fwiw, tmzt has made this patch for tsc2003.c that allows the kaiser ts to be used with non-android ts apis (like tslib)

@agentofboom

make zImage ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-

this cmdline assumes your toolchain (cross compiler) prefix is inside of the current working directory, which means it must reside in your kernel / . it's best to specify the full absolute path to your toolchain prefix.
[Tilt, TyTN II, MDA Vario III Android Development] disturbed4686:
i wish i understood just one word of that :D Hopefully it means android on my phone soon.
[Tilt, TyTN II, MDA Vario III Android Development] anod:
2dcordes

Thank you. I will check angstrom image

Yes, I compiled ts2003.c with vogue merge, it's working, but there is some problem with coordinate points, want to check if i can do something...
[Tilt, TyTN II, MDA Vario III Android Development] agentofboom:
dcordes,

so this means I should specify it like this:

"make zImage ARCH=arm CROSS_COMPILE=path/to/toolchain/arm-none-linux-gnueabi-"

?

Im sorry Ive read about people having this problem and Im just missing something simple... thanks for your patience and help. I swear im not an idiot...all the time...

Let me know! Thanks.

-boomer
[Tilt, TyTN II, MDA Vario III Android Development] rogro82:
just do the following:

export PATH=[pathtotoolchain]/bin:$PATH

make [configfile] ARCH=arm

make zImage ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
rogro, you had any luck using kaiser-smd.c in the vogue tree? I tried it but didn't succeed.
[Tilt, TyTN II, MDA Vario III Android Development] rogro82:
Well i can make it boot using the board-htckaiser-old-smd code ( which i can also use to make a data connection ), but its a bit strange though.

It wont let me boot into Android, unless i put in a new data.gz which has to extract. If its done it will load up the smd and it boots into android ( I think it has something todo with the delay the extracting is causing ) , had no luck to get the data connection though, but im still looking for the original libreference-ril.so. The one in the image is the one that DZO modified for cdma support.

Already tried setting up a sleep of 20 seconds in the setupmodem.sh but its not bringing me anything consistent.
[Tilt, TyTN II, MDA Vario III Android Development] ddfire:
problems android + tilt

hi

i can boot android and play a little but when i tap on an app that need internet it crash, freez.

other thing the pointer is like one inch upper where i click.

i am not able to do any calls or anything just play and start some apps and then it freez.

what info i can provide to fix it?

thanks
[Tilt, TyTN II, MDA Vario III Android Development] disturbed4686:
you're still running Android .8 dude. People are currently working on getting Android 1.0 working. Give them some time, and soon it will work. Right now 1.0 has no touchscreen or radio or much of anything, but it boots (and is pretty stable) which is huge.

Keep checking this thread and watch the updates come in.
[Tilt, TyTN II, MDA Vario III Android Development] coincoinlapin:
Can someone update the first post? This would stir interest. I think booting 1.0 is a huge step forward that needs to be visible, and not buried in a 200 pages long post...

Besides, the steps to accomplish this feat were quite simple (to me anyway), but I still had to read at least 5 pages to do so: right file dl + right radio update...

Great work, to whomever may be concerned.
[Tilt, TyTN II, MDA Vario III Android Development] supradan22:
I'm sure a new thread once 1.0 gets more stable for the KAISER.
[Tilt, TyTN II, MDA Vario III Android Development] togles:
Can someone please reply with a page / link that I can download the appropriate 1.0 version of android?

Currently I am downloading from the 1 pages link at:

http://linuxtogo.org/~lgorris/kaiser-bootkit/

I am not sure if this represents the latest 1.0 version or not, I am guessing not.

Thanks in advance!
[Tilt, TyTN II, MDA Vario III Android Development] ryoojin83:
On page 183

Post 1824 (I think)
[Tilt, TyTN II, MDA Vario III Android Development] ryoojin83:
I was just curious if anyone could give me a few pointers on how to compile this myself? There was a post a while back that gave specific directions about using git and compiling, and there was also a post a few pages ago with a rar file that had some of the current vogue files, but I am not sure if I am supposed to use git to download the full source, then copy the vogue files over, and compile, or just compile the git source, or what. I hope I didn't miss these directions when I was reading the instructions earlier.

Thanks for your help.
[Tilt, TyTN II, MDA Vario III Android Development] mullins07:
The attached zImage includes keypad and touch screen support for Kaiser Android 1.0

You must use the radio version 1.65.24.36 of course.

Touch screen is not 100% but not too bad. (Why is the Y axis not linear anyone?)

Cursor keys don't work at the moment so I have mapped the front keys as follows:

Call - UP

Menu - DOWN

Menu Left - LEFT

Menu Right - RIGHT

End Call - BACK

IE Button - Menu

Mail - TAB

OK - OK

Compiled from latest htc-vogue commit by Dzo with some changes.

Thanks to Rogro82 and Dcordes for help so far.
[Tilt, TyTN II, MDA Vario III Android Development] Kaiser01:
Thanks a lot!

Keyboard and touchscreen are working for me as described, keyboard has english layout. Was able to add a new contact with full name via keyboard. Best first post I've seen so far!
[Tilt, TyTN II, MDA Vario III Android Development] disturbed4686:
you rule dude, we're 1 step closer to full android on the Kaiser. Now on to the radio! lol
[Tilt, TyTN II, MDA Vario III Android Development] anthonws:
That's one small step for man, one giant leap for mankind!

Thank you!

Best regards,

Anthon.
[Tilt, TyTN II, MDA Vario III Android Development] biscuits1978:
We have got to update the first post if things are cookin' along -- better access to those who could have valuable development experience to get us closer to a functional Kaiser running Android!
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
Hi,

Can you push any changes or send me a diff. I have it booting but the egpio code doesn't work (for some of the buttons), I'll probably port the trout egpio code and change the kbd driver. The smd driver is nearly working, it now supports three different smd read/write mechanisms, does qct make things incompatible on purpose!

We probably need some more organisation to make sure people are not working on the same thing now, I'll push everything I'm doing to the htc-vogue tree and perhaps dcordes can coordinate what needs work. Here is what I think needs to be done:

libreference-ril: needs some small changes to work with htc radio, should be easy. Source is all in the android repo (use cupcake).

audio: needs adsp queue numbers and images to be found along with rpc calls to the audio manager, not trivial but shouldn't be too hard to get the existing code to work.

power collapse: seems to be quite different to vogue, its almost impossible to trace so needs careful examination of the wince code. Without this the battery will probably only last about 12 hours so it is important.

battery level: haven't looked at this yet, probably not hard, it'll be a proc_comm or rpc call and some manipulation of the results.

camera: seems very similar to vogue, again needs some rpc calls and adsp queues documented.

Thats all I can think of now.
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
Iv'e gotten it working on mine too with said radio and such, as noted the touchscreen is at the best, wacked out and isnt very ... right i should say? lol but everything seems to work that should be working at this point, no crashes, no reboots, and it hasnt died while ive left it on which is new.

A few things to note though for development from a user side, (some if not most everyone knows about but im listing anyway)

Battery level always shows charging,

When the screen turns off, the keypad light stays on,

No working radio,

No working camera,

Not seeing the SD Card as an SD card,

The keyboard buttons (ive only noticed the 'FN' buttons so far) are not mapped correct, EX. 8 is 6, 2 is 8, 5 is 5, 9 is also 6, etc.

The keypad buttons are not properly mapped as the original post says aswell.

The screen is not properly aligned,

Most UI items are not made for QVGA and are not sized properly (example "Music" shows buttons with icons outside of their graphic boundries.)

Also a few notes on how to use it as it is right now,

To roll down the top bar, tap and hold in the far upper left corner as that is the closest point that seems to be aligned.

an easy way to graphically check how it is aligned go to programs menu > api demos > Graphics > Fingerpaint and use the stylus and draw around the edges of the screen or just play around with it.
[Tilt, TyTN II, MDA Vario III Android Development] mullins07:
No problem Dzo.

I will try to send a diff tomorrow when I get back to my machine. The kaiser board code would not boot and the vogue board code would, so I used the vogue board as a starting point and began to bring across kaiser relevant devices etc.

It is compiled using CONFIG_MACH_HTCVOGUE as it would only boot with vogue-smd and the vogue specific stuff.

The touch screen driver is another item which is not perfect yet either and might want to go on to the list.

When you push everything and the kaiser config compiles and boots no problems then it would be great to co-ordinate from there. Just need to get a commit which works first I think.