yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] nicko666:
Hi, I have only recently got my Orbit 2 and am getting familiar with the polaris forums...

This looks great and I followed the above advice and the bits ovindhal had already put in I can confirm that I can launch Android on my phone, I have not changed the ROM at all it is the shipped O2 rom.

I am no developer so will sit and watch the smart folk doing their magic but if you want me to test anything or confirm anything just shout...otherwise this is just a Hello!!:D

PS Simple things please simple minds and I love the Globe i can spin with my fingers!!!!!:p
[Touch Cruise Android Development] ovindahl:
Gotten it to boot a couple of times now (like 1/10 tries), but I always get a huge graphical bug =/
[Touch Cruise Android Development] Scalap:
Hi everyone,

I tried to build myself the zImage but i'm stuck at the last step :

I tried to quote the line saying

but the result was worse...
[Touch Cruise Android Development] premy:
Here's a small patch to correct the graphical bug we've been facing when trying to use the Kaiser zimages. It needs to be applied against the latest version on linuxtogo.

Let me know if it works for you.
[Touch Cruise Android Development] imfloflo:
can anybody compil a new zImage with this fix please.thanks
[Touch Cruise Android Development] premy:
You can try this one.
[Touch Cruise Android Development] cybertron:
it works!!

but the touchscreen calibraion is off and no buttons except powerbutton seems to work

but hey

great job!!
[Touch Cruise Android Development] imfloflo:
This rom won't boot with 0.5.2 version of haret. i will try with the modify version of 0.5.1. And post conclusion later.

Is there temporary files when haret crash and I soft reset my phone that i must delete before i restart haret ?
[Touch Cruise Android Development] Scalap:
thank you premy ! only two posts and already a solution !! You are a promising one !

like cybertron said, you solved the display problem. Now, the keys have to be reassigned, because they are yet assigned to letters. Therefore, Android automaticly opens the contact screen when I hit them and I can't leave it.

Thank you premy, we made one big step in the direction of a working android on our polaris !
[Touch Cruise Android Development] imfloflo:
@Scalap > What is your Haret version ? cause mine won't boot this zImage !
[Touch Cruise Android Development] shippyt:
Well done that man! Mine boots perfectly, we just need to work on the screen calibration and mapping the buttons now. I'll take a look on the Kaiser forums to see how to do this.

:)
[Touch Cruise Android Development] dubbeld00:
Here you have a better implementation of the gpio, because kaiser has a whole keyboard that you have to make working...

{.gpio=31,.code=0x6a}, // Right
{.gpio=32,.code=0x69}, // Left
{.gpio=33,.code=0xe8}, // OK
{.gpio=34,.code=0x6c}, // Up
{.gpio=35,.code=0x67}, // Down
{.gpio=41,.code=0xe5}, // Menu
{.gpio=42,.code=0x9e}, // Back

now you only have to configure this... (no, this isn't the working configuration!).

I've also attached the zImage with this implementation of GPIO, you will see that it doesn't go right into the contact screen. (But you can't do a thing yet).

Hopefully someone can do something with this info :)
[Touch Cruise Android Development] Scalap:
imfloflo :

I'm using a beta version of Haret :
[Touch Cruise Android Development] schaggo:
I hope the htc dream will feature similar hardware to the current generation of htc devices. Because once that one is out, it should be a 1-2-3 task to port the working android onto the current platforms (which then will be outdated anyway).

Good to hear that you guys are making progress. I'm kind of in the mood to ditch my Vista for some Linux, but I cant, there's no WM6.x interoperability... :mad:
[Touch Cruise Android Development] cybertron:
works quite good here too...

I will try and read on about gpio
[Touch Cruise Android Development] dubbeld00:
Never heard of VMware or virtual PC? With ease you can get Ubuntu running... Create a share on your windows device and you can bake your own zImages, but it on your windows share (from ubuntu) and get it on your mobile :)

But ehm, now we got this far, and we have people with some experience, when shall we really start development? (So get ourselves singed up to the git from linuxtogo) ;)

It's just general input and output, if you press a key an event will take place; the only thing you will have to do is fetch this event and assign a task to it. (there was an initrd with only a command line on the kaiser thread (you can find the link on page 1 of this thread) they used it to fetch the GPIO events I thought...

