yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] bally3:
Since its quiet, I wanted to put some thoughts down to virtual paper, as I often do..

Theres been a lot of talk of project management recently and as DZO agreed, there is no real need for project management for the kernel development. As DZO said, the userspace (Android system.img) is the one that ay benefit from some management, but as this is generic across devices, it could be managed by x-devs from one cross-device forum.

I'll get to the userspace later, but for the kernel development, it seems to me that besides the developers involved in the commits, there are many developers who pledged their interest in developing who seem to have been largely silent whist this development has picked up its pace recently. Certainly its true to say that without ;my good friend Rogro here in the Polaris forum, development for the Polaris would have, well it wouldnt be happening lets be fair!

i've been wondering why theres been a lack of involvement from our other volunteers and something DZO said in his post about how he and his ifellow developers develop the kernel and how he advised anyone else who wanted to help - using the commits and checking what needs fixing - got me thinking. Theres a few possibilities why this is:

It could be that with the development moving so fast, the devs who volunteered decided to just sit and see how it went, letting the other devs get on with it. It could be that some of these devs dont know what needs to be done or how to get started (yes I know theres lots of instructions flying around). it could also be that the devs who wanted to get involved feel that they're not really required as the development seems to be doing fine without them (not true).

Whatever the reason, i think some thought needs to be given to how we can better cater for the devs who wanted to come on board and encourage them to get involved so we can speed up the development significantly by ironing out the kernel issues that we currently need to sort out before we can be comfortale to start using Android as an every-day alternative to WinMo.
[Touch Cruise Android Development] bally3:
I've already mentioned the seperation of kernel and userspace and that it without question agreed across the board I believe. To get the kernel issues more devolved, I suggest then that we start listing what isnt working, what task is a priority and ASK devers to take ownership of each issue, using the commits as DZO mentioned in the Kaiser forum:

I'm happy as I mentioned before to list all the issues that need working on if somone can help me compile a definitive list and post it to the first page and we can start asking devs or, any devs who volunteers their skills to the issues that are required to be fixed.
[Touch Cruise Android Development] bally3:
Secondly, I dont know about anyone else, but the talk of gits, trees, branches, repos and commits is starting to confuse me a little. I'm a Windows user who currently installed linux onto his laptop to learn more about linux and get involved with this project. I would appreciate it if someone knowledgeable would explain how this all works, i suspect that a step by step guide may actually help some of our devs get kick started if they are a bit unsure of some aspects of the working of these technologies.

I know it would definitely make it easier for our readers to follow whats being talked about in this thread. Please - no hasty links pointing to some external website please. If possible I'd like the explanation or guide to be put into the post so that we can put some reference to it and not send our users off-site that often happens.
[Touch Cruise Android Development] rogro82:
Checking my backups as we speak using an ubuntu live image ( never thought i would actually need linux besides development :D starting to fall in love... )

Bally3:

I cant agree more.... heck thats why i put all my sources in the git or online / make manuals etc... I love doing it all on my own ( control freak when it comes to this kind of stuff ) but its not just that my knowledge isnt ever lasting but also I dont always have the time to do the things I would love to do on this matter ( gf already hates android :D )...

If anyone ( experienced in developing ) needs some help from me to guide them how to start working just let me know... I think i setup a clean path for the polaris support in the kernel and I hope people will also keep it clean and logical.

Need help starting?

PM me or leave your message in this thread and I will try to answer them as good as I can...

Edit:

Now im gonna grab another bottle of wine... ;)

I wanna say thanks for all the kind donations ( wont call people by name as i dont know if they mind, but they will know ) and of course to all people putting effort and support in this whole android thing.
[Touch Cruise Android Development] excogitation:
Here's your listing - if something is missing - just add it.

That certainly depends on who you ask - but it's up to the person being able to work on it to choose what's most important to them.

Git is a free distributed revision control, or software source code management project with an emphasis on being fast.

If you don't know about branches, trees, commits and repos in regards to Git - I doubt you can be of kernel development assistance (might be wrong about that).

