yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] polfrank:
The feature you are talking about is working fine for me in LOS16 with chrome. I think that it depends on the webpage.

For example, Outlook opens as you say, as a full webpage without browser bar. Wikipedia opens in chrome with browser bar.
[G4 Android Development] Termehansen:
Ok, anyone with an idea how to control that - it is a homepage of a server in my house...

Edit: I guess it is related to PWA

https://en.wikipedia.org/wiki/Progressive_web_applications
[G4 Android Development] polfrank:
Try creating the shortcut with another web browser and see. Keep in mind that this whole thing may be affected by your preference in

Settings>System>Developer Options>WebView implementation

(I don't know if they are spelled exactly this way because I am using another language)
[G4 Android Development] a tiny ant:
First of all thanks for another update.

I'm using a galaxy watch and since the last update the Galaxy Watch plugin is broken and basically locks up the phone with a repeating "sorry, watch plugin has stopped." error message.

I did a clean flash then, not even LOS root and tried again from the play store but the error keeps happening unfortunately.

It looks like the logcat guide posted in the OP ( http://www.bit.do/logcat) is unreachable so I can't give a proper logcat now but I do have the error logs generated by the Wearable app. Maybe they show what went wrong.

https://paste.omnirom.org/view/552cc9e2

https://paste.omnirom.org/view/7a7677a0

With the previous version the watch plugin worked fine. I'll try to make a proper log once that guide works again.

Thanks again.
[G4 Android Development] steadfasterX:
The guide link works . But without www ... Exactly as described in the faq..

Also - as written in every of my changelogs - did you tried with selinux off?
[G4 Android Development] Marvel in Kyrgyzstan:
F500

Hi, help me please, I have an F500 with uSu, I can’t find a ROM for it. I don't know much English, please help
[G4 Android Development] steadfasterX:
Flash h815 UsU on your f500.
[G4 Android Development] a tiny ant:
Apparently my browser was picky about the site for some strange reason.

The logcat is too big to copy paste on mobile so I uploaded it to http://m.uploadedit.com/bbtc/1566119850705.txt instead.

Thanks!
[G4 Android Development] tullyp:
Updated to latest August ROM flashed on vs986 Verizon phone with no issues. All apps appear to work so far, but could not get root with su add on. Do have twerp 3.3.1 Preview 144 recovery installed. Since saw that there is a newer 3.3.1 200 so this may be root issue., Did do full clean before flash. Also tried Magisk 19.3 and no root. More importantly no RIL working yet. Could sometimes find SIM, but not always. Tried setting network to Global and Lte, gsm, cdma, but nothing worked for Cell service. This is my primary phone, so had to flash back to Verizon Marshmellow which works great. I am following the "no RIL" as a known issue under 15.1 Github if I can help with info. All the work done here by delelopers is fantastic and this post is for information only, not a complaint. My USUd phone with Marshmellow works flawlessly and I only will need to upgrade when I eventually find a needed app, such as banking, no longer works in MM.
[G4 Android Development] falenjam:
I have an issue with the app "DMP" (French health insurance app, fr.cnamts.dmp on playstore). I got a message saying there's a security issue with my device.

Safetynet status is green, I also tried with selinux disabled and without magisk but still no luck...

My guess is it's selinux related but I'll let you judge. Here is the log:

https://paste.omnirom.org/view/73e61cb3

Thanks :)
[G4 Android Development] polfrank:
Did you try to select your app in Magisk Hide list?
[G4 Android Development] falenjam:
Yes I did that, rebooted and tried again with no success...

Also, it's not very annoying but I noticed that screen tearing is still happening sometimes with the latest version (when scrolling in a module's readme in the download section of Magisk manager for instance).
[G4 Android Development] hamed_forum:
I install LineageOS 16

My phone h815

Hidden wifi can't connect
[G4 Android Development] Marvel in Kyrgyzstan:
Error 7 , What am I to do?
[G4 Android Development] EWBG29:
I have a vs986 as well and no issues so far, the battery is great. First of all I upgrade my TWRP version to the lastest preview (twrp-3.3.1-PREVIEW-200_g4_P). Did a full Clean install. After I flashed LineageOS, I then flashed the G4-VideoLag-Fix file (found in the unlock G4 forum), Gapps (nano) and then the addonsu file...

I restore my data using the Google method at the startup screen, since I got "error 255" in TWRP when restoring from a backup.

Everything is working fine: Mobile signal, calls, bluetooth, root...
[G4 Android Development] steadfasterX:
Install the latest TWRP preview for Pie. And again no log no help. Read my signature how to get a TWRP log .
[G4 Android Development] polfrank:
Logs or it didn't happen.

.

.

.

I'm sorry, not trying to be rude, I'm just joking. But if you want to help solve your problem, it would just be better to provide a log with the method provided by [MENTION=5545101]steadfasterX[/MENTION]

Okay, so... Did you try without rooting at all? Does this work without root?
[G4 Android Development] falenjam:
Yes I did. The logs I provided were taken without root. With or without selinux the result is the same, it doesn't work.
[G4 Android Development] jjcdennis:
Thanks again steadfasterX. Battery life was getting poor for sure and I'm looking forward to any improvements I can get. Another burger on the way.
[G4 Android Development] busattovini:
"Anyone of you is also experiencing random phone freezes?

I have had that like 3 times. Black screen with blue led light.

Only option: battery out and hard reset?" — [MENTION=5658249]ConradP[/MENTION]

It happened now! I had to take out the battery and then turn the phone on again. The device was locked when it happened.
[G4 Android Development] verbage:
I can confirm this also happened to me using the new 8/15 build that I installed onto an H811 yesterday. For those who saw a recent post of mine talking about a bootlooping H811, please note that this is not the same phone--it is a whole second H811 that is stable!!! Anyway, it happened just a few hours after the install yesterday, and seemingly out of blue, i.e. it did not lock while being used, just when it was sitting on the table by itself. I was hoping to get a log via the new pstore mechanism, but no go--it was completely locked, and needed a battery pull. It has not done it a second time yet... But getting a log--pstore or otherwise--may be difficult if it happens at random, and is always a hard lock. Whatever the case, if it happens again while I'm around the computer, I'll plug it in so see how it pops up under the Windows Device Manager (if at all...), or to see if it is accessible via adb or otherwise.
[G4 Android Development] busattovini:
Exactly what's happening to me! Thanks for sharing it. ❤️
[G4 Android Development] a tiny ant:
I've had the blue light of death a couple of times too on different roms, both stock and Lineage. It's very rare though and I suspect it is caused by Gapps somehow.

It has also happened in recovery mode while restoring a backup and in the middle of encryption. Overall about 6 times this year.

It could also have to do with overheating.
[G4 Android Development] Termehansen:
I just had blue light of death twice (last night and this morning), both times while phone was just lying idle. Also noticed that though screen was black it had backlight on. No contact, and no adb. Only removal off battery helped. How to get log in this case? The new pstore will not help here as far as I understand...

On H815, with 0815 Rom and gapps
[G4 Android Development] hamed_forum:
i install on twrp-3.3.1-PREVIEW-193_g4_O.img the battry good but hidden wifi cant find
[G4 Android Development] steadfasterX:
ok error located.. will work on a fix..

EDIT: [MENTION=7251779]a tiny ant[/MENTION] : what is your model and how unlocked (UsU / official)?

it seems (we don't know until we test) its just trying to read your selinux state from /sys/fs/selinux/enforce - which it can't as selinux denies it.

when you set selinux to permissive it will allow access there ofc, but then it will see that you are permissive. so the only way is adding a sepolicy .

the problematic part with that is it affects all apps. In this particular case it shouldn't be a problem as long as we stay selinux=enforced.

Let me know if you have a h815 official or a h815 UsU unlocked and I give you a boot.img for testing.

I work on a way to handle that panic. It seems the only reliable way at this time will be to auto-reboot after a period of time. I will set this to 15 sec and upload a testing image for h815, h815 UsU and h811 asap.

1) you write the same time in two threads. once in the N/O thread and here. You should only post where it belongs to.

2) if you flash/use pie you HAVE to use TWRP pie. if you flash/use oreo you HAVE to use TWRP oreo.

3) grab a log for option "specific issue" (http://bit.do/logcat) when you try to connect to a hidden wifi

4) report that log in the CORRECT thread.

.-
[G4 Android Development] falenjam:
Ok, I have a h815 official. Thank you !
[G4 Android Development] a tiny ant:
I'm using an officially unlocked H815.
[G4 Android Development] steadfasterX:
ok. try the attached one (extract, fastboot flash boot boot.img)

View attachment 4807798

if you still have issues provide a logcat (specific issue) again, ofc.

