yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] cyclon1978:
I'll try to work with the values you gave me, next version will have proper logging, so we can make it perfect.

Can you see the mysterious y jump in cinfo lines? Try to reproduce it and check if it also have a gap in these coordinates

Gesendet von meinem E380 mit Tapatalk
[Android Q&A, Help & Troubleshooting] hackwerk:
Sorry! Check my last post again. I forgot about your special Firmware and Gesture / Velocity logging version (before last kernels)!

I grepped all logs etc on 'mtk tpd cinfo FTS mediatek touchpanel focaltech touchinfo' (OR and case insensitive) but only got the cinfo lines, the Firmware lines and the Velocity tracker errors.

The gap is of course also in dmesg/kmsg (hops from 639 to 689 or from 686 to 641 etc etc) but like I said, this is only when trying to be slow and very gentle. Not when using with a good and fast press/swipe.

Ps. If I flash back to the previous version (v12) I get the Firmware etc again, and the Velocity, but also one/two I didnt see last time:

D/VelocityTracker( 1292): Couldn't open '/dev/touch' (Permission denied)

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

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

And Wallpaper by the way (when swiping top bar down):

V/WallpaperService( 1210): Delivering touch event: MotionEvent { action=ACTION_DOWN, id[0]=0, x[0]=194.72955, y[0]=1276.0032, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x1, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=793451, downTime=793451, deviceId=3, source=0x1002 }
[Android Q&A, Help & Troubleshooting] cyclon1978:
i made a mistake...

i changed mapping & logging for gesture points (with disabled gestures that is senseless).

Now it should work and give you:

printk(" RAW cinfo->x[0] = %d, cinfo->y[0] = %d, cinfo->p[0] = %d, point_num=%d\n", cinfo->x[0], cinfo->y[0], cinfo->p[0],point_num);

printk(" CAL cinfo->x[0] = %d, cinfo->y[0] = %d, cinfo->p[0] = %d, point_num=%d\n", cinfo->x[0], cinfo->y[0], cinfo->p[0],point_num);

I need RAW and CAL Values for top of screen, bottom of screen, button area (search for absolute value in button area, for example min and max value for button area should be between 0 and 60).

And tell me how "off" we are if we are still off.

http://d-h.st/x46R

And one version for more debug info:

http://d-h.st/KJAh

This ones print "DATA high= low=" values which is the data from the touchpad without any modifications.

That might help with the gap problem, maybe in the data is a "long press/press intensity" value coded which has to be removed.

Directly use the second version.

And try to check what "point_num=" says if the gap occurs -> this is the number of parallel touch points pressed, it might help if the gap only occurs with a value of 2 or more. Then your gap happens because of double recognised finger....

Greetings,

Andreas
[Android Q&A, Help & Troubleshooting] cyclon1978:
Then I need the dmesg raw and on screen coordinates from all the good points and from the most off ones

If you make a table with real position on screen (f.e. 5mm from top)...

Gesendet von meinem E380 mit Tapatalk
[Android Q&A, Help & Troubleshooting] cyclon1978:
Can you get the values from touching at the top around the acer logo? (on sensor, camera, acer logo Y position)

My screen gives there negative on screen coordinates, i think that's how the proximity sensor works...
[Android Q&A, Help & Troubleshooting] hackwerk:
Nope, I do not get any touch or values above the visible screen. I gave you the maximum value (cinfo 1259/1399, mapped on screen 0), and this is reached by touching a little under the top edge (because touch is off a little, above my finger). So if i press the exact edge (or above) with my finger, nothing happens.

Under the bottom (lowest cinfo value I gave 107/118, mapped on screen 1280) I can get reaction to about the middle between a button and the bottom edge of the visible screen.

To go short: No reaction whatsoever above the top, and no negative values ever (with this screen and your new kernel).
[Android Q&A, Help & Troubleshooting] hackwerk:
I already gave you all those / everything (press SHOW button last post)?!

