yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] jim256:
EXCELLENT... :)

Thank you sir! Itching to ditch wm! (only thing I'll miss is pocketcm keyboard)

Jim
[Touch HD Windows Mobile ROM Development] daniel.hunt:
*twitches*

I'm excited now ;)
[Touch HD Windows Mobile ROM Development] CutePinkSox:
Slightly off topic but hey!

This was an interesting read... http://www.slashgear.com/android-running-on-eee-pc-1000-netbook-0228541/

Note the bit it about it taking 4 hours and the part about screen res.

EDIT FAQ - http://venturebeat.com/2009/01/02/an-faq-about-those-android-netbooks/ mentions framebuffer... you guys know all this but thought you might want to read it
[Touch HD Windows Mobile ROM Development] orux:
does anyone know how we can download this "user guide":

高通MSM6280+User+Guide.pdf

http://www.52rd.com/bbs/Dispbbs.asp?BoardID=144&ID=129430

It is related to msm6280 processor, but it has a lot in common (mddi, mdp, ...) with msm7201a processor.
[Touch HD Windows Mobile ROM Development] avimak:
[02:12 - Israeli time] I'm downloading the file right now...

[02:17 - Israeli time] and now I'm uploading it to megaupload...

Enjoy :)

http://www.megaupload.com/?d=B83EKN1T
[Touch HD Windows Mobile ROM Development] Lox_Dev:
I have try the latest files (TMP folder on storage card)

Is "Storage Card" hard coded? Because I have a french Blackstone and "Storage card" is "Carte de stockage".

As it, my Blackstone hangs at the end of the progress bar
[Touch HD Windows Mobile ROM Development] jim256:
EDIT: Wrong thread sorry.
[Touch HD Windows Mobile ROM Development] daniel.hunt:
I think we've established by now that this isn't the problem :)
[Touch HD Windows Mobile ROM Development] jim256:
Oh gosh oops sorry guys, I thought I was posting in a different topic / thread... :S embarrassing.
[Touch HD Windows Mobile ROM Development] Bongo2k:
7 more days and I get my Touch HD :D...hopefully.
[Touch HD Windows Mobile ROM Development] xmoo:
Damnn the intermship takkes a lot of time. Usualy i'm off from my apartment from 8 and cming back home around 10 :(
[Touch HD Windows Mobile ROM Development] apokryphus:
Take a look in here: http://xdaforums.com/showthread.php?t=431329

It referes to the omnia, but due to it has a similar resolution it could be helpful...
[Touch HD Windows Mobile ROM Development] BigDaemon:
what i think is very strange (ok, i don´t understand much about the hardware of the PPCs...) is, that the only device i know that has that much display-problems is the touch HD. The Vogue worked as first device, now even the Samsumg Omnia works, X1 works....but not the display of our Blackstone...why??
[Touch HD Windows Mobile ROM Development] orux:
Perhaps this is blackstone problem:

"Tearing or drawing effects will result if the frame buffer write pointer gets ahead of the read

pointer. In order to prevent this, the MDP tracks the LCD’s frame buffer write pointer (via

LCD_VSYNC and SST). MDP can throttle writes to the frame buffer so that updates occur

only when safe. To ensure correct operation, it is important to verify that the frame buffer

update rate is longer than one refresh cycle (to prevent the write pointer getting ahead of the

read pointer) and shorter than two refresh cycles (to prevent tearing). In addition, the frame

buffer update has to be synchronized with the read pointer."
[Touch HD Windows Mobile ROM Development] patp:
So this relates to a similar processor to the one in the Blackstone? It certainly sounds consistent with the output. Are there timing parameters you can adjust in the framebuffer code, or does this entail a whole new approach?

