yashsingh1/xdaforums huggingface dataset:
[Desire HD Android Development] liljom:
got it

I asked the guys at the HD2 forum. I just edit the question :)
[Desire HD Android Development] bergfex:
One importend file will be the

/etc/X11/xorg.conf

Some links:

http://htc-linux.org/wiki/index.php?title=Ubuntu/Leo

http://www.htc-dream-g1.net/en/Linux/Debian/Native

Could you upload all /etc/X11/xorg.conf from the different images you have?
[Desire HD Android Development] liljom:
I deleted them :)

but I start to download them again before I go to the park with my familiy

you don't need the one from the HD2 image, right?!
[Desire HD Android Development] bergfex:
Yes and I also have the one from the LeeDroid Thread
[Desire HD Android Development] liljom:
here is one:

http://www.multiupload.com/V3V4B5E9YE
[Desire HD Android Development] zFr3eak:
thanks man
[Desire HD Android Development] bergfex:
I hit your thanks button :)

I think it should look something like this, mayby event1 instead of event0
[Desire HD Android Development] liljom:
and I pulled the one from rhobuntu, that is 0 byte. First I thought, that I did something wrong, but after a reboot and checking it, it is really 0 byte

and I owe you a big thanks, because you work on it, and I just help you a bit

...

other images I couldn't download as the download stopped after a few hours, or the ones from the ubuntu download site I couldn't mount
[Desire HD Android Development] zFr3eak:
i hit it too ^^ but there are only a few people who help the devs to fix something. so thanks :)
[Desire HD Android Development] liljom:
thank you :)

but I'm so excited about it, that I have to help

and if there is something simple like this, I'm happy to help you :)
[Desire HD Android Development] zFr3eak:
thats good i will now push the xorg to the image ;)
[Desire HD Android Development] liljom:
I booted the nook image, and it mounts the phones partitions nicely and places it to the desktop
[Desire HD Android Development] zFr3eak:
the honeycomb one?
[Desire HD Android Development] liljom:
nope, it's an ubuntu
[Desire HD Android Development] zFr3eak:
mmh i have here a honeycomb.img of nook maybe this work too :)
[Desire HD Android Development] torsrex:
I just noticed that if you use the hd2 image, you are able to acces your phone through the adb shell. If you use the leedroid one, you are not able to do this.
[Desire HD Android Development] liljom:
I booted 4 images, and only the HD2 can handle adb
[Desire HD Android Development] zFr3eak:
yes i try now to fix logcat too
[Desire HD Android Development] liljom:
hey

maybe these can help a bit:

http://www.conan.de/touchscreen/evtouch.html

http://forum.eeeuser.com/viewtopic.php?id=78661
[Desire HD Android Development] zFr3eak:
thanks. until now i am not succesfull.
[Desire HD Android Development] liljom:
any news? :)
[Desire HD Android Development] zFr3eak:
tried yesterday some things but was not succesfull will try again today :)
[Desire HD Android Development] liljom:
nice

and what did you try?

so if I have time, I won't do the same?
[Desire HD Android Development] zFr3eak:
i edited the xorg but was not succesfull with a working touchscrren ;)
[Desire HD Android Development] liljom:
okay

did you try the links I pasted?
[Desire HD Android Development] zFr3eak:
no will try it today :)
[Desire HD Android Development] bergfex:
The way we should be able to make the touch screen work:

Finding out witch X version we are using

Getting the right evtouch_drv.so for our version from

http://www.conan.de/touchscreen/evtouch.html#config"

We may have to cross compile it if it is not compiled for arm

Putting the evtouch_drv.so to /usr/lib/xorg/modules/input/

Figuring out witch /dev/input/event is "connected" to touchdriver

adb shell cat /sys/devices/virtual/input/input1/name

adb shell cat /sys/devices/virtual/input/input2/name

adb shell cat /sys/devices/virtual/input/input3/name

...

(The adb command would be used in the console of "Start Here.bat")

Using a xorg.conf like this (with corrected /dev/input/event0)

Section "Monitor"
Identifier "Monitor0"
Mode "480x800"
DotClock 0
HTimings 480 480 480 480
VTimings 800 800 800 800
Flags "-HSync" "-VSync"
EndMode
EndSection

