• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][OFFICIAL][hotdogb][11] LineageOS 18.1

Search This thread

GreenApp

Member
Mar 3, 2020
25
10
I also got the 1907 from B&H. Unlocked bootloader, flashed global rom with this guide


but never rooted it. I then ran an update or 2 before moving to this rom. I haven't had any of the described calling issues. Haven't really found any issues at all. Once in a while I can't get VLC to kill audio streaming, but that could be the app (?).
I got the same deal, but I got my 1907 WITH global rom already installed for reference.
I might be moving to LOS since magisk with OOS11 and Viper4android/JamesDSP are not functioning. Even with Dora Kernel.
 

sputnik13121974

New member
Sep 1, 2021
4
1
tested today everything vorking didnt test gogle pay . wifi,lte,hotspot wifi thether vpn,call network,battery drain ok ,no complikated.if interesting i flash that way
1 unocked bootloader,adb,usb,on phone set max time screen
2 install lineage recovery18 fastboot
3 didnt install like lineage said copy partition !!! important
4 from recovery factory reset
5 select “Apply Update”, then “Apply from ADB” to sideload lineage zip
6 you will see process stop at 47 % ,dont worry see on phone step1,2 after few min if everything ok you will see failed to read no error
7 advanced then reboot to recovery then apply update aply from adb sideload finalize.zip(small file make copy for bouth partition i find from may previos 6t said thanks for that gay)
8 phone ask for signature put yes
9 reboot again to recovery then adb sideload open gapps i take from open gapps site ,phone ask again for signature put yes
10 reboot to recovery then factory reset
11 reboot to boot
Thanks
 

Attachments

  • Finalize.zip
    1.6 KB · Views: 5

peppers42

New member
Sep 4, 2021
3
2
Please someone help any ROM I install phone mic does not work. The other person only hears a loud ringing noise. I can hear them tho. Anyone else having this issue?
 
  • Like
Reactions: aenubis

xdabushrang3r

Senior Member
Feb 14, 2016
298
67
OnePlus 7T
Redmi Note 8 Pro
I have just installed this ROM.
I have two apps that I use the phone lock pattern to unlock.
Each time I try to unlock them, I touch the first dot in the unlock sequence and the system ui crashes. I thought it was the app that was the problem, but it started happening on another app too.
This problem does not occur when using a PIN number to lock the apps.
 
Last edited:

Orion9k0

Senior Member
Oct 30, 2015
85
19
Has anyone been able to get the stock OP7T Cam to work? I've tried the stock Lineage and GCam, but neither are as good as stock.

Also, I wish there was a way to hide notch...
 

aenubis

Member
Sep 7, 2021
8
1
Please someone help any ROM I install phone mic does not work. The other person only hears a loud ringing noise. I can hear them tho. Anyone else having this issue?

I am as well having this issue.

Nope, flash stock and see if hardware prob

Did that, works fine in OOS.

