yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] AxxPyrtlexx20:
Data is disabled by default so you gotta enable it and make sure that you're apn setting is set too
[One (M8) Android Development] mcwups1:
Such trickery.

Sprint M8 Converted HK 4.25.654.14
[One (M8) Android Development] AxxPyrtlexx20:
Its better this way on your data that's why we have it set like this
[One (M8) Android Development] AxxPyrtlexx20:
New build is up
[One (M8) Android Development] ckvisme:
Did you get data up?

If not... Grab a terminal emulator and type:

su

svc data enable

Then wait a few and.... Poof... That annoying little excitation point disappears from your status bar.
[One (M8) Android Development] AxxPyrtlexx20:
First check and see if you can enable it l, for some reason not showing up for sprint users
[One (M8) Android Development] ckvisme:
Yep, you were correct... No need for terminal commands... Lol, data toggle right Near the tip of settings menu ( and data is working great for me).

Cool build, I like that it's themed right out of the gate, look awesome.

Thx again ?

Sprint 4.25.651.14

2.8.6.x(MultiRom) TWRP

S-OFF
[One (M8) Android Development] Broodn:
I don't have any sound on this build. I did a clean install and I'm on the latest TWRP recovery
[One (M8) Android Development] ckvisme:
I don't either ...just thought it was something I flash earlier today..

---------- Post added at 09:14 PM ---------- Previous post was at 09:05 PM ----------

I'm not sure what's up.. I flashed a Slim build this morning that had bad audio issues.. Screeching and such (flashed To my internal partition/ multirom).. Then Tesla, now Validus...but none of my secondary roms have sound (well I can call on the phone and hear.. But no system sounds)... I deleted Tesla and restored Candy as internal.. Sound is fine on it...

I also tried flashing hk/bs switcher MOD.. No luck.. I think I'm going to have to re-flash my set ups.... Mmm

Let me know if you find something that corrects sound

TIA
[One (M8) Android Development] AxxPyrtlexx20:
Of course there's something wrong jeez cm breaking audio again
[One (M8) Android Development] ckvisme:
Lol, surprise surprise cm does it again...

BTW I got sound back on my sense rom and on my internal... But Tesla and Validus are fried... Time to start from scratch ?
[One (M8) Android Development] AxxPyrtlexx20:
Okay I'll work on a fix
[One (M8) Android Development] AxxPyrtlexx20:
Build is up
[Galaxy Note 4 Q&A, Help & Troubleshooting] mneu777:
Hi!

When play RR3 I see a bad screen effect, is for the screen resolution?

Any ideas?

Thanks!
[Galaxy Note 4 Q&A, Help & Troubleshooting] mneu777:
Now with Lollipop is fixed!
[Android Q&A, Help & Troubleshooting] hackwerk:
URGENT, PLEASE HELP:

I bought a replacement digitizer/glass for my Acer Liquid E3 / E380 as it has been broken (only the glass) for months now. It has a different chip but has the Acer brand on top.

Problem: I placed the new digitizer and all touch is REVERSED / MIRRORED! Up is down and down is up. So Y-Axis (or X?!) must be reversed now

PLEASE help me (asap) to do this! A lot of people replacing their glass have this problem on the internet, and a lot of fixes are available. From script.bin methods to running calibration apps or modding kernels and/or installing other drivers or as simple as echo 1 > /sys/modules/tpd_settings/parameters/tpd_mode_axis or something like that somewhere like that?!

It is impossible to use my phone now, but ADB is working fine. Anyone who can give me the solution to fix by ADB (or Recovery)??

Edit: [MENTION=1376601]cyclon1978[/MENTION] Is already helping me an awful LOT, in our big Acer E380 thread!
[Android Q&A, Help & Troubleshooting] cyclon1978:
Ok, so i need your mtk-tpd info for all three buttons like described in the other thread.

Should look like

<4>[10963.246322] (0)[77:mtk-tpd] cinfo->x[0] = 150, cinfo->y[0] = 1400, cinfo->p[0] = 2, point_num=1