Section "Device"
Identifier "fbdev"
Driver "fbdev"
Option "ShadowFB" "on"
Option "Rotate" "CW"
Option "RandRRotation" "true"
EndSection

Section "Screen"
Identifier "Framebuffer"
Device "fbdev"
Monitor "Monitor"
DefaultFbBpp 16
SubSection "Display"
Depth 16
Modes "480x800"
EndSubSection
EndSection

Section "Screen"
Identifier "480x800x16"
Device "fbdev"
Monitor "Monitor"
DefaultFbBpp 16
SubSection "Display"
Depth 16
Modes "480x800"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Builtin Default Layout"
Screen "Framebuffer"
InputDevice "Touchscreen" "CorePointer"
InputDevice "Keyboard" "CoreKeyboard"
EndSection

Section "InputDevice"
# use usb mouse until touchscreen driver is present for machine
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
Identifier "Touchscreen"
Driver "tslib"
Option "Protocol" "auto"
Option "Device" "/dev/input/event0"
Option "CorePointer" "true"
EndSection

Section "InputDevice"
Identifier "Keyboard"
Driver "kbd"
Option "XkbLayout" "en_US"
EndSection

The problem is, that I have to study for an exam the next days.

PS: I have uploaded all kernel modules on the first post. (Would be useful for dev who want to fix WiFi)
[Desire HD Android Development] Ghaztehschmexeh:
I've done this, all but the cross-compiling. Unfortunately, I get errors when starting X after modifying my Xorg.conf:

FBDEV(0): FBIOPUTCMAP: Invalid argument

Also something about failing to load tslib. Does the driver need cross-compiling?
[Desire HD Android Development] bergfex:
Thanks!

Whitch version have of evtouch_drv.so have you used?

A *.so (system object) is something like a *.dll. Using "file evtouch_drv.so" should give ous some information about this file. If this says something like X86 we need cross compiling. If this says something like ARM we may are the lucky ones. But cross compling should be quit possible.
[Desire HD Android Development] bergfex:
~/Downloads/evtouch-0.8.8$ file evtouch_drv.so
evtouch_drv.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, not stripped

=> Cross compiling is needed.
[Desire HD Android Development] liljom:
slowly getting closer and closer to working touchscreen :)
[Desire HD Android Development] Ghaztehschmexeh:
Right then, project for tonight! >:)
[Desire HD Android Development] zFr3eak:
when you try this, i will try to boot the system without cmd. so that we only have to flash a small "rom" with a boot.img and it will boot from sdcard.
[Desire HD Android Development] Ghaztehschmexeh:
Also, I can only find one evtouch_drv.so? The one in the precompiled drivers? Can you get it elsewhere?
[Desire HD Android Development] Ghaztehschmexeh:
Sound good :D
[Desire HD Android Development] bergfex:
@liljom:

Can you have a look if this image has a evtouch_drv.so in /usr/lib/xorg/modules/input/ or elsewhere, please?
[Desire HD Android Development] bergfex:
It should be possible to find evtouch_drv.so for arm somewhere in the web.

Googling for "evtouch_drv.so for arm" found sites like this:

http://www.openmamba.org/distribution/distromatic.html?tag=devel&pkg=xorg-drv-input-evtouch.arm
[Desire HD Android Development] liljom:
no, there's no one, but there is a evdev_drv.so

but here is the input folder:

http://www.multiupload.com/ZYU2DLW0F8
[Desire HD Android Development] bergfex:
we should try to add the tslib_drv.so and the synaptics_drv.so seems to be bigger than ours....
[Desire HD Android Development] torsrex:
Does this help?

http://packages.debian.org/lenny/arm/xserver-xorg-input-evtouch/filelist

Or this?

http://packages.debian.org/lenny/arm/xserver-xorg-input-evtouch/download
[Desire HD Android Development] liljom:
I'm not a dev, but I think it does
[Desire HD Android Development] zFr3eak:
ok i found the problem why the system don't boot and get reboots when i flash it in recovery. it's to big. but when i remove busybox it dont work because the kernel can't detect the init. so we have to find a solution to make the boot.img 1 mb smaller. any idea?
[Desire HD Android Development] Ghaztehschmexeh:
Well, I'm going to try and cross-compile it myself anyway.
[Desire HD Android Development] Jhinta:
make more modules like sound wifi lan and so on you .

