yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] Monkeyt:
good day to you all, [MENTION=4630246]Hashbang173[/MENTION] could you please, if you have the spare time, generate a new LOS15.1 so i could test and give you some feedback and logs (if you need them)?! I'm at Nougat Stock right now, and will go back to LOS14.1.

ty all =D
[X Style (Pure) Android Development] andromobilogy:
Any new update for the unofficial version? I'm at 14.1-2180127
[X Style (Pure) Android Development] Hashbang173:
FYI: for future unofficial builds of LineageOS 14.1 and 15.1, I will be using the same version of F2FS used in the current official LineageOS14.1 builds. This should resolve some incompatiblities leading to corrupt userdata.

If you are currently on an unofficial build, you will probably have to switch back to official TWRP and may have to format userdata.

---------- Post added at 05:58 PM ---------- Previous post was at 05:56 PM ----------

https://www.androidfilehost.com/?fid=673956719939818950

---------- Post added at 06:37 PM ---------- Previous post was at 05:58 PM ----------

https://www.androidfilehost.com/?fid=962187416754459823
[X Style (Pure) Android Development] andromobilogy:
Thnx for the new update. Should I use the above link with the official twrp or starting with the new ones after the above link you provided?
[X Style (Pure) Android Development] Hashbang173:
You should be able to use the official TWRP with these builds (though you may need to format userdata)
[X Style (Pure) Android Development] Chetan-123:
[MENTION=1689574]HashBang[/MENTION]

I want to update the latest version of los 14.1 to 10/2/18 build

Wht should i do??????
[X Style (Pure) Android Development] GRVsingal:
Sir im on official twrp which means marshmallow, so can i flash unofficial 15.1 and won't face any bootloop and stuff.
[X Style (Pure) Android Development] antariksh:
You still have to upgrade to Stock Nougat. Unofficial LOS14.1 and LOS15.1 are based on Nougat modem.

Only thing that's changed is you don't have to flash unofficial TWRP.

Official TWRP will work for both official and unofficial Lineage builds.
[X Style (Pure) Android Development] AsquareX:
I'm using TWRP recovery by hashbang for Nougat modem. Is it okay to flash 10/02/18 update with it? If not, please let me know what changes should be done.
[X Style (Pure) Android Development] kb8no:
I had a horrible time with twrp 3.2.1-0 official. It bootlooped. It didn't wipe. It didn't install. I finally was lucky to flash twrp unofficial and restore my backup of 14.1. Very unpleasant. Am I doing something wrong?
[X Style (Pure) Android Development] Hashbang173:
To make your device compatible with the F2FS changes you may have to do the following

Erase userdata in fastboot

Flash the official build of TWRP

Format /data in TWRP

Flash the unoffial build from yesterday that has the F2FS changes

Please note that erasing userdata in fastboot erases all of /data (including /sdcard)
[X Style (Pure) Android Development] kb8no:
What is the correct fastboot erase command?

Just to be sure. Format /data to f2fs, yes?

I'm just a little over my head and I'm so close to a brick.
[X Style (Pure) Android Development] Hashbang173:
It should just be

fastboot erase userdata

Yes, format /data to F2FS using TWRP

If worst comes to worst you can just flash the factory image

Switching back to the F2FS used in the official builds is to avoid all this confusion.
[X Style (Pure) Android Development] kb8no:
This is the link to the exact factory image you are referring to?

https://xdaforums.com/showthread.php?t=3704142

To be f2fs or not to be f2fs is not the question, but which variety of f2fs is the issue, yes? Official and unofficial use a different f2fs?

Just to make sure (gun shy), official TWRP is the one you find on the TWRP Clark download page, yes?
[X Style (Pure) Android Development] Hashbang173:
It looks like that factory image should work since it is for XT1575 Nougat

Offical TWRP is the one you find on the TWRP clark download page.

Official builds and unofficial Nougat builds have used different versions of F2FS. With the start of yesterday's build, unofficial builds are now using the same version of F2FS as the official builds.
[X Style (Pure) Android Development] kb8no:
Do these f2fs versions have names by which they are referenced more than just "official" and "unofficial"?

In TWRP I find you can format Data two different ways:

Wipe > Format Data

Wipe > Advanced Wipe > click Data > Repair Change File System > Change File System > F2FS?​

Are they the same thing? Which one are you assuming?

