yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
Oh, nice! Hopefully we'll see some more progress soon. Keep us updated!
[Touch Diamond, MDA Compact IV ROM Development] TripleQ:
Yeah I also notificed that...

I just compiled it with the latest CVS source..

For people who are interested..see attachment for that version of haret.
[Touch Diamond, MDA Compact IV ROM Development] -Mr. X-:
tried it for giggles as i am really interested in android.

with your haret, it doesnt even attempt to load i get "Please se start of ram (RAMADDR)"

then it errors out when it opens
[Touch Diamond, MDA Compact IV ROM Development] TripleQ:
Hmm thats strange..

I just worked here..

These are the release changes for this version.
[Touch Diamond, MDA Compact IV ROM Development] -Mr. X-:
Ill try again

maybe it was a fluke

Edit. i got it working. still locks up on "Booting Linkux..."
[Touch Diamond, MDA Compact IV ROM Development] Howell:
Tried with Android092408 and latest Haret (given a few posts before by TripleQ) and the result is the same...

Here is haretlog.txt :
[Touch Diamond, MDA Compact IV ROM Development] TripleQ:
I see some differents in this new version I compiled...

The post above this one was also made by the new 0.5.2_TripleQ version

and his haretlog says:

Welcome, this is HaRET 0.5.2_TripleQ running on WindowsCE v5.2

Minimal virtual address: 00010000, maximal virtual address: 7FFFFFFF

Detected machine Generic MSM7xxxA/MSM7xxxA (Plat='PocketPC' OEM='HTC Touch Diamond P3700')

and I have a Touch pro (rapheal)

and it says

Welcome, this is HaRET 0.5.2_TripleQ running on WindowsCE v5.2

Minimal virtual address: 00010000, maximal virtual address: 7FFFFFFF

Detected machine Raphael/MSM7xxxA (Plat='PocketPC' OEM='HTC Touch Pro T7272')

So this new version is only for the touch pro?

But is also freeze the phone when booting linux...
[Touch Diamond, MDA Compact IV ROM Development] kState:
i look in source and diamond is not in machine list, but some changes maybe help on diamond too, i don't know, anyway Diamond&TouchPro still have some problem as say some people in this tread, mmu ? fb ?
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
Will we be needing HaReT for the android that will probably be 'ripped' from the T-mobile G1 / HTC Dream?
[Touch Diamond, MDA Compact IV ROM Development] cr2:
It's only the name that is registered. diamond and raphael are

mostly identical in hardware, so wait a bit for the raphael zImage.

There are 3 LCD panels used by HTC on these devices (toppoly, hitachi and

sharp), and the framebuffer driver needs to detect them and initialize properly.

It seems that current raphael phones use hitachi LCD, so it'll be the first supported by linux. Unless you'll do it faster for other panels :)
[Touch Diamond, MDA Compact IV ROM Development] cr2:
G1 will boot directly from NAND flash, and will not need haret.

Don't forget that G1 has a different LCD, so you can't just use G1 zImage

for diamond/raphael. Let's hope that G1 will use the same TI1251 wifi chipset.
[Touch Diamond, MDA Compact IV ROM Development] edwinzhang:
Any progress now?
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
Nothing new yet?
[Touch Diamond, MDA Compact IV ROM Development] nummer20:
Be patient.
[Touch Diamond, MDA Compact IV ROM Development] ballex:
I'm following this thread intensive right now. To me it's very exciting if it will be able to run android on the device. You go guys!
[Touch Diamond, MDA Compact IV ROM Development] Dits_s:
Good luck to everyone working on this! Cant wait for the results :D
[Touch Diamond, MDA Compact IV ROM Development] Riel:
Well, please cut it out making posts like 'nothing new yet'. I also want to know, and I see a new post every time beeing just SPAM.

I think we will know it when something happens in this area, please stop ASKING for progress, sjeez.
[Touch Diamond, MDA Compact IV ROM Development] cielorosso:
what device did you test it on...? I tested it on my RAPH100, and I can't get the navipad to work in this new build (worked in the previous)!
[Touch Diamond, MDA Compact IV ROM Development] Gautje:
Could be well possible. I tested this build on my DIAM100. Please note that this is the last build, that has nog been published @ connect-utb.com yet. I don't know how far raph builds are similar to diam builds.
[Touch Diamond, MDA Compact IV ROM Development] reasons:
Testing on the latest build on my raph800. It gets stuck loading android, never making it to the android screen.
[Touch Diamond, MDA Compact IV ROM Development] adil786uk:
Starting andriod while plugged into USB seems to have broken andriod, going to try copy folder over again. When in the andriod GUI it just keeps saying "andriod.com. has encountered an error. Force Close".

