I'm using a Moto G 1st gen with CyanogenMod 13 official nightly. The memory used by system in the first few hours after boot is about 300-350MB. But after that it increases constantly and then reaches up to 500MB. That is only the memory used by system.
During first few hours (Attachment 2)
After many hours (Attachment 1)
I know that in Android a full memory is a good thing and it is not like Windows, but my phone slows down and starts lagging a lot when all the memory is eaten up by the system. I have tried going into safe mode, uninstalling xposed, disabling certain apps I thought to be the cause of the problem, upgrading to the latest nightly, updating gapps, beating my head against a wall, etc. but I couldn't figure out the problem. Please help me if you can and if you need any additional information please tell me.
I would also same thing is happening with MM, but not all roms
That is something that almost all roms present. Not only in marshmallow, i've experienced this in 12.1 especially in cyanogenmod based roms.
Related
Hi Xda, to start sotty for my bad english.
i've a strange bug on my moto g
i've use for many time Cm11,cm12 and others aosp based rom without problems,(my moto g have 16 months) but now , from about two months when i install aosp based rom when i reboot my moto lost data and time everytime., also in TWRP and Philz recovery data is wrong.
instead if i flash stock rom, Motorola or GPE everything work perfect, in recovery time is wrong but when reboot is not lost time.This forces me to keep the stock rom, because on AOSP i've problem with messaging programs like whatsapp that tell me wrong data every reboot, or with data monitoring programs.
I've investigated and i think is a bug related to time_daemon service...but i don't find a solution...i think is change something on aosp sources but I can not understand why this problem occurs only for me.
Can anyone help me?
I'm fairly new at using custom ROMs on my phone (Moto G 2013 XT1304) and I want to get some answers that I've not been able to find, at least clearly, on my own. I'll ask all in one go in case others might benefit. I appreciate any help or confirmation in response.
GAPPS
Following the guide on xda, I installed CM 12.1 successfully and also installed the gapps package from July located in the cgapps site (can't post links yet). I was confused about the other option being called "OpenGApps" and thought they were the ASOP vs Google version. Once booted, Google Play Services updated but I've still had a few "Google Plays Services has stopped working" issues. My question is this, should I reflash and use the latest nano install from OpenGApps or does the play store update these relevant apps and framework once up and running anyway? Which is best?
Nandroid Backups
I want a way to fully backup the entire phone and system so that I can fully restore if something should get botched - something like a full drive image on a computer. Using TWRP backup, if I were to backup the system, data and boot partitions, would restoring those to a completely wiped phone bring it back to the state it was in when backed up? And do those partitions need to be wiped before restore or does the restore process do that anyway? Last, is is this the best way to do this sort of backup?
ROM updates
First, if "Check for Cyanogenmod updates" is set on the phone, and I have a snapshot installed, will this only provide an update if another snapshot is released? If not, how does that work since there is a new nightly releases every day.
Second, I've read a lot of negative about downgrading ROMs, but it seems ok to flash a newer version of the same one while keeping the data in place. Is this correct? Is there a "best practices" post on this somewhere?
I'm experienced with Linux, and feel somewhat at home with Android because of that, but I only switched to CM12.1 recently because Motorola had done nothing about the choppy bluetooth audio in the Lollipop update for the Moto G 2013. I use the feature extensively and it was left too broken to enjoy, but works perfectly in the CM ROM. Now I'm hooked and want to go further. Thanks for any help or direction.
Moto G 16MB (2013)
CyanogenMod 12.1 (Snapshot 11/17)
TWRP 2.8.7.0 (h2064)
Hey folks, first of all, sorry but I couldn't find anything that helped.
I have a Galaxy Note 4 (SM-N910F (international Version); Codename: "trltexx") and had flashed an unofficial version of Cyanogenmod 14.1. Except for a few bugs, it was running fine.
I've then changed to Lineage OS 14.1, obviously unofficial as well. This was running fine too and had less bugs (i.e. camera was working unlike with CM).
Well, then, after about a week or so, the phone became unstable and just won't recover from it since then - at least two weeks.
System and Play Store apps/services began to crash (sometimes several at once), the device restarts/turns off randomly or keeps displaying the boot animation and won't turn on till I take the battery out and put it back in.
The weird thing is, these problems sometimes don't occur at all and everything runs nice and smooth and later, everything starts again and is even worse. It feels like the phone is destroying and recovering itself over and over again.
Right now, I'm running the latest version of Ressurrection Remix OS (V5.8.1./Android 7.1.1).
Well, I'd like to thank you in advance for your answers.
User422 said:
Hey folks, first of all, sorry but I couldn't find anything that helped.
I have a Galaxy Note 4 (SM-N910F (international Version); Codename: "trltexx") and had flashed an unofficial version of Cyanogenmod 14.1. Except for a few bugs, it was running fine.
I've then changed to Lineage OS 14.1, obviously unofficial as well. This was running fine too and had less bugs (i.e. camera was working unlike with CM).
Well, then, after about a week or so, the phone became unstable and just won't recover from it since then - at least two weeks.
System and Play Store apps/services began to crash (sometimes several at once), the device restarts/turns off randomly or keeps displaying the boot animation and won't turn on till I take the battery out and put it back in.
The weird thing is, these problems sometimes don't occur at all and everything runs nice and smooth and later, everything starts again and is even worse. It feels like the phone is destroying and recovering itself over and over again.
Right now, I'm running the latest version of Ressurrection Remix OS (V5.8.1./Android 7.1.1).
Well, I'd like to thank you in advance for your answers.
Click to expand...
Click to collapse
Greetings and welcome to assist. Have you tried asking in the rom threads to see if anyone else is having the same issues ? Unfortunately using cm/lineage based roms can have bugs as they are not based on samsung firmware
Regards
Sawdoctor
Hi, thanks for the answer. I wanted to say that I went down to resurrection remix Rom which is based on Android 6 (Marshmallow).
It's fine now.
Now I'm just looking to find a way to hide my root. Can't use my banking app anymore since I've rooted my device.
Update 2: The phone problems I have described reoccur over and over again. A factory reset via TWRP fixes that and then the phone slowly goes back to the old problems.
I don't know what to do anymore except for doing this over and over again.
I have a Moto G running Lineage OS. This has been running fine for a couple of months now. However, a couple of days ago it turned itself off and wouldn't go past the Lineage boot animation.
After reading several threads I tried clearing all data from the phone and reinstalling Lineage. Then it worked for two or three days and then the same thing happened.
Does anyone have suggestions other than reinstalling Lineage again?
What might be the cause?
did you make any modifications to /system? what and how you flashed? maybe you should try with another rom
Did you try logcat? A moto g in my household had a symptom like this due to a bad line in the wifi network history file. But there could be any number of other causes. Logcat should give some clue.
Sent from my Moto G (5) Plus using Tapatalk
I followed the instructions on the page doe the Falcon rom a couple of months ago. Everything worked fine. I made no modifications to system or anything else.
I read some posts on that the battery might be the cause. Is that plausible?
I've had a strange issue with my LG V20 ever since I got in last year and installed LineageOS 18.1 after rooting my H990 on LG firmware 10d (H990ds10d_00_OPEN_AU_DS_OP_1216.kdz) with DirtySanta and installing TWRP. Whenever I left the range of my Wi-Fi network, I would cause the System UI to become unresponsive while doing certain tasks - Unlocking, going to Settings -> Wi-Fi, expanding the Wi-Fi quick toggle in notifications, and probably a few more things.
This doesn't happen on the aforementioned stock firmware, nor on 10g AU 0117 stock firmware either.
For a while, I dealt with it by simply not using Wi-Fi. This sucked because I couldn't access computers over LAN, mobile data was slower, and it also had a data cap that I had to be wary of.
However, I decided I wanted to fix it.
I saw some recommendations involving installing every Lineage version since 14.1 sequentially until the latest. This didn't make sense to me, as clean flashing shouldn't leave any remnants behind, but dirty flashing that many versions went against everything I'd ever heard of regarding custom ROMs.
I also heard that it could be a modem firmware issue. Since I started on the last version of the stock OS for my region vulnerable to DirtySanta I thought surely not.
I later found out about KDZWriter, and used that to install the latest Nougat version of the stock rom available (also mentioned above). After installing that, I tried installing the latest LOS on top, which constantly informed me that com.android.media had stopped, I still had the LG sounds and wallpapers, and I didn't go through the initial setup - A sign of a dirty flash. I was still crashing in the same way too.
I formatted my data partition in TWRP (the "type yes to confirm" way), and tried again. Same crashes.
I've been awake for a little too long trying to fix this, but :
What I believe ended up working was backing up my /efs and /firmware partitions in TWRP while on rooted 10g firmware, dirty flashing LOS on top, formatting data as before, then flashing my /firmware backup in TWRP.
I'm hoping for this thread to document this issue as well as the fixes that worked for people. I saw tidbits of information spread out everywhere, so I'd like a central repository for it.
I hope this caffeine-induced writeup will help someone else with the same or similar issues.
If I have any more experiences with it, I'll do my best to write them down. Please share your experiences too!