yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] dejant_9:
Haret.exe and cache.ext2.img are the same than wikki's. If you have the lavender.t cupcake, you juste need the zImage, and default.txt

This webspace is my own old PC in server mode. It was just for test. Sorry i don't have another webspace with more than 130mo for sharing datas..
[Touch Diamond, MDA Compact IV ROM Development] esbenr:
How did it go with Android on Touch Diamond?

I've just got a Diamond in spare so i thought that i'll try to put some Android on to it.

Where can i find a guide and the nescary files?

Did you guys get to fix the minor issues?
[Touch Diamond, MDA Compact IV ROM Development] chemical1979:
In the first post in this thread is a link to a wiki where you can find the information you need.
[Touch Diamond, MDA Compact IV ROM Development] Gavin_H:
That's ok, thanks.
[Touch Diamond, MDA Compact IV ROM Development] balsat:
Webserver

I got the files to on my home server, it might be a little bit faster!

http://87.72.13.87/
[Touch Diamond, MDA Compact IV ROM Development] c4software:
if you need a didcated server to upload/share files. i can share my dedicated server if you want. i upload the lastest file tonight. i post the link when its done.
[Touch Diamond, MDA Compact IV ROM Development] Bimboy:
Tip: Some of you may not know this, but you can go into the Settings application and change the sleep timeout value, under the display app. This will keep the OS active for longer than a minute, unattended.

Nice to see the Vol+ and Vol- buttons being mapped to actual vol up and down, center, up, and down as well as power button! Good progress.
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
I was in a test call on my phone to my home phone. and the screen went dead.

I pushed the end button after a few seconds... and the phone hanged up. so yeah, i would say that it's only a screen fail :)

Oh yeah, buttons work nice, volume and end/call buttons :)

Other thing, when i tried to call to my phone, it ringed 2 times... but nothing to see on my phone itself. after 2 rings it went to voicemail.

Then, when i called to home from my mobile phone, that worked. Strange...
[Touch Diamond, MDA Compact IV ROM Development] timmy1980:
Tried this zimage and it works great on my diam100, buttons work as described making it feel more and more like it should!

Not sure if this is related or not (not even sure it could be!) I have a problem in WM where by whilst connected to my laptop in either activesync or disk mode, after a few seconds my diamond screen turns off and I lose the USB connection. The only reason that I mention it is that it seems to have been doing it since I started playing around with Android??? More than likely a coincidence I realise but thought I would mention it anyway.
[Touch Diamond, MDA Compact IV ROM Development] TheLord-Akira:
tested on diam100

sms works

making a call works (without sound of course)

buttons OK

getting a call not works (caller get busy signal)

this is my second android test. first one (first android 1.0 image from ehmm i dont know) was very fast and smooth. the last one with radio OK is very slow like wm ^^.

i hope it dont depand on radio.

great work guys.
[Touch Diamond, MDA Compact IV ROM Development] c4software:
Strange, on my diamond i can make/receive call.
[Touch Diamond, MDA Compact IV ROM Development] ripnetuk:
Use DropBox to distribute binaries?

If there is really a shortage of bandwidth / space to distribute these rootfs's, why done we just open a DropBox account, and stick it on there? it allows up to 2gb of free storage, and can generate a public http:// link to let others download the file. It also comes with client software to keep the online storage in line with a local folder, so to 'release' a file, you just copy it to the folder, and right-click and do 'copy public url'. It has none of the annoyingness associated with RapidShare et al...

Alternatively, I have a unlimited bandwidth and unlimited storage account with DreamHost, so I can host anything that needs hosting...

Really excited with all the recent progress... thanks to everyone working on this :)

george
[Touch Diamond, MDA Compact IV ROM Development] Arktronic:
Same thing happens on my Fuze. Which device do you have? (BTW, it'd be nice if everyone put their device info in their signatures ;))
[Touch Diamond, MDA Compact IV ROM Development] gunar_adrian:
I tried to install Android on a Diamond with 7201 chipset and this is the log.

Any idea?
[Touch Diamond, MDA Compact IV ROM Development] frysee:
storage/bandwidth problems...

another way for hosting the necessary files: Wuala

Once uploaded, the files are (encrypted, splitted and) spread all over the Wuala network - you get 1GB space to start.

This would solve the bandwith and storage problems and its easier to follow all the progress :)

A little example: Linux/Android on HTC Diamond

The files can be accessed by using your browser or downloading the optional java-client for more options (e.g commenting, adding your own files, filesystem integration etc.) ;)

