yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] chowdarygm:
i am trying to boot the 1.6 build on my DIAM100 but getting stuck up at

"Kernel BUG at kernel/workque.c:188!"

any idea on this?

edit: Found it out....forgot to change the zIamage to DIAMOND one :D .... Testing
[Touch Diamond, MDA Compact IV ROM Development] Critical_Impact:
I tried out the 1.6 from babijoee and my front screen buttons do not work. Seems smooth using the touch screen though.

Any help with this?

I'm using Rapheal 100
[Touch Diamond, MDA Compact IV ROM Development] gajdik:
Best build so far (this 1.6) on my DIAM200. Except data connection which causes freezing... Anyway thanks for this
[Touch Diamond, MDA Compact IV ROM Development] akil3x:
I'm using Diam 100 and this build don't even start :(

Make automatically soft reset..
[Touch Diamond, MDA Compact IV ROM Development] flymanj:
Have you changed the statup.txt file?

Mine is with the following content:

set ramsize 0x08000000
set ramaddr 0x10000000
set mtype 1805
set FBDURINGBOOT 0
set KERNEL zImage
set initrd initrd.gz
set cmdline "init=/ console=tty0 mem=76M msmsdcc_id=3 imgdevname=/dev/mmcblk0 imgdevnum=1 imgdir=/ ppp.nostart=1 msmts_calib=115.105.863.911 mddi.width=320 mddi.height=480 lcd.density=240 msmvkeyb_toggle=off"
boot

And the Android starts fine.

I'm not able to start the WiFi but I'm sure that and this one will be managed soon.
[Touch Diamond, MDA Compact IV ROM Development] akil3x:
I'm gone try that :)
[Touch Diamond, MDA Compact IV ROM Development] prinex:
Same for me on the DIAM100.

I noticed that if i delete the data file, then the buttons work again. But after setting Spare Parts -> end call key to home and disabling display timeout, at the next reboot the keys are gone.

Also by receiving a call android goes in sleep mode (stripes etc).
[Touch Diamond, MDA Compact IV ROM Development] c4software:
Yep Hard key seems a little bit buggy.
[Touch Diamond, MDA Compact IV ROM Development] edgevision:
On a RAPH800, using the RAPH-specific startup.txt, this does not boot. Just turns phone off after the

"xxxxxxxxxxx

xxx A N D R O I D xxxxx"

part.
[Touch Diamond, MDA Compact IV ROM Development] chowdarygm:
i was able to get android booted on my DIAM100 successfully....hardware buttons are little messy but i dont know why the device is getting freezed every 4-5 minutes after starting.....

is it cause of device trying to make data connection????

if we can get data connection active without problems, i think this build will rock our devices even without wifi and bluetooth.......

hoping to see it soon :)

and thank you babijoee for the awesome build....
[Touch Diamond, MDA Compact IV ROM Development] babijoee:
Good to hear people are having positive experiences. Remember to change the files accordingly to your device.

zImage and startup.txt must be changed if you are using a diamond.

This build could last soo much longer if the entire panel powers off as someone mentioned before just the backlight goes off but the screen is still displaying.

:D

I'll keep working on improving my builds and modifying it to be more stable and faster. :)
[Touch Diamond, MDA Compact IV ROM Development] chowdarygm:
you can replace the startup.txt file with the one attached to use this 1.6 build on diamond(DIAM100)......

and replace the origianl zImage file with the "zImage-Diamond" one in "babijoeeDonut1.6pack\startup-configs\zImage" and rename it to zImage
[Touch Diamond, MDA Compact IV ROM Development] r_aymond:
Trying the 1.6 version now......

And....

the Babijoee pack can now also be downloaded from here:

http://jinxworld.net/diamondroid/babijoeeDonut1.6pack.rar
[Touch Diamond, MDA Compact IV ROM Development] Eligos4ever:
Any luck with the Diamond 500 and Donut 1.6?

If so, could someone post their Zimage and startup file please?

TIA
[Touch Diamond, MDA Compact IV ROM Development] chowdarygm:
did you check with the startup.txt file i posted in this page???
[Touch Diamond, MDA Compact IV ROM Development] chemical1979:
Btw, this is the first kernel that I tested on my DIAM300 that is able to cleanly shut down the phone and power it off. Contrary to your statement, btw. The provided zImage in the root is the "best" kernel I've ever used.

