yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] Michel82:
Fixing the keymappings would be really great!!! It's freaking annoying it doesn't work now, i keep hitting that middle button as 'enter'. I remember that in one of the first cupcake builds the keymappings were still right. I could attach one of the files if you want, i archived all versions and files. In the wiki (http://wiki.xda-developers.com/index.php?pagename=Polaris_Linux) there's a reference on how the buttons used to be mapped.
[Touch Cruise Android Development] Mormy:
You are right, Android closes apps when I press the red button.

What I found it isn't the task manager but recently opened apps :)

Thanks
[Touch Cruise Android Development] life02:
That would be very helpful! I've tried quite a few builds that I've seen online and haven't found one that was right yet.
[Touch Cruise Android Development] life02:
Ok I got the right key working now! Unzip the attached zImage and test with it. It is freshly compiled with just the right key changed. Anyone know when the center (OK) button worked? I'll see if I can't get that fixed as well.

The new zImage also has the solid blue led that I have yet to mess with. I will look at it after work... the keymapping was about all I had time for during lunch.
[Touch Cruise Android Development] bally3:
Works a treat life02! its good to be able go back to using the nav keys for left and right normally. good job :)
[Touch Cruise Android Development] briggs81:
Nice work.

not sure if you have checked the updates on google code, but hikeit did reply to the post about the button changing app saying that something is in the works. not sure if you want to tell him about your changes, maybe he will be that modified zimage up for download for polaris users
[Touch Cruise Android Development] bally3:
Got adb working on Windows 7 - check this post

If you're struggling, try the info I posted here

Some more info on adb and android sdk here

Basically, if windows recognises our device and you have the android sdk in your pc's root, you should be able to type adb shell after navigating to the tools folder of the sdk and it should drop you into your phones shell.

If you get that far then you have working adb! :)
[Touch Cruise Android Development] life02:
Good idea, I added a comment to the issue on the google code page. Once I get the OK button fixed, I will submit the keymap source to the kernal repository and it will included in all future zImage compiles.
[Touch Cruise Android Development] bally3:
Ok..I've had some conversations with vilord on the Vogue forum and he's agreed to help us with what he can and forward on the Polaris to someone else if they can help with things he cant.

Vilord is in the US, where our phones are $400+ to buy even on ebay.

I've found a used Polaris at a reasonable price of around $220 including shipping which says very good condition in the UK from a seller who has over 1200+ feedback at 100% - so I'd say he should be trustworthy enough:

http://cgi.ebay.com/HTC-TOUCH-CRUISE-XDA-ORBIT-2-vg-cond-EU-chrgr_W0QQitemZ270422524202QQcmdZViewItemQQptZUK_MobilePhones_MobilePhones?hash=item3ef670412a&_trksid=p3286.m63.l1177&_trkparms=|293%3A1|294%3A50

Take a look at the advert and let me know what you think, we've got currently enough offered to purchase this if everyone, including vilord is happy with the proposal.

I will ask everyone to donate to vilord directly as I will be asking him to make the purchase, as phones bought at one address and sent to another country are usually seen as dubious credit card frauds and it may look suspicious and cause issues.

I think vilord is a good person, I havent known him long but I believe him to be a man of principles and good to his word. I suspected right, he has been the one whose been making the changes to fix some of the issues for our devices and he is also helping on the Kaiser thread, like dzo, I think he's a shining example of what xda devs is all about - helping cross-platform to make our devices better.

But I'll let everyone else who will be donating to have their say on the matter and I'm open to suggestions. I've posted this here as I wanted to leave the Bounty thread clean for the actual donations. Once and if, we've agreed that we're going ahead with this, I'll ask everyone to donate to vilord and post what they have donated on the Bounty thread. If we do not raise the full amount, vilord will refund back the donations to everyone (minus any cost he may incur from Paypal of course).
[Touch Cruise Android Development] Michel82:
I've tested with sleep_mode set to 1 for the last two days, as bally3 suggested. Works a treat! Power performance is noticably better, the phone lasted for about 1.5 day with normal usage, which is similar to winmo. I did found one issue though; It doesn't seem to wake with just using the power button. I have to press another button and then the power button to wake it up. Do you have this too bally3?
[Touch Cruise Android Development] Mormy:
@ Bally3

I'm in. Let me know how to donate to Vilord and I'll do it. I hope nobody will offer more ;)

@Michael82

Me too have the same problem, but I think it's a knowed issue.
[Touch Cruise Android Development] bally3:
Yup same issue, its a bit of a press-all-and-hope-for-the-best, but in its defense it has only died once or twice when sleeping for me of recent.

Glad the tips are working out for you all, I've got adb working on my Win 7-based media centre and following vilord's suggestions ran adb-logcat in a command prompt and have been watching whats been happening on screen.

I have fbook, which I think I got from one of the dowloads, which I no longer use as facebook mobile is better, and noticed that it was invoking a lot of activity so I've uninstalled it. May help to speed it up.

I also noticed that in the latest build, neocore reports that we have no 3d hardware again! :rolleyes:

i'm going back to the last initrd.gz and system.img to see whether I can bring it back.
[Touch Cruise Android Development] bally3:
If you have adb working and want to run adb-logcat, you need to download and install the full androd sdk, installing is simply putting it in root and changing the variables as in the readme file. pretty simple stuff.

Once you've done that, boot android and plug in your device and wait for it to be recognised.

start a command prompt and navigate to the tools folder in the sdk (may ot be required to do but I seem too need to to do it).

type in adb logcat

If you've got vista or win 7, right click on the command prompt icon in accessories and choose "Run as administrator" or you'll have issues.

hopefully if more of us can get this far, maybe we can start helping out rather than waiting to be helped. :)

UPDATE: I've found I can only connect to adb if I plug into the PC BEFORE running haret.. interesting.
[Touch Cruise Android Development] briggs81:
don't press your power button, you just need to press the unlock button a few times! Sometimes it locks up, but i will take the longer battery life!
[Touch Cruise Android Development] life02:
Well it was fun while it lasted. I'm glad you found someone who really knows what they are doing. Hopefully we'll see regular updates now for the polaris incorporated into the vogue branch. I'll go ahead and bow out now so we won't step of each others toes with code changes.
[Touch Cruise Android Development] bally3:
Definitely the wrong thing to do Life02, actually we need you now more than ever. Polaris doesnt have dedicated devs, you're the only one recently whose shown any dev skills and remember that vilord's first priority is the vogue as he is a vogue owner.

What would really help this community would be if you could work with vilord and actually get us involved in the changes (I'm itching to learn some of this stuff myself). I understand the concern of steppinng on each others toes, this was raised by rogro when dzo started to help us - but as dzo said himself at the time that since we are usig git repo's theres nothing stopping anyone making changes as long as they push their changes to the repos.

I really hope you will not stop, as great as it will be to have vilord on board, it will be just as great if not better to have a Polaris owner who knows what he's talking about involved in the development. Also bear in mind that if you take some of the stuff thats working on the Vogue already (gps, camera etc)and liaise with vilord so you're not trying to fix the same things at the same time, it will give him more time to get the other stuff fixed he's working on like Bluetooth.

If you have any other concerns, please pm me before bowing out.

Thanks.
[Touch Cruise Android Development] bally3:
I've been using Android pretty much all day today to see how the current build fairs. Battery life was ok, I'd say I'd get a days use out of it in normal use.

Still too many freezes for my liking, device froze at least four times today, whether I was in Market or sending an sms.

It also gets very hot whilst charging using the charger in Android mode, much warmer than in WinMo.

3G is a hit and miss affair on each boot, but works well when it does. I invoke 3g in WinMo and usually works well in Android after that but a few boots gave me the pppd started error which meant I had to reboot and try again.
[Touch Cruise Android Development] kulen:
Bally,

Can you send a link to paypal so we can start paying donations. we are losing time by not collecting money. people might lose will to give money if we wait too long.

If you didn't arrange details with vilord could you post a link so we pay you money. and when you collect enough you can send it to vilord so he can buy a polaris.

The rest of money (if there is some) could go for a bounty.

P.S. I have HTC touch cruise. is it completly the same as this O2 we plan to buy for vilord?
[Touch Cruise Android Development] life02:
The OK button is finally working

Guess what? I now have the center button working as OK! The entire dpad now works as it should. I have attached my latest zImage with the new corrections.
[Touch Cruise Android Development] pananza:
Nice one. I'm downloading this to test now....
[Touch Cruise Android Development] bally3:
Yeeeay! (Again!) :)

