yashsingh1/xdaforums huggingface dataset:
[Moto G Original Android Development] michael_ch:
Sure, I'll try to provide some real numbers about this. For now I can tell that the number of launcher redraws has been reduced from ~80% to ~5% of all times when I open the launcher. My usage scenario is usually just Gmail and TweetCaster, my launcher is Google Now Launcher. So it's always about the same apps, but the minfree change clearly does make a difference!

Ok I've read that post but I think that you are understanding it wrong!

He says that changing the

permissions

does not have an effect, and that's true. This was the main "feature" of the minfree fixer that was presented in the mentioned thread. However, I'm only changing the permission so that I can read the value for myself. I have used that for debugging the problem, and stumbled about the big difference compared to the stock ROM.

Now what Ethan did not write is that changing the

value

will certainly make a difference, because that's why the file is there after all!

Please stop repeating that this is all about placebo and give it at least a try. I'm sure you will notice the difference easily...

Here's the code that you need to try:

echo "8192,10240,12288,14336,16384,20480" > /sys/module/lowmemorykiller/parameters/minfree

No need to change permissions if you don't like that, because I know your value already ;) It's defined right here and I tell you it's wrong because someone changed it based on pure feelings (read the commit message).

Next steps:

1. I'm going to submit a patch which reverts https://github.com/CyanogenMod/andr...mmit/0ef11bcb65d493fcf354f2212b4596a846618199

2. Additionally, revert https://github.com/CyanogenMod/andr...mmit/bff4d905bc8bc88b78cf96442f42c3ea711f0992

3. Change the config_lowMemoryKillerMinFreeKbytesAbsolute value to 81920.

This results in exactly the same minfree values as on Stock Moto G (8192,10240,12288,14336,16384,20480 - see above).

(The reason why I did not submit the changes yet is because I cannot access my Gerrit account right now. Waiting for feedback from CM ops...)
[Moto G Original Android Development] michael_ch:
Ok, here is a reproducable scenario. Please try this 1) with the original settings and 2) after changing the minfree values:

1. Open Google Maps, choose a destination and start the navigation to it (arrow icon appears in the notification menu).

2. Go back to the launcher, open a music app, start playing some music (in my case I started PocketCasts for that)

3. Go back to the launcher, check mails with Gmail

