yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] jaduvet:
FYI I have read the thread - ALL posts(!) And YES i know one could find lots of posts with some info on what I could need to get started. But I still very much would like some nice :cool: programmer to sum up where to go to get the basics. Reading all 583 posts to understand where it is best to start is not the easy way to start being useful (that was my conclusion by reading ALL posts).
[Touch Diamond, MDA Compact IV ROM Development] skiwithpete:
Go to the Freenode channel HTC-Linux
[Touch Diamond, MDA Compact IV ROM Development] dcordes:
well as cr2 said, as long as you do not write, everything is ok. to my experience linux doesn't do random things like writing to a device if you don't want it to. I will attach a zImage with nand enabled. you can boot it along with a console initrd and try hexdump /dev/mtd0 see if you get data. or use dd.

please only try if you are familiar with console use.

in case you would do things like cat blblabla > /dev/mtd0 that would be the

ultimate brickage

cause I think the spl and all are at the very beginning.

here's the .config I used to build this from the raphael git.
[Touch Diamond, MDA Compact IV ROM Development] Nilfik:
Hi sorry if its a bit offtopic O:)...

But what about gps navigation? I guess TomTom and Navigon wont work on android devices or?
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
Allright, so i've got android version 0.8 working.

It's a bit difficult to align the screen, but you'll have to do it while it's booting.

Maybe netripper can make something so that it aligns automatic.

Download the files here:

http://www.ebudget.nl/android08/
[Touch Diamond, MDA Compact IV ROM Development] itsallsubliminal:
this is great to hear, but freezes on my sprint diamond on boot kernel... you think you can do an edit so it can work with internal storage?? please? :D
[Touch Diamond, MDA Compact IV ROM Development] teddyen66:
.

boots nicely on my Diamond :-)

GREAT NEWS :-)
[Touch Diamond, MDA Compact IV ROM Development] sensorama:
Cool ****. Boots on my raphael.

Will check it on my diamond later tonight.
[Touch Diamond, MDA Compact IV ROM Development] ampao:
Tried the files keeeerrttt.

Still at HTC Linux framebuffer console.

Cant seem to get to the screen you posted. Any tips what to do from here? Thanks.
[Touch Diamond, MDA Compact IV ROM Development] mcage:
Confirm working on my Diamond, but indeed screen calibration is way off.

Cool big step though!
[Touch Diamond, MDA Compact IV ROM Development] Pixel du Rezo:
Is it possible to know how to use it ?

Copy all the files to the root of internal storage ? in a new directory ?

Thx for the answer.
[Touch Diamond, MDA Compact IV ROM Development] mcage:
Can be in a folder of your internal storage. Run the exe and your done.
[Touch Diamond, MDA Compact IV ROM Development] druidu:
Good job!

I have to emphasize this:

Calibration works only for the keyboard. The data is still reported to the Linux kernel in raw, unprocessed form (as the calibration should be libts's job, the touchscreen library that is).

As I already said, touchscreen and virtual keyboard drivers are in early form, useful only for developers to run stuff in the shell to make the rest of the drivers work :)

Also, touchscreen IRQs don't fire in Linux, not sure why. There should be a very suggestive message if they do fire (with lots of !!!!!!!!!!) -- I only got it to fire like 2 times, completely random -- or you find a way to make them fire, please tell me to fix the driver (right now it polls the touchscreen 20 times a second).

Did you make any changes to the kernel to boot it or was it just the initrd? I can make some changes so that the touchscreen gives calibrated results.

Edit: initrd also works with my older kernel build. Any changes to the initrd, maybe we can make the 1.0 boot? :)
[Touch Diamond, MDA Compact IV ROM Development] liamhere:
noobs

please note this is very early stages

if you don't know what you are Doing...YOU WILL BRICK YOUR DIAMOND.
[Touch Diamond, MDA Compact IV ROM Development] Global_Inferno:
Just so that people who might be interested know, today I downloaded the latest *.bin's and voila! It let me get passed the loading screen and I could see my UI for the first time. I believe it then locked up mind.. as I couldn't seem to "do" anything; but it's better than an endless loading screen!? :D

