yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] bally3:
There are some instructions in earlier posts a couple of pages back about using 1.1 files and then replacing them with 1.5 that might help you connect to 3G. Some people have managed to connect to Market but I'm still struggling to do so.

Let us know how you get on.
[Touch Cruise Android Development] evoluzionne:
does replacing means that i should replace the Zimage with rogro's or the other files (system, data, initrd) because in my previous kit they doesn't have on screen keyboard on it and also non-working battery indicator....
[Touch Cruise Android Development] philmayhem:
really awful build that one, are you sure it's for polaris, everytime I touch the screen, it thinks I'm trying to change the ring volume...can't believe it's june and there's still not a decent working version of Android compiled for Polaris!!!
[Touch Cruise Android Development] excogitation:
Go ahead :D

Since biktor_gj also stepped down (Nike) I doubt there's going to be progress on our end any time soon.

I'm starting my applied informatics studies in Oktober ... so about a year after that I think I could really step up ... but I highly doubt I'll still be having a Polaris by then (I can hear the I7500 calling) :p
[Touch Cruise Android Development] bally3:
relax.. it will happen.. theres people picking up cheap polaris devices all the time. Its just a matter of getting a polaris owner who knows how to compile kernel and such and we're cooking again.

Its inevitable that things are going to slow down, the majority of the devving Polaris owners have moved on. But there will be fresh blood in due course dont you worry.

The trick is to go looking for help and making sure users coming here offering to help dont get ignored. Right now theres more people waiting around for something to happen on our forum than participating unlike the Kaiser forums. If you want to help, speak to the kaiser devs and see if someone will help to complile a build for Polaris. They're decent folk, someone might offer to help us if you ask nicely enough, like biktor did from Nike forum. :)
[Touch Cruise Android Development] adderz91:
I would love to help, ive just bought a brand new housing and digitizer for my Touch Cruise so it looks like a brand new device!

I have the time to do it, but i have NO idea how to do any of it, it all looks very confusing haha, im not a dunce when it comes to computers, but i just dont know about any of the stuff needed to do that kind of stuff.
[Touch Cruise Android Development] gooner187:
The reason this is happening is beacuse you are using the default.txt included in the package, replace it with a polaris one in the wiki or just paste the text below to replace the txt in your original default.txt file. Just replace ppp. settings with your apn settings.

#Polaris

set RAMSIZE 0x08000000

set MTYPE 1723

set KERNEL zImage

set initrd initrd.gz

set cmdline "ppp.apn=internet ppp.username=t-mobile ppp.password=t-mobile mddi.width=240 mddi.height=320 mddi_client_vogue.vsync=0 pm.sleep_mode=0 board-htcpolaris.panel_type=0"

boot
[Touch Cruise Android Development] bally3:
Adderz man, you need to finish that rom of yours, I checked it out last night and you sure put some work into the theming.. shame to let it go to waste, the files Chavonbravo posted should solve the camera issue. I'd finish it if I were you.. shame to let all that hard work.

Thanks for the offer on this project btw, I guess we'll just have to see how we go on. My guess is that theres a lot riding on the new wave of phones, people waiting for compatible chipsets and the like to make it easier to port some of the functionality like camera and gps to our devices, and to the extent I think we're now in the waiting game for the while at least.
[Touch Cruise Android Development] dzo:
I don't want to pop your bubble but new phones won't help us at all. Anything that comes out will be based on MSM7225 or MSM7201A and more importantly will have AMSS 6.X running on the A9 while we are using AMSS 4. For GPS, we just need to document the AMSS pdsm rpc calls (not easy to do!). Bluetooth and wifi are close to working, someone just needs to do a bit more poking around. A working camera is quite possible because I did most of the work already getting the vogue one (crap as it is) working. So, rather than wait you just need some adventurous people to play with the device some more.
[Touch Cruise Android Development] philmayhem:
ah, yes, thank you, looks a lot better now.
[Touch Cruise Android Development] bally3:
Thanks for the input dzo :)

Sorry, just going of whats been said around here in the forums.

Glad to hear about the camera, I know wifi is being worked on. From what they're saying in the Kaiser thread GPS is looking slim a the moment.