You can also use EGPIO (which I guess stands for extended GPIO) but since we only have to assign 7 events, why should we be using that? It's not a full qwerty keyboard ;).
[Touch Cruise Android Development] imfloflo:
Can anybody make a new cab version with all files and the lastest zImage which work cause now my haret won't launch any zImage anymore :(
[Touch Cruise Android Development] premy:
You might be running into mtype mismatch problems.

The zImages recently posted here have been compiled for mtype=1553 (kaiser). You have to make sure your default.txt declares the corresponding mtype :

set MTYPE 1553.

If you've been playing with vogue zImages, you might have a vogue default.txt, with the corresponding mtype (1667).
[Touch Cruise Android Development] dubbeld00:
What I wanted to ask, is the touchscreen working in Vogue? (because I saw it doesn't load the kaiser touchscreen at all (at least the config for this). From what I remember the touchscreen was working on a previous build of Vogue.
[Touch Cruise Android Development] premy:
AFAICT, the vogue zImages use their own touchscreen driver (vogue-ts.c), not the kaiser ts driver (tsc2003.c).

As a side note, I think the vogue code from the linuxtogo repository is basically broken (never been able to make it work). I believe the working vogue images floating around are built directly from the android repository and Martin Johnson's patches. Not from the linuxtogo code.
[Touch Cruise Android Development] premy:
Here are some values I've found:

GPIO19: wheel left

GPIO20: power button

GPIO21: power cord plugged/unplugged

GPIO29: camera button half way

GPIO37: wheel down

GPIO38: wheel up

GPIO42: ts tap

GPIO76: camera button full

GPIO90: wheel button

GPIO91: wheel right

GPIO94: SD card inserted/removed

Can somebody confirm ?
[Touch Cruise Android Development] dubbeld00:
I'm creating a zImage at the moment using these values... give me 30 minutes ;)

Edit 1:

:D You are the man!

GPIO38: wheel down

GPIO37: wheel up

Up was down and down was up, fixed this thing, now the keys are working :D

Edit 2:

Attached the working zImage. The only keys we now have to get are the "call", "hangup", "gps" and "internet".

Edit 3:

Back key now is "camera button half way"; allright... checked the touchscreen kernel/drivers/input/touchscreen files, but can't find your vogue-tc.c (i'm to lazy to search further) can you tell me where you found it?

Old vogue file was working on polaris with touchscreen! So if we can compile that one :)

Edit 4:

Added a zImage test, can someone test this one if the touch screen is working? (zImage 3 is fully working with keys zImage TEST is a test build!)
[Touch Cruise Android Development] be_vigilant:
OK using the test zimage it seems the screen is reversed vertically.

If I press and drag my finger bottom to top the top bar extends down as if I am dragging from top to bottom.

Hope that makes sense. Buttons working OK though :-)

well done man! :D

The apps now load OK with no crashes. I can spin the glob around in 3D and it doesnt slow down like in WM6 it would!
[Touch Cruise Android Development] dubbeld00:
Strange... I added: y=ADC_MAX-y; so it shouldn't be upside down anymore... premy can you find me the driver of the vogue? (only found the modified one).

The globe is indeed spinning nice :D no lag or whatever ;)
[Touch Cruise Android Development] premy:
You can get the vogue source code by applying M. Johnson's diffs ( http://it029000.massey.ac.nz/vogue/diffs ) against the android repository (git.android.com).

If you're only interested in vogue-ts.c, you can get it directly from the diff file, since it's not in the android repository (will save you the time to download the whole source code).

