yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] Smokeey:
:| the calibration is.half an.inch.off

Lol
[Droid Incredible Android Development] twistedumbrella:
Did you try the tscalibrate stuff I posted up before to fix calibration?
[Droid Incredible Android Development] Smokeey:
will do now :D
[Droid Incredible Android Development] Unholyfire:
Dang, just synced about 2 hours ago to his git lol. I'll do it again and work the calibration also.
[Droid Incredible Android Development] zoomy942:
I could hug each and every one of you
[Droid Incredible Android Development] twistedumbrella:
Sorry I misplaced the link. It gets hard keeping on stuff miles from my computer, but I can be more specific later tonight.
[Droid Incredible Android Development] renzo.olivares:
just wanted to tell u guys about this

http://galnetmiui.co.uk/landing/ics-builds/

miui builds with ics framework
[Droid Incredible Android Development] GRZLA:
Both real miui porters for the US has dubbed those poor build.prop edits.
[Droid Incredible Android Development] renzo.olivares:
ahh damn......lol i just finished downloading...
[Droid Incredible Android Development] ZealotOnAStick:
Yeah, I posted the same thing much earlier in either this thread or maybe the SDK porting thread.

Disappointing. I kinda feel outright lied to.

Sorry if this is slightly off-topicish.
[Droid Incredible Android Development] Unholyfire:
IRONMatt said: r2, just so you know, you can easily add the touchscreen home/back/menu buttons

by adding the following to your config.xml in the device overlay

("device"/overlay/frameworks/base/core/res/res/values/config.xml)

<bool name="config_showNavigationBar">true</bool>

it is really helpful when stuck with pointer mode and capacitive keys not functioning

Me: I'm building with this change right now.

EDIT: This is killing me, I'm running my build on a VirtualBox Ubuntu install guested on my mid-range PC. Gonna also setup my Blade-Server and see if it finishes before this VBox does lol.
[Droid Incredible Android Development] Unholyfire:
I'm trying to estimate the remaining time on my build.

[Q] Anyone know the common size range of your "out/target/product/inc/" folder when the build has completed?

I did not notate mine when I did the full_maguro-eng build the other day. And I've wiped that working_directory since then.

I have my blade installing ubuntu right now (splitting the HDD takes some time since I'm leaving my XP install for Minecraft Server on the same disk LOL).
[Droid Incredible Android Development] jermaine151:
Mine was:

6.5G	./inc
[Droid Incredible Android Development] Unholyfire:
Oh dear lord. OK I'm killing this vbox and gonna stick with letting my blade do the builds lol.
[Droid Incredible Android Development] linuxmotion:
The requirements that jbqueru posted says 20GB for one build and ~50 for the 3 builds in AOSP.
[Droid Incredible Android Development] Unholyfire:
Yup, knew I need a chunk of hdd for all the source. Just didn't realize the build output was so big. All that for a ~200MB ROM lol.
[Droid Incredible Android Development] dyetheskin:
never understood why such a massive amount of data just for a tiny aosp rom
[Droid Incredible Android Development] jermaine151:
LOL! Only 100MB rom once you put the system files and boot.img in a zip. :)
[Droid Incredible Android Development] Unholyfire:
It's like going to a buffet. You're offered everything, but you're likely only gonna eat ~5%.

---------- Post added at 11:03 AM ---------- Previous post was at 10:53 AM ----------

Ok. I'm using the OMX git that r2doesinc has up. I've just recreated my entire OS/build-environment on my blade server. I've sync'd the google repo, added r2doesinc's commits, and kicked off the build.

Now I'm getting this pretty quick:

build/core/base_rules.mk:166:
*** packages/providers/ContactsProvider/loc_api/libloc_api:
MODULE.TARGET.SHARED_LIBRARIES.gps.inc
already defined by hardware/qcom/gps/loc_api/libloc_api. Stop.

I was not getting this error when I attempted the build on my vbox last night. And from what I can tell, r2 hasn't made any new commits since then.

Anyone got a suggestion for this one? Should I just comment out the line for the shared library in contactsprovider? And allow the qcom definition stick?
[Droid Incredible Android Development] twistedumbrella:
In my case I had to port the gingerbread gps, but mine also uses 5000 which was not an option in iCS.
[Droid Incredible Android Development] jermaine151:
Is your Thunderbolt build booting Twisted?
[Droid Incredible Android Development] Unholyfire:
Yea, I'm just trying to figure out why my identical source structure from one PC (that was in build process and moving along with no errors for 3 hours), to another PC, is now throwing errors right away.

