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

[Deltadroid]

Thank you very much for the very good instructions. I was successful and have finally no more black screens.

Any questions I have. What ist to do, If I flash a new CM 12.1 Nightly? Do I need to repeat steps 6 and 7?

Can it be that the battery consumption is higher (with RedKernel)?

Yes. Red Kernel r015 is not bumped so that is what the second script is for. The official cm12.1 nightly builds are bumped, but when you install r015, it makes the kernel loki, so then the third script changes back to bumped.

You only need to flash your recovery and bootloader when you want to change it or update it. Just one time usually.

 

[Deltadroid]

The Bluetooth sepolicy should now be fixed in the next nightly build. The selinux Bluetooth patch I just posted a few back should not be necessary anymore after the next build.

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

 

[ThunderBolt_BR]

The Bluetooth sepolicy should now be fixed in the next nightly build. The selinux Bluetooth patch I just posted a few back should not be necessary anymore after the next build.

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

Something very weird happened to me on the last build: I went to 4.4.2 base, flashed TWRP 2.8.5.0 bumped, the nightly and your patch to fix the Bluetooth issue. Nightly booted OK but I started having SDcard unmounted messages appearing when unlocking. I hadn't had any message before with 4.2.2 base...

 

[Deltadroid]

Something very weird happened to me on the last build: I went to 4.4.2 base, flashed TWRP 2.8.5.0 bumped, the nightly and your patch to fix the Bluetooth issue. Nightly booted OK but I started having SDcard unmounted messages appearing when unlocking. I hadn't had any message before with 4.2.2 base...

updating to red kernel will fix the unmount issue. The stock cm kernel needs to update the sdcard driver to work with the latest 4.4.2 firmware.

 

[Deltadroid]

I just want to note that the next nightly build fixes the resolution of our devices. CM nightly builds have been 1080x1920, but the correct resolution is 1200x1920. This is fixed in next nightly and it looks a lot better now.

 

[Cal]

I just want to note that the next nightly build fixes the resolution of our devices. CM nightly builds have been 1080x1920, but the correct resolution is 1200x1920. This is fixed in next nightly and it looks a lot better now.

What about the Color Correction mentioned in post #335 over on Rick Roll's thread? Will the above fix that also? Like I stated in post #336 in Rick Roll's thread, as soon as CM-12.1 official 2015-6-05 is posted I'll be testing.
Thank you Deltandroid.

 

[Deltadroid]

What about the Color Correction mentioned in post #335 over on Rick Roll's thread? Will the above fix that also? Like I stated in post #336 in Rick Roll's thread, as soon as CM-12.1 official 2015-6-05 is posted I'll be testing.
Thank you Deltandroid.

No, not yet. The fix still needs testing.

 

[Cal]

Just dirty flashed the latest CM official June 6 and with the default CM kernel, I got dimming (extreme). Felt my way to display & cranked brightness to full & default processor was idling at 918Mhz also. So now using the RRxx22 kernel & brightness is fine, but still 918Mhz idle. Will stay & check resourses.

 

[Deltadroid]

Just dirty flashed the latest CM official June 6 and with the default CM kernel, I got dimming (extreme). Felt my way to display & cranked brightness to full & default processor was idling at 918Mhz also. So now using the RRxx22 kernel & brightness is fine, but still 918Mhz idle. Will stay & check resourses.

The backlight is not set for the 4.4.2 bootloader with stock cm kernel. That is why it was dim.

 

[Deltadroid]

Bluetooth is now fixed. no more need for any patches for sepolicy or permissive mode.

 

[Cal]

The backlight is not set for the 4.4.2 bootloader with stock cm kernel. That is why it was dim.

What do you think about the 918Mhz idle? If I don't get too much memory use I'll stay and maybe the next nightly may 'fix' that? If the RR#xx22 kernel holds.
Have you tried the latest nightly, or is it just me??

 

[Deltadroid]

What do you think about the 918Mhz idle? If I don't get too much memory use I'll stay and maybe the next nightly may 'fix' that? If the RR#xx22 kernel holds.
Have you tried the latest nightly, or is it just me??

I'm on 20150606 and using ondemand. The cpu idles around 486, but goes up and down. Seems normal. I think a factory reset will fix it. The problem you are having must be from changing performance settings with the other kernel and now something got stuck when trying to use stock.

 

[mackeev]

Bluetooth is now fixed. no more need for any patches for sepolicy or permissive mode.

Are you sure? Latest nightly keeps asking my bt device's password every time I re-start. And your sepolicy patch does not work anymore (v500 won't see any bt device at all if I flash it!)

 

[Deltadroid]

Are you sure? Latest nightly keeps asking my bt device's password every time I re-start. And your sepolicy patch does not work anymore (v500 won't see any bt device at all if I flash it!)

Did you try unpair Bluetooth devices and then pair over again?

I can now restart Bluetooth service and reboot and the devices reconnect.

Also, that Bluetooth sepolicy patch will still work for all cm12 nightly builds. It may seem that it will not connect, but it will eventually.

 

[mackeev]

Your patch works only if I un-pair and re-pair the device. Without the patch, it keeps asking for password (unpairing and re-pairing won't help). So, in terms of bt device pairing, nothing's changed for the better in the new build (apart from having gotten worse). At least, for me.

 

[Deltadroid]

Your patch works only if I un-pair and re-pair the device. Without the patch, it keeps asking for password (unpairing and re-pairing won't help). So, in terms of bt device pairing, nothing's changed for the better in the new build (apart from having gotten worse). At least, for me.

I found the problem and have submitted a patch.

http://review.cyanogenmod.org/#/c/100316/1

 

[Deltadroid]

Its merged now.. The next build should fix the problem, hopefully.

 

[Deltadroid]

microphone fix for Google Hangouts

Ive noticed that the microphone is not working properly when making calls with Google Hangouts. Ive created a flashable zip that fixes the audio policy for the v500. Can someone please test this and verify if the microphone is working ok now with Google Hangouts?

cm-12.1-v500-audio-policy-sample-rate-signed.zip

Thanks @jsevi83

 

[davebuk]

Ive noticed that the microphone is not working properly when making calls with Google Hangouts. Ive created a flashable zip that fixes the audio policy for the v500. Can someone please test this and verify if the microphone is working ok now with Google Hangouts?

cm-12.1-v500-audio-policy-sample-rate-signed.zip

Thanks @jsevi83

@Deltadroid I tried hangouts with 20150606 and the receive audio did work but seemed a little distorted. I ran your patch and the audio seemed to work fine.

Will there be a way to get the CM team to sort out the USB OTG so we don't need your patch for that?

 

[Deltadroid]

@Deltadroid I tried hangouts with 20150606 and the receive audio did work but seemed a little distorted. I ran your patch and the audio seemed to work fine.

Will there be a way to get the CM team to sort out the USB OTG so we don't need your patch for that?

Thanks for testing. The usb otg patch was recently merged in the latest nightly build. The patch for usb otg isn't necessary anymore with 20150606.