yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
I suggest you read the complete conversation again: in one of his first postings [MENTION=1763460]Dirk[/MENTION] explained safetynet api tests are passing, playprotect status is certified and gpay is working. So "Am I three only one without any safetynet issues?" is completely off-topic and shows a lack of reading/understanding the conversation.

This conversation is about additional root checks done by third party apps. These checks are different from third party app to third party app. Some of these checks include different so called "dangerous props" and/or checks for the presence of twrp dirs on data, and reports rooted - though no root package is installed. Obviously you havn't used apps with these additional root checks.

[MENTION=9708417]Eric_Lev[/MENTION]: when you found that los recovery is working with your app in question but twrp doesn't, did you delete the TWRP dir or did you format data? I'm asking to understand if the presence of the TWRP dir alone triggers the positive root detection, or if it's "presence of TWRP dir and something else".
[OnePlus 3 & 3T Cross Device Development] BillGoss:
It's been mentioned in the Magisk thread that some protected apps detect the use of other apps that require root such as TB and/or the presence of TWRP folders.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I had deleted my TWRP directory before installing my banking app ... If my memory isn't playing tricks on me.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=1763460]Dirk[/MENTION], because of your issues I noticed some double settings in the LOS build.prop which I have included in the script now.

What I change now twice in ro.build.xxx and ro.system.build.xxxx are:

ro.build.tags=release-keys

ro.build.type=user

ro.system.build.tags=release-keys

ro.system.build.type=user

Could you therefor please download the setup.sh.txt script again at post https://xdaforums.com/showpost.php?p=82204597&postcount=710 and see if it makes any difference?
[OnePlus 3 & 3T Cross Device Development] Naudiz:
Today's build 20200615 fixes a lot of the annoying issues that the alarm clock was having. Looks like I can wake up again without getting angry at my ROM lol.

However one issue remains: the default notification sound is still played at the beginning of every alarm. Is there any way to fix this?
[OnePlus 3 & 3T Cross Device Development] Dirk:
Thanks but the script is unnecessary for me. Everything is working now without it. (With Oreo fingerprint as ROM default and locked Bootloader, Safetynet is passing. That takes care of Google Pay and anything else that only requires Safetynet. Renaming the TWRP folder fixed my Banking App).
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
"Ask, and it will be given you. Seek, and you will find. Knock, and it will be opened for you" ... (LOS Gerrit bible)
[OnePlus 3 & 3T Cross Device Development] Naudiz:
lol, I did search already, but naturally all results are older than today, so when today's build contains a new commit that is supposed to fix the issue, but in reality it doesn't, I believe it's fair to ask again.
[OnePlus 3 & 3T Cross Device Development] Dirk:
What issues have you had? I've used my alarm almost hourly last night without problems. N.B I'm not using the Clock app included in the ROM, which is removed by my Gapps Config. I use an older build of the Google Clock app.

I've had alarms set which have gone off while i was using Bluetooth and with Bluetooth turned off. i.e playing through the phone. In either case there's been no Notification sound played at the beginning. I can't imagine there's anything particularly special about my setup. I don't have the Sounds app installed, if that makes any difference.

Make sure you check all the places where you can set tones. The Clock App settings and Sound settings in the main settings particularly. Also, see if putting the phone in 'Do Not Disturb' makes any difference. (With Alarms allowed/Notifications disallowed).
[OnePlus 3 & 3T Cross Device Development] rohan164:
[MENTION=2911853]BillGoss[/MENTION],

[MENTION=4405529]nvertigo67[/MENTION]

i checked the path with Mix explorer, the path is same system/build.prop

but i don't know why i am not able to pull it.

i mounted system in LOS recovery

I enabled ADB in LOS recovery

/system_root/system/build.prop also not working

still no luck:crying:

[MENTION=10511117]Johan2020[/MENTION]

please let me know how you pulled & pushed build.prop file using ADB in LOS recovery.?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
You're right.

The alarm comes with the default sound notification ... Forget my previous joke ... ;)

A workaround : enable "Do not distrub" mode or Ring volume = 0
[OnePlus 3 & 3T Cross Device Development] Dirk:
Using the File Manager in TWRP i had to open 'system_root' folder, then 'system' to get to the file. So BillGoss was correct in that respect. Does Mix Explorer begin with the view already in the system_root folder?

Hopefully Johan will be able to solve the ADB issue for you.
[OnePlus 3 & 3T Cross Device Development] :
As stated in the post where I explain what and how I installed (page 171), I also mentioned I am not using LOS recovery AND that I am using a script in twrp to change build.prop.

As you have to update build.prop every time you do an update, I think it is not the most easy way to have LOS recovery and use adb to pull/push build.prop.

My advice would be to move to twrp and do flashing and running scripts/ updates whatever in twrp; you know what is happening, you can make backups and you have the most of flexibility.

Though for the path you can try:

/system/system/build.prop

/system_root/system/build.prop

/system/build.prop

The first two are based on SAR.
[OnePlus 3 & 3T Cross Device Development] Naudiz:
Until today the alarm would not come into the foreground, just showing the notification on the lockscreen. Also the default notification sound is played once before (or at the same time) the actual alarm melody begins. The former was patched in today's build, the latter not, apparently, even though the commit I linked describes this problem as well.

You will probably not encounter any of these if you replaced stock clock with Google clock. But I usually enjoy having as little Google as possible on my phone.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Good Afternoon Eric!

Is this with the Clock App included in ROM? Have you tried another Clock App?

Understood. I'm sure it will get fixed soon. Especially as it's now been confirmed as an issue by more than one person.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Hello Dirk

Tested with DeskClock stock app only.

I'll test another Clock app... asap.

Edit 1: No such trouble with Google Clock app.

Edit 2: https://www.reddit.com/r/LineageOS/comments/h9fmso/desk_clock_stock_app_los_171/
[OnePlus 3 & 3T Cross Device Development] Dirk:
Perhaps someone who's familiar with some non-Google, 3rd party clock apps, could recommend a good one for those who need an alternative for now?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
An alternative from F-Droid : https://f-droid.org/en/packages/com.simplemobiletools.clock/

APK : https://f-droid.org/repo/com.simplemobiletools.clock_19.apk

---------- Post added at 15:34 ---------- Previous post was at 15:28 ----------

FYI ... ;)

==> https://review.lineageos.org/c/LineageOS/android_packages_apps_DeskClock/+/278315
[OnePlus 3 & 3T Cross Device Development] Dirk:
I didn't realise Simple Tools had a Clock App. Looks really nice too. Now i'm debating whether to ditch the Google App myself!

Looks like LOS are on top of the issue too.

Thanks Eric! :good:
[OnePlus 3 & 3T Cross Device Development] rohan164:
After today update 15.6.2020, phone started to heat mildly.

Anyone faceing?

I am moderate user, no gamer.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Are you seeing anything unusual in your Battery stats? Like an app or system process using more than normal? Otherwise, i'm sure there are apps that can give a breakdown of CPU usage by process.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Now it's patched. Let's wait a week or till your next unofficial build :)

(I wouldn't need it as I use scheduled "do not disturb" over night and even didn't notice the issue till I read here and tried it myself )

One thing that persists:

The accent color is still yellow, but my theme color is blue. I don't know if it's purpose, but I don't think so: In my opinion tt should be the theme color.

Is the yellow screen still there?

In dark mode it's working normal.

I found the reason for the crash:

I'm using Bing wallpapers for getting a new wallpaper every day.

The app doesn't change the wallpaper everyday but uses a "Live wallpaper"

If I'm using a normal, stock wallpaper I can open the design & wallpaper app after applying a custom theme.

As soon as I switch back to a live wallpaper (Bing wallpaper) and apply a custom theme in design & wallpaper app - it crashes again after reopening it.

Can anybode reproduce this? You can try any livewallpaper from the playstore.
[OnePlus 3 & 3T Cross Device Development] :
I have tested a little with GPS settings and though GPS is working fine for me on LOS 17, locking is slow. When switching on GPS (no Google services and no WiFi or Bluetooth scanning) it took almost 30sec till first lock.

I changed my GPS.conf to:

# My GPS settings

# NTP Server - only one allowed!
NTP_SERVER=nl.pool.ntp.org

# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
# If DEBUG_LEVEL is commented, Android logging levels will be used
DEBUG_LEVEL=0

# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=1

# Accuracy threshold for intermediate positions
# less accurate positions are ignored, 0 for passing all positions
ACCURACY_THRES=0

