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

[Cal]

CM just came out with 2015-6-09. Will continue testing the RRxx22 kernel with this ROM...but not expecting anything and some commits look like they are entered so all 'quirks' may be fixed.

 

[davebuk]

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.

Thanks for the info about OTG. To be honest I haven't tried it without the patch recently. I'll give it a go sometime to confirm.

Sent from my Nexus 5 using Tapatalk

 

[mackeev]

Flashed 0609. The problem with bt did not go away! The same behavior as I described in #215. Deltadroid's sepolicy patch works fine, though

 

[ukguy115]

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.

Thanks for all your work lately on the gpad. Seems like this thing running as good as ever, even the little picky stuff.

 

[Deltadroid]

Flashed 0609. The problem with bt did not go away! The same behavior as I described in #215. Deltadroid's sepolicy patch works fine, though

Thanks for testing. I'll check the logs on the latest build.

 

[Pootch]

Hello.

Auto rotation of the screen does not work. Any way to fix this?

Br
Pootch

Edit: Reflashed same version > works.

 

[vimesUK]

Not sure why I didn't motive this ROM thread earlier, anyway....

Did a full wipe and format, without apps restore, and it seems well but...

After first boot the first app I tried invoked landscape mode but them the tablet seemed to be kicked in the orientation and would no longer auto rotate. A reboot sorted that out.

I have had a black, blank screen and read the thread to see that I have not been the first....! I'm not sure as yet if that it well be a common occurrence or not but is the r15 Redkernel still considered to be the preferred choice of potential fixes.? If so would I then need to change baseband to 4.4.2, for the potential brightness issue....?

The ROM seems responsive and thankfully works fine with my CCTV app, and others.

Thanks for what you have done here, and for all the other work you continue to do, as it is most appreciated.

 

[GXGOW]

Not sure why I didn't motive this ROM thread earlier, anyway....

Did a full wipe and format, without apps restore, and it seems well but...

After first boot the first app I tried invoked landscape mode but them the tablet seemed to be kicked in the orientation and would no longer auto rotate. A reboot sorted that out.

I have had a black, blank screen and read the thread to see that I have not been the first....! I'm not sure as yet if that it well be a common occurrence or not but is the r15 Redkernel still considered to be the preferred choice of potential fixes.? If so would I then need to change baseband to 4.4.2, for the potential brightness issue....?

The ROM seems responsive and thankfully works fine with my CCTV app, and others.

Thanks for what you have done here, and for all the other work you continue to do, as it is most appreciated.

It's normal that rotation doesn't work on first boot. The blank screen issue is indeed infamously known, but I have faith in our great developers it will get sorted out sooner or later.

Sent from my LG-V500 running CM12.1

 

[kude87]

6.11 build gets a mobile data force close upon first boot, and sticks around. Flashed again, still got it. Had to go back to 6.10.

Are the latest GPU drivers implemented, or should we keep flashing them with each build? Same with the audio policy fix? PS, thanks for both of those, btw.

Sent from my LG-V500

 

[Deltadroid]

6.11 build gets a mobile data force close upon first boot, and sticks around. Flashed again, still got it. Had to go back to 6.10.

Are the latest GPU drivers implemented, or should we keep flashing them with each build? Same with the audio policy fix? PS, thanks for both of those, btw.

Sent from my LG-V500

The latest adreno drivers and the audio policy changes are not merged into the official nightly builds yet. They need to be flashed again after updating. I'm also still testing the audio policy.

 

[meanoc]

The latest adreno drivers and the audio policy changes are not merged into the official nightly builds yet. They need to be flashed again after updating. I'm also still testing the audio policy.

Where would I find the newest Adreno drivers?

 

[Deltadroid]

Where would I find the newest Adreno drivers?

Post #168

 

[kude87]

Just reporting that builds 6.11, 6.12, and 6.13 all have the mobile data force close. Bug report sent, but 6.10 is quite nice at the moment. :thumbup:

Sent from my LG-V500

 

[olbc]

My battery is consumed in standby per day approximately 15-20%. I have reseted the tablet, but it was not successful . it was only installed CM12 and some Google apps like Play Store or Play services. I have now again the stock ROM installed (4.4.2). The standby consumption is now optimally, only 1-2% per day. However, I prefer CM12 . Does anyone have an idea?

 

[zacharias.maladroit]

You should try the kernel in permissive mode to see if it fixes the Wi-Fi problem. There is another thread about bumping the kernel in the recovery, those patches also have an option to set the kernel in permissive mode.

Is this issue fixed on this ROM and/or upstream CM12 ?

I'm currently on FlexOS which shows the same behavior, permissive might be a short-term "quickfix" solution but I'd prefer Enforcing

Thanks :good:

 

[Deltadroid]

Is this issue fixed on this ROM and/or upstream CM12 ?

I'm currently on FlexOS which shows the same behavior, permissive might be a short-term "quickfix" solution but I'd prefer Enforcing

Thanks :good:

The unofficial cm12.1 from fefifofum has it fixed,I believe.

 

[olbc]

I can´t install CM12.1 now. The error is:
no MD5 file found
Error executing updater binary in zip ... Can you help me, please?
Actual Android is 4.4.2, TWRP is 2..8.6.0

I found a solution: I installed the recovery PhilzTouch 6.48.4, made a reset and installed CM with success. Before I installed some other TWRP older Versions without success.

 

[jm1981]

Hi,

I have a question about CM nightlies and releases.
If I decide to wipe/factory reset my V500 to install a brand new CM12.1 for example.
As only nightlies are available, I think that I could update to next nightlies without wipe/factory reset.
But what about any release or Stable CM (M version ?) when I'd want to update from a nightly to release ? Will it possible without wipe/factory reset ?

Thanks !

 

[Cal]

Hi,

I have a question about CM nightlies and releases.
If I decide to wipe/factory reset my V500 to install a brand new CM12.1 for example.
As only nightlies are available, I think that I could update to next nightlies without wipe/factory reset.
But what about any release or Stable CM (M version ?) when I'd want to update from a nightly to release ? Will it possible without wipe/factory reset ?

Thanks !

NO

 

[luisbraz]

Hi,

I have a question about CM nightlies and releases.
If I decide to wipe/factory reset my V500 to install a brand new CM12.1 for example.
As only nightlies are available, I think that I could update to next nightlies without wipe/factory reset.
But what about any release or Stable CM (M version ?) when I'd want to update from a nightly to release ? Will it possible without wipe/factory reset ?

Thanks !

Yes, it is. I do that in the s4 mini. But you cannot be on the latest nightly. If you are in a nightly 1 week older than the m release you can upgrade without wipes. Every time a m release is release, in the cyanogenmod blog is announced and there you can find the information about the last nightly where is possible to flash the m version without any problem.