yashsingh1/xdaforums huggingface dataset:
[G Pad 8.3 Original Android Development] Deltadroid:
[MENTION=1077833]infected_[/MENTION] which patches for bt did you apply to fix it? I abandoned the one that removes the rules.
[G Pad 8.3 Original Android Development] mackeev:
I'm still using your patch that switches SELinux into "Permissive" mode. This is the only way to make my V500 remember passwords for bt devices.
[G Pad 8.3 Original Android Development] Deltadroid:
Yes, I've just about fixed the sepolicy so we can use enforcing again. Soon to make it official. It's fixed now in infected builds.
[G Pad 8.3 Original Android Development] mackeev:
Thank you. I'll be waiting for the fix. I'm on the official build.
[G Pad 8.3 Original Android Development] deepongi:
http://review.cyanogenmod.org/#/c/99870/

http://review.cyanogenmod.org/#/c/99862/
[G Pad 8.3 Original Android Development] Deltadroid:
Ahh 99870 is probably what fixed it. That's the one I had to abandon because they want me to fix the existing policy.

Does Bluetooth still work if you back out 99870 and just use 99660?

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

I should have waited for the results of the first patch before asking you to test the second one.
[G Pad 8.3 Original Android Development] Deltadroid:
Bluetooth sepolicy patch

I have created a flashable zip that fixes the sepolicy for the bluetooth loader instead of having to disable selinux and use permissive mode. This is a much better option than disabling selinux. After installing latest CM12.1 ROM and the bluetooth sepolicy patch, I rebooted to the system and I removed my bluetooth devices to pair them again. After pairing my bluetooth devices with the sepolicy patch applied, everything was fixed and I could restart the service and all the bluetooth devices still reconnect.

Requirement: This is only for bumped ROMS and kernels.

Note: There is no more need to use permissive mode to fix bluetooth. This bluetooth sepolicy patch needs to be reinstalled after flashing a new rom or kernel.

Instructions:

1) Flash Bumped ROM (and bumped custom kernel optionally)

2) Flash Bluetooth sepolicy patch

3) Reboot to system

v500-bluetooth-sepolicy-signed.zip

#!/sbin/sh
+
+cd /tmp
+mkdir ramdisk
+cd ramdisk
+gunzip -c ../boot.img-ramdisk.gz | cpio -i
+sed -i '/seclabel u:r:bluetooth_loader:s0/d' init.awifi.rc
+find . | cpio -o -H newc | gzip > ../boot.img-ramdisk-new.gz
+cd ..
+
echo \#!/sbin/sh > /tmp/createnewboot.sh
-echo /tmp/mkbootimg --kernel /tmp/boot.img-zImage --ramdisk /tmp/boot.img-ramdisk.gz --cmdline \"$(cat /tmp/boot.img-cmdline) androidboot.selinux=permissive selinux=0\" --base 0x$(cat /tmp/boot.img-base) --pagesize 2048 --ramdiskaddr 0x82200000 --output /tmp/newboot.img >> /tmp/createnewboot.sh
+echo /tmp/mkbootimg --kernel /tmp/boot.img-zImage --ramdisk /tmp/boot.img-ramdisk-new.gz --cmdline \"$(cat /tmp/boot.img-cmdline)\" --base 0x$(cat /tmp/boot.img-base) --pagesize 2048 --ramdiskaddr 0x82200000 --output /tmp/newboot.img >> /tmp/createnewboot.sh
chmod 777 /tmp/createnewboot.sh
/tmp/createnewboot.sh
return $?

