yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
If you look at https://wiki.postmarketos.org/wiki/Devices you'll see oneplus3 is listed as booting device as well as non-booting device. If you look at the devices page (https://wiki.postmarketos.org/wiki/OnePlus_3T_(oneplus-oneplus3t) ) and follow the installation link, you are directed to the sources (https://gitlab.com/DrGitX/linux-postmarketos-qcom-msm8996/-/commits/master ) - there's no installation/flashing instructions. If you look at https://gitlab.com/DrGitX/linux-postmarketos-qcom-msm8996/-/blob/master/Makefile you'll see it's 5.6-rc5. 5.6 is eol and the kernel sources aren't updated since then (IMHO basing a rom on eol kernels is a bad idea).

Since postmarketos is linux and not android, all android specific modifications are missing (in deed I highly doubt these sources are building at all inline los).

Considering all these and also having in mind the failed attempts to port the op3/t android supporting kernel to 4.x over the last 2 years, I think keeping up with the current 3.18 development is much more promising then trying to make the postmarketos kernel working with android.

(OT, but I see the questions popping up: current 3.18 development: https://lwn.net/Articles/788689/ ; https://android.googlesource.com/kernel/common/+log/refs/heads/android-3.18 )
[OnePlus 3 & 3T Cross Device Development] husam3235:
Thanks for your time,i found this link

https://gitlab.com/msm8996-mainline

This is the PostmarketOS 820 mainline kernel 5. 8 is in wip,

https://pkgs.postmarketos.org/package/master/postmarketos/aarch64/linux-postmarketos-qcom-msm8996

PKG is 5.7.

And I heard 5.9 just need one patch to boot android.

Maybe just need device tree files to boot AOSP on mainline kernel

---------- Post added at 02:26 PM ---------- Previous post was at 01:57 PM ----------

Miracast is lagging when screen resolution is better than 720p ,we need a setting to modify resolution*:cool:
[OnePlus 3 & 3T Cross Device Development] :
Device tree is here: https://github.com/LineageOS/android_device_oneplus_oneplus3 Good luck!

Looking forward to your review.

BTW. I'd recommend using a lts release insted of "mainline", since "mainline" is always release canditate (it's moved to "stable" as soon as release quality is reached). Latest lts is 5.4.
[OnePlus 3 & 3T Cross Device Development] knpk13:
In theory, yes. In practice, no, because of all the companies in the supply chain using proprietary blobs and not open sourcing them. At least according to this link.

https://www.phoronix.com/scan.php?page=news_item&px=Android-AOSP-Close-Linux-5.9

Hopefully we get more information about GKI's when the pixel 5 is launched, which is what I think will be ultimately used over mainline linux in devices. I don't know if it would be possible to port either to older devices like the OP3 though.

https://source.android.com/devices/architecture/kernel/generic-kernel-image
[OnePlus 3 & 3T Cross Device Development] CodesCodger:
[MENTION=5091734]dianlujitao[/MENTION] sir, is it possible to merge this commit: https://github.com/ShivamKumar2002/...mmit/5a84f0caa1189bb49c0bb352b6461688d00b4538 .

My carrier has enabled VoLTE for all VoLTE capable devices. This is the only relevant commit i have found for enabling VoLTE for my carrier
[OnePlus 3 & 3T Cross Device Development] moso11:
The flashlight on my 3T seems to turn on by itself.

I'd place the phone on table, pick it up after a few minutes, and the flashlight would be on.

This happens once in every 10 times maybe.

I have removed flashlight from quick settings, turned off long press to turn on flashlight, and turned off gestures from settings menu. But this still keeps happening.

This started after I installed 20200914 update.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Just saw this. 5.9 mainline on AOSP 11. Interesting that a not very well known Sony device got it first lol.

https://www.xda-developers.com/sony-xperia-m4-aqua-mainline-linux-kernel-android-11-custom-rom/

