yashsingh1/xdaforums huggingface dataset:
[OnePlus 5 & 5T Cross Device Development] xyrnox:
Hey, thanks for the ROM, it's working great, I just have 2 issues.

1080p 60 FPS recording isn't available with the apps I tried. What is the technical reason for this? Can we help debugging this somehow?

Every few days randomly when I try to unlock my phone it doesn't do anything. The screen stays black and nothing happens. I need to power it off and on by pressing the power button for a really long time. After that it boots and works normally.
[OnePlus 5 & 5T Cross Device Development] pleomaxell:
I faced the exact same problem but only once. After the last update it didn't happen again.
[OnePlus 5 & 5T Cross Device Development] pleomaxell:
What issue are you talking about? Can you be a bit more specific?
[OnePlus 5 & 5T Cross Device Development] zohar_ml:
Is there an option to install the OOS camera? I searched for this but could not find.

With the Nikita GCAM I found xml files that give me the icon for 1x & 2x but both give me the same zoom. is there an xml that give the zoom camera?
[OnePlus 5 & 5T Cross Device Development] Eric_Lev:
Yes, it's a kernel-side issue and flashing Lazy kernel (Lazy-custom-dev-vX.18.zip) fixes this problem, pending a future fix (?).
[OnePlus 5 & 5T Cross Device Development] pleomaxell:
Does Lazy Kernel (Lazy-custom-dev-vX.18.zip) work with the latest update of Lineage OS?
[OnePlus 5 & 5T Cross Device Development] Eric_Lev:
Yes.
[OnePlus 5 & 5T Cross Device Development] gsser:
been a while since i have used an official los, got a question about the performance slider. is it working like this in this post? https://xdaforums.com/t/battery-sav...explanation-of-profiles.3730602/post-77234396 if so what are the clocks based on each profile? @T1mb3
[OnePlus 5 & 5T Cross Device Development] js-xda:
Decided today to dare dirty flash over the last official LineageOS 16.0 build:

upgrade to twrp-3.4.0-0-cheeseburger_dumpling.img

full NANDroid backup

flash firmware_10.0.1_cheeseburger.zip

flash lineage-17.1-20201221-nightly-cheeseburger-signed.zip

flash open_gapps-arm64-10.0-pico-20201223.zip

wipe cache/Dalvik

reboot

Everything working fine so far! Not sure whether I observe some seldom cases of not responding to touch as previously mentioned in this thread but might be also my dry skin.

Thank you, @T1mb3!
[OnePlus 5 & 5T Cross Device Development] :
Damn, and i thought i was imagining it. I've had some touch screen issues since upgrading to 18, but since there's really no way to verify or reproduce it reliably, i too thought it might be just dry skin. I might miss a tap every now and then, nothing too serious but it seems like it is an issue after all.
[OnePlus 5 & 5T Cross Device Development] pleomaxell:
I am also having these touch misses. Today I tried to pull down to Expand Notification and it took the OS a couple of times to realize that I was touching the screen.
[OnePlus 5 & 5T Cross Device Development] Hui531:
Do anyone have problem with Android Auto I installed and it show an error of "Android Auto requires one or more Google Play services that are not currently available. Please contact the developer for assistance."

