Bug free custom rom for daily use - Xiaomi Mi A2 Lite Questions & Answers

I'm currently on stock pie and I have 3 main issues with it.
Slow wifi with bluetooth on
Screen flashing when using some apps: this one is more common on Chrome, YouTube and when pulling down the notifications tray on any app running in fullscreen
Adaptive Battery killing background apps really aggressively: if I'm playing any game I cannot switch apps for a second, the system will kill the app and I'll have to restart it. It gets really annoying when I'm playing and want to reply a message or check something online.
I was thinking of flashing a custom rom and wanted to know if there's a rom (device specific or GSI) that solved these issues, or at least some of them.

Related

[Q] InsertCoin ROM - Killing apps too aggressively?

Hi all,
This is my first post here.
I have flashed the InsertCoin stable ROM 03/06 and I have to say it's great (despite the video playback bug). Recently I found another issue that bothers me a lot.
The problem I found is that the ROM seems to be killing non-active apps too aggressively. I learnt if I press "home" button in an active app, it should stay for a while until it is killed to free up memory. However, in my phone, the non-active apps are always killed within one minute even when the phone isn't running out of memory. Why it is an issue to me? Because:
1) It is killing the browser too fast. Usually I switched to other app, do some work, and back to the browser. Since the browser is killed it has to reload the whole page to restore the state. This wastes time and data.
2) Most importantly It is killing my music app!! I tried fire up HTC's music app, select a song, tap to play, leave the app and do other things like web surfing. The music app would surely be killed in a minute. This happens to other music playing app like Winamp.
This makes my phone a relatively single tasking one. I didn't install any 3rd party task killer because I never needed one. But I cannot find any settings regarding this "feature" on my phone.
I found people in this forum seeking help on how to kill some background apps. What I want is the opposite: How to prevent some background apps to be killed.
Anyone here has similar problem and has found a solution?
Thanks in advance!
on 1.0.8 i had no problems
on v45 (which is last 2D Rose version) you need to flash pre46test.zip in order to fix agressive app killing.
other than that i never heard of any complaints regarding apps being killed too quickly.
Thanks, dzumagos. Yes I am running 1.0.8 and unfortunately this happens on my phone
Maybe I'll try flashing the nightly version (v51) to see if things improve.
Whatever you do, don't use task managers and other memory scripts. Every developer makes his own memory parameters which suit his rom the best, so I think you are best off pointing baadnwz to this issue and see what he says.
erklat said:
Whatever you do, don't use task managers and other memory scripts. Every developer makes his own memory parameters which suit his rom the best, so I think you are best off pointing baadnwz to this issue and see what he says.
Click to expand...
Click to collapse
The ROM has HTC's ROM manager built in, and I didn't have any installed by myself. AFAIK the only difference between the Stable and Nightly version is the Rosie 3D homescreen that is missing in the Stable version, so I flashed 1.0.9 and unfortunately the problem persists.
And looks like I'm not eligible to ask on the development thread

WhiteRabbit 1.5.2 Bug report thread

Since I'm a fairly new user here I cant post to the development section I'll post my bug reports here.
ROM: WhiteRabbit 1.5.2
clean installation with beatsaudio, motorola defy red lens GB kernel.
(*)FC on miui music player when choosing a file to play.
(*)false pairing on A2DP headset, says its paired yet i cant control or hear anything from the phone, music is still played through speaker.
(*)Default messaging app hides the "Enter" button on keyboard (other apps keyboards are fine).
(!) Reinstalling (not clean) without the beatsaudio (default CM7) solves the FC and A2DP pairing issues.
Hopefully this thread will be just moved into the development thread.
I had many issues with the 2.3.6 version!!
when the battery got below 26% and I tried to open any rooted app they would not open as they would get errors.
I had a few other errors and things I didnt like but I cant remember them ATM wether they where program conflicts (or lack of programs or services I choose not to install) I am not sure.
I thought it was really good, but the lack of some things put me off it and I liked the go launcher but I can put that on any ROM!.
I now run CM7.2 latest by quartx with V6 supercharged and cant be happier. Fast enough and battery usage is minimal with using the power control panel and everything turned off apart from 3G. Got rid of JuiceDefender now and just use the control panel I can turn things off and on when I like on the main screen so no hassles

