yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] kulen:
you can find working tattoo build here:

http://xdaforums.com/showthread.php?t=544906&page=201

have not tested much but I think there is some problem with audio and wifi doesn't work. but I believe it'll be fixed soon.
[Touch Cruise Android Development] Michel82:
Android 1.6 (Donut) system for dev phone and ion are available for DL:

ION: http://developer.htc.com/google-io-device.html

DEV phone: http://developer.htc.com/adp.html
[Touch Cruise Android Development] whashnez:
Android 1.6 (Donut) system for dev phone and ion are available for DL

So what can we do with tsese builds?Flash them to polaris?
[Touch Cruise Android Development] imfloflo:
This is a KERNEL development don't post new build here!

Devs are aware of this new SDK and will release new builds compatible with our device soon be patient. Thanks
[Touch Cruise Android Development] dzo:
OK, I had a bit of spare time today and I fixed the wakeup behavior so you have to press the power button now. This was pretty trivial really. I had a play with the phone and things seem to be working pretty well. To get good power consumption make sure you disable wifi and that gps is not on before switching the phone off. Also disable background data. If you do this, the battery should last a few days.

The new kernel is here:

http://cs-alb-pc3.massey.ac.nz/vogue/files/zImage-01-10-09
[Touch Cruise Android Development] imfloflo:
Yeah thank you very much dzo first step in polaris world
[Touch Cruise Android Development] Michel82:
Great to have you on our side dzo! This whole android porting crazyness all started with your first kernels for vogue. Hope you can make some steps in porting things working on vogue that are not working on polaris yet (camera, mic, bt, power mgmt).

With you on the polaris team and all the development on the roms i really feel like were moving towards a mobile os that can be used on a day to day basis for a large group of individuals.

Downloading your latest kernel now.
[Touch Cruise Android Development] Skywalker74:
My battery never charges till 100%. 95% is the maximum. Any thoughts why is that?

I have board-htcpolaris-battery.battery_capacity=1350 in my default.txt
[Touch Cruise Android Development] bbezja1:
thanks dzo, thanks alot
[Touch Cruise Android Development] joannerve:
With the latest kernel after going to rest android system (when go black) and after a time resting I can not use it. It continues in black and I can not wake up so I need to reset.
[Touch Cruise Android Development] vilord:
Hmm, thought I'd fixed the wakeup about a month ago, I guess there was another step I missed...

I'm thinking I should shut down the code-google page, bring my code from github to sourceforge...

What is the new plan for releasing builds? Are we just going to release with all of the google apps stripped out, or are we going to stick with torrent sites and megauploads etc?
[Touch Cruise Android Development] bally3:
hey hey welcome back vilord my friend :)

looks like you mean business too!

all good stuff...
[Touch Cruise Android Development] vilord:
Hey! What've you been up to?

You ready to buy a tattoo and put the polaris on ebay?

Oh yeah, and whats the status here? not many posts in the past weeks...
[Touch Cruise Android Development] moesfeld:
Hmmmm:confused:

The rulez say no warez but relasing roms (WM 6.5) seems to be no problem since M$ didn´t complain.(AFAIK)

But Google did. So I think it´s up to the mods.

The Google Apps is what is making Android special (besides UI).

So if the mods say "I´ll allow it" I would go for Megauploads torrents etc.

But that´s only my two cents. I´m not owning a Polaris but this project almost made me buy one( but pending now because of the cryogen/google/etc..).
[Touch Cruise Android Development] vorticerosso:
I'm waiting for Android on polaris too.

Please. torrents, Megauploads etc ;-)

I hope Google changes mind, I'd like to have a full working Androind on Polaris.

Thanks for the great job.

VR

PS: Does someone can guess when a new build with bluetooth working or Android 1.6 will be released ?
[Touch Cruise Android Development] bally3:
Its a sticky situation for sure, on one hand Google have opened up a platform for developers to create whatever kind of system that they wish to use, on the other hand they are effectively close-sourcing their own apps that many will see as key to the usability of the system.

