yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
1.) put the bootkit on first partition of your sd card

2.) in default.txt remove initrd line add root=/dev/mmcblk0p2 somewhere in cmdline

3.) deboostrap lenny arm locally (e.g. check the g1 link for instruction or debian.org wiki on deboostrap) and put it on the root of your second SD partition (ext3 or so)

4.) run haret from sd and boot

in theory this works with any distro and you boot it directly and natively unlike on the g1 guide you posted above with chroot etc

regarding this aspect of flexibility, a kaiser (or the raphael etc. once more usable) is the ultimate luxury. because what we do on our ported devices is "jailbrake" by design. g1 is designed to not be accessed in that way so it is way more hacky to use other filesystems and kernel is not changeable at all ;)
[Tilt, TyTN II, MDA Vario III Android Development] Akya:
so your saying we could use haret to boot debian? could we do this with ubuntu or any distro? cause im just dieing to demo winmo...
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
of course, try what I said
[Tilt, TyTN II, MDA Vario III Android Development] xmoo:
Dcores. Do you want to take over the thread?

I got my Xperia now, and want to move on.

If any update needed. Just holla @ me on MSN.

PPL good luck with Android + Kaiser
[Tilt, TyTN II, MDA Vario III Android Development] Akya:
If i boot debian is it going to overwrite winmo? or is it just booting from the sd card?
[Tilt, TyTN II, MDA Vario III Android Development] dwaradzyn:
It won't overwrite WM. Booting Linux with HaRET does not need any flashing nor hardresetting to make changes to Linux based OS. It is safe to boot Linux using HaRET. I have two words of advice to you:

1. It is quite easy to try to run distros like debian on Kaiser/Polaris if you are experienced Linux user. If you are not Linux expert then I warn you that it could be pain...

2. That question has been answered about 50 times in this thread. I gently encourage you to use search function more extensively before asking.
[Tilt, TyTN II, MDA Vario III Android Development] soulbandaid:
We need a new thread

We need a new thread. Actually we need two of them. We need one that's a guide about how to get the latest stable version of android to run on your phone, and one for development. I'm sorry I'm bad with commitments and would do a terrible job of maintaining a thread, but it would be a great contribution for someone to start another thread about either development or how to run android for the complete idiot. just my opinion.
[Tilt, TyTN II, MDA Vario III Android Development] Akya:
actually we need a new sub forum thats linux development... and i knew that haret didnt erase winmo i just wasnt sure if debian would install to the memory over winmo but i suppose there wouldnt be any diff especialy since theres not enough space without the sd card..
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
traitor!!!!1111111111111

of course, if that's possible I would welcome being able to update the thread myself.

edit: :D btw, did you boot kaiser kernel on X1 ? I bet you need to run the unlock thing first before you can run haret
[Tilt, TyTN II, MDA Vario III Android Development] farukb:
quick question...does the android use RADIO software from the WM...i have some trouble with wm radio and connections
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
yes we don't flash a different radio rom. are your troubles in wm? if so they are offtopic, sorry.
[Tilt, TyTN II, MDA Vario III Android Development] cijoml:
Dcores any news with sd driver and hints provided by dzo?
[Tilt, TyTN II, MDA Vario III Android Development] farukb:
i had some trouble and tried several roms and several radios

so i tried android (i was hoping that it would work so i could blame the WM :) ..but nothing)

and by the way...great work and thanks to all devs i hope you will continue with this and we will finally get rid of any windoze form (pc and ppc)

i'm a ubuntu user myself:D
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
nope.

"The message you have entered is too short. Please lengthen your message to at least 10 characters."

:P
[Tilt, TyTN II, MDA Vario III Android Development] slovoflud:
Thanks Xmoo and Good Luck and new adventures with the Xperia! :)
[Tilt, TyTN II, MDA Vario III Android Development] biscuits1978:
Sorry for the spam, but any updates? Haven't seen much activity on this forum for a while...:confused:
[Tilt, TyTN II, MDA Vario III Android Development] echofloripa:
You might be kidding... Look 4 posts above....

I'm as anxious as you, but there is nothing we can do other than wait for dzo to get the kaiser and finally get a working sd driver...
[Tilt, TyTN II, MDA Vario III Android Development] whitenight639:
Hey peeps,

I've just put android on my phone as per instructions on the first post in the thread and it worked for a while!!

how do I go about helping develop this, i am learning Java programming at college and think id be ok at bits and pieces, I just dont know where to start, what kit do i need? what should i start working on first?

