yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
Perhaps Lavender.t, like most other people who are actually do the dev work on this project are a little busy over the X-mas/New Years holidays with family and friends and we should be happy with whatever work they do regardless? Hopefully when he gets back from a little more of his vacation he'll upload his android 1.0 images and it will be a little easier to find out where we are and what hardware is working in the new version due to newer drivers being included. I think up until this point we've been rushing towards getting android 1.0 to boot for that reason, no need to re-write that's included in the actual operating system release since we've basically been running a beta up until we can get our grubby little hands on lavender.t's patches.

Edit: GJ Lavender.t
[Touch Diamond, MDA Compact IV ROM Development] lavender.t:
download

sorry for the delay folks. my internet went down last night just as i was checking my messages and trying to pack files up to upload.

thanks willis111 for lending his space. now you can download the 40MB .tar.gz from http://xda.willboost.com/. i myself have a microsoft office live host but it just allow me upload at most 10MB a time ... well, what can i say ... :(

this gz packags is by no means to make it easier to run in your phone (at this time). as i have said it is still in a very preliminary stage. very few things work. i just tried the calculator and it worked :) the key map doesnt work yet and the virtual keyboard always gets in my way which is kinda annoying ... no network ..., and no way to bring it back once the LCD is off after idle for a while ...

that being said, now the instructions: :)

1. unpack the tar.gz and copy the files to your phone. you will need haret.exe which is not included. make a dir named "tmp" from the root of the "internal storage". copy the 3 .ext2.img files into it.

2. now you might want to modify the default.txt a little bit. in my zImage i added 2 kernel parameters:

msmsdcc_id=2

msmts_calib=0x7a.0x5e.0x35a.0x37f

msmsdcc_id is the SDC number (1 - 4) of the "internal storage". my DIAM100 uses 2. and i think other diamond phones should use the same. so unlikely you'd need to change this.

msmts_calib is the touch screen calibration. i'm just lazy to click the tiny red dots every time booting up linux. so this parameter just allow me to do that once for all. i'm not sure if all the diamonds have the same calibration (but i think they are hopefully similar). so what you can do is to remove this parameter setting for the first boot. after calibration you will see the xmin = xxxx, ymin = xxxx .... values. these are hex numbers of your calibration. write them down. and next time, put in default.txt:

msmts_calib=<xmin>.<ymin>.<Xmax>.<Ymax>

note, they are dot (.) separated, NOT comma (,).

3. after booting up linux, you need to run /init.android to launch android.

well now i think you are pretty much ready to give it a try. one of the reasons for this package is that i hope it would be useful for other android 1.0 port since here we have a relatively clean cut of android and linux.

enjoy, and happy new year! :)

- lt
[Touch Diamond, MDA Compact IV ROM Development] lavender.t:
clock settings

thanks for the info maejrep. i'm getting the same from my diamond phone running haret.

HaRET(1)# pdump 0xa86000a0 0x20
a86000a0 | 0001fff4 fff50044 0001fffa fffb0044 | ....D.......D...
a86000b0 | 0005fcff fd04005c 0005fcff fd04005c | ....\.......\...

i guess it should be the same for yours too. A0/A4 are for SDC1, A8/AC for SDC2 ... and so on. i'm still yet to find out how to decrypt these numbers :(

from the logs you sent me last time, i'm worried that raph might be quite different from diam on this aspect. or possibly there are something different in the wince BSP of raph that touched some registers haret doesnt reset.

- lt
[Touch Diamond, MDA Compact IV ROM Development] fredfredburger123:
gave it a go

thanks lt - worked a treat

look forward to any more updates

am no where near an expert on this - just keen to see it running on the diamond

am always happy to test as have a spare one knocking about

thanks again!
[Touch Diamond, MDA Compact IV ROM Development] ronni.rasmussen:
Amazing work and thanks for the download works fine on the diamond with the deault.txt file.

Gonna be the phone geek at the party tomorrow thanks to you guys.

Happy new year yall!
[Touch Diamond, MDA Compact IV ROM Development] NoBody20013:
hi,

great work here!

can anybody tell about the performance? feels it faster than WM?

