yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
Allright, so i booted, it works great. the slide problem is now gone.

It automatically found my network and logged on and i could make a call. Of course, you can't hear anything on both sides, but it works.

When i tried to put roaming on (that's needed for my network's data connection) the settings dialog freezed and forced quitted. Really nice work though, beginning to get a lot better and better!

Too bad that while in the call, the screen got lines and all like before and went to dark... weird that that happens... power management issues?

Edit: same thing as when you type F4. What's even weirder. i can see the windows/touchflo 3d a little bit when the screen goes weird. That's even weirder!
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
no no no no .. thank _you_! :)

Does it also have the toggle thing and the non-flicker thing? Or should I try and produce a clean diff?

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] rl2000:
Isn't it about time to remove the "drawing" yellow dots thing from the framebuffer?
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
Yeah, i was thinking the same. Also, how can you disable the system keyboard again? i can drag it, but can't seem to disable it.
[Touch Diamond, MDA Compact IV ROM Development] rl2000:
I just tried the cupcake-20090103-2.tar.gz that was posted and it asks me for a PIN code? And the right one is "incorrect". Anybody else seeing this? I'll try to boot it a couple more times. Also, I can't seem to disable the keyboard either, only drag it.

UPDATE: Disabling PIN code skips this but as soon as I get the desktop it tells me I've lost connection due to roaming is disabled. When I try to enable it gives an error message and I'm stuck in that menu. Also as someone else mentioned F4 is a killswitch :P

The other Fkeys seem to enable some color chart like the ones shown on screenshots back when there was talk about the screwed colors of the CDMA version.

Booting a couple more times and selecting to ignore that I don't have a gsm connection I can use the system okay but the "bks" backspace thing doesn't go bakc in the menus though.
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
I would advise you to not try to input a pin for more then 2 times (maybe it will block...). You can try to disable your sim pin code and see if the message dissapears. Good to know thougs that iw probably doesn't communicate good in pin checking.

On the other hand, it could be (i'm not so lectured on sim cards) that because you are booting from windows mobile, the sim is already in ready mode, but android sees that there is a pin code on the sim... something like that..

Anyhow, minor issue for now i would say.
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
Tap the green square. It should turn blue. The vkeyb is now off. It doesn't go away until the screen updates that section, but in android thats quite often.

If it works as in those attached images with the kernel I posted earlier (in the update), then that code is just not in here and I shall produce a diff. If that one doesn't work either, you're doing something wrong. ;) (Tapping without dragging, even with a 3 pixel treshold is not always easy, depending on the time of day..)

-Jobo

EDIT: I just tried the kernel in the package lavender.t posted. It does not have the toggle feature. (So it's not you ;) ) Also, that kernel makes android run in safe mode for me.

EDIT: A diff of the entire tree turned out a bit messed up, but this is a diff for msm_vkeyb.c that has the toggle behavior.
[Touch Diamond, MDA Compact IV ROM Development] c4software:
Hi,

In my Diamond. the Bks button on Vkeyboard seems not map because when i press it i'm not return in the home screen.

maybe mapping keys would be the major todo point.

PS: My diamond gone sleep, and i can't turn on. (reboot :D)

PS': Call Works :D
[Touch Diamond, MDA Compact IV ROM Development] plbelanger:
As soon as wifi and making/receiving calls work I'll jump on...till then, keep up the great work! At this rate, perhaps the touch diamond will be the 2nd Android device :)
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
Yeah, i think mapping at least a hardware key to get back to the home screen would be a major todo point.
[Touch Diamond, MDA Compact IV ROM Development] holydhaliwal:
Hey guys im trying to get this working but have had no success so far, from reading through the last 4-5 pages i think its a problem with my sd card not being mounted, as probably a few others have, i just want to be sure before i start reformating it,

1- i should have one vfat partition and one ext2 partion?

2- which one should have the /tmp in its root directory?

3- Also will windows mobile be able to read the "storage" partition,

4- Another thing is how big should the partition that is holding the /tmp folder be?

Thanks a bunch guys! good progress in the last week or so!:)
[Touch Diamond, MDA Compact IV ROM Development] Bimboy:
I used lavender.t's image, along with your zImage-Jobo, and I did get the toggle. I'm not in safe mode (

for the first time

!!!), and I can make calls, but do not have data capabilities. I also get the new pop-up keyboard when using google search.

If I go into the Settings app, I can see that my SDHC is not mounted in Android, as it says 'not found'. Also, just after the SDHC card is found, I get the following:

[ 3.406379] EXT2-fs warning: mounting unchecked fs, runni

ng e2fsck is recommended

I am assuming this is due to me not having created a partition on my SD card, and merely have it formatted FAT32 with my img files in a tmp dir?
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
Try using the lavender.t images, that is the most simple solution.
[Touch Diamond, MDA Compact IV ROM Development] plbelanger:
I have used linux exclusively for 10 years and you can disregard that...It's just a warning because the fs hasn't been checked...you can check it if you like using fsck. However, I'm not sure exactly all the internals of android and this port work as of now.
[Touch Diamond, MDA Compact IV ROM Development] iAmNotorious:
I hope you don't mind but I'm impatient and that server was a bit slow so I uploaded it to my place to mirror..

http://dirtyhippie.org/files/cupcake-20090103-2.tar.gz
[Touch Diamond, MDA Compact IV ROM Development] holydhaliwal:
I am using lavender's images however they aren't working for me, i have a cdma diamond btw...so in what way should i re-partition?
[Touch Diamond, MDA Compact IV ROM Development] Gavin_H:
Ok, I've been messing with lavender.t's upload and in case it's helpful the following works:

I can receive but not send SMS.

I cannot access the internet.

I can make and receive calls, but they are silent.

I can play snake. (It's crap)

If you go to the 'Spare Parts' App and change the "End Button Behaviour' to "Go To Home" that will change the "End" key on the soft keyboard to go back to the home page.

F1 on the soft keyboard appears to work as the 'Menu' hard button.
[Touch Diamond, MDA Compact IV ROM Development] ChiefmasterB:
Hm... I´m not a developer.... but I wonder why some guys get android running fully on an ASUS Eee PC?

http://www.chip.de/bildergalerie/An...sus-Eee-PC-1000H-Galerie_34300064.html?show=2

The review says that the guy needed just 4 hours to get android running on the PC.....

any help for diamond-porting?
[Touch Diamond, MDA Compact IV ROM Development] NielDK:
I think the guys working on this here has come just about as far as the EEE port. Just, remember, the EEE is NOT a phone, so the radio part (phone, SMS and so) is not applicable for that project, as it is for a phone.
[Touch Diamond, MDA Compact IV ROM Development] sandmen:
wiki + howto

Hi guys,

nice to hear the progress with linux + android.

Is it possible to make a small howto in the wiki.

1. Bake a cupcake like lavender.t

1.1 howto make kernel

1.2 make userdata + system

1.3 make android

thanks
[Touch Diamond, MDA Compact IV ROM Development] Krad213:
And what about G1's rom leaked out is it completly useless ? Cuz G1 has almost the same hardware ...
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
Hey, that's a nice discovery. makes checking android out much easyer! thanx
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
I put a 'build your own' section underneath 'useful links', with how to build haret, how to build kernel, how to build android.

(I shall add a bit more on how to copy it to your phone and boot into it.)

After I applied that change, it started prompting me for a PIN at startup too. It doesn't matter whether or not I had unlocked the SIM prior to booting linux. It doesn't matter whether I use 'a kernel that makes android run in safe mode' (whatever that means) or not. Disabling SIM PIN gets rid of this. Phone and SMS works.

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] sandmen:
@touch of jobo

i want to try.

thanks.

I think this patch is not included or klick
[Touch Diamond, MDA Compact IV ROM Development] katmandu421:
Aha!! The stylus must be out before booting in order to get the onscreen keyboard!

...but how in the world do you type /init.android on it :eek:

EDIT: Wow, my screen is mirrored, down is up, up is down. I think I remember seeing this in .8 at some point...and there was a fix, Any ideas?
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
What kind of phone do you have, and what kind of provider/brand.
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
By the way, maybe we can look how the ppl at the vogue android topic mapped hardware buttons. Don't they commit their changes?
[Touch Diamond, MDA Compact IV ROM Development] dcordes:
can somebody with gsm diamond please build the current htc-msm-2.6.25 revision with htcdiamond_defconfig and check if everything works as it does with the old code plus lavender.t patch?
[Touch Diamond, MDA Compact IV ROM Development] katmandu421:
CDMA HTC Touch Doamond on Sprint, Juicy's ROM
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Please note that I split up Raphael and Diamond in the git tree.

The Diamond and the Raphael have their own board files now, due to differences with SD card detect and probably more differences to come.

