Search results

echo performance > /sys/devices/system/cpu/sched_balance_policy/current_sched_balance_policy

Idk. I don't use flashify. I would recommend using fastboot.

Reflash the latest radio and bootlaoder in fastboot. I had same issue when restoring a backup. I tried everything I could think of before doing that, but that's what fixed it for me believe it or not..

Delete..

What a great little device [emoji6]

And the floodgates are about to open... Not to mention you already posted this in the correct section??

It has nothing to do with the boot.img and everything to do with flashing the userdata.img. To correct the issue avoid flashing the userdata.img and cache.img or if you already did that you can do the following: Boot into STOCK RECOVERY (MUST BE STOCK RECOVERY. NO CUSTOM RECOVERY) Clear cache...

Its apparent that the OP is just trolling. From his previous posts, he owns a Note 3 and Note 4..

https://play.google.com/store/apps/details?id=com.sharpregion.tapet

Sorry to hear that. That sucks. I didn't get any info until an hour before it was delivered. Tmo sent me a text this morning that it had shipped, I checked the tracking and it was already out for delivery. I def wasn't expecting it to come today, but I'm not complaining. Believe me it is worth...

I ordered the 64gb on 11/19 @ 3:25pm EST and it shipped last night and recieved it this morning at 10am. I opted for expedited next day shipping.

I am looking for a close to stock ROM. Wanted to check this out since I never had before..

Does anyone have a link? Euroskank is only sending 0 byte files. Its back up..

Classic XDA... One person needs to feel more important than the next and needs more attention, so BAM! Let's create an issue out of a non-issue and grab some attention..

No

He did.

On CAF06 I'm floating around 40c while charging and tethering. Normal idle (e.g. Not charging or tethering) seems to be around 33c. Still need to give it more time, nonetheless an improvement over CAF05.

With the CAF05 I also have high battery temps and phone is also noticeably warmer to the touch with normal usage.

AcDisplay

6 is the default..

Not having that issue on the 0904 Nightly. If you're using a theme, try reverting to default and see if issue persist..

Settings > display & lights > prevent accidental wakeup Make sure that's not checked or be mindful of your proximity sensor..

OK.. Not realizing I was on yesterdays nightly, when I updated to today's I had the same issue. Wipe data from contact and contacts storage and report back..

Not happening on my end.. Did you/can you get a log??

Pressing every button? Holding the power button works. And no, not facing any issues. Without any detailed info its hard to help.. Grasping at straws but make sure that 'prevent accidental wake up' in display settings is unchecked or make sure proximity sensor remains uncovered when turning on...

I was under the same impression. I don't have any data to back up the claim, but when I was running the test builds, more heat was being generated even at idle..

The recents button jank has been there since forever. To say its not present in the official nightlies isn't accurate. It only seems to be present when dalvik runtime is selected, I assume it has something to do with garbage collection. Steve was working on a solution but never seem to make past...

Considering the G watch R has yet to be released.. I would assume the original.

Defeats the entire purpose..

You have to have your device in vibrate mode for this to work. From your screenshot you have the sound enabled. Only works if the device is in vibrate mode..

As its been noted many times, battery life is very subjective. To answer your question in short, CM tends to be more battery friendly than compared to stock.

Not sure if you meant you didn't understand what "just my 2 cents" means? If you didn't, just means that's my opinion..

Battery life is very subjective. What's good for me may not be so good for you. Usages can vary greatly between users. My suggestion would be make sure you're on the latest M release or nightlie, make sure you don't have a rouge app creating unnecessary wakelocks, and give it a day or two...

Without knowing specifics, it is something on your end. Stock CM kernel gives the best battery out of the box compared to stock..

yeah mpdecision is borked for sure.. I am digging around now to see what i can find. edit: So upon further investigation, its clearly an issue with the mpdecsion binary used in the build. Replacing the mpdecision binary with the one from the latest CM nightly resolves the issue.. Just to...

Anyone else that is using the cm-11-20140823-PROOF-OF-CONCEPT-hammerhead.zip experiencing this?? E/MP-Decision( 1454): Error 2 getting cpu 1 online status at /sys/devices/system/cpu/cpu1/onlind E/MP-Decision( 1454): Error 2 getting cpu 2 online status at /sys/devices/system/cpu/cpu2/onlind...

Yes. Still easy to enable without having to build from source..

The call recording feature is still there and is still able to be enabled. https://github.com/CyanogenMod/android_packages_apps_Dialer/tree/cm-11.0/src/com/android/services/callrecorder

Not a single one. Running the latest and greatest. No xposed, no mods, no nonsense, just clean CM.. The more info you can provide, the more we can help you out. Logs are even better if you happened to grab one of the random reboot.

There were no new commits. The one commit came early yesterday morning (EST). That is more than likely why it didn't build, not because it failed..

[SKIN_THERMAL_management_1] algo_type monitor sensor xo_therm_pu2 sampling 10000 thresholds 40000 42000 44000 thresholds_clr 38500 40500 42500 actions cpu+lcd cpu+lcd cpu+lcd action_info...

The CM team implemented a build overlay for a reason. The reason is not because they are not ready to ship it, but because they don't want it to ship.. So I am not sure the source of your information, but you're misinforming others. http://review.cyanogenmod.org/#/c/70497/

I agree.. I suppose it comes down to a convenience feature. I always prefer to use native options before going to a 3rd party alternative. It would be great if the issues get worked out. In many cases this is a very useful feature IMO. Use cases vary from state to state, and country to...

https://code.google.com/p/android-apktool/ Also.. For those that have enabled the call recording, I found that if you use speakerphone the sound volume of the other party is 10x's better than compared to when using the earpiece. And also again.. I will not explain or be giving any tutorials on...

It's not in the settings.. You have to enable it within the actual Dialer.apk. meaning.. You must decompile the actual .apk

To help clarify with the confusion on call recording.. It will not be enabled by default for legal reasons. It needs to be enabled within the build. It is possible to do this without having to build from source. It can be enabled from within the Dialer.apk. the call recording works, but the...

After a random reboot you will need to pull the last_kmsg. You can do that by either using adb, or a file manager and navigate to.. /proc/last_kmsg Or adb pull /proc/last_kmsg There are other ways to do this as well.. I just listed the 2 easiest IMO.

You're going to have to provide more information and something to back it up (logs). I am running the latest nightly and have not experienced any such issues. So it might be something to do with your setup??

WiFi hotspot has worked for me on all nightlies for at least the last 6 months. Never had issues with tethering at all..

Most recent nightly with stock kernel and none of that xposed nonsense.. That game ran smooth as butter. 1st time I ever played it, actually like it.