yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
I packaged it in Windows with WinRAR 3.80. Works fine for me and most likely works fine for most other users :) Can't explain why it doesnt work for you :) filename: android-diam100-20090204.zip
[Touch Diamond, MDA Compact IV ROM Development] mugglesquop:
worked fine for me, unpacked with WinRAR :)
[Touch Diamond, MDA Compact IV ROM Development] Rich1974:
When i unpacked the zip file with WinRar, I got one file. Then I had to put on an extention the the new unpaked file to filename.zip. And Unpack that again, then I got the tmp folder. (Don't know if it is a bug or...)

Is there anyone that hav had åproblems to unpack the config_tool? I can not unpack that one.

Anyway, thanx for all the work you guys do.

------------------------------------------

HTC Touch Diamond P3700, Qtek S200
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Really weird this.. Maybe il stop using .zip and start using .rar instead :)
[Touch Diamond, MDA Compact IV ROM Development] skero666:
I come again with my question...how can we access the sdcard(inernal memory) since android boots automatic and we can't type "mkdir sdcard" in linux? i installed file explorer application and i have a folder called MMC witch is the internal storage, but in the gallery and music player i still can't access it.

10x for all the work u guys are doing
[Touch Diamond, MDA Compact IV ROM Development] jutley:
When i unpacked the zip file with WinRar, I got one file. Then I had to put on an extention the the new unpaked file to filename.zip. And Unpack that again, then I got the tmp folder. (Don't know if it is a bug or...)

Is there anyone that hav had åproblems to unpack the config_tool? I can not unpack that one.

This happened to me to god irm so happy this has been figured out i am going to test it now on my htc p3700 diamond.
[Touch Diamond, MDA Compact IV ROM Development] jutley:
1 - Download the .zip file and extract the contents to your desktop. You should have a folder called tmp there now.

2 - Connect your phone to the computer with a mini-USB cable.

3 - copy the tmp folder to your storage root. The tmp should then be located in [internal storage]/tmp Inside the tmp folder is a boot folder. You may put that anywhere or

leave it in tmp.

4 - Disconnect the usb-cable and soft-reset your Touch Diamond.

5 - Open up the file explorer, find the tmp directory and launch haret.exe and click run.

6 - Wait for android to boot up, and enjoy! At the first boot it takes a while before the android boot screen comes up and then the boot screen (with the glowing android) stays up quite long before you get to the boot screen.

Subsequent boots are faster.

irm not having much luck i have got all the folders in the corect place now but above step

5-Open up the file explorer, find the tmp directory and launch haret.exe and click run

but where is haret.exe please can someone explain where haret.exe is thanks in advance
[Touch Diamond, MDA Compact IV ROM Development] mugglesquop:
in a folder called 'BOOT' in the TMP folder.
[Touch Diamond, MDA Compact IV ROM Development] jutley:
ok thank you found it i have got it to boot and it seems to be stuck on a screen oh wait god damm it its its its android its f....... working you are a god well done
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
DIAM100: mtype + kernel test

DIAM100 + zImage-kll:

This kernel works with mtype set to 1805, but hungs with 1910. Working default.txt:

set mtype 1805
set kernel zImage-kll
set initrd root.cpiogz
set ramsize 0x6000000
set ramaddr 0x10000000
set cmdline "root=/dev/ram0 init=/init console=tty0 mem=76M msmsdcc_id=2 imgdevname=/dev/mmcblk0 imgdevnum=0 imgdir=/tmp msmts_calib=0x7a.0x5e.0x35a.0x37f msmvkeyb_toggle=hide"
boot

DIAM100 + zImage.25-jobo:

I can't get this kernel to boot into Android; either with mtype 1805 or 1910:

* mtype 1805: device hungs in hARET when booting Linux with the "Go go go" message.

* mtype 1910: takes me to a the Linux shell (no LEDs working, but vibrates once). Device hungs at "mmcblk0" - just like before.

Current default.txt:

# Hungs in WM6:
#set mtype 1805
# Hungs in Linux shell:
set mtype 1910
set kernel zImage.25-jobo
set initrd root.cpiogz
set ramsize 0x6000000
set ramaddr 0x10000000
set cmdline "root=/dev/ram0 init=/init console=tty0 mem=76M msmsdcc_id=2 imgdevname=/dev/mmcblk0 imgdevnum=0 imgdir=/tmp msmts_calib=0x7a.0x5e.0x35a.0x37f msmvkeyb_toggle=hide"
boot

EDIT: after I played around with mtype + kernel in default.txt and soft-resetting the device a couple of times I can't do anything in Android (android.core errors + "Force close" messages) when starting Android with mtype 1805 and zImage-kll. So it seems the images becamse corrupted?
[Touch Diamond, MDA Compact IV ROM Development] jutley:
all working quite well but the virtual keyboard when you try to move it messes the screen up and the keys are increadbly small and how do you minimise the keyboard?
[Touch Diamond, MDA Compact IV ROM Development] balsat:
Wiki.

Untouchab1e maybe you can copy the wiki to a Howto.txt and put it in your zip file, just sow we don't have to answer stuff like "How can i enter sim code" etc.
[Touch Diamond, MDA Compact IV ROM Development] c4software:
@sibbor, don't forget to poweroff correctly android before soft reset.

Long press hang button and select power off.
[Touch Diamond, MDA Compact IV ROM Development] mugglesquop:
ah nice one - didnt know about this :)