NM: Fixed by re-copying folder.
[Touch Diamond, MDA Compact IV ROM Development] maejrep:
Well, it's been about 100 pages, but here's an update on what I've been working on, that is not yet in git (mostly for RAPH800, but some things affect other models too):

* Charger support - Switches between battery, AC (high-current), and USB (low-current), based on what is plugged in

* Preliminary battery support for raph800, and probably other msm7500 devices. Tried the capacity formula from htc-vogue branch, and it does not seem to work, so will need to find out what the correct formula should be

* SMD_DS support. This is the AT-cmd channel, which is not detected like all the other SMD channels on msm7500 (works fine on 7200/RAPH100, etc). I get regular signal quality status updates, and SMS notifications. Have not tried using EVDO/data yet.

* A lot of new clocks added to the API, with cr2's help. This affects hardware only (no, I'm talking about a new clock you can put on your snazzy android desktop...), but should be fundamental to getting new hardware like bluetooth working

* With a nudge in the right direction from orux, I've fixed up the board-htcraphael-panel file to add support for the Epson S1D13774 MDDI controller (the LCD panel). There's still something not quite right with it, as the screen appears shifted about 20 pixels to the left (left edge of screen shows up on the right side), but we are now able to go from a complete controller reset to almost what we have in CE/SPL (and Epson has docs!), so that's promising. RGB444/565 discrepancy is still there, which makes me think that either I haven't found the 565 mode yet, or there's something else wrong with msm_fb.

Will work on cleaning up the patches and get them into git in the next week.
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
The first boot takes longer because it has to build the dalvik-cache for the frameworks and app packages. Not more than between 1 and 2 minutes though. Going from the console to the 'glowing android screen' takes a bit longer (like 20 secs in stead of 6) and the glowing android screen stays up considerably longer than on subsequent boots. If you don't get to the glowing androids within 30 seconds or to the home screen within 3 minutes on 1st boot, its not going to happen. No idea what wrong with your particular config.

Ok, so that means that the leds driver we have now works only for Raphs, not Diams (at all), and that the navi touch chip is on the same i2c ID but is data-compatible only for the ring, not for the left and right touch areas. (This is weird. It would make more sense that either everythig works or nothing, butnot just the wheel. Are you sure it always does left or right, never home / send / back / end, no matter where you push?)

The term 'build' is used very loosely. Unless you know from which commit the kernel was actually built (like when you built it yourself), there is no telling what you run. Latest git has a driver for the navi pad that is functional (tho not perfect) for raph100 and afaik also raph800.

What most likely 'breaks' (corrupts) it, is that the file systems never get cleanly unmounted when you reset out of android. (Neither the vfat fs you mount in the 1st place nor the image file you loop-mount from that.) It is probably good practice to go through the power down sequence (hold end button more than 1 second), then count to 5 (or 10 if you count fast) before you stick the stylus in the reset hole.

I don't believe there is something wrong in msm_fb. I still think that 'somehow' :rolleyes: the dma2 in mpd_dma_to-mddi() shifts bits incorrectly. (or is that 'not found the 565 mode yet' ?) BTW: Do you have any thoughts on the navi working a little bit but mostly not on the Diamonds (other than that it is weird ;) )? As for the 'ghost behavior' of the navi pad, I did some experiments like keep reading i2c data until it returns nothing (or gives an error) but that never happens so it hangs, also I tried reading 18 bytes in stead of 19 (which I think I should anyway) but that didn't fix it either. I guess there is some bit that indicates I should ignore the rest and consider it not touched.

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] maejrep:
I don't know what mdp_dma_to_mddi() is .. Haven't looked that far into it (though I've been up to my elbows in disptools.dll asm the past couple days). The incorrect bit shifting shouldn't be a problem because it should be doing the same operations on raph800 that it's doing on raph100. I don't want to do the rgb444-to-565 conversion in the driver, as I've heard blackstone is currently doing. I'd rather just figure out how to get it into the correct 565 mode and have it display things correctly :)

Maybe if you get a chance to look at the documentation, you can point out something that would be useful? :) You probably have a much better grasp of low-level display devices than I do.

