yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] huzzug:
Hey guys,

I recently flashed mine with 17.1 nightly. I liked OOS, but for the past few months, a few of the apps started getting stuck which started overheating the phone.

I'm less than a week into this new install, but I'm liking it. Only, a few of the features that came with OOS aren't there. If some of you can suggest any free or better alternatives, I'd get this phone to just the way it was with OOS sans the overheating.

An app cloner or parallel app as was available in OOS

An app locker

Anyway for me to increase battery life. I've already disabled background tasks, unrestricted accesses and am always on battery saver, but is there a way to get even more battery life.

Anyway to root the phone as I'm currently using LineageOS with gapps installed.

P.s. The phone also feels sluggish while operating apps or playing games which didn't happen with the OOS.

Thanks for any help.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Flash Magisk
[OnePlus 3 & 3T Cross Device Development] huzzug:
Will it cause a complete format of the phone?
[OnePlus 3 & 3T Cross Device Development] Imnoa:
Rooting, no.

Unlocking bootloader, yes.

Please do some research before you ask things.
[OnePlus 3 & 3T Cross Device Development] :
Based on what I have read and my own results and the fact that both are proprietary software I think it is wise to revert the patches back to LOS16 GPS stack.

Is more testing needed [MENTION=5091734]dianlujitao[/MENTION] to make a decision?
[OnePlus 3 & 3T Cross Device Development] Adam Hui:
Can everyone pls check, on every build, enable dci-p3 then restart, the color will faraway from accurate... Must back enable again to standard or dynamic to taking a normal accurate color.
[OnePlus 3 & 3T Cross Device Development] Holgott:
Can anyone confirm the GPS fixes, based on last test built are available in the nightly from today?
[OnePlus 3 & 3T Cross Device Development] :
You can easily check yourself: follow the links [MENTION=9708417]Eric_Lev[/MENTION] has posted. If they are merged look for the next build started after the merge date.

Maybe it's quicker to check the commits overview for oneplus3: https://review.lineageos.org/q/project:LineageOS%2Fandroid_device_oneplus_oneplus3
[OnePlus 3 & 3T Cross Device Development] lokeshjt:
You can see the list of changes included in the build here: https://download.lineageos.org/oneplus3/changes/
[OnePlus 3 & 3T Cross Device Development] punio4:
Saw a lot of bluetooth stack related updates for lineage-17.1-20200629.

Bluetooth turn-by-turn directions in navigation still don't work. Microphone is still behaving weird

mmrhaul did a nice followup on the issue: https://gitlab.com/LineageOS/issues/android/-/issues/1805#note_358898400
[OnePlus 3 & 3T Cross Device Development] pro_drive:
Yes, I flashed 20200627 unoffical test build and got GPS fixed. It may take serveral days to merge changes to offical ROM.
[OnePlus 3 & 3T Cross Device Development] :
At least a week as the builds are weekly at the moment. If implemented before, you can use Wickenberg though, as he is building daily.
[OnePlus 3 & 3T Cross Device Development] Zebnastien:
I tried but couldn't reproduce here. Not shure how to check color accuracy but did seem significantly far from accurate.
[OnePlus 3 & 3T Cross Device Development] Adam Hui:
The comparation 'seemed color' between first attempt enabling dci-p3 with the result after direct reboot is enough for checking accuracy.
[OnePlus 3 & 3T Cross Device Development] Geenwor:
Hello!

I have an issue on 29 June build. Tinkoff bank app crashes when attempting to login with following error:

[06-30 13:20:17.918 15034:15034 E/AndroidRuntime]
FATAL EXCEPTION: main
Process: com.idamob.tinkoff.android, PID: 15034
java.lang.RuntimeException: java.lang.NullPointerException: Attempt to invoke interface method 'android.os.IBinder android.os.IInterface.asBinder()' on a null object reference
at android.app.job.JobServiceEngine$JobHandler.handleMessage(JobServiceEngine.java:112)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:214)
at android.app.ActivityThread.main(ActivityThread.java:7356)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)
Caused by: java.lang.NullPointerException: Attempt to invoke interface method 'android.os.IBinder android.os.IInterface.asBinder()' on a null object reference
at android.os.Parcel.createException(Parcel.java:2077)
at android.os.Parcel.readException(Parcel.java:2039)
at android.os.Parcel.readException(Parcel.java:1987)
at android.bluetooth.IBluetoothGatt$Stub$Proxy.startAdvertisingSet(IBluetoothGatt.java:1526)
at android.bluetooth.le.BluetoothLeAdvertiser.startAdvertisingSet(BluetoothLeAdvertiser.java:434)
at android.bluetooth.le.BluetoothLeAdvertiser.startAdvertisingSet(BluetoothLeAdvertiser.java:239)
at ru.tcsbank.mb.bluetooth.BluetoothAdvertiseJobService.onStartJob(SourceFile:24)
at android.app.job.JobService$1.onStartJob(JobService.java:62)
at android.app.job.JobServiceEngine$JobHandler.handleMessage(JobServiceEngine.java:108)
... 6 more

[06-30 13:20:18.030 2751:15226 I/DropBoxManagerService]
add tag=data_app_crash isTagEnabled=true flags=0x2

[06-30 13:20:18.031 2751:5159 W/ActivityTaskManager]
Force finishing activity com.idamob.tinkoff.android/ru.tinkoff.mb.ui.auth.BankPinActivity

Full logcat attached.

System specs: Magisk 20.4, nano GApps (20200630).

On previous build from 22 June app wokrs fine.

UPD:

What the hell?! Just turned bluetooth off and app launched properly! Some recent bluetooth changes have issue? Why the bank app even calls any bluetooth methods?
[OnePlus 3 & 3T Cross Device Development] CryNickSystems:
Updated to LOS lineage-17.1-20200629-nightly-oneplus3-signed.zip (from download.lineageos.org) on my 3T yesterday using OTA and it caused my phone to get stuck in a bootloop (as in: the boot logo would disappear after some time, the screen would turn black and then restart into TWRP directly).

I think it had something to do with the full disk encryption and magisk (as I got an error in TWRP while updating regarding "addon.d" and the data partition - didn't write it down).

Tried reflashing LOS, wiping everything but data but it wouldn't work. Had to wipe every partition (didn't have a backup).

Now I am hesitant to activate encryption again :D
[OnePlus 3 & 3T Cross Device Development] knpk13:
I also have a 3T, encrypted and with Magisk, and I had no issues with the OTA updater with this build. Are you using TWRP 3.4? Older versions of TWRP have issues with OTA updates with this setup.
[OnePlus 3 & 3T Cross Device Development] :
This has been a well known issue of automatic flashing (no passwd dialog; automatic reboot) an ota in twrp - it's also reported in this thread, the 16.0 thread the official twrp thread and in the help forum. It should be fixed in 3.4.0-0. Is this the first report of a boot loop on 3.4.0-0? Which version of twrp was installed on your device when using the automatic flashing?
[OnePlus 3 & 3T Cross Device Development] CryNickSystems:
I was using 3.3.1-0 from 2019-05-26 20:59:55 EDT :crying::eek:

Thanks for pointing me to the newest version. Out of curiosity: is there further info on this issue (e.g. a Github / GitLab issue link) about what I could have done to fix it? Or what the actual problem was?
[OnePlus 3 & 3T Cross Device Development] :
As explained it has been discussed already. The issue is known. The reason has been found and fixed. I gave you some hints where to search in my last posting. Please stick to xda rule #1: https://xdaforums.com/announcement.php?a=81
[OnePlus 3 & 3T Cross Device Development] :
+1

