yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] Michel82:
Just installed the complete latest package from DZO (including system.img and a new data)

My internet connection is working again, BUT some other elements the previous version had are missing;

- Adjusted size boot logo.

- Some translations (other package had much more languages and the Dutch translations, which i use, does not have as much translated as the previous)

Looks like this package contains an older system.img. Why would this be?
[Touch Cruise Android Development] radem205:
Holding the power on / off button works very well with the latest files from dzo ! And the touchscreen respons better!
[Touch Cruise Android Development] rogro82:
It should work ok now as I changed the keypad driver in the latest commit.. The touchscreen response could be because i removed the IRQ triggering on the touchscreen press to reset the inactivity timer ( this isnt needed anymore because its now handled in userland )
[Touch Cruise Android Development] radem205:
Rogro: Is it difficult for you to change the code from the kaiser to let the charger work?
[Touch Cruise Android Development] rogro82:
Havent looked into it yet... Will do when i have some time left.
[Touch Cruise Android Development] imfloflo:
What we need to have the battery charging? gpio code? cause its very disappointing to must go to winmo to charge :s

But i can test pointui :).
[Touch Cruise Android Development] excogitation:
productideas

Don't think it's going to help - but vote for it anyways ;-)

Android Community porting
[Touch Cruise Android Development] TomAngel:
Hi,

DS.store is a file generated by Mac OSX like the thumb.db under Windows XP or else. You can delete it, without an issue...
[Touch Cruise Android Development] dzo:
Sorry about that, I was testing and forgot to take it out. I've changed it back and pushed the change to git.

Looks like polaris is going well, keep up the good work.

Martin
[Touch Cruise Android Development] rogro82:
No problem :) You dont need to apologize to me...

Already thought you were testing stuff.. had it fixed locally so want worrying.

I guess well need to change how the shared stuff is working... Ill think things through so we wont have to make separate calls for each machtype.

Things can get confusing with adding support for all three devices... Maybe its better to share a same code base for all devices (vogue/kaiser/polaris) which incorporate the handling of these functions, which are now mostly setup in the vogue_hw.
[Touch Cruise Android Development] bally3:
I've run the current Android files through their paces for the first time today to see how it would fair on a daily use now that call, gprs and battery are working.

Files are from dzo's latest build and rogro's last kernel upload.

The battery lasted from a full charge for about nine hours, with a few calls made and about half an hour of data use (browsing the web mainly). This isnt brilliant, I would expect to get a full day out of it at least with winmo also it drains just as fast as someone mentioned earlier when its in sleep mode (its set to "1" in default.txt) looks like we still have a power consumption/collapse issue?

Calls work both ways for me, both made and recieved so I seem to be in a better situation than some. GPRS works from connecting to Togga, "G" icon only appears if settings are entered in Settings, GPRS is still unstable - whilst it connects every time, it doesnt allow you access to the internet. Resolved this by disconnecting Togga and reconnecting a few times.

The good news is that the device stayed relatively cool in use during the day with little or no warming even when in call.

Edit - Tried the new kernel build from asj's auto-build site just now but it crashed the phone so back to rogro's build.
[Touch Cruise Android Development] dzo:
I guess the official way to do this is to have separate drivers added by the board files with different resources if the hardware is slightly different. The problem is that things like setled are called by other drivers.

Perhaps the way to go is to leave it as it is and rename it to htc_msm7x00-hw and try not to put anything else in there.

btw, does power collapse work for you, do you get a red led when the phone is asleep and "msm_pm_collapse() returned 1" in the log (may need debugging enabled in pm.c)
[Touch Cruise Android Development] rogro82:
Do we have to manually use the setled in other drivers? We can also set it up to be controlled via /sys/class/leds... I can add them if you like this weekend ( although the G1 only supports blue, red en green if im correct ) ..

Maybe we should indeed create seperate userland drivers and just use the htc_msm7x00-hw for shared functions ( eg. the panel / backlight code ).

This way each device can implement its own userland functionality, so that one devices handles the keyboard backlight while another without an actual keyboard can leave it out.

It will also make it easier to copy stuff from each other without having to change all calls because functions not being static..
[Touch Cruise Android Development] imfloflo:
No red LEd for us on polaris, and need to have the battery charge implements.

