yashsingh1/xdaforums huggingface dataset:
[Sony Xperia M] droncheg:
I'm stuck with strange error and update repos doesnt help. Sadly, google also doesnt know about this error. If only someone can help me with this:

I'll try to compile after resolving compile problem (see above). Also, HDD not so important - much more important is RAM (~10GB) and CPU cores (much is better, i'm using 8x1.8GHz Xeon E5-2603). With this configuration clean building lasts 4-5 hours, update building - 15-20 mins.
[Sony Xperia M] Nicklas Van Dam:
I think it's from device tree and kernel source , I'll looking at problem when I'm free.

That error from oms patch, I've same problem too when building oms. I think github already have some fix about that problem. Try to google it, for now build with stock first.

I've full day class now :crying:

And one more, my laptop is quad core 2.2Ghz (Intel Core I3 2nd 2328M) with 6GB RAM, and you're is octa core :eek:
[Sony Xperia M] A7.Rtb:
Hello there

Can I suggest something ?

I think It's a good idea to make a weekly pure build (without OMS support) between the OMS nightly builds if possible.

l think It's good for those who prefer the pure LineageOS experience.

Thanks for your time.
[Sony Xperia M] droncheg:
Today i've compiled clean LOS nicki firmware without OMS patchset. Here is lineage-14.1-20170830-UNOFFICIAL-nicki-los. Since today i will compile clean LOS instead of LOMS (till they fix compile error).
[Sony Xperia M] didyou:
lineage-14.1-20170830-UNOFFICIAL-nicki-los.zip

los? what it means?
[Sony Xperia M] droncheg:
It means LineageOS without OMS patchset =)
[Sony Xperia M] A7.Rtb:
Thank you so much for your great work, you are the best.
[Sony Xperia M] Nicklas Van Dam:
So stock lineage still work without any patch from OMS? That's good, then we still have hope to compile lineage 14.1 continuously. [MENTION=7670323]droncheg[/MENTION] should we wait lineage 15 to stable release or want to try to compile it now? But I'm not sure about it still it's still on experimental stage, and I was failed to compile slimroms with Oreo.:confused:
[Sony Xperia M] emc02:
Thank for developing on our good old devices.

I've tried to flash lineage-14.1-20170830-UNOFFICIAL-nicki-los over latest official version. The device booted and starts to "finish android update", but it did not finish this process for 2h+ and most of the apps don't work (crash on start) and sms messages, caller lists etc... are gone.

I thought that this update should work directly over offical lineageos because it's pure lineage, or?!
[Sony Xperia M] droncheg:
:confused: Again. My builds incompatible with official builds, as all others (RR, XOSP etc)
[Sony Xperia M] Nicklas Van Dam:
what's problem? you can't build stock lineage? :confused:
[Sony Xperia M] droncheg:
If you give me stock signing key then it will be =)

