[PRJ][OS]Linux and Android on HTC Diamond "NOT YET WORKING"

[mak213]

im using udK's r4 6.1 rom, ive used android alot and been keeping up with thread for some time now but i downloaded lasted build and ran haret and it started linux then vibrated twice then just hanged there yes i restarted phone countless times even disabled manila so id get a fresh boot but no help....cant wait for latest offical build !

[mak213]

There was a error in the root.cpiogz on my preveus build, i can't check my latest build out at the moment, but i hope it's running now!

ive used a the april 8th build and i finaly got to the android logo blinking etc but then it hangs there so in reply to u..it is not fixed appreciate the hard work ur up puttin tho


EDIT: im on 6.1 build 21040 btw DIAM100

[balsat]

ive used a the april 8th build and i finaly got to the android logo blinking etc but then it hangs there so in reply to u..it is not fixed appreciate the hard work ur up puttin tho


EDIT: im on 6.1 build 21040 btw DIAM100


I have just tried my latest build (http://balsat.servehttp.com/index.php?dir=Android-08Apr-09/&file=Android-images.tar.gz)on a diam100 and it work perfect!

[baalbaal]

Hi Balsat!

Thanks for all the hard work you're putting in!

Tried the file form the "latest build" link, and I'm getting the same results as mak213. It boots up, but hangs at the Android logo. Looks like it's in a loop somehow.. The logo will pulse almost two times, then hang.. blink and start over.

Keep up the good work!

baalbaal

[duuri]

hi balsat latest build works for me:) even can send sms:) and make call, but receiving doesn't work

[djsven]

Hi,

realy realy good work an big thanks to developer.

But in my DIAM200 doesn´t work.
Can someone tell me why?

Thanks.

Bye

[yann79]

Hello,

I had my diamond previously getting stucked at the "mmcblk0" when booting.
Also with the balsat version from the 6th of April it is now working fine and I get to the android OS (the funny thing is I have a PIN code in windows and it doesn ask it in android. Also I can send calls...strang).
With the 7th it also get stucked at the Android logo.

Nice work guys!
Yann

[saudoo]

Oh great... I'll try and run the newest build asap..

Btw.. Does anyone know if it's possible to change the resolution android is using? I find everything a bit too small. Especially dragging down the Notifications bar....

[dcordes]

Hello,

I had my diamond previously getting stucked at the "mmcblk0" when booting.
Also with the balsat version from the 6th of April it is now working fine and I get to the android OS (the funny thing is I have a PIN code in windows and it doesn ask it in android. Also I can send calls...strang).
With the 7th it also get stucked at the Android logo.

Nice work guys!
Yann

AMSS (modem operating system on arm9 side) doesn't know you booted a different operating system on the system processer. it doesn't notice any change so it doesn't ask for the pin again after you booted linux kernel on system proc

the gsm builds (both, raphael and diamond) are broken in the current kernel. and freeze during bootup. hope this will be fixed soon

[mak213]

I have just tried my latest build (http://balsat.servehttp.com/index.php?dir=Android-08Apr-09/&file=Android-images.tar.gz)on a diam100 and it work perfect!

i just upgraded from udK r4 to r5 and now it works flawlessly sry, but also tysm :)

p.s. i cant wait for audio, backlight toggle on and off then ill start using daily i dnt care if any bugs! lol

[mak213]

bah nvrmind it only workd fine once then 2nd time anroid loaded then said a process error then hanged then i tried to boot again and it hangs on android llogo

[balsat]

bah nvrmind it only workd fine once then 2nd time anroid loaded then said a process error then hanged then i tried to boot again and it hangs on android llogo


Will look into that, once i in a couple of days get home to my linux box!

[balsat]

delete this

[keaneo]

Hi, very nice work you are doing here! i have tried the 6th april version of your android, it works fine! great job..

i can send sms
but there is a problem, i don't have sound..and no wifi ..also i cannot shut down the phone to save battery...

i also tried the latest version on Connect UTB...all the wallpapers works in full screen on this version...have you developped this one too?

[scope008]

Over the past couple of days there has been a massive amount of changes made to the official android kernel source. (http://android.git.kernel.org/?p=kernel/msm.git) Has anyone tried compiling the new code for use on Raphael yet?

[gebruikershaes]

I don't think people are working on this anymore..

[mak213]

I don't think people are working on this anymore..

yes they are...it would work faster if the developers didnt get useless replys from fools like u

Hi, very nice work you are doing here! i have tried the 6th april version of your android, it works fine! great job..

i can send sms
but there is a problem, i don't have sound..and no wifi ..also i cannot shut down the phone to save battery...

i also tried the latest version on Connect UTB...all the wallpapers works in full screen on this version...have you developped this one too?

how about u read the dam wiki?

[chronster]

yes they are...it would work faster if the developers didnt get useless replys from fools like u



how about u read the dam wiki?

try and talk to people the way you'd want to be spoken to.

[sd00]

yes they are...it would work faster if the developers didnt get useless replys from fools like u



how about u read the dam wiki?

Fella, chill, i'm sure these guys feel the frustrated and are simply inarticulate when trying to convey this (but harmless all the same) - all of us monitoring this thread dream of the day the announcement comes "Andriod 1 - for HTC Diamond"

I too wish development was speedier, but I lurk, quietly, waiting & hoping.

Best regards to the gurus putting thier spare time & efforts into this.

Steve.

[keaneo]

thanks to you all...this is a god damn good job...HTC businessmen want to sell their "Magic" or "Dream", so they don't care porting Android on other phones....
i hope your working hard on the sound problem, this is in my opinion the N°1 priority issue, as a phone is made to call, and not just read...:p

for now, the android's sms interface is much more intuitive than WM65....

i also notice, that all the wallpapers are in FULLscreen on the 20090222 version http://connect-utb.com/index.php?option=com_jdownloads&Itemid=58&task=view.download&cid=25
but on the latest version on the basalt server, just 1 wallpaper is in fullscreen, why?

Good luck for you all

[Untouchab1e]

Keep in mind that Balsat's daily builds is basically the result of his own development work (correct me if I'm wrong here Bal ;) ), while on Connect-utb you will find the latest "stable" releases.

Right now I am trying to focus on the development process itself, because as of now, I feel that people are basically working on their own little mini-projects instead of working together.

We are basically just "code 'n fixing" this thing while we should be more organized.

[NoBody20013]

hi,

sorry, but i think the posts here in this topic are 80% "how can i help but i am a noob" posts, 8% "android isnt booting" and only 2% new code or bugfixing... and this for more then 4 month...

am i wrong?

for me it doesnt seem that there are one or two people who are able to port android to diamond because of knowledge... changing an mtype doesnt provide the functions needed. and waiting for functions implemented in a new kernel isnt the right way.

i dont know much about andoid and linux- so i cant help too :(

But maybe there are one or two people of you who CAN.

So if these people would post their knowledge or the fact that they have knowledge and then communicate over PM or the HTC Android Forum then we could have a chance to have a fully working android some day...

if i am wrong and there is a "Coding-group" then i am sorry. But maybe then this group is too little or not "powerfull" enough. Providing info on which part someone is coding/testing eg. would bring more people who want to help?


dont misunderstand me- i would love to have android on the diamond!

greetings!

[Untouchab1e]

There are quite a few working hard on this project, believe it or not. Pop in the irc channel and maybe you will learn something. I have no doubt that we have the neccessary skill and knowlage to get Android fully running..

Patience is needed though.

Furthermore, this topic isnt being used for development discussion anymore, at least not significantly ;)

[saudoo]

But you are still updating the wiki though.. right?

Edit: I mean.. When theres something to write about ofc! :P

[Dav0]

Hello:

Do this ADROID version works too with the FUZE? If works, how could I test it and then uninstall it? I like to try for sure.
...I use UBUNTU in an hard drive partition already with Windows on my laptop. I'm downloading now, and then I'll change to UBUNTU OS to search mora about that...
Linux OS are leaner and fastest.

[Untouchab1e]

For all those who want to actually try to help out with development and wants some help to get started, here is some info:

