yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] nuke1:
A suggestion: I think there should be two threads. One with development-ONLY, and the other with people trying to figure out how to run the latest build.
[Touch Diamond, MDA Compact IV ROM Development] gebruikershaes:
Aagreed.:)
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Best thing would be for those who cant help out with the development to wait for a fully working version to be completed instead of messing up the topic with lots of questions on how to get Android running when we cant use Android as a daily OS yet.
[Touch Diamond, MDA Compact IV ROM Development] plbelanger:
Better yet why not a seperate forum under Diamond for Android Development =)
[Touch Diamond, MDA Compact IV ROM Development] Nooblet:
Booting Issue.

Alright in no way do I understand what exactlly goes on in your coding and everything, but dont get me wrong I have the utmost respect for you guys and what your trying to do, just have a small question, and it might help out a little , who knows though. Im running on Sprint Touch Pro, or if I believe so RAPH800, and while I am able to get haret to boot up the linux kernel, it stops booting at a certain point, and Ive not been able to figure out how to go about fixing this issue. It locks up at, "[ 22.391159] trout_pwrsink_set:STUB!" ive seen the pictures of others booting up and it seems to make it past this point without even bringing up this part, also It does the same on both 0.8 and 1.0, so its not just something one kernel has and the other doesn't. Any ideas on how I could go about getting around this issue?
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
That is a good idea. A dev thread and a 'support' thread.

And link to the support thread from the topic title and from post #1.

That _would_ be the best thing, but the likelihood is somewhere between pigs flying and hell freezing over. We have more control over the structure of the site/forum than over human behavior.

1 - There is no android development.

All development is kernel development. The trick is to get android working on a device without touching android or the device. The thing that sits between the hardware and android (or any other user space app) is the kernel. Android, like other user spaces, is a way to test the kernel.

(Actually there _is_ android development, but that is not in here as it is not device specific.)

2 - Then that thread would get the same abuse that this one gets now.

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] foh1981:
I agree with you on that. I'm not fond of WM, it's not an operating that is designed for mobile phones. What I was wondering was more specifically if starting Android with haret had some downsides hardware-wise, so to speak. I got the answer further down :) Dual-booting is always nice to have, as a safety thing. I would rather be booting in to Android by default though. We'll see what the future brings :)

At some point I'm assuming the developers would want user input though... With enough eyes, all bugs are shallow (if the "eyes" know what to look for, that is :rolleyes:)

I had this problem at one time on my Diamond (DIAM100, P3700). I can't remember what I did to get past it, it was either that I just tried booting again or I tried the ActiveSync-thing that's mentioned in the Wiki. It seems to me that the problem is that it can't access the files correctly.

So my suggestion to anyone trying Android, be sure to disconnect the phone from your computer properly as to not lock the internal memory card in any way. Disconnect the phone and reconnect it in ActiveSync mode.
[Touch Diamond, MDA Compact IV ROM Development] sazinas:
In reference to the previous messages,

I was wondering if the android build on the 'wiki' page is the latest, or should I look for it somewhere else?

thx
[Touch Diamond, MDA Compact IV ROM Development] oliwan:
Can I help?

Hi,

I have a diamond and programming knowledge. Love what you've done so far. Is there anything I can do to help move this along?

I'm sick of WM. It's a massive, stinking pile of...

Cheers.
[Touch Diamond, MDA Compact IV ROM Development] mdrobnak:
As noted on the Wiki you can check out #htc-linux on FreeNode using an IRC client. That's where most of the developers hang out.

-Matt
[Touch Diamond, MDA Compact IV ROM Development] hibby50:
same problem, same phone
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Connect your phone via usb to your pc and use ActiveSync mode (not disk drive). Then use haret to start linux. It should continue then. It's in the FAQ.
[Touch Diamond, MDA Compact IV ROM Development] clampi:
so will this work on my sprint tp?? and is it fully functional? and if it doesnt work can i go back without a hard reset? or is this ljus like flashing a rom?
[Touch Diamond, MDA Compact IV ROM Development] NoBody20013:
www.justreadtheWIKI.com
[Touch Diamond, MDA Compact IV ROM Development] hibby50:
I have it almost working. as soon as it is working i will post it up so everyone wont have to do what i did.
[Touch Diamond, MDA Compact IV ROM Development] frysee:
wiki says:

