yashsingh1/xdaforums huggingface dataset:
[G Pad 8.3 Original Android Development] ronche2000:
finally!!! downloading now

---------- Post added at 04:19 AM ---------- Previous post was at 04:15 AM ----------

it is compatible with gamma kernel?
[G Pad 8.3 Original Android Development] dark0shark:
Installed and runs very smooth. Thanks a lot! (Just date in Build is not localized, so what? ?)
[G Pad 8.3 Original Android Development] mackeev:
Dirty-flashed coming from 1225 (last CM) - root is gone!

Please confirm... or is it just me?
[G Pad 8.3 Original Android Development] wizzardsk:
Thank you very much, fefifofum!
[G Pad 8.3 Original Android Development] xelyt:
I can confirm this, dirty flashed rom and delta gapps and now root is gone. I can allow it only for ADB but not for Apps. Is there a way to get root back?

EDIT: i've done a clean install and it doesn't fix the issue so for now it's better off not to install if you need root
[G Pad 8.3 Original Android Development] fluxxis:
As always thank you very much for your hard + good work! Will try the new build immediately.
[G Pad 8.3 Original Android Development] mackeev:
This is exactly what I got!
[G Pad 8.3 Original Android Development] 1eStar:
Ditto. Lost root access for apps. Fortunately I did a full nandroid backup yesterday so am once again back up and running the last version of CM14.1
[G Pad 8.3 Original Android Development] paulomodesto:
Well, since with this first release of LAOS there is a bug of lost root, I will stay with CM until this were fixed.
[G Pad 8.3 Original Android Development] Deltadroid:
SU is now disabled by default. A separate addon will be provided to enable root apparently. This is a work around for safetynet.

Another way to fix this is to export an environment variable during compile time:

# Enable SU by default

export WITH_SU=true
[G Pad 8.3 Original Android Development] GXGOW:
I didn't even notice root was disabled, probably because I'm using Magisk + phh's superuser. That combo is still working without issues. Don't know about SuperSU though.
[G Pad 8.3 Original Android Development] hodgestl:
Please read in the OP. To quote...

Important information:

The following is NOT SUPPORTED: custom kernels, xposed, mods, supersu. Do not report bugs if you use any of those.
[G Pad 8.3 Original Android Development] wizzardsk:
Will be there some OTA update support?
[G Pad 8.3 Original Android Development] fefifofum:
New build released

with root access enabled again in dev options. We'll probably get weekly official builds soon (but not before next week).
[G Pad 8.3 Original Android Development] 1eStar:
Root access for apps is now working again. Thanks.

It is same build date and file name but if you download new ROM file with MD5 = 037dcbf9fb2974b650b237c68a26bce4 then reflash (plus gapps) your root (ADB and apps)is now enabled.

Enjoy!

The vanilla android boot animation is very nice too, not considered a bug by me!
[G Pad 8.3 Original Android Development] mackeev:
Agreed.
[G Pad 8.3 Original Android Development] dark0shark:
Today's build works great. Like to recommend Lineage Downloader app to follow changes and download image: https://play.google.com/store/apps/details?id=com.paolinoalessandro.cmromdownloader
[G Pad 8.3 Original Android Development] paulomodesto:
I tried to OTA but at the end of the download it gives an error.
[G Pad 8.3 Original Android Development] giovaorama:
I have a problem with Google Contacts (from gapps) that force close. Anyone has this problem?

Anyway I'd like to format system and flash rom and gapps again but I can't guess where the updater store the downloaded nightlies.

Inviato dal mio LG-V500 utilizzando Tapatalk
[G Pad 8.3 Original Android Development] fefifofum:
I don't know where that value is stored or how to check it differently. I'll try to find out more about it.

Stock setup wizard force closes, and gapps replaces it with its own. I think it's a known bug, and most users use gapps anyway.

They are in /data/data/org.lineageos.updater/app_updates. I guess the management of ota update packages will be improved, so the user can manually delete old builds (or at least easily know where they are).
[G Pad 8.3 Original Android Development] tikkalamt:
Hello,

I have a problem to flash the latest nightly. I'm on the Jan 16th build and I couldn't flash the Feb 8 nightly. The error was 'incompatible data'. Now I have a doubt that I'm running a wrong rom; it's called 14.1-20170116-UNOFFIAL.

Have I really flashed a "wrong" ROM?

Thanks!
[G Pad 8.3 Original Android Development] fishears:
You should flash the experimental build of lineage, boot it, reboot then flash the latest nightly
[G Pad 8.3 Original Android Development] tikkalamt:
Thanks, that did the trick!! ??
[G Pad 8.3 Original Android Development] ronche2000:
everytime have update in the future you need to flash gapps and root or rom only? im using latest update
[G Pad 8.3 Original Android Development] nsmart:
For future updates you only need to flash rom.zip. Wipe caches is recommended. No need to reflash gapps or root.
[G Pad 8.3 Original Android Development] paulomodesto:
Your OTA downloads without problems?
[G Pad 8.3 Original Android Development] fishears:
I don't know about caches, I just let it update automatically & I don't think that wipes cache.

Yes, haven't had any problems with download or flashing
[G Pad 8.3 Original Android Development] Deltadroid:
When downloading updates with the new Updater application, sometimes the downloads fail to install. But, I've noticed that if I start to download an ota update from the Updater then go to recent applications and clear all running processes, the ota update will not fail and finish successfully.
[G Pad 8.3 Original Android Development] giovaorama:
[MENTION=5227588]Deltadroid[/MENTION], since use this rom and maintain the gapps package, do you also have problem with the Google contacts addon?

I also made a wipe but it always force close. Does it depends in something that i forgot to install?

Inviato dal mio LG-V500 utilizzando Tapatalk
[G Pad 8.3 Original Android Development] Deltadroid:
There is probably an issue with replacing Contacts on Lineage if a factory reset does not fix it. You may only be able to replace Contacts if the system has not yet booted up for the first time. I have not personally tried replacing Contacts with the new Lineage builds.

---------- Post added at 11:25 PM ---------- Previous post was at 11:23 PM ----------

[MENTION=4517918]fefifofum[/MENTION]

Some devices do not set QCOM_BSP_LEGACY flag (v500 for example), and this is not supported with legacy media HAL, and causes things like screen recording to fail when setting up the encoder. A crude fix for Screen Recorder for v500 is this:

Date: Fri Feb 10 21:49:45 2017 +0100

stagefright: omx: Never signal dataspace change on legacy QCOM

QCOM_BSP_LEGACY is not defined for Flo and v500

Change-Id: I75af3875b38e70f6699f82646e559b7bfe964ddb

diff --git a/media/libstagefright/omx/GraphicBufferSource.cpp b/media/libstagefright/omx/GraphicBufferSource.cpp
index d9ffca4..6d5400a 100644
--- a/media/libstagefright/omx/GraphicBufferSource.cpp
+++ b/media/libstagefright/omx/GraphicBufferSource.cpp
@@ -568,7 +568,7 @@ void GraphicBufferSource::onDataSpaceChanged_l(
aspects.mTransfer, asString(aspects.mTransfer),
err, asString(err));

-#ifndef QCOM_BSP_LEGACY
+#if 0
// signal client that the dataspace has changed; this will update the output format
// TODO: we should tie this to an output buffer somehow, and signal the change
// just before the output buffer is returned to the client, but there are many
[G Pad 8.3 Original Android Development] ralxx:
Dear all. First of all thanks for the great work.

I am writing you as I have Wifi issues after upgrading the latest nightly (20170208).

When I initially installed the 20170201-nightly (with latest opengapps), the system run smoothly and everything was perfect. After flashing to the latest version my V500 does not connect to wireless network anymore. Even after a comlete reinstall of the initial 20170201, the Wifi is not working.

Typically, first all 5Mhz wifi networks are shown, 30 seconds later the 2.4Mhz wifi networks sourrounding me. I can connect to my network, but after just a few secs the connection is cut. No internet, no play store, nothing possible - even with the 20170201-nightly. This is not logic, I am aware, but does anyone have a suggestion what to do?
[G Pad 8.3 Original Android Development] dilacerated:
GPE/V510?

Afternoon all. I am considering getting off the Nook HD+'s I've got in use throughout my family and am looking at the LG G Pad 8.3. Unfortunately I am finding a lot more GPE/V510's out there than V500's. From what I have read the GPE/V510 is only different at the ROM level (no LG tweaking). That being said is this ROM able to be flashed on the GPE/V510 or am I missing something?
[G Pad 8.3 Original Android Development] fishears:
They are different and Roms are not compatible between the two devices.
[G Pad 8.3 Original Android Development] dilacerated:
OK --> thanks for the confirmation.
[G Pad 8.3 Original Android Development] LGFr....:
Any chance to get Viper Audio working? I always get i\o error at driver Installation...?

Supersu and busybox is installed...
[G Pad 8.3 Original Android Development] papa-nundo:
This was a great tip that saved me. I followed the official instructions to get from CM14.1 to Lineage OS 14.1 and got stuck with "Secure booting Error! Cause : boot certification verify".
[G Pad 8.3 Original Android Development] Calibaan:
Wiki refers to "Extract proprietary blobs". Since the build guides are generic it is not really clear if this is really needed for this device. So must the extraction via "extract-files.sh" script be done for the V500? :confused:
[G Pad 8.3 Original Android Development] LGFr....:
No one? No ideas?
[G Pad 8.3 Original Android Development] Disrupthor:
Magisk + Viper module.
[G Pad 8.3 Original Android Development] fefifofum:
Recovery won't allow you to install it, they have different codenames and the assert in update-script is only for V500/awifi. Anyway, they are very very similar, if some dev had V510 he could use V500 repos to port Lineage to V510 easily. As a matter of fact, a couple of years ago I thought of making a common repo for V500, V510 and VK810, to give support to all of them, but I don't own the three devices (so tests would be difficult) and I don't have much free time anyway.

No idea, but I don't give support for mods here (read first post), so it would be best to discuss it somewhere else so we can focus on development here. Feel free to create a new Q/A thread for this rom or just to discuss mods. You could also ask in viper audio thread or maybe some user can help you by private message.

Every device needs a vendor repo with the proprietary files. You can follow the instructions to extract the blobs from the device (in case you are already running Lineage 14.1), or simply add TheMuppets LG vendor to your local_manifest.xml (that's what everybody does, I think).
[G Pad 8.3 Original Android Development] Calibaan:
Ah, thx. :good: This additional LG vendor repo might help since using the extraction script does break building with missing targets, unknown lineage_v500 etc.
[G Pad 8.3 Original Android Development] Calibaan:
fefifofum´s hint concerning the TheMuppets repo was the missing link. THX again!

So if somebody does want to build the official LineageOS on it´s own here some hints from my side which are not mentioned in the official Wiki Howto http://wiki.lineageos.org/v500_build.html.

Instead of extracting the proprietary LG blobs add the appropriate TheMuppets repo in your local manifest. This has also the advantage that you don´t need a device with an existing LineageOS ROM installed for the extraction.

You need also additional blobs from Qualcomm which can be also found in this repo.

A local manifest is a XML file located in the .repo folder:

android/system/.repo/local_manifests

For e.g. you could create a file called local_manifest.xml in the mentioned folder using this XML content:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-14.1" />
<project name="TheMuppets/proprietary_vendor_qcom_binaries" path="vendor/qcom/binaries" remote="github" revision="cm-14.1" />
</manifest>

If building does still break after adding the additional repo then clean up things:

cd ~/android/system/
make clobber

Now start the build process again as explainend in the wiki article.

If the build process still stops around building the kernel you´re probably missing the lzop package on your system. At least this happened for me (don´t know why the lzop package has been removed on my system :confused:).

But you can add the package again with:

sudo apt-get install lzop

Afterwards start the build process again as explainend in the wiki article.
[G Pad 8.3 Original Android Development] bessakerb:
google play services error solution

you should set the webview channel to "stable" in the developper options or install the latest webview version for your android version
[G Pad 8.3 Original Android Development] mymmx:
Did you try installing via a new TWRP recovery? Sometimes it fixes. You can try some tips from this page.
[G Pad 8.3 Original Android Development] ronche2000:
Can I clean flash latest build Feb 14? Came from 2/1 build
[G Pad 8.3 Original Android Development] GXGOW:
No problem, clean flashing shouldn't create any issues normally.
[G Pad 8.3 Original Android Development] jesterhead82:
Worked for me yesterday, first boot is maybe not working not working properly (restarted it after some minutes, 2nd boot was fast then).

---------- Post added at 22:29 ---------- Previous post was at 22:28 ----------

Worked for me yesterday, first boot is maybe not working properly (restarted it after some minutes, 2nd boot was fast then).
[G Pad 8.3 Original Android Development] wizzardsk:
Guys, I still do not get the reason why QuickPic always deletes all the thumbs in 7.1.x while it works fine in 6.0.x. Even on my LG G3 in LOS 14.1 it works fine already (it is 2017-02-16 build)
[G Pad 8.3 Original Android Development] piit79:
Sorry if this is a stupid question but I didn't have luck searching. Anybody has any idea why latest CM 14.1 nightly (25 Dec 2016) boots fine but the first experimental migration build gives "Secure booting error" at bootloader (presumably) and doesn't boot? I tried flashing the -F bootloader but it didn't help.

Thanks!
[G Pad 8.3 Original Android Development] vedko:
It's because of the Loki vs Bumped kernels. It's been discussed here in quite a length, so you may want to go a few pages back. Anyway, short explanation and solutions can be found in this post:

https://xdaforums.com/showpost.php?p=70740668&postcount=91
[G Pad 8.3 Original Android Development] illusion119:
Hi guys! Thank you very much for your work here.

I'm planning to flash Lineage OS, actually I'm running the stock KitKat. The latest Lineage Nightly version is a stable version? I should use this one, or there are any important bug? To avoid problems, I'm planning to do a clean install. I guess I don't need to install intermediate versions, I can go directly to the latest Nightly, is this correct?

Thank you in advance.
[G Pad 8.3 Original Android Development] fishears:
Yes, a clean install of the latest nightly will work fine. No important bugs. In fact its a lot better than stock in many ways. Take a back up first just in case you disagree ;)
[G Pad 8.3 Original Android Development] Deltadroid:
TWRP with Lineage

[MENTION=4517918]fefifofum[/MENTION]

Since the default stock lineage recovery is not being worked on very much, can we make TWRP the stock lineage recovery instead, so the recovery gets automatically updated with TWRP when installing nightly builds?

Something like this?

https://review.lineageos.org/#/c/161968/
[G Pad 8.3 Original Android Development] earlemf:
OTA Nightly installs well once TWRP is updated to 3.0.2-2

After doing a clean install, OTA Nightlies did not install until TWRP was updated from 3.0.2.0 to 3.0.2-2. Updates perfectly!:)
[G Pad 8.3 Original Android Development] marty_bebop:
I've been running 1402 on my V500 for a few days and on the whole things have been very smooth, especially as I barely know what I'm doing.

Little question - in the "old days" there was a hidden or secret menu accessible by contacts and 3845#*500#. Is such a thing accessible within this ROM and if so how?

Thanks to everyone for their work with this ROM and keeping our V500's alive.

Marty
[G Pad 8.3 Original Android Development] illusion119:
Yesterday I did the upgrade. One word: Awesome!

Very smooth system, all functionalities that I've tested were working perfectly. Crazy jump, from 4.4.2 to 7.1 :D My tablet just reborn.

Thank you very much to all of you that makes this possible.
[G Pad 8.3 Original Android Development] marty_bebop:
Forgive my ignorance - are you saying that when a new nightly is released, your system will automatically update to it? I have TWRP 3.0.2-2 installed. Is there a setting somewhere to configure whether or not to check for and get/install new nightlies? If so, where is it please? If this is how it works, do you need to re-install GAPPS after the update?

Cheers,

Marty

Thanks to everyone for their work with this ROM.
[G Pad 8.3 Original Android Development] ThunderBolt_BR:
You must trigger the update process manually in settings, about tablet, LineageOS updates.

When available, You'll be able to download and will be asked to install an updated weekly. If you have a proper TWRP recovery, the whole flashing process will be automatic.

[]'s

Enviado de meu LG-V500 usando Tapatalk
[G Pad 8.3 Original Android Development] Cal:
Frankly, I still like to download from the link provided that has a MD5 file. I've never had an update go bad using the auto-update feature, but I just feel better to save the ROM file and check the MD5 and then use the latest TWRP to install.

But I presume it's as safe the auto way...but one has no check on the install file to make sure

it

is OK. Mistakes have happened to me many times on downloads executed on a tablet.
[G Pad 8.3 Original Android Development] Deltadroid:
To prevent any problems flashing zip files in the recovery, make sure that "check file signature" is selected in twrp options. This is the same as checking the md5sum and will prevent any corrupted files from being flashed. This option should be enabled by default in twrp.

Edit:

Since lineage uses a new key to sign it's zip files, I'm not really sure now if this method works with lineage. We would need to test that. It works with test keys.
[G Pad 8.3 Original Android Development] wizzardsk:
Downloading via updater still does not verify the md5, I have to download manually...
[G Pad 8.3 Original Android Development] Cal:
Very stable here with the 2017-2-23 Rom. Loaded much faster than 2-14 Rom also. Good nightly!
[G Pad 8.3 Original Android Development] paulomodesto:
I still can't update from updater.

In the end of download it gives an error.

Have to manually download from site and manually do everything.
[G Pad 8.3 Original Android Development] marty_bebop:
I did not know an update was available, I am set to check for updates weekly. Anyway, I manually triggered a check, downloaded and installed perfectly. Whilst I have not timed it, my device seems to boot quicker and performance seems snappier. Fantastic.

I have TWRP 3.0.2-2 installed - if you do not have that, maybe that is why you have run into some issues.

Many thanks to everyone who has/is contributing to the development of this ROM :)
[G Pad 8.3 Original Android Development] paulomodesto:
That's the TWRP version I have, it's the latest for our device.

But I cannot figure out what is the cause I can't download to the end the file.

I always trigger manually the OTA update, it's not set for automatically do it because I don't won't to be always flashing a new ROM version.

I stay a while with a version of a room that don't give me problems.
[G Pad 8.3 Original Android Development] Deltadroid:
This is a known issue. I have the same problem sometimes.
[G Pad 8.3 Original Android Development] snke:
What's happened with Chromecast notification sounds??

:eek:
[G Pad 8.3 Original Android Development] kaalalto:
The ROM is really stable and I'm enjoying Android 7.1.1 on my device !

I have this issue : IR blast seems not working with my apps. Did you tried a specific app that works or it's just because IR is nor supported yet ?

Thanks !
[G Pad 8.3 Original Android Development] GXGOW:
IR blaster doesn't work on any of the custom ROMs, since it is managed by proprietary libraries from LG, which we don't have access to. It used to be in the OP, but I guess he forgot to put it back after the transition to LineageOS.
[G Pad 8.3 Original Android Development] GXGOW:
Can confirm this. Probably just a visual issue.
[G Pad 8.3 Original Android Development] piit79:
Thanks a lot! I did read a bit about bumped vs. loki. What confused me was that Lineage was said to be bumped, which apparently wasn't true for the experimental migration build. Flashing v500-loki-kernel-to-bumped-kernel-signed.zip after the experimental build worked and as did flashing further standard builds without it.
[G Pad 8.3 Original Android Development] switch_42:
Hi all,

I updatet to last nightly but the pad reboots after unlocking the screen. I flashed it two times but still no result.

TWRP 3.0.2-2 is installed.

Any hints?
[G Pad 8.3 Original Android Development] andreshell:
NAVBAR

Any method to reduce the size of the navigation bar in this rom ?? Thanks for any help
[G Pad 8.3 Original Android Development] Cal:
As you're not specific as to 'what' you updated from...might be helpful if you stated this info. Also, it must not have been direct download of the nightly internally because if you used the auto-update feature it would not update but once and not give you a second go at it, at least to my understanding.

Tell the forum what *exactly* the facts are about your system in detail and someone will be able to see what might be causing your problem.
[G Pad 8.3 Original Android Development] NatanaelRS:
Yes! I did it!

PPFirst time rooting and flashing a Android device.

Device: Brazilian LG GPad 8.3 V500.

Original ROM: stock LG 4.4.2.

Current ROM: LineageOS 7.1.1 14.1-20170223NIGHTLY-v500 (clean install)

Also first time bricking and unbricking an Android device. It seems caused by SuperSu. After reboot the system keeped for hours into bootscreen. Solved by reinstalling the LineageOS in recovery mode.

My opinion on LineageOS:

Much much better than stock ROM.

It have a pure Android Look and Feel and so it's very beaultiful.

It's fast and smooth. No lags or microlags like stock ROM.

It's updated with the lastest version of Android, not thanks to LG.

And finally it very complete and funcional. Stock ROM was a trash.

Now, it seems a new device. Very happy and proud!
[G Pad 8.3 Original Android Development] switch_42:
Ok. Here are my facts:

I came from nightly 2017-02-14. My first try was using autoupdater but it ends in reboot after unlocking the device.

Then I went back and flashed 2017-01-26 with TWRP 3.0.2-2 and all was fine. So I downloaded 2017-02-23 again and flashed it without autoupdater. But again it ends in restarts after unlocking the device.

Now I'm back on 2017-02-14 without any problems.

I have no idea what went wrong.
[G Pad 8.3 Original Android Development] Cal:
If you followed all of Fefifofum's instructions on the first page...then that is what I was wanting you to post to show us where you started...but if all is solid and OK now, I believe you did follow the instructions. Reason I inquired was that many of the flaws from users have been from not following every install instruction to the letter from the first page of this thread.

Good luck and thanks! :)