Current LOS 15 ported devices list - there is no Xperia M yet :(

BTW, NUI just released 7.3 :good:
[Sony Xperia M] hhjadeja007:
Can you try to port LOS 15?
[Sony Xperia M] Nicklas Van Dam:
I think it should wait for any device get official release for Oreo, then we can try to port it. To avoid much error from unofficial build of lineage itself

---------- Post added at 10:04 AM ---------- Previous post was at 10:01 AM ----------

Stock signing key? What? I mean build stock lineage with [MENTION=4343949]PecanCM[/MENTION] device tree and our stock kernel, is that still error?

If error, what error that show up?

NUI release new build? That's great ;)

I'm building ROM with F2FS support now, I'll report soon when it's success or not to build.
[Sony Xperia M] droncheg:
If you look at my commits on device tree you can see that all diffences is camera-related stuff (Snap and Camera2 removal, OpenCamera include). My kernel commits also same 1:1 as LOS kernel and just synced to be updated as LOS kernel. And there is no error build for my LOS builds (not LOMS, which i stop build now till LOMS devs will fix that). I found a forked project CustomLOS which also uses LOMS patchset, and they fix that problem. I'll try use their commits to build LOMS, but later.

And again, my friends, any unofficial builds will be incompatible with latest official LOS for C1905 (lineage-14.1-20170427-nightly-nicki-signed.zip). ANY! And it's incompatible due to different signing key, which applied to all packages in firmware. If any OPs or DEVs will explain more exact - that would be great =)
[Sony Xperia M] Nicklas Van Dam:
Sorry if my word insult you, I don't mean that anyway. I'm just asking if you can still build stock lineage or not, if from OMS then I don't know . because I've same problem too when it build, I'll looking up later when I'm compiled to build. My laptop need 7 - 12 hours to only build 1 ROM for 1 Device, with unknown know about status will success or not.

About your device tree it's fine, you only make change on camera build. And try to revert intrusive led if not make any warning and error.

Anyway our device read as "Nicki" I think it should read as our device type re-generately , are you make change on device type or number?

And remind our forum developer is retired or decrease much at this time, so not much active at here to fix device problem at fast or properly. I'm work at kernel for now, I'll try to submit kernel patch to lineage again if I can.
[Sony Xperia M] A7.Rtb:
Excuse me for my quistion, but what did you mean with "I'm work at kernel for now, I'll try to submit kernel patch to lineage again if I can" ?

does that mean you'll try to restart official lineage support for our device :D ??
[Sony Xperia M] emc02:
Hello,

maybe I can help at this point, I've a Quadcore machine with 16GB of RAM and Debian 9 on it. I am now trying to build original lineageos for first time and it is at 10% at the moment.

I've no ideas about kernel development and so on, but if you can help at this point I can build it and we can support our devices together. I think that's the point of a community ;)

edit: make completed successfully in 01:33:02, I am testing now!

edit2: second run finished in 00:22:25! I think that's good ;)
[Sony Xperia M] emc02:
Good morning ;)

My build of lineageOS (lineage-14.1-20170902-UNOFFICIAL-nicki.zip) is working fine, but only with clean install!

With dirty flash over lineage-14.1-20170427-nightly-nicki-signed.zip I've got the same problems like I had with dirty flashing the build from [MENTION=7670323]droncheg[/MENTION] (lineage-14.1-20170830-UNOFFICIAL-nicki-los).

But I think its not depending on official-unofficial or signed and unsigned, I think there was some major change in lineageOS since our last official build. Because the dalvik/art cache generating process changed. In older builds it was done during boot and now it's done after boot in background task and you can use your phone during this time normally. So I think this is the problem.

So I've done a titanium backup of my apps, then did a clean install with opengapps pico and rooted my phone and now everything works fine.

As said before to [MENTION=5608002]Nicklas Van Dam[/MENTION], I'll build the ROMs, but I don't know how to change things in kernel and so on. But I want to learn ;)
[Sony Xperia M] Nicklas Van Dam:
at the moment no, i'll only update several patch of CVE. during i'm still work on custom kernel and F2FS ROM, i'll priority for F2FS to complete first and try to port oreo to our device. But i can't give full promise about oreo in our device, because i'm still less about porting new device with outdated device tree.

I'll looking it around and ask about how to solve to another

---------- Post added at 04:41 PM ---------- Previous post was at 04:40 PM ----------

good if you can do that, can i ask you something about this?

and [MENTION=2716968]emc02[/MENTION], can you please build lineage with this device tree link, replace your current device tree with this device tree. and tell me a report about success or not for building, thanks :)
[Sony Xperia M] A7.Rtb:
Ok sir, thank you for your work, and good luck with custom kernel and F2FS ROM.

And for Oreo, [MENTION=2233641]AdrianDC[/MENTION] has just ported Aosp 8.0 for Xperia SP, I think the devices are somewhat similar, maybe you can find something helpful in his work.
[Sony Xperia M] emc02:
of course you can ask me ;)