Just by reading the wiki page all of your questions are answered - so please stop bloating this thread with questions answered 1000 times before ;)

greetz

edit:

You are free to add any information valuable to other interested people :)
[Touch Diamond, MDA Compact IV ROM Development] asticinzano:
Maybe we should create a thread with the title "Ultimate r0xxors ANDROID for DIAMOND - YO! Get that ****!!!111"

Obviously this will attract a certain clientel who is nearly dieing from exhaustion after reading more than four words.

And to make something clear: It's extremely useless to post things like "I wish I could help but I only can program HTML. You guys are so awesome!"

Wake up! Typing something between

<html>

and

</html>

is not programming! So move along!

Enough ranting. Whoever is in charge can delete this post after some youngsters have read it.

I really am getting old and grumpy. ;)
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
I've updated the wiki for current state - Andriod 1.0 with the some new information, mostly taken from the progress section. Again, correct/update the information if it's incorrect.

Hardware keyboard: NO (RAPH series)
Although the keyboard slider switch works. It rotates Android display orientation between portrait and landscape mode.

Hardware buttons: Partial (All)
* On/Off = Doesn't work
* Home/Send = Send
* Up = Menu
* Center = Enter/Select
* Down = Back
* Back/End = End
* Volume Up/Down = Volume Up/Down
[Touch Diamond, MDA Compact IV ROM Development] NoBody20013:
One Question for understanding the Kernel Compilation process:

Is it "only" the Kernel Config which is needed that for Example the Sound works or the sound when making/recieving a call or the other Hardware as Buttons and Camera, GPS etc.? are all drivers (working/compatible drivers) already available or "build in" in android? Or what is the way you DEV´s have to go?

thank you for your answers!
[Touch Diamond, MDA Compact IV ROM Development] Bakuryu91:
I've found that if you launch ActiveSync on the PDA (even if there's no computer) before launching HaRET, there is no more bug ! Can anybody confirm ?

Sorry for my english ^^"
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
I just wanted to say what awesome progress have been made the last couple of weeks. If we get calls working as well as the Touch Pro hardware keyboard, Android would be very near a useable state on the TP and Diamond :D

I have a question though. Android, at least on my Touch Pro was slightly laggy and slow compared to Android on my G1. Is this something that would be improved upon in later builds, or what do you guys reckon?

And how do we enable the Raph's qwerty keyboard? What's missing?
[Touch Diamond, MDA Compact IV ROM Development] Maestro Nobones:
I hope I'm allowed to pop in here and say THANK YOU SO MUCH to all devs working on this project.

My GF has the G1 and I have the xv6850 Verizon Touch Pro and I am so jealous that her phone does everything my phone tries and fails to do without even breaking a sweat. WinMo is a lost cause and I look forward with great anticipation to the day I can run Android on my TP.

