yashsingh1/xdaforums huggingface dataset:
[T-Mobile LG V10 Android Development] pedrazamarcos:
Same wifi problem here,saved but not connected.3 different wifi's,I will upload logs to my drive and send you the link

I have 3 different phones that I have used many different roms and i never have this issue,they all connect to both wifi without any issues.

My wife and my kids phones(3 in total) also connect without any problems.

As soon I re-install H90130c_00_0914.kdz wifi connects.
[T-Mobile LG V10 Android Development] ninjasinabag:
To the individuals having wifi issues, are you starting from a clean slate? Just the rom and gapps?

[MENTION=7228928]johngalt1[/MENTION]

The memory fix, is that associated with the booting into recovery issue I had?

Nope. New version doesn't even boot.
[T-Mobile LG V10 Android Development] pedrazamarcos:
I do a factory reset,install rom,install Gapps ,wipe davik (sometimes i have boot without wipe davik) boot and when i try to connect wifi it says Saved but there is no connection.

I have tried factory reset,install rom and boot without gapps just to test wifi but is also a no wifi conection.

If i do a factory reset with this rom it always end with twrp boot loop (always boot into TWRP) (i saw the adb command but have not used)
[T-Mobile LG V10 Android Development] pedrazamarcos:
There is a new build you may want to try,and post back results about wifi
[T-Mobile LG V10 Android Development] SparkyKitty:
I can confirm that wifi on both 2.4 GHz and 5 GHz attempts to connect but fails.
[T-Mobile LG V10 Android Development] famewolf:
[MENTION=7228928]johngalt1[/MENTION]

Very impressive work!
[T-Mobile LG V10 Android Development] SparkyKitty:
Other than the wifi not working, it is pretty good. I like it, and xposed with magisk all works perfectly on it too. A huge thumps up :3 :good: :)
[T-Mobile LG V10 Android Development] johngalt1:
Damn, another one without wifi! I merged kernel fixes for the only thing in your logcats I saw for wifi, so could one of you with the issue please do the following?

Reboot

Try connecting to wifi

Run adb shell

dmesg > /sdcard/dmesg

Upload /sdcard/dmesg to a site like vomitb.in

As far as fingerprint goes, I've moved onto trying to get a custom HAL working (based on Sony's open source HAL). This way, we'll be able to use the current binderized calls like on some other oreo shipping devices.

In its current state, fingerprint gesture support may also work if we add support for it.

I've been unable to get magisk modules working personally (why in OP I say modules may not work). What magisk version did you flash, and how? I'm also using xposed, but not systemless because of my issue.

Edit: there's a wifi shim that's used on lineageos the g4 guys disabled for cypheros. I don't see a difference with the shim built, so I'll include it on the next build in case that also fixes the issue for you (but dmesg may still help).
[T-Mobile LG V10 Android Development] SparkyKitty:
I flashed the Magisk v16.0 and seems to have no problems. Flashed it through TWRP after the ROM and Gapps were installed.

---------- Post added at 03:38 PM ---------- Previous post was at 03:30 PM ----------

Also here is the Dmesg: https://vomitb.in/FxYbZ9Jwez :)
[T-Mobile LG V10 Android Development] johngalt1:
Thank you. Unfortunately I don't see anything in dmesg either, so in next build I'll have that wifi shim included to see if that helps. If not, I think the next step is comparing /firmware/ (modem) from a nonworking device to working.
[T-Mobile LG V10 Android Development] johngalt1:
New test build for the users who have no WiFi: https://www.androidfilehost.com/?fid=818222786056029155
[T-Mobile LG V10 Android Development] SparkyKitty:
Just now tried it, wiped everything and installed the update and wifi still does not work sadly. Though I did however see the MAC address for the WiFi is "00:00:00:00:00:00". Same symptom of attempting to connect then says "saved".
[T-Mobile LG V10 Android Development] pedrazamarcos:
wifi saved but not connected

does not detect sim card

MAC address for the WiFi is "00:00:00:00:00:00"
[T-Mobile LG V10 Android Development] johngalt1:
Thank you for testing. I'm going to make sure no wifi related fw is being loaded from /firmware/, and if so move it to /system/. At this point it's all I can think would cause this.

