Develop Bugs

Custom picture frame?

I'd like to change the look of the frame used with the picture frame widget, but I can't find the image anywhere in the ROM (CM 4.1.999). Anyone know where I might find it? Thanks!

Camera.apk/res/drawable/appwidget_bg.9.png

daveid said:
Camera.apk/res/drawable/appwidget_bg.9.png
Click to expand...
Click to collapse
thank you

Awesome. Thank you!
Edit: Hmm ok, so I went in and replaced the default image with one I made, almost exactly the same except it's got sharp corners (I know, I'm picky). Anyway, I went ahead and repacked the apk and pushed it thru adb to /system/app. Now, the default frame is gone, but the one I made isn't showing up. It's like there's no border at all. Thoughts? I used Photoshop,, same dimensions as original with transparent background, saved as PNG.

this image is a ".9.png", are you aware that these have to be edited and compiled correctly to work correctly? You should search the theme forums for "draw9patch", it is a tool that is used to properly recompile these images.
A ".9" is a strechable image that has guide-lines on it that tell the OS where to stretch the image. then you must use eclipse to recompile the images, and THEN they will show up and work correctly.
If you need any help, or a good in-depth explanation of how this works, lemme know...
-BMFC

bmfc187 said:
this image is a ".9.png", are you aware that these have to be edited and compiled correctly to work correctly? You should search the theme forums for "draw9patch", it is a tool that is used to properly recompile these images.
A ".9" is a strechable image that has guide-lines on it that tell the OS where to stretch the image. then you must use eclipse to recompile the images, and THEN they will show up and work correctly.
If you need any help, or a good in-depth explanation of how this works, lemme know...
-BMFC
Click to expand...
Click to collapse
Thank you! Now I've got something "fun" to look forward to after class.

daewond3r said:
Thank you! Now I've got something "fun" to look forward to after class.
Click to expand...
Click to collapse
If you don't plan to do a lot more "theming" than setting everything up to sign 1 .9.png probably isn't worth it for you.
If you upload the file I'll sign it for you.

nebrada said:
If you don't plan to do a lot more "theming" than setting everything up to sign 1 .9.png probably isn't worth it for you.
If you upload the file I'll sign it for you.
Click to expand...
Click to collapse
Thanks nebrada!

daewond3r said:
Thanks nebrada!
Click to expand...
Click to collapse
not a problem. here ya go! lemme know if it still doesn't look right

nebrada said:
not a problem. here ya go! lemme know if it still doesn't look right
Click to expand...
Click to collapse
It's perfect! Thanks man. Would you mind doing a black one for me as well?

BLN Support for SGS2 - With Example.

Hi Dev's
This is not my code, so credits to the owner 'creams'
I happened to stumble on some code yesterday from somebody who have attempted to integrate BLN to his kernel and done it successfully.
I thought the dev's might like to take a look at this one and implement this on their work.
blog : http://creamsnexus.blogspot.com/
git : git://github.com/creams/SGS2-SC02C-BLN-Kernel.git
His kernel was built for the Jap version of GS2.
Cheers!

AdamG has already implemented this into his AOSP ROM and it's working fantasticly, I know another Dev has already implemented it into a ROM just forgot his name. Thanks for pointing us to the source though!

hope that the devs give credit to the fix/implementation.

Ninpo also has putted it into his GIT so maybe they are already aware of it

oh i gave him a pm about it before i posted this.

samaral said:
oh i gave him a pm about it before i posted this.
Click to expand...
Click to collapse
July 31 in his GIT. You're ahead of him maybe.

I hope we will get it on MIUI and CM7 as well

vegetaleb said:
I hope we will get it on MIUI and CM7 as well
Click to expand...
Click to collapse
Don't know about MIUI but for sure on CM7. It's probably low on their to do list but BLN is something they will most definitely support just as they did with the 2X/G2X