That is my first button as an example.

The mtk-tpd cinfo debug is the raw touchpanel data, so it is generated prior to the y axis invert.

so the "edge coordinates" and button coordinates will help to make it perfect.
[Android Q&A, Help & Troubleshooting] cyclon1978:
So...

your button area is y=1 and x=90/330/627

your screen area is y=0 up to 1279

That is odd, how can i differ between button area and screen if both use same coords... can you recheck if thats really the case?

---------- Post added at 03:34 PM ---------- Previous post was at 03:25 PM ----------

http://d-h.st/cwYt

Now i check if y = 1 > buttons else area with y flipped.

buttons x/y are changed to your coords...
[Android Q&A, Help & Troubleshooting] cyclon1978:
ok, so the buttons should work anyway with the ast version.

i can only set an exact value for the button, so you have to decide which of the two x-values for every button is "easier" or more intuitive/more centered.

can you reach every y coordinate? they should be slightly off, if you enable the display of coordinates in info/debug menu you should be off around 10% of screen size in y axis.

or is y working correctly?
[Android Q&A, Help & Troubleshooting] hackwerk:
No, (so) this 4th kernel is a step back.

The height of every touch is still a tiny little off (1279 instead of 1259??) and when I now come below the screen, so INTO the button area, the pointer jumps to the TOP of the screen?!

All these posts and values are confusing me/us hahaha,

re-read my last (corrected) posts please

. Added preferred buttons too.

Ps. What do you think? Will I always have to use your customized kernel from now on? Also in other ROMs like CM 10.1?

Ps2. Will another ROM like CM 10.1 also need this customization, or can it work right away out of the box maybe?

Ps3. Maybe a good idea to post exactly WHAT you are doing/changing, and WHERE, so anyone (dev) can learn from this problem?
[Android Q&A, Help & Troubleshooting] cyclon1978:
http://d-h.st/PH0R

Now its button area 0-79

Screen area 80-1259.

Should be again off a little bit but better as before.

i still need to re- calculate (match 80-1259 to 0-1259 or something like that)

i will put the change to github when its done

you'll always need to use a kernel with this patch.

i need:

report if buttons are working

report if y axis is nearly correct (test on top, middle and bottom, should be differently off, try to descripe that)
[Android Q&A, Help & Troubleshooting] hackwerk:
Height is still a tiny bit off.

Pressing buttons again show a touch on the ultimate top of the screen.
[Android Q&A, Help & Troubleshooting] cyclon1978:
So.. do the buttons work never/sometimes?
[Android Q&A, Help & Troubleshooting] hackwerk:
No never. The touch is still generated (checking kmsg, same result as log in last posts), but it visually shows a touch on ultimate top of my screen ?! :confused:

(And height is a tiny off, it shows a visual touch just (5mm?) above my finger press)
[Android Q&A, Help & Troubleshooting] cyclon1978:
http://d-h.st/yw7O

i think i understood now how the buttons work...

what i am doing:

buttons if y < 80