Thought maybe the phone was hosed, as I got a HD1907 refurbed on ebay, and with the intent to immediately unlock and flash it, so I didn't even do any testing to make sure it was good. Didn't even test it waiting the week for the unlock code. Installed lineage 18 (and older build), moved in, thought everything was good (I don't make many phone calls) and ran into this issue. Tried the latest build of 18.1, and just tried DotOSv5.1.3, and all the same. Wanted to use HavocOS originally, but it doesn't see my sim. Seems to be a rom for a dual sim phone, so maybe I didn't check the rom specifics close enough. Found the stock image flashes via the MSM tool method, and got Oneplus_7T_T-Mobile_11_O.01_200904 installed. Tested phone, worked normally.

The only thing I've done (and not very scientifically) to produce any difference is network settings, and on some settings it's a loud constant beep, and on other settings it's what you'd describe as the begining of a modem screech. No audio can be heard around either, and the audio incoming is fine. I can hear them, they can hear beep. Feels like a driver problem. To be fair, HD1907 isn't in the LOS wiki as supported for the 7t. Just all the other variants, and it seems like most of the other roms are based on the same original rom driver extraction.
 

peppers42

New member
Sep 4, 2021
3
2
Update on my issue. Flashed back to stock using MSM tool. Updated OOS to latest version. Did unlock via developer settings. BTW I didn't need unlock.bin to unlock my bootloader after updating to latest OOS. Flashed recovery and reflashed crDroid (also tried Lineage) with same results. Cleared data and factory reset in recovery, did not try clearing dalvik cache (that might be the issue). The other caller always hears this loud ringing sound like "ringing in your ears". I gave up and got a Pixel 5a 5G. Will receive that tomorrow hoping for better results. I just want a custom ROM without tons of preloaded garbage/analytics.
 
  • Like
Reactions: xdabushrang3r

HueyT

Senior Member
Apr 3, 2014
4,179
1,954
New Albany, IN
OnePlus 7T
Update on my issue. Flashed back to stock using MSM tool. Updated OOS to latest version. Did unlock via developer settings. BTW I didn't need unlock.bin to unlock my bootloader after updating to latest OOS. Flashed recovery and reflashed crDroid (also tried Lineage) with same results. Cleared data and factory reset in recovery, did not try clearing dalvik cache (that might be the issue). The other caller always hears this loud ringing sound like "ringing in your ears". I gave up and got a Pixel 5a 5G. Will receive that tomorrow hoping for better results. I just want a custom ROM without tons of preloaded garbage/analytics.
If it works fine in oos11 then u need to convert hd1907 to global using hacked msmtool to use custom ROM correctly:

 
Last edited:
  • Like
Reactions: aenubis

xdabushrang3r

Senior Member
Feb 14, 2016
298
67
OnePlus 7T
Redmi Note 8 Pro
If it works fine in oos11 then u need to convert hd1907 to global using hacked msmtool to use custom ROM correctly:

I bought a HD1905 on global, flashed this ROM, and now the mic doesn't work. (I can hear others but they can't hear me)

How do you clear cache and dalvik on this rom?
 

aenubis

Member
Sep 7, 2021
8
1
If it works fine in oos11 then u need to convert hd1907 to global using hacked msmtool to use custom ROM correctly:


Thanks. Tried HavocOC again first, and it was both able to see my sim, and didn't have my call problem. Would probably fix the issue in lineage as well. Might verify later.
 

xdabushrang3r

Senior Member
Feb 14, 2016
298
67
OnePlus 7T
Redmi Note 8 Pro
Thanks. Tried HavocOC again first, and it was both able to see my sim, and didn't have my call problem. Would probably fix the issue in lineage as well. Might verify later.

Interesting that your mic didn't work the first time you tried Havoc but it worked the second time. What did you do differently? Maybe your mic would work if you tried Lineage again?
Do you mean Havoc (Android 10)?
 

aenubis

Member
Sep 7, 2021
8
1
Can you post a link for that please? I can't find it in this forum. Only Android 10.

So I think it got taken down...


I downloaded 4.6 in a mad dash to just get a bunch of roms on my PC to choose from, and couldn't find it the next time I sat down. A website linking to 4.8 also drops you on the above link, which only currently has 3.1. Maybe it can be updated OTA from there?
 

xdabushrang3r

Senior Member
Feb 14, 2016
298
67
OnePlus 7T
Redmi Note 8 Pro
So I think it got taken down...


