yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Android v1.0 is impossible without SD card working, it's too large to pass in an initrd. You would've know if you would've read the wiki page. ;) Showing v0.8 just adds to the 'cool' factor for me.

Devices differ too much on a lower level. They could all end up in the same kernel source tree, but you'd still need to compile different versions for different devices. And by the way, we are actually already combining devices. The Diamond and the Raphael are already working on a single kernel.
[Touch Diamond, MDA Compact IV ROM Development] Toug:
Haret Limitation

From what I read, there is a Haret limitation. Haret is used to boot Linux from Windows. This limitation is on the size of the bin. Android 1.0 is too big for Haret. I think this is why people is curently working with 0.8.

Drivers should be compatible.
[Touch Diamond, MDA Compact IV ROM Development] dzign-it:
So, android 1.0 will never work on diamond? If its too big, then its too big lol. I have read that your trying to tap into the internal storage of the diamond and/or the sd or rapheal, once this is done, i take it 1.0 should be loadable?

Also, yeah showing 0.8 is certainly cool, but alot of people here are looking for a fully functional replacement to windows, and, maybe (just maybe) people can see some light at the end of the tunnel with what you guys are doing, so, less cool and more functional lolol.

You should gather some heavy linux gurus and get to work, set up a website (androidonwindows.com ?) lol, take donations, and blast android 1.0 onto the diamond and work with others on multiple devices.

Im sooo tempted to buy a G1 just to have the android interface - but the phones so damn ugly lol, if theres hope at all to have it on the sexy diamond....im in, and waiting :)

again, in no way am i been negative, i fully support you guys and il be one of the first to install anything you guys come up with :)
[Touch Diamond, MDA Compact IV ROM Development] jamesd256:
Getting the gui up is one thing, but getting the hardware to function fully is in a different ball park.

It's very encouraging what people have accomplished so far, and as for your comments about hardcore linux gurus, it's pretty clear that some of the people here are fairly able with linux themselves to have gotten this far.

However, getting everything working will depend on more than just skill. We need other devices to be supported which share hardware with ours, so we can patch in the drivers. Otherwise reverse engineering will be required, which is VERY hard and VERY slow compared to what's been done.

Kudos to the guys so far, and good luck. To everyone who expects to be able to finish with WM in the near future, good luck, and don't hold your breath.
[Touch Diamond, MDA Compact IV ROM Development] Riel:
Blahblah to work blahblah can't wait.

Will that never stop here?
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
There is a HaRET limitation yes, but it's not a hard-coded limitation. The limit is there for a reason. I've looked briefly through the haret code and it just manages with what it can. I think it's pretty neat it can pass an initrd of 20MB. It's pretty unusual you know ;)

You really should read wiki or this thread. Diamond has an Internal Storage, which, at first sight, seems similar to the SD card.
[Touch Diamond, MDA Compact IV ROM Development] skiwithpete:
Am just curious, and its not on the wiki...

are the changes being fed upstream?

Does google / android have a system for sending things upstream? (I know they said they don't plan to support our phone, but if its just a bit of code to be added are they willing to do it?)

If not: Is there a group that is going to deal with Android and going to try to fork it so that the changes can flow up?

Are there other interfaces that might replace Android if we can get the linux base code working?

Maybe I should just ask if Android is a shell, or if its more...
[Touch Diamond, MDA Compact IV ROM Development] courtlandre:
I don't think that is true... On my vogue Android boots 1.0 and works very well. Data, phone calls, sms all work fine. You can even install some apps.

I thought that the reason we are working with .8 is because we dotn have internal storage working and the files are just too big to fit into memory.
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
I don't think the proper solution is to slim down the image, sooner or later we will need a internal storage, so i think we better get on that instead of doing work twice... but of course, it's your decision ;)
[Touch Diamond, MDA Compact IV ROM Development] beboxed:
Aren't we all just butting our heads on this DMA problem while there is plenty of other hardware to enable?

I seems to me that very little progress is made in the last month on this DMA problem, and lots of developers are just waiting for the storage to work.

But while the storage doesn't work other people could work on for instance getting the sound devices (speaker, mic) to work properly, right?

So when the storage problem is cracked (which would really make my day) The devices would be even more usable because the other hardware support.
[Touch Diamond, MDA Compact IV ROM Development] yuco91:
HI GUYS ! any news?
[Touch Diamond, MDA Compact IV ROM Development] Addicteddddd:
Yes, totally.