mach0boi said:
July 31 in his GIT. You're ahead of him maybe.
Click to expand...
Click to collapse
im from the past
i didnt check his git commit date. thanks for the correction.

Do i also need to install any app from the market to enable it ?
Answer : Yes

Sorry if this is a noob question but what is BLN?

soupiejr said:
Sorry if this is a noob question but what is BLN?
Click to expand...
Click to collapse
Back Light Notification
using the led keys for notification.

Yay, my kernel will have BLN support to in the next version, just need to build all the seperate versions
(time to make a "one-for-all" kernel, that goes onto any (stock) ROM.... )

the only downside to this bln "version" is that it uses a kernel wakelock that will be hard on the battery

ogdobber said:
the only downside to this bln "version" is that it uses a kernel wakelock that will be hard on the battery
Click to expand...
Click to collapse
Yep, people are in for a treat when they realize their battery is being raped. We'll have to wait for CM7 to implement it into the framework like they did with the Optimus 2X/G2X

Nothing can beat the old good trackball lights on N1
It's a pitty all the brands stopped producing trackball,they could just reduce its size

ogdobber said:
the only downside to this bln "version" is that it uses a kernel wakelock that will be hard on the battery
Click to expand...
Click to collapse
jlevy73 said:
Yep, people are in for a treat when they realize their battery is being raped. We'll have to wait for CM7 to implement it into the framework like they did with the Optimus 2X/G2X
Click to expand...
Click to collapse
Yeah.... that is.... so not nice.... but well.... can't have everything.... :-/
// EDIT
Hm, for one, maybe some things can still be tweaked in the involved kernel code and for the other, how about disabling BLN when not needed? Does that release the wakelock? Haven't checked yet.... should check....
And does the drain/wakelock accour all the time while while activated or only when the lights are actually on - as far as I understood it so far the wakelock ist required to keep the powersupply up for the lights, but when no blinking is needed (due to no notification) the wakelock could/should be released....
Maybe that's something to tweak if that isn't already the case.
If the drain only accours when the lights are on, that's kinda OKish IMO, time to answer the damn phone *lol*

so creams put out an update that is supposed to release wakelock after the led cycle (pro app needed)
That would be an acceptable solution, I am testing to see
ps, btw jlevy he wasn't keen to your battery rape comment
HellcatDroid said:
Yeah.... that is.... so not nice.... but well.... can't have everything.... :-/
// EDIT
Hm, for one, maybe some things can still be tweaked in the involved kernel code and for the other, how about disabling BLN when not needed? Does that release the wakelock? Haven't checked yet.... should check....
And does the drain/wakelock accour all the time while while activated or only when the lights are actually on - as far as I understood it so far the wakelock ist required to keep the powersupply up for the lights, but when no blinking is needed (due to no notification) the wakelock could/should be released....
Maybe that's something to tweak if that isn't already the case.
If the drain only accours when the lights are on, that's kinda OKish IMO, time to answer the damn phone *lol*
Click to expand...
Click to collapse

ogdobber said:
so creams put out an update that is supposed to release wakelock after the led cycle (pro app needed)
That would be an acceptable solution, I am testing to see
Click to expand...
Click to collapse
NICE!
Compiler is already running

ogdobber said:
so creams put out an update that is supposed to release wakelock after the led cycle (pro app needed)
That would be an acceptable solution, I am testing to see
ps, btw jlevy he wasn't keen to your battery rape comment
Click to expand...
Click to collapse
It wasn't anything personally directed at him. I'm very grateful for his work in bringing BLN to our devices. I appreciate the update it looks like it will have a helpful impact on battery life.

Find 7a prospected ROMs with on-screen buttons instead?

Alright, I must say, I'm not a fan of hardware navigations keys. That is a reason as shallow as it can be to some but not for me, I like it on-screen.
So my question is, is there an existing ROMs around that supports that feature even on a phone with hardware navigation keys?
If yes, are they planning to support 7a? Thanks all in advance.
PS: doesn't want to start with the hardware versus on-screen argument(or get a phone with on-screen instead), just want to know if there are ROMs that do that

