yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] rogro82:
Ok... just bought my self a phone for everyday use ( I was developing on the Polaris more then i was using it as a phone... Unreachable for 99% of the time :) ). So now i can use the Polaris as a development phone only.

And I can compare the two because I just bought a G1 :D
[Touch Cruise Android Development] bally3:
Oh NO rogro!

Does that mean we're not going to see much of you from now on?? :eek:
[Touch Cruise Android Development] rogro82:
No bally this means i dont have to worry about destroying my device :D

Like i said I really needed a phone for development use only, because it wasnt really working the way i used the phone the last few weeks. ( even the 3d quest was nothing compared to this ).

And now i can get a prepaid card from another provider so I can test the sound on calls which wasnt working with my t-mobile somehow...

And i can see how things should work :)
[Touch Cruise Android Development] excogitation:
Well ... there's your cause for the lag.

Switch back to dzo's system.img and the lag is gone.

I have no idea what changes mullins made -

just that the bootscreen is optimized for qvga

and the screen orientation switches to the other side

(so it isn't upside down for Kaiser).

Why would you even change the system.img

(or any other file for that matter)

without knowing what changes/improvements were made.
[Touch Cruise Android Development] radem205:
I never used the mullins system.img (still the DZO one) but I have the lag too. So I think this isn't the problem....
[Touch Cruise Android Development] Michel82:
Please read the other posts, the lag issue was solved and had nothing to do with the system.img

Because you don't know what changed doesn't mean i do too. I've followed all threads closely, including the kaiser one, the first system.img was based on DZO's without the ril changes, the second is based on DZO's latest. I tried that one to see how the bootlogo turned out to be. Please don't jump to conclusions.
[Touch Cruise Android Development] excogitation:
Well - I did read the other posts - still - when I just switch

from dzo's system.img (23rd, sms enabled) to mullins there is serious lag. When I switch back it's gone.

More than 107 files changed. Would you be so kind to enlighten me with a changelog?
[Touch Cruise Android Development] T1663R:
okibi just linked this http://www.ddev.info/android/Android1-31.zip

in the kaiser android threat with this description :

Someone do me a favor and test this package:

http://www.ddev.info/android/Android1-31.zip
[Touch Cruise Android Development] bally3:
dont know whether this helps but if you click the camera icon and let the camera app start and press the camera button, it goes to terminal and shows whats happening.

interesting is when you press the up or down volume keys. it shows "audpp dma missed"

Also this error message "mdp_dma_to_middi:busy" regularly appears.

Hope this may help in debugging some of the the outstanding issues.
[Touch Cruise Android Development] rogro82:
The audpp event is fired when it missed an audio event ( for example when you first press a button, it doesnt play a sound ) and the mdp is from the video driver... nothing really to worry about.

My work has been commited to the vogue kernel. You can see it over here:

http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-vogue

Hopefully more people can start working on it now :)
[Touch Cruise Android Development] dubbeld00:
Quick thing... you've changed the vogue_defconfig, maybe add a htcpolaris_defconfig and get the vogue back to normal.

Also in the make file:

obj-$(CONFIG_VOGUE_TS) += vogue-ts.o tsc2003.o board-htcpolaris-ts.o

remove board-htcpolaris-ts.o and add it to CONFIG_MACH_HTCPOLARIS, else i guess DZO can't build his zImages anymore.

Btw I must say, pretty neat code you've written!
[Touch Cruise Android Development] rogro82:
dubbeld00 ive changed the defconfig as its the one everyone is using... maybe we should change names ones, but this one will compile for polaris/kaiser/vogue at once without changes.

I also changed our ts so that it can be used next to the kaiser/vogue ts :)

