yashsingh1/xdaforums huggingface dataset:
[XPERIA X10 General] fiscidtox:
It has been basically proven that it is hardware limitations....

The nexus one and the desire which all came or around the same time all have the exact same cross axis problem/behavior and they both have the clearpad 2000 digitizer, which the x10 also has. (some will argue this but friends in the electronics industry confirm it)
[XPERIA X10 General] OmegaRED^:
ok.. i get that..

Then why does the driver only update the output value's after your fingers move and not a passively as required for better dual touch and multi touch?

Cuz games would be much more bearable..
[XPERIA X10 General] fiscidtox:
No idea, I only do hardware/electrical stuff, don't know too much about drivers/firmware :P

I'm with you though, when playing games it can definitely be frustrating
[XPERIA X10 General] crx_ed9_2002:
2.3 Update is comming official by SE

http://www.sonyericsson.com/cws/support/phones/xperiax10?cc=de&lc=de

I'm sorry it's the German link to the News.

so in Short Words,

Androids 2.3 will be deliver at the end of the sec. quarder or on beginn of the third Quarder of the year 2011.

This update is only for phones WITHOUT Phonecontracts. This upgrade will deliver only by PC-Companion.

the Release Candidate Functions and Features are not given at this time. We will inform you and give you more information on short times to release.

so i hope it's brings the ligth in the Darkroom..
[XPERIA X10 General] a2ha:
hmmm... can't find any comparisons about 16k colors vs 16m colors with same screen's :(
[Wildfire General] jazzzy786:
When I start my phone in hboot bootloader screen it is showing S-ON at the top of the screen yet I was able to root it with unrevoked and flash it with custom rom Cyanogenmod 6.1. So what exactly does S-OFF actually allow you to do?
[Wildfire General] f0xy:
Flash recoveries on the fly, resize internal memory partitions. You need to search.
[Wildfire General] bx19:
S-OFF by xtc clip allows u not only to root but also has several advantages.

S-OFF in general by any method has advantages.

check those advantages here in post #3

http://xdaforums.com/showthread.php?t=1041530
[Galaxy Tab Q&A, Help & Troubleshooting] fishstick600:
I have been trying to flash the new v5 of voodoo but have been getting stuck at the samsung logo like a lot of people.. so i read pretty much the entire thread and saw people were having success using the new v3 good.zimage and then flashing v4 so i flashed it w/ success. After i flashed v3 my pc will no longer pick up the tablet ... i have no idea what to do because now i cant even revert to stock.. i really wanted to get the 1.4 kernal working, not to say v3 of voodoo isnt good, i just wanted to OC it.. ANY ideas would be greatly appreciated. 2nd question.. on the voodoo forum there is a link to ECO2 ext4 files.. What are those/what do they do/ and how do i apply them? assuming i can get my pc to recognize my tablet.

Note: i am not an advanced user and only have experience with heimdall and rsdlite.
[HTC Incredible S] vido.ardes:
Previous version of this post, kept for historical reasons:

I am sure everyone here wants to see CM7 hit this device. I am also sure that in our collective efforts, we can do it. At the moment, it is just me (or no one else is saying they are trying ;)) I basically want to try and get a team of people to crack the porting problem, because so far I am unable to do it on my own.

Finding information is proving difficult, and I just keep hitting dead ends. Is anyone willing to help? Has anyone ported a ROM from one device to another before? Can anyone point me towards information on how to start / debug?

As a community, this will get done a lot quicker, so if anyone can help please post here. If you idea of helping is posting "[I]I can help, what can I do / tell me what to do /give me something to do[/I]" then thanks, but no thanks.

[SIZE=3][B]Please keep this thread clear of chatter so it can be used for discussing the problem at hand.[/B][/SIZE]
[HTC Incredible S] knightrocker:
I have ported from the HTC Dream to the HTC Diamond ...

If you wish to get started the way i do it ... Take a cm build from the closest device ... Say the DHD ... And chuck the system.img into an official update zip or any other zip with a working boot.img etc ... Then try booting directly ... If it bootloops ... The first thing you should try is to replace /lib from a stock rom ...

This will get you to boot surely ... But if you manage to boot directly then keep the libs ... After that we need the appropriate libs extra things like the secondary cam that u can take from the stock rom ...

A more detailed way to do it would be to get the ported libs working by using logcat to see whats wrong and replace only the related libs from a stock rom ... Keeping stock libs will make performace related things such as battery in the same state as stock ... So it is best to keep the ported libs ...

I would have done this myself by now but i have a s-on devoce :-/