.-
[G4 Android Development] busattovini:
Oh, thanks, but how does auto-reboot impacts the system? I mean, will it reboot in every 15 seconds when the screen is off or only when the panic happens?
[G4 Android Development] steadfasterX:
only when it panics it would reboot (after 15s).

this means: when it reboots you have to pull the pstore logs but instructions will follow then.

.-
[G4 Android Development] busattovini:
Thank you! ?
[G4 Android Development] jjcdennis:
steadfasterX, gotta say that the battery issue for me looks resolved. I charged to 100% last night and left the phone on through the night. Result for almost 12 hours later = 98% battery. This is the best result I have seen on any rom, so all is good. With the previous rom (7-25) battery would be dead, or close to overnight.

I haven't used it much so far...but looks great.

Also, I saw someone mention that the lineage addonsu wasn't working. I works as expected for me.

Thanks again.

OK, last comment on battery life - checked the phone this am. It was charged to 100% Sunday PM 8'ish, very light duty yesterday and has been turned on since Sunday PM. Its a 6000 mAh battery I paid ~$30 for. Power is at 95% as of this AM. Great job steadfasterX. Beginning to wonder if the batter display is stuck...awesome result.
[G4 Android Development] busattovini:
I agree. (and I'm still impressed)
[G4 Android Development] falenjam:
Same issue with the attached boot.img.

Here are the logs:

permissive: https://paste.omnirom.org/view/d0a24b4b

enforce: https://paste.omnirom.org/view/20597bfc
[G4 Android Development] tullyp:
Still no RIL Verizon cell service on VS986 , have root

OK, must have been older 144 TWRP that prevented my root. Flashed twrp-3.3.1-PREVIEW-200_g4_P and rooted with Addon 16.

However still no phone service. I have read all that I can about this and up til now haven't seen anybody get a ROM other than stock to have service on Verizon, but glad to see hope if you have it! This is my first attempt at making a log, but see attached zip of my "one shot" logcat. Let me know what else I can do.
[G4 Android Development] steadfasterX:
Did you cleared the app data as well? I still seeing a crash caused by that app.. Will look into it more deeply later.

You really should read the known issues..

Besides that I made a guide which includes all steps from A to Z which includes also proper sharing of logs. You can ofc still attach if they are too big or you like that more. It will just take longer for me to read and so answer ..
[G4 Android Development] falenjam:
Yes I even cleared several times just to be sure ;)
[G4 Android Development] sdembiske:
Also occurred on my H812 UsU with this latest version.

I will mention that I did not have this issue arise with the version before, so I suspect it's to do with one of the changes implemented since then. An automatic reboot would not seem to get at the core of the issue but simply be a 'workaround'.
[G4 Android Development] busattovini:
Maybe the workaround is the first step to solve the issue...
[G4 Android Development] sdembiske:
You do not solve an issue by 'working around it'. It's a bandaid. If it didn't happen with the last version, it would make sense to isolate the changes since then and test cumulatively one + one + one ... repeating, until the issue arises again in order to pinpoint the cause or test the one issue that knowledge would suggest may be the likely culprit, e.g., a kernel change ... ?
[G4 Android Development] steadfasterX:
the auto reboot is not a workaround it is actually the best way to solve the issue. that's the only reason why I want to add it.

Why?

With an auto reboot we hopefully get the dmesg output written by pstore which then guide me in solving the issue caused by the latest commits - if any.

