yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
Constantly correcting people who don't ask the 'right' questions correctly is a HUGE waste & directly leads to unnecessary thread BLOAT...reported.:rolleyes:
[OnePlus 3 & 3T Cross Device Development] :
Enough kids. :silly::silly::silly::silly::silly::silly:

[MENTION=4405529]nvertigo67[/MENTION] Maybe you're on a bad day, or maybe it's just you being you. You must draw a line, clearly your last post isn't going nowhere other than flame wars.

Sometimes, ignoring is better. Well unless you want trolling around :silly:

I type this because i know you, you are a good caring developer :good:

And it's rare in this day, don't make your caring looks bad :cool:

“I've learned two things the hard way: You can't fix stupid and you shouldn't use up your patience to fix stupid.”
[OnePlus 3 & 3T Cross Device Development] BSAB:
Quick question before I do a factory reset (cause it seems it might be the only way to fix this)

I dirty flashed to the latest nightly after finally updating the firmware.

The phone booted fine, but when I insert my pin (on the "Pin Required After Device Restarts screen), it just goes back to the lockscreen, doesn't actually unlock the phone.

Anyone else ever experienced that, and if yes how did you fix it?
[OnePlus 3 & 3T Cross Device Development] :
Dirty flash again the rom

Or

There is a method you could try to remove pin lockscreen from twrp
[OnePlus 3 & 3T Cross Device Development] BSAB:
Cheers, [MENTION=5616867]150208[/MENTION].

Dirty flashed it again but no luck, same result.

Also tried this method, but the files I need to delete aren't there, so think it's time for the ol' factory reset!

https://support.mobiledit.com/portal/kb/articles/use-twrp-to-bypass-android-lockscreen
[OnePlus 3 & 3T Cross Device Development] Dirk:
Wait...

You're saying you boot straight to Lockscreen, (so no on-boot security), right?

You're PIN is no longer working on Lockscreen as it was before?

I'll attach a .zip that you can flash in Recovery to remove your Lockscreen security. Then you can re-add your Lockscreen security from Settings when you boot back into your OS.

Edit: Also, the reason "the files I need to delete aren't there", is because that guide doesn't tell you to Mount /System before you look for the files, so i'm assuming you didn't do that step.

Edit2: Also, when you re-add your Security (Fingerprint+PIN for example), make sure you say 'yes' to the prompt when asked to use that security at Boot. The fact that you can use the zip i provided to circumvent your Lockscreen is the reason that on-boot security exists in the first place!
[OnePlus 3 & 3T Cross Device Development] BSAB:
Dirk, you star, that worked!

Will definitely set up a boot pin, did not know it was this easy to bypass security!
[OnePlus 3 & 3T Cross Device Development] Dirk:
This is why FDE is bad. People like me don't use a Boot PIN because the janky boot-up procedure, but then TWRP goes and uses 'default_password' to let any old person with a zip file remove the Lockscreen Security.

FBE (Direct Boot) let's you get to the Lockscreen before any security is needed, unless you boot into Recovery, whereupon you have to enter it there before getting access.

Using a Boot PIN with FDE goes:

Bootloader Unlocked screen-Splash Screen-Boot Animation-Boot PIN-Splash Screen-Boot Animation-Lockscreen

It's awful. But it's secure.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
The relevant files are in /data/system so mounting the system partition does nothing for this.

The reason the files weren't found is because the guide is old. It should have also said to delete the locksettings.* files. But Dirk's zip replaced these, which is why it worked.
[OnePlus 3 & 3T Cross Device Development] :
it's an useful exploit, i don't really like being bothered with POB too

Saving a big time in cases like this

Of course it's useful with a pre-caution that you're well aware of your device (always being close to you all the time) and you can remotely wipe out your system if you wanted to.

Anything with physical access, especially if you are a high value target, even with POB and encryption means always screwed..

If you just a regular guy, chances are you might just get a low star thief who will just wipe your phone and sell it on ebay the next day...

oh yeah, since it's solved. i think it would be better to just remove your zip in case it might be doing harm for someone..
[OnePlus 3 & 3T Cross Device Development] Dirk:
My mistake. I assumed they were in /system. I've never had to delete them manually as that zip has always been in my toolbox. It was found on this forum, but in an old, obscure post that's impossible to find when you need it.

Also, Bill..you have a new face! :good:
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Lol! It's an old face (a more current photo).

I always delete the lock screen files using the terminal command in TWRP:

cd /data/system

rm -f gatekeeper.* locksettings.*

Or, to be more precise, I have a shell script on my sdcard that contains those command. The file is called rmpwd, so what I really run in TWRP is:

. /sdcard/rmpwd

Well, actually I do most of my TWRP work by creating a TWRP script file (/cache/recovery/openrecoveryscript) which TWRP executes as soon as it boots up. So, for example, when restoring a backup of a different ROM the ORS file would contain:

remountrw

restore /sdcard/TWRP/BACKUPS/1ebc8e1b/190305-133511_oos-5.0.8-m BSDM

cmd source /sdcard/rmpwd

Anyway, this is a bit off topic but, nevertheless, interesting.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Google translate says "Oldish fella in Australia land knows more about TWRP than most youngish folks in the rest of the world, while dodging any number of interesting and dangerous animals that could kill you while you sleep"

Also likes warm, fizzy Beer and hates when a Pom gets his hands on something called 'The Ashes'. :p
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Oh, very good! ?
[OnePlus 3 & 3T Cross Device Development] :
Absolutly! With hands on the device any encryption, passphrase or other security precautions can be broken - it's just a matter of effort. There is no absolute security or privacy. I agree with [MENTION=1763460]Dirk[/MENTION] on his fde vs. fbe review: booting with fde and POB is ugly and uncomfortable (and I reboot really often... ;) ).

Though my conclusion is just the opposite: most stolen data (from "just" addresses to banking account to complete digital identities) isn't done by intelligence services or criminal groups with high effort and nearly endless resources, but by criminals with few resources attacking weak or absent passphrases.

Using POB will dramatically increase your privacy and security, though it's not comfortable and - of course - can't give 100% security. In other words: not getting absolute security, is not the same as no security at all.

From my point of view using a passphrase on boot is really usefull.
[OnePlus 3 & 3T Cross Device Development] ikunalgautam:
Low volume in earphone ?? Any body facing this issue ??
[OnePlus 3 & 3T Cross Device Development] Der-Knuffi:
Did you use the search? About 3 Million hits...

Deactivate AudioFX.

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] Pablo.x:
Then, if I'm not wrong, easiest way to encrypt it's (from decrypted), format /data (to be decrypted and without any data to be faster).