Making seperate files/configs wouldnt work in making all devices supported in the same zImage. Now every image that gets compiled can be ran on all 3 devices :)
[Touch Cruise Android Development] Michel82:
Nice and clean commit. Good news you acquired a G1, hope you're able to make the polaris android version as good as the G1's.
[Touch Cruise Android Development] radem205:
I see that DZO has solved the audio path issue (http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-vogue)
[Touch Cruise Android Development] rogro82:
Yes, just spoken to DZO about some changes... Also hes going to change some calls like machine_is_htckaiser to msm7200 so that most stuff isnt working only when kaiser mtype is used ( I edit the mach-types.h to make the polaris also use the kaiser stuff ). That way it will even get it easier and cleaner.

Going to compile a new kernel to see how the changes affect our sound and if all is still working the way it should.
[Touch Cruise Android Development] imfloflo:
yeah a new kernel to test :)
[Touch Cruise Android Development] dubbeld00:
http://git.linuxtogo.org/?p=groups/...;hpb=138320aaed1046aca36f886d3f569a533414668d

hahaha DZO "fixed" the makefile again :)

btw, about the defconfig... it's about this line:

-# CONFIG_MACH_HTCPOLARIS is not set

+CONFIG_MACH_HTCPOLARIS=y

Now the vogue will also compile

+obj-$(CONFIG_MACH_HTCPOLARIS) += board-htcpolaris.o board-htcpolaris-generic.o board-htcpolaris-keypad.o board-htcpolaris-keypad-matrix.o board-htcpolaris-osd.o

Edit:

missed your last line "zImages can now be used for every device". That's great never saw the code which will select the board-<device> for the device. but nice to hear :)!
[Touch Cruise Android Development] rogro82:
He only moved the ts to the polaris section in the makefile... and he copied the brightness functions from the board-htcpolaris-generic to the vogue_hw so that is also works on kaiser/vogue.

This new way is way more easy for everyone. No need to set things up again after a new commit has been made. Only thing that needs to be changed are the specific machine_is_htckaiser/polaris to a more generic msm name, so that we can share code easier.
[Touch Cruise Android Development] dubbeld00:
Don't get me wrong (English isn't my native language as you might know)... the way you've created it is great, didn't know the goal was to create one zImage for all the devices, thought you still had to compile a device specific zImage :).

Saw DZO made a start with audio in phone calls, can't find it at the moment (git is "down" or extremely slow).
[Touch Cruise Android Development] rogro82:
No problem :)

Just created a new zImage with the latest changes from dzo included... Can anyone try if sound is better? Still need to buy a prepaid card so that i can make calls with my polaris again...
[Touch Cruise Android Development] marcelkordek:
thanks rogro... audio is fully working =) in call audio and mic works great =)
[Touch Cruise Android Development] imfloflo:
Just test the lastest zImage.

I had probleme with the wheel only the right button and the center button work.

The speak button pass the device in vibro or silent mode.

The volume key can pass the phone in vibro but unable to set the volume on again.

Haven't test the audio cause bad system.img i'll change it to another one.

But when i change the system.img to the lastest 21-01 package from dzo files the volume works great.

I think there are some function which are connected between system.img and zImage
[Touch Cruise Android Development] Michel82:
Tested and everything seems to work like before now including in call audio. This is a really awesome step. To be able to actually make and receive phonecalls with a phone makes this usable for day to day use :)

Going to try tomorrow for a whole day during work if it holds out and if i find it functional enough.
[Touch Cruise Android Development] marcelkordek:
i think battery life is not (yet) good... after 3-4 hours using android my battery is dead...
[Touch Cruise Android Development] bally3:
Are we still using mullns system.img, as I'm still unable to connect to gprs or make calls with than image. trying the previous dzo image
[Touch Cruise Android Development] imfloflo:
No we are using lastest DZO system.img with ril or sms code. but not working for everyone :s
[Touch Cruise Android Development] bally3:
Not working for me either I'm afraid, mic works but ear piece speaker doesnt, so caller can hear me but I cant hear them. this is with 21st Jan system image from dzo.
[Touch Cruise Android Development] radem205:
Try the package in the first post of the testing and bug reporting thread. This one works for me after I boot Android twice.
[Touch Cruise Android Development] imfloflo:
i download it again and finally work but calls not working .waiting new system.img from dzo
[Touch Cruise Android Development] croisez:
Hello,

