yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] dubbeld00:
You need to do some changes to the source, but since nobody is working on it anymore (they still didn't solve the DMA problem, which should be solved easily (according to DZO)) I think we will never see it on our device...
[Touch Cruise Android Development] Maxxx33:
Has not to count on that ?
[Touch Cruise Android Development] dubbeld00:
There's news! Someone has given a Kaiser to dzo, who will fix the SDCard issues (I hope :)). Hopefully there are still people with a Polaris (if so, who is also able to do a little compiling and can program more or less) to help developing it to our devices :)

Please do reply, so we can make it really work! (After the SDCard is done, we can probably put all the things together!)
[Touch Cruise Android Development] dwaradzyn:
Stable SD will be major breaktrough with linux/android on polaris. I don't think this issue is easily solvable, but if dzo is working on it, I expect he will sucess in couple of days. He has proven his skills with vogue many times.
[Touch Cruise Android Development] dubbeld00:
That's why I just posted here...

Btw, his post on the Kaiser thread... It might not be easy to solve for an starter like us, but it looks like peanuts to him... They've lent him a Kaiser so he can develop on it :) the only thing we have to do is compile and test it, remove some keyboard related stuff (we don't have a kaiser keyboard) and compile the Vogue software keyboard for it.

But like i said... I hope there are still members over here, because it seems to be quieter every day...

http://www.youtube.com/watch?v=g854_ezQHXs&feature=related just a video to illustrate Android running on a HTC Vogue
[Touch Cruise Android Development] Michel82:
I'm still here mainly watching progress as i would love to have android on my polaris. If any help is needed i would be willing to help, i have some programming skills although a bit rusty. And hardware programming for portable devices would be new. But if any help is needed ... i am willing to help
[Touch Cruise Android Development] dubbeld00:
All I need to hear... I'm waiting for progress on the Kaiser port (SD Card), as soon as that is done (hopefully this week), I'm going to check what needs to be done for our devices... will inform you soon.
[Touch Cruise Android Development] thejigsaw:
I am here to

I am here to i am little bit client side programmer more javascript and that stuff but i have expirience in c# c++ linux and compiling some linux software so let's see what's done and what needs to be done, and lets make it... cos we all want android on or polaris, but the status stays the same for weeks
[Touch Cruise Android Development] jespernorman:
I'm also here. Not any good with programming, but I can offer moral support ;)!
[Touch Cruise Android Development] tcvaio:
Great to hear that :)
[Touch Cruise Android Development] dubbeld00:
Glad to hear so :) didn't hear from anyone anymore... thought you were all dead, glad to see the community is still alive... I'm following DZO's findings close and hope to get the SDCard fix soon (like I said, expect it to see it this week)... If that's done, G1 has to run on our device, and we can focus on the unique functions on our device...

What's already done:

- keymap of our "keyboard"

- on screen keyboard (provided by DZO)

- working touch screen

- working screen driver

- working "radio" for calling, browsing and SMS (and MMS)

What needs to be done:

- power savings (DZO will provide it to the Kaiser, we might have to do some porting)

- battery charge levels (probably DZO also will fix it for the Kaiser)

- working Wireless driver

+ - the one for the HTC G1 phone can be used

- working bluetooth driver

+ - the one for the HTC G1 phone can be used also

Might be "a lot" but is doable.. I'm not a king programmer myself (can do some though, and can compile) but I think we can fix this... As long as we keep on working together...

But I'll keep you up to date and wait for DZO to fix it all :)
[Touch Cruise Android Development] killerjohn:
WOW the actual status ("what's already done") is much better than I thought! You are great guys!
[Touch Cruise Android Development] thejigsaw:
I am also surprised what's left. It's not at all "a lot" i'll keep on reading deeper in this stuff today and i'll see what I can learn and help, but i think that if DZO makes it on Kaiser it will be a very little job or almost not at all job to port it to Polaris. dubbeld00 you scared me two days ago with your statement that will never see it on our device....
[Touch Cruise Android Development] dubbeld00:
Trying to wake people up... That's the only thing I want to do... And it was based on the truth, since nobody was making the SD-Card driver work... But finally there is progress...

