yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] BillGoss:
For me that's meh.

I expect to get about 10%/hr (or less) drain when the screen is on.

Here are my stats from this morning (I switched from nano Gapps to pico, so that's why "full charge" starts around 85%).

And on the topic of Google Pay: using pico Gapps (like you are) and hiding Google Pay and Google Services Framework in Magisk still makes no difference. My phone is still not recognised by the terminal.

I can't make any sense of why it works for you but not for me. You are using NFC and tapping the phone on a terminal to pay, right? And you don't have any modules installed that modify NFC?
[OnePlus 3 & 3T Cross Device Development] Siddk007:
Wait. We dont use NFC in India much:p

Its all scan qr code and pay or direct transfer to upi account
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Aha! Thanks for this - now things make more sense.

Here in Australia we use tap-and-pay (NFC) for card transactions.
[OnePlus 3 & 3T Cross Device Development] Almohanned:
i have formatted and flashed the latest build with latest open gapps. and still crashing. i have tried MSM rom also with open gapps. and this one crashed once i connected to the car before even starting Android Auto. Finally, Nitrogen OS with open gapps worked fine. from the first try. i guess that is the only Android 10 rom that i can use with r-link.
[OnePlus 3 & 3T Cross Device Development] AnotiaWang:
I couldn't connect to any Wi-Fi. System Apps kept crashing too. Could you fix this problem? I can only surf through mobile data now
[OnePlus 3 & 3T Cross Device Development] Imnoa:
Did you clean flash and is your modem firmware up to date?
[OnePlus 3 & 3T Cross Device Development] Jigneshg:
Is that Airtel Volte u r talking abt?
[OnePlus 3 & 3T Cross Device Development] Siddk007:
yes, Airtel VoLTE
[OnePlus 3 & 3T Cross Device Development] AnotiaWang:
Solved. Thanks
[OnePlus 3 & 3T Cross Device Development] Jigneshg:
I guess it's time to flash this rom.. Encryption is supported I guess
[OnePlus 3 & 3T Cross Device Development] :
No need to guess. Just use thread search: https://xdaforums.com/search/thread/3990061?query=encryption and read (preferable before posting).
[OnePlus 3 & 3T Cross Device Development] vny10:
[MENTION=5091734]dianlujitao[/MENTION] override force dark mode in developer option auto turned off after reboot can u check
[OnePlus 3 & 3T Cross Device Development] Siddk007:
is there any way to automatically record calls? Have to click on record call option everytime while answering.
[OnePlus 3 & 3T Cross Device Development] Imnoa:
Maybe some dialers or 3rd party apps support this feature, check the play store
[OnePlus 3 & 3T Cross Device Development] :
No. According to the -1 comment from Danny, https://review.lineageos.org/c/LineageOS/android_packages_apps_Dialer/+/251235 won't make it to 16.0 without rewrite. I'm sure it's the same for 17.1 (btw: it's not cherry-picked to 17.1 yet, anyway). Not to talk of the legal implications (countries, that allow call recording doesn't neccessarily allow automatic call recording w/o notice). All in all I guess you won't see this feature in any official los builds in the (near) future.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Search the thread.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=8791678]hugoaferreira[/MENTION]:

...and stop your massive crosspostings:

https://xdaforums.com/search.php?searchid=462537187

Ask in the help forum for 10 roms with working nfc payment instead, if you can't find the answer by searching and reading the threads you've crossposting in.
[OnePlus 3 & 3T Cross Device Development] H. K. ROY:
anyone have this kind of icons stuck in the launcher? I know this happens when installing apps from the playstore but for me it just appeared all of a sudden and cannot remove it. I have tried clearing playstore data, force stop but nothing resolve this and there was no background app download.
[OnePlus 3 & 3T Cross Device Development] Master_TC:
Yes that is known.

Is not the ROM but the Launcher if I am not mistaken. This is the case with almost on all Android 10 ROMs.

Should be resolved in the future.
[OnePlus 3 & 3T Cross Device Development] Psydawg:
Hi there,

It seems doze mode is not working and that is currently the biggest issue IMO. Battery is almost dead overnight. Will there be any solution for this coming? Overall decently happy with this experimental build. Glad to see OP3 still supported as the phone itself is still wonderful. Thank you.
[OnePlus 3 & 3T Cross Device Development] Master_TC:
Sorry, no problem with doze mode or deep slepp. It's not rom releated.

It's up to your settings or apps.
[OnePlus 3 & 3T Cross Device Development] Psydawg:
Okay, that is good to know. Thank you.

My battery has been draining abysmally fast since the flash though (with fewer apps than before).

Currently, Android OS is taking up 32% battery drain and Android system 15%. Far more than any apps.

During the night the battery is usually drained by half unfortunately.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Try rebooting the phone.

I find that after installation, or restoring a backup, the phone has a kernel wake lock (rmt_storage*) that keeps the phone from going to sleep. But a reboot makes the problem go away.

Edit: added screenshots
[OnePlus 3 & 3T Cross Device Development] nucleerz:
I just received this email regarding openGapps

if you're interested;

https://www.xda-developers.com/open-gapps-android-10-roms/
[OnePlus 3 & 3T Cross Device Development] Imnoa:
Nice, only pico and nano so far, but that's the only versions I flash anyway.

No more week old beta gapps packages :)
[OnePlus 3 & 3T Cross Device Development] Psydawg:
Thanks for the suggestion but it wasn't flashed today. I have been running it for at least 3 weeks now. No changes so far.
[OnePlus 3 & 3T Cross Device Development] :
Does your device enter deepsleep over night?

