yashsingh1/xdaforums huggingface dataset:
[RAZR HD Android Development] CWGSM3VO:
I agree with the governor statement, I too doubt it makes any difference simply because before all this talk happened, I was using ondemand and never had any issues. I'm simply bringing things into alignment (in my view).

One of the memory leak patches I merged into my source is the mythical memory leak patch in ColorFade.java -- now a lot of the technical data I ran into stated this basically happens when screen-off (the fade portion) and since memory isn't dispatched in a sane manner, the leak occurs. Although in truth, I've yet to see any kind of leak. The other patch is a kernel patch which exists already in the CM tree for other devices based on the same family/chipset (it's agnostic in this case).

Some users seem to be able to repro the issue easier than others and frankly, since I know Z messes with configs (specifically, OOM/governor/etc) it's hard to say definitively what his issue might be. I've never been able to reproduce it myself :( But I do know others can and waiting to hear back from them with the builds I've recently posted (for what it may be worth).

But if this is a library/hardware issue that's been exposed, yes, it's going to be tough to figure out and way beyond my skillset.
[RAZR HD Android Development] Zeljko1234:
Damn it! I told you several times already that I was clean flashing/testing stock CM12 (and all other available roms) without changing anything (especially not OOM/governor). Before you blame me, I did not block play service. I even wiped damn internal storage (and lost everything on it), changed back to ext4, flashed dhacker's gapps with all bloadware... With all roms I've tested I could easily reproduce calc bug.

Today I accidentally discovered that changing governor (first performance then interactive) fixes calc bug. Now, I cannot reproduce calc bug anymore. Maybe is just coincidence, maybe after reboot bug will appear again, maybe system just quicker recovers from freeze... But please don't say that is my fault! Why every time when I find something, I must spend more time to convince people than to find solution?!
[RAZR HD Android Development] CWGSM3VO:
I'm not blaming you dude, sheesh. Perhaps I forgot a key point when commenting, if so, I apologize.
[RAZR HD Android Development] ermito:
Ok. I've been using Balanced all day and didn't have the calc bug, yet. But this build seems to have a problem when landscape mode is triggered, I got a pop up message saying the interf sist has stopped. I can't use landscape mode in any app, basically. I will keep with this build anyway, at least it has calculator fully working. lol.
[RAZR HD Android Development] CWGSM3VO:
Not saying it doesn't happen but I just tried a bunch of apps (Play Store, MXPlayer, etc) in landscape, worked out fine for me.
[RAZR HD Android Development] ermito:
Sorry, my bad. A custom font in themes was causing it. Now it's fine.
[RAZR HD Android Development] KC69:
Having no issues with your build today C. A little slow to redraw home page, but a lot faster than cm has been. And that's running it as it flashed. No changes. Good yob Mon.
[RAZR HD Android Development] ncsuwolfs:
recently switched to CWGSM3VO 's build because of lag ive been experiencing on other custom roms. everything is super fast, just wondering is there a hosts file blocker built in and im not finding it?
[RAZR HD Android Development] CWGSM3VO:
It's completely stock except for two patches; one to the UI and one to the kernel. Nothing else has been changed or altered in any way. This is in reference to the last two builds I posted today (xt925/xt926). It is current up to "xt925: Set proper partition sizes" at Mar 7, 2015 6:16 PM (at whatever timezone gerrit observes). I also compile with Oracle Java rather than OpenJDK as well, for whatever difference that makes.
[RAZR HD Android Development] ncsuwolfs:
so short answer no? lol ive searched everywhere but havent found it anywhere . i actually havent ran a official cm 12 because the latest puts me in a boot loop. ive tried unbeloved hosts but it doesnt seem to work. just wondering if i missed it somewhere :D
[RAZR HD Android Development] gappledroid:
Yeah! The Adreno failure has been reported by madmonkey57 with the calc logcat he posted here and I saw something similiar going on too in the browser logcat I grabbed. Maybe the issue with Play Store reported by Z and I is all the same.
[RAZR HD Android Development] madmonkey57:
Indeed, this looks very much like what I saw in my logcat with the calc bug

---------- Post added at 10:10 AM ---------- Previous post was at 10:10 AM ----------

OK, been playing with C's build for a few hours now:

- It's way smoother than on the lastest official builds I tried. I used to have lags all over the system notably when going back to the launcher

- Recent apps remain in memory for a while. Not too long apparently, but still better than nothing

- So far, can't reproduce the calc bug...
[RAZR HD Android Development] CWGSM3VO:
Was playing around last night and noticed something...

I found last night that once I enabled Automatic mode (was on "day") for LiveDisplay, I could no longer turn my display back on and had to reboot the device. It comes up with the display but the minute the screen blanks, it never comes back. I didn't wait long enough to see if perhaps a recovery would happen but thought I'd throw it out there.

I have a QS tile for it, and can switch between Auto, Day and Night without issue. It was after rebooting with it on auto and the screen blanked, it happened.

There doesn't appear to be a way to turn it off either, just the three settings. I have it back on Day now and it's working fine.

*edit* might be related to this... http://review.cyanogenmod.org/#/c/90856/
[RAZR HD Android Development] kkruglov:
sorry for asking, CWGSM3VO you are not doing unified builds anymore? only xt925/6?

i'm on xt907 ;/
[RAZR HD Android Development] CWGSM3VO:
There is no such thing as unified builds anymore. The entire moto_msm8960 family was broken apart into individual devices again (ie; before all the moto devices were unified).

The VM that I build in has limited space allocated to it so I can only build one device at a time. Even with CCACHE it takes a long time to build for one device after which I have to do a full source clean (otherwise I run out of space). I really don't have time to rebuild my VM to accomodate larger builds. I only have xt925 and xt926 device trees in my source so I'm only building for them. I don't have a JBBL device so I can't test builds for devices that still are JBBL (while I'm sure will build fine but I can't do much to "support" it).

I suppose if enough people ask for it, I can try to build for xt907 but I won't make any promises.
[RAZR HD Android Development] CWGSM3VO:
Thanks for reporting back on this. As it stands, this issue is hard to reproduce to begin with but I verily appreciate the effort spent in trying for me.

All I want for Christmas is for Z to try the build as he can reproduce the issue quite easily ;)

---------- Post added at 09:59 AM ---------- Previous post was at 09:33 AM ----------

I'm not sure what you mean by "unbeloved hosts". I'm guessing you mean something like AdAway or AdBlocker or something to that effect? If so, then no, there isn't any that I'm aware of. Shorter answer ;)
[RAZR HD Android Development] gappledroid:
That patch is supposed to be merged in android kernel motorola msm8960-common device tree when was unified, isnt it?

