yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] s-diamond:
ok now works.

thanks
[Touch Diamond, MDA Compact IV ROM Development] killzusall:
Ok, so I and many other people said about a new thread, phhusson and a few others said about a subsection instead, people are saying they need a guide, people are moaning about seeing people asking for help (wonder how many of the moaners have never asked for help), but if you want to start out and you're faced with 510 pages of jargon you're gonna ask questions, because the first post which could be updated to give info doesn't even want to talk android.

Anyway, a subsection sounds like a good idea.

-Android for Diamond/Raphael

|

+-Project summary (what android is, aims, progress etc...)

|

+-Guide (also explaining different startup.txt's and how to sort out wifi calibration file etc....)

|

+-FAQ

|

+-Request Help

|

+-Device configurations (DIAM100, DIAM400, RAPH800 etc....)

sorry if the formatting looks bad did it on my phone
[Touch Diamond, MDA Compact IV ROM Development] kistler82:
agreed

I totally agree - while it's easy to say "rtfm" (can i say that here?) There isn't really a manual to read.. a quickstart guide with a good FAQ would be very nice and would cut down on the flood of the same questions over and over.

On another note - anyone heard any news on develoment - it's been 10 days since I've seen a commit to http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-msm-2.6.27 ...
[Touch Diamond, MDA Compact IV ROM Development] ydoucare:
It shut down again on the 2nd boot (didn't touch anything)....i'll go for a third...

edit: no go on 3rd boot either. *sigh* ultra frustrating

What does your startup look like? Are you using the one MrPippy posted a while back, or the one that came with the package?

So it finally worked. I had it connected via activesync, copied over everything fresh, went ahead and booted with the default mtype and it froze. Restarted, changed mtype to 2040, disconnected from computer, then started haret and it booted fine. I think the problem has to do with it not detecting the battery, so it instantly powers off. Somehow it thinks it is plugged into a charger now, which is why it's working.
[Touch Diamond, MDA Compact IV ROM Development] manekineko:
As reported by others, without any modification, just unzipping this to my internal storage, this starts up on my Sprint Diam500, but the colors are all weird.

I think it may have also froze on the tutorial prompt, but it was hard to tell because responsiveness was really bad too.

Edit: Thanks ydoucare!

Fixed the touch screen weirdness by changing startup.txt to msmts_calib=0x81.0x393.0x358.0x7D

First time I booted I got a Wait or Force Quit screen on the soft keyboard, and on subsequent boots, it just doesn't seem to be available at all. Even if I hold down the ok button, and select Android keyboard while selecting a text field, nothing ever happens.
[Touch Diamond, MDA Compact IV ROM Development] karlanal:
:eek::eek::eek::eek::eek::eek::eek:

no manual, i bet you were one of those kids which rolled on the ground and cried when they didnt get what they wanted:mad::mad:

http://www.androidonhtc.com/boot_options

and there are dozens of them, but thenagain, why bother, it is easier thisway

there is no excuse for questions like theese

btw

didnt have one crash since yesterday
[Touch Diamond, MDA Compact IV ROM Development] manekineko:
Not to get into a discussion of whether that really works as a manual for beginners, but are you really suggesting that it's NOT a good idea to create a subforum or at least an organized thread header that contains the proper links to manuals and FAQs?

It's seriously small wonder people are filled with so many questions when the first posts of this thread are so out of date. People are not going to read 500+ pages before they give up and ask, and it's pretty tough at times to find the right keywords to search this monster thread for things that are basic.

I mean, seriously, the title of this thread is: Linux and Android on HTC Diamond "NOT YET WORKING", while the first post states "We are not trying to make android work. But we are making the linux kernel work well on our phones. Gogle Android (tm) already works." The link to the new wiki only contains very technical information of no use to someone just trying to get things to work. Talk about confusing.

I wholeheartedly agree with others that say that there should be a new subforum made to make information more easily accessible, or at the very least a new, better organized thread. There's nothing wrong with making information easy to find. Even if we had to walk 9 miles uphill to school in the snow each day when we were kids doesn't mean that we shouldn't try and make things easier for new people. If nothing else, it would seriously cut down on the amount of clutter and redundant questions, which is something everyone could appreciate.
[Touch Diamond, MDA Compact IV ROM Development] ydoucare:
That is because the mtype and calibration strings in startup.txt are not setup for the DIAM500. To get correct color, I think you need mtype 2040 (the wiki says 1805 though so i'm not sure), and the calibration should be 0x81.0x393.0x358.0x7D

However, I cannot get it to do anything but power off after it sits on the android logo for a bit.
[Touch Diamond, MDA Compact IV ROM Development] karlanal:
now you are talking

seriously, i found in about 2 days at least 10 different pages that are as good as thatone, and im not smarter than "these guys"

than anyone can, but ant this is a big BUT

if people arent ready to sarifise a bit of their time, and try to learn and understand

than, at this point, android is nothing for them
[Touch Diamond, MDA Compact IV ROM Development] magicman0:
+1 for new thread

anyway to get a working data connection?

also, is it okay to delete the FSCK files?
[Touch Diamond, MDA Compact IV ROM Development] manekineko:
Thanks on the touch screen fix, worked like a charm!

Regarding changing the mtype, that indeed fixes the colors for me (the penguin on the bootloader now looks much better) but causes it to crash at the pc_clk_disable step that others have reported. Guess it's still 1910 and the bad colors for me.

Also, the soft keyboard doesn't seem to work.

Have you tried booting it plugged in? Mine shutsdown unless I boot it plugged in. Or at least that's the trend I've seen so far.
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
I think the 2040 mtype is something that MrPippy patched together for a specific kernel. I think for regular(unpatched specifically for diam500) zimages diamond is 1805.

+1 for this
[Touch Diamond, MDA Compact IV ROM Development] manekineko:
1805 doesn't boot on my DIAM500.
[Touch Diamond, MDA Compact IV ROM Development] jaellis:
Can't we all just get along???

Before you get all worked up, no one is saying that there aren't guides available, what people are saying is that there isn't one here, which is generally seen as the repository of information for all HTC Devices.

And that website that you linked to is not complete and has no information for anything CDMA in the boot options page it leaves out the mtype 2040 which is part of most of the current diamond/Raphael builds, this would leave out anyone using Sprint and Verizon.

We are just having a conversation and whenever someone says there is not a guide they are saying there is not a unified guide for ALL diamond and Raph stuff relating to android.
[Touch Diamond, MDA Compact IV ROM Development] ydoucare:
When I use 1805 on the non-MrPippy kernels I get messed up colors.

I got this working with mtype 2040:

http://www.cobaltcode.com/fileupload/data/Android/AllInOne/android-donut_diam-raph-27-10-09.7z

Never got it to boot past the android logo with 1805, and the colors were messed up on the android logo.

There's still something going on with the DIAM500 where it's either not recognizing the battery or cannot get the bat level so it thinks the battery is dead and powers off right after it boots. Somehow I got it to boot thinking it was plugged into the charger (it wasn't plugged in at all) and it worked fine. It could be something else though, and maybe someone in the know can correct me, but this is what it seems like it's doing to me. I wish we had some more organization here in regards to CDMA vs GSM development.
[Touch Diamond, MDA Compact IV ROM Development] gleng:
So you got it running just using that package with the included kernel? Or did you use some other kernel. Using just that package and mtype 2040 it hangs at "FIXME! disabling a clock that doesn't have an ena bit: 24"

using DIAM500
[Touch Diamond, MDA Compact IV ROM Development] diamond_lover:
We can edit the WIKI and insert all this information :)
[Touch Diamond, MDA Compact IV ROM Development] xaoc747:
Make please new thread and just for Diamond!!! New build, new instruction, etc... And no more longer redundant and silly questions!
[Touch Diamond, MDA Compact IV ROM Development] killzusall:
However it is done, it needs to happen. People are being slated for wanting help which isn't fair to them, agreed some people are to lazy too look, but some are easily confused and need guidance, so why not make a new thread with links to the guides or update the wiki and point to that.

I know it's not the same but it's like getting mad when you're stuck behind a learner driver and you're cursing that they've got the instructor there so they have all the help they need, but are still going slow, signalling wrong etc..... But fail to remember alot of drivers felt the same about you, when they were stuck behind you, when you were learning.
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
Git's broken :(
[Touch Diamond, MDA Compact IV ROM Development] rpgman:
Searching to test the losck screen i activate the screen "blackout" in 30s of inactivity, i activate the lock screen with gesture and it's work good. No reboot.

If i don't activate Wifi, i can use 2 3h android.

With wifi that's too fast before the warning for battery.

I use the market (and so doing gmail ^^) send receive some text message too. I tryed to launch a video (wmv) from an email : after the download i've got only the sound and after a while : an error saying that video can not be played.

Have a soft that don't work (the game card Klondike Solitaire) it crash when i click on start.

I hesitated to buy a HTC Hero or wait for the Leo or Dragon, using the BSB 6.5.1 rom helped me for waiting ^^ testing this build of android makes me want a google android phone again and stronger :)

Thanks for you time and work ;)
[Touch Diamond, MDA Compact IV ROM Development] patrikbarden:
Finally got it working!

I just got my Diam100 to boot Android, after numerous failed attempts. The error message I got while booting went somthing like this:

Failed to mount the SD card. Cannot continue

/ibn/sh: can't access tty; job control turned off

/ # _

Finally i read somewhere that the Internal Storage had to be formatted as a primary partition. Followed the guide on that webpage on how to do this, but it didn't work. I could no longer find the internal storage from within my phone. After hours of struggeling I finally got it back, but still formated as a logical drive.

This is how I converted the internal storage to be a Primary patrition:

1: connect your phone to your pc in Disc Drive mode

2: On your PC, click start and then run. Enter "Diskpart" and click OK

3: in the diskpart terminal type "list disk". This will show all the discs connected to your computer.

4: type "select disk X", where X is the number representing your phone's internal storage.

MAKE SURE THE RIGHT DISK IS SELECTED BEFORE CONTINUING!

5: type "clean", this will wipe all the data on the selected disk

6: type "create partition primary". No explaination needed for this command I think.

7: close the disc part console, or type exit. Now open "Computer" on your PC, right click your internal storage and choose "format".

8: Select FAT32 as your filesystem, and uncheck "quick format" to do a full format of your disk. Wait until format is completed

9: Disconnect your drive, and hopefully your phone will now be able to boot android.
[Touch Diamond, MDA Compact IV ROM Development] nearlybritish:
Raph 110

Can anyone on AT&T with a Fuze actually get data working on the new package? Mine freezes every time, whether I use the carrier information in Startup.txt or leave it out.

This was the same problem I was having with other 1.6 builds, only 1.5 has been working for me so far.
[Touch Diamond, MDA Compact IV ROM Development] dzo:
Yes, I just emailed Kevin about this and it should be fixed now.
[Touch Diamond, MDA Compact IV ROM Development] GlemSom:
autobuild system updates

Thanks to phh and babijoee, my autobuild-service will now contain a rather special build. :D

Buildname: "special-diamond-raphael-wifi-bluetooth"

This is actually a tar package, containing a zImage (using special configurations file), and a tar.gz package containing wifi and ramzswap modules.

Unpack the package on your sdcard, and edit startup.txt accordingly.

As the buildname indicates; this build contains wifi modules - which can be used with the latest Android build: http://xdaforums.com/showpost.php?p=4826791&postcount=4991

This package is currently tested on diam100 ONLY, please give feedback on other devices!

NOTE: You'll need your calibration-file placed in /sdcard/calibration for wifi to work!

Direct link: http://glemsom.anapnea.net/android/special-diamond-raphael-wifi-bluetooth
[Touch Diamond, MDA Compact IV ROM Development] BobLC:
Hi Glemson,

Do I need a calibration file with your build ?

Just try on me DIAM100, manage to activate wifi but the networks can't be search.

Well, in fact, I don't know how find the calibration file... In which build can I find it ?

Thanks for your help.
[Touch Diamond, MDA Compact IV ROM Development] boas:
Download this pack http://www.cobaltcode.com/fileupload/data/Android/AllInOne/babijoee-wifi.7z

(use save target as)

Can be read about at http://connect-utb.com/index.php on the second page the post by Babijoee.

If you boot that release you will get a calibration file.

EDIT. On an other notice, I have now have time to test the last build even more. And if I don't use the device it will reboot the phone with in 1 minute. But w-lan works, and the release is quite nice. Then again, if I boot Android with an already working data.img, then Dpad won't work and Android won't boot properly, phone reboots before even entered android completely (during ANDROID screen).. :)
[Touch Diamond, MDA Compact IV ROM Development] BobLC:
Thanks Boas, but the link is broken. Try to google for mirror, without chance.

Another way to obtain the calibration file ?

EDIT : i will try with babijoee-wifi in the same post on connect-utb
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
I just stumbled across this package and I am going to organize full testing of it (hopefully including all RAPH and Diamond models).

The feedback will be collected here and I am pushing this out to my testing group so hopefully, the feedback will come in pretty soon.

IN other matters, I havent been working much on the CDMA issue but I constantly get questions regarding it. Why cant we get cellular network coverage on CDMA devices? I know CDMA is hardware based so I am guessing that is the basic issue, but does anyone else have anymore insight?
[Touch Diamond, MDA Compact IV ROM Development] rpgman:
"This is actually a tar package, containing a zImage (using special configurations file), and a tar.gz package containing wifi and ramzswap modules.

Unpack the package on your sdcard, and edit startup.txt accordingly."

I do that, take your STARTUP.TXT, change in it the name of zImage file, boot, test the wifi without and with bt activate, wifi become activate, it's searching for netword and desactivate itself. > When i do that i had my calibration file, and it's been working before this kernel and files from tar.gz. If i'm not wrong i see some errors on module wl.... not loading in boot stage

I can try to get back the dmesg from it if you want
[Touch Diamond, MDA Compact IV ROM Development] bojkic:
new wifi bluetooth build is great! props to phh and bj!!!

here are the things I've noticed on my RAPH100:

1) wifi works nicely, a bit weaker signal and it is kinda slow, but works!!! :D when connection is lost you cannot reconnect until you turn off wifi and then turn it back on again. it remembers passwords.