oh and btw the zimage-kiaser-new wont work on my phone it just reboots WM.

(im running a standard o2 XDA ROM of some kind).
[Tilt, TyTN II, MDA Vario III Android Development] Kaiser01:
@whitenight639:

Posts #1446 and #1269 have been very helpful to me. I managed to compile the source after installing some additional packages in the ubuntu system. If you get errors, packages are missing, most of the answers can be found here. Good luck!
[Tilt, TyTN II, MDA Vario III Android Development] sswalia:
really, how long can it take to recieve a phone in the mail??

dzo have you recieved it yet? If it was not sent, then we should continue our quest to find a suitable donor kaiser for dzo to test on.

The phone was only supposed to go from one part of australia to another part, right?

Has the phone been sent in the mail?

Dzo have you recieved it yet?

PS: this used to be the most exciting thread on this forum since it seemed that we were on the brink of a fully working kernel for the past 2 months.

Now i think i might shift gears and watch linux get ported to completely undocumented hardware (the iphone) cuz the progress they are making is pretty rediculous considering how closed the hardware info is.
[Tilt, TyTN II, MDA Vario III Android Development] whitenight639:
Thanks Kaiser! Does anybody know of an android plugin for netbeans (i havnt had chance to google it yet im at college so dont shout at me for asking stupid questions just yet!)
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
I would check the documentation provided by google, android newsgroups at google and #android on freenode on that kind of stuff.

I've also been wondering what's up with the dzo-kaiser. I emailed him about it.
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
I haven't got it yet (and New Zealand isn't really just another part of Australia!!). It has a broken display so I won't be able to do a lot until that's fixed. You will have a working kernel, just not for a little while. If the Australian kaiser doesn't work out I'll let you know.
[Tilt, TyTN II, MDA Vario III Android Development] rkadar1:
k great news.... as for linux on iphone.... what the heck, that sounds pretty cool but why would you want to do that?
[Tilt, TyTN II, MDA Vario III Android Development] Dessie:
i don't know but from Sydney Australia to Auckland New Zeeland is about 2153.61 Km or about 1338.23 miles, and that's also over sea.

Then again from Darwin AUS to Sydney AUS is also 1956.36 Km :)
[Tilt, TyTN II, MDA Vario III Android Development] Michael.Bourn:
nothing important - just a thankyou

Hi guys, i've been reading this thread since it started, been playing along the way too, so far its been great fun so i thought id leave a message to

say thankyou to all involved for getting us as far as we currently are :)
[Tilt, TyTN II, MDA Vario III Android Development] cijoml:
Any news? Has finally dzo's Kaiser visited Opera in Sydney? :)
[Tilt, TyTN II, MDA Vario III Android Development] adderz91:
Yes what is the news, im tempted to send him my Polaris because i would LOVE Android on it...*sigh*
[Tilt, TyTN II, MDA Vario III Android Development] fb401:
Wanted to bring this back because I see there's a new angstrom console image.
[Tilt, TyTN II, MDA Vario III Android Development] echofloripa:
read the readme

008-10-29 htc raphael and htc diamond code are now available at http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-msm-2.6.25 based on the g1 branch
[Tilt, TyTN II, MDA Vario III Android Development] Sharkaat:
Eppur si muove :) We're getting somewhere now :D
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
I also put a new SD folder so you can boot the same rootfs off the card. http://linuxtogo.org/~lgorris/index.php?path=kaiser-bootkit/SD/

for some fun try putting a movie in there and play like this "mplayer /path/to/movie.avi"
[Tilt, TyTN II, MDA Vario III Android Development] cijoml:
Wau! Does it mean DMA problems are fixed and now we can make step further and boot version 1.0 now!? Who is the brave hero?
[Tilt, TyTN II, MDA Vario III Android Development] GuySparkz:
how does it look to have att 3g speeds actually working on the tilt with andriod?
[Tilt, TyTN II, MDA Vario III Android Development] silasrye:
A little more info please

I have been holding off on even testing android because it just wasn't usable, and the screen alignment was a big part of that too. I'm interested by recent posts about new android packages from 11/30.

however, it isn't simple for me to format my sdcard with an ext3 partition, so I'd like to know what I can expect if I do.

Could someone who has tried this please post a review?