I just followed that guide to build lineageOS. How can I use another device tree?

In the guide it was just:

source build/envsetup.sh

breakfast nicki

how to replace that or use just another tree?

just clone everything to /android/lineage/device/sony/nicki/ ? Or is it possible to create and build another device tree? What about the proprietary files? Are they still the same?

....

Trying this way aborts with that error:

Checking build tools versions...
build/core/base_rules.mk:183: *** device/sony/nicki_orig/camera: MODULE.TARGET.SHARED_LIBRARIES.camera.qcom already defined by device/sony/nicki/camera.
build/core/ninja.mk:166: recipe for target '/home/nas/android/lineage/out/build-lineage_nicki.ninja' failed
make: *** [/home/nas/android/lineage/out/build-lineage_nicki.ninja] Error 1
make: Leaving directory '/home/nas/android/lineage'

#### make failed to build some targets (16 seconds) ####
[Sony Xperia M] droncheg:
I'm builded succesfully with your device tree and pure clean LOS. Here is lineage-14.1-20170903-UNOFFICIAL-nicki-nicklas
[Sony Xperia M] emc02:
I'll be very thankful for some instructions how to add a additional device tree and build with that.
[Sony Xperia M] Nicklas Van Dam:
Oh great, thanks . and then this is for first build test for F2FS ROM :D, I'll download and test it now. Will report it soon, but remind for F2FS support, it need kernel that already support F2FS file system and TWRP support too.

I'll looking at TWRP support for F2FS later if this test is complete :), anyway, thanks [MENTION=7670323]droncheg[/MENTION] :D
[Sony Xperia M] droncheg:
I've created new manifest repo with your device and kernel, but your kernel doesnt ready for automated building of firmware. It contains ccache and custom kernel config name. I can fork your kernel to adopt for this and make building compete firmware much easier (especially for newbies).

PS: so many forks :silly: github requires creating organizations for multiple fork of same projects =)
[Sony Xperia M] Nicklas Van Dam:
for custom kernel, you can remove it for building a rom. and for kernel config, you must change it on device tree commit. try to configure and remove ccache to recompile.

or just rename my defconfig to stock lineage.
[Sony Xperia M] Nicklas Van Dam:
F2FS on data

[MENTION=7670323]droncheg[/MENTION] , okay F2FS work for data partition. Thanks to compiled it, now i need to configure cache partition to use it if need. i'll need your help again for compile it, after this then we can try to compile lineage 15 if not happen much problem.

i'm already add commit on device tree, try to sync and re-built again (please ;)). if this work then cache can use f2fs.

and for speed to compare, isn't really different enough from f2fs and ext4. but during f2fs formatted new more size after use. then our internal storage will have less internal storage space from ext4 itself.

F2FS

EXT4

I'll add documentation later, and i'm not sure for cache using f2fs. during our cache partition isn't really big, but we can just try it or abandon it. so just only use data for f2fs, and i'm not recommended to using f2fs for system.
[Sony Xperia M] droncheg:
Done lineage-14.1-20170904-UNOFFICIAL-nicki-nicklas.zip. I forked your device tree to add custom kernel config for automated building and install ccache in build environment to avoid kernel forking too. So, it's include your kernel and device tree.

Build manifest: here

Device tree: here
[Sony Xperia M] Nicklas Van Dam:
Oh okay, thanks to build. Sorry to make you busy with my request, I'll test it tomorrow for that. I think we need to talk in other social media
[Sony Xperia M] Nicklas Van Dam:
F2FS for cache works !

This need terminal command to format from TWRP - advanced - terminal

Note : unmount your cache first before do this command

Command :

mkfs.f2fs /dev/block/mmcblk0p26

