yashsingh1/xdaforums huggingface dataset:
[G Pad 8.3 Android Development] Deltadroid:
CyanogenMod 12 (CM 12)

Android 5.0.x for LG G Pad 8.3 V500​

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.

#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/

About CM:

CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

Wiki:

Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/w/V500_Info

Important Information:

Be sure you are using latest available recovery!

Download:

http://download.cyanogenmod.org/?device=v500

Installation:

Read the official wiki

Copy GApps and CM12.0 ZIPs to your internal SDCard

Boot into Recovery

wipe data factory reset

wipe cache

wipe dalvic cache

format system

Flash CM12.0 zip from internal SDCard

Flash GApps zip from internal SDCard

Reboot

Don't restore system data using Titanium Backup!

Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!

Upgrading from earlier version of CyanogenMod 12.0:

Copy CM12.0 ZIP to your internal SDCard

Boot into Recovery

Flash CM12.0 zip from internal SDCard

Reboot

Important Information for kangers:

If you're going to reuse our work, which we're doing for free, be fair and give proper credits.

This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.

Used sources:

https://github.com/cyanogenmod

XDA:DevDB Information:

CM 12.0 ROM for the LG G Pad 8.3 (V500)

Contributors:

CyanogenMod Team

ROM OS Version: 5.0.x Lollipop

ROM Kernel: Linux 3.4.0

Version Information

Status: Testing
[G Pad 8.3 Android Development] Deltadroid:
Reserved for additional information.
[G Pad 8.3 Android Development] Deltadroid:
While we wait for patches to be merged, I have patched framework-res.apk from the 20150210 nightly build to enable the missing navigation bar menu. The zip file below can be flashed on top of the latest cm12 nightly build to enable the missing navigation bar menu.

EDIT: Patch removed because the fix is now successfully merged into 20150212 nightly build.

Note: the contents of framework-res.apk does not change very often, but I will update this link when necessary (until it is fixed in the official sources).

--- framework-res.orig/res/values/integers.xml	2015-02-08 15:28:49.828484209 +0100
+++ framework-res/res/values/integers.xml	2015-02-08 15:29:05.556484196 +0100
@@ -77,7 +77,7 @@
<integer name="config_longPressOnHomeBehavior">2</integer>
<integer name="config_doubleTapOnHomeBehavior">0</integer>
<integer name="config_longPressOnMenuBehavior">3</integer>
- <integer name="config_deviceHardwareKeys">0</integer>
+ <integer name="config_deviceHardwareKeys">64</integer>
<integer name="config_deviceHardwareWakeKeys">79</integer>
<integer name="config_screenBrightnessSettingMinimum">10</integer>
<integer name="config_screenBrightnessSettingMaximum">255</integer>
[G Pad 8.3 Android Development] 55Pegasus:
Thanks for the Official thread, have not had any major problems but it's nice to see.
[G Pad 8.3 Android Development] Deltadroid:
I created this thread because there was no proper place to post for the current status of the official nightly cm12 builds for v500. We don't want to use the cm11 thread for cm12.
[G Pad 8.3 Android Development] 55Pegasus:
The only issue I've have is with the SD card. It will not allow apps to move to it and sometimes it becomes unmountable until I reboot.
[G Pad 8.3 Android Development] Deltadroid:
Problems with moving apps to the sdcard could caused by SuperSU. Try disabling "mount namespace separation" in the SuperSU settings, if you are using SuperSU.
[G Pad 8.3 Android Development] 55Pegasus:
I'll give it a try. Thanks.
[G Pad 8.3 Android Development] Stransky:
Only problem I have is "SD Card removed unexpectedly". Using an alternative Kernal (Redkernal 14 or mani) cures this but it has to be reinstalled after every update. Any chance this problem can be cured without having to change kernals. Also CM updater is not working , downloads OK but tab reboots instead of going into recovery. CyanDelta works so I use this.

Stransky
[G Pad 8.3 Android Development] Deltadroid:
I think we need to gather more info on which sdcards are causing the problem and maybe we can find something in common between them.