Here's a wacky thought? Could it be that your slow workaround to the rgb problem is actualy working because it accidentally adjusts the timing, preventing the write buffer getting ahead. Probably not the case, but vaguely possible I guess!
[Touch HD Windows Mobile ROM Development] davideuck:
I've seen a video of android working on Toshiba G900(WVGA), too!
[Touch HD Windows Mobile ROM Development] Rewpparo:
I've been mangling with the htc framebuffer console for two days now on my blackstone, and I think I understood two things. First, this is the file responsible for drawing the console at early stages. Second, the file is totaly self contained, and only calls for DMA functions, and bypasses all MDDI and stuff. So changing mddi parameters, for example in htc_fb, won't change the output of the console.

However I can't make any sense of why the shearing is happening. I read a report saying that the screen may be 262k colors, that would be 666 with 18 bits per pixel. I tried to compensate, but it didn't work, I always get that shearing. I tried many bits per pixel without success. But I always get some artifacts on my screen. It's been suggested that screen clock may be a cause, I'll see what I can find.

But I definitely think the problem is in htc_fb_console.c

Orux, if you still have a diff of that hack of yours, I'd love to see it.
[Touch HD Windows Mobile ROM Development] orux:
What I know about mddi and mdp:

Lcd understands rgb666 format only.

Linux and Wince framebuffer is in rgb565 format.

You can send a framebuffer to the lcd using two ways:

fb-->mddi interface. This works (more or less) but you need to convert fb stream in rgb666 format. rgb565 to rgb666 is time and processor expensive (by software). If the display is updated 60/sec, the processor has to convert and rewrite 800*480*2*60 bytes/sec. It gets crazy!!

fb-->mdp. Mdp (mobile display processor) can convert (by hardware) rgb565 to rgb666. After that, the stream is sent to the lcd through mddi interface. This process is easy, few instructions per refresh. This is the correct way. Mdp works fine in raphael and diamond, but not in blackstone.

There is a sync problem using mdp, and the linux framebuffer arrives wrong to lcd controler.

But mdp is complex, and has a lot of undocumented registers. May be the solution is a simple flag, or an instruction to the lcd controler....
[Touch HD Windows Mobile ROM Development] orux:
Ok,

1º you need a kernel from: git://git.linuxtogo.org/home/groups/mobile-linux/kernel.git

2º change to branch htc-msm-2.6.25

3º apply black-orux-020209.diff. This is the start point.

4º apply black-orux-040209.diff. If you want see my hack.
[Touch HD Windows Mobile ROM Development] Rewpparo:
thx that helped a lot. I'll see what I can make of it
[Touch HD Windows Mobile ROM Development] Rewpparo:
if I understand correcly your code, you've bypassed mdp by redirecting all calls to mddi, and added a correction for bpp before sending it down mddi link. Quite a feat !

by the way I booted android thanks to your code :) colors are messed up (too much red I think) and I get a frame every two seconds, but it works:)

however, I don't quite understand where you're getting at. I see you've changed mddi initialisation code. Is that part of your hack or is that a step towards getting mdp to work ?

All this is way out of my league, but I've learned so much in the past few days that I can't stop here. I'd love to help you out in whatever lead you're following. Where do you think is a possible fix that would get mdp to work ? what can I do to help ? I can't wait to get this screen to work.
[Touch HD Windows Mobile ROM Development] orux:
Yes;

That initialization code is the code used by spl to initialize blackstone mddi interface. It depends on lcd controler. There are different controlers; this is the init code that (I think) blackstone needs, because the original code in git linuxtogo is not for epson blackstone controler.

Spl does not initialize mdp, because does not use it. Mdp init is done by wince dlls. There are many dlls that work with display: DDI.dll, disptools.dll, GXDMA.dll, ...

The problem is that spl is easy to trace, but not that complex dlls.

I am working with those dlls, looking for the way that wince uses. But it is very dificult, because there are a lot of dependences with other dlls, threads, deferred tasks,....

What we can do?

-Wait for an Android device with the same hardware ¿G2?

-Play with mddi and mdp, in wince and linux, looking for a 'happy idea'.

-Look for good documentation about this hardware.