is there any HaRET booting Android on my official HTC 6.0 ROM?

I would like to test Android on my Cruise, without reflashing the last official ROM image.

Louis.
[Touch Cruise Android Development] Michel82:
This thread is for development only. There's a separate testing thread. I've answered your question there: http://xdaforums.com/showthread.php?t=473102&goto=newpost
[Touch Cruise Android Development] Michel82:
Lots of hardware addons (wifi, bluetooth, GPS) on the dream GIT: http://android.git.kernel.org/?p=platform/vendor/htc/dream.git;a=summary

Maybe some are usefull for our polaris?! Some hardware is the same. At least bluetooth is, don't know about GPS and wifi.
[Touch Cruise Android Development] Michel82:
Seems like i'm the onlyone posting but DZO released a new zImage in the kaiser thread with some changes to the powermanagement:

http://xdaforums.com/showthread.php?p=3266089#post3266089

Changes are also comitted to the git:

http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-vogue
[Touch Cruise Android Development] imfloflo:
You aren't the only one :p i read and test each release too :p

But it's true don't speak very much.

My problem for the moment is to understand why the new zimage and system.img are so long to boot.

But hte lastest zImage-kaiser don't boot on my polaris i though there where generic code which read the mtype variable in the zimage to make it compatible with all device
[Touch Cruise Android Development] rogro82:
Ill look into when i get back from work... :)
[Touch Cruise Android Development] croisez:
OK Michel,

BTW I found my error: I had to define MTYPE for Polaris. Now the kernel boots.

Kind Regards,

Louis
[Touch Cruise Android Development] rogro82:
Hmmmm... Just got home from work but somehow the linuxtogo git seems to be down...

Ill try again in a few. Guess some changes broke the polaris support ( maybe the change from machine_is_htckaiser to msm ).

Ill look into it as soon as i have the new commits from the git.
[Touch Cruise Android Development] excogitation:
Does power management / led's already work like on Kaiser?

Does anybody else have a problem with volume up while playing an mp3?

Does the power button behave? ;-)
[Touch Cruise Android Development] xdadeverik:
In call audio works well (including via the speaker), brilliant work rogro82!! This means that I could now start using it by default. I still don't have internet access, but I'll try some different things before giving up on that. If it's reported to be broken I personally see working internet as the next highest priority.

For the first time, with DZO's image and rogro's 1-2-09 kernel/zImage, i'm able to switch to landscape (and back) through the button on the side.

I'm really amazed by the speed of development. Its like unpacking a present three times a week :)
[Touch Cruise Android Development] imfloflo:
just test the lastest DZO package with rogro files but no call working :s

same thing with http://slackthebox.com/android/Android2-1.zip
[Touch Cruise Android Development] radem205:
Rogro: I was wondering if you already had some time to add the new commits into a new zimage?
[Touch Cruise Android Development] rogro82:
Yes im working on it as we speak ( just about to boot a new zImage ), also found out why it isnt booting using DZO's image.

He copied the backlight stuff from my generic file to the vogue_hw file so that all devices could use it, but it isnt removed from our file... So compiling will break because of the duplicate declarations etc. So DZO commented out the CONFIG_MACH_HTCPOLARIS..

So i just fixed this for the time being and will make a new diff file later on to commit so that we can be added again.
[Touch Cruise Android Development] Michel82:
Great! Can't wait for the release to test. Does this include new additional changes by you besides the commityed power changes?

How's working with android everyday with your G1?

