yashsingh1/xdaforums huggingface dataset:
[G Pad 8.3 Original Android Development] Darkmasterhk:
Getting SuperSU to work

[MENTION=3345782]Disrupthor[/MENTION]

Just flash this file by [MENTION=5227588]Deltadroid[/MENTION] (after flashing SuperSU)

The first file should be enough I guess. But I've no idea if "rebumping" could have unwanted side effects, cause I don't know anything about it.^^

Also use the systemless version. I tried it with 2.67.

Guess this should also work with other roms.

Maybe someone with more knowledge then me can create something like this

---

[MENTION=4517918]fefifofum[/MENTION] if you have some time maybe you could take look at this issue it appeared for the third time

by now and I always need to wipe /data. Strange thing is it just started to appear recently, it worked fine

for a few months. Might it be related to an app that corrupts the fs or something?

Guess for now I go with ext4.
[G Pad 8.3 Original Android Development] Deltadroid:
"rebumping" the kernel should not have any unwanted side effects. That is great that you found a way to make SuperSU work.
[G Pad 8.3 Original Android Development] davebuk:
See http://xdaforums.com/showthread.php?p=64816681 #257

It describes the same issues I had when trying to use the SD card as internal storage.

As a fix, either the OTA app within CM13 needs the option to choose some other storage location or TWRP needs to be able to access the encrypted files on the SD card.

[MENTION=4517918]fefifofum[/MENTION] /all, please correct me if I'm wrong [emoji3]
[G Pad 8.3 Original Android Development] Disrupthor:
[MENTION=5031769]Darkmasterhk[/MENTION] Thank you so much, rebumping works perfectly.

