yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] sandic:
my device is DIAM500, a CDMA diamond of sprint.

after some research, i downloaded Untouchab1e's package "android-diam100-20090222-ALTERNATE.rar"

and i unzipped the folder "tmp" to my "internal storage" root

i found the mtype for DIAM500 is 2040 in the wiki, so i changed default.txt 's configuration to "set mtype 2040", then i try to run the application, and surely i got an error of "mounting /dev/mmcblk0 on mmc failed", and the system was hang.

after that, i revert the configuration to default "set mtype 1805", and i successfully make my diamond running with a messed up color shown and a messed up screen tapping. but finally it works.

my question is, is there a mtype 2040 for DIAM500 device or not?

BTW, the project is fantastic, thanks you guys the excellent work!:D
[Touch Diamond, MDA Compact IV ROM Development] saudoo:
I believe the color fix was applied a bit later than when that version was build.

You should try a newer build from http://balsat.servehttp.com/ ... afaik there's some problems with the builds done in April, so you should try a build from late March out instead.

Oh and read the wiki.. I believe theres something about the color fix in there. :)

Edit: Balsat, that didn't work. I tried it with the 06-04-09 build. Did a soft reset. Put it into ActiveSync (dno if that's possible on Ubuntu though). It hangs at the bootloader screen, right after the two vibrations the phone makes in the beginning, with all that text that is complete nonsense to most people. :)
[Touch Diamond, MDA Compact IV ROM Development] Soaa-:
I reported that the 2040 mtype doesn't mount the internal storage properly. It hasn't been fixed yet though.

A few things I tried:

Change mtype to 2040. I got the same error as you.

Copy the MMC configuration for GSM phones to CDMA phones and recompile. I got to the Android boot screen, but after loading for a few seconds, my phone shut down.

Copy the color fix from the CDMA phones to GSM phones and recompile. Set mtype to 1805 for DIAM100 and it runs, but of course, this solution isn't viable.
[Touch Diamond, MDA Compact IV ROM Development] balsat:
Updatet root.cpiogz

There was a error in the root.cpiogz on my preveus build, i can't check my latest build out at the moment, but i hope it's running now!
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
Did you read my previous post? Changing the mtype in the default.txt and then passing mmcblk0p1 as your mmc when your mmc is actually mmcblk0p5 is going to cause the same error regardless. I posted a solution that was provided for me by lavender.t when I ran into the same issue months ago on the last page. I'll toss it up on the wiki as well as it is seems to be the only solution I can find atm since if I pass mmcblk0p5 in default.txt I still get errors for some reason. I would put money on it that a user more familiar w/linux could tell me what I'm doing wrong and even write a script that would do what needs to be done here to auto detect and mount the correct partitions regardless of device. This is a problem w/user input and not understanding the os not being able to mount a partition because it's on sda1 and not sdb1 like is typed out in fstab.

Where he types "this should have the mmcblk0p? with the correct minor code and you should be able to mount on that device." the ? = the minor code. In my case it's mmcblk0p5. So after running "mdev -s" I would "ls -l mmcblk" and it would list all mmc devices. You could fdisk mmcblk0 and print out the partition table which would tell you what partition you should be mounting etc and then "mount -t ?vfat? mmcblk0p?" (I think it's vfat, might be msdos etc, man mount for more info) where ? is your correct minor code for the partition on your mmc in your device. In my case I tried setting my partition info in default.txt to mmcblk05 but I still come up with the error messages that the partition and therefore images cannot be found. I see in the log that the device is detect but for some reason w/out a little user input it isn't mounted correctly. Anyways, I added this to the wiki under the device info.

The issue w/screwed up taps is setting screen calibration in your default.txt. As far as I know this information doesn't need to be passed and if passing it causes your screen to be calibrated incorrectly wouldn't it make more sense to remove the calibration info and manually click the 2 dots on the screen when you get to that point? ^^
[Touch Diamond, MDA Compact IV ROM Development] mrbigben:
so ive been at this for over 4hours now on something I expected to take 4 min.

I cant get android installed on my vogue (bell). if i try the CAB file i get "installation of the cab file was unsuccessful" if i try placing the files (in the root, outside the root, in a folder, some in some out, if you look hard enough you will find every opinion the the issue) and when i try and run Haret.exe i get an error indicating its certificates are not trusted.

