yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] steadfasterX:
ok folks first of all sorry , really. I should have tested it more deeply before releasing it.

Current state:

Until now it was proven that fuses are blown:

when you flash (and boot) a bootloader stack

when you flash (and boot) a modem partition

when you use QFIL (firehose related)

I didn't expect that files within the ROM partition (so /system) will also blown fuses but it turns out I am -maybe/likely- wrong.

A first investigation shown that these files

may

blow fuses:

01 000000020000000E SW_ID0
found in system/etc/firmware/venus.b01
01 000000020000000E SW_ID0
found in system/etc/firmware/venus.mbn
01 000000020000000E SW_ID0
found in system/etc/firmware/venus.mdt

The above means ARB v2 fuse. Currently I am not sure what exactly happened and not exactly what venus is meant for but a quick check shown that it is mainly related to video codecs/compression (h264/h265..).

That makes sense as it would explain why it would fix the video playback issues - at least on some devices.

further investigations shown that all these files were for the vs986 and not (as thought/mentioned) for the v29 which explains why it has an ARBv2 level on the venus files.

The fact that this issue affects multiple parts of the phone's hardware is a bad sign for sure. Audio, Camera and Phone issues the same time usually means the system cannot load the firmware properly from the modem partition as all these come from here.

I am currently backing up my g4 with SALT and afterwards I will try to reproduce the issue as just sharing logs here isn't satisfying enough. I need my hands on that to find a fix - if there is any to find..

TLDR;

Currently it looks bad. I mean really bad. If it turns true that an ARB fuse in /system can be blown the situation may be unsolvable as the whole system drivers expects now an ARBv2 to load drivers which will not work on an ARBv0 device.

I will let you know asap what my tests will show.

EDIT:

just a note: the Camera app in LOS will show up automatically when a camera has been detected. As the current issue does not allow to load the cam properly LOS thinks the device does not have a cam and so hiding the app.

.-
[G4 Android Development] Sir Daniel III:
Ohhhhh, so that's why everything broke when I tried to restore backups.... well that's not good.

BTW I still have my SALT backup of before I UsU'ed my phone. Will that be able to fix my phone? (Probably not).
[G4 Android Development] adam_s_459_:
So does this mean if I try to install arb0 firmware it will brick my device? Or would cam, audio, calls and bluetooth just not work if I was to restore stock MM (arb0) from an extracted kdz?
[G4 Android Development] steadfasterX:
This means (when it turns true) that even flashing a ROM (only system & boot partition) has the potential to brick some functionality of your device (like cam and phone).

This is still under investigation.

.-
[G4 Android Development] fates13:
Luckily I have a VS986 and the video/camera fix worked great for me. Am I safe to flash any rom that I want?
[G4 Android Development] steadfasterX:
yes as long as your ARB is v2 it shouldn't be an issue for you. If it still works on yours you are not affected (which would be another proof a fuse has been blown).

If you flash another ROM you have to re-flash that zip though (as it replaces files in /system to get video working).

.-
[G4 Android Development] steadfasterX:
Follow up #3:

SUCCESS

. I got the android digital sound processor (adsp) working again. Sound is back.

woa.. ok my guess was fixing adsp first might be a good idea because it seemed to be the reason for several service crashes which works like a domino effect (crashing adsp crashes all others - like RIL).

so .. after now havin a working adsp again I am able to get called again!! yea and call by myself.. pfff. wow. Ok so let me complete investigate all the other stuff first and then I need brave testers :p

without having rebooted this works again:

- call (in/out)

- camera

- sound in general

- auto-rotate

- youtube 60fps is fine

- clash royale

- what else to check? let me know

next test: rebooting and hoping it will still work :p

EDIT

damn .. rebooted.. still working :) wow what a journey. I will sort all needed stuff now and then let me know if you wanna test the fix by PM or @ Telegram.

.,
[G4 Android Development] Sir Daniel III:
Damn you're a god! But could you please check if it still all works fine when you flash new ROM/restore backups? That's what ended up breaking my phone.

Edit: May you please also check Instagram performance (how well do videos load), YouTube performance and Clash Royale performance? (Clash Royale crashes for me right now). I'm also having "Sign in as Google" problems on Summoners War. These problems may have been fixed with everything else, but these are the rest of the issues I've gotten .
[G4 Android Development] sdembiske:
[MENTION=5545101]steadfasterX[/MENTION]