cheers
[Touch Diamond, MDA Compact IV ROM Development] gildenman:
Hi,

Firstly, thank you for all the work you have put into this. I never expected this to work on a Diamond and I continue to be surprised by your selfless contributions here.

I got the same problem as this guy. Tho I have my SIM in with no PIN code required.

I can get into Android. Have a look around. I disabled the screen timeout.

However, I can't seem to get out of some menus. So I've tried pressing the the 'back' key and the screen fades to black. Nothing I do except hitting reset will get it out of this.

Tried other times and always eventually hit a point where I'm stuck in Android and have to press a key at which point fade to black again.

Any ideas?

Forgive me if this has been answered, cos I couldn't find it.

Many thanks.

BTW this is with android-diam100-20090204.zip
[Touch Diamond, MDA Compact IV ROM Development] mugglesquop:
use the direction buttons :) down i think (might be left) takes u back to the previous menu.
[Touch Diamond, MDA Compact IV ROM Development] dejant_9:
yes!! i finally found the solution to unpack the diamond configurator...unpack with 7-zip (the only one who want unpack without error..), then rename the file without extention to ".zip" and unpack it with winrar..
[Touch Diamond, MDA Compact IV ROM Development] jasonmfarrow:
O2 XDA Ignito (HTC Diamond) not yet working

I have been testing the builds by lavender.t (wiki page) and c4software (post 1975).

The lavender.t will boot but dive down to any app and you cannot get back as the use of any h/w keys hangs.

c4software just will not boot. It does not mount the internal storage and then cannot mount the system images.

BTW. HARET does not see my device as a DIAM100 but a generic device.
[Touch Diamond, MDA Compact IV ROM Development] jutley:
Testing Results

ok here are my testing results so far

1 you cant change the date or time keeps reverting back to default settings

2 when holding down the end call key it powers down but gets frozen have to reset.

3 when the screen timeout shuts the screen you cant wake it up but can have on all the time but this drains battrey great if we can figure this out.

4 the virtual keyboard above the one with the tiny buttons i think to type command promps when you try to move it about it messes the screen up and you cant minimise it,

5 when i make a call the recievers phone rings but nothing can be heard in my earpeace incall volume sound not present,

6 No sound what so ever,

7 No vibration when enabled,

8 wifi does not start when enabled,

7 GPS does not work

8 cant seem to get a data connnection going will try o2 setting and try again,

9 cant get capitals when the shift button is presses when using the main keyboard,

10 cant access the internal storage or phone memory,

11 no mac address,

12 no bluetoothe,

this is all for now hope we can get some of thease things working soon and maybe one day a rom install file to overite the htc rom thease are finding whi;st testing today but great work to even getting it to boot up keep up the great work guys.
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
re re re re