THANKS AGAIN GUYS!!!!
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
If you telnet into your phone right after android starts loading, you can use logcat to see the messages it spews out. (provided that you have an initrd that enables usb networking and telnetd, afaik lavender.t's does.)

You can do that by modifying /init in the root fs image. Alternatively, you can use a different partition as your media storage by changing /system/etc/mountd.conf (like when you run android off its own partition).

Start at the 'build your own' section on the wiki and confirm that you are 'in business'. Then check the useful links / research pages and #htc-linux on freenode.

When you do, do it on the wiki. A forum post disappears below the horizon in 2 days.

Android already know how to talk to the kernel to inquire about the hardware or to manipulate the hardware. It does this in way not specific to a device. The kernel contains the drivers that translate between user<->kernel speak and the hardware.

The way the devs have to go it to figure out how to tell the hardware what android tells the kernel, and how to decipher the hardwares answer and translate back to kernel<->user speak to tell android about it. (android or any other user environment for that matter.)

The thing that makes this non-trivial and take time is the fact that HTC does not provide the necessary details.

There are a couple of things that negatively impact performance.

* No hardware display acceleration (libhgl)

* We (you) run off an ext2 image on a vfat partition, maybe running directly off a yaffs partition has some benefits..

* Polling rather than irq based touchscreen

* Drawing the vkeyb

* ...other stuff I have no clue about (power management?) ..

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
I just gathered all the files together and threw up a .zip file for those with the Touch Pro who just wants to give Android a go with the latest files available from jobo and all the others here.

Follow the guide and download here

Enjoy!
[Touch Diamond, MDA Compact IV ROM Development] norkoastal:
For the rest of the newbs out there I thank you.. :D

Edit oops.... I have a Raph110... Still no go?
[Touch Diamond, MDA Compact IV ROM Development] expanium:
Do we have any new pics of Android in Diamond?
[Touch Diamond, MDA Compact IV ROM Development] Sonfire:
No Luck with Fuze.

I was not able to Start Android with my HTC Fuze, never gets to the keyboard!

Oh well.... Thanks for the Files!
[Touch Diamond, MDA Compact IV ROM Development] oaa8:
Make sure it's connected to the computer with activesync not storage device and edit the device.txt to say

set cmdline "mem=64M msmsdcc_id=2 msmts_calib=0x7a.0x5e.0x35a.0x37f msmvkeyb_toggle=on"

instead of

set cmdline "mem=64M msmsdcc_id=2 msmts_calib=0x7a.0x5e.0x35a.0x37f msmvkeyb_toggle=off"

EDIT You may also want to remove the calibration part

set cmdline "mem=64M msmsdcc_id=2 msmvkeyb_toggle=on"
[Touch Diamond, MDA Compact IV ROM Development] Sonfire:
Cool, i'll try that when I get home!
[Touch Diamond, MDA Compact IV ROM Development] BGH80:
I don't mean to sound like a greedy mofo but at the moment it seems as though the biggest issues with the port are the lack of sound/mic (and keyboard I guess).

Are these likely to be significant hurdles to overcome?
[Touch Diamond, MDA Compact IV ROM Development] Sl4sher:
I finally got a change to get Android 1.0 booted on my Raph800 and I'm noticing a bug that I didn't see before.

When in android and when pressing some keys on the vkb in the text shell my screen scrambles like the system doesn't know how to align the frame buffer to the physical screen. In the same session it'll switch between scrambled like tv where each line is offset, uniformly shifted to the left with the left side of the buffer wrapped around to the right side of the screen, and aligned correctly. It seems to do this during normal usage rather than caused by a particular input or operation.

I don't know if this a know bug or not, but I did not see it mentioned in this thread so I thought I'd throw it out there.

Otherwise I'm really happy with the progress the devs have made and am looking forward to the full function version.
[Touch Diamond, MDA Compact IV ROM Development] norkoastal:
After these two changes the keyboard appears but the keys are very tiny and dont respond. The bottom message reads

"/bin/sh: cant access tty; job control turned off #"

The phone is locked at this point and will only Hard reset.
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Thanks, I will try to keep the files updated as well as new builds are available. I dont have a Raph110 myself, so give it a go and please let me know how it works out so that I can add that information!

Cheers
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Here is a few of Android on my Raph100
[Touch Diamond, MDA Compact IV ROM Development] jbelman:
DIAM100 Progress

Apologies since this is not technically development, but as an update from my first post my VF-UK DIAM100 is running Jobo's new zImage well, albeit without a few bits working.

My on-going work on this I'm logging here if anyone want's to have a look/comment (1 Pic so far).

I'm going to do a full writeup including the links for the files used to get this working so n00b's check back within next couple of days on above link.
[Touch Diamond, MDA Compact IV ROM Development] theintelligent:
Same here.
[Touch Diamond, MDA Compact IV ROM Development] liamhere:
or you can look here too

http://wiki.xda-developers.com/inde...ux#Currentx20.statex20.-x20.Androidx20.1x2e.0
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
The 3rd option is: msmvkeyb_toggle=hide. This does initialize the vkeyb, but has it initially minimized / collapsed / you only see the blue drag-square. (This way it is not so much in your face but still there when needed.)

I hope you mean _soft_ reset. Does the phone really hang or do you still see the flashing cursor after the last line?

Try removing the msmts_calib option, then manually calibrate on boot. This prints your calibration values to the console. Use these to construct a new msmts_calib option with your own values.

"In android .. in the text shell" - do you mean in the Terminal application in Android or do you mean before android starts loading?

..interesting. I'm hoping this is a clue to also get stable video on the Blackstone Touch HD. If you have a setup that lets you telnet or ssh into your phone, can dmesg to see if there are (m)any 'invalid update' messages?

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] norkoastal:
The cursor is still flashing, but there is no way to escape back to WM. I have to hard reset every time after launching. After picking at the screen for a while I was able to get (very innacurate letters typed). Any way to expand the keyboard to a manageble size to type in the launch message? Thanks :D
[Touch Diamond, MDA Compact IV ROM Development] Bimboy:
What happens when you try to soft reset? (me thinks you are getting the terms mixed up) A soft reset is putting the stylus into the reset hole, by the USB port. Hard reset is basically setting it back to factory default, where you have to set the whole device up again, as if it were new.