Anyway can you tell me whats wrong with your attempts? Where do you get stuck? Which device are u trying to port from?

EDIT: idon see why you hit dead ends if u port from a similar device it should be no problem to boot ... Heck ports from the dream to the bloody winmo diamond worked out of the box ... The dream libs worked fine ... Would be nice if u could chuck us a logcat ... Even if i cant figure it out ill ask neopeek ...hes a pro :) but idon think this will go that far ;)
[HTC Incredible S] vido.ardes:
I tried it the other way round, taking an ACE rom and chuckign the INC S kernel into it and i just got

format: format_ext3_device failed (-1) on /dev/block/mmcblk0p25

I will try what you said, it's a good starting point, thanks!

EDIT: Can't even get a boot loop :( Logcat just says exec '/system/bin/sh' failed: No such file or directory (2) which is annoyingly obscure...
[HTC Incredible S] knightrocker:
Hehe ... Good point ... U cant get a bootloop if u dont even start boot ... I admit ... U sure have a funky way of trying things out ... :D

EDIT: that logcat ... Did u get it with what i said or what u tried? O_o
[HTC Incredible S] vido.ardes:
Both gave me that result. Can't really find out what it means other than it couldn't mount the system partition, no idea why
[HTC Incredible S] knightrocker:
I think the problem comes earlier ... Look at what you have said ... That failed to format part ... I think it screwed up halfway and now its empty ... Have you compared the update script with the one from the dhd? You are porting from the dhd right? Its the best option ...
[HTC Incredible S] vido.ardes:
I use the same script I use for lpremix so I know the script is fine. Which is why I am stuck.
[HTC Incredible S] knightrocker:
Hmmm ... We need to narrow this down ... Try copiying in only /app /framework /media ... And also try using the older setup with the stock build.prop ... If u can boot this then the problem is in the rest ...

EDIT: did u also try different update scripts? Try using the dhd one as it is ... I think the problem is there might be a difference in the way the IS is partitioned compared to the dhd ... Cuz idon think we really have a mmc's upto 25 O_o
[HTC Incredible S] MarylandCookie:
Have you tried converting the Ace updater script to update script then changing the mount partitions to say from:

format("ext3", "EMMC", "/dev/block/mmcblk0p25");
format("ext3", "EMMC", "/dev/block/mmcblk0p27");
format("ext3", "EMMC", "/dev/block/mmcblk0p22");

to

format SYSTEM:
format CACHE:
format BOOT:

Then convert back?
[HTC Incredible S] knightrocker:
K bro i think ive got some thing ... In /system/etc there is a file called vold.fstab ... Please do a comparison ... There might be a difference there ... Check the cm one with stock ... Also compare the cm7 update script from ace and the update script from a lp remix ... Maybe you just need to change the partition name ... Also try removing those lines completely from the script you are using ... Chuck all the lines related to format...

EDIT: its getting a little late ... Its around 330 am now ... I think ill go to sleep ... Ill see if i can think up of anything else for u bro ... Gnite every1 :) -_-
[HTC Incredible S] Hawkysoft:
looks like u have the same prob as me bro
[HTC Incredible S] MarylandCookie:
As far as i know Desire HD is ext3 and IS/DS are ext4.

Try to change the partition information.

See my previous post.

Also here in your script you have a reference to /system/bin/sh which is probably missing from your rom.
[HTC Incredible S] Hawkysoft:
hmm didnt even read that, but yes it shud be 4 o.0 or is that why my script is fkin me up?

imma test 3 anyway...
[HTC Incredible S] knightrocker:
Im back from bed :P ... Maybe marylandcookie is right ... But where can that problem be? He is using the lpremix update script that usually works not the dhd script ... So why is it trying to chuck up ext3? Are u sure we are ext4?

@marylandcookie: do you have a nickname ... Ur name is real handfull to type out -_-

EDIT: do we even have a mmcblk025? The furthest ive seen is 4 or 5 ...
[HTC Incredible S] vido.ardes:
Ext3 works fine, but I will try ext4 anyway. It's us more likely to be a problem in the system files so I will check void.fstab file

The sh file is there, the system partition just isn't mounts properly
[HTC Incredible S] bl4ckluna:
it's too diffcult for me...but i believe we can
[HTC Incredible S] vido.ardes:
I'm not sure what you mean, I suggest you look at the partition table. It's differant from mtd blocks cause its nand, system is definately mmcblk025
[HTC Incredible S] knightrocker:
Really? Still not used to this whole nand partition thing :P

