[ROM][OFFICIAL][hotdog][11] LineageOS 18.1

Search This thread

Hw4ng3r

Senior Member
Will you change this rom to no sdcardfs in the future updates?

See below:

TLDR: no

 
  • Like
Reactions: Ondřej Holomek

veti

Senior Member
May 12, 2015
102
47
i am having problems with the screen registering touches during a phone call.
when my phone is held to my ear i have repentantly changed settings with my face in the quick settings pulldown.
 

the-essay

New member
Aug 2, 2018
3
0
i am having problems with the screen registering touches during a phone call.
when my phone is held to my ear i have repentantly changed settings with my face in the quick settings pulldown.
Hi - and thanks for that great ROM,

I got the same problem. The only workaround is to switch to a different app and then lock the phone. If you lock the phone with the call-app in front or when you put it on your ear, the screen gets dark for a few seconds only. I think that moving the phone (so the sensor I guess), activates the screen. When I use the hands free speaker, while not moving the phone, the screens doesn't wake up.

I hope that helps so find the cause.

EDIT: I got some WiFi-issues too, with a flapping connection. IMHO the problem only appears with 5GHz, but I got to few infos to be more precise. I will reply again after taking a closer look.

Best regards
 
Last edited:

S1FT_Y_FelloW

New member
Aug 10, 2021
2
0
What is your--
LineageOS version: 11 RQ3A.210705.0016c559d13bc
LineageOS Download url: https://download.lineageos.org/hotdog
Gapps version: 11 arm64

Did you--
wipe: yes
restore with titanium backup: no
reboot after having the issue: yes

Are you using--
a task killer: no
a non-stock kernel: no
other modifications: magisk

Many thanks to the developer for the ROM. It works very stably. But for myself, I noticed inconveniences.
1) After installation, I could not use Gpay (The problem was solved through MagiskHide Props Config -> I asked that I have OP 8 PRO CN).
2) Auto brightness does not work correctly, it can change its level at the same lighting level, it also does it abruptly.
3) Sometimes, when unlocking, inversion of all colors in the system occurs (negative effect).
4) Fingerprint unlocking works worse.
 

wiegje

New member
Nov 5, 2009
4
0
Hello, same issue here. My fingerprints won't work anymore - with or without Night Light, with or without Force HW Overlays. I have reset my fingerprints multiple times and still have the same issue. The previous build was just fine.
 

Max-E-Moose

Senior Member
Dec 15, 2010
91
24
Hey LuK1337,

I've been using this ROM for around a month now and it's been great. Many thanks for your efforts. The one issue I've had has been with Adaptive Brightness; it has been all over the place. Too dark in light areas, too bright in dark areas, and updating seemingly randomly.

Despite giving it nearly a month to "adapt" it never did so I started looking for solutions. Then I stumbled on a commit for LineageOS 17 that seemingly addresses the issue. You're already aware of it, I'm sure ;). I don't think this change has made it's way into LineageOS 18 for the 7T Pro yet.

In an issue about adaptive brightness being unstable in 17.1, another fix is mentioned: Disabling the naruto light sensor service. For anyone looking to test this, simply change the following value in system/build.prop from true to false and then reboot:
Code:
persist.vendor.naruto.light.support=false

I've been running with this change for the last few days and Adaptive Brightness has been really stable this whole time.
 

darkoj2007

Senior Member
Nov 12, 2012
595
124
Skopje
Hey LuK1337,

I've been using this ROM for around a month now and it's been great. Many thanks for your efforts. The one issue I've had has been with Adaptive Brightness; it has been all over the place. Too dark in light areas, too bright in dark areas, and updating seemingly randomly.

Despite giving it nearly a month to "adapt" it never did so I started looking for solutions. Then I stumbled on a commit for LineageOS 17 that seemingly addresses the issue. You're already aware of it, I'm sure ;). I don't think this change has made it's way into LineageOS 18 for the 7T Pro yet.

In an issue about adaptive brightness being unstable in 17.1, another fix is mentioned: Disabling the naruto light sensor service. For anyone looking to test this, simply change the following value in system/build.prop from true to false and then reboot:
Code:
persist.vendor.naruto.light.support=false

I've been running with this change for the last few days and Adaptive Brightness has been really stable this whole time.
how did you manage to change build.prop? I can't even delete files from system or app folder in system, not to mention changing build.prop?
 

Max-E-Moose

Senior Member
Dec 15, 2010
91
24
how did you manage to change build.prop? I can't even delete files from system or app folder in system, not to mention changing build.prop?
I used Solid Explorer and it's in-built text editor, with root permission granted.

I think you can edit system files rootless via ADB, though you need to be able to mount the system partition from your recovery.
 
  • Like
Reactions: darkoj2007

darkoj2007

Senior Member
Nov 12, 2012
595
124
Skopje
@LuK1337 thanks for implementig those brightness improvements, now autobrightness is perfect for me becouse it doesnt go up and down on low light situations, it`s updated just once after screen is turned on. Now Lineage is my daily driver :) please only if you could make this rom to use sdcardfs becouse it`s very slow while moving files and stuff. all other stuff is top notch! THANKS :)
 

RayfG

Senior Member
Jan 28, 2016
495
130
outa space
Has anybody experiance with volte and Wifi Calling under Lineageos 18.1? If yes, is it working out of the box or do I have to enable it first under ooS?
Thank u for any hint
 

Ondřej Holomek

Senior Member
Nov 29, 2016
78
18
Hi, i had build los without sdcardfs and now i wanted to convert userdata from ext4 to f2fs, but when i change things in fstab and BoardConfig in hotdog, phone will not boot. So my question is... Can LOS run on f2fs ? If yes what do i need to change, if someone can help me please.

EDIT: I solved that, it booted
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 11
    FYI, next week you'll get the first official 18.1 build.
    Follow official installation instructions on https://wiki.lineageos.org for upgrade/install and https://wiki.lineageos.org/devices/hotdog/fw_update for firmware update as OOS 11 FW is needed.
    9
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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. You can also view the Changelog for a full list of changes & features.

    Instructions :
    Downloads :
    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
    
    Did you--
    wipe:
    restore with titanium backup:
    reboot after having the issue:
    
    Are you using--
    a task killer:
    a non-stock kernel:
    other modifications:
    
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
    3
    Just saw that LOS 18.1 was officially released today. Can we expect getting official builds starting next week?
    3
    What is your--
    LineageOS version: lineage-18.0-20201201_212539-UNOFFICIAL-hotdog
    LineageOS Download url: lineage-18.0-20201201_212539-UNOFFICIAL-hotdog.zip | by LuK1337 for OnePlus 7T Pro (androidfilehost.com)
    Gapps version: NikGapps-core-arm64-11-20201122-signed

    Did you--
    wipe: yes
    restore with titanium backup: yes but with swift backup (tested gps before doing that with just core gapps as well)
    reboot after having the issue: yes

    Are you using--
    a task killer: no
    a non-stock kernel: no
    other modifications: magisk only

    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

    Problem is GPS doesn't work. Everything else is fine. Tried last 2 versions from one I linked, doesn't work. Also tried first version and it doesn't work.
    Icon appears calling for location but no app can get it including maps, weather etc.
    It does eventually get my location but only after waiting 10 mins or, its not live at all. And when it eventually shows location its where I was quite a while ago. Completely wrong.

    EDIT: GPS also not working on AICP. But does work on OOS and MSM-EXTENDED. So no clue what the **** is going on.
    2
    Everybody hates "when will you release...?" questions,
    but can you say if you're *planning* (without any guarantees!) or currently working on it?

    If not I knew that I shouldn't wait or so. Thanks for your big works and contributions!