yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] sensorama:
Check these links. Might answer something for you:

http://www.qis-brew.com/brew_bnry/p...aftab_munshi_ati_optimizing_games_imageon.pdf

http://brew.qualcomm.com/brew/en/
[Touch Diamond, MDA Compact IV ROM Development] skiwithpete:
ace_ddi.dll

http://xdaforums.com/showthread.php?t=296241

last page for the download
[Touch Diamond, MDA Compact IV ROM Development] sensorama:
What do you mean?

The diamond, for what i can se, doesnt use ace_ddi.dll.
[Touch Diamond, MDA Compact IV ROM Development] skiwithpete:
Sens,

Doesn't have or doesn't make use of?

I thought what was meant was doesn't have - as in 'file was missing.'

As espenfjo said...

But I'm still trying to figure out what your Qualcomm Brew link posting has to do with anything...
[Touch Diamond, MDA Compact IV ROM Development] andrewloh:
I hope it is booting into new Android OS ROM.. current WM6.1 is a bit out dated in terms of OS technology.
[Touch Diamond, MDA Compact IV ROM Development] lennysh:
From what I understand, haret completely unloads WM. Since nothing in WM is useable in Android. Please correct this if I'm wrong. I've just always been told it unloads WM completely. Maybe only a few files left in memory to run haret or whatever. If those are even needed.
[Touch Diamond, MDA Compact IV ROM Development] egilrs:
Really looking forward to development on this. Cant wait to boot up Android :D
[Touch Diamond, MDA Compact IV ROM Development] ATT-Half:
Hello i was wondering if is there a .exe with hillsdale sprint video fixed already applied out there i would like to try it. i know colors still don't work ok but i would like to get a feel of android GUI on touch pro. ( it looks good on the stock htc touch pro from the pics on the wiki )

I have no idea how to apply m7aefaeb8.c to raph_20081105-01_android_v0.8_touchscreen_fix :)

keep on great work guys
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
Did you even read the thread or wiki? Couple pages back in this thread and right up near the top on the wiki page ...
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Just updated progress section @ wiki with two new linload's (ready to boot .exe's). They have the latest kernel available so it works with RAPH800 (sprint) too. One of them is android, the other is angstrom with usbnet support. Note that colors are still messed for RAPH800. :)

Have fun.
[Touch Diamond, MDA Compact IV ROM Development] holydhaliwal:
Just thought i'd say I've just tested this out on my telus cdma diamond and it works perfectly (minus known issues)

Good work!
[Touch Diamond, MDA Compact IV ROM Development] dcordes:
I added support for kaiser polaris raphael diamond and vogue to openembedded. The angstrom images netripper uses are a result of my test builds.

Everything is built with armv6 and novfp optimization. (new architecture in openembedded because all the msm7* have no vfp).

If you want to install/remove/update packages in the angstrom images you can use opkg. Its usage is very similar to dpkg. so to debian/ubuntu users it might seem familiar:

update the package cache with

to upgrade your angstrom distro use

to get a list of installable packages do

installing packages:

removing

Since SD is not operational on raph and diam yet, your changes are not persistent using the initrds. You could use nfs with the available usbnet if you wanna mess around with the angstrom userspace though.

You can also browse available packages here.

If you feel brave and want to build your own angstrom iamge, visit angstrom-distribution.org where you can find this nice howto . As machine set htckaiser htcpolaris htcdiamond htcraphael or htcvogue.

After walking through this, it will get you the entire cross building environment and will also clone and build the latest kernel for the device of your choice.

Unfortunately you can't use the phone yet in angstrom (and other non-android userpaces) with the msm7* devices. I'm working on this in cooperation with the openmoko developers :)

BTW, did somebody test an Xserver on the diamond or raphael?
[Touch Diamond, MDA Compact IV ROM Development] komteks:
Both worked for me as well on a Sprint Touch Pro. :)
[Touch Diamond, MDA Compact IV ROM Development] michbeck100:
Driver for internal storage

Hello,

I've been following this thread since it started and read every single post.

From my point of view the most crucial issue is the missing sd card driver. Once we have this thing working, we can start using Android 1.0.

After a few hours of searching the web, i found that the Diamond is using a moviNAND flash chip from Samsung. This chip has an integrated mmc controller (see this for more information). I haven't tried the mmc drivers that come with the kernel from linuxtogo git. Maybe these are working out of the box?