And wait until process finish, after finish try to mount storage and go to wipe menu and select repair / change file system. Then select cache and see about current file system and size, if size 0 mb then try to change file system for cache to ext4 (not this only reformatted your cache to f2fs because TWRP can't format f2fs for cache. After format complete, go to mount option and mount cache.

Check data partition with unmount and remount data partition and go back to repair file system and choose cache to check f2fs size. Then you're safe to reboot and try f2fs on cache.

F2FS for data (TWRP)

Go to wipe option, select change or repair file system and choose data then change to f2fs and after finish. Check data partition with unmount and remount data partition and go back to repair file system and choose data to check f2fs size.

This need kernel that already support for F2FS, current supported kernel :

- Mimori Kernel v4.3 RC2 (@droncheg based ROM 20170905)

- NUI Kernel v 7.3 (@ngxson Latest Version)

I'll add documentation after this, it's midnight here xD.

Have try ;)
[Sony Xperia M] hhjadeja007:
Can I change this with any rom or just with lineage os?
[Sony Xperia M] Nicklas Van Dam:
for now it's only for lineage from [MENTION=7670323]droncheg[/MENTION] build, because it required support from device tree and kernel source. it can be applied to all ROM. But ROM must re-build and using f2fs patch to device tree and using kernel that already support for f2fs.

;)
[Sony Xperia M] hhjadeja007:
Okay. So, droncheg's new build already contains mimori kernel or do I have to flash it separately?
[Sony Xperia M] Nicklas Van Dam:
Yes, it's already contain since build 4 September ;)
[Sony Xperia M] emc02:
I guess it works only with clean installation?

Is there something else to do, or just wipe system and data and flash the new ROM with F2FS support?
[Sony Xperia M] Nicklas Van Dam:
You're don't need anything to use f2fs, flash this ROM, reboot to recovery and format only for data and cache to f2fs using my method upper of this post. And you can use f2fs in your device ;)
[Sony Xperia M] droncheg:
To test F2FS you need atleast format some partitions, so it's better do at new clean install.
[Sony Xperia M] Nicklas Van Dam:
And during me and [MENTION=7670323]droncheg[/MENTION] built this ROM with pre-built of test build custom kernel, then this will need custom kernel manager to control your kernel.

I'll try to apply F2FS patch to stock kernel, so [MENTION=7670323]droncheg[/MENTION] can build using stock kernel instead of my kernel.

Building stable ROM with custom kernel, isn't my best choice here.
[Sony Xperia M] didyou:
Do you know a valid way to install applications directly on the memory card?
[Sony Xperia M] Nicklas Van Dam:
I think that's isn't possible to do, whenever we set to force app to install in external storage. App will still stored to internal storage as first step of installation, and when installation is complete. Then it'll move silently to ext sdcard, so algorithm it's still stored to internal.

I don't know for that point, but that method will applied in almost all app management.
[Sony Xperia M] emc02:
OK, that are two different answers, but I'll try it. Is it really faster than ext3/4?
[Sony Xperia M] Nicklas Van Dam:
Yes, it's faster but isn't stable enough for speed. It's experimental and can use as daily usage.

My answer and [MENTION=7670323]droncheg[/MENTION] is basically same ;)
[Sony Xperia M] didyou:
%100->%23 last update and Mimoria Kernel. Nice :)
[Sony Xperia M] didyou:
When I use Opera Mini, the phone is locked because I want to switch between the tapes. When I take out the battery, I have a drop in charge. I hope you are interested.
[Sony Xperia M] Nicklas Van Dam:
Drop on charge? Try to re-calibrate your battery, are you've root access?
[Sony Xperia M] didyou:
When the battery is in good condition and only locked in the Opera, then I remove and install the battery.
[Sony Xperia M] hhjadeja007:
Today I tried lineage os Nicklas build and changed partitions to f2fs. For comparison between ext4 and f2fs, I installed subway surfers and checked app opening time. Before it was 42.4 sec and after it is 32.4 sec now. I have to use this rom a bit more to comment on stability compared to stock lineage but still it seems like it's like good improvement. Thanks [MENTION=5608002]Nicklas Van Dam[/MENTION]
[Sony Xperia M] Nicklas Van Dam:
f2fs will improve app r/w speed for data and cache, are you use it for adopted too? or only for data?

