yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
(disclaimer: if this turns out to be an embarrassing drunk post, I shall edit it into something more appropriate.. ..later.)

When you first posted your diff after you first mounted your mmc, it didn't work for me. I got some CRC errors and finally error -110 (iirc). Then, when I applied the mmc2 diff, the one you said had nothing new, just some cleanup and the kernel boot option thing, I could see my SD card.

After that, I was able to replicate what others had done.

Well .. when I first read about how android ran on vogue, I partitioned my SD card to have a vfat partition large enough to hold the system and data images and a large ext2 (or yaffs2?) partition to be the external storage. Then I found out it was useless but it's been sitting there ever since. Now, 2 months (or so) later, it finally gets mounted. :D

It could be a pro that its more suitable to put a complete root fs on (im not sure how well vfat behaves when it comes to symlinks, permissions, case sensitivity, whatnot). It could be a con that wince doesn't see it.

In order to create the ext2 partition and fs, I mounted it directly and used fdisk and mkfs.ext2 respectively. That was long ago.

In order to get this android setup running, I only created a directory named 'tmp' on that fs (/dev/mmcblk0p2 in msm linux on raph, /dev/sdc2 in ubuntu in a vbox with the sd card in a card reader in a usb port) and put all images in there. That was in the final couple of hours of last year.

I changed init to mount /dev/mmcblk0p2 as ext2 in stead of /dev/mmcblk0p1 as vfat. That's it. Other than that I just downloaded lavenders file and followed the recipe.

..and put the root fs next to haret.

Oh yeah .. and I changed init to exec /init.android in stead of /(system/?)bin/sh, so I don't have to type.

One of those things where the linux kernel just takes over where windows left it. No (complete) init code or init code that assumes some state.

:( This is a bit of a bummer ..

In the android 1.0 setup that runs off SD card, typing works, but end and f4 kill it, and there is no way (afaik) to go 'back/cancel'. When I boot into a single ram fs (like we've done with android 0.8 for a while now...) I can not type properly because any key (other than the 2 that kill it) have the (side?-)effect of going 'back'. This means you can really 'do' more stuff (if you can call it that) or at least fiddle around more and not get to a dead end...

Happy new year. |)

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] sfxc13:
I was able to succesfully boot Android 1.0 on a Sprint Touch Diamond (CDMA)

what I did:

Follow the steps on here:

http://wiki.xda-developers.com/index.php?pagename=RaphaelLinux

After it says "can't access tty; job control turned off" you are supposed to type

/init.android

the problem is the screen calibration is flip flopped so when you touch the top of the screen it is trying to press the bottom. To get it to work properly I pressed and held where I though the buttons would be at the bottom of the screen (the top buttons are closest to the bottom and the bottom buttons are closer to the middle) the helpful part is if you press and hold it while highlight the key you are pressing until you let go. So you can hold the stylus until the correct keyboard letter is highlighted and then let go.

For the record I still got the funky colors that existed on .8

Great works guys!!! Everybody I know REALLY appreciates all your hard work.
[Touch Diamond, MDA Compact IV ROM Development] sfxc13:
doh! figured out how to get the screen calibration to come up

delete msmts_calib=<xmin>.<ymin>.<Xmax>.<Ymax> from your default.txt file
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
Is that an extended partition?

Try

mmcdevp1=/dev/mmcblk0p5 #Add this line
mknod ${mmcdevp1} b 179 5 #Add this line too

(change those 1's to 5's. I changed them to 2's to use the 2nd partition.)

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] dabs:
DOH!! You are spot on jobo! Somewhat of a schoolboy error... That will teach me to assume cards are formatted normally out of the box..

No need to change the initrd, I just formatted the damn thing properly and bingo - we have android.

Many, many thanks (and a happy new year!!)

/me leaves muttering about extended partitions....

ps. To use android/busybox without usb connected do a soft-reset immediately before running HaRET.
[Touch Diamond, MDA Compact IV ROM Development] Arktronic:
Has anyone else noticed in 1.0 that Android's Ringer Volume screen pops up momentarily when the reset button is pressed? I guess the button press is processed by Android before the lower-level stuff takes over and reboots, so that button is mapped...

Oh, and happy new year!
[Touch Diamond, MDA Compact IV ROM Development] slag02:
I have been messing with it since I saw it in my RSS reader

