[ROM][5.1.1] CyanogenMod 12.1 [NIGHTLY]

[Olivier]

Before anyone asks: Yes, I am your new CM maintainer and yes, official nightly builds will eventually come (once we're ready).

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.1 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.

/* Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 */

NOTE
Should you ever face any issues, provide logs (use Google to find out how to gather those). Additionally, I need to know what build you're on, hence you should mention the build number.
Hint: "It doesn't work" is not a bug report and will be ignored (and eventually removed). To keep the thread clean, try to use DevDB for real bug reports.

SUPPORT ME
If you like my work, feel free to buy me a beer (or two ).
You can also contribute to CM using gerrit.

DOWNLOAD
Official builds
Screenshots

SOURCE
CyanogenMod
Kernel: CyanogenMod/android_kernel_sony_msm8930 (branch cm-12.1)

XDA:DevDB Information
CyanogenMod 12.1 for Sony Xperia L, ROM for the Sony Xperia L

Contributors
Olivier
Source Code: https://github.com/CyanogenMod/android_kernel_sony_msm8930

ROM OS Version: 5.1.x Lollipop

Version Information
Status: Beta

Created 2015-09-07
Last Updated 2015-09-26

 

[Olivier]

Changelog

CHANGELOG

20150922
- Added and enabled BFQ I/O scheduler
- Synced kernel f2fs driver with upstream
- Enabled proximity wake
- Enabled WCDMA only mode
- sepolicy cleanup

20150907
- Fixed manual network selection
- Patched CVE-2012-6657 and CVE-2014-9529 in the kernel

20150906
- Initial public release
- Fixed keys (specifically the camera button)
- The device will now vibrate before the user can choose between Android/recovery, reminding him to actually make the choice (by hitting the volume rocker or not)
- Patched tons of CVEs (common vulnerabities and exposures) in the kernel
- SELinux patches
- Updates from common Google 3.4 kernel
- Switched logcat buffer to userspace (enabled logd)
- Offmode charging: Replaced deprecated charger with healthd (this also adds battery percentage as well as tricolour LED support)
- Updated vendor init; this means the model number will be "Xperia L" on both C2104 and C2105 from now on, however, build fingerprint and description are now variant-specific.
- Synced kernel with CAF (LA.AF.1.1_rb1.18)

 

[rostifaner]

@Olivier
Woohoo, awesome work bro,THANKS

 

[adil089]

Great work man. I'm going to test this right away.

 

[Luncer]

Welcome to our device @Olivier
You rocked bro with this rom
I found a new bug
Can u fix manual network registering problem?
I've face with this bug since beta 4
Can you fix that? @Olivier

Sent from my taoshan using Tapatalk

 

[Joel16]

For those of you who don't know Olivier, and you're reporting bugs. This is what he's gonna say, "Log-cat or it didn't happen". Also let's try to keep this thread clean, shall we?

 

[corphish]

Logs?

Did someone say logs?

All logs are in attachments with appropriate names.
Since I have a habit of examining the logs to see what went wrong, I use filters a lot, hence I will mention the commands executed:

1. HDR

adb logcat *:e | grep -i "camera" > hdr.txt

2. Torch

adb logcat *:e > torch.txt

3. Manual Network Selection (Until now, I thought it was my carrier problem )

adb logcat -v long > manual_network

As for HDR and torch, logs just bombarded terminal, hence didn't go through the text files.
For Manual Network, I got nothing much in reasonable detail.

Hope you find the cause.

Cheers,

Edit:Clash of Clans not working.
Logcat says:

java.lang.SecurityException: Not allowed to start service Intent { act=com.google.android.c2dm.intent.REGISTER pkg=com.google.android.gsf (has extras) } without permission com.google.android.c2dm.permission.RECEIVE

Anything to do with the new SELinux Patches you have added @Olivier?
Anyways changing it to permissive wont help (setenforce 0).

 

[Olivier]

3. Manual Network Selection (Until now, I thought it was my carrier problem )

adb logcat -v long > manual_network

Have you been facing this issue since the beta 4 release (like @Luncer)?

Anything to do with the new SELinux Patches you have added @Olivier?.

Nope, I don't think so (as they were applied to the kernel). I guess what you're suspecting are SELinux denials - however, I haven't made any changes to the sepolicies yet.

For denials, just do the following (in an ADB shell or a Terminal Emulator):

dmesg | grep 'avc:'

However, it could be the log (dmesg) is flooded for whatever reason, hence this should be your best bet:

cat /data/misc/audit/audit.log

 

[Luncer]

Have you been facing this issue since the beta 4 release (like @Luncer)?


Nope, I don't think so (as they were applied to the kernel). I guess what you're suspecting are SELinux denials - however, I haven't made any changes to the sepolicies yet.

For denials, just do the following (in an ADB shell or a Terminal Emulator):

dmesg | grep 'avc:'

However, it could be the log (dmesg) is flooded for whatever reason, hence this should be your best bet:

cat /data/misc/audit/audit.log

I was tried that in beta 4 and latest rr and infinitive
Nerwork selection is buggy


Sent from my taoshan using Tapatalk

 

[corphish]

Have you been facing this issue since the beta 4 release (like @Luncer)?


Nope, I don't think so (as they were applied to the kernel). I guess what you're suspecting are SELinux denials - however, I haven't made any changes to the sepolicies yet.

For denials, just do the following (in an ADB shell or a Terminal Emulator):

dmesg | grep 'avc:'

However, it could be the log (dmesg) is flooded for whatever reason, hence this should be your best bet:

cat /data/misc/audit/audit.log

Yup, since beta 4 release.
And thanks, I will take a look with those commands.

 

[beuntje]

Can someone help me out, as i'm unable to find the correct Loggings for my issue..

When changing the Phone when it is off, i cannot boot it up when charger is attached.
But when i disconnect the charger, i am also unable to start the Phone up,
it keeps displaying the batterty picture (charging icon)
I have to Pull the battery, after that i can boot up my Phone normaly.
Hope someone has the same issue and is able to get some logs... (or assist me in getting the logs...)

 

[kennyFF92]

Can someone help me out, as i'm unable to find the correct Loggings for my issue..

When changing the Phone when it is off, i cannot boot it up when charger is attached.
But when i disconnect the charger, i am also unable to start the Phone up,
it keeps displaying the batterty picture (charging icon)
I have to Pull the battery, after that i can boot up my Phone normaly.
Hope someone has the same issue and is able to get some logs... (or assist me in getting the logs...)

After pulled out the charger you need to wait until the battery picture disappear, then you can turn on the phone. No need to take out battery

 

[beuntje]

After pulled out the charger you need to wait until the battery picture disappear, then you can turn on the phone. No need to take out battery

Sorry, but that doesn't happen

I have the same issue when charging the Phone when powered on.
When pull out the charger the green led keeps burning
After reboot all is ok, till i charge the Phone again...

 

[Luncer]

Sorry, but that doesn't happen

I have the same issue when charging the Phone when powered on.
When pull out the charger the green led keeps burning
After reboot all is ok, till i charge the Phone again...

I think this led bug is googles source problem cuz I see this bug in infinitive
And both of these roms based on r12

Sent from my taoshan using Tapatalk

 

[Aenadon]

I think this led bug is googles source problem cuz I see this bug in infinitive
And both of these roms based on r12

Sent from my taoshan using Tapatalk

I'm on beta 4 and the led doesn't stay on. However I do face the other problem too (can't turn on while charging). When that happens, I pull the charger out and wait till the battery is gone, as you said

Sent from my C2105 using XDA Free mobile app

 

[Olivier]

Okay guys, a new experimental build is up.

Manual network registration should be now fixed (works for me at least), as well as two other security vulnerabities in the kernel (CVE-2012-6657 and CVE-2014-9529).

You can get it from my download server.

 

[beuntje]

Sorry, but that doesn't happen

I have the same issue when charging the Phone when powered on.
When pull out the charger the green led keeps burning
After reboot all is ok, till i charge the Phone again...

I think this led bug is googles source problem cuz I see this bug in infinitive
And both of these roms based on r12

Sent from my taoshan using Tapatalk

Reflashed the Rom (using the Experimental version)
all seems to be ok now, led is no longer burning when disconneting the Charger.

Seems that my GAPPS version was the cause

 

[Abhinav1997]

Thread cleaned. Please provide logs with the bug reports.

Regards,
XDA-Staff

 

[Flashing_Expert]

incompatible games on playstore

Hi
these two lines must be in build prop else games like MC5 will not be compatible with our device

ro.product.board=msm8960
ro.product.device=taoshan

I used latest sources and vendor sources from TheMuppets to compile build, so idk if it's their problem or not... :good:

 

[matrix2012xman]

I am sorry for posting here but I didn't know how to post in bug tab
Anyway, I can't understand this message, this screenshot from my xperia l device, this app was working in beta 4 without any issues
Second, I think there are something in data connection, sometimes gone and sometimes work but slowly till turning it off and turn it on again , NOTE .. I faced this error in a good single place
That wasn't in beta 4