Card info needed: brand, size, type of file system, firmware base.
[G Pad 8.3 Android Development] Stransky:
Mine: Sandisk 64GB XC fat32 Ext4

Stransky
[G Pad 8.3 Android Development] Deltadroid:
I'm using a Verbatim Premium Class 10 UHS-I MicroSDXC Card 64GB with 4.2.2 firmware base and I have never had problems with the stock kernel causing unmounts. How do you know the card is unmounting? Is there a message that pops up?
[G Pad 8.3 Android Development] Stransky:
Yes message as inside quotes on my previous msg. I am on 4.4.2 base. This has been happening ever since 20150115 nightly. Never had problem on CM 11 nightlies.

Stransky
[G Pad 8.3 Android Development] Deltadroid:
The unmount problem on stock cm12 could be related to the ext4 partition on your sdcard. Ext4 is not an officially supported sdcard format, so there is probably very little testing with the sdcard drivers going on. At least, if I were to try and guess.

I suggest a single fat32 partition.
[G Pad 8.3 Android Development] Deltadroid:
I have updated the Navigation Bar Patch on post #3 for todays build on 20150210. Usually, framework-res.apk does not change very often, but I will keep the link in post #3 updated when necessary (until it is fixed in the official sources).
[G Pad 8.3 Android Development] Stransky:
I have reformatted my SD card as fat32 and it still gives the message "SD card unexpectedly removed" after each update. I also have a Galaxy S4 which is running Lollipop 5.0.2 and an ext 4 32GB Sandisk Ultra SD card and it does not dismount or remove itself. Only problem I have with the S4 is have to do updates manually because neither CWM or CyanDelta will run them automatically.

Stransky?
[G Pad 8.3 Android Development] Deltadroid:
The "missing navigation bar menu" patch is now successfully merged into the cm12 sources. Tomorrow's build (20150212) will be fixed and I will then remove the temp patch I posted.

Special thanks to [MENTION=1077833]infected_[/MENTION] and [MENTION=3265523]slebit[/MENTION] for the info and support.
[G Pad 8.3 Android Development] DonDizzurp:
[MENTION=5227588]Deltadroid[/MENTION] I just want to personally thank you for keeping our tablet alive.

It's an excellent piece of hardware that still has strong specs even to today's standards. It doesn't seem to get much love. Most people went with a Samsung I'm guessing.

Thanks for keeping our overlooked and under-appreciated device breathing with the latest software!
[G Pad 8.3 Android Development] Deltadroid:
I just didn't like Samsung's big ugly physical button. :)
[G Pad 8.3 Android Development] michd2:
I just didn't like the lack of decent materials and buildquality on Samsung's tablet ?
[G Pad 8.3 Android Development] GXGOW:
Well , good thing I hadn't installed the latest nightly yet.

Sent from my LG-V500 running CM12
[G Pad 8.3 Android Development] davebuk:
I ran the 'fix permissions' option from TWRP to see if that would help. I wonder if that caused my issue. It's was like the internal memory had become corrupted and the ROM just wouldn't boot correctly. Anyway, currently working (20150318) and hoping [MENTION=5227588]Deltadroid[/MENTION] can help get the CM team to try and fix the bluetooth issue. ?
[G Pad 8.3 Android Development] Deltadroid:
What we should do next is compare our Bluetooth selinux policy in our device tree with another device tree that is confirmed working.
[G Pad 8.3 Android Development] davebuk:
Bluetooth on my nexus 5 running 5.1 is fine?
[G Pad 8.3 Android Development] nigelhealy:
So I had CM11, I booted into recovery mode, then flashed CM12 March 20th, gapps, and I have the settings crash bug.

I can't now get into recovery. I can't enable usb debugging to issue adb commands and I've tried the hardware buttons method (off, vol down + power, release power, press power vol down vol up) and it doesn't go into recovery it just boots.