From what I can see the issue is the MMC is not mounting in the right location, perhaps an easy fix for someone?

Here is an Image of it loaded and I went to the /dev directory and ran a dmesg then an ls

AWESOME WORK!

I wish I could help out more, maybe I will start pick up a Java book?

HAPPY NEW YEAR
[Touch Diamond, MDA Compact IV ROM Development] mdrobnak:
Wow great job everyone!

I was on IRC just a day or two ago, it seems like a lot of work has happened with respect to RAPHX00 devices...

I will have to test this out tomorrow.. (later)

Next thing to get working will be audio and modem stuff for phone calls & data, then it should be a very usable OS while other features are worked on...

And here I estimated 3 months to my coworkers as to when I'd see Android on my Fuze..it's great to see that open source collaborative development works so well - everyone working on this kinda blows me away in the amount of knowledge that they have...

I will definitely stop on IRC to see what I can do with the phone stuff, but I'm very rusty, so we'll see...lol

Happy New Year everyone!

-Matt
[Touch Diamond, MDA Compact IV ROM Development] ermin15:
I think we have reached a point where many here think that this thread is not enough for this project. We could migrate to forum, but I think I have found a better solution: How about a social network like the one I created here?

Why a whole social network? First of all, it's quite unique. I personally didn't encounter a project with it's own network. It has nice features besides the forum. For example: chat. Wouldn't it be nice to write your "thank you, good job..."-posts in the chat, where it doesn't bother anyone? It's also convenient for other less important chit-chat.

But most important of all - i think it would be fun.

If this solution is accepted, the devs can pm me with their usernames and i will give them admin-status. Of course I would also forfeit my own.
[Touch Diamond, MDA Compact IV ROM Development] Gavin_H:
I was interested to notice that it remembers your settings when you reboot. I tested the long-press by adding shortcuts to the home screen and moving the clock and it remembers these changes everytime I re-boot.

I cannot wait until you guys get this working fully. :D
[Touch Diamond, MDA Compact IV ROM Development] holydhaliwal:
Hi good job everyone, when booting thoughi get errors saying
[Touch Diamond, MDA Compact IV ROM Development] Bimboy:
Are you typing in /init.android after "nothing happens"?

I got most of those errors, and Android does boot after issuing the command for it. However, on my Fuze (RAPH110), it boots to safe mode with no networking.
[Touch Diamond, MDA Compact IV ROM Development] abc12345:
You have a RAPH101? my fuze says 110. Are there different versions of the fuze?
[Touch Diamond, MDA Compact IV ROM Development] dabs:
This thread really needs splitting into support and dev...

This is what mine displayed when the mmc was not mounted.

type "ls /mmc" to check the card has been successfully mounted. If it hasn't that will be empty and you should see lines this right before the busybox shell:

"mount: mounting /dev/mmcblk0p1 on /mmc failed: Invalid argument"

followed by three lines saying:

"mount: Unable to mount '/mmc/foo' No such file or directory"

^ That's from memory so may not be exactly right...

How is your SD card partitioned... Read jobo and lavender.t's posts over the last couple pages for clues.

@Devs:

What work needs to be done to map the front buttons? As I see it the biggest problem we face is currently inability to navigate menus due to no back button. Some buttons do appear to be mapped however, for example closing the slide on the raph types 14, and as someone mentioned above, the reset button is mapped to volume :)

The left d-pad button seems to be mapped to something, would be very nice if we could just xmodmap that to Back!
[Touch Diamond, MDA Compact IV ROM Development] Bimboy:
Sorry.. Finger malfunction... RAPH110 here. The rest is true. Can get to safe mode only. There is only one known version of the Fuze to date.
[Touch Diamond, MDA Compact IV ROM Development] slag02:
One More Screenshot

Here is a Screenshot of the Errors that Sprint RAPH800 Users are seeing*

*footnote:

I have used both initrd files and the error is the same barring the small change between them - on this boot I also had removed the calibration flag from the default.txt
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
Is this version of android 1.0 we are booting now also the newest version around? There was a new version released a few days ago right?
[Touch Diamond, MDA Compact IV ROM Development] abc12345:
I can only boot up in safe mode also
[Touch Diamond, MDA Compact IV ROM Development] Bimboy:
First, not looking for help. Thought I would pass this along in case it helps.