all in all, awesome!!! :D thx!

2) you cannot turn off the phone by holding end button and choosing shut down, and you could with bj's last build

3) it seems my screen is off, when in sleep!! :D however bluetooth and wifi combo drains battery extremely fast :D

4) hard keys still dump up sometimes

5) over all phone is slower when wifi is on :D

6) sounds working. discovery of multimedia files is perfect too. calls not so much :D

EDIT: and yes, it turns off when in sleep for some time.
[Touch Diamond, MDA Compact IV ROM Development] jaellis:
Maybe Martin/DZO has some insight, I know he got CDMA working well on the vogue, but not sure with the diamond. Just a thought. I used it for 2 months before mine dropped in water, it was great. That was also Android 1.0 though
[Touch Diamond, MDA Compact IV ROM Development] jaellis:
Difference between 090909 Build and Newer builds

So I am having trouble getting any of the newer builds to run on the DIAM400. The 090909 UTB build works everything that is supposed to work seems to but all the newer builds freeze on the mmcblk0: p1 in the start up. Any ideas?? yes I tried editing startup.txt but for some reason I'm getting frozen there. Can anyone explain the difference between the old UTB build and the Newer ones why it would act this way? I know that this is on the sqsh filesystem, how is this different and why would the system.img file have no problem but the system sqsh not run?
[Touch Diamond, MDA Compact IV ROM Development] ydoucare:
Yes, it booted with both the included kernel and MrPippy's kernel. I found out if I had it connected via activesync when trying to run haret, it would freeze at that line, but when just connected to the charger it booted.
[Touch Diamond, MDA Compact IV ROM Development] aussiewan:
Android 2.0