greetings
[Touch Diamond, MDA Compact IV ROM Development] ronni.rasmussen:
To early for me to say, cause no buttons is working for me so get stuck everywhere i got cause i cant go back. But what i've seen so far between the 10 soft resets i would say yes. But it would also be a HUGE suprise if it wasnt faster than WM :)
[Touch Diamond, MDA Compact IV ROM Development] xmoo:
msmsdcc_id is the SDC number (1 - 4) of the "internal storage". my DIAM100 uses 2. and i think other diamond phones should use the same. so unlikely you'd need to change this.

What about Xperia?? Storage Card
[Touch Diamond, MDA Compact IV ROM Development] fredfredburger123:
android 1.0

yeah if anyone can work out anything with returning to the homescreen that would be great! :)
[Touch Diamond, MDA Compact IV ROM Development] fredfredburger123:
performance

is good :0)
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
I'm getting an error""

mmc0: new mmc card at address 0001

mmcblk0: mmc0:0001 000000 3932160KiB

mmcblk0: unknown partition table

And then it hangs there...
[Touch Diamond, MDA Compact IV ROM Development] ronni.rasmussen:
Get the same message but it works fine so did you remember to:

make a dir named "tmp" from the root of the "internal storage". copy the 3 .ext2.img files into it. ???

Cause it seems like it has a problem with the ext2 files or the Intermal storage.
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
When I try and run your package I run into an error @

mmc0: new MMC card at address 0001

mmcblk0: mmc0:0001 ZLEODM 3932160KiB

mmcblk0: p1 ( p5 ) mount: mounting /dev/mmcblk0 on /mmc failed: Invalid Argument

followed by a bunch of errors about how it couldn't mount /mmc/tmp/system.ext2 etc etc

I can then calibrate the screen but of course can't init.android since it can't find the files.

Running on a telus cdma touch diamond

Edit: When I change the mmc address to 1 it crashes out after trying to set the mmc clock and about 3 trout messages w/no valid info
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
stupid, must be that if i create a folder on my phone from my pc it capitalises it.

testing again now...

Edit: tested it, still no luck . same error... will check some more.
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
Allright, its working now.

I replaced the files using activesync instead of using it as disk drive.

That worked fine, and now it's showing me android 1.0.

Great job :D

Edit, works pretty fast also, smooth animations and everything. impressive!

Also great that i don't have to calibrate myself :P

Allright, another update:

it looks like android only boots up when i connect it with usb to my computer. the other times it hangs during the process and i don't get a busybox terminal.
[Touch Diamond, MDA Compact IV ROM Development] abc12345:
It works partially on my fuze, it stops at

mmc0: Host does not support reading read-only switch. assuming write-enable

mmc0 new SDHC card at address 41b7

mmc0: p1
[Touch Diamond, MDA Compact IV ROM Development] maejrep:
Hmm, not quite... Only a0-a7 are the same. Probably due to diam only having 2 real sdcc devices?

sd1
HaRET(27)# pdump 0xa86000a0 0x08
a0 a4
a86000a0 | 0001fff4 fff50b44 | ....D...

sd2
HaRET(29)# pdump 0xa86000a8 0x08
a86000a8 | 0019f3ff f418005c | ....\...

sd3
HaRET(30)# pdump 0xa86000b0 0x08
a86000b0 | 0001fffd fffe007c | ....|...

sd4
HaRET(31)# pdump 0xa86000b8 0x08
a86000b8 | 0019f3ff f418005c | ....\...

Agreed, there seems to be a lot of differences between raph and diam, and even between raph100 and raph800 (can't wait to see what raph500 brings :))
[Touch Diamond, MDA Compact IV ROM Development] abc12345:
there is going to be a raph500?
[Touch Diamond, MDA Compact IV ROM Development] Arktronic:
RAPH500 is Verizon's Touch Pro.

Major differences are to be expected between GSM and CDMA Raphaels. After all, they have completely different radio stacks, so why not throw in a few more changes? ;) I'd expect the differences between 500 and 800 to be minimal, though, just like with 100 and 110.
[Touch Diamond, MDA Compact IV ROM Development] chlinkchlink:
Can anyone update the wiki with last linux for newbies like me ?
[Touch Diamond, MDA Compact IV ROM Development] Rusher:
Sprint HTC Diamond boots android 1.0 - OK. Colors messed up :(
[Touch Diamond, MDA Compact IV ROM Development] tdmusic:
Boots fine on my UK Diamond, awesome work Lavender (and everyone else who has contributed, of course!)

I get some weird graphical glitches - like random pixels on the screen? The first time, it took a while to boot (just on the "glowing robot" loading screen) and whenever I tapped the screen, a pixel would light. The second time, I noticed that when I pressed the # key in the dialer some random pixels would light?! Strange.

Also, the on-screen keyboard flickers in Android (I think this has already been mentioned).

We really do need a way to get back to the home screen too ;-) I remember reading that in 0.8, the stylus-in sensor functioned as a home button. This doesn't seem to be the case here - is there any way we can change the key mappings?