in my experience, i'm used on adopted storage and don't try to make your storage almost full. Or your r/w speed will decrease sometimes and you'll have problem when entering twrp (it will need much load time to load all your data on f2fs partition).

For twrp that from twrp current bug, so i can't fix it. for adopted, i'm still don't know why. I think that from old formatter tool, so i'll look for how to resolve it later.

View attachment Mimori_Kernel-nicki-signed.zip

I'm already sync f2fs to latest stable branch on that test kernel, you can try to flash it if you still use f2fs. I'll try to compile f2fs formatter from git.kernel.org later.

For back to ext4, go to TWRP - advanced - terminal

and type this command

make_ext4fs /dev/block/mmcblk0p26 (this is for cache)

make_ext4fs /dev/block/mmcblk0p26 (this is for data)

this command will re-format your data and cache to ext4 if you're use f2fs.

Anyway, thanks to test it ;):good:
[Sony Xperia M] hhjadeja007:
I want to flash your zip. But do I have to change to ext4 before flashing the zip or I can flash it directly? Thanks
[Sony Xperia M] Nicklas Van Dam:
you can flash it directly if you still use f2fs, that method only for if you want to revert back to ext4.
[Sony Xperia M] didyou:
The phone automatically silences itself after you have made a phone call in the last two updates.
[Sony Xperia M] Nicklas Van Dam:
auto silence? like what? can you give clear explaination?

i'm using 18 september build, not find any problem.
[Sony Xperia M] didyou:
When I make a call while my phone is silent, it automatically exits silently. More precisely, quiet mode is disabled when it comes out of disturbance mode.
[Sony Xperia M] didyou:
İ'm download to Lineage 15. But not installed error 7 from TWRP. İnstalled from CWM recovery but not open phone.
[Sony Xperia M] Nicklas Van Dam:
that's still experimental, why you downloaded it?
[Sony Xperia M] didyou:
I did not know. Also, there was no harm, just the load.
[Sony Xperia M] Nicklas Van Dam:
oh okay, i'll notice or make a thread if that already completed.

So far ROM only builded, but not working
[Sony Xperia M] droncheg:
Please don't try to install 15.0 LOS builds. It's still very experimental and cause bootloops. I'll notice further when builds will be stable.
[Sony Xperia M] didyou:
When I try to switch between the tabs in the Opera Browser, the phone stays locked. [MENTION=7670323]droncheg[/MENTION]
[Sony Xperia M] Nicklas Van Dam:
What's locked? Go to lockscreen interface?
[Sony Xperia M] litemaster:
I experience this too with the 20170919 build. Usually, I keep my phone in silent mode (vibrate only) all day long.

1. My alarm (Sleep as Android) puts the phone in DnD at night, but when it turns off DnD in the morning, I'm in ringing mode and have to manually put it back to silent.

2. Phone is in silent mode, I make a phone call (outgoing), phone is in ringing mode after call is finished.

I didn't experience this with the 20170818 build I had installed before.

Minor annoyance, otherwise 20170919 appears to be very stable. :good:
[Sony Xperia M] didyou:
The intruding phone freezes completely and I have to throw it to reset.

I am currently living this problem with the last few updates.
[Sony Xperia M] Nicklas Van Dam:
I'm not really understand with your problem, you're not installing any custom kernel or magisk module or closed right?

Try to send logcat and last_kmsg here, and we'll check it
[Sony Xperia M] hhjadeja007:
There is a lineage 15 available again. Is it safe to download?
[Sony Xperia M] droncheg:
nope)
[Sony Xperia M] Nicklas Van Dam:
Nope, it's still experimental. But I can't test it for now
[Sony Xperia M] didyou:
I'm looking forward to Lineage 15. In addition, there is a root error in recent updates, only ADB appears in options.
[Sony Xperia M] iampatricktan:
How come after my first reboot my device is stock to Sony Logo and then bootloop?
[Sony Xperia M] iampatricktan:
How come my device is on bootloop after flashing AddonSU??
[Sony Xperia M] hhjadeja007:
There is a chance that you get stuck into bootloop after flashing superSU. So better flash this version
[Sony Xperia M] AyamPushUp:
1st of all, Thx a lot to devs for keep our old device alive :)

