yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] maejrep:
No, my colors do not look normal with the git kernel, but your changes DO make it look normal! So what does that mean? We do have 3 different displays?

Also worth noting that current git doesn't boot on my phone anymore. I think I'm going to revert the df6bc3917c80b8e4e6d718d58e4ca227259a8408 patch for usb ether and see if that's the cause. The symptom is the same as others are reporting on the previous page, just hangs after the 4 STUB lines, no chance to calibrate.
[Touch Diamond, MDA Compact IV ROM Development] :
Sure would be nice if HTC, or Quallcomm was a little more forthcoming about there hardware. Talk about throwing a dog a bone... Open Handset Alliance? What alliance. lol.

The point to be made here, is that it's pretty sad that open source devs are going it alone when there is all this talk about the open source alliance, but regular joe's are having to do all the work.

Guess it just pisses me off, after having bought a few HTC phones. Everyone was pissed about the Kaiser not having proper video drivers, and again, where are these companies other than spouting off propaganda?

Sorry I have nothing positive to add here. Really wish there was something I could contribute.

Sincere thanks, for doing what the billion dollar companies can't spare a few dollars to do themselves.

-James
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
Great to hear... sounds like we got some neat progress here :D
[Touch Diamond, MDA Compact IV ROM Development] zonyl:
Unfortunately I dont have much time to help, however, I am excited about the efforts of getting Linux / X running and have money if that helps. Is there a specific link to donate to the group working on this (post on the Wiki page please)? If one cannot be organized, could those folks who are all contributing here put a donate link in their sigs? Thanks for all of your efforts!!
[Touch Diamond, MDA Compact IV ROM Development] dcordes:
That's interesting. I'm glad some more people tested it. I wonder why do some experience the freeze when X attempts to start and you get to the calibration screen. But I think it's not dependend on the mddi client because on the kaiser it sometimes draws one frame and then freezes, sometimes even freezes before it draws anything. On the other hand you are the only person who seem to get anything at all drawn to the fb by X. Did you ever get the black screen only without any cursor?

If you want to sort out it's not just the touchscreen driver not working, you can login and run Xfbdev manually, then run some application on it with 'DISPLAY=:1 pidgin' or so. Just remove the gpe-dm from init. Would also be interesting to see if druidu's ts driver works with tslib so you might also run tslib_test tslib_calibrate.
[Touch Diamond, MDA Compact IV ROM Development] skiwithpete:
Looks like the HTC touch is android-ed.

http://www.engadget.com/2008/12/10/video-android-rocking-on-the-htc-touch/
[Touch Diamond, MDA Compact IV ROM Development] kragil:
WANT!

Wow, super cool!

I want Android on my Diamond and I am willing to put my money where my mouth is.

I will pledge 10$ (for a bounty) to get Android running that well on the Diamond. Anyone willing to join in? If enough people join in we might get a decent sum together.
[Touch Diamond, MDA Compact IV ROM Development] Stebo85:
please guys i cant wait to have android because winmo just sux. been using it for 3 moths and its driving me "BLEEPing" crazy! im ready to pay an contribution for this.

keep me updated
[Touch Diamond, MDA Compact IV ROM Development] courtlandre:
It has been running pretty stable like this for over a month. WinMo is still better because it actually supports apps. Android on the vogue still has many problems and in my opinion is not in a usable state.
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Would also be willing to pay whatever it takes to get Android running properly on the Touch Pro :D Please let me know if there is anything I can do!

Keep up the great work!
[Touch Diamond, MDA Compact IV ROM Development] Mikey:
You are not on a playground.

Please watch your language.
[Touch Diamond, MDA Compact IV ROM Development] garuda50:
What a long treat yessurr!!! You guys are desperately convinced that u could make a HTC diamond run on Android?? Whuhahahahah don't make me laugh:mad:

Instead of wasting your time on your precious girl.. Guys or should i say d....

Use your heads! I know the truth comes very hard but please go work with google to make an real OS but U bunch of amateurs.

Please close this treat MODERATORS.. This is just cowsh.t...

:mad: Im not pleased to see a new reply that goes in the middle of nowhere.

Now people, if u have a mind and have the balls. We should stop this stupid threat. Think forward not with a bow. I know im right!!!:mad:

For shizzle!! Yessurr!!
[Touch Diamond, MDA Compact IV ROM Development] Mikey:
The next posting you make better be to someone that already posted or you will be placed in the time-out corner. :D

Got my drift??
[Touch Diamond, MDA Compact IV ROM Development] garuda50:
I just dont want people to donate them wannabe programmers and developers. Just because one silly man asked if its possible to make an google OS run on Diamond.

It's like if u ask.. Does Santa Claus really excist? No it don't excist but we make them excist.

Im for real people. PLEASE STOP this shizzle. Im really mad about the progressing here. I dont apreciate the work done here cause it leads to nowhere. PLEASE stop ok! Youre making other people desperate :rolleyes:
[Touch Diamond, MDA Compact IV ROM Development] garuda50:
You think you tough huh?!?! Come and meet me cowboy!!!:mad:
[Touch Diamond, MDA Compact IV ROM Development] Mikey:
These forums are open to open topics. Whether something is possible or eventually possible.

Are you so definite that Android wont be able to run on the Pro?
[Touch Diamond, MDA Compact IV ROM Development] badbrad4080:
LMao i can tell you know nothing about software mod that timeout would be good now and through ip give his other accounts timeout.
[Touch Diamond, MDA Compact IV ROM Development] Mikey:
in about 1 minute sign in with another account :D
[Touch Diamond, MDA Compact IV ROM Development] garuda50:
GIVE ME time out then, i have 4 other accounts brother. Yeah you know nuthin bout it bout naah mean... Go buy yourself a HTC g1 if u ask santa maybe he'll give u one!!!:D
[Touch Diamond, MDA Compact IV ROM Development] abovelegit:
Im pretty sure he can ban your IP adress just as easily.
[Touch Diamond, MDA Compact IV ROM Development] Mikey:
I have all his names :)

No need to ban them all. Maybe he has a different personality with each name he has. lol
[Touch Diamond, MDA Compact IV ROM Development] Kasaki:
Great going so far guys, iI quite developing stuff a while back but this looks like great progress. Now the issue with the cdma phones and the android os is? excuse if if the question has been asked. Also the android os never came with a virtual keyboard to begin with correct?
[Touch Diamond, MDA Compact IV ROM Development] muscleman7911:
Nice one!!

I come from no wer into this topic but its amusing,

I see it that this personality is just mad that Android is not on his diamond or raphael... yet..

LOL:D:D:D
[Touch Diamond, MDA Compact IV ROM Development] maejrep:
So going over that diff (http://git.linuxtogo.org/?p=groups/...ff;h=df6bc3917c80b8e4e6d718d58e4ca227259a8408), I found an issue that may have already been brought up or addressed, but from what I can tell, latest git is still wrong..

.ifc_class = 0x02,
#ifdef MACH_HTCRAPHAEL
.ifc_subclass = 0x00
#else
.ifc_subclass = 0x0a,
#endif
.ifc_protocol = 0x00,

If MACH_HTCRAPHAEL is set, you end up with:

.ifc_class = 0x02,
.ifc_subclass = 0x00
.ifc_protocol = 0x00,

Which is saying:

.ifc_class = 0x02,
.ifc_subclass = 0x00.ifc_protocol = 0x00,

That should probably be fixed in git. I was hoping that might be the reason for the hangs that we're seeing on the raph800, but even after fixing that, I still hang at the same spot. I'll try fresh and see if maybe I screwed something up at some point.
[Touch Diamond, MDA Compact IV ROM Development] Arktronic:
Shouldn't that kind of mistake have caused a compiler error? You wouldn't even be able to build an image then. Perhaps MACH_HTCRAPHAEL isn't being defined properly (if at all)?
[Touch Diamond, MDA Compact IV ROM Development] maejrep:
Indeed, you should get "error: request for member 'ifc_protocol' in something not a structure or union". How it did manage to compile is beyond me, unless like you said, MACH_HTCRAPHAEL wasn't being defined, which checking now, is clearly the case:

CC drivers/usb/function/ether.o
drivers/usb/function/ether.c:217:2: warning: #warning Not Set

#ifdef MACH_HTCRAPHAEL
#warning Is Set
.ifc_subclass = 0x00,
#else
#warning Not Set
.ifc_subclass = 0x0a,
#endif

Looks like that is intended to be #ifdef CONFIG_MACH_HTCRAPHAEL
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Doesn't this mean the #ifdef is actually not needed at all? I can ssh to my Raphael with the current code, thus it works with the 0x0a subclass. Let me know.
[Touch Diamond, MDA Compact IV ROM Development] konsta819:
I'm sure the gurus are aware of this, but the Vogue project met with considerable success today - they are now running Android 1.0 with everything working. Is there anything that can be learned from their devs?

http://www.engadget.com/2008/12/10/video-android-rocking-on-the-htc-touch/

http://xdaforums.com/showthread.php?t=382265
[Touch Diamond, MDA Compact IV ROM Development] maejrep:
That's probably true, but lavender.t said he had problems with the x0a subclass. Could be only a certain phone (GSM/CDMA, Diamond/Raphael, ..) that has that problem.

And as we know, booting on one device doesn't mean it'll boot on all :) We might need to find out from lavender.t what exactly happens with 0x0a on his phone, etc.
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
It means that your LCD wants pixel data in the frame buffer in xxRrrrGg-ggxxBbbb format, like hillsdale suggested in post #896.