also ,, mutiboot is possible i have flash it my self (DREAM) <- but cant find the image.

somthing like-->

load kernel --> load initrd --> choice witch partition (vol +- ) - run init --->

recovery android or linux possible
[Desire HD Android Development] bergfex:
Sounds quit possible if the all work with the same kernel.
[Desire HD Android Development] Ghaztehschmexeh:
When cross-compiling, what processor type should I be using? ARM720T, ARM920T, ARM926T or ARM1020?

I'm guessing ARM720T because that's ARM7. Didn't even realise there was ARM10.

Edit:

Wait:

"ARM11 is an ARM architecture 32-bit RISC microprocessor family which introduced the ARMv6 architectural additions."

Oh man idk.

Then again I might be using an out of date ARM patch...

Edit:

Alright, I'm downloading the most recent linux kernel and ARM patch, I'll see how it goes.

Right, no ARM patch for most recent version, will be using 2.6.
[Desire HD Android Development] Ghaztehschmexeh:
grrrrrrr. I can't seem to get these to go together. Someone please tell me one of those processor types is the correct one.

Edit: HER A DERP. The linux kernel doesn't need patching since 2.6.0-test2. Okay! Well time to continue!

Edit: Right, the latest kernel has indeed got ARMv7 support. My current problem is that the guide I am using (this is my first time compiling a kernel) wants me to run "make dep". This then runs me through all of the kernel config options one by one... I don't think that's what is supposed to happen.

Edit: Right, going to see if I can get an oldconfig from my phone and compile with that. Either that, or enter through the wwwhhhhhhoooooole thing : D

Edit: Okay actually I am using make ARCH=arm with a default config instead, but I'm not sure which to use yet.
[Desire HD Android Development] torsrex:
Okay, after a whole LOT of googling, I found out that the processor is an ARM720T or an ARM920T.
[Desire HD Android Development] Ghaztehschmexeh:
No, it's not I'm afraid. After using a more update kernel I found that ARMv7 is separate. I've got that down, my current problem is the processor family defconfig to use to configure the kernel for cross-compiling. I'm not sure what to use. Basically I need to configure the kernel; I need a config file - I'm not answering ~1300 questions by hand! And when I tried one that seemed right, I have a generic-asm not arm-asm. Once I get this sorted it'll just be a case of compiling gcc for ARM, and then using that to recompile the driver.
[Desire HD Android Development] Ghaztehschmexeh:
Hmmm, just pulled out config.gz from the ubuntu running on my DHD, let's give this a go...

... it's 9am here and I have yet to sleep ...
[Desire HD Android Development] EmptyArea:
Crazy all nighters FTW!!

Swyped on transparent XDA app.

Get cape. Wear cape. Fly!
[Desire HD Android Development] Ghaztehschmexeh:
Indeed!

Ugh, the config file seems to have worked, but I still end up with an asm-generic, not asm-arm. And I guess it's this that's making gcc configure for i686 and not ARM, even though I tell it to configure for ARM. Blech, maybe I should sleep.
[Desire HD Android Development] bergfex:
Our SoC uses a ARM Cortex A8 Processor -> which meens ARM architecture ARMv7-A

For compiling a kernel for the DHD you should use arm-eabi-4.4.0 or newer (arm-eabi-gcc). This gcc is for ARMv7-A and can make use of the NEON core a SMD unit we have (like SSE on the PC) for example.

arm-eabi-4.4.0 comes with the Android sources form AOSP, Andriod NDK or with CM sources (not with Android SDK).

(Beware if you use Android sources newer then froyo branch you will need 64bit ubuntu)

Getting arm-ebi-4.4.0:

1)Prepare build inverment

http://source.android.com/source/initializing.html

2)Get android sources

http://source.android.com/source/downloading.html

3)make Generic Build

http://source.android.com/source/building.html