Which Gapps 8.1 do you use/recommend? Link? OpenGapps site only has 8.0.
[X Style (Pure) Android Development] Hashbang173:
You can see my recent change to F2FS here: https://github.com/HashBang173/andr...mmit/4a50ee744de6098614b72876b50f3dbf5ac6a381

I think either of those ways to format data should work

I've used unofficial builds of OpenGapps for 8.1: https://xdaforums.com/android/apps-games/arm-unofficial-opengapps-builds-android-t3743495

Keep in mind that if you want to use a LineageOS 15.1 for clark, there are still some bugs (particularly camera is not yet working)
[X Style (Pure) Android Development] kb8no:
Victory! Thank you [MENTION=4630246]Hashbang173[/MENTION] so much. Now on Official TWRP 3.2.1-0 and official f2fs with LOS15.1-20180210. Sigh. Install went smooth. Google login 100% functional.

Works: data, WiFi, BT, Text, SMS, Gmail, WiFi tether, streaming, GPS, Play Store, phone calls in and out, native explorer. Root explorer copying file to SD aborts right at the end but native explorer works. Not Working: camera as advertised. Graphical stutters here and there.

Pretty exciting to be on O! This could be good enough to be a DD if camera didn't matter.
[X Style (Pure) Android Development] TheYoz:
Nothing to see here...still learning how to read and search.
[X Style (Pure) Android Development] kb8no:
We should be able to dirty flash your next update over this 15.1, yes?

Because I want to learn, what are the camera issues you are facing?

Can you start a thread for 15.1?
[X Style (Pure) Android Development] ShapeShifter499:
So official build of TWRP 3.2.1-0 is working now for us on Nougat?

---------- Post added at 07:51 PM ---------- Previous post was at 07:49 PM ----------

Where is the latest fully working LineageOS 14.1 or 15.1 rom for us with Nougat?
[X Style (Pure) Android Development] edison0354:
Does anyone can enable Camera2 API on this ROM?

I added the line in build.prop with magisk module, then camera HW just can't be detected in system, even AIDI64 reports there's no camera on this phone...
[X Style (Pure) Android Development] kb8no:
Official TWRP is configured for a specific "official" version of f2fs. However the early Nougat LOS ROMS both 14.1 and 15.1 needed an f2fs variant and therefore a special "unofficial" TWRP. The news is that the latest builds that [MENTION=4630246]Hashbang173[/MENTION] dropped on 20180210 of 14.1 and 15.1 have been upgraded to work on the official f2fs and hence we have to move to the official TWRP that it requires.

Here's the Nougat 15.1 builds and use the most recent build with official TWRP 3.2.1-0.

https://androidfilehost.com/?w=files&flid=244563

The latest 14 1 Nougat build is a few posts back.
[X Style (Pure) Android Development] TheYoz:
Running the latest unofficial with twrp 3.2.1 and I'm unable to wipe dalvik/cache in recovery. Wasn't this suppose to be fixed or did I misunderstand?
[X Style (Pure) Android Development] Punkard85:
Im having trouble getting any official twrp to load after installing the unofficial 3.1.1 version for nougat compatibility, anyone else as well?

Update: Nvm, formatted back to ext4, reinstalled and loaded just fine.
[X Style (Pure) Android Development] dzidexx:
I don't use LOS & TWRP 3.2.x but I understand it like this:

Install twrp 3.2.1, reboot recovery, format cache & data to ext4, reboot twrp, format back to f2fs, reboot twrp, install LOS.
[X Style (Pure) Android Development] leonardoafa:
Maybe a factory reset!? Are you sure your blacklist is empty?
[X Style (Pure) Android Development] db3:
I factory reset before installing cm14.1. the blacklist appears empty; I definitely had numbers in there before, but I assumed that the data was wiped and i didn't restore it. I tried downloading the google phone and contacts apps to see if there's a difference, but they seem to access the same data... I also checked options associated with the contact and the option to route all calls to voicemail isn't selected.
[X Style (Pure) Android Development] leonardoafa:
Try to reset network settings.

See attached image below
[X Style (Pure) Android Development] seang:
ive been on the 1st nightly since it dropped.

clean flash.

