Search results

In this build, color calibration settings don't apply on boot. You have to go into the setting to set it even though the values didn't change.

SIM works :)

I'm getting some serious lag in jef's 08/03 build like when unlocking the phone using only swipe, the phone would freeze for a moment, or even turning on the phone when playing music, the visualizer would freeze a bit, screen being unresponsive as well, among many other instances where lag also...

I do, on your build, my SIM isn't detected after a clean flash without GApps too. Reverting fixed it though.

I'm on the 02/03 build. Under lock screen in settings, it just displays a blank screen. Wiped and clean flashed and still same result. Is it happening to anyone else?

Have you tried changing your SELinux to permissive? Mine couldnt work with enforcing. Had to use permissive anyway because of V4A.

I can't seem to get fingerprint to work correctly. Every time I try to register it just gives me the dialog box that enrollment was not completed. I am on 18th using agsola's build, N910G and SELinux is on permissive. I don't think I've missed anything out for it to supposedly work? Or is that...

Language & Input.

I was on 21st, now 22nd, both with no problems whatsoever regarding bootloops so something must have went wrong in your set up.

Have you even tried any of the basic fixes (reboot, wipe app's cache and data, factory reset and reflash) to see if the problem still persists? I am able to change the resolution so the problem definitely lies on your end only.

Rebooting usually helps with issues related to themes as they don't apply correctly sometimes.

These fixes are literally in the latest nightlies from 28/09 onwards, there's absolutely no need to flash the fixes after flashing the said nightlies so if you're on a older nightly, now would be a great time to update. :good:

I believe it's meant to be like this due to something related to GPU, nothing to worry about though, it's normal.

Not so sure if it would work. Most here would strongly advise you not to flash SuperSU in reovery as Superuser is already built-in and could cause some issues (this used to be the case in the past, not sure if anything has changed now). But if you insist on using SuperSU, just enable root in the...

Mine is filled as you can see from the attached image so not sure why it is not so for you. I'm certain you waited a period of time before checking the statistics and not immediately after turning it on so I'm not even going to list that out as a cause.

That's caused by the built-in Superuser, not sure why. Using SuperSU here and the statistics page is filled.

Mine has gotten somewhat leggy/slow as well. Not really sure as to which nightly this started occurring on. It would take a bit longer to clear all tasks as compared to last time.

mike13ftw Maybe try doing a full wipe (clear everything, except MicroSD), I do sometimes get weird issues if I do not perform a full wipe but a factory reset so maybe it may help you as well.

Using the latest Lollipop one is fine. My baseband is BOC7.

No, you are no longer required to change it anymore... This has been the case for a long time now.

Something must've broken battery mode in the recent nightlies as it used to work before which must be the reason why you're not experiencing any difference (try using a kernel manager to change the governor). Performance mode doesn't change a thing to CPU frequencies like its supposed to.

Nope, doesn't occur on mine. Theme installs fine and applies correctly.

Is battery mode working for everyone else from the 31/7 night lies? I noticed its not changing the governors as it should when changing modes in 01/8 and 31/7 nightlies. Not too sure about previous few as I don't have time to test them.

They are the same. It's just called fauxclock on the home screen/app drawer

There are but I was just asking if the integrated battery mode in the ROM would actually change the governor since it usually don't with custom kernels. I have tried and it does. Thanks for the quick reply!:)

Gekke, are we able to change it to performance mode using the included battery mode like before or must FauxClock be used? I do recall it still usable in bootv3 (not sure about the later versions)

Ah, that makes sense. Thanks for the info. AuxXxilium, awesome support on this kernel. Appreciate all the effort you've put into this. I shall be eagerly waiting for the next build. :good:

All I did was install SuperSU using the app from the Play Store. Than set thermal settings on boot in FauxClock. The rest seems to be fine when set on boot. Though can't test more as currently busy.

The Set On Boot shut down issue is still present I'm afraid.

Interesting, just updated to 1.3 OC, the capacitive buttons when the screen is off are still able to vibrate when tapped on.

I can't seem to get this to work on N910G KK bootloader. After installing the kernel (wiped cache and dalvik), after the splash screen, the screen just turns black without any boot logo. Could the issu lie in the bootloader?

Maybe the Gapps you installed replaced Trebuchet with Google Now launcher. Try reflashing the ROM without Gapps to confirm my theory. EDIT: Never mind, missed the previous posts.

That's very odd, I can swipe up and it does bring about more options. Maybe try rebooting?

I switched to 5.1 no problem without wiping my data but just the usual. As for 5.1.1, it should be the same I guess.

gekkehenkie11 I have a bug to report. Not sure if anyone else experienced this but whenever I try to stop recording a video with the stock CM camefa when the battery is at 15% or less, the phone will crash and reboot (i think it even wiped dalvik cache because when it rebooted, I got the...

Is anyone able to move apps to the SD card on the latest nightly? I saw that they enabled that in cmxlog and I am still unable to move apps to the SD card even though my install location preference is set at let the system decide.

Have you tried doing a full wipe and reflash? If that doesn't help then I don't know how else I can help you as I do not have that issue myself.

http://forum.xda-developers.com/note-4/orig-development/official-cm12-910f-910g-t3046965/post60526400#post60526400 This is my solution to get AudioFX working, well most of it. Only reverb doesn't seem to be working.

1)MMS is working for me, am using Hangouts though. 2) stock CM camera works as well but I do occasionally get Camera Error but it no longer require a reboot to fix it. Just tap OK and then tap the camera app again and it should be fine. 3) Haven't really tinkered with display settings so can't...

To those who desire to get AudioFX working, I just found a solution, a semi-working one though. Only reverb doesn't work but the equalizer and presets do (on headset and speakers at least, didn't try the others)...

I'm on 30/3 nightly and do not have that issue. Did you dirty flash? If you did, do a full wipe and see if that helps.

I'm on TWRP 2.8.5.0 and do not have that issue. You must be other recovery I assume since I read you only get that error when using PhilZ.

I have it too, usually when I reboot then I have to to go the WiFi settings to connect. But this may be only occurring on my end but my Note doesnt seem to like 5GHz WiFi since it keeps on dropping back to 2.4GHz after a few minutes of connecting to 5GHz. I'm on N910G latest nightly BTW

I had to wipe numerous times to sort it out though, countless reboots didn't help since I kept seeing the time it kept the CPU awake soaring.:victory:

Battery drain by mm-qcamera-daemon Is anybody here experiencing battery drain caused by mm-qcamera-daemon in the latest CM12 build? I had this issue since the official 5th's official nightly where I would leave my phone on standby overnight from 100% till 87% 8hrs later with mm-qcamera-daemon...

No one?

I recently installed franco.Kernel R15 on my stock OPO with TWRP and I noticed when I plugged in my headphones, there is a full second delay of it being detected (this was also present on R14). Is this normal? This occurred on several other kernels on my OPO as well such as stock Mahdi's, stock...