-Start working with htc-msm-2.6.27 branch.

-Ask htc for a driver.

-...We acept suggestions :)
[Touch HD Windows Mobile ROM Development] Ryu Kenshin:
Hijack Qualcomm server for documents, aim a gun at HTC dev staff for a driver, ... :D
[Touch HD Windows Mobile ROM Development] Rewpparo:
what I've been doing in the past few days is turning every stone I can think of, hoping to find the grail beneath it. But I have a hard time breaking the thing, let alone fix it. I think I tried changing most of the dma flags in htc_fb_console, but couldn't get it to work. do we have a clear idea of why the screen isn't working ? is the controler different ? is it because of the 800 height ? what parts of the linux kernel are concerned ?
[Touch HD Windows Mobile ROM Development] Rewpparo:
question : did you try to ask qualcomm nicely ? they work with google on the linux kernel, and they do release gpl code. they just might send you the docs you need, after all we're doing a job they may have to do someday.

http://www.qualcomm.com/contact/index.html

I think it's worth a try. I can do it if you tell me exacly what you need
[Touch HD Windows Mobile ROM Development] sudo_x60s:
Yip, contacting Qualcomm is worth a try.

Bwt, are u from finland Rewpparo? :)
[Touch HD Windows Mobile ROM Development] Rewpparo:
nope I'm french, why ?
[Touch HD Windows Mobile ROM Development] Thegn:
Hi,

Have anyone talked to the talented people at IRC channel htc-linux? I often check this page: http://irclog.iclem.net/?chan=htc-linux, to see where they are in the development. Unfortunately they rarely mention the Blackstone.

I'm not a programmer, so I'm of no good use :o. But since we have good and talented programmers on this thread, maybe talking to the people at htc-linux and ask them for some help, can pave the road for us HD users? Asking can't hurt? If some programmers could join that channel and get active there, it might drive the interest for getting Android working on the HD forward.

The screen is working on many different devices, so I do think that it could work on the HD too, without to much hassle. But again, I'm not a programmer, so what do I know??? :-)

Anyway, thank you all for keeping trying!

Have a nice weekend, everyone!
[Touch HD Windows Mobile ROM Development] patp:
Regarding the code to initialise the MDP, what I don't understand is why we can't get that from the G1 code, doesn't it have the same MDP?
[Touch HD Windows Mobile ROM Development] Rewpparo:
we're using the android code, but blackstone isn't exacly dream, and we're trying to compensate
[Touch HD Windows Mobile ROM Development] jim256:
I have sort of been thinking the same thing.

I doubt that they will give it to us, despite it possibly making their job easier, but who knows....miracle's do happen sometimes, and it just might happen. Which of course would be excellent.

That irc channel could be a GREAT thing too!

Thanks everyone!

Jim.
[Touch HD Windows Mobile ROM Development] xmoo:
I'm trying to follow this thread as fast as I can.

But there is a whole qualcomm document leaked about the MSM7200 and the 7201. I don't have it, I also do not know where to get it. But I know it is somewere on the web!
[Touch HD Windows Mobile ROM Development] sudo_x60s:
Ah, ok, sry! I have a friend that writes exactly like you and your nick name reminds me of his surname.
[Touch HD Windows Mobile ROM Development] JanSchotsmans:
xmoo: any idea why it keeps Haret keeps hanging after the green bar fills for so many of us?

I'm always getting that, eventhough I tried several roms.

Could it depend on the radio we use?

What radio version do you use?
[Touch HD Windows Mobile ROM Development] avimak:
I already upload the msm6280 documentation:

http://xdaforums.com/showpost.php?p=3300911&postcount=323

for msm7200 i found this:

http://bbs.cnttr.com/redirect.php?tid=193908&goto=lastpost

but it cost money to download the file (40$ for 40 MB! WTF!?).

I'm trying to find it for free on the web. the only problem is that it probably will be in chinese and it takes much more time to find...

