[ROM][OFFICIAL] LineageOS 17.1 [OnePlus Nord/avicii]

Search This thread

retos

New member
Apr 29, 2021
2
0
Hi everyone,

such a great ROM, really enjoy it. Thank you KakatkarAkshay for providing it.



The only small bug I saw was that date/time and brightness don't survive a reboot, but that's nothing compared to the functionality gained, and the battery life is just ridiculously good.


Two questions:

- When you update the ROM, you have to re-flash the Magisk-apk/zip via sideload every time after the LOS-update it seems?
Without it, root access is lost – or did I miss any other way to make Magisk persistent for this ROM?
It's not a big issue, but I feel uncomfortable to manually flash anything without applying the -copy-partitions-20210323_1922.zip- beforehand, as per the wiki there is apparently a risk of bricking because of the A/B-partitions – though I'm not sure if I interpreted that correctly.

- While the ROM is up-to date, the Recovery is not. Are you guys aware of a way to apply the latest recovery without resetting everything? Surprisingly I didn't really find anything on this topic, but I can't be the only one wondering about this.


Anyway, man I really missed to have some control over Android, even a heavily adb-debloated stock just doesn't compare at all.
 

flocke000

Senior Member
Apr 26, 2014
329
317
Oberhausen
- When you update the ROM, you have to re-flash the Magisk-apk/zip via sideload every time after the LOS-update it seems?
Without it, root access is lost – or did I miss any other way to make Magisk persistent for this ROM?
It's not a big issue, but I feel uncomfortable to manually flash anything without applying the -copy-partitions-20210323_1922.zip- beforehand, as per the wiki there is apparently a risk of bricking because of the A/B-partitions – though I'm not sure if I interpreted that correctly.
After the update is installed don't reboot, instead go to Magisk Manager and click on "Install Magisk" then choose "Install to inactive slot (after OTA)" and confirm. Once it is installed just reboot.

That way you will have Magisk back after the update directly.
 

retos

New member
Apr 29, 2021
2
0
After the update is installed don't reboot, instead go to Magisk Manager and click on "Install Magisk" then choose "Install to inactive slot (after OTA)" and confirm. Once it is installed just reboot.

That way you will have Magisk back after the update directly.
Thank you – that's neat and exactly what I was looking for.
 

krakard

Member
May 7, 2021
10
1
Hey guys,

does the camera with lineage still suck ? Is there no solution ? I think I will switch back to Oxygen OS since the camera on Lineage is really terrible compared to the Oneplus cam on Oxygen
 

ccpower

Senior Member
Nov 21, 2016
66
32
Hey guys,

does the camera with lineage still suck ? Is there no solution ? I think I will switch back to Oxygen OS since the camera on Lineage is really terrible compared to the Oneplus cam on Oxygen

The stock camera is quite poor, but GCam works fine and i'm very happy with the picture quality i get with it. This ROM doesn't currently allow recording in 4K with either stock camera or GCam, so you'll need OpenCamera for that at the moment. I haven't tried others so i can't say if it's a general custom ROM issue, or just this one.
 

krakard

Member
May 7, 2021
10
1
Thanks for the feedback. I'll look into going back to Oxygen OS unfortunately as I can't be bothered to have a lower quality cam in any shape or form.
 

g0nfi

Member
Apr 10, 2015
13
3
Is anyone having problems updating the ROM through the OTA Updater?
After downloading I need to confirm installing the update and instantly a "Install Error"-Notification pops up.
The log says:
/system/bin/update_engine: [liblp]Not enough free space to expand partition: system_a