Looks like they needed to make a whole new device tree from scratch though.
[OnePlus 3 & 3T Cross Device Development] brmbjn:
how to open recent app ? please
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Press the recents button, which by default is on the left hand side. You can swap back and recents in settings>system>buttons>additional buttons
[OnePlus 3 & 3T Cross Device Development] brmbjn:
My recent button not work

How to fix ?
[OnePlus 3 & 3T Cross Device Development] Sudhangshu:
Use on screen navigation then or full screen gestures.
[OnePlus 3 & 3T Cross Device Development] :
How should we know?

Assumimg you've serached the thread before posting you know allready that's not a common issue, but specific to your setup. Without detailed knowledge of this specific setup, we can't help you.

Based on current infprmation this can be anything from a misconfigured button, a misbehaving app or mod to a physical damage.

Additionally the issue report "my recent button doesn't work" may be ambiguous. Is just the recents not poping up, or is the physical button without function (easy test: do the buttons light up if recents button is touched)?

Can you reproduce the issue on a clean flash with only gapps (nano or pico fpr opengapps) and nothing restored? If so, get a log from the failing button press.
[OnePlus 3 & 3T Cross Device Development] brmbjn:
How to ?
[OnePlus 3 & 3T Cross Device Development] Sudhangshu:
Look in settings for buttons option or else you can use magisk or any app from playatore, try searching it, it's easy.
[OnePlus 3 & 3T Cross Device Development] Freg:
https://www.google.com/search?q="recent+apps"+lineageos+17.1

Unfreeze Trebuchet, even if you are using a different launcher.
[OnePlus 3 & 3T Cross Device Development] brmbjn:
What launcher ?
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=978982]freq[/MENTION]: Good point. Maybe [MENTION=6511605]brmbjn[/MENTION] has replaced trebuchet alltogether by gapps package (https://github.com/opengapps/opengapps/wiki/Stock-Package ). That's why I've told him we can't help him without detailed information on the setup, but he should try to clean flash with nano or pico and share a log if the recents button is still failing. I'm not sure if [MENTION=6511605]brmbjn[/MENTION] is trolling us, or why [MENTION=6511605]brmbjn[/MENTION] is asking things like "What launcher?"; but I'm sure it's a waste of time to answer him without more setup specific details.
[OnePlus 3 & 3T Cross Device Development] g96818:
I'm having trouble on a fresh install of the 9/28 build. The screen goes black right after it asks me if I want to copy over data from my old phone or start fresh. Anyone know how to get past that?
[OnePlus 3 & 3T Cross Device Development] :
Which gapps package do you use?
[OnePlus 3 & 3T Cross Device Development] g96818:
I used stock. I didn't see anything recommending a specific gapps package.
[OnePlus 3 & 3T Cross Device Development] :
Stock replaces quite some rom shipped stuff (see the link for the readme for the stock package - e.g. the launcher is replaced). This is very prune to issies and unwanted side effects. Use nano or pico. If it still breaks, try an older package (due to automatic building opengapps sometimes ship nro,en packages).

If you search this thread you'll find the nano/pico recomendation many times.
[OnePlus 3 & 3T Cross Device Development] g96818:
Thanks. I'll admit i didn't search which package people recommended, just look on the first post and lineage site. It's been a while since I've used LOS since OOS is pretty nice, but it's not being updated and i didn't really see any OOS based for android 10.
[OnePlus 3 & 3T Cross Device Development] brmbjn:
Yes. Fixed

Not support gapp package.
[OnePlus 3 & 3T Cross Device Development] :
Some general notes on gapps - applies to all aosp/los roms/versions: https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post83170309#post83170309
[OnePlus 3 & 3T Cross Device Development] lokeshjt:
I'm on the Sep 28 build. Phone is encrypted and bootloader is locked. No Magisk. It passes safetynet and Google Pay and some banking apps work fine. But HDFC bank app doesn't work, saying that phone is rooted. I have already tried renaming the TWRP folder but it didn't help. Also tried deleting the TWRP folder and reinstalling the app. Is there any other known pattern that apps use to detect if phone is rooted?
[OnePlus 3 & 3T Cross Device Development] :
Depends on the root dection the app is using. Most probably "dangerous properties" are detected. I've never managed to get hands on a comprehensive list of "dangerois properties", but

ro.secure=1
ro.adb.secure=1
ro.debuggable=0

are expected as above by most root detection kits/libs. E.g.:

ro.debuggable=1

can trigger root detection (among many other possible trighers).
[OnePlus 3 & 3T Cross Device Development] rohan164:
Query.

How to disable trebuchet lancher and use lawnchair launcher .

I disabled trebuchet launcher using adb and used lawnchair but recent apps does not work.

Then i used quick switch magisk module.

That too didn't work.

Please support.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I use Nova and made it the default Home App in Settings>Apps and Notifications>Default apps. I didn't disable Trebuchet and Recents works fine.
[OnePlus 3 & 3T Cross Device Development] rohan164:
if we don't disable trebuchet, it hogs too much battery in the background.

[MENTION=2911853]BillGoss[/MENTION]
[OnePlus 3 & 3T Cross Device Development] Iceman248:
I just did a clean install of latest 9/28 build with latest BiTGApps-arm64-10.0.0-R17_signed and BiTGApps-addon-arm64-R5_signed. During first boot, it reboots during animation logo to recovery over and over. I had previously used 10/8 stock and aroma and it made it as far as just after the part where it asks to restore from backup and then says it's doing something but eventually black screens except for top bar and nothing gets it past that, then I read about BiTGApps, so I tried them, but it's even worse. Without any GApps, it works fine.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
On my phone Trebuchet barely does anything. Here are some stats from BBS. Also, I've never seen it show up on the system battery usage graph chart.

Note that I've only had the screen on for 43 minutes (it's the start of my day), but the phone has been on for 13 hours since I charged it.
[OnePlus 3 & 3T Cross Device Development] Naudiz:
I just updated to 20201012 build and my phone started freaking out during the bootloader screen. The screen with the 1+ logo constantly loops while vibrating with a frequency of just half a second.