But if someone of you guys is familiar with developing linux kernel drivers you might be interested in this document . It's an essay how to implement an moviNAND flash for a WinCE system. It also describes the registers used for accessing. I think this could be helpful for developing such a driver. In the appendix there are also some other interesting data sheets for this NAND chip.

Would be great if this information could be of any value fro somebody here.
[Touch Diamond, MDA Compact IV ROM Development] beboxed:
Dudes, did you know that TomTom devices also use MoviNAND chips?

And that they have the kernel source diffs downloadable on their website?

Just take a look here: http://www.tomtom.com/page.php?Page=gpl#kernel

Browsing thru the diffs i found a couple of references to MoviNAND functionality like:

+ * at4_sd.c - Cenatrality AT2/3 SDIO Host driver

+ *

+ * Copyright (c) 2007 Centrality Communications, Inc.

+ * Original version for AT4X0A

+ *	by Roger Huang <roger.huang@centralitynav.com>

+ * Modified to support MoviNAND and Power Management

I hope that someone can use this for improving the kernel for diamond devices.
[Touch Diamond, MDA Compact IV ROM Development] ATT-Half:
thanx NetRipper

my RAPH800 sprint is getting stuck after:

[26.720054] drivers /rtc/hctosys.c: unable to open rtc dev ice (rtc0)

[27.372075] trout_pwrsink_set: STUB!

[27.379887] trout_pwrsink_set: STUB!

[27.382105] trout_pwrsink_set: STUB!

[27.391098] trout_pwrsink_set: STUB!

maybe set = get txt is small hard tor read but yeah it stuck there any ideas i left it there overnight thinking maybe takes a while fell sleep woke up this morning it was still stuck there.

tested Angstrom for the heck of it also gets stuck same place

but around [21.382075] time
[Touch Diamond, MDA Compact IV ROM Development] lennysh:
1st of all, it's set not get. Second of all, I get this same result on my Alltel CDMA Touch Pro. I assumes RTC0 is the problem. What is that so we can troubleshoot?
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Did you try tapping the screen, even when it seems to hang?

Btw, it doesn't hang because of the 'rtc' message. We all get that message. The STUB messages are normal too.

RTC is real time clock (reads the clock from hardware). This also doesn't work on RAPH100. It's not causing any problems.
[Touch Diamond, MDA Compact IV ROM Development] lennysh:
I seem to be able to get it working with tf3d turned off for more ram. With tf3d running, i only have 110, but without it running, i have 140-133. Seems it werks better with the more ram to start with.
[Touch Diamond, MDA Compact IV ROM Development] Riel:
Works just fine on DIAM100 device, with the right colors. But will not be much news for you? :)

I also had not much memory left before booting (with an eye on previous posts).
[Touch Diamond, MDA Compact IV ROM Development] oberheimer:
It seems to work good on the HTV touch phone

http://www.youtube.com/watch?v=j3v7q8gdCZc&NR=1

http://www.youtube.com/watch?v=d0z9bWiAT44&feature=related

Btw android looks really good cant wait to get a phone with android :p
[Touch Diamond, MDA Compact IV ROM Development] mugglesquop:
HTC? and which Touch Phone... :rolleyes: (i cant get on YouTube at work... dam filtering :p)
[Touch Diamond, MDA Compact IV ROM Development] NikPraskaton:
Looks really good. I dont really like TouchFLO on my HTC.. its slowing down the device.. nothing more. Cant wait for android to get working..
[Touch Diamond, MDA Compact IV ROM Development] nin2thevoid:
True. Especially on the HD, but that is a future issue. I really like TouchFLO3D but Android is becoming a very good platform.

The only thing I don't like about the G1 is the G1... I'd love that OS on some great hardware/form factor like the Diamond.
[Touch Diamond, MDA Compact IV ROM Development] kal1990:
hey there, i get the same messages like ATT-Half. then it seems to hang.

i tried the .exe and the files, i turned tf3d off but nothing changed...how can i find out whats the problem?
[Touch Diamond, MDA Compact IV ROM Development] petay:
i have found another phone running android. well i think i have!!! the site looks a bit amateur but maybe there pooling all there efforts into the device rather than the web site!!! http://www.zzzphone.com/

maybe they could help with the port or there device may hold some drivers for us????
[Touch Diamond, MDA Compact IV ROM Development] kam187:
lol it looks like a 15 year old made that site for a school project
[Touch Diamond, MDA Compact IV ROM Development] balsat:
Nand flash