I can see BusyBox shell starts and the next thing I see before the command prompt is "/bin/sh: can't access tty; control turned off"

I then init android, it boots in safe mode, and I immediately get a pop up:

"Sorry!

Application Settings (in process

com.android.settings) is not responding"

with two buttons: [Force Exit] and [Wait]
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
i guess everyone get's that forcing error. Some programs hang most times. If you try to dial a number it hangs also.

Maybe this is because it cannot reach things like battery status, network, bluetooth e.t.c.
[Touch Diamond, MDA Compact IV ROM Development] butterdori:
Yep, i also get that..

But when I dial a number, it goes back to home screen
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
Oh, i thought i got a error there too, but it could be that it just returns to the home screen yes.
[Touch Diamond, MDA Compact IV ROM Development] fredfredburger123:
i believe that it returns to the home screen because it has no mobile signal

things need mapping to enable such things

has anyone thought about how to migrate it as the main os?

sorry if its a daft question
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
Yes. Well.. we can.

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MAIN
ro.build.version.incremental=eng.job.20090101.225127
ro.build.version.sdk=3
ro.build.version.release=1.5
ro.build.date=Fri Jan 2 08:17:06 CET 2009
ro.build.date.utc=1230880626
ro.build.user=job
ro.build.host=jobuntu
ro.build.tags=test-keys

This recipe gives you a bootable set of the latest android:

* Check out the latest (current) android,

* Build it (..over night (or over work) if you build on a vbox with little ram :rolleyes: as it takes a looong time),

* Combine the root, system and data folders from ./out/target/product/generic into a single tree,

* Change init.rc to disable some lines that create the /system and /data mount points and mount them,

* Put this tree in the root of an ext2 partition on the SD card,

* Create a default.txt with no INITRD, and a CMDLINE that says: "root=/dev/mmcblk0p2 rootdelay=10 init=/init console=tty0 mem=64M msmsdcc_id=2"

* Boot the kernel. (The linuxtogo htc-msm kernel you know and love, not the kernel that comes with the SDK. One that will mount your internal storage or SD card.)

I have no idea why mem=64M but it does appear to be necessary. :o

In this latest build, when dragging the tab thing up or down, it looks as I would expect. :)

It no longer says 'Safe mode'.

It still dies horribly when left idle for 1 minute or when hitting END or F4. :(

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] plbelanger:
I believe the new version you are speaking of is the cupcake perhaps? I don't know if it's a release in the traditional sense just addons e.g. onscreen keyboard..something diamond users need =)
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
I understand that you have done this yourself and have the files of the new build?

Can you please place that build online? i would like to test that one on my phone also ;)

I'm not that good with linux.
[Touch Diamond, MDA Compact IV ROM Development] balsat:
I just compiled Android 1.0 and now the "bks" is assign as the back button!

A can dump the hole ext2 FS if anyone want it?
[Touch Diamond, MDA Compact IV ROM Development] NoBody20013:
hi,

what is the "bks" button? and how did you map it.

-yes please upload your build so we can test it or see your changes....
[Touch Diamond, MDA Compact IV ROM Development] fredfredburger123:
yes please - i would like to test also
[Touch Diamond, MDA Compact IV ROM Development] ermin15:
Android on Notebooks!?!?!? Find out more here.
[Touch Diamond, MDA Compact IV ROM Development] balsat:
Bks=backspace on the soft keyboard... I didn't map the key, it is automatic maped in Android build eng.root.20090102.152519

Someone with about 70-80 mb free webspace?
[Touch Diamond, MDA Compact IV ROM Development] dejant_9:
yes. PM me if you want.
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
I can set you up with a free 250MB Web hosting account if you want.. Just let me know ;)
[Touch Diamond, MDA Compact IV ROM Development] balsat:
I send you a PM... The dump is 40 mb
[Touch Diamond, MDA Compact IV ROM Development] c4software:
hi,

its possible to make a dump like the previous release aka : 3 files cache system and userdata ?
[Touch Diamond, MDA Compact IV ROM Development] balsat:
The files are now uploaded http://217.128.108.212/master/ AND

http://87.72.13.87/

The android_fs.tar.gz is a dump of my /dev/mmcblk0p2 ext2 partition