Was using Magisk 21.0 and a locked bootloader. Maybe the latter is the problem here, but it never was before. I will try and check what's going on and keep you updated.

UPDATE: A first success: Uninstalling Magisk 21.0 made the phone boot again. I keep on testing. Caution is advised for other Magisk users.

UPDATE2: Manually re-installing Magisk 21.0 works. The problem occurs only when Magisk's addon.d script is run. I was able to reproduce this behavior three times now. For users who need a hassle-free updater, I recommend reverting to Magisk 20.4. Others who are willing to test could try to reproduce this issue on their devices. Maybe it affects only devices with locked bootloaders. Maybe Magsik 21.0 addon.d script has a bug that forgets to sign the boot IMG properly. This will need further testing from other users. When we know more, we could file an issue on Magisk's github.
[OnePlus 3 & 3T Cross Device Development] mk_1996:
I was on the same setup but my bootloader is unlocked and i faced no issues while updating. Maybe it's an issue with locked BL?
[OnePlus 3 & 3T Cross Device Development] Naudiz:
It's good to know that unlocked BL works.

I also believe that it happens with a locked BL only. It makes sense - an unlocked BL will simply not care if Magisk's addon.d will sign the boot.img or not, while a locked BL will refuse to boot.

Maybe here's another user with a locked BL who is willing to give it another test.
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
I have the same setup like you, but I'm afraid to test. :eek:
[OnePlus 3 & 3T Cross Device Development] Naudiz:
In my case the problem was easily fixable by flashing Magisk Uninstaller ZIP file in TWRP. Recovery was reachable by pressing Vol up + Power. No need to be afraid. What's the alternative anyway? Never update again? ;)
[OnePlus 3 & 3T Cross Device Development] :
Get it fixed in magisk, of course.

