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

[takis]

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.

Can you pls explain what pros do we get by the implementation of those commints and of the open bumps one?

 

[Deltadroid]

Can you pls explain what pros do we get by the implementation of those commints and of the open bumps one?

In the storage options, you will now have the option to unmount the sdcard to remove it while the system is running.

OTG storage options are now available.

Some fixes to selinux Bluetooth rules to try and fix the problem where Bluetooth devices dont reconnect after the Bluetooth service is restarted

Open bump fixes the secure boot error message on startup and also allows you to install cm12.1 without having to downgrade aboot to 4.2.2. Open bump is compatible with aboot from 4.4.2 and 4.2.2 firmware.

 

[jesuita]

Confused now.
Can I upgrade to the latest nightly like usual (through cyandelta) or do I need something else?

 

[Deltadroid]

Upgrade should be normal. No special action required.

Edit: except if you use a custom kernel. Custom kernel install scripts need to be adjusted to not remove the loki patch.

 

[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 think I fixed the selinux bluetooth problem. Can you please do a build with the following:
http://review.cyanogenmod.org/#/c/99660/

I can use as many testers as possible. Thanks, everyone.

Edit: we could also set only bluetooth in permissive mode like this:

# Bluetooth executables and scripts
type bluetooth_loader, domain;
type bluetooth_loader_exec, exec_type, file_type;
permissive bluetooth_loader;

# Start bdAddrLoader from init
init_daemon_domain(bluetooth_loader)

 

[Kraig.kak]

Help! Tried to use LG Mobile Support Tool to upgrade to Lollipop (VK810 WiFi only). Long story short, had some problems (equivalent to unplugging USB cable during flash), now tablet is stuck in download mode. Tried some key combinations, no good. Tried following these instructions. Flash Tool in CDMA mode gets stuck at 4%, in 3GQCT mode, gets to 10%. Tried both normal and CSE flash. Mobile Support Tool in Upgrade Recovery, fails at 10-11%. At my wits end.

---------- Post added at 11:39 PM ---------- Previous post was at 11:36 PM ----------

Sorry wrong thread!

Help! Tried to use LG Mobile Support Tool to upgrade to Lollipop (VK810 WiFi only). Long story short, had some problems (equivalent to unplugging USB cable during flash), now tablet is stuck in download mode. Tried some key combinations, no good. Tried following these instructions. Flash Tool in CDMA mode gets stuck at 4%, in 3GQCT mode, gets to 10%. Tried both normal and CSE flash. Mobile Support Tool in Upgrade Recovery, fails at 10-11%. At my wits end.

 

[infected_]

I think I fixed the selinux bluetooth problem. Can you please do a build with the following:
http://review.cyanogenmod.org/#/c/99660/

I can use as many testers as possible. Thanks, everyone.

Edit: we could also set only bluetooth in permissive mode like this:

# Bluetooth executables and scripts
type bluetooth_loader, domain;
type bluetooth_loader_exec, exec_type, file_type;
permissive bluetooth_loader;

# Start bdAddrLoader from init
init_daemon_domain(bluetooth_loader)

finishing a sirius PA build and i'll start right away a CM v500 one with that commit.

 

[Deltadroid]

Here is a potential fix for the black screens with the latest stock cm12.1 kernel. CM has merged the latest 5.1 source code, but they never updated the binary blobs for the video drivers. Here is a zip that you can flash to update the video blobs. I have fixed the install script to set the proper permissions.

https://www.androidfilehost.com/?fid=23991606952612021

 

[DSC05]

Here is a potential fix for the black screens with the latest stock cm12.1 kernel. CM has merged the latest 5.1 source code, but they never updated the binary blobs for the video drivers. Here is a zip that you can flash to update the video blobs. I have fixed the install script to set the proper permissions.

https://www.androidfilehost.com/?fid=23991606952612021

I'll test.....

 

[takis]

real developers!

This great tablet has some great developers supporting it! Thanks guys

 

[jesuita]

Ok.
Update went well, no more that error when booting, cool I guess.

Had a black screen already though.
Will test the zip for video blobs.

 

[Deltadroid]

Latest adreno video blobs didn't fix the black screen. It seems r015 is only solution at the moment.

 

[zacharias.maladroit]

Latest adreno video blobs didn't fix the black screen. It seems r015 is only solution at the moment.

RedKernel 15 with the new drivers doesn't show that issue ?


I just remembered, that I'm running the "Twilight" app (screen dimming, color temperature - red touch), which supposedly uses overlays

there are others like "Screen Filter", ...

So if you guys are using one of these - see if disabling or stopping them prevents the screen from going blank after some time.

It's not a "Fix" per se, but at least you don't have to turn the device off or reboot (sometimes pretty immediate after start up)

and it would clearly indicate - that there's a problem with overlays

 

[Deltadroid]

I've repackaged r015 for bumped kernels and included the latest adreno drivers and it's working good now.

 

[jesuita]

RedKernel 15 with the new drivers doesn't show that issue ?


I just remembered, that I'm running the "Twilight" app (screen dimming, color temperature - red touch), which supposedly uses overlays

there are others like "Screen Filter", ...

So if you guys are using one of these - see if disabling or stopping them prevents the screen from going blank after some time.

It's not a "Fix" per se, but at least you don't have to turn the device off or reboot (sometimes pretty immediate after start up)

and it would clearly indicate - that there's a problem with overlays

Funny, I'm also a twilight user.

 

[DSC05]

I've repackaged r015 for bumped kernels and included the latest adreno drivers and it's working good now.

Could you share it?

 

[Deltadroid]

Could you share it?

Ive posted patches in the Red Kernel thread for installing modified kernels on ROMs that don't use loki anymore. I shall only post the modified r015 kernel installer in collaboration with @Rick Roll

 

[ThunderBolt_BR]

Flashed latest nightly together with the new Adreno Libs provided by @Deltadroid and haven't had a black screen on a full day usage (browsing the web, facebook, g+ and 9gag). Are you sure that these black screens aren't app cause? I do not use any screen dimming app here.

[]'s

 

[Deltadroid]

Flashed latest nightly together with the new Adreno Libs provided by @Deltadroid and haven't had a black screen on a full day usage (browsing the web, facebook, g+ and 9gag). Are you sure that these black screens aren't app cause? I do not use any screen dimming app here.

[]'s

It did seem like the updated adreno libs helped. The black screen took almost an entire day of heavy usage to show up. I think Rick Roll is very close to the answer.

 

[zacharias.maladroit]

Funny, I'm also a twilight user.

disabling it unfortunately didn't help.

For ROMs which have the LiveDisplay feature enabled - it would also be worth a try to disable it temporarily ...

Meanwhile RickRoll pushed an additional kernel with voltage updates