greetz
[Touch Diamond, MDA Compact IV ROM Development] camdenb:
Running on HTC Fuze

Hi folks, just writing to report that I have successfully booted android on an HTC Fuze, using the directions in the wiki and LordKiwi's initrd.cpio. Radio does not appear to work, sound does not appear to work, hardware buttons don't work, and I cannot find this spare parts app!

but it boots!

now that I've been through the fires of initial setup, I am willing to do further testing if anybody needs me to.

EDIT: Also, thanks a ton for all your hard work, guys!
[Touch Diamond, MDA Compact IV ROM Development] lattiS710:
Which files from this site do I need to run android with (almost) working radio and hardware buttons?

http://87.72.13.87/

sorry for this noob question :o
[Touch Diamond, MDA Compact IV ROM Development] jringo718:
I am having trouble with mounting my 1GB Sandisk Microsd. I don't have a linux system, only Vista, so I am not sure how I stop the /mmc/tmp/system.ext2 not found, etc etc errors from showing up. I have transferred the files through a memory card reader as well as through activesync and i've tried it with activesync on and off.

I have tried a combination of the files from last week and now I am using the Haret18 and zimage-jobo from his site, the system.ext2.img and userdata.img from the cupcake gz, and the cache.ext2.img and intrid.droid.gz from the wiki(the intrid.droid.gz is from Lordkiwi's modified Touch Pro intrid) I put everything in tmp on the root of memory card.

I have a Sprint CDMA Touch Pro btw. It shows that mmc error then I calibrate the screen and type /init.android and press enter. It says loading ANDROID and a bunch of stuff and then just hangs.

Thanks guys.
[Touch Diamond, MDA Compact IV ROM Development] nuke1:
Please state your device: Raph or Diam?
[Touch Diamond, MDA Compact IV ROM Development] lattiS710:
nuke1, u r really helping me a lot, thank you :)

i have a diamond
[Touch Diamond, MDA Compact IV ROM Development] counterfitninja:
Im trying Diamond as well, not much luck. Got it work earlier this week, but wanted to try new keyboards
[Touch Diamond, MDA Compact IV ROM Development] xianthax:
more on the touch part of the navipad, forgive me if this is already known

fired up HaRET (very good work whoever created this diog tool btw)

i noticed that just touching the navi pad fires these IRQs:

001936: mem IRQS(1) 95300084=00000001 (00000001)

004332: mem IRQS(0) 95300080=00080000 (00080000)

004332: mem IRQS(0) 95300080=00010000 (00010000)

this is interesting, in normal embedded design practices with i2c you want to avoid polling on the bus because its a slow bus and designed to be shared with multiple devices. In this case the cypress part only supports i2c slave operation and therefore can never initiate a transfer itself. the presence of this IRQ would indicate to me that the cypress touch sense IC has a GPIO pin or 2 tied back to the qualcomm chip to trigger this IRQ in the qualcomm chip effectively saying "hey i have some information you may want"

I would try just sending a read request to the cypress IC after catching this IRQ (i'm assuming you can find the trigger for this IRQ in the linux kernel too?) you may find that the cypress IC will just dump some information to you, probably just the finger location(s) on the touchpad.

If this is true then there is no need to decipher the i2c protocol but just decipher the data that comes back from the cypress IC which should be pretty easy...

I'd try the atmel controller also, as it may have something to do with this?

so the questions are:

1) does simply touching the navipad fire an IRQ or event in linux?

2) what are the i2c addresses of the cypress and atmel parts?

if someone is familiar with the i2c driver in the linux kernel, would you be willing to scan the bus? Unfortunately i work in mostly custom embedded OS's or bare metal so i'm not familiar with the procedure in linux

By scan i mean for each possible address do this:

Start Condition