The issue we have here is a lack of linux devs, though I happen to know a few but they are not interested in the project and the ones that were have moved on to other devices.

I tried to learn to do some of this myself, I have a laptop set up with Ubuntu but in all honesty, most of whats required is beyond my scope of knowledge and I think most novice linux users like myself. So we wait for a decent dev to come on board and offer his/her services... :rolleyes:
[Touch Cruise Android Development] imfloflo:
I'm stille here to try the build but like i use my phone for daily use i can't soft/hardreset to often.

I can give you some gpio code if need, like we did previously with exco.

But we still need linux dev after to modify the source for our polaris.
[Touch Cruise Android Development] bally3:
I might have somebody willing to take the on the work, I'm waiting for them to get back to me. He's a friend of mine and very verse in linux and kernel stuff.

Fingers crossed! :)
[Touch Cruise Android Development] bally3:
still waiting to hear back from this guy, anyone else want to try and encourage a linux dev or anyone willing to lend a polaris to any devs by all means let it be known.
[Touch Cruise Android Development] bally3:
Thanks flo, I probably wont be using mine full-time soon so i will be able to try a bit more, (Im getting a new phone for my birthday next week - or so i believe!) I really hope we can get another dev on board soon.
[Touch Cruise Android Development] gygy:
Latest zImage an initrd

Hello guys,

I'm noticed that the kit posted on the first page is very outdated. Can somebody please give me the link for the best working version ?