green over at htc-android.com has just written a really good guide on how to compile the latest android version for the DIAM100 (can be tweaked towards other devices). Check it out here (http://htc-android.com/viewtopic.php?f=13&t=193&start=0)!

Good luck!

[Untouchab1e]

But you are still updating the wiki though.. right?

Edit: I mean.. When theres something to write about ofc! :P

The Wiki information on XDA is currently in the process of being ported over to htc-linux.org/wiki (The Raph is complete now I think)

[mike171562]

Untouchab1e, you stated a few pages back you were working on configurations for the DIAM500 color fix, then a few pages later there was a reference to a fix on the wiki, which I cannot find, is there a fix for the messed up colors and screen tap for the DIAM500?

[jeckhart]

I recall reading on the list that the radio was working on the RAPH800 from Sprint (also reflected on the wiki). Using the two latest builds from Basalt, however, the radio does not appear to be active. Have I missed a crucial step? Was I mistaken that the radio works on the CDMA models?

Thanks,
John!!

[balsat]

I recall reading on the list that the radio was working on the RAPH800 from Sprint (also reflected on the wiki). Using the two latest builds from Basalt, however, the radio does not appear to be active. Have I missed a crucial step? Was I mistaken that the radio works on the CDMA models?

Thanks,
John!!

The radio should work on the raph800!
The 15 April build i released today had some trouble with the radio, that is fixed in this build (http://balsat.servehttp.com/index.php?dir=Android-15Apr-09/)

[mindphasr]

I too have no working in radio on the Sprint RAPH800 with the latest build..

[bombzhome]

yeah, radio doesnt work for me either.. with any build.

[petay]

I just tried Balsat's build for the 15th of April, im impressed as always, i was able to make and receive calls (with no sound of course) didnt get as far as txt messaging before the battery died but it was good!! just a thought though, i noticed the key maping has changed, up used to be the menu, i had a thought that as the power button on a diamond is unused in android, we could maybe map that to the menu button?? also it moaned at me that the sd card had been removed maybe thats just my default.txt that needs changing i shall have a look.

if you need anyone for testing i am keen and eager with me P3700/DIAM100!!

[richs1992]

hi all, I have a problem with the 14th april version for DIAM100 because when I have an incoming call, who call listen to only the first ring and after busy; after ,when I go to see to the incoming call received, there is the call.
what's the problem ?? I know that the volume doesn't work, but is this also a known problem ?
I hope you can give me an help asap
bye

[petay]

the older builds used to do that and i think the ones on Untouchab1e's site may still do

i tried the 15th of april build and it seemed to keep ringing untill i pressed the answer hardkey

I have tried changing my default.txt to get the internal storage to pretend to be the sd card buty nothing has worked yet, 1,2 or 3 for the command line options

[richs1992]

thanks very much, I'll try it asap
bye

[bombzhome]

Does anyone have a confirmed working radio release for the RAPH800?

[qq108108108]

the latest build works very great on diam100,thanks balsat for his effort.

[lappin]

hi all
i don't understand : does android works on diamond, or only raphael ?

[balsat]

hi all
i don't understand : does android works on diamond, or only raphael ?

Android works on Both!

[bombzhome]

Balsat, does the radio work on the RAPH800? I tried the latest build and it didnt work.

[GregDDC]

I can also confirm that the radio does not work on my RAPH800 using the 4-17 build. It is really nice though!

[petay]

i have tried the 17th of april build on my DIAM100 and the radio does work. power checking seems odd though, it shut itself down with a wasning message behind saying its less than 15%, but when i boot back into winMobile the battery has 2 bars (it didnt say a percent but im guessing about 30-40)

[richs1992]

excuse me petay ,
I alredy have a DIAM100 where I tested the 17/04 version, but the radio doesn't work to me ( only the phone line but no wifi gps bluetooth ).
Have you done anything else after or before booting android ?
I hope you can give me an help
bye

[jaymit]

excuse me petay ,
I alredy have a DIAM100 where I tested the 17/04 version, but the radio doesn't work to me ( only the phone line but no wifi gps bluetooth ).
Have you done anything else after or before booting android ?
I hope you can give me an help
bye

wifi, etc dont work at the moment - they're not working on most android ports as yet - I think its only the cell line which works for now.

[bombzhome]

wifi, etc dont work at the moment - they're not working on most android ports as yet - I think its only the cell line which works for now.

Yeah, I don't really care for WiFi for now, but I'd like to try it out with the radio.

[richs1992]

yes , I knew that the wifi etc didn't work, but petay had said that with his DIAM100 the radio worked; so I wanted to know because, only this.
thanks to all
bye

[Spike1506]

I would like to test the latest build on my HTC Touch Diamond.
How can I do this best?

[butterdori]

I would like to test the latest build on my HTC Touch Diamond.
How can I do this best?

Please read the first page or the wiki first before asking.

[touch of jobo]

Hi all,
I'm trying to get back into this linux and android development thing.
I noticed that my attempt at g-sensor driver was added to ltg git. I have been coding a little bit more on it: made the code a bit nicer, added more debug logging, renamed everything from raph-gsensor to kionix-kxsd9, swapped the axis around so that they make more sense. Also added pedometer and free-fall detector.
The measurement part works, as I see correct values getting dumped to console by the kernel. Unfortunately, I have no clue how to make sensor manager recognize and use it. I also tried just using the akm8976 driver with some extra logging to see when and where it gets called, but it doesn't, other than its init and probe.
Does anyone here have knowledge on sensor manager, and especially what it looks for in an input device?

The latest android code doesn't work for me. I think it is the -1.5-pre. It comes up with the new animated logo and boots all the way up to the point where it's supposed to launch the home screen, but it shuts down there.
@balsat: I think you're pretty much using the same recipe as I do for getting a cleanly built android ready for raph/diam. (right?) Does that still work for you on the latest code?

Thanks,
-Jobo

[balsat]

The latest android code doesn't work for me. I think it is the -1.5-pre. It comes up with the new animated logo and boots all the way up to the point where it's supposed to launch the home screen, but it shuts down there.
@balsat: I think you're pretty much using the same recipe as I do for getting a cleanly built android ready for raph/diam. (right?) Does that still work for you on the latest code?

Thanks,
-Jobo


Hey Jobo

The cubcake branch was ruin for 1 month ago, and has not been fixed yet... the Android master branch "repo init -u git://android.git.kernel.org/platform/manifest.git" does work fine with minor changes!

Nice to see you back jobo

[petay]

hi richs1992, i have managed to use the radio with no additions (no wifi or bluetooth)

i am able to call another phone number (although without sound)

i am able to see an incoming call, although a few seconds delay where it must be loading the call screen. i can also accept this call by pressing the bottom left (green) button. the call remains open until i press the bottom right (red) or the other phone ends the call (again there is no sound) after a short delay i get taken back to the place i was before the call came in

i am able to send a text message

i am able to receive a text message

this is what i mean by working radio, i have used the Android-images archive

just going to try the latest april 19th build. do you have any change logs balsat?

[richs1992]

thx very much petay for your kindness, I wanted to know only that.
thx again

@ balsat: thx very much for your incredible work but is there any improvement for the diamond in the 19th aprile release( as asked petay) ? However I'll go to try it asap

[petay]

i have tried the latest build and it seems as good as the rest. im at work so i can not properly test the calling but it did hold a call to the answer machine ok!!

I have aquired a G1 to play with so if there is anything anyone needs to know please feel free to ask!! i will try my best although it is locked to T mobile at the moment and im on orange, so i am stuck at the first registration screen!!! :p

the screen seems better than the diamond though, being capacitive rather than resistive you only have to touch it rather than actually pressing it

but yes 19/04/09 seems to me as good as the last build balsat!!

oh and welcome back jobo!!

[balsat]

just going to try the latest april 19th build. do you have any change logs balsat?

You can see the change log here (http://android.git.kernel.org/?o=age)

[mak213]

what is the progess on audio? and/or backlight controls?

[touch of jobo]

[...] made the code a bit nicer, added more debug logging, renamed everything from raph-gsensor to kionix-kxsd9, swapped the axis around so that they make more sense. Also added pedometer and free-fall detector. [...]
This (link) (http://tibook.jb.b4m.com/j0b0/diffs-commits/commit-raph-gsensor-kionix-kxsd9.txt)is a commit against the latest git at time of posting. This (link) (http://tibook.jb.b4m.com/j0b0/diffs-commits/kionix-kxsd9.c.txt)is the code for the latest driver. Again, measurement works, but the only test case I have (the Android bubble level app) fails.
I found something weird: when I move the .c file from ./arch/arm/mach-msm/ into ./drivers/i2c/chips/ (and modify Makefiles, Kconfigs and defconfig accordingly) it doesn't work anymore. The driver still runs, but the values it reads are different (and wrong). No idea why.

[...] the Android master branch "repo init -u git://android.git.kernel.org/platform/manifest.git" does work fine with minor changes! [...]
It appears to checkout the cupcake branch, or at least the resulting build_id=CUPCAKE and it won't boot all the way. Oh well .. not so important.

-Jobo

[kingoldstyle]

Is nice, what can i tell ... dw the Android-21Apr-09.tar , untar him, untar and Android-images.tar.gz , => a TMP folder, copyed to Internal memory, in side i found a boot folder, and inside him haret18.exe. I execute him ...and now i have Android .

Ok .... now , my opinions:
1. Why should we have this in our phones ....? there are more and nicer apps for Android ...? ( btw ... the interface, the look is nicer )
2. no sound, no in call, not at all ...
3. mmmm my opinion ....battery drainer !
4.is not closing the screen ... that is again not good.
5.I m asking ( io know this is a linux ported topic) , Win Xp maybe it will work better? and there are more apps ?
6.How I can mount internal memory ( "Your phone does not a SD card inserted")

Sry for my bad English .
And this indeed is a great work for who made it. Great release.

Your kindness MadQueen.

[duuri]

@kingoldstyle i think you missed whole point of this thread.

[kingoldstyle]

@kingoldstyle i think you missed whole point of this thread.

And what it will be this missing point ? :confused:

[Riel]

"NOT YET WORKING"

And:
http://en.wikipedia.org/wiki/Google_Android

[petay]

well the point of this thread is for us all to work together to get android working on a touch diamond.

i have got a G1 which runs android and i can say that it works really well. everything i need is there and i no longer need a stylus. It has been redesigned to be a phone operating system rather than being a windows pda with a phone part added. this makes it easier to use as a phone (in my opinion at least).

the hardware is quite similar between the G1 and the diamond/raphael the only main difference being the screen (apart from the subtle hardware differences that make this port difficult of couse).

The diamond is a lot better looking than the g1 so getting android onto the diamond would be a win win situation!!!

[kingoldstyle]

can we know what are the advantages of Android beside WM? ( off course the good looking is ovious, but others than that?)

[mike171562]

Anyone with a DIAM500 found a fix for the color issue? and the screen taps. I would start playing with it more, but the screen calibration is way off and the color issue just makes the screen look ugly.

[touch of jobo]

[...] I found something weird: when I move the .c file from ./arch/arm/mach-msm/ into ./drivers/i2c/chips/ (and modify Makefiles, Kconfigs and defconfig accordingly) it doesn't work anymore. The driver still runs, but the values it reads are different (and wrong). No idea why. [...]
Got it. :)
Rather than just doing the same thing wince does, I now have some chip init code that makes sense according to the kionix data sheet. :) This seems to make it work no matter where it is located.
Also, the driver creates 3 sysfs files: (in /sys/class/i2c-adapter/i2c-0/0-0018/)
enable - 0 = off, non-zero = on,
scale - 1..4 = +/-2G .. +/- 8G,
rate - number of samples per 10 seconds

A new full commit against current head (http://tibook.jb.b4m.com/j0b0/diffs-commits/commit-raph-gsensor-kionix-kxsd9-090423.txt). It puts the driver in /drivers/i2c/chips/ and updates Makesfiles, Kconfigs, and defconfig accordingly. Just the new driver code. (http://tibook.jb.b4m.com/j0b0/diffs-commits/kionix-kxsd9-090423.c.txt)

-Jobo

[balsat]

Anyone with a DIAM500 found a fix for the color issue? and the screen taps. I would start playing with it more, but the screen calibration is way off and the color issue just makes the screen look ugly.

The screen calibration can be edited in the default.txt... I though the color on the Diam500 was fixed, but maybe I'm wrong.

[mike171562]

balsat, thx for the response, is there a guide somewhere on how to calibrate using the default.txt? The color issue is still there for the DIAM500

[balsat]

Got it. :)
Rather than just doing the same thing wince does, I now have some chip init code that makes sense according to the kionix data sheet. :) This seems to make it work no matter where it is located.
Also, the driver creates 3 sysfs files: (in /sys/class/i2c-adapter/i2c-0/0-0018/)
enable - 0 = off, non-zero = on,
scale - 1..4 = +/-2G .. +/- 8G,
rate - number of samples per 10 seconds

A new full commit against current head (http://tibook.jb.b4m.com/j0b0/diffs-commits/commit-raph-gsensor-kionix-kxsd9-090423.txt). It puts the driver in /drivers/i2c/chips/ and updates Makesfiles, Kconfigs, and defconfig accordingly. Just the new driver code. (http://tibook.jb.b4m.com/j0b0/diffs-commits/kionix-kxsd9-090423.c.txt)

-Jobo

Very nice work Jobo.
A new kernel with Jobo's new patch can be found here (http://balsat.servehttp.com/index.php?dir=Kernels/) and a new Android build with the new kernel can be found here (http://balsat.servehttp.com/index.php?dir=Android-23Apr-09/)

[balsat]

balsat, thx for the response, is there a guide somewhere on how to calibrate using the default.txt? The color issue is still there for the DIAM500

Remove the msmts_calib=xxx.xxx.xxx.xx from the default.txt, start android and look for the calibration when the kernel boots... When the calibration is done write down the numbers and put it in the default.txt like this msmts_calib=xxx.xxx.xxx.xxx

[Krad213]

2 balsat

Can you fix "
Incorrect format for file ./languages/ru.txt on line 46.
Format is "variable name[tab]value"
" error on your site ?

[balsat]

2 balsat

Can you fix "
Incorrect format for file ./languages/ru.txt on line 46.
Format is "variable name[tab]value"
" error on your site ?


It should work now! if not, try to change your browsers language to english and i will look at it after the weekend!
Next time give me a private message!

[Pandur]

I try to start Balsat's 2304 but everytime Android shows up the GUI there is a Massage to plug in the power suply and than it hangs with the shutdown logo on a grayed out homescreen...


My Battery is at 100% and it shows the same massage with charger pluged in...

[asifqabil]

i get that aswell

[AdamHC]

can we know what are the advantages of Android beside WM? ( off course the good looking is ovious, but others than that?)

Touch friendly, easier and better looking interface, not by microsoft.
My main reason for wanting it is that it will been touch friendly and not have the ugly Today screen of WinMo. TouchFLO is nice, but i'd prefer the Android home screen.

Its just a different operating system, its like saying whats better about a windows PC than a Mac.

[mak213]

I try to start Balsat's 2304 but everytime Android shows up the GUI there is a Massage to plug in the power suply and than it hangs with the shutdown logo on a grayed out homescreen...


My Battery is at 100% and it shows the same massage with charger pluged in...

yes i also have this problem - DIAM100

[touch of jobo]

[...] everytime Android shows up the GUI there is a Massage to plug in the power suply [...]
i get that aswell
yes i also have this problem - DIAM100

Thank you! :) Suddenly this post on htc-android (http://htc-android.com/viewtopic.php?f=13&t=193) makes sense. Apparently the latest Androids (both master and cupcake) refuse to startup or immediately auto shutdown if the battery level is too low or unavailable. (In our case it's the latter.)
Green's kernel patch puts a dummy battery driver in place that reports full battery, just so that Android is happy. This didnt use to be necessary in 1.1 builds.

Another difference between the 1.1 and 1.5 Androids is that mountd was abandoned in favor of vold. However, the vold.conf file does not get installed by the build process. Merely copying it from ./development/data/etc/ is not enough, as it points to the wrong device node. Right now, Android does not mount my DS card. I'm still experimenting with this.

Finally, the Maps and streetview apps from the 1.1 SDK don't work in this Android anymore and the 1.5 SDK doesn't come with those apps. I will play around with that as well.

-Jobo

EDIT: I just noticed that maejrep submitted a battery/charger driver into git so we may not need the dummy driver anymore. Got maps and street working again. Still no love from vold. This is the kernel (http://tibook.jb.b4m.com/j0b0/android-1.5/zImage-jobo) that boots the latest cupcake albeit without /sdcard.

[Krad213]

It should work now! if not, try to change your browsers language to english and i will look at it after the weekend!
Next time give me a private message!

It works now, thanks :)

[mak213]

when should we expect a newer "Stable" build that we get from connectutb for example cause they still offer the 2-22-09 build witch is terrible :(

keep up the good work devs

[mak213]

Is nice, what can i tell ... dw the Android-21Apr-09.tar , untar him, untar and Android-images.tar.gz , => a TMP folder, copyed to Internal memory, in side i found a boot folder, and inside him haret18.exe. I execute him ...and now i have Android .

Ok .... now , my opinions:
1. Why should we have this in our phones ....? there are more and nicer apps for Android ...? ( btw ... the interface, the look is nicer )
2. no sound, no in call, not at all ...
3. mmmm my opinion ....battery drainer !
4.is not closing the screen ... that is again not good.
5.I m asking ( io know this is a linux ported topic) , Win Xp maybe it will work better? and there are more apps ?
6.How I can mount internal memory ( "Your phone does not a SD card inserted")

Sry for my bad English .
And this indeed is a great work for who made it. Great release.

Your kindness MadQueen.


read the wiki please we fully know all the bugs,defects, etc. we dont need u to rant and cover it up with oh that is just my opinion, we dnt need them

[clickdeath]

I spent hours trying to compile this on OS X then gave up and downloaded Balsats build :P I can't wait for this to be fully functional!

I'm hoping May will be a good month for this, with the release of the HTC Magic

[touch of jobo]

I spent hours trying to compile this on OS X [...]
I really recommend to just run linux in a virtual machine. It will save you a lot of trouble. Also, if something doesnt work, its much easier to find someone who had the same situation and found a fix.
(If your problem is that you get some link errors for the current ltg git head, thats not you. Its broken, needs 1 or 2 more options in defconfig, like this. (http://tibook.jb.b4m.com/j0b0/diffs-commits/commit-3d12634-090426-1-headfix))
-Jobo

EDIT: git head is now fixed

[clickdeath]

yeah it's all good now. for some reason android wont get past the glowing logo screen, any suggestions?

[mak213]

yeah it's all good now. for some reason android wont get past the glowing logo screen, any suggestions?

yes rarely it gets passed but then it activates shut down then it hangs
but most of time it freezes at logo

[Willis111]

man, I would take it hard, fast and dry right now if I could get the aircrack suite loaded onto my phone. Any takers? I take it the real discussion about current progress is on IRC atm. I check the wiki and forums and connect-utb all the time for updates. I notice on the wiki that the diam500's partition scheme is listed as unknown. I have a diam 500, I've repartitioned the storage card in it a few times but I think that origially it was /dev/mmcblk0p5 ... it is not anyways if you know what I mean ... If anyone else out there has the know how to look up the mmc partitions in nix through fdisk or listing devices mine is listed as /dev/sdc with /dev/sdc5 as the only space alotted for anything in an extended partition. As I've posted before I've tried many things like dropping down to 1 primary parition, setting it up for /dev/sdc1 etc and it seems that it can read /dev/sdc1, not the primary parititon only and that when I erase the partition table on the phone and then let it boot up it restores the partition as /dev/sdc5.

[fliggygeek]

Hi, im just trying to get into the dev for porting android, i bought one of the modified diamonds that are known as the Diamond 3720 and come with an additional 850mhz band on the radio to enable the use of telstra's nextg network. I was wondering how hard it would be to edit the build to support this as the current build hangs on boot.

[shadowline]

If I may ask, at this point in time, on either the diamond or touch pro series, does it boot past console? What works and what does not?
I ask because I am trying to see what my base model is and what im working off of when I am attempting to get it to boot on a diamond 2, so I know what I've broke and what was already broken.

Just for info, on the TD2, using mtype 1805 or 1910 it will boot into a console then nothing at all. As if it does not want to load anything from the img files.

Thank you. :D

[touch of jobo]

yeah it's all good now. for some reason android wont get past the glowing logo screen, any suggestions?
yes rarely it gets passed but then it activates shut down then it hangs
but most of time it freezes at logo
If I may ask, at this point in time, on either the diamond or touch pro series, does it boot past console? [...]

I have only one device to test with, a Raph100, but on that device I have just now tested and confirmed that a kernel built from git head at time of posting (with htcraphael_defconfig) will boot all the way into Android 1.1 (the boot logo with the white text and the green glowing robot) as well as 1.5 (the boot logo with the blue-grayish shiny text). Both are 'functional' as we know it: no audio, no sleep, no wifi, no bluetooth, etc... ;) ..and on 1.5 also no sdcard. :D

I tested by putting the entire Android file system on a dedicated partition and booting straight into that, not using image files. However that should make no difference once you have your images mounted and init running. (The boot screen is proof that you have...)

BTW: For anyone who builds their own Androids: If you put this file (http://tibook.jb.b4m.com/j0b0/android-1.5/root/initlogo.rle) in the root (next to init) of your Android file system, you get a (nice? .. I think so) Raphael/Diamond themed splash during preparation for first boot.

[...] EDIT: I just noticed that maejrep submitted a battery/charger driver into git so we may not need the dummy driver anymore. [...]
Yes, that works. With this driver, no dummy/fake driver is required anymore to keep Android happy.

-Jobo

[sibbor]

I have only one device to test with, a Raph100, but on that device I have just now tested and confirmed that a kernel built from git head at time of posting (with htcraphael_defconfig) will boot all the way into Android 1.1 (the boot logo with the white text and the green glowing robot) as well as 1.5 (the boot logo with the blue-grayish shiny text). Both are 'functional' as we know it: no audio, no sleep, no wifi, no bluetooth, etc... ;) ..and on 1.5 also no sdcard. :D

I tested by putting the entire Android file system on a dedicated partition and booting straight into that, not using image files. However that should make no difference once you have your images mounted and init running. (The boot screen is proof that you have...)

BTW: For anyone who builds their own Androids: If you put this file (http://tibook.jb.b4m.com/j0b0/android-1.5/root/initlogo.rle) in the root (next to init) of your Android file system, you get a (nice? .. I think so) Raphael/Diamond themed splash during preparation for first boot.


Yes, that works. With this driver, no dummy/fake driver is required anymore to keep Android happy.

-JoboSeems like we're really getting somewhere. Nice contributions mate! I'll keep on testing out new builds and report bugs (that's all I can do atm).

[touch of jobo]

[...] Still no love from vold. [...]
Ok, so I finally got A-1.5 / vold to mount the SD card, which means we're basically at the same level of functionality on 1.5 as we were on 1.1.
However, I'm not too happy with this solution, as it requires modification of Android system sources, which is always something I don't like.
Either the sysfs structure of the G1 is different that ours, or (more likely) vold can only handle SD cards that contain just one partition.
Here is a quite dirty patch (http://tibook.jb.b4m.com/j0b0/android-1.5/commit-90a4257.android.system.core-vold-raph-sdcard.txt) to have vold mount the (1st VFAT partition on the) SD card in a Raphael. I don't even think I have control over which partition gets mounted. The two changes are:
1 - It considers every node under /sys/class/mmc_host/mmcX/mmcX:XXXX/block:* rather than only looking for "block".
2 - It ignores error conditions from blkdev_get_num_pending_partitions() and considers those 'zero'. (So even if I didn't mind modifying Android, this still makes it a dirty one.)

If anyone wants to dive into making this work _properly_ (in stead of merely work), please do so.. ;) Hopefully all this is only because vold is still young and stupid, and we wont need such hacks anymore when it grows up. Until that time, I guess this is better than nothing.

Oh, and this is the modified vold (http://tibook.jb.b4m.com/j0b0/android-1.5/root/system/bin/vold). You can replace the original one in /system/bin/ with this one.

-Jobo

[TaC]

I know it's not a good idea to ask for this, but i will try...

I come from Kaiser, and Android file structure is quite different to Android for Diamond.

I have been reading the first post, htc-android forum, git... and i can't still find a way to get the whole latest package.

Any of you have a recent full package uploaded in any server? From that point, i can try different kernels and updates, but i need a starting point... :o

[touch of jobo]

[...] Any of you have a recent full package uploaded in any server? [...]

Follow the links in balsat & untouchab1e's signatures.

-Jobo

[TaC]

Follow the links in balsat & untouchab1e's signatures.

-Jobo

Doh! Thanks.

What's the difference between android_images and android_fs compressed files? Do i need both of them?

[touch of jobo]

Doh! Thanks.
What's the difference between android_images and android_fs compressed files? Do i need both of them?
You don't need both. It's 2 different ways to do the same thing:

The 'images' approach boots into a ramdisk, mounts the DS card, and then mounts the android images from the SD card onto the ramdisk. This is the way to go if you don't want to partition/format your DS card or if you can't mount your SD card onto a linux box. Also, you could argue that it is a bit closer to how G1 does it.

With the 'fs' approach, you untar an fs into an ext2 (or ext3) partition on your SD card and boot directly into that. If you build your own Android, this way is probably easier / faster.

I have no opinion on which way is 'better'. ;)
-Jobo

[TaC]

Thanks, Jobo. I understand it now.

"Images" is the way Android for Kaiser works, for me is the easiest way.

Gonna try it. :)

[TaC]

Ok, Android images boot fine (thanks again). In Diamond screen, Android looks pretty good, but still a bit slow. For the audio in calls thing, isn't possible to "copy" dzo's Kaiser work to get it working? He just got graphic acceleration enabled, but sound works since a few months, and may be possible to apply the same logic/programming structure to Diamond chip...

[touch of jobo]

If anyone (else but me) has trouble building android after repo syncing lately, here is your fix:

In ./build/target/product/generic_with_google.mk, comment out (or delete) the PRODUCT_COPY_FILES line (and the next 2 lines) then make.

-Jobo

[fliggygeek]

Hi all, i managed to get the RAPH800 build working on the DIAM130. The main builds dont work properly for the 130 for some reason.

[gm112]

Ugh.. been trying to get Google Android to properly boot up the HTC Fuze. Mines a RAPH110. I have no clue why, but it refuses to boot up. I've tried different command line switches that were posted in this topic(I searched RAPH110), tried the latest April 28th build found here (http://balsat.servehttp.com/index.php?dir=Android-28Apr-09/).. both failed. My last attempt was to modify the root.cpiogz image and stick the latest fs image in there. Haven't been able to get passed console handover: boot [htc_fb-1] -> real [tty0] after that. Although, with the untouched root.cpiogz it get does get past that. The problem is, it fails to find some files in "/system/bin". I'm already aware that other people have posted similar cases with the RAPH110. Can you give me any tips on what to do? I've been messing with this all day =\.

[fliggygeek]

i just dloaded the balsat images and am getting the error "rild needs 32 bit mode maybe run in legacy mode" wtf is this and why is it hanging there?

[djsven]

realy realy great work!!
Works realy good your new version balsat !!
But how can i remove the blue point left side?
I guess this ist the keyboard.

And new problem, android wants to know why there isn´t a sd card insert :-))
But you can make calls and write SMS.

Next problem is the hardware button mapping.
German diamond has got the call button / end call button over home and end button.
Android mapped different about.

Big thanks
bye

[fliggygeek]

to removethe blue square all you need to do is change the keypad option in default.txt from "hide" to "off" its the only place in the file that the word "hide" exists so its easy to find

[colossuss]

I've just gone through the stuff on balast's site, got Android up, just have a few questions (Sorry to be a leach)

Can anyone make a Europe (Perticually UK) Android image?

And after booting Android whats the best way to shut it down?

[bombzhome]

Any idea if radio/data is working on RAPH800 (Sprint Touch Pro)? I tried it on like the April 15th build and it wasn't.

[kmartburrito]

I've just gone through the stuff on balast's site, got Android up, just have a few questions (Sorry to be a leach)

Can anyone make a Europe (Perticually UK) Android image?

And after booting Android whats the best way to shut it down?

The best way to shut it down is to soft reset.

Also, to the above poster, the data/radio still isn't working on the RAPH800, I've got the build from the 28th and still no-go.

Be patient though, it's-a-comin!

[balsat]

The best way to shut it down is to soft reset.




I prefer to hold down the power button, and then press yes when asked to shout down.. wait 2-3 sec and then soft reset!

[eezak]

The best way to shut it down is to soft reset.

Also, to the above poster, the data/radio still isn't working on the RAPH800, I've got the build from the 28th and still no-go.

Be patient though, it's-a-comin!

the best way to shut down is to hold hangup button for a few second then select shutdown.

[balsat]

If anyone (else but me) has trouble building android after repo syncing lately, here is your fix:

In ./build/target/product/generic_with_google.mk, comment out (or delete) the PRODUCT_COPY_FILES line (and the next 2 lines) then make.

-Jobo


I you sure about that jobo?
I got the 2 lines in my file, and have no errors compiling!

[Marcin808]

Hi,
I tried with the latest five versions downloaded from the Balsat server and
all of them cause the following problem:
Hardware buttons do not work - when I enter for example the settings using the stylus and then I want to come back to to home screen and ... the Back Button, Home Buton simply do not work.

I use DIAM-100.
Any help would be appreciated.

Thanks,
Marcin

[fliggygeek]

did you make sure you were using the correct mtype for the diam100?

[saudoo]

And did you try to run Android more than once? Dno with the newest builds... But older ones did from time to time render the hw buttons unusable under android...

[touch of jobo]

I you sure about that jobo?
I got the 2 lines in my file, and have no errors compiling!
I'm sure. I build TARGET_PRODUCT=generic_with_google.
generic.mk doesn't have those lines.

On a more serious note: probably one of these days, we get nand enabled in the stock kernel. It may be wise to disable and delete flash_recovery and wipe, maybe more, when repackaging and distributing canned androids.. just a thought.

-Jobo

[Synth3t1c]

sorry to be this guy, but i was wondering if someone could update the wiki. i have no clue what state it is in after reading the thread for a few pages back...

[mak213]

sorry to be this guy, but i was wondering if someone could update the wiki. i have no clue what state it is in after reading the thread for a few pages back...

this is true an update is required :)

[balsat]

On a more serious note: probably one of these days, we get nand enabled in the stock kernel. It may be wise to disable and delete flash_recovery and wipe, maybe more, when repackaging and distributing canned androids.. just a thought.

-Jobo

Good point there!

[livefastdiefun87]

I havent been following this for a little while now can someone please update me on the status of the project ie whats working, can you call etc. Or a wiki link would be nice too ;) Also a link to d/l the newest files for android to operate on my HTC diamond

Thanks

[cetrespeo]

I've been here too for months and I've never been able to make it work properly.

I really can't figure out why we've 7201 and HTC or Google or whoever has made a fully opperative Rom. In my modest opinion this is a big mistake in google's intention to own the market. There are millions of HTC and no clear support is made. That means that nowadays WM6.1 is the best soft for our Diamonds and thats a very bad new. What a pitty.

We need to thank you developers for your great and dificult work. It seems that your work is to guide a blind in a desert. Thanks anyway. ;)

[livefastdiefun87]

The reason behind this is because they manufacture the ROM to specific standards depending on the hardware. Also even though Android is open source, Google have not fully released the source code for it so there are a lot of things which are trial and error.

Im not too sure how much you know about Linux Distro's (sorry if you do know this already) but anthing created outside of the main OS is usually done by devs such as the wonderful guys here trying to make this happen. So drivers to support hardware is literally made from scratch.

I know this project has been going on for ages but that is the beauty of open source, it will never stop because although one day there may be a stable fully working release, people dont sit back. They constantly improve on it :cool:

[mak213]

I've been here too for months and I've never been able to make it work properly.

I really can't figure out why we've 7201 and HTC or Google or whoever has made a fully opperative Rom. In my modest opinion this is a big mistake in google's intention to own the market. There are millions of HTC and no clear support is made. That means that nowadays WM6.1 is the best soft for our Diamonds and thats a very bad new. What a pitty.

We need to thank you developers for your great and dificult work. It seems that your work is to guide a blind in a desert. Thanks anyway. ;)