Hold your fingers for me :)
[Touch HD Windows Mobile ROM Development] frottage:
if we could get it would the code from this be closer to the blackstone ?
[Touch HD Windows Mobile ROM Development] frottage:
looks like the document reference is "80-VA736-2"
[Touch HD Windows Mobile ROM Development] heatsha:
No thats not Android thats only Home Edition Android thats mean thats the UI from Android based on Symbian !!! Look in web for more info!!

But the real Android G2 thats could be the same licke blackstone!!

http://www.androidauthority.com/index.php/2009/01/21/htc-sapphire-t-mobiles-g2-spotted-in-the-wild/

http://phonereport.info/tag/htc-dream-2/
[Touch HD Windows Mobile ROM Development] xmoo:
Check my signature.

Everything is the same but I have a other rom now, can't tell you wich one. It has to release.
[Touch HD Windows Mobile ROM Development] avimak:
Yeah. I already saw that :)

but it's not helping to know the chapter name...

as deep as i dug google, i'm afraid to say that it's impossible for me to find the doc for the msm 7k family :(

The only thing I've found is that site i already mantion two posts ago:

http://bbs.cnttr.com/redirect.php?tid=193908&goto=lastpost

It's the doc of msm7200 but it cost money to download the file.

maybe chinese user of xda-dev can help to find a way to download it free?

xmoo, i did everything i can :cool:
[Touch HD Windows Mobile ROM Development] frottage:
How crucial is this file to the development of Android on Blackstone ? if its the crucial link - I certainly wouldnt mind buying it or at least contributing
[Touch HD Windows Mobile ROM Development] frottage:
seems the diamond guys are also looking for the same document http://xdaforums.com/showthread.php?t=402002&page=29
[Touch HD Windows Mobile ROM Development] JanSchotsmans:
Only difference I see between yours previously and mine is that I'm running the WWE version of Dutty's 1.7

On the hardware side I doubt there is any difference either since mine is belgium bought and yours most likely netherlands bought.
[Touch HD Windows Mobile ROM Development] Skallgrim:
Hi im new to this thread so im not updated on how the project is going.

I just wanna ask how it is going with making Android work on Touch HD?

maby you know when it will work?
[Touch HD Windows Mobile ROM Development] Bongo2k:
Currently there are problems with accessing the display correctly, it works but its kinda buggy. Once the display issue is fixed the project can move forward
[Touch HD Windows Mobile ROM Development] Skallgrim:
aah ok, thanks :)
[Touch HD Windows Mobile ROM Development] dedafmonteur:
Hey guys,

I just got a htc touch hd and i would like android pretty bad.

is it stable enough to use it?

and will it need to be booted every time i start my htc hd?

thanks and greetings from holland:)
[Touch HD Windows Mobile ROM Development] BigDaemon:
Oh come on guys, just read the last 2 or 3 Pages and you know whats going on here.....
[Touch HD Windows Mobile ROM Development] avimak:
I can't be more agree with you.

Guys, please, keep this thread clean as possible - just read/search the thread for the answers.

:D:D:D
[Touch HD Windows Mobile ROM Development] Cyclone_storm:
Your absolutly right, pfff getting tired of reading these posts. :D :D :D
[Touch HD Windows Mobile ROM Development] orux:
Hmmmm

We need to play with mddi and mdp clock rates.

If we use this value, display pattern changes.

#define MDDI_PMDH_CLK_RATE 128784000

//#define MDDI_PMDH_CLK_RATE 122880000
[Touch HD Windows Mobile ROM Development] BigDaemon:
Hmm, if i understand it right this is something like the "refresh-rate", isn´t it??

If so, this is what i suggested thousands of pages ago ;-)