I will try a couple more times to confirm, but it felt very much like changing the bit packing made the X server quit or crash. Will get back on that.

During the 1 second that the X cursor is there, its color is affected.

When I removed the hack from msm_fb that dma's the entire screen every time, I don't see X draw anything. Other than that it has always started up and drawn.

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
I was just wondering which initrd you are using to boot. Could you post it/host it/link it or whatever?

EDIT: With the x11 initrd and initrd-android-raphael.cpio.gz 05-Dec-2008 it's stopping for me at the framebuffer handover. Using a cdma telus touch diamond.
[Touch Diamond, MDA Compact IV ROM Development] Hamido123:
wtf i am waiting for android 1.0

sorry for this post my keyboard getting errors
[Touch Diamond, MDA Compact IV ROM Development] Hamido123:
wtf i am waiting for android 1.0

hallo to everybody,

i am one of many people who want to get android 1.0 running on the diamond and i want to develop with you but i don`t know why android doesn´t work and how progressed you are so far so please can someone post a short "diary of android for diamond"

i have read in archives that we were not able to boot android because we do not got a SD card is that true and if it is so why we do not rename in the registry the attributs of internal storage as we want to?

sorry for my bad english i am a kurd
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
It is this one, the one dcordes requested to test and report back on in post #1017.

That would have more to do with your kernel/zImage than with your initrd. At that point it hasnt started decompressing the initrd yet.

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
http://wiki.xda-developers.com/index.php?pagename=RaphaelLinux
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
I have tested another bunch now. Using dcordes x11 initrd and 2 almost identical kernels. Only difference is the 444 vs. 565 bit packing definition in msmfb_probe(). The 565 (link to kernel image) one _always_ makes it all the way through (link to that same movie) to the 'touch the crosshairs to calibrate'-message. The 444 (link to kernel image) one _always_ shows the X cursor for a second and then drops back (link to new movie that shows this) to the login prompt.

When I then go through the msm_ts calibration process, login and start the X server, it stays up but doesn't show the crosshairs or the message. Just an X cursor on an X background:

I can not move the cursor. ..or do anything at all for that matter. ..except of course drawing yellow dots.

init links to /sbin/init.sysvinit which is an ELF binary. But for logging in and launching stuff, right now, booting the '444 kernel' has the same effect...

Those tslib tools are not in the fs image (nor is gpe-dm). Can I find them somewhere or cross compile from source and add to the initrd or can you put together one that includes those tools? I'd be happy to run tests and report back.

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
Both of those flop out @ "console handover: boot[htc_fb0] -> real [tty0]"

2 messages before that I see "console [htc_fb0] enabled" which I would assume is a good thing.

Of course, I'm using a cdma touch diamond and assuming that you're running the gsm version of the same phone.
[Touch Diamond, MDA Compact IV ROM Development] nuke1:
CDMA is probably different enough to warrant lauching a new thread dedicated to that solely. :p
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
The .diff that touch of jobo posted lately didn't include the CDMA mddi panel code. It could be that he didn't apply the latest git to his code yet - thus being the reason it doesn't boot on CDMA.

@touch of jobo, I'm referring to this commit. If you apply that, the panel is recognized on CDMA devices.
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
No, see wiki.
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
That is correct. Thanks. I shall apply it and update those 2 kernel images. Probably not until later tonight though..

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] sensorama:
Yes.

in post #998
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Read the FAQ and Progress sections @ wiki. Android is not functional yet.

Let's just redirect people to wiki. No point calling names.
[Touch Diamond, MDA Compact IV ROM Development] col Cyber:
Thanks!

:)

you are soo kind
[Touch Diamond, MDA Compact IV ROM Development] lavender.t:
0x0a subclass is ok

sorry just saw this post for being busy for a while. yes 0x0a works too but it just made the host system thinking the phone was talking MDLM and gave annoying warnings (because the ether implemented was indeed CDC Subset, which doesnt have a proper subclass yet). and i was worried that somewhere down the road it might have some trouble. that's the reason i changed it to 0.

i kinda doubt this was the reason that your phone didnt boot. but if you change it back to 0x0a and your problem is gone then feel free to revert this file.
[Touch Diamond, MDA Compact IV ROM Development] schweinshax:
you need more free space on your internal drive
[Touch Diamond, MDA Compact IV ROM Development] Black_Angel:
Hi everyone,

Sorry I don't speak english very well...

So, yesterday, I ran Android on my HTC TD and it succesfully boot. But, on the "home screen" I don't know what to do :eek:

It seems the touchscreen don't work very well, if I take the stylus, I arrive on a contact page and stars appears.

That's all I can do.

Does anyone know what can I do with this version of Android on my phone?

Thnks :)
[Touch Diamond, MDA Compact IV ROM Development] cobain84:
I'm looking forward to getting a RAPH800 and helping out with the dev. Either way if the current devs would like I have MASSIVE amounts of server space I do not use that I would be happy to donate to this project for website/blog/CVS. I'd like to see the Raph be the secord (or third??) Android handset.
[Touch Diamond, MDA Compact IV ROM Development] lavender.t:
calculating MSM_CLK_CTL A0/A4 ?

wonder if anyone has a pointer to how the A0/A4 clock values are calculated. i saw the table in clock-7x00.c but that is pressumably based on the 400MHz clock, which is different from the diamonds 528MHz.

also, why is there a 'freq' and an 'actual_freq' which is most half the value of the former ? from the code apparently if function pc_clk_set_rate() is called to set the clock to 2000000, then calling pc_clk_get_rate() would return 144000, etc. i'm quite confused.

i pdumped my diamond and got values A0 = 0001fff4 and A4 = fff50044, matching none of the entries in the table. dont know where these values should fit in (with the freq and actual_freq). and how to get the rest of the entries ... :confused:

//sigh ... i guess probably the biggest help would be getting the datasheet of this MSM chip. but i know what a greedy company qualcomm is. :mad:

- lt
[Touch Diamond, MDA Compact IV ROM Development] skiwithpete:
This is from a post on page29:

For ARM datasheets you can refer to this one, which seems to be most alike with the ARM core in the MSM7201A:

http://infocenter.arm.com/help/topic...01g/index.html

Then further down:

Actually, the exact datasheet for the cpu core is this one,

http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0211j/index.html

but this is general -- it won't give us the specifics of MSM7201A like how to drive the MDDI inside the chip or list of registers and memory locations.

I remember that someone had tried to start a map, but I can't find the right post at the minute.

P
[Touch Diamond, MDA Compact IV ROM Development] dejant_9:
heuuuu possible but i think that more French speak English than English speak French...first i want to know if everyone here is interested by a forum. I don't want to spend my time for a unused forum
[Touch Diamond, MDA Compact IV ROM Development] WatskeBart:
Linux will not boot if you have the usb cable connected. It will say that ARMv9 has crashed and it stays in that screen. Also no keyboard available.

I don't know if this info helps but i just wanted to let you dev's know. :)

If there is anything i can do to help with the development let me know, but do know that i have very little linux expierience.
[Touch Diamond, MDA Compact IV ROM Development] jlewis11:
So since android is almost completely running on the Touch, all except for the Voice radio part, do you think we are remotely that close for For Diamond and Touch Pro. You would think that since G1 and Touch Pro are very similar it would be easier...but obviously thats not the case
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
further test results on X

Here is a post that has something to do with running linux on an HTC Diamond or Raphael phone ;)

The X server runs and draws fine. I can't add another host to the access list with xhost. It restarts the server with a clean list. However, I can ssh in, kill everything, and then relaunch X without access control. Then I can have X client apps run on my linux vm and draw on the raphael.

Input from the vkeyb goes to the focussed X window. (I can type commands in an xterm that runs on my linux vm.)

When I start x-window-manager, the X shaped cursor changes to an arrow pointing NNW. This wm draws some window decoration and also changes the geometry of any client app to full screen, ignoring any -geometry supplied.

When I kill the wm, leaving X running, I can position X clients -geometry.

I can not move the pointer, but I do have a /dev/input/mouse0 that seems to work. When I cat /dev/input/mouse0 and then drag across the screen, I see stuff spewed. It appears to work like a trackpad tho, outputting speed and direction, rather than position. If I boot into netrippers busybox initrd, I have a /dev/mouse0 in stead of a /dev/input/mouse0. The init in that one doesn't seem to explicitly create this device. I can not read/edit the init in the x11 angstrom initrd (or I don't know where to look).

Some photographs:

With WM: Without WM:

Decoration:

-Jobo

PS: Can someone boot this kernel on a cdma phone? Thanks.
[Touch Diamond, MDA Compact IV ROM Development] pixelwix:
this what i got when i boot it up on my sprint touch pro

colors still messed up and it gets stuck
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
Booting on my telus diamond touch/x11-initrd it boots to the screen calibration at which point clicking the xhairs has no effect and the device seems stalled. The screen also has a bit of a greenish/blueish tint to it. Images attached, first 3 w/ x11-initrd and last 1 w/netrippers initrd(img00049). Tried it w/ netrippers initrd-android-raphael and I'm able to calibrate the screen, get x loaded and play with apps in x though the colors are messed ofc.

@Pixelwix: are you booting this off your internal storage or off your program memory? Try booting off your program memory as it stalls out @ that point every time if you're booting off the internal storage for some reason.
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
I have the same results. This calibration screen doesn't do anything for me. You still have to go through the 'normal' (msm_ts.c) calibration during boot (or later).

I would say they're even more messed up.

I hoped it wouldn't do that.. :( ..thanks for testing :)

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
You really make me anxious for a .diff. I'd love to test if it also detects something on my Raphael (even if it is inaccessible).

@touch of jobo, your latest screenshots show virtual keyboard somewhere in the middle. Did you make it draggable? Do you have some time to make a clean diff, possibly without the 'landscape keyboard' (as that's not compatible with diamond). We can commit that to git then, would be a nice addition.
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
If you had read the first post in this topic, you would have found this which is what you are looking for..

EDIIT: lol.. I suddenly have no idea where i found that message.. wrong page
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
Yes, I made it draggable, because it would sometimes get in the way. First I made it toggleable between it eating clicks and clicks going right through it, but this seemed more useful.. It still eats clicks. To change that, make msm_ts_handler always return 0 or ignore the return value in msm_ts.c:do_softint(). It is now also completely flicker free (even through transition animations or dragging the curtain down/up) by calling msm_ts_handler(0,0,-1) right before starting dma. When dragging the vkeyb around, it leaves a trail of keyboards, because I don't know how to 'undraw'.

Here is a git-diff. It is pretty clean, as I have updated to the latest git last weekend.

I just changed MSM_VKEYB_LEFT and _TOP from macros to static globals, keeping them the same names and in the same spot, because this keeps the diff smaller. It would probably be more ..uhm.. appropriate to lose the MSM_ and make them lower case and move them with the other static globals, but that would give a bunch of small modifications all over the place.

(There are some differences where I've been playing with color spaces, which doesn't have the desired effect anyway (as I'm probably barking up the wrong tree on that :( ) but hey.. Just ignore those.)

Does the landscape thing break the kernel on Diamond, or does it just not do anything? I left that code in there, but #if 0'd it out.

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] liamhere:
i am going to clean this thread up a bit

if anyone has a problem with this please pm me

will remove thanks posts....and other pointless posts

hope this will then put the thread back on track :)
[Touch Diamond, MDA Compact IV ROM Development] etiger13:
can you do that with the Vogue thread too?
[Touch Diamond, MDA Compact IV ROM Development] dcordes:
liamhere: wood welcome some moderation on the kaiser thread as well. thanks a lot. http://xdaforums.com/showthread.php?t=396782&page=178