Thanks
[Tilt, TyTN II, MDA Vario III Android Development] cijoml:
I am gonna try it today evening. Will let you know.
[Tilt, TyTN II, MDA Vario III Android Development] Pure4Real:
I've tested the new kernel (zImage-kaiser-new.bin) with angstrom and android

With angstrom it boots and gives me a console login screen but i cannot do that because somehow every button i press gives the same character ( something like [b )

With android it starts booting but doesnt go further than the red swooshing light (nightrider-like thing)

Could someone tell me how i should use this? I used the descriptions coming with the angstrom tar.gz but they gave me the first result. I put the angstrom tar.gz on the ext2 partition and correctly put the name of the partition in the default.txt

Greetings,

P4R
[Tilt, TyTN II, MDA Vario III Android Development] ex87:
This image http://linuxtogo.org/~lgorris/kaiser-bootkit/SD/angstrom-20081127.tar.gz is Angstrom image. It have nothing to do with Android. It's another Linux distro for ppc.

About "new" zImage-kaiser-new.bin - I think it's same zImage from 23rd October. (diff didn't show any difference).

For me image boots ok, buttons works ok, tried minicom at commands, it's possible to call but it seems that microphone isn't working.
[Tilt, TyTN II, MDA Vario III Android Development] Pure4Real:
Just tried it with the other zImage-kaiser-new and it appears there are some differences, as now i'm able to type stuff with the keyboard, but i assume there should be some window manager loaded? I see an angstrom loading screen for a few seconds but then it falls back to console view with the following text (i type-copied it so typos/hard to read stuff are there):

Remounting root file system read-write

root: mount: mount point /proc/bus/usb does not exist

configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device

eth0	No such device

udhcpc: SIOCGIFINDEX: No such device

Done

Starting portmap daemon: portmap.

hwclock: can't open '/dev/misc/rtc': No such file or directory

Thu Nov 27 23:59:00 UTC 2008

hwclock: can't open '/dev/misc/rtc': No such file or directory

INIT: Entering runlevel: 5

Starting Dropbear SSH server: dropbear.

Starting system message bus: dbus.

Starting syslogd/klogd: done

* Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon

[ OK ]

Starting gpsd: No /dev/tty3 GPS device, aborting gpsd startup. Check /etc/default/gpsd

(Angstrom ascii image here)

The Angstrom Distribution htcPaphae1(?) tty1

Angstrom 2008.1-test-20081127 htcPaphae1 tty1

htcPaphae1 login:_

From here i can log in and issue commands, is this how it's supposed to be or should i get a nice windows manager thingy?
[Tilt, TyTN II, MDA Vario III Android Development] Pure4Real:
Ok, tried it with android now aswell and it worked, felt like it was booting slower than before, but i didnt try to confirm it with a timer.

So if my conclusions are correct the zImage-kaiser-new.bin of 30 november is indeed newer and better, as it managed to boot both angstrom and android on my htc opposed to the older zImage-kaiser-new.bin. What are you using exactly ex87?
[Tilt, TyTN II, MDA Vario III Android Development] ex87:
I used cmp utility.

Downloaded and compared one more time - there is no difference (or I'm very far from truth :) ).

n3o@one-n3o-comp:~/kaiser_test$ ls
n3o@one-n3o-comp:~/kaiser_test$ wget http://linuxtogo.org/~lgorris/kaiser-bootkit/SD/zImage-kaiser-new.bin -nv -O k1
2008-12-02 00:22:22 URL:http://linuxtogo.org/~lgorris/kaiser-bootkit/SD/zImage-kaiser-new.bin [1138124/1138124] -> "k1" [1]
n3o@one-n3o-comp:~/kaiser_test$ wget http://linuxtogo.org/~lgorris/kaiser-bootkit/zImage-kaiser-new.bin -nv -O k2
2008-12-02 00:22:48 URL:http://linuxtogo.org/~lgorris/kaiser-bootkit/zImage-kaiser-new.bin [1138124/1138124] -> "k2" [1]
n3o@one-n3o-comp:~/kaiser_test$ ls
k1 k2
n3o@one-n3o-comp:~/kaiser_test$ cmp k1 k2
n3o@one-n3o-comp:~/kaiser_test$ wget http://linuxtogo.org/~lgorris/kaiser-bootkit/zImage.bin -nv -O k3
2008-12-02 00:23:43 URL:http://linuxtogo.org/~lgorris/kaiser-bootkit/zImage.bin [1213396/1213396] -> "k3" [1]
n3o@one-n3o-comp:~/kaiser_test$ cmp k1 k3
k1 k3 differ: byte 45, line 1
n3o@one-n3o-comp:~/kaiser_test$ cmp k2 k3
k2 k3 differ: byte 45, line 1

n3o@one-n3o-comp:~/kaiser_test$ md5sum -b k1 k2 k3
c4bb96d4ea2350b96ce9321379b29aa7 *k1
c4bb96d4ea2350b96ce9321379b29aa7 *k2
cdb26a86c0b36a6168ec611b10f4eba1 *k3

Where k1 is "new" zImage (from SD), k2 is "old" image and k3 (for comparison) is 21st July image. k1 is the same as k2 and both differ from k3.

If any think I'm wrong, please show me some differences in those 2 files :)
[Tilt, TyTN II, MDA Vario III Android Development] Pure4Real:
Strange, i guess i'm wrong then (not strange that i'm wrong, but more or less unexpected with different results in same kernels)