To get the touch dot/line at the top edge, I have to touch a little under the edge (touch is off, touch is higher than finger). When I touch higher (i.e. ON the edge, nothing happens anymore (resulting Y would be lower than 0).

To get the touch dot/line at the bottom edge, I have to touch a little above the edge (touch is off, touch is lower than finger). I can touch lower (i.e. ON the edge or a little below, until it jumps to button press (Y is 1).

In the middle of the visible screen touch is perfect/spot on.

Seems I can reach the mapped edges by touching a less high (Y) area. In other words, this kernel thinks my touch screen hardware (raw data) range is smaller/more narrow than it IS?

That could also explain a "black hole" in the middle :)

Hope we are getting closer instead of more lost? :D

PS. CAL is always the same as the normal cinfo, so why added it?
[Android Q&A, Help & Troubleshooting] cyclon1978:
Can you give me the number of screen pixels you are off for every data high value? Then I will add/subtract these pixels in the area.

Best would be to remap every value, but that would mean I need 1280 values from you, so it is only 5 values...

Gesendet von meinem E380 mit Tapatalk
[Android Q&A, Help & Troubleshooting] hackwerk:
I dont understand I guess? You already can if I am right?

I gave you DATA (plus RAW and CAL Y) values of the top edge (which is off) and 1/5, 2/5, 3/5 and 4/5 and bottom edge (5/5)(which is also off)?

I do not understand the difference between the 4 values (DATA low, RAW, CAL and the visible Y (shown by Cursor Location) good enough to help you.

Also I do not know what is a genuine value and what is remapped?

Most important, I dont know what all values normally could/should be?!

My DATA low starts (high section 4) on top at 235 instead of the other 255's, so there should be a 20 px area above the top (prox sensor?) in the normal screens?

My DATA low ends (high section 0) at the bottom with a 107 instead of the normal 0, so the button area is 107px (inc 0)?

What are your unmapped values? And how come the cinfo can hit 1400 (1399) when my hardware seems only capable of 1280px (5 high sections times low 256 (255 to 0) = 1280)??
[Android Q&A, Help & Troubleshooting] cyclon1978:
I need the RAW Point vs. real screen point YOU WANT.

For Example:

RAW CENTER -> Screen CENTER -> so no correction.

RAW top segment: -> 3 mm too much to top -> needs a correction -20pixels

RAW 2. segment: -> 2 mm too much to top -> needs a correction -15pixels

You have to guess the pixels off... you can check how much "on screen real mm" relates to how much "on screen pixels"
[Android Q&A, Help & Troubleshooting] hackwerk:
I edited my last post (like always), please read.

I think it is still an exact riddle/problem and not one of guessing and somewhat off etc. Read my last lines please?

Edit2: So the cinfo should go from 120 to 1400 which is standard remapped with -120 (visible Y is 0 to 1280)??

So 120 pixels outside of (under) the visible screen?

Seems my hardware only does (max) 1280 instead of 1400 or?
[Android Q&A, Help & Troubleshooting] cyclon1978:
To make it clear:

you check points on screen in the segments you identified (high byte)

for every segment:

- you check of inside the range of the segment (256 pixels) the touch is off.

- then you give me a correction assumption, for example:

segment (always measure IN THE MIDDLE of the segment, for example HIGH=3 LOW=127) or better measure MIDDLE, LOW=0 and LOW=255 and give me three values for best result

HIGH=4 (TOP) -> ca. 30 pixels off (-30)

HIGH=3 -> ca. 15 pixels off -15

HIGH=2 (CENTER) -> matches 100%

HIGH=1 -> ca. 15 pixels off +15

HIGH=0 (BOTTOM) -> ca. 30 pixels off (+30)

These added pixels are equivalent to mm, 1cm is around 80 pixels? you can test that with a ruler.

So... you check how much mm it is off, and calculate how many pixels (on screen from debug menu show location) you want it to be changed.

I know that wont give a perfect result, but if you give me

---------- Post added at 03:27 PM ---------- Previous post was at 03:18 PM ----------

as a "blind" shot i added:

if (high_byte == 4) {

cinfo->y= cinfo->y - 20;

}

if (high_byte == 3) {

cinfo->y= cinfo->y - 10;

}

if (high_byte == 1) {

cinfo->y= cinfo->y + 10;

}

if (high_byte == 0) {

cinfo->y= cinfo->y + 20;

}

should be a little better, but will make jumps between HIGH-changes. These we'll address later. So if i know how much to add/substract for every RAW y-coordinate it can be perfect remapped to the on-screen-coordinates.

http://d-h.st/H8EP

Other way would be to use a mathematical function, that could be done with enough test-points.
[Android Q&A, Help & Troubleshooting] hackwerk:
Thanks, this is a little better and a nice 'guess' indeed.

Lemme sum up. If I am correct the DATA is raw unmapped/unedited data from the hardware, and makes the raw coord by Y RAW = (high * 256) + lower?

The the RAW is remapped by your hack with something between 11 and 140 to make the CAL/cinfo?

How is it possible then that it was upside down? Or are you doing the remap AFTER the CAL/cinfo by subtracting 1400 and multiply by -1 or?

Isnt the upside down problem one of switching the DATA area's?? I need to know where/what your hacks are in the current kernel already?
[Android Q&A, Help & Troubleshooting] hackwerk:
[MENTION=1376601]cyclon1978[/MENTION] Please tell me, what should all normal values be (in your stock phone)? And where and how (much) you do a translation in my current kernel?? I need to understand more of how we are already transformed and how the normal/basic situation is, so I can help you think :)

Btw: This current kernel is quite ok, only the gap at slow swipe in the middle still exists, and the top segment (4) is still a little too high (I see the touch a mm above my finger). Bottom seems ok now.
[Android Q&A, Help & Troubleshooting] cyclon1978:
The problem is, i need the difference between visual point and finger. So i cant really map because your touchscreen is not linear (thats why the gap is changing)

Only way is you get me as much RAW HIGH/LOW Values with the info how many pixels you see it off.

We can concentrate on the most annoying points. And we also can map "HIGH=3 LOW < 50" to another value than "HIGH = 3 LOW >= 50" and so on.

I will then make a map containing 1280 (or whatever) RAW points mapped to the visible points.
[Android Q&A, Help & Troubleshooting] hackwerk:
I will report asap ok? I have some wrist pains (RSI) so I am not very busy online now :(
[Android Q&A, Help & Troubleshooting] cyclon1978:
as long as your device works, there's no pressure ;)

at the moment i am compiling lollipop, so i would have not much time for this anyway...

hope youll get better soon.
[Android Q&A, Help & Troubleshooting] hackwerk:
End of story

[MENTION=1376601]cyclon1978[/MENTION]; You wouldnt believe it but my girlfriend accidentally swiped the phone out of bed, and then stepped on it! The screen is broken, AGAIN :(

It is still usable (thanks to you of course!) but I have to order a new screen (hopefully a normal one now), AGAIN!

This means (I hope) your work on the flipkernel is done now :D

You helped me A LOT (and my phone had been usable this whole time)! I never had anyone online invest so much time and attention in helping me. Big thumbs up and we all love you man! ;) :good:

Ps. I also ordered a XiaoMi RedMi 2 to go on with (4G, 64-bits, MIUI etc). So from now on I will be less active maybe.
[Android Q&A, Help & Troubleshooting] roky217:
Hello, I got similar problem whit my acer E380, I bought 2 different Touch screen, the first one from Brapa and I got the inverted touch issue, I thought it's broken so I order I new one from Ebay and I still got the same issue, Inverted axis and buttons are not working.

I read this tread, and I try to download the last kernel that I find in this tread, but it's tell me file not fond when I try to download.. So I try whit a older version.. but when I try to instal whit Carliv touch recovery 3.0 I got an error: "this package is for acer_e3 devices; this is a "E380" ".

Anything I could do for fix my reversed touch?

Thanks in advance for your reply.

______

Edit:

I find out how to apply the kernel, I just use the SPFT to flash the boot.img into my device and the touchscreen and buttons are finally start to work again. But I was wonder if it's possible to upload again the last version that was on this tread, since when I try to download it's keep telling me "File not found"
[Android Q&A, Help & Troubleshooting] pepsicolaaa:
Hello, I have the same problem here, my touchscreen is reversed after have changed it, and all your links are down, could you please send the working one back again ? thanks :)
[Android Q&A, Help & Troubleshooting] cyclon1978:
Custom Kernel with flipped screen

here is the kernel with corrected touch screen:

http://d-h.st/Qhrx

only flash if you replaced your screen, original screen will go crazy with that ;)

