yashsingh1/xdaforums huggingface dataset:
[LG V20 Guides, News, & Discussion] TheIronMaiden:
Phroot suggested to use gamma so I did it knowing it wasnt compatible to prove a point. Lol
[LG V20 Guides, News, & Discussion] phr00t:
Where are you committing changes? I don't see any commits here: https://github.com/Ahrotahn/android_packages_apps_AOSPSignBoard & it says you have no July activity... I was hoping to merge them into my branch, so I can build stuff you guys are working on to test & share.

Ahh, I was hoping the changes were not part of the kernel.

In my build, I think only the android_frameworks_base project, which I forked from Zacharee1, was modified from Lineage for the second screen area? I suppose this becomes part of the kernel? The Gamma kernel is the android_kernel_lge_msm8996 project... do I just need to update my Manifest to pull from oxavelar's android_kernel_lge_msm8996 project instead of straight from Lineage to get the Gamma improvements along with the second screen requirements in android_frameworks_base? I'd like to build a "best of both worlds" kernel.

This is the source for the Gamma kernel for reference: https://github.com/oxavelar/V20-Kernel-Gamma
[LG V20 Guides, News, & Discussion] x86cpu:
Eventually they'll probably be added to the device/lge/v20-common/sepolicy dir. It will exist with new changes going in. That should get them in the correct location. Most device changes should go into that directory.

---------- Post added at 11:04 AM ---------- Previous post was at 10:58 AM ----------

SystemUI plugin.

Lights will be changing:

https://review.lineageos.org/#/c/219308

https://review.lineageos.org/#/c/219307 (this is also where sepolicy gets added)
[LG V20 Guides, News, & Discussion] Phoenix591:
without actually looking at the current experimental kernel (but having looked at the disabling code),the change is simply changing a config setting from a y to an n (or commenting out the line), when the second screen disabling code was created they made it easy to switch off.
[LG V20 Guides, News, & Discussion] phr00t:
It appears the config files are here: https://github.com/oxavelar/V20-Kernel-Gamma/tree/integration/android/configs

... but I can't seem to find one that references the second screen...? Am I missing it or not looking in the right location?
[LG V20 Guides, News, & Discussion] Blaises:
It's all in the frameworks/base repo.

I was placing my sepolicy stuff there originally. The rules were indeed being added, but the definition in service_contexts never worked so the rules that were added were never applied to the service. The service would always be in the "default_android_service" context in the logs. I assume it's because of the wildcard at the end of the base service_contexts, and the sepolicy directory is being concatenated to the end of that one so the wildcard comes ahead of my definition. Do you know how to best handle that, or is there something I'm overlooking?

Oh that's fantastic! There's always stuff like this hiding in the framework it seems.

Yup, I've been following the gerrit and saw that. I'm only using it for a temporary hack, and I shouldn't be using it by the time that is merged.
[LG V20 Guides, News, & Discussion] x86cpu:
For now do the service_contexts how you are, I'll have to check into that to override/add system. I will if that lights is merged adjust the backlight-ex one to not be the same brightness if something else will be controlling that one. Or adjust it based on the OFF/DOZE, etc...
[LG V20 Guides, News, & Discussion] phr00t:
OK guys, I've got another Lineage OS 15.1 build for the H910 (AT&T) V20 that includes all of the latest signboard updates & the Gamma v17 kernel source:

https://drive.google.com/open?id=1MYQSGzWte0cp7zvglABX6lKvx_PWCwqJ

This is very experimental & I admit to not testing it yet myself... but the short story is, I've brought in the source from the Gamma tree in replace of the standard Lineage kernel + the android_frameworks_base from [MENTION=1852121]Blaises[/MENTION]. I had to do a few things to get it to compile, which I'm hoping won't cause problems:

1) I had to add "#pragma GCC diagnostic ignored "-Wmaybe-uninitialized"" to the top of a few include files, because there were a bunch of uninitialized variables in the Gamma source & I couldn't find a nice way of allowing those warnings in the build/Makefiles.

2) I got some errors that there were "mismatched sections" and I could CONFIG_NO_ERROR_ON_MISMATCH=y to bypass them... which I did. I'm crossing my fingers that this was complaining about a different kernel than what the normal Lineage build was expecting, but I'm not sure.

I applied the things I talked about in earlier posts, like enabling the second screen via the kernel/lge/msm8996/arch/arm64/configs/lineageos_h910_defconfig file (which is the one I needed to update/replace from lineageos_h910_oxavelar_defconfig). Also, I added this line:

TARGET_PROVIDES_QTI_TELEPHONY_JAR := true

... to hardware/lineage/telephony/Android.mk (right before the check for that value) -- I understand there is a better place to set that variable, but I was just trying to get this thing to build & I want to document what worked. :)

Here is the link for the signboard APK, which hasn't changed:

https://drive.google.com/open?id=1uOCxX7xWzoi2e9DUGrNmppQ0vE5dE4gB

I need to backup everything on my device before I can test this out. [MENTION=5371326]hawkeye29[/MENTION] feeling brave again? :P
[LG V20 Guides, News, & Discussion] TheIronMaiden:
Sure why not. After work though.
[LG V20 Guides, News, & Discussion] phr00t:
I flashed my build, and the resolution looked good... but I couldn't get past the initial setup screen. No screen taps were being registered. Sound, service & physical buttons were working fine... just couldn't tap the "Start" button (or anything else). I wonder if you'll have the same experience.... I'm not sure why this is happening & would love any help :-/
[LG V20 Guides, News, & Discussion] Zacharee1:
Sorry guys. I kind of dropped off the map here. Server is back up, but I'm involved in a bunch of other stuff, and Android Studio is not cooperating. I'll work on it when I can.
[LG V20 Guides, News, & Discussion] poixninja:
4

I know this doesn't contribute to the development, but take your time! Most people never expected second screen to work on aosp, so what you're doing is beautiful!

Edit: also, I plegded 10 bucks, so we are up to 500 now with me :)
[LG V20 Guides, News, & Discussion] Zacharee1:
It's actually $530 I think, but XDA won't let me edit the damn post.
[LG V20 Guides, News, & Discussion] Blaises:
Yeah, things have been pretty busy on my end as well.

I didn't have a chance to run my builds on Thursday, but that doesn't mean there hasn't been any progress. I committed my changes that include the service now.

It's a little sloppy since I'm still playing around with what ideas would work the best. I'll have to separate some of that out to make things easier to work with.

I just threw a random icon and background color together for the test views plus one with a textclock so I could make sure things are being updated correctly.

At risk of being a tease, I've attached a gif of the current state of my changes.

When I get some time later this week I'll see about making some test builds available for y'all to play with.
[LG V20 Guides, News, & Discussion] phr00t:
I got another Lineage 15.1 build for the H910 AT&T version, using the Gamma v17 kernel source & the latest signboard updates from Blaises:

https://drive.google.com/open?id=17aOFxceY2lLMwec7czXSDuIGHyLPwIOD

I haven't tested it yet, but this build was much more clean -- no "mismatch" errors. I plan on testing this tomorrow.

I had trouble building your latest APK, [MENTION=1852121]Blaises[/MENTION]... couldn't find:

import android.os.ServiceManager;

import android.os.ISignBoardService;

.... heading to bed though, I'll look more into it tomorrow (unless you happen to post an answer why).
[LG V20 Guides, News, & Discussion] Blaises:
That's the new service I had added, that means you didn't pull in my new changes. Just resync the repo and you should be good to go.
[LG V20 Guides, News, & Discussion] Zacharee1:
[MENTION=1852121]Blaises[/MENTION], how against making a Telegram would you be?
[LG V20 Guides, News, & Discussion] me2151:
You know where to find me :P
[LG V20 Guides, News, & Discussion] Zacharee1:
I made a Telegram group with someone else who says he can help out. It'd be good to have you there.
[LG V20 Guides, News, & Discussion] Zacharee1:
OK guys, I've got proper basic functionality in now: https://youtu.be/lLoWoNsemwU

I just need to get some way of chat communication with [MENTION=1852121]Blaises[/MENTION] so I can hook into the system service and work out a few remaining issues.

EDIT: I just realized that video doesn't actually show anything lol. I'll get a proper recording in a second.

EDIT2: fixed.
[LG V20 Guides, News, & Discussion] The_Keeper86:
I sure hope so even though I love the Weta rom I want to switch to an aosp rom so bad without dual booting. The second screen is extremely useful. Those who keep saying it isn't are just lying to themselves.
[LG V20 Guides, News, & Discussion] USA-RedDragon:
So guys. Just a teaser [IMG="Second Screen working"]https://i.imgur.com/jhD5oW2.jpg[/IMG]
[LG V20 Guides, News, & Discussion] The_Keeper86:
Looking good!
[LG V20 Guides, News, & Discussion] Aaren11:
Awesome work Red!