I had sign-in problems with MS Outlook - I restored just the Data from a Titanium backup and I was back in, so it's a workaround not a solve of the actual issue.
[G4 Android Development] Sir Daniel III:
I think my issue is more related to the game (Summoners War) because everything else I am able to sign in as Google, but in the game when I try to sign into Hive as Google I get an error. This should be fixed once we get the new patch (because it worked before I flashed the zip and everything broke).
[G4 Android Development] steadfasterX:
cant check instagram (no account)

clash royale works fine here

youtube video (battlefield video 60fps) is fine here
[G4 Android Development] NickName777:
Congratulations [MENTION=5545101]steadfasterX[/MENTION] ! Thank you for the time and work you put in our phone!
[G4 Android Development] Sir Daniel III:
Oh okay that's fantastic! Can you check to see if flashing ROMs or restoring backups breaks it? If it doesn't please send the fix over.
[G4 Android Development] steadfasterX:
flashing ROMs will change slightly for those who want/need the patch: you need to re-apply the patch after flashing a ROM or restoring a backup. That's it.

I let currently 2 users test the patch. That shouldn't take long and if that has been done all instructions and the file follows

thx for your patience

.-
[G4 Android Development] Sir Daniel III:
That's great to hear! Okay, if testing goes well, please post the patch so we can all use it! Thanks
[G4 Android Development] steadfasterX:
believe me - that's the plan - as said ;)
[G4 Android Development] steadfasterX:
so here it is.. the real & fixed fix for low video framerates on UsU'd devices.

sorry again for any inconvenience and those who got a heart attack after applying the first version of that patch (broke cell service, camera and more).

This patch is needed only for those who are willing to take a risk and who are able to read instructions thoroughly.

Flashing that patch will change how you flash ROMs afterwards and it may break things nobody knows (yet).

You know it, of course: flashing things is always a risk even when we all are so used to the fact it goes well - most of the times.

We see the warnings when flashing but as it is written everywhere we ignore or simply do not want believe them.

Like: "It went fine the last billion times so why should it fail

now

?"

This whole thing here showing me (and I guess you) again how risky it is especially when working with vendors like Verizon, Sprint and such who makes heavy use of locking down android phones.

(Funny enough that exactly one of these(!) OEMs who are trying to tie up his customers makes UsU possible at the end.. lol.. )

ok here are the instructions: follow them briefly and you will hopefully have a working device again - with full framerate performance, of course:

https://github.com/Suicide-Squirrel/issues_oreo/issues/11#issuecomment-483691424

The above has been tested by 3 persons, me (h815 - UsU'd), thsachs (h815 - official unlocked) and [MENTION=6302635]sdembiske[/MENTION] (H812 - UsU'd).

Thanks again dudes.

Please report back if that fixes your issue or not.

if you had read the instructions and so the README.txt you will find that flashing this will increase another qfuse to make your device working again. qfuses cannot be reverted so again:

DO THIS AT YOUR OWN RISK !

:p

As you can read there this patch should work for any UsU'd g4 model but .. we all are aware again that flashing is a risk - always.

and last but not least and before you may ask:

This patch will never find its way into my LOS builds as it increases qfuse levels which should be IMHO a user decision.

Even when this fixes an issue with the UsU implementation I am not willing to take that decision. In general an UsU'd device works fine

without

that patch.

If a user thinks he needs this fix he must apply it

manually

. Over and out :)

.-
[G4 Android Development] Sir Daniel III:
So far so good, but one small issue: I can't install Instagram.

Camera, video, sound, sensors are all working. Except for Instagram...
[G4 Android Development] adam_s_459_:
If I could thank this more then once I would. All functionality restored :)
[G4 Android Development] sdembiske:
[MENTION=5545101]steadfasterX[/MENTION]

No problem installing Instagram on mine. Also, now was able to log in to MS Outlook with no problems - without the fix I had problems.

Something that I did

that perhaps you didn't, was a clean install of the rom (in TWRP, wiping Cache, Dalvik cache, System and importantly

format

Data > yes before installing the rom), installed gapps and then the video fix. All good throughout now, having tested pretty well everything.
[G4 Android Development] Sir Daniel III:
Ohhhhh FORMAT Data!!!! I just ended up wiping cache, dalvik cache, system and data!! Thank you for telling me!!!