Now, [MENTION=4517918]fefifofum[/MENTION] could you investigate why after using this (http://xdaforums.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796) I still can't use V4A with your ROM/kernel with SELinux in Enforce? I have to set it to Permissive in order for V4A to work as oposed to my other devices. Tank you.
[G Pad 8.3 Original Android Development] GXGOW:
I second this. I also expected it to work now in Enforcing mode with SuperSU, like on my Oneplus One, but unfortunately, it doesn't. It's not that big of an issue, but if there's some spare time, could you take a look at this?

Sent from my LG-V500 running CM 13
[G Pad 8.3 Original Android Development] StraightOn.NL:
Did a clean install, wipped the CM12.1 completely and installed the nightly from 13th january.

Now I can't boot into TWRP anymore and I have lost root access (and yes, developer options are enabled, and yes root access is enabeld for APPS and ADB)

I even lost the 'root-access' prompt in the LG screen when booting...Any idea anyone?

::edit::

Hmmm didn't have the kitkat boatloader when I flashed cm13 from TWRP; still weird and still not found a solution...
[G Pad 8.3 Original Android Development] fefifofum:
I will need logs to fix that. Please read post 2.

Installing cm-13.0 doesn't affect recovery, and root access is working as expected. I guess you did something else, so it's hard to give you a solution.
[G Pad 8.3 Original Android Development] StraightOn.NL:
thanks, fully aware of that...that why i said "weird" haha...gonna try to root it again...:

::edit::

Not a final conclusion but:

I was going to enable root access again, so i was following this guide: link

Downloaded the LG Gpad Android USB drivers and downloaded the Kingo app

Connected my Gpad with USB debugging enabled...but Kingo did not detect the USB debugging mode...So I decided to reboot the Gpad.

::this is where the magic happens:: I press reboot, and all of a sudden I get the old familiar "do you want to boot into recovery/soft reboot/etc" prompt. So I went ahead and clicked 'Recovery"

Then it took maybe 5 minutes or so...and again magic happens...It booted succesfully into TWRP

I managed to flash the correct kitkat bootloader, wipped dalvik and cache and flashed the 25/1/2016 CM13 version...after the install I rebooted yet again to recovery...and ofcourse (yes I should have expected that) I got:

Fastboot mode started

udc_start()

Gonna try to fix root for real now...and then Gonna try to update TWRP to latest...I was/am on 2.6.2.X

::edit2::

- Have been unable to re-root the Gpad from CM13: Kingo app keeps on failing, other tools are for 4.4.2. only (like root_gpad and ioroot25r1)

- Have been unable to revert to Android 4.4.2. stock with LGMobileSupportTool.exe tool (does not accept the serial number)

- Did get into FASTBOOT mode when using the CM13 build-in 'boot to recovery' mode.

- Via FASTBOOT flashed twrp-2.8.7.1-v500.img using this guide

- Now I am ABLE to boot into TWRP via the build in CM13 build-in 'boot to recovery' mode (YEAH!)

- Upon the first entry of the latest TWRP version I got this message:

I accepted; swipe to modify.

- Quirk...still says I don't have root access and am unable to update SuperSU

Conclusion: i think flashing CM13 with an outdated TWRP version and an to old bootloader f*ck something up...
[G Pad 8.3 Original Android Development] Wicked One 612:
USB OTG + Charging

I see that in the kernel menuconfig (https://github.com/awifi-dev/android_kernel_lge_awifi is the correct source for the V500, correct?) there is an option for USB OTG ACA at:

Device Drivers > USB support > Support for accessory charger adapter (ACA). This is disabled by default. When enabled, there's also an option for 'Support for Standard ACA (New)'.

I am extremely hopeful that these options allow me to use USB OTG and charge the tablet at the same time using an OTG Y cable. That is my end goal, as I plan to have this tablet in a fixed installation.

I have unsuccessfully attempted to compile and flash the kernel with this option enabled. Maybe someone here can help a fella out and point out the error of my ways?

Here are the steps I've taken so far:

1. Clone https://github.com/awifi-dev/android_kernel_lge_awifi
2. Clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/
3. export ARCH=arm, export SUBARCH=arm, export CROSS_COMPILE=~/android/arm-linux-androideabi-4.9/bin/arm-linux-androideabi-
4. make awifi-perf_defconfig
5. make menuconfig (enable the ACA options).
6. make

There were a bunch of compiler errors (and warnings that were treated as errors) that stopped the build. Some were misspellings of methods, undefined variables, CONFIG_DEBUG_FS defines improperly placed, etc. I managed to fix all of those and get it to compile.

That's about where I'm stuck. I have the zImage, but I'm unsure of the proper way to flash it to the tablet. I read about using fastboot, but unfortunately, adb reboot bootloader does not boot into the bootloader, it just reboots the tablet. So I attempted to get the kernel into a zip to flash in TWRP. I downloaded another kernel in this forum, unpacked it, swapped the zImages, and repacked it (making sure there wasn't anything extra being installed in /system). Flashing that seemed to work and I confirmed that it installed in the Settings > About. But alas, as soon as I plugged in a USB (any USB, even a normal one to my computer), the tablet freezes and then reboots. It refuses to boot into the ROM unless I unplug the USB. This happens even when I compile the kernel clean without altering anything in menuconfig.

So I'm a bit stumped. It might be that I'm not installing the kernel properly or it might be that I'm compiling it incorrectly. Does anyone have any advice on getting this working? Maybe there's an even easier way to get USB OTG + charging working that I'm unaware of. Cheers!
[G Pad 8.3 Original Android Development] ckret:
there is an echo in skype

anyone experiencing the same or is my device broken?
[G Pad 8.3 Original Android Development] Deltadroid:
I've just updated the Marshmallow Base Gapps installation so that Google's Setup Wizard will not replace the stock Provisional Setup Wizard. This seems to be causing FC's with the latest CM source code on a fresh install. By default, Google's Setup Wizard will now be an addition to the stock provisional setup wizard instead of a replacement.

Edit:

It is still uncertain if these changes did actually fix the recent fc problem with Google's setup wizard after all. It needs more testing. We will know if there is a problem once we get a new build and perform a fresh installation of the ROM.
[G Pad 8.3 Original Android Development] fefifofum:
Yes, twrp needs an update to handle encrypted sdcard used as internal storage.

I guess rooting/rebumping the boot.img is detected by selinux, because in your logs there are a several denied init services which normally aren't. I checked oneplus one selinux policies and they don't have rules that match the denials in your logs.

On first post it says kitkat bootloader is a requirement, and you can find it in post 3. Also on posts 1 and 3 I mention that latest official TWRP is recommended. Maybe the conclusion should be that it's always better to read first.

Yes, https://github.com/awifi-dev/android_kernel_lge_awifi is the source for the kernel, and it builds fine in cm-13.0 tree (no errors at all). That would be the easiest way for you get your boot.img, or you could also extract the boot.img from latest cm-13.0 release, replace the kernel, pack the boot.img again and bump it. If after trying it you don't manage to do it, send me a pm with the defconfig changes and I will build a boot.img for you. BTW, the defconfig file used in cm-13.0 builds is cyanogenmod_awifi_defconfig (not awifi-perf_defconfig), as you can see here.
[G Pad 8.3 Original Android Development] redhk886:
is it possible to add knock code to this rom?
[G Pad 8.3 Original Android Development] Deltadroid:
you could rebump and turn selinux off with one of those scripts I posted a while ago, but, why not just use the stock superuser? That would be the easiest and safest way.

---------- Post added at 09:11 PM ---------- Previous post was at 09:10 PM ----------

Read op. You just need to enable it.
[G Pad 8.3 Original Android Development] Deltadroid:
I'm trying to fix ability to restore system settings upon initial installation. Please see following post: http://xdaforums.com/showpost.php?p=65065486&postcount=1912

If you can help test, please let me know.
[G Pad 8.3 Original Android Development] redhk886:
i was referring to the lock screen knock code, not the knock to wake up.
[G Pad 8.3 Original Android Development] GXGOW:
There's an Xposed module for that: http://xdaforums.com/showthread.php?t=3272679

Sent from my LG-V500 running CM 13

---------- Post added at 10:57 AM ---------- Previous post was at 10:51 AM ----------

Well the main reason why we wanted SuperSU to work is so that we can use Viper4android with SELinux in Enforcing. Currently it only works in permissive if you're using anything else than SuperSU.

Sent from my LG-V500 running CM 13
[G Pad 8.3 Original Android Development] redhk886:
Is the ext SD card formatted as internal storage option working for you guys? Once formatted, it only shows up in settings.I can't access it,it doesn't show up in file managers or when I connect to PC.only format as portable works.also in LP when adding another user,you get separate SD and ext sd so you can have your own files and apps.but now just SD, both users use the same ext SD.was this feature removed with MM or is it just this ROM?
[G Pad 8.3 Original Android Development] Wicked One 612:
Nice, it works! My problem was that I wasn't using cyanogenmod_awifi_defconfig. Thanks fefifofum!

I used the process in this thread to extract and repack the boot.img.
[G Pad 8.3 Original Android Development] juniorhxcx:
Good afternoon!

I got a doubt, could help me as soon as possible, please.

The problem of dismantling the MicroSD from previous versions still continues?

When I now install Android 6.0.1 enabling it to use as an internal MicroSD? What is the advantage of that? A bug? You are ready for everyday use?

Thank you!
[G Pad 8.3 Original Android Development] redhk886:
WiFi keeps dropping. Wifi icon greys out, nothing happens when i press it.I have to enable flight mode then disable to fix.
[G Pad 8.3 Original Android Development] Deltadroid:
You are in demo mode.
[G Pad 8.3 Original Android Development] redhk886:
Demo??? What do you mean? I haven't changed any settings.
[G Pad 8.3 Original Android Development] Cal:
Where, and what, is this 'demo mode'?

@Deltandroid: Explain what demo is please.

Thanks!
[G Pad 8.3 Original Android Development] Deltadroid:
[MENTION=4340741]redhk886[/MENTION]

In demo mode, the status bar is cleaned up and shows no notifications, a full battery, full Wi-Fi and cellular signal strength, and the time is always set to 6:00.

Settings-> About (tap on build date about 5 times)
[G Pad 8.3 Original Android Development] redhk886:
then im not in demo mode. everything looks normal,just the wifi keeps dropping.
[G Pad 8.3 Original Android Development] Cal:
What about 7 taps there to get "Deve!oper"?
[G Pad 8.3 Original Android Development] Deltadroid:
That is still the same.
[G Pad 8.3 Original Android Development] jt1998:
Started having an issue when updating apps from the play store. Wifi is connected/working. But apps won't update and get an error that Background data needs to be enabled. Ummm what? Don't know why its asking for that. I try toggling airplane mode and sometimes that works. Reboot usually resolves it until the device goes to sleep again and then the issue happens again...advice/solution? Thanks all.
[G Pad 8.3 Original Android Development] Wicked One 612:
Is there a file I can write to on this ROM (e.g. echo 0 > /sys/class/power_supply/...) that will allow me to enable/disable charging? I'd like to be able to control through software whether the G Pad is charging or discharging while leaving it connected to a charger. If there's no way to explicitly disable charging, perhaps there's a way to programmatically limit the current that is drawn (effectively disabling/enabling it)?

EDIT: Figured out how to do it. For anyone trying to do the same here it is.

To disable charging:

echo 1 > /sys/module/pm8921_charger/parameters/disabled

To enable charging:

echo 0 > /sys/module/pm8921_charger/parameters/disabled
[G Pad 8.3 Original Android Development] fefifofum:
The problem is that bump edits the boot.img, and that is detected by selinux and blocks some services. The best solution would be SuperSU no needing to edit the boot.img to root, or V4A not depending on SuperSU.

If you want to lock the screen with a double tap, that option is already available but only on the status bar. If you want it to work anywhere on the screen, then no, I cannot add that code to this rom.

I guess that is the default behaviour in MM (or cm-13.0).

The sdcard unmounts only happen with some sdcards, not others. If you have a lot of sdcard unmounts, the easiest solution for you would be buying a new sdcard. There is a samsung sdcard that has been recommended in several threads, use the search function.

I never had that problem. If you don't attach logs I cannot help you. Please read post 2.

Did you read the FAQ section in post 2? There is a solution for gapps problems. Also, are you using the recommended gapps in post 1?
[G Pad 8.3 Original Android Development] jt1998:
I am not using the recommended delta gapps. Sorry and appreciate the help. I'll reinstall and use the recommended ones. Thanks.
[G Pad 8.3 Original Android Development] redhk886:
what your referring to is knock on, right? where you turn screen on and off by double tapping, that works. I'm talking about knock code. where you tap a 4 squared pattern on the lock screen to unlock device.
[G Pad 8.3 Original Android Development] fefifofum:
New build released

with launcher rotation enabled by default and battery percentage visible during off charge.
[G Pad 8.3 Original Android Development] mackeev:
Thank you ever so much for this!
[G Pad 8.3 Original Android Development] Deltadroid:
The new live lock screen in this latest version is nice!
[G Pad 8.3 Original Android Development] ThunderBolt_BR:
Hi [MENTION=4517918]fefifofum[/MENTION],

Please don't understand this as a request, just a doubt: I know that our cameras are very limited, but do you have plans on bringing CM's Snap camera to our V500?

Thank you for your superb work!

[]'s

Enviado de meu LG-V500 usando Tapatalk
[G Pad 8.3 Original Android Development] mackeev:
... and buggy! I can't turn if off. To reproduce:

1. Turn off Live lock screen in Settings-->Lock screen

2. Reboot.

It will be on, while it's still off in the Settings. You need, once again, to turn it on and than back off. It will be off... until next reboot. Weird.
[G Pad 8.3 Original Android Development] Deltadroid:
Strange, I'm unable to reproduce that problem.
[G Pad 8.3 Original Android Development] mackeev:
Thank you for your prompt response. It is really strange. I returned to the previous build - the problem disappeared (there is no "new live lock screen" in 20160125). I re-flashed the latest build - the problem is back again. Luckily, I made a backup on Feb 6 (with the latest build). To enable live lock screen in it (I've never used one, ever), I need to turn it on and tap the radio button on Colors (it's blank and I don't see any other option). And thus the problem starts. I'd better stick to no live lock screen at all.
[G Pad 8.3 Original Android Development] giovaorama:
I have the same problem

Inviato dal mio LG-V500 utilizzando Tapatalk
[G Pad 8.3 Original Android Development] Deltadroid:
permissions error

[MENTION=4517918]fefifofum[/MENTION]

When I use Root Explorer to copy a *.md5sum file from the network to my external sdcard, I get the following error:

http://pastebin.com/QsBpgns8

Although, when I use Root Explorer to copy a .md5sum file from the network to my internal sdcard, then it works fine.

Ive tried renaming the file to *.md5, but nothing seems to work when I copy the file from a samba drive to my external sdcard.

Edit:

I've found the following selinux denials, which could be related:

[72529.861019 / 02-07 23:14:00.187] type=1400 audit(1454883240.187:279): avc: denied { getattr } for pid=10027 comm="IntentService[S" path="/cache/recovery" dev="mmcblk0p24" ino=14657 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:recovery_cache_file:s0 tclass=dir permissive=0
[72529.861995 / 02-07 23:14:00.187] type=1400 audit(1454883240.187:280): avc: denied { getattr } for pid=10027 comm="IntentService[S" path="/mnt/media_rw" dev="tmpfs" ino=7259 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:mnt_media_rw_file:s0 tclass=dir permissive=0
[G Pad 8.3 Original Android Development] turbomann:
When i force selinux permissive all works (Viper including) but when you shut off the screen, tablet blocks itself and no more shows image. Just wait to superSU, I think

Enviado desde mi SM-N920C mediante Tapatalk
[G Pad 8.3 Original Android Development] Deltadroid:
I'm having the same problem you described also now. I'm unable to disable the live lock screen once I enabled it. The live lock screen turns back on after every reboot.
[G Pad 8.3 Original Android Development] fefifofum:
New build released

with upstream fixes and and other minor updates. I will test again Snap camera app to see if I can include it in next release. BTW, I made a stupid mistake and you won't be able to ota update to this release, so you'll need to install it manually.
[G Pad 8.3 Original Android Development] Deltadroid:
Thanks for the update. The problem with disabling the live lock screen is now fixed. Good work!
[G Pad 8.3 Original Android Development] fishears:
Any chance you could add 2560x1600 (8:5, 4.1MP) resolution to the back camera for our device?
[G Pad 8.3 Original Android Development] wizzardsk:
No update found in cmupdater, why?
[G Pad 8.3 Original Android Development] ThunderBolt_BR:
Man...

Just two posts above yours...

Fefifofum said that he made a mistake and this time we will have to download and install it manually.

[]'s

Enviado de meu LG-V500 usando Tapatalk
[G Pad 8.3 Original Android Development] wizzardsk:
Sorry, and thank you very much :)
[G Pad 8.3 Original Android Development] mdio:
Hello all.

I'm using this ROM for a while and I am very happy with it, thank you.

But I have a newbie question: Is it safe to do the OTA updates that appears in "CyanogenMod updates" ??

Thank you.
[G Pad 8.3 Original Android Development] Deltadroid:
Yes. It is safe to use the cmupdater with this rom. Although, the last update is unavailable with cmupdater and will be fixed in the next release.
[G Pad 8.3 Original Android Development] mdio:
Thank you. ;)

Have a nice weekend.

EDIT:

How do change this alfabetic order to the regular screen?
[G Pad 8.3 Original Android Development] fefifofum:
I think that depends on the camera app. Usually only 4:3 and 16:9 resolutions are available, but maybe I can add that resolution to Snap camera app when/if we switch to it.

I explained it in my latest post. Anyway, today I tried to fix it, but I'm not sure if it will work. Full changelog in post 1 is also corrected.

From launcher settings (long press on empty space of the launcher).
[G Pad 8.3 Original Android Development] darksidesh007:
Anyone having an issue with turning on bluetooth causes a FC of settings, and won't enable?
[G Pad 8.3 Original Android Development] ThunderBolt_BR:
No issues with Bluetooth here.

[]'s

Enviado de meu LG-V500 usando Tapatalk
[G Pad 8.3 Original Android Development] GXGOW:
I connected to my Bluetooth speaker without issues a few minutes ago. Did you install a theme? Have you tried rebooting?

Sent from my LG-V500 running CM 13
[G Pad 8.3 Original Android Development] darksidesh007:
No Themes, and rebooted into recovery to wipe Cashe/Devork (sp), and still the issue. Going to wipe totally and restart from scratch.
[G Pad 8.3 Original Android Development] wiedster:
so, first of all thx for the work thats been put into this rom. i had a twrp recovery ( dont remember the version) and cm12 installed (rooted). i wanted to try this rom and installed it just like every other rom i ever installed ( via recovery). i flashed the rom, the gapps and the bootloader. before that i made a backup of my old system just in case. after bootup and setup i found that my root was gone. in no way im an expert user, but AFTER bootup i did nothing to hurt my root access. now i cant enter recovery to reflash my backup. i enabled root in the developers options. i installed supersu. what can i do to regain root? to enter recovery? help!!oneeleven
[G Pad 8.3 Original Android Development] jt1998:
Well if you enabled root in developers options then you have it.

What happens when you try to enter recovery? Just reinstall twrp again like the 1st time.
[G Pad 8.3 Original Android Development] wiedster:
rootcheck and all other things tell me i dont have root. i have no access to my recovery. could it be, that by installing the bootloader i removed my twrp recovery and my root? i did this years ago, so i dont remember how i installed my recovery the first time. ill have to look into that.

edit: i double checked that root is "on" in dev options.
[G Pad 8.3 Original Android Development] Deltadroid:
I do not recommend using SuperSU because it will cause problems with the boot signature, since we must use a bumped boot image. Use the built in super user that is included with cm instead.

Flashing the bootloader will not replace the recovery. It is possible that your older recovery was using the loki method which is no longer compatible with the new aboot partition from the new kitkat bootloader.

If you updated the bootloader to the latest kitkat, you should also flash an updated version of the recovery.
[G Pad 8.3 Original Android Development] wiedster:
1. but how do i flash it?

2. there is no super su app besides the one i installed from market.
[G Pad 8.3 Original Android Development] Deltadroid:
You could try booting into the recovery using the button press method, before the system boots. Otherwise, if your recovery really is inaccessible, you may need to go back to stock and start over.
[G Pad 8.3 Original Android Development] wiedster:
the button method (the one mentioning a wipe) yields no result. any hint how to go back to stock?
[G Pad 8.3 Original Android Development] Deltadroid:
http://xdaforums.com/showthread.php?p=57137360