In my situation, the notification entry for Google Maps disappears usually when I open the 2nd foreground app (in this case it's PocketCasts), but definitely after opening a 3rd app. It also happened to me that sometimes the music stopped when opening another foreground process.

However, with the new values, Google Maps stays in the notification area and the music keeps playing. That's how I expect things to work!
[Moto G Original Android Development] hurtsky:
i believe, we can solve this problem by just disable this CONFIG_ANDROID_BG_SCAN_MEM=y in kernel config. with it our lmk aggressively try to free up our RAM space.. in my testing, with and without this, lmk reduce it scanning moderately.. i can open music plus playing game and without having launcher redraw.

maybe some patches from motorola also may do good, because latest cm kernel did not have this patch https://github.com/MotorolaMobilityLLC/kernel-msm/commit/f3383a39cc2569ccbaa6c08212cd6665b36d283a
[Moto G Original Android Development] objr:
It's no placebo effect!

Those values this the magic for me!

They worked!

I wonder if they'll remain even after I reboot my device or do I have to manually insert those values again!?

Inviato dal mio Moto G utilizzando Tapatalk
[Moto G Original Android Development] mato_d007:
Im pretty sure is not placebo, is very noticeable. I mean, with stock lmk values i just need to open facebook on chrome and the launcher will most likely be killed. This is not happening with the modified values I posted earlier. We have to find a way to make this easy to test, in a "scientific way". Maps+music+Chrome in a heavy web page like The Verge or something like that.
[Moto G Original Android Development] LuizHenrique91:
Quick tip: use Kernel Auditor (https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor) for creating profiles for LMK. First, backup the current setting as a profile, then change freely, but always creating one profile for each set of values.
[Moto G Original Android Development] tzzeri:
It was already discussed. But your right, it can improve performance a lot
[Moto G Original Android Development] sjandroiddeveloper:
Try using facebook + chrome

When you are using fb and you open a page in chrome the fb app is most of the times killed and takes 6-7 seconds to start again ( sometimes even >10 sec)

And just for everyone's Knowledge the facebook app is a massive ram eater
[Moto G Original Android Development] t4n017:
Feeling the phone/multitasking smoother could be placebo, I give you that. But, since I changed lmk values I never had a launcher redraw again, and I'm not the only one (read the comments above).

It isn't easy to deny that, even if minfree file permission is read only, modifying the values makes a difference.
[Moto G Original Android Development] michael_ch:
I agree about the missing patches (there were 4 commits since the last merge into CyanogenMod which ended at 8c715323f6cfb5ac3bbe6b760fc3a1d32aef64eb) and will try them out next.

However, I'm not sure about disabling CONFIG_ANDROID_BG_SCAN_MEM=y. It was introduced by Motorola and seems to be used in their stock kernel, too:

https://github.com/MotorolaMobilityLLC/kernel-msm/commit/7c08a87468ea61e55a918c0665a6c215a9a3b896

https://github.com/MotorolaMobilityLLC/kernel-msm/commit/38fe5a90c6fe78689d9e4f4b5f68f597498ce0c7

I also don't see the need to revert it because after changing the minfree value (see my last comment) the system works just fine...

---------- Post added at 06:32 PM ---------- Previous post was at 06:31 PM ----------

Final summary: https://jira.cyanogenmod.org/browse/NIGHTLIES-1361
[Moto G Original Android Development] Eurofighter_ty:
and what is the conclusion ? It will be fixed or not ?

I don't know what the f*ck I did but the system started consume 600+ MB !!!!! with just 50 MB of free RAM and apps about 200 MB. It's a serious memory leak but I don't know how the hell it's started.
[Moto G Original Android Development] bogante:
For this you need to use a PC right? Can you give me a hand or something easier?
[Moto G Original Android Development] michael_ch:
Use Kernel Auditor and set the values to 32, 40, 48, 56, 64, 80 (all in MB).
[Moto G Original Android Development] hurtsky:
yup, there are 4 more commits need to pick and i already done it in my kernel changes.

not by reverting it, just disable it in config, stock motorola rom also had suffer with their own ram management. and also many kernel modder from another phone also picking useful commits from motorola also had problem when this config enabled. They found that CONFIG_ANDROID_BG_SCAN_MEM really aggresively scan and kill apps even there is plenty of free RAM and makes them keep restarting with just dying apps, most of them did not enabled this feature... and yes, the way you suggested, also will work.. I just providing my suggestion in kernel way seems its more easy.. :D
[Moto G Original Android Development] luca020400:
Today I'll compare stock Motorola defconfig & cm one

I already added missing commits , but maybe I missed some of them
[Moto G Original Android Development] objr:
How do I disable that "config" in kernel?

Do I have to disable it in the build.prop?

If yes, which is the string, line...

Inviato dal mio Moto G utilizzando Tapatalk
[Moto G Original Android Development] michalurban:
Guys, I was going to unlock my second Moto G (I had sold my first one but then I saw a great offer so I bought another xt1032 again lol) and install CM12.1 ... but now I'm a bit confused of the last few pages here. I suppose something is wrong right now and the CM ROM is not good for use ... ?
[Moto G Original Android Development] UltraMaks:
Can someone tell me if I can submit a bug?

As I did not see any answer here for my question

I think I need to post it somewhere on a developers bugtracker sitw
[Moto G Original Android Development] Shub77:
Confirmed, it happens on my phone too. I dont' now where to submit bugs to devs, tough. :(
[Moto G Original Android Development] matmutant:
CM12.1 is perfectly usable, the only issue is the little lack of multitasking habilities that is inherent to the very low amount of RAM on the device; the "issue" is how to optimize it to get the best we can with it ... (and at the moment if you dont use any RAM hungry apps like Facebook or google maps you should still be able to multitask : i can swap between hangout/Opera/9gag without any launcher redraw and only rare page refresh on Opera; if people wanna know the REAL multitask struggle they can try the old 1GB limited netbok i'm using right now...)

There are also a few things that bother me with CM12.1, nothing that could prevent a day-to-day usage : Read here

So you can definitely install CM12.1 on your XT1032 :cool:
[Moto G Original Android Development] Rendoqoz:
I can only agree. I've tested many ROMs after unlocking bootloader and installing custom recovery, but I found myself going back to CM 12.1 all the time. I'm now running CM 12.1 and it's good daily driver for me. Perhaps this RAM management is something that needs to be worked on, but I've used Root Booster from Play store and seems like system is more stable/faster than with stock CM 12.1 (I couldn't call it placebo effect).

However, as I'm interested in daily builds, I usually skip a few builds and always like to update asap. This has sometimes led to some unforeseen performance drawbacks (only one with one-two builds that were faulty). But since I do not host critical files on my phone, I've done many clean installs to be sure I'm in good condition (vs dirty flashing).

To sum it up: CM 12.1 is my choice of OS despite trying many of other custom ROMs. Stable, fast and elegant + gives me the options I need :)
[Moto G Original Android Development] michalurban:
Thank you very much for your answers! :) I suppose from them answers you consider CM12.1 nightly to be a better than stock 5.0.2 ... I thought there was some memory leak or something.

As for the RAM - I know people are against task killers, but I'm using Advanced Task Manager for many months and I'm happy with that. I added all my daily apps to the not-kill list (eg. launcher, messenger, viber, opera, all my widgets ...) and set it to kill apps every 5 minutes. I see no decrease in battery life and everything is much smoother. Before this, after few days of uptime the launcher (apex) kept reloading, now it doesn't and other apps are fast to load and multitask fine. After two days of use I have circa 250MB of RAM free. And I remember having about the same amount after a week. I usually restart the phone once a week.
[Moto G Original Android Development] LuizHenrique91:
About the RAM, my experience is way better now. I unninstalled Facebook and defined LMK values based on values from stock Moto G ROM.
[Moto G Original Android Development] sjandroiddeveloper:
You can consider CM 12.1 better than stock 5.0.2 because the android 5.1 brought many bug fixes one of which was fixing memory leak

Like said before there are some problems with multitasking currently but I am sure devs will be able to fix it to a certain level ( not completely as 1gb is after all a low amount of memory considering today's standards)
[Moto G Original Android Development] matmutant:
This app is evil...

I personally use greenify, it may help a lot, both regarding RAM and Battery life as it prevents all unused services to keep the device awake. (the only non-greenified apps on my device are Hangout, Telegram, and a few tools/widgets ==> see why below)

Contrary to task-killer, apps won't restart and being kill every once in a while : they will stay in an hibernated state instead (thus they won't be able to receive notifications... or refresh their widgets)

:cowboy:
[Moto G Original Android Development] LuizHenrique91:
If you use Xposed, you can even greenify Hangouts, Telegram and any other app wich use Google Cloud Messages.
[Moto G Original Android Development] michalurban:
"uninstall facebook"? You mean Facebook or Messenger? I need Mess., because I have people there who refuse or cant use say Viber ...
[Moto G Original Android Development] LuizHenrique91:
I only unninstalled Facebook. I have Messenger installed (greenified).
[Moto G Original Android Development] michalurban:
Could you tell me where is this discussed, please?

I never before defined LMK values and dont know what the stock values are. :)
[Moto G Original Android Development] UltraMaks:
I wonder do CM's developers know about this issue?