Android 15.23 beta is working, go try it now, it has new features such as a 3d projector, working coffee vendor and other cool things!

Alternatively, you could just watch the thread for updates instead of asking :)
[Touch Diamond, MDA Compact IV ROM Development] asticinzano:
How could you forget to mention the flux capacitor for time travelling? :D
[Touch Diamond, MDA Compact IV ROM Development] petay:
first off i just want to say thankyou to everyone who has worked on this!! it is something i am very interested in, as i love linux, although i dont really have the skill to contribute much on the software development side (i can code in c/c++/java etc but nowhere near this level :p ) i have been playing with the emulator which runs really slow on my pc and was amazed by how fast android is on my diamond!!! hats off to you all. One thing i have noticed happening, but have not seen anyone mention, is that if i remove then insert the stylus to go back to the main screen, it sometimes comes up like a key is stuck down it keeps typing in the search box and everything go's all flickery because its trying to type in the search.

also i know feature requests are the last thing that anyone wants posting here but i thought it would be good if the keyboard could be shown/hidden with a key combination?? like back+home. this could help reduce the flickering and maybe make the keyboard more usable??
[Touch Diamond, MDA Compact IV ROM Development] skiwithpete:
Debian on the G1

Looks like a geek has ported Debian to his G1.

http://www.engadget.com/2008/11/10/debian-gets-ported-to-the-g1-makes-nice-with-android/

Sourced from Engadget.
[Touch Diamond, MDA Compact IV ROM Development] zEar:
Why not virtualize ?

VMWare has just announced support for mobile phones.

http://www.vmware.com/technology/mobile/index.html

It will be a valuable tool for cross-platform OSes !!
[Touch Diamond, MDA Compact IV ROM Development] christofur84:
reboot

anybody tried typing in reboot on the kb. i have cdma TP and cant boo
[Touch Diamond, MDA Compact IV ROM Development] NielDK:
Original G1 update

Wonder if any of you guys working on this have considered having a look at the G1 update ?

Might not be ready for this yet, but I believe it may give some answers for further steps, like how the updater works, how to install Android permanantly, and of course, how to jailbreak :)

I would post a link, but I think that is agains forum rules, however, Google can help with hacking Google (hint: signed-kila-ota-115247-prereq.TC4-RC19_RC28.zip) <- allthough it says RC28, it actually contains the RC29 update.
[Touch Diamond, MDA Compact IV ROM Development] adwinp:
There you go:

debian on android

http://www.saurik.com/id/10
[Touch Diamond, MDA Compact IV ROM Development] NielDK:
Well, this is one reason I would like the G1, if not before.

Allthough, it aint Debian on Android.

It's Debian together with Android, ON the G1 (Dream) device.
[Touch Diamond, MDA Compact IV ROM Development] jamesd256:
It's android on steroids, but if you read the article, the possibility to do this is short lived, as a patch has already been sent out to phones to fix the root jailbreak.

I'm sure they'll get there though.
[Touch Diamond, MDA Compact IV ROM Development] NikPraskaton:
Guys stick on Android for this time :)
[Touch Diamond, MDA Compact IV ROM Development] NielDK:
Already covered. Done.

http://xdaforums.com/showthread.php?t=443041

This is about Android. Not about Diamond and Android, but might be usefull, once Android is running on Diamond.
[Touch Diamond, MDA Compact IV ROM Development] mcage:
Maybe the screwed up colors as posted in the wiki are related to this:

http://androidzaurus.seesaa.net/article/105551643.html
[Touch Diamond, MDA Compact IV ROM Development] hillsdale:
I don't really think so. I've more or less got it worked out, just can't get it to work. :)

There is a function call mddi_init in drivers/video/msm/mddi.c which gets the video capabilities from the phone (supposed to be calling into a toshiba video to lcd bridge chip). The call is returning garbage on the cdma phones. I forced a few variables to get it to work at all, but I haven't overridden the color mapping variables and a few others.

There are even comments in the google code about how the chip doesn't always respond to the get capabilities call - they actually query it four times in a row and hope it bothers to respond.

So, I see two ways to get this working:

1) Figure out how to get this MDDI (qualcomm standard) info from the chip. This means

a) checking if we have the same chip in RAPH800 as RAPH100 (which I haven't been able to very easily, as the wince dmesg seems to be located somewhere different in memory from the RAPH100 as well).

b) assuming we do have the same or similar chip, figuring out why the get capabilities call isn't working (for instance, it returns widthxheight of 864x864).

or

2) Override all the variables that the chip is supposed to return, and hack them into the code. I expect this will work fine for now. We just need someone with a GSM phone to add printks in mddi_init (around line 660) for every field in the mddi_client_caps structure (defined in mddi_hw.h), and then we can hardcode them for the RAPH800. The only pain here is that they will need to be hand transcribed off the screen... :)

I think the critical variables are probably Color_Map_Size, Color_Map_RGB_Width, and RGB_Capability, but we'd probably want all of them to be sure.

Thanks!

(BTW, I'll be traveling for a few days starting tomorrow, if I don't respond thanks in advance, I'll be back next week.)
[Touch Diamond, MDA Compact IV ROM Development] flibblecx:
initrd larger then 25M

The following should cope with the large sizes, it allows me to load the 30M initrd for V1, doesn't fully work yet but you sometimes get as far as the pulsating android logo.

http://richard.flibble.cx/haret-rp.exe

It just a change of MAX_INDEX from 6 to 8 in linboot.cpp, I have no idea how stable that change is but works for me.
[Touch Diamond, MDA Compact IV ROM Development] pereira.stephen:
Is it possible to have android running on my Diamond even if I don't have access to a linux machine to build the kernel?
[Touch Diamond, MDA Compact IV ROM Development] remi.rez:
Did you read any message saying that you could run Android (1.0) on the Diamond?

No? I though so.

If you want to give a shot at Android 0.8 everything's in the wiki.

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

Don't thank me
[Touch Diamond, MDA Compact IV ROM Development] pereira.stephen:
May I ask where you saw me refer to Android 1.0? I was speaking about the current version being worked on (0.8)

I've been to the Wiki page, can I just copy that Raphael file to my Diamond and run that one?

Is it so hard to be civil when responding to posts? I was only asking a simple one line question, there was no need to insert your attitude.
[Touch Diamond, MDA Compact IV ROM Development] jamesd256:
Haret vs flashed rom

I would like to know how people envisage their use of Android if and when the community gets it working.

I personally would continue having my main rom as WM6 with the ability to boot Android over the top, at least for now.

Of course dual boot would be nice, but that's another matter.
[Touch Diamond, MDA Compact IV ROM Development] newjamie:
If you had bothered to read the wiki page instead of just going there then you would have seen this:
[Touch Diamond, MDA Compact IV ROM Development] jamesd256:
Yes. But all the usual warnings apply, at your own risk etc. Some people have reported some issues that require a hard reset to fix from doing this.

You should ask yourself if having a play with 0.8 is worth the risk, as you can't really use it for anything.
[Touch Diamond, MDA Compact IV ROM Development] pereira.stephen:
I read the wiki page earlier, but it was referring specifically to Raphael, where as I have a diamond, please if you have nothing positive to say then please refrain from your comments.
[Touch Diamond, MDA Compact IV ROM Development] pereira.stephen:
Thanks for your help, I ran the file on my diamond with the new Dutty rom and it works as it is meant to =)
[Touch Diamond, MDA Compact IV ROM Development] liamhere:
do you have any idea about android?....as this question makes me think not.

again...please read..before you ask...all the answers you need are here.
[Touch Diamond, MDA Compact IV ROM Development] pereira.stephen:
do you have any idea about courtesy?....as your response makes me think not.

Have I claimed to have an expertise in Android or Linux?

No. If I did, why on earth would I have asked a simple question? And since when does ANYONE have to be an expert on Linux or specifically Android to post on XDA Developers?

Please be civil next time.
[Touch Diamond, MDA Compact IV ROM Development] Sebienbon:
Don t bother, this guy is jumping in every second post , u ll find those type of comments in every single thread ......

Sorry for the off topic but he is getting annoying
[Touch Diamond, MDA Compact IV ROM Development] kmartburrito:
Hey man, chill! It's nothing to get so confrontational about. You'll find everywhere that there are people will take what you originally meant out of context and think you didn't do your research when you feel that you did. It's a fact of teh internetz.

