yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] ThePiGuy:
Any chance you could do a fresh build and try it again. I spoke to [MENTION=5461026]kessaras[/MENTION] about how he fixed the encryption on his AOSCP O, and he recommended a lineage-15.1 patch that had been applied in the android_system_vold section. I had a look and it had already been synced, so I built it and encrypted my device and it seems to be encrypting perfectly
[G4 Android Development] obvious:
This one wasn't it? https://review.lineageos.org/#/c/199360/
[G4 Android Development] ThePiGuy:
Yes it was. I also checked a few other crypto related patches and mostly they have been applied in cm-14.1 as well.

Having now booted into TWRP, it asked for my password, and once that had been entered it decrypted my data successfully (@steadfasterX, it works on non-stock N as well)
[G4 Android Development] kessaras:
It's not the same rom this one and AOSCP. It's two roms different.

Only cafs and hals are related and a few external.

Do not confuse things.

What is recommended to fix encryption in aoscp N is not what is going to fix it here too.

I know that I'm usually right , but the rom we were talking about was my aoscp n.... Anyway I'm glad it fixed it here too , but we got no dev to maintain it and of course no way I maintain more ....

[MENTION=8699949]ThePiGuy[/MENTION], wouldn't it be better if you cherry-picked the commits after syncing to my aoscp n from Suicide Org in github and help me out a bit ?

i got no time to build/test N i said but instead you followed my instructions and fixed something that has no dev to be maintained.......

If you fix it in aoscp n , tell me to merge the commits.
[G4 Android Development] ThePiGuy:
Oh ok. Anyway, encryption is working on my device on LOS 14.1 now

---------- Post added at 04:29 PM ---------- Previous post was at 04:10 PM ----------

[MENTION=5461026]kessaras[/MENTION] I never actually fixed anything - it was already fixed (I just gave it a go after checking commits, but somebody else had got there first). I can have a go at fixing your N at some point, but I don't have time right now (at least, not enough to sync up with the AOSCP code and build it - I am building in a VM so a full build takes about 5 hours)
[G4 Android Development] ThePiGuy:
Unfortunately, I have since been locked out (this was the issue, wasn't it), so maybe it isn't working after all.
[G4 Android Development] hteles:
You can delete some files on /data related to gatekeeper to regain access.
[G4 Android Development] ThePiGuy:
Not quite the same as it actually working though unfortunately. Not sure why I got about half an hour of properly working encryption though
[G4 Android Development] Kortex@XDA:
Where can we found the changelog of the updates of this ROM ? I'm running the 0319 release, and I see there's a 0322 one.
[G4 Android Development] hteles:
I Suppose that you can find the changelog at LOS official site, just browse for a different device ( eg D855 ) and all the non device specific entries should be the ones in the same time frame.
[G4 Android Development] Pierro29:
Hi everyone! I first thanks [MENTION=5776465]genesixxbf3[/MENTION] for his work!

I asked me if anyone has create a "custom X cores boot image" for the "lineage-14.1-20180322-UNOFFICIAL-h815" or earlier version?
[G4 Android Development] ThePiGuy:
Does [MENTION=5776465]genesixxbf3[/MENTION]'s unofficial have CVE patches beyond the patches already in the lineage is official repo
[G4 Android Development] Pierro29:
Yes the security patch in the last version is March 5, 2018.
[G4 Android Development] lq092009:
https://xdaforums.com/g4/development/recovery-twrp-3-touch-recovery-t3442424/page85

Encryption errors now appear to be resolved completely. You can now encrypt and decrypt in Oreo. It is possible that the LG G4 will be added back to Lineage 15.1 as an official device?
[G4 Android Development] obvious:
Let's see some love ;-D
[G4 Android Development] nummer:
That would be awesome, and maybe they could do LOS for other models too?
[G4 Android Development] ThePiGuy:
[MENTION=5776465]genesixxbf3[/MENTION] [MENTION=3208754]codeworkx[/MENTION] do you have a record of the CVE patches you have applied to the LOS 14.1 kernel (I have been patching mine and a lot of the unpatched CVE's on the lineage os CVE tracker have actually been patched)
[G4 Android Development] codeworkx:
No. Kernel got replaced with the lg N source drop.
[G4 Android Development] ThePiGuy:
Oh ok so I probably need to start around mid 2017 then
[G4 Android Development] steadfasterX:
You could just use titan. It has several security patches already applied.
[G4 Android Development] ThePiGuy:
How is titan performance compared to los
[G4 Android Development] steadfasterX:
Well titan is based on stock N sources like LOS. But performance is just a word. It can mean everything and nothing. It depends on your own requirements most of the times.
[G4 Android Development] ThePiGuy:
Battery is a biggie for me, and as far as I am aware titan is very good at that. I was just wondering if this came at a cost of feeling slightly laggier than los kernel
[G4 Android Development] ThePiGuy:
[MENTION=5545101]steadfasterX[/MENTION] I have decided to give titan a go - which branch is it on suicide squirrel that I need for LOS 14.1 (I originally thought nougat-stock, but I am now wondering if that is for the LG Stock nougat, and now thinking aosp might be the correct one)
[G4 Android Development] steadfasterX:
AOSP
[G4 Android Development] ThePiGuy:
Ok thanks. Does it also need the android_device_lge_g4-common and android_device_lge_h815 from suicide squirrel as well or do the lineage ones work?
[G4 Android Development] kessaras:
No.

Device tree only affects init which is a "must" work for the rom to boot.

You will have to use LOS trees and MAYBE do changes to init according to the errors you will get during boot.

(I don't think there are gonna be any)

I will change from Titan to msm8992 the path soon too to avoid confusion. Make sure to rm -rf the Titan folder and repo sync --force-sync tomorrow night.

The only thing you may need to change is the defconfig name in device tree. I don't remember what name they use in los
[G4 Android Development] ThePiGuy:
Thanks. It's happily building in the background now (only had to change the defconfig names slightly from los to lineageos).

One other thing I had to do was add 'rc' to the dependencies of the 'qpnp_hap_td_enable' function in drivers/platform/msm/qpnp-haptic.c, as it was giving an error stating that rc hadn't been defined
[G4 Android Development] kessaras:
ye i added some O commits which come from a higher kernel version.

in N i only add the most important of them i dont add all commits from higher kernel versions (e.g 4.4.x).

i will push in a minute it just happened you sync the moment i did a test here and i couldn't do it locally so i pushed. Simply sync again in 10 minutes.

EDIT:

Done. rm -rf the kernel and resync. And this time change the defconfig name in device tree. keep kernel unchanged so that it can always easy sync to me and it doesn't need you to change the defconfig every time i change something.

EDIT2: As said , remember tomorrow night do the same. delete the kernel and resync. it will change the name to msm8992 so it will be easier ;)

if you need anything else later after building, share a log so that we will help.
[G4 Android Development] ThePiGuy:
Ok, will do :)
[G4 Android Development] ThePiGuy:
Ok, rebuilding now :)

Just a quick question, how come I can't see the commit on github (I was watching github for the change before I saw this, and I am still new to github so I am wondering if I am doing something wrong)?

Thanks, will do :)
[G4 Android Development] kessaras:
which commit you mean ? the one that fixed it ?

because i rebased and removed the commit that broke it. i didnt add a commit.

and sry i forgot its about los. you dont need to resync tomorrow.
[G4 Android Development] ThePiGuy:
I have just thought of a few more questions (sorry, just occurring as I build it). I know by default Titan is set to selinux permissive, but can I run it as enforcing on LOS (stock LOS is enforcing)? Also, what is WireGuard? Is it active all the time?
[G4 Android Development] kessaras:
titan is permissive in O only.

the sepolicy is set to permissive in N in the boot args of the cmdline.

https://github.com/Suicide-Squirrel.../blob/oreo-mr1-release_synced/board/kernel.mk

same in Los. it can't enforce without adding all needed sepolicies. it will have bugs everywhere.

Wireguard is a VPN kernel module , added for some extra security. No it's not running unless we make use of it.

Android auto hibernates and caches anything thats not active (services, apps, anything you can think of).

Sleeping and hibernated stuff do not take any active ram. They only take a tiny amount of disk space.

EDIT:

here aoscp branch i use for N.

https://github.com/Suicide-Squirrel/android_device_lge_g4-common/blob/aoscp/board/kernel.mk

there is the permissive.

In O its here :

https://github.com/CypherOS/kernel_lge_msm8992/commit/813a6093e0cd84b0b842057dc36303d49d012727

i set enforce 0 in kernel level.
[G4 Android Development] ThePiGuy:
Ah ok, so as I am building LOS 14.1 it should default to enforcing automatically as that line in the the boot args is not there? (I think I was thinking of the oreo version that has it hard coded in the kernel)

Edit: Just seen your edit :)
[G4 Android Development] kessaras:
yes sadly it will be enforcing and it may cause you many errors in many functions because policies r not ready.

you can dirty build permissive anytime. it will overight the previous cmdline.

and (out of subject) about encryption , i will try fix it in N too some time later (in June) when i will have finished from my 2nd job.
[G4 Android Development] ThePiGuy:
So are the policies in the kernel and not in the rom then (sorry - all this android development is still relatively new to me)? I just assumed that as it was working in Enforcing on the LOS kernel, Titan would be able to do the same.

Good luck :)
[G4 Android Development] kessaras:
no. policies r in device tree

https://github.com/CypherOS/device_lge_g4-common/tree/oreo-mr1-release/sepolicy

(The ones we add , besides the system policies)

We also use qcom sepolicies.

Its not hard to enforce N. But O is at a totally different level...
[G4 Android Development] ThePiGuy:
Ok cool, so enforcing N LOS with the LOS device tree and titan kernel should be ok
[G4 Android Development] johnnyfg:
"lineage-14.1-20180329-UNOFFICIAL-h815.zip" does not work with NFC Mifare Classic.

Seems like it have same hardware as d855 because it have same identical "/vendor/firmware/libpn547_fw.so".

The app "NFC Checker" by TapKey says it (h815) have no support for Mifare Classic.
[G4 Android Development] lq092009:
https://xdaforums.com/g4/...3442424/page85

Encryption errors now appear to be resolved completely. You can now encrypt and decrypt in Oreo. It is possible that the LG G4 will be added back to Lineage 15.1 as an official device?
[G4 Android Development] codeworkx:
No maintainer, no builds. And all lineage repos are still at 14.1.
[G4 Android Development] ThePiGuy:
What is the process for updating a phone to a newer rom? How do you know what to do?
[G4 Android Development] kessaras:
a dev or just a maintainer needs to simply update it locally at his pc or server and then push everything to lineage gerrit.

If the dev is already a los team member he will merge them on his own and update the official. if not, he will simply wait for his patches to be reviewed and accepted by a los dev.

**Ofc everything must be committed properly , otherwise his patches will get denied.
[G4 Android Development] ThePiGuy:
I was wondering more in terms of going from e.g. Android 7 to Android 8. I tried building LOS 15.1 with a moto g peregrine (LOS 14.1 sources) to see what would happen, and hundreds of errors occurred. Is the process of updating to a newer android fixing all these errors, or is there more to it?
[G4 Android Development] kessaras:
you can't use N to build O.

indeed errors were many and its not just that.

it needs binder update and seecom update and fs update in kernel level which i have already applied.

it also won't boot without an O tree. Meaning , you need a manifest to add hidls and lastly add all O hals. It will also need rild shim for ril to work.

Using my AOSCP tree,

it's not hard to do an initial LOS O bringup, but it will still have the same bugs.

1) torch tile will crash the cameraserver because it only takes value 0 ( i do not know how to fix that in kernel , so we r good with the flashlight fix in playstore )

2) bluetooth audio will be distorted. i got no idea what format to use. everything changed in O there.

3) p2p0 never worked. we have missing device error in MM and in N so in O too. i maybe know how to fix that (soon).
[G4 Android Development] Pierro29:
Hi, I regularly loose data connection and need to restart to restore it. (I'm using lineage-14.1-20180322-UNOFFICIAL-h815)

Do I need to install V29a modem to solve this? Could it be done over the rom or must I do it before and reflash the rom?

Thanks!
[G4 Android Development] whitenoise2007:
Have some install issues. H815, Imperium ROM v7, V20i. Wiped everything, the ROM installed fine, installed Gapps super fine. After the first boot, at the configuration pages, after the wireless section, Google Play Services crash and can't go forward from there. It just loops back to wifi selection.
[G4 Android Development] txpalacios:
Are you sure you're flashing nano gapps? Anything above that crashes and burns in current CM-14.0, with symptoms similar to yours.
[G4 Android Development] whitenoise2007:
Not nano. I'm flashing Super package. Strange, since the same package works flawless on AICP. Will try with the nano version.
[G4 Android Development] popy2006:
I am on 26.10:

gallery -> just freeze with tibu and use quickpic from playstore works for me

sd card issue -> is still here. Rom reporting "0,0 GB" size to apps, maybe thats the issue

popy
[G4 Android Development] popy2006:
I have to report an issue with airplane mode an activated bluetooth.

Issue:

When toggling airplane mode with bluetooth activated, bluetooth is working again but the bluetooth tile shows that bluetooth is "off".

Also there is no bluetooth icon in the status bar.

To reproduce:

Switch on bluetooth

toggle airplane mode twice (so airplane mode is disabled at the end)

bluetooth works but tile shows bt off & no bt statusbar icon

I have made a logcat during toggling airplane mode (08:32 -> airplane mode activated, ~08:33 -> airplane mode deactivated).

Also i have made some pictures, see attachments.

thx

pOpY
[G4 Android Development] ntelas:
changelog

Hey dev(genesixxbf3), is there any link to view the changelog of your builds? (your nighties)
[G4 Android Development] kpirnie:
flawless here. pleasantly suprised to see substratum works ?
[G4 Android Development] Rdogg112:
Was also one of the first things I tried and does indeed work flawlessly

MOD EDIT: Thanks for not mentioning the app not permitted in this FORUM
[G4 Android Development] Drenabrab:
Excellent battery life: 5 hours Sot (on stock i get 2,3 hours) but fc close and reboot everytime i open gallery and not working SDcard. Battery percentage doesnt work and i cannot find theme chooser
[G4 Android Development] popy2006:
Freeze gallery and use quick pic from play store.

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] piturcaandrei97:
First thing, thanks to brig N to our device. Second, this build it's "stable" enough to use for daily drive? I use in combo with Imperium and no need Cm camera, use Stock when take photo. I want to know it's have a good battery and if it's fluidy.
[G4 Android Development] popy2006:
i saw "cm-14.1-20161028-UNOFFICIAL-h815.zip" in your download folder :p

big thx!
[G4 Android Development] funnix:
Genesixxbf3, big big thanks for 14.1. :D
[G4 Android Development] InvalidCast:
14.1 is for 7.1 or 7.0? in fact i don't even know if 7.1 is released :)

i asked because gapps for 7.0 didn't installed: i add an error message.

will try again and post error message

EDIT: my bad, i should have searched and see that 14.1 is 7.1

cm installation succeeded, now i'm downloading 7.1 opengapps.

will tell if this one installs correctly

to all: be more carefull than me :)

EDIT2: even with dev options and advanced reboot menu enabled, recovery reboot is not available

i rebooted recovery with flashify

EDIT3: be aware that if you reboot once without proper gapps, accounts are not available (especially gmail)

after configuration, all is good, so i suppose that if you flash good gapps AT THE SAME TIME as 14.1, all should be good
[G4 Android Development] macart:
hi [MENTION=5776465]genesixxbf3[/MENTION] will cm14 focus fix brick phone if I use it on cm14.1?
[G4 Android Development] genesixxbf3:
shall work
[G4 Android Development] popy2006:
With 14.1 this issue is semi gone :p

Now airplane mode doesnt toggle bluetooth at all, but when ill set bluetooth on/off with tasker or even in the "settings -> bluetooth" menu it works.

Statusbar icon & tile state is correct all the the time!

running now 14.1 build from today and see how things goes..

big thx.

pOpY
[G4 Android Development] InvalidCast:
for those, like me, who installed 14.1 without proper gapps (7.1), if you have FC with some google apps, just uninstall and reinstall, that should work

talking about FC, 7.1 has a new menu for that: can't take scrennshot, but it says (sorry, it's french):

- rouvrir l'application (reopen application??)

- envoyer des commentaires (send comments??)

- ignorer jusqu'au redémarrage de l'appareil (ignore until next reboot??)

---------- Post added at 07:07 PM ---------- Previous post was at 06:57 PM ----------

in case of synchro problems (ex: with gmail account, contacts, especially if you had to reinstall the app), go to "settings" -> "accounts", choose your account (google, exchange or whatever) and for each activated toggle, disable then re-enable.

wait a little bit

that should do the job
[G4 Android Development] derBeukatt:
Hey [MENTION=447256]popy2006[/MENTION]

Could you please test for me if external sd card size will be reported correctly? I reverted back to CM13.

Thanks in advance.
[G4 Android Development] popy2006:
Already done : sadly the same issue as on cm14, size is 0 GB.

popy

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] Netsab:
Idem for me
[G4 Android Development] ThePiGuy:
I actually did port LOS 15.1 using your sources a few weeks ago, but I never shared it as RIL was completely broken (no amount of restarts would fix it) and the keyboard was missing for some reason so it was a bit useless
[G4 Android Development] kessaras:
You only need to see why the ril shim was not applied.

You could share a test build for people to flash and grab logs and then it's easy.

Don't just quit something when it only has a few bugs.

Also Los has a huge irq support if you share the link to the log there. They would definitely help. Los is a huge community.
[G4 Android Development] ThePiGuy:
Yeah I know. It's just this phone is my daily driver, so as soon as I go out to do something it needs to be working with everything installed again. I might try again soon and see if I can sort it
[G4 Android Development] kessaras:
A full TWRP backup saved in internal sd will work perfect for that purpose.

It's same here now. I sold all my phones except g4 in order to buy the upcoming Nokia 9.