Thanks for not quitting on us Life02!
[Touch Cruise Android Development] bally3:
Yup, does what it says on the tin! nice one :)

Are you pushing these changes to the google tree Life02?

I assume these changes will not affect or break things in the other devices?
[Touch Cruise Android Development] dzo:
Can you push your changes to the ltg git repo so everything is in one place. Join the mobile-linux project to get access.

http://projects.linuxtogo.org/projects/mobile-linux/

Thanks
[Touch Cruise Android Development] Michel82:
Whoohoo!! This small change makes such a big difference in usability! Love it. Now we have to see how to merge this with the big tree. Bally since you're in comms with vilord, could you ask him to merge this change with the vogue branch?

Im really glad to see we have someone on board who's actually capable of making kernel changes. Sure hope vilords promise to help us out too, hasn't scared you off, cause we need all the help we can get.
[Touch Cruise Android Development] bally3:
I'll have an answer by the end of the day, dont worry.

and yes, its exactly the same thing. If you're happy to send it to vilord for testing then we'll happily pay for the postage. I could have sent him mine and bought one from the donations but the reason I did it this way and prefer to do it this way is transparency because it involves money and it always gets ugly where money is concerned. We had that with the 3D driver and to be honest, it was one of the factors that killed off the project in my opinion, ugly and slanderous postings from a few wasters regarding donation links - yuck! the memory of it still leaves a sour taste..

I'd rather avoid it here hence the ebay purchase - everyone can track whats been bought and paid for from their donations. Also if its bought this way, as vilord suggested, it can be sent to different people to fix different things as required.
[Touch Cruise Android Development] ovindahl:
Summary

I have a touch cruise, and would love to run android on it. This thread is getting quite long, so I would love if anyone could post a short update on how far this development has gone. What is working/not working? When (if at all), will it be possible to switch over to android 100%?
[Touch Cruise Android Development] kulen:
I'll be happy to donate and forget about that money, but I can't send my phone.

10 EUR is how much I just spent on the beach for drink. so it's not some money to spill blood about.

and this is much more useful than drinking some coffee.

But I understand people are different and it can get hard when it comes to money so I just hope this will work and we will get a fully funcional Android for our Polarises.
[Touch Cruise Android Development] life02:
These changes are specific to the polaris board and therefore will only affect our device. Everything I have changed so far has been in board-htcpolaris-keypad.c. Once it's uploaded to the distribution tree, all future kernels compiled will have the changes incorporated.

I have also uploaded the new zImage to the vogue-android google code page under Issue 23. Hiket said he would take the file and add it to the front page.
[Touch Cruise Android Development] bally3:
Nice one Life, looks like we're really rolling.

I've pm'd you, can you meet up with me for a chat here I'm there now.

Thanks.
[Touch Cruise Android Development] bally3:
I've cleared it with Vilord and he's happy to make the purchase.

If everyone can start donating to his link: VILORDS DONATIONS

I've asked vilord to let me know who donates and how much, if we dont make the target before the phone is sold or the auction finishes, then he will look for another one for around the same price.

Can everyone make their donations as soon as possible please.

Can someone post this link to the Bounty thread too.

W04g005, can you update your first post with this information and also pm it to everyone whose offered donations.

Thank you.
[Touch Cruise Android Development] fets:
I did it : 30 $
[Touch Cruise Android Development] tfm426:
$10 from me good luck with it i cant wait.
[Touch Cruise Android Development] cuzzo94:
can this version of android run on artemis?

thanks
[Touch Cruise Android Development] pananza:
$20 from me sent...
[Touch Cruise Android Development] briggs81:
Donation sent!
[Touch Cruise Android Development] cuzzo94:
nothing? pleaaaaaaaaseeee:)
[Touch Cruise Android Development] bally3:
The Artemis has an OMAP 850 chipset, which is also the same on the htc elfin which has more than a passing physical resemblance to the Vogue incidently.