Like I said, I'm pretty confident I grabbed the same commits R2 posted yesterday, so it should have just kicked off like the one last night did :confused:

I'm gonna keep digging at it, got a few errands to run first though. Will hop back at it in a few hours.
[Droid Incredible Android Development] twistedumbrella:
I had the same happen with audio. Fixed it in one build, cloned it and both broke...
[Droid Incredible Android Development] GRZLA:
r2doesinc just posted a new build that has the touchscreen SORT OF working. Touches register half an inch higher than they are supposed to.

I'm sure r2doesinc doesn't want me direct linking to his work but here is a link to the thread he is posting his work in.

http://rootzwiki.com/topic/9881-icsomx-preview/
[Droid Incredible Android Development] linuxmotion:
Its cause the intermediate files. About a gig of intermediate files turns into like 10mb of rom files. Its just the way it works.

Though the rom is only about 150mb the libraries that the rom requires take up almost all of it.
[Droid Incredible Android Development] Unholyfire:
Since I'm new to git and repo, I wasn't aware that it wouldnt sync my previous modified WORKING_DIRECTORY with R2's manifest.

So, doing a full sync with his manifest now... 6.5GB downloads later, I'll be working on this once again :p Off to run errands for now.
[Droid Incredible Android Development] ithrewitontheground:
Are you saying my link is botched? It takes you right to the main thread, I figured people would look through it to find the latest work/updates.
[Droid Incredible Android Development] GRZLA:
I was saying the link the OP was botched when I posted this, but I changed the post and linked to the OP instead now. I flashed the build and it works albeit not very well as it is still in alpha. Has two finger mode similar to the SDK build that we had going for a few days. We had a guy who was working on tweaking our driver for the touch screen. Haven't seen him post in here though.

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

This is the thread he made regarding the touch screen stuff, maybe there is something useful in there?
[Droid Incredible Android Development] dyetheskin:
I'd like to learn how to do this,point to a guide?
[Droid Incredible Android Development] Shelnutt2:
One thing you guys can do to cut down on the space taken for compilation is use pipes instead of pages. This also will speed up the build some :).

export CFLAGS="$CFLAGS -pipe"
export CXXFLAGS="$CXXFLAGS -pipe"
[Droid Incredible Android Development] Unholyfire:
Build from your own local source?

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

R2DoesInc has a pretty well put together public repo already going though.

If you'd like to contribute to his progress (or simply start where he's left off), when you get to the repo sync stage in the AOSP guide, use his repo manifest instead of the google one.

Dont use:
repo init -u https://android.googlesource.com/platform/manifest
repo sync

USE:
repo init -u git://github.com/OMX/manifest.git
repo sync

