yashsingh1/xdaforums huggingface dataset:
[Touch Cruise Android Development] T1663R:
Hey,

just a question, which radio u guys use for the newest release ?

because with my old radio all the releases worked good until now, but the new release always stopped at haret 100 % so i updatet to radio 1.59.46.12 and 1.59.44.02 but with both radios i dont have sound and my camera doesnt really work anymore in windows mobile . Is there maybe a other radio that could work with the new release for me ?

i use 3LIT3´s rom.

greetings tigger
[Touch Cruise Android Development] marcelkordek:
you can try the unreleased 1.65.30.09 Polaris radio...
[Touch Cruise Android Development] excogitation:
will also be in the git in a bit (sent it to biktor to look at it).

see my signature - R 1.59.44.02 - I don't see a reason why yours shouldn't work anymore all of a sudden.

I don't see a reason - unless that has improvements (receiption, gps, less energy,...) - so is it better?
[Touch Cruise Android Development] T1663R:
alright i tryed radio 1.65.30.09 but same result as before, no audio and camera not working. any other idea ? :-(

EDIT

@ excogitation

i had an older radio, but it doesnt seem to work with the new android realeses.

if i update my radio to R 1.59.44.02 i dont have sound in win mobile anymore, also the camera doesnt work.

thats the problem

1.59.46.12 and 1.65.30.09 also dont really work

only thing ive seen is that somethimes audio works, but after one call it doesnt work anymore and i have to restart the phone for it to work again...

EDIT2

i forgot to mention that the newer radios never really worked for me.

I used the older ones but now that i have to switch to newer radios for android to work i got alot of trouble because of the reasons i have described ...
[Touch Cruise Android Development] excogitation:
So you have some ****ty rom?

I would just use (actually I do) the standard 6.1 rom.
[Touch Cruise Android Development] T1663R:
ah thanks exco, with the official 6.1 rom it works. Also when ive plugged in the usb cable and run android the phone gets detectet in Windows howerer it want drivers for the android phone to sync with it, where can i get those or is there any workaround for that ?
[Touch Cruise Android Development] dysolve:
hello all,

Its been awhile! After a visit to Martins site over @ massey. I go the lastest file, put them on the root of the sd-card , adjusted the default.txt file and tried to boot .. but it stoped @

"no partation on sd card

/bin/sh: can't access tty1 job control turned off

#"

so what am I missing this time LOL!

radio:1.65.30.09

rom:3lite3

thanks.

edit: i just downgraded the radio to 1.59.44.02 and now haret does not even boot to command prompt.

edit 2: tried again and its getting stuck at the "no partation on sd card" part again
[Touch Cruise Android Development] marcelkordek:
thank you..works great
[Touch Cruise Android Development] webbdn:
Hey has anyone been able to use ADB to connect to their Android (dzo's cupcake image) phone?

I've been trying but ADB just keeps saying " - Waiting for device -". If I type "adb devices" there are none shown.

This hasn't worked from my Windows box nor my Ubuntu box. Using ADB from the Android 1.1 and 1.5_pre SDKs.

Now that USB is up using latest zImage and Dzo's initrd.gz I can telnet to the phone from Linux but no ADB.

Anyone managed to get this working?

@dysolve I've got the same radio (1.65.30.09) and ROM (3lit3 VI) as you and I've not had that problem with the sdcard.

I've got the following setup on the root of the sdcard:

Dzo's cupcake android.zip (http://it029000.massey.ac.nz/vogue/files/android.zip)

Dzo's initrd.gz (http://it029000.massey.ac.nz/vogue/files/initrd.gz)

Excogitation's zImage from this thread

HaRET

Default.txt
[Touch Cruise Android Development] dysolve:
thanks for the advise/input webbdn, I download all of what you are using. first time I run haret, it stops at the 100% on the haret load screen, then after a softreset it stop at the sd card poblem. I left it at the haret screen over night to see what would happen but it was still stuck there 8 hours later.

Maybe I am having some sd-card issues. I will try a different card today.
[Touch Cruise Android Development] dzo:
I just put a new build on my site, it should have the latest polaris patches, can you check it out. Also has the vsync fix so should be smoother (though this doesn't seem to work as well on kaiser as vogue).

Out of interest what frame rate does the api demo in graphics..opengl es..sprite text give you. Vogue is 22, kaiser is 36 and I can't understand why it should be different.

Thanks,
[Touch Cruise Android Development] pananza:
I get 33 ms/f on my Polaris.
[Touch Cruise Android Development] dysolve:
I just noticed something. I changed cd-cards and I am still having the same issues but when I run haret the "start bar" moves from the top of the screen to the bottom. is that normal?
[Touch Cruise Android Development] marcelkordek:
yes "start bar" moves from top to bottom...
[Touch Cruise Android Development] webbdn:
Hi Dzo, I did a before and after test using the Sprite Text demo:

Before the latest android.zip/zImage I was getting 43 ms/f (23 fps).

After the update this improved to 32 ms/f (31 fps)

Feels much smoother.
[Touch Cruise Android Development] dysolve:
I just figured out that will bot ok with out sim card in the phone, but once I put a sim in the phone it will not load! past the booting Linux screen
[Touch Cruise Android Development] marcelkordek:
you must disable your sim/pin.
[Touch Cruise Android Development] dysolve:
ok after a little more reading and playing, I now have android booting up and it is able to send and receive sms's it can also receive calls but disconnects before dialling the number while making a call. I can also not get data to work but that's not a big deal. The funny thing is I have never been able to make a call with android. The only thing I did to get it to boot with a simcard in it was to disable the bluetooth.
[Touch Cruise Android Development] excogitation:
That's interesting...

because I (Polaris) do get 22ms with 1.1 and mddi.width=312 mddi.height=416

Also biktor_gj gets the same result for his Nike.

(depending on "I still have to find out" ... my system runs awful (->1000ms))

Btw "task 38 and 55"

Same as on Kaiser:

S5K3C1FX03

OV7670

TNETW1251
[Touch Cruise Android Development] radem205:
When I use the Android 1.1 files everything is going very slow. Also booting Android is going very slow. I have tried different versions (also the 1.1 20-04-2009 files) without better results.
[Touch Cruise Android Development] imfloflo:
@radem205 same thing i remember at the begining the androids boots very fast with the first 1.1 release
[Touch Cruise Android Development] radem205:
@imfloflo: Also in Android everything is going very slow. So this isn't the same issue which you and some others noticed a while ago.
[Touch Cruise Android Development] excogitation:
I also have this issue - but I can't pinpoint it atm - because sometimes it runs really smooth (faster as before) and sometimes it runs terribly slow.
[Touch Cruise Android Development] dysolve:
I am having the same issue but its not on every boot. I have noticed that it is slow every third or forth boot and if I soft reset the device it is slow on next boot. If I power the device down correctly it seems to work fine the second time but after a few retries it goes slow again.
[Touch Cruise Android Development] dzo:
Perhaps the cpu clock isn't at the right speed after power collapse, try setting pm_saved_acpu_clk to 400000000 in pm.c just after line 331.

Martin
[Touch Cruise Android Development] excogitation:
Here's a kernel with that setting and it does run fast (just tried a single boot).

btw the sprite demo also runs at 22ms with 320x480.

Also, Martin - is there an easy way to get rid of the the panel_type kernel parameter?

From what I remember there were 2 different panels on Magician and it didn't need a kernel parameter to detect it.

As far as Polaris goes from what I read there are 2 different screens actually used (but I found 8 different part numbers that are supposed to fit).

I think we might not even have the data for the 2 different screens (if they're not the same as on Kaiser) but you already told us how to get the needed info.
[Touch Cruise Android Development] dzo:
I don't think there is an easy way, it is possible but the easiest thing to do is probably to disassemble the wince code to see how it checks for the panel type, not really fun. It probably only checks on boot so tracing won't be helpful.

I don't really know how much power the panel uses. You could do an experiment, boot with panel type 0 and then the correct type and look at the battery messages to see how much power is being used when the panel is off.

22ms is good, same as vogue, looks like my kaiser doesn't actually have a hardware vsync, it's just a timer.
[Touch Cruise Android Development] radem205:
It's working now I guess. Thanks dzo and exco!
[Touch Cruise Android Development] imfloflo:
Thanks Exco booting faster.

But i have an issue i don't success to reproduce.

I download the android-20-04-09.zip version and when i launch it my PC detect my phone as "Android Phone" but unable to install it because no good driver found.

Then i install android-1.1-20-04-09.zip version and i haven't this detection anymore. My pc don't see the Polaris under Android. I retry the first version but my pc don't see it anymore :s

I read DZO says it was a cupcake version..
[Touch Cruise Android Development] dzo:
Those both have the same kernel but the usb is a bit unreliable on 7200 phones, usually it detects it the first time but not afterwards. It won't work on a windows box anyway. Perhaps I'll have a look at getting the adb driver working.
[Touch Cruise Android Development] imfloflo:
Yeah the first time adb.exe launch on my process list but seconde time nothing appears and neither in the device manager (for information i'm under Windows Seven)
[Touch Cruise Android Development] briggs81:
I've sort of lost track of what the latest/most stable image I can use is.. and where are you guys watching for updated versions to come out?
[Touch Cruise Android Development] Scalap:
My way to see if there are some changes is to go on the dedicated thread on the kaiser/polaris forum and to check this web page : http://it029000.massey.ac.nz/vogue/files/?C=M;O=A (with chronological classification).

There is also this website that eezak spoke about on the kaiser thread : http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-vogue

Good Luck/Reading
[Touch Cruise Android Development] imfloflo:
I just test the lastest f00bar release and i have some problem with some key ( red key) whici is broken :s.

The SDK 1.5 version running good. BTW global time crash when i launch it .
[Touch Cruise Android Development] radem205:
@imfloflo: Red button is working for me, but I can't open the menu box :s.

Edit: When I boot again Android gets stuck while booting :s.
[Touch Cruise Android Development] dzo:
I've got the GPU working on Vogue and Kaiser, to make it work on Polaris all you need to do is add pmem_gpu0 to the board file in stacked memory and move the mdp pmem to EBI. Just look at the kaiser changes. With a new system.img the hardware openGL renderer works nicely. See my posts in the kaiser and vogue threads.
[Touch Cruise Android Development] radem205:
Very nice job, dzo! I have one question: is it difficult to integrate the new SDK1.5 with your files? Maybe a new version? On the polaris the biggest issue with your files is the absence of the softkeyboard.

You are doing a fantastic job so far!!!!!!
[Touch Cruise Android Development] imfloflo:
@radem205 with the lastest files from f00bar my red button not owrk for me.

BTW hope you will success to have openGL working on our Polaris
[Touch Cruise Android Development] radem205:
But did you have problems booting foobars' version? Because sometimes it's booting and sometimes not. And when vibrating, it never stops vibrating so I can shave with it :).

If you don't have problems booting android, could you please post your default.txt?
[Touch Cruise Android Development] imfloflo:
NO problem with boot with or without usb plug in

#Polaris
set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.gz

set cmdline "mddi.width=312 mddi.height=416 pm.sleep_mode=0 board-htcpolaris.panel_type=0"
boot

The screen seems little blur with this settings but all working fine.

Like the new bootlogo and the Android booting very speed the second time :)

(the red button have the same option as the power button turn off/on screen )

Vibrating is bugging for me too. ( i must type red button or power button to stop it) btw the operator name isn't auto detect i read Android instad Orange F.

When trying to take photo push the middle button and camera.apk crash.
[Touch Cruise Android Development] radem205:
Thanks, I think it has to do with the pm.sleep_mode. I set it to 1 but when I set it to 0 everything is fine.

You have to set the resolution to 240x320 in order to fix the blur.

BTW: Finally a working keyboard. Nice!
[Touch Cruise Android Development] briggs81:
You guys using a particular radio rom and windows base rom?

I've downloaded f00bars latest.. will give that a shot.
[Touch Cruise Android Development] briggs81:
I am either really bad at this or unlucky.

I have downloaded..

android-21-01-09 and edited my boot script

set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.gz

set cmdline "mddi.width=240 mddi.height=320 pm.sleep_mode=0 board-htcpolaris.panel_type=0"
boot

Tried booting android while connected and not connected.. freezes both times.. waiting a few minutes each time.

I've also started from scratch with dzo's latest cupcake/android.zip and that one just freezes.

dzo's android-1.1-25-04-09.zip showed a whacked (mess of colors and unreadable) out screen at first, then i tried a second time and it's just the Linux black screen recording my "polaris wheel direction".. doesn't do anything else.

dzos 1.1 results in a load up, but no keyboard of course. and the icons and text are bigger then they should be but not a huge deal.

I am using the same boot script above for all attempts. Is that a problem?

I will continue to play with it, maybe i"ll get the right combination eventually.
[Touch Cruise Android Development] biktor_gj:
Hi all, I ported the gpu config from dzo's work on Kaiser, you should have 3d hw acceleration enabled on this kernel:

http://rapidshare.com/files/226253116/zImage

Let me know what it does and I'll push the changes to the git if it's working fine, ok?

Regards!
[Touch Cruise Android Development] radem205:
nice work biktor, thanks! I'll try it later today and let you know if all is ok.
[Touch Cruise Android Development] midafaya:
hey !nice work

But i can't see the keyboard in android-21-01-09

is there something to specify in default.txt?
[Touch Cruise Android Development] imfloflo:
Can someone upload this zImage directly on the forum upload tools cause my proxy block rapidshare :s please
[Touch Cruise Android Development] marcelkordek:
latest zimage from biktor... thanks
[Touch Cruise Android Development] biktor_gj:
Second test run with dzo's latest changes: http://rapidshare.com/files/226325730/zImage

On the nike it has worse performance, but all the garbage on the screen has disappeared...

Thanks dzo!
[Touch Cruise Android Development] radem205:
The first thing I noticed is that the wheel is working now (in the terminal) :). I think the gpu is working too, but I don't know for sure. The overall performance is great!

Edit: When I change the resolution to 312x416 the overall performance is very bad (it stutters) :s

@Biktor: Could you please check if this is set ok: http://xdaforums.com/showpost.php?p=3662443&postcount=1154
[Touch Cruise Android Development] marcelkordek:
testing the new system.img and your zimage... works great but i have no audio and when i try to run a opengl test my phone reboots...
[Touch Cruise Android Development] Michel82:
I've been away for a while and am trying to catch up on progress. Can anyone give me a quick update. What's this f00bar version, is it based on 1.5 (with keyboard)? Where can i find it.
[Touch Cruise Android Development] bally3:
In Advanced Config program in Win Mobile, there are power management optiions for SD and MMC - mine are disabled by default on Maxniper's Omio rom - but could these settings effect the sd card initialisation process in linux since we were saying that the card is already initialised by windows?

worth a consideration..
[Touch Cruise Android Development] dubbeld00:
DZO also said Windows Mobile had disabled it by default (also on his device), maybe because of a hardware error. Therefore wince uses PIO (as DZO told).

Also the SD card is only mounted and completely initialized by Linux... So the settings on WinCE shouldn't matter (as far as I know). DZO also told us that PIO mode might be in a newer SD Driver (but I guess dcordes (or someone else) already checked that out) which should work properly.

But I'm awaiting DZO's findings on the Kaiser... which should arrive in January :). I think I'll wait for that...
[Touch Cruise Android Development] imfloflo:
That would be a great git for the new year :)
[Touch Cruise Android Development] bally3:
May get to that, but I think we're making progress as it is as DZO himself commented on irc. To be honest, if we do have to wait for DZO to fix it, so be it, but it does highlight the problem we are facing with these projects - we're too happy to let someone else do it for us.

Rolk and Dwaradzyne have made great progress on their own, I'm still of an opinion that we should try to get more linux developers involved and I do NOT accept "lack of kernel development skills or time" as an excuse not to get involved. (I'm not a programmer, I have a wife, children and a new baby on the way in the next week or so and even I'm putting both feet in - thanks to Dwaradzyne).

It may require someone with the dev skills of DZO to fix it in the end, but the sd card issue is not the only issue we'll have to overcome and I think we should keep on plugging at it - if only to get a better understanding of what we need to do once the sd card issue is resolved. In the mean time it wont hurt anyone interested to try making changes and compiling the kernel as Rogro82 is doing to see what we can learn. There is plenty of help available if you get stuck- you only need to ask.
[Touch Cruise Android Development] dubbeld00:
You are absolutely right... Also about the program thing... Read some documentation, and start changing scripts... It really isn't that hard.

Btw I shall soon make a new guide about how to check out the git (or is the previous one still right?).

Secondly, we are using the linuxtogo git?

And finally, any progress/news? (just out of curiosity)
[Touch Cruise Android Development] maximos86:
well instead of writting the same things again(documentation) and again y not just write a basic bash or perl or python script that does the checkout and aplies the patches??? it might make easier for new users to checkout the repository
[Touch Cruise Android Development] rogro82:
Ok im building a new zImage against the commit c092738e01ab845dc7406dc1b53589b1f9edebbc and using most of DZO's .config file.

At the moment im fixing all errors that come up.

Ive managed to create a zImage that boots and extracts the gz files without a problem ( with the older code i had to unzip them myself ) and then mounts them..

I had to hard code a delay in the post_init call to wait for the sd card to initialize, because rootwait and rootdelay calls werent working for me.

But still need to fix / include some ( rpc / battery / adsp etc ) sources.... but its worth a shot :)

At this moment it still hangs after the modem / local loopback initialisation ( init: untracked pid 432 exited )
[Touch Cruise Android Development] imfloflo:
Well done, rogro82, And if you try to jump this step (modem) just to try if we can go further?
[Touch Cruise Android Development] dubbeld00:
http://xdaforums.com/showpost.php?p=3029702&postcount=87

devslashnull already did this... (same commit hash)... Don't know if you already saw this... but we don't use the linuxtogo git? or are we now using 3 different bases to make the same thing?
[Touch Cruise Android Development] dwaradzyn:
Just to clear things up. We should use this commit + szsoftware patches as our base. Details of how to get them are in post #40 of this thread.
[Touch Cruise Android Development] dwaradzyn:
devslashnull diff

Did anyone look/try at the diff posted by devslashnull? What changes does it contain?

devslashnull: you could save us the effort to reverse engineer your changes by simply posting what changes you have done.
[Touch Cruise Android Development] rogro82:
I didnt have time to look into it and if its just the patches applied then its ill continue my own work, so maybe he can clear up what has been done.

As said before im working on the commit c092738e01ab845dc7406dc1b53589b1f9edebbc which is the htc dream/g1 commit against the linuxtogo git.

As soon as i have some serious work done ill post a diff file.
[Touch Cruise Android Development] SHAYDER:
Link in 1-st post dont work!!

initrd for Polaris
[Touch Cruise Android Development] dwaradzyn:
dirty hack to get X working

For those interested in playing with X on Polaris. Compile kernel according to post #51 + replace vogue-ts.c with attached one (and preferrably make a diff I had no time to make and post it here for others). It contains a dirty hack to force a screen refresh 20 times per second.
[Touch Cruise Android Development] dwaradzyn:
new basecode

Many of the messy things we happen to have with linux/android on HTC is because there is no common repository with current kernel codebase. I promised to do something about that - do the merge of polaris/kaiser code into current raph/diamond htc-msm-2.6.25 branch. Current raph/diamond code should boot on blackstone (i happen to be a happy owner of one and i can test it). I will try to push my changes about the end of 2008. Then all polaris focused developers should switch to that branch. Further roadmap includes merging with google 2.6.27 branch. It will be much easier if we (XDA) have one common codebase.
[Touch Cruise Android Development] dubbeld00:
Thank you... It shure is :) It looks like the first time we start the development, everyone was starting from scratch, had an own codebase... and once in a while they were willing to share there code... (almost the same for this attempt). But I'm leaving for a week...
[Touch Cruise Android Development] Michel82:
Good progress here guys. Seems like this is finally slowly becoming a real project together with the vogue and kaiser people. I'm following this thread and the irclogs closely. But i'm wondering how far away we are from a 'normal user' installable android rom. This is our final goal right; Android linux available for every polaris user?

Is there somebody how can give me an estimate on the timetable and the biggest open issues.
[Touch Cruise Android Development] rogro82:
Ive managed to make a bootable zImage based on DZO's changes ( Im merging dzo's code with the changes from the polaris/kaiser diff files and change things where needed ). It mounts the filesystem, and then starts Android.

But for now it hangs on the screen that shows the android logo and the robot with the fading glow...

Is there any log output of android? maybe in the data file?
[Touch Cruise Android Development] Michel82:
logcat gives you all log information (logcat -d for dump to screen) http://code.google.com/intl/nl/android/reference/adb.html
[Touch Cruise Android Development] Michel82:
This guy (http://sites.google.com/site/siteofhx/Home/android/android-porting-steps/english) makes porting android sound like something to do in your lunchbreak ;)