i unplugged this morning. about 7am, and its now about 330. i have 71% battery left with moderate use.
[X Style (Pure) Android Development] db3:
Thanks, I tried, but it didn't seem to work. I'll try removing the contract and adding back manually. Fingers crossed...
[X Style (Pure) Android Development] Spirotot:
Got it working. Had never tried to use NFC before, turns out the adhesive-backed piece of metal for my car mount was blocking NFC for some devices I was testing with. Removed the panel, now all the devices work. SWEET. Really liking this ROM, and would have still liked it even if NFC didn't work. :)
[X Style (Pure) Android Development] jphuff:
Just realized that my cellular data isn't working. Realized on build 12/07/2016. Tried turning off/on mobile data, turning on/off airplane mode, restarting, reverting to 12/06/2016, update device config which never seems to finish, in developers options I turned on cellular data always on, and resetting network settings. In SIM status it just says searching. Might explain battery drain, in part, on my device.
[X Style (Pure) Android Development] Gulfstream 650:
Just flashed the 12/9 nightly, I think they fixed the camera lag...it seems to fire right up now. Still have issues connecting to an encrypted wifi router but can connect to an open one. The flashlight is now working too. Feels real smooth, so far I'm real happy with it...time will tell. **Edit, I'm an idiot, can't connect to an encrypted router with the wrong password :o, wifi is working fine**.

---------- Post added at 10:29 PM ---------- Previous post was at 09:54 PM ----------

Still appears to be a hotplugging issue, both the big cores will go offline when idle but none of the littles will according to kernel Adiutor and there's no minimum cores little control.
[X Style (Pure) Android Development] JohnMcW:
Sd Card Log ... A little further

Well, here is a cat log for the 12-09

exFat for External SD Card is a little better,

Titanium backup allows you to select the storage and pick the folder,

it doesn't allow anything to be restored.

CM File manager still doesn't let you look at the sd card

Settings storage, lets you look at the ext sd card and pick folders, but it says all the files are 0 bytes

and nothing can be read.

[MENTION=4630246]Hashbang173[/MENTION]
[X Style (Pure) Android Development] Sagar_1401:
Toggle flashlight still not working on latest build

Still heating issues...

And battery drains very quick..
[X Style (Pure) Android Development] Cdub1976:
For the flashlight, edit the tile from one position to another then try again.
[X Style (Pure) Android Development] Sagar_1401:
Worked man thanks...
[X Style (Pure) Android Development] Gulfstream 650:
Sagar, the flashlight toggle is working for me with the new build (12/9)

No heating issues but I haven't pushed it real hard either

I'm getting decent, but not stellar battery life.
[X Style (Pure) Android Development] OCmylife:
The little Cores aren't meant to be hotplugged, as it would be a big performance hit.
[X Style (Pure) Android Development] Gulfstream 650:
Well, that could be, I'm not sure how the Qualcomm solution to hot plugging works. I was running CM13 prior to this ROM and using the Purebliss kernel which used their "hot brick" driver that allowed control over the little cores and the hot plugging of them. You could idle (and deep sleep) with just one little core running at 304 MHz, great battery life and no performance hit as it would activate additional cores instantly as required.
[X Style (Pure) Android Development] Bwangster12:
Those that were complaining of poor battery life....are the latest builds any better? I switched to Cypher because I was experiencing same thing.
[X Style (Pure) Android Development] Sagar_1401:
No bro not good... It still over heats and battery drains tremendously fast..
[X Style (Pure) Android Development] gabrielsena:
Battery going very, very, fast :crying:
[X Style (Pure) Android Development] fdc77:
camera issue

CM 14.1 09/12

