[ROM][OFFICIAL][enchilada][11] LineageOS 18.1

[Spaceoid]

How long does it take for your phone to connect to your home wifi after you get home? For me, it sometimes takes a minute and I wonder why. Is that to be expected? (No big problem though, obviously. Just curious.)

 

[antonyjr]

How long does it take for your phone to connect to your home wifi after you get home? For me, it sometimes takes a minute and I wonder why. Is that to be expected? (No big problem though, obviously. Just curious.)

For me in stock rom, the IMEI and baseband would magically disappear and re-appear again after some time or never appear and crash and reboot. With Lineage OS I only seen this very very rarely or never. I think this might be hardware issue. But using Lineage OS for like 3-4 days now, I have seen this issue occur very rarely in my phone(But it did occur to me twice in 3 days, but reboot would fix it or it would repair itself after seconds. But no crashes ever in LineageOS). So for you if in your stock everything works great but you only encounter this in Lineage OS then you can just use Stock or try to fix it or just use LineageOS with these little quirks.

Maybe oneplus screwed up some firmware. We will never know until they release the source which will never happen xD.

 

[mcboums]

sometimes screen flickering is this firmware issue?

 

[antonyjr]

sometimes screen flickering is this firmware issue?

I really don't know, It could be hardware issue. These phones are notorious for that. or Maybe Oneplus is deliberately doing something to throttle something like Apple to make use buy new phones. Because IMO OP6 is really good in terms of performance. Why drop support for software when these phones are good in terms of performance.

Have you tried to connect a new display(yes you need to open up your phone to do that) and check if the flickering exists even in the new display? If it exists then the problem might be firmware/os or the motherboard itself. Because things like these which occurs randomly are very very hard to debug.

But I'm no expert in electronics or circuits.

I will stop here since the discussion is going off-topic and I'm really stupid with respect to electronics, so all I said is just my 2 cents not to be taken as verdict. Thanks.

 

[antonyjr]

