yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] dubbeld00:
1. Before opening haret, open Opera and browse to google, wait before this page is loaded and don't close Opera

2. open haret, boot android

3. open togga in android (it's below in the list of programs)

4. click connect

Never saw anyone of you reported an error of togga (which will give you an error if it is not able to connect)

this is only explained 10 times before...
[Touch Cruise Android Development] roms5:
how can i switch to street view in google maps?

becouse i dont have a menu in google maps at all...
[Touch Cruise Android Development] brumbrum:
Same error when I do exactly this!

Could be a radio-related problem as mentioned above.

What radio-version do you use and what do you recomend?

When I open togga I get the following message: "The application Togga (process net.retrobits.togga) has stopped unexpectedly. Please try again".

Hope somebody can help me...

Thanks for a great work this far, and I am really impressed that it works as good as it does for some people! :-)
[Touch Cruise Android Development] roms5:
work for me with

rom: m-amine german 2 final

radio 1.59.44.02
[Touch Cruise Android Development] dubbeld00:
Please people, stay on-topic... (else we have to browse 100 pages again before having an answer, or getting the same question over and over again due to this) the last 5 or 6 posts are all not related to the development. You can try what is mentioned before, this is the only way to make a working GPRS/3G connection. If it isn't explained, you can always ask...

If it isn't working, it isn't, there is nothing you can do at the moment... (except wait for a new version) The code isn't even finished for calling/gprs/sms etc...

So please, keep it development related... (not bugs, but suggestions to make things work... like fixing EGPIO).
[Touch Cruise Android Development] bally3:
If someone who wishes to contribute would like to start a "Polaris Android Project - Testing and Bug Reporting" thread and is (and this is important) willing to maintain it, we can start diverting these type of posts to that thread which has proved successful in the past.
[Touch Cruise Android Development] Michel82:
Great progress guys!! Making radio (sorta) work is a big step forward in an actually usable android. I have one finding i haven't seen before though: after a while of iddleness and putting the screen back on it gets divided in two sections where the top part of the screen is shown at the bottom and vice versa.
[Touch Cruise Android Development] Quilapvd:
Tested, it's so far working great.

Got operator to call (only no sound) and gprs is working to.

My Radio Radio 1.59.44.02 and a custom rom :).

Tested some stuff, if you open the Camera program, Android crashes.

But it's a big step forward, can't wait if this is fully working on the Polaris.

P.S. I noticed that Android is much smoother at use that normal Windows Mobile :).
[Touch Cruise Android Development] CyberCSK:
Hi,

for me the zImage with default.txt from post #341 is not working. I use the files form the wiki

Android_1.0_Rogro_f00bar_090110.zip

Radio 1.59.44.02

The screen is white and flickering. Please, can somebody help?

My ROM is a Touch-IT m2d beta3.5 with 3d drivers wwe

Device: XDA Orbit 2 (Polaris 200)
[Touch Cruise Android Development] marcelkordek:
hi, use "board-htcvogue.panel_type=3" in default.txt
[Touch Cruise Android Development] marcelkordek:
have start a new tread Polaris Android Project - Testing and Bug Reporting