The nice thing is that vogue-ts provides an onscreen keyboard, which is not included in the kaiser source code (they don't need it). We will need such a beast.

I was working on this, actually. But if you want to do it, that's fine. There's plenty of work elsewhere. I'm especially thinking of starting a board_htcpolaris of our own, so that we could integrate our code with the linuxtogo repository in the end.
[Touch Cruise Android Development] schaggo:
Ever heard of VirtualBox? IMHO its more powerful than VMware and I'm not even gonna get started on VirtualPC... *chchch*

I'm posting this from an Ubuntu 8.04, getting a distro running is out of question. Still in question is Ubuntu fully replacing Windows on my laptop. This is a no-go since Linux isnt synchable with WM. Or vice versa, WM isnt synchable with Linux.

Having no idea of development, I dont want to and probably cant help. I'm just going to be a user being happy about Linux compatibility. But I want the full Android flashable ROM, not a WM loader.

Whatever, I'll let the people with knowledge now do the talking and just gonna watch this thread. I hope interesting information of other threads/forums (Kaiser...?) will get crossposted.
[Touch Cruise Android Development] ovindahl:
It isnt upside down, but something isnt right for sure. If you go to the dev tools from the "all" tab on the homescreen, you can find "pointer location" which shows you where your touches are registerred. For me it doesent seem to be any logical system for it; almost whereever I press, it is registered in the uppermost part of the screen and is responding weirdly to my touches. Guess it wouldnt be too much of a problem for the skilled people here too fix though.

Also, if someone could make a working on-screen keyboard would be fantastic.
[Touch Cruise Android Development] cybertron:
great work all of you ! It keeps getting better and better!

I've noticed that it seems to freeze after 10-15 minutes or so, but this might be normal (reda about something similar in the kaiser thread)

otherwise it is the touch thingie,

according to the pointer program it seems to start at the center of the screen, and up is down and vice versa. and left seems to be right so it feels that it is very similar to the screen being up side down problem.
[Touch Cruise Android Development] Scalap:
Thank you dubbeld00 for this new version.

I went in almost every corner of the android and it's working great ! I tried to make a call but we don't have a call key yet, have we ? And I also tried to create a new contact but I didn't had a clue how to do that !!

I'm gonna try if we can have any data transmission through it.
[Touch Cruise Android Development] premy:
Here's an update. It should solve the touchscreen issue (still some misalignment on the left border of the screen, though).

It also provides an on screen keyboard (press camera key to hide/show the keyboard).

Back is mapped to the hang up key.

Tell me if it works, I'll clean up the code.

Edit:

new zImage attached, correcting the calibration problem.
[Touch Cruise Android Development] be_vigilant:
Latest zimage and touchscreen is working for accessing apps.

However when I launch the keyboard and type they seem to be one letter out. Like if I hit E and R will showup on screen. Not sure if the touch calibration just needs fine tuning or something.

When I launch the pointer developer tool it also shows a slight fine tuning is needed.

---

Correct me if I am wrong but GSM is not working yet. The vogue uses something other than GSM thats why they can make calls and receive texts etc.

I dont think even the kaiser has GSM function yet :confused:
[Touch Cruise Android Development] dubbeld00:
Nice job, keys are working, touchscreen is working correctly :) What's next... ;)

And to schaggo, didn't mean to flame you, was in a bad mood writing that post

Great idea (was hoping someone would eventually do this)... BTW the new rom doesn't always boot (1 out of 6) never had that problem using the kaiser codebase... don't know if it's my device or that more people are noticing this problem.

Edit:

Premy I don't want to reinvent the wheel, can you please tell me where you are working on? Maybe share the code... and so on ;)
[Touch Cruise Android Development] Scalap:
+1, I also would like to see how you did.
[Touch Cruise Android Development] premy:
It's not much more than back porting the developments from the vogue implementation (msm_fb.c, vogue-ts.c).

I need to do some clean up, though, so it might take a bit of time.
[Touch Cruise Android Development] imfloflo:
I would like to now, why android won't boot on my Cruise since the lastest zImage?

What the rom have to do with this cause i really like Bepe 0.67 and don't want to flash another rom for the moment, so I try to find how can I make it boot.

In the default.txt there was RAMSIZE and another offset before, i can't see anymore in the new default.Txt is it important point ?
[Touch Cruise Android Development] dubbeld00:
That's the same what I did, but I wanted to make a whole "new" set of files (so board_htcpolaris and so on) since I was still modifying the kaiser files. Don't you have an IM; (MSN, ICQ or whatever) don't want to create the same code as you.

The only "new" function I created is already shared here: http://xdaforums.com/attachment.php?attachmentid=92124&d=1213278332; the implementation of the gpio (which just is a rip off of the vogue board (I'm lazy... ;)))

The only thing is, there is something in the vogue codebase that is giving my polaris a hard time to boot that zImage (don't know if you also noticed this) never had it using the kaiser image.

Hahaha you really want to have it working don't you ;) well for me it also won't boot all the time (only got it working once, tried it 7 times) try booting without SD-card; maybe that's working... Else try hard resetting your device ;) Or just wait till there's a new zImage :)
[Touch Cruise Android Development] imfloflo:
Yes i really want :)