Thank you !
[Touch Cruise Android Development] radem205:
The new ION files are working great (also on the polaris!! Only wakeup isn't quiet right but it works). Try it out: http://xdaforums.com/showpost.php?p=4003156&postcount=5917
[Touch Cruise Android Development] BeRo1985:
Which default.txt content does you have used? At me boots it with the kaiser default.txt but the polaris hardware keys doesn't respond correctly (instead these triggers numeric keys on my polaris) and the screen is wrongly 180° rotated.
[Touch Cruise Android Development] imfloflo:
HAve you change the MTYPE number in the default.txt to the polaris one ?
[Touch Cruise Android Development] BeRo1985:
If I do this, then I get only a corrupted screen with random memory content. I guess it uses then a wrong framebuffer memory offset or something in the kind.

Only as far from my view as a linux developer of a embedded broadband router company and an active demoscener with recently focus on embedded devices.
[Touch Cruise Android Development] briggs81:
wow it is pretty responsive.

I am using imfloflo's default.txt with it, have not tried the included one. Interface seems a bit big for the polaris, but still impressed wtih the speed.
[Touch Cruise Android Development] briggs81:
any channce someone could post their default txt that works correctly with these ion files? or maybe also say what the correct screen resolution should be?

just playing around with it still and am susprised how quick it is. still have to get internet connection working though
[Touch Cruise Android Development] pananza:
I use this settings file. The true resolution on Polaris is 240x320 which is actually too small for Android. Android apps are usually created for 480x640 or higher. But tweaking a bit and setting resolution to 312x416 scales down the UI of Android. This makes more app usable and more room on the desktop for shortcuts and widgets.

#Polaris
set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.gz

set cmdline "mddi.width=312 mddi.height=416 pm.sleep_mode=0 board-htcpolaris.panel_type=0"
boot
[Touch Cruise Android Development] briggs81:
very nice thank yoy. are you using the default txt provided with polaris modifications or are you using one of ypur own with differrent parameters?
[Touch Cruise Android Development] pananza:
??? I am using the one I posted.
[Touch Cruise Android Development] briggs81:
oh! ok, great. I will try yours out.
[Touch Cruise Android Development] briggs81:
Hmm quite a few things not workin' quite right yet I guess.. oh wel! Still impressed with it's speed.

What radio you guys using?
[Touch Cruise Android Development] schrotti007:
Working really nice but unfortunately, my internet connection still doesnt work. When i start the modem app and click connect, it says im connected, my phone ip is something with 10.72... and my p-t-p ip is something with 10.64.

I always get this kind of private network ips because my network operator (o2 in germany, provider is tchibo) puts many users on one public ip

however, is it possible that there is a network device in android that is also using private ips in this range, maybe the wlan or bluetooth or the virtual usb network connection?
[Touch Cruise Android Development] gygy:
Thank you !

Works very well.
[Touch Cruise Android Development] pananza:
The new ION files are really good. WiFi, bluetooth, gps and camera still don't work. But all basic Android OS features works including 3G. Also most apps work fine including Android Marked.

But there is still one big issue and that is power consumption. Even though the screen turns off the CPU does not sleep. I can feel that the phone is slightly warm and it eats through a freshly charged battery in about 4 hours.

I tried to use Android on my phone all day and it's worked fine both during calls and when I was listening to some mp3's on the head phones. But this evening the phone was dead and the battery totally flat. Would not even boot into WinMo until it has charged a couple of minutes.

I assume this is a known issue. Can anyone confirm this, or post and solution to this if known?

Thanks.
[Touch Cruise Android Development] bally3:
You're having more luck than me.. I cant get past the image extraction - even after leaving for half and hour! :rolleyes:
[Touch Cruise Android Development] briggs81:
What radio are you using?

I can't call out to anyone, it automatically ends my call. And forget about a data connection, that won't even bother to try and work!
[Touch Cruise Android Development] radem205:
Indeed this is a known issue. Unfortunatly the battery isn't optimal yet for the polaris. And also the battery calibration isn't good for the polaris. In Android the battery level is 40% for example and in WinMo it's 10%.

I think for us polaris users we have to wait for someone who can fix this (I think it isn't quiet difficult, but for now I don't have knowledge to fix this :().

I read somewhere it's possible to set the battery capacity in default.txt, but I don't know where I can find it and if it works...

I'm using Radio 1.59.42.15 for such a long time without any problems during calls.
[Touch Cruise Android Development] briggs81:
Anyone using radio 1.59.46.12?

I can't seem to find 1.59.42.15 to test with, just the radio rom.

nvm found it. Have to re install android, after updating radio, android just loaded a multicolored crappy screen!

edit edit: even after installing fresh radio rom and fresh android, get the crazy colored screen. can't use it. damn
[Touch Cruise Android Development] rthunstrom:
The ION files does not work on my Touch Cruise (Polaris) regarding connection to internet. Yes, it is slightly faster than my usual setup but if it doesn´t work..

I upgraded from an working 1.1 to 1.5 using http://www.ratedo.com/android/android-1.5-upgrade-kaiser.zip.

I get my zImage from http://it029000.massey.ac.nz/vogue/files/?C=M;O=D and the System.img from http://www.ratedo.com/android/

This is my default.txt:

set RAMSIZE 0x08000000

set MTYPE 1723

set KERNEL zImage

set initrd initrd.gz

set cmdline "mddi.width=264 mddi.height=352 ppp.apn=internet.telenor.se ppp.username=none ppp.password=none pm.sleep_mode=0 board-htcpolaris.panel_type=0"

boot
[Touch Cruise Android Development] pananza:
I too use radio rom 1.59.42.15. What WinMo ROM I'm using does not seem to have much effect. Now I'm even running with the standard plain WM 6.1 rom from HTC.

This is what I did to get 3G working in Android:

1. Go here http://en.wikipedia.org/wiki/Mobile_network_code and find the MCC and MNC codes for your mobile network.

2. Make sure you do not have PIN code security turned on (disable it in WinMo).

3. Make sure you have a 3G connection running in WinMo before running Haret. (Sync mail, update weather or whatever)

4. Boot Android

5. Under Settings \ Wireless controls \ Mobile Networks \ Access Point Names make sure you have a setting with the corrent MMC and MNC as specified in pt 1 above.

6. Run the "Modem" application in Android and click "Connect".

Then I get a public IP for the phone and some private 10.64.x.x address for P-t-P whatever that is.

Good luck.
[Touch Cruise Android Development] pananza:
You can add board-htcpolaris-battery.battery_capacity=1350 to the cmdline

in default.txt (the polaris has 1350 mAh batteries as default). I've seen this over at the Kaiser threads, but if it has any effect for us I don't know.

Also you can try to specify pm.sleep_mode in there as well. The phone is not hot is I specify pm.sleep_mode=1, but I'm also unable to wake the phone if it's been sleeping for more than a few seconds :)

pm.sleep_mode - The mode used when the phone is off

0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep, 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt

Default is 0, use 3 if you have an old radio, 1 is best power saving.
[Touch Cruise Android Development] briggs81:
Sigh, even with that radio I still can't make any calls :(
[Touch Cruise Android Development] radem205:
Do you have pin disabled?
[Touch Cruise Android Development] briggs81:
I have never enabled it, so probably not, but i'll check.
[Touch Cruise Android Development] pananza:
If you need to enter a four digit pin number every time you boot your phone into WinMo then it's enabled. If not, then it's not.

If you still cannot make calls it might have someting to do with your SIM card or carrier. I have a totally free phone (not locked to a carrier) and a standard non-pre-paid SIM card. Can call and receive calls just fine.
[Touch Cruise Android Development] briggs81:
hmm.. odd. I have never had a problem making calls with android before.. at least dialing numbers.. just these ion packages.

My phone is not locked either, and my sim card is somewhat new. very odd. Guess i'll keep trying.
[Touch Cruise Android Development] MercuryMonkey:
Can't get past setup screens

Loving the work here.

I've tried to get Android working a couple of times now, but to no avail. it's booting fine, but when going through setup steps to connect to my google account I can't get an internet connection, so can't get past it. I've tried with just the settings in the default.txt, and also by putting the details into the apn settings of android (by clicking the "ok" hardware button on the "tap android" screen).

Any help would be really appriciated:

Orbit2 (Polaris)

O2 UK

Ion build (link from a few posts up)

Default.txt:

#Polaris

set RAMSIZE 0x08000000

set MTYPE 1723

set KERNEL zImage

set initrd initrd.gz

set cmdline "ppp.apn=mobile.o2.co.uk ppp.username=mobileweb ppp.password=password mddi.width=240 mddi.height=320 pm.sleep_mode=0 board-htcpolaris.panel_type=0"

boot
[Touch Cruise Android Development] radem205:
You 'll have to set the APN settings manually before you are able to connect to the internet. Only the APN name and APN itself is needed for the data connection (you can find these settings under Menu -> Settings -> Wireless Settings). Use Modem (with 1.5 and ION) or Togga (with 1.1) to connect!
[Touch Cruise Android Development] Michel82:
Kaiser and Vogue development are taking a leap with the different releases of ION and Hero, with the vogue even having GPS working. We should use this momentum for development for our polaris.
[Touch Cruise Android Development] radem205:
Yes indeed, but who? I think the most releases are also working on the polaris, but for us polaris users the battery is the most annoying part :(

Edit: For me pm.sleep_mode = 1 isn't working quiet well. The screen doesn't wakup correctly, I have to push the power button several times to wakup the phone. With sleem_mode=0 I haven't had any problems with it.
[Touch Cruise Android Development] Michel82:
Just installed the vogue ION version. First thing in notice: The screen resolution is big again, or small depending on how you look at it, icons are too big. Do we need the mddi scaling again? Cause that s*cked in the 1.1. versions.
[Touch Cruise Android Development] MercuryMonkey:
Thanks for the reply radem, but I'm not sure how to do this, seems like a catch 22.

I can't get to the Menu and change the connection settings, or use Togga to connect, because I can't get past the "tap andriod to begin" setup screens where you enter your google account.

There doesn't seem to be a way of getting past these without a connection, if I press the "ok" hardware button on the first screen I can get to the apn settings (this is the only setting i can get to), which I've done, but still no connection?
[Touch Cruise Android Development] radem205:
Further on in the google setup screen you 'll find the skip button (scroll down to see this button).
[Touch Cruise Android Development] briggs81:
If my damn radio(s) would work and could make calls I would use android all day! But for some reason, any radio I use with Ion, i can't do anything that has to do with calls. I just got my sim card 1 year ago, a 3g one. Never had these problems before.
[Touch Cruise Android Development] bally3:
As frustrating as it is to see the other devices making gains on a complete operating system whilst we watch in envy, we have to accept it as we have no devs on this forum at this time to take on the work. Although on a positive note, once the dev work on the vogue and kaiser kernels get close to completion stage, one would think it would be easier to adapt the changes required to make it compatible with our device. Also some kind devs may turn their attention to the Polaris or a decent dev may come along that gets involved.

Unfortunately their isnt a more positive outlook at the moment as we really are struggling to get developers on board. As yet no-ones come forward and offered a device, though mine may become available soon and I'm hoping if I can get the dev I mentioned before interested, I can lend my device to him if he's interested.
[Touch Cruise Android Development] bally3:
I've managed to finally get the ION files booting on my device using a combination of the latest files posted on the Vogue-Android google code site and their kaiser-working-ion files from the kaiser thread, but the latest zimage that works for me is the from the end of april from dzo's files

Has anyone got a later zimage, especially with the gpu enabled to work?

A number of users have posted successes but have not explained what and how they got it to work with the ION files. It wold be helpful if you would post what you did and what files you or combination of files you used.
[Touch Cruise Android Development] bally3:
The 1.59.. radios work pretty well... what radio are you using and what rom?

Try using a 6.1 rom with a 1.59.46.12 radio which seems to work well with the old builds and has just booted into the new ION build.

The most reliable radio I've used for android is still 1.59.44.. and a standard 6.1 rom like maxnipers omnia or m-amines final roms.
[Touch Cruise Android Development] bally3:
ok.. tested various zimage builds with my working ION setup:

zimage-gpu 26-Apr-2009 12:24 works but causes market and Googlemail to blink but not start. Also data connection using modem doesnt work but that cold be the ION setup issue as other users have reported same on Kaiser thread.

The May kernel build from dzo's site gives me kernel panic on boot.

The June ones just sit at SD init and hang.

zimage-adb - June build hangs on sd init delay 2.50ms message

zimages included in the ION bulds range from hanging at extraction of data image (over an hour or so before gave up!) or hanging at various points of bootup before logo appears.
[Touch Cruise Android Development] briggs81:
I have been using 1.59.46.12 for a long time now, no problems, with windows or android. Well, I was at least able to dial out, it may not have always worked, but at least i could get data working and receive a call.

I use only 6.1 roms, lately just the 3lite3 vii ones, from naked to full versions.

I tried 1.59.42.15 also with no success. Actually, after I tried that one, any time i booted android i would get the multicolored screen of death and would have to take out battery.

Since then, I have re-flash the rom and the radio back to .46.12. I still try to make a call and it goes "end call" right away with the lovely red end call screen.

Maybe I'll try a different rom and 1.59.44 radio if i can find it.

As for how I got android to work on my unbranded cruise, I basically just downloaded all his files, used my old default.txt. Booted up every time, no problems at all, just no internet or calling.

Only time i had problems booting android was after i started messing wtih radios, and then i kept getting ugly multi colored screens, even after re flashing rom and radio and putting on fresh ion files!

But as of now I'm back to square one.
[Touch Cruise Android Development] bally3:
This has been reported before when you change radios, which is the reason chavonbravos roms with radios cooked in used to freak me! :rolleyes:

Throughout my Android journey I have used 1.59.44.02 radio which is a reliable radio for both Android and WinMo. I only moved the 1.59.46.12 after reports that it gave better battery and was considered to be a better radio that the 44.02 because of battery saving.

I havent found much battery saving and I havent had the opportunity to test call performance in Android till now but my recommendation to one and all, if you're having problems go with 1.59.44.02 radio and a stock 6.1 radio and.. (shameless plug coming..) ... enjoy the 3d driver without hacks too. ;)
[Touch Cruise Android Development] bally3:
Briggs, try downloading and flashing an official 6.1 rom with radio built in using the official upgrade method and not the sd card method.

reflash to the 1.59.44.02 radio try again - fingers crossed! :)
[Touch Cruise Android Development] bally3:
I've narrowed the issues down to the initrd.gz I think.

Using different versions of the initrd.gz file I've managed to boot up using the ION files, the kaiser-working initrd.gz and the zimage-gpu posted above to boot into android with working calls but still no data.
[Touch Cruise Android Development] briggs81:
Interesting. I wonder why it just doesn't work for you out of the box and you have to do a bunch of combinations.

I am flashing to official 6.1 atm and will flash the other radio after, and see if that makes a difference.
[Touch Cruise Android Development] bally3:
So does yours work with the zimage included in the ION package?

and are you able to run neocore.apk to test 3d etc?

If so can you post the link to the files you used? there seem be several versions.