yashsingh1/xdaforums huggingface dataset:
[ONE General] fabio_mcz123:
First of all I wanted to thank you for your rom, congratulations. I'm just experiencing problems with loading time. I did the tests and it loads below 1000 mha even with the screen off. Would it also be possible to add a charge speed controller?
[ONE General] Rifat94:
Flash "Franco Kernel" :) :) :) :good:
[ONE General] Rifat94:
Bro New Build Already Released , Waiting for your one 03/14 ?
[ONE General] SivaVr:
Update

- 20180315

changelog - https://www.lineageoslog.com/14.1/bacon

download link - https://androidfilehost.com/?fid=890129502657590752
[ONE General] SivaVr:
lineage-15.1-20180322-UNOFFICIAL-bacon Mar-22-2018

lineageos -15.1 -unofficial from latest source

What works?

everything.

Bugs?

you tell

Flashing Instruction:

use latest official TWRP 3.2.1.0 to avoid error 7:

this is like test build,don't ask for updates . camera feature has been added.

there are too may threads for lineage 15.1 , so i am posting it here .

Download Links

ROM: https://www.androidfilehost.com/?fid=890129502657592947,

TWRP Recovery: https://dl.twrp.me/bacon/twrp-3.2.1-0-bacon.img.html,
[ONE General] Falfa_31:
Short feedback : Camera working but not in third party apps like bacon camera or telegram inbuilt camera.GPS fix is fast but with gps status-agps reset not work anymore.Anyway thank you [MENTION=7388800]SivaVr[/MENTION] solid build
[ONE General] Rifat94:
Okay finally flashed that....

it's smooth like hell.. damn