matmutant, any ideas? :)
[Moto G Original Android Development] bigas:
Have you tried FACEBOOK LITE?

OK, it's 2000's internet, but everything works!
[Moto G Original Android Development] michalurban:
Thanks, but I can't install that (neither from phone nor PC browser).
[Moto G Original Android Development] LuizHenrique91:
You can download from apkmirror, but I recommend Tinfoil for Facebook.
[Moto G Original Android Development] sjandroiddeveloper:
Here you go
[Moto G Original Android Development] bogante:
Are you using Opera or Opera mini?
[Moto G Original Android Development] matmutant:
I used Opera Mini for ages (since CM6); and migrated to Opera a few months ago, since Opera features both "standard" (it behaves like a normal browser) and turbo (it behaves like Opera Mini and gets compressed data from Opera servers)

I also use Opera 26 on my Linux Mint 17.1, but i really miss the light presto machine that was in use in Opera 12...
[Moto G Original Android Development] michael_ch:
see:

- http://xdaforums.com/showpost.php?p=61229725&postcount=2899

- https://jira.cyanogenmod.org/browse/NIGHTLIES-1361
[Moto G Original Android Development] michael_ch:
Hmm, so you are saying that https://github.com/MotorolaMobilityLLC/kernel-msm/commit/7c08a87468ea61e55a918c0665a6c215a9a3b896 and https://github.com/MotorolaMobilityLLC/kernel-msm/commit/38fe5a90c6fe78689d9e4f4b5f68f597498ce0c7 harm more than they help? Hmm... I'm giving it a try now. Will let you know.
[Moto G Original Android Development] aqswde123:
I tried cm12 couple of Months back, loved it but had to switch back to stock gpe due to battery reason. The gpe gave me 2 hours more SOT. Has the battery usage been improved because I would like to switch to 12.1
[Moto G Original Android Development] matmutant:
:)