this tread is only for testig and bug reporting
[Touch Cruise Android Development] Quilapvd:
default.txt (got only one error about msm.. but hey it's booting)

Edit set cmdline "ppp.username=vodafone ppp.password=vodafone" to your own settings.

Greetings.
[Touch Cruise Android Development] excogitation:
Took me a while to also get it working...

Nice job.

all-in-one-package (dzo's stuff from 19.01. (identical to f00bars?) + rogro82's latest kernel from 18.01.)

For O2 Germany ppp.username=Internet ppp.password=Internet works (http://android.v-dh.nl/internet.php says it should be empty - but ppp.username= ppp.password=) doesn't work.

Also - may I strongly suggest - to at least check the first post for updates and read the wiki before asking the same questions over and over again.

Feel free to join in anytime - updating/improving the wiki I mean :-)
[Touch Cruise Android Development] Michel82:
Maybe this has already been addressed before, but i left android running overnight with a 100% full battery and it was completely drained out this morning. So there's most definetely some work to be done in the power management department.
[Touch Cruise Android Development] dubbeld00:
On the Kaiser thread they are having a donate action in order to get DZO a kaiser... We can do the same, or donate them money... but don't know if the kaiser is exactly the same... If it is true... we can maybe put our hands together and donate them... don't think we can collect a whole polaris with the 10 active users over here.

But I hope bally3 can make things clear (he wrote DZO about his "progress" or non-progress)... Hope to hear from him soon.
[Touch Cruise Android Development] bally3:
ok.. I've emailed dzo asking for some assistance and updates.

Looking around on his site, I saw this on the top lines...:

"Luckily the hardware is very similar to that used by the Google android project. There are some differences, the VIC is completely different and the phone software (AMSS) is a different version. It seemed to hang when I turned off the MMU so I rewrote the bootloader (haret) to set up some identity pages and boot with MMU on. "

Anyone able to "de-geekify" this for me? whats VIC code?
[Touch Cruise Android Development] thejigsaw:
i'am willing to donate some moneyy i always donate to the os comunity but my country doesnt support paypal any other payment method will be great. also i can't afford whole polaris but with a drop from everyone i think we'll make it. compliment for the new post i just wanted to say to make separate posr.

queston: since the last image (from the old post) is working can't we just find a way how to put android 1.0 in it instead of the old version?
[Touch Cruise Android Development] adderz91:
I sent DZO a PM telling him i was willing to send him my Polaris, but i havent heard back...

Donations for postage costs would be welcome, but i wanted to get a response from DZO first.

It is my main phone, so i would need him to send it back.
[Touch Cruise Android Development] NeoS:
Hey guys. Nice project here. But wasn't there already a topic for porting Android to Polaris?

Anyway, I've got a Polaris just laying there, and it won't matter if i have to hard reset it every day, since i don't use it for everyday use anymore.

So, if you have anything for me to get this running, just yell. I'll brick my device for the hell of it. :-P
[Touch Cruise Android Development] bally3:
My PM to DZO and his prompt response (Thanks DZO :) )

----------------------
[Touch Cruise Android Development] rogro82:
Where can i find the latest sources on this? Maybe im able to help a bit... not much time but i could take a look..
[Touch Cruise Android Development] dubbeld00:
http://xdaforums.com/showpost.php?p=2698830&postcount=409

Here is a guide to checkout a git... This will checkout the official google git...

please DON'T APPLY THE PATCHFILE!... You have to checkout branch android-msm-2.6.25 commit 07fe2e3914202167a4d314bf5e81bbd2f5d3062b

You have to find out how to do that... Then apply the patchfile of http://it029000.massey.ac.nz/vogue/ DZO, now you have DZO's files in order to get his drivers...

Now you have to checkout the linuxtogo git, which the kaiser people are working on and will work on our device!... Do this in a seperate folder! so you have DZO files and "our" files.

http://xdaforums.com/showpost.php?p=2271238&postcount=73

It also explaines how you can make a zImage.

Now you have to do like DZO spoke... check the stuff... and fix it where needed... If you've fixed something you can share it with us using the "share your work" content in the first link (post 409).

Hope we can all work together... so please keep people up to date about what you are doing...

To debug use: http://linuxtogo.org/~lgorris/index.php?path=kaiser-bootkit/ the angstrom thingy... edit your .txt and refere it to the .gz file.

(btw I was to lazy to do some spell checking so I hope you will understand it)

Good luck! (seems a lot, but it should be easy...)
[Touch Cruise Android Development] bally3:
Thanks Dubbeld00 for the info and a big thank you and welcome back to Neos2007 and Rogro82 - thanks guys :)

in order to pull this project together we need to be working together. To do that we need to ensure we all have the same setup with regards to the linux build.

Dubbeld00, The instructions are clear enough in the link in how to build the zimage - thank you, I'll repost it below to avod having to flit from one to another.

So what do we need?

1) PC running with linux - I'll probably go with ubuntu to keep with the instructions and I recommend anyone with limited linux skills like myself to do the same.

2) Polaris device running winmobile 6.1? (does it matter?) it should work with all versions but we'll have to test this.

3) Setup your device using Dubbeld00's instructions below:

Now you're ready to begin creating the zimage for the Polaris.
[Touch Cruise Android Development] bally3:
4) Update your ubuntu system with Dubbeld00's instructions:

Get your Ubuntu up to date, go to your command line:

Enter your password, now you are logged on as root; enter:

Your system is now up to date.

You have to install a couple of packages so you can cook your own zImage so enter:
[Touch Cruise Android Development] bally3:
CREATING THE ZIMAGE:

Checkout the git

First make a directory to put everything in:

Now go to that directory

Get the google android git:

Switch directory:

Checkout the andoid-msm-2.6.25

Get linux toolchain:

Change dir:

Download toolchain (around 100mb)

Unpack it:

Apply patch file:

Get patch file:

Change dir:

Patch it:

Make a zImage

Change dir:

Prepare it (using config file)

Cook it:
[Touch Cruise Android Development] bally3:
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

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

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

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:

2. Remove all extra added files:

3. Reset the git:
[Touch Cruise Android Development] bally3:
OK so quite a lot to do then to get to a working setup state, but thats where we have to start.

Those of you who have pledged support to try out these versions, we'll have to post up the zimages we create.

A question then (and probably a noob one), can we use anyones zimage creation to work with or does everyone have to compile their own?

It seems to me thats where we have the situation of everyone working on the same problen by themselves, it would help if we could get a working zimage that boots at least and then work from there on?
[Touch Cruise Android Development] dubbeld00:
No, If I compile a zImage, you can also use it... Only a zImage doesn't contain any source files (it is compiled ;)). The zImage will boot the linux kernel and some drivers in order to get Android (or any other image) working.

Big tnx for the "repost" and edits here :)!

Think it is best to create 3 folders with all different outputs...

- the latest google git + polaris patch (see the guide bally just posted).

- the latest linuxtogo git, see this post

- the google git + patchfile of DZO, so branch android-msm-2.6.25 commit 07fe2e3914202167a4d314bf5e81bbd2f5d3062b

You will have to have THAT commit (so that hash string is required in the linux command!!!!), you have to change the command, I don't know how... if someone can check that...

Now we have 3 folders with source files... think it is best to take the linuxtogo as base, and apply patches from DZO to this... isn't that hard :)

Also use the angstrom not the android rom... This is a linux environment only :)

Seems a lot to do, but it is all done in 20 commands, and take you 10 minutes of time... Good luck with it... (hope someone has a lot of spare time... I'm in the middle of a big programming project, so I don't have that much time).
[Touch Cruise Android Development] thejigsaw:
Hi, in the previous posts I read that we need a kernel for the android to work on polaris according to this google document ( http://source.android.com/projects ) which represents what's in open source package of google android they say that they give the kernel too and a bootloader reference which i think also was some problem why we couldn't install android as a default operating system and not using haret anymore.
[Touch Cruise Android Development] dubbeld00:
True... only the drivers don't match :) That's why we try to do that... And if we have all the drivers, then you can make android your default operating system... but I think we should focus on creating the drivers (and fixing) first.
[Touch Cruise Android Development] bally3:
Anyone care to try the instructions above and post up a zimage to try out?

come on... you know you want to! :p
[Touch Cruise Android Development] earthman123:
I am in.

Hello, I am a newbie at this forum. Just today decided to buy polaris(HTC Touch Cruise) for day to day use. While watching youtube videos about it, discovered about Android. On my opinion it's great. I'am working as a Java Developer. And the possibility to write Java apps, strong Linux basement, eclipse environment, etc fascinating me. I've read the forum thread and would be very happy to help with creating fully-featured ROM image for polaris. I have experience writing kernel module for freebsd, strong C knowledge. I'll buy polaris in a week or two, after selling Palm TT3 and Asus P696.
[Touch Cruise Android Development] imfloflo:
So very happy to see this post grow up and every body working on the project again :)

Message from DZO is good to hear.

I'll follow this.
[Touch Cruise Android Development] dubbeld00:
We know :)