camera working great, but camera not working on telegram, face unlock...... :( it also has slow charging issue....
[ONE General] oikonomp:
Can confirm that no third party apps that use the camera work. I also tried installing Google camera 2.7 and that didn't work either. That also caused problems in the stock camera app. I had to clear the camera cache and data to fix this.

The second thing is that the cLock widget can't get weather feed.

The last thing I noticed is that the app drawer despite choosing a dark theme remains in this light gray color.

Everything else seem to work fine as of now.
[ONE General] pranavrocksharma:
Will it become official
[ONE General] zzjea:
I have been using this 15.1 ROM for a week and all I use regularly works well. I use it as a daily driver and am awaiting any improvements or additions going toward an Official version. Thanks for the ROM.
[ONE General] SivaVr:
lineageos - 15.1 latest build, April security patch included

change log - https://www.lineageoslog.com/15.1

Download Link - https://androidfilehost.com/?fid=962187416754475592
[ONE General] gk4218:
The ROM is indeed the best one among all oreo, very stable almost like official... keep the good work going :good:

one question:

Can we use weather provider from lineage os source ? I have downloaded and installed yahoo weather provider but can't apply it with clock widget.
[ONE General] DreadfulDrummer:
What camera blobs are used in this ROM?

I see people talking about using Franco Kernel and asking for OOS blobs to be used instead.

That gives me a lot of hope. I don't like Sultan's HAL/OOS v1 blobs, as they don't allow for a long exposure time; maximum shutter speed of 2" just doesn't cut it.

3rd-party camera apps aren't working; is SELinux enforcing?

If so, could somebody switch it to permissive and check if, for example, Bacon Camera works with full 64" shutter speed.
[ONE General] theekilla:
Where can you post bugs?
[ONE General] SivaVr:
LineageOs 15.1 -Update[30/04/2018]

Camera working on third party apps .

Changelog - https://www.lineageoslog.com/15.1

Download Link: - https://androidfilehost.com/?fid=818070582850510982
[ONE General] DreadfulDrummer:
Could you tell me which blobs you're using?

I'd assumed, a couple posts back, that it wasn't Sultan's.

Has this changed?

All other Oreo ROMs use Sultan's HAL; it's merged with Lineage 15.1 officially.
[ONE General] zzjea:
What am I missing here? I have been using this ROM for about 2 months and it is performing like an official version of Oreo. How is it that there are so few replies? Is this the best kept secret in Androidville? I am also rooted and we have two OPO's with this rom running every day as our daily drivers. Why is this rom not getting the coverage it deserves?
[ONE General] DreadfulDrummer:
I'm guessing because there's nothing wrong with it so nobody's coming here to troubleshoot/complain ?
[ONE General] CheeseyFighter:
Great ROM

First of all: Thank you [MENTION=7388800]SivaVr[/MENTION] for this great ROM! I'm running it since last week and so far it is running smoothly and without any major issues. I just got my Oneplus One back from their support, my screen broke so I used the fresh start to try out an Oreo Build.

I looked through many sites and almost every blog mentioned one LineageOS 15.1 ROM made by [MENTION=6164562]jhalayashraj[/MENTION]. Since the last update was made in January/February, I flipped a coin and decided to try my luck with this neat ROM here.

I was a bit concerned, since nobody mentioned any bugs or errors with this ROM at all, which seemed to good to be true. I was right but so far the list (for me) is very short. However, I'd still like to help SivaVr to improve the ROM so here it goes:

Slow Battery Charge

Before my phone was fully charged in about an hour. Right now it takes my phone about 2h to get from 20% to 95%. It seems to be an issue with some other ROMs as well. It's not too bad, but still it'd be nice to charge this nice piece of hardware in about an hour when time is of the essence.

No Connection to Computer

One real drawback for me is the fact, that the phone is no longer recognized by my computer. I can charge my phone with the adapter, but when connected to my computer, I don't even get a connection jingle from my computer nor a dropdown option in the status bar on my phone. It seems like there is no connection whatsoever. Anyway, the phone seems to get charged, when connected to the computer.

Vendor Image Mismatch

Everytime I restart my phone, this error message flashes. As far as I could find, it's just an annoying message, but nothing more to worry about, bit still a bug to mention:

If you need any more information on this issue, please let me know what you need. I'm happy to provide help for you.
[ONE General] zzjea:
I have been using this ROM for about 2 months without issue. To your concerns:

--Battery- My battery charges as fast as it ever did and have not had slow charging issues

--USB Connection to PC- If you turn on USB for "File Transfer" you will see the connection on the PC assuming you have drivers installed

--Vendor Image Mismatch- I got this in the previous version but it disappeared with the latest version dated 4/30/18

Best Oreo ROM for OPO that I know of. Very happy with the work that has been done by XDA developers (SivaVr) to keep my 2 OPO's current
[ONE General] CheeseyFighter:
Oh shoot. I seem to have downloaded the version before that, I have installed the 4/17/18 -.-

Thanks for pointing that out, I just checked again. Obviously my mistake.

Do you know, can I somehow update to the latest version without loosing everything? Can I just run over it as it is or do I have to make a complete wipe again?

What Kernel do you use? I didn't flash an extra one, so I have installed the one that came with the 4/17/18
[ONE General] zzjea:
First, I always take a Nandroid backup before I do anything and I keep the latest 2 versions in case I need to go back to them (I have the 64GB OPO and have plenty of space).

You should be able to just do a Dalvik wipe and install the latest zip. I do a "dirty" install with new updates to this ROM and all is good.

I do not use a special Kernel. I also re-root during my updates. I use the latest TWRP and set it for multiple zip installs (latest ROM, Open Gapps (Micro) and SuperSU).

When you do a first install from another ROM, you do need to do a factory reset. Some say you should always do that, but I don't want to reconfigure all my settings and apps every time and it has worked for me.
[ONE General] CheeseyFighter:
Yeah, I'll definitely do a Nandroid backup =)

What do you mean by "re-rooting"?

You use Micro? I installed the latest Gapps (Nano). Do I need to install them again after the update?

And why do you use SuperSU? Isn't LineageOS 15.1 capable of "rooting" in the options menu?
[ONE General] zzjea:
If you are not already "rooted" just disregard that reference (it's another option if you want to do some research on it).

Nano is Okay too. I could use that version but have not. Yes, you need to install whatever Open Gapps you want to use. I would strongly suggest you do a multiple install where all the zips are installed at the same time in succession. This is the way I do it and it works for me.

Lineage 15.1 in the ROM we are discussing, does not have on-board root capabilities. You have to add that functionality if you want it. This may be true of all the Lineage 15.1 ROMS. Of course your bootloader must be unlocked first.
[ONE General] CheeseyFighter:
Thank you for your fast and friendly help. I'll do a multi-zip-install, just like last time!

One last thing: Which version of SuperSU did you flash?

SuperSU-v2.82-201705271822

- or -

SR5-SuperSU-v2.82-SR5-20171001224502
[ONE General] zzjea:
The SR5 version. You are welcome.
[ONE General] CheeseyFighter:
Thanks again for the help, everything went smoothly and without problems. I now have the latest ROM.

The good news is: The vendor mismatch error message is gone.

The bad news is: I still can't connect my phone to my computer. If I boot to recovery, the phone gets recognized and I can even transfer files and such. As soon as I boot the system, the phone doesnt even show any options to choose from (normally you can choose between loading, file transfer, etc.).

When I plug in the phone, the computer doesn't flash the plugin-in-jingle and the cell phone either doesn't react at all or the LED is flashing rapidly for a short amount of time and stops. Either way, no connection :/

As for the charging, I still have to try that one, I'll come back as soon as I had to charge it again.
[ONE General] zzjea:
If you are booted into the Android system and using your phone normally, go to

Settings: Connected Devices: USB: (select Transfer Files or which ever choice you want)

If you then go the the "This PC" icon on your PC you should see the device A0001 (OnePlus One).

You can open it and see your Internal Storage files on the phone.

Mine works just as described above.

If this does not work for you, then you probably do not have the appropriate drivers installed on your PC. Or you have not turned on Developer Options and setup Android debugging (ADB interface).
[ONE General] CheeseyFighter:
Thank you, but unfortunately my case is a bit different. When in recovery mode, the phone connects to my computer as you have described above: An icon with A0001 appears in "This PC" and I can access it like a normal folder. That's the reason why I know, that my computer drivers are working and up to date (that and the fact that I have installed them prior the flashing a week ago).

As soon as I boot my phone normally, it doesn't react when connecting to the computer. USB Debugging is active and the phone is also set to MTP. Since it works in recovery mode, I think it has to do with the ROM or something system related, since in recovery it works just fine.

I'm still glad for your help. If I find out anything about it, I'll let you know. I still hope that this ROM will get future updates either way =)
[ONE General] zzjea:
There are only 4 options on the Lineage 15.1 ROM for Connected Devices: USB.

--Charge this device

--Transfer files

--Transfer photos (PTP)

--Use device as MIDI

You said your USB was set to MTP. Do you mean the MIDI setting? What are you trying to do? If I choose MIDI, I do not get a PC acknowledgement but I do on Transfer Files and Transfer Photos.

Also, while in Recovery, what is it that you are doing that requires you to connect to a PC? Do you use Bootloader and is that what you mean when you say Recovery? I'm not sure what you are trying to do between your phone and PC in either case (regular system or recovery). If you can explain what you are trying to accomplish, maybe we can figure it out.

Do you use TWRP for recovery?

I download all of the files (zip) necessary for an install (flash) to a new or updated ROM by using my current phone's ROM (regular ole download). I do not go through my PC to accomplish any flashes (ADB sideload, etc.) although I have in the past. It is easier to download directly from the internet to my phone's Internal Storage and then boot into TWRP Recovery and do all the flashing there from my phone's Download directory, or wherever I have moved it (I use Root Browser to move my zips to an Oreo directory I created for 15.1 files).
[ONE General] CheeseyFighter:
I know. I didn't mean the MIDI setting. Transfer Files = MTP (media transfer protocol).

I use TWRP for recovery and I also used it to copy the OS-files, SU-files and gapps-files onto the phone. That's why I noticed that in TWRP-Recovery the connection (MTP) works and with the OS it didn't.

I'm already past that. I have installed everything I wanted, I just wanted to transfer some music onto my phone. The problem was, that my phone didn't react to the USB-connection with the computer. No sound, no options to choose from (e.g. Charge, Transfer Files, etc.), nothing. It was like the phone didn't realize that there is a USB connection made. It only worked in TWRP Recovery, there I could transfer stuff onto my phone and from my phone to my PC.

I don't know what happened, I tried it a few times, then I paused for a few days and tried again. Then suddenly I heard the connection jingle from Windows and I also had the opitons to choose from and set it to Transfer Files (MTP). The connection was cut off during some file transfer but I could establish it again and it worked again, so I'm not quite sure what the problem was.

(I could eliminate a faulty cable and a faulty board via other cables and devices, so that's not the reason. If I find out what caused this, I'll update this post.)

For the charging: It is still very weird. Sometimes it charges a bit faster than other times, but I have no clue why. All in all the charging duration lies between 2-4h which is way to long. There is not setting I could find to accelerate this, but I know, that the OPO is able to charge from 10%-80% in about an hour, so I think it has to do with the OS.

Does anyone else has the feeling that the picture quality of the camera is a bit worse compared to CM13.1?

I still hope this ROM is not dead since I like it a lot for most of my uses and it is very clean and fast. Keep up the great work!
[ONE General] iofujsiow:
I have issue running astrill vpn with lineageos 15.1. I have the latest twrp installed, fully wiped before flashing the rom, i am able to open the app, but as soon as i type my username and password and then hit 'login', the phone freezes and restart, anyone have any idea how to solve it? resurrectionRemix rom also has this issue i assume its also based on lineageos.
[OnePlus 5 Questions & Answers] saar17:
For more then 3 weeks now Im having a problem with GPS (google play store).

Im using XXX version 9.6 and in that version there was added support for xposed.

Ive did a clean flash and afterward GPS didnt open at all. Ive re install the rom without the xposed support. This time GPS open but no new updates are been shown and when I click on the ¨installed" tab no apps are shown.

Ive tried reinstall the flash again, updating the GPS and the Plat services, delete cache and data and to remove my account and add it again but nothing works.
[G4 General] steadfasterX:
Force SDCARD boot

How-To force booting from sdcard (LG G4 only)

(e.g. when the device is NOT in 9008 / QDL mode)

The easiest method these days is using SALT as here you can simply press a button but if that is not working or not an option here is the physical way:

You may know the 2-pin-bridge method which can enforce the

9008/QDL mode

(on the back of the main board which is shown when disassembling the back cover).

Now you may think: you can enforce that mode by bridging these pins and then you could boot from sdcard as this guide here says 9008 mode is a requirement.

The answer is: NO. This will

NOT

work!

But there seems to be a way (which I personally never have tested!) to force that

sdcard boot

by doing the following.

Be aware: You do this on your

own

risk! Do not cry if something is failing/destroyed/whatever. Its totally up to you to proceed or not but its on your own risk like always when following guides.

prepare the sdcard as described in the above guide

insert the sdcard in the device

remove battery of the device

unplug usb cable

disassemble the back cover by loosen all screws

disassembling the mainboard like described here: fixit guide

on the

FRONT

of the mainboard find 5 (DAT0) and 6 (GND) as shown in the picture:

View attachment 4454585

bridge these both and

while

bridging plugin the usb cable -

WITHOUT TOUCHING

anything with your fingers/body/soul on the mainboard!!!!

Keep thumbs pressed.. it may work if you flashed the correct files, with a matching ARB, in a correct way and [fill-on-on-whoever-u-believe-in] is with you
[G4 General] steadfasterX:
Like I wrote to FWUL so yes to your PC where FWUL is running
[G4 General] commandervadeo:
it seems either ubuntu 17.10 messes something up or salt 3.6-6 stable can't find partitions and i've downloaded two different h812 kdz.
[G4 General] Shepxda:
This is happening to me too?
[G4 General] steadfasterX:
upload the log after extracting a KDZ:

advanced menu -> Logfile -> upload button -> share the link
[G4 General] Shepxda:
No, you see, when you select the KDZ and the location to extract to, no partitions are available to choose from. It's just a blank page
[G4 General] steadfasterX:
Yes. After this do what I said above. Give me the log.
[G4 General] birry:
Hi, I have an H811 bricked this way, as it is bricked, I cannot check antirollback on phone's android.

On the rear label (the one with serial number near to battery) I can see model (H811) and it says H/W 1.0, S/W V10d

I search and saw that there is not V10d kdz for H811, is that data useful? Which kdz will be the best choice to use?
[G4 General] steadfasterX:
do you remember at least if you had installed Android marshmallow or lollipop? Any chance that you have made a TWRP backup in the past? Or did you never unlocked your device?
[G4 General] birry:
Never upgraded Android, I guess it was lollipop. No backups or unlock also, it just bootlooped and I bricked it trying to install a H812 image with lgup (I know which image I tried if it is useful, I remember editing a value because lgup was refusing to install h812 image on the h811, I didn't find h811 image for lgup bootloop flashing fix).

This was my reference when I destroyed the phone [emoji14]

https://www.reddit.com/r/lgg4/comments/45gfg2/dae_g4_series_msm_big_core_disable_tool_guide/
[G4 General] steadfasterX:
well..omg..

ok so the h812 has no ARB. The h811 has. Here is the reason for your hard brick. Do not cross flash random files without knowing what you do really.

Start with 10h which is ARB 1 for the h811: http://downloads.codefi.re/autoprime/LG/LG_G4/H811/H81110H

download the single files or the KDZ and use SALT to extract. then follow the rest of the guide above.

if that

fails

to boot go on with ARB 2 : http://downloads.codefi.re/autoprime/LG/LG_G4/H811/H81110N

I would not recommend to go further then that as u otherwise will increase your ARB for sure.

The next step if that all above still fails would be to use QFIL with proper files for the h811 but beware: there are QFIL files marked as h811/h815/... which in fact are converting your device to a ls991. Best is to search XDA for other users reports which files gave them a good result.

Last but not least if your device is ARB 3 or higher all the above will fail (including the QFIL method) and your only chance to bring back life is the sdcard method described here but using ARB 3 or higher files.

.
[G4 General] Vishnuisgod:
I hate to say it but Im here....

LGG4 - 815eur - new frankenphone (new to me, chinese refurb) - received jan

never had a sim in it. only kept it on to see how long the battery would last in idle mode (airplane mode on, no wifi active)(14 days!) - LGUP to MM

still stock - no google play services installed yet, I was waiting for the UsU (woohoo steadfasterX!!, where do I send my bounty contribution?)

I was downloading all the required files for FWUL / Virtual Box last night, I was going to spend the afternoon getting to know the process/Arch linux, before attempting to mess with my phone... I was adjusting the pull down notification settings and it froze.

I waited till this AM, hoping maybe it would sort itself out. NOPE. Battery at 0.

Im at the logo bootloop with pulsing blue LED.

I have read the entire thread, I wanted to make sure that this workaround is the proper "fix" for this type of bootloop.

I was at v20k IIRC and I know for a fact my ARB was 0.

Im not sure where to dl the required files from several sources Ive tried, dont leave me feeling confident its a trusted source.

Any thoughts on what may have happened?

cheers

ac
[G4 General] birry:
Cool!! It worked like a charm with H81110H file :laugh::laugh::laugh:

Now I can run it into download mode and I could see that info on SALT:

Device model: LG-H811

Firmware (laf): H81120v

Firmware (system): LGH811AT-01-V20v-310-260-APR-25-2017-ARB03+0

Carrier: TMO

Country: US

UsU: no

GPT compatibility: H811

LAF protocol: 1000001

AntiRollBack: 3

I don't want to make a mistake so now that it boots in download mode I will wait for options, which is the best choice now? Updating it with a .tot with LGUP (for the bootloop) or installing other rom (perhaps one with bootloop workaround)

Thanks for your great work!
[G4 General] steadfasterX:
This unbrick will work only when you bricked your phone. It's not an ilapo fix and your description sounds like one. Your best chance is using a modded boot image with just 4 cores enabled. That requires an unlocked phone though.. There is a guide from me to create such boot images here on XDA.

You're referring to what TOT? The one containing just the aboot?
[G4 General] birry:
Yes, anything that patches the bootloop. I am a bit confused with partition structure, the cpu workaround is done editing something in the aboot partition?

I just would like to patch the bootloop (I prefer to have the four tiny cores enabled instead of just one as it normally does and installing stock Rom).
[G4 General] steadfasterX:
There are 2 patches available. The one with tot and the boot image one.

The TOT one which is something between 4 and 10 MB contains just the aboot one and disables the cores in the aboot itself.

The boot image one is made in the kernel cmdline

Both have the same effect.

The difference : the TOT aboot fixes it permanently (as long as you don't reflash a kdz/tot again). So you can flash custom ROMs without needing to care about it.

The boot image adjustment instead does not touch your aboot but needs to be done on ever new boot image you want to use.
[G4 General] birry:
So then I have the patch that just contains the aboot partition (files are of exactly 4mb)

Downloaded from here: https://www.reddit.com/r/lgg4/...m_big_core_disable_tool_guide/

The problem is that there are several models in the file that I downloaded from there but H811 is missing, I cannot find a tot with just aboot for H811, is this really available? I would prefer to write a tot with just aboot that leaves all cores enabled and the faulty ones disabled, not just one core enabled as those tots does.
[G4 General] steadfasterX:
Afaik there is none for the h811 and I highly recommend to not use any of the others to avoid bricking your phone again. So it seems you're stuck with modifying boot images