7bit Address with R/~w = 0 (shouldn't matter usually)

Stop

and record if the address transmission is ack'd.

addresses that are reserved and don't need checking, assume lsb is R/W:

0x00 through 0x0F

0xF0 through 0xFF

that would give us the list of all I2C addresses that are active in the device, and may be faster than trying to disassemble the windows dll to find them

cheers,

x
[Touch Diamond, MDA Compact IV ROM Development] iservealot:
In an effort to not sound dumb here, am I reading correctly that there has been an "end" button mapped correctly?

When I try to the new zImages posted here, all I get it a faded grey screen whenever a button is pressed. ...am I missing something here?
[Touch Diamond, MDA Compact IV ROM Development] xvx45:
With files found here : http://xdaforums.com/showpost.php?p=3130207&postcount=1426 work great with my DIAM100, for the moment I only test sound with calling my voice mail but no sound of course, keymap work grea too.
[Touch Diamond, MDA Compact IV ROM Development] allofthepeople:
I'm running the Sprint HTC Touch Pro, any one ever fix the frezing after the pwrsink_set: STUB! messages yet? I also am not seeing a keyboard.

Thanks
[Touch Diamond, MDA Compact IV ROM Development] mdrobnak:
You need to run the "Spare Parts" application in Android, and map the end key to go back home. The default is to go to sleep, which causes the issue you're experiencing.

-Matt
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
We can make any row the top row (or bottom row for that matter) by putting the gpi number for that row first (or last for that matter) in the row_gpios array. same for columns.

Yes, if you request an irq for gpio #94, that will fire when you touch (not even press) the navi pad.

It seems that there are more devices on the bus than just the navi touch pad. So we would have to be able to tell from the data which device sent it.

Added this one to FAQ on the wiki :) (2x or 3x is frequently)

Following the example of lavender.t, I added a new kernel boot option for the virtual keyboard: msmvkeyb_toggle=hide makes the vkeyb initially hidden/collapsed (you see the blue square only) and msmvkeyb_toggle=off makes it not even init at all. (Now that we dont need the vkeyb for all the time for everything anymore..)

static int __init msmvkeyb_toggle_setup(char *str)
{
if (!strcmp(str,"off"))
vkeyb_toggle = -1;
else if (!strcmp(str,"hide"))
vkeyb_toggle = 0;
else
vkeyb_toggle = 1;
return 0;
}
__setup("msmvkeyb_toggle=", msmvkeyb_toggle_setup);

Also, I connected the 'keyboard slide open'-gpio, so that android turns landscape when you open slide open the keyboard on a raphael, see attached pictures. Here is kernel with this boot option and the rotation. I shall post code/diffs shortly..

-Jobo

Hmmm ... that wallpaper image got shrunk by the attachment system .. it should be 720x640.
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
Wuala has fast downloads and it's easy to use... overall, seems great! I became a member on there and hope that updates will be uploaded there.

Downloaded all the latest files for Android 1.0 for my Diamond. Tested jobo's image that was on there (no clue if it was the latest one around!?). It had dragable & hideable onscreen keyboard either way.

First try = failure. Got stuck after some mmcblk0 stuff. I read it might be with USB connection from WM6 - if the device had been connected to a PC and was disconnected when trying to start Andriod it would failed. In my case I've justed transferred the files to my device and disconnected it from the PC - so USB connection was NOT active.

After a reboot of my device I managed to get past the prior stage and boot into Android from the shell using /init.android.

Using a DIAM*00 - how do I find out exact version?

Got nothing new to add, but atleast I tested it out ;)!

init: cannot find '/system/bin/playmp3' disabling bootsound or something similar in the shell right after /init.andriod

The com.android.settings error

LCD display screen issues during sleep state - same as everyone else

I was able to see my carrier and the network in use in the "status screen" of Andriod

Since you just released this new zImage I was able to test it out on my Diamond. Added the command to default.txt:

set cmdline "mem=64M msmsdcc_id=2 msmts_calib=0x7a.0x5e.0x35a.0x37f [b]msmvkeyb_toggle=hide[/b]"

, and it works. My Diamond booted into Android in landscape mode, and I wasn't able to change it. I understand this is a image for Raph, but reporting either way. Also the virtual keyboard didn't rotate (and I don't know if it's supposed to - probably not...). So typing on the Diamond was a pain - of course.

Another thing I noticed: Android perhaps thought there's a hardware keyboard slided out? Because I can't seem to get the official onscreen keyboard up in the Google searchbox.
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
The GPIO that indicates whether the keyboard is out (1) or in (0) always reports 1 on the Diamond, which is why you get the landscape on diamond.
[Touch Diamond, MDA Compact IV ROM Development] frysee:
Thats what I said :D

Would be nice to concentrate the new files there as it works with good speed for everyone.

Yesterday I tested the new files by myself, android wont accept my PIN - any ideas? :(

greetz
[Touch Diamond, MDA Compact IV ROM Development] NoBody20013:
as far as i know: try disabling PIN in Win Mobile
[Touch Diamond, MDA Compact IV ROM Development] mdrobnak:
What he said. :-)

It's in the FAQ on the Wiki

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

