yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] ThePiGuy:
Ok maybe it's just a hardware fault with my phone then ? I don't use it much anyway
[G4 Android Development] hteles:
Damn. :(
[G4 Android Development] fi5z.x9:
Pls where is the link to Genesixx Los rom? Also, is it available for H811? Thanks.
[G4 Android Development] mikemech:
Try here: host.llamasweet.tech/genesixx/LineageOS/h811/
[G4 Android Development] hteles:
In the op of this same thread.

https://goo.gl/k8798n
[G4 Android Development] Kortex@XDA:
Hi all

What's this message about potential software hacking with 20180405 ROM ? I downloaded it from sale repos as usual... Is there a problem ?
[G4 Android Development] belrik:
The Los coins? It's a bad joke from the Devs.
[G4 Android Development] Kortex@XDA:
OK, thx. And what about the sticky notification ?
[G4 Android Development] Ponder Stibbons:
Maybe a 1st April joke?

Please see URL for further details:

https://lineageos.org/Changelog-17/

Open your TWRP Recovery go to a terminal write "setprop persist.lineage.nofool true" and reboot. That should disable the notification.

Hth,

Ponder
[G4 Android Development] Kortex@XDA:
Thank you, did it, works :)
[G4 Android Development] ThePiGuy:
[MENTION=5461026]kessaras[/MENTION] I am trying once again to build LOS from your O sources, and I have encountered a duplicate SE Policy error (https://hastebin.com/orulirehoy.vbs) that I cannot find the root of. I know you are busy with AOSCP, but I was wondering if you could point me in the right direction

Edit: If it helps, the g4 files I am using are on my github (https://github.com/thepiguy0) under device_lge_g4-common, device_lge_h815 and kernel_lge_msm8992 (without android at the front - those are forked from the lineage repos instead)
[G4 Android Development] kessaras:
a te_macro is missing to point to what exactly is qmuxd_socket. missing or is wrong

EDIT (to explain):

"conflicting TE rule" = a te_macro rule is wrong, or duplicated and one rule is different from the other
[G4 Android Development] ThePiGuy:
Thats interesting, because I got a duplicate qmux error before which stemmed from the device/qcom/sepolicy/wcnss_server.te file, and looking at your AOSCP version, you had commented out the second qmux_socket(wcnss_socket) line. Maybe that is what caused this error

EDIT: You are right - the te_macros.te file was causing issues. I have removed it for the time being and will add in the necessary parts later if I have to (it will just come up as an SELinux denial, won't it?), and that allowed me to put the second qmux_socket(wcnss_socket) line back in, fixing the above error

EDIT 2: Turns out the definitions in that te_macros.te are needed for the other SEPolicies (e.g. tee.te). Now I need to work out which line in te_macros.te is giving me a duplicate definition error (qmux_socket duplicate decleration)
[G4 Android Development] Ponder Stibbons:
Hallo all und have a nice weekend.

Now I have installed LineageOS as described in the first Posting.

4. Wipe data/factory reset
5. Flash LineageOS
6. Optional: Install the Google Apps addon package, install the SU addon package(https://download.lineageos.org/extras, choose arm64)
7. Reboot

To point 6 I have installed addonsu-14.1-arm64-signed.zip and addonsu-remove-14.1-arm64-signed.zip from https://download.lineageos.org/extras. Now I want to delete some apps with amaze file explorer but I didn't get root rights. Why? What is wrong? Please can someone kick me in the right direction to install Su correct?

cu, Ponder
[G4 Android Development] ThePiGuy:
[MENTION=5461026]kessaras[/MENTION] I think I have found the problem - the te_macros file is defining all the qmux_sockets, including the one already defined in the qcom sepolicy. Is there a way to see and edit the list that the $1 symbol refers to
[G4 Android Development] kessaras:
first of all i need to know which rule you need to add and why (to fix which denial ? We don't blindly add rules, we follow the denials), which qcom sepolicies repo you use and your g4-common repo.
[G4 Android Development] ThePiGuy:
It's not a denial - it's a build error. Firstly, I get qmux_socket duplicate declaration, which I have found to be fixed if I remove the te_macros file. However, this causes other issues as then the other declarations that aren't duplicates are then undeclared

Edit: my g4-common repo is Https://GitHub.com/ThePiGuy0/device_lge_g4-common but it is currently very similar to your AOSCP one
[G4 Android Development] kessaras:
you do not remove the te_macro if you use qmuxd_socket policies. the compiler won't know what is qmuxd_socket and it most likely didn't log more errors because the compiler is stupid and skipped those policies.

just remove the policies that cause the error since its about a compiler error only.

You only must add policies which you found denials about, not add everything. If you add everything , then its not enforcing, its a joke.
[G4 Android Development] ThePiGuy:
Ah ok. So I have been going about it the wrong way. I should remove all the SEPolicies from AOSCP, build permissive and then add in the relevant ones

---------- Post added at 11:40 AM ---------- Previous post was at 11:32 AM ----------

[MENTION=5461026]kessaras[/MENTION] interestingly, even if I remove all the SE policies (except the te_macro file), I still get the error I mentioned (https://hastebin/ruwudibuzi.scala)

Edit: turns out no SEPolicies at all is the answer :)
[G4 Android Development] steadfasterX:
Better join our TG group [MENTION=8699949]ThePiGuy[/MENTION]. That's a better place to discuss things regarding development then a forum..
[G4 Android Development] kessaras:
i didnt see the log. it gave me error 404.

anyway. besides g4-common tree policies , you also have qcom selinux policies and system se-policies.

just remove the te files and keep the file_context.

file context is important. keep qcom policies too. build permissive yes and then take full log.

join tg group as i told you before. the link is in aoscp op and my tg is @ pavlaras
[G4 Android Development] sdembiske:
Download SuperSU-v2.82-201705271822.zip and flash it in TWRP. You can download it from here: https://xdaforums.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703 - choose the TWRP / FlashFire installable ZIP
[G4 Android Development] ThePiGuy:
Don't flash both. "addonsu-14.1-arm64-signed.zip" is to get root access and "addonsu-remove-14.1-arm64-signed.zip" removes it again. So what you have done is gain root access to immediately take it away again
[G4 Android Development] ThePiGuy:
I have done it!!! I have a booting LOS 15.1 using [MENTION=5461026]kessaras[/MENTION]'s AOSCP O sources. Unfortunately RIL is still completely broken ( [MENTION=5461026]kessaras[/MENTION], what was this shim you were talking about?). Where do people recommend hosting zips for people to try (if they want to of course)
[G4 Android Development] kessaras:
wherever is better for you.

android file host which is free and unlimited, it sucks.

strace rild could help* us fix it.

share it somewhere so that i can test it too and trace that when i get the time.

just google it. OR do not flash the remove su zip -_-
[G4 Android Development] Ponder Stibbons:
I got an "404 Page Not Found"-Error.

---------- Post added at 02:13 PM ---------- Previous post was at 02:07 PM ----------

That's make sense! Such mistakes can be avoided if I read more closely.
[G4 Android Development] ThePiGuy:
[MENTION=5461026]kessaras[/MENTION] I have put the zip here (https://drive.google.com/file/d/1HsKqVJSmo2cqd2WN_gO0Ym7KvREmWJML/view?usp=sharing) and the md5sum here (https://drive.google.com/file/d/1vSh5HbBawimNEElXiwgEEzDpjfJQ4uo1/view?usp=sharing). All sources are detailed in my manifest (https://github.com/thepiguy0/g4_manifest)

Edit: rename manifest to g4
[G4 Android Development] sdembiske:
Sorry about that:

Try this now: https://xdaforums.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
[G4 Android Development] ThePiGuy:
What advantage is there using that one instead of the one straight off the lineage website?
[G4 Android Development] kessaras:
great work. downloading now. i tag [MENTION=5545101]steadfasterX[/MENTION] to see it too. Maybe he wants to perform any crazy usu test again with los 15.1 :p

supersu is supersu and the one in los is the old native simple root method that cm used to have in developer options
[G4 Android Development] sdembiske:
Using one that is much more well known and proven to work across a variety of devices and roms - granting SU permissions has been problematic for some apps with the Lineage add-on.
[G4 Android Development] cablematicman:
I flashed the latest build as I always do and now the phone is overheating. I tried wiping cache and re-flashing. wiping cache and dalvic etc... tried everything including flashing older build. Not sure what went wrong this time. I did what I usually do. During installation it says something like :Can't unmount /system because it's busy" but I think it always says that?
[G4 Android Development] ThePiGuy:
Yep it normally says that. Where are you getting your builds from. If the kernel and source are stock Los ones then they haven't been changed for months
[G4 Android Development] cablematicman:
downloading from this thread under personal nightlies (personnal nightlies http://host.erwanleboucher.fr/), same as always... I've been downloading from this thread for about 2 months now. this happened once before actually and I ended up doing a full wipe to fix it. I just wish I knew what went wrong in particular. a full wipe is annoying to set everything up again.
[G4 Android Development] ThePiGuy:
Ah ok so you are using [MENTION=5776465]genesixxbf3[/MENTION]'s personal nightlies. I think they just use the official Lineage sources (somebody correct me if I am wrong) and therefore whilst you are getting updated LOS software, the actual G4 sources haven't been updated for at least 6 months. Therefore, unless Lineage have done something in their LOS 14.1 sources to cause this bug, it's unfortunately a side effect of dirty flashing, and will probably need another full wipe and clean install to fix it. You could also try flashing down again to the last version to see if that fixes it
[G4 Android Development] steadfasterX:
System mount issue is NOT normal but happens when using an outdated TWRP (so not the latest preview one)
[G4 Android Development] ThePiGuy:
Oh. Even on the latest nougat one (doesn't seem to on Oreo) it does for me
[G4 Android Development] steadfasterX:
That's bad and would have been nice to know :p

I have fixed that a while ago and here it works.

Pls share the TWRP log in the TWRP thread.. (just boot up and grab the log)
[G4 Android Development] cablematicman:
dang, full wipe? 9 times out of 10 dirty flash is OK. I wonder what goes wrong.
[G4 Android Development] michael_0394:
Will you build a h811 version too? I'd gladly help with testing too but sadly I don't have h815
[G4 Android Development] ThePiGuy:
I can give it a go. I don't have an h811 though so anything that gets uploaded will be completely untested

Edit: correct model
[G4 Android Development] michael_0394:
I'll be sure to have a full backup ready lol
[G4 Android Development] ThePiGuy:
Did you get it to work in the end?

I get a weird vendor mismatch message every time I boot - I thought it was because I had altered the signature in lineage.mk from the AOSCP android 8 one to the LG stock marshmallow one (I read this can help with google play certification and that all lineage builds do it), but it didn't help when I changed it back.

Apart from that, RIL seems to be the only major problem that I can see right now
[G4 Android Development] codeworkx:
Fix: https://github.com/LineageOS/androi...mmit/e5507baeed3caf5837b988ffbe328f601b8c8a81
[G4 Android Development] ThePiGuy:
[MENTION=8633200]michael_0394[/MENTION] and others, just built the H811 variant. Use at your own risk though - I have no idea if this even boots (I don't own an H811 to test it)

Let me know if you get a vendor mismatch error on this as well - I'm just building the fix mentioned above by [MENTION=3208754]codeworkx[/MENTION] into the H815 version

All in my drive folder (https://drive.google.com/open?id=1E_7gAZFyT-u1LLz_lmHUvKlEF4AGzCNj)
[G4 Android Development] michael_0394:
Awesome! As soon as I have extra time later tonight probably I'll flash and let you know what happens.
[G4 Android Development] kessaras:
hold the horses ! I can't procceed immidiately.

i'm carefully updating our kernel even more. first for N, then will test in O. Then i'm ready to flash it and help with the errors.

if you need to strace rild on your own in the meantime it goes like that:

First of all, grab the strace executable https://github.com/Suicide-Squirrel/logcat_reports/blob/master/strace.bin (its being built to work in our arm64 processor)

adb root && adb remount

adb push the strace in /system/bin

adb shell

cd system

find -name rild

exit

adb shell "strace.bin -y -Ff -a 120 -s 200 -o /sdcard/Download/strace.txt /vendor/bin/hw/rild"

-------- strace -- standard options needed to trace it-- -o output ----- what to trace

< wait one minute max if strace hasn't stopped >

adb pull /sdcard/Download and see why
[G4 Android Development] KonterBiER:
Is it possible to dirty flash the new inofficial LOS 14.1 builds for H815 over the last official LOS 14.1?
[G4 Android Development] ThePiGuy:
I did it, but to be honest I have absolutely no idea what any of it means (it's attached)

Having done more testing, audio doesn't work either. Does the G4 tree link to an AOSCP audio framework that needs to be altered for lineage?
[G4 Android Development] raptorddd:
maybe asking too much but...can you also fix N stock kernel:D remeber last build keeps big cores active and small inactive making phone hot.
[G4 Android Development] michael_0394:
I tried flashing it today and I got the vendor mismatch error.
[G4 Android Development] ThePiGuy:
Ok cool, I'll build it with [MENTION=3208754]codeworkx[/MENTION]'s fix when I get the chance (probably tonight)
[G4 Android Development] michael_0394:
Okay sounds good and so I'll know what known bugs to be looking for what isn't working on the h815 build as of now?
[G4 Android Development] ThePiGuy:
New 20180417 h811 build up. That vendor issue should be fixed. Hopefully I'll get an H815 zip up as well at some point

So far, I think issues are no phone signal, no audio (I think) and some apps crash when they try to use these features (e.g. camera can take stills but not video due to audio and voice recorder doesn't work)

All in https://drive.google.com/drive/folders/1E_7gAZFyT-u1LLz_lmHUvKlEF4AGzCNj?usp=sharing
[G4 Android Development] scottyrick:
H811 4/17 15.1: I can confirm my audio and camera app crashes for me every time. Otherwise seems to work just fine for most of my apps, etc.

---------- Post added at 08:47 AM ---------- Previous post was at 08:46 AM ----------

I meant NO audio. Sorry for the typo.
[G4 Android Development] ThePiGuy:
Thanks. Notification led isn't working as well but I think I know how to fix it - it just need to build it in, but unfortunately my build environment is really slow at the moment so I need to sort that out first.

As for audio and RIL, hopefully [MENTION=5461026]kessaras[/MENTION] will be able to help (I have no idea how to fix them) but I am fully aware he is busy with AOSCP at the moment
[G4 Android Development] ThePiGuy:
For anyone interested, got a new H815 20180425 LOS 15.1 build up that contains a fix for the broken RIL. That works now, and I just need to sort out the broken audio before it will become vaguely usable. It's there if anybody wants to test it though. Battery and notification LED's are also fixed, and I have tested encryption and can confirm that works properly too. All in my google drive folder (https://drive.google.com/drive/folders/1E_7gAZFyT-u1LLz_lmHUvKlEF4AGzCNj?usp=sharing)

Edit: For H811 users, I'll try to get a build up tomorrow
[G4 Android Development] steadfasterX:
You should start your own ROM thread for 15.1..

Btw I dunno your plans but I could offer scheduled builds..
[G4 Android Development] ThePiGuy:
Ok I will create a new thread this afternoon. As for scheduled builds, that would be great once I have everything working (from that point onwards, I just plan to keep it up to date with the cypheros enhancements and lineage code)
[G4 Android Development] popy2006:
Thx, for you effort on LOS 15.1 :o

Any chance of getting official again?

I'll think we was dropped because of encryption (which is now fixed), right?

Does BT voice call works on your build?

This is the only feature stopping me from using an 8+ build, because ill need it daily in my car.

thx a lot

pOpY
[G4 Android Development] obvious:
Broken audio. It's right there in the previous post. Early days yet. Amazing accomplishment
[G4 Android Development] ThePiGuy:
All thanks to [MENTION=5461026]kessaras[/MENTION] really though. He did the real hard work getting the G4 up to Oreo for AOSCP. I just ported it to LOS

Edit: btw, SELinux is currently permissive as well, so that need to be sorted too
[G4 Android Development] ThePiGuy:
New H811 build is out now.

Also, I am aware that I am hijacking a thread so I have created my own LOS 15.1 thread here and I will be moving here for further updates
[G4 Android Development] Netsab:
Hi. Still have problem sometimes to get my MMS with 12042018 and need to reboot... Anybody else have too?

Thanks

Edit : seems to be fix with last build...
[G4 Android Development] Luca4k4:
Bug waking up the phone

Hello,

i'm using this awesome custom rom since yesterday and i've noticed just a bug: often, when i press power button to wake up the phone, it does not wake up and i've to press power button at least 2-3 times. I tried to remove the film (tempered glass) but without solving the problem. How can i solve it? Because in this way it's so annoying :(

My version is: lineage-14.1-20180503-UNOFFICIAL-h815.zip

Another minor question: after each update (today Genesixx has published a new update in his repository) have i to re-flash the ROM from recovery losing all data? or will i get the update via OTA?

Thank you very much!
[G4 Android Development] ThePiGuy:
First thing you should know - those builds are automated and get no bug fixes and security patches other than LOS generic ones. So any bugs you have now are likely to stay.

Also, you will not get OTA's as only official builds get them. However, all you need to do is dirty flash (no wiping except maybe cache) to update
[G4 Android Development] Luca4k4:
Hi, thank you for the reply. I would know at least if someone else are getting the same problem and if exists a solution (eg. disable some option, etc). It's very strange if i would be the only with this problem :rolleyes:
[G4 Android Development] ThePiGuy:
I'm running Los 14.1 with titan kernel and that has no such issues. However, I have noticed that the LOS 15.1 that I am developing does sometimes have this issue. Not sure what it is at the moment
[G4 Android Development] Luca4k4:
Sorry for the ignorance: have i to do something to install Titan Kernel or it is integrated in this Rom? Anyway, in addition to my problem, double tap doesn't wake up the phone too :rolleyes:
[G4 Android Development] ThePiGuy:
No this rom is lineage kernel. I think there is something you can flash (I build mine from source so I'm not sure about this).

Check under display in settings to see if double tap to wake is on
[G4 Android Development] Luca4k4:
Okay! Thank you very much:)

I checked: the option is on but it doesn't work. Maybe the Microsoft Launcher give some problem? It's very strange. I have to change this awesome ROM for this little problem :(
[G4 Android Development] ThePiGuy:
Microsoft launcher may affect double tap to sleep but not wake (as double tap to wake is controlled by the system).

(By the way, if somebody helps you on XDA, it's generally nice to drop them a thanks :))
[G4 Android Development] Luca4k4:
:p sure!

Hoping someone else has fixed this problem and can help me!
[G4 Android Development] ThePiGuy:
Your other options are of course to move to a rom that has a maintainer. AOSCP is the main one for G4, with [MENTION=5461026]kessaras[/MENTION] maintaining both N and O versions.

Also if you feel like experimenting, you could try my LOS 15.1 (based on O) but it is early days yet for that rom and it still has a few bugs and is fairly untested
[G4 Android Development] Luca4k4:
I have found AOSCP with Nougat only on steadfasterX nightlies. Are these version the ones i should download for Android N ?

After this i end the OT :D
[G4 Android Development] ThePiGuy:
Yes. The official AOSCP N has ended but [MENTION=5461026]kessaras[/MENTION] kept maintaining it on [MENTION=5545101]steadfasterX[/MENTION]'s server. O AOSCP has official support
[G4 Android Development] JidoFisterFilly:
Problems with my g4

Hey I have a problem with my G4 h815 on LOS 14.1 official and unofficial versions.

Short story:

I bought my LG G4 last June and to this time xposed wasn´t ready for androd 7.

So I used the “lineage-13.0-20170614-UNOFFICIAL-h815” rom and everything worked perfect until end of December when I wanted to update to LOS 14.1.

One Week ago I bought my second G4 h815 because I crashed my first one. But with the second one I have the same problems which are very annoying

I tried all the official ones and unofficial versions that you can see in the pic below and with all of them I have the same problems.

Problems:

With the official roms I have the problem that after different hours (sometimes after 18h, 24h or 76h) the phone don’t detect the sim card any more.

With the unofficial roms I have the problem that I stuck in airplane mode when I am the more than 6 hours in it. I use the Ril control app and then I have connection again.

With both official and unofficial I have the problem that they show me after some hours that they have full cellular connection but when someone calls me I don’t get the call or message for a missed call but mobile internet/data worked.

I even can’t call. When I want to call a number the dialer app tries to dail and stop working and do nothing ( I don’t get a crashed app message or so).

When I use the Ril Control app than it the dailer works again and i have real connection again.

First i was on v20a and then i updated the modem and bootloader to v29a. Same problems.

My Dad has a G4 h815 too and he stays on the on the “lineage-14.1-20170822-nightly-h815-signed” rom since end of august 2017 and he has no problems.

Know someone what’s wrong with my phones or have the same problems?

It is possible that my sim card is the reason of the problems?

But on LOS 13.0 I had no problems.

The last two weeks I used another phone with the sim card until I had my new G4 and with this one I had no problems too.

Maybe it some hardware or software issue with the ril?

Thanks in advance and sorry for my bad English :D

The versions i tried:
[G4 Android Development] kinuris:
Hi. I'm not sure, but maybe you need to upgrade your modem to v29a

Edit: I think I'm wrong, but you can try the unofficial Titan version of this ROM, which works with v29a modem and bootloader.
[G4 Android Development] JidoFisterFilly:
First i was on v20a and then i updated the modem and bootloader to v29a.

That didn´t change anything.

Sorry i forgot to write this.

Edit: I tryed the LOS 14 with Titan Kernel and v29a but unfortunately the same problems.
[G4 Android Development] ThePiGuy:
Have you given an Oreo based rom a go like my LOS 15.1 unofficial or AOSCP. The ril has mostly been fixed (it was a bit dodgy) and mostly connects (albeit sometimes a bit slowly). If it doesnt, a quick restart fixes it.

LOS 14.1 development has halted so any bugs now are unlikely to be fixed
[G4 Android Development] JidoFisterFilly:
I tried the aoscp android 8 version but with that i had huge barrery drain and the phone got very hot.
[G4 Android Development] ThePiGuy:
That's solved now, so maybe you should give it another go