you have no clue wat ur saying....please shut up and just not "watch the forum for months" because if u truly were watching u would know MORE then u alrdy know witch is nothing so please stfu

[cetrespeo]

@livefastdiefun87 Totally right. But I'm just blaming Google for saying that they want their os in every phone and not helping developers. So this is too hard work for making it properly. As you say, if source code was really free, it would be another developing timing.

you have no clue wat ur saying....please shut up and just not "watch the forum for months" because if u truly were watching u would know MORE then u alrdy know witch is nothing so please stfu

:D So mature, thanks for the laughs ;)

[Marcellus_pnz]

@livefastdiefun87 Totally right. But I'm just blaming Google for saying that they want their os in every phone and not helping developers. So this is too hard work for making it properly. As you say, if source code was really free, it would be another developing timing.

This is so stupid... Google is developing the software for the mobile manufacturers. HTC developed the Diamond with WM onboard (developing the phone is not easy and short process). Why do you think HTC must provide the different OS for the product they already released?

[cetrespeo]

This is so stupid... Google is developing the software for the mobile manufacturers. HTC developed the Diamond with WM onboard (developing the phone is not easy and short process). Why do you think HTC must provide the different OS for the product they already released?

Who's talking about HTC?... As you mention it, which company was the first one to run an Android (by Google)?... Nonsense