couldn't agree more: ota update, encrypted, Magisk AND twrp 3.4 is working without any issues
[OnePlus 3 & 3T Cross Device Development] :
Since the issue with boot looping after ota automatic flashing doesn't show up every time but perhaps one out of 10 or 15 times, we should carefully observe this...

BTW: Is the boot passphrase dialog shown on ota automatic flashing in twrp-3.4.0-0? (https://gerrit.twrp.me/c/android_bootable_recovery/+/1664 )
[OnePlus 3 & 3T Cross Device Development] knpk13:
I have used the OTA updater 3 times so far with TWRP 3.4 and it has worked. From what I can remember, with previous versions of TWRP, the issue occured every time for me, not one out of 10 times.

And yes, I am asked to decrypt data in TWRP when I use the OTA updater now.
[OnePlus 3 & 3T Cross Device Development] :
I really think/hope/expect this beimg solved. But if you take a look at the conversations on this issue, some users expirience it immidiatly but some users were using the ota automatic flashing successfully for some time and were hit out of the sudden (lack of following the los and twrp threads... ;) ) by this issue. It won't hurt to keep an eye on it. You are allowed to call me paranoid and a Murphy-Believer... ;) Optimism is just a lack of information... ;)
[OnePlus 3 & 3T Cross Device Development] RKS96:
U didnt have to wipe all partitions. Only system. In your case 1. wipe system, 2. Install linage os, 3. gapps and magisk. Always before wiping data check if you can decrypt in TWRP. If yes then problem might not be in data partition. And you still can create backup.
[OnePlus 3 & 3T Cross Device Development] deadmind:
Dont disturb - auto-activate ...

Hello,

since I installed LOS 17.1 from a scratch with pico gapps & magisk it did a great job for me beside 1 problem ... the 'don't disturb' -function tends to activate itself especially at night-time --- I deactivate it but after a while it's active again.

Any idea / suggestion how to fix that?
[OnePlus 3 & 3T Cross Device Development] agnava99:
In the latest build as of this post, I realized my phone gets real slow during battery saving mode (slower than usual)… and I'm wondering if anyone else notices an issue like this.
[OnePlus 3 & 3T Cross Device Development] :
May I kindly ask to read the thread and references given on "ota automatic flashing"-issue before posting? If you would have done so, you would have known, that the userdata partition is inaccesseble if this issue hits. Once again: this is a well known issue known since los-16 (at least since 18 months). xda rule #1 is not only valod for questions but also for answers... ;)

[MENTION=8329222]RKS96[/MENTION]:

Encrypt your device again. twrp-3.4.0-0 should have fixed it. If you want to be on the safe side, update manually (download with Update.apk; flash by maually booting twrp) for two months. If the "automatic flashing issue" stil persists some user not willing to read will run into it. After two months with no new reports, you (we) can be sure it's fixed.
[OnePlus 3 & 3T Cross Device Development] RKS96:
All information I gave was from my experience. Maybe I am missing something? I was on twrp 3.3.1 sar and encrypted. Was lazy didn't read thread and tried to flash using automatic updater. That resulted in bootloop. Tried flashing manually and still couldn't resolve bootloop. Wiped system and flashed los and everything worked fine. No data loss.
[OnePlus 3 & 3T Cross Device Development] :
Good to know - thanx for the heafs up. Since quite some users reported that formating (default action for wiping system in twrp) system hasn't worked, but formatting data did, we've two different issues here (excluding the possibility that all those isers arn't able to format/wipe system properly).
[OnePlus 3 & 3T Cross Device Development] Hemuli:
At which position do you have the notification slider? Did you select a schedule for the don't disturb mode?
[OnePlus 3 & 3T Cross Device Development] Siddk007:
Same case as [MENTION=8329222]RKS96[/MENTION]

twrp 3.3.1 SAR and encrypted. Updated through OTA and resulted in bootloop. Tried flashing manually but still bootlooped. Wiped system and then flashed the rom and everything worked fine. No data loss.
[OnePlus 3 & 3T Cross Device Development] :
Maybe my assumption was overoptimistic:

The longer I think the more I wonder if there are really two different issues... According to Ockham's razor the simpler explenation is user error on wiping system then two different issues...
[OnePlus 3 & 3T Cross Device Development] knpk13:
I don't recall having any issues with data loss or messed up encryption either. It's been a long time so I'm not sure, but I think I simply wiped system and flashed the update manually to get it working again.
[OnePlus 3 & 3T Cross Device Development] finr0d:
LiveDisplay is weird for me. I'm on the latest Nightly.

LiveDisplay can be toggled between "Automatic", "Off" and "Outdoor(bright sun)" modes and will be activate instantly upon tapping on the quick toggles(working as intended).

After pressing the power button to lock the phone and then unlocking it, Outdoor(bright sun) mode would not instantly activate if I press the toggle. I have to toggle to Outdoor(bright sun) mode, press the power button to lock the phone, unlock it, then only the Outdoor(bright sun) mode will be activated. Likewise, I have to lock the screen with the power button to activate the Automatic or Off modes. This only happens if AOD is activated.

Once I have deactivated AOD, LiveDisplay toggles instantly.

Is this normal behavior? Can't I have AOD activated and also choose to toggle between the 3 modes of LiveDisplay activating instantly?
[OnePlus 3 & 3T Cross Device Development] deadmind:
Position: down

Position-Setup (SYSTEM->KEYS->ADDITIONAL KEYS):

Upper: mute

Middle: only priority

Down: none

& I didn't select any schedule / deactivated them ...

So at the 'down-position' the don't-disturb-mode activates itself time by time (like if I would slide down the upper menue und manually enable it) --- strange, isn't it!?
[OnePlus 3 & 3T Cross Device Development] Hemuli:
Any change you could be accidentally pressing Vol UP and Power button together? There's just too many ways to change the mode. I would disable every shortcut and one by one enable them if it no longer occurs.
[OnePlus 3 & 3T Cross Device Development] Imnoa:
https://twrp.me/site/update/2020/06/24/twrp-3.4.0-0-released.html

Has anyone tested this (in combination with LOS17.1) yet? Otherwise I will test it

Edit: Nevermind, already been tested but search was borked so I didnt find it
[OnePlus 3 & 3T Cross Device Development] :
Why do you ask?

Did you read this thread? At least the last pages and OP? Or at the very least the installation instructions in OP?
[OnePlus 3 & 3T Cross Device Development] Imnoa:
Last edited by Imnoa; Today at 10:38 AM.

See my edit, search was borked so I did not find any results regarding twrp 3.4
[OnePlus 3 & 3T Cross Device Development] RKS96:
PS I am using f2fs.
[OnePlus 3 & 3T Cross Device Development] klickig:
Can anyone tell me how to cherry pick those changes. When I do it in the same order as above I get an error: cherry-pick is not possible because you have unmerged files.
[OnePlus 3 & 3T Cross Device Development] :
repopick from lowest to highest commit number. Don't forget to rebuild (or partially checkout) the vendor repository after applying changes to proprietary-files.txt.
[OnePlus 3 & 3T Cross Device Development] klickig:
Does not work for me. The first commit to cause the named error is 279475.

These is the output of "git status" in the "device/oneplus/oneplus3" branch:
[OnePlus 3 & 3T Cross Device Development] sahed01:
sorry if it sounds a bit noob but how do i root this rom? i tried magisk, bricked the device and tried su but cannot flash.
[OnePlus 3 & 3T Cross Device Development] Sudhangshu:
Well how did you flashed magisk and did flashing magisk was the reason for brick..?

So far I know you just have to flash the magisk zip file and after install manager for magisk.

That's how I have rooted my device.
[OnePlus 3 & 3T Cross Device Development] :
Please give a detailed description of

of "bricked" (bootloop? stuck on boot logo? stuck on boot animation? Can you boot recovery?)

the setup you've started from

all exact versions of all softwrae involved

all steps taken to flash magisk

Additional mandatory information to help you:

a recovery log from flashing magisk

a logcat from tne failed boot - if possible (setup adb before flashing magisk)

BTW: apart from hardware failures it's not possible to brick an op3/t - unbrick tool can restore all not hardware related unbootables. As long as you can boot recovery and/or fastboot mode the device is not even soft bricked.
[OnePlus 3 & 3T Cross Device Development] sahed01:
well, first i flashed SU with official latest twrp , didnt root. then flashed Magisk-v19.3 again with the same twrp and then it bricked.

---------- Post added at 08:45 AM ---------- Previous post was at 08:42 AM ----------

sorry about that. yes i was stuck at the boot logo. latest twrp (twrp-3.4.0-0-oneplus3) and Magisk-v19.3.zip was used.
[OnePlus 3 & 3T Cross Device Development] fswijoyo:
Did you have your bootloader unlocked?
[OnePlus 3 & 3T Cross Device Development] sahed01:
yes. umm, nevermind brother. i will figure it out. thank you for your reply.
[OnePlus 3 & 3T Cross Device Development] :
Please give ALL requested information:

A detailed description of the setup you are starting from and all software invloved, includes (but of course is not limited to) firmware version and bootloader state.

Magisk 19.3 is outdated and well known not to work with locked bl nor with android 10. Use current versions fpr M and MM.

EDIT: since I guess from the pieces of information you've given that you've flashed suaddon (from which bersion of los) or Superuser (both are known to doesn't support 10), but you javn't flashed the uninstaller, I'd recommend a clean flash before trying Magisk 20.4.
[OnePlus 3 & 3T Cross Device Development] zethis:
Hello there,

Fisrt, thanks for your work !

I have some delay issues with my SMS, 13 minutes to get one, also i have serious Wi-Fi drop, there is something i can do for help to fix this ? thanks :)
[OnePlus 3 & 3T Cross Device Development] klickig:
Thanks for the help. I was able to build and flash but was unable to boot. Really hope this hole GPS thing gets resolved soon.
[OnePlus 3 & 3T Cross Device Development] :
Which vendor blobs repository are you using?

Did you check the output of the extract script?

Did you check if the vendor bl9b reposotory has the changed blobs?

Where is booting stopped: boot logo or boot animation?

Can you get a logcat of the failed boot?

What's in pstore on the very first boot after the failed boot?

If I should guess, I'd say somethings wrong with the blobs repository.

EDIT: Always make a booting build before repopicking and changing the blobs.
[OnePlus 3 & 3T Cross Device Development] klickig:
Probably because of blobs. Im using the muppet repo. So should I 'repo sync' after cherry picking?
[OnePlus 3 & 3T Cross Device Development] :
No. You need to rebuild the vendor repo either by running extract-files.sh against an unpacked oos 9.0.6 op3(!), an oos 9.0.6 running op3(!) or an oos zip and commit the changes localy or by manually checking out the needed files from the 16.0 brach and commiting the changes localy. In other words: you need to make sure that all changes to proprietary-files.txt are also done in the vendor repo. Note that all files pinned (lines ending on "|sha1sum") arn't taken from unpacked rom or an oos 9.0.6 running device, but needed to put in the repo manually (as done for the current gps stack).

If you want to use an op3t rom zip or an op3t running oos 9.0.6, you need to adjust this:

https://github.com/nvertigo/android...d8dbba6#diff-e18a190ec9e1d301d38ff968dea34a59 (note the sha1sums for pinning arn't current, but you get the idea how to handle a530-zap* for unification).

EDIT: after every sync you need to repick the commmits or you can put it in a local branch. Keep in mi d to manually checkout your local vendor changes after each sync.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
You could use the unofficial build 20200627 from [MENTION=5091734]dianlujitao[/MENTION] if your own builds are failing - I'm using it for 1,5 weeks and gps works great with it :)

Link to post with DL link

https://xdaforums.com/showpost.php?p=82932809&postcount=1678
[OnePlus 3 & 3T Cross Device Development] sms3299sms:
Can someone tell me about gaming in this rom...?

Is it worth installing the rom on this device for gaming..?
[OnePlus 3 & 3T Cross Device Development] Sudhangshu:
I don't think you'll get gamers here, well there's always an option to try it for yourself and share your experience.

Besides I haven't tried it myself but heard corvus ROM is good for gaming, if that's what you are looking for give it a try.
[OnePlus 3 & 3T Cross Device Development] CallmeReaz:
Right now, I'm using Havoc ROM. can I install your?
[OnePlus 3 & 3T Cross Device Development] :
Clean flash. Depending on the havoc version you may need to update the firmware and twrp.
[OnePlus 3 & 3T Cross Device Development] Adam Hui:
I'm gaming pubg as heaviest on mine beside another two and it's ok with default auto graphics configured by pubg itself. But u need to keep interactive as governor & bfq as i/o scheduler to balancing its perfomance & battery durability.
[OnePlus 3 & 3T Cross Device Development] felixchris:
I second this. This build has definetly improved GPS performance for me. Have been following the discussion. Unfortunately my second device is beyond repair. That would have made for an amazing side by side comparison.
[OnePlus 3 & 3T Cross Device Development] Mustkeg:
Same here. I had arranged myself with subpar GPS performance under LineageOS because its other benefits greatly outweighed this concern.

But now even this seems to be fixed!

With the test build, I get a 3D fix inside a building in under 20 seconds with device location only.

Great work! :good:
[OnePlus 3 & 3T Cross Device Development] generalprobe:
[MENTION=4405529]nvertigo67[/MENTION]

Anything new on the Galileo front?
[OnePlus 3 & 3T Cross Device Development] :
Still searching. Waiting for confirmation. E.g.: https://xdaforums.com/showpost.php?p=82932523&postcount=70
[OnePlus 3 & 3T Cross Device Development] helderfp:
Nope, i'm in latest lineage 17 and still using GPS (USA Navstar) and GLONASS (Russia)

Edit: tried today and voila Galileo satelite
[OnePlus 3 & 3T Cross Device Development] punio4:
The changes to GPS are in!

https://www.lineageoslog.com/17.1/oneplus3
[OnePlus 3 & 3T Cross Device Development] sahed01:
you are right. i clean flashed the rom again and after that flashed the latest magisk. used the latest official twrp btw. and it worked. thank you very much.
[OnePlus 3 & 3T Cross Device Development] punio4:
What's the status with the microphone issues?

https://gitlab.com/LineageOS/issues/android/-/issues/1805#note_358898400

Someone did some really good research on the issue on Gitlab
[OnePlus 3 & 3T Cross Device Development] lokeshjt:
[MENTION=4405529]nvertigo67[/MENTION]

Took me a while but i found the difference by comparing carrierconfig apk. The vendor.xml file in OOS has this entry for my mcc/mnc (missing in LOS):

<carrier_config mcc="404" mnc="49">
<boolean name="carrier_volte_available_bool" value="true" />
<boolean name="carrier_volte_default_enabled_bool" value="true" />
<boolean name="carrier_vt_available_bool" value="false" />
</carrier_config>

and there's a whole bunch of entries for mcc = 404 and 405 which are missing in the LOS version of vendor.xml. I'm guessing adding these to LOS vendor.xml should resolve it ? Attaching files for reference.
[OnePlus 3 & 3T Cross Device Development] :
Please use the code tag for code - for readability.

You can overwrite the carroer config for these three properties by adding this to build.prop:

persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1

You may also try:

persist.dbg.wfc_avail_ovr=1
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1

Or you can ask the homebuilders here to make a build with your xml findings (overlayed in the device tree or in vendor/lineage). This would be needed anyway to proof it's working before commiting it to los.