# Below bit mask configures how GPS functionalities
# should be locked when user turns off GPS on Settings
# Set bit 0x1 if MO GPS functionalities are to be locked
# Set bit 0x2 if NI GPS functionalities are to be locked
# default - non is locked for backward compatibility
#GPS_LOCK=0

# supl version 3.0
SUPL_VER=0x30000

# Report supl ref location as position, 1=enabled, 0=disabled
REPORT_POSITION_USE_SUPL_REFLOC=1

#SUPL_MODE is a bit mask set in config.xml per carrier by default.
#If it is uncommented here, this value will overwrite the value from
#config.xml.
#MSA=0X2
#MSB=0X1
SUPL_MODE=0X2

# End of my settings

I guess because of INTERMEDIATE_POS=1 I have a location immediately and within about 3-5sec it is pretty stable. Much an improvement for me.

As I have heard a lot of people have issues with GPS, I am wondering if those people also get better results with the settings above.

You can find the file in /system/vendor/etc.

.
[OnePlus 3 & 3T Cross Device Development] Dirk:
I wonder how much of that is due to running Google free. I haven't turned on Location since flashing LOS a couple of days ago. As far as i know i'm just running default Location settings with the regular Google services. Just popped outside, turned on Location, opened Google Maps and it instantly zoomed in to my location. Didn't even need to press anything.

No GPS complaints here!
[OnePlus 3 & 3T Cross Device Development] snyperius:
Why is the security string not updated to the latest version? Or was it already included just not posted on the recent changes page on the LOS download site?
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Was your INTERMEDIATE_POS=0 ? Because I opened this file and it's identical to yours - but I haven't change anything before..

For me, sometimes it's working fine. It's finding my location fast.

But on other days, for example if I start Google maps, it stays 15min. at my home before it refreshes to my right place.

I also cannot evaluate how much Google with its location services helps there. I definitely have WIFI Search and BT Search turned off, but high accuracy turned on.

There is no regularity behind it, it just appears sometimes. Reboot is also helping, or waiting (but you often haven't the time to wait..)

Security patch is on level of 5th June since build from 8th June

It's also included on the recent changes site, but under the name "Merge tag 'android-10.0.0_r37' into staging/lineage-17.1_merge-android-10.0.0_r37"

https://review.lineageos.org/c/LineageOS/android_build/+/277007/
[OnePlus 3 & 3T Cross Device Development] DavidWolfen:
Hello, everyone! I'm experiencing bootloops when installing Magisk (both through survival add-on and manual flashing) with the most recent update (June 15). Am i the only one? Does anybody know how to fix that?
[OnePlus 3 & 3T Cross Device Development] Darkestnoir:
Still having GPS issues with the latest version(June 15), i also tried a clean flash (also because my recent app menu no longer worked again...) without success, GPS is to unreliable, sometimes it works, most of the time not, i think i am going back to latest OOS...

Edit: I also tried Johan2020 changes, but it not really improved anything. Now the GPS accuracy also shows values over 9000m
[OnePlus 3 & 3T Cross Device Development] :
Do you have gapps installed or not?

Wondering as [MENTION=8423339]Johannes1098[/MENTION] reported to have no issues with gapps installed, I am running without...
[OnePlus 3 & 3T Cross Device Development] Darkestnoir:
Yeah got gapps stock installed.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
https://wiki.lineageos.org/gapps.html

As reminder :

Note: If you opt to use Open GApps, they offer a variety of sizes of packages that include and overwrite different apps. We only recommend package sizes up through nano, as described in Open GApps Package Comparison. If you use a larger package, we can not guarantee that everything will function on your device, as in many of these cases our included apps are overwritten in favor of the Google App equivalents.
[OnePlus 3 & 3T Cross Device Development] knpk13:
It took longer than usual to boot after dirty flashing the June 15 build (with addon.d magisk) but it booted and everything works. I'm using Magisk canary btw. I did notice that with this build, my clock app keeps FC'ing and refusing to open even after clearing data.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Here also no problems with booting with Magisk 20.4 and Gapps

Sure that the cause is Magisk, and not for example some custom scripts (installing app without permission file to priv-app etc. etc.)

No problem isn't right.

Sometimes it's working, but other times not.

I think that we can say that Google Apps aren't the cause for our gps problem, because people with and without gapps have seen the issue.

But I think (personally for me): the Google high accuracy is sometimes fixing the location (with wifi and network cells), or "assists" gps to get a gps signal faster.

But in the end that doesn't change the fact that the gps signal itself isn't that good as with LOS 16 for several users..

I installed LOS 16 on my second op3t, maybe I can find some differences in gps configs...
[OnePlus 3 & 3T Cross Device Development] DavidWolfen:
Sorry, I was working (from home) while trying to find a fix and didn't have the time to get back here. I felt so stupid, but I just had to disable some Magisk modules. Reinstalling (most of) them from scratch did the trick. Thank you all for your answers!
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
I created a ticket on gitlab for this issue

https://gitlab.com/LineageOS/issues/android/-/issues/2115

It would be nice if some people can try it by themselves (only lasts less than 5min) - see the instructions on gitlab to reproduce

And if it also crashes on your device, please upvote the ticket :)
[OnePlus 3 & 3T Cross Device Development] Joshmccullough:
Of course it is. Had I just looked a little further down, I'd have seen it :silly: Thank you!
[OnePlus 3 & 3T Cross Device Development] H. K. ROY:
Stand by battery drain