[tidus25]

Hi everyBody, I read on a website that with the cupcake distribution that calls works fine, is that true or not?

[cdahlquistjr]

If you have a GSM Raph/Diam model, the call will work, but the sound won't, ie you can't hear them and they can't hear you, so you better wit till free nights and weekends kick in, cause it's going to be a bit of a waste.

[evilxhwnd]

i hate to ask, but can anyone update the wiki with the latest info?

[Marcellus_pnz]

Who's talking about HTC?... As you mention it, which company was the first one to run an Android (by Google)?... Nonsense
Google DOESN'T have the drivers for the Diamond, so if google programmers wish to port the android to the diamond (why would they?), they CAN'T. Only HTC can port google os to the diamond, but it will cost money to pay programmers, they will work on outdated phone instead of developing new devices. THIS is the nonsense.
Understand me right, I'm hoping enthusiast won't leave their work of porting and someday we will see the fully functional android on our diamonds, but you you talking like google or htc own you something. No, they don't! Surprise?

[seattleweb]

I'm sure now that this is out it will help http://andblogs.net/2009/05/specs/

[Drobilliard]

Touch friendly, easier and better looking interface, not by microsoft.
My main reason for wanting it is that it will been touch friendly and not have the ugly Today screen of WinMo. TouchFLO is nice, but i'd prefer the Android home screen.

Its just a different operating system, its like saying whats better about a windows PC than a Mac.

and whats wrong with MS. :p

[Willis111]

@balast or any of the other devs

