yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] MrSmileyJr:
How do I get 1.0 to boot?

Hello,

I'm looking for exact instructions on how to get 1.0 to work.

Heres what I got so far but theres a few missing pieces..:

1) Make sure you have the correct radio = 1.65.24.36

2) Get Haret from ????

3) Get zImage from post # 1888

4) Put all files on SD card

5) run haret and enjoy

Now I know something is missing... anyone want to fill in the blanks?
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
for #2 and the files go here http://xdaforums.com/showthread.php?t=396782&page=179
[Tilt, TyTN II, MDA Vario III Android Development] astrocrep:
Download the RaR from page 183 post 1824 (I believe)

Extract the Rar to the root of your sd card...

Take the newest zImage from the last page and drop it into the andriod folder. Then edit the default.txt and removed the # from the line that says something like KERNEL zImage and put a # at the line the sets the kernel to the vogue ok...

Heres my default.txt

-Rich
[Tilt, TyTN II, MDA Vario III Android Development] MrSmileyJr:
ok - I did this, but I get stuck at "Haret:booting linux...."

using the zimage from post 1824, android boots, but the new zimage....stuck at the end of the green bar booting...

ne1 know why?
[Tilt, TyTN II, MDA Vario III Android Development] drofmij:
Why specific radio version?

What ties this to a specific radio version?

Would it be possible for this kernel to work with other radio versions (obviously with code changes)?

How much work would this require?
[Tilt, TyTN II, MDA Vario III Android Development] skola28:
Mine boots fine. Using indicated radio, and modifying the config file to point to the correct zImage.

NICE WORK!

Hint, once you get it to boot, 'Menu' is the Internet Explorer button. RED (hang up) is 'BACK' ENJOY!
[Tilt, TyTN II, MDA Vario III Android Development] ajclai08:
I with these guys..I want to stick with a Kiaser radio. I'm pretty sure they could get it working becasue the version they're booting from was taken straight from another phones version of android...
[Tilt, TyTN II, MDA Vario III Android Development] uplinked:
I might be confused, but why do you say 1.65.24.36 is not a kaiser radio? I've been using that radio on my Tilt for ~3 mo.s and it provides far-superior reception to any of the other radios i've tried.
[Tilt, TyTN II, MDA Vario III Android Development] MB300E:
Tried and it booted fine in my phone, nice work :)
[Tilt, TyTN II, MDA Vario III Android Development] ddfire:
hi

i few questions i use this zimage but the others files? from where i can download them?

how i know iwch radio i have? how i put the rigth one?

there isnt any web page/wiki just whit the latest info instead of an infinite post?

if not i can host it just point me the step by step how to run android on kaiser

(tilt,tytn II, others)

link to each file

Thanks
[Tilt, TyTN II, MDA Vario III Android Development] Kaiser01:
Activate WLAN before starting Haret, and press button "Listen for network connection" inside haret before pressing "Run"-button.
[Tilt, TyTN II, MDA Vario III Android Development] Kaiser01:
Read only one page back, same question there.

Radio version is shown in Settings -> System -> Device Information (or something like that). Information about flashing a new ROM can be found in the Wiki, hints some more pages back, same question there.

Nope, not now. Developing a stable version is more important at the moment. Be patient...
[Tilt, TyTN II, MDA Vario III Android Development] MrSmileyJr:
i got it to work - i redownloaded the new zimage and copied it over to my card again - it must have been corrupted or something - works now - no need for the wlan + listen for net connxn thing

it seems to work pretty well - i think we're pretty close to a usable android kaiser :-)
[Tilt, TyTN II, MDA Vario III Android Development] echofloripa:
I believe it's important to have this information in a single place...

Unfortunately if a better consolidated information isn't given properly, be it at the first page or at one of the wikis already created for this, this thread will continue to be bombarded by the same old questions over and over, and people that could be fixing the problems will be wasting their times reading/answering here... And the main answers will be lost in the middle of the hundreds of questions. Where is xmoo to update the first post???
[Tilt, TyTN II, MDA Vario III Android Development] ex87:
Fn not working

