yashsingh1/xdaforums huggingface dataset:
[Moto G Original Android Development] rzac:
i disabled the search bar since ever and the ram bug is still there. seems like the used ram is not made available again after usage .. so its literally 'lost'
[Moto G Original Android Development] SeannyM:
I dont have the ram bug either :D

Sent from my Moto G
[Moto G Original Android Development] will8578:
Me either, i hav animation turned off, always hav done on android

---------- Post added at 07:32 PM ---------- Previous post was at 07:28 PM ----------

I stand corrected, i do have it, phone laggy, just checked and got 60mb left, wow 1st time iv had it, bastard finally got me!
[Moto G Original Android Development] ig0r260892:
[MENTION=4888452]SeannyM[/MENTION]

see? check your memory too :D
[Moto G Original Android Development] NZ_Kobra:
Yep. I didn't have any RAM issues until last night when my phone stopped receiving text messages and chrome was crashing while loading pages. When i checked my RAM usage, i had 40Mb free. It seems that it finally got to me.
[Moto G Original Android Development] SeannyM:
With an uptime of 14:56:19 I still have 334MB RAM free. My phone has never started to lag on me.
[Moto G Original Android Development] ig0r260892:
so you think its normal to have 334 mb on idle phone? or do you have some hardcore game in background?

you have it too.. just dont reboot your phone for the next day and you'll see it
[Moto G Original Android Development] SeannyM:
Well, I see people complaining about having 100MB after a day and extreme lagging. I don't have that. My phone never lags and the lowest its dropped to is ~310MB. It does decrease from when it first boots up, but it doesn't affect my performance in any way so I'm fine with it.
[Moto G Original Android Development] ig0r260892:
bro, 14:56:19 is not "one day"... we all are talking here in >=24 hours.. so just keep it on for more like 10 hours and you will have it on 150 mb and less
[Moto G Original Android Development] SeannyM:
I have had it running for more than one day before, I just can't get the stats now because 15 hours is my current uptime. I usually reboot within a day anyways to install a new nightly or if my phone dies.

Sent from my Moto G
[Moto G Original Android Development] theepicflyer:
I don't have RAM bug either. I have been using my phone for more than 24 hours. Have 150mb left. Some heavy usage.
[Moto G Original Android Development] SeannyM:
150MB is pretty low, last time I ran for over 24 hours I recall having ~325MB free.
[Moto G Original Android Development] ig0r260892:
lol, you just told that you actually DO HAVE ram bug :D:D:D

150mb free.. look at your running apps, and cached.. sum all the memory they are using and tell me if it is near 700mb :D

and another thing.. try to unload them from memory.. force stop them and you will notice that you arent getting any free ram back
[Moto G Original Android Development] theepicflyer:
Oh yeah! I realize I do have the RAM bug. Tried clearing. Went down to 600 MB then shot back up to 700+. Sorry guys [emoji51]
[Moto G Original Android Development] dhacker29:
I haven't seen any fixes posted to review for this, and I have yet to experience any ram bug. If a fix is submited to review I will test it and include.
[Moto G Original Android Development] xheon:
Is there a way to fix the low incall volume?
[Moto G Original Android Development] dhacker29:
Test next nightly

https://github.com/CyanogenMod/android_device_motorola_msm8226-common/commit/417f5d79b764696512d2470f42360bbe7b598967
[Moto G Original Android Development] dhacker29:
After reading all of these "serious issues" with the ROM I am solving the problem by pulling Moto G from offical CM permanently.

Bye
[Moto G Original Android Development] wstruction:
Yeah he probably has the ram bug. And I always completly turn off animations because they sow down the device. Slowing them down or turning them off makes your device feel snapier
[Moto G Original Android Development] xheon:
Lol, that's an fast and easy way to solve problems, back to stock rom I guess...
[Moto G Original Android Development] SeannyM:
It's a joke, it's supposed to show how dumb it is that everyone complains about all the bugs and never just appreciates that we actually have official builds. Lots of devices don't have official CM and sometimes don't even have unofficial builds that are fully working hardware-wise. The bug will get fixed eventually and since everybody knows about it now what with the ~50 pages all about how the RAM bug is terrible and whatnot, it's fine to stop reporting the well-known bug to everyone again and again.

Just my two cents. Carry on now ;)

Sent from my Moto G
[Moto G Original Android Development] winsonlam:
yeah you're right.