Even leaving that space as homescreen real-estate would be so useful. Wonder what ideas people have got for AOD / screen-off notifications.
[LG V20 Guides, News, & Discussion] rubiicon59:
In what way?
[LG V20 Guides, News, & Discussion] Aaren11:
There's plenty of apps like Swiftly or AppSwap that could be used to replace the functionality of the second screen if the area was accessible without the statusbar conflicting. Widgets on the homescreen could be docked there, apps could be written to replace the recents menu or shunt the softkeys in there when the screen is rotated 180 degrees. Having the real-estate as mappable screen-space opens up a whole plethora of options for AOSP devs.
[LG V20 Guides, News, & Discussion] dudeawsome:
Hey man I'd be glad to be a beta tester of this rom
[LG V20 Guides, News, & Discussion] Team DevDigitel:
it would be nice to force the status-bar to be into the 2nd screen, make it use that portion for the status-bar and allow the regular screen for apps, shortcuts etc.
[LG V20 Guides, News, & Discussion] fr4nk1yn:
I was wondering if there was software to do that. I mistakenly flashed a stock kernel to AOSP and the second screen was an extension of the main with, of course, part cutoff.

Great work being done here. Going to make the v20 so much better.
[LG V20 Guides, News, & Discussion] Vibbix:
Looks pretty amazing; if there is any sort of API for it, I would love to work with it to recreate some of built in one's LG provides.
[LG V20 Guides, News, & Discussion] Zacharee1:
That's the plan for it.
[LG V20 Guides, News, & Discussion] emdroidle:
Is source code for your work publicly available? What license? (I very much hope "yes" and GPL2 or GPL3)
[LG V20 Guides, News, & Discussion] Zacharee1:
Not my work; it's [MENTION=5184450]USA-RedDragon[/MENTION]'s. Since it's being built right into System UI, I think it's going to be FOSS.
[LG V20 Guides, News, & Discussion] cordell12:
lies! :laugh::laugh::laugh:
[LG V20 Guides, News, & Discussion] TheLoonyRebel:
mentalmuso has done some AOSP work doing something similar to that. However he's more focused on getting his stock based kernel working right now but it is progress on the AOSP side.
[LG V20 Guides, News, & Discussion] me2151:
Honestly I think all of us Devs are just bored with the V20... Some are switching to other devices(not naming who) I know USA Red Dragons been working on things other than 2nd screen. Mentalmuso has been working on his stock kernel. Ive been doing a new rom And Im too lazy to do a RTS installer so thats put off.... Team Dev has been having issues with his roms. Tilde88 just disappeared off the face of the earth... SaintZ only doing kernels now as the main developers of EmotionOS disappeared. Chaz has been busy with life.

None of us are putting in TOO MUCH active effort in getting this phone booming.
[LG V20 Guides, News, & Discussion] Chaz187:
Well said man!
[LG V20 Guides, News, & Discussion] USA-RedDragon:
Yeah. Like [MENTION=4591212]me2151[/MENTION], we all have real life and other stuff going on. This work takes time that not all of us have. The way I see it, people should be happy it's being done at all. I'm not even running with it correctly. It's broken and I haven't touched it in a week
[LG V20 Guides, News, & Discussion] lowridincrew,:
Just stumbled upon this thread. I was wondering if anything was getting done with the 2nd screen. I thought It was a lost cause. I appreciate you guys work. I'm patient so I'll just sit back and wait. I keep going from AOSP back to stock because of the 2nd screen
[LG V20 Guides, News, & Discussion] exadeci:
Is your work in progress available github? The 990DS now got rooted and I would be interested in helping.
[LG V20 Guides, News, & Discussion] Zacharee1:
Sorry for the ping-spam, [MENTION=1852121]Blaises[/MENTION], but I can't find you on Matrix by either Blaises or Ahrotahn.
[LG V20 Guides, News, & Discussion] phr00t:
Are you just making changes to the APK for this functionality, and no further changes were needed within LineageOS 15.1? I didn't see any commits in your android_framework base.

I did build another Lineage OS 15.1 for the H910 AT&T Version -- the last build accidentally had the configuration item disabling the second screen in there... this new one should be "proper" and I plan on testing it tonight:

https://drive.google.com/open?id=1HAhvcxcUhWrLGwWb-PHBN9acIAteEM2q

I did pull in [MENTION=1852121]Blaises[/MENTION] changes for building my Lineage ROM, but I'm using Android Studio with the "default" build environment... looks like I will need to somehow reference your source to get the signboard services.
[LG V20 Guides, News, & Discussion] me2151:
I mean. as i said. you know where to find me...
[LG V20 Guides, News, & Discussion] Blaises:
I just set up an account there: Ahrotahn