But I'll wait till they are done and then really start the polaris development, hope we can work together, and make it work fast... I'm still missing the "we work together" in the kaiser thread.
[Touch Cruise Android Development] tcvaio:
Good to see the project is alive again too...

Will come in and cheer reguarly ;)
[Touch Cruise Android Development] donkarlos13:
If any help needed, count me in!
[Touch Cruise Android Development] imfloflo:
Still waiting SD support on kaiser/polaris from dcordes ?

I really hope things will accelerate soon with the debian portage to G1.
[Touch Cruise Android Development] belabartok:
It would be such a great thing to have android on polaris, thanks for the work, I hope to see soon it running here
[Touch Cruise Android Development] belabartok:
Maybe I`m amazed :eek::eek:
[Touch Cruise Android Development] kensou.8:
I'm not well talented in programming but if I can help in something...

Anyway I'm waiting for a functional release too.
[Touch Cruise Android Development] Maxxx33:
i'm wainting to android rom for polaris:p
[Touch Cruise Android Development] bally3:
seems like we need to put a team together to work on this.. As soon as we get a working port it might be an idea to co-ordinate this. It looks like there are a number of techies and linux programmers wanting to help but no co-ordinated effort.

If you would like me to take lead on this, let me know.
[Touch Cruise Android Development] dwaradzyn:
I would really appreciate your leadership bally! Once SD is stable we should support Android and some linux distro with opie/gpe. There should be separate threads at least for:

1. Kernel developement.

2. Non-kernel developement.

3. New versions, installing, configuring, using.

4. Issues and bug reporting.

Let me know what you think about this.

Another thing is that we need to integrate closely with kaiser dev team. They have a lot of knowledge and experience. I think if we manage to create and maintain those threads in right way - they will see that it is the proper way and will join us and share.
[Touch Cruise Android Development] bally3:
Thanks Dwaradzyne :)

Ok to start, I have a few questions to get me up to spec with the current developments.

1) The current versions of linux labelled android, are they indeed Android or are they custom linux creations from linux base kernel?

2) Are we working from the G1 rom?

3) Probably not as important, at the moment, but is haret the only way to run linux on our phones and would we be able to convert whatever we end up creating from what we currently have into a rom?

4) If we create a rom and burn it, would we be able to return to a windows rom?

5) The SD Card issue - What is it? Linux wont recognise an SD Card? its being currently run from an SD Card maybe thats the problem - maybe it needs to run from memory?
[Touch Cruise Android Development] bally3:
Agreed, but I'd leave me to worry about that.. Its a better idea to learn to walk before we can run so to speak.. if we dont get anywhere a load of threads would be a waste.. just like p3d thread, we should start the other threads once we have a product to build on. (ie a working polaris port).

I'll stick with this thread until we know what direction we're going in and then start the development thread from that point onwards, Again, if we ARE going to develop the kernel . If we are going the "port" direction then the kernel development may become moot.

I would like to set up a dev team initially and would appreciate if the users who showed willing earlier would pm me so we can gauge the expertise we're working with. I also have access to some linux devs who may assist us. Please, at this moment, linux programmers and developers only as testing on this particular project will likely be done by everyone if we stay with haret, being relatively simple and fairly risk free as far as I can see and as suggested by Dwaradzyne, we will set up a different thread for this.

Once the dev team is in place we'll approach the kaiser team and see where we can progress from there onwards.
[Touch Cruise Android Development] bally3:
About SD Card support:

http://vivien.chappelier.free.fr/typhoon/index.html

The Linux tree is derived from the OMAP tree at muru.com. The current version is 2.6.22-rc4 and has support for the framebuffer, USB (network or serial device), mini-SD, keypad, and leds. See the status page for more details.

I know this is for smartphones, but may be useful.
[Touch Cruise Android Development] bally3:
http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser/Android

I take it this is the kaiser development page. It seems they are working to make it compatible with Polaris also, so worth a read. (Just holding info here for the time being).
[Touch Cruise Android Development] imfloflo:
dcordes make few zimage for polaris but we alwys wait for the SD solution.
[Touch Cruise Android Development] bally3:
Is the vogue image worth looking at? I've got it and currently looking at it it seems more complete than the what we have - bigger file etc. but doesnt run on our devices. Someone mentioned DMA issue that was also mentioned on the kaiser page?
[Touch Cruise Android Development] bally3:
What I want to know is will the G1 rom be any good to us or do we continue with the zimage and haret route?

My understanding is, and correct me if I'm wrong, the current android ports flying around were pre-release android that were made to work on the various devices to prove that linux could work on the devices but need lots of work to get to a production stage.

I was under the impression that once we had a working g1 dump, since the dream is essentially a htc device, this would be more complete with drivers and such and would be ported to work with our devices with more specific hardware (soft keyboard etc) requiing work though modems and radios could possibly be used from g1 as it is essentially a htc device.

Anyone care to correct my assumptions and clear this up please?
[Touch Cruise Android Development] dwaradzyn:
1. Android uses Linux kernel but it is a unique distribution - very different from standard Linux distros like Debian, Gentoo or Red Hat. Google created special Java JVM named Dalvik for this distro and every user program is meant to be developed in Java using Android API. It is not Java ME, not Java SE, it is something new. One of the main goal is to create open mobile platform where everybody is able to create an application, and every application is equal. This mean that there is no distinction between standard phone software and third party software - you can change basic apps like desktop or dialer. Not to mention the security... Enough with that description - you can find more in Wiki and Android homepage. It is important to have in mind that almost only common part of Android and every other distro is Linux kernel.

2. We don't need to work with that ROM - we have sources for Android. We shouldn't focus on working with Android sources now. This has been done by Google and Android is mature enough for everyday use. All we have to do now is to make Linux kernel support Polaris hardware. After achieving that we should start customising Android and the only limit is the sky...

3. Until we do not have stable Linux kernel there is no use of making our devices boot directly into Android. I don't mind booting this way and I want to preserve many great software I have in Windows.

4. With HaRET there is no flashing and you can have as many Linux distros as you want. You just put your SD Card into Linux enabled PC and manage some partitions - no flashing, no hardreset to make system change (like kernel upgrade).

5. At this point you already know that this is all about Linux kernel developement. G1 is MSM7201A based machine. Polaris is MSM7200. The main porting from Google code to MSM7500 has been done by dzo in his work with HTC Vogue. A number of people (dcordes, premy, ginge to name a few) has been porting Vogue to Kaiser/Polaris. The SD is working in Linux for some time now. I have been able to mount my 8GB SDHC card and read and modify its contents. The problem is that there is DMA stability issue when stressing input/output on SD. Especially when the stress is made by parallel processes. This prevents booting Android as it always fails during boot process. I was able to boot OpenMoko but there was no way to pass screen calibration in GUI - at the time I tried it touchscreen driver was not compatible with X Windows. The SD issue is very hard to repair because the code talks directly to hardware and there are no technical documentation about MSM7200 freely available.
[Touch Cruise Android Development] imfloflo:
Must create a new bootloader to have dual boot ..
[Touch Cruise Android Development] dwaradzyn:
This is all about SD stability issue (kernel developement level). Kaiser/Polaris are stuck with old 0.8 version of Android because this is the latest one that can be booted from ramdisk image instead of SD partition. Size of ramdisk is limited to about 25MB (HaRET/WM limitation). If ramdisk is loaded to memory under Windows then Linux will work with it as its root partition without problem - contrasting to SD. There is no point in trying to produce Android 1.0 ramdisk - it would be very hard to cut it out to size of 25MB and preserve most of its functionality. Another thing is that once we have SD working - a major breakthrough - we will be able to boot other Linux distros, like Angstrom, OpenMoko, Debian and so on.
[Touch Cruise Android Development] dubbeld00:
Don't have to have a working port, it is already working... And yes we have to co-ordinate this... At the very start of this project, everyone was working on the same (that's why I didn't develop, don't want to waste time on things that are already in development).

DZO is still working (or waiting on the kaiser to arrive) to make the SD-Card work. As soon as that is done, we can use my post somewhere on page 85, checkout the git and compile it.

Then we've to check the error's and fix them... the last time I compiled it, i had a working android 0.8... with a working SD card it should even boot 9 out of 10 times (because now there were troubles with the memory allocation on the RAM drive (and in version 1.0 there were troubles with the 25 megs limitation of the RAM drive)).

This is all as far as I know, didn't really take a look at it, so it's based on findings of other posters, so please correct me if I'm wrong... I'm still awaiting DZO's findings before I really start focusing. So as soon as the SD card is working, I hope we can split the tasks and make a real working Android.
[Touch Cruise Android Development] Michel82:
So .....

If i'm understanding these last few posts right development can be divided in three steps:

1) Kernel development. Which should actually be the only polaris specific and hardest part (Includes DMA and SD issues).

2) GUI development. Should be just compiling android srcs

3) GUI adjustments. Not really necessary for the creation of a first workable Polaris Android ROM.

So what's needed the most for a succesful dev project team are some hardcore linux kernel programmers. I do have some programming skills but kernel and i/o is not really my thing.

So where are those hardcore hardware kernel devvers?
[Touch Cruise Android Development] belabartok:
I think we should start organizing this starting with who is going to develope and then distributing the work
[Touch Cruise Android Development] imfloflo:
dcordes work on kaizer and polaris kernel too but we always wait SD fix to create a new kernel fully working with 0.9 and 1.0 SDK

there is also htc-liux channel on freenode
[Touch Cruise Android Development] bally3:
thanks for the info guys, I now have a much better understanding of whats required here.

As the users above said, we need to get a dev team up working on this. I mentioned before about linux developers contacting me, up to now no-ones come forward.

With it being kernel development, which I know little about without a good developers base the project is going to be a none-runner I'm afraid.
[Touch Cruise Android Development] dubbeld00:
I know my bit... can compile, make adjustments to the code... But like I said, that's the only requirement... make fixes, change keymappings etc... The rest should work out of the box :).
[Touch Cruise Android Development] kensou.8:
Just the same for me. :rolleyes:
[Touch Cruise Android Development] imfloflo:
New update from dzo has been release now the camera work but always no polaris 1.0 version :( only vogue
[Touch Cruise Android Development] Maxxx33:
nothing new?
[Touch Cruise Android Development] Michel82:
This guy: http://cs-alb-pc3.massey.ac.nz/vogue/ seems to know what he's doing with his vogue, he even got the camera working last week. He has a GIT repo (http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=log;h=refs/heads/htc-vogue), which could be usefull to this project.
[Touch Cruise Android Development] imfloflo:
This guy is DZO from the forum and he is waiting to receive a Kaiser or Polaris to adapt his work to our Polaris.
[Touch Cruise Android Development] rparslow:
I managed to boot Android on my HTC Touch Cruise running from WM6.1.

1. Downloaded the zip in this folder http://linuxtogo.org/~lgorris/index.php?path=polaris-bootkit/

2. Modified the default.txt for my phone provider

3. Copied to MicroSD card in a folder called ANDROID.

4. Started HaRet and press "Run"

5. Android boots

Observations :

Phone works.

Modified the built in Zzz contact to my house number and that works too.

Goggle Maps not working maybe to do with my gprs settings.

Tips for others interested in trying use :

The camera button brings up the keyboard.

The IE button gives sort of right click

Dpad can navigate screen.

Photo/Video can be seen here : http://www.ukit.be/android/BootUpAndroid_.wmv (sorry for the shaky hand :o )

remove from site : Tried with this boot image http://linuxtogo.org/~lgorris/builds/zImage-polaris-2.6.25-test-8 and phone still boots but seems slower to me and keys work badly and it even rebooted alone and I have no "G" icon however clock is now running no longer stuck at 12:00am

new zimage http://linuxtogo.org/~lgorris/builds/kernel/polaris/zImage-htcpolaris.bin
[Touch Cruise Android Development] erfaldo:
I confirm, it boot for me too (parameters SFR France) but didn't achieve to connect GPRS :-(.

SMS works, phone calls works too.

Power button do not switch off screen.

Anybody has tried to test 3rd party applications with this version
[Touch Cruise Android Development] tiepeks:
I tried it just now, phone boots fine and my gprs-settings worked. I could surf right away.

(T-Mobile in the Netherlands)

But my Linux-knowledge is

zero
[Touch Cruise Android Development] psicobra@hotmail.com:
hi how do i get android working on my polaris i have made the zimage now what do i do?
[Touch Cruise Android Development] dubbeld00:
Get lost? I guess!

It's explained 300 times before... You only had to go 1 page back... But I know, finding things is not easy...

Please read his previous posts, and find out why I react like this...
[Touch Cruise Android Development] psicobra@hotmail.com:
right so instead of posting a link with the answer to my question you act like an idiot and post a link to all of my previous post's people like you are the reason no body ask's questions do you feel like a big man now do you feel better i hope so that way at least some good has come from your post so it is not a complete waste of time and xda-developers server space.
[Touch Cruise Android Development] kyphur:
And Now a word from a Moderator....

First, stop bickering like small children or we (the Moderators) will start handing out "time-outs".

First, If someone is behaving in a negative or disruptive manner don't engage them in a battle of wits, they'll just bring you down to their level and then they have the advantage!

Second, don't get upset when someone thells you where the answer to your question is, be gracious and go to the first page. Nobody owes you anything here, RTFF!

Third, if I have to return to this thread I'll just start swinging my "Big Hammer of Ban" until the BS Stops.
[Touch Cruise Android Development] dubbeld00:
The only thing I was trying to say is that users who have a question, should at least search first, 2 posts before your post (only 1 page back), someone explained what to do with the z-image...

Since I read almost every thread over here, I know you ask a lot of questions (no offense) but please do me a favor, and read the first and the last 3 pages of a thread before you ask something...

Normally I'm not to lazy to give you a link back, but because of your history of asking before searching, I won't... especially because the answer is on almost every page.

And most of all, I'm not doing this to piss you off, but to let you search first... And to the moderator and you, there are nicer ways to say this... Excuse me for my inappropriate behavior. PSI, please take this as it is, I don't want to discuss any further on this subject.
[Touch Cruise Android Development] thejigsaw:
I tested the last image that is mentioned in the previous page :) and it worked great for about an hour then it crashed and same like the old image i couldn't start it again it freezes on but.. but it's a good progress that even started for once :D so for future how complex is to put the last SDK 1.0 instead of this old one? Does anyone have an idea how to make this or want to help me to implement 1.0?
[Touch Cruise Android Development] dubbeld00:
We've started a new thread of this... because this thread is... to long to read :)
[Touch Cruise Android Development] niegara34:
Hi body

links broken down
[Touch Cruise Android Development] imfloflo:
Why there is always a guy who post in old thread to put it on the first page when there is a ne w thread ???

http://xdaforums.com/showthread.php?t=452108&page=18
[Touch Cruise Android Development] freelucos:
Hi all,

Someone could post a functional pack for Cruise, because for now I'm in France SFR and I still can not call. Moreover, it becomes very difficult to install the files to run ANDROID.

Thank you in advance
[Touch Cruise Android Development] imfloflo:
freelucos stop SPAMMING in all thread just read your PM !

http://wiki.smartphonefrance.info/Android%20sur%20HTC%20Cruise.ashx
[Touch Cruise Android Development] henry2004:
need to have a good look. I have tried many times to run haret on my touch cruise but failed all.
[Touch Cruise Android Development] excogitation:
Does anybody feel like updating the wiki or telling me in short on what's our current status?

I'm still running a version from a few months back and was wondering if there has been progress and what's left to do besides replacing winmo with Android?
[Touch Cruise Android Development] bbezja1:
this thread was not supposed to be brought to life.

read this and this thread
[Touch Cruise Android Development] twotee:
Hi everyone,

I am very, very new to this forum and also not very techy, so please forgive me if I ask 'stupid' questions.

I first of all want to wish everyone a happy and fulfilling new year.

I have had this phone (HTC Orbit 2) for over 2 years now and just about going for a new/android phone when I thought, why not look up the internet, then I bumped into this.

Can someone please take me step by step on how to install android operating system on my Orbit 2?

I sincerely apologies to taking you back.

regards,

2tee.