This has been mentioned in this thread already, but you can minimize the number of keys to tap on the vKeybd by doing this:

/i<tab>.a<tab><enter>

This changes the number of taps from 13 taps to 7. When you tap <tab> for the first time, you'll see 'init' display, the second time, you'll see 'android' display. :)
[Touch Diamond, MDA Compact IV ROM Development] norkoastal:
Please forgive my newbishness.. correct.. soft reset..ill follow your steps and give it another go thanks ;)
[Touch Diamond, MDA Compact IV ROM Development] thisperishedmin:
Just checking in to say great work and keep it up!

I've been keeping tabs on this and I'm really amazed so far...of course, I'd love to see it all go faster, but at the same time - my mind is just blown that everyone has accomplished what they have so far.

I look forward to testing and maybe on day usually Android fully with my Raphael.

keep it up! :cool:
[Touch Diamond, MDA Compact IV ROM Development] NikPraskaton:
Cant wait to have fully functional Android on my HTC :) Keep Up The Good Work Guys.
[Touch Diamond, MDA Compact IV ROM Development] refl3x0r:
Hey Guys!

Great Work so far but...

When I try to boot android it hangs at:

#mmc0: new MMC card at address 0001

#mmcblk0: mmc0:0001 000000 3932160KiB

#mmcblk0: p1

_

and this was it

any idea to bring it further?

P.S.: got a XDA Diamond from O2
[Touch Diamond, MDA Compact IV ROM Development] Riel:
How to boot it on Diam100?

Something not finding /mmc/ there, which I believe should've expected :)
[Touch Diamond, MDA Compact IV ROM Development] skiwithpete:
I'd like to help, have been trying to learn little bits (like what a trampoline is).

I have no programming experience (except HTML) but everyone needs to start somewhere right?

Can someone point me in the right direction to learn how to help this progress. Whether that be a beginners coding site, or an android site.

Cheers,

P
[Touch Diamond, MDA Compact IV ROM Development] doopsie:
I know this post is hardly of any use, but i really am super excited to see linux on my phone. :) All the best for the progress! Bless those working on this project, Thank you for taking a time out of your busy schedules just to share your knowledge and make the world a better place to live in. :)
[Touch Diamond, MDA Compact IV ROM Development] NikPraskaton:
I would also like to help.. but sincerely I dont know ANYthing about linux :( Just webdesign..
[Touch Diamond, MDA Compact IV ROM Development] dave94o:
so this is great,no new progress,great
[Touch Diamond, MDA Compact IV ROM Development] sensorama:
yea. Come on. *bump*
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
If you make any progress with Linux/Android on the HTC Touch Diamond, I'm willing to spare a few dollars for donation.
[Touch Diamond, MDA Compact IV ROM Development] NikPraskaton:
Me too :) Just to see it runnin...
[Touch Diamond, MDA Compact IV ROM Development] GurneyHalleck:
Perhaps something to bear in mind... it's only a couple of months (-ish) untill the HTC Dream comes out with Android ready to rock. It'll be so much easier to figure out a 'port' to the Diamond with a hands on working version of Android to refer to, that I imagine most devs will wait that couple of months, rather than flailing around in the dark, so to speak.

Besides, who knows - we might even see an official version from Google or HTC?
[Touch Diamond, MDA Compact IV ROM Development] Global_Inferno:
I'd love to think that HTC will bring out a "port" for Touch Diamond users, but the reality is that they haven't really got any reason too... It's a retail product already. Although you could argue it might spark a renewed interest in the Diamond if they did?
[Touch Diamond, MDA Compact IV ROM Development] molnitza:
Is it possible to emulate the complete hardware of the HTC Touch Diamond. That would make it easier to devlop/compile a linux for the phone.
[Touch Diamond, MDA Compact IV ROM Development] NikPraskaton:
Any help from this?