EDIT: The version in the Repos (http://linuxtogo.org/~lgorris/index.php?path=raphael_and_diamond-bootkit/) doesn't seem to work, I still get the endless loading screen. However the one from here: http://www.ebudget.nl/android08/ does indeed work.
[Touch Diamond, MDA Compact IV ROM Development] DimitrisC:
Just a thought. Maybe all you great programmers working on getting android to HTC Touch Pro/Diamond should form a team and work together and make this thread dedicated to this cause so that an account is set up and we can donate to your work. People donate around this forum for cooked roms so I think its only fair we donate for android as well.
[Touch Diamond, MDA Compact IV ROM Development] itsallsubliminal:
Rezo, if that works for you, let me know, cuz its not working with my cdma internal storage :(
[Touch Diamond, MDA Compact IV ROM Development] Razzee:
mine resets at that point, if I touch it...
[Touch Diamond, MDA Compact IV ROM Development] greebear:
Donating, Developing

I'm highly interested in helping out on this topic.

What I'd be willing to do:

1) Donate =)

2) Develop

Anybody(:confused:) interested in helping me out to open the door for me on this project can pm me. I then can describe what I _can_ do.

greebear

EDIT:

found this

http://connect-utb.com/index.php?op...d-diamond&catid=42:the-android-port&Itemid=67
[Touch Diamond, MDA Compact IV ROM Development] Razzee:
even if I don't touch it. Is there a logfile somewhere?

for some reason its detecting a vogue and not my diamond. the source seems the same at that point.

elif [ "`cat /proc/cpuinfo|grep -o Diamond`" = "Diamond" ]; then

both in our and in the vogue build
[Touch Diamond, MDA Compact IV ROM Development] Razzee:
which distro did you use?

k@k-desktop:~$ make ARCH=arm htc_msm_android_defconfig

make: *** No rule to make target »htc_msm_android_defconfig«.
[Touch Diamond, MDA Compact IV ROM Development] chamonix:
Maybe you made the same mistake as I made: I got the wrong source from an older how-to, the utb-connect tut says >> git clone git://gitorious.org/linux-on-qualcomm-s-msm/linux-msm.git

After checking that out I found the expected defconf.
[Touch Diamond, MDA Compact IV ROM Development] RationalGaze:
Umm...i did that too :D Trying with this how-to today.
[Touch Diamond, MDA Compact IV ROM Development] Razzee:
copied it 1:1 from the utb page

except for the page command
[Touch Diamond, MDA Compact IV ROM Development] chamonix:
Mabe you could be a little more precise about what you did, obviously it's working for some of us so the problem is in the details...

Does the defconf file exist in arch/arm/configs? did you enter the linux-msm dir before calling make?
[Touch Diamond, MDA Compact IV ROM Development] Razzee:
did the trick, thx

._.
[Touch Diamond, MDA Compact IV ROM Development] mmone3:
Great to see more people helping out, i have been playing around with some code changes too, made my own accel axis fix and a few things to the gps over the last month. Wish I had more time too.
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Used OpenSUSE 11.2. Just needed to install gcc ;)
[Touch Diamond, MDA Compact IV ROM Development] batkoo:
now tell me can i use android on my htc touch diamond wihtout troubles:)
[Touch Diamond, MDA Compact IV ROM Development] Razzee:
nope, still work in progress
[Touch Diamond, MDA Compact IV ROM Development] MrPippy:
DIAM500 update

For anyone with a DIAM500 (Touch Diamond CDMA), I've posted a new kernel and instructions in this thread
[Touch Diamond, MDA Compact IV ROM Development] babijoee:
I've been working on getting Android Eclair 2.0.1 build working for the Raph/Diam for the last couple of days. This build comes from Zenulator and many other fixes by other members. At the moment I am unable to detertime the cause of the system freezing just as it enters Android setup page.

I've tried removing GPS and disabling data connections but no avail.

JeckyllHavok was kind enough to provide me with a modified rootfs.img along with his system.ext2. I had created a new image but the problem remains.

I am going to setup a new thread to make things less confusing between eclair and donut within the Raphael forums.

If anyone would like to have a look and offer any advice please head on over.

I will update this post when i have created the thread. :D

http://xdaforums.com/showthread.php?p=5163756#post5163756
[Touch Diamond, MDA Compact IV ROM Development] axelo:
RAPH100 power management & autonomy

Hi Guys,

it seems like I have found the root cause of my terrible autonomy. I had a minor typo in the APN setting (i had a MMS proxy address entered in the default APN) which somehow caused an inifinite data transfer. Now since I have fixed the default APN the radio communication is greatly reduced. Removing the APN reduces the radio communication even more, but that's obviously not the way to go :-)
[Touch Diamond, MDA Compact IV ROM Development] axelo:
MMS on Raph100

Good news guys. Since I fixed my APN settings I can confirm that I CAN RECEIVE MMS! It is still a little tricky tho - when the message arrives it fails to download automatically so i have to manually request the download and it usually fails the first time too (maybe problem related to switching APNs?).