Anyway, far from usable, of course, but looks lovely and runs very smoothly in terms of loading, animation, etc. I'm really impressed.

I don't know much C, so I'm not sure how much I could contribute towards development, but my Diamond is a spare (company) phone so I'm willing to test whatever on it.

Awesome work guys, can't wait to see this get to the level it is on the Touch Pro or whichever handset it was :)
[Touch Diamond, MDA Compact IV ROM Development] xxxxchrisxxxx:
Don't know much (anything really!) about the technical side of things - just posting to say that I followed the instructions and this booted on my uk TMobile MDA Compact IV

Thank you :)
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
I dont reckon the files Lavender posted would work on the Touch Pro? But as Lavender said, its a pretty clean port of Linux and Android, so it Im hopefull that NetRipper or someone else can make it work on the Raph100 as well?
[Touch Diamond, MDA Compact IV ROM Development] tdmusic:
Yeah, I don't think I mean the Touch Pro... there was a Youtube vid of one HTC WinMo handset which seemed to be running Android pretty smoothly anyway!

Edit: I mean the Vogue
[Touch Diamond, MDA Compact IV ROM Development] lupine_85:
Nope, definitely doesn't work on the RAPH100 - same stopping-point as mentioned previously.
[Touch Diamond, MDA Compact IV ROM Development] pauldgroot:
Wiki updated by me.

Check it out here.
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
1.0 also on touch pro (raph100)

