yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] Addicteddddd:
can someone reupload "Even Hotter news: "Mirror" issue on touch screen solved in latest linload version from Netripper." from the wiki, i will reupload it to my server but i cant download it from that site because its so slow or dead?

EDIT: im leeching it to my server and ill repost the link once it's done, eta 20min :|
[Touch Diamond, MDA Compact IV ROM Development] neilson:
But is the development the same between CDMA and GSM versions of the Diamond and Pro?
[Touch Diamond, MDA Compact IV ROM Development] NikPraskaton:
Nice tnx. I have downloaded the one from wiki but I dont see any improvements. Touchscreen isnt aligned right..
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
HaRET & initrd

Which one is this larger one of which you speak? (And where could I obtain it?)

Not having a clue what I'm doing, I changed MAX_INDEX from 6 to 8 in HaRET. (linboot.cpp:148) That makes it load and boot kernels and ramdisks where the original HaRET would complain about the image being too large.

(It fails to get past the console handover about 50% of the time.. ..it's the other 50% that counts!)

Edit: Here is the modified HaRET.

I've tried to modify an initrd following this recipe, but with my new initrd in place it would never get past the console handover. Can anyone confirm that that works and/or does anyone have any idea what I might do wrong?

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] hillsdale:
Getting better. NetRipper is narrowing it down pretty quickly. If you comment out the if statement on line 1184 of kernel/printk.c you can get it to boot almost the whole way through the calibration step. But since that statement is where it hands off the console to (I think) the graphical framebuffer, still no GUI or keyboard access.

Walking through the code now...
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Sorry it was hosted on my DSL temporarily, didn't notice the demand was that high. ;)

I changed the link on wiki, points to some webspace kindly provided by rl2000:

http://netripper.babyburner.dk/raphael/raph_20081105-01_android_v0.8_touchscreen_fix.exe
[Touch Diamond, MDA Compact IV ROM Development] yuco91:
I've tried it ! very well JOB !
[Touch Diamond, MDA Compact IV ROM Development] ftdm.mav:
nice JOB, touchscreen ok :D
[Touch Diamond, MDA Compact IV ROM Development] Toug:
Great

Great touchscreen is OK, but how do we exit from applications? (like the browser)

Is it android 0.8 or 1.0?
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Funny thing is, GSM also works (when you have entered your PIN in windows mobile). You can call and receive calls, but speaker and mic don't work ;)

(p.s. you can hangup a call by pressing 'end' on virtual keyboard as i heard, havent tried myself yet though)
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
I don't know. However, if you tap 'home' on the virtual keyboard, you go back to the desktop / home screen, so you can go 'do' another 'thing'.

Open apps stack up on the right, above dialer and contacts.

0.8

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] Htc86:
It boots and works really well at this stage...really, hats off to you guys, amazing! You're definitely making it happen...best regards and keep up the unbelievable work!
[Touch Diamond, MDA Compact IV ROM Development] Addicteddddd:
congrats on the proper kernel update :)

is there a definitive list of things you are going to try and get working in order? eg int storage etc
[Touch Diamond, MDA Compact IV ROM Development] komteks:
So the latest build work for Touch Pro on CDMA/Sprint?
[Touch Diamond, MDA Compact IV ROM Development] techtim:
Not yet, the latest testing zImage will boot (yay!) but you can't do anything because it seems like it has no network support, no cdma, no hardware keyboard and no onscreen keyboard.
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
That latest zImage on my open dir is higly experimental - it enables druidu's framebuffer console all the way to shell. Normally there's a handover to the msm_fb driver, but it seems it doesn't get init'ed. So for now it seems it's "just" the msm_fb that is giving problems.
[Touch Diamond, MDA Compact IV ROM Development] mcage:
Openmoko posted their port of Android for their Freerunner phones (no keyboard either from the specs). Maybe parts of this port can be reused?

Link: http://wiki.openmoko.org/wiki/User:Seanmcneil3
[Touch Diamond, MDA Compact IV ROM Development] Bandit13:
You can exit from applications by insert and pull out the stylus ;)

Sebastien
[Touch Diamond, MDA Compact IV ROM Development] aldur:
though i'am not a developer i have to post sth in this thread to:

i'd like to follow the development(status) of android in this thread... because there a posted a lot of questions and answers NOT regarding the development of android, i would propose to split this thread in

