• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[ROM][OFFICIAL][fajita][11] LineageOS 18.1

Search This thread

flyoffacliff

Senior Member
Jun 4, 2014
141
19
I thought someone said this wrong work for Verizon now, but it still has a significant bug in the dialer. Anytime you call someone, real time text (RTT) mode gets stuck on, which is for deaf / hearing impaired people. This basically turns the whole screen into a giant text box when making a call. Rtt is turned off in the dialer settings.
Have this issue with my previous tom, PixenOS, also based on Android 11, and I worked with the developer to fix it. I can forward the same log cat to you if you want or get a new one.
Issue occurs in both the dialer app built into this rom, and Google dialer from the Play store.
 

LuK1337

Recognized Developer
Jan 18, 2013
8,452
16,865
Samsung Galaxy S III I9300
Moto G 2014
I thought someone said this wrong work for Verizon now, but it still has a significant bug in the dialer. Anytime you call someone, real time text (RTT) mode gets stuck on, which is for deaf / hearing impaired people. This basically turns the whole screen into a giant text box when making a call. Rtt is turned off in the dialer settings.
Have this issue with my previous tom, PixenOS, also based on Android 11, and I worked with the developer to fix it. I can forward the same log cat to you if you want or get a new one.
Issue occurs in both the dialer app built into this rom, and Google dialer from the Play store.
I'd prefer changes over logs if someone actually fixed it.
 

flyoffacliff

Senior Member
Jun 4, 2014
141
19
I'd prefer changes over logs if someone actually fixed it.

Here is the first build with the fix. It's in the change notes. Maybe compare it to previous build to see exactly what changed?


Edit: I can't find any relevant source on Github

EDIT 2: Found this in the logcat, if it helps:

Code:
[01-03 11:43:10.152 20392:20392 I/DialerRttSettingsEnabledFn]
com.android.dialer.rtt.settings.impl.RttSettingsEnabledFn.isEnabled:31 enabled by flag


[01-03 11:43:10.152 20392:20392 I/DialerRttConfigurationLoaderImpl]
com.android.dialer.rtt.settings.impl.configuration.RttConfigurationLoaderImpl.isSupported:64 checking if rtt is supported, use google device configuration: false


[01-03 11:43:10.152 20392:20392 I/DialerRttConfigurationLoaderImpl]
com.android.dialer.rtt.settings.impl.configuration.RttConfigurationLoaderImpl.isSupportedOnNonGoogleDevice:75 checking if non google device is supported
 
Last edited:

LuK1337

Recognized Developer
Jan 18, 2013
8,452
16,865
Samsung Galaxy S III I9300
Moto G 2014
Here is the first build with the fix. It's in the change notes. Maybe compare it to previous build to see exactly what changed?


Edit: I can't find any relevant source on Github
I don't think I want to binary diff someone's ROM...sorry.
 

flyoffacliff

Senior Member
Jun 4, 2014
141
19
Do you see their device trees anywhere? I went through 3 github orgs and personal github account of OP and I haven't found anything.

Thanks for looking into this. I also checked out GitHub and found the same thing. :(
I'll PM you the full log cat.

There are a few good posts on this page relating to the same issue in a different ROM. They said it was fixed in V-7.0. so maybe we can find the source for that one?
 

hayvan96

Senior Member
Mar 23, 2018
257
199
Well, I've read this https://forums.oneplus.com/threads/fingerprint-option-missing.975435/page-2 -- it seems that even on OOS, OP6T may "lose" its fingerprint scanner. I've tried many tricks, when rebooting in safe mode, the fingerprint figure appeared but I was asked to unlock SIM1 with the PIN, and after that, no sign of fingerprint scanner, setting is missing in options, etc.

If our dev needs any logs or info, I'd be glad to provide any details.
So after a week of investigation, I wonder:
* can it be a broken persist.img? I've seen for many OP6T, 7x or 8x, it can happen -- in that case if I flash a persist.img for instance from here https://forum.xda-developers.com/t/...t-stock-fastboot-roms-for-oneplus-6t.3862516/, can I brick the device? Asking because it's my wife's device lol
* Simply linked to OOS10.3.10 -- if I follow fw_update instructions, can I downgrade the fw to 10.3.9 safely?

thanks
 

Eric_Lev

Senior Member
Jan 27, 2019
1,172
2,310
Angers
androidfilehost.com

Attachments

  • Screenshot_20210522-095558_LineageOS_Settings.png
    Screenshot_20210522-095558_LineageOS_Settings.png
    148.6 KB · Views: 80
  • Screenshot_20210522-095243_Settings.png
    Screenshot_20210522-095243_Settings.png
    155.5 KB · Views: 81
  • Screenshot_20210522-095324_SafetyNet_Test.png
    Screenshot_20210522-095324_SafetyNet_Test.png
    114.4 KB · Views: 78

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    A stable firmware 11 in a few weeks?

    2
    About GCam:
    The latest release of Nikita (v1.3) is compatible with OP6/6T

    My config file in attached file.
    2
    https://www.reddit.com/r/LineageOS/comments/otagrf
    Some latest builds were removed (e.g. OP5/5T, OP6/6T)
    So - I WASN'T the only one... 😜
    Thanks!
    2
    I rolled back (switched slots) to 7/22 version, and am not longer experiencing the touch issue above. Anyone else experiencing this issue with the 7/29 update?
    https://www.reddit.com/r/LineageOS/comments/otagrf
    Some latest builds were removed (e.g. OP5/5T, OP6/6T)
    2
    I just installed the 7/29 update. The touch response is really off for me where initial touches register as "select" rather than "click". I have to touch a second time often.

    Anyone else experiencing this? Suggestion how to fix?
    I rolled back (switched slots) to 7/22 version, and am no longer experiencing the touch issue above. Anyone else experiencing this issue with the 7/29 update?
  • 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.

    What's not working :
    • WFD
    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:
    9
    @LuK1337 Tahnks for all your hard work.
    Will our beloved 6T also get official 18.1 support?
    Eventually.
    5
    So I went and read through the RTT docs. One way to make sure RTT is disabled is to remove it from the carrier configuration, lol. So I went and did just that:

    UPDATE: So, I found a better way to do this that doesn't break everything else. You can go to /data/user_de/0/com.android.phone/files and edit the carrierconfig file there, mine was called carrierconfig-com.android.carrierconfig-89148000001882338238-1839.xml. Change the following line:

    <boolean name="rtt_supported_bool" value="true"/>
    becomes
    <boolean name="rtt_supported_bool" value="false"/>

    And reboot! After that, RTT shouldn't be a bother anymore. This is a bit of a hack, but it works! XD
    5
    Why do the builds say nightly and not stable on the download page? I thought the ROM was "official" and stable now?
    lmao.
    4
    Thanks for your reply! I have a noob question, I can find several guides and instructions on how to install Magisk using TWRP recovery. However, I cannot seem to find any guides on how to install Magisk using Lineage OS recovery.

    Probably because most people on this device are using TWRP, myself included.

    You should be able to use the steps for installing Magisk from 8T Guide. (Should be the key word, as I'm using TWRP, this is untested on this device personally. It is how I would do it though if I needed to try it.)

    It's basically just

    In LOS recovery choose:

    - Apply update
    - Apply from ADB

    Now in the terminal on the PC:
    - sudo adb sideload Magisk-v22.1.zip. (remove sudo if you aren't using Linux)

    If you get a warning about them not being signed, choose flash anyways. We should be ready to reboot to the system now.

    The section there about passing safety net will work as well. Just remember the safety net test in Magisk doesn't currently work.