Install ROM and encrypt from settings.

I think it might be better to encrypt only with ROM flashed (to do the process as fast as possible) and then make a clean flash (once encrypted) with ROM+GApps+Su...

Am I wrong? I would come from NOS decrypted (as there were problems with encryption some time ago)
[OnePlus 3 & 3T Cross Device Development] :
The less userdata is used, the faster encryption works. But our hw accelerated encryption process is quite fast. Flashing nano or pico adds only some KB to userdata (apps itself are added to /system - only gsettings db and some account data are added to userdata). So flashing additional gapps and magisk doesn't hurt much. i.e. Navigon incl. 4GB of maps data is a complete other story...
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
While talking about encryption...

Can anyone explain, how to check easily if my cellphone has a working encryption footer?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Settings ... Security & location .... Encryption & credentials .... Encrypted or not
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
"Encrypted"... is that good? :good:

And how can I set up a pin on boot?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
when choosing your screen lock:

Settings ... Security & location .... Screen lock ...
[OnePlus 3 & 3T Cross Device Development] Syssx:
Well you can just try and push the patch to LOS gerrit and add dianlujitao as reviewer, my guess is this should be in op3 device repo, as it doesn't seem to be an issue on other devices (or I did not see anything about it). Worst case scenario [MENTION=5091734]dianlujitao[/MENTION] says it can't be merged or thats it's wrong. Thats why Gerrit is in there in the first place.
[OnePlus 3 & 3T Cross Device Development] :
As long as I don't know how to answer 1. I can't give reasons why to merge. Perhaps this is just the fix for a side effect of something else. If you are right and no other device with fde needs these two rules, why does some users of op3/t need it?

If you feel ready to stand the discussion of these questions feel free to push it. I need my question answered, before I feel ready to push it to gerrit.
[OnePlus 3 & 3T Cross Device Development] Syssx:
That's a really good point which I don't really know the answer, I guess only guys from LOS will know that.

This is the reason why you're a great developer (if I can say it like this), you always try to ask questions which people like me don't even have in mind.
[OnePlus 3 & 3T Cross Device Development] Cmindo:
Thanks for this! Disabling AudioFX worked! However, is there a way to DELETE AudioFX from my phone completely?
[OnePlus 3 & 3T Cross Device Development] Dirk:
It's in either System/App or System/Priv-App, so Mount /System in TWRP and delete the package using the File Manager. There's never a bad time to learn how to gapps-config.txt either:

https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options
[OnePlus 3 & 3T Cross Device Development] kryzeK:
I have "fake" alarm clock in the status bar, they are activated randomly. When I check in the clock app if these alarms really exist, I see they do not exist. And obviously, when the time comes for that alarm clock to ring, nothing happens...
[OnePlus 3 & 3T Cross Device Development] :
com.android.deskclock or com.google.android.deskclock?
[OnePlus 3 & 3T Cross Device Development] kryzeK:
com.android.deskclock (the stock one), but I don't have set any alarm clock.

I've already freezed my clock apps (aosp clock and sleep as android) but the problem persists, it seems to be something related to SystemUI since these alarms are displayed only there.

For example now, in statusbar displayed an alarm for the 9pm, now that spent this time, it's showing an alarm for 9:40 pm. This is crazy...
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
No such issue on my side.

After performing a nandroid backup, could you check the persistence of clock issue with a clean installation of LOS 16.0?
[OnePlus 3 & 3T Cross Device Development] dtibor:
Hi!

There is a nasty bug in this ROM: each time when a video/music is played and I plug in a headphone the volume level is set to a very low level or there is no sound at all.

The bug is present after firmware update as well (version 5.0.8).

Did anyone experience this issue?

Thank you!
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
**** Please read the thread before reporting a issue ****

in SEARCH THREAD... Low & volume ... Enter

==> https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3866517/post79109345#post79109345

==> https://xdaforums.com/showpost.php?p=79123064&postcount=1218

.... etc

Fix: Disable audio FX
[OnePlus 3 & 3T Cross Device Development] Bindu009:
[MENTION=5091734]dianlujitao[/MENTION]

Please fix the headphone issue fast. The 3.5mm jack doesn't work since the 1st build. They don't work when plugged in but do work when anything is played on phone's speaker and then plugged in.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Please, see just above pour post ....

Otherwise, ask [MENTION=4405529]nvertigo67[/MENTION], he will be happy to answer you.... :D
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
I never attempted to do an OTA update so I can't tell what's wrong, but I completely don't get why only some of you are affected, and why "it doesn't seem to be an issue on other devices"?
[OnePlus 3 & 3T Cross Device Development] camdadeye291:
Greetings [MENTION=5091734]dianlujitao[/MENTION] :)) I have a question, what's the difference between the official and the unofficial (aside from the obvious). Peace
[OnePlus 3 & 3T Cross Device Development] Syssx:
Well that's the thing, it only affects some of us and we weren't able to track it down why. There is just a wild guess it has something to do with F2FS and SELinux. Please see:

https://xdaforums.com/showpost.php?p=79098123&postcount=1170 and especially this one:

https://xdaforums.com/showpost.php?p=79098599&postcount=1172 where [MENTION=4405529]nvertigo67[/MENTION] says:

That's why its so strange.