Afaik there is a xposed framework plugin that enables onscreen buttons

Dat-Guy said:
Afaik there is a xposed framework plugin that enables onscreen buttons
Click to expand...
Click to collapse
good to know:good:
although, personally, I prefer it be built-in into the ROM coz sometimes xposed(or maybe the module) gets in the way of the ROMs' stability, etc. as far as I've seen on other threads
but if that's the last resort, I may still consider that xposed thingy

If I can set the hw buttons behavior I don't see the point in using SW buttons.. The space is used, so why to reduce dimensions of the useful screen?

andriman said:
If I can set the hw buttons behavior I don't see the point in using SW buttons.. The space is used, so why to reduce dimensions of the useful screen?
Click to expand...
Click to collapse
as i've mention, it's my preference and don't want to start an argument with on-screen versus hardware nav keys
to each his own and i understand that
and yes, it's also good if the hardware can be set as back-HOME-recent setup, I can tolerate that(again personally my opinion only)

I just saw One+'s feature regarding switching to on-screen or capacitive keys. That's quite neat being a built-in feature. Oppo 7 hope will have this built into their ROM as well.
Tapatalked from my Nypon

I prefer on screen buttons myself so I can set them up my way (four across in my chosen order) but I cant say I would be willing to give up screen area for them as you would be doing here. Regardless xposed will usually play well with others if you keep it to a minimum, its when you pile on the changes that things usually go wrong. Might be worth a try if nothing else comes up.

i already found a way to disable capacitive buttons and enable onscreen/soft-keys buttons. Its pretty hacky though and involves root and commenting a few things in Generic.kl in system/usr/keylayout. Also adding a line to build.prop

ayysir said:
i already found a way to disable capacitive buttons and enable onscreen/soft-keys buttons. Its pretty hacky though and involves root and commenting a few things in Generic.kl in system/usr/keylayout. Also adding a line to build.prop
Click to expand...
Click to collapse
PA dev to the rescue! Thanks man.?

Rycon33 said:
PA dev to the rescue! Thanks man.?
Click to expand...
Click to collapse
ill see if i can make a flashable zip with this mod

ayysir said:
ill see if i can make a flashable zip with this mod
Click to expand...
Click to collapse
Great, the 7a will be available here at my place next week. So having this mod ready is really good. Just hope there's no delay on the availability here.

While I've generally been "not a fan" of hacks like this, since CM is officially doing it on the OnePlus - I'm going to look into this eventually for Omni. (I think maxwen has already implemented 75%+ of it on the N1...)
With Omni though, my top priority after basic bringup is figuring out a way to have unified storage in an optional way.
ayysir - don't try to use the omni f7a kernel in its current state BTW. I screwed up merging something somewhere in the display code and it IOMMU faults where stock usually does the contsplash handoff.

I love you for this entropy.
Gesendet von meinem MI 2 mit Tapatalk

Entropy512 said:
While I've generally been "not a fan" of hacks like this, since CM is officially doing it on the OnePlus - I'm going to look into this eventually for Omni. (I think maxwen has already implemented 75%+ of it on the N1...)
With Omni though, my top priority after basic bringup is figuring out a way to have unified storage in an optional way.
ayysir - don't try to use the omni f7a kernel in its current state BTW. I screwed up merging something somewhere in the display code and it IOMMU faults where stock usually does the contsplash handoff.
Click to expand...
Click to collapse
Unified storage? Oh yes. That would rock. I have no idea why OPPO chose to go with the ancient implementation of the 3GB partition for apps.
I prefer hardware keys myself, but giving people the choice would be cool.
I can't wait until I get my 7a.
Sent from my HTC One using Tapatalk