http://vdc.epson.com/index.php?option=com_docman&task=cat_view&gid=279&Itemid=40 -> S1D13774B02B Spec Rev 1.5 is a zipped PDF.

Would need to have the device, or have someone do some mmutrace analysis from wince to have any idea. Might also be worth using i2cdump (without the navi driver compiled in, and with i2c-dev support, so you have /dev/i2c* nodes) to see if touching at the same spot generates the same numbers you are expecting. I have i2c-tools compiled for ARM if you need it.

There might also be something useful to be learned from the diamond version of htcnavi.dll, if it is indeed different. If it's different it should be as simple as detecting the PSOC version at run-time to change its behavior. I have local modifications to your navi driver for grabbing the version (doesn't do any checking, just stores it in a property)

I believe it should be 18 bytes from data address 0x1 (instead of 19 bytes from data address 0 or 1). Looks like your code is using data address 1, but I2C_MSG_LEN is 19, and it should be 18, if you want to mimic wince behavior. The strange thing though, is that there should be no reason to continue reading beyond byte 0xd -- because everything after that will always be the same. E.g., 0xe - 0x10 (from your buffer) or reading 3 bytes from data address 0xf, is the PSOC version. For you that's { 1, 2, 0x36 }, but for me, it's { 0x82, 0, 0x20 }. There's no reason to grab that on every poll. This is a parallel data interface, which is different from the ksc interface, where the controller chip is actually forcing you to clean the buffer first before the IRQ can be reactivated.

As for detecting that you're not touching it anymore, I believe bytes 0-3 will be { 55, aa, 55, aa } when it's not being touched.
[Touch Diamond, MDA Compact IV ROM Development] c4software:
Hi,

Well sorry guys for the late response i don't have my computer right now.So like say J0b0 one the current 2.6.27 build only the right scroll works, and the led of navipad don't works when i touch the scroll or sensitive surface.

If anyone want to try the newest build on diam (We have to understand the button on the bottom of the diam don't works normally) i can upload it tonight.

J0b0 : To fix the problem the only way its to listen the i2c chip when we touch the surface ? if you explain to me the method i can try it tonight or tomorow.
[Touch Diamond, MDA Compact IV ROM Development] Vizzimo:
Well, eh.. yeah! I'd really like to try the newest DIAM-version! (So, I'd be more than glad :p)

Cheers and keep up the good work!
[Touch Diamond, MDA Compact IV ROM Development] Adante:
Hi there, i have a question. Is it possible to link the right softkey on the Home tab to the menu that you get when you hold the Endkey?

If so please tell me how it can be done. First of all how what registery i need to edit to chance this linking, and second to what i actually got to link.
[Touch Diamond, MDA Compact IV ROM Development] c4software:
Okay i will upload it. i compil the lastest 2.6.27 kernel on git, navipad seems okay.
[Touch Diamond, MDA Compact IV ROM Development] rmahmoodi:
Can anyone actually post the sources used and maybe a list of what files were modified or added? I'm just interested in learning how this whole process works, and I understand you can't take the time to write up a huge tutorial, but I'd like to be able to compare files and directories to see where it is you genius' are making these changes.

Hope it's not asking for too much.

Thanks!
[Touch Diamond, MDA Compact IV ROM Development] c4software:
Its the lastest git build (2.6.27 Kernel).

Lastest Android for Diamond (Working on My Diam100)

Screen :

- Touchscreen Works.

Buttons :

- Navi Weel works

- Home button show the option Menu

- back go back.

- Hang up button Go To home, long press ask to shutdown Android)

- Get call button seem snon working.

Call :

- Make Call Works

- Get Call Seems non working (on my device)
[Touch Diamond, MDA Compact IV ROM Development] setix:
just download the newest build, will post back with how it runs on a diam500
[Touch Diamond, MDA Compact IV ROM Development] setix:
on my sprint diam500, the color is still messed up, and the touch screen is reversed( you have to click at the top of the screen to touch a button on the bottom, vice versa)

it is more stable and faster,

still no network connection to sprint.

color seems to be correct on pac man game
[Touch Diamond, MDA Compact IV ROM Development] Gautje:
Lately I posted that sending/receiving sms works fine, Then I posted it didn't. To make it a little more clear:

It is possible to send messages that contain <= 160 digits. When it passes this, only the first message gets sent, and you will get an error that the message could not be sent.
[Touch Diamond, MDA Compact IV ROM Development] setix:
i got the screen calibrated on my diam500

