yashsingh1/xdaforums huggingface dataset:
[LG V20 Guides, News, & Discussion] phr00t:
After installing the arm cross compiler & trying different ones in the Makefile, I got past the liblto_plugin problem. Compilation gets much further now, but now I get this error:

In file included from include/linux/rcupdate.h:43:0,

from include/linux/rbtree.h:34,

from include/linux/mm_types.h:9,

from include/asm-generic/pgtable.h:7,

from ./arch/arm64//include/asm/pgtable.h:522,

from ./arch/arm64//include/asm/io.h:29,

from include/linux/clocksource.h:19,

from include/clocksource/arm_arch_timer.h:19,

from ./arch/arm64//include/asm/arch_timer.h:27,

from ./arch/arm64//include/asm/timex.h:19,

from include/linux/timex.h:65,

from include/linux/sched.h:19,

from ./arch/arm64//include/asm/compat.h:25,

from ./arch/arm64//include/asm/stat.h:23,

from include/linux/stat.h:5,

from include/linux/module.h:10,

from init/main.c:15:

include/linux/completion.h:45:9: error: initializer element is not constant

struct completion work = COMPLETION_INITIALIZER(work)

^

init/main.c:391:19: note: in expansion of macro 'DECLARE_COMPLETION'

static __initdata DECLARE_COMPLETION(kthreadd_done);

^

include/linux/completion.h:45:9: error: (near initialization for 'kthreadd_done.wait.lock')

struct completion work = COMPLETION_INITIALIZER(work)

^

init/main.c:391:19: note: in expansion of macro 'DECLARE_COMPLETION'

static __initdata DECLARE_COMPLETION(kthreadd_done);

^

scripts/Makefile.build:257: recipe for target 'init/main.o' failed

make[1]: *** [init/main.o] Error 1

Makefile:965: recipe for target 'init' failed

make: *** [init] Error 2
[LG V20 Guides, News, & Discussion] Phoenix591:
A clean build plus a slight cflag change and this should work.
[LG V20 Guides, News, & Discussion] Zacharee1:
OK guys. Before I start, PLEASE DON'T REPORT BUGS!

Don't share this link either. Let people see it themselves and read the post.

DON'T TRY THIS IF YOU'RE ON ARB1 OR LATER! The final product will be designed for ARB1, in the official LineageOS 15.1.

This isn't anywhere near complete, but here's what works:

- Portrait orientations (0° and 180°)

- Settings to modify what's enabled and the order (Settings >> Display >> Advanced >> SignBoard)

- BoredSigns (the main app itself won't work, but the widgets will load just fine)

- Widget configuration access (hold down on the page in the SignBoard or tap an enabled page in the Settings area)

Here's what doesn't work:

- Landscape orientations

- Full AOD (it will appear and function when Ambient Display activates, and if you make Ambient always-on, it'll be on too, but this obviously isn't a great solution)

- Stock widgets (you'll have to use BoredSigns for now, until I can make some)

- Certain apps (DU Recorder, AOSP Keyboard confirmed) and possibly some screen overlays will be inset by 160px from the right side of the display.

- The pager isn't infinite like on LGUX. If you go to the last widget, you can't just keep going to get back to the first.

Note: the SignBoard does't start automatically on boot right now. You need to open the AOSPSignBoard app and tap "ADD WINDOW" or go to the Settings and change something there.

Again, NO BUG REPORTS! If you want, you can add an issue to my GitHub for a future feature request. Try to make it something LGUX and BoredSigns don't have. I'll be replicating the LGUX widgets, and potentially just integrating BoredSigns (although I don't know the logistics of keeping it updated, since it can't be done through the Play Store).

Here's the download link: https://www.zwander.tk/#losdownloads

At the time of posting this, only the H918 has a build, and I'm currently building for the H910.

EDIT: Fixed downloads. H910 is done.
[LG V20 Guides, News, & Discussion] Sigil_Thane:
I got somewhat turned about in this thread I fear, is this a full Lineage ROM, or just a kernel?

Thanks for the awesome work, and I'll wait for the H910 version
[LG V20 Guides, News, & Discussion] Zacharee1:
Full ROM.
[LG V20 Guides, News, & Discussion] phr00t:
Does the ROM & APK need to be bundled together, or is that done for convenience?

I couldn't open the H910 Lineage build ZIP... I opened it up to check the header, and for some reason it had "Downloading <the filename>..." before the PK header. I removed that odd text & now it opens fine. Backing up my phone to try it now....
[LG V20 Guides, News, & Discussion] Zacharee1:
You mean AOSPSignBoard? It contains the layout editor, so it's needed. It'll also have the stock widgets when I make those. So yes, it's needed.
[LG V20 Guides, News, & Discussion] phr00t:
I'm having trouble flashing the H910 version. It says it checks for a digest file, then skips the digest file because it isn't found. Updater process then ends with Error: 3

Possibly something is getting messed up via uploading & downloading from your website, since there was a weird header in the file. Removing it allowed me to open the ZIP in 7zip, but other things might be screwy for TWRP to read it...

---------- Post added at 10:06 PM ---------- Previous post was at 10:03 PM ----------

Yeah, the AOSPSignBoard as an APK -- I was wondering if that could be built & upgraded separately if no Lineage ROM changes were required. Just trying to see what & how I could build things in the future.

Having trouble flashing the H910 Lineage ROM from your site. Updater exits with error code 3. No further errors or explanations... although it says it looks for & doesn't find a digest file before the error...
[LG V20 Guides, News, & Discussion] Zacharee1:
I'll fix the site when I can.

The app has to be included with the ROM because it will rely on features only system/signature apps have access to. I can't put it on the Play Store or anything like that.
[LG V20 Guides, News, & Discussion] phr00t:
It won't work as a separate APK either? How do you build it with the ROM if I may ask?

Good news is, the new kernel Pheonix posted for the H910 works! I did try an old APK I was able to build, but nothing appeared in the second screen when clicking "Add Window". Probably because I built it separately & that isn't the right way of doing things... funny seeing stuff rotate into the second screen area for a moment, though.
[LG V20 Guides, News, & Discussion] Zacharee1:
It can't possibly. I just explained why it can't.

Just put it under packages/apps/ and it builds with the rest.
[LG V20 Guides, News, & Discussion] Ak7J4:
Link appear to be down for rn
[LG V20 Guides, News, & Discussion] jaysonic88:
Hmm., download the link isn't working for me either.

Sorry, i didn't see the above reply! :silly:
[LG V20 Guides, News, & Discussion] Zacharee1:
The server is down right now, so links won't work. It should be back in a few hours or so, with fixed downloads as well. Still only H918 and H910. LS997 is next.

[MENTION=2881807]x86cpu[/MENTION] might build for ARB1.
[LG V20 Guides, News, & Discussion] TheLoonyRebel:
Fantastic news. How soon before all the bounty money begins to get collected by the way?
[LG V20 Guides, News, & Discussion] Zacharee1:
No idea. I don't even know if I'm allowed to take any (I started the thread). Then there's the logistics of figuring out who wants any, and how it should be divided...
[LG V20 Guides, News, & Discussion] phr00t:
Zacharee1 doesn't know if he is allowed to take any. Ha. Funny. :D I do think Blaises should get a portion, but most of my contribution will be going to you. It may be up to the individual contributors on where their money will go -- so every person feels comfortable.

In other news, trying to build Lineage 15.1 with your latest changes & the AOSPSignBoard included. Fingers crossed!
[LG V20 Guides, News, & Discussion] Zacharee1:
Blaises did more than a portion. He got the second screen to actually show, and built the whole system service.
[LG V20 Guides, News, & Discussion] phr00t:
A big portion, it was. :) I will plan on splitting my contribution in half then. I do think each person will decide how to divide it up, but splitting it in half between you two is probably a safe route. I'm unsure if anyone else has a claim to the bounty, though. Also, work isn't done yet. More people could come in & we don't want to discourage anyone else that could contribute & earn a claim.
[LG V20 Guides, News, & Discussion] runningnak3d:
[MENTION=7055541]Zacharee1[/MENTION] Do you mind updating the first post with a list of the developers that actually made this happen? I don't run Lineage (yet), but this will be a big part of me switching over, so I want to contribute to everyone that helped -- even old devs that aren't active anymore -- if they made a significant contribution.

PS - sorry to see that you retired as a mod.

-- Brian
[LG V20 Guides, News, & Discussion] Zacharee1:
I'll try to edit it, but XDA hasn't been letting me edit my own threads lately.
[LG V20 Guides, News, & Discussion] phr00t:
Latest H910 AT&T Lineage 15.1 build with Signboard changes:

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

This should work with the H910 Gamma kernel Pheonix posted a few posts back. This probably isn't much different than the one Zacharee has on his website, although I pulled the most recent Lineage updates in too. I haven't tested this yet, but plan to soon.
[LG V20 Guides, News, & Discussion] phr00t:
I don't see the AOSP Signboard app in my build... I put it in packages/apps... was there anything more that needed to be done?

EDIT: Think I figured it out. Looks like I needed to add a PRODUCT_PACKAGES line in device/lge/v20-common/v20.mk for AOSPSignBoard -- my apps/ folder wasn't exactly called AOSPSignBoard last build, either. Anyway, this is a link to hopefully a fixed build:

https://drive.google.com/open?id=1QZ8qYCQUmHrwjjfaEGMkEH1UaL06iC5q
[LG V20 Guides, News, & Discussion] Blaises:
I appreciate it, but I'll have to turn that down. Really Zach put in much more time and effort to get this going.

There's still a good bit more to get done before things are really usable though.

Yeah, because of the types of changes we're making, it's a lot easier to build everything together.
[LG V20 Guides, News, & Discussion] phr00t:
So, I now have AOSPSignBoard in my Lineage build. Unfortunately, when clicking "Add Window", I get this exception from logcat:

07-27 21:17:02.378 4864 4864 E AndroidRuntime: FATAL EXCEPTION: main

07-27 21:17:02.378 4864 4864 E AndroidRuntime: Process: com.zacharee1.aospsignboard, PID: 4864

07-27 21:17:02.378 4864 4864 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke interface method 'void android.os.ISignBoardService.removeAllViews()' on a null object reference

07-27 21:17:02.378 4864 4864 E AndroidRuntime: at com.zacharee1.aospsignboard.MainActivity.lambda$-com_zacharee1_aospsignboard_MainActivity_857(MainActivity.java:29)

07-27 21:17:02.378 4864 4864 E AndroidRuntime: at com.zacharee1.aospsignboard.-$Lambda$sYkVkHCTqHnnu27unuXqnfRvqPM.$m$0(Unknown Source:4)

07-27 21:17:02.378 4864 4864 E AndroidRuntime: at com.zacharee1.aospsignboard.-$Lambda$sYkVkHCTqHnnu27unuXqnfRvqPM.onClick(Unknown Source:11)

07-27 21:17:02.378 4864 4864 E AndroidRuntime: at android.view.View.performClick(View.java:6294)

07-27 21:17:02.378 4864 4864 E AndroidRuntime: at android.view.View$PerformClick.run(View.java:24770)

07-27 21:17:02.378 4864 4864 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:790)

07-27 21:17:02.378 4864 4864 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)

07-27 21:17:02.378 4864 4864 E AndroidRuntime: at android.os.Looper.loop(Looper.java:164)

07-27 21:17:02.378 4864 4864 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6494)

07-27 21:17:02.378 4864 4864 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)

07-27 21:17:02.378 4864 4864 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:440)

07-27 21:17:02.378 4864 4864 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)

Is this something wrong with my build or the app, [MENTION=7055541]Zacharee1[/MENTION]? I feel like I'm sooooo close to being able to build & hopefully use some of this time to code functionality, instead of nagging you guys for build troubleshooting help :P

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

ISignBoardService service = ISignBoardService.Stub.asInterface(ServiceManager.getService("signboardservice"));

... must be returning null in my case... hmmmm.... [MENTION=1852121]Blaises[/MENTION], you did the service stuff... any ideas on what would cause that to come back null? I'm pretty sure my android_frameworks_base is up to date with your changes, which should have all the service stuff, right?

---------- Post added at 09:30 PM ---------- Previous post was at 09:25 PM ----------

Also, for you guys: https://i.imgur.com/eFfmdb3.jpg
[LG V20 Guides, News, & Discussion] Zacharee1:
You have to merge the sepolicy repo from either my GH or Blaises' (I forked his). The SignBoard service won't work without it.
[LG V20 Guides, News, & Discussion] phr00t:
Ahhh perfect, thank you. I pulled that one in & hopefully the 56th times the charm! This again is a new Lineage 15.1 H910 AT&T V20 build with signboard changes:

https://drive.google.com/open?id=1wAJzvgwjN21YpdxEV5XUfPwbGVtcEA3Y
[LG V20 Guides, News, & Discussion] Zacharee1:
I'm rebuilding for H918 and H910 right now. Screenshots have been fixed: by default, the SignBoard won't be included, just like it is on LGUX. There's also an option to enable it, just like on LGUX. However, this option is in Settings.Secure instead of SystemProperties, meaning it can be easily toggled on the fly. The value is "enable_signboard_screenshot 1/0" for anyone who might want to change it before I add a GUI option.
[LG V20 Guides, News, & Discussion] phr00t:
In my build, Add Window no longer crashes. Yay! Unfortunately, nothing shows up in the second screen. I also tried without the modified Gamma kernel, and the screens vertical resolution was too short. Clicking the Add Window button then still didn't show anything...
[LG V20 Guides, News, & Discussion] Zacharee1:
By default, there are no widgets, like I said in my release post. You'll need to buy or build BoredSigns and then enable widgets from Settings>>Display>>Advanced>>SignBoard.
[LG V20 Guides, News, & Discussion] Ak7J4:
Are you rebuilding for ARB 1 or should we wait for x86cpu ?
[LG V20 Guides, News, & Discussion] Zacharee1:
I'm not going to be building for ARB1.
[LG V20 Guides, News, & Discussion] Zacharee1:
So I can edit the OP again finally. I now I've missed 3 or so people who wanted to be added to the bounty, but I don't remember who and how much. If you're not on the list and you should be on the list, repeat your pledge.
[LG V20 Guides, News, & Discussion] phr00t:
Ahh, OK. You probably (understandably) don't want me sharing ROMs with BoredSigns prebuilt & bundled, correct?
[LG V20 Guides, News, & Discussion] Zacharee1:
You can do that if you want.
[LG V20 Guides, News, & Discussion] Zacharee1:
If you're willing, could you fill out this form? https://docs.google.com/forms/d/e/1..._xSZfu0CmIU0wJuneOnKMCIg/viewform?usp=sf_link

I want to see which pages are people's favorites so I know what to prioritize.
[LG V20 Guides, News, & Discussion] TheLoonyRebel:
Done. I added "immersive status bar" as that's a huge thing I use the second screen for.
[LG V20 Guides, News, & Discussion] Zacharee1:
I'm not going to be doing that stupid special fullscreen display LG did. The SignBoard will remain the SignBoard no matter what.
[LG V20 Guides, News, & Discussion] TheLoonyRebel:
I feel stupid but.... Information on BoredSigns has nearly what I use "Immersive Status Bar" for. I haven't really touched BoredSigns since the early days so I'm pleasantly surprised at how far it's come. This makes me very excited for when the H918 ARB1 builds are done. Thanks for inadvertently nudging me to try BoredSigns since I remember you developed that.
[LG V20 Guides, News, & Discussion] phr00t:
This is a Lineage 15.1 H910 V20 AT&T version build, with AOSPSignBoard + BoredSigns bundled -- should be everything you need to get the signboard working on this phone (minus the second-screen-enabled Gamma kernel, which Pheonix posted @ https://xdaforums.com/showpost.php?p=77151789&postcount=591):

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

I had a couple of issues getting BoredSigns to compile & had to make a few changes to do so:

https://github.com/phr00t/BoredSigns/commit/87223eaf02b796ad60b2705eb190f71c987ad77f

Most notably I didn't have a weather API key, so the weather feature probably won't work. There also was VOLUME_VOICE line that was undefined, and a launchAssist call that was also undefined, which I had to ultimately comment out to get the build to complete.
[LG V20 Guides, News, & Discussion] Zacharee1:
The weather API key is something you need to get on your own, but the AudioManager constants are just hidden. You need to use https://github.com/anggrayudi/android-hidden-api to have access to them.
[LG V20 Guides, News, & Discussion] phr00t:
I'm unfamiliar with Kotlin, but that Settings.System.VOLUME_VOICE line appears it isn't doing anything (no assignments or function calls etc.), just a line with a constant on it... which if that is the case, I'm not worried about commenting it out.

However, that SearchManager.launchAssist(null) call looks like launchAssist should exist when I look up references of SearchManager, so I'm not sure why that is "unresolved" -- and it looks like functionality actually had to be removed. :(

I'll look into getting a key, although I don't use the weather panel myself, so I didn't take the time to do so yet.
[LG V20 Guides, News, & Discussion] jal3223:
It would be great if the second screen could be used as a mini status bar with the signal information, notifications, and time when in immersive mode. It was an amazing hack when it was done on stock and made better use of both screens.
[LG V20 Guides, News, & Discussion] phr00t:
I tested my build & found some problems with BoredSigns. Clicking the first option (on screen widgets) brings up a dialog that says going to some configuration screen after clicking "OK". Clicking "OK" just brings up a toast message saying there was an error going to the configuration. The second option (AOD widgets) crashes BoredSigns. Under Settings -> Display -> Advanced, I don't see an option for SignBoard...
[LG V20 Guides, News, & Discussion] jl10101:
When / how was that done on stock? Can't figure out the combination of settings etc to achieve that. Thanks!
[LG V20 Guides, News, & Discussion] TheLoonyRebel:
WETA Mods that is included with several roms such as Alpha and Super has that feature. Keep in mind those roms are stock based.
[LG V20 Guides, News, & Discussion] fatmaster:
How do I build a rom that works on ARB1? I have built Lineage/Cyanogen before from source before on my S5, and I see that ARB1 builds are possible on Lineage 15.1. I have a spare computer that I could set up a build environment on and would be willing to host on my google drive.
[LG V20 Guides, News, & Discussion] TripOG:
This rom won't start for me, just kicks me back to recovery after a while of the lineage dots going.
[LG V20 Guides, News, & Discussion] Phoenix591:
I hacked this beauty together in less than 20 minutes: it replaces the three tiny firmware files that differ between arb 1 and 0 to make any h918 lineage rom h918 arb 1 compatible (in theory, only confirmed with lineage 15.1 and this WILL break and need changes if we ever get a split treble style vendor partition, oh and all bets are off if you update to stock Oreo when it eventually releases, who knows what shenanigans LG might put in there) I just made and used it myself to run Zacharee1's arb 0 builds on my arb 1 h918. Also has an addon.d script to ensure the change sticks between lineage build updates.

Flash a lineage build then my zip and once the zip has been flashed once you may reflash/update lineage as much as you want and as long as you don't format system or change roms from lineage the change will stick around.
[LG V20 Guides, News, & Discussion] phr00t:
Are you clearing data and cache before flashing?
[LG V20 Guides, News, & Discussion] TheLoonyRebel:
On the latest H918 builds that Zach has done using the kernel results in the screen getting squashed in with a huge gap at the top of the main screen. Second screen does "work" but it's also squashed within where that huge gap at the top of the main screen is.

Also your ARB1 works great on my end. Lineage boots perfectly with it.
[LG V20 Guides, News, & Discussion] Zacharee1:
Use the kernel in my builds. Don't flash Gamma or anything.
[LG V20 Guides, News, & Discussion] TheLoonyRebel:
Yep I did exactly that a bit ago using the kernel with your build. Second screen runs great on the build from yesterday. However the notification bar won't drop down when I try to do that regardless of if SignBoard is running or not. BoredSigns works great as well I had Information running perfectly! I can test more later today as I just went back to Alpha ROM on my end.

I reported the Gamma kernel issues so it's known how it works and what works.
[LG V20 Guides, News, & Discussion] Koont:
You don't need Weta mod. Just hide the status bar and it'll push it all in second screen. Zach's mod or system UI tuner will do it.
[LG V20 Guides, News, & Discussion] Ak7J4:
So basically flashing this will in theory allow us ARB 1 H918 users to flash the older version of Lineage that Zach has? Also why would this possibly break a split treble style vendor partition? I'm pretty sure I'll stay on Lineage 15.1 (Cause LG is trash af on their updates) but in the worst case possible, if I needed to flash back to stock using LGUP for example or TWRP would it be impossible cause of this change.
[LG V20 Guides, News, & Discussion] TripOG:
Yeah third time was a charm, unfortunately it seems everything is offset to the left a little.
[LG V20 Guides, News, & Discussion] Zacharee1:
Ignore the Treble part. You'll have no trouble flashing back to Stock, since you'll have to clear data anyway, deleting the addon script.
[LG V20 Guides, News, & Discussion] Ak7J4:
Alright , Thanks for the response. Also since this is still Lineage OS 15.1 I should in Theory still have my data correct?

Process I'm going to flash in. Flash the Zip File, then flash the Lineage Build with the Second Screen Changes.
[LG V20 Guides, News, & Discussion] TripOG:
Same issue here.
[LG V20 Guides, News, & Discussion] phr00t:
Yeah, because the problem is in my ROM we both are using :p I think it is because the SignBoard option isn't there, so the service isn't starting. I'm thinking on just modifying the service start function to always run the SignBoard service, so I don't need to worry about the missing setting.
[LG V20 Guides, News, & Discussion] TripOG:
I went back to normal los, the keyboard and home screen all being offset annoyed me too much to use it.
[LG V20 Guides, News, & Discussion] phr00t:
I think these are known bugs, or at least the keyboard. I haven't nocied the home screen being offset... I'm hoping another keyboard, like Swift, won't have the offset problem. Building another ROM now that hopefully will start the SignBoard service without an option.
[LG V20 Guides, News, & Discussion] TripOG:
Keyboard and Microsoft launcher we're both offset, couldn't place icons there or stretch my widgets out to full width on the right hand side or the screen. I used Gboard and the aosp keyboard fwiw with that bug
[LG V20 Guides, News, & Discussion] TheLoonyRebel:
Gboard on the latest build actually worked perfectly fine for me. However the offset issue prevented me from putting widgets/icons on the right side of my home screen. And couldn't get into "about phone" to get development mode on.
[LG V20 Guides, News, & Discussion] TripOG:
Well yeah you're an angry old man Gboard of course would work for you.
[LG V20 Guides, News, & Discussion] Zacharee1:
I'm building a new set of ROMs. Changelog:

SignBoard starts at boot now

Add Music Controller

Add QuickToggles

Some internal stuff

This still has the offset and rotation issues, of course. [MENTION=1852121]Blaises[/MENTION] has a potential fix for the offset, which I need to merge at some point and test out.