yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] stefh:
on ram booting now... looks a lot faster than on your video (probably because I increased the sd card read speed through advanced config)

edit:

using UK original rom: 1.14.401.3 (22273) WWE

Radio: 1.09.25.14

Got to the Android "desktop". Then I got the following message:

Sorry!

The application Maps (proces com.google.android.apps.maps) has stopped unexpectedly. Please try again.

And I had to take the battery out to get the phone to work again.

Man I am so excited about seeing Android coming :)

edit2:

Forgot to say thanks for all your hard work so far.

Second boot, I got the screen moving to the left and saw the google search bar.
[Touch HD Windows Mobile ROM Development] xmoo:
Ok so the file have been correctly uploaded now!
[Touch HD Windows Mobile ROM Development] monzablue16v:
Good progress :) getting there now :0)
[Touch HD Windows Mobile ROM Development] BigDaemon:
As i already mentioned, the next steps are now:

By the way, this works quiet well on my device, even if i have some white lines from top to bottom on the screen on android. also the touchscreen doesn´t respond on anything.

But i think whats most important now is that we can throw that "workaround" for the screen overboard and get it really working.

Touchscreen and all those stuff can be done if we have a stable and quick-refreshing picture/console on the screen :-)
[Touch HD Windows Mobile ROM Development] degake:
Xmoo,

How did you manage to get Touchflo working in landscape?? It looks nice :D

Keep up the good work mate!!

Goed bezig ;)

Grtz,

Degake
[Touch HD Windows Mobile ROM Development] *_Touch_HD_*:
the goal is almost reached

Android on Touch HD without WinMo possible?
[Touch HD Windows Mobile ROM Development] michi6787:
drivers/rtc/hctosys.c: unable to open rtc dev ice (rtc0)

What now?
[Touch HD Windows Mobile ROM Development] xmoo:
It's the new rom by Dutty.

Will release soon!
[Touch HD Windows Mobile ROM Development] xmoo:
Try again.

Also uploaded to off ram version!
[Touch HD Windows Mobile ROM Development] degake:
If you had some free time, could you help Dutty to translate it into Dutch? :D

Grtz,

Degake
[Touch HD Windows Mobile ROM Development] cobrawnl:
lol... why dont help dutty by yourself??! :P
[Touch HD Windows Mobile ROM Development] xmoo:
Will do,

But this is about android not dutty's roms.....

stay on topic.
[Touch HD Windows Mobile ROM Development] degake:
Sorry :o

Keep up the good work :)

We know you can work this out :D

Grtz,

Degake
[Touch HD Windows Mobile ROM Development] daniel.hunt:
As much as you're going to hate me for this - the progress bar is *still* stopping at 100% and going no further! :(

*edit* Ooooh, I lie! I lie!

It took about 30 seconds, but the loader appeared. I see a penguin!
[Touch HD Windows Mobile ROM Development] unclesomebody:
Out of interest, in the development of android on the other HTC devices, what has been the deployment time schedule from the point we are at now in this thread? I mean, what sort of timeframe are we looking at (using other HTC devices as a benchmark) before we have a functional build on android for our HD's?

Good luck!
[Touch HD Windows Mobile ROM Development] daniel.hunt:
This is the same message I see.

The loader is obviously working its magic, but it stops (I still see a vague penguin in the top left corner, the screen is black, with white/grey text on it showing me the progress), with this line being the last one on the screen.
[Touch HD Windows Mobile ROM Development] Cyclone_storm:
Wow guy's great job, 1 day of work and I see were about 8 pages further haha. :D :D :D
[Touch HD Windows Mobile ROM Development] Bongo2k:
http://ray.thorp.users.btopenworld.com/IMG_0137.JPG
[Touch HD Windows Mobile ROM Development] daniel.hunt:
You could at least have waited until the image was fully uploaded before you posted the url :)

*edit* but that's the exact same error I'm getting.
[Touch HD Windows Mobile ROM Development] daniel.hunt:
What on earth?! A second attempt and it worked?! Very strange.

The same error came up, but it somehow got past it this time.
[Touch HD Windows Mobile ROM Development] furrypotato:
I too was getting the same error. It happened twice.

Then I put the files in the device root directory and it boots into Android.

Keep up the good work guys !
[Touch HD Windows Mobile ROM Development] :
Yup.

This did the trick for me too. It boots into the (garbled) GUI now.