My programing skills is very bad, but this http://ethesys.library.ttu.edu.tw/ETD-db/ETD-search-c/getfile?URN=etd-0831107-173708&filename=etd-0831107-173708.pdf pdf file seems very usefull!?
[Touch Diamond, MDA Compact IV ROM Development] ATT-Half:
yes tried tapping the screen hit every possible key on the phone nothing
[Touch Diamond, MDA Compact IV ROM Development] Blazeitup123:
Android 1.0 gets ported to the Nokia N810

http://www.engadget.com/2008/12/05/android-1-0-gets-ported-to-the-nokia-n810/
[Touch Diamond, MDA Compact IV ROM Development] saphir:
Could you point us to some links to confirm the use of a Samsung chip?

If you're right, porting Samsung native linux driver to the kernel should be easier than developing a new one.

[edited] The driver is not yet available on their website but http://www.linuxdevices.com/news/NS8555920711.html?kc=rss
[Touch Diamond, MDA Compact IV ROM Development] vomoho:
Hi,

Sorry to distrib you, for this question, I thing you have already answer to this question but i didn't the answer.

i want to know if install android on my htc (diamond) need to remove WM, because i need to keep some application like tomtom...

Thanx for your answer, and sorry for my bad English I'm French.
[Touch Diamond, MDA Compact IV ROM Development] itsallsubliminal:
android is not near full functionality yet

when you load android, it shuts out windowsmobile(completely) and boots android... by shut out, i do not mean erase... you can toy with android for some fun of having a different operating system, and when you want to return to windows mobile, just do a soft reset, thats all...

your windows mobile applications will NOT work on the android, nor will you have your contacts in android
[Touch Diamond, MDA Compact IV ROM Development] Unimaginative:
Not sure if this would be any help, re: getting Android to see the NAND:

"YAFFS2 -- 35 Files

Unlike PCs, which store files on disks, mobile phones store files in solid-state flash memory chips. The HTC G1 uses NAND flash, a type of flash memory that is becoming more popular due to its combination of high density and low cost.

YAFFS2 is an acronym for "Yet Another Flash File System, 2nd edition" and provides a high-performance interface between the Linux kernel and NAND flash devices. YAFFS2 was already freely available for Linux. However, it is not part of the standard 2.6.25 Linux kernel, and so Google added it to Android."

From http://nthcode.com/pubs/porting-android-to-a-new-device.html (cheers to Blazeitup123 for posting that link).
[Touch Diamond, MDA Compact IV ROM Development] Mr.Wuan:
Android on htc diamond

Can somebody post the link to the latest version to the android on the htc touch pro?
[Touch Diamond, MDA Compact IV ROM Development] GlemSom:
Are their any complete SDK kits for Android on HTC Diamond?

(Including kernel, android, cross compiler, binutils and glibc/ulibc?)

Or will I have to start by getting a working crosscompiler platform - and then getting kernel and programs(android) to compile using that toolchain?
[Touch Diamond, MDA Compact IV ROM Development] -Mr. X-:
boot from internal memory not sd card.
[Touch Diamond, MDA Compact IV ROM Development] dcordes:
what's wrong with the msm_nand ?
[Touch Diamond, MDA Compact IV ROM Development] ATT-Half:
works now strange it did not work when i copied the .exe to my devices folder but it worked when i cut and pasted to internal storage folder.

thanx
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Just to clearify. In the Diamond there are TWO NAND devices. The first NAND has the SPL, OS, radio and some program space. The second NAND is the MoviNAND which (by the way) is compatible with MMC protocol and contains the "internal storage" of 4gb.

The internal storage (movinand) is the one that should be focused on for Diamond. I doubt that it is the same as msm_nand. In fact, I'm hoping the MoviNAND is just accessible like an SD card via the msm mmc host. We'll know when we get SD card to work on Raphael (or movinand to work on Diamond).
[Touch Diamond, MDA Compact IV ROM Development] dcordes:
can somebody try this initrd? it has the angstrom rootfs plus x11 packages. what happens when you boot it? does it display a nice gui when finished?