Thanks to dejant_9 for hosting
[Touch Diamond, MDA Compact IV ROM Development] c4software:
same use as before ?

Edit: WoW web Server seems really slow, if ou need an other dedicated webserver pm me.
[Touch Diamond, MDA Compact IV ROM Development] balsat:
No you should unpack the contents of android_fs.tar.gz to a ext2 partition on your sdcard.

but i'am uploading userdata.img and system.img now, but thees img'es i NOT in ext2 format, but yaffs2
[Touch Diamond, MDA Compact IV ROM Development] fredfredburger123:
hey sorry for being numb!!

am trying to make an ext2 partition of my 4gb internal storage on diamond but gparted sees it all as free space?

will it kill all my current data if i give say 2gb to ext2?

Thanks
[Touch Diamond, MDA Compact IV ROM Development] c4software:
With this image's i just have to replace old image with yours ?
[Touch Diamond, MDA Compact IV ROM Development] balsat:
First of all... MAKE A BACKUP of your fat partition.

I use fdisk under Ubuntu and it see the fat 4gb part just fine!

Delete the partition and create 2 new, the first a fat16 LBA, the second ext2
[Touch Diamond, MDA Compact IV ROM Development] c4software:
what is the advantage to split the internal storage?
[Touch Diamond, MDA Compact IV ROM Development] fredfredburger123:
thanks for that
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
I have. I did. I can.

By now, balsat has done the same, and dumped the file system.

Mine is only 30M (link), not 40. I guess balsat had already booted it, so it comes with a pre-populated dalvik-cache. (This is why the 1st boot is waaay slower than subsequent boots.)

My ISP seems to have trouble with web space, so if that other link doesn't work, you can get it from here for now. (I'm not going to leave it there if it saturates my pipe too much. Please try the other link first.)

The reason I posted that recipe (which I think is pretty clean) was so that we don't need to fling multi-meg images around. (30 or 40M is a lot for not being able to do anything really...) The fact that the process is almost completely automated and involves very little tinkering is imho A Good Thing, because it means there are only few steps that need to be repeated (and that could potentially break) when updates happen.

-Jobo

EDIT: This is _not_ a file system image that gets mounted from an init script in a ramdisk. You have to unpack it into the root of a partition of your SD card and boot into it using a command line like I posted before.

EDIT: Can anyone confirm they get the on screen keyboard (see attached picture) when you click in the google search widget (on the right most screen)?

EDIT: Oh yeah .. to get wallpaper pictures fit nicely, they must be 720x640 ;)
[Touch Diamond, MDA Compact IV ROM Development] balsat:
sdcard

I have mounted a fat partition at /sdcard but Android can't see any sdcard, anybody know why?
[Touch Diamond, MDA Compact IV ROM Development] iRiKi:
none, it's actually a disadvantage. it's like in the desktop windows world, two partitions because of incompatibilities in the m$ OS (again) :>
[Touch Diamond, MDA Compact IV ROM Development] abc12345:
Can someone reupload the files somewhere else because, the link is incredibly slow
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
I don't want to be an asshole ;), but is it possible to put it in a .ext2.img format so that i/we don't have to mess around with partitions and stuff?
[Touch Diamond, MDA Compact IV ROM Development] balsat:
Yes i got the same nice keyboard when i press on the google search within the android i compilede!
[Touch Diamond, MDA Compact IV ROM Development] Gavin_H:
I would be really grateful for this also, I'm not technically gifted and I don't really want to partition my drive.
[Touch Diamond, MDA Compact IV ROM Development] lavender.t:
source diff

got some requests for the source diffs so i'm attaching the patch file here. the only change from my previous diff attachment is the kernel parameters of msmts_calib.

this is the source that i built my zImage from.

- lt
[Touch Diamond, MDA Compact IV ROM Development] abc12345:
I dont want to sound like a noob but where do I place the other two img's
[Touch Diamond, MDA Compact IV ROM Development] c4software:
@balsat

Can you make system.img and userdata.img image in ext2 format ?
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
That wouldn't help you because it is the entire file hierarchy on a single fs: root, system, data, cache. You would still have to roll a ram disk to boot from that mounts the image and chroots into it. ("This is _not_ a file system image that gets mounted from an init script in a ramdisk.") At the risk of being an asshole myself: If you have a setup that lets you do that, then I'm sure you can pump this cpio archive into any flavor file system. If not, an ext2 image wouldn't help either, and it might be more practical to use the method where you have an initrd mount a vfat partition and then some image files.

