yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] 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
[Touch Diamond, MDA Compact IV ROM Development] Spike1506:
I would like to test the latest build on my HTC Touch Diamond.

How can I do this best?
[Touch Diamond, MDA Compact IV ROM Development] butterdori:
Please read the first page or the wiki first before asking.
[Touch Diamond, MDA Compact IV ROM Development] 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
[Touch Diamond, MDA Compact IV ROM Development] balsat:
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
[Touch Diamond, MDA Compact IV ROM Development] 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?
[Touch Diamond, MDA Compact IV ROM Development] 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
[Touch Diamond, MDA Compact IV ROM Development] 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!!
[Touch Diamond, MDA Compact IV ROM Development] balsat:
You can see the change log here
[Touch Diamond, MDA Compact IV ROM Development] mak213:
what is the progess on audio? and/or backlight controls?
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
This (link) is a commit against the latest git at time of posting. This (link) 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.

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
[Touch Diamond, MDA Compact IV ROM Development] kingoldstyle:
Yep .... Android on my Diamond

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.
[Touch Diamond, MDA Compact IV ROM Development] duuri:
@kingoldstyle i think you missed whole point of this thread.
[Touch Diamond, MDA Compact IV ROM Development] kingoldstyle:
ok?

And what it will be this missing point ? :confused:
[Touch Diamond, MDA Compact IV ROM Development] Riel:
"NOT YET WORKING"

And:

http://en.wikipedia.org/wiki/Google_Android
[Touch Diamond, MDA Compact IV ROM Development] 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!!!
[Touch Diamond, MDA Compact IV ROM Development] kingoldstyle:
well

can we know what are the advantages of Android beside WM? ( off course the good looking is ovious, but others than that?)
[Touch Diamond, MDA Compact IV ROM Development] 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 Diamond, MDA Compact IV ROM Development] touch of jobo:
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. It puts the driver in /drivers/i2c/chips/ and updates Makesfiles, Kconfigs, and defconfig accordingly. Just the new driver code.

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] balsat:
The screen calibration can be edited in the default.txt... I though the color on the Diam500 was fixed, but maybe I'm wrong.
[Touch Diamond, MDA Compact IV ROM Development] 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
[Touch Diamond, MDA Compact IV ROM Development] balsat:
Very nice work Jobo.

A new kernel with Jobo's new patch can be found here and a new Android build with the new kernel can be found here
[Touch Diamond, MDA Compact IV ROM Development] balsat:
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
[Touch Diamond, MDA Compact IV ROM Development] 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 ?
[Touch Diamond, MDA Compact IV ROM Development] balsat:
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!
[Touch Diamond, MDA Compact IV ROM Development] Pandur:
Battery Error???

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...
[Touch Diamond, MDA Compact IV ROM Development] asifqabil:
i get that aswell
[Touch Diamond, MDA Compact IV ROM Development] AdamHC:
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.
[Touch Diamond, MDA Compact IV ROM Development] mak213:
yes i also have this problem - DIAM100
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
Thank you! :) Suddenly this post on htc-android 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 that boots the latest cupcake albeit without /sdcard.
[Touch Diamond, MDA Compact IV ROM Development] Krad213:
It works now, thanks :)
[Touch Diamond, MDA Compact IV ROM Development] 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
[Touch Diamond, MDA Compact IV ROM Development] mak213:
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
[Touch Diamond, MDA Compact IV ROM Development] 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 Diamond, MDA Compact IV ROM Development] touch of jobo:
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.)

-Jobo

EDIT: git head is now fixed
[Touch Diamond, MDA Compact IV ROM Development] clickdeath:
yeah it's all good now. for some reason android wont get past the glowing logo screen, any suggestions?
[Touch Diamond, MDA Compact IV ROM Development] mak213:
yes rarely it gets passed but then it activates shut down then it hangs

but most of time it freezes at logo
[Touch Diamond, MDA Compact IV ROM Development] 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.
[Touch Diamond, MDA Compact IV ROM Development] fliggygeek:
HTC Diamond 3720

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.
[Touch Diamond, MDA Compact IV ROM Development] 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 Diamond, MDA Compact IV ROM Development] touch of jobo:
yes, it should boot all the way

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 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.

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
Seems 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 Diamond, MDA Compact IV ROM Development] touch of jobo:
vold mounts SD card

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 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. You can replace the original one in /system/bin/ with this one.

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] 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 Diamond, MDA Compact IV ROM Development] touch of jobo:
Follow the links in balsat & untouchab1e's signatures.

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] TaC:
Doh! Thanks.

What's the difference between android_images and android_fs compressed files? Do i need both of them?
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
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
[Touch Diamond, MDA Compact IV ROM Development] TaC:
Thanks, Jobo. I understand it now.

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

Gonna try it. :)
[Touch Diamond, MDA Compact IV ROM Development] 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 Diamond, MDA Compact IV ROM Development] 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
[Touch Diamond, MDA Compact IV ROM Development] fliggygeek:
HTC Touch DIAM130

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.
[Touch Diamond, MDA Compact IV ROM Development] 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.. 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 =\.
[Touch Diamond, MDA Compact IV ROM Development] fliggygeek:
Htc diam130

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?
[Touch Diamond, MDA Compact IV ROM Development] switchgott:
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
[Touch Diamond, MDA Compact IV ROM Development] fliggygeek:
removing the blue square

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
[Touch Diamond, MDA Compact IV ROM Development] 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?
[Touch Diamond, MDA Compact IV ROM Development] 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.
[Touch Diamond, MDA Compact IV ROM Development] kmartburrito:
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!
[Touch Diamond, MDA Compact IV ROM Development] balsat:
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!
[Touch Diamond, MDA Compact IV ROM Development] eezak:
the best way to shut down is to hold hangup button for a few second then select shutdown.
[Touch Diamond, MDA Compact IV ROM Development] balsat:
I you sure about that jobo?

I got the 2 lines in my file, and have no errors compiling!
[Touch Diamond, MDA Compact IV ROM Development] Marcin808:
HW Buttons do not work

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
[Touch Diamond, MDA Compact IV ROM Development] fliggygeek:
hardware buttons

did you make sure you were using the correct mtype for the diam100?
[Touch Diamond, MDA Compact IV ROM Development] 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...