I just tried Android 2.0 Eclair System.sqsh file from http://code.google.com/p/vogue-hero/downloads/ on the off chance that it works... and it does boot! I was using http://www.cobaltcode.com/fileupload/data/Android/AllInOne/android-donut_diam-raph-27-10-09.7z with zImage.20091018_114250 from glemsom's site and the Diamond startup.txt. I just put the new .sqsh file in, and it booted! It's nowhere near as smooth as 1.5/1.6, but is usable for having a look :)

I found I had to hold down the hardware keys for a fraction of a second longer than normal sometimes to get it to do what I asked.

It could not connect to any network - it fails when searching.

According to the download link, it does not support calls/data/audio yet.

Calibration and colour seem fine.

Shutdown works.

Setting an unlock pattern works - it prompts for it on subsequent startup. Pressing power comes up with a task manager. Volume, dial, end, back and home buttons work as expected, except pressing the End button did not make it sleep even though I set it to go home and sleep.

Bejeweled is playable but laggy.

Camera app loads but shows the moving checkerboard instead of the image.

Music player loads and looks like it's playing but no sound comes out.

If I leave it for a minute or so it restarts itself. I think this is when it normally goes to sleep.

This is all on my DIAM130.
[Touch Diamond, MDA Compact IV ROM Development] gleng:
Using MrPippy's old kernel I did have CDMA service (voice and txt messaging at least). I don't remember exactly but I think he enabled some kind of CDMA initialization code. He would be able to provide better insight into this of course.

Hmmm..strange. I tried different combinations (activesync, connected to computer with charge-only cable, connected to charger, not connected at all) but still no luck...always get the same message.
[Touch Diamond, MDA Compact IV ROM Development] ND4SPD:
Which rootfs are you using? For me, it keeps repeating the Android boot splash screen.
[Touch Diamond, MDA Compact IV ROM Development] babijoee:
After some thought I've decided to work together with Glemsom and setup a Diamond and Raphael specific google code page.

It will have many instructions and faqs noted by many people here.

I'll try to get into this within the busy weekend, but hopefully finish it early next week.

I will also post a mirror faq on for connect-utb site aswell as this will save Untouchable time and hair pulling :p from the ongoing questions.
[Touch Diamond, MDA Compact IV ROM Development] AndroHQUist:
And put yet another link in your signature ;)
[Touch Diamond, MDA Compact IV ROM Development] aussiewan:
As I said, I used android-donut_diam-raph-27-10-09.7z. The only files I replaced were zImage (zImage.20091018_114250), startup.txt (for Diamond) and system.sqsh. It did sit on the android splash screen for a couple of minutes... but the hardware keys continued to respond to touch so I let it keep going. I did actually boot with the system.sqsh file that came in that pack first, then deleted the data.img and fsck files and replaces system.sqsh - I don't think that would have made a difference, but perhaps it did... also I do not have a wireless calibration file because I haven't been interested in wireless enough to invest the time in it.
[Touch Diamond, MDA Compact IV ROM Development] karlanal:
wtf