I've been use this version since build 20171003 & all work great, more smooth than last official LOS.

Where can I find the changelog for every nightlie build? Maybe I dont need it but, I'm just a curious person :D

Anyway, thx again to devs who keep working on this device.
[Sony Xperia M] litemaster:
Make sure you flash addonsu-14.1-arm-signed.zip (mind the *14.1* part, found on the official LOS Extras Page), and not the older one linked in the first post (named addonsu-arm-signed.zip).

I have no issues with this one.
[Sony Xperia M] seanp25:
Can I flash the latest LOS builds from here over the last official LineageOS build? (from 20170427)
[Sony Xperia M] Nicklas Van Dam:
Of course you can, it'll same like nightly update. But the different this one is unofficial ;)
[Sony Xperia M] droncheg:
Good news, everyone! I continue build roms with OMS with new patches LineageSubstratum.

Since lineage-14.1-20171030_095059-UNOFFICIAL-nicki-loms.zip all roms will be OMS-compatible ;)
[Sony Xperia M] RAZER001:
thanks for oms update but will we taste oreo?:confused::confused:
[Sony Xperia M] droncheg:
I waiting for device tree, still nobody ported to Oreo :(
[Sony Xperia M] litemaster:
FYI - This issue has been fixed in the mean time, as build 201721015 doesn't show the bug anymore. :good:
[Sony Xperia M] hhjadeja007:
Can you do that?
[Sony Xperia M] seanp25:
Great, thanks!
[Sony Xperia M] seanp25:
It seems it doesn't work for me. When I try to flash the latest unofficial LOS with OMS patch over the last official build, TWRP says it failed as the data is incompatible.

Should this work?
[Sony Xperia M] droncheg:
Nope, official incompatible with my builds
[Sony Xperia M] eCoB:
did this for /cache and i had a bootloop

I also did this for /cache and /data and i stuck again ia a bootloop

rom: lineage-14.1-20171027-UNOFFICIAL-nicki-los

kernel: latest beta Mimori_Kernel-nicki-signed

recovery: TWRP v 3.1.1-0

I would appreciate any help
[Sony Xperia M] hhjadeja007:
You cannot format to f2fs with that lineage os build. Actually f2fs needs to be supported in rom also which is not. Droncheg compiled a separate build only once which had support for f2fs. I'm not sure that build is still available to download or not . Hope [MENTION=7670323]droncheg[/MENTION] can help you.
[Sony Xperia M] Nicklas Van Dam:
Sorry for this issue before, but since ROM with f2fs give slow r/w speed when memory usage is full and not much is use or test it when I'm worked on it. So I think I should abandon it, it's already stable and work for both data and cache partition. But during a general issue from f2fs I think not much user will use it, first for adoptable storage user like me.

That ROM is separated from [MENTION=7670323]droncheg[/MENTION] build, he isn't build that ROM again since I'm not requested anymore. For f2fs support it need ROM support too not only from kernel or even with my kernel itself.

If you want to try f2fs, [MENTION=7670323]droncheg[/MENTION] must build a new ROM with my device tree and install my prebuilt kernel that already support f2fs.

It's stable and good to use, but when memory is full your r/w speed will decrease. That's problem from f2fs, not from ROM problem
[Sony Xperia M] Marek8299:
Hi, I'm trying to build LineageOS on WSL, but it always fails. Anybody know what's wrong?

Oh, I think I know: When I tried to build last time, I've got a GSOD. I'll resync source and delete out folder :)

Looks like it worked :)