yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] prisonking101:
try my build of android for the HTC POLARIS (2007 Model)

http://xdaforums.com/showthread.php?t=926561
[Touch Cruise Android Development] Elvez:
What's up with Android on Polaris

I'm really into this Android on the Polaris/Orbit2 thing - after all a nice OS seems to be waiting right around the corner.

Could anybody summarize what the main problems are that keep Android from running on the Orbit2? I mean, I've seen a couple of videos of Android working just fine (don't know on which devices though) and I'm wondering why this isnt't possible on the Orbit2 so far. Would that be because there's no functional linux around for our device?
[Touch Cruise Android Development] cybertron:
does anyone have all the files in one place? I have downloaded 10 different haret/default.txt and so on and one combination gave me a linuxlogo and a green keyboard.

Does anyone have a combination of files that gives them something nice ?

please post these four/five files that works for you

/CyberTron

ps. I have searched a lot! in this thread and kaisers...
[Touch Cruise Android Development] joey jojo:
english translate http://translate.google.com/transla...tc-dream_25471.html&hl=en&ie=UTF8&sl=it&tl=en

.wysiwyg { background-attachment: scroll; background-repeat: repeat; background-position: 0% 0%; background-color: #ffffcc; background-image: none; color: #000000; font-family: Verdana, Arial, Arial; font-style: normal; font-variant: normal; font-weight: 400; font-size: 10pt; line-height: normal } p { margin: 0px; } .inlineimg { vertical-align: middle; }
[Touch Cruise Android Development] Mormy:
Sorry, you're right. I link an Italian web page :(
[Touch Cruise Android Development] imfloflo:
@cybertron : i was able to launch Android but with the last release it does'nt boot :s
[Touch Cruise Android Development] psychedelicNerd:
Do you have the set of files that you used which worked? If yes, could you make em available somewhere? I have an HTC Touch Cruise and I have tried various versions of Haret, Initrd.. and zlImage but to no luck in getting Android running. The max I have reached (that too once) was upto the point of the red dancing dot.

Thanks
[Touch Cruise Android Development] areenahmed:
Do you have the set of files that you used which worked? If yes, could you make em available somewhere? I have an HTC Touch Cruise and I have tried various versions of Haret, Initrd.. and zlImage but to no luck in getting Android running.

Ive the same problem so pls help us.
[Touch Cruise Android Development] imfloflo:
I used the files in the first post and i tyr other init and zImage which works i don't remember and i overwrite them sorry.
[Touch Cruise Android Development] Mormy:
I have a very newbie question:

If I try to flash my orbit 2 with android and I can't even boot, like many other people :( , how could I re-flash my wm 6.1 rom??
[Touch Cruise Android Development] imfloflo:
Launch Haret if it doesn't boot just push the soft reset button off your Htc.I just reboot on wm6.1 without losing data.
[Touch Cruise Android Development] Mormy:
This week end I'll take a look to android :)
[Touch Cruise Android Development] imfloflo:
There is a new thread very interesting here http://xdaforums.com/showthread.php?t=396782
[Touch Cruise Android Development] Mormy:
Maybe I did something wrong, but the only thing that I've got is the "touch screen calibration" with sever number.

If I touch the screen the number changes, but nothing more :(
[Touch Cruise Android Development] Scalap:
Hello, I made a little movie to show what happens when i try to boot Android :

http://www.youtube.com/watch?v=QJaGaTy-Pmw

Tell me if you know what is going on !
[Touch Cruise Android Development] cybertron:
you've got more than most of us here, what did you do? which files? (care to upload to megaupload or similar)?
[Touch Cruise Android Development] be_vigilant:
if you use the very first andoid which came out on the vogue site then android works fine. I had it loading up and staying loaded. If you tried to load any apps or anything it just hangs. But you could browse through the menus.

Once it even crashed and started making a beaping sound even though there are not supposed to be any sound drivers or support haha must have been a BAD crash!

The newer andoid files seemed to be more customised to the kaiser and the vogue and as such dont load on our HTC TC.
[Touch Cruise Android Development] dubbeld00:
http://www.youtube.com/watch?v=64LYnTxhj44

mine is working though :P (yeah... it's an old version of it... no applications are working on that version) BTW, I also noticed that it isn't working on all ROM's (Bepe's ROM always worked fine, but can't get it working on the ROM of Lexi)...

Also you have to download a Haret version of haret-20080304 or lower.

I also have the grapical issue on the latest version of Android. I guess there is nothing you can do, or you will have to cook a version for this device...
[Touch Cruise Android Development] imfloflo:
I have the same visual bug .
[Touch Cruise Android Development] shippyt:
Hi guys

For those that have got as far as the visual bug can you upload the files you are using as a .zip or something, I've tried various versions of each file but haven't managed to get past the cylon screen yet.

Thanks in advance

Tim
[Touch Cruise Android Development] ouioui01:
+1 :D

cheers
[Touch Cruise Android Development] imfloflo:
http://rapidshare.com/files/112623915/SH4Y_s_Andriod_UI_Installer.CAB

http://xdaforums.com/attachment.php?attachmentid=88257&d=1211818766

http://www.handhelds.org/~koconnor/haret/haret-0.5.1.exe

all my files with the graphic bug from this post http://xdaforums.com/showthread.php?t=396782
[Touch Cruise Android Development] shippyt:
Thanks imfloflo, am downloading now. :D
[Touch Cruise Android Development] shippyt:
Exactly the same problem as you imfloflo with the messed up screen, its a step in the right direction though.
[Touch Cruise Android Development] Scalap:
Now the question is : how to change that ?

Is the problem in the zImage or in the initrd_android file ? That must be in one of them.

How to edit these files ? I think we need some special tools because these files are unreadable the way they are given to us. Something like a "decompilateur" for those who can speak french.
[Touch Cruise Android Development] cybertron:
you need a linuxdistro, and Android SDK, then you compile your kernel (zimage + initrd) from an .config

haven't done this myself yet so this might not be entirely true, but something along this path

btw, the zimage is the kernel and the initrd should be the modular part of the kernel if it is similar to linux.
[Touch Cruise Android Development] corpus:
kernel + initrd

zImage is the kernel and (as far as I can see from the .config - http://it029000.massey.ac.nz/vogue/.config) it is build without support of loadable modules. initrd is the image of the ram-disk (where all applications are stored) and it will be mount during the boot.

to build the kernel on a host machine it is necessary to install arm toolchain.
[Touch Cruise Android Development] cybertron:
http://xdaforums.com/showthread.php?p=2213586&highlight=build+kernel#post2213586

there you have more specific detail on how to build...

and now with the latest zImage i am having the same screen problem..:D but hey, it boots!
[Touch Cruise Android Development] sedde:
so i re-installed your cab, i dropped haret and renamed it, i tried to boot, it didnt boot at all, i tried cleartemp and it still wont boot.

:mad:

EDIT : it actually booted after 150 tries, but the graphics bug is so intence that i cant do anything :<
[Touch Cruise Android Development] shippyt:
In the diffs.htm file there's reference to pixel_data 240 (the vouge screen is 240 x 320 and the Polaris appears to be 320 x 240), just a thought but that might be why the screen goes odd when loaded on the cruise??? Then there is also the line "Arr Matey! A Hairy Bilge Rat" in this file so it might not reference anything valid :p
[Touch Cruise Android Development] shippyt:
ignore my last post, they've all got 240 x 320 screens. I get the crazy screen regardless of which zimage i'm using, interestingly I get a much higher boot success rate now I've moved the folder from my SD card onto my device (1 in 5 rather than 1 in 20).
[Touch Cruise Android Development] dubbeld00:
Also turn off 3g, wifi and don't connect to your PC (USB). This will also affect the boot success rate.
[Touch Cruise Android Development] Scalap:
The problem is, my linuxdistro doesn't work anymore... pb with Ubuntu 8.04 who doesn't recognize my 3D card : I get nearly the same graphical bug than on my polaris with android !

An idea is to find the older version of the Initrd and zImage files and to look which are the differences and then which of them is refering to the display. Now we have to find somebody able to do the comparison!
[Touch Cruise Android Development] cybertron:
i will take a shot quite soon, but I will reinstall my distro tonight

so perhaps tonight/tomorrow...
[Touch Cruise Android Development] imfloflo:
i successful create my first zImage but now must to find what is the cause of the visual bug.

What is the role of init-android files ?
[Touch Cruise Android Development] cybertron:
I read a little more on the initrd file, it is our "main memory", it contains our applikations and maybe other stuff, but it is like our internal flashdisk.

it loads everything up in our phones memory at boot time
[Touch Cruise Android Development] imfloflo:
there is an new zimage avalaible on this site http://it029000.massey.ac.nz/vogue/

i download all filles and launch Haret i see the boot screen without graphical bug, next i see the red loading light and sht blacks.

There is no graphical bugs but i cann't running the desktop too bad !

the zImage from my lastest post http://xdaforums.com/showpost.php?p=2263118&postcount=61 won't boot at all.
[Touch Cruise Android Development] dubbeld00:
Well... Compare:

- http://it029000.massey.ac.nz/vogue/.config

with:

- ~/android-kernel/kernel/arch/arm/htckaiser_defconfig

What you will see:

- CONFIG_HTC_EGPIO=y won't be used in the working .config (line 553)

- CONFIG_FRAMEBUFFER_CONSOLE_ROTATION Also won't get used (line 607)

This, and we use the CONFIG_MSM_KAISERSMD, CONFIG_MSM7X00 and CONFIG_MACH_HTCKAISER.

First try if CONFIG_HTC_EGPIO and CONFIG_FRAMEBUFFER_CONSOLE_ROTATION may resolve the problem (by commenting them out one by one, and together)

If that's not working, we have to check the source of the CONFIGS of the kaiser, which we can find in the ~/android-kernel/kernel/arch/arm/mach-msm folder:

- board-htckaiser.c (problem might be in here)

- board-kaiser-keypad.c (this will only map the keypad)

- kaiser-smd.c (or in here)

Maybe a developer of the source can help us find the problem. Since the Kaiser is more related to our device then the Vogue, it's better to check this first. (I don't have the time to really get into this, I really hope someone can do something with the given info).

Good luck!

______

EDIT: I tried one thing; can someone check the attached zImage

EDIT2: tried myself, still same bug. commented CONFIG_FRAMEBUFFER_CONSOLE_ROTATION out, but it didn't fix the problem.

I also guess CONFIG_HTC_EGPIO doesn't solve it eighter... so maybe someone can contact a Kaiser developer, who can give us a tip.
[Touch Cruise Android Development] imfloflo:
i tried your zImage but it won't boot, stay on the haret screen.
[Touch Cruise Android Development] dubbeld00:
Sometimes you will have to run it multiple times (on my ROM it boots all the time (it's the VEGA R2)).

More screenshots

Some screenshots of Android :P Hoping someone likes it and try to fix it for the polaris ;) (it shouldn't be that hard...)
[Touch Cruise Android Development] imfloflo:
i know i try a lot but it won't boot , it stays on the haret loader. i have Bepe 0.67 Rom.
[Touch Cruise Android Development] dubbeld00:
Does it say MSM7500? Or a Generic ARM Machine? (you will see this in the messagebox within Haret). If it doesn't say MSM7500 it won't work.

Also you have to use Haret version 0.5.1 or 0.5.2 20080304 (i prefere the last one) Don't use the latest version from handhelds.org (builds higher than 20080304), they won't work!

Don't put haret (and the other files) on your SDCard, but onto your phone memory.

You can get a high boot success rate (9 out of 10) with the Vega R2 ROM; also:

- disable 3g

- disable wifi

- disable bluetooth

- you have to be connected onto your phone network

Then just press Go...

____________

About solving the problem; btw the problem seems to be in: board-htckaiser.c (this will allocate all the memory; related to video and normal ram) maybe it is better to start our own code... hopefully there will be developers starting this... (I don't have time).
[Touch Cruise Android Development] imfloflo:
It says MSM7500, with the 0.5.2 it boots i see the keyboard and the red light, but its block on this red light and i must soft reset.

I disable 3g,wifi,bluetooth, it's on my device not on SD and i just press Go.

Do you think the rom of the Cruise change anything in the boot ?
[Touch Cruise Android Development] dubbeld00:
No, as long as it boots (so really see that it is booting up linux) your ROM is ok, but if it always stays in the Haret program, or doesn't boot to linux all the time, changing your ROM to VEGA R2 is recommended.

But I stop answering these kind of questions; related to booting up Linux... It is all mentioned before; I hope we can now focus on getting andriod to work.
[Touch Cruise Android Development] imfloflo:
it's not question about booting linux just the zImage which blocks during the boot and that is the probleme cause old zImage boot and i can use android but with the lastest release i can't so i would like to understant why to help the project !

i comment the line about "set cmdline ppp.username=mobile@jamamobile ppp.password=telecom" and its shows the red light more but blocks too
[Touch Cruise Android Development] shippyt:
I can boot this latest image dubbled but still have the same problem with the mangled screen, some of the screen is readable on this one though. I could tell that I had opened the dialler :)

It's a step closer

I'm using Bepe's ROM btw but will be upgrading to the diamond ROM
[Touch Cruise Android Development] Scalap:
I'm gonna try the zimage you made dubbeld00. I will give my impression soon.

Edit : Still the same problem with the display. I tried with two version of the initrd file, one of them being the latest one. With the latest one I had the subjective feeling that the screen was scrolling more than with the other one.
[Touch Cruise Android Development] cybertron:
i'm trying to compile my zimage but gets this error

<code>

root@mkl-laptop:/home/android-kernel/kernel# make zImage ARCH=arm CROSS_COMPILE=/home/android-kernel/arm-2008q1/bin/arm-none-linux-gnueabi-

make: /home/android-kernel/arm-2008q1/bin/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: /home/android-kernel/arm-2008q1/bin/arm-none-linux-gnueabi-gcc: not found

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

make: *** [prepare0] Error 2

</code>

the compiler is there and executable
[Touch Cruise Android Development] imfloflo:
Have you install all the package "git-core git jfsutils xfsprogs quota isdnutils-base nfs-common oprofile" try to redownload the files
[Touch Cruise Android Development] dubbeld00:
Did you check the requirements at the bottom of this post: http://xdaforums.com/showpost.php?p=2271238&postcount=73.

I presume that the directory "/home/android-kernel/arm-2008q1/bin/arm-none-linux-gnueabi-" exists and has content (so you've downloaded and extracted it). It seems that it doesn't exists... If so, download it again...

"/home/android-kernel/arm-2008q1/bin/arm-none-linux-gnueabi-gcc: not found"
[Touch Cruise Android Development] Mormy:
I'm using Vega R2 and the duoblled00's zimage + haret 5.2

It starts, but I obtain a not centered screen with "contact" "www" and something else that I coud't catch.

It is possible have better result??
[Touch Cruise Android Development] Scalap:
mormy you have the same problem as everyone in this topic. some people are working on a solution. so wait and see !
[Touch Cruise Android Development] dubbeld00:
I really hope someone is fixing this problem... We have to start our own development, because it seems the kaiser really differs from our device. (Now we are using scripts made for Kaiser).

I want to help making it work on our polaris, but I simply don't have time to pull the whole development... I'm seriously hoping someone over here can start developing for our polaris. (Haven't seen a volunteer who really is into linux and can make scripts (like making our "keyboard" work)). Also we need a device code... we also are using the 1553 code from the kaiser...

I did actually try to get the kaiser script running (by modifying some scripts) but still didn't managed to make the screen work...

Again, I'm still hoping we can really start developing (no, we didn't even start), but we need volunteers to start this all...
[Touch Cruise Android Development] imfloflo:
Someone create a MTYPE code for the Polaris but i don't remember 1667 don't sure.

I really want to help this topic, I'm student engineering in informatique but i don't know android.
[Touch Cruise Android Development] Mormy:
I misunderstood the screen error of other people :p

I tried to compile the kernel with my ubuntu 8.04, but I recived an error on the first make command :(
[Touch Cruise Android Development] dubbeld00:
go to the directory: ~/android-kernel (So not the KERNEL directory)

sudo -i
aptitude install gcc-3.4-base gcc libgcc1
git clone git://git.linuxtogo.org/home/groups/mobile-linux/kernel.git
cd kernel
git checkout -b htc-msm origin/htc-msm

But it should be compatible with gcc 4.2.3 (I thought).

(If you are shure you've got the whole git (so the folder ~/android-kernel/kernel is filled up correctly) skip everything from git clone [...] to [...] htc-msm)

what we are doing at the moment is creating a working linux kernel... Android just loads on top of it... so you don't have to know anything of android, if you can program "a bit" and you know (or get the help by one of the guys from the kaiser thread) "a bit" of linux it should be alright.

A little more information:

- you first boot the zImage (which is a linux image), this will include drivers for grapics, keypad, sound and so on

- on top of this you will have the initrd-android, which will give you the software...

So the only thing what we have to do is making a working linux image which includes all the hardware drivers :)

(dunnow how that git thing works, but if we really want to develop, we need an account to "commit" our changes to that git, also we need a new "branch" so that we can start using our own code in stead of the non-working kaiser stuff, maybe someone can figure this out)
[Touch Cruise Android Development] imfloflo:
Thanks for this description off initrd-android and zImage , ihadn't make the difference between this 2 files yet ^^

When I say i don't know android, iwould like to say i don't know which files i must edit before i recompil my zImage. i'm going to explore it tomorrow and read wiki and google description.
[Touch Cruise Android Development] dubbeld00:
See attached, these are the files the kaiser ROM currently uses... We can partly rip the GPIO part of the kaiser (it seems to have the same events)

GPIO = General Purpose Input/Output, so the LEDS (output), keyboard (input) and so on.

We also need to be included in the Makefile, Kconfig file and create our own htcpolaris_defconfig... But have fun reading ;)
[Touch Cruise Android Development] Scalap:
I thin k I'm gonna use VirtualBox in order to have a linux distro and try to see if I can be of any help solving this issue with the display and the GPIO (for the keyboard).

If I understood right, we also need an offical repositery for the polaris ?
[Touch Cruise Android Development] dubbeld00:
I think that's the best option, else we need to share our files here on the forum in stead of just refresh the git to get our latest changes :)

BTW! for the people having a hard time to compile the zImage:

Your android-kernel folder must be in the /root/ folder!

i just saw the following line in arch/arm/mach-msm/.kaiser-smd.o.cmd:

-nostdinc -isystem /root/android-kernel/arm-2008q1/bin/

The paths are absolute... so that's why compiling for some of us failed...
[Touch Cruise Android Development] alladdin:
I solved this errors:

apt-get install libstdc++6-dev

Alladdin
[Touch Cruise Android Development] dwaradzyn:
There is no reason why we should avoid using linuxtogo repository. In the end we want Polaris and Kaiser (and others too) changes to kernel to be included in kernel.org repository. The more distinct repostories created the more merging it takes to handle development. I fear there are too few developers to maintain one more repository at the time of writing.

This is not true. You should avoid doing things as root when it is not necessary. I can successfully compile kernel as regular linux user. Also the path for kernel compilation can be arbitrary.
[Touch Cruise Android Development] ovindahl:
I've downloaded zimage, Haret.exe, default.txt and initrd for android from page 1 and placed them in the root folder on my TC, but when I launch Haret ("found machine Generic MSM7500") and press run, I get the errormessage "Failed to load file \initrd-android". Why?

Also, I've gotten it up and running on my cruise with this (http://connect-utb.com/htcandroid/viewtopic.php?f=5&t=3) guide, but can not input text or get any kind of data transfer or calls/messaging.
[Touch Cruise Android Development] dubbeld00:
That's also my fear... That's why I didn't start with the repo, I don't have that much time at the moment... I hope there is someone who can start this development. (And can write C which is recommended ;) (isn't that hard btw, if you are not new to programming))

I didn't say you really have to compile with root... (I only mentioned the /root/ folder), but because some of us are Linux starters, I don't want to explain everything (starting with CHMOD and CHOWN). It also was a quick guide I made... and because I don't want to solve loads of problems because of wrong permissions, I did mentioned the sudo -i command. (don't want to explain this further)

The only thing I was trying to say is that the script is using absolute paths (which isn't true btw, the line I copied was generated by the kbuild/make script). So yeah, you can skip that comment :) (no you don't really have to put it in the /root/ directory of your Linux Distro, which I thought...)

Think this is using the vogue image (which is also working on our device, but indeed missing functionality)...

About your other problem, try this: posting, only do "First of all"... this should work.
[Touch Cruise Android Development] dwaradzyn:
In your version of my kernel compilation howto :P you explicitly mentioned to "always keep in root mode!!". Also none of "jfsutils xfsprogs quota isdnutils-base nfs-common oprofile" packages are needed to compile kernel. I use Kubuntu 8.04 and the only needed packages needed to follow my howto are "git" and "git-core".

I am trying to make hardkeys in Android working for Polaris. The main issue is that kernel compiled from linuxtogo repository does not boot on my Polaris. I've tried Vega R2 + airplane mode + running from phone memory but it still does not boot for me (hangs up after Go Go Go... in HaRET). I will post here if make any progress.
[Touch Cruise Android Development] ovindahl:
Now I can press run and get to the "HaRET: Booting Linux" screen, but then it just hangs. Been trying alot of times, but no luck.
[Touch Cruise Android Development] dubbeld00:
Well it's working on multiple devices... See tips; D. (at the bottom of the page) (just added).