Now have fun testing, i am currently stuck on the Haret-boot-problem :-(

Orux you use the files we can find on the first page?! If not, can you give us all your current files please so we can help you? ^^
[Touch HD Windows Mobile ROM Development] Mykstar:
I'm guessing that the clock rate needs to be increased as the sheering overflows onto the next line of the screen. If the screen is getting data from the frame buffer too late this is what will happen.. Anyone found any data sheets of the panel itself...

I've found this thread : http://wiki.xda-developers.com/index.php?pagename=RaphaelMDDI which indicates the LCD Controller is :

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

Here you can find the datasheet and Windows drivers for the LCD Controller itself... Not sure if this is any good but might be worth a look.
[Touch HD Windows Mobile ROM Development] daniel.hunt:
I've completely disabled TF3D because it just isn't nice. So I'm really looking forward to some progress with getting Android on my beloved device

Hey, that rhymes :D

If there's anything I can do to help out, just let me know.
[Touch HD Windows Mobile ROM Development] xmoo:
Keep on testing the files we give. To see if it boots on other phones.....
[Touch HD Windows Mobile ROM Development] daniel.hunt:
Well, unfortunately this isn't really an option for me. I'm one of the (very, very many) people who find that HaRet just stops doing whatever it's supposed to be doing once the progress bar reaches 100%

:(
[Touch HD Windows Mobile ROM Development] BigDaemon:
Very bad this problem, i have the same here.....

COULD it have something to do with Haret??

At the moment have to reinstall Linux on my Notebook (had to unsinstall it a few weeks ago :( ) and will compile the kernel myself just to look if it will work then, but i guess i know the answer right now....NO :-(

//edit\\ God damn it, my Notebook doesn´t like my Linux-Cd :-(

But after playing around a bit with my Blackstone i found 2 things: 1) In wiki you get a default.txt for Angstrom which says:

set MTYPE 2030

The one on page 1 says:

set MTYPE 1910

Which one is right and what exactly IS this number??

second thing:

With the angstrom-file "initrd-angstrom-usb.cpio.gz" until gogogo..., could it be that the root.cpio.gz is broken or something?? (Sorry if this questions are stupid, just getting into all that stuff slowly)
[Touch HD Windows Mobile ROM Development] orux:
Work with clocks it is not easy!!!

Something interesting (another place to play):

MDP_SYNC_CONFIG_0 (0xaa200000): 15:0-->This is the ratio of the core MDP clock frequency to LCD panel frequency divided by the no. of rows (lines) in the LCD panel. If the MDP clock is 133 MHz and the LCD is 176 lines (rows) at 60 Hz, then the value to be programmed is 133 * 10^6 / (60 * 176) = 12594

Some files that (more or less) work, with Angstrom dist: http://www.gigasize.com/get.php?d=xvd0wjym4fc

My pda is an "untouched" blackstone, recently hard reseted (frozen this weekend on mountains)

1.-unzip the folder in your sd

2.-Connect usb (activesync mode)

3.-Execute haret

There are two zImages inside:

zImage -->bad display; ssh connection works fine (see wiki).

zImage2 -->(change file name to execute this zImage). Wait 20 sec. to see first display output. Readable output, bad response.

Warning: Please note this is still in very early stages. If you don't know what you are doing...YOU WILL BRICK YOUR PHONE, we take no responsability. You've been warned.
[Touch HD Windows Mobile ROM Development] daniel.hunt:
I really do have to ask - can HaRet actually brick your phone?
[Touch HD Windows Mobile ROM Development] BigDaemon:
Haret not, but what the guys are doing here is "coding" Linux on a very very low level, so it could brick the phone if you for example send some wrong commands to the LCD, the display could be damaged or something like this ;-)

//edit\\ Okay, just tried the files of orux, nice work man, it works on my device :-)

Now i guess i know what the problem on most of the devices is that haret doesn´t boot: the zImage in the first post seems to be damaged. If i boot with the one(s) from orux it works, the one in the first post always freezes my device.....

Hope this will knowledge will help us a bit ;-) Even if it doesn´t solve the screen-issuse, it solves the "Haret-freeze"-problem :-)