http://vivien.chappelier.free.fr/typhoon/index.html
[Touch Diamond, MDA Compact IV ROM Development] dcordes:
unfortunately it will not help because it is a whole different chipset and quite old.

I sent some info to premy
[Touch Diamond, MDA Compact IV ROM Development] eranhazout:
htc diamond

Hi

I have an HTC Diamond ...

I would like to install Android on my Diamond ... did you find any solution for this ?

you are welcome to send me any version to check on my mobile and I will post the bugs here ...

Thank you
[Touch Diamond, MDA Compact IV ROM Development] Riel:
Read this topic.
[Touch Diamond, MDA Compact IV ROM Development] sjeems:
@riel:

Erm exactly what topic should we read?

Or were you just informing us you had read this topic? ;)

I wss hoping you have a nice topic with some more info (and maybe even some solutions) on this topic.

Grtz,

Sjeems
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Basically the latest news is, that there is no news. Linux is still not booting on Diamond*/Raphael. Even worse, currently it's stuck at the point _before_ even booting the linux kernel (i.e. haret configuration trouble).

* I myself own a Raphael, so I'm not 100% sure if there may be more progress for the Diamond. But as the platforms are almost identical, I doubt it.
[Touch Diamond, MDA Compact IV ROM Development] skiwithpete:
I've done a search, but where can I find more information about haret? and its configuration? Which version is being tested on the diamond?
[Touch Diamond, MDA Compact IV ROM Development] schmeichler:
here is what I found on HaRET
[Touch Diamond, MDA Compact IV ROM Development] dave94o:
well that is just dendy
[Touch Diamond, MDA Compact IV ROM Development] dcordes:
here's a snippet of irclog which might contain a useful hint for solving the diamond boot issue. btw: does booting the msm7* kernels on raphael show the same symptoms?

<dcordes> dzo gave some interesting hints on the diamond boot problem:

http://xdaforums.com/showthread.php?t=402002&page=14

<swetland> dcordes: actually they can do IO with the mmu off

<dcordes> Espenfjo, if you didn't see it yet, you might look at it.

unlike you were assuming, he says it is more likely to be a problem in

the kernel code

<swetland> but you have to setup the periperhal window correctly

<dcordes> hm what's that?

<swetland> arm11 has sort of an alternate bus for peripherals

<swetland> which can be accessed by setting the right bits in the PTEs

(with MMU on)

<swetland> or configuring a range of address space for it (with MMU off)

<swetland> periph_2gb_open: /* open the peripheral port 2gb */ /* see

1136trm 3-164 */ ldr r0, =0x80000016 mcr p15, 0, r0, c15, c2, 4 bx lr

* swetland kicks irssi

<dcordes> no clue what are PTEs either. maybe I should put that info

in the forum

<swetland> imagine there are some linebreaks in there ^^

<swetland> page table entries

<Espenfjo> hmm, yeah, ok

<Espenfjo> Sadly the MMU stuff is way out of my league :\

<dcordes> Espenfjo, you understood what dzo said further? (because I

have no clue :'( )maybe we should pass that info to premy and dzo

<dcordes> I mean what swetland just said.. sorry

<Espenfjo> No, not really :)

<Espenfjo> or.. well.. somewhat.. but no clue how to address those issues

<swetland> feel free to repost. if their issue is peripheral access

when the mmu is off, the above snippet should do the trick.

<swetland> of course the kernel should be turning the mmu on first thing
[Touch Diamond, MDA Compact IV ROM Development] dejant_9:
For all the people: android is not yet a usable OS.

"NOT YET WORKING"

So stop noobs questions, keep this tread clean and let the developpers working...

And in order to test android:

- 1 read the wikki

- 2 if you have a question: read the wikki

- 3 if android don't boot : read the wikki

- 4 ..read the wikki.
[Touch Diamond, MDA Compact IV ROM Development] refl3x0r:
Got that point, following the wiki for weeks, but there's no answer for my problem!
[Touch Diamond, MDA Compact IV ROM Development] oaa8:
I read this in the wiki and it seemed to fix that problem for me but I have a raphael
[Touch Diamond, MDA Compact IV ROM Development] refl3x0r:
No, it isnt an unknown partition table

he finds partition p1, but it seems he can't access it!

But also tried with active sync activated and many different zImages and default.txt-changes