Btw rogro, seems DZO fixed SMS (or it was already working on Kaiser, but not on our phone), fixed screen rotation, backlight powerdown (your zImage only made the screen black, but thought it didn't powerdown the backlight) and fixed sound!

Btw2, can you share a patch file :) so I can play around a bit.
[Touch Cruise Android Development] Michel82:
Where is this new zImage to be found? Would like to try it.

Btw is asked a question in the other topic:

Does anybody here know if it is possible to get the Gmail app installed and the calendar and contacts sync working?
[Touch Cruise Android Development] radem205:
This type of questions belongs to the testing and bug reporting thread! The new zimage isn't compatible with the polaris yet. Rogro (or something else) will convert the new zimage to a working polaris zimage I think.

But again, this type of questions belongs to the other thread!!
[Touch Cruise Android Development] rogro82:
Ive seen he made another commit after i started working on it... ill check the changes he made ( ive seen the backlight one ). I think with screen rotation he means when the keyboard slides out, screen rotation already works (eg in the browser ).

Did he fix the sound overall or just some sound issues with calling?

If he fixed the SMS that means he changed the ril because the cdma sms format is different. If this is the case there should be a new system.img/initrd.gz.

At the moment im trying to fix all the input issues and trying to create a keypad file instead of doing all keypad work in polaris-ts or in the board. That would make it a bit easier to create special functions on for example double press / long press etc.

For now I moved to keypad->get_gpio solution so we can use the exact values that haret returns like IN1_13 (camera) as (1,13,function,bit) etc.

Trying to find out if a column gpio is triggered before the shared buttons are triggered ( like hangup/call button). From what ive seen in the kaiser keypad code this is how its fixed.

So that means first check the column gpio and then check the row gpio, but had no success yesterday... If someone can try to see if there is a gpio triggered before the actual call/hangup gpio is triggered that would really help a lot.
[Touch Cruise Android Development] radem205:
Nice to see you are working on it!! So far I can see he fixed the audio overall (listening to music for example works). DZO has made a new system.img here: http://xdaforums.com/showpost.php?p=3194496&postcount=2146

Maybe this could help a bit to know how gpio and irq works: http://www.unixresources.net/linux/clf/embedded/archive/00/00/30/66/306640.html
[Touch Cruise Android Development] rogro82:
K i just seen the new commits... It will take me sometime to migrate to the new commit but hopefully tonight we will have sound :)
[Touch Cruise Android Development] radem205:
That sounds good :)
[Touch Cruise Android Development] craigad:
I have experimented with the new system.img and can report the following:

SMS does indeed work.

SIM Card is recognised. Phone number, IMEI, IMSI are now displayed under Settings, About Phone, Status.

However GPRS is no longer available.

Messaging works inbound and outbound.

Signal Strength now works

hope this is useful feedback

/craigad
[Touch Cruise Android Development] rogro82:
And I can confirm PCM audio is somewhat working :D

Just made a quick build against the new commit and im trying it as we speak.. Im at work so its just a quick tryout.
[Touch Cruise Android Development] radem205:
Nice! SMS is working very good and the networkname is displayed right! But GPRS didn't work anymore with the new system.img (like someone said already) :(.

When I setup the right values from here (http://android.v-dh.nl/internet.php) the grps icon appears in top of the screen but I can't get the connection work.

Do you have this experience too Rogro?
[Touch Cruise Android Development] KundK:
Close to perfect! :)

But I can't hear a bit of sound. I mean when playing mp3.

Not even notification when sms is coming in.
[Touch Cruise Android Development] radem205:
This has to do with the fact Rogro didn't released a zimage yet with the latest commits of dzo (including the audio fix) .
[Touch Cruise Android Development] excogitation:
You need compile a new kernel with dzo's changes or wait for someone to release a new one with the changes incorporated.
[Touch Cruise Android Development] rogro82:
Give me 30 more minutes to get things right and then ill upload a new zImage.

Its becoming a real problem that we are dependant of both vogue and kaiser code, especially since everyone is incorporating machine type dependant code.

Ive created 2 dummy functions (machine_is_htckaiser_dummy / machine_is_htcvogue_dummy :)) so i can switch to a newer release more easy and can concentrate on development instead of loosing a lot of time merging to a new commit..
[Touch Cruise Android Development] imfloflo:
Very good idea to create this.