I tried the touchscreen, waited for a couple of minutes, but not getting any responses of it after I touched it.
[Touch HD Windows Mobile ROM Development] daniel.hunt:
I had to touch it 3 times I think. Then it went into the Android UI. It looked like poop, but it was Android :)

Also note that I did *NOT* have to move the files into the root of anything. The second time I ran HaRet it worked - the error still came up, but it got past it
[Touch HD Windows Mobile ROM Development] brumbrum:
Wow! This is very impressing! :-)

Any of you guys that have it booted: Is the radio working? Is it possible to make phonecalls and/or recive gprs/gsm-signals?

I wonder how long it will take before you are able to create a fully flashable android-system-image... This device is almost the same as G1, so I really hope it will be the first HTC device with a flashable Android-system (that is not G1). That would be really cool! When that is possible, I will convert my phone to android without even blink!

Because the files didn't work for me, I wait some more days before trying again. I really think you guys can make this work! If someone is able to do it, You are! :-)

Also, for the persons that got phones that this is able to boot on: What Rom and what Radio are you using?
[Touch HD Windows Mobile ROM Development] audscott:
I haven't been swong over to Android yet, but I support your wonderful efforts:

Paypal Confirmation number: 2PK06693A9627101A.

Keep up the good work!!
[Touch HD Windows Mobile ROM Development] furrypotato:
Once it's booted everything pretty much grinds to a halt. When I went to slide up the bottom menu slider it took about 30-60 seconds for it to do so. Then I went to click on an icon and it registered the click but then froze.

So it's far from usable yet, still some major screen issues I think. But the main point is that it boots that far. That makes fixing the screen issues a lot easier for those with the ability such as xmoo.

I',m using Daviduck 4.5 ROM on 1.09.25.14 Radio
[Touch HD Windows Mobile ROM Development] xmoo:
Thx you very much, added you on first page!
[Touch HD Windows Mobile ROM Development] xmoo:
Finaly!!!

Well sometimes when it does not load, boot again. Out of the 10 times Android boots like 8 times....

Check my signature, and I will check if the radio is working. In 0.8 the radio is working. I was able to get a call but not pick it up or hear any sound.
[Touch HD Windows Mobile ROM Development] JanSchotsmans:
Little question and possible theory about the boot failures quite a few are having.

What SD card are you using to boot from?

Mine is a Class 4 8GB card (Sandisk) while the one delivered with the Touch HD is a Class 2 8GB card. Thats the only difference I can find, since I did a fresh hard reset on my Dutty 1.7 rom yesterday to try to these new files.

I'm going to try and boot it from the built in ram of the phone, maybe that'll work.

Also xmoo, did you think about adding your tree to http://android.git.kernel.org/ you might attract some experienced developers that way.

Also I noticed some updates on the hardware/msm7k repository there, are you using that too or only the one from linuxtogo?

I'm also building Android for the Asus R2E tablet atm :)
[Touch HD Windows Mobile ROM Development] xmoo:
JanSchotsmans,

The kernell is not mine it's ornux his. I made a small change in it and also combinaed it with Android. All credit in this kernell goes to ornux.

I'm in Barcelona and don't have my Linux machine with me, will try to install Linux on vmware and try to do some extreme kernel creating here :P
[Touch HD Windows Mobile ROM Development] JanSchotsmans:
Oh, sorry I'm getting you 2 mixed up then :p

So Orux, those questions are for you :)

Hrm, actually, I don't think I did, you did create the display patch didn't you?
[Touch HD Windows Mobile ROM Development] *_Touch_HD_*:
Hi,

is Android on Touch HD without Windows Mobile possible?

A system in a system ist not the best solution.

:D:D please make a stand alone of Android :D:D

cheers
[Touch HD Windows Mobile ROM Development] xmoo:
Check this: http://pocketnow.com/index.php?a=portal_detail&t=news&id=6880

MY Youtube video is famous now cause of Manila landscape + new keyboard :P
[Touch HD Windows Mobile ROM Development] BigDaemon:
Come on, just read a bit. we had this question hundreds of times in here and the answer always was: Perhaps, IN VERY FAR future, it will PERHAPS be possible.

But at the moment we are even far away from getting android running with Haret.