Before making the generic build i will recomand to modifing the following lines in tools/mkbootimg/bootimg.h

hdr.kernel_addr = 0x04008000;
hdr.ramdisk_addr = 0x05000000;
hdr.second_addr = 0x04F00000;
hdr.tags_addr = 0x04000100;

Then you will also get a working mkbootimg for the DHD

The .config you have pulled should be fine.

But you should use kernel sources form there:

http://xdaforums.com/showthread.php?t=835608&highlight=boot.img

But the git link has a mistake it should be:

https://github.com/BuzzBumbleBee/htc-kernel-ace

use this as tutorial:

http://wiki.cyanogenmod.com/index.php?title=Building_Kernel_from_source

PS: Cross compiling the evtouch_drv.so has NOTHING to do with the kernel.

That is not a kernel driver. It is a driver that laies between the kernel driver (that is already working (try touch during booting)) and xorg.
[Desire HD Android Development] bergfex:
Here comes the evtouch_drv.so for arm and everything else appending we need.

All the thanks goes to torsrex!!

The files are from his link:

http://packages.debian.org/lenny/arm...touch/download

file evtouch_drv.so
/home/patrick/Desktop/evtouch_drv.so: ELF 32-bit LSB shared object, ARM, version 1 (SYSV), dynamically linked, not stripped

I hope this will work!
[Desire HD Android Development] bergfex:
The "/var/log/Xorg.0.log" log file shows that the /dev/intput/event 1 is not "connected" to a xorg. We have to find out why.

[ 66.478] (II) config/udev: Adding input device synaptics-rmi-touchscreen (/dev/input/event1)

[ 66.478] (II) No input driver/identifier specified (ignoring)

The thierd line of the log file has to look like the followin otherwise you are looking to an old log file from the htc hd2

[ 64.682] Current Operating System: Linux htcleo 2.6.32.35_BUZZ_SENSE_1.3.8.3_OC/UV #20 PREEMPT Sun Apr 24 20:05:22 EEST 2011 armv7l
[Desire HD Android Development] Ghaztehschmexeh:
thanks a lot! I realise it isn't, but the tutorial I was following said I needed to compile a kernel for the cross-compiling toolchain.
[Desire HD Android Development] Ghaztehschmexeh:
Do we only need the evtouch_drv.so?
[Desire HD Android Development] bergfex:
Maybe we had to add a line in the 69-touchscreen.rules
[Desire HD Android Development] Jhinta:
i still dont have any luck with it , but do you know the way to get adb internet working , maby we can install tslib
[Desire HD Android Development] Ghaztehschmexeh:
Can't we push push the required package to the device and install it without a connection? Also leedroid beat us to this: here.
[Desire HD Android Development] Jhinta:
please do a wiki about chroot and native what leedroid have is chroot we are running it native ,

and yes we can install files in chroot, i will try to install tslib maby this will help.
[Desire HD Android Development] Ghaztehschmexeh:
Ah yes sorry, I didn't actually read the post at the time :P I can see that it's chroot now. Sweet, this means we should continue.
[Desire HD Android Development] EmptyArea:
Yumm ubuntu 11.04

Swyped on transparent XDA app.

Get cape. Wear cape. Fly!
[Desire HD Android Development] Ghaztehschmexeh:
I just put that on for download a second ago : D Although I'm upset that it looks like it doesn't come with gnome 3.0 (based on the beta).
[Desire HD Android Development] bergfex:
About ubuntu 11.04, remember we are using an ARM CPU, so we need a Ubuntu for ARM. You can use rootstock to build your own ubuntu image for ARM. I don't know if rootstock supports ubunutu 11.04 yet.

https://wiki.ubuntu.com/ARM/RootfsFromScratch
[Desire HD Android Development] bergfex:
tslib sources are at:

svn://svn.berlios.de/tslib/trunk/tslib

Ceck out:

"svn co svn://svn.berlios.de/tslib/trunk/tslib"

or with the svn tool of your choice (tutoris svn for windows)

http://linux-dvbh.blogspot.com/2006/12/tslib-download-and-cross-compile-for.html

The how to install section is very interesting!!!