When booting this kernel keep in mind that you need to configure the correct mtype in haret's default.txt:

1805 for Diamond

1910 for Raphael

I have tested this for Raphael to work properly, but not yet for Diamond. Would be nice if anyone could.

edit: just fixed an error in git that prevented diamond board from compiling into the kernel... also, you can use this zImage for the test, just cleanly compiled from a clean defconfig.
[Touch Diamond, MDA Compact IV ROM Development] sandmen:
I try it, just downloading.

i need a little bit more time. (old debian and no JDK5 update 12)

i set up a new virtual machine :(
[Touch Diamond, MDA Compact IV ROM Development] petay:
i have been playing with the image on the wikki and added the files from the cupcake branch and i must say its fantastic!!! i eagerly await the day when its the only os on my diamond.

one thing i will sat is that i dont see the need for the on screen floaty keyboard anymore. once android is booted it is just in the way, i only need it to get back to the home screen. once the hardware buttons are properly mapped i will have no use for the floaty keyboard.

Also when the screen fades (if you leave the fone for long enough) is there any way to get it back on??
[Touch Diamond, MDA Compact IV ROM Development] balsat:
I just compiled it, and it do not find my /dev/mmcblk0p2.
[Touch Diamond, MDA Compact IV ROM Development] dejant_9:
I've used the haret.exe and cache.ext2 of the wiki, the 3 images of the cupcake-20090103-2 and rename this "20090401_zImage_git.txt" to "zImage" and put all of this in a tmp folder on my phone. No problem android boot in normal mode. I've the draggable keyboard, i can make a call etc.. i juste have some error messages with "force close" and "wait" buttons.
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Erm, the kernel (20090401_zImage_git) does not have the draggable keyboard. I think you must have done something wrong. :)

I see it as well. Let me find the problem and fix it.
[Touch Diamond, MDA Compact IV ROM Development] dejant_9:
woops! sorry,i made a mistake.. i test now this new kernel.

edit: (your right, no draggable keyboard ..) android boot with the default.txt of the wiki. but,

My diamond boot fine with mtype set to 1910. No problem, same functions available.

But with mtype set to 1805, init stop to " [21.700061] trout_pwrsink_set:STUB!"

With the other kernel(cupcake) and mtype set to 1805, haret crash
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Fixed the Diamond mmc problem in git. Latest git should supports mmc for Raphael and Diamond (GSM versions) without needing to specify msmsdcc_id. Here's a zImage, if someone with a Diamond could verify to make sure, that'd be great.

Should be fixed now.

@jobo

Did you mention having a cleaner .diff for the draggable and toggable vkeyb than the one you already provided? I still got the one from a few weeks back. If so, let me know. :)

And anyone know any other patches that are already available and should be added to git?
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
I've been trying to get some hard buttons working, but not really successfully. :( It looks like we don't get all GPIs, maybe the hardware keyboard on the Raphael is not even GPI driven, and then there is the thing where monitoring one GPI will inhibit another, just to make things difficult (and slow)...

Without changing the GPIO drivers in arm/mach-msm (except for disabling halibut/trout keypads in board_htcraphael.c:halibut_init()), the following GPIs work work: (Tested on raph100)

38 - keyboard slider open

40 - left 1/3 of the navi pad: home/left/phone

41 - volume up / volume down

42 - right 2/3 of the navi pad: up/down/center/right/back/end

83 - power button

94 - navi pad touched (not even pressed) anywhere

This is the test driver code I wrote to investigate, in case someone can use it to get further.

In this kernel (yes, I keep replacing that one), the volume up and down buttons do 'end'.

UPDATE: The gpio test driver apparently makes diamonds hang. I updated the kernel with one that only monitors the GPI for the volume buttons (which should act as the 'end' key) and no others. Maybe that helps. (Let me know.. :)) I also built one without the gpio driver, so that gives you nothing new (except the vkeyb toggle?).

I attached the diff for msm_vkeyb.c only to this post. If that conflicts or doesn't work, I can generate a complete diff of the entire tree, but that's quite messy...

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
With your new zImage i get the following error:

Console handover: boot [htc_fb0] -> real [tty0]

At least, that's the last line it shows, then it stops.

I have a HTC Touch Diamond unbranded (DIAM100)
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
Tested it, get the same message a couple of times , but it boots through though. seems working fine...
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Jobo has a Raphael. Could be that some gpio's that are raphael-specific that jobo is trying to access is causing a hang on the Diamond. I.e. the "keyboard-slider" is something the Diamond doesn't have.
[Touch Diamond, MDA Compact IV ROM Development] dejant_9:
same here on diamond unbranded.

Originally Posted by NetRipper :

Fixed the Diamond mmc problem in git. Latest git should supports mmc for Raphael and Diamond (GSM versions) without needing to specify msmsdcc_id. Here's a zImage, if someone with a Diamond could verify to make sure, that'd be great.

Should be fixed now.

no, same problem..
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Are you using mtype 1805? And USB must be in Activesync mode (not disk drive). Other than that it should work on GSM Diamond. Multiple people have tested and verified as ok. You're sure you use the 01 zImage? :)
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
The gpio test driver apparently makes diamonds hang. I updated the kernel with one that only monitors the GPI for the volume buttons (which should act as the 'end' key) and no others. Maybe that helps. (Let me know.. :)) I also built one without the gpio driver, so that gives you nothing new (except the vkeyb toggle?).

I think that was @me. Another case of my gpio test thingy breaking diamonds... (@dejant_9: was it? and if so: does the update fix it?)

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] DfenZ:
can someone post the latest progress or update the wiki? i just get confused reading the thread : P
[Touch Diamond, MDA Compact IV ROM Development] holydhaliwal:
I can confirm that i have gotten it working on my cdma telus diamond (finnally) of course colors are still messed up, messed up in a different way then with android 0.8 though i noticed, its a lot more blue lol. Also performence seems to be a little laggy, anyone else notice this? Not sure if this has to due with early code or anything...
[Touch Diamond, MDA Compact IV ROM Development] Gavin_H:
I noticed that when going through the F buttons on the "floaty" keyboard that a bunch of different sets of colour bars come up when you go between F8-F10. Maybe if you messed with those you could sort out the colours? Unlikely I know, but maybe a clue to the actual solution?
[Touch Diamond, MDA Compact IV ROM Development] lavender.t:
works nicely in my diamond

it worked like a charm in my DIAM110 :)

regarding the code, netripper, should we, at a certain point, separate MACH_HTCRAPHAEL and MACH_HTCDIAMOND totally ? now they are built together only to be switched by the MTYPE.

it means some more code changes like quite some #ifdef CONFIG_MACH_HTCRAPHAEL need to be changed to #if defined(CONFIG_MACH_HTCRAPHAEL) || defined(CONFIG_MACH_HTCDIAMOND).

- lt
[Touch Diamond, MDA Compact IV ROM Development] mdrobnak:
Wow everyone's on a roll..

I'll have to check out these later kernels to see how they are on the Fuze..

-Matt
[Touch Diamond, MDA Compact IV ROM Development] dejant_9:
kernel with gpio work for my diamond. vol down = go to home :D

@NetRipper yes it was the good zimage.. :rolleyes:

i don't know, maybe Activesync problem. today it work fine..

so, Netripper fixed the Diamond mmc problem,and now diamond boot fine with the good mtype (1805). Jobo update kernel with volume down patch and draggable keyboard but diamond don't boot with the good mtype. Maybe everyone have to start with a unified kernel?

And after that, maybe someone can try to update the wiki with latest kernel and all latest ext2.img, I want to make that but my english is so bad :(
[Touch Diamond, MDA Compact IV ROM Development] timmy1980:
I did notice performance was a little slow too (diam100) but assume that this is down to it still being in the early stages?

I'm really impressed with the progress here, seems like Lavender getting 1.0 to boot was the break through everyone was waiting for.. since then there has been some awesome work from all involved! (netripper, jobo etc.. sorry if i've forgotten to credit anyone!) Very exciting stuff!

On a side note, I noticed that the ambient light sensor works in android... screen brightness is adjusted automatically. Is this expected?
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
looking into hardware buttons / navi pad

I have been looking into hardware buttons and the navi pad a bit more.