[MENTION=5091734]dianlujitao[/MENTION]

Setup- op3, clean flash ( wiped system, cache, delvik, ext4) los17.1-20200615, open gapps, magisk

Issue- facing significant battery drain in stand by (100 to 84 in 4hrs with 4 min screen on). this happened for the last 2 nightlys (0608 & 0615)
[OnePlus 3 & 3T Cross Device Development] Sudhangshu:
Hello everyone

I would like to change my filesystem to f2fs, I have came across few post in XDA claiming to improve performance but I'm not quite sure about it so wanted to test myself. I have little to no knowledge on how to change filesystem in android, currently I'm on LOS 17.1 the most recent version with TWRP and unlocked BL. I have already searched the thread for any relevant information regarding changing from ext4 to f2fs but didn't find any, so if there's any guide kindly share here. Or any suggestion related to this query ,like if anyone here using f2fs and their experience, is welcomed.

Thanks to all.
[OnePlus 3 & 3T Cross Device Development] Dirk:
The 'How' is easy. In TWRP you go to the Wipe menu, advanced, select the partition you want to format and then select the filesystem you require. Like any format this will wipe your phone and erase everything from Internal Storage.

There was a thread on XDA with some comprehensive testing between f2fs and EXT4. The former showed a good lead in synthetic Benchmarks. This does not necessarily translate into real world perfomance though. I personally cannot tell the difference.

Moreover, EXT4 is better for compatability and some ROM expressly state that they do not support f2fs.

Personally i think you should stick with EXT4 if that is what you already use. Have you actually confirmed what your file system is at the moment? I recall it being f2fs by default on the 3T when the phone was released.
[OnePlus 3 & 3T Cross Device Development] giovanniro98:
I hear my voice echo from WhatsApp/Duo calls.

Anyone else noticed it?
[OnePlus 3 & 3T Cross Device Development] Sudhangshu:
Thank you for your response.

I'll check my filesystem, honestly I don't know what's default file system in 3t.
[OnePlus 3 & 3T Cross Device Development] :
See https://www.xda-developers.com/f2fs-why-file-systems-matter-interview-stan-dmitriev-tuxera/ A bit old but still valid (as for f2fs degration). It also answers your question.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I'm also facing GPS fix problems since the 0615 update.

Sometimes it's working (e.g. screenshot 16:23), but other times not (e.g. screenshot 16:21).

My setup : LOS recovery/Latest build/Nano open gapps/no root

[MENTION=1763460]Dirk[/MENTION] and [MENTION=2911853]BillGoss[/MENTION] : same trouble ?

Note: the OTA update of build 0615 with LOS recovery/Magisk/Unencrypted fails ... Uninstalling Magisk solves this issue!

Similar problem as: https://xdaforums.com/showpost.php?p=79072048&postcount=1094
[OnePlus 3 & 3T Cross Device Development] Dirk:
I'm using 0608 build and Google Maps has pinpointed my Location immediately, both times i tried it.

I probably won't be updating builds unless i see a commit that looks like something worth updating for.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Well, I'm still running 0608 and I've not made any system changes. I've not checked GPS behaviour since my previous post on this https://xdaforums.com/oneplus-3/one...ageos-17-0-oneplus-3-3t-t3990061/post82809491