Pre compiled:
[Desire HD Android Development] EmptyArea:
I haven't looked at the beta but I read its got Unity, but you can choose Ubuntu. Classic & you get Gnome

Swyped on transparent XDA app.

Get cape. Wear cape. Fly!
[Desire HD Android Development] torsrex:
This guy got the touchscreen working on the nexus s: http://xdaforums.com/showpost.php?p=12340794&postcount=28

(From this thread: http://xdaforums.com/showthread.php?t=907760 )

Can we use some of the work he did to get it to work on our desire HD?
[Desire HD Android Development] zFr3eak:
looks interesting but the problem will be that the config of the nexus s is most different between ours.
[Desire HD Android Development] torsrex:
This is a setup for arm (archos10) https://wiki.kubuntu.org/ARM/Archos101it

Maybe this config will work?
[Desire HD Android Development] bergfex:
I got a "nearly" working touchscreen!!! :)

The touchscreen works, but is not calibrated.

I get it working with following /etc/X11/xorg.conf

Section "Monitor"
Identifier "Monitor0"
Mode "480x800"
DotClock 0
HTimings 480 480 480 480
VTimings 800 800 800 800
Flags "-HSync" "-VSync"
EndMode
EndSection

Section "Device"
Identifier "fbdev"
Driver "fbdev"
Option "ShadowFB" "on"
Option "Rotate" "CW"
Option "RandRRotation" "true"
EndSection

Section "Screen"
Identifier "Framebuffer"
Device "fbdev"
Monitor "Monitor"
DefaultFbBpp 16
SubSection "Display"
Depth 16
Modes "480x800"
EndSubSection
EndSection

Section "Screen"
Identifier "480x800x16"
Device "fbdev"
Monitor "Monitor"
DefaultFbBpp 16
SubSection "Display"
Depth 16
Modes "480x800"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Builtin Default Layout"
Screen "Framebuffer"
InputDevice "touchscreen" "CorePointer"
InputDevice "Keyboard" "CoreKeyboard"
InputDevice "dummy"
EndSection

Section "InputDevice"
Identifier "touchscreen"
Driver "evdev"
Option "Device" "/dev/input/event1"
Option "DeviceName" "touchscreen"
Option "Emulate3Buttons" "false"
Option "SendCoreEvents" "On"
EndSection

Section "InputDevice"
Identifier "dummy"
Driver "void"
Option "Device" "/dev/input/mice"
EndSection

Section "InputDevice"
Identifier "Keyboard"
Driver "kbd"
Option "XkbLayout" "en_US"
EndSection

and with the files from tslib-0.0.4-5-arm.zip, that I have posted earlier.

Thanks to torsrex and his last link!!!

So let's calibrate the touch now! ;)
[Desire HD Android Development] bergfex:
Maybe we can find a precomplied for ARM version of "ts_calibrate".

Or we can configur it directly in the xorg.conf.

Or we find out you a /usr/etc/pointercal must look like (this file will be generated by "ts_calibrate")

Or we cross compile "ts_calibrate"

http://linux-dvbh.blogspot.com/2006/12/tslib-download-and-cross-compile-for.html
[Desire HD Android Development] Ghaztehschmexeh:
I was thinking, would it be possible to just compile it on the device itself rather than creating a cross-compiling tool-chain? Although I have yet to look at that arm version of gcc.
[Desire HD Android Development] bergfex:
some links to the cross compile results from Duncaen (he has to less posts for posting in the dev section)

http://duncano.de/tslib_build.tar.gz

http://duncano.de/tslib_crosscompiled.tar.gz
[Desire HD Android Development] bergfex:
Seems like the tslib is still not connected with our kernel touch driver.

Why are

/sys/devices/virtual/input/input1/vendor

/sys/devices/virtual/input/input1/product

both "0000"?

Edit: It's the same on an Nexus S

Maybe we should modify our kernel, so that this shows involve values.

Jhinta can you give it a try, I don't have access to a kernel build envirment during the weekend.
[Desire HD Android Development] torsrex:
Great that the touch screen is finally working (to some point)! :D

I don't know how to build kernels, but I do know how to google, glad my links helped out. ;)