What I can say at the moment is that .25 kernels built with htcraphael_defconfig don't boot with MTYPE=1805. I don't know why. It used to work. With MTYPE=1910 the kernel will boot on a Diamond but run into trouble as it thinks it runs on a Raphael. I shall built one with htcdiamond_defconfig and put it online. I only have a Raph100 to test with.

The interesting columns would be the phone model, msmsdcc_id, imgdevname/num, and maybe good working msmts_calib. The values in the original package are good for Raph100.

If you can telnet into your phone, you're root and you can delete everything (even if you don't intend to). As far as I know, youre not root in Term.apk Alternatively, you could mount the system or data image onto your host and the modify them.

Creating the /sdcard directory won't help. Besides, android creates it on boot. The problem is that it tries to mount /dev/mmcblk0p1 (Which is right for Raphael but not for Diamond. I modified it to do that. Originally it would be correct for Diamond... sorry :D) This is controlled from /system/etc/mountd.conf Maybe a symlink from /mmc to /sdcard would work, but I believe that Android won't believe it's there if it hasn't mounted it itself.

&

How about a nice hot cup of RTFW! (There you will find that you can change the End Button Behaviour in the Spare Parts app, and also how the keys on the navi are mapped for kernels that don't have full navi support.)

Since we can now specify the imgdir from the cmdline it doesn't necessarily need to be /tmp anymore, as long as you specify where the images are located.

The app copying does not rely on the kernel. It is in the init script on the roof fs image.

The 1st time you boot, it takes a while before the android boot screen comes up and then it takes another while for the home screen to come up. (Not more than 2 or 3 minutes or so though.) Subsequent boots will be faster.

Sorry for the real estate.. hopefully it helps understanding how stuff works.. ..a bit.

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] c4software:
@jobo What is the IP of phone? i try to connect in telnet, and always say connection refused :(
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
htcdiamond_defconfig does not exist. So thats not it.

The phone is 192.168.0.206. You should sudo ifconfig usb1 192.168.0.200 on the host your usb is connected to.

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] balsat:
The htcdiamond_defconfig did exist before the git got upgraded to .27
[Touch Diamond, MDA Compact IV ROM Development] skero666:
Stupid request

PLEASE! in the previous build for diamond it's a wallpaper with Ecko Raw and Uncut (it's the last one in wallpaper gallery) and in the last build from 04/02 it has been removed. Please someone upload that wallpaper beacuse i am searching for it for days, i have a problem with this wallpaper :)
[Touch Diamond, MDA Compact IV ROM Development] jutley:
games

ok i have got pacman working fine on android you use finger swipe to control though the screen needs resizing for the htc diamond if someone can help here i can post the file and also connect 4 runs well,opera mini 4.2 also works but i cant seem to get connected on my diamond yet.
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
Right .. thanks .. switching to .25 branch ... updating some 20000 files ... checked out ... kernel is building ... and building ... and here it is. Diamond config.

It's in the repo (history) along with the entire Android source. Keep in mind that the wallpapers in the Android repo are too small for our screens. In the Android I built last week, I scaled all wallpapers to be 640 high so they look good on our raph/diams.

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] goga2002:
Hi, I have a problem here. When I enter my PIN code, I wrote here is, (Incorrect PIN code!). What could be the problem?

Sorry for my English.
[Touch Diamond, MDA Compact IV ROM Development] jutley:
why does the android configuration tool for htc diamond say build vershion 20090203 when i have the latest one already 20090204 it seems to think its a older vershion i am using configuration tool 0.4.0.0 and the tmp folder loaded in it is build 20090204 i downloaded it today 4/2/09 is it me or is it no updating the vershion number
[Touch Diamond, MDA Compact IV ROM Development] gebruikershaes:
Why does no1 read the god damn wiki.. :F
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
This image works out well for my DIAM100.

Updated the wiki with hardware differences and configurations, but I need help to get proper values in there for all sorts of phone models.
[Touch Diamond, MDA Compact IV ROM Development] goga2002:
Thx.

Problem solved by disabling the PIN code request.
[Touch Diamond, MDA Compact IV ROM Development] c4software:
The New image works fine on my Diam100 too.