But, now that you've asked, I had a look and my GPS signal is again getting a fast fix but it's erratic (2s, 9s, 27s) and I'm getting 0/18 satellites locked (screenshot).

So, like I said, this all makes no sense - go figure!
[OnePlus 3 & 3T Cross Device Development] :
Can someone tell me in which file the doze settings are stored?

I would like to shorten the time to go to deep doze without additional apps or using adb; would like to change it in the configuration file itself directly.

Though, no idea where these settings are in system....

Hope someone can help!
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
FYI : https://www.reddit.com/r/LineageOS/comments/hakn5j/state_of_encryption_for_someone_totally_out_of/

==> Take a look at goosnarrggh's answers ... Very educational ... IMHO !
[OnePlus 3 & 3T Cross Device Development] :
Take the answers from goosnarrggh with a grain of salt. The first of his answeres is nonsens: stock oos has forced encryption enabled, los hasn't. So

is nonsense. I havn't checked the rest (don't want to spend more time), but the above dpesn't make me want to do so... :(
[OnePlus 3 & 3T Cross Device Development] knpk13:
Actually I remember reading that general guideline about encryption either on the LOS wiki or in a reddit post by an LOS dev. Goosnargh didn't say it was a rule, he said the "odds are" encryption will follow stock ROM rules. I suspect it's ultimately up to the maintainer though, although in my experience most custom ROMs don't force encryption on the 3T (other than glassrom). On my 7T Pro, all custom ROMs I've tried forced encryption.

The rest of his posts basically talk about FBE and FDE and seem correct to me.
[OnePlus 3 & 3T Cross Device Development] Dirk:
I'm almost certain that when LOS published their Charter, it was stated that if a device had Encryption by default, that LOS would have to force encrypt. (Or words to that effect). Personally i prefer it as it is on the 3/T. The option exists from Settings, but not by default.

I'm also certain that i pointed this out the last time we had this coversation here! :D

Edit: Here it is:

All devices that supported hardware-backed encryption on their stock OS MUST support hardware-backed encryption.

All devices that shipped stock as forceencrypt SHOULD default to forceencrypt enabled.

All devices MUST support software encryption.

https://github.com/LineageOS/charter/blob/master/device-support-requirements.md
[OnePlus 3 & 3T Cross Device Development] sanchaz:
Anyway to force VoLTE/VoWifi?

The files on this https://xdaforums.com/oneplus-5t/how-to/guide-volte-vowifi-german-carriers-t3817542 guide are no longer available, but some in the thread confirmed it works for the carrier I need.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Are you looking for this?

https://xdaforums.com/oneplus-3/one...velopment/rom-nlos-16-0-t3879405/post82814595

---------- Post added at 06:46 PM ---------- Previous post was at 06:38 PM ----------

A SHOULD is not a MUST? Maybe they SHOULD use clearer language. No they MUST.
[OnePlus 3 & 3T Cross Device Development] Oblias:
Nice, I'll make note of that.

I see a trend here, in that LOS17 has to be involved somehow in order to just do a clean flash of the rom. I'm sure the others, Havoc, Xtended, all the rest will get there eventually tho.
[OnePlus 3 & 3T Cross Device Development] nucleerz:
I just flashed this ROM coming from stock OOS. After logging on I went to Security and enabled Encryption, whereupon it powered off (with no light or other indicator that anything was happening). Waiting for about an hour and a half for something to notify me of the process ending (or any indicator), I just unplugged the phone, held the power button until re-start and voila!...Lineage prompted for my log-in and I was back in to my phone. I checked Security again and yes, the phone was indeed Encrypted.
[OnePlus 3 & 3T Cross Device Development] :
Stock OOS without modification has forced encryption enabled. Your device is encrypted, if usimg stock OOS.
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
I've understood, he enabled encryption from settings running LOS17

Our mate didn't mention his previous status, OOS is ok, but encrypted or unencrypted?
[OnePlus 3 & 3T Cross Device Development] nucleerz:
yes, sorry for that. prior to installing, I disabled all passwords on OOS. Then in TWRP i formatted data, thus erasing the data encryption from stock.
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
I understood you correctly then, thanks for sharing your experience and ratifying a working encryption status ;)
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I'm sorry, but what do you mean by "refuting a working encryption status"?

I know for a fact that flashing Los 17 on an encrypted phone works.