If deepsleep is less then 96 %, which wakelocks prevent deepsleep?
[OnePlus 3 & 3T Cross Device Development] H. K. ROY:
Random Shutdown and Faulty Battery Percentage

I have been using the los17.1-20200112 build from the release date and 2 things that I have faced that annoyed me most is - random shutdown and battery percentage being inconsistent during usage.

Firstly, for the shutdown issue, I have noted that my device turned off at 46% (during writing this post), at 20-30% (most of the time), and in very few cases between 0-15%. According to Accubattery app my device's battery health is 80% and I was consistently getting 3.5-4hrs sot on my average usage on los16 with a similar setup. Sometimes, I have found the device dead after waking up in the morning with 90-100% charge before sleep (was listening to music) which didn't happen with los16.

Secondly, the battery percentage acts weirdly, for example- I was using camera for about 30min continuously and it didn't drop a single percent (stuck in 100%). In addition, when using (mostly music and browsing on wifi) percentage decrease was significant and for cellular, it was worst (can not complain much- network issue in my location, but it was not satisfactory in the better areas either). At one point I tried to recalibrate the battery and that worked for a few days but again the same problems. Surprisingly I did have some outstanding sot results also(attachments).

I use OP3 as my secondary device and it was clean flashed (wipe system, cache, dalvik, and formatted data when upgrading to los17.1, magisk, fw-9.0.6). I know it is too early to judge los17 but tried to share my experience which might help everyone here. :)
[OnePlus 3 & 3T Cross Device Development] hugoaferreira:
You spent more time in your unhelpful answer than you would replying to my question. Next time don't even bother to respond.
[OnePlus 3 & 3T Cross Device Development] :
Do you really see no advantage in asking one question in the help forum instead of crossposting in many threads? Crosspostings show a lack of understanding and/or bad manners. Reconsider your attitude, please.
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
Dear Hugo, I'd love you to understand that this forum requires behavioral norms, and that it's necessary to prevent development threads (such as this) from becoming massive of comments... (sometimes questions about things that are recurring topics and have been answered thousands of times).

Sometimes nobody has tested whether certain applications work or not and therefore can't answer the questions asked. In my opinion everything would be easier if we all tried things and shared the information logs, tricks, tutorials, and experiences. In addition to thar many colleagues (I include myself) use the forum application and receive some kind of notification for each comment.

While it is true that posting a question and being answered directly is the easiest way, there're several types of tools that allow users to ask questions and also search for specific topics quickly and efficiently, what we should use ALL. We want to motivate users to make use of them.

So don't take this personally, we all have the right and are free, but we also have to comply with rules and duties to maintain coexistence in the forum.
[OnePlus 3 & 3T Cross Device Development] hugoaferreira:
I apologise if I did something I shouldn't. Although, I would like to say I tried to search and didn't find the answer. Maybe because I'm a rookie and not because I was lazy. Don't worry. I won't spam the thread anymore. Thanks for the reply.
[OnePlus 3 & 3T Cross Device Development] ReeseyD:
Give a man a fish, he'll eat for a day. Teach a man to fish, he'll eat for a lifetime.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Build a man a fire and he'll be warm for a night. Set a man on fire and he'll be warm for the rest of his life.

- Terry Pratchett.
[OnePlus 3 & 3T Cross Device Development] Anghirrim:
[MENTION=5091734]dianlujitao[/MENTION] Just to say thank you for keeping our phone alive!
[OnePlus 3 & 3T Cross Device Development] pjgowtham:
Has lineage added their black theme yet?
[OnePlus 3 & 3T Cross Device Development] moscic:
No
[OnePlus 3 & 3T Cross Device Development] ajekb78:
Is it possible to get PS4 Remote Play working?