an NEW development thread and leave this one for questions etc...

(don't know if possible with forumsoftware: only grant developers write access to the new thread)
[Touch Diamond, MDA Compact IV ROM Development] Riel:
But teddyenn isn't ;)
[Touch Diamond, MDA Compact IV ROM Development] teddyen66:
ups, sorry :-)

Yeah now mine says the same: Found machine Generic ARM v6
[Touch Diamond, MDA Compact IV ROM Development] teddyen66:
I just tried the Vouge version and it got further.

It stops at: Go Go Go

And partly blacks screen.
[Touch Diamond, MDA Compact IV ROM Development] ihatethis:
Ok, here is my log with HaRET pre-0.5.2-20080726f

It detects Generic ARM v6, freezes on booting linux and log shows Go Go Go...

Thanks a lot to marbalon for his help with that :D
[Touch Diamond, MDA Compact IV ROM Development] Araldwenn:
I'm very interested in this post, as it would be syply great to make Android works on Diamond...

Just one question (i'm not an expert in PDA...)

As Android, if i'v understood erverything, is based on a linux kernel, is it the same as on home computer ? I mean, does the file system has to be changed in order to make it work ?
[Touch Diamond, MDA Compact IV ROM Development] espenfjo:
Ok, a few basic questions from me.

I gather that you need hardSPL for this to work?

And it is safe to flash these ROMs, i can just flash again with one of the cooked ROMs on this site to get my device "normal" again?
[Touch Diamond, MDA Compact IV ROM Development] Kisja:
Hi,

As I understand this, Android/Linux IS NOT A ROM. You copy the Rootfs,Kernel and Haret to the Storage and run it. No flashing at all. Haret unloads Windows and starts Linux. The internal storage is mounted under Linux as a normal partition. After a SoftReset it returns to WM automatically. So no flashing and no formatting with different filesystem.

correct me if I'm wrong. On REAL Android devices (shipped with android and not with windows) it will be something like a ROM.
[Touch Diamond, MDA Compact IV ROM Development] ihatethis:
Good night, something new about this?

I would like to help patching haret for running it on Diamond

I have cegcc installed on my linux and compiled haret, tried it and it runs well, so marbalon, I can help you if you want compiling haret and trying the changes you want to do. By the way, I'm programmer but never code nothing for handled devices, but maybe I can help you patching it if you guide me a little where to start, I have been viewing code under src/mach, I will read something about haret and how it runs if I have time tomorrow

PD. sorry for my poor english!
[Touch Diamond, MDA Compact IV ROM Development] ihatethis:
Hi again, which machine it have to detect? I did a small hack on haret to force machine without autodetection

There is no Generic MSM7200 machine so I tried with Generic MSM7500 machine and Kaiser (MSM7200) but I got the same result as with Generic ARM v6

log shows this machines and architectures:

Looking at machine Alpine
Looking at machine Apache
Looking at machine AximX50
Looking at machine AximX5
Looking at machine Beetles
Looking at machine Blueangel
Looking at machine Himalaya
Looking at machine Magician
Looking at machine Universal
Looking at machine H1910
Looking at machine H1940
Looking at machine H2200
Looking at machine H3600b
Looking at machine H3700
Looking at machine H3800
Looking at machine H3900
Looking at machine H4000
Looking at machine H4300
Looking at machine H5000
Looking at machine H6340
Looking at machine HX2000
Looking at machine HX4700
Looking at machine Sable
Looking at machine Wizard
Looking at machine Hermes
Looking at machine Trinity
Looking at machine Athena
Looking at machine G500
Looking at machine Artemis
Looking at machine Herald
Looking at machine Prophet
Looking at machine RX3000
Looking at machine Treo700wx
Looking at machine e310
Looking at machine e740
Looking at machine Acer_n30
Looking at machine Mio_P550
Looking at machine Kaiser
Looking at machine Loox5xx
Looking at machine Loox400
Looking at machine MioA701
Looking at machine Jornada820
Looking at machine H3100
Looking at machine H3600a
Looking at machine Tornado
Looking at machine Libra
Looking at machine Generic Intel PXA27x
Looking at machine Generic Intel PXA
Looking at machine Generic Intel StrongArm
Looking at machine Generic TI OMAP
Looking at machine Generic TI OMAP15xx
Looking at machine Generic Samsung s3c24xx
Looking at machine Generic MSM7500
Looking at machine Generic Atlas
Looking at machine Generic ARM 920t
Looking at machine Generic ARM 926
Looking at machine Generic ARM v6
Looking at arch Generic Intel PXA27x
Looking at arch Generic Intel PXA
Looking at arch Generic Intel StrongArm
Looking at arch Generic TI OMAP
Looking at arch Generic TI OMAP15xx
Looking at arch Generic Samsung s3c24xx
Looking at arch Generic MSM7500
Looking at arch Generic Atlas
Looking at arch Generic ARM 920t
Looking at arch Generic ARM 926
Looking at arch Generic ARM v6
[Touch Diamond, MDA Compact IV ROM Development] sensorama:
This link below should supposedly contain some drivers for MSM7201...

I dont know what to make of it but i hope you guys can sort some thing out.

http://git.android.com/?p=linux-msm.git;a=tree;f=arch/arm/mach-msm
[Touch Diamond, MDA Compact IV ROM Development] espenfjo:
Ok, since this will preserve WM on the main storage one should simply add hell loads of debuging information in the kernel and make it write to a file (ok.. I know that writing to files directly from the kernel isnt that easy, but somehow it should be doable). It might just be the framebuffer not working properly.
[Touch Diamond, MDA Compact IV ROM Development] ihatethis:
Hi, maybe yes, I had been reading other threads about android & kaiser & polaris and some people has the same problem and it was the framebuffer driver.

I'm at work now, this weekend i will try to compile the latest snapshot for android msm kernel and will make more test

Cheers
[Touch Diamond, MDA Compact IV ROM Development] ihatethis:
I'm downloading now kernel from git.android.com, I really hope we'll be able to run it in diamond soon, at google io 08 in May google presented the latest version of android under device with MSM7201A and I think (and hope) they really release all source code of kernel and use the same kernel for it

I would like to help with this task but I need help too! I'm totally noob developing for handled devices but I like to collaborate with the community
[Touch Diamond, MDA Compact IV ROM Development] sensorama:
Well, report any success or failures.

Good luck.
[Touch Diamond, MDA Compact IV ROM Development] agjell:
Any progress?

BTW I read in this article that HTC will be shipping the Diamond with Android by Q4 this year:

http://phonereport.info/2008/06/15/htc-google-android-q4-windows-mobile-7-q1-2009/

Old news maybe?

Edit: Found a newer article that confirms it:

http://www.digitimes.com/news/a20080801PD216.html
[Touch Diamond, MDA Compact IV ROM Development] Atse:
Neither of those articles confirm what you are saying. They both confirm that HTC is going to ship a device with Android, but nothing is said about this device being the Diamond. I would like that though...
[Touch Diamond, MDA Compact IV ROM Development] agjell:
Damn, I must have been too excited... Sorry to be off topic then, not intended.
[Touch Diamond, MDA Compact IV ROM Development] sensorama:
Any progress on this subject?
[Touch Diamond, MDA Compact IV ROM Development] espenfjo:
I have now tried with various kernels (self compiled and from the kaiser), and i get the same results as everyone else here..

For me it seems like Haret isnt able to boot the linux at all, so maybe its the memory settings that is wrong? RAMSIZE RAMADDR?

Anyways, ill start looking into the kernel itself to see if i can see anything obvious there (cant say that im neither a kernel expert, nor any good in C).
[Touch Diamond, MDA Compact IV ROM Development] kState:
hi,

i too tested kernel from kaiser, from this thread and selfcompiled kernel from htc/kaiser git.. and result is same as have many people in this thread...

log end with Go Go Go... (btw: GoGoGo="now i switch to linux")

is here anyone who know that value in haret conf is right for diamond ? model, ram address etc... ?

kState
[Touch Diamond, MDA Compact IV ROM Development] skiwithpete:
G1 has been rooted.

http://mobile.slashdot.org/mobile/08/11/05/1436224.shtml

This could provide useful.

P

edit// should this be added to the wiki?
[Touch Diamond, MDA Compact IV ROM Development] Riel:
Or tap 'end' on virtual keyboard :)
[Touch Diamond, MDA Compact IV ROM Development] Toug:
Hi