hey, I seem to be having trouble mounting my mmc @ boot using the default.txt to specify it. My device is a DIAM500, the partition I need to mount (and it's always been this way on my phone) is sdc5 (just used sdc to stand for sd card) or mmcblk0p5. I am able to boot when I use mdev etc from the console of my phone/telnet. Any help would be appreciated and if some dick would stop removing this god damned info from the wiki every time I put it up ... wow, I'm just going to stop editing the wiki for my model phone and let some other guy with a diam500 tell you all that it's mmcblk0p5...

[Marcellus_pnz]

and whats wrong with MS. :p
As for me, it's ugly, unfriendly and very slow. Diamond is the firs and the last phone with WM I bought.

Let's stop the offtopic, there is already too much flame.

[logoutreally]

druidu would you be able to confirm the source of hardware (especially LCD controller and panel) used in HTC G1/Dream and Magic?


We have the core and we have Toshiba LCD controller (http://www.digchip.com/datasheets/new_parts/200605/1097779.php) already implemented (which is probably used in G1 and hopefully in Diamond too). ?

[johnnymatrix]

I have pretty much given up hope on android for my diamond. check out SPB mobile 3, it has a home screen very similar to androids with the 3 horizontally sliding desktops and the widgets. It helps the cravings!

[Willis111]

I have pretty much given up hope on android for my diamond. check out SPB mobile 3, it has a home screen very similar to androids with the 3 horizontally sliding desktops and the widgets. It helps the cravings!

How do I get aircrack/kismet to run on spb mobile 3 ^^.

Edit: Women think I'm sexy because I can crack wep in 10 minutes on my old p2 laptop, imagine all the action if I was using a pda.

Edit: I realize my problem is probably enduser w/not being able to mount the partition but if anyone could help me out I think it could also be included in a build assuming all DIAM500 devices are the same.

[donald-c]

Got Android 1.5 on my phone :O only problem is it really heats up :( no music. Mostly minor things (battery indecator, camera doesn't work and so on)
I thought 1.5 was released today, but I found a release from Febuary, probably a pre-release I suppose lol.

Edit. Is there a reason for the blue box at the top corner? Or is it a bug :P it can be moved but leaves a trail :(

[schildirulez]

Got Android 1.5 on my phone :O only problem is it really heats up :( no music. Mostly minor things (battery indecator, camera doesn't work and so on)
I thought 1.5 was released today, but I found a release from Febuary, probably a pre-release I suppose lol.

Edit. Is there a reason for the blue box at the top corner? Or is it a bug :P it can be moved but leaves a trail :(

answered some post before by fliggygeek:

to remove the blue square all you need to do is change the keypad option in default.txt from "hide" to "off" its the only place in the file that the word "hide" exists so its easy to find

[donald-c]

answered some post before by fliggygeek:

to remove the blue square all you need to do is change the keypad option in default.txt from "hide" to "off" its the only place in the file that the word "hide" exists so its easy to find

Thanks, I'll try it now :)
Oh and, I installed a few apps to the NEWAPPS folder, it appears in 'Manage Applications' but, how do I actually run them :(

[touch of jobo]

[...] Is there a reason for the blue box at the top corner? Or is it a bug :P it can be moved but leaves a trail :( [...]
It is not a bug. It is actually a keyboard in a kernel driver. If you tap it without dragging, it toggles the keyboard on and off.
-Jobo

[JaXx_StORm]

Hello guys, I'm interested in trying to write some device drivers for the sound, is that working yet? I contribute to Ubuntu on and off so I wanna see if I can get my hands dirty porting Android efficiently. I've just got a few questions.

Once you've booted Android with Haret, does a soft reset reboot you into WM? It's not very clear?

Whats working and what isn't. I think the Wiki page is a tad behind.

Before I compile from source, does someone have a link to the current working build to boot from Haret? I want to give it a whirl first!

Thanks in advance

[No1ustad]

Hello guys, I'm interested in trying to write some device drivers for the sound, is that working yet? I contribute to Ubuntu on and off so I wanna see if I can get my hands dirty porting Android efficiently. I've just got a few questions.

Once you've booted Android with Haret, does a soft reset reboot you into WM? It's not very clear?

Whats working and what isn't. I think the Wiki page is a tad behind.

Before I compile from source, does someone have a link to the current working build to boot from Haret? I want to give it a whirl first!

Thanks in advance

soft reset boots into WM, from there u can choose to stay in WM or boot the kernel

[touch of jobo]

[...]
Once you've booted Android with Haret, does a soft reset reboot you into WM? It's not very clear?
Whats working and what isn't. I think the Wiki page is a tad behind.
Before I compile from source, does someone have a link to the current working build to boot from Haret?

A soft reset boots the device back into windows.
It's not so much about porting Android but more about porting the kernel to expose the entire device.. ..to Android for example.
Not working: audio, data over radio, bluetooth, wifi, gps, most power management, gpu, cameras, fm tuner, ..
For canned Androids follow the links in the signatures of balsat or untouchab1e. (See here for quick explanation on fs vs. images. (http://forum.xda-developers.com/showthread.php?p=3701971))
When you have a good set you can just use that and only replace the kernel. Building your own Android doesn't give you that much extra, altho on occasion its useful to look into some Android source. Also, you need to take some extra steps to get it booting on your Raphael or Diamond.
The git branch you want to checkout is htc-msm-2.6.27

-Jobo

[mike171562]

I've been playing around with the Alternate build for the diamond on connect-utb, it seems when i change the mtype from 1805 to 2040 as is suggested here for the DIAM500, It will not boot but gets stuck on cannot find /system/bin/sh, /system/bin/servicemanager etc. like show here

http://www.flickr.com/photos/smesser/3408587152/

When i change the mtype back to 1805, it will boot but colors and screen calibration are still messed up. Anyone have a DIAM500, and been able to boot successfully with no color/screen issues?

[Willis111]

I've been playing around with the Alternate build for the diamond on connect-utb, it seems when i change the mtype from 1805 to 2040 as is suggested here for the DIAM500, It will not boot but gets stuck on cannot find /system/bin/sh, /system/bin/servicemanager etc. like show here

http://www.flickr.com/photos/smesser/3408587152/

When i change the mtype back to 1805, it will boot but colors and screen calibration are still messed up. Anyone have a DIAM500, and been able to boot successfully with no color/screen issues?

No, i think you and i are the only diam500 users on this forum. By any chance can you confirm your sd card layout? Mines extended/logical and my actual memory card is listed in android as mmcblk0p5 (meaning to me mmc block 0, partition 5). When I mount it up in gentoo it's the same thing, I mount sdcard5. I can confirm the problems that you're having with mtype, only solution I've found is to put it back on 1805. I think we're going to have color issues until this is a lot closer to release. I don't think changing mtype solves the color issue, check the wiki as there is some code that actually needs to be compiled into your images to take care of the problem (codes been figured out for raph100?). As for your calibration problems the easiest way possible is to remove the calibration bit from your default.txt and then manually calibrate your phone at boot though a search of this thread will reveal other ways (I think your calibration info is displayed when you manually calibrate your screen and can be copied down and moved into your default.txt in place of the calibration info that's there now).


Offtopic from the OP, I have read a few places that the wifi in our diamonds is based on the same chipset that the acx100 linux drivers use or tiacx100 (texus instrument acx 100). I was just wondering if anyone has tried building this driver into an image and accessing the wlan card after that. The driver is available through a project on sourceforge but it needs the correct firmware placed in /lib/firmware/ which I would guess be our problem if this is indeed the correct driver.

[DeadDaemon]

Kernel from Andrion 1.0 work also on HTC 4G, detect sd, but only internal (8g) with no partitions. External sd card not detected.

[computerguru]

No, i think you and i are the only diam500 users on this forum.

Nope...I'm also a poor soul stuck with a Sprint DIAM500...and have never gotten the colors to work correctly.

[zdrapka]

Hi guys, I have Diamond 2 and try to run Android 1.0 on it. I got stuck on Linux black screen after running HARET. Is there any way to boot Android? This is a sample of Diamond 2, not a device from a shop.
I will be grateful for help.

[computerguru]

Hi guys, I have Diamond 2 and try to run Android 1.0 on it. I got stuck on Linux black screen after running HARET. Is there any way to boot Android? This is a sample of Diamond 2, not a device from a shop.
I will be grateful for help.

I would assume that the Diamond 2 has different hardware from the original Diamond. The Diamond 2 has a 800x480 screen, while the original has 640x480...and I would assume they upgraded video chipsets, so the drivers from the original Diamond may/may not work.

My answer to you is wait...considering this forum is for getting it to run on the first-gen Raphaels and Diamonds.

[pegaz]

As far I can see there is rather no hope for fully working android on diamond/raphael almost 300 pages with posts and still nothing new -the same problems as on the beginning so I'm waiting for htc magic to be cheaper cuz I fed up with stupid and slowly WINDOW$ mobile...

[balsat]

As far I can see there is rather no hope for fully working android on diamond/raphael almost 300 pages with posts and still nothing new -the same problems as on the beginning so I'm waiting for htc magic to be cheaper cuz I fed up with stupid and slowly WINDOW$ mobile...

Hmmm no news... we cant be reading the same pages

[aniseto]

As far I can see there is rather no hope for fully working android on diamond/raphael almost 300 pages with posts and still nothing new -the same problems as on the beginning so I'm waiting for htc magic to be cheaper cuz I fed up with stupid and slowly WINDOW$ mobile...

Check Balsat server builds before saying this mate:

http://balsat.servehttp.com/

As you can see there are many builds and activity, so just say thanks to balsat. :)

[damo66a]

I wanted to find out if linux itself works on a diamond then saw how many pages on this thread there were lol.

Has anyone got a link to a working ROM? Or is linux not possible on these?

[Willis111]

Nope...I'm also a poor soul stuck with a Sprint DIAM500...and have never gotten the colors to work correctly.

I think the color issue is going to realitively easy to identify and resolve the closer android gets to being operational on our phones. You could always check the wiki and start messing with that code segment



I wanted to find out if linux itself works on a diamond then saw how many pages on this thread there were lol.

Has anyone got a link to a working ROM? Or is linux not possible on these?

You're joking, right? It says "not working" right in the thread title and if you'd pick any page in this thread and read it it would probably answer your questions about roms.

EDIT: Just wondering if any of our awesome devs checked into the tiacx100 drivers.

[katmandu421]

As far I can see there is rather no hope for fully working android on diamond/raphael almost 300 pages with posts and still nothing new -the same problems as on the beginning so I'm waiting for htc magic to be cheaper cuz I fed up with stupid and slowly WINDOW$ mobile...

Or you can get a HTC Vogue (aka sprint touch) and have a fully functioning Android 1.1 OS (1.5 aka Cupcake is almost ready, a few minor issues keeping me from going there) minus the bluetooth and gps. I have a diamond but had to grab a touch from ebay to try this out and am very glad that I did. I have not gone back to winmo except for the occasional GPS need.

[pegaz]

Sorry guys for this little provocation... I found this thread on the 3rd page a little dying so... I know there was done a lot of good job in this case (thx balast & other builders) but "we" stucked on the most important functions - sound, ability of calling ,connections (wifi,BT)etc. Maybe I'm wrong but I've read somewhere that android developers can't proceed because there is no drivers from google or htc for diamond and only they can provide them that's why I've lost hope.

[gm112]

Today's build seemed to fix the issues with rotating the screen on console. It doesn't force the text to overlap becoming impossible to read. Still unable to boot up completely on a RAPH110 due to the kernel failing to mount a partition, but I'm sure you guys are already aware of that. I'm looking forward to this project becoming more complete :P. You guys should setup donations so people can give you old phones or money.

[neptunes50]

I remember a guy Garuda50.. He mentioned that this aint gonna work.. BUt somehow.. he's banned for unknown reason..

[balsat]

I remember a guy Garuda50.. He mentioned that this aint gonna work.. BUt somehow.. he's banned for unknown reason..

And that guy is now known as neptune50!?
And why aint it gonna work?

[touch of jobo]

Ever noticed how in WinMo (in explorer and settings and such) you can scroll with your finger and (multi-)select with the stylus or your nail? This proves that the touch screen can detect something like 'touched area size'. So I decided to try and figure out how to get this information.
It appears that both +0x110 and the +0x114 contain position data, but the positions +0x114 reports are offset, scaled and skewed relative to the +0x110 positions, so that..
x1 = ax * x2 + bx * y2 + cx and
y1 = ay * y2 + by * x2 + cy

Now here is the nice thing: the amount of offset (c), scale (a) and skew (b) are pretty constant across the screen as long as you touch the screen the same way, and changes when you press softer/harder or smaller/bigger (i.e. stylus vs. finger).
So I did some measurements, found some values for ax,bx,cx,ay,by,cy for soft touch with stylus. Now for every (x1,y1)(x2,y2) pair, it solves for each of those 6 values. Weighing and combining those 6 numbers gives a pretty reliable reading for how big/hard you touch the screen.

The touch screen driver now reports this as a value between 1 and 15 (or 0 when not touched) as EV_ABS, ABS_TOOL_WIDTH. In the 'pointer location' app in Android, it now draws a small orange circle when I touch with my nail or stylus and a big one when I touch harder or with my finger. Also, the 'size' field shows a value between 0 and 1.

Here is a diff. (http://tibook.jb.b4m.com/j0b0/diffs-commits/commit-7bac2f0-msm_ts-size-090516.txt) The magic numbers in there are based on my measurements on my Raph100. Altho it uses raw values, not calibrated values, I still doubt that the numbers are good for Raph800s or Diamonds. Also, the math in this method is so dark that I can't believe its the proper way. But its a small modification and it works. Right now it can not (yet?) separately tell pressure from size.

This kernel is current ltg git head plus that diff. (http://tibook.jb.b4m.com/j0b0/zImage-msm_ts-size-090516-jobo) It'd be interesting to know whether it works on other devices than Raph100. If not, we'd need (to write) a different calibration routine.

-Jobo

[theoottesen]

i can get my diam500 to boot until i need to type /init.android, at this point the keyboard does not respond... any ideas

[chemical1979]

Ever noticed how in WinMo (in explorer and settings and such) you can scroll with your finger and (multi-)select with the stylus or your nail? This proves that the touch screen can detect something like 'touched area size'. So I decided to try and figure out how to get this information.
It appears that both +0x110 and the +0x114 contain position data, but the positions +0x114 reports are offset, scaled and skewed relative to the +0x110 positions, so that..
x1 = ax * x2 + bx * y2 + cx and
y1 = ay * y2 + by * x2 + cy

Now here is the nice thing: the amount of offset (c), scale (a) and skew (b) are pretty constant across the screen as long as you touch the screen the same way, and changes when you press softer/harder or smaller/bigger (i.e. stylus vs. finger).
So I did some measurements, found some values for ax,bx,cx,ay,by,cy for soft touch with stylus. Now for every (x1,y1)(x2,y2) pair, it solves for each of those 6 values. Weighing and combining those 6 numbers gives a pretty reliable reading for how big/hard you touch the screen.

My utmost respect to your reverse engineering abilities.

[No1ustad]

My utmost respect to your reverse engineering abilities.

x2. :):cool:

[ali15873]

hi
how can i install andorid os in my diamond
:D

[balsat]

hi
how can i install andorid os in my diamond
:D

Read the wiki and then download Android-images (http://balsat.servehttp.com/index.php?dir=Android-19May-09/)

[Willis111]

i can get my diam500 to boot until i need to type /init.android, at this point the keyboard does not respond... any ideas

Try removing and manually calibrate your touch screen and/or
try mtype for the diam100 in haret.

Edit: Spelling, punctuation, etc.

[ali15873]

Read the wiki and then download Android-images (http://balsat.servehttp.com/index.php?dir=Android-15May-09/)

thanck you i can install andorid

[mouyias]

there's an HTC optimized version of android that is due to be released soon. Will that improve the compatibility of our devices?

I've carefully read the wiki and i've seen that many of the functions of the HTC diamond do not work with android. Maybe all those problems could be resolved with the HTC version of android. What do you think guys?

here's a link:
h**p://gizmodo.com/5260862/htcs-android-interface-makes-us-temporarily-forget-all-about-palm-pre

[AdamHC]

there's an HTC optimized version of android that is due to be released soon. Will that improve the compatibility of our devices?

I've carefully read the wiki and i've seen that many of the functions of the HTC diamond do not work with android. Maybe all those problems could be resolved with the HTC version of android. What do you think guys?

here's a link:
h**p://gizmodo.com/5260862/htcs-android-interface-makes-us-temporarily-forget-all-about-palm-pre
I don't think this is that at all. I think its just an adjusted interface for HTC devices. Like the way that HTC has added TouchFLO to Windows Mobile. Its still the exact same Windows Mobile, just that it has a new interface and some other tiny tweaks. Won't really help with with getting Android onto the Diamond.

[aceofspades1217]

Honestly I would pay for a working bug-free version of Android (or at least a working bug-free version of windows mobile >.<). I would be more than happy to fork over 50 bucks for a decent OS.

[slovoflud]

hi
how can i install andorid os in my diamond
:D
God, save us all!

[AdamHC]

God, save us all!

I want to slap these guys through their computer screens, lol :)

[yuco91]

I\'ve a question: may I install androin on my diamond as default OS ?

[balsat]

I\'ve a question: may I install androin on my diamond as default OS ?

You can't install Android as your default os, because Haret.exe is the only bootloader at the moment, and haret is loaded from winmo.

[tughi]

Hi guys,

How can I make the balsat's image boot in the console?
I know that once there I can use ./init.android to start android, but how do I get into the console first?

I tried by changing default.txt settings "init=/init" to "init=/bin/sh" and "init=/system/bin/sh" but without success.

Thanks

[mike171562]

No, i think you and i are the only diam500 users on this forum. By any chance can you confirm your sd card layout? Mines extended/logical and my actual memory card is listed in android as mmcblk0p5 (meaning to me mmc block 0, partition 5). When I mount it up in gentoo it's the same thing, I mount sdcard5. I can confirm the problems that you're having with mtype, only solution I've found is to put it back on 1805. I think we're going to have color issues until this is a lot closer to release. I don't think changing mtype solves the color issue, check the wiki as there is some code that actually needs to be compiled into your images to take care of the problem (codes been figured out for raph100?). As for your calibration problems the easiest way possible is to remove the calibration bit from your default.txt and then manually calibrate your phone at boot though a search of this thread will reveal other ways (I think your calibration info is displayed when you manually calibrate your screen and can be copied down and moved into your default.txt in place of the calibration info that's there now).


Offtopic from the OP, I have read a few places that the wifi in our diamonds is based on the same chipset that the acx100 linux drivers use or tiacx100 (texus instrument acx 100). I was just wondering if anyone has tried building this driver into an image and accessing the wlan card after that. The driver is available through a project on sourceforge but it needs the correct firmware placed in /lib/firmware/ which I would guess be our problem if this is indeed the correct driver.



I gave up hope and got spb mobile shell 2, its the next best thing i guess.

[balsat]

Hi guys,

How can I make the balsat's image boot in the console?
I know that once there I can use ./init.android to start android, but how do I get into the console first?

I tried by changing default.txt settings "init=/init" to "init=/bin/sh" and "init=/system/bin/sh" but without success.

Thanks


Extract the files from the root.cpiogz and remove the init.android from the file init, repack the root.cpiogz!
Or download the root_noautorun.cpiogz form here (http://balsat.servehttp.com/index.php?dir=Boot/)

[tughi]

Thanks balsat.

I tried yesterday the steps you said too, but I my repacked root.cpiogz was invalid and linux would not boot.
What did I wrong?


mkdir test
cd test
zcat ../root.cpiogz | cpio -i
# edit init by commenting the last line
find . -depth -print | cpio -o | gzip >../root.cpiogz

[balsat]

Thanks balsat.

I tried yesterday the steps you said too, but I my repacked root.cpiogz was invalid and linux would not boot.
What did I wrong?


mkdir test
cd test
zcat ../root.cpiogz | cpio -i
# edit init by commenting the last line
find . -depth -print | cpio -o | gzip >../root.cpiogz


fnd . | cpio -o -H newc | gzip -9 > ../root.cpiogz

[tughi]

How can I set the DNS for usb0?

Update: I found a solution... I appended "net.dns1=x.x.x.x" to default.prop

[balsat]

How can I set the DNS for usb0?


Search and you will find (http://forum.xda-developers.com/showpost.php?p=3291064&postcount=2181)

[TR3Y]

Would anyone here know how I can get this to work on my Sprint Touch Diamond, which is DIAM500?
Please Let me know if anyone finds out.

[Saturn2888]

I have the same phone wanting to put Android on it as well :D.

[blacriderv]

Hey Balsat, there is an error when trying to acess to your server, I got this message displayed :

Error in download_counter.txt on line 125.
./Android-19May-09/Android-images.tar.gz is already defined.

Can you fix this please ? I wanna download the last Android package ;)

Thx in advance :)

[blacriderv]

Hum, I finally found the issue, used this link instead: http://balsat.servehttp.com/Android-19May-09/Android-images.tar.gz

[cr2]

I would assume that the Diamond 2 has different hardware from the original Diamond.

Can you post the haretlog.txt for diamond2 ?

[balsat]

Hey Balsat, there is an error when trying to acess to your server, I got this message displayed :

Error in download_counter.txt on line 125.
./Android-19May-09/Android-images.tar.gz is already defined.

Can you fix this please ? I wanna download the last Android package ;)

Thx in advance :)


I'm not at home at the moment, and i forgot to start my ssh deamon berfore i left :rolleyes: but mabye i can guide my girlfriend to start the deamon (don't get your hopes up) so i can fix the error!

[cr2]

Not working:... data over radio, ...


fixed that already for raph100

[cr2]

The reading from non-AMSS/oemsbl NAND partitions works too.
So stop whining and help the kernel development :)
TVOUT just needs some nice person who will port the qualcomm
tv_enc/mdp code for g1 kernel.

[touch of jobo]

[...]
Here is a diff. (http://tibook.jb.b4m.com/j0b0/diffs-commits/commit-7bac2f0-msm_ts-size-090516.txt) [...] This kernel is current ltg git head plus that diff. (http://tibook.jb.b4m.com/j0b0/zImage-msm_ts-size-090516-jobo) It'd be interesting to know whether it works on other devices than Raph100. [...]
Has anyone tried this? It'd be nice to know whether this is different for different devices.

Not working:... data over radio, ...
fixed that already for raph100
Cool. Was that the thing where you changed smd7 (and then some) from packet to stream interface?

The reading from non-AMSS/oemsbl NAND partitions works too.
So stop whining and help the kernel development :)
TVOUT just needs some nice person who will port the qualcomm
tv_enc/mdp code for g1 kernel.
How safe/dangerous is access to nand? (..if you don't mind my whining:))
For the tvout, I'd be happy to look into that but I'll need time and probably help. (Is it in the mdp code in the kernel/msm git?)



Also, I've been looking at the battery driver. Android only looks at it once or twice at startup and never again. The g1 driver creates an RPC server, so I guess the arm9 notifies the driver of status changes. The vogue driver has a kernel thread that just reports status change every 10 seconds, which in turn makes Android inquire battery status, etc.. (I will use this approach at least until I figure out the data..)
I guess it is just monitoring, not controlling charging, or is it? Do we have any info on how to interpret the data in smem?
@maejrep: Did you get it to report anything real on Raph800?

-Jobo

[slovoflud]

Also, I've been looking at the battery driver. Android only looks at it once or twice at startup and never again. The g1 driver creates an RPC server, so I guess the arm9 notifies the driver of status changes. The vogue driver has a kernel thread that just reports status change every 10 seconds, which in turn makes Android inquire battery status, etc.. (I will use this approach at least until I figure out the data..)


-Jobo
if that's true - can we later change the check time to more than 10 secs? that's way too often and will reqiure more battery. I'd think 1 per min is quite enough.

[lrp1985]

To people cant boot ANDROID from Balsalt or ConnectUTB because raise the follwing error:

mount: mounting /dev/mmcblk0p1 on /mmc failed: Invalid argument


change this line in default.txt

imgdevname=/dev/mmcblk0 imgdevnum=0


for this


imgdevname=/dev/mmcblk0p1 imgdevnum=1



Works for me !

[balsat]

Hey Balsat, there is an error when trying to acess to your server, I got this message displayed :

Error in download_counter.txt on line 125.
./Android-19May-09/Android-images.tar.gz is already defined.

Can you fix this please ? I wanna download the last Android package ;)

Thx in advance :)


It is up and running!

[richs1992]

Excuse me all ,
I have a question because I don't understand a thing on the readme.txt (I'm a bit stupid :p) : it's written a way to have android on a partition but this means that is there a way to have definitely android on our device(even if choosing which os using at the starting of the device) ?
(excuse me for my enaglish)
waiting for a your reply
Richs

[Saturn2888]

It really would depend on your device though.

[richs1992]

excuse me very much, but if you (saturn2888) replied to me I don't understand the meaning of your reply. what "depend on your device" means ??
bye richs

[Saturn2888]

The type of phone you have. That changes how it will work. For instance, Android seems to be working better on the Touch Pro/Raphael than the Diamond by a lot.

[balsat]

The type of phone you have. That changes how it will work. For instance, Android seems to be working better on the Touch Pro/Raphael than the Diamond by a lot.

The hardware is almost the same, so why does Android work better on the Raphael than the Diamond?

[balsat]

Excuse me all ,
I have a question because I don't understand a thing on the readme.txt (I'm a bit stupid :p) : it's written a way to have android on a partition but this means that is there a way to have definitely android on our device(even if choosing which os using at the starting of the device) ?
(excuse me for my enaglish)
waiting for a your reply
Richs

Search and you will find (http://forum.xda-developers.com/showpost.php?p=3701971&postcount=2843)

[richs1992]

thanks very much for the help, now I understand and I'll continue to do the faster way .
thanks for all
Bye Richs

[Saturn2888]

The hardware is almost the same, so why does Android work better on the Raphael than the Diamond?
That's what I thought too but it's apparently not the case. I'd hope someone could elaborate on my point and verify it. I was just under that impression from what I've read thus far.

[wywywywy]

Raphael doesn't really work much better than Diamond according to this -
http://wiki.xda-developers.com/index.php?pagename=RaphaelLinux
It looks like there are more devs on Raphael than Diamond though.

I think, going at this rate, we will likely have a daily-usable (with compromises) build by the end of the year! :D

[Saturn2888]

YAY! :D. I've still got this phone until October 2010 so I'm happy about that, ha ha.

[fabius88]

is there a date for the android relase for diamond?

[balsat]

is there a date for the android relase for diamond?

Here is what you need (http://lmgtfy.com/?q=patience)

[touch of jobo]

Also, I've been looking at the battery driver. [...] Do we have any info on how to interpret the data in smem?

I now get somewhat sane values for 'level' based on voltage and current(?) and for temperature and report those to linux. This is a diff (http://tibook.jb.b4m.com/j0b0/diffs-commits/raph100-batt-jobo-090527.diff.txt). It leaves Raph800 code unchanged. I don't have the correct GPIs yet to detect charging...
@maejrep: What's with the battery driver in htc_hw.c ?
-Jobo

Edit: Just in case it's useful, here is a log of smem values (http://tibook.jb.b4m.com/j0b0/raph100-info/raph100-battery-log.txt).

Edit: Better capacity values and some kind of charging detection. This is a commit against current ltg git head. (http://tibook.jb.b4m.com/j0b0/diffs-commits/commit-86bfe43-raph100-batt-jobo-090528.txt) It'd be nice if someone could test if this works for Diam100 too..

[balsat]

I now get somewhat sane values for 'level' based on voltage and current(?) and for temperature and report those to linux. This is a diff (http://tibook.jb.b4m.com/j0b0/diffs-commits/raph100-batt-jobo-090527.diff.txt). It leaves Raph800 code unchanged. I don't have the correct GPIs yet to detect charging...
@maejrep: What's with the battery driver in htc_hw.c ?
-Jobo

Nice work Jobo... I have compiled a zImage with your patch, it can be found here (http://balsat.servehttp.com/index.php?dir=Kernels/)

[fabius88]

Here is what you need (http://lmgtfy.com/?q=patience)

ok I wait for android, no problem for me ;)

I don't understand why when start "camera" I see this message: please insert sd card before using the camera

is it normal?

[illi]

Anyone can help me please. What changes is needed to the default.txt file to make it run on Touch Diamond2 (Topaz)?

TQ

[gm112]

Kernel panic on something relating the device drivers. Not exactly sure what since the console spits out so much information at a time. Anyhow, I've posted this before. It's on a RAPH110 HTC Fuze. Anywhere I could possibly donate to the current team who's porting this? :p.

[TR3Y]

would anyone here know color correction thing posted on the Wiki (the color correction is expired) for the DIAM500? Because I am getting really close to getting Android to work on my Diamond.

[Saturn2888]

I just had a second Diamond go bad on me, and I just got this one today. If you can find out I would love to try it on the replacement I get.

[adilkhan1214]

So I currently have a Diam100 and I just installed the latest balsat image (zimage270509) and I got through all the screens and as soon as the android splash screen is done, it just says shutting down with a little circle revolving but then that just freezes and stops.

In the fuzzy background I see the "connect a charger" window with a ok button and I see the actual android home page loaded up.

[sibbor]

Was a while ago since I last tried Android on my DIAM100, so I thought I'd give it a shot today. I downloaded the latest files from Balsat's server; the current zImage and images.
So I currently have a Diam100 and I just installed the latest balsat image (zimage270509) and I got through all the screens and as soon as the android splash screen is done, it just says shutting down with a little circle revolving but then that just freezes and stops.

In the fuzzy background I see the "connect a charger" window with a ok button and I see the actual android home page loaded up.Same issue here

[touch of jobo]

Raphael doesn't really work much better than Diamond according to this -
http://wiki.xda-developers.com/index.php?pagename=RaphaelLinux
It looks like there are more devs on Raphael than Diamond though.
Maybe more devs have Raphs than Diams, but most development would apply to both devices. It's just hard to test and confirm that stuff works if you don't have the device.
The differences between Raphs and Diams are really in board-htcxxxx.c If you have a Diamond, and a Linux box, it doesn't take über-mad hacking skills to move changes over from raph to diam. (Although it helps if you can read C.)

would anyone here know color correction thing posted on the Wiki (the color correction is expired) for the DIAM500? Because I am getting really close to getting Android to work on my Diamond.
Expired? Right now, the 666 vs. 565 flags are used based on GSM vs. CDMA. It would be more appropriate to do this based on Toshiba vs. Epson. Something along the lines of this commit here. (I'd love to hear what this does on different devices...) (http://tibook.jb.b4m.com/j0b0/diffs-commits/commit-98c868f-mdp-666-565-jobo-090529.txt) Here, msm_fb passes the pixel packing format from the mddi client platform data on to mdp->dma() which uses it to configure the dma2 flags. Maybe the 'output_format' member was intended for this, I didn't see it used anywhere, but I wasn't sure so I introduced a new member.

[...] and as soon as the android splash screen is done, it just says shutting down with a little circle revolving but then that just freezes and stops. In the fuzzy background I see the "connect a charger" window with a ok button and I see the actual android home page loaded up.
The battery_smem driver is one of those things you may want to copy over from raph to diam. (Also, once you have a battery driver enabled, make sure it doesnt report zero capacity. I got good values for the Raph100 (2-byte smem layout) with the commit from my previous post (http://forum.xda-developers.com/showthread.php?p=3845111), but I'm not sure about the Raph/Diam800 side.) I would guess that the Diam100 uses the same smem layout as the Raph100 for this, and the Diam800 the same as Raph800. (But thats just a guess because I have nothing else to guess...)


Please report back when stuff moved over from Raphael works on Diamond so that it can be added into git.
Thanks,
-Jobo


EDIT:
So I went ahead and merged board-htcraphael into board-htcdiamond and here is the result (http://tibook.jb.b4m.com/j0b0/board-htcdiamond-raph-jobo-090531.c.txt). It compiles but I can't test it. I will produce a kernel and a commit against head as soon as I rebase my battery branch.

[frodo9999]

Hello to everyone,

I have the same problems with the battery drivers than adilkhan1214. I talk about the last Balsat build (Android-28May-09). My HTC Device is a:

DIAM100 64M
SPL-1.93 Olinex
MicroP-Diam (LED) v11
PSOC-Diam STAGE_PVT v0x30

I can confirm that at least two more user have the same problems with the same DIAM100 model.

Thank you to everyone for help to port Android to other devices.

P.D: I think a lot of user are able to Donate to support this projets. Donations could help to devs to have enough devices for testing changes in the kernel and test it in diferents diam/raph models.

[Soaa-]

Just a quick reminder: the DIAM500's mtype (2040) activates the color fix, although it also changes the configuration and makes it not boot.

Fun fun. :|

[yochen]

i will try ,but not now~~~~~

thanks for sharing your idea!

[mitpianoman]

Not sure if there was any doubt, but I'm happy to report I was able to boot under WM 6.5 on a RAPH800.

[TR3Y]

Just a quick reminder: the DIAM500's mtype (2040) activates the color fix, although it also changes the configuration and makes it not boot.

Fun fun. :| Also, I've found that changing mmcblk0 (in the default.txt) to mmcblk0p5 makes the keyboard atleast show upon the screen in some android versions

[Erik_PLD]

Hello everybody!Please, can you update at some time the XDADeveloperWiki page?
thnx

[irusul]

Not sure if there was any doubt, but I'm happy to report I was able to boot under WM 6.5 on a RAPH800.

Good for you

[richs1992]

even I confirm the problem with the diam100 with the 28th may release (as the 26th).
I hope the problem will solve asap ... I like very much android and I hope there will be a 100% functional release one day.
good work
Richs

[lucxxx]

Hello

has anyone manage to boot diam 100 with Android_fs.tar.gz ??
i'm not able to boot, it freeazes my phone sayng "booting in 5 seconds....."

I need to format my "Internal Storage" to an ext2 or ext3 partition? or it works as is?

[jutley]

Hi i was woundering if anyone could help on the HTC Touch Pro2 section under roms i have opened up a thread for android port we need help testing and trying to ge a base vershion running on this device would anyone be so kind to help thanks for your time.

[touch of jobo]

[...] as soon as the android splash screen is done, it just says shutting down with a little circle revolving but then that just freezes and stops. In the fuzzy background I see the "connect a charger" [...]
This clearly indicates that the only problem is lack of battery driver. I'd be happy to work on this together with someone who has a Diam100. I will produce a kernel from last weeks head plus battery in Diamond (later tonight), just to get a handle on this...

EDIT: So I went ahead and merged board-htcraphael into board-htcdiamond and here is the result (http://tibook.jb.b4m.com/j0b0/board-htcdiamond-raph-jobo-090531.c.txt). It compiles but I can't test it. I will produce a kernel and a commit against head as soon as I rebase my battery branch.
I've heard that we need to change #if 1 to #if 0 in htcdiamond_fixup() in that board-htcdiamond. Tho I'd like to have a single board-htcblergh for both raph and diam (and maybe blackstone) and do everything in htcbergh_device_specific_fixes().

Has anyone manage to boot diam 100 with Android_fs.tar.gz ?? i'm not able to boot, it freeazes my phone sayng "booting in 5 seconds....." I need to format my "Internal Storage" to an ext2 or ext3 partition?

You need an ext2 (or 3) FS on a partition on your SD card and extract the .tar.gz into it. (You get to use fdisk, mkfs, tar.) Then, in your default.txt you don't specify an initrd, and on the cmdline you specify root=/dev/mmcblk0p2 (or whatever your partition is) in stead of /dev/ram0.
I personally don't have a Diamond, but I would say Balsat has managed to untar these onto a partition and boot into it. I do the same all the time on Raph100.

-Jobo

EDIT:
This kernel (http://tibook.jb.b4m.com/j0b0/diamtest/zImage-diamtest-jobo) is head at 09/04/26 plus battery driver. This is a commit (http://tibook.jb.b4m.com/j0b0/diamtest/commit-diamtest-jobo-090603.txt) against that head (NOT current head. That commit would be huge :) )

If you have a Diamond an old set (kernel + images) that works (confirm this first so as to not chase ghosts), please test that it still works with this kernel (to make sure this kernel doesnt break anything new), that it doesn't work with recent images and the old kernel (to make sure the problem exists and that its the issue we're looking for), and finally that it works again with recent images and this kernel.

[richs1992]

how can I do an ext2(3) partition on my sd card ?? (I don't understand anything about these things)
Await for a your help
Richs

[touch of jobo]

how can I do an ext2(3) partition on my sd card ?? (I don't understand anything about these things)
Await for a your help
Richs
On Diamond I'm not sure, as you can't take the SD card out. (Maybe from within Linux on the device itself?) With Raph I use a card reader to mount the (removable) SD card on a Linux box.
Not to sound like an asshole, but if you don't understand anything about these things, using the FS images you put in /tmp is probably the better way to go.
-Jobo

[Willis111]

On Diamond I'm not sure, as you can't take the SD card out. (Maybe from within Linux on the device itself?) With Raph I use a card reader to mount the (removable) SD card on a Linux box.
Not to sound like an asshole, but if you don't understand anything about these things, using the FS images you put in /tmp is probably the better way to go.
-Jobo

I just use fdisk on my diamond ... plug it in, set it to disk mode, rtfm and fdisk away.

[fliggygeek]

Hey Balsat, whats up with your server?
its redirecting to another domain. also can i mirror the images when theyre accessible?

[krymel]

Hey,

i'm searching for the android images for installing them on my HTC Touch Diamond too. I also have webspace to mirror the images if wanted.

Would be nice to have a chance for building android images if the hosting / mirrors are offline.

Is there a documentation how to build such an image? :)

[krymel]

I've found the image build by Balsat on 2009-05-06 for touch diamond.

Uploaded it:

http://kyrosoft.de/downloads/Android-images.tar.gz

It's also available from:

http://www.wuala.com/Linux%20and%20Android%20on%20HTC%20Diamond/Android%201.0/_Builds/latest%20Builds/Diamond/?lang=de

[lucxxx]

This clearly indicates that the only problem is lack of battery driver. I'd be happy to work on this together with someone who has a Diam100. I will produce a kernel from last weeks head plus battery in Diamond (later tonight), just to get a handle on this...


I've heard that we need to change #if 1 to #if 0 in htcdiamond_fixup() in that board-htcdiamond. Tho I'd like to have a single board-htcblergh for both raph and diam (and maybe blackstone) and do everything in htcbergh_device_specific_fixes().



You need an ext2 (or 3) FS on a partition on your SD card and extract the .tar.gz into it. (You get to use fdisk, mkfs, tar.) Then, in your default.txt you don't specify an initrd, and on the cmdline you specify root=/dev/mmcblk0p2 (or whatever your partition is) in stead of /dev/ram0.
I personally don't have a Diamond, but I would say Balsat has managed to untar these onto a partition and boot into it. I do the same all the time on Raph100.

-Jobo

EDIT:
This kernel (http://tibook.jb.b4m.com/j0b0/diamtest/zImage-diamtest-jobo) is head at 09/04/26 plus battery driver. This is a commit (http://tibook.jb.b4m.com/j0b0/diamtest/commit-diamtest-jobo-090603.txt) against that head (NOT current head. That commit would be huge :) )

If you have a Diamond an old set (kernel + images) that works (confirm this first so as to not chase ghosts), please test that it still works with this kernel (to make sure this kernel doesnt break anything new), that it doesn't work with recent images and the old kernel (to make sure the problem exists and that its the issue we're looking for), and finally that it works again with recent images and this kernel.


I cant format internal storage of diamod with ext3, in fact i can but afther an restart the partition is back with fat32!! this is stupid!!!

[frodo9999]

Thank you Touch of Jobo¡¡¡

I test the lmage that krymel found (Balsat on 2009-05-06) and I can confir that it boot. Later I test that files changing the zimage file by your zImage-diamtest-jobo and my DIAM100 boot android without problem. With the new zImage test file my DIAM100 report a 84% Battery Level, and with WM6.5 I have a 52% Battery Level.

I´m waiting that some friends of Htcmania test this new zImage file to help you.

Thank you very much and if you need more test, please only order it.

EDIT:
_Erik_ - DIAM100 - Test the same Balsat build with the new zImage-diamtest-jobo with the same result. The old build work with the new zImage-diamtest-jobo file.
eco17 - DIAM100 - Test the same Balsat build with the new zImage-diamtest-jobo with the same result. The old build work with the new zImage-diamtest-jobo file.

[Saturn2888]

I cant format internal storage of diamod with ext3, in fact i can but afther an restart the partition is back with fat32!! this is stupid!!!
You might have to hit apply somewhere.

[celsius0010]

I searched all thru a few threads... what is the best build for a sprint touch pro. I loved android on my mogul i wanted to try it out on this phone but it seems the touch pro thread is behind this one thanks for the help

[touch of jobo]

With the new zImage test file my DIAM100 report a 84% Battery Level, and with WM6.5 I have a 52% Battery Level.
That 84% is hard coded (see the commit (http://tibook.jb.b4m.com/j0b0/diamtest/commit-diamtest-jobo-090603.txt)) , just to make sure the test couldn't fail because of battery smem layout differences making it report zero.
- buffer->level = capacity;
+ buffer->level = 84; // capacity;

You can check dmesg to see if it detects sane values (http://tibook.jb.b4m.com/j0b0/raph100-info/raph100-battery-log.txt). If so, and if we can get confirmation for raph/diam 800, we can remove that hack.
[...]if you need more test, please only order it.
Can you fetch from git, apply patches, and build and run your own kernels, or do you need prebuilt kernels? I'd love to see some feedback on the touchscreen area size thingy (http://forum.xda-developers.com/showthread.php?p=3788860), but I have to rebase this test stuff up to current head before I can build one that works on Diamond.

You might have to hit apply somewhere.
Also, you might want to make 2 (or more) partitions. One vfat for haret and images and one (or some) ext2 (or 3) to boot directly into.

-Jobo

[etx]

Ah hah! I found the mtype for the DIAM500. It's 2040. Problem now though, is that under this mtype, the internal storage doesn't fire up, so the images don't get mounted.

= Android fails to start.

Same here on my sprint cdma diamond. Any developments on this?

[sibbor]

That 84% is hard coded (see the commit (http://tibook.jb.b4m.com/j0b0/diamtest/commit-diamtest-jobo-090603.txt)) , just to make sure the test couldn't fail because of battery smem layout differences making it report zero.
- buffer->level = capacity;
+ buffer->level = 84; // capacity;

You can check dmesg to see if it detects sane values (http://tibook.jb.b4m.com/j0b0/raph100-info/raph100-battery-log.txt). If so, and if we can get confirmation for raph/diam 800, we can remove that hack.I'll see what I can do. Tested this out yesterday, but just moved to a new apartment w/o Internet connectivity so couldn't report back. I'll see if I can get hold on a dmesg log.

I'd love to see some feedback on the touchscreen area size thingy (http://forum.xda-developers.com/showthread.php?p=3788860), but I have to rebase this test stuff up to current head before I can build one that works on Diamond.Would love to test this out on my DIAM100, but as it looks now I'll need pre-built images.

[touch of jobo]

Ah hah! I found the mtype for the DIAM500. It's 2040. Problem now though, is that under this mtype, the internal storage doesn't fire up, so the images don't get mounted.Just a quick reminder: the DIAM500's mtype (2040) activates the color fix, although it also changes the configuration and makes it not boot.Same here on my sprint cdma diamond. Any developments on this?Is there any MTYPE with which you do have access to internal storage? (Like maybe 1805?)
Forget about the colors for now, I want to try this approach for the color issue (http://forum.xda-developers.com/showthread.php?p=3855490), which should not depend on MTYPE. But first we need storage mounted.

[...] I'd love to see some feedback on the touchscreen area size thingy (http://forum.xda-developers.com/showthread.php?p=3788860), but I have to rebase this test stuff up to current head before I can build one that works on Diamond.[...] Would love to test this out on my DIAM100, but as it looks now I'll need pre-built images.Now that these changes (on an old kernel) make Diam100s work, here is another kernel (http://tibook.jb.b4m.com/j0b0/diamtest/zImage-diamtest-on-head-jobo) that is based on the same changes as the previous one, but now on current git head (and htcraphael_android_defconfig) rather than on a month old git head. If it still works, that would confirm that new commits haven't broken it since.
So if that is all OK, here is yet another kernel (http://tibook.jb.b4m.com/j0b0/diamtest/zImage-diamtest-on-head-plus-jobo) that is the same, plus the touchscreen area size patch (http://tibook.jb.b4m.com/j0b0/diffs-commits/commit-7bac2f0-msm_ts-size-090516.txt) plus the mdp 565 vs. 666 patch (http://tibook.jb.b4m.com/j0b0/diffs-commits/commit-98c868f-mdp-666-565-jobo-090529.txt). (So for Diam500: if you have an MTYPE that fixes storage but breaks color, this kernel _might_ fix color without breaking storage, on the same MTYPE.)

Thanks for your feedback,
-Jobo

EDIT: So here are the things we should now be able to tell but aren't known yet:
* Do all devices boot into android on that 1st kernel (or on the 2nd for that matter..), without complaining about battery/charging? - Probably yes, but Diam500 needs an MTYPE that fixes mmc, not color.
* Does touchscreen size report work for Diam100 (with the 2nd kernel)? - I guess it does, but please confirm.
* Does touchscreen size report work for Raph/Diam 800/500? - No idea. Its possible that it does, as it uses raw data, not calibrated. Please confirm.
* Does the 2nd kernel fix colors for Diam500, using an MTYPE that enables mmc, and what is tat MTYPE? - I have good hope that it works. I guess the MTYPE would be 1805. Please confirm.
* Does the battery driver detect sane values for 4-byte smem layout (Raph800/Diam800)? - I don't think it does. Someone with the device should adjust the battery_table_4 (or post the values the driver logs for almost full, for almost empty, and for something less than half full).

EDIT: Clarificación
The touchscreen patch is supposed report how hard and/or 'big' you touch the screen, as per this post (http://forum.xda-developers.com/showthread.php?p=3788860). You can see the effect in Apps > DevTools > Pointer Location and in Apps > ApiDemos > Graphics > TouchPaint

[frodo9999]

Is there any MTYPE with which you do have access to internal storage? (Like maybe 1805?)
Forget about the colors for now, I want to try this approach for the color issue (http://forum.xda-developers.com/showthread.php?p=3855490), which should not depend on MTYPE. But first we need storage mounted.

Now that these changes (on an old kernel) make Diam100s work, here is another kernel (http://tibook.jb.b4m.com/j0b0/diamtest/zImage-diamtest-on-head-jobo) that is based on the same changes as the previous one, but now on current git head (and htcraphael_android_defconfig) rather than on a month old git head. If it still works, that would confirm that new commits haven't broken it since.
So if that is all OK, here is yet another kernel (http://tibook.jb.b4m.com/j0b0/diamtest/zImage-diamtest-on-head-plus-jobo) that is the same, plus the touchscreen area size patch (http://tibook.jb.b4m.com/j0b0/diffs-commits/commit-7bac2f0-msm_ts-size-090516.txt) plus the mdp 565 vs. 666 patch (http://tibook.jb.b4m.com/j0b0/diffs-commits/commit-98c868f-mdp-666-565-jobo-090529.txt). (So for Diam500: if you have an MTYPE that fixes storage but breaks color, this kernel _might_ fix color without breaking storage, on the same MTYPE.)

Thanks for your feedback,
-Jobo

Hi Jobo,

I´m sure you are waiting for new about the dmesg output but I´m in a bussines travel and I can´t test it as I like.

First of all I said that as sibbor I need pre-build Image files. The second thing is that i dont have a lot of linux/unix knowledge and is difficult to me understand the output of some commands.

I test your 2 last zimage files and both run in DIAM100. The first one boot but I have a problem with the diamond keys and once I go to the battery menu I can´t go out of this menu and I reboot my DIAM. The second one boot ok and all keys run well. Trying the second kernel I execute dmesg and I see it report a 40% battery level that is near the 48% that wm6.5 report. I´m not sure but I think DIAM don´t detect when I plug the USB.

Do you know a easy think to export dmesg output in a file and put it in internal storage to send it to you? (I´m not sure if android could access to internal storage).

I try to do more test this weekend and report it.

Thank you Jobo.

EDIT:
frodo9999 => wm6.5 48% -> android 36%
frodo9999 => wm6.5 38% -> android 31%
Marcitus => He think android report the battery power without problems.

EDIT2:
Touchscreen works ok with DIAM100. I don´t found issues in the touchscreen area (I only use the stylus to test it, I don´t know if you like I test it with some android software or command)

EDIT3:
I don´t have a image with contains developers tools. I usually download file image from Balsat server, but today is down. Jobo or Balsat, Could you share a link with a full android image file that contains developer tools?

EDIT4:
Frodo - DIAM100 -I have a Build with devtools and i can confirm that touch screen detect the touch size area. The circle is small when i touch with the stilus, and a little biger when i press hard with the stylus. If i touch with a finger i can see a big circle.
Erik - DIAM100 - Tha size of the circle is diferent when he touch the screen with a stylus ans when he touch the screen with the finger.

[torpie13]

Don't flame me guys but, from the Wiki there's no progress since March '09. So, what really changed from that date ? any progress on Raphael's side ? Sorry but It's hard to read every post from a +300 page thread !!!

Cheers

[Soaa-]

The DIAM500 can boot under the DIAM100's MTYPE, but of course, with the wrong colors.

I'm not sure if it actually mounts anything from within Android, but it does read the images and does load up Android correctly.

[andrewloh]

I hope i cannot see "NOT YET WORKING" in the topic. :)

Add oil!!!!

[Willis111]

Is there any MTYPE with which you do have access to internal storage? (Like maybe 1805?)


It's funny, I've posted on this and put this in the wiki only to have it removed .... Mtype 1805 + the mdev instructions I threw up on the wiki are the only way android USED to boot. Now there's no input (keyboard doesn't work, can't configure networking etc on the device because of no input). Changing the mtype from 1805 it's failed every time. I'm not sure why android boots, the keyboard is displayed and then when you try to type on it it won't output anything to the prompt but ...It kind of reminds me of how I've been adding mmcblk0p5 for the diam500 image device name but someone keeps clearing it out(the mtype is actually going to fix colors??), even though I've seen a few other diam500 users saying "I have mmcblk0p5 but it's not working!!!" Almost need another thread or something for end users to post their info that won't get flooded w/"is it working, how do I ..."

[frodo9999]

I think I have found the last image build by Balsat (2009-05-28) for touch diamond in a russian forum. I´ve upload it here:

http://www.gazup.com/J62ax-android-28may-09.tar.gz-download-mirrors

[gebruikershaes]

Not sure if anyone has posted this allready, but it seems that Open Kernal Lab has released a virtualization tool that allows Android to run on top of any guest OS.

http://www.ok-labs.com/releases/release/ok-labs-accelerates-smartphone-deployments-with-okandroid

[etx]

Is there any MTYPE with which you do have access to internal storage? (Like maybe 1805?)
Forget about the colors for now, I want to try this approach for the color issue (http://forum.xda-developers.com/showthread.php?p=3855490), which should not depend on MTYPE. But first we need storage mounted.

Now that these changes (on an old kernel) make Diam100s work, here is another kernel (http://tibook.jb.b4m.com/j0b0/diamtest/zImage-diamtest-on-head-jobo) that is based on the same changes as the previous one, but now on current git head (and htcraphael_android_defconfig) rather than on a month old git head. If it still works, that would confirm that new commits haven't broken it since.
So if that is all OK, here is yet another kernel (http://tibook.jb.b4m.com/j0b0/diamtest/zImage-diamtest-on-head-plus-jobo) that is the same, plus the touchscreen area size patch (http://tibook.jb.b4m.com/j0b0/diffs-commits/commit-7bac2f0-msm_ts-size-090516.txt) plus the mdp 565 vs. 666 patch (http://tibook.jb.b4m.com/j0b0/diffs-commits/commit-98c868f-mdp-666-565-jobo-090529.txt). (So for Diam500: if you have an MTYPE that fixes storage but breaks color, this kernel _might_ fix color without breaking storage, on the same MTYPE.)

Thanks for your feedback,
-Jobo

EDIT: So here are the things we should now be able to tell but aren't known yet:
* Do all devices boot into android on that 1st kernel (or on the 2nd for that matter..), without complaining about battery/charging? - Probably yes, but Diam500 needs an MTYPE that fixes mmc, not color.
* Does touchscreen size report work for Diam100 (with the 2nd kernel)? - I guess it does, but please confirm.
* Does touchscreen size report work for Raph/Diam 800/500? - No idea. Its possible that it does, as it uses raw data, not calibrated. Please confirm.
* Does the 2nd kernel fix colors for Diam500, using an MTYPE that enables mmc, and what is tat MTYPE? - I have good hope that it works. I guess the MTYPE would be 1805. Please confirm.
* Does the battery driver detect sane values for 4-byte smem layout (Raph800/Diam800)? - I don't think it does. Someone with the device should adjust the battery_table_4 (or post the values the driver logs for almost full, for almost empty, and for something less than half full).

EDIT: Clarificación
The touchscreen patch is supposed report how hard and/or 'big' you touch the screen, as per this post (http://forum.xda-developers.com/showthread.php?p=3788860). You can see the effect in Apps > DevTools > Pointer Location and in Apps > ApiDemos > Graphics > TouchPaint

Hey Jobo, I just tested your second kernel with all the patches on my DIAM500 and the screen colors are correct!! Well done! I'm using 1805 as the mtype and the touch screen calibration values from a RAPH800 and its pretty close.

The build I have does not have the dev tools, and for some reason the newest build someone posted a few posts back from balsats server will not boot for me. So i cannot test the touch screen mods right now.

[frodo9999]

Hey Jobo, I just tested your second kernel with all the patches on my DIAM500 and the screen colors are correct!! Well done! I'm using 1805 as the mtype and the touch screen calibration values from a RAPH800 and its pretty close.

The build I have does not have the dev tools, and for some reason the newest build someone posted a few posts back from balsats server will not boot for me. So i cannot test the touch screen mods right now.

Hi ext,

Here you have some files that I took of Jobo server.

http://www.gazup.com/v7NSd-diamond-jobo-050509.zip-download-mirrors

If you overwrite that files you have a build with devtools.

The build I post some post back don´t boot in my DIAM100 too. I use that files with the lastest jobo zimage file to make possible to boot it, but that build don´t have devtool.

[etx]

Hey Frodo, Thanks! That build is really nice, looks like its much more current. I made a video of the touch working on my diam500, and i'm going to look up that network over usb stuff so i can dump some dmesg output.

https://dl.getdropbox.com/u/120967/MVI_1826_sm.MOV

My battery is showing 84% with the newest jobo kernel. I only have a windows box and a osx box here at home so i dont think ill be able to setup net over usb anytime soon. But if you can tell me any info you need I will absolutely get it from my diam500 for you. I could setup virtualbox and network to that, so if you need dmesg output or anything else please do let me know and I'll get it. I really appreciate your hard work, I would love to be able to use Android on my diamond as well and I used to use it on the Touch port!

Also, I'm curious if ADB from the sdk can connect to android on the diamond if usb networking works. I'll try on my dev box at the office tomorrow.

[Saturn2888]

Awesome man! :D YAY For DIAM500

[BlazerRazor]

I just tried the new build on my DIAM100 - just have a little problem... I can't unlock the phone after I've booted :D

Anyone have a similar problem? can I disable unlock on boot?

[Erik_PLD]

I just tried the new build on my DIAM100 - just have a little problem... I can't unlock the phone after I've booted :D

Anyone have a similar problem? can I disable unlock on boot?

You only have to quit the sim lock in winMo before lunching Haret, and android will boot fine. ;)

[BlazerRazor]

You only have to quit the sim lock in winMo before lunching Haret, and android will boot fine. ;)

No success, I am running WM6.5 and I do not have any lock enabled but I still get the sim locked when entering Android. What am I doing wrong here? I used to be able to boot android without SIM locked popping up.