I downloaded 4.6 in a mad dash to just get a bunch of roms on my PC to choose from, and couldn't find it the next time I sat down. A website linking to 4.8 also drops you on the above link, which only currently has 3.1. Maybe it can be updated OTA from there?
Thanks for that. I wonder why it was taken down.... 🤔
Interesting that the mic works on Havoc (A11). Maybe it will be released again here on the forum....
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I tried that as well. The moment I boot the image the errors occur. But only on LineageOS, no problems with stock rom.
    Hmm. I very vaguely remember running into something similar a few years back. I believe what ended up being the fix for me was to go back to 100% stock (use the MSM tool to flash stock everything), then start the process fresh. If memory serves, it ended up being a nonstandard partition that was being missed by all the other install methods. This got everything back to where it needed to be, and I had no issues after.
    1
    About GCam:
    FYI, I use Nikita's NGCam 7.4.104 (NGCam_7.4.104-v2.0_eng.apk)... No sweat so far.
    In attached file, my config file for Nikita's NGCam 7.4.104.

    About updating firmware on hotdogb:
    If needed, you can download the required files for updating your firmware here (unzip and follow the official instructions ... use LOS recovery in fastbootD mode)
    1
    Hmm. I very vaguely remember running into something similar a few years back. I believe what ended up being the fix for me was to go back to 100% stock (use the MSM tool to flash stock everything), then start the process fresh. If memory serves, it ended up being a nonstandard partition that was being missed by all the other install methods. This got everything back to where it needed to be, and I had no issues after.
    IT WORKED! THANK YOU SO MUCH!!!!!!!!
    I did everything as you said and went back to stock via MSM tool and now everything works perfectly. I nearly gave up but thanks to you I now have a working phone.
    Thank you!
    1
    I'm having an issue after flashing. Everything works awesome until I try to call someone. I can hear them but all they hear is a high pitch tone. Plus it seems like i can hear what I say echoed back at me from the speaker. Any assistance you can provide would be appreciated.

    This is a known issue. You need to flash stock firmware to get the mic to work. Follow the instructions below.

    1
    I figured it out. I wasn't in fastbootd.
  • 51
    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 /proc/last_kmsg. (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:
    4
    Latest August 1st Update seems to have screwed up the fingerprint unlock.

    Re-scanning the fingerprint works, but the issue is unlocking the phone with the fingerprint.

    It almost always says "Not recognized".

    This was not an issue before this update.
    4
    For those unhappy about the camera app situation I've found that the stock Oneplus camera app can be installed and used with a few caveats. This was tested on the May 30th LOS build, below I list a few notes to keep in mind for anyone interested:
    1. In my limited testing, APKs with version number 3.X.X are the newest ones that can be installed and actually work. Specifically 3.8.116 is the most stable I've found. The apk can be download here (APKMirror link).
    2. The app will always crash upon normal launch. In order to use it you must long press on the app icon and select one of the popup shortcuts (Pro, Take a video, Selfie, or Portrait). Launching from any of these shortcuts the camera app will work and so far I believe all the camera features work.
    3. There might be occasional crashes mostly due to switching between camera modes too much (Most notable on other 3.X.X versions).
    4. In Photo mode (not Pro mode) the aspect ratio button works only on 4:3 and 1:1, switching to fullscreen will render photo mode unusable as the app will crash upon switching to it. Other modes will still function as normal and Pro mode can use fullscreen aspect ratio without issues. If you accidentally switched to fullscreen aspect ratio in photo mode then it can be fixed by clearing the app data.
    5. The gallery button does not work, likely due to the missing oneplus gallery apk. Probably it will work with it installed but I haven't tested that yet.
    6. Systemlessly installing the app to the system folder does not improve anything. So installing the apk as any other normal sideloaded app is probably the best option.
    I'm not sure if the rom can be tweaked to prevent the normal launch crash. Though I'm not expecting anything from the dev about this. The app works without much issue and I'm trying to workaround the launch issue with tasker. Hopefully I'm succesful with it.
    2
    Finally, thank you luk
    2
    for installing magisk, I always follow the following:
    • install magisk manager in the phone
    • extract the boot.img from the payload.bin
    • upload to phone
    • use magisk manager to install magisk to the boot image
    • fastboot boot the rooted boot image
    • when the phone boots again: you have root. Use magisk manager again to do a direct install to the current slot
    • reboot
    • profit