Ive formatted the sd card, ive hard rebooted, soft rebooted, reformatted the card and so on. I've run out of ideas. please help ive looked at probably hundreds of posts on your forums, to no avail.... yet
[Touch Diamond, MDA Compact IV ROM Development] mak213:
im using udK's r4 6.1 rom, ive used android alot and been keeping up with thread for some time now but i downloaded lasted build and ran haret and it started linux then vibrated twice then just hanged there yes i restarted phone countless times even disabled manila so id get a fresh boot but no help....cant wait for latest offical build !
[Touch Diamond, MDA Compact IV ROM Development] mak213:
ive used a the april 8th build and i finaly got to the android logo blinking etc but then it hangs there so in reply to u..it is not fixed appreciate the hard work ur up puttin tho

EDIT: im on 6.1 build 21040 btw DIAM100
[Touch Diamond, MDA Compact IV ROM Development] balsat:
I have just tried my latest build on a diam100 and it work perfect!
[Touch Diamond, MDA Compact IV ROM Development] baalbaal:
Hi Balsat!

Thanks for all the hard work you're putting in!

Tried the file form the "latest build" link, and I'm getting the same results as mak213. It boots up, but hangs at the Android logo. Looks like it's in a loop somehow.. The logo will pulse almost two times, then hang.. blink and start over.

Keep up the good work!

baalbaal
[Touch Diamond, MDA Compact IV ROM Development] duuri:
hi balsat latest build works for me:) even can send sms:) and make call, but receiving doesn't work
[Touch Diamond, MDA Compact IV ROM Development] switchgott:
Hi,

realy realy good work an big thanks to developer.

But in my DIAM200 doesn´t work.

Can someone tell me why?

Thanks.

Bye
[Touch Diamond, MDA Compact IV ROM Development] yann79:
mmcblk0

Hello,

I had my diamond previously getting stucked at the "mmcblk0" when booting.

Also with the balsat version from the 6th of April it is now working fine and I get to the android OS (the funny thing is I have a PIN code in windows and it doesn ask it in android. Also I can send calls...strang).

With the 7th it also get stucked at the Android logo.

Nice work guys!

Yann
[Touch Diamond, MDA Compact IV ROM Development] saudoo:
Oh great... I'll try and run the newest build asap..

Btw.. Does anyone know if it's possible to change the resolution android is using? I find everything a bit too small. Especially dragging down the Notifications bar....
[Touch Diamond, MDA Compact IV ROM Development] dcordes:
AMSS (modem operating system on arm9 side) doesn't know you booted a different operating system on the system processer. it doesn't notice any change so it doesn't ask for the pin again after you booted linux kernel on system proc

the gsm builds (both, raphael and diamond) are broken in the current kernel. and freeze during bootup. hope this will be fixed soon
[Touch Diamond, MDA Compact IV ROM Development] mak213:
i just upgraded from udK r4 to r5 and now it works flawlessly sry, but also tysm :)

p.s. i cant wait for audio, backlight toggle on and off then ill start using daily i dnt care if any bugs! lol
[Touch Diamond, MDA Compact IV ROM Development] mak213:
bah nvrmind it only workd fine once then 2nd time anroid loaded then said a process error then hanged then i tried to boot again and it hangs on android llogo
[Touch Diamond, MDA Compact IV ROM Development] balsat:
Will look into that, once i in a couple of days get home to my linux box!
[Touch Diamond, MDA Compact IV ROM Development] balsat:
delete this
[Touch Diamond, MDA Compact IV ROM Development] keaneo:
Hi, very nice work you are doing here! i have tried the 6th april version of your android, it works fine! great job..

i can send sms

but there is a problem, i don't have sound..and no wifi ..also i cannot shut down the phone to save battery...

i also tried the latest version on Connect UTB...all the wallpapers works in full screen on this version...have you developped this one too?
[Touch Diamond, MDA Compact IV ROM Development] scope008:
Changes to Android Kernel

