[ROM][OFFICIAL] LineageOS 14.1 Weeklies for the Google Nexus 4 (mako)

[Ahkah]

Had not a single BSOD since 2017-03-12 when I activated the "Keep in the foreground" option of SOD Killer. Before I tried "Kernel Adjutor" app to increase minimum CPU freq, no luck. And then SOD Killer without foreground setting, worked about 1-2 days but then BSOD again. Since activating "foreground" not a single issue (beside an noticeable battery usage of at least 10% per day caused by keeping the phone awake).

Thanks for reporting the detailed test results! When I installed this app I intuitively activated that foreground option and no longer thought about it.

 

[AraldoL]

Damn, guys i reading thats comments and i don't know how did you not had sod before, because i think, i was that in all roms what i installed ( i don't remember about stock rom 5.1)

Bought my Nexus 4 in January 2013 with Android 4.2, then was always on the "official path" to 5.1.1 till July 2016 when I unlocked the device and installed TWRP and CM13. Used this till February 2017 when I changed to LOS 14.1 with a full wipe. All the time before LOS14.1 I never had a single BSOD (*) in those four years, it started with LOS14.1 for me.

(*) In CM13 I had a different issue, about once a month there was a huge battery drain out of nowhere where I couldn't find out what caused it. If I didn't catch it early and rebooted the device I had a BSO-empty-battery afterwards. But never a BSOD where I couldn't wake the phone when battery was not empty. And I had and have none of the "usually suspicious" apps installed, no WhatsApp, no FaceBook, no Twitter, no Instagram or any other messenger beside "Messages" from Google.

 

[Poil44]

I had SOD with official since Android 5, when I'd switched to CM13 I had no more. First releases of CM14 was also working fine.

 

[ryancell]

I had SOD with official since Android 5, when I'd switched to CM13 I had no more. First releases of CM14 was also working fine.

Come to think of it when I first installed LineageOS I don't think I had bsod (the first build it launched with). As the builds progressed, it got worse and worse. Not sure what changed.

 

[GuestK0092]

New version ( lineage-14.1-20170330-nightly-mako ) is free from BSOD?

 

[rogers11]

No

 

[donate_ro]

New version ( lineage-14.1-20170330-nightly-mako ) is free from BSOD?

Got BSOD after 3 hours after installation.

 

[pxrave]

New version ( lineage-14.1-20170330-nightly-mako ) is free from BSOD?

no take two today :/

i tryd to disable powersavings hope it works if yes i will submit it into gerrit (same as slimrom)

 

[GuestK0092]

Is this problem (BSOD) reported to LineageOS 14.1?

 

[AraldoL]

Yes:
https://jira.lineageos.org/browse/BUGBASH-230

 

[underskyzx]

Lol they marked priority medium...this sod thing is urgent priority

 

[DriftJos]

I have installed LineageOS + Gapps + SU two weeks ago. All works great. Got a OTA delivered, but cancelled that one because I like to flash it manually. I have two questions:
- Do I need to flash Gapps + SU again after flashing a new nightly, or could I just flash the nightly?
- How do I stop the automatic OTA searching for new nighlies? Could I just deactivate the "LinageOS Updater" process via the settings, or is there a switch somewhere?

Thanks

 

[AraldoL]

GApps remain when you flash an OTA. Same for SU (if you used the official AddonSU from LineageOS and not a third party like SuperSU what isn't recommended at all). So just flash the OTA and you loose nothing. Before you should check if you have a current TWRP (not below 3.1.0.0) because older versions can create a boot loop on Android 7 OTA updates. And a backup (can be made with TWRP) is never wrong before such an action.

The Updater is located (I hope I translate it correctly to english): Settings - About the Phone - LineageOS Updates. There was an option there in the past to change update frequency and to disable it. Currently I can't find it, I have deleted all downloads on this page with the three-point-menu, perhaps this is the cause it's missing. Before the option was below the found updates, had to slide them upwards if I remember correctly. Can't test it now as this list is empty here.

 

[raaph]

Not sure if it helps to avoid BSOD but before I had several errors like this in logcat :

03-30 08:01:05.381 27188 27202 D QSEECOMAPI: : QSEECom_start_app sb_length = 0x19000
03-30 08:01:05.382 27188 27202 D QSEECOMAPI: : App is not loaded in QSEE
03-30 08:01:05.382 27188 27202 E QSEECOMAPI: : Error::Cannot open the file /vendor/firmware/tzapps.mdt
03-30 08:01:05.383 27188 27202 E QSEECOMAPI: : Error::Loading image failed with ret = -1
03-30 08:01:05.383 27188 27202 D QSEECOMAPI: : QSEECom_start_app sb_length = 0x19000
03-30 08:01:05.390 27188 27202 D QSEECOMAPI: : App is not loaded in QSEE
03-30 08:01:05.412 215 215 I ServiceManager: service 'media.drm' died

Then I copied the missing files into /vendor/firmware :

adb root
adb shell
mount -o rw,remount /system
cp /system/etc/firmware/tzapps.* /vendor/firmware/
mount -o ro,remount /system

And then no more QSEECom or media DRM error !
No more BSOD either but there is only 4 days...

 

[abdess47]

Hi,
Someone know how can I do for enable double tap to wake on this OS ?
Thank's.

 

[justmix4]

Hi,
Someone know how can I do for enable double tap to wake on this OS ?
Thank's.

Use custom kernel.

Sent from my mako using XDA Labs

 

[cyprien T]

 

[abdess47]

I tryed Franko and semaphore kernel but anyone works, anh suggestions ? Thanks

 

[jer_ying_fd]

I tryed Franko and semaphore kernel but anyone works, anh suggestions ? Thanks

Wrong android version, those are for 5.1.1, this is 7.1.1

 

[abdess47]

Some advise ?