How do you make a call, I know how to dial the number but after I do not succeed to launch the call. Where is the "green key".

My work is to test S60 Symbian builds. I think it could be usefull to test android bin you can develop. Here is an extract of the basic test I do.

I will these test as soon as we can do a real call.
[Touch Diamond, MDA Compact IV ROM Development] sazinas:
There is a Development thread, you just have to find it:)
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
Thanks to NetRipper's zImage, which logs more visibly (the one from yesterday), I found out that the kernel was complaining about the initrd not having the correct cpio magic number. It turned out that adding '-H newc' to the cpio arguments did the trick.

Even with a good initrd, the kernel will 'sometimes' (:confused:) complain about junk in the cpio/gz. Could this be due to Windows interfering with HaRET mapping virtual memory to physical memory? Would it make sense to disable file system cacheing in Windows?

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
The fact that it is complaining about the initrd is not the problem at hand. When it switches to initrd, it should've already initialized the msm_fb, which it doesn't.

Disabling file system caching won't do a thing. And so far I haven't noticed HaRET doing anything wrong regarding memory placement. However, if you want to be sure, you can add a line to default.txt (before bootlinux command) to make it do a CRC check on the kernel and initrd:

set KERNELCRC 1

It'll perform a CRC before and after kernel/initrd replacement and report back if there are problems.
[Touch Diamond, MDA Compact IV ROM Development] jamesd256:
I need to know where it is so I can go and ask when it will be finished
[Touch Diamond, MDA Compact IV ROM Development] beboxed:
I think that the developers have other things to do instead of answering this continues ongoing flow of questions like 'when will the port be finished'.