Thanks [MENTION=4517918]jsevi83[/MENTION] for providing sepolicy patches. That was a big help.
[G Pad 8.3 Original Android Development] mackeev:
Official builds ain't bumped, are they?
[G Pad 8.3 Original Android Development] Deltadroid:
Yes, official cm12.1 is now bumped.
[G Pad 8.3 Original Android Development] olbc:
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)?
[G Pad 8.3 Original Android Development] Deltadroid:
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.
[G Pad 8.3 Original Android Development] 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/
[G Pad 8.3 Original Android Development] ThunderBolt_BR:
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...
[G Pad 8.3 Original Android Development] Deltadroid:
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.
[G Pad 8.3 Original Android Development] 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.
[G Pad 8.3 Original Android Development] Cal:
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.
[G Pad 8.3 Original Android Development] Deltadroid:
No, not yet. The fix still needs testing.
[G Pad 8.3 Original Android Development] 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.
[G Pad 8.3 Original Android Development] Deltadroid:
The backlight is not set for the 4.4.2 bootloader with stock cm kernel. That is why it was dim.
[G Pad 8.3 Original Android Development] Deltadroid:
Bluetooth is now fixed. :) no more need for any patches for sepolicy or permissive mode.
[G Pad 8.3 Original Android Development] Cal:
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??
[G Pad 8.3 Original Android Development] Deltadroid:
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.
[G Pad 8.3 Original Android Development] mackeev:
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!)
[G Pad 8.3 Original Android Development] Deltadroid:
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.
[G Pad 8.3 Original Android Development] 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.
[G Pad 8.3 Original Android Development] Deltadroid:
I found the problem and have submitted a patch.

http://review.cyanogenmod.org/#/c/100316/1
[G Pad 8.3 Original Android Development] Deltadroid:
Its merged now.. The next build should fix the problem, hopefully. ;)
[G Pad 8.3 Original Android Development] 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 [MENTION=4517918]jsevi83[/MENTION]
[G Pad 8.3 Original Android Development] davebuk:
[MENTION=5227588]Deltadroid[/MENTION] 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?
[G Pad 8.3 Original Android Development] Deltadroid:
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.
[G Pad 8.3 Original Android Development] 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.
[G Pad 8.3 Original Android Development] davebuk:
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.
[G Pad 8.3 Original Android Development] 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
[G Pad 8.3 Original Android Development] ukguy115:
Thanks for all your work lately on the gpad. Seems like this thing running as good as ever, even the little picky stuff.
[G Pad 8.3 Original Android Development] Deltadroid:
Thanks for testing. I'll check the logs on the latest build.
[G Pad 8.3 Original Android Development] Pootch:
Hello.

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

Br

Pootch

Edit: Reflashed same version > works.
[G Pad 8.3 Original Android Development] 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.
[G Pad 8.3 Original Android Development] GXGOW:
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
[G Pad 8.3 Original Android Development] 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
[G Pad 8.3 Original Android Development] Deltadroid:
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.
[G Pad 8.3 Original Android Development] meanoc:
Where would I find the newest Adreno drivers?
[G Pad 8.3 Original Android Development] Deltadroid:
Post #168 :)
[G Pad 8.3 Original Android Development] 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
[G Pad 8.3 Original Android Development] 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?
[G Pad 8.3 Original Android Development] zacharias.maladroit:
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:
[G Pad 8.3 Original Android Development] Deltadroid:
The unofficial cm12.1 from fefifofum has it fixed,I believe.
[G Pad 8.3 Original Android Development] 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.
[G Pad 8.3 Original Android Development] 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 !
[G Pad 8.3 Original Android Development] Cal:
NO
[G Pad 8.3 Original Android Development] luisbraz:
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.
[G Pad 8.3 Original Android Development] testman86:
[MENTION=5227588]Deltadroid[/MENTION] do you have any news about solving black-screen issue in original CM12 or is it still needed to flash ricks kernel? Or do you find the source of the issue? I see that daily nightlies are coming, but still waiting for the day to have a daily driver after few months again :)
[G Pad 8.3 Original Android Development] Deltadroid:
The black screen is caused by the new color calibration method added to the kernel and ROM in cm12.1.

You can use specific versions red kernel to fix the black screen, but the rom also needs to be changed to use the previous color calibration method.

I have been testing [MENTION=4517918]fefifofum[/MENTION]'s unofficial cm12.1 build and there are no problems with the black screen.