Also my statement "it doesn't seem to be an issue on other devices" is just my guess, because I did not find anyone complain on xda/reddit/gitlab issues about failing OTA auto flash. I could be really wrong.
[OnePlus 3 & 3T Cross Device Development] kryzeK:
I already come from a clean flash :(
[OnePlus 3 & 3T Cross Device Development] BSAB:
Hum, I think that method decrypted my phone, is that possible? Can't access my banking app and Google Pay doesn't let me tap to pay any more.

The phone is saying it's decrypted, and I go to the settings option to encrypt it and click on it (fully charged battery and plugged in to the charger), the green Android comes up for less than a minute and then the phone just goes back to the lock screen, and the encryption hasn't changed.
[OnePlus 3 & 3T Cross Device Development] :
Let me add some mystery:

I don't think it's filesystem relatd:

https://xdaforums.com/showpost.php?p=79090015&postcount=1152

---------- Post added at 15:39 ---------- Previous post was at 15:26 ----------

If you're reffering to [MENTION=1763460]Dirk[/MENTION]'s zip by "that method" the answer is: No. Not possible.

Once your device is encrypted you can't go back to unencrypted without loosing data. If your device wasn't encrypted after using this zip, it wasn't before either.

The only method to remove encryption is formating data. If you can't encrypt your device, there is quite some probability, that you have used twrp-3.2.3-1 for formatting, which is broken and removes the encryption footer. To get back the encryption footer, format with either <=twrp-3.2.3-0 or format with fastboot. Once you have the encryption footer back, you are recommended to us twrp-3.2.3-10 (this version of twrp honors what it finds: no encryption footer present, format will be done without encryption footer and vice versa).
[OnePlus 3 & 3T Cross Device Development] counterfeit187:
Does anyone know of any way to adjusted vibration duration and intensity for notifications? I imagine these are saved in a value somewhere in the system, right? I just don't feel it when it vibrates, its almost as week as haptic feedback
[OnePlus 3 & 3T Cross Device Development] BSAB:
Then I wonder what else might have happened as the banking app and the Google pay were working fine before I upgraded LOS and used the zip.

Is it possible that one of the files deleted by the zip had to do with it?
[OnePlus 3 & 3T Cross Device Development] pedritopl:
Google Pay stopped working with latest Google Play Services (15.0.90) and Magisk v18.1 for many. It's still unclear for me what exactly triggers it as it was working one day, and suddenly stopped the next day even though the app versions were the same.

Anyway I installed the lastest Canary build of Magisk (v18.2-8893cbd6, 18119) and it fixed Google Pay for me.
[OnePlus 3 & 3T Cross Device Development] :
I'm not using gpay, so idk.

My banking app (https://play.google.com/store/apps/details?id=de.sdvrz.ihb.mobile.secureapp.sparda.produktion ) would definetly break if configuered for fp auth. Even deleting and/or adding a fp breaks the app and I need a new first time auth key from sparda.
[OnePlus 3 & 3T Cross Device Development] Dirk:
When your phone detects you don't have a Secure Lockscreen you usually get a warning that Banking Apps won't work unless you fix that.

I'm going to guess that if you check Google Play settings it might say 'Uncertified'. Clearing Data/Cache from Settings/Apps should return it to 'Certified' and Pay will work again. (Providing you have Lockscreen Security set up now).

What probably happened. When you removed Lockscreen Security you started failing Safetynet, which would be reflected by the 'Uncertified' status in Play. Once Safetynet is fixed you need to do the Data/Cache wipe to get 'Certified'.

Let us know.

Edit: Also you might have to clear Data/Cache form Google Pay. Don't forget that once it detects the phone is failing Safetynet, it won't start working again unless that is done.
[OnePlus 3 & 3T Cross Device Development] detective zero:
Today's build is corrupt. Tried via OTA and directly from recovery. After flashing phone tells me to be an Asus X00TD and there's no mobile data, wifi, bt...
[OnePlus 3 & 3T Cross Device Development] helderfp:
Not for me, everithing working fine
[OnePlus 3 & 3T Cross Device Development] Dirk:
Are you saying that the LOS OTA updater downloaded an Asus ROM on your OP3/T, and when it failed to flash automatically you used the OTA file and manually flashed it?

What is the filename of that OTA zip?
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
I'm affected on my OP3T, too, whilst OTA update always worked unter LOS 15.1.

Other LOS 16 devices seem to be affected, too: Samsung Galaxy S5+ (kccat) has the same problem and LineageOS based rom "AICP" on Sony Xperia Z1 Compact (amami) also has the same problem.

These three devices exist in my family and I experience the OTA update problems by myself.

None of the devices had OTA problems in LOS 15.1 and previous versions.
[OnePlus 3 & 3T Cross Device Development] Uqbar:
I have done a manual update from 15.03.2019 to 16.03.2019 neightly and my phone is working great:

downloaded with the browser from the repo and the flashed from recovery ( [MENTION=5091734]dianlujitao[/MENTION]'s -10 version of TWRP).

I've never used the OTA update, though.

I don'ty know where the OTA update download is saved. If someone tells I can give a hand...
[OnePlus 3 & 3T Cross Device Development] :
/data/lineageos_updates
[OnePlus 3 & 3T Cross Device Development] :
I've no problems with this Sparda Secure app and fp authentication ...
[OnePlus 3 & 3T Cross Device Development] Dirk:
Not under normal circumstances, but if it detects Safetynet has broken or a change has been made it might require a clean setup to re-authorise it.

I personally restrict the Boot permission of Banking Apps. That way if you run into a temporary safetynet issue, like changing your Lockscreen Security, the app isn't running and doesn't detect the problem. Of course, if you don't realise you have a safetynet issue and launch your banking app, it will do a safetynet check and crap out.

Currently in LOS 'Trust' is set to Notify you of two seperate issues. Build Signature and Selinux problems. It would be great if a Safetynet check were added to that. A notification at Boot that Safetynet is broken would be useful. Of course, Safetynet is supposed to be broken by default on LOS. But that's another story.
[OnePlus 3 & 3T Cross Device Development] :
My bad. This time I was to lazy to be accurate... ...I thought accidently that the explenation was precise enough, to answer the general question regarding if "that method" (deleting lockscreen credentials) can interfere with banking apps.

Precisely:

After deleting lockscreen credentials (including fps like done by [MENTION=1763460]Dirk[/MENTION]'s zip) and readding them after setting up lockscreen passphrase, I get "internal error" message. This happens always when restoring a backup (with lockscreen passphrase set, and therefor require the deletion of lockscreen credentials). The "and/or" was a btainfart, it has to be "and"... ;)
[OnePlus 3 & 3T Cross Device Development] Stier16:
Its working fine for me too. No issues.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
No issue with 0316 build (automatic update with Lineage Downloader).

I confirm my previous post (https://xdaforums.com/showpost.php?p=79090015&postcount=1152): OTA updater fails with f2fs format (data and/or cache).

If I have time, I will try again with all the partitions in ext4 format.
[OnePlus 3 & 3T Cross Device Development] :
You've checked that already: https://xdaforums.com/showpost.php?p=79090015&postcount=1152 that's why I'm sure it's not f2fs related!
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
No issue with 0316 build, too!
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
About this post: https://xdaforums.com/showpost.php?p=79131243&postcount=1242

OTA updater fails for Samsung Galaxy S5+ (kccat) and Sony Xperia Z1 Compact (amami): Is it confirmed?

Note that Samsung Galaxy S5+ (kccat6) is currently supported in LineageOS 16.0 ... but that's not the case for Sony Xperia Z1 Compact (amami).
[OnePlus 3 & 3T Cross Device Development] Zebnastien:
Not working for me with YouTube Music : whenever jack is plugged, I heard the music 0.5 second in my headphones then I can't ear anything (but music keeps playing). All fine with Google Play Music. AudioFx doesn't change anything...

Spectacular ROM by the way, thx to Devs :)
[OnePlus 3 & 3T Cross Device Development] :
Deleting AudioFX completly from the device doesn't help? If so, please set the logbuffer to 4 Mio, reboot to system, reproduce in Yoitube and get a complete log, please.
[OnePlus 3 & 3T Cross Device Development] vinoxflame:
I just tried YouTube Music and it's ok on my side - AudioFx disabled, Sauron and V4A installed
[OnePlus 3 & 3T Cross Device Development] detective zero:
No, it's the op3 file. And I downloaded directly from the webpage. Really strange. Will try again later with today's build...
[OnePlus 3 & 3T Cross Device Development] Milka78:
Hi.

I'm wondering why the flashlight toggles on / off, when I swipe up in standby.

I can't find any menu to switch this function off.

Is it Lineageos or some other app?

Thanks

Milka
[OnePlus 3 & 3T Cross Device Development] 6bre6eze6:
System > Gestures > Touchscreen gestures maybe?
[OnePlus 3 & 3T Cross Device Development] :
Settings->System->Advanced->Gestures->Touchscreen gestures
[OnePlus 3 & 3T Cross Device Development] Milka78:
Found it! Thank you for the hint.

It's not very well described in german...

Milka
[OnePlus 3 & 3T Cross Device Development] xowzinho:
Anyone else having issues with the 16th March build?

After updating OTA or even dirty flashing after manual download, Bluetooth keeps stopping to the point I can't use the device.

Had to revert back to 15th March build.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
No such issue on my side with 0316 build... U2 via BT works fine!
[OnePlus 3 & 3T Cross Device Development] raphael.e:
I had the same issue, and hence also reverted to 15.03 nightly. I haven't tried 17.03 yet
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
I confirm no such issue on my side with the 0316 and 0317 builds... Tested with the stock music player on two BT devices.
[OnePlus 3 & 3T Cross Device Development] :
A detailed description (i.e. which bt functions and devices are effected: filetransfer, tethering, mice, keyboards, smart watches, fitness devices, audio devices [inkl. used codec]; what is the effect [detailed description, error messeges detailed observations]) and a complete log from boot to shortly after the issue (with logbuffer length 4 Mio.) would surely be helpfull to get the cause.