About what you use, i meant on your htc, what kernel and android/angstrom do you use? Did you manage to get more than a working console out of angstrom?
[Tilt, TyTN II, MDA Vario III Android Development] cijoml:
I tested kernel boot now haret starts kernel almost imeditially. I also tried play prison break episode with -vf rotate and seek few times forward and backwards for second, minute, ten minutes and in a while kernel crashed.

But great progres!
[Tilt, TyTN II, MDA Vario III Android Development] david.galindo:
Hi, I tried steps recomended by dcordes, with android with not success.

I have a SD with 3 partitions, 1 fat and 2 ext2.

1. in fat partition I put haret, zimage and default.txt as dcordes said.

2. in partition 2 I put angstrom image.

3. in partition 3 I put all android images, from android-23-10-08.zip (I found in one post)

- initrd with command cpio

- system and data in corresponding folder, by using command losetup and mount (see init script on initrd)

I modified default.txt in order to set rootfs for 3rd partition, but when I start with haret, at the end crash!

I started angstrom, and it works perfectly. Automatically it mounts other partitions. Then I try to execute init1 file on android partition and give me "FAT: codepage cp437 not found" error.

Any idea to continue?
[Tilt, TyTN II, MDA Vario III Android Development] Pure4Real:
Did you use http://linuxtogo.org/~lgorris/kaiser-bootkit/android.bin or another android? This one works for me (for as far it is functional) You dont have to put it on an ext partition, just leave it in the same directory as the haret and make sure you changed the default.txt.
[Tilt, TyTN II, MDA Vario III Android Development] cijoml:
your kernel is not compiled with p437. You must recompile it. Piece of cake ;)
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
hey,

when kernel dies while you seek in mplayer and the file played is on the sd, that is the dma problem. I will try contacting barry about how to enable pio mode. I think it would be slower, but if it is stable we are one step closer towards a working device.

btw I talked to dzo and he said he never received the kaiser. I really wonder why on earth people make such offers while they know they won't do it anyway. makes no sense.

anyway. furthermore dzo said it would be better ifw e could collect 300 euros so he can buy one himself.

edit: the stuck button problem where every key prints b) or so, is documented in the README.txt todo list. just rotate the scrollwheel when it happens and it's gne.

regarding audio when dialing manually: you need to set the mode. iirc it's also done using AT. I wil look it up when I'm home.

regarding a 'fancy windowmnager thing' : Xserver doesn't work with the framebuffer codew e use now. android has some userspace magic to make zygote work. 'pixelflinger'. we need to port that tot he fb code or also apply in userspace
[Tilt, TyTN II, MDA Vario III Android Development] cijoml:
I could buy kaiser with destroyed display...

http://www.aukro.cz/item494168454_poskozeny_htc_kaiser_tytn_ii.html

1USD = 21 Czech crowns
[Tilt, TyTN II, MDA Vario III Android Development] cijoml:
http://anymore.nl/ipaq/files/graphical_images/unstable/

I tried boot GPE from this, but it stays stuck after logo - probably fb problem
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
@ cijoml read what I said in my last post regarding X:

you might try this root filesystem which also has X. you will get the same result though. you can pick all the builds for msm7* from my site ( OE folder). they are optimized for the armv6-novp (used on msm7*) arch.
[Tilt, TyTN II, MDA Vario III Android Development] TaC:
A question comes to my mind after reading the last 10-20 pages of this post.

Why has to be dzo the one who make this possible??? There are too many different phones and no one has got it working on them. Why should we give dzo a Kaiser to get Android running on it?