If you would have read the thread you'd have seen that such messages pop up every 5mins or so and people start cursing at the posters. So please son't do that again, people might go beserk....
[Touch Diamond, MDA Compact IV ROM Development] jamesd256:
I didn't expect anyone to fall for it. Lesson learned :|
[Touch Diamond, MDA Compact IV ROM Development] sazinas:
are we back on the air?
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
So it seems. Great! I've once again tried to init Android 1.0, but yeah... HaRET still says "No, no, no! Too big image". Just hope everytime it'll work ;P Gn!
[Touch Diamond, MDA Compact IV ROM Development] sazinas:
A bit quiet tonite... Everyone working on android then?
[Touch Diamond, MDA Compact IV ROM Development] koboldx:
What Image do you use? (or: how to translate system.img, ramdisk.img, userdata.img into an "android.bin"?)

I've changed the code of haret.exe...at least it says GoGoGo instead if No, but it still doesent work.

cheers

Edit: Before someone askes; I just changed the MAX_PAGES.
[Touch Diamond, MDA Compact IV ROM Development] grojulius:
Perhaps there's another method, but here's the one I've used to have an Android.bin :

- make your 3 .img files with the android source

- start the android emulator with these 3 files, an SDCard and a kernel. You must have a writeable area to get back data. So you should create an SDcard with the utility privided in the same directory as the emulator.

- With the "adb push" command, send a busybox binary to the emulator and install it

- Once you're in the Android shell, tar (and don't tar + gz) all directories, and get back with "adb pull" or by mounting the sdcard file (with -o loop option of course)

- Now you should have retrived all the directories. You just have to create a gzipped cpio of the root file system that you call .... Android.bin :D
[Touch Diamond, MDA Compact IV ROM Development] koboldx:
HAH! I will definately try that, thank you. (I had _many_ different tries ;)

Would you be willing to upload the file somewhere? (I am at work at the moment, cannot build it here)

Cheers
[Touch Diamond, MDA Compact IV ROM Development] Sigilium:
0.8 works great here on Touch Pro :)

I have just noticed that if I pull out the HW keyboard on the main screan, then on the bottom of the main screen there pops up a screeen wide button named "Change desktop wallpaper" (or something similar).

If I pull out the keyboard inside an application it seems to react as if down arrow was pressed.

(I am looking forward to see the 1.0 working and ready for daily use on Raphael. :D)
[Touch Diamond, MDA Compact IV ROM Development] elganso:
A question to ROM developers: Is there some known technical problem that cold screw that project in the next few months? I know it's early to say it, but I've readed that full thread as well as the wiki page, and I'm just asking for an opinion. For example, maybe there's some point in android hardware that's not documented at all, and the full proyect depends on it, or maybe Google has already stated they will try to cancel that kind of projects.