-Matt
[Touch Diamond, MDA Compact IV ROM Development] frysee:
Wow, I'm sure this wasnt in the wiki yesterday :rolleyes:

greetz
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
Alright I see. Quick question: I wasn't able to use the official on-screen keyboard with that image. Was it because Android inactivates it if GPIO for the keyboard reports 1, or was it because it doesn't support landscape mode, any clue?

It was added recently ;)
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
I honestly don't know. Best guess would be that it doesn't use the android-keyboard because it is in landscape, and on G1, that means the keyboard is out. Android probably assume a keyboard when it is in landscape mode. The kernel just sends a EV_SW (swap) event, not a specific event that indicates the keyboard is actually out (as far as I know, jobo could confirm this perhaps).
[Touch Diamond, MDA Compact IV ROM Development] c4software:
I make a video of Android on Diamond.

http://www.youtube.com/watch?v=Ws7lSl8UfuY

For those who are afraid to test.
[Touch Diamond, MDA Compact IV ROM Development] allofthepeople:
I finally got it to show the keyboard and last prompt but the visual keyboards still not working for me?
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
Correct. It would be nice it it were always low on diamonds, but what can we do..

I don't get the soft keyboard either when switched to landscape mode, and NetRippers best guess is mine as well: Android doesn't do soft keyboard (or soft keyboard doesn't do itself) when the keyboard is open. (The GPI doesn't request landscape mode, it indicates hardware keyboard open.)

The kernet sends and EV_SW (switch, not swap) and does provide whether the switch is on or off. But in Diamonds, the gpi in question indicates that the keyboard is open.

I put this code:

void htcraphael_init_keypad(void)
{
/* no slider switch for diamonds */
if (!machine_is_htcraphael())
htcraphael_keypad_data.info_count = 1;

..in board_htcraphael_keypad.c, as a quickie to inhibit the switch on non-raphaels (thanks for that tip last night NetRipper), but I guess I have to build separate kernels for raph and diam (or update to the latest git ;) ? ..or both? :confused:) for that to work?

Right. :) Please add frequently asked questions to the FAQ, preferably along with the answers.

-Jobo

EDIT: Oh, and by the way, I changed the keypad mapping so that up='menu' and down='back'. Having a back button is nice, so you don't have to go all the way back to the home screen every time. I can't seem to get the menu button to perform a menu like function.. I tried KEY_MENU, 229 (softkey1) and 230 (softkey2) but neither work.

Moreover, apps or activities seem to crash a lot when tapping the wrong key at the wrong time. I see this message a lot:

W/KeyCharacterMap( 198): No keyboard for id 0
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
The fun thing about machine_is_htcraphael() is that it checks the mtype at runtime. Any #if or #ifdef's are compiletime. With the machine_is_xxx() style we can build a single kernel with support for both diamond and raphael. However, diamond users must set mtype 1805 and raphael users must set mtype 1910 (we now all use 1910). This is already present in git, which is why I suggest you also update your local copy to the latest git. Currently the kernels you build cant be used with mtype 1805 (it will simply hang at the haret screen, as the kernel bails out directly when it doesn't recognize the mtype).

Also, when you update your git, you will have two board files. One for raphael and one for diamond. That way you can also just enable the GPI thingy in raphael, and leave it disabled by default for any other mach's. It's also done this way with the SD slot card detection.

Obviously, for the kernel to support both raphael and diamond, you need to have both CONFIG_MACH_HTCDIAMOND and CONFIG_MACH_HTCRAPHAEL enabled in your .config file, so that it builds both mach's.
[Touch Diamond, MDA Compact IV ROM Development] poxo:
when I'm in the android htc my screen gradually fades diam 2 seconds, then nothing blank screen.

happen after a few dozen seconds or when I press the pad "arrow" or when I press the button "end", "top down", "page up "....

Apart from that everything is fine, as-OK, sms-OK, OK-pad, ....

you have a solution, thank you in advance Paschal.
[Touch Diamond, MDA Compact IV ROM Development] jlavoie:
change screen timeout to never and also change the end button behaviour to go home and not sleep.
[Touch Diamond, MDA Compact IV ROM Development] poxo:
just little problem

when I'm in the android htc my screen gradually fades diam 2 seconds, then nothing blank screen.

happen after a few dozen seconds or when I press the pad "arrow" or when I press the button "end", "top down", "page up "....

Apart from that everything is fine, as-OK, sms-OK, OK-pad, ....