One other question: have you had a chance to look into the hardware drivers added to the android GIT? http://android.git.kernel.org/?p=platform/vendor/htc/dream.git;a=summary
[Touch Cruise Android Development] rogro82:
Ok here is the new zImage with the fixed power collapse from DZO. I didnt have any time this week to continue development ( some large projects at work ), besides a small start at the onscreen keyboard, hopefully I can do some later on this week or in the weekend :)

I also made a diff file of the changes I had to make to make it compile next to the kaiser/vogue code again and send it to Dcordes so he can commit it and people will be able to use new builds with the Polaris compiled in.

I think the latest pm.sleep_mode should be set for the power collapse. I guess it should have pm.sleep_mode=1 in the default.txt

Can anyone let me know if everything is working ok.

I made one change because i heared people couldnt get the sound to work when set to the vibrator once.. For me its working now..

Thanks.

Michel82:

The G1 is fun to play with... Speed is good and a fully working android is fun :D Only problem is that the new EU G1's are not able to get root rights "yet"
[Touch Cruise Android Development] excogitation:
I can't tell if power collapse works, but it boots fine.

I'll let it run for the night and again tomorrow with an old image to compare.

Isn't there an osk around that suits your needs?

I did have that problem - but only when playing mp3's - now it works fine.

Was the green led blinking before?

Can you adjust volume during a call? (dialtone)
[Touch Cruise Android Development] radem205:
Great job Rogro! Everything is working as it should be (except holding the power on / off button, but that's already known). In the kaiser thread DZO said that you would see the red led, but when do I have to see this light?
[Touch Cruise Android Development] rogro82:
Exco:

Ill use the old full keyboard and make it easier to switch in the future, at first it was implemented in the touchscreen driver, but this isnt the way to do it... because with every change you had to watch carefully you didnt mess up the driver and it was all too messy for me.. now the keypad driver just triggers the osd/osk and it will show up if it needs to and im going to make it so that the touchscreen driver will just redirect the input to the osd/osk when its on and the actual press can be handled in the osd file.

Will think of a nice way to implement this, so others dont have to find out the wheel again...

The led code is added to the vogue_hw code but i dont know if its working as its created for the kaiser, but i hope it does.. But i cant test it as i still dont have a prepaid card so i still cant call or register to a network..
[Touch Cruise Android Development] bally3:
works fine except I cant seem to connect to gprs again .. ear piece speaker is working again .. testing the power collapse to see whether battery improves, running cooler than before though. nice work again rogro :)

Is there any chance of getting the battery meter working or is that a userspace issue? would help to check the battery life at least.
[Touch Cruise Android Development] rogro82:
Bally:

Poly-p man is working on the battery driver (i2c)... the latest commit is from him ( almost-there attempt at kaiser battery ). Ill keep track of his changes and as soon as its working for the kaiser ill see if its also works for the Polaris or what has to be done to make it work.

The Polaris specific todo list im going to focus on first is:

* fix the problem with the power button

* add the soft press cam event and map it to the osk

* make the wheel work

* finish the osk ( most of it is already working, just need to handle the actual keypress event when pressing a button and clean up some stuff )
[Touch Cruise Android Development] imfloflo:
This zImage works great but i don't understand why booting is so long with the lastest commit ?
[Touch Cruise Android Development] bally3:
Thanks Rogro, have you been reading the kaiser thread re: project management?

i think the consensus now is since dzo spoke that kernel (zimage) development should be left alone to the developers to get on with and userspace (system.img) should be unified for all devices as its not device specific and maybe managed.

To that effect can you clarify what needs to be done at kernel level yet please, I'm going to add the todo list to the first post and try to seperate the kernel tasks from userspace tasks to avoid the "can we do this and that" posts that will inevdently follow once we have a daily usable kernel (for me that would HAVE to include working wifi as its in use constantly!).

As it stands theres:

Power button issue

Wheel

WiFi

Bluetooth

GPRS

GPS

LED's

Camera (mine seems to show a fuzzy green screen sometimes)

Can someone let me know if any of these are userspace and what other kernel develpements are pending.

thanks
[Touch Cruise Android Development] rogro82:
Onscreen keyboard is also implemented in the kernel.... The userspace already has one but thats no good for debugging/terminal use.

Battery driver is kernel level that interacts with the userspace, just like i set up the backlight.

Al userspace stuff for these kind of things ( leds, backlight ) etc are already in the Android build... "All" we need to do is create the appropriate drivers etc and implement them so they interact with parts in the userspace ( sys/class/leds etc )
[Touch Cruise Android Development] rogro82:
And a new zImage before im off to work...

I added the changes DZO made this morning.. It should fix some stuff on the data connection.

You should get the new system.img dzo upload on his site (http://xdaforums.com/showthread.php?t=396782&page=278). Youll have to add the ppp.apn to your default.txt.

Hopefully it will help for the people who have problems settings up a data connection. ;)
[Touch Cruise Android Development] excogitation:
With #630 kernel and pm.sleep_mode=1 power collapse isn't working (after 12hours barely one bar left).
[Touch Cruise Android Development] radem205:
rogro: did you also include the new commit with the few power management changes init? because i saw that this have different codes for the polaris.
[Touch Cruise Android Development] rogro82:
Radem:

Its build against a commit of 4am ( if im not mistaking ), I cant connect to linuxtogo at the moment because it seems to be down again else i could give you the exact description.

Havent looked at the power management changes yet.
[Touch Cruise Android Development] Michel82:
Kept android running for the day and it holded out fine. It used about 50% of the battery, which is a just a little more than WinMo does in a working day.

To be able to use android for a longer time at once raises another issue though; The internet connection seems to time out after a while. The 3g icon at the top disapears but Togga says i'm still connected. I'm able to disconnect in Togga and even reconnect again, but i don't have an actual connection as i'm unable to load any page or search in Maps.

edit: Forgot to mention. I'm not using the latest system.img from DZO with the channel opening changes. His website seems to be down. Anybody here has a copy and wants to upload it? Maybe this'll make sure i can reconnect.
[Touch Cruise Android Development] Michel82:
Somebody posted a rapidshare upload in the kaiser forum with the latest DZO files: http://xdaforums.com/showthread.php?p=3279463#post3279463
[Touch Cruise Android Development] briggs81:
Just curious what radio most of you are using if you are in America or Canada..
[Touch Cruise Android Development] bally3:
The new files allow me to connect to gprs and shows the ip address but i cant browse the web - I've connected through togga but not through winmo - testing with winmo gprs on.

EDIT: Rebooted and now gprs works fine without winmo
[Touch Cruise Android Development] dubbeld00:
Everything is working here :D (internet, sms, google maps (didn't made a phone call though)), don't forget to set the ppp.APN. You can debug in the other thread, but I made a connection in WinMo, adjusted the settings in the default.txt and ran togga. Great work :)! Btw, if you get an IP, you must be able to use Internet...

The ts only seems weird... Sometimes it is pick up 0, 0 (LEFT DOWN) point, when I start to press somewhere (looks like he is reading the position too soon), didn't happen before (only booted android once though, so don't know if it always happens).

Btw for vodafone NL users: ppp.apn=live.vodafone.com ppp.username=vodafone ppp.password=vodafone.
[Touch Cruise Android Development] rogro82:
Ill take a look at the ts driver... ive stripped a lot of stuff out of it but didnt have any time to look at the rest.

Its still not what i want it to be, so i guess ill redo it once i have some more time.

For now im busy fixing my laptop as it just totally died on me ( fan died and it was around 100 degrees when i got home and had crashed and booted all day long )...

Hopefully I can get it back to work else ill need to get me another one ( cant wait for it to be repaired... one day without a laptop is like hell :D ) :(
[Touch Cruise Android Development] bally3:
Damn you're having bad luck..!

Does anyone know why even though I have a 4gb card with over 2gb free, its still complaining of out of space when i try to download files? Do I need a linux formatted partition?