It seemas that Fn button doesn't work itself. By pressing 8 you press N, that's 6 on standart phone., like 9 = M (MNO = 6 on standart phone). It's for calling "easy memorizeable numbers", like 1-800-GOOG411 where goog part is 4664.
[Tilt, TyTN II, MDA Vario III Android Development] ddfire:
i cant develop android but i can make the wiki so give me the info and i will make it and host it for the community.

and as some told that will finally stop the same questions every time.

i will transform an ugly txt to a decent wiki if someone give me the ugly step by step. or point me whit a link or something

David
[Tilt, TyTN II, MDA Vario III Android Development] lyka:
For those who can't put all pieces togheter, here is a ZIP with haret, initrd.gz, zImage.bin by mullins07 and default.txt.

You have to use radio 1.65.24.36.

Working fine for me, with touchscreen & keypad mapped like this

Radio not working.

Download HERE:

http://www.megaupload.com/?d=BR6GHMXR
[Tilt, TyTN II, MDA Vario III Android Development] ddfire:
and from where i get android 1.0?

thanks

David
[Tilt, TyTN II, MDA Vario III Android Development] disturbed4686:
really dude, look right above your post
[Tilt, TyTN II, MDA Vario III Android Development] ddfire:
in that zip isnt any android.bin or anything like it...

what i should put in defalut.txt to boot android?

thanks
[Tilt, TyTN II, MDA Vario III Android Development] astrocrep:
You dont need that file... inside the rar is the data and system.img files... everything for android is in there.

-Rich
[Tilt, TyTN II, MDA Vario III Android Development] djmp89:
it doesnt have the system or data files its only 2.33 mb.

I think we could really do with updating that first post with a guide and updated links. xmoo isnt working on it anymore though so a moderator would have to change it or start a new thread?

the system and data files are further back, just read backwards through the posts dude its not hard really!
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
*this post is full of somewhat useless information, only meant for devs, and anyone hving issues running with the files posted above, i am not responsible for you wasting your time reading this post... youve been warned... :P*

Hmm, for some reason, they keypad has decided to stop working when i boot with WIFI on. It boots into the locked screen, and is not frozen as the clock keeps running. But another odd thing to note is the signal/operator. when I had wifi on and used listen for connections, android found a signal named android as an operator instead of showing the usual no service, and the signal icon also change to reflect the new found something.

Addition: as im writing this post im testing a bit more, it seems since then, the front keypad is no longer mapped correctly or at all, no files have changed since the initial working boot.

Edit1: resetting with the sound and wifi off seems to have been a fix. I am going to try and see if it was a random thing or if it always does this.

Edit 2: booting back in with wifi enabled and listen for connections on, the keypad again does nothing Not even lights up. and the 'android' service provider is there again..

It could be another random fluke because of the unstableness of it all, but after turning wifi off again and not using the listen for connections, the new android service provider is still there and keys are still not working...

The next restart got rid of the android provider in favorof no service again, and the keypad still does not work, (although im sure it will work next time it reboots)

Edit 3: It seems as if having an active data connection is the problem, every time the keypad was not working, there was no data connection (runing 3g at the moment too) and now that I boot with both an active connection, wifi and listen for connections, it seems to be working just fine....
[Tilt, TyTN II, MDA Vario III Android Development] milas:
There is already a wiki at xda and I put up one a couple months ago at www.androidonhtc.com but they have both been neglected. Feel free to read through the post and fill them out, nobody else has had the time or patience to do so yet.

However, at the current stage a wiki really isn't that useful - the developers are doing most of their work in private and communicating over IRC, etc.

We hoped before the wiki would solve the incessant stupid questions from everyone who vehemently refuses to read two posts above them or think at all, but even after putting it up where it clearly answered all the constant questions, people still refused to read it.

