yashsingh1/xdaforums huggingface dataset:
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] young0ne:
I ask one the guys in the other fourm he replied back with this

will this be of some help to you?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] smr404:
Final edit: this is not actually an issue if you flashed the kernel successfully unlike I had. If you flash the kernel in TWRP and it reverts back to the stock LG one, try flashing it again (like it says in the instructions) and try wiping the dalvik cache immediately after the flashing operation. Worked for me. End of edit.

[MENTION=5672995]jcadduono[/MENTION] Running lsusb does indeed show the external wireless card. This is reassuring because it is clear the issue is not due to power supply or something.

The 'enable monitor mode' command in the nethunter app is intended for use with a wlan.

Unfortunately, the external wireless card is not automatically assigned as wlan1 (or any wlan number), as I might expect.

Is there a way to assign the wireless card as a wlan (shouldn't drivers ensure this happens automatically?).

Below are screenshots of lsusb and ifconfig just to show that the device is recognized as a usb device but is not assigned as a wlan.

Edit: Welp, only 1 screenshot appears to have uploaded...

Final edit: solved, see top of this post.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Gungrave223:
Follow up question if you don't mind... Is it patched to no longer report the bootloader status to SN?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] 533y4:
Anyone else install this and not able to mount /system as read write? I did some searching and found an and command "adb disable-verityv. Any thoughts on this?

Also when I goto install a chroot env, I keep getting no bootkali* files at all in /system/bin/*. And when I goto symlink them myself, I (ofcourse) get the read write problem. Help?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] LvDisturbed1:
Can't set TTL target in iptables. Is this not yet supported?

Edit: Confirmed. I checked /system/lib/modules/ and xt_hl.ko is missing. Any chance this can get cooked in the kernal?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] smr404:
Final edit: this is not actually an issue if you flashed the kernel successfully unlike I had. If you flash the kernel in TWRP and it reverts back to the stock LG one, try flashing it again (like it says in the instructions) and try wiping the dalvik cache immediately after the flashing operation. Worked for me. End of edit.

Looks like my issue with the AWUS036NEH wireless adapter is undoubtedly due to drivers on the LGV20.

I went ahead and plugged in the adapter to my laptop running kali linux. Running 'lsmod' before and after I plug the adapter in shows that my laptop loads the appropriate modules as soon as I plug it in. They are:

rt2800usb

rt2800lib

rt2x00usb

rt2x00lib

All of these can be found in /sys/modules

Now, stepping away from my laptop and going to chroot on the LGV20: using the kali shell to navigate to sys/modules/ I don't see any ralink drivers. Here is a screencap of the contents of /sys/modules.

Are the wireless drivers actually included or am I missing something stupid? (sorry if I am)

Final edit: Turns out I was missing something stupid. There were no mistakes by jcadduono and everythings works if you pay better attention to what your doing than I did. See top of this post.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] jcadduono:
Done. KCAL in next build.

Done. Enabled a few different things: https://github.com/jcadduono/androi...mmit/42191cecdf74f3c466901ab578f2088c83595069

we don't build wireless as modules, we build them into the kernel, I can't help you unless you provide dmesg of unplug/replug

that being said I don't know why they aren't showing up in /sys/modules for you since they should show up even if built in... they are being built with the kernel and I can see them getting linked in.

WAIT A TICK, I see dm verity in your modules!

You don't even have the NetHunter kernel flashed!

Update: New kernel up on nightlies! (I also added that safetynet hack thing hoping it would assist with something, dunno if it even affects this device)
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] slayerh4x:
Hey,

I have this same adapter and it works fine on mine. I've been running wifite, reaver, aircrack etc for days now. I simply had to enable monitor mode and start using it. :confused:
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] smr404:
Yes, turns out it was wholly my fault. SuperSu must have gotten rid of the kernel the first time I flashed it. So I went back and flashed it twice in a row and it stuck the second time. I wiped the dalvik cache second time around, not sure if it helped but it didn't hurt. Now everything works, I mean everything.

I want to thank [MENTION=5672995]jcadduono[/MENTION] for his wonderful work and patience towards a noob like me. Sorry for the confusion. I went back and edited my posts to show it's actually a non-issue.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] LvDisturbed1:
Cool, I'll try testing out iptables later tonight. Thanks!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] smr404:
Two bugs to report.

I'm using us996 and on the latest kernel (the zip was named kernel-nethunter-us996-nougat-3.15.3-20161126-1805).

1.) Bluetooth doesn't seem to work at all. In the stock settings app, the bluetooth address is listed as 'unavailable'.

2.) Every 45 minutes or so, the kali splashscreen appears out of nowhere, and the device appears to reboot (looking at the logs make me think the system is actually rebooting). It happens even when the phone is not in use. Once, it was charging and out of the corner of my eye I saw the screen turn on and the splash screen appear. It took around 10 seconds for the splash screen to finish, it then immediately went to the lock screen and I was able to unlock the phone. The phone had to reacquire cell signal. I paid attention to the uptime and the 'crashes' don't reset it.

I know another user reported dropped calls but that doesn't seem to be an issue for me.

Edit: Logs in my next post
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] jcadduono:
sounds related to changing fm/bt to builtin...see if https://build.nethunter.com/test-builds/lge/kernel-nethunter-us996-nougat-bt-test1.zip does anything to help

still, logs would be really nice!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] smr404:
Ok, here are the logs. I followed the instructions you gave to dfogelstrom.

A crash occurred around 11-26 22:15:06, I believe. I had to split up the logcat file since it was > 512kb.

Thanks a bunch! Tell me if I forgot to retrieve a useful log. I'll try that zip and see if it helps.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] LvDisturbed1:
Last kernal nightly fixed iptables for me, but am also experiencing random softboots. Happened a couple of times while at work, so couldn't pull logs. I'm waiting for another so I can pull them.

Edit: Bluetooth is also broken for me. H918 user here. Of course as I wait for another softboot, it's working fine besides Bluetooth. I looked for a last_kmsg, but it wasn't there.

Edit 2: Finally crashed again. Here are some logs. Crashed right before 03:31. Hope this helps!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] jcadduono:
please try https://build.nethunter.com/test-builds/lge/ (bt-test1)

i think both the crashes and broken BT were due to conflicting bluetooth power management drivers loaded at same time
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] LvDisturbed1:
BT seems to be working now, but I got another softboot. Logs provided.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] jcadduono:
those fatal errors are really weird for sure...doesn't make sense, /system/bin/dex2oat is using /system/bin/linker and /system/lib64/libcutils.so is for some reason getting called instead of /system/lib/libcutils.so

i'm not sure they are actually part of your soft reboots though, they certainly don't seem kernel related :S

try flashing pure stock boot/system and then just that last kernel test and getting logcats, maybe see if youre still getting it with stock kernel as well

dmesg has no errors to report it seems
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] NotATreoFan:
Installed the latest test (bt-1) H918 kernel posted above, and I lost SuperSU. I got it back, but want to make sure I didn't do anything to cause the kernel to return to stock.

Flashed test, lost root

Boot to TWRP, flash stock boot.img

Reboot directly to TWRP, flash test kernel

While still in TWRP, flash SuperSU 2.78 SR4

After doing that, I had a full reboot (with T-Mo jingle during splash), and then 2 or 3 soft reboots where it just went back to splash screen but played no sounds.

Is this normal?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] NotATreoFan:
[MENTION=5672995]jcadduono[/MENTION]

My phone booted into the OS, and then proceeded to soft reboot around 10 times in under 5 minutes on the test kernel. I grabbed console-ramoops from /sys/fs/pstore/, is that the file you need to analyze?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] jcadduono:
all the files from /sys/fs/pstore makes it easier, especially if you have a timestamp of when the soft reboots are happening that i can compare to in the logs otherwise i am just left guessing

was the soft reboots happening on previous builds like:

https://build.nethunter.com/nightly/3.15.3-20161121-2039/

or...

https://build.nethunter.com/nightly/3.15.3-20161125-1955/

if not, i can probably attribute it to the kcal driver patch being incompatible with LG's massive changes to display calibration drivers

btw, flashing just the kernel by itself couldn't kill supersu, it doesn't remove anything :S

the soft reboots on boot after flashing supersu are normal, supersu is supposed to do that

sound shouldn't disappear though...

try kcal app and see if using it causes crashes too: http://downloads.codefi.re/savoca/kcal/re.codefi.savoca.kcal-v1.2.apk (or if it even works at all)
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] NotATreoFan:
I was running the 3.3.2 ROM from [MENTION=1325580]Tilde88[/MENTION] prior to flashing your test kernel. Everything was good up to that point. After flashing only the test kernel, I had lost SuperSU.

The only file in pstore was the console-ramoops, and I've uploaded it to my Dropbox. I had to dirty flash the ROM again to clean get the soft reboots to stop. I can do some more testing tomorrow morning, but I'm heading to bed and can't risk reboot loops and missing my train to DC due to alarm not going off.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] LvDisturbed1:
https://build.nethunter.com/nightly/3.15.3-20161125-1955/

This one is worked fine for me besides the iptables not supporting TTL target. I flashed it again and random softboots stopped.

Edit:

Good news is these errors dont seem to be related to softboots issue. Logs indicate I am getting those strange fatal errors still. For some reason dex2oat is linking /system/lib64/libcutils.so but wants /system/lib/libcutils.so. Why would it want to load the 32-bit dependency over the 64-bit one? Shouldn't it choose either depending on the if the app it is trying to convert is compiled for 32 or 64-bit?

I was using Tilde88's modded stock ROM v3.3.2 as my base and flashed Kali Nethunter kernal and full rolling pack after (after removing SuperSU). I am going to try the stock deODEX ROM alone to see if this error clears, then try Kali Nethunter after if it does.

Even though these errors don't seem related to the softboots, they are bugging me. I want to get to the bottom of it lol.

Edit: Well, looks like stock deODEX ROM did the trick. No more fatal errors. I'll give the test kernal another go and see if softboot still occurs, hopefully with better logs.

Update: Another softboot. Logs, hopefully with some useful info inside. I want to say crash started around 05:35:54 or so. Unfortunately time stamps in console-ramoops are useless. I'd look towards the bottom of the log though. Done all I can tonight. Time to pass out.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] young0ne:
Hey I tried the kernel bluetooth is not working Kcal works fine I pushed it as hard as I can no reboots while change values. I only had one reboot that I seen but nothing other than that. Im on a stock ROM nothing else just flashed kernel 11262015-1805

edit I'm now getting reboots at least every 20 minutes I haven't did a manual Cat login a while is there an app I can use to make it easy for you to get this log quickly?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] smr404:
My bluetooth was not functioning at all and I was getting softboots every 30 minutes until I flashed the latest kernel. I'm now on 20161125-1955 and bluetooth works. I haven't had a softboot in the approximately 5 hours that it has been flashed. Try flashing the new one.

Edit: 1955 is not and was not the latest kernel when I posted this message. My mistake! 1955 is pretty stable though.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] NotATreoFan:
Is your ROM full stock, or are you running one of the customized ones uploaded here?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] young0ne:
Delete
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] smr404:
I have the US996 btw. Coming from a fully stock ROM, I flashed the kali kernel and installed nethunter. I haven't tried any other ROMs.

Edit: Also when I was on the other kernel, the older one giving me softboots and bluetooth issues, the phone would get very hot at odd intervals. Battery life was decreased by like 5 times. I would look at the battery usage application and graph's line would be pointing nearly straight downward following softboots. Then this morning I found that the device had turned itself off overnight and didn't want to turn on whatsoever. Power button did nothing at all. I thought it was bricked for sure. I took the battery out a few times and removed the sd, and it finally turned on. The phone had been plugged in the whole time and the battery was at 100% so it wasn't due to battery. I power cycled it a few times before I realized that that was probably a stupid idea. My first priority was then to update the kernel. I did, and all the above issues seem to have gone away. Time will tell if they really have.

Edit 2: I'm on the 20161125-1955 kernel for the us996.

Edit 3: ^ that's not even the latest kernel. My mistake. It's relatively stable though.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] LvDisturbed1:
That isn't the latest kernel. The one giving softboot and BT issues is 20161126-1805, which is from the latest nightly build. The test builds jcadduono linked are technically the latest kernels available, which fixed BT but still had softboots.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] smr404:
My mistake. I'll go edit my post.

So 1955 isn't the latest kernel but I can confirm it doesn't suffer from softboots, battery issues, or bluetooth issues.

Edit: Roughly 35 hours on 1955 so far. No softboots yet.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] jcadduono:
please try https://build.nethunter.com/test-builds/lge/ (bt-test2)

i disabled KCAL driver
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] young0ne:
Hey I'm on your bt-test1 and for about an hour I haven't had any reboots or anything out of the ordinary KCAL still works still able to change things so . I was looking at my live log and it didn't give any major flags as an issue with the display driver I'm on a non modify stock rom. I will continue to monitor through out the next couple of hours
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] NotATreoFan:
Flashing this one now to test. Will report back on reboots and if I lose SuperSU again,
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] smr404:
I just flashed US996 bt-test2.

Bluetooth works.

I didn't lose SuperSu.

Haven't gotten a softboot yet.

So far so good! I'll be giving an update later.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] LvDisturbed1:
H918 bt-test2 still causing softboots for me. I'll try and get logs on the next one, but so far they don't really seem helpful.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] NotATreoFan:
Didn't lose SuperSU on Test-2 kernel, but still getting softboots. They're not happening around every 10 minutes, up from the 30-45 second intervals last night.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] LvDisturbed1:
A few logs as promised. logcat.txt was running in background to get logs BEFORE softboot. logcat2.txt has logs immediately after.

Edit: Damnit, I might have trimmed to much in logcat.txt.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] smr404:
Just checking in to say that I am yet to get a softboot on US996 bt-test2. It's been about 3 hours. I'll update this post if I get one.

Edit: got a softboot. They only happen when the screen is locked. I was using the device for a continuous 4.5 hours and never got one. Then overnight the same issue I described earlier happened. The phone turned itself off. I think it got too hot and it turned off to protect the hardware. Not sure tbh.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] jcadduono:
okay... bt-test3 is just 3.15.3-20161125-1955 with iptables extended configs and kcal

https://build.nethunter.com/test-builds/lge/

i guess we've ruled out kcal, so iptables changes is what's left, i doubt that could cause reboot problems

i'm left to think it was the verifiedbootstatus patch lol
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] LvDisturbed1:
I'll flash now. Will report findings.

Update: More softboots. 23:34:12.717 is start of crash. Hopefully some of this is of some use.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] ZDeuce2:
[MENTION=5672995]jcadduono[/MENTION], would it be too much trouble to ask if you could post a stock kernel .zip , I lost my original back up, and need to check out a couple things on stock... Any help would be greatly appreciated.

Common sense isn't all that common
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] jcadduono:
h918: https://build.nethunter.com/misc/h918/

be sure to flash no-verity-opt-encrypt after flashing (flash image on install page -> boot)

i don't have us996, nobody has volunteered to let me gets backups of their unmodified device yet

[MENTION=831787]LvDisturbed1[/MENTION] ok now im really convinced its due to missing CONFIG_NETFILTER_XT_MATCH_QTAGUID=y and now looking at the cfg option that completely makes sense! :) kinda missed it getting disabled when i enabled MATCH_OWNER

update: try new kernel build @ https://build.nethunter.com/nightly/3.15.3-20161129-1413/ :)
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] ZDeuce2:
Thank you sir...

Common sense isn't all that common
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] LvDisturbed1:
It was pretty good for awhile, but I got a softboot again. Unfortunately I wasn't running logcat in background to capture logs before softboot. I went a good 6 hours or so before it crashed. Timestamp of crash is 19:35:07.858.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] jcadduono:
logcat only shows after crash, no idea what cause is without other half of logcat :( the processes dying are just a result of softboot
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] LvDisturbed1:
Figured as much, but I wasn't running logcat in background so didn't get those logs. I will this time around for sure though.

Edit: Just learned about the -r and -n options for logcat. I was concerned about file size, and this takes care of it. Might have been obvious to some of you, but I'm still learning. Overall it seems much more stable. Only had that one softboot so far in 10 hours or so of moderate use.

Update: 5:06 a.m. and still no more softboots. Going to pass out now.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] tnick84:
Just now had random reboot watching video through fire fox browser

Build: kernel-nethunter-h918-nougat-3.15.3-20161129-1413

http://cloud.tapatalk.com/s/583ef87c386b3/logcat.txt

http://cloud.tapatalk.com/s/583ef864f0705/last_kmsg.txt
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] jcadduono:
looks like your issue happened at 10:48:23 but your logcat is from a minute or so after that so nothing there, you are pulling all logs from /sys/fs/pstore immediately after reboot? its weird, it should create 2 logs after each crash, one before and until the crash and one after
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] tnick84:
Delete

---------- Post added at 01:36 PM ---------- Previous post was at 01:34 PM ----------

@jcadduono I was able to get another reboot but no logs are available

Here is the scenario that I recreated

- about 5-7 apps running in background

- auto brightness enabled while outside (florida)

- played same exact video (YouTube video) linked to website through firefox browser

- mobile network data (no Wi-Fi)

I'm not sure if that helps but its the best I can give you without logs

---------- Post added at 02:04 PM ---------- Previous post was at 01:36 PM ----------

On another note:

I modified kali boot animation to 1440x2560 instead of 1080x1920. It was really annoying me lol feel free to throw it into next build if you like

https://drive.google.com/file/d/0BwE3q_r0FZ7-RTR3ZHhldVVJVms/view?usp=drivesdk
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] LvDisturbed1:
Please try:

logcat -v time -f /sdcard/logcat.txt -r 512 -n 2

If you can recreate softboot, this should get you logs. It will continuously write logs between 2 files up to a max of 512kb each. The files will be overwritten as needed and should continue until you stop it from terminal with ctrl-c or on reboot.

Edit: Where did you pull last_kmsg from? I thought it was moved in marshmallow and above to /sys/fs/pstore/console-ramoops. Which reminds me...

[MENTION=5672995]jcadduono[/MENTION] That log doesn't seem to generate for me on softboot. Also, no other log seems to generate at that location for me. Still no other softboots other than the one yesterday.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] smr404:
Sorry if if this is redundant or unhelpful. 3 or so days ago I was running the bt-test2 kernel and had softboots occasionally (every 4 or so hours). So I reverted to 1955 and I haven't had a softboot in ~ 51 hours. Just thought I might point it out since I'm sure you've all moved on from that version.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] LvDisturbed1:
https://build.nethunter.com/nightly/...20161129-1413/

So far this seems fairly stable. I had one random softboot 7 hours after I flashed it, but havent had one since. Over a day and a half without softboot.

I recommend installing new kernal and running logcat continuously for a few days in case you get one. Use nethunter terminal and type

logcat -v time -f /sdcard/logcat.txt -r 512 -n 2

Actually try new build. I haven't tested yet.

https://build.nethunter.com/nightly/3.15.3-20161201-1343/
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] jcadduono:
same build i just triggered it for the new oneplus 3T build, you can see changelog at the top of each page
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] LvDisturbed1:
Still no more crashes on my end. How is everyone else faring?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Torridred04:
Been using the 1955 version for a few days and have had zero softboots. Only 2 issues I've noticed is my Gear S3 randomly disconnects throughout my day (simple switch off & on of Bluetooth fixes it) and my SD cards not being read properly (says corrupted). Battery life and features have been superb! Running on stock rom.

Will try updated versions tonight. Thank you for all the hard work on this!!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] :
Calibrated my v20 using a spyder4 thanks to op's kernel:

Red:256

Green:242

Blue:202

Brightness: 58%/125cd/m2. Accuracy will decrease as you increase/decrease the brightness, not by much, but still a good thing to know.

While it's not 99.99% perfectly calibrated srgb I'd say it's good enough for everyday use. Best I can do without trying thousands of combinations.