I try 4-5 times with each zImage, soft reset and reboot are boring, too long :p

No hard reset please :). So I will wait...

Can a modo or someone else make a post or a cab with the lastest zImage when new zImage comes and post it in the first post ?
[Touch Cruise Android Development] dubbeld00:
Well we can put it in a CAB but it doesn't make a difference... the only thing the cab will do is put it in the "Android" directory... the same as you are doing at the moment, so it probably still doesn't work.

(and I can't see the difference, download cab, put the cab on your device, run the cab, click 300 times to get it installed

or just, download the zImage and put it in the directory)
[Touch Cruise Android Development] cybertron:
Best way that always seem to work is to have battery fully loaded and have either the sync cable or powercord stuck in the usb.

that way it always boot for me
[Touch Cruise Android Development] premy:
Here's a patch against the latest linuxtogo version. It includes some small enhancements compared to my last post.

I've tried to set up a clean basis for further polaris specific developments.

Please note that I now use a polaris specific machine type, so that your default.txt file should now specify:

MTYPE=1723

You'll find my default.txt attached.

Please review, comment and test.
[Touch Cruise Android Development] be_vigilant:
wow nice progress again :-)

The keyboard now lines up perfectly. Some of the API demos are cool. The 3D transitions between photos is just the same as in Touchflow 3D on the diamond lol And they run smooth as in android
[Touch Cruise Android Development] Scalap:
This version is working great. It last around 10 minutes on my polaris.

And this is 5/5 for boot : imfloflo, this time, it is gonna work !

Where did you find the 3d transitions be_vigilant ?
[Touch Cruise Android Development] cybertron:
I can only agree, it is very nice to see that this phone has potential o be smooth and extreemly fast!!

no lag what so ever :D

now, if we only could get gsm/3g/edge or whatever working, :D

great work premy/dubbeldd00
[Touch Cruise Android Development] be_vigilant:
If you load up all in the bottom right corner. then on the left menu which comes up click on API demos.

Have a browse through the graphics and Animation demos :-)

This seems to be rock solid and has booted 5 out of 5 for me so far. I am using the latest udK Vega rom.

For anyone wanting to try the latest version out I created a .cab file for an easy install

http://www.4shared.com/file/51548129/95bc2828/Polaris_Android.html

Install to device memory not SD card ;-)

All credit to premy/dubbeldd00. Once the .cab is installed you can easily update andoid by just dumping the latest zimage from these talented people into program files\android directory.
[Touch Cruise Android Development] Scalap:
Ok ! I think I don't use the last version initrd-android, because i don't have API demos on my left menu.
[Touch Cruise Android Development] imfloflo:
Hey i'm going to test it right now !

Downloading... Installing....Testing...

All work good very thanks i don't touch until the next good release :p

I don't see any Keyboard :$

When i click on the top of the screen I see a white page and i can scroll this one until the bottom of the page what is her purpose?(what is it for ?) sorry bad english but i can't explain it.
[Touch Cruise Android Development] be_vigilant:
press the camera button to bring up

the soft keyboard
[Touch Cruise Android Development] ovindahl:
The white page is where you see your new messages/unanswered calls.
[Touch Cruise Android Development] maximos86:
is there a way to make calls or is it not possible yet?
[Touch Cruise Android Development] psychedelicNerd:
Thanks :D

Officiallyy... Thank You. This has been the first version "ever" that has been able to boot up successfully on my Cruise. Thanks to Premy for putting in the hard work and everybody else too.

Looks great. Now if only the Radio started working :D
[Touch Cruise Android Development] be_vigilant:
No way to make calls or any GSM functions yet.

I really need to get my ubuntu sorted out so I can take a poke around
[Touch Cruise Android Development] Scalap:
these fonctions are working on the vogue.

it's just a matter of time before we have it working too.
[Touch Cruise Android Development] premy:
Guys,

I must have been tired when I generated the patch file I attached to my last post. Half of the changes were missing. I've modified my post to attach the proper patch file (hopefully...). Sorry for that.
[Touch Cruise Android Development] shippyt:
The white screen that pulls down from the top is the screen lock, you pull it down like a window blind, works brilliantly :)
[Touch Cruise Android Development] obstler:
I just tried that on my polaris. installed to main mem. launched haret and pressed the run button. device just hangs at the end of the booting linux progress bar. anything else needed to start that up? launch anything before haret, etc?