I would check the efin forum and see and also the Artemis forum for Android threads and see what progress has been made. Failing that, google Omap 850 android and see what you get.

If you have no luck there, you may as well have a go with the files posted in my signature and see how far you get. Unfortunately we cant help you beyond there as we do not own the device or have much knowledge of it.

If you're the first - and I doubt thats the case - to have thought of it then you may have better luck creating thread on the Artemis forum and posting these files and what you've learnt and see whether you can get some devs on board to discuss what needs to be done to make or port to a working kernel.

All the best - its how we all started :)
[Touch Cruise Android Development] nemiers:
20$ your way!
[Touch Cruise Android Development] cuzzo94:
i've tryed with the files in your signature but the screen become black.......
[Touch Cruise Android Development] bally3:
Sorry Cuzzo, cant help you any further. Please ask in the Artemis forum or start a thread there as I suggested.
[Touch Cruise Android Development] kulen:
15$ donated
[Touch Cruise Android Development] Mormy:
20$ donated :)
[Touch Cruise Android Development] bbezja1:
$30 donated

life02 thanks

bally3 thank you

i hope you can get things moving full speed ;)
[Touch Cruise Android Development] cuzzo94:
ok thanks!!:)
[Touch Cruise Android Development] bbezja1:
what the hell? its 200 eur MAX in germany. it would be cheaper to buy it in .de and send it :S
[Touch Cruise Android Development] w04g005:
20$ donated.

One of the Polaris i saw in a german forum os now beeing sold on Ebay:

http://cgi.ebay.de/ws/eBayISAPI.dll?ViewItem&ssPageName=STRK:MESELX:IT&item=280368342238viele

look at it maybe it will be very cheap (if you compare it with the us prices!)
[Touch Cruise Android Development] kulen:
just find one on ebay or somewhere else and link it to vilord. I believe he'll buy the best he can with that money.

and if, after he buys it, we find a cheaper one I won't be sorry. I donated money and forgot about it. I just hope it will lead to fully functional Android for Polaris.
[Touch Cruise Android Development] vilord:
Hey all, don't worry I'm not gonna go spending $400 bucks on something that can be had for half that from an intl auction... But I do want to be sure I actually order the right device. What is the model numbers? I guess the "polaris" that is listed for $400+ is not the same device? How can I tell what the right one is?

Thank you, and I really hope I can fulfill your expectations!

EDIT:

Okay I see what the right device is. What should I be expecting for total price in USD, about $200, or more than that?
[Touch Cruise Android Development] imfloflo:
Yeah there is a new version of a HTC device which name is polaris but our polaris is also known as HTC CRUISE/POLARIS(POLA100)
[Touch Cruise Android Development] bally3:
This was posted in the old thread by Dcordes, I thought might help us since we're having a developers renaissance:

NOT YET WORKING "HOW TO HELP DEVELOPING" GUIDE

How to develop

I've used a Linux distro called Ubuntu, version 8.04, default installation x86 (so not the AMD_64 version):

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

sudo -i

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

aptitude update && aptitude upgrade -y

Your system is now up to date.

You have to install a couple of packages so you can cook your own zImage so enter:

aptitude install git-core git jfsutils xfsprogs quota isdnutils-base nfs-common oprofile

Checkout the git

First make a directory to put everything in:

mkdir ~/android-kernel

Now go to that directory

cd ~/android-kernel

Get the google android git:

git clone git://git.android.com/kernel.git

Switch directory:

cd ~/android-kernel/kernel

Checkout the andoid-msm-2.6.25

git checkout -b android-msm-2.6.25

Get linux toolchain:

Change dir:

cd ~/android-kernel

Download toolchain (around 100mb)

wget http://www.codesourcery.com/gnu_toolchains/arm/portal/package2549/public/arm-none-linux-gnueabi/arm-2008q1-126-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2

Unpack it:

tar -xjf arm-2008q1-126-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.*

A

pply patch file:

Get patch file:

wget http://linuxtogo.org/~lgorris/git-diff-2.6.25-170908-polaris.diff

Change dir:

cd ~/android-kernel/kernel

Patch it:

patch -p1 < ../git*

Make a zImage

Change dir:

cd ~/android-kernel/kernel

Prepare it (using config file)

make htckaiser_defconfig ARCH=arm

Cook it:

export PATH=~/android-kernel/arm-2008q1/bin:$PATH

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

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

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

Older info:

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

http://xdaforums.com/showpost.php?p=2311710&postcount=168

Movies:

http://www.youtube.com/watch?v=64LYnTxhj44

http://www.youtube.com/watch?v=tV_fsLkNTEE
[Touch Cruise Android Development] bally3:
Mine is a POLA200 btw, 02 branded XDA Orbit II
[Touch Cruise Android Development] kulen:
Where can I see which model is mine?
[Touch Cruise Android Development] bally3:
If someone wants to help out but cant develop yet, if you try the info posted above and succeed, can you take screenshots/videos and put together "Polaris developing Guide for Dummies" type of thing on the Wiki please?

We could really use something like that to encourage more people to have a go.

Life02, can you take a look at that info and correct/change it to how you do things please?

Thanks.
[Touch Cruise Android Development] Mormy:
I have an O2 XDA Orbit II too and like yours is a POLA200

I take a look under the battery
[Touch Cruise Android Development] bally3:
Underneath the battery in the compartment on the top left side it should say POLA100 or POLA200.

It would be interesting to find out whether theres a difference in components between the two, certainly would go some way to explain why we have so many variations in results when using Android.

Booting issues for example could be card or radio related, but calls and data issues (providing apn details etc are there) are more likely to be radio or device related in my opinion.
[Touch Cruise Android Development] kulen:
I have HTC Touch Cruise

Under the battery says POLA100

and product number (P/N) is 99HDZ012-00 B
[Touch Cruise Android Development] briggs81:
Mine is a POLA100
[Touch Cruise Android Development] Mormy:
Sorry, I don't know that P/N is important. Byaway:

POLA200

P/N: 99HEK001-00
[Touch Cruise Android Development] pananza:
POLA100 here...
[Touch Cruise Android Development] rogro82:
Try the files i uploaded.... dont seem to have that problem. Did you get the sdk 1.0 or the latest version from DZO?
[Touch Cruise Android Development] Vo1:
system.img and data.img from http://it029000.massey.ac.nz/vogue/
[Touch Cruise Android Development] kensou.8:
I'm trying WorkingAndroid.zip.

I get a lot of :

May be, it is an issue with my sd card :confused:

My sd card is an sdhc formatted in FAT16
[Touch Cruise Android Development] rogro82:
Its because of the video driver... still need to change to polaris code on this one.

It shouldnt give any real problems for booting
[Touch Cruise Android Development] radem205:
I have this also! (sorry, I didn't read the previousest post)
[Touch Cruise Android Development] kensou.8:
It seem to be a IRQ conflict.

a remapping of IRQ may solve this issue i think
[Touch Cruise Android Development] rogro82:
Ok ive created a manual on how to I was able to make a kernel that can make the Polaris to boot android.

Hopefully someone can clean up all code and make Android work in both the polaris and kaiser and maybe some other devices.

Ive included a short manual and all files I think were needed.

http://rapidshare.com/files/176877021/Android_vogue_merge.zip

I know its not the cleanest etc... but due to my lack of time and knowledge ( ive just started working on linux/android for 2 weeks or so ) its the best i could come up with.

To boot after creating an image make sure you get the android 1.0 sdk and use the correct default.txt that can be found here in my other upload. ( page 14 of the Polaris Android thread )

Good luck :) and merry Christmas to everyone...
[Touch Cruise Android Development] kensou.8:
I still don't understand why certains can boot android 1.0 and others can't.

I still have this error:

mdp_irq_already on already on 4 4

mdp_dma_to_mddi: Busy

How can it be possible ? the hardware is the same after all ?
[Touch Cruise Android Development] belabartok:
I`m going to download it now, thanks rogro
[Touch Cruise Android Development] Swifty:
Are your android files at the root of the SD card? (ie. not inside any folders)

Boots on my Orbit2, great work Rogro!