We just need to solve the screen-issuse!
[Touch HD Windows Mobile ROM Development] patp:
It's good to hear you say that, because dumb readers like me got the impression you hadn't realised that. I'm glad to be proved wrong and I'm looking forward to seeing your diffs. Can you tell us what changes you made? Other than booting it with the Android file system.
[Touch HD Windows Mobile ROM Development] xmoo:
It is more a sctructure change, cause on the Xperia many ppl had the same problem not being able to boot android. Cause of a small structure change now many ppl are able to boot linux (and in most of the times also android).
[Touch HD Windows Mobile ROM Development] jim256:
Tried it w/ android 1.1? Just wondering if any sort of changes they've made would give us a magical strike of luck lol :S ?
[Touch HD Windows Mobile ROM Development] JanSchotsmans:
I think you better mark the thread title as "DEV" and post in your opening post in HUGE letters that this is a development thread.

People don't seem to understand that.

Anyway, tried booting from built-in storage, failed. Now going to try you In-Ram version on both SD and Built-in.

This is really getting on my nerves :p

I'm not much of a programmer, but when it comes to extending and patching and tweaking a partially working kernel and system I can honnestly say I'm Guru. But for that I need it to at least try and boot which up to now it hasn't done.

As for going from Haret boot to rom boot, I don't think that will be that much of an issue. There's plenty of people around here that know how the layout of a rom needs to be.

And if its possible to load a rom with the same bootloader and HardSPL as WinMO, loading and reloading linux roms won't be much of a problem even if they won't even start booting.

Anyway, I'm going to do another hard reset and try the in-ram version.
[Touch HD Windows Mobile ROM Development] patp:
great stuff. can you explain what the structure change was? or is it a secret?
[Touch HD Windows Mobile ROM Development] xmoo:
No it's actualy very easy, but it took like a week to know this.

On the Xperia developement, we went hard. In one week almost 60/70% of android was working. But not many ppl were able to run Linux, and if you cannor run linux, you cannot run Android.

I've founded out that when you rename the files and give a extension to it, haret will boot linux.

Zo zImage renamed to zImage.bin, als the other files with no extensions renamed it.

And as you can see everybody can boot Linux now.
[Touch HD Windows Mobile ROM Development] JanSchotsmans:
I got it to boot. After doing 1 simple thing I hadn't tried yet.

I Unplugged the phone from USB! So for anyone where it persistenly wouldn't boot, unplug USB and see what happens then. (I got the idea after rewatching Xmoo's latest video. Noticed he had it unplugged in there. The reason why I was alway plugged in is because thats a given when loading roms :p)

Some points to make.

The screen is readable but for lines where it does a line wrap there is still a 1 pixel wide error, it seems the first line of pixels of the new text line is put at the end of the line.

So if a line starts with a "t", the left - of the t is drawn at the end of the line while the rest of the t and all that follows is displayed at the beginning of the line.

Also, Xmoo, could you post your latest diff?
[Touch HD Windows Mobile ROM Development] xmoo:
There is no new one, still using the stock one.
[Touch HD Windows Mobile ROM Development] JanSchotsmans:
Ah OK.

Note about boot failures.

In-Ram now consistenly boots for me when placed in the root of SD or Built-In storage.

Out-Ram doesn't boot anywhere. The Haret progressbar loads rediculously fast (less then a second) and then stays there. While with the In-Ram version, it takes 5-6 seconds to load and then 15 seconds to show the dmesg output.

So for anyone still having these problems, use In-Ram version and put the 4 files in the root of your SD or Built-in Storage, with the USB cable disconnected from the phone it should boot OK.

I'm still mixing you and Orux up :p I was wondering if his Diff from 0402 was the latest or if this kernel has some new stuff in it.
[Touch HD Windows Mobile ROM Development] xmoo:
Well with Orux zImage the sd-card is not enable or it does not have the correct sd-card driver.

On-ram always works, cause it loads in on ram.....
[Touch HD Windows Mobile ROM Development] Emblema:
Hi xmoo, very compliment for your job, one question:

in the video you use a ram version o non-ram version, because in my touch HD (blackcook 1.8 rom) a off-ram version stopped in first screen whit Haret booting linux bar, on ram version after first screen (haret booting linux) stopped in next black screen whit white fonts (started linux screen it's similar)?

Thank you for job and share
[Touch HD Windows Mobile ROM Development] stefh:
I just put the android10 with its contents into my SD card root and run it from that folder and it just works fine. So probably it is not necessary to put all the files inside your root.

I was actually hoping miracles would happen today, that somebody came up with a simple screen fix and sweeping the Android wallpaper would already work smoothly ;)

But like I said I already saw the GOOGLE search bar, bij sweeping to the left.

I just can't believe because of the same hardware on almost every part, that it actually will take long to get everything working after finding a way to output properly to the HD's screen.

Just look at the chipsets by comparing the Touch HD with for instance the G1 on this website:

http://pdadb.net/index.php?m=pdacomparer

(Or they are really wrong about the specs or I am just too dumb to understand why there is actualy much difference)
[Touch HD Windows Mobile ROM Development] Bongo2k:
Remember that you are running Linux on top of windows mobile. You are bound to get performance issues and other anomalies. Unless someone fancies flashing their phone with this? ;D
[Touch HD Windows Mobile ROM Development] xmoo:
My video is showing the On-Ram boot.

It doesn't matter where u put the files. The files will boot on-ram.

The off-ram did actualy boot, also booted linux but at the part when it needed to mount Android from the sd-card, I got the rror that he could not find android (cause of Sd-Card not working).

Bongo2K I tought when booting linux, WM would be killed.

Look @ HTC TyTN II. It boots from WM but the preformances are still fast.

The Slow preformance is cause if the screen fix.

If you see a older video of my with the screen issue.

You will see that the colours are correct and android is preforming fast.

Als on this video I was booting off-ram.

http://www.youtube.com/watch?v=9zgC9vNrjIU
[Touch HD Windows Mobile ROM Development] Bongo2k:
Is the performance as fast as the G1?
[Touch HD Windows Mobile ROM Development] xmoo:
I havn't had a G1. So don't know.

And what kinda preformance are you talking about??
[Touch HD Windows Mobile ROM Development] patp:
OK, got a boot. I don't want Android gui right now, just console. I am using:

compiled kernel, haret.exe and default.txt from Orux:

http://xdaforums.com/showpost.php?p=3269320&postcount=290

plus a minimal initrd from:

http://members.upc.nl/m.hoek9/initrd.droid.cpio.gz

(actually part of the Raph linux dev project on: http://wiki.xda-developers.com/index.php?pagename=RaphaelLinux

With these 4 files in the root folder of my device (not SD) it boots to a console, I can calibrate the screen and enter commands (only tried ls so far, it works OK). the calibration is a bummer though, you can't see where the reference dots are.

xmoo, I have no idea why you had to put .bin on the end of the zImage file. It makes no difference. In my opinion, there has been no significant development here since Orux figured out the screen kludge. This thread is utterly full of chaff and if i were a developer I would want to start a new one expressly to talk about the real business of getting this project working.
[Touch HD Windows Mobile ROM Development] daniel.hunt:
It allows my (and others') device to boot the images from HaRet, without the app stalling once it reaches 100%. Why this is, I don't know. But it works.
[Touch HD Windows Mobile ROM Development] orux:
Hello people;

We are NOT running Linux on top of windows mobile. Linux replaces Winmo in RAM.

A pda is not only a processor + memory; there are a lot of chips and controlers. Install ati graphic drivers in your pc with nvidia graphic card (or vice versa) and tell me what happens.

You are running android over an experimental zImage. This kernel uses ~90% of processor power drawing the screen. It was only an experiment and I'm not going to work on it never again.

We need to found a definitive solution.

Anyway; strange development team; thousands of testers, few developers ;)

Has someone take a look at epson docs and code?

http://vdc.epson.com/index.php?option=com_docman&task=cat_view&gid=278&Itemid=40

We need ORGANIZATION!!!

Is there outside anyone working with the kernel?

We need more eyes and hands. Skills:

1.-linux kernel, C, driver (better display driver) developers -->please, send me a PM

2.-ARM assembler -->please, send me a PM

3.-Winmo developers -->please, send me a PM

Again, sorry about the bad English; it is not my fault, it is my spanish adsl who loses some words :)
[Touch HD Windows Mobile ROM Development] patp:
All I can say is try the files linked in my last post. They work fine on my device.
[Touch HD Windows Mobile ROM Development] xmoo:
Same problem here bro.

As he already said. Some ppl have this problem. And this is a posible fix around it.
[Touch HD Windows Mobile ROM Development] JanSchotsmans:
Orux, now I've got Linux to boot I'll be doing kernel hacking and adding tools for device analysis to an initrd.

As I said before, I'm no programmer and can't write from scrap, I can however gather information, debug, hack, patch, rewrite and tweak the crap out of things.

As for what I'll be doing first:

1: USB HID for a keyboard, will speed things up considerably. That or working Bluetooth so I can tether a keyboard to my phone.

2: NAND

3: SD

4: Adding tools and utils to a developer Initrd. At this point, noone should even think about Android itself imho, the first thing to do is getting a spotless and perfect kernel going.