Power Management really is at the same state as WM here.
[Touch Diamond, MDA Compact IV ROM Development] prinex:
Update: by setting the end call key to Nothing the keys are alive again.

GPRS works but freezes after a while.

Battery loading from usb cable (when connected) works provided activesync is selected.

Getting there !
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
Just did a quick thread search for raph500. I edited the wiki(the xda one) with an unconfirmed mtype for the raph500 which seems to still be unconfirmed. If anyone can post a reply "yes/no, android (doesn't) boot/s with that mtype on my raph500" or shoot me a pm to confirm that this info is correct that would be awesome. Also, if you are running a raph500 and know which calibration settings you are using and could post those that would be super badass.

TIA,

Willis

Edit: Wow, this is my 50th post right here!! Not sure if that includes posts deleted by mods or not. Would probably be closer to 100 if they were since I'm such a grumpy bastard most of the time.

Edit2 @Babijoe etc: Just wondering... I noticed in the startup.txt posted with your android build that it has all the msmdcc_id info, imgdevnum etc and in my old config I had removed all of that and had android booting. My old startup.txt doesn't even have imgdevname=/dev/mmcblk... Just mtype for diam500(2040) and the lcd lines, ppp lines and of course everything at the top down to setting the initrd. Could this be a problem? Does this info actually have to be set or is it detected based on mtype now?

Edit3: Getting the usual problems with the 1.6 package on my DIAM500. With mtype set to 2040 it boots until it's supposed to mount the sd card and I get "Waiting for sd card" messages scrolling by. With mtype set to 1805 it stalls out at the console handover "console handover: boot [htc_fb-1] -> real [tty0](slightly edited startup.txt replaces htc_fb-1 with htc_fb0 but stalls @ same point)" is the last message I see, only errors are mmdi.width, mddi.height, lcd.density are all ignored as "unknown boot options". Any help/push in the right direction would be appreciated or perhaps if there's a diam500 owner out there who has this build booting they could post their startup.txt so I can compare with mine and get a more specific idea of what's going on here.

Basically I can get by the console handover freezing by setting the mtype to 2040 and it doesn't detect my mmc( I just saw "error -22 whilst initialising sdio card" followed by power stub message then waiting for sd card) or get stuck @ the console handover with mtype 1805 (after double vibration) which would probably detect my mmc but have messed up colors in android (hard to tell since the boot console has always been correctly colored up until the fb handover :P).
[Touch Diamond, MDA Compact IV ROM Development] MacWell:
hi guys

I have a question,

I want to test if I could get android on my touch diamond..(like you all are testing;))

but I don't want to be without a proper working phone.. so is there a way to make a complete backup(not just my files but also the windows mobile)

because i also want to test the things you all are doing.(I haven't read all of the posts on this thread because it has been more than a year and I haven't got the time to read more than 400 pages(A)) please help me!

Greets from a Dutch guy(explains my bad English)
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
I find usually a quick search of this thread or one of the wiki's listed in the first post or a quick check @ connect-utb etc will usually resolve my issues and if not I make a post AFTER I try and figure it out for myself. Basically, you are asking someone to spoon feed you on how to backup your personal info (hard reset restores windows mobile? zomg ...) and then ?

Perhaps people releasing android images/packages could add a README with something along the lines of

_______________

Extract the package to the root of your memory card, edit your startup.txt to match your phone and run haret.

_______________

Things haven't changed in a year ...
[Touch Diamond, MDA Compact IV ROM Development] MacWell:
No i know the hard reset function but if i do that i have to update the rom and personal settings.. i'm looking something just like a ghost image for a PC but then for my touch diamond.

*edit* ... if it is possible becouse if it isn't i will do the hard reset thing;)
[Touch Diamond, MDA Compact IV ROM Development] rattenfanger:
You are asking this at the wrong place. But you can try using SPB Backup, Sprite Backup or one of the others.. They all can do complete system backups.

Rene
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
... go use google and search for ppc backup software? Hard reset restores winmo to it's freshly installed condition, I'm not sure what you mean about updating the rom but if you're talking about installing additional software after a hard reset check out some of the auto installers available for winmo... basically you're asking a bunch of questions about how to backup your windows mobile phone in an android thread and obviously haven't searched ANYWHERE at all to come up with the answers yourself. Good luck with your search.

Regards,

Willis

Again, try google ... if you put a little thought into your search terms you'll be amazed with the results/answers you'll be able to come up with all by yourself.
[Touch Diamond, MDA Compact IV ROM Development] chowdarygm:
you said you wanted to test the android build, so that u need to backup right? but for testing android i dont think u need to hard reset you device.......

i never encountered problems with my WM ROM even if something goes wrong in android testing

but as you asked for back up, yes its possible.......you can use SPBBackup software to back up the status of you device with your settings and everything.....

but you need to restore the backup only on the ROM on which you took backup.

it will restore everything completely like the status of the device when you took backup
[Touch Diamond, MDA Compact IV ROM Development] babijoee:
Seriously there isnt anymore point in answering questions to people who dont even bother to read a couple of pages or even do a search. :mad:

I suggest all answered can be re-directed to the raph/diamond wiki since tuxhero hasnt replied to my pm or updated first post. despite him still being active on the forums. :(
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
Indeed, that sounds like a good answer. I would also suggest changing the title of the thread from [PRJ][OS]Linux and Android on HTC Diamond "NOT YET WORKING" to something like "[PRJ][OS]Linux and Android on HTC Diamond "NOT YET WORKING"/NOT READY FOR USERLAND or END USERS". Hopefully people who have never booted linux on a pc before or anything close to that will realize that that would be them(in the old days weren't end users = noobs?)

Pretty much I'm seeing a lot of this here ...

Seems pretty lazy to me, no wonder everyones so sick of answering the same question over and over and over and over and over and over and over and over and .... you get the point. Feel free to attach my image to the first post ... I bet the same people that were confused before will still be confused after reading this ...

Edi: I know we were all somewhat spoon fed a lot of what we know about computers. IMO best way to spoon feed is show people how to do it themselves and then throw a dump on their heads when they don't do it.
[Touch Diamond, MDA Compact IV ROM Development] Nakebod:
Is it me or is WM feeling slower every time I boot Android? :D

Tried babijoee's pack today (With startup.txt adjustments for Diamond).

Noticed @ small typo @ boot:

Dount build detected

Experience on my Diam100 so far:

Sound is making cracking noises.

Data connection isn't working (yet), it shows 3G sometimes, but after a while it seems to freeze.

I did also notice that GPS was enabled (By default?), device freezes when trying to use it :(

I don't know if this zImage was built for the Diamond, if not, you can probably ignore my text :p

At this point, Android 1.5 was a little bit better usable for me.

But damn, those speeds, nice, very nice :)
[Touch Diamond, MDA Compact IV ROM Development] babijoee:
Yeah those things were reported on my post. For me i just disabled GPRS and the build has not crashed ever since. Its very stable and fast :D
[Touch Diamond, MDA Compact IV ROM Development] Tenny:
I'm still having the same issues with the DIAM500. I honestly don't know if mtype 2040 is the right mtype for the DIAM500. I agree the colors work properly, but it assumes that we have a SD card. Maybe it's the correct mtype for Verizon's Diamond (I think DIAM300) which is CDMA but has the SD Card.

So I put in MrPippys zImage for the DIAM500, kept mtype at 2040 and I am getting:

msm_12c msm_12c.0: Warning bus was busy

It will be busy for a while, then get something done, then busy again, then get something done... It's been sitting at the current one for about 5 minutes now... Not sure if it'll get past it.
[Touch Diamond, MDA Compact IV ROM Development] Zeman4323:
Diam 500

Yea, same here. I am going to keep messing with this, but I am having no luck with the 2040 mtyle due to the SD Card Looping issue.
[Touch Diamond, MDA Compact IV ROM Development] aeropatel:
had that problem with 1.5 on the Sprint diamond... 1805 hangs and 2040 waits for sd card. I tried the following startup.txt and it worked. I don't know if it'll work with 1.6 but give it a try and let us know. here it is:

***

My 1.5 package was from http://connect-utb.com/index.php?op...=file&Itemid=68&id=29:android-for-htc-diamond. Also, i should point out that I replaced the zImage from the 1.5 package with the one created by MrPippy (http://xdaforums.com/attachment.php?attachmentid=226100&d=1252565799). i guess it was specifically for the DIAM500. but, that combined with the startup file below worked for me.

***

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

set RAMSIZE 0x08000000

Set ramaddr 0x10000000

set MTYPE 2040

set KERNEL zImage

set initrd initrd.gz

#

# The following kernel parameters are useful

# ppp.username - The username used to connect to the network when dialing #777

# ppp.password - The password used to connect to the network when dialing #777

# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller

# pm.sleep_mode - The mode used when the phone is off

# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,

# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt

# Default is 3, use 0 for best power savings

# board-htcvogue.panel_type - Panel type used to power the panel off and on

# 0=Don't power off the panel (Default)

# 1=Hitachi 2=Topoly 3=Samsung

# mddi.width - width of the scaled display

# mddi.height - height of the scaled display (these should be multiples of 16 for the camera to work I think)

set cmdline "msmts_calib=0x81.0x393.0x358.0x7D msmvkeyb_toggle=off mddi.width=320 mddi.height=480 lcd.density=240 ppp.apn=sprint ppp.username=username ppp.password=password no_console_suspend"

#set cmdline "no_console_suspend"

# fbcon=rotate:1

# console=ttyMSM0"

Boot

mkdir /proc

mkdir /sys

mount -t proc proc /proc

mount -t sysfs sysfs /sys

mount -t tmpfs tmpfs /dev

mdev -s

"ls -l /dev/mmc*"

--------------------------------------------------------------------------
[Touch Diamond, MDA Compact IV ROM Development] aeropatel:
try the startup.txt in my post above... i had that problem with 1.5 and this startup file seemed to have fixed it.

Also, I wonder if the zImage file has to be specific to the DIAM500. If thats the case then startup file won't be a factor. However, i have no idea how the zImage (or linux/android for that matter) works so don't take my word for it.
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
Ooops, double post, please delete
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
The default configuration build the zImage with both CDMA and GSM support.

Try pre-accelerometer version (before 4 october).
[Touch Diamond, MDA Compact IV ROM Development] GlemSom:
zImage autobuild system update

"Donut 1.6" and "SquashFS" seems to be buzzwords right now in this thread! :P

So, I decided to do a few updates on the autobuild system.

The difference since last update is:

- All zImages are now located on another storage server (I have 1G of diskspace - that should be fine!)

- Introducing two new branches, Diamond and Raphael builds with SquashFS 3.4 support! :D

- [ A lot of internal changes to support the new storage host... error handling... optimizing... ]

The SquashFS support is patches using http://glemsom.anapnea.net/android/squashfs-htc-msm-2.6.27.patch

(note: This patch also patches the default config files for both diamond and raphael)
[Touch Diamond, MDA Compact IV ROM Development] toastcfh:
ive tryed a bunch of things to get the latest respatories to bot on the diam500. ive changed the pdata for the mmc to read like its a diam100 mmc. doin that gave me a a kernel panic on the batery. so i config the pdata for the batery.. those changes got me closer but it still crashes. my problem now is i need to use telnet or haret console and for the life of me cant get my phone to sync. so now im stuck. i cant see whats makin this thing crash. if someone could pm me and try help me get this phone to sync that would be great. but yeah something is screwed with the mtype 2040
[Touch Diamond, MDA Compact IV ROM Development] ElCondor:
I get:

mount: mounting /dev/block/loop0 on /data failed: invalid argument
Failed
Failed to mount /data
/bin/sh: can't access tty; job control turned off
/ #

Is this because of WM 6.5.1?
[Touch Diamond, MDA Compact IV ROM Development] toastcfh:
idk... but i get the samething. i have a diam500 running 6.5
[Touch Diamond, MDA Compact IV ROM Development] Tenny:
Alright, I tried the 1.6 package w/ MrPippy's zImage, and your startup and same thing :(

Going to continue playing around with it
[Touch Diamond, MDA Compact IV ROM Development] boas:
I'm not sure in what extent you now of this, but DPAD have some kind of issues. It got solved by deleting the data.img and booting again. But at start up there was a process handling the keyboard that crashed, some lagg was experienced with that. And if taken in to air-plan mode it cant be take out from it. I have read everything about your build, but either missed the notice about the low resolution. Tried to fix this by changing the startup.txt but nothing happened.

Good build, looking forward on future builds. Very fast version but not even close to be as nice as the xRom.. :p

Keep it up!

(rebooted, air-plane mode could then be disabled, but homescreen is VERY laggy from time to time.. =)

Phone rebooted by it self, unknown reason why..
[Touch Diamond, MDA Compact IV ROM Development] chowdarygm:
VOGUE detected????

just now i noticed one thing....when i am booting android on my DIAM100.....why is it showing "VOGUE" detected???????? :confused::confused:
[Touch Diamond, MDA Compact IV ROM Development] IceBone:
I tried it too. It's very fast and screen wakes up, but I have to have data, so I'm back to the hero build, sorry. But I hope the two's strong points and working features can be combined and the faults removed soon. :)
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
Here is an android build with Wifi and bluetooth available! http://husson.hd.free.fr/Android-diam-bt-wifi.7z

As usual, please mirror.

It is based on 090909 from connect utb, and don't try any other image, it won't work.

Unless you know what you do, you won't be able to get wifi by using only 3 of the zImage, initramfs, rootfs, system.

WiFi can't be stopped (or you can somehow, but it won't restart while still consuming some extra power), and sometime (1 out of 20 times ~), wifi won't start, just reboot (or unload the wl1251_sdio driver from the console).

Bluetooth has only 115200 baudrate, handfree won't work. A2DP might work, but because of the available rate, it don't think it will.

Please note that this release has the usual bugs like data connection being hard to get (i just found why, i'll try to fix it), or suspending screen reboots the phone (or make android unusable).

As usual, thanks goes to cr2, dcordes and friends.

If some android builders want to know how to get wifi in their rom, PM me, or go in #htc-linux.

PS:I know i said i'll enable accelerometer, but i haven't succeeded yet.

PPS:Might work (without hardware keyboard i think) on raph too.
[Touch Diamond, MDA Compact IV ROM Development] aussiewan:
Free storage space

Free storage space for Android stuff! :)

I have web hosting with 300Gb capacity and 3Tb transfer a month, which I barely use... so feel free to store any Android related stuff here. I would love to see my traffic graphs actually show something for a change!

http://www.cobaltcode.com/fileupload/

Log in as android, password xda

If you click on file/folder names, it lets you do actions such as rename/delete. Click on the icon for files/folders to navigate/download.

Click on the Browse button at the top to go back to the top level.

I could not upload a system image - connection timed out - not sure if the server has a problem with large files or not. If so, then I might have to set up FTP access for anyone who wants to upload larger files. Just let me know :)

