yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Because there's not much code to make it upstream. I don't know why people "bash" the CM11 kernel, it's really polished most of the time. It's the rom that's kind of messy. Plus it caters to stability rather than sheer performance unlike some other kernels, so tweaks that could result in data loss or crashes is usually left out.

Changing the voltage, custom frequency tables with overclock, fsync disabled, experimental schedulers and governors usually won't make it into the kernel. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Yeah, the stock CM11 kernel has always been pretty stable when I've used it. The main problems with it are lack of governor options and other things that strike a better balance with battery life and performance than the CM11 defaults. But of course it's understandable why they'd leave that out of the stock kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I agree, and it's also why I often switch kernels. Eek out a bit of performance at little to no cost on battery life but dropping a bit of safety. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
I flash kernel for faux sound, which is not enabled in stock cm kernel.. The default cm call volume is too low.

I tried volume blaster but randomly the volume goes down.. Fax sound is more stable
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crewxp:
bumps :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Yes. I've used it. (Before Google locked Canada out.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PiperD:
So my inability to use Rogers' SureTap and TD's tap-to-pay feature is because of a Google restriction? The latter app keeps crashing whenever I try to configure tap-to-pay, while the former app says that I do not have NFC. This is on CM11 M6 with a Rogers Suretap SIM (and NFC enabled in settings for good measure)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
No, strictly talking about Google Wallet here, which used to work in Canada via a workaround but now doesn't work anymore.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Did you replace your battery with one that's missing the NFC antenna? I've never had NFC issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PiperD:
Nope - stock battery. My wife has a stock s3 so I'll try transferring something to her phone via NFC to see if that works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Just so you guys know, yes there's a menu button glitch in the builds since the 22.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tejajuloori:
can someone please explain what "This patchset was cherry picked to branch stable/cm-11.0 " seen in some commits mean? I thought there were no stable versions anymore and just the monthly M releases
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Where is that present?

Sent from my S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Webkit based browsers such as Dolphin and Naked Browser for example. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Menu key bug should be fixed on today's nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
What happens with that bug? The menu does not appear for dolphin?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
The menu key doesn't get released properly I believe, so the menu might just flash quickly as if you pressed it twice in a rapid succession.

---------- Post added at 11:04 AM ---------- Previous post was at 10:48 AM ----------

aaaaaand menu key is still broken.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Are you sure it's not just your settings? I've never had menu key issues on any nightly, and I update every day.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Ney ney. Observable on a clean flash of a nightly newer than 20th of May. If you check the current commits you'll see what I mean too. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Most stable/useful yet.

For anyone interested, I've long suffered bluetooth, battery, performance, stability issues with CM11 nightlies. If I weren't a flashoholic I'd have stayed on the old 10.2 December 2012 build.

Anyways, I think we're back to that type of experience now. I have a Ford Edge with Sync (touchscreen) and bluetooth is mostly rocking. Fast reconnects, etc.

Performance is good. Battery life is good. No reboots in 2 days.

CM version 11-20140520-nightly-d2lte

Kernel: DKP 3.4.90 <-- "dkp-aosp44-20140515.zip"

No special settings or tweaks enabled.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Install CyanDelta to get quick and easy nightly updates; you're a week behind! You can have CyanDelta flash custom kernels etc too, (I use it to replace the Dalvik engine, reenable Xposed, and flash DKP after each update automatically. :))
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Nothing wrong with the 20th nightly, all things considered. However, I'm wondering how do you re-enable Xposed after a flash? Just reflash a modded app_process? Link me? :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Set Xposed to install via ZIP files flashed manually in recovery (it's in Xposed's settings) and copy Xposed-Installer-Recovery.zip (Xposed tells you where to find it) to /sdcard/CyanDelta/. Now go to CyanDelta's settings, under "additional files to flash", and select the Xposed enabler. Now you can change Xposed's settings back to normal. Make sure to generate a new ZIP this way every time Xposed gets updated. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Ah duh, it's so simple since the Xposed 2.6 beta I should have thought of that. Thanks a bunch for shedding light!

FULL AUTOMATION GO
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I'm wary to update since this is the first "stable" I've seen since the beginning of cm11. I'll look at the change log though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
I have been reading your problems about reboot. I also jumped from 10.2 to Cm 11M6. Even though it was a milestone but for me had serious memory leaks.

I suggest you do a nandroid of your current m6 and then try latest nightly. Look at the recent change logs for memory leaks.