I would also really like to see that fixed in the official build.
[G Pad 8.3 Original Android Development] takis:
Why are there no new builds?
[G Pad 8.3 Original Android Development] Tqpolo:
I don't have a black screen issue (not sure). Does this video blobs file fix watching video or youtube at 720p or higher? Mine freezes at anything higher than 720p.
[G Pad 8.3 Original Android Development] Deltadroid:
The updated video blobs do not fix the black screen problem. I do not think these updated video blobs will fix the problem you are describing with watching video or youtube at 720p or higher.

Edit: There were some recent changes to livedisplay that could potentially fix the black screen issue for the official builds. Can anyone verify if the latest nightly build fixes the black screen issue?
[G Pad 8.3 Original Android Development] Tqpolo:
Is there a known issue for playing videos in full HD?
[G Pad 8.3 Original Android Development] Deltadroid:
not that I'm aware of. It may depend on the encoding and if you use hardware or software decoding.
[G Pad 8.3 Original Android Development] davebuk:
Its all gone a bit quiet on this thread. Are people playing with a different ROM? Im not having any issues with official CM12.1 but don't want to be missing out :)

[MENTION=5227588]Deltadroid[/MENTION] do you know what happened with the bluetooth connection issue that this ROM has?
[G Pad 8.3 Original Android Development] Deltadroid:
The Bluetooth connection issue with official cm12.1 is related to selinux policy blocking the device. I've fixed some rules, but there could still be some denials with specific Bluetooth devices.

I think many people are testing [MENTION=4517918]fefifofum[/MENTION]'s sources because he reorganized the v500 repos and fixed many of the problems still found in the official sources.

We have been working together to get things fixed and merged into the official sources, but the review process is very slow sometimes. Right now, we are waiting for the kitkat backlight settings to be merged to official sources so we can update the bootloader with the official cm12.1 rom.
[G Pad 8.3 Original Android Development] Cal:
Just grab the latest by Fefifofum (unofficial) CM12.1) and you will not be disappointed. That is the very best I've very used. Solid of stability, battery, and all else. Simply great IMO. :)
[G Pad 8.3 Original Android Development] davebuk:
I might have a look into fefifofum at some point. My Bluetooth headset still has issues but i just power it up in pairing mode and re-pair when i want to use the. That way i leave selinux as enforcing.
[G Pad 8.3 Original Android Development] davebuk:
Well I've gone over to fefifofum. See you over there! ;)
[G Pad 8.3 Original Android Development] Ultraman1966:
Flashed the latest 2407 and just encountered the black screen issue, shall I dirty flash back to earlier versions?
[G Pad 8.3 Original Android Development] ol31:
No more black screen issue with [MENTION=4517918]fefifofum[/MENTION] build.
[G Pad 8.3 Original Android Development] sabamimi:
+1
[G Pad 8.3 Original Android Development] Deltadroid:
Kitkat Bootloader

The next official CM12.1 build will require users to update to the Kitkat bootloader.

Thanks [MENTION=4517918]fefifofum[/MENTION] for getting the necessary backlight settings merged.