For now reboot and it should be good (random on boot and even with the work by kessaras and steadfasterx not 100%). Kessaras recently said he got radio with newer blobs, and just had to do a shim for LTE support before merging. So the good news is we should soon have fully working radio that doesn't have these bugs or hacks.
[T-Mobile LG V10 Android Development] famewolf:
Any of the current methods to allow dual booting (multirom is an older version but there was another more widely supported to dual boot) available where we could help test the rom and still keep a stable daily driver? I use bluetooth alot in my vehicles and connecting to cordless handsets at home (cell phone only) so not something I can give up yet.

Would any of the V20 and V30 fingerprint code help as some of them already have oreo rom's?

https://www.xda-developers.com/dual-boot-on-android-a-power-users-holy-grail/
[T-Mobile LG V10 Android Development] pedrazamarcos:
I managed to connect to wifi.... this is how i did it,

Thanks to SparkyKitty, he mentioned that his wifi mac address is 00:00:00:00:00:00 I noticed that mine i was also all zeros.( 00:00:00:00:00:00)

I reverted back to my stock rom and i wrote down my wifi mac address 00:9x:4c:xD:xx:xx......etc (you don't need to do this but i taught was good to write my mac address)

I installed the previous build (aoscp_h901-6.0.0-CBNP.8102.05.05052-unofficial) because with the latest did not detect sim card...NEVER! neither wifi worked

So,I installed (aoscp_h901-6.0.0-CBNP.8102.05.05052-unofficial) and then installed Magisk 16.0

Then i installed the App "Wifi Mac Changer_v3.6_apkpure.com" https://apkpure.com/wifi-mac-changer/com.wireless.macchanger

and proceeded to open the app and change my wifi mac address (i input the real original number from my phone,but it doesnt matter because the app DOES NOT CHANGE THE ADDRESS PERMANENTLY)it will go back to the real number as soon as you boot,you need to change the number every time after you reboot until a fix is made.

I think the wifi issue with this rom is that the wifi mac address is all zeros
[T-Mobile LG V10 Android Development] johngalt1:
Off the top of my head, we'll need kexec support in kernel, but I'll look into this when I get back to oreo. Given the Bluetooth issue, I've decided to do a cypheros nougat build. This will give us fully working Bluetooth as well as better RIL (radio). It may also give us fingerprint. It should give users in your situation a better daily driver until oreo is fully functional. I'd do lineageos, but something in their source causes the graphical glitches on first boot from the second display hack to persist.

Regarding fingerprint, there's a chance we may never get it functional on oreo. Our driver is a crucialtek variant that no other fpc1020 devices use, and frankly the qseecom enrollment error is nothing that other devs have seen before. At the very least, we can use fingerprint gestures on oreo.

On another note, do you know of anything different between your full v30c zip and the kdz? The users who have the wifi issue seem to have all flashed the kdz, whereas I flashed your zip from MM.

Also, would you be interested in working on bringing the USU unlock to v10? With a bit of work it should work, and allow the unlocking of other v10 variants. I've been meaning to get to it but just don't have enough time.

The fact this works has given me something to test. Thank you!
[T-Mobile LG V10 Android Development] famewolf:
I literally extracted the kdz into a dz and then the individual image files then put together a zip that flashes each to the appropriate partition with the following exceptions (I mounted system under linux, removed the recovery-from-boot.p file then removed the recovery.img from the file and did not overwrite recovery). It should be identical in handling otherwise.

I knew nothing about the USU unlock method until you mentioned it. I read up on it here: https://xdaforums.com/g4/general/unlock-unlock-lg-g4-device-usu-t3760451

I'd have to do more reading to figure out exactly what they are doing and what would have to be changed. The G4 is probably the closest "sister device" to our V10.

With the risk so high of perm bricking these other devices I don't have in my hands I don't think I'd be comfortable with it, nor am I sure my skill level is adequate. I've stumbled along but you clearly have a much better grasp of things. That said I'd still try to help as I could and am willing to do some reading...I do however use linux 100% so if the tools required use windows it will be more of an issue.
[T-Mobile LG V10 Android Development] SparkyKitty:
I may have to add in that charging does not work. It is not all the time but it happens when you dont expect it like right now I plugged my phone in the wall charger and then tried computer, both does not charge, but on computer the device is recognized. More strange thing is It says "Last Full Charge: 239d 4h 37m ago" which is not right but would be nice to have a battery last that long :P
[T-Mobile LG V10 Android Development] johngalt1:
I've noticed this recently as well, but as far as I can tell it's only the indicator that doesn't show up. I've had it "discharging" with the percentage going up on the charger. Even in these situations, it still fast charges for me.
[T-Mobile LG V10 Android Development] SparkyKitty:
Ahh Alright, that makes it more relieving to hear. :laugh:

---------- Post added at 03:56 PM ---------- Previous post was at 03:21 PM ----------

Well I can now say the SIM card is not getting recognized now. It was before, hmm.

---------- Post added at 04:16 PM ---------- Previous post was at 03:56 PM ----------

This does work luckily since :3
[T-Mobile LG V10 Android Development] johngalt1:
I deleted that test build due to the sim issue. Now I see why it was reverted.
[T-Mobile LG V10 Android Development] SparkyKitty:
Luckily I do have the 050518 build on the SD card, right now I am reverting back to that for the time being.
[T-Mobile LG V10 Android Development] SparkyKitty:
I have noticed that my V10 tends to get really hot to the touch as well as fast battery drain. This was all just by texting for a few minutes nothing heavy running or anything. No idea what it is but its a problem that I need to resolve. It also feels somewhat slower too but GG it gets very hot when I am just texting or just navigating through the OS.
[T-Mobile LG V10 Android Development] ninjasinabag:
My recommendation for this is to use a kernel manager app, turn off the two big cores. (Make sure they stay inactive)

Knock down the top speed on the little cores somewhere in the ballpark of 1900mhz.

Gpu doesn't need much management besides knocking the speed down to around 400.

BTW don't forget to switch the CPU governor to something heat friendly, I personally stuck with ondemand.
[T-Mobile LG V10 Android Development] johngalt1:
You may have hit a bug with RIL. You can check by running top in adb shell and seeing if rild is at the top of the window. The g4 guys have done a bit of work on it since the last build, and I'll include them in the next Oreo build (after I do a nougat build which won't have this issue, and will also have fully working BT). If this is the issue, you can work around it by using the RIL reset app linked in OP for now.