Ideas how to get into recovery? I don't have root, can't enable usb debugging.....
[G Pad 8.3 Android Development] Deltadroid:
Make sure you have the usb cable disconnected before trying the button method. It should work.
[G Pad 8.3 Android Development] nigelhealy:
Phew, yep cable unplugged it worked. Thanks. Installing CM March 19th now,,,,
[G Pad 8.3 Android Development] Vegasden:
Tried this. Settings kept crashing.
[G Pad 8.3 Android Development] Deltadroid:
20150320 build has a bug. 20150319 works.

I was about to try 20140322 to see if it fixes the problem. Anyone else try today's build yet?
[G Pad 8.3 Android Development] Deltadroid:
The 20150322 build is working again. It should be safe to update now. :)

I love the new changes to the settings menu now.
[G Pad 8.3 Android Development] dabizb:
Hello. I have this rom installed and is fantastic , but is beginning to be unusable . For some time it closes the background processes continuously . Closes ftp transfers, or google chrome, or pockectcast play, or another apps. Someone with the same problem ?. Any solution . Thanks in advance.

Enviado desde mi LG-V500 mediante Tapatalk
[G Pad 8.3 Android Development] Deltadroid:
Have you tried testing with red kernel or mani kernel? The problems you mention seem memory related. Although, I'm not experiencing these symptoms with stock cm12.
[G Pad 8.3 Android Development] GXGOW:
I only experience this after an uptime of about 48 hours, but a simple reboot fixes this for me. It's probably the infamous memory leak, which I also had on my S3 Mini on 5.0.2. The 5.1 fixed it, luckily.

Did you try to reboot your device?

Sent from my LG-V500 running CM12
[G Pad 8.3 Android Development] dabizb:
Yes, but after a short time ir begins again.

Enviado desde mi Nexus 4 mediante Tapatalk
[G Pad 8.3 Android Development] mackeev:
0322 nightly no good either: screen went black on me after just 3 min of flash streaming in FF. 0318 looks more stable (I've had this blank screen problem on earlier nightlies).

And I have one more thing... I don't know why no one's complaining. I've had it since day one (or rather since mid-January):

I can't load owner's picture into the blue circle in Profile info. Neither Choose photo from Gallery nor Take photo is working for me. When I choose a photo from the gallery and tap Save, nothing happens. When I take a photo with either camera and tap the check mark, I get a message Can't load the image.

I flashed AOSP 5.1 (and 5.02 earlier, just for the hack of it), and it worked fine in there. Something is broken in CM12. Am I the only one with this issue?
[G Pad 8.3 Android Development] Deltadroid:
In earlier releases, I also had the problem you mentioned with not being able to load a picture into the owners profile. I was able to successfully choose the picture I wanted using the Contacts application. It might also depend on which helper application you use to select the photo. Also, clearing the data in Contacts Storage should reset the Contacts application, if the program gets stuck.
[G Pad 8.3 Android Development] Deltadroid:
You may want to also try just replacing the stock launcher with Google's launcher. I have read several reports that this also helps with the memory problems. I have supplied a gapps add-on that will replace the stock launcher with Google's version. It might be worth testing that.

That might be the reason why I'm not experiencing this issue.
[G Pad 8.3 Android Development] mackeev:
Thanks a lot for your advice. Picture via Contacts app worked perfectly. You've made my day (another one, actually). Earlier, I used your usb-otg-option patch to retrieve flashstick recognition in recovery.
[G Pad 8.3 Android Development] Deltadroid:
I'm trying to look into the cause of our paired Bluetooth devices not reconnecting after restarting the Bluetooth service.

If anyone wants to help, I need some logs of /data/misc/audit/audit.log

First test, pair Bluetooth headset device, restart Bluetooth service, try to connect Bluetooth headset.

Unpair Bluetooth devices.

Second test, set tablet in permissive mode, pair Bluetooth headset device, restart Bluetooth service, try to connect Bluetooth headset.

To set permissive mode:

su
setenforce 0

Finally, attach log here in thread of both tests.
[G Pad 8.3 Android Development] davebuk:
Please find attached 3 logs explained in their filenames. They all have the same file date of 01/06/1971 when in their audit folder if that points to anything?
[G Pad 8.3 Android Development] Deltadroid:
Thanks. This will help.
[G Pad 8.3 Android Development] Deltadroid:
Hmm, I'm trying to find audit denials in the logs, but I don't see it yet. Maybe there would be more info in a logcat or dmesg. I'll keep looking.
[G Pad 8.3 Android Development] Cal:
@ Mr. Deltadroid...

For the life of me, I can't understand why you are posting these regular Cyanmod Roms when they can be found elsewhere fairly easy, and so can the change-logs.

Do you not agree that the same nightly by Infected is a bit smoother, and perhaps faster, after installing?

Just curious, and no disrespect is meant toward you. I consider you exceptional in your abilities, and generosity to make things better, and easier, for upgrating LG Tab 8.3. You've been putting out excellent other items.

Please clarify for me please your motives for posting these Roms, which are the same in format as are Infecteds. That is all I request, and thank you very much for your extremely hard work.

Cal
[G Pad 8.3 Android Development] Deltadroid:
Well, I'm not actually posting any roms in this thread. All the roms mentioned in the op are built automatically each night by a central server. This thread is about the current state of the official cm source.
[G Pad 8.3 Android Development] annoyingduck:
Huh? Really? You should read up first. There's no cm12 thread for us because the original maintainer has been occupied, along with the official cm11 thread in original development being long abandoned. [MENTION=5227588]Deltadroid[/MENTION] has kindly created this thread for discussion and bug reporting and has been swarn in as our official maintainer. Oh and this tiny detail: he is submitting bug patches for us!!

If you want your cm builds broken (including the infected builds that use the official builds), by all means tell Deltadroid to go pound sand and petition to have this thread closed.

The uselessness of this post amazes me.... Including my need for a response. Wow.
[G Pad 8.3 Android Development] testman86:
I still have this black screen problem 25th build. After a while, or in this case after 4 min of using, screen gets black again and on/off-button does not awake it anymore. Just touch seems to work and I can hear lock und unlock noise... Didn't my last logs help? What would you need to figure out where the problem might be? :)
[G Pad 8.3 Android Development] Deltadroid:
What version bootloader are you using?

Edit: it seems the bug could also be related to enabling adaptive brightness. Does disabling automatic brightness fix it?
[G Pad 8.3 Android Development] Deltadroid:
[MENTION=4558034]testman86[/MENTION]

Are you watching video before the crash? I'm seeing errors about adaptive playback also. I wonder what happens if you disable adaptive playback in the video driver. I posted a patch in this thread somewhere that disables adaptive playback, for testing purposes.

Patch to disable adaptive playback is on post #64
[G Pad 8.3 Android Development] testman86:
thanks for fast reply! As we were talking here, http://xdaforums.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472/page8 starting with post 77, I was on latest OTA and then flashed 4.2.2 base as you mentioned there and took the .zip you were referring to. And I use TWRP 2.8.5.0 so latest one to be compatible to CM12. Maybe you remember that I was asking in detail to avoid issues ^^ But that does not seem to help. :) I will try to use static brightness and not adaptive and will give feedback. Before crash I was not watching videos, I was using Netflix on Chromecast, but I also had this crash when I was changing some settings in google settings after a fresh install.
[G Pad 8.3 Android Development] Deltadroid:
Ahh.. yes. That is why I see the adaptive video playback errors. When viewing videos on Youtube and Netflix, there is a proprietary adaptive video playback feature that will allow the server to select higher quality video. The problem with that adaptive video playback feature seems to be that sometimes the selected video quality is too high and it forces the video to be rendered by software drivers instead of hardware playback. I'm not sure if that is the problem with the video driver crashing, but it might be worth testing with that adaptive video playback feature disabled from the patch I posted.

Edit:

If none of the suggestions help, you could also try updating your bootloader to 4.4.2 and test Mani or Red Kernel. That would definitely make a difference testing with the newer video drivers.
[G Pad 8.3 Android Development] Cal:
@ annoyingduck...

That you say "there in NO CM12 thread for us" is why I asked Mr. Deltadroid why duplicate as I didn't understand why he does not use Infected's nightlys (optimized, but code remaining the same), to correct bugs. I know that Infected's thread is not acted on by correction, but there are many useful posts to Infected's thread that both he and Deltandroid discussed regarding the problems. If 'you' read Infected's OP of his optimized CM12s, you will see this:

"Disclaimer:

These builds are freshly compiled/synced from CyanogenMod Rom open-source code:

https://github.com/CyanogenMod

Special Thanks

CyanogenMod Dev Team = for the code sources."​

That was why I asked Mr. Deltadroid my question. He answered with courtesy and an explanation. I was not being sarcastic in my question to Mr. Deltadroid and I fully appreciate him ironing out the bugs and if he finds a new bug which slips by the CM techs...he lets them know and they seem to pay a lot of attention to him and make modifications. Obviously the techs at CM respect Mr. Deltandriod, just as I do, and his abilities.

Best regards annoyingduck, and I hopes this answers why I posted what I did.

Cal
[G Pad 8.3 Android Development] annoyingduck:
I actually should apologize for the harshness of my response, it was unwarranted. I misread the tone of the original post. It's all good, thanks for the clarification, and you handled it like a gentleman.
[G Pad 8.3 Android Development] Anthrax_OC:
Is adaptive brightness working on this ROM at all? I'm currently on the 20150319 nightly and I can't get it to work. I also had the dark screen issue a few times but I believe it was only in the 20150320 nightly.

I'm on the 4.2.2 base.

At the moment, what is the latest "stable" nightly without any major issues?
[G Pad 8.3 Android Development] testman86:
I am on 25th nightly and still have the dark screen issue if disabling adaptive screen brightness. Maybe I will test some other Kernel or infected's Nightly but I am tired of not be able to use the tablet properly and doing every two days a compelte fresh install and set-up everything and every programm...
[G Pad 8.3 Android Development] Deltadroid:
I think testing out red or mani kernel with the 4.4.2 bootloader would give best chance at fixing it.
[G Pad 8.3 Android Development] Deltadroid:
At the moment, the latest stable is the current nightly build. I haven't tested adaptive brightness very much, but it seems to work as expected.
[G Pad 8.3 Android Development] Deltadroid:
20150330 should have some Bluetooth patches that could potentially fix this issue. I can't verify yet, but it's worth testing.

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

Edit: I just tested and it's still not connecting after rebooting. I think we just need to wait for cm12.1 to fix this. Apparently, this bug is already fixed in aosp 5.1.
[G Pad 8.3 Android Development] mackeev:
Thank you. It is good to know it'll be fixed eventually.

I have one more question, though: is it possible to have a patch for ethernet connectivity? I believe it is disabled in cm12, at least my attempts at connecting to the internet via a Plugable ethernet adapter have failed so far.
[G Pad 8.3 Android Development] Deltadroid:
The CyanogenMod blog states that cm12.1 nightlies should start rolling out next week. There are going to be lots of changes in cm12.1, so maybe that Ethernet issue will be fixed as well. If there are regressions in the nightly builds, the cm team has also mentioned that they still be accepting bug reports on jira for the nightly builds now.

http://www.cyanogenmod.org/blog/all-about-l-part-1
[G Pad 8.3 Android Development] ThunderBolt_BR:
Finally it's time to learn how to post a report on jira ;)

[]'s
[G Pad 8.3 Android Development] RobaL4:
Hi, I agree on that.

The only thing that work's for me is first to get your device connected with trying over and over again.

Afterwards the device is saved and should be ready to connect every time you turn on bluetooth. The trick is now to turn on bluethooth, turn your device into pairing mode and click connect. The tablet will then pair device once again and it works.

This is not how bluetooth is intended to work but it's a way to get a connection. Still believe and hope this will be fixed in the near future.
[G Pad 8.3 Android Development] Deltadroid:
Microsoft bought up cyanogenmod.
[G Pad 8.3 Android Development] galaxys:
^LOL, April 1st! :D