Really the best thing would be for people to stop posting questions that just waste everyone's time in this thread.
[Tilt, TyTN II, MDA Vario III Android Development] echofloripa:
I don't agree. If we had someone which is active part of the development with access to the first post, it could at least keep the status on the thread name and a very short description of how well are the latest image, and a link to it. Oh man, this alone would stop 90% of the thread traffic. Then, when time allows to the thinking heads, we get a wiki with more detail, how to build, known bugs, tasks, etc...

It seems xmmo is not around anymore, although in his profile it tell his last activity was today, maybe he moved on to another device? In any case is it possible to transfer ownership of the thread to someone else? If this can't be done, so I think the best is to create another thread, by someone that is willing in updating it regularly. Is it possible to share a thread edit permission with more than one person?
[Tilt, TyTN II, MDA Vario III Android Development] tilttheworld:
Got it to boot. Nice work. Am using the official htc / att windows mobile 6.1 rom and radio 1.65.24.36

I noticed during boot up it says 'old radio : Audio disabled'

Why is it we have to use this radio only?

Keyboard is working, but no backlight, and no fn symbols are ever typed. Still, great work. Its times like this that i wish i could help out in the development, but i only know a tiny bit of python.
[Tilt, TyTN II, MDA Vario III Android Development] mullins07:
The attached zImage includes most parts of Dzo's latest commit.

He has fixed the keypad shift, caps lock and function keys.

The phone also powers down if idle and will have to be soft reset.

I have improved the touch screen a bit too.