impossible to capture slow motion video with every camera app.
[X Style (Pure) Android Development] Sagar_1401:
Yes it doesn't work it does record but when played the slowmo effect is not seen...
[X Style (Pure) Android Development] TheYoz:
The strange thing is I fastboot flashed Stock Nougat back to the phone (where [MENTION=1689574]HashBang[/MENTION] stated to avoid confusion because it's based on f2fs) flashed 3.2.1, installed the latest unofficial 14.1 and after setting my phone up with all apps, I normally clear dalvik/cache. Executing this in TWRP reboots the phone back to LOS.
[X Style (Pure) Android Development] Alibaba0101:
So I'm a little confused here. I am running stock los 14.1 nightly with twrp 3.1.1-0 with MM modem. When I tried the official twrp and it wasn't able to backup my rom so I reverted back to 3.1.1.0. Does this mean the new los official rom now supports the latest twrp? Do I need to reformat my data partition?
[X Style (Pure) Android Development] stevejohnson42:
I was unofficial 14 and the unofficial TWRP ; started with going to the bootloader and trying to fastboot the Nougat stock rom - had failures at "fastboot partition gpt.bin"

So - next shot ; installed the official TWRP ; and used the suggestion made by kb8no to In TWRP "I find you can format Data two different ways: Wipe > Format Data"

From there did a an install of the 20180210 unofficial 14.1 build ; used BeansGapps-Mini-7.1.x-10170725 and went from there

Updated -- when I rebooted from recovery it went to the bootloader ; apparently I missed a step -- I went back ; reflashed the unofficial TWRP and restored my backup ; will review this again when I have time and try again -- even with that it goes to bootloader ; I scroll to START and let it go - mess with it later

Last update - figured out why I keep going to bootloader ; I forgot to go back and use fastboot oem fb_mode_clear --
[X Style (Pure) Android Development] Monkeyt:
[MENTION=4630246]Hashbang173[/MENTION] Sorry for the delay, i tried to install both versions (the one most recent i asked to you and the older one (29-01-18 i think)) and in both my modem (SIM) can't work and every time it changed the screen it would flick a red borderline on the screen, i came back to stock nougat

PS: In both versions tried, i used first the Stock nougat then i tried stock MM without success.

PSS: if you want i can reinstall any release as you instruct, however i saw in the /r/LineageOS that LOS15.1 would be release by the end of this month (23/02/18)

Ty for the patience =D
[X Style (Pure) Android Development] justmoto92:
Hey! Do you have the link to the site where they mentioned about the LOS15.1 releasing by end of this month for our Clark? Thanks! :)
[X Style (Pure) Android Development] Breezeblocks:
Loving HashBang's unofficial build right now, (I'm on 20180127) but I seem to be having a problem with making/receiving phone calls. Whenever I call someone all I get is total silence and then it automatically hangs up. I restarted the phone and it seemed to fix the issue briefly, but a few minutes later it went back to complete silence and hanging up. I noticed that "Do Not Disturb" automatically turns on too when I try making a call, turning it off doesn't seem to do anything. I have the unofficial TWRP flashed along with GApps 7.1 ARM64 nano. Does anyone know how to fix this? Thanks.
[X Style (Pure) Android Development] kb8no:
I took the Nougat OTA. You are on N firmware, not M? I flashed the image of TWRP 3.1.1 unofficial using TWRP official. I flashed LOS 7.1 20180127 with a complete clean flash. It works fine with none of your problems. Try a complete wipe including data and try again is my suggestion.

However, LOS 7.1 20180210 is better with official TWRP if you can move there. Follow Hashbang instructions above.

fastboot erase userdata

use fastboot to install official TWRP

complete wipe

use Wipe > Format Data to reformat data with f2fs

Flash LOS 7.1 20180210, Open Gapps 8.2recommended by Hashbang, and Magisk all at once

This worked for me and is better than the old LOS 7.1

And if you can get by without a camera, 20180210 Oreo is amazing. If you are already on LOS 7.1 20180210 then all I did was a complete wipe and install with Gapps.

I cleaned up this post so sorry if we cross posted.
[X Style (Pure) Android Development] Breezeblocks:
Thanks for the reply. Just erased user data in fastboot, flashed official twrp 3.2.1. Advanced wiped cache, system, and data, as well as going into format and wiping the data there. Then flashed unofficial 20180210, restored everything with Titanium backup. Unfortunately the problem seems to still persist.
[X Style (Pure) Android Development] kb8no:
We gotta figure this out. Did you format data with f2fs using TWRP 3.2.1 official?
[X Style (Pure) Android Development] Breezeblocks:
Ha ha I appreciate your enthusiasm. Thanks! I'm sorry, I'm pretty new to all this, not quite sure what it means to format data with f2fs. After messing around some more on the phone, I find that certain numbers will work fine while others won't (i.e. when I called my bank I couldn't hear anything, but the VA and some other numbers worked fine). After restarting the phone the numbers that worked didn't seem to work anymore and the others seemed to work (my bank number worked now, but with the VA I couldn't hear anything on the other end). Maybe it might be an issue with my carrier (T-Mobile)?

What I did in order:

-Backed up everything with Titanium.

-Booted into fastboot with adb and erased user data using the line HashBang posted.

-Flashed official TWRP 3.2.1.

-Booted into "Recovery Mode."

-Went to "Wipe" and chose the "Format Data" option, typed "yes."