And always make a backup prior to flashing, but no data wipe required.

I had to recompile it due to i have not saved it, so i hope it works...

Greetings.
[Android Q&A, Help & Troubleshooting] joe_xda:
Hi cyclon1978,

thank you for your work. I would try the modified kernel too. Would you update the link please, it is outdated again.

Regards

Joe
[Android Q&A, Help & Troubleshooting] joe_xda:
Hi,

may you make the compiled kernel available? I have the same problem here.... :(

Thanks
[Android Q&A, Help & Troubleshooting] cyclon1978:
Flip-ScreenKernel:

http://d-h.st/Evj4

Can anyone show me a tutorial how to replace the screen? I dropped my device and the LCD ist broken in two pieces... (half working, half dark).
[Android Q&A, Help & Troubleshooting] joe_xda:
Hi,

thanks for the Kernel I download it.

For screen replacement this is a good video. Its not E3 but it is very very similar, all screws, cabels you find as the Z5.

I have too few posts I cannot post a link so just the youtube video ids:

IT86A-DPTRg

Than to remove the touch screen you may watch this:

ubDyO_u0LZg

Regards

Joe
[Android Q&A, Help & Troubleshooting] hackwerk:
If you check my big E380 thread, and follow the battery link in the phone info section, you see the first disassembly steps.
[Android Q&A, Help & Troubleshooting] yuraaa_73:
Hi!

thank you for your work. I would try the modified kernel too. Would you update the link please, it is outdated again.

Regards

Yura
[Android Q&A, Help & Troubleshooting] J.Marek:
Update Link please
[Android Q&A, Help & Troubleshooting] Amiroff:
Hello! I have same problem, my new touchscreen with inversed Y-axis. You are my last hope!!! Can you update the link??
[Android Q&A, Help & Troubleshooting] KZekai:
cyclon1978 you still around? Can you lend me a hand with my inverted touch?
[Android Q&A, Help & Troubleshooting] KZekai:
I went through all of them so far:

- script.bin is not applicable for my device and Android 7.0, it sounds like some nonsense in general

- echo 1 > /sys/modules/tpd_settings/parameters/tpd_mode_axis is ignored by tpd device completely

- ro.sf.hwrotation always locked to 180, apparently by device driver?

The only thing I have no idea how to do is:

- modding kernels and/or installing other drivers

Kernel might be doable, but drivers seems pretty ogre since I dont think for such niche device they are available anywhere
[G3 Q&A, Help & Troubleshooting] FaNTaTehPr0:
Hi everybody. I know there is many similar threats like mine but i after a big search iam confusded. i have bought my LG G3 D855 2 weeks ago. I am actually a big fan of Custom roms like CyanOgenMod but the problem is the Stock Rom of Lg G3 Has an awesome Camera Apk.. I was looking if there is a possibility to install A custom Rom and install the stock camera of Lg G3 . So far i found only for G2.. And Besides the camera there is a huge difference between stock and custom rom in LG G3.. In battery Drain and especially In the Ram management... I have the g3 with 2 GB Ram and it eats the 70-80 % . Any help an idea is appreciate .. Sorry for creating a threat which may already been created.
[G3 Q&A, Help & Troubleshooting] joooe:
Saying Sorry is not an excuse for not using search.

In this forum, press the SEARCH THIS FORUM button and write "camera apk".

Guess what, you will see a few threads about the subject.
[One (M8) Themes and Apps] skeleton1911:
what is required:

A Rom with 1% Battery Mod in it.

or you have flashed Lyapota's Modpack with 1% mod. -link to his modpack: Lyapota' Modpack

take a look into post #2 for a quick 1% Guide.

confirmed working with:

Eragon ROM

Maximus_Rom

if you dont want lyapota's modpack . flash this 1% mod for the Maximus Rom : LINK

------------------------------------------------------------------------------------------------------

Flash them in recovery and reboot
[One (M8) Themes and Apps] skeleton1911:
How to make 1% mod for your Rom

i will not explain how to set apktool up or what you need to decompile an app.

because there are many threads/guides out here for that.

i use vts (virtual ten studio)

1. decompile the SystemUI.apk

2. browse to res / drawable / stat_sys_battery.xml and stat_sys_battery_anim.xml

3. remove all codes and copy the codes from the zip into it..

4. browse to res / drawable-xxhdpi and copy all files from the drawable-xxhdpi folder in the zip to it.

5. recompile .

6. done
[One (M8) Themes and Apps] wILLRoiD:
nice work (:
[One (M8) Themes and Apps] skeleton1911:
Thanks. Hope all works . because i haven't checked all.
[One (M8) Themes and Apps] aiwapro:
Does Lyopta's Mod Pack have 1% built in? It has what is called 'battery %.' Is that the same. I have Lyopta's Mod Pack running on Android Revolution. Will your theme were with me just flashing in Recovery?
[One (M8) Themes and Apps] skeleton1911:
Yes. If you choosed 1% in lyapotas mod . my themes will work :)

Just flash them in recovery..
[One (M8) Themes and Apps] GCbard:
Does the work for GPE rooms?
[One (M8) Themes and Apps] skeleton1911:
Should work. If the codes are the same..
[One (M8) Themes and Apps] rc420head:
Whoops wrong thread sorry

CandyRoms Maintainer
[One (M8) Themes and Apps] Deathsting_50cal:
I assume you have this in your rom? ;)