edit the default.txt's calibraition with the raph800's settings, and it will have a near perfect calibration on the diamond

here is the settings

msmts_calib=0x81.0x393.0x358.0x7D
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Great work! Will host it on Connect-utb.com within an hour or two!

EDIT: Its up!
[Touch Diamond, MDA Compact IV ROM Development] adil786uk:
Thanks! Willl try it now.
[Touch Diamond, MDA Compact IV ROM Development] mak213:
neither calling function work on my diam100 :( just letting ya know
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
You mean the audio doesnt work or that you dont recieve the notifications at all?
[Touch Diamond, MDA Compact IV ROM Development] adil786uk:
-Scroll Wheel Now Working

-I can access internal storage now, but file browser crashes when opening any file.

-The circle light constantly lights up.

-I can make calls, but can't hear anything.
[Touch Diamond, MDA Compact IV ROM Development] Gautje:
@Untouchable;

Don't know if you need it, but I could host all Diamond/raph builds on my site, as a mirror. If interested/needed, just send me an email and I'll provide you with an ftp account to upload them :-)

My site is located at www.gautam.nl. To test, a 10mb.bin, and 50mb.bin. Please don't download these for fun. Only for test purposes. :)
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Thanks for the offer, but I think Il be fine for the moment. Easier to handle one source rather than two. But again, thank you..
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
There are no soft keys and there is no registry.

55 aa 55 aa sounds a lot like clock run-in, but I shall investigate and report back. I do read 18 bytes, not 19, but that is not in git yet. I want to have it working first. (And yes, reading 14 bytes is probably enough..)

I downloaded the epson pdf but haven't had a chance to read it yet.

You need to interrogate the i2c chip to tell whether and if so where you touch the Navi. (I do that when the IRQ for gpio 94 fires..) But even if you don't touch it, I still get the IRQ, and the data from the i2c chip indicates that you do touch the Navi, even if you don't. Especially the right side of the pad. I shall look into it a bit more to see whether I can tell from the data that you didnt actually touch it. (Like maejrep suggested.) I don't have a lot of time right now as I'm away on a project at a customer's site, probably until the end of the month. (My signal strength indicator has an R for 'roaming' in it :))

Yes. This is the list of changes. Also, see the wiki for how to build a kernel from it.

If you can distinguish between 'back' and 'hang up' (and 'right', and between 'home', 'send' and 'left'), I consider that working Navi, albeit without LEDs. So things are not as weird as I feared.

The raph/diam500 may need the same calibration as the raph/diam800 then. See settings on the wiki.

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] c4software:
@J0b0: Yep navi seems working. But the button to get call seems non working. And the navi ring led doesn't flash.
[Touch Diamond, MDA Compact IV ROM Development] skero666:
I have tried the new build DIAM100, navipad lights don't work for me (but i don't know if it's because of the ROM, i flashed Claudyfa's wm 6.5 beta2), sensitive wheel works, with OI File Explorer .apk i don't have the crash issue when opening a file, buttons: home:left, up:up, Down:down, Left:left, Right:back(:confused:), back:back, end:home(default in spare parts), send:left.

Nice progress, wish you the best of luck
[Touch Diamond, MDA Compact IV ROM Development] g0ldenchild562:
is it possible to get this working on HTC Touch Pro CDMA phone?b\
[Touch Diamond, MDA Compact IV ROM Development] petay:
i tried the new version on my DAIM100.it took me 2 go's to get it too boot. seems to be working well it knows the difference between back and call end, as well as menu/call start. the navi lights arround the circle do nothing for me, but the 4 other lights are lit. i can also use the navi scroll to go up and down. Its nice to see the clock working :)

also its nice to see the screen timeout is already disabled and the end key is mapped to home already. that should stop some of the questions on here!!!
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
DIAM100 test

I've tested with both "20090222" and "20090222-ALTERNATE" on my DIAM100 - and the result is the same:

The LED's works; the four (4) LED's around the navi pad is constantly lit

The navi pad works; I can scroll trough different parts of Android

Buttons: it was a bit difficult to use right/left because of the navi function; it sometimes wanted to scroll instead. Home button = popups a menu in different situations, End button = Home button (Spare parts config), Back = Back

Yes, the date & clock works correctly

Calling my device results in a busy tone immediately; although I do believe it's Android sending the busy tone somehow, because there's a short crackling sounds in my unshielded stereo here at work ;)