Code:
05-07 09:15:26.248  5772  5772 D UpdaterService: Starting service
05-07 09:15:26.252  1317  1317 I update_engine: [0507/091526.252181:INFO:update_attempter_android.cc(456)] Enabling performance mode.
05-07 09:15:26.254  1317  1317 I update_engine: [0507/091526.254351:INFO:update_attempter_android.cc(259)] Using this install plan:
05-07 09:15:26.252  6555  6555 W kworker/0:6: type=1400 audit(0.0:7617): avc: denied { read write } for name="sde67" dev="tmpfs" ino=17428 scontext=u:r:kernel:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file permissive=0
05-07 09:15:26.254  1317  1317 I update_engine: [0507/091526.254539:INFO:install_plan.cc(83)] InstallPlan: new_update, version: , source_slot: B, target_slot: A, url: file:///data/lineageos_updates/lineage-17.1-20210506-nightly-avicii-signed.zip, payload: (size: 1183837444, metadata_size: 189229, metadata signature: , hash: 5373DDD727A763847C38D087DF408E101DD7D27CE46B4A11BCF85D479C5411CE, payload type: unknown), hash_checks_mandatory: true, powerwash_required: false, switch_slot_on_reboot: true, run_post_install: true, is_rollback: false, write_verity: true
05-07 09:15:26.255  1317  1317 I update_engine: [0507/091526.255170:INFO:metrics_utils.cc(349)] Number of Reboots during current update attempt = 0
05-07 09:15:26.255  1317  1317 I update_engine: [0507/091526.255327:INFO:metrics_utils.cc(357)] Payload Attempt Number = 1
05-07 09:15:26.255  1317  1317 I update_engine: [0507/091526.255529:INFO:metrics_utils.cc(374)] Update Monotonic Timestamp Start = 1/1/1970 0:11:34 GMT
05-07 09:15:26.255  1317  1317 I update_engine: [0507/091526.255705:INFO:metrics_utils.cc(383)] Update Boot Timestamp Start = 1/1/1970 0:18:31 GMT
05-07 09:15:26.255  1317  1317 I update_engine: [0507/091526.255764:INFO:update_attempter_android.cc(580)] Scheduling an action processor start.
05-07 09:15:26.255  1317  1317 I update_engine: [0507/091526.255963:INFO:action_processor.cc(51)] ActionProcessor: starting UpdateBootFlagsAction
05-07 09:15:26.256  1317  1317 I update_engine: [0507/091526.256021:INFO:update_boot_flags_action.cc(36)] Already updated boot flags. Skipping.
05-07 09:15:26.256  1317  1317 I update_engine: [0507/091526.256064:INFO:action_processor.cc(116)] ActionProcessor: finished UpdateBootFlagsAction with code ErrorCode::kSuccess
05-07 09:15:26.256  1317  1317 I update_engine: [0507/091526.256103:INFO:action_processor.cc(143)] ActionProcessor: starting InstallPlanAction
05-07 09:15:26.256  1317  1317 I update_engine: [0507/091526.256145:INFO:action_processor.cc(116)] ActionProcessor: finished InstallPlanAction with code ErrorCode::kSuccess
05-07 09:15:26.256  1317  1317 I update_engine: [0507/091526.256182:INFO:action_processor.cc(143)] ActionProcessor: starting DownloadAction
05-07 09:15:26.256  1317  1317 I update_engine: [0507/091526.256229:INFO:install_plan.cc(83)] InstallPlan: new_update, version: , source_slot: B, target_slot: A, url: file:///data/lineageos_updates/lineage-17.1-20210506-nightly-avicii-signed.zip, payload: (size: 1183837444, metadata_size: 189229, metadata signature: , hash: 5373DDD727A763847C38D087DF408E101DD7D27CE46B4A11BCF85D479C5411CE, payload type: unknown), hash_checks_mandatory: true, powerwash_required: false, switch_slot_on_reboot: true, run_post_install: true, is_rollback: false, write_verity: true
05-07 09:15:26.256  1317  1317 I update_engine: [0507/091526.256276:INFO:download_action.cc(199)] Marking new slot as unbootable
05-07 09:15:26.256   990  6870 E InputDispatcher: Window handle Window{b17aeb8 u0 org.lineageos.updater/org.lineageos.updater.UpdatesActivity} has no registered input channel
05-07 09:15:26.280   594   594 W [email protected]: type=1400 audit(0.0:7618): avc: denied { getattr } for path="/dev/block/sde20" dev="tmpfs" ino=20897 scontext=u:r:hal_bootctl_default:s0 tcontext=u:object_r:uefi_block_device:s0 tclass=blk_file permissive=0
05-07 09:15:26.286  1317  1317 I update_engine: [0507/091526.286151:INFO:multi_range_http_fetcher.cc(45)] starting first transfer
05-07 09:15:26.286  1317  1317 I update_engine: [0507/091526.286311:INFO:multi_range_http_fetcher.cc(74)] starting transfer of range 46548+1183837444
05-07 09:15:26.287  1317  1317 I update_engine: [0507/091526.287175:INFO:delta_performer.cc(208)] Completed 0/? operations, 16384/1183837444 bytes downloaded (0%), overall progress 0%
05-07 09:15:26.290  1317  1317 I update_engine: [0507/091526.290948:INFO:delta_performer.cc(519)] Manifest size in payload matches expected value from Omaha
05-07 09:15:26.291  1317  1317 I update_engine: [0507/091526.291142:INFO:delta_performer.cc(1614)] Verifying using public key: /etc/update_engine/update-payload-key.pub.pem
05-07 09:15:26.291  1317  1317 I update_engine: [0507/091526.291480:INFO:payload_verifier.cc(58)] signature blob size = 264
05-07 09:15:26.291  1317  1317 I update_engine: [0507/091526.291889:INFO:payload_verifier.cc(78)] Verified correct signature 1 out of 1 signatures.
05-07 09:15:26.291  1317  1317 I update_engine: [0507/091526.291952:INFO:payload_metadata.cc(237)] Metadata hash signature matches value in Omaha response.
05-07 09:15:26.300  1317  1317 I update_engine: [0507/091526.300920:INFO:delta_performer.cc(1645)] Detected a 'full' payload.
05-07 09:15:26.312  1317  1317 I update_engine: [0507/091526.312045:INFO:prefs.cc(122)] dynamic-partition-metadata-updated not present in /data/misc/update_engine/prefs
05-07 09:15:26.312  1317  1317 I /system/bin/update_engine: [libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
05-07 09:15:26.308  1317  1317 I update_engine: type=1400 audit(0.0:7619): avc: denied { search } for name="/" dev="sda13" ino=2 scontext=u:r:update_engine:s0 tcontext=u:object_r:metadata_file:s0 tclass=dir permissive=1
05-07 09:15:26.316  1317  1317 I /system/bin/update_engine: [libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
05-07 09:15:26.317  1317  1317 I update_engine: [0507/091526.317442:INFO:dynamic_partition_control_android.cc(197)] Loaded metadata from slot B in /dev/block/bootdevice/by-name/super
05-07 09:15:26.317  1317  1317 I update_engine: [0507/091526.317527:INFO:boot_control_android.cc(312)] Removing group oneplus_dynamic_partitions_a
05-07 09:15:26.317  1317  1317 I update_engine: [0507/091526.317566:INFO:boot_control_android.cc(343)] Added group oneplus_dynamic_partitions_a with size 7511998464
05-07 09:15:26.317  1317  1317 I /system/bin/update_engine: [liblp]Partition odm_a will resize from 0 bytes to 1056768 bytes
05-07 09:15:26.317  1317  1317 I update_engine: [0507/091526.317698:INFO:boot_control_android.cc(360)] Added partition odm_a to group oneplus_dynamic_partitions_a with size 1056768
05-07 09:15:26.317  1317  1317 I /system/bin/update_engine: [liblp]Partition product_a will resize from 0 bytes to 1806266368 bytes
05-07 09:15:26.317  1317  1317 I update_engine: [0507/091526.317777:INFO:boot_control_android.cc(360)] Added partition product_a to group oneplus_dynamic_partitions_a with size 1806266368
05-07 09:15:26.317  1317  1317 E /system/bin/update_engine: [liblp]Not enough free space to expand partition: system_a
05-07 09:15:26.317  1317  1317 E update_engine: [0507/091526.317820:ERROR:boot_control_android.cc(356)] Cannot resize partition system_a to size 2290823168. Not enough space?
05-07 09:15:26.317  1317  1317 E update_engine: [0507/091526.317854:ERROR:delta_performer.cc(975)] Unable to initialize partition metadata for slot A
05-07 09:15:26.317  1317  1317 E update_engine: [0507/091526.317882:ERROR:download_action.cc(336)] Error ErrorCode::kInstallDeviceOpenError (7) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
05-07 09:15:26.317  1317  1317 I update_engine: [0507/091526.317933:INFO:multi_range_http_fetcher.cc(177)] Received transfer terminated.
05-07 09:15:26.317  1317  1317 I update_engine: [0507/091526.317956:INFO:multi_range_http_fetcher.cc(129)] TransferEnded w/ code 200
05-07 09:15:26.317  1317  1317 I update_engine: [0507/091526.317976:INFO:multi_range_http_fetcher.cc(131)] Terminating.
05-07 09:15:26.321  1317  1317 I update_engine: [0507/091526.321851:INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kInstallDeviceOpenError
05-07 09:15:26.321  1317  1317 I update_engine: [0507/091526.321924:INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
05-07 09:15:26.321  1317  1317 I update_engine: [0507/091526.321949:INFO:update_attempter_android.cc(468)] Processing Done.
 

noway0

Member
May 11, 2021
6
1
I installed this Rom and used it for a while and found these issues:

Calls:
- not able to receive any calls whatsoever (Europe), 3g and 4g
- also not receiving any messages that someone tried to call me
-> otherwise sms works (as far as I can tell)
- when in LTE only mode not able to call out, instantly ends call after dialing no matter how good the signal is
-> calls going out work when the 3g network is enabled too

USB-Tethering:
- randomly doesn't work, sometimes it does, more often it does not and one has to restart everytime to try again, as when it doesn't work changing to airplane mode and back or disable and re-enable tethering does absolutely nothing.

Other:
- clock completely resets itself every reboot
- why is there google bloat included ("ok google enrollment")? Ins't LineageOS supposed to be free of bloat, especially of the privacy invading kind? From the initial post: "It can be used without any need to have any Google application installed."
- camera is pretty weak compared to stock


I appreciate the effort from the developer, I really do, yet I begin to get why these Roms are nowadays called "nightly".
With official status I hoped for basic functionality, quite frustrating to waste time to no end to find it is the Rom itself.

Would be good to update the issues list in the first post, so everyone knows what they get beforehand.
 

KakatkarAkshay

Recognized Developer
Feb 16, 2020
219
344
OnePlus 8 Pro
OnePlus Nord
I installed this Rom and used it for a while and found these issues:

Calls:
- not able to receive any calls whatsoever (Europe), 3g and 4g
- also not receiving any messages that someone tried to call me
-> otherwise sms works (as far as I can tell)
- when in LTE only mode not able to call out, instantly ends call after dialing no matter how good the signal is
-> calls going out work when the 3g network is enabled too

USB-Tethering:
- randomly doesn't work, sometimes it does, more often it does not and one has to restart everytime to try again, as when it doesn't work changing to airplane mode and back or disable and re-enable tethering does absolutely nothing.

Other:
- clock completely resets itself every reboot
- why is there google bloat included ("ok google enrollment")? Ins't LineageOS supposed to be free of bloat, especially of the privacy invading kind? From the initial post: "It can be used without any need to have any Google application installed."
- camera is pretty weak compared to stock


I appreciate the effort from the developer, I really do, yet I begin to get why these Roms are nowadays called "nightly".
With official status I hoped for basic functionality, quite frustrating to waste time to no end to find it is the Rom itself.

Would be good to update the issues list in the first post, so everyone knows what they get beforehand.
Calls: all those issues have something to do with the way you installed it or idk because it works just fine for me.
Usb tethering; same as calls.
Clock: same as above.
Ok google enrollment: it's required else in some cases audio randomly stops working because of soundtrigger, it's just to support it in case user flashes gapps and wants to use it. It's not enabled by default
Camera: there's nothing I can do about that
 
  • Like
Reactions: noway0

noway0

Member
May 11, 2021
6
1
Calls: all those issues have something to do with the way you installed it or idk because it works just fine for me.
Usb tethering; same as calls.
Clock: same as above.
Ok google enrollment: it's required else in some cases audio randomly stops working because of soundtrigger, it's just to support it in case user flashes gapps and wants to use it. It's not enabled by default
Camera: there's nothing I can do about that
Thanks for your quick and helpful reply.

It's good to hear it's supposed to work and the error has to be on my side, yet I followed the instructions on the wiki closely and get those issues, so I'm puzzled. The device itself is definitely a supported model number.

I will start from scratch and see if something changes, but at least the clock/date I know for sure resets at every reboot right from the beginning, though that alone is not that much of a problem.

The calling stuff is quite weird but I now noticed especially the LTE only mode is apparently prone for things like this in LineageOS, there are a lot of reports of others with all kinds of devices with the same problem. Maybe it has something to do with gsm vs cmda based networks or voice-over-LTE?


Regarding google: I see, this makes sense and I appreciate the explanation.
 

noway0

Member
May 11, 2021
6
1
@noway0 Calls via VoLTE and VoWiFi work flawlessly, no problems here with LOS on an EU model.
and @KakatkarAkshay :

After starting from scratch and way too much testing all call related issues are gone, you were both completely right with that.


There were 2 causes apparently:
  • When only using LTE as Network type, calls don't come in when one doesn't also allow the option -4G Calling-, which seems quite obvious in hindsight, though that appears to be the switch for VoLTE.
  • The other was the app Invizible Pro in root mode, that also breaks incoming calls completely but I could not figure out why exactly, the alternative rootless vpn mode however doesn't.

What persisted were rather small issues:

  • usb-tethering: ca. 1 out 5 times (20 test runs that were very similar) it does randomly not work (tethering hardware acceleration is enabled and seems to help). Which makes it hard to debug as it is so inconsistent. When it failed: "ip a" on the pc shows the device is connected and recognized but has no local ip and no connection comes through, so apparently dhcp failed for some reason. I then connected another android with stock and tried usb-tethering again to make sure it's not a random failure of debian or the dns-server on the pc-side, but then it worked, so it really appears to be the avicii (It were only resolved through rebooting the device). After each test I rebooted both the phone and the pc. But all in all not that big of an issue.
  • the clock and date still reset after reboot to what appears to be the built-time of the rom, this was immediately the case without any system changes other than enabling airplane mode. It might not be too noticeable because the default setting is to get the time from the network
  • the brightness settings appear to also revert back after each reboot


But these I can live with and I was wrong to state that basic functionality were not given.
 

sniperle

Senior Member
Dec 8, 2010
422
361
and @KakatkarAkshay :

After starting from scratch and way too much testing all call related issues are gone, you were both completely right with that.


There were 2 causes apparently:
  • When only using LTE as Network type, calls don't come in when one doesn't also allow the option -4G Calling-, which seems quite obvious in hindsight, though that appears to be the switch for VoLTE.
  • The other was the app Invizible Pro in root mode, that also breaks incoming calls completely but I could not figure out why exactly, the alternative rootless vpn mode however doesn't.

What persisted were rather small issues:

  • usb-tethering: ca. 1 out 5 times (20 test runs that were very similar) it does randomly not work (tethering hardware acceleration is enabled and seems to help). Which makes it hard to debug as it is so inconsistent. When it failed: "ip a" on the pc shows the device is connected and recognized but has no local ip and no connection comes through, so apparently dhcp failed for some reason. I then connected another android with stock and tried usb-tethering again to make sure it's not a random failure of debian or the dns-server on the pc-side, but then it worked, so it really appears to be the avicii (It were only resolved through rebooting the device). After each test I rebooted both the phone and the pc. But all in all not that big of an issue.
  • the clock and date still reset after reboot to what appears to be the built-time of the rom, this was immediately the case without any system changes other than enabling airplane mode. It might not be too noticeable because the default setting is to get the time from the network
  • the brightness settings appear to also revert back after each reboot


But these I can live with and I was wrong to state that basic functionality were not given.

As @KakatkarAkshay wrote, these seem to be problems that are specific to you. For me, both the time and the brightness "survive" a reboot without problems. I don't know about USB-tethering, I haven't used it yet.
 

noway0

Member
May 11, 2021
6
1
As @KakatkarAkshay wrote, these seem to be problems that are specific to you. For me, both the time and the brightness "survive" a reboot without problems. I don't know about USB-tethering, I haven't used it yet.
Well I checked the integrity of the downloads and I followed the wiki/the instructions on page 1 to the dot mutliple times by now, I simply see no further room for any error on my side for the time- and the brightness-issue – if these instructions are correct, and the hardware works, which I assume.
 
  • Like
Reactions: sniperle

krakard

Member
May 7, 2021
10
1
Do you guys know a custom ROM that'd be better than Lineage for the Nord ?
I was satisfied but the camera app was really garbage...

I want to go degoogled but I am afraid that Nord is too new and that'd I'd be better off selling it and buying Pixel and go Graphene OS.
 
  • Like
Reactions: eNVy

sniperle

Senior Member
Dec 8, 2010
422
361
Well I checked the integrity of the downloads and I followed the wiki/the instructions on page 1 to the dot mutliple times by now, I simply see no further room for any error on my side for the time- and the brightness-issue – if these instructions are correct, and the hardware works, which I assume.

Please do not misunderstand, that was not meant as an accusation.
You have certainly done everything right. I also read through the wiki first.
Nevertheless, it should be noted that there is no problem with time and brightness on my two Nords.
I have roughly installed the following: LOS 17.1 + Magisk + microG
 

sniperle

Senior Member
Dec 8, 2010
422
361
Do you guys know a custom ROM that'd be better than Lineage for the Nord ?
I was satisfied but the camera app was really garbage...

I want to go degoogled but I am afraid that Nord is too new and that'd I'd be better off selling it and buying Pixel and go Graphene OS.
Before you change the ROM, try GCam first.
I like OpenCamera much more than GCam, but the image quality is much better with GCam on the Nord.
Link: https://www.celsoazevedo.com/files/android/p/google-camera-oneplus-nord/
 

noway0

Member
May 11, 2021
6
1
Nevertheless, it should be noted that there is no problem with time and brightness on my two Nords.
I have roughly installed the following: LOS 17.1 + Magisk + microG
That's interesting, I don't use microG, just Los 17.1 and Magisk. It doesn't seem all that likely, but maybe that has something to do with the date and brightness not being saved in some cases.
 

noway0

Member
May 11, 2021
6
1
In case someone else has apparently random problems with USB-tethering:
If you are using PrivateDNS you could try other DNS-Servers (one with ad- and malware blocking already included makes particular sense), as some of them are sometimes apparently failing and preventing the phone from sharing the internet connection.
The weird thing is that the phones network still works, but the tethering silently fails, which makes the issue hard to detect. But the problem goes away when changing the privateDNS-Server.
 

sniperle

Senior Member
Dec 8, 2010
422
361
That's interesting, I don't use microG, just Los 17.1 and Magisk. It doesn't seem all that likely, but maybe that has something to do with the date and brightness not being saved in some cases.

I don't think it's because of microG. The time and the brightness are settings of the base system. MircoG provides some Google services and location services, so this will not be the decisive difference. However, it's very strange what's going on with your Nord.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    The first post says
    Last Updated 2020-11-03

    I this ROM updated with the latest security patches or is it completely abandoned?
    That's just the original post modification date. This ROM receives weekly updates, built automatically with generic changes to the LineageOS 17.1 branch. This includes monthly security patches. Nothing Nord-specific is being done right now, though.
    1
    Hi, I have been running the microG version of this ROM for a while now and I'm very happy with it so far.
    I'd like to install the automatic updates through the system menu but I don't want to risk screwing up anything.

    The phone is not rooted, just installed Lineage (microG version) and the bootloader is still unlocked. is it OK to install the updates or should something be done before?
    1
    want to know the same..
    i use two gapps though maps n Gpay ..both dont work from aurora store. any solution for this?
    As far as I know it's not possible to get Gpay to work with microG. I don't want to use google maps because of the tracking, so I use Osmand+ instead from F-droid. I'm very impressed by how well Osmand+ works. The version in F-droid is the full version too.
    1
    Well i can get away with Gpay alternative but Gmaps and osmand both are not locking on to location. So navigation seems to not work for me. Turned on all the modules in microg for location. Any fix?
    for me I have not had issues with osmand, but it only works outside were it can get GPS signal. it gets nothing from wifi indoors.
  • 11
    Hi, any plans about Lineage18.1 on Avicii ?
    11
    Builds are now official and will be published on https://download.lineageos.org according to the build schedules. Builds will be updated weekly.
    9
    https%3A%2F%2Fimg.xda-cdn.com%2FNEqGNs6rv5B0hFKzbB7Z_gXjqkY%3D%2Fhttp%253A%252F%252Ffiles.paulfasola.fr%252FCyanogenMod%252FLineageOS.png


    Code:
    /*
    * I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
    * Please do some research if you have any concerns about features included in the products you find here before flashing it!
    * YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
    * Your warranty will be void if you tamper with any part of your device / software.
    * Same statement for XDA.
    */

    LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.


    What's working :
    Boots
    RIL
    Fingerprint
    Wi-Fi
    Bluetooth
    Camera
    Audio
    Sensors
    Flash
    GPS
    Alert Slider
    NFC

    Known issues :
    You tell me.

    Instructions :
    Download the latest build.
    Reboot to Recovery.
    Flash the build.
    Reboot to recovery.
    Format Data.
    Flash GApps (Optional).
    Flash Magisk (Optional).
    Reboot

    Downloads :
    Grab ur build : Link

    XDA:DevDB Information
    LineageOS, ROM for the OnePlus Nord

    XDA:DevDB Information
    LineageOS 17.1, ROM for the OnePlus Nord

    Contributors
    @KakatkarAkshay
    Device Tree: https://github.com/LineageOS/android_device_oneplus_avicii
    Kernel Tree: https://github.com/LineageOS/android_kernel_oneplus_sm7250

    ROM OS Version: Android 10
    ROM Kernel: Linux 4.19
    Based On: LineageOS

    Version Information
    Status:
    Stable
    Current Stable Version: 17.1
    Stable Release Date: Updated weekly

    Created 2020-11-03
    Last Updated 2020-11-03
    7
    Sadly that seems to be the case: no changes by the maintainer since Jan 27. It's on auto-build or something, since weekly updates do come along with generic updates applied. I don't know how long is that able go on before the device is dropped from the official roster. Maybe another developer will pick it up, if the current maintainer has lost interest in this ROM.

    Again, no complaints - it's volunteer work and i'm grateful for it all anyway.
    I haven't lost interest, I'm busy irl and don't have time to work on Nord right now.
    3
    Yes I also have the problem that Chrome freezes this happens but also with Brave. I have now once reflashed and leave the Props module away. But unfortunately the error is still there. Chrome Crasht after about a minute.

    @KakatkarAkshay: Thanks for the info. But do you have any idea why Google Chrome freezes? The Jelly Browser (default system browser) works flawlessly without freezing
    This seems to solve it:


    Make sure you backup /vendor/etc/vintf/manifest.xml before editing!