Edit: Yay! It works now.
[G4 Android Development] thekeemo:
Amazing work as always! Any info as to why face unlock doesnt work in updates past January?
[G4 Android Development] adam_s_459_:
So I installed this and it's working but every second reboot or so, when I enter my pin/pattern my systemui crashes and it boots me back to the lock screen (this is on my h812 using lineageos 15.1 but I have tried other oreo roms and they are the same, the issue is nonexistant on nougat). I can provide logs if nescisary when I get home tonight.

Cheers:)
[G4 Android Development] sdembiske:
If you didn't do a clean install of the rom (in TWRP, wiping Cache, Dalvik cache, System and importantly

format

Data > yes before installing the rom), installing Open Gapps and then the video fix you could have some potential issues. I did it the way I've outlined here and have had no issues at all.
[G4 Android Development] steadfasterX:
Exaclty as [MENTION=6302635]sdembiske[/MENTION] said.
[G4 Android Development] adam_s_459_:
I did clean flash I formatted data and completely set up rom from new.
[G4 Android Development] steadfasterX:
....and? Does it work now?
[G4 Android Development] adam_s_459_:
No that's what I orrigionally did
[G4 Android Development] sdembiske:
I'm presuming you installed Open Gapps, immediately after clean flashing the rom, before booting up for the first time? Forgetting to do that will create similar issues, even when Open Gapps is installed after 1st boot.

The other time, I've run into a similar issue was when I installed the Greenify4Magisk module before actually opening Greenify and selecting to use the root method to do the first set-up. May be a similar-type issue you're running into.

I would do a clean flash again, re-install Open Gapps and the video fix, boot it up and see if issues are there and if good then reboot to TWRP to install Magisk, Xposed etc. When booted up again, and having activated those apps, take note what order you're doing/installing other apps to see if the issue presents again.
[G4 Android Development] adam_s_459_:
Ok I will try. thanks!
[G4 Android Development] Sir Daniel III:
BTW, are there any plans for Android Pie? (Just a quick question)
[G4 Android Development] thekeemo:
Anyone having issues with GPS? It's very slow to respond. I'm not sure if it's a rom issue, or because I'm using it without a Sim card.
[G4 Android Development] rundumdieuhr:
Might be the latter. Works fine for me.

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] mad_max034:
great work [MENTION=5545101]steadfasterX[/MENTION]. I've been running the ROM for 2 weeks on my H812 (Rogers v20x) and it's a pleasure to be able to benefit from the improvements over the stock MM one in terms of battery saving and responsiveness.

Tough, I've been having some infrequent but annoying demigod SOC blue screens and tried to flash the stock modem (I realized after the fact that I didn't have a backup of the phone). I've tried to flash an updated nougat modem that I found on the xda forums as a mistake thinking it could help improve the stability.

After twiddling around with the N modem, I reflashed the MM modem you posted, but it seems like the phone is not able to send/receive calls (on a pure vanilla ROM, no Gapps installed, no root). The phone just freezes and reboots. One thing to note is that SMS and data work.

Another thing to note is that the accelerometer, microphone, light (for automatic brightness) and camera (through OpenCamera) sensors support/availability all seem to have gone out the window too. All sensors worked prior to the N modem flash.

I also applied your patch for the video lag fix that prevents me from downgrading to the stock version (triggers an anti rollback error in LGUP)

Got any idea of what I could do to fix my issue ?

---------- Post added at 03:52 AM ---------- Previous post was at 03:41 AM ----------

I reapplied the video lag fix patch and all sensors are back and running. Next time, I'll RTFM !
[G4 Android Development] steadfasterX:
New build is up

Noteworthy Changes:

June security patches

BT voice fixed

Keep in mind that even when I have done some tests it might have unknown side effects or behave not in every situation as expected as I cannot test everything ...

so always keep a recent backup of your important data !

just to be crystal clear all the credits going to [MENTION=7268092]z3DD3r[/MENTION] and [MENTION=7412373]Sashko98[/MENTION] . I have just spent over one year and was not able to solve it but these guys are heroes !

several internal adjustments regarding Wi-fi and Bluetooth firmware paths and patch files

A "REGULAR CLEAN FLASH" is required !

See the FAQ of this thread for what that means :