The point is I'm need a new phone, and I am in doubt of buying a second hand G1 (I live in Spain, so I can't buy it "oficially") or a new Diamond, and hold with Windows till Android ROM is operational, while trying to help with the development. I prefer the "Diamond style" of phones, so I'm tempted to take the second choice, but I need a little help with the decision :rolleyes:

Thanks in advance!
[Touch Diamond, MDA Compact IV ROM Development] jameselder232:
Well Android is already running on the phone so theres nothing that might stop it running, these obstacles have already been overcome. However not all the hardware of the phone is operational with Android as the drivers need to be re-written for Android and the Diamond hardware, so it is possible that say for example the camera may never work, however in my experience this is usually not the case, as someone somewhere works out a way of getting the drivers working. As with Android 1.0 this isn't currently working due to a technical problem however the reason for it not working is know and they are working hard to overcome this also. It is likely that Google will release new version which we will have to re-hack in order to run, however there will eventually become a point when so much is known about Anroid that everytime there is a new release, shortly afterwards there will be a diamong compatible release. Whats your biggest reason for wanting to run Android at the moment though? It is quite new and therefore theres not many programs designed for it or many tweaks you can apply to it, however there soon will be and by this time there should be diamond compatible versions.
[Touch Diamond, MDA Compact IV ROM Development] elganso:
Well, I want to use Android for a few reasons: I use Google Apps in my domain, so I use just use the mail, calendar and chat from Google; I work as a Linux administrator, and so I'd like to use it in mobile device too; and I like the look and feel of the OS as far as I've seen.

I could say that the actual version of Android is just the mininum of what I'd ask a OS for, while, with Windows Mobile, I should need some tweaks and apps.

Just one more question: if all the hardware problems where fixed, what about the Google accound activation? I've read unlocked G1 have problems with that, that affect both Gmail and Android Market access, so it may be possible that "unofficial" phones could be blocked in Google servers.
[Touch Diamond, MDA Compact IV ROM Development] skiwithpete:
It is open source. What is not open source will be replaced.
[Touch Diamond, MDA Compact IV ROM Development] livefastdiefun87:
WooHoo works prefectly (as well as it can ATM) much less trouble than the thread over on the kaiser forum :D

For all of the people saying when will the WiFi be running, when will the radio be running etc.

As this is all open source it wont be long until a dev compiles the drivers and gets it all working. When we finally find a way to intergrate it from boot then we will be singing loud and proud. HTC diamond with Android!!!
[Touch Diamond, MDA Compact IV ROM Development] Sigilium:
I have compiled the 1.0 kernel, used intrd from http://www.stdev.org/2008/11/01/GettingStartedWithAndroidOnTheHTCDiamond.aspx

and got into the "not signed" trouble: http://xdaforums.com/showthread.php?p=2880353#post2880353 :(

I do not want to hard reset! Is there another option?
[Touch Diamond, MDA Compact IV ROM Development] thevery:
I had to hard-reset, nothing helped me :(
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
1. no, i'm almost certain you have to hard-reset, too bad.

2. Can you please upload dat 1.0 image?:D
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Kernel in combination with the initrd may be the reason he needs to hard-reset, you want it too? ;)

A small theory, not sure if it's true: msm_defconfig (used for original G1 kernel) by default has MTD enabled (needed for NAND). The android 1.0 default initrd tries to mount the NAND, which is the operation that almost bricked druidu's device. It may as well be the cause for this strange behaviour.

So be warned. It's not experimental for nothing. :)
[Touch Diamond, MDA Compact IV ROM Development] dzign-it:
Hey, iv been reading this thread for a few weeks now... progress is looking good but untill android 1.0 is bootable in some fashion, then it seems a waste of time.

Why are you guys wokring on 0.8? i understand its one step at a time stuff but even netripper said theres a big step to getting 1.0 working at all on these devices.

So...surley its best to put all effort into getting 1.0 working/booting/whatever coz yeah your gunna get 0.8 all sorted and working...then immediatly loadsa people are going to want 1.0.

So, from what i can see your still working with 0.8, why not put all efforts into 1.0? Or is that whats going on? If i missed something, then fair fo :-)

Also - How come we have to build a version purley for the diamond - is there not a device similar that we can just port across, or maybe work together on a multi device version?

Some of my comments and questions might sound negative, but there not - just questions for us other people who read the thread most days and dont really know whats going on and why lol.

Cheers!