BUT recalculate -> y+1399 (should give 1400 like with original touchpanel

screen if y >= 80

BUT inverse y; y = ((1260-y))

maybe i should do (y-80) (to have it in 0->1260 and divide through 1260 and multiply with 1280

so you would have

0 -> 1280 Screen

and 1400 Buttons

can you make shure the minimum for visible screen is 80 ?

the maximum for buttons is 79 ?
[Android Q&A, Help & Troubleshooting] hackwerk:
Hahahah this is getting science. My respect for you is big my man!

But no, this kernel 6 aint it:

Height still the tiny off, and buttons now do nothing (no touch nowhere).

Yes all is double checked, although I cannot find the exact division line of the screen and buttons, but 80 is my most accurate guess.

Edit: Isnt the config/values for this other brand of chipset/digitizer to be found/copied from elsewhere instead of re-inventing our wheel?!
[Android Q&A, Help & Troubleshooting] cyclon1978:
http://d-h.st/RY3A

This should be it, i forgot you have other x koords for buttons after display switch...

---------- Post added at 04:56 PM ---------- Previous post was at 04:54 PM ----------

are your button-positions different with new glass? they should because the x position is so different but the min max for x is same... ( i mean "real position" on the glass)

if i would know your brand i might get the driver... but you dont know the brand/phone your display is from?

---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------

that's last version for today, i will continue tomorrow ;)
[Android Q&A, Help & Troubleshooting] hackwerk:
:good::good: YEEEEHAAAAAAAAAAAAAAAAAAAAAAA! Y O U A R E K I N G! :good::good:

Buttons ARE WORKING, and touch also is good, not perfect though:

The height is still the tiny bit off. Can we fix this? This is annoying...

Touch shows a few mm above my finger, so top of the screen is reachable, but things in the bottom of the screen are not.

It seems relative (not 1 same absolute difference at all heights)! The difference is small at the top, and starts to get bigger from the middle of the visible screen.

If i touch the ultimate bottom of the screen edge, the touch shows on/just above the top row of the 3x3 small white dots within the big green All Apps circle in the bottom middle.

In other words, touching at the top area shows half the touch dot (as if my nail is touching)(other half is covered by my finger). At the bottom area the whole touch dot is shown with a distance of 1mm above my finger/nail.

(Glass/hardware is EXACTLY the same as original, only another chip layout (and different chip?) on the connection ribbon!)

Ps. Do you have a donation system or an address I can send my flowers to? :D
[Android Q&A, Help & Troubleshooting] cyclon1978:
The difference between finger and screen is 0 on top and growing toward bottom?

Gesendet von meinem E380 mit Tapatalk

---------- Post added at 05:31 PM ---------- Previous post was at 05:28 PM ----------

If you enable debug / input / overlay you can tell me the max and min y you reach

Gesendet von meinem E380 mit Tapatalk
[Android Q&A, Help & Troubleshooting] hackwerk:
Yes it is. Re-read my last edited post.

Y starts at 1 (screen top) and 1179 is the highest value (lowest of the visible screen) I can hit (and then it jumps to 1476 (?!) in the button area).

X is correct from 0 to 719.

The bottom line (blue line)(at Y = 1179) is displayed on exactly the top of space bar in my slided up Google keyboard.
[Android Q&A, Help & Troubleshooting] cyclon1978:
http://d-h.st/RQBH

Changes:

Y is always mapped to 1400 if in range 0..79 (you have to test if a press above the buttons on the line to visible screen causes a button press then it must be adjustet.

Y is recalculated now so everything in visible screen should be fine or at least equally off (maybe by 1 pixel)

Where have you bought the replacement part? Is it stated as "original e3 PLUS" screen or maybe an e3 standard version screen and there is a difference...
[Android Q&A, Help & Troubleshooting] hackwerk:
Nope :(

This kernel 8 is almost the same as the last. No differences but the max Y (bottom) now is 1195.

Phone is still hard to use, with (almost) no spacebar and no text input in WhatsApp etc. All in the bottom (only usable if I rotate my phone), and touch is still off. :/

The screen is sold on AliExpress (sorry) by Brothers, and is stated as a custom high quality screen (maybe not original, but with Acer brand and looks the same, but different chip layout).
[Android Q&A, Help & Troubleshooting] cyclon1978:
http://d-h.st/j8oJ

As last time check min and max y and report... it should now be near to 0/1 -> 1279
[Android Q&A, Help & Troubleshooting] hackwerk:
THIS IS THE ONE! :D :D :D

:good::good::good::good::good:

Love you man, thanks for ALL your work and efforts!!

Again: Maybe report exactly what/how you did, for others?

And where can I check the digitizer chipset (version)? Whats yours (stock)?

This kernel is your 7.19 custom one right, or is it stock kernel with this fix?
[Android Q&A, Help & Troubleshooting] Hannah Stern:
Isn't there an app, that can do this?

Try to...

Check the Developer Options.
[Android Q&A, Help & Troubleshooting] hackwerk:
[MENTION=1376601]cyclon1978[/MENTION]:

After a while of usage, I now notice a 'gap' between Y 600 and 660, but only when I swipe slowly?!

Another (more irritating) thing is that the touch (visual dot) is still a tiny bit off.

Everywhere 1 or 2 mm right of my touch, and as I come closer to the top of the screen, it still gets higher and higher above my touch/fingertip (up to 3 mm).

Seems like a relative problem (not absolute) and I can reach all coords and the maximums and minimums are correct.

Any idea!?

Ps. Yes the 5 multitouch works.
[Android Q&A, Help & Troubleshooting] cyclon1978:
Hmm... any information from the panel itself? there should be some writings on chip/connector differing to the original, that may help. The manufacturer could also give information if it is also sold for another device, maybe the e2 so that would help finding the correct driver/settings.

---------- Post added at 12:08 PM ---------- Previous post was at 11:44 AM ----------

please try this version and report back:

http://d-h.st/NMM

i changed a Y width constant used in touchpad calibration to the new touchpanel's value...
[Android Q&A, Help & Troubleshooting] hackwerk:
Seems (?) a tiny bit better. But still it is 2 mm or so off (touch shows too high) in about the top quarter of the screen :(

My phone is closed already and cannot open it anymore, lemme check the seller.
[Android Q&A, Help & Troubleshooting] cyclon1978:
http://d-h.st/IGv

report if a little bit better or worse ;)
[Android Q&A, Help & Troubleshooting] hackwerk:
Hahahah yes again, a little bit better, not 100% yet ;)

By the way, a problem since the glass change is that the screen goes off/black when calling or called, so I cannot hang up or press DTMF-numbers etc untill I press ON/OFF button etc.

Proximity sensor or so is not working (anymore)?! Got an error in the Chinese Test menu that some kind of sensor was not found when I just switched.

Ps. The chip stamp was unreadable by naked eye, and someone else switched the glass for me (I cannot open it).
[Android Q&A, Help & Troubleshooting] cyclon1978:
The proximity sensor is included in camera...

how can it change with exchange of touchpanel?

thats odd... but there is some proximity sensor related stuff in touchpanel code.

Maybe the panel is not transparent above the front camera? is the camera working?
[Android Q&A, Help & Troubleshooting] hackwerk:
Yes both cameras are fine, and the glass layout is exactly the same, only the chip layout differed.
[Android Q&A, Help & Troubleshooting] cyclon1978:
If you can get a “compatibility“ list from the panels trader i could check these sources for a better driver.

Gesendet von meinem E380 mit Tapatalk
[Android Q&A, Help & Troubleshooting] hackwerk:
[MENTION=1376601]cyclon1978[/MENTION]:

Here info and pictures of the ordered screen at AliExpress, sold by Brothers Communication Technology.

Enough info? I contacted the seller (Jerry Fu) for more info too.

(The phone is irritating my ass off, because typing and touching in heavy daily use is so often wrong :( so I am almost considering buying a Moto G 4G, or Redmi 2 or Lenovo A806)
[Android Q&A, Help & Troubleshooting] cyclon1978:
Which model do you have, e380 PLUS or standard model?
[Android Q&A, Help & Troubleshooting] cyclon1978:
Maybe worth a try:

install "old" / original firmware (4.2, oldest you have, ideal would be original dump if you made one), after that update with auto update funktion.

Maybe the firmware in the touchpanel is old and with one of the updates a firmware upgrade is coming. (the source says it is possible to install firmware upgrades for the chip from the touch panel, maybe kitkat needs the update).

That could be the reason other people report the touch panel you bought as working... (if they have 4.2 firmware for example)

Good luck...
[Android Q&A, Help & Troubleshooting] hackwerk:
Yes I will, it is strange eh?

I have the normal model, but DUO (not PLUS). See my sig :P
[Android Q&A, Help & Troubleshooting] hackwerk:
Ok I tried these:

- Restore to original stock firmware (inc erasing everything else);

- Restore to original stock firmware (inc erasing everything else) and then updating to new version;

- Erasing everything and flashing CM 10.2 for E380.

All with no positive result. Would be strange because it would mean original screens AND inverted Y screens would work in those releases!?

Also the other buyers have working screens, but did not have to first upgrade (which is almost impossible with Y ax inverted btw!). Btw your kernel does not boot in anything else than KK.

Isnt it the different regional releases of the phone (different countries/continents) and versions (DUO, single, PLUS) that may use another (my new) screen?!

I would then need to check other regions' firmwares/ROMs, although we should see complaints or my sort the other way around of people in my thread flashing our EU-versions...

No way to find out the chip/needed firmware etc with the pics of the seller or within my Android (terminal)??

I must get this fixed, because it is making me crazy every day, but the phone is still a very good phone and I would not like to buy another one...
[Android Q&A, Help & Troubleshooting] cyclon1978:
Use new kernel and grep for "FTS" (will give firmwareversion every time you press a button)

<4>[ 91.875694] (1)[77:mtk-tpd]mtk-tpd: [FTS] Firmware version = 0x25

link: http://d-h.st/cGdU

additionally i have disabled gesture support, it worked anyway with wrong coordinates, may have caused some glitches.
[Android Q&A, Help & Troubleshooting] hackwerk:
[MENTION=1376601]cyclon1978[/MENTION]:

Thanks! But I use this new kernel (12th) but it changes nothing (it seems).

In kmsg I get this one at the press of buttons:

<4>[ 2316.273378] (1)[77:mtk-tpd]mtk-tpd: [FTS] Firmware version = 0x25

<4>[ 2316.288815] (1)[77:mtk-tpd]mtk-tpd: [FTS] Firmware version = 0x25

etc.

Ps.

In logcat I get this one on every touch:

D/VelocityTracker( 1324): tpd read x fail: Bad file number

D/VelocityTracker( 1324): tpd read y fail: Bad file number

?!

Ps2. Still also annoying is the 'broken' 'proximity sensoring' because I always have to press the on/off button to hangup a call or to press a number in a menu in a call etc.!

Ps3. Semi off topic: Nice thread here, about all kernel tweaks and options.
[Android Q&A, Help & Troubleshooting] cyclon1978:
I will look into the error message.

But the log nearly proves you have same chip as original. Was there a possibility to connect it wrong?

Gesendet von meinem E380 mit Tapatalk
[Android Q&A, Help & Troubleshooting] hackwerk:
Nope, checked for that thoroughly. Copper lips were only on 1 side of the ribbon, and the ribbon could not be twisted too. Screen itself is also placed as it should.

Looks more like THEY placed the chip or contacts on the circuit wrongly. :/
[Android Q&A, Help & Troubleshooting] cyclon1978:
The error message you got is same with my device, so no new hint for a solution...
[Android Q&A, Help & Troubleshooting] hackwerk:
:crying:

No new reaction yet from the seller but "Not working!? it should be?!".

No App or kernel possibility to calibrate the touch so it adapts and remembers how much it is off everywhere?

Coming closer and closer to buying a Mi RedMi 2 :D
[Android Q&A, Help & Troubleshooting] cyclon1978:
another try, i have rewritten the mapping, the point should now match linear.

maybe out of scope, but if you give me the coordinates from log:

tpd_gesture_handle2 RAW

vs

tpd_gesture_handle2 MAPPED

(only the y value is relevant, it should now go from 0 to 1399; 1399 is at TOP of screen, if thats right, all should be fine)

i can calibrate it.

Proximity sensor should also be fixable, but that comes next ;) For now i disabled them completely, i hope the kernel will work without it (cant test ist)

http://d-h.st/IflS
[Android Q&A, Help & Troubleshooting] hackwerk:
(First of all I am still VERY grateful for your continuous help, you are an amazing guy!)

About your version v13:

The X is (still) perfect, and goes from ultimate left (0) to ultimate right (719) in Kmesg (mtk-tpd).

The Y is now off (touch on the screen shows too low) the same (!) at every spot on the screen.

I cannot touch the top of the screen (the info bar) because the touch is approx half an inch (13mm?) under/below my fingertop.

Y starts running at that toplocation (which is half an inch under the visible screen top) with 1259 and goes to 1 (the buttons in the black button area). The edge between visible screen and button area is about 124 now. All this in Kmesg (mtk-tpd).

I am guessing we are again coming closer to a non variable/non dynamic solution?! :D :D :D

Awaiting version v14 :D

Ps. Prox sensor would also be a great fix, because pressing a button to turn on my screen (and hang up or press a number) during calls is still very irritating!
[Android Q&A, Help & Troubleshooting] cyclon1978:
I need “screen coprdinates“ from developer mode y min and max and matching y coordinates from log for the min and max y (top + button area) ideal both coordinates from log: raw and mapped

Looks really good, we'll have a fix soon

Gesendet von meinem E380 mit Tapatalk
[Android Q&A, Help & Troubleshooting] hackwerk:
I am very excited :D :D :D

So you don't want the Kmesg values (as in last post) but the ones it shows in the info bar when enabling Cursor Location in Developer Menu?

(Which other files/methods are there for more debug info on this issue than kmesg and cursor location?)

On screen with Cursor Location from Developer Menu:

X is ok, and goes from 1.0 to 718.0

Y starts half an inch below visible screens top edge with value Y 139.8 and is about 1280.0 at the edge between visible bottom and button area.

(The highest Y value now (below screen bottom) is 1398.9 (in the middle of the button area))

Bad news maybe: It seems (?) it is AGAIN/STILL a tiny little MORE off (lower) on the top, than at the bottom. Or is this because the visible screen is still squeezed? Probably eh?

Difference starts to be visible at the middle of the screen, where the touch makes a JUMP. It is really really strange behaviour. I cannot explain, but lemme try:

When swiping gently and/or slow, it jumps from 702 to 758 (and the other way around). Only when pressing firmly and/or smooth and quick I DO get the coords between 702 and 758.

I am now really starting to question the quality of the replacement part although it still seems a software/firmware crazyness instead of hardware :(

Would still be a waste to have to order a new phone :(
[Android Q&A, Help & Troubleshooting] cyclon1978:
I need 9 values, screen top (as top as you can get) y value from screen coordinates from debug option, y values (2 values) for a touch on these top y value from dmesg.

The same 3 values for bottom.

And then same three values from button press.

Additionally you can check if the mystery jump happens with dmesg values or only the on screen coordinates

Gesendet von meinem E380 mit Tapatalk
[Android Q&A, Help & Troubleshooting] hackwerk:
As already mentioned (I dont understand you 2 values from dmesg?!)(dmesg seems same as /proc/kmsg):

Top (touching/swiping from the top shows a circle half inch below the top on the visible screen, so I can now not touch the Android top bar)

Cursor Location Y 139.8

Dmesg Y 1259

Bottom (edge between visible and black button area)

Cursor Location Y 1280.0

Dmesg Y 122

Button area (black area with 3 buttons)

Cursor Location Y ? (but max Y on screen when swiping downwards into button area is 1398.0)

Dmesg Y 1 (X is 90 and 329 and 628)

Need more?!
[Android Q&A, Help & Troubleshooting] cyclon1978:
You have no tpd_gesture_handle2 in dmesg or logcat?

Gesendet von meinem E380 mit Tapatalk
[Android Q&A, Help & Troubleshooting] hackwerk:
No not anymore! Youve disabled gestures remember?

Also the Firmware doesnt show anymore in this kernel.

Only info I get with this newest v13 kernel is the cinfo lines!