I can also build the Titan kernel (not default because it was jittery for me compared to our CAF kernel). It may get better battery life and be a bit of a trade-off. It will be a boot.img you can flash from recovery.

I'm hoping to have a nougat build (and manifest for any other devs) this weekend before moving back to Oreo, but real life has been crazy for me recently.
[T-Mobile LG V10 Android Development] SparkyKitty:
I have tried the Ril control app but seems like it is not making much difference, I tried turning off Ril and then turning back on but still the problem persisted. Last night I was using it and the top part of the phone above the battery actually burned me. I do think that the custom kernel would help the battery as well as keeping the phone cooler, I have tried putting the CPU governor to powersave but no difference and the minimum CPU frequency was set at around 800 MHz by default and couldnt change that too. Hopefully the nougat build with custom kernal would be alot better because I want to use my v10 again. And I do understand how life can be an obstacle for us all, no worries :)
[T-Mobile LG V10 Android Development] pedrazamarcos:
Try flashing stock kdz rom ,lock bootloader and sell this "developers forgotten device",

then buy a Le Max 2 so you can root,install any of many roms available https://xdaforums.com/le-max-2/development

unfortunately the developers have decided not to support this device and that and the bootloop problem have doomed this device.

Huge thanks to runningnak3d for his awesome work on root https://xdaforums.com/tmobile-lg-v10/general/root-h901-nougat-t3773942

Big thanks to Johngart1 for his support and work on his rom,I hope this rom get completed some day and the wifi,fingerprint,battery charge indicator and second screen get fixed and some day this rom can be stable,but for now,i have a mint condition white H901 for sale for $120
[T-Mobile LG V10 Android Development] SparkyKitty:
Time will only tell for this device, but I know there can be improvements, we just have to try and test. I saw something that the Nexus 4 still is being supported despite the device is older than the V10.

Hopefully the bootloop problem was fixed, Lately I had no problems with that but still, the v10 is a good device and having an unlocked bootloader with TWRP is a huge advantage over the s8+ I have. And I do appreciate and thank johngalt1 for supporting the v10 to this very day,very great honors.
[T-Mobile LG V10 Android Development] johngalt1:
As far as this device goes, I picked mine up in mint condition for $90. The boot loop issue has good workarounds, still giving a solid quad core device (if needed) with a swappable battery (external charger pack + spare battery for $25 here), and expandable storage (256 +64G woo). In my opinion -- even leaving the second screen out of it -- this still makes for a good budget device. We can also probably get P when released with similar bugs as current Oreo.