You may feel he was being out of line, but I guarantee you won't help the situation by arguing the point. Just let it go, and keep lurking on the boards. This is a great community to learn, and a great sub community, if you will, for the development of Linux for our phones. People will always be around to rub you the wrong way, but don't take it to heart, just blow it off and if you know you weren't in the wrong, who cares. We certainly don't need to start a flame war in this awesome thread!
[Touch Diamond, MDA Compact IV ROM Development] elganso:
Just a link, in case it can help. It looks there's now a virtual keyboard in android market: http://androidcommunity.com/android-gets-the-first-virtual-keyboard-still-needs-some-work-20081112/

Maybe it can be hardcoded in the Diamond version of the OS.
[Touch Diamond, MDA Compact IV ROM Development] kmartburrito:
Good idea!
[Touch Diamond, MDA Compact IV ROM Development] H3PO:
to help the atmosphere a bit... if people continue asking for the features which are not yet running, you can point them to my blog - i'm trying to give short status updates and simple step-by-step descriptions. i also added a link to the raphael linux page on the android list, because some people might not think about looking into others' pages.
[Touch Diamond, MDA Compact IV ROM Development] davey33:
yeah well said mate he posts on every thread usually with negative comments:eek:
[Touch Diamond, MDA Compact IV ROM Development] kano69:
the htc G1 Android is also called the HTC Dream. search it up its there. the very first name the phone had was HTC Killah, it was meant as a threat for the Iphone.
[Touch Diamond, MDA Compact IV ROM Development] pereira.stephen:
Excellent idea :D I found your blog quite helpful, I didn't know about the "stylus out" being mapped to the back key

Quality!
[Touch Diamond, MDA Compact IV ROM Development] skiwithpete:
bump

C'mon, we need some progress!!!
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
No progress from my side. Have been really busy lately. Still need to get SD card working as first priority.
[Touch Diamond, MDA Compact IV ROM Development] dcordes:
did somebody look into raphael/diamond msm_sdcc yet? I guess it won't be much different from trout sdcc
[Touch Diamond, MDA Compact IV ROM Development] dcordes:
did somebody look into raphael/diamond msm_sdcc yet? I guess it won't be much different from trout sdcc. did you just try the trout code?
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Can't boot trout on Raphael, for some reason the screen goes white when initializing msm_fb. Can't find out why. Haven't looked into memory addressing differences yet. Booting with druidu's console doesn't work as it's only an early boot console, not a full console.
[Touch Diamond, MDA Compact IV ROM Development] maejrep:
Not sure if this is relevant, but its in the latest git code, and appears to be wrong:

x = par->update_info.left;
y = par->update_info.top;
w = par->update_info.eright - x;
h = par->update_info.ebottom - y;
#ifdef CONFIG_MACH_HTCRAPHAEL
w = 0; y = 0; w = 480; h = 640; // XXX - VERY ugly hack so we can draw in fbram
#endif

I think that w = 0 should be x = 0? fwiw, I'm trying to make some headway on a CDMA/Sprint Touch Pro. Can someone re-post hillsdale's patch on some place other than pastebin.com? Seems that site is *always* down >:( A friend of mine runs privatepaste.com, and it is much, much more stable and reliable. Would be appreciated.
[Touch Diamond, MDA Compact IV ROM Development] hillsdale:
Hi Maejrep!

I caught that as well - played with it a little, don't think it really makes a difference (though they did clearly intend for it to be x=0).

The real issue is summarized in my post #833 in this thread - the call to get the video screen information is returning trash data. One of the things that call returns is a manufacturer and device id, which is different from the gsm phone. I can't tell if it is different because they are not using the same toshiba chip, or different because the data is garbage. In any case, my hack patch simply forces initialization as if it had returned the toshiba identifier.

However, the call is also not returning all types of other info that gets used elsewhere, such as the color depth maps. Ideally, we would get the call working. Failing that, if we could get someone with a gsm phone to print out the entire structure they get back from the call, we could probably just hardcode all the fields and I bet it would work fine. Check post 833 for more detail.

I re-uploaded my initial patch to http://www.privatepaste.com/09rcsUiFNn .

Good to see someone else taking a look at this. Thanks!
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
mddi->caps

Someone just did, albeit a week late... ;)

There is no color map and RGB_Capabilities == 0x8888

(The messed up colours look like when you put BGR565 data into a BGR555 buffer.)

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] hillsdale:
Awesome - thank you!!!

Sadly, this didn't work. :(

I tried overriding my details with yours, but no go. I must say, comparing the fields, I'm really starting to think they must have changed the chip. Here are where my fields differ from yours (all in hex):