Here is a link provided by [MENTION=4517918]fefifofum[/MENTION] for a flashable zip to update the bootloader to kitkat.
[G Pad 8.3 Original Android Development] dbux:
I had black screen issues with the latest build but not too often. So is this .zip file(LINK: https://www.androidfilehost.com/?fid=23991606952612021) that has to be flashed? Sorry for troubling you by asking, I saw a post of somebody once that this could be due to gapps, that's why got confused. I will also flash the .zip file quoted in this post for the backlight also. Is there any wipe needed?

Also please look into this issue http://xdaforums.com/showpost.php?p=62314465&postcount=94
[G Pad 8.3 Original Android Development] Deltadroid:
The updated adrino video drivers probably will not solve the black screen issue. The best solution for fixing the black screen is to use the unofficial cm12.1 build from fefifofum. Maybe your audio volume issue will also be fixed with the other ROM from fefifofum.

When updating the bootloader to kitkat, there is no wiping necessary. Flash the bootloader zip in recovery and that is it.
[G Pad 8.3 Original Android Development] jamarita:
Hi , I upgrade today from CM12 to cm 12.1 , everything is fine no problem after instal new gapps, only I have problem with the bluetooth smart connection with mi heart rate monitor Polar H7 , the Gpad doesn´t recognize the bluetooth strap now.

Thanks
[G Pad 8.3 Original Android Development] Deltadroid:
Selinux is probably blocking something. You can try setting the kernel to permissive mode.

https://www.androidfilehost.com/?fid=95916177934554765
[G Pad 8.3 Original Android Development] jesuita:
This topic is pretty quiet now, does that mean we should move to fefifofum build?
[G Pad 8.3 Original Android Development] juniorhxcx:
My Gpad has a problem disconnecting MicroSd, using the Korean ROM 5.0.2. This Rom have this problem too?

Enviado de meu C6503 usando Tapatalk
[G Pad 8.3 Original Android Development] fefifofum:
I submitted some commits to fix the black screen issue and the random reboots. Not that I recommend official builds over mine, but it was something that had to be done.

https://github.com/CyanogenMod/android_device_lge_v500/commits/cm-12.1

https://github.com/CyanogenMod/android_kernel_lge_v500/commits/cm-12.1
[G Pad 8.3 Original Android Development] Deltadroid:
Just pressing the like button was not enough for me. Thank you, [MENTION=4517918]fefifofum[/MENTION] for all the work you do and the contributions you have made for our v500's.
[G Pad 8.3 Original Android Development] neodraig:
I can't connect to the wifi with this ROM.

I tried both the snapshot and the last nightly (wiped and formated everything) and even though my home network is detected and I can enter my password, I can't connect to it :(

Didn't have that problem with the stock ROM.
[G Pad 8.3 Original Android Development] fefifofum:
I fixed moving apps to sdcard in official builds, in case anyone is interested:

https://github.com/CyanogenMod/andr...mmit/d76ffbc775e2ae62a5ebd6a745a067f26b88e417
[G Pad 8.3 Original Android Development] darkvoid_66:
The Bluetooth works fine for me but when I create a new user, that user cannot enable Bluetooth.

Anyone know why?
[G Pad 8.3 Original Android Development] RoadBicyclist:
Does anyone know if today's new CM12.1 release, 2015-10-07, fixes anything like the black screen?

Anyway, I'm about to do fefifofum fixes, BTW, you're the man!

---------- Post added at 08:27 PM ---------- Previous post was at 08:25 PM ----------

Pre-apologies for the stupid question, getting back into rooting/ROMs after years of not doing this, is like re-learning what you already know, but forgot... I know, no comment!!!

Do these just need to be flashed in recovery?
[G Pad 8.3 Original Android Development] Deltadroid:
All of the fixes mentioned above are now merged into the latest official nightly build.
[G Pad 8.3 Original Android Development] RoadBicyclist:
OK excellent, since I don't want nightly, the latest release will have these fixes too, right?

Also, can I flash over without wiping or should I wipe? Also, if wipe, what should I wipe, everything?

Thanks, I feel like a newbie asking all these questions!!! :D
[G Pad 8.3 Original Android Development] Deltadroid:
Only the latest nightly build contains the latest fixes.

I recommend a factory reset for first time installation.
[G Pad 8.3 Original Android Development] Icefluffy:
can i install this CM version from stock rooted 4.4.2?
[G Pad 8.3 Original Android Development] Deltadroid:
Since you are already on kitkat, you will not need to change the bootloader. CM12.1 for v500 uses the kitkat bootloader.

Just make sure you factory reset and use the latest version of TWRP for your recovery.
[G Pad 8.3 Original Android Development] Icefluffy:
whats the diference between twrp and CM recovery? i have twrp installed and was about to download yesterday's nightly to install but i saw the recovery download and become confused :cowboy:
[G Pad 8.3 Original Android Development] Deltadroid:
The cm recovery is a very bare bones version of ClockworkMod and it is used mostly by developers. The cm recovery is not recommended because it will only work with properly signed packages and it can not be disabled.

I recommend using the latest official twrp.
[G Pad 8.3 Original Android Development] Icefluffy:
thanks mate, by the name i thought it was something for developers but i rather ask then ending up with a paperweight i don't need :laugh: