[ROM][10.0][OFFICIAL] LineageOS 17.1

Bodygard379 · Oct 26, 2017 35 6 8

Oneplus has released a new official build OxygenOS 10.0.1 today. Let's wait and see.

Besuz · Nov 11, 2020 at 12:33 PM

@whatnoww Thats the trick, hiding Magisk from Play Services. Will update my post aswell, thx!
@andreivassaliev Its recommended to do a clean installation.
For recovery T1mb3 advised that if you want to use a "stock like Lineage", Lineage recovery is fine, otherwise use TWRP as TWRP will give you more flexibility.

andreivassaliev · Jul 18, 2013 11 4 0

Besuz said:
@whatnoww Thats the trick, hiding Magisk from Play Services. Will update my post aswell, thx!
@andreivassaliev Its recommended to do a clean installation.
For recovery T1mb3 advised that if you want to use a "stock like Lineage", Lineage recovery is fine, otherwise use TWRP as TWRP will give you more flexibility.

Thank you @Besuz

In fact, since official LOS 14 (14->15, then 15->16), I always performed the "upgrade" instructions, without clean install. I never had any issues doing this.
The problem is I always forget excatly the steps I performed (I really should write down the steps on a text file for future upgrades) ...
So, just to be sure, I prefer ask here if I plan rightly my upgrade process from officials LOS 16.0 to LOS 17.1 (?):