https://xdaforums.com/g4/development/rom-lineageos-16-0-t3929082/post79502871

If you wanna show your gratitude for the BT voice fix give those guys at least all your 8 thanks clicks (open the post I linked and click on every post you can find there from those guys):

[MENTION=7268092]z3DD3r[/MENTION] (does not accept donations):

https://xdaforums.com/google-nexus-5/devs-only/bt-calling-robotic-audio-t3798105/post79747463

[MENTION=7412373]Sashko98[/MENTION] (accepts donations as well):

https://xdaforums.com/google-nexus-5/devs-only/bt-calling-robotic-audio-t3798105/post79749418
[G4 Android Development] m13b:
Installed latest June 28 build, lineage-15.1-20190628-UNOFFICIAL-h812_usu. When flashing GApps (stock 8.1 ARM64 20190629) I get an error:

***Incompatible Android ROM detected***

This GApps package is for Android 8.1.x ONLY

Please download the correct version for your ROM: 9 (SDK 28)

I'll try the Pie GApps, just want to be sure this is intended behaviour.
[G4 Android Development] steadfasterX:
No that's not correct and do not try to flash pie gapps on oreo. That won't work.

My guess is you're using the wrong TWRP version but share the recovery log after that error occurs (see my sig)
[G4 Android Development] m13b:
Think this is the correct recovery.log. Sorry I had to filedropper it, it's 30K lines of the same error message making it too massive to dump just the text: http://www.filedropper.com/recovery