Keep up the awesome work!
[Desire HD Android Development] Jhinta:
Tonight i got some time , good that tslib is working
[Desire HD Android Development] Jhinta:
config sould be added /root/.bashrc or ~/.bashr

<- but when running test , and dont know if they are needed

No raw modules loaded.

ts_config: Success

export TSLIB_CONSOLEDEVICE=none

export TSLIB_FBDEVICE=/dev/fb0

export TSLIB_TSDEVICE=/dev/input/event1

export TSLIB_CALIBFILE=/etc/pointercal

export TSLIB_CONFFILE=/etc/ts.conf

export TSLIB_PLUGINDIR=/usr/lib/ts

Also you zip dir is not correct sould be /usr/lib/ts

pointercal wil be made when one we have run ts_calibrate.

also when you have time build it with debugging support and witch command was it compiled with? or how did you compiled it , iḿ getting errors
[Desire HD Android Development] bergfex:
The tslib was crosscompiled by Duncaen a new user, who isn't allowed to post in the dev section. I just post the link to his result
[Desire HD Android Development] Immorten:
Bump! Any updates on this? :D
[Desire HD Android Development] bergfex:
Yes! I get a working touchscreen today! :)

I now using the multitouch driver instead of tslib or evdev.

The axis are interchanged at the moment but the won't be to hard to fix.

Thanks to Jhinta for the hard work on this and to figure out that the problem is the multitouch!

How to get it working:

download xf86-input-multitouch.arml.dep on the pc

put the multitouch_drv.so to /usr/lib/xorg/modules/input

change the following line in /etc/X11/xorg.conf (see post 138)

Driver "evdev"

to

Driver "multitouch"
[Desire HD Android Development] bergfex:
Here is an helpfull PN i received today:
[Desire HD Android Development] Jhinta:
So i was trying to shut down till i got you pm and post , well i thing iḿ not going to sleep just yet . grade job ad fixing this , now to get wifi and 3g working.

i did a insmod on wfif so but didnt help , any sugestion on this?
[Desire HD Android Development] zFr3eak:
wow great job will try it today definitly. :)
[Desire HD Android Development] bergfex:
Attention!

Ubuntu auto mounts all Partitions of the DHD including boot and recovery Partitions.

Touching this Partitions will BRICK your phone.

Needs fixing! ;)
[Desire HD Android Development] bergfex:
There is something with firmware file, I have to find the link again.

We need the .ko files and some firmware files.

http://htc-linux.org/wiki/index.php?title=LeoWifi
[Desire HD Android Development] zFr3eak:
the mount progress is normaly by booting. could it possible that the fail is in the boot.img?
[Desire HD Android Development] Jhinta:
its not a error i just has to be removed to disabled it
[Desire HD Android Development] zFr3eak:
yes but this is in the boot.img right?
[Desire HD Android Development] Jhinta:
Ramdisk that is in bootimg
[Desire HD Android Development] bergfex:
Yes it's in the boot.img ramdisk at /bin/MAKEDEVS.
[Desire HD Android Development] torsrex:
How is this project going? Is the touch screen finally calibrated?
[Desire HD Android Development] bergfex:
I have uploaded my actual rootfs and two new boot.img in the "easy to use.zip in the first post.

The touch pad driver has still interchanged aches.

The seconde boot.img should have usb host support instead of adb.

The needed *.ko are under /lib/modules.

The loadKernelModules under /etc/init.d should load this modules, but it does not.

So I don't have managed to get usb host support on this, yet.

I hope this give you some new things to play with.
[Desire HD Android Development] torsrex:
just in case you didn't know, you can run linux commands from the adb shell...
[Desire HD Android Development] zFr3eak:
oh nice thanks. :)
[Desire HD Android Development] Ghaztehschmexeh:
you need busybox installed though. Although most ROMs include this. Obviously running ubuntu means you don't need busybox though.
[Desire HD Android Development] zFr3eak:
you need busybox anyway. ;)
[Desire HD Android Development] torsrex:
is this the wifi module? http://android.git.kernel.org/?p=pl...7;hb=f427424c414886903e4ad654c143c8ce6ec10e3c