Edit: Looks like i forgot my good eyes on my nightstand and forgot to read the OP...
[MX Player] ciberneticu:
Hello,

how i can repositioning the video screen? (bottom, top, left or right)

Best regards,

Dan
[MX Player] josuearisty:
I think this what you are looking for:

Settings->Player->Touch controls->Zoom and Pan

Then just use to fingers while playing videos to control it.
[General Topics] fallenczar:
hey guys...

here are some vga themes that i made and have been using for some time...

if you like themes then post a screenshot of your device...

if enough people request i may consider making square and qvga themes...

PM me only and only if you want to send some money to me....[:D]

all the wallpapers are from www.deviantart.com

Cheers!!
[General Topics] fallenczar:
somemore screeny to be followed by the file
[General Topics] fallenczar:
few more......
[General Topics] fallenczar:
last one with the themes file
[General Topics] natee:
Wow, thank you very much. I was just wondering where I'd be able to find themes if I ever get bored of my current theme. Classy designs and files not too big either!!
[General Topics] fallenczar:
my latest update
[General Topics] fnordelus:
Here you go!

You might wan't to consider pokeing around on this site: www.pocketpcthemes.com they must have nearly a million themes my now.

Good Luck.
[General Topics] fallenczar:
and here are the files
[General Topics] DaVince:
It's quite easy to make your own themes using McDebs or Thememaker X.. I usually just do my own themes when I want a theme with my girl's picture on it..and if I want something else.. this site already has everything.
[General Topics] fallenczar:
at the expense of sounding boastful, most of the themes i came across the web (apart from a couple which were part of a theme suite) were...let us say the last option in this thread's poll.