I've suffered lack of ROM in my last device and i'm glad to have official supported ROM now(even though i have xt1033 which dhacker is working on it),i wont hurry and wait in clam and peace

any bugs that reported will be seen and no need to repeat and repeat it in the thread:p
[Moto G Original Android Development] theepicflyer:
[MENTION=1555922]dhacker[/MENTION]

I really hope you are kidding. We're not complaining. Just trying to find possible fixes for these problems. Good job!
[Moto G Original Android Development] MasterAwesome:
Dual sim

Suppose i were to install this rom on a dual sim varient will it atleast start? and if it will, will one sim work?
[Moto G Original Android Development] theepicflyer:
There is a test build for the dual SIM version. Search around.
[Moto G Original Android Development] P.Kosunen:
Total RAM: 903276 kB
Free RAM: 451868 kB (48212 cached pss + 363456 cached + 40200 free)
Used RAM: 367823 kB (317303 used pss + 4300 buffers + 1152 shmem + 45068 slab)
Lost RAM: 83585 kB
ZRAM: 2428 kB physical used for 6184 kB in swap (131068 kB total swap)
KSM: 43108 kB saved from shared 6112 kB
196220 kB unshared; 332316 kB volatile
Tuning: 64 (large 256), oom 122880 kB, restore limit 40960 kB (high-end-gfx)

There is some leak after all, Lost RAM increases 30 to 40MB/day on my usage. So it would take over ten days before i would see any negative effects.
[Moto G Original Android Development] cra1g321:
Ok people, we can all keep going on about the RAM bug every single day, or you can stop posting about it,

and just wait for someone who is developing the ROM to mention that it has been fixed.

You got to remember, "official" does not mean stable, this ROM is still being released as "Nightly" which are unstable builds.

If you have an issue which has not already been posted about, then post it,

else shut up, deal with the fact that there is bugs else move back to stock ROM.

I don't have anything to do with this ROM, besides just being a user of it a few builds ago, but even i'm getting annoyed at the comments about people saying dhacker29 should do this and do that, and fix this and that
[Moto G Original Android Development] Indigoreli:
How to change the tiles per row? Xposed Framwork (Gravity Box) don´t work
[Moto G Original Android Development] Carlos_EVH:
Dhacker29 we are trying to help you reporting issues like the RAM bug, igor260892 posted this link a few posts ago but I don't know if you see it, http://forum.cyanogenmod.com/topic/89863-cm11-on-moto-g-ram-full-after-24-hours/

It has more info about the bug in our moto g's
[Moto G Original Android Development] rzac:
had a strange issue this morning on latest nightly: booted up my phone, it was totally laggy and all my account settings were gone. finally, i restored one of my nandroid backups. might be that i misconfigurated something, but i just wanted to mention it in case more people are affected.
[Moto G Original Android Development] syrkles:
There was no nightly for last night guys he might have official dropped it
[Moto G Original Android Development] Wechy77:
No, only media-caf-new has new commit and it breaks build. Check cm jenkinks
[Moto G Original Android Development] dr.pythagora:
it's always the same problem - stucked at booting.

i reboot the phone when it's at (endless) booting - i flash the nightly rom but still the phone stucks at the booting phase.
[Moto G Original Android Development] vocoderism:
And thanks to dhacker now anyone can choose across different roms Cm, Pa, slimkat, infinity ecc.... Great guys

Inviato dal mio MOTOROLA MOTOG utilizzando Tapatalk
[Moto G Original Android Development] dhacker29:
I am not dropping it. I was being sarcastic. I try to fix things as I figure them out. I know call audio is an issue it is on several new ports, and I have been exploring it. I am trying to took at the ram issue and see what I can find.
[Moto G Original Android Development] dhacker29:
I don't develop a rom for the public. I develop a rom for me and make it available. End of story.
[Moto G Original Android Development] Tijmen:
Thread cleaned.

35 posts, people. I had to dig up 5 pages of crap because of 3 or 4 people who don't understand what XDA is for. This forum is not a helpdesk or make my phone cool, smooth, whatever forum. This is a development forum.

Don't complain about the behavior of the developer, if you don't agree with it; tough luck. It's his thread, and he can do whatever he wants in and with it. Read in awe or contribute to the development, don't go around reporting bugs that have been reported a thousand times before unless you have new information about the bug, backed with serious stuff like logs. Don't go around complaining about the lack of solutions or development