I've install nano Gapps package with map, play music and text to speech service installed
[OnePlus 5 & 5T Cross Device Development] js-xda:
Well, ran today into some issue: Out of the blue, no reaction to any touch. Only power button worked (didn't check volume but could open shutdown/reboot dialog and start my camera via double-tapping the power button) and I had to force shutdown. The issue is gone for now.
[OnePlus 5 & 5T Cross Device Development] whatnoww:
Where the left and right channels will eventually get unbalanced volume output after pausing ocasionally when using the headphone jack.
[OnePlus 5 & 5T Cross Device Development] giddie:
Not quite so lucky for me: it seems there's an issue with GApps "stock". Using "pico", like you, the upgrade seemed to work OK. However, with "stock", boot gets stuck on the OnePlus splash screen, and never reaches the LineageOS loading animation. GApps does indicate that there are some outstanding issues with 10.0. I tried wiping /data, which didn't help. So long as I use "pico" or raw LineageOS, it seems the new system is able to decrypt the existing data OK.
[OnePlus 5 & 5T Cross Device Development] js-xda:
Have you updated also TWRP (recently also 3.5.0 was published)? There have been lately quite some issues related to decryption and TWRP. But not sure whether it helps in your case as it seems to be an issue during startup of the system.
[OnePlus 5 & 5T Cross Device Development] giddie:
I'm using TWRP 3.4.0. I'll try the new version but, as you say, it's probably not related: TWRP decrypts just fine, and in fact it saved the day with its backup/restore feature. I *did* initially think the issue was caused by me not removing my lock pattern before upgrade, but the pattern worked fine without GApps (and with pico).
[OnePlus 5 & 5T Cross Device Development] TufTurf:
Installed latest official build in op5t and noticed that magisk safetynet is throwing 'attestation failed'

Before updating lineage, I had already upgraded magisk to 21.2 and running it for last 2 weeks without issues.

Any help here pls ?
[OnePlus 5 & 5T Cross Device Development] LuisCarlosHK:
install the magiskhide pros config module then update the fingerprint
[OnePlus 5 & 5T Cross Device Development] djrion:
Gonna try and make this TL;DR

I don't use root. I don't use custom kernel.

1. Ran 16 official forever (through the no update period to the monthly sec patches when they came back)

2. upgraded via dirty flash to 17 for about 4 hrs (TWRP) Aug 2020 maybe?

3. Dirty flashed 18 over the top and then 18.1 (all twrp). I've used almost every build through Dec of 2020.

4. Everything was great, until a few days ago when I was playing Apex and decided to flash the January 2021 update. Mid game on a 5 or6 kill streak, I realized i dirty flashed 17.1.

5. I never changed recoveries...

6. Suddenly i was on LOS recovery.

7. Tried to dirty 18.1, tried to dirty 17.1, and only 17.1 would load.

8. knowing i should have clean flashed a few years ago, I wiped everything in LOS recovery and tried to clean install 18.1 --- all it did was hang on 3 moving lineage pieces.

9. flashed TWRP in bootloader

10. factory reset / adb sideload / flashed 18.1 / gapps 11 / wipe cache - still stuck on 3 moving lineage bootup things

11. factory reset / adb sideload /flashed 17.1 / gapps 10 / wipe cache - still stuck same place

12. flashed LOS recover in bootloader

13. factory reset / adb sideload / flash 17.1 / gapps 10 / wipe cache - works like a charm.

Couple questions

1. I'm willing to give LOS recovery a shot, even though I don't like it asthetically and it is UBER limited without a pc/mac in hand. But I've been told I can flash 18.1 with LOS Recovery - so why am I hanging?

2. If it can't be done, what do I need to do to get 18.1 back on my phone using TWRP (even though it failed above)

*even tho LOS has built in firmware now, I still made sure on a couple of separate instance (not above) to try and flash most recent firmware to see if that was hanging for some reason. it wasn't and i was on most recent firmware anyway.

**if this needs to go to 18 forum, that is fine, I will move it. but i never had any problems till I accidentally came here (my own fault).

thanks in adv!!!
[OnePlus 5 & 5T Cross Device Development] diziet_sma:
What is the hotfix I've read about for? I just received my brother-in-laws old phone, and flashed it to the latest cheesburger 17.1 lineageos. It works fine, except occasionally I could swear it doesn't register my touches.

The lineageos website said nothing about a firmware update, should I worry about this? Is there a way to check on the ophone for the firmware version?

diziet
[OnePlus 5 & 5T Cross Device Development] :
No need to worry about firmware. During install, your fw version is checked and if it's outdated, it'll be automatically updated with message Upgrading firmware to 10.0.1 or Firmware is up-to-date if it is at required version.

Note that this only applies to LineageOS that is official or built by me (including 18.1 unofficial).
[OnePlus 5 & 5T Cross Device Development] :
I've had the same issue when it comes to the touches. In my case flashing a Lazy kernel solved it for me.
[OnePlus 5 & 5T Cross Device Development] Jaffel:
I need help please. I'm experiencing the same touch issues on my OP5T running LOS 17.1 and TWRP 3.5.0, and I have never flashed a custom kernel before.

Do I just flash Lazy Kernel through the recovery? Any special steps to follow?

And should I flash vX.17 or vX.18?

Thanks
[OnePlus 5 & 5T Cross Device Development] lethallunatic:
Did anyone get Nightly Lineage to work with nanodroid/microg ?

I would really like to stick with the Lineage Nightly updates.

Yes,

Always nandroid before anything to be sure you're safe and are able to roll back to your ROMs state safely.

TWRP 3.5 is buggy, better use 3.4 or Orange Fox recovery which has proper treble support.

Just download both versions and see which one works. You can flash one above the other. Unsure which version you need though.
[OnePlus 5 & 5T Cross Device Development] Jaffel:
I flashed version 18 and the phone is running very smooth now. Thanks!
[OnePlus 5 & 5T Cross Device Development] lethallunatic:
This is off topic as it is unrelated to this ROM development,

However, after checking version numbers and history, x18 is really old. better check their telegram group for current version, it is somewhere around 265 as of this post
[OnePlus 5 & 5T Cross Device Development] NazuNalika:
So I'm coming back to revisit this. I have yet to get around this issue. Is anyone else running into this issue or does anyone know of a way to fix this? I decided to clean flash, format everything and just start clean and I'm still having this issue.
[OnePlus 5 & 5T Cross Device Development] :
Since the past few nightlies the fingerprint sensor becomes unresponsive 3-4 times a day, seemingly at random. The phone also hangs fairly often, requiring forced power off to snap out of it. The screen might turn on, it might even prompt for the PIN code but after inputting it the home screen doesn't show up and there's nothing to do except force power off.

We have two identical 5T's and both are experiencing the hangups. The fingerprint sensor bug may also be present on both but i'm the only one who uses it so... I kind of wish i had stayed with 16 since it was rock solid stable, but obviously there were no more updates coming for it. :(
[OnePlus 5 & 5T Cross Device Development] :
Hi,

What Gapps are you using? Any other mods?

I haven't heard about such issues, maybe there's something wrong with your setup.
[OnePlus 5 & 5T Cross Device Development] :
No Gapps or mods. Just stock Lineage. I'll probably wipe my phone soon, and see if these issues persist. I believe they will, since our other 5T experiences the hangups too.
[OnePlus 5 & 5T Cross Device Development] mohamad ali raad:
@T1mb3 in latest 17.1 phone is'not showing saved pictures in gallery
[OnePlus 5 & 5T Cross Device Development] :
Next update fixes VoWIFI, thanks for all who helped fixing it(y)
[OnePlus 5 & 5T Cross Device Development] IXI Mo IXI:
I installed todays update (lineage-17.1-20210125-nightly-cheeseburger-signed.zip) via the updater app.

The installation process ended successfully and the device rebooted.

It stayed longer than normal at the LineageOS boot animation and then it rebooted into the TWRP recovery.

Can someone help me troubleshooting the issue?

I have the recovery.log and the dmseg.log files.

Best regards

Mo

Edit:

Device: Oneplus 5

TWRP: twrp-3.3.1-20190908-0-codeworkx-signed-forcedecrypt-cheeseburger.img

Magisk: Magisk v21.4

Edit 2:

Solution steps:

- boot TWRP

- flash Lineage

- flash GAPPS

- reboot and enjoy
[OnePlus 5 & 5T Cross Device Development] :
I need the log from bootanimation to help.
[OnePlus 5 & 5T Cross Device Development] :
Next weeks update fixes offline charging(y)
[OnePlus 5 & 5T Cross Device Development] js-xda:
Bit of a wild guess: Are you using GAPPS? If yes, flash new ones right after flashing the latest build and it might work. Saw this being reported as an issue and workaround for some other devices with recent builds. Haven't tried the build that you mentioned so far.
[OnePlus 5 & 5T Cross Device Development] IXI Mo IXI:
Yes, i am using GAPPS.

I am going to backup my internal SD Card first (via TWRP) and then i am trying to update the GAPPS.

EDIT:

You were right! It had something to do with the Gapps. Thanks a lot!

Solution steps:

- boot TWRP

- flash Lineage

- flash GAPPS

- reboot and enjoy

I still have some force closes in Google Apps but that should be fixable.
[OnePlus 5 & 5T Cross Device Development] Besuz:
Hi,

updated my dumpling to 20210126 via ota today, now mobile data is not working anymore on both sim cards. No error, the "4G" icon is just missing and the phone is offline. Calling is working fine, wifi too. Reboot, airplane mode and changing the data connection in sim settings does not help.

German carrier Telekom on both sim cards, phone is rooted via magisk.

Anyone have a clue what to do/test?

Thx!
[OnePlus 5 & 5T Cross Device Development] Pikoon:
Same for me, I had to downgrade back to previous 20210119 to get the mobile data back again. Also i noticed that I was able to get turn on mobile data on both Sim cards at the same time.

Sadly, I totally forgot to take a log before revert back to the previous update.

Anyway, thank you very much for keeping this device alive and maintening this amazing ROM !
[OnePlus 5 & 5T Cross Device Development] Besuz:
Hi,

I have it still installed. Currently sitting at home every day the whole day :( so not really a problem for me.

@T1mb3 If you want to dig into this and need logfiles, just let me know what you need.

Thx!
[OnePlus 5 & 5T Cross Device Development] :
Have you tried searching "sim cards" in settings and enabling there? An update caused it to disappear from the menu but it's still available in search.

Next update adds it back, you can manually get it by going to Developer options -> feature flags and enabling enable mobile network settings v2.

New menu will be in Network & internet -section.
[OnePlus 5 & 5T Cross Device Development] :
If you didn't wipe data there, that's going to cause problems for all Gapps.
[OnePlus 5 & 5T Cross Device Development] Besuz:
Works, thx!
[OnePlus 5 & 5T Cross Device Development] pleomaxell:
I am facing the same problem. After the January 25th update mobile data isn't turning on. I too can enable mobile data on both SIMs and still it doesn't turn ON. Toggling Airplane mode also didn't work.

Searching for "SIM Cards" and enabling mobile data from the option fixed this issue for me. Thanks @T1mb3 for the solution.
[OnePlus 5 & 5T Cross Device Development] js-xda:
Wondering on the statement of @T1mb3 in this specific context (assuming updating same 17.1 ROM and GAPSS package from what @IXI Mo IXI writes): To the best of my knowledge and experience, it is not needed to wipe data if flashing newer build of same Android ROM and newer build of same GAPPS package. Doing this since several years on an Nexus 7 using Android 7.1.2. Happy to learn differently for other settings.

On the force closes: Before wiping data completely and if it is possible to narrow down to a few specific apps, I suggest to remove the data of the specific app as workaround to avoid clean flashing. Yes, only a workaround and only for those who accept that underlying issues may remain. But it saved me from reinstalling a OnePlus 2 to wipe the data of two apps when upgrading from 16.0 to 17.1 instead of wiping everything as I had forgotten to backup before. (OK, pretty stupid fail on my behalf but nevertheless ...)
[OnePlus 5 & 5T Cross Device Development] IXI Mo IXI:
I didn't wipe any data and that's propably the reason for the FCs in some of the Google Apps.

I have already done what you are proposing now. I only cleared the data or reinstalled the Google Apps with issues.

So there wasn't any data loss since the last update and no need to wipe the whole system and reinstall everything from the beginning.
[OnePlus 5 & 5T Cross Device Development] razzor1984:
I'm also facing the "Mobile Data" isn't working after the January 26th update.

Latest room which works were jan19th - I dirtyflashed back and now my Mobile works again. Must be a bug in the ROM.

I don't have any kind of gaps on my device - not any kind of google stuff - the rest in Blocked via custom Afwall scripts ;)

best regards

Razzor
[OnePlus 5 & 5T Cross Device Development] Thimoteo:
I did a clean install of Lineage 17 about a month ago, and like it a lot ... but also have one OS freeze problem that I haven't read about in this forum, experienced on several builds.

Between a couple of times a week and once a day, my 5T screen will go black, the 'battery recharge' light next to the front camera lens will come on (always blue), and the phone becomes so unresponsive that I have to press and hold in the power button for a looooong time to get it to reboot. When I do reboot, all is well again.

Has anyone else seen anything similar? Any ideas on a fix?
[OnePlus 5 & 5T Cross Device Development] LuisCarlosHK:
I got the same problem
[OnePlus 5 & 5T Cross Device Development] Scream275:
I got Teufel Airy headphones, which support the aptx codec. On latest OOS my 5T used the aptx codec (saw the aptx toast), but on the latest LOS 17.1 official, there is no option for aptX/HD inside the bluetooth menu. Developer options show me that sbc is auto selected. Is there some issue with aptx and/or is there some trick to activate it? If I select aptx under developer options, it is auto reverted if I leave developer options and open the menu again.

EDIT: I'm, using gcam and thus the dot fix magisk modul, in case that's relevant
[OnePlus 5 & 5T Cross Device Development] diziet_sma:
Thanks for the replies about firmware. I have a query now about sms messages being read over bluetooth.

Once upon a time with lineageos 14.1 on my old moto thingy I could get sms messages read out using text to speech during music playback over bluetooth, if I installed an app called a2dp volume from f-droid.org.

This no longer works. I have picogapps installed which seems to give the google text to speech which is enabled and the test 'play' works.

Is there a way to do this with 17.1? I have a dual sim oneplus5 with 64gb (are they all dual sim? this was my b-in-law's).

diziet
[OnePlus 5 & 5T Cross Device Development] :
Hi,

After such crash, there should be log files in /sys/fs/pstore/. Please send contents of this directory once it occurs along with small details on what you were doing at the time.

The logs exist there only right after a reboot (either in twrp or Android), and you need root access to get them.

How to:

Enable adb root in developer options.

Open shell, "adb root", "adb pull /sys/fs/pstore".

You can PM me the files.
[OnePlus 5 & 5T Cross Device Development] LuisCarlosHK:
I can't find any file in /sys/fs/pstore/ after crash.
[OnePlus 5 & 5T Cross Device Development] pi_dev:
I got the same problem. Still after 20210202 update.

If I search "sim cards" I see nothing because I use a different language. But I enabled mobile data for my sim card. I also reseted APNs and network settings. Mobile network settings v2 is enabled in developer menu.

Can you please show me the way to the magic setting? :)
[OnePlus 5 & 5T Cross Device Development] Jaffel:
Same problem for me on the latest build. My data Sim is in tray 2 but I cannot find that magic menu to enable data.
[OnePlus 5 & 5T Cross Device Development] Jaffel:
Just found a way around the issue that worked for me. Eject the Sim tray and insert it again. That magic menu option will appear in the notifications. Mobile data active again!
[OnePlus 5 & 5T Cross Device Development] pi_dev:
If I do that I get a new option highlighted at the top of settings. Telling me mobile internet is not working. But the activate button does nothing for me.

If I remove the second sim card it works fine without changes. Maybe that's because the second card does not provide internet at the moment because it is not paired for?
[OnePlus 5 & 5T Cross Device Development] debby_:
Have 2 sim card active. Did not work after update. Eject tray and work without changes.

#####

THX Jaffel

--> after restart it works properly.
[OnePlus 5 & 5T Cross Device Development] curiousrom:
@T1mb3 - Could you please add the models to your thread's title so they are included in links?

Something like [ROM][10.0][OFFICIAL] LineageOS 17.1 for OnePlus 5 & 5T maybe?

@ the present when inserting a link to page #1 with the XDA BB Code enabled, this is how it looks & it's similar with Reddit's Fancy Pants Editor:

https://xdaforums.com/t/rom-10-0-official-lineageos-17-1.4169147/

Compare to for example:

https://xdaforums.com/t/official-lineageos-17-1-for-galaxy-s5-klte-variants.4181821/
[OnePlus 5 & 5T Cross Device Development] :
Sure.
[OnePlus 5 & 5T Cross Device Development] DaniRainbow:
Hello,

I did the OTA update for lineage-17.1-20210202 and my phone would not boot up after doing so. I ended up having to wipe the cache and transfer lineage-17.1-20210126 to my phone via USB in order to get it to boot. Thank god I didn't lose my photos, but I am going to have to redo all my apps and customizations. Has anyone else had this issue with the latest update?
[OnePlus 5 & 5T Cross Device Development] debby_:
Reflash gapps?
[OnePlus 5 & 5T Cross Device Development] Marsbar:
Changing "Vibration and haptic strength" setting between "Low", "Medium" and "High" appears to make no difference on my OP5.

Is there a setting I'm missing? Does it work for everyone else?
[OnePlus 5 & 5T Cross Device Development] DaniRainbow:
I did reflash Gapps when I was able to boot successfully, but did not flash Gapps as part of the OTA update. Is that something that needs to be done each time? I lost all apps, not just Google apps.
[OnePlus 5 & 5T Cross Device Development] Thimoteo:
Thanks for the reply, T1mb3. I'll send the files after the next crash.
[OnePlus 5 & 5T Cross Device Development] js-xda:
No, not needed for OTA updates. But there have been lately several cases where reflashing GAPPS resolved being stuck during the boot process. If you boot to recovery and flash both the ROM update and a matching recent GAPPS package without booting to system, you shouldn't have issues with the app lose (doing so on monthly basis on a Necus 7). Deviating from this is nevertheless never a good idea. Also flashing GAPPS on a system having run without them before is not a good idea.
[OnePlus 5 & 5T Cross Device Development] DaniRainbow:
Thanks! I'll be sure to do this from now on.
[OnePlus 5 & 5T Cross Device Development] zumi001:
I experienced the same issue today on the lineage-17.1-20210201-nightly-cheeseburger version, locked up phone with the notification led being cyan, and the phone not waking up with the power button. the /sys/fs/pstore was empty a few hours after the incident (but without rebooting). I had to power cycle it with the power button. Is it cleaned on a timer or what do you mean by "right after a reboot"?

I did nothing specific before the lockup, the phone was just idle for ~1h, during which I went away from my home wifi network and probably switched to 4G, and it didn't wake up when I tried to use it.
[OnePlus 5 & 5T Cross Device Development] denisovich:
I've managed somehow to use dumpling lineageOS 17.1 for a while now, without any bootloops or any other issues for some time now, including OTA updates. This ROM is very nice, and very stable.

Am I doing something wrong?

Because I feel a bit left out judging by some of the posts here.