- Upgrade to latest available official firmware (https://sourceforge.net/projects/lineageos-cheeseburger/files/firmware/)
- Upgrade to latest available TWRP (https://dl.twrp.me/cheeseburger/)-
- Flash the LineageOS 17.1 through TWRP.
- Flash latest Magisk (20.4)
- Flash OpenGapps (nano, or pico)
- Reboot

Thank you all !

AshenFire579 · Oct 8, 2020 22 0 1

Do we now need to flash the 10.0.1 update before flashing the official LineageOS version or can we stick with hotfix 1

Besuz · Nov 11, 2020 at 1:50 PM

Personally I would do it this way:
- Disable screen lock/Pin
- Create a backup

- Flash latest TWRP
- Reboot to recovery
- Flash latest firmware
- Wipe anything except "Internal Storage"
- Flash Lineage
- Flash gapps (I have used nano)
- Reboot to System
- Go through initial config
- Reboot to recovery & flash Magisk

meta1hacker · Nov 12, 2020

I've just dirty flashed over LOS 16.
If someone cannot open the gallery, just clean up the media provider data (com.android.provider.media) (This will not delete your pictures, it just clears some cache).
If someone cannot open the camera setting (com.lineages.snap), just clean up it's data (This will not delete your pictures).
Hope to help people who have the same problem.

IcerJo · Nov 11, 2020 at 1:52 PM

AshenFire579 said:
Do we now need to flash the 10.0.1 update before flashing the official LineageOS version or can we stick with hotfix 1

Hotfix till the new Firmware is implemented from my understanding.

Sent from my ONEPLUS A5010 using Tapatalk

T1mb3 · Nov 11, 2020

AshenFire579 said:
Do we now need to flash the 10.0.1 update before flashing the official LineageOS version or can we stick with hotfix 1

So yeah just stick to the instructions for now

. Hotfix 1.

andreivassaliev said:
- Upgrade to latest available official firmware (https://sourceforge.net/projects/lineageos-cheeseburger/files/firmware/)

Use firmware mentioned in first post.

I can see why the official instruction ("Download the latest firmware zip file for cheeseburger") can be a little misleading, but I have to release the firmware zip before the rom update is released.

LordMethenor · Nov 9, 2020 8 1 3

Is there any way to put this Thread on the ROMs feed for the 5? I get why it's on cross-development, but it might be a lot easier to find the official thread there as well.

andreivassaliev · Nov 13, 2020

andreivassaliev said:
Thank you @Besuz

In fact, since official LOS 14 (14->15, then 15->16), I always performed the "upgrade" instructions, without clean install. I never had any issues doing this.
The problem is I always forget excatly the steps I performed (I really should write down the steps on a text file for future upgrades) ...
So, just to be sure, I prefer ask here if I plan rightly my upgrade process from officials LOS 16.0 to LOS 17.1 (?):

- Upgrade to latest available official firmware (https://sourceforge.net/projects/lineageos-cheeseburger/files/firmware/).
- Upgrade to latest available TWRP (https://dl.twrp.me/cheeseburger/)-
- Flash the LineageOS 17.1 through TWRP.
- Flash latest Magisk (20.4)
- Flash OpenGapps (nano, or pico)
- Reboot

Thank you all !

Hi,

I finally upgraded from LOS official 16.0 to 17.1 following these steps:
- Backup
- Reboot TWRP
- Flash latest available 3.4.0-0 TWRP
- Flash firmware hotfix1
- Flash the LineageOS 17.1
- Flash OpenGapps (nano)
- Reboot & initialize
- Flash latest Magisk (20.4) from TWRP

OS seems to work, i noted few issues so far:
- 4G or WiFi icons display "no internet connection" whereas i obviously have internet access from both (tried to desactivate one then the other to test, and internet is OK). Seems like an icon inversion.
Edit: Fixed by a deactivate/cache clean/re-activate of AFWall+ , which was limiting connections for an unknown reason
- ~~All my camera apps (latest Arnova custom GCam & integrated LOS one) always force closes. I tried to clean cache/data of both apps. No success, still force closes~~
Edit: Cameras force closes have been fixed by installing latest Magisk module "OnePlus 5/5T Front Camera Fix (V5.7)" (https://www.celsoazevedo.com/files/android/google-camera/op5fix/) :highfive:

Hope this helps someone.

And a massive "Thanks" to our volounteers devs working on this release !!

mkhcb · Nov 12, 2020

On the official 17.1 for the 5t w/hotfix 1, I don't receive an incoming calls. Does anyone else have this problem?

Edit: changed the sim card to the other slot and it worked. Please ignore.

rustaman_89 · Nov 12, 2020 at 4:59 AM

mkhcb said:
On the official 17.1 for the 5t w/hotfix 1, I don't receive an incoming calls. Does anyone else have this problem?

Same here. After this.

Johnassel · Nov 12, 2020 at 10:22 AM

Coming from unofficial builds for OnePlus5 my WiFi won't start anymore - it just switches to disabled after a few seconds.
That is what ADB gives me:

Code:

11-12 10:58:22.545  1341 13793 I WifiService: setWifiEnabled package=com.android.settings uid=1000 enable=true
11-12 10:58:22.546  1341  2449 D WifiController: StaEnabledState.enter()
11-12 10:58:22.546  1341  2450 D WifiActiveModeWarden: received a message in WifiDisabledState: { when=0 what=0 target=com.android.internal.util.StateMachine$SmHandler }
11-12 10:58:22.546  1341  2450 D WifiActiveModeWarden: Switching from WifiDisabledState to ClientMode
11-12 10:58:22.546  1341  2450 D WifiActiveModeWarden: Entering ClientModeActiveState
11-12 10:58:22.546  1341  2450 D WifiClientModeManager: entering IdleState
11-12 10:58:22.546  1341  2450 D WifiActiveModeWarden: State changed from client mode. state = 2
11-12 10:58:22.547  1341  2450 I WifiVendorHal: Vendor Hal started successfully
11-12 10:58:22.547  1341  1341 D WifiP2pService: Wifi enabled=false, P2P Interface availability=true
11-12 10:58:22.548  1341  2451 I WifiP2pNative: Registering for interface available listener
11-12 10:58:22.549  1341  2450 I SupplicantStaIfaceHal: Starting supplicant using HIDL
11-12 10:58:22.551  1341  2450 I android_os_HwBinder: HwBinder: Starting thread pool for getting: [email protected]::ISupplicant/default
11-12 10:58:22.552  1341  2450 E SupplicantStaIfaceHal: Death handler already present
11-12 10:58:28.794   840   840 I vendor.rmt_storage: rmt_storage_connect_cb: clnt_h=0x14 conn_h=0x7d1ca05010
11-12 10:58:28.794   840   840 I vendor.rmt_storage: rmt_storage_rw_iovec_cb: /boot/modem_fs1: req_h=0x14 msg_id=3: R/W request received (wr_count 4)
11-12 10:58:28.794   840   840 I vendor.rmt_storage: wakelock acquired: 1, error no: 42
11-12 10:58:28.794   840  1497 I vendor.rmt_storage: rmt_storage_client_thread: /boot/modem_fs1: Unblock worker thread (th_id: 537356590416)
11-12 10:58:28.860   840  1497 I vendor.rmt_storage: rmt_storage_client_thread: /boot/modem_fs1: req_h=0x14 msg_id=3: Bytes written = 2097152, wr_count 4
11-12 10:58:28.860   840  1497 I vendor.rmt_storage: rmt_storage_client_thread: /boot/modem_fs1: req_h=0x14 msg_id=3: Send response: res=0 err=0, wr_count 4
11-12 10:58:28.861   840  1497 I vendor.rmt_storage: rmt_storage_client_thread: /boot/modem_fs1: About to block rmt_storage client thread (th_id: 537356590416) wakelock released: 1, error no: 0
11-12 10:58:28.861   840  1497 I vendor.rmt_storage: 
11-12 10:58:28.861   840   840 I vendor.rmt_storage: rmt_storage_disconnect_cb: clnt_h=0x14 conn_h=0x7d1ca05010
11-12 10:58:32.587   804   804 E WifiHAL : Timed out wating on Driver ready ... 
11-12 10:58:32.587   804   804 E [email protected]: Timed out awaiting driver ready
11-12 10:58:32.588   804   804 E [email protected]: Failed to start legacy HAL: TIMED_OUT
11-12 10:58:32.588  1341  2450 D HalDevMgr: updateRttController: no one is interested in RTT controllers
11-12 10:58:32.589  1341  2450 E HalDevMgr: executeChipReconfiguration: configureChip error: 9 (, timed out)
11-12 10:58:32.589  1341  2450 E WifiVendorHal: Failed to create STA iface
11-12 10:58:32.589  1341  2450 E WifiNative: Failed to create STA iface in vendor HAL
11-12 10:58:32.589  1341  2450 E WifiClientModeManager: Failed to create ClientInterface. Sit in Idle
11-12 10:58:32.589  1341  2450 D WifiActiveModeWarden: State changed from client mode. state = 4
11-12 10:58:32.589  1341  2450 D WifiClientModeManager: expected stop, not triggering callbacks: newState = 1
11-12 10:58:32.590  1341  2450 E WifiNative: Could not get Iface object for interface null
11-12 10:58:32.595  1341  1341 D WifiP2pService: Wifi enabled=false, P2P Interface availability=true
11-12 10:58:32.599  1341  2450 D WifiActiveModeWarden: ClientMode failed, return to WifiDisabledState.
11-12 10:58:32.599  1341  2450 D WifiController: ClientMode unexpected failure: state unknown
11-12 10:58:32.599  1341  2450 D WifiClientModeManager:  currentstate: IdleState
11-12 10:58:32.600  1341  2450 D WifiScanRequestProxy: Sending scan available broadcast: false
11-12 10:58:32.600  1341  2453 I WifiScanningService: wifi driver unloaded
11-12 10:58:32.603  1341  2450 I WifiScanRequestProxy: Scanning is disabled
11-12 10:58:32.615  1341  2450 D WifiActiveModeWarden: Entering WifiDisabledState
11-12 10:58:32.615  1341  2450 D WifiActiveModeWarden: received a message in WifiDisabledState: { when=-15ms what=3 target=com.android.internal.util.StateMachine$SmHandler }
11-12 10:58:32.615  1341  2450 D WifiActiveModeWarden: Switching from WifiDisabledState to WifiDisabled
11-12 10:58:32.615  1341  2450 D WifiActiveModeWarden: Entering WifiDisabledState

It is working on unofficial builds from October so it isn't a hardware failure.
I'm on firmware 10.0.1.

T1mb3 · Nov 12, 2020 at 10:26 AM

Johnassel said:
Coming from unofficial builds for OnePlus5 my WiFi won't start anymore - it just switches to disabled after a few seconds.
That is what ADB gives me:

It is working on unofficial builds from October so it isn't a hardware failure.
I'm on firmware 10.0.1.

What about using the firmware stated in first post? No one has told you to use newer firmware, right?

Johnassel · Nov 12, 2020 at 10:31 AM

T1mb3 said:
What about using the firmware stated in first post? No one has told you to use newer firmware, right?

Had it before latest firmware, same behaviour.

T1mb3 · Nov 12, 2020 at 12:02 PM

Johnassel said:
Had it before latest firmware, same behaviour.

Then you need to uninstall your mods or clean flash.
Wifi works for me.

Did you follow flashing instructions?

maxammann · Feb 28, 2016 2 0 0

Mobile data is not working

Unfortunately Mobile data is not working for me on cheeseburger. I wiped my device completely. Then I flashed OxygenOS 10.0.1 and then the official build.

The following data can be found in the log:

Code:

11-12 17:14:01.439  2926  2926 I QImsService: ImsSenderRxr : [0073]> REQUEST_SET_SERVICE_STATUS [SUB0]
11-12 17:14:01.439  2926  2926 I QImsService: ImsSenderRxr : REQUEST_SET_SERVICE_STATUS to ImsRadio: token -73 SrvType:0 Network:14 enabled:2 RestrictCause:0
11-12 17:14:01.439  2926  2926 W QImsService: ImsSenderRxr : mImsRadio V1.6 is null. invoking mImsRadio.setServiceStatus()
11-12 17:14:01.439  2926  2926 I QImsService: ImsConfigImpl : SetServiceStatus = 3 13 2
11-12 17:14:01.440  2926  2926 I QImsService: ImsSenderRxr : [0074]> REQUEST_SET_SERVICE_STATUS [SUB0]
11-12 17:14:01.440  2926  2926 I QImsService: ImsSenderRxr : REQUEST_SET_SERVICE_STATUS to ImsRadio: token -74 SrvType:3 Network:14 enabled:2 RestrictCause:0
11-12 17:14:01.440  2926  2926 W QImsService: ImsSenderRxr : mImsRadio V1.6 is null. invoking mImsRadio.setServiceStatus()
11-12 17:14:01.440  2926  2926 I QImsService: ImsConfigImpl : SetServiceStatus = 25 13 2
11-12 17:14:01.440  2926  2926 I QImsService: ImsSenderRxr : [0075]> REQUEST_SET_SERVICE_STATUS [SUB0]
11-12 17:14:01.440  2926  2926 I QImsService: ImsSenderRxr : REQUEST_SET_SERVICE_STATUS to ImsRadio: token -75 SrvType:25 Network:14 enabled:2 RestrictCause:0
11-12 17:14:01.440  2926  2926 W QImsService: ImsSenderRxr : mImsRadio V1.6 is null. invoking mImsRadio.setServiceStatus()
11-12 17:14:01.441  2926  2926 I QImsService: ImsConfigImpl : SetServiceStatus = 0 18 0
11-12 17:14:01.441  2926  2926 I QImsService: ImsSenderRxr : [0076]> REQUEST_SET_SERVICE_STATUS [SUB0]
11-12 17:14:01.441  2926  2926 I QImsService: ImsSenderRxr : REQUEST_SET_SERVICE_STATUS to ImsRadio: token -76 SrvType:0 Network:19 enabled:0 RestrictCause:0
11-12 17:14:01.441  2926  2926 W QImsService: ImsSenderRxr : mImsRadio V1.6 is null. invoking mImsRadio.setServiceStatus()
11-12 17:14:01.442  2926  3031 I QImsService: ImsRadioResponse : SetServiceStatus response received.
11-12 17:14:01.442  2926  3031 I QImsService: IFRequest : [0073]< REQUEST_SET_SERVICE_STATUS error: 2
11-12 17:14:01.442  2926  3105 I QImsService: ImsConfigImplHandler : Message received: what = 2
11-12 17:14:01.442  2926  2926 I QImsService: ImsService : enableIms :: slotId=0
11-12 17:14:01.442  2926  3031 I QImsService: ImsRadioResponse : SetServiceStatus response received.
11-12 17:14:01.442  2926  3031 I QImsService: IFRequest : [0074]< REQUEST_SET_SERVICE_STATUS error: 2
11-12 17:14:01.443  2926  2926 I QImsService: ImsSenderRxr : [0077]> REQUEST_IMS_REG_STATE_CHANGE [SUB0]
11-12 17:14:01.443  2926  3105 I QImsService: ImsConfigImplHandler : Message received: what = 2
11-12 17:14:01.443  2926  2926 I QImsService: ImsSenderRxr : REQUEST_IMS_REG_STATE_CHANGE request to ImsRadio - token:77 RegState1
11-12 17:14:01.443  2926  2926 D MultiSimSettingController: onUserDataEnabled
11-12 17:14:01.443  2926  2926 D MultiSimSettingController: setUserDataEnabledForGroup subId 1 enable true
11-12 17:14:01.444  2926  3031 I QImsService: ImsRadioResponse : SetServiceStatus response received.
11-12 17:14:01.444  2926  3031 I QImsService: IFRequest : [0075]< REQUEST_SET_SERVICE_STATUS error: 2
11-12 17:14:01.444  2926  3105 I QImsService: ImsConfigImplHandler : Message received: what = 2
11-12 17:14:01.445  2926  3031 I QImsService: ImsRadioResponse : SetServiceStatus response received.
11-12 17:14:01.445  2926  3031 I QImsService: IFRequest : [0076]< REQUEST_SET_SERVICE_STATUS error: 2
11-12 17:14:01.445  2926  3105 I QImsService: ImsConfigImplHandler : Message received: what = 2
11-12 17:14:01.445  2926  3031 I QImsService: ImsRadioResponse : Got registration change response from ImsRadio.
11-12 17:14:01.446  2926  3031 I QImsService: IFRequest : [0077]< REQUEST_IMS_REG_STATE_CHANGE error: 2
11-12 17:14:01.458  2926  2926 I QImsService: ImsServiceSubHandler : Message received: what = 9
11-12 17:14:01.458  2926  2926 I QImsService: ImsServiceSub : [0] Request turn on/off IMS failed

The device actually shows me "Mobile data 4G" when I pull down the status bar. But there is no connection

Spidersoft · May 19, 2009 43 7 28

maxammann said:
The device actually shows me "Mobile data 4G" when I pull down the status bar. But there is no connection

I had the same problem. Try to configure your APN settings manually. This worked for me.

quinne8d · Feb 17, 2012 21 1 0

Any idea how to fix Google Pay? I cant add my credit cards

maxammann · Feb 28, 2016 2 0 0

quinne8d said:
Any idea how to fix Google Pay? I cant add my credit cards

Thank you, that worked!

[ROM][10.0][OFFICIAL] LineageOS 17.1

Member

Member

Member

Member

Member

New member

Senior Member

Senior Member

Member

Member

Senior Member

New member

Senior Member

Senior Member

Senior Member

Senior Member

New member

Member

Member

New member