edit: the red LED exist sure, but we can't see it on android
[Touch Cruise Android Development] rogro82:
I thought it actually had a red led... or we could just use the red led as the actual orange led.. setting it up from userland will save a lot of work setting the leds right and its basically the way it should be setup i guess...

I can take a look at the battery charge this weekend... dont have too much time right now ( too busy with some large projects at work ). If someone else wants to take a look at it, maybe they can do it before the weekend.
[Touch Cruise Android Development] vEnEr95:
thank you

@imfloflo

having evil with the English language I made to a French tuto thus all the people who speak French are it welcome

and large a mercy has all the devellopers of this project like bally3, rogro82, dzo which are kings and all the others

in french

ayant du mal avec la langue anglaise j' ai fait un tuto en francais donc toutes les personnes qui parlent francais sont le bienvenue

et un grand merci a tous les devellopers de ce projet comme bally3,rogro82,dzo qui sont des rois et tous les autres

http://www.actualitemobile.com/forum/index.php/topic,8523.0.html
[Touch Cruise Android Development] dzo:
The charging code just looks at the current from the battery, if it's negative it says it's charging. On kaiser it seems to charge automatically, on vogue I needed to set a gpio to charge. I guess polaris is the same as vogue, you will have to trace a usb plug/unplus to see which gpios/egpios are changed.
[Touch Cruise Android Development] rogro82:
Already traced them... i thought it was either 5,1 or 5,4... ill try it later on, its strange that although the polaris and kaiser are that much alike, but some general stuff still is different.
[Touch Cruise Android Development] excogitation:
There's only one gpio change when connecting a USB cable (bank 1 pin 5).

edit - just checked AC again - and that changes

plug 1-5=1, 1-12=1, 0-1=0

unplug 1-5=0, 1-12=0, 0-1=1
[Touch Cruise Android Development] rogro82:
Thanks... switched bank and bit then :) memory failures hey
[Touch Cruise Android Development] redhoerbi:
How does the recognition of the gpio work? I've tried it with haret and the watch command, but i resolve just a lot of hex combinations like this:

I just try to understand these things, that i can help someday...
[Touch Cruise Android Development] excogitation:
Don't really know - but if you tell me what unplugging AC looks like - I'm sure we can figure it out.

Using haretconsole unplugging AC (after silencing the spamming ones <- "ibit gpios #"):

HaRET Documentation
[Touch Cruise Android Development] dzo:
Also look at the cpld, on kaiser it sets bit 7 of cpld 3 (at physical addr 0x98000006). kaiser also does a proc_comm to set dplus to A9 (whatever that means).

I put some code in battery.c (in htc_get_batt_info), it's commented out and it could be dangerous but it's what kaiser does.
[Touch Cruise Android Development] paipo:
Hello all,

this is my first post, just to report how things are working for me.

With DZO build from 11/02, my Polaris boots, I can make and receive calls with sound, I have internet (running Toga first).

I changed default-kaiser.txt to set the correct MTYPE for Polaris, set initrd "initrd.gz" and the right ppp for my mobile operator (TMN - Portugal).

If anyone wants to know, it's:

ppp.apn=internet ppp.username=guest ppp.password=guest

If I use rogro's latest kernel, my Polaris doesn't boot, it freezes on Andoid logo.

Any idea?

Edit:

Forgot to mention: great work guys!!!
[Touch Cruise Android Development] redhoerbi:
I took a look on the haret documentation before - but i still dont understand why i see just hex-addresses although in the documentation are integers

What i found out:

Battery not loading:

mem GPIOS(6) 92a00c20=07e0f0be (00000000)

mem GPIOS(6) 92a00c20=07e0f8be (00000000)

Battery loading:

mem GPIOS(6) 92a00c20=07e0f09e (00000000)

mem GPIOS(6) 92a00c20=07e0f89e (00000000)

I tried also ibit, i didnt work for me (i tried "ibit gpios 6")

I found out this values using the setting "settigs->power management->battery->"dont charge akku when connected with pc". (i translated the names from my german winmo, maybe the names are not correct). I hope i did it right and i could help.
[Touch Cruise Android Development] a.s.j:
@Bally3 & excogitation,