thanks.
[Touch Cruise Android Development] shippyt:
The patience of a saint usually helps, the older builds were booting something like 1 in 20. I'm downloading this version now and will test shortly.
[Touch Cruise Android Development] maximos86:
i just turned off 3G and it booted after having this problem
[Touch Cruise Android Development] imfloflo:
can anyone release a new version of zImage with the lastest patch please :)

what can i do i my git pull doesn't work anymore ?
[Touch Cruise Android Development] be_vigilant:
Its not a 100% boot rate. If it hangs reboot your phone and try again. Just keep trying it will boot :-)

Some people say if you press the listen for connection waite 3 seconds then hit run you get a better boot chance rate. I think this is just placebo effect hehe

I find I get a better boot rate if I reset my phone then the first thing I do is launch android. That way maximum memory is available to haret.
[Touch Cruise Android Development] dubbeld00:
Brilliant! (throws his ported keyboard and vogue-ts in the recycle bin ;)). I'm having a look at the Radio part (for SMS and so on)... Don't think the vogue implementation is the same... Already tried it? At the kaiser thread the are also stuck here...
[Touch Cruise Android Development] dubbeld00:
Alright for you all: How to apply the patchfile:

first get all the android files using: http://xdaforums.com/showpost.php?p=2271238&postcount=73 start at section "Now we can bake a zImage."

then log on to root user (if you know Linux, you don't have to do this; but you have to chown and chmod yourselve)

sudo -i

________________

Patching

1. get the patch file from premy

rm -R latest_patch*
wget http://82.168.116.233/~android/latest_patch

* I try to get this file up to date

2. now go to ~/android-kernel/kernel

cd ~/android-kernel/kernel

3. run the patch file, so that the modifications done by premy, will be loaded in the ~/android-kernel/kernel dir

patch -p1 < ../latest*

If it says: "Patch detected; just answer N"

________________

Stay up to date

If you want to get the latest git, go to your a directory:

cd ~/android-kernel/kernel

Now get the latest changes

git pull

________________

Share your work (create a patch file)

If you've changed something within the kernel/ directory, and you want to share it with us; then you can create a patch file:

1. Go to the android-kernel/kernel folder

cd ~/android-kernel/kernel

2. Now give the following command (so it will get the changes)

git-diff > ../new_patchfile

You can find the patch file in ~/android-kernel/new_patchfile

________________

Create a zImage

Prepare default .config for Polaris:

cd ~/android-kernel/kernel
make htcpolaris_defconfig ARCH=arm

And compile the kernel to get zImage (takes a minute or two):

export PATH=~/android-kernel/arm-2008q1/bin:$PATH
make zImage ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-

Now copy ~/android-kernel/kernel/arch/arm/boot/zImage to your phone (in the folder Android).

________________

Undo all the changes

If you've modified files, but you've messed it all up, you can easily undo those changes (so you will get the original kernel)

1. Go to the kernel directory:

cd ~/android-kernel/kernel

2. Remove all extra added files:

git clean -fx

3. Reset the git:

git reset --hard

Now you can apply the patches as described above

________________

Got comments? Please share them;

Maybe time to create a new "Android developing thread"
[Touch Cruise Android Development] premy:
I'm currently looking at this, yes. I'm reasonably confident we should be able to make it work. We're almost there.... I'll let you know if I make any progress.
[Touch Cruise Android Development] aitsch:
hi,

i've tried the files from http://it029000.massey.ac.nz/vogue/ on my "XDA Orbit2".

The boot process has a infinite loop at the TouchScreen Calibration.

When i touch the screen the device shows the coordinates of the touch but the boot process doesn't goes on.

what can i do?

cheers

aitsch
[Touch Cruise Android Development] corpus:
hmmm... you are talking about apps, gsm etc... but on my polaris only the kernel boots normally. i`ve tried with 2 different ram disk images: i only see blank screen (and sometimes white bar appears on top of the screen) or red bar in the middle of the screen (with other initrd). but on-screen-keyboard works very well :), i can get to it by pressing camera button :).

how do you get to all android apps? did i miss something?

anyway - great job has been done!!!

p.s. i will try to use console initrd and play with it :)