Maybe dzo is an Google technician who works on Android and he can do it without problem. In that case, then i have not understood anything, and i will be the first giving him money for the cause.

If he doesn't... then i don't understand the interest and importance in giving him the device. Please, tell me. :)
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
look, there are many persons involved in such projects. if you count everybody in who contributed to the linux kernel, you count a long time. dzo is one of the persons who were involved for the beginning in making linux run on msm7* chipset devices, namely the vogue. and now vogue is the best supported hlinux handheld with msm7* chipset. he offered his help in case he gets a kiser and that's how the motivation giving him a kaiser arose
[Tilt, TyTN II, MDA Vario III Android Development] TaC:
OK, nice answer. I understand it now. But, since Vogue has the same chipset as Kaiser, why don't we wait till vogue is fully operative with android, and then giving the creator/s the tools they need to port it to Kaiser? If dzo is working in vogue, let him finish that work (he will do anyways) and after that point, we may contribute to give him the kaiser he needs to do the same as with vogue.

In any case, it is very odd that we have magnificent developers here, and no one has got an open source OS to work on devices with a supported chipset. :confused:

BTW, i'm not accusing anyone (of course not dzo), i'm only triying to "move minds" around this Android thing.

P.D: gotta polish my english... :D
[Tilt, TyTN II, MDA Vario III Android Development] wornbat:
Screens are Cheap on Ebay

I got a screen for $49 AU from EBAY not long ago to replace my cracked Kaiser Screen (also comes with Touch panel). Its easy as to replace the screen on them just 4 screws and a plastic knife to open the tags around the front panel. So if you can get one cheap then its no big deal to replace the display.
[Tilt, TyTN II, MDA Vario III Android Development] cijoml:
vogue and kaiser are not the same chipsets. They are slightly different and peripheals are all different (which device is cheaper at the moment, that device HTC incorporate into new phone)
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
Not really true, the only different peripherals are the panel and wifi(which vogue doesn't have) all the important stuff, sd, audio, i2c etc are identical. The main difference is the radio (amss), but that shouldn't be much of a problem.

I'm away for a few weeks from mid december so even if i did have a kaiser, i couldn't do much for a while. If someone wants to step up and really get this working, I am quite happy to help. I think what you need to do is the following:

1. get sd working, look at the vogue tree and copy that exactly. if DMA is broken (it isn't on vogue so I don't know why it would be on kaiser) use pio mode. It's all there in the driver. The msm SD hardware seems to be quite timing dependent, if you look at the halibut code it also has some delays in it, possibly a well placed udelay could solve all your problems.

2. See if the smem layout is different, there should be a table near the start giving the location of various data structures. It should be fairly obvious, important are the smsm states (for the A11 and A9), the rpc fifos and the gpio_save structure. Sizes and contents should help, I can send you an example of the vogue smem if you need it. The pm code (pm.c) needs to write to smem to set up power collapse. Without this the phone can only do a swfi (suspend and wait for interrupt) and will run the battery down quickly. rpc is needed for audio and the camera.

3. check that rpc works the same way as on vogue. there should be 2 pairs of fifos, one pair for commands, one for replies. the program numbers may be different but probably not.

4. find the adsp image and queue numbers. the way the adsp works is that you send an rpc to the a9 to open a "task" then the a9 replies with an image no. you look this up in a table and this gives you a set of numbers for queues to do various things (audio post processing, video front end, etc..)

Somebody must be able to get kaiser running, after all I've done most of the hard work. I know the vogue code is not very well documented, I was just trying to get something to work most of the time so if you have any questions just let me know.

Martin
[Tilt, TyTN II, MDA Vario III Android Development] cijoml:
Martin does it make sense for you to have kaiser with broken display? I could buy it for you...
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
Martin,

Barry proposed trying this in common.c in order to enable PIO mode on the kaiser:

I put that function in place and it doesn't work. Booting from SD I get the following

any idea?

The kernel I use is here http://linuxtogo.org/~lgorris/diffs/git-diff-android-msm-htc-2.6.25_kaiser_20082210.diff applies against android-msm-htc-2.6.25 in the google gits. (g1 branch)

edit1: I thought in pio mode it might take longer for the card to initialize. but I added a rootdelay of 10 seconds and ended up with the same errors. will try booting with initrd
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
update

Barry experienced the same results and will probably have a close look

@dzo the sd code we have is pretty much an exact copy of the vogue code