Is there any way of getting PS4 Remote Play working on Lineage? I tried this ROM on my OP3 and it works well, but even with Magisk and the Remote Play enabling magisk module it doesn't work. It's a shame because Remote Play only works with DS4 controllers under Android 10, and there won't be an official Android 10 ROM for the OP3 now it's been EOLed.

Could Remote Play perhaps be failing on custom ROM detection rather than Magisk detection, and if so is there a workaround to that?
[OnePlus 3 & 3T Cross Device Development] :
I've no hands on such controllers, but I've always thought kernel support is needed, isn't it?

CONFIG_HID_SONY=y
CONFIG_SONY_FF=y

Both options arn't used in los-17.1 (not in los-16.0, nor los-15.1):

https://github.com/LineageOS/androi...ch/arm64/configs/lineageos_oneplus3_defconfig

https://github.com/LineageOS/androi...ch/arm64/configs/lineageos_oneplus3_defconfig

https://github.com/LineageOS/androi...ch/arm64/configs/lineageos_oneplus3_defconfig

I cm-14.1 at least the controllers (but without forced feedback) are supported:

https://github.com/LineageOS/androi...m64/configs/lineageos_oneplus3_defconfig#L479

I'm pretty sure the magisk module can't work without the kernel modules. I guess the magisk module just adds/oberwrites the keylayout files.

So two changes (one for the kernel config, one for fw/b to add the additional keylayouts) should be sufficient to add PS2/3/4 controllers to los.

[MENTION=5091734]dianlujitao[/MENTION]: to avoid misunderstandings and don't make you wonder why no commit is pushed: the above is guessing - I can't test this (lack of controllers). I don't push untested commits to gerrit. I'll add the additional kernel config to my next nlos-16.0 build. If an nlos user reports it's working, I'll push it.

EDIT: Adding the keylayouts isn't neccessary. Tjey are already merged:

https://github.com/LineageOS/android_frameworks_base/commit/0a5109d955935e16b71812ec3c25c0e63d646e19

The magisk module is obsolete as the fw/b change.
[OnePlus 3 & 3T Cross Device Development] archcry:
I am trying to use NFC payment but this is not working. I searched this thread and I am not the only one apparently. The thing I cannot find at this moment is what causes NFC payment to not work. Can anyone give me some insight into this?
[OnePlus 3 & 3T Cross Device Development] Imnoa:
Did you hide root for the payment app using magisk hide?
[OnePlus 3 & 3T Cross Device Development] archcry:
I did not, let's see.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I tried both with and without hiding Google Pay in Magisk and it makes no difference.

I've never needed to hide Google Pay on any rom on this phone.

I think the problem is related to how the phone communicates with the POS terminal over NFC, because Google Pay sets up properly and doesn't report any errors and works if you don't use NFC. Also, Google Pay works in Nos 10 using the same gapps.
[OnePlus 3 & 3T Cross Device Development] asemenov:
I also do not understand why reinvent the wheel when there is a guaranteed working solution. Take it and use it, but no, for some reason they’ve been trying to do something of their own for several months, and nothing comes of it. In NOS10 AOSP NFS and here CAF NFC.
[OnePlus 3 & 3T Cross Device Development] :
Generally spoken, using code from qcom's code aurora forum is not reinventing anything. BTW: OnePlus uses caf code in quite some places.