Entropy512 said:
While I've generally been "not a fan" of hacks like this, since CM is officially doing it on the OnePlus - I'm going to look into this eventually for Omni. (I think maxwen has already implemented 75%+ of it on the N1...)
With Omni though, my top priority after basic bringup is figuring out a way to have unified storage in an optional way.
ayysir - don't try to use the omni f7a kernel in its current state BTW. I screwed up merging something somewhere in the display code and it IOMMU faults where stock usually does the contsplash handoff.
Click to expand...
Click to collapse
nawh im not, im basically trying to help out which way i can for ya
btw, oppo messed up on back key software keys drawable

ayysir said:
nawh im not, im basically trying to help out which way i can for ya
btw, oppo messed up on back key software keys drawable
Click to expand...
Click to collapse
Omni kernel is now usable - at the very least, the kernel/device tree produces a usable TWRP.
It also builds successfully when using blobs from teamgruntled - but I have yet to actually try flashing it. (plan is to whip up an eng build tomorrow, I'm too busy tonight to make any progress.)

Entropy512 said:
Omni kernel is now usable - at the very least, the kernel/device tree produces a usable TWRP.
It also builds successfully when using blobs from teamgruntled - but I have yet to actually try flashing it. (plan is to whip up an eng build tomorrow, I'm too busy tonight to make any progress.)
Click to expand...
Click to collapse
great bro, its omni's repos?

ayysir said:
great bro, its omni's repos?
Click to expand...
Click to collapse
teamgruntled for blobs temporarily since I might forcepush-rebase the blobs once or twice, kernel/device tree are in omni github.
Current state of the device tree is almost guaranteed to result in massive bogosity if flashed. As in if I'm afraid to flash it to my device you should be too!

Entropy512 said:
teamgruntled for blobs temporarily since I might forcepush-rebase the blobs once or twice, kernel/device tree are in omni github.
Current state of the device tree is almost guaranteed to result in massive bogosity if flashed. As in if I'm afraid to flash it to my device you should be too!
Click to expand...
Click to collapse
i know, the main objective is for me being able to compile it then back track from there
atm though i am recieving this issue: http://jenkins.hostingsharedbox.com...l=93.buildbot.hostingsharedbox.com/20/console
dtb related

[Tool] Panel Info (lgd/jdi) [Tool]

Panel Info
Some of you already use it or have used it.
It will detect if your pannel is LGD or JDI.
thx to @Cloudyfa on informations, hints, suggestions about it, basically it's only a wrapper for the command he used in his thread.
I thought if I should post it or not, since I've already released the LKF - Little Kernel Flasher, first I thought not to post it..then I thought, people need information in one tool, then they can handle with other tool if needed so i decided to post it.
Q) Does my G2 have to be rooted ?
A) YES
So IF your panel type is jdi you can either flash kernel which is suitable for your panel OR proceed to LKF thread and it will automatically detect the panel, patch the kernel and flash it.
The interface itself is clear, simple. If you've got issues please post them here in a clear form with full and understanding sentence.
thx
Link: Version 1.1
Md5:
c41a110ec94c41d51e478cc6ad8b726b
Click to expand...
Click to collapse
Changes:
1.1 - 4.June 2014 - Added more accurate information (More or less accurate - depending on user input)

Hi mine is a lgd/lgit what are the differences between the both many thanks.
Sent from my LG-D802 using Tapatalk

Works well on latest mahdi. Nice job.
Tapatalk-kal küldve az én LG-D802-el

MRobbo80 said:
Hi mine is a lgd/lgit what are the differences between the both many thanks.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Just different types. Jdi is Japanese I think.
Sent from my Vs980 running Xdabbeb's 24a v1.1.1

So having this version lgd I will not worry about patching my kernels, personally I have never had issue with white lines.
Sent from my LG-D802 using Tapatalk

MRobbo80 said:
So having this version lgd I will not worry about patching my kernels, personally I have never had issue with white lines.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Kernel devs are now creating and naming the kernels in a way you will see which one is right for you.
Usually if it's just the kernel name then it's the LGD. If it's in the jdi folder or the name contains jdi then it's for jdi.
also, if you get the lines it means you have to flash the opposite one.
But it's easier this way, just informative.