So when I need to go out I simply restore the full backup.
[G4 Android Development] xalien:
Also for me
[G4 Android Development] Pierro29:
[MENTION=6010113]Netsab[/MENTION] & xalien did you flashed directly from marshmallow ?
[G4 Android Development] Netsab:
Nope, come from successive dirty flash of each unofficial version
[G4 Android Development] Pierro29:
Ok, I have finally installed V29a then clean flash the last unofficial (20180401), hope it will be better!

It seems Quickcharge don't work with this release.
[G4 Android Development] Pierro29:
The connection issue is the same with modem V29a :( It seems that simcard is not detected when I came back from airplane mode.

Quickcharge really don't work.

[MENTION=6010113]Netsab[/MENTION], which is the last more "stable" version according to you?
[G4 Android Development] Netsab:
Maybe the 20180322
[G4 Android Development] :
I have the same simcard problem with these builds. Read https://xdaforums.com/showpost.php?p=76018863&postcount=191 and the following posts.

I tried a lot and nothing did work.
[G4 Android Development] Pierro29:
Thanks but I tested this one first and the flight mode/SIM issue was the same, but quickcharge was ok.

[MENTION=8868715]oldsmarti[/MENTION] , thanks for the link... It will save me from testing the other rom! All we have to do now is avoid flight mode...
[G4 Android Development] Ponder Stibbons:
Hello and Good Morning to all.

First of all I haven't read all the 3540 messages but I have read the first post carefully. Of course since I got my smartphone (that was long time ago) I also read this thread (the latest news) from time to time.

Current state:

LG-G4 H815 (intl)

Bootloader is unlocked

Smartphone is rooted

TWRP is flashed

TWRP-App is installed

Stock rom

Android-Version:	6.0

Security-Patch-Level:	2016-07-01 (This point really annoys me very much. Thanks LG)

Kernel:	3.10.84

Build-No.:	MRA58k

Software-Version:	V20g-EUR-XX

TWRP from steadfasterX

twrp-3.1.1-1-g4.img

[RECOVERY][h815/h811][OFFICIAL][MM][N][O] TWRP 3 touch recovery [2017-12-07]

https://xdaforums.com/g4/development/recovery-twrp-3-touch-recovery-t3442424

me.twrp.twrpapp-26.apk

https://eu.dl.twrp.me/twrpapp/

My questions:

Q1

Is there a better place for my questions?

If it so than (@Administrator) please move my posting to this place.

Q2

Is this the correct source for LineageOS 14.1 for our device? The informations are from the first posting of this thread.

personnal nightlies http://host.erwanleboucher.fr/ respectively https://host.llamasweet.tech/genesixx/LineageOS/h815/

e.g. lineage-14.1-20180405-UNOFFICIAL-h815.zip 05.04.2018 03:18 493.7 MB

Q3

Is this LineageOS 14.1 (from Q2) recommended and suitable for daily use?

Q4

Can I flash this LineageOS 14.1 (from Q2) on my H815 (for specifications please see above) to replace stock rom?

If my question is answered with yes then I will follow the recommended Installation:

First time flashing LineageOS 14.1 on your device, or coming from another ROM?

Download the zip(s)
Install a compatible Recovery
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package, install the SU addon package([url]https://download.lineageos.org/extras[/url], choose arm64)
Reboot

Thank you for your help,

Ponder
[G4 Android Development] ThePiGuy:
Q1: This seems a good place to start ?

Q2: Unfortunately there is no official lineage due to an encryption bug, but that seems to be one of the sources of unofficial lineage nightlies that people use (I think - I am building my own so don't quote me on that)

Q3: The lineage hosted by lineage repos in GitHub (the sources that I use) seems stable. I don't know if any improvements have been made in those nightlies you linked to, but if so then they will only be better

As mentioned above, the main bug is encryption - once you encrypt you will no longer be able to unlock the phone (forcing a full reset from inside twrp)

Q4: That unofficial is for an h815, so you are good to go. The standard instructions a a good guide as to what to do

Btw, the official twrp hosted on their website is a bit out of date. It doesn't make much difference with these ROMs, but you can get the latest unofficial from the twrp thread (the developer [MENTION=5545101]steadfasterX[/MENTION] has a website hosting them all)
[G4 Android Development] ThePiGuy:
Just out of interest, for anybody running an older version of Lineage 14.1 on their G4, does your NFC work (I have built a version for my phone using official sources and NFC does not work)
[G4 Android Development] hteles:
Just successfully paired my Pioneer BT Speaker using NFC

ROM: Its not old official but 14.1-20180405 from Genesixx with LOS Coins :p

Regards.