But I have been using LineageOS nightly 220104 build and it works very good. Never going back to stock. No issues with IMEI or baseband anymore. Wifi and Data working flawless. But sometimes I can see the network just disappear but it will reappear in less than 10 seconds (This occurs very rarely though, I can't pinpoint the issue yet, it might be a corrupt EFS partition which I have backup so let me see, only time will tell).

But when I use internet constantly there is no interruption, in Stock I used to reboot randomly and interrupted network connection with both Wifi and data. The oneplus forums is suggesting it is a hardware issue. But how does LineageOS works flawlessly if it's hardware issue? I have no clue. Maybe it is caused by overheat and LOS seems to keep my phone cool all the time unlike the Stock.

 

[Udaya.kr]

Same here. With 220111 stuck in boot animation. Went back to 220104, this work well for me

I flashed 220111 via updater working fine

 

[antonyjr]

I flashed 220111 via updater working fine

Yeah. If you update with the official updater it does not break. This only happens if you freshly flash lineage os from stock.

 

[Spaceoid]

Can someone else confirm that his phone takes 10-20 seconds to connect to wifi?
My old Sony took like 3 secs. According to OP forums, this might be an OOS 'issue' (if you want to call it like that), though.

 

[gamertag128]

Can someone else confirm that his phone takes 10-20 seconds to connect to wifi?
My old Sony took like 3 secs. According to OP forums, this might be an OOS 'issue' (if you want to call it like that), though.

If I toggle it off and on again, it takes about 3 seconds on my device.

 

[Spaceoid]

I reset my wifi and bluetooth settings (via the settings) and also rebooted my router. Now the connection is made every time in 3 secs, too. So it was either a settings or router issue. Sorry for the confusion.

Edit: After 20 mins, connecting to wifi now takes 20 secs again.

 

[madman]

I reset my wifi and bluetooth settings (via the settings) and also rebooted my router. Now the connection is made every time in 3 secs, too. So it was either a settings or router issue. Sorry for the confusion.

Edit: After 20 mins, connecting to wifi now takes 20 secs again.

20 secs seem reasonably fast to me but if you really need it as fast as you can maybe try toggling this setting in developer options.
"WiFi Scan Throttling".

As the name suggests, android generally throttles how fast it should scan for networks to save power but I guess you can make that tradeoff?

 

[Spaceoid]

20 secs seem reasonably fast to me but if you really need it as fast as you can maybe try toggling this setting in developer options.
"WiFi Scan Throttling".

As the name suggests, android generally throttles how fast it should scan for networks to save power but I guess you can make that tradeoff?

Ty for that input! I already tried that option, no change.
And no, I do not 'need' it that fast... The backstory is, at work we operate at 5 GHz, too, and recently my phone lay very close to a 5 GHz antenna with very high output. So now I am wondering if the wifi delay is a software issue or a hardware fault caused at work.

Edit: "Slow" wifi connection (up to 20 sec) only happens with 5 GHz, 2,4 GHz seem to go faster. Might be a remnant of previous 5 GHz problems in OOS...?

 

[Not_perfect]

"Slow" wifi connection (up to 20 sec) only happens with 5 GHz, 2,4 GHz seem to go faster.

Same here. I haven't figured it out why yet.

 

[Bart-NL]

I was in the same situation and used this tutorial with the 20220104 build, because some people had problems with the 20220111 build (updated on it afterwards with no issues). Instead of the microG builds, I downloaded the it directly from the LineageOS website If you want to use it as an instruction, I would recommend to watch it first and then go thru step by step, because he made some mistakes, which he corrects afterwards. As for the GApps I used "MindtheGApps" as recommend.

Thanks... I'll try it with a regular ROM since I don't mind some Google stuff..

Currently I'm still messing around with drivers while in Fastboot mode.. Can't get them installed...

 

[mcboums]

delete

 

[gamertag128]

Thanks... I'll try it with a regular ROM since I don't mind some Google stuff..

Currently I'm still messing around with drivers while in Fastboot mode.. Can't get them installed...

It can be a bit of a struggle to get it done, but as of now, I can say it was fully worth it. It took me about a day to get adapted and I'm just happy to be able to receive further updates

 

[antonyjr]

I'm getting qualcom crash dump frequently and randomly. But reboot just fixes it. What is happening? is it software issue or hardware?

I'm going to get a logcat to see if I could pinpoint the moment it crashes.

Using Lineage OS (Built from source and self-signed), the bootloader is re-locked with lineage os and working fine. OnePlus 6 Enchilada. I think I had no crashes with official lineage os build 220104 with the bootloader unlocked.

 

[Spaceoid]

Same here. I haven't figured it out why yet.

Just to gather some data (and because I have some free time right now) I chose to sweep to the 5 GHz channels manually in my router settings and take the time it takes to connect the phone to wifi.
Interestingly, lower channels (e.g. 36 and 40) get connected near-instantly (takes like 3 seconds), while higher channels (e.g. 60 or 116) take up to 10-15 seconds.
At this point I am not sure anymore if this is something like a small bug or just normal behaviour, as it is so constant and reproducable. Also, ofc. I can totally live with that behaviour.

Edit: Still, my old Sony connects to all possible channels within 2-3 seconds, so there is a difference.

 

[gamertag128]

I'm getting qualcom crash dump frequently and randomly. But reboot just fixes it. What is happening? is it software issue or hardware?

I'm going to get a logcat to see if I could pinpoint the moment it crashes.

Using Lineage OS (Built from source and self-signed), the bootloader is re-locked with lineage os and working fine. OnePlus 6 Enchilada. I think I had no crashes with official lineage os build 220104 with the bootloader unlocked.

Build 220118 here. Unlocked bootloader, no issues.

 

[Bart-NL]

It can be a bit of a struggle to get it done, but as of now, I can say it was fully worth it. It took me about a day to get adapted and I'm just happy to be able to receive further updates

You don't have the correct driver (as inf file) laying around? ;-)