Much better with android itself :) have made any progress?
[HTC Incredible S] vido.ardes:
I won't today or until Tuesday as I am on holiday and away from a pc, but I will get back to it next week
[HTC Incredible S] knightrocker:
Ok then ... Ill see if i can think of something by then ...
[HTC Incredible S] madmaxx82:
Yipeee!!

I managed to get until the Cyanogenmod bootanimation :)

Then it loops..

I don't have time right now, but would really like to debug a little bit further, although I'm BY FAR really not capable of really porting that as I'm really a noob :D

IF noone else has gotten the IS to boot that far, maybe then someone of the real devs would continue?
[HTC Incredible S] knightrocker:
Hmmm ... Ill start work tomorrow ... Should be able to boot ...
[HTC Incredible S] vido.ardes:
I never even got that far to be honest, you should be able to get something useful out of the logcat if you are getting a boot anim
[HTC Incredible S] vido.ardes:
BTW I've got a beer waiting for anyone who can work out how to port the code to make the backlights on the hardware keys work... It's driving me nuts! It's in the power management section of services.jar, but it seems to be all over the shop
[HTC Incredible S] madmaxx82:
Hey ;)

I just booted into CM7 :)

I can use the homescreen and the launcher, everything looks really nice, but I don't have radio yet.

AND... :D NO backlights ;)

Update: the buttons do work however... really interesting that we have the same problem.

Is there a checklist somewhere I could use to check if things are working? (For later) Of course it would be a nice step forward if the radio worked :D
[HTC Incredible S] madmaxx82:
BTW: I compiled a kernel with ext4 support for the boot.img, but clockworkmod didn't support the fs. I then flashed the compiled clockworkmod 3.0.2.8, but still the same problem.

Does anyone know how to replace/rebuild the kernel inside clockworkmod recovery for the IS?
[HTC Incredible S] vido.ardes:
I have a list of libs worth moving over, will post tomorrow when I get to my work PC. Glad to hear you can boot into it though :D

I will also post a modified coy table to see if it builds, as I can't get it to compile :(
[HTC Incredible S] madmaxx82:
Thanks :) that would be great.

Either I'm missing a device or there's a problem with the init scripts.

Where do you have problems when you try to compile?
[HTC Incredible S] vido.ardes:
I really not sure, I don't get compiler errors but when I try and load it, I get nothing. Recovery flash log doesn't show anything out of the ordinary, but it just hangs at the splash and never gives out a logcat. I tried using a manual method to create a boot.img, dsixda's kitchen and koush's anykernel, no dice with any of them
[HTC Incredible S] madmaxx82:
You mean cm7 right? So you flash it but it hangs?

Did you compile everything from source and let it also build the boot.img?

Good morning btw ;)
[HTC Incredible S] vido.ardes:
Morning :D

Sorry I meant problems with compiling the kernel, not CM7. I haven't really given that a proper go yet, I thought it would be quick to fix the backlight issue on LPRemix but that has taken up a lot of my spare time :mad:

As promised, I have attached a modified CPU table and below is a list of files I think is worth porting. I basically looked at the vendor overlays for a few similar devices and hand picked some items

/system/bin/akmd
/system/bin/awb_camera
/system/bin/bma150_usr
/system/bin/htc_ebdlogd
/system/bin/logcat2
/system/bin/lsc_camera
/system/bin/rmt_storage
/system/bin/snd3254
/system/etc/AudioBTID.csv
/system/lib/egl/libEGL_adreno200.so
/system/lib/egl/libGLESv1_CM_adreno200.so
/system/lib/egl/libGLESv2_adreno200.so
/system/lib/egl/libq3dtools_adreno200.so
/system/lib/libaudio.so
/system/lib/libaudioalsa.so
/system/lib/libaudioeq.so
/system/lib/libcamera.so
/system/lib/libgemini.so
/system/lib/libgsl.so
/system/lib/libhtc_acoustic.so
/system/lib/libhtc_ril.so
/system/lib/libmmipl.so
/system/lib/libmmjpeg.so
/system/lib/liboemcamera.so
/system/lib/libposteffect.so
[HTC Incredible S] madmaxx82:
Thanks for posting. I'm using nearly the same list.

libaudioeq.so and snd3254 don't exist on my device though.

I omitted libaudioeq as I wasn't able to find something similar with just a little bit of reasoning :D

Instead of snd3254 I used snd8k where I'm not sure if it's really proprietary. I'm so happy that it's booting that I don't care about sound at the moment :D

