[ROM][G920/5-F-I-S-K-L-T-W8][9.0] UNOFFICIAL LineageOS 16.0

[xerves78]

The device tree is enough stable, just we miss the lack of HWC

battery drain is still high
echo issue
bluetooth calls problems
often no deep sleep
....

 

[ripee]

but only security patches ?
no bugfixes und optimizing ?

If I learn how to fix any of the below, or someone else does, I will cherry-pick whatever fixes become available. If you would like to contribute, by all means!

battery drain is still high
echo issue
bluetooth calls problems
often no deep sleep
....

 

[lerum]

S6 Edge : G925F - Build 20190614, question

Hi,

First of all many thanks for all efforts.

I did replaced some old 7.0 distro and all seem to work
There is only one thing, and I'm wonder if I can tune it.
When I'm charging it goes extremely slow.
So far in 30 min I was able to charge 50 % of battery now 5 %.
I read that LineageOS has some feature to not let battery to overheat so maybe I got hit by this issue and it cuts charging .. as it reach some temperature..
Anyone had/has same issue?
Anyone know how to fix it?


Anyway big thanks for build! :good:

P.S. in order to install OS16 I did full wipe and installed TWRP 3.3.1-0

 

[DqrKn3Zz]

battery drain is still high
echo issue
bluetooth calls problems
often no deep sleep
....

Battery drain isn't here if you have disabled "Mobile data always on" on developer options.
No echo issue here, that should be you carrier.
Bluetooth calls? Who still using Bluetooth calls in 2019? There are better services than it tbh.
Deep sleep is fine or maybe isn't working for you if you have 1000 apps opened at the same time or any other weird things that no one knows.

 

[xerves78]

Battery drain isn't here if you have disabled "Mobile data always on" on developer options.
No echo issue here, that should be you carrier.
Bluetooth calls? Who still using Bluetooth calls in 2019? There are better services than it tbh.
Deep sleep is fine or maybe isn't working for you if you have 1000 apps opened at the same time or any other weird things that no one knows.

-3% battery per hour during deep sleep is very high
sometimes no deep sleep, only after reboot

my second mobile phone drain -3% in 12 hours over night

echo issues have many user in the telegram groups

what is better than bluetooth headset calls ?

 

[DqrKn3Zz]

-3% battery per hour during deep sleep is very high
sometimes no deep sleep, only after reboot

my second mobile phone drain -3% in 12 hours over night

echo issues have many user in the telegram groups

what is better than bluetooth headset calls ?

You don't know what are POWER PROFILES or Air Plane mode.

Well, they don't have luck, if AOSP isn't stable for they, then idk why they are using it, no one forced them to flash and using AOSP, so, don't chill.

Don't use the device meanwhile youre driving a car, it's common sense and safety.

 

[ripee]

Changelog

Build 0716 for all 4 variants (link in my signature)
* Partial HWC fix that I had mistakenly overlooked in my previous builds, but I am familiar with these changes because I use them in my S7 builds, from Ivan_Meler's sources. PLEASE NOTE: This is NOT something new! enesuzun2002 had included these changes in his own builds.

surfaceflinger: check for unreliable retire-fences before invalidating
[TEMP] graphics: libhwc2on1adapter: fix up layer handles

Once Ivan_Meler pushes his finalized HWC fix, I will be sure to cherry-pick it into my forks of enesuzun2002's S6 sources.

* Synced with LineageOS sources.

You should be able to dirty flash my builds overtop of enesuzun2002's lineage-16.0 builds. However, if in doubt, do a clean flash.

Q: Why don't you make use of the Lineage OTA Updater in your builds?
A: Because I upload to Google Drive, it is impossible to use Lineage's OTA updater because the download URL of the build would have to be predicted prior to building and merged into the OTA updater's settings. Because Google Drive only assigns a file ID once a file is finished uploading, it is impossible to predict the file ID ahead of time to insert it into the OTA updater. I use Google Drive because of virtually zero downtime and generally fast download speeds. I have used Android File Host and BasketBuild in the past, as well as Mega, and all these services had let me down at one point or another. Not that Google Drive is perfect, but it has been the most reliable for me. However, for those unfamiliar, the easiest way to be able to download my updated builds straight to your phone is to add your variant's folder from my account to your account as a shared folder.

 

[TheElate]

Use English dude, that's claimed in the forum rules.