I was on TWRP 3.2.1-0 before, tried on 3.3.1-0 but ran into the same error. I'm just formatting Data before installing, not sure if I should be doing anything else.
[G4 Android Development] steadfasterX:
Use the correct TWRP preview release for the oreo flavor. Link is in my official TWRP thread .
[G4 Android Development] Obermudez19:
Hey dude... There is a problem with WiFi on H812... Someone knows how to Solve it? :(
[G4 Android Development] m13b:
Hey again, used the twrp-3.3.1-PREVIEW-193_g4_O.img posted on June 24 from your leech server. Rebooted back to recovery. Did a full clean, rebooted back to recovery, flashed the image, then flashed GApps. Still getting the same error. Can provide the TWRP recovery.log again if needed but it looks to be more of the same.
[G4 Android Development] steadfasterX:
Ofc. Without the recovery log I can't do anything . Pls use a paste service this time like paste.omnirom.org or similar .
[G4 Android Development] m13b:
What specific issue? Are you having trouble detecting some 5GHz networks? See: https://github.com/Suicide-Squirrel/issues_oreo/issues/16

---------- Post added at 03:22 PM ---------- Previous post was at 03:17 PM ----------

I tried redownloading the image and it installed fine this time, no issue. My bad for wasting your time, I must have screwed something up the first time ._.
[G4 Android Development] Obermudez19:
Whats new on the new update?? [MENTION=5545101]steadfasterX[/MENTION]
[G4 Android Development] steadfasterX:
4th July 2019: https://xdaforums.com/showpost.php?p=79842583&postcount=1293

8th July 2019: https://xdaforums.com/showpost.php?p=79867733&postcount=1299
[G4 Android Development] steadfasterX:
This thread has been marked deprecated.

I moved everyone to the generic LOS 15.1 thread here instead: general LOS all-in-one thread

Ensure you write your model and that you have an UsU model when asking questions there.

Also ensure you subscribe that all-in-one-thread to get news i.e. when new builds arrive.

.-
[G4 Android Development] vsTerminus:
Thanks [MENTION=4302074]bdasmith[/MENTION] for confirming.

I tried [MENTION=6302635]sdembiske[/MENTION]'s Battlefield video and it definitely doesn't play well at 1080p60 for me. Exactly the same behavior as every other 1080p60 video I have tried so far.

Also, regarding the APN settings... If you need to edit an existing or add a new APN there is a workaround... You can edit /system/etc/apns-conf.xml (assuming you are rooted) and add new entries or modify existing ones there. Once you've updated the file go into your APN config and choose "Restore Defaults" and you'll see your changes. It's not a great solution but if you're like me and absolutely need to be able to do that, there's an option for now.
[G4 Android Development] bdasmith:
Quick question, do all of these issues work the way they are supposed to with the v29a stock nougat? I didn't think to check those things when i had it installed.
[G4 Android Development] ThePiGuy:
That's for H815 only. Do you have an H815 or H812?
[G4 Android Development] bdasmith:
812. The version for "arb any" can be used on the h812. I had it installes along with the kernel for 812 usu N
[G4 Android Development] ThePiGuy:
Oh right ok (you know more than I do then :D)
[G4 Android Development] steadfasterX:
Thx for the serial info! Do you had mobile service / signal while on N?
[G4 Android Development] bdasmith:
Yes i sure did. It was working flawlessly for several weeks. I only changed to try lineage ?
[G4 Android Development] bdasmith:
[MENTION=4256326]vsTerminus[/MENTION] [MENTION=5545101]steadfasterX[/MENTION] tonight im going to go back to atick v29a and test to see if any of these problems existed there. Then may come back to lineage, but I'll decide later.
[G4 Android Development] n01z:
Hey,

I'm running this ROM, *two thumbs up*

I have the same video playback issue on YouTube. Other than that, pretty much everything is working fine. I rooted with Magisk and everything seemed smooth, until I flashed the safetynet v2beta5 .zip

It passed safetynet but every time I boot I am faced with a pop-up:

"A vendor image mismatch has been detected. Typically this means your vendor image is out of date.."

I asked in the safetynet thread they said:

"You need to flash a vendor image which matches the rom you are on"

Ok, I have no idea where to find this vendor image. Any ideas?

One other completely unrelated question, how can we change the system font? Will replacing the .ttf files in system/fonts work like in the good ol' days?? or am I headed for impending bootloops??

I've seen the green demigod screen too many times lately..

Anyways, thanks again, you all are awesome.
[G4 Android Development] bdasmith:
Everything works perfectly in stock nougat. I wiped all, flashed stock mm modem 20z, flashed v29a arb any, flashed h812 stock usu kernel, flashed magisk.

Its only july 2017 security updates, but better than mm and everything works as it should!

Love lineage very much, but stock lg just feels right at the moment. I'm sure you will get it to the point i will switch. Thank you guys! Look forward to testing upcoming versions!
[G4 Android Development] ThePiGuy:
Vendor mismatch was an issue we had on the H815 and H811 a while ago. Should be a simple change in the device tree for us. I'll have a look into it
[G4 Android Development] glenrocks:
H812-Lineage Oreo- SIM Unlock prompt

Hi

Since steadfasterX is off this weekend, and he suggested- soI tried flashing H812-Oreo-LOS again with Gapps+SU and then I tried MM modem to see if system still hangs.. somehow modem H810 MM twrp zip worked (crazy phone). So now my question is I get SIM unlock prompt without Signal bars/no SIM-- I remember steadfasterX mentioning but thought unlock code I had would work... seems not-- maybe radio signal is off?? Any suggestions till Monday..thanks

(for steadfasterX) - FYI, I also noticed that Wifi network only shows 2.4 (not 5.0 as before). Sound works..Camera works..Video in 1080 works.. IMEI shows...Baseband version shows (3-00128-.M8992FAAAANAZM-1.50758.1)).. Mobile network is a pain now (seems like you might have to look at the device on Monday or next week). Thanks for all your kind help.
[G4 Android Development] ThePiGuy:
I think the sim unlocking might be an issue with the rom at the moment. I don't use it so I don't know how it is supposed to work - I assumed unlocking the sim would then enable it to connect to the network. What does the sim pin do?
[G4 Android Development] glenrocks:
it shows unsuccessful message.. I assume there is some mismatch somewhere?!
[G4 Android Development] steadfasterX:
You have to reflash the modemst1 and modemst2 then it should went back to work. I have it in your home dir iirc basebandtest or similar. Or wait until Monday ;)

Just to be clear I'm off on IRC only ;) can't be completely off ever :D

Which MM modem do you had flashed exactly??

"modem H810 MM twrp zip" what exactly do you had flashed? Which zip? The baseband one?
[G4 Android Development] n01z:
In DEV Ops the Kill App Back Button feature doesn't work. No app gets killed. I do get a second vibrate when I hold it down, however.
[G4 Android Development] ThePiGuy:
I'm trying to replicate the magisk safety net issue - what safetynet hiding thing did you flash. I thought magisk hide was in the manager app
[G4 Android Development] nummer:
Is 60fps playback working well?