If I get enough time today I'd like to look through the logcat more carefully to hopefully find the reason why there's no radio.

It would be really really awesome if you could get that kernel to boot ;) the first overclocking kernel for IS :)
[HTC Incredible S] wdfowty:
AFAIK, you can split a recovery.img into kernel/ramdisk by renaming it to boot.img and using dsixda's kitchen option #20 (split boot.img). Haven't tested though, just gathered from other sources. http://android-dls.com/wiki/index.p..._Images#Structure_of_boot_and_recovery_images
[HTC Incredible S] madmaxx82:
Thanks, I used that for unpacking boot.img but not for recovery yet. Will definately try it :)
[HTC Incredible S] wdfowty:
"snd*" and "sound*" binaries are proprietary IIRC

You can consult an extract-files script from CyanogenMod on their github, www.github.com/CyanogenMod

Just look at the closest device to Inc-S (probably Ace, as stated earlier), and you'll probably get a feel for what you'll need.
[HTC Incredible S] madmaxx82:
Thanks the list I'm using is actually from the ace.. just that I couldn't find any other libaudio* for replacing the libaudioeq. I'll look further for blobs, but now I'd really like to have radio.
[HTC Incredible S] vido.ardes:
If you want to post the compiled version or just posting the logcat it I don't mind taking a look as well. I am determined to get the kernel building and overclocked though :D
[HTC Incredible S] madmaxx82:
Ok, finally back from work.

Thank you, I'd like to post everything that could be of possible use to anyone wanting to port CM7 anyway. If there's ;) If it could help speed something up, great! Otherwise, it was fun ;) Seeing CM7 on the IS was really nice! I somehow felt at home :D

So please anyone who's interested and thinks that anything I did could be of some use, tell me what else I should upload.

Here's the logcat from boot where you'll love to see lots and lots of errors and the rom on rapidshare (sorry I didn't have time to upload it somewhere else yet)

Edit: BTW: I probably won't continue as this needs very much time and even more if you aren't experienced at all (like me :D )!

Edit2: I changed the filename, that noone jumping in straight from google flash this. since it's so alpha that it's omega :D

CyanogenMod7 for the IS which does boot (but not so much else): https://rapidshare.com/files/18202344/cm-7.1.0-RC0-LONG-BEFORE-ALPHA-Incredible-S.zip
[HTC Incredible S] vido.ardes:
Thanks, I'm downloading the ROM now and looking over the logcat. Did you build it from source or port it from another device?

I don't think it's as bad as you think, although it will be hard work getting the backlights working :s
[HTC Incredible S] madmaxx82:
Hi thanks ;)

I built it from source, with help of Makefiles and the prop. blobs list I adjusted from the DesireHD.

I didn't look through that logcat yet. I was just happy that it was booting :D

Previously it was extremely helpful though when I got far enough to get a bootloop I saw that it couldn't mount /data and was looping because of that..

It's really frustrating when it doesn't boot and you can't even get an adb connection. I tried enabling bootchart in hope it would work before adb, but didn't succeed.. and then I was just lucky to get a bit further ;)

I really hope you and others will get this thing done ;)
[HTC Incredible S] vido.ardes:
Might have been a little optimistic, no camera, no radio (bluetooth, wi fi or calls), no speaker, volume rocker doesn't work...

But it is booting, and that is a start. I will see what I can do ;)
[HTC Incredible S] madmaxx82:
BTW: I messed around to get product.device et.c. to match "vivo" (before build) as it's in the original build.prop. And then I realized that in ClockworkMod it's all "incs".. do you know and could explain to me why that's so?

Thanks!

Those terrible backlights ;)

BTW: When I compile the kernel myself, usb doesn't work. Doesn't that look like the kernel sources published by HTC are for a slightly different version than the one I'm running and so some more (proprietary, copied from my device) modules are failing to load? I used my config.gz from /proc.

I also tried to use your changes to the CPU table and disabled HTC PERFLOCK. But like you say, it hangs then :(

And those terrible button backlights :D
[HTC Incredible S] madmaxx82:
Hahaha yes, there isn't so much that works. But hey why need radio/wifi et.c., it's enough to see the CM logo and these wonderful notification bar toggles isn't it? ;)
[HTC Incredible S] vido.ardes:
Its incs in CM because I presume that's what koush set it up as when he created ClockworkMod. It should be vivo.

I got the radio recognised, but it still can't connect to the network.There is so little hardware working I must be missing something really fundamental...
[HTC Incredible S] madmaxx82:
That's great!

I think one should take a closer look at the init scripts.. I'm sure there's much wrong/missing, required permissions not set et.c.

Edit: when you compare the original init.rc wit hthe one from the "port", there's much missing. Didn't have time to look at it closer though.
[HTC Incredible S] vido.ardes:
Could you zip up your INCS source folder and post that? I don't think I can fix these problems on the compiled ROM, but I may be able to with the sources

Don't need the whole CM source, just what you have in your Incs folder ;)
[HTC Incredible S] madmaxx82:
Of course, here it is: https://rapidshare.com/files/164635561/incs.tar.gz

It's quite a mess, I hope it can help nontheless.

It's really great that you are spending your time on this! Hopefully you'll get some help. Doing that all alone is too much of work I think.

Have a nice evening!
[HTC Incredible S] timbo007up:
Ty alot madmaxx, im helping out atm, and your files are really helpfull, currently trying to build and debug everything :)

also in the same boat as you guys: first time building rom. But hope we can make something of it :)
[HTC Incredible S] madmaxx82:
Hey Timbo007up ;)

Thank you very much! And great that you are with us!! In fact you are with l0st.prophet for now ;) as I KNOW that when I start looking at it again, I can't stop it like the last days :D and I really have so much of work to do :(

That may sound dumb as you all do that in your spare time, but I'm so extremely inconsequent that I neglect everything else when I'm doing something like this which is much more fun than getting other things done ;)

BTW: don't you guys think we should use some sort of svn? I'm sure this project will take much time.. and it's so easy to mess something up and then forget what file that was.. also that way it would be much asier to work together..

In my opinion it might be better to take a close look at the init scripts first, since there's really much wrong with them! I just quickly fixed them up so it could boot and didn't pay really much attention. Didn't even look at them as a whole.

Before I pretty much used init.spade.rc that came from the ace with only very minor changes and it wouldn't boot because it couldn't mount /data.

I then copied the mounting part from the original init.vivo.rc (partition@emmc..) and it worked. Later I took a closer look at the top of the script and saw that originally I had forgotten to also change the mount options.. it was using nobarrier which doesn't exist for ext3 :D

So it might have booted without those changes from the original script.

Also the original htc script uses different events than the one from the repo for the ace.

For example there was no device mtd@misc 0460 radio diag which was executed on early-init. Also the original one uses "on EMMC" instead of "on fs". I don't remember exactly but if I used those events it wouldn't boot.

Booting with an unmodified init.rc + init.vivo.rc wasn't possible either. I'd get a bootloop or a freeze even before adbd starts..

So I get the idea that it's more important to fix up the init scripts as I didn't pay much attention to them (just quickly copied/changed some code and wasn't careful at all) and then think about what's wrong with the build process and which files/drivers/proprietaries are wrong/missing.. what do you think?

BTW: it was quite late yesterday and I had forgotten to tell you that I merged device-incs.mk with incs.mk (as it's the case with many other models in the repo).. so device-incs.mk is obsolete now.

Also I forgot to post my cyanogen_incs.mk. I'm sure you already created one yourself, but if not and for completeness, I have attached it to this post.

Sorry for the long post ;)

This will kick ass!!! :D
[HTC Incredible S] vido.ardes:
It's looking OK, I am in the process of going through the init files now. One small change, you need to change BOARD_EGL_CFG to incs and copy the files from ace. Probably doesn't make a difference to the build, but it's cleaner.

Also, poking around in the board config has finally let me work out what was wrong with my kernel, got wifi running now with a 1.8GHz OC! Smooth as you like, but unfortunately HTC broke the camera :mad: So I have to try and fix that as well.
[HTC Incredible S] madmaxx82:
Very nice!! And big congratulations to your oc kernel! The oc you accomplished is amazing!

You got wifi running in CM7?

May I ask what you changed?
[HTC Incredible S] vido.ardes:
Sorry, I was having trouble with wifi on stock with my kernel, not in CM7. I am going to try apply my kernel to CM7 now
[HTC Incredible S] eddycyf:
Following is my result... I'm porting it from ACE rom, not building from source, kernel is using MDJ V3.

Phone - able to make and receive call, but no sound

Mobile data - OK

Wifi - able to turn on and scan network.

Bluetooth - broken

Camera - broken
[HTC Incredible S] madmaxx82:
That's GREAT!!!

Thank you very much! We are much closer now :)

Now it would be nice if building from source would work as well, since some things will require that sooner or later.
[HTC Incredible S] vido.ardes:
Great news, well done! I agree building it from source wold be better, but a working port would be really nice to play with and could help us in building from source as well