and most importantly: Don't react to the trolls who do

.

If you don't agree with something, suck it up. If you think something's against the rules, report it. If you think you can improve the ROM, back it up with evidence and post about it. Any other action is unnecessary and hampers the development.
[Moto G Original Android Development] dgauze:
dhacker29, thought you might be interested to know that I had problems installing this ROM on the GPE, following the intructions on the CM wiki. This happened with the latest versions of both recoveries.

More specifically, I had to format /data and /data/media first, and this resulted in the internal storage filessytem being formatted to f2fs.

Flashing without foramtting (following the wiki) gave me the "Encryption Unsuccessful" message after each boot.
[Moto G Original Android Development] herna:
The best way is to flash without formatting, and after flash format the data/media, and ROM will work, but you will have nothing on your internal storage. This is the only way right now.
[Moto G Original Android Development] dgauze:
How can this make any difference? Nothing is flashed to the /data partition anyway.
[Moto G Original Android Development] herna:
Maybe data/media is formatted on different formats or some mismatches, but errors are related to /data/media. I did not investigate deeper into it, but I could see the only time I flashed GPE on my Moto G.
[Moto G Original Android Development] xheon:
Anyone tested 03/17 build?, it has a lot of changes.
[Moto G Original Android Development] NZ_Kobra:
I have installed it via OTA CM update.

The first thing I have noticed is that magnetic wake/sleep (flip shell) functionality now works perfectly.

I haven't noticed any [new] issues so far. I will continue to monitor the free RAM although I'm unsure if dhacker has commited any potential fix.

Thanks for all your hard work dhacker!
[Moto G Original Android Development] diego88it:
I have a question: i put the cm11 on my moto g gpe...when i download the new nightlies i have everytime to format data in twrp recovery?
[Moto G Original Android Development] Geordie Boyo:
Not necessarily just do a dirty wipe, so as I do i just boot into recovery and then flash the nightly build you wish to install, then re-flash the kernel if your using a third party version like pink. i've had no issues doing it this way.

However, i have found from my experience that CWM swipe works better than TWRP with this method of upgrading.

Link to the latest version recommended by [MENTION=4112553]dhacker29[/MENTION] is on my signature below, or first post of this thread.
[Moto G Original Android Development] diego88it:
On the gpe version TWRP works much better, for example with cwm swipe i had problems, like it doesn't recognize the internal storage.
[Moto G Original Android Development] alokhan:
But do you think it is a issue in the telephony app of CM or a kernel issues on specific devices ?
[Moto G Original Android Development] dannyfritz:
This sort of question should be directed at a debugging tool for finding leaks. I've heard of many speculative possibilities. Doesn't really matter until it has been determined with a tool.
[Moto G Original Android Development] rzac:
just a minor thing: since a few nightlies, some german labels of the privacy guard permissions (location, read battery status, ..) are mixed up and don't correspond to the icons shown. i'm still new here but willing to contribute. are there certain language files where this can be changed?
[Moto G Original Android Development] Entropy512:
And if anyone is wondering why I have yet to release an alpha test build of Omni on the G - well, just look at this thread.

I just don't have the time to deal with all of that. I'm working on getting things to at least a level where just "repo sync", pulling in vendor blobs, and brunching is all a person needs, but I'm deathly afraid of releasing a build here now.

As to the RAM bug, I haven't observed it on my own device, but I also don't really use it for anything other than a Chromecast remote most of the time. If users want to solve it, rather than just complaining, provide information:

1) Are there any usage patterns that seem to make things worse? (For example, Exynos4 devices, especially 4210 devices, were prone to a graphics memory leak that was especially bad if you pulled down the notification bar repeatedly.)

2) Is there a point in time where this seemed to start? I've seen some users claim it was around February 24, which indicates that it might be related to display-caf-new being "frankendisplayed" with AOSP patches.

3) Are there any processes that seem to be using excessive memory? Does the memory free up if you do "adb pkill surfaceflinger"? (The latter hints at graphics memory leaking, although killing surfaceflinger can often cause many other processes to restart so it may still not be graphics.)