Anyway, would you point me to the nfc caf code in 17.1, please? I've always thought nfc caf code was optionally used in 14.1 the last time. If caf based nfc is reintroduced again in 17.x, this would explain, why gpay via nfc terminal is working in 16.0 but not in 17.x anymore. Sadly, I can't find it (maybe because I'm not so familar with the 17.x sources as I am with 13.x to 16.x).

General note: I've read on the gpay-nfc issue in many threads, but I've seen no debugging attempts at all - so I'm not sure if somebody is working on this at all.
[OnePlus 3 & 3T Cross Device Development] archcry:
just tried with Magisk hide but NFC payments don't work as pointed out by [MENTION=2911853]BillGoss[/MENTION].

[MENTION=4405529]nvertigo67[/MENTION], are you saying this is a lineageOS 17 issue for all devices?
[OnePlus 3 & 3T Cross Device Development] :
No. I don't know. But that's one of the first questions i'd ask, if I'd want to debug this. Other good questions would be if nfc works at all, if extended length payload works, if only qcom soc based devices are effected (if caf code is the reason, exynos or kirin powered devices shouldn't be effected), if the logs show something (crashes, selinux denials etc. the usual suspects) etc.

Since none of the above has been discussed, I've guessed no one is dealing with this issue currently.

I'm not debugging this issue, I was just surprised when reading it's related to caf code in the nfc stack and "to do something of their own for several months".
[OnePlus 3 & 3T Cross Device Development] giovanniro98:
[MENTION=4405529]nvertigo67[/MENTION]

https://review.lineageos.org/c/LineageOS/android_build/+/257243

https://review.lineageos.org/c/LineageOS/android/+/256957

Switch to AOSP NFC could fix Gpay I think.
[OnePlus 3 & 3T Cross Device Development] :
This doesn't effect oneplus3, because NfcNci is called here:

https://github.com/LineageOS/android_device_oneplus_oneplus3/blob/lineage-17.1/device.mk#L364

This is clearly aosp based ("Switch to our AOSP NXP NFC HAL fork"). If you compare

https://android.googlesource.com/pl...+log/8a94bb8c26287d8d17a4969684c42f27bd71e1de with https://github.com/LineageOS/android_hardware_nxp_nfc/commits/lineage-17.1 you'll see it's 100% aosp - I guess the reason for using los' own fork is readding 1.1 hal for older devices without 1.2 hal blobs.

I've liked the idea (would have explained breakage from 16.0 to 17.x), but sadly it is actually aosp.
[OnePlus 3 & 3T Cross Device Development] archcry:
I realise you've helped me once before with some NFC issues. I think this fix was for extended length payload. I am still using my Yubikey with NFC and I can confirm that this still works in this ROM. I would like to help de-bugging I just don't know how. Like, do I have to go to a NFC payment terminal with by laptop hooked up to it with adb logcat running? It's kind of embarrassing to be at a terminal with the cassiere waiting for you to pay and you fiddling with your phone only to end up taking out a card of your wallet and pay with that.
[OnePlus 3 & 3T Cross Device Development] Siddk007:
Can Wifi Calling be enabled in this rom? already did a search regarding this but couldn't find anything
[OnePlus 3 & 3T Cross Device Development] Imnoa:
Try searching for "volte" in this thread
[OnePlus 3 & 3T Cross Device Development] Siddk007:
I'm talking about VoWifi
[OnePlus 3 & 3T Cross Device Development] knpk13:
Just switch it on? Is the option not there for you? My carrier doesn't support it so I can't test if it actually works though.
[OnePlus 3 & 3T Cross Device Development] Siddk007:
My carrier supports it but I'm unable to find the option. Where is this present?
[OnePlus 3 & 3T Cross Device Development] physpher:
Settings > Network & Internet > Mobile Network > Advanced > WiFi calling
[OnePlus 3 & 3T Cross Device Development] MJPollard:
Thanks, appreciated. I figured there were some extra things that needed doing, I just didn't know what they were. (I'm just tinkering around with it, anyway, as I have no intention of moving off Pie as my daily driver any time soon. I probably could have waited longer before experimenting, until 17 was beyond the alpha stage, but I've been itching to do something new ever since I got Pie up and running with all the features I wanted.)

Such insight. I never would have guessed. ;)
[OnePlus 3 & 3T Cross Device Development] PlayFriik:
Without this guy our device would be pretty much "dead"..

Thank you so much [MENTION=5091734]dianlujitao[/MENTION]
[OnePlus 3 & 3T Cross Device Development] BillGoss:
That works ... until you reboot the phone.
[OnePlus 3 & 3T Cross Device Development] JahGruva:
Nice job [MENTION=5091734]dianlujitao[/MENTION] will flash the next update...
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Oddly enough I tested NFC again after playing around with Digital Well-being and now it works. Maybe the system needed a few reboots. If the problem happens again I'll take logs.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Hi Bill

Does it boot up on encrypted storage?
[OnePlus 3 & 3T Cross Device Development] giovanniro98:
Have you tried to update to the beta version of the wellbeing?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Yes! See https://xdaforums.com/oneplus-3/one...ageos-17-0-oneplus-3-3t-t3990061/post80662027
[OnePlus 3 & 3T Cross Device Development] BillGoss:
No, haven't tried that. Since I don't use Wellbeing, I'm not bothered that it fails.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Sorry to bother again, but can i ask what gapps did you flash with this? I've observed on other devices' forums that gapps are usually an issue with 10 ROMs being beta. So wanted to get a version that works as it should
[OnePlus 3 & 3T Cross Device Development] BillGoss:
It's in my original post.
[OnePlus 3 & 3T Cross Device Development] clavelm80:
I have installed LineageOS 17 20191024 from LineageOS 16.

I had encrypted my phone.

I had to format data for 17 to work OK.

I've upgraded to 17 20191025 and I was in a bootloop, going back to recovery after entering the boot encryption password.

I tried downgrading to 20191024 but still a bootloop.

After wiping data, 20191025 booted OK.

I'm using magisk 20.

In 20191025 I've found a problem : when using the wifi sharing, the phone soft boot.

Thanks for the build of LineageOS 17.

Edit: also, Trust Data protection is not working, you can't set it on apps and advanced options forced closes.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I can confirm that BT is fixed for me on 1025 build.
[OnePlus 3 & 3T Cross Device Development] vny10:
Low volume during call in earpiece

Battery % also not working
[OnePlus 3 & 3T Cross Device Development] counterfeit187:
I'm very glad to see development has begun on los17. Thanks D. Best maintainer.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I clean installed 1025. While NFC turns on and off normally and I've successfully set up my card in Google Pay, the terminal doesn't recognise the phone. Logs attached.
[OnePlus 3 & 3T Cross Device Development] chtitlou:
First of all, thank you very much for this amazing job.

I didn't check everything to find some bugs - except confirming the known issues. But it seems that VoLTE works fine. Data switches to H+ when making a call and the sound is crystal clear. Well, it's just my feeling but I really notice the difference compared to a regular call. I don't know if there is another way to check it though.

Maybe something missing is the "+" for LTE - or 4G on my phone - in the status bar when bands are aggregated. I don't know if it's just a display that is missing or the feature that is not implemented yet. But I've got the same transfer rates as on LOS 16 with LTE+.

Besides, any tweak on the battery icon - text was known, but also the circle icon and so on - doesn't have any effect on the display in the status bar. But all of these are just cosmetics compared to what has been done.

Thank again ! So glad to see that OP3 is still on track and up to date !
[OnePlus 3 & 3T Cross Device Development] immi803:
[MENTION=2911853]BillGoss[/MENTION]

As few posts back, you wrote "once i set the security patch date to... Safely net passes..." , Can you please elaborate how to get it setup?

Cts false with me always :(
[OnePlus 3 & 3T Cross Device Development] Dirk:
Read post 3 in the NLOS ROM thread. In short you need to edit the Security Patch Date in the build.prop so that it matches the ROMs build fingerprint. Flashable zips are available.

This takes care of the CTS Profile part, but i'm surprised that safetynet as a whole passes. Usually the kernel patches need to be present for that. But then it was the same on LOS 16. It started life passing safetynet, but then was 'fixed' so that it stopped eventually.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I change the security patch date in Magisk. You can use this file:

1. Rename the extension from .txt to .sh

2. Follow the install instructions in the file itself (either using a file manager with root access or using the file manager in TWRP)
[OnePlus 3 & 3T Cross Device Development] redlozenge:
Anyone had any luck getting android auto to work when connected to the car? (I tried searching but don't see any successes mentioned.)

When I connect to the car (2017 Honda Civic) it starts to load on the car (black loading screen) and the screen on the phone turns black but nothing ever happens. It seems like it completely locks up the phone because nothing I do makes it come back on until I hard power off.

If there is anything I can do or provide to help troubleshoot please let me know. Not really sure where to begin, as this is my first ROM. Thanks!
[OnePlus 3 & 3T Cross Device Development] Siddk007:
I don't see such an option!
[OnePlus 3 & 3T Cross Device Development] xuser_:
I think op3/t is not officially supported devices for WiFi calling with Airtel/JIO
[OnePlus 3 & 3T Cross Device Development] knpk13:
Its not from what I know but I have Jio (I should have said the device is not supported, not that my provider doesn't support it) and I believe the settings option should show up regardless of support. I had the option show up when I was in the US and using cricket; I don't think it had WiFi calling or it wasn't supported, since I could never get it to work there either.
[OnePlus 3 & 3T Cross Device Development] Siddk007:
Any idea why it's not showing up for me at all!
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Try Magisk with Module VoEnabler-v1.5
[OnePlus 3 & 3T Cross Device Development] fiepi:
Screen Cast not work.

OnePlus 3

https://i.loli.net/2020/02/05/VesuEWlSCg6hKib.jpg

Another

https://i.loli.net/2020/02/05/UlAXG91xqo2btO7.jpg