In short - the git repository if you want to get involved is git.linuxtogo.org (ltg)

and "our" branch is htc-vogue (that will change someday).

For developing on your machine you'd checkout that branch (with tracking to be able to update it easy whenever changes have been made/committed).

Once you developed something you wanted to share you'd commit it either by sending a diff to someone with write permission to ltg or ask to get write permission yourself.

Have a look here.

Just put it on the wiki - this way it can be adapted easily (because not just the post author can change it)
[Touch Cruise Android Development] freelucos:
Hi and thank you for the work on Android.

But I have some problems:

1 - Unable to have the SFR network and internet use, etc..

2 - The camera does not work on my Cruise with the last elements download.

In addition I would like to know how to return to Windows without restarting the mobile phone.

Thank you.:D

----------------------------------------- Merci google.

Salut et merci pour le travail accompli sur Android.

Mais j'ai quelques problemes:

1- Impossible d'avoir le reseau SFR et de profiter internet, etc.

2- L'appareil photo ne fonctionne pas sur mon Cruise avec les derniers éléments télécharger.

De plus je voudrais savoir comment faire pour revenir a windows mobile sans redemarrer le téléphone.

Merci.:D
[Touch Cruise Android Development] dubbeld00:
Salut,

Vous pouvez poser des questions / bugs sur Android ici. Vous y trouverez des informations sur les parametres que vous avez a changer dans l'Internet afin d'obtenir de travailler.

A propos de votre deuxième question: Non, il n'est pas possible de retour a WinMo sans redemarrer votre telephone.
[Touch Cruise Android Development] bally3:
Nice one exco, fast as usual :)

I'm thinking about redesigning the way we dish out files here, noticed in some threads they use post numbers and singular post and change/update files in the same post which I think is a good idea and maybe something we can set up.

.

That may be true, but the goal is to take out any obstacles that might be stopping a dev from having a go, besides, if rogro can turn his impressive dev skills to linux I'm sure there are others who are just as capable of doing it. The main this is to get those type of people on board so that poor rogro doesnt end up being a one man show for the whole journey.

I'm almost tempted to look for the idiots guide for the step by step - maybe just me but if soneones's got the time and inclination, would they take the steps in the link posted by exco and do screen grabs etc and post up a real beginners startup guide on the Wiki please - this is to the many volunteers who've asked me how they could help as they cant develop - heres your chance. You might be confused by my approach here - but bear with me, theres method to my madness and it will become apparent soon.
[Touch Cruise Android Development] excogitation:
I've thought about that too (and I was a bit lazy repackaging a complete set) -

and I think we should just link the individual files