There is definitelly still some problem related to APN switching and power management since there is a lot of gprs/edge data communication going in the background even when the wifi is on... maybe deleting the APN will be a PM solution for me after all :-(
[Touch Diamond, MDA Compact IV ROM Development] RationalGaze:
rational@rational-laptop:~/kernel/linux-msm$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- zImage
make: arm-none-linux-gnueabi-gcc: Command not found
CHK include/linux/version.h
make[1]: `include/asm-arm/mach-types.h' is up to date.
CHK include/linux/utsrelease.h
CC kernel/bounds.s
/bin/sh: arm-none-linux-gnueabi-gcc: not found
make[1]: *** [kernel/bounds.s] Error 127
make: *** [prepare0] Error 2

I get this....I set the path to arm-2008q3/bin (at least i think i did :D). Well...i get stuck here. I am running Ubuntu 9.10 through virtualBox... gcc is installed..

i added the PATH like this

export PATH=/home/rational/kernel/linux-msm/arm-2008q3/bin:$PATH

it should be right... :confused:
[Touch Diamond, MDA Compact IV ROM Development] chamonix:
It looks a little weird that your xcompile env is within the kernel sourcedir (assuming ~/kernel/linux-msm is your source-dir).

My layout looks like:

~/kernel/
./linux-msm
./arm-2008q3

and corresponding to that my path:

> echo $PATH
/home/sven/kernel/arm-2008q3/bin/:/usr/local/sbin:<snip>

So I see following possible reasons from here:

- your path is not set for the shell you're running make in (do "echo $PATH" to check that)

- mixing tools and source does not work well

- arm-none-linux-gnueabi-gcc is not present in your "arm-2008q3/bin" directory (you installed the tools right?)

- arm-none-linux-gnueabi-gcc does not have execute rights
[Touch Diamond, MDA Compact IV ROM Development] evalabonazza:
test on my diam 100

.....name operator for my sim is old,tag omnitel pronto italia,this is old ,new is vodafone it but upgrade is possible ?:confused:

Thank for reply.

:)
[Touch Diamond, MDA Compact IV ROM Development] chamonix:
Settings - Wireless - Mobile networks - Provider and make sure you are not on manual. You can force a scan from there as well

Edit: typo
[Touch Diamond, MDA Compact IV ROM Development] Razzee:
your in the kernel dir

try

PATH=linux-msm/arm-2008q3/bin:$PATH

then get in the msm dir

cd linux-msm

then try to compile

the problem is definitiv in your path declaration, I got the same before I got it right. and you need to be in the right dir to execute
[Touch Diamond, MDA Compact IV ROM Development] RationalGaze:
Did it so, that i now have linux-msm and arm-2008q3 folders in the kernel folder. I echoed the path, and it is set to ./arm-2008q3/bin/ . arm-none-linuxgnueabi-gcc is definetly present in that folder... It's still giving me the same error.

Have to do some java programming for school now, will try again later. Thanks for your help!
[Touch Diamond, MDA Compact IV ROM Development] chamonix:
I would avoid relative stuff in PATH if I were you.
[Touch Diamond, MDA Compact IV ROM Development] RationalGaze:
No no, it isn't relative. I just wrote it with ./ ...beacuse i'm lazy.. :) the pathi is full /home/....
[Touch Diamond, MDA Compact IV ROM Development] chamonix:
Well I did a few tests modifying my environment to reproduce the problem and I'm afraid it's your path:

This is what happens when PATH is wrong:

>$ export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/sven/bin:/home/sven/android_sdk/android-sdk-linux_x86-1.6_r1/tools
>$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- zImagemake: arm-none-linux-gnueabi-gcc: Command not found
CHK include/linux/version.h
make[1]: `include/asm-arm/mach-types.h' is up to date.
CHK include/linux/utsrelease.h
CC kernel/bounds.s
/bin/sh: arm-none-linux-gnueabi-gcc: not found
make[1]: *** [kernel/bounds.s] Error 127
make: *** [prepare0] Error 2

and this when it's right:

>$ export PATH=~/kernel/arm-2008q3/bin:$PATH
>$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- zImage
CHK include/linux/version.h
make[1]: `include/asm-arm/mach-types.h' is up to date.
CHK include/linux/utsrelease.h
CALL scripts/checksyscalls.sh
<stdin>:1097:2: warning: #warning syscall fadvise64 not implemented
<stdin>:1265:2: warning: #warning syscall migrate_pages not implemented
<stdin>:1321:2: warning: #warning syscall pselect6 not implemented
<stdin>:1325:2: warning: #warning syscall ppoll not implemented
<stdin>:1365:2: warning: #warning syscall epoll_pwait not implemented
CHK include/linux/compile.h
<snip>
[Touch Diamond, MDA Compact IV ROM Development] Kreeckmann:
i have the same problem, i install the Connect-UTB package, whith the DIAM100 kernel, and, the batery die after 50 min.

camera is not working... :/ well i'm waiting for the new advances

greetings from Chile!
[Touch Diamond, MDA Compact IV ROM Development] Razzee:
time problem is fixed with the newest auto build.

the other problems are known http://pjottrr.no-ip.org:81/redmine/projects/show/androidphh
[Touch Diamond, MDA Compact IV ROM Development] da_flux:
When there will be a full rom available for the htc touch diamond you guys think?

Will I have to wait another months, or will the rom be here sooner?

thx
[Touch Diamond, MDA Compact IV ROM Development] Sina™:
any hope for replacing win mobile with android 2.xx?
[Touch Diamond, MDA Compact IV ROM Development] da_flux:
Yeah I would like to replace my win mobile with android! xD
[Touch Diamond, MDA Compact IV ROM Development] MarcLandis:
Read first before posting things that have been answered hundred times:

http://wiki.xda-developers.com/index.php?pagename=RaphaelDonut
[Touch Diamond, MDA Compact IV ROM Development] Dormantlemon:
you guys seen this? sorry if its been posted previously, but going through 602 pages of replies is very time consuming..

http://www.androidonhtc.com/diamond/installing_android

It does work fine for me, though its very sightly laggy.

Oh and if posting that link is against the rules, please forgive me
[Touch Diamond, MDA Compact IV ROM Development] da_flux:
Like I din't read that, i have even this build on my Diamond, but I'm asking when a full version would be available, a full rom.

Not something you run using haret
[Touch Diamond, MDA Compact IV ROM Development] Sina™:
i'm talking about version 2.xx, not 1.xx

2 years i think.
[Touch Diamond, MDA Compact IV ROM Development] babijoee:
At this stage loading Android through Haret is sufficient. Until we get better power management its a no go. WinMo still does the job for me and when Android gets a much better power management i wouldnt expect it. Please read abit before posting.
[Touch Diamond, MDA Compact IV ROM Development] da_flux:
Thx for the answer, I'm using winmo too, but i would rather have Andoird on my phone, and i don't have money for a new android phone.
[Touch Diamond, MDA Compact IV ROM Development] chamonix:
What's the problem with using Haret? Except the risk of bricking your phone and make it harder to do updates I don't see any benefit for a ROM at this time. Battery life is quite usable in my eyes (10+ hrs in normal use with appropriate settings here on RAPH110) and I tend not to reboot to wimo except for backing up my SD and apply builds or test settings.
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
You need more than 30hours autonomy for a smartphone ? That seems really weird.
[Touch Diamond, MDA Compact IV ROM Development] babijoee:
Actually i recharge my phone about once in 2 days while using winmo. But when running android i forget to charge it or turn it off otherwise the battery will die and i wont have much battery life for the next day.
[Touch Diamond, MDA Compact IV ROM Development] da_flux:
Yeah I use my winmo phona and charge also once in 2-3 days, I'm using android with haret.

But my question is when will we have an full android build, where all the functions(camera, gps ...) are available.
[Touch Diamond, MDA Compact IV ROM Development] bxmatus:
It will be done exatly in 22 days, 17 minutes and 5 seconds.

Really, what kind of answer are you expecting ? It will be done exactly at time when someone make it done. And b/c all developers are working on it in their free time and basicly for free you can't expect dead line.

You can hire your own team of programmers, pay them and make a dead line, and then you can choose an exact day when you want it done.

I'm voting for stronger rules here and for deleting this kind of questions without excuse. There is nice wiki page with all important information and when someone is lazy even to read it then there is no reason for keeping here those questions every second page.

btw last kernel is really cool, my device is up all the day, no crash so far. Good work !!! :)
[Touch Diamond, MDA Compact IV ROM Development] da_flux:
Maybe you should read my posts to?

I just said that i know that it cant be done in 1-2-3, i know that!

But maybe someone knows, what the thing are they need, that they don't have now to make a full rom.
[Touch Diamond, MDA Compact IV ROM Development] Razzee:
it's not necessary at the moment
[Touch Diamond, MDA Compact IV ROM Development] maury1234:
it worked

i tried to test android 1.6 on my diamond....

i downloaded this kernel(1.6) http://www.connect-utb.com/index.php?option=com_rokdownloads&view=file&Itemid=68&id=53:android-1

and the diam500 image (i think its for cdma) http://www.connect-utb.com/index.ph...iew=file&Itemid=68&id=79:diam500-kernel-image

extracted them to the root of the internal storage and it runed ok
[Touch Diamond, MDA Compact IV ROM Development] salim1001:
Maybe this might work for you as it worked for me...use the "Home" button when your phone gets locked and make sure you are pressing it properly as there are time lags in between...Best of Luck!
[Touch Diamond, MDA Compact IV ROM Development] Nakebod:
Unless I missed it somewhere, BT supports only an audio profile at this moment.
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
Everything but audio phone should work.
[Touch Diamond, MDA Compact IV ROM Development] Nakebod:
In that case I've missed something :+ Plus the comment @ this wiki page is outdated.

Not using BT much, so that could be an explanation.

And if you say "audio phone" I guess you mean the BT headset profile? Because if I remember it right, I used my stereo headset (A2DP?) a while back, and it kinda worked.
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
This page is totally outdated, not only for bluetooth.

Yes that's what I mean.
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
Also, diam500's mtype can be changed to 2040 now on the wiki?

I also see a lot of users supplying this to their default/startup.txt

mkdir /proc
mkdir /sys
mount -t proc proc /proc
mount -t sysfs sysfs /sys
mount -t tmpfs tmpfs /dev
mdev -s

without having any idea what it does. Personally, having used *nix once or twice I would figure that IF you can pass options to haret like that (just extra lines in your startup, no variable setting/passing etc) that the last line should be "mount /dev/mmcblkp* /sdcard" for it to actually do something(mdev -s will create mmcblkp?, * is a wild card to mount any device named mmcblkp with 1 additional character.) Question is, can I pass commands like this through haret? I've edited the wiki a little with this info.
[Touch Diamond, MDA Compact IV ROM Development] Bob_eponge:
Bugs report

Hi !

Quick report for last release :

- sometimes, i have a total black out : no wake up, no backlights on buttons, no charge with USB plugged in. This can be solved by removing battery.

- sometimes, auto reboot if i launch Haret, just before the Android logo.

- rarely, auto-reboot when sleeping.

Where can i find logs to help devs ?

Thanks you.

Bye
[Touch Diamond, MDA Compact IV ROM Development] beboxed:
So it does charge with no battery installed? ;)

Sorry, couldn't help myself there :)
[Touch Diamond, MDA Compact IV ROM Development] beblioy:
my battery wears very quickly... what i can do ?? please help
[Touch Diamond, MDA Compact IV ROM Development] chamonix:
I really depends on how quick quick is ;-)

I can tell you my battery lasts for about 10 hours with the last builds (e.g. 20091218) after I made sure no apps were doing stuff behind my back:

- gmail sync is off

- contacts sync is off

- cal sync is on

- wifi stays off when I don't need it

- I've disabled whatever location services

- I avoid apps like fring that do not respect my settings (they are not supposed to load and do anything as the SDK states but they still do)

- I've added "Advances Task Killer" and I kill all apps that are not supposed to be there regularly (about once an hour)

- use widgets carefully and look closely at what they are doing

I guess there is no receipt but now you know what is possible. Disabling data completely is also an option if you don't need it. I have seen serious figures about expected life > 20 hours without data.
[Touch Diamond, MDA Compact IV ROM Development] salim1001:
ANDROID ECLAIR 2.0.1

Has anyone tried the Android Eclair 2.0.1?

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

Can someone please test and respond back with the results?

Its for Raphael however clearly mentions that it works for Diamond too..
[Touch Diamond, MDA Compact IV ROM Development] beblioy:
my battery wears very very quickly for 3-4 hours.... can not withstand one days
[Touch Diamond, MDA Compact IV ROM Development] beblioy:
On WM my battery withstand 1-2 days ...

(sorry for bad english)
[Touch Diamond, MDA Compact IV ROM Development] gajdik:
It is really nice and fast build on my diam200. Radio is working, but no sound so far...
[Touch Diamond, MDA Compact IV ROM Development] beblioy:
please help .. what i can do whit this battery .. my brothe have a bithday tommorow and i want to surprise with android .. i buy HTC diamond yesterday.. please help
[Touch Diamond, MDA Compact IV ROM Development] beboxed:
I gave it a quick test on my DIAM100

- The system boots and responds slightly more smooth that Android 1.6 even though window animation are enabled.

- I couldn't get a working data connection, but i see that GPRS is still an opn issue so that's okay.

- Wifi and bluetooth also don't work.

These are the things i could test while working ;) hopefully i can test more thorough when i'm back home.

Cheers!
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
I'm working on making it usable.

Currently I fixed phone audio, sensors, and data connection. I also added lights and proximity sensors (I still have no clue on how to check wether it works ....). I'm still fighting with wifi and bluetooth.