Hey guys, does the kernel work on polaris now or not? AFAIK it seems there is only some settings needed to be changed in defalt.txt, is that right?
[Touch Cruise Android Development] dwaradzyn:
Darn, I was working with wrong sources. I checked out the ones you mentioned - 2.6.25 from git.android.com with 3 patches from szsoftware. I will try to get onscreen keyboard working again.
[Touch Cruise Android Development] dubbeld00:
Nice progress :) I hope I can find some spair time to do something myself, but I haven't seen a working zImage in a while, so this really is a good start :)

This looks like the next thing to do :) (really don't know what he is talking about, hope someone does... and can clear things up :))
[Touch Cruise Android Development] bally3:
The logs from the htc-linux irc room show a lot of activity. Looks like we have a "booting" 1.0 android with some errors is that correct?

Also can someone post the entire lot of files being used to do this please?

Theres a whole load of different files posted on the other thread and it would be good if we could all see the same thing - at least the eager testers could report back what their experiences are, you never know what breakthrough you may get from having it run on different setups.

I also want to update the first post with these files so that we can point everyone who comes on here wanting to get involved to the most current file set.
[Touch Cruise Android Development] belabartok:
Congratulations to the team that it`s developing it, and good luck!.I`m really excited, I`m quite of a linuz fan so you can get an idea
[Touch Cruise Android Development] dubbeld00:
great idea :) Btw, isn't it an idea to donate DZO a Polaris (if he is willing to port linux to it), think there are cheap Polaris phones on eBay... Is a quick solution for our problem, he has all the knowledge, and was willing to do the same for the Kaiser.
[Touch Cruise Android Development] bally3:
Last night, rolk on irc helped me get linux "running" on my device at root level and a prompt using Angstrom. (Thanks Rolk! :) )

I enquired how to get the GUI running and was told that, this could be done by typing startX. This didnt work and I was told that this could be found in the initrd file but Angstrom doesnt have startX as far as its known. I left it at that deciding to have another go today.

This morning I read the logs again, and a user called glyph who was trying to do the same as myself - get the system up and running to see whats been done and what needs doing, asked a simple question after having followed the instructions and got to the prompt as myself - "How do I get android working on the device?" and got a confusing response.

I assume, like myself that Glyph is still confused as to what do next.

And here lies the problem. Its an endemic problem with linux and its multitude of incarnations - linux power users vs the the "NOOB".

What THE END-USER on here wants to do is to get an Android version of Linux working on their phones.

What the power users want to do is to create a whole new Linux version for these devices.

Theres nothing wrong with either endeavours and I understand the wish of linux users to get away from Googles close-sourcing and its control issues and secret patches but we seem to be working on multiple projects at the same time.

I personally would like to see DZO's vogue version working on my Polaris - and I think the majority of the users here would like to see the same.

I dont understand why we are using Angstrom over the other initrd if it does not contain the android GUI, If I understand correctly, DZO was using 1.0 android and the initrd file from what I see in the download from his site. I would like to know what needs to be done to his setup to make it work with ours.

I hope someone can explain who's working on what project and maybe we should separate the two endeavours if that is indeed what is happening.

Whilst creating a linux from scratch for these devices is a noble endeavour, the sheer scale of this task is something which I think should be left for a dedicated thread with its own project name.
[Touch Cruise Android Development] imfloflo:
That what i was saying we should create new topic, there is the kernel first, and after that we can run many distrib on polaris. the kernel is indepedant from distrib. That's an important point.

Angstrom is just a simple distrib without X but you can test gprs and different things but all in commande line :(

DZO use the 1.0 SDK files on a SD format in ext3 and he ahs a specific version of haret.

With polaris we have problem because some code to boot aren't the same as the vogue so we can't use DZO's vigue files like that.

That why DZO ask a kaiser or a Polaris to see what's cause probleme and repair that to release a version for our device.

As you said in this thread people really want to see Android running, not another distrib.That why i suggested to make 2 thread but its complicated to read multi-thread after. (we already have lot information on Kaiser +vogue+ polaris threads)
[Touch Cruise Android Development] bally3:
Cant we fix the problem with the code or is that not within the capabilities of the devs on this thread? Sending DZO a polaris doesnt seem to be much of an option to me.
[Touch Cruise Android Development] imfloflo:
I think it's require lot of skills in basic dev, maybe ASM, or like that.

I think we should wait he receive his kaiser from another member of XDA and see if we can use this.

After that if no solution found we must send him a Polaris
[Touch Cruise Android Development] belabartok:
good news here
[Touch Cruise Android Development] bally3:
I downloaded the recent version of DZO’s vogue version and renamed the default.txt file that I modified yesterday to startup.txt with rolk and copied the angstrom file into the directory and it worked exactly the same. This tells me that the only things different are these two files?
[Touch Cruise Android Development] imfloflo:
Why rename default in to startup ??
[Touch Cruise Android Development] bally3:
because there is only a startup.txt file in the vogue version with similar content in it.
[Touch Cruise Android Development] imfloflo:
Ok i need a little explaination ,plz , what is the difference between 0.8SDK of Polaris with many files and he 1.0 SDK vogues files with different archive?
[Touch Cruise Android Development] dubbeld00:
Because our kernel isn't completely working to support android we are using Angstrom... With angstrom you can debug and see what your device is doing... to see the SDCard bug, for example, play a movie (by mplayer <filename>)... you will see that it will crash after a while...

Systematic you have to see it like this:

Kernel: Linux <-- this is what we working on (zImage)

Interface: Android <-- this is already completely working (initRd)

Kernel: Linux <-- this is still what we are working on (same zImage as above)

Interface: Anstrom <-- Commandline only, but also working (initRd)

zImage (kernel) contains:

- keyboard (for now)

- sdcard driver

- video driver

Interface contains:

- well... a GUI, and stuff that can access the drivers

In short:

We can't run Android 1.0 (this needs too much memory to put all in your RAM) if we don't have a SD-Card driver which keeps running

We can run Android 0.8 (which will crash sometimes, because it is using much memory, but not too much).

So we have to do modifications onto the SD-Card driver within the zImage... that's why we are compiling those zImages... hope this post is quite clear

Imfloflo:

In the 0.8SDK it was possible to put all the files onto your RAM... You couldn't save anything and so on and so on...

The 1.0 requires external storage (because we can't put linux + android onto your ram), so that's why you will see a new filestructure...

in short: 0.8 didn't had a file structure, all was put into RAM (temporary memory)

1.0 needs more storage, so you will have to create partitions on your SDCard

General message

Someone has send DZO a Kaiser... this will probably mean that he will fix the SDCard issue for the kaiser, and since the hardware is very related to our device, it will also be a fix for our device... so we might finally see it all working... then we have to finetune the zImage
[Touch Cruise Android Development] bally3:
This is what we got to last night on IRC:

22:03 Bally3 trying to figure out where the sd card setings would be

22:05 Bally3 see the initrd is the android etc..

22:06 Bally3 in the vogue default.txt there is a line about the sd

22:09 imfloflo what it says?

22:16<= tekkdrone left/quit

22:16<= BabelO left/quit

22:18=> Bally3_ joins

22:18=> xe0n1 joins

22:20 Bally3_ # msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller

22:

22 Bally3_ # This is what I use: "msm_sdcc.msmsdcc_fmax=32000000 pm.sleep_mode=0 board-htcvogue.panel_type=1"

22:27<= kiozen left/quit

22:27 Bally3_ flo

22:27 Bally3_ have a look at this:

22:28 Bally3_ http://cs-alb-pc3.massey.ac.nz/vogue/.config

22:29 Bally3_ thin i found it

22:29 tmzt_ rolk: the sources for the on-screen keyboard where added by dzo and others, not google

22:29 imfloflo do you think its jsute this param?

22:29 Bally3_ CONFIG_MMC_EMBEDDED_SDIO is not set

22:29 Bally3_ #

22:29 Bally3_ # MMC/SD Card Drivers

22:29 Bally3_ #

22:29 Bally3_ CONFIG_MMC_BLOCK=y

22:29 Bally3_ # CONFIG_MMC_BLOCK_BOUNCE is not set

22:29 Bally3_ # CONFIG_SDIO_UART is not set

22:29 Bally3_ # CONFIG_MMC_TEST is not set

22:29 Bally3_ #

22:29 Bally3_ # MMC/SD Host Controller Drivers

22:29 Bally3_ #

22:29 Bally3_ CONFIG_MMC_MSM7X00A=y

22:29 Bally3_ #

22:29 imfloflo so its a files which need to compile zimage?

22:29 Bally3_ its in there somewhere

22:29 imfloflo the configure file

22:29 Bally3_ i think so

22:30 Bally3_ so.. edit.. compile... test?

22:31 imfloflo yes so edit set to 0000 compile test, redit set to 0001 compile test ... again :p
[Touch Cruise Android Development] bally3:
As you can see, there are some settings in the default.txt file in the vogue version relating to the sd card and also the config file used to compile the zimage.

The latter I think is the key and as was said on IRC, we will probably have to change the parameters, compile test, change etc. until we get it right.

Imfloflo, Dubbeld00 and Dwaradzyne, you guys seem to be able enough to take on this task – for the rest of us I think we should do some research on what these settings maybe. If we're really struggling, we can then ask DZO if he could shed some light on it by providing him the specs of our devices and the config files.

I may pm him again tonight and ask him if we're on the right track or where else we should look for these settings but I think we are right with the config file.
[Touch Cruise Android Development] bally3:
have a read of this for the BlueAngel, especially the command line for the sd mmc:

http://groups.google.com/group/android-internals/msg/fe8e8773c2f588a2

Kernel command line: root=/dev/mmcblk0p2 rootdelay=10

console=ttyS0,115200n8 console=tty0

I'd say this is the kind of thing we're looking for.
[Touch Cruise Android Development] craigad:
Rolk seems to be handy!

I know this is my first post, but I have been lurking in the back ground for some weeks now, watching the progress on Android both here and on IRC.

I think we are in danger of overlooking the skill and progress that rolk is making........................

just my 2 penny worth.

/Craigad
[Touch Cruise Android Development] bally3:
Not at all, rolk is doing extremely great stuff on here, but it is prudent that we should try and catch up and help as he is but one dev alone. Apart from that, there are other talents on here eager to get involved and we need to start working as a team. :)
[Touch Cruise Android Development] imfloflo:
Yes kernel works great on polaris , just need to use the default-kaiser and change the mtype to 1723 all is good after that :)
[Touch Cruise Android Development] excogitation:
I think you need to change "set RAMSIZE 0x07000000" to "set RAMSIZE 0x8000000" to make use of our full 128MB ram.

and we also don't need

"set RAMADDR 0x10000000"

"set FBDURINGBOOT 0"

if you start out with Kaiser's default.txt.

But yes, a.s.j, the Kernel works on Polaris thanks to all the work rogro82 put in on Polaris and dzo of course.
[Touch Cruise Android Development] a.s.j:
That is good to hear, cause I was asked by Bally3 to make also Polaris Kernel auto builds on my site, but there is only Kaiser one now, so if it is the same one just check site in my signature every now and then.

Tight now there is only a file list, but whole web is also ready for using other things if wanted, so I'll try to continuously build the knowledgebase etc to have full support for both users...
[Touch Cruise Android Development] bally3:
Working well and I love the Autobuild you've done mate, thanks for the effort :)

Makes checking quickly for an update a breeze, which is what we needed. I'll add the url to the first post.
[Touch Cruise Android Development] excogitation:
What we need imho is developers ;-)

If changes get pushed to git devs usually release a kernel - so I don't really understand what the autobuild is needed for - especially without changelog - but that's just me.
[Touch Cruise Android Development] bally3:
Agree with the point about the changelog, but I think for all general testers using different file sets, to be able to stick with one file set and just download new builds may ease some of the probs (more on kaiser thread admittedly - I think for us (polaris) users not having that many radios that are confirmed working on here is a hidden blessing. We dont seem to have that many users complaining of builds not working or as many issues).

Trust me I've pulled every trick in the book to get more devs on board, I might resort to putting a plea in General thread. To be honest, I didnt envisage poor rogro being the only dev working on this when I came on board on the project. Devs like Dwaradzyne, Rolk and earlier devs who did much of the work on the kernel seemed to have disappeared, as have the other devs who were involved in the old thread. I've pm'd a number of them, but no answer from any of them.

Either they have moved to newer, shinier devices or they think that dzo will fix all and they arent needed - I admit not having a clue why this is, but will keep on appealing to devs to come on board.