I have a Moto G4 Plus XT1641 Single SIM, 2GB RAM and 32 GB ROM.
I tesed a lot of ROM's (Stock MM, Nougat and Oreo) and always I have delay in animations, in games is very bad, and when have sixity or fifty percent the phone freeze and shutdown, but the battery charge is the same, i actually use Pixel Experience Unofficial with Waver Kernel 4.6 , but is the same result
Somebody can tell me why?
Thanks. (And sorry for my bad english)
DrakoDev said:
I tesed a lot of ROM's (Stock MM, Nougat and Oreo) and always I have delay in animations,
Click to expand...
Click to collapse
You mentioned Stock ROM, does it happen there ?
In custom ROMs, it's known problem of 'Live Display'
Try turning off 'Live Display' in settings...
____Mdd said:
You mentioned Stock ROM, does it happen there ?
In custom ROMs, it's known problem of 'Live Display'
Try turning off 'Live Display' in settings...
Click to expand...
Click to collapse
Yes, for example when I do a videocall on Google Allo, the device is very slowly (in Rom Stock or custom) the status bar animation have lag and the screen freeze around five or six seconds, in games too, i have disable Live Display.
Related
Hi guys! I've got a little problem with all CM based rom (except CM13/CM13 based) on my OP2. With CM 14.1 based roms when I put my phone in charge during the night, the screen doesn't power off at all, it's dim , and there are two battery animations. I've tried everything (disabling screensaver, disabling ambient mode) but nothing changes. This doesn't happen with stock OOS 3.1 Is there any solution? Thanks and sorry for my english
There is an option in the developer menu to have the screen stay on when charging - have you checked that this is disabled?
Corlan said:
There is an option in the developer menu to have the screen stay on when charging - have you checked that this is disabled?
Click to expand...
Click to collapse
Yes, it's disabled
Hi!
I've searched almost the whole forum for this, but found mostly only vague similar issues...
I'm currently on CM12.1 official and it works like a charm (besides of missing security updates). After flashing latest Stock 6.0.1 Marshmallow, I experience a lag in many user interactions, e.g. when pressing a button/key or scroll in the settings. This lag is not occurring on every interaction, but approx. 2-3 times per minute and lasts for less than 1 second.
What I tried so far:
remove bloatware
install Custom Rom (Marshmallow/Nougat, no touchwiz)
fix CPU frequency
use different CPU governor
Is it just me having those issues?
Try *#2663# then press TSP FW update(General).
I've experience a little bit of a lag when I'm booting my device from a cold start up sometimes. But otherwise my N910C has been working perfectly on the stock Samsung Marshmallow OS.
GrippingSphere said:
Try *#2663# then press TSP FW update(General).
Click to expand...
Click to collapse
Sorry, but this didn't fixed it...
My Moto G4 Plus is on the latest stock build NPJS25.93-14-4. The notification bar is lagging a lot. I thought it might be cause of some apps having notification access but this lag happens even when the phone has been reset. It's really annoying... Pure Nexus didn't have this problem.. but had to switch back cause VOLTE wasn't working on Pure Nexus.
Can someone tell my why this lag is present?
Syncsyll said:
My Moto G4 Plus is on the latest stock build NPJS25.93-14-4. The notification bar is lagging a lot. I thought it might be cause of some apps having notification access but this lag happens even when the phone has been reset. It's really annoying... Pure Nexus didn't have this problem.. but had to switch back cause VOLTE wasn't working on Pure Nexus.
Can someone tell my why this lag is present?
Click to expand...
Click to collapse
There are a Few Reasons
~ The New Notification API Introduced in Nougat
~ Your Device Simply Overheating Causing UI Stutters
And Pure Nexus Has Volte Support
electronode said:
There are a Few Reasons
~ The New Notification API Introduced in Nougat
~ Your Device Simply Overheating Causing UI Stutters
And Pure Nexus Has Volte Support
Click to expand...
Click to collapse
Thank you for your quick reply.
I posted the VOLTE problem in the pure Nexus thread but failed to get a solution as to why VOLTE wasn't working.
:/
It's because ROM kernel doesn't supports advance color control, so if you have nigh mode enabled, the UI will lag
(sorry if this has already been discussed before)
I like my second screen in AOD/standby mode to read the time, notifications, battery level ...
I recently received my second $110 lg v20 h910 from aliexpress and was ready to get to play with a lineageos based ROM (I find my stock based rom a little bloated) but I read ( https://www.reddit.com/r/lgv20/comments/agefj5/lineage_151_second_screen_not_turning_off_when/ ) that there is a MASSIVE BATTERY DRAIN on ALL the NON STOCK roms with second screen support in AOD mode when the phone is in AOD MODE ...
Could somebody please tell me how bad this battery drain is on these ROMS (lineageos 15.1 and resurrection remix with second screen support) ??? Does this make these roms unusable ??
Also it seems like development has stopped on these roms ... is that the reason why ??
(I know that there is a lineageos 16 rom with notch support for the second screen but I understand that it doesn't support AOD mode for the second screen, right ??)
Thanks folks for your lights on this subject !
Its not bad enough to make it unusable, but for me it was enough to make me have to charge twice a day instead of once. The problem is that the LG V20 has an LCD, so the whole backlight needs to be lit to be readable.
From what I get, development has stopped because the Devs are putting in all they can into Pie based roms.
Pie based roms don't support AOD, once again because of the backlight. If I understand this phone correctly (Correct me if I'm wrong, happy to learn), the backlight is split into 2 pieces, one for the second screen, and one for the rest. LG Roms used just the second screen part.
I personally love the Pie roms, dont even miss the second screen. Yeah, it was useful, but not something that made a huge difference.
Excudent said:
Its not bad enough to make it unusable, but for me it was enough to make me have to charge twice a day instead of once. The problem is that the LG V20 has an LCD, so the whole backlight needs to be lit to be readable.
From what I get, development has stopped because the Devs are putting in all they can into Pie based roms.
Pie based roms don't support AOD, once again because of the backlight. If I understand this phone correctly (Correct me if I'm wrong, happy to learn), the backlight is split into 2 pieces, one for the second screen, and one for the rest. LG Roms used just the second screen part.
I personally love the Pie roms, dont even miss the second screen. Yeah, it was useful, but not something that made a huge difference.
Click to expand...
Click to collapse
Thanks a lot for your answer ! :good::good:
Then I guess I am going to try LineageOS Pie on my test phone to see if it's worth it while staying on Nougat Alpha Omega on my daily driver (On Nougat Alpha Omega I like Zacharee "mod control" to tune the battery size in the second screen, etc ... and I am not sure if this "mod control" app is working on Oreo Stock based roms ...)
has anyone ever noticed that the phone screen flickers awfully when unlocked with a fingerprint? the screen can flash a moment after unlocking and artifacts are created in menu animations. everything takes literally half a second.
the problem only occurs on all Xiaomi.EU MIUI 12 beta versions and on the stable version. I didn't check the global version, but I think it will be the same.
it wouldn't bother me much if it didn't create terrible graphic artifacts sometimes.
Indian version doesnt have this problem
Same thing here on miui 12 betas. I was sacred that i damaged my phone in work.
Moanderdj said:
has anyone ever noticed that the phone screen flickers awfully when unlocked with a fingerprint? the screen can flash a moment after unlocking and artifacts are created in menu animations. everything takes literally half a second.
the problem only occurs on all Xiaomi.EU MIUI 12 beta versions and on the stable version. I didn't check the global version, but I think it will be the same.
it wouldn't bother me much if it didn't create terrible graphic artifacts sometimes.
Click to expand...
Click to collapse
Yep, Noticed this on Xiaomi.eu 12.0.3.0 Stable. The main thing I noticed when I installed the update.
The previous ones were smooth. The blurring is also not good on the latest, the blur goes away real quick when exiting notif bar making the transition look like you set animation to 0 on devs settings. But the exact opposite on the Control Panel. Closing it, you'll see the delay in the blur. Can see icons still blurred before it goes away. Too delayed that it is noticeable. Setting .5x on animation and transition fixes it but that awful unlocking animation flicker become more noticeable when doing so.
I hope next update will be better.
---------- Post added at 10:04 AM ---------- Previous post was at 10:02 AM ----------
zubin1594 said:
Indian version doesnt have this problem
Click to expand...
Click to collapse
Same 12.0.3.0 build? Noticed the issue on 12.0.3.0. I believe indian Stable is still on 12.0.1.0. On that build we did't have the issue as well.
It is interesting that the problem only occurs when we use the fingerprint on the screen. using the fingerprint on the screen off, does not create artifacts and flickering. all beta versions had this problem, I thought stable version would eliminate this problem.
he does not always occur. and sometimes it is strong that it looks like a phone breaks down.
I wonder what is causing this error. maybe a fingerprint mechanic?
Moanderdj said:
has anyone ever noticed that the phone screen flickers awfully when unlocked with a fingerprint? the screen can flash a moment after unlocking and artifacts are created in menu animations. everything takes literally half a second.
the problem only occurs on all Xiaomi.EU MIUI 12 beta versions and on the stable version. I didn't check the global version, but I think it will be the same.
it wouldn't bother me much if it didn't create terrible graphic artifacts sometimes.
Click to expand...
Click to collapse
Did xioami add the DC dimming option for Mi9T in Miui 12? Can anyone tell?
@projjalkhisa You can activate it easily with Activity Launcher -> Settings (the second option) -> Anti-Flicker
On Global stabile MIUI 12 it's fixed. I have EEA model, and every miui 12 custom rom have this bug (xiaomi.eu) (beta relases from china model)
dancho2000 said:
@projjalkhisa You can activate it easily with Activity Launcher -> Settings (the second option) -> Anti-Flicker
Click to expand...
Click to collapse
It doesn't work. The setting changes but it still flickers on mine.
Moanderdj said:
has anyone ever noticed that the phone screen flickers awfully when unlocked with a fingerprint? the screen can flash a moment after unlocking and artifacts are created in menu animations. everything takes literally half a second.
the problem only occurs on all Xiaomi.EU MIUI 12 beta versions and on the stable version. I didn't check the global version, but I think it will be the same.
it wouldn't bother me much if it didn't create terrible graphic artifacts sometimes.
Click to expand...
Click to collapse
Moanderdj said:
has anyone ever noticed that the phone screen flickers awfully when unlocked with a fingerprint? the screen can flash a moment after unlocking and artifacts are created in menu animations. everything takes literally half a second.
the problem only occurs on all Xiaomi.EU MIUI 12 beta versions and on the stable version. I didn't check the global version, but I think it will be the same.
it wouldn't bother me much if it didn't create terrible graphic artifacts sometimes.
Click to expand...
Click to collapse
Any solution on this yet??
this is so random. i have this problem again after few months that i didnt have it. this issue has occured to me 4 times in the last year. but this time it is the worse. phone is almost useless. what is going on....