why don't use MTTY device for all the code like this we can have only one release kaiser/polaris/vogue and the code detect the device

ps: rogro82 can you answer my question here please :)
[Touch Cruise Android Development] marcelkordek:
thanks rogro, great work.
[Touch Cruise Android Development] rogro82:
Hmmmm some weird issue...

If i use dzo's code to play audio I cant get any audio during calls.

If i change some code in msm_audio_path i get sound during calls but no normal audio.

Entering debug mode again :)
[Touch Cruise Android Development] radem205:
I have seen this issue before in the kaiser thread after dzo had released his latest zimage and system.img .
[Touch Cruise Android Development] rogro82:
Was it fixed or not? Its because it the current code in the latest commit always return 0 on the msm_audio_path..

Ill try to just set it the same for in call audio as for normal audio...
[Touch Cruise Android Development] radem205:
It has not been fixed. I saw that dzo has already made a new commit but I don't know if this commit is a solution for some problems (http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-vogue).

Edit: Dzo has fixed the audio issue in his new kernel: http://xdaforums.com/showpost.php?p=3197959&postcount=2177
[Touch Cruise Android Development] excogitation:
I didn't realize before...

I didn't know I had to set my APN in Android before - but if I do - SMS and Internet work with dzo's latest system image.

It's in Menu -> Settings -> Wireless controls -> (scroll down) Mobile network settings -> Access Point Names

delete the ones that are there by opening -> Menu -> Delete APN

and put the right one for your network there.

Still you have to make an aktive internet connection in Windows before (you know you did it right when the data icon shows next to signal strength - not sure about this).
[Touch Cruise Android Development] radem205:
Which system image do you mean? The one in Android-21-01-2009.zip? This system.img the sms doesn't work anymore.
[Touch Cruise Android Development] rogro82:
Still the same sound issue :mad:

I can either set it up as dzo did and return 0... this will make all sounds loud out of the speaker but you cant hear anyone in calls.

Or set the sound profile like the vogue, but this will make the sound very low but you can hear the other one talking.

Going to take some more time to figure out what is going on but for now ill upload a new zImage so you can test it.

As far as other problems solved:

After getting out of suspend the screen should be ok now...
[Touch Cruise Android Development] radem205:
Thank you! But Dzo has fixed the audio issue, you know that?
[Touch Cruise Android Development] rogro82:
This is against his latest commit... the sound issue is another issue that would cause the phone to hang after a call.
[Touch Cruise Android Development] excogitation:
The one from here.

21-01 ... someone's been to the future or maybe just in a different timezone
[Touch Cruise Android Development] radem205:
hmm, weird. With your latest zimage I noticed the following:

- Audio (when playing music) is very low (what you said already)

- You can't hear anything during call (no speaker, no microphone)

- I can't hang up a call when I press "menu" -> "End call"

- When you turn the screen on again the screen well placed (good job!!)

- GPRS doesn't work anymore (already known)

It's a different timezone (new zealand) :)
[Touch Cruise Android Development] imfloflo:
Very long to boot , and mdq error still here :s

when i select "camera" phone freeze

succes to make a call and i see "G" top icon too
[Touch Cruise Android Development] rogro82:
Heres the one with the better sound but i cant get any sound in calls...
[Touch Cruise Android Development] radem205:
I can confirm this and with this zimage I can hang up a call.
[Touch Cruise Android Development] Quilapvd:
Oké the latest zImage and system.img from DZO gives me a good working speaker (the speaker @ the back of the phone.. mp3 plays..) But now I've got no network so I can't test calls (front speaker)..

But so far we're getting somewhere, can't wait till Android is fully working :).

Good job guys.
[Touch Cruise Android Development] imfloflo:
I try the lastest 21-01 + your lastest zimage.

i can make/receive call sound is good but other personne listen my voice + his voice (double sound) with front speaker but the mp3 sound isn't very good back speaker.

I can call only number with +33 number type

I wasn't able to send sms try 06.... or +336.... number type
[Touch Cruise Android Development] Scalap:
same problem as you imfloflo.

can't send any sms...

but i am writing you this from my polaris and that's great enough !!