you have a solution, thank you in advance Pascal.
[Touch Diamond, MDA Compact IV ROM Development] butterdori:
Instead of using the keyboard out GPI, is there something that can trigger just the landscape view (using the g-sensor to switch between them for diamond, perhaps)? This leads to the question, is there a (cupcake) keyboard for landscape as well?

Would making a kernel that supports both devices increase its size significantly? Or would this more depend on what the differences are between the two..
[Touch Diamond, MDA Compact IV ROM Development] Arktronic:
While a single kernel is probably a good idea at this early stage of development, once the kernel is more or less stabilized, we should switch to compile-time conditionals and have separate builds for Diamond and Raphael as that would make both kernels smaller, easier to debug, and (theoretically) faster.

EDIT: butterdori beat me to it :)
[Touch Diamond, MDA Compact IV ROM Development] allofthepeople:
nevermind... another site says delete calb line in default.txt
[Touch Diamond, MDA Compact IV ROM Development] poxo:
OK, "dispaly screen" = timeout never

but when I press on keypad "<---"	the screen goes blank !@]@!!@°°@!!!:mad:
[Touch Diamond, MDA Compact IV ROM Development] curiousblue:
this is a problem thats been discussed earlier in the thread. take a look at the wiki and FAQ.
[Touch Diamond, MDA Compact IV ROM Development] jlavoie:
from wiki:

When I boot android 1.0, the screen fades to black / gray / weird liney pattern when I hit some key (home, end, F4) or even when I do nothing

This happens when the phone goes to sleep. There are 2 things to prevent this: For the timeout, go to settings->sound and display->display timeout->never timeout. (default is 1 minute) For the button/key thing, go to spare parts->end key behavior->go home. (default is sleep or home+sleep)
[Touch Diamond, MDA Compact IV ROM Development] poxo:
thank you :)
[Touch Diamond, MDA Compact IV ROM Development] Dasken:
just wondering....

if the development is going forward, i´m realy hoping to juse adroid in my HTC Tuch Diamond:)
[Touch Diamond, MDA Compact IV ROM Development] allofthepeople:
mines doing the cannot find /system/bin/servicemanager , disabling servicemanager thing I tried "is/mmc" like suggested it says "/bin/sh: is:/mmc: not found"
[Touch Diamond, MDA Compact IV ROM Development] Arktronic:
FYI, it's not "is/mmc", it's "ls /mmc" - LS, just all lowercase, and a space between that and "/mmc".
[Touch Diamond, MDA Compact IV ROM Development] allofthepeople:
i tried it both ways...
[Touch Diamond, MDA Compact IV ROM Development] allofthepeople:
just tried to run it from device and not card but same issue
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Depends on the differences between the two. Generic parts are only kept once. I just tested it and compiling for one specific device saves 892 bytes. We'll see how it goes. I guess experience will tell. I'm new to this as well ;)
[Touch Diamond, MDA Compact IV ROM Development] sticks13:
Quick Question

Hello All,

Thanks to everyone who is contributing. I have been following this thread for some time now, checking it several times daily while I'm at work! :D

I plan on picking up a Raphael from Verizon in the next few days. I'm quickly learning the work involved to port android over to the raphael. I know everyone is working hard on this, but when might we expect a fully working version of Android on the raphael? Are we talking weeks or months here?
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Hi. I should warn you about the Verizon version of Raphael. If I'm not mistaken, the Verizon one is the raph500. That phone seems to have a different chipset from the other Raphaels.

The raph100, raph110, raph800 have the MSM7201A. The raph500 seems to have MSM7500A.

Although someone is already working on the raph500, I thought I should warn you anyway ;)

Pretty please correct me when I'm wrong :)
[Touch Diamond, MDA Compact IV ROM Development] ydoucare:
Running on my Sprint Diamond (DIAM500), with the funky colors. Appreciate all the work everyone is doing on this! Can't wait to see what is down the road.
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Sprint Diamond (CDMA) is DIAM800, not 500.
[Touch Diamond, MDA Compact IV ROM Development] ydoucare:
Then why does it clearly say DIAM500 in device info?
[Touch Diamond, MDA Compact IV ROM Development] Bimboy:
Go to the bootloader screen, and see what your device is there.. (Hold Vol down button while doing a soft reset, until tri-color screen appears)
[Touch Diamond, MDA Compact IV ROM Development] mattdh:
I second that answer. I have my Sprint Touch Diamond right here in front of me and its clearly the DIAM500.