(with size/md5 hash and possibly changelog (but I don't know about the latest/different changes to system/initrd/data))

on the wiki - so that it's not up to one person to keep it updated.

That would be really good - without rogro there wouldn't be any progress - thanks again!

I could setup a working Ubuntu VirtualPC image (or the like) or even screengrabs (which I think is totally useless since there's a step by step guide to build the kernel here) if there's real demand for it.

Also here's an explanation on how to edit initrd

and howto create/edit system.img here

and f00bar's changes to userspace here
[Touch Cruise Android Development] bally3:
Dwaradzyne tried this for me with an Ubuntu vmware image - but it ended up being 4gb - compressed and took a week to download. Would be interested to see another solution.

I'll have a read of these and add them to the info I post up, but this is the problem from my point, theres plently of fragmented info around, but if someone who who was an inexperienced dev wanting to get involved would have to do some digging to get started. The info is all there but I think we could make it a little easier to get into - just a thought, not wanting to upset anyone's efforts. But I'm really set on getting some more devs on board - especially for our device.

Rogro has kindly offered his support to help anyone interested and i think we should find some devs to motivate to take up the golden opportunity.
[Touch Cruise Android Development] bally3:
Ok quick question, i've installed a file manager in my Android installation by copying the file into the AndroidApps directoy, but if I try to downoad any apk's from the net from the browser it tells me that there is no space. i have a 4gb card with 2gb free but it looks like the files are trying to install into ram? is this correct? and if this is the case any chance we can change where programs get installed please?
[Touch Cruise Android Development] excogitation:
That's why I'm trying to get people to get involved in wikiing :-)
[Touch Cruise Android Development] vEnEr95:
Hi

Please or the safeguards of the adjustments of android I am need all to remove to set out again on a clean installation but I do not see it or it hides

thank you
[Touch Cruise Android Development] excogitation:
Posting it in multiple threads doesn't make it any less confusing.

What are you trying to say/ask?

Thank You!
[Touch Cruise Android Development] vEnEr95:
afflicted my translator badly translated

I wanted right knowledge in which file or which file or android back up its settings and the parameters of user?

to leave on the clean

in french :

desolé mon traducteur a mal traduit

je voulais juste savoir dans quel dossier ou quel fichier ou android sauvegarde ses reglages et les parametres d'utilisateur ?

pour partir sur du propre
[Touch Cruise Android Development] excogitation:
Dans data.img.
[Touch Cruise Android Development] imfloflo:
For information : New version on DZO site
[Touch Cruise Android Development] psicobra@hotmail.com:
wow

wow this is the second time i have tried android and the first time it was nowhere near as advanced looking as this it is amazing i can't wait until it is fully functional but until then (and i have searched the forum but to no avail) when i start android it doesn't pick up my mobile network i guess it is a setting some where i am on o2 UK pay monthly can some one tell me what i need to do and secondly when i click the camera app i get an error saying please insert an sd card before using the camera and ideas thanks

psicobra
[Touch Cruise Android Development] pt-1:
Could you post a link for people that only reading the latest post's ?
[Touch Cruise Android Development] dubbeld00:
1. Are you running the latest files... Can you call/SMS/internet... What did you tried to get it working (removed PIN etc?).

2. Camera isn't working on android yet.

- Please post these answers in the other thread, this is the development thread...

Lazy :D, but here you are:

http://it029000.massey.ac.nz/vogue/android-kaiser-09-02-09.zip
[Touch Cruise Android Development] radem205:
I thought it was already known, but with the latest files from dzo and the zimage from Rogro the tap register is sometimes somewhere else then where I tap (often in the lower left corner). Also in the dailer I have to tap twice (or more times) on number 4 and 7.
[Touch Cruise Android Development] Michel82:
Yes that is a known issue, it seems the ts always get 0,0 as a first input and then jumps to the touched area.
[Touch Cruise Android Development] croisez:
Trying to understand Android devpt on xda-developers.com

Hello,

I don't understand very well,

during the development of the linux kernel for Polaris, must we also adapt the Android layer, or will it fit automagically when our kernel will be ready?

In other words, is Android only managed by the Google community, meaning that once you got the kernel you got a GPhone-like device?

( a little bit obscure question is'nt it, huh? :p )
[Touch Cruise Android Development] dubbeld00:
"Automagic" nice word :D,

Linux (drivers etc) <--- This is what we develop

V^

Android (Framework) <--- This is what google develops (and we still have to adjust a bit, since not all the info is provided by Linux)

V^

Applications <--- This is what some nerd in a little 2 by 2 dark room creates, and publishes...

Of course the last line was a joke, not really to laugh about, but I found it hilarious.

So most of Android will directly work on our mobile if you only have a working zImage... But not all ;)
[Touch Cruise Android Development] croisez:
Merci so much! :D

Now I begin to understood why there is no actually much discussion about Android itself.

The zimage is the key.

And a last question then: what is the roadmap for the zimage development of the Polaris flavour? Is there a (wiki/forum) page describing the todo and the already done?

Louis
[Touch Cruise Android Development] imfloflo:
Yes there is a wiki and a todo list here http://wiki.xda-developers.com/index.php?pagename=Polaris_Linux

but the zImage will become generic so we can use DZO website zimage and just set the mtype in the futur
[Touch Cruise Android Development] rogro82:
The zImage as a base will become generic. This only means that the 3 devices are compiled in ( So its basically one kernel that supports the 3 devices depending on there machine type, in the past this wasnt possible because of the way things were set up. )... The kaiser and polaris are almost on the same base so a lot of the actual code can be shared, besides that there are the device specific drivers ( like touchscreen, keypad etc ) which should be worked out for each device.

I finally have my development environment up and running again so finally i can do some stuff again :)
[Touch Cruise Android Development] imfloflo:
Ok so we can use both zImage yours and DZO's.

If i download the lastest kaiser package from DZO website it should be work?

Just changing the default.txt or default-kaiser.txt
[Touch Cruise Android Development] rogro82:
It should work as soon as my changes are commited to the git... i send them to dcordes a week ago but hasnt heared from him yet. Guess ill also send them to Martin, so he can add them.

That way it shouldnt matter which one you choose because we are all working on the same.

So the kernel has the support for all the devices and you can indeed just specify the right one using the right mtype in your default.txt
[Touch Cruise Android Development] imfloflo:
Why you can't submit your files directly to the git? why they don't create an account for you?

BTW what are the next things todo for polaris ?

i see DZO release a new files on the vogue thread and a user suggest to build system.img every night.

http://xdaforums.com/showpost.php?p=3296538&postcount=2900
[Touch Cruise Android Development] rogro82:
I dont really need to have git access... I dont care as long as they are commited, i like the idea that someone with a kaiser can check that changes dont break anything in the kernel support for the kaiser ( I only have a Polaris so i can basically only check if its working for us and not for any other devices ).

I just send my diff file to Martin so he can check it... hopefully he will add it soon, so that everything should be right again.

Edit:

Martin replied and he will commit it tomorrow.
[Touch Cruise Android Development] excogitation:
With dzo's latest files and rogro's latest kernel

(don't know about the status with other combinations) data is working without a connection in Win

and without setting up my custom APN (I still had to run Togga - and no gprs icon showed).

After setting up my APN manually (MCC and MNC get detected automatically) it still works to connect

through Togga and the gprs icon shows (right from the start).

Also my Android is now German - Gag!

The camera app doesn't crash anymore and tells you to press the capture button

(do we have one mapped? - is it working?)
[Touch Cruise Android Development] imfloflo:
I see we can change language of android in settings but not in french :s is it really working ?

Vogue package and kaiser package are the same just different zImage ?

I try to push the on/of button longer to power off my device, i see the prompte to power off but immediatly it goes to standby mode, i must touch the screen at the good timing to block the screen and push the power off popup.

with same configuration than your excogitation can't make a call :s

lastest DZO package and lastest rogro zimage

Here is my default.txt

and this in APN under android
[Touch Cruise Android Development] KundK:
Seem well done. Unfortunately data connection still doesn't work here in hungary. Not even connecting first in winmo.

Also I can't get used to it that unable to hung-up calls with the red button.
[Touch Cruise Android Development] bally3:
I've just run the 09-02-08 files - I can get a reliable data connection with Togga with this version - but sometimes need to reboot to enable the connection but once connected it stays connected.

I still have heat issues - and this is a newer phone to the last one I reported on - I was on a 15 min call on Android - phone rang while I was playing - and the screen heated up so much - event after the screen went black - I had to move the phone away from my face! it also cut off twice during the call and I was sat in my house, where the signal is quite strong for three network. Call quality is excellent though through the ear piece.

I've tracked the heat issues down to the gprs connection as it always seems to be when togga is trying to connect and whilst connected.
[Touch Cruise Android Development] excogitation:
rogor's changes are now in git (don't know if there's a kernel around with those & dzo's headset changes - if not - I will build one later).
[Touch Cruise Android Development] bally3:
When you say later... do you erm.. mean soon? :rolleyes:
[Touch Cruise Android Development] excogitation:
You pushed me to do it sooner :-)