Just complaining about a bug does nothing, especially if the maintainer can't reproduce it. Data that can be analyzed does.
[Moto G Original Android Development] :
Didn't someone have a solution for the RAM bug in another thread?
[Moto G Original Android Development] michalurban:
Im having trouble with signal on 0317 nightly. I have low or none signal or only E in areas that I never expected signal troubles and always had H or at least 3g.
[Moto G Original Android Development] ph4zrd:
Glad to see you here. Just want to share my experience on that one.

1) I think for me the RAM bug happens more frequently if I use mobile internet instead of WiFi but can't say that definitely.

3) As far as I remember, ps didn't show something special when I last checked after experiencing low mem, did also try to kill some system processes via adb, phone soft rebooted, available RAM was still low. Nothing special in /proc/meminfo as well. If it helps, I can collect some file contents or the output of some cmds (fresh boot vs ram bug) tomorrow.

To check if it's something kernel related... I saw that kmemleak is compiled into the cm moto g kernel, maybe someone can explain how to use that on Android over adb?!
[Moto G Original Android Development] dgauze:
Can someone clear up my confusion on the recoveries regarding the GPE?

For CWM Swipe, GPE users need to use a separate version, but the latest TWRP supports both non-GPE and GPE? If so, any reason the GPE version of CWM Swipe is not listed on the CM wiki?
[Moto G Original Android Development] -ION-:
Not possible unless you make your own xposed module or build your own rom, also don't use GravityBox on CM as the author explicitly told in his thread:
[Moto G Original Android Development] vitokes:
So is MMS working on xt1031 by chance yet? I was looking through the comments but nothing.
[Moto G Original Android Development] dr.pythagora:
I suspect that the installation of cm11 stucks at booting because the bootloader is not unlocked properly.

Unlocking it another time does not work, as it says the bootloader is unlocked. But I did get a message when i unlocked it, saying about an error(failure) - I dont remember the exact message.

question: is there any way how to lock the bootloader so I can try unlocking it again properly?

thanks.
[Moto G Original Android Development] Doublepranks:
We are not far from an emblematic moderators post that kindly asks for a much cleaner development thread and I can already see people turning it all back into some sort of messy complaining Q/A costumer service care thread.

Come on boys and girls...

Let's listen to Mr entropy and over flow this thread with logs and and much more in topic information.

BTW its the forth day using my own build for the xt1033 and not even a sight of ram bug so far.
[Moto G Original Android Development] syl0n:
DoublePranks - I use your build and do suffer from the RAM bug. After a day of use, phone gets slow randomly and some apps just die, music stops playing, I can't run games that use large memory (they quit back to home screen). Only a reboot fixes it.
[Moto G Original Android Development] dhacker29:
The latest cwm works with both retail and gpe. If you have gpe it will format and read ext4. It detects from service file system
[Moto G Original Android Development] dgauze:
IME, it does not. I have to format /data and /data/media to avoid the "encryption unsuccessful" message after flashing, and even then it formats to f2fs.
[Moto G Original Android Development] Entropy512:
The old Exynos memleak was nasty like this - didn't show in top, but if you killed surfaceflinger the memory would free up, and it went away when we moved to newer Mali blobs. (Samsung never revealed the secret of making r2p4 mali not leak with Jellybean...)

I may release an Omni build just to see if it has the RAM bug or not... If it doesn't that really points towards it being related to frankendisplay.
[Moto G Original Android Development] dhacker29:
Using the included kernel or flagging a different one?
[Moto G Original Android Development] dhacker29:
I formatted my device ext4 and everything just worked
[Moto G Original Android Development] dgauze:
No, just going from stock GPe to CM. Specifically, CWM fails when wiping data/factory restore because it cant mount /data. I also remember a message about a hidden directory under /data, and I think I got that when formatting jsut /data without formatting /data/media.

FWIW, I did notice some differences in the partition layout between the XT1032's on another thread.

Just to be clear, there is a specific version of CWM on your site (from 2/20/2014) for the GPE, but that's not needed?
[Moto G Original Android Development] dr.pythagora:
CM11 on Koodo/Telus Moto G (XT1032)

I have tried to install CM11 on this model. The installation stuck at booting logo.

I have tried once starting with the factory/original stock rom. Later, I re-installed the stock rom.

The only error I found in all the steps (unlock bootloader, root, cwm,...) is when I unlock the bootloader.

Though the bootloader is unlocked I do have this message

sudo fastboot oem unlock ....

...

(bootloader) Unlock code = ....

(bootloader) Unlock completed! Wait to reboot

FAILED (status read failed (No such device))

finished. total time: 21.914s

I suspect this is responsible for stucking at the boot step.

Has anyone succeeded installing cm11 on koodo/telus moto G?

Thanks.
[Moto G Original Android Development] dseries60:
I have CM Build 02/23/2014 running on the G (GPE) with no problems, including no memory bug. Below are some details. Perhaps build info will help as to when the bug surfaced. Using TWRP as well.. I run Omni on everything else.
[Moto G Original Android Development] dseries60:
Here is the build info to match the post above
[Moto G Original Android Development] dhacker29:
That was before I unified them so either "should" work
[Moto G Original Android Development] myabc:
hello. please, solved problem of echo in phone? what version did solve this problem? thanks
[Moto G Original Android Development] matmutant:
[DEV/DEBUG/COMPLAINS] CM11 debug thread for Falcon

To keep this [Rom] thread clean, there is now a place for

bugtracking

: http://xdaforums.com/showthread.php?t=2685338

i know people will still want a place to complain and request things ? ok, i assume this new place will stand for that -even it's not the main goal-. So please keep CM11 thread clean and post here instead.

Thanks.
[Moto G Original Android Development] alokhan:
Well the repo sync things already sounds very good :)
[Moto G Original Android Development] michalurban:
Im curious why the RAM BUG isnt mentioned in the CM wiki here

http://wiki.cyanogenmod.org/w/Known_Issues_page_for_falcon

Is there any particual reason?
[Moto G Original Android Development] theepicflyer:
It says there on the page that the guy just be reproducible after a clean install. And not everyone gets this bug. Plus there's no concrete evidence it's a bug.
[Moto G Original Android Development] michalurban:
OK, I understand the not-reproducible part ... but I dont understand how this couldnt be a bug if its clearly affecting so many people (including myself) ...
[Moto G Original Android Development] obvious:
Unexpected reboot on 20140317.

last_kmsg attached
[Moto G Original Android Development] theepicflyer:
I don't really understand that part either. All i know is that the bug report thread mentions it having no logs as well as nothing in meminfo that could help. However they do know that it came in around Feb 24. That could help them solve it.
[Moto G Original Android Development] matmutant:
move on my thread for these kind of discussion.

(and show me with screen shots, logs or whatever you want that this "Lost RAM" is increasing and never decreasing ; that this "Lost RAM" is really linked to slow down ...)

i'm not saying i don't believe you all, just that until we get REAL and workable data we can't do anything...
[Moto G Original Android Development] theepicflyer:
Sorry. Yes I understand. I will try to do something.
[Moto G Original Android Development] wstruction:
A few small issues that no one else has reported so I might as well do it: When I set my volume panel to expandable it goes back to single after about 5 minutes, the only temporary fix is to change to single then back to expandable, but then it just goes back to single again. Also the animation when you go into standby doesn't work. Any fixes? And is it because of an app I'm running? Also I am running milestone 4 and I have the us version (xt1034)
[Moto G Original Android Development] matmutant:
What wasn't big enough in this post ?

http://xdaforums.com/showpost.php?p=51174728&postcount=2370
[Moto G Original Android Development] obvious:
Congrats on your mod status
[Moto G Original Android Development] michalurban:
Only for someone who reads every single post after returning home. Thanks for creating this post, though! ;)
[Moto G Original Android Development] $lim $hady:
Dual Sim

Does both sims work on this rom??? XT1033:confused:
[Moto G Original Android Development] theepicflyer:
Please search before posting. There is another thread for an experimental build for the dual sim version by double pranks
[Moto G Original Android Development] jamstar.5:
Threat???? :eek::eek::eek::eek::eek::eek:
[Moto G Original Android Development] anerik:
Yeah... i tried also init.d scripts to change gov and freqs but nothing... they reset
[Moto G Original Android Development] SeannyM:
I have been using this for about a day now, and the only bugs I found (besides CPU freq) are:

-Settings->About phone->Status->My phone number "Unknown" (no big deal, I know my number anyways)

-DSP Manager doesn't work, FCs when new song plays (again no big deal, I have expensive headphones so I never use DSP Manager anyways)

Besides that, everything is perfect! I don't know if it's me or not, but I feel that it is slightly smoother than the stock KitKat which was already super smooth.