[OFFICIAL] LineageOS 19.1 for the Razer Phone 2 - Razer Phone 2 ROMs, Kernels, Recoveries, & Other D

[OFFICIAL] LineageOS 19.1 for the Razer Phone 2 - Razer Phone 2 ROMs, Kernels, Recoveries, & Other D

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Razer Phone 2
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Razer Phone 2.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
aura - Official builds
aura - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
Known bugs:
- Chroma RGB LEDs are not implemented yet
Known bugs (won't fix):
- Can't switch screen resolution (defaults to 2560x1440)
Find any more? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/LineageOS/android_kernel_razer_sdm845

Coming from PixelExperience. Performed a clean install of 19.1. Having an issue using a VoIP app. In this case Streams UC, but also experience the issue with voice calls on Signal. Everything works on outbound calls, but with inbound calls, the microphone isn't working. Caller cannot hear my voice. Any suggestions? Possible changes to the build.prop file?

runuts said:
Coming from PixelExperience. Performed a clean install of 19.1. Having an issue using a VoIP app. In this case Streams UC, but also experience the issue with voice calls on Signal. Everything works on outbound calls, but with inbound calls, the microphone isn't working. Caller cannot hear my voice. Any suggestions? Possible changes to the build.prop file?
Click to expand...
Click to collapse
it works on PE?

npjohnson said:
it works on PE?
Click to expand...
Click to collapse
No. This is why I switched from PE to Lineage 19.1 where it also didn't work. Flashed back to 18.1 and it is working.

Upgraded via adb successfully from the 18.1 ROM.
Got the 47% glitch during sideload, but it rebooted fine.
Similar results on my Razer Phone 1 (cheryl).
(Still mourning the end of HTC One M8 support, though.)

unsponsoredgeek said:
Upgraded via adb successfully from the 18.1 ROM.
Got the 47% glitch during sideload, but it rebooted fine.
Similar results on my Razer Phone 1 (cheryl).
(Still mourning the end of HTC One M8 support, though.)
Click to expand...
Click to collapse
Hint: I am working on m8 right now

npjohnson said:
Hint: I am working on m8 right now
Click to expand...
Click to collapse
That is good to know. I installed an unofficial LineageOS 18 ROM recently, but haven't played with it since then.

Just updated to LineagOS for MicroG 19.1 so far so good.

unsponsoredgeek said:
Upgraded via adb successfully from the 18.1 ROM.
Got the 47% glitch during sideload, but it rebooted fine.
Similar results on my Razer Phone 1 (cheryl).
(Still mourning the end of HTC One M8 support, though.)
Click to expand...
Click to collapse
If you read the install instructions this is normal behavior

npjohnson said:
Known Bugs:
Known bugs:
- Chroma RGB LEDs are not implemented yet
Click to expand...
Click to collapse
Not really a bug as its an app in the stock ROM. The current solution is to root and install Logo+ and it works.
Should also list Dolby Atmos missing too

omega552003 said:
If you read the install instructions this is normal behavior
Click to expand...
Click to collapse
I did. It was not unexpected.

I followed the instructions to the letter upgrading from 18.1 and mine is stuck in boot. It's been showing the little logo animation for almost 10 minutes now. Mild panic has set in.
edit: Fixed it!
Had the wrong gapps package. Downloaded the correct one, (MindTheGapps12.1 arm64 for those lost souls still out there).
Fixing procedure if stuck on LOS logo loop:
1. Make sure your devices is still plugged into your computer and hold down power button until you see the fastboot landing page where it gives you the option to pause boot. PAUSE BOOT.
2. hold down power button again to turn phone off. You'll know it's off when you get the white and black charge animation
3. hold power and volume down until you get to the recovery page.
4. Choose recovery mode, recovery from adb, and then run adb sideload /path/to/zip to install the correct gapps package.
Hope no one else does the same dummy move I did but if they do I hope this helps.
P.S. I have no idea yet what my screw up did long term btw. Device is still finishing the update. I did have to reinstall messages and gmail but for all I know that would have needed to happen anyway.

Just installed the UNOFFICIAL version on my Vzw RP2, but I can't make/receive calls/texts. Should Lineage work on the Verizon network?

edison said:
Just installed the UNOFFICIAL version on my Vzw RP2, but I can't make/receive calls/texts. Should Lineage work on the Verizon network?
Click to expand...
Click to collapse
Yes, it should. I remember seeing some folks have similar issues with 18.1 but I don't recall what the issue was. Maybe check out the 18.1 forums and see if there's any applicable advice there

Coming from Pixel Experience and I am getting audio crackling/stuttering only when using game streaming apps such as Moonlight and PSPlay and the volume is less than 50%. I had the same issue on Pixel Experience but the dev had fixed it using this commit. Any chance the fix can apply here too?

With the most recent build I am seeing Location pings even though Location is off and no apps are granted Location permissions. It was difficult, but I did get a screen capture of the event. You can see the location pip in the status bar. What is going on?

How do I root this version because I tried flashing the latest magisk zip and nothing happened do I have to rebuild the boot with magisk manager

Cylow333 said:
How do I root this version because I tried flashing the latest magisk zip and nothing happened do I have to rebuild the boot with magisk manager
Click to expand...
Click to collapse
I was looking for the same information

This is working very well for me keep up the good work. One thing I have found however is that while on a call rtt or tty as it is known seems to be on. I have made sure it is off in accessibility settings so I am sure it's just a bug but wanted to make aware of it. Does anyone else have this issue? I am on verizon. Not sure if that matters.

marcxpr said:
I was looking for the same information
Click to expand...
Click to collapse
I was able to root by adb sideload and running adb sideload followed by the magisk.zip file

Related

[OFFICIAL] [WEEKLIES] Lineage OS 15.1

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Moto Z2 Force
Code:
- Your warrenty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the official Lineage OS thread for the Motorola Moto Z2 Force, codename nash.
We support both the Sprint, International, and T-Mobile variants, as their bootloaders are unlockable, while we can 't support the Verizon and AT&T variants, as their bootloaders are permanently locked.
How to install:
Necessary Base Firmware: 8.0.0 (OCSX27.1.2, May 2018) (for TMO, or equivalent security patches for other variants)
Boot the newest TWRP .img from the Official TWRP Project Site.
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
ADB sideload the newest weekly
(Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need ot be re-installed every update), and has no addon.d-v2 persistence.
Click "Reboot, then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps - MindTheGApps arm64 are recommended, OpenGApps are compatible with A/B as of 09102018, but I still only reccoemend and support MindTheGApps.
(Optionally) Flash SU - you'll need to turn it on from in developer settings after first boot Lineage OS SU Addon. - Magisk works fine, though is not supported.
Reboot
Known Problems:
Audio Mods don't work (this includes headphone jacks on mods) -- We can't fix this, don't use custom ROM's if you care about these.
Official Lineage OS builds will not ever allow Moto's Battery Mod "Efficiency Mode" to work -- though these can be made to work unofficially, join our discord if you're interested in this feature.
Wi-Fi Calling won't work until either the International or T-Mobile variant gets 8.1 blobs.
Ultrasonic Proximity Sensor doesn't work -- likely won't ever. It is used my Motorola's Active Display, but by nothing in Lineage.
Compass doesn't work -- no clue why.
Stock Display Color Profiles (the ones in Settings, "Display", "Colors") -- The ones in Settings, "Display", "LiveDisplay" work.
The default LiveDisplay "Natural" setting in Settings, "Display", "LiveDisplay", will occasionally dispaly color corruption, to deal with this, just swap to the "SRGB" profile, and swap back to "Natural", or leave it on "SRGB if you don't mind, then you won't experience those infrequent issues.
Notes:
Official Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status.
Official Lineage OS builds ship with full treble compatibility, with VNDK runtime enforcement! This means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run any GSI (yes, even Pie!) without need for hacks or additional flashable zips. We relabeled /oem as /vendor (as /oem isn't used in custom ROM's anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image. Please don't report GSI bugs here, report them instead to the GSI's maker.
Download:
LineageOS Updater
XDA:DevDB Information
[OFFICIAL] [WEEKLIES] [TREBLE] Lineage OS 15.1, ROM for the Moto Z2 Force
Contributors
npjohnson, invisiblek, erfanoabdi
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: 8.0.0 (OCSX*)
Based On: LineageOS
Version Information
Status: Stable
Created 2018-07-15
Last Updated 2019-03-18

first (always wanted to do that)
thanks for this, nice work everyone!!!

Nice, I was wondering when we were going to get an official thread. I'll be waiting for the 17th to install the weekly.

I have the international version (-05) and have installed plenty of these version (since unofficial release from both invisiblek site and ods.ninja site) as well as the official weeklies (all versions already released) and everything works (based on the description here and known issues), so I'd say it's safe to say intl version had been tested and known to be working as well.
Let me know if you need additional/specific tests that I can do here.
Thanks the official post!
Also, how about volte support? Is it supposed to work?

felipevsw said:
I have the international version (-05) and have installed plenty of these version (since unofficial release from both invisiblek site and ods.ninja site) as well as the official weeklies (all versions already released) and everything works (based on the description here and known issues), so I'd say it's safe to say intl version had been tested and known to be working as well.
Let me know if you need additional/specific tests that I can do here.
Thanks the official post!
Also, how about volte support? Is it supposed to work?
Click to expand...
Click to collapse
If it isn't in the bugs list, its expected to work, it works on TMO and SPR. And I'll flag the international as compatible, thanks.

Since it isn't in known issues, I assume VoIP compression was fixed?
Edit: known workaround is use Bluetooth for video/VoIP calls. I don't know if USB audio would work or not.

Uzephi said:
Since it isn't in known issues, I assume VoIP compression was fixed?
Edit: known workaround is use Bluetooth for video/VoIP calls. I don't know if USB audio would work or not.
Click to expand...
Click to collapse
Added to OP as an issue.

??? for listing known accurate issues ???
I was pissed after installing Invictrix rom only to find out sound mods don't work.

I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.

fixed, can remove this.

DTHayakawa said:
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
Click to expand...
Click to collapse
Anything that uses VoIP compression is broken. Most video calling or internet calling apps in general use it.

DTHayakawa said:
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
Click to expand...
Click to collapse
1. Added to known bugs.
2. I don't experience this (and if it is present, its platform wide, and not our problem specifically).
3. I can't really easily support a prebuilt app all that easily. The B&W cam us supported in the default Snap camera.

Also, OTA will be broken until we figure out why signing server's aren't signing our payload zips right.
To work around this, you can update weekly by sideloading the nightly, rebooting to recovery (important), re-sideloading any mods you use (GApps, AddonSU, etc.).

fixed, can remove post now.

Uzephi said:
Anything that uses VoIP compression is broken. Most video calling or internet calling apps in general use it.
Click to expand...
Click to collapse
So I assume this would apply to hangouts and hangouts dialer?

npjohnson said:
Also, OTA will be broken until we figure out why signing server's aren't signing our payload zips right.
To work around this, you can update weekly by sideloading the nightly, rebooting to recovery (important), re-sideloading any mods you use (GApps, AddonSU, etc.).
Click to expand...
Click to collapse
Resolved.

Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?

MattKilla said:
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
Click to expand...
Click to collapse
I was literally plugging in to try this ROM until I read this. Have you tried Magisk yet?

Magisk Works
3's&7's said:
I was literally plugging in to try this ROM until I read this. Have you tried Magisk yet?
Click to expand...
Click to collapse
I have ran into this same issue when flashing build > lineage-15.1-20180721-nightly-nash-signed.zip
I can confirm that it happens with both TWRP 3.2.2-2 & TWRP 3.2.1-1
I flashed Magisk 16.4 and it works flawlessly no issues.
I am very happy with this ROM it works great for me. Thank You Devs! :good:

MattKilla said:
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
Click to expand...
Click to collapse
was TWRP installed or did you just boot to it?

[OFFICIAL] LineageOS 18.1 for the Moto Z2 Force

How did you find this? I got an alert that lineage 18 came out but went to the website less than five minutes ago and it wasn't available for nash yet ?
*Edit* I just checked again it's not available for download even though it's listed ..weird

PrivyetCyka said:
How did you find this? I got an alert that lineage 18 came out but went to the website less than five minutes ago and it wasn't available for nash yet ?
*Edit* I just checked again it's not available for download even though it's listed ..weird
Click to expand...
Click to collapse
Am the developer - and it is building on official servers tonight, check back in 24 hours.

npjohnson said:
Am the developer - and it is building on official servers tonight, check back in 24 hours.
Click to expand...
Click to collapse
Oh awesome. Thank you for the hard work ! Glad to see roms still being made for this phone

Just flashed on my t-mobile device from recovery. My phone is bricked. The battery life on my z2 force was getting old anyway so I am probably going to have to get a new phone if I can't fix it.
If you have a t-mobile device DO NOT FLASH FROM RECOVERY!!!

I fixed it! Please make sure to flash lineage from your computer when you are updating to a new version of lineage... NP Johnson makes this clear in his instructions. Unfortunately it has been awhile since I have flashed a rom onto a phone and I forgot that step...
here is how I did it
fastboot flash boot_b recovery-nash.img
factory reset your phone
flash the lineage zip from your computer using adb sideload lineage 18.1 nightly

Very good upgrade, thanks for the hard work and making this real

Thank you for not letting our device die

Thanks a ton for keeping our device up to date! I see that the efficiency mode is working for the battery mod, amazing!!

The clock app is not working and I think usb tethering is not working.

Vibration is not working

Firstly, THANKS FOR THIS!
I get the following error when opening the Camera app: dlopen failed: library "libmcf-jni.so" not found.
HDR mode is missing and you still can't save to SD - otherwise seems to work OK
Install steps taken:
1. adb sideload lineage-18.1-20210401-nightly-nash-signed.zip
2. Reboot into the newly-updated 18.1 recovery
3. adb sideload MindTheGapps-11.0.0-arm64-20210328_143848.zip
Since I was updating from 17.1 with Google Apps, I did not perform a factory reset per the upgrade instructions here: https://wiki.lineageos.org/devices/nash/upgrade
Was this wrong? Should I have done a clean install?

Big_Brother_Is_Watching said:
Just flashed on my t-mobile device from recovery. My phone is bricked. The battery life on my z2 force was getting old anyway so I am probably going to have to get a new phone if I can't fix it.
If you have a t-mobile device DO NOT FLASH FROM RECOVERY!!!
Click to expand...
Click to collapse
Flashing from recovery is fine - so long as you can see the zip, it's no problem. Not sure where your problem hit.
But thank you for ultimately flowing the guide and using your PC, it just raised and more seamless.

vivebatu said:
Thanks a ton for keeping our device up to date! I see that the efficiency mode is working for the battery mod, amazing!!
Click to expand...
Click to collapse
Yup! And will from here on out
Big_Brother_Is_Watching said:
The clock app is not working and I think usb tethering is not working.
Click to expand...
Click to collapse
Clock app works, maybe gapps overwrite it with a broken one? Will try usb tethering locally.
Manuelmartad said:
Vibration is not working
Click to expand...
Click to collapse
It works, your motor may have died.
wyldwilly said:
Firstly, THANKS FOR THIS!
I get the following error when opening the Camera app: dlopen failed: library "libmcf-jni.so" not found.
HDR mode is missing and you still can't save to SD - otherwise seems to work OK
Install steps taken:
1. adb sideload lineage-18.1-20210401-nightly-nash-signed.zip
2. Reboot into the newly-updated 18.1 recovery
3. adb sideload MindTheGapps-11.0.0-arm64-20210328_143848.zip
Since I was updating from 17.1 with Google Apps, I did not perform a factory reset per the upgrade instructions here: https://wiki.lineageos.org/devices/nash/upgrade
Was this wrong? Should I have done a clean install?
Click to expand...
Click to collapse
dlopen, HDR, and save to SD: all expected and WIP. Working on them

npjohnson said:
Yup! And will from here on out
Clock app works, maybe gapps overwrite it with a broken one? Will try usb tethering locally.
It works, your motor may have died.
dlopen, HDR, and save to SD: all expected and WIP. Working on them
Click to expand...
Click to collapse
Noice/Thanks!
Oh, I'd like to report that my Mophie external battery seems to be working better than it did in 17.1.

wyldwilly said:
Noice/Thanks!
Oh, I'd like to report that my Mophie external battery seems to be working better than it did in 17.1.
Click to expand...
Click to collapse
That's efficiency mode and proper battery mod support for ya! Haha.

npjohnson said:
Yup! And will from here on out
Clock app works, maybe gapps overwrite it with a broken one? Will try usb tethering locally.
It works, your motor may have died.
dlopen, HDR, and save to SD: all expected and WIP. Working on them
Click to expand...
Click to collapse
no, its not working i tried it on;stock and it works well

Wifi is not working, everything else looks fine. No using cellular (no chip in device). Any ideas?

idelgador said:
Wifi is not working, everything else looks fine. No using cellular (no chip in device). Any ideas?
Click to expand...
Click to collapse
sounds like a persist issue - did you ever flash pie firmware?

npjohnson said:
sounds like a persist issue - did you ever flash pie firmware?
Click to expand...
Click to collapse
Is that related to a previous flash of pie? :O

[OFFICIAL] LineageOS 18.1 for the Google Pixel 3a XL

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Google Pixel 3a XL
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for the Google Pixel 3a XL.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
bonito
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/LineageOS/android_kernel_google_msm-4.9

Going to try it now.
Thank you!

npjohnson said:

Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Click to expand...
Click to collapse
syntax error Are we talking about the Kernel being bundled?

ssurell said:
syntax error Are we talking about the Kernel being bundled?
Click to expand...
Click to collapse
What? No, firmware, like modem, bootloader, etc.

Question:
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
So are you saying if we root there is no support? As most of us coming from stock would at least need root temporarily to restore all our apps.
Can anyone confirm if root even works on this build. I woudnt see any reason not but would like to know cause of the above reason.
UPDATE: Decided to just go for it and everything is working great so far. Took a little work to get google apps working instead of the included aosp ones (phone calendar and contacts) and a bt more work to get it to pass safteynet but its all working 100% now. Also tested this build with both ex kernel and mvk and they both seem to work just fine as well. Will report back if anything changes as have only been running it.a few hours but so far no issues or complaints at all.
Great job LOS team

What is the official way to obtain root access? or is there one any more?

cliffordd said:
What is the official way to obtain root access? or is there one any more?
Click to expand...
Click to collapse
Based on the above statement i quoted sounds like root is not "officially" supported at all. That said to get root i followed the process by which you patch a boot image file with magisk manager. Making it pass safteynet net took additional steps.
If you need more details on either process just post back and i can be more detailed

adm1jtg said:
If you need more details on either process just post back and i can be more detailed
Click to expand...
Click to collapse
Yes please - maybe message me off thread, as this topic might not be appropriate on here.
I have Magisk app installed, due to using Titanium Backup to keep a backup of my app. The upgrade went great and everything is working fine under LOS 18.1. But I miss the ability to take backups and use certain features properly on the device (ie clipboard sharing and other features in KDE Connect, scheduling backups etc) There used to be a package provided by LOS to add or remove su - https://download.lineageos.org/extras but that seems to have stopped now. I was just wondering if there was an "official" way of doing it!
I actually held off upgrading due to the previous download being released on 1st April and not finding some previous April fools pranks to be very funny!!

cliffordd said:
Yes please - maybe message me off thread, as this topic might not be appropriate on here.
I have Magisk app installed, due to using Titanium Backup to keep a backup of my app. The upgrade went great and everything is working fine under LOS 18.1. But I miss the ability to take backups and use certain features properly on the device (ie clipboard sharing and other features in KDE Connect, scheduling backups etc) There used to be a package provided by LOS to add or remove su - https://download.lineageos.org/extras but that seems to have stopped now. I was just wondering if there was an "official" way of doing it!
I actually held off upgrading due to the previous download being released on 1st April and not finding some previous April fools pranks to be very funny!!
Click to expand...
Click to collapse
sent you a private

cliffordd said:
What is the official way to obtain root access? or is there one any more?
Click to expand...
Click to collapse
i flashed the version of Magisk (v21.4) via the LineageOS recovery using the adb sideload and just updated to v22 via the app. I haven't had any issues with root since installing.

First off, I want to say thank you for all the hard work on these builds.
I have came across one issue that isn't working for me, but might not be something everyone else uses a lot. My "squeeze" for Assistant isn't working, but I can change it to take a screenshot of any other option, except the Assistant. Am I doing something wrong or is there another settings need to activate for it to work?
Thanks!

Really want to try this, but can't "fastboot boot twrp.img" or "fastboot flash boot twrp.img" in Android 11 to backup my partitions. What's the point of Android OS if I can't backup my system? I can boot into Lineage OS Recovery, enable adb, figure out the partition names, dd the partitions from shell or pull with adb? But good grief, kinda ridiculous if you ask me.

Haven't been able to use twrp since Android 9 far as i know

lineage-18.1-20210401-nightly-bonito-signed.zip
Searching Settings aborts after a matter of seconds and while typing.
Derelict non-clearable notifications requiring reboot or force close.
Desk Clock stuck at "Loading".
The final LOS 17 seems more polished, but lingering notifications are still present requiring force close.

Nevermind, user error.

ssurell said:
lineage-18.1-20210401-nightly-bonito-signed.zip
Searching Settings aborts after a matter of seconds and while typing.
Derelict non-clearable notifications requiring reboot or force close.
Desk Clock stuck at "Loading".
The final LOS 17 seems more polished, but lingering notifications are still present requiring force close.
Click to expand...
Click to collapse
you're using opengapps - don't do that ;p
Use MindTheGapps, which doesn't break that feature.

npjohnson said:
you're using opengapps - don't do that ;p
Use MindTheGapps, which doesn't break that feature.
Click to expand...
Click to collapse
Actually, it's the first time I've used MindTheGapps. I used OpenGapps after falling back to 17.1 though since it is recommended on the LOS site. I kind of liked the Slim Gapps feel of MTG though, and might try it on 17.1

ssurell said:
Actually, it's the first time I've used MindTheGapps. I used OpenGapps after falling back to 17.1 though since it is recommended on the LOS site. I kind of liked the Slim Gapps feel of MTG though, and might try it on 17.1
Click to expand...
Click to collapse
weird - we don't have MTG builds for 17.1 though, sadly.

How do I disable encrypted device? Tried ElemntalX kernel and Disable_Dm-Verity_ForceEncrypt_quota.zip but phone is still encrypted under security settings after first boot.
When I see "Say Hello To Trust", I just want to punch it in the face. Somebody just needs to build an updated LOS 16 so we have TWRP and possible access to /data (formerly user space) and call it a day.

ssurell said:
How do I disable encrypted device? Tried ElemntalX kernel and Disable_Dm-Verity_ForceEncrypt_quota.zip but phone is still encrypted under security settings after first boot.
When I see "Say Hello To Trust", I just want to punch it in the face. Somebody just needs to build an updated LOS 16 so we have TWRP and possible access to /data (formerly user space) and call it a day.
Click to expand...
Click to collapse
Why do you want encryption disabled?
It's hardware backed, and FBE, so very little gain from running unencrypted...
"Trust" has nothing to do with encryption, it can be on, off, trust just reports it to the user.
Why do you want TWRP? Lineage Recovery does the job just fine. What do you mean "/data (formerly userspace)"? That statement doesn't make much sense.
Regardless of all the above, the disabel force encrypt zip, followed by `fastboot -w` to format userdata ought to do it - but be warned, if you set a PIN, Android (AOSP, not a lineage thing specifically) will re-encrypt you... hence there being no point.

[ROM][UNOFFICIAL] LineageOS 17.1 for Lenovo Tab M10 HD (TB-X505F/L/X)

Reserved.

can we flash it on x505x?

UDONTHAVERIGT said:
can we flash it on x505x?
Click to expand...
Click to collapse
Yes it should work on x505x.

I am reporting with an X505f, Lineage OS logo appears but goes into a bootlop ending up TWRP? How can i debug more? Any advice?
For reference OTA is at TB-X505F-S001142-210804_ROW.zip

What do i do when i have S001137? Can i just normally install this? TB-X505F
(I have twrp btw)

sinhus said:
I am reporting with an X505f, Lineage OS logo appears but goes into a bootlop ending up TWRP? How can i debug more? Any advice?
For reference OTA is at TB-X505F-S001142-210804_ROW.zip
Click to expand...
Click to collapse
Please format data and enable ADB On boot.

DominicNoobAtRoming said:
What do i do when i have S001137? Can i just normally install this? TB-X505F
(I have twrp btw)
Click to expand...
Click to collapse
I recommend upgrading to S001142 for safety reasons (since I'm not really sure about the changes Lenovo did between the updates).

tried this rom on a x505f.
A few issues:
1. I couldn't get it to start unless gApps was installed.
2. I also can't get the wifi to work at all.

How do i install the update safely becauss im worrying about bricking my tab

yukeiw said:
tried this rom on a x505f.
A few issues:
1. I couldn't get it to start unless gApps was installed.
2. I also can't get the wifi to work at all.
Click to expand...
Click to collapse
1. I didn't need GApps here. What do you mean "can't get it to start"? Care to be specific?
2. WiFi works OOTB here, but it may be due to kernel (highly unlikely tho as I tested kernels of all 3 tabs on my X505L). Were you on S001142?

henloboii said:
1. I didn't need GApps here. What do you mean "can't get it to start"? Care to be specific?
2. WiFi works OOTB here, but it may be due to kernel (highly unlikely tho as I tested kernels of all 3 tabs on my X505L). Were you on S001142?
Click to expand...
Click to collapse
I have same issue S001142, no WiFi on X505F, toggle just flicks on/off instantly.
However works fine without GApps (only because it wouldn't install, not enough system space Err70 apparently)

Same problem on my X505F, no WiFi. GApps worked well.

Can any X505F users send logs? I would like to take a look.

henloboii said:
Can any X505F users send logs? I would like to take a look.
Click to expand...
Click to collapse
happy to assist if you tell me what logs/where to pull them from, someone on telegram group said they were updating the image?

I tried this on my X505L and I couldn't get it to boot using S001142 and TWRP following the instructions exactly, is there a way to log or debug it if it doesn't boot, or do I have to reflash the firmware and hope for a better attempt?

Hi,
I tried it on my X505F and it was not as easy as I thought. I already had S001142 and started with installing TWRP as denoted here:
[RECOVERY][TB-X505F][UNOFFICIAL] TWRP 3.6.x for Lenovo Tab M10 HD
This version of TWRP works on the Lenovo TB-X505F (wifi). For the TB-X505X, see this thread. For the TB-X605F/L, see this thread. For the TB-X606F/L, see this thread. The X606F/L is the second gen M10 and it uses a Mediatek SOC. #include...
forum.xda-developers.com
Installing Magisk led to some problems, though, as the wipe of /data afterwards prevented me from flashing the ROM ("Magisk binaries not found"). I had to install Magisk again *and* create a symlink from /data/adb/magisk to /data/magisk to be able to uninstall it again (additionally to renaming it to uninstall.zip etc.). Then I was able to flash this LineageOS.
It didn't boot, though, but was stuck at the Lenovo logo (very early boot phase). I flashed it again, but it didn't help. What *did* help was installing Magisk via TWRP Now the tablet booted into LineageOS, but only with an Android popup that some internal error occured and I should contact my vendor.
After having a black screen for a minute or so the LinageOS setup UI appeared and I was able to set up the clock. When reaching the WiFi page, I wasn't able to switch it on (like the other reported).
Attached you find a logcat and the dmesg output. I hope that's what you need.

I would love to try this but i do use bt audio so i look forward to any updates. i dont think ill ever see this thing run anything past android 10, but im not too worried about that, i know its an old cheap tablet. are you able to expand internal storage to an sdcard? my number one complaint about this thing is it always complaining of low storage.

Hay dose anyone have a copy of the stock firmware (so
TB-X505F-S001142-210804_ROW.zip)

I had the exact same experience as this. Ah well... It would've been nice to strip out this Lenovo bloated ROM with something sleeker.

[Discontinued][ROM][12.1][Unofficial][Instantnoodlep] Lineage OS 19.1 [08-11-22]

Official Lineage OS 19.1 is here, so there is no reason to continue these unofficial builds. That was fast!! Thank you for those who gave their support. If you were on this build, you should be able to update to the official August 28, 2022 build directly from the updater (or dirty flash it yourself).
Lineage OS 19.1 - Unofficial
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi all. I noticed that there isn't official Lineage OS support for our OnePlus 8 Pro past version 18.1, so I decided to attempt building 19.1. Since it appears to be working correctly, I wanted to share it with anyone else who has an interest. I'm not changing anything about it (other than making it compile) and building straight from the Lineage OS sources. I'll attempt to build it roughly 1x per month, usually around the middle to allow for most security updates to take effect. I daily drive the ROM, so I'll only post updates when I see basic functionality working.
Latest ROM and recovery, August 11, 2022:
ROM
Recovery
Old Releases:
Older ROM/Recovery
Follow the official directions in order to flash the ROM and recovery files:
https://wiki.lineageos.org/devices/instantnoodlep/install
OTA Support:
I modified the built in updater to support updates from my unofficial source for all flashed builds after 8/11/22. I added an option under preferences to go back to the official source in the event that official builds are started. Just go to Settings -> System -> Updater to check. I plan on uploading to OneDrive and Dropbox for these updates (bandwidth might be temporarily limited). You can always manually flash without it from a PC.
Sources:
https://github.com/LineageOS
https://github.com/TheMuppets/proprietary_vendor_oneplus
https://github.com/LineageOS/android_device_oneplus_instantnoodlep
https://github.com/calsurferpunk/android_device_oneplus_sm8250-common
https://github.com/LineageOS/android_hardware_oneplus
https://github.com/LineageOS/android_kernel_oneplus_sm8250
https://github.com/calsurferpunk/android_packages_apps_Updater
https://github.com/calsurferpunk/lineageos_update
(roomservice.xml attached to this post for reference)

Based on OOS11 or OOS12?

doesn't recognise sim card

The_Lord_of_Lost said:
doesn't recognise sim card
Click to expand...
Click to collapse
I'm not sure what carrier you have, but I've been using AT&T in the United States without any issue.

keaheng said:
Based on OOS11 or OOS12?
Click to expand...
Click to collapse
It should be OOS12 if that's what the TheMuppets GitHub is using for the vendor (if that's the same thing). Otherwise everything is just straight from the Lineage OS GitHub.

calsurferpunk said:
I'm not sure what carrier you have, but I've been using AT&T in the United States without any issue.
Click to expand...
Click to collapse
Im using vodafone uk ,18.1 works perfectly fine but 19.1 is has slow response (especially settings options) and doesn't recognise sim

The lineageOS rom installs fine and looks good. I sideloaded the Mind the GAPPS package directly afterward before booting as directed with ver12.1 arm64 but there is no sign of Google play anywhere on the device. I have repeated 3x and downloaded package twice. Another GAPSS? Anyone else have this? I have not tried another GAPPS package but might do that

p-we said:
The lineageOS rom installs fine and looks good. I sideloaded the Mind the GAPPS package directly afterward before booting as directed with ver12.1 arm64 but there is no sign of Google play anywhere on the device. I have repeated 3x and downloaded package twice. Another GAPSS? Anyone else have this? I have not tried another GAPPS package but might do that
Click to expand...
Click to collapse
Have now tried several other GAPPS including NikGApps 12.1 but while it seems to install normally, not a trace of it on the phone itself

p-we said:
Have now tried several other GAPPS including NikGApps 12.1 but while it seems to install normally, not a trace of it on the phone itself
Click to expand...
Click to collapse
I've got GAPP's working. At least NikGApps 12.1 as I didn't verify the others. It wasn't clear in the instructions that you have to perform a recovery reboot between sideloading lineageOS and GAPP's.

Warp charging and wireless charger with quiet mode working?
Is face unlock on board?

everything works perfectly, to see if the battery life is good. Thanks!

New build for 8/11/22. See first/main post.

thanks

Installed this yesterday, with mindgapps and magisk. Works like a charm. Thanks for compiling this

Is there any progress on getting this to official status? I'm running official 18.1 but I'd really like to be on Android 12 at some point so I'm looking forward to being able to update, I just don't feel like wiping or having there be any hassle with data.

Got this installed yesterday with nikgapps and magisk. working great! warp charging doesn't say warp charging, but considering it went from 10% to 50% in 5 or 6 minutes, it's definitely there.
only thing, and it's not you, it's lineage, is not being able to change the display refresh rates. Hopefully that's something coming down the line..
What was sad was that Google backup and restore didn't see this as an IN2025 anymore. It shows as IN2023. But titanium backup kept my apps backed up enough

mattgyver said:
Got this installed yesterday with nikgapps and magisk. working great! warp charging doesn't say warp charging, but considering it went from 10% to 50% in 5 or 6 minutes, it's definitely there.
only thing, and it's not you, it's lineage, is not being able to change the display refresh rates. Hopefully that's something coming down the line..
What was sad was that Google backup and restore didn't see this as an IN2025 anymore. It shows as IN2023. But titanium backup kept my apps backed up enough
Click to expand...
Click to collapse
Afaik you can change the display refresh rate on lineage. They enabled a feature available in AOSP called "Smooth display"
Settings > Display > Smooth display
Keeping this off will have the device use the minimum refresh rate at all times (60hz). Turning it on will cycle between 60/120 depending on touch input.
You can also force the peak refresh rate by enabling "Force peak refresh rate" in developer options.

AnierinB said:
Afaik you can change the display refresh rate on lineage. They enabled a feature available in AOSP called "Smooth display"
Settings > Display > Smooth display
Keeping this off will have the device use the minimum refresh rate at all times (60hz). Turning it on will cycle between 60/120 depending on touch input.
You can also force the peak refresh rate by enabling "Force peak refresh rate" in developer options.
Click to expand...
Click to collapse
Thanks for that!

calsurferpunk said:
Official Lineage OS 19.1 is here, so there is no reason to continue these unofficial builds. That was fast!! Thank you for those who gave their support. If you were on this build, you should be able to update to the official August 28, 2022 build directly from the updater (or dirty flash it yourself).
Click to expand...
Click to collapse
Thanks for your work with the unofficial build. Greatly appreciated, at least from my perspective!

Are we going to still get security updates ? or its THE END? for 18.1?

Database Develop

welcome