I was rather hoping that Google wouldnt go down this road but we all know that Google isnt any more a friend of ours as Microsoft or Apple. Even Palm having used an Open Alliance webkit to create their OS have recently announced their dirty plans to control their Market for "quality" purposes similar to Apple's policies. In the end they are all businesses in the business of making money.

We do need to have some self-moderation with the Google apps issue, but I'll stress again that these are userspace issues and we should only be concerned with the kernel at the moment which still has a fair bit of work to do on it to make it usable.

With dzo and vilord back, I hope this will push forward in the coming weeks, the lack of camera is a real deal-breaker for me and I havent really bothered using Android these last few weeks as I constantly find myself having too switch back to use the camera which is annoying. Also I still experience call issues (no sound) randomly. All these issues will need to be and hopefully will be addressed in the near future to make android more usable and then maybe we can worry about what to do with missing google apps, hopefully someone will already be working on replacement apps if we're lucky.

The thing to remember here is that the more complete kernels we have for all these devices, the more talented devs we should be able to attract and hopefully that will trigger some development on open source apps to replace the google apps we lose.
[Touch Cruise Android Development] bally3:
Here you go, I'm thinking it and others are already planning it:

"Cyanogen's announcement came as a separate group of open-source developers said they planned to create an Android alternative that includes their own versions of the closed-source apps that Google is forbidding Kondik from redistributing. Dubbed the Open Android Alliance, the project plans to write or borrow open-source clones of those apps that are built from the ground up so that Google has no legal claim over any of the code."

Source: http://www.theregister.co.uk/2009/09/28/google_android_developers_reaction/

looks like theres a group of devs already working on an idea for alternative apps.

smile.. open source is THE only way.. :)
[Touch Cruise Android Development] bbezja1:
from how i see... google gives you a nice and supported mobile system BUT only when he wants some credits for his entirely own apps they stab him in the back and say FU we will exploit the open source you so openly and friendly choose to build on and push you away. google we dont need you anymore we can do it on our own. you made the market now we gonna make it our own.

EDIT: seems to me like google didnt think it through
[Touch Cruise Android Development] bally3:
Naah not buying a tattoo, I'm sticking with the idea of a dual boot and best of both worlds. Cant drop winmo until android has an alternative gps software that isnt turn by turn. (igo8 on linux anyone?)

status is what you see right now, we got working wifi but everything else is pretty much as you left it bar the userspace developments.
[Touch Cruise Android Development] whashnez:
To Bally

Excuse me bally but Microsoft is too far from being friends with anyone in this world...Everything they release is closed-coded and as a computer engineer I can tell that every operating system they release is 20 years behind cause it's based on the first steps of Bill Gates at operating system developing...Plus many other things that may cause harm to all of us...At least Google gives some open source code, but it' s always a huge company that all they care about is money...Now, if somebody would create a real open source linux operating system for pocket pc's as it is for desktops, then we 'll have a very different story... But I think we are far away from something like that...
[Touch Cruise Android Development] bbezja1:
back that up with facts please? as a computer engineer i can say that what you said is generaly true but has no point (no meaning?). did you even see what "first steps of bill gates" look like?
[Touch Cruise Android Development] bally3:
ok lets not get into a my "os is better than your os argument"

washnez, i think you missed my point there which is that google arent any better than ms, oh we were al hoping they were when they released android as open-source. as far as close-sourcing is concerned, all the roms we enjoy and a lot of the apps on them are "close sourced".

I expect google woud quite rightly take a much tougher stance on the matter if devs continued to include google apps.

The question you have to ask yourself is this: if google apps are illegal for you to use if you do not own a android phone, will you continue to use android without them or illegally install them?

you see my championing android was basically from the fact that i liked the moral high ground that linux offers me to enjoy new developments without forking out hundreds of pounds i can ill afford or by breaking the law with illegal downloads. My dissapointment thus is now that google have taken these steps to stop the use of their apps, which lets face it, without them android is a pretty shallow experience, am I willing to accept androids shortcomings and use it as my full time system of choice?

I'll let you know when we have a fully working kernel and i've switched over and I've used android full time for a few weeks! :)
[Touch Cruise Android Development] imfloflo:
Guys this is a Android kernel thread ...
[Touch Cruise Android Development] bally3:
yup.. and lets get back to kernel developing :)