In terms of fully functional, I'm confident we can get this on nougat at least. Regarding fingerprint, there's a good chance we won't get this on Oreo. For Bluetooth and RIL issues, we're tracking the work done on G4, which has the exact same issues we do. Kessaras had stated he's planning on testing g5 oreo audio blobs when they come out in hopes it might fix the BT issues (which don't exist on nougat).

As far as second screen goes, we can use whatever solution is used for v20, but again this isn't something with a timeline or to hold breath over. I like the idea of treating it as a notch with the screen on, but with blacklight bleed on v10 this causes issues.

Also pushing back my nougat goal to Monday.
[T-Mobile LG V10 Android Development] johngalt1:
nvm, fixed*
[T-Mobile LG V10 Android Development] NYLimited:
I'll wait a while longer - at the rate prices are dropping they'll pay me to take one pretty soon! :D
[T-Mobile LG V10 Android Development] pedrazamarcos:
Did you fix the wifi and battery charging indicator issue?
[T-Mobile LG V10 Android Development] johngalt1:
New oreo testbuild with very minimal testing. Not editing OP due to amount of testing needed. Changes:

- Various G4 changes

- Reverted kernel to 100hz for potential battery improvements Needs testing (also look below).

- Various audio changes. ACDB ids are imported from v30c blobs. Needs audio testing.

- Synced with upstream CypherOS

Build: https://www.androidfilehost.com/?fid=746163614322264597

Boot.img test with Titan kernel. May improve battery life but also may be jittery. https://www.androidfilehost.com/?fid=674106145207487019

Probably not.
[T-Mobile LG V10 Android Development] johngalt1:
I seem to be getting far better battery life with the Titan kernel on defaults. BTW, remember to reflash magisk after flashing the boot image. I'm interested in opinions on it, because I'm leaning toward making it default and attempting to merge in CAF.

So far on a very worn battery:
[T-Mobile LG V10 Android Development] johngalt1:
New build uploaded in OP. Fingerprint is now working ???.

Changes:

- Working fingerprint.

- Ruthless launcher updated. You will lose layout, but now have the ability to install any pixel launcher alongside.

- Using Titan kernel by kessaras now. This isn't quite as buttery smooth, but battery life is significantly improved.

- Audio changes reverted from test build (still working on them in audio-rework branches)

- Synced with upstream CypherOS (new security patch).

The G4 guys are also hard at work on the Bluetooth calling issue.
[T-Mobile LG V10 Android Development] amoot329:
Is there an alternate kernel that I may flash if I'm not worried about the battery life? I have the zerolemon battery so rarely needs to charge it (maybe once every 3 days) if not then I will certainly give this a try.

Happy to hear about the fingerprint solution ?
[T-Mobile LG V10 Android Development] johngalt1:
I'll upload a boot.img tomorrow with the other kernel ?

Edit: Unfortunately that kernel has issues with fingerprint. I'm working on fixing it, but until then we'll have to stick with this (or something closer to the stock v30c kernel).
[T-Mobile LG V10 Android Development] amoot329:
That's okay, did flash it late last night. Haven't had much of a chance to test it out yet. Been pulling a lot of overtime at work. Probably try tmrw when I have more time. Fingerprint is fairly useful for me so will stick with this Titan kernel for now. Yes the flashing setup/intro is still there but goes away once you're in the home screen. May I suggest an epilepsy warning in the description?
[T-Mobile LG V10 Android Development] johngalt1:
Will add one.
[T-Mobile LG V10 Android Development] johngalt1:
New build uploaded. Changes:

- WiFi Tethering now working (ty kessaras)

- transparent hugepages enabled in kernel.

- CPU sets enabled in kernel.
[T-Mobile LG V10 Android Development] ninjasinabag:
I've effectively given up on trying this out. The rebooting into recovery issue happens every time for every new build, regardless how many times I put that code in.

Gonna go back to stock.

Good luck getting this 100%. Loved what I saw when I did see it.
[T-Mobile LG V10 Android Development] johngalt1:
That's too bad, and I say that as someone that runs it as a DD with the only issue for 100% being BT calling now. If it's happening that often, then it's likely another issue. This happens mostly on LG devices (even newer) when they hang on boot too long. In all the builds I flash (probably 10x as many as I upload), it's been well over a week since this happened and it was caused from another issue I introduced that was stopping me from booting.