If you use/link anything from this repo, please make sure you give credit where credit is due (aka, credit all the contributors listed in the OMX git @ https://github.com/OMX )

Speaking of which; R2DoesInc and linuxmotion - Thanks for allowing me and others to see/use your progress!
[Droid Incredible Android Development] twistedumbrella:
What libaudio do you guys use? Is It the generic, 8, or 52?

Wondering before I sync this repo if it will be another dead end filled with working fixes that don't apply to my hardware...
[Droid Incredible Android Development] Shelnutt2:
We use the Generic libaudio
[Droid Incredible Android Development] Smokeey:
Koush just released his build of ICS for the Nexus S....any help tthere????
[Droid Incredible Android Development] GRZLA:
Doubtful, but our device is pretty similar hardware wise with the Nexus One.
[Droid Incredible Android Development] Smokeey:
Ya but doesn't the.Nexus have the.same (very similar) amtel touchscreen?
[Droid Incredible Android Development] GRZLA:
I don't know to tell you the truth, but that does raise a question for the devs in this. Since the INC comes in two forms of screens, does that have an impact on getting the touchscreen working or is the driver a one size fits all type deal on our device?
[Droid Incredible Android Development] Smokeey:
The initial SDK port's .idc came from a Nexus S port...it has the same touchscreen..
[Droid Incredible Android Development] haseeb1029:
I'm pretty sure the touchscreen is similar in hardware but different because the nexus S had a functional touchscreen on the sdk builds as well. So I'm sure something is different.
[Droid Incredible Android Development] Unholyfire:
Well I'm just having some crappy luck. I kicked off a build about 2 hours, walked away, and just came home to see the ubuntu linux kernel panic (caps and scroll lock leds on keyboard flashing). I think I assigned too many threads to the make. Time to try again with "make -j4" instead of -j8 :(

I'll let ya all know what I end up with in this cooking session :)
[Droid Incredible Android Development] Smokeey:
YA, the way Samsung's drivers sent and receive data was different.
[Droid Incredible Android Development] wdfowty:
make -j`grep 'processor' /proc/cpuinfo | wc -l`

That way, there's no guessing game.
[Droid Incredible Android Development] Smokeey:
Just almost bought a Rezound from Amazon Wireless, should I get it than swap it for the GN when it drops?
[Droid Incredible Android Development] GRZLA:
Those penny phones are for new subscribers only, upgrades won't work. On top of that, I don't think Verizon will let you trade it in when you bought it from Amazon. You might want to check their exchange policy.
[Droid Incredible Android Development] Smokeey:
Ya, I noticed that, then I also noticed that I could still get the phone $100 cheaper than from Verizon..
[Droid Incredible Android Development] civicsisedan:
You can add a line and get it for a penny.

Then change it to your line replace it with a dumb phone and drop data.

$10 X 24 = $240 + the penny.

Did that for my wife because she's not eligible.
[Droid Incredible Android Development] revthanki:
Ladies and gents, hi!

I'm a visitor from the HTC Desire forums. We have pretty much identical hardware to you, same mix of amoled and s-LCD screens, Adreno 200 graphics, same RAM etc.

We got a pretty functional build of ICS from source going. Basic functionality is there but we're missing some biggies: like Camera Sensors HW accelration . Making great progress. It may even be the case that HW Acceleration could be unlocked soon since the ZTE Blade guys might have cracked it (we have the same graphics chip).

You can find our work here: http://xdaforums.com/showthread.php?t=1355660 . You might find it helpful in getting a D inc ROM going. We child also use some extra skills in the quest to get this running perfectly.

---------- Post added at 12:31 AM ---------- Previous post was at 12:19 AM ----------

Just to make clear, I'm a tester, not a dev but we have some very good guys working away in IRC right now.
[Droid Incredible Android Development] tiny4579:
You guys have a github for the ROM? We could look at the changes necessary to make certain functions working and incorporate them for our device.
[Droid Incredible Android Development] revthanki:
As far as I know one is bring set up. I'm away from PC right now but best to ask Sandvold in the thread. There are so many similar devices out there with basic architectural similarities that it would be silly not to. We could then commit changes made by the CM team too.
[Droid Incredible Android Development] Smokeey:
Is there anyway you can link us the IRC or is it private?
[Droid Incredible Android Development] DiGi91:
#ics_desire_nexus_dev on #freenode it's not private.
[Droid Incredible Android Development] mjb413:
The eris devs have the touchscreen working well with gapps. The post has a link to their github and how they fixed touchscreen "For us, it was just adding an idc file to /system/usr/idc/ that gave us a full working touchscreen instead of just the pointer type. As for source, some of us working on the eris, heroc, and gsm hero have set up an account on github: https://github.com/TeamICS "

Full post here:

http://xdaforums.com/showpost.php?p=19588560&postcount=41
[Droid Incredible Android Development] GRZLA:
So you can confirm their fix works on our phone?
[Droid Incredible Android Development] tiny4579:
I should have been clearer in my post. It doesn't boot due to the error shown in my previous post so I can't confirm until I can get it booting.

I am trying a rebuild this morning before I go to sleep to see if the latest sync of the CM tree gets it working.
[Droid Incredible Android Development] tiny4579:
It boots but there's literally nothing on the screen. Improvements? Not really but I can peek into the system with adb at least now.
[Droid Incredible Android Development] GRZLA:
Have you tried jumping into the Desire's ICS IRC room? Those dudes are going at it non-stop to get their build running, so maybe they can give you a nudge in the right direction?
[Droid Incredible Android Development] frostincredible:
You could try using the idc file you think may fix it in r2's current build, just to see if it works.
[Droid Incredible Android Development] r2DoesInc:
not really active over here these days, but wanted to save you guys some wasted time.

im on vacation, so ics deving has gone pretty slow, but i did try pushing that idc file and im still in pointer mode. havent played around with it at all other than that.
[Droid Incredible Android Development] Alton (Halo 2):
Plz help us r2 :D
[Droid Incredible Android Development] russosv:
Hi All,

I'm new here & have been following the thread, and playing along at home.

I'm sure you are all 100 steps ahead of this, but in the off chance it helps someone out; I just compiled stock AOSP with r2DoesInc's GitHub changes (github.com/OMX) overlaid on top of the tree.

It compiled flawlessly in about ~30min (I have access to a shared 12-core machine w 25G RAM). The fact that there were no problems in compiling is definitely a testament to r2DoesInc's work-- nice job!!

File is here, in case anyone feels like trying it.

dl.dropbox.com/u/50612393/OMX_inc-ota-eng.svrusso1.zip

I haven't tried running it, yet so I don't know if it works-- but I just saw that he hasn't made any progress on it so I don't really expect much. :)
[Droid Incredible Android Development] tiny4579:
I've got it building with the CM forked tree (~45 min - intel i7, 6 GB ram) and cannot get any graphics on the latest build. I'm to the point where I say forget it as they'll figure it out soon or I'll get ICS on my Nexus.
[Droid Incredible Android Development] r2DoesInc:
i have builds posted on rootz...
[Droid Incredible Android Development] russosv:
I suspected that... some devs post stuff to their git and dont neccesarily keep up to date binaries on hand, so i thought maybe your git was more recent than your build. Wishful thinking :)
[Droid Incredible Android Development] zoomy942:
I'm looking for inc1 builds right now.

Got it.
[Droid Incredible Android Development] r2DoesInc:
Builds are compiled whenever I.commit.
[Droid Incredible Android Development] GRZLA:
Go enjoy your vacation!
[Droid Incredible Android Development] r2DoesInc:
so, since my inc has an atmel screen, i renamed it to atmel-touchscreen.idc, pushed it and it works, put only for the first touch. it also wont register the "untouch", the part where you lift you find up.
[Droid Incredible Android Development] r2DoesInc:
idk what your source is.

try forking my OMX stuff and merging in the mecha stuff. i have no issues -afaik- with surface flinger.

actually. sunds like your still building the msm7k-gralloc module.

see how i removed gralloc and libaudio here from the qsd8k build?

https://github.com/OMX/hardware_msm7k/commit/eca63936b82749c60c71aa31ace39e81d1d5fb32
[Droid Incredible Android Development] twistedumbrella:
Thanks, ill check it out. Part of the issue is I use msm7x30 and not the qsd8, but I do have one last test to run with some new edits.
[Droid Incredible Android Development] r2DoesInc:
you would modify the other line? the msm7k line not the qsd8k.
[Droid Incredible Android Development] twistedumbrella:
I wasn't intending to sound like I was an idiot, I just had the misunderstanding that more was done than simply disabling those parts. Alternate versions of qsd8 fixes modified the audio and such, so I guess I expected similar. I guess I will keep disabling those two in mind as a last resort. Thanks.
[Droid Incredible Android Development] r2DoesInc:
ya, theres multiple ways to fix it, but since gheres so much broken already, im doing the quickest fixes. once we have a build thats somewhat functional ill go back in and clean stuff up
[Droid Incredible Android Development] Smokeey:
Have you guys looked at the Desire files?

Anyway there touchscreen drivers can help us out?
[Droid Incredible Android Development] Unholyfire:
OK. So with qwerty.idc and qwerty2.idc removed. I added the atmel-touchscreen.idc with this code: (Thanks Twistedumbrella)

# Copyright (C) 2010 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

#
# Input Device Calibration File for the Crespo touch screen.
#
# These calibration values are derived from empirical measurements
# and may not be appropriate for use with other touch screens.
# Refer to the input device calibration documentation for more details.
#

# Basic Parameters
touch.deviceType = touchscreen
touch.orientationAware = 1

# Touch Size
touch.touchSize.calibration = pressure

# Tool Size
# Driver reports tool size as an area measurement.
#
# Based on empirical measurements, we estimate the size of the tool
# using size = sqrt(22 * rawToolArea + 0) * 9.2 + 0.
touch.toolSize.calibration = area
touch.toolSize.areaScale = 22
touch.toolSize.areaBias = 0
touch.toolSize.linearScale = 9.2
touch.toolSize.linearBias = 0
touch.toolSize.isSummed = 0

# Pressure
# Driver reports signal strength as pressure.
#
# A normal thumb touch typically registers about 100 signal strength
# units although we don't expect these values to be accurate.
touch.pressure.calibration = amplitude
touch.pressure.source = default
touch.pressure.scale = 0.01

# Size
touch.size.calibration = default

# Orientation
touch.orientation.calibration = none

And... Same result R2 got... but with new info :)

So, if you either allow the device to fall asleep, or reboot the device via adb, it will return to the lock screen. Now, you can drag the circle around and it follows with exact precision!!! But, it still odes not recognize the release event :(

---------- Post added 23rd November 2011 at 12:14 AM ---------- Previous post was 22nd November 2011 at 11:48 PM ----------

Logcat:

I/InputReader( 123): Touch device 'atmel-touchscreen' could not query the properties of its associated display 0. The device will be inoperable until the display size becomes available.

Further down:

I/InputReader( 123): Reconfiguring input devices. changes=0x00000004

I/InputReader( 123): Device reconfigured: id=4, name='atmel-touchscreen', surface size is now 480x800, mode is 1

---------- Post added at 12:59 AM ---------- Previous post was at 12:14 AM ----------

Just did tons of reading in other threads regarding this same issue. Looks like ya gotta modify the amtel.c file (touchscreen driver) in the kernel :( No sauce for me then, since I'm currently unable to get even R2's OMX build to complete (I'm still a noob!)

Regardless, this is what others did:
[Droid Incredible Android Development] tiny4579:
If I get mine to boot and display stuff then I can poke around in the kernel. It boots but won't display anything. I'm thinking its related to the gralloc that r2 mentioned.
[Droid Incredible Android Development] twistedumbrella:
I'll give that a shot using the nexus port and let you know what happens.

Edit: In the driver I use (atmel.c) it doesn't even find that line to disable it.
[Droid Incredible Android Development] r2DoesInc:
Use the kernel source posted on my rootzwiki thread. Its in like drivers/input/touchsxreen or something.
[Droid Incredible Android Development] Unholyfire:
In the CM kernel referenced in R2's rootswiki thread, there is one instance of this call: Lines 764 - 776

static void compatible_input_report(struct input_dev *idev,
struct atmel_finger_data *fdata, uint8_t press, uint8_t last)
{
if (!press)
input_report_abs(idev, ABS_MT_TOUCH_MAJOR, 0);
else {
input_report_abs(idev, ABS_MT_TOUCH_MAJOR, fdata->z);
input_report_abs(idev, ABS_MT_WIDTH_MAJOR, fdata->w);
input_report_abs(idev, ABS_MT_POSITION_X, fdata->x);
input_report_abs(idev, ABS_MT_POSITION_Y, fdata->y);
[COLOR="Magenta"]input_mt_sync[/COLOR](idev);
}
}

Yet, it's not the full expected line I was referred to.

I'm reviewing the whole driver file to see if I can spot any inconsistencies.

R2, this is the kernel you are using in your OMX build, correct?
[Droid Incredible Android Development] r2DoesInc:
ya. thats the current kernel in there.
[Droid Incredible Android Development] kozmo198:
Whats this ics thread for? Are you devs creating the official ics rom for the HTC incredible?
[Droid Incredible Android Development] Alton (Halo 2):
There working on it and I hope we get it soon
[Droid Incredible Android Development] Unholyfire:
I wish I could find a real reference to the amtel-touchscreen.idc file (all available configuration variables). Namely I wanna better understand the options for:

" touch.deviceType =

touchScreen

" (IE, is there a different statement available here for defining multitouch?)

" Tool Size "

Different devices make use of different calls/variables in this field... IE:

Crespo -

touch.toolSize.calibration = area
touch.toolSize.areaScale = 22
touch.toolSize.areaBias = 0
touch.toolSize.linearScale = 9.2
touch.toolSize.linearBias = 0
touch.toolSize.isSummed = 0

INC -

touch.toolSize.calibration = linear
touch.toolSize.linearScale = 10
touch.toolSize.linearBias = 160
touch.toolSize.isSummed = 1

But I remember reading in another Devices ICS thread that "touch.toolSize.calibration = linear" can no longer be used as of 4.0
[Droid Incredible Android Development] twistedumbrella:
That's actually what I ended up looking at. I tried commenting the last line but I didn't get to test it yet.
[Droid Incredible Android Development] twistedumbrella:
Check this out for the settings that you have to work with

http://xdaforums.com/showpost.php?p=18904688&postcount=116
[Droid Incredible Android Development] tiny4579:
I can't get the screen to display anything. Using a combo of CM plus some fixes from OMX. I want to just sync the whole OMX tree but it's not very repo-friendly.
[Droid Incredible Android Development] r2DoesInc:
lol the OMX repos work fine. ive had multiple people who dont know anything about how to build sync, compile, and boot no problem.

mkdir OMX ; cd OMX ; repo init -u git@github.com:OMX/manifest.git ; repo sync