http://review.cyanogenmod.org/#/c/84654/
[RAZR HD Android Development] CWGSM3VO:
I believe that is JBBL, it's definitely not msm8960dt that KKBL builds use.
[RAZR HD Android Development] gappledroid:
for JBBL not because there were not CM 12_JBBL at the date of merge.

msm8960dt for xt92x and msm8960 for xt907... dont know. Lets wait [MENTION=2218140]kabaldan[/MENTION] to talk about that patch.

BTW, Android 5.1 is here :victory:
[RAZR HD Android Development] CWGSM3VO:
Ah I see. Then it was missed for this branch of moto. Lots of other devices merged this patch in as well.

EDIT: 5.1 has a lot of changes. See the changelog here: https://paste.teknik.io/1010
[RAZR HD Android Development] gappledroid:
Yes! Maybe was missed for this branch. The patch has the status merged but I can't remember to see it in CM changelog.

Edit: 5.1 has a huge list
[RAZR HD Android Development] CWGSM3VO:
Interesting:

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

My builds include this commit but only partially:

http://review.cyanogenmod.org/#/c/91004/1
[RAZR HD Android Development] madmonkey57:
With all those patches C (and others) have pointed out in recent posts, it's kinda hard to follow up:

1/ what is already merged in the xt92x branches

2/ what is in another branch and can be ported to the xt92x branches

3/ what is exclusive to C's build for now
[RAZR HD Android Development] CWGSM3VO:
The 5.1 memory leak fix was unique (I guess) to my build as is the kernel leak patch. Now the 5.1 memory leak patch is merged into CM12 as a complete patch (mine was partial). The kernel leak patch appears to be merged into the xt907 tree but not the xt92x tree so it's still unique to my build.
[RAZR HD Android Development] madmonkey57:
Thanks.

Guess it's gonna take a few days before the first cm build based on 5.1 gets ready. And we're gonna have to keep ean eye on the kernel leak patch also.
[RAZR HD Android Development] CWGSM3VO:
Android 5.1 will end up as CM12.1 based on the comments I've read so far but I'm guessing.
[RAZR HD Android Development] gappledroid:
Guess what? I have a xt907 and all the issues previously reported here.
[RAZR HD Android Development] CWGSM3VO:
So you would have had the kernel patch but not the memory leak fix.