IMPORTANT: Just remembered by web host is fussy about file extensions - can only have .html, .htm, .zip, .rar, .txt, etc... common web file extensions... so it doesn't like .sqfs or .img for example. I don't know WHY they do that, but yeah. I think this only applies to PHP access, so I will test FTP access later and see if it has the same problem.

UPDATE: YAY! FTP doesn't have the file type restrictions! Sorry for anyone who's been playing already.

ftp.cobaltcode.com

username: ccandroid

password: passw0rd! (that's a zero and an exclamation mark - love enforced minimum password requirements)

Also, you can browse to here:

http://www.cobaltcode.com/fileupload/data/Android/

instead of logging in to the web-based file manager.

Use it and abuse it - within reason :) Please only store Android related files. If other stuff starts appearing, I will change the password and only give it out on request.
[Touch Diamond, MDA Compact IV ROM Development] c4software:
@phhusson Thanks dude :). And Great Great Job ;)

How do you do this ? made some new driver in Android (in sys/class ?)
[Touch Diamond, MDA Compact IV ROM Development] zenulator:
is it time for me to switch to raphael/diamond?
[Touch Diamond, MDA Compact IV ROM Development] aeropatel:
delete the data.img file from the root folder and try again.

also, i don't know if MrPippy's zImage file will work with 1.6. But, the only way to find out is try.

let us know how it goes.
[Touch Diamond, MDA Compact IV ROM Development] aeropatel:
try deleting the data.img file and run it again. see if that works. what startup.txt file are you guys using?

if your default startup doesn't work, use the startup.txt i posted and see if that helps.