Music distorting on ICS?

I experience music distorting when I hold down my home button key (to get to recent apps) or sometimes taping different places on the phone . It doesn't happen with the stock music player(only happens with apps like Player Pro, Power Amp, N7 player, Music Mod, Datpiff) and I know it's not my phone or a bad download.. Because all other audio on my phone is fine (YouTube, phone calls, stock player, alarm sounds etc).. Kinda bothering me especially since I shelled out money for some of these music player programs which are now useless (got them while I was on Gingerbread and never had that "distorting problem)
*Set up is in my signature of what I'm currently running*
When your running your music app try and see if you get any CPU spikes. Sounds like your ram could be running low . Since the real source code for Ics is coming soon that could fix it. have you tried rebooting your phone? I know your running blu Kubans ROM. Go to the updater and try another kernel. These are just thoughts so my two cents may not help any.
Also did you notice these issues before any of RUs updates? if not try to revert back to one of the other updates or even ask him on his thread
juggalo1300 said:
When your running your music app try and see if you get any CPU spikes. Sounds like your ram could be running low . Since the real source code for Ics is coming soon that could fix it. have you tried rebooting your phone? I know your running blu Kubans ROM. Go to the updater and try another kernel. These are just thoughts so my two cents may not help any.
Click to expand...
Click to collapse
juggalo1300 said:
Also did you notice these issues before any of RUs updates? if not try to revert back to one of the other updates or even ask him on his thread
Click to expand...
Click to collapse
What app would you recommend to monitor cpu spikes. And if my ram is running low how could I fix that?
I've tried different kernels (agats numerous ones). And no avail.. Also tried rebooting.. But it had happened on all the updates, tried asking on the thread but I'm the only individual with the issue
I just use a stock player im not picky. I went back to GB roms so I use the ROM manager to see how much ram is being used. For the CPU I'm sure the market has some apps for CPU usage. Have you tried clearing the cache for the music apps you own? are they up to date? They may not be compatible with ics roms yet.

Weird notification drawer lag on any 4.4 based ROM

I have this really weird lag when I'm on ANY 4.4 based ROM no matter what kernel or gapps package I use. So I install the ROM and its all great but I start travelling and after sometime the notification drawer is all laggy and stuttering like never before. I thought it could be a GPS issue and tried disabling wifi, gps and mobile data but no luck, I also tried clearing app cache, doing a clean wipe and reinstalling ROM, trying almost every 4.4 based ROM out there. All I did was do a Clean install (factory reset, wipe dalvik, cache, system) from TWRP 2.6.3.2, configure the accounts, install superSU from playstore and update binaries, install TiBackup and restore user apps with data. It was still smooth until I leave work/home/travel somewhere. Anyone else facing this issue? Other than this weird lag, the UI is buttery smooth (no lags on homescreen, app drawer, opening and closing apps, etc) and even the RAM usage is quite low (<300MB). I cant seem to figure out what could be causing this. Please help me.
PS: the notification drawer lags ONLY when there are no notifications or when there is a permanent notification. When I get a dismissable notification it doesnt resemble any lag at all!
Thanks.
Is it only with 4.4 ROM's?
isajoo said:
Is it only with 4.4 ROM's?
Click to expand...
Click to collapse
Yes.
the phone is pooping itself because Google messed it up
droidnxs said:
It was still smooth until I leave work/home/travel somewhere.
Click to expand...
Click to collapse
Me too (latest Cm11 nightly + Mpokang 1080p + Nephilim's settings)!!
:crying:
Shambola said:
Me too (latest Cm11 nightly + Mpokang 1080p + Nephilim's settings)!!
:crying:
Click to expand...
Click to collapse
Know that feel bro. If you run into any solution please post here or PM me. If this gets fixed it'll be the best thing to ever happen for our GNex. :fingers-crossed:
i'm on the 12-16 Nightly on CM 11 and i dont have any problems or lag ill keep you updated as i start to add apps and tweaks
GalaxySubie said:
i'm on the 12-16 Nightly on CM 11 and i dont have any problems or lag ill keep you updated as i start to add apps and tweaks
Click to expand...
Click to collapse
I'm also on a recent nightly, and although I don't *feel* any disturbing stutter in notification drawer, it isn't quite as smooth as what's on my Nex4. Now, as the OP has hinted, I tried getting a dismissable notification in the drawer and boom, the drawer is suddenly as smooth as hell - but only for seconds. Wondering why...
Sent from Samsung Galaxy S Relay 4G @ CM11
I have loaded app and stuff and i still have not seen any sort of lag.
When you are flashing are you wiping the device correctly it may still have files that will slow it down.
Sent from my SCH-I545 using Tapatalk
GalaxySubie said:
I have loaded app and stuff and i still have not seen any sort of lag.
When you are flashing are you wiping the device correctly it may still have files that will slow it down.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I do a clean flash as I stated previously. Factory Reset, Wipe dalvik cache, system, cache, Flash ROM, Gapps (dhacker29's latest), and reboot. Since I use TiBackup to restore, I also download SuperSU from playstore just to update binaries and make TiB work, I uninstall superSU after that and use the built-in superuser app.
I got that problem too!firstly i thought i was a bluetooth issue as i turn on the bluetooth and the notification drawer become laggy.but after a while i found it laggy continually even if i turn off the bluetooth.it's really a annoying thing
geekbrain said:
I got that problem too!firstly i thought i was a bluetooth issue as i turn on the bluetooth and the notification drawer become laggy.but after a while i found it laggy continually even if i turn off the bluetooth.it's really a annoying thing
Click to expand...
Click to collapse
I know right? Once I disabled Wifi optimization as it was on, and it got smooth again, but that wasn't the end. I went to work and pulled out my phone, and boom, its all laggy and stuttering again. A few hours back I gave KitKat another shot but this time it was laggy even after the clean install without any apps restored. This is the weirdest thing to ever happen to my GNex. Now I'm back on AOKP 4.3.1 M1 with Tiny Kernel 5.4 with the smoothest android experience ever. Let's wait for the developers to take a look into this issue. :fingers-crossed:
Okay I think I found a solution. I tried 5 use-cases:
Flash method: Clean - Factory reset, wipe dalvik cache & cache, wipe ROM, flash ROM, gapps
1. CM11 ROM with built-in kernel
2. CM11 ROM with Tiny 5.4 kernel
3. CM11 ROM with built-in kernel
4. CM10.2.0 (stable) ROM with built-in kernel
5. CM10.2.0 (stable) ROM with Tiny 5.4 kernel
I noted that when I did not flash a 3rd party kernel the issue seemed to persist even at first start-up. But when I flashed a 3rd party kernel (be it any compatible kernel) there was absolutely no lag at all. But then the question of why I tested it on CM10.2 ROM is because I found the same notification drawer lag on CM10.2 (official) ROM. Maybe this started after the ram-disk was changed? (I'll leave that for the developers to decide).
Note: I'm currently on Gummy 21-12-13 build with Tiny 5.4 kernel, ART enabled. When I started off to work today I wanted to switch to 3G and when I did so the lag was back, but after it found a signal tower it disappeared. I have found no lag so far.
Something off-topic : But commonly throughout these tests, I found that these ROM's exhibited terrible lag when using live wallpaper.
If someone (facing the same issue as stated in the OP) can confirm that the above solution works, it will help alleviate the problem.
Edit: Also found in tricksterMOD that the deep-sleep mode was in the 'unused states' category.
Bump
Okay I guess the problem hasn't been quite solved yet, bumping so people can have a look at this.
Update:
In the recent builds notification drawer lags only when I'm not on Wifi no matter what KK ROM+Kernel combo I try.
droidnxs said:
Okay I guess the problem hasn't been quite solved yet, bumping so people can have a look at this.
Update:
In the recent builds notification drawer lags only when I'm not on Wifi no matter what KK ROM+Kernel combo I try.
Click to expand...
Click to collapse
I'm on CM11 with Fancy kernel. I also see the lag when not on wifi. It really has not bothered me. The KK ROMs are still fairly new, so I would just give it some time.
Break me off a piece of that Kit-Kat ROM!
TheMan0790 said:
I'm on CM11 with Fancy kernel. I also see the lag when not on wifi. It really has not bothered me. The KK ROMs are still fairly new, so I would just give it some time.
Break me off a piece of that Kit-Kat ROM!
Click to expand...
Click to collapse
I just wanted to confirm if it was really a bug or something that was specific to my phone. That confirmed the former, thanks!
Just wanted to add my thoughts on this. Are you guys using the Google Experience launcher with the "Ok Google" Hotword Detection? If so, turn off the hotword detection in settings. After doing that, I get no lag whatsoever in my notification drawer. I didnt use that feature that much anyway.
Still no dice on this issue? Not intentionally bumping, but I think this issue might have a deeper cause that requires more attention from devs.
I've read through the "suggestions" above and I can say that nothing works. What I have is a VERY clean CM11 + Franco r395 - no Gapps, no Google Experience Launcher, no Google Now (Google Search is force stopped and its shortcut removed), very few installed apps, no background apps except for input method, lots of free RAM (~520MB), yet this still happens. Only thing that removes the lag temporarily is an incoming notification, which only makes it smooth for seconds.
Sent from Google Nexus 4 @ CM11
Okay, tried many JB ROMs and they all don't have the lag. Try one of the KK ROMs and they come back immediately. Something with KK source?
Sent from Google Nexus 4 @ CM11
One more update: flashed latest CyanogenMod nightly (CM11 20140325) and I surprisingly discovered that the notif lag is gone. Turns out I'm wrong, as the lag is gone only in lockscreen and Trebuchet. However, on second thought, does this phenomenon mean that CM/Trebuchet recently implemented something that potentially removes the lag? What patch is it exactly, and why isn't it applied on other apps?
I still think that this "simple and bearable" problem has a darker side that requires more attention.
Sent from Google Nexus 4 @ CM11

Memory consumption with lollipop

My lollipop experience is this: battery life seems OK but less than I was getting with the elementalx kernel, the sound stutters especially when the screen is locked. Its pretty random but the buffer is underrunning at times. Which leads me to what's bugging me the most. With KitKat and the same apps installed I was getting roughly 800mb-1gb free of memory. With lollipop it starts out OK at boot but quickly starts eating up ram like candy. I've had Pandora force close in the background which is probably why I'm getting sound stutters because something is using memory and force closing services in the background. I'm using apex launcher and that constantly has to reload to. Before it very rarely reloaded. Also various widgets are having their services killed and I have to go and manually restart them. I've gone from 1gb free typically to like 3-400 mb free. Does L really use that much more ram? Also what about the damned "focus" on battery life they claimed? Its definitely worse here. Looks like this update was half baked if you ask me. I'm at least not getting horrible fps in games like some are claiming. And yeah the YouTube bug is really random and annoying. Anyone else have low memory issues??
Sent from my Nexus 7 using XDA Free mobile app
Same issue. But found the soultion
Facing the same issue. But what i came across is that maximum people who updated to lollipop via OTA are facing these.
Others who have side loaded it or flashed the new lollipop image are all fine. There are bugs in lollipop but atleast they are not facing the terrible issues like us. That battery life is insane , i cant use it as my daily driver with such pathetic battery life. But people who have updated it other than OTA are infact getting better battery than KitKat what Google claimed it to be.
Also the memory issue. Yes this is the main problem what we all OTA updaters are facing. This is called memory leak. I founded it over here. Few developers have explained it in detail - You should have a look.
They have suggested for a clean install of lollipop by complete flash or a factory reset. I have not done it yet. Too lazy to get the backup and all.
But have to try it as we are left with no other option. Check out this link for memory leak - tinyurl.com/pmjlol2
If you decide to install it yourself, use one of the current builds instead of the factory image. Google has pushed a few revisions out.

Categories

Resources