Dzo: I will continue to focus on the touch screen accuracy for the moment if that's OK.
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
OK, I still can't get the smd driver to work, whenever it reads from smem it crashes AMSS. I've just pushed some more stuff, I ported the sd driver from the latest kernel and pio mode works now. This may let it work with other radios (haven't tried yet though).
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
I booted the kernel with the previous commit (the one before the SD update) on kaiser and used rootfilesystem on SD. I got no errors but didn't move a lot of data. I still have the uptodate 1.7* radio.

ok with the same kernel (only removed the kaiser gpio printks) and radio I wrote some data to the card (used 'cat /dev/zero > /file'). first I canceled after about 20M with no errors. then I wrote to a second file and it dma-errored after a filesize of 12M. I will git-pull now and try out the pio mode with the same radio.

dzo: btw you removed the audioparams.c and the kernel doesn't build for me without that

did try booting form sd with the pio kernel and it doesn't seem to work: (still same 1.7.* radio)

Slot eject status = 0

Power save f eature enable = 1

PIO transfer enabled

Polling status mode enabled

Waiting 15 secs before mounting root (added root delay because I thought driver wasn't ready on mountiong rootfs from sd. but it makes no difference)

Command timeout

Command timeout

Command timeout

Command timeout

SD Init

mmc_sd_init_card: Delay 250 ms

clk_set_rate 21:50000000

host does not support reading read-only switch.assuming write-enable.

SD Init retry

new high speed SDHC card at address efe4

mmcblk0: mmc0: efe4 SD04g 3870720KiB

mmcblk0: p1 p2

EXT2-fs warning: mounting unchecked fs, running e2fsck is recoomended

VFS: Mounted root (ext2 filesystem).

Freeing init memory: 96K

<freeze>

I just tried the same with these params added to cmdline: "msm_sdcc.msmsdcc_pwrsave=1 msm_sdcc.msmsdcc_fmax=20000000"

same freeze on boot

ok I flashed the 1.65.24.36 radio version and tested SD with the non-PIO kernel. I copied some 60M files around on the ext2 / and got no DMA errors.

__________________________________

conclusion:

1.7 radio and non-PIO kernel: DMA problems

1.7 radio and PIO kernel: sd initializes but doesn't seem to work - can't boot from / on sd, even with 15 seconds rootdelay

1.65.24.36 and non-PIO kernel: no DMA problems - can copy 60M files with no errors.

1.65.24.36 and PIO kernel: sd initializes but doesn't seem to work - can't boot from / on sd, even with 15 seconds rootdelay
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
I cant seem to get the keypad to work in the latest version zimage. Is it the same setup as the last on mapping?

Edit: If I just re-read the post a bit better, they are actually not mapped at all. I seriously do miss some things when I read it on a small screen.... lol
[Tilt, TyTN II, MDA Vario III Android Development] rockerrock:
Hell yes! Get this working please! I don't have any cash to donate but I got plenty of food and wine to donate if you need it :D
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
I'll donate my left shoe, its a bit old, smelly, and dirty but id go shoeless just for Android! lol :D
[Tilt, TyTN II, MDA Vario III Android Development] d3sm0nd:
I downloaded the rar's provided and still can't get it to boot.

In the root of my storage I have:

DATA.IMG

DEFAULT.TXT

HARET.EXE

INITRD.GZ

SYSTEM.IMG

zImage.bin (latest from mullins07)

Content of default.txt:

I receive this error:
[Tilt, TyTN II, MDA Vario III Android Development] lyka:
sorry

if you refer to the rar i uploaded in few pages back, i'm sorry it was a bad rar, i forgot a couple of file.

uploading right now.

edit:

Keep in mind that developers suggest to use radio 1.65.24.36

This is how it works for me:

extract the following to the ROOT of sd card

- android(folder that include haret.exe, default.txt, initrd.gz, zImage.bin *version posted on post number #1924 10 01 2009by mullins07*)

- data.img

- system.img

all credits to developers.

http://www.megaupload.com/?d=BR6GHMXR

p.s when a new zImage is posted, just overwrite the one in android folder with the new one.

Let's try to make this thread clean and with less double question as possible ;) this is the way users help developers.
[Tilt, TyTN II, MDA Vario III Android Development] nato2k:
just to make sure im not a complete idiot. the radio isnt working on the kaiser yet right? I'm getting no service in Android.

overall great work though, i enjoyed reading through the progress.
[Tilt, TyTN II, MDA Vario III Android Development] biscuits1978:
As far as I know, there is no consistently working radio. The radio version that consistently works for now (check my sig) does not allow any connection to work, phone or internet.

This may have been asked before, but is there a working method to get WiFi to work or is this a work in progress as well?

BTW, thoroughly impressed with the progress from everybody. Wished I had more experience in this stuff so I could contribute, but I'll be glad to test! I do software QA testing for a telecom company, so I'm pretty experienced in QA/UAT in software and processes.
[Tilt, TyTN II, MDA Vario III Android Development] nato2k:
Thanks! I am running 1.65.24.36. I was pretty sure it wasnt working, but reading through some of the posts/readme's elsewhere it sounded like it might be working.
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
shhh! its too loud in here! (where is everyone? xD)

Anyway, out of pure boredom, I figured out one thing, and got totally lost on another.

First off, for those of you (if any as I might be the only one with the issue) that are having problems with the front keypad only working sometimes and not always, I have found that making a data connection (going into IE and going to any web page) before booting seems to remedy the issue most of the time.

And I just can't install apps yet from .apk's ... :D
[Tilt, TyTN II, MDA Vario III Android Development] predo:
honestly, who ever ports this to be a usable system on Kaiser will be the king! just had a go at this last release and it looks awesome although not too much that can be done but still animations and response is quicker then windows... I wonder if it will ever happen that this system will be fully ported to kaiser, what you guys reckon ?
[Tilt, TyTN II, MDA Vario III Android Development] flea_hamdani:
mounting /dev/block/blk0p1 on /sdcard failed: invalid argument

failed

failed to mount SD card

/bin/sh cant access tty; job control turn off

is there any step that i miss? please help thx
[Tilt, TyTN II, MDA Vario III Android Development] Completenutter2:
I followed the instructions listed in this post. It booted for me.

What an awesome achievement. Thanks everyone.
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
Hmm, before I thought it was just something being touchy, or not enabled, or based current cycle of the moon, but android boots every time for me, the problem is, im always stuck at the "press menu to unlock" screen because the front keypad just seems to do nothing at all. Now using no modified files at all, it works every now and then, about 20% of the times ive booted. And a different (original zimage in the 1.0 pack) does the same. Ive had the most success when there is an active data connection, but not always.

Anyone else having similiar issues? or am I just special? :P
[Tilt, TyTN II, MDA Vario III Android Development] gleonard3:
The "IE Button" gets me by that lock screen every time. Boots 100% of the time. Fun to look at, but touch screen needs calibration. And without a data connection there's only so much fun you can have.
[Tilt, TyTN II, MDA Vario III Android Development] JM33:
testing results

I am getting it to boot 100% of the time also. Keypad is working every time as well. Shadowline - you must be special :)

I noticed an issue with the touch screen that is not limited to android. In the fingerpaint under API demos, of course I can see the alignment is off. However, sometimes when I drag a line across the screen, or even just making a dot, it will draw a line straight down to the bottom of the screen. I have also had this happen on pocket painter, on WM. Other paint programs (VSpainter/Photogenics) don't seem to do this.

Do you think this is an issue with the HTC touchscreen, or mmy phone specifically? I know its early in the development, but do you think it will get better with android?

Also, just wanted to say thanks for everyone's work on this. Can't wait to make a call on android!
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
I think my phone is just weird... It only doesn't work when im home? o.0 It hates me.... lol
[Tilt, TyTN II, MDA Vario III Android Development] Epicardium:
Boots 100% of the time. I can make and receive calls. I can compose text messages as well, but they don't reach their destination...so I guess they're not really sending. All-in-all, the progress is encouraging!

EDIT - false alarm. Had an old Zimage loaded up still. Can't even boot with the newest one.
[Tilt, TyTN II, MDA Vario III Android Development] Rash1981:
First off:Awesome work on android! Many thanks to the devs!

Loved seeing andriod 0.8 work on the kaiser and can't wait to try 1.0.

One minor setback though...

The linux bootkit seems to have trouble mounting my sd card.

I get the following error:

mount: mounting /dev/block/mmcb1k0p1 on /sdcard failed: no such device or adress.

I'm using the recommended radio, and using Mullin's package on a Dutch T-mobile vario III edition of the kaiser. My WM version is 6.1 (HyperDragon III distro)

Should i format the card to ext3 or am i just missing something?

Any tips/tricks/hints?
[Tilt, TyTN II, MDA Vario III Android Development] jinth0688:
can you post a link to the radio you used?
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
Sounds like 0.8 to me... 1.0 has an issue with the messaging app as it needs the keyboard to slide out, and it doesnt seem to notice when it actually is... So no messaging, and without a proper fixed zimage, no calls either.
[Tilt, TyTN II, MDA Vario III Android Development] Epicardium:
You're probably right on the version. I'll double check. I assumed it was the latest because I downloaded it from the link just a few posts back, but that download may have included an older Zimage file. Downloading the latest Zimage now, and will update my post if necessary. Sorry if I've caused any undue excitement or confusion.
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
Speaking of versions, the new SDK seems to have a different version than we are running... Where is the source of the android system files we have? the source code? g1? or sdk?

Oh and side note on my "special" issues with booting... Turning all data connections off prior to booting seems to do the trick... Or just load in a HSDPA area... lol

Edit: and every time I say that it stops working again... >_> I swear it hates me... :P
[Tilt, TyTN II, MDA Vario III Android Development] stringbean82:
Hi all,

Been following the Android topic for a while now, and yesterday I started testing it myself on the phone and it runs directly, am impressed how fast it performs.

My Kaiser is running AthineOS 3.1 and Radio 1.65.24.36

No network service

No keyboard functionallity

The reason am responding now is because I want to contribute in getting Android on Kaiser. Let me know how I can help :D