Over the past couple of days there has been a massive amount of changes made to the official android kernel source. (http://android.git.kernel.org/?p=kernel/msm.git) Has anyone tried compiling the new code for use on Raphael yet?
[Touch Diamond, MDA Compact IV ROM Development] gebruikershaes:
I don't think people are working on this anymore..
[Touch Diamond, MDA Compact IV ROM Development] mak213:
yes they are...it would work faster if the developers didnt get useless replys from fools like u

how about u read the dam wiki?
[Touch Diamond, MDA Compact IV ROM Development] chronster:
try and talk to people the way you'd want to be spoken to.
[Touch Diamond, MDA Compact IV ROM Development] sd00:
Fella, chill, i'm sure these guys feel the frustrated and are simply inarticulate when trying to convey this (but harmless all the same) - all of us monitoring this thread dream of the day the announcement comes "Andriod 1 - for HTC Diamond"

I too wish development was speedier, but I lurk, quietly, waiting & hoping.

Best regards to the gurus putting thier spare time & efforts into this.

Steve.
[Touch Diamond, MDA Compact IV ROM Development] keaneo:
thanks to you all...this is a god damn good job...HTC businessmen want to sell their "Magic" or "Dream", so they don't care porting Android on other phones....

i hope your working hard on the sound problem, this is in my opinion the N°1 priority issue, as a phone is made to call, and not just read...:p

for now, the android's sms interface is much more intuitive than WM65....

i also notice, that all the wallpapers are in FULLscreen on the 20090222 version http://connect-utb.com/index.php?option=com_jdownloads&Itemid=58&task=view.download&cid=25

but on the latest version on the basalt server, just 1 wallpaper is in fullscreen, why?

Good luck for you all
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Keep in mind that Balsat's daily builds is basically the result of his own development work (correct me if I'm wrong here Bal ;) ), while on Connect-utb you will find the latest "stable" releases.

Right now I am trying to focus on the development process itself, because as of now, I feel that people are basically working on their own little mini-projects instead of working together.

We are basically just "code 'n fixing" this thing while we should be more organized.
[Touch Diamond, MDA Compact IV ROM Development] NoBody20013:
hi,

sorry, but i think the posts here in this topic are 80% "how can i help but i am a noob" posts, 8% "android isnt booting" and only 2% new code or bugfixing... and this for more then 4 month...

am i wrong?

for me it doesnt seem that there are one or two people who are able to port android to diamond because of knowledge... changing an mtype doesnt provide the functions needed. and waiting for functions implemented in a new kernel isnt the right way.

i dont know much about andoid and linux- so i cant help too :(

But maybe there are one or two people of you who CAN.

So if these people would post their knowledge or the fact that they have knowledge and then communicate over PM or the HTC Android Forum then we could have a chance to have a fully working android some day...

if i am wrong and there is a "Coding-group" then i am sorry. But maybe then this group is too little or not "powerfull" enough. Providing info on which part someone is coding/testing eg. would bring more people who want to help?

dont misunderstand me- i would love to have android on the diamond!

greetings!
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
There are quite a few working hard on this project, believe it or not. Pop in the irc channel and maybe you will learn something. I have no doubt that we have the neccessary skill and knowlage to get Android fully running..

Patience is needed though.

Furthermore, this topic isnt being used for development discussion anymore, at least not significantly ;)
[Touch Diamond, MDA Compact IV ROM Development] saudoo:
But you are still updating the wiki though.. right?

Edit: I mean.. When theres something to write about ofc! :P
[Touch Diamond, MDA Compact IV ROM Development] Dav0:
Hello:

Do this ADROID version works too with the FUZE? If works, how could I test it and then uninstall it? I like to try for sure.

...I use UBUNTU in an hard drive partition already with Windows on my laptop. I'm downloading now, and then I'll change to UBUNTU OS to search mora about that...

Linux OS are leaner and fastest.
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
For all those who want to actually try to help out with development and wants some help to get started, here is some info:

green over at htc-android.com has just written a really good guide on how to compile the latest android version for the DIAM100 (can be tweaked towards other devices). Check it out here!

Good luck!
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
The Wiki information on XDA is currently in the process of being ported over to htc-linux.org/wiki (The Raph is complete now I think)
[Touch Diamond, MDA Compact IV ROM Development] mike171562:
Untouchab1e, you stated a few pages back you were working on configurations for the DIAM500 color fix, then a few pages later there was a reference to a fix on the wiki, which I cannot find, is there a fix for the messed up colors and screen tap for the DIAM500?
[Touch Diamond, MDA Compact IV ROM Development] jeckhart:
Radio for RAPH800

I recall reading on the list that the radio was working on the RAPH800 from Sprint (also reflected on the wiki). Using the two latest builds from Basalt, however, the radio does not appear to be active. Have I missed a crucial step? Was I mistaken that the radio works on the CDMA models?

Thanks,

John!!
[Touch Diamond, MDA Compact IV ROM Development] balsat:
The radio should work on the raph800!

The 15 April build i released today had some trouble with the radio, that is fixed in this build
[Touch Diamond, MDA Compact IV ROM Development] skiwithpete:
Emulator of the G1

Hey kiddies, looks like we can virtually play with the G1 through a great flash based emulator.

Check out:

http://tmobile.modeaondemand.com/htc/g1/

sooner, not later.

P
[Touch Diamond, MDA Compact IV ROM Development] H3PO:
i read the complete thread. on the irc channel, i was told to try the kaiser bin if i want to start at some point.
[Touch Diamond, MDA Compact IV ROM Development] brumle80:
whoopsie, for more tension ^^
[Touch Diamond, MDA Compact IV ROM Development] jr_daza:
come on guys i want to play with a "diamdroid" :) btw the android os have any keyboard solution for the phones w/o hasdware keyboard?
[Touch Diamond, MDA Compact IV ROM Development] lemagi:
there are news about how to install androis on diamond? ... if you like?
[Touch Diamond, MDA Compact IV ROM Development] sascha.egerer:
? ? ? what ? ? ?
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Probably English by online translator...

There's been progress in finding out memory addresses, gpio's, irqs and some other stuff though. Just not on booting linux (to my knowledge).
[Touch Diamond, MDA Compact IV ROM Development] cr2:
You should check the 'Linux/Androoid on Vogue' thread.
[Touch Diamond, MDA Compact IV ROM Development] Gluck:
In this thread man have G1 on hands and want to help.

Maybe somebody can explain how to get kernel from it?

Or asks questions which help to install android on other devices?

http://xdaforums.com/showthread.php?t=434223&page=2
[Touch Diamond, MDA Compact IV ROM Development] iRiKi:
just found this page, dunno if anyone has found and posted earlier:

http://mobiledevdesign.com/hardware_news/qualcomm_chipset_runs_android_phone_0926/

The first Android-powered mobile phone, the T-Mobile G1 manufactured by HTC Corp., will use a chipset from Qualcomm Inc., a founding member of the Open Handset Alliance (OHA). The Android platform is a software stack for mobile devices that includes an operating system, middleware, and key applications.

As part of its work with the OHA, Qualcomm optimized the Android software by integrating it with the company’s MSM7201A-a.

.. while the Diamond has the "normal" MSM7201A. Should't be that hard to migrate android to Diamond, then ^^
[Touch Diamond, MDA Compact IV ROM Development] sir0x:
At first we must be able to boot any kernel with haret, or has anybody already took this hurdle?
[Touch Diamond, MDA Compact IV ROM Development] djind:
Just read that HTC will not convert Diamond and HD to the Android platform.. So we're dependant on you in this forum!! hehe
[Touch Diamond, MDA Compact IV ROM Development] lexi1986:
Here is an Dutch item: http://tweakers.net/nieuws/56128/htc-geen-android-op-diamond-of-touch-hd.html

In this item HTC tells that they will not bring out Android on the Touch Diamond, Touch Pro. So we must do it ourselfs :)
[Touch Diamond, MDA Compact IV ROM Development] druidu:
I just got my HTC Diamond and I'm ready to start hacking Android onto it :)
[Touch Diamond, MDA Compact IV ROM Development] druidu:
I've done some tests on my own regarding the FB. Dumped 480x640x2 bytes of memory from address 0x1686a000 and loaded it in Photoshop as a raw file and I got a screenshot of my screen. Then I wrote some byte to that whole memory area and nothing happend. But then, when I did something on the device so that it would refresh part the screen, some parts were colored with the color I wrote in the memory.

My conclusion is that that address is only the windows driver's internal buffer and we still need windows code to update it on the screen -- so it's pretty much useless. Reversing engineering the lcd driver from wince might help though (actually, I couldn't find them in the File Explorer, shouldn't they be in /windows/system32/drivers ?).

On the other hand, looking in the latest Android source from git.android.com, there's a device called msmfb (see /drivers/video/msm/) that might be useful (although I'm not sure if it's functional yet).
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
The GETRAWFRAMEBUFFER method should be the correct one. However, as I understood, the MSM processor has graphics optimizations. When new data is written to the framebuffer, the chip must be signalled to update the lcd. So far no idea on how to do this.

You can try adding a sleep of 100 ms after updating the framebuffer. It then does update the screen (or at least it did for me in haret). However, sleep() requires interrupts to be enabled, so it's no use for debugging in haret.
[Touch Diamond, MDA Compact IV ROM Development] H3PO:
sounds interesting... how is this done? can a python haretconsole do this?
[Touch Diamond, MDA Compact IV ROM Development] druidu:
I don't see how that would work. I can wait like forever after writing to memory and it won't get updated by itself. And if I touch something on the device, only the dirty regions will change background color.

Anyway, making the FB work in haret is not the main issue here. We need a working LCD driver which I believe we could test by writing code in haret to reset the lcd driver then try to reinitialize it. I suspect it's similar with Raphael's (it looks like they're identical, just that Raphael has a keyboard). The msmfb code the guys at android.com wrote should be useful.
[Touch Diamond, MDA Compact IV ROM Development] marios96:
So what you are saying is that Android runs on Raphael and it should run on Diamond?
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
The android phone has a different LCD panel. As such, the LCD driver used for the android phone won't be useful. On the other hand, the framebuffer code will be useful.
[Touch Diamond, MDA Compact IV ROM Development] daviss:
I too have no working in radio on the Sprint RAPH800 with the latest build..
[Touch Diamond, MDA Compact IV ROM Development] bombzhome:
yeah, radio doesnt work for me either.. with any build.
[Touch Diamond, MDA Compact IV ROM Development] petay:
I just tried Balsat's build for the 15th of April, im impressed as always, i was able to make and receive calls (with no sound of course) didnt get as far as txt messaging before the battery died but it was good!! just a thought though, i noticed the key maping has changed, up used to be the menu, i had a thought that as the power button on a diamond is unused in android, we could maybe map that to the menu button?? also it moaned at me that the sd card had been removed maybe thats just my default.txt that needs changing i shall have a look.

if you need anyone for testing i am keen and eager with me P3700/DIAM100!!
[Touch Diamond, MDA Compact IV ROM Development] richs1992:
hi all, I have a problem with the 14th april version for DIAM100 because when I have an incoming call, who call listen to only the first ring and after busy; after ,when I go to see to the incoming call received, there is the call.

what's the problem ?? I know that the volume doesn't work, but is this also a known problem ?

I hope you can give me an help asap

bye
[Touch Diamond, MDA Compact IV ROM Development] petay:
the older builds used to do that and i think the ones on Untouchab1e's site may still do

i tried the 15th of april build and it seemed to keep ringing untill i pressed the answer hardkey

I have tried changing my default.txt to get the internal storage to pretend to be the sd card buty nothing has worked yet, 1,2 or 3 for the command line options
[Touch Diamond, MDA Compact IV ROM Development] richs1992:
thanks very much, I'll try it asap

bye
[Touch Diamond, MDA Compact IV ROM Development] bombzhome:
Does anyone have a confirmed working radio release for the RAPH800?
[Touch Diamond, MDA Compact IV ROM Development] qq108108108:
the latest build works very great on diam100,thanks balsat for his effort.
[Touch Diamond, MDA Compact IV ROM Development] lappin:
hi all

i don't understand : does android works on diamond, or only raphael ?
[Touch Diamond, MDA Compact IV ROM Development] balsat:
Android works on Both!
[Touch Diamond, MDA Compact IV ROM Development] bombzhome:
Balsat, does the radio work on the RAPH800? I tried the latest build and it didnt work.
[Touch Diamond, MDA Compact IV ROM Development] GregDDC:
I can also confirm that the radio does not work on my RAPH800 using the 4-17 build. It is really nice though!
[Touch Diamond, MDA Compact IV ROM Development] petay:
i have tried the 17th of april build on my DIAM100 and the radio does work. power checking seems odd though, it shut itself down with a wasning message behind saying its less than 15%, but when i boot back into winMobile the battery has 2 bars (it didnt say a percent but im guessing about 30-40)
[Touch Diamond, MDA Compact IV ROM Development] richs1992:
excuse me petay ,

I alredy have a DIAM100 where I tested the 17/04 version, but the radio doesn't work to me ( only the phone line but no wifi gps bluetooth ).

Have you done anything else after or before booting android ?

I hope you can give me an help

bye
[Touch Diamond, MDA Compact IV ROM Development] jaymit:
wifi, etc dont work at the moment - they're not working on most android ports as yet - I think its only the cell line which works for now.
[Touch Diamond, MDA Compact IV ROM Development] bombzhome:
Yeah, I don't really care for WiFi for now, but I'd like to try it out with the radio.