net, did you try msm_nand on the raphael?
[Touch Diamond, MDA Compact IV ROM Development] balsat:
It outputs a lot of stuff and then stops with black screen and a white cursor in upper left corner!
[Touch Diamond, MDA Compact IV ROM Development] dcordes:
can you move the cursor? did you go through the calibration?
[Touch Diamond, MDA Compact IV ROM Development] balsat:
It did not stop for the calibration, but continue for the init... I can't move the cursor, and there is no USB net.
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Well, it doesn't work out of the box. Druidu played with it on his Diamond and you know it almost bricked his device. I stopped playing with it, as it's for the OS part, not for SD. And I don't want to risk bricking my device. We don't need the nand on which OS resides working anyway (low priority at least).

Btw I tried that initrd of yours and on my raph it just gives a black screen when loading X. I don't get a cursor like balsat resports.
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
You can calibrate it anyway. The first tap on the screen inits the calibration, the second tap must be top left, the 3rd tap must be lower right. Do that and see if you can move the cursor. :)
[Touch Diamond, MDA Compact IV ROM Development] balsat:
I tried that and the cursor (A non blinking white line) still wont move!
[Touch Diamond, MDA Compact IV ROM Development] dcordes:
it seems like this is the same problem as on the kaiser where also the first frame drawn by Xfbdev gets stuck.

this proves it's typical on all devices using msm_fb so it's a problem with the driver itself.
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Oh, that sounds like a hang. I thought you had a graphical cursor. ;)
[Touch Diamond, MDA Compact IV ROM Development] dcordes:
retry a few times and see if you can get it to draw something. also you can remove the gpe-dm from init.d and run Xfbdev manually from remote host through usbnet or on a different tty

on the kaiser the display also freezes sometimes before it draws one frame (also on the white cursor line)
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
Regarding the flickering on screen keyboard..

A workaround for the flickering is to put a

msmfb_update(registered_fb[0],
MSM_VKEYB_LEFT,
MSM_VKEYB_TOP,
MSM_VKEYB_LEFT + MSM_VKEYB_COLS * MSM_VKEYB_KEY_W,
MSM_VKEYB_TOP + MSM_VKEYB_ROWS * MSM_VKEYB_KEY_H);

at the end of msm_vkeyb_draw_keyboard(); (plus a little bit of fiddling as msmfb_update() is static in msm_fb.c and registered_fb[] is extern from fbmem.c) Together with plotting not only on (x,y) but also on (x,y + lcd_height), as I mentioned in this post, you get a non-flickering keyboard with nicely responsive red pressed keys. (You probably only need to draw in 1 of the 2 buffers ... I dont yet know how to tell which one.)

As a side effect, you can then also get rid of the // XXX - VERY ugly hack around line 207 that forces redraw of the entire buffer every time. This breaks the yellow-dot-drawing though. If you value that you have to mark the buffer dirty there too. (Same goes for test pattern drawing.)

The messed up colors thing:

I've been playing around with the bit packing settings in msm_fb.c This does impact the post handover console drawing and the blitting of the tux image,

but as soon as the android GUI kicks in, everything looks normal. (I have a GSM Raphael, so my colors are OK, I'm _trying_ to get them messed up..)

@hillsdale, or anyone with a cdma device: does the tux logo look normal, color wise, and if not, does it if you change to:

red.offset = 10;

red.length = 4;

green.offset = 6;

green.length = 4;

blue.offset = 0;

blue.length = 4;

in msm_fb.c, msmfb_probe(), around line 707 ?

I get an error downloading it...

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Ive been following this ever since the first Android images came out, but I am curious as to how far away from a fully functional port we are? I know that regarding Diamond and the Raphael, we still cant even boot it properly, but do you find it likely we will have a fully working version of Android on our HTC phones any time soon?
[Touch Diamond, MDA Compact IV ROM Development] n.mowberry:
Ages, i actually don't think they'll get it going.
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Wow, the vote of confidence is overwhelming. ;)
[Touch Diamond, MDA Compact IV ROM Development] smile_gerard:
If there is a will.... There is a way :)
[Touch Diamond, MDA Compact IV ROM Development] liamhere:
rome wasn't bulit in a day.....give them time

if you really want it now and can't wait.....go buy G1 ;)
[Touch Diamond, MDA Compact IV ROM Development] n.mowberry:
Lawl, sorry just sick of annoying people asking asking asking.

I have confidence in you!!
[Touch Diamond, MDA Compact IV ROM Development] petay:
i tried the x11 angstom image and got the same. little white cursor type thing. i saw no calibration but i did notice there were a few errors in the console while it was booting on my gsm diamond. i will try and make notes what they are!!

