yashsingh1/xdaforums huggingface dataset:
[LG V20 Guides, News, & Discussion] ezzony:
@Ascii3​

Your problem seems to be you do not understand what 'stock' means. All it means it that STOCK = ORIGINAL kernel that comes with the phone. Our Custom Kernels are modified original kernels and all that is detailed already in our threads.

Finally, there is going to be no more development for these kernels as this is quite old phone, so whatever you experience you are stuck with it. Buy a new battery if you have serious battery drain issues.
[LG V20 Guides, News, & Discussion] Ascii3:
@ezzony

Thank you for affirming.

I would clarify that I do not believe that I am not having serious battery issues. I brought up the point of the battery in my last posting in this thread simply to describe my observed performance and thought it a useful point of feedback, particularly because it was a point of comment somewhere earlier in this thread.
[LG V20 Guides, News, & Discussion] xdasree:
@ezzony

Thanks a bunch for this kernel. I have strange issue with stock. with stock, HDMI display out not working for all output devices. Like works for one monitor for others don' t. It says connected to secondary screen but no video signal. after patching this kernel (oreo), boom it works. is there any build.prop setting or something that stopping video signal. ?
[LG V20 Guides, News, & Discussion] ezzony:
You are welcome a bunch :)

No I don't think build.prop will affect much really.

Is everything working fine for you now?
[LG V20 Guides, News, & Discussion] xdasree:
Yes, everything works well. I'm just using my v20 as media player/streaming only. Just wondering since there's no "pie" versions available for my h918 variant , Can I use your pie kernel on linage OS pie.

I've tried LOS 18.1 but HDMI display did not work. just thinking with your pie kernel with LOS 17.1.
[LG V20 Guides, News, & Discussion] ezzony:
No ezv2020 is for stock only. Won't work on LOS.

I'm on Lighthouse Rom now, stock on my second spare phone. I'll see if hdmi works on Lighthouse later. Or maybe if it doesn't we can get it to work. Maybe.
[LG V20 Guides, News, & Discussion] ezzony:
My hdmi hub works on lighthouse

Project Lighthouse Downloads
[LG V20 Guides, News, & Discussion] xdasree:
Just flashed Lighthouse. no luck for me on video out. It doesn't even recognized usb-c. no vibrate/input accepted sound.

I didn't port gapps yet. I hope It's nothing to do with gapps..right
[LG V20 Guides, News, & Discussion] ezzony:
Oh Damn. Well, since it works for you on Stock then I would say the most likely reason for your problem is the model of hub you are using.

One last try you could try this one, (aosp extened), if not I'd go back to stock.

File folder on MEGA

mega.nz
[LG V20 Guides, News, & Discussion] xdasree:
OK., I'll try that and report back. As I said before, it didn't work even with stock. After flashing ezV2020 kernel. It worked.

Another strange thing is it worked for all other monitor/projector, but not withTHE one always have problem.

Btw i should mentioned this before, I'm using usb-c on both ends not hdmi.

It accepts usb c as video input. Yeah cable is good.. worked with all my laptop, note 10 and all other devices which allows usb c alt mode.

All my reaserch leads to something something to do with kernel which led me to port ezV2020. and It worked ☺

Anyways I'll try that.... thanks again
[LG V20 Guides, News, & Discussion] askermk2000:
Where you using an older stock rom then? Since ezV2020 is supposed to be near stock, then I guess it was using the latest official sources from LG,

which then likely was newer than what you where using... IDK but I have here my kernel for custom rom. I've been working on lately, for LG G5, but

I have facilitated V20 as well. So I did a quick compile so you can try that. There is also gamma kernel for V20 series.

TLDR: Try my new kernel for custom roms (not stock/official roms).

Removed -- this was a beta with known problem. If desired I can upload for V20 variants when issues are resolved.
[LG V20 Guides, News, & Discussion] xdasree:
Thank you !

unfortunately, no luck with it too.

one thing I've noticed is that, I've set hdmi rotation to true in build.prop with kernel manager and rebooted. Now the moment I plugged in USB C, phone display rotating to horizontal automatically but NO video signal/display. Same thing happened to stock (oreo) as well until I flashed ezv2020.
[LG V20 Guides, News, & Discussion] el-sahef:
Hello ezzony,

I am using your kernel since it became available and had no issues with it so far, it is working great. I know that the purpose of your kernel is to be as close to stock as possible without adding a ton of features or enhancements that might cause problems and I appreciate this orientation. However, the one thing that is missing for me is init.d support.