The touchscreen works out beautifully (although it's a bit too "sensitive")
[Touch Diamond, MDA Compact IV ROM Development] Gautje:
- My leds do not work...

- In the filebrowser I seem not able to browse/open any file

- In for example pacman, I think the touchpad must be disabled, since playing is impossible because it moves up/down all the time... Not nice :(

- Compas crashes at starting it...

- Changing volume works, but the speaker does not :)

- My last report is still into count: http://xdaforums.com/showpost.php?p=3359096&postcount=2382

- EDIT: Where my "Internal storage", or "SD-Card" in my Diamond worked in the build I downloaded a few days ago, it does not in the 20090222 build... Strange, no?
[Touch Diamond, MDA Compact IV ROM Development] shikigamild:
With the new version now the buttons and the navi pad works properly on my DIAM210.

Thanks :)
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
DIAM210? What device is that? Operator? GSM/CDMA? And which MTYPE do you use?
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Ive done some research now and run this through quite a few testers.

The Android package c4software posted and hosted here apparantly works for some, but for several users, especially DIAM100-users have reported nit: cannot find '/system/bin/flash_image', disabling 'flash_recovery' and similar errors.

This one though, seems to work for most, if not all! Ive noticed a few differences, in default.txt for instance (set initrd root.cpiogz vs set initrd initrd.cpio.gz).
[Touch Diamond, MDA Compact IV ROM Development] aldur:
testing on DIAM300 (o2 germany) (booting with USB connection):

using this

working:

* Clock and date

* touchscreen works perfectly

* navwheel+right+left+up+down +backkey +hang up ("red button") seem to work fine

* volume up+volume down works fine

* cant see anything happen, when pressing home (go to homescreen?) and pick up ("green button"-should go to dialer?)

* sending/recieving SMS working fine

* software keyboard working

not working:

* no virtual keyboard on pin enter page

* making a phonecall (can dial)

* sound?

* LEDs

* WLAN (wasnt started under winmob)

* bluetooth (hangs on activating)

* camera (displays chessboard+ and moving grey rectangle)

* calendar (does not start)

* android filebrowser (cant change dirs)

* long press end key: power down phone pops up, but hangs when powering down

Phonestatus:

+ network

+ signalstrength

+ servicestate

+ roaming ("no roaming" displayed)?

+ runningtime and activetime

-akkustate

-telephonenumber?

-mobil networktype ("unknown")?
[Touch Diamond, MDA Compact IV ROM Development] skero666:
Tried this one too on my DIAM100, i am impressed. All the hardware keys work fine (no navipad lights though). home:menu, send:send, end:end/home, up:up,

down:down, left:left, right:right, back:back, enter:enter/select, touchweel works..somehow, only up/down movement. i can access my internal memory now :D yuppppy, still no thumbnails, dunno why..., another new thing: i can receive calls, this is the most biggest step i think, still no voice, but it's a start. i'm impressed. Congratulations!
[Touch Diamond, MDA Compact IV ROM Development] shikigamild:
Japanese Emobile S21HT.

The network is WCDMA but the phone is actually the GSM version with WCDMA support.

I'm using the default MTYPE, so I believe it is 1805

This is the official web page of the S21HT:

http://emobile.jp/products/ht/s21ht/
[Touch Diamond, MDA Compact IV ROM Development] elamodelmerol:
confirmed android-diam100-20090222.rar works just fine with my DIAM100
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
I am puzzled as to why for some DIAM100 that one works, while for others, it doesnt but the alternate do..
[Touch Diamond, MDA Compact IV ROM Development] straylight:
You're right there has to be a common denominator,

I believe Successful and unsuccessful reports should identify,

1) The model and Network they are on and

2) Whether they plugged the phone into a USB cord Prior to testing.

Ive found the presence (or lack thereof) a USB cord to greatly varies successful boots into Android.
[Touch Diamond, MDA Compact IV ROM Development] Gautje:
On mine the normal works fine. The alternate works too :)

I am in The Netherlands, using the KPN network. (Well, Hi, but they use the KPN network). My phone is a Dutch HTC Touch Diamond, said to be the DIAM100.

And I notice that when my USB is plugged in, it boots, but it takes about 7(!) minutes. Sometimes it does not boot at all. When the USB is not plugged in it works perfectly fine (4/5 times), and boots within about a minute.

Any more information needed?
[Touch Diamond, MDA Compact IV ROM Development] mrwhite84:
how can I use it without PIN code? :confused: