• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.

Inverted Touchscreen

5 posts in this topic

Posted

Hello guys,

I noticed a weird bug I am having with my phone.

Its the GSM variant.

I am/was currently using the rom in the signature, MoDaCo Ir6/preIr7

I wanted to try out the new KANG's, so went into CWM, wiped everything, installed.

Following bug: The touchscreen is mirrored/flipped vertically, that means if I want to press the "Next" button in the Android Installation wizard in the bottom right corner, I have to touch into "nothing" in the top right.

Thinking this was due to rom, I flashed bigxie's Stock Rooted Rom. Same there.

Restoring my MoDaCo ROM would repair everything again.

Then I went to try googles STOCK images here: http://code.google.c...ages.html#yakju

I flashed 4.0.2 (ICL53F) using fastboot.

And with the STOCK Image, I had the very same problem.

Flashing back to stock 4.0.1 (ITL41F): everything fine again.

Just did:

Hard reset

Flashed Stock ITL41F via fastboot

Rebootet several times, no update still

Flashed Stock ICL53F via fastboot

And made a pictureof the problem happening again:

L0Wml.jpg

Any ideas?

Please help me :(

0

Share this post


Link to post
Share on other sites

Posted (edited)

If I use USB OTG the mouse moves correctly, no inverted Y axis there.

logcat events which mention touchscreen:

I/EventHub(  194): New device: id=6, fd=140, path='/dev/input/event1', name='Melfas MMSxxx Touchscreen', classes=0x14, configuration='/system/usr/idc/Melfas_MMSxxx_Touchscreen.idc', keyLayout='', keyCharacterMap='', builtinKeyboard=false

I/InputReader(  194):   Touch device 'Melfas MMSxxx Touchscreen' could not query the properties of its associated display 0.  The device will be inoperable until the display size becomes available.

I/InputReader(  194): Device added: id=6, name='Melfas MMSxxx Touchscreen', sources=0x00001002

[...]


I/InputReader(  194): Device reconfigured: id=6, name='Melfas MMSxxx Touchscreen', surface size is now 720x1280, mode is 1

[...]


I/Pointer (  194): Input Device 0: tuna-gpio-keypad

I/Pointer (  194):   Keyboard Type: non-alphabetic

I/Pointer (  194):   Sources: 0x101 ( keyboard )

I/Pointer (  194): Input Device 5: Tuna Headset Jack

I/Pointer (  194):   Keyboard Type: none

I/Pointer (  194):   Sources: 0x80000000 ( )

I/Pointer (  194): Input Device 6: Melfas MMSxxx Touchscreen

I/Pointer (  194):   Keyboard Type: none

I/Pointer (  194):   Sources: 0x1002 ( touchscreen )

I/Pointer (  194): 	AXIS_X: source=0x1002 min=0.0 max=719.0014 flat=0.0 fuzz=0.99861306

I/Pointer (  194): 	AXIS_Y: source=0x1002 min=0.0 max=1279.0007 flat=0.0 fuzz=0.99921936

I/Pointer (  194): 	AXIS_PRESSURE: source=0x1002 min=0.0 max=1.0 flat=0.0 fuzz=0.0

I/Pointer (  194): 	AXIS_SIZE: source=0x1002 min=0.0 max=1.0 flat=0.0 fuzz=0.0

I/Pointer (  194): 	AXIS_TOUCH_MAJOR: source=0x1002 min=0.0 max=1468.6047 flat=0.0 fuzz=0.0

I/Pointer (  194): 	AXIS_TOUCH_MINOR: source=0x1002 min=0.0 max=1468.6047 flat=0.0 fuzz=0.0

I/Pointer (  194): 	AXIS_TOOL_MAJOR: source=0x1002 min=0.0 max=1468.6047 flat=0.0 fuzz=0.0

I/Pointer (  194): 	AXIS_TOOL_MINOR: source=0x1002 min=0.0 max=1468.6047 flat=0.0 fuzz=0.0

If you have ANY idea whom I could write (I already twittered Paul, no answer though :( I also asked Jean-Baptiste Queru, but he answered: "@agormog Nope, no idea, sorry, I have very little visibility over what those retail builds." Shall I try to RMA? Please If you have ANY idea try to help me, I am really desperate Edit:
uid=0 gid=0@android:/ # cat /system/usr/idc/Melfas_MMSxxx_Touchscreen.idc

# Copyright (C) 2011 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 Tuna touch screen.

#


# Basic Parameters

touch.deviceType = touchScreen

touch.orientationAware = 1


# Size

touch.size.calibration = diameter

touch.size.scale = 10

touch.size.bias = 0

touch.size.isSummed = 0


# Pressure

# Driver reports signal strength as pressure.

#

# A normal thumb touch typically registers about 200 signal strength

# units although we don't expect these values to be accurate.

touch.pressure.calibration = amplitude

touch.pressure.scale = 0.005


# Orientation

touch.orientation.calibration = none

Edited by agor
0

Share this post


Link to post
Share on other sites

Posted

My config file is identical to yours.

I suggest re-flashing the stock image that works and then getting the OTA update to 4.0.3 to see what happens. If that's broken then get a replacement handset.

0

Share this post


Link to post
Share on other sites

Posted

So, I just came back from exchanging my device at the store.

To exclude user errors, which would be the safest way to get to the newest MoDaCo Kitchen.

I would:

Superboot

Install ROM Manager

Flash CWM Recovery

and Update from ZIP, but this is what I did last time without success.

Greets

0

Share this post


Link to post
Share on other sites

Posted (edited)

So, I just came back from exchanging my device at the store.

To exclude user errors, which would be the safest way to get to the newest MoDaCo Kitchen.

I would:

Superboot

Install ROM Manager

Flash CWM Recovery

and Update from ZIP, but this is what I did last time without success.

Greets

Once you've installed CWM do a nandroid backup BEFORE you flash MCR so you can restore if the next step doesn't work...

Edited by djmcnz
1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.