Cool. I guess it's time to make the kernel vkeyb toggleable again.. :)

Thanks! My screen is getting thin in those 2 corners...

-Jobo

UPDATE: This kernel (link) has the (latest?) clock and mmc code (it sees the SD card in my raph100) as well as the msmts_calib boot option from lavender.t (so you don't have to calibrate every time)..

..and a toggleable vkeyb (so it doesn't get in the way when you don't need it). To the left of the vkeyb, there is a green square. You can drag the vkeyb around the screen with this. The square goed red while dragging. If you tap on it without dragging (which is really hard, so there is a 3 pixel threshold) it turns the vkeyb off (it wont undraw until the that part of the screen updates) and the square turns blue, so you can tell it's turned off even when its not (yet) undrawn. Again, you can drag it around, or tap on it to turn the vkeyb back on (which of course draws immediately).

BTW: Should you encounter unexpected behavior: This kernel does not init halibut-keypad or trout-keypad. Also, the htcraphael defconfig has CONFIG_TOUCHSCREEN_SYNAPTICS_I2C_RMI enabled. Disabling it didn't seem to make a difference so I left it disabled.
[Touch Diamond, MDA Compact IV ROM Development] Gavin_H:
Could someone not just update the wiki with the latest version of Android 1 in place of the link there currently?
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
Getting so excited about the nice progress here!

Too bad, my MMC seem to have been damaged. I can read in high speeds from the card, but writing data to the card is VERY slow (50~100 kb/s)

Also my device seems to drop USB connection after a few seconds... sigh, can't test these stuff out anymore. Will try to get ActiveSync up and flash my device again.
[Touch Diamond, MDA Compact IV ROM Development] Toug:
Yes I would know too if Android is working and what are bugs still present, so If somebody can update the wiki?

I left Windows for Ubuntu and I would leave Windows mobile too.

Thanks
[Touch Diamond, MDA Compact IV ROM Development] kowen:
It's so nice to see progress here, with android 1.0

Great job you guys !!

Unfortunately I cant be of help, but looking forward to any progress.

I know how much work these things take (software engineer)
[Touch Diamond, MDA Compact IV ROM Development] michbeck100:
Great work lavender.t!

I guess you've used the sources from linuxtogo.com? Will you also commit your changes? It's easier to keep track of the changes that way.

Cheers
[Touch Diamond, MDA Compact IV ROM Development] balsat:
GSM Signal

I got a GSM signal on my diamond, and it connect to my GSM provider "3", but when i touch the softdialpad it crashes.

In /system/build.prop i changed the "rild.libargs=-d /dev/ttyS0" to "rild.libargs=-d /dev/smd0"

I can receive SMS, but i can't send yet
[Touch Diamond, MDA Compact IV ROM Development] abc12345:
can someone please explain better what to do
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
Yeah, for me too. Can't seem to find out a way to:

1. make a ext2 partition on my diamond (after i have resized it of course)

2. Read the cpio file...

3. copy all the files needed to there.

I'm on windows, and with me a lot of other diamond users i would guess (quite often linux users prefer a unix based phone over a windows based phone.

For me the solution with the 3 .img files was perfect... so i secretly hope that someone has somekind of same solution :)

On the other hand, i don't wanna ruin anyone's drive or developing, it's going great the last days. I'm really proud of what a community like this can accomplish :)
[Touch Diamond, MDA Compact IV ROM Development] lavender.t:
cupcake images

your secret wish has been secretly granted ... :) check out the cupcake images at willis111's server: http://xda.willboost.com/cupcake-20090103-2.tar.gz.

the zImage there has jobo's draggable vkeyb patch.

here i also incorporated the smd issues that mdrobnak and netripper figured out. so like the 0.8 image you had before, it is now able to place phone calls. still, no voice no rings, etc.

the change to use smd was as balsat suggested in the irc to modify build.prop in /system:

-rild.libargs=-d /dev/ttyS0
+rild.libargs=-d /dev/smd0

thanks guys !

- lt
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
Really cool dude, booting now :D