PS: and i always can't acces to my phone via usb, my host have correct ip (i think the phone too), but i can't ping it.
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
Does it merely boot, or do you have working Navi and LEDs? For me (Diam kernel with mtype1805 on a Raph100) the Navi and LEDs don't work.

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] jutley:
how do you aply the new imiage what do i have to change
[Touch Diamond, MDA Compact IV ROM Development] skiwithpete:
anyone wanna post a vid of the latest? and then link it on wiki?
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Thanks for the kind words! In order to prevent the screen fading to black when hitting the end key, you should go into the "spare apps" application and map the end-key to "Home", so that when you press it, you are thrown back to the home screen. The reason the screen fades to black is that by default, the end key puts the device to sleep, and since we dont have power management up and running yet, this messes things up.

So, use the spare apps program and your problems will be solved :)

Have a nice evening! (Ive been taking the afternoon and evening "off" due to my birthday, but just thought I wanted to answer this one) :)

Kind regards!
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
I can definetly make a quick vid of my Raph100 running the latest build, and Il can power up my Diam100 as well I guess, although it will look exactly the same :) I can have it up tomorrow evening ;)

Good night!
[Touch Diamond, MDA Compact IV ROM Development] jutley:
quick question whats the diferance between diamond 100 and diamond p3700
[Touch Diamond, MDA Compact IV ROM Development] balsat:
There is NO difference!
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
LEDs doesn't work. Where should the navi work?

EDIT: and yeah, I was able to "copy" apk packages from the internal storage. Minesweeper ;)!
[Touch Diamond, MDA Compact IV ROM Development] c4software:
Its can be cool if in the wiki we have some links to apk's for try ? no ?
[Touch Diamond, MDA Compact IV ROM Development] Rennat:
Can someone tell me what each grouping of the calibration codes are which in the 'default.txt' because on my Diamond's the screen is flipped so the top is the bottom and bottom is the top. But the right and left are ok.

I have tried setting the calibration during booting but the keyboard isn't working (key turn red but inputs nothing) so I can't boot android.

Thanks a head of time...

EDIT:

Never mind I found the answer on another website... Switched 2nd and 4th grouping.
[Touch Diamond, MDA Compact IV ROM Development] c4software:
#developpers.

I'm currently testing somes apps from G1, and the highter resolution of Diam & Raph its really a problem. A lot of apps are made for the resolution of G1.

its can be fine if we can pass a parameters to set the screen resolution on boot?
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Could you name which apps have problems with the resolution? Those apps are in my opinion poorly developed as Android developing allows for pretty nice resolution neutral designing through .xml, so It would be interessting to see if the popular apps such as ChompSMS, TuneWiki and others have the same problems.

My point being that apps with resolution problems are designed for the G1 and the developer just havent done it properly ;)
[Touch Diamond, MDA Compact IV ROM Development] c4software:
Yep, the problem come from the developpers (some of these don't make there app screen independant). For example pacman.apk.

i prefer an highter resolution but for some case (and for the begining, after i think developpers respect the independant screen resolution) its can be cool to switch the resolution to lower.
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
I am pretty confident that the decent apps are resolution independant, so I dont think there is a very big problem, and definetly a low priority one ;)

The only problem I am having with the high resolution is the fact that draggin down the notification curtain is significantly more difficult than on my G1 ;)

EDIT: Try Ringdroid ;)
[Touch Diamond, MDA Compact IV ROM Development] jutley:
i am going to donate soon keep up the great work
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
No worries! Hope things are working out for you finally ;)
[Touch Diamond, MDA Compact IV ROM Development] c4software:
Yep dragging top bar is very difficult.(easy only with stylus).

PS: G1 have a trackball, diam and raph don't have it. maybe the trackaball can be replaced by the sensitive panel no ?
[Touch Diamond, MDA Compact IV ROM Development] jutley:
yes i really enjoy playing with android 1.0 on my diamond and cant wait for the next release getting the wakeup feature going would be ace
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
For those of you who want to play around with a few apps, I just published a little article on Connect-utb with a few links to a few applications. Havent tested them myself, so not sure how well they work (I reckon skype and ringdroid wont be much use yet, but maybe fun to play with anyhow).

Read it here