bender_007 said:
Kernel devs are now creating and naming the kernels in a way you will see which one is right for you.
Usually if it's just the kernel name then it's the LGD. If it's in the jdi folder or the name contains jdi then it's for jdi.
also, if you get the lines it means you have to flash the opposite one.
But it's easier this way, just informative.
Click to expand...
Click to collapse
Really great you making these little tools for people that don't feel comfortable doing/running commands themselves.
Thanks
Sent from my Vs980 running Xdabbeb's 24a v1.1.1

Lawlrus said:
Really great you making these little tools for people that don't feel comfortable doing/running commands themselves.
Thanks
Sent from my Vs980 running Xdabbeb's 24a v1.1.1
Click to expand...
Click to collapse
They are mostly set of commands but yes I know some people want to do things but are uncomfortable typing and fiddling around. It's better shortening the time, make this little things faster and mostly safer. It's a pleasure whenever the tools help someone , you're welcome.

bender_007 said:
They are mostly set of commands but yes I know some people want to do things but are uncomfortable typing and fiddling around. It's better shortening the time, make this little things faster and mostly safer. It's a pleasure whenever the tools help someone , you're welcome.
Click to expand...
Click to collapse
Cuts down on me havin to yell at people for asking the same simple questions over and over lol
Sent from my Vs980 running Xdabbeb's 24a v1.1.1

bender_007 said:
Panel Info
Some of you already use it or have used it.
It will detect if your pannel is LGD or JDI.
Link: DOWNLOAD
md5:
Code:
bce735462bfefe7e858650e5abf17eeb
Click to expand...
Click to collapse
Nice work, bud. Btw, I think you should add the info that the app requires running on stock kernel (before using AutoRec or flashing any kind of custom/patched kernel) because I know many pp will try to run it after they have white lines issue and the result may not be correct

Cloudyfa said:
Nice work, bud. Btw, I think you should add the info that the app requires running on stock kernel (before using AutoRec or flashing any kind of custom/patched kernel) because I know many pp will try to run it after they have white lines issue and the result may not be correct
Click to expand...
Click to collapse
Thx for pointing it out again m8, I thought of it, too. I'll make it communicate with people to recorrect the status if needed(lkf too):"do you currently have a white line issue?" if yes then the opposite result is correct, if no then the current result is true
4. June 2014 - Added v1.1 - More accurate informations depending on user input.

I'm vexed.. Yesterday the app said jdi and today lgd. How is that?

New day, new chances to win m8. Joking.
It detects whatever your current kernel is.
If it detects lgd and you say that you've got WHITE lines then it knows that your panel is actually JDI.
If it shows jdi and then it asks you if you see white lines and you say yes, then it knows it's lgd actually.

bender_007 said:
New day, new chances to win m8. Joking.
It detects whatever your current kernel is.
If it detects lgd and you say that you've got WHITE lines then it knows that your panel is actually JDI.
If it shows jdi and then it asks you if you see white lines and you say yes, then it knows it's lgd actually.
Click to expand...
Click to collapse
Thanks. That explains a lot.. I thought the Lgd/jdi difference was hardware based..

Filgaliel said:
Thanks. That explains a lot.. I thought the Lgd/jdi different was hardware based.. )
Click to expand...
Click to collapse
Based on your user input it will make sure to detect the right one. I hope it helps

Does the d800 even come with a Jdi display? I keep getting that I have a jdi display but when I look for a pa rom for jdi displays I don't see a d800
Sent from my AT&T LG G2 using Tapatalk

xxxrichievxxx said:
Does the d800 even come with a Jdi display? I keep getting that I have a jdi display but when I look for a pa rom for jdi displays I don't see a d800
Sent from my AT&T LG G2 using Tapatalk
Click to expand...
Click to collapse
Please send me direct link for the kernel. i'll patch it for you so you can try.

bender_007 said:
Please send me direct link for the kernel. i'll patch it for you so you can try.
Click to expand...
Click to collapse
Actually I ran a command via terminal and it says I have a lgd display
Sent from my AT&T LG G2 using Tapatalk

Well. You "have" whichever kernel you flash at the last
If the tool has mistaken then it's because of user input

Hi @bender_007
when you talk about white lines, to what lines do you refer?
I have white lines, vertical when the screen is off, and if I saw the screen in a wide angle and with light over the phone.
also, with the command "grep|dmesg -i panel" it shows LGD panel.
I´m using Omnirom with the stock omnirom kernel.
So, I don´t know with option do I have to chose in your app (white lines yes or not)
thanks!

[8.1] [Magisk Module] Multi-Touch Fix for 8.1 Devices

Hello guys and girls,
As some of you already know Android 8.1 suffers from a severe Multi-Touch Issue. This issues makes the smartphone randomly jumping between the two touching points on the screen when touching with two or more fingers.
The issue is known to google since the preview of 8.1. It isn´t only affecting pixel but most probably all devices running 8.1. The issue is also present on P.
An issue got created here: https://issuetracker.google.com/issues/70344455
There is a fix since mid march in review on google gerrit. But that didn´t make it into the april release, obviously.
To visualize the issue refer to the following videos:
https://youtu.be/wgYN5GwIgIc
https://youtu.be/2Vv584tvVyg
https://www.youtube.com/watch?v=4dnIk_5qdK8&feature=youtu.be
This is especially bad for gamers. With the recent release of PUBG this issues seems dramatic to some, less to others.
I´m no gamer but I noticed the issue on the google foto app.
This issue has nothing to do with the corners badly reacting to touches, or touch sensitivity etc.
So but now to the fix. It seems the issues is only related to resampling but not to touching specific points of the screen ( not related to crossing x and y axis).
That also explains why the issue wasn´t happening when using the touch tracking tool in dev settings but on various multi touch test apps.
The fix is on google gerrit currently under review here:
https://android-review.googlesource.com/c/platform/frameworks/native/+/640605
https://android-review.googlesource.com/c/platform/frameworks/native/+/640606
Last week I compiled myself a DU build with the changes included and I couldn´t trigger the issue at all. I found no other side effects caused by the two patches.
For now I decided to provide a Magisk Module which replaces the changed libs that fixes the issue.
I compiled the libs while doing my april build of DU. The magisk module can be found on the link a little bit down.
The download is here:
https://www.androidfilehost.com/?fid=890129502657595755
A few disclaimers here.
1. That fix should in theory work for most 8.1 devices, including the likes of pixel 1st gen, pixel 2nd gen, one plus, xiaomi which suffer from this severe issue.
It seems devices with oos on 8.1 ( op5/t) cannot use this mod.
AOSP and LOS roms should be okay.
2. I didn´t fix this, I just compiled the libs with the fix found on google gerrit.
3. Rom devs you are very welcome to include this fix. I found no ill consequences as of yet but I can understand google taking it slow and reviewing it longer. Maybe they will find a better fix, but as of now this is the best thing we have.
Donations:
Donations are not mandatory but very welcome.
If you like my work: http://paypal.me/freak07

@calebcabob
 @Myself5
 @BDogg718
 @sixohtew
 @nitin.chobhe
 @auras76
you may want to look at this and include it in your april releases.
If not users can just make use of the magisk module.

This causes a bootloop on P DP1.

iaTa said:
This causes a bootloop on P DP1.
Click to expand...
Click to collapse
Thanks for the report.
can anyone confirm this?
In the meantime i removed the p tag from the thread title.
Could be That there are additional changes in p that make this libs unusable and only workable on 8.1.
Unfortunately there is afaik no complete source for p yet. So I can’t compile them specifically for p.

Fixed for me!! I only ever noticed the issue when pinch/zooming images on Instagram.. it's gone! Using the April update of 8.1 ... Thanks!!!

jbarcus81 said:
Fixed for me!! I only ever noticed the issue when pinch/zooming images on Instagram.. it's gone! Using the April update of 8.1 ... Thanks!!!
Click to expand...
Click to collapse
Same with me on google fotos!
Glad it’s fixed for you.

Freak07 said:
Same with me on google fotos!
Glad it’s fixed for you.
Click to expand...
Click to collapse
Also fixed for me, thanks for solving this problem!

I can't replicate this problem, but good to know that there's a fix if I ever experience it.

I'm a beginner at this.But when I tried to install it via magisk manager,I get this error.What are the correct installation steps to flash a magisk module?
Thanks

I never had this issue but it's good to know there's a fix..I'm on the p preview so I'm not sure if I will ever have this issue and no one reported it in my builds but I will include the fix anyways that way no one has to do anything. Good catch

Prey521 said:
I can't replicate this problem, but good to know that there's a fix if I ever experience it.
Click to expand...
Click to collapse
sixohtew said:
I never had this issue but it's good to know there's a fix..I'm on the p preview so I'm not sure if I will ever have this issue and no one reported it in my builds but I will include the fix anyways that way no one has to do anything. Good catch
Click to expand...
Click to collapse
I also thought at first I didn’t have this issue at all.
But once I triggered it accidentally I experienced it many times. Maybe I just learnt what to look for.
Another fun thing is. A friend of mine also got the pixel XL 2 and I could reproduce it right away on his locked phone which is stock 8.1.
I can also trigger it on my pixel C tablet.

ReapinDevil said:
I'm a beginner at this.But when I tried to install it via magisk manager,I get this error.What are the correct installation steps to flash a magisk module?
Thanks
Click to expand...
Click to collapse
Either try flashing it in recovery or use the latest magisk?

Freak07 said:
@calebcabob
@Myself5
@BDogg718
@sixohtew
@nitin.chobhe
 @auras76
you may want to look at this and include it in your april releases.
If not users can just make use of the magisk module.
Click to expand...
Click to collapse
The mention for the last dev didn't work for some reason, so:
@auras76

mistermojorizin said:
The mention for the last dev didn't work for some reason, so:
@auras76
Click to expand...
Click to collapse
Thanks in the quote from your post of my post it worked tough

Freak07 said:
Thanks in the quote from your post of my post it worked tough
Click to expand...
Click to collapse
That is really weird, because even when I quoted you, then hit "preview post" to see what it would look like, it still didn't work inside the quote.

Kudos to you,
Previosly my device has a bad touch pressure sensitivity along the edge, and in certain spot, it wont even register the touch,
Now it all fixed.
The corner two still has less sensitivity, but previously all edge zone were patchy, full of red zone.
And considering am using full cover glass protector. This is amazing work !

What app did you use for that test?

I've experienced lack of touch response quite often. It's weird and seemingly random. I just flashed this on 8.1 with magisk. I don't have any results yet, but based on what everyone else is saying, this is a solid fix. Thanks for your work!
Do we have to worry about removing this in the future if google updates fix the issue too? Will this being on the system cause conflicts and issues?

mistermojorizin said:
That is really weird, because even when I quoted you, then hit "preview post" to see what it would look like, it still didn't work inside the Autor.
Click to expand...
Click to collapse
That’s just xda bring xda.
I had this problem a few times when updating the OP for a new release. Sometimes the OP won’t update at all...

otonieru said:
Kudos to you,
Previosly my device has a bad touch pressure sensitivity along the edge, and in certain spot, it wont even register the touch,
Now it all fixed.
The corner two still has less sensitivity, but previously all edge zone were patchy, full of red zone.
And considering am using full cover glass protector. This is amazing work !
Click to expand...
Click to collapse
Glad it works out for you!
Enjoy your phone