On matrix I'm: [MENTION=1852121]Blaises[/MENTION]:matrix.org
[LG V20 Guides, News, & Discussion] phr00t:
Unfortunately, my Lineage builds with Signboard changes & the Gamma kernel source are not responding to screen taps. I could build with just the Lineage kernel instead, which is what Zacharee & Blaises are doing, but you'd be missing at least KCAL support. Perhaps we can get the Gamma developer to get these Signboard changes in, but may have to wait for this whole project to be more stable.
[LG V20 Guides, News, & Discussion] Phoenix591:
The compiler used for the lineage kernel is WAY older (last update for that major version was in 2015, while iirc the one gamma normally uses was last updated july last year) than the one used for his releases... you may find it, and his buildscripts on his github. it would probabily be simplist to build it with his script (make sure to adjust it to account for your system) and use the modded standard lineage kernel in the rom build itself and have a second zip with the modded gamma. (Trying not to directly spoon feed you, but instead let you grow, if you really need or want further explaining or an example gamma kernel built this way I can have one done quickly)
[LG V20 Guides, News, & Discussion] phr00t:
I'm using gcc 7.3, which is pretty updated, if that is the compiler you are referring to.

I tried some of the scripts & patches in that github... the makefile was originally setup for the 996, so I had to change it to the 910 (my AT&T version). However, it would complain there was no build target for lineageos_h910_oxavelar_defconfig (nor the pulled 996 one). The kcal patch seemed to have applied, although the voltage-control one said "input was garbage" (patch doesn't mince words). There was a list of cherry picks, which about half were already applied to the code & I did cherry pick the rest. I'm building again now, although much doesn't seem to have changed (taken in some cherry-picked commits & the kcal patch).

I'm very new to android ROM development & only jumping in because I really want to upgrade to Lineage 15.1 + Gamma + be Signboard ready... I don't particularly have the time to get my hands really dirty, so I'm happy to be spoon fed :P I'm not sure how to get the mods into the Gamma kernel without building it alongside android_frameworks_base (where Zacharee & Blaises are making changes in & is part of the entire Lineage build process).
[LG V20 Guides, News, & Discussion] Phoenix591:
A lot of the compiling when done in the aosp tree gets done with ancient gcc versions located in the prebuilt folder (the exact one is specified in Boardconfig.mk in device/lge/h910 or more likely one of the -common folders also in device/lge) The only "mod" that goes into the kernel is simply setting disable_second_screen=n (paraphrasing the config name) you didnt need to mess with applying any patches-kcal is already applied to the kernel along with all the other features gamma already has.
[LG V20 Guides, News, & Discussion] Dr_DjEnder:
try using:

git checkout firmware/analogix/mi1_eeprom_20_8b.img

right before you compile the kernel, make mrproper, the cleaning make, deletes that firmware file sometimes and results in non working touch screen. I ran into it on cm-14.1

(credit to ehem for the fix)
[LG V20 Guides, News, & Discussion] x86cpu:
That's not used on our devices though. It's the usb g6 or g5 driver... i just don't remember which one.

---------- Post added at 11:07 PM ---------- Previous post was at 11:05 PM ----------

Once things are more stable i will be happy to provide builds with things in. Plus the eventual goal is to get it into LineageOS sources for official builds.
[LG V20 Guides, News, & Discussion] Phoenix591:
The builds weren't working... Builds fixed and uploaded on post 737
[LG V20 Guides, News, & Discussion] phr00t:
Oh man, I got excited to try this... but it appears the H910 ZIP is corrupted! :crying: The file doesn't appear to have a ZIP header & it can't be opened. I tried a few others, which seem to work fine...

I can build Lineage 15.1 with signboard changes for H910 & have been (see my previous posts for a link), just haven't been able to get past the setup screen. However, these kernels hopefully will resolve that -- I'm hoping you can double-check the H910 one!

Thank you for the tip, [MENTION=7467520]Dr_DjEnder[/MENTION] on git checkout firmware/analogix/mi1_eeprom_20_8b.img -- I did actually notice that file disappearing when "make clean"ing, but my build process would fail out when it was missing. I don't recall seeing anything about a USB G5/G6 driver, but there is a ton of text & if it wasn't showing an error, I probably would miss it. Anyway, I shouldn't have to bang my head against the wall on this anymore, since we (almost) have all the kernels with the second screen enabled.

I see there were some more improvements, so I'll plan on trying to build a new Lineage & APK tomorrow.
[LG V20 Guides, News, & Discussion] Phoenix591:
having that file along with other parts of firmware for that other thing is part of what broke usb otg on lineage for so long.. its supposed to be gone.

.

I reuploaded the h910 zip, should work now
[LG V20 Guides, News, & Discussion] karismakaris:
Vs995?

---------- Post added at 09:25 AM ---------- Previous post was at 09:19 AM ----------

Vs995?
[LG V20 Guides, News, & Discussion] phr00t:
Here is today's Lineage 15.1 H910 AT&T build with signboard changes, which hopefully will work with the posted Gamma kernels above:

https://drive.google.com/open?id=14AcUrhI-Ilr5wpikbiTd3wozNKkKb7Wq

This was build with the standard Lineage kernels & should be ready for replacement. There are at least one more commits of Zach's not in this build -- but I'm glad to see updates happening faster than I can build them :)