---------- Post added at 02:16 PM ---------- Previous post was at 01:53 PM ----------

So I'm now rebuilding for XT925 and then I'll flash it and test it. Still including the kernel patch. At time of compiling, my source was complete with what's seen on cmxlog. If all goes well, I'll build XT926 and post both up. Hopefully the nightlies will return to normal soon.
[RAZR HD Android Development] Zeljko1234:
1d 14h of uptime, no single calc bug (or any other similar, like with business calendar 2, play, etc) since I change governor to interactive. Another benefit that phone is more snappy but still has problem with memory management (killing background apps). Didn't touch OOM or anything else, just CPU governor.

I can try latest C's build or should I wait for the latest?
[RAZR HD Android Development] CWGSM3VO:
I'd wait for the upcoming one.
[RAZR HD Android Development] Zeljko1234:
Ok, phone is charging right now anyway. Started calculator thousands of time, used browser, here maps, poweramp, cleared recent... repeated everything again and again.

---------- Post added at 12:55 PM ---------- Previous post was at 12:52 PM ----------

Forgot to say, there's another friend (one who started thread how to unlock bootloader after kk update) who has calc bug too. After he changed governor, no calc bug anymore.
[RAZR HD Android Development] CWGSM3VO:
Testing xt925 build - so far so good. Currently building xt926.
[RAZR HD Android Development] kabaldan:
jbbl devices use motorola/msm8960-common kernel (3.0)

kkbl devices use motorola/msm8960dt-common kernel (3.4)

msm8960dt-common kernel was originally ghost (Moto X) and obake shared kernel and when kitkat was released for xt926, David merged the support for kkbl 2012 devices to it, as the 3.4 moto kernels for Moto X and xt926 were very similar and shared common history for the most part.

(After David went missing, ghost was later separated to use motorola/ghost kernel)

To be correct, motorola/msm8960-common kernel repo should be renamed to motorola/msm8960_jbbl-common and motorola/msm8960dt-common kernel should be renamed to motorola/msm8960-common. But that would break the older cm10.1/cm10.2/cm11 builds, unless someone would spend some time on fixing the old branches. And no one had the time for it so far.

The mentioned kernel patch is not a memory leak patch but a security patch and I indeed missed it and forgot to merge it to msm8960dt-common kernel. Thanks for bringing it to my attention.

As for the unification/de-unification and repos used:

Most of the stuff has been shared between device builds even before the great unification into a single build and is still shared after the split.

xt926, xt925 and xt907 (kkbl) repos inherit from motorola/msm8960-common repo.

xt925_jbbl, xt897 and mb886 (jbbl) repos inherit from motorola/msm8960_jbbl-common repo.

Both motorola/msm8960-common and motorola/msm8960_jbbl-common repos further inherit the shared stuff from motorola/qcom-common repo.
[RAZR HD Android Development] kabaldan:
As far as I'm aware, the interactive governor is the default cpufreq governor used by CM builds for all moto msm8960 2012 devices since the beginning (cm10.1).

So the rationale of the story is that forcing a different cpufreq governor makes the GPU/Adreno bug more prominent?
[RAZR HD Android Development] CWGSM3VO:
I tracked this down originally to the kernel, it defaults to ondemand and at some point while I was browsing commits daily, David changed some init scripts to reflect ondemand in conjunction with performance-boot and then later, PowerHAL focused on these based on various device commits I reviewed at the time. This was quite some time ago but can be found in this thread. I simply went through init to reflect this throughout.

edit: I checked msm8960dt_mmi_defconfig and this no longer appears to be true meaning PowerHAL is setting ondemand via profile I'm guessing.
[RAZR HD Android Development] KC69:
03/10 is finally out. DL ing it now. C does it have your fixes? Your ⁿ3/09 is running pretty good for me.
[RAZR HD Android Development] KC69:
Some observations on 03/10. SNAPS back to home page, no delay, last ROMs have all had 3-5 seconds to redraw home screen. Gonna try some more things, that one just grabbed me right off and had to holler a attaboy to cm team.
[RAZR HD Android Development] CWGSM3VO:
3/10 is newer than I was going to post, so I'll skip all that.

[MENTION=4187680]KC69[/MENTION] the only thing missing is the aforementioned kernel patch.
[RAZR HD Android Development] KC69:
I'm gonna revise my attaboy to an almost always attaboy. Man , its kind of hit or miss . two,three times fast then uhhhmmm OK waitin on it. Overall seems better. Haven't played with it all the way through my usual repertoire, but what I have seems good.

---------- Post added at 11:24 PM ---------- Previous post was at 11:20 PM ----------

C. Can you put the kernel patch and your other fixes over 3/10 ? Seems like that would be awesome , sumpin that would work as a daily till 5.1 rolls out. What say ye partner. ??
[RAZR HD Android Development] technoid1964:
I'm running C build from last night, wanted to play with the governor, but when I go into the performance setting, no CPU governor settings. Z, where are the governor settings? I've searched hi n lo, can't find it.

I think I lost a bolt or two searching...
[RAZR HD Android Development] Zeljko1234:
According 3pp tool (3c toolbox in my case, friend uses another app) balanced in battery setting is ondemand. First I just changed to performance under battery settings and tested, no calc bug but CPU could be on the max freq or sleep. Would be strange if I change governor back to balanced/ondemand and still be without calc bug. I'll try now.

We could say that bug is less prominent with performance driven governors or CPU/GPU really stuck at the lowest freq in some cases causing slow app start, slow system response and even crash.

---------- Post added at 10:28 PM ---------- Previous post was at 10:25 PM ----------

Stock shoukd be under settings, battery, battery mode but with only three options: battery save, balanced (ondemand) and performance.
[RAZR HD Android Development] Zeljko1234:
Changed governor back to balanced in settings/battery (changed to battery safe then to balanced) and after few minutes of putting phone on harder load (navigation, music, browsing...) got calc bug. Actually like before, phone get laggy, not responsive, freezing, couldn't start play market... Let's go back to interactive using 3pp app.
[RAZR HD Android Development] madmonkey57:
Confirmed here. Uptime is now > 1d. I get very noticeable lags when going back to the launcher, just as described by [MENTION=4187680]KC69[/MENTION],hit or miss... [I'm on C's build).

I'm undecided whether to switch back to official dailies or stay with [MENTION=4418762]CWGSM3VO[/MENTION]'s build (i.e kernel leak patch). It seems that [MENTION=2218140]kabaldan[/MENTION] is going to apply the patch to our kernel anyway... Oh well, let's wait a few days...

EDIT: BTW, still no calc bug...
[RAZR HD Android Development] ermito:
I got calc bug in latest nightly (10/03) using balanced in battery settings. If I use performance it does not happen, at least for now. Also, the launcher redraws less.
[RAZR HD Android Development] Mikerhinos:
Been tired of LP problems (mainly the signal loss ones) and tried to go back to 4.4/4.6, but I have a message when trying to flash like "sorry that rom is made for xt926 etc... Your phone is xt925"...even when I try with a xt925 certified rom like http://xdaforums.com/showthread.php?t=2696606 or http://xdaforums.com/droid-razr-hd/development/rom-motomsm8960-omnirom-t3042282 :(

It's not possible to go back ?
[RAZR HD Android Development] CWGSM3VO:
He merged that patch last night, it should appear in the next nightly.

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

---------- Post added at 07:01 AM ---------- Previous post was at 06:47 AM ----------

It's possible to go back.

The obvious thing here is your recovery or the ROM. If it's a ROM looking for moto_msm8960 then it won't recognize your device if you're using a newer non-unified recovery (my first guess).
[RAZR HD Android Development] Mikerhinos:
I'm on TWRP 2.8.4.0

So I have to go back to an old recovery too ? :(
[RAZR HD Android Development] CWGSM3VO:
I'll let you experiment with that and find out. Both ROMs you mentioned are based on moto_msm8960 (ie:unified).
[RAZR HD Android Development] technoid1964:
Did you wipe before flashing? If you don't, it may not flash. I had that happen too, wiped, and 4.4.4 installed fine.
[RAZR HD Android Development] Mikerhinos:
Flashed CWM 6.0.4.9, tried again, same error message.

Wiped cache/factory reset, same error.

Pretty sure that it's the recovery, will have to find an old one that can flash an unified 4.4 KKBL rom.

Thanks for your advices guys, hope that I will manage to go back to when radio was working perfectly :rolleyes:
[RAZR HD Android Development] StefanGA:
I confirm, I had to go back to TWRP 2.8.3.0 to flash any old unified build!
[RAZR HD Android Development] Zeljko1234:
After >2 days of uptime, changing governor back to ondemand brought calc bug and make my system damn laggy and unstable. Changing back to interactive or even performance didn't help at all so I had to reboot. After reboot, calc bug was easy to reproduce and was gone after changing governor to interactive.

Dirty flashed C's build 03/09 (wiped dalvik and cache), couldn't reproduce calc bug whatever I tried but the system is not very responsive. Background apps are still getting killed even I see that default OOM settings in this build are less aggressive. Changing governor to interactive makes the system quicker. Looks like that is really something wrong with GPU, some apss are starting normally then quickly show black screen, then normal app GUI. Also looks like that default ondemand governor doesn't scale quickly enough to cover that GPU crash but interactive does. Not solution of course, just workaround but at least makes phone useful. Would be nice to have interactive as default for our CM12 builds. Not just because of bug, because of better user experience.

Did not change anything during initial testing. After, only change is governor.
[RAZR HD Android Development] Mikerhinos:
Tried Philz recovery same error.

Tried TWRP 2.8.3.0; epinter's nightly 20140801 CM11 gave same error, 20140104 Snapshot flashed, woohoo ! Then, installed Gapps 4.4.4, wiped, reboot...and it's a bootloop... :crying: (not even booting splashscreen, I'm bootlooping the "warning bootloader unlocked" stuff).

I'd try 4.1 because looks like 4.4 roms already had RIL problems, but as I'm on KKBL I don't think that it will flash :(

Guess that I'm condemned to reflash and use LP now lol...
[RAZR HD Android Development] CWGSM3VO:
I have a commit lined up to make this so. Just gotta get it into the system.

*edit* I built last night and changed the PowerHAL profiles to use interactive vs ondemand and frankly, the performance seems about the same to me. However, there's still that annoying I/O lag that happens (not sure if it's storage based or not that's triggering) and get that annoying lag every so often, heard audio skip a bit switching to different apps. I realize flash storage isn't that fast but I'm beginning to think there may be some starvation or lack of buffer-fill (for lack of better wording) going on here and I think I'm going to focus on trying to ferret that out.

*edit* I think I just figured it out.
[RAZR HD Android Development] Mikerhinos:
Ok so got back to TWRP 2.8.4.1, flashed the 1st LP rom that I saw in my SD card, booted, and got signal without doing anything like airplane mode on/off, "killall -HUP rild" in a terminal etc...

And now it's been like 2 or even 3h that it's alive and kicking....I don't want to reboot to check if it will be the same lol...

Oh, and before it was quite laggy, now it's pretty quick.

Weird, but awesome :good: :cool:
[RAZR HD Android Development] CWGSM3VO:
If you're referring to the radio issue (seems like you are based on what you said above) that problem was resolved quite some time ago and should only surface in older builds before the fix. One of the symptoms of a stuck rild was extreme lagginess as the process would consume what it could of processor time which you (the user) would see as lag/slowness.

I've managed to work around this a little while ago. Seems the default cache sizes are not optimal (at least, based on my device) and I've managed to almost completely eliminate the lags. Music skipping is now a blip (and a very short one, have to listen for it) rather than a crackle. Was easy to repro before adjustment by listening to music and then drag down the statusbar (quick settings/etc) and you could hear it. Just tweaking a bit further here. Most of it seems to be related to cache size for the FAT32 external SD. At 32GB the cache size was insufficient to make caching effective at that size.
[RAZR HD Android Development] Mikerhinos:
Was still having it with 0309 build :/

Edit : and yes, I always wiped and clean installed every daily :(
[RAZR HD Android Development] CWGSM3VO:
No need to do a complete wipe between nightlies. You should just flash over top of the existing installation. Only need to do a clean wipe when moving between ROMs or because it's necessary (too much junk, etc).
[RAZR HD Android Development] Zeljko1234:
You described everything except cache size you set.
[RAZR HD Android Development] CWGSM3VO:
Yes because I'm still testing it and I seem to have a bad habit of beaking off before I complete proper testing and having it bite me in the rear. So I'm playing it safe this time around ;) It's also not just cache values but cache configuration as well. As soon as I'm satisfied, I'll post my findings and see if others can replicate and/or substantiate my findings.
[RAZR HD Android Development] MarcusWhite:
The dock is working again. Thank you, I hope bought a cup of coffee, I hope. I'm not sure what the cost is in Prague, ;) .
[RAZR HD Android Development] amedeh123:
I dont think so, Im using latest TWRP 2.8.5.1 with latest KK 20150104

Try RSD back to stock > update to KK bootloader > install cm11