Hey guys...
With the release of CM12+ and derivatives comes a rare issue for Z1c owners that only a few people are experiencing and we're trying to track down it's origin.
We believe that it is tied to the new thermanager.xml which replaced sysmon.cfg when LP came out and also the type of display that your Z1c has. Sony used 2 versions of the display when they produced the Z1 and the Z1c.
We'd like to try and find as many of those who like us experience this black line issue which randomly appears when certain conditions are met (we have yet to discover exactly what they are ) but in combination with battery temp rise so you feel the device getting hot.
Here is a video of the issue in action :
https://www.youtube.com/watch?v=E9wyRHnjH3E&feature=youtu.be
Please let us know the display type you have which can be read via ES file explorer
Nick
Black lines:
- JDI, revision 14W09
- JDI, revision 14W04
- JDI, revision 14W15
No black lines:
- AUO, revision 14W26
- JDI, revision 14W32. Replaced screen on AUO - no black lines.
- AOU, revision 14W32
P.S. Check revision of your Z1c by opening sim tray, and look on back side of paper "tongue" .
rtimoff said:
Black lines:
- JDI, revision 14W09
- JDI, revision 14W04
- JDI, revision 14W15
No black lines:
- AUO, revision 14W26
- JDI, revision 14W32. Replaced screen on AUO - no black lines.
- AOU, revision 14W32
P.S. Check revision of your Z1c by opening sim tray, and look on back side of paper "tongue" .
Click to expand...
Click to collapse
Yes.... thanks Roman.... the revision number is also good additional information please folks (indicates production run... lower number= earlier production date)
mine is JDI, revision 14W12 for the record
I have stripes on CM12+
On stock LP - nothing stripes
Display: JDI/ Date of manufacture my phone - 14W04
AUO, revision 14W46 here. No black lines.
It seems that only screens JDI is a problem(
JDI 14W11 no black lines.
JDI 14W15
https://www.youtube.com/watch?v=2jC887JEVcM
Wanted: JDI panel ROM testers
John.D.. said:
It seems that only screens JDI is a problem(
Click to expand...
Click to collapse
yes... indeed it seems the JDI panel is the culprit.
We need a few of us with the JDI panel and unlocked bootloader to install the FXP AOSP 5.1 Build 150522 (needs fastboot flash) and run it to try and invoke the black line issue.... so whatever you have had running previously on your device when you've experienced the issue needs to be replicated to see if it happens using this ROM (which has the original thermanager.xml.)
EDIT:.... if you run this test and get the issue still happening please can you take a photo of it while on the 'about phone' tab scrolled down to show the Kernel and Build Number info which displays that the device has AOSP 5.1 installed..... then either post here or send to me whichever you like.
Once we get the results of this we have a way forward to get this issue fixed for any ROM use.
iNDEX3 said:
JDI 14W15
https://www.youtube.com/watch?v=2jC887JEVcM
Click to expand...
Click to collapse
Ah... Hitchhikers guide fan.... ..... early revision JDI is causing a few of us this problem.... but Robin and myself have set out to find a solution and having narrowed it down we need the ROM tested as per my request above.
If your English is not so good then I'm sure one of the other Russians can translate for you...?
cheers
On http://uploaded.net/f/ub0dtu i look last AOSP for amami from 150522. But today 150526.
160lightning said:
yes... indeed it seems the JDI panel is the culprit.
We need a few of us with the JDI panel and unlocked bootloader to install the FXP AOSP 5.1 (needs fastboot flash) and run it to try and invoke the black line issue.... so whatever you have had running previously on your device when you've experienced the issue needs to be replicated to see if it happens using this ROM (which has the original thermanager.xml.)
Once we get the results of this we have a way forward to get this issue fixed for any ROM use.
Click to expand...
Click to collapse
F***! There still remain the strips! I have just checked..They begin from the loading screen. I installed 150522
John.D.. said:
F***! There still remain the strips! I have just checked..They begin from the loading screen. I installed 150522
Click to expand...
Click to collapse
Ok.... thanks for trying this John.... lets see if others also confirm.... but don't worry, this was not intended to fix but rather to pin down the source. We are organised for a developer who has a good connection direct to Sony to get the appropriate changes made for those of us with the JDI panels once we know absolutely for sure that the issue stems from the original Sony thermanager.xml which is what resides inside this AOSP 5.1 ROM.
iNDEX3 said:
On http://uploaded.net/f/ub0dtu i look last AOSP for amami from 150522. But today 150526.
Click to expand...
Click to collapse
Where is 150526....? I only see 150522.... but it should not matter which one you have
160lightning said:
Where is 150526....? I only see 150522.... but it should not matter which one you have
Click to expand...
Click to collapse
I took AOSP_L_MR1_150522_amami.zip it to the bottom of the list of references
So... which version of the test?
John.D.. said:
I took AOSP_L_MR1_150522_amami.zip it to the bottom of the list of references
So... which version of the test?
Click to expand...
Click to collapse
I'm fairly certain that any of the builds will be ok to use for this test.... especially as you just tested the latest and still get the black lines. I doubt very much whether thermanager.xml has been changed at all since it was released for amami.
But of course the other ROM devs such as CM may well have made changes.... this is why we need to be sure it originates from the Sony file.... so this test is the logical way to discover the answer.... begin with the source.
160lightning said:
I'm fairly certain that any of the builds will be ok to use for this test.... especially as you just tested the latest and still get the black lines. I doubt very much whether thermanager.xml has been changed at all since it was released for amami.
But of course the other ROM devs such as CM may well have made changes.... this is why we need to be sure it originates from the Sony file.... so this test is the logical way to discover the answer.... begin with the source.
Click to expand...
Click to collapse
Well, I have installed this AOSP_L_MR1_150522_amami.zip version, and the strip is still there)
This latest version, therefore no changes
John.D.. said:
Well, I have installed this AOSP_L_MR1_150522_amami.zip version, and the strip is still there)
This latest version, therefore no changes
Click to expand...
Click to collapse
John.... please can you open your 'about phone' tab and scroll down so you can see 'kernel' and 'Build Number' info showing the AOSP as installed and with the black lines over the top and take a photo of this please....?
The more ammunition we have to give Sony the better for us to get our fix... the right people at Sony can then see with their eyes also.....
160lightning said:
John.... please can you open your 'about phone' tab and scroll down so you can see 'kernel' and 'Build Number' info showing the AOSP as installed and with the black lines over the top and take a photo of this please....?
The more ammunition we have to give Sony the better for us to get our fix... the right people at Sony can then see with their eyes also.....
Click to expand...
Click to collapse
Sh*t, I have returned to stock
I can ask somebody from the Russian-speaking community, to make it
John.D.. said:
Sh*t, I have returned to stock
I can ask somebody from the Russian-speaking community, to make it
Click to expand...
Click to collapse
Apologies.... I thought you probably would have returned to your original ROM after the test.... Ideally I should have thought to ask for the photo with original request.... not to worry.... if you can find anyone else this would be a bonus
thanks
Related
Due to conflicts between Color Calibration and the camera/video playback overlays, I would recommend not to do these modifications. If it was the case, just restore your nandroid backup.
Sorry for the inconvenience.
I'll try to improve the compatibility with our devices.
Hello everyone,
I just wanted to share some knowledge about a discovery I've made today.
Just like a lot of our Galaxy S community members, my screen was way too blueish (temperature "over 9000" kelvin).
However, by googling a few keywords around, I saw that a fix by storm9999 was available for the droid, N1, and even desire xx phones.
Basically I just tried to do the modifications on my Galaxy S with the Darky's 6.0 Gingerbread edition rom. And it works!
Here is a screenshot of the application:
http://img600.imageshack.us/i/uicolor.jpg
Requirements:
- Rooted phone
- Clockworkmod
- An Android 2.2[+] ROM (successfully tested on Darky's 6.0)
Installation:
- Make an nandroid backup just to be safe (français, english)
- Put the under-attached zip and apk files into the root folder of your internal sdcard
- Restart your phone in recovery mode
- Choose "install zip from sdcard", "choose zip from sdcard", and select the "calibrated-signed..." zip file
- Reboot your phone. Note: At first reboot, sim card may not be functional. Just reboot, and the issue should be gone
- Install the "calibrator-5.1" apk file with Astro or else
- Enjoy!
Please if you try this fix with another froyo rom, tell us if it works or not. I'll put a compatibility list here!
ROM compatibility:
- Darky's v6.0 Gingerbread ed. JPX => OK
- Stock JPU with CF-root => OK
Known bugs:
- If calibration is enabled, Spare Parts will crash when Render Settings is opened.
- When you tune your colors, the overlay appears over the sliders, and not over the calibration field at the top
- Camera and video playback lose their overlay
Credits
- Storm9999 for the apk and certificate
- Cyanogen and his team for the source files
- RixKliq for the icon making
- Xenio2000 for the UI improvements
- Supercurio for not integrating his awesome voodoo colorfix in JPU and JPX versions Sans rancune l'ami!
eruur said:
- Supercurio for not integrating his awesome voodoo colorfix in JPU and JPX versions Sans rancune l'ami!
Click to expand...
Click to collapse
Lol yeah it's a good alternative and don't require recompiled kernel !
Limitation is that it lower the final brightness and reduce the color-resolution (something like 18 or 20 bits depending the adjustment you apply - very rough estimation)
but hey, it works !
Thank you eruur
Just installed, but i noticed no differencies, droid calibrator has red blue and green at 1000 is it ok?
Working in stock JPU with CF-root
but is the color overlay really supposed to appear over the sliders? shouldn't it be covering the calibration field at the top?
looks like this here:
Razer(x) said:
Just installed, but i noticed no differencies, droid calibrator has red blue and green at 1000
Click to expand...
Click to collapse
You need to click on "User 1", then tune your colors. If your screen is a little blue, just decrease its value to something like 960.
Then save your settings.
At first I thought it wasn't working too, but if I put my blue value to 500, my screen is all yellow :d So it is actually working
I also recommend to do your calibration with the maximum brightness in order to be accurate!
@supercurio: De rien! lol
XlAfbk said:
Working in stock JPU with CF-root
but is the color overlay really supposed to appear over the sliders? shouldn't it be covering the calibration field at the top?
Click to expand...
Click to collapse
Indeed, I've noticed that also. You need to save, quit, and relaunch the calibrator to see the effect on the top field. I will try to fix the overlay position!
Does it make you lose overlays in camera and video player like it used to do before? Ie. is it modified in some way to be more compatible with stock Galaxy Froyo or is it just the unmodified files from stormy?
works with darky's rom 6.0 JPX + speedmod kernel K11C
Case_ said:
Does it make you lose overlays in camera and video player like it used to do before? Ie. is it modified in some way to be more compatible with stock Galaxy Froyo or is it just the unmodified files from stormy?
Click to expand...
Click to collapse
I searched and did not find any info about galaxy compatibility. You're right, the overlays do not work anymore in camera and video player.
Sorry about that, hadn't noticed. I guess it doesn't work that well afterall :/
I'll look into that.
Wowww ! work very good
eruur said:
You need to click on "User 1", then tune your colors. If your screen is a little blue, just decrease its value to something like 960.
Then save your settings.
At first I thought it wasn't working too, but if I put my blue value to 500, my screen is all yellow :d So it is actually working
I also recommend to do your calibration with the maximum brightness in order to be accurate!
@supercurio: De rien! lol
Click to expand...
Click to collapse
Thanks, mine seems to be good with no changes
nesquix said:
Wowww ! work very good
Click to expand...
Click to collapse
Does your camera still work good?
i can confirm the camera issues. had to restore libsurfaceflinger.so
XlAfbk said:
i can confirm the camera issues. had to restore libsurfaceflinger.so
Click to expand...
Click to collapse
Where to find it?
in your nandroid backup or an extracted factoryfs.rfs
XlAfbk said:
in your nandroid backup or an extracted factoryfs.rfs
Click to expand...
Click to collapse
Yeah, but where? (path)
eruur said:
I searched and did not find any info about galaxy compatibility. You're right, the overlays do not work anymore in camera and video player.
Sorry about that, hadn't noticed. I guess it doesn't work that well afterall :/
I'll look into that.
Click to expand...
Click to collapse
I think I've posted about that in the original thread quite some time ago and I'm fairly certain I've mentioned this option in some Galaxy S threads either here in Development or in General. But that was most likely sometime in August or September, so it's long forgotten.
I guess it makes sense that the overlays stop working, given that you need to replace the libsurfaceflinger.so for this to work.
Too bad, I was quite excited that someone finally managed to get it to work on stock Galaxy ROM. I'd love to have the option to calibrate my screen to 6500K properly to match my PC screen and I thought someone finally made it possible without the need to use CyanogenMod (not that I have anything against CM, it's just it isn't all that stable/usable just yet).
Anyway, if anybody is interesting in using this even in this state, my screen is pretty close to 6500K when using these settings:
R: 965 G: 740 B: 720
Of course every screen is a bit different and the color temperature of SAMOLED screens changes with time, so no guarantees that this will work for you as well.
Case_ said:
I think I've posted about that in the original thread quite some time ago and I'm fairly certain I've mentioned this option in some Galaxy S threads either here in Development or in General. But that was most likely sometime in August or September, so it's long forgotten.
I guess it makes sense that the overlays stop working, given that you need to replace the libsurfaceflinger.so for this to work.
Too bad, I was quite excited that someone finally managed to get it to work on stock Galaxy ROM. I'd love to have the option to calibrate my screen to 6500K properly to match my PC screen and I thought someone finally made it possible without the need to use CyanogenMod (not that I have anything against CM, it's just it isn't all that stable/usable just yet).
Anyway, if anybody is interesting in using this even in this state, my screen is pretty close to 6500K when using these settings:
R: 965 G: 740 B: 720
Of course every screen is a bit different and the color temperature of SAMOLED screens changes with time, so no guarantees that this will work for you as well.
Click to expand...
Click to collapse
Sorry for the false joy.. I was also disappointed!
Anyway, I'll play with the modified libsurfaceflinger to see if I can come up with something.
Oh and for Razer: path /root/system/lib
I think you need to put a DEV tag on the title. Good threads have been tossed to general becuse of this.
Sent from my GT-I9000 using XDA App
oh ****ttttt camera don't work too on JPX
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!
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
I just change my phone from my old one (Xperia C3 Dual) to A2 lite, and the first thing I noticed is that every time I scroll, it fell slower/less responsive; It's like you are scrolling something heavier (that what I fell?). My old phone is really laggy, running android 5.1, but still give me the better feeling when scrolling through setting, fb, web,... Is this how most xiaomi phone is like, or is there something with my unit?
I don't think there's something wrong with your unit. I have the same problem too, especially when typing something (for example in WhatsApp)... If anybody knows a fix, please post it.
After some research, there seem to be a same problem on the mi A1.
(add reddit dot com here)r/Xiaomi/comments/756lh5/facing_motion_blur_issue_on_my_new_mi_a1_texts/
HoangP05 said:
After some research, there seem to be a same problem on the mi A1.
(add reddit dot com here)r/Xiaomi/comments/756lh5/facing_motion_blur_issue_on_my_new_mi_a1_texts/
Click to expand...
Click to collapse
It sends to this topic here in XDA.
It says that it's a screen problem. You could check the LCD model installed in your device entering the test menu *#*#6484#*#* and doing the first test on the list "Version information". Then you could report it here, so we can check if the problem is related to some brand of screens or not.
For my device, that doesn't seem to suffer this problem at the moment, the screen (and other related hardware) is:
Code:
Board ID:
PCBA_V2_GLOBAL
LCD:
oncell,vendor:bird,IC:lol898
TP:
[Vendor]Biel(TP) + EBBG(LCD), [TP-IC]GT917D, [FW]Ver501c,[CFG]Ver0x53
TP surface color:
0x32 Black
BubuXP said:
It sends to this topic here in XDA.
It says that it's a screen problem. You could check the LCD model installed in your device entering the test menu *#*#6484#*#* and doing the first test on the list "Version information". Then you could report it here, so we can check if the problem is related to some brand of screens or not.
For my device, that doesn't seem to suffer this problem at the moment, the screen (and other related hardware) is:
Code:
Board ID:
PCBA_V2_GLOBAL
LCD:
oncell,vendor:bird,IC:lol898
TP:
[Vendor]Biel(TP) + EBBG(LCD), [TP-IC]GT917D, [FW]Ver501c,[CFG]Ver0x53
TP surface color:
0x32 Black
Click to expand...
Click to collapse
Have same LCD as you and do not feel there is a problem with the Input latency. But to be honest sometimes the sensor does not register some touch events. It is really occasionally, for example after unlock the phone with the fingerprint and try to swipe right in the launcher, sometimes I need to touch two times, could be probably the unlock animation still does not finish (but I see the launcher).
Sometimes while typing if I do not press exactly in the center of the letter it does not register my touch input.
Could be probably that I had a Huawei y9 2018 with 18:9 (instead of 19:9) and bigger camera and I used to that and needs more time for the a2 lite.
niko_3100 said:
Have same LCD as you and do not feel there is a problem with the Input latency. But to be honest sometimes the sensor does not register some touch events. It is really occasionally, for example after unlock the phone with the fingerprint and try to swipe right in the launcher, sometimes I need to touch two times, could be probably the unlock animation still does not finish (but I see the launcher).
Sometimes while typing if I do not press exactly in the center of the letter it does not register my touch input.
Could be probably that I had a Huawei y9 2018 with 18:9 (instead of 19:9) and bigger camera and I used to that and needs more time for the a2 lite.
Click to expand...
Click to collapse
No, it's not only you. I have your same problem with the touchscreen, but not always, sometimes it works fine.
BubuXP said:
No, it's not only you. I have your same problem with the touchscreen, but not always, sometimes it works fine.
Click to expand...
Click to collapse
Could be a software issue? I mean not the latency but the not recording touches occasionally.
niko_3100 said:
Could be a software issue? I mean not the latency but the not recording touches occasionally.
Click to expand...
Click to collapse
Yes, I think so, because of it not happening always, and because doing the touchscreen test (from the test menu I posted before) it looks fine.
same problem here i also had this issue on on older redmi note which was fixed by flashing with different firmware.
I can't replicate any of these problems. Maybe I got lucky with the touchscreen model? My version information is the same though..
Happens to me also on home screen with a heavy lwp and typing on messenger. Maybe a cpu or gpu issue? Can't handle the load?
BubuXP said:
It sends to this topic here in XDA.
It says that it's a screen problem. You could check the LCD model installed in your device entering the test menu *#*#6484#*#* and doing the first test on the list "Version information". Then you could report it here, so we can check if the problem is related to some brand of screens or not.
For my device, that doesn't seem to suffer this problem at the moment, the screen (and other related hardware) is:
Code:
Board ID:
PCBA_V2_GLOBAL
LCD:
oncell,vendor:bird,IC:lol898
TP:
[Vendor]Biel(TP) + EBBG(LCD), [TP-IC]GT917D, [FW]Ver501c,[CFG]Ver0x53
TP surface color:
0x32 Black
Click to expand...
Click to collapse
Yay that's the LCD i have
That sounds like a complete dealbreaker...
I was just going to buy the phone tomorrow
I had a similar problem when I had Xposed installed, removed it and now the phone is working great. So if you have Xposed,this is probably your problem.
Can you guys shed some more light on the issue? I am interested how many of you are encountering it and to what level.
No issues here. The phone is smooth, and I neither have Xposed nor Magisk installed.
I have the same problem
Help
i did this , open developer option then tick force gpu rendering and set animation scale to 0.5
it helps to get rid off laggy
anyone using crossbreeder lite (magisk module) on a2lite?
Me too with Mi 6x,
having high latency input and got keyboard typing errors, latency is prominent when scrolling smth even in settings scrolling. I hav compared with redmi note 5 side by side and note 5 did really fast touch TBH...
may b it got fixed by getting miui + touchpanel firmware updates Zzz
Nice changelog!
js931 said:
Nice changelog!
Click to expand...
Click to collapse
Yup.
Hope this will provide a fix to black crush / tint
Full-ZIP EU:
https://otafsg1.h2os.com/patch/amaz...5.E.17_OTA_017_all_2005100255_3f3e1afc578.zip
It's installed [emoji3]
misteurz said:
It's installed [emoji3]
Click to expand...
Click to collapse
Were you rooted before the update and if so did you keep it after the update?
Nope, i wasn't rooted
Got it via the updater app..
Green tint totally fixed
but image retention persist
Definitely not getting it in the US right now, either in system updates or the Oxygen updater
Doesnt mention display improvement
I noticed image retention a few days ago on the battery bar at the top. Ghosting can happen. I removed all icons from bar at the top but it took 24 hours for the battery ghosting to disappear. 24 hours.
Due to burn in risk I removed these icons for good.
With the new update put icons back and I can confirm the ghosting still remains. Don't want to test long term as I'm worried about burn In
got it through updater. green tint is massively improved. maybe even solved (cannot comment as I can't go into a fully dark room right now), but there is clearly some shade difference moving the brightness lower (likely when PWM changes its rate). I do notice a bit of a red effect around some elements but it is too early to tell if it is anything.
also DC Dimming black crush is improved massively, I am super happy about that
dladz said:
Got it via the updater app..
Click to expand...
Click to collapse
i did it too ,will the file be deleted after the update finished?
alandd86 said:
i did it too ,will the file be deleted after the update finished?
Click to expand...
Click to collapse
Nope file stays on your device
Nice to see Oneplus is busy to enable 5g for new providers on every OTA, it sucks they didn't activate VF NL (yet)
Maybe they're holding on the US to give us dual sim.... Or is this wishful thinking?
These version is EU only.
No update for Global for now...
js931 said:
Nice changelog!
Click to expand...
Click to collapse
Hasn't come out on the AA models yet. Not even on the Oxygen updater app.
ctonylee1965 said:
Maybe they're holding on the US to give us dual sim.... Or is this wishful thinking?
Click to expand...
Click to collapse
Would guess wishful ....ha ha
Now will be checking every few hours for AA.
The Bluetooth connectivity is so messed up with this update that the phone is not usable with a Bluetooth headset (and its the only way how I take calls). I dont get this: I hoped that they improved the WiFi 5Ghz problem and video stutter issue ( I didnt checked the first one) with the update, but they messed up one of the essential functions of the phone. The problem is: the phone is 1000 Euro and after every update it has at least one MAJOR ISSUE. I couldnt use it normally for a single day for a 1000 Euro phone. And I wanted to give it a chance. This is getting rediculous.
I think they fixed the green tint with the red tint?. Anyway much better than before. I want to try for a day the input lag of the touchscreen and the tint if are gone