As for coordination and organisation, if you want I'll setup a site with all the needed developer coordination tools (GIT, Closed forum, bug tracker, documentation repo, etc, etc)
[Touch HD Windows Mobile ROM Development] gerdgerdgerd:
you could create a sourceforge projekt. so you can use cvs and bugtracking and so one. so wen can make our problem open source and hope that other skilled developer helps us.
[Touch HD Windows Mobile ROM Development] daniel.hunt:
CVS is complete and absolute muck ;) SVN ftw! :p
[Touch HD Windows Mobile ROM Development] patp:
4 Is absolutely right. Booting into a gui without working hardware is pointless. Would it also be useful to set it up so it accepts a net login over the USB? The Angstrom initrd on the wiki is meant to do that but I think the file might be corrupt. If you can ssh in the small screen and non-existent kbd is no problem.
[Touch HD Windows Mobile ROM Development] JanSchotsmans:
Angstrom Initrd works ok for me. Including USB Lan.

I still rather have a keyboard hooked up to it :p

As for version control, considering the core kernel dev and android dev is al done in Git, I don't see why we would use Subversion or (shrugs) cvs.
[Touch HD Windows Mobile ROM Development] orux:
There is a good repository in linuxtogo: http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=summary

We are using 99% code from there. We only need to convince them to add blackstone machine specific code. I think this wont be a problem.

The guys that are working there, for other devices (diamond and raph,...) are working for us too.

I recommend you to take a diary look at: http://irclog.iclem.net/?chan=htc-linux and collaborate in this channel

There is a lot of source code with epson drivers. It is written for Windows, but it is more readable than assembler code :)

Let me think about how we can organize (tomorrow, now I have work)
[Touch HD Windows Mobile ROM Development] patp:
Can you post me a link to the version you're using? Perhaps it won't boot for me cos I haven't got it connected to the PC (waiting for net?).
[Touch HD Windows Mobile ROM Development] JanSchotsmans:
I downloaded it again from the wiki this afternoon. Works fine for me.
[Touch HD Windows Mobile ROM Development] patp:
OK - working now; I had a bad download before.

It's not interactive on the device though; calibration not happening and it's hung at drivers/rtc/hctosys.c

The minimal one I linked to is actually usable on the device (but has practically nothing in it as it's meant to refer to Android on SD card). I was quite amazed the touchscreen worked and the onscreen kbd too.
[Touch HD Windows Mobile ROM Development] JanSchotsmans:
the hcto hang only happens once ever 4 or 5 boots for me.
[Touch HD Windows Mobile ROM Development] brumbrum:
Is the kernel-development in this project (Blackstone-Android-project that is) taken from this kernel-code: http://source.android.com/download ??

If not: Why?
[Touch HD Windows Mobile ROM Development] kylegordon:
Because Android isn't a kernel. Linux is a kernel, and Android is the userland interface that runs on top of it.

This is similar to how Ubuntu includes the GNU/Linux kernel, and then you get Bash, coreutils, Xorg, Gnome, etc all coming together to form a working system that we just know as 'Ubuntu'
[Touch HD Windows Mobile ROM Development] mallman:
doesnt boot for me on TL26_THDV7.5_WWE ROM. Tried both sets of files. Just an FYI
[Touch HD Windows Mobile ROM Development] xmoo:
Dit you tried a couple of times????
[Touch HD Windows Mobile ROM Development] mallman:
twice per set (on and off RAM) will try some more to see. was expecting a call so I had to stop for a minute lol. trying again in a sec
[Touch HD Windows Mobile ROM Development] xmoo:
Just try the on-ram. Off-ram doesn't work, we know that.
[Touch HD Windows Mobile ROM Development] mallman:
gotcha and yes it "booted" this time to the black screen where the text is (doesnt make it to calibration), hangs there. Going to try a few more times and see what happens. I moved the filed to my SD card and it worked. I see you say it has nothing to do with that but it worked for me nonetheless.

EDIT***

after 2 more tries it booted all the way to android but then appeard to hang. I know the touch screen is supposed to be really slow but couldnt get anything like your result in the video as far as android "working". I provide any real value I know :) just wanted to confirm it booting on another device with a different ROM.
[Touch HD Windows Mobile ROM Development] brumbrum:
Yeah, I know all this.

But I was refering to this: http://android.git.kernel.org/?p=kernel/common.git;a=summary

http://android.git.kernel.org/?p=ke...b;hb=462bfbff2e3b4e93b0509a48f8372f7dd3d17e0b

If the kernel-development for this project was going on there, it would be possible to get more developers. Maybe?