No idea, with CM12.1 my XT1032 could last about 2 days and a half if i wanted to... but i plug it every evening :cool:

Nevermind, you might be interested in reading this article about battery life :cowboy:
[Moto G Original Android Development] tzzeri:
Nice article.
[Moto G Original Android Development] michalurban:
I'm sorry for possible OT but I have a problem. I unlocked my bootloader, flashed twrp from OP, made Stock ROM backup, installed CM12.1 nightly 0609 and everything went fine. Then I wanted to return to the Stock ROM to check something, so I made CM ROM backup, then wipe, then reboot recovery. But when I try to restore my backup (either Stock or CM), TWRP says:

"E:Cannot restore System -- mounted read only."

And that's it. I can flash CM files though. Any help, please?
[Moto G Original Android Development] sjandroiddeveloper:
That is a bug in the latest TWRP 2.8.6.0.1 by [MENTION=4792450]h2o64[/MENTION]

I already reported him the issue, so maybe he will fix it when he gets time

Use the version 2.8.6 its bug free
[Moto G Original Android Development] michalurban:
Thanks man, you saved me a lot of cussing and reinstalling! 2.8.6.0. works! :)
[Moto G Original Android Development] UltraMaks:
It seems like I became an invisible man :(

Guys, how do I (someone else) confirm a bug for CM12.1? I see that since it started there was no any fix for this (I mean crashing of trebuchet when pressing direct dial or contacts widget)!
[Moto G Original Android Development] sjandroiddeveloper:
[MENTION=2736373]michalurban[/MENTION] Dude press thanks instead of saying it
[Moto G Original Android Development] michalurban:
I would love to but my thanks are depleted for the day ...
[Moto G Original Android Development] matmutant:
When it crashes, simply send the bug report :)

report > submit
[Moto G Original Android Development] tzzeri:
Depleted? Never happened to me
[Moto G Original Android Development] DjFrantec:
can it work on ma htc vivid
[Moto G Original Android Development] UltraMaks:
Just did it :)

I saw in report that it's related to java.lang.NullPointerException. I wonder how soon it's going to be fixed. Seems like no one uses these widgets so devs do not know about this issue
[Moto G Original Android Development] michalurban:
Is there a way to prioritize PIN request? Feels weird to be able to go through my calendar and tasks entries in widgets long before asked to enter PIN ...

---------- Post added at 01:11 PM ---------- Previous post was at 12:49 PM ----------

XDA says I have eight thanks for a day and I already used them up. It's not the first time this happened to me. :cyclops:
[Moto G Original Android Development] matmutant:
This can only happen to people that really use the button for its purpose : avoiding "thank you" posts :silly:

edit :

PIN is meant to prevent people from using the SIM card and the call function (and not the calendar, contacts...), an Android device works perfectly without any, if you want to protect the device content itself, then you need to use a screen lock security :)
[Moto G Original Android Development] tzzeri:
This is in the Moto G section.
[Moto G Original Android Development] UltraMaks:
I wonder is it possible to decrease the time for ancient display to light up after it has been automatically switched off.

Sometime you read a book and then walk away from the phone and as you're back the display just become dark. Trying to pass by the hand over the phone and only after a several passes (seconds) it lights up

... and what if I'm very nervous and want the display become active immediately :)
[Moto G Original Android Development] michalurban:
If I could have thank-you-buttoned him :D I would have. As I couldn't have, saying thanks seemed to be the best alternative at the moment. ;)

I may well go back now and thank him. :cowboy: :)

PS: Done! ;)
[Moto G Original Android Development] matmutant:
Press the Emergency [read "power"] button, the screen will light up instantly ;)
[Moto G Original Android Development] LuizHenrique91:
Does someone know what is the default ZRAM value for XT1033 on Android 5.1.1?

--

Edit: it's 168MB
[Moto G Original Android Development] UltraMaks:
workaround, ah? :)

BTW sometimes I see that "ambient display" starts failing. If the display is black and I press power button I see that the display lights up for a moment and then becomes black again. And I cannot unlock device any way. Passing over the sensor, pressing the power button only lights up for this small moment so you have no time to unlock the device. I tried to call on my phone at this moment and saw that display was staying black (locked). The only thing that helped me in these cases - pressing power button for a long time to reboot it