I stayed on 10.2 mainly cause external SD card usability. As we all know Google has ruined it with kitkat.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shiniyoyo:
[MENTION=4311957]polobunny[/MENTION] what kernel are you currently using? & do you recommend the may 20th nightly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Guys please enlighten me on xposed. I have known about it but resisted using it. I have CM on my S3. I have nexus 7 stock kitkat rooted. I installed xposed on my nexus last night after reading your posts. I also installed Wanam kitkat module. I am looking for some of CM 11 functionality on my stock nexus 7. Such as quiet hours, is there one?

Dstruct ... You are using CM 11and yet you are using xposed just so you can customize cm11 even further?

Warnings about softbricking and bootloops during xposed install.... Is it as risky as installing a custom Rom or is it even riskier?

Where do you get most of your modules for kitkat? I have seen some kitkat repositories, just wondering where do you guys get yours from. Please share some of your xposed mods that you guys are using.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Currently using the 20th nightly simply because of a small glitch that popped up since the 22 in certain apps, one of them being a browser that I use. The nightlies have reached a pretty stable point however. Right now I have KT747 (Ktoonsez) using ktoonservative governor because I like how quickly it drops to a lower frequency (good for battery life considering my type of usage). I have used many kernels and they all have their pros and cons, but overall are very good. dkp, leankernel, BMS, quantum are among my favorite.

Wanam is meant to be used mostly with TouchWiz rom. I would recommend GravityBox for AOSP roms.

For me, I use Xposed to enhance furthermore the experience. I have a few select modules:

ActivityForceNewTask

Always Expandable Notifications

BootManager

Burnt Toast

CrappaLinks

CustomShare

EnhancedToast

ReceiverStop

Smooth System Progress Bars

StatusbarVolume

StopSwitchDelay

XVolume30

Translucent Recent

Some of these are very specific and might not fit for everyone.

You can find most modules in the official repository under Xposed app itself. For the rest, there's an XDA subforum dedicated to them

http://xdaforums.com/xposed/modules
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I went ahead and flashed 0527 for the Bluetooth and leak stuff. All stock, great so far! Might try dkp again for the improvements there also.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Carsus55:
I've noticed some significant LTE signal issues on m6. I have not read all of the posts. Has this been covered?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yep.

Solution is simple:

Boot to recovery

Make a backup

Wipe everything but your SD card

Flash to stock or stock based rom (TW!)

Try LTE (it works!)

Reboot to recovery

Restore backup

????

PROFIT
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Carsus55:
OK, just to make sure I understand, I came from official tw, tried PA, seemed slow, then tried m6. Just updated to 5/27 nightly. LTE does connect, and work... Intermittently. I will try this tonight however.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Oh Polo I won't call this simple :eek: I have had nightmares back when we were having to install new bootloaders (for cm 10) using latest stock. I even ended up uprooting to install stock Rom. I hope others don't run into those troubles, 'bootloops'

And thanks a bunch man for gravity box suggestion I'm loving that mod. :beer:

That developer Rovo89 deserves a donation for his work on xposed installer. Just awesome :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Carsus55:
So I did all this, seems to be working. Real test will be tomorrow. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Carsus55:
Deleted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
cheers

:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Carsus55:
Ok, still getting wonky speeds, however, didn't notice until I flashed BMS kernel, latest. Tried reflashing after wiping system, dalvik, and cache. Still strange. Getting like 2 mbps down and like 10-11 mbps up. I wouldn't think only flashing kernel would mess with the lte.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
What modem and bootloader do you have? Sometimes using a different modem will give you better speeds depending on a bunch of factors (location, provider, etc)

You can check with Device Info

https://play.google.com/store/apps/details?id=com.jphilli85.deviceinfo
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Carsus55:
Using Baseband/Bootloader UCUEMJB. Was on official 4.3 OTA before rooting and flashing anything. I just wiped, went back to stock, LTE works, but getting poor speeds, maybe 2-3 mbps. I'm now thinking it's the area/time of day. I just didn't notice such a huge decrease in the speeds in this area before now. Anyway, totally off-topic at this point. Thank you all for your assistance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Aaaaand menu key will be fixed in 29th nightly. For real, this time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Hopefully it fixes my battery life too...I updated to 05/25 & 05/27 and battery life is goat out terrible. Even with extended battery I'm only getting 2 hours screen time compared to 6 on early May nightlies.