Without the auto reboot you have to pull out the battery to get it working again and that means loosing the logs.
[G4 Android Development] Gigio755:
Maybe it could be usefull for someone (i really don't know)

For blulight death, in the past some dev (for another rom) suggest me to re-flash h815_20p_bootloader_29a_modem_TWRP-flashable.zip and wipe cache and it worked

I flashed the 15/08 build 2 days ago and yesterday after hours of music playing, texts, email, chrome navigation etc.. my h815 had a blulight of death (so not at startup), i just re-flashed h815_20p_bootloader_29a_modem_TWRP-flashable.zip, i wiped cache and it never happened again
[G4 Android Development] verbage:
A couple of additional observations about the hang with the blue led--when it happened again just now, the backlight was on as Termehansen noted (but very low), and I also noticed the phone appeared to be in text mode because there was a single dash or underscore character at the very top left of the screen. I posted a pic of this at https://ibb.co/cNsVkNv. And also as Termehansen reported, no adb/fastboot/download mode contact was available. In fact, even beyond that, the phone is like completely dead to the outside world because on plugging it in to the computer, it was not even recognized/registered with a dmesg blurb. A final note--whereas some locks with LOS14 would result in a burning hot phone probably because of it being stuck in an endless loop, I note that is not the case with the blue led hang at all--the phone is only very slightly warm (if at all).
[G4 Android Development] steadfasterX:
ok here you go: http://leech.binbash.it:8008/lineage/experiments/ --> lineage_h815_20190819_01.zip (dirty flash is fine)

this is an insecure build so not thought for productive usage while it is still in enforcing mode (just saying, selinux is not the reason for your issue).

Let me know if the issue is gone and if not do a logcat again .

well the other selinux policies which get requested need more time. I have to check if I want to add those (have to check the security concerns).

Nevertheless you find a boot image with all these policies requested. its pretty sure we need one ore multiple rounds again as adding policies can be a long journey.

grab a log in any case - even when it works.

View attachment 4808206

I also want to investigate the crash further which is caused by the dmp app. the app triggers a seccomp filter which denies the request.

I am not sure if that can (should) be solved by us, more likely it needs to be solved within the app as the call is simply wrong/unexpected.

seccomp prevents stuff often used by malware and I am not sure if an exception here is a good solution. the tombstone might tell me more:

so do this:

boot to TWRP

adb pull /data/tombstones/tombstone_43

if you can't find that one try if you see others in that directory and grab the latest.

compress it and attach it to a post (that's an exception to my regular way but the most easy one which ensures I get what I need).

.-
[G4 Android Development] busattovini:
The blue light death is happening quite often now. I think I'm going back to the previous build...

--------

I'm going to reflash last build again, and then I tell you if it helps me.

---

anyway, I'm waiting for the auto reboot feature

---

Edit: it's still happening frequently. :(

I don't know if it means something, but the panic doesn't happen when the phone is charging
[G4 Android Development] falenjam:
The app is still crashing so it seems other selinux policies are required. For information, I also tried to launch the app on my brother's device (nokia 7+, android 9) and it's working fine.

permissive logs: https://paste.omnirom.org/view/0e55b132

enforce logs: https://paste.omnirom.org/view/acfb2a8a

Regarding the tombstones, I could grab tombstone_43 and I added the newer ones too just in case. I didn't find how to attach the file here (maybe the 10 posts policy) so I used a file sharing site: http://dl.free.fr/tmMkYStlc

I also got the blue light of death twice. The first occurred shortly after leaving airplane mode: the device felt laggy then it crashed. The second was just after enabling and disabling bluetooth.
[G4 Android Development] steadfasterX:
ok thx for the logs. the seccomp deny is something I have to look in later.

could you pls test again with the attached boot.img? Ofc policy got updated according to your log.

this boot image MIGHT also fix the panic screen but thats a big MIGHT.

View attachment 4808354

.-
[G4 Android Development] steadfasterX:
killing the panic - tests

it seems we have an increasing amount of kernel panics and so I need your help.

pls test by flashing this boot image according to your model:

h815 (official): download

h815 (UsU'd): download

h811: download

As you can see I have not created a test image for all models but I hope these are enough to get some testers

Installation:

boot to fastboot (e.g. adb reboot bootloader)

extract the zip and flash the boot image (fastboot flash boot boot.img)

fastboot reboot

just do what you ever do and see if the panics are gone or not.

HINT: The provided builds are

insecure

builds - meaning they are auto-rooted on adb and usb-debug is auto-enabled without auth.

.-
[G4 Android Development] falenjam:
Still crashing. It seems endless :eek: What a crappy app :p

- permissive : https://paste.omnirom.org/view/d02d7526

- enforce : https://paste.omnirom.org/view/b42c64c5

I'll check and report about the potential panic screen fix. Thx!
[G4 Android Development] Hotdogint:
Installed on repaired Frankenstein h810 (originally h812). So far everything is holding, 720p/1080p youtube videos play without lag. Good work!
[G4 Android Development] baconbacon:
Here you go https://pastebin.com/iWZ6SNBD

Here is what I did before getting the dmesg: Full wipe including data, installed lineage 16/lag fix/gapps, booted, enabled adb/root, rebooted a few times, got dmesg.

I did this while the phone was booting to try and grab dmesg as fast as possible

while true; do sleep 0.5 ; adb root && break ; done ; while true; do sleep 0.2 ; adb shell dmesg > dmesg.log && break ; done

what works: bluetooth, wifi, sim card (data + receiving texts, calls not tested)

what doesn't: sensors (rotating), camera, sound
[G4 Android Development] svetloslav:
I appreciate your help. I have a few further questions.

1. In the instructions it states I would need to update the baseband as well , but the is none to be found. I have the feeling the file h815_20p_bootloader_29a_modem_TWRP-flashable.zip should be enough.

2. Also there are 2 versions of the above file and I don't know which should I use:

h815_20p_bootloader_29a_modem_TWRP-flashable.zip

or

h815_UsU_20p_bootloader_29a_modem_TWRP-flashable.zip

3. How can I avoid the encryption of data?

4. Is the standard Magisk version compatible with this rom?
[G4 Android Development] belrik:
1. & 2. Hey, I checked and I flashed "LG-H815_29a_Modem_and_Bootloader_no_splash.zip" which includes baseband and modem (as far as I know).

3. Just encrypt, it's easier.

4. I don't use magisk anymore, I prefer to avoid upgrade issues. The only benefit to me was increasing the number of volume steps in nougat and pie seems to have added more steps.

---------- Post added at 10:51 PM ---------- Previous post was at 10:47 PM ----------

Issue of note: massive lag launching everything. From the settings app to YouTube to the keyboard.
[G4 Android Development] Hotdogint:
Upon further testing throughout the day, the battery tanks. Fortunetly I have an extended battery. Obviously this is an early build and not a representative of the final build, just thought I would let you know.
[G4 Android Development] cablematicman:
Currently using lineage-15.1-20190515-UNOFFICIAL-h812_usu. I'm not sure if I ever...flashed the UsU baseband package, do I have to clean flash the modem partition? I just don't understand step 1 unfortunately. Is there a way to see if I flashed the UsU baseband? Thanks.
[G4 Android Development] marti.2092:
I didn't have any battery issues compared to 15.1 or stock.
[G4 Android Development] steadfasterX:
no log - no fix. Read the FAQ #1 (let it run 2min).

no log - no fix. Read the FAQ #1 and #2.

also read the known issue https://github.com/Suicide-Squirrel/issues_pie/issues/15 and check if thats related to your situation.

First of all: What model do you own? h815? Do you have unlocked officially (LG website) or by UsU?

If you have not UsU'd do not use anything tagged with "

UsU

" in the filename.

There is no default encryption enabled in this ROM. You would need to enable it in the android settings.

Magisk worked fine last time I tested it.

You never need to flash a

baseband

for this ROM. UsU'd or not! where do you read such a thing..?

You should ensure you have an updated bootloader stack and so a current modem partition (which is not the same then the baseband).

First of all: What model do you own? h812?

If you do not know if you ever flashed it simply flash your modem partition again and you can be sure. This can't do any harm.

.-
[G4 Android Development] steadfasterX:
This looks like you have not applied the videolag-fix after flashing the ROM or it had not being applied correctly.

after flashing LOS reboot -> recovery then flash the videolag-fix again. after that grab the recovery.log (see my signature) and on reboot grep the dmesg again

an IMHO better way on linux to grab the log is

adb wait-for-device && adb root && sleep 1s && while true;do dmesg -c; done >> dmesg.log

That needs a CTRL+C after android has fully booted and will be the fastest and best way to catch it.

.-
[G4 Android Development] baconbacon:
lag fix reflash log: https://pastebin.com/Ct16ut9Z

boot afterwards: https://pastebin.com/MrgYq4wp

And here is the fixed bash you posted in case somebody wants it

adb wait-for-device && adb root && sleep 1s && while true; do adb shell dmesg -c; done >> dmesg.log
[G4 Android Development] steadfasterX:
thx yea just saw I missed the keyword "do" there :p that happens when typing on my phone while taking my breakfast xD

ok so this was a frankenstein right? what is the BOARD now?

also do this:

adb shell md5sum /system/etc/firmware/venus.mdt

do you have that issue only on LOS pie?

.-
[G4 Android Development] marti.2092:
by the way [MENTION=5545101]steadfasterX[/MENTION], encryption isn't working for me.

The option isn't enabled.

is this an issue?
[G4 Android Development] steadfasterX:
https://github.com/Suicide-Squirrel/issues_pie/issues
[G4 Android Development] ozukoc:
Thanks for everything. Just flashed now and than installed magisk. Seems stable so far.