The 'home', 'send', and 'left' button are the same (pressing one while olding down the other doesn't give another click). Same for 'end', 'back', 'right'. Up and down can be pressed at the same time, and both give a click, but might be wired together, maybe even along with the center button. To tell where you press, the surface is a touch pad. (The input device driver for the navi pad would be a combination of multiple (2) platform devices?)

Looking at this touch pad, I found the following:

In HaRET, when you look at physical address 0xA990000C, the first byte of that word changes a lot when touching the navi pad (the thing that fires GPI 94 in my earlier tests). There is a little bit of a pattern in values versus finger movement, but not entirely clear or consistent; maybe have to only read at the right moment (in the irq handler?). 0xA9900004 contains 0x072D.

In Linux, When I watch 0xA990000C, it contains some value that doesn't change, but it's different every time I boot, so I guess it just doesn't get updated. 0xA9900004 contains 0x035D.

All these addresses are in the I2C region according to the memory map on the wiki. In i2c_msm.c/msm_i2c_probe(), it says:

enum {
I2C_WRITE_DATA = 0x00,
I2C_CLK_CTL = 0x04,
I2C_STATUS = 0x08,
I2C_READ_DATA = 0x0c,
I2C_INTERFACE_SELECT = 0x10,

[... skipping about 350 lines to msm_i2c_probe() ...]

/* I2C_HS_CLK = I2C_CLK/(3*(HS_DIVIDER_VALUE+1) */
/* I2C_FS_CLK = I2C_CLK/(2*(FS_DIVIDER_VALUE+3) */
/* FS_DIVIDER_VALUE = ((I2C_CLK / I2C_FS_CLK) / 2) - 3 */
i2c_clk = 19200000; /* input clock */
target_clk = 100000;
/* target_clk = 200000; */
fs_div = ((i2c_clk / target_clk) / 2) - 3;
hs_div = 3;
clk_ctl = ((hs_div & 0x7) << 8) | (fs_div & 0xff);
writel(/*clk_ctl*/ 0x72d, dev->base + I2C_CLK_CTL);
printk(KERN_INFO "msm_i2c_probe: clk_ctl %x, %d Hz\n",
clk_ctl, i2c_clk / (2 * ((clk_ctl & 0xff) + 3)));

dmesg says:

[ 0.430000] msm_i2c_probe: clk_ctl 35d, 100000 Hz

So the driver calculates a (wrong?) clock control value for the i2c bus. Merely writing 0x072D in stead of clk_ctl is not enough to make it work. (If only we knew someone who is good with clock divider values and stuff :p )

About the not updating thing: In msm_ts.c, we apparently need to clear some bits in some registers for the position to get updated again:

/* Without next 2 lines, position won't get updated */
writel(readl(MSM_TS_BASE + TSSC_CTL) & ~0x400, MSM_TS_BASE + TSSC_CTL);
writel(readl(MSM_TS_BASE + TSSC_CTL) & ~0xc00, MSM_TS_BASE + TSSC_CTL);

.. maybe we need something similar for the i2c data (after all .. it _is_ another touch panel). I have no on clue how to figure out which bit in which address if any. (There are so many...)

Another thing I could tinker with (unless someone with actual knowledge tells me its a waste of time) is the 'interface select' register. In HaRET, that address contains 0x0300 (which is _SELECT_SDL | _SELECT_SDA but not _SELECT_INTF_SELECT). Let's see...

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] balsat:
And if you hold the vol up for a while = Phone power off
[Touch Diamond, MDA Compact IV ROM Development] zycho:
which files do you use for diam300?

can anyone pls post current working links to the files?
[Touch Diamond, MDA Compact IV ROM Development] Blazeitup123:
Android now running on HP Mini-Note 2133

http://www.engadget.com/2009/01/05/move-over-eee-android-now-running-on-hp-mini-note-2133/
[Touch Diamond, MDA Compact IV ROM Development] jbelman:
any advice where I'm going wrong?

Am using DIAM100 running WM 6.1 (ROM VER: 1.93.161.2 WWE, RADIO VER: 1.00.25.03, Protcol Version: 52.26a.25.09U)

Connected to PC using ActiveSync and moved the following to a folder on internal storage.:

http://members.home.nl/j0b0/zImage-nogpio-jobo

http://members.home.nl/j0b0/zImage-jobo

Haret.exe (0.5.2)

default.txt:

set MTYPE 1805
set KERNEL zImage-nogpio-jobo
set RAMSIZE 0x7800000
set RAMADDR 0x10000000
bootlinux

Launch haret.exe shows: Found machine Generic MSM7xxxA

Run then I just get "HaRET: Booting Linux ... " (left this for 5 minutes no joy)

So swapped default.txt to:

set MTYPE 1805
set KERNEL zImage-jobo
set RAMSIZE 0x7800000
set RAMADDR 0x10000000
bootlinux

Run then again I get "HaRET: Booting Linux ... " (left this for 5 minutes no joy)

What am I missing?