You may have noticed that I've not been as active on the forum of recent, one reason for this is that work has overtaken my me-time as students return to study, this happens every year, but there is also another reason for this. I am now re-evaluating my time with the Polaris kernel development as I feel I have wasted precious time waiting around when I should have used that time on other projects.

One such project is the HTC Hermes Android project which I'm looking into re-energising if I can get any devs on board as this is one of the devices that is capable of running android but development has lost momentum and so far its at a kernel booting stage.

This is not to say I will no longer be involved with the Polaris project, far from it, I want to see this project through to completion and it will remain my number one priority, but I also do feel that with the devs back, development will progress in its time with or without my input which is how it should be anyway.

Of course theres always a need to kick the project up its hindsight occasionally... :)
[Touch Cruise Android Development] SnoopThaDoctor:
Latest build for Polaris?

Forgive me for asking... but besides discussion about new kernels and builds, new kernels/builds for Kaiser/Vogue keep showing up in this thread. As a newbie and having an almost insane curiousity for Android, I'm wondering which latest build/kernel (don't know what I'm talking about:D) I can or should download for my Polaris :confused: THANKS and I appreciate your efforts to port Android to Polaris!
[Touch Cruise Android Development] idreadful:
I am not sure if it's kernel issue, but it seems that applications (except phone) cannot access mic. Neither voice recording nor spectral analyzer record nothing except silence.

P.S. Glad that android on polaris seems to have a future with devs here, thank you.
[Touch Cruise Android Development] bally3:
idreadful, the mic issue I believe stems from the sound driver which is also one of the things we hope dzo will be able to resolve for us.
[Touch Cruise Android Development] idreadful:
Excited about that =)
[Touch Cruise Android Development] dzo:
OK, I got audio in to work. The quality isn't very good yet but it does work. To test it, compose a new SMS message and then press menu..attach and chose "record audio". Voice dial doesn't work very well but voice search and the maps voice search should work ok. I haven't tried shazam on polaris but it should also work.

The new kernel is on the google code site.
[Touch Cruise Android Development] imfloflo:
Great job dzo thanks ;)

BTW : What do you think about the HTC polaris ?
[Touch Cruise Android Development] Mormy:
Good news :)

Thanks for going on...
[Touch Cruise Android Development] idreadful:
Thanks, dzo! Audio recording works well, i could make a record in message attachment, as you told. Once I made a record, "sound recorder" application crashed. Spectral analyzer displays graph and react on the sound!))) Great! Also glad to have right power button mapping now.

Will put my eye here regulary.
[Touch Cruise Android Development] radem205:
Thanks dzo for your work! I've tried Shazam and it's working great! Good work!

I trust that Android becoms fully functional with your hard work!!
[Touch Cruise Android Development] idreadful:
After closing any app which uses mic, mic doesn't work anymore.

adb logcat after that:

W/AudioRecord( 1485): obtainBuffer timed out (is the CPU pegged?) user=00000000, server=00000000
W/AudioRecord( 1485): obtainBuffer timed out (is the CPU pegged?) user=00000000, server=00000000
W/AudioRecord( 1485): obtainBuffer timed out (is the CPU pegged?) user=00000000, server=00000000
W/AudioRecord( 1485): obtainBuffer timed out (is the CPU pegged?) user=00000000, server=00000000
W/AudioRecord( 1485): obtainBuffer timed out (is the CPU pegged?) user=00000000, server=00000000
W/AudioRecord( 1485): obtainBuffer timed out (is the CPU pegged?) user=00000000, server=00000000
W/AudioRecord( 1485): obtainBuffer timed out (is the CPU pegged?) user=00000000, server=00000000
[Touch Cruise Android Development] dzo:
I've almost got the camera working. I wrote it for polaris but it has problems with colour on polaris and works fine on kaiser, this could be caused be a different adsp image in the kaiser radio.

The following things don't work:

It doesn't use the full sensor resolution because my vogue userspace driver only supports the vogue resolution.

It doesn't do any focusing so won't work for close ups.

Exposure control isn't great so it may take some time to adjust and will be grainy in low light.

Colour information is wrong on Polaris, this gives you some psychedelic pics but thats probably not what you want. I'm posting it anyway in case it works on some polaris radios.

New kernel is on the google-code site here:

http://code.google.com/p/vogue-android/downloads/list?can=2&q=&sort=-uploaded
[Touch Cruise Android Development] dzo:
I found a workaround for the colour problem. If you start the camera and then close it in wince before booting then it works. There's obviously something I'm not setting up correctly.
[Touch Cruise Android Development] imfloflo:
Nice 2 posts and 2 news functionality thank you :)
[Touch Cruise Android Development] idreadful:
Really great news! Android on polaris runs camera much more faster than WinMo! Great progress, dzo =)
[Touch Cruise Android Development] bbezja1:
alright!! thats what I want :p

amazing job dzo, amazing
[Touch Cruise Android Development] Michel82:
omg, with this pace of kernel releases we'll run out of things to do for kernel developers in no time. ;-)
[Touch Cruise Android Development] pananza:
Nice work. It's been a long time since I last tried Android because all the latest I've tried had audio issues when someone called me. Can someone please list a combination of files that work with these new zImages?

Are these a good combination (all from google code site)?

zImage-08-10-09

system-dont-be-evil.sqsh

basefiles-20090915.zip

rootfs-01-09-09.img
[Touch Cruise Android Development] imfloflo:
@pananza : I hadn't be able to boot with the files you named :(

after renaming system-dont-be-evil.sqsh to system.img the android don't want to mount system/

edit: try another old working android but unable to launch the launcher or to add a shortcut on the home screen, can't have menu :o very strange
[Touch Cruise Android Development] radem205:
Very nice job dzo! It's going very fast now! It would be very great to have the headset working.
[Touch Cruise Android Development] SuperJMN:
I can't test it because since they forced Cyanogen to cease and desist, I don't have any good source for a bundle. As imfloflo says, that file combination doesn't work. Any recommendation?

Thanks!
[Touch Cruise Android Development] imfloflo:
@SuperJMN you can add google's apks manually from an older rom.
[Touch Cruise Android Development] Kiiv:
Wow, great work dzo! Thanks you for your time, it looks very great, i will try it for sure.
[Touch Cruise Android Development] imfloflo:
@Kiiv can you tell me if this works with your lastest configuration cause try with your lastest package you previously post and everytime android failed to mount the system.img
[Touch Cruise Android Development] Kiiv:
Yes, i've tried right now and same thing for me. Seems it looks only for a "system.img" file and I've only .sqsh files... I don't know if it's the zImage or the rootfs file which is the problem...

