yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] bally3:
Sadly its becoming painfully apparent that none of the threads have the development resources to take this project forward at any great speeds anymore. As exco pointed out in an earlier thread, Polaris and Nike are down to zero near enough (though rogro hasnt officially declared himself off the project) and it looks like Kaiser has not more than couple. I think we can safely surmise at the moment that most of the development is being burdened on dzo. We really need to get out there and get the word out, I'm constantly amazed how many websites reference xdev work but do any developing themselves yet the posts from many users here and on those sites give the impression that they have development experience.

If the project was dead in the water with no hope of success it would be understandable if devs were reluctasnt to waste effort in developing for it, but Android has real potential for all of our devices and now that its booting - thanks to the efforts of dzo and rogro for the polaris - and I'm sure if we put more effort in getting the word out there, some shy developer(s) will come forward as they have done for 3D driver when we made the request for help on the project.

I've been checking up on what happened to some of the other devs who were initially keen on getting us involved to see whether they were still on xdevs or not. It seems they've all moved to other devices from their recent posts, as I suspected (would have been nice to have been told) so I'm feeling a bit cheated after putting so much into this project and loyally purchasing another Polaris when I sold mine not so long ago. I honestly believe we can still do this. but we need more users going out there trying to encourage devs to join or having a go themselves if they are able to, rather than the confusing pointless posting going on in the Kaiser thread from users trying new builds and posting the same issues over and over again.

I'm quite happy to discuss and helping to decide the best way forward to get the project moving but I rather suspect most users here and on the other threads are just happy to sit back and let someone else do it.
[Touch Cruise Android Development] imfloflo:
Yeah very disappointing every project finish like that, chef, devs change thier device to the new one and poor people who can't buy new one stay without update :s

I don't think this project is dead, the new HTC G2'll be avalaible very soon in French so we could dump the rom for DZO.

I had install a ubuntu virtual machine and try to look into the android svn but i don't know all the commande, how to apply patch, which file i need to change how to rebuilt zImage or system.img after change. So i wait and try to help by finding and reproduce bug.
[Touch Cruise Android Development] adderz91:
I dont know why you feel cheated...

This stuff is hard, time consuming work. Im not surprised no one is willing to help, although i am disappointed. Its not like you can sit down for 5 minutes and get the WiFi working...it takes hours....days...weeks...

If a dev with a Polaris wanted Android, he would be putting up his hand but theyve all moved onto better devices, which is there choice.

So lets hope Rogro and DZO stay with the project.

I dont think its a case of people "not caring" or people "sitting back and letting other people do it all" The people who have the time, experience and ability to help ARE helping.
[Touch Cruise Android Development] bally3:
Sorry Adderz, maybe cheated is the wrong word, but I am annoyed that I started this thread with a number of devs who pledged their support and ended up with only rogro, who only dropped in and said he would do what he could to help and ended up doing most of it himself - as far as Polaris was concerned. But here ends my winge.. its done, cant change whats gone etc. etc.

Anyhoo, the project as flo rightly said is not dead yet and we shall strive to continue trying to attract new devs to work on it and it seems their are a number of users on kaiser willing to have a go and hopefully we'll find some on Polaris and nike to do the same.
[Touch Cruise Android Development] bally3:
Getting very excited by the progress being made in the Kaiser thread recently thanks to Markya23, enatefox, AngryDead to name a just few, hoping that the wifi starts working so we can test it and see if works for us too. :)
[Touch Cruise Android Development] biktor_gj:
That's not true! Nike devel is not down to zero! Ok, I broke my phone, and it's going to be some time until I get it back from support (hopefully fixed) but that doesn't mean I abandoned!

And by the way, some of the problems you're all having with the polaris devel is because you have some parts of the hardware uninitialized (cpld). I've been talking with excogitation, to see if with some effort from both parts maybe we can get something working (at least you already have a blinking blue led :))
[Touch Cruise Android Development] radem205:
That sounds great, but I haven't a blinking blue led yet (I guess no one has it). But it sounds great that you are able to help us to get something working!
[Touch Cruise Android Development] dubbeld00:
So if you don't have any time at the moment you are declared off the project... Btw, you mentioned before that I should make a new TS driver, but like I said before... I'm waiting on rogro, since he should fix this.

I'm not investing time in something that is already in development. Btw we can take over the code of Kaiser, so we only have to copy paste bits to get where they are.

Btw. To fix the TS and the onscreen keyboard (which we need) I also have to wait on the new TS driver of Rogro. If he is off the project, I'm also able to fix it.

Btw 2: I don't have any time at the moment, I had it before, but that was during the period rogro was still making progress and there was not really a way to address tasks to me.

Btw 3: To get things like bluetooth and Wifi working, you need to trial and error... this is taking loads of time which I don't have. The only thing I am willing to do is port things from kaiser to polaris, which is "easy" and can be done within a reasonable time-span.

Btw 4: Everyone can help developing... On page 3 you will find how to checkout the git...
[Touch Cruise Android Development] bally3:
oh wow.. triggered some responses there I see!

Sorry guys.. was having an off day and let of some steam because I was checking some of the devs who were with us before and they've moved on and since rogro is busy with in the Dream thread it started feeling a bit like another failing project. I'm glad that you guys are still around though, it does seem like we're at that point where its really looking possible to start using Android full-time as some are doing with the Kaiser. At the moment I havent been able to do this with the incoming call bug which usually means resetting the phone thats frustrating... but we're getting there.

Rogro hasnt signed himself off the project and I havent asked him - I really hope he hasnt, he's been a great asset to the Polaris community and no doubt will do great things on the Dream forum but it would be a shame to lose him on this project now that we're so close and he was the one that made the kernel boot on our devices- but I dont think as I mentioned before that creating the ts driver would be duplicating his work.
[Touch Cruise Android Development] bally3:
http://osdir.com/ml/AndroidDiscuss/2009-02/msg00119.html

Is this any good to us? it looks like an unoffical 1.5 sdk?
[Touch Cruise Android Development] radem205:
It can be good for us I think. As I read the cupcake version and the SDK 1.1 version is combined together. That would be great if this is true.
[Touch Cruise Android Development] dubbeld00:
Well I will try to continue rogro's work, but I'm very busy the next two weeks (it's a pitty that I didn't know rogro should be "quite" for this long... previous two weaks I had "nothing" to do (so I created an MP3 player using JS and Flash just search for u2 or coldplay (artist only)...)).

Nice :) anyone saw a changelog (1.1 > 1.5)
[Touch Cruise Android Development] imfloflo:
Another system.img with 1.5 cupcake version don't know if you can use some part of it http://nullwire.com/try_out_cupcake_yourself
[Touch Cruise Android Development] bally3:
Cant use the system image from that link, its more for the emulator.

I've downloaded the sdk and looking at whats there at the mo.
[Touch Cruise Android Development] Liquid-Silver:
Hi, I've posted some cpld info to the polaris wiki. I dug the information out of your MFG polaris spl. I hope this helps.

Btw the polaris has a TNET1251 wifi chip just like the HTC dream.
[Touch Cruise Android Development] imfloflo:
Thanks Liquid-Silver how can you find this value ?can you explain ?so i can find more if needed. thanks
[Touch Cruise Android Development] bally3:
Not had any response about the SDK in the kaiser thread as yet, I wonder if anyone else could direct us in how to get it working. i downloaded the linux sdk and installed it but its complaining of plugins missing so I'm going to look at it again tonight.

It would be great if it can be used, the lack of the soft keyboard is really stopping me from getting any decent use of it as I cant send sms messages using the Q&D keyboard.

Phone calls for me are working fine with 01-03 files but I cant get market working.
[Touch Cruise Android Development] bally3:
Using 01-03 files but with 27-02 kernel I now have working calls and 3g connection works great too! :p
[Touch Cruise Android Development] kulen:
You have one very grateful Polaris owner here.

we do not need to have daily changes, but at least from time to time (weekly? - or how ever you have time) to catch up Kaiser progress.

And maybe some other devs could help. Maybe rogro didn't leave us. Maybe he will come back to finish this project in which he gave so much.

So Rogro if you read this I'm very grateful to you for all you did and hope you'll continue making me and others happy by coming back from time to time.

And big thank you to all developers and helpers and especially Bally for all you did and you do.
[Touch Cruise Android Development] bally3:
Thanks kulen, its nice to be appreciated and I'm sure devs wlll appreciate it too.

Someone on the kaiser thread recommended chomp sms , which comes an on screen keyboard and works great too.

So with Chomp SMS and STEEL browser along with the q&d keyboard for all else, we can just about make do with the lack of osk for the time being - great! :)

On the flip side my combination of 27-02 kernel and 01-03 files worked only until i rebooted again after which gprs wouldnt connect at all. I'm going to leave the system files for the time being as its too tiring to load everything again and again and try different versions of the kernel to see whether I can improve the connection - will report back if i have any success.

I dont know what to do with the 1.5 sdk - played around with it last night but I cant get past the plugin error. I've downloaded the windows version today so I'll have a try on that later. Would be nice if someone could tell us how we can make it work with our devices, i imagine its not just a case of creating a system image and thats it - though at this moment I havent even managed to that yet :rolleyes:
[Touch Cruise Android Development] bally3:
Was checking the thread for the posted kernels from Rogro and noticed earlier posts where the osk diff files were posted. Would it be possible to include these in the kernel?
[Touch Cruise Android Development] dysolve:
is anybody keeping the polaris wiki up to date? I was was sure some one said they would keep it up to date with the latest "work" files. I noticed bally was talking about "27-02 kernel and 01-03 files" are these from the kaiser thread? because I just checked the wiki and the last update was last month
[Touch Cruise Android Development] excogitation:
The wiki is up to date - all-in-one package points to the 27-02 files on dzo's site.

On kernel side there hasn't been progress - I think I can get bt up and leds once cpld is working (which it isn't atm - I made some first attempts with biktor - but as I said: I don't really know what I'm doing) and there's also no developer osk atm.

Since there's no osk included in the 1.1 files - I didn't feel like adding it to the wiki - though it's a great improvement otherwise (screen scaling - if you like it - and google services work).

Feel free to edit away if you feel different ... you know ... it's a wiki.
[Touch Cruise Android Development] bally3:
And a good job you've done with it too exco, sometimes forget to mention your name with the credits but thanks for the wiki man :)

I'm getting a wierd consistent error now, with the 01-03 files, every time I reboot it hangs on the Android logo. i have to copy the zimage over again to the root overwriting the one thats there to make it work.. strange but I think it might be app related (or number of!) I might trim off some of the apps I dont use to see if it helps but on a positive note, two whole days of Android use and I have working 3g connection and perfect calls - as long as I dont reboot - happy times :D

One other thing I noticed - and maybe this is already known - is that charging only registers if started in WinMo.
[Touch Cruise Android Development] bally3:
Tried new kernel posted by dzo here havent noticed anything different but it does seem to have resolved my "freeze on Android logo after reboot" issue.

Since calls are working fine for me, as are sms I've started using Android almost full-time (apart from when wifi is needed). Its a drain on the battery but its worth noting that if you leave 3G on all the time even in Winmo it will reduce the battery time too so its worth switching off when not required. Also make sure wifi is disabled in WinMo before booting Androd as it will keep on attempting to switch on wifi and cause heat/battery issues.
[Touch Cruise Android Development] imfloflo:
@bally3 the cupcake keyboard is back on this version ? or must use the Q&D Keyboard ?
[Touch Cruise Android Development] biktor_gj:
Could anyone tell me where to get those diffs with the code for the osk? I'm trying to port back some parts of the osk using the vogue-ts driver, but it's a pretty big mess, and some diffs will come handy :)

@excogitation: Sorry, not been able to do anything else from what we left the other day, but I expect to have some free time tomorrow to keep on with this. BTW I think the cpld is working fine, what is not is part of the keypad driver because I think I messed something else while porting back from the kaiser :)