I need it to use the "fix startup leak" option in afwall+. Would you consider adding it to your kernel?
[LG V20 Guides, News, & Discussion] ezzony:
I'll consider it. Are you on Oreo or Pie and what variant v20 do you have so that if I make it you can test it.

Edit: are you sure this is a kernel thing?
[LG V20 Guides, News, & Discussion] el-sahef:
I'm on H990DS Oreo. I'd like to use Pie but I need mobile data and calls to work so as long as this is not sorted out I can't use it.

The folder /system/etc/init.d is already present but scripts in this folder are not executed according to this test: https://sangams.com.np/add-init-d-support-android-kernel-rom/

If the provided information is correct init.d support is part of boot.img

In the wiki for afwall+ it says that the kernel would need some kind of busy-box:

init.d

AFWall+ (Android Firewall +) - iptables based firewall for Android - ukanth/afwall

github.com

That's all I know.
[LG V20 Guides, News, & Discussion] ezzony:
Okay. So as I suspected it's not part of the kernel, it's part of the "ramdisk". The boot.img is not just a kernel it is a kernel+ramdisk.

The changes have to be made in the ramdisk, not the kernel.

You need to extract your H990DS boot.img (which I don't have) using Android Image Kitchen, and add init.d support to the init.rc file in the ramdisk.

To get the boot image you can back up the boot image only in twrp, it will be called boot.emmc.win. Rename that file to boot.img, put it in the Android Image Kitchen root folder and extract it using unpackimg.bat, make the changes required in the init.rc file in the ramdisk folder, and then repack the boot image using repackimg.bat which recreates a new modified boot.img you can flash back using twrp.

That is actually quite straightforward. The only think I don't know is if those instructions, the code you need to add in the init.rc file, will actually work.

#!/system/bin/sh #added init.d support export PATH=${PATH}:/system/bin:/system/xbin mount -o remount,rw -t auto /system chmod -R 755 /system/etc/init.d mount -o remount,ro -t auto /system logwrapper busybox run-parts /system/etc/init.d/

I would suggest searching xda as I wouldn't trust that website you linked to.
[LG V20 Guides, News, & Discussion] el-sahef:
After reading a bit further I tried to add init.d support to the ramdisk but found out during the process that no one does this any more since magisk provides the ability to start custom scripts on boot. They have to be put into /data/adb/service.d

After placing the afwallstart script into this folder (script file has to be executable) all traffic is blocked until AFWall+ starts up and loads the configured rules for iptables.

Sorry for the confusion on my part. The documentation of AFWall+ is not updated in that regard and mentions only the old init.d method.
[LG V20 Guides, News, & Discussion] ezzony:
No problem. I had a feeling something like that would be the case.
[LG V20 Guides, News, & Discussion] doniedogawa:
My friend had installed this kernel on stock Oreo. And it works well without problem until now.

Thank you bro 🙏
[LG V20 Guides, News, & Discussion] Darnrain1:
@ezzony Hey I just wanted to stop by and say hi. I wanted to thank you for compiling the ezV2020 kernel. It's very very stable and works good. Anyway take care.
[LG V20 Guides, News, & Discussion] ezzony:
Well thank you and I'm pleased it's working out for you. Are you running the PIE or Oreo version?
[LG V20 Guides, News, & Discussion] Darnrain1:
Yeah thank you for asking, I am running Stock Oreo 8.0. I looked into the PIE but it looks like the radio is not working that great on US roms.
[LG V20 Guides, News, & Discussion] liyafe1997:
Do you have US996 PIE Kernel without dirtysanta?

Thank you!
[LG V20 Guides, News, & Discussion] ezzony:
I don't think so i'd have to check. Are you intending to use it on us996 official bootloader unlocked stock Oreo? I think the dirtysanta version will work on it, have you tried?
[LG V20 Guides, News, & Discussion] liyafe1997:
My US996 is official bootloader unlocked but I flashed your PIE ported rom. Your PIE US996 dirtysanta kernel basically works, but the screen is fuzzy during booting and also after booted up. (As same as if you use a stock kernel on a dirtysanta unlocked bootloader). I only can recover the screen by turn it off and on again(seems the kernel will reset the panel by correct parameters).

But if I enabled the second screen on screen off, I have no chance to recover it since the whole panel are always on.

So could you build a US996 PIE regular kernel like your Oreo kernel? It's really helpful for the official bootloader unlocked users.

Thank you!
[LG V20 Guides, News, & Discussion] ezzony:
I'll see what I can do, I'll let you know either way.
[LG V20 Guides, News, & Discussion] ezzony:
^^ This is untested so keep an eye out for issues.
[LG V20 Guides, News, & Discussion] liyafe1997:
It works well, no screen fuzzy!

Thank you!
[LG V20 Guides, News, & Discussion] ezzony:
Sorry I didn't read your earlier post well. I just noticed you said you flashed the Pie Rom. It has been reported it kernel crashes from time to time. Since LOS works well on A11 I wasn't minded to even try to fix it. I have 2 V20's, one with LOS and the other with Stock Oreo with the Pie Kernel that works well, better than stock oreo kernel. You might have to go back to Oreo with the Pie kernel. See how you get on anyway.
[LG V20 Guides, News, & Discussion] liyafe1997:
By the way, do you have any clue where the configuration of the WIFI baud limitation is? Before I flash your F800 Pie rom, I am able to connect to my 5GHz WIFI, whatever on the stock US996 Oreo ROM or LineageOS, but after I flashed this F800 Pie ROM, my 5G WIFI is no longer visible, only 2.4G, but I can see some of my neighborhoods 5G WIFI.

I guess there are some baud limitations of the Korean version OS. Maybe it is just in some configuration files.
[LG V20 Guides, News, & Discussion] liyafe1997:
But actually, your Pie ROM seems works well. I haven't faced kernel crash issues, or, yet.
[LG V20 Guides, News, & Discussion] ezzony:
Once a day or so I was told.
[LG V20 Guides, News, & Discussion] nickb2b:
I'm also running stock Oreo with your Oreo kernel, are you saying I can also try the Pie variant of your kernel (and that it works better)?
[LG V20 Guides, News, & Discussion] ezzony:
Yes, on stock oreo.
[LG V20 Guides, News, & Discussion] nickb2b:
Got an error trying to flash. Guess the pie kernel won't work on my VS995.
[LG V20 Guides, News, & Discussion] xxseva44:
It should, what's the error?
[LG V20 Guides, News, & Discussion] nickb2b:
Had to get my readers out, error shows as corrupt zip file. I redownloaded the file and will try again. Size was a bit less than 7MB but the info says it should be around 11MB?
[LG V20 Guides, News, & Discussion] nickb2b:
Downloaded it again but still getting the corrupt zip error. @ezzony, can you reupload US996Santa_1.1 _exfat_-PIE-ezV2020.zip?

Thanks.
[LG V20 Guides, News, & Discussion] ezzony:
LG_V20 - Google Drive

drive.google.com
[LG V20 Guides, News, & Discussion] nickb2b:
Thanks for the link.
[LG V20 Guides, News, & Discussion] ezzony:
New Pie kernel that will force hifi mode via tile toggle rather than using the mixer path method.

Pie kernels can be flashed on Oreo.

See OP for download link
[8525, TyTN, MDA Vario II, JasJam General] bigjoe87865:
Hi ,

i have an ATT 8525... its used from another guy.... he has told me that the touchscreen will work at random....

as far as i can tell.... when i charge the phone .... the touchscreen stops working... because bof the temperature im assuming.

he told me to remove the battery and let it set there for an hour or 2.. and pop it back in...

voila... the touchscreen is back....

BUT.. it only lasted for about 10min... while the phone was on... it stopped responding again after 10min..... because the phone heated up again to operating temperature ?...

does anybody have any idea what i will need to replace to get it back to normal?

the phone DOES NOT have the common issue that i see everywhere about the top right hand corner being stuck and always closing apps or launching the start menu...

the phone screen just becomes unresponsive.

i have tried loosining up the screws behind the slide... it did not help.
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
This has been reported before:

http://xdaforums.com/showthread.php?t=287824&page=2

http://xdaforums.com/showthread.php?p=2365269

and even if not identical the causes are likely to be the same.

Unfortunately, the same effects of screen not reponding could be caused by different components.

All we can say is that it is likely one of the following:

The d/pad daughter board

a poorly fitting d'pad to screen connector block

The Digitizer/LCD or its flex cable

A fault in any of these - made apparent often when the device is warm or been switched on for 10 or more minutes.

There is no magic bullet here! If you do not have test equipment then replacing these parts (probably starting by checking the d/pad connector) is all you can do. Repair centre's appear to have mixed results with this as well - probably due to it's intermittent nature.

Mike
[HTC Desire 630 Questions & Answers] Saranga_lanka:
Hi,

I was having an issue with my HTC Desire 628 dual sim phone. Earlier it was automatically restart. Then i tried to flash the firmware using SP flash tool and forgot to make a back up. I have selected format all & download option in the flash tool. After that, flashing was succeeded with 100%. But now my phone is not starting up. any thing to do with it. Really appreciate your support.

***Locked***

HTC_V36BML 128 SHIP S-ON

CID-HTC__060

LK-1.01.0000

OS-1.17.400.1

I have used below firmware file name which i have downloaded for SP flash tool.

2PVGIMG_V36BML_DUGL_L51_DESIRE_SENSE70_HTC_India_S EA_1.17.400.1_Radio_0.1524V28P45.0504.0422_1_relea se_504976_combined_signed_2_4.zip

Thank you in advance.
[Samsung Galaxy Fold Questions & Answers] Benji180:
Hi all, has anyone else had a Samsung fold thats middle screen has gone black?.

I have tried to rest it the pin screen on outside is half slide over meaning I can't press Ok.

Any help appreciated as my fold is now useless.

TIA

Benji
[Samsung Galaxy Fold Questions & Answers] liggerz87:
Id get in touch with Samsung see what they can do
[Moto Z2 Force  Questions & Answers] 41rw4lk:
What -05 firmware did you flash?
[Moto Z2 Force  Questions & Answers] urvurm:
I don't even know anymore, it was on a computer that I had to wipe and install windows over in order to try everything I did. The clue in my other computer, which is probably accurate, is NASH_TMO_C_OCXS7.109-51-14-7_subsidy-TMO_RSU_regulatory-default_DEFAULT. I'd be willing to bet that is the firmware that is currently flashed, before it was modified with Magisk v20.4, MindTheGapps-8.1.0-arm-20180808_153837, and either MK100 or MK81 of Mokee. I'm no longer even sure if this firmware is for 05, that's just what the name of some other archive this all got dumped into. It's also the version that the instructions I was following used, before I even knew there were 6 versions.
[Moto Z2 Force  Questions & Answers] 41rw4lk:
NASH_TMO_C_OCXS7.109-51-14-7_subsidy-TMO_RSU_regulatory-default_DEFAULT is the last firmware available for TMO, hopefully whatever firmware you've flashed wasn't a pie firmware.

With a locked bootloader you can only flash official signed same version or newer firmware. I would try to flash that again, your goal is to get a booting system that you can enable oem unlocking in. That will give you more flexibility to solve other issues if needed. However if you've flashed a oie firmware you might be out of luck.
[Moto Z2 Force  Questions & Answers] urvurm:
Well, I looked up that exact filename and attempted to flash the firmware from it. Am I somehow doing this wrong? (see attached -- fastboot version eac51f2bb6a8-android )

https://postimg dot cc/BPq1sbmS

This matches the firmware from the folder I found everything else in, like magisk and some utilities from the first night of this, so it should be the one that's on there. I don't think I flashed pie firmware, unless I installed a ROM that was Pie I think that I only flashed Oreo stuff. (Were they just unable to think of a desert that starts with Q?)

I'm noticing my build fingerprint and blur version correspond with the firmware OCSX.109-51-7/9, which also tells me this should have worked (that firmware also doesn't work). I lost baseband before this happened though ( that's why I locked it, because I thought that would fix it smh), I don't know what does that besides flashing the wrong firmware or really screwing something else.
[Moto Z2 Force  Questions & Answers] 41rw4lk:
I've attached the latest adb/fastboot files and a flashall.bat for TMO. Delete any .bat files in your firmware folder and then extract the attached zip into the same firmware folder. Then try running the flashall and keep track of what flashes and what doesn't. Again the goal is to get a booting system that you can enable oem unlocking on so that you can unlock your bootloader again.
[Moto Z2 Force  Questions & Answers] 41rw4lk:
Try copying the the commands in the flashall one at a time and adjust accordingly.

For example say you post the command fastboot flash logo logo.bin and it returns fastboot: error: Command failed logo__a: not found

You know it's trying to flash the _a slot, which is fine so tell it to do so manually fastboot flash logo_a logo.bin

With a locked bootloader you might get some permissions denied, especially since you flashed the -05 firmware, which might have mismatched a few things. Keep going to the end of your flashall. You need a bootable os so you can get the bootloader unlocked and hopefully overwrite more wrongs and get back to good.
[Moto Z2 Force  Questions & Answers] urvurm:
Well, permission was denied for all slots except for gpt.bin (consistently the only one to work), which I attempted to analyze to better understand the partion table but I think the tool I used was not designed for moto z. Anyway, this is just how it's been. From here, all boot options stop me at the "your software is corrupt you evil hacker anathema to corporate purity"

While I haven't tried it after this round of 100% failed commands, I have used fastboot boot boot.img and been able to enter a dysfunctional wreck of an OS that can almost but not quite get past pixel setup and allow me to edit prefs. Is there maybe a way to bypass setup and edit settings from here? ( It's too broken to launch adb, but it does persist to some degree, I was able to set a pin that remains. It's just infinitely crashing and never makes it past the checkpoint where I disagree to all of tmobiles usage stats agreements,
[Moto Z2 Force  Questions & Answers] 41rw4lk:
I assume you mean the lenovo rescue and smart assistant tool. With a mismatch system it might not recognize the phone (which is moto z 2nd gen for the record).

I'll attach a both slot flashall, maybe the other slot can be sorted a little better. For what it is worth, you might boot to recovery and do a factory reset 1st. Then try the other flashall. You might just be out of luck, but it's worth trying a few things before you call it. Same deal with this flashall too, if you need to manually go line by line do it. Also, when it's all said and done, try another factory reset from recovery if needed.

If you see the no command dead android in recovery, just hold pwr and press vol up to get to the actual recovery.

I just seen your edit, no way to get past setup that I know of. Another user tried forever to find away, but I don't think they did. Also, I wouldn't set any screen security until you're in a clean state. It will only hinder what you're trying to do.
[Moto Z2 Force  Questions & Answers] urvurm:
I was actually referring to this: https://androidforums.com/threads/guide-how-to-create-partition-xml-gpt.1125433/

To see if I could get a better Idea of the partition names, since even when I set --slot all, I get the (permission denied) instead of (command fail) or whatever.

And you're right, LMSA wasn't able to do recognize it and I think it's because of mismatched firmware. I'm glad someone else has seen this broken boot ing. thing before. I know setting a pin was a bad idea, I just felt like I was running out of options.

I'll try this modified flashall you sent me.
[Moto Z2 Force  Questions & Answers] urvurm:
No dice.. failed uniformly as flash permission denied or permission denied for the erase commands. Tried line by line and got the same result. Only noteworthy things I saw anyway:

#after any flash attempt, with both invalid and valid partition names, I get this:
(bootloader) is-logical:<Insert whatever partition name I just attempted _a, _b either way>: not found

#it always says flash permission denied, unless I try an invalid partion name, like radio
(bootloader) is-logical:radio: not found Sending 'radio' (97459 KB) OKAY [ 3.039s] Writing 'radio' (bootloader) Invalid partition name radio FAILED (remote: '') fastboot: error: Command failed

C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot --set-active=other
Setting current slot to '`' FAILED (remote: '')

I tried booting to recovery from bootloader, holding power+ vol up, and also just booting with power +vol up. I always get to the "corrupted, can't trust" screen. I think it's trying to boot into TWRP but isn't allowed. It's weird though because I remember trying this before and it just restarting the bootloader, but it might have been a dead battery.
[Samsung Galaxy Note 10 Questions & Answers] Ferhenhite:
My proximity sensor is not working while i am in a call. The screen remains black even after i take the phone one my ear. The sensor was perfectly working before one ui 2.1 update. Since i updated proximity sensor is not working anymore. I have already performed a factory reset but still no luck:crying:. Is anyone facing the same issue? If so what is the solution. Please advice.
[Samsung Galaxy S9  Questions & Answers] dayonbochnia:
I have a S9 (Snapdragon) and recently I've installed a custom rom on it. After that, I could notice that my bluetooth connection quality dropped a lot.

The phonecalls in my car's media have a horrible sound quality and I have been having problems with spotify connectivity.

Anyone have a light for me?
[Samsung Galaxy S9  Questions & Answers] TheMadScientist:
I'm gonna assume its us model. Rooting should have no bearing on bluetooth quality. There was an issue losing pairing after reboot but since fixed
[8125, K-JAM, P4300, MDA Vario ROM Development] peterpunx:
I have downloaded different versions of the skype installation files, from the skype web site and other webs but none of those work on my cell I always get one of this two errors

1. This is not a valid pocket pc application

or

2. There are some missing files for running skype (I dont remember the exact message but that is what it said)

I have a HTC 8125 G3 with an upgrade to windows mobile 6.1, a month ago I installed a version of skype and I was working with that with no problem but a week ago I had to restore a previous backup and I lost all my programs and I dont have the skype cab that works for me.

Please can anyone can post a cab of skype that works for my cellphone

Thanx
[8125, K-JAM, P4300, MDA Vario ROM Development] Noonski:
Do you have one of the Cabs that's not working for you?

It might be that it's not set to work with your OS version.