i came all happy in good mood and now this

first, since i installed the 1.6 build with enhanced sound, yesterday

i havent had a crash, not one, and ive been playing with him the whole

day yesterday and today, nothing, rock solid

when i get too hasty, and push 2-3 buttons at once he needs 5-10 seconds to remember what was pushed, but still, im now happier with the phone then i was when i got my first stock diamond

as i said, came all happy and now

i see wifi package, i instantly got a boner

damn, is this thay good or what, what is next, my girlfriend leaving me

not beore the job is done, or even better while she is doing her job ill install wifi

guys i dont know what to say

tha....naaah, what startup.txt is for my diamond, or even better,

can anyone send me config file:confused::confused:

guys im bowing to you and your work
[Touch Diamond, MDA Compact IV ROM Development] karlanal:
oh dear god, what a gay picture i cho

se

, thisone is more apropriate

sifu
[Touch Diamond, MDA Compact IV ROM Development] Marcellus_pnz:
yesterday, with zimage and modules from glemsom, i was able to connect to my home wifi network. browser worked fine, but why google account setup doesn't use it? it requires data connection over edge/3g.

i tried it today and it doesn't work again.
[Touch Diamond, MDA Compact IV ROM Development] BobLC:
Well, that's ok with the babijoe-wifi, the calibration file is created.

The wifi connection is ok on a secured network, but i have to try many times before having a successful connection.

The Google account setup (with existing account) is ok over wifi, all emails have been retrieved.

Having some problems with the battery status... Seems to be a well-known problem...
[Touch Diamond, MDA Compact IV ROM Development] kholk:
Android 2.0 squashfs reporting - DIAM300:

*- Bluetooth not working.

*- WiFi not working.

*- Telephone not working. (No signal)

*- System is much slow.

*- Buttons not recognized (apart the upper button) and mapped differently than other builds.