If i can help in any way just say it. Sadly i don´t know that much about Linux kernel coding :-(
[Touch HD Windows Mobile ROM Development] ddhb:
Orux you are the best! zImage 2 works' fine on my phone.. no display issues at al!!!

Go on and test it with the real Android!

PS.: You're zImage is the first that boots on my phone and hangs not at 100percent ;)
[Touch HD Windows Mobile ROM Development] orux:
Haret probably not, but a bad kernel yes.

I have booted this files hundreds of times, with no problems. Nand is not enable in the kernel ....

I think those are safe files, but this is only a hobby, and I cant be responsible if some wrong happens.

I recommend all of you to compile your own kernels; there are a lot of documentation in wiki, and it is a interesting work.
[Touch HD Windows Mobile ROM Development] Turb0wned:
Im going to also try this out and see what happens.

Another thing, what makes you guys like Android better than wm? I played with a Google G1 and hated everything about it...
[Touch HD Windows Mobile ROM Development] Emblema:
Helo' people,

for me it same, android V1 not work(not boot), android V 0.8 boot whit very problem (blocked in start) for VGA maybe, angstrom not work (not boot).

Sorry my bad english, im' learning :)
[Touch HD Windows Mobile ROM Development] gaelynx:
Will do. However I don't have much experience editing a kernel, I'm game programmer professionally speaking... And it's 3am over here in Singapore, so for now it's time to sleep.
[Touch HD Windows Mobile ROM Development] xmoo:
Open source, all drivers included, no microsoft crap, many apps can be build (cause of opensource)
[Touch HD Windows Mobile ROM Development] loadme:
this thread isnt about comparing android to wm6

its about how to GET THE WHOLE THING WORKING, AS WE ALL WANT IT

keep it up

in one or two hours even me owns a touch hd and works with ya on this
[Touch HD Windows Mobile ROM Development] heatsha:
New video is aviable of Htc touch HD run Android !!!

It shows that the slide and mediaplayer work!!!

http://de.youtube.com/watch?v=tiDqjqUjpcU
[Touch HD Windows Mobile ROM Development] cybermaus:
Looks genuine. If you watch him move the second icon up and down, his hand jerks to the left. The icon, though with delay (bad driver probably) follows the jerk exactly.

Very promising. Audio even.
[Touch HD Windows Mobile ROM Development] xmoo:
The video does not look like a Touch HD, but more like a Movit Mini

http://www.engadget.com/2009/01/07/giiniis-movit-mini-wifi-android-tablet-hands-on/
[Touch HD Windows Mobile ROM Development] katolo:
It is an Touch HD... check the video again at 3:18 and you can see the buttons of the HTC phone.
[Touch HD Windows Mobile ROM Development] xmoo:
Ooh IC,

Hmz.....

Why don't he want to share it.......
[Touch HD Windows Mobile ROM Development] sumitescp:
There are more videos of the HD running Android from the same author on youtube.

This guy should share it coz sharing is caring.

I can imagine my BlackStone running Android. HAHA:):):)
[Touch HD Windows Mobile ROM Development] xmoo:
i've packed a new package.

Can someone try it?

http://www.xmoo.org/X1/linux/Android 1.0.rar
[Touch HD Windows Mobile ROM Development] El Massman:
still no different than previous images. just a blurred screen. thanks for the effort. it is much appreciated. keep up the good work.

marc
[Touch HD Windows Mobile ROM Development] daniel145:
nothing :(
[Touch HD Windows Mobile ROM Development] El Massman:
a second try while tapping the screen constantly got the same result but the device turned off afterwards. i'm guessing still framebuffer issues then?
[Touch HD Windows Mobile ROM Development] jim256:
is there anything more specific that you want us to test or anything?

I have been following this and just tested the latest one because I am DESPERATE to get android on blackstone and would love to know of any additional ways that I could help. (could fire up a linux box, but don't know much about programming and nothing at all about messing w/ kernels).