I managed to bang together a single root fs booting into Android 1.0 from ram (..only moments before being able to access storage, so I guess it's no longer useful to pursue).

Results are pretty much the same.

- Screen times out, no way to bring it back. Per default, the display timeout is set to 1 minute. You can prevent this from happening in Settings -> Sound & Display -> Display Settings -> Screen Timeout -> Never Timeout.

- Hitting the 'end' key (on the vkeyb) has the same effect as letting the screen timeout: it dies. Any other key seems to go 'back' (..so I can't really type anywhere).

- The analogue clock doesn't run. The dgital clock in the status bar does. (I see that in the pics on the wiki, it does run..)

- The wallpapers seem to be too small for the screen: there is some black on the top and bottom, and when panned to the right also on the right side.

- In the bottom-left corner is a small overlay saying 'Safe mode'.

- When dragging the tab up or down, I would think that the lower half should be darkened (behind a dark semi transparent layer) but it isn't. The background only gets dark when the tab is completely up.

About the vkeyb getting in the way: In this kernel, the vkeyb is draggable. (..but it doesn't recognize the boot option for touchscreen calibration. A .diff for that is linked to from this post.)

With the latest clock-7x00.c on a raph100, I can now see the removable SD card, not the built-in storage. ..and mount and boot into any partition on it.

When I put the initrd on the SD card and boot from it, it doesn't get past the screen with the glowing android. (Sometimes it stops glowing after a while and it hangs completely, sometimes it keeps glowing forever.) I shall test with the fs images you posted and see if that makes a difference.

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] kal1990:
hey guys,

i tested it on my diamond....it works fine....

but how come i back to the home screen when i do:Settings -> Sound & Display -> Display Settings -> Screen Timeout -> Never Timeout.

is there any way?
[Touch Diamond, MDA Compact IV ROM Development] plbelanger:
This is awesome work guys. Keep it up. I look forward to the day when everything functions correctly. Has anyone considered techy or social network sites to try and get the word out and get more people involved in development?
[Touch Diamond, MDA Compact IV ROM Development] LordKiwi:
android 1.0 touch pro

the touch pro needs something a little different.

/dev/mmcblk0 points to the sd card.

for it to boot into the gui you need to copy the ext2.img file to /tmp map on the sd card.

And the init file in initrd.droid.cpio needs to be edited.

this way the raphael boots android 1.0 from it's sd card.

Click here to download it.
[Touch Diamond, MDA Compact IV ROM Development] AstainHellbring:
can you upload your edited initrd?
[Touch Diamond, MDA Compact IV ROM Development] sensorama:
i thougt this was a social network site for techy nerds. ;)

btw great work lav.
[Touch Diamond, MDA Compact IV ROM Development] Sl4sher:
Thanks, that got it booting for me.

Unfortunately now that there's no screen calibration, Android seems to think the digitizer is on upside down so I can't type the command to start the gui. Is there any way to fix it?

EDIT: Actually now that I look at it, regardless of which initrd (original or kiwi's) I use it fails to mount the mmc using either device. I'm on a sprint raph 800. Maybe the sd card has a different name? Would it be possible to change the init file to mount the filesystems from internal storage (as in program memory, not the diamond's internal storage)?
[Touch Diamond, MDA Compact IV ROM Development] abc12345:
It doesn't work for me, I get no such file or directory for all 3 imgs
[Touch Diamond, MDA Compact IV ROM Development] Vector-SS:
These should all be found under the imgs folder.
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
Remove the screen calibration from your default.txt and manually calibrate the screen @ boot.
[Touch Diamond, MDA Compact IV ROM Development] be_vigilant:
Claiming Credit?

Wow looking good thanks for all your hard work guys.

Just came across this on youtube and seems to be the exact same version lavander created.

Is Lavander associated or are they claiming credit for his work?

http://uk.youtube.com/watch?v=VR-tsHQhPRo

edit...OK at the end they give thanks?......
[Touch Diamond, MDA Compact IV ROM Development] liamhere:
looks fishy to me

just watched the clip....strange

his favorite clips says it all really :eek:
[Touch Diamond, MDA Compact IV ROM Development] racedout:
Can confirm I just got it working on my FUZE from the sd card. Had to have it plugged in USB to get it to work though. The on-screen keyboard flickers but it is really cool booting 1.0!!! Keep up the good work and thanks!!!
[Touch Diamond, MDA Compact IV ROM Development] butterdori:
Yes he does mention lavender, but he also says 'powered by valvasoftware'... strange hmm....
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
confirmed android 1.0 off raph100 sd card

Yes, that works for me (raph100). I had to adapt it a bit to mount an ext2 filesystem in stead of vfat, on the 2nd partition in stead of the 1st.

Things that are different:

* I get an error: "Sorry! Application Settings (in process com.android.settings) is not responding."

* Waaay more apps. :)

* Typing on the vkeyb now works and no longer has the side effect of back/cancel.

* Analogue clock runs.

Thanks,

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
it seems I can't mount my mmc w/lavender.t's or touch of jobo's files. both drop me out to busy box saying mounting failed. when I ls /dev/mm* I see mmcblk0 listed, when I try and mount it manually to /mmc which also exists it says no such file or device.

Edit: Running a cdma telus touch diamond
[Touch Diamond, MDA Compact IV ROM Development] lavender.t:
Valvasoftware ?!?!?!

what the *!! i'm NO valvasoftware. i'm just myself. :mad:

and i wont take the credit for this either... many people, like netripper, druidu, dcordes, etc, had done lots of important work before i even start to read this board. i just came in at the right time to put what's been working so far together. and that's it ...

c'mon folks, if you find this useful, please *DO RESPECT* other people's hard work. for myself, i just did this for fun.

- lt
[Touch Diamond, MDA Compact IV ROM Development] dabs:
Hi all,

Sorry to clutter up the diam thread with yet more raph questions... Maybe at this point this thread should fork, as the differences between diam and raph seem to be becoming more of an issue...

With that said, here goes:

I am struggling to get this to boot on a RAPH100 (o2 UK variant).

I am using the initrd LordKiwi kindly posted and it boots as far as the busybox shell (only when usb is connected), but fails to mount the imgs.. I tried the original initrd and see the exact same issues..

eg:

Then tries and fails to mount the three img's and (obviously) fails with No such file or directory errors then loads busybox.

Any ideas anyone? Quite probably I have made a stupid mistake somewhere, but cant see where. I dont need an "idiots guide" and am prepared to get my hands dirty messing with the initrd (or partitioning the SD card to add a second ext2 partition), but if anyone knows what going on it would save me a lot of time fumbling with the initrd and then waiting for the damn thing to soft-reset ;)

@jobo,

What are the pros/cons of using vfat imgs vs. an ext2 partition?

Could you post the procedure you followed (or even better zip/gz up the whole lot and up it someplace, but I know thats a lot to ask) for running from an ext2 partition.

I assume you extract the imgs to their relevent folders on the root of the ext2 partition then hack the initrd to mount everything where it should be, but a little tut would be very nice.

btw. Major props to all those involved in the project so far!

Thanks in advance :D

ps. Whats the deal with it crashing immediately before loading busybox when usb is not connected? Odd...
[Touch Diamond, MDA Compact IV ROM Development] lavender.t:
great !

wow ! first confirmation of the sd working in raph ... cool and thanks jobo !

yes it is meant to be the external sd for raphael. from netripper's info raph and diam uses (mostly) the same board design -- even the sd part. the difference is that diam built the sd inside.

i was wondering why the raph phones had no luck getting the clock right ... great to hear that at least one model works. :)