length 4a (interesting because correct, yours has 1)

Minimum_Protocol_Version = 01 vs your e0

Number_of_Alt_Displays = 02 vs your 01

Bitmap_Width = 360 vs 100

Bitmap_Height = 360 vs 280

Display_Window_Width = 0 vs 1e0

Display_Window_Height = 0 vs 280

Client_Feature_Capability_Indicators = 440000 vs 448000 (need docs!)

Maximum_Video_Frame_Rate_Capability = 40 vs 3c

Minimum_Sub_frame_Rate = 8888 vs 0

Keyboard_Data_Format = 7f vs 0

pointing_device_data_format = 7f vs 0

Mfr_Name = 4ca3 vs d263 (anyone know how to look this up?)

Year_of_Manufacture = 10

All the other fields were the same.

The fact that the length field is correct implies that the call really is returning successfully from the chip, interesting that yours doesn't include it at all.

I think I'm probably stuck for now. Next step would be to figure out how to access the wince dmesg area (seems to be in a different location from the one listed on the wiki?) and see if it mentions the hardware...

Thanks again!
[Touch Diamond, MDA Compact IV ROM Development] davey33:
awesome work guys keep it up!
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
Oops!

...in fact, too interesting to be true, so it wasnt.

I dont know how, but I had the 1st column of my dump 1 row up. This is better.

4A 00 42 00 00 00 01 00
01 00 90 01 00 01 90 01
E0 01 80 02 E0 01 80 02
00 00 00 00 00 00 88 88
00 00 00 00 00 00 00 00
00 80 44 00 3C 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 63 D2
00 00 00 00 00 00 00 00
00 00 44 55

It changes the following:

length = 0x004A (same as yours, and sizeof *caps - sizeof caps->length)

mim.prot.ver = 0x0001

bitmap width = 0x01E0

Sorry for the misinformation

-Jobo

edit: some more rambling

another thing i noticed, which is a bit off topic and of questionable use but i'll mention it anyway:

there appears to be another frame buffer 'below' the 1st one. if you plot the keyboard and the yellow dots not only on (x,y) but also on (x,y + lcd_height) you dont get so much flicker when you run the android gui, which apparently alternates between the 2. it still gets overdrawn and redraws late, but it doesnt flicker continuously anymore.
[Touch Diamond, MDA Compact IV ROM Development] meetdave:
..you guys are god among men

lol i'm so stoked for when this turns out.

keep up the good work!
[Touch Diamond, MDA Compact IV ROM Development] doena:
Hey guys,

I only wanna tell you, what great work you are doing here.

REALLY GREAT - THANKS

greets doena
[Touch Diamond, MDA Compact IV ROM Development] Marcellus_pnz:
Sorry everyone, i didn't want to interrupt the thread BUT I THINK, that anyone who desire to show his/her appreciation can do it with DONATION or in another thread, and all of the posts like "good work keep up" is just ANNOYING and ABSOLUTELY USELESS.
[Touch Diamond, MDA Compact IV ROM Development] skiwithpete:
You're right Marcellus, keep up the good work.

;)
[Touch Diamond, MDA Compact IV ROM Development] hillsdale:
No problem at all - I'm completely crosseyed trying to read the 2 point font myself. :)

I think its interesting that my device is claiming 864x864 resolution and 2 displays. Wish I'd gotten that one instead. Maybe they swapped in the hardware from the Touch HD without telling anyone... :)
[Touch Diamond, MDA Compact IV ROM Development] jamesd256:
Maybe they don't want money. I don't, I'm rich. A thanks here and there goes a long way IMHO.

I'm sorry it's so annoying for you, but try not to let it ruin your day. It will never change.

While I'm here, I'd just like to express my appreciation for all the work that has been put in. Keep it up guys.
[Touch Diamond, MDA Compact IV ROM Development] dblanchard:
Some help from Google?

I was thinking about all those Google engineers with 20% time to work on pet projects and wonder whether any of them are working on this, or even whether any Google engineers are on XDA-Devs. I searched this thread and found that skiwithpete also wondered along these lines. I think he is really on to something here and if no one at the Goog is working on it, maybe we could find some people there who could be persuaded to join the cause, or at least point us to someone who could answer some questions now and then. Same goes for HTC. There isn't any reason (aside from NDAs, etc. which I think would largely be nullified by now) we have to feel our way through the dark on our own.