But as I know this bug has bin discussed several times here so devs probably know about this "ambient" behavior
[Moto G Original Android Development] tzzeri:
Wow! You're so smart! That's a brilliant idea, I didn't even think of it. You mean you can actually turn on the display with the power button?
[Moto G Original Android Development] sjandroiddeveloper:
Really is it possible on moto g

Man it even beats ambient display as a way to wake display
[Moto G Original Android Development] matmutant:
I had no better answer xD

Devs won't be able to do anything until one of us find a way to replicate the issue, for now it still appears to be 'random'
[Moto G Original Android Development] tzzeri:
If you leave a logcat running until it happens....
[Moto G Original Android Development] matmutant:
i won't. :fingers-crossed:

Ricardo came with the fix you were waiting for :

http://review.cyanogenmod.org/#/c/100778/

-keep in mind that if anybody removes your SIM (s)he will still be able to access the whole device content-
[Moto G Original Android Development] UltraMaks:
I can only think that it happens if you mix pressing power button and "pocket" wake up. Btw try to call "Power Menu" using Power button after several times of waking the display by "pocket" mode and putting it into sleep mode by double tap in the status bar.

You will see that it behave in a strange way. Sometimes this menu appears only on 5-6 times switching on and off the display by the Power button
[Moto G Original Android Development] Shub77:
The same happened to me. And on conjunction with the 80 ms timeout :) for reading messages, I switched Ambient Display off and now I use the "power button" approach :)

Another bug: when I boot the phone, there is a mess with "screen unlock" and "entering PIN" sequences: ok, I can do things before I entered the pin, and to me this is weird anyway. When the phone detects there is a sim inserted, asks for the pin: I can't go on without entering the pin (and is is ok). So far, so good (kinda). The odd behaviour starts here, when I entered the right PIN and try to draw the unblocking sequence for the first time: I have to wait 20 seconds as if I inserted it wrong several times.

-- EDIT sorry, I read now of http://review.cyanogenmod.org/#/c/100778/
[Moto G Original Android Development] JoaoMarcos:
Guys look to this: http://review.cyanogenmod.org/#/c/100760/

If it will merged, it can help with our problem with lmk?
[Moto G Original Android Development] LuizHenrique91:
Probably. I manually changed my LMK values to these and the multitasking was improved a lot. It's hard to get a launcher redraw after this.
[Moto G Original Android Development] objr:
Why can't it be merged?

Inviato dal mio Moto G utilizzando Tapatalk
[Moto G Original Android Development] michael_ch:
Hey, it was only pushed a few hours ago (by me btw.)

Actually it's a set of 3 patches that needs to be merged:

http://review.cyanogenmod.org/#/c/100758

http://review.cyanogenmod.org/#/c/100759

http://review.cyanogenmod.org/#/c/100760

For further details on the changes, see https://jira.cyanogenmod.org/browse/NIGHTLIES-1361

If you want to help, please test these patches and submit your review... :)

---------- Post added at 10:14 PM ---------- Previous post was at 09:40 PM ----------

All changes have just been merged. You can uninstall Kernel Auditor now ;)

Looking forward to tomorrows nightly build...
[Moto G Original Android Development] objr:
I'm so happy! The less app I own, the less worried I am.

Great Job myFriend!

Inviato dal mio Moto G utilizzando Tapatalk
[Moto G Original Android Development] LuizHenrique91:
I think since the first CM ROM for Falcon, the current is the best, considering features, stability and performance. I'm not an expert, but I guess we will have a stable soon.

Enviado de meu Moto G usando Tapatalk
[Moto G Original Android Development] KHM90:
Security options in settings force closing on 9th june build, can anybody help?

I can't side load apks because of this.
[Moto G Original Android Development] objr:
Mine is working just fine!

Inviato dal mio Moto G utilizzando Tapatalk
[Moto G Original Android Development] matmutant:
And the nightly is now out ! :laugh:

http://www.cmxlog.com/12.1/falcon/#cm-12.1-20150611-NIGHTLY-falcon.zip

Are using any theme or stock one? usually themes break a few things when they aren't totally up-to-date (like Deep Darkness that makes Gallery force close a few times before starting correctly)
[Moto G Original Android Development] KHM90:
Using stock theme, no other theme installed, I'll try updating to today's nightly because some users reporting they have no issues. Thx for help :)
[Moto G Original Android Development] N3tro:
Multitasking still sucks. Even with 1106.

Отправлено с моего Moto G через Tapatalk