-Went to "Advanced Wipe" and wiped data, system, and cache.

-Flashed unofficial LineageOS 20180210 with GApps arm64 7.1 nano 20180207 and SuperSU 2.82.

-Started phone and restored my backup with Titanium.

Thanks again for all the help!
[X Style (Pure) Android Development] kb8no:
don't use Titanium. It is tedious but it has to be CLEAN. I gotta go to work. I'll look over your post later.
[X Style (Pure) Android Development] Breezeblocks:
Ok thank you, so should I wipe everything in advanced wipe and format data then? Or just proceed with everything and not use Titanium? I saw in your other post to instal GApps 8.2, where can I find that? Also Magisk is root right?
[X Style (Pure) Android Development] RBTT:
Just flashed 15.1-20180210. So far so good - enjoying Oreo for fist time. Everything seems good beside camera not working.

Thanks [MENTION=4630246]Hashbang173[/MENTION].
[X Style (Pure) Android Development] kb8no:
Its awesome! I'm now using it as my DD.
[X Style (Pure) Android Development] Monkeyt:
I think it's more a rumor, however i saw in the Official Reddit, a guy posted about LOS13 being deprecated and a user (not oficial LineageOS Team Member) dig through and predict a date, the funny thing is harryyoud (a member) posting a emoction, in the end the predicter deleted his post however i really have a good memory for "trash" things (like the release date for LOS15.1 :p:p)

The reddit link: https://www.reddit.com/r/LineageOS/comments/7x2s4v/lineageos_130_has_been_deprecated/

thats why i ask you [MENTION=4630246]Hashbang173[/MENTION] this is "true" or we are going to wait more (i really do not have problem with this)
[X Style (Pure) Android Development] antariksh:
Lineage 15.1 was on staging. Think of it as more like beta. Means they were still testing out the 'source code of OS'. Adding/removing features.

They have started unstaging the LOS15.1 two days ago. That means the source code we use to build LOS15.1 is in stable environment, not the actual device build for clark.

For the device build to be 'official' or 'officially upgraded', it has to be fully stable, no hardware feature malfunctioning/missing, enforcing SELinux etc. LOS team has recently realeased a 2 paged charter for it.

So when they officially make the announcement for LOS15.1, only the devices which are passing the charter requirements will be available to download officially.

Talking about clark, Oreo is still under development. But the unofficial builds are available to download. Only thing that's not working is camera. But it's far away from being stable or official.
[X Style (Pure) Android Development] Breezeblocks:
I tried everything you posted, formatted the SD card as well, didn't restore anything with Titanium. Still having problems with phone calls, I wonder if it's carrier related?

EDIT:

I went into mobile network settings and turned off enhanced 4G LTE Mode, this seems to have solved the problem.
[X Style (Pure) Android Development] olswede:
Try disabling "Enhanced 4G LTE Mode" in network settings.

Just doing that cleared up calling issues in my phone.
[X Style (Pure) Android Development] kb8no:
Geez. It was carrier. What carrier do you have?

So now you are on Nougat firmware, TWRP official, f2fs "official", and LOS 14.1 20180210. BAM. You have arrived. Try 15.1 if you don't care about camera, it is a rush. Just full wipe and flash ROM, Gapps 8.1, and root. I posted Hashnang download link above.

My bad. Open Gapps 8.1 unofficial and not 8.2 for LOS 15.1. There is no 8.2. You use Open Gapps 7.1 official right off the Open Gapps web site for LOS 7.1. Hope i did not lead you astray. Use Hashbang gapps link for 8.1 above. I think it doesn't matter, Magisk or SuperSU. The former is popular right and what worked for me.

Ciao
[X Style (Pure) Android Development] kb8no:
I don't have that option. Is it carrier dependent? (Note I don't have keyboard problem)

Addendum after a little Google action. It is voLTE. I think it is carrier dependent. I found some dialer's do not work with voLTE dialing even if it is enabled.
[X Style (Pure) Android Development] Hashbang173:
So VoLTE is causing calls not to work on the unofficial build? If you can capture a logcat of the issue, I'll try to look into it.
[X Style (Pure) Android Development] TheYoz:
I'd occasionally get MMS issues too. "Message not sent destination address invalid"

---------- Post added at 06:45 PM ---------- Previous post was at 06:44 PM ----------

To fix it I delete the APN setting and reset to default.
[X Style (Pure) Android Development] neeraj@5:
Volte enabled???