If I get some time I'll try to reach you through im and see if we can get a good build :)

Regards! Biktor
[Touch Cruise Android Development] bally3:
I think these are it.

Full keyboard

Full screen keyboard 2

If you go back to the thread listings and click on the paperclip next to the thread name, you'll be able to see every attachment posted on this thread.

Hope you find what you need, an on-screen keyboard would be "perfection" in chandler-speak ;)
[Touch Cruise Android Development] sjoerdarntzen:
usefull?

On the official HTC support page I found this android image:

http://www.htc.com/www/support/android/adp.html#s3

Maybe this can be of any use in the development of android for polaris??
[Touch Cruise Android Development] bally3:
Thanks for the find sjoerdarntzen :)

Maybe useful to one of the devs. I am surprised that the system.img is a lot bigger, weighing in at 54Mb compared to our 32mb.
[Touch Cruise Android Development] Braynid:
The link http://vstrien.csoft.net/Polaris-build/polaris-build.tar.bz2 appears to be broken. Where from can I get the Android archive?

Thanks
[Touch Cruise Android Development] imfloflo:
http://it029000.massey.ac.nz/vogue/ download the lastest package and change the default.txt values
[Touch Cruise Android Development] bally3:
Been running android as my main o/s for over a week now and 01-03 files (updated to 09-03 kernel), apart from the battery wearing down fast with gprs turned on, its working great.

I would recommend this setup to anyone having issues to try this and see how you go.

xmoo has shown the g2 (htc magic) on the Dream forum and I believe they are trying to dump the rom so that might help.

biktor, how did you get on with the osk? did those diff files help at all?
[Touch Cruise Android Development] Braynid:
Thanks for the link.

I've tried to boot harret from the root of the memory card but it freezes on "Booting Linux...". Besides User/Pass what should I modify in default.exe?

On the other hand I'm using Polaris so what template should I use, Vogue or Kaiser ?

Thanks
[Touch Cruise Android Development] Windows X:
I just don't get it. Polaris has same CPU spec and 3D support but why Dream? Because of QWERTY keyboard? 320x480 screen? Polaris is the cheapest model that can run Android and its performance isn't far from Dream.....
[Touch Cruise Android Development] taspankya:
i know this is for polaris, and i am on a titan, but...

im having the same issue my friend, i have tried several different builds. all with the same result.

values are different but overall issue is the same.... prompts are all talking about the sd.

I have a Kingston 2GB micro sd, doesnt specify that it is sdhc, so i am assuming its not.

i am getting my builds from http://magister.ipsys.net/projects/android-for-titan/

and http://cs-alb-pc3.massey.ac.nz/vogue/ (among some other sources at ppcgeeks)

sd is formatted fat32 1024allocation

is this an SD issue or setting or something else?

any help would be appreciated...
[Touch Cruise Android Development] biktor_gj:
Hi all, I have updated the git with some changes to the polaris, I thought I'd let you know:

* Start at cpld code: The code is ported from the kaiser, and it seems to be working, but maybe something is a bit screwed up, as upper leds don't light up when they should on the polaris, but on nike they do (don't have a polaris to test).

* Start at wifi code: Just ported the code from the kaiser too. I guess it won't work out of the box, but if someone patches it with the correct gpios for the polaris it should do the same it does on kaiser (it may work, but with a lot of problems ;)

Anyway it's a start so you can keep developing :)

Still working on the osk, it's taking more than expected... when I have it working I'll let you know and push the code to the git

Regards!
[Touch Cruise Android Development] radem205:
Wonderfull job Biktor!! I'm glad you want to help the polaris users, without having a polaris. Thank you so much and hopefully the osk will work soon so I can use android daily!

Again, nice job!!!
[Touch Cruise Android Development] bally3:
Change the mtype to 1667 - and please ask for help in the testing and bug reporting forum in future.
[Touch Cruise Android Development] bally3:
I second the thanks from radem205, I always warm to people like you and dzo who try to help development on other devices without even owing them. I am tirelessly working to bring more devs on board as I really do think that Android is the next step for our devices. Once completed, I expect few people to want to return to winmo for any more than use TomTom or the odd app or game.
[Touch Cruise Android Development] feteti:
if there were a functional room . I would be more than happy to install it and make it my default OS.

I usually run haret during night, so I can´t the battery level, since I leave it connected to the plug, and it shows the battery status on the phone ¨charging¨ all the time.

This is a hell of project that could take our phones to the next lvl.

Bottom Line... THANKS
[Touch Cruise Android Development] kulen:
Thank you very much for helping us!
[Touch Cruise Android Development] Braynid:
I have tried to run both the last version of android found here: http://it029000.massey.ac.nz/vogue/files/?C=M;O=D and this version: http://rapidshare.com/files/192510679/01-02-09_polaris-package.zip

Whatever I do, and whatever I write in default.txt it freezes with "Loading linux" on the screen.

Do you have any ideas ?

Thanks
[Touch Cruise Android Development] bally3:
Braynid I have already answered you and also asked you to ask these type of questions in the testing and bug reporting thread. Also read the threads, your questions have all been answered there.

Please stop posting here or I'll have to ask a moderator to remove your posts - This is a development thread only. Thank you
[Touch Cruise Android Development] biktor_gj:
It's not that I can do much anyway, and most of the code is a copy+paste from the kaiser, but if I can help at least porting some base board code so you can keep developing is good enough :) In the end, we are all here to help, right? And what's the fun on having a Windows phone if you can't run linux on it? ;)

Btw, for all those who don't know a thing about C programming or kernel programming but want to help, you could also help (and a lot) if you find and fill the missing information for the cpld (http://wiki.xda-developers.com/index.php?pagename=Polaris_CPLD) and for the gpios (http://wiki.xda-developers.com/index.php?pagename=Polaris_GPIO), or find information of other devices the polaris has, for example, the camera vendors and models, datasheets etc. That's one of the most important parts. Most of that is quite easy to find. Kernel code is very important too, but without that information there's not much you can implement. And, for the code, you always have dream and sapphire kernel source to take a look and port whatever you need :)

PS: Having the cpld "working" means you should have access to the gps too. It may not work, or may not initialized if not started within windows, but on kaiser worked out of the box, maybe you are lucky too!

Regards!
[Touch Cruise Android Development] bally3:
Hi bikto, this sounds like something we can get our teeth into if we knew where to start :)

How do you find the missing information?
[Touch Cruise Android Development] excogitation:
Maybe Liquid-Silver can tell us how to find the cpld info's.
[Touch Cruise Android Development] bally3:
IS this service manual any good to us?
[Touch Cruise Android Development] Braynid:
I'm sory. I did't see your reply...

Thanks again for all the great work you guys are doing.

Cheers!
[Touch Cruise Android Development] imfloflo:
With the lastest zImage always have the split screen probleme when in put my phone in standby and then i wake up it.
[Touch Cruise Android Development] biktor_gj:
well I don't have a magic formula, and, as excogitation said, LiquidSilver knows better than me how to take part of the information, but, some of the options would be:

For finding vendors and models for specific stuff, you can open the device, take good photos of what's inside, and copy the serial numbers on some of the parts. For example, on the camera you should find the vendor and a model number or something like that, add google to the mix and you should find some info about it (who knows, maybe it's the same camera as the vogue and you have part of the work done already :)

For the gpios, I used haret console, and watch gpios command, handhelds.org has a nice tutorial for it...
[Touch Cruise Android Development] radem205:
I also have this problem. I've tried several builds and several default.txt settings but no luck. In the vogue thread Iread that some other people have this problem too when usingg a non-native resolution. Although it's very annoying!!!
[Touch Cruise Android Development] excogitation:
1.1 or cupcake (or both)?

I think dzo mentioned earlier in this thread how to get the needed info to fix that.

cpld is working btw thx to biktor_gj - haven't achieved much with it though (apart from finding which led correlates to which gpio).