Maybe I could find an old .img file but it will be a very old build :(

Dzo, which system file are you using?

EDIT : system-dont-be-evil.sqsh works fine with zImage included in basefiles-20090919-v2.zip

So I wonder that this is the new zImage that don't support sqsh file system. No problem for me if there is new builds in .img format ^^
[Touch Cruise Android Development] mylostnick:
Hi! First of all many thanks to Dzo for his hard work.

Then I want only report that on my device (HTC Touch Find - POLA200) camera doesn't work with latest kernel...

Trying to access my camera I've an error message for processocom.android.camera.

There's something I can do to help to improve the kernel code (error log or other)?

Thank u very much for all. Bye-
[Touch Cruise Android Development] Kiiv:
Which system file are you using to get it work? :confused:

EDIT : I'll continue the discussion in the dedicated thread ;)
[Touch Cruise Android Development] mylostnick:
I've used basefiles V2 with a msmisonrogers system of 11/09.

It's the system I currently use. I've replaced only the zImage file.
[Touch Cruise Android Development] radem205:
Try using the original cupcake system (I don't know exactly where you can download it at the moment). With the original cupcake files everything is working fine and I think Dzo 'll test his releases only with this version.
[Touch Cruise Android Development] mylostnick:
Can't u upload it somewhere? Unfortunately I haven't found.
[Touch Cruise Android Development] dzo:
I've put up a new kernel with some changes to power management and the polaris leds. It works very well for me (i left my polaris overnight with data off and the battery dropped 6%) but to get good battery life you also need to do the following:

Make sure you are using the correct panel type in defaut.txt (not 0).

Disable sync and background data.

Switch off wifi before putting the device to sleep.

When in power collapse (deep sleep) the left led should flash amber and only the power key will wake the device. If this doesn't happen, then something is wrong and you possibly have something installed that is keeping the device awake.

Get the new zImage from the google code site.
[Touch Cruise Android Development] osilvan:
Hi all, I'm still having problems with audio input. When I open an application that uses mic (Shazam) I'm able to capture sound only once. It fails on next attempts and shows an error message.

Thanks in advance
[Touch Cruise Android Development] bally3:
Thanks dzo,

I'll test the power management tonight.

You've got the same Polaris as I have which is the XDA Orbit II, what panel are you using?
[Touch Cruise Android Development] dubbeld00:
Can we please focus on the development... And not on "this is or is not working for me"... The version is only to show where we are in the development, but not to report bugs... Maybe create another (not sticky) topic for some support.

Else we have to read 100 non-related posts again (like the old thread).
[Touch Cruise Android Development] rcravero:
dubbeld00

we can following yr raccomandation if anybody is updating the first page, writing what's ok and what it's not running. Maybe people is asking because it's not very clear which part of software is already running.
[Touch Cruise Android Development] bally3:
It is clearly mentioned in the first page that this a development thread ONLY.

At this point the kernel cannot be classed as a version 1 kernel. When a working version is available we will post it. until then this thread is for development and for users involved with the development of a working kernel only.
[Touch Cruise Android Development] excogitation:
wiki

I'll try - and you can also help - to keep the wiki page updated (link is in my signature).

Also just fyi I built a kernel yesterday using htcpolaris_defconfig, htc-msm branch and another using htc-vogue branch - without any additional changes -> which don't mount the SD card.
[Touch Cruise Android Development] bally3:
An update:

As you may be aware, dzo has posted that the sd card will only work with the 1.65.24.36 radio, which works is a NIKE radio that works fine on the Kaiser.

Tonight, both Radem205 and myself took the bold step to flash the radio to the Polaris after some experts on irc assured us it shouldnt cause any damage to try.

Unfortunately, Radem205 reported it only got to 5% (using CustomRUU I assume).

I tried it with the SD Card method and SPL wouldnt even recognise the NBH file as a rom, instead showing "0058002" error after the loading screen.

A bit of a set back for us unfortunately. It appears that this radio is not compatible with our device which means we may not have a working SD card resolution anytime soon. It also could mean that while the Kaiser will see more expedient development in the near future, we will again have to sit and wait patiently for someone to figure out how to get the sd card working on the Polaris.
[Touch Cruise Android Development] bally3:
OK it appears that the Polaris may need to be "Security Unlocked" to flash the NIKE radio- read http://xdaforums.com/showthread.php?t=361236

Of course that thread is about Kaiser SuperCID and not for the Polaris, but we may have to do some research into finding out how it can be done on the Polaris.

Might be worth reading up on this folks and posting your findings.

** A word of warning to the uninitiated. Unlocking the security is risky business - please only attempt to do it if you know clearly what you are doing (and how to undo it if it goes wrong!) to avoid bricking your device).
[Touch Cruise Android Development] meknb:
To security unlock my polaris i used the polarisUnlockerhttp://xdaforums.com/showthread.php?t=375338 I think once you have flashed the radio with the unlocker and click the run Unlocker button.Next time you go to your tri coloured (spl) screen it should say security unlocked at the top.
[Touch Cruise Android Development] radem205:
Nice! That is propably the one we need to let the new Radio work! Great finding!

Edit: I have succesfull unlocked my phone but when I want to install the new Radio I get the following error: "[244] Invalid Model ID | This update utility cannot be used for your pda phone. Please Check Your Update Utility."
[Touch Cruise Android Development] Skywalker74:
Same here. Security unlocked, CID set to 11111111 and when I try to flash NIKI-radio from sd-card it says "Loading ...", then "00058002" and back to the tricolor screen.
[Touch Cruise Android Development] bally3:
It appears mine was already unlocked so no go there..