not to sound disrespectful to any one but dude i am not intrested in some semi naked obese ugly female staring at me when i turn on my pda.

some people might say that my themes are crap, but hey i like them..and i wanted to share them with you.
[General Topics] victoradjei:
You are 100% right there :D :D
[General Topics] cktlcmd:
fallenczar,

NICE!!!! Which file can I get the cute turtle?
[General Topics] StellaDel:
Thank you for your time and your themes, while I too use McDebs for personal themes I always appreciate the work of others...

Once again thanks :)
[General Topics] fallenczar:
it should be in the first group..if you want only that perticular theme i can send it to you...just pm me your email
[General Topics] fallenczar:
you need to share them with us!!! :)
[General Topics] tenzin:
Thanks a lot Fallenczar, I really prefer your themes than the ones on pocketpcthemes and so on ... nice to share with us
[General Topics] fallenczar:
its not me tenzin, its the great artist at deviantart we need to thank
[General Topics] Laurentius26:
Cool themes!

Thanks,

Leo ;)
[General Topics] davieshyland:
cheers

:D :D muchas grasias :D :D
[General Topics] kdskamal:
Dude, is it just me or they they f*** up the visibility of text? I m still on wm5(universal) and take a look at how the contacts or any PIM app is getting displayed. This is NOT happening with any other theme
[General Topics] chaiya:
Thank you nice theme
[General Topics] fallenczar:
"Dude" if i were to qoute M$ i would say "thats not a bug, thats a feature"

I don't just put on a wallpaper on a standard template and make a new theme, as much as possible i like to modify the template so that it goes well with the theme...and that every thing is perfectly visable...

most of the time i manage to do what i want...some times i dont (usually these themes are not released or are released as v1.x ) and very rarely one of these themes escapes into the wild....

If you ask me, the color combination in the vista theme is...as you rightly voted crap..

will i modify it....hell no!!!
[General Topics] N1TeSH1FT:
I totally agree with you. This type of themes is exactly what I looked for. I tested about 100 themes and all were crap, because they have nice wallpapers which don't look good in landscape mode or where you can't read the text because its nearly the same color as the background and so on...

These are REALLY great themes. Thanks a lot for them :-)
[General Topics] cktlcmd:
Thanks. I downloaded it already. I just want to know which one of them is the CUTE TURTLE. In the folder VGA 1, is it the COOL DUDE file?

EXCELLENT THEMES!!!
[General Topics] HansiHusten:
Look real nice, will test em later.

Thx m8
[General Topics] fallenczar:
yes, it is the cool dude one
[General Topics] danielherrero:
:eek: wow. No comments. Thanks¡¡
[General Topics] N1TeSH1FT:
OK, I must correct my meaning of the themes. they have nice wallpapers and well chosen colors for top or lower bar, but the colors in text like outlook and some others are really unreadable and make the themes unusable.

Don't misunderstand me, the themes are great and they would be even better if you would lighten up the colors a little bit. They are too dark.
[General Topics] fallenczar:
sure...just give me a list of themes you want modified with the colour of your choice
[General Questions and Answers] himanshuladia:
I am a newbie to XDA and i have written a short, simple but detailed tutorial on how to unbrick your Yu Yureka in case you have stuck in a bootloop.

Simple follow this guide MOD EDIT: Don't link to external blogs. Put your information in here.

Post Any questions if you have !

:D:D
[General Questions and Answers] Hovatek:
what chipset does this phone run on?
[General Questions and Answers] himanshuladia:
Snapdragon 615