but it doesn't boot on Polaris without changes (yet?) - and I don't know what needs fixing.
[Touch Cruise Android Development] chab7:
yes, i think the apn settings are not right.

i am tryin to solve it too, but anything i can get - data icon up, arrows blinking up and down on it, but internet isnt working :(

we must find the right apn settings for hungarian services.
[Touch Cruise Android Development] excogitation:
Blinking arrows mean that data is transferred (up/down) - so it seems internet is working ?!

Do you have ppp.username=\"\" ppp.password=\"\" set in default.txt? (that's the only thing regarding data you need in there).

Also in Android APN standardnet.vodafone.hu MCC 216 MNC 70 (MCC and MNC should get detected when setting up a new APN).
[Touch Cruise Android Development] radem205:
With the latest files from dzo (you could find it in the kaiser thread) the battery-level isn't working on the polaris yet :(. I think this is caused by a different gpio number, isn't it?
[Touch Cruise Android Development] rogro82:
Can anyone confirm it boots using a new zImage in the Kaiser thread ( Radem205 i guess you did this ).

The changes made should bring polaris support in the new zImages :) Havent had time to try it yet.

Radem205:

Ill add the battery driver to the board ( this needs to be added manually per device as its a device specific driver ) and try to see if it works for us.
[Touch Cruise Android Development] radem205:
with the new files, including the zimage, it just boots fine.
[Touch Cruise Android Development] bpmorris:
I can also confirm my polaris boots fine with the new set of files. Data has stopped working again but probably something I am doing. The other noteworthy item is the boot splash appears centered. Its just a little thing but it still looks good. I am still seeing battery meter set at %100 by the way. Keep up the cracking pace guys, we will have this phone fully functional in no time!

