[ROM][OFFICIAL][redfin] LineageOS 20

Search This thread

Horrible Username

Senior Member
Jun 16, 2018
56
13
Well, LOS20 is broken for me (can only use internet over wifi). It seems that now 20 has been pushed to FOTM, the only way I can get security updates for 19 is to build it myself (19 hasn't been updated for over 1 mo.) Since I'd need to build it myself to keep "secure", I might as well go for 18 because, quite frankly, I can't stand Android 12. It looks like it was designed by and for preschoolers, loaded with feature bloat. Simple things on earlier versions of Android now need an expedition through nested menus.
Of course, this is just my opinion, and like I said, if I have to build a updated secure rom, it might as well be something I like using - although if it was remotely possible, I'd go all the way back to Oreo (I do like a simple clean UIX)
and as a bonus, I can also go back to using TWRP too
 
  • Like
Reactions: goodrench

andrew2432

Senior Member
@Ty07allstar
@AlkaliV2
@Horrible Username

I have had issues very similar to this since cyanogen with a galaxy s4. Sprint and lineage have always had issues together, sometimes making wonderful useful bugs but mostly ruining both worlds. Most custom Roms I try running require a prl update, and many times in the past its related to apns, or I've been able to find fixes that way, usually doing something semi related and it fixes itself.

Almost always while on sprint a custom is had much much worse signal than stock, and even worse data connection.

I want to come up to 20 from 18 myself, worried about this sim issue. I had a sprint esim, everything was working ok, I had constant phone heat ups and restarts that seemed to be related to LTE/5g but I assumed that was more related to the sprint issue. I have a physical Sim, T-Mobile. I think I can swap back to esim but since there's issues reported, I can't decide if I upgrade to the T-Mobile stock and try physical or you seem to have...better luck on esim than on physical Sim?
 

Ty07allstar

Senior Member
Mar 28, 2010
608
33
Nexus 7 (2013)
HTC One (M8)
@Ty07allstar
@AlkaliV2
@Horrible Username

I have had issues very similar to this since cyanogen with a galaxy s4. Sprint and lineage have always had issues together, sometimes making wonderful useful bugs but mostly ruining both worlds. Most custom Roms I try running require a prl update, and many times in the past its related to apns, or I've been able to find fixes that way, usually doing something semi related and it fixes itself.

Almost always while on sprint a custom is had much much worse signal than stock, and even worse data connection.

I want to come up to 20 from 18 myself, worried about this sim issue. I had a sprint esim, everything was working ok, I had constant phone heat ups and restarts that seemed to be related to LTE/5g but I assumed that was more related to the sprint issue. I have a physical Sim, T-Mobile. I think I can swap back to esim but since there's issues reported, I can't decide if I upgrade to the T-Mobile stock and try physical or you seem to have...better luck on esim than on physical Sim?
It seems like eSIM has been better but still causes issues. I have had no issues with my eSIM on Tello.
 
  • Like
Reactions: andrew2432

AlkaliV2

Senior Member
Jun 12, 2012
1,504
1,698
¯\_(ツ)_/¯
Google Pixel 5
if I upgrade to the T-Mobile stock and try physical or you seem to have...better luck on esim than on physical Sim?
I can't speak for anyone but myself but mine is a 5G to LTE hand off issue that happens no matter what SIM type I use. Not related to LineageOS at all because the hand off failed on stock Google January release also. So in this case I don't think what SIM you choose matters if you use T-Mobile and live in a place with bad 5G coverage or travel often.
 

andrew2432

Senior Member
I can't speak for anyone but myself but mine is a 5G to LTE hand off issue that happens no matter what SIM type I use. Not related to LineageOS at all because the hand off failed on stock Google January release also. So in this case I don't think what SIM you choose matters if you use T-Mobile and live in a place with bad 5G coverage or travel often.
Are you using the Feb stock that was released for T-Mobile?

@lefteyecat
@mad4ever92

I have a redfin nightly from 10.29 I could upload somewhere, check sig yourself.
 

AlkaliV2

Senior Member
Jun 12, 2012
1,504
1,698
¯\_(ツ)_/¯
Google Pixel 5
Are you using the Feb stock that was released for T-Mobile?
I have not tried it yet, my failures and issues were from January. I want to research which firmware components I can flash from February stock without compromising my LineageOS install. But if I can't, I will go back to stock clean and come back to LOS after that.

Seems like they re-enabled the OTA update based on posts I saw in the Pixel subreddit so the fix must be there.
 

andrew2432

Senior Member
I have not tried it yet, my failures and issues were from January. I want to research which firmware components I can flash from February stock without compromising my LineageOS install. But if I can't, I will go back to stock clean and come back to LOS after that.

Seems like they re-enabled the OTA update based on posts I saw in the Pixel subreddit so the fix must be there.

Im sure they have a wonderful "fix" lol I just saw the image on googles developers page. I'm all hacked up to use my free hotspot through sprint, so I can't help but wonder how much that helps the situation. I'm free the rest of the day, guess I'll try this swift backup and see how it goes
 
  • Like
Reactions: AlkaliV2

AlkaliV2

Senior Member
Jun 12, 2012
1,504
1,698
¯\_(ツ)_/¯
Google Pixel 5
Im sure they have a wonderful "fix" lol I just saw the image on googles developers page. I'm all hacked up to use my free hotspot through sprint, so I can't help but wonder how much that helps the situation. I'm free the rest of the day, guess I'll try this swift backup and see how it goes
I've been dragging my feet on converting back to stock for the fix because I have setup my phone on Lineage in a way I like. I jumped in the Lineageos discord yesterday asking for help with determining what firmware partitions I could flash from the Feb update to leave LOS intact. But while I wasn't ignored, when I answered their questions they didn't reply back. So...it looks like flash something, try to boot, write it down and repeat. Though I did find from searching that boot, system, vendor, dtbo and vbmeta should all be included every release/update. Anything outside of that I would be guessing.
 

mumal

Member
Jul 24, 2011
12
1
Hey everyone, I wanna give an update on my experience with this Rom!

First of all: great job @aleasto!
This Lineage is definitely smoother than stock rom. Seriously, my Pixel 5 feels like a true flagship now, finally the 765 is working like a charm.

_

Now, some little features I do really enjoy:

- percentage only in the status bar (no battery icon needed)
- you can hide the navigation bar (the one at the bottom of the screen) but use the phone as if it was visible
- FINALLY no google assistant swipe-up from the bottom of the screen!

There are also some little bugs, nothing serious:

- with google camera, changing from portrait mode to standard mode (and viceversa) usually slows down a little bit. Maybe it's just my gcam version.
- vocal messages: recording vocal audio messages often does not work. The recording is muted, I haven't figure out how am I able to fix it, but sometimes I am able to do it.

_

A quick guide on how to install this ROM (for lineage os newbies like me):
  1. Unlock the bootloader (here you can read how)
  2. Download all the files from the first post and put them in the "platform tools" folder
  3. Put the Pixel 5 in fastboot mode and connect it to the computer
  4. Open a prompt window in the platform tools folder
  5. Digit these commands:
    - fastboot flash boot boot.img
    - fastboot flash vendor_boot vendor_boot.img
    - fastboot flash dtbo dtbo.img
  6. Now you have to reboot into the recovery from the fastboot menu, just use the volume buttons to search the recovery option and select it with the power button.
  7. You will enter the Lineage Recovery, then select "apply update" -> "apply from ADB"
  8. Go back to your cmd window on your computer and write:
    "ADB sideload xxxxxxxxx.zip" where the "x part" is the name of the ROM zip file (remember to put .zip at the end of the command)
  9. Just wait until the end of the installation (around 5-8 minutes) and then reboot the phone from Lineage OS recovery.
  10. Enjoy!

Personally I wasn't able to install magisk correctly, if anyone got it working just let me know!

Again, thanks Ale for the awesome rom, can't wait to see it becoming official!
- you can hide the navigation bar (the one at the bottom of the screen) but use the phone as if it was visible

As???
 

baschi7

Member
Aug 21, 2010
19
0
Hi everyone, where can i find the Lineage os recovery files? On the Lineage page there is only the ZIP file for the Os itself.

Thx
 

thatsupnow

Senior Member
Jan 31, 2011
2,566
618
Vernon
Google Pixel 3a XL
Google Pixel 5
Anybody else notice battery life drops fairly quick when using earbuds?? I notice like a 15% or more drop after maybe an hour. On A12 I could go all night at the drill and still have 40% but there's no chance of that on A13, I'm on the latest but I found it was more or less the same on stock rom too. Maybe it's just an Android 13 thing
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hi, I just replaced my 6 year old phone with a Pixel 5 and now I was shocked to see that Stock ROM does not support exFat, which my old phone was able to.

    Does LOS support exFat via OTG?
  • 53
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android, 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. LineageOS does still include various proprietary hardware-specific code.

    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.

    Informations :
    • This ROM uses source built kernel, kernel modules, boot kernel modules (vendor_boot) and vendor image.
    • This ROM bundles the latest firmware so you don't have to worry about updating firmware.
    • To use the eSIM you need to install GApps
    Instructions :
    Downloads :
    Reporting Bugs
    • 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/* (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.

    Known Issues
    • None!
    Contributors
    mikeioannina
    aleasto
    The LineageOS team

    Source Code: https://github.com/LineageOS

    ROM OS Version: Android 13
    11
    New build out
    The final checkups before official rolls out.
    We've also managed to remove the need for flashing vendor_boot.img so now the install instructions are back in line with other pixels.
    11
    New build out
    Enable Adaptive Sound, Live Captions, Now Playing, Screen Attention pixel features.
    These all work without gapps, and all process data offline.
    11
    New build out
    • Feb 2021 security patch
    • Update modem firmware from the T-Mobile factory images to enable 5G Standalone.
      Google only did this for T-Mobile images (RQ1C.210205.006), but it doesn't seem to negatively affect non T-Mobile users, thus I'm including it in the generic build (RQ1A.210205.004 based).
    10
    Bluetooth HD Audio fixed in the next build