Sent from my S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
There's a slew of commits in the next nightly, so fingers crossed. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
I hope it is fixed this time or I'm going to blame you :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
The nighly is out..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Is anyone seeing the nightly in CyanDelta?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Nope :( mine is still showing 28th as the newest.

Sent from my S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Updated to the new 30 and still have bad bat life :(

Could just be me though...only major wakelock I have is "NipWakelockCollector".

Sent from my S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Any wakelocks?

Edit: oops you ninja edited as I was pressing quote haha. It's NLP, as in, NetworkLocationProvider. Major being?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Same here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
I also cannot use suretap or the TD app. TD keeps crashing and suretap says I don't have the right Sim card even though I have one installed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djHandy:
You need a special SIM card from Rogers. I think it costs $10?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] v1nsai:
I recently bought two small bluetooth headsets, thinking that I could sync them to my phone and have mono/stereo headphones without cords. Well, it didn't work quite so easily. CM11 only lets me connect to one of them at a time. I'm trying to find the functions in the source code that will be called so I can try to make it ignore how many devices are connected at a time. Just to see what happens. First step is to find the relevant lines in the source.

So is "adb logcat" going to be the best way to view the log from a computer? I know it has the jvm log, but does it also show dmesg messages and whatever else there might be? Any other advice on how I might go about finding this would also be appreciated, I'm a self-taught programmer and I've never worked with something as complex as kernel source before.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
I have one installed.

Has anyone here gotten suretap to work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tejajuloori:
M7 will have more bluetooth fixes

http://www.cyanogenmod.org/blog/last-week-in-cm-may-31-2014
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Carsus55:
Fwiw I flashed the June 01 nightly, then BMS and it wouldn't boot past the kernel splash screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phazonclash:
Same with QuantumKernel and KT747.

Looks like they made major changes in the stock CM kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Carsus55:
Does it boot without a custom kernel? I haven't tried yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JBTY:
Hey guys I'm having issues getting the bootloader the link in the op seems to be broken can someone help me with that
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Here you go :)

http://xdaforums.com/showthread.php?t=2321310
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phazonclash:
Yes no problem with the stock CM kernel. Only the custom kernels like Quantum, BMS, KT747, etc. are problematic
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
Anyone have problems on recent nightlies with all SMS's showing up as MMS slideshows? See attached.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
On 31 nightly and all is fine. Didn't test 01.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Does anyone have a bug with Wi-Fi where you can't see new networks? I've had this for like 3 months even after multiple clean flashes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Nope.

I'm however having a MSM_OTG wakelock. Not sure if USB port is dirty or new CM bug. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nico3d3:
A new version of LeanKernel just got uploaded, it's working with the latest Nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Got a glitch from 31 to 02 nightly where viewing video content in a browser causes media_server (and then kswapd0) to spike the CPU usage and slow down the phone to a crawl, making all the apps try to exit to save memory. I imagine it's a memory leak of some sort, but if someone else gets this, you're not alone.

20th nightly is just fine. Back to it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phazonclash:
Thanks, I used to have good results with LK back in the CM10 days. I'm gonna give it a try
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JBTY:
Thank you very much! for any that follow this link remember to flash the modem as well

http://xdaforums.com/showthread.php?t=1831898
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Check your advanced Channel and 'region' settings for wifi.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
Is the screen rotation (sensor) effed up in the latest few nightlies? Or is it just me? Hope its not because I dropped my phone...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rdoac:
Looks like my Wi-Fi hotspot had gone in the last week or so. If I try it with a nightly from last week or last night the I get error under the menu option and can no longer use Wi-Fi. Restoring my backup works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tbrummell:
I just installed 03 nightly and the hotspot works fine, upgraded from the last milestone release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Can anyone confirm or deny that the equalizer tile in quick settings is working properly.

Start some music then open your quick tiles menu. At the bottom there is a tile titled equalizer with the icon dynamically showing an equalizer. The icon is working for my nexus 7 tablet but not on my s3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ser_98:
i'm running m6 and i'm having trouble with exchange accounts, am i the only one ??

i have my business email (exchange 2010) and my Hotmail account setup on my phone and both accounts can't sync. I'm having battery drain because of that.

any help ???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ThreeofNine:
I'm having the same issue. Did you get an answer on this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] n_alvarez2007:
I figured out the issue on my own. Apparently certain CM11 themes mess with the button responsiveness. Just the buttons though which is weird. I changed it back to the system default theme and buttons/switches all started working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djHandy:
Having a Bluetooth issue where it constant connects and disconnects over and over in my car with phone and audio support. Any hints? Running June 1 Nightly. Wiped clean and reinstalled with no luck.

Update - updated to June 5 nightly with no luck, but discovered turning off Phone audio makes it so Media audio works and stays connected. Linking phone audio back causes problems again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
4.4.3 on the latest nightly ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheemer:
Dialer FCs with lates 0 day modular
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benjihana:
The 6/06 nightly (skipped the 6/05) is causing a force black screen and then I have to battery pull. Dirty reversion to 6/04 isn't solving it and I'm afraid I'll have to nandroid back about a week. Anyone else experiencing this?

I was in Browser those few times.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] keithfrombm:
I didn't even notice the 4.4.3 on the 6/6 nightly! NICE!

---------- Post added at 03:27 PM ---------- Previous post was at 03:24 PM ----------

I drive truck, so my phone's using Bluetooth and Auxiliary audio day long. It seemed like a week ago, this issue was solved, but within last nightlies, it's returned with a vengeance. I usually have to disconnect/reconnect my Bluetooth a couple times to get it straightened out.

---------- Post added at 03:30 PM ---------- Previous post was at 03:27 PM ----------

ART. I read somewhere yesterday that ART is supposedly more stable now in 4.4.3. I tested it out a few weeks ago, for 24 hours, and didn't notice anything impressively different. Anyone else experimented with it? Tips or ideas? Cautionary tales of apps "breaking?"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] araemo:
Yeah, I just saw no real documentation that it WAS hexadecimal, most of what I saw said that the last digit is the week of the month... and there aren't 11 weeks in a month.

Yeah, the bootloader package updates more than just the bootloaders. It updates the TrustZone and Resource Power Manager firmwares as well as the actual bootloaders. (It does sound like RPM loads before the primary bootloader, so it is involved in boot, but it's involved in other things as well).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yeah absolutely. Bootloader is just one thing, make it easier than saying it updates the TZ and RPM as well as bootloader, because people would just get confused. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] araemo:
The tz/rpm firmwares were causing a ton of weird issues back in 10.0 development.. some users had no issues, others had constant crashes after pulling some updates into the kernel. It's just really hard to keep up on when you need to do a bootloader update when you never run stock.. because there's no real 'official' bootloader update list. InvisibleK's list is nice, but I don't think he's planning on maintaining it forever.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yep!

As far as it goes I don't believe they're not gonna go further than MJB. d2's are probably not gonna get official 4.4 since it's getting EOL.

As for a list, modems and bootloaders get released together, so you can follow modems order to get bootloaders versions.

Just to clarify one last thing, thought I said it earlier but I didn't, the last character in the bootloader/modem is the day. The second from last is supposed to be the month from A=1 to L=12. The third from last is the year again from A to Z.

LK3 becomes 2012 Nov 3.

MG2 becomes 2013 July 2.

MJB becomes 2013 October 11.

and so forth for all of them. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peneoark:
Subscribed ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liebowa:
I'm having this issue, too.

Why would I need to flash stock and, how would I do this now that I'm on MJB bootloader and modem?

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Samsung naming works as follows with the last 3 characters:

M= year

J= month

B= build#that month. Usually starts at 1, goes alphabetical after 9.

---------- Post added at 04:56 PM ---------- Previous post was at 04:53 PM ----------

With the new MJB bootloader you can not downgrade to previous bootloader. Attempting to downgrade the bootloader will hard brick your phone. The recovery flash bootloader packages are designed to fail should you try to downgrade (for your protection).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Would be surprised last number would be build number, since it matches up perfectly with the release date day. Quite the coincidence. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] araemo:
I am quite aware of that. But because of the way the checks are written, the MJB installer won't install over top of MJ2 anymore than MJ2 will install over MJB, so if I was stuck on MJ2, I'd be stuck on an outdated bootloader.

(Also, does MJ2 have the downgrade restriction? If so, you might be able to get away with going from MJB to MJ2? I won't be testing it any time soon.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Mj2 will allow downgrade, but trying to go mj2 first results in the same brick.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cristianpark:
Correct me if I'm wrong but MJ2 is a modification of previous bootloader for matching MJB's changes without losing ability of downgrading or flashing stock