Cheers

Ben
[Touch Cruise Android Development] excogitation:
No, not a gpio ;-)

After dzo's latest commits the kernel works on Polaris.

Anybody feeling the need to join developing - here's a guide how to build a working kernel for Polaris.

If not - I'm sure we can find out how to adapt it to work on Polaris.

Also could you add the (wired) headset from vogue?

This kernel should be the same then as the one in the Kaiser thread:
[Touch Cruise Android Development] dubbeld00:
Haven't test my zImage, but it should include the kaiser-battery driver :)

Edit:

... forgot to click "Upload"

Edit2:

Well... it is booting... and working :D, only my battery is empty according to the zImage... while it has 5% left... dunno if it's just my device :) since it is almost empty

Edit3:

No battery reading... please use the other zImage... looks like the current battery driver isn't working on our device.
[Touch Cruise Android Development] radem205:
After booting (in Android) the phone just restart immediately.
[Touch Cruise Android Development] dubbeld00:
That's a pitty... have to change the driver then... (thought it was my device, since it was already low on power... maybe rogro has a great idea to get it running.
[Touch Cruise Android Development] rogro82:
If it reads 0 battery it will indeed reboot... thats why i set it to a fixed value before and later on just removed the vogue-battery driver as it wasnt going to work the same as the vogue one and a new i2c driver had to be created...

Im at work at the moment so I dont really have any time to look at it at the moment... Will look at it as soon as i get back home.

Edit:

Left my polaris at home so i cant test anything... dubbeld00 did you only add the vogue_battery_device in the board or did you also specify the i2c driver?
[Touch Cruise Android Development] dubbeld00:
Did also specify the i2c driver ;) (i'm not that stupid) but got it working now :D

machine_is_htckaiser() in battery.c, replaced it with a 1... (so if(1) { //dirty) because is_msm7200() doesn't work there...

I'm not quite into the code yet... also got the TS working normally (not going to 0,0 point anymore, well ... less failures)

BTW it doesn't detect if you are charging your device! (since kaiser-keypad is detecting this, and we haven't got that file and I only wanted to test if the battery meter was working (which is working :D))

BTW2: or my SD-card is formatted, OR SD isn't found anymore... haven't changed something to it... might be also in the original zImage?