This seems a regretion to pre-20.3 behaviour (https://github.com/topjohnwu/Magisk/issues/2013 ) and shouldn't be hard to fix. A recovery log from the dirty flash (which includes the log of magisk's addon script) would be helpful to tell if it's wrongly signed or not signed at all. A github issue report is the way to go here. [MENTION=4544860]osm0sis[/MENTION] is extremely helpfull on signing issues.
[OnePlus 3 & 3T Cross Device Development] risheek7:
No sensors working.

I flashed lineage os 17.1 October 12th build and cpu z shows a blank page in sensors tab. I have f2fs file system and clean flashed the rom via twrp 3.1.1.0
[OnePlus 3 & 3T Cross Device Development] :
I'm surprised twrp 3.1.1.0 is working at all. I suggest you reread the OP and follow the directions (twrp 3.4+). Tip: use nano or pico gapps and clean flash.
[OnePlus 3 & 3T Cross Device Development] risheek7:
Well, I had my doubts on that too and clean flashed it via twrp 3.4 and still sensors weren't just working. I even went back to ext4 and still it's the same.
[OnePlus 3 & 3T Cross Device Development] :
Which firmware are you using?

Which version and size of gapps are you using?

Do you have anything installed/restored (apart from gapps)?

Is it just cpu z that can't find sensors (e.g. is fp working? is the light sensor (automatic brigthness) working? Is display rptation working?)? You can check these even without gapps.

Do you see any successfull/failed sensots in the log?
[OnePlus 3 & 3T Cross Device Development] risheek7:
I am on oxygen os 9.0.6 firmware and tried clean flash without gapps as well. All hardware info apps show no sensors and no sensors are working. Speaking of logs, how do we check it?
[OnePlus 3 & 3T Cross Device Development] :
Setup adb on a pc:

adb logcat -d >logcat.txt
[OnePlus 3 & 3T Cross Device Development] risheek7:
10-15 14:54:49.997 12459 12459 E Sensors : sns_main.c(447):Timeout waiting for SMGR service. Exit sensors daemon!

10-15 14:54:49.997 12459 12459 W Sensors : sns_main.c(355):sns_main_exit called unlock daemon to exit

10-15 14:54:49.997 12459 12459 E Sensors : sns_main.c(561):Exiting! Err 0

10-15 14:54:50.006 1 1 W libc : Unable to set property "ro.init.updatable_crashing_process_name" to "vendor.sensors.qti": error code: 0xb

10-15 14:54:50.007 1 1 W libc : Unable to set property "ro.init.updatable_crashing" to "1": error code: 0xb

10-15 14:54:50.037 12656 12659 E Sensors : sns_fsa_la.c(448):realpath failed for directory name13

10-15 14:54:50.037 12656 12659 E Sensors : sns_fsa_la.c(448):realpath failed for directory name2

10-15 14:54:50.037 12656 12659 E Sensors : sns_fsa_la.c(89):invalid directory path -128

10-15 14:54:50.037 12656 12659 E Sensors : sns_reg_la.c(299):/persist/sensors dir dismiss, and remake it failed

10-15 14:54:50.037 12656 12659 E Sensors : sns_reg_la.c(312):Error creating registry file

10-15 14:54:50.036 12656 12656 W sensors.qti: type=1400 audit(0.0:369): avc: denied { getattr } for path="/mnt/vendor/persist" dev="sda2" ino=2 scontext=u:r:sensors:s0 tcontext=u:object_r:persist_file:s0 tclass=dir permissive=0

10-15 14:54:50.037 12656 12659 W Sensors : sns_reg_mr.c(367):File init failed 5

There you go
[OnePlus 3 & 3T Cross Device Development] :
Please use code tags for partitial logs.

The selinux denial is really strange. May be a followup error of something else - impossible to tell from the filtered log snippet. Does you ever mess with the persist partition?

Which firmware package did you use?

What was the last running rom?

Which exact steps did you perform after shutting down the last running rom?
[OnePlus 3 & 3T Cross Device Development] risheek7:
No, i never messed with the persist partition. Last running rom was oos 9.0.6. FYI, this same bug was in september 14th nightly that was removed from the site later. The newer nightlies didn't have this, however it seems to have reappeared and dian seems to be unaware this time.

I wiped /system, /data, /cache, /dalvik, mounted /system, /data, /cache and flashed the nightly.
[OnePlus 3 & 3T Cross Device Development] knpk13:
I've tried upgrading to the 1012 using the OTA updater to check for the sensors bug a few times and it keeps failing. I'll try flashing it manually and let you know if I can reproduce the bug.

Edit: I cannot confirm the bug. All my sensors work and show up in AIDA64 after upgrading to the October 12th build.
[OnePlus 3 & 3T Cross Device Development] moscic:
Same for me
[OnePlus 3 & 3T Cross Device Development] risheek7:
This is strange. I have flashed nitrogen os 10 and everything is working for me. I wonder what is the problem. I faced similar issue on havoc 3.9 gapps build and mokee 10.

PS: I tried flashing nitrogen os kernel on the roms in which sensors were missing and they came back (sensors started working).
[OnePlus 3 & 3T Cross Device Development] :
Not surprising: if the selinux denial (a full log would be more helpfule then the filtered snippet) is the cause for the disappeared sensors, nos boot image (boot img is not only the kernel!!!) will "fix" it. nos is selinux permissive...
[OnePlus 3 & 3T Cross Device Development] risheek7:
I have mokee logcat but can't figure out a way to send that file
[OnePlus 3 & 3T Cross Device Development] Cotopaxi42:
Hi there,

I have a question: when using my OP3 with LOS 17.1 as hotspot for my laptop, my OP3 freezes when I use Bittorrent and I have to reboot the phone.

I can use other softwares without problem.

Do you know what could cause this? And how I could solve it?

Thanks!
[OnePlus 3 & 3T Cross Device Development] :
Disclaimer: I won't examine logfiles from other roms in the los17 thread. I won't examine logfiles from los17 with cross and back flashed kernels. This is too complecated and far behind my knowledge and abilities. Keep it short and simple for my small brain. Reduced complexity makes me smile, increased complexity makes my head dizzy.

To answer your question: zip the log and attach it to the posting.

Note: it's important for this issue to see the complete boot sequence. Since logcat is a kimd of ring buffer it would make sense to increase the logbuffer size in devopts to 1 mio and reboot.
[OnePlus 3 & 3T Cross Device Development] risheek7:
Oh okay

---------- Post added at 07:32 PM ---------- Previous post was at 06:45 PM ----------

https://drive.google.com/file/d/1-yvxLqJoCisI9lLjeqiD4ClZR1vpdKdc/view?usp=sharing

i made a fresh log cat from lineage os
[OnePlus 3 & 3T Cross Device Development] BillGoss:
[MENTION=10300871]risheek7[/MENTION], I'm also on Los 17.1 201012, md5 cab785e2bfa780affbefc7792c5e1f0d and I have absolutely no problems with sensors. The logcat errors you're getting don't show up in my logs.

I'm using Open Gapps 200711 pico, Magisk 21000 and Magisk Manager 307.

It seems to me that the problem is with your installation or your phone.
[OnePlus 3 & 3T Cross Device Development] :
I've no access üermissions for that file.
[OnePlus 3 & 3T Cross Device Development] risheek7:
https://drive.google.com/file/d/1-yvxLqJoCisI9lLjeqiD4ClZR1vpdKdc/view?usp=sharing

Sorry, i forgot about removing the restriction. This will work.
[OnePlus 3 & 3T Cross Device Development] :
It's really strange: selinux policy denials access from sensors to the persist partition, but I've no clue why this happens. Maybe flashing a sar rom with a non-sar supporting recovery has broken something. I'd try in this order:

flash firmware package (https://github.com/nvertigo/firmware-3t/raw/master/archive/op3t/oxygenos-9.0.6-firmware-3T.zip ) and clean flash los.

clean flash oos 9.0.6 and check if sensors are working (https://xdaforums.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119 ), if so try los again.

use unbrick tool to revert the device completely (https://xdaforums.com/oneplus-3t/how-to/op3t-collection-unbrick-tools-t3896765), update with updater app to 9.0.6, and check if sensors are working - if not: rma at oneplus.
[OnePlus 3 & 3T Cross Device Development] risheek7:
I already tried that, it didn't help either. :(

---------- Post added at 10:20 AM ---------- Previous post was at 10:18 AM ----------

Will changing the selinux to permissive fix this? if yes, can you help me with that?
[OnePlus 3 & 3T Cross Device Development] :
I'm realöy tired on spending my time in your issue and getting one liners as an answer. "Check" means:

If you flash oos, do the sensors work and is selinux running enforcing or permissive?

If run the msm tool, do the sensors work and is selinux running enforcing or permissive?

Do you've really rma'ed the device at oneplus? If so: do the sensors work and is selinux running enforcing or permissive?

No. Switching off selinux (permissive is log only mode and should only be ised for setting up the policy and shouldn't be used in a daily driver, YMMV) is a security hazard and not a fix at all. Even calling this a workaround seems euphemistic to me. IMHO permissive is for debugging/setting up only.

Since we know it's setup specific, it has to be send to this setup state by your acitions. All thes strange things you've done (flashing sar rom with non sar recovery; mounting system and cache in recovery before flashing) there's quite a probability you've done something you've forgotten to mention and it's so far fetched, that I'm not able to ask for it. If msm tool isn't fixing this, I'm out of ideas and my last resort is rma...
[OnePlus 3 & 3T Cross Device Development] risheek7:
I am sorry for the inconveniece but I am happy to report that the issue has been fixed. It had something to do with a broken file system, apparently. I repaired the filesystem through twrp by reformatting it with ext4 and then f2fs. All the sensors are working now. Also, thanks a lot for your willingness to help me.
[OnePlus 3 & 3T Cross Device Development] server3249:
How do you change the color calibration in LineageOS 17.1 ? Can't find the option. Just came from stock where I have been using SRGB and these stock colors are totally inaccurate.
[OnePlus 3 & 3T Cross Device Development] risheek7:
You'll find it in Settings->Display->Live Display
[OnePlus 3 & 3T Cross Device Development] server3249:
TRAI official DND application is not working on this ROM. Can someone please check ?
[OnePlus 3 & 3T Cross Device Development] Eggstones:
I installed the latest version (19th October 2020) and now my phone is stuck on the start screen. Normally when I install the update the phone just restarts without any issues. I tried choosing choosing restart the bootloader but the phone just went back to the start screen. I haven't tried recovery mode yet. Turning the phone off and on again didn't help. Any idea what to do?
[OnePlus 3 & 3T Cross Device Development] :
What do you mean by start screen? boot logo or boot animation?

How did you update? Manual flashing or Updater app?

Which twrp version are you using?

Did you validate the downloaded zips by it's checksum?

Did you try wiping caches?

Did you try dirty flashing the rom again, wiping caches and storing the recovery log?
[OnePlus 3 & 3T Cross Device Development] Eggstones:
Not sure what the screen should be called it has four options: start, restart bootloader, recovery mode and power off.

Previously when I've had a linage 17.1 update notification I've just downloaded and clicked install and the phone would just rattle through the installation process without any problems. Never done any validating of checksums as all had been done by the installer. Not sure what version of twrp I have as it is sometimes since I installed it. I've not viped any caches or stored any recovery log. Don't actually know how to do that.