[ROM][V500][5.1.x][CM12.1] Official CyanogenMod 12.1

[scaramonga]

Yup, RedKernel # 15 is the only thing that stops the black screens for me, on any build of latest version. Beginning to think that this will never get fixed properly, as most of the time its a random occurrence.

 

[Deltadroid]

Yup, RedKernel # 15 is the only thing that stops the black screens for me, on any build of latest version. Beginning to think that this will never get fixed properly, as most of the time its a random occurrence.

I wish there was someone to contact over at cm. Maybe Ricardo Cerqueira. Maybe on irc?

 

[Deltadroid]

I just updated to latest nightly build that was giving me trouble and installed red kernel #15. I've updated my bootloader to 20D. So, let's hope this fixes it.

 

[edisso10018]

Does pure aosp have this problem?

AOSP 5.1.1_r1 by adrianom doesn't have this problem. He uses a 4.4.2 base kernel by ckret.

CM 12.0 N20150417 doesn't have this problem.

Stock 5.0.2 (Korean international version) doesn't have this problem.

Only CM 12.1 and ROMs based on it.

 

[davebuk]

I just updated to latest nightly build that was giving me trouble and installed red kernel #15. I've updated my bootloader to 20D. So, let's hope this fixes it.

I've only had one instance of the black screen issue and that was with cm12. I'm currently running cm12.1 20150509 with stock kernel. Before I started flashing cm12 ROMs I was on either bootloader C or D. I can't remember but I do remember searching as a lot of posts were for A or B. Also have 4.4.2 base files as I get the dim screen post flashing ROMs but that's not an issue, just go to standby and back on and everything works as normal. @Deltadroid I'm not sure if I can check what bootloader I was running now I'm on cm12.1 but if you can tell me how I'll let you know ?

 

[Deltadroid]

Black Screen

Red Kernel #15 does indeed fix the "black screen" problem with the latest CM 12.1 nightly builds (thanks @Cal). I was having a BSOD every 10 minutes and then I installed Red Kernel #15 and its been fine since. I am also not having any trouble with my sdcard unmounting with Red Kernel #15. When I test the newer versions of Red Kernel, my sdcard becomes unmounted unexpectedly. I've noticed that Red Kernel #16 stopped working properly after the source code was rebased against CM12. Here are the steps I took to fix the problem:

1) Reboot to recovery
2) Flash V500-4.4.2-Base-KOT49I.V50020D_US-no-aboot-signed.zip
3) Flash twrp-2.8.6.0-v500.zip for 4.4.2 bootloader
4) Reboot to recovery (not system) to reload new bootloader.
5) Flash CM 12.1 Nightly ROM
6) Flash RedKernel-r015.zip
7) Flash Bump/Permissive kernel script v500-loki-kernel-to-bumped-permissive-kernel-signed.zip
8) Reboot to system

 

[tewje]

In the last week I had no problems with this configuration. I hope this finally solves the problem and you'll find a way to simplify this. Greetings!

 

[scaramonga]

1) Reboot to recovery
2) Flash V500-4.4.2-Base-KOT49I.V50020D_US-no-aboot-signed.zip
3) Flash twrp-2.8.6.0-v500.zip for 4.4.2 bootloader
4) Reboot to recovery (not system) to reload new bootloader.
5) Flash CM 12.1 Nightly ROM
6) Flash RedKernel-r015.zip
7) Flash Bump/Permissive kernel script v500-loki-kernel-to-bumped-permissive-kernel-signed.zip
8) Reboot to system

Yup, that is exactly the steps I took to get to where I am today. You can't really fail by following the above, and as you noted, it does fix the problem rather nicely

 

[ThunderBolt_BR]

Weird. I had no black screens with 20150523 nightly. Been using it for 3 days and everything is fine.

 

[jllabres]

can I use this rom for VK810 if I am not going to use the sim card?

 

[Deltadroid]

can I use this rom for VK810 if I am not going to use the sim card?

No. This rom is not compatible with vk810.

 

[zacharias.maladroit]

AOSP 5.1.1_r1 by adrianom doesn't have this problem. He uses a 4.4.2 base kernel by ckret.

CM 12.0 N20150417 doesn't have this problem.

Stock 5.0.2 (Korean international version) doesn't have this problem.

Only CM 12.1 and ROMs based on it.

Nope:

I've had this ROM installed for two days and I keep getting black screens which require reboots when using VLC media player to watch a .m4v video.

Any suggestions? I can capture logs if required.

http://forum.xda-developers.com/showpost.php?p=60980171&postcount=1103

Red Kernel #15 does indeed fix the "black screen" problem with the latest CM 12.1 nightly builds (thanks @Cal). I was having a BSOD every 10 minutes and then I installed Red Kernel #15 and its been fine since. I am also not having any trouble with my sdcard unmounting with Red Kernel #15. When I test the newer versions of Red Kernel, my sdcard becomes unmounted unexpectedly. I've noticed that Red Kernel #16 stopped working properly after the source code was rebased against CM12. Here are the steps I took to fix the problem:

1) Reboot to recovery
2) Flash V500-4.4.2-Base-KOT49I.V50020D_US-no-aboot-signed.zip
3) Flash twrp-2.8.6.0-v500.zip for 4.4.2 bootloader
4) Reboot to recovery (not system) to reload new bootloader.
5) Flash CM 12.1 Nightly ROM
6) Flash RedKernel-r015.zip
7) Flash Bump/Permissive kernel script v500-loki-kernel-to-bumped-permissive-kernel-signed.zip
8) Reboot to system

So what exactly introduced this issue ?

The changes in the initramfs or the kernel ?

according to the commits in RickRoll's git repo RedKernel 15 + 16 should work since the commit which added support for the color temperature interface came afterwards:

https://github.com/victormlourenco/...mmit/52e21c99668e2d2c22f578ea9e2da538c3ea60c7
(March 13th; RedKernel 16 released/uploaded March 12th)

It, of course, also could be that he pushed that commit AFTER he built that kernel

Not really sure though which branch the kernels are based off - also there's no tags or commits indicating which kernel matches with which state in the repo ...

 

[Deltadroid]

It's something in the zImage that contains the fix. Red Kernel uses the initramfs from the original rom. The bug was introduced in #16 when red kernel rebased against cm12.

 

[Deltadroid]

Cyanogen needs to appoint an active maintainer for the v500. The official maintainer, Ricardo Cerqueira, seems inactive for several months now. Commits that are specific to the v500 device tree and kernel are not getting checked in. This includes any fixes for Bluetooth selinux rules and the black screen problem.

 

[Deltadroid]

Great news..

The following changes have now been officially committed to cm12.1:

http://review.cyanogenmod.org/96023
http://review.cyanogenmod.org/96022
http://review.cyanogenmod.org/96021
http://review.cyanogenmod.org/96020

@infected_

We shall see if the bluetooth reconnect problem is fixed now.. there might still be more selinux denials that need fixing first. Its a start.

edit 2: The open bump commit is now being reviewed and will also probably be committed soon.

 

[Deltadroid]

Open bump is now official for v500

On the next build, make sure you use the correct permissive patch, if you use that. The kernel is not using loki anymore.

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

Thanks @jsevi83
Thanks @Skin1980

@infected_

 

[infected_]

which permissive patch?

been using 97617 since it was pushed, i have has a repopick on my build script.

never needed to set anything on permissive 'cause of it.

 

[Deltadroid]

which permissive patch?

been using 97617 since it was pushed, i have has a repopick on my build script, so even if it gets a new patchset, it will also be in my build.

http://forum.xda-developers.com/showthread.php?t=3081457

Permissive mode is to fix the Bluetooth reconnect issue after the Bluetooth service or system is restarted

There is also no more need to manually bump the kernel in the recovery... Obviously, but we may still need to use permissive mode to fix the Bluetooth reconnect problem until it is further looked at.

We just need to use the "already bumped kernel to permissive kernel" script now, perhaps.

 

[infected_]

http://forum.xda-developers.com/showthread.php?t=3081457

Permissive mode is to fix the Bluetooth reconnect issue after the Bluetooth service or system is restarted

There is also no more need to manually bump the kernel in the recovery... Obviously, but we may still need to use permissive mode to fix the Bluetooth reconnect problem until it is further looked at.

We just need to use the "already bumped kernel to permissive kernel" script now, perhaps.

i can set the kernel of my builds to permissive.

we just need to add this "androidboot.selinux=permissive" to BoardConfig.mk

but i've rather use SELinux the way it should...

so we may have to have a better look to see if its possible to solve that BT issue, without using permissive on the kernel.

 

[Deltadroid]

i can set the kernel of my builds to permissive.

we just need to add this "androidboot.selinux=permissive" to BoardConfig.mk

but i've rather use SELinux the way it should...

so we may have to have a better look to see if its possible to solve that BT issue, without using permissive on the kernel.

I completely agree. I also want to keep selinux in enforcing mode. I think we can fix the Bluetooth problem. Also, I think It is better that you don't permanently set the kernel in permissive mode so the problem gets attention.