In some of these builds, there's a chance some changes may have required dalvik cache wiping for dirty flashes which may have been the issue for you (don't know without a log). Depending on what you were running prior, it could also be that changes in the Titan kernel don't play well with your device (given stuff like voltages changes, it's also possible).
[T-Mobile LG V10 Android Development] ninjasinabag:
I've figured out what it is, but it's out of my league to fix. As soon as you said it's usually due to a boot hangup, mine doesn't really wait for the boot sequence. I hit the power button, get the unverified boot warning like usual and then it jumps right into recovery.

Phones refurbished, so I just opened it up real quick. For some reason the GPU is running cold.

Okay, not so out of my league. I used small non-conducting springs to make a little room between casing and motherboard where the plastic was starting to pinch. The casing is screwed together a little loosely now, but the SoC isn't gonna move because of it.

(Edit level 2)

First boot with modifications went to recovery, buuuuut there was a small delay in between unlike before.

Tried the code you provided before and it's currently booting.

Also noticed that magisk says the rom already has a previous root solution built in that isn't active. Is that something to worry about?

It's fully booted. Everything is 100% cool from boot screen to home screen. Yassss

(Edit 3)

Rebooted successfully.

My bad for the edit spam.
[T-Mobile LG V10 Android Development] johngalt1:
Re: magisk, there's nothing to worry about. That's interesting -- I'm glad you figured it out! :good:

On another note, something I found that can cause boot hangs for others: this titan kernel seems to be a bit more likely to cause corruption on hard power off than our CAF kernel (have been forcing it to compare). I just found the issues with 1) stuck on performance mode with our CAF kernel, and 2) fingerprint with our CAF kernel, so I'll be switching back to it for the future builds and offering titan kernel as an addon to anyone who wants to use it instead. Battery life should actually end up being close on our caf kernel now so it seems like a sane default.
[T-Mobile LG V10 Android Development] ninjasinabag:
The stuck on perf issue is actually alright in some cases. Disabled the big cores and let the littles do the rest. Just keep them as is on clock speed and if possible either lower the voltage or use VDD restriction from the thermal settings in any kernel app. Vdd does the work that manually editing voltage would. Which should impact performance very little while keeping heat and battery use stable.
[T-Mobile LG V10 Android Development] johngalt1:
well, we haven't had the issue since switching to the Titan kernel which is very conservative in it's governors (tuned conservative on big cores and blu_active on little cores). Due to basing the device repos off cypheros g4 trees, we were using a post-boot script that set titan kernel settings even on our caf kernel, which would then use all performance governors.
[T-Mobile LG V10 Android Development] johngalt1:
New build uploaded. Reverted back to our CAF kernel with fixed performance gov only bug and working fingerprint (CAF crypto reverts). Should now be close for battery life to Titan kernel with better performance.
[T-Mobile LG V10 Android Development] amoot329:
With the change in kernel, dirty or clean flash recommendation?
[T-Mobile LG V10 Android Development] johngalt1:
Dirty should be fine. My testing has been all dirty flashing unless there are issues.

Edit: I forgot to mention if you have fingerprint issues from the kernel changes, delete one pre-existing fingerprint and it will work again ?.
[T-Mobile LG V10 Android Development] johngalt1:
New build uploaded. Changes:

- Synced with upstream CypherOS.

- Added DRM HIDL

- Continuous TRIM enabled

- Kernel: Updated to 3.10.104 so far

- Kernel: Cpu-boost changes, better with big cores.
[T-Mobile LG V10 Android Development] ninjasinabag:
Day 3 of using the latest update and daaaaaaaaaamn. First time I've seen the phone hit deep sleep.

I've been letting the phone sit at standby testing out the battery drain since first install and sign in. Started out at 90% and dipped to 88% over that time. Compared to the 30% loss I would have suffered by default over a couple hours.
[T-Mobile LG V10 Android Development] rasniker:
I got the problem with wifi...any solutions?
[T-Mobile LG V10 Android Development] pedrazamarcos:
Temporary fix:

Install the App "Wifi Mac Changer_v3.6_apkpure.com" https://apkpure.com/wifi-mac-changer/com.wireless.macchanger

and proceeded to open the app and change my wifi mac address ,the app DOES NOT CHANGE THE ADDRESS PERMANENTLY)it will go back to the real number as soon as you boot,you need to change the number every time after you reboot until a fix is made.

Permanent fix (This is the one i did,works perfectly!)

Flash stock kdz ,lock bootloader and sell the V10