ps after a few more boots i can not read the messages fast enough to write down the errors, however i have found the calibration is in there. if you wait for the STUB! STUB! STUB! STUB! then click the screen you see the calibration messages within all the other console stuff. i managed to calibrate before getting to the black screen but alas nothing new happens :( i can not move the cursor or anything
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
How can I help in porting Android? Is there any donations needed, etc?
[Touch Diamond, MDA Compact IV ROM Development] zero2k58:
same question: how can i help you guys without breaking my htc touch diamond?
[Touch Diamond, MDA Compact IV ROM Development] slovoflud:
Uniting your questions...

You guys can send your diamonds to any of the people who're working on it... Make sure it's packed in Bubble Wrap, so that it won't brake...
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
X

After the kernel boots, it outputs a lot of stuff to the console. Then it shows (for a very short time) the classic X windows background pattern with the classic X shaped X windows cursor. After that, the screen goes white, in the upper left corner are dark blue cross hairs (plus shaped). Above the center of the screen it says 'touch the crosshairs to calibrate the screen'.

Thats it. Touching the cross hairs does nothing. (Touching the cross hairs some more draws yellow dots on it.) At this point I don't see the X cursor anymore.

It does require a kernel with the hack in msmfb_start_dma() that marks the entire buffer dirty. The kernel still runs, as you can keep drawing dots and the vkeyb still shows pressed keys red. I did go through the calibration process in the touchscreen driver.

(Tested on a GSM Raphael)

-Jobo

EDIT: I shot a movie of it booting. This time it shows the X cursor longer and the background is black, not the classic pattern. Its not quite sharp enough to read clearly but if you know what youre looking for you can probably recognize it. Hope it helps. -Jobo
[Touch Diamond, MDA Compact IV ROM Development] freakolowsky:
and other than that ... due to the fact that my Raph is the only working phone i have :D

I'd be glad to pich in with some coding, but due to the lack of time all i'm offering is happy thoughts, money donations, mirror space for testcases on my servers, ...
[Touch Diamond, MDA Compact IV ROM Development] brainbubble:
FYI

Android 1.0 SDK 2 is out....

=>http://code.google.com/android/RELEASENOTES.html
[Touch Diamond, MDA Compact IV ROM Development] Vince13:
Thanks you!

Now we should be able to use the Windows USB Driver in order to debug. It was already possible on UNIX, let's see with Windows now.
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
These kind of videos are great for showing up the progress. I would love to see more videos as we progress further, linked from the Linux/Android for Diamond wiki too.
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
Anyone who wants to try and see/feel/report what the effect is, you can find a zImage here that..

..has pixel bit packing set to match xxRrrrGg-ggxxBbbb,

(tux may look normal on cdma? or does it already? things are very green / cyan on gsm)

..does not have the hack in msm_fb.c/msmfb_start_dma() that would force updating the entire screen,

..plots on (x,y) and (x,y + ymax),

..calls msmfb_update() in msm_vkeyb_draw()

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] jeforce:
I have try your image on a diamond whith the x11-image-120708.cpio.gz , all was green and the dot wasn't in the corner.
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Could you make a .diff? When using git, just use git-diff > my.diff, no arguments needed.
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
Is your diamond a GSM one? (Did you already have proper colors in the android background for instance?)

I think that the X server on that initrd image requires a kernel _with_ that msmfb hack because it doesn't mark the frame buffer dirty. This kernel only dma's the dirty area. It is probably better for now to leave that hack in, I guess.

If you have proper colors in android, yet everything goes green on this X server, that would indicate that it does honor the bit packing as set up in msmfb_probe() unlike android. Will test and confirm.

I sure can. Here it is. Its a bit big because of tinkering around (did some cleaning up on that now..) and its not against the latest git.

-Jobo

EDIT:

The X server does indeed draw green/blue when I set the bit packing differently in msmfb_probe(). However, it only draws the X cursor for a second or so and then drops back to the console. I get a login prompt. I assume the X server crashes. When I put the bit packing back to 'correctly' match rgb565, the X server stays up and draws the cross hairs and the instruction to touch it, as in the movie.

red offset = 11, length = 5;

green offset = 5, length = 6;

blue offset = 0, length = 5;

Again, the X server needs the XXX - very ugly hack (msm_fb.c~207) in place.

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
How will the Android SDK 2 affect the porting? Will it help in any way, or will it just allow much more to be done from Windows rather than Linux?