- lt
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
I think I could use an idiots guide. The device is always created but for some reason it's never actually there and can't be mounted.

I'm running w/setup like

/device

/device/internal storage/tmp/haret files

/device/internal storage/tmp/images

(just dumped everything all in the same dir same as ss's on the wiki)

in async mode and sd card mode both flop out after trying to mount the sd card/images and I'm not able to manually mount the drive, therefore images. I've tried jobo's image and it does the exact same thing. Has anyone got this running on a cdma diamond and can post a step by step/are all you guys that have gotten this running using gsm versions of the phone?
[Touch Diamond, MDA Compact IV ROM Development] lavender.t:
sd partitions

hello dabs, for the external sd it really depends on how the sd is partitioned and formatted. so other people's sds might be different from yours base on how they are used.

if you can plug the sd into a linux box it would be easier to see what's in there. sorry that i didnt build fdisk into the busybox so it would be a little tougher to do in the phone.

if the linux box recognizes your sd card, e.g., as device /dev/sdd, then you can do a "fdisk -l /dev/sdd" to see all the partitions and types. if it doesnt show any, then the entire card is used as a single storage media (which is the case for my DIAM110). in this case, running "dd if=/dev/sdd count=1 | hd" will dump the first sector and this may give some hints what type of file system is formatted in there. but if you havent done anything special to your card, by default it should be vfat.

regarding the type of file systems to use, android natively uses yaffs2. the reason i used ext2 is that the file system needs to support symbolic links (i guess without symlink it might work as well, but that's a waste of space and i dont have much time to try), which is a no for vfat. and i had trouble getting yaffs2 over loopback working in my kernel image. the downside of ext2 loopback over vfat is the performance -- disk access has to go thru an extra layer. but the good thing is you dont have to repartition/reformat your card for a different file system so you dont lose any existing data.

hope this helps,

- lt
[Touch Diamond, MDA Compact IV ROM Development] lavender.t:
have you tried the cmd i sent you in PM ?

hi willis111, have you tried what i sent you in the private message ? we can chat by PM or in the irc. dont wish to turn this thread into support ... ;)

- lt
[Touch Diamond, MDA Compact IV ROM Development] dabs:
I am pretty certain my card is formatted as a vfat single storage media.

Not near a linux box atm, but diskutil under os x gave me:

/dev/disk4
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *5.7 Gi disk4
1: DOS_FAT_32 SDHC6GB 5.7 Gi disk4s5

I have booted up an old fedora live image i had lying around in a vm, but it dog-slow, and I'm not entirely sure I trust it to format my card, seems like asking for trouble formatting a disk mounted inside a vm running a live image and using the phone in mass storage mode..

fdisk -l gives:

$ fdisk -l
Cannot open /dev/sda
Cannot open /dev/sdb

Which doesn't look promising...

Am stuck at home sick for New Years :(, so at least I have something to mess around with...

I have no particular aversion to repartitioning for an extra ext2 partition, I am only using 2gb on the 6gb card..

I will try to replicate what jobo did, but first il poke around and try to find why this happens on the raph100

#mount -t vfat /dev/mmcblk0p1 /mmc
mount: mounting /dev/mmcblk0p1 on /mmc failed: Invalid argument
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
Not really trying to turn it into a support thread but it would be nice if I saw one reply saying "I think you're an idiot cause it boots fine on my cdma touch diamond". I read and replied to your pm though, thank you very much. Figured you'd be busy working on something else which was why I was looking for input from other cdma owners.