I don't have a new APK to test with, since the new code is integrating more with custom services which makes the build process a little more tricky. I'll try and figure it out, though :) This old one still may work for testing:

https://drive.google.com/open?id=1uOCxX7xWzoi2e9DUGrNmppQ0vE5dE4gB

---------- Post added at 02:53 PM ---------- Previous post was at 02:24 PM ----------

The H910 ZIP is still corrupted. Perhaps it isn't the upload, but the file itself that is messed up? The header of the file still doesn't appear to have a proper ZIP header... maybe something went wrong during the building process? :confused:
[LG V20 Guides, News, & Discussion] Phoenix591:
rererereuploaded.. the zip would work...until it wouldnt on my end
[LG V20 Guides, News, & Discussion] phr00t:
It is an actual ZIP file now that opens! :D Now time to test it...

---------- Post added at 09:51 PM ---------- Previous post was at 09:22 PM ----------

Unfortunately, the Gamma kernel [MENTION=8639605]Phoenix591[/MENTION] built doesn't flash properly. I get the following errors:

New image larger than boot partition. Aborting...

Updater process ended with ERROR: 1

Error installing zip file <shows zip filename>...

Not sure why it was touching the boot partition...
[LG V20 Guides, News, & Discussion] jl10101:
[MENTION=7055541]Zacharee1[/MENTION] Forgive me if I'm wrong, but the rotation for 270 doesn't seem to correspond with 180?

https://github.com/zacharee/android...mmit/69c33837264021215de73108b8a1e9e9175d324a

View attachment 4557528
[LG V20 Guides, News, & Discussion] x86cpu:
The kernel is inside the boot partition. The boot partition is the / ramdisk and the kernel image too. (Hence if you every tried to change files in / they will not stock on a reboot.)
[LG V20 Guides, News, & Discussion] Redline:
Stock 8.0 has begun rolling out for the V20 variants worldwide, presumably (still) with support for the second screen. Does this mean you guys will have more solid bases to work from and/or integrate, hopefully making things easier?
[LG V20 Guides, News, & Discussion] Zacharee1:
Doubtful.
[LG V20 Guides, News, & Discussion] Zacharee1:
That's a really old commit.
[LG V20 Guides, News, & Discussion] jl10101:
Oops...*climbs back into the cupboard*

BTW, super promising progress on the YouTube video you posted!
[LG V20 Guides, News, & Discussion] x86cpu:
.kdz link anywhere?
[LG V20 Guides, News, & Discussion] phr00t:
https://xdaforums.com/v20/development/kdz-8-0-oreo-v20-f800slk-t3820449
[LG V20 Guides, News, & Discussion] phr00t:
Since [MENTION=8639605]Phoenix591[/MENTION] kernel for H910 couldn't flash (got an error that the image was bigger than the boot partition), I've been trying to build just the Gamma kernel myself. I pulled the source & tools. I configured it for lineageos_h910_oxavelar_defconfig without the SECOND_SCREEN_DISABLE defined successfully. When trying to build, I get this error:

aarch64-linux-gnu-gcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found

compilation terminated.

arch/arm64/kernel/vdso/Makefile:34: recipe for target 'arch/arm64/kernel/vdso/vdso.so.dbg' failed

make[1]: *** [arch/arm64/kernel/vdso/vdso.so.dbg] Error 1

arch/arm64//Makefile:133: recipe for target 'vdso_prepare' failed

make: *** [vdso_prepare] Error 2

I don't see that .so library in the Gamma build tools, but I do see it in the Lineage build environment. I tried copying that .so file in a few locations, but still got the error. I don't know where it is suppose to go to be properly picked up or what bigger I may be doing wrong here. Any help is greatly appreciated!