Enjoy!
[Touch Diamond, MDA Compact IV ROM Development] jutley:
if you hold the drop call key on diamond it trys to power of but hangs a soft reset is the only way out wouldnt it be great if it shuts down and returns back to wm6.1 home screen one day i hope.
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Since we dont have power management working yet, Nothing related to device sleep or power on/off is working yet as we are currently relying on Windows Mobile to do all the initializations before booting into Android.
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
diam navi

Ok, that couldn't have worked, as the Navi driver had never been added to Diamond :o, only to Raphael. (When I say "the Navi works" I mean you can use Home/Send/Left and Back/End/Right separately and the wheel scrolls through menus. :cool:) I now replaced the keypad (gpio matrix) driver with the navi driver in board-htcdiamond.c and added maejreps i2c LED chip driver.

When I boot the resulting kernel (replaced same link as before) with mtype 1805 (on my Raph100) , I have working Navi and LEDs. I guess this will work on a Diamond as well (please confirm).

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] skero666:
Test result on my diamond (DIAM100):

-Touch screen not working (i don't know why)

-Navi and LEDs not working

-Key's:UP/UP, Down/Down, Left/Left, Right/Back, Back/Back, End/back, send and home/left, enter/enter

-no network signal (i have signal with Untouchab1e build)

this is a quick test, not much time right now
[Touch Diamond, MDA Compact IV ROM Development] dejant_9:
exactly same results for my diam100 with the latest build for diamond (connect-utb) and this zimage
[Touch Diamond, MDA Compact IV ROM Development] uachi:
great work

i have run the android-diam100-20090204 and it works fine.

even send and receive sms.

i wish there will be no answer in the future for "'pin problem on Android''

it is not a big problem to read the wiki
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Did you have network signal before booting Android? Since it all depends on what WinCE does before you boot up Android (meaning that putting your phone in flight mode is not a good idea), it might be the cause as well!

Just curious ;)
[Touch Diamond, MDA Compact IV ROM Development] skero666:
Yes, full signal...
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
Perhaps it would make more sense that someone with a Diamond tries this.

Here is a diff against the latest (at time of posting, 090205,16:00,CET) git state of the .25 branch. It looks big but that's because it adds a bunch of new files.

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] jutley:
when i dont have signal before i boot up android i wont have signal in android at all but if i have signal in windows first then boot my signal is fine in android i can confirm this as true
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
Just tested the new image out, and noticed the same thing as the others:

* No LED's worked in the Linux shell (don't know how it's supposed to look)

* I was able to boot into Android

* Touchscreen didn't respond to clicks, although I'm able to navigate to a certain point with the hardware buttons

* Also I didn't get any signal in Android, even though I had it in WM6

Update: I'm able to move around the virtual keyboard in the Linux shell. When the Android boot screen shows I can barley move it, and once Android booted the virtual keyboard cannot be moved at all - since the touchscreen doesn't respond to clicks as told earlier...

The previous zImage worked out "better" (depending on what you test ;))
[Touch Diamond, MDA Compact IV ROM Development] daronnz:
Hi folks,

first of all i'd like to thank you all for the good work, very good job.

On my diam100 the newest build 20090204 with the zImage-diam.25-jobo kernel runs very good and relatively fast.

Her is my default txt:

set mtype 1805

set kernel zImage-diam.25-jobo

set initrd root.cpiogz

set ramsize 0x6000000

set ramaddr 0x10000000

set cmdline "root=/dev/ram0 init=/init console=tty0 mem=76M msmsdcc_id=2 imgdevname=/dev/mmcblk0 imgdevnum=0 imgdir=/tmp msmts_calib=0x7a.0x5e.0x35a.0x37f msmvkeyb_toggle=hide"

boot

The Calibrationstring which is posted on the wiki (msmts_calib=0x81.0x393.0x358.0x7D) isn't working for me (seems all input on the touchscreen is "upside down")

does someone have a tip how to include the mkdir /sdcard on boot, so we could play around with some additional software?

Keep on running!

Thanks
[Touch Diamond, MDA Compact IV ROM Development] dejant_9:
seems to work with the latest build for diamond..I don't know why it dosen't work before...