sorry

LineageOS 16.0 (14.06.2019) and ResurrectionRemix 7.0.2 (16.06.2019) have 2 bugs in Caller:

1. when the proximity sensor is triggered, the screen is disabled, but the sensor is not disabled
respectively, when touched by the cheek - actions are performed
2. In the speakerphone mode, the microphone does not work.

SM-G925F
zerofltexx-userdebug 9 PQ3A.190605.003 eng.enes_a.20190614.114453 testkeys

 

[xerves78]

You don't know what are POWER PROFILES or Air Plane mode.

Well, they don't have luck, if AOSP isn't stable for they, then idk why they are using it, no one forced them to flash and using AOSP, so, don't chill.

Don't use the device meanwhile youre driving a car, it's common sense and safety.

i use only power profiles

and it only for car navigation

its stable but still much battery drain

 

[tillward]

sorry

LineageOS 16.0 (14.06.2019) and ResurrectionRemix 7.0.2 (16.06.2019) have 2 bugs in Caller:

1. when the proximity sensor is triggered, the screen is disabled, but the sensor is not disabled
respectively, when touched by the cheek - actions are performed
2. In the speakerphone mode, the microphone does not work.

SM-G925F
zerofltexx-userdebug 9 PQ3A.190605.003 eng.enes_a.20190614.114453 testkeys

These bugs are present in the latest Viper OS too, and the active screen during calls in pretty much every Pie rom i've tried. G920F

 

[carnazas]

has anyone facing some issues of this: sim signal losing every 5 minutes, calls interrupted, need to reboot to gain again network signal (sometime two times reboot is need), battery consumption very high, and device temperature reachs very hot. sry for my poor english, but i use my phone every day and i only realy need to find a fix for losing signal.if everyone know, please post here. the rom is absolute great, but the network loss is a real stop to use every day. im using gs6 edge and lastest build of july

 

[AyyazXOX]

Extreme Power Saver

Hi,
I am trying to enable the extreme power saver but whenever i click it just says "This performance profile is currently not available."
Can anyone help?

 

[zogoibi]

HUGE battery drain here with 2019-06-14 version: Phone idle process sucks 85% of battey overnight (off a full charge) in airplane mode. (And, YES: Mobile data always active is disabled; that's for the heralds of that so-called "fix".)

Oh! Another bug: clicking Search on Settings app makes it crash (the app). I believe, though, that this is a general bug in LOS, because it happens to me also in another device.

 

[lintern]

How do I go back to stock? I did do a quick search but could not find a clear guide. The model is SM-G925F UK.

 

[ripee]

Changelog

Build 0816 for all 4 variants (link in my signature)
* audio: fix libvisualizer path for s6
* kernel: All commits since Aug 4, 2019.
* zero-common: All commits since Aug 15, 2019.
* Synced with LineageOS sources.

 

[lintern]

Changelog

Build 0816 for all 4 variants (link in my signature)
* audio: fix libvisualizer path for s6
* kernel: All commits since Aug 4, 2019.
* zero-common: All commits since Aug 15, 2019.
* Synced with LineageOS sources.

Just updated to this now and my phone is stuck on phone is starting after rebooting.

 

[ripee]

Just updated to this now and my phone is stuck on phone is starting after rebooting.

I think I know what the problem is: I reverted the two LiveDisplay commits in zero-common from Aug 15. I'll run new builds for tomorrow.

 

[mentat]

I think I know what the problem is: I reverted the two LiveDisplay commits in zero-common from Aug 15. I'll run new builds for tomorrow.

If it helps (isolate the issue), I get the same behavior with update to lineage-16.0-20190816-UNOFFICIAL-zerofltecan on my SM-G920W8.

I also tried a clean flash and got stuck at "Just a Sec..." (initial setup) then black screen, then back to "Just a Sec..." (stuck in loop).

Thanks.

 

[lintern]

I think I know what the problem is: I reverted the two LiveDisplay commits in zero-common from Aug 15. I'll run new builds for tomorrow.

I tried flashing the July update but it is still experiencing the same issue. The same procedure happening as the comment below your reply to mine.

 

[KlaverBoer]

